Hi P999 users. Ive been experimenting with the Eagles Blood ICS ROMs and wanted to post some of my findings. I am not allowed to post in the relevant developer area where a detailed report would be useful so I will just post my feelings about the ROM's here for the next few weeks, until I am allowed to post more useful information.
I started out on the CM9 version of Eagles Blood, and then switched to a nightly AOSP ROM two weeks ago. I wanted to find out with AOSP was all about. This build felt very smooth. However crashes and force closing have cropped up in the past few days and this made me feel uncomfortable with the ROM's stability.
An update was released on the 20th so I felt the need to backup with Titanium and install the new ROM.
While installing the new ROM I read a notice in the changelog which confirmed my suspicion about the frequent new force closing. It seams there was some file corruption happening in previous builds... Maybe this was the reason mine was having issues??? How do I feel about this?
Anyways, after installing the newer ROM, and restoring my backup things were out of whack. Something about the restore had left some systems settings unusable and my Data connection was not working. Everything was force closing, even the android keyboard. I re-wiped and re-installed the ROM and backups with the same issues.
I decided to go back to build 4.0.3 and things have been good since. I had a feeling my Titanium backup was ruining my AOSP installations so this time I took a selective approach to restoring apps and did not restore system settings. My data connection is working again and my apps are working well. (Just to be clear I went back to the CM9 based version of EGB and not the AOSP version I was using which became unstable over time)
I do appreciate the AOSP development on behalf of EGB team but will be staying with the CM9 build for stability sake until file corruption issues are dealt with.
And that's how I feel about that.
the file corruption issue is your issue though, how are they supposed to fix your backup from your phone? Don't restore the settings and system, just apps. I don't get what the big issue is...
good job
mt3g said:
the file corruption issue is your issue though, how are they supposed to fix your backup from your phone? Don't restore the settings and system, just apps. I don't get what the big issue is...
Click to expand...
Click to collapse
MT3G thanks writing verbatim the solution I wrote into the OP.
*edit* the file corruption issue and the titanium backup fiasco are not related. It is my understanding that EGB team is aware of corruption cause by the early ASOP release and that they are working on it. I've decided not to use the AOSP version until they take care of it. (Solution / Workaround #1)
Maybe this is a big issue for someone who would not make the connection between restoring a system backup and the data connection not working anymore. I felt this was good information and that's why I posted it (Solution / Workaround #2)
Yeah that's why I never back up or restore any type of system settings; always gets you trouble.
Glad to see you're a problem solver , we don't have much of those here.
exactly my thoughts, most people wold just freak out and say the rom was stupid or something, I read the post as he was saying he is going to wait for EB team to fix the issue where as it isn't going to be "fixed" lol. Unless you are updating the same rom or a rom that hasn't been extremely updated then it's possible for it work out okay. But using cm7 backing up and then going to cm9(4.0.x) and restoring is going to be a no go probably. i'm with Buru though except I just stay away from TB all together, I only use about 12 apps and no games.
update
Just a quick update. Its been almost 3 weeks on the EGB CM9 build 4.0.3. I've been very happy with it. Occasionally I install updates and I get strange behavior after. I've found that rebuilding permissions after an update is a good practice.
buru898 said:
Yeah that's why I never back up or restore any type of system settings; always gets you trouble.
Glad to see you're a problem solver , we don't have much of those here.
Click to expand...
Click to collapse
I have restored email (with all accounts, data and app) as well as saved wifi locations before. I believe both of those are system settings and they never caused problems.
Sent from my LG-P999 using XDA
Try using GoBackup for apps, contacts (if you don't sync to your gmail), and some system settings. I like it more than TB. I'm not saying it won't cause FC's and that's because I don't know. But it might work better.
Related
I've loaded the new CM7 RC2 versions from 009 to 011.
The WLOD accurs when launching stock browser or facebook and some games.
What I've done is to go to Cyanogen Settings and to Performance.
I ticked the Set on boot checkbox and changed to Battery saver.. since then haven't had any WLOD on stock browser or facebook for android.
Guess this is OC related.
Although when I restart my phone it gives a "force close " error on Cyanogenmod Settings and changes my govenerback to on demand the WLOD is still not accuring.
Is the WLOD issue resolved in 012 or am I just lucky for now.
Also hope this works for more people or the Devs . Sorry but I can't post on the Devs Threads.....
I've tried everything... no WLOD on the 2 mentioned apps anymore. Don't know what fixed it , but it only stopped after as mentioned above
i would try this but im on the 12 rom. Are you suggesting that going back to 11 and changing the settings, then reflashing and restoring data would work?
I won't suggest that... I went on to the new v012 and now WLOD on v012..
I Will go back to v011 and do the same changes to see what happens..
This was not meant as a solution to the problem just maybe for the DEVS to have a look.
Also on v011 I can play fruit slice but WLOD on v012.
EDIT: also i've noticed when playing 3D games White LED coming on and off but not killing phone and when on low power,, this WLOD issue might be the Mhz Difference and battery types in lots of different phones.
So one custom rom maybe doesn't support various types, hense forth people getting diiferent WLOD crashes
EDIT : Now the fruit slice game works... Haven't changed anything..
This WLOD's are really an extreme random thing, DEVS must have a really hard time.
I think most people don't flash their phone completely the right way maybe even me..
I've noticed that unless you do a complete format of the sd card and don't restore anything from a previous version there is always something
left on the phone and when downloading the same app it uses that data. hense WLOD's (maybe)
v012 Facebook and Browser working
Ex : I've Reflashed my phone cleared all the things off and when I reinstalled the fancy widget's app the downloaded skins were still their, I think lots of apps leave traces so even with the cleaning tools that exist you dont always get rid of everything and with a restore lots of people probably import the corrupted files.
CM 7 v012 is alot better than v011.. Thanks to the DEVS..
i've Had minor issues that somehow sort themselves with a reboot after first load of a app,,, nothing else serious as yet.
v012 Is The most stable Android 2.3.3 so far.
Thanx
Apologies for a long post.
But more importantly... "THANK YOU" to all the members of XDA-Developers!! (Too many individuals to list/remember separately)
OK, long story:
I have a 32 GB wifi Xoom. I upgraded from Tiamat kernel 1.4.1 to Tiamat Moray Rom 2.2.2 last week. In the kernel, I was experiencing sluggishness, FCs (launcher, market), and long (2 min. +) boot times. Moray fixed the sluggishness and the FCs, but boot time increased by 30 sec. (no big deal).
After about 6 days (yesterday), problems started mounting, and my device "eroded" (steadily crept toward what I saw as death.):
* The wallpaper had strange markings/moire
* Gmail FC'ed immediately
* None of my computers would recognize the Xoom file system (after having done so minutes prior on my work machine and that morning for my home machine).
So...
I attempted to reflash Moray-- things got worse, EVERYTHING FC'ed, wifi died.
I attempted to restore my nandroid (of Tiamat kernel before I originally flashed Moray)-- things hit rock bottom, it bootlooped.
This morning, I was about to give up. I had already placed a new Xoom in my Amazon.com shopping cart.
But, I tried again...
From you amazing contributors, I was about to find potential answers, and hope
One guy had the exact problem I did:
http://forum.xda-developers.com/showthread.php?t=1240904
In other places, I learned about adb and fastboot and Motohelper PC drivers.
Now, I have just finished a nandroid of a "clean" Moray flash.
I'm ecstatic.
But, also worried. I have NO CLUE how/why the problems started.
If anyone who made it through reading all this has any idea to help me and others, or confident words that the problem(s) are gone for good, please pass them along. Basically, I would like to know if there are specific apps to avoid, filetypes to never save, actions to never perform, etc...
This ordeal has taught me that ANYTHING on xda-developers is potential gold.
Anyway, thanks again from a slightly-less-noob-ish Xoom user.
A lot of times, all the problems mentioned can be completely avoided by doing a clean install of any rom. I always do this even if the directions say it is unnecessary. by wiping all data, you are removing any incompatible or corrupted files from your device. For force closes with google apps, it can be caused by not having the proper signature from the maker itself. I have avoided this in all roms I have made by not resigning them and even removing them entirely, since they can be installed from the market.
As far as the long boot times, the incompatibility of apps and corruptions removed during the wipe process should have fixed this as well as the system isn't trying to start and piece together these apps.
I hope this gives you a little understanding as to your issues and why they happened...if you want a further explanation, please contact me. Also, I am glad to see your issues are fixed and you didn't purchase another xoom...
another tip...restore your apps only and not system data from titanium backup...a lot of times, the data is not compatible with the new system you put on your device.
dhemke17 said:
A lot of times, all the problems mentioned can be completely avoided by doing a clean install of any rom. I always do this even if the directions say it is unnecessary. by wiping all data, you are removing any incompatible or corrupted files from your device. For force closes with google apps, it can be caused by not having the proper signature from the maker itself. I have avoided this in all roms I have made by not resigning them and even removing them entirely, since they can be installed from the market.
As far as the long boot times, the incompatibility of apps and corruptions removed during the wipe process should have fixed this as well as the system isn't trying to start and piece together these apps.
I hope this gives you a little understanding as to your issues and why they happened...if you want a further explanation, please contact me. Also, I am glad to see your issues are fixed and you didn't purchase another xoom...
another tip...restore your apps only and not system data from titanium backup...a lot of times, the data is not compatible with the new system you put on your device.
Click to expand...
Click to collapse
Excellent advice!
dhemke17 said:
A lot of times, all the problems mentioned can be completely avoided by doing a clean install of any rom. I always do this even if the directions say it is unnecessary. by wiping all data, you are removing any incompatible or corrupted files from your device. For force closes with google apps, it can be caused by not having the proper signature from the maker itself. I have avoided this in all roms I have made by not resigning them and even removing them entirely, since they can be installed from the market.
As far as the long boot times, the incompatibility of apps and corruptions removed during the wipe process should have fixed this as well as the system isn't trying to start and piece together these apps.
another tip...restore your apps only and not system data from titanium backup...a lot of times, the data is not compatible with the new system you put on your device.
Click to expand...
Click to collapse
Thanks. Your words are spot on:
1) I fixed the problem by learning how to install/use fastboot to get rid of *everything*.
2) My force closes began immediately after boot of Google apps: Gmail, Market, Video, Browser, and something called "ancore" (I guess its the core android os).
3) Between my original flashing of Moray and the disaster, I had installed two potentially "improper" apps: the ICS Gmail that was circulated in a Tiamat Moray thread here, and tTorrent. Neither will be reinstalled on my "new" Xoom.
4) In my panic to reflash Moray and restore my nandroid, I may have mixed system data and made things worse.
I may leave my Xoom alone for awhile until I have more thoroughly researched xda-developers.
mightydr said:
Thanks. Your words are spot on:
1) I fixed the problem by learning how to install/use fastboot to get rid of *everything*.
2) My force closes began immediately after boot of Google apps: Gmail, Market, Video, Browser, and something called "ancore" (I guess its the core android os).
3) Between my original flashing of Moray and the disaster, I had installed two potentially "improper" apps: the ICS Gmail that was circulated in a Tiamat Moray thread here, and tTorrent. Neither will be reinstalled on my "new" Xoom.
4) In my panic to reflash Moray and restore my nandroid, I may have mixed system data and made things worse.
I may leave my Xoom alone for awhile until I have more thoroughly researched xda-developers.
Click to expand...
Click to collapse
There is a wealth of information here, almost all of it buried in the back pages. It's a guarantee that "someone" has had the exact same problem, and usually has been able to find a solution, and as you said, almost everyone wants to share.
It seems like every time I set up a new ROM, it takes me forever to get everything set back up and I always miss something, contacts are missing, apps go all wonky... I used to backup all my apps and data, but a lot of the time the new ROM will download many of the apps I had, so when I restore the backup of my Apps, it screws everything all up.
So I guess my questions is... Whats the most sufficient, easiest, most thorough way of restoring all apps and whatnot on a new ROM?
For the basics use the market app to backup your sms to google cant remember what its called, backup your contacts to google (highly recommend) that way you will never loose them.
For apps i would only ever backup downloaded apps with titanium backup pro. System apps can be a pain in the ass to restore.
Other than that everything else is fairly easy...
Sent from my GT-I9100 using xda premium
Hmm... Ive never gone about backing up SYSTEM apps, but like paid apps, that Ive bought and backed up, seem to get all jacked when I restore or reinstall them. Ive tried a few different methods of restoring my system and never get it to go smoothly. Didnt know if there was an easier way. Thanks for the info!
You might want to upon first boot of the new ROM, bypass initial setup with the tap corners trick, restore apps with Titanium, then resume the setup process. Market will see your apps as already having been installed and not bugger everything up.
Good idea! Hadnt thought of that. Will try with my next rom. Thanks! Anymore tips out there?
First thing I thought of was nandroid backup using clockworkmod on a rooted device. I have restored my phone countless times and everything restores exactly how it was.
sometime i got errors while restoring with CWM..
Titanium is still the recommended.
When I first started out, I actually had to make a list and check it off. Eventually, I found some apps that would cover those items (Titanium, etc), but still even with that I have to manually go in and do a few settings. MIUI ROMS have a backup program (I used MIUI on my HD2) and it seemed to do a decent job.
I usually keep a current back up of all apps from market(not system apps) made from my backup pro. Everything else gets a fresh start.
When I switch android versions ei, from gingerbread to ics, nothing gets restored, everything is a fresh install from market.
Sent from my HTC Vision using XDA App
Was it through CWM rom manager or manual recovery mode? I mean did you install a kernel that installed cwm or did you install rom manager? After a couple weeks walking around blind I figured out that flashing the right kernel gets cwm to work without problems.
Restoring system settings is a big no no. It is just asking for trouble as with each update the source code is changed and then you are restoring outdated settings that may or may not be there.
TIBU is still the main app restore program. As for restoring settings that is never advices. Well unless you like troubleshooting random errors lol
Thanks for ALL the replies! Some stuff I hadnt thought of in here, and some stuff to try. If anyone else has any more info, please feel free to share. I have heard that restoring settings is asking for trouble, so luckily Im not too picky about those. I really only change the haptic feedback and stuff off the bat, anyway. It also sucks losing all my WiFi networks and having to have all my friends dig up their network passwords.
Anyway, gonna try out some of this stuff today as Im sick of the ROM I just flashed. Still waiting on MIUI getting that MMS workin
zelendel said:
Restoring system settings is a big no no. It is just asking for trouble as with each update the source code is changed and then you are restoring outdated settings that may or may not be there.
TIBU is still the main app restore program. As for restoring settings that is never advices. Well unless you like troubleshooting random errors lol
Click to expand...
Click to collapse
I concur, system restores after updates, different roms etc are a nightmare lol. It might be a pain in the a$$ but i ALWAYS start afresh after each flash and never use the same data image lol
Hey, I've done a fair whack of searching and unfortunately even though I've done a lot of lurking and reading, I do not have permission to post in the developers forum. Supposedly I need 10 posts before I'm able to post inane drivel to spam up the threads.
Annnnnyway, I've had a crack with a few of the more popular SMS apps, along side the native Messaging app, and all of them crash immediately on launch. The exception is Go SMS Pro, which is unable to detect any SMSes or even send any SMSes.
I've no clue how or why this is, I've cleared both my normal and Dalvik cache, the MMS.APK is in place in /system/app/ folder, the permissions are correct, I've tried clearing the data, and I think short of a full wipe and install, unless someone can point me in the right direction, I've tried most things a reasonable person would think of. Granted, I'm not knee deep in Android development like a few of the people who lurk around here, so I could be mistaken.
I'm running a standard HTC Sensation with a slightly out of date version of the default 1.5GHz kernel included with Android Revolution HD, although I am planning on flashing the latest TamCore to see if that will clear it up (though I doubt it). Currently I have OpenSensation-20120809-NIGHTLY.zip installed, but I'm downloading OpenSensation-20120810-NIGHTLY.zip as well in hopes that maybe it's a bug in this nightly that is resolved in the newer one, although I doubt that.
Anyway, any help is much appreciated.
Cheers.
toejam316 said:
Hey, I've done a fair whack of searching and unfortunately even though I've done a lot of lurking and reading, I do not have permission to post in the developers forum. Supposedly I need 10 posts before I'm able to post inane drivel to spam up the threads.
Annnnnyway, I've had a crack with a few of the more popular SMS apps, along side the native Messaging app, and all of them crash immediately on launch. The exception is Go SMS Pro, which is unable to detect any SMSes or even send any SMSes.
I've no clue how or why this is, I've cleared both my normal and Dalvik cache, the MMS.APK is in place in /system/app/ folder, the permissions are correct, I've tried clearing the data, and I think short of a full wipe and install, unless someone can point me in the right direction, I've tried most things a reasonable person would think of. Granted, I'm not knee deep in Android development like a few of the people who lurk around here, so I could be mistaken.
I'm running a standard HTC Sensation with a slightly out of date version of the default 1.5GHz kernel included with Android Revolution HD, although I am planning on flashing the latest TamCore to see if that will clear it up (though I doubt it). Currently I have OpenSensation-20120809-NIGHTLY.zip installed, but I'm downloading OpenSensation-20120810-NIGHTLY.zip as well in hopes that maybe it's a bug in this nightly that is resolved in the newer one, although I doubt that.
Anyway, any help is much appreciated.
Cheers.
Click to expand...
Click to collapse
Might be an issue with OpenSensation (as you're using nightlies). Back up what you have, format everything but SD card, and I'd recommend trying a completely different non-nightly ROM, try AOKP m6. This way you can see if the SMS issue is related to OpenSensation or not. backup m6 THEN try the newest OpenSensation nightly to see if the issue is fixed. This way you'll likely be left with at least one ROM you can restore with working SMS functionality.
I might yet have to do that, although I would prefer to stay as close to vanilla as possible, that's why OpenSensation interested me - I think I'll try regressing to the CM9 RC2 on the official Cyanogen mod website first, then try other projects after that if that doesn't work. Does seem strange that no one else is complaining of this issues though, and I really can't see myself being the only one running the latest versions.
Oh yeah, the newest nightly and Tamcore kernel didn't work - the only thing that's changed is now I know I can't regress directly to my ARHD backup, yay!
This one's a bit of a thinker.
Well, I did a full wipe, installed the latest HyperSensation CM9 build and reinstalled the TamCore Kernel. Everything seems to be working now.
Thanks for the input, thread can be closed.
Hi,
I upgraded my Tab to 4.1.2 and have been having problems with my SMS. The Messaging app is not moving the thread to the top when a new text comes in, only when I reply.
ie the 10th thread in my list continues to be at the 10th position after receiving new messages. It doesn't get moved to the top which it used to. I thought it was a problem with the app and tried using Handcent. The same problem persists. It seems like there is something wrong with the time stamp of the thread not updating properly or something.
Anyone has any idea what's going on or what a solution might be? It's a big annoyance.
Thanks!
Hep, have this problem too. Very annoying.m I think samsung is doing this on purpose to force us to buy a new tab. Even though the 7.7 still holds it ground with the latest device.
Samsung is probably slowing things down on purpose too for this tab. I still notice a little lag.
I have the same problem.
same problem here, already tried a full flash (JB) still the same, i thought it was just GO SMS but I already uninstalled and and the problem persist, it's so annoying when you have to look for the one who sent u sms
In XDA, you'll find a mod to correct the date-time stamp for stock de-odex MMS.apk.
There are some simple guides, but you must be rooted first and most likely de-odexed.
Sorry, don't have the time right now to actually do a JB version for you, and also unable to test without device model (assume you have P6800).
I have previously modded a P6800 ICS app here : http://forum.xda-developers.com/showthread.php?t=2204628. 122 dl, and ZERO feedback. Didn't even know if it worked.....can only assume so.... This is not for JB, won't work. The JB MMS.apk needs to be modded.
It may not even solve your problem. But hey, at least there's a 'possible' solution if you're willing to try to mod yourself
Sent from my GT-I9500 using xda premium
I can't even begin to imagine how to mod an app. my skills are limited to just rooting and flashing roms. If I flash a custom ROM, say Cyanogen, will it fix the problem???
ok, I contacted Samsung about it and their advice was to do a complete factory wipe. I backed up my SMSs and tried it. After restoring the messages, everything was fixed. so there's the fix. but at the cost of having to restore everything after a complete wipe
Android sucks. Its the only os that forces u to do a full wipe for each updates.