yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] jph1282:
Anyone have any problems with netflix seems like it does not play well it plays good at first then starts to stutter and then force close.
[Xoom Android Development] Peterpaulmarie:
I´m using this ROM several days without any problems. No FC/reboots. GREAT!

One thing: I´m missing the charging light
[Xoom Android Development] dreamcwli:
It will be added in future release.
[Xoom Android Development] archaen:
I don´t have any issue with Netflix. Already watched 2 movies and it works perfect.

Great ROM, and i especially like the new user switching.
[Xoom Android Development] PearlMikeJam:
Is the camera suppose to be working? I get all green images.
[Xoom Android Development] dreamcwli:
It should be working. Can you try to stop and clear data on camera app?
[Xoom Android Development] PearlMikeJam:
Well duh! I should have know to try that. Thanks! I am loving the ROM.
[Xoom Android Development] dreamcwli:
Quick toggles for tablet UI is added (currently not configurable) but I want to publish next release after making them available on phone UI (fixing shortcut-only tiles) so it may take some time. It's really good to see feedbacks here and know my ROM really help some users with Xoom.
[Xoom Android Development] Peterpaulmarie:
In my quick toogles I do not have a switch for WLAN and bluetooth isn't inside.
[Xoom Android Development] dreamcwli:
They are available in next release.
[Xoom Android Development] PearlMikeJam:
This is great! Now I can get rid of SwitchPro. I love the ROM because it is very minimal and similar to what Google would have pushed to the device if it were supported.
[Xoom Android Development] dreamcwli:
ROM and legacy hwcomposer support updated. See first post for more details. The new implementation for legacy hwcomposer support is better than previous one but still cause random reboots occasionally so use at your own risk.
[Xoom Android Development] Peterpaulmarie:
I've updated with a full wipe because I had problems with the keyboard. Now everything works fine.

Will wait for charging light maybe next time?

Thanks a lot!!!!!
[Xoom Android Development] dreamcwli:
Enabling charging light is easy, but after testing for a while I felt system performance is reduced. I will include it if there is no significant performance issue.
[Xoom Android Development] PearlMikeJam:
Do you recommend a full wipe or can this be a flash over?
[Xoom Android Development] dreamcwli:
I flashed over previous one and wipe cache & dalvik.
[Xoom Android Development] Winesnob:
Seeing "unfortunately clock has stopped" pop up frequently. Did a cache and dalvik wipe prior to installing the latest update.
[Xoom Android Development] phishfi:
So is it possible to get the soft keys back to the left side of the screen? On a 10" display I find it wildly inconvenient to move a hand all the way to the center of the screen just to press the back button, especially when I'm reading feeds and stories on Google currents,where there's no other back button option..

Thanks for the help
[Xoom Android Development] dreamcwli:
Can you upload logcat with this error? I didn't get the error so I can't find what's going wrong there. Also can you try to stop and clear data on clock app?
[Xoom Android Development] dreamcwli:
You can change to use system bar (tablet UI used in previous version) in developer options.
[Xoom Android Development] phishfi:
Where is the developer options menu? I remember it being near the bottom of the settings list on other ROMs, but I can't find it on this one...
[Xoom Android Development] dreamcwli:
It is hidden by default in Android 4.2. You have to go to about tablet and click build number 7 times then developer options tab is shown.

Looks like we should have a Q&A thread for changes in Android 4.2 to prevent duplicate questions since this thread is too long to find the answer.
[Xoom Android Development] scooby1024:
Your Rom is awesome. Manufacturers just make the device, devs like you MAKE the device. Thanks!
[Xoom Android Development] runandhide05:
he is talking about this,

http://www.youtube.com/watch?v=3WjrJpCdbvE&feature=plcp

and that still should get you working for gnow if you havent follow the steps in the video and should get it working for you
[Xoom Android Development] logitechor:
alpha release

Runandhide you are everywhere. Thank you for what you do.

I have been using the ROM foremost of the day. Have not installed my software. Working well.

Except I am having troubles with Photosphere. Am going to try a couple of things. Reinstall first. Thank you for theRom.
[Xoom Android Development] runandhide05:
I'm mobile tight now, but if you have room in your /system download this and move the libs over to /system/lib and move the gallery app over too and that may fix the photo sphere issue

####Untested###

http://d-h.st/xKk

