yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] Winesnob:
No issues here as of yet. Wiped cache and dalvik, flashed New ROM and gapps, OC to 1600 with on-demand governor. Been up for well over an hour.

---------- Post added at 12:30 PM ---------- Previous post was at 12:20 PM ----------

I have noticed that Beautiful Widgets causes a soft reboot when updating from the play store,I think due to the presence of the lock screen weather widget. Happened on alpha version also, so probably unrelated to the ROM.
[Xoom Android Development] AlEsC:
That may explained why I've got it too.

By any "chance", do you have a lot (a lot lot) of W/Trace messages in your logcat when you do any action on the screen ?
[Xoom Android Development] Winesnob:
Haven't looked at the logcat yet but will try tonight. From the surface, this build seems very good. Max OC benefit seems to be at 1500mhz but I need to do some more work to see.
[Xoom Android Development] Winesnob:
Been playing with CPU settings and found 1700 mhz to be very unstable, in fact froze the Xoom as soon as I switched up. Also noticed that my OC settings are not saved at reboot even if the box is checked. Unless others are finding 1700 to be stable, you may want to cap the OC at1600.

My performance gains using AnTuTu benchmarking: 1200=+11%, 1400=+22%, 1500=+23% (not much enhancement here), 1600=+36%. All increases are compared to the stock max of 1ghz. All benchmarks were using ondemand governor.
[Xoom Android Development] dreamcwli:
The kernel is forked from kernel in Team EOS ROM and is very different from stock one. I am still trying to implement some features on stock kernel and will switch back once necessary features are implemented.

Overclock settings will gone if you fail to boot the system with overclocking to make it safe. You can try to reboot with a safe maximum CPU frequency like 1200 MHz and settings should be kept.
[Xoom Android Development] Winesnob:
Good to know, and glad you built in something to keep us from getting stuck in an unstable clock setting. Currently booting on interactive governor at 1.6 GHz, and very stable. Chrome has always lagged on the Xoom, but now it is very responsive. Stock browser still a bit quicker, but glass to use chrome as my primary browser on all platforms.

I did try to install the hot word search zip file, but search crashed as soon as it opened. Maybe it'll work eventually.

Great work on this ROM, and now that you, Team EOS and the CM guys are working together, this is only going to get better. Long live the Xoom!!
[Xoom Android Development] dreamcwli:
I will check the hot word detection, is it broken after Google Search is updated?
[Xoom Android Development] Winesnob:
It is broken on the most current version of search; I didn't test on the previous version.
[Xoom Android Development] dreamcwli:
OK, thanks for your reporting. You can try to revert it back by re-flashing the ROM.
[Xoom Android Development] Winesnob:
Still can't get sound search to work. I add the widget, press on it, and after a second of listening it force closes. Minor issue in comparison to what has been achieved with this beta, but a handy feature nonetheless.
[Xoom Android Development] dreamcwli:
I think I should have this fixed. Can you check if there is libvorbisencoder.so under /system/lib? If it is available but music search is still broken, can you send me the logcat with the crash?

I have music search working so it is a bit surprising.

[YOUTUBE]mO9iY2ONJ8M[/YOUTUBE]
[Xoom Android Development] Winesnob:
The closest I could find in /system/lib is libvorbisidec.so

Discovered last night that touching the screen during video recording (to take a snapshot) causes the camera to crash. I attached what I think is the relevant portion of the bug report.
[Xoom Android Development] dreamcwli:
I just found that I didn't update Google Apps :eek:. Download the new Google Apps and flash it should fix music search. I will check for the video recording problem, thanks for your reporting!
[Xoom Android Development] Winesnob:
Perfect! Thanks for posting the new gapps. :D
[Xoom Android Development] dreamcwli:
ROM updated. Only switch back to stock kernel with overclock capability for stability reason.

Have stuck on hardware issues for some time, I will start implementing some features like quick toggles this week. Hope we can have some useful features next week.
[Xoom Android Development] AlEsC:
Flashing updates right now :)

Just a suggestion, but I think putting a date near the download link in the first post would be usefull so we know if we are downloading a new version or not.
[Xoom Android Development] dreamcwli:
I put them after titles of ROM and Google Apps. Hope it is clear now.
[Xoom Android Development] franzfrontal:
Hi, before flashing the new ROM do i need to do a full wipe or just wipe cache and Dalvik?

Many thanks!

Inviato dal mio Xoom con Tapatalk 2
[Xoom Android Development] khanh1289:
If you're coming from an older 4.2.1 then no. If from a different version, 4.1.2, or Rom, full wipe.

