Related
Hello good people of XDA, I am having a bit of an annoying issue with my Cyanogenmod 7.1 "stable" install on my Evo 4G. Tiamat 4.1.0 SBC+ Kernel.
When I run a gps related application like Ulysse speedometer, Google Maps and Navigation, after a seemingly random amount of time the phone crashes and reboots itself. The time that I can use the app may be a few seconds to a few minutes and I havent noticed anything that would help determine the timing issue.
I have been doing a little testing and while running logcat on my PC via ADB, I have pulled the last events that occur immediately before the crash. It seems to me that the issue is more/only likely to occur when the phone is also not connected to a wifi network. Everything works fine when using GPS while connected over wifi.
Is anybody interested in reading through the end of my log file? How should I post it?
Please, any help at all?
sntmods said:
Please, any help at all?
Click to expand...
Click to collapse
I've been having the same problem as you and I think I've figured out a fix for it. I'm on Deck's 1.3 stable (which is essentially CM7.1) with Tiamat 4.1.0 SBC, using the smartass governor (the original one) with a CPU frequency range from 128 MHz to 768 MHz, and undervolted by 100 mV.
I've only encountered the issue sporadically and it's only occurred when using Google Maps or Navigation. I would be using Maps and moving the map around a lot, rotating it, or zooming in and out and all of a sudden the screen would freeze and the phone would reboot after 10 seconds or so. I figured out that I could reproduce the problem by opening up a bunch of apps to get the free memory (RAM) down to about 100 MB, open up Google Music and start streaming a song on the handset speaker, then open up Maps and just move around the map a lot; after less than a minute of doing this, the screen would freeze and the phone would reboot.
I tried uninstalling and reinstalling Maps; wiping the cache, dalvik cache, and fixing permissions; reverting to an older version of Maps (5.10); reversing the undervolting; changing governors; and changing the CPU frequency range; but none of these things fixed the problem.
I noticed that if I tried the Music and Maps crash technique when there was more free RAM (say 150 - 250 MB free), it wouldn't work, so I figured the problem probably had to do with the apps in use not having enough available RAM to operate properly and the default values that Android uses to kill idle apps was set too low. Fortunately, I remembered about Autokiller Memory Optimizer, which allows you to set those values, so that you always have above a certain level of free RAM. First, I tried the “Aggressive” preset (82, 90, 98), which didn’t fix the problem, so I then tried the “Extreme” preset (150, 160, 170) and that fixed it (for a full explanation of what the numbers mean and how the app works, see the Autokiller Memory Optimizer). I tried several different combinations of values between the Aggressive and Extreme presets and finally settled on Hidden app: 110, Content provider: 120, Empty app: 130. I was able to use lower values and still prevent the crash/reboot issue, but I figured I should leave a little buffer room to be safe and the 110, 120, 130 combo seemed low enough to prevent idle apps from being unnecessarily killed.
So, I’m not exactly sure what the root cause of the problem is, but Autokiller Memory Optimizer seems to be a nice workaround to fix the problem.
Well after testing this workaround for some time now, I can say that it doesn't prevent the reboots completely, but it does seem to have decreased their frequency, such that it's only happened one or two times since I started using it. I tried changing the cutoff values for when certain types of apps are killed, but eventually returned to the original levels I went with (Hidden app: 110, Content provider: 120, Empty app: 130) as they seemed to work the best (the one or two reboots that did happened, occurred when I was experimenting with the values).
Hi,
i want to start a discussion with those of you who have such unstable Desires.
I am one of the sad guys having one of them. It seems that there are a few Desires which do not run like all the others.
A typical thing with this Desires are complete freezes of Android. Very often they happen when the screen is off, the phone is idle and recieve a SMS or a Phone call. The phone freezes imediately and you are never informed of the SMS or Call. It is just lost. You just detect that you can not power on your phone and must remove the battery to get it back to life.
I have this starnge freezes with every ROM. Most people do not believe you because they do not have the problems.
I have tried several things till now.
- A new SD Card
- Several ROMS
- Allways full wipe
- Allways format SD card with gparted
- Allways start from scratch without backup of Apps
- Different Kernels
- Delvik internal
- uvm...
But all of this things did not help! It seemed that only i have the Problem and i was thinking its a hardware defekt.
I was searching for a new Android device as i again installed a new ROM and read from someone with the same problems. I also read about the UV capabilities of Deamon Controller.
So i give this a try.
I now have installed AIO 3.0.4 on CM7r2 with x2sd with latest radio and one Ext4 partition. First of all i went to deamon controller and put up the voltages a little bit. And since i have done this my freezes nearly are gone.
I now played around with the settings and it turns out that you must find the right values. To much voltage is not good and to less is also not good.
It seems that there are some CPU's in some desires which are not very stable and do not like the OC / UV.
It would be very nice to know about your expirience with unstable Desires and what you have done to fix this. Perhaps we can also find good values for UV.
Or we can find a mix of things to make this Desires also stable.
Regards
Kai
It's a known issue that too much undervolting or overclocking leads to CPU freezes, or kernel panic and then restarts. That different boards have different thresholds of these is also known. That's why we usually built locks for CPU freq and voltages while booting up, and then the user is responsible for experimenting with different freq/volt values and finally arriving at an optimium range for his CPU.
Hi,
thanks for the reply.
Do you know what are the default settings in a standard rom? Is there a CPU freq and voltage change or is the standard 998 and 1275 mv?
My problem is that standard settings, tables from custom roms did not work for my desire. It is really very unstable wiith this settings and i am hoping to find other Desire users having the same problem to find a good solution.
Thanks again for the help.
Yes, 998 Mhz is the standard freq at which freq is usually locked/
Thanks again, so using 998 with 1275 schould be the normal mode every desire is supposed to work with?
I am happy
Thanks to all of you who helped me with my problems.
Finnally after one year of Problems it seems i have a solution for my unstable desire.
After 2 Days of intensive testing i want to share my experience with you.
Seems my Problem was solved by setting own UV(undervolt) values.
It works great for me, other CPU can need other values, you must play around with it. But you can also try to use my settings.
I can say the phone is now rock solid. I could not believe that it was such a little thing. I even managed now to overclock it to 1190 without freezes.
As i said i had issues with every image and tried alot with new SD cards, other kernels, setting CPU speed ... Nothing helped. I had total OS freezes 3 - 15 times a day.
But now with the new UV settings in Deamon controller i get it really stable!
I want to explain you exactly my set up.
But i strong believe it was the UV / OC settings which do the stabilisation!
My set up:
Alpharev cm7r2 (S-Off)
4 ext Recovery
16 GB Samsung Sd Card Class 10
Fat32 + 1024MB Ext4 for x2sd
Runnymed AIO 3.0.4
X2SD Script
Deamon Controller with andrev_oc and custom UV settings entered in Deamon Controller.
Things i have applied:
RunnyMede_NO_Xloud.zip (speakers are too load for me in original)
No_TPWakeUp-Runny.zip (I do not want to wake up the phone with TP)
50+ APP's
Batterylife is not too bad i think. This is a screen shot of a medium to haevy using day.
Now here are the screens on UV and OC (and battery life):
kai-t said:
Thanks to all of you who helped me with my problems.
Finnally after one year of Problems it seems i have a solution for my unstable desire.
After 2 Days of intensive testing i want to share my experience with you.
Seems my Problem was solved by setting own UV(undervolt) values.
It works great for me, other CPU can need other values, you must play around with it. But you can also try to use my settings.
I can say the phone is now rock solid. I could not believe that it was such a little thing. I even managed now to overclock it to 1190 without freezes.
As i said i had issues with every image and tried alot with new SD cards, other kernels, setting CPU speed ... Nothing helped. I had total OS freezes 3 - 15 times a day.
But now with the new UV settings in Deamon controller i get it really stable!
I want to explain you exactly my set up.
But i strong believe it was the UV / OC settings which do the stabilisation!
My set up:
Alpharev cm7r2 (S-Off)
4 ext Recovery
16 GB Samsung Sd Card Class 10
Fat32 + 1024MB Ext4 for x2sd
Runnymed AIO 3.0.4
X2SD Script
Deamon Controller with andrev_oc and custom UV settings entered in Deamon Controller.
Things i have applied:
RunnyMede_NO_Xloud.zip (speakers are too load for me in original)
No_TPWakeUp-Runny.zip (I do not want to wake up the phone with TP)
50+ APP's
Batterylife is not too bad i think. This is a screen shot of a medium to haevy using day.
Now here are the screens on UV and OC (and battery life):
Click to expand...
Click to collapse
I hope this works with my setup. I have not applied wht you've listed. And I am on stock hboot, 4 GB class 4, Clockwork Mod recovery...
Will try it later in the day. Thanks!
Hi kartnite,
would be nice if you could share your experience with us if you have tried it.
Some more infos i have collected in onother thread, perhaps helpfull:
I have also used the SD Tools App.
Think i was wrong it's a samsung class 6 card:
6.1 MB write speed
27 MB read speed
My own thoughts to the comments about OC / UV:
Since the Display uses the most amount of the Battery it does not really matter to use some mv more or less. This is also prooven because the original images uses 1275 mv and 998 MHZ fix!
Some CPU's seems not to like undervolting. Some seems to have no problems with this.
For my CPU it is true that standard UV values make the phone freeze very often. Set the voltages up a little bit makes the CPU happy and my phone is stable
Also i think it is no danger, as long as you do not go over 1275 you are using the normal voltages.
About battery life i think it is important that your phone enters deep sleep mode when you turn the display off. You can check it with CPU Spy App.
My battereylife is good, at least more than 24 hours with normal usage.
My deamon settings are:
sleep min: 384
sleep max: 998
wake min: 284
wake max:1190 (here with 1350 mv)
I have set the 1190 since my phone is stable. The 1190 makes the ROM even more responsive if used.
Regards
Kai
Well, been a few hours now since I applied those settings.
Total of three force closes- Facebook, Mail and Sense.
Comparatively lesser than what it was earlier, but force closes nonetheless.
Yes, I did find that "improvement" in responsiveness but the lag returned.
I'm looking at other options, too.
Sorry for the delayed response. Wanted to wait a few hours before sharing what I observed.
Thanks for those additional points, mate. Will try them later in the day...
-
Swyped from XDA-Premium
kai-t said:
Hi kartnite,
would be nice if you could share your experience with us if you have tried it.
Some more infos i have collected in onother thread, perhaps helpfull:
I have also used the SD Tools App.
Think i was wrong it's a samsung class 6 card:
6.1 MB write speed
27 MB read speed
My own thoughts to the comments about OC / UV:
Since the Display uses the most amount of the Battery it does not really matter to use some mv more or less. This is also prooven because the original images uses 1275 mv and 998 MHZ fix!
Some CPU's seems not to like undervolting. Some seems to have no problems with this.
For my CPU it is true that standard UV values make the phone freeze very often. Set the voltages up a little bit makes the CPU happy and my phone is stable
Also i think it is no danger, as long as you do not go over 1275 you are using the normal voltages.
About battery life i think it is important that your phone enters deep sleep mode when you turn the display off. You can check it with CPU Spy App.
My battereylife is good, at least more than 24 hours with normal usage.
My deamon settings are:
sleep min: 384
sleep max: 998
wake min: 284
wake max:1190 (here with 1350 mv)
I have set the 1190 since my phone is stable. The 1190 makes the ROM even more responsive if used.
Regards
Kai
Click to expand...
Click to collapse
Thanks Kai,
finally i found someone with the same problem,
firstly i even try to use another kernel just like gingerbread 0.9 or 0.8.
I forgot the low-voltage influence(just like OC in Computer),
thank for your sharing~
Hi all,
sorry, but i have bad news.
The UV settings seemed to help a couple of days, but than my desire begin to freeze again.
It all started with a forced close of Whatsapp. After that many force closes returned and my desire also beginn to stuck.
I tried to repair the Filesystem with gparted. But it made it even worse.
I tried the whole Weekend, and even with only 998 and no UV the Problems kept.
Seems that somehow the image gets corrupted, even Dalvik wipe, or reflashing did not help.
Now i again started from scratch.
I installed AIO 3.0.5 with complete wipe and new partitioned SD card.
This time i set up the ROM without inserted SIM Card. I have done this because things alsways stuck when SMS, Phone things happen.
I think the SIM can have influence on the ROM's stability. I do not know why.
But without SIM Card insert i could set up everything without Problems.
Installed Andrev_OC and let all settings and UV as they are. Setup Apps, Contacts, Facebook. Let the phone sync and set up. Started it a few times.
I runs stable. I made a backup.
After the Backup got this HTC Launcher error, restrted and it was ok.
Then i inserted the SIM card. Till now it works. But lets look if it gets unstable again.
If this try will not succeed i will buy a new HTC and will sell my Desire. This freezes sucks.
But as said today it worked perfect. With many SMS and phone calls withoud freeze. It is really a strange thing!!!
Hope i can tell good news in a couple of days!
kai-t said:
Hi all,
sorry, but i have bad news.
The UV settings seemed to help a couple of days, but than my desire begin to freeze again.
It all started with a forced close of Whatsapp. After that many force closes returned and my desire also beginn to stuck.
I tried to repair the Filesystem with gparted. But it made it even worse.
I tried the whole Weekend, and even with only 998 and no UV the Problems kept.
Seems that somehow the image gets corrupted, even Dalvik wipe, or reflashing did not help.
Now i again started from scratch.
I installed AIO 3.0.5 with complete wipe and new partitioned SD card.
This time i set up the ROM without inserted SIM Card. I have done this because things alsways stuck when SMS, Phone things happen.
I think the SIM can have influence on the ROM's stability. I do not know why.
But without SIM Card insert i could set up everything without Problems.
Installed Andrev_OC and let all settings and UV as they are. Setup Apps, Contacts, Facebook. Let the phone sync and set up. Started it a few times.
I runs stable. I made a backup.
After the Backup got this HTC Launcher error, restrted and it was ok.
Then i inserted the SIM card. Till now it works. But lets look if it gets unstable again.
If this try will not succeed i will buy a new HTC and will sell my Desire. This freezes sucks.
But as said today it worked perfect. With many SMS and phone calls withoud freeze. It is really a strange thing!!!
Hope i can tell good news in a couple of days!
Click to expand...
Click to collapse
Hope you succeed in it.
I just replied you yesterday & set the UV setting before I slept last night.
And I have fully charge with battery in 100%.
But it still happened again, drained of battery to 30% and froze.
Also I have late for work without alarm clock.
I dont want to give up, but it is hard.
kai-t said:
Hi all,
sorry, but i have bad news.
The UV settings seemed to help a couple of days, but than my desire begin to freeze again.
It all started with a forced close of Whatsapp. After that many force closes returned and my desire also beginn to stuck.
I tried to repair the Filesystem with gparted. But it made it even worse.
I tried the whole Weekend, and even with only 998 and no UV the Problems kept.
Seems that somehow the image gets corrupted, even Dalvik wipe, or reflashing did not help.
Now i again started from scratch.
I installed AIO 3.0.5 with complete wipe and new partitioned SD card.
This time i set up the ROM without inserted SIM Card. I have done this because things alsways stuck when SMS, Phone things happen.
I think the SIM can have influence on the ROM's stability. I do not know why.
But without SIM Card insert i could set up everything without Problems.
Installed Andrev_OC and let all settings and UV as they are. Setup Apps, Contacts, Facebook. Let the phone sync and set up. Started it a few times.
I runs stable. I made a backup.
After the Backup got this HTC Launcher error, restrted and it was ok.
Then i inserted the SIM card. Till now it works. But lets look if it gets unstable again.
If this try will not succeed i will buy a new HTC and will sell my Desire. This freezes sucks.
But as said today it worked perfect. With many SMS and phone calls withoud freeze. It is really a strange thing!!!
Hope i can tell good news in a couple of days!
Click to expand...
Click to collapse
Changing UV din help me too.. So back on Samsung SD card (class 2) and it works fine.. I would suggest you to try with Samsung SD cards, cause they have better read speed.. I never has even i single with Samsung SD card but with Sandisk class 4 i had many freezes with same ROM and setup...
Thanks for the suggestiones,
i think that UV did not really help.
Yes i have a 16 GB Samsung card. I tried everything to get rid of this bug.
Now i am very supriesed, since the last setup yesterday the phone worked without freeze. But lets see sometimes things get worse after a few days.
I really do not understand what causes the trouble.
Setting it up without SIM Card seemed to help?
I am really confused. I always set up ROMS very correct. Means full wipe. Let boot , give time to stabilize... But mostly the ROMS crash before having set up all apps.
Without sim there was no problem. Now lets look how it goes on with this set up.
Before i have inserted the SIM again i pressed on the metal from the sim slot to make the sim fit better? Perhaps this helped? Anyone knows about problems with this causing ROMS to freeze?
If i think back my Problems started with a new SIM Card from O2 Germany.
I will report if it will start to freeze again or if it work.
Regards
Kai
kai-t said:
Thanks for the suggestiones,
i think that UV did not really help.
Yes i have a 16 GB Samsung card. I tried everything to get rid of this bug.
Now i am very supriesed, since the last setup yesterday the phone worked without freeze. But lets see sometimes things get worse after a few days.
I really do not understand what causes the trouble.
Setting it up without SIM Card seemed to help?
I am really confused. I always set up ROMS very correct. Means full wipe. Let boot , give time to stabilize... But mostly the ROMS crash before having set up all apps.
Without sim there was no problem. Now lets look how it goes on with this set up.
Before i have inserted the SIM again i pressed on the metal from the sim slot to make the sim fit better? Perhaps this helped? Anyone knows about problems with this causing ROMS to freeze?
If i think back my Problems started with a new SIM Card from O2 Germany.
I will report if it will start to freeze again or if it work.
Regards
Kai
Click to expand...
Click to collapse
I guess for me it was more over SD card issue.. My be your case is different .. best of luck on new setup.. I will be buying new SD card soon
Hi,
wish you the best luck! I have a Samsung SD card.
Works since 2 days stable. One FC when installing Facebook and i had to reboot.
But no OS freezes or missed SMS / calls.
Let's see if it stays like that. Sorry tht the UV not helped, but perhaps try fitting the SIM card better (with tesa on the back or pressing on the mettal) and try to install ROM first without SIM.
Another tip for Battery drain. I recognized yesterday that i have battery drain and i could see that my phone only gets partitialy into Deep Sleep. I serached what it is and in the end i recognized that it was the Facebook app. Installed the update to the newest version and now my phone went into Deep Sleep.
If you are not sure use CPU Spy to check.
If your display is off your phone should be nearly 100% in Deep Sleep. In Deep Sleep my phone uses nearly no battery! Thats really great and gives a long standby time! So check that newest Facebook is installed!
Regards
Kai
I don't want to be the spoilsport, but I've got the same problem only with my Samsung 16gb class 6 card, not with my "older" Sandisk class 2. But this card is way too slow for sense 3.5.
I've tried the higher UV values, which solved the freezing problem for a few days. But only temporary.
I'm considering switching to an ASOP ROM, just to keep my phone running stable. It often crashes on incoming calls or during nighttime. I missed a lot of calls and alarms.
kai-t said:
Hi,
wish you the best luck! I have a Samsung SD card.
Works since 2 days stable. One FC when installing Facebook and i had to reboot.
But no OS freezes or missed SMS / calls.
Let's see if it stays like that. Sorry tht the UV not helped, but perhaps try fitting the SIM card better (with tesa on the back or pressing on the mettal) and try to install ROM first without SIM.
Another tip for Battery drain. I recognized yesterday that i have battery drain and i could see that my phone only gets partitialy into Deep Sleep. I serached what it is and in the end i recognized that it was the Facebook app. Installed the update to the newest version and now my phone went into Deep Sleep.
If you are not sure use CPU Spy to check.
If your display is off your phone should be nearly 100% in Deep Sleep. In Deep Sleep my phone uses nearly no battery! Thats really great and gives a long standby time! So check that newest Facebook is installed!
Regards
Kai
Click to expand...
Click to collapse
Thanks for the tips.. I do get great battery while display is off, but when display is on it consumes lots of battery.. For this, some one asked to set the auto brightness to lowest. in rcmix display settings..
After months of suffering the random freezes and blank screens I've came to the conclusion that my problem stems from the sd card (not the actual card as I've tried a few) but the component which holds the card.
I've returned the phone to cpw but got it back untouched!
The way I test if it's the sd card if to open my camera app and if the small box in the bottom right of the screen is not showing the last picture taken (it shows black instead) then I turn phone off, push down on the sd card, reboot, and everything works - for a while!
Edit-I'm using the oxygen ROM so the camera app is the aosp one. If you have a file explorer then trying to open a file on your sd card will also let you know if there is a problem
Hi iain2510,
which camera app do you use? I do not have this small box.
Regards
Kai
I've been noticing something with my cpu that seems strange to me. I run an app called system panel to monitor my phone for various things and I've noticed for the past few days that my second core is constantly sleeping, even under a full load it stays at 100% idle and system panel says that cpu 1 is asleep. I downloaded kernel tuner and it says that cpu 0 is active but cpu 1 is offline. Was running stock rooted with no tweaks or other things added so i tried using odin to go back to stock but I still get the same info. The first screenshot is from kernel tuner with root and the sceond is from system panel with no root. Could my phone be defective?
Sent from my SGH-T989 using xda premium
Try system tuner in the play store. It has an option in settings to force the second core online, all the time. Set it to always on, and set it to boot that way. At least you can test it to see if it can be forced online. It is normal for the second core to be sleeping most of the time. In your first screenshot I see a toggle for cpu1 on/off at the bottom. You accidently toggle that?
Also, what's up with your CPU temp being 32°F? Are you in the arctic tundra?
You could also try flashing a new kernel. I believe there are a few for touchwiz based ROMs. IMO you should go aosp based ROMs. Slimbean4.1.2 with asdk kernel is the best performing rom/kernel combination I've ever flashed
there is no spoon.....
I tried flashing other kernels when my phone was rooted but it kept giving me the same thing. I tried the toggle in kernel tuner to see if I could turn the second core on after noticing the issue but it did nothing. System tuner was able to force the second core on for a bit but about 30mins after boot, the core went offline and has not come back on since.
Update: found out why core went offline. Apparently, if I touch any frequency settings such as core speed or governor for either core, the processor doesn't like it and shuts down the second core. Not sure if that's normal or not. Once phone is charged enough, gonna try flashing a different kernel to see if the same thing happens when I try to change the speed and governor.
Sent from my SGH-T989 using xda premium
Here is a long story, but please read it all as I really think it will help explain how the two cores work together.
I had/have the same thing. Exactly as you described it. Here is what I found (What I think anyway). I ODIN'd to stock, rooted, and installed Trickster MOD. That app showed only one core working. From reading up on Trickster MOD changing any CPU settings will apply to both cores. I changed the speed, and check the info panel. It showed both cores at the same speed that I changed it to, but the second core was still not moving. I reset Trickster MOD to default, uninstalled it, and installed Kernel Tuner. Same thing. Only one core was working. I started to think it was the stock kernel, so I flashed Tiberius, Jedi, and am now on Faux123. All kernels are doing it. It's not a kernel issue, but a kernel/Stock ROM function. Here is why I say that. I installed CPU Stats, and enabled it to display the CPU cores in the status bar. 99.9% of the time only one core was working (When I mention "99.9% of the time" I mean only one core would be working for about five minutes at a time. Which would lead a person to think somethings wrong since they normally wouldn't stare for ten minutes at the phone's kernel stats trying to catch the second core come on, and think only one was working.). I did catch the second core come on very briefly, so I knew it was working even for a split second. When I did see the second one on I tried to quickly open whatever kernel tuner I had to see what the cores were set to, and what they were doing, but by the time I opened the app only one core was working. I did some thinking, and I opened Lookout and ran a full scan, opened a couple more apps that use a lot of CPU. Then I opened, and kept on top my kernel tuner. To my surprise again 99.9% of the time only one core was working. Even if the CPU load was at 100%. The second core never came on, BUT it was because the first core wasn't at 100%. The CPU load would get to 90% when the first core would hit 100% under heavy load, but no second core was working at all. I finally watched it long enough to see a pattern (Like 15 minutes). The second core will only come on when the first core is at 100% AND the CPU load is at 100%. Then the second core kicks in. Once both cores were working at the same time the CPU load quickly dropped back under 100%, and once it did the second core shut right off to leave the first core do the work. So long story short your phone is not broken. That's the way it's meant to work. In my finding anyway. I'm running the stock ROM from ODIN with Faux123 JB release 1 kernel. That's all my mods are, and running quadrant I get an average score of 3730, so I'm thinking both cores have to be working to get a score like that. Here is the Play link to the CPU Stats app: https://play.google.com/store/apps/details?id=jp.takke.cpustats
And here is what it looks like in the status bar (The last icon on the left showing both cores at max in one screen shot, and the second screen shot showing only one core working. Just to show it does show both cores working separately.):
Thanks for the explination. I watched everything like you did and same results as you. I'm grateful for everyone's input. It puts my mind at ease knowing that everything is like it should be.
Sent from my SGH-T989 using xda premium
That's a good score. What frequency and governor you running?
there is no spoon.....
ctrlaltdeln said:
That's a good score. What frequency and governor you running?
there is no spoon.....
Click to expand...
Click to collapse
It's easier to show in pics that type all the stats. Here you go:
Not sure if me forcing my second core to be on constantly did something or what but I just ran quadrant twice and I got a score of 5661 the first time and 5981 the second.
Sent from my SGH-T989 using xda premium
damn dude. Now that's a score. Obviously your battery life will suffer with that kind of performance. If still using system tuner u definitely want to turn that second core back to default. You dont need all that muscle. I run at 1.18ghz/ lag free governor monday - Friday and 1.67ghz on the weekend. Battery life is more important to me. And everything is still buttery smooth. Glad all is well, your phone is back baby.
there is no spoon.....
I have perpetually experienced overheating issues while using 4.4-based ROMs; typically while using Navigation as part of Google Maps and while docked in the Galaxy Nexus Car Dock.
My frustration lead to inquiring with some skilled members of the Galaxy Nexus community, including @Ziyan, @freshgiammi, and @aosp. They have indicated that 4.4-based ROMs seem to be afflicted with this problem, but that it might also be tied to the kernel being used.
I have two phones; one running stock 4.3 (Sprint) and another running CM11 M8 (also Sprint).
Testing Setup:
I have Google Maps (and all other software, including Google Play and Play Services) completely updated. The screen brightness is set to auto. I've tested using Navigation initiated by WiFi, and then disabling the cellular radio (to ensure that the overheating is not being caused by radio activity.) I checked OS Monitor by switching through recent apps mid-testing; this gave me a snapshot of system temperatures and a glimpse of CPU usage.
Stock - Worked perfectly. Navigation, at any time of day, seems to work wonderfully. I do notice that the phone does get warm, and using OS Monitor, can confirm that it reaches 47 degrees C (and holds), never exceeding it. The phone continues to charge without issue. OS Monitor cited CPU usage of 29% at the highest (note that this does not indicate that Maps never used more than 29%, just that 29% was the most I witnessed while checking 15-20 times over the course of 10 miles.)
CM11 - Phone overheats within minutes of starting Navigation, reaching temperatures of 53 degrees C--and as high as 58 degrees C. The phone stops charging as soon as the system registers an "overheated" state. OS Monitor's highest CPU usage was 52%, which is almost double as high as I saw under the stock firmware.
IMGUR link of screenshots while Navigating, idle temperature, overheating, etc.
So far, it appears when my phone has been asleep or idle, it's operating at 29-35 degrees C; so it's nearly doubling it's temperature when Navigating. Additionally, this behavior occurs at night, when the sun (and warmer temperatures) are no longer a factor, which seems to rule out the idea that the environment is a major contributor.
I have a good friend who also as a Sprint Galaxy Nexus running CM11; he is a Waze user, and is experiencing the same issue.
Is this a known issue/problem with 4.4-based ROMs? This has been speculated in other threads, but perhaps a more definite answer/explanation is warranted?
Might this be related to the kernel in use, and the thermal throttling limits? What would be the best method of testing such?
What tests or other steps should I take to gather more information or test more factors?
EDIT 1: At @aosp 's recommendation, I'm looking for thermal throttling capabilities via the Kernel Tuner (2014 beta) application. The "Thermal" button is available, but grayed out. Is it safe to assume that means the kernel I'm using has no thermal throttling capabilities, which would (probably) explain how the Galaxy Nexus seems to be able to work itself into an overheated state?
Shidell said:
I have perpetually experienced overheating issues while using 4.4-based ROMs; typically while using Navigation as part of Google Maps and while docked in the Galaxy Nexus Car Dock.
My frustration lead to inquiring with some skilled members of the Galaxy Nexus community, including @Ziyan, @freshgiammi, and @aosp. They have indicated that 4.4-based ROMs seem to be afflicted with this problem, but that it might also be tied to the kernel being used.
I have two phones; one running stock 4.3 (Sprint) and another running CM11 M9 (also Sprint).
Testing Setup:
I have Google Maps (and all other software, including Google Play and Play Services) completely updated. The screen brightness is set to auto. I've tested using Navigation initiated by WiFi, and then disabling the cellular radio (to ensure that the overheating is not being caused by radio activity.) I checked OS Monitor by switching through recent apps mid-testing; this gave me a snapshot of system temperatures and a glimpse of CPU usage.
Stock - Worked perfectly. Navigation, at any time of day, seems to work wonderfully. I do notice that the phone does get warm, and using OS Monitor, can confirm that it reaches 47 degrees C (and holds), never exceeding it. The phone continues to charge without issue. OS Monitor cited CPU usage of 29% at the highest (note that this does not indicate that Maps never used more than 29%, just that 29% was the most I witnessed while checking 15-20 times over the course of 10 miles.)
CM11 - Phone overheats within minutes of starting Navigation, reaching temperatures of 53 degrees C--and as high as 58 degrees C. The phone stops charging as soon as the system registers an "overheated" state. OS Monitor's highest CPU usage was 52%, which is almost double as high as I saw under the stock firmware.
IMGUR link of screenshots while Navigating, idle temperature, overheating, etc.
So far, it appears when my phone has been asleep or idle, it's operating at 29-35 degrees C; so it's nearly doubling it's temperature when Navigating. Additionally, this behavior occurs at night, when the sun (and warmer temperatures) are no longer a factor, which seems to rule out the idea that the environment is a major contributor.
I have a good friend who also as a Sprint Galaxy Nexus running CM11; he is a Waze user, and is experiencing the same issue.
Is this a known issue/problem with 4.4-based ROMs? This has been speculated in other threads, but perhaps a more definite answer/explanation is warranted?
Might this be related to the kernel in use, and the thermal throttling limits? What would be the best method of testing such?
What tests or other steps should I take to gather more information or test more factors?
EDIT 1: At @aosp 's recommendation, I'm looking for thermal throttling capabilities via the Kernel Tuner (2014 beta) application. The "Thermal" button is available, but grayed out. Is it safe to assume that means the kernel I'm using has no thermal throttling capabilities, which would (probably) explain how the Galaxy Nexus seems to be able to work itself into an overheated state?
Click to expand...
Click to collapse
IMHO, handling of thermal throttling in 4.4 should be secondary thing to investigate about.
Shouldn't we first think of why for the same application, CPU is hogging this much?
Is it that CPU is not offloading its tasks to GPU which is supposed to happen, and happening with 4.3?
Good thing is that you have two tuna phones available to test out various scenarios.
If you use a ROM's stock kernel, thermal throttling is enabled correctly.
Give Omni and Trickster Mod a try. Omni is more stable & bug-free than CM, and Trickster will show you your CPU temps, as you only posted your battery temps - which are way too high! How the hell did you reach it? Even if I do some antutu, mine never reaches more than 40 °C. 58 °C is either a sensor misbehaving, or you put your phone in a jacket, lol, as it's far enough from the CPU to not heat up.
Post some Omni & Trickster temps with it's stock kernel something must be wrong, as I didn't notice anything like this on my maguro.
Ziyan said:
If you use a ROM's stock kernel, thermal throttling is enabled correctly.
Give Omni and Trickster Mod a try. Omni is more stable & bug-free than CM, and Trickster will show you your CPU temps, as you only posted your battery temps - which are way too high! How the hell did you reach it? Even if I do some antutu, mine never reaches more than 40 °C. 58 °C is either a sensor misbehaving, or you put your phone in a jacket, lol, as it's far enough from the CPU to not heat up.
Post some Omni & Trickster temps with it's stock kernel something must be wrong, as I didn't notice anything like this on my maguro.
Click to expand...
Click to collapse
My battery goes to about 44 degrees C when watching Netflix and charging and about the same during navigation and charging. Only time it's gotten hotter than that is due to environmental issues (such as very hot car interior before ac cools down). I run cm11 and faux123 kernel. Looks like OP is having some kind of hardware issues.
Shidell said:
I have Google Maps (and all other software, including Google Play and Play Services) completely updated. The screen brightness is set to auto. I've tested using Navigation initiated by WiFi, and then disabling the cellular radio (to ensure that the overheating is not being caused by radio activity.) I checked OS Monitor by switching through recent apps mid-testing; this gave me a snapshot of system temperatures and a glimpse of CPU usage.
Stock - Worked perfectly. Navigation, at any time of day, seems to work wonderfully. I do notice that the phone does get warm, and using OS Monitor, can confirm that it reaches 47 degrees C (and holds), never exceeding it. The phone continues to charge without issue. OS Monitor cited CPU usage of 29% at the highest (note that this does not indicate that Maps never used more than 29%, just that 29% was the most I witnessed while checking 15-20 times over the course of 10 miles.)
CM11 - Phone overheats within minutes of starting Navigation, reaching temperatures of 53 degrees C--and as high as 58 degrees C. The phone stops charging as soon as the system registers an "overheated" state. OS Monitor's highest CPU usage was 52%, which is almost double as high as I saw under the stock firmware.
Click to expand...
Click to collapse
I think it would be helpful to try to narrow down where the heat is coming from. Some possibilities:
1. Mobile data or LTE - a likely suspect, but you've already eliminated this one.
2. GPS - set Google Maps aside for a bit, get an app like GPS Status and Toolbox, set it to keep the screen on, and see if this still causes the heating issues.
3. GPU (or lack of proper use of GPU) - If Google Maps overheats the phone but GPS Status does not, it could be how CM is handling the display for Google Maps.
I got a chance to do some testing yesterday afternoon while driving. Toroplus on Page Plus, OmniROM 8-31 nightly, NukedTrinity kernel (was running it to test something else, will test stock kernel today but I fully expect results to be the same). Mobile data off as always. Started GPS right after a 15 minute phone call, battery was at 40 C. Hooked up the charger and ran GPS Status for 5 minutes, battery temp went up to 44 C. Ran Google Maps for 15 minutes (had previously downloaded offline maps for the area), still charging. Battery temp had gone back down to 40 C.
Sdobron said:
My battery goes to about 44 degrees C when watching Netflix and charging and about the same during navigation and charging. Only time it's gotten hotter than that is due to environmental issues (such as very hot car interior before ac cools down). I run cm11 and faux123 kernel. Looks like OP is having some kind of hardware issues.
Click to expand...
Click to collapse
Can you provide me with a link to the exact kernel you're using? I'd like to test it as well. Thanks!
Shidell said:
Can you provide me with a link to the exact kernel you're using? I'd like to test it as well. Thanks!
Click to expand...
Click to collapse
http://faux.romhost.me/tuna/kk44/tuna-kk-kernel-039m-sr.zip
Thank you. I'll test with this shortly as well.
@Ziyan
I agree that these temperatures are way too high; as you'll see below, though, my phone is reaching 46 degrees C simply by using GPS Status! I don't know what to make of that.
@musical_chairs
Thank you for testing as well. I agree that your hypothesis about separate testing is sound, and so I've been testing using GPS Status. I've tried @bsmitty83 's kernel, FancyKernel v56, and Laux123's kernels--all provide slightly different results, but to varying degrees of bizarre behavior using GPS Status.
Stock 4.3 works very well; it determines a bearing indoors without GPS fix and maintains it, with almost no change over a 10 minute period of time. Also, 4.3 warms up, but it never exceeded 44 degrees C.
CM11 w/ Laux123, Fancy Kernel and bsmitty83's all exhibit strange heading behavior. If you'll watch this youtube clip I uploaded (2:45), you'll notice that the phone is laying flat on a wooden table, and yet the Heading will change by 15 or more degrees on it's own. Later in the clip, I move the phone manually to force it to readjust, and you'll see that finds a new bearing from the beginning.
Laying both phones down next to one-another, stock 4.3 indicated the bearing was approximately 219 degrees. In this video clip (FancyKernel r56), my phone believes the bearing is 285 degrees (to begin with) and 260 degrees at the end.
Might GPS be the problem? I suppose I should flash Stock 4.3 to my phone, to make sure it does not continue to behave this way and rule out hardware problems/failure, right?
This just seems really bizarre. Especially that using a GPS fix application can ramp up the temperature so quickly, and so dramatically. Perhaps is the driver/kernel making too many callbacks, causing an escalation in CPU use and heat?
Finally, where can one find the CM11 M8 kernel (indivdually)? I'd like to re-flash it and compare it as well.
Thanks for the continued help in troubleshooting what's happening, everyone.
YouTube CM11 FancyKernel r56
@Shidell just download cm11 m8 and pull out the boot.img so you can fastboot flash it
I managed to gain -5°C on my maguro.
Basically just lowered the thermal throttle to stock values, and now it feels cooler. However still hotter than 4.3 so we're now sure that's not the culprit. Just FYI.
freshgiammi said:
I managed to gain -5°C on my maguro.
Basically just lowered the thermal throttle to stock values, and now it feels cooler. However still hotter than 4.3 so we're now sure that's not the culprit. Just FYI.
Click to expand...
Click to collapse
That's really interesting--5 degrees makes a pretty big difference.
I think I'm going to put stock back on my phone soon, in order to make sure it isn't some sort of hardware failure (maybe the chips in the GNex start to fail if they overheat too high/much? I've heard of that type of failure causing strange issues.)
I'm not sure what to chalk up as the culprit yet, but something is amiss.
If anyone else is reading this thread with a Galaxy Nexus and can comment on their experiences, that information would be useful.
@Ziyan A stock 4.2 or 4.3 kernel should work with any ROM, such as CM10.2 or CM11, is that correct?
I've tried pushing boot.img via fastboot, against both, but neither wants to boot. Am I doing something incorrectly?
Shidell said:
@Ziyan A stock 4.2 or 4.3 kernel should work with any ROM, such as CM10.2 or CM11, is that correct?
I've tried pushing boot.img via fastboot, against both, but neither wants to boot. Am I doing something incorrectly?
Click to expand...
Click to collapse
Yep, but you should only flash the zImage, as flashing the full boot.img flashes the 4.2/3 ramdisk too, which won't work.
BTW, it would be much easier to just flash the latest Omni to your phone. It uses a kernel close to stock, and it's close to AOSP... unlike CM
Ziyan said:
Yep, but you should only flash the zImage, as flashing the full boot.img flashes the 4.2/3 ramdisk too, which won't work.
BTW, it would be much easier to just flash the latest Omni to your phone. It uses a kernel close to stock, and it's close to AOSP... unlike CM
Click to expand...
Click to collapse
I plan on testing Omni today. The reason I ask about the kernel is because I'd also like to test various other ROMs using one of the stock 4.2 or 4.3 kernels.
Can I extract the zImage from the boot.img to ensure I'm only flashing the kernel?
Shidell said:
I plan on testing Omni today. The reason I ask about the kernel is because I'd also like to test various other ROMs using one of the stock 4.2 or 4.3 kernels.
Can I extract the zImage from the boot.img to ensure I'm only flashing the kernel?
Click to expand...
Click to collapse
Yes Connect the gnex via usb and "fastboot flash zimage zImage"
Thanks @freshgiammi I've done some extensive testing, so I hope that this helps us determine where the problem is. @Ziyan, @aosp, @musical_chairs, @poo706, @rkpeterson, @MWisBest, @BigBrother1984, @something15525 I'm hoping you might be able to lend a hand as well.
I created this thread based on the Galaxy Nexus tending to overheat when Navigating. However, I've found another discrepancy--live wallpaper performance with the Google Now Launcher. When using the GNL with the Phase Beam wallpaper, sometimes the GNex can draw it just fine; it's smooth, no (or few) dropped frames--it looks and works great. However, with other ROMs, it's very janky, stuttering and performing poorly.
(Note that GNL with a static picture works fine.)
I suspect that there might be a GPU driver issue, or perhaps a configuration issue, in some ROMs that's causing this behavior. Perhaps a certain GPU driver is used in some ROMs, and not others, causing the problem? Perhaps there is a config file with GPU settings where one has specific features enabled, others do not, and it results in poor performance in certain rendering cases?
I wonder if it might be related to overheating on the Galaxy Nexus when Navigating, watching video, playing games--items that tax the GPU. If it is such an issue, though, it might also mean extra work is being performed to compensate, and that would mean extra heat and battery use.
Here are two YouTube links displaying the behavior in question. First is Factory Stock 4.3--I wasn't able to directly record the screen (as that feature wasn't introduced with ADB until 4.4), but hopefully it's clear enough to see that it's smooth. (There is one hiccup when the cards are loading, but that's it.) The second video shows the same test, but running on CM11 M8--it's very choppy and lags behind input, and it's extremely noticeable in person.
I tried to capture video from OmniROM, but received this error while using ADB:
Code:
D:\Android\sdk\platform-tools>adb shell screenrecord /sdcard/omni44.mp4
WARN: Unable to set device connection state for audio submix IN
WARN: Unable to set device connection state for audio submix OUT
Unable to instantiate audio source (error -1)!
Factory 4.3
CM11 M8
I've conducted some tests on a spare Galaxy Nexus, and wiped my own personal model, to be sure that the behavior is the same on both devices--to ensure I don't have a damaged GPU or some other weird hardware issue that might be responsible.
Results:
Factory 4.2.1 - OK
Factory 4.3 - OK
LiquidSmooth LS-KK-v3.2-2014-09-03 - OK
Paranoid Android 4.6 Beta 1 - OK
OmniROM 4.4.4 - 20140905 Nightly - FAIL
CM10.2 RC 1 - FAIL
CM11 M8 - FAIL
Further, I extracted the kernel zImage from Factory 4.2.1 and 4.3, and flashed it into CM11 M8 just to see if the kernel alone made any difference. The 4.2.1 kernel wouldn't boot; 4.3 booted up properly, but the lag/choppiness persisted, which seems to indicate that the problem is not kernel related.
What should I investigate next? Clearly LiquidSmooth and ParanoidAndroid are getting smooth GPU performance, which I expect is also what's causing Navigation to cause my phone to overheat (but I can't prove that, unless we can solve this issue and then I can test with a fix and determine if it's the cause or not.)
Could a config file be at fault? A difference in drivers being used?
I'm having a huge lag with the latest version of Chrome which updated with material design. I'm afraid will we be having these gpu related bugs with Android L as well.
Will these gpu drivers issues be fixed with 3.4 kernel?
sagara.sandaru said:
I'm having a huge lag with the latest version of Chrome which updated with material design. I'm afraid will we be having these gpu related bugs with Android L as well.
Will these gpu drivers issues be fixed with 3.4 kernel?
Click to expand...
Click to collapse
Hm, I'm not sure I can answer that without more information.
What ROM and Kernel are you using? What type Galaxy Nexus? If you are using 4.4, can you do a screencap of what you're experiencing and upload it to YouTube as I have?
Shidell said:
Thanks @freshgiammi I've done some extensive testing, so I hope that this helps us determine where the problem is. @Ziyan, @aosp, @musical_chairs, @poo706, @rkpeterson, @MWisBest, @BigBrother1984, @something15525 I'm hoping you might be able to lend a hand as well.
I created this thread based on the Galaxy Nexus tending to overheat when Navigating. However, I've found another discrepancy--live wallpaper performance with the Google Now Launcher. When using the GNL with the Phase Beam wallpaper, sometimes the GNex can draw it just fine; it's smooth, no (or few) dropped frames--it looks and works great. However, with other ROMs, it's very janky, stuttering and performing poorly.
(Note that GNL with a static picture works fine.)
I suspect that there might be a GPU driver issue, or perhaps a configuration issue, in some ROMs that's causing this behavior. Perhaps a certain GPU driver is used in some ROMs, and not others, causing the problem? Perhaps there is a config file with GPU settings where one has specific features enabled, others do not, and it results in poor performance in certain rendering cases?
I wonder if it might be related to overheating on the Galaxy Nexus when Navigating, watching video, playing games--items that tax the GPU. If it is such an issue, though, it might also mean extra work is being performed to compensate, and that would mean extra heat and battery use.
Here are two YouTube links displaying the behavior in question. First is Factory Stock 4.3--I wasn't able to directly record the screen (as that feature wasn't introduced with ADB until 4.4), but hopefully it's clear enough to see that it's smooth. (There is one hiccup when the cards are loading, but that's it.) The second video shows the same test, but running on CM11 M8--it's very choppy and lags behind input, and it's extremely noticeable in person.
I tried to capture video from OmniROM, but received this error while using ADB:
Code:
D:\Android\sdk\platform-tools>adb shell screenrecord /sdcard/omni44.mp4
WARN: Unable to set device connection state for audio submix IN
WARN: Unable to set device connection state for audio submix OUT
Unable to instantiate audio source (error -1)!
Factory 4.3
CM11 M8
I've conducted some tests on a spare Galaxy Nexus, and wiped my own personal model, to be sure that the behavior is the same on both devices--to ensure I don't have a damaged GPU or some other weird hardware issue that might be responsible.
Results:
Factory 4.2.1 - OK
Factory 4.3 - OK
LiquidSmooth LS-KK-v3.2-2014-09-03 - OK
Paranoid Android 4.6 Beta 1 - OK
OmniROM 4.4.4 - 20140905 Nightly - FAIL
CM10.2 RC 1 - FAIL
CM11 M8 - FAIL
Further, I extracted the kernel zImage from Factory 4.2.1 and 4.3, and flashed it into CM11 M8 just to see if the kernel alone made any difference. The 4.2.1 kernel wouldn't boot; 4.3 booted up properly, but the lag/choppiness persisted, which seems to indicate that the problem is not kernel related.
What should I investigate next? Clearly LiquidSmooth and ParanoidAndroid are getting smooth GPU performance, which I expect is also what's causing Navigation to cause my phone to overheat (but I can't prove that, unless we can solve this issue and then I can test with a fix and determine if it's the cause or not.)
Could a config file be at fault? A difference in drivers being used?
Click to expand...
Click to collapse
Could you give FML a try? In particular the latest beta build...
not sure if you're on a maguro or a toro, so I'll link them both:
omni-4.4.4-20140825-maguro-FML.zip (159.56 MB)
omni-4.4.4-20140824-toro-FML.zip (159.41 MB)
With FML being based on OmniROM, if there's an issue with OmniROM but not FML or vice-versa it can help narrow down what might be the difference that causes the issue.
I'm also interested if screen record via adb works with that build for ya as well, so if you could test that it'd be much appreciated.
sagara.sandaru said:
I'm having a huge lag with the latest version of Chrome which updated with material design. I'm afraid will we be having these gpu related bugs with Android L as well.
Will these gpu drivers issues be fixed with 3.4 kernel?
Click to expand...
Click to collapse
The 3.4 kernel isn't looking to be the smoking gun we were hoping for, however if we can get Ducati (hardware video encode/decode and camera stuff) working with the updated GPU drivers in the 3.0 kernel that would definitely be helpful. The newer GPU drivers have better power management by a landslide.
I need somebody's help. The coolest my Note 4 CPU/GPU seems to get is about 53 degrees C and that's when I turn it on after it's been asleep on my desk. It is not a rogue app or anything like that because I have done both Factory resets and I have install custom roms, so everything has been factory reset multiple times. The water damage sticker indicates no water damage whatsoever. I know phones can get hot when gaming, my Note 4 gets to anywhere between 70 to 85 degrees Celsius and I am just wondering if that's normal I reduced my screen resolution to 720P and disabled two cores of the quad core processor and it does not seem to help one bit. Is this temperature normal or do I need to get rid of the phone?
PS when doing normal browsing it seems to hover around 60 to 67 degrees C
And the battery does not seem to go over 37 degrees Celsius
bucs9115 said:
I need somebody's help. The coolest my Note 4 CPU/GPU seems to get is about 53 degrees C and that's when I turn it on after it's been asleep on my desk. It is not a rogue app or anything like that because I have done both Factory resets and I have install custom roms, so everything has been factory reset multiple times. The water damage sticker indicates no water damage whatsoever. I know phones can get hot when gaming, my Note 4 gets to anywhere between 70 to 85 degrees Celsius and I am just wondering if that's normal I reduced my screen resolution to 720P and disabled two cores of the quad core processor and it does not seem to help one bit. Is this temperature normal or do I need to get rid of the phone?
PS when doing normal browsing it seems to hover around 60 to 67 degrees C
And the battery does not seem to go over 37 degrees Celsius
Click to expand...
Click to collapse
Okay, so I got rid of my Note 4 so this is off of memory (full-disclosure). My Note 4 always ran pretty hot when it had to do anything. When flashing ROMs I'd be lucky if the CPU was below 70 C and any time I'd be playing a GPU intensive game it would get too hot to touch. I never had a lot of issues with the battery temp being too high though despite this.
As far as solutions go:
1) Screen res might help.....but I would try my other suggestions first
2) I wouldn't recommend disabling cores, it just makes the other two have to work harder to accomplish the same tasks and may be worse overall.
3) Kernel adiutor will allow you to do two things: adjust thermal throttling and adjust max GPU/CPU frequencies. I always reduced the max GPU frequency on this phone to lower the temps and adjusted thermal throttling to 55 C. The only CPU adjustments I did were to make sure the CPU wasn't overclocked.
4) I know you said it wasn't a rouge app, but get a task viewer (this is a good one) just to make sure (I had Nova taking 25% CPU usage in the background because I restored it from TiBu).
I saw your post in the NSeven thread and decided to respond, but please in the future try not to post errors in other threads unless you have the issue in that ROM. It sounds like you might have the same issue in that ROM as well, but you didn't say so in your post.
Well first of all I would like to say thank you! I have been hoping for a while that someone would have some knowledge on the subject and I very much appreciate yours. Secondly, I apologize and I will try to refrain from posting the wrong thing in the wrong area in the future. Thirdly I have kernel auditor when I changed their frequencies on my CPU cores they just change right back. If I set a minimum it will stay but then if I try to set a maximum it resets them both to the default setting. I will turn my other course back on though thank you for that information do you have any idea why I may be having this frequency issue?
bucs9115 said:
Well first of all I would like to say thank you! I have been hoping for a while that someone would have some knowledge on the subject and I very much appreciate yours. Secondly, I apologize and I will try to refrain from posting the wrong thing in the wrong area in the future. Thirdly I have kernel auditor when I changed their frequencies on my CPU cores they just change right back. If I set a minimum it will stay but then if I try to set a maximum it resets them both to the default setting. I will turn my other course back on though thank you for that information do you have any idea why I may be having this frequency issue?
Click to expand...
Click to collapse
You're welcome, and no worries for the post . As for your third point it would be really helpful if you tell me what you're running.
Could you list: kernel, ROM, root method, Android version, and any kernel mods (govtuner, skynet, etc)?
Also, does the same thing happen when you set a GPU max frequency? Have you tried having the settings run on boot and then reboot the phone?
Yes I have tried that a couple of times I am currently running the nseven ROM with the CPU frequencies set at a minimum of 300 megahertz and a maximum of 1190 megahertz, or at least that's what I'm attempting to do LOL I have not tried changing the GPU Max frequency. The N7 ROM I believe is Android version 6.0.1. here is what I have tried
Wiping cache in recovery
Starting in safe mode
Factory resetting
Turning off certain settings such as WiFi calling, data Etc.
Using apps such as greenify to limit background processes.
Changing screen resolution to 720P
I actually installed this ROM hoping that it would make a difference because I have the same exact issue on the stock ROM before I ever unlock my bootloader or rooted my phone at all. And according to the sticker on the back of the phone it is not nor has it ever been water damaged. The picture I have attached shows my phone's activity just while writing this reply to you. In the bottom left-hand corner you can see the statistics. Sorry for the Inception lol
bucs9115 said:
Yes I have tried that a couple of times I am currently running the nseven ROM with the CPU frequencies set at a minimum of 300 megahertz and a maximum of 1190 megahertz, or at least that's what I'm attempting to do LOL I have not tried changing the GPU Max frequency. The N7 ROM I believe is Android version 6.0.1. here is what I have tried
Wiping cache in recovery
Starting in safe mode
Factory resetting
Turning off certain settings such as WiFi calling, data Etc.
Using apps such as greenify to limit background processes.
Changing screen resolution to 720P
I actually installed this ROM hoping that it would make a difference because I have the same exact issue on the stock ROM before I ever unlock my bootloader or rooted my phone at all. And according to the sticker on the back of the phone it is not nor has it ever been water damaged. The picture I have attached shows my phone's activity just while writing this reply to you. In the bottom left-hand corner you can see the statistics. Sorry for the Inception lol
Click to expand...
Click to collapse
Since you're replying to both threads I'll keep my responses to your other Q&A thread to make life easier .