Related
Is it me, or did froyo fix the "crazy screen" bug? I also noticed that my phone doesn't get as hot when it's been charging on my car dock.
I'm running FRF50 since it was released. The screen issue is long gone. I use to have it a couple of times a day. I sometimes get it but that's once a week.
lorin.bute said:
I'm running FRF50 since it was released. The screen issue is long gone. I use to have it a couple of times a day. I sometimes get it but that's once a week.
Click to expand...
Click to collapse
This, and I'm on FRF85B
Gotta be the best part of froyo for me, crazy screen bug fix, flash player, Jit compiler.
Which crazy thing happening are you guys screaming about? Are you talking about when the touchscreen would begin to register touches in the wrong place until the screen is turned off and on again?
Yeah that's what they are talking about. But the bad news is this problem still exists. I've had it happen many times on froyo. It's not gone at all.
RogerPodacter said:
Yeah that's what they are talking about. But the bad news is this problem still exists. I've had it happen many times on froyo. It's not gone at all.
Click to expand...
Click to collapse
Funny thing is that I had those issues on an AT&T-banded phone and they have gone way downhill since Froyo.
I find the granularity/preciseness of the screen better, and more responsive when, for example, you are dragging left-to-right and you start dragging up-down. However, I only do this in the browser so it could be down to better browser performance and/or JIT?
Still have screen uncalibration issues but seem to be better in 85 than 72
Does indeed seem to be a thing of the past, and on a similar note, it's improved the capacitive button accuracy as well.
Good that they've done it, but now I keep hitting them in the wrong place.
I'm using FRF91. Crazy screen bug happens with me twice a day. I don't know what I do to go away, but after a few minutes it stops by itself.
Ok I have been noticed a new problem for the past few days where the screen did not response at all when I turned on the phone. I cannot slide the unlock bar to unlock it. I had to turn it off and on again for one or two times to make the screen response again. Anyone else having this same problem?
Crazy screen occurrence definitely reduced.. however, it still happens when phone heats up significantly.. say, on a dash board while navigating. It's most definitely heat-related... so it must be hardware =(
I'm running Geo's FRG83 and I get it quite a bit when using Skype. I've seen this problem from the beginning and haven't seen a reduction in this issue with later versions of Android. It is the only problem I have with Android/N1.
vzontini said:
I'm running Geo's FRG83 and I get it quite a bit when using Skype. I've seen this problem from the beginning and haven't seen a reduction in this issue with later versions of Android. It is the only problem I have with Android/N1.
Click to expand...
Click to collapse
I've had the N1 since day one and never had this bug. But I don't use Skype...
I meant to create this thread a while ago, but thought it was now time to do so given the fact I'm getting 2-3 reboots per day, and doing lots of different things.
The last reboot was just as I begun to upload a YouTube video, but it can happen when doing anything - or when doing nothing (as in it will sit on a desk and restart by itself).
I can now see other people talking about it, but it would be good to establish just how big a problem there is and perhaps work out how/why it's happening?
jonmorris said:
I meant to create this thread a while ago, but thought it was now time to do so given the fact I'm getting 2-3 reboots per day, and doing lots of different things.
The last reboot was just as I begun to upload a YouTube video, but it can happen when doing anything - or when doing nothing (as in it will sit on a desk and restart by itself).
I can now see other people talking about it, but it would be good to establish just how big a problem there is and perhaps work out how/why it's happening?
Click to expand...
Click to collapse
Have done a factory reset? I've seen a few reports of reboots and soft-reboots and it could very well be user installed apps, settings and other stuff causing it.
Try a full factory reset and install the most "needed" stuff only. Try it for a day or two.
Sent from my C6903 using Tapatalk
I'm really not keen on doing that if I can help it. I'd sooner wait for an update, or someone figuring out what is causing the problem if there's a workaround temporarily.
Over the years I've done loads of resets and reinstalls, only to find it doesn't fix the problem and just wasted hours of my time.
Getting the random reboots as well. On a couple of occasions I had a running out of memory message just before reboot. Nothing installed I didn't have on previous Samsungs with no issues.
Sent from my C6903 using Tapatalk
travisb said:
Getting the random reboots as well. On a couple of occasions I had a running out of memory message just before reboot. Nothing installed I didn't have on previous Samsungs with no issues.
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
I've been at an exhibition today and it was quite embarrassing (and frustrating) to have it crash twice. Once when uploading the YouTube videos (as mentioned) - which fortunately resumed okay, and then later when I was trying to watch the Apple event (via The Verge).
One thing I've noticed from the beginning, is that changing settings sometimes required a reboot to take effect
Sent from my C6903 using Tapatalk
I'm not expecting much, but I'm now downloading the Central Europe FTF and will flash that to see if it makes any difference at all (currently on commercial/journalist version).
Anything I can try that won't force me to start from scratch has to be worth it.
http://www.xperiablog.net/2013/10/22/minor-xperia-z1-update-14-1-g-2-259-certified/
looks like a minor bug fix fw is coming real soon.
In the interest of scientific research (and reading the high CPU thread) I've backed up my sd card, re formatted it and just copied the music and DCIM folders back in, to see if that makes any difference. Card is genuine SanDisk 32gb class 10 card. Watch this space.
Sent from my C6903 using Tapatalk
Gitaroo said:
http://www.xperiablog.net/2013/10/22/minor-xperia-z1-update-14-1-g-2-259-certified/
looks like a minor bug fix fw is coming real soon.
Click to expand...
Click to collapse
Good news. Some weird stuff happening here.
Latest issue was the phone vibrating solid when pinch zooming (in or out) which was rather annoying!
jonmorris said:
Good news. Some weird stuff happening here.
Latest issue was the phone vibrating solid when pinch zooming (in or out) which was rather annoying!
Click to expand...
Click to collapse
Glad to see Sony keeping up with the updates
I have the same problem with the Z1. Also on ...257 and using 4G/3G. On the old firmware the phone hard-crashed several times and needed at 'hard-reset' at the simcard. But that happens not now - only 'soft restarts'. But very annoying. It happens both when using the phone and when its idle (in the night for example it restarts several times). You can see the restarts in the log on the phone.
I have some 'old' samsungs and they almost never restarts (sometime app's closes - but thats different) . I didn't expect such an unstable product from Sony when it's so expensive.
The value doesn't matter. It's just a silly bug that they need to fix quickly. I fear it will be a few weeks potentially for us to get it.
jonmorris said:
The value doesn't matter. It's just a silly bug that they need to fix quickly. I fear it will be a few weeks potentially for us to get it.
Click to expand...
Click to collapse
I've not had a single random restart.. I've been on Global LTE firmware for a week and have just changed to Central Europe one.. Will report if anything happens...
Two this evening with central Europe firmware, so clearly need new version ASAP. It's almost getting to the point where I can't use it because reset will happen at any moment.
Yes, also had 2 in last 30 minutes. So sd card reformat not a cure.I've contacted @SonyXperiagb on Twitter to see if they are aware of problem.
Sent from my C6903 using Tapatalk
it is a bug on sony fw and appear on google 4.1 - 4.2 android. it has something to do with wifi sleep power policy and wakelocks, im not sure. I had experience this problem with many devices on 4.1 and 4.2, include samsung ones. The easiest way to fix is to reset to factory and trace back your steps, anything to do with wifi (auto update, auto upload) is the culpit. Or if you can remember, try to trace back so you dont have to factory reset .
on .534, i had this problem when turning on update via wifi only in update center settings, get sod and constant restarts. disable it does not help, only to find out has to reenable again backlight optimisation.
Good luck!
I don't think that's it. Just need to wait for fix. Didn't have problem before this update, ever.
jonmorris said:
I don't think that's it. Just need to wait for fix. Didn't have problem before this update, ever.
Click to expand...
Click to collapse
the fix are only those i told , further more updates will fix it but you can do it manually your self
A factory reset with a whole world of pain, and no guarantee it won't still mess up, isn't really a solution to me. Sorry!
Hi guys,
I have encountered massive sudden unresponsiveness about 3 times since I've got the phone and I'm trying to troubleshoot the problem.
The phone becomes very unresponsive with extreme lag and eventually after a long wait it reboots itself. I saw it twice on Nougat leaked beta and just today, on official OOS4.
On one occasion I encountered while it was charging in the car, and navigating. It was frustrating as GPS wasn't reliable. Phone felt warm too.
However, on other occasions, I was doing some simple tasks like browsing FB and the issue started. I highly doubt this is CPU throttling as I I've gotten the phone hotter before without any problems.
Now, is there any app which logs CPU resources in the background? Kinda like Windows task manager which tells you which app is hogging resources. I have Wakelock detector which is great, but the app using more batt is not necessarily the culprit.
So far, I replaced LightFlow with LED blinker and will monitor. Any ideas, feel free to share.
Thanks for reading!
MasK said:
Hi guys,
I have encountered massive sudden unresponsiveness about 3 times since I've got the phone and I'm trying to troubleshoot the problem.
The phone becomes very unresponsive with extreme lag and eventually after a long wait it reboots itself. I saw it twice on Nougat leaked beta and just today, on official OOS4.
On one occasion I encountered while it was charging in the car, and navigating. It was frustrating as GPS wasn't reliable. Phone felt warm too.
However, on other occasions, I was doing some simple tasks like browsing FB and the issue started. I highly doubt this is CPU throttling as I I've gotten the phone hotter before without any problems.
Now, is there any app which logs CPU resources in the background? Kinda like Windows task manager which tells you which app is hogging resources. I have Wakelock detector which is great, but the app using more batt is not necessarily the culprit.
So far, I replaced LightFlow with LED blinker and will monitor. Any ideas, feel free to share.
Thanks for reading!
Click to expand...
Click to collapse
if you saw these on Nougat leaked beta, its normal, because as the name says, its an old build, not the one that came out before EOY. On official build, its normal as well, being Beta 1 build. I`m using it too, and I encounter a lot of lag, small freezes , and things like there. These are going to be fixed, but we just need to simply wait for OnePlus to do their job. And I`m ok with this, since I`m also working in development branch and I know how their processes work
smilirulz said:
if you saw these on Nougat leaked beta, its normal, because as the name says, its an old build, not the one that came out before EOY. On official build, its normal as well, being Beta 1 build. I`m using it too, and I encounter a lot of lag, small freezes , and things like there. These are going to be fixed, but we just need to simply wait for OnePlus to do their job. And I`m ok with this, since I`m also working in development branch and I know how their processes work
Click to expand...
Click to collapse
Thanks. I've searched quite a bit for this issues but I couldnt find it. I felt that nobody else saw it. The occurrence might be low, but the problem is big. Phone becomes unusable for quite a substantial amount of time.
Lets see how it goes.
MasK said:
Thanks. I've searched quite a bit for this issues but I couldnt find it. I felt that nobody else saw it. The occurrence might be low, but the problem is big. Phone becomes unusable for quite a substantial amount of time.
Lets see how it goes.
Click to expand...
Click to collapse
Have you tried to reset to factory settings after update? That might help
smilirulz said:
Have you tried to reset to factory settings after update? That might help
Click to expand...
Click to collapse
I didn't feel the need for it, as all my installs were clean from scratch. So having this issue across at least 2 FW tells me that it's likely a rogue app causing this..
What about the stable version of Nougat here?
http://otafsc.h2os.com/patch/amazon...s3TOxygen_28_OTA_035_all_1612310259_2dc0c.zip
Link from this original thread: https://forum.xda-developers.com/oneplus-3t/how-to/zip-flashable-firmware-modem-t3509015
m0d hipp� said:
What about the stable version of Nougat here?
http://otafsc.h2os.com/patch/amazon...s3TOxygen_28_OTA_035_all_1612310259_2dc0c.zip
Link from this original thread: https://forum.xda-developers.com/oneplus-3t/how-to/zip-flashable-firmware-modem-t3509015
Click to expand...
Click to collapse
Yup.. I am using that right now. Saw the issue once so far.
Hard to say if it's a rogue app without knowing which apps you have installed
I'd recommend a factory reset since that's usually the first troubleshooting step. Try installing apps back slowly, and only the ones you absolutely need. I'm on the stable nougat build and haven't noticed that happen with me yet.
My phone has been doing this for days now. Stock, L29 B120. I've stripped out any recent installed apps. Is anyone else suffering?
Thanks
damage98 said:
My phone has been doing this for days now. Stock, L29 B120. I've stripped out any recent installed apps. Is anyone else suffering?
Thanks
Click to expand...
Click to collapse
First, update it. Second, built in Facebook application could be to blame. Disable it, but first, update your phone.
Floodland said:
First, update it. Second, built in Facebook application could be to blame. Disable it, but first, update your phone.
Click to expand...
Click to collapse
I have never used Facebook and the build I have is the latest afaik, when I check for update it says none available. It got steadily worse so I've returned it today to Amazon and ordered an s8. P10 was nice phone, shame it started rebooting. Thanks for helping!
I couldnt find a solution or the same issue on the forums.. so here is my problem:
Pixel 4XLs face unlock is so bad. After a few unlocks the phone says "clean sensor". Rebooting usually does the job for a few hours.
I browsed the web and this error is common on so many Pixel 4/XL devices.
Is there a solution to this? Any CustomROM or Kernel solving this issue?
I am on stock kernel/ROM and wiped the whole thing before freshly installing Android 12.
Thanks!
Matzeus said:
I couldnt find a solution or the same issue on the forums.. so here is my problem:
Pixel 4XLs face unlock is so bad. After a few unlocks the phone says "clean sensor". Rebooting usually does the job for a few hours.
I browsed the web and this error is common on so many Pixel 4/XL devices.
Is there a solution to this? Any CustomROM or Kernel solving this issue?
I am on stock kernel/ROM and wiped the whole thing before freshly installing Android 12.
Thanks!
Click to expand...
Click to collapse
Probably a hardware issue. Find one of the many sensor testing apps and run it several times to identify a weak or defective sensor. There is not going to be a cleaning or software solution. If you do find a sensor not working 100%, do another clean wipe and test again before looking into replacement. Normally the FR on the P4 is extremely fast and accurate.
Thanks @v12xke for your reply!
To be honest, i dont think it's an hardware issue. See this link on the google forums: https://support.google.com/pixelpho...ing-the-dreaded-clean-the-top-of-screen?hl=en
There are countless other posts and threads about this error.
I should mention that the issue was there from time to time on Android 11 too. Looking at googles changelog, they tried to "fix" the issue in their updates. Nothing helped yet.
Matzeus said:
Thanks @v12xke for your reply!
To be honest, i dont think it's an hardware issue. See this link on the google forums: https://support.google.com/pixelpho...ing-the-dreaded-clean-the-top-of-screen?hl=en
There are countless other posts and threads about this error.
I should mention that the issue was there from time to time on Android 11 too. Looking at googles changelog, they tried to "fix" the issue in their updates. Nothing helped yet.
Click to expand...
Click to collapse
Google forums are a joke, this issue has *nothing* to do with Android11 or 12... and no, there is not a fix coming from anywhere. You're going to have to fix it yourself. Have you removed and re-added your facial profile at least once or twice since this started? Have you been able to replicate in safe mode? How can you know it is not a hardware issue if you don't test the sensors? It's just one step in the process of elimination. Try these and you may discover something you didn't know before.
v12xke said:
Google forums are a joke, this issue has *nothing* to do with Android11 or 12... and no, there is not a fix coming from anywhere. You're going to have to fix it yourself. Have you removed and re-added your facial profile at least once or twice since this started? Have you been able to replicate in safe mode? How can you know it is not a hardware issue if you don't test the sensors? It's just one step in the process of elimination. Try these and you may discover something you didn't know before.
Click to expand...
Click to collapse
How can you say google forums are a joke when literally hundreds of people are having the same issue? I dont want to believe that we all have hardware issues. Otherwise the hardware would be some hot garbage.
I removed and readded the face multiple times already.
I booted into safe mode. It works there. But like I said, it also works after a normal reboot for some hours/days before it needs a reboot again.
I also did test the sensors, no errors there. However my next step is to run the test when the error is present.
Any specific suggestion on which app I should use for testing?
Thanks again.
@Matzeus
No specific sensor app. Facial data is stored on the Titan M chip, and the only way I know to wipe that facial data and potentially fix it is by doing a factory reset from the stock recovery. Fastboot flashing will not wipe the Titan data and even from recovery is only a partial wipe. If you've ever had TWRP installed, there is a looong thread on broken face lock there. FDR from both recovery and setup would be my next suggestion.
@v12xke
In the past i ran the factory default from the system settings, didnt help. After that I used Googles "Android Flash Tool", which didnt help either.
Additional information: the device has never been rooted or anything. Always been on stock firmware.
Anyways, small update on the whole thing:
The issue occured again, I ran the app "Soli Sandbox" and it simply didnt do anything. So far so good.
After closing Soli Sandbox and clicking on the face unlock option in the system settings, magically everything worked properly again. Even without a reboot.
I am not sure what solved the error now..
I guess its safe to say, that all motion gestures stop working once the problem occurs.
Will keep this thread updated as I find out more.
I've had absolutely no major issues with my Pixel 4 XL's face unlock. I've upgraded from android 11 to 12 and still working perfectly. Yeah, i get the odd clean the bar notification but goes away after a bit and it just works.
The face unlock is fantastic on the Pixel 4 XL
The march update claims to have brought some improvements to Pixel 4s face unlock feature. At least thats what they say in the official changelog.
Biometrics
General improvements for face unlock stability & performance *[4]
Lets see if the problem is gone now. Will keep this thread updated.
sufy1000 said:
I've had absolutely no major issues with my Pixel 4 XL's face unlock. I've upgraded from android 11 to 12 and still working perfectly. Yeah, i get the odd clean the bar notification but goes away after a bit and it just works.
The face unlock is fantastic on the Pixel 4 XL
Click to expand...
Click to collapse
It's uncannily good. I keep the phone upright in a cradle by my PC so I can monitor it, and all I have to do is turn my head to peek, and it unlocks every time. It's pretty amazing. I've never had a problem with it.
The last official update didnt help either. My hope for a fix from Google is gone.
-------------------
I have now installed LineageOS. Its been a week and Face Unlock is now working perfectly fine.
Will keep this thread updated in case anything stops working
Matzeus said:
The last official update didnt help either. My hope for a fix from Google is gone.
-------------------
I have now installed LineageOS. Its been a week and Face Unlock is now working perfectly fine.
Will keep this thread updated in case anything stops working
Click to expand...
Click to collapse
Still going strong? And did you notice this issue on Android 10?
@puzzlefighter
Still on LineageOS 18.1, no Face Unlock issues since I installed the ROM.
I am honestly not quite sure if this issue occured on Android 10 already. But i think so, yeah.
Matzeus said:
@puzzlefighter
Still on LineageOS 18.1, no Face Unlock issues since I installed the ROM.
I am honestly not quite sure if this issue occured on Android 10 already. But i think so, yeah.
Click to expand...
Click to collapse
Thanks. I've got a new 4 XL that definitely has this issue but I didn't spend much time with it before updating to 12 from 10. It's a real PITA. I've never installed a custom ROM, but thinking I may need to do what you've done as this is irritating af.
@puzzlefighter
Just go for it man.
I was so upset about face unlock and i regret that i didnt install a custom ROM earlier.
Share your results afterwards please if you installed a custom ROM
this is not a hardware problem, but a software one, it started with the release of android 12, the problem is not in the face unlock sensor, but in the proximity sensor, it sticks, as if it was closed with a finger, I use Pixel experience + 12, this firmware does not have this problem, I'm disappointed with google developers(