Sent from my Nexus 4
[Xoom Android Development] Peterpaulmarie:
Second try. After EOS was failed.

Get no keyboard.

Will try it again later.
[Xoom Android Development] dreamcwli:
Do you flash Android Keyboard by Google? It is randomly crashed and make itself hidden so I move it to unstable packages. Stock keyboard in the ROM works fine but doesn't have gesture typing.
[Xoom Android Development] Peterpaulmarie:
Unfortunatly the download by mediafire failed, so I tried "latimine-2012-11-24-signed" but w/o success.
[Xoom Android Development] dreamcwli:
Just flash ROM and Google Apps the stock keyboard is included.
[Xoom Android Development] tumpy:
Random reboot i am getting with this built, will have to pass on this one.
[Xoom Android Development] dreamcwli:
20121207 or 20121209? And do you have hwcomposer flashed? It is useful if you can give me some information as I only release it if I can have it for my daily use (besides unstable packages).

Does anyone have the same problem with 20121209?
[Xoom Android Development] Cm9aphla:
This Tom looks perfect definetly will try
[Xoom Android Development] tumpy:
sorry for not replying sooner. I only flash the rom and gaap you post i didnt flash the two others but i did with the previous rom..
[Xoom Android Development] dreamcwli:
It's OK, just want to keep my ROM stable for everyone. Can you try to format /system and flash ROM and Google Apps? Also wipe cache & dalvik to make system as clean as possible.
[Xoom Android Development] Winesnob:
Been buttery for me. Find that overclocking too much will cause a few reboots. Thus far 1700 is REALLY unstable, 1600 loses stability with a few apps. 1504 and lower seem to be working well, trying to balance performance and battery life at this point. Also note that Beautiful Widgets will cause a reboot when updating the app from the Play Store if you have the BW lock screen widget running.
[Xoom Android Development] dreamcwli:
Looks like I should remove frequencies higher than 1504 MHz from the kernel. I have set a Beautiful Widget widget on my lock screen and waiting for updates to see what happened.
[Xoom Android Development] Peterpaulmarie:
Yes, keyboard seems to be included and stopped with an error message.

I´m running TWRP 2.3.2.3 with factory reset, wipe cache/dalvik....

Maybe CWM makes difference????
[Xoom Android Development] dreamcwli:
Can you try to upload logcat with the error of keyboard?

You can also try CWM, but I think they should make no difference.
[Xoom Android Development] AlEsC:
I'm sorry to say, but for me the 20121209 feels laggy and slow. Every application is less responsive, tapping on something (a key on the keyboard, a mail in gmail, an icon in the launcher) sometime take 2/3 seconds before actually doing the action. It’s like something is eating all the CPU (but I’ve checked and there is nothing wrong).

I tried 1200 and 1600 freq, both feels "slow".

The 20121207 was a lot more responsive (at least for me).
[Xoom Android Development] logitechor:
Using Dec9 ROM with latest Gapps and experimental HW zips. Watched an Amazon Instant Video on a big screen using HDMI out for the first time on 4.2.1. Thank you. Worked fine.
[Xoom Android Development] dreamcwli:
Are you running 20121209 now? Can you try to download 20121207 and use fastboot to flash boot.img to see if there are any difference? If not there may be some system problems.

As I have said the kernel in 20121207 is forked from kernel of Team EOS ROM and I think it is much better than the stock one. However, the kernel leads to many system warnings as you can see in the logcat. To make it simple, I switch back to the stock one and check what can be merged to improve performance.

Can you check this video and tell me does you system work like this one?

[YOUTUBE]1-PRKeVnNCI[/YOUTUBE]
[Xoom Android Development] dreamcwli:
Looks like hwcomposer works better with stock kernel. I have using it for a day and have no reboot. But the implementation is still a bit slow and I have to find another solution to make it better.
[Xoom Android Development] xoom68:
Having a play with this ROM. Came from EOS 4 as this one says USB storage is fixed.

Still can't mount a USB external drive, was not concerned as have always had to use an app, I did manage to get the latest version of Stickmount to mount the drive in EOS, but with this one I can't.

They also both say the SD card needs formatting when you try and connect a USB drive, and thats from using an external app.

Apart from that seems nice and smooth, does anyone else wonder why a file explorer is not included with ROMs ? Seems silly having Super SU to use root, but I need to download a file explorer to have a play with a ROM ?
[Xoom Android Development] AlEsC:
I'm on 20121209 right now, and my ROM does not responds as well as your video, but it did when I was on the 20121207 kernel.

