yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy SL i9003] crazbanditz:
Sorry for late reply. It took me quite a while to search my computer, its a little messy. Once again I apologize the link should be working when you see this post :)
[Samsung Galaxy SL i9003] ALoGeNo:
Works perfect to me in cm10 alpha4, just the sphere camera fail moving to the left or rigth (looks like compas dint work).

Cheers.
[Xoom Android Development] khanh1289:
downloading, will try and report! thanks!
[Xoom Android Development] rmcsc:
Awesome.
[Xoom Android Development] swimdude1120:
everything running great here!

---------- Post added at 04:27 AM ---------- Previous post was at 04:08 AM ----------

if you need help or questions about any fixes, talk to mmuzy. I know its for the galaxy nexus, but I'm sure the bugfixes for aosp can translate over
[Xoom Android Development] lynxboy:
Struggling to find issues with this, but it's only been an hour or so.

WELL DONE!!!!!!

Regards.
[Xoom Android Development] dreamcwli:
Since Galaxy Nexus is maintained in AOSP, it should work without fixing anything. Anyway I will build for Galaxy Nexus and test to see if it has any problems. Thanks for your suggestion.
[Xoom Android Development] extremetempz:
Bugs And ISSUES

When I Get A Notification From Gmail The Sound Stutters and takes 10 seconds to complete Alot Of Apps Crash EX. Quadrant Not Sure If Rom ISSUE and homescreen is laggy is i no this is a very early build but there the bugs i have encounted
[Xoom Android Development] dreamcwli:
You can try to restart Wi-Fi as I describe in the issue list. I think there is something wrong with Wi-Fi and entire system resource is consumed. Restart Wi-Fi make it back to normal state.
[Xoom Android Development] logitechor:
installed

Thank you very much. I first started by installing 4.2 gapps on top of previous version of CM10. Worked pretty well. This is very nice. I will have to update all the software later in the day. So far all working.
[Xoom Android Development] assef:
Great work bro! Is it possible to make for the Xoom 3G MZ601?
[Xoom Android Development] MarciWoi:
Sound interesting, lets give this a try :)
[Xoom Android Development] mongday:
Gesture input doesn't work for me.
[Xoom Android Development] dreamcwli:
I have noticed this. Since I didn't see gesture input introduction on Nexus 10 page, I think maybe gesture input isn't available in large tablets by default. Will check this after finishing the essential part of this ROM.
[Xoom Android Development] mongday:
Spherical camera force close for me.
[Xoom Android Development] dreamcwli:
I forget to include some binary files in Google Apps, will re-upload it later. Thanks for your report.
[Xoom Android Development] mongday:
Can not launch the Google now by saying "google" like the previous android version.
[Xoom Android Development] sibax:
Great ROM and congrats on being first. I am having trouble seeing my files and writing to internal storage after having flashed the ROM. On the storage section of settings I can see how much is used and how much I have left but the amounts quoted and what they are allocated to appear to be incorrect. Using file explore and or root explorer I can not see files or items stored to internal storage. Strangely however my pictures that I had stored to internal storage show up on gallery....!?
[Xoom Android Development] dreamcwli:
I am not familiar with this, can you provide some information?

Due to the multi-user support, the internal storage structure has changed. Generally speaking, data originally located under /sdcard have been moved /sdcard/<number> based on your current user number (started from 0). The storage summary shows storage size used by every user.