Don't flash it, contains a bunch of stuff not needed, it was a zip I put together for the xyboard
[Xoom Android Development] dreamcwli:
Google Apps updated. Changing camera into sphere mode is no longer causing foced close. However, camera shows the device is not supported. Does anyone know how to solve this?

Video chatting on Talk still causing forced close due to hardware issue and I will try to fix the problem after fixing Wi-Fi and Bluetooth. I have no idea how to make Google Now activated by saying Google but will take a look at it later.

Please help me if you can solve above issues, thanks to everyone reports here. :)
[Xoom Android Development] runandhide05:
I'll dive into the camera and the Google now. Give me a few minutes to wipe and install, haven't touched my Xoom yet today, been working on gnex all day.
[Xoom Android Development] arielp:
seem new phablet ui made effective screen estate lower? on tablet UI, we have effective 1280x752,

anyone can confirm the effective resolution using phablet UI ?

(bottom softbutton and top notif bar will be always visible, right?)

also, on the other thread phablet UI mod, the DPI is changed to 180, does 4.2 on xoom also runs on 180 or still the default 160?
[Xoom Android Development] runandhide05:
OK, got Google now working with a very crud method, in short you were missing the /usr/srec/ for the hot word detection.

Haven't got to the camera yet, need sleep.

Also the "crud" method is due to the lack of space of the /system need to symlink some files, only problem is I don't know how to get it working right on the zip it fails to run my script properly and its been a while since I messes about with it. Also I don't remember where I need to add the addon.d to get it to be able to backup/restore.

I say we get this stupid small partition issue fixed...lol

Let's symlink the hole freaken system to a part of the /data.

Like a /data/fakesystem and just do away with the og /system partition.
[Xoom Android Development] RiThBo:
I'm having difficulties installing the gapps. I tried yesterdays version and todays version of them posted in the 1st post. But after i flash them, nothing appears in the app drawer. I am using TWRP 2.3 recovery. It says when i'm trying to flash, checking MD5 file- skipping, no md5 file found - updating partition details -successful. Any ideas? Thanks

And also the quick setting notification bar on the right hand side does not appear to be there either.

EDIT: Just tried the same gapps on cm10 final, and some of the apps work eg. camera, gmail but not play store, clock. I shall try with a different gapps package
[Xoom Android Development] pikesmatrix:
Sounds like you've run out of space on the system partition, the only gapps that work for me is team eos gapps, but that's for 4.1.* only.
[Xoom Android Development] RiThBo:
Thank, didn't think of that, but there is nothing to remove to free up some space. I think I will just go back to cm10 final. That works
[Xoom Android Development] pikesmatrix:
If 4.2 was to be officially released for the Xoom, it will be the last update. The only way around this is to increase the the system partition, but that is not likely to ever be possible.
[Xoom Android Development] dreamcwli:
Thanks for your information!

It is really annoyed that Xoom has internal storage of 32 GB but only 251 MB is used for system partition. Linking to /data/media is a better choice since factory reset of third party recovery will not erase content in the folder.
[Xoom Android Development] dreamcwli:
After switching to Tiamat AOSP Kernel Wi-Fi works on every boot but Bluetooth failed to connect to devices. I will spend sometime on kernel to solve the hardware issues.
[Xoom Android Development] MarciWoi:
I love your rom but the original launcher is really laggy :-/

Someone with the same problem :confused:

Hope you are able to fix this in the next update, because I like who the original launcher looks like :)

Marcel
[Xoom Android Development] dreamcwli:
I think Android 4.2 is a bit laggy compared to Android 4.1 on Xoom due to hardware limitation. However it should not too laggy to be unusable. Can you check the following video and do you have the same result with mine?

[YOUTUBE]lCJpd05fXdQ[/YOUTUBE]
[Xoom Android Development] redtramp:
Why I can't Root?

Please Help Me!
[Xoom Android Development] dreamcwli:
SuperSU is built in so just flash the ROM will provide you the root permission.
[Xoom Android Development] Muffycheeks:
This belongs in the questions and answers section.
[Xoom Android Development] MarciWoi:
:o Mine is much more lagging .

I think half of your speed, did you du something special?
[Xoom Android Development] dreamcwli:
This is exactly what I uploaded here. Maybe you can try to factory reset and restore your apps individually? I once update to Android 4.2 without factory reset on my Galaxy Nexus and Nexus 7 and even can't boot them up.

