Hello again xda, today I want to present something tiny, but nontheless important (in my view) for our old TF101 ...
The first working HOTPLUG governor for this device!
Q: What the hell is 'hotplug' ?
Hotplug Governor:
The “hotplug” governor scales CPU frequency based on load, similar to
“ondemand”. It scales up to the highest frequency when “up_threshold”
is crossed and scales down one frequency at a time when “down_threshold”
is crossed. Unlike those governors, target frequencies are determined
by directly accessing the CPUfreq frequency table, instead of taking
some percentage of maximum available frequency.
The key difference in the “hotplug” governor is that it will disable
auxillary CPUs when the system is very idle, and enable them again once
the system becomes busy. This is achieved by averaging load over
multiple sampling periods; if CPUs were online or offlined based on a
single sampling period then thrashing will occur.
Click to expand...
Click to collapse
As you can see, hotplug is able to deliver you the fastest experience and the most fps in game (kernel independant), but it also allows for completely switching off one core to save battery life. In my testings, that worked very well. I also found out, that with this governor, my TF is deep-sleeping like a baby. No governor around here (not even smartassv2 ... could deliver me this performance while maintaining a decent battery life).
Tested on EOS 4.2.1 with EOS4 kernel
But try out yourself:
NOTE: This works on any 2.X kernel available (my Harmony series, ELiTE series, KatKernel series, or any other kernel except my divemaster)
Code:
1) Download a terminal emulator (if you don't have one already)
2) Download the .ko module from [URL="https://dl.dropbox.com/u/31119007/xda/hotplug-tegra-2/cpufreq_hotplug.ko"]here[/URL]
3) Remember the path you saved the module to (or preferably move it into /system/lib/modules)
4) su
5) insmod path-to-module/cpufreq_hotplug.ko
6) Switch to 'hotplug' governor with your favourite tool.
If you were too lazy to read my instructions, this is for you ..
DOWNLOAD
As always, have fun, share, and report back!
I have followed the instructions, do I have to run it every reboot or just this one off?
Nothing really happened when I ran it but I guess it just loads the module.
Cheers buddy
Must say thanks again for all the amazing work!
pops106 said:
I have followed the instructions, do I have to run it every reboot or just this one off?
Nothing really happened when I ran it but I guess it just loads the module.
Cheers buddy
Click to expand...
Click to collapse
Ahaha figured it out, it adds the govenor so we can then change it.
Cheers
---------- Post added at 08:41 PM ---------- Previous post was at 08:36 PM ----------
pops106 said:
Ahaha figured it out, it adds the govenor so we can then change it.
Cheers
Click to expand...
Click to collapse
wouldn't wake up after putting it to sleep, had to hold power button till it rebooted then it is gone from the options.
Soz
Running eos3 and kat69
Cheers
Good work! I was trying to do this same thing the cpusleeper app but couldnt get it to work. Definitely giving this a go.
Edit: installed fine but wont survive a reboot. Any fix for e this?
Sent from my Transformer TF101 using xda premium
Got a reboot while browsing with stock browser for five minutes.
Eos81,kat kernel
The only problem as 2 people discribe abovme is RR or Random Reboot.
Thats only problem.
sounds very promising i'll try it out and report if I get any RR's.
Getting error insmod: Can't open 'path-to-module/cpufreq_hotplug.ko'
Cd to my download folder which is where it is, am I doing something wrong?
morphuex said:
sounds very promising i'll try it out and report if I get any RR's.
Getting error insmod: Can't open 'path-to-module/cpufreq_hotplug.ko'
Cd to my download folder which is where it is, am I doing something wrong?
Click to expand...
Click to collapse
path-to-module should be the path the the module.
st0nedpenguin said:
path-to-module should be the path the the module.
Click to expand...
Click to collapse
Wow I derped that up, thx lol.
Was running fine at 1.2 decided to bump it up to 1.4 hit apply and it rebooted on me, is also didn't stick after reboot like others have said.
In here you may find how to make permanent the governor insmod.
Long story short is "add a script in /system/etc/init.d , it can be something like 91modules. . Add execution permission and it can contain the same code as before. Reboot and it should load your module at boot (be sure that the path to your module is right).
Also, you can do that in one line as root in a terminal. First, be sure that your /system is mounted as rw, not ro. If you don't know how to do that, as root, in a terminal, execute:
Code:
mount -o remount,rw /system
Then:
Code:
echo -e \#\!/system/bin/sh'\n'insmod [B]/path/to/module[/B]/cpufreq_hotplug.ko > /system/etc/init.d/91modules | chmod +x /system/etc/init.d/91modules
"
It should load automatically next time you reboot.
I created the 91modules file and done the editing and file permission in ES File Manager, but the above instructions should work flawlessly.
Don't thank me for this. Thank MapleSyrup
RaymaFX, you always amaze me!:victory:
hunterval said:
RaymaFX, you always amaze me!:victory:
Click to expand...
Click to collapse
Posts like this are keeping my work up and my releases coming.
People like you are the reason I am putting this much effort in this kinda old device .
For those who experience SOD/RR with hotplug and can confirm it's not related to anything else, please gimme a dsmg/ksmg (I recommend using 'Lumberjack' from the playstore (made by Chris Trotman, EOS founder).
*NO* logcat, that isn't any useful for me in this case ..
I do now have 2 days uptime with hotplug governor, not a single SOD/RR, pretty much usage (wifi on all the time, a little Riptide GP, web browsing, most of the time playing music) and still got 20% left with EOS4 kernel while achieving full performance while needed. This thing is deep-sleeping just perfectly.
I have placed the hotplug in the system this morning and my battery life still 99% im using it with dock and dono m8 but if theres any problem but seems my tf101 dont consume energy at all im starting to get scarry lol
Sent from my Transformer TF101 using xda app-developers app
turtlemask said:
In here you may find how to make permanent the governor insmod.
Long story short is "add a script in /system/etc/init.d , it can be something like 91modules. . Add execution permission and it can contain the same code as before. Reboot and it should load your module at boot (be sure that the path to your module is right).
Also, you can do that in one line as root in a terminal. First, be sure that your /system is mounted as rw, not ro. If you don't know how to do that, as root, in a terminal, execute:
Code:
mount -o remount,rw /system
Then:
Code:
echo -e \#\!/system/bin/sh'\n'insmod [B]/path/to/module[/B]/cpufreq_hotplug.ko > /system/etc/init.d/91modules | chmod +x /system/etc/init.d/91modules
"
It should load automatically next time you reboot.
I created the 91modules file and done the editing and file permission in ES File Manager, but the above instructions should work flawlessly.
Don't thank me for this. Thank MapleSyrup
Click to expand...
Click to collapse
I typed all this in and it wont survive uve a reboot. I placed the module in /system/lib/modules and typed that. When i see the | is that a new line or all one line?
Sent from my Transformer TF101 using xda premium
You can make that code in 2 commands, 1st is all before the | and 2nd the command after the |.
In order to work your final 91modules should look like
Code:
#!/system/bin/sh
insmod /system/lib/modules/cpufreq_hotplug.ko
In order to test if it's working you cat try to run it from the terminal (it may need "su" before)
Code:
./system/etc/init.d/91modules
If it's not complaining about not being executable, you may test to see if it's loaded with "lsmod".
If it's loaded it surely will survive the reboot.
I hope that helps you.
Looks like it created the 91modules file in init.d but when i try to set permissions using chmod +x it says bad mode. Maybe thats why it isnt working, wrong permissions.
Sent from my Transformer TF101 using xda premium
Indeed the chmod +x command doesn't work.
You may use ES file explorer to set file permissions but also you need to allow it superuser access, mount /system as writable and "up to root" and mark execute and write to the user. At the end the file should have the following permissions: rwx r-- r--
Ill give that a try and see if that does it. Thanks!
thanks
Thanks RaymanFX, this is a great addition to our device.
Also thanks to all your work, you are keeping this device alive...
Related
LAST UPDATE to this thread.
RC1 of Collin_ph battery tweak has been released.
Due to several changes, etc.. I'm starting a new thread here: http://forum.xda-developers.com/showthread.php?t=762283
Newest!
UPDATE - Beta 10 released 08/16/2010
Sorry about 2 updates really quick-- this latest release was to address 2 bugs that cropped up.
Description: Battery tweak is a collection of settings that enable the hero to optimize battery lifetime. I get 35+ hours on my hero with the tweak installed with the normal 691mhz settings. When on battery power, the cpu is gradually lowered (configurable) as the battery drains, and when put on power, the cpu is put into high performance mode. Most settings are configurable.
Beta 6 includes an optional LED fix if your charging LED is hanging, and some optional performance tweaks to the cfs scheduler. For more information see the documentation linked below.
Simply download the tweak and flash.
Reboot and under adb shell run batt-cfg
Note: Make sure you are root first by running su if you are going to run batt-cfg through terminal.
You may change the settings at any time by running batt-cfg again and settings will take effect without rebooting.
New verison as of 08/16
http://www.primoweb.com/froyo/collin_ph_battery_tweak_v3_beta10.zip
Documentation (Updated for Beta 10):
http://www.primoweb.com/froyo/battery_tweak_v3.html
This tweak will conflict with setCPU and OCWidget, so please disable them.
Can I say it again. Don't use set CPU, or OCWidget. You don't need them with this tweak. If you want to customize your CPU, simply run the customize utility in batt-cfg -- you can set your min/max clock speeds there. Thanks!
Feature list:
Customizable Battery Tweak with 2 presets
LED Fix for charging LEDs that are stuck on
Experimental CFS (completely fair scheduler) performance tweaks
Audio quality fix for froyo (disables stagefright)
Disk tweaks (mounts all mount points noatime,nodiratime)
Probably more I'm missing.
Edit:
If you want to try this tweak in another rom, your rom will need a /system/etc/init.local.rc file-- that's where the service is started.
Additionally, it won't do much good unless it's on a clockable kernel.
There are other prerequisites such as sh existing in /system/bin but generally speaking if it starts up, it should work. If your rom has no /system/etc/init.local.rc, you can add the file and "import" it (I believe), within the init.rc of the boot image, but it'll require a little work.
collin_ph said:
Description: Battery tweak is a collection of settings that enable the hero to optimize battery lifetime. I get 35+ hours on my hero with the tweak installed with the normal 748mhz settings. When on battery power, the cpu is gradually lowered (configurable) as the battery drains, and when put on power, the cpu is put into high performance mode. Most settings are configurable.
Simply download the tweak and flash.
Reboot and under adb shell run batt-cfg
You may change the settings at any time by running batt-cfg again and settings will take effect without rebooting.
http://www.primoweb.com/froyo/collin_ph_battery_tweak_v3_beta4.zip
Documentation:
http://www.primoweb.com/froyo/battery_tweak_v3.html
Note: I don't recommend setting the "charging" minimum speed any higher than 480mhz, as it may not charge when connected by USB (not charger).
This tweak will conflict with setCPU and OCWidget, so please disable them.
Click to expand...
Click to collapse
is there a way to get this tweak to work on a 2.1 sense rom
Papa Smurf151 said:
is there a way to get this tweak to work on a 2.1 sense rom
Click to expand...
Click to collapse
It should work with any .29 kernel that's has the same structuring as toasts/darchs, so theoreticaly, it'll work with any ROM really.
Can this be done if I'm using the darch overclock undervolt kernel for Fresh 2. 3. 3? The reason I'm asking is because my battery life is already good with darch's kernel but if I can flash this on top of what I'm using that would be great.
Sent from my HERO200 using XDA App
aerajan said:
Can this be done if I'm using the darch overclock undervolt kernel for Fresh 2. 3. 3? The reason I'm asking is because my battery life is already good with darch's kernel but if I can flash this on top of what I'm using that would be great.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Only way to find out, try it.
Only problem is that I have no idea how to config the settings after setting this up. The instructions say to go back into the shell and configure the battery settings. Guess I will have to wait until someone who knows what they're doing tries. I don't have any skills at working within shell and wouldn't know what coding to write.
aerajan said:
Only problem is that I have no idea how to config the settings after setting this up. The instructions say to go back into the shell and configure the battery settings. Guess I will have to wait until someone who knows what they're doing tries. I don't have any skills at working within shell and wouldn't know what coding to write.
Click to expand...
Click to collapse
Go into shell and type "batt-cfg"
i have tested on my red dawn rom and it is working. Thanks for the tweak man
Thank you for this tweak. I have been using it for a few days and getting 30+ hrs. Awesome work
Sent from my HERO200 using XDA App
I tried going into terminal emulator just to test out the batt-cfg, and it continues to tell me permission denied. Granted I haven't flashed the update yet, so maybe that's why... at least on that.
I'm a straight noob when it comes to this stuff, I can't seem to get it to work, always getting permission denied on terminal emulator.
Thanks! Configured mine to use the 748mhz setting.
Can I do batt-cfg thru terminal?
Update: keep getting this when I do it through terminal
Loading 748mhz defaults
Saving Settings...
mount: permission denied (are you root?)
/system/bin/batt-cfg: cannot create /system/etc/batt.conf: read-only file system
/system/bin/batt-cfg: cannot create /system/etc/batt.conf: read-only file system
/system/bin/batt-cfg: cannot create /system/etc/batt.conf: read-only file system
/system/bin/batt-cfg: cannot create /system/etc/batt.conf: read-only file system
/system/bin/batt-cfg: cannot create /system/etc/batt.conf: read-only file system
/system/bin/batt-cfg: cannot create /system/etc/batt.conf: read-only file system
/system/bin/batt-cfg: cannot create /system/etc/batt.conf: read-only file system
/system/bin/batt-cfg: cannot create /system/etc/batt.conf: read-only file system
mount: permission denied (are you root?)
Settings Saved.
Starting batt.sh
Started
NOTE: when you exit ADB or terminal, you may have to hit CTRL-C
$
Sent from my Hero CDMA using XDA App
Is there a difference between this and setting profiles in SetCPU for different battery levels?
platinumrug said:
I tried going into terminal emulator just to test out the batt-cfg, and it continues to tell me permission denied. Granted I haven't flashed the update yet, so maybe that's why... at least on that.
I'm a straight noob when it comes to this stuff, I can't seem to get it to work, always getting permission denied on terminal emulator.
Click to expand...
Click to collapse
I do believe u have to type su to get it to work on terminal to get it to work (thanks duff.... i was completely off and to think i use terminal hah)
xxproblemzxx said:
Can I do batt-cfg thru terminal?
Update: keep getting this when I do it through terminal
Loading 748mhz defaults
Saving Settings...
mount: permission denied (are you root?)
/system/bin/batt-cfg: cannot create /system/etc/batt.conf: read-only file system
/system/bin/batt-cfg: cannot create /system/etc/batt.conf: read-only file system
/system/bin/batt-cfg: cannot create /system/etc/batt.conf: read-only file system
/system/bin/batt-cfg: cannot create /system/etc/batt.conf: read-only file system
/system/bin/batt-cfg: cannot create /system/etc/batt.conf: read-only file system
/system/bin/batt-cfg: cannot create /system/etc/batt.conf: read-only file system
/system/bin/batt-cfg: cannot create /system/etc/batt.conf: read-only file system
/system/bin/batt-cfg: cannot create /system/etc/batt.conf: read-only file system
mount: permission denied (are you root?)
Settings Saved.
Starting batt.sh
Started
NOTE: when you exit ADB or terminal, you may have to hit CTRL-C
$
Sent from my Hero CDMA using XDA App
Click to expand...
Click to collapse
Type su in the terminal first to make it root.
Sent from my CDMA Hero running CM6 using the XDA application.
duffkitty said:
Type su in the terminal first to make it root.
Sent from my CDMA Hero running CM6 using the XDA application.
Click to expand...
Click to collapse
Ah lol totally 4got. Thanks man
Sent from my Hero CDMA using XDA App
Testing.... will post results tomorrow
black7 said:
Is there a difference between this and setting profiles in SetCPU for different battery levels?
Click to expand...
Click to collapse
I was wondering the same thing
Don't know if there is an actual difference, but my phone seems a lot smoother now. As though I eliminated a huge bog from it's processes.
atoz350 said:
Don't know if there is an actual difference, but my phone seems a lot smoother now. As though I eliminated a huge bog from it's processes.
Click to expand...
Click to collapse
Did you have it OC'd before?
hi everyone
I present to you:
Darkness in the dark hours
this is a pack of:
- a script I made
- Gscript lite
- Screen filter(optional, but recommended)
I strongly recommend to you to read the whole post and only then apply my script!
A lot of users tried to find a way to do this, so I polished my script I used for Eternity to make it universal(hopefully )
this script made to work with rooted 2.1+ firmwares and busybox properly installed.
1. Install Gscript lite
2. To make this script revertable on the newer brand of kernels, you will need to add one line to hw_config.sh (because I just don't trust init.d scripts)
run this from adb or any terminal emulator from phone as superuser
Code:
echo "\n\n\nrm /data/noled_tmp_reverse.prop" >> /system/etc/hw_config.sh
3. in Gscript choose Add a script and name it whatever you want(e.g. NOLed) and paste these lines in it
Code:
#! /system/bin/busybox sh
# "turn off keyboard and notification LEDs" for ANY android firmware
# this script needs su access
# made by Adolf1994
# thanks for the help diimaan
# maybe final version - revertable
# requires hw_config.sh modification to be properly revertable
DIR=$(cd /sys && find | grep brightness | cut -c 3- | cut -d : -f 1 | head -n 1)
LED=/sys/$DIR
LED1=$LED:rgb1:red/brightness
LED2=$LED:rgb1:green/brightness
LED3=$LED:rgb1:blue/brightness
LED4=$LED:sled/brightness
if [ -s /data/noled_tmp_reverse.prop ]; then
chmod 00644 $LED1
chmod 00644 $LED2
chmod 00644 $LED3
chmod 00644 $LED4
rm /data/noled_tmp_reverse.prop
else
echo 0 > $LED1
echo 0 > $LED2
echo 0 > $LED3
echo 0 > $LED4
chmod 00444 $LED1
chmod 00444 $LED2
chmod 00444 $LED3
chmod 00444 $LED4
echo 1 > /data/noled_tmp_reverse.prop
fi
exit
4. tap on "Needs SU" then save
5. run the script and enjoy surfing at night without the annoying hw leds
(most likely you WILL get stderrs on 2.2+, but it's normal)
Note: if you get EMPTY stderrs, that's no problem. BUT if something is shown next to the stderr, like permission denied, then please report
optional. install Screen filter from market: https://market.android.com/details?id=com.haxor&feature=search_result
This is only for 2.1 and/or 2.2. On 2.3 I experienced a problem that's I couldn't press install in package installer activity. I nearly reinstalled the whole thing. You've been warned!
Night is over? Just run the script again and wait till the LEDs light up.
If You Don't Like LEDs At All, This Pretty Line Will Disable Them At Startup
http://forum.xda-developers.com/showpost.php?p=17514012&postcount=27
Q: Why modifying hw_config.sh?
A: Because if you reboot your phone while the leds are off, there will remain a file that normally indicates how the script should act upon running it. That one particular file should not present after boot.
Q: I'm on Wolfbreak's ROM. Won't that mess tweaks up?
A: In no way. Impossible. Unless you didn't follow steps properly.
hope you like it
and don't forget to press thanks button
can I use script manager to run this at boot?
I think it'd be fine
the script didnt work for me i went to my dolphin browser copied text pasted it saved i run it it showed up stderr twice that's it?
shahkam said:
the script didnt work for me i went to my dolphin browser copied text pasted it saved i run it it showed up stderr twice that's it?
Click to expand...
Click to collapse
i cant paste the text corectly ffs i think thats the problem can you upload the script as ".sh" so i can load it whit gscript?
shahkam said:
the script didnt work for me i went to my dolphin browser copied text pasted it saved i run it it showed up stderr twice that's it?
Click to expand...
Click to collapse
from gscript I get a bunch of stderrs, too. however, from a terminal emulator it runs fine, so no problem.
It's the most noticeable if the phone is on the charger, because you will see that the led suddenly switches off.
you can revert the script back with a simple reboot.
Sorry for being a noob, but what does this do? :$
It disables the l.e.d.s. It should be made a little clearer in op.
Is there a script to turn them back on?
Sent from my X10a using XDA App
AyDee said:
It disables the l.e.d.s. It should be made a little clearer in op.
Is there a script to turn them back on?
Sent from my X10a using XDA App
Click to expand...
Click to collapse
sorry if I wasn't clear. I'll fix it soon
and change it to revertable, too
Adolf any clue why it didnt work.for me and i kept having stderr thingy
Sent from my X10i using XDA Premium App
shahkam said:
Adolf any clue why it didnt work.for me and i kept having stderr thingy
Sent from my X10i using XDA Premium App
Click to expand...
Click to collapse
since they are empty it's ok
Huh? I think i wasnt clear i used your script and when i ran it whit gscript i got twice stderr message twice one under the other like this
Stderr
Stderr any clue why?
Sent from my X10i using XDA Premium App
shahkam said:
Huh? I think i wasnt clear i used your script and when i ran it whit gscript i got twice stderr message twice one under the other like this
Stderr
Stderr any clue why?
Sent from my X10i using XDA Premium App
Click to expand...
Click to collapse
for this script only gscript gives empty stderrs. if I run it with a terminal emulator/adb there's no stderr.
it's a problem of gscript
@Adolf or @My_Immortal
any new experiments with sd card mounting?
There was some interesting posts by one shaun in link2sd thread! he's using x10! somehow he managed to find more free space in /system than in /data!
so no need of an extra partition, you can just run the script to mount the /system as rw on boot and then link the link2sd mount point to it! I sent a PM to him about how is it working! let's see...
Ohhh but i tried terminal too pasted the script and nothing happened?
Sent from my X10i using XDA Premium App
I use this script most nights now, thanks Adulf! perhaps a mod to the script could be to set an expiry time value? (or is this not possible!)
diimaan said:
@Adolf or @My_Immortal
any new experiments with sd card mounting?
There was some interesting posts by one shaun in link2sd thread! he's using x10! somehow he managed to find more free space in /system than in /data!
so no need of an extra partition, you can just run the script to mount the /system as rw on boot and then link the link2sd mount point to it! I sent a PM to him about how is it working! let's see...
Click to expand...
Click to collapse
There are currently 190 MB free in my system partition, 219 MB in data and 11 GB in my sdcard, so I really want to use Links2SD on an ext partition in my SD, rather than anywhere else!
But it's nice that there's progress!!
My_Immortal said:
There are currently 190 MB free in my system partition, 219 MB in data and 11 GB in my sdcard, so I really want to use Links2SD on an ext partition in my SD, rather than anywhere else!
But it's nice that there's progress!!
Click to expand...
Click to collapse
190 mb? that's far less you should clean up some junk in your system then!
btw this is the msg I got from shaun! you can check how it works!
http://forum.xda-developers.com/show...&postcount=834
Should explain how to do it, just need to add commands to a start up script that is editable on your phone, that runs before the GUI is started. Dunno how I would create a universal script as you will need to edit diff files on diff phones.
If there is anything you don't understand from my post I'll try and help.
Click to expand...
Click to collapse
Brilliant this is exactly what i wanted, thanks Adolf !!
[email protected] said:
I use this script most nights now, thanks Adulf! perhaps a mod to the script could be to set an expiry time value? (or is this not possible!)
Click to expand...
Click to collapse
Adulf... hehh, funny
yyeeeeaaaaaaahhhh...no
that'd be a bit complicated.
but this is why it's revertable
Hello All,
I have looked on every forum I can think of for the past two days and can not find an answer to my problem anywhere... so if i am double posting i am very sry please point me in the right direction...
I successfully rooted my gf's optimus t yesterday using Z4root (extremely easy!!) My problem occurs when i try to flash the recovery thunderg.... I have tried many many times using a Terminal Emulator from the market and then (after much headache) I taught myself how to use adb shell. With both applications and after all my attempts I get the error message: cannot create /system/bin/flash_image: read-only file system. I have followed all the steps as carefully as I can from: All In One Recovery from Android Forums.
Here is the code I followed:
$ su
# mount -o remount,rw -t yaffs2 (your device /system path) /system
# cat /sdcard/flash_image > /system/bin/flash_image
# chmod 755 /system/bin/flash_image
# mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
# flash_image recovery /sdcard/(your device recovery.img name)
# sync
I get the error after I enter: # cat /sdcard/flash_image > /system/bin/flash_image
Any help would be much appreciated thanks!
HTC Sensation 4G
Cyanogenmod 7.0 beta
Overclocked
Why not just use ROM Manager to flash recovery?
&10chars
I have used ROM Manager in the past to flash but I thought I remembered reading somewhere that the LG p509 was having issues with clockworkmod??
btw thanks for the quick reply!
I've used rom manager twice to flash recovery for optimus t ...never any problems...
Sent from my LG-P509 using xda premium
Excalibur6677 said:
I have used ROM Manager in the past to flash but I thought I remembered reading somewhere that the LG p509 was having issues with clockworkmod??
btw thanks for the quick reply!
Click to expand...
Click to collapse
Only if you flash wrong device.
&10chars
Excalibur6677 said:
I get the error after I enter: # cat /sdcard/flash_image > /system/bin/flash_image
Click to expand...
Click to collapse
rom manager can randomly cause problems, so id stick with this first.
what is the error that you get? check the following:
is the file "flash_image" located in the root of your sdcard? and make sure that the name of the file is "flash_image." if that is not the name of the file, replace "flash_image" in the command with whatever the file name is
You're receiving that error because you didn't copy flash_image to your sdcard.
Download it here
I went ahead and used Rom Manager (figured what the hell) and it worked great! Thanks to everyone for your help!
Now that I have flashed Mik's CM7 I tried flashing francos 19.4 kernel to overclock. Everytime I would set the over clock over 748 the phone would freeze, a white screen would appear, and the phone would reboot.... any suggestions??
Excalibur6677 said:
I went ahead and used Rom Manager (figured what the hell) and it worked great! Thanks to everyone for your help!
Now that I have flashed Mik's CM7 I tried flashing francos 19.4 kernel to overclock. Everytime I would set the over clock over 748 the phone would freeze, a white screen would appear, and the phone would reboot.... any suggestions??
Click to expand...
Click to collapse
That's classic kernel panic. Lower your overclock and try again. Keep lowering until it's stable.
That what I read but I was hoping there was another option... I was looking forward to pushing this little beast a little haha
Go to 729,710...729 is recommended but some users claim to get as high as 806, I've never used higher that 787, what your experiencing is called a KP (kernel panic)...try changing your governor around than OC at higher than 710 and see what your phone is doing...or try to start over from scratch...wipe it all than reflash rom than OC....just a heads up I run 480/729-767 on interactivex (governor) and noop for I/O scheduler..follow my configuration and see what it does for you
Sent from my LG-P500 using xda premium
Excalibur6677 said:
That what I read but I was hoping there was another option... I was looking forward to pushing this little beast a little haha
Click to expand...
Click to collapse
It's luck of the draw. Some can do 768 or better while others struggle at 729.
For example, mine is stable at 748 but panics at 768.
Trust me, your phone is a whole lot better now than when you bought it
Oh no question about it!! Its running sooo much smoother. The Optimus is actually my gf's phone. I put CM7 on it because I running it on my HTC Sensation and its awesome!
You can only push this device so far before you fry it, settle for adequate performance and stellar battery life....I'm not even sure why there's an option for us to OC past 787, our phones don't have a snapdragon processor....some roms can handle OC at higher voltages and some can't, most I got out of cm7 is 787 but its not stable enough for me
Sent from my LG-P500 using xda premium
Thanks man Ill take your word for it! Any other suggestions/concerns with the phone?? I just flashed the rom yesterday so i dont know what to expect (as far as bugs and such) are there any nightlies yet?
Well if you have a computer, learn how to code source and you can cook roms for everyone else to enjoy....there is alot more to android development other than the basics...ie...root than custom recovery and custom roms....speaking of kernel panics, I just had one at 748 on popdogs oxygen port, cm7 I can easily run 767...btw are you using no frills or setcpu
Sent from my LG-P500 using xda premium
Jrhodes85 said:
You can only push this device so far before you fry it, settle for adequate performance and stellar battery life....I'm not even sure why there's an option for us to OC past 787, our phones don't have a snapdragon processor....some roms can handle OC at higher voltages and some can't, most I got out of cm7 is 787 but its not stable enough for me
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
Actually, CPU's rarely fail due to OC'ing. Instability forces you to lower the clock. The phone's metal casing and battery acts as a heatsink.
Batteries on the other hand are extremely susceptible to damage due to excessive heat. This is what you need to watch.
Is the stuff hard to learn? I'm not bad with a computer but to be honest it took me like two hrs to figure out how to adb shell haha... i believe im using setcpu with the interactiveX governor but i dont have the phone right in front of me so im not sure..
Excalibur6677 said:
Is the stuff hard to learn? I'm not bad with a computer but to be honest it took me like two hrs to figure out how to adb shell haha... i believe im using setcpu with the interactiveX governor but i dont have the phone right in front of me so im not sure..
Click to expand...
Click to collapse
Read the sticky in the Dev section. Links to all the tutorials are there. Read them and see if it's beyond your skill set.
Didnt know that either thanks! Ill definitely keep that in mind for my Sensation shes tends to get a little warm. I have it OC at 1.56 which isnt that high but it still gets warm.
Since I've gotten my Sidekick, I've noticed on most ROMs a horrible tendency to not register key-presses on the physical keyboard. There was one ROM early on that didn't do this (or very little) and one of the versions of RAGE was very good. I'm running GOV3.2 Bulky right now and it's not horrible, but it's noticeable. Does anyone have an idea of what might cause this? Thanks.
ged92781 said:
Since I've gotten my Sidekick, I've noticed on most ROMs a horrible tendency to not register key-presses on the physical keyboard. There was one ROM early on that didn't do this (or very little) and one of the versions of RAGE was very good. I'm running GOV3.2 Bulky right now and it's not horrible, but it's noticeable. Does anyone have an idea of what might cause this? Thanks.
Click to expand...
Click to collapse
I thought my keyboard was going bad or i just did not press the key all the way, now im on stock and i have not had that issue, hope someone finds the rom
ultraprimeomega said:
I thought my keyboard was going bad or i just did not press the key all the way, now im on stock and i have not had that issue, hope someone finds the rom
Click to expand...
Click to collapse
I wonder what the issue is that's causing it to show up on custom ROMs. Though, I've had it on the stock ROMs as well.
Have you tried this version of the kernel? Along with the removal of the keystroke logger, it also contains a patch that allows you to lower the keystroke timer delays... If you are experiencing dropped keystrokes, this could help, as the patch was designed for tht very issue.
http://forum.xda-developers.com/showthread.php?t=1663622
yogi2010 said:
Have you tried this version of the kernel? Along with the removal of the keystroke logger, it also contains a patch that allows you to lower the keystroke timer delays... If you are experiencing dropped keystrokes, this could help, as the patch was designed for tht very issue.
http://forum.xda-developers.com/showthread.php?t=1663622
Click to expand...
Click to collapse
Thank you!!!!!!!! I went ahead and dug into that thread. I do have that kernel already on my phone. I looked at the thread linked in that thread that gives a patch to adjust the timer delay and column delay in the kernel. HOWEVER, I'm not knowledgeable enough to apply that patch to my phone as it's given. Elsewhere in that thread, someone gave the commands to edit the settings manually through a terminal which I did through Android Commander on my PC and it worked wonders! Being the suspicious type, I guessed that the settings might not keep after a reboot. Unfortunately, that is the case and I had to reapply the settings after my phone finished restarting. So, I'll have to play with this a bit more to get it to keep, but thank you for showing me this!
You're welcome! That patch was made just for this issue. And yeah, it doesn't stick after a reboot, so we could either compile the kernel with chosen settings added in, or make a simple init.d script. I never did either one lol, was too lazy to try editing and building the kernel from source, and was on the stock ROM so I thought maybe it had no init.d support. You could probably create a file with those same commands used in Terminal, and throw it in your init.d folder to change the settings at boot.
yogi2010 said:
You're welcome! That patch was made just for this issue. And yeah, it doesn't stick after a reboot, so we could either compile the kernel with chosen settings added in, or make a simple init.d script. I never did either one lol, was too lazy to try editing and building the kernel from source, and was on the stock ROM so I thought maybe it had no init.d support. You could probably create a file with those same commands used in Terminal, and throw it in your init.d folder to change the settings at boot.
Click to expand...
Click to collapse
I set my column delay to 30 and my timer delay to 1 and it now feels like I'm typing on a Sidekick again! I wouldn't know how to correctly compile the kernel myself with these settings changed. So, are there any devs out there willing to make a zip that can be flashed in CWM so these settings will become permanent?
ged92781 said:
I set my column delay to 30 and my timer delay to 1 and it now feels like I'm typing on a Sidekick again! I wouldn't know how to correctly compile the kernel myself with these settings changed. So, are there any devs out there willing to make a zip that can be flashed in CWM so these settings will become permanent?
Click to expand...
Click to collapse
+1
I've noticed this problem and thought it was just me :$
I've had this happen as well as my screen thinking I was pressing it in one location when I wasn't even touching the phone. :s Had me at my wits end.
Sent from my SGH-T839 using xda premium
To those interested in the commands I used to fix the keyboard, see below. If you reboot your phone, these settings will go away and you will need to input these commands again. For a permanent fix, someone will need to add them to a kernel that can be flashed. To use these commands, your phone must be rooted. I've successfully used Android Commander to enter these commands from my PC while my phone is connected via USB.
The current timer delay may be read with:
cat /sys/devices/platform/s3c-keypad/timer_delay
The default is 5 if I remember correctly.
A new timer delay may be set with:
echo 1 > /sys/devices/platform/s3c-keypad/timer_delay
The default 300 µs column delay value may be read with:
cat /sys/devices/platform/s3c-keypad/column_delay
A new delay may be set with:
echo 30 > /sys/devices/platform/s3c-keypad/column_delay
In either command, you may experiment with different values by changing the 1 or the 30 in either command to what you want. I believe the lowest is 1 and the max is 256 for the timer delay. If you damage your phone running these commands, that's on you. I'm just telling you what I did and feel worked for me. YMMV. Also, if you don't want to connect your rooted phone to your PC and want to use Terminal Emulator from the Play store, that will work too. You need to enter 'su' prior to running the above commands and grant the terminal super user permissions for the commands to take.
ged92781 said:
I set my column delay to 30 and my timer delay to 1 and it now feels like I'm typing on a Sidekick again! I wouldn't know how to correctly compile the kernel myself with these settings changed. So, are there any devs out there willing to make a zip that can be flashed in CWM so these settings will become permanent?
Click to expand...
Click to collapse
I'll work on it for the next releases of the Bi-Winning roms and also try to attach flashable zips.
RicAndroid said:
I'll work on it for the next releases of the Bi-Winning roms and also try to attach flashable zips.
Click to expand...
Click to collapse
Thank you!
ged92781 said:
Thank you!
Click to expand...
Click to collapse
You are very welcome! All done, BTW. Posting my updates now.
Permanent Fix(Manual way)
Taking the timer_delay and column_delay tricks shown above...I was able to make an init.d script(pretty easy, tbh) but don't feel it merits an update.zip since it's so easy. What I did was:
1. go to /etc/init.d
2. find the last script(In GOV3.3 it's 18complete) and rename it - adding one to the sequence(In my case I renamed it to 19complete)
3. make a new file name 18keyboardfix(The number depends on your rom, really...like if you renamed the above file to some thing like 33complete, you'd call this 32keyboardfix. Easy? right?)
4. Open the file you just created and put:
Code:
!#/system/bin/sh
echo 1 > /sys/devices/platform/s3c-keypad/timer_delay
echo 30 > /sys/devices/platform/s3c-keypad/column_delay
5. Set the permissions to rwxr-xr-x or whatever the numeric equivalent is. (0755, iirc)
6. Reboot
7. (Optional) Recheck the values with the following commands:
Code:
cat /sys/devices/platform/s3c-keypad/timer_delay
Code:
cat /sys/devices/platform/s3c-keypad/column_delay
I take no credit for this fix. Really, it was all ged92781 for providing the commands. All I did was find a way to make it permanent(Well, it's just reset when the devices is turned off and the init.d scripts set it back to you desired values, but that's debatable on whether it's permanent or not...either way...it works and is a simple fix)
SammaelAkuma said:
Taking the timer_delay and column_delay tricks shown above...I was able to make an init.d script(pretty easy, tbh) but don't feel it merits an update.zip since it's so easy. What I did was:
1. go to /etc/init.d
2. find the last script(In GOV3.3 it's 18complete) and rename it - adding one to the sequence(In my case I renamed it to 19complete)
3. make a new file name 18keyboardfix(The number depends on your rom, really...like if you renamed the above file to some thing like 33complete, you'd call this 32keyboardfix. Easy? right?)
4. Open the file you just created and put:
Code:
!#/system/bin/sh
echo 1 > /sys/devices/platform/s3c-keypad/timer_delay
echo 30 > /sys/devices/platform/s3c-keypad/column_delay
5. Set the permissions to rwxr-xr-x or whatever the numeric equivalent is. (0755, iirc)
6. Reboot
7. (Optional) Recheck the values with the following commands:
Code:
cat /sys/devices/platform/s3c-keypad/timer_delay
Code:
cat /sys/devices/platform/s3c-keypad/column_delay
I take no credit for this fix. Really, it was all ged92781 for providing the commands. All I did was find a way to make it permanent(Well, it's just reset when the devices is turned off and the init.d scripts set it back to you desired values, but that's debatable on whether it's permanent or not...either way...it works and is a simple fix)
Click to expand...
Click to collapse
Uh, oh....I used echo "number" /proc/sys/devices/platform/s3c-keypad in my script. Will I have to change it?
RicAndroid said:
Uh, oh....I used echo "number" /proc/sys/devices/platform/s3c-keypad in my script. Will I have to change it?
Click to expand...
Click to collapse
Idk, honestly. Try and see if your script works first, if not, then use the one I made using the commands ged92781 provided. Now...to find a way to fix the spaztic touch screen...that'll be tricky.
SammaelAkuma said:
Idk, honestly. Try and see if your script works first, if not, then use the one I made using the commands ged92781 provided. Now...to find a way to fix the spaztic touch screen...that'll be tricky.
Click to expand...
Click to collapse
I'm using your commands, dude. I'm very into details....so thanks!
RicAndroid said:
I'm using your commands, dude. I'm very into details....so thanks!
Click to expand...
Click to collapse
Lol. No problem. And good luck with the custom rom cooking.
As there are again and again discussions concerning the minfree settings in CM12 roms, I decided to open this thread. If a moderator thinks, this is the wrong place for this thread, just move it, to where it belongs.
Obviously, since the last builds of CM12, the settings for minfrees cause some trouble. After a clean install of any rom, the minfree settings in trickstermod and in fauxclock are completely empty. In fauxclock the settings for OOM (out of memory) Score as well. Some people entered them manually, but I'm afraid, this won't help.
To really solve this, you have to do the following steps: open your file explorer, go to sys/module/lowmemorykiller/parameters. There you will find 5 files. Two of them do not have correct permissions. The first one, called adj, is for the OOM Scores. The other one, called minfree, is, you won't guess it, for the minfrees. :fingers-crossed:
As you see, both of them have only write permissions, but no read permissions. So I guess, the system will ignore these settings completely. I checked this, using cool tool from play store, very nice tool to show for example the actual free ram in your status bar. And in deed, the ram went down to 25MB, after I had opened a handful apps, and then my phone stopped working. I only could do a reboot.
Now the solution, which is quite easy: change the permissions into rw-rw-rw (666), and maybe change the group under owners into root (I'm not sure, if this is necessary, but it does make no problems, so why not).
Et voilà - if you now open trickstermod or fauxclock again, you will see the preset parameters. As you can see also, the minfrees there are really high. In another thread, there have been suggested the following settings, which are a good standard:
trickstermod 48/60/72/84/96/120
fauxclock 12288/15360/18432/21504/24576/30720
Important: In fauxclock, the minfree settings are not made in MB. You have to enter the so called "pages" for minfrees, which I can't explain exactly, what this is. In general, if you want to change minfrees in fauxclock, just take the settings in MB, you want to, and multiply by 256. This will give you the correct values.
BTW I don't think, it's a good idea, to change the OOM Scores, as long as you do not know exactly, what you're doing.
So, hopefully I could help a bit and clear some things up. But the final question to the CM devs remains:
is this a bug or is this a feature?
With me, those files were already chmod 666, owner root. I use latest liquidsmooth rom. What i did, prior reading your post, was that i set minfree in trickster, from my presets, than immedatly switched to faux, parameters were there, pressed apply, switched set on boot and rebooted. After that minfree r sticking in faux and trickster. Guess that my actions leaded to what you have described. Anyway, your way is much more convinient - at least one app less to use
I don't get it... The directory you mentioned is empty on my one s as well as on my nexus 10 both with cm12.
However my settings stick since I use fauxclock.
One more thing I don't get is in fauxclock. It says "kilobyte" explicitly in the minfree settings although you said (and it stems to be) this strange pages value....
mariachi62 said:
I don't get it... The directory you mentioned is empty on my one s as well as on my nexus 10 both with cm12.
However my settings stick since I use fauxclock.
One more thing I don't get is in fauxclock. It says "kilobyte" explicitly in the minfree settings although you said (and it stems to be) this strange pages value....
Click to expand...
Click to collapse
You have to use your file manager with root permissions. Depending on which file manager you use, this can be done differently. The inbuilt CM12 file manager can be given root permissions in settings, in Root explorer for example you have to mount the directory as r/w.
An yes, you are right, fauxclock says, the settings are in kilobyte, but this is not correct. If you succeed to open the minfree file with your file manager, you will find there exactly the values, you have entered in fauxclock.
Damnit, you're right. Solid explorer doesn't show the content of the directory.... I use it a long time and always had the feeling solid explorer shows me all files...
Cm file manager works, thanks!
mariachi62 said:
Damnit, you're right. Solid explorer doesn't show the content of the directory.... I use it a long time and always had the feeling solid explorer shows me all files...
Cm file manager works, thanks!
Click to expand...
Click to collapse
It does work with solid explorer as well. The point is, there is no option, to set root permissions manually in solid explorer. So the trick is to create a situation, where solid explorer will ask for root access. For example: long press any folder in your system root, tap properties, tap change (attributes) and now press OK, without changing anything. You will be asked for root access.
Now everything should be fine!
got a problem.
parameter file is empty.
using unofficial cm12 on htc one s with icecode kernel
waver1967 said:
got a problem.
parameter file is empty.
using unofficial cm12 on htc one s with icecode kernel
Click to expand...
Click to collapse
problem solved
For solid explorer, just try to open /data and it will ask for root permissions. I do it every time I flash my phone.
Thanks a lot man! I wasn't aware of the skewed minfree files. Was setting them in Trickster and wondering why the apps keep shutting down on me when multitasking. Great work
oll0 said:
Thanks a lot man! I wasn't aware of the skewed minfree files. Was setting them in Trickster and wondering why the apps keep shutting down on me when multitasking. Great work
Click to expand...
Click to collapse
They will still close even so...just not so obvious
Rapier said:
They will still close even so...just not so obvious
Click to expand...
Click to collapse
Uh yes obviously. However they were actually closing the instant i opened another app. Couldnt even keep two apps open at the same time, that was pretty bad.
oll0 said:
Uh yes obviously. However they were actually closing the instant i opened another app. Couldnt even keep two apps open at the same time, that was pretty bad.
Click to expand...
Click to collapse
Yes, I know what you mean. Was the same for me. Having better minfree settings that stick after a reboot helped but didn't solved the issue completely. But at least now phone is usable. I put my hopes in that Google patch they'll release with 5.0.3
Sent from nowhere over the air...
deleted
Thanks for this thread, I changed the permission with "chmod 666" using adb shell, but after a reboot, the files were back to write-only mode, is it normal ? How do you make it permanent ?
Sylvain_44 said:
Thanks for this thread, I changed the permission with "chmod 666" using adb shell, but after a reboot, the files were back to write-only mode, is it normal ? How do you make it permanent ?
Click to expand...
Click to collapse
If it's reverting, I guess the only way would be through an script that runs at boot time. But it's strange, the permissions should stick once set...
Sylvain_44 said:
Thanks for this thread, I changed the permission with "chmod 666" using adb shell, but after a reboot, the files were back to write-only mode, is it normal ? How do you make it permanent ?
Click to expand...
Click to collapse
I used a file explorer with root permissions like root explorer or ES file explorer. My permissions are actually rw-rw-rw, both for adj and minfree file. I guess, this is 666? And they stick after a reboot. But honestly I am not quite sure, if I changed something else. IIRC, I might have changed the permissions for system/etc/init.d/90userinit to rwxr-xr-x. Maybe you want to check this, too.
Well, they don't stick because init.rc sets them to chmod 0220 on boot. That makes me wonder if maybe it was supposed to be like this? I wanted to change it but I don't want to screw anything up. There is a dedicated section for low memory killer in init.rc and only things there are chmod 0220 for those two files and chown for them - so basically the things that we are fixing in this thread. A bug or a feature?
jakubmi9 said:
Well, they don't stick because init.rc sets them to chmod 0220 on boot. That makes me wonder if maybe it was supposed to be like this? I wanted to change it but I don't want to screw anything up. There is a dedicated section for low memory killer in init.rc and only things there are chmod 0220 for those two files and chown for them - so basically the things that we are fixing in this thread. A bug or a feature?
Click to expand...
Click to collapse
Thanks for this hint! Indeed, this might be the other thing, that I had changed. In CM11 roms, the described permissions in init.rc are 664 - both for adj and minfree file. I am not quite sure, if this helps, but it's worth an attempt. You can change the permissions in init.rc to 644, reboot and see, if the permissions for adj and minfree are sticky now. I just did this ,and everything is fine -so you can try without risk, I guess. But I must say, I hadn't the problem before, that the permissions for adj and minfree were reset after reboot. Could be related to the changes in init.rc, but I am not sure.
A weird thing: I made a backup and tried anyway yesterday but after a reboot my init.rc restores itself to normal. I tried another time: Modified the values and saved. After reopening it's still there and it stays there but only until I reboot the phone. After reboot the permissions are not set correctly and init.rc restores itself to original state. Is there something I do not know about modifying init.rc? Because that is the first time I try to do something with it.