Related
So i wanted to see if im the only one who get some of the bugs below:
1) keyboard(any keyboard) falling animation stops in the middle and disappear instead of going all the way down whic is kind of ugly and make it looks like lagging.
2) and the more crucial is this(photo attached) - contacts names in people section randomly getting blank and the only way to know which contact it is, is to enter the contacts edit and see the name there.
couldn't be more annoying!
any other bugs we should know?
just noticed there is a bug thread already. please move this to there, sorry.
pookipsy said:
So i wanted to see if im the only one who get some of the bugs below:
1) keyboard(any keyboard) falling animation stops in the middle and disappear instead of going all the way down whic is kind of ugly and make it looks like lagging.
2) and the more crucial is this(photo attached) - contacts names in people section randomly getting blank and the only way to know which contact it is, is to enter the contacts edit and see the name there.
couldn't be more annoying!
any other bugs we should know?
just noticed there is a bug thread already. please move this to there, sorry.
Click to expand...
Click to collapse
Em ya wow to that bug. If you have TWRP or CWM try wiping cache and dalvik.
all stock never touched anything.
Since I updated to Jelly Bean I experience very bad reception. Almost all the time "ermerncy calls only". Factory reset doesn't work. Looking at costom roms atm...
I've got a stupid bug (on stock) when you click power off and the screens black u click power button it shows lock screen then powers of again have to do soft reset to make it boot properly again
Sent from my HTC One S using xda premium
pookipsy said:
all stock never touched anything.
Click to expand...
Click to collapse
Try wiping data for the People app.
Darknites said:
Try wiping data for the People app.
Click to expand...
Click to collapse
i just tried, and it didnt help :\
Which rom are you on?
Maps broken
I have a HTC One S locked to Orange/T-Mobile/EE network which is stock ROM, haven't had the need to mess around with it just yet. It received the OTA update to JellyBean 4.1 on Christmas Day, which installed fine without any problems.
Now I find that regardless of what I do, the maps and navigation crashes within a couple of minutes of use. This part is annoying since it seems to work and then anywhere between 1 minute and 5 minutes it simply stops with a force close message. I did a factory reset to see if this would clear the problem, but it hasn't.
The details of my phone are:
Android Version 4.1.1
HTC Sense Version 4+
Software Number 3.16.401.8
HTC SDK API Level 4.63
Kernel Version 3.4.10
Build Number 3.16.401.8
Maps Version 6.14.2
Would be interested to hear from anyone else who has this problem, or more so from anyone who has it and managed to cure it. Else I will have to look at downloading an alternative ROM, one which has working maps!
There is a thread regarding the google map issue already.
I often have loss signal...any idea?
I've seen a topic already.. but the keyboard, especially in WhatsApp is so horribly slow on JB.. not just the One S, Galaxies etc. have it too.
I'm definitely having signal issues. Anyone else's WiFi taking a long time to automatically connect? On ICS wifi used to connect as soon as the phone was unlocked but now I'm waiting up to a whole minute for it to connect!
no problems with wifi here.
i already said im using all stock never touched device.
very weird
Maps
Goatshocker said:
There is a thread regarding the google map issue already.
Click to expand...
Click to collapse
I searched the HTC One S forums for maps crashing and found one which is to do with Cyangenmod ROM as opposed to the stock ROM. I've posted it in here simply because it only started after the JB 4.1.1 update was completed over Xmas. (If I search again for maps crashing, I now get two which is the original thread and this one.)
If you can point me to the thread which deals with this problem, then I would appreciate it greatly, as it is really getting on my nerves. More so since I've removed all updates for Google Maps, they're now back to the stock JB version, and it still crashes.
Cheers
ok, so i just backed up my contacts to my sim card and deleted from phone and google account than i imported from sim and re synced and now the people bug is gone.
The notification badge on my stock Messaging app icon is incorrectly showing 1 unread message.
I have a totally stock Droid RAZR MAXX HD running 4.4.2. My stock messaging app is version 4.4.2-10. SMS is set to "Messaging" (not "Hangouts"). All settings are default. Verizon Wireless is my service provider.
From my own troubleshooting, I have concluded that the problem is probably KitKat-related since stopping, disabling, and clearing (data, cache, and defaults) the stock messaging app has no effect. Also, this problem started after my OTA upgrade to KitKat (never had it before). Further, after completely disabling the stock messaging app, I alternatively installed GO SMS Pro, chomp SMS, and Verizon Messages and experienced the exact same problem with each.
Any ideas about how to fix this problem, without FDR'ing or rooting the phone, would be greatly appreciated.
clear dalvik?
you try clearing dalvik cache?
Great suggestion, but how do I perform it? Can you direct me to instructions on how to clear the Dalvik cache on a stock RAZR MAXX HD running KitKat? I can't find any that don't require a rooted phone. Thx much.
PW_Irvine said:
Great suggestion, but how do I perform it? Can you direct me to instructions on how to clear the Dalvik cache on a stock RAZR MAXX HD running KitKat? I can't find any that don't require a rooted phone. Thx much.
Click to expand...
Click to collapse
i never have stock recovery on, so i could be wrong, but i dont think you can do that in stock recovery.
which means you would have to put on a custom one and root, which i think you said you didnt want to do.
it is somewhat common to have random issues like this on a major software upgrade, especially one that jumped so many other builds.
i know you really dont want to do it, but clearing the corrupted data is really the best course of action, and it may be the only one honestly.
and if you are going to go that far, it is really best to just re-flash the phone encase something in the system is corrupt. just no point in going 1/2 way just to find out you still have the issue later.
sorry thats not the answer you were looking for, but sometimes it is not avoidable.
bweN diorD said:
i never have stock recovery on, so i could be wrong, but i dont think you can do that in stock recovery.
which means you would have to put on a custom one and root, which i think you said you didnt want to do.
it is somewhat common to have random issues like this on a major software upgrade, especially one that jumped so many other builds.
i know you really dont want to do it, but clearing the corrupted data is really the best course of action, and it may be the only one honestly.
and if you are going to go that far, it is really best to just re-flash the phone encase something in the system is corrupt. just no point in going 1/2 way just to find out you still have the issue later.
sorry thats not the answer you were looking for, but sometimes it is not avoidable.
Click to expand...
Click to collapse
Have the same problem - I find that if I delete a recent MMS message sent from me, then it goes back to normal.
PW_Irvine said:
Great suggestion, but how do I perform it? Can you direct me to instructions on how to clear the Dalvik cache on a stock RAZR MAXX HD running KitKat? I can't find any that don't require a rooted phone. Thx much.
Click to expand...
Click to collapse
baldbob said:
Have the same problem - I find that if I delete a recent MMS message sent from me, then it goes back to normal.
Click to expand...
Click to collapse
nice suggestion :good: i have never heard of that.
thanks
yeah dont think its possible on a phone that isnt rooted or has a custom recovery, whats the reason you dont want to to root?
Unfortunately, deleting all SMS and MMS messages did not solve the problem either, so I just FDR'ed the phone. Problem is gone on reboot of course, but so is 13 months worth of app configuration. I would root the phone this time except that the screen is also acting up on me and the phone still has 4 months left on the Costco warranty that I got (for free) with the phone. Wouldn't it be great if Android "L" allowed you to back up app settings along with apps without the need to root the phone first! Thx to all.
PW_Irvine said:
Unfortunately, deleting all SMS and MMS messages did not solve the problem either, so I just FDR'ed the phone. Problem is gone on reboot of course, but so is 13 months worth of app configuration. I would root the phone this time except that the screen is also acting up on me and the phone still has 4 months left on the Costco warranty that I got (for free) with the phone. Wouldn't it be great if Android "L" allowed you to back up app settings along with apps without the need to root the phone first! Thx to all.
Click to expand...
Click to collapse
Follow-up: same problem occurred following FDR. It is related to MMS messaging and it is solved by removing all MMS messages from phone. I did not have this problem with JB. It showed up after OTA upgrade to KK. Too bad for those who like to keep their MMS messages.
Okay, guys, here's the problem. I have been pulling my hair out for days over this. On any Lollipop ROM I install, no matter what combination of gapps and AOSP ROM I install on my OPO, after completely and totally formatting caches, system, data, and /data/media, the problem persists:
Always after logging into an account, but not always the same one, I start to get an error "android.process.acore has stopped." It happens every few seconds and renders the device unusable. I have tried every fix I could find online, including wiping contacts storage data, contacts data, etc. I have formatted my phone several times, and each time the problem comes back. It only stops when I disable Contacts Storage in settings, which then in turn disables all contacts functionality.
This is getting totally ridiculous, and the only thing I can think of is that the AOSP version of contactsprovider.apk is totally corrupt. Any ideas?
I have the same problem... Did you succeed in resolving it?
flolep said:
I have the same problem... Did you succeed in resolving it?
Click to expand...
Click to collapse
Somewhat. The issue manifests itself when Facebook is synced with your contacts, and you use Facebook OAuth to sign into another app. For whatever reason, this causes the contacts app to go nuts, and the only way to fix it once it happens is to get rid of the Facebook app. It's a bug that is quite beyond me to fix. There is a modded Facebook apk floating around somewhere, that has had permissions modded so it's not allowed to use your contacts or register as an account in your phone. That works. It also works if when you install a new ROM, you sign into any apps that use your Facebook login before you install the Facebook app, that way you log into them with the browser and they never talk to the contacts app. Once you have installed the Facebook app, DO NOT EVER click "Sign in with Facebook" in any app on your phone, or you're screwed again.
That's pretty much what I've come up with thus far. Hope that helps.
EDIT: Here's the link to the thread with the modded Facebook apk: http://forum.xda-developers.com/showthread.php?t=2333637
I have the same issue on all CM12 based roms. It seems to happen for users with many contacts (hundreds). Uninstalling facebook seems to fix the problem for me. I have no such problems on my Nexus 5 with the same setup and facebook installed, so I wonder if it's not something specific to the bacon CM12 code.
prometheus1010 said:
I have the same issue on all CM12 based roms. It seems to happen for users with many contacts (hundreds). Uninstalling facebook seems to fix the problem for me. I have no such problems on my Nexus 5 with the same setup and facebook installed, so I wonder if it's not something specific to the bacon CM12 code.
Click to expand...
Click to collapse
It happens for other phones users... See here : https://productforums.google.com/forum/m/#!msg/nexus/Ip-hdFEQccY/OSFCz4Qj59oJ
Thanks for your partial solution @jkotzker... For me it's a no go because I am a big facebook user and I can install app with Facebook account linked at anytime... It's really really annoying to not log with Facebook account if the Facebook app is installed I don't know what to do... I tried everything like you.
I've recently been getting the same issue but mine says "unfortunately the process com.android.phone has stopped" everything was fine had this phone for about a month was on a lollipop ROM and that just randomly popped up. At first I thought it was the ROM so I switch to another lollipop ROM and got the same issue. So I went back to the latest ota kk ROM and til now I'm still getting the pop up. What's going on here? Please help
marcviado said:
I've recently been getting the same issue but mine says "unfortunately the process com.android.phone has stopped" everything was fine had this phone for about a month was on a lollipop ROM and that just randomly popped up. At first I thought it was the ROM so I switch to another lollipop ROM and got the same issue. So I went back to the latest ota kk ROM and til now I'm still getting the pop up. What's going on here? Please help
Click to expand...
Click to collapse
Oh yeah I've been trying to figure this out since cm12 unofficially came out for the note 4. Like all of you said it's fine for a while or sometimes it's messed up right away. I've had it work for two or three days then out of nowhere just have the error pop-up and never go away. Disabling google contacts storage also got rid of the error for me but of course I can't have the phone without google contacts and sync. This last time it happened just by downloading and signing into Dropbox, which isn't related to Facebook at all. This is belong frustrating because nobody seems to have a fix and it's the only thing stopping me from using cm 12. Is there any Dev that can help or work on this with a logcat?
Sent from my SM-N910T using XDA Free mobile app
pablo1215 said:
Oh yeah I've been trying to figure this out since cm12 unofficially came out for the note 4. Like all of you said it's fine for a while or sometimes it's messed up right away. I've had it work for two or three days then out of nowhere just have the error pop-up and never go away. Disabling google contacts storage also got rid of the error for me but of course I can't have the phone without google contacts and sync. This last time it happened just by downloading and signing into Dropbox, which isn't related to Facebook at all. This is belong frustrating because nobody seems to have a fix and it's the only thing stopping me from using cm 12. Is there any Dev that can help or work on this with a logcat?
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
I didn't find one...
I talked about this problem in xda temasek rom thread and ak kernel thread without success. I even sent a message on official cyanogenmod website, with last crash and logcat attached. No success. The problem happened in 2012 too... And since then, Google didn't have a solution for it.
It seems that Google is finally aware about this problem and the correction could arrive in "a future version"... Well. I want it now... Indeed, there seems to be only to increase the buffer transaction between applications and contact storage from 1MB to 2MB for example, to have it corrected. But no dev wants to do it because the problem cannot be reproduced! And it's rare! But we have it! It's incredible to have it back after a full wipe... And happening randomly, just after a random sync between application and Android system...
Any more updates on this issue/ anything else we can do to get this resolved? Even my partial, temporary solutions have stopped working, and I am getting really frustrated.
Glad to see I'm not the only one here with this issue. Took different search terms to eventually land me here since this such an old and somewhat common issue. Nonetheless... Same problem. OnePlus One running Temasek CM12. Disabling contacts storage.... Blah blah blah. Its rather disappointing there's no actual solution instead of a workaround. But, I'm finally happy to know its Facebook. An app I rarely use but do need unfortunately.
Edit: wondering if anyone has had any luck fastboot flashing the factory image? I know it's a pain in the ass to have to back up all your files, etc off the device so I'd like to know if anyone has had success or even tried this. Cuz, I really won't feel satisfied until I've resorted to this last measure if there's the possibility of eradicating the problem.
t3chn0s1s said:
Glad to see I'm not the only one here with this issue. Took different search terms to eventually land me here since this such an old and somewhat common issue. Nonetheless... Same problem. OnePlus One running Temasek CM12. Disabling contacts storage.... Blah blah blah. Its rather disappointing there's no actual solution instead of a workaround. But, I'm finally happy to know its Facebook. An app I rarely use but do need unfortunately.
Edit: wondering if anyone has had any luck fastboot flashing the factory image? I know it's a pain in the ass to have to back up all your files, etc off the device so I'd like to know if anyone has had success or even tried this. Cuz, I really won't feel satisfied until I've resorted to this last measure if there's the possibility of eradicating the problem.
Click to expand...
Click to collapse
I initially had this problem when I switched to lollipop, not sure how it fixed itself but I'm guessing it's the contacts sync like you posted here; only the first time I accidentally synced Fb contacts, and due to the massive number of friends on it, it crashed. But you can disable any sort of sync services on Fb and continue using the app for everything else, I've had no issues since.
Do you mean luck with fixing this issue after flashing the factory image or only returning to stock? Because I've had no issues returning to stock from lollipop by flashing the factory images through fastboot.
Aditya Srinidhi said:
I initially had this problem when I switched to lollipop, not sure how it fixed itself but I'm guessing it's the contacts sync like you posted here; only the first time I accidentally synced Fb contacts, and due to the massive number of friends on it, it crashed. But you can disable any sort of sync services on Fb and continue using the app for everything else, I've had no issues since.
Do you mean luck with fixing this issue after flashing the factory image or only returning to stock? Because I've had no issues returning to stock from lollipop by flashing the factory images through fastboot.
Click to expand...
Click to collapse
I meant with flashing the factory image via fastboot to stop the frustratingly obnoxious pop ups of the process stopping (w/o uninstalling FB). You answered my question.
So, get this... Resolved the error by uninstalling Facebook. Today I picked up a Moto 360 and you HAVE to install Motorola Connect to really personalize the device... Once I allowed it to see my Google+ account info the android.process.acore started again. I'm SO annoyed. Gonna try a factory reset again and see if that helps. The only way to stop it is to uninstall Motorola Connect and that really sucks cuz I want to (of course) mess with my watch. I know nothing of Android Wear yet or how to root, etc the 360 so.... Here I go. Boldly. Lol
I'm just curious why I haven't seen more people having this issue. It's been plaguing me now for almost 2 weeks. I'm ready to throw my Bamboo OPO out the effing window. WTF.
t3chn0s1s said:
I meant with flashing the factory image via fastboot to stop the frustratingly obnoxious pop ups of the process stopping (w/o uninstalling FB). You answered my question.
So, get this... Resolved the error by uninstalling Facebook. Today I picked up a Moto 360 and you HAVE to install Motorola Connect to really personalize the device... Once I allowed it to see my Google+ account info the android.process.acore started again. I'm SO annoyed. Gonna try a factory reset again and see if that helps. The only way to stop it is to uninstall Motorola Connect and that really sucks cuz I want to (of course) mess with my watch. I know nothing of Android Wear yet or how to root, etc the 360 so.... Here I go. Boldly. Lol
I'm just curious why I haven't seen more people having this issue. It's been plaguing me now for almost 2 weeks. I'm ready to throw my Bamboo OPO out the effing window. WTF.
Click to expand...
Click to collapse
It's mostly not because of lollipop, but might be the app itself, I read a few others having this problem on other forums with HTC, the solution they found was to clear data on contacts storage. Give that a try and see if it works, if not I'd suggest going back to Stock or probably the new OxygenOS which is supposed to be out by now. Check out @timmaaa index thread in the general section, it has all the necessary stock images you need. Report back and let us know if it fixed the issue for you
Aditya Srinidhi said:
It's mostly not because of lollipop, but might be the app itself, I read a few others having this problem on other forums with HTC, the solution they found was to clear data on contacts storage. Give that a try and see if it works, if not I'd suggest going back to Stock or probably the new OxygenOS which is supposed to be out by now. Check out @timmaaa index thread in the general section, it has all the necessary stock images you need. Report back and let us know if it fixed the issue for you
Click to expand...
Click to collapse
Yea, I tried clearing contacts storage numerous times to no avail. I can live without the app... At first I thought it was a requirement to change watch faces... But, I do have a backup of stock, rooted but I can't go back to KK after being so used to LP. I'm def going to jump on Oxygen just to try it out but I'm guessing I'll end up running stock CM12s. I can't wait. I'd much rather have a stock (w/root of course) or mostly stock device that actually works completely.
t3chn0s1s said:
Yea, I tried clearing contacts storage numerous times to no avail. I can live without the app... At first I thought it was a requirement to change watch faces... But, I do have a backup of stock, rooted but I can't go back to KK after being so used to LP. I'm def going to jump on Oxygen just to try it out but I'm guessing I'll end up running stock CM12s. I can't wait. I'd much rather have a stock (w/root of course) or mostly stock device that actually works completely.
Click to expand...
Click to collapse
The bug has been corrected by Google themselves with Android 5.1. Finally!.. So, like me, just try omni 5.1 or last cm12.1 unofficial and the error has gone! So good to use my phone.... Hmmm... How to say... Normally... Lol.
flolep said:
The bug has been corrected by Google themselves with Android 5.1. Finally!.. So, like me, just try omni 5.1 or last cm12.1 unofficial and the error has gone! So good to use my phone.... Hmmm... How to say... Normally... Lol.
Click to expand...
Click to collapse
Very nice. Glad to hear this... Xposed isn't compatible with 5.1 yet, right?
Two things to try…
Go into settings/apps , press the menu button and select "reset app preferences". Reboot
You Can also try entering the following in your commands:
Su (enter)
Killall rild (enter)
reboot
Should have read the entire post, glad that has been fixed by google, I experienced the same thing and it's a huge pain in the butt.
t3chn0s1s said:
Very nice. Glad to hear this... Xposed isn't compatible with 5.1 yet, right?
Click to expand...
Click to collapse
No. Not yet. But. Well. CM12 is already good functionality wise. And with this bug disappeared it's really a happiness.
---------- Post added at 12:42 AM ---------- Previous post was at 12:39 AM ----------
tmjm28 said:
Two things to try…
Go into settings/apps , press the menu button and select "reset app preferences". Reboot
You Can also try entering the following in your commands:
Su (enter)
Killall rild (enter)
reboot
Should have read the entire post, glad that has been fixed by google, I experienced the same thing and it's a huge pain in the butt.
Click to expand...
Click to collapse
Yeah, yeah. Already tried... Lol. I think I tried every single advice given in all the Android forums of the world on this bug lol. Well. Google finally heard us. +++
tmjm28 said:
Two things to try…
Go into settings/apps , press the menu button and select "reset app preferences". Reboot
You Can also try entering the following in your commands:
Su (enter)
Killall rild (enter)
reboot
Should have read the entire post, glad that has been fixed by google, I experienced the same thing and it's a huge pain in the butt.
Click to expand...
Click to collapse
Neither worked but thanks for the suggestion. I did find a Facebook work around. Found the Lite Version via a Google search (since its technically not available in the US) , installed it and it works fine. No android.process.acore FC's or repeated pop ups.
Update: This problem reared its ugly head again on CM12 and I ended up having to uninstall Twitter this time. So, now I'm on CM12s and as soon as I logged into my other Google account user Boxers email app I got the android.process.acore crash again. Uninstalling that app immediately stopped it. God I can't wait for 12.1 for our OPOs. This problem is absolutely ridiculous. I can't take this anymore. I really can't use ANY social media apps unless its like Tinfoil for FB or Twitter. I don't have any connected accounts except Google & Cyanogen.. Which I truly can live without but... Just for the hell of it.... Knowing I have a backup and I'm about to clean flash the latest stock build I tried to add Waze and it caused the crash all over again. Uninstalling Waze didn't help. I shouldn't have to deal with this. Only way to stop it is to disable contacts storage. Once it begins it doesn't stop. Effing Google with their half baked crap.
During the new phone setup in Lollipop, after flashed new rom, there is an option to restore old settings. Mine said that the last setting it back up is 27 days old. In the last few weeks i've flashed various roms and have setup my device as "new". For some reason it is not updating and backup my current settings and apps.
The 27 days backup settings have apps and settings that i no longer want to use. I like flashing new roms so it be nice to have settings and app back up current. I have tried various things to try to get my phone to update the settings with google but it is not working. Is there a way to force the phone to back up my current setting to google?
Thanks.
EDIT: If the back up is working for you, can you guy let us know so we have more info to troubleshoot the problem
sumasage said:
During the new phone setup in Lollipop, after flashed new rom, there is an option to restore old settings. Mine said that the last setting it back up is 27 days old. In the last few weeks i've flashed various roms and have setup my device as "new". For some reason it is not updating and backup my current settings and apps.
The 27 days backup settings have apps and settings that i no longer want to use. I like flashing new roms so it be nice to have settings and app back up current. I have tried various things to try to get my phone to update the settings with google but it is not working. Is there a way to force the phone to back up my current setting to google?
Thanks.
Click to expand...
Click to collapse
I have this issue as well. The limit seems to be 10 devices. If anyone has any solution, it would be much appreciated.
Koopa777 said:
I have this issue as well. The limit seems to be 10 devices. If anyone has any solution, it would be much appreciated.
Click to expand...
Click to collapse
I dont think this would be relate to the 10 devices limit. Wouldnt make sense if that is the case.
sumasage said:
I dont think this would be relate to the 10 devices limit. Wouldnt make sense if that is the case.
Click to expand...
Click to collapse
It doesn't work for a lot of people, the reason is unknown at this point.
Lethargy said:
It doesn't work for a lot of people, the reason is unknown at this point.
Click to expand...
Click to collapse
Oh i didnt now this. Was there a discussion on this on the forum somewhere? I searched before posting and didnt come up with anything. Would be good to know for sure so i can stop searching for a solution.
sumasage said:
Oh i didnt now this. Was there a discussion on this on the forum somewhere? I searched before posting and didnt come up with anything. Would be good to know for sure so i can stop searching for a solution.
Click to expand...
Click to collapse
No, but a couple others have had the exact same problem.
I've been having the exact same issue.
I just went into the settings/backup option and clicked to turn off auto backups. It says it will also delete all backups on the servers. Hopefully next clean flash on set up it will show no backups and then I can turn it back on and thing will work from there.
AndrasLOHF said:
I just went into the settings/backup option and clicked to turn off auto backups. It says it will also delete all backups on the servers. Hopefully next clean flash on set up it will show no backups and then I can turn it back on and thing will work from there.
Click to expand...
Click to collapse
Let us know how it goes.....
Did a clean flash this morning and my old backups were still there even though the pop up said they world be deleted. Instead of setting up as new I used the last backup from 28 days ago. Maybe the next clean flash it will update the data.
This is very frustrating.
Same here is there a way to Fix it
Sent from my Nexus 5 using XDA Premium HD app
Yes, and this problem isn't Nexus 5 specific! What the hell is Google doing there? We need this feature. On my opinion, they can delete the old ones, so there is space for the latest. Oh well, Google....
Just did another clean flash after choosing an older backup to continue from. It did not work and did not backup any of my old settings.
I guess Google thinks we should only have 10 backups for infinity and after that we're screwed? Maybe they hope we will setup new accounts? I know this will only really affect tech enthusiasts but come on man.
I tested flashed as well. Turned off the back up option for a few days and flashed stocked 5.0 and setup new device., run for a few days, and flashed CM12, still no new back up choice.
When you guy select the backup to restore, how many choices do you have? I only have one and it is about 34 days old. I dont think google would limit it to 10, maybe they just turn off that feature for now???
Hopefully other people can chime in as well. Let us know if the back up is working for you.
I have only ten choices to choose from.
I've been searching for a fix for a week or two now and can't find anything that works. I can't even find good contact info to directly email Google and get the old backups erased.
I'm on an AOSP Lollipop rom on my Galaxy S5, and having same problem (still!)...
This really sux when doing a fresh install every couple of days...
Any news on this?
How can we fix this???
Weird. I just made a new install. And for the first time in a month I could choose a device from today! Yay!
Sendt fra min klte med Tapatalk
You could always chose to setup as a new device, just click on the drop down during install and select new device instead of an older back up.
I gave up on finding a fix. My theory is that this is new to lollipop and maybe Google turn off the feature or something. Probably due to bug. I just shelled out money for titanium back up.
Sent from my Nexus 5 using Tapatalk
AndrasLOHF said:
I have only ten choices to choose from.
I've been searching for a fix for a week or two now and can't find anything that works. I can't even find good contact info to directly email Google and get the old backups erased.
Click to expand...
Click to collapse
Have you tried removing the phone from googles security page? That should reset everything. Disclaimer, I am not having this problem and have not tried tried my tip myself.
Firstly I want to apologize if there's a thread on this. I tried searching and didn't find anything. Google fails me as well.
For a few months now, Chrome has been driving me insane on my stock nordic Z3 (5.0.2 with the .690 firmware). I also have the most recent version of Chrome installed.
Every single time I open the app, it works for about 2 seconds, then completely freezes for around 15 seconds after which a message pops up stating "Chrome is not responding. Would you like to close it?" If I press "OK", it obviously closes the app and the problem appears again when I restart it. If I choose "wait", Chrome works just fine until the next time I open it. EDIT: The freezing problem started happening three times in a row a few days ago.
This happens every single time I open the app, whether launching it or opening it from the recent apps menu.
I'm pretty certain the problem has been around since the v39 build of Chrome, as 38 worked just fine. I have tried everything I can think of to fix it. Uninstalled updates and re-updated it, updating to lollipo didn't help, I also did a completely fresh install today (repairing via Sony Bridge for Mac) and it didn't help either. And apparently I can't go back to v38 anymore since lollipop doesn't seem to support it.
I would really want to use Chrome, as I've gotten used to it and enjoyed it quite a lot. I'd really appreciate the help.
Try clearing the data in settings - apps - chrome
gregbradley said:
Try clearing the data in settings - apps - chrome
Click to expand...
Click to collapse
I have done this too. Also, the problem persists even with completely fresh installs of Chrome.
Remove your google account, restart the phone and restore your google account
gregbradley said:
Remove your google account, restart the phone and restore your google account
Click to expand...
Click to collapse
Tried it, sad to say it didn't work either. Interestingly it now does the same 15 second freeze, but without the error message in the end. Curious indeed.
EDIT: Got the error message again.
Does this happen on Wifi or on data?
If on wifi is always the same router?
gregbradley said:
Does this happen on Wifi or on data?
If on wifi is always the same router?
Click to expand...
Click to collapse
I Use data 90% of the time, and various routers when on wifi. The problem occurs in all circumstances.
Are you rooted? Unlocked bootloader?
You say you are on the Nordic version of .690, is that the original region for the device you bought and the area you reside in?
Can you revert back to KK by flashing a FTF for your device and region and try V38 again to see if that works still.
gregbradley said:
Are you rooted? Unlocked bootloader?
You say you are on the Nordic version of .690, is that the original region for the device you bought and the area you reside in?
Can you revert back to KK by flashing a FTF for your device and region and try V38 again to see if that works still.
Click to expand...
Click to collapse
I have a completely untouched device. So no root, locked bootloader and it's always been that way. Thus Nordic is the original region of my device.
I'd rather not flash back to kitkat, but I can tell you that I tried reverting back to v38 before updating to lollipop and it worked normally without the freezing issue.
This is my version of chrome on Lollipop. Can you update to this? I am also not rooted so you should be able to update to this
gregbradley said:
This is my version of chrome on Lollipop. Can you update to this? I am also not rooted so you should be able to update to this
Click to expand...
Click to collapse
I have the same version of chrome as you. The problem has persisted during every single update after v38.
ok without logs I can go no further with this. Is there any chance you can pull some logs off your device?
gregbradley said:
ok without logs I can go no further with this. Is there any chance you can pull some logs off your device?
Click to expand...
Click to collapse
How do I do that?
install a logCat app from the playstore
gregbradley said:
install a logCat app from the playstore
Click to expand...
Click to collapse
Does this require root? One of the apps I tried is requiring it and the other one isn't doing much either. Should I be doing something to make it work?
isshoni said:
I would really want to use Chrome, as I've gotten used to it and enjoyed it quite a lot. I'd really appreciate the help.
Click to expand...
Click to collapse
Maybe try the beta version of chrome in case it's a bug which has been fixed but not yet rolled out to chrome. Perhaps try this first as it'll be quicker!
Perhaps it's some data associated with chrome that's getting pulled down after each restore. Perhaps you can try, on a desktop pc, backing up your bookmarks and then deleting them, and clearing chrome's data on your phone, then trying again? And if that doesn't work try getting rid of extensions (not that I think they should be pulling them down as chrome for android doesn't yet support them, although I'm sure I read years ago that one day they would). And anything else associated with your chrome account.
Another one, perhaps quicker (not sure) would be to see if you can associate your phone with a new google account with no previous chrome use and see if it goes wrong with that one. It would help to rule out account-related problems.
Another possibility is that it's not chrome causing the problem but something it relies on; google play services, for example. Perhaps clear data on any apps chrome could conceivably use.
I'm happy to report that my problem is now solved, though still a giant mystery.
My upper speaker broke and I had to get it replace under warranty. I got insanely lucky as they replaced both front and backside glass pieces, the frame, the screen module itself and of course the speakers. So I've now got a brand-new looking phone So happy.
Anyway, I complained about the software being a mess so they also did a complete reinstall and after that Chrome works absolutely perfectly. As magically does everything else too. Not yet a sign of lollipop's previous lagging and rebooting.
It still bugs me, however, that why would Chrome suddenly start having this unreasonable issue. I had tried everything suggested in this thread and nothing worked. My own clean install didn't work. I'm really quite bothered by this.