[Q] Input / Scrolling Lag on Samsung ROMs - T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting

Howdy,
My T-Mobile Note 4 hangs for about 2 seconds every few seconds while typing and scrolling. The text catches up after the hanging.
I have tried several different Samsung-based ROMs and they all exhibit this issue.
CyanogenMod does not exhibit this issue and runs very smoothly.
I'd leave it at that, except I do like to use the Gear VR.
Curiously, some ROMs like TekXODUS run great until after the first reboot, and then the problem returns. I've tried a few different kernels, just to see what happens, and there doesn't seem to be an impact.
I noticed on this last ROM flash the fingerprint scanner registration works on first boot but not after reboot (I get the "try rebooting" error), but I'm not sure if that could be related.
Can anyone help me understand:
What tools I have available to troubleshoot this?
How to tell what updated or changed after first reboot?
Or guide me in any way? It's driving me nuts.
Some supplmental information:
I cannot be sure exactly what model this phone is, since I bought it off Craigslist and the sticker on the back is gone. (Dumb I know, I only thought to check the IMEI through the menu)
It reports as a N910T with a valid IMEI but this whole thing has me wondering. Any help in determining what this thing actually is would be helpful as well.
Thank you!

outsmartbullet said:
Howdy,
My T-Mobile Note 4 hangs for about 2 seconds every few seconds while typing and scrolling. The text catches up after the hanging.
I have tried several different Samsung-based ROMs and they all exhibit this issue.
CyanogenMod does not exhibit this issue and runs very smoothly.
I'd leave it at that, except I do like to use the Gear VR.
Curiously, some ROMs like TekXODUS run great until after the first reboot, and then the problem returns. I've tried a few different kernels, just to see what happens, and there doesn't seem to be an impact.
I noticed on this last ROM flash the fingerprint scanner registration works on first boot but not after reboot (I get the "try rebooting" error), but I'm not sure if that could be related.
Can anyone help me understand:
What tools I have available to troubleshoot this?
How to tell what updated or changed after first reboot?
Or guide me in any way? It's driving me nuts.
Some supplmental information:
I cannot be sure exactly what model this phone is, since I bought it off Craigslist and the sticker on the back is gone. (Dumb I know, I only thought to check the IMEI through the menu)
It reports as a N910T with a valid IMEI but this whole thing has me wondering. Any help in determining what this thing actually is would be helpful as well.
Thank you!
Click to expand...
Click to collapse
Its all about the kernal. And setting it up properlly. Using a controller such as synapse or kernal aduitor. And setting up the kernal. Uping the cpu minimum threshold and using a cpu gov..
I must say your lucky in your purchase and finding out that the device is a T..
Flashing the wrong kern on a device can produce unwanted results..
I suggest Ael. Or emotion kern. And follow the op as to settings and speed and battery life..
Rom choice is crucial as well. Im running darth staker COD6 atm with a custom kern overclocked at 2688 and there is no lag...[emoji16]
Sent from my SM-N910T using Tapatalk

Flashvetrin said:
Its all about the kernal. And setting it up properlly. Using a controller such as synapse or kernal aduitor. And setting up the kernal. Uping the cpu minimum threshold and using a cpu gov..
I must say your lucky in your purchase and finding out that the device is a T..
Flashing the wrong kern on a device can produce unwanted results..
I suggest Ael. Or emotion kern. And follow the op as to settings and speed and battery life..
Rom choice is crucial as well. Im running darth staker COD6 atm with a custom kern overclocked at 2688 and there is no lag...[emoji16]
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
Thank you very much for the advice regarding synapse and working on the Kernel. I've got CM12 back on it for a bit for my sanity as well as for a trip I'm about to take, but when I come back I'll try some fiddling. Thank you!

outsmartbullet said:
Thank you very much for the advice regarding synapse and working on the Kernel. I've got CM12 back on it for a bit for my sanity as well as for a trip I'm about to take, but when I come back I'll try some fiddling. Thank you!
Click to expand...
Click to collapse
Your very welcome..
Cm should run smooth and clean..
The tw stuff is were the tweaking comes in..
I am happy to help if you decide the leap...
By this thread or pm..
Travel blessings on you..[emoji4]
Flashvetrin

Related

Nexus One charging at 106F ~Froyo

