I'm getting huge delays with some push-based apps (e.g. Whatsapp) since the update when I'm on the data connection. When I'm on WiFi everything is fine.
Does anybody else have this issue?
Whatsapp delay
Yes. I'm having the same problem for a month or so. ever since I installed cyanogen 7 on my galaxy ace, no matter what i did, whatsapp messages kept on delaying. I first tried restoring a nandroid backup, didn't work. I then tried reinstalling cyanogenmod, it worked for a bit but it then start failing again so i reinstalled cyanogen and did a nandroid. It didn't work. I thought it could be something the nandroid backup did to the cell, so i reinstalled everything from the beginning: flashed the device to original stock rom then root, cwm, and cyanogen again.
The delay i noticed then was not to take on account 3 to 4 minutes the most.
But now again! i open the app and start recieving messages from hours ago. The thing is i've been using the device during the hours that i should have recieved all those messages. I don't know where can the problem come from. All I know is this didn't happen before having cyanogenmod installed, and know it does.
Does anyone have the problem above? Does anyone know of a possible solution?
Thanks in advance!
I have exactly the same problem and i don't find any solution...
Well I've changed carriers twice since I created this thread and my problem has been solved long ago by itself. Maybe the first carrier's data coverage was weak or something. Well TBH with the first carrier I rarely got 3G, I was on Edge most of the time I recommend that whoever's having this issue should check his connection.
[Solved]
I think i at last found how to solve the problem. I bought an Lg O2x and obviously installed a csustom rom, (MIUI) it all worked fine until I did a nandroid backup in order to try a new rom, which i didn't like. After trying it i restored the nandroid backup, and whatsapp started misfunctioning again. I then installed the rom from the very begining, and configured all step by step and whatsapp didn't fail since then.
Conclusion: The same problem happened in two different devices which only had in common the cwm and a nandroid backup restored, diferent rom, diferent devices, different carriers. So try flashing the device from the start or reinstalling rom from cwm. Remember to wipe data, cache, and dalvik. and remember not to restore any backups at all.
Hope this can help you!!
Related
I've searched the forum and Google for over an hour, and I cannot find any information on this issue. I am trying to install attn1's R012 ROM. I previously installed the R008 build a couple of months ago, and I have had no issues. I want to upgrade to the latest build, but I am running into a problem when doing a Nandroid backup. As the title to the post suggests, on the last step of the backup, it seems to freeze at "Generating md5 sum...". I have let it sit for over an hour now, and it is still frozen.
I cannot find any information on the root cause of this problem or the resolution. Could anyone shed some light on this for me? And help is greatly appreciated!
What speed SD card do you have? That would be the only real variable as to why your phone is having issues - there could be a timing issue if you are using a real slow card.
have you done a nandroid backup before with no issues? is this a new problem or has it existed previously?
Thank you both for your replies. The SD card is a Transcend 8GB Class 6, and yes, I have done a Nandroid backup before, prior to installing attn1's R008 ROM. I had no issues with that backup.
Also, to at least use my phone for now, I did a battery pull. I tried running the backup again, with the same result.
if your old backup was created normally, i would recommend reflashing that backup and trying installing the new rom again.
reinstalling your apps may be a pain, but it seems like your best chance at restoring the functionality of your phone. or simply wipe everything and install a new rom.
thats happened to me before, right after i flashed a new kernel! It sucked! i had to wipe
Checked around but no details for my prob...
Suddenly getting many FCs for software that was previously working... Namely HD games that others state work fine on Iconia. Software that was working fine 2 days ago, suddenly FC immediately after startup.
I'm running Stock 3.1 rom rooted, with a tweaked kernel (thor latest).
Anyone else getting similar issues lately? Bit of a noob but would love to avoid a wipe or flashing a new rom...
Greatful for any advice from you experts... Do lead thru in baby steps... Ta!!
what about a wipe of just the data for one of the offending apps?
Some are newly downloaded from market e.g. "Diversion". Odd, as it was working along with others perfectly fine a day or 2 ago. Now it's like a plague of software immediately FCing...
Possibly need to do a CWM wipe of data or a factory reset (makes me nervous) or bite the bullet and try a clean 3.2 rom with root...
Any further advice?
I got something similar with stock 3.1, no hd or tegara apps working all FC. happened after a live wall got distorted or corrupted, the same way like video corruption on PC, before this i had installed sprinkle game. Fixed it with full format, and never installed sprinkle or that live wall again.
Phew... was feeling like I was the only one! Thanks... So what way should I run a full format? How much will I lose (I do have Titanium backup throughout)? Should I even restore the Iconia Phone status via the market program BEFORE I wipe?
Sorry for panic... just want to be SAFE!
i just ran format from the settings menu, i don't know about backup
Thanks... I'll try later as a last resort. Fingers into cross-mode!
EDIT - Bit the bullet and tried a 3.2 rom... my virgin turn but seems to have worked now! Possibly a CWM use of wipe data / cache may have worked, but why not jump in the thrilling fire of flashing roms!
Hi all. First, forgive me if this has been questioned and answered before, but I face a really BIG BIG problem with my CWM made backups...
Regardless the are created right, and restored, the restored ROM gives me android.core.gapps errors continuously, rendering the phone unusable...
Maybe it's only my phone, I don't know, maybe CWM recoveries are young on my S4 variant and have bugs...
BTW: I own an S4 LTE Advanced (GT-I9506)
I have had the exact same issue. I have a Samsung note 2 N7105. I rooted made a backup in CWM and flashed ditto n3/s5 rom made another backup in CWM. No issues. Got a bit cocky seen as it was my first time doing anything like that. My next adventure was to try a custom kernel (agni). This didn't go so well, so I tried to do a restorw to my working backup of ditto n3/s5 rom through CMW. restore went smoothly and the phone booted. once I opened the lock screen I got the gapps error as described. I had to do a factory reset to get the phone working and then re-flashed ditto n3/s3. I've since flashed other roms and when ever I try to do a restore, I get the issue described. Note I am using the latest CWM. I putting off flashing and trying any other ROMs because of this issue. I do love dn3/s5 but id love to try others. Anyone can help it would be appreciate.
Hi all,
Some time ago i asked, and received, some support on these forums on how to properly carry out a nandroid backup... following the sound advice i got, i carried out my backup (using TWRP for the record, with all the options checked), and stored it away for a rainy day... said day came yesterday, when i messed up my system and rendered it instable (i tried to manually delete the dalvik cache directory in order to free up the 2,5GB of space it was taking)... since i knew there was i high chance of this ending in disaster, the last thing i did before the delete was carry out another nandroid, so i could easily return to where i had left off... how wrong i turned out to be
as soon as i the system became instable following my experiment of deleting the d. cache directory, i recovered the latest nandroid (i.e. the one i had made just hours before) and everything seemd to go smoothely until the first reboot... when the following happened:
- first reboot after recovery took ages, much like the first reboot following the flashing of a new rom... not the end of the world, but that was the first sign that all was not well
- the status bar disappeared, and there was no way of making it come back (i.e. nothing to do with the launcher, i typically use apex but i i tried switching to both nova and touchwiz which i also kept up to date but the stats bar was nowhere to be seen)
- even if not having a status bar with all the info on it is acceptable (which of course it isn't, but lets just say), the sytem became completely instable after 5minutes of operation... with each app taking turns to shutting down until i kept getting the message "system UI has closed" over and over, to the point that doing a reboot was challenging since i barely had the time to press on the screen between instances of this bloody error message appearing...
...i did of course try and return to my older nandroid backup, but... lo and behold... exactly same behaviour...
so now i have resorted to formatting the internal memory card and flashing a new rom and basically starting over... just what i hope the nandroid would spare me basically :/
question is: does this sort of error sound familiar to anyone? can someone give me a tip maybe on what i may have done wrong?
any opinion, tips& advice much appreciated
I have the exact same problem. It happens on TW Lollipop ROMs. Haven't found a fix. I'm using Philz Touch Recovery and the old no knox bootloader.
Anyone? I have researched this but cannot find any similar problems reported... it can't just be me and pavelcheto...
Maybe it a recovery fault. Faulty backup or faulty restore.
No problems with my older backups. I restored my KitKat TW backup, working fine. Restoring CM12 backups also works fine. I've looked for a new recovery, Philz is discontinued, CWM hasn't been updated for a year and I really don't like TWRP.
I use TWRP 2.8.3.0 and never have (and hopefully never will) encountered any issues with restoring backups.
Considering i recovered 2 separate backups for a total of 3 times (i tried recovering the first backup twice) i doubt the issue was with the recovery itself... however since pavelcheto had no issues with the kk recovery maybe it could be lollipop related?
Anyone successfully recovered a lollipop nandroid backup?
platypus78 said:
Considering i recovered 2 separate backups for a total of 3 times (i tried recovering the first backup twice) i doubt the issue was with the recovery itself... however since pavelcheto had no issues with the kk recovery maybe it could be lollipop related?
Anyone successfully recovered a lollipop nandroid backup?
Click to expand...
Click to collapse
I recovered my lollipop gpe backup a couple of times without a problem.
Data encryption may cause restoring problems.
I have restored CM12 backups (based on 5.0.2) serveral times, no problem there. I've had issues only with TouchWiz Lollipop ROMs, I have tried different custom roms, all get bugged at restore.
pavelcheto said:
I have tried different custom roms, all get bugged at restore.
Click to expand...
Click to collapse
Just to make sure I understand correctly : you mean all TW custom roms you've restored have had problems?
Wonder if anyone else has managed a bug-free restore of a 5.x TW?
Yes, but only on Lollipop. KitKat TW roms restore just fine. I am using Philz Touch Recovery. I have tried 3 different TW Lollipop roms and they all fail to restore properly. No wallpaper, black wallpaper and no status bar. And after a minute or two System UI starts crashing. If then I do factory reset from recovery and the rom starts normally (welcome guide and stuff) and works fine.
bumping this thread because i cant seem to find a solution for this anywhere.
TheAwesomeBit said:
bumping this thread because i cant seem to find a solution for this anywhere.
Click to expand...
Click to collapse
There's no solution for this as per comments above. TW LP is not restorable. You can flash a new lollipop ROM tho'
Sent from my GT-I9505
Hello people of all ages, races, and denominations. I have a problem with my Nexus 6P. I just recently upgraded from the Nexus 6 so I'm still learning how the new phone works in TWRP etc. For some reason everytime I make a backup then install a new ROM, I can't get that backup to work again. For example, I tried to restore an old Backup and it booted fine but I couldn't get in it because it kept saying incorrect password. It's happened 3 times now. I know my password wasn't changed whatsoever so that's not the problem. I then realized I also had no WiFi by pulling down the bar from the lock screen and even after fresh installation, still no WiFi. It seems no matter what each time I want to install a new ROM or restore an old one I have to reflash the bootloader, radio, and vendor image, EVERY SINGLE TIME. Even if the ROM I'm on already uses the same vendor, radio, and bootloader I still have to reflash them all the time.
With the Nexus 6 I can just flash them once and all rims who use the same will work across it seamlessly but with the 6p I have to have a laptop and go through all the fast boot stuff just to test a new ROM and I sometimes do it on the go and don't carry my laptop with me everywhere so is there anyway for me to just flash new ROM without going through all of that all the time?
Thanks.
TransportedMan said:
Hello people of all ages, races, and denominations. I have a problem with my Nexus 6P. I just recently upgraded from the Nexus 6 so I'm still learning how the new phone works in TWRP etc. For some reason everytime I make a backup then install a new ROM, I can't get that backup to work again. For example, I tried to restore an old Backup and it booted fine but I couldn't get in it because it kept saying incorrect password. It's happened 3 times now. I know my password wasn't changed whatsoever so that's not the problem. I then realized I also had no WiFi by pulling down the bar from the lock screen and even after fresh installation, still no WiFi. It seems no matter what each time I want to install a new ROM or restore an old one I have to reflash the bootloader, radio, and vendor image, EVERY SINGLE TIME. Even if the ROM I'm on already uses the same vendor, radio, and bootloader I still have to reflash them all the time.
With the Nexus 6 I can just flash them once and all rims who use the same will work across it seamlessly but with the 6p I have to have a laptop and go through all the fast boot stuff just to test a new ROM and I sometimes do it on the go and don't carry my laptop with me everywhere so is there anyway for me to just flash new ROM without going through all of that all the time?
Thanks.
Click to expand...
Click to collapse
It works.
Search is your friend.
http://forum.xda-developers.com/nexus-6p/general/psa-twrp-backups-lockscreen-security-t3245070
Seems like shutting off security first would be easier
Sent from my Nexus 6P using XDA-Developers mobile app
Always remove all security before making backups. Makes restores painless!
I made a post about the solution. Search, my friend, and you will find the answer.
TransportedMan said:
Hello people of all ages, races, and denominations. I have a problem with my Nexus 6P. I just recently upgraded from the Nexus 6 so I'm still learning how the new phone works in TWRP etc. For some reason everytime I make a backup then install a new ROM, I can't get that backup to work again. For example, I tried to restore an old Backup and it booted fine but I couldn't get in it because it kept saying incorrect password. It's happened 3 times now. I know my password wasn't changed whatsoever so that's not the problem. I then realized I also had no WiFi by pulling down the bar from the lock screen and even after fresh installation, still no WiFi. It seems no matter what each time I want to install a new ROM or restore an old one I have to reflash the bootloader, radio, and vendor image, EVERY SINGLE TIME. Even if the ROM I'm on already uses the same vendor, radio, and bootloader I still have to reflash them all the time.
With the Nexus 6 I can just flash them once and all rims who use the same will work across it seamlessly but with the 6p I have to have a laptop and go through all the fast boot stuff just to test a new ROM and I sometimes do it on the go and don't carry my laptop with me everywhere so is there anyway for me to just flash new ROM without going through all of that all the time?
Thanks.
Click to expand...
Click to collapse
Make sure you have the latest TWRP 3.0.2-0 link here . With the latest TWRP you should be able to back up and restore everything, including pin and fingerprint (I use pin so that's what I tested), not sure about pattern and password just because I don't use those.
Make a backup without the security settings , turn off the fingerprint and lock screen then back up , you'll never have an issue that way
Sent from my Nexus 6P using XDA-Developers Legacy app
I have never successfully restored a backup with the 6P regardless of the version of TWRP used. I always turn off security settings. Makes no difference. I have given up even trying. And I never had that problem with any other phone that I have ever owned.
I had the same problem maybe i backup and restore wrong partition. Can someone post the correct steps which partitions backup and what wipe before restore.
Maybe read the post by Heisenberg , I've never had an issue backups on the 6p or any other device
Sent from my Nexus 6P using XDA-Developers Legacy app