yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] LQQKS:
Try Titanium or Mybackup for your apps. Also backup in recovery (nandroid) in case it all goes wrong.

Once rooted wipe cache and dalvic, wipe system.

Then flash CM10 zip and then flash Gapps zip

Sent from my rooted, S-Off HTC Vivid 4G

running Pegasus 2.5.0a ICS 4.0.3

using XDA Premium app \o/
[Xoom Android Development] rmkilc:
The camera app hangs up when using the effects (silly faces and background) in video mode.
[Xoom Android Development] Submarine854:
Thanks for your reply. Still one question remains: can I restore the backup'ed apps with Titanium Backup after flashing CM10?

Michael

Gesendet von meinem Xoom mit Tapatalk 2
[Xoom Android Development] afpapa:
Yes, no problem. Bug be careful not to restore system apps.

Στάλθηκε από το MZ601 μου χρησιμοποιώντας Tapatalk 2
[Xoom Android Development] burgi400:
settinggs

setting auto brightnes values and push button save and use new values fc settingany one else with this problem?
[Xoom Android Development] rmkilc:
Yes. I reported this awhile ago. http://xdaforums.com/showpost.php?p=32382901&postcount=218
[Xoom Android Development] joho5:
I have always done a complete wipe in between flashes but now I have a WiFi network setup on my Xoom from work that the IT guy has to setup because its secured. If I just download the latest nightly...is it OK just to wipe the caches? Or will this eventually muck up the system? If I go this route, do I flash gapps again?

Also, if my Xoom is being backed up to Google...will it save all my WiFi settings if I do elect to wipe and install a ROM from a clean wipe?

Thanks
[Xoom Android Development] LQQKS:
If coming from a nightly, just wipe cache and dalvic.

Then flash new nightly and gapps.

All your settings will be saved

Sent from my rooted, S-Off HTC Vivid 4G

running Pegasus 2.5.0a ICS 4.0.3

using XDA Premium app \o/
[Xoom Android Development] joho5:
Thanks.... I appreciate it.
[Xoom Android Development] rmkilc:
No need to wipe anything between flashes.

---------- Post added at 03:08 PM ---------- Previous post was at 03:07 PM ----------

You shouldn't need to flash gapps, unless you wipe system.
[Xoom Android Development] LQQKS:
Oh OK, I just do it as a precaution :)

Sent from my rooted, S-Off HTC Vivid 4G

running Pegasus 2.5.0a ICS 4.0.3

using XDA Premium app \o/
[Xoom Android Development] tincbtrar:
Go to data/misc/wifi and read the wpa.supplicant.conf file - it will have the password and security type there. :)
[Xoom Android Development] thenemis:
no

is /emmc OR /sdcard /external_sd , autochoosen from cmupdater

and xoom have the second

https://github.com/CyanogenMod/andr...mmit/d56f4b6ebfd43b43ac176fe57f5928a4630ab08b
[Xoom Android Development] Darkman:
Here is the USSD MOD for every Users they needed to use USSD Codes.... for the CM10-nightly-20121104 ....

Please flash only for the appropriate ROM and Nightly Version!
[Xoom Android Development] rmkilc:
CM Updater

Here are further findings with CM Updater and the Xoom:

With a micro SD card in the Xoom, the CM Updater does not work. This is the path it sends to recovery:

Without a micro SD card in the Xoom, the CM Updater does work. This is the path it sends to recovery:
[Xoom Android Development] LQQKS:
Inside Android mine reads /sdcard but in recovery (TWRP) it reads it as /emmc which is why I can't use CyanDelta auto installer :(

as I can't find a way to change the target directory to /emmc I'm about to email the Dec.

Sent from my rooted Xoom MZ601

running CM10 JellyBean 4.1.2

using XDA Premium app \o/
[Xoom Android Development] thenemis:
this is the partition on twrp for wingray

https://raw.github.com/TeamWin/device_motorola_wingray/ics/recovery.fstab

and here the name /data/media /sdcard used by twrp

https://raw.github.com/TeamWin/device_motorola_wingray/ics/BoardConfig.mk
[Xoom Android Development] LQQKS:
Would the Everest (MZ601) be any different?

Sent from my rooted, S-Off HTC Vivid 4G

running Pegasus 2.5.0a ICS 4.0.3

using XDA Premium app \o/
[Xoom Android Development] thenemis:
https://raw.github.com/CyanogenMod/...c/com/cyanogenmod/updater/misc/Constants.java

if you have some time to try to remove / from

public static final String UPDATES_FOLDER = "/cmupdater";

and rebuild and test ...
[Xoom Android Development] z1gackly:
http://review.cyanogenmod.org/#/c/25931/