my nexus one is charging on a regular basis around 106-7 F. I know there is another thread about this issue but the question was not resolved. So does anyone have experience with this issue. Is it a defect or dangerous? I have OSmonitor installed, this si where I am reading my temps. I also notice the CPU usage is pegged around 98-99%..is this normal?
I heard using setCPU with a charging profile can solve this problem if you have root?
No, it is not normal for the cpu to be maxed out while charging. Are you using the car dock or a wall charger?
nexous one
mine does the same thing all the time its not going to damage your phone at all
my phone has got about 120 F on car doc
my phone is perfect just set your set cpu for fail safe and your all good
You probably could use SetCPU to solve this problem, but the fact that your CPU usage is so high in the first place means there is something going wrong - my guess would be a rogue app.
Try downloading a task killer from the Market. Kill each app running one at a time then check your CPU usage. You'll soon find the culprit.
sn95chico said:
my phone has got about 120 F on car doc
Click to expand...
Click to collapse
Yeah I'm starting to see the problem with the phone having a metal casing. Not good when it's summer and you have to place it under direct sunlight for extended amounts of time, while using navigation AND charging
That thing can get burning hot alright.
Are you using froyo 2.2?
I have had the same problem; I also have random periods of high cpu use when not charging as well. This issue is not caused by problem apps either. I must reboot to fix the issue, sometimes I must reboot several times until the cpu load is back to normal.
I am not sure it is a bug or a hardware fault. Maybe a quick call to HTC and/or google is in order.
I will also try to reapply the 2.2 update.
Marine6680 said:
I am not sure it is a bug or a hardware fault. Maybe a quick call to HTC and/or google is in order.
Click to expand...
Click to collapse
Been there, done that. I opened a thread asking other users about the problem, and even mailed HTC's support. In the end I decided to try flashing the stock 2.1 rom again to see if the problem persisted, and it didn't.
I'm pretty sure it's not a hardware problem, but you might want to install eclair too and see if it works for you.
frandavid100 said:
Been there, done that. I opened a thread asking other users about the problem, and even mailed HTC's support. In the end I decided to try flashing the stock 2.1 rom again to see if the problem persisted, and it didn't.
I'm pretty sure it's not a hardware problem, but you might want to install eclair too and see if it works for you.
Click to expand...
Click to collapse
I bet your heat issues are related to cpu loads or staying at high frequencies like mine. Sometimes the phone does not feel like it is really running as hard as the system monitors say, though it may still get hot.
Where can I find the older ROM? I thought the bootloader would not allow going to older ROMs, or maybe I am mistaken.
I am re-flashing the leaked 2.2 update to make sure there was no issue with the original install. I am also using the copy my GF downloaded when I sent her the instructions on the off chance that my download was corrupted in some small way; unlikely but hey. I do think that the original flash may have gone wrong, as mine hung and never rebooted after the flash was complete; I had to manually reboot. Lets hope this fixes it.
This issue may be more widespread than we realize, as many people do not actively monitor their cpu or notice/worry about the heat after charging. I do believe that these leaked ROMs send debug data to google, I remember reading something along those lines; these are internal test ROMs after all. Maybe this is a reason that 2.2 is not out yet, this and other bugs found during real world use.
Marine6680 said:
Where can I find the older ROM? I thought the bootloader would not allow going to older ROMs, or maybe I am mistaken.
Click to expand...
Click to collapse
What I did was follow this guide up to the point where you have a stock eclair rom, then not upgrade to Froyo. Keep using that for some time, see whether the phone gets hot or not, THEN (if you want) move back to Froyo.
I am using the wall charger hat came with the nexus one. I am also running Froyo 2.2... can I set a CPU fail safe without my phone being rooted? Also what is a quick to check if my phone is rooted? I just bought this Nexus One from someone. I know on my G1 it was rooted bc I had Superuser permissions.
Using OSmonitor I can sort the processes by their CPU load and the one process that always has the highest load is " /init" which always has around 85-96% of the load. You can also kill these processes directly inside of OSmonitor and I have tried killing " /init" to no avail.
The fastest way I can think would be installing Lamppu, then trying to use it to light up the camera flash. If it works your phone is flashed, if it doesn't it's not.
As for your other questions... sorry, i don't know. I hope someone else can help you.
foethalove said:
Using OSmonitor I can sort the processes by their CPU load and the one process that always has the highest load is " /init" which always has around 85-96% of the load. You can also kill these processes directly inside of OSmonitor and I have tried killing " /init" to no avail.
Click to expand...
Click to collapse
Thats a system process so you can not kill it.
Going to test my GFs nexus and see if she has these issues as well.
I restored my N1 to the factory image, the updated back through each update to 2.2; so far so good. My GF's N1 has been running fine since I really started watching it, so I figured it would hurt to try to restore and redo the update.
No 100% cpu load during charging any more!
i am using the Motorola charger and my phone is not getting hot at all. with the charger that comes in the box for the N1 it seems to heat up.
Still had the CPU load get stuck at 100% today; though charging is not forcing 100% loads any more.
By the way, how do you measure how busy the processor is? How do you know that it's at 100%?
frandavid100 said:
By the way, how do you measure how busy the processor is? How do you know that it's at 100%?
Click to expand...
Click to collapse
System monitor apps, some will even put a little icon in the notification tray that shows current cpu load.

