I'm writing this to report issues I've had AND to see whether or not I'm the exception or the rule:
1) I am not rooted (waiting patiently for S-off). After installing the OTA last night, I woke up this morning to no alarm. Gentle alarm had an error report on screen. I checked the stock clock app alarm. It was ringing WITH NO SOUND.
2. I called into work to report being late. Our receptionist could not hear me speaking and hung up. I could hear her fine, though.
3. Text messages have been sending sporadically as has 3g reception been sporadic (still no 4g in my area).
4. Attempting to access the settings menu makes the phone freeze.
Last but not least, I have rebooted several times in an attempt to fix these issues. Verizon tech support says, "There are no known issues with the update."
Please respond with specific issues you've had with the OTA to keep the rest of the community informed.
Sent from my ADR6425LVW using xda premium
I lost wifi with it. I am rooted and unlocked though so I am thinking it was a bad flash since I didn't restore the stock recovery image before applying the update. Nandroid back up fixed it for me. I think I will be waiting on a stable rom based on this ota.
after the OTA, I had to reset my skin, and some of the stock messaging app settings.
have made a few calls with no problems, speakerphone too.
Been running the OTA since this a.m. and haven't had any issues. I did have to run it twice for it to actually stick though ..that was odd.
Well if you notice after the update all of what's in your int. sd was deleted and changes were made in a different partition. Other than that it maybe a bad flash? I'm running fine atm.
mines running fine, but i did have to reset my skin back to blue sky...and i think my battery might be worse after the OTA..not too sure yet.
Related
Is there a specific process/service that could be blocked/delted/frozen to stop the OTA from constantly happening? Or is it quite deep system within the Android OS?
I'm currently running the first release of GB OTA, then went ahead did Revolutionary and then flashed SU to get root.
Now its not a big deal when the phone does try to update, it just fails(not sure why it fails, but I just get the "!" and blue android icon). I just normally go in hboot and wipe the cache and good for a few days.
Well now its been really like trying to get the OTA going. Every hour or so it re-downloads it and try to install it. Only 8am, and its tried 3 times since 6am. :/
I really don't feel like loading a custom rom(kinda afraid I might brick it), i'm quite happy on how my phone is setup now. Other then this minor annoyance it never crashes or locks up.
Have you tried freezing
com.smithmicro.dm or HTC DM?
I have so many apps frozen that i can't remember which it was. I also don't use stock home, which freezing some services causes issues with.
Sent from my ADR6400L using Tapatalk
Hi all,
I'm using a GSM Razr XT910 with the CyanogenMod 9 customised ROM by J.Y. Daddy (RAZR-CM9-12.05.17-UNOFFICIAL-GSM-J.Y.Daddy) and I keep receiving duplicate SMS messages. I've changed to "Original timestamp" in SMS settings to see what's going on, and it seems I'm getting the same message up to 9 times.
It happens with multiple contacts, and I'm not sure how to fix it. I'm in the UK on O2 - does anyone have any ideas for how to fix, or has anyone else experienced a similar issue?
I had this issue too.
I live in Australia and have been using J.Y.Daddy's CM9 builds pretty much since he started porting them over to GSM. I tried to narrow the issue down to a few factors and the main causes I suspected were:
1) Different kernel version to your phone's "natural" one. Have you used RSDLite to flash any different fastboot files? Or are you on rooted stock initially?
2) Handcent. I began using this app after making the switch from GOSMS a while back and shortly before the duplicate message problem began. They have actually confirmed that there is some compatibility issues with some Motorola handsets, and this is reflected by Handcent's changelog. Are you by any chance using Handcent?
3) Finally, the last cause I come up with was a network issue which is refusing to send an 'acknowledgement' packet to the provider, essentially meaning the message is never marked as received and therefore, it keeps sending the message in an attempt to correct this.
In my experience, the problem was #3. I was on Optus for a long time (The 'second place' Australian telco), and recently made the switch to Telstra (#1 telco) and the issue has been resolved. If you are on stock kernel and do not use Handcent, then unfortunately I think it may be a network issue.
Don't take my word on this though, I'm not an expert. Just speaking from experience.
Thanks Mr. Ektid, I think in my case it's probably #1. I installed a different 2.3.6 rom over RSD in order to get the Bluetooth working without causing a bootloop, so I guess that must have messed things up. I don't use or have installed any SMS apps other than stock, and I don't think it's a network issue as texts were working fine before installing ICS.
I've rolled back to Arctic for now, seems to have sorted things again. I suppose the way to fix the issue in CM9 would be to RSD a stock UK 2.3.6 rom and then flash CM9 over that - but I'm not sure if that would mean I would still get Bluetooth bootloops, as it seems like a fairly specific 2.3.6 rom is needed for that to work.
Ah well. Back to Gingerbread for a while.
So I posted this on the Paranoid Android thread, and I think that was the wrong place to post since I have no eliminated it as a ROM issue. Here is what has happened:
This is the reason I am posting here: today my text messaging has gone goofy. When I send a text message in the default, stock, PA AOSP app, the message says "sending" under it for a little while, then it says the "failed to send message" with the little red triangle on it. Meanwhile, the recipient has gotten 4 copies of the text. Yes, four. It has happened to literally everyone I have sent texts to today: iPhones, Droids, feature phones. I have clean installed the ROM and GApps 3 times today and it still happens. I wiped my internal and SD card from TWRP (got into a little issue there, had to figure out adb sideload, but we are all good now). Checked the MD5's before I installed. It's still happening. Other people with Verizon in the area that I know don't have this issue. Also, this was my 3rd day since installing the ROM, and it didn't happen the first two days, only today. Bottom line, I have no idea what's going on, and I need some help to fix it.
Update on the texting issue: I called VZW and went through their steps, and they said its almost certainly a device issue, and not a network issue. She said that my phone is having trouble contacting the SMS switch, and so it keeps trying to send the message, but it never hears back so then it reports that it can't be sent. The lady I spoke with did file a ticket for a "Network Technician" to take a look at the issue, but that will probably take at least 72 hours. I really hope this is either an issue with the ROM or with the network, because I really don't want to have to go through the process of unrooting and returning to complete stock to get one of vzw's crappy "like new replacements"
Update 2: Restores some of my backups from previous ROMs, including an AOKP 4.2.2 Milestone and an CleanROM VZW SE and the text messaging is still messed up. That pretty much eliminates the chance that its a PA issue, and it is most definitely either a device issue, or a Verizon Network issue. Cross your fingers that its a network issue so I don't have to go through the mess of returning to stock and all that.
Any possible fixes that you guys can think of?
Indeed its a device problem. I've got the reverse issue! I keep receiving the same copies of one message about 10 to 15 times a day. Due to this, the latest message from the respective recipient delays to the next day! I do have tried third party apps but still it doesn't work out... Need help!??
Sent from my A2 using Tapatalk 2
It's only been a couple days since i updated but so far all has not been smooth like it was with the last ota update.
SMS has been quirky..missed texts and wrong time stamps. May just be the google hangouts app. I will be using stock messaging app until i figure this out.
Also noticed issues with bluetooth and ford sync..albeit an older 2012 version of sync. Audio stutters and sync doesn't recognize the phone unless I manually seek bluetooth devices. Had to delete old phone connection in the sync settings and re-pair the phone to my car. Seems to be normal now.
Haven't noticed lower connection speeds but I haven't really tested 4G much yet.
I haven't s-off or rooted this phone yet. So I didn't think of even doing a factory reset..may not be a bad idea at this point.
Sorry if this is not new info just wondering what general issues people are encountering.
I would suggest doing a factory reset. With Roms it is always recommended when upgrading major versions of Android to do it clean, and I recommend the same with stock software. I've done stock updates and had issues, but after clean wiping everything went back to normal. I'm rooted and soff but using the stock software and it has been running great without any of the issues you are having. Try a factory reset and see what happens.
Sent from my HTC6435LVW using Tapatalk
Hi, my sister's unrooted HTC One on stock 4.4.3 has a phone call issue. She'll call someone but they can't hear her and she can't here them. If this happens, she does a reboot and when she makes a phone call it'll connect. After a certain amount of time the phone call issue will appear again.
Has anyone else experienced this? This also happens on my GF's rooted HTC One running Viper rom.
dragonsamus said:
Hi, my sister's unrooted HTC One on stock 4.4.3 has a phone call issue. She'll call someone but they can't hear her and she can't here them. If this happens, she does a reboot and when she makes a phone call it'll connect. After a certain amount of time the phone call issue will appear again.
Has anyone else experienced this? This also happens on my GF's rooted HTC One running Viper rom.
Click to expand...
Click to collapse
Have your sister copy all of her personal data and files off of the phone and perform a factory reset through Settings. If that doesn't work, then have her download and the run the T-Mobile RUU assuming she is on T-Mobile. Again make sure all of her personal files and data has been removed from the phone.
majmoz said:
Have your sister copy all of her personal data and files off of the phone and perform a factory reset through Settings. If that doesn't work, then have her download and the run the T-Mobile RUU assuming she is on T-Mobile. Again make sure all of her personal files and data has been removed from the phone.
Click to expand...
Click to collapse
Thank you! She is on t-mobile. I will help her with this and report back.
This literally just started happening to me as well. T-Mobile HTC One on ViperROM 7.0.0.
I made a phone call Sunday (12/7) no problem. Now all of a sudden no audio in either direction using the default phone app. But hangouts dialer has no issues.
This just started happening to me as well! When I'm on wifi calling, I'm able to make a phone call without any issues. But 2 times this week when I tried to make a call when I wasn't on wifi, it was a dead call where I couldn't hear the caller and she couldn't hear me.
I have an unrooted t-mobile HTC One.
Any one have any ideas as to what could be the cause of the issue?
EDIT: It appears to be caused by the HTC lock screen on the google play store which was recently updated. Hopefully a fix will be released soon.
jpzsports said:
This just started happening to me as well! When I'm on wifi calling, I'm able to make a phone call without any issues. But 2 times this week when I tried to make a call when I wasn't on wifi, it was a dead call where I couldn't hear the caller and she couldn't hear me.
I have an unrooted t-mobile HTC One.
Any one have any ideas as to what could be the cause of the issue?
EDIT: It appears to be caused by the HTC lock screen on the google play store which was recently updated. Hopefully a fix will be released soon.
Click to expand...
Click to collapse
Where did you hear about this? I'm having the exact same issue. I'm on Viper 7.0.1. Restarting the phone doesn't work but a flashing the rom fixes it again for a little bit. Trying to find the cause of the issue so I can correct it without having to wipe my device again.
Well I ran the new RUU to return my phone to bone stock. Calls work after this no problem. So i started re-installing all my apps via titanium backup and today I get a phone call, same thing no audio either direction. This is on the stock ROM, i never re-installed Viper.
I'm going to do a TWRP back up and do a factory reset and not install any apps to see if the problem comes back.
---------- Post added at 11:42 AM ---------- Previous post was at 11:36 AM ----------
jpzsports said:
EDIT: It appears to be caused by the HTC lock screen on the google play store which was recently updated. Hopefully a fix will be released soon.
Click to expand...
Click to collapse
Just noticed the edit. Can you let us know the source of this info please?
More info here: http://forum.xda-developers.com/htc-one/help/m7-mute-calls-please-help-t2921985/page8
HTC is taking responsibility for it, but I don't think it's clear if it's HTC or Google's fault. Either way, HTC pushed an ota for an Australian carrier that fixes the issue, and the venom guys released a flashable fix a little earlier today for their ROM. As far as stock tmobile users, I have no idea nor have heard of a permanent or even a solid temporary fix that normal users could do, i.e. my wife.
Google hangouts dialer does work. I used it today to call people back once they called me and we couldn't hear each other There are other calling apps, but this one is nice cuz you don't have to sign up for anything, it's just Google which we all obviously use already.
Sent from my HTC One using Tapatalk 2
Just got an update from T-mobile to fix this. OTA