All right, so a while ago say..few hours or a day ago, I dropped my phone. Nothing seemed wrong, everything was working fine. Until I decided to go play Abduction World Attack. It's a game where you tilt the G1 and the little character moves according to how you tilt it. Surprise Surprise I ran into my problem. The little avatar wouldn't move and it was just stuck there no matter how I turned my phone. I also just noticed that auto-rotate won't work. I believe it's because the accelerometer is broken...Anyone have any advice on how to fix this or calibrate it? I've tried calibrating inside apps that use the accelerometer. I've searched but to no avail. Help will be appreciated Thank-you.
[Edit]: A wipe has fixed this! =)
If your under warranty, you may want to try and get it exchanged. Let T-Mobile/HTC know that it just stopped working.
If you are out of warranty, you can attempt at looking for a solution by taking apart the phone. The official manual is here
The manual has all of the disassemble instructions. Hopefully that will lead you to a solution.
Sounds like it could be a hardware issue but no harm in testing to see if it is a software one. Tried rebooting the mobile? If so see if other programs like Bubble works. If not then a final resort would be a reflash to at least eliminate the software side of things.
If its no go then best to try and get it exchanged...
I've fixed it guys ^^ Seemed like a wipe would do it. I changed to the hero build for a second and then reflash CM after a wipe and accelerometer is fixed. Thanks for the suggestions though! Greatly appreciated
The power of the mighty wipe ^_- Good to hear its been sorted. Since you're the OP too, could you edit the title to SOLVED so people know?
NeoBlade said:
The power of the mighty wipe ^_- Good to hear its been sorted. Since you're the OP too, could you edit the title to SOLVED so people know?
Click to expand...
Click to collapse
Sure. OP and title has been updated!
Sure wish I had your luck. I'm having the same problem and a wipe didn't do me any good.
I have tried several different mods and none of them work.
tested with browser, bubble, Papi game apps, and Accelerometer xyz Values.
I don't have any akm files located in /data/misc
I do have a /system/bin/akmd but my ps output doesn't show it running.
whatchamccallum said:
Sure wish I had your luck. I'm having the same problem and a wipe didn't do me any good.
I have tried several different mods and none of them work.
tested with browser, bubble, Papi game apps, and Accelerometer xyz Values.
I don't have any akm files located in /data/misc
I do have a /system/bin/akmd but my ps output doesn't show it running.
Click to expand...
Click to collapse
Most likely a hardware problem then mate. You could try un-rooting and see if the accelerometer works.
If I install RC29 then the accelerometer works without issue. So that rules out hardware issue.
Here is another thread I found that goes in much more detail about what I am experiencing.
http://forum.xda-developers.com/showthread.php?t=533749
so far there isn't any movement on this thread. I'm surprised that this issue isn't more wide spread.
I just had the accelerometer on my HTC Sapphire go belly up.
Auto-rotate was broken, compass apps wouldn't initialize, tilting maze games would slowly move the ball to the top left side regardless of actual tilting, etc..
Reboot didn't fix it. However I did have a file under /data/misc/akmd_set.txt and most of the values in it were set to 0.
I renamed that file to akmd_set.txt, then killed akmd, per instructions in a neighboring thread.
akmd rose from its ashes, a new akmd_set.txt automagically appeared, with lots of different numbers for each value in it. All my accelerometer-depending features were happy again.
so yay, and all that.
As a side-note, I've been playing with some not insignificant magnets on my desk, and I'm wondering if abnormal magnetic fields around my phone might have caused the accelerometer miscalibration?
Good for my G1 too.
Kudos to the OP, this solution worked perfectly on my G1 with the same symptoms. Many Thanks!
Related
Hello there,
I've tried Googling and searching these threads, and I can't seem to find anyone else with the same problems as me, so if anyone can help me I'd be really grateful!
Basically, I've had a rooted G1 for about 6 months now, started off using JesusFreke, went on to CM and now I'm running the latest ROM with an 8 gig class 6 SD card. Anyway, everything runs smoothly except for a few niggly things. As far as I can remember I've always had most of these problems since rooting, and now they're worse than ever and starting to grate. I don't think it's my particular handset, as this is the second G1 I've had - although as I said, I haven't read of these problems with other people, so I don't really know. The problems in question are:
1. Email isn't very 'pushy' anymore - when I first got my G1, and for a while after first rooting, I was amazed at the push Gmail...I loved it, and it often worked faster than my computer email client could retrieve emails with its 5-minute interval. However, now my G1 seemingly only downloads emails when it can be bothered, and more often than not I'll do a manual refresh to find about 6 emails waiting for me. It's somewhat annoying really.
2. This is another major thing: Locale just won't recognise where it is anymore. I'll go into Locale for a few seconds, it'll snap on to 'home' or 'work', I'll come out and after about five minutes, it'll jump straight onto the default settings again. I'll do this again, and it happens again, etc. My phone knows where it is, as the maps work perfectly, and I'll even tried leaving GPS on all day, but to no avail. This is a major annoying niggle, and it seems to get better/worse with different updates. Has anyone experienced this? At the moment, Locale is virtually unusable.
3. Since I'm asking for help, the other little niggle is that to add shortcuts to my desktop takes an age...I'll do the longpress, click 'shortcut'...and then wait. And wait. As far as I can remember my phone's always done this (even the old one), but if anyone knows what I'm doing wrong it'd be really good.
In fact, if anyone can help me with any of the problems I've described I'd be really happy...the email and Locale thing are starting to become a big nuisance, and I'm starting to think about changing my handset over it, despite my love of Android, the G1 and the excellent CM updates that Cyanogen tirelessly sends out.
Thanks so much in advance,
Mark
I've never had any of those issues the gmail issue is the only one that woulg get me... what rom did you go with this time around?
Hi, I've just got the standard CyanognMod ROM with the latest 4.2.9.1
I have the same Gmail problem.
No idea how to fix it.
I'm going to say it's probably two things together:
1. Low memory. Having had your G1 for a while, you've installed lots of apps. Each app uses RAM. Low RAM makes everything sluggish and buggy. Uninstall anything you don't use regularly. Doing a full wipe and reflash of the htc update image, and then the latest cyanogenmod, will give you a blazing fast phone again, with everything working beautifully (but you'll have lost ALL your installed apps, saved sms, settings, etc.).
2. Task-killing app. You probably use Taskiller, Close Everything, or something like that. It is killing Gmail so it doesn't refresh, killing locale's location service so it doesn't know where it is, etc. Make sure you exclude ANYTHING that runs in the background constantly to work. Basically, anything that does something automatically, or generates a notification, or anything. Email, gmail, messaging, etc.
Not cool
You can't say niggly, only we can say niggly.
gmail push
there is a way to 'Set download frequency' by default.
oneofone1 said:
You can't say niggly, only we can say niggly.
Click to expand...
Click to collapse
'Niggly' is a word of Scandinavian origin which in this context essentially means 'irritating'. It is in no way related to similarly spelt offensive words, which is what I think you're getting at.
Anyway, many thanks to all those who posted help, I deleted a load of programs and it helped greatly. I had no idea that having too many apps, even in an apps2sd setup, would impact performance that much.
Still can't get Locale to work properly though. I'll delete a few more apps and see if that helps.
markdjj said:
'Niggly' is a word of Scandinavian origin which in this context essentially means 'irritating'. It is in no way related to similarly spelt offensive words, which is what I think you're getting at.
Anyway, many thanks to all those who posted help, I deleted a load of programs and it helped greatly. I had no idea that having too many apps, even in an apps2sd setup, would impact performance that much.
Still can't get Locale to work properly though. I'll delete a few more apps and see if that helps.
Click to expand...
Click to collapse
I think he is quoting "Something Something Something Darkside" It is the new Family Guy movie.
spigatelli said:
I think he is quoting "Something Something Something Darkside" It is the new Family Guy movie.
Click to expand...
Click to collapse
+10 pts for being spot on.
I'm really sorry if this has been asked already, but I looked and couldn't fine anything.
I just got a used nexus one online, and its working fine except that the auto rotation isn't working. When I tilt the phone nothing happens, sometimes if I turn the screen off and on a couple times the orientation will change, but then I have to do the same thing to get the orientation back to what it was before.
I've had this problem on four different roms, stock 2.1 and 2.2 before I rooted, and then CM5 and CM6 RC1 after. I've tried wiping and reflashing, as well as wiping the rotation settings using Amon_ra's recovery. The only thing that makes me think its a software issue is that the accelerometer seems to work fine in other apps, such as the bubble lever app, and the labyrinth game.
I've looked everywhere and can't find any fix for this issue. I really love this phone otherwise, but rotation is pretty important for me. I'm kind of at a loss at this point, so any help would be very much appreciated. Thanks!
I know it seems silly but is the box checked under settings : display?
The audio both from the speaker and headphones only seems to work after a reboot. I have no idea when it stops functioning.
This was a problem from day 1 with the free elephant kid book using the Read To Me function. I just had it happen with the music player, both the native one and MortPlayer. I had originally assumed it was a glitch with the book.
If a reboot fixes the problem, it's a software issue, right? Why did a search here not produce any similar threads? If I'm alone here, then it's a hardware issue and I'll need to unroot and return it, right?
timmyjoe42 said:
The audio both from the speaker and headphones only seems to work after a reboot. I have no idea when it stops functioning.
This was a problem from day 1 with the free elephant kid book using the Read To Me function. I just had it happen with the music player, both the native one and MortPlayer. I had originally assumed it was a glitch with the book.
If a reboot fixes the problem, it's a software issue, right? Why did a search here not produce any similar threads? If I'm alone here, then it's a hardware issue and I'll need to unroot and return it, right?
Click to expand...
Click to collapse
Your search method must be flawed, as this is a known & frequently discussed issue.
timmyjoe42 said:
The audio both from the speaker and headphones only seems to work after a reboot. I have no idea when it stops functioning.
This was a problem from day 1 with the free elephant kid book using the Read To Me function. I just had it happen with the music player, both the native one and MortPlayer. I had originally assumed it was a glitch with the book.
If a reboot fixes the problem, it's a software issue, right? Why did a search here not produce any similar threads? If I'm alone here, then it's a hardware issue and I'll need to unroot and return it, right?
Click to expand...
Click to collapse
It's defective. Get a new one.
Thanks for the reply.
Now to unroot...
Mine had the same exact problem. Audio usually stopped working after the screen went to sleep for the first time after a reboot. I recently flashed the 900mhz "screamer" overclock kernel and I've yet to have an audio problem since then. As much sense as that does or doesn't make, it seemed to fix the problem for me. Its worth a try. Hope it works for you (if you haven't already unrooted and returned by now)
Sent from my Droid using XDA App
When you get your hands on the new one, before you leave the store do this. After power on & such, try the audio (V0l + -). Works? Put to sleep for >10sec. Wake & test audio. No-work? Reboot, (Long power press) Try sleep/wake sequence again. If it works you are golden, now check a few other things & go home & root it! If it fails the test, don't let the Nook Genius tell you that you should let it charge for at least 4 hrs. before testing. The three that I have received had between 50% & 90% charge OOB. That's plenty for it to work properly, assuming the battery level meter is accurate. Put together your own checklist based on info on this forum. Crossword to test edges of screen, kbd. when charging from wall adapter etc.
Good luck, when you get a good one they are solid!
kev
trumpet444 said:
Mine had the same exact problem. Audio usually stopped working after the screen went to sleep for the first time after a reboot. I recently flashed the 900mhz "screamer" overclock kernel and I've yet to have an audio problem since then. As much sense as that does or doesn't make, it seemed to fix the problem for me. Its worth a try. Hope it works for you (if you haven't already unrooted and returned by now)
Sent from my Droid using XDA App
Click to expand...
Click to collapse
Interesting! That would support the thinking that this issue is related to timing & initializing the audio codec or something related. Hardware specs may be skewed just enough for it to not work when waking up. That's actually encouraging! Means that all those with this problem may see a F/W fix if they don't want to re-clock it.
Cheers,
kev
Well, I unrooted and restored it to factory new using the 9 reboot method. This brought the device back to 1.0.0. I then went back to the store. The manager came out, took the device, and said "it needed 1.0.1 to fix the problem. Let me load it for you." I was thinking, "whatever dude. It had 1.0.1 on it and it still had the issue." But the guy was super nice and ran off with the device to some back office. He came back while it was installing 1.0.1 and it's working fine now. I kept trying to get it to recreate the problem with no luck. (So it actually is good luck.)
I'm assuming the 1.0.1 software update didn't install properly the first time.
I could have done all that myself without going to the store.
timmyjoe42 said:
Well, I unrooted and restored it to factory new using the 9 reboot method. This brought the device back to 1.0.0. I then went back to the store. The manager came out, took the device, and said "it needed 1.0.1 to fix the problem. Let me load it for you." I was thinking, "whatever dude. It had 1.0.1 on it and it still had the issue." But the guy was super nice and ran off with the device to some back office. He came back while it was installing 1.0.1 and it's working fine now. I kept trying to get it to recreate the problem with no luck. (So it actually is good luck.)
I'm assuming the 1.0.1 software update didn't install properly the first time.
I could have done all that myself without going to the store.
Click to expand...
Click to collapse
That's interesting. I had the audio/sleep problem with 1.0.0 & exchanged it for another 1.0.0 that worked fine. ?????
I've tried browsing the forums, and even locating the post talking about the fix for the camera, and I simply can't find it. I really don't want to go without a phone seeing as my job requires my phone, but it really sucks not having a camera or a flashlight toggle.
I've seen some people that have indicated its a physical issue, however, it sporadically starts working again. Note: I would like to avoid doing the super data wipe as I'm also having computer issues at the same time. If someone needs me to post a catalog, I will need help Learning what to filter out in order to upload only the necessary info.
I've tried wiping the data through twrp advanced wipe, and of course the dalvik cache has been wiped many-a-time. Any help would be appreciated!
Um...I don't think you even explain you problem. Might want to elaborate a bit.
Sent from my Nexus 6 using XDA Free mobile app
No matter what ROM I use, no matter what camera I try to install, I cannot get it to consistently work. More often than not, cannot connect to camera. I feel like its a setting or file sticking on the "SD card" that is interfering. I also cannot use the flashlight toggle, and parts of Google+ and gallery crash at times. This has been intermittently occurring since my first flash. Blissful ROM v1.7 twrp 2.8.4.0
Tried every wipe except for the one that makes me type yes. I've already flashed boot.IMG to disable decryption, and I'm starting to think that may have something to do with it.
I was under the impression I had twrp 2.8.4.0, but after double checking, it looks like it was stuck on 2.8.2.1. I flashed the newer version from twrp manager, and now my camera is working. I didn't do anything other than install the new recovery. And yes I've tried rebooting my phone in the past. This may be a temporary fix, but I'll report back tomorrow on whether it is still working. This is very odd.
Andddddddd it stopped working again. Super legit.
Might be similar to my issue.
My camera started only showing front facing..even the option for back facing wasn't there. Did wipes in recovery and app settings. Would work, it seemed, but would revert right back to not working. At one point the camera app wasn't appearing in the app drawer at all even though it was shown in "all apps".
This occurred on stock and custom ROMs. I was advised to try flashing factory IMG but I'm well within the warranty period ( phone less than 2weeks) so I'm locking it back up and have a replacement on the way from ATT...
* I also noticed the issue starting while I was on bliss ROM 1.7
Sent from my Nexus 6 using XDA Free mobile app
My camera is really shaky and won't focus correctly in landscape mode. I returned the first phone I had for basically the same thing because it wasn't focusing in portrait mode but looked fine in landscape. I haven't seen anyone else have this issue. At first I thought the camera was inconsistent but if you zoom in you can see that it doesn't focus properly.
I'm starting to wonder why there are so many people experiencing the same or similar camera issues. The only reason I'm starting to think that it is software based and not entirely hardware based is because I was having this same issue (cannot connect to camera) on my sgs5 with cm based Roms.
I'm not saying any of this makes sense, its just strange. I wish we could help troubleshoot what the root of this problem is instead of just RMAing the device. I'm afraid to RMA with T-Mobile.
you better do it before its too late. id rma it.
cellularticulate said:
No matter what ROM I use, no matter what camera I try to install, I cannot get it to consistently work. More often than not, cannot connect to camera. I feel like its a setting or file sticking on the "SD card" that is interfering. I also cannot use the flashlight toggle, and parts of Google+ and gallery crash at times. This has been intermittently occurring since my first flash. Blissful ROM v1.7 twrp 2.8.4.0
Tried every wipe except for the one that makes me type yes. I've already flashed boot.IMG to disable decryption, and I'm starting to think that may have something to do with it.
I was under the impression I had twrp 2.8.4.0, but after double checking, it looks like it was stuck on 2.8.2.1. I flashed the newer version from twrp manager, and now my camera is working. I didn't do anything other than install the new recovery. And yes I've tried rebooting my phone in the past. This may be a temporary fix, but I'll report back tomorrow on whether it is still working. This is very odd.
Click to expand...
Click to collapse
There is no sdcard.
Try going back to factory sysimage, and data wipe.
Are you using any "added in" camera software? If so, what?
cellularticulate said:
I'm starting to wonder why there are so many people experiencing the same or similar camera issues. The only reason I'm starting to think that it is software based and not entirely hardware based is because I was having this same issue (cannot connect to camera) on my sgs5 with cm based Roms.
I'm not saying any of this makes sense, its just strange. I wish we could help troubleshoot what the root of this problem is instead of just RMAing the device. I'm afraid to RMA with T-Mobile.
Click to expand...
Click to collapse
Similar issue. Get errors "Unfortunately, camera has stopped" or "cannot connect to camera." I picked up the phone right before a 2 week vacation so unfortunately I can't bring back to AT&T. Hopefully Moto plays nice. Problems originally occurred on stock 5.0 before the 5.0.1 update. Since AT&T was lagging on OTA, I flashed to the official BlissPop rom but I have the same problems. Sometimes it'll work like it's supposed to for a couple days but always reverts back to the errors. Nothing like being at the top of a mountain in Hawaii and "cannot connect to camera" right????Since I've read about this happening on so many different firmware variations, I have to believe it's a hardware issue.
I have only had issues with the stock camera app. Ive been running Pure Shamu for 2.5 weeks now and only using the Google Camera app from the play store (the one with HDR+ and the icon has the lens filled with rainbow colors) with absolutely no issues and only getting excellent quality pictures.
Had the issue where the camera wouldn't focus and everything on the screen gets jiggly and wavy like there's some sort of interference. I had motion sickness looking at the screen. Called Moto for an advance replacement and after a week of delay due to stock issue...somehow they were kind enough to upgrade me to a CW 64gb model. I hope it's new and no more camera issues.
Has everyone who got the 'no-focuse OIS' issue gotten new phone on RMA?
I took mine to repair few days ago and they said that they won't give me a new phone instantly, rather they try to fix the OIS. Not sure how that is going to work..?
They also suggested that this issue might be "self inflicted" or just an "feature" of the camera itself. fml.
Giants2010 said:
Similar issue. Get errors "Unfortunately, camera has stopped" or "cannot connect to camera." I picked up the phone right before a 2 week vacation so unfortunately I can't bring back to AT&T. Hopefully Moto plays nice. Problems originally occurred on stock 5.0 before the 5.0.1 update. Since AT&T was lagging on OTA, I flashed to the official BlissPop rom but I have the same problems. Sometimes it'll work like it's supposed to for a couple days but always reverts back to the errors. Nothing like being at the top of a mountain in Hawaii and "cannot connect to camera" right????Since I've read about this happening on so many different firmware variations, I have to believe it's a hardware issue.
Click to expand...
Click to collapse
I returned mine to stock, unroot/locked boot loader, factory reset, before shipping it off and the camera issue was still there. Maybe hardware related I'm thinking.
Sent from my Nexus 6 using XDA Free mobile app
Something rather peculiar Ive noticed...
I didn't really pinpoint this until today, but the camera very consistently starts working when you go into fastboot, load the recovery, and then boot into system. I'm really, sincerely not quite sure why this would be happening, but I still feel like it has something to do with boot.IMG
If any devs can point me in the right direction to try and track down the possibility of this being an issue, I'd love to potentially fix a bunch of people's camera issues (albeit there is probably also a hardware defect direct from moto).
Is logcat going to pick up on issues that originate from boot?
cellularticulate said:
I've tried browsing the forums, and even locating the post talking about the fix for the camera, and I simply can't find it. I really don't want to go without a phone seeing as my job requires my phone, but it really sucks not having a camera or a flashlight toggle.
I've seen some people that have indicated its a physical issue, however, it sporadically starts working again. Note: I would like to avoid doing the super data wipe as I'm also having computer issues at the same time. If someone needs me to post a catalog, I will need help Learning what to filter out in order to upload only the necessary info.
I've tried wiping the data through twrp advanced wipe, and of course the dalvik cache has been wiped many-a-time. Any help would be appreciated!
Click to expand...
Click to collapse
This is a hardware issue. Check http://forum.xda-developers.com/nexus-6/help/camera-lens-movement-t2984298
rdizzle707 said:
This is a hardware issue. Check http://forum.xda-developers.com/nexus-6/help/camera-lens-movement-t2984298
Click to expand...
Click to collapse
Not the issue I'm explaining though. This is a bit more deeply seeded of an issue. When I boot directly into the ROM, my twrp installer says I'm back on 2.8.2.1, but when I boot into fastboot and then twrp, and then ROM, it says 2.8.4.0 and my camera works. This is legitimately weird as ****.
cellularticulate said:
Not the issue I'm explaining though. This is a bit more deeply seeded of an issue. When I boot directly into the ROM, my twrp installer says I'm back on 2.8.2.1, but when I boot into fastboot and then twrp, and then ROM, it says 2.8.4.0 and my camera works. This is legitimately weird as ****.
Click to expand...
Click to collapse
Ohhh man that is weird.
rdizzle707 said:
This is a hardware issue. Check http://forum.xda-developers.com/nexus-6/help/camera-lens-movement-t2984298
Click to expand...
Click to collapse
rdizzle707 said:
Ohhh man that is weird.
Click to expand...
Click to collapse
It appears a bit more stable now. I tried flashing twrp from my computer and it seems to be a bit more nice. That and normal reboot to twrp doesn't say 2.8.2.1 - let me check twrp manager now.
And my camera and flashlight have worked for almost three days now. Dafuq.
Same issue. "Unfortunately, Camera has stopped."
No flash light available, only front camera working, clicking on HDR exits the app with the aforementioned error message.
Has anyone solved this issue?
I was on 5.1 stock (with root) and now I've updated to 5.1.1, but with no change to the Camera behaviour.
Seems once again Sony can't seem to get a stable phone. Shame as it offers so much potential with good design and great specs but failing on software again.
Constant app crashes, phone freezing,
Just goes to show you can't just chuck all the latest bits in a package and think it will work.
Going to have to return this unless there is a sudden fix in the next few days as I only have a 14 day change or mind.
That hasn't been my experience at all. I got the US phone and flashed the UK firmware. I haven't had any issues whatsoever. You should try a factory reset before returning the phone.
I have it for 2 weeks now, no freeze or reboots whatsoever... European Firmware here...
My phone was purchased from O2 in the UK. Don't think there is much bloat on there so don't think it's O2 that's screwed it up.
Phone is completely standard with just a handful of apps on it.
So far I have had numerous '' email has stopped working' to Google stopped working to music not working errors.
OK Google seems to hardly ever work. Almost seems like it can't hear the hot word.
I also think that many of the push services are being put to sleep which is why the battery life is so could as I often don't get notifications until I wake the phone yet the same accounts on my old s3 always come through first.
So far had one update come out for the phone. Don't know if it's the latest firmware though.
I can totally not agree with you.
Well I guess all I can do is try reset then but it's such a pain in the ar#e putting all your info back in again.
hpsauce37 said:
Well I guess all I can do is try reset then but it's such a pain in the ar#e putting all your info back in again.
Click to expand...
Click to collapse
Does the launcher you use rebuild your home screens after a reset? I still use Google Now Launcher, and after a reset, when I reinstall GNL, everything is put back in its proper place, even web browser page links.
I am using the US firmware, and have not experienced any of the problems you mention. You may have a defective unit. Then again, if you're not happy with the phone for other reasons (and there certainly are things that could be better), you certainly don't want to wait past the return date!
I'm running the UK firmware with the US OEM file to have Volte and fingerprint sensor on T-Mobile and has been rock solid since day one. I would reset.
Have reset the phone and just setting it back up.
Will see how it goes over the next few days.
One thing I did think that was odd previously when it was playing up was when it would crash and reset itself was that when it started up it was on the Google keyboard set up screen. I had installed the Google keyboard as I preferred it to SwiftKey. Maybe the issues were linked to that somehow.
Wow too many errors there... Probably a faulty unit... Or maybe u should do a software repair with Sony pc companion
Don't forget it runs Android Orea 8.0 by means a lot of third party apps may not fully compatible at this moment, consider not many phones running Oreo hence the app developers are not in hurry to tweak their app to run smooth in Oreo. That's what causes the occasional app crashes I believe.
OK so after the full reset and initial impressions are good. Seems smooth with no crashes. I'm back running nova launcher (previously instilled this as thought it might be linked) ive also not installed Google keyboard yet and giving SwiftKey a go.
Only issue that really remains is the one with the ambient sensor. Find my self having to switch the adaptive brightness off at night when using the phone as it jumps around. Need to then switch it back in on the day where it seems fine. Hopefully a fix comes for this soon.
hpsauce37 said:
OK so after the full reset and initial impressions are good. Seems smooth with no crashes. I'm back running nova launcher (previously instilled this as thought it might be linked) ive also not installed Google keyboard yet and giving SwiftKey a go.
Only issue that really remains is the one with the ambient sensor. Find my self having to switch the adaptive brightness off at night when using the phone as it jumps around. Need to then switch it back in on the day where it seems fine. Hopefully a fix comes for this soon.
Click to expand...
Click to collapse
On reddit someone write that he downloaded LUX https://play.google.com/store/apps/details?id=com.vitocassisi.luxlite and everything was working much much better. Maybe later i will find the post. (https://www.reddit.com/r/SonyXperia/)
No single reboot or app crash for me.
The only thing that crashes on me on occasion is Google Photos, other than that, rock solid so far.
Just had an a 3rd party app crash but as someone mentioned above it might be because the developer has not updated yet for oreo???
Other than that been much better so far
Davka said:
No single reboot or app crash for me.
Click to expand...
Click to collapse
Same for me. 3 weeks i have got it 100% stable.:good:
Uhm ok I guess now it's my turn.
Today the "touch" went crazy. 2 times. Like for example keeping pressing recent button ? will result in multiple touches. Basically every touch is not a "pressing" touch. So I can't do swiping or other keep pressing relative touching. First time happened, a reboot fixed. Second time nothing worked. I have to SHUT DOWN THE PHONE AND WAIT A LITTLE BIT, then turn it on and everything was OK...
Is it just me?
P.s. UPDATE: I tried everything, safe mode, total reset, even software repair through PC companion...nothing. Its obviously a hardware problem, not software related. I returned this morning to assistance. They should give it back to me within a week...
My first week with XZ1C, 100% working, perfect, no reboot or other problems. One of the best phones I ever bought...
Phone's stable, no software/hardware issues. Working away reliably, battery consistently giving me expected results (ending day with 25%-50%, depending on use), connectivity perfect, performance smooth as butter.