It doesn't fix the updater not working on the Xoom, but it makes the code more consistent.
[Xoom Android Development] thenemis:
wingray or everest ?

bacause there is 2 different recovery.fstab

https://raw.github.com/CyanogenMod/android_device_moto_wingray/jellybean/recovery.fstab

https://raw.github.com/CyanogenMod/android_device_moto_everest/jellybean/recovery.fstab
[Xoom Android Development] xgrzenio:
hm.. in cm-10-20121105-NIGHTLY-everest.zip is small bug ... download only 53 mb. on computer on xoom
[Xoom Android Development] LQQKS:
I didn't get a nightly yesterday

Sent from my rooted, S-Off HTC Vivid 4G

running Pegasus 2.5.0a ICS 4.0.3

using XDA Premium app \o/
[Xoom Android Development] thenemis:
me too, so i DL from jenkins ;) http://jenkins.cyanogenmod.com/job/android/

EDIT: opps they have some server problem :(
[Xoom Android Development] aR_ChRiS:
http://xdaforums.com/showthread.php?t=717874

Although obviously our xoom does not use the same nand chip as the G1, but I think this is interesting for Team Rouge to look into...
[Xoom Android Development] tb-killa:
We have enough storage at our device to get more than one rom save but First of all we have to figure out how to Partition our Nand so we could got higher space for System Partition and also creating another Partition for another rom. Hope we could figure these final fault !
[Xoom Android Development] sundials:
Since flashing cm 10 on my Everest Xoom I don't have the camera or gallery apps. I have tried different gapp packages but none fix the problem. Any one have a solution?
[Xoom Android Development] uzi2:
This will help explain why not....

http://xdaforums.com/showpost.php?p=33349961&postcount=47
[Xoom Android Development] z1gackly:
Let's just quote that to make it crystal clear:

Do not attempt this at home!
[Xoom Android Development] burgi400:
incompatible apps

Hl,

the app öffi and some others are not compatible with this rom. why?

on eos rom there is no problem to install the app
[Xoom Android Development] pikesmatrix:
I had the exact same problem with the same app, so what I did was wiped system and cache then flashed cm10 again. All sorted now
[Xoom Android Development] lynxboy:
This ROM just gets better and better. The smoothest Xoom experience available. Eagerly anticipating the first 'stable' release!

Regards.
[Xoom Android Development] skylenorman:
I'm using the 10112012 Gapps, but can't seem to find the place where I can download offline voice recognition. It's not in the same place my CM10 phone has is. Were these moved, or are they not available for tablets?
[Xoom Android Development] BatGnat:
Has there been an update on this? This is all that is holding me back from moving to CM10.
[Xoom Android Development] nadiros:
Eh - It works for me with the EOS gapps, however they are still 4.1.1 based. I use the same gapps as you but placed in the EOS package and

voice recognition works :cyclops:
[Xoom Android Development] alex_72gr:
Hi I have a xoom euro 3g and I have been using this rom for a week now. It is quite fast and nice, and I dont have any major issues. There is one thing thought. Adfree doesn t seem to be working. Up to now I never had any problems with adfree. Does anyone else have the same problem?
[Xoom Android Development] uzi2:
Adfree can only be as good as it's latest hosts file. Personally, I don't use it. Adignore is much better and it's all in the mind ;)
[Xoom Android Development] z1gackly:
Can't ignore away cookies collecting data about you. I'll take the hosts file solution every time because it does block a lot.
[Xoom Android Development] Sardo Numspa:
I had issues with adfree, switched to AdAway and have been happy with it.
[Xoom Android Development] LQQKS:
I've been using AdAway and its awesome

Sent from my rooted, S-Off HTC Vivid 4G

running Pegasus 2.5.0a ICS 4.0.3

using XDA Premium app \o/
[Xoom Android Development] LQQKS:
With 1112 update, 3G doesn't work...:(

Sent from my rooted Xoom MZ601

running CM10 JellyBean 4.1.2

using XDA Premium app \o/
[Xoom Android Development] mermigas:
Stable CM 10 is out !!
[Xoom Android Development] spy0r:
Yay :cowboy:
[Xoom Android Development] mykar3z99:
is it for Motorola Xoom WiFi+3G (MZ601)?
[Xoom Android Development] felipevsw:
No, wi-fi only (wingray/MZ604).
[Xoom Android Development] Gynlemon:
Yes!! ;)

http://get.cm/?device=everest
[Xoom Android Development] lynxboy:
Just saw the news and thought I'd come and say thanks to all those working on CM10 behind the scenes.