Don't forget to restart Wi-Fi on every boot. The ROM currently consume much resource if you don't restart Wi-Fi and make the entire system laggy.

Beware of data moving issue due to factory reset of old recovery, your content maybe moved to /sdcard/0/0/.../0. Or you can wait me to upload ClockworkMod Recovery 6.0.1.8 later.
[Xoom Android Development] Winesnob:
Problem solved. Tried clear clock data and force stop, which didn't do anything, so went to recovery and formatted the system partition (twice for good measure). Flashed the latest ROM and gapps again, and the problem seems to have disappeared.

However,I did find that the Bluetooth toggle in quick settings will only work for the device owner; any additional user profiles cannot use (or even turn Bluetooth on through regular settings). The latter may be they underlying issue. Other than that, seems like another great work for the Xoom!
[Xoom Android Development] dreamcwli:
I have seen the clock issue in CM 10.1 thread but have no idea about that since the clock app isn't modified in this release. It is good to hear it can be solved by clear system partition.

I will take a look at Bluetooth for multi-user support. Thanks for reporting this important issue.
[Xoom Android Development] angel.de.marc:
I've been following this thread for a couple weeks now. A few questions:

How stable is this for stingray? Have these gapps been integrated into main gapps for this rom? If not, how stable are they?

I would really like to get 4.2 up and running on my Xoom, but I use it for school so I need something I can use as a daily driver. I'm not really concerned about green pics and photosphere not working. Gesture typing would be nice but not a deal breaker. Data is really important.
[Xoom Android Development] XxLordxX:
Hey friend, amazing ROM, it seems everything is working (except HDMI), may I ask about an everest build? If you want I can be your tester :)

BTW, I'm only with one little problem here, which is the clock widget (lockscreen) is not right sized (only with some times like 20:59), screenshot is right there :D

"This Story Ends Where It Began"
[Xoom Android Development] dreamcwli:
Currently I only build for wingray since I can't get data working on stingray. You have to wait if data is important for you.

I am going to build for umts_everest this week and will send you the link when finished.

I also notice the clock widget is cropped in lock screen but forget to look at it. Added it to issue list now.
[Xoom Android Development] logitechor:
For the immediate future I am using this ROM. I have flashed Teameos and CM10.1. All are good and working with different items. Gapps can be a problem depending which ROM and which Gapps.

I really appreciate all the effort and the difficulty 4.2.1 presents over 4.1. Thanks again. In your latest Photosphere works. Not sure about HDMI - will look after work.
[Xoom Android Development] dreamcwli:
Photo Sphere was fixed for some time (since 20121125) :p Flash legacy hwcomposer support can make HDMI work but cause some random reboots (more likely when Xoom is sleeping or waking from sleep). You can simply flash the ROM to get rid of it after flashed the exeprimental package.
[Xoom Android Development] assef:
I installed this ROM and i have a question, why it havent face unlock?
[Xoom Android Development] dreamcwli:
Face lock is relied on proprietary files but these files are not working in Android 4.2 so it is unsupported. There is no official face lock support for Xoom as I remembered.
[Xoom Android Development] Borkata81:
You need to change in init.stingray.rc these lines:

Change group from bluetooth to net_bt_stack
[Xoom Android Development] dreamcwli:
Thanks for the tip. This fixed Bluetooth for multi-user support.
[Xoom Android Development] MarciWoi:
I can uncrop the clock on the lockscreen with just delete it and replace it with a new one :)
[Xoom Android Development] assef:
Xoom have no oficial option for Face Unlock,but on TeamEOS Ice Cream Sandwich, it was enbled, but later on Android 4.1 it wasn't enable, and now on 4.2 its not enabled too, its a shame, because its a cool feature!
[Xoom Android Development] MarciWoi:
I have to say that this Rom makes big steps to a stable Rom :) I'm using it at the moment as my daily driver and the only thing that is a bit anoying is that the homescreen could be smoother. The rest is absolutely perfect for me :)

But I really appreciate your work thank you ;)

Gesendet von meinem HTC One X mit Tapatalk 2
[Xoom Android Development] dreamcwli:
Since face lock relied on proprietary libraries, it is unlikely to work if proprietary libraries not updated. What make it worse is that Tegra 2 has no NEON support, so we can't use proprietary libraries from devices with NEON support. Since most Tegra 2 devices with face lock are stopped at ICS, it is also unlikely we can get proprietary libraries from them. Basically I think it is impossible for face lock to work on Xoom after Android 4.2.

