Related
If you haven't tried this app already, definitely give it a shot. So many features. It basically incorporates Titanium, Root Explorer, Voltage Control, SetCPU, SD Card Boost, ROM Manager, TMobile ThemeChooser (for CM7), Terminal Emulator, Ad Blocker, Rebooter, V6 Supercharger, Autokiller, Font Installer, Custom Boot Animations, Battery Icon Changer, Boot Logo Changer, and probably several other common Root apps all-in-one. You can mess with Build.prop tweaks, vm heapsize, sysctl tweaks, and more. AND it lets you Apply any changes you make on Boot.
And the best part.....ALL FREE!!!! (though there is a donate version, not sure what the extra features are - but all I mentioned above is in free version)
Let me know what you think:
ROM Toolbox Market Link
Check out Imoseyon's recommended settings/tweaks as well here.
great app
Thanks for the tip...I just got it and MAN is it amazing! I'll play around with it some more, but if it holds up...I'll buy the donate version. Really good app!
Just found this today as well. Super useful.
FrankyFiggz27 said:
If you haven't tried this app already, definitely give it a shot. So many features. It basically incorporates Titanium, Root Explorer, Voltage Control, SetCPU, SD Card Boost, ROM Manager, TMobile ThemeChooser (for CM7), Terminal Emulator, Ad Blocker, Rebooter, V6 Supercharger, Autokiller, Font Installer, Custom Boot Animations, Battery Icon Changer, Boot Logo Changer, and probably several other common Root apps all-in-one. You can mess with Build.prop tweaks, vm heapsize, sysctl tweaks, and more. AND it lets you Apply any changes you make on Boot.
And the best part.....ALL FREE!!!! (though there is a donate version, not sure what the extra features are - but all I mentioned above is in free version)
Let me know what you think:
http://bit.ly/rhxwX5
Click to expand...
Click to collapse
Thanks for the tip! I like the app, with no reliable data connection I'm out of the loop on most things great to have them here when I do get data!
Sent from my Samsung Legen-wait for it-dary! 4g
It will not change your boot animation if your on ei22
Sent from my SPH-D700 using Tapatalk
I used this app. The paid version provides the ability to set most of those functions to apply at boot
Sent from my SPH-D700 using XDA App
slayer450 said:
It will not change your boot animation if your on ei22
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
It will, but only if you are using a kernel that supports then
Sent from my Samsung Legendary 4G, a Universe UTES phone, running "two.three.five"
nicenice19 said:
I used this app. The paid version provides the ability to set most of those functions to apply at boot
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
what other things can you set at boot in the paid version that you can't in the free version? cuz u can set governor, sd card read speed, and other things at boot for free..
possibly a result of some tweaks i just made using Rom Toolbox, I'm flying right now. Faster than ever. Here's what I changed, just in case anyone can point out if I did anything bad:
Auto memory manager
6,8,24,30,40,50 (same as Aggressive 1 settings in V6 Supercharger)
vm heap size = 32
sd boost = 3072
Min Free KBytes = 4096
Dirty Ratio = 90
Dirty Background Ratio = 70
VFS Cache Pressure = 5
Oom Kill Allocating Task - SET ON
Applied everything at boot, obviously. I did a little research on what to change these values to, and so far these values have definitely sped me up considerably.
__________________
How has battery life been with those settings?
interfreak said:
How has battery life been with those settings?
Click to expand...
Click to collapse
Great so far. The improved performance is even more noticeable, however. only thing you might want to change, if you know what it is, is the oom kill allocating task setting. a lot of people seem to leave it off, but from what i understood it did, keeping it on should save more battery and just operate more efficiently (makes the killing off of tasks to regain ram less random). so far there's been no downside to having it on. also, you might want to test out putting the vfa cache pressure setting to 1. many people do that, too.
It requires the pro version to freeze apps
hey just want to ask a simple question ....
i am having samsung galaxy s2 and i had update it with 2.3.6 stock rom KK5 and i want to change the battery icon on the taskbar. but as i change it. my phone didn't boot and stuck on sangung galaxy s2 logo. even didn't find the boot animation or sound..
i didn't make any changes except the battery icon.
even my phone is root.
please check it and revert what i have to do to change the battery icon ...
thanx ..
waiting for +ive response
Rg.
Sachin...
sacmat said:
hey just want to ask a simple question ....
i am having samsung galaxy s2 and i had update it with 2.3.6 stock rom KK5 and i want to change the battery icon on the taskbar. but as i change it. my phone didn't boot and stuck on sangung galaxy s2 logo. even didn't find the boot animation or sound..
i didn't make any changes except the battery icon.
even my phone is root.
please check it and revert what i have to do to change the battery icon ...
thanx ..
waiting for +ive response
Rg.
Sachin...
Click to expand...
Click to collapse
I think you're in the wrong forum
Sent from my SPH-D700 using XDA App
IronReaver17 said:
I think you're in the wrong forum
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Well, he did make the change with Rom Toolbox. To the guy with the battery issue, I think you need to be on a deodexed rom to change the battery.
WOW!!! The speed change is amazing!!!! hard to believe that just a few tweaks did that!
Bought the pro version of this. Tried to change battery icon and it froze on boot logo on reboot. Tried to refund and it won't refund. Will be emailing the developer.
Sent from my SPH-D700 using Tapatalk
Zeinzu said:
Bought the pro version of this. Tried to change battery icon and it froze on boot logo on reboot. Tried to refund and it won't refund. Will be emailing the developer.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Man, Android and you sure have a strange releationship...
..... you always get the wierdest issues....
Hope you get a good response from the dev
This Epic post as brought to you via Tapatalk
Yea... don't get me wrong I'm sure all the functions work great, and it's not like I tried anything else with it. Having one freeze was enough for me to stick with the ways of doing things that I know I never have issues with. But knowing me I'll just keep the paid version and try again at some later date. Maybe something just glitched during the reboot.
Sent from my SPH-D700 using Tapatalk
Zeinzu said:
Yea... don't get me wrong I'm sure all the functions work great, and it's not like I tried anything else with it. Having one freeze was enough for me to stick with the ways of doing things that I know I never have issues with. But knowing me I'll just keep the paid version and try again at some later date. Maybe something just glitched during the reboot.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Not sure if this will help, but I have the pro version as well and was able to successfully change the battery icon. I liked having the number off to the side so since I have the ICS theme on my phone, I used that battery icon. I think it's 'Bar Ice Cream Sandwich'.
Hello,
I'm reactivating this thread since I cannot talk with samm every now and then to update the OP from this thread here.
What works:
It is stable for a daily driver but there are definitely things that doesn't work. For starters, the Hero is too small for ICS since we don't have any GPU posibility. Adreno 130 drivers are oh, too small and too bad for animations on ICS, they suck even in GB and Froyo. Still, the statusbar and fling are much smoother than other android releases because that's how ICS is built. It is more RAM friendly and it looks, well, sexy!
Will try and update this rom when it will be possible. We might jump on the bandwagon of 4.0.4 if I can make it to move faster than it moves right now (yes, I have an experimental build).
If one of you want to join me to develop this rom further, send a PM and I will send you some details about what is in the works, how far it is. I know there are few people that can work on builds here on Hero thread but if we work together, we can pull this out one more time.
FLASH THIS AT YOUR OWN RISK. I AM NOT RESPONSIBLE FOR:
- YOUR BRAIN
- YOUR HOUSE
- YOUR PHONE!
ON with the ROM. What has been changed:
Added:
Code:
- Google Music apk (yes, official google music app);
- Explorer.apk
- Latest and greatest LV Kernel 1.2+
- Revert to Evtoolbox back from 4.0.3 builds
- Set the cpu to scale at 352-672 from startup
- Tweaked the build.prop a little (added some experimental lines)
Why this is v3?
Because the memory management inside the kernel (remember, INSIDE THE KERNEL) is tweaked and fixed to nice values in order to allow our hero to better multitasking (you can find these values in my other rom called 1ceCream BEAST Flavor). No need for tweaks in init.d to do the job, no bull****.
Just plain and simple!
If you are texting someone, sending an email, playing a game, doing something, and you are locking the screen, after unlocking you will find that the application is ON the screen, and is not closed how it is in many other roms for hero. The multitasking with my values is so much better, you will definitely like it!
Click to expand...
Click to collapse
The rom moves fast, even if it is ICS, I have the animations on and no force GPU in Developer settings and it is still moving so much fast than the older builds.
Overall, I am happy with this release and I hope you will be too! Post me some of your opinion and tell me if it is fast or am I dreaming!
Some user's feedback:
Loxxy said:
wow 'HeroICS v3' is running on rocket power !!! what the hell
amazing job
Click to expand...
Click to collapse
Carrier Internet connection issue:
- Create Manual APN for provider's internet connection.
DOWNLOAD HeroICS v3
If you make these changes maybe you'll see better performance, the hero can't handle dithering on anything higher than stock GB or Sense froyo and doesn't have enough RAM for 48mb of dalvik heapsize. I may be wrong but these always worked for me in the past altough ICS is supposed to be better on RAM.
dalvik.vm.execution-mode=int:fast
dalvik.vm.heapsize changed to 24m or 32mb
persist.sys.use_dithering=0
Good work. Flashing now.
How about keeping this as lite as possible, only the absolute essentials pre-installed, everything else as optional zips / apk. For instance, I personally have no use for the music player.
I would really like to see a bare bones, fast and stable ics rom where you just add what you need.
---------- Post added at 03:56 AM ---------- Previous post was at 03:16 AM ----------
Unexpected reboot just as I was about to install Opera Mini. Followed by: "New Sim Detected, reboot required." Never seen that before.
I've applied CSL00's values.
Wonder if V6 Supercharger or Auto Memory Manager can improve things.
Play Store is noticeably faster. Unsure if was CSL00's values or the introduction of AMM.
Regarding the error message: 'No more room on this home screen.'
In Play Store app. Menu > Settings > Deselect Auto-add widgets.
Second unexpected reboot, otherwise things are getting faster. No wifi issues, BT still won't pair.
Running AMM on 'Aggressive.'
CSL00 said:
If you make these changes maybe you'll see better performance, the hero can't handle dithering on anything higher than stock GB or Sense froyo and doesn't have enough RAM for 48mb of dalvik heapsize. I may be wrong but these always worked for me in the past altough ICS is supposed to be better on RAM.
dalvik.vm.execution-mode=int:fast
dalvik.vm.heapsize changed to 24m or 32mb
persist.sys.use_dithering=0
Click to expand...
Click to collapse
dalvik execution mode was on fast until I changed it in the last second to "jit".
vm.heapsize was changed to 48 because I was testing 32 mb and I saw that it takes a little while to enter in one application. With 48 mb the time is reduced somehow. Please feel free to change it to 32 mb if you want. Dithering, well here is a mistery, I don't know if this works in ICS. It does look a little better than with it changed to 0 and my phone can suport dithering pretty well.
About the reboots, please install set cpu and set your max cpu frequency to a respectable value such as 691 or lower. I suggest using governor smartassV2.
The whole rom does feel a little snappier but we have an issue when someone calls you and after 20 seconds the call gets interrupted. I'll look into that today after work and see if I can fix it somehow.
I've tried Supercharger, the V8 doesn't wanna start on ICS and when applied V6 with option 6, the phone just got stuck on bootloop.
The reason that I've made it like this with apk.s that you can easly uninstall is that I didn't want you guys to have to flash any other optional zips or anything. But as I said, feel free to do what ever you want and uninstall those unused apps.
Oh, If you want to try supercharger yourself, you have to first delete these scripts from /etc/init.d:
03tweaks
04netspeed
05fixsdcardspeed
06loopy_smoothness_tweak
15cleanup_init_ram
16sqlite_optimize
17speedy_modified
Just to avoid any unexpected issues.
L.E:
CAN SOMEONE PLEASE, make a LOGCAT while you are in a call and save it to a txt? I want to see if we can narrow down the problem of disconnecting. I am unable to make a logcat atm.
1ceb0x, back to using your original build.prop, and Setcpu. Things seem more stable.
I'm looking for a notification toggle (cm-style) that has no icon when running (or only hides it, leaves a space.)
I will make a logcat, but I've tried aLogrec and all it seems to produce is an empty file. Should it not be dumping info on any activity I do?
lost101 said:
1ceb0x, back to using your original build.prop, and Setcpu. Things seem more stable.
I'm looking for a notification toggle (cm-style) that has no icon when running (or only hides it, leaves a space.)
I will make a logcat, but I've tried aLogrec and all it seems to produce is an empty file. Should it not be dumping info on any activity I do?
Click to expand...
Click to collapse
Seems stable than samm000's build.prop?
Glad to hear this.
As for the logcat, you cannot use any of the readers on the market because they will not work on ics. I've tried to make a log using android sdk but it seems that we need a file called 'main' in /dev/logs. I tried to make the file manually but then I've encountered an EOF read error on cmd. I forgot to make permissions for the respective file. Will make it again now and see how it goes.
As for cm notification toggle, I don't know what are you talking about. The notification toggle on ICS is nicer than any other available .
Tell me if you have calls issue (your call is disconnected after some seconds)?
Well it is probably more stable because I reduced the cpu speed.
In a voicecall now, 2mins+. Call lost around 3 mins.
6mins+ this time and still going...
lost101 said:
Well it is probably more stable because I reduced the cpu speed.
In a voicecall now, 2mins+. Call lost around 3 mins.
Click to expand...
Click to collapse
Did you checked the box "Force GPU rendering" in Develop Options?
Is it stable because I've added graphical tweaks and some tweaks to speed...
Yeah, 'Force GPU rendering' is enabled. In a voicecall now, 10mins+.
I ended the call myself at 22mins.
lost101 said:
Yeah, 'Force GPU rendering' is enabled. In a voicecall now, 10mins+
Click to expand...
Click to collapse
10 minutes without disconnecting? What's your settings on network? GSM ONLY, or WCDMA preferred?
(to see this, please go to dialer and dial *#*#4636#*#* , then go to Phone information, scroll down and you will see the value above the button "Turn Off Radio").
as default the version is WCDMA preferred. What Radio firmware are you using?
also, did you installed Habarug's tweak to hide the end button call during a call? (it's in samm000's thread).
this information will be helpful! cheers
WCDMA preferred. Radio: 63.18.55.06PU_6.35.15.11
I have not installed Habarug's tweak.
lost101 said:
WCDMA preferred. Radio: 63.18.55.06PU_6.35.15.11
I have not installed Habarug's tweak.
Click to expand...
Click to collapse
and you had 10 minutes without disconnecting? you were able to end the call normally?
1ceb0x said:
and you had 10 minutes without disconnecting? you were able to end the call normally?
Click to expand...
Click to collapse
It was 22mins when I ended the call myself.
Regarding notification toogle this is what I mean: 15 toggle status bar as implemented in this rom. Check the video.
Very ODD.
I have 63.18.55.06OU_6.35.15.01 on my device with WCDMA preferred but I keep getting call disconnected after 10 seconds or so.... regarding the notification status bar power widget, I don't know what to say. I'm not a dev so...
i'm trying to find a way to make a log cat of the calling issue because I don't really want to change my radio because my version seems to be battery friendly...
thank you for your support
Obviously the notification thing isn't even important right now. I shouldn't really have mentioned it.
I thought this radio was considered one of the best to be using, and find the battery life to be good on it.
Don't know if its the best really. But I've flashed it anyway. Since this will end my calling interrupt, it will be a small price to pay if the battery doesn't play well.
Will test the voice calling. Btw, I am maybe working on RC2, with some new tweaks and fixed latinime.apk keyboard..
can confirm right now that the latinime.apk is fixed.
@Habarug: are you using my mod or sam's rom?
Thanks lost, will try your radio, im on .14 atom
Just to clarify, the radio I am using still has calls dropping with ics. It seems to happen at random times. 1 minute into a call, 3 minutes or not at all. Maybe it's because of the numbers I am ringing. I can't be sure they would not drop anyway. But it sounds like it is doing better than some other radios.
Also, what about having a build based off ics 4.0.4?
lost101 said:
Just to clarify, the radio I am using still has calls dropping with ics. It seems to happen at random times. 1 minute into a call, 3 minutes or not at all. Maybe it's because of the numbers I am ringing. I can't be sure they would not drop anyway. But it sounds like it is doing better than some other radios.
Also, what about having a build based off ics 4.0.4?
Click to expand...
Click to collapse
we have to fix this issues first and then talk about another version. anyhow, 4.0.4 is much laggier than this version. i saw a bit of logcat and some awkwardly errors regarding the "animations" but i was unable to save the log for future use.
I've asked Maclaw, a dev from Galaxy Gio/Fit/Mini who made CM9 possible on those device to look at our build and maybe with some luck he can see something that make this calls drop...
managed to past 3 minutes in call with your radio version lost101. cheers
L.E: I am unable to send PM's. so i cannot ask Maclaw for help.. too bad! I'll just have to post on their op!
Come on people.. test the build!
Please read the entire OP
DISCLAIMER:
I am NOT responsible for anything YOU do that causes damage to your device. Follow the instructions to TEE and there won't be any problems.
Your ROM/kernel MUST support init.d scripts
How do you know if your kernel supports init.d scripts? There are a number of ways to check, but the best way is to ask the developer of that kernel. You can also check in the ROMofCHOICE.zip by navigating to /system/etc/init.d. If the original .zip of your ROM has an init.d folder with scripts in it, then you are good to go.
What is Lightning Zap!?
Lightning Zap! is a set of tweaks that I have written and compiled to make the LG Nitro Lightning fast, super smooth, and contain excellent battery life!
I have used these same tweaks on devices like the Samsung SGS4G, Samsung Captivate, Samsung Skyrocket, Samsung Blaze, Sony S Tab. I have also assisted others with adding Lightning Zap! to their devices such as the Nexus S and various HTC devices. They have been proven time and time again to add amazing improvements to all devices.
What's the difference in the various version I find of Lightning Zap! when I google it?
Simply put, all devices are setup, formatted and created differently.
What's included in Lightning Zap!:
Battery tweaks for awesome battery life
Governor tweaks for amazing speed and performance without sacrificing battery life
Kernel tweaks
Memory and Ram tweaks
Cleaner tweaks
Build.prop tweaks
Internet speed tweaks
and MORE!
I used ParanoidAndroid ROM to test these tweaks. Although I have used the tweaks from froyo to jellybean, the the mounts, on some devices, are sometimes different as well as some kernel differences on each android version. If you are using a different ROM, feel free to test and post your results in this thread.
Install instructions:
Make a backup and then backup your data with titanium or something alike
***Download link is at the bottom of this post***
Download Lightning Zap! v1.zip to pc (Can be downloaded to sdcard also)
Place Lightning Zap! v1.zip on sdcard
Flash
Allow phone to set for 10 minutes after reboot
Enjoy
Confirmed ROMs & kernels
This space is going to be used to track the ROMs and kernels people have tested and confirmed Lightning Zap! installs and functions correctly.
Gningerbread:
ICS:
Jellybean:
ParanoidAndroid
CM10
Miui 2.9.27
CodeNameAndroid
I'm also adding some helpful tips on how to test Lightning Zap! to get the most positive results.
Testing option 1:
After flashing Lightning Zap!, download SManager from the market, navigate to /system/etc/init.d
Press menu key/more/advanced options/mount /system as rw and click ok
Press on each script individually then a ui will come up
In the ui, tap the icon at the top that is a skull and cross bones (has SU under it) then tap run.
An output will be displayed. Note the output for errors and report errors to me. Please use pastebin.com to upload your outputs
Testing option 2:
Plug phone into pc, open a terminal/command prompt and type each command individually
adb shell
su
cd /system.etc.init.d
Now type the file name of each tweak individually, eg:
01governor
Now note each output that is displayed and look for errors
If errors exist, report errors to me. Please use pastebin.com.
There may be some errors that exist that are not true errors. I know what they are, but haven't noted them yet.
If you have failures, please get them to me as soon as you can so I can fix it
FYI, since I installed Lightning Zap! on my wife's Nitro, she is at 100% with light use at 4.5 hours... I know it is not a normal day for her as she uses her phone much more than what she is using it today, but this is just to give users an idea of how great my scripts are. Typically on my S2 Skyrocket I get about 30 hours under moderate use (many texts from my wife, 5-10 calls, 30-45 minutes of web browsing, etc.) on a single charge...
More improvements and tweaks
The governor tweak is set pretty high for performance. If you find yourself needing battery life over performance, you can make some minor changes. Here's how:
1 Download Script Manager from the market (it's free)
2 Open Script Manager and navigate to /system/etc/init.d
3 Press menu/more/advanced options and select mount as RW
4 Select 01governor and select "edit" at the top (this will open the file in atext editor)
5 Change:
Code:
echo "45" > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold;
To:
Code:
echo "[COLOR=red]70[/COLOR]" > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold;
6 Select menu/save
7 Press the skull and cross bones icon at the top (this will allow Super User)
8 Press run, close app and enjoy
This will result is slightly slower performance but higher battery life.
If you want even better battery life:
1 Following steps 1-4
2 Add a # at the begining of lines 11 to 19
3 Scroll to "pwoersaver" section
4 Remove the # at the begining of lines 28, 30-38 and 43
Code:
#AWAKE_GOVERNOR="ondemand"
#SLEEP_GOVERNOR="ondemand"
# echo "70" > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold;
etc
Code:
AWAKE_GOVERNOR="powersaver"
#SLEEP_GOVERNOR="powersaver"
echo "20000" > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_rate;
5 Follow steps 6-8 (no need to select super user icon if you already did)
This will result in lower performance, but ultimate battery life
When running in a higher performance mode (especially for gaming) you can disable powersave_bias by changing the 1 to a 0 like this:
Code:
echo "1" > /sys/devices/system/cpu/cpufreq/ondemand/powersave_bias;
echo "[COLOR=red]0[/COLOR]" > /sys/devices/system/cpu/cpufreq/ondemand/powersave_bias;
Powersave_bias only allows the CPU to peak for small increments at a time, and not allow the CPU to remain peaked even when the system calls for it. In gaming, that could result in choppy, laggy perofrmance and slow FPS..
Although it says not to in the script, you can change the sampling rate as well. Do not go below 50000. I left it at 57500 as I found this seems good setting for smooth scrolling and performance.
Code:
echo "[COLOR=Red]57500[/COLOR]" > /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate;
Always leave SLEEP_GOVERNOR="powersave" uncommented (no #) and do not uncomment any other SLEEP_GOVERNOR as this will keep ultimate battery save while screen is off.
Only change values in increments of 5 for the up_threshold.
I am not resposible if you do something wrong. Make a back up just in case.
Working on CM10 latest nightly. Noticing a slight speed up. Will keep an eye on battery and post back if I notice any notable changes. Thank you!!
Sent from my LG-P930 using XDA Premium HD app
Can i use it with official miui?
Jl6owa said:
Can i use it with official miui?
Click to expand...
Click to collapse
You should be able to, but like i said in the op, i need you guys to help me test. At worst, you will have to reflash your Rom and gapps... make sure you backup your data too...
Please report back with your results...
When i get home, i will post some testing tips for you guys also...
Sent from my SGH-I727 using xda app-developers app
Thanks for supplying this! I'll have time to make these changes tomorrow and hope to see great improvements.
Sent from my LG-P930 using xda app-developers app
AllstarE4 said:
Thanks for supplying this! I'll ha e time to make these changes tomorrow and hope to see great improvements.
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
Are you building from source? If so, you can add many of the values straight into the kernel. I haven't looked at the Nitro's source, but I can still somewhat guide you on how to make a Lightning Zapped! kernel where the tweaks work MUCH better than going thru scripts...
thomas.raines said:
Are you building from source? If so, you can add many of the values straight into the kernel. I haven't looked at the Nitro's source, but I can still somewhat guide you on how to make a Lightning Zapped! kernel where the tweaks work MUCH better than going thru scripts...
Click to expand...
Click to collapse
Oh heck no. I'm still a noob. I'm pretty good at following instructions though. Lol
Does SQLite Editor work the same? Can I perform all those changes with it or do I need the other app mentioned?
Sent from my LG-P930 using xda app-developers app
Jl6owa said:
Can i use it with official miui?
Click to expand...
Click to collapse
It works fine with miui. Phone become little more faster.
+500 points in antutu
Jl6owa said:
It works fine with miui. Phone become little more faster.
+500 points in antutu
Click to expand...
Click to collapse
Which version of MIUI?
Anyone tried it on Full Throttle 8.4
I'm not proficient enough so I want to hear if other Full Throttle 8.4 finds this working for them.
Jl6owa said:
It works fine with miui. Phone become little more faster.
+500 points in antutu
Click to expand...
Click to collapse
Want to raise your scores even higher, refer to the second post but lower the up_threshold to 15. Of course this will take from your battery life, but it will seriously enhance your performance. You can also change powersave_bias, io_is_busy, down_differential, ignore_nice_load to "0" and play with sampling_rate a bit too... Keep in mind, the more you add performance, the less battery life you will have...
AllstarE4 said:
Oh heck no. I'm still a noob. I'm pretty good at following instructions though. Lol
Does SQLite Editor work the same? Can I perform all those changes with it or do I need the other app mentioned?
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
Any text editor that supports shell scripting will work. As for adding this to a port, then it's as easy as adding files and a few entries in your updater-script...
Tried to install this on Full Throttle. Is it supposed to restart in the middle of flashing?
rsalan said:
Tried to install this on Full Throttle. Is it supposed to restart in the middle of flashing?
Click to expand...
Click to collapse
It does reboot itself as soon as it is done flashing... Since it rebooted, it flashed correctly...
Is full throttle ICS and how is it working for you?
thomas.raines said:
Which version of MIUI?
Click to expand...
Click to collapse
Miui 2.9.27
thomas.raines said:
It does reboot itself as soon as it is done flashing...
Click to expand...
Click to collapse
I get that you want to automate the process a bit, but I think it could be annoying in some cases. What if I wanted to do something else in recovery before rebooting? Just my personal opinion.
drumist said:
I get that you want to automate the process a bit, but I think it could be annoying in some cases. What if I wanted to do something else in recovery before rebooting? Just my personal opinion.
Click to expand...
Click to collapse
From my experience, when flashing tweaks, you want to reboot immediately after so they fully install. Same with ROMs, kernels and recoveries... Otherwise, you can cause gremlins to take over and corrupt your partitions...
thomas.raines said:
From my experience, when flashing tweaks, you want to reboot immediately after so they fully install. Same with ROMs, kernels and recoveries... Otherwise, you can cause gremlins to take over and corrupt your partitions...
Click to expand...
Click to collapse
Not true, but whatever. It's a minor point anyway.
I know, many people here want to have Android 4.x.x on their phones, but unfortunately, because of low-end processor as well as less RAM, these CM10/CM10.1 ROMs are laggy and slow. I am also one of them, but, after using these type of roms since 4 months, I have now got a perfect idea of using them. So, I am sharing the way I use these roms. Many people told that this also helps for CM7 users. So, now I have declared this thread as UNIVERSAL PERFORMANCE THREAD. This method can be used on - Stock | CM7/9/10/10.1.
NOTE : This thread is mainly from galaxy mini forums. But, I have posted it here also, so that Gio users also get its benefits.
NOTE : This method is same for PAC ROMS.. because they are based on CM. So, you can use this on PAC ROMs also.
♦ FINDING STABLE VERSION :
First of all, you will need to find a good stable version of any CM7\CM9\CM10\CM10.1 ROM. Find stable version by asking in general discussion thread of those particular ROM and then download that version. But, do not flash now.. Follow next step.
Note : For CM7 users - Official CM7 is best, but if you want you can try it on custom roms also. If you are using CM7 custom or stock based custom rom, then for scripts n tweaks to work, you must delete all the scripts from init.d so that scripts will not get overridden.
♦ SLIMMING THE ROM :
Slimming means making rom size less by removing unwanted and unnecessary applications from system/app. It reduces system memory use. Here is a chart of cm10.1 apps which are safe to remove - LINK
With reference to that chart you should remove following apps with adding alternatives to them.
Note: Left side apps are to be removed and right side apps are alternatives.
● LatinIME.apk - WP7 Keyboard App
● Browser.apk - Holo Web Browser
● CMFileManager.apk - Root Explorer File Manager
● Trebuchet.apk - Holo Launcher
NOTE: On CM7, default ADW is good, but you can also use Holo Launcher.
Other apps that can be removed without alternatives-
● CalendarProvider.apk - One of the big RAM consuming apps. This app start anytime, you do anything, so it will be a big save of memory removing this app. But, you will get problems with calendar sync..
● GoogleCalendarSyncAdapter.apk - Reomove this only if you do not sync calendar.
● Email.apk - If not in use.
● Gmail.apk - If not in use.
● Talk.apk - If not in use.
● GoogleBackupTransport.apk - It is used in google backups, remove on your own risk. (Not a risk, i always remove it.)
● ChromeBookmarkSyncAdapter - No use.
● HTMLViewer.apk - Never needed.
● UserDictionaryProvider.apk - It is useless without LatinIME.apk.
● VisualizationWallpapers.apk - Wallpapers app. Remove it always.
● CMWallpapers - Remove it always.
● VoiceDialer.apk - Do you really use it?
● LiveWallpapers.apk - Dont you care for your battery?
● QuickSearchBox.apk - If you dont use.
● PicoTTS.apk - Text to speech function.
NOTE: Alternative apps should always be installed in system/app only. For that, I recommend you to remove these apps drectly from rom's zip before flashing.
♦ USE OF SCRIPTS N TWEAKS :
Many people use hard scripts n many tweaks to get good performance. But, it is totally wrong.
Highly recommended to use Activo Speeder. It is the best script for performance. Dont use anyother thing with it- such as ram manager, seeder or anyother script.
(Note: If the above script doesnt work on your device then please find another good script and flash it.)
IT IS RECOMMENDED TO USE SUPERCHARGER ON ICS\JB :
After testing a lot, I found that SuperCharger is the best script which can be used with any ROM to get more performance and for perfect RAM Management. Here are some steps on how to use SuperCharger -
● Here is the original thread for SuperCharger script.
● Script can be downloaded from this download page.
● Download latest script as well as starter package if needed (Read Original Thread).
● Now, for 4.x.x ROMs, you do not need to do anything with services.jar. But, for below 4.x.x, services.jar needs to be patched to get SuperCharger Memory Management working.
● Now, copy script to SDcard and run it with Script Manager as root. For more detailed guide plz prefer the original supercharger thread.
● Now, you are running the script. You will find many options and info on screen. Read it all and choose what you want.
NEW DISCOVERY : SUPERCHARGER + CROSSBREEDER = ULTIMATE PERFORMANCE WITH MAX ENTROPY ! - by Dark Passenger
● LINK FOR THE POST.
Here are some tweaks-
In Build.prop -
●
Code:
ro.ril.disable.power.collapse=0
and change the value from 0 to 1. (Add the line with proper value if does not exist)
This one is for battery saving.
●
Code:
dalvik.vm.heapgrowthlimit=48m
If it already exists then just match the values.
This is a VM Heap management for RAM.
●
Code:
ro.ext4fs = 1
Improves EXT4 performance.
● IMP :
Add following lines below "# Other" in build.prop
Code:
ro.com.google.locationfeatures=0
ro.com.google.networklocation=0
(If exists, just change the values as above).
(Note: This one will remove location feature increasing performance freeing up more RAM. This frees up to 30mb of RAM)
And now remove NetworkLocation.apk from system/app as well as com.android.location.provider.jar from /system/framework.
For further build.prop tweaking, you can use this great guide -> Click Here. Thanks to Dark Passenger for some build.prop tweaks.
This much tweaking and scripting is enough. DONT USE TOO MUCH TWEAKS N SCRIPTS.
♦ BASIC APPS TO USE :
Your rom's performance also depends on the apps which you use. Always look for apps' memory usage and if the app consumes more ram then try to find an alternative app for it. Here are some basic apps which you should use (i always use them).
● Use Root Explorer as file manager, Holo Launcher as Launcher.
● Use Cache Cleaner App. It is must. Clean cache once a day.
● Use Root Cleaner App. A must have app. Do "Quick Cleaning" twice a day. It will regulate your performance.
You can also freeze the apps you are not using at that time, such as DSPManager (Unfreeze it only at the time of listening songs)
Freezing Google Apps will be a great way to reduce RAM consumption.
● Use this amazing app - Autostarts. This app controls the apps that start automatically in your phone. If you want settings which I use then PM me. I will tell you, how to use this app.
CLICK HERE FOR AUTOSTART APP SETTINGS
● ABOUT TASK KILLERS :
Using task killer is good but, it is also bad. Task killing is actually meaningless. Some apps never really get killed. They start again n again. So, use Autostarts instead task killers. But, here is a nice app for killing processes and freeing RAM. This is the original app. I have themed it to look good. Download it here.
Use it as a task killer, press menu button and include system processes and then start killing processes which are useless.
● Try to use apps as system apps.
● If you are using UC Browser then in its settings, check "Clear Data on Exit". If did, you will see UC will take less than 10mb but, if you wont do this, UC will take more than 15mb.
♦ IMPORTANT TIPS AND SETTINGS :
● Always flash rom with a clean wipe and proper flashing method.
● Do not flash gapps again if they are included in the rom.
● Do not flash internal memory scripts as they reduce performance.
● Use Adrenaline Boost. Boost once or twice a day. Boosting much will increase battery consumption.
● Use Root Cleaner app and freeze the apps which you are not using at that time. Freeze Google Play Store, Google Services Framework and other google apps which are always on. Unfreeze them when you want.
● The apps used for Backup purposes should not be installed always. Keep them in your sdcard and install them when you want and uninstall when done with them.
● Basic apps should always be in system/app.
● In Developer Options -
Set all animations scale to .5x
Set Background Process Limit to "Atmost 4 processes", if issues occur then set it back to "Standard Limit".
Enable "Kill App Back Button". Always use this feature to come out of the apps which do not really exit on pressing just back button.
● Do not expect much from our phone as it is not a high-end phone. Dont expect good battery life but, still to gain good battery life. Keep RAM free by using the ProcessKiller app as told above. I always get 170 mb RAM free.
● Do not charge battery until it gets discharged upto 10% or less. While charging do not remove it till it reaches 100% and 20 mins above that.
● Calibrate battery when needed.
● Avoid use of apps which are always running either in background or foreground.
● Press thanks. .
Thanks! I'm definetely going to try this out, even though I'm not running JB but ICS.
Deleting unneeded apps works on every Android version I think, and ActivoSpeeder works on ICS too, so I'm happy!
StiQuezNL said:
Thanks! I'm definetely going to try this out, even though I'm not running JB but ICS. Deleting unneeded apps works on every Android version I think, and ActivoSpeeder works on ICS too, so I'm happy!
Click to expand...
Click to collapse
As I hv mentioned in the title.. this method is for all ROMs.. It is not needed that you should be running JB only.. it is for all...
Noobwithdumbquestions said:
this made everything a lot more laggy and gmail stopped syncing... Also takes about 3 times as long to boot.
No offence, but this is pretty terrible. And after doing some actual research a lot of the "tweaks" you talk about here are never proven effective and frowned upon by actual experts. Even in the article you linked the writer says that something like dalvik heapsize is not something you should or have to change.
I would advice anyone to NOT waste any time on this.
ps: the last part (under tips and settings) is actually some good advice, although the background process limit is not saved in CM10 (and the max.mem tweak doesnt work), so you'll need to do that everytime at startup
Click to expand...
Click to collapse
please dude if you don't know how to tweak you can go i don't use this guide but it's a good one maybe you installed all those thing over a already tweaked rom, this guide if for clean stock, cm7/9/10/10.1
Nice guide...but I think you are wrong about the services.jar. You have to patch it when you use ICS or Jelly Bean, not on GB. And there is no Official CM7 on Gio.
Verstuurd van mijn GT-S5660
Verstuurd van mijn GT-S5660
tcris45 said:
please dude if you don't know how to tweak you can go i don't use this guide but it's a good one maybe you installed all those thing over a already tweaked rom, this guide if for clean stock, cm7/9/10/10.1
Click to expand...
Click to collapse
I applied it on a clean cm10.1 twice, had the same results, twice. I am not trying to talk down on someone elses work, but the fact is that some of the "tweaks" he talks about are never proven and often based on urban myths and the perception of people who applied them and saw improvement (placebo effect). fwiw, OP himself links to an article that busts some of the myths about tweaks, he tells people to apply...
So, maybe my device didnt start to lag more, in fact, it might have been more stable... however, setting the fs.file-max too big (as is one of the many things that activo script does) will make it less responsive, like there is a 100ms sleep between every action... I also experienced that with manual sysctl.
And some other tweaks that do work are still not great for everyone because they got other side effects that are not mentioned anywhere in this article. I got no idea why sync started giving errors and gmail stopped updating (twice) after these tweaks, but they did....
I am completely new to android, and should've done more research before blindly following some article that states to have some magical cure. But I am not new to linux and it seems this community suffers from the same kind of idiosyncrasies at the bottom end, where people constantly try to fix **** that isnt actually broken.
I'm talking about tweaks here obv, removing gapps. bloatware and lowering requirements for the OS is obv fine...
When someone's Gio lags, it's probably because they want to do stuff with it it's not made for, it's a slow device with minimal specs that does the pure core tasks as pda, phone, messenger and email, and as long as you do those it'll be fine. If you want more, buy a better phone. If it's that important to you and you dont have money, learn to appreciate what is actually important in life.
Nuff said.
Noobwithdumbquestions said:
I applied it on a clean cm10.1 twice, had the same results, twice. I am not trying to talk down on someone elses work, but the fact is that some of the "tweaks" he talks about are never proven and often based on urban myths and the perception of people who applied them and saw improvement (placebo effect). fwiw, OP himself links to an article that busts some of the myths about tweaks, he tells people to apply...
So, maybe my device didnt start to lag more, in fact, it might have been more stable... however, setting the fs.file-max too big (as is one of the many things that activo script does) will make it less responsive, like there is a 100ms sleep between every action... I also experienced that with manual sysctl.
And some other tweaks that do work are still not great for everyone because they got other side effects that are not mentioned anywhere in this article. I got no idea why sync started giving errors and gmail stopped updating (twice) after these tweaks, but they did....
I am completely new to android, and should've done more research before blindly following some article that states to have some magical cure. But I am not new to linux and it seems this community suffers from the same kind of idiosyncrasies at the bottom end, where people constantly try to fix **** that isnt actually broken.
I'm talking about tweaks here obv, removing gapps. bloatware and lowering requirements for the OS is obv fine...
When someone's Gio lags, it's probably because they want to do stuff with it it's not made for, it's a slow device with minimal specs that does the pure core tasks as pda, phone, messenger and email, and as long as you do those it'll be fine. If you want more, buy a better phone. If it's that important to you and you dont have money, learn to appreciate what is actually important in life.
Nuff said.
Click to expand...
Click to collapse
Look in signature, this thread is also there for Fit as well as Mini and is getting good response all over.. but you are the first one to complain on this. My advice to you- DO NOT USE THIS DO NOT POST HERE!
Some of your sayings are correct but, still this is the best way to increase performance. You might have did something wrong because this has been researched by me and some other people that this guide is perfect for low activity devices like ace, fit, mini, but if you dont want to use then dont use. I have NO PROBLEM.(I really dont get money or anything for this). lol..
FlemishDroid said:
Nice guide...but I think you are wrong about the services.jar. You have to patch it when you use ICS or Jelly Bean, not on GB. And there is no Official CM7 on Gio.
Verstuurd van mijn GT-S5660
Verstuurd van mijn GT-S5660
Click to expand...
Click to collapse
Yeah services.jar needs to be patched on ics and jellybean only. I didnt knew that official cm7 is not there for gio.. I dont own this device. sorry.
Noobwithdumbquestions said:
I applied it on a clean cm10.1 twice, had the same results, twice. I am not trying to talk down on someone elses work, but the fact is that some of the "tweaks" he talks about are never proven and often based on urban myths and the perception of people who applied them and saw improvement (placebo effect). fwiw, OP himself links to an article that busts some of the myths about tweaks, he tells people to apply...
So, maybe my device didnt start to lag more, in fact, it might have been more stable... however, setting the fs.file-max too big (as is one of the many things that activo script does) will make it less responsive, like there is a 100ms sleep between every action... I also experienced that with manual sysctl.
And some other tweaks that do work are still not great for everyone because they got other side effects that are not mentioned anywhere in this article. I got no idea why sync started giving errors and gmail stopped updating (twice) after these tweaks, but they did....
I am completely new to android, and should've done more research before blindly following some article that states to have some magical cure. But I am not new to linux and it seems this community suffers from the same kind of idiosyncrasies at the bottom end, where people constantly try to fix **** that isnt actually broken.
I'm talking about tweaks here obv, removing gapps. bloatware and lowering requirements for the OS is obv fine...
When someone's Gio lags, it's probably because they want to do stuff with it it's not made for, it's a slow device with minimal specs that does the pure core tasks as pda, phone, messenger and email, and as long as you do those it'll be fine. If you want more, buy a better phone. If it's that important to you and you dont have money, learn to appreciate what is actually important in life.
Nuff said.
Click to expand...
Click to collapse
okay go step by step and tell me what is it that is actually bothering you about the tweaking.(talk only about supercharger method not activ speedo).
yes most of the tweaks are utter bull**** The tweaks in the op(build prop ones are actually proven read the article again).As for dalvik size its recommended to keep a size around 48 so that you processes don't need to split their dalvik heaps into two separate piles thus reducing ram consumption.
Dark Passenger said:
okay go step by step and tell me what is it that is actually bothering you about the tweaking.(talk only about supercharger method not activ speedo).
yes most of the tweaks are utter bull**** The tweaks in the op(build prop ones are actually proven read the article again).As for dalvik size its recommended to keep a size around 48 so that you processes don't need to split their dalvik heaps into two separate piles thus reducing ram consumption.
Click to expand...
Click to collapse
I didnt use the supercharger method... The OP says the activo speedo is recommended, and the supercharger method is proposed as an alternative... I already said what problem I had with it (the response thing, and believe me or not, to me this difference is obvious and makes sense, I was able to reproduce it with just changing some of the same sysctl settings myself) but I wouldnt be surprised if there were more as it seems to do a buttload of things.
As far as the heapsize goes, I am not basing my conclusions on anything other than the OP's own link, which says things like:
dalvik.vm.heapgrowthlimit and dalvik.vm.heapsize - BUSTED,
Click to expand...
Click to collapse
This is one property that has cropped up recently in various build.prop recommendations for ICS. Typical suggested values range from “48m” all the way up to “256m”, likely motivated by the common misconception that more is better. The real purpose of this property is much less obvious than one might initially guess. It is also another one you should probably avoid changing.
Click to expand...
Click to collapse
Should you change this setting? Probably not.
Click to expand...
Click to collapse
Maybe you are right, I dont know all the technical implications, and I got no way to check it other than to test it and I see no difference in ram consumption if I change this property.
The ro.power.dissable thing might shut off wifi when in deep sleep and jumps back to mobile (I think, it happened after applying all tweaks and it seems the most likely thing to do that), but whatever causes that, you should warn people about that sort of thing as it can cost them money..
I didnt use it for long and I'm not an expert, i'm just sharing my findings, people can make up their own mind about it and share their experiences as well..
OJ said:
Look in signature, this thread is also there for Fit as well as Mini and is getting good response all over.. but you are the first one to complain on this. My advice to you- DO NOT USE THIS DO NOT POST HERE!
Some of your sayings are correct but, still this is the best way to increase performance. You might have did something wrong because this has been researched by me and some other people that this guide is perfect for low activity devices like ace, fit, mini, but if you dont want to use then dont use. I have NO PROBLEM.(I really dont get money or anything for this). lol..
Click to expand...
Click to collapse
Sorry, I didnt mean to offend you in any way and appreciate your effort... But telling me to stop posting just because I'm critical seems pretty backwards. If you only want people to say thanks and be greatful all the time, maybe you should start sharing horse pictures on a hello kitty forum...
I'm just sharing my experience and my problems might be related to my rom and it could very well work great on other phones or other roms... But I used a clean cm10.1, the CM10.1 rom almost everyone with a Gio uses, so I'd think it's still important to bring up my findings...
Noobwithdumbquestions said:
I didnt use the supercharger method... The OP says the activo speedo is recommended, and the supercharger method is proposed as an alternative... I already said what problem I had with it (the response thing, and believe me or not, to me this difference is obvious and makes sense, I was able to reproduce it with just changing some of the same sysctl settings myself) but I wouldnt be surprised if there were more as it seems to do a buttload of things.
As far as the heapsize goes, I am not basing my conclusions on anything other than the OP's own link, which says things like:
Maybe you are right, I dont know all the technical implications, and I got no way to check it other than to test it and I see no difference in ram consumption if I change this property.
The ro.power.dissable thing might shut off wifi when in deep sleep and jumps back to mobile (I think, it happened after applying all tweaks and it seems the most likely thing to do that), but whatever causes that, you should warn people about that sort of thing as it can cost them money..
I didnt use it for long and I'm not an expert, i'm just sharing my findings, people can make up their own mind about it and share their experiences as well..
Click to expand...
Click to collapse
the ro.power.disable.ril actually causes the phones radio to go to sleep so if your mobile data is off there is no reason to switch on rather the wifi might switch off(devs already stated so) and again switch back on once you get out of deep sleep.
its a good thing that you are coming back to provide a feedback and is appreciated(at least should be).
the change for dalvik.vm larger than 48 only allows the heap to grow to that value then split into a new heap since we can't/shouldn't/don't use apps with such a large memory footprint the chances of a split occurring post 48mb(gb and below) and 64mb(ics and above) is highly unlikely hence the changing the value to a larger quantity will make no difference.
PS personally even i dont like activo mainly cause i dont know how it works rather i use supercharger and its a much better option in my opinion.
Sorry, I didnt mean to offend you in any way and appreciate your effort... But telling me to stop posting just because I'm critical seems pretty backwards. If you only want people to say thanks and be greatful all the time, maybe you should start sharing horse pictures on a hello kitty forum...
I'm just sharing my experience and my problems might be related to my rom and it could very well work great on other phones or other roms... But I used a clean cm10.1, the CM10.1 rom almost everyone with a Gio uses, so I'd think it's still important to bring up my findings...
Click to expand...
Click to collapse
No, I already told you that many of your ideas are correct but, your way of expressing was not good.
Ex- You said that "Dont waste time on using this guide".
Now, if you think that was correct then please do not post again. If you are providing information then you can but, if you are telling people not to use this then dont post.
In fit's thread, Dark Passenger also wanted to express his ideas and wanted to help me. And I was happy about that. Because the way he helped me was like he really wanted to help. But, you was not polite as him.
You can ask Dark Passenger, there is a lot of information in the thread provided by him and I used that. And he never complained like you.
@Dark Passenger, please explain him.
OJ said:
No, I already told you that many of your ideas are correct but, your way of expressing was not good.
Ex- You said that "Dont waste time on using this guide".
Now, if you think that was correct then please do not post again. If you are providing information then you can but, if you are telling people not to use this then dont post.
Click to expand...
Click to collapse
Yeah, I was frustrated and my first response was not really fair. I agree.
Noobwithdumbquestions said:
Yeah, I was frustrated and my first response was not really fair. I agree.
Click to expand...
Click to collapse
When you use ics or jelly bean you need supercharger script and a patched services.jar (it's easy to do) because any other script don't works 100 % on it.
Sent from my GT-5660 using xda premium
Introduction
If you think there is a drain in Lollipop this is not that fix. This fix the "high cell standby mobile radio active time" bug. You can still test this if you want.
Some people are writing that this patch "only" fix the battery radio active time counter. I say that if you know java and take a look on the code you will note that the side effects of this bug includes, among others, not calling various NetworkManagementEvent observers that will have role in other modules of the inner core of Android, and not only the battery stats. So you say me what are the other side effects fixed.
Other people are saying that this patch doesnt fix the "cell standy radio active time" bug, so take your chances, or wait until Marshmallow :fingers-crossed:.
If after the patch you see a "miscellaneous" item in the battery stats, I am sorry for you but this indicates a bug in your RIL module (or other module) which this patch not solve. The bug in the RIL module was only masked by the Lollipop radio active time bug.
Hi,
I'm working on a fix to the Cell standby / Mobile radio active time issue. The bug manifests as a high mobile radio active time on the Cell Standby in the battery stats.
I think I found the bug in the inner core of Android, and I made some fix to test if it works.
In this thread you will find a Cyanogenmod 12.1 (Android 5.1) build for Odin/Xperia ZL with the fix applied. I already flashed this build onto my odin device and the bug seems to be fixed.
So now I want some of you to test this build and see if the bug is definitely gone.
NOTES
- Your device must have bootloader unlocked.
- CyanogenMod and my work comes with NO WARRANTY as usual. Don't blame me for anything you think I deserve.
- This is my other work on fixing droids: http://forum.xda-developers.com/showthread.php?t=1312398
Patches
I submitted the fix patches to AOSP/Google and CM.
https://android-review.googlesource.com/#/c/168231/
http://review.cyanogenmod.org/#/c/107828/
FAQ
How to install
-Make a backup (using recovery or your preferred tool)
-Download .zip and copy to the phone external sd card
-Boot into recovery (TWRP recommended)
-Install zip cm-12.1-20150827-UNOFFICIAL-odin.zip
-Wipe dalvik/cache
-If you was not on CM12.1 before then Wipe Data
-Reboot
-Wait Android installing apps
How to test
-Enable mobile data (with wifi off)
-Use mobile data (now the bug was triggered)
-Disable mobile data
-Use your device normally and then some hours later look for the mobile radio active time on the battery stats.
-On normal circumstances the display should be the bigger drain. The bug manifests as the Cell Standby being the bigger drain with a high mobile radio active time.
-Please report in this thread if it works or not for you. Thank you!
Can I have a Xposed module of this
- Yes. Thanks to @pyler
http://forum.xda-developers.com/xpo...oactivefix-t3189393/post62570773#post62570773
Download: flashable ZIP
- 2015-08-27 v1 (new)
http://www.mediafire.com/download/2f0igf17ixs52zc/cm-12.1-20150827-UNOFFICIAL-odin.zip
MD5: 3c3641ad6738fad953a90a5d3e745f75
Info about the patches
How to reproduce the bug:
-Enable mobile data (with wifi off)
-Use some mobile data (radio active timer starts in battery stats)
-Disable mobile data (radio active timer keeps running in battery stats)
After some investigation on the issue I found that the BatteryStats
service was not receiving the radio power down notification. The
investigation lead me to the NetworkManagementService.java, where
I found that some code was discarding the radio power change
notifications after the first radio power on.
The problem is that in NetworkManagementServer.java the
notifyInterfaceClassActivity method is discarding the notifications
of radio power change to the BatteryStats (via noteMobileRadioPowerState)
if the fromRadio parameter is false after it's being true some time before.
Even after a detailed analysis, it was unclear what is the real role of
the fromRadio parameter. Changing it to true in the calling methods
solved the issue in the testing unit (Sony Xperia ZL).
Change that introduced the code with the potential to trigger the bug:
-Introduction of "boolean fromRadio" in
NetworkManagementService.java / notifyInterfaceClassActivity()
https://android.googlesource.com/platform/frameworks/base/+/2ffa11e4b71c545e34533ef827bdc1a07fbe8246
Change that triggered the bug:
-Uncommenting the code that calls notifyInterfaceClassActivity
with fromRadio=true
https://android.googlesource.com/platform/frameworks/base/+/2d4b4ed681efcfb64c4d2b4d2a2d236aae1dc7ee
Instructions on how to make an Xposed Module from this patch
XDA member pyler is working on a Xposed module to apply thish patch:
http://forum.xda-developers.com/xpo...oactivefix-t3189393/post62570773#post62570773
---
You can use and Xposed module to apply this fix on-the-fly. If you decide to make an Xposed module from this patch, please credit my work and put a link to this thread.
How to do:
- on package com.android.server class NetworkManagementService (NetworkManagementService.java)
- verify if the method assinature for notifyInterfaceClassActivity method is correct (have the fromRadio parameter)
- intercept the call for the notifyInterfaceClassActivity method
- change the value of the fromRadio parameter to true
- and then call the original method
package com.android.server
class NetworkManagementService
private void notifyInterfaceClassActivity(int type, int powerState, long tsNanos, boolean fromRadio)
For devs
- CyanogenMod: you can repopick the patch 107828 before building.
- Other ROMS: apply the patch manually, it's tiny. The project is frameworks_base.
- There is no APK alone that solves this, only the xposed module.
Supporters
Unexpected but not least important, the following people appreciated my work and made a donation or special thanks:
phoneturf
I submitted the fix patches to AOSP/Google and CM.
https://android-review.googlesource.com/#/c/168231/
http://review.cyanogenmod.org/#/c/107828/
good work! finally a patch
Sounds Awesome!!! @jgcaap Could you please spin a build with this patch and let us all know if it fixed it on bacon as well?
@YoshiShaPow @kantjer @fusionjack @temasek
This is what Android has become, the bug second most stared on their tracker is fixed by volunteers on XDA.
In general that does not make me very happy, but the work you did for them is awesome, thank you!
I'm a little confused now... Does this really fix the battery drain or is it just a fix for false measurement in batterystats? Because battery life on mobile data is much worse than on wifi for me since Android 5/5.1
It appears from your patch that this is only a reporting issue in the battery stats, and that the mobile radio IS being shut down, it just isn't being reported properly. If this is the case, do you have any idea why the battery performance in Lollipop is som much worse than KitKat?
acwest said:
It appears from your patch that this is only a reporting issue in the battery stats, and that the mobile radio IS being shut down, it just isn't being reported properly. If this is the case, do you have any idea why the battery performance in Lollipop is som much worse than KitKat?
Click to expand...
Click to collapse
Yes. In my device the radio IS being shut down properly. But in fact the code is a mess and I think there are many other bugs in the networking module.
I was on stock Kitkat and now I'm getting the same battery duration on CM12.1 (4h display on + 30m GPS/3G). Need more tests to detect more issues.
Anyway, I found another issue that I want to investigate that is the mobile data radio being activated and deactivated for a few seconds every time the wifi is connected.
Bazoocaze said:
Yes. In my device the radio IS being shut down properly. But in fact the code is a mess and I think there are many other bugs in the networking module.
I was on stock Kitkat and now I'm getting the same battery duration on CM12.1 (4h display on + 30m GPS/3G). Need more tests to detect more issues.
Anyway, I found another issue that I want to investigate that is the mobile data radio being activated and deactivated for a few seconds every time the wifi is connected.
Click to expand...
Click to collapse
Interesting. I was beginning to suspect that the Radio active time being displayed was a reporting issue, if the radio was really turned on as much as it claims, I think battery life would be much worse. Your patch is useful in that I now have a good idea of where to add logging statements to try see if there ARE issues with the actual radio active time.
reaper90 said:
I'm a little confused now... Does this really fix the battery drain or is it just a fix for false measurement in batterystats? Because battery life on mobile data is much worse than on wifi for me since Android 5/5.1
Click to expand...
Click to collapse
I do not know for sure. This will only solve the "mobile radio active time" issue on my device, where there is not a drain, but only the false measurement.
But if there is a problem in the RIL module of your device this patch will not solve the drain.
acwest said:
Interesting. I was beginning to suspect that the Radio active time being displayed was a reporting issue, if the radio was really turned on as much as it claims, I think battery life would be much worse. Your patch is useful in that I now have a good idea of where to add logging statements to try see if there ARE issues with the actual radio active time.
Click to expand...
Click to collapse
You ARE CORRECT.
I concluded the same when I put the decice in ariplane mode for several hours: the battery percent was the same at the end, but the mobile radio active counter keeps running for several hours, indicanting that the radio was turned of properly (same battery percent) but the timer keeps running.
Bazoocaze said:
You ARE CORRECT.
I concluded the same when I put the decice in ariplane mode for several hours: the battery percent was the same at the end, but the mobile radio active counter keeps running for several hours, indicanting that the radio was turned of properly (same battery percent) but the timer keeps running.
Click to expand...
Click to collapse
This is a good news/bad news situation. Good news, you have found the cause of the high radio active times. Bad news, something is still draining the battery. At least now we have better information...
Excellent work on pathing the issue, by the way...
abhibnl said:
Sounds Awesome!!! @jgcaap Could you please spin a build with this patch and let us all know if it fixed it on bacon as well?
@YoshiShaPow @kantjer @fusionjack @temasek
Click to expand...
Click to collapse
Concept seems interesting. Lemme look at the commits first before we go as far as building :good:
abhibnl said:
Sounds Awesome!!! @jgcaap Could you please spin a build with this patch and let us all know if it fixed it on bacon as well?
@YoshiShaPow @kantjer @fusionjack @temasek
Click to expand...
Click to collapse
Done
jgcaap said:
Done
Click to expand...
Click to collapse
Nice!
Still trying to put this into an xposed module, gonna take ages for me to do it
merewood bebox said:
Still trying to put this into an xposed module, gonna take ages for me to do it
Click to expand...
Click to collapse
I will make an detailed explanation on the first topic.
----
EDIT: done
So anyone here has made the module for xposed?
Sent from my Oneplus One using Tapatalk
---------- Post added at 12:58 PM ---------- Previous post was at 12:54 PM ----------
jgcaap said:
Done
Click to expand...
Click to collapse
@jgcaap would you like to share link for your build that has this patch?
Thanks
Sent from my Oneplus One using Tapatalk
Bazoocaze said:
I will make an detailed explanation on the first topic.
----
EDIT: done
Click to expand...
Click to collapse
thank you very much
Could anyone make either a xposed module or a flashable zip that we can use on bacon OnePlus One 5.1.1 to fix the mobile radio active issue? Thanks