Related
My phone has reboot a few times since ive purchased it, on active phone calls, twice today alone. I have a feeling its a software compatibility issue with one of my apps, but i just wanted to see if other people have experienced this, and any advice before i try a factory reset.
My phone is not rooted. It has the latest OTA update. When i first booted phone, it did a google backup
My other question was on the NFC. When i have NFC checked in the wireless area, it works great. But as soon as i turn it off, and try to turn it back on, it gives an error code. It wont turn back on until i reboot the phone, and than it checks just fine again until i turn it back off. I played with a phone at BB and it gave an occasional error when i cycled the check mark fast, but it always corrected the error eventually. This is probably another software bug, but just seeing if anybody else is experiencing this.
If i reset my phone, i will lose all my save game data correct?
My Nexus S is also resetting during phone calls, four times in a row now.
Is there any news on this issue?
http://forum.xda-developers.com/showthread.php?t=880497
I just reported rebooting issue to the Google. Please add your comments and star it, so Google will be aware of the problem and start fixing it!
http://code.google.com/p/android/issues/detail?id=13674
I exchanged the phone, and it was great for a week or so, but just tonight reboot twice during an active calls. I suspect it to be some sort of software bug, but, I'm most likely going to be exchanging it again. Works great until you need to use the phone as a phone, than it doesnt work.
Psosmith82 said:
My other question was on the NFC. When i have NFC checked in the wireless area, it works great. But as soon as i turn it off, and try to turn it back on, it gives an error code. It wont turn back on until i reboot the phone, and than it checks just fine again until i turn it back off. I played with a phone at BB and it gave an occasional error when i cycled the check mark fast, but it always corrected the error eventually. This is probably another software bug, but just seeing if anybody else is experiencing this.
Click to expand...
Click to collapse
I can recreate this problem as well, and was a major concern for me (didn't want to have a defective NFC down the line when/if it becomes common use). After speaking with some people over at Android Central, one of the editors had this to say:
"Yes, if I toggle the NFC switch enough times I will see the error notification. It still works as intended though. Looks like there is a "cool down" time on the NFC hardware, and messages to the kernel are getting picked up as errors. Either the filter needs tweaked (the filter that reports kernel messages) or the output from the NFC hardware needs "re-worded"
Makes sense to me. I wouldn't worry too much about it. However, I did create a report to bring to Google's attention, if you feel like starring it: http://code.google.com/p/android/issues/detail?id=13581
Hi guys,
It seems that after receiving the new OTA update I ran into some issues.
My problem is that after installing the update my phone started to occasionally refuse to unlock the screen after pressing the power button.
If I connect the charger the screen unlocks but otherwise I have no option to unlock it.
I did a Factory restore (of course I lost every bit of apps I had installed - even tough I had the Backup settings activated-) and it seems that I'm seeing the same problem a few times a day.
Has anyone encountered this issue?
The phone is bought from Vodafone and original software installed.
Haven't rooted or S-off it.
Thanks
if ur phone is s-on and have same issue like s-off phones thats actually good news..seems that HTC messed up something...maybe is good advice for u to give phone to repair service if is s-on and see what thay can say about that.
I actually had that bug BEFORE the update, but not after. Instead of that, HTC Locations stopped working after the update and still is refusing to start even after factory resets and reinstall.
I have tried to contact HTC through their website to ask wheter something can be done about the issue, but the "Email Us" form doesn't seem to be sending anything after pressing submit and the "Chat with Us" form just shows blank white... I tried them on IE, FF and on my phone but they all show the same kind of behaviour.
It's really beginning to get irritating...
Clearly a software issue if it really happened after the OTA.
Wiping your Cache, Dalvik-cache partitions along with your Data (Factory Reset) should be able to refresh your phone as a "brand-new" one. That is if you can.
Stock recovery has an option to wipe Data and Cache.
If these still doesn't work, shove it to HTC's arses.,
Just kidding..
Send it for repair or maybe show it first to them.
some more bug.
-> live wallpaper sometime hang.
Starting yesterday I disabled the new feature "Trace keyboard" and since then the phone unlocked everytime.
Has anyone else kept this option activated and working ok?
2.3.5 OTA suxxxxs
Hi All,
I got OTA 2.3.5 Sense 3.0 on last Friday.
Since I have the screen problem = after a call sometimes I cannot unlock the screen with power button. If connect to the charger it's unlock and after the
power button works again. My phone is S-ON, fully original.
And I have 2 friends, they have Desire S and got this update too,
and after it the problem appear on their phones too.
So I think something wrong with new OTA update.
And I also notice the TTS Service, don't work too, it's always
halted.
(I made a factory reset and my friends too, but we have this problem too)
Any idea?
Everybody "got" this bug with OTA?
Bye,
Istvan from Hungary.
Wait for fix from HTC. They messed up something.
~Swaypovano sa Desire S BRE!~
I was finally able to get in touch with HTC regarding the Locations bug. The service agent said that he has never heard of such a problem before. His advice was that I should try the factory reset once more without the SIM card and without logging in to my Google account. I did that but the Locations still won't work. Only advice after this was to send my phone in for service... I'm really not happy with sending it in just to get an app (that was broken by their own update) to work again. I'm also pretty sure there was something wrong with the update to begin with considering all the new bugs being surfaced all the time.
This is really frustrating...
Would the people that have updated please tell wheter their Locations works perfectly? And if so, where are you from?
Bmw_m6 said:
Hi All,
I got OTA 2.3.5 Sense 3.0 on last Friday.
Since I have the screen problem = after a call sometimes I cannot unlock the screen with power button. If connect to the charger it's unlock and after the
power button works again. My phone is S-ON, fully original.
And I have 2 friends, they have Desire S and got this update too,
and after it the problem appear on their phones too.
So I think something wrong with new OTA update.
And I also notice the TTS Service, don't work too, it's always
halted.
(I made a factory reset and my friends too, but we have this problem too)
Any idea?
Everybody "got" this bug with OTA?
Bye,
Istvan from Hungary.
Click to expand...
Click to collapse
Try to disable the "Trace keyboard" feature. I did that and it seems that for the last ~18 hours I didn't encountered the unlock bug once.
Trace keyboard...
My "Trace keyboard" was off and the problem also present.
I tried to switch on, it hasn't any effect to the problem.
I hope the HTC will soon cede to this OTA full with bugs...
But as I known them, they not soo fast.....
Since the OTA update my Desire S crashes about once a day, and after it reboots it tells me it has recoverd from an error and asks me if i want to send the report to HTC. Seeing as how it reboots without any problems, and it works perfectly except the crash once a day, i suspect it has something to do with the flashing to 2.3.5.
Should i try a factory reset, or could there be another solution (seeing as how i really want to avoid a factory reset).
Oh and I have not rooted or S-OFF'ed my DS before the OTA update, so it's totally stock (as it has been since I got it)
I was able to fix the bug with Locations not starting up by changing my phone's language to English, then starting Locations, then changing the language back to Finnish again and voilá, it worked. One less problem for me.
I think that the Locations bug is limited to Nordic language versions (or even only to Finnish versions).
Hello
After update i have also the issue with the screen impossible to re-activate by power button after call is ended.
howto reproduce the issue: it happens only when screen is locked by security lock (PIN) and I receive a call. I pick up the call, screen is automatically turned off during call. After the call is finished, I'm unable to get the screen active again by pressing the power button!
Only working workaround is to attach phone to charger or connect to USB. Then the screen is activated and I can unlock it by PIN and working normally...
I need to have security lock enabled to be able to sync corporate email ( this is the security policy enforced by corporate Exchange server).
Ferro
Sent from my HTC Desire S using XDA App
This new OTA update looks more like a beta testing for many users still haven't got it and those who got it are complaining about bugs.
Some are affected by power button bug and others experience difficulties unlocking their phones.
What makes the situation even more strange is HTC not announcing the update.
Sent from my HTC Desire S
hamedunix said:
This new OTA update looks more like a beta testing for many users still haven't got it and those who got it are complaining about bugs.
Some are affected by power button bug and others experience difficulties unlocking their phones.
What makes the situation even more strange is HTC not announcing the update.
Click to expand...
Click to collapse
I'm sure you're right. HTC must have got a whole load of their people committed on new phones, others working on the recent security issues, so updates to our DS must be fairly low-priority. It smacks of the way that Microsoft beta-tested new OSes (perhaps still do) - Deploy many different public beta versions, don't bother actually reading the feedback but just simply measure how many complaints come in on each version. Finally, make official the version that got the fewest complaints.
I wouldn't be surprised if it goes quiet again for a week or so now.
The reply from HTC regarding the power bug:
Thank you very much for your cooperation and please be informed that we will get into this issue and we will try to determine what could cause these problems and what can be the solution. Please be patient with us because the investigation process itself it may take between 2 weeks and 4 weeks.
Have a nice day!
Disappointing
Hello,
After investigating further on my issue about "unable to resume screen by power button after call is finished" I described in my previous post I found it is most probably not related to OTA update but to HW problem...
I found my Proximity sensor is possibly dead. How the phone behaves (regarding screen on/off) during making or pick-up the phone is non standard. I also tried several android apps that are checking all sensors available on the phone and I see activity from all sensors except Proximity .
Talked also with HTC support... I'm going to sent my DS to HTC service center
Wish all getting the OTA update to enjoy it - I will certainly do so after I get my phone is repaired.
cheers
Ferro.
Pressing the power button during call or afterwards should light up the display.
At least that's what happened with the previous software version.
I'm still convinced HTC messed something in the update.
I have the exact same issue.
Has there been any work arounds how to fix this problem.
Mine's is on O2, never been rooted. Just stock.
If all fail looks like I will have to wipe phone and start again
Hi, since 2 months i have been experiencing random crash on my U11+ i tried to reset my phone today and by completing my phone setup i added the option to restore some of my apps, everything was working perfectly until the phone got to homescreen and the app start to downloads, it crashed 3 times in 10 minutes.
Anyone experiencing the same problem?
kuihome21 said:
Hi, since 2 months i have been experiencing random crash on my U11+ i tried to reset my phone today and by completing my phone setup i added the option to restore some of my apps, everything was working perfectly until the phone got to homescreen and the app start to downloads, it crashed 3 times in 10 minutes.
Anyone experiencing the same problem?
Click to expand...
Click to collapse
It started happening to me as well.
However in my case I've managed to (partially/temporary) solve it by going to Boost+ and change from "Optimize" to "Don't optimize" for following apps: Google Play Store, Google Services Framework, Phone, People.
That did it for me for most crashes but Play Store still behaves weird and the only way to prevent Play Store and it's ridiculous crashes is to do in these steps exactly: as soon as you open Play Store > swipe from left > click on Play Protect > and just go back > Play Store won't crash at all.
I haven't tried resetting so I can't tell if that would solve but there are few posts regarding insane crashes related to Play Store and Boost+.
Might be different for you but you might give it a try
cli_junkie said:
It started happening to me as well.
However in my case I've managed to (partially/temporary) solve it by going to Boost+ and change from "Optimize" to "Don't optimize" for following apps: Google Play Store, Google Services Framework, Phone, People.
That did it for me for most crashes but Play Store still behaves weird and the only way to prevent Play Store and it's ridiculous crashes is to do in these steps exactly: as soon as you open Play Store > swipe from left > click on Play Protect > and just go back > Play Store won't crash at all.
I haven't tried resetting so I can't tell if that would solve but there are few posts regarding insane crashes related to Play Store and Boost+.
Might be different for you but you might give it a try
Click to expand...
Click to collapse
Hey thanks for the advice dude, sory for late replying you i was kind of busy and hasnt been using xdav at all. well i tried it but to no avail :/.. the thing has gotten worse. someone else is having the same problem as me. Thinking of getting it to warranty and in the mean time im getting back to my old S8.
kuihome21 said:
Hey thanks for the advice dude, sory for late replying you i was kind of busy and hasnt been using xdav at all. well i tried it but to no avail :/.. the thing has gotten worse. someone else is having the same problem as me. Thinking of getting it to warranty and in the mean time im getting back to my old S8.
Click to expand...
Click to collapse
No worries mate
Sorry to hear that it gotten worse
Most of my issues were caused by Boost+'s aggressive power saving option(optimization?) and going though every app that I think does not need any power saving options I just set it to "Don't optimize". Strangely enough - this did help but it is far from solution.
Yeah, phone does have some serious issues such as what I've recently discovered on my unit is if you have 2 SIM cards inserted* and someone calls you or you call** someone sometimes(very often) it freezes right away. By that I mean screen stops responding completely, ignoring any touch input or vol up/dn, power button or anything at all you just have to wait until it crashes on it's own and pulls it self back together.
On first try or after 2nd or 3rd call, it doesn't even have to be answered it will freeze and will 100% soft-reboot. Before it crashes during the call you can perfectly communicate with person on the other end without any problem but sadly it is timed as it is going to soft-reboot.
(dual sim phone and has issues with it's very own purpose of having 2 SIM cards)
*Inserted and active: it doesn't matter if you switched one SIM card off or another one it still happens (Dual SIM manager settings) Maybe my phone doesn't like that there is 1 UK and 1 HR (Croatian) sim cards together? Maybe has to be both UK or both HR? Can't verify that, sorry. Never had dual sim phone before.
**It does not matter is it SIM1 or SIM2 as it happens on both.
Not sure if it's just my unit or I am doing something wrong that is causing this, couldn't find anything online with this problem.
I can reproduce that issue at any given time but have no idea how to debug this problem sadly.
However in my case I no longer need the 2nd SIM card (HR) and now have microSD card inserted.
To summarize
Phone itself is great, I really love the camera (and DNG pictures) and video recording (60 fps all the time), battery lasts incredibly long way better than anything I had before!
I've completely purged play store as it has no purpose to me and I can live without that, coming from previous incredibly bad phones I am not worried about that.
But because of this serious Dual SIM problem, sadly, I can not and will not recommend this phone to anyone.
Only way is to have patience if HTC is going to release patch for this, but looking though U11+ posts, this might take a while.
Personally I'm not worried, I've rooted and flashed TWRP/CWM on all previous devices I had and in any time I'll just reflash original boot.img and restore stock recovery.img (which took a lot of time to find online) so OTA can work and update when it arrives.
Hey! you could bring it to warranty, and maybe they will replace your unit with a new one, yes i did say that the software on the u11+ is not perfect :/, its been a long long time since the european u11+ got any update the .401 version im still on december 1 security patch thats way too slow for a high end phone, i just read that the u11 life is getting android 9.0 pie in certain part of europe :'( thats not fair.
Well as for my problem i got it solved by bringing my device to an htc shop they took 3 days to analyse and all, at the end they just gave me a new unit. well not as if the old one could be repared.
I did say that the U11+ is an awesome device, excepts for sme little flaws in the system everything is just perfect. i choose this one because the the bigger battery i less powerful cpu compared to the U12+. well i can't wait to have my hands on Htc's new flagship next year
The Pixel 4a is the first phone in 10 years I didn't root because of the hardware check, but nevertheless Google Pay doesn't work for me on this phone. I had no single problem on my OnePlus 6 with Magisk. Is there a known bug? Does anybody know if usb debugging enabled is a problem for Google Pay? It's very frustrating to go back to the plastic card to pay.
Did you unlock bootloader? That'd cause it to fail the check even if not rooted.
fleischbanane said:
The Pixel 4a is the first phone in 10 years I didn't root because of the hardware check, but nevertheless Google Pay doesn't work for me on this phone. I had no single problem on my OnePlus 6 with Magisk. Is there a known bug? Does anybody know if usb debugging enabled is a problem for Google Pay? It's very frustrating to go back to the plastic card to pay.
Click to expand...
Click to collapse
USB debugging enabled kills some streaming services; wouldn't be surprised if Google Pay is sensitive to this
No, I didn't unlock the bootloader. I think this triggers the Google checks.
The only thing I did was enabling the developer options in order to give Tasker and some other apps special permissions.
I have a 4a on Android 10 with developer options enabled. I've used GPay once, and it worked ok for me.
woody1 said:
I have a 4a on Android 10 with developer options enabled. I've used GPay once, and it worked ok for me.
Click to expand...
Click to collapse
Thanks a lot, so I have to check my card. As mentioned before it worked last week on my OnePlus 6, so it's really strange.
Will try another card next time.
Not sure if it helps but sometimes I have run into an issue with using magnet mounts on the back of my phone case with pay terminals.
It's very frustrating. I tried three different cards and looked up the NFC location which is very different to my OnePlus 6. Under the fingerprint scanner instead of in the camera module. I really don't want to factory reset because I already set up all banking apps.
Thank you all for your help.
Edit: I found on Reddit, that there seems to be s a problem with Tasker, so I uninstalled it and also disabled the developer options. Will see if this works for me.
To be clear, is Google Pay telling you your device is ineligible / incompatible etc and refusing to let you set up a card? Or is the issue that it simply doesn't work at a payment terminal?
If doesn't work at the terminal. The app tells me everything is fine. I also tested the NFC chip with a German ID card. The phone can read all information stored in the ID.
Ok. That clarifies things a bit. If Google Pay isn't complaining about device eligibility then that's not what your issue is.
It's still not impossible that it's a hardware problem. Maybe it still works correctly for reading other unpowered devices like an ID card, but doesn't work for being read by payment terminals.
I'm not alone. :highfive:
The process in the video is the exact same I see every time I try it: https://9to5google.com/2020/10/26/some-pixel-5-owners-cant-make-nfc-payments-with-google-pay/
Luckily I didn't try a factory reset. :fingers-crossed:
Google Pay Not working
I have the exact same problem but this also happens on Oneplus Nord and Pixle 4a i have both devices and i get the same error on both devices .
Google pay works on
S10 Android 10
realmme 6 pro
Realme x50 5g
Fossil gen 5 Wear os Watch
pixel 3axl Android 11 beta
Will not work on
Pixel 4a Android 11
Oneplus Nord Android 10
have uninstalled the app and reinstalled
Cleared cache
Cleared storage
Cleared play services
removed account
removed card
re added card
re added account
reset device one plus nord only
none of the above methods worked for me
also i can connect my watch to the phone not working and the app on watch will work for making a contactless payment
the Nfc is working on my phone i have tested it with other NFC device and it works as intended
Called the bank No blocks on my card and it is setup correctly
Called google asked a million times the same question over and over and talking with support at the moment
so sorry i cant solve the issue but just thought id let you know what i have been doing
Also tried on different card machine get the same error all the time
Version 2.119.338332786 solved all my issues!
https://www.apkmirror.com/apk/google-inc/google-pay/google-pay-2-119-338332786-release/
So, every since I have updated my pixel 4a to the August security patch, it starts giving me an issue with my SIM, it seems to not detect my SIM at random points of the day and I sometimes have to restart it multiple times to get it to detect again. After it gets detected, it will work fine for about 12 - 15 hours before the issue comes back again. When the issue occurs, my mobile network option in the settings will get greyed out. (see attachment below)
Went to my carrier and get a new SIM. Still, the issue persists. Even tried an E-SIM and it still doesn't work
I have contacted Google support and they told me to send my device down for repair and inspection however, even after repairing my device, the issue still persists. Factory reset does not fix it as well. Dig thru Reddit and Google forum as well, tons of others are facing the same exact issue after the August update leading me to deduce that this is not a hardware but a software issue with the update.
I saw that there was the September security update patch yesterday and I went to update it, however, the issue is still there
I then proceeded to contact Google support again and they kept telling me to send it for repair even though I already have?
Does anyone have a clue what to do?
Felixxxxx said:
So, every since I have updated my pixel 4a to the August security patch, it starts giving me an issue with my SIM, it seems to not detect my SIM at random points of the day and I sometimes have to restart it multiple times to get it to detect again.
Dig thru Reddit and Google forum as well, tons of others are facing the same exact issue after the August update leading me to deduce that this is not a hardware but a software issue with the update.
Click to expand...
Click to collapse
If others are experiencing the same issue after the update, then that highly suggests the problem was caused by the update.
So, unfortunately, ONLY google can fix it with another patch and you will have to wait until google gets around to fixing it.
I have similar problem though I thought it's caused by android 12 beta so I outped out it and everything was fine for few days. I restated my phone after day or two and the problem of no serivce came back. This time even factory reset didn't help.
I can't manually change preffered network type to 2g/3g and everytime I try to make a phonecall it says i need to turn off aeroplane mode off.
Felixxxxx said:
So, every since I have updated my pixel 4a to the August security patch, it starts giving me an issue with my SIM, it seems to not detect my SIM at random points of the day and I sometimes have to restart it multiple times to get it to detect again. After it gets detected, it will work fine for about 12 - 15 hours before the issue comes back again. When the issue occurs, my mobile network option in the settings will get greyed out. (see attachment below)
Went to my carrier and get a new SIM. Still, the issue persists. Even tried an E-SIM and it still doesn't work
I have contacted Google support and they told me to send my device down for repair and inspection however, even after repairing my device, the issue still persists. Factory reset does not fix it as well. Dig thru Reddit and Google forum as well, tons of others are facing the same exact issue after the August update leading me to deduce that this is not a hardware but a software issue with the update.
I saw that there was the September security update patch yesterday and I went to update it, however, the issue is still there
I then proceeded to contact Google support again and they kept telling me to send it for repair even though I already have?
Does anyone have a clue what to do?
Click to expand...
Click to collapse
Wow, unfortunate for sure. Isn't it possible to roll back to just before the update? Of course google makes the entire firmware available and I believe I've read if you remove the '-w' at the end of the script it doesn't wipe data?
At least if this was possible it would certainly indicate if it was the update or not?
cheers
So my Pixel 4a updated to the October Security Patch this night, and from there on it says "SIM not detected".
But when I go in settings it shows the network name.
I tried switching the SIMs with my Pixel 2 and everything works there, but any SIM I put in my 4a shows "SIM not detected" even though it can detect the network.
Which it probably wouldn't do if the SIM slot were defective, right?
And the timing with the update is too much of a coincidence...
I have similar issue - Pixel 3A, after update with November Security Patch, "No simcard" error appears with mandatory reboot. Tried with different SIM, there was prompt for PIN, verified and then it seems no access to simcard data. Even "emergency call" is no allowed from now. Looks like additional privilidges needed for access SIM card. No clue, how to proceed...