Active Topics
-
[ANNOUNCE] CSSU-thumb thread - stable Thumb2 on N900 (2,264)
to Maemo 5 / Fremantle by panjgoori - 22 mins ago -
Porting apps to Leste (31)
to Maemo 7 / Leste by HtheB - 7 hrs, 9 mins ago -
Full linux distros on Sailfish OS (254)
to SailfishOS by qoh - 22 hrs, 30 mins ago - more...
|
2013-06-18
, 14:37
|
|
Posts: 1,994 |
Thanked: 3,342 times |
Joined on Jun 2010
@ N900: Battery low. N950: torx 4 re-used once and fine; SIM port torn apart
|
#12
|
Originally Posted by pichlo
Wifi-switcher's purpose is to give you option of cutting off wireless LAN connectivity and restoring it whenever you want to, with possible battery charge savings as side-effect. Presumably, wifi-switcher sometimes doesn't properly restore wlan connectivity - I don't know about proof of this bug, but for me need-to-use-wifi (as if my life depended on it) is more rare than snowfall in Hell, so this bug, even if it actually exists, is non-important. Especially since a reboot would likely fix the problem.
Symptoms: "wlan connectivity loss"
Wow! For a package whose name clearly states and stated purpose is to cut off your network connection.
I am using this package, and I will use it in the future, but it's highly likely that I will finally rewrite its source into a Makefile-free package. It's too useful to remain uncomfortable to use. Just like GoldenDict.
When will somebody repackage GoldenDict for Fremantle? Then it would finally be possible to edit preferences in GUI, instead of xml file. The changes needed are small: .desktop file location, icons location, recompilation against Fremantle version of Qt libraries, probably a bug fix to display images.
Best wishes.
|
|
2013-06-18
, 14:43
|
|
Posts: 3,328 |
Thanked: 4,476 times |
Joined on May 2011
@ Poland
|
#13
|
Using auto-disconnect since I bought my n900 and absolutely no problems. Couldn't imagine not using it 
| The Following User Says Thank You to marmistrz For This Useful Post: | ||
|
|
2013-06-18
, 17:25
|
|
Posts: 2,290 |
Thanked: 4,133 times |
Joined on Apr 2010
@ UK
|
#14
|
Originally Posted by VulcanRidr
http://wiki.maemo.org/Community_SSU/Thumb
Okay, I was using CSSU, but CSSU Thumb? I didn't run across that in the repos.
FlopSwap is in my future...As is backupmenu. That will go on as soon as I flash.
Why do you recommend against overclocking? I have been running mine at 900 MHz for two years with no ill effects. And I could tell a difference between 600 and 900. At 900, it was a bit snappier.
The N900 wasn't really designed to operate at 900Mhz.
You will find the issue with the N900 is third party applications and widgets slowing down the system. A reflash, CSSU Thumb and Swap on uSD should solve the "snappiness" issue.
Originally Posted by fw190
Hmm I'm was using Auto-disconnect for a very long time and had no problems. The same goes for Wi-fi switcher.
Originally Posted by marmistrz
Using auto-disconnect since I bought my n900 and absolutely no problems. Couldn't imagine not using it
Originally Posted by Wikiwide
I have found with a fair bit of testing removing the wlan driver doesn't reduce current consumption.
Presumably, wifi-switcher sometimes doesn't properly restore wlan connectivity - I don't know about proof of this bug, but for me need-to-use-wifi (as if my life depended on it) is more rare than snowfall in Hell, so this bug, even if it actually exists, is non-important. Especially since a reboot would likely fix the problem.
I was testing wifi-switcher for a while and also advanced interface switcher I found no difference in consumption over a period of time. In fact I found most of them call dbus signals which stopped my device hitting C4 sleep.
As for autodisconnect this is a load of "ash" scripts that calls dbus signals to find out if you are using a function, it also stores a huge log file in /var.
Take a look at the sources before you install things you'll be surprised what you find. As mentioned it's not the best packaged application either.
While these bugs haven't effected everyone there have been a few reports of it. The device will not restart the wlan drivers correctly, for some people IIRC this resulted in a reflash due to wlan errors popping up in dmesg output even after a reboot.
I have come to the conclusion after testing many wifi-switchy applications over my Maemo life, they're just not worth the bother installing.
The best thing to do is:-
Settings > Internet Connections > Search Interval > None
...if your not planning on using the WLAN for a while.
__________________
Wiki Admin
sixwheeledbeast's wiki
Testing Squad Subscriber
- mcallerx - tenminutecore - FlopSwap - Qnotted - zzztop - Bander - Fight2048 -
Before posting or starting a thread please try this.
Wiki Admin
sixwheeledbeast's wiki
Testing Squad Subscriber
- mcallerx - tenminutecore - FlopSwap - Qnotted - zzztop - Bander - Fight2048 -
Before posting or starting a thread please try this.
| The Following 2 Users Say Thank You to sixwheeledbeast For This Useful Post: | ||
|
|
2013-06-18
, 17:41
|
|
Posts: 3,328 |
Thanked: 4,476 times |
Joined on May 2011
@ Poland
|
#15
|
Originally Posted by sixwheeledbeast
Wait, are you talking about wlancond not starting?
While these bugs haven't effected everyone there have been a few reports of it. The device will not restart the wlan drivers correctly, for some people IIRC this resulted in a reflash due to wlan errors popping up in dmesg output even after a reboot.
I have come to the conclusion after testing many wifi-switchy applications over my Maemo life, they're just not worth the bother installing.
The best thing to do is:-
Settings > Internet Connections > Search Interval > None
...if your not planning on using the WLAN for a while.
//edit: are all the problems with autodisconnect written somewhere? we could ask the dev to fix it..
| The Following User Says Thank You to marmistrz For This Useful Post: | ||
 |
