Guest Teasy Posted January 16, 2011 Report Posted January 16, 2011 Trying to overclock with SetCPU. Installed it but it keeps saying I don't have root access. I'm using this ROM which is rooted AFAIK, so not sure what the problem is. What device should I select at the start? (doesn't mention the Blade).
Guest z01z Posted January 16, 2011 Report Posted January 16, 2011 Trying to overclock with SetCPU. Installed it but it keeps saying I don't have root access. I'm using this ROM which is rooted AFAIK, so not sure what the problem is. What device should I select at the start? (doesn't mention the Blade). Check the root rights with Superuser, allow it for SetCPU
Guest Teasy Posted January 16, 2011 Report Posted January 16, 2011 (edited) Check the root rights with Superuser, allow it for SetCPU Right SetCPU has access, but I can't get any frequency above 528Mhz at the moment. What device should I choose? Edited January 16, 2011 by Teasy
Guest z01z Posted January 16, 2011 Report Posted January 16, 2011 I've got a problem with wifi, which became obvious since RLS6, the increase of wifi.supplicant_scan_interval to 180s. The problem is, when the phone comes back from sleep, it'll only reconnect after this wifi.supplicant_scan_interval elapsed. When I go to the wifi settings, it'll start scanning right away and reconnects. Any idea how to fix this? Thanks in advance!
Guest _amano Posted January 16, 2011 Report Posted January 16, 2011 Well, the long intervall is just a feature to save battery (though I am not sure if that is proven). If you need wifi instantly you can turn it off and on within the power widget or just go to the wifi settings.
Guest z01z Posted January 16, 2011 Report Posted January 16, 2011 Right SetCPU has access, but I can't get any frequency above 528Mhz at the moment. What device should I choose? Go to Menu/settings/applications/manage applications. Select SetCPU and force stop it and clear its data. Now start SetCPU and select the button with autodetect in it.
Guest z01z Posted January 16, 2011 Report Posted January 16, 2011 Well, the long intervall is just a feature to save battery (though I am not sure if that is proven). If you need wifi instantly you can turn it off and on within the power widget or just go to the wifi settings. I've tried this already, it doesn't help. Thanks though. Seems like the timer needs to pass before a scan. There's also a Blade wifi fix app in the market, which doesn't work for me either.
Guest Teasy Posted January 16, 2011 Report Posted January 16, 2011 (edited) Go to Menu/settings/applications/manage applications. Select SetCPU and force stop it and clear its data. Now start SetCPU and select the button with autodetect in it. Thanks, unfortunately the only device options it gives me are: G1/Dream/myTouch/Magic 32B [MSM7K] Motorola Droid/Milestone [OMAP3] Nexus One/Smapdragon [QSD8x50] Samsung Galaxy [MSM7k Turbo] Motorola Cliq [MSM7K] T-Mobile Pulse [MSM7K Turbo] Acer Liquid [QSD8x50] Samsung Moment [ARM] HTC Hero/Tattoo [MSM7k Turbo] - All features may not work with some kernels Custom Frequencies - Reads setcpu.txt on SD fat ext. Sort speed in kHz, seperate by comma, from lowest to highest. It does mention autodetect in the description above the options but no autodetect option is visible. Edited January 16, 2011 by Teasy
Guest _amano Posted January 16, 2011 Report Posted January 16, 2011 I've tried this already, it doesn't help. Thanks though. Seems like the timer needs to pass before a scan. There's also a Blade wifi fix app in the market, which doesn't work for me either. Well. It certainly takes more than just a few seconds to receonnect to my router, but it is cerstainly not 3 minutes...
Guest z01z Posted January 16, 2011 Report Posted January 16, 2011 It does mention autodetect in the description above the options but no autodetect option is visible. What rev do you have? Mine is 2.0.4. When I press the menu button in SetCPU, then select the device selection, I've got a page full of text with 3 buttons at the end. The middle button is "autodetect speeds recommended". I don't need to select any device...
Guest popoyaya Posted January 16, 2011 Report Posted January 16, 2011 Brilliant rom thanks for all the hard work. Are we any closer to fixing the phone/dialler battery drain? I'm getting 45% battery used by cell radio (Cell Standby) and 20% battery used when phone is idle (Phone Idle) even without having used dialler since boot. Also what is causing the phone to hang when on granting superuser permission? Can this be fixed? Also A2SD doesn't work on my EXT3 partition.
Guest Teasy Posted January 16, 2011 Report Posted January 16, 2011 (edited) What rev do you have? Mine is 2.0.4. When I press the menu button in SetCPU, then select the device selection, I've got a page full of text with 3 buttons at the end. The middle button is "autodetect speeds recommended". I don't need to select any device... I had an old version. I've just installed 2.0.2 (newest I could find) and it now lets me select autodetect. Still though it has the max speed fixed at 528Mhz ;) EDIT: Rebooted my phone and now it allows higher speeds. Thanks for all the help! Edited January 16, 2011 by Teasy
Guest IronDoc Posted January 16, 2011 Report Posted January 16, 2011 I've tried this already, it doesn't help. Thanks though. Seems like the timer needs to pass before a scan. There's also a Blade wifi fix app in the market, which doesn't work for me either. Just change wifi.supplicant_scan_interval back to what you want.
Guest LVL91 Posted January 16, 2011 Report Posted January 16, 2011 (edited) About the battery drain people, it has none on JJ RLS7. I have a second phone and use my OSF as an android laboratory like many of you do to. Since I had to make some exams, I wasn't able to experiment with the OSF, so I just left it on my desk. I regularly checked to see whether the battery has dropped/been drained. I have been looking for 2 days now, and the battery has dropped only for about 15%, that is incredible to see since my HTC Desire often likes to drain the battery. I am going to overclock it now @ a stable 710Mhz, set the Wifi interval back to 15 sec and see what the battery has to say next. Will let you know ;) Edited January 16, 2011 by LVL91
Guest popoyaya Posted January 16, 2011 Report Posted January 16, 2011 (edited) About the battery drain people, it has none on JJ RLS7. I have a second phone and use my OSF as an android laboratory like many of you do to. Since I had to make some exams, I wasn't able to experiment with the OSF, so I just left it on my desk. I regularly checked to see whether the battery has dropped/been drained. I have been looking for 2 days now, and the battery has dropped only for about 15%, that is incredible to see since my HTC Desire often likes to drain the battery. I am going to overclock it now @ a stable 710Mhz, set the Wifi interval back to 15 sec and see what the battery has to say next. Will let you know ;) Sorry, but the dialler is still showing with a high percentage of battery usage when idle. Whilst it may not amount to a huge drain it's still an annoying bug. Edited January 16, 2011 by popoyaya
Guest popoyaya Posted January 16, 2011 Report Posted January 16, 2011 hello I got massage during any change in mobile settings but everything is ok... PS1 i did not change ANYTHING. PS2 I see that this problem is not minor. Maybe you installed the Japanese Shiatsu rom by mistake? ;)
Guest nSkuL Posted January 17, 2011 Report Posted January 17, 2011 Maybe you installed the Japanese Shiatsu rom by mistake? ;) :'D
Guest Daminos Posted January 17, 2011 Report Posted January 17, 2011 Hello, How i apply the addons after installing the rom?
Guest jr866gooner Posted January 17, 2011 Report Posted January 17, 2011 Not sure if this effects others but I cannot sync with AppBrain with this rom at all! Am I alone?
Guest dwl99 Posted January 17, 2011 Report Posted January 17, 2011 Not sure if this effects others but I cannot sync with AppBrain with this rom at all! Am I alone? You beat me to it! I also have this problem, whether with wifi or 3G.
Guest dwl99 Posted January 17, 2011 Report Posted January 17, 2011 (edited) Sorry, but the dialler is still showing with a high percentage of battery usage when idle. Whilst it may not amount to a huge drain it's still an annoying bug. I also get the dialer using 48% of the battery. I installed Ray Dialer as an alternative to the stock dialer & now get the following: Cell standby 45% Phone idle 29% Display 23% Android System 3% Not sure if this is any better? Edited January 17, 2011 by dwl99
Guest ak167777 Posted January 17, 2011 Report Posted January 17, 2011 Thanks for the Brilliant rom and hard work ;) It works really fine for me
Guest M1kz Posted January 17, 2011 Report Posted January 17, 2011 Hello, How i apply the addons after installing the rom? same way as you install the rom
Guest Salsaholic Posted January 17, 2011 Report Posted January 17, 2011 [...]for some reason I cannot install ClockWorkMod and get it up running, is there any chance I can compile a TPT version with the hardware acceleration installed ? Also, can I compile a TPT with other rom's Zip files ? (out of curiosity) Once you used TPT to install RLS7, you will have RA Recovery installed (similar to ClockWork, just better ;)). You can then use the RA Recovery to install addons or even other ROMs - as long as these fit into the 128 MB system partition. So, no re-packing of the TPT image needed!
Guest Autarch Posted January 17, 2011 Report Posted January 17, 2011 Kallt, could you pleas provide a kernel with IPv6: Privacy Extensions enabled? The kernel does not use this by default, so every mobile can be identified in the net. CONFIG_IPV6_PRIVACY is already compiled into the kernel, but I think it's not enabled by default. A quick bit of Googling suggests you can hack it with sysctl, either with something like the following, which I guess could be added to your init.rc (which itself needs to be built into boot.img) sysctl -w net.ipv6.conf.default.use_tempaddr=2 sysctl -w net.ipv6.conf.all.use_tempaddr=2 I've now tested this from the command line and it works. Kallt suggests adding these to /system/bin/userinit.sh as in his ROMs this gets executed at the end of init.rc Adding similar lines (less the "sysctl -w" bit) to /etc/sysctl.conf may also work.
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now