I have been wanting to learn more about my Thunderbolt and been researching different components of my rom (bamf 1.6.3).
Something i would like more information on, especially before i start messing around with settings in my i/o scheduler on my das bamf toolkit.
I have not messed with any of the choices, but i have read up on a little bit of it and wikipedia'd it and kinda understand the concept.
My das bamf setting have nothing selected in the i/o scheduler, should it be? What should i set it two? Thanks guys.
Related
It seems that the guys with the Viewsonice G tablet located some issues at wake-up making the CPU run in 216Mhz..
Synopsis of what we learned:
Under certain conditions (LP1 suspend?), when the Tegra 2 was in a suspend state and a driver returned an error on wake-up, there is a step in the resume process where the voltage was supposed to be reset to the CPU, and that step was getting skipped. When the voltage was stuck low, the CPU would get stuck at minimum frequency, 216MHz and couldn't be pushed back to 1GHz or any other setting by the governor. There was a patch from NVidia that fixed this behavior, from a newer branch of the Tegra 2 source code than what Viewsonic used. We integrated this patch and found that indeed, it resolved the problem.
Maybe Teknoraver og badstorm2010 can include the patch those guys found with Nvidia, to fix our kernel too? not sure if Toshiba has the patch included..
or maybe its already in place, but it might be a cause for the wakeup issue we see on our tablet?
I still havent the kernel compile in place, due to a storage crash i lost all changes, so im unable to compile a new version atm..
See this post for alot more details on the problems.
Was messing around with the kernel anyway, so here we go.
I've also included utf8 NLS support (which is also default now) to support mounting NTFS volumes with utf8 charset.
The debug version of the patch sets the following properties
ro.debuggable=1
persist.service.adb.enable=1
This allows debugging/tracing of every (java-)process running on the system, no matter if they have the debuggable attribute set in their manifest.
weeds2000 said:
Was messing around with the kernel anyway, so here we go.
I've also included utf8 NLS support (which is also default now) to support mounting NTFS volumes with utf8 charset.
The debug version of the patch sets the following properties
ro.debuggable=1
persist.service.adb.enable=1
This allows debugging/tracing of every (java-)process running on the system, no matter if they have the debuggable attribute set in their manifest.
Click to expand...
Click to collapse
Thanks weeds! Do you have the original kernel laying around? For rollback purposes...
/Edit: Trying your kernel now, seems the HW buttons react now much better, did you change anything bout this?
weeds2000 said:
Was messing around with the kernel anyway, so here we go.
Click to expand...
Click to collapse
you compiled it with the patches included? right? sounds like the current custom kernel needs to be replaced..
im really hoping it solves some issues...
Did your kernel patch just fix out awake issue? i havent seen it for a while? and im wondering if the patch really was the solution, if so... its sooo great!
ill do some more "sleeping"
edit: ok, 2sec's after i wrote this it happened again, so didnt solve the screen awake issue i think..
I didn't do anything except implementing the patches. No button fixes, no wakeup stuff.
But it seems to be a good idea to get the Nvidia kernel running on the Folio as we then get some patches from Nvidia. Actually this was the "messing around" thing I've mentioned before.
I agree. Porting nvidia kernel might ease development when nvidia comes up with kernel for future android versions. At this point it looks like toshiba is dumping folio 100 for their announced honeycomb tablet. I am about to jump onto the ship and try out folio 100.
This is a script made by a member on AndroidForums originally for the LG Leon. We noticed that the CPU doesn't fall below 800mhz at all regardless of being under load or idle. This causes alot of battery drain since the CPU is running for literally no reason. I noticed the same problem on my Grand Prime G530T as the two devices share the same CPU.
This script will tune the CPU frequencies to drop to 200mhz when idle and fixes the time spent at higher frequencies, spreading the load across the cores more evenly for sustained performance and better battery life.
Instructions (root required obviously):
Download the script and extract it
Install SManager from the Play Store
Locate and select the MSM8916.sh file
At the top select SU
Hit RUN and allow permissions if asked
To see the difference, use a kernel tuning app (Kernel Adiutor I recommend) and watch the cores before and after running the script. It really does make a significant difference.
Credit to Bichofelix at AndroidForums for the script
Edit: fixed the script, now will keep max freq at 1190mhz instead of 998mhz
Edit 2: added sample screenshots of projected battery life
Hi, my device is G530HXCU. I also noticed on CPU-Z app that my device CPU doesn't fall below 800mhz. Tried using this script by following your procedures but the SManager shows "swapon failed for dev/block/zram0" when I run the script, just wanna ask if it is normal? Though when I closed all other apps on the task manager, my device CPU is now shown as 200mhz in CPU-Z. It seems like it worked. Thank you.
slasherkev said:
Hi, my device is G530HXCU. I also noticed on CPU-Z app that my device CPU doesn't fall below 800mhz. Tried using this script by following your procedures but the SManager shows "swapon failed for dev/block/zram0" when I run the script, just wanna ask if it is normal? Though when I closed all other apps on the task manager, my device CPU is now shown as 200mhz in CPU-Z. It seems like it worked. Thank you.
Click to expand...
Click to collapse
Yeah, the swapon thing can happen if your kernel (I think) doesn't support swap memory/zram. My G530T with the custom root kernel does and I don't receive this error, but it won't hurt anything if that particular part of the script doesn't run.
Enjoy the script and let us know how your device is faring with battery and performance. I'm a heavy gamer and from personal experience I get the same amount of performance and better battery, letting me play harder for longer ^_^
Hi, just wanted to share some feedback while using it. It greatly helps with reducing the battery drain and I really loved it, but on my G530H device, I need to run this script again whenever I reboot my phone. Though, when I did press the "boot" icon beside the "su" icon in the SManager and run the script again, it somehow solves the problem. However, the other problem that I've seen so far is that the maximum cpu of my device becomes 998mhz only, so I need to overclock it using a CPU controller app (I used No-frills CPU Control in playstore) to make it 1.19ghz and it worked. Is there anything I can do to help you fix that in the script so I won't need to use any CPU control app? Thank you very much I'm just a newbie here.
slasherkev said:
Hi, just wanted to share some feedback while using it. It greatly helps with reducing the battery drain and I really loved it, but on my G530H device, I need to run this script again whenever I reboot my phone. Though, when I did press the "boot" icon beside the "su" icon in the SManager and run the script again, it somehow solves the problem. However, the other problem that I've seen so far is that the maximum cpu of my device becomes 998mhz only, so I need to overclock it using a CPU controller app (I used No-frills CPU Control in playstore) to make it 1.19ghz and it worked. Is there anything I can do to help you fix that in the script so I won't need to use any CPU control app? Thank you very much I'm just a newbie here.
Click to expand...
Click to collapse
As stated in the OP, its not my script. But I went ahead and did it for you. Redownload the file and do the same as before. Setting the Boot option in SManager will run the script at boot after the system loads and the apps can gain SU permissions
Thanks for the tip and and glad you enjoy!
Added screenshots to the OP as proof of battery saving with the script.
Note: This usage was actually with an app called Resolution Changer that allowed me to use my screen in 720x1280 resolution, higher than stock which is 540x960. I also have Viper4Android installed with the highest audio driver available for it. These mods actually add more stress on the CPU, GPU and battery which would cause more drain. But as you can see...
I am also using a personally rebuilt rom that isn't ready for release yet as I'm having issues building it.
Who needs a 4000mha battery when you know how to use your system?!
Hello guys! I'm posting this now as I was searching on the Internet about Qcomm msm8916 devices! One tip I can give you as I learned some things, is to learn to build your device's kernel from source if your vendor has released it and remove the stock cpufreq limit API, as it is common in qcom. This API simply locks the frequency above some values to seem more snappy, but also reduces battery life in general! So it is common to sacrifice battery for speed and vice versa.. As you will see there are lots of posibilities also if you search the ramdisk for "optimizations" in frequencies that are done there, and change them to your liking! Happy modding! Cheers!
Nick Verse said:
Hello guys! I'm posting this now as I was searching on the Internet about Qcomm msm8916 devices! One tip I can give you as I learned some things, is to learn to build your device's kernel from source if your vendor has released it and remove the stock cpufreq limit API, as it is common in qcom. This API simply locks the frequency above some values to seem more snappy, but also reduces battery life in general! So it is common to sacrifice battery for speed and vice versa.. As you will see there are lots of posibilities also if you search the ramdisk for "optimizations" in frequencies that are done there, and change them to your liking! Happy modding! Cheers!
Click to expand...
Click to collapse
Nice bit of info there, but this script actually furthers those optimizers to reduce the number of cores needed to run processes and at lower frequencies. If it doesn't need it, your wasting performance and battery. This script helps regulate core speeds and cores online depending on what your doing using the interactive governor, which appears was not setup properly by the phone manufacturer of the device containing the msm8916 chipset.
I tried using it in CM12.1 unofficial rom for G530H and it works. I also think it helps reduce the appearance of deadlock bug for that rom. I edited the script and set the maximum cpu value to 1190400 instead of 1190000 because my device cpu is not going up to 1.19ghz when the script is only set to 1190000 so I tried to make it higher and it solves the problem.
Does it work on all MSM8916-based devices ?
What is the point of going under 800MHz? CPU takes same voltage on 200MHz and 800MHz.
I found this trick in S6 forums. Thanks to @mikeyinid
Paste:
Explanation: (From @mikeyinid )
Here is a quick rundown on how this came about, and what we actually know.
Since I purchased the S6 on release day, I've been messing with certain things, as you can see from the ROM I posted, Looper(shameless plug). Debloating Samsung apps really helped with battery life and I was pretty happy with the results. But like so many other people, I didn't understand why my S6 killed apps so aggressively. Initially I thought it might be the memory leak we all know so much about in 5.0. So, I did a little research and found the patch for that. While it did help keep the device stable over time, apps were still being killed with no prejudice. All this time I noticed really useless services running in the background, often stuff I'd never even opened. I studied LMK and started messing with those settings. After a month of trying everything I could find documented, I was ready to give up. Yesterday I was looking through the services.jar smali for the 37,875th time and realized the DHA referenced in there has to have something to do with memory management. I kept overlooking it because I hadn't seen mention of it anywhere else. I am no smali guru, as some of you know. But it was pretty obvious DHA was influencing memory management to some extent. Samsung, although leaving us in the dark on this, was kind enough to give us props to set the values for DHA. I pulled a few that seemed relevant, added them to my build.prop, and what do you know. For the first time in almost two months of tinkering, I saw an improvement in the way my device was managing memory.
The thing everyone needs to understand; I have no clue what DHA is. It overrides every aspect of Googles LMK and seems to do so in a way that makes more sense. I'm sure someone with more knowledge than myself will be able to tune this to the point the S6 will be the multi-tasking champ. There are several other props in the smali that are probably useful. I will try to get them all with their default values posted today. This has been pretty exciting for me, I spent way to much time trying to figure out the issue to not make some sort of progress. I hope you guys enjoy the tweaks, and I hope it helps sway those of you on the fence about keeping this device to stay. It's only gonna get better
Instructions:
First find your build.prop. This is located in /system. to get to /system you need to go to the root directory using a file explorer and then go to the system folder. The build.prop will be in there. You can also use and app such as build.prop tweaker but its a bit harder (imo)
In your build.prop scroll to the very bottom and paste this in:
(values in my build.prop Note 3 Neo, may be others values work better but for me are awesome)
ro.config.dha_cached_max=30
ro.config.dha_cached_min=14
ro.config.dha_empty_init=36
ro.config.dha_empty_max=12
ro.config.dha_empty_min=8
ro.config.dha_th_rate=1.0
ro.config.dha_lmk_scale=0.878
Delete duplicate lines if you find.
Other thing. With Kernel Adiutor in LMK section select "very agressive" and apply on reboot.
Finally reboot your device.
Enviado desde mi SM-N7505 usando Tapatalk 2
other values to compare how it works, only four lines to add to build.prop:
ro.config.dha_cached_max=15
ro.config.dha_empty_max=30
ro.config.dha_lmk_scale=0.600
ro.config.dha_th_rate=1.4
Note, activate too "very agressive" mode in LMK (Kernel Adiutor)
everything works without freezing, bootloop?
I have a dual boot Android 5.1/Win 10 tablet (the Onda oBook10) that I recently managed to acquire root on (for any owners of this device that would like to know how, I'll be posting a guide soon). This thing has 4 gigs of RAM, but starts kicking apps out as soon as 1 GB is occupied. I've tried setting minfree using both Kernel Adiutor and by echoing manually to /sys/module/lowmemorykiller/parameters/minfree, but neither has any effect. I know that this change doesn't persist across reboots on any Android, but in this case, it has no effect even on the current session. What's even stranger, going by the default values that have been set, there shouldn't be any issues at all - it's actually less aggressive than most other devices I've seen. The values are:
Code:
13107,16384,19660,22937,26214,32768
According to Kernel Adiutor, that translates to (in MB):
Code:
51,64,76,89,102,128
Yet, running apps shows 2.8 to 3.1 GB free constantly, even though apps are reloading.
Does anyone know what might be causing this? It's an x86 device, in case that's relevant. I have access to the boot image (in case it's some kind of kernel flag), and can unpack to ramdisk and zImage, but I have no experience with kernels, and have no idea where to even begin looking; if someone could point me in the right direction, that would be awesome.
Thanks,
SirVer
Hi I just rooted my phone (KingRoot) last night and got ROM Toolbox Pro. First thing I wanna test out is adjusting the CPU settings under the Performance tab. I've looked into a bit at what I/O Scheduler does, and the Governors, but still not quite familiar with them. I'm using an Alcatel OneTouch Elevate (5017B) which uses a Qualcomm Snapdragon 210 8909. Anyone have any ideas, or pre-made settings, as to add more smoothness to games? If it matters, I play Book of Heroes, which isn't really a graphic intensive game at all, but this isn't a great cpu/gpu unit to begin with ;p
Also, any recommended Kernel Tweaks, if any, to help with smoothness?