I will flash back the 20121207 kernel tonight, but the annoying kernel logcat spam (about the W/Trace) is painless since I’m a developer (I know I can filter messages, but I’m lazy too :))

Btw, maybe this could help :

http://code.google.com/p/android/issues/detail?id=39723

Thanks for your realy good work and your help !
[Xoom Android Development] dreamcwli:
Does your USB drive use FAT format? Currently this ROM only supports FAT format so maybe it is the problem.

File manager is not included due to two reason: I want to keep usage on system partition to be as small as possible to future use, and users have different choices on apps. Including an app that users not use isn't a good idea for me, so I always include only necessary apps.
[Xoom Android Development] dreamcwli:
I know the logcat spam is really annoying but I have not found how to solve it yet. I also found the issue you post but it doesn't help much. I should spend some time to look at this. Just waiting for your response on switching kernel back to 20121207 to see if there are any problems.
[Xoom Android Development] xoom68:
No its NTFS. Just wonder why Stickmount is not working with this ROM. All the apps say they mount the drive in both EOS and this ROM but stickmount was the only one that actually showed any files on EOS.

Yeah just something that I have always wondered over the last few months with different ROMs. I would have thought a file manager would have made sense to get to files on initial boot up. Especially for someone new to ROMs. Just my opinion of course. :)
[Xoom Android Development] dreamcwli:
I think StickMount works on Team EOS ROM because they have NTFS support in their kernel. You remind me I should take a look at NTFS and exFAT support. I also think file manager is a necessary app but fail to choose what should be included.
[Xoom Android Development] ArtoD2:
CM10 File Manager is quite capable.
[Xoom Android Development] AlEsC:
Kernel

Quick question :)

I managed to compile the ROM without problems, but I can't build the kernel correctly, correct me if I’m wrong:

shell> make ARCH=arm tegra_android_defconfig
shell> make ARCH=arm CROSS_COMPILE=/aosp/myandroid/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-
[...]
CC arch/arm/mach-tegra/board-harmony-pcie.o
CC arch/arm/mach-tegra/board-harmony-power.o
CC arch/arm/mach-tegra/board-harmony-sdhci.o
CC arch/arm/mach-tegra/board-ventana.o
arch/arm/mach-tegra/board-ventana.c:36:41: fatal error: linux/usb/android_composite.h: No such file or directory
compilation terminated.
make[1]: *** [arch/arm/mach-tegra/board-ventana.o] Error 1
make: *** [arch/arm/mach-tegra] Error 2
shell>

I can't find the "android_composite.h" anywhere (ROM, Kernel, NDK) and it seems like there is no alternative for building (no particular #ifdef).

I must doing something wrong, but I can't find what...
[Xoom Android Development] dreamcwli:
You should use stingray_defconfig instead.
[Xoom Android Development] dreamcwli:
Have it installed and feel it may be a good choice but I can't find a way to change to SD card or USB drive. Can you help me on this?
[Xoom Android Development] AlEsC:
Works perfect, thanks :)
[Xoom Android Development] dreamcwli:
I found I forget to upload the branch forked from the kernel of Team EOS. You can checkout it from the 'forked' branch later.
[Xoom Android Development] ArtoD2:
I don't have my Xoom at hand, but looking from my S2, it needs the "Root access mode" From advanced settings and then I'm able to browse from Storage\ to sdcard0 or 1 etc.
[Xoom Android Development] tumpy:
Dreamcwli, after loading the two other files the random reboot stop, thanks for the reminder, I love to see the NTFS implication add in the next release..
[Xoom Android Development] dreamcwli:
What do you mean about the two other files? I will try to add NTFS support, but require some time to make it work.
[Xoom Android Development] AlEsC:
Thanks, I will !

Have you tried to flash EOS kernel into your ROM ?

Sorry to ask for your help again, but I wanna be sure my boot.img is correct before flashing it :

mkbootimg \
--cmdline 'androidboot.carrier=wifi-only product_type=w' \
--kernel arch/arm/boot/zImage \
--ramdisk ~/myandroid/out/target/product/wingray/ramdisk.img \
-o ~/myandroid_boot.img

Is this correct ? Sould I use another ramdisk ?
[Xoom Android Development] tumpy:
Dreamcwli, after loading hwcomposer and the hot word files last night the random reboot stop...
[Xoom Android Development] dreamcwli:
I think I am a bit lazy on this part. I copy zImage to device/moto/wingray/kernel and use 'make out/target/product/wingray/boot.img' to generate the boot.img. Be sure to use 'lunch my_wingray-userdebug' before generating boot.img.
[Xoom Android Development] dreamcwli:
You have sent this twice... Just want to know what you mean the other two files. I think it should be most stable if you only have ROM and Google Apps flashed unless there are some apps on your system need other files to work.
[Xoom Android Development] AlEsC:
Hum... I do not have a my_wingray-userdebug. I only have full_wingray-userdebug.

