google restoring apps - Samsung Infuse 4G

Most times when I load a cm7 or above ROM, all my apps get restored as soon as I log into the play store... now suddenly it isn't. Is there something I'm not doing?

For me it sometimes randomly happens, or maybe it has to do with it not connecting correctly to google because of poor connection or something.
Sent from my sweet & buttery Infuse

I don't think its poor connection, I'm on my home WiFi. When it works, it works great. All the apps, WiFi keys, and Bluetooth keys as well... when it don't, it REALLY dont!

I've noticed it too, seems to be rom specific, some roms do it, some don't. when I go thru the setup after flashing a rom, I have the option to restore apps, and another option to back up this phone with google. there have been a few roms where I only had the option to backup the phone to google, no option to restore apps from google. I don't remember which roms, should have made a list.

I'm with you, but the last two cm10 roms I've used, both had the backup & restore options, but did nothing once installed. I can flash Scott's cm10, not paranoid, the other one, and it will load allthe apps I had minutes before flashing. Cm7 does the same thing, but others just leave me high and dry only restoring bookmarks.

Related

OTA 605.19, rooted, app defaults

I'd been running rooted (Revolutionary) with the Verizon/HTC stock ROM (605.9) for awhile and fairly happy. Then I received the OTA push attempt about 2 weeks ago for 605.19... so I opted to defer the push for 2 weeks (June 1) so I could do some research and decide what best to do.
That's when the following problems began... I noticed right after the OTA request... that anytime I restart or reboot the Tbolt many of my core app defaults now go away:
GO Launcher... requires to re selected
Power widget... will not reload (but GO Calender widget is fine?)
Facebook... contacts sync have to be reset (but Google syncs are fine?)
Swype keyboard... must be re selected
Even though I could/can manually fix these disconnects, I decided to take the opportunity to try some other ROMS to see if that would correct the problem. Long story short... I have basically tried 4 different ROMS including 2 different stock ROM (650.19) variants. I am now currently running iKReaM.605.19.NOSeNSe.ROM.v1.0.RLS-R3Ds
which is a nice running ROM.
BBUTTT... with every clean and wipe and reflash, the above "default" disconnects occur? I have tried to search several sites for anyone experiencing similar problems with no success... I know this can't be a ROM issue because it occurs no matter what ROM I use.
Misc info: Several ($paid$) rooted apps that I use are... TiBackup, ADfree, Root Explorer, Superuser (DDChain), No Frills CPU, ROM Mgr... all of which seem to be working together just fine.
Thanks for reading and any thoughts would be appreciated.
I'm beginning to narrow this down to self-affliction... perhaps via something I've done in ROM manager and I keep restoring the problem (???). I deleted all backup data and have reflashed iKReam. One by one I'm adding apps back and have had no app "default" disconnects as of yet. Also I'm not going to reload GO launcher... since the default iKReam launcher (LauncherPro +) is working/reloading just fine and I don't want to chance it.
App Defaults
Sometimes weird things happen like this for the oddest of reasons.
Try running fix permissions in ROM manager.
If it doesn't work...
Did you also clear the dalvik cache when you flashed over to your new ROM?
Did you restore data only from your pervious ROM onto your new one?
Always make a backup before doing anything different, just in case.
If none of this works, I really don't know what to tell you man.
Hopefully this will bump your thread and someone will be able to help you out a little bit more.

Random Reboot+FC's