There is also another problem due to recovery. Currenty recovery wipe all content under /data excepts /data/media on factory reset. On Android 4.2, when system boots it checks if /data/.layout_version is existed. If not, it thinks user are updating from old Android version, and move content in /sdcard to /sdcard/0. If you factory reset several times, the content will move to /sdcard/0/0/.../0. ClockworkMod developers have made a workaround of this issue and hopefully every recovery will support Android 4.2 soon.
[Xoom Android Development] sibax:
Great thanks for the quick response. Found all my stuff under the file marked 0 under sdcard .
[Xoom Android Development] truskuss:
Very good rom, gtalk video and sphere does not work: (, everything else perfect
[Xoom Android Development] dreamcwli:
Aren't the first two features already available in the power menu?

Yes, this is a must and the reason I start learning to build ROMs in the past.

I'll try it and make it available in my Google Apps package, thanks!
[Xoom Android Development] dreamcwli:
Hot word detection works but keyboard still crashes on normal typing. In my opinion, moving entire /system/lib to /data is a bit dangerous since factory reset will delete them and make system unbootable. Thanks for your efforts, I will merge hot word detection feature into my Google Apps package.
[Xoom Android Development] runandhide05:
It works on your latest build, all of it works, you r free to do what you will with it.

and as for moving libs something needs to be done, and just like the rest of the eos gapps things have to be moved, its just the way it is, there are already plenty of things symlinked to data, and all eos users should know by now if you are going to factory reset you need to reflash rom and gapps anyways. so you/we have two options, remove features from aosp to slim it down enough, or move stuff around and keep the all the things possible.

there are all the addon.d scripts needed to backup and restore all the files and symlinks just like in any normal gapps.

so as i said, you are free to do what you will with these, no problem either way. just helping out,

:D

http://www.youtube.com/watch?v=tPH9vRNMhv0&feature=g-upl
[Xoom Android Development] dreamcwli:
You can try typing letter by letter at Google in Chrome. Everytime I enter the first letter of a word, the keyboard gets hidden and recover a bit later. Enter rest part of the word is fine, but it still gets hidden in first letter of next word and so on. If you use logcat you can see libjni_latinimegoogle.so crashed. The keyboard works fine if suggestion is turned off, but seems not a good solution.

Will upload a video on this problem later since I am not with Xoom now.
[Xoom Android Development] runandhide05:
ok i see what your saying, i dont use chrome so didnt catch that, odd it only minimizes when it populates a suggestion, and only in chrome.

o well,
[Xoom Android Development] dreamcwli:
Not only on Chrome but everywhere the keyboard tries to make suggestions. It is weird since I use the same keyboard on my build for Galaxy Nexus and Nexus 7 without issues. Can't figure out why the library only crashed on Xoom...
[Xoom Android Development] Winesnob:
Getting ready to install this ROM for the first time, can't wait! Been stock until now. One addition that I like from the latest CM builds is an option in developer options to toggle root access on or off. Unless I'm working with system files or doing things that specifically require root, I prefer to disable root access.
[Xoom Android Development] jaya21:
Installed 30/11 build today. Awesome work. Only one thing ive found that crashes is under settings, display, daydream and clock. Changing to this or going into settings crashes.
[Xoom Android Development] dreamcwli:
Sounds good. I will try to add it.

Thanks for reporting. Set to clock didn't crash for me but clock settings do. I will take a look at what happened.
[Xoom Android Development] AlEsC:
Awesome !

Nice work !

Latest version is totaly usable on daily purpose !

Is there a "simple way" to make the "No services" disapear on lock screen for wingray users ?

I've tried freezing all phone related apps, no luck here, would have been to easy :)
[Xoom Android Development] dreamcwli:
This should be done by ROM modification. I will fix this in next release.
[Xoom Android Development] cctv35:
@dreamcwli

Can you compile a MZ600 (stingray_cdma) 3G version?:confused:
[Xoom Android Development] dreamcwli:
Stingray_cdma is the same as stingray without LTE? If true I can build it after I make stingray radio system work.
[Xoom Android Development] XxLordxX:
I'm using your ROM now, but it's really amazing! Loved the usability of it, always even the phablet screen. The keyboard wasn't a problem because I use SwiftKey keyboard, so I don't need to run the other keyboard. It ran nicely a 720p video, just waiting for a 3g version (umts_everest), and I think can be your tester if you want ;)

Congrats :D ROM usable DAILY!

"This Story Ends Where It Began"
[Xoom Android Development] aR_ChRiS:
Is it possible to post the tiamat 4.2 kernel that we've used in the 19/11 build? I love how usable this rom is even in an early testing phase, but I would just want the OC back.
[Xoom Android Development] dreamcwli:
In fact it is kernel for 4.1 instead 4.2 so Bluetooth is broken. I checkout kernel source code for Xoom from Team Eos but they have not merge Bluetooth changes into their kernel yet. I think it is a bit strange if I patch their kernel and release it here...
[Xoom Android Development] aR_ChRiS:
I think you can PM them and ask for permission of doing so, since they have yet to release a working 4.2 rom yet and your input maybe beneficial to them as well, who knows?
[Xoom Android Development] dreamcwli:
Looks like Team Eos members turn off their PM functionality. I will try other ways to contact them and release the kernel if possible. I am also thinking about derive their work but not using their name as some bugs may be introduced by my patches.
[Xoom Android Development] Winesnob:
This is very good work. Only suggestions are to enable Google Now from the lock screen and allow over clocking to 1.2GHz. The latter would really boost the Xoom. Aside from these, this is really responsive, and great work getting the photosphere working.
[Xoom Android Development] dreamcwli:
If you don't change to tablet UI, there is a circle in the center of bottom bar for launching Google Now. From responses it looks like overclocking become a must have one on Xoom, maybe I should start implementing it.
[Xoom Android Development] Winesnob:
Understand, but Google Now was also accessible from the lock screen in 4.0 - 4.1x. Not sure if 4.2 removed that feature or I'm missing something.