[Q] Serious Dialer Lag

Ok I am having some serious dialer lag. I am talking up to a minute to actually dialer a number that I have put in or chosen a contact before it actually dials. I am running the 2.1 update and don't know if this was an issue before this update as I just got the phone wihin the last month and downloaded the update right away.
I do use Advanced Task Killer and have killed everything before attempting to make a call but it is still just a laggy. I have also gone in and killed processes that are running like Sprint TV. Still have major lag issues.
Is there a way to fix this? I am getting so frustrated and am about to return the phone to Sprint!
For as cool as the Sense UI is, I don't think it was quite ready for the Hero.
Plus there are bugs that have been talked about quite a bit in the official 2.1 update for the Hero.
Hero + Sense = Dialer lag. Even after rooting and running a (mostly) much cleaner flavor of version 2.1, any rom I installed still had lag in the dialer app.
I finally scrapped Sense altogether and went with a vanilla aosp rom (darchdroid) and the whole device, including the dialer, runs smooth as butter. No lag at all.
Thank you!! I did try and run Drachroid 2.8 but it just kept looping on me so I do have another rom installed at the moment and will wait for a fix for 2.8. Any other Vanilla roms you would recommend?
brookegray said:
Thank you!! I did try and run Drachroid 2.8 but it just kept looping on me so I do have another rom installed at the moment and will wait for a fix for 2.8. Any other Vanilla roms you would recommend?
Click to expand...
Click to collapse
It's possible that the bootloops happened to you because of the overclocked (OC) kernel in DarchDroid. Some phones cannot boot at overclocked speeds and will just bootloop while trying to load up.
The latest DD 2.8 already comes with an undervolted (UV) kernel, which some phones can boot better than the regular OC kernel, so it may just be that your phone doesn't like OC at all. Lots of phones here are like that.
Try flashing and booting DD2.8 on a FULL battery. You'll have a much better chance booting an OC kernel on a full battery, and while it's plugged into the charger still.
Another good Vanilla ROM I really liked was Ic3Rom, but it is no longer kept up so it's not as current as DD or the 2.2 Cyanogen Froyo ROM.
Good luck!
Try turning off the dialer sound in settings. That fixed the lag for me.
If you try the latest froyo nightly, it should boot, it's capped at 691- which is still overclocked but seems like everyone can boot.
Sent from my HERO200 using XDA App
Help: Sprint tech Actually Sent Me Here to Root my Phone!
mkhopper said:
I finally scrapped Sense altogether and went with a vanilla aosp rom (darchdroid) and the whole device, including the dialer, runs smooth as butter. No lag at all.
Click to expand...
Click to collapse
I've been complaining to Sprint about the lag since before 2.1. Last night a Sprint tech said to come here for an "unofficial" way to get my phone running smooth, including rooting it to make it do things that aren't "supported." So after searching around here I see posts about Nandroid, rooting, backing up, restoring, and flashing roms. I've rooting iPod Touches but never a phone. I want to try this while I have hours to kill at work. Forgive the shortcutting but can you:
1. Point me to an updated step by step guide.
2. Point me to an updated recovery image.
3. Point me to an updated ROM that you PRAISE.
4. Pray for me.
Thanks,
Ken
kenwhittaker said:
Forgive the shortcutting...
Click to expand...
Click to collapse
Welcome to XDA! Just as an FYI, many of us here don't take too kindly to this. We have had to put in our time searching and reading -- it's only fair that you should too.
That being said, this thread will tell you how to root and will include a recovery image: http://forum.xda-developers.com/showthread.php?t=694572
That's all you get from me Now it's up to you to browse around and find a ROM that you like best. No one here can tell you which one the "best" one is....it's all about personal preferences and tastes. Browse the Development forum and try several ROMs. Also check the Themes and Apps forum for cool extras. You'll soon find what you like.
Good luck, and make sure you do PLENTY of reading here before doing anything to your phone.
chromiumleaf said:
Welcome to XDA!
Click to expand...
Click to collapse
Thank you. I'm well on my way. Rooting as I type. I'll check out the Dev threads.
I am running a non OC version of aloyuisus and i am loving it nothing ever lags i don't run task killers. I get great battery life, last me all day with moderate use, if i tether i always make sure its plugged in otherwise its never plugged in until late night. I listen to Audible and mp3s and probably make about 1 - 1.5 hrs worth of calls a day.
no random reboots either,
Nannuq said:
I am running a non OC version of aloyuisus
Click to expand...
Click to collapse
Thanks buddy. I'll look for a download link for that one. I just dropped to RUU 2.27.651.5 so I can root.
brookegray said:
Ok I am having some serious dialer lag. I am talking up to a minute to actually dialer a number that I have put in or chosen a contact before it actually dials. I am running the 2.1 update and don't know if this was an issue before this update as I just got the phone wihin the last month and downloaded the update right away.
I do use Advanced Task Killer and have killed everything before attempting to make a call but it is still just a laggy. I have also gone in and killed processes that are running like Sprint TV. Still have major lag issues.
Is there a way to fix this? I am getting so frustrated and am about to return the phone to Sprint!
Click to expand...
Click to collapse
I had this same problem. Even after rooting and installing fresh 2.3.3 it wasn't much better. I was almost to the point of taking the phone back to sprint when i found Cyanogenmod 6. I started with test 4 which was still pretty buggy but the current nightly that is out is awesome. FroYo is the best thing that has ever happened to my phone. No Lag, EVER.
RocStar629 said:
i found Cyanogenmod 6.
Click to expand...
Click to collapse
The 5MP Cam, preview, and video camera? No video playback problems? I need to find that one!
brookegray said:
Ok I am having some serious dialer lag. I am talking up to a minute to actually dialer a number that I have put in or chosen a contact before it actually dials. I am running the 2.1 update and don't know if this was an issue before this update as I just got the phone wihin the last month and downloaded the update right away.
I do use Advanced Task Killer and have killed everything before attempting to make a call but it is still just a laggy. I have also gone in and killed processes that are running like Sprint TV. Still have major lag issues.
Is there a way to fix this? I am getting so frustrated and am about to return the phone to Sprint!
Click to expand...
Click to collapse
this is a bug that was never fixed by htc when 2.1 was released and finalized. do a google search, lots of people are having this issue. no fixes for it either as the hero was left behind by htc.
Actually darch fixed the lock screen lag in his latest kernels. It's amazing
Sent from my HERO200 using XDA App
danaff37 said:
Actually darch fixed the lock screen lag in his latest kernels. It's amazing
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
hes talking about the dialer lag.
chromiumleaf said:
Good luck, and make sure you do PLENTY of reading here before doing anything to your phone.
Click to expand...
Click to collapse
That one statement can't be said enough.
Read, attempt to comprehend, read some more and then do the work.
There are some apps and / or scripts nowadays that will give you "1-click root", but I frown on these to be honest. There's too much "magic stuff" going on behind the scenes that you're not aware of and if an issue pops up, it's harder to backtrack to figure out what went wrong.
1-click root apps are fine, later on down the road when you're comfortable with the process and just want to get it done, but manually running through the steps to root, backup and finally flash a new rom is the best way to go.