ISSUE RESOLVED: DISABLE OC DAEMON SCRIPTS AND DON'T RESTORE DATA, WHETHER FROM TITANIUM OR IN APP FUNCTIONS.
I haven't been able to find anyone fix on the web, so I'm taking it to XDA
So far I've gotten these issues on these ROMs, stock.
-Core Droid
-Runny Xtreme Surprise
-RcMix
Certain apps FC when they try to access the web. Off the top of my head I know Dolphin Browser HD and Friendcaster for Facebook don't work. They don't immediately force close when I open them, they FC when they try to access the internet. Only when I try to load something on Dolphin or Friendcaster does it FC.
And I get random reboots. No idea why, although I seem to only get them when the screen is on but I'm not doing anything. E.G. if I leave my screen on it'll just start rebooting.
I'm not sure what's wrong- the first two times I had it on Runny Xtreme Surprise and RcMix was with heavy modifications. I ended up reflashing and not modifying or installing any apps (Except for Dolphin to test). Still had the problem.
I don't have this issue with Android Revolution or Redemption (which is weird, I have less stability on gingerbread than ICS...), so I'm pretty sure it's not any app causing this.
All three ROMs with this issue are very heavily modified Sense, which might be what's causing this. However, they aren't known bugs and seem to be unique to me.
Any help appreciated And yes, I must have either one of them- I really like the Sense 3.5+ tweaks.
TL;DR- Random FC+Reboot, don't think I did anything wrong. HALPZ
Well best would be the roms thread that you have had issues with and see what the devs offer .
Sent from my HTC Inspire 4G With Beats Audio using xda premium
Everytime you flash a rom are you fully wiping? A full wipe is recommend between flashes.
Also make sure you watch what you restore after flashing. Do not restore any system settings.
"I am the Bacon Pope"
To tie in with CW if.you restore any apps make sure your restoring data not app and data..
Sent from my HTC Inspire 4G With Beats Audio using xda premium
I'm pretty sure I'm doing everything right, but I'll post a breakdown in case I'm wrong
Before flash:
Wipe Data/factory reset, wipe cache/dalvik, format system.
After flash: power off, reboot, wait a few minutes, setup phone.
I usually restore app+data, so I guess I'm doing that wrong , but I've tested this issue with a 'fresh' flash and the app downloaded off the market, no restore. Same problems.
On the Coredroid Q&A 'Towboat_man' said that it might be an OC/UV script issue. I'm going to reflash for the third time, and disable the scripts to see if it changes anything.
Thanks for all your replies
EDIT: Just reflashed (just in case), and disabled OC scripts. So far Dolphin HD, downloaded off market is working fine. I'll test this on friendcaster later.
Yeah sometimes scripts can mess you up. I always suggest trying a rom for a few days without adding any scripts or over locking. I personally never do any of that anymore and get perfect results. Glad you figured it out.
"I am the Bacon Pope"
CRAP+ oh well
Well I ended up having the same issue with OC daemon scripts removed. Apparently this issue was two fold. One, the OC daamon scripts were causing random reboots and possibly my FC problem. The second issue was my back up. Somehow a few certain apps that relied of network access kept crashing when I restored their settings. They FC on on data restore, regardless of where that restore came from. In app restore functions could cause this, as well as titanium.
I'm not sure why this is so, possibly because my backups were from the Redemption ICS rom, whereas all the ROMs I had this issue on were gingerbread. However, I didn't have this issue with non modified gingerbread/sense ROMs like Android Revolution.
I tested this again, and gReader (by oinoin) also had the FC issue.
So long story short, if you have network caused FC's, don't restore data!

Combine Google Play Devices

This was my first experience today flashing a custom rom, and I was really annoyed by one big issue. For some reason, google detected the new rom as an entirely different device, and so it didn't sync anything. On the play store, I now have two devices listed, a verizon SCH-I535, and a verizon SCH-I535. Is there anyway to combine these two or to force the new rom to id itself as the old on to prevent this?
Edit: Sorry for not mentioning this earlier, but the new rom I tried was CM10, although I seemed to be having the same issue with Synergy, but everything syncs up just fine when I flash back to root66.
I have had success using titanium backup to restore my "Android ID" after it was changed. It just pops up and asks you right when you start the app after you've backed up and changed roms. You may have success getting Google's backup to restore that way... I personally disable Google's backup and use titanium only, because you get more control over the whole process that way.
Is there anyway to manually change your Android ID so I can switch it back to what it was on the stock Rom? Also, is this normal to be getting a different ID for each ROM? Also I thought the whole point of Android's sync was so that when you get a new phone/device, it would be able to update that new device to have the same apps/contacts/etc as your old device. Does this option have to be specifically enabled? If not, then why is it not working correctly for me?
<delete>
Hmm.. just came to mind, why does the button say "Edit/Delete" and yet there is no option to delete?