Edit: I must be visually impaired. I see it now on the lock screen.
[Xoom Android Development] dreamcwli:
Will try to build umts_everest version soon since this is the 3G model available in my country.
[Xoom Android Development] AlEsC:
possible bug...

It seems the notification button "clear all notifications" does not work. It looks like it works but notifications reapear, at least in tablet ui.

I've switch to phablet ui to see if the bug is still here.

Btw, is the tablet ui code in 4.2.1 AOSP or is this a port from previous android release ?
[Xoom Android Development] dreamcwli:
I will check the problem, thanks for reporting.

The tablet UI is available in 4.2.1 but require some modification to make it work.

EDIT:

I have tried clear notifications with tablet UI but they don't appear again. Can you describe how you get the problem?
[Xoom Android Development] Winesnob:
Is there a recommended recovery to use with this ROM? Installed CWM touch 6.0.1.9 which seems to be working well, just want to be sure there aren't any potential pitfalls.
[Xoom Android Development] aR_ChRiS:
Either use CWM 6.0.1.9 or TWRP.
[Xoom Android Development] dreamcwli:
ClockworkMod Recovery is well supported because I use it. There should be not much difference between recoveries if they supported Android 4.2.
[Xoom Android Development] NoMercyWWE:
Absolutely great for building umts Everest version
[Xoom Android Development] AlEsC:
Removing system package does work (freezing does not) :

Here are the packages I have removed :

/system/app/Email.apk (I just don't need it)

/system/app/Exchange2.apk (same)

/system/app/Phone.apk

/system/app/StingrayProgramMenu.apk

/system/app/StingrayProgramMenuSystem.apk

/system/app/TelephonyProvider.apk

And no more "NO SERVICE" message on lock screen ! :)
[Xoom Android Development] cctv35:
radio system work,but use SIM card does not Read, I'm from China
[Xoom Android Development] AlEsC:
Wingray

I've made two small recovery zip for wingray users.

The script will remove stingray packages and the locksreen message "NO SERVICE".

Removed APKs (wingray-phone-remove.zip) :

/system/app/Phone.apk

/system/app/StingrayProgramMenu.apk

/system/app/StingrayProgramMenuSystem.apk

/system/app/TelephonyProvider.apk

The second (wingray-phone-email-remove.zip) will remove above APKs and :

/system/app/Email.apk

/system/app/Exchange2.apk

Not that the script will also change the bootanimation to "Moto heart beat".

Install :

Just go in recovery and flash it.

Use it only if you need it :)
[Xoom Android Development] LOGMD:
Loving this, refused official update but we still get it fast ;)

this rom is pretty stable for the most part!

im still getting some issues with bluetooth but it works on boot,

i turned off bluetooth before sleeping then work up and bluetooth would not switch on (tried wifi on of, aeroplane on of then bluetooth) reboot worked fine for now though. also i had to re-pair any devices used

other then that id say this is nearly a daily driver for the casual user =]
[Xoom Android Development] dreamcwli:
I think this could not be called radio system work, since the app to initialize SIM doesn't work now so no mobile network is available. Will try to fix it later.