I have the my_wingray.mk but vendorsetup.sh is set to full_wingray

Did you push the changes ? :)
[Xoom Android Development] dreamcwli:
I don't add it to vendorsetup.sh but it is possible to use `lunch my_wingray-userdebug` to build it.
[Xoom Android Development] AlEsC:
I must do something wrong then :

> repo init -u https://github.com/dreamcwli/android -b jb-mr1
> repo sync

Fetching projects: 100% (334/334), done.
Syncing work tree: 100% (334/334), done.

> . ./build/envsetup.sh

[...]

> lunch my_wingray-userdebug
build/core/product_config.mk:228: *** _nic.PRODUCTS.[[device/moto/wingray/my_wingray.mk]]: "vendor/my/common.mk" does not exist. Stop.

** Don't have a product spec for: 'my_wingray'
** Do you have the right repo manifest?
[Xoom Android Development] dreamcwli:
It's my fault this time, vendor files for My Android was not included in the manifest but updated now. Sync again you should have it work. Note I didn't upload vendor files for other manufactures like Broadcom, Motorola and NVIDIA, so you need to extract them from ROMs if you want to make working build. See device/moto/wingray/self-extractor/generate-packages.sh and device/moto/wingray/proprietary-blobs.txt for details.
[Xoom Android Development] Winesnob:
Switched back to the 20121207 ROM with the current gapps, and the Xoom seems much more responsive at 1504 mhz, much less lag. I would favor this kernel over stock. I understand there is some"clutter" in the logs caused by this version, but it works well.
[Xoom Android Development] PearlMikeJam:
I am new to flashing the Xoom. Does a factory reset before flashing wipe internal storage? I only ask because this is the first device that wiped system and internal storage in order to unlock and root.

I just want to make sure I don't lose my back up by wiping. I cannot wait to flash.
[Xoom Android Development] XxLordxX:
Actually no... Just will delete your apps and stuff ;)

"This Story Ends Where It Began"
[Xoom Android Development] AlEsC:
Agreed with that... I flash back the kernel from 20121207 and my Xoom is verry smooth at 1200.
[Xoom Android Development] dreamcwli:
I have found a way to get rid of the logcat spam now. Maybe we can switch to the forked kernel if there are no other problems.

Have some tests and the main difference between my kernel and the forked one is on I/O. I will also try to tune this part in order to make my kernel better. Hope one day I can use my kernel since I have less knowledge on the forked one...

Guys can you show me some video for the difference between my kernel and the forked one? I have switched between them but not felt much difference.
[Xoom Android Development] dreamcwli:
If you use third-party recovery then no. Stock recovery will erase everything on internal storage. Nexus devices always erase everything on internal storage during unlock as I know.
[Xoom Android Development] Peterpaulmarie:
Third try; I got it run. My fault! Using TWRP2.3.2.3. You have to wipe ALL: cache/dalvik/factory/system

I´m using stock keyboard for now.

Everything works fine and fast. No FC up to now. Will testing again.

my opinion: I found the control panels on the left side more practical, as well the dialogs on the bottom.

Much Thanks to all developer!! Great job!
[Xoom Android Development] dreamcwli:
What are the control panel and dialogs you refered to?
[Xoom Android Development] Peterpaulmarie:
control panels: BACK/HOME/ALL until 4.1 on the leftside with 4.2 in the middle

dialogs: all messages until 4.1 right bottom now left on top

settings/clock: now right top before right bottom

It is possible to add something to the settings (f.e. GPS)?
[Xoom Android Development] dreamcwli:
You can change back to tablet UI in developer options.

Quick toggles should be added in next release (may only for tablet UI in next release).
[Xoom Android Development] Peterpaulmarie:
Thanks a lot. I will try it.

Small bug: In settings/storage the available space on SD card will not calculated.
[Xoom Android Development] dreamcwli:
Yes, there is a small bug. If you want to see availble space you have to insert SD card before you enter storage settings.
[Xoom Android Development] Peterpaulmarie:
Yes, of corse you have to insert the card before! What I mean is, I see the bargraph but not the calculated space (f.e. 8GB)

but no problem only a hint.

