I got my phone about a month ago. I updated the software to 4.4.2 kitkat released by sony. It's not rooted. This problem occured yesterday for the first time. When I call someone or someone calls me, the earphone doesn't work. I don' hear anything. When I run earphone test in Service tests, it works fine. The problem is fixed when I reboot the phone. But I can not reboot the phone everytime. It happened once yesterday and next time now. I am so pissed off. This is my first sony phone and so far I am very dissapointed. My audio jack flap is opening by its self and as I can see a lot of people complain about it. I hope this can be fixed
jankos98 said:
I got my phone about a month ago. I updated the software to 4.4.2 kitkat released by sony. It's not rooted. This problem occured yesterday for the first time. When I call someone or someone calls me, the earphone doesn't work. I don' hear anything. When I run earphone test in Service tests, it works fine. The problem is fixed when I reboot the phone. But I can not reboot the phone everytime. It happened once yesterday and next time now. I am so pissed off. This is my first sony phone and so far I am very dissapointed. My audio jack flap is opening by its self and as I can see a lot of people complain about it. I hope this can be fixed
Click to expand...
Click to collapse
Hi, is there any particular reason why you want to keep using stock firmware and not to root?
If not might I suggest rooting and using a custom firmware, because in my experience custom firmware is much more reliable than the stock.
Its really quite easy to do and the phone seems to benefit from doing a clean install getting rid of any junk thats built up over time.
Good Luck!
jankos98 said:
I got my phone about a month ago. I updated the software to 4.4.2 kitkat released by sony. It's not rooted. This problem occured yesterday for the first time. When I call someone or someone calls me, the earphone doesn't work. I don' hear anything. When I run earphone test in Service tests, it works fine. The problem is fixed when I reboot the phone. But I can not reboot the phone everytime. It happened once yesterday and next time now. I am so pissed off. This is my first sony phone and so far I am very dissapointed. My audio jack flap is opening by its self and as I can see a lot of people complain about it. I hope this can be fixed
Click to expand...
Click to collapse
I recommend you to use SUS or Sony PC companion to "reinstall" FW i am not sure if this can help you but its better than sending it to repair center without trying anything. Good luck and don't forget to backup you data, etc.
Same Earphone problem
Hello, i have the same issue too. Every rom (stock based) i install, that use 4.4.2 have the same issue.
Its very annoying, have someone can resolve this?
I have, UB and at moment ExistenZ Rom
I just opened the forum to make a thread about this, as I'm facing the same problem and it can get really annoying.
Sometimes my phone works normally for 3-4 days, and then it just suddenly happens. Someone calls me, and I can't hear them, but they can hear me...and after I reboot it usually works.
I flashed the 4.4.2 UK Generic a few days ago, and now I face two different problems regarding calls : first one is like this, I can't hear people that are calling me, and the other is that sometimes I don't hear them for a few seconds and then I hear them again, and then again I can't during the call. Don't know if this is firmware based, I guess it is. If I can remember correctly 4.3 worked perfectly, as I got the phone already on 4.3 firmware.
Also Cyanogenmod has the same issue, as well as PAC-man (some versions of these ROMs, the ones I tried LOL) so I'm wondering could it be a hardware issue...what are your experiences? If someone can confirm that it is a firmware issue and that 4.3 doesn't have these problems, I might actually switch back because its annoying and the phone seems to be working better on 4.3, even though I love the transparent interface of Kitkat =)
Have a nice day guys, hope we will fix this issue !
amar92 said:
I just opened the forum to make a thread about this, as I'm facing the same problem and it can get really annoying.
Sometimes my phone works normally for 3-4 days, and then it just suddenly happens. Someone calls me, and I can't hear them, but they can hear me...and after I reboot it usually works.
I flashed the 4.4.2 UK Generic a few days ago, and now I face two different problems regarding calls : first one is like this, I can't hear people that are calling me, and the other is that sometimes I don't hear them for a few seconds and then I hear them again, and then again I can't during the call. Don't know if this is firmware based, I guess it is. If I can remember correctly 4.3 worked perfectly, as I got the phone already on 4.3 firmware.
Also Cyanogenmod has the same issue, as well as PAC-man (some versions of these ROMs, the ones I tried LOL) so I'm wondering could it be a hardware issue...what are your experiences? If someone can confirm that it is a firmware issue and that 4.3 doesn't have these problems, I might actually switch back because its annoying and the phone seems to be working better on 4.3, even though I love the transparent interface of Kitkat =)
Have a nice day guys, hope we will fix this issue !
Click to expand...
Click to collapse
For me, only the stock based rom haver this issue, i haver tested omni rom and works normal
numero13 said:
For me, only the stock based rom haver this issue, i haver tested omni rom and works normal
Click to expand...
Click to collapse
Thanks for the info. Haven't tried Omni ROM yet, I might. Can you just tell me did you have this issue on 4.3 ?
amar92 said:
Thanks for the info. Haven't tried Omni ROM yet, I might. Can you just tell me did you have this issue on 4.3 ?
Click to expand...
Click to collapse
In 4.3 stock, the earphone seems work well, but i want 4.4, and for some time it worked
Hi there
I'm having exactly the same issue on 4.4 (existenz ultimate)
I can confirm once I had this issue on stock 4.3 rom as well (existenz 7). I installed Soundabout app and it fixed the issue somehow, and i never experienced the problem until yesterday (on 4.4) . I again installed soundabout, it worked for some time, but now earphone doesn't work again. It's really frustrating! According to service test it's not a hardware problem. But could sony engineers make the same mistake twice (both in 4.3 and 4.4)?
David.V said:
Hi there
I'm having exactly the same issue on 4.4 (existenz ultimate)
I can confirm once I had this issue on stock 4.3 rom as well (existenz 7). I installed Soundabout app and it fixed the issue somehow, and i never experienced the problem until yesterday (on 4.4) . I again installed soundabout, it worked for some time, but now earphone doesn't work again. It's really frustrating! According to service test it's not a hardware problem. But could sony engineers make the same mistake twice (both in 4.3 and 4.4)?
Click to expand...
Click to collapse
thats exactly same situatiom i have
So, are you positive its not a hardware issue? I sure hope that Sony is going to fix this and all the other Kitkat problems they've had with this new update that got certified (10.A.5.1.283)..Its probably going to be 4.4.4 and the last update for Xperia Z, as Android L is probably reserved for newer phones and Sony won't get anything from supporting the update for the original Z.
I really like Kitkat but if this earphone bug is related to Sony's Kitkat update and the next version doesn't fix it, I'm sure I'll get back to 4.3, as its really frustrating when you need to make an important call, or if you're in a hurry about something and your phone doesn't work...
If anyone knows the cause of this or is certain that it is related to specific firmwares please help us out and write it here.
Greetings from Bosnia
Lets hope it will be fixed on 4.4.4
maybe i will try another stock firmawares, based on 4.4.2, just for know if its region firmware related
numero13 said:
Lets hope it will be fixed on 4.4.4
maybe i will try another stock firmawares, based on 4.4.2, just for know if its region firmware related
Click to expand...
Click to collapse
i just flased the 4.4.4 and its the same problem again
---------- Post added 10th September 2014 at 12:07 AM ---------- Previous post was 9th September 2014 at 11:56 PM ----------
amar92 said:
So, are you positive its not a hardware issue? I sure hope that Sony is going to fix this and all the other Kitkat problems they've had with this new update that got certified (10.A.5.1.283)..Its probably going to be 4.4.4 and the last update for Xperia Z, as Android L is probably reserved for newer phones and Sony won't get anything from supporting the update for the original Z.
I really like Kitkat but if this earphone bug is related to Sony's Kitkat update and the next version doesn't fix it, I'm sure I'll get back to 4.3, as its really frustrating when you need to make an important call, or if you're in a hurry about something and your phone doesn't work...
If anyone knows the cause of this or is certain that it is related to specific firmwares please help us out and write it here.
Greetings from Bosnia
Click to expand...
Click to collapse
i try existenz v7 and have the same problem, but its based on 4.3, and stock 4.3 work fine to me, so i think maybe is something related to 4.4 sony framework
hello, i have tested lots off roms and the problem is ther on almost 4.4 rom. the Free Xperia rom, not have this problem.
i was thinking is there is some app that can manually disble the 3.5mm jack is on solution, but i not find that for 4.4
lets keep trying
I'm on stock .230 and never had this problem...
Sent from my C6603
Hey Xda'ers, I have this weird (and really frustrating ) problem with my Xperia Z, when it enters Deep Sleep mode, sometimes it won't come back (won't turn on the screen & wake up.) I keep tapping the status bar (got CM11 Nightly & tap to wake option enabled) and hitting the power button to wake up, but it never does, then it just reboots.
The only workaround i've found it's to implement a partial wakelock so the cpu keeps running even if the screen is off, but thats eating my battery away. I Bought the phone a month ago and since its arrive, has this problem, i know it's a software problem cause if it wasn't, then there would be no workaround like the cpu kept running all the time (or at least my noob brain figures that out ). it's been really frustrating. the most frustrating part is not finding ANYWHERE on the internet (not even here on XDA) any resemblance to the same problem im facing, they are all different kinds of rebooting problems, but not even one the same as mine, it means my problem it's really new or special, or i'm not looking up really well, anyways it's been so frustrating for me this month, cause i repeat, since it arrived it has this problem.
First i thought it was a Wifi Problem, cause it happens when i get a notification meanwhile is asleep (i've seen it happen more often but it happens with or without a notification too.) and the screen off; When i try to wake up to see the notification, the problem triggers and it wont wake up, so i installed "Advanced Wifi Lock" (I saw a thread with a similar problem but with an Xperia Pad of some girl on the Sony Mobile Forums, and one guy posted this solution as the only workaround he had found to the same problem.) and the problem was solved.
But then i realized that it was eating my battery, so i changed to "Wakelock Power Manager" (cause i read it was a lighter weigh solution than "Advanced WiFi Lock") and there, there is this option for the implementation of various degrees of wake lock, since i thought it was a wifi problem, i turned on the "WiFI_Mode_Hi_Perf" which is a wakelock that keeps the wifi running in a high performance mode even while in deep sleep, i thought this was a lighter solution to my problem, but then the deep sleep reboot problem started again :crying:. so i tried increasing the level of wakelock to a "Partial_Wake_Lock" which is a wakelock that keeps the CPU running even while the screen is off, but this wakelock won't let the phone enter in a deepsleep mode, so it's the "Advanced Wifi Lock" problem all over again. Battery Drain . And this pisses me off, cause my battery, that should have a more than 14 life hours, just have those with a 4-5 hours of screen on time with a mild use of whatsapp and facebook.
I don't know what to do, i've tried flashing other Stock Firmwares, 4.1, 4.2, 4.3, 4.4, reflashing the original (was a 4.1 "10.1.1.a.1.307 customized hk"),, rooting and flashing roms, and the problem persists. I left CM11 on cause i like it and i don't think it has anything to do with the rom or firmware cause i've tried so many already.
Finally, over a month of trials and reading and so, so, so, but SO much frustration, i come to you guys, i don't know what to do anymore, Please Help .
Just bumping with some screenshots with details about my phone, i guess it will be easier to solve the problem, if posible, somehow. Muy Xperia Z is a 6603 model btw.
Note: I set the minimun CPU frecuency to 486 because i had the weird "buzz" sound problem sometimes with whatsapp & messenger notifications, & found that solution here over the forums, anyways, the problem was there way before that change.
I ask for some help again developers, i didn't wanted to start a help thread before i did my research & exhausted all my options, but i've done everything i could, & still got no solution, hope the screenshots help .
Sent from my Xperia Z using XDA Free mobile app
I had the same thing, and mine was fixed with increasing my minimum CPU speed to 384. Runs like a dream now!
I know you'v said you've tried a whole load of different roms but have you tried any different kernels? Mine seemed to come up only when using certain kernels.
i had the CPU running on 384 since i bought it, i only recently changed cause of the buzz problem, & no, i haven't tried different kernels, only different roms, i don't know how to flash a kernel only.
What kernel do you have? & Just to be sure, you had the same rebooting problem when it went to deep sleep mode right?
Thanks for answering.
Sent from my Xperia Z using XDA Free mobile app
I haven't got a solution but get the same problem on the stock 4.4.2 kernel, intermittently between once a day and every other day, so I can live with it. As I recall the problem was more frequent until I got rid of a legacy app which put the phone to sleep when I shut the case, and was supposed to wake it up when the case was opened (which didn't always happen and about half the time I couldn't wake the screen with the on-button either, only reboot). It was a battery hog too. Running the CPU faster (up to 904??) didn't help, though.
mervluk said:
I haven't got a solution but get the same problem on the stock 4.4.2 kernel, intermittently between once a day and every other day, so I can live with it. As I recall the problem was more frequent until I got rid of a legacy app which put the phone to sleep when I shut the case, and was supposed to wake it up when the case was opened (which didn't always happen and about half the time I couldn't wake the screen with the on-button either, only reboot). It was a battery hog too. Running the CPU faster (up to 904??) didn't help, though.
Click to expand...
Click to collapse
With once a day or every other day i could live with it too, i guess it's worth to let the phone deep sleep and save more battery even tho it reboots once a day or sometimes none, the battery saving should be greater than the annoyance, i hope mine was like that, but as soon as i release the cpu wakelock & let the cpu get into deep sleep, the problem begins, i get like 10 reboots in a day, and if only the reboots just happened when i weren't looking, but no, they barely happen this way, it happens when i try to use it and i notice it won't wake up, it's a really weird problem, & i find it very weird that no one has it. (you two guys are the first that i know have this kind of problem, and still, it's slightly different, for the number of reboots at least.) although it's good to know finally someone has the same issues as me, though i don't have high hopes since you told me you haven't found a solution.
I wanna try flashing a different kernel as orangejuice43 said, but i don't know how, or any compatibility issues with the rom i have (CM11 Nightly), sides, i don't know which kernel would be good to try.
Thanks for answering!
Flashed succesfully "Lightning Kernel v. 8.0" for CM11, will test for a few hours or days hopefully, if reboot comes i'll notify you guys, so far this is the first "new" solution i try.
After less than two hours of flashing the "Lightning v. 8.0" Kernel and the partial wakelock off, the reboot problem happened again, no solution yet, and have the wakelock up again.
Anyone having the same issues? anyone with another suggestions or fixes? bummed down here .
Jorge Plascencia said:
After less than two hours of flashing the "Lightning v. 8.0" Kernel and the partial wakelock off, the reboot problem happened again, no solution yet, and have the wakelock up again.
Anyone having the same issues? anyone with another suggestions or fixes? bummed down here .
Click to expand...
Click to collapse
Flash another ROM...
TapaTalked from my Xperia™ Z (C660²) running Ultimate PureXZ Ultra!
That's a shame, I'm using lighning v8 and my problem is sorted. Sorry I can't be of much more help... lets hope a more knowledgeable person may be able to contribute for you.
Have you got an app like Trickster MOD installed to control the Kernel etc? might give you more of an insight as to what's going on. If you set a governor that keeps your Z from going into deep sleep it may be a bit better for your battery life than the wakelock solution...
This might help for information about Kernels
http://forum.xda-developers.com/galaxy-s2/general/ref-kernel-governors-modules-o-t1369817
Sorry for the late reply, i was on a trip so i couldn't actually test & give any feedback.
I downloaded Trickster Mod for my lightning kernel but all i could understand (after reading the post orange kindly shared.) was that every governor has this different settings that mod the cpu functionality & can be picked to adapt your own needs, i really doubt that any of them help with my problem, but as orange suggested, one may be a better choice compared to the wakelock fix i have used lately. i learned that since i flashed the lightning kernel, my governor was Interactive all this time, i really didn't noticed any battery drain or saving, i felt it just the about the same as before with the stock CM11 kernel.
a new question is, which kernel has the option or the setting for keeping the cpu awake? cause i didn't read any of them did this, or at least i didn't understood that any of them did this. anyways, that would be only another work around for the deep sleep reboot problem.
I though, read something interesting about frequencies and voltage of the cpu on the Thread, this:
Q. "Well i have set my favorite governor as screen-on governor and another one as screen-off governor. Why the hell is the phone not waking up after deep sleep. I need to force-restart the phone by pressing power button for about 10 secs. Is it a sleep-of-death?"
A. Yes it is. Do not use two governors as screen-on & screen-off govs, if they both have an upper frequency limit for screen-off state.
Didn't get it? Examples for Wrong combinations: (screen-on:screen-off):-
ondemandX:smartassV2
Examples for right combinations:-
ondemand:smartassV2, lulzactive:smartassV2
Click to expand...
Click to collapse
The Question resembles just exactly what my problem is, my phone enters into deep sleep and then it won't wake up, the only difference is that i don't have to force restart it, it just. when i try to wake it up, restarts itself, with no need of long pressing the power button, and sometimes, i just find that the phone is off, and then i do have to start it by long pressing the power button (plain old power on.), but that brings me another question, isn't that maybe the problem is on the frequency & voltage side of my CPU? maybe the stock kernel (not CM11, and for the matter CM11 too, cause the problem persists, even with lightning kernel...) came with a rare code line or something? i dunno, im just wondering, maybe it doesn't make sense, but its just that the question and problem stated there on the thread about governors and kernel settings, resembles very much what my problem is.
I hope someone can orient me about this or make a mental link with something (maybe) wrong about my kernel or phone, could it be hardware? :crying: . I don't know, maybe i should try another kernel? maybe i should go back to Stock ftf and try another kernel? any suggestions or long shots are apreciated.
Thanks for the replies, & sorry for all the descriptions and text, it maybe kind of boring -_-.
Adding another detail that i may have not mentioned, the problem NEVER happens while plugged in, (don't know if phone has a setting preventing deep sleep while plugged in, if it does, that may be the cause )
Update: just flashed AOKP ROM (jellybean 4.3 version) will test for a few hours or mins till the problem arises again... (lost all my Xposed modules & settings :crying: .)
Update 2: After less than 2 hours again, around the 1:30-1:45 hours time, reboot problem happened. getting sick of trying...
Update 3: Just flashed AOKP ROM (Kitkat 4.4 version). less than 15 min into the flash, reboot happened... help...
will flash Paranoid Android 4.4 Later.
Update 4: Flashed Paranoid Android 4.4, nearly 2 hours of deep sleep and 2:14 hours of total on time, reboot occured, was getting high hopes about this ROM, but as i said on my first post, i don't think it has anything to do with the ROM- Side note: PA is really cool, im sticking with it. and hoping anyone still answers with some fix or advice. thanks for reading.
Jorge Plascencia said:
Adding another detail that i may have not mentioned, the problem NEVER happens while plugged in, (don't know if phone has a setting preventing deep sleep while plugged in, if it does, that may be the cause )
Update: just flashed AOKP ROM (jellybean 4.3 version) will test for a few hours or mins till the problem arises again... (lost all my Xposed modules & settings :crying: .)
Update 2: After less than 2 hours again, around the 1:30-1:45 hours time, reboot problem happened. getting sick of trying...
Update 3: Just flashed AOKP ROM (Kitkat 4.4 version). less than 15 min into the flash, reboot happened... help...
will flash Paranoid Android 4.4 Later.
Update 4: Flashed Paranoid Android 4.4, nearly 2 hours of deep sleep and 2:14 hours of total on time, reboot occured, was getting high hopes about this ROM, but as i said on my first post, i don't think it has anything to do with the ROM- Side note: PA is really cool, im sticking with it. and hoping anyone still answers with some fix or advice. thanks for reading.
Click to expand...
Click to collapse
It's look like the battery is damaged or something...
TapaTalked from my Xperia™ Z (C660²) running Ultimate PureXZ Ultra!
androidfreak70 said:
It's look like the battery is damaged or something...
TapaTalked from my Xperia™ Z (C660²) running Ultimate PureXZ Ultra!
Click to expand...
Click to collapse
That sounds good cause the problem only happens when the phone is unplugged, but then again, what does it have to do with the CPU lock? the problem solves when i have a wakelock for the CPU, if the battery was damaged, probably it wont matter if the CPU is on or in deep sleep, it would just reboot randomly still, but that has never happened.
tldr: But CPU wakelock solves the rebooting problem, doesn't make sense.
Jorge Plascencia said:
That sounds good cause the problem only happens when the phone is unplugged, but then again, what does it have to do with the CPU lock? the problem solves when i have a wakelock for the CPU, if the battery was damaged, probably it wont matter if the CPU is on or in deep sleep, it would just reboot randomly still, but that has never happened.
tldr: But CPU wakelock solves the rebooting problem, doesn't make sense.
Click to expand...
Click to collapse
There is nothing called *CPU lock* wake lock is not preventing the phone from waking up.
Wake lock is the apps which wake the phone from the deep sleep mode. Like WhatsApp. When you get a message the phone will wake up from deep sleep.
You cannot lock the CPU.
Anyway. Your primary problem seems with the battery because many people reporting while they unplug the phone it will reboot or turn off. So changing the battery may help.
TapaTalked from my Xperia™ Z (C660²) running Ultimate PureXZ Ultra!
androidfreak70 said:
There is nothing called *CPU lock* wake lock is not preventing the phone from waking up.
Wake lock is the apps which wake the phone from the deep sleep mode. Like WhatsApp. When you get a message the phone will wake up from deep sleep.
You cannot lock the CPU.
Anyway. Your primary problem seems with the battery because many people reporting while they unplug the phone it will reboot or turn off. So changing the battery may help.
TapaTalked from my Xperia™ Z (C660²) running Ultimate PureXZ Ultra!
Click to expand...
Click to collapse
Yes i understand that's what "wakelock" means, what i meant, it's that i have this app called Wakelock Power Manager, and in that app, i got this "Partial_Wake_Lock" on, & that's the only way around i could find for the problem, on the description of this option it says "Ensures the CPU is running even if screen is off." so that's what i meant when i said i had a CPU lock or wakelock, sorry if i didn't made myself understand.
regarding your suggestion, i don't know, i don't wanna spend more money on a "maybe" solution, i've already spent quite a lot buying this phone, and had a bad experience trying other common solutions as replacing the sim card with a new one, didn't solved anything. i would like to be sure that is the problem before spending more bucks on this.
Thanks for the reply.
Jorge Plascencia said:
Yes i understand that's what "wakelock" means, what i meant, it's that i have this app called Wakelock Power Manager, and in that app, i got this "Partial_Wake_Lock" on, & that's the only way around i could find for the problem, on the description of this option it says "Ensures the CPU is running even if screen is off." so that's what i meant when i said i had a CPU lock or wakelock, sorry if i didn't made myself understand.
regarding your suggestion, i don't know, i don't wanna spend more money on a "maybe" solution, i've already spent quite a lot buying this phone, and had a bad experience trying other common solutions as replacing the sim card with a new one, didn't solved anything. i would like to be sure that is the problem before spending more bucks on this.
Thanks for the reply.
Click to expand...
Click to collapse
Well yeah that's right. I suggest you to wait for others. I may be wrong.
TapaTalked from my Xperia™ Z (C660²) running Ultimate PureXZ Ultra!
Jorge Plascencia said:
regarding your suggestion, i don't know, i don't wanna spend more money on a "maybe" solution, i've already spent quite a lot buying this phone, and had a bad experience trying other common solutions as replacing the sim card with a new one, didn't solved anything. i would like to be sure that is the problem before spending more bucks on this.
Thanks for the reply.
Click to expand...
Click to collapse
Just a thought: are you sure it's not a misbehaving app? I'd start with the obvious suspects, those that run in the background or make regular checks, and find tb's freeze facility invaluable; not least your Wakelock monitor, perhaps!
mervluk said:
Just a thought: are you sure it's not a misbehaving app? I'd start with the obvious suspects, those that run in the background or make regular checks, and find tb's freeze facility invaluable; not least your Wakelock monitor, perhaps!
Click to expand...
Click to collapse
About the misbehaving app, i really don't think so, as i said in my first post, the problem was already there 1 hour after unboxing, it could be a stock app, but im not sure how to 'find' it. and about the rest, sorry but i didn't understood could you be more clear (noobier) please? ha, thanks in advance!
Jorge Plascencia said:
About the misbehaving app, i really don't think so, as i said in my first post, the problem was already there 1 hour after unboxing, it could be a stock app, but im not sure how to 'find' it. and about the rest, sorry but i didn't understood could you be more clear (noobier) please? ha, thanks in advance!
Click to expand...
Click to collapse
If you are saying after 1 hour of unboxing so I think you need to talk with the seller. Maybe you will get another Z.
TapaTalked from my Xperia™ Z (C660²) running Ultimate PureXZ Ultra!
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.