How do you get the problem? I tried booting with Bluetooth on and turn it off and put Xoom into sleep for a while. After waking Xoom up I can turn on Bluetooth and devices are connected automatically.
[Xoom Android Development] Winesnob:
Nice work, but you reversed the names on the zip files.
[Xoom Android Development] AlEsC:
Indeed, sorry about that ! (I've edited the post)
[Xoom Android Development] tumpy:
For what it worth, I try both this 4.2 and eos and find this is more worthwhile for what it offer, I cannot access my SD card in eos unless I go to system then storage to find SD card, also your recovery for 4.2 work better for me, twrp 2.3.2.3 give me boot loop it won't go into recovery...
[Xoom Android Development] AlEsC:
To be continued ?

@dreamcwli are you still working on this ROM or do you plan working on EOS one ?
[Xoom Android Development] PearlMikeJam:
According to post #157, here is what he said...
[Xoom Android Development] dreamcwli:
I am still working at this ROM and will keep doing so. Don't worry about it since I always use my ROM. I plan to release once a week in order to make it stable for use.
[Xoom Android Development] tumpy:
with that attitude i will stay onboard, once a week is much better than nightly it give you time to sort out the kinks.
[Xoom Android Development] Winesnob:
Looking forward to what may come. With the 1130 build and removal of the telephony system apps, this thing is solid. The Xoom continues to breathe...
[Xoom Android Development] Winesnob:
Bug report: sound search widget is force closing after a few seconds of listening.
[Xoom Android Development] dreamcwli:
I will take a look at this, thanks for reporting.
[Xoom Android Development] boabsmith:
Installed this ROM tonight. Very sweet.

Many thanks.

Any chance of a user agent choice in the stock browser?
[Xoom Android Development] dreamcwli:
I can implement it later. If you need this now you can type about:debug in address bar of stock browser, then there is an UAString option under debug section in browser settings.
[Xoom Android Development] dreamcwli:
Mainly fix bugs reported these days so I am not sure if there are new features in next release. At least we will have CPU overclocking as many user suggested but I don't know if it solves the performance issue.
[Xoom Android Development] Winesnob:
Looking forward to testing!
[Xoom Android Development] boabsmith:
Fantastic, many thanks
[Xoom Android Development] dreamcwli:
Looks like we can move to beta release this week. (thanks to ejtagle!)
[Xoom Android Development] cctv35:
3G MZ600 (stingray_cdma):crying:
[Xoom Android Development] dreamcwli:
Take it easy. I have to fix everything step by step and the basic part is almost fixed. Once I fix mobile network it will be all working on your device.
[Xoom Android Development] assef:
When you launch the new release?
[Xoom Android Development] dreamcwli:
About every weekend. I am still testing kernel and HDMI to ensure their stability.
[Xoom Android Development] assef:
Ok, i'm waiting for the new release!
[Xoom Android Development] theMaDHakkeR:
I'm just wondering if its normal for the launcher to lag all the time? I had that issue before due to the io scheduler. But i can't change it yet with the provided kernel.
[Xoom Android Development] Winesnob:
I've had some lag, but not consistently. Usually after Play Store updates or adding apps until the memory gets flushed out. Overall my experience has been BUTTER in comparison to stock 4.1.2. Looking forward to the beta release for bug cleanup and over clocking.
[Xoom Android Development] dreamcwli:
Can you test if Launcher is laggy after factory reset?
[Xoom Android Development] theMaDHakkeR:
I'm going to try a fresh flash. I need to update my cwm to support jb also.

It was one of the issues I had with eos3 when they changed the io scheduler. Pure lag instead of butter. Everywhere. Every app. Everything.

Also I did a full factory reset and wipe before installing. So not sure what can cause this.
[Xoom Android Development] theMaDHakkeR:
So after flashing twrp and wiping everything i did a fresh install. Its still lagging a lot in just about everything. Is there any way to change the io scheduler? 4.1.2 ran so smooth...
[Xoom Android Development] dreamcwli:
I will release next build with a better kernel, so let's wait. I have to say 4.2 is also not as good as 4.1 even on my Galaxy Nexus and Nexus 7. Personally I think 4.2 is not a stable release.
[Xoom Android Development] theMaDHakkeR:
Maybe true since my LGOG scored higher than the N4 on 4.0.4....
[Xoom Android Development] AlEsC:
git

@dreamcwli are you committing to git on every changes or only when you release a new ROM/kernel ?
[Xoom Android Development] dreamcwli:
I push to GitHub when I clean the source tree. The changes of a release should all be pushed when it releases. Do you want to find something there?
[Xoom Android Development] AlEsC:
I like to make some tweaks (for testing), maybe help (if I can and if you allow it), and also... I just can't wait one week for a new release :)
[Xoom Android Development] dreamcwli:
Sounds good. If you fix anything feel free to send pull request to me.
[Xoom Android Development] dreamcwli:
ROM and Google Apps updated. See first post for more details. HDMI is fixed but include in an unstable package since it causes random reboot. However flash the HWComposer package not only fix HDMI but also make graphic system work better. You can have it a try and back to original state by re-flashing the ROM.
[Xoom Android Development] bigrushdog:
My maintainer runandhide5 has referenced several commits from your repo. I properly merged to maintain commit attribute history. It is most refreshing indeed to see fresh talent in xoom land! If Eos can be of service, don't hesitate to ask.

brd
[Xoom Android Development] dreamcwli:
I am glad I can help. Hope we can help each other to make Xoom an incredible device!
[Xoom Android Development] bigrushdog:
Grab my email from my xda profile and send a gtalk invite. Or i'm often on irc freenode on #teameos, #xoom, and a bunch of chans. Xoom will become a challenge now as it is no longer supported. Also I have a good relationship with TDR and SteadyHawkin who maintain the xoom cm build as well.
[Xoom Android Development] dreamcwli:
Sounds good. Looking forward to discuss with you for making Xoom work better.
[Xoom Android Development] franzfrontal:
This beta version is more unstable than alpha!!...too many reboot!

Inviato dal mio LT26i con Tapatalk 2
[Xoom Android Development] dreamcwli:
Do you have hwcomposer flashed? If not it should not be rebooted as I used it for several days. Can you describe how you flash the ROM and try to see if wipe cache & dalvik even factory reset helps?

Does anyone have the same issue?
[Xoom Android Development] franzfrontal:
For first i did a full wipe, then I flashed the main rom and hwcomposer and then google apps and latinme! ...

Inviato dal mio LT26i con Tapatalk 2
[Xoom Android Development] dreamcwli:
First use the ROM and Google Apps only. Unstable packages is separated from downloads section since they still have some problems. The hwcomposer is the main reason why system reboots, but sometimes it just works. Once it becomes stable I will include it in the ROM.
[Xoom Android Development] franzfrontal:
Ok, just reflash the rom!..many thanks for the tips!:thumbup:

Inviato dal mio LT26i con Tapatalk 2
[Xoom Android Development] alex94kumar:
If we want to flash this from eos4, would you suggest a full wipe?
[Xoom Android Development] dreamcwli:
Since they are both based on Android 4.2, I think wipe cache & dalvik should be enough. If configs are not conflicted between Team EOS 4 and My Android 4.2.1 it should work. If you have time for backup and restore, full wiping always make a most clean system.
[Xoom Android Development] AlEsC:
I've updated from previous release (only ROM + gapps, no unstable pkg, no OC, phablet ui) and I've already experienced 2 randoms soft-reboots (no moto logo, direct to bootanim) in less than an hour. Both times I was in the stock browser.
[Xoom Android Development] dreamcwli:
Does wipe cache & dalvik help?

Can you use ADB to get logcat and upload here? Also can you provide the website you are browsing when Xoom reboots? I would like to test if it happens on my device.
[Xoom Android Development] dreamcwli:
Since I changed kernel most in past few days, the unstable system state may be caused by it. If many of you have stability problem, I will release the ROM with previous kernel and provide overclockable kernel in another package. Please let me know if you have stability problem.
[Xoom Android Development] AlEsC:
First time I was browsing this thread pages, second time I don't remeber.

I've tried and retried browsing all pages, swaping, moving, sliding... but I can't reproduce it. The only difference is that I've OCed to 1200mHz.

I'll try to get you a logcat if I can reproduce.
[Xoom Android Development] dreamcwli:
Thanks!
[Xoom Android Development] AlEsC:
Just so you know, I got hundreds of lines per second in my logcat like :

[...]
W/Trace ( 1399): Unexpected value from nativeGetEnabledTags: 0
W/Trace ( 1717): Unexpected value from nativeGetEnabledTags: 0
W/Trace ( 2379): Unexpected value from nativeGetEnabledTags: 0
W/Trace ( 2379): Unexpected value from nativeGetEnabledTags: 0
W/Trace ( 1717): Unexpected value from nativeGetEnabledTags: 0
W/Trace ( 1399): Unexpected value from nativeGetEnabledTags: 0
W/Trace ( 1717): Unexpected value from nativeGetEnabledTags: 0
W/Trace ( 2379): Unexpected value from nativeGetEnabledTags: 0
W/Trace ( 2379): Unexpected value from nativeGetEnabledTags: 0
W/Trace ( 1717): Unexpected value from nativeGetEnabledTags: 0
W/Trace ( 1717): Unexpected value from nativeGetEnabledTags: 0
W/Trace ( 1717): Unexpected value from nativeGetEnabledTags: 0
W/Trace ( 1717): Unexpected value from nativeGetEnabledTags: 0
W/Trace ( 1717): Unexpected value from nativeGetEnabledTags: 0
W/Trace ( 1717): Unexpected value from nativeGetEnabledTags: 0
W/Trace ( 1717): Unexpected value from nativeGetEnabledTags: 0
[...]

I've googled it, it seems to come from the kernel.
[Xoom Android Development] dreamcwli:
I will revert to previous one and provide overclockable kernel in another package. Thanks for your help.