And by the way. Is there a possiblity to skip the google search bar?
[Xoom Android Development] dreamcwli:
OK, I see the problem now. The search bar will be removed in future release.
[Xoom Android Development] Winesnob:
Can the search bar be an option? I personally like it as is.
[Xoom Android Development] dreamcwli:
OK, it should be fine.
[Xoom Android Development] Winesnob:
I'll try to get a few clips together tonight.
[Xoom Android Development] boabsmith:
Where is the developer options?

I presume in settings but I don't have it.
[Xoom Android Development] AlEsC:
Click build version 9 times.
[Xoom Android Development] aR_ChRiS:
Go to about tablet, tap the build number 7 times.
[Xoom Android Development] PearlMikeJam:
Is it safe to update Google Search?
[Xoom Android Development] dreamcwli:
If you didn't flash hot word detection package it should be fine.
[Xoom Android Development] dreamcwli:
Looks like I have found a solution to make HDMI work without making system reboot. Will upload an experimental release here with forked kernel and new hwcomposer implementation for everyone who wants to test the stability.
[Xoom Android Development] Winesnob:
Here are 2 short videos comparing the 1207 build with custom kernel and the 1209 build with stock kernel. Both are overclocked at 1504 with minimum 216 mHz. Only Play Store and Chrome are demonstrated, but these seem to be more demanding processes so were good examples. On the 1209 build you can see significantly longer delays between touch and response, also pages in Chrome are slower to load and very choppy when scrolling (and took more than a single touch to get them to scroll).

Ok, so I don't shoot a lot of video for sharing (first time in fact), and the amazing camera on my GNex was set for 1080p so too big to upload. Tried to convert to other types, but wasn't having success. Here are download links to the videos:

http://www.mediafire.com/file/dmhwyu0zeb48bl8/20121207_build.mp4

http://www.mediafire.com/file/veukpv4ma6sn388/20121209_build.mp4
[Xoom Android Development] dreamcwli:
Thanks! I have used the ROM with forked kernel for a while and found it is faster on everything with I/O (obvious on Beautiful Widgets lock screen widget after reboot). We will switch to the forked kernel if there is no stability problem.
[Xoom Android Development] dreamcwli:
Here are the experimental builds for testing HDMI:

My Android 4.2.1 Experimental for Xoom Wi-Fi (20121212 with Forked Kernel)

https://docs.google.com/open?id=0B0rD7FYbKaR3NmtyMGZ4U0l4OGc

My Android 4.2.1 Experimental for Xoom Wi-Fi (20121212 with My Kernel)

https://docs.google.com/open?id=0B0rD7FYbKaR3cnZLNllKeW41aTQ

I have used them for several hours but still have some reboot with forked kernel. With my kernel I have no reboot so far but still need more test. Please give some comments if you have tried these builds.

Edit:

Have no luck on my kernel too, looks like the kernel need to be patched in order to have stable use. HDMI support will remain separated from the ROM.
[Xoom Android Development] PearlMikeJam:
Dream-

I have been using this for 24 hours now and am enjoying it. Performance is inconsistent. In some areas, this is smoother than 4.2.1, but at times their is stuttering. To be expected with a beta.

One minor bug I found (very minor)...

The bluetooth icon, in tablet ui, does not show when connected. It shows gray when connected and when it is on but not connected.
[Xoom Android Development] dreamcwli:
Switching to kernel with better performance will help system to be smoother, so you can expect next release to see if it becomes better. And thanks for your report, I will take a look at it.
[Xoom Android Development] Winesnob:
This prompted me to check my bluetooth keyboard, which connects and turns the notification icon blue in the new 4.2 UI. Still using the 1207 build, and no issues overall. Daily driver for me at this point.
[Xoom Android Development] dreamcwli:
There are some bugs with tablet UI since it is not officially supported in 4.2. I have to fix them in order to make it usable.
[Xoom Android Development] PearlMikeJam:
It has been very usable for me. I am having some issues with apps, but I do not think it is related to the ROM.
[Xoom Android Development] Winesnob:
Just noticing that the camera access from the lock screen is absent in this build of 4.2. It's this something that was removed from the tablet in AOSP? Just curious; it was a nice feature.
[Xoom Android Development] dreamcwli:
Yes, it is removed from tablets in AOSP. I think I can add it back but I have to say camera shortcut in 4.2 is not as good as in 4.1.
[Xoom Android Development] Winesnob:
From looking at the N4 demos I completely agree about not being intuitive. Seems like a step back from its introduction with ICS. No need to add when there are many other features that would benefit all, just more of an observation. Making the Quick Settings into toggles would benefit many more than a camera from the lock screen.