Network icons never turn blue anymore on JB

My network icons (WiFi, Cell Signal) used to turn blue (showing connectivity to Google). I tried XenonHD and decided it wasn't for me so I flashed back my Nandroid of the 4.1.1 OTA from kibmcz. For some reason, it seems that after flashing back, my icon never turns blue, even though I can connect to the Play Store, retrieve Gmail, receive Google Voice notifications, etc.
Any thoughts on how to restore this background connection to allow my network icons to turn blue?
I'm backing up (TB) and getting a Nandroid, then reflashing. I think it may be due to the device ID. This was the first time I chose to get the old device ID back when restoring from TB, instead of choosing ignore and keep the new device ID.
Update coming soon...
I've never had issues with changing or not changing the device ID (I've done both over the course of trying out way too many roms). Any chance you accidentally restored some system or Google date with TB? That could cause some problems. In general, don't restore through TB unless there is unrecoverable data that doesn't really interact with the system (such as game scores). If you can restore the data from somewhere else (email from a server, etc) do that. Restore any apps that don't need their data restored from the Play Store (translate, browsers, etc)
Instead of reflashing the OTA, I decided to go with a CM10 (listed in signature). This time I selected "Ignore (keep the new device ID)" and this seemed to work. Coincidental or not, the only time this has been an issue is when I told TB to restore the device ID. Perhaps a TB bug? I'm not sure. I've always restore almost everything stored in TB and never had any issues, especially since I typically don't flash multiple ROMs. I usually stick to stock OTA.
Thanks for the reply, dvorak. I may start doing that if I switch ROMs and not just re-flash the same ROM.

[Q] Gapps crashing on boot (PA 2.52)

