Related
I know there are countless threads related to G2x Problems but none of the threads are focusing on isolating the reasons of Freezing Issue. I have recently upgraded my phone from Galaxy S Vibrant to G2x and i have to say i love the hardware and performance. Only Issue for me is random freezing.
After using the phone for 2 weeks and trying 3 roms
1. Stock
2. EB 1.04
3. Dark Sinister 1.1
I have come to a conclusion that kernel and rom is not the solution. At least not for me.
So i will try to solve the problem using hardware testing.
From my past 2 weeks experience.
1. Phone Freezes at night during charging
2. Phone Freezes when ever i turn off/on wifi and bluetooth and gps and Data (4g/3g) (Still have to figure out which of them is the cause. Cause i usually turn all off when i need to save battery).
Test Day 1
For Reason 1
I am using SetCpu and have changed Min from 216 to 312Mhz. I am trying this because i think very low cpu usage in standby for a very long period causes the phone to freeze. Its a Hunch i am not sure.
For Reason 2
I will keep wifi, Bluetooth and GPS off.
I will keep 4g/3g Data On all the time.
To My Surprise its been 16 hours no freeze. It includes charging at night. Lets see how long i can go without a freeze. Upon freezing i will make some changes.
Update 31/5/2011 (Test Day 2)
Ok its been more than 40 hours and not a single crash...
I removed the following possibilities as well....
It wont crash upon excessive usage.
Also Normal Heat up does not cause the crash.
As i have been playing Samurai II Vengeance all day long... Until I ended it. Several times charging along playing. I even played it on TV using HDMI. Not a single crash. I used to have around 3 crashes a day on stock rom when i unboxed my new G2x.
I also started using GPS from today. So lets see how it goes. I will update it every 24 hour.
Update 3/6/2011 (Test Day 5)
Ok i am considering Random Freezing On standby as solved because i havent had a single freeze at night after setting CPU Clock at 312 MHz using SetCPU. There are also other comments that back up my solution. I am considering this the solution of one problem.
2nd Issue of freezing while using cell phone apps is because of certain applications that are either buggy or not compatible with tegra Platform. For that i will start another thread with individual application testing for all apps that can cause the system to freeze or crash.
Please Discuss apps System Bloat-ware/User Apps that cause your G2x to Crash or Freeze in the following thread i created:
http://forum.xda-developers.com/showthread.php?p=14399089
Thanks for all the feedback.
Luckily I dont get that issue, buy I think this is a good test :u
Good point. I have not had these issues but i do have trinity kernel and minimum speed is 300
G2x with CM7 and trinity kernel
All you have to do is be careful what apps you install. I've had the phone for over a month and the one time it rebooted or froze was when I used an app the phone didn't agree with.
I am almost certain that people are experiencing reboots and freezing because of the apps they have on their phone. Hopefully the update will solve the problem because it shouldn't be that way.
Sent from my LG-P999 using XDA App
In my opinion, the shut down has to do with temperature of the phone. As long as I keep the phone cool by not charging and multitask with other things, then my phone is fine.
garrychau said:
In my opinion, the shut down has to do with temperature of the phone. As long as I keep the phone cool by not charging and multitask with other things, then my phone is fine.
Click to expand...
Click to collapse
I used to think the same thing but the problem is my phone gets hot and works fine. I am almost positive it has something to do with an issue in the kernel that's being exposed by certain apps. My Xoom on release had reboots and SOD and it went away with app updates and removals. It also has Tegra 2
Sent from my LG-P999 using XDA App
mobilehavoc said:
I used to think the same thing but the problem is my phone gets hot and works fine. I am almost positive it has something to do with an issue in the kernel that's being exposed by certain apps. My Xoom on release had reboots and SOD and it went away with app updates and removals. It also has Tegra 2
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Do you or @kangxi remember what Apps gave you issues?
it has to be a driver issue, its virtually the only explanation for why devs have not hammered it out yet or even CM7 team for that matter... it has problems on pure AOSP which leaves drivers or overheating (unlikely)... LG has to come up with the fix because they know their drivers and hardware better than everyone else...
Well the obvious problem I see is that they are all based on the stock rom. Try using one build from AOSP or a CM variety.
I didn't stay stock long but I did have reboot using the leaked Gingerbread (which is what EB is built from). I don't follow it but one is based off the stock 2.2.2 rom and the other is based off the leaked 2.3.3 rom.
I had nothing but problems with the stock roms. Thus your problem I think. Move over to Bionic, CM7, Gigglebread, or something.
I tested my phone and I didn't have a reset in like 5 days (which then my battery died overnight because I forgot to plug it in). I usually crackflash the CM nightlies and haven't had any problems with reboots or any issues requiring a reboot (aside from the flashlight killing audio, but just don't use it).
There are definitely two problems - software and the battery. I used to way more problems until I exchanged the battery for a new one and that solved most of my issues. The issues that remain are definitely software based.
tackleberry said:
Good point. I have not had these issues but i do have trinity kernel and minimum speed is 300
G2x with CM7 and trinity kernel
Click to expand...
Click to collapse
Thanks for this information/ Changing the minimum speed didnt affect the battery life but it has survived two nights without crashing. So i am planning to keep it at 312Mhz min.
kangxi said:
All you have to do is be careful what apps you install. I've had the phone for over a month and the one time it rebooted or froze was when I used an app the phone didn't agree with.
I am almost certain that people are experiencing reboots and freezing because of the apps they have on their phone. Hopefully the update will solve the problem because it shouldn't be that way.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
I Completely Agree with you. Some Applications do cause system crashes. But I have removed all the t-mobile bloatware and i only have few games and GPS apps. All games are from tegra zone. So I am sure they are supported.
For GPS App i am using Copilot and it didnt crash on me once.
I just installed setcpu and set minimum to 312. I'm keeping everything else the same to see if this change has any difference. Will report back.
Sent from my LG-P999 using XDA App
Looks like you are gaining progress. Sounds like keeping the processor revved up a little more does the trick.
It would be a simple fix for people to try that have reboot issues. I can't get mine to reboot, so unfortunately I cannot help you. My contribution was to resist from flashing for as long as possible to test how long I could get my "uptime" to. I got up to 127 hours when I passed out without charging it.
I'm running 20 hours now because I forgot to charge it again (seems to be my only problem, lol).
Looks like you may have fixed your rebooting issues. It sounds feasible that the clock speed could be causing it. I never had a reboot so I can't help you out but I can tell you that I have a profile under SETCPU that clocks it at 216 min and 216 max when the display is off and I don't have a problem. I wonder why the low clock speeds would only effect certain devices? Maybe it's certain apps that stay running in the background (since there poorly written) that require higher clock speeds than what the G2X gives at idle?
jrwingate6 said:
Looks like you may have fixed your rebooting issues. It sounds feasible that the clock speed could be causing it. I never had a reboot so I can't help you out but I can tell you that I have a profile under SETCPU that clocks it at 216 min and 216 max when the display is off and I don't have a problem. I wonder why the low clock speeds would only effect certain devices? Maybe it's certain apps that stay running in the background (since there poorly written) that require higher clock speeds than what the G2X gives at idle?
Click to expand...
Click to collapse
I've definitely noticed that the G2X wakes up faster and smoother (fade in from screen off) when min is set to 312mhz that's for sure. if this is all it will take to stop the reboots, I'll be super happy because otherwise this phone is just amazing.
mobilehavoc said:
I've definitely noticed that the G2X wakes up faster and smoother (fade in from screen off) when min is set to 312mhz that's for sure. if this is all it will take to stop the reboots, I'll be super happy because otherwise this phone is just amazing.
Click to expand...
Click to collapse
Have you noticed any changes in battery usage? I haven't really played around with SETCPU much but can the clock speed be set lower and if it can, have you tried slightly lower settings than 312mhz?
y are u guys using setcpu? and its def cuz the min is too low faux has his at 400 and no problems morfic also has his a little higher then what is it i think 216?? thats too low thats y setcpu isnt supported yet.....pimp my cpu
Someone asked me a question earlier. Only app I had issues with was fring. Soon as I opened it and started playing around with it, phone rebooted.
I uninstalled and it never happened again.
Sent from my LG-P999 using XDA App
mobilehavoc said:
No clue what you're trying to say but setCPU works fine. At startup for first time I selected Tegra2 and it works great. I have max set to 1000 and min to 312mhz (default was min to 216mhz). I'm running stock ROM but with root. that's all.
Click to expand...
Click to collapse
well thats y it works for u, u cant overclock over a thousand mhz so in ur situation ur ok i guess it only applies for people running a custom kernel then setcpu doesnt work, then u would need pimp my cpu
The main problem with my G2X is the sleep of death, which happens a lot. I get occasional reboots too, but not too often. I tried flashing EaglesBlood 1.05 and then CM7 nightly (7/6), which I'm on now, and I still get sleeps of death and reboots, with perhaps reduced frequency but still bad. Maybe it's the battery, though I don't have overheating/charging/battery drain issues, so I'm not sure what the problem is and if it's hardware or software. Any advice on what I should do would be appreciated - thanks!
I enabled "stay awake" and flashed faux's oc kernel and haven't had an sod in weeks on the stock rom.
regP said:
I enabled "stay awake" and flashed faux's oc kernel and haven't had an sod in weeks on the stock rom.
Click to expand...
Click to collapse
Wouldn't that drain your battery much faster?
Also, I only seem to get the SOD when the phone is charging overnight, and I have a damn screen off profile set to underclock too, not even the lowest frequencies either so it cant be the freeze that that causes sometimes. Tho when it does and I figure out it is frozen asleep, it is usually hot. Might have to either get new battery or replacement. Tho what seems to heat up the most is the area around the camera, so I don't know if the battery or CPU are to blame.
No. Stay Awake only takes effect when your phone is plugged into a power source. Give it a try. I used to get 1 SOD per day. Since i made those changes I've had none in over a month. I posted the same thing in other SOD related threads but no one seems to care.
Thanks regP - I enabled Stay Awake and it seems to help. I've only had one SoD since. My new theory is that it relates to heat (leaving phone in the sun, running too many apps etc.). I've also noticed I don't get an SoD at work, where I get no reception and it's air-conditioned...might be related.
You also need to flash Faux's OC kernel. Even if you dont OC it gets rid of the faulty 300hz frequency that is believed to be part of the problem. Do that along with stay awake and you should not see any more SOD or reboots.
I've noticed I only ever got SOD when using any different kernel than what's in the original ROM. I have been on CM7 since RC1 and have been updating each nightly since and not touched the kernel and have not had a single SOD since, even when charging overnight. Only when I would try Faux kernel or Trinity kernel I would get SOD's.
I dunno then. completely stock for mean means sod and reboots. gingerbreak leak means sod and reboots. stocks + days kernel and stay awake means no sod or reboots. buddy of mine also cured his problems the same way.
For me stock froyo and gingerbread solves the problem.Initially when there was a call waiting sods used to occur, not in any other situation.I tired latest cm7 nightly with fauxs kernel,MIUI with fauxs kernel (and yes wiped cache , wiped dalvik cache and fix permissions and stay awake) but still sods.Then the stock froyo / gingerbread solves the problem for me.Hope this helps somebody.But my point is can I install the stock kernel with cm7 or MIUI ?.
viraj071 said:
For me stock froyo and gingerbread solves the problem.Initially when there was a call waiting sods used to occur, not in any other situation.I tired latest cm7 nightly with fauxs kernel,MIUI with fauxs kernel (and yes wiped cache , wiped dalvik cache and fix permissions and stay awake) but still sods.Then the stock froyo / gingerbread solves the problem for me.Hope this helps somebody.But my point is can I install the stock kernel with cm7 or MIUI ?.
Click to expand...
Click to collapse
no, miui and cm7 are both built from AOSP code and thus won't work with the stock kernel.
I guess I got lucky... never encounter the SOD or Reboot. Running cm nightly 163... I only update nightly when I notice major change only from change log.
Sent from my LG-P999 using XDA App
regP said:
no, miui and cm7 are both built from AOSP code and thus won't work with the stock kernel.
Click to expand...
Click to collapse
So can you suggest any other kernel I should try to stop the sleep of death ?
I have two G2x - Stock Froyo and kernel, manually restart once per day - no SOD or async reboots. Both G2x did suffer from SOD (with or without heat) and reboots. Manual restarts are not as sexy as 3rd party kernels and roms, but it works.
My wife uses her G2x as an alarm clock - she gets in beds, manually shutsdown the G2x, restarts it, plugs into the charger, and it wakes her up in the morning. EVERY DAY.
viraj071 said:
So can you suggest any other kernel I should try to stop the sleep of death ?
Click to expand...
Click to collapse
my sod issues stopped when I enables "stay awake". never used anything but the included kernel of whatever Tom I decide to use.
What is the best solution for this? Makes me think i wasted good money on getting 2, for me and my girl. I tried that "stay awake" and same, shuts off out of nowhere. Ive flashed both faux kernel, same results. I dont experience it with CM but for me, stock its just more responsive BESIDES the shutoff. And Weapons rom just has too much addons.. Now people are saying that the SGS2 isnt all that because of benchscores.. And i wanted that phone.. But they make it seem like it isbt a big step forward.
Sent from my LG-P999 using Tapatalk
noodles2224 said:
What is the best solution for this? Makes me think i wasted good money on getting 2, for me and my girl. I tried that "stay awake" and same, shuts off out of nowhere. Ive flashed both faux kernel, same results. I dont experience it with CM but for me, stock its just more responsive BESIDES the shutoff. And Weapons rom just has too much addons.. Now people are saying that the SGS2 isnt all that because of benchscores.. And i wanted that phone.. But they make it seem like it isbt a big step forward.
Sent from my LG-P999 using Tapatalk
Click to expand...
Click to collapse
Our phone at 1 ghz has surpassed the gs2 and 1.2 ghz
Sent from my LG-P999 using XDA App
If missing with software and settings dont work you may just have a bad phone.
regP said:
I enabled "stay awake" and flashed faux's oc kernel and haven't had an sod in weeks on the stock rom.
Click to expand...
Click to collapse
Thanks for this. I'll be sure to use the "Thanks" button when i have enough posts. I'd been leaving the phone screen on in my pocket (using an alarm clock app) because it would SOD anytime i used the lock button. Working better already.
I keep on getting SODs ONLY when there is a call waiting in the background and this happens only with CM7,MIUI.When I flash the stock gingerbread or even weapons G2x,EaglesBlood ROM the sods that occur during call waiting vanish. Can anyone help me here ? I tried fauxs kernel along with Stay awake and increasing the minimum CPU frequency but failed. Any help will be appreciated.
For the people that SOD occurs on the charger, try another charger (instead of stock LG charger). I tried the Motorola micro USB charger which put out only 550mA (which came with the H730 bluetooth) and the SOD vanished.
Probably over heating with the LG charger which puts out 1000mA
i experience alot of lags and hangs in menu. how can this be fixed. i just bought it and i wanna throw it away!?
hard reseted it.....and the problem appears again afer 1 day of usa. soft reset works well for 1-2 hours then the same!
shi**y phone!
just upgrade to 2.3.4 , i think this will clear ur problem...
We would use lagfix if the devs made it
Sent from my GT-I9001 using XDA App
gangstar said:
i experience alot of lags and hangs in menu. how can this be fixed. i just bought it and i wanna throw it away!?
hard reseted it.....and the problem appears again afer 1 day of usa. soft reset works well for 1-2 hours then the same!
shi**y phone!
Click to expand...
Click to collapse
You realy have 2 options :
1. Go to warranty with it (if you have one)
2. If you don't have warranty just flash android 2.3.4 and I assure you that this will be fixed
larry200ro said:
You realy have 2 options :
2. If you don't have warranty just flash android 2.3.4 and I assure you that this will be fixed
Click to expand...
Click to collapse
Bulls**t.
From the 5 SGS+ users I know, every single one of them (including me) has the sceen/menu lag problem, and we all have different Android versions, 2.3.3, 2.3.4, not to mention different branding.
I contacted Samsung and they can't (or won't) fix it.
Mikolak28 said:
Bulls**t.
From the 5 SGS+ users I know, every single one of them (including me) has the sceen/menu lag problem, and we all have different Android versions, 2.3.3, 2.3.4, not to mention different branding.
I contacted Samsung and they can't (or won't) fix it.
Click to expand...
Click to collapse
can you describe what do you mean by screen/menu lag?
Mikolak28 said:
Bulls**t.
From the 5 SGS+ users I know, every single one of them (including me) has the sceen/menu lag problem, and we all have different Android versions, 2.3.3, 2.3.4, not to mention different branding.
I contacted Samsung and they can't (or won't) fix it.
Click to expand...
Click to collapse
All using TWLauncher? Have you tried another launchers (GO Launcher EX runs smoothly in my phone)?
Mikolak28 said:
Bulls**t.
From the 5 SGS+ users I know, every single one of them (including me) has the sceen/menu lag problem, and we all have different Android versions, 2.3.3, 2.3.4, not to mention different branding.
I contacted Samsung and they can't (or won't) fix it.
Click to expand...
Click to collapse
A reason might be a underclock of the processor in order to increase the battery life. You might want to install ROM Toolbox and check at what frequency is the processor working (the device will need to be rooted)
You can also check if the processor is getting hot >43 degrees(battery booster on the market can help you with that)
Please reply with response and if my post helped press on thanks
I tried using different launchers - didn't help.
As to the processor frequency thing - it might very well be the case, since the screen wakes up instantly when I'm listening to music (so using more processor power).
I'll check that out as soon as I figure out how to flash 2.3.4
Mikolak28 said:
I tried using different launchers - didn't help.
As to the processor frequency thing - it might very well be the case, since the screen wakes up instantly when I'm listening to music (so using more processor power).
I'll check that out as soon as I figure out how to flash 2.3.4
Click to expand...
Click to collapse
I'l advise you on how to flash it...give me a PM when you are available
2.3.4 not yet available ota
After Upgrading to 2.3.4 rooting and removing twlauncher I have no lag problems any more, ADW, Launcher Pro and Zeam are all working just fine. I know of others that have upgraded to 2.3.4 and still have a 2s lag when waking the phone so IMHO removing twlauncher may be key....
Yeah, but by removing TW, won't Kies stop working?
ETA:
After rooting my phone and installing CPU Master, I can honestly say it is, as mentioned before, because of the CPU.
It's usually down to 250mhz ondemand when sleeping, and when i bumped it up to 800 performance, it instantly turned on, no delay.
Well I personally don't see the need for Kies apart from providing the USB drivers so that doesn't really bother me...... but if you were a big Kies user then I guess that would be a show stopper .....
Mikolak28 said:
Yeah, but by removing TW, won't Kies stop working?
ETA:
After rooting my phone and installing CPU Master, I can honestly say it is, as mentioned before, because of the CPU.
It's usually down to 250mhz ondemand when sleeping, and when i bumped it up to 800 performance, it instantly turned on, no delay.
Click to expand...
Click to collapse
Personally I didn't remove TWLAUNCHER but just froze it(in case I need it later). I also made a backup with it and installed go launcher. I am very satisfied.
Edit : application is Titanium Backup (I think the best application there is for android)
I did what you said, and it still hasn't changed the screen sleep lag.
It might be a tad bit quicker, but not a lot.
This is a duplicate thread with http://forum.xda-developers.com/showthread.php?t=1284850
Basically there is nothing you can do except increase your cpu frequency which will decrease (drastically) your battery life.
I'm afraid that I can't agree with it being a CPU frequency scaling issue. My CPU frequency is also going down to 245Mhz on no or low demand and I have no lag...
igor_999 said:
I'm afraid that I can't agree with it being a CPU frequency scaling issue. My CPU frequency is also going down to 245Mhz on no or low demand and I have no lag...
Click to expand...
Click to collapse
Mikolas is refering to the delay the phone has when trying to unlock it. It takes about 2.5 seconds for the screen to turn on.
I also have no lag when waking up the phone .... after pressing home or power I get the lock screen in under a second. BTW if I monitor the current CPU frequency with setCPU then I can see it scale the frequency down to 245 while the screen ist still on and experience no lags when resuming phone use ..... if your experiencing lags of 2.5s then IMHO it must have another cause.
Running Synergy r73
Synergy was giving me pretty good battery life, but I wanted more so I went ahead and got SetCPU. When I got my first few random reboots I didn't think of SetCPU because I had recently unlocked and flashed. I kept getting those same issues with rebooting so I re-installed everything and found that not installing SetCPU kept my phone from randomly rebooting.
As far as SetCPU tweaks, all I really did was try to use Smartassv2 (tried ondemand and standard) and setup a profile that brought down clock speed whenever the screen was off or when I was using navigation/music player with the screen off. Anyone currently having similar issues with SetCPU and figured out what's causing them? I was able to eek out quite a bit more when it came to battery life (even with 3-5 reboots through the charge cycle) and would like to resume use of SetCPU.
On some ROMs (Even just certain ROM builds for that matter) the tweaks they have applied, especially some kernel tweaks are know to interfere and cause problems with SetCPU such as the random reboots. I would recommend uninstalling SetCPU and see if that fixes your problems. If not I'd head over to the synergy thread and read/ask what they recommend for CPU tweaking
Sent from my SCH-I535 using xda premium
shimp208 said:
On some ROMs (Even just certain ROM builds for that matter) the tweaks they have applied, especially some kernel tweaks are know to interfere and cause problems with SetCPU such as the random reboots. I would recommend uninstalling SetCPU and see if that fixes your problems. If not I'd head over to the synergy thread and read/ask what they recommend for CPU tweaking
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Yeah, I uninstalled SetCPU and it seemed to fix the problem. I forgot I have over 10 posts now, wasn't used to being able to post up in the developer threads.
http://youtu.be/6XZSef6fuKU?t=21s
Could this be a hardware issue and worth RMAing? I'm running Franco Kernel r32 at the moment and someone said it could be that so I'm going to try going back to stock for a while to see if that solves the problem. Aside from that though, does anyone know what the problem could be?
edit: Forgot to mention, this isn't my video. The video was just to show you what the sound is. It happens to me without a bug report being created.
This is not an issue.
Just before it happens you pressed create bug report.
That usually takes a few seconds to create the report which is when you are hearing the distortion.
A bug report only usually happens when something misbehaves.
It creates a log of what was happening at the time and is quite an intensive task for the few seconds it takes.
It's likely that the CPU was unable to keep playback smooth while it was performing the log.
If it only happens when creating the log and no other times then do not worry about it.
Just for your piece of mind. I just tried the exact same thing.
Playing music.
Take bug report.
3 distortions happened during the time it was collecting.
Once complete no problems.
So I have the exact same behavior as you. And I'm not even slightly concerned that there is a problem
Sent from my Nexus 5 using xda app-developers app
AliMusa said:
http://youtu.be/6XZSef6fuKU?t=21s
Could this be a hardware issue and worth RMAing? I'm running Franco Kernel r32 at the moment and someone said it could be that so I'm going to try going back to stock for a while to see if that solves the problem. Aside from that though, does anyone know what the problem could be?
Click to expand...
Click to collapse
Alex240188 said:
This is not an issue.
Just before it happens you pressed create bug report.
That usually takes a few seconds to create the report which is when you are hearing the distortion.
A bug report only usually happens when something misbehaves.
It creates a log of what was happening at the time and is quite an intensive task for the few seconds it takes.
It's likely that the CPU was unable to keep playback smooth while it was performing the log.
If it only happens when creating the log and no other times then do not worry about it.
Just for your piece of mind. I just tried the exact same thing.
Playing music.
Take bug report.
3 distortions happened during the time it was collecting.
Once complete no problems.
So I have the exact same behavior as you. And I'm not even slightly concerned that there is a problem
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
On top of that, it may be related to a power saving setting on the custom kernel. Try changing governors/ increasing CPU frequency....
and playing around with the kernel features. The kernel is hot supplying enough CPU power to handle the bug-report process (or any other heavy process) + the music app at the same time.
GUGUITOMTG4 said:
On top of that, it may be related to a power saving setting on the custom kernel. Try changing governors/ increasing CPU frequency....
and playing around with the kernel features. The kernel is hot supplying enough CPU power to handle the bug-report process (or any other heavy process) + the music app at the same time.
Click to expand...
Click to collapse
Sorry, I forgot to mention that that's not my video, just an example of the sound. I don't get that noise when a bug report is sent, it's random.
AliMusa said:
Sorry, I forgot to mention that that's not my video, just an example of the sound. I don't get that noise when a bug report is sent, it's randm.
Click to expand...
Click to collapse
Its ok, the answers still apply to your or any similar case. Could happen with different music apps sometimes when phone is sleeping.
GUGUITOMTG4 said:
[/COLOR]
Its ok, the answers still applies to your or any similar case. Could happen with different music apps sometimes when phone is sleeping.
Click to expand...
Click to collapse
Interesting. So this isn't a hardware issue and I shouldn't RMA the phone? Is there anything that'll fix it eventually?
AliMusa said:
Interesting. So this isn't a hardware issue and I shouldn't RMA the phone? Is there anything that'll fix it eventually?
Click to expand...
Click to collapse
I gave the potential solution on my first post.
Also, if it doesn't work, try flashing another kernel.
GUGUITOMTG4 said:
I gave the potential solution on my first post.
Also, if it doesn't work, try flashing another kernel.
Click to expand...
Click to collapse
I'm skeptical about messing around with the kernel since I have no idea what anything means, nor what they do. I just knew that FKU was a set and forget kernel so that seemed like the best option for me. As of now, I'm running stock and seeing if the problem happens again so we'll see. Hopefully it doesn't.
AliMusa said:
I'm skeptical about messing around with the kernel since I have no idea what anything means, nor what they do. I just knew that FKU was a set and forget kernel so that seemed like the best option for me. As of now, I'm running stock and seeing if the problem happens again so we'll see. Hopefully it doesn't.
Click to expand...
Click to collapse
It may be ok now that you are stock..
Now that you are into flashing kernels, you first need to how they work, at least understand what the settings are for.
learn here about governors http://forum.xda-developers.com/showthread.php?t=1369817
Just raise the minimum CPU frequency up by one step if it bothers you.
It's 100% not a problem with the phone.
Is your screen on or off when it happens.
The best explanation I can think of is;
Your phone has a quad core 2.3 GHz processor.
Most of the time it is running at 1 core 0.3ghz in order to save power.
If something happens while your listening to music. Say an email starts coming through.
Your phone takes a small amount of time increasing the speed of your processor to better handle the tasks it's performing.
It looks like during that small amount of time it can't handle and the music skips.
Then as the speed increases it continues playback.
Again this is likely only noticeable on francos with the settings you have for the kernel.
Sent from my Nexus 5 using xda app-developers app
This happens to me all the time and I never create I bug report
Sent from my Nexus 5 using Tapatalk
The custom kernel is at fault. It's due to the minimum freq. being too low. Either raise the min frequency or switch back to the stock kernel. I have yet to experience this on my stock Nexus 5.
El Daddy said:
The custom kernel is at fault. It's due to the minimum freq. being too low. Either raise the min frequency or switch back to the stock kernel. I have yet to experience this on my stock Nexus 5.
Click to expand...
Click to collapse
Yeah, I'm on stock kernel right now. I just wanted to try out a custom kernel because I heard it makes the battery like a lot better and it seemed like it was, but then again I didn't really give the stock kernel a chance.