Hi,for the past two weeks,i discovered my HTC desire (unrooted,unbranded and unlocked,on froyo) has been laging like crazy not just web browsing but the entire OS.for example,the smooth transition between each screen (Home screen and the rest) is gone.Also,accessing menus and apps tend to lag, basically everything.You can easily tell that the device is definitely buggy.
Could anyone please recommend a fix different from hard/factory reset?As I've put so much work into device i.e. customizing screens,sorting out apps,and most importantly getting all my email accounts functioning.
It would be a big shame if I have to do a complete factory reset and if that's the only solution for now,will a future software update resolve this issue (lags)? And if i decide to go ahead with the hard reset,will the device let me do automatic backup of the following details:
* Text and multimedia messages
* Settings in the Messages application
* Web bookmarks
* Keyboard dictionary
* Settings in your phone that fall under these categories:
o Wireless & networks
o Sound & display
o Location
o Applications
o Date & time
o Language & keyboard - only the Locale setting
Thanks
what have you done to it?!?!
since day 1, I had loads of apps, no lag, loads of music, movies, pictures etc.. no lag. now, counting.. counted.. 48 rows x 4 columns of apps.. = 192 apps including all the sense ones.. still NO LAG! do a factory reste and see if that works, if not, try flashing a different ROM laterz.
Are you using a task killer?
Invisible Elf said:
Are you using a task killer?
Click to expand...
Click to collapse
I used one called Advanced Task pro but uninstalled it immediately as soon as I found out 'task killers' are more damaging .
Sent from my Archos5 using XDA App
Im underclocking my desire to 700mhz and even then, the only time it lags is the first few minutes after boot....
Sent from my HTC Desire using Tapatalk
Checked RAM usage?
Hi nasimdejai!
I have a similar problem after a day or two, when I have often browsed the web, searched for something and watched youtube vids in browser.
Is the problem after a reboot gone?
Have you checked if you are running out of mem? (Install e.g. Temp+CPU V2 from market and put the widget on your homescreen)
Because in my case, there are running a few instances of the android browser which are eating up my mem and don't get killed by the process managment.
To check this, install Terminal emulator and type in ps.
When there are more processes like com.android.browser or FP_DoPlay you have the same issue like I do. (see attachments)
I kill the unwanted/older instances with the command kill 5920 (PID number from process, see 1st attachment).
You can easily tell that the device is definitely buggy.
Click to expand...
Click to collapse
There is no "Galaxy S lag" type problem/bug that affects all Desires, so I think it is your configuration/setup, not the device itself per se!
My advice to you would be to take a Nandroid backup and then factory reset, so see if this "cures" your problem. If it does, chances are you have a rogue app that is causing your problems rather than a "system" setting, so you then have two realistic options.
1. Restore your Nandroid backup and start de-installing applications until performance becomes acceptable again. If you have something like Titanium Backup, you can always backup the app+data you wish to de-install, so that you can bring it back again easily if you require.
2. Start setting your device up from scratch again.
Note that if your phone is not rooted, you won't be able to make a Nandroid backup anyway, so you'll be left with option 2 only!
Regards,
Dave
hi floyd0815,thanks for the suggestions.I've got this app that displays memory (RAM) each time i use the device for any task be it browsing,youtube vids.And I could tell that some of these tasks do eat up memory but after completing said tasks,i immediately go into the "manage application" setting,clear the cache for each process/app used and then the RAM usually goes back to the previous size.Presently i've got 71MB of RAM and execution of processes/applications usually shaves 2MB or 3MB at most,off the current memory size.Alot of people tend to have way less RAM on their devices and still have fully function phones without lags.The reason for me being a bit worried.I'll either wait for the rumoured december update or do a factory reset if the problem persists.I'll try downloading Terminal emulator.Cheers
71MB of RAM????????? My Desire usually had 200MB of ram free before i rooted! Use a task Killer. Its nessecary. those things that tell you they are not are not always true. Get a good task killer like quick process killer or such. that should solve your problem.
Hi nasimdejai!
After a fresh boot, I have got about 120mb of free mem with the browser opened, but after 1-2 days it's going down to 70-40mb and stays there. Then it's sluggish. (e.g. FolderOrganizer onscreen-folder links open slowly,...) There I first started to clean the caches and logs, but that gave only a few mb's and the system stayed slow. Then I have seen those multiple browsers in the terminal.
I don't understand, why the android-process-managment doesn't kill the old browser instances but other processes that provide widgets?!
When I kill that old instances, I have up to 160mb+ of free RAM and the system is snappy again.
Do you have Astro (file manager) installed? If so, you can open it and press menu -> Tools -> Process manger -> Processes and look for FP_DoPlay (thats the browser). There it's shown how much RAM those processes need. (look at my 1st posts 2nd attachment)
Keep me updated about your Terminal emulator result! (ps)
P.S.: I don't use a task killer for killing running processes, only if something has crashed or as list of running apps.
shockem said:
Its nessecary. those things that tell you they are not are not always true. Get a good task killer like quick process killer or such. that should solve your problem.
Click to expand...
Click to collapse
Not again!
No task killers are *not* necessary. Some people perceive some benefit from using them, but in general as long as you don't have an errant app they are most certainly not necessary!
Also - the amount of free memory you have is not an good indicator of performance! Remember than by default Android does not "swap" and just because memory is being consumed doesn't mean that CPU cycles are.
If anything, freeing up memory by killing processes can actually slow the system down because the process might not be consuming any CPU cycles but may well be required later and so keeping it in memory will actually allow it to resume far quicker than it would do otherwise.
Regards,
Dave
Hi Dave!
I am not a killer too! ;-)
But my system gets really slow after a while. (1-2 days, depending on how often I use the browser)
Before I have seen the multiple browser instances, I tried to make it faster by clearing caches and logs with no big change.
I know "the amount of free memory you have is not a good indicator of performance" but it was the only thing I noticed when the system was getting sluggish.
And as you can see in the attachments of my 1st post here, the android browser needs A LOT OF RAM (4 instances: 150mb+) and doesn't get killed by the android process managment.
PLEASE type in a terminal ps > /sdcard/ps.txt to save the output onto your sd-card and then post it here, so we can see if your system does the same! (your desire should have been runing for a while)
THX in advance!
My ps attached. Note that I hadn't used the browser this morning (last time was last night), so I started it and opened all 4 windows to different sites before running ps.
It definitely sounds to me like the Android memory management is not running correctly on your device - have you done anything to it, or set up swap etc?
Regards,
Dave
@Dave
THX for the quick response!
In your system are 2 running browser processes (and some FP_DoPlay = flash?), which could be normal, but one of them (PID 4734) is old and maybe should have been closed by the system.
Would be nice to check later again, when a task manager tells you, that there is no running browser.
And no, I haven't done anything to the memory management or something else.
Leedroid 2.2d + sdfix kernel + bright silence theme
Radio ***09.05.30_2
This also happend on PinkyROM, after that I did a full wipe.
THX
EDIT: In /system/etc/sysctl.conf is standing "vm.swappines=1", so on my system is swapping enabled?!
floyd0815 said:
n your system are 2 running browser processes (and some FP_DoPlay = flash?), which could be normal, but one of them (PID 4734) is old and maybe should have been closed by the system.
Click to expand...
Click to collapse
I wouldn't expect the system to kill a process just because it is old if there is sufficient memory available.
EDIT: In /system/etc/sysctl.conf is standing "vm.swappines=1", so on my system is swapping enabled?!
Click to expand...
Click to collapse
Have you partitioned your SD card with a swap partition?
Regards,
Dave
I wouldn't expect the system to kill a process just because it is old if there is sufficient memory available.
Click to expand...
Click to collapse
Thats true and I don't know if your sys is running out of mem, but in my case, android should close those processes. (only ~40mb left)
I also read, that the "vm.oom_kill_allocating_task=1" in the sysctl.conf means, android kills the processes with the highest mem usage, but it doesn't! (in my case)
And I haven't made a swap partition or customized the sysctl.conf. (stock from LeeDroid 2.2d) Just read, that ...swappines=1 doesn't take an effect if you haven't got swap.
But now I changed "vm.oom_kill_allocating_task=0" and rebooted.
Lets see what happens!
floyd0815 said:
Thats true and I don't know if your sys is running out of mem, but in my case, android should close those processes. (only ~40mb left)
Click to expand...
Click to collapse
40mb left is nowhere near running low on resources IMO - killing at 40mb free is just a waste of 40mb memory.
And I haven't made a swap partition or customized the sysctl.conf. (stock from LeeDroid 2.2d) Just read, that ...swappines=1 doesn't take an effect if you haven't got swap.
Click to expand...
Click to collapse
I don't have a sysctl.conf file at all, so "stock" isn't always stock!
Regards,
Dave
T
foxmeister said:
40mb left is nowhere near running low on resources IMO - killing at 40mb free is just a waste of 40mb memory.
Click to expand...
Click to collapse
But I see the android process manager working to free RAM, kicking out apps but not the browser, which is huge?! With the sysctl.conf "vm.oom_kill_allocating_task=1"?!
I don't understand that and I don't care anymore.
I make me a script like:
Code:
#!/bin/sh
ps|grep com.android.browser|grep -v grep|awk '{print $1}'|xargs -r kill
exit
und Pasta!
I have the same problem, but i can't kill browsers through terminal emulator. Nothing happens when I enter kill *pid*
And fp_doplay isn't listed there it is listed in astro with 78mb! But i can't kill it there.
My terminal emulator ps after browser closing:
export PATH=/data/local/bin:$PATH
$ $ps
PID USER TIME COMMAND
1 0 0:03 /init
2 0 0:00 [kthreadd]
3 0 0:22 [ksoftirqd/0]
4 0 0:24 [events/0]
5 0 0:00 [khelper]
6 0 0:00 [ksmartass_up/0]
7 0 0:05 [ksmartass_down/]
8 0 0:00 [async/mgr]
9 0 50:24 [suspend]
10 0 0:00 [sync_supers]
11 0 0:01 [bdi-default]
12 0 0:01 [kblockd/0]
13 0 0:02 [kmmcd]
14 0 0:00 [bluetooth]
15 0 0:01 [smd_tty]
16 0 0:00 [qmi]
17 0 0:00 [rpcrouter]
18 0 0:00 [krpcserversd]
19 0 0:00 [microp_work_q]
20 0 0:00 [detection/0]
21 0 0:00 [button/0]
22 0 0:00 [detect/0]
23 0 0:00 [button/0]
24 0 0:06 [kswapd0]
25 0 0:00 [aio/0]
26 0 0:00 [kslowd000]
27 0 0:00 [kslowd001]
28 0 0:00 [crypto/0]
41 0 0:59 [panel_on/0]
42 0 0:00 [msm_serial_hs]
43 0 0:00 [mtdblockd]
50 0 0:00 [msm_hsusb]
51 0 0:00 [usb_mass_storag]
52 0 0:00 [gs_tty]
53 0 4:37 [synaptics_wq]
54 0 0:00 [proximity_wq]
55 0 0:01 [ls_wq/0]
56 0 0:03 [curcial_wq]
57 0 0:00 [w1_bus_master1]
58 0 0:00 [kstriped]
59 0 0:00 [kondemand/0]
60 0 0:00 [kconservative/0]
61 0 0:00 [kinteractive_up]
62 0 0:00 [knteractive_dow]
63 0 0:00 [binder]
64 0 0:00 [krfcommd]
65 0 3:33 [ds2784-battery.]
66 0 2:59 [mmcqd]
85 0 0:00 [kjournald]
129 1000 0:04 /system/bin/servicemanager
130 0 0:04 /system/bin/vold
131 0 0:04 /system/bin/netd
133 1001 0:33 /system/bin/rild
136 1002 0:01 /system/bin/dbus-daemon --syst
137 0 0:01 /system/bin/installd
138 1017 0:01 /system/bin/keystore /data/mis
139 0 0:01 /system/bin/ipd
140 1008 3:40 /system/bin/akmd
391 0 0:06 [loop0]
393 0 0:00 [kdmflush]
407 0 0:00 [kcryptd_io]
408 0 0:47 [kcryptd]
891 0 0:00 [loop1]
892 0 0:00 [kdmflush]
893 0 0:00 [kcryptd_io]
894 0 0:03 [kcryptd]
897 0 0:00 [loop2]
898 0 0:00 [kdmflush]
899 0 0:00 [kcryptd_io]
900 0 0:00 [kcryptd]
901 0 0:00 [loop3]
902 0 0:00 [kdmflush]
903 0 0:00 [kcryptd_io]
904 0 0:00 [kcryptd]
905 0 0:00 [loop4]
906 0 0:00 [kdmflush]
907 0 0:00 [kcryptd_io]
908 0 0:06 [kcryptd]
923 0 0:04 [loop6]
924 0 0:00 [kdmflush]
925 0 0:00 [kcryptd_io]
926 0 0:31 [kcryptd]
4864 0 0:00 [loop5]
4865 0 0:00 [kdmflush]
4866 0 0:00 [kcryptd_io]
4867 0 0:03 [kcryptd]
5370 0 0:00 /system/bin/debuggerd
10069 10007 0:00 com.android.browser
10074 10007 0:00 com.android.browser
11135 10014 0:36 com.htc.android.htcime
11142 10024 0:26 com.google.process.gapps
11489 10049 0:00 com.android.mms
12799 10005 0:06 com.android.htccontacts
15240 9999 0:31 com.htc.launcher
15403 10105 1:21 com.zomut.watchdoglite
15759 10010 0:07 com.htc.bgp
15988 10010 0:11 com.htc.bg
16748 10121 0:00 com.handyapps.easymoney
16769 0 0:00 [flush-179:0]
16906 10040 0:00 com.esmertec.android.jbed
16932 0 0:00 [iscan_sysioc]
16933 0 0:00 [dhcp_sysioc]
16934 0 0:00 [dhd_watchdog]
16935 0 0:00 [dhd_dpc]
16936 0 0:00 [dhd_sysioc]
16937 1007 0:00 /system/bin/logwrapper /system
16939 1010 0:00 /system/bin/wpa_supplicant -Dw
16955 1014 0:00 /system/bin/dhcpcd -ABKL eth0
17048 10088 0:00 org.peterbaldwin.client.androi
17079 10123 0:02 com.google.code.appsorganizer
17090 10067 0:02 com.android.vending
17110 10121 0:00 com.handyapps.easymoney:remote
17119 10096 0:08 com.thedeck.android.app
17136 0 0:00 [flush-31:0]
17147 10076 0:01 com.google.android.googlequick
17175 10039 0:00 com.htc.WeatherWallpaper
17198 10093 0:00 jackpal.androidterm
17205 10093 0:00 /system/bin/sh -
17210 10131 0:02 com.estrongs.android.taskmanag
17228 10093 0:00 /system/bin/sh -
17231 10093 0:00 ps
22931 1013 2:49 /system/bin/mediaserver
22932 0 0:16 zygote /bin/app_process -Xzygo
22937 1000 80:34 system_server
23034 1001 5:06 com.android.phone
23043 10085 0:25 sg.ruqqq.quickdesk
24864 10005 3:22 android.process.acore
27354 10007 0:00 com.android.browser
$
Hi Vukis!
Seems that we are the only ones having this problem, maybe because others are flashing/restarting there Desire daily so they don't have/get it.
Try:
Code:
su
kill -9 10069
kill -9 10074
...
It's an aggresive killing, but the only way I know to get rid of these "zombies".
Regards,
Floyd
Related
It seems like once a day, my phone will become super sluggish, to the point of no longer being usable. A simple reboot will clear up the problem, but there seems to be a larger issue as this is happening every day.
ROM - Myn's Warm 2.2 RL2
Kernel - Ziggy's 10/26
Code:
# top -m 5 -n 1
User 92%, System 7%, IOW 0%, IRQ 0%
User 278 + Nice 0 + Sys 23 + Idle 0 + IOW 0 + IRQ 0 + SIRQ 0 = 301
PID CPU% S #THR VSS RSS PCY UID Name
106 98% S 67 303536K 50328K fg system system_server
76 2% S 3 2764K 304K fg compass /system/bin/akmd
21278 1% R 1 940K 416K fg root top
5 0% S 1 0K 0K fg root events/0
21238 0% S 10 165336K 20484K fg app_124 jackpal.androidterm
Is this just an issue of needing to find a new kernel or rom? I am just not sure where to start looking for the culprit.
Thanks
I was having that issue as well and even sluggishness as well when touching the screen. I ended up reading about other people having that issue on his thread with his rom so check there. Might have to do alot of reading though. But I ended up leaving and going back to Baked Snack 1.9
Globetrahter said:
I was having that issue as well and even sluggishness as well when touching the screen. I ended up reading about other people having that issue on his thread with his rom so check there. Might have to do alot of reading though. But I ended up leaving and going back to Baked Snack 1.9
Click to expand...
Click to collapse
Yeah, I tried to read through the thread, but it turned in to a clusterF pretty quickly, just like every other rom thread.
This issue only started on Thursday, the 28th, so like I said I wasn't sure how to figure out where the real problem was. Guess I'll grab some beer and start reading through Myn's thread again.
If anyone has an idea of how to track down the culprit, please let me know.
Hi
i have a weird thing , dont know if its rom related but defenetly noticed it after rooting my device and installing cosutm roms. well i only used ARHD since 2.0.09 and i love it.
but , what happens is that suddenly and out of nothing (after like hours/days and the rom running smooth and ultra fast) , system cpu usage jumps to 100% and never bugs off only through a restart, and this seems to happen with all the different versions of ARHD i had, even though i install most of them with full wipes. but this i don't understand and it annoyes me cos it uses this cpu amount and drains battery and it happens suddenly and randomly , dunno what triggers it, and no matter how i tried to track it to see the error but couldn't find a thing.
i just hope u can help me by taking a look at this log i saved from android systeminfo app registering some errors (3 min log and it drained 14% battery ) , it shows something about "activity manager", im not a developer and i know nothing about those codes, but would be awesome if someone helps me out with any tip please.
thank you.
I am not a DEV but i don't think your log file includes any clue of what is causing your problem. Do you have sense account on? or any types of account that let you track your phone?
Activate usb debugging
Seems to be the bug with the .init process.
Sent from my Desire HD using Tapatalk
thank you for the replies , i already have usb debugging on. dunno what is causing this, its totally random and its driving me nuts.
can you see a process that uses 100% cpu in android system info? If yes, try to kill it and look at your cpu usage.
CPUNotify is a great tool. It shows cpu usage in the notification bar
Sent from my Desire HD using Tapatalk
the process showing 100% cpu usage (not always but randomly, no idea what triggers it ) is system , and u can't force close or end that task
Hmm strange... i can't even find a process called activity manager on my phone...
Well i don't know but maybe it's related to the DroidDream malware. Some apps in the market were infected with this virus. And i've read that the virus gains root access and can download other apps in the background.
Here's a link: http://forum.xda-developers.com/showthread.php?t=977154
I really don't know if it's related to this but it just came to my mind
Sent from my Desire HD using Tapatalk
thx for the help mate , but i dont think its related to droidream cos ive been having this issue since a while (long time before droidream was up )
im still monitoring to find out what is causing this issue.
i have the same issue since going to a rooted ROM (HD rev 2.0.12). tried every build up to 3.0 and i have the same issue. it seems to be randomly triggered (i've seen it trigger after playing "robo defense", playing music, making a call etc).
i have no sense account and dont have malware and have usb debugging on
I fix/hack it this way..open adb shell
type
chmod 700 /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
ie disallow anything (even system_server) from reading this file.
in fact i automate this command to run every 15 mins using an app called phone prioritizer. as soon as you type the chmod..your logcat will stop spinning and all will be well (iove not seen any side effects yet).
ps. you have to run this every time you open setcpu, as it will reset the permission on this file to 777/666 depending on the version of setcpu you have.
Activate usb debugging
Seems to be the bug with the .init process.
Click to expand...
Click to collapse
nope that totally different. that problem shows itself in "top -m 5" as init taking all the cpu ..this will show as system_server.
the "bug" manifests itself in this kernel file:
goto url github.com/android/platform_frameworks_base/blob/master/services/java/com/android/server/ProcessStats.java#L157
it spins on getCpuSpeedTimes() where it reads time_in_state..why it does this i dont know..it looks like mBuffer is corrupt as nosuchelementException would indicate that the buffer didnt have 2 words per line of the file yet the real file looks fine if you cat it (readFile seems not to initialise this on reading it to null first (but i'm not a java expert..maybe ".read" does this) so perhaps it has junk in it on certain conditions..any java guys out there can explain why they made this a glbal variable? it seems like it should be a local one)
by chmodding the file i cause an IOException to throw in readFile (which is then ignored and the return is gracefully set as null..this then skips the infinate loop).
you can see this issue in a few bugs like android issue 9733..oxygen rom issue 507 etc.
wow , cheers mate for the help , sounds a bit complicated for me but at least we know what it is now and how to get over it.
but how come mike1986 doesnt know about this bug and its fix ? he could incorporate this into his next build so it saves us that command run every 15 mins. or it cant be incorporated ?
someone should tell him to be honest
but cheers for explanation mate, thank you
Is Apache14 informed about this? Maybe he can solve it in next Kernelversion.
walda said:
Is Apache14 informed about this? Maybe he can solve it in next Kernelversion.
Click to expand...
Click to collapse
i have no idea about that , if he does then im sure he will fix it
As I read in mikes 3.0 thread, he is informed. Fine...
sent from my DHD via Tapatalk
further to this.
in ProcessStats.java (im not sure if this is a kernel file or if it sits just outside the kernel).
mBuffer looks to me to be the main problem.
1. in apaches rom, which is overclocked he defines 23 CPU speeds..ProcessStats.java only allows 20
Code:
private long[] getCpuSpeedTimes(long[] out) {
long[] tempTimes = out;
long[] tempSpeeds = mCpuSpeeds;
final int MAX_SPEEDS = 20;
if (out == null) {
tempTimes = new long[MAX_SPEEDS]; // Hopefully no more than that
tempSpeeds = new long[MAX_SPEEDS];
this is a minor issue..as this overflow is trapped in the loop anyway:
Code:
if (speed == MAX_SPEEDS) break; // No more
however, the definition of mBuffer is too small:
Code:
private byte[] mBuffer = new byte[256];
my file at the moment is 300 bytes. the readFile reads only once instead of looping until end of file:
Code:
int len = is.read(mBuffer);
is.close();
so only the first 256 bytes are ever read.
My assumption is that IF the files first 256 bytes ends up cutting off the last read line (and that line lies in the first MAX_SPEEDS lines of the file) before the speed time element..this causes a NoSuchElementException to throw..as the last line will be like
921600 255
960000 750
998400 8042
10368
ie the line
1036800 3089
was cut off too soon and this code
Code:
long val = Long.parseLong(token);
tempSpeeds[speed] = val;
token = st.nextToken(); <-- here
val = Long.parseLong(token);.
in getCpuSpeedTimes() fails as it cant see the timing?
would then fail on the second nextToken().
the big question is who owns that code in our custom ROM? is it the same as the original android code so we are at the mercy of Google to fix it or is this something Mike / Apache will be able to patch up ..assuming i'm making sense
the only workaround is as i said before: to chmod this file to 700 and ensure it stays there (avoid using setcpu as it changes the permissions).
You can probably also reduce this by limiting the CPU frequency range your phone uses (ie keep the filesize smaller)..if you have profiles that span 200mhz to 1.2ghz then you will probably hit this sooner
i did a test.
1. rebooted my phone..ensured time_in_state had permissions -r--r--r--
2. manipulated CPU frequency using cpu tuner to make all frequencies have at least 5 bytes per line.
once the first 20 lines were > 256 bytes and the 256nd byte sat between <cpu speed> and <time spent at that speed> i get the loop.
eg just before the issue arose i saw:
Code:
# cat time_in_state
cat time_in_state
245000 200030
422400 12676
460800 11929
499200 10333
537600 37021
576000 10685
614400 13672
652800 10646
691200 14864
729600 13956
768000 12662
806400 15025
844800 22094
883200 26741
921600 10389
960000 9937
998400 17606
1036800 6864
1075200 1560
1113600 1296
1152000 2158
1190400 2540
1228800 2463
i had my cpu pinned to 960 mhz.
the 256 at this point lies here:
Code:
1075200 1560
1113600 1
ie line 20 is cut off after 1..this is still "valid" in terms of the data in mBuffer..but once 960 rolled into five digits
Code:
# cat time_in_state
cat time_in_state
245000 200030
422400 12676
460800 11929
499200 10333
537600 37021
576000 10685
614400 13672
652800 10646
691200 14864
729600 13956
768000 12662
806400 15025
844800 22094
883200 26741
921600 10389
960000 10288
998400 17606
1036800 6864
1075200 1560
1113600 1296
1152000 2158
1190400 2540
1228800 2463
the 256 byte now meant the last line shifts to:
Code:
1036800 6864
1075200
the 2nd word is now totally missing!
as soon as this happened..my logcat started issuing
Code:
Unexpected exception collecting process stats
java.util.NoSuchElementException
at java.util.StringTokenizer.nextToken(StringTokenizer.java:272)
at com.android.server.ProcessStats.getCpuSpeedTimes(ProcessStats.java:596)
at com.android.server.ProcessStats.getLastCpuSpeedTimes(ProcessStats.java:568)
at com.android.server.am.ActivityManagerService.updateCpuStatsNow(ActivityManagerService.java:1657)
at com.android.server.am.ActivityManagerService$4.run(ActivityManagerService.java:1583)
errors.
something later on then causes this behavior to go into a full tight loop (as once the issue starts..it just issues this every few seconds..so most uses wont notice it).
didnt mike fixed it with his latest release (ARHD 3.1) ?
Goodm7sn said:
didnt mike fixed it with his latest release (ARHD 3.1) ?
Click to expand...
Click to collapse
mike changed the file permission to 700 to get around it. the bug is still there in the code though. also im not sure if hes scheduling it to make it stay at 700..if not then users with setcpu installed may still get the problem (as setcpu changes the file permission back to 777/666 when you open the gui).
DazzaL said:
i have the same issue since going to a rooted ROM (HD rev 2.0.12). tried every build up to 3.0 and i have the same issue. it seems to be randomly triggered (i've seen it trigger after playing "robo defense", playing music, making a call etc).
i have no sense account and dont have malware and have usb debugging on
I fix/hack it this way..open adb shell
type
chmod 700 /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
ie disallow anything (even system_server) from reading this file.
in fact i automate this command to run every 15 mins using an app called phone prioritizer. as soon as you type the chmod..your logcat will stop spinning and all will be well (iove not seen any side effects yet).
ps. you have to run this every time you open setcpu, as it will reset the permission on this file to 777/666 depending on the version of setcpu you have.
nope that totally different. that problem shows itself in "top -m 5" as init taking all the cpu ..this will show as system_server.
the "bug" manifests itself in this kernel file:
goto url github.com/android/platform_frameworks_base/blob/master/services/java/com/android/server/ProcessStats.java#L157
it spins on getCpuSpeedTimes() where it reads time_in_state..why it does this i dont know..it looks like mBuffer is corrupt as nosuchelementException would indicate that the buffer didnt have 2 words per line of the file yet the real file looks fine if you cat it (readFile seems not to initialise this on reading it to null first (but i'm not a java expert..maybe ".read" does this) so perhaps it has junk in it on certain conditions..any java guys out there can explain why they made this a glbal variable? it seems like it should be a local one)
by chmodding the file i cause an IOException to throw in readFile (which is then ignored and the return is gracefully set as null..this then skips the infinate loop).
you can see this issue in a few bugs like android issue 9733..oxygen rom issue 507 etc.
Click to expand...
Click to collapse
Thanks mate, your solution is really effective on my DHD with revolution 3.0.
I am going to reflash with revolution 3.1, hopefully 3.1 will cure the cpu 100% usage
im on android revolution HD and i can confirm this , 100% system cpu of death is still here, didnt get fixed , had to change setcpu frequency and it stopped
meh phone cant last 12 hrs without a restart, frustrating.
DazzaL said:
mike changed the file permission to 700 to get around it. the bug is still there in the code though. also im not sure if hes scheduling it to make it stay at 700..if not then users with setcpu installed may still get the problem (as setcpu changes the file permission back to 777/666 when you open the gui).
Click to expand...
Click to collapse
if setcpu changed the range once the gui is opened , what do u recommend us to use for overclocking ? something safer
thx for helping
I read that it happens with CPU tuner and even without anything also!
The only solution I see is to fix the frequency file.
sent from my DHD via Tapatalk
Hi,
My "defy" always had freezing and lag problems when I try to run heavy applications, such as 3D games, or Gmaps, etc.. in every ROM I've tried (CM7, MIUI, stock froyo, stock gb, etc.)
I read that a solution could be setting the minimum values of memory with an application called SYSCTL CONFIG (it's in the Market)
Anyone also has this problem? What values do you use? Increasing this value, can cause problems?
Code:
Mine are:
Min Free Kbytes: 8192
Dirty Ratio: 95
Dirty Background Ratio: 60
Pressure VFS Cache: 20
PD: This is the post I found: http://forum.xda-developers.com/archive/index.php/t-1047153.html
Same here ... : )
I had to use Sysctl config to set the min free Kbytes to 8192.
But all remaining parameters are left in default values.
Dirty Ratio = 20
Dirty Backgr. = 5
VFS Cache Pressure = 100
Note: I am not a developer. I am merely informing the community about this rom. I take no credit for this rom. All credits for this rom go to the Virtuous Team for such an amazing rom I will post updates as the rom gets updated
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Virtuous Infinity
We are pleased to announce the first release of Virtuous Infinity.This ROM is the first ever which brings the full Sense 4 experience to your favorite WVGA device.Thanks to great effort of our M10 team (including Cypis, Diamondback and Flemmard) we finally cracked the new m10 format to bring you the lastest HTC software!It is based on the 1.11.401.110 release RUU of VilleC2. We would like to give special thanks to Football for the RUU.This build currently is a X-Series release, however, it is suitable for use as a daily driver if you can live with a few minor bugs.We hope to have the ROM feature complete as soon possible. Check bellow for a full list of what is working and what is not.
Primo is the result of a collaborative, team effort by the following developers:
Flemmard
Diamondback
rmk
chrisch
mdj
seo
eViL_Dee
cypis
cjward
tbalden
Features
Based on the VilleC2 ROM (1.11.401.110).
"Full" Sense 4 resized for WVGA resolution
Tweaks app build with latest HTC SDK 15
Fully Deodexed
Ported for almost full functionality on all of supported devices
Heavily optimized for fluid performance and usability.
Market-sourced applications (Gmail, Maps, Voice, etc) automatically installed on first boot into /data/app for easy removal.
Bloatware and unnecessary applications removed.
Working
Camera
HW Acceleration
WiFi
Bluetooth
Mobile Data, SMS, MMS & Voice Calls
GPS
Sensors
Audio
USB Storgage (No 3rd Party App Required)
FM Radio
Not Working
Rosie: Folder isn't perfectly resized in landscape
Rosie: Mail widget is force closing
Weather: Weather animation in landscape mode broken
Weather :Full screen weather animation broken
Camera: Not all effects are working
You tell us
Screenshots:
Devices Supported:
Desire Z / G2
Desire HD
Inspire 4G
My Touch 4G
Desire S
Incredible S
My Touch 4G Slide
Incredible 2
Credits and Acknowledgements
Virtuous Team - For an amazing rom
Bangincrazy – For testing on MT4G
lowveld – For pointing us in the right direction to fix WiFi
Football – For the RUU
xvicdice – For music playback fix
Download Link:Bug Tracker
Since you made a link here I'll go ahead and attach some stuff.
Wifi, Data, Music Player working.
Camera works rather nicely in both default app and third party apps (instagram etc)
Attached are some screen shot with the default camera app, actually doing special effects smoothly in live preview.
It's a bit slow, especially if you're multitasking, but I'm impressed with how far they got with the camera.
When initially setting up, the setup stage can seem painfully slow (i.e.: on screen keyboard taking a sec or two to register a key, or the next/confirm dialog taking just as long).
Also wake by trackpad doesn't work even though the option is there.
The power menu requires a longer than normal long-press to activate (noticed this when getting the screenshots).
Also Infinity appears to install some apps to the SD Card via it's own custom folder (screen shot also attached).
by the way in terms of 'not all effects', I haven't come across a single effect on the list of effects that didn't seem to crash (maybe not rendered, but didn't die either).
I've switched back to EliteMod in the meantime (normal working hours have approached), I haven't had much time to test extensively how multitasking behaves (i.e.: Facebook, twitter, etc) or any graphical type of games etc.
The free ram at just bout any time is around 10MB, and uptime showing loads around 5.0 on average. The launcher can lag a bit on redraw even if you got the device clocked to 1400mhz (I believe it's more a ram issue than anything, so between supercharger V6 and swap, it might be bearable.)
---------- Post added at 08:07 AM ---------- Previous post was at 08:05 AM ----------
Oh also adb connectivity is somewhat glitchy. Devices never showed up during the initial boot, and had to mess with the power menu a couple of times (between charge only, HTC sync, and disk) to get it to show up and be able to do stuff with adb shell. Switching between various USB modes tends to be laggy.
Though one nice thing about the preview is that I did not receive a single force close or crash, just lags, and some functionality not occurring at all (i.e.: trackpad wake, FM radio).
Desire HD (ace), Desire Z (vision), Inspire 4G bugs
When phone goes into sleep you need to make a long press of the power button to wake it up
Mic doesn't work in some apps like Voice Search, Soundhound, ...
Camera isn't working on some phones
Camcorder only works with disabling sound in the video settings
I have a funny feeling it's going to turn into a bit of a 'can you port Sense Camera to XXX ICS Rom?', when it was the other way around.
FM Radio appears to be broken on both the included FM app, and the FM Radio Widget.
Though fine with SpiritFM Free Edition (which of course requests root permission).
Also the stock FM Radio app, seems to never turn off, it's always "Turning Off", and when the dialog does go away, it's still "On" (showing the icon in the status bar)
How's video recording, 720p?
The above mention of 10MB of free RAM is scaring me away from trying it though. Hell with CM7 as soon as it hits 70MB's, I feel like its lagging too much.
Tried some games with this, with supercharger, swap and 1.4ghz o/c:
Temple Run: Without swap it closes immediately, with swap its getting huge lags while playing, but when theres no lags its smoother then previous kernels.
Death Rally: Smooth as s..t.
Helicopter 3D: Smooth as f..k.
these games rather heavy considering their 3d natures. so its a good thing that this rom can run them smoothly.
generally speaking, if you make this your dd, it will drive you crazy time to time because the interface is slower then most of the roms out there. hope it will get better tho.
edit: with swap and supercharge i get 100-120 mb free ram ( at least it shows that way on the task manager)
boost3d23 said:
How's video recording, 720p?
The above mention of 10MB of free RAM is scaring me away from trying it though. Hell with CM7 as soon as it hits 70MB's, I feel like its lagging too much.
Click to expand...
Click to collapse
I find this pretty common of just about every ICS rom though (mostly cached it would seem). i.e.: free ram is wasted ram.
I'll try out the video soon as TiB does some app restores (I kind of doubt it's full 720, but maybe it'll surprise me).
---------- Post added at 10:15 AM ---------- Previous post was at 10:13 AM ----------
By the way home screen lag ain't so bad once you replace HTC Sense with the Apex Launcher (though I guess some people want the whole experience )
---------- Post added at 10:24 AM ---------- Previous post was at 10:15 AM ----------
720p is Selectable (though 1080p is also shown, obviously won't record at that though), however when you finish recording and had audio turned on, it's the forever-saving-video issue.
With audio off... did saving video for a while, and then force closed, and also a very funky buffer issue (like the screen split in half and scrolled up while recording.
The result from both are files with thumbnails with exclamation marks.
Now if I set the Video quality to 800x480 Wide (default), and audio off, it saves fine.
I respect your work.I'm about to try.
Can't even get it working it lag badly after the setup and hot reboot more than 6 times =\ anyway,good job to them as they get the camera working make me looking forward for updates XD
Sent from my Desire Z using xda app-developers app
Steven How said:
Can't even get it working it lag badly after the setup and hot reboot more than 6 times =\
Sent from my Desire Z using xda app-developers app
Click to expand...
Click to collapse
Would help if your hboot/radio/etc info was in your signature
kbeezie said:
Would help if your hboot/radio/etc info was in your signature
Click to expand...
Click to collapse
Ah...I forget abt radio and all those... does it effect the performance? And I'm using a Italian dz not g2
Sent from my Desire Z using xda app-developers app
Steven How said:
Ah...I forget abt radio and all those... does it effect the performance? And I'm using a Italian dz not g2
Sent from my Desire Z using xda app-developers app
Click to expand...
Click to collapse
As long as it's a DZ hboot it should be fine (i.e.: because the G2 hboot only has a ~400MB /system which is way too small, as this preview takes up about 96% of /system on DZ hboot).
Also depending on what rom you're coming from (i.e.: /system, etc may still be formatted as ext3 instead of ext4).
And far as radio... I don't know if this requires 26.13.04.19 or equivalent.
I guess if you can attempt a logcat output, might be helpful to someone who knows how to read those things.
kbeezie said:
As long as it's a DZ hboot it should be fine (i.e.: because the G2 hboot only has a ~400MB /system which is way too small, as this preview takes up about 96% of /system on DZ hboot).
Also depending on what rom you're coming from (i.e.: /system, etc may still be formatted as ext3 instead of ext4).
And far as radio... I don't know if this requires 26.13.04.19 or equivalent.
I guess if you can attempt a logcat output, might be helpful to someone who knows how to read those things.
Click to expand...
Click to collapse
I'm using 4ext recovery and I only left 20mb in my system space..I have restore back to ARHD 6.3.3.. until infinity become more rock stable perhaps? hope so
Sent from my Desire Z using xda app-developers app
Steven How said:
I'm using 4ext recovery and I only left 20mb in my system space..I have restore back to ARHD 6.3.3.. until infinity become more rock stable perhaps? hope so
Sent from my Desire Z using xda app-developers app
Click to expand...
Click to collapse
Hence why it NEEDs the DZ hboot
it is an alpha/preview
I enabled swap with this script http://dl.dropbox.com/u/1169731/swap_enabler.sh (ie: pop it on /data/local/tmp, chmod 775 , run it, reboot). So will see how SD-swap helps it.
I would remove some unesacary apps from the Rom to free up space
Sent from my HTC Sensation 4G using xda premium
I DO know how to enable swap lol, but it still lag badly.. after opening an app it hang there and finally reboot...lol I understand it's an alpha build so I'm not that demanding for the best performance for now
Sent from my Desire Z using xda app-developers app
evilcuber said:
I would remove some unesacary apps from the Rom to free up space
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
Seems kind of pointless since the /system partition isn't normally going to change after installation. So removing those apps from /system doesn't really give you much benefits in 'freeing up space'. If it were on /data/app that'd be a different story, but it's pretty light in that department upon start.
Now you *could* disable some system apps (if it won't break anything) to improve some degree of performance, but then again what would be the point of testing/previewing if you didn't take it as is.
---------- Post added at 11:26 AM ---------- Previous post was at 11:15 AM ----------
So with 128MB swap on, overall it does seem smoother. However for any *new* item, there can be occasional freezes for a few seconds, in which time I'll notice the swap usage (via adb shell) will jump 20-30MB at a time, eventually once the phone has unfrozen it'll be quite smooth after that. In the last 3 freezes I've jumped from about 30MB to 60MB to 96MB.
Right now it's down to 87MB after about a minute since the last freeze (added a power widget to the desktop, taped the brightness, froze for about 15-20 seconds, changed the brightness, was smooth after that).
Also I'm not using the launcher that came with it, but rather Apex Pro and fancy widgets.
current memory usage, uptime and top:
Code:
[email protected]:/ # free
total used free shared buffers
Mem: 370420 360300 10120 0 600
-/+ buffers: 359700 10720
Swap: 131580 88232 43348
[email protected]:/ # uptime
15:25:04 up 34 min, load average: 2.69, 3.22, 3.40
Code:
Mem: 360772K used, 9648K free, 0K shrd, 1020K buff, 57144K cached
CPU0: 5.7% usr 5.7% sys 0.0% nic 88.4% idle 0.0% io 0.0% irq 0.0% sirq
Load average: 2.18 2.93 3.29 2/680 8348
PID PPID USER STAT VSZ %MEM CPU %CPU COMMAND
316 104 1000 S 425m117.2 0 2.3 com.android.systemui
209 104 1000 S 403m111.3 0 1.1 system_server
7173 104 10148 S 378m104.5 0 0.0 com.facebook.katana
421 104 10165 S 373m103.0 0 0.0 com.anddoes.launcher
467 104 10141 S 372m102.7 0 0.0 com.htc.idlescreen.shortcut
513 104 10018 S 351m 97.0 0 0.0 android.process.acore
3783 104 10017 S 334m 92.2 0 1.1 com.google.process.gapps
501 104 1001 S 329m 91.0 0 2.3 com.android.phone
760 104 9999 S 322m 89.0 0 0.0 com.htc.launcher
7847 104 1000 S 313m 86.4 0 0.0 com.android.settings:remote
1323 104 10018 S 310m 85.6 0 0.0 com.android.htccontacts
482 104 10163 S 310m 85.5 0 0.0 com.touchtype.swiftkey
7394 104 10106 S 309m 85.3 0 0.0 com.android.mms
7882 104 10017 S 301m 83.0 0 0.0 com.google.android.gsf.login
8235 104 10014 S 301m 83.0 0 0.0 com.htc.calendar
8192 104 10014 S 301m 83.0 0 0.0 com.htc.bg
8163 104 9996 S 300m 82.9 0 0.0 com.htc.notes
7862 104 10153 S 300m 82.8 0 0.0 com.google.android.googlequicksear
8214 104 10146 S 300m 82.7 0 0.0 com.dropbox.android
5568 104 10162 S 298m 82.3 0 0.0 com.mhuang.overclocking.ProfilesSe
kbeezie said:
Seems kind of pointless since the /system partition isn't normally going to change after installation. So removing those apps from /system doesn't really give you much benefits in 'freeing up space'. If it were on /data/app that'd be a different story, but it's pretty light in that department upon start.
Now you *could* disable some system apps (if it won't break anything) to improve some degree of performance, but then again what would be the point of testing/previewing if you didn't take it as is.
---------- Post added at 11:26 AM ---------- Previous post was at 11:15 AM ----------
So with 128MB swap on, overall it does seem smoother. However for any *new* item, there can be occasional freezes for a few seconds, in which time I'll notice the swap usage (via adb shell) will jump 20-30MB at a time, eventually once the phone has unfrozen it'll be quite smooth after that. In the last 3 freezes I've jumped from about 30MB to 60MB to 96MB.
Right now it's down to 87MB after about a minute since the last freeze (added a power widget to the desktop, taped the brightness, froze for about 15-20 seconds, changed the brightness, was smooth after that).
Also I'm not using the launcher that came with it, but rather Apex Pro and fancy widgets.
current memory usage, uptime and top:
Code:
[email protected]:/ # free
total used free shared buffers
Mem: 370420 360300 10120 0 600
-/+ buffers: 359700 10720
Swap: 131580 88232 43348
[email protected]:/ # uptime
15:25:04 up 34 min, load average: 2.69, 3.22, 3.40
Code:
Mem: 360772K used, 9648K free, 0K shrd, 1020K buff, 57144K cached
CPU0: 5.7% usr 5.7% sys 0.0% nic 88.4% idle 0.0% io 0.0% irq 0.0% sirq
Load average: 2.18 2.93 3.29 2/680 8348
PID PPID USER STAT VSZ %MEM CPU %CPU COMMAND
316 104 1000 S 425m117.2 0 2.3 com.android.systemui
209 104 1000 S 403m111.3 0 1.1 system_server
7173 104 10148 S 378m104.5 0 0.0 com.facebook.katana
421 104 10165 S 373m103.0 0 0.0 com.anddoes.launcher
467 104 10141 S 372m102.7 0 0.0 com.htc.idlescreen.shortcut
513 104 10018 S 351m 97.0 0 0.0 android.process.acore
3783 104 10017 S 334m 92.2 0 1.1 com.google.process.gapps
501 104 1001 S 329m 91.0 0 2.3 com.android.phone
760 104 9999 S 322m 89.0 0 0.0 com.htc.launcher
7847 104 1000 S 313m 86.4 0 0.0 com.android.settings:remote
1323 104 10018 S 310m 85.6 0 0.0 com.android.htccontacts
482 104 10163 S 310m 85.5 0 0.0 com.touchtype.swiftkey
7394 104 10106 S 309m 85.3 0 0.0 com.android.mms
7882 104 10017 S 301m 83.0 0 0.0 com.google.android.gsf.login
8235 104 10014 S 301m 83.0 0 0.0 com.htc.calendar
8192 104 10014 S 301m 83.0 0 0.0 com.htc.bg
8163 104 9996 S 300m 82.9 0 0.0 com.htc.notes
7862 104 10153 S 300m 82.8 0 0.0 com.google.android.googlequicksear
8214 104 10146 S 300m 82.7 0 0.0 com.dropbox.android
5568 104 10162 S 298m 82.3 0 0.0 com.mhuang.overclocking.ProfilesSe
Click to expand...
Click to collapse
This rom didn't come with virtuous oc?
Sent from my Desire Z using xda app-developers app
Brief background on the idea. I was originally inspired by soniCron and their work with the SD808. I created a custom profile for my LG G4, which allowed me to get more SOT.
>
Suggestions for the Advanced section in EX Kernel Manager:
sched_upmigrate_min_nice = 0
sched_upmigrate = 95
sched_restrict_cluster_spill = 1
sched_downmigrate = 65
Under Misc, enable "wq_power_saving" too.
>
What's Required
1. Root
2. Kernel tuner app (Preferrably EX Kernel manager, as it can use the profiles, otherwise you need to input them manually)
3. Interactive Governor for both clusters
>
Steps
1. Download a profile
2. Unzip it, put the file (not folder) into the EX Kernel directory for profiles
(/ElementalX/gov_profiles)
3. Alternatively, put the values yourself if using a different app such as Kernel Auditor
>
Profiles
Bifrost v1: Tries to keep the frequencies low, avoids aggressive ramping up to the max freq on either cluster
View attachment Bifrost.zip
Bifrost v6
View attachment Bifrost_v6.zip
Beast Mode v1: Performance profile
View attachment Beast_Mode.zip
>
Manual Input
Bifrost v1:
/sys/devices/system/cpu/cpu0/cpufreq/interactive/go_hispeed_load 98
/sys/devices/system/cpu/cpu0/cpufreq/interactive/above_hispeed_delay 0
/sys/devices/system/cpu/cpu0/cpufreq/interactive/hispeed_freq_hysteresis 0
/sys/devices/system/cpu/cpu0/cpufreq/interactive/timer_rate 250000
/sys/devices/system/cpu/cpu0/cpufreq/interactive/hispeed_freq 537600
/sys/devices/system/cpu/cpu0/cpufreq/interactive/timer_slack 384000
/sys/devices/system/cpu/cpu0/cpufreq/interactive/target_loads 85 307200:39 384000:55 460000:64 537600:69 614400:74 768000:78 864000:81 902000:84 979200:87 1056000:90 1132800:91 1209600:92 1286400:93 1362000:94 1440000:95 1516800:98 1593600:99
/sys/devices/system/cpu/cpu0/cpufreq/interactive/min_sample_time 0
/sys/devices/system/cpu/cpu0/cpufreq/interactive/ignore_hispeed_on_notif 1
/sys/devices/system/cpu/cpu0/cpufreq/interactive/boost 0
/sys/devices/system/cpu/cpu0/cpufreq/interactive/fast_ramp_down 1
/sys/devices/system/cpu/cpu0/cpufreq/interactive/align_windows 1
/sys/devices/system/cpu/cpu0/cpufreq/interactive/use_migration_notif 1
/sys/devices/system/cpu/cpu0/cpufreq/interactive/use_sched_load 0
/sys/devices/system/cpu/cpu0/cpufreq/interactive/is_skip_max_logic 0
/sys/devices/system/cpu/cpu0/cpufreq/interactive/max_freq_hysteresis 0
/sys/devices/system/cpu/cpu0/cpufreq/interactive/boostpulse_duration 0
(Big cluster)
/sys/devices/system/cpu/cpu2/cpufreq/interactive/go_hispeed_load 99
/sys/devices/system/cpu/cpu2/cpufreq/interactive/above_hispeed_delay 60000 700000:70000 800000:80000 1000000:100000 1400000:140000 1500000:150000 1700000:170000 1800000:180000 1900000:190000 2100000:200000 2200000:220000 2300000:230000
/sys/devices/system/cpu/cpu2/cpufreq/interactive/hispeed_freq_hysteresis 0
/sys/devices/system/cpu/cpu2/cpufreq/interactive/timer_rate 480000
/sys/devices/system/cpu/cpu2/cpufreq/interactive/hispeed_freq 460800
/sys/devices/system/cpu/cpu2/cpufreq/interactive/timer_slack 384000
/sys/devices/system/cpu/cpu2/cpufreq/interactive/target_loads 95 307200:28 384000:33 480000:41 537600:46 614400:51 748800:58 825600:62 902400:67 1056000:70 1132800:72 1209600:74 1286400:76 1363200:78 1440000:80 1516800:82 1593600:85 1670400:87 1747200:89 1824000:92 1900800:94 1977600:96 2054400:97 2150400:98 2246400:99 2342400:100
/sys/devices/system/cpu/cpu2/cpufreq/interactive/min_sample_time 20000
/sys/devices/system/cpu/cpu2/cpufreq/interactive/ignore_hispeed_on_notif 1
/sys/devices/system/cpu/cpu2/cpufreq/interactive/boost 0
/sys/devices/system/cpu/cpu2/cpufreq/interactive/fast_ramp_down 1
/sys/devices/system/cpu/cpu2/cpufreq/interactive/align_windows 0
/sys/devices/system/cpu/cpu2/cpufreq/interactive/use_migration_notif 1
/sys/devices/system/cpu/cpu2/cpufreq/interactive/use_sched_load 1
/sys/devices/system/cpu/cpu2/cpufreq/interactive/is_skip_max_logic 0
/sys/devices/system/cpu/cpu2/cpufreq/interactive/max_freq_hysteresis 0
/sys/devices/system/cpu/cpu2/cpufreq/interactive/boostpulse_duration 0
Bifrost v6:
(small cluster)
/sys/devices/system/cpu/cpu0/cpufreq/interactive/go_hispeed_load 99
/sys/devices/system/cpu/cpu0/cpufreq/interactive/above_hispeed_delay 0
/sys/devices/system/cpu/cpu0/cpufreq/interactive/hispeed_freq_hysteresis 0
/sys/devices/system/cpu/cpu0/cpufreq/interactive/timer_rate 250000
/sys/devices/system/cpu/cpu0/cpufreq/interactive/hispeed_freq 460800
/sys/devices/system/cpu/cpu0/cpufreq/interactive/timer_slack 384000
/sys/devices/system/cpu/cpu0/cpufreq/interactive/target_loads 95 307200:35 384000:45 460000:55 537600:61 614400:66 768000:71 864000:76 902000:81 979200:86 1056000:90 1132800:91 1209600:92 1286400:93 1362000:94 1440000:96 1516800:98 1593600:99
/sys/devices/system/cpu/cpu0/cpufreq/interactive/min_sample_time 10000
/sys/devices/system/cpu/cpu0/cpufreq/interactive/ignore_hispeed_on_notif 1
/sys/devices/system/cpu/cpu0/cpufreq/interactive/boost 0
/sys/devices/system/cpu/cpu0/cpufreq/interactive/fast_ramp_down 1
/sys/devices/system/cpu/cpu0/cpufreq/interactive/align_windows 1
/sys/devices/system/cpu/cpu0/cpufreq/interactive/use_migration_notif 1
/sys/devices/system/cpu/cpu0/cpufreq/interactive/use_sched_load 0
/sys/devices/system/cpu/cpu0/cpufreq/interactive/is_skip_max_logic 0
/sys/devices/system/cpu/cpu0/cpufreq/interactive/max_freq_hysteresis 0
/sys/devices/system/cpu/cpu0/cpufreq/interactive/boostpulse_duration 0
(big cluster)
/sys/devices/system/cpu/cpu2/cpufreq/interactive/go_hispeed_load 200
/sys/devices/system/cpu/cpu2/cpufreq/interactive/above_hispeed_delay 40000 537600:60000 748800:80000 1056000:110000 1286400:140000 1440000:170000 1747200:200000 1900800:220000 2150400:250000 2342400:270000
/sys/devices/system/cpu/cpu2/cpufreq/interactive/hispeed_freq_hysteresis 0
/sys/devices/system/cpu/cpu2/cpufreq/interactive/timer_rate 200000
/sys/devices/system/cpu/cpu2/cpufreq/interactive/hispeed_freq 460800
/sys/devices/system/cpu/cpu2/cpufreq/interactive/timer_slack 384000
/sys/devices/system/cpu/cpu2/cpufreq/interactive/target_loads 95 307200:28 384000:33 480000:41 537600:46 614400:51 748800:58 825600:62 902400:67 1056000:70 1132800:72 1209600:74 1286400:76 1363200:78 1440000:80 1516800:82 1593600:85 1670400:87 1747200:89 1824000:92 1900800:94 1977600:96 2054400:97 2150400:98 2246400:99 2342400:100
/sys/devices/system/cpu/cpu2/cpufreq/interactive/min_sample_time 10000
/sys/devices/system/cpu/cpu2/cpufreq/interactive/ignore_hispeed_on_notif 1
/sys/devices/system/cpu/cpu2/cpufreq/interactive/boost 0
/sys/devices/system/cpu/cpu2/cpufreq/interactive/fast_ramp_down 1
/sys/devices/system/cpu/cpu2/cpufreq/interactive/align_windows 0
/sys/devices/system/cpu/cpu2/cpufreq/interactive/use_migration_notif 1
/sys/devices/system/cpu/cpu2/cpufreq/interactive/use_sched_load 1
/sys/devices/system/cpu/cpu2/cpufreq/interactive/is_skip_max_logic 0
/sys/devices/system/cpu/cpu2/cpufreq/interactive/max_freq_hysteresis 0
/sys/devices/system/cpu/cpu2/cpufreq/interactive/boostpulse_duration 0
Beast v1:
/sys/devices/system/cpu/cpu0/cpufreq/interactive/go_hispeed_load 200
/sys/devices/system/cpu/cpu0/cpufreq/interactive/above_hispeed_delay 0
/sys/devices/system/cpu/cpu0/cpufreq/interactive/hispeed_freq_hysteresis 0
/sys/devices/system/cpu/cpu0/cpufreq/interactive/timer_rate 50000
/sys/devices/system/cpu/cpu0/cpufreq/interactive/hispeed_freq 768000
/sys/devices/system/cpu/cpu0/cpufreq/interactive/timer_slack -1
/sys/devices/system/cpu/cpu0/cpufreq/interactive/target_loads 80 307200:25 384000:38 460000:46 537600:50 614400:54 768000:58 864000:62 902000:65 979200:70 1056000:80 1132800:85 1209600:89 1286400:92 1362000:94 1440000:96 1516800:98 1593600:99 2188800:100
/sys/devices/system/cpu/cpu0/cpufreq/interactive/min_sample_time 0
/sys/devices/system/cpu/cpu0/cpufreq/interactive/ignore_hispeed_on_notif 1
/sys/devices/system/cpu/cpu0/cpufreq/interactive/boost 0
/sys/devices/system/cpu/cpu0/cpufreq/interactive/fast_ramp_down 0
/sys/devices/system/cpu/cpu0/cpufreq/interactive/align_windows 1
/sys/devices/system/cpu/cpu0/cpufreq/interactive/use_migration_notif 1
/sys/devices/system/cpu/cpu0/cpufreq/interactive/use_sched_load 0
/sys/devices/system/cpu/cpu0/cpufreq/interactive/is_skip_max_logic 0
/sys/devices/system/cpu/cpu0/cpufreq/interactive/max_freq_hysteresis 0
/sys/devices/system/cpu/cpu0/cpufreq/interactive/boostpulse_duration 0
/sys/devices/system/cpu/cpu2/cpufreq/interactive/go_hispeed_load 200
/sys/devices/system/cpu/cpu2/cpufreq/interactive/above_hispeed_delay 0
/sys/devices/system/cpu/cpu2/cpufreq/interactive/hispeed_freq_hysteresis 0
/sys/devices/system/cpu/cpu2/cpufreq/interactive/timer_rate 40000
/sys/devices/system/cpu/cpu2/cpufreq/interactive/hispeed_freq 825600
/sys/devices/system/cpu/cpu2/cpufreq/interactive/timer_slack -1
/sys/devices/system/cpu/cpu2/cpufreq/interactive/target_loads 90 307200:28 384000:30 480000:40 537600:45 614400:60 748800:65 825600:69 902400:70 1056000:72 1132800:74 1209600:76 1286400:77 1363200:78 1440000:80 1516800:82 1593600:85 1670400:87 1747200:89 1824000:92 1900800:94 1977600:96 2054400:97 2150400:98 2246400:99 2342400:100
/sys/devices/system/cpu/cpu2/cpufreq/interactive/min_sample_time 20000
/sys/devices/system/cpu/cpu2/cpufreq/interactive/ignore_hispeed_on_notif 1
/sys/devices/system/cpu/cpu2/cpufreq/interactive/boost 0
/sys/devices/system/cpu/cpu2/cpufreq/interactive/fast_ramp_down 0
/sys/devices/system/cpu/cpu2/cpufreq/interactive/align_windows 0
/sys/devices/system/cpu/cpu2/cpufreq/interactive/use_migration_notif 1
/sys/devices/system/cpu/cpu2/cpufreq/interactive/use_sched_load 1
/sys/devices/system/cpu/cpu2/cpufreq/interactive/is_skip_max_logic 0
/sys/devices/system/cpu/cpu2/cpufreq/interactive/max_freq_hysteresis 0
/sys/devices/system/cpu/cpu2/cpufreq/interactive/boostpulse_duration 0
>
Benchmarks (Beast v1 & Bifrost v1 compared)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Honestly, I find it strange that you are claiming 11+ SOT when the actual usage is very low. What sorts of activities did you do over those 11 hours period? I am guessing more standby time and just glancing at notifications, email etc? 11 hours period should maximize the battery capacity of Le Pro 3 so we should be seeing at least 3500+ computed power usage here.
Here is a typical medium usage on the Le Pro 3 and its SOT.
Joms_US said:
Honestly, I find it strange that you are claiming 11+ SOT when the actual usage is very low. What sorts of activities did you do over those 11 hours period? I am guessing more standby time and just glancing at notifications, email etc? 11 hours period should maximize the battery capacity of Le Pro 3 so we should be seeing at least 3500+ computed power usage here.
Here is a typical medium usage on the Le Pro 3 and its SOT.
Click to expand...
Click to collapse
Voice calls, messaging (Textra or kik), Feedly, mail (Inbox+Alto), browsing (Opera Mini & CS Beta), ~20-30mins YouTube, XDA app, updating apps, various shopping apps (Amazon, eBay, etc), and Google Keep for notes/to-do list. Sometimes I might take a few pictures, but no video recording. Do I play games? Yes, but not often. I have quite a few intensive games. Again, I'll update the post with recent stats.
Edit: If you check the original thread by soniCron you'll see that many users have seen the benefit of using a custom profile.
Ace42 said:
Voice calls, messaging (Textra or kik), Feedly, mail (Inbox+Alto), browsing (Opera Mini & CS Beta), ~20-30mins YouTube, XDA app, updating apps, various shopping apps (Amazon, eBay, etc), and Google Keep for notes/to-do list. Sometimes I might take a few pictures, but no video recording. Do I play games? Yes, but not often. I have quite a few intensive games. Again, I'll update the post with recent stats.
Edit: If you check the original thread by soniCron you'll see that many users have seen the benefit of using a custom profile.
Click to expand...
Click to collapse
Would you please charge it at 100% and run PCMark Work Battery Life? This will be a very good indicator on how effective your profile is. Set the display brightness to about 40% (200 nits) TIA
If you want to try more profiles there is a HUUUUGE thread over at OP3 forums. Lots of profiles. As a OP3 owner I can tell you that these profiles do make a difference. I wish we can get a custom kernel that lets us turn off input boost so we can save more power with these profiles.
https://forum.xda-developers.com/oneplus-3/how-to/advanced-interactive-governor-tweaks-t3476589
Joms_US said:
Would you please charge it at 100% and run PCMark Work Battery Life? This will be a very good indicator on how effective your profile is. Set the display brightness to about 40% (200 nits) TIA
Click to expand...
Click to collapse
Sure. I'll compare both profiles to see if there's a difference.
Tikerz said:
If you want to try more profiles there is a HUUUUGE thread over at OP3 forums. Lots of profiles. As a OP3 owner I can tell you that these profiles do make a difference. I wish we can get a custom kernel that lets us turn off input boost so we can save more power with these profiles.
https://forum.xda-developers.com/oneplus-3/how-to/advanced-interactive-governor-tweaks-t3476589
Click to expand...
Click to collapse
The frequency table is a bit different from the OP3.
Ace42 said:
Brief background on the idea. I was originally inspired by soniCron and their work with the SD808. I created a custom profile for my LG G4, which allowed me to get 6-7hrs SOT using interactive.
Now, I have a Pro 3, which uses the SD821. I've been doing various battery related tests on this phone too. The highest SOT I've seen on this phone was nearly 12hrs by using less than the battery's full capacity (strictly use 90-20%, equating to 70% of the capacity. Imagine 13-14+ with a full discharge). I can't promise that the experience will be the same for you, but my screenshots basically show the effectiveness of custom parameters.
So far I've focused on a battery efficient profile, as I don't care as much about having the best performance. However, I will create a perf profile by testing it with games later on.
>
What's Required
1. Root
2. Kernel tuner app (Preferrably EX Kernel manager, as it can use the profiles, otherwise you need to input them manually)
3. Interactive Governor for both clusters
4. MUST disable touchboost (Don't know if any app besides EX has this feature YMMV)
>
Steps
1. Download a profile
2. Unzip it, put the file (not folder) into the EX Kernel directory for profiles
(/ElementalX/gov_profiles)
3. Alternatively, put the values yourself if using a different app such as Kernel Auditor
>
Profiles
Bifrost v1: Tries to keep the frequencies low, avoids aggressive ramping up to the max freq on either cluster
View attachment 3992868
Beast Mode v1: Performance profile
View attachment 3992995
>
Manual Input
Bifrost:
/sys/devices/system/cpu/cpu0/cpufreq/interactive/go_hispeed_load 98
/sys/devices/system/cpu/cpu0/cpufreq/interactive/above_hispeed_delay 0
/sys/devices/system/cpu/cpu0/cpufreq/interactive/hispeed_freq_hysteresis 0
/sys/devices/system/cpu/cpu0/cpufreq/interactive/timer_rate 250000
/sys/devices/system/cpu/cpu0/cpufreq/interactive/hispeed_freq 537600
/sys/devices/system/cpu/cpu0/cpufreq/interactive/timer_slack 384000
/sys/devices/system/cpu/cpu0/cpufreq/interactive/target_loads 85 307200:39 384000:55 460000:64 537600:69 614400:74 768000:78 864000:81 902000:84 979200:87 1056000:90 1132800:91 1209600:92 1286400:93 1362000:94 1440000:95 1516800:98 1593600:99
/sys/devices/system/cpu/cpu0/cpufreq/interactive/min_sample_time 0
/sys/devices/system/cpu/cpu0/cpufreq/interactive/ignore_hispeed_on_notif 1
/sys/devices/system/cpu/cpu0/cpufreq/interactive/boost 0
/sys/devices/system/cpu/cpu0/cpufreq/interactive/fast_ramp_down 1
/sys/devices/system/cpu/cpu0/cpufreq/interactive/align_windows 1
/sys/devices/system/cpu/cpu0/cpufreq/interactive/use_migration_notif 1
/sys/devices/system/cpu/cpu0/cpufreq/interactive/use_sched_load 0
/sys/devices/system/cpu/cpu0/cpufreq/interactive/is_skip_max_logic 0
/sys/devices/system/cpu/cpu0/cpufreq/interactive/max_freq_hysteresis 0
/sys/devices/system/cpu/cpu0/cpufreq/interactive/boostpulse_duration 0
(Big cluster)
/sys/devices/system/cpu/cpu2/cpufreq/interactive/go_hispeed_load 99
/sys/devices/system/cpu/cpu2/cpufreq/interactive/above_hispeed_delay 60000 700000:70000 800000:80000 1000000:100000 1400000:140000 1500000:150000 1700000:170000 1800000:180000 1900000:190000 2100000:200000 2200000:220000 2300000:230000
/sys/devices/system/cpu/cpu2/cpufreq/interactive/hispeed_freq_hysteresis 0
/sys/devices/system/cpu/cpu2/cpufreq/interactive/timer_rate 480000
/sys/devices/system/cpu/cpu2/cpufreq/interactive/hispeed_freq 460800
/sys/devices/system/cpu/cpu2/cpufreq/interactive/timer_slack 384000
/sys/devices/system/cpu/cpu2/cpufreq/interactive/target_loads 95 307200:28 384000:33 480000:41 537600:46 614400:51 748800:58 825600:62 902400:67 1056000:70 1132800:72 1209600:74 1286400:76 1363200:78 1440000:80 1516800:82 1593600:85 1670400:87 1747200:89 1824000:92 1900800:94 1977600:96 2054400:97 2150400:98 2246400:99 2342400:100
/sys/devices/system/cpu/cpu2/cpufreq/interactive/min_sample_time 20000
/sys/devices/system/cpu/cpu2/cpufreq/interactive/ignore_hispeed_on_notif 1
/sys/devices/system/cpu/cpu2/cpufreq/interactive/boost 0
/sys/devices/system/cpu/cpu2/cpufreq/interactive/fast_ramp_down 1
/sys/devices/system/cpu/cpu2/cpufreq/interactive/align_windows 0
/sys/devices/system/cpu/cpu2/cpufreq/interactive/use_migration_notif 1
/sys/devices/system/cpu/cpu2/cpufreq/interactive/use_sched_load 1
/sys/devices/system/cpu/cpu2/cpufreq/interactive/is_skip_max_logic 0
/sys/devices/system/cpu/cpu2/cpufreq/interactive/max_freq_hysteresis 0
/sys/devices/system/cpu/cpu2/cpufreq/interactive/boostpulse_duration 0
Beast:
/sys/devices/system/cpu/cpu0/cpufreq/interactive/go_hispeed_load 200
/sys/devices/system/cpu/cpu0/cpufreq/interactive/above_hispeed_delay 0
/sys/devices/system/cpu/cpu0/cpufreq/interactive/hispeed_freq_hysteresis 0
/sys/devices/system/cpu/cpu0/cpufreq/interactive/timer_rate 50000
/sys/devices/system/cpu/cpu0/cpufreq/interactive/hispeed_freq 768000
/sys/devices/system/cpu/cpu0/cpufreq/interactive/timer_slack -1
/sys/devices/system/cpu/cpu0/cpufreq/interactive/target_loads 80 307200:25 384000:38 460000:46 537600:50 614400:54 768000:58 864000:62 902000:65 979200:70 1056000:80 1132800:85 1209600:89 1286400:92 1362000:94 1440000:96 1516800:98 1593600:99 2188800:100
/sys/devices/system/cpu/cpu0/cpufreq/interactive/min_sample_time 0
/sys/devices/system/cpu/cpu0/cpufreq/interactive/ignore_hispeed_on_notif 1
/sys/devices/system/cpu/cpu0/cpufreq/interactive/boost 0
/sys/devices/system/cpu/cpu0/cpufreq/interactive/fast_ramp_down 0
/sys/devices/system/cpu/cpu0/cpufreq/interactive/align_windows 1
/sys/devices/system/cpu/cpu0/cpufreq/interactive/use_migration_notif 1
/sys/devices/system/cpu/cpu0/cpufreq/interactive/use_sched_load 0
/sys/devices/system/cpu/cpu0/cpufreq/interactive/is_skip_max_logic 0
/sys/devices/system/cpu/cpu0/cpufreq/interactive/max_freq_hysteresis 0
/sys/devices/system/cpu/cpu0/cpufreq/interactive/boostpulse_duration 0
/sys/devices/system/cpu/cpu2/cpufreq/interactive/go_hispeed_load 200
/sys/devices/system/cpu/cpu2/cpufreq/interactive/above_hispeed_delay 0
/sys/devices/system/cpu/cpu2/cpufreq/interactive/hispeed_freq_hysteresis 0
/sys/devices/system/cpu/cpu2/cpufreq/interactive/timer_rate 40000
/sys/devices/system/cpu/cpu2/cpufreq/interactive/hispeed_freq 825600
/sys/devices/system/cpu/cpu2/cpufreq/interactive/timer_slack -1
/sys/devices/system/cpu/cpu2/cpufreq/interactive/target_loads 90 307200:28 384000:30 480000:40 537600:45 614400:60 748800:65 825600:69 902400:70 1056000:72 1132800:74 1209600:76 1286400:77 1363200:78 1440000:80 1516800:82 1593600:85 1670400:87 1747200:89 1824000:92 1900800:94 1977600:96 2054400:97 2150400:98 2246400:99 2342400:100
/sys/devices/system/cpu/cpu2/cpufreq/interactive/min_sample_time 20000
/sys/devices/system/cpu/cpu2/cpufreq/interactive/ignore_hispeed_on_notif 1
/sys/devices/system/cpu/cpu2/cpufreq/interactive/boost 0
/sys/devices/system/cpu/cpu2/cpufreq/interactive/fast_ramp_down 0
/sys/devices/system/cpu/cpu2/cpufreq/interactive/align_windows 0
/sys/devices/system/cpu/cpu2/cpufreq/interactive/use_migration_notif 1
/sys/devices/system/cpu/cpu2/cpufreq/interactive/use_sched_load 1
/sys/devices/system/cpu/cpu2/cpufreq/interactive/is_skip_max_logic 0
/sys/devices/system/cpu/cpu2/cpufreq/interactive/max_freq_hysteresis 0
/sys/devices/system/cpu/cpu2/cpufreq/interactive/boostpulse_duration 0
>
Benchmarks (Bifrost & Beast compared)
View attachment 3992996View attachment 3992997
>
Screenshots
View attachment 3992859View attachment 3992860View attachment 3992861View attachment 3992862
(Taken on 20s EUI, stock. Will put newer ones for LTE/HSPA usage at some point)
Click to expand...
Click to collapse
Sorry i am unable to locate disable touchboost?
Where is it in EX Kernel ?
saraprobe said:
Sorry i am unable to locate disable touchboost?
Where is it in EX Kernel ?
Click to expand...
Click to collapse
It's here. It's located at:
/Sys/module/cpu_boost/parameters
Ace42 said:
Sure. I'll compare both profiles to see if there's a difference.
The frequency table is a bit different from the OP3.
Click to expand...
Click to collapse
We can edit them to suit our SD 821 better.
Tikerz said:
We can edit them to suit our SD 821 better.
Click to expand...
Click to collapse
I know, but I wanted to use the profile I had with my G4 and Flex 2. And I just like testing different configs.
Ace42 said:
It's here. It's located at:
/Sys/module/cpu_boost/parameters
Click to expand...
Click to collapse
That's input boost, we don't want to touch that. That's the configurable part of the profiles.
Touchboost is the one you want to disable but we can't because the stock kernel doesn't give the option.
---------- Post added at 10:41 AM ---------- Previous post was at 10:39 AM ----------
Ace42 said:
I know, but I wanted to use the profile I had with my G4 and Flex 2. And I just like testing different configs.
Click to expand...
Click to collapse
You should try burnout from the OP3 thread.
If we had the option to disable Touchboost it would look like this in EX Kernel Manager. We need a custom kernel badly. You can still play around with these profiles but their full potential wouldn't be realized unless we can disable Touchboost.
Ace42 said:
It's here. It's located at:
/Sys/module/cpu_boost/parameters
Click to expand...
Click to collapse
So turn this on as highlighted
saraprobe said:
So turn this on as highlighted
Click to expand...
Click to collapse
No, don't touch it. That's input boost, not touchboost. See my post above.
Tikerz said:
No, don't touch it. That's input boost, not touchboost. See my post above.
Click to expand...
Click to collapse
No worries. Is that Leeco Le pro 3 or a different phone?
Tikerz said:
If we had the option to disable Touchboost it would look like this in EX Kernel Manager. We need a custom kernel badly. You can still play around with these profiles but their full potential wouldn't be realized unless we can disable Touchboost.
Click to expand...
Click to collapse
The directory for touch boost is present (msm_performance), but the file isn't. I'll still play around with input boost to see if it affects battery significantly, or user experience. The profiles don't actually mess with input boost though.
saraprobe said:
No worries. Is that Leeco Le pro 3 or a different phone?
Click to expand...
Click to collapse
My screenshot is from a different phone.
---------- Post added at 10:53 AM ---------- Previous post was at 10:52 AM ----------
Ace42 said:
The directory for touch boost is present (msm_performance), but the file isn't. I'll still play around with input boost to see if it affects battery significantly, or user experience.
Click to expand...
Click to collapse
So if it's not there does that mean it's off? That would be great. It would mean that Le Eco didn't implement Touchboost in their kernel. So we don't have to worry about turning it off.
Tikerz said:
My screenshot is from a different phone.
---------- Post added at 10:53 AM ---------- Previous post was at 10:52 AM ----------
So if it's not there does that mean it's off?
Click to expand...
Click to collapse
thought so cant find here
---------- Post added at 05:56 PM ---------- Previous post was at 05:54 PM ----------
So boost millisecond on or off?
saraprobe said:
thought so cant find here
---------- Post added at 05:56 PM ---------- Previous post was at 05:54 PM ----------
So boost millisecond on or off?
Click to expand...
Click to collapse
Don't touch anything there. Just load the profile. All the settings you see are from the profile.
Tikerz said:
My screenshot is from a different phone.
---------- Post added at 10:53 AM ---------- Previous post was at 10:52 AM ----------
So if it's not there does that mean it's off? That would be great. It would mean that Le Eco didn't implement Touchboost in their kernel. So we don't have to worry about turning it off.
Click to expand...
Click to collapse
I think it's possible, unless they implemented the feature in another way. Usually the CPU jumps to a high freq with touch boost, but the Pro 3 only changes slightly.