Re: H.264 playback
While poking around the tableteer info, I ran into a chart of supported media player video file formats. There are significant limits to frame size of various video formats. Native video on higher end camera video is out of range. When my [EMAIL PROTECTED] mp4 video is scaled to full wide screen, the video details are lost as well as is overall viewability. The quality of HW scaling on N800 is excellent (bicubic according to S1D13745 TV-Out Mobile Graphics Engine product brief), so I don't think you would lose many video details. Also scaling is performed by hardware and does not consume any extra cpu resources, so there is no reason not to use it. It chops the audio into short blips while individual video frames take 5 or more seconds to load. While the N800 doesn't technically lock up, the home screen becomes unaccessible so killing the essentially locked up video player is difficult to impossible without rebooting the machine. At least when trying to view this particular video. While H.264 has a good potential for ARM11 optimizations, mplayer does not have any of them yet and I don't have any plans for adding such optimizations for my own reasons. And AAC audio decoder is not properly optimized for ARM in mplayer either. So using mplayer to watch H.264+AAC videos is not a very good choice right now. By the way, ARM has released some H.264 and AAC optimized libraries recently: http://arm.com/news/18441.html Who knows, maybe Nokia can use them in one of the next N800 firmware updates to provide H.264 video support in the built-in media player. ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
Re: Updates in red-pill mode
Updating in red pill mode is just asking to brick your device. I've heard of it happening almost every time. Use red pill mode as a temporary workaround for a single package, not as a way of life, no matter how much of a power user you are. The device just doesn't support it. Ryan Jonathan Greene wrote: I can't answer that as I have nothing to do with software releases... thats a Nokia / Maemo team question. I think you just need to tread lightly with Red Pill mode knowing it's an official unofficial (or perhaps unsupported) method of doing things. On 9/11/07, *Pedro Rodrigues de Almeida* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hello Jonathan, Why then should there be patches to some of the OS 2006 files? Do you mean that these patches could simply be experimental even though they have a version later than the ones installed in the 770? Does anybody at Nokia releases patches to essential OS 2006 system files which can be updated under red-pill mode? Cheers, Pedro - Original message - From: Jonathan Greene [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] To: Pedro Rodrigues de Almeida [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Cc: Maemo users maemo-users@maemo.org mailto:maemo-users@maemo.org Sent: Tue, 11 Sep 2007, 22:27:15 CEST Subject: Re: Updates in red-pill mode Welcome to the Matrix I don't think Red Pill mode is advised for general use or system updates. It's really more of a backdoor. I've used it to get Python to install in the past as it seems to get past the missing library error though I'm not sure that's so much of a good thing either. On 9/11/07, Pedro Rodrigues de Almeida [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hello, I have realized that in red-pill mode a series of system patches are available for installing, e.g., patches fr browser controls, opera etc. I have installed some of these patches - not all - and my 770 became more unstable ad even crashed to the point of aving to remove the battery to be able to reboot it. Opera also got a new look as new, orange scroll bars replaced the old ones. Is it recommended to install the updates in red-pill mode or is this unwise? Thanks, Pedro ___ maemo-users mailing list maemo-users@maemo.org mailto:maemo-users@maemo.org https://lists.maemo.orghttps://lists.maemo.org/mailman/listinfo/maemo-usersgt; /mailman/listinfo/maemo-usershttps://lists.maemo.org https://lists.maemo.org/mailman/listinfo/maemo-usersgt /mailman/listinfo/maemo-usersgt https://lists.maemo.org/mailman/listinfo/maemo-usersgt; -- Jonathan Greene +1.914.750.8740 AIM / iChat - atmasphere gtalk / jabber - [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Skype / Gizmo - JonathanGreene blogs - http://www.atmasphere.net/wp http://www.atmasphere.net/wpnbsp nbsp http://www.atmasphere.net/wpnbsp; / http://www.maemoapps.com -- Jonathan Greene +1.914.750.8740 AIM / iChat - atmasphere gtalk / jabber - [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Skype / Gizmo - JonathanGreene blogs - http://www.atmasphere.net/wp / http://www.maemoapps.com ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users -- Ryan Pavlik AbiWord Win32 Platform Maintainer, Art Lead: www.abisource.com AbiWord Community Outreach Project: www.cleardefinition.com/oss/abi/blog/ Optimism is the father that leads to achievement. -- Helen Keller The folder structure in a modern Linux distribution such as Ubuntu was largely inspired by the original UNIX foundations that were created by men with large beards and sensible jumpers. -- Jono Bacon, The Ubuntu Guide ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
Re: Memory corruption during WLAN use: detailled analysis and workaround
Hello Tilman, Well done, thank you. This was already observed but solution was not found. See details here https://bugs.maemo.org/show_bug.cgi?id=677 (comment #7). Please can you add your findings to the bug report? Frantisek ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
Re: Is the IPhone ready for Business?
On 9/11/07, Acadia Secure Networks [EMAIL PROTECTED] wrote: here is an interesting short video from the CNET www site that poses the question of whether or not the Iphone is ready for business use. [snip] Interesting. Thanks for that. The same question applies to the N800 and its future derivatives as well. marketing company=nokiaBut the *N*800 is a multimedia Internet Tablet. Its primary purposes are to provide a desktop-level Internet experience in your pocket, and excellent media functionality. Business users should look elsewhere.../marketing Of course, if you then start comparing the iPhone or iPod Touch with the N800 (multimedia devices which provide an Internet experience in your pocket), prepare to be flamed (at least by some on ITT). I agree with you, though, the Nokia Internet Tablets have a lot to learn to be acceptable to business (in many ways they're like the Psions of old - but even more insular). Cheers, Andrew -- Andrew Flegg -- mailto:[EMAIL PROTECTED] | http://www.bleb.org/ ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
Re: Memory corruption during WLAN use: detailled analysis and workaround
Tilman Vogel wrote: Very interested in any feedback, Oh, BTW, you can possibly track it down with latest bootmenu update with USB network recovery in initfs, see my blot at http://www.maemopeople.org/ or ITT thread here http://www.internettablettalk.com/forums/showthread.php?t=9649 You can log in and insert wlan modules yourself (possibly mixed with other modules) and continue with booting to determine which is the faulty one. When still in initfs you have also almost all memory free so the testing could be easier. If you need to compile something with uclibc toolchain, let me know. For N770 initfs this one is correct: http://www.scratchbox.org/download/files/sbox-releases/0.9.8/tarball/ scratchbox-toolchain-arm-gcc3.4.cs-uclibc-0.9.8.5.tar.gz It works even in apophis scratchbox used for 2.2 and latest Bora. Frantisek ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
Re: Memory corruption during WLAN use: detailled analysis and workaround
On 12 September 2007, Frantisek Dufka wrote: Well done, thank you. This was already observed but solution was not found. See details here https://bugs.maemo.org/show_bug.cgi?id=677 (comment #7). Please can you add your findings to the bug report? Maybe it is better to submit a new bugreport with the descriptive summary and all the details explained to keep bugzilla in a good shape? The following bugreports (hijacked by me later) are too vague and it is not clear if their initial reporters had the same problem or a different one, probably it is even better to close them as they are reported against older firmware release: https://bugs.maemo.org/show_bug.cgi?id=677 https://bugs.maemo.org/show_bug.cgi?id=820 On the other hand, the wifi related memory corruption problem is reproducible and confirmed by a lot of people, so it deserves its own bugzilla entry and can be handled individually. No matter if Nokia is going to do anything about it or not, it is better to have this bug recorded somewhere with all the relevant links (to cx3110x driver sources for example), ideas and other information, so that one of the community kernel hackers could try to fix it without the need to search and collect vital information from various places. Too bad I did not know about cx3110x garage project at that time and nobody cared to notify me, otherwise I would try doing something about this issue when I was investigating it. Unfortunately Nokia used to open parts of previously closed code without notifying anyone properly and then probably thinking: look, this idiot is complaining again about something that is already open :) Here is one spectacular example: http://www.internettablettalk.com/forums/showpost.php?p=51002postcount=15 http://www.internettablettalk.com/forums/showpost.php?p=51169postcount=18 Well, what do you think a community developer would do after receiving an answer like: 'this stuff is currently closed but we probably will consider what can be done about it'? Would he subscribe to kernel mailing lists and waste time tracking them every day in the hope that something gets suddenly committed there knowing that it may just as well never happen actually? Nokia has no responsibility to notify anyone about anything, but it's a communication problem that hurts everyone in the end. By the way, if the same wifi memory corruption gets confirmed on N800 too, probably the following issues can be also related to it: https://bugs.maemo.org/show_bug.cgi?id=999 https://bugs.maemo.org/show_bug.cgi?id=1608 https://bugs.maemo.org/show_bug.cgi?id=1990 ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
Re: Memory corruption during WLAN use: detailled analysis and workaround
ext Siarhei Siamashka [EMAIL PROTECTED] writes: On 12 September 2007, Frantisek Dufka wrote: Well done, thank you. This was already observed but solution was not found. See details here https://bugs.maemo.org/show_bug.cgi?id=677 (comment #7). Please can you add your findings to the bug report? Maybe it is better to submit a new bugreport with the descriptive summary and all the details explained to keep bugzilla in a good shape? Yes, please file a bug about this. It's a lot easier to track these kind of issues. One problem per bug report is a really good rule. It's not like we are running out of bug ids :) -- Kalle Valo ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
Re: Memory corruption during WLAN use: detailled analysis and workaround
ext Tilman Vogel [EMAIL PROTECTED] writes: This is going to be a bit longer, but may be interesting to many Nokia 770 users as I suspect that this problem is present on all 770s: Thank you for the excellent report, but I have some extra questions: What about N800 or is this reproducible only on 770? What are your WLAN settings? Is this related to some particular settings, like WPA for instance? How long does it take you to see the corruption with memtester? -- Kalle Valo ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
Re: Memory corruption during WLAN use: detailled analysis and workaround
On 9/11/07, Tilman Vogel [EMAIL PROTECTED] wrote: A few weeks ago I had a very bad spontaneous crash of my 770 making it unbootable. The progress bar never showed up. I could reflash, but got suspicious about what might have caused it. I started searching for a memory checker and found: Can you write protect the page getting corrupted and cause a kernel OOPS on the write? That would generate a stack trace that would target the offending code. Of course if DMA hardware is doing the write this won't work. -- Jon Smirl [EMAIL PROTECTED] ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
Questions #3: root
What's the cleanest way to get this? Thomas ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
Re: Memory corruption during WLAN use: detailled analysis and workaround
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi! Kalle Valo schrieb: What about N800 or is this reproducible only on 770? Unfortunately, I couldn't test this because I only have a 770... What are your WLAN settings? Is this related to some particular settings, like WPA for instance? I don't use WPA but I experienced it both without any encryption and with my WEP network. The fact that already scanning for networks causes the problem makes me think that it doesn't depend much on special settings... Also, the address stays the same in all cases. How long does it take you to see the corruption with memtester? With test sizes of about 24 MB, chances seem to be very good to catch the bad bytes. In other words, usually if I run memtester 24 after booting and still without WLAN, everything is ok. As soon as I click on Choose connection... and scanning starts, I see FAILURE messages from memtester. I don't have to wait for it. If they don't show up, it means memtester didn't get the corrupted bytes. Then it usually helps to start it again with a little bigger size. Also, when I shut down the WLAN connection, the errors immediately stop. If you have more questions, let me know. I'll also file my bug report soon. Best regards, Tilman -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFG6Fz09ZPu6Yae8lkRAhzKAKCny84mXBOxMoB5zxaa+7JGZ5XGkQCfW3l3 VmAD+N97YUAtnAfGpZqJG2Q= =OJRe -END PGP SIGNATURE- ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
Re: Questions #2: Nuking built-ins
Check out a few entries on my maemo info site for some advice on freeing up space on the root filesystem. http://sparrsstuff.com/maemo On 9/12/07, Thomas Leavitt [EMAIL PROTECTED] wrote: my / filesystem is pretty full already... ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
Re: Memory corruption during WLAN use: detailled analysis and workaround
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ok, I filed the bug: https://bugs.maemo.org/show_bug.cgi?id=2006 Do you think, I should add comments to the mentioned bug reports pointing to this one? Regards, Tilman -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFG6GY+9ZPu6Yae8lkRAlgZAKCdQM4hxMGmOySI+pvhl87N6ztLZwCfU/E+ k2TmJLnbCgmcE7NiULFZV+M= =y2Ss -END PGP SIGNATURE- ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
Re: Updates in red-pill mode
I didn't think there was a warning about red pill mode on the Wiki, so I added one to the red pill page: http://maemo.org/community/wiki/applicationmanagerredpillmode/ That might flush out an official comment (or not). regards, Paul Ryan Pavlik wrote: Updating in red pill mode is just asking to brick your device. I've heard of it happening almost every time. Use red pill mode as a temporary workaround for a single package, not as a way of life, no matter how much of a power user you are. The device just doesn't support it. Ryan Jonathan Greene wrote: I can't answer that as I have nothing to do with software releases... thats a Nokia / Maemo team question. I think you just need to tread lightly with Red Pill mode knowing it's an official unofficial (or perhaps unsupported) method of doing things. On 9/11/07, *Pedro Rodrigues de Almeida* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hello Jonathan, Why then should there be patches to some of the OS 2006 files? Do you mean that these patches could simply be experimental even though they have a version later than the ones installed in the 770? Does anybody at Nokia releases patches to essential OS 2006 system files which can be updated under red-pill mode? Cheers, Pedro - Original message - From: Jonathan Greene [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] To: Pedro Rodrigues de Almeida [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Cc: Maemo users maemo-users@maemo.org mailto:maemo-users@maemo.org Sent: Tue, 11 Sep 2007, 22:27:15 CEST Subject: Re: Updates in red-pill mode Welcome to the Matrix I don't think Red Pill mode is advised for general use or system updates. It's really more of a backdoor. I've used it to get Python to install in the past as it seems to get past the missing library error though I'm not sure that's so much of a good thing either. On 9/11/07, Pedro Rodrigues de Almeida [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hello, I have realized that in red-pill mode a series of system patches are available for installing, e.g., patches fr browser controls, opera etc. I have installed some of these patches - not all - and my 770 became more unstable ad even crashed to the point of aving to remove the battery to be able to reboot it. Opera also got a new look as new, orange scroll bars replaced the old ones. Is it recommended to install the updates in red-pill mode or is this unwise? Thanks, Pedro ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
Re: Questions #3: root
On Wednesday 12 September 2007 12:39:52 Thomas Leavitt wrote: What's the cleanest way to get this? Thomas ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users For me and my way of thinking. Install Xterm... Install openssh (as apposed to dropbear) from garage. open Xterm and do ssh [EMAIL PROTECTED] use rootme as the password. Add this line to /etc/sudoers user ALL=(ALL) NOPASSWD: ALL Now give bother the user named user and root real passwords. Once you do this user, user can sudo su to root whenever you need it to. I also recommend removing the ability of root to ssh directly after you have confirmed that you can sudo. James -- READ CAREFULLY. By [accepting this material|accepting this payment|accepting this business-card|viewing this t-shirt|reading this sticker] you agree, on behalf of your employer, to release me from all obligations and waivers arising from any and all NON-NEGOTIATED agreements, licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap, confidentiality, non-disclosure, non-compete and acceptable use policies (”BOGUS AGREEMENTS”) that I have entered into with your employer, its partners, licensors, agents and assigns, in perpetuity, without prejudice to my ongoing rights and privileges. You further represent that you have the authority to release me from any BOGUS AGREEMENTS on behalf of your employer. ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