In fact I have tried using proprietary libraries from ICS to set face lock and have success. The problem is the multi-user support introduced in 4.2 since old proprietary libraries have no such functionality so I can't unlock it.
[Xoom Android Development] dreamcwli:
The hwcomposer support is required to make the system smoother. If you flashed the legacy hwcomposer support package you will find it is as smooth as in 4.1. The only problem is there are some bugs in kernel so sometimes the system will reboot randomly. I am still working on it and once it is done we can have our smooth system back.
[Xoom Android Development] hipocrazy:
I would be interested of seeing a video of this rom in action. maybe showing off photosphere/viewer, some browsing etc.
[Xoom Android Development] NWinfuse:
Make a nandroid of your current rom and then just flash this and try it out for yourself to see what you think.
[Xoom Android Development] MarciWoi:
I flashed it already, but I still have lags on home and lockscreen ... The rest is smooth!

Gesendet von meinem Xoom mit Tapatalk 2
[Xoom Android Development] dreamcwli:
Can you try to wipe cache & dalvik or backup and do factory reset? I have accidently enabled it one day and found it make scrolling much smoother compared to when it is disabled.
[Xoom Android Development] MarciWoi:
That doesn`t change anything when I wipe cache and dalvik before flashing :-/

Maybe I will try with a factory reset. But I flashed the composer when I fresh installed the Rom yesterday...

Gesendet von meinem Xoom mit Tapatalk 2
[Xoom Android Development] dreamcwli:
OK, I will check the problem and upload my current build for people who are interested since I felt less laggy on my current build.
[Xoom Android Development] PearlMikeJam:
Dream- latest build is running pretty smooth for me. Two issues I have noticed...

1 - the battery life on the latest build seems to be an issue. In using the ROM for about 20 minutes looking through the forums, I went from 100% to 90%. This would usually only use about 3% of battery.

2 - when using tablet ui, the keyboard icon in the status bar is duplicated. See below. I know Google half baked tablet ui. Just thought I would report.
[Xoom Android Development] dreamcwli:
I will take a look at the keyboard icon. Can you check what is eating your battery? Sometimes it may be an app issue instead of a ROM issue so it is better to find out what caused it first.
[Xoom Android Development] dreamcwli:
This is what I am using now. You can use it to see if it is smoother for you.

my_wingray-experimental-20121218-signed.zip

MD5: 05f5e9d0a76217254e614c4b3fb1ce3e

SHA1: 8d26f786b5794220eb949dc00ec0397c6e5e75d7
[Xoom Android Development] MarciWoi:
Thank you I will test it when I'm at home :)

Gesendet von meinem HTC One X mit Tapatalk 2
[Xoom Android Development] lepa71:
for #2

Isn't one icon for google voice input and another for keyboard?
[Xoom Android Development] dreamcwli:
No, if you switch to tablet UI you will find they are both IME switchers.
[Xoom Android Development] dreamcwli:
After playing my current build for a while, I thought there are two changes fixed the performance issue. First is the Bluetooth fix for multi-user support so even if we have no hwcomposer enabled we still have some improvement over last beta release. And hwcomposer support is also required if we want it to be as smooth as in 4.1. It is obvious when scrolling between apps and widgets in stock Launcher. Hope I can work it out soon.
[Xoom Android Development] Peterpaulmarie:
I flashed the experimental ROM. After a rough test, I see/feel no difference, but 26 was smooth as well without any problems (I do not use HDMI out). Thanks again.
[Xoom Android Development] PearlMikeJam:
No. When you expand notifications, there is only one keyboard/input select notification and nothing else. My screenshot may not be the best example because I had other notifications there, but the number of notification icons does not match the number of notifications in the status bar because the keyboard is duplicated.

---------- Post added at 01:55 PM ---------- Previous post was at 01:49 PM ----------

I will install a battery monitoring app and report back. In just looking at the Android battery information, it lists screen and mediaserver as the top 2, which is typical for my use. Tablet Idle is the next item in the list, which is not something I recall seeing in the past.
[Xoom Android Development] alex94kumar:
How's the work on the kernel going? Making any noticeable progress?

Xoomed using xda app-developers app
[Xoom Android Development] dreamcwli:
Not yet. There are details hidden in proprietary libraries so I need much time to trace what going on in the kernel. The performance in current build seem to be OK so stay tuned for developers to do their work.
[Xoom Android Development] Winesnob:
I flashed this version this morning and running well. Not sure if smoother than previous build, but I thought that one was quite good also. Running the CPU at 1504 seems to make a world of difference on the Xoom. I was able to toggle Bluetooth in the secondary user account through settings on this version, but still cannot toggle via quick settings.
[Xoom Android Development] dreamcwli:
After diving into the code I found there are some problems with SystemUI. SystemUI (status bar, navigation bar and system bar) are running under owner identity. When switching to another user, the quick settings in SystemUI is still running under owner identity so Bluetooth manager service refuse to take action for non-foreground user. I have a temporary fix on it but still want to find a better solution. This also affects quick settings for personal settings like GPS so toggling GPS only affects the owner.

The idea of multi-user support is really great but current implementation is not as mature as we thought. We may need some time to fix it for our use.
[Xoom Android Development] dreamcwli:
Finally found a way to fix the issue so multi-user support should be fine in next release. I will push an OTA update once small bugs reported these days are fixed. Please help me to test the OTA update functionality if possible.

I also have a build for umts_everest now and I will post here after uploaded. I will need some users to help me on testing the umts_everest build since I only have wingray.
[Xoom Android Development] Peterpaulmarie:
Of course I will testing your OTA and report here.

I'm as well only a user of wingray...
[Xoom Android Development] assef:
I can test on umts_everest! After you post it i will download and try!
[Xoom Android Development] MarciWoi:
I will test the umts Everest version when it's uploaded :)

Gesendet von meinem HTC One X mit Tapatalk 2
[Xoom Android Development] dreamcwli:
my_umts_everest-experimental-20121218-signed.zip

This is an experimental build so I don't know if it works. Remember to backup your data if you want to try it. Please upload your logcat and radio logcat if you have any problems.
[Xoom Android Development] XxLordxX:
Here is the screenshots you asked on PM
[Xoom Android Development] dreamcwli:
I have received your logcats, thanks!
[Xoom Android Development] assef:
Bro, I installed teh umts_everest version, so by now, no bugs, just the same on the wyngray version, the radio is working, but i dont know how to make a logcat, can you tell me?
[Xoom Android Development] dreamcwli:
You have to use adb to get logcats:

adb logcat > logcat.txt (press Ctrl + C to stop after several seconds)

adb logcat -b radio > radio-logcat.txt (press Ctrl + C to stop after several seconds)
[Xoom Android Development] Winesnob:
Response from the Beautiful Widgets developer on reboots after app update when the lock screen widget is active:

From: Sally

Subject: reboot on 4.2 after BW update

HI,

This is a known issue which is due to Android itself. When uninstalling / updating a paid app while one of its widget is on the lockscreen, the device may reboot.

Google is working on a fix for this and unfortunately, there is nothing we can do for that on our size.

Sorry for the inconvenience.

Regards

View this Discussion online: http://support.levelupstudio.com/di...oken=fd47b8d22f6376867217f390024a0cb229e688e3
[Xoom Android Development] dreamcwli:
I will check master branch of AOSP to see if there are any fixes. Thanks for you information.
[Xoom Android Development] AlEsC:
It seems like something is eating battery very fast. I've fully charged my Xoom last night, use it a few this morning, and this evening it's already half empty (should be something like 90%).

Maybe a clue, in battery stats "Android OS" is first, in general it's "Screen" the first one...

I'm on 1218 (but I think it was the same in 1216), and nothing strange in logcat.
[Xoom Android Development] dreamcwli:
I should take a look at this. Can you help me to test if 20121216 have the same problem? The main difference between 20121216 and 20121218 is the Bluetooth fix for multi-user support. If it is the problem I have better to revert it back.

Does anyone also have battery issue on 20121218?
[Xoom Android Development] AlEsC:
I've "downgrade" to 1216. Results in 24h :)
[Xoom Android Development] dreamcwli:
OK, I will check the Bluetooth fix. Thanks!
[Xoom Android Development] assef:
i made a logcat, the radio one, teh xda sayd its to much heavy! so i upload in another place!
[Xoom Android Development] XxLordxX:
Dream, I don't know how, but today it's working fine the 3g :p... It wasn't working, now it's fine, do you want another logcat?

"This Story Ends Where It Began"

Edit: I think it's the hw composer I installed before, but the Bluetooth isn't working :(