Hello,
i have flashed CM10.1 for Xoom.
I have a Question about Gapps.
If there is an Update for CM10.1 Available must i Flash Gapps again after Update?
Greets
I run 10.1 as well and the gapps reflash will depend. Because sometimes i dont have to reflash it but other times i have to.
I could not figure it out yet, whats causing this problems.
Sent from my Galaxy Nexus using XDA Premium App
I am running CM 10.1 latest nightly on my xoom. I downloaded the "EOS gapp pack for xoom only" to free up some space on system rom. I was having same problem with losing my gapp pack everytime I flashed a new nightly. I downloaded Cyan Delta app and it gives you the option of flashing newest nightly delta file along with your gapp pack or any other zip file all at the same time. Very nice app. Now when I flash my newest nightly it also flashes the gapp pack and I'm good to go. Running CM 10.1 JB 4.2.1 on Xoom wifi. Latest "EOS gapps for xoom only. My system recovery is TWRP 2.3.3.0. Hope this helps.
Sent from my Xoom using Tapatalk HD
---------- Post added at 03:53 PM ---------- Previous post was at 03:43 PM ----------
By the way CM 10.1 has auto updater in the rom. Go to settings>about tablet>CyanogenMod updates. The rest is pretty easy from there. Have a good one.
Sent from my Xoom using Tapatalk HD
i do it now so ...
1. flash newest nightly over cm auto updater
2. if its done i flash the eos gapps in my recovery again
Yes. Just flash the gapps again and you should be good to go. Like I said in my previous post, Cyan Delta will do both in one shot.
Sent from my Xoom using Tapatalk HD
Related
After flashing latest CM 10.1 nightly (20130311) my tablet booted up but I got the message " Unfortunately System UI has stopped working". Rebooted into twrp recovery and flashed CM 10.1 20130310 nightly. Everything worked fine as usual. Tried flashing CyanDelta 20130311 update file and got the same message. Flashed back to CM 10.1 20130310 nightly again and everything was fine. Has anyone experienced this problem with the CM 10.1 20130311 nightly on Xoom wifi? I have flashed CM 10.1 20130311 nightly on both my GNex and my Nex 7 and have had no problems. Has anyone heard of any bugs with the Xoom CM 10.1 nightly (wingray)? Thanks.
Sent from my Xoom using Tapatalk HD
I had the exact same issue last night. I chalked it up to user error since I had not upgraded CM from within the settings before. I am new to CM and didn't have this option on the competing ROM I used.
kevk60 said:
After flashing latest CM 10.1 nightly (20130311) my tablet booted up but I got the message " Unfortunately System UI has stopped working". Rebooted into twrp recovery and flashed CM 10.1 20130310 nightly. Everything worked fine as usual. Tried flashing CyanDelta 20130311 update file and got the same message. Flashed back to CM 10.1 20130310 nightly again and everything was fine. Has anyone experienced this problem with the CM 10.1 20130311 nightly on Xoom wifi? I have flashed CM 10.1 20130311 nightly on both my GNex and my Nex 7 and have had no problems. Has anyone heard of any bugs with the Xoom CM 10.1 nightly (wingray)? Thanks.
Sent from my Xoom using Tapatalk HD
Click to expand...
Click to collapse
Just wanted to report the same. Yesterday build did not work so I had installed 20130310 build and it is ok although I did not check all the apps.
RoryPG said:
I had the exact same issue last night. I chalked it up to user error since I had not upgraded CM from within the settings before. I am new to CM and didn't have this option on the competing ROM I used.
Click to expand...
Click to collapse
sashykanth said:
Just wanted to report the same. Yesterday build did not work so I had installed 20130310 build and it is ok although I did not check all the apps.
Click to expand...
Click to collapse
So far all my apps seem to be working with cm10.1 20130310 nightly.
Sent from my Xoom using Tapatalk HD
gapps won't flash after reflashing older nightly
kevk60 said:
After flashing latest CM 10.1 nightly (20130311) my tablet booted up but I got the message " Unfortunately System UI has stopped working". Rebooted into twrp recovery and flashed CM 10.1 20130310 nightly. Everything worked fine as usual. Tried flashing CyanDelta 20130311 update file and got the same message. Flashed back to CM 10.1 20130310 nightly again and everything was fine. Has anyone experienced this problem with the CM 10.1 20130311 nightly on Xoom wifi? I have flashed CM 10.1 20130311 nightly on both my GNex and my Nex 7 and have had no problems. Has anyone heard of any bugs with the Xoom CM 10.1 nightly (wingray)? Thanks.
Sent from my Xoom using Tapatalk HD
Click to expand...
Click to collapse
I had the same exact issue with my Xoom. I reflashed an older nightly and it's working again but now I can't get Gapps to flash properly. Every time it loads no gapps....????
I have tried reflashing the latest gapps 3 times now.
Anyone else have this issue or have Any suggestions? Running twrp if it matters but thinking of switching to CWM to try flashing gapps to see if it will take.
I use the team eos gapp pack for Xoom only. When I tried using other gapp packs my system ROM would be full and I could not update supersu. When I use the team eos for Xoom only gapps I found that I have about 30 mb left on my system ROM. My supersu was able to update then. I am using twrp 2.4.3.0 on my Xoom. Am running cm 10.1 20130310 and will stay there until a fix has been made. Do not know if this will help you, just wanted to let you know what has helped me. Are you wiping cache and dalvik before flashing gapps? I'm taking it you are flashing a previous build over the newest nightly.
Sent from my Nexus 7 using Tapatalk HD
kevk60 said:
I use the team eos gapp pack for Xoom only. When I tried using other gapp packs my system ROM would be full and I could not update supersu. When I use the team eos for Xoom only gapps I found that I have about 30 mb left on my system ROM. My supersu was able to update then. I am using twrp 2.4.3.0 on my Xoom. Am running cm 10.1 20130310 and will stay there until a fix has been made. Do not know if this will help you, just wanted to let you know what has helped me. Are you wiping cache and dalvik before flashing gapps? I'm taking it you are flashing a previous build over the newest nightly.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I did wipe both dalvik and cache before flashing gapps. I was using the gapps 20130301 so it could be that or maybe it's an older version of twrp that's causing the issue because I think I'm on 2.4.1.0.
I saw in another thread that I just read someone else was using a different gapps the gapps unified 20130220. I was thinking of giving that a try but I will try the one you recommended first as we both had the same issue above. I will also try flashing the new twrp to see if that's it as well.
Thanks I'll post back up later whether it worked or not.
If you have goo manager you could just update twrp from there.
Sent from my Xoom using Tapatalk HD
Looks like system ui bug issue has been fixed in the newest cm 10.1 nightly (20130314). Thanks to the devs.
Sent from my Xoom using Tapatalk HD
I have used this rom for several days but i don't why my battery keeps getting drained fast, even if it is on standby mode. However today i installed the nightlies rom but i don't what the difference is between the nightlies rom and a release rom can anybody help a new guys out??? Thanks
Hello,
Nightlies are unreleased versions, still under beta (devs) testing. While release versions are stable ones released to public and claimed to have bug fixes.
Sent from my Desire S using xda app-developers app
---------- Post added at 03:22 AM ---------- Previous post was at 03:17 AM ----------
ThehTCguy2 said:
I have used this rom for several days but i don't why my battery keeps getting drained fast, even if it is on standby mode. However today i installed the nightlies rom but i don't what the difference is between the nightlies rom and a release rom can anybody help a new guys out??? Thanks
Click to expand...
Click to collapse
Hello ThehTCguy2,
Nightlies are unreleased versions, still under beta (devs) testing. While release versions are stable ones released to public and claimed to have bug fixes.
Sent from my Desire S using xda app-developers app
Problems with PAC Man v23 rom installation
i have flashed the given kernel in the rom which i have downloaded from the forum.
i have 4ext latest version installed and even have the latest rom with me.
i followed all the given procedures but i get the kernel flashed correctly and then rom also gets installed using 4ext but after that
when ever i reboot the phone gets stuck in the HTC screen.
i can't do anything from that point.
i remove the battery and then again boot into the 4ext recovery to install my old SVHD rom and flash its kernel and use it.
i want to use Pac-Man rom v23...pls help...
saki2rules said:
i have flashed the given kernel in the rom which i have downloaded from the forum.
i have 4ext latest version installed and even have the latest rom with me.
i followed all the given procedures but i get the kernel flashed correctly and then rom also gets installed using 4ext but after that
when ever i reboot the phone gets stuck in the HTC screen.
i can't do anything from that point.
i remove the battery and then again boot into the 4ext recovery to install my old SVHD rom and flash its kernel and use it.
i want to use Pac-Man rom v23...pls help...
Click to expand...
Click to collapse
Do you know which panel type you have? Check the thread in the general section about non-sony panels
This thread:
http://forum.xda-developers.com/showthread.php?t=1943524
ishahxeb said:
Hello,
Nightlies are unreleased versions, still under beta (devs) testing. While release versions are stable ones released to public and claimed to have bug fixes.
Sent from my Desire S using xda app-developers app
---------- Post added at 03:22 AM ---------- Previous post was at 03:17 AM ----------
Hello ThehTCguy2,
Nightlies are unreleased versions, still under beta (devs) testing. While release versions are stable ones released to public and claimed to have bug fixes.
Sent from my Desire S using xda app-developers app
Click to expand...
Click to collapse
Thank You very much
OK so I rooted my sprint galaxy s3, and installed cynagenmod with the current gaaps(at the time).
I have upgraded cynagenmod several times through
>settings>about phone>CynagenMod updates
At one point I stopped running cm updates because goomanger prompted me of a new version of gaaps. I was not sure if I needed the current gaaps to also update to a newer release of cynagenmod.
I am currently running
10.1-20130304-EXPEREMENTAL-d2spr-M2
I would like to upgrade to
10.1.2 (stable build)
I have TWRP as my recovery,
Can I just flash both the upgrade for cm and gaaps and not have to reset my phone?
I am not sure if I need to do a full fresh install, because I recall various upgrades making changes to the boot partition.
So I guess I am looking for the proper procedure to upgrade/update cm and gaaps.
When a fresh install is necessary, and the order in which gaaps needs to be installed..., before? simultaneously? Or after?
thanks
Sent from my SPH-L710 using xda app-developers app
Bump..
Sent from my SPH-L710 using xda premium
proper procedure sphl710 cm update
pm me if u need a walk through
I've recently installed CM 10.2 and while I do like it much more than TW there is an issue with bluetooth audio playback that is a deal breaker for me. Before CM I was running the latest version of CleamROM (a touchwiz ROM) with lean kernel. I made a backup before I updated to CM and now I'm looking to go back to that backup.
My question is this: is there anything special I would have to do to go from AOSP to TW? Should it be as simple as restoring the backup or is there anything else I should have to do? Do I have to be careful with the kernels? Right now I have the latest AOSP Lean Kernel, when I was on TW I had the TW Lean Kernel? Will there be an issue when I restore the backup or will it restore the old kernel I was using as well?
Thank you!
If you would like to continue trying CM and don't mind using 4.2.2, the latest CM 10.1 stable build has working bluetooth. I'm using the build now and it runs like a champ.
Sent from my SCH-I535 using XDA Premium 4 mobile app
skytbest said:
I've recently installed CM 10.2 and while I do like it much more than TW there is an issue with bluetooth audio playback that is a deal breaker for me. Before CM I was running the latest version of CleamROM (a touchwiz ROM) with lean kernel. I made a backup before I updated to CM and now I'm looking to go back to that backup.
My question is this: is there anything special I would have to do to go from AOSP to TW? Should it be as simple as restoring the backup or is there anything else I should have to do? Do I have to be careful with the kernels? Right now I have the latest AOSP Lean Kernel, when I was on TW I had the TW Lean Kernel? Will there be an issue when I restore the backup or will it restore the old kernel I was using as well?
Thank you!
Click to expand...
Click to collapse
I am unable to install a new rom after having gone down the cyanogenmod 10.2 route, Did you ever find a solution to your problem? Please do share if you have had any luck.
deewan a16 said:
I am unable to install a new rom after having gone down the cyanogenmod 10.2 route, Did you ever find a solution to your problem? Please do share if you have had any luck.
Click to expand...
Click to collapse
What do you mean? What have you tried?
deewan a16 said:
I am unable to install a new rom after having gone down the cyanogenmod 10.2 route, Did you ever find a solution to your problem? Please do share if you have had any luck.
Click to expand...
Click to collapse
I was able to factory reset/wipe cache and then install another ROM no problem. I'm not sure why you are not able.
skytbest said:
What do you mean? What have you tried?
Click to expand...
Click to collapse
I have tried factory resetting, wiping cache, delvik cache. I can install aosp ROMs and I can restore tw ROMs I had backed up but I can not install a new tw ROM.
Sent from my SCH-I535 using XDA Premium 4 mobile app
---------- Post added at 07:12 PM ---------- Previous post was at 06:15 PM ----------
I just had to turn off the signature verification in TWRP settings. Kind of feel silly
Sent from my SCH-I535 using XDA Premium 4 mobile app
I was thinking of flashing the cyanogenmod on the n8010 but i read that only n8013 and n8000 are supported which is kind of confusing because i also read that the n8020 can be updated to 4.4.2 with CM. What do I do now?
N8013 is actually N80XX & it works perfectly on the N8010, we will likely be stuck with CM10.2 as the hardware is getting old and there are no maintainers at CM for the device.
Sent from my GT-N8013 using Tapatalk
benpaddlejones said:
N8013 is actually N80XX & it works perfectly on the N8010, we will likely be stuck with CM10.2 as the hardware is getting old and there are no maintainers at CM for the device.
Sent from my GT-N8013 using Tapatalk
Click to expand...
Click to collapse
Are you using CM? Which is your android version?
Thanks.
I have a N8010 running latest CM nightly http://download.cyanogenmod.org/?device=n8013 which is Android 4.3
Ben
Sent from my SGP311 using Tapatalk
benpaddlejones said:
I have a N8010 running latest CM nightly http://download.cyanogenmod.org/?device=n8013 which is Android 4.3
Ben
Sent from my SGP311 using Tapatalk
Click to expand...
Click to collapse
Would you mind explaining to me what nightly is? I am wondering whether I should flash and try the CM. Would you recommend me doing it?
I mostly wanted to flash it because of the comments saying they always script the latest OS version on all devices (as now I am stuck at 4.1.2).
Again thank you
Oh i just read what nightly means. The most unstable version the CM offers and the only one they offer for the note 10.1.
Nightly means it is the cutting edge version, it may have minor bugs ( only sometimes fixed by flashing yesterdays version. Becuase CM has moved on 10.2 is extremely stable with only language updates. Install the latest nightly and unless you want the latest Russian settings don't bother upgrading and you'll be on Android 4.3 Note you do lose some samsung features such as multi windows s pen etc.
I want latest Android and need IP tables so Incandescent authenticate against a proxy so nonchoice but CM.
Unless you need S Pen or Multiwindows don't just flash away.
Ben
Sent from my SGP311 using Tapatalk
---------- Post added at 11:37 AM ---------- Previous post was at 11:36 AM ----------
Tip read full documentation on CM and the CM 10.1 thread below, its how I learnt everying I know about CM
Sent from my SGP311 using Tapatalk
benpaddlejones said:
Nightly means it is the cutting edge version, it may have minor bugs ( only sometimes fixed by flashing yesterdays version. Becuase CM has moved on 10.2 is extremely stable with only language updates. Install the latest nightly and unless you want the latest Russian settings don't bother upgrading and you'll be on Android 4.3 Note you do lose some samsung features such as multi windows s pen etc.
I want latest Android and need IP tables so Incandescent authenticate against a proxy so nonchoice but CM.
Unless you need S Pen or Multiwindows don't just flash away.
Ben
Sent from my SGP311 using Tapatalk
---------- Post added at 11:37 AM ---------- Previous post was at 11:36 AM ----------
Tip read full documentation on CM and the CM 10.1 thread below, its how I learnt everying I know about CM
Sent from my SGP311 using Tapatalk
Click to expand...
Click to collapse
Alright, that was pretty much the answer I needed. Thank you Ben.
S-Pen actually DOES work on CM 10.1, quite well. I use it with Papyrus app and it has the featurest like pressure and button support.