Related
Now I love my DZ; it is by far the most capable phone I've ever owned, but it has this nasty habit of failing me whenever I seem to need it the most.
For example, today I was stuck behind a huge accident on the highway with an exit coming up in a few feet. I thought, "hey I'll just see if I can find a detour around it from this exit." Pulled out my phone and quickly launched google maps. right then, it completely stops responding to all touch input; the trackpad and physical buttons work fine, but nothing was registering on the touchscreen or capacitive buttons. I eventually had to pull the battery to fix the issue.
It just seems that these things tend to happen whenever i need to lookup something quickly on the phone (when im just screwing around on it, it works perfectly fine) be it completely not responding to touch input, or something weird happening like getting stuck between 2 homescreens, or the notification panel gets stuck halfway down, or massive input lag (5+ seconds) to the point of it not being usable.
And everything goes back to normal after a reset; but by then, I usually don't need to lookup whatever it was anymore.
The most frustrating part is that I can't seem to figure out whats causing it. I'm running virtuous 2.0.0 without any sense 3 additions, and I generally only have 1 or 2 tasks going on on the phone at once (usually just music player + whatever I'm doing). I originally thought it was just a performance issue, so I've increased the clock up to 1.5ghz (using daemon controller) but it hasn't has of an effect.
Any ideas on what else i can try?
Sounds like simple bad karma, I suggest donating to a charity or going to church
Other than that, I'd have no idea, sorry. Seeing as its not totally regular, there'd be no good way to easily pinpoint the issue. Maybe see if the rom produces a last_kmsg?
-Nipqer
makken85 said:
Now I love my DZ; it is by far the most capable phone I've ever owned, but it has this nasty habit of failing me whenever I seem to need it the most.
For example, today I was stuck behind a huge accident on the highway with an exit coming up in a few feet. I thought, "hey I'll just see if I can find a detour around it from this exit." Pulled out my phone and quickly launched google maps. right then, it completely stops responding to all touch input; the trackpad and physical buttons work fine, but nothing was registering on the touchscreen or capacitive buttons. I eventually had to pull the battery to fix the issue.
It just seems that these things tend to happen whenever i need to lookup something quickly on the phone (when im just screwing around on it, it works perfectly fine) be it completely not responding to touch input, or something weird happening like getting stuck between 2 homescreens, or the notification panel gets stuck halfway down, or massive input lag (5+ seconds) to the point of it not being usable.
And everything goes back to normal after a reset; but by then, I usually don't need to lookup whatever it was anymore.
The most frustrating part is that I can't seem to figure out whats causing it. I'm running virtuous 2.0.0 without any sense 3 additions, and I generally only have 1 or 2 tasks going on on the phone at once (usually just music player + whatever I'm doing). I originally thought it was just a performance issue, so I've increased the clock up to 1.5ghz (using daemon controller) but it hasn't has of an effect.
Any ideas on what else i can try?
Click to expand...
Click to collapse
although people say roms are 'stable' and can recommend these ROMs as "dd" (daily drivers) you cannot say that will be completely reliable. This is because when people say a ROM is 'stable', it's only after using it for 2-3days; unfortunately, roms gather clutter and begin to slow down over time. Not a problem for many flashaholics, but a problem if you're a one-rom kinda guy (or girl). So if you're not one-night-stand rom kind of person, here are some tips:
Reset your phone regularly. Phones start acting funny when they've been on for too long
Try stock ROM with addons flashed on top of it, rather than baked in a new rom
Most reliable roms i've experienced are Stock Gingerbread or CyanogenMod. Try those
If you are flashing a new rom, use SuperWipe, this can help get rid of clutter from old roms
skulk3r said:
although people say roms are 'stable' and can recommend these ROMs as "dd" (daily drivers) you cannot say that will be completely reliable. This is because when people say a ROM is 'stable', it's only after using it for 2-3days; unfortunately, roms gather clutter and begin to slow down over time. Not a problem for many flashaholics, but a problem if you're a one-rom kinda guy (or girl). So if you're not one-night-stand rom kind of person, here are some tips:
Reset your phone regularly. Phones start acting funny when they've been on for too long
Try stock ROM with addons flashed on top of it, rather than baked in a new rom
Most reliable roms i've experienced are Stock Gingerbread or CyanogenMod. Try those
If you are flashing a new rom, use SuperWipe, this can help get rid of clutter from old roms
Click to expand...
Click to collapse
Hmm, so you believe that this is purely a rom issue?
I havent run a stock rom for a while, but from what i remember the experience wasnt that pleasant, there was significant lag almost everywhere in the ui. Although i will admit that was back with froyo; i havent tried a stock gb stock rom yet.
Ill probablygive cm7 a go. Ive just grown so used to some sense features that its going to be hard for me to give them up (mainly recent apps in notifications, news widget, t9 dailer+manually linking contacts, and remote ring and forward on htcsense.com)
Has anyone had similar issues running virtuous sense 2.0.0?
As far as recent apps goes, long pressing the home button is a standard feature of android that brings up the most recent. Stock is the last 8 (I think) cm7 can show 15.
Sent from my HTC Vision using xda premium
Higher overclocking will make your phone LESS stable, not more. I'd stick around 1 GHz, as this is known to be very stable on most Z's, and usually does not result in any significant additional battery drain. OC may not have anything to do with your random hangs, but its probably not helping either.
redpoint73 said:
Higher overclocking will make your phone LESS stable, not more. I'd stick around 1 GHz, as this is known to be very stable on most Z's, and usually does not result in any significant additional battery drain. OC may not have anything to do with your random hangs, but its probably not helping either.
Click to expand...
Click to collapse
I'd agree. I really wouldn't ever go over 1.2ghz for a daily driver personally.
I run my ROMs at 800mhz lol, so I don't see the advantage of a huge overclock unless you're just bragging about benchmark scores.
its funny when u wanna show off your phone and you take it out of your pocket acting all cool and stuff and when u press the power button it wont wake up or you get a blank screen
haha its just bad karma for u like nipqer said
Try the stock pre-rooted gingerbread...I just flashed t last week and it is way faster than my froyo was, and amazing battery life, for me anyways, I do have an extended life battery though lol. Anyways as far as speed it is snappy on 800 mhz
Sent from my T-Mobile G2 using XDA App
redpoint73 said:
Higher overclocking will make your phone LESS stable, not more. I'd stick around 1 GHz, as this is known to be very stable on most Z's, and usually does not result in any significant additional battery drain. OC may not have anything to do with your random hangs, but its probably not helping either.
Click to expand...
Click to collapse
I've noticed the random hangs / glitches @ 800Mhz and 1Ghz, so I'm hesitant to say that the OC is the cause.
What do you use for stability testing? I've been running quadrant nonstop to test new OCs, but I don't think that benchmark stresses the cpu enough.
i am running Virtuous v2.0.0 w/ kernel unity v6 on it on desire z.
i've found bugs like
1/the top black bar ui, top left corner, some times i see the background wallpaper rather than the black bar. but it goes away if i pull down the notifications.
2/ the mail with microsoft exchange active sync, if i delete the mail it will automatically resync and downloads all mail including the on i deleted. but i got around that by using pop/imac instead.
all rather minor as i got ways to go around it.
i did have a similar issue where the touch screen goes unresponsive and i had to force close it, restart phone to get it back alive. but then i readjusted the clock speed and never had it happened again.
the phone is at around 825mhz with governor smart ass on wake time max, unless im watching 720p movies on the phone then i ramp it up at 1.4ghz.
sleep time on 368mhz max with governor at conservative.
i had it on like this since 11/09/11 (as i made a rom backup) and it never occured yet.
swinderz said:
i am running Virtuous v2.0.0 w/ kernel unity v6 on it on desire z.
i've found bugs like
1/the top black bar ui, top left corner, some times i see the background wallpaper rather than the black bar. but it goes away if i pull down the notifications.
2/ the mail with microsoft exchange active sync, if i delete the mail it will automatically resync and downloads all mail including the on i deleted. but i got around that by using pop/imac instead.
all rather minor as i got ways to go around it.
i did have a similar issue where the touch screen goes unresponsive and i had to force close it, restart phone to get it back alive. but then i readjusted the clock speed and never had it happened again.
the phone is at around 825mhz with governor smart ass on wake time max, unless im watching 720p movies on the phone then i ramp it up at 1.4ghz.
sleep time on 368mhz max with governor at conservative.
i had it on like this since 11/09/11 (as i made a rom backup) and it never occured yet.
Click to expand...
Click to collapse
I've been playing with the wake min and wake gov settings the past few days. I have it set at 600Mhz min, performance gov; I haven't noticed much difference in the battery life, but I'll have to do more extensive testing to be sure.
Performance feels slightly better, especially after a fast wake. can anyone give a detailed explanation of the behavior of the different gov settings? I can't seem to find much info on it.
makken85 said:
I've been playing with the wake min and wake gov settings the past few days. I have it set at 600Mhz min, performance gov; I haven't noticed much difference in the battery life, but I'll have to do more extensive testing to be sure.
Performance feels slightly better, especially after a fast wake. can anyone give a detailed explanation of the behavior of the different gov settings? I can't seem to find much info on it.
Click to expand...
Click to collapse
http://www.droidforums.net/forum/droid-hacks/21309-setcpu-1-4-6-what-cpu-governor-options-mean.html
ok i got a refushbished hd2 from best buy the third one and it seems to work well this tim the first one would overheat then the next wifi wouldnt work now this third one i have the Dorimax rom on there a really awesome rom but after some non use of the phone it doesnt respond the screen doesnt respond and then i take out battery restart and screen will not work and after a few hours the screen will work again and theres no over heating over anything works prefect but screen sometimes doesnt wanna work any ideas?
Try adjusting the CPU governor settings. I've had better luck on smartass, smartass2, interactivex with no more freezing, make sure your min CPU setting is at least 245mhz. Cm settings/performance/cpu
Sent from my HTC HD2 using Tapatalk
how you had this issue before?
sorry to say but well i did it i did a full wipe and a clean install and adjusted my cpu it looked like it was working and then it happened again and i dont think its a freeze issue i think its the lcd/digitalizer because it can reboot and the screen will still not work but ill vibrate the same way it reboots
hello, I would like to know if I'm alone on this issue, right now I'm running stock 2.3.6 on my i9100 and I have found an issue.
When Power saving mode is activated (the default one), if I open the camera app and turn off the screen for 1 minute, the phone dies and I have to reset it to make it work again.
Some friends told me that on ICS it doesn't happen so I was wondering if I got a faulty unit or this OS has this bug.
I would like some feedback from you guys with gingerbread onboard, thanks.
ellokomen said:
hello, I would like to know if I'm alone on this issue, right now I'm running stock 2.3.6 on my i9100 and I have found an issue.
When Power saving mode is activated (the default one), if I open the camera app and turn off the screen for 1 minute, the phone dies and I have to reset it to make it work again.
Some friends told me that on ICS it doesn't happen so I was wondering if I got a faulty unit or this OS has this bug.
I would like some feedback from you guys with gingerbread onboard, thanks.
Click to expand...
Click to collapse
This has never happened to me, but maybe try to turn off the device and take the battery out, leave it for a minute and reinsert the battery and restart. Then try to reproduce the problem.
Never happened to me or even heard of it
Sent from my GT-I9100
have you tried to see if this bug would occur without power saver mode on?,i never had this issue before nor heard of it
thanks everyone for your answers and concerns, the problem has been isolated:
It was a bug caused by a underclock that I did have that so far only occurs on the circumstances that I had on my phone.
When your phone turns off the screen, it will go to sleep mode or deep sleep mode depending on the running apps you have in that moment, these modes allow the CPU to low the frequencies (CPU Clock) in order to preserve battery life.
Comes to public interest that when using the camera app, the phone uses a high frequency clock to process photos and videos taken with the camera.
As because I did have a custom kernel that tweaks the CPU in order to gain more battery life, when battery saver option (which slow the max freq. clock of the CPU) was ON in my phone, the phone couldn't jump directly from sleep mode to max freq mode to keep camera app running and the CPU kept "slept"
If serves as interest of anyone, the kernel I was using was Siyah Kernel (don't remember which version, just check out the date this thread was posted and compare it with siyah kernel log to know by that date which was).
DOWNGRADING TO LOLLIPOP:: --- B151 from B331
I got it all sorted fellas.
Went to the 5X Repository. Downloaded the Stock 1.51 firmware. Placed the "update.app" from it under "dload" on sd card.
Opened up SuperSU on phone and went to settings to remove root and reboot.
After reboot hooked phone to computer and adb flashed the stock 1.51 recovery found in the repository. "same method as flashing twrp, only use 1.51 recovery.img instead"
Reboot phone again and then powered off.
Hold Volume up/down and power to restart and it updates form the 1.51 stock firmware on the SD card WIPING ALL DATA.
Now fingerprint and all factory settings are restored!
Thanks to all, and hope this helps others coming back from Marshmallow or CM13 like i did.
----
THX @skeppley
THX @Demian3112
----
Figured the above was an important surprise for some of you... OP still valid
Hello Everyone! Im new to the whole Honor 5x thing, coming from an m8 now, and before that a nexus 6, and before that a z3 then before that an S4 and before that an HTC Evo 4G LTE... Along with some minors, LG Risio, Moto E, S5...
Im just happy to say that so far I really enjoy this phone! Within the first few days of using it on Lolipop, i was getting 1d 15h type battery life which if youve looked at the phones ive mentioned so far... Really..really..wasnt what I was used to. A Day? For sure, the htc would be at 18% getting back on the charger... and it would die at 10%... with how long id had it. But... A Day was doable.
Ive been looking for a phone for SOOooOOO long now that had good enough battery to last a day at max brightness... Tweaking kernels, and Installing various ROMS (all of them per device)... Crack Flashing, as some would say. It just became a hobby... Ive noticed many weird things about the community, to those reading... let me list them now...
1. People all of the sudden(within the last 2 years?) prefer stock android over anything, regardless of what additional features are being added... Such as battery life improvements, Multitasking improvements, theme improvements, usability improvements... People like stock android... hmmm?
2. People want to be nexus so bad they will theme other UI's to death, just to make it look like stock, generic android... hmm..
3. Battery life, while a common complaint, seems to be indifferent to how frequently people update their phones.. (note: Marshmellow EMUI has a multi core battery bug, listed on XDA under mods..) or what ROM they choose (note the most popular rom being one with significantly worse battery life than stock)
4. Security improvements are completely unnecessary to the community (note the most popular rom being one that hardly supports the fingerprint sensor)
5. No matter how many bugs (even those listed in OP) people will always flock to the latest update of android. And then subtly complain to the developer about the bugs they already know about..
Such a strange mixture of people...to be sure.
However what ive noticed here, is a complete lack of readily available information, so i am hoping some of you might be able to assist me.
TL;DR
So I succeeded in downgrading my phone from MM to LP, as the battery life thing is a legit problem for me, as much as it may not be for other people. However the fingerprint sensor has been disabled, and no longer exists in the settings list... nor is it part of the startup. (confusing to be sure, you would think it would be there, and just FC when clicking on it were there to be a bug, or if the OS didnt detect the sensor or something... it should still be there yeah? If i understand how it works...
Also I cant seem to flash a B151 rom at all, being on B33...3? <- marshmellow... and im assuming at this point that means i wasnt supposed to be able to downgrade... (oops)
So i got TWRP installed (whats up with all the random errors twrp is throwing? Assuming thats normal...?) and am awaiting a BMarshmellow rom to finish... Which leads me to...
Where are the Emui ROMS? Unless its closed... but if this rom maker can do it... ?
and also, is the fix to the battery life on marshmello noticable to those of you who also care about battery life at all?
Marshmallow battery is really bad compared to lollipop.. we had a BIG.little concept that worked great. But Huawei decided to make it a 8 Core CPU even when idle. If someone could make a kernal that activates the 4 BIG cores only when needed it would be approciated! Stock it runs almost always with 8 cores and the highest freq. This phone is really let down by poor software..
Demian3112 said:
Marshmallow battery is really bad compared to lollipop.. we had a BIG.little concept that worked great. But Huawei decided to make it a 8 Core CPU even when idle. If someone could make a kernal that activates the 4 BIG cores only when needed it would be approciated! Stock it runs almost always with 8 cores and the highest freq. This phone is really let down by poor software..
Click to expand...
Click to collapse
Well there is a fix for it in the mods section that fixes battery. Finally got this phone back to functional lol..
Anyway, the fix for the moment anyway looks like it works, just has to be redone every reboot but really isn't that hard. After applying mincores mincpu 0 the big cores only light up when necessary. So far its helping a lot with battery life at least noticeably. Listented to music the whole way to work this morning and was still at 97% when I got there (I have an hour drive) , and that's using Youtube Music over 4g.. Not too shabby.
Yesterday I got to work doing the same thing on marshmallow at about 85-90 so it is doing something, and watching Kernel Auditor shows the big cores turning off when not in use. Worth checking out, applying the settings that are mentioned there don't do much im afraid, as I cant get them to stick through a reboot yet.
Currently writing an init.d script to make that happen every boot.
For now to my knowledge though it is working. Though I think lollipop was for sure better apps on screen off actually worked properly -_-; which im noticing more and more it doesn't anymore. Its more like a Doze control which is annoying because Doze is not near as good as stock lollipop control. I cant seem to revert back to lollipop and keep the fingerprint sensor though, if anyone figures that out please let me know!
TL;DR
I cant seem to revert back to lollipop and keep the fingerprint sensor though, if anyone figures that out please let me know! Id much rather downgrade than continue to fix marshmallow.
Though for those of you wondering, Viper|Atmos//Sony Beats the audio mod works perfectly on this phone
Just finished Init.d for Mincpus to fix the whole Big Little problem Super good stuff. Phone now booting in the big little mode you were talking about. super easy stuff.
Anymore u tried? I posted that script but still EMUI is an heavy OS im waiting for CM to be abit more stable. U can revert back to LP using a local update though dload. I did it aswell when my phone was bricked. Fp is not working because u miss the firmware
I also lost fingerprint when going back to lollipop. I'll let you know if i come up with any fixes for it.
skeppley said:
I also lost fingerprint when going back to lollipop. I'll let you know if i come up with any fixes for it.
Click to expand...
Click to collapse
U need the firmware had same.. revert though dload
Demian3112 said:
Anymore u tried? I posted that script but still EMUI is an heavy OS im waiting for CM to be abit more stable. U can revert back to LP using a local update though dload. I did it aswell when my phone was bricked. Fp is not working because u miss the firmware
Click to expand...
Click to collapse
@Demian3112
So Dload for lollipop will revert back from Marshmallow and keep fingerprint reader? Interesting... Does the Dload relock the bootloader? Sorry for the somewhat noobish question, new.
Just looking through sys at the moment to understand the language used for big.little, seems to be a comma separation for them. Wondering if I can set min max this way and keep cores 4-7 at min freq 200000. Also looking for a way to get all big cores to disable when not in use, not just 3 of them which is the current.
Swap set to 0 in marshmellow, seems to speed the phone up a little.
testing Xposed here in a bit to get a few different features, debloated the phone, mostly normal stuff. Playing with other CPU files at the moment in root browser to see what I can do regarding the power draw from the CPU...
set SElinux to permissive to allow for proper audio playback through Viper//Atmos//Sony//Beats...Found Multiwindow, enabling that soon, don't know why it was ever disabled?
Otherwise mostly enjoying the phone at the moment, still above 80% battery with all this that im doing and im half way through my day. the CPU thing really helped with the battery draw.
You should try CyanogenMod 13: excellent battery life, USB OTG and gyro working, much better CPU & RAM management...
FP reader is working, but you must upgrade to MM first (to update trust zone and radio firmwares).
igotlostintampa said:
@Demian3112
So Dload for lollipop will revert back from Marshmallow and keep fingerprint reader? Interesting... Does the Dload relock the bootloader? Sorry for the somewhat noobish question, new.
Just looking through sys at the moment to understand the language used for big.little, seems to be a comma separation for them. Wondering if I can set min max this way and keep cores 4-7 at min freq 200000. Also looking for a way to get all big cores to disable when not in use, not just 3 of them which is the current.
Swap set to 0 in marshmellow, seems to speed the phone up a little.
testing Xposed here in a bit to get a few different features, debloated the phone, mostly normal stuff. Playing with other CPU files at the moment in root browser to see what I can do regarding the power draw from the CPU...
set SElinux to permissive to allow for proper audio playback through Viper//Atmos//Sony//Beats...Found Multiwindow, enabling that soon, don't know why it was ever disabled?
Otherwise mostly enjoying the phone at the moment, still above 80% battery with all this that im doing and im half way through my day. the CPU thing really helped with the battery draw.
Click to expand...
Click to collapse
It stays unlocked.. u Miss firmware thats why it doesnt work get stock firmware for your device and it should work not sure how you reverted.. keep in mind u will lose all data and stuff.
Demian3112 said:
Anymore u tried? I posted that script but still EMUI is an heavy OS im waiting for CM to be abit more stable. U can revert back to LP using a local update though dload. I did it aswell when my phone was bricked. Fp is not working because u miss the firmware
Click to expand...
Click to collapse
Demian3112 said:
It stays unlocked.. u Miss firmware thats why it doesnt work get stock firmware for your device and it should work not sure how you reverted.. keep in mind u will lose all data and stuff.
Click to expand...
Click to collapse
Oh of course, I loose data all the time anyway so im used to that flash far too often to be healthy.
I reverted via a twrp backup, used emergency data recovery to factory reset using stock recovery, then it let me boot into lollipop, just missing that all important fingerprint reader//navigation tool. Will most def do that soon, at 60% :/ not sure where the random drain came from. just an hour later and lost 20%? Has to have to do with Screen off app closing. Huawei probably did the lazy thing and just changed over from their own tools to doze I guess that helps while its on your bed at night? And then never again?
As for CM13, im fairly apathetic to the topic... Not to be annoying, or rude, but ive heard the excellent battery life claim a million times about stock android, and while ive noticed its improvements over something like...say, Sense, or Touchwiz... Ive never seen it beat the z3's battery saving tool (before marshmallow), or as of the day I got this phone, Huaweis non-debloated lollipop.
Ive never seen a phone still be at 30-40%, at the end of work, the day after the day I charged. Until this phone. The Z3 would make it a little past lunch if I barely used it on day 2, but this phone played pokemon go for 2 hours the day I charged it, I spent the day listening to streaming music, browsing for various small things, watching a few youtube videos, a little navigation... And it had 40% when I left work the next day lol at 100% auto brightness. Id love to see some screen on vs idle drain comparisons between this phones CM13 and Stock, at that point, ill believe a battery claim.
It played pokemon go at 60fps and the game is a known battery/gpu hog (s7 plays slower than this phone, likely due to lack of gyroscope?)
other than some various laggy UI glitches, the phone was pretty much what id been looking for (I Prefer Miui over stock android, this phone is similar)
igotlostintampa said:
Oh of course, I loose data all the time anyway so im used to that flash far too often to be healthy.
I reverted via a twrp backup, used emergency data recovery to factory reset using stock recovery, then it let me boot into lollipop, just missing that all important fingerprint reader//navigation tool. Will most def do that soon, at 60% :/ not sure where the random drain came from. just an hour later and lost 20%? Has to have to do with Screen off app closing. Huawei probably did the lazy thing and just changed over from their own tools to doze I guess that helps while its on yuur bed at night? And then never again?
Click to expand...
Click to collapse
What buildnumber and Custom version/Cust do you have? Might be able to link you the right firmware.. twrp backup doesnt backup firmware that explains that you dont have a finger print, is the H from Honor at boot logo Red also?
I got it all sorted fellas.
Went to the 5X Repository. Downloaded the Stock 1.51 firmware. Placed the "update.app" from it under "dload" on sd card.
Opened up SuperSU on phone and went to settings to remove root and reboot.
After reboot hooked phone to computer and adb flashed the stock 1.51 recovery found in the repository. "same method as flashing twrp, only use 1.51 recovery.img instead"
Reboot phone again and then powered off.
Hold Volume up/down and power to restart and it updates form the 1.51 stock firmware on the SD card WIPING ALL DATA.
Now fingerprint and all factory settings are restored!
Thanks to all, and hope this helps others coming back from Marshmallow or CM13 like i did.
skeppley said:
I got it all sorted fellas.
Went to the 5X Repository. Downloaded the Stock 1.51 firmware. Placed the "update.app" from it under "dload" on sd card.
Opened up SuperSU on phone and went to settings to remove root and reboot.
After reboot hooked phone to computer and adb flashed the stock 1.51 recovery found in the repository. "same method as flashing twrp, only use 1.51 recovery.img instead"
Reboot phone again and then powered off.
Hold Volume up/down and power to restart and it updates form the 1.51 stock firmware on the SD card WIPING ALL DATA.
Now fingerprint and all factory settings are restored!
Thanks to all, and hope this helps others coming back from Marshmallow or CM13 like i did.
Click to expand...
Click to collapse
Your Reply has been added to the OP for those concerned with Downgrading. Figured it might be nice to stumble upon the directions that, after reading many posts throughout the various roms, many people might actually be looking for. Will likely try this tonight when I get home, battery is much better with the battery fix, but not as good as lolipop
Great.
Hope to help others that were stuck the same way
@igotlostintampa flashed CM13 today.. Im sold on this device i would suggest you to upgrade aswell.. Everything works no bugs so far and its smooth as hell. Battery is insane.. Every core has a task and with normal use it doesnt even scale above 800mhz and the other 4 are offline all the time only when needed they get activated.. Since 1PM i lost only 20% battery (Im on 23 now) while i was installing CM also.. Deffinitaly recommended
Demian3112 said:
@igotlostintampa flashed CM13 today.. Im sold on this device i would suggest you to upgrade aswell.. Everything works no bugs so far and its smooth as hell. Battery is insane.. Every core has a task and with normal use it doesnt even scale above 800mhz and the other 4 are offline all the time only when needed they get activated.. Since 1PM i lost only 20% battery (Im on 23 now) while i was installing CM also.. Deffinitaly recommended
Click to expand...
Click to collapse
Alright so question for you, im interested in that CM13 seems to be using the big little concept we have been speaking about...
((Marshmellow Big.Little Fix does not function properly. It resets without reboot being required, just takes longer to apply than the core modifications under smart power saving, init.d through kernel auditor on smart battery saving mode does not run script on boot, must be manually executed))
Does the CM13 Fingerprint reader allow you to pull down notifications? Will likely check it out, interested... Also, how about a screen off task killer? Is that present... Looking through its forums.
igotlostintampa said:
Alright so question for you, im interested in that CM13 seems to be using the big little concept we have been speaking about...
((Marshmellow Big.Little Fix does not function properly. It resets without reboot being required, just takes longer to apply than the core modifications under smart power saving, init.d through kernel auditor on smart battery saving mode does not run script on boot, must be manually executed))
Does the CM13 Fingerprint reader allow you to pull down notifications? Will likely check it out, interested... Also, how about a screen off task killer? Is that present... Looking through its forums.
Click to expand...
Click to collapse
No fingerprint pull down.. No gestures for it yet. No off screen taskkiler but thats fine its stock android you will have enough memory spare.. Got 10 apps open right now no issue and u can instant change to one. CPU is tweaked already with kernal adiutor u can turn off cores manually and tweak it to what ever you like.. Day 2 of using battery is better.. ALOT smoother u can switch from app in a instant no waiting time at all. If u have any questions just ask it. Rom is stable enough for daily use no bugs so far!
Demian3112 said:
No fingerprint pull down.. No gestures for it yet. No off screen taskkiler but thats fine its stock android you will have enough memory spare.. Got 10 apps open right now no issue and u can instant change to one. CPU is tweaked already with kernal adiutor u can turn off cores manually and tweak it to what ever you like.. Day 2 of using battery is better.. ALOT smoother u can switch from app in a instant no waiting time at all. If u have any questions just ask it. Rom is stable enough for daily use no bugs so far!
Click to expand...
Click to collapse
Ah see im not worried about memory usage, I never run low on a stock rom in the first place. Stock android has this problem where it allows some apps to sit open eating battery life when the screen is off. Instances of this include facebook, Google maps, general overall "Wakelocks" not present inside of the stock Huawei rom, that prevent the phone from going to sleep even though they aren't doing anything. The off screen task killer is there to close apps hogging battery life in the background that should have turned off when they weren't needed but didnt, after your screen turns off. For the most part this is the cause of the smoothness that you feel inside of a rom. Its going to be smooth because none of the apps are ever turning off, its a balance scale.
Not a big problem, I don't mind fixing that its really easy lol, just curious. As for the gestures that's a little disappointing.. It just seems like I may have to add a bit, but I can try it before I run over to lollistock, ill test it out today. You've convinced me with a claim of good battery though lol, and your previous comments about marshmallow, don't let me down!
igotlostintampa said:
Ah see im not worried about memory usage, I never run low on a stock rom in the first place. Stock android has this problem where it allows some apps to sit open eating battery life when the screen is off. Instances of this include facebook, Google maps, general overall "Wakelocks" not present inside of the stock Huawei rom, that prevent the phone from going to sleep even though they aren't doing anything. The off screen task killer is there to close apps hogging battery life in the background that should have turned off when they weren't needed but didnt, after your screen turns off. For the most part this is the cause of the smoothness that you feel inside of a rom. Its going to be smooth because none of the apps are ever turning off, its a balance scale.
Not a big problem, I don't mind fixing that its really easy lol, just curious. As for the gestures that's a little disappointing.. It just seems like I may have to add a bit, but I can try it before I run over to lollistock, ill test it out today. You've convinced me with a claim of good battery though lol, and your previous comments about marshmallow, don't let me down!
Click to expand...
Click to collapse
Im using Force doze app.. U can whitelist apps and as soon as you turnoff your screen it starts doze... You wont get notifications from apps you didnt whitelist until you turn it back on
Hello XDA
I have the Note4 N910F, it start to random reboot tow month's ago
i decided to look why is that happen i noticed it reboot when its get hot
i installed the Device Control app it show the CPU temperature 84C° TO 86C° with out doing anything in the device so i decided to UC The max CPU frequency from 2649MHz to 1958MHz the temperature now never across the 75C° and its never reboot anymore
but when i reboot the device it go through the boot process and reboot when the home screen appears i have to cool it with cold air to boot normaly so i can UC the cpu again
why is that happening and is there away to UC the CPU permanently?
by the way its the same on stock firmware and the same on other roms
Thanks XDA
AOWS said:
Hello XDA
I have the Note4 N910F, it start to random reboot tow month's ago
i decided to look why is that happen i noticed it reboot when its get hot
i installed the Device Control app it show the CPU temperature 84C° TO 86C° with out doing anything in the device so i decided to UC The max CPU frequency from 2649MHz to 1958MHz the temperature now never across the 75C° and its never reboot anymore
but when i reboot the device it go through the boot process and reboot when the home screen appears i have to cool it with cold air to boot normaly so i can UC the cpu again
why is that happening and is there away to UC the CPU permanently?
by the way its the same on stock firmware and the same on other roms
Thanks XDA
Click to expand...
Click to collapse
Hello!
I'm afraid that I can't really tell you why this is happening. I strongly think of a hardware issue.
But I think I know a way how to prevent your phone from overheating while booting. You mentioned the Device Control app on your post, so let's start with my first suggestion:
Is there an option in the app like "apply settings on boot" or anything like that? If yes, try to enable this option and reboot your device to proof if it worked.
If Device Control does not support this feature, I recommend you Kernel Adiutor. I used it for over one year and also used the "apply settings on boot" option that worked like a charm for me. It's basically the same application, just with another design, another name and so on, but practically it does the same.
Vygravlil said:
Hello!
I'm afraid that I can't really tell you why this is happening. I strongly think of a hardware issue.
But I think I know a way how to prevent your phone from overheating while booting. You mentioned the Device Control app on your post, so let's start with my first suggestion:
Is there an option in the app like "apply settings on boot" or anything like that? If yes, try to enable this option and reboot your device to proof if it worked.
If Device Control does not support this feature, I recommend you Kernel Adiutor. I used it for over one year and also used the "apply settings on boot" option that worked like a charm for me. It's basically the same application, just with another design, another name and so on, but practically it does the same.
Click to expand...
Click to collapse
Hello
Thank you for respond
The Device Control doesn't have Apply On Boot so I used the Kernel Adiutor You recommend
It do have Apply On Boot and i switched it on but It didn't make a different because it apply the setting after the boot process complete not before or during the boot process
you mentioned a great app thank you for that, the thermal option is useful it turn of cores if the CPU Temperature Get higher than a temperature i chose which i set to 50C°
i will learn to live with the (Cooling during booting) what really bothering me is the rebooting when i am on the middle of a call or working or playing on the phone
now it's solved with Kernel Adiutor
here is a picture of the CPU and GPU temperature before changing frequency and setting the thermal control
seconds after booting
______
and this after make changes
Thank you
AOWS said:
Hello
Thank you for respond
The Device Control doesn't have Apply On Boot so I used the Kernel Adiutor You recommend
It do have Apply On Boot and i switched it on but It didn't make a different because it apply the setting after the boot process complete not before or during the boot process
you mentioned a great app thank you for that, the thermal option is useful it turn of cores if the CPU Temperature Get higher than a temperature i chose which i set to 50C°
i will learn to live with the (Cooling during booting) what really bothering me is the rebooting when i am on the middle of a call or working or playing on the phone
now it's solved with Kernel Adiutor
here is a picture of the CPU and GPU temperature before changing frequency and setting the thermal control
seconds after booting
______
and this after make changes
Thank you
Click to expand...
Click to collapse
You're welcome!
At least I was able to help regarding the phone's random reboots due its heat development while using it.
I something comes to my mind that could help with preventing the phone from overheating while booting, I'll let you know.
But for now, I'm happy you can use your phone under normal conditions again. Have a nice day!
Vygravlil said:
You're welcome!
At least I was able to help regarding the phone's random reboots due its heat development while using it.
I something comes to my mind that could help with preventing the phone from overheating while booting, I'll let you know.
But for now, I'm happy you can use your phone under normal conditions again. Have a nice day!
Click to expand...
Click to collapse
It's almost normal it just have fever hope it'll recover soon
You have a nice day too