The Xoom's best ROM just got better.

Regards.
[Xoom Android Development] rmkilc:
My wingray is not waking up very reliably now. When I push the power button after the device has been sleeping for awhile, the screen does not turn on. I have to force a reboot with volume-up + power button. Anyone else experiencing this?
[Xoom Android Development] Gynlemon:
+1

with everest, it happened to me a couple of times already .. with the version of today still do not know ..
[Xoom Android Development] LQQKS:
Awesome news \o/

Will there be more nightlies or are the Team giving their eyes a well deserved break?

Sent from my rooted Xoom MZ601

running CM10 JellyBean 4.1.2

using XDA Premium app \o/
[Xoom Android Development] duk3r:
Just flashed the final CM10 on my Everest. I have only one problem. The home button in the center doesn't take me back to my home screen. In order to go there I have to press the back button many times. Any clues?
[Xoom Android Development] Steady Hawkin:
Lots of stuff going on rite now but I wanted to give a few quick updates. We are aware of a few lingering issues with current builds that were working on. I personally don't put to much emphasis on build names (ex. Stable, M, etc). We are however going to to finish pushing the remaining stable builds soon. Most importantly, the Xoom has reached EOL in terms of AOSP support. What does this mean? For now it means we are still going to move forward with building and moving onto CM10.1, we may just have a few more hurdles then we would like. As always, your patience and support it appreciated and we look forward to 10.1. Long live the Xoom!
[Xoom Android Development] Sardo Numspa:
Nooooo!!! :)

long live the Xoom is right, i still love this thing, even if it was a bit before its time and never got the appreciation it should have.

thanks for all the support Steady.
[Xoom Android Development] logitechor:
I use the Xoom everyday and really appreciate the developers support. What set the Xoom a part was both the updates and the hardware options. Their maybe better spec'd machines now but is their another tablet that has all the features of the Xoom. Not many for sure.
[Xoom Android Development] felipevsw:
I considered CM10 nightlies stable since a very long time.

I did install every single nightly every single day, and it only got better and better!

Looking forward to CM10.1!
[Xoom Android Development] themichael:
What gapps have people been using with the nightlies? I heard the stock cm 10 gapps causes memory issues.
[Xoom Android Development] aR_ChRiS:
I would recommend the teameos gapps package since they use symlink to link the apps into the data partition and you should have a couple of MBs left in your system after a clean flash.
[Xoom Android Development] weldontimbo:
Been seeing the same problem. Seems like it happens most often when my tablet has been asleep for a while and unplugged. I will try get a logcat if I can next time to see if that reveals anything.
[Xoom Android Development] taliesin1077:
I'm having the same issue, but I just installed it yesterday afternoon, so I don't have a lot of experience with it.

One thing I have noticed is that when I pair my Hipstreet bluetooth keyboard up to the tablet, I get a "Select Keyboard Layout" notification. When I tap it, I get a message "Unfortunately, settings has stopped." I later got the same thing when I was attempting to configure Thumb Keyboard for use. The Bluetooth error is on a clean install, fresh wipe of Cache, Dalvik, and User Data with no apps restored.
[Xoom Android Development] rubber guard:
forgive me for not reading the whole thread, but how can we know when 4.2 is implemented into this ROM.

is CM 10 inclusive of 4.2? only 4.1.2?

TIA
[Xoom Android Development] taliesin1077:
The CM10 stable that has been posted is 4.1.2.
[Xoom Android Development] LQQKS:
I imagine the devs have a copy of 4.2 from Nexus and fingers are furiously flying across keyboards as we speak

Sent from my rooted, S-Off HTC Vivid 4G

running Pegasus 2.5.0a ICS 4.0.3

using XDA Premium app \o/
[Xoom Android Development] cviniciusm:
Hello,

On Cyanogenmod site, Android 4.2 will be CM 10.1.

Just follow Cyanogenmod on Twitter and/or on Google+.

Enviado de meu Motorola MZ605 (Android 4.1.2 - CM10) usando o Tapatalk 2.
[Xoom Android Development] rcobourn:
At some point in one of the recent builds, Google Talk vanished, and reflashing the gapps won't bring it back. Anyone else?
[Xoom Android Development] urushiol:
I think this may be due to the fact that many of the latest CM builds for the stingray don't actually leave enough room in the system partition for the gapps. Today I downloaded CM10(official, stable) for the stingray, wiped and flashed just the rom, no gapps. I had something like 23mb of free space left in my system partition. In order to flash the gapps, first I had to remove faceunlock from the gapps zip. Then I had to move about 6 apps from my system partition that came with CM, to my data partition(the launcher app, keyboard, clock, cmwallpaper, and a few others), then I deleted the ringtones and sample movies and all live wall papers. This got me up to around 90mb or 95mb free. Then I was able to flash the 4.1.2 gapps(with the aforementioned removed faceunlock) and I had a few mb of free space left after adding the gapps.

