Sliding volume to zero in Jelly Bean crash -- logcat data - Kindle Fire Q&A, Help & Troubleshooting

I'm running twa_priv's JB rom (20120801) and am one of only a few people seeing a persistent crash when sliding the volume to zero (not muting, actually sliding down to zero). It's only a nuisance bug since it's easy to avoid but it's bothering me that barely anybody else can reproduce it. I've seen a few other reports in the various JB rom threads so it doesn't seem to be rom specific.
I did an 'adb logcat' and reproduced the crash several times using both Volume Control (app by RubberBigPepper) and the regular volume widget in the status bar (tablet mode). Maybe some clues in there for those smarter than I. The entire logcat is attached. Each time the crash happens the first logged event looks like this:
E/AndroidRuntime( 1425): FATAL EXCEPTION: main
Is this helpful? Anything else I can do to narrow this one down? Does anybody else care? =)
Thanks!
-S

I am also using twa_priv's JB [20120801]. Sliding volume to zero does not crash on my KF, but when I set the volume to mute, I cannot turn it back on. I need to reboot the device to get the sound back.

I'm running the same build and have neither of your 2 issues go figure eh??? You both may benefit from a good wipe front to back and a fresh flash
---------- Post added at 05:30 AM ---------- Previous post was at 05:26 AM ----------
Thepooch said:
I'm running the same build and have neither of your 2 issues go figure eh??? You both may benefit from a good wipe front to back and a fresh flash
Click to expand...
Click to collapse
In fact I have been sitting here running the volume button up and down and muting it while watching hulu trying to duplicate what your experiencing
for twenty minutes without so much as a hiccup

Thepooch said:
I'm running the same build and have neither of your 2 issues go figure eh??? You both may benefit from a good wipe front to back and a fresh flash
---------- Post added at 05:30 AM ---------- Previous post was at 05:26 AM ----------
In fact I have been sitting here running the volume button up and down and muting it while watching hulu trying to duplicate what your experiencing
for twenty minutes without so much as a hiccup
Click to expand...
Click to collapse
I'm not able to replicate the problem either.

Thepooch said:
I'm running the same build and have neither of your 2 issues go figure eh??? You both may benefit from a good wipe front to back and a fresh flash
---------- Post added at 05:30 AM ---------- Previous post was at 05:26 AM ----------
In fact I have been sitting here running the volume button up and down and muting it while watching hulu trying to duplicate what your experiencing
for twenty minutes without so much as a hiccup
Click to expand...
Click to collapse
As I am new to JB on my kindle, the volume issue for me might due to my misoperation. I really enjoy this ROM now.

Well, i think there must be some audio bug, because since i flashed i haven't had audio on build 8-1-2012. And even on build 7-22-2012 a reboot would cause audio loss. I would have to fix it by randomly playing with volume in settings.
I would really want HELP with this problem.
Sent from my MB855 using Tapatalk 2

I also have this volume problem with my Kindle. Did you find any solution or roms which do not have this bug?

I did a full wipe several weeks ago and haven't seen this crash since then. Still using twa_priv's ROM on my KF.
-S
Sent from my Galaxy Nexus using xda premium

I did a full wipe several weeks ago and haven't seen this crash since then. Still using twa_priv's ROM on my KF.
Click to expand...
Click to collapse
It worked. I did a full wipe (External, System, Factory Reset, davlik cache and cache) and the problem went away
Thanks

Once a mute, always a mute
songzi said:
I am also using twa_priv's JB [20120801]. Sliding volume to zero does not crash on my KF, but when I set the volume to mute, I cannot turn it back on. I need to reboot the device to get the sound back.
Click to expand...
Click to collapse
I am experiencing the same issue with the mute button in the notification bar. If I press mute, the little speaker will get a slash through it indicating that it is muted. Pressing the button again will not unmute it. I have to go into the settings and turn the volume up with the sliders. Sometimes i have to do this two or three times before the volume settings will take. Even with the volume turned back up, the volume indicator in the notification bar still shows the device being muted. A reboot will correct. Any thoughts?
Edit: It is doing it in the 09132012 as well as the previous build.

Moved to Q&A

Related

screen glitches and other concerns topic(pics +movie added)

