I notice that whenever I play music (Pandora or Google Music) with the screen off and a bunch of recent applications, the sound will skip and stutter. This only happens when the screen is off AND when I have a bunch of recent applications open. It sounds like an issue with how JB is handling RAM, but I have 80-90% ram usage at most when it happens; or perhaps is an issue with the wakelock under heavy RAM usage. If I clear all the recent applications by holding the home button down and clicking the trash icon, this problem goes away.
Phone Info:
- Teshxx's stock T-889 rom odexed (03-05-13) 4.1.2
- Baseband T889UVALK8
- Model: GT-N7105 (I could rename to T-889 but I believe this is relevant to the issue)
Attempts to resolve:
- Wiped dalvik cache and regular cache
- Installing newer versions of Teshxx's stock odexed rom
- Wiped app data from Google Music and Pandora
Potentially related:
- I deleted the stock music player and musicFX app
- I deleted some other miscellaneous apps
- I have some tasker profiles that address both Pandora and Google Music (one is a trigger to open Pandora, the other is to increase volume of Google Music)
- I have not tried and would like to avoid doing a full system wipe
Im completely stock and listen to pandora several hours a day. Usually while driving to and from work.
No issues for me.
Could be an issue with your ROM.
IAmSixNine said:
Im completely stock and listen to pandora several hours a day. Usually while driving to and from work.
No issues for me.
Could be an issue with your ROM.
Click to expand...
Click to collapse
Do you usually have the screen off and have a bunch of recent apps?
Same happens to me with LG O3D in every music player (only while screen off). Even If I Use only 70 % of ram
Sent from my LG-P920 using xda app-developers app
Jinra321 said:
Do you usually have the screen off and have a bunch of recent apps?
Click to expand...
Click to collapse
Screen is off when im driving.
Ive gone days with out rebooting my phone, and i dont go in and stop them. So yes recent apps has what ever has been opened in between reboots.
Probably a ROM issue. I am back onto stock with my gs3 (Waiting on note 2) and have never had those issues. O have had them on different ROMS though.
I can have tons of apps open and screen off and no issues on stock. Shouldn't be a RAM issue either as 2G is plenty.
Sent from a galaxy far away!
I encountered a simular problem on my Samsung infuse tracked it down to cpu throttling I'd check governer and scheduler may be some screen off power save bias built in to rom maybe
Sent from my SGH-T889 using xda app-developers app
SIGMAxB said:
I encountered a simular problem on my Samsung infuse tracked it down to cpu throttling I'd check governer and scheduler may be some screen off power save bias built in to rom maybe
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
I do believe it may be related to CPU throttling as well. I do not have powersaving enabled and also do not have have any governing apps. I have better battery stats to track my CPU speeds and battery stuff, but I'm not sure how to set governing without an app.
Jinra321 said:
I do believe it may be related to CPU throttling as well. I do not have powersaving enabled and also do not have have any governing apps. I have better battery stats to track my CPU speeds and battery stuff, but I'm not sure how to set governing without an app.
Click to expand...
Click to collapse
With a script
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Are you using voodoo sound?
Could be ROM, kernel, CPU settings, etc. This happened to me last week with the CM nightlies. I installed an update & my music started stuttering like crazy when the screen was off. Turns out I had the CPU settings customized for a special kernel but hadn't reinstalled that kernel, so the phone was trying to manage the stock CM kernel with settings for the custom kernel.
This used to happen to me before I switched to Perseus kernel. Since then I don't have the issue. Could you try that?
Sent from my SGH-T889 using xda app-developers app
I tried doing a full wipe and installed teshxx's N7105 t-mo rom (4/09/13) and did not use any throttling apps (everything else stock). The music was still skipping with the screen off, but I tried setting my minimum CPU speed to 400mhz (from 200mhz) and the skipping stopped (300mhz still skips). So I'm positive it's a problem with CPU throttling now. Since it's a full wipe and I'm still having this issue, I feel that it's a hardware issue. Perhaps I should just warranty my phone.
Changed governor to on demand and all is good.
Music skipping when screen turns off
Hey guys, I didn't realize how many other people were having this problem too....
My phone is rooted and I used ROM Toolbox Pro to turn up the min CPU value from 200mhz to 400mhz and it seems to work so far. So if you can find any type of app that can up your minimum value on your CPU it might do the trick. Because that stutter is super annoying....
I will keep you guys up to date if this doesn't work. But so far so good.
I noticed the same thing on my note 10.1 tab. Fully stock, first day i got it it did that with Google play music. Only noticed it that one time though. I'll report back if it happens again.
Related
I reflashed stock JB kernel the other day and found my phone to be running very smoothly. But I can't stand the colours on my purply screen, so back to Trinity (latest stable release).
The problem is, I'm getting a lot of lag and jerkiness on Trinity. Google Now takes forever to load, responsiveness takes a hit, and it generally feels like that whole "Project Butter" has turned into cold chunks of margarine.
I did buy the Trinity app to change settings. Is there anything I should be doing with Trinity that would give me stock-like smoothness and performance? I have a feeling there is some default setting in Trinity that is supposed to be helpful for some users but for me it's just killing the experience.
Or alternately, would I get better results with Franco?
I had similar issues. Not flowing very well , reboots and crashes. Also even though I bought the trinity app changing the clock speeds made the phone very very unresponsive. Tried many times to install it but no luck. Swapped back to Franco / glados (tried air kernel which was nice for battery but a bit laggy)
Franco also has trinity settings you can play with
J
Sent from my Galaxy Nexus using xda app-developers app
Me personally had a better experience than Franco. But all the phone are different and some might like trinity and some might like Franco. Seems like yours like Franco more
Swyped on my Galaxy Nexus running AOKP with Trinity Kernel, overclocked to 1.4GHz
Personally I've had ridiculously good results with Trinity - with 384 GPU, not 512 (1536-384-Stable35). Absolute butter even when I have very resource heavy, multiple, tasks running - and havn't had a forced reboot, freeze or anything of the sort even once. Interactive/SIO, min 307, max 1190. Everything else on default (except screen colours/gamma which I changed to my liking).
That said, if the 384 GPU is also not working for you I suppose you can give Franco or the other kernels a try, every phone set probably responds a little differently to each kernel.
cmstlist said:
I reflashed stock JB kernel the other day and found my phone to be running very smoothly. But I can't stand the colours on my purply screen, so back to Trinity (latest stable release).
The problem is, I'm getting a lot of lag and jerkiness on Trinity. Google Now takes forever to load, responsiveness takes a hit, and it generally feels like that whole "Project Butter" has turned into cold chunks of margarine.
I did buy the Trinity app to change settings. Is there anything I should be doing with Trinity that would give me stock-like smoothness and performance? I have a feeling there is some default setting in Trinity that is supposed to be helpful for some users but for me it's just killing the experience.
Or alternately, would I get better results with Franco?
Click to expand...
Click to collapse
What trinity kernel are you using? I am on trinity 384 Alpha 56 and it is butter smooth... even get great deep sleep with it.
Sent from my Galaxy Nexus using xda app-developers app
cmstlist said:
I reflashed stock JB kernel the other day and found my phone to be running very smoothly. But I can't stand the colours on my purply screen, so back to Trinity (latest stable release).
The problem is, I'm getting a lot of lag and jerkiness on Trinity. Google Now takes forever to load, responsiveness takes a hit, and it generally feels like that whole "Project Butter" has turned into cold chunks of margarine.
I did buy the Trinity app to change settings. Is there anything I should be doing with Trinity that would give me stock-like smoothness and performance? I have a feeling there is some default setting in Trinity that is supposed to be helpful for some users but for me it's just killing the experience.
Or alternately, would I get better results with Franco?
Click to expand...
Click to collapse
try using supersu instead of superuser. also, update your busybox. a lot of people have issues with root apps obtaining su slowly with superuser on jelly bean, which leads to lag.
I have good flow with trinity kernels. No lag or unresponsivness
*Who needs a gs3 when you have a NEXUS*
simms22 said:
try using supersu instead of superuser. also, update your busybox. a lot of people have issues with root apps obtaining su slowly with superuser on jelly bean, which leads to lag.
Click to expand...
Click to collapse
Already doing both, thanks for the input.
I'm using 1344/307 and I also previously tried 1536/384. My phone seems to have some overheating issues so I don't want to crank it too hard... Just want to get close to stock performance.
I'll try interactive / sio. Are those essentially what the stock kernel uses?
Sent from my Galaxy Nexus using Tapatalk 2
cmstlist said:
Already doing both, thanks for the input.
I'm using 1344/307 and I also previously tried 1536/384. My phone seems to have some overheating issues so I don't want to crank it too hard... Just want to get close to stock performance.
I'll try interactive / sio. Are those essentially what the stock kernel uses?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
i like ondemand/deadline. overheating.. whats your cpu temperature? most think that their devices are overheating when it falls in the normal range. tkt comes with widgets(in the app drawer widget menu), put the no background cpu temp widget on your homescreen and youll also get a cpu temperature reading in your status bar. at 100C the thermal throttle will kick in to lower your cpu speed and cool down your device. the safety shutdown temperature is 110C, your cpu will automatically shut down at that point. 110C is only reachable if you turn off the thermal throttle in the tkt app and you are benching your phone at a high oc. otherwise, i wouldnt worry about overheating.
The other thing is I get lockups every day or three. Today I rebooted the phone and plugged in the charger while it was rebooting. The moment the screen went off the phone was locked up. Power button would not respond. Unplugging/plugging the charger did not light up the screen. Had to do a battery pull.
In fact this happened again a second time in a row. Is there a reason the phone is locking up immediately after boot if I have the charger in? I'm trying it again a third time with the charger out, letting the screen auto-sleep before I touch the phone. Okay apparently it has nothing to do with the charger.
EVERY time I start the phone up now, if I don't unlock the screen myself before it auto-sleeps, the phone locks up and auto-reboots again. WTF??
cmstlist said:
The other thing is I get lockups every day or three. Today I rebooted the phone and plugged in the charger while it was rebooting. The moment the screen went off the phone was locked up. Power button would not respond. Unplugging/plugging the charger did not light up the screen. Had to do a battery pull.
In fact this happened again a second time in a row. Is there a reason the phone is locking up immediately after boot if I have the charger in? I'm trying it again a third time with the charger out, letting the screen auto-sleep before I touch the phone. Okay apparently it has nothing to do with the charger.
EVERY time I start the phone up now, if I don't unlock the screen myself before it auto-sleeps, the phone locks up and auto-reboots again. WTF??
Click to expand...
Click to collapse
are you undervolting at all? which yrinity kernel are you using? did you happen to use franco kernel before using trinity? try using a different charger too, ive had similar issues with a certain charger before too, until i started using a different charger.
Despite the fact that I disabled "Set On Boot" in Trinity Kernel Toolbox, it does seem I'm still set to interactive/sio on boot. And check out the logcat I captured over USB when I was doing a reboot and it locked up:
http://pastebin.com/sSe9eFXT
In particular to trim out just the TKT lines and the last few lines before lockup:
Code:
D/TKTBootHelper( 1853): TKT: Boot Completed
D/TKTBootHelper( 1853): TKT: Set file permissions.
V/LockPatternKeyguardView( 299): Set visibility on com.android.internal.policy.
[email protected] to 8388608
V/LockPatternKeyguardView( 299): Set visibility on com.android.internal.policy.
[email protected] to 8388608
D/TKTBootHelper( 1853): Current Version: 3.0.38-04149-g1d1c555-dirt00:23:38|
D/TKTBootHelper( 1853): Previous Version: 3.0.38-04149-g1d1c555-dirt00:23:38|
D/TKTBootHelper( 1853): TKT: Versions match, let's restore settings.
E/vpnapi ( 1672): Function: Connect File: AndroidIPCSocket.cpp Line: 172 failed
to connect fd=38: Connection refused
E/vpnapi ( 1672): Function: Run File: LocaleChangeMonitor.cpp Line: 140 Invoked
Function: AndroidIPCSocket::Connect Return Code: -26476533 (0xFE6C000B) Descrip
tion: ANDROIDIPCSOCKET_ERROR_CONNECT_FAILED
So it would seem that right after TKT says "let's restore settings" it locks up, if the screen is off, when set to interactive/sio. Huh?
simms22 said:
are you undervolting at all? which yrinity kernel are you using? did you happen to use franco kernel before using trinity? try using a different charger too, ive had similar issues with a certain charger before too, until i started using a different charger.
Click to expand...
Click to collapse
See my post immediately after yours.
No undervolting at least that I know of. I tried cranking max screen off frequency up in case that was the cause, and tried going back to default CPU settings. Still does the same upon reboot.
But I can confirm that if I uninstall TKT completely and boot with Trinity Kernel, there is no screen-off lockup. Whatever settings were being restored by TKT were causing the phone to freeze if the screen was off. I'll leave it at that for now and give it another go when it's not so lovely and sunny outside.
cmstlist said:
See my post immediately after yours.
No undervolting at least that I know of. I tried cranking max screen off frequency up in case that was the cause, and tried going back to default CPU settings. Still does the same upon reboot.
But I can confirm that if I uninstall TKT completely and boot with Trinity Kernel, there is no screen-off lockup. Whatever settings were being restored by TKT were causing the phone to freeze if the screen was off. I'll leave it at that for now and give it another go when it's not so lovely and sunny outside.
Click to expand...
Click to collapse
delete the data for the tkt app(main phone settings, apps). dont use set on boot, its usually not a good idea. my screen off is set to 307. if you are overclocking, you have to disable smart reflex mpu or you will freeze and reboot if not other issues. turning off smart reflex is very important if raising the cpu speed. otherwise the device will try to automatically set the voltage too low for the cpu speed and itll cause freezes/reboots.
simms22 said:
delete the data for the tkt app(main phone settings, apps). dont use set on boot, its usually not a good idea. my screen off is set to 307. if you are overclocking, you have to disable smart reflex mpu or you will freeze and reboot if not other issues. turning off smart reflex is very important if raising the cpu speed. otherwise the device will try to automatically set the voltage too low for the cpu speed and itll cause freezes/reboots.
Click to expand...
Click to collapse
I didn't overclock and I didn't undervolt. What is smart reflex?
Set on boot was DISABLED, let me emphasize. Yet the logcat shows TKT restoring settings, followed up very soon with a lockup.
Sent from my Galaxy Nexus using Tapatalk 2
cmstlist said:
I didn't overclock and I didn't undervolt. What is smart reflex?
Set on boot was DISABLED, let me emphasize. Yet the logcat shows TKT restoring settings, followed up very soon with a lockup.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
does your rom have its own cpu settings? maybe theres something enabled in there?
---------- Post added at 04:40 PM ---------- Previous post was at 04:36 PM ----------
cmstlist said:
I didn't overclock and I didn't undervolt. What is smart reflex?
Set on boot was DISABLED, let me emphasize. Yet the logcat shows TKT restoring settings, followed up very soon with a lockup.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
smart reflex is a built into stock, it controls your voltages. the thing about it is that it doesnt know overclock or undervolting, so if you overclock or undervolt, it restores voltages for stock cpu speeds. which causes freezes if youre trying to overclock by setting the voltages too low.
simms22 said:
does your rom have its own cpu settings? maybe theres something enabled in there?
Click to expand...
Click to collapse
Stock yakju Jellybean flashed straight from Google image files, with the exception of Trinity.
Sent from my Galaxy Nexus using Tapatalk 2
cmstlist said:
Stock yakju Jellybean flashed straight from Google image files, with the exception of Trinity.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
did you try clearing the tkt data, or uninstalling it and reinstalling it? honestly, this is the first time ive seen this behavior. do you have any other cpu control apps installed?
cmstlist said:
I didn't overclock and I didn't undervolt. What is smart reflex?
Set on boot was DISABLED, let me emphasize. Yet the logcat shows TKT restoring settings, followed up very soon with a lockup.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yes, set on boot is for critical settings only, like frequency policy and voltages.
All trivial settings are always restored as they were set.
What ROM are you on? I jumped into the middle of this page and missed it.
Side note, if it's settings being restored, clear the app data using the option in the menu.
Sent from my SGH-T999 using Tapatalk 2
simms22 said:
did you try clearing the tkt data, or uninstalling it and reinstalling it? honestly, this is the first time ive seen this behavior. do you have any other cpu control apps installed?
Click to expand...
Click to collapse
No I do not. I will try reinstalling now since I uninstalled it completely.
morfic said:
Yes, set on boot is for critical settings only, like frequency policy and voltages.
All trivial settings are always restored as they were set.
What ROM are you on? I jumped into the middle of this page and missed it.
Side note, if it's settings being restored, clear the app data using the option in the menu.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Again, pure stock flashed straight from Google, except for Trinity.
This just happened to me today. First time it happened was early in the afternoon when I was playing Mini Motor Racing and I turned off the screen for a while. When I turned it on and unlocked my phone, the game screen was black. When I pressed the home button, it froze on me, then it rebooted. Second time, it was the same situation. Then the third time, when I was downloading a game from via my browser, it froze and restarted on me and now, I tried to transfer an obb file from a game to my phone and when it was half way done, it restarts on me. Anyone know what's going on?
Sent from my Galaxy Nexus using xda app-developers app
mini motor does that to me as well. not the gnex's fault. it just doesn't resume so well.
svtfmook said:
mini motor does that to me as well. not the gnex's fault. it just doesn't resume so well.
Click to expand...
Click to collapse
So could it be mini motor racing that's causing the reboots?
I forgot to mention that it makes a popping noise when it freezes and restarts
Sent from my Galaxy Nexus using xda app-developers app
More than likely it is mini motor. I've had apps that froze my phone that required battery pull. Deleted the app and all was fine.
Sounds pretty typical of overheating, or overclocking/undervolting. Maybe try keeping a fan on it when doing anything intense. Or you might try a kernel that lets you raise the voltages a bit. Some phones are more stable that way.
I dont know about volting. How much should I overvolt? I'm using AOKP w/ Franco kernel. My max clock speed is 1305 (previously 1420) and my min clock speed is 920.
Sent from my Galaxy Nexus using xda app-developers app
I'd try furst uninstalling the app just to see it after the pone runs properly or it keeps rebooting. The OC/UV issue is hard (at least for me) and have never given to me no good experiencies. I tried once to UV and had the same problems you're having, only solving theme by retoring setting to default.
If you're rooted, get the Trickster Mod app from the Play Store and disable Smart Reflex (all three switches) and see if the reboots stopped.
Cause apparently, that seems to be the case foe my phone (I use Faux's kernel v 21 with no smart reflex... the basic basic kernel)
sent from my mini tractor
question useless
Most kernel use Smartreflex, and if he had do this answer , i dont think it's going to undervolt under stable value for his phone
If you could provide more info about your phone specs its better, if you use OC kernel like Glados with 2 ghz, it's pretty normal, ever cpu is different
using CM10 nights can cause ( never ) bug like this, but if your phone freeze in infinite bootloop with metallic sound under is surely voltage value.
try to use your ROM's stock kernel , ( you might reflash without wipe anything your ROM and ( if needed ) GAPPS )
Well... if your post was directed to me, in that case, I'm using the non smart reflex version of the kernel. The stock kernel also uses smart reflex.
Strangely, I have to use the kernel without smart reflex... cause if I get another kernel which has the provision for smart reflex, and manually turn it off, it doesn't seem to help (or stick).
Of course, if your list wasn't targeted to me, then feel free to ignore this post
sent from my mini tractor
Been noticing this since last week. Every time I use my phone for like 1 or 2 minutes, the phone starts getting hot. Usually, it gets hot after an hour of use (Facebook, Messaging, Browser, Twitter, Play Store). Went to Performance settings in Settings, then Processor, and notice the Current CPU frequency is always at 1000 MHz, then goes down to 200 or 100 MHz when idle for a few seconds. Switched between conservative and ondemand governor, no OC. Was on PA 2.54 when this happened, but I'm on CM10 Stable now, and it's still getting hot after using it for a few minutes.
This hasn't happened to me before. Not sure if this is normal, but I just want to make sure.
My recent heat and battery drain was coming from an app. I didn't check the CPU.
I checked the battery area of the settings and found a locale add-on that was draining more juice than my screen.
sent from a secret underground bunker
It will happen if your signal is real bad or 3G is down in your area.
I don't think it's my signal. I get 2 or 3 bars almost all of the time at home with the FC09 modem.
Besides opening and/or using an app, it seems that the CPU clock will go max speed if I do something, such as scrolling. Battery is also draining quickly before this was happening to me.
Sent from my SPH-D700 using Tapatalk 2
InsaneHien said:
Went to Performance settings in Settings, then Processor, and notice the Current CPU frequency is always at 1000 MHz, then goes down to 200 or 100 MHz when idle for a few seconds. Switched between conservative and ondemand governor, no OC. Was on PA 2.54 when this happened, but I'm on CM10 Stable now, and it's still getting hot after using it for a few minutes.
Click to expand...
Click to collapse
I think that's a Jellybean-specific CPU behavior (to keep system flowing like "silk", JB put CPU at max the instant you have your finger on screen... At least that's what I heard). Try ICS/GB ROMs and see if problem persists.
Sent from HTC Incredible S @ AOKP
AndyYan said:
I think that's a Jellybean-specific CPU behavior (to keep system flowing like "silk", JB put CPU at max the instant you have your finger on screen... At least that's what I heard). Try ICS/GB ROMs and see if problem persists.
Sent from HTC Incredible S @ AOKP
Click to expand...
Click to collapse
Yeah, you're right. I even looked it up. It's part of Jelly Bean.
I'm going back to CM9 or The People's ROM.
You could try a different kernel, or lower voltage. Sorry not sure what phone this topic is for lol but that's some options. It takes a lot to get my phone hot, and I'm on jelly bean
Sent from my Galaxy Nexus using Tapatalk 2
I don't have this problem on nitest kernel with the ns4g modem
Sent from my SPH-D700 using Tapatalk 2
You likely have an issue with your settings.
If it's not an app, you probably have an issue with your performance settings.
Try turning off some of the eye-candy features in the settings. This will likely include the Cyanogenmod specific setting area as well.
That should at least help.
Ruedii said:
If it's not an app, you probably have an issue with your performance settings.
Try turning off some of the eye-candy features in the settings. This will likely include the Cyanogenmod specific setting area as well.
That should at least help.
Click to expand...
Click to collapse
It didn't help unfortunately.
I flashed CM9 earlier and the issue still exists. I'm now back on CM10 (11/22 nightly).
It's okay if this can't be resolved. I am probably gonna go back to a GB ROM.
EDIT: Issue still persists in GB. I'm guessing it could be a hardware issue? I have no idea. Back to JB. I'm still willing to try anything to resolve this. Thanks to those who posted some solutions.
Sent from my SPH-D700 using Tapatalk 2
My Note 3 randomly reboots and a factory restore hadn't solved the issue. There's no bootloop issue, it just reboots a few times a week, sometimes twice a day. Any possible solutions?
Kawaisa said:
My Note 3 randomly reboots and a factory restore hadn't solved the issue. There's no bootloop issue, it just reboots a few times a week, sometimes twice a day. Any possible solutions?
Click to expand...
Click to collapse
dont install any apps, except for the essential one, and see if it reboots. Probably it might be an app which is hogging your memory
prasanthlt said:
dont install any apps, except for the essential one, and see if it reboots. Probably it might be an app which is hogging your memory
Click to expand...
Click to collapse
You're probably right, I had like half the app store installed. I did another hard reset and will see if it happens again. Is there a way to check if there's any specific apps that are memory hogs?
I had this cleaner app that kept asking me to clear my memory because 90%+ of it was being constantly used. I figured 3GB was enough
Kawaisa said:
My Note 3 randomly reboots and a factory restore hadn't solved the issue. There's no bootloop issue, it just reboots a few times a week, sometimes twice a day. Any possible solutions?
Click to expand...
Click to collapse
Are you rooted, stock, custom? If your using a stock kernel would you have installed any apps that would require a custom kernel such as android tweaker.
This exact samething happened to me on my rooted stock S3 running a stock kernel. I installed android tweaker pro not realizing I needed to have a custom kernel installed and it caused random reboots 3 or 4 times a day. Flashing back to stock or doing a factory reset would not fix the issue I just ended up sending it back because I wasn't sure what the issue was then realized it was Android tweaker that caused the random reboots.
Sent from my SM-N900T using XDA Premium 4 mobile app
djrysk said:
Are you rooted, stock, custom? If your using a stock kernel would you have installed any apps that would require a custom kernel such as android tweaker.
This exact samething happened to me on my rooted stock S3 running a stock kernel. I installed android tweaker pro not realizing I needed to have a custom kernel installed and it caused random reboots 3 or 4 times a day. Flashing back to stock or doing a factory reset would not fix the issue I just ended up sending it back because I wasn't sure what the issue was then realized it was Android tweaker that caused the random reboots.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Running stock everything
no android tweaker installed
My note did this for a bit when I unlocked it. Called tmobile they told me it was a Gmail issue. So go. Into settings/apps disable Gmail reboot then re-enable it. It's something with how Samsung integrated it into the system.
Sent from my SM-N900T using XDA Premium 4 mobile app
I am currently running*DARTHSTALKER*v5*and Compulsion Ultimate v6. *I have been running Jovys roms and kernels for a few months already and absolutely love it. *Just recently (about a week ago) I decided to go into Trickster Mod and try overclocking it. *The phone runs fine for a while but all of a sudden out of nowhere when it is just sitting on idle it will reboot. *At least once or twice a day. *I only know this because I will wake up in the morning and I see the notification that Trickster Mod set on boot was successful. *The last 2 times it happened, I received an Exchange mail and it looks like when these emails came in, it woke the device and then it rebooted. *I installed "CatLog" from the play store to see what the logs are saying and I see about 8 of these messages around the time of the reboot:*
296 ThermalEngine E Threshold 0 Action [0] : shutdown
I know the phone is not overheating when this happens. *I am wondering if the kernel has an issue with the Intelli-Thermal Controls or something. *I did enable that and set the thresholds to 95 and 100. *If that is Celsius or Fahrenheit I do not know since it is just a number value in trickster. *I was on Darthstalker v3 a couple days ago when this started happening and I thought upgrading to v5 would fix it but to no avail. *Does anybody have any thoughts or seen this issue?
I am going to try to overclock it again to the full 2.6 GHz (2649600) but this time turn off Intelli-Thermal and see if I still get this issue. *I am hoping I don't have a faulty device. *I never had a problem until I changed the max frequency from 2265600 to anything higher. *With the device not overclocked and with Intelli-Thermal enabled I do not get this problem; only when I introduce the slightest overclock into the mix.
Changed in trickster are as follows: (everything else is stock)
--Scheduler = sio
--Governor = ondemand (I think this was stock but just in case it wasnt)
--Max Frequency = 2649600
--MP-Decision = OFF
--Intelli-Plug = ON
--Intelli-Thermal Control = ON (freq throttle = 95, core offline = 100)
Sent from my SM-N900T using xda app-developers app
so it happened again today, noticed that I have about 1GB of free ram at start up, not sure if that's normal
Hi,
I've been a lurker for a while, but made an account because I have scoured the forums for an answer to this "old" question and none of the answers have solved it for me. I wish there was a forum for people who have tried everything and have had 0% success haha.
So, sorry if this is the wrong location for this, and sorry if it has been answered already 100 times!
I have a first generation Note 3, and have recently rooted (like 4 months ago?). I got the Pandora Patcher and figured out how to get it working, so I use Pandora v5.6.1 with Pandora Patcher v3.6.1.
BEFORE I started using Pandora Patcher I did not have any stuttering (maybe because i was on the current version of Pandora? But since I've been using the Patcher it stutters after every other song for 5 seconds or more, it almost sounds like lag or something. I've tried everything short of wiping it, as it was working before i downgraded Pandora for the Patcher.
My question is, am I out of luck with the Patcher? Or is there a way for me to have my cake and eat it too? (use the patcher and not have stuttering/choppiness)
Thanks for reading, appreciate the help!
Try installing a stock version and see if that works.
And what's this patch /file that you install for?
Pp.
Thanks for the reply, I believe I have a stock version of pandora. The patcher is an app root users can get that helps you get the features of a paid subscription and other stuff. Which, I only use it so I can listen to a continuous stream, since I sleep with it on...
Try this, delete your stock pandora and patch from your files, then install this apk https://www.dropbox.com/s/n5hp7rabgoa5i9w/pandora5.5FULL.apk?dl=0
It's for pandora one free with unlimited skips and no charges.
After installing just log in with your regular pandora account and enjoy.
Pp.
Wow, I didn't know this existed, THANKS! I just did what you said and downloaded this, and it seems to have unlimited skips, but will it still time out after a few hours? you know, the "Are you still listening?" pop-up?
Much appreciated, I will have a better chance of testing this out later after work and will update to see if this is solved or not.
Don't know about "Are you still listening" pop up. I use it all the time, longest about 4 hrs. Enjoy.
Pp.
So, I've had it running the past few hours like normal, except I'm using the app you linked me. It still stutters on some songs, but not as often. It was REALLY obnoxious before, and now its fairly bearable. I really appreciate it, but I wouldn't consider this solved.
This version is MUCH BETTER though, it doesn't time-out on me, and I can skip as much as i want.
Are you running stock /rooted rom?
Or a custom rom?
You may be having an app causing some conflicts.
I'm running stock /rooted / debloated rom and it works smoothly, also running on an GS4, GTAB 2 10" and GalTab Pro 7" , getting same smooth performance on all devices.
Pp.
I'm running the stock/rooted rom v4.4.2. no custom recovery...
I do not have a debloated rom ( I didn't know that was a thing!), but if there is a bloatware causing conflicts, then that would make sense? I don't have any task killers or anything I can think of that could possibly interfere. Usually when I play Pandora, its the only app running in the foreground (to my knowledge). I'm also not sure how one would go about checking for that sort of thing...
Things I've tried but did not work for me
-delete both caches
-use a wifi app to keep wifi from being throttled when screen is turned off (which btw this happens on data 4GLTE and wifi)
-use regular Pandora app without any hacks (still stutters, I was wrong before about it working then not working)
Thank you for taking the time to help me, Pancho!
I run CWM recovery which allows me to use Romtoolbox Pro and delete all that Samsung and T-mobile junk they stuff the phones with, including Knox.
The operating system runs lighter and saves your battery.
Edit; custom recovery not needed to run Romtoolbox Pro, just root will do.
Pp.
Hey,
So I wanted to test this over the weekend to see if it worked, and it has been SOLVED!
THANK YOU SO MUCH.
Here's what I did/happened:
I saw what you said about CWM recovery, and learned that I could get Rom Toolbox Pro without it, so I did using Lucky Patcher.
Now, here's the funny thing. I remember reading in another forum somewhere that some people were able to solve their stuttering with a CPU manager. I stupidly didnt even try that assuming it wouldnt work haha. So since Rom Toolbox comes with one, I used it there.
switched the Governor to "ONDEMAND" and changed the lowest speed it could have to 300 instead of 200(default).
I did all of this on Friday 2/20 , and have used Pandora everyday since (with the Pandora Patcher, I went back because of the time-out) and no stuttering or anything. I've used Bluetooth, aux and just the phone speakers and its all fixed! I cant believe it was the CPU, and I hope I never forget that in the future haha.
EDIT 3/11/15: So, I was horribly horribly wrong about how this worked for me, and I believe I have now fixed the stuttering problem for my situation specifically (knock on wood).
Here's what has happened since I wrote this "solved" post.
I realized that the previous solution only worked on some kernels (mostly custom) but not the one that came standard with my Note 3 N900T. I also stopped using the ROM Toolbox CPU Manager, as I needed something with profiles.
So I flashed LeanKernel, and got setCPU. I use LeanKernel's InteractiveX Governor with I/O ROW, and it improved my phone overall, but specifically for Pandora stuttering, it did nothing. So I use setCPU profiles.
My setCPU profiles for Pandora (really my only profiles):
100 priority - App Pandora + screen off + charging (any ) = CPU Max 2726 - Min 422
99 priority - App Pandora + screen off = CPU Max 422 - Min 422
I originally had an issue getting the profiles to even stick/activate, but what I had to find out for myself is if you go to the Governers tab in setCPU, just check set on boot, and set in profiles, then it should work. ALSO, I learned that even with all of this going on, if I'm listening to Pandora and go look at a different app, or return to the home screen (basically putting Pandora in the background) The profiles do not work. Pandora has to be in the FOREGROUND in order for the profile to be active. When that happens, and the screen is off, I get flawless playback.
This is just for me specifically, I hope this helps someone else, as this was A LOT of trail and error... sorry for jumping the gun earlier
Thanks Pancho, from the bottom of my heart, I thank you and wish to give you plenty of internet hugs!!! Please have a wonderful day and I hope this helps anyone else that was in my predicament.
TL;DR: FOR ME PERSONALLY, I GOT LEANKERNEL AND SETCPU (USE INTERACTIVEX AND ROW), USED PROFILES FOR PANDORA + SCREEN OFF AND PANDORA + SCREEN OFF + CHARGING. THEN MAKE SURE PANDORA IS IN FOREGROUND WHEN PLAYING AND SCREEN IS OFF, THEN NO MORE STUTTER!!!