In the past, I tested flashing the gapps zip when there was not actually enough space for it to fit and found that for some reason our recovers don't tell us that it wont fit, they just flash it until its full and the rest just doesn't get put in. In your case rcobourn, i'd say there just isn't room for talk.apk. Check your /system, I bet its dead full.

I really wish the CM devs would look at this issue closer, many of the apps could be safely moved to the data partition(of course you would lose them if you accidentally uninstalled them), however if the don't do something the Xoom will no longer be viable for development, as the newer versions of android simply will not fit! Our System partition is only about 250mb, our data part is 32gb, lefts find a way to use it!!!
[Xoom Android Development] logitechor:
I have become a bit more adventurous in the system folder too. As a result I have most of 4.2 apps running successfully. Including the camera app. But I have less in the system. I have seen posts by the developers indicating that symlinks and other techniques work but some preferred not to do this. Me I just have fun knowing I can go back to recovery and start over.
[Xoom Android Development] aR_ChRiS:
I think symlinks are quite neat but I think if the cm team decides to move non-hardware related appear to the data partition would be a much better solution for devices which have limited space in the system partition.

Sent from my nexus prime (maguro)
[Xoom Android Development] Alxoom33:
I'm running 4.2 gapps on CM10. Disabled the 4.2 keyboard due to FC notifications and restored my thumb keyboard with Ti backup. Needed to reload my corporate email info for calender and email Widgets to work properly. Everything seems to work except the Google play store. Tried to reload from Ti backup but could not load, probably not compatible with 4.2. Does anyone have a playstore apk or zip file that will work?

Thanks

Btw 4.2 camera and gallery seem to be working fine.
[Xoom Android Development] marcuso:
Hi,

as most people using CM on the Xoom will be discussing here (instead of the Q&A section) I want to ask if anybody using recent CM nightly or 10-stable on xoom also has issues with certain apps shown as not beeing compatible in play-store ? (such as google goggles for example)

http://xdaforums.com/showthread.php?t=1991755

http://code.google.com/p/cyanogenmod/issues/detail?id=6621

If so - you can star/confirm in the bug I filed at CM ... and maybe somebody can help investigating ... seems build.prop is not the issue (at least another user says there are no relevant changes compared to a nightly that still works). But that is of course strange .. what esle could be the problem here ? any ideas ?

Thx
[Xoom Android Development] mermigas:
Android 4.2 Play Store:

Phonesky.apk

Updated to 3.9.17

Get it here http://www.mediafire.com/?h5610yb0f664lqg

Just push it to system / app with the right permissions and reboot.

For keyboard you can flash this 4.2 AOSP Keyboard with swipe like input method , taken from here

http://xdaforums.com/showthread.php?t=1986627

By the way I am runninig with latest EOS nightly everest with 4.2 gapps since I had quite a lot FC with CM 10

Which 4.2 gapps you are using with CM10 ?
[Xoom Android Development] cviniciusm:
Hello,

I am unable to install foursquare because Google Play said this app is incompatible with my tablet.

I am using CM 10 Stable.

Before that, I was on Team Eos 3 Stable and no issue with apps.

P.S.: I observed GPS is not working well as on Team Eos 3 Stable.

Enviado de meu A953 usando o Tapatalk 2
[Xoom Android Development] thegreatwall88:
I jist installed cm10 stable and my 4g stop working. Anyone know how to solve this? Thanks
[Xoom Android Development] marcuso:
Unfortunately someone from CM-Team trashed my bug-report just with the comment "NoLogAttached" ... I did not see anything helpful in logcat .. so i really don´t know what i should post as a log here. Can anybody help ?

Obviously this is really an issue as several other people have confirmed the very same problem.

EDIT: I have now attached a logcat ... actually found the correct part now ;) .. I hope the issue gets reopened .. otherwise i will open another one.
[Xoom Android Development] Alxoom33:
Thanks, I am using 4.2 apps posted on this thread a week or so ago. Don't remember the source. Thanks for your help, I'll try flashing the Everett 4.2 gapps EOS I am using wingray.
[Xoom Android Development] Alxoom33:
Tried installing phonsky.apk from system/apps changed permissions to Owner x x _;

Group x_ _; Group x _ _. Did not parse when I tried to install.??
[Xoom Android Development] LQQKS:
Try emailing to yourself via gmail.

It will have an install option