|
2013-06-18
, 18:15
|
|
Posts: 6,445 |
Thanked: 20,981 times |
Joined on Sep 2012
@ UK
|
#16
|
Originally Posted by sixwheeledbeast
I had used AutoDisconnect for a while (a few months IIRC) and never had any problems with it, but in the end I had decided to take it off for the same reason. It is far superior to connect when I want to, do whatever there is to and disconnect. Manually.
I have come to the conclusion after testing many wifi-switchy applications over my Maemo life, they're just not worth the bother installing.
The best thing to do is:-
Settings > Internet Connections > Search Interval > None
I have a question regarding swap on SD. What are the relative merits of having it entirely on SD and having two swaps, one internal and one on SD, borh with the same priority? The latter is supposed to spread the bandwidth (or so I've been told) and it definitely seems that way;
Code:
~ $ cat /proc/swaps Filename Type Size Used Priority /dev/mmcblk1p2 partition 786368 74456 1 /dev/mmcblk0p3 partition 786424 74944 1 ~ $
|
|
2013-06-18
, 18:29
|
|
Posts: 2,290 |
Thanked: 4,133 times |
Joined on Apr 2010
@ UK
|
#17
|
Originally Posted by pichlo
Stripping swap is pointless.
I have a question regarding swap on SD. What are the relative merits of having it entirely on SD and having two swaps
The whole idea is to be able to "de-fragment" the swap by switching between swap spaces.
I created FlopSwap to be able to flip between two uSD swaps. This makes swap refreshing quicker as you only refresh the swap one way.
Also swap on uSD reduces the bottleneck to eMMC and device flash wear.
http://wiki.maemo.org/Flopswap
__________________
Wiki Admin
sixwheeledbeast's wiki
Testing Squad Subscriber
- mcallerx - tenminutecore - FlopSwap - Qnotted - zzztop - Bander - Fight2048 -
Before posting or starting a thread please try this.
Wiki Admin
sixwheeledbeast's wiki
Testing Squad Subscriber
- mcallerx - tenminutecore - FlopSwap - Qnotted - zzztop - Bander - Fight2048 -
Before posting or starting a thread please try this.
| The Following User Says Thank You to sixwheeledbeast For This Useful Post: | ||
|
|
2013-06-18
, 19:16
|
|
Posts: 473 |
Thanked: 141 times |
Joined on Jan 2009
@ Virginia, USA
|
#18
|
Okay, I'm throwing out a lifeline. I am having issues flashing my N900. I am using a Debian desktop, flasher 3.5, and
My exact steps were:
I have done it three times, and not gotten an allegedly good flash. The output from the Linux box says:
All three times, the N900 shuts off instead of rebooting. Twice I have gotten what looks like the initial screen, but everything has "Missing image" for the desktop background and all of the icons. (four across the center of the screen, and another in the bottom right.) The third time, I got the status indicator in the upper left corner as a pink rectangle with blocks where the characters and icons are, which is one of the symptoms that caused me to have to flash it in the first place.
Please note that I got these images from the skeiron site.
Does anyone have any idea what the problem is with the flash? Something with my procedure? Should I get the images from the Nokia site?
Thanks,
--vr
Code:
RX-51_2009SE_10.2010.13-2.VANILLA_PR_EMMC_MR0_ARM.bin RX-51_2009SE_20.2010.36-2.002_PR_COMBINED_002_ARM.bin (the US release of PR1.3)
- Turn off N900
- Open keyboard, hold U key and plug in USB cable
- Run [code]sudo flasher-3.5 -F RX-51_2009SE_10.2010.13-2.VANILLA_PR_EMMC_MR0_ARM.bin -f[code]
- When complete, run [code]sudo flasher-3.5 -F RX-51_2009SE_20.2010.36-2.002_PR_COMBINED_002_ARM.bin -f -R[code]
- When the reboot starts, unplug the USB cable.
I have done it three times, and not gotten an allegedly good flash. The output from the Linux box says:
Code:
$ sudo flasher-3.5 -F patched-VANILLA.bin -f flasher v2.5.2 (Oct 21 2009) Image 'mmc', size 255947 kB Version RX-51_2009SE_10.2010.13-2.VANILLA USB device found found at bus 006, device address 040. Found device RX-51, hardware revision 2101 NOLO version 1.4.14 Version of 'sw-release': RX-51_2009SE_21.2011.38-1_PR_MR0 Booting device into flash mode. Suitable USB device not found, waiting. USB device found found at bus 006, device address 041. Raw data transfer EP found at EP2. Image(s) flashed successfully in 39.759 s (6437 kB/s)!
Code:
$ sudo flasher-3.5 -F RX-51_2009SE_20.2010.36-2.002_PR_COMBINED_002_ARM.bin -f -R flasher v2.5.2 (Oct 21 2009) SW version in image: RX-51_2009SE_20.2010.36-2.002_PR_002 Image 'kernel', size 1705 kB Version 2.6.28-20103103+0m5 Image 'rootfs', size 185856 kB Version RX-51_2009SE_20.2010.36-2.002_PR_002 Image 'cmt-2nd', size 81408 bytes Version BB5_09.36 Image 'cmt-algo', size 519808 bytes Version BB5_09.36 Image 'cmt-mcusw', size 5826 kB Version rx51_ICPR82_10w08 Image '2nd', size 14720 bytes Valid for RX-51: 2217, 2218, 2219, 2220, 2120 Version 1.4.14.9+0m5 Image 'xloader', size 14848 bytes Valid for RX-51: 2217, 2218, 2219, 2220, 2120 Version 1.4.14.9+0m5 Image 'secondary', size 109440 bytes Valid for RX-51: 2217, 2218, 2219, 2220, 2120 Version 1.4.14.9+0m5 Image '2nd', size 14720 bytes Valid for RX-51: 2101, 2102, 2103 Version 1.4.14.9+0m5 Image 'xloader', size 14848 bytes Valid for RX-51: 2101, 2102, 2103 Version 1.4.14.9+0m5 Image 'secondary', size 109440 bytes Valid for RX-51: 2101, 2102, 2103 Version 1.4.14.9+0m5 Image '2nd', size 14848 bytes Valid for RX-51: 2307, 2308, 2309, 2310 Version 1.4.14.9+0m5 Image 'xloader', size 14848 bytes Valid for RX-51: 2307, 2308, 2309, 2310 Version 1.4.14.9+0m5 Image 'secondary', size 109440 bytes Valid for RX-51: 2307, 2308, 2309, 2310 Version 1.4.14.9+0m5 Image '2nd', size 14848 bytes Valid for RX-51: 2407, 2408, 2409, 2410 Version 1.4.14.9+0m5 Image 'xloader', size 14848 bytes Valid for RX-51: 2407, 2408, 2409, 2410 Version 1.4.14.9+0m5 Image 'secondary', size 109440 bytes Valid for RX-51: 2407, 2408, 2409, 2410 Version 1.4.14.9+0m5 Image '2nd', size 14848 bytes Valid for RX-51: 2301, 2302, 2303, 2304, 2305, 2306 Version 1.4.14.9+0m5 Image 'xloader', size 14848 bytes Valid for RX-51: 2301, 2302, 2303, 2304, 2305, 2306 Version 1.4.14.9+0m5 Image 'secondary', size 109440 bytes Valid for RX-51: 2301, 2302, 2303, 2304, 2305, 2306 Version 1.4.14.9+0m5 Image '2nd', size 14848 bytes Valid for RX-51: 2401, 2402, 2403, 2404, 2405, 2406 Version 1.4.14.9+0m5 Image 'xloader', size 14848 bytes Valid for RX-51: 2401, 2402, 2403, 2404, 2405, 2406 Version 1.4.14.9+0m5 Image 'secondary', size 109440 bytes Valid for RX-51: 2401, 2402, 2403, 2404, 2405, 2406 Version 1.4.14.9+0m5 Image '2nd', size 14720 bytes Valid for RX-51: 2104, 2105, 2106, 2107, 2108, 2109, 2110, 2111, 2112, 2113, 2114, 2115, 2116, 2117, 2118, 2119 Version 1.4.14.9+0m5 Image 'xloader', size 14848 bytes Valid for RX-51: 2104, 2105, 2106, 2107, 2108, 2109, 2110, 2111, 2112, 2113, 2114, 2115, 2116, 2117, 2118, 2119 Version 1.4.14.9+0m5 Image 'secondary', size 109440 bytes Valid for RX-51: 2104, 2105, 2106, 2107, 2108, 2109, 2110, 2111, 2112, 2113, 2114, 2115, 2116, 2117, 2118, 2119 Version 1.4.14.9+0m5 Image '2nd', size 14848 bytes Valid for RX-51: 2501, 2502, 2503, 2504, 2505, 2506 Version 1.4.14.9+0m5 Image 'xloader', size 14848 bytes Valid for RX-51: 2501, 2502, 2503, 2504, 2505, 2506 Version 1.4.14.9+0m5 Image 'secondary', size 109440 bytes Valid for RX-51: 2501, 2502, 2503, 2504, 2505, 2506 Version 1.4.14.9+0m5 Image '2nd', size 14848 bytes Valid for RX-51: 2607, 2608, 2609, 2610 Version 1.4.14.9+0m5 Image 'xloader', size 14848 bytes Valid for RX-51: 2607, 2608, 2609, 2610 Version 1.4.14.9+0m5 Image 'secondary', size 109440 bytes Valid for RX-51: 2607, 2608, 2609, 2610 Version 1.4.14.9+0m5 Image '2nd', size 14848 bytes Valid for RX-51: 2507, 2508, 2509, 2510 Version 1.4.14.9+0m5 Image 'xloader', size 14848 bytes Valid for RX-51: 2507, 2508, 2509, 2510 Version 1.4.14.9+0m5 Image 'secondary', size 109440 bytes Valid for RX-51: 2507, 2508, 2509, 2510 Version 1.4.14.9+0m5 Image '2nd', size 14720 bytes Valid for RX-51: 2201, 2202, 2203, 2204, 2205, 2206, 2207, 2208, 2209, 2210, 2211, 2212, 2213, 2214, 2215, 2216 Version 1.4.14.9+0m5 Image 'xloader', size 14848 bytes Valid for RX-51: 2201, 2202, 2203, 2204, 2205, 2206, 2207, 2208, 2209, 2210, 2211, 2212, 2213, 2214, 2215, 2216 Version 1.4.14.9+0m5 Image 'secondary', size 109440 bytes Valid for RX-51: 2201, 2202, 2203, 2204, 2205, 2206, 2207, 2208, 2209, 2210, 2211, 2212, 2213, 2214, 2215, 2216 Version 1.4.14.9+0m5 Image '2nd', size 14848 bytes Valid for RX-51: 2601, 2602, 2603, 2604, 2605, 2606 Version 1.4.14.9+0m5 Image 'xloader', size 14848 bytes Valid for RX-51: 2601, 2602, 2603, 2604, 2605, 2606 Version 1.4.14.9+0m5 Image 'secondary', size 109440 bytes Valid for RX-51: 2601, 2602, 2603, 2604, 2605, 2606 Version 1.4.14.9+0m5 USB device found found at bus 006, device address 041. Raw data transfer EP found at EP2. Using flashing protocol Mk II.
Please note that I got these images from the skeiron site.
Does anyone have any idea what the problem is with the flash? Something with my procedure? Should I get the images from the Nokia site?
Thanks,
--vr
|
|
2013-06-18
, 19:43
|
|
Posts: 6,445 |
Thanked: 20,981 times |
Joined on Sep 2012
@ UK
|
#19
|
@sixwheeledbeast,
This is the first time FloSwap come into the picture I am aware of it and appreciate its usefulness but I thought the talk was about using SD for swap to increase performance by
a) Using a medium faster than our relatively slow eMMC
b) Reducing bus contention between reads/writes to optfs/MyDocs and swap
My understanding was that with memory intensive operations, striped swap can increase performance, in a way similar to b) above. What I would like though is some exact numbers/benchmarks as these are all just speculations. That article says explicitly, "Depending on the performance of your microSD card, your N900 might now feel much faster when swapping takes place, about the same, or even slower - YMMV."
I'd assume that if the SD card's performance is the only determining factor, then a simple test with swap on eMMC, SD and both should give me the right numbers for any given card. I'd just like to know what kind of test this should be.
This is the first time FloSwap come into the picture I am aware of it and appreciate its usefulness but I thought the talk was about using SD for swap to increase performance by
a) Using a medium faster than our relatively slow eMMC
b) Reducing bus contention between reads/writes to optfs/MyDocs and swap
My understanding was that with memory intensive operations, striped swap can increase performance, in a way similar to b) above. What I would like though is some exact numbers/benchmarks as these are all just speculations. That article says explicitly, "Depending on the performance of your microSD card, your N900 might now feel much faster when swapping takes place, about the same, or even slower - YMMV."
I'd assume that if the SD card's performance is the only determining factor, then a simple test with swap on eMMC, SD and both should give me the right numbers for any given card. I'd just like to know what kind of test this should be.
| The Following 2 Users Say Thank You to pichlo For This Useful Post: | ||
 |
|
2013-06-18
, 19:59
|
|
Posts: 1,986 |
Thanked: 7,698 times |
Joined on Dec 2010
@ Dayton, Ohio
|
#20
|
Originally Posted by VulcanRidr
The procedure looks correct to me, although the Updating the Firmware page notes that you should power down the N900 between flashing the EMMC and rootfs (by temporarily removing the battery).
Does anyone have any idea what the problem is with the flash? Something with my procedure? Should I get the images from the Nokia site?
I hate to mention it, but this could just be a simple hardware failure. The cost of overclocking is reduced lifespan; the faster you run a chip, the shorter it lasts.
| The Following 2 Users Say Thank You to Copernicus For This Useful Post: | ||
 |
| Tags |
| fremantle, nokia n900 |
«
Previous Thread
|
Next Thread
»
|
All times are GMT. The time now is 17:16.
Wow! For a package whose name clearly states and stated purpose is to cut off your network connection.