Related
Hi guys. I've been running the Android Stock Desire build from Cotulla for a few months now. Every once in a while I'd get a freeze, but then a battery in, and out would fix the problem (usually within the first try. sometimes I need to do this a few times, but no more than 5 times)
However, since last Friday my phone has been crashing like crazy! Constant crashes at random stages, and even reboots. Removing the battery also didnt guarantee a fix. I think I may have tried it about a hundred times, and Android just crashed at a random point in time during every boot. Eventually it booted, but since then it has crashed again! I figured that perhaps I should try a newer build.
I've decided to try out this build: [08.MAR.2011][CWM]TyphooN CyanogenMod 7 RC2 v2.5.4[2.3.3][A2SD/RAM][rafpigna OC 1.8]. Since I already have radio 2.15.50.14, these are the steps I've taken:
- Flash Task29 (ShaDrac version).
- Flash MAGLDR 1.13
- Flash ClockworkMod Recovery v1.3 135M System
- Flash CM7
Now, even during the various stages before flashing the CM7 rom, I would get freezes during the MAGLDR 1.13 bootscreen, or recovery won't load and I'll get stuck on the GOGOGO screen. Also, copying the zip file over in the MAGLDR mass storage mode won't work, and causes a freeze when I start the copy. Reset, or Battery removal seems to get me to the next step again.
Eventually I've flashed CM7, but now it freezes at the setup stage.
I'm starting to think maybe its not the various Android builds that I'm trying, but perhaps the problem lies somewhere else on the phone? Any ideas? Is my radio perhaps not the best one for the phone (even though its the latest)?
Any help will be much appreciated.
Regards,
XA83
Shameless bump (hope I'm not breaking any rules!)
I realize this post should have probably been under the CM7 thread as well, but I don't have access to that yet due to my low post count...
Could be:
*Wrong CWM Size, check in the rom thread for information
*leftover data, task 29 and reinstall everything
*Corrupted data on SD card, try booting without sd card to see if this is the case.
Thanks for the reply.
I've removed both the SD card and the SIM card. Phone seems to work flawlessly. Boots CM7 without a hitch. Next step I've added the SD card back, and formatted the card from the CM7 settings page. Still perfect.
I've tried it about 5 times now and every time the SIM card is not present, the phone works like a dream. Every time I put the SIM card in, CM7 crashes within the first few seconds of showing the home screen.
Finally, some progress!! Thanks again for the assistance. However, what dis this mean? Could this be related to the actual SIM card I'm using, or does it have to do with the part where it initiates the network connection and possibly the 3g connection?
*Also, just for information, I believe that I do have the correct CMW size. The build indicates "Flash ClockworkMod Recovery v1.3 135M System" which is the one I've flashed.
maybe reflash back to winmo then do evrything all overagain to android
I doubt it's an issue with the phone and its initiating with the sim card. Just replace the sim card
the SAGA continues
Hi Guys,
So since my last posts I have actually managed to get the phone running Typhoon's CM7 and its been working great... for a while.
I'm currently on version 3.0.4 and I still get:
1) Freezes,
2) Reboots,
3) SOD,
4) This happened today: phone cuts mid-phone call and makes a loud buzzing noise until I pull the battery.
I'm thinking more towards hardware problem at the moment, but please let me know what you think, and what I can do to debug the sitaution. Is there perhaps a hardware monitoring app that I can install that logs the whole system every 1 minute that I'll be able to pick something up.
I was also thinking maybe the phone overheats. As explained in my original post, whenever a crash or reboot occurs, it would sometimes not restart the first time round after pulling the battery out and putting it back in. Sometimes I get crashes even during the MAGLDR stage with "fatal hit" and strange things like that. Or even when I boot into CWM sometimes.
Now, to test this overheating, I've experimented with placing my phone in the fridge for 5 minutes after a crash. Thusfar I've done this 3 times, and every time I get a clean boot when I put the cold battery back in and then the phone functions perfectly for a while.
So, overheating, or do I perhaps need another radio? I'm out of ideas.
Any help will be much appreciated. The problem now is that I'm so used to android that I wont be able to go back to winmo or even blackberry
Regards,
XA83
it happens to my phone, and did on my previous HD2.
I've tried every build, task 29, every radio...new sd card....everything.
matt
Are there any apps we can run to test battery temp, cpu temp, cpu voltage or anything like that? I'm pretty effecient at debugging PC hardware issues, but when it comes to my phone I feel like I'm back in the stoneage!
Please help
I have tried over and over and over and over on this kind of issue.
most if the time was some unfinished coppied file which can;t runs properly on roms.
Try to asks ROM developer.
- SD partition : how many partititons?
- SD partitions : what kind of partitions, is it using etc 2/3/4, does it comes with swap etc?
- Installation method : does it needs to clear phone ROM with cwr ? what is the size?
HD2 usually I will go for 400M size
- config.txt settings for SD/NAND.
A proper guide could helps you on in the installations
If you guys are having overheating problems resulting in freezes, you might want to use SETCPU and set a lower maximum frequency. Something like 800-900 mhz might keep your cpu's from getting too hot. Or maybe setting it to a different governor could help too, idk for sure.
Sent from my HTC HD2 using XDA App
Freezes
huggs said:
If you guys are having overheating problems resulting in freezes, you might want to use SETCPU and set a lower maximum frequency. Something like 800-900 mhz might keep your cpu's from getting too hot. Or maybe setting it to a different governor could help too, idk for sure.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Possible solution, Thanks mate,
I changed the CPU speed to 1036 Mhz from stock 998 Mhz speeds and haven't had a Freeze yet,
before that The touch screen would freeze occasionaly when there was a lot of activity like in games such as fruit ninja ....
a Lower CPU speed such as 806 Mhz also seemed to do the trick ...
I don't understand why the Freezes would occur at stock speeds ...
I'll have to give it a few days though ...
Touchscreen Freezes
huggs said:
If you guys are having overheating problems resulting in freezes, you might want to use SETCPU and set a lower maximum frequency. Something like 800-900 mhz might keep your cpu's from getting too hot. Or maybe setting it to a different governor could help too, idk for sure.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Update:
Tried that with Interactive Governer, it still freezes on odd occasions, and the battery temp shows 33-36 Degrees Celcius on load when running games ...
i'm beginning to think the freeze is temperature related, as it never freezes while it's cool ...
I'm going to try running it with Smartass governer and see if it makes any difference ...
regards.
Yeah, there's been alot of HD2 owners who've had high-temp related freezes, one guy even went as far as to dissassemble his phone, re-bond the cpu to his mainboard, and add a home-made heat sync to prevent further overheating (successfully)
I just figured changing the cpu freq or governor might reduce cpu load, or increase efficiency, resulting in less overheating. But I feel pretty confident in saying that you guys' freezes are very likely coming from heat. It was even a problem in stock WinMo roms
Sent from my HTC HD2 using XDA App
Yawp, I can barely charge my phone with the silicone case on anymore and that's in ac (the AC in my house is usually set at 74F) I have noticed I get freezes at 36C however I can go to the beach and get it up to 44C and it runs flawlessly
Touchscreen Freezes
Dylan Wilson said:
Yawp, I can barely charge my phone with the silicone case on anymore and that's in ac (the AC in my house is usually set at 74F) I have noticed I get freezes at 36C however I can go to the beach and get it up to 44C and it runs flawlessly
Click to expand...
Click to collapse
Thats wierd, I'd have thought that such a High Temp as 44 Degrees C would cause more freezes ....
regards.
i'm getting freezes from cyanogenmod android too. i recently restored my ROM to the original 2.13 and believed to have all previous settings related to android deleted.
freezing
i realy didnt undrestand what the exactly means of freeze, my phone freeze after change rom ,i can't use "TyphooN CyanogenMod " becuz my phone freeze at the android logo and it didnt any animation to boot !!!
i have hspl8 , radio 2.15.50 ,Recovery_130M_system_4M_cache[v3.0.2.4],mgldr 13.
i install windows then install android but it steel frezz, i can install just HyperDroid-GBX rom !!
it this problem fix with cpu temp ??
i get it in Refrigerator still feee !!
Temperature
Hi guys. It's definitely the overheating causing all the freezes. I've now succesfully "fixed" my phone 11/11 times by placing it in the freezer and then it works flawlessly for at least a day.
I'll try setCPU to try and lower the CPU frequency from stock and prevent heat issues.
However, ideally I'd like to return the phone to the manufacturer as a defective one! Only problem - how do you convince the 'genius' tech guy that the phone overheats. Last thing I want is to send the phone in, and only get it back after a few months with some response that they found nothing wrong.
Hence, I'm still looking for some sort of app to prove in a way that the overheating is causing crashes... At least in that case they may be more likely to issue a replacement immediately. Any ideas yet?
Regards,
XA83
Just a follow up:
My phone has been sent back to HTC. After a long wait, tech support said they replaced the hardware components - I'm assuming the phone mainboard.
I've reflashed CM7 since, and it hasn't crashed a single time!
Verdict: Random freezes was caused by hardware problems on the phone, and the crashes was most likely due to overheating of the components.
Regards,
XA83
Hi,
Anyone been keeping an eye on hotplugging on the n9005 ?
Mine is still unrooted, so I'm talking 100% vanilla Samsung configuration...
I use Android Tuner's online core notifications to keep an eye on this, there are other apps that can to this as well.
At some point, after a few hours of uptime, sometimes only after quite a many (20h+), I just notice that it will never drop below 2 or 4, never had it lock on 3 minimum, so can't comment on that scenario.
Once this happens, it's impossible to get back to single core even on very low load.
Also when leaving the device doing nothing, freq. drops to 300MHz and still 4 cores remain online.
There is obviously an impact on battery drain as well.
Only way to get back to normal is to reboot...
JP.
I've noticed the opposite issue, two cores just going offline forever until I reboot the device.
So that would point to obvious hotplugging issues, except if you ran into thermal throttling, maybe.
Were you running some heavy stuff when this happened ?
JP.
i tested it out of curiosity using the widget in system monitor app.
i have exactly the same issue as SentinelBorg above. the two cores go offline and never come back online until the next restart.
very wierd.
Well for the very least we can conclude hotplugging is flawed in the current firmware ...
As soon as we get a proper recovery (nandroid restore that don't bootloop) I'll start working on an improved kernel, this is just not acceptable for a top notch 700€ pricetagged device
JP.
Send from my Note 3 (n9005)
Latest case ...
Send from my Note 3 (n9005)
Again ...
Send from my Note 3 (n9005)
You're on full stock. Doesn't that mean you have no options regarding CPU government?
nakedtime said:
You're on full stock. Doesn't that mean you have no options regarding CPU government?
Click to expand...
Click to collapse
Correct, so I cannot do anything about this misbehaving, except reboot.
I want to know whether this is something others observe as well.
The thing is, if you're not looking at it, you won't know it's happening, cause who really keeps an eye on online cores all the time ? I do as I do kernel coding and as such also work on governors, which make me look at stuff like that.
If this happens of yours, you'll just have a hotter Note 3 with less lasting battery without knowing why, or worse without knowing battery easily could last longer if that was fixed.
This clearly is a bug in the current firmware, since as you correctly stated, being full stock unrooted, I can't be influencing this in any other way than applying load to the CPU which is clearly not the case as you can see in the screenshots... and it just happens randomly.
Once I start on a Note 3 kernel that will be in the top list of things to take care of.
JP.
Sent from my SlimBean 4.3 build 1.8 / Yank555.lu CM10.2 kernel v1.6g-beta4 (Linux 3.0.99) powered Galaxy S3 i9300
I would have gone with the N9000 if I knew how to develop a kernel. BIG.little sounds like so much fun to dev on.
PS
Have you found any Info about the thermal throttling? I'd love to be able to manipulate the temps for less heat when over clocking.
I was actually not going to get any more Samsung device because of crappy open source support they (in fact don't) give
I ended up going for the note 3 because of the specs and exactly because it was the Qualcom and not the Exynos version and a one time offer I could not refuse, but I will go nowhere Samsung's own super secret Exynos CPUs ever again unless they change their policies, which I doubt.
I just do hope I won't regret my move...
JP.
Sent from my SlimBean 4.3 build 1.8 / Yank555.lu CM10.2 kernel v1.6g-beta4 (Linux 3.0.99) powered Galaxy S3 i9300
exactly the same here, after a reboot everything is back to normal
Sent from my SM-N9005 using Tapatalk 2
Happened again after ~10h uptime while watching a live video stream...
Cores went to a steady 4 online, load was unchanged over a longer period (~45 mins of video stream over WiFi).
This makes little sense, hotplugging is flawed.
JP.
PS: Still stock unrooted.
Send from my Note 3 (n9005)
This is still happening for me, reboot solves it. Running 4.4.2 and thought this should be solved by now.
Sent from my SM-N9005 using XDA Premium 4 mobile app
Stock kitkat XXUENB3, unrooted. I have a similar problem when all of the sudden all cores are stuck online with core 1 and 2 stuck at 1958 mhz and core 0 and 3 scaling normally just not going offline. A reboot fixes the issue untill it happens again randomly. This is my last Android device and I had gs2,gnex,n4 and now n9005.
I've rooted and when the issue happens, disabling mp decision and enabling it again fixes the issue so this means that hotplug doesn't play well. Maybe a custom kernel will fix this issue.
ciprianruse88 said:
I've rooted and when the issue happens, disabling mp decision and enabling it again fixes the issue so this means that hotplug doesn't play well. Maybe a custom kernel will fix this issue.
Click to expand...
Click to collapse
Yes, long time I've open this thread
Indeed, on TW I used to do just that, "pkill -9 mpdecision", which killed the daemon and it respawned and all was back to usual.
I've since then moved to CM11, and this never happened again ever since, so I expect this to be a TW related issue, since mpdecision had the same MD5 signature in CM11 as on my stock 4.3 TW ROM.
And it looks like if the problem still persists on KK TW...
But it's certainly not a kernel related issue, as I've use my own kernel on JB TW, where this happened as well, once I went CM11, I ported my kernel to CM, and as I mentioned, never happened ever since.
Might be TW messing with DVFS (for benchmark cheating and maybe other things...).
Maybe worth trying to use Wanam's Xposed Module and disable ROM DVFS.
JP.
2 cores always online and the other 2 always offline= Dual Core
Ok guys I have experienced the bug with 2 cores being always offline which basically makes your Note 3 a dual core phone many times in the past untill I found what caused this! Even firing up Antutu the cores are still 2 and not 4 online! So yeah at first a reboot was an easy and effective sollution but that was not enough so I devoted 2 days trying to find out what caused this. Guess what? The problem was inside one of Samsung apps, specifically the bloody S-Finder app! I can reproduce the bug 100% whenever I want so I am very sure about it! Also I have tested this on 2 other Note 3s (n9005) and I noticed the same bug , with 4.3 and unfortunately now on 4.4.2!
Steps to reproduce it:1) Fire up S-finder 2) Search any app and launch it or even without launching just only by typing on the search bar the phone enters into dual core mode(!) after few seconds 3)Now this is the critical step, remember now the phone is already having only 2 cores enabled so if you press the home button then you are stuck with the buggy dual core mode!!! So this is how you end up with only 2 out of 4 cores working!
The sollution is of course to reboot the phone but another more faster and specific sollution is to close the S-Finder with only this (correct) way: while you are on the S-finder app close it by simply pressing the back button untill it exits completely and you are out to the menu. Incase you are not in the S-finder app then you must check if the program is shown in the recently used apps(longs pressing the home button) then tap on it to open it and then close it by hitting the back button." Don't close/kill it from the task manager or from the recently used apps, only close it when you are inside of the app and hitting the back button!"
Synopsis All in all, the culprit at least on my case is the S-finder app in which when it is used it somehow forces the phone to get into dual core mode and it stays like this because you forget to properly close it after the search is done. The sollution is simply closing the S-Finder gently/properly by using the back button from the inside of the app and not with any other way.
I don't know if this is truly a bug of Samsung or just a sneaky way to increase/improve the battery life at the expense of performance but I surely know that many people have this issue without even realising it!
I said too many things so that I can give a detailed review on this bug, I hope I have expressed it clearly and not to confuse you!
I think it is a very serious issue and it should be fixed as well as inform people about it!
SAVVAS. said:
Ok guys I have experienced the bug with 2 cores being always offline which basically makes your Note 3 a dual core phone many times in the past untill I found what caused this! Even firing up Antutu the cores are still 2 and not 4 online! So yeah at first a reboot was an easy and effective sollution but that was not enough so I devoted 2 days trying to find out what caused this. Guess what? The problem was inside one of Samsung apps, specifically the bloody S-Finder app! I can reproduce the bug 100% whenever I want so I am very sure about it! Also I have tested this on 2 other Note 3s (n9005) and I noticed the same bug , with 4.3 and unfortunately now on 4.4.2!
Steps to reproduce it:1) Fire up S-finder 2) Search any app and launch it or even without launching just only by typing on the search bar the phone enters into dual core mode(!) after few seconds 3)Now this is the critical step, remember now the phone is already having only 2 cores enabled so if you press the home button then you are stuck with the buggy dual core mode!!! So this is how you end up with only 2 out of 4 cores working!
The sollution is of course to reboot the phone but another more faster and specific sollution is to close the S-Finder with only this (correct) way: while you are on the S-finder app close it by simply pressing the back button untill it exits completely and you are out to the menu. Incase you are not in the S-finder app then you must check if the program is shown in the recently used apps(longs pressing the home button) then tap on it to open it and then close it by hitting the back button." Don't close/kill it from the task manager or from the recently used apps, only close it when you are inside of the app and hitting the back button!"
Synopsis All in all, the culprit at least on my case is the S-finder app in which when it is used it somehow forces the phone to get into dual core mode and it stays like this because you forget to properly close it after the search is done. The sollution is simply closing the S-Finder gently/properly by using the back button from the inside of the app and not with any other way.
I don't know if this is truly a bug of Samsung or just a sneaky way to increase/improve the battery life at the expense of performance but I surely know that many people have this issue without even realising it!
I said too many things so that I can give a detailed review on this bug, I hope I have expressed it clearly and not to confuse you!
I think it is a very serious issue and it should be fixed as well as inform people about it!
Click to expand...
Click to collapse
Yes. I've did the exact same thing and cpu was dual core but after I've reset mp decision I couldn't reproduce it anymore. Good catch!
Yank555 said:
I use Android Tuner's online core notifications to keep an eye on this, there are other apps that can to this as well.
Click to expand...
Click to collapse
How did you enable the online core notifications in Android Tuner?
Hi Guys,
I am a new Note 4 user, I've had note 2 before. Recently I have used Z3, OneplusOne and S5, which in my opinion other than the S5, the phones were smooth and laggieness was non existence. I have since changed to the Note 4 and immediately I have realised that even in the kitkat (currently running lollipop) that the phone lags when changing between the programs, turning on the camera, or even after a picture has been taken it takes a while to get to respond. Hardwar-wise I believe the Note 4 is very respective and I can only blame this on the software. I have since upgraded to lollipop and I must say the performance is no different than before. Could anyone tell me without rooting and installing a modified rom, is there a way to increase the smoothness of the phone? it is because of the bloatware? how to de-bloat? or is it just how it is?
Thanks
Patrick
the better is a clean installation and after that come back and report any issue's
Thanks vagenrider but this issue was already apparent when I first used the phone right out of the box and noticed the lag.
pplwu said:
Thanks vagenrider but this issue was already apparent when I first used the phone right out of the box and noticed the lag.
Click to expand...
Click to collapse
hi,
I can say this,
that i had my Note4 (N910F rooted, stock Rom.) since October 2014 till now.
Overall i had little or no "lag" of note. (apart from Recent button plus an setting issue.. minor )
Over this period of time, if i found/noticed a bit of "lag" and i found culprit, causing the problem, I would uninstall app,
i also noticed, so far that it has always been a 3rd party (badly coded.. or on lollipop the app was not "playing" nicely.. etc etc)
So overall.... when i was on Android v 4.4.4 or now on Lollipop my device has been working fine.. battery use, been good, very, very smooth
So all i can say, if you have issues it is either you have a faulty device or an app/combination of apps causing lag.or setting issue
I have stated this, in many of my post that i have following devices.. on hand
Note 4, Note 3,Note 8.0 (tab) Note 2 and they all running fine..( 100% satisfaction)
Bottom line
is that i think i am in a good position to state that my Note 4 compares 100%plus, with my Note3(which is a very very, good device, smooth no lag, etc etc)
Above is just my opinion and i hope that you can sort out your device
Good luck
pplwu said:
Hi Guys,
I am a new Note 4 user, I've had note 2 before. Recently I have used Z3, OneplusOne and S5, which in my opinion other than the S5, the phones were smooth and laggieness was non existence. I have since changed to the Note 4 and immediately I have realised that even in the kitkat (currently running lollipop) that the phone lags when changing between the programs, turning on the camera, or even after a picture has been taken it takes a while to get to respond. Hardwar-wise I believe the Note 4 is very respective and I can only blame this on the software. I have since upgraded to lollipop and I must say the performance is no different than before. Could anyone tell me without rooting and installing a modified rom, is there a way to increase the smoothness of the phone? it is because of the bloatware? how to de-bloat? or is it just how it is?
Thanks
Patrick
Click to expand...
Click to collapse
I am having the same issues with my device. I've had it with both lollipop and KK. I've had multiple ROMS (all stock). I've done fresh installs, cleaned cache, disabled apps, and completely run with none of my apps installed. All the same issues, as you've mentioned. I'm thinking of returning my note 4 if they don't fix it by 5.1.1 or August. This device cost way too much for these kinds of issues... :-\
zkyevolved said:
I am having the same issues with my device. I've had it with both lollipop and KK. I've had multiple ROMS (all stock). I've done fresh installs, cleaned cache, disabled apps, and completely run with none of my apps installed. All the same issues, as you've mentioned. I'm thinking of returning my note 4 if they don't fix it by 5.1.1 or August. This device cost way too much for these kinds of issues... :-\
Click to expand...
Click to collapse
pplwu said:
Hi Guys,
I am a new Note 4 user, I've had note 2 before. Recently I have used Z3, OneplusOne and S5, which in my opinion other than the S5, the phones were smooth and laggieness was non existence. I have since changed to the Note 4 and immediately I have realised that even in the kitkat (currently running lollipop) that the phone lags when changing between the programs, turning on the camera, or even after a picture has been taken it takes a while to get to respond. Hardwar-wise I believe the Note 4 is very respective and I can only blame this on the software. I have since upgraded to lollipop and I must say the performance is no different than before. Could anyone tell me without rooting and installing a modified rom, is there a way to increase the smoothness of the phone? it is because of the bloatware? how to de-bloat? or is it just how it is?
Thanks
Patrick
Click to expand...
Click to collapse
About debloating:
Without root you cannot really debloat the rom. You can only try to holding every app you don't need and drag&drop on touch wiz launcher and drag&drop it to "app details". New window with details will be prompted and you can delete or deactivate the app. This is everything you can do on stock to debloat.
About the main problem:
Also here without root and custom rom I could only suggest to try following:
Go to Settings app.
Scroll down to device information.
Tap few times (I think 5 times shoul it be) on build number to activate developer options.
Go back to main screen of settings, scroll down to developer options and open them.
So from here you can try to change following values:
- Force GPU rendering
- Turn off hardware overlays
- lower values for animations (all three) or just set them to zero if you don't need them. That gives really bounce speed (but mainly just for eyes, it doesn't really chages overall performance of device, just little bit maybe)
The nagtive thing of GPU and harware overlay is little bit higher the battery drain then usual.
vbaschen said:
About debloating:
Without root you cannot really debloat the rom. You can only try to holding every app you don't need and drag&drop on touch wiz launcher and drag&drop it to "app details". New window with details will be prompted and you can delete or deactivate the app. This is everything you can do on stock to debloat.
About the main problem:
Also here without root and custom rom I could only suggest to try following:
Go to Settings app.
Scroll down to device information.
Tap few times (I think 5 times shoul it be) on build number to activate developer options.
Go back to main screen of settings, scroll down to developer options and open them.
So from here you can try to change following values:
- Force GPU rendering
- Turn off hardware overlays
- lower values for animations (all three) or just set them to zero if you don't need them. That gives really bounce speed (but mainly just for eyes, it doesn't really chages overall performance of device, just little bit maybe)
The nagtive thing of GPU and harware overlay is little bit higher the battery drain then usual.
Click to expand...
Click to collapse
Thanks for that!! I've just done the above, will use this setting for a while and see how it goes.
Hi Guys, after applying vbaschen's suggestion I believe the phone has improved in terms of window changing and smoothness in operation. Battery discharge hasn't affected me that much given the battery has always lasted an entire day of heavy use and I plug it in everynight. I would recommend this quick mod. Thanks again vbaschen.
vbaschen said:
About debloating:
Without root you cannot really debloat the rom. You can only try to holding every app you don't need and drag&drop on touch wiz launcher and drag&drop it to "app details". New window with details will be prompted and you can delete or deactivate the app. This is everything you can do on stock to debloat.
About the main problem:
Also here without root and custom rom I could only suggest to try following:
Go to Settings app.
Scroll down to device information.
Tap few times (I think 5 times shoul it be) on build number to activate developer options.
Go back to main screen of settings, scroll down to developer options and open them.
So from here you can try to change following values:
- Force GPU rendering
- Turn off hardware overlays
- lower values for animations (all three) or just set them to zero if you don't need them. That gives really bounce speed (but mainly just for eyes, it doesn't really chages overall performance of device, just little bit maybe)
The nagtive thing of GPU and harware overlay is little bit higher the battery drain then usual.
Click to expand...
Click to collapse
Right on. I was going to recommend reducing the animation values as well as that is usually the case. Hope it helped!
Androidious said:
Right on. I was going to recommend reducing the animation values as well as that is usually the case. Hope it helped!
Click to expand...
Click to collapse
I went for a completely different solution: the Note 4's Snapdragon cpu has the bad habit of heating up very quickly. Two or three minutes of heavy usage (gaming/emulation, or worst: piles of file operations, e.g. media scanner) make it shoot up to 85° C. To prevent serious damage, the cpu is then automatically scaled down to extremely low values, which results in abysmal performance. When I first unboxed my N910F and inserted my old sdcard, the media scanner went haywire because my sdcard was faulty (works alright in my old Note 2, but the Note 4 is picky). The phone quickly got too hot to even touch, ran sluggish as hell (AnTuTu scores between 24000 and 29000), then shut itself down. :crying:
After I had replaced the sdcard, things got better, but only when I didn't put too much load on the phone: 52000 AnTuTu points in the morning (first thing to do with the cold phone), but getting worse steadily until I couldn't score more than 43000 points.
Now, after a lot of fiddling and tweaking (Kitkat, Lollipop, Stock, Custom, CM 12.1), I finally settled for (Lollipop) Emotion Revolution R8 ROM along with the Emotion nightly kernel (r17) and (most important) Synapse kernel tweaker. Instead of overclocking the blasted thing even more, I actually downclocked it one step (2572,8 MHz). The result: a rock stable phone that actually runs way better than with the higher (stock) clock rate. The cpu hardly ever scratches 70° C, and usually stays around 65° C even when I run demanding apps like PPSSPP, Dosbox, or Real Racing 3 (don't like that one, but it beats the s**t out of the cpu - 85° with stock cpu clock!). AnTuTu scores reach about 51500 - almost as much as with stock clock rate - but several times in a row now, with no performance hit. So, even though the peak performance may be one or two percent lower, I can run my phone for hours without any performance drops. Oh, and it's good for battery life, of course. :good:
So, if you're rooted, you may want to give it a shot. :fingers-crossed:
Hi, so I've had my G2 D800 model for a while (about a year or two), and for the most part, it's been an excellent phone despite being 3 years old now. Never had any slowdown problems, and it's always performed well in games and in general.
But just recently, about a week ago, it just started lagging out and being very, very slow.
For example, if I'm watching a YT video through the app, if I rotate the screen, it takes maybe 5-8 seconds to actually rotate. Also, in a lot of circumstances where the keyboard has to pop up, it just freezes the app until the keyboard pops up maybe 10 seconds later.
It's also just laggier in general in most apps, scrolling through FB or Twitter freezes nearly every second when I'm scrolling. It's generally unresponsive and sometimes just freezes outright. It also acts this way on the homescreen, and in most everything else.
The most annoying part, however, is that sometimes the devices just doesn't turn on for sometimes up to 15 seconds after pushing the power button (and it usually just refuses to turn on when using my knock code).
The odd part, however, is that once it's actually in something like a game, it performs perfectly fine.
I've played a number of Cardboard games, as well as games like Nova 3, and it performs perfectly.
I've also ran multiple benchmarks (Geekbench, 3DMark, etc), and it scores around where it should.
Info about the device:
LG G2 D800
Stock Lollipop 5.0.2
Software Ver. D80030f
Kernel Ver. 3.4.0
Rooted
TWRP Recovery installed
XPosed Lollipop installed
G3 Tweaks installed, a number of tweaks applied
Everything else is stock (homescreen, etc)
What I've tried/checked:
Checked memory usage during "lag sessions", rarely dips below 300mb free
Changing minfree values through Rom Toolbox (tried every preset, as well as setting everything to the max to free as much as possible)
Rebooting (affects nothing)
Checked CPU speed with Rom Toolbox (is at max, and does achieve the max speed of 2265 MHz. Setting it to performance mode/setting the min speed to be 2265 MHz has no effect, but reduces battery time)
Changed default cache sizr (tried every preset from 128kb to 4096kb. With multiple benchmarks, the optimal value for r/w bounced between 512kb and 4096kb, currently on 4096)
Things I have not tried (that I am aware would possibly have an affect):
Changing anything in the kernel tweaks/build.prop
Completely wiping, reformatting, and reinstalling (I really would rather avoid this if possible, as it would take a while to get everything back to what it is now, and it was a pain to upgrade to Lollipop in the first place)
I am unaware of anything else I could try to fix it, which is why I'm here
So, does anyone know of any other solutions or things to try? This has made my phone very unreliable, even for phone calls and messages, which is a problem.
Thank you for your time and help!
Jtpetch said:
Hi, so I've had my G2 D800 model for a while (about a year or two), and for the most part, it's been an excellent phone despite being 3 years old now. Never had any slowdown problems, and it's always performed well in games and in general.
Click to expand...
Click to collapse
Hi,
First thing i need you to try out is this custom kernel : http://forum.xda-developers.com/lg-g2/development/lp-5-0-2-kernel-3-4-107-dorimanx-1-0-lg-t3102512
Then install greenify, and hibernate all the unnecessary apps.
This should solve the issue.
iubjaved said:
Hi,
First thing i need you to try out is this custom kernel : http://forum.xda-developers.com/lg-g2/development/lp-5-0-2-kernel-3-4-107-dorimanx-1-0-lg-t3102512
Then install greenify, and hibernate all the unnecessary apps.
This should solve the issue.
Click to expand...
Click to collapse
Thanks for the quick reply!
I'll try out greenify, though there aren't many unnecessary apps running (i uninstalled all the bloatware first thing, when I rooted).
And about the custom kernel, it's something I've never tried, so I have a couple questions.
Will it wipe my device, or break TWRP, root, or Xposed? (Sorry, didn't see the answer on that forum)
Will a TWRP backup I make be able to fully restore my device to it's current condition?
Is everything that is supported on my device be supported with that kernel? (Apps, etc. Don't know a whole lot about how kernels work, so I don't know)
Thank you!
Jtpetch said:
Thanks for the quick reply!
I'll try out greenify, though there aren't many unnecessary apps running (i uninstalled all the bloatware first thing, when I rooted).
And about the custom kernel, it's something I've never tried, so I have a couple questions.
Will it wipe my device, or break TWRP, root, or Xposed? (Sorry, didn't see the answer on that forum)
Will a TWRP backup I make be able to fully restore my device to it's current condition?
Is everything that is supported on my device be supported with that kernel? (Apps, etc. Don't know a whole lot about how kernels work, so I don't know)
Thank you!
Click to expand...
Click to collapse
Hi,
Even you uninstalled bloatware, the apps you use daily could be running in background and taking all those rams. So whenever you play a game or dont use a certain app, just go to greenify and hibernate. Since you have xposed installed, you can do more than that such as u can stop sync , etc.
About the kernel, it has a ram management settings and cron task.
Ram management dont need to be altered. It has some preset profile so if you seek performance, just choose performance or if u need battery , select battery profile etc.
Cron task is useful because it will do alot of things automatically. For example, it will release ram at certain amount of time from the apps , it will restart google play service since that could be an issue , etc.
All you need to do is take a nandroid backup just to be safe. Then download Dorimanx Ota from playstore and it will detect ur device and show u which version of kernel is available. Then download that, go to recovery, flash it, and you will see three app installed : Synapse -- will give you all the details of ur setup including cpu speed, temp etc for monitoring purposes
Dorimanx settings - this is the main settings of the kernel. You will see a P icon on top, tap it and choose your desired profile.
Color management : It is as the title says, just leave it be.
Then use your device, check your ram and report back. Hopefully it will resolve your issue.
Wow. Dorimanx did a lot more than I was expecting.
Downloaded the app, downloaded the kernel, flashed it no problem, went through and checked out synapse.
Went into the Dorimanx settings, and set it to the "Performance" profile.
Immediate improvement.
The whole phone seems a lot more snappy, and I switched back and forth between a 1080p60 YT video, facebook, and twitter with absolutely no problem.
Free memory when idle (no apps open) stays around 1gb; it used to be about 500mb before.
Tested a few games for the heck of it, and it actually seems to have improved game performance somehow. (It seems to have overclocked my CPU to 2.5ghz, though, so that makes sense.)
Temps stayed at around 58-60c while running a few Cardboard apps, so it seems fine.
Thanks for the help iubjaved! This has fixed my issue and then some! Ah, the wonders of the Android dev community.
Jtpetch said:
Wow. Dorimanx did a lot more than I was expecting.
Downloaded the app, downloaded the kernel, flashed it no problem, went through and checked out synapse.
Went into the Dorimanx settings, and set it to the "Performance" profile.
Immediate improvement.
The whole phone seems a lot more snappy, and I switched back and forth between a 1080p60 YT video, facebook, and twitter with absolutely no problem.
Free memory when idle (no apps open) stays around 1gb; it used to be about 500mb before.
Tested a few games for the heck of it, and it actually seems to have improved game performance somehow. (It seems to have overclocked my CPU to 2.5ghz, though, so that makes sense.)
Temps stayed at around 58-60c while running a few Cardboard apps, so it seems fine.
Thanks for the help iubjaved! This has fixed my issue and then some! Ah, the wonders of the Android dev community.
Click to expand...
Click to collapse
No worries, happy to help. I gave you advice based upon my experience using all those .
Feel free to post in XDA if you need any sort of help, you will find many that will give you insights and stuff to solve your issue.
GL :good:
As many others here I started to have mmc_read and mmc_write errors with my N910F plus freezes and restarts or no boot. For me is another case of programmed obsolescence from our beloved Samy as I previously had with the Note 2 chip bug. I supposed that the problem comes from overheating (from a short-circuit or a failing transistor) and I got confirmed. The phone cpu and gpu go up to 90-100deg Celsius. In case you still want to keep your phone and save money until the Note 8 is out here is a possible workaround:
- In case you get mmc errors when flashing with odin you have to take out the battery an keep them both somwhere cool for 15 minutes. Then flash immediatly after starting in download mode, before is heating again.
-If you managed to boot and root you can install Kernel Adiutor or something similar and keep the processors at a max frequency around 1000MHz .
For me it worked and after 2 weeks of testing all kinds roms with repartitioningn, nand erase etc. I have a working if little less performant phone for a week now.
Edit: Device Control is another app that seem more stable and it has a thermal dedicated control over CPUs. Even with intensive use the phone doesn't freeze now. It still needs to be cool to boot.*I also flashed RamKernel and I don't know it KernelAdiutor works with factory kernel.
Edit2: Wakelock app with level 4 setting > 3 days and going with no lag and no restart. So maybe all above is wrong...