So I bought my new Z2 today, rooted, unlocked the bootloader, installed recovery, and am now running CM11. So I've noticed that after I lock my screen, it doesn't respond. The power button still works, though. Also, this may be unrelated, but the camera doesn't focus either, and the flash stays on as a torch until I force quit the camera. Thanks if you can help!
(I have Xposed, installed, too. I tried booting with it disabled, and it happened again. Note, this doesn't happen if I unlock the screen immediately after locking it)
firerappedR said:
So I bought my new Z2 today, rooted, unlocked the bootloader, installed recovery, and am now running CM11. So I've noticed that after I lock my screen, it doesn't respond. The power button still works, though. Also, this may be unrelated, but the camera doesn't focus either, and the flash stays on as a torch until I force quit the camera. Thanks if you can help!
(I have Xposed, installed, too. I tried booting with it disabled, and it happened again. Note, this doesn't happen if I unlock the screen immediately after locking it)
Click to expand...
Click to collapse
Official CM11 or unofficial CM11 both have the same issues
Device touchscreen doesnt respond after deepsleep
Camera doesnt work
Stay on the stock rom for now
Both CM11 releases are not to be used as a daily driver yet
Sent from my D6503 using XDA Premium 4 mobile app
Should of read the cm thread instead of making this one, kali is currently working on a fix AFAIK
apologies
Sorry guys, I thought the official CM11 was different.
No worries, touchscreen is supposed to be fixed in next build, patches have just been merged apparently
Related
Starting from yesterday, screen started to behave strangely. Sometimes it doesn't register touch at all, sometimes it registers wrong area or when I long press the screen it does the regular press. This problem is not permanent through. After about 10 minutes when I unlock the screen, it works fine, then it starts to behave strange as i described. Also relocking screen and waiting for some time "fixes" the issue. What is causing this? I am on Wolf rom 1.2 with experimental 9.1 kernel, I already reisntalled rom with wiping data, but problem persists.
Please help!
I have the same problem dude, try to flash stock ics again..
Sent from my MT27i using xda app-developers app
Well, I was going to do that, but I tried everything before it, including fixing permissions through CWM and it helped! Now screen is working normally as it was before!
I have had the Xperia Z2 for three days now, after giving my wife my Galaxy S4. Today a problem started occurring that hasn't happened so far.
When I boot into the camera from lockscreen by holding down the hardware camera button, when I try to take a photo the camera app freezes. It will either simply freeze, or it will pop-up the lockscreen asking for my security pattern, or it will allow me to depress the button to focus, but it will never actually take the photo. When I turn the screen off, re-open the screen and log-in using security pattern, I see the "Unfortunately, Camera has closed" error. On a few occasions I have been unable to re-open camera app from the app draw until I reboot the phone.
Bringing up app info and clearing data fixes the problem temporarily, but it comes back. Once the problem starts, it will happen every single time until you delete camera app data.
I am running the stock Australian ROM (Telstra branded unfortunately). Build number 17.1.A.2.55. I have yet to root or unlock bootloader as I am checking for issues like this and other reported problems first.
Has anyone experience this? Does anyone have a solution?
I have the same problem booting into the camera to take video. This happens 5 out of 10 times.
Video recording would freeze and crash the app.
My Xperia Z2 is on Build number 17.1.A.2.55 from Telstra.
Let me know if you have a solution to this!
pierrotee said:
I have had the Xperia Z2 for three days now, after giving my wife my Galaxy S4. Today a problem started occurring that hasn't happened so far.
When I boot into the camera from lockscreen by holding down the hardware camera button, when I try to take a photo the camera app freezes. It will either simply freeze, or it will pop-up the lockscreen asking for my security pattern, or it will allow me to depress the button to focus, but it will never actually take the photo. When I turn the screen off, re-open the screen and log-in using security pattern, I see the "Unfortunately, Camera has closed" error. On a few occasions I have been unable to re-open camera app from the app draw until I reboot the phone.
Bringing up app info and clearing data fixes the problem temporarily, but it comes back. Once the problem starts, it will happen every single time until you delete camera app data.
I am running the stock Australian ROM (Telstra branded unfortunately). Build number 17.1.A.2.55. I have yet to root or unlock bootloader as I am checking for issues like this and other reported problems first.
Has anyone experience this? Does anyone have a solution?
Click to expand...
Click to collapse
Did ya install some mod for camera? Or is it even rooted? If not it is sony's fault just take it back to shop. It is not meant to happen by any reason.
I purchased my Xperia Z2 from Australian Telco Telstra, and not having issue. So I guess it is not matter of software? Before it get worse or mess it,
I strongly recommend you to take it back to shop and explain everything and show it to shop assistance.
CenteaOSD said:
Did ya install some mod for camera? Or is it even rooted? If not it is sony's fault just take it back to shop. It is not meant to happen by any reason.
I purchased my Xperia Z2 from Australian Telco Telstra, and not having issue. So I guess it is not matter of software? Before it get worse or mess it,
I strongly recommend you to take it back to shop and explain everything and show it to shop assistance.
Click to expand...
Click to collapse
Thanks for your reply. I returned it and got a HTC One (M8). Much happier now. No issues whatsoever.
Just updated to Lollipop on the latest generic firmware (23.1.A.0.726) and all was great initially until I decided to try to video my goddaughters first steps.
I was then greeted with a "Unknown Error" on the 4K Camera, and the camera also Force Closed on the regular video camera function.
Is there a fix available for this, as I know the camera works perfectly under Android 4.4, but I have had nothing but problems on Android 5.0
I have taken a look in the exisiting bugs thread for Lollipop but nobody seems to have the same issue...
Have you concidered resetting your phone
See this is the wierd thing....
I've done some googling and it appears it may be a generic Android Lollipop bug that Google is aware off...
And yes, rebooting the phone does somehow clear the issue, but surely this is not the answer to have to keep rebooting the phone just to get the video camera working??
Are you sure you haven't used the flashlight before? Lollipop has a bug when after using the flashlight for a couple of minutes the camera doesn't work anymore.
I never use the flashlight on my phone :-/
Happens to me as well, but occasional random or planned reboots related to Xposed framework and modules mitigated video issues..
Hmm...that's even wierder then as my phone is purely stock...no unlocked bootloader, no root.
Hmm. At least we can rule out an unlocked bootloader as a cause now (two other users and I are/were facing the same issue and we all had unlocked bootloaders).
Hello!
I recently switched to the m4 from my trusty LG OG, an it is perfect except for one thing... it doesn't ring.
I have tried all Sony-solutions, including PC software repair, etc... but no joy. My wife also has an M4 and has the same problem.
It is worked-around by using a 3rd party lockscreen (I use Hi-Locker), which is awesome.. but not ideal due to security problems, most notably Android Pay.
My question?
Can I replace the lockscreen at the ROM level? Can I replace the basic function with maybe a lockscreen from the Z5?
Unless someone knows how to fix this
I have never compiled my own rom, but I have a reasonable level of tech-savvy. I can flash ROMS and do work in Linux.
I have rooted and unlocked my bootloader, and I am using Stock Sony ROM
I have the latest firmware
Kernel 3.10.49
build 26.1.A.2.99
I have NOT tried using an old firmware- or an alternate ROM. I probably will, but my wife doesn't love the idea for her. Thus, I would like to work out a precision fix.
My thoughts?
Idea 1. find where the stock lockscreen/security module lives.. and try and replace with something from a different phone.
Possible?
Thank you for reading.. I know some other people have these problems, as I read them in threads here.. but I didn't find much in the way of fixing.
just for reference- THIS is the problem.
just for reference- THIS is the problem.
Mustang243 said:
My phone doesn't ring when it 's locked. If phone is unlocked ringtone rings and vibrates. When it's locked no sound or vibrate. Whatsapp messages vibrate but they have no notification sound. I have checked all the settings, volume is up. Last resort is factory reset but i'm not there yet. I don't wanna lose all my settings.
E: Okay I used Sony PC Companion and used the Fix phone/tablet -thing and it downloaded the firmware and installed it so I think it reset my phone. Still my phone doesn't ring if its locked. If I press the power button when someone is calling to me, I can see the lockscreen notification on the screen but it doesn't ring or vibrate. FFS. Any ideas guys?
E2: I guess I find a solutions. Or a temporary solution. I noticed that if I disabled the screen lock, my phone would ring and vibrate normally. So I decided to try and download "Next" lockscreen app. Guess what. When I use it, my phone works perfectly. I don't know why it stopped ringing because there wasn't any new updates from Sony but it's clearly problem in Sony's software.
Click to expand...
Click to collapse
Mustang243 said:
I still have the "silent phone" issue with this update. I have to use third party lock screen app. If I use Sony's lock pattern or pin code and use my gf's phone to call my phone: screen doesn't wake, no ringtone can be heard and no vibration. When I press power-button I can see that someone's trying to call me. Anyone else experiencing this problem? I hope you understand what I tried to say, the issue is kinda hard to explain.
Click to expand...
Click to collapse
Yeah this is a huge problem and we're not the only ones suffering from it. Now I use CM Locker because Next drained my battery. I also noticed that my phone works fine if I boot on safe-mode. Still haven't figured it out which app causes the problem. Gotta wait for the 6.0 update and hope that fixes things.
Same issue with out-of-the box...
Well, have M4 'out of the box' - meaning - no custom software installed, no customized ROM, no custom lock-screen... and well - to make the ring work back I have to restart phone every few days (as soon as realize that it's not working) - oh Sony, what should I say ....
After switching to LineageOS 14.1, my Samsung S3 i9300 randomly turns off. Not a proper shutdown, screen just goes black.
Happened 7 times in 2 days so far, first time while I was tinkering with the settings, second time while I was swiping to another page in Nova Launcher, third time while I was asleep last night, woke up and discovered my phone was off. The other shutdowns happened while the phone was locked.
The device does not shut down completely. I can see the Samsung Led flashing for the message notifications. Just the display turns off. I have to go into recovery mode and reboot the system from there to get the display working again.
I came from the stock ROM. It started immediately after flashing Lineage.
If this happens on a stock rom, it is probably a hardware issue.
audit13 said:
If this happens on a stock rom, it is probably a hardware issue.
Click to expand...
Click to collapse
Thank you for your reply, but this does not happen on the stock rom.
It's definitely good that this doesn't happen in stock.
Sounds like a incompatibility between the phone and rom. Have you tried earlier or later versions of lineage?
All custom roms are considered beta. You will encounter issues. The issues should be in a list on the website/dev forum for the developers.
Beamed in by telepathy
I can also confirm this on the latest lineageos nightly update to date. It's as if phone is on standby/sleep and no way to wake it up without rebooting the phone by holding down the power button until phone restarts. I don't need to go into recovery like OP. Anyone else?
Are we the only ones experiencing this issue? Any help would be appreciated.
Gizmotech said:
Are we the only ones experiencing this issue? Any help would be appreciated.
Click to expand...
Click to collapse
You got a reply in the other thread where you posted about it:
minealex2244 said:
I'm feeling bad for you guys. Everyone should get the same beautiful LOS experience.
Thank you @Gizmotech for the last_kmsg. I think that you removed the battery to be able to reboot your phone. If you received a notification (sometimes you will receive it but it will freeze before letting you know that you got a notification) then the kernel will freeze. If the kernel is freezing it's because of root or a failed attempt to remove root (even if it said that it was a successful removal). It's very simple: you get a notification and it freezes. Maybe it will give a sound and the LED light maybe not. What's sure is that the kernel will freeze. Lastest SuperSU has this issue fixed. If you want it working then dirty flash latest build again. Tell me if the issue was fixed and avoid root until that time. After you'll tell me the results you can flash latest SuperSU and tell me again what happened. Do not remove root. This is always a dangerous thing.
Click to expand...
Click to collapse
kgndrn said:
After switching to LineageOS 14.1, my Samsung S3 i9300 randomly turns off. Not a proper shutdown, screen just goes black.
Happened 7 times in 2 days so far, first time while I was tinkering with the settings, second time while I was swiping to another page in Nova Launcher, third time while I was asleep last night, woke up and discovered my phone was off. The other shutdowns happened while the phone was locked.
The device does not shut down completely. I can see the Samsung Led flashing for the message notifications. Just the display turns off. I have to go into recovery mode and reboot the system from there to get the display working again.
I came from the stock ROM. It started immediately after flashing Lineage.
Click to expand...
Click to collapse
Providing the last_kmsg will help Simon to find a solution. If you only complain about this issue then it won't be solved. Next time make sure to include last_kmsg.
---------- Post added at 19:49 ---------- Previous post was at 19:45 ----------
shivadow said:
All custom roms are considered beta. You will encounter issues. The issues should be in a list on the website/dev forum for the developers.
Beamed in by telepathy
Click to expand...
Click to collapse
Really? Do you know what beta means? I'm sure that you don't. Beta means that it is not really stable (80% or less of the things are working) while stable means that 95% of the things are working. This explains why LOS 14.1 for S6 was considered stable: because everything was working. Also that issues are already listed in the forums.
kgndrn said:
After switching to LineageOS 14.1, my Samsung S3 i9300 randomly turns off. Not a proper shutdown, screen just goes black.
Happened 7 times in 2 days so far, first time while I was tinkering with the settings, second time while I was swiping to another page in Nova Launcher, third time while I was asleep last night, woke up and discovered my phone was off. The other shutdowns happened while the phone was locked.
The device does not shut down completely. I can see the Samsung Led flashing for the message notifications. st the display turns off. I have to go into recovery mode and reboot the system from there to get the display working again.
I came from the stock ROM. It started immediately after flashing Lineage.
Click to expand...
Click to collapse
Same problem with last lineage version. Are you found solution ?
Any news on this? g9305 boots just fine but reboots after a few seconds / minutes.
cRaZy-bisCuiT said:
Any news on this? g9305 boots just fine but reboots after a few seconds / minutes.
Click to expand...
Click to collapse
The problem is the rom or kernel. It happens to all custom roms and kernels on the s3. No-one has found the source of the problem.
Everything custom is beta even if it is considered stable. Beta means "not final". Unless you see a rom with "final" on it then you'll encounter issues at some point.
The only truly final product if you want root is stock rom rooted. If you flash a kernel you'll get the same problem.