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
Related
I have been a lurker here for a long time. But have needed to register in order to figure out if I have run into a bug...or if I did something wrong.
I registered just now...so I am not allowed to post this in the Dev sections...so please forgive me for putting this in the General Section.
I am not new to rooting or loading roms on android phones. So I don't think this is a result of a mistake or issue with either of those processes.
I have noticed that since loading DasBAMF 1.2 (first version I loaded...so can't speak to earlier versions), my bluetooth voice no longer syncs voice with my car. What is weird is the media sync is working fine...but it just cannot connect to the phone for calls.
BTW...It did work when I was using stock OS.
Thanks,
bump....anyone?
did you try wiping ?
oh yes....
Full wipe-> Install DasBAMF1.0-Logged into Google->let sit for 45 mins->checked all contacts settings and what not to make sure everything was settled->recovery-> no wipe->install DasBAMF 1.2->install apps only via TiBackup->used for 2 days->recovery->no wipe->install DasBAMF 1.3
BTW...had the same issue with 1.2 (but that might have been obvious).
Thanks for the response.
Have you wiped since you installed 1.3? I have had similar problems as you, with other devices, and this one, and usually after several attempts I can remove the device from the BT pair window and repair.
I would try the latter first, then do a cache wipe, dalvic wipe and a factory reset and check.
No issues with BT connectivity in my car or my headset. Version 1.3 actually connects faster than the other ones did for me (including ROMs on my Droid 1). I haven't tested it yet but I will with my next ROM but historically my connections have come back using TiBu so I'll be testing that later.
My TB was working with my car radio and syncing via bluetooth. After performing the "1 click" root, having issues with bluetooth and car. Not sure whats up, still have stock ROM. I see others are having this issue even without root.
I just replied in http://forum.xda-developers.com/showthread.php?t=1018438
for pairing issues with a car, but along the same lines I was able to successfully make a call with no voice/pairing issues running Das BAMF 1.3. I haven't tried the media sync, so I cannot attest for that.
Never got this solved for DasBAMF.
Wiped and restored the virgin OS that only had root and nothing else, then installed 1.2, 1.3, and 1.3.2 ... Bluetooth would not work for voice.
So wiped and installed Liquid ThunderSense...and I am back in business. weird....but hey...at least I am good to go now.
Hi everyone I posted this on my roms page but I thought I would branch out and ask others if they have seen anything like my problem. It seems my phone hates my brother or at least his phone number. Every time he calls me or I call him I get the error process.acore has stopped unexpectedly problem, force close. I tried to clear the phone app but no go. The problem has occurred on two separate roms, fresh installs over a two week period? Of course the phone stops working and I get frustrated. Thought it was a dirty download so I tried Flips newest creation and sure enough after I have it set up enough to do a nandroid make the back up then about the time I make a few phone calls it starts kicking our the error android.process.acore has stopped unexpectedly problem, force close.(just found it was only my brothers phone number) I am on TWRP 2.0 for my current recovery.
Oh thanks everyone for any ideas,
I'm on 1.4 hboot, baseband 0.97.10.0808, PRI 1.24.003, PRL 21083, Android version 2.3.4 & Sense 3.0 currently....boot ready to SVN back to most recent Warm nightly.
Ok now it gets really weird, I just realized it's my brothers phone that causes the issue? What the f?I called many different phone numbers even a Miami area code like his....it has happened on two different fresh installs of two different Roms. I did clear the data on the phone app but should I completely delete his contact and then allow google to sync? It seems I basically already did that with the installs of the different roms? Any ideas WHAT COULD POSSIBLY CAUSE THIS? Very weird.
Thanks again because I have no clue
Charles
Ok so I reprovisioned the phone and still the same problem. It varies as to which phone contact causes the force close issue. Going to try and delete contacts although I doubt it does any good.
Anyone, Buehler, Anyone?
The same thing is happening to me on my 3d and i haven't rooted it yet. I will turn on the phone and everything will crash. I don't think it has to do with the rom but maybe a phone defect. I would say unroot and see if the problem still occurs if it does bring it back to sprint. They have a warranty for stuff like this.
TWRP 2 is really buggy, try flashing through cwm or twrp 1.1.1
Sent from my Transformer Prime TF201 using xda premium
I've been running twrp2.0 since release and I've restored nands, did wipes, etc all has worked fine.
#Root-Hack\Mod*Always_
""Shooter on Deck""
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.
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.
Hi everyone,
Last week, I updated my G3 to Lollipop. Ever since then, I have been unable to recieve app notifications when I am on wifi. When I turn off Wifi and use a regular signal, the notifications work fine. They also work fine when I have my phone in airplane mode, with wifi on. But, when I have wifi and the data signal on, they do not work. Ii have already done a factory reset to my phone once, and it has not resolved the issue. Is this a known bug? If so, is there a fix in place? If anyone knows, I'd appreciate any info, as this is becoming quite frustrating.
Matt
This is the dreaded WiFi Sync bug, It doesn't affect all WiFi spots. It just depends on the router you are connected to. It mainly stems from IPV6 issues. There is a fix in the works for the official OTA or you can root, and apply a fix for it. I believe Jasmine ROM has the fix in it, but I cannot say for sure as I do not run custom ROMS. I stick with stock.
This has only really affected me with GMail syncing with a 3rd party app at home. At work, I have no issues.
So, you can either root, flash the fix (search the forums and you'll find the issue) or you can wait until LG/Verizon release the patch for this, or go back to KK.