easiest way to install apk's :)

Sent from my rooted, S-Off HTC Vivid 4G

running Pegasus 2.5.0a ICS 4.0.3

using XDA Premium app \o/
[Xoom Android Development] Alxoom33:
Had a bad download, redownloaded and worked. Thanks :)
[Xoom Android Development] Alxoom33:
This is the 4.2 gapps i'm using,

http://xdaforums.com/showthread.php?t=1965290

---------- Post added at 07:29 AM ---------- Previous post was at 07:25 AM ----------

See response above
[Xoom Android Development] lynxboy:
+1 with the incompatible apps issue in Play Store. Real shame as everything else is perfect. Is this a Xoom specific bug, or across multiple devices? Will try messing with the build.prop a bit later.

Regards.
[Xoom Android Development] Alxoom33:
Yea thanks, although the above playstore APK installed OK, still getting fc's with the playstore.
[Xoom Android Development] themichael:
Anyone get voice search fc on the stable release?
[Xoom Android Development] rocky12345678900:
when?

When will you merge 4.2 into cm source?
[Xoom Android Development] spy0r:
cm-10-20121117-NIGHTLY seems to be out, but down...
[Xoom Android Development] waz675:
Coming from ICS to teamEOS JB ROM dozens of people didn't full wipe and back then the majority of people reporting issues came from people full wiping, I recall it vividly. So not always a full wipe is needed, especially on 'new' ROMs it seems, sometimes it can be detrimental.
[Xoom Android Development] nadiros:
IMHO this concept is incorrect. (Above)

It may work out in some cases where a function or feature is broken in a newer update which worked previously, and then by not wiping you retain the old behavior through the update process....
[Xoom Android Development] waz675:
Stuff concept, I was talking possibilities and actual reality(for context of the scenario I was quoting about). I never said people who had broken rom installs moving to JB improved it automagically. I said several people and as far as I remember, the only people who had issues initially post upgrade to teameos JB ROM from ICS were people who stated they full wiped. People stating they didn't have an issue also stated they didn't full wipe. (Of course people full wipes had sucess but not all as I saw). Could have forgotten a couple minor incidents due to the truckload of pain meds I'm on these days but it struck a chord with me seeing full wiping installs sometimes had problems and not seeing other installs have these problems.

While I'm not saying this is the rule, just stating observations from that particular ROM after the first day(s) it came out and people's reports on it. My concept would be do a nandroid backup, upgrade (however wiping procedure one wants), then see what works to have a 'good' upgrade.

And from 22 years as a Unix admin (and forced windows at times ugh) and coding my first program either 79 or 80, I know 'best practice' doesn't always work, computer OSes are complex environments, 'things happen' is a good motto ;)
[Xoom Android Development] z1gackly:
If a ROM works better without a full wipe then it's a poorly formed ROM, full stop, because it means it was missing something it needed.

I'm not disputing the anecdotal evidence you present, but I believe other factors must have been at play in those instances, and can assure you from personal experience that I have never once experienced a problem installing an EOS ROM after a full wipe.

It was my habit to do a full wipe and install on each new EOS nightly for the first few months of Jellybean releases, as I was testing the ROM with benchmarks against other JB ROMs.

So that is my anecdotal evidence. I've installed every single EOS JB ROM up until the last couple after a full wipe and it's always been fine. I have observed problems moving from one ROM to another without a full wipe however, and this is to be expected because of the possibility of incompatible data artefacts.

Not looking for an argument, just passing on my experience and opinion.
[Xoom Android Development] waz675:
i can't see any basis of an argument, it's just 2 people presenting their views of what they have experienced regarding the ROMs of a bloody small sample set (like .000000001% of the amount of upgrades people have done all up heh)

Plus all I was getting at that no one way of upgrading always guarantees a complete error free upgrade experience so be prepared for anything, well actually hopefully a nandroid backup will guarantee that coming across an issue means we can restore it and explore a different path (hardware failure non withstanding). Just mentioned that 'full wipe should be done to fix issues etc' isn't always right, mainly just from the posts I saw that I mentioned. It may have been a badly formed ROM in those initial 2 or 3 releases where I recall said problems being mentioned with people who did full wipes (may have been people having speed/lag issues for the main?)

And even if you were gunning for an argument I'd just laugh it off, I don't have any input on the coding for XOOM ROMs, so nothing worries me about a particular thing being right or wrong :D

Well enough off topic crap from me, my wife needs attention since our kids have gone to bed. Should be fun checking out the CM10 nightlies and TEAMEOS releases, variety is great. Enjoy!!
[Xoom Android Development] z1gackly:
You're dead right there :)