I have some screen glitches and it is pretty annoying...
I notice it especially when in the browser and when the menu of the browser comes on the screen... Is this a hardware or a software problem?
Saw it on the home screen too sometimes when i want to scroll the homescreens the status bar glitches while scrolling...
Anyone noticed this?
Also when entering system task manager I always only have like 200mb free space? When i choose end all, i have like 300. So there is almost always 3/4 in use? Is this normal?
Other question:
I was trying teeter earlier, and It isn't as smooth as on other devices. The ball doesn't run smooth on the screen, it stutters especially when you tilt the phone and the ball should go fast... Anyone notice this too?
Other questions and concerns can be placed here.
I will also try to make a movie of the screen glitches...
Thanks for the answers!
Edit: So someone else posted pictures of the problem in dropdown menu in the browser, it is exactly the same as mine.
Glitch pics
And a video also from the same user:
Glitch movie
And from another user who captured the status bar glitch(that i also have):
Status bar glitch
please describe your glitches and bad teeter is it only on low battery only?
hamdir said:
please describe your glitches and bad teeter is it only on low battery only?
Click to expand...
Click to collapse
No my battery is 55% now, I played it again, and when also when trying to move the ball slowly, sometimes the balls makes a little 'jump' instead of rolling smooth...
And the glitches is, that the there are horizontal lines of the things on the screen, i don't know what could cause it?? Is it hard or software... Will try to make a little clip of it tommorow when it happens again.
r_a_c said:
I have some screen glitches and it is pretty annoying...
I notice it especially when in the browser and when the menu of the browser comes on the screen... Is this a hardware or a software problem?
Saw it on the home screen too sometimes when i want to scroll the homescreens the status bar glitches while scrolling...
Anyone noticed this?
Click to expand...
Click to collapse
I only have my phone for a day but I definitely encountered those screen glitches, i think 3 times since. It usually happened on top of the screen. I think it's only software bug(let's hope).
I did test one in three store and found it was lagging. Scrolling through different screens s sluggish very surprising and poor. The phone also froze hopefully it was software issue!!!
Anybody noticed a small blue patch on the screen? A few cases are reported in Singapore.
It can only be seen if the screen has a black background. Try using the camera app and cover the lens with your hands.
Sent from my HTC One X using xda premium
most reviewers except two reported no glitches, faulty units?
Same problems as the OP here.
All software bugs I would say, there are plenty of small software bugs/glitches I have found so far.
I think they'll release an update soon, well.. they should.
Remember many reviews were based on later firmware than is (currently) publicly available. If reviewers saw bugs in earlier firmware, then saw it fixed in final firmware, it would be unlikely that they'd mention the bugs. They wouldn't have been expecting units to reach retail before the updates (and their reviews) were available...
Sent from my Transformer TF101 using XDA
i think a lot of apps need to update for ICS and tegra 3. i don't even know what teeter is. but yeah maybe HTC has some updating to do, too.
i posted this in the other thread but got no response
reviewers who faced this related it to applied pressure on screen, when the affected area is pushed the screen might move a bit or flex and the glitch appear, can you test?
owners with the glitches should immediately contact HTC the more you complain the sooner you get a solution
we have one feedback so far
engwee said:
in my case it's not from pressure
it appears random sometimes
before I updated it I had the issue in music app where the red album art is displayed.. it always used to glitch in the middle of it
can anyone try that?
maybe it's a software bug after all
Click to expand...
Click to collapse
Hi all... I have the same glitch issue on my HTC One X. Often, in the botton of the screen, there's a wobbles but it isnt joint with the pressure of the screen.
For example, the issue doesnt appaer in the lock screen with One X on.
So... software issue? I hope...
---------- Post added at 01:24 PM ---------- Previous post was at 01:18 PM ----------
Errata corrige... the problem appears also in the lock screen...
---------- Post added at 01:43 PM ---------- Previous post was at 01:24 PM ----------
Now I'm trying to reset to the factory the smartphone.
---------- Post added at 02:03 PM ---------- Previous post was at 01:43 PM ----------
Nope... also with a reset the problem persists.
There are anyone with this problem?
bye
stefano
steveweb said:
Hi all... I have the same glitch issue on my HTC One X. Often, in the botton of the screen, there's a wobbles but it isnt joint with the pressure of the screen.
For example, the issue doesnt appaer in the lock screen with One X on.
So... software issue? I hope...
---------- Post added at 01:24 PM ---------- Previous post was at 01:18 PM ----------
Errata corrige... the problem appears also in the lock screen...
---------- Post added at 01:43 PM ---------- Previous post was at 01:24 PM ----------
Now I'm trying to reset to the factory the smartphone.
---------- Post added at 02:03 PM ---------- Previous post was at 01:43 PM ----------
Nope... also with a reset the problem persists.
There are anyone with this problem?
bye
stefano
Click to expand...
Click to collapse
the problem is sticking now?
Is there anyone WITHOUT this problem? Someone who used the phone for more than a day?
hamdir said:
the problem is sticking now?
Click to expand...
Click to collapse
yes... the problem is always there :-(
By the way, I have sent an email to HTC.
steveweb said:
yes... the problem is always there :-(
By the way, I have sent an email to HTC.
Click to expand...
Click to collapse
mate now im thinking its hardware, try to push on the affected area and see if you create interference
steveweb said:
yes... the problem is always there :-(
By the way, I have sent an email to HTC.
Click to expand...
Click to collapse
yeah best reporting any issues to HTC
I'm still thinking is a software issue
The reply from HTC... It seems a tipically "all purpose" reply for any questions!
Dear Stefano Ferri,
Thank you for contacting HTC.
Dear Mr. Stefano, regarding your enquiry, kindly try the following steps:
Please try to: enter the safe mode on your phone and check if you still have the same issue . You can enter safe mode by:
Safe mode:
Press power key to switch off the device
1. Press " power key " for power on device
2. Wait until "HTC logo" appears on screen
3. Press and hold " Volume down key " until entering OS
4. " Safe Mode " text will appears on the lower left of screen Safe mode will disable all 3rd party apps and only preinstalled apps will work, this is done because some of 3rd party apps can interfere with your phone functionality.
5. If the device is working properly in "safe mode" please try to remove the 3 party applications, or remove the latest 3rd parties that you installed..
If this doesn't resolve your issue then you need to factory data reset your phone. You can do that by:
Warning: Resetting your phone will erase your phone completely. Remember to back up your phone information and settings.
Please press MENU on the Home screen, then tap Settings > Phone storage > Factory data reset > Reset phone.
NOTE: Resetting your handset to factory or manufacturer's default setting will delete all the data stored on your phone memory, please back up your files first.
If these steps don't resolve your issue, please, immediately take back your new device to the retailer where you bought it and ask for the replacement/new device.
If you have any other inquiries, don’t hesitate to contact us again.
For further details, please go to http://www.htc.com/europe/support.aspx
Thank you so much for using HTC products.
Respect & Regards,
HTC Technical Support Team
http://www.htc.com
Let me know if I have successfully answered your question, please click here to complete this.
To send a reply to this message, please click here.
Sincerely,
Nemanja
HTC
steveweb said:
The reply from HTC... It seems a tipically "all purpose" reply for any questions!
Dear Stefano Ferri,
Thank you for contacting HTC.
Dear Mr. Stefano, regarding your enquiry, kindly try the following steps:
Please try to: enter the safe mode on your phone and check if you still have the same issue . You can enter safe mode by:
Safe mode:
Press power key to switch off the device
1. Press " power key " for power on device
2. Wait until "HTC logo" appears on screen
3. Press and hold " Volume down key " until entering OS
4. " Safe Mode " text will appears on the lower left of screen Safe mode will disable all 3rd party apps and only preinstalled apps will work, this is done because some of 3rd party apps can interfere with your phone functionality.
5. If the device is working properly in "safe mode" please try to remove the 3 party applications, or remove the latest 3rd parties that you installed..
If this doesn't resolve your issue then you need to factory data reset your phone. You can do that by:
Warning: Resetting your phone will erase your phone completely. Remember to back up your phone information and settings.
Please press MENU on the Home screen, then tap Settings > Phone storage > Factory data reset > Reset phone.
NOTE: Resetting your handset to factory or manufacturer's default setting will delete all the data stored on your phone memory, please back up your files first.
If these steps don't resolve your issue, please, immediately take back your new device to the retailer where you bought it and ask for the replacement/new device.
If you have any other inquiries, don’t hesitate to contact us again.
For further details, please go to http://www.htc.com/europe/support.aspx
Thank you so much for using HTC products.
Respect & Regards,
HTC Technical Support Team
http://www.htc.com
Let me know if I have successfully answered your question, please click here to complete this.
To send a reply to this message, please click here.
Sincerely,
Nemanja
HTC
Click to expand...
Click to collapse
Sounds correct though, if your still having screen issues after a factory reset, even after a few days - I'd get a replacement, could be faulty.
Sent from my GT-I9100 using Tapatalk

3G Periodically Shuts Off

Have Cyanogen Mod installed, constantly have 4 bars of 3G data in Brooklyn, NY.
Whenever I'm using the phone in hand, the data shuts off every 10 to 45 minutes. The only way to bring it back on reliably is to go into the settings, turn off data, put it into airplane mode, wait a few seconds, then turn it back to normal mode.
There's no "data" toggle on the top-screen slide-down applet, so this is kind of a pain in the ass to do every single time this happens.
Has anyone else experienced this and/or solved it?
I have had this on my EVO, and it may just be the ROM. I have not ran CM b/c the other ROM's that are based off CM have more features like a notification toggle for data, which would help you.
I recommend doing a full wipe and re-install of the ROM. You can use Titanium Backup to save everything and restore everything. It should be like nothing changed, and hopefully it fixes that bug. If not, maybe resort do a different version of CM or ROm altogether.
Best of luck with this, it is annoying, but not the worst problem you can get (on the bright side).
-Xont!c
srsizzy said:
Have Cyanogen Mod installed, constantly have 4 bars of 3G data in Brooklyn, NY.
Whenever I'm using the phone in hand, the data shuts off every 10 to 45 minutes. The only way to bring it back on reliably is to go into the settings, turn off data, put it into airplane mode, wait a few seconds, then turn it back to normal mode.
There's no "data" toggle on the top-screen slide-down applet, so this is kind of a pain in the ass to do every single time this happens.
Has anyone else experienced this and/or solved it?
Click to expand...
Click to collapse
Yeah, I have that issue too, but I switched to blackbean5 ROM, and I dont see it that often now, also I am running a KTOONEZ kernel, I dont know bout you but my sprint reception here in bklyn is awful.
Its still in the nightly stage and has this, as well as plenty of other problems but they are getting fixed so give it time and try the newest nightlys
---------- Post added at 11:58 AM ---------- Previous post was at 11:49 AM ----------
livito said:
Yeah, I have that issue too, but I switched to blackbean5 ROM, and I dont see it that often now, also I am running a KTOONEZ kernel, I dont know bout you but my sprint reception here in bklyn is awful.
Click to expand...
Click to collapse
Yeah I'm also using the same kernel and ROM, it works well but I want to use cm when its out of the nightly stage and finished.
blacuda said:
Its still in the nightly stage and has this, as well as plenty of other problems but they are getting fixed so give it time and try the newest nightlys
---------- Post added at 11:58 AM ---------- Previous post was at 11:49 AM ----------
Yeah I'm also using the same kernel and ROM, it works well but I want to use cm when its out of the nightly stage and finished.
Click to expand...
Click to collapse
Ah, alright. Good to know it's just a basic issue. Will update to a new build eventually. Thanks!

(Thread Closed)

Thread Closed !!
New Google's Android 4.2.1 Features
-> Photo Sphere
-> Gesture Typing
-> Multi-User Support (Tablets Only)
-> Miracast Wireless Display Support
-> Daydream
-> Notification Power Controls
-> Google Now Improvements
For More Information on Which of the above features available in CyanogenMod, Come to My New Thread T989 Official CM10.1 4.2.1 Discussion (Coming Soon)
Enjoy !!! :good:
This is very useful! I am currently running AOKP JB and I will pay attention to this thread as it geets updated so I can see which ROM has less bugs, AOKP JB by TLS, or CM10.
theandroidrooter88 said:
This is very useful! I am currently running AOKP JB and I will pay attention to this thread as it geets updated so I can see which ROM has less bugs, AOKP JB by TLS, or CM10.
Click to expand...
Click to collapse
This is why i started this Thread, So we can discuss Bugs in the latest versions. :highfive:
I heard AOKP JB is stll having SODs and RRs. Do u find anything like these?
Why do we say there are no more SOD or RR? are we just taking guesses? Haven't seen any changes that would be anywhere near relevant for fixing those.
Sent from my SGH-T989 using Tapatalk 2
algorhythm said:
Why do we say there are no more SOD or RR? are we just taking guesses? Haven't seen any changes that would be anywhere near relevant for fixing those.
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
First we have to fix our flashing methods and recoveries used. I for one haven't experienced one single RR or SoD since I started flashing official nightlies. People are probably causing these issues themselves to begin with. Expecting a fix for an issue that has no identifiable cause.. I wonder if any other phones outside the t989 forums are experiencing RR and SoDs with Jelly Bean..
Sent from my SAMSUNG-SGH-T989 using xda premium
algorhythm said:
Why do we say there are no more SOD or RR? are we just taking guesses? Haven't seen any changes that would be anywhere near relevant for fixing those.
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
running 10-10. I experienced one soft reboot after restoring apps and then running all of them (I don't blame my phone). no sod yet. i don't know if they fixed rr or sod completely but i believe they made an impact. I think people are making assumptions since the 4.1.2 update claimed "better performance and stability fixes" and the bbq log shows a lot of framework and system updates
algorhythm said:
Why do we say there are no more SOD or RR? are we just taking guesses? Haven't seen any changes that would be anywhere near relevant for fixing those.
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
We are not guessing. I said there are no SODs or RRs because I installed each update and i am pushing hard my device to get a RR. Also as i observed that there are no SODs. CM10 09-Oct Nightly is more stable than previous Nightlies. I know there are still some issues like as i stated above. We can find solutions for common problems but not major problems.
garth719 said:
running 10-10. I experienced one soft reboot after restoring apps and then running all of them (I don't blame my phone). no sod yet. i don't know if they fixed rr or sod completely but i believe they made an impact. I think people are making assumptions since the 4.1.2 update claimed "better performance and stability fixes" and the bbq log shows a lot of framework and system updates
Click to expand...
Click to collapse
Great to hear that your running latest 10-Oct Nightly. A Simple advice to you & all other users, is to restore app without data if your are using any backup tools such as TitaniumBackup etc., Restore Apps with data cause Problems.
srikanth.t989 said:
We are not guessing. I said there are no SODs or RRs because I installed each update and i am pushing hard my device to get a RR. Also as i observed that there are no SODs. CM10 09-Oct Nightly is more stable than previous Nightlies. I know there are still some issues like as i stated above. We can find solutions for common problems but not major problems.
Click to expand...
Click to collapse
Sorry, I don't mean to crap on the thread but unless you can confidently say that SODs and RRs have been fixed (changelogs, yourself writing the code, etc.), going by your own experience shouldn't be the end-all-be-all to say whether something is fixed or not. Just like with call echo, some devices are worse than others.
I see that supposedly the issue with audio and docking has been addressed. However, the docking option is still grayed out for me when docked. Just looking for audio pass-through while docked...
Been running CM10 for the past few days and updating nightlies. My issues so far:
1. No sound with Alarms, just vibrating
2. I have been told by caller that I sounded weird using phone mic, but fine with headset
3. Had phone freeze once this morning on 10/9 with touch keys lit, but screen black, had to pull battery
I am now on 10/10 and plan on doing a clean install of it this afternoon, so I'm not sure how many of these issues with persist yet
SOD RR is not fixed for me, ran latest cm10 as well as aokp nightlies
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
eight_heads said:
Been running CM10 for the past few days and updating nightlies. My issues so far:
1. No sound with Alarms, just vibrating
2. I have been told by caller that I sounded weird using phone mic, but fine with headset
3. Had phone freeze once this morning on 10/9 with touch keys lit, but screen black, had to pull battery
I am now on 10/10 and plan on doing a clean install of it this afternoon, so I'm not sure how many of these issues with persist yet
Click to expand...
Click to collapse
1. There are issues with all of the volume settings. To fix your alarm volume open the clock settings, go to volumes and chnge the volume level. It should work. You can fix all volume settings with a simple toggle. 2. Make sure you have noise suppression enabled in call settings. 3. To avoid pulling the battery hold down the power for 10-15 seconds and it will reboot.
running 10-10 with TWRP and clean install (no tdj scripts). No rr/sod for 6 hrs so far. just a soft reboot after loading a ton of apps and running them all to push my phone to the max. No issues except the ones above and a tiny camera app issue thats already been reproduced (switching from camera mode--> video mode-->panorama-->camera will cause fc). I'm starting to think this is dd material. will let you know of any rr/sods.
I'm on recent CM10 Oct10 nightly and the BLN lights stay on, even with the Oct 7 nightly.
Update: fixed my own problems. This post helped: go to menu - systems - advanced settings - sensor and uncheck and check enable keys notifications and then send yourself a text or email. It actually should work out the box mine always has. Make sure you have notifications checked off in the apps like sms and gmail.
Also check display - notification light to make sure it enabled and you can add the apps you want to have the light enabled to work
Sent from my SAMSUNG-SGH-T989 using XDA Premium HD app
on CM10: 10-10. Google Now still no voice. ( prompt voice ). also, Google Now Initializing takes forever after press on mic. I am using GAPP 0726.
garth719 said:
1. There are issues with all of the volume settings. To fix your alarm volume open the clock settings, go to volumes and chnge the volume level. It should work. You can fix all volume settings with a simple toggle. 2. Make sure you have noise suppression enabled in call settings. 3. To avoid pulling the battery hold down the power for 10-15 seconds and it will reboot.
running 10-10 with TWRP and clean install (no tdj scripts). No rr/sod for 6 hrs so far. just a soft reboot after loading a ton of apps and running them all to push my phone to the max. No issues except the ones above and a tiny camera app issue thats already been reproduced (switching from camera mode--> video mode-->panorama-->camera will cause fc). I'm starting to think this is dd material. will let you know of any rr/sods.
EDIT:
Just ran the music player for 45min on a run. no skips, nothing.. ran a 90 mb mp3 file too which usually gives my ipod trouble.. good sign
Click to expand...
Click to collapse
So is that how we're saying we don't get random reboots anymore? We just call them something else??
algorhythm said:
So is that how we're saying we don't get random reboots anymore? We just call them something else??
Click to expand...
Click to collapse
well there was a difference in this reboot because my phone didnt actually fully shut off. the "cyanogenmod" boot animation came up and the phone was ready to go in about 20 seconds. there was no usual vibration indicating that the phone has shut off and no "samsung" boot image as a regular reboot would do. call it what you will
Quote:
[email protected]: on CM10: 10-10. Google Now still no voice. ( prompt voice ). also, Google Now Initializing takes forever after press on mic. I am using GAPP 0726.
Try updating it on the market
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Laazyboy said:
SOD RR is not fixed for me, ran latest cm10 as well as aokp nightlies
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Run only One ROM. Do a clean reflash. We are not experiencing any SODs or RRs. Use only one ROM because Flashing different ROMs one after the Other will Make your device weak. The data left by the AOKP causes some errors to CM10. Thats why i said that don't restore the apps with data.

Severe Wake-Up Lag

I've heard of the usual 2 or 3 second lag for most users. They'll try to wake up their phone with the power button, but there's about a two or three second delay. I wouldn't care at all if I had that!
My problem is far more sinister. I don't have the usual wake lag. It's dynamic and unpredictable.
Let me explain. When I first boot up my phone (or restart it) it works flawlessly. No lag—nothing. Not even the three second wake lag most people get. Then, out of nowhere (I can't pinpoint when it starts) I'll try to wake it up and... nothing! The backlight will turn on (that very dim black light) along with the soft keys. They'll turn on fine, but my display will not show up. Funny thing though, sometimes I'll tap the screen and it'll vibrate as if it was on. The only way to fix this is one of two ways: restart the phone (very annoying) or turn it on and wait. Sometimes, eventually the display will kick in but I have about a second to react before it shuts off. Then, I have to press the power button twice more to turn off the backlight and turn it back on and wait for the display to kick in. If I tap and swipe to unlock, I'm mostly in the clear. But, most of the time it takes SwiftKey about 30 seconds to respond. I'll tap and tap and nothing will be written, but after 30 seconds of spamming it'll finally start to write. Then, my phone has minor/no lag while the display is still on. But, if I let it shut off, then it starts all over again. Backlight, but no display.
Sometimes I'll be lucky: I had a three day streak of no lag at all, but then it happened. It really is random, and I have no idea what could be causing this. It wasn't always this way either.
I have this rooted and am running CarbonRom (Android 4.4)
ANY help would be appreciated. Nothing seems to fix this permanently.
Try another rom, or better yet... Try stock 4.1.2 for comparison. Install the same things on it and see. It could be certain apps slowing your phone down, or lack of ram, or your setup.
Mine is on stock 4.1.2...and I'm sometimes amazed when I do pick it up and use it, like when I'm charging my other phone, at how zippy it is. It's not way slower feeling like you'd think it would be, at all.
---------- Post added at 11:13 AM ---------- Previous post was at 11:12 AM ----------
Also a cache and dalvik wipe can often help. Especially on older devices.
This is a common issue with KK ROMs & kernels. Try a JB ROM instead.
KJ said:
Try another rom, or better yet... Try stock 4.1.2 for comparison. Install the same things on it and see. It could be certain apps slowing your phone down, or lack of ram, or your setup.
Mine is on stock 4.1.2...and I'm sometimes amazed when I do pick it up and use it, like when I'm charging my other phone, at how zippy it is. It's not way slower feeling like you'd think it would be, at all.
---------- Post added at 11:13 AM ---------- Previous post was at 11:12 AM ----------
Also a cache and dalvik wipe can often help. Especially on older devices.
Click to expand...
Click to collapse
Agreed, a dalvik cache and a cache wipe will often help. What would be the best way to update to stock 4.1.2 from stock 4.0.3? It is not showing up in ota and I can't use kies or Odin as I don't have a Windows computer. Heimdall can only seem to successfully install ICS on this phone.
Sent from my SGH-T989
You could just flash a stock 4.1.2 rom... Tho its usually best to Odin stock first , then flash things 4.1.2 and higher.
Yeah, without a pc ... Not sure what you can do. Maybe you could visit someone that has Windows pc ?
You can try just flashing a stock rom, buy good chance you'd freeze at boot up.
KJ said:
You could just flash a stock 4.1.2 rom... Tho its usually best to Odin stock first , then flash things 4.1.2 and higher.
Yeah, without a pc ... Not sure what you can do. Maybe you could visit someone that has Windows pc ?
You can try just flashing a stock rom, buy good chance you'd freeze at boot up.
Click to expand...
Click to collapse
Don't know. All I know is when I try flashing 4.1.2 in Heimdall it freezes after Android is upgrading and then boot loops. I've tried wiping data, cache, and falcon after flashing and it still didn't work. I'll probably just stock with AOSPA since it is fairly stable right now and has decent battery life.
Sent from my SGH-T989
I'm running CarbonROM + WildKernel. Currently, I have no problems with wakeup lag when tapping the power button. Though, when I recieve a call, it takes several seconds for the screen to wake. I have my kernel configured for 96Mhz when screen is off. You might try increasing the base cpu frequency and see if that helps. You might also try changing your cpu governor and see if that helps.
However, your tapping the power button twice description might be indicative of something wrong with your power button. Just a thought. These particular phones are known to have issues with the power button after time.
ayr0 said:
I'm running CarbonROM + WildKernel. Currently, I have no problems with wakeup lag when tapping the power button. Though, when I recieve a call, it takes several seconds for the screen to wake. I have my kernel configured for 96Mhz when screen is off. You might try increasing the base cpu frequency and see if that helps. You might also try changing your cpu governor and see if that helps.
However, your tapping the power button twice description might be indicative of something wrong with your power button. Just a thought. These particular phones are known to have issues with the power button after time.
Click to expand...
Click to collapse
96mhz will definitely cause some things to lag on wake. Test it tho and then compare to 300. I very much doubt you'll see any difference in battery life at all.
Thanks for all the replies, and I just may have to try a ROM that's a bit older. This phone is basically ancient history now, but it suits me well. I'll try the stock JB ROM but probably won't keep it—I do enjoy having the features many custom ROMs include.
I've also installed and ran LagFix free from Google Play, and I can say it greatly reduced the frequency of the wake lag occurring. It still happens but for the most part it turns on fine.
ayr0 said:
I'm running CarbonROM + WildKernel. Currently, I have no problems with wakeup lag when tapping the power button. Though, when I recieve a call, it takes several seconds for the screen to wake. I have my kernel configured for 96Mhz when screen is off. You might try increasing the base cpu frequency and see if that helps. You might also try changing your cpu governor and see if that helps.
However, your tapping the power button twice description might be indicative of something wrong with your power button. Just a thought. These particular phones are known to have issues with the power button after time.
Click to expand...
Click to collapse
Twice in meaning once to turn off the backlight to put it to sleep and then once more to attempt to "wake" it up again.
KJ said:
96mhz will definitely cause some things to lag on wake. Test it tho and then compare to 300. I very much doubt you'll see any difference in battery life at all.
Click to expand...
Click to collapse
You are right, I just looked at the voltage tables in my ROM and everthing below 153Mhz uses the same amount of power.
I'm going to try 153Mhz for awhile and see if that helps. Thanks for bringing that to my attention.
---------- Post added at 04:58 PM ---------- Previous post was at 04:53 PM ----------
Saturable said:
Thanks for all the replies, and I just may have to try a ROM that's a bit older. This phone is basically ancient history now, but it suits me well. I'll try the stock JB ROM but probably won't keep it—I do enjoy having the features many custom ROMs include.
I've also installed and ran LagFix free from Google Play, and I can say it greatly reduced the frequency of the wake lag occurring. It still happens but for the most part it turns on fine.
Twice in meaning once to turn off the backlight to put it to sleep and then once more to attempt to "wake" it up again.
Click to expand...
Click to collapse
How much time do you wait between button pushes. On my rom, it they are I press the button twice in immediately consecutive pushes, it does take a second or two for the phone wake. However, if I wait a second or two before pressing the power button again, wakeup is almost instantaneous. I attribute this to the fact that even though the screen is powered off, it takes a little bit of time for the phone to actually go to sleep. The phone might be lagging because it has to wait for the phone to sleep before it can wake up again.

Volume wheel stops working

My volume wheel only works for the first 15 minutes or so then and then it stops working until I reboot the unit.
Any idea ? Software or hardware fix ?
A few have the same issues. Myself included. For me it was software related. Out of interest what navigation do you use.
Sent from my SM-G920F using Tapatalk
I agree, since a software reboot fixes it I'm guessing it a software. Did you find a fix ?
I'm using Waze
Waze was my culprit. Try an alternative as an experiment.
Sent from my SM-G920F using Tapatalk
Unfortunately, Waze is the reason why I bought the head unit. Although I'll try to see if that's the problem and if so ask Waze if they can fix it
Thanks
Some others have went back to an older version of Waze. The last one before the change in material design.
Some others with same problem have discounted Waze so it's a bit of a lottery.
Sent from my SM-G920F using Tapatalk
Just noticed I have the same problem as well (volume knob stops working after a few minutes, reboot fixes it for a bit, repeat). I don't know when it started as I've always just used the steering wheel controls for volume.
Kicker is that I don't use Waze nor have it installed.
Using latest (Apr 23 2016 RK3066 800x400, latest JY MCU) Malaysk ROM, basic JY headunit.
@gk66 - since you last wrote your post, have you had the problem occur again despite using the older version of Waze?
I don't use an older version. Ditched Waze completely. Use Google maps. Problem hasn't resurfaced yet.
Sent from my SM-G920F using Tapatalk
gk66 said:
I don't use an older version. Ditched Waze completely. Use Google maps. Problem hasn't resurfaced yet.
Click to expand...
Click to collapse
Ah, I should learn to read. Thanks for the info though!
I haven't done extensive testing but Waze seems to be the culprit in my case too.
Muting waze also works. I've set it to "alert only" and it's much better but still stops from time to time.
When Waze talks it lower or mute media volume, my guess is that Waze does it wrong or uses an old API, I've had problem even on my phone where media volume would stay low or stop altogether.
I'll make a bug report and hopefully they can fix it
Caddish said:
I haven't done extensive testing but Waze seems to be the culprit in my case too.
Muting waze also works. I've set it to "alert only" and it's much better but still stops from time to time.
When Waze talks it lower or mute media volume, my guess is that Waze does it wrong or uses an old API, I've had problem even on my phone where media volume would stay low or stop altogether.
I'll make a bug report and hopefully they can fix it
Click to expand...
Click to collapse
Thanks for that. Glad you've found the culprit.
Sent from my SM-G920F using Tapatalk
Waze is not the only cause, also this happens with pc radio with the latest malaysk firmware for rk3188
Nobody said it was the only culprit. Why not start a thread to identify all the culprits
Sent from my SM-G920F using Tapatalk
I'm having the same issue. Radio works fine until I launch waze, within ten minutes the knobs don't work anymore.
Since everybody is having sporadic issues, I'm actually testing out if the audio mixing you can set in Settings->GPS has anything to do with it. I always had it set to mixing, and I now put it to switch. Tomorrow I'll know more after a round trip to work.
No waze here, yet I have the same issue. Happens out of the blue, even when just running the original radio apk and no navigation at all. The SWC keeps working. Functionality returns after a reboot or a jump to the hardware settings. As the SWC always functions I don't mind TOO much but it a bit sloppy.
Tried changing the GPS settings today. Whatever I did, nothing helped, not even putting a random app that doesn't produce sound as my navigation app.
Which MCU do you all have? Mine is JY/Joyous...
Waze is not the culprit, it just happens more often when using it. Bluetooth calls (interrupting your current audio) often break it. Other apps switching audio break it too.
It is most likely some bug in the firmware related to switching the audio input.
There is no solution found yet.
---------- Post added at 11:12 PM ---------- Previous post was at 11:09 PM ----------
SilverViper2k said:
Since everybody is having sporadic issues, I'm actually testing out if the audio mixing you can set in Settings->GPS has anything to do with it. I always had it set to mixing, and I now put it to switch. Tomorrow I'll know more after a round trip to work.
Click to expand...
Click to collapse
Mine is set to Mixing 5. I haven't tried to switch yet.
---------- Post added at 11:14 PM ---------- Previous post was at 11:12 PM ----------
SilverViper2k said:
Which MCU do you all have? Mine is JY/Joyous...
Click to expand...
Click to collapse
KLD2, RK3188 SD. Came with KLD2 v2.77 firmware, now running v2.81. Both have the issue. I haven't tried flashing older firmware
I tried using tomtom as my main GPS application, same issue, so it's definitely not Waze specific. Friday I'll drive without using any GPS app and see if it still fails.
Next time as soon as I notice it failed, I'll check system log for any errors or exceptions, perhaps something stands out.
I do know that the turning of the knobs is logged in the log even after they failed and don't change volume. One of the xposed modules that shows the buttons pressed and such does not recognize turning of the knobs after they have failed...
SilverViper2k said:
I do know that the turning of the knobs is logged in the log even after they failed and don't change volume. One of the xposed modules that shows the buttons pressed and such does not recognize turning of the knobs after they have failed...
Click to expand...
Click to collapse
Hmmm. The system log still gets the volume knobs turning but not the app? That could mean the firmware is ok and the bug is somewhere in the Android audio?
shtirlitz111 said:
Hmmm. The system log still gets the volume knobs turning but not the app? That could mean the firmware is ok and the bug is somewhere in the Android audio?
Click to expand...
Click to collapse
Yeah that's why I started playing around the GPS settings...
Any idea which app/service is responsible for handling the volume knobs?

Categories

Resources