This is the second time I've had this problem. I'm running Paranoid Android 2.52 on my Infuse, and everything's been working just fine ever since I ported it. I've installed no new apps and have changed nothing whatsoever, but suddenly, Gapps has begun crashing and this takes other processes down with it.
On boot, Gapps will immediately crash, which takes Talk down with it, and sometimes Trebuchet. And a handful of my apps are crippled by this problem, as well. I can't download anything from the Play Store, the download immediately errors out. If I try to create a picture message, Messaging will crash (though regular texting is okay). Titanium Backup crashes on load, and I'm sure there's plenty more errors I haven't found yet. And the little WiFi or mobile data icons in the notification bar never turn blue, they're permanently grey now. But I still have the ability to use data and make calls (I can connect to Facebook and dial my voicemail, anyway).
I've done some searching into other people with crashing Gapps, and one suggested a fix by wiping the cache and dalvik cache, but this didn't improve anything. Someone fixed it by formatting datadata, which I don't have as I'm on JB. Another suggested it's a shortage of storage space in the apps folder, but I'm showing hundreds of megabytes left in that particular folder alone. I've used a very small percentage of my phone storage altogether. Phone, internal, and external SDs are very low in storage use. When searching for apps, I prioritize a very small file size.
The first time this occured, it was as sudden and inexplicable. The first time was on an older version of PA JB. One day it worked, the next day, after making no changes of any kind, Gapps started crashing with the same symptoms. After enough searching and failing, I decided I was okay with just wiping back to stock and moving up to the latest (at the time) PA, so first I experimented with flashing the newest compatible version of Gapps, and then EVERYTHING on my phone would crash on boot, and it was completely unusable. So I Odin'd back to stock, worked my way up to PA 2.52 a few months ago. The release had only been a couple days old at the time. And everything was perfectly solid and stable, up until just today, again with no changes made on my part.
The only thing I can report is that this time it began happening while I was watching a YouTube video, which I tend to do a lot on my phone, over WiFi. I haven't installed any new apps in weeks, I haven't changed any settings since I first ported PA. Just, suddenly, BAM. Gapps is completely unusable.
Anybody have any idea what the issue is and how to fix it?
Be sure you are using this version of gapps http://goo.im/gapps/gapps-jb-20121011-signed.zip
If not, uninstall the version you are using, wipe cache and dalvik and install from above link. Also be sure not to restore from TiBu anything more than just the app. (no data). gl
Pony Express said:
Be sure you are using this version of gapps http://goo.im/gapps/gapps-jb-20121011-signed.zip
If not, uninstall the version you are using, wipe cache and dalvik and install from above link. Also be sure not to restore from TiBu anything more than just the app. (no data). gl
Click to expand...
Click to collapse
That is the precise version of Gapps I'm using. Also, I never performed any restore from Titanium, because when this happened last time, it prevented Titanium from loading, so I couldn't make a backup. I made a Nandroid backup from CWM, but then I discovered that no app could restore from the Nandroid backup because it's JB. So, this current port is entirely clean and from scratch, basically.
This is the exact process I went through when going back to stock and building up to JB:
UCLB3 Return to Stock - http://forum.xda-developers.com/showthread.php?t=1705260
Unofficial CM9 - http://forum.xda-developers.com/showthread.php?t=1601844
PA 2.52 - http://forum.xda-developers.com/showthread.php?t=1742073
There was absolute minimal use on the phone between steps. Only use was to prepare the phone for the next steps. All instructions I followed are found in those threads and it all went without error.
You did a great job with the process. I am on a different rom (4.1.2 using Scott's build as a base) and am using 20120726 gapps with no prob... may be worth a shot
Sent from my GT-I9300 using xda premium
Pony Express said:
You did a great job with the process. I am on a different rom (4.1.2 using Scott's build as a base) and am using 20120726 gapps with no prob... may be worth a shot
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Well, the last time I had this problem and I tried updating Gapps, it rendered my phone completely unusable, everything would crash on boot, requiring the return to stock. And to be totally honest, this is the week before finals for me, and I just don't have the time to do a whole new back-to-stock-and-build-up right now, lol. So I'm hoping there's a solution that doesn't require all that time and work, because I won't have the time until next Monday night or Tuesday morning. And that's a long time to go with a phone that doesn't work properly.
Either way, thanks for your help so far.
It also appears that some of my apps have started vanishing. I haven't uninstalled anything, but I noticed that my XDA app is no longer there. Just... vanished. And there are some apps I have on my home screen that, when I try to open them from the home screen, I get a small error saying "App is not installed," and that app is not present in the app drawer, despite its shortcut still being on a home screen.
A long series of bizarre errors, this.
How come you gt to have all the fun ?? lol
I will try to find time tomorrow to download the rom and see if I can duplicate the errors and go from there.
I made a tiny breakthrough last night. I was going through my app manager and saw that, despite my clearing the cache in CWM, some apps still had HUGE caches reserved. So I cleared the cache of apps like GooManager, Play Store, YouTube, G-Mail, and any other apps that had enormous caches, and the problem seems to have subsided as a result.
I remember doing something similar last time, and it only worked for a couple hours before the problem came back again. So I'll keep you updated on whether or not the issue does come back. But so far, it seems to've done the trick.
Sent from my SGH-I997 using xda app-developers app
Nice! There is an app in Play called Cachemate (free) that I like for stuff like this. I use it every 2-3 days.
Welp, it's been about a week since I cleared the caches and things. I also moved all the apps to the SD card that would still work. I found an app (DroidSail) that will force-move apps to the SD, regardless of whether or not the stock app manager will allow it. Such as Facebook. There's no reason the 33mb of Facebook can't be on the SD. And a couple other apps like that, the real unimportant, non-functional ones.
Anyway, it's been about a week now and so far, so good. That seems to've done the trick. But why does that happen? What makes this kind of maintenance necessary? And, actually, while I'm at it, what cache am I clearing in CWM if it's not this one? And why does my phone require somewhat regular cache-clearing? Is it a PA thing, or a JB thing, or is just a me thing because I've done all this to my phone?
Either way, final verdict:
Anyone having these problems in the future. just clear your caches using the above methods.

Categories

Resources