Random crashes and reboots on Thrillseeker 3.1

I installed Thrillseeker 3.1 about 2 weeks ago, and have been noticing a few things. Sometimes the phone stops responding to touches for a while, like its locked up, or lagging, or maybe the wrong CPU governor. I don't know what's going on. Sometimes it randomly resets. One repeatable problem is that if I turn Wifi on, then off, then on again, the phone resets.
I have tried the 1.30Ghz kernel included in 3.1, the 1.38Ghz kernel, the 1.0Ghz "Saver" kernel, and the 3.12 update, but the same reset-on-wifi problem persists.
Is anyone else having similar problems? Simple fix?
I would try reflashing back to stock. Reinstall CWM, then try installing the ROM again.
Beyond that, maybe you should PM the guy who made the rom.
brianosaurus said:
I installed Thrillseeker 3.1 about 2 weeks ago, and have been noticing a few things. Sometimes the phone stops responding to touches for a while, like its locked up, or lagging, or maybe the wrong CPU governor. I don't know what's going on. Sometimes it randomly resets. One repeatable problem is that if I turn Wifi on, then off, then on again, the phone resets.
I have tried the 1.30Ghz kernel included in 3.1, the 1.38Ghz kernel, the 1.0Ghz "Saver" kernel, and the 3.12 update, but the same reset-on-wifi problem persists.
Is anyone else having similar problems? Simple fix?
Click to expand...
Click to collapse
I haven't had the reboot problems since 3.12 update from 3.11 clean install. Have had lag issue a couple times..for me restarting holo launcher corrected...tried to recreate wifi issue bit is working for me. All three kernels are very similar the saver has 1.3 and 1.2 disabled and the hotplug gov tweaked
Also posting this in my thread might get you more help.. since your running thrill seeker its ok to post problems you are having in that dev thread as others may be having same issues and ill see it quicker and try to help fix it if I can.
Sent from my LG-P925 using xda premium
yeah, i'm a noob
I'll try going back to stock and then reflash the latest thrill seeker. I would have posted in the dev forum, but I don't have 10 posts yet, so I'm restricted from posting in dev. only 8 more to go
3.12 hasn't had a random reset on me, just the wifi reset, but that one "works" every time.
Thanks,
brian
found lag problem and found possible fix
lag problem on thrillseeker 3.11/3.12 appears to be the CPU somehow resetting the Max MHz to 100MHz after the phone sleeps for 10-15 mins. Having Romtoolbox installed, then adjusting the CPU sliders quickly bypasses this issue. Although a true fix is in the coding, this workaround appears to be permanent once preformed. At least we now know it is not a flaw in the Rom as far as an overload or hang-up problem. I have not experienced the Wifi issue yet. If I can get a heads-up on how to induce it, I can look into it. Great work on the Rom!
problems im having
The rom itself is near perfect to me...I give thanks to all that put the hours and hardwork into this
I am a complete noob so any help or answers I will greatly appreciate. The only trouble I have from rom so far is if I'm using the browser while its plugged in.. might be a bad install after all. I really jumbled a few things like not making a nandriod. So I'm kinda stuck with with out a return to stock option...I have been trying to work through this but im a bit unsure how to get a stock Back on here. ..????? Any help....... back to rom I love thrillseeker 3.1....I been testing what I need in a rom and well I couldn't be happier that this rom seems to to do the job and then some....everything works perfect ....like I said the only thingthat seems fuzzy is when I plug in to wall charger and then it gets glichy.....
cpu
I adjusted sliders as well the second one seems to revert back to 100mhz often so its not a permanent fix. It does help....
Yeah. Funny thing. My phone broke (cracked screen), so I did an exchange at best buy and this rom works just fine on the new one. I guess my old one was kind of janky on the inside.
Sent from my LG-P925 using xda app-developers app

