Related
Hey guys! This is my first post on XDA, though I've been using it for quite a while.
I'm not exactly looking for answers/solutions, but rather sharing my problem and see if someone else is having them too.
I have a Latin American version of the I91000 (TTT). I recently upgraded to ICS using the official firmware from Samfirmware (UHLPE). At first everything looked great. The performance improvement was noticeable from the first bootup. Not only was it faster, but the intro video was far smoother and looked nicer. The general UI changes are very nice, and I did notice an improvement in battery life.
However, I've been experiencing a couple of glaring issues that really mared the experience enough to make me want to go back to Gingerbread, which I will probably do.
These are the problems:
1. The mobile data connection is very unstable. Sometimes it just doesn't load anything, and sometimes I lose the signal altogether. The 3G/H/H+ icon disappears and all. I never had this problem in GB during the 6 months I've had this phone.
2. The Bluetooth audio connection also has problems. It's now more unstable and susceptible to interference, and the lag is also much more noticeable now. It was about .5 seconds before, but now it's more than a full second.
But that's not the worst issue. The media remote control functions just stopped working altogether, namely, the |<< , >>| , >/|| buttons on my headset. I have a Nokia BH505 Bluetooth headset, and I didn't have any of these problems before either.
So that's it. I would like to know if someone else is experiencing one or both of these issues. I'll also check the Samfirmware forums to look for replies on the matter. Thank you for your feedback.
Hi
Looked for this issue on the forum and can find instances of it happening occasioinally, but not with the frequency that i have. Symptomns are that the screen will stop responding to input. I.e the screen stays painted but does not respond to my pokes or pros. Flicking the screen on and off for a split second fixes it. I believe its related to software or resource usage -sometimes i can go for ages without issues, however in the last half an hour this has happened around ten times. please help!
I have tried isolating it down to a particular app with no success, and also changed the CPU governance settings, asgin unsuccessfully. I have no such issues in WebOS.
Thanks.
ps running CM9 alpha 2, but had same issue on 0.6
flash the latest nightly.
screen unresponsive281]flash the latest nightly.[/QUOTE]
Thanks for the reply. I may consider doing that, guess that with a Android backup I don't have much to lose. Would like to avoid it if possible as not being as widespread they aren't as proven and I've ironed out all other issues in alpha 2 such as wifi etc ...
Thanks
the latest nightly offers quite a few fixes.....
including vibration from sleep and tons of other stuff. not much can go wrong.
Andysan said:
Thanks for the reply. I may consider doing that, guess that with a Android backup I don't have much to lose. Would like to avoid it if possible as not being as widespread they aren't as proven and I've ironed out all other issues in alpha 2 such as wifi etc ...
Thanks
Click to expand...
Click to collapse
There has been loads of improvements in CM9 wifi has been fixed sound distortion when the screen off is fixed many speed fixes we now have themes working
Do a nandroid backup in CWM then copy that to your pc for safety then wipe system partition DO NOT FACTORY RESET OR WIPE DATA or you will lose you data, then flash latest nightly and latest gapps then wipe dalvik cache/cache partition's then in advanced fix permission's and reboot system
Well.... I dip my hat to you guys.
Went ahead and installed the latest nightly - even if it doesn't fix my issue, I was suprised by how polished it felt compared with Alpha 2. Typically with bleeding edge stuff I'd have expected to have more issues, but alls I had to do was reinstall YouTUbe and flash the gapps-fixer zip for my Calender sync, plus I see lots of lovely new settings to play with.
Will report back if the screen hangs again, here's hoping...
Frustratingly this issue has started happening for me again running 31 May nightly - touch screen has become unresponsive half a dozen times in the last ten minutes.
Maybe trying wiping it and doing a brand new flash from the latest nightly. (I know it sucks to reinstall stuff, but maybe there are some leftover codes that is causing trouble.. )
i agree either to wiping data or up your min cpu speed as it might the amount of apps you have installed that auto start/resume when turn on the screen..
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
I only had that problem once. Rebooted by holding home and power never had it again.
Sent from my YP-GI1 using XDA
Had this issue yesterday for the first time since installing cm9 6(?) months ago.
Tried a nightly build as suggested, but given the rarity in the first place, can't be sure it's fixed
This happens to me all the time across all ROMs I have tested.
This happens in OaT's and turning the screen off/on, fixes it temporarily.
This happens in Butta, but turning the screen off/on does nothing. I have to reboot using power/home.
I have also been unable to find a specific app that causes it, but it does seem to occur more often in graphic intensive games.
I can go for days without it happening, then BAM, it stops responding to touch, from that point forward, no about of reboots or full shutdowns seems to fix it for several hours. I'll reboot and sometimes it'll be immediately, sometimes it will be 3-5 minutes, but it will happen again.
Then a few hours later it'll stop happening and I'm good for a few more days.
Do those of you using CM9 find that screen off/on fixes it, or do you need a full reboot?
I am running the night lies and have to say that the only time I experienced this was with the may nightlies. I have not experienced any issues with the 7/04 nightly.
Sent from my cm_tenderloin using Tapatalk 2
Interestingly enough I think I found out what causes the screen to stop responding. When the TouchPad is locked in landscape and then I turn it portrait while its still locked, then the screen becomes unresponsive. Does that make sense?
Sent from my Touchpad using xda app-developers app
I take it back. The screen became unresponsive even in landscape mode. There goes my well formed and thoroughly investigated theory.
Sent from my Touchpad using xda app-developers app
---------- Post added at 07:54 PM ---------- Previous post was at 07:22 PM ----------
I've been using Nova Launcher ... I switched back to Trebuchet and it appears to be working normally. Of course I may be spouting this half-cocked like I did before. What launcher are you using?
I run SPB 3D launcher and do not experience any response issues with the latest nightlies. I use my touchpad constantly as a laptop replacement so mine gets a workout every day. To my knowledge, no one was ever able to find any one app that was responsable for this behaviour but it was noted in earlier builds.
,
Sent from my cm_tenderloin using Tapatalk 2
I too still have this issue - as per others, fine for days, then it will occur consistently and I keep having to screen off/on and eventually it stops of its own accord. Am sure its a software issue, but someone here says they also had it in WebOS and HP provided a replacement.
http://rootzwiki.com/topic/20740-screen-unresponsive-in-cm9/
For me as simply flapping the screen on/off fixes it and I've never had the issue within WebOS, it has to be software - this started as soon as I first installled CM9.
Bump - still no fix identified for this by anyone with this issue please?
To anyone still following on, followed nevertells advise and completely started again from scratch and it happened after about twenty mins of using the stock browser. I think i've tried not using that app before so am just going to assume that this is either a software bug or a hardware issue that only manifests itaelf within Android
Hi everyone!
I have a strange problem with my Droid 4: sometimes it stops playing sounds (or music, or ringtones), and I can't figure out if there's something in particular that triggers this. Anyway the only fix I could find is rebooting the phone.
There's another problem though: when this happens, if I try to use the phone app or the contacts app, the app itself hangs before I can do anything. If I kill the hanged app and retry a few times, the phone reboots itself.
Any idea on what could be causing this? What could I try to diagnose the problem?
I'm using a Verizon-branded Droid 4 with CM10.1.3, but I had the problem on 10.1.2 too. If it's relevant, I had to install "Tobby's mod" to enable GSM (I'm in Europe)
Many thanks for your attention!
This is the only and the known problem with droid4 on cm10.1 cm10.2 but I have a very good experience with the latest nightlies using buildprop editor to change only the telephony.lteOnCdmaDevice=0. Don't use the patch and se if it helps for you.
Sent from my XT894 using xda app-developers app
I have that property "zeroed" already, do you mean I should try reverting Tobby's mod?
Try the latest nightlies, there are some changes regarding to apns, it's updatable from cm10.1 and make only that change don't apply any patch.
Sent from my XT894 using xda app-developers app
Joril said:
Hi everyone!
I have a strange problem with my Droid 4: sometimes it stops playing sounds (or music, or ringtones), and I can't figure out if there's something in particular that triggers this. Anyway the only fix I could find is rebooting the phone.
There's another problem though: when this happens, if I try to use the phone app or the contacts app, the app itself hangs before I can do anything. If I kill the hanged app and retry a few times, the phone reboots itself.
Any idea on what could be causing this? What could I try to diagnose the problem?
I'm using a Verizon-branded Droid 4 with CM10.1.3, but I had the problem on 10.1.2 too. If it's relevant, I had to install "Tobby's mod" to enable GSM (I'm in Europe)
Many thanks for your attention!
Click to expand...
Click to collapse
I've seen this on stock, and I think it's related to bluetooth - perhaps it's not releasing the audio properly after a device disconnects?
There's an app in the Play Store called "Earpiece", and I can use that to bring the audio back when that happens by switching it on, and then switching it off again.
HTH.
Steve.
I don't use bluetooth at all, but I'll try Earpiece, thanks
the problem is that it will crash before you realize and you will loose the next call, so I don't think it is of some use.
I tried latest nightly and safestrap 3.65 (from 3.63) and I had lots of black screens, several on one day and then I realize that before, I had it working stable on cm10.1 when I found out that noop was the problem, cfq and deadline was ok (after speaking with hashcode it made the default to cfq) but it was on safestrap 3.11, but then newer versions of safestrap appeared and I updated it and from time to time it started to go bad again.
I reverted back to 3.11 and I have it working ok since 17.11.2013 (almost 2 days of stable, finger crossed)
I would ask hascode if safestrap can be a problem, but now he has retired in supporting the d4, of course this can be applied to razr
Regards
lucize said:
I reverted back to 3.11 and I have it working ok since 17.11.2013 (almost 2 days of stable, finger crossed)
Click to expand...
Click to collapse
How is it going?
For me is very good, tried 4.4, now back on cm10.2 nightlies, so
Ss3.11 and only the lteoncdma change, everything else is working fine except tha battery that is shorter than moto default
Regards.
Sent from my XT894 using xda app-developers app
lucize said:
For me is very good, tried 4.4, now back on cm10.2 nightlies, so
Ss3.11 and only the lteoncdma change, everything else is working fine except tha battery that is shorter than moto default
Click to expand...
Click to collapse
Ok, now I'm on a 10.2 nightly, with just the lteoncdma fix... Let's see how it goes
It took a while to connect to the GSM network, did this happen to you too? (The signal strength icon even changed to a question mark at one point)
I first have no sim, then no signal then I get full bars
Sent from my XT894 using xda app-developers app
I had it working nicely for 6 full days, but this morning sound went out again Better than before, but still...
I'm on the 28/11 10.2 nightly, I'll try updating again this evening
Joril said:
I had it working nicely for 6 full days, but this morning sound went out again Better than before, but still...
I'm on the 28/11 10.2 nightly, I'll try updating again this evening
Click to expand...
Click to collapse
I'm on kitkat, I think that I had it too with 28, try 27 or other, maybe stable, anyway is better than 1 or 2 days
Regards
Definitely better, yes So you're using CM11? Any problems?
Joril said:
Definitely better, yes So you're using CM11? Any problems?
Click to expand...
Click to collapse
the 05 fromm stargo is not so ok, the previous was stable, or at least I didn't had problems.
I'll try the 07, I have problems with deep sleep and I don't know why, because for now wakelocks can't be accessed on 4.4, then again is not a new install, is an upgrade from 10.2
the strange thing is that now I have another error in catlog when it goes out of sound compared to the error when it is on the gsm patch, maybe I'll try a test without changing build.prop at all, in the end it doesn't matter if the signal icon is wrong as long as it's stable.
Regards
Hey! Joril! I posted in your other thread, on another forum, about this same topic, but I figure that I'd get comfy here, since the Droid 4 "scene" has seemingly migrated from DroidForums to this website.
Anyway, I haven't been able to fix the problem. In fact, at one point, when the audio died, I went through the typical steps - I turned off Bluetooth, and reset the phone. However, when the phone was "coming back", so to speak, an "Android is upgrading" box popped up. Odd, I thought, since I didn't do anything different. Anyway, it gets through this, and... I get an UID error. Something about the UID being inconsistent with the system, and that the data partition was terribly unstable.
So, my phone was freaking out. Great. I was missing several apps, and the whole device is incredibly unstable - apps are crashing, left and right, as well as background services. It is at this point that I decide to bite the bullet and restore my phone to stock settings.
I do so. I use the Droid 4 Utility, restore the stock ROM, getting rid of Safestrap 3.11 in the process. Everything's back to normal. Stabilized. I commence to rooting the phone, installing the latest version of Safestrap, and installing CyanogenMod 10.1.3. I get it running, and... the problems remain. I still have the same audio issues. MMS is still iffy. GPS is a hit-or-miss process; every once in a while, if the planets align, a system reboot will "fix" GPS.
Anyway, that's my story. I've been doing some research - or, rather, a lot of research - and it seems to me that the audio problem was, perhaps, fixed in the latest CyanogenMod 11 build. Something about the previous code not playing well with the "Audio HAL", whatever that is, and the Audio HAL issue being consistent with other phones with the same processor, I believe - or something to do with an "MSM8660". I believe that "MSM8660" is a Snapdragon processor, but I could be wrong!
To make a long story short: CyanogenMod 10.1.3 seems to be stuck with the audio/crashing issue, but CyanogenMod 11 may fix it. I'm not ready to make the jump to CyanogenMod 11, though, not until it is FULLY stabilized and out of Experimental/Alpha/Nightly status. In that regard, I wonder how open Stargo, Hashcode, or another coder would be to patching up 10.1.3 with the GPS/MMS fixes that have been seen in the later builds? I don't know how to code, but it should be relatively simple to patch the few crippling bugs remaining on 10.1.3, using code from future builds and versions.
Jishkah said:
CyanogenMod 10.1.3 seems to be stuck with the audio/crashing issue, but CyanogenMod 11 may fix it. I'm not ready to make the jump to CyanogenMod 11, though, not until it is FULLY stabilized and out of Experimental/Alpha/Nightly status. In that regard, I wonder how open Stargo, Hashcode, or another coder would be to patching up 10.1.3 with the GPS/MMS fixes that have been seen in the later builds?
Click to expand...
Click to collapse
Right now I'm on a CM10.2 nightly and the audio issue appears a bit less than when on 10.1, I'd say once every 5/6 days instead of once every other day... Anyway I'd like to wait a bit more before trying CM11 too
CM11 has this issue also, but the error will not be the same if the build.prop has only lteoncdma modified, for me, if I apply the full gsm patch the error will appear more often and catlog will show the cpu pegged error.
the problem with CM11 (for me) is no deep sleep, the sound issue is not so important anymore
Hallo,
I am sorry, to post it here, but I cannot post in the related forums below 10 posts.
So I had 4.1.5 and it was great. I flashed 4.2.3 now and it was great until after pretty much one day, when it becomes slow, had the same issues with 4.2.2 (becomes slow after a day until reboot or downgrade to 4.1.5) where I downgraded again, but it is not possible anymore without resetting the launcher3 due to some changes.
It will crash repeatedly.
Any help?
Kind regards
neox
I've been using CM based Mackay ROM for a long time now, updating to every new version as they have been released, and have not experienced anything like what you are describing.
Also, you should have really posted in the Mackay ROM thread...
Sent from my GT-I9000 using Tapatalk
@neox456! I am not sure I understand your problem fully. I have been using the same ROM since it came out for Kit Kat but never had a problem such as yours.
Could it be the no. of apps you have in your phone ? Or maybe because you aren't using low mem option (which was a feature of Kit Kat)?
It'd be good if you could explain your issues a bit briefly.
neox456 said:
Hallo,
I am sorry, to post it here, but I cannot post in the related forums below 10 posts.
So I had 4.1.5 and it was great. I flashed 4.2.3 now and it was great until after pretty much one day, when it becomes slow, had the same issues with 4.2.2 (becomes slow after a day until reboot or downgrade to 4.1.5) where I downgraded again, but it is not possible anymore without resetting the launcher3 due to some changes.
It will crash repeatedly.
Any help?
Kind regards
neox
Click to expand...
Click to collapse
Did you install CM10.2 (stable) or CM11 before Mackay 4.2.3? This increases your partition giving you better performance and is recommended for KK roms. Try again with 3 wipes plus Format System first, then the CM11, 3 wipes and format again then the Mackay Rom. If you get into trouble, go back to GB 2.3.6 with ODIN like you did when you first rooted your phone and back up from there. Hope it works for you.
The difference was between 4.1.5 and 4.2.2/3. But I played around a little and the main difference was, that KSM was on with the later ones and not with 4.1.5 so I am pretty sure that slowed my device down after a while.
I'll try 4.2.3 without KSM now and see if it won't slow down.
I cannot answer on the official Mackay-Thread until I reached 10 posts!
neither can I yet...
Naaah, it did not really help...
But I guess it is the KitKat slow downs... it is not as horrible as 4.3, but still far from well usable.
neox456 said:
Naaah, it did not really help...
But I guess it is the KitKat slow downs... it is not as horrible as 4.3, but still far from well usable.
Click to expand...
Click to collapse
Very strange.. I went all the way back to GB 2.3.6 then CM 10.2 (or 11) then SlimKat and it works really well with no FC or lags. (well maybe say max 2 second delay opening Whatsapp but I can live with that. Plus they all seem to have a 1 or 2 second delay when a call comes in for the screen to register.
Well... I am not sure... Maybe it is too many apps. At least they are not constanlty crashing like in JB4.3.
What about waking up the phone for you? Do you have a 2 seconds delay there, too? Well I sometimes have a more like 10-15 seconds delay. I press the power button and nothing happens and after a while you notice the phone is ready, because the LEDs are glowing and funnily you can already unlock it, although the screen does not show anything yet...
Well and sometimes it is only a few seconds...
I have always used CM or Mackay-CM... not sure, whether the other ROM will make such a big difference...
I had lags with CM in ICS so I went to Liquid smooth by aways .
http://forum.xda-developers.com/showthread.php?t=2223729
I like that one, no problems opening apps or answering phone call. Pkus he uses semaphore and the Nova Launcher which has a nice look and feel. Pluis customisable.
Then after to SlimKat, (after increasing partition using the CM11) which works pretty good. I will flash the mackay rom or the omni this weekend to see how it behaves in comparison.
I am down to CM9 (still Mackay) now and happy with it. :angel:
Some features got lost, but I am happy, because in general it is way more useable.
Hello guys,
I've been testing all lolipop roms that had listed everything as working. Such as crDroid, CandyRom, SlimLP. On every of those lolipop roms pretty much most of the important stuff worked. There were stuff like equalizer not working or too dim notification LED, but from time to time I got touchscreen freezes. I mean I could use phone for a couple hours and then the touchscreen would freeze really often, sometimes it froze for couple of seconds and that was it and sometimes it could last for 10 minutes. This is really annoying and unacceptable if developer says that the touchscreen works.
I ended up contacting crDroid developer - davidteri81 and he said that the touchscreen works fine for him. I asked in the thread and I got only a single response saying he doesn't have this issue, but the sensivity is too high.
I've tried like literally 4 lolipop roms on my Z1 and each one of them had those touchscreen freezes. I even ended up flashing liquidsmooth in which I didn't had this issue, or it just didnt had the chance to happen since most stuff doesn't work there and it isn't usable as a daily driver so I quickly got rid of it.
My question here is:
Do you get touchscreen freezes? Please reply only after minimum 24h of usage. If you don't have any touchscreen freezes on lolipop rom on the Z1 then please, tell me what Lolipop rom do you use as I couldn't find any that wouldn't have a buggy touchscreen.
Please tell me if it works for you without issues or do you also have this issue on the Z1 as I'm puzzled because it couldn't be just me since I did a full phone wipe, flashed the phone clean, even wiping internal memory, but it still happens and I cant find a way to use any Lolipop rom everyday on my Z1. The more replies I get, the better.
@olokos: I'm on CM12 official and use it now for many days. In this time I never faced any touch freezes on my Z1.
I've got some other "bugs" that confused me a bit and make some manual fixes like Wi-Fi MAC. But for me I can say that this ROM is really stable and I use it as my daily driver.
schickel said:
@olokos: I'm on CM12 official and use it now for many days. In this time I never faced any touch freezes on my Z1.
I've got some other "bugs" that confused me a bit and make some manual fixes like Wi-Fi MAC. But for me I can say that this ROM is really stable and I use it as my daily driver.
Click to expand...
Click to collapse
Same for me, although, the touch screen did freeze once, but I locked it and unlocked it and it worked again. It's probably hardware since I got my Z1 replaced because of this issue that even happened on stock ROM occasionally.
using CandyRom 5.0.2
I never faced any touch freezes issue
@olokos: I'm on 20150214 and now I've got touchscreen freezes. This is the first time for me on Z1.
But I think that this could be a global Cm12 issue, because my Nexus 7 also get some freezes and I thought that something is wrong with my fingers or tempered glass.
The problem is how to debug this?
im on candy 5 and my screen dont freeze, but my screen percieves touches from nowhere... but only if i have earphone plugged in .. thats more than just annoying
anyone has the same prob?
sry for my really bad english
Touchscreen freezing issue definitely isn't hardware issue on custom roms. I haven't tried CM12 or any other apart from those listed on XDA, but I will propably build some lolipop rom from source by myself if I get enough reports that will be useful for me. If touchscreen works for you then please, tell me what rom you are using and for how long you use it, what't the way you flashed it.
I only need those 3 things. If touchscreen doesn't work just for me then I'll build my own stock based rom based on Sony sources. I just have to make sure that the touchscreen issue isn't just on my side.
All I need is:
Do you have touchscreen issues? Yes/no
What ROM/Kernel you are using? CandyRom 5.0
For how long? 5 weeks
Answer those 3 questions, legitimately and I'll consider that. I'm not sure If I'll have enough time to work on this, so please, be honest with your answers because I'm not going to fix the touchscreen, or maybe I will if it doesn't happen for everyone.
I experience dramatic touch screen freezes as well since the first time I installed Lollipop nightlies. (4 weeks now). Tried clearing cache, factory restores, de- and reinstalling apps. Reflash kernel, format SD, reinstalling gapps, puzzeling at logcat logs etc. Nothing helps. Random freezes from seconds till minutes. Only thing that 90% of the time will help is keep pressing powerbutton until screen becomes responsive. It happens more when I have a lot of (hangout or whatsapp) notifications, or when trying to type something (stock keyboard). Tried other keyboards: no luck. Tried every toggle: WiFi , Bluetooth etc. : no luck.
I experience dozens of freezes a day. Almost to the point that cm12 is completely unusable. Love this ROM, but this is a real showstopper.
1. No
2. AOSP Vanir 5.02
3. Since first availibility (12/14)
I experienced this issue on 2 roms in 2 forms
1. No (coming from Stock 14.4.A.0.108)
2. KitSlim_AMG [Evo 8.1] / iHackers advanced Stock Kernel
3. Since installing the Rom
This was the first time i experienced touch-issues. Not a freeze of the screen, but the screen sometimes started registering touch-events on the wrong places. This was temporarly fixed by locking/unlocking the display.
1. Yes (coming from KitSlim_AMG [Evo 8.1] )
2. crDroid-5.0.2-20150303-honami / 3.4.0-crDroid (packaged with rom)
3. Since installing the Rom a day ago
This time i get freezes. And they are much more frequent than those "ghost-inputs" from KitSlim_AMG. Unlocking the device also fixes it temporarly.