I noticed something a few days ago while I was flashing the newest build of AOKP, and I was curious to see if anyone has noticed this or if it is just an issue for me. For as long as I can remember, every time I would flash a new ICS rom other than miui, all of the apps i had installed on my phone before the flash would automatically start downloading again upon the first boot on the new rom.
But as i said, upon flashing aokp build 40, remICS, paranoid android, and cm9, none of my apps from the play store have automatically restored. I tried all of them, being that there are different gapps packages for each rom, to see if it was a problem with the GAPPS package(s), but none of them worked. I also noticed that the GAPPS version had been changed for cm9 roms on the cyanogenmod wiki.
Can someone pleas explain to me what is going on, and what I need to do to get the feature of my apps restoring back. I tried searching but came up with nothing, any help is appreciated. Thanks, and have a good day!
thanks for the awesome help everybody, i knew i could count on you guys! (jkjk)
System settings > backup and reset. Back up Google account. Once that's done it should start restoring apps in between builds of anything as long as you do it on that rom. For example you back up on cm and flash aokp... it won't work. But if you flash another cm build it will start restoring again. Oh . And you don't need to wipe data between builds... its unnecessary unless directed otherwise.
Sent from my sprint galaxy nexus
whenever I load a cm10 based rom my wifi drops after 2 minutes. stock based wifi is consistent but as soon as I load cm10, jelly ro, or even the new experimental m1 build with always drops. to reconnect I have to turn off and on wifi. is there any solution? I was reading about cm10 modems and I didn't install anything besides cm10, aosp jelly camera and jelly gapps. any help will be greatly appreciated!
ps just realized I install the camera on every build could that mess it up lol
I've been running several nightlies over the last few weeks and now I'm solid with the M1 build and at this point I have never experienced an issue with wifi dropping.
What steps did you take to flash CM10? (cache clearing? Full wipe? Permissions?)
Ian
Ian1331 said:
I've been running several nightlies over the last few weeks and now I'm solid with the M1 build and at this point I have never experienced an issue with wifi dropping.
What steps did you take to flash CM10? (cache clearing? Full wipe? Permissions?)
Ian
Click to expand...
Click to collapse
I did everything except permissions. Are there permissions for wifi?
No I was just mentioning the common steps so you would tell us everything. Sounds like you've installed the rom correctly but obviously their's an issue. I'm assuming that this issue is right after a clean install and not after you've installed juice defender or something like that? Assuming you're installing the correct version of CM10 for your phone (d2att?) their shouldn't be anything else needed to make wifi work (ie modem file).
If I were you I'd be tempted to redownload CM10 m1 and jellybean Google apps. Ensure you have the recommended version of cwm installed. Clear caches, full wipe, flash CM10 and apps followed by clearing of the caches again. Forget the camera initially and test the wifi. If it still doesn't work we'd need to start looking at logs.
Ian
Ian1331 said:
No I was just mentioning the common steps so you would tell us everything. Sounds like you've installed the rom correctly but obviously their's an issue. I'm assuming that this issue is right after a clean install and not after you've installed juice defender or something like that? Assuming you're installing the correct version of CM10 for your phone (d2att?) their shouldn't be anything else needed to make wifi work (ie modem file).
If I were you I'd be tempted to redownload CM10 m1 and jellybean Google apps. Ensure you have the recommended version of cwm installed. Clear caches, full wipe, flash CM10 and apps followed by clearing of the caches again. Forget the camera initially and test the wifi. If it still doesn't work we'd need to start looking at logs.
Ian
Click to expand...
Click to collapse
ya shes still being stubborn. how do i show logs for you?
Hey, I was hoping someone else would chime in about the logs. I have used "alogcat" for logs before but I'm not familiar with wifi filters so I'm probably not the best person to help at this point.
Anyone?
Ian
Running the new cm10 15th build wifi is more stable but still drops after about 10 minutes. Any help would be very kind.
With all your flashing and even using latest versions I'd start to wonder if something to do with the rom is not compatible with you're rougher. Have a you tested it on an alternate wifi source? Maybe a neighbors open signal or something. It's a noob thought but it couldn't hurt.
Sent from my SGS3 I747m on CyanogenMod 10 using xda premium
Yes I have. Currently on a different network right now and it was still dropping. Less frequently but still happening.
I've been trying to get alogcat working on my phone but the log is blank no matter what I do. Either way, the main developer thread just got a post about wifi and how it's note staying connected. No responses yet but it would become a good place to follow as that's where the CM brains are. If I can make some sense offer this log business ill get back to you without some more ideas.
That post: http://forum.xda-developers.com/showthread.php?p=31612608
Sent from my SGS3 i747m (Bell) on CM10 (Yesterday's Nightly) using xda premium
---------- Post added at 09:39 PM ---------- Previous post was at 09:33 PM ----------
There we go, if you go into settings > wifi > menu button > advanced their is several options about wifi timeout, power saving and sleep mode. Their is a frequency setting as well you might want to toy with. I think I stumbled upon these options a while back but never had any use for them.
Sent from my SGS3 i747m (Bell) on CM10 (Yesterday's Nightly) using xda premium
Ian1331 said:
I've been trying to get alogcat working on my phone but the log is blank no matter what I do. Either way, the main developer thread just got a post about wifi and how it's note staying connected. No responses yet but it would become a good place to follow as that's where the CM brains are. If I can make some sense offer this log business ill get back to you without some more ideas.
That post: http://forum.xda-developers.com/showthread.php?p=31612608
Sent from my SGS3 i747m (Bell) on CM10 (Yesterday's Nightly) using xda premium
---------- Post added at 09:39 PM ---------- Previous post was at 09:33 PM ----------
There we go, if you go into settings > wifi > menu button > advanced their is several options about wifi timeout, power saving and sleep mode. Their is a frequency setting as well you might want to toy with. I think I stumbled upon these options a while back but never had any use for them.
Sent from my SGS3 i747m (Bell) on CM10 (Yesterday's Nightly) using xda premium
Click to expand...
Click to collapse
None of those settings ever help me. Can anyone report if CM10 is working perfect on there rogers galaxie s3? Tomorrow is my last day to return my phone so if it's every odd phone I'll just get a replacement.
T-HO6969 said:
None of those settings ever help me. Can anyone report if CM10 is working perfect on there rogers galaxie s3? Tomorrow is my last day to return my phone so if it's every odd phone I'll just get a replacement.
Click to expand...
Click to collapse
Same problem here with wifi on Galaxy Note n7000. It started since I moved from CM9 to CM10.. Now trying every new Nightly, but with no success. Still losing wifi spot every 1min - 10minutes.
Thought if I download something, then wifi is stable, but soon after download is finished, wifi connection is dropped.
Working for me ...
T-HO6969 said:
None of those settings ever help me. Can anyone report if CM10 is working perfect on there rogers galaxie s3? Tomorrow is my last day to return my phone so if it's every odd phone I'll just get a replacement.
Click to expand...
Click to collapse
I have a Rogers S3, and am currently running CM10 NIGHTLY 20120924. Everything appears to be working well, including Wifi; however, there is the occasional (and I mean quite rare) glitch where Wifi does seem to have a bit of difficulty connecting. Again, this is extremely rare on my device, and it may simply be something unrelated to the ROM.
Peter
YES!! This has occurred for me on the stock ATT TW rom and then same thing happened on EVERY OTHER ROM I tried after that including AOKP, LiquidRom, Aristodemos....
It's annoying and I don't know what to do.
The wifi will connect and stay blue for 5 seconds then turn grey for 10 more sec and then wifi will completely disconnect and wont reconnect unless i turn wifi off and then on again. im at a complete LOSS.
anyone have any ideas?
Exchange it. Don't put it off just use titanium backup and switch your phone.
I am having issues with WiFi on CM10 also. I can use the internet like always but the signal bars will go gray sometimes then back to blue. While they are gray I can browse, usually with chrome, but youtube will not work. It is odd that some apps won't work but some will. It may be dropping and coming back but is not strong enough to stream video.
I am using CM10 10/9/12 nightly and an N600 Netgear router. I am starting to think the Netgear router might be my culprit. I have always had dropout issues with them in the past, although, my computers, 360, and PS3 have no issues. Maybe I could just make it a signal repeater and get a Linksys again.
Has anyone else had this issue, think it is the Netgear? Should I try a new router firmware like dd wrt?
Android 4.0.4 error installing cyanogen 10
hi there, I am having trouble installing Cyanogen 10 on my galaxy s3 I747m android 4.0.4
rooted and running cwm 5.5.0.5.
i get an error that says status 7. installation aborted.
Does anyone know why I'm having this error?
thank you
androidehca said:
hi there, I am having trouble installing Cyanogen 10 on my galaxy s3 I747m android 4.0.4
rooted and running cwm 5.5.0.5.
i get an error that says status 7. installation aborted.
Does anyone know why I'm having this error?
thank you
Click to expand...
Click to collapse
Because you are in the wrong thread.
And you need to redownload and wipe everything.
thacounty said:
Because you are in the wrong thread.
And you need to redownload and wipe everything.
Click to expand...
Click to collapse
my bad. I'll try to do that as soon as the website come back up to redownload the file and try it again.
thank you
androidehca said:
my bad. I'll try to do that as soon as the website come back up to redownload the file and try it again.
thank you
Click to expand...
Click to collapse
Meant that kind of silly, but yea you should just redownload, that is usually the problem. Try out Euroskanks version for now if you don't want to wait. Jellybro.
I need help finding a stable rom. I've tried a lot over the past few months, and they all have problems rendering my tablet inconvenient for use.
Before I was using a CM7 mod which was working pretty well, but then I upgraded to an ICS rom somewhere around September. That's when the performance started to drop. Then somewhere around March I upgraded to a Jelly Bean rom, and that's where the serious problems started.
At first I tried SmoothRom, but that just wouldn't install until I did some tweaks (removed an "assert" line of code). And even then, stuff in settings kept crashing. So I tried the HellFire rom, which worked but was having some serious performance problems. The launcher I was using (Apex) was slow and unresponsive at times, and various apps (browser, music player) kept crashing at times.
A few weeks later, I tried SmoothRom again, and it seems to work better. No more tweaking needed to flash it, and no more crashing in settings. But the problems were even worse. My browsers (Dolphin, Chrome) kept crashing frequently when I browse, the music player (winamp) kept stopping, and worst of all, sometimes my kindle won't wake up from sleep (I have to hold my finger on the power button to turn it off before turning it back on).
I just don't know why I keep having problems. So today I tried using the modified stock roms. The http://forum.xda-developers.com/showthread.php?t=2211872 won't even flash (something about failing). So I tried the older modaco rom. I had a problem with a launcher (Holo) where it kept saying "holo launcher stopped unexpectedly" every time I tried to run it. I tried rebooting, clearing the cache, but it still had problems. Plus I found out not a lot of apps were compatible with my gingerbread based android os, so now I'm going to give this rom a shot:
http://forum.xda-developers.com/showthread.php?t=2051331
But basically, why am I running into so many problems? Is this normal, or is there something abnormal with my kindle fire?
Do a full wipe while installing a new rom. I don't think Holo Launcher works with stock. And for the stock modded, are you sure you downloaded the main not alt zip?
Sent from a DROID Pro that is rooted and runs vanillalvl's CM7
Hmm......I use twa_priv's latest CM10.1 ROM (4-01-13) and it runs sweet. I have my Kindle set up to boot either CM7 or JB.....the CM7 ROM is sblood's November 2012 release. When I get tired of JB, I will switch to GB. There are certain apps that won't perform correctly on JB but run flawlessly on CM7.
You need to start with a truly clean wiped system and SD card partition, but please make sure you have the ability to mount the Kindle's storage from recovery to place the ROM after wiping SD. Install apps sparingly so it's easier to weed out potential culprits of malfunction......it sure is hard to figure out what is going on if you install 50 apps all at once.
And remember no OS is flaw free.....they are like human beings, unique and not perfect
There are plenty of stable enough for daily use ROMs, some faring better than others.
Sent from my Amazon Kindle Fire using xda premium
Yeah, I have TWRP and I always wipe and factory reset before flashing a ROM.
Try using an Official CM10.1 from hash ode. It seems to be the most stable out there
Sent from my Amazon Kindle Fire using xda premium
You need wipe all the cache before you install any new rom
So I've decided to start playing around with custom ROMs. I'm still pretty new to Android so maybe this is going to be stupidly simple.
Earlier today I flashed PACman Rom. Downloaded directly from the thread. I wasn't super happy with how slow it ran and a friend suggested it might be a nightly. I noticed in settings it said the release was from 09/09 so I thought he might be right. I decided to wipe it and install the most recent stable version of PAC man.
Seemed to flash just fine, but the startup was a bit odd. It didn't go through the standard stuff like syncing your google account, setting up wifi, etc. Jumped right to the home screen. At first that didn't seem like an issue. I can do that all manually. But then it flashed on screen saying AOSP keyboard couldn't launch. Obviously without being able to type at all or even open the keyboard, I can't do a whole lot to get it set up.
Tried a couple times to flash that ROM and same thing every time. Restored from my nandroid and everything worked perfectly. Decided to try CyanogenMod and got 10.2 stable release with gapps. Wiped and flashed. Same thing. Straight to the home screen, no keyboard. Every other gapp is there.
Any ideas on what I can do differently? Or what I might be doing wrong, or some way I can get this to work?
Did you flash gapps with pacman ROM?
Sent from my Galaxy Nexus
Yes I did. And I actually just figured out what it was. I was using 4.3 gapps with 4.2.2 ROMS
Merry Christmas to all!
JLM, have posted similar on your other site.
Having a problem with the BrokenPop 5.0.2 on my L900 (Sprint Note2)
I can't seem to dial out with this rom. I get popup saying 'Unfortunately, Dialer has stop"
Are others seeing this problem? Is this an rom issue or a setup issue on my end?
I don't expect a daily driver from an early alpha of this rom and do expect issues but I would hope that I can at least make phone calls, after all, the Note 2's primary function is a phone
What I have done so far.
DL and installed rom twice. Both DL check via MD5 OK
Using Philz 6.07.9 recovery
1. Backup internal sdcard to pc
2. Factory reset / Install new rom option
3. Wipe/format internal sdcard
4. Reboot recovery (selected yes to restore root notification)
5. Install rom
6. Boot rom
7. Boot into recovery
8. Flash Gapps
9. Did minor setup of things like Wifi, Google Login, Play Store, DL ES File Manager.
10. Try to make phone call using dialer (phone icon) and get 'Unfortunately, Dialer has stop"
11. DL another free dialer from Play Store.. same error message.
I'm open to suggestions on how to get this to work.
I do like what I see from my little tour around this rom, but not being able to make calls is a major issue for me even for an alpha release. For now I have fallen back to my trusty Community Rom 4.4.2 which has been rock solid for me.
Thanks
bump.... a few people have viewed this posting .. anyone else having this problem? I have since try to install once again.. had some limited success with dialer, but then problem returns. even made a nandroid of when it was working.. still my favorite early lollypop rom for the l900
I installed Broken5.0.2, ran it for 24, and found it seemed to be one of the least reliable functioning loli roms for L900. I personally am preferring the LiquidSmooth 12-23 nightly. The LS rom has overcome the wifi/screen off hotboot bug, the keyboard bug, but still needs the manual GPS fix. Right now it offers hands down the most functioning options at this particular time and the phone is semi reliable??? Lol its doesnt FC but its buggy.
My two cents ... Cheers!
I've tried LiquidSmooth 12-23 nightly also.. one thing I had issues with was I have a OTG usb drive and did not find a way to unmount it. Did you find that function anywhere in LS?.. Other issue I have is no XPOSE support right now.. and I'm not a fan of the AOSP messaging pgms. Lots of things I don't like about TW .. but they make a nice messaging pgm
I did see a semi-workaround where you click on the carrier setting and it kinda resets the capability to make calls.. kinda hokey.. but it seems to work.. Lolllypop is still very early.. and I guess these are the growing pains for being alpha testers. Hopefully over time it will get more mature. Back on 4.4.2 for now.. everything works.. the thing is huge.. over 2gb nandroids using high compression.. but hey, everything works.. Thanks for responding.