No matter what I do, I always have problems

hello all, ive just been having these issues, their always random, either its screen of death, random reboots, google services f/c'ing, it doesnt matter what rom i flash, or if i fastboot back to stock, nothing changes, theres always "something" that goes wrong. I've tried, and tried and tried but something always seems to be messed up with this phone. I dont know what im doing wrong, I've been flashing roms for years and never had so many problems, except, I had these same issues on the nexus 5, same thing.
anybody ells going through this? or is it just me?
i have both nexus 5 and nexus 6, i know both of them very well, is there anything i can help you with? ive figured out solutions to the majority of random things theyve thrown at me..
Thanks for the help. Well, every rom i try has browser f/cs, google play f/cs random reboots sometimes it reboots and wipes cache for some reason. Sometimes its like system ui f/cs so it just does a "soft" reboot, i have audio issues even on stock, like when i get a call, the ringtone starts out real quiet then boosts all the way up, sound is distorted over 50%, i tried to up my voltage by 15mv global and that didnt help anything..... Im not sure what to do, i already switched out the phone once, i think im at the end of my 15 day byers remorse period
Sent from my Nexus 6 using Tapatalk
Andromendous said:
Thanks for the help. Well, every rom i try has browser f/cs, google play f/cs random reboots sometimes it reboots and wipes cache for some reason. Sometimes its like system ui f/cs so it just does a "soft" reboot, i have audio issues even on stock, like when i get a call, the ringtone starts out real quiet then boosts all the way up, sound is distorted over 50%, i tried to up my voltage by 15mv global and that didnt help anything..... Im not sure what to do, i already switched out the phone once, i think im at the end of my 15 day byers remorse period
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Ima jump in here and try to provide a helpful response.
The nexus 6 is the best device I've ever owned beside my beloved g2, I did have to get my nexus 6 replaced the second day I had it because of a battery issue, but no problems ever since.
As far as the Gapps force closing, try using a different set of Gapps. I prefer to use the latest version of the multirom twrp and always use Banks Gapps(pm me if you can't find them.)
Only onn two, maybe three, roms have I had soft reboots/blackscreens/systemui closes. And most of the time they can be solved with a different kernel and a bit of tuning with an app such as faux123 or kernel auditor.
Audio problems can be hard to fix, but let's make sure you can distinguish the problems from the features. An example of a common misconceptions is the audio "clipping" or "lagging" when rotating the screen. This is a feature, it is swapping the left and right channels to keep the audio correct. There is a build prop line you can edit to diable this.
The phone ringtone volume steadily increasing is also a feature in most roms, including stock. It can be found in Settings>sound and notifications> and somewhere near the vibrate option.
Sound distortion is a problem I suffered from on older roms. I eventually started using viper4android on ALL of the roms I install with the superior audio driver (power drain is unnoticeable). All the settings are super easy to use, and easy to discover while playing a song and listening to the differences. Just make sure selinux is set to permissive.
I don't think increasing/decreasing the voltage can be any good for the hardware. If your car says "premium only" then you shouldn't run regular or racing fuel, you should stick to what was intended to work. You can kill battery life, starve the cpu/gpu, increase lag and overheating when messing with voltages.
Try this.
Go get the LATEST version of twrp, go find the Pure nexus rom and download it and Banks gapps, also go find francos kernel and download the latest release.
WIPE EVERYTHING TWICE (cache, dalvik, system, data) and install ROM>KERNEL>GAPPS and reboot into your super stable phone!
Message me for anything else!
Andromendous said:
Thanks for the help. Well, every rom i try has browser f/cs, google play f/cs random reboots sometimes it reboots and wipes cache for some reason. Sometimes its like system ui f/cs so it just does a "soft" reboot, i have audio issues even on stock, like when i get a call, the ringtone starts out real quiet then boosts all the way up, sound is distorted over 50%, i tried to up my voltage by 15mv global and that didnt help anything..... Im not sure what to do, i already switched out the phone once, i think im at the end of my 15 day byers remorse period
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
what bin number does your phone have? try raising your cpu, inly at your highest cpu, by 20-30mV more. about it wiping the cache, what build android are you on? it used to do that to me all the time, but not since android 5.1.1 hit aosp.
noidea24 said:
Ima jump in here and try to provide a helpful response.
The nexus 6 is the best device I've ever owned beside my beloved g2, I did have to get my nexus 6 replaced the second day I had it because of a battery issue, but no problems ever since.
As far as the Gapps force closing, try using a different set of Gapps. I prefer to use the latest version of the multirom twrp and always use Banks Gapps(pm me if you can't find them.)
Only onn two, maybe three, roms have I had soft reboots/blackscreens/systemui closes. And most of the time they can be solved with a different kernel and a bit of tuning with an app such as faux123 or kernel auditor.
Audio problems can be hard to fix, but let's make sure you can distinguish the problems from the features. An example of a common misconceptions is the audio "clipping" or "lagging" when rotating the screen. This is a feature, it is swapping the left and right channels to keep the audio correct. There is a build prop line you can edit to diable this.
The phone ringtone volume steadily increasing is also a feature in most roms, including stock. It can be found in Settings>sound and notifications> and somewhere near the vibrate option.
Sound distortion is a problem I suffered from on older roms. I eventually started using viper4android on ALL of the roms I install with the superior audio driver (power drain is unnoticeable). All the settings are super easy to use, and easy to discover while playing a song and listening to the differences. Just make sure selinux is set to permissive.
I don't think increasing/decreasing the voltage can be any good for the hardware. If your car says "premium only" then you shouldn't run regular or racing fuel, you should stick to what was intended to work. You can kill battery life, starve the cpu/gpu, increase lag and overheating when messing with voltages.
Try this.
Go get the LATEST version of twrp, go find the Pure nexus rom and download it and Banks gapps, also go find francos kernel and download the latest release.
WIPE EVERYTHING TWICE (cache, dalvik, system, data) and install ROM>KERNEL>GAPPS and reboot into your super stable phone!
Message me for anything else!
Click to expand...
Click to collapse
Thanks for the info. As for the google f/cs, so far that was only on one rom, and i havent had it since. Only browser f/cs are what im dealing with now. As for the sound. I understand the differences between the features, this is not a feature, i know what you mean by increasing ringtone, my issue is nothing like that, its not like, the sound slowly gets louder and louder... It starts out real quiet, and then BOOM full volume. Sometimes the speakers pop a little. Its weird, because it only does this the very first time a sound is played, if i have for instance, touch sounds enabled, and go through my ringtones, i dont have any sound issues. But if i turn off touch sounds, then go back to ringtones, the very first one i select will be reeeeal low.... And then BOOM full volume. This was the very first thing i checked when i switched out phones, and the very first time i tryed it on the brand new phone it did this very same thing. I just assumed it was a known issue.
Sent from my Nexus 6 using Tapatalk
simms22 said:
what bin number does your phone have? try raising your cpu, inly at your highest cpu, by 20-30mV more. about it wiping the cache, what build android are you on? it used to do that to me all the time, but not since android 5.1.1 hit aosp.
Click to expand...
Click to collapse
bin number? do you mean BUILD number? I have the tmobile variant of the nexus 6, before i started flashing roms, the first thing i did was download the factory image of 5.1.1 for the tmobile version, which is (LYZ28E), then i found the unenforced encryption boot.img someone posted which is the same boot.img, I unlocked, flashed the stock 5.1.1 image, unencrypted the device, then went on to flashing roms, right now, im on cyanideL which is LYZ28E, and so far, ive had two reboots, one of them had wiped cache by itself apon rebooting, same sound issues, same browser force closing, i even tried chrome, which force closed the second i loaded a web page, other than that, taptalk, g+ hangouts all work fine, its just these 3 or 4 same issues with pretty much all roms
Andromendous said:
bin number? do you mean BUILD number? I have the tmobile variant of the nexus 6, before i started flashing roms, the first thing i did was download the factory image of 5.1.1 for the tmobile version, which is (LYZ28E), then i found the unenforced encryption boot.img someone posted which is the same boot.img, I unlocked, flashed the stock 5.1.1 image, unencrypted the device, then went on to flashing roms
Click to expand...
Click to collapse
ok, got ya.
which browser do you use btw?
simms22 said:
ok, got ya.
which browser do you use btw?
Click to expand...
Click to collapse
sorry, i edited my post above, I try to use AOSP, which seems to be the best, it force closes the least, but chrome immediately f/c's, firefox works pretty good too, but it has graphical glitches all over the place,
ugh..... so i just wiped everything twice and flashed pure nexus rom, and i have no service, at all... . it just never ends.
Andromendous said:
ugh..... so i just wiped everything twice and flashed pure nexus rom, and i have no service, at all... . it just never ends.
Click to expand...
Click to collapse
reboot.
try this rom, with the latest gapps, and supersu, its Terminus https://goo.gl/ojD6Z6
now i know that this rom has no issues. if you start developing issues, its either something that your doing, or defective(or something else?).
simms22 said:
reboot.
try this rom, with the latest gapps, and supersu, its Terminus https://goo.gl/ojD6Z6
now i know that this rom has no issues. if you start developing issues, its either something that your doing, or defective(or something else?).
Click to expand...
Click to collapse
well, its definitely getting interesting. I just tried optipop, and my sound was working normaly! but to my amazement, it was very laggy and system animations werent working correctly, if i backed out of a screen, sometimes it would slide down, sometimes the creen would just flash white and would switch to the last screen, if that makes any sense. I got the same thing as all roms, no network, but i went and searched for networks and it failed, but then my network signal popped up, and when i tried it a gain, tmobile popped up.
so now im trying tremindous, and its doing the same thing with the network, im testing everythnig ells now.
BTW, what kernel would you suggest?
Andromendous said:
BTW, what kernel would you suggest?
Click to expand...
Click to collapse
either elementalx, vindicator, despair, or lean kernel.
simms22 said:
either elementalx, vindicator, despair, or lean kernel.
Click to expand...
Click to collapse
Why not Franco kernel? Just a question
gee2012 said:
Why not Franco kernel? Just a question
Click to expand...
Click to collapse
he doesn't include ondemand and no oc. i know his conservative is similar to ondemand, but its not the same. and i strictly use ondemand. about oc, he made me an oc kernel that i used for a little, but its old now. amyways, i dont really use his kernel, but we are still friends
simms22 said:
he doesn't include ondemand and no oc. i know his conservative is similar to ondemand, but its not the same. and i strictly use ondemand. about oc, he made me an oc kernel that i used for a little, but its old now. amyways, i dont really use his kernel, but we are still friends
Click to expand...
Click to collapse
How is OC for batterylife? Is there a big difference when you OC to say 3Ghz and what about heat issues or do you undervolt?
gee2012 said:
How is OC for batterylife? Is there a big difference when you OC to say 3Ghz and what about heat issues or do you undervolt?
Click to expand...
Click to collapse
i get from 5-6.5h sot using 3033mhz/300mhz ondemand/deadline. and the n6 doesnt have a heat issue. in fact, i have a hard time getting it over 75C whwn im pushing it to try and get hot.
simms22 said:
i get from 5-6.5h sot using 3033mhz/300mhz ondemand/deadline. and the n6 doesnt have a heat issue. in fact, i have a hard time getting it over 75C whwn im pushing it to try and get hot.
Click to expand...
Click to collapse
Ok, running Terminus with the latest hellscore kernel and i cant believe it but everything is working good so far. Gonna test some more now. Thanks for the help simms
Andromendous said:
Ok, running Terminus with the latest hellscore kernel and i cant believe it but everything is working good so far. Gonna test some more now. Thanks for the help simms
Click to expand...
Click to collapse

CPU small cores do not stop, big cores not working

So, my issue is as the title shows.
The A53 cores do not stop, and A57 cores only work like 0-1 core at a time, usually doing nothing.
Which causes my phone to be heating up whenever it isn't sleeping, sometimes drains battery even when charging at 2A.
I'm using E6533(dual sim version), and it happened when I updated my phone to 7.1.1(32.4.A.0.160) from 7.0.0(32.3.A.2.33) firmware with flashtool.
Yes, I've rooted my phone, but just for removing shutter sounds.
I tried to rollback to my TWRP backup, factory reset, rollback to 32.2.A.0.305, using custom ROM(lineage), quite everything I know, but nothing worked.
Does anyone have a clue of what might be the problem, and what might work?
Thank you.
baconbeacon said:
So, my issue is as the title shows.
The A53 cores do not stop, and A57 cores only work like 0-1 core at a time, usually doing nothing.
Which causes my phone to be heating up whenever it isn't sleeping, sometimes drains battery even when charging at 2A.
I'm using E6533(dual sim version), and it happened when I updated my phone to 7.1.1(32.4.A.0.160) from 7.0.0(32.3.A.2.33) firmware with flashtool.
Yes, I've rooted my phone, but just for removing shutter sounds.
I tried to rollback to my TWRP backup, factory reset, rollback to 32.2.A.0.305, using custom ROM(lineage), quite everything I know, but nothing worked.
Does anyone have a clue of what might be the problem, and what might work?
Thank you.
Click to expand...
Click to collapse
did u tryed to install a custom rom? or a stock but flashing a kernel?
op3n said:
did u tryed to install a custom rom? or a stock but flashing a kernel?
Click to expand...
Click to collapse
I was using stock ROM, but while trying to fix the issue, I've tried custom ROM too. Though nothing has changed…
baconbeacon said:
I was using stock ROM, but while trying to fix the issue, I've tried custom ROM too. Though nothing has changed…
Click to expand...
Click to collapse
i think is normaly to run even 1 cpu. to me is working permanently 2 - 2 from big, and 4 from little and battery is ok. is normaly to bicom hot our *****es z4; u want to say is permanently hot even is in standby or blabla?
op3n said:
i think is normaly to run even 1 cpu. to me is working permanently 2 - 2 from big, and 4 from little and battery is ok. is normaly to bicom hot our *****es z4; u want to say is permanently hot even is in standby or blabla?
Click to expand...
Click to collapse
Well, if that's normal, this shouldn't be an issue. Though I do wonder where's the big little concept gone.
Did it ever occur to you guys that it might be dynamic hotplugging and a specific configuration/setup is being used ?
Or is it in your case really being buggy and broken ?
You left something working in the background and monitored how the cores behaved ?
Using different apps ? (say: kernel adiutor [or kernel adiutor mod], EX Kernel Manager, CPU Z, etc.)
My situation has improved, so I'll update my situation, hopefully it'll help someone.
After updating to stock 7.1.1(without modifications), my phone got just very hot while the screen was on., consuming more than 2A.
Rolling back did solve the problem(becomes normal heat), but as for me, I chose to use lineage OS, which was great. The only drawback I'm having now is that the camera button's function isn't as versatile as the stock ROM, especially while opening the camera app from sleep state, is a bit unstable.
A great thanks for all of you guys for giving me advices.
My situation has improved, so I'll update my situation, hopefully it'll help someone.
After updating to stock 7.1.1(without modifications), my phone got just very hot while the screen was on., consuming more than 2A.
Rolling back did solve the problem(becomes normal heat), but as for me, I chose to use lineage OS, which was great. The only drawback I'm having now is that the camera button's function isn't as versatile as the stock ROM, especially while opening the camera app from sleep state, is a bit unstable.
A great thanks for all of you guys for giving me advices.

Categories

Resources