yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] lemmy_0:
I too am having the FC when I select Lockscreen.

Another thing, what is the recommended kernel for this ROM?

Seems a bit laggy to me
[Xoom Android Development] SoCalArm:
Yup lags here too

Sent from my SCH-I605
[Xoom Android Development] Alxoom33:
Of course it lags a little! You have an older single core processor made to run at 800 kHz oc'd to 1.4 to 1.6 gig hz. With a modified operating system. I think it's awsome that we can run 4.4.4 on our 3 yr old Xooms that just refuse to die!

Thanks BRD and EOS!
[Xoom Android Development] lemmy_0:
doesn't answer the question.
[Xoom Android Development] hochoch:
I always flash Elemental X 2.1 GPU OC after a new build. I believe that the rom comes w/ 2.0 vanilla. Does my xoom run as good as a brand new quad core tablet? No. But it definitely suits my needs.

Just make sure to overclock to at least 1400, use interactive gov and turn down/off animations in the dev options. I also use greenify to make sure nothing running in the background.

Also - lockscreen is still FC settings on the latest build for me too.

EDIT: forgot link to kernel http://xdaforums.com/showthread.php?t=2144360
[Xoom Android Development] runandhide05:
Have to bust your chops... It's a dual core and it's 1000Mhz (1Ghz) not 800kHz

In 1979 Intel released the 4004 which was a 800kHz cpu just to give you some references to a 800kHz

sent from space
[Xoom Android Development] shpitz461:
How's RnH's 'kernel' doing? getting better? :)
[Xoom Android Development] runandhide05:
Not use what your referring to as I don't do kernel work, although I'm sure there is a pun or joke I'm missing there somewhere. On a more serious note as you can probably tell I've kind of lost any passion I had left for android development stuff. So il still be around for help and the occasional support but I'm pretty much done otherwise.

This isn't just answering you but the other "how ya doing/recovering from surgery questions" as I know this is way off topic (although it seems like our mods don't bother in /xoom anymore) who cares. But if you have any questions that are off topic feel free to pm me

sent from space
[Xoom Android Development] Alxoom33:
Busted[emoji1] That's what I get for rushing... But my lockscreen doesn't fc. Oc'd to 1.6 GHz interactive.
[Xoom Android Development] lemmy_0:
thanks!

updated to this kernel now!

another thing, my settings do not have Performance on the menu.

do you use another tool for overclocking or is this an issue with the nightly?
[Xoom Android Development] Alxoom33:
I use Android Overclock app. It has most governors and profiles, as well as other handy tools. ON to 1.6 GHz for the last 3 yr or so. Interactive Governor.
[Xoom Android Development] hochoch:
I like trickstermod. Gives the notification when boot completes that all your settings are active.
[Xoom Android Development] lemmy_0:
thanks. I guess trickstermod will do the trick
[Xoom Android Development] drewski_1:
I thought governors were Kernel dependant, not the control app?

Sent from my 4.4.4 Razr Maxx
[Xoom Android Development] brewer75:
Recent Problems with Nightlies

I have flashed both the 9/16 and 9/17 Wingray builds only to find that my Xoom wouldn't run properly. Both builds booted and opened but then they stopped and I was stuck on the security log in page I use. I'm sorry to report that I didn't run any logs and didn't copy down the error message that these builds throw but I can say I was able to restore my 9/14 build and everything works great. Is anyone else having problems with recent nightlies? I really don't want to clean everything and start over if there are others having the same problems. :confused:
[Xoom Android Development] Blondblueyed_girl:
Running 9/16 OK here

---------- Post added at 10:40 PM ---------- Previous post was at 10:06 PM ----------

Now have updated to 9/17. And its running fine
[Xoom Android Development] brewer75:
Thanks. I'll wait for the next build and try it again. Everything has been fine for several flashes but something now seems to be causing my Xoom some problems.

**Update**I just re-flashed the build from 9/17 and everything worked fine. I don't know what caused the problems the last time I flashed this but all is well now!
[Xoom Android Development] SoCalArm:
Just updated still found lockscreen to FC but am able to change it via security. Day dream music comes on sometimes after tablet sits for hours not charging (I have day dream set when docked and charging). Cool song but took me a while to figure out where the magical music was coming from one day lol. Good job dev keep up the good work EOS #1.

P.s where does one download themes for the EOS rom as there is a theme option ?

Sent from my SCH-I605
[Xoom Android Development] brewer75:
**UPDATE #2** I spoke too soon. although my Xoom ran properly after flashing the 9-17 Wingray build, upon reboot everything seems ok during boot but I get the following "Unfortunately, the process com.android.systemui has stopped" and the device cannot open the rest of the way. So either I remain happy with the 9/14 build which works fine, or I clear everything and start over apparently.

**UPDATE #3** OK, I just flashed the new 9/20 Wingray build and everything seems to be working normally. I've rebooted a couple of times and so far, so good. No more errors and life is good!

**UPDATE #4** Bummer. This morning when I booted up it wouldn't work and I got the same "Unfortunately, the process com.android.systemui has stopped". So, I guess I'l do a wipe and start over. Still wonder why the 9/14 Wingray build works fine and the same is true when I go back and restore that build after the subsequent builds keep giving me the "Unfortunately..." message.

**UPDATE #5** I didn't do a full factory reset but I did wipe everything except the SD card and then I flashed

the 9/21 build yesterday. Everything seemed OK and I had to do all the re-entry of the owner info, Google account info, etc. The system was humming along fine UNTIL I rebooted, then I got the "Unfortunately, the process com.android.systemui has stopped" message again! Once I get this message the Xoom is not functional so I restored the old 9/14 build and again the Xoom is running as it should. I guess at this point I'll just leave well enough alone and not update.
[Xoom Android Development] Alxoom33:
I believe selection of the governors is Control app dependent.
[Xoom Android Development] kmcrane:
Double post
[Xoom Android Development] kmcrane:
Pretty sure the governors are in the kernel. I can flash a different kernel and have different choices in the same app. I have always used trickster and some kernels give 3-4 choices some will give you 10.
[Xoom Android Development] tnfsmith:
Yes me too.

Sent from Tapatalk MZ601 - TeamEOS 4.4.4 Kitkat nightlies
[Xoom Android Development] bigrushdog:
Lockscreen settings should be fixed. I forgot there's extra stuff I gotta do for tablet settings.
[Xoom Android Development] ahmed007:
Lock screen settings working
[Xoom Android Development] bigrushdog:
I'll bring in lock ring targets when opportunity permits. Been very busy doing behind the scene stuff in preparation for L. I don't know if non neon will be supported or not. Or how much h4xR it will take to make it work. Even if it doesn't happen the TeamEos kk4.4 branch will still be buildable if folks want to continue Kk development.
[Xoom Android Development] matt4321:
If L doesn't happen, I can get further kitkat builds based off EOS kk branch up.
[Xoom Android Development] brewer75:
Unfortunately, the process com.android.systemui has stopped

I didn't do a full factory reset but I did wipe everything except the SD card and then I flashed the 9/21 build yesterday. Everything seemed OK and I had to do all the re-entry of the owner info, Google account info, etc. The system was humming along fine UNTIL I rebooted, then I got the "Unfortunately, the process com.android.systemui has stopped" message again! Once I get this message the Xoom is not functional so I restored the old 9/14 build and again the Xoom is running as it should. I've tried every nightly since 9/14 and get the same message with every one of them. I guess at this point I'll just leave well enough alone and not update. :(
[Xoom Android Development] SoCalArm:
Lockscreen now works. Thanks dev for listening to the consumer.
[Xoom Android Development] Blondblueyed_girl:
Have never had a problem downloading any of the ROMs. Until now. Anybody else having a problem with the latest wingray 20140921 downloading with the Xoom.

Edit

Scub that its OK now

2nd Edit

Although it eventually downloaded, would not flash ( zip unable to open ) message.

Will keep trying.
[Xoom Android Development] Alxoom33:
No problems here.
[Xoom Android Development] brewer75:
"Unfortunately, the process com.android.systemui has stopped" message

I've been having problems with the nightlies for about 2 weeks. The 9/14 Wingray build works fine on my Xoom but every time I have flashed a nightly build since 9/14 the build seems perfect at first, except once I reboot I get the same message: "Unfortunately, the process com.android.systemui has stopped". Once I get this message the Xoom cannot be used but when I restore the 9/14 build everything works great. I have not done a factory reset and would prefer not to but I have wiped everything except the SD card and still got the above message. I guess I can be content with the 9/14 build but I'd like to keep as current as I can so I welcome any guidance from all the brains out there.
[Xoom Android Development] shpitz461:
Are you o/c'ing? did you restore any apps? get a logcat and provide it here, maybe BRD can spot something.

I flashed 9/21 Wingray on my Stingray last night, i'll see how it goes.

I never saw any FC's in any of the builds, but i'm experiencing a weird issue where if I reboot and not unlock immediately, and let the tab idle, if i try to unlock it, the touchscreen is non-responsive. Only way to get touch back is to reboot and unlock before the tab goes to sleep.

I've restored my apps with Ease Backup, but didn't run Trickster, so i'll see when I come home.
[Xoom Android Development] brewer75:
I used to OC but now that BRD has changed the clock speed in the build I've been going with the default. BUT, I've used Trickster MOD to change the TCP Congestion Control from Cubic to Westwood, the Read Ahead Buffer size from 128 to 512, and the Governor Control hispeed_freq from 100000 to 120000 on boot up. This worked fine on builds up to 9/14 but not afte (apparently). So, I disabled Trickster MOD on boot up and also reverted back to it's defaults, and then flashed the 9/24 nightly. My problems must have been due to Trickster MOD because the flash worked fine and I have rebooted twice with continued success. So, hopefully that was my problem and I guess I'll shelve the Trickster MOD app for now!

Edit...Well I guess I spoke too soon because when I booted my Xoom this morning I got the familiar "Unfortunately, the process com.android.systemui has stopped" message again. So, apparently Trickster MOD wasn't the culprit. I just don't understand why I was able to reboot several times last evening after flashing the 9/24 Wingray nightly and everything went smoothly but this morning it's a different story.
[Xoom Android Development] SoCalArm:
downloading EOS WINGRAY 20140924 112634 now will post shortly if it works

Sent from my SCH-I605

Edit

It works. My xoom is stingray but only use WIFI so I use wingray.
[Xoom Android Development] pots22:
Dimension unlock screen

I re-flash the last update of Everest, and all work perfect now.

Good fluidity and good speed. No reboot.

Wifi and 3G work great.

Gps work great.

Hdmi perfect.

Only the dimension of the unlock screen stay wrong size like OMNI in the first release.:confused:

And no buton for erase all recent applications.:crying:
[Xoom Android Development] hochoch:
Try using gravity box for xposed to gain the clear recent button back and lots of other useful stuff.
[Xoom Android Development] runandhide05:
Haven't used it often...but the standby time is amazing, and obviously no random reboots

15 days without a charge

sent from space
[Xoom Android Development] stanl56:
I cannot get the 9/24 Wingray build to boot. It hangs on the Dual Core screen. Had to restore the 9/21 ROM. The only issue with 9/21 is the non responsive screen when trying to turn on in the morning. Other than that I'm very happy with the EOS Xoom Roms.
[Xoom Android Development] brewer75:
Had to Switch

I hate to do this but I am forced to switch to a different 4.4.4 Rom. After repeatedly trying to update TeamEOS Wingray Nightlies after 9/14 but constantly getting the same message, "Unfortunately, the process com.android.systemui has stopped", I wiped everything but the SD card again, tried the most recent Cyanogenmod build and everything works fine. I then wiped everything but the SD card and flashed the 9/24 TeamEOS Wingray build and again got the same "Unfortunately..." message. So, short of reverting back to regular partition and resetting back to factory, then big part etc., I decided to just go with what seems to be working fine. I'd like to stay on TeamEOS but I really don't want to do the whole process over again. If there are other solutions I'm listening!
[Xoom Android Development] Alxoom33:
Maybe you have a bad dl. 9/24 build works fine for me. What gapps did you flash?
[Xoom Android Development] kmcrane:
9/24 with PA nano gapps have been great for me on my Xoom and grouper.
[Xoom Android Development] Alxoom33:
I like the PA full gapps myself.
[Xoom Android Development] kmcrane:
I like minimal apps. I'll download what I actually use. Otherwise I don't want the extra.
[Xoom Android Development] brewer75:
The 9/14 Wingray build worked for me but I have tried every nightly since that one and each was fine until I rebooted, then I got the "Unfortunately, the process com.android.systemui has stopped" message I listed in my previous post. I have been using PA Full Modular Gapps forever and I haven't changed anything I can think of since I flashed the 9/14 build. The reboot thing stymies me but as I wrote in my post, Cyanogenmod seems to work fine AND survive rebooting. The strange thing is that I can restore the TeamEOS 9/14 build and it works fine. So I could stay with that build but based on what I am seeing with my Xoom I would not be able to update from that build.
[Xoom Android Development] Alxoom33:
Sounds like a bad download. Re- download and check MD5. Or wait for next nightly.
[Xoom Android Development] pots22:
Xposed Gravity KK

Many thank's

with this tool i resize the unlock sim keyboard and put a buton for close all recent app. :fingers-crossed:
[Xoom Android Development] brewer75:
Thanks for the suggestion about re-downloading due to the possibility of a bad one. Over the past couple of weeks I have dl'd every nightly that has been posted since the 9/14 one that works on my Xoom and I get the exact same message on every single one of them once I reboot. Obviously something is amiss but I still can't understand why the 9/14 build works fine, the other TeamEOS builds don't, AND the Cyanogenmod build works fine. I would like to stay with TeamEOS but since it looks like there wouldn't be a possibility of ever updating I guess I'll be forced to make the switch away from TeamEOS.
[Xoom Android Development] hochoch:
Have you tried a full wipe of internal memory, not just factory reset? And try booting without the SD card? I've been updating nightlies since this was re-released with no issues.
[Xoom Android Development] brewer75:
I've used TWRP to wipe everything except the SD card several times but get the same message. The two things I have not done are to boot without the SD card and a factory reset. I really don't want to do a factory reset since I assume it would require changing back to the regular partition then having to switch to big part. If it isn't a big deal I would be willing to do it but I can just keep Cyanogenmod 4.4.4 without having to do the big reset.
[Xoom Android Development] hochoch:
So you already went back to "small part"? Then yes, you would have to repeat that process. Factory reset does not undo big part tho. If you do, definitely try booting without the sd card and latest pa gapps just to rule everything out.
[Xoom Android Development] brewer75:
I am still "Big Parted" running Cyanogenmod 4.4.4. I guess I was under the impression that if I did a factory reset I would need to revert to "small part" and I really didn't want to do that and wanted to stay with "big part". So, if I can stay with "big part", do the factory reset, then use TWRP to flash the most current TeamEos 4.4.4 nightly as well as the 2.1 kernel and PA Gapps, I'll give it a try. However if it requires switching back to small part, etc. I think I'll just stay with Cyanogenmod 4.4.4.
[Xoom Android Development] hochoch:
the recovery is big-parted and unless you undo the process of the part and re-install a standard version of TWRP without the big part your tablet will stay that way using the recovery's factory reset tool. so feel free to switch between cm11/omni/eos big part versions without worry.
[Xoom Android Development] brewer75:
OK, I wiped everything again except the SD card in TWRP and did the Factory Reset. I populated all the information that is requested and Google is restoring all the apps that it has backed up. I've rebooted 5 times and everything seems to be working OK. I'll continue to do this and also see if it boots properly tomorrow. If this works or if it doesn't, thank you very much for your time and guidance! :good:
[Xoom Android Development] kmcrane:
About every couple months. (depending on the flashing) i will format internal drive. I load the rom and gapps on the micro SD and install from there.

I NEVER have issues and Xoom is always snappy.
[Xoom Android Development] brewer75:
Well, everything was humming along nicely UNTIL I re-installed Nova Launcher. I had been using Nova for several months with no problems but after the 9/14 wingray nightly I kept getting the "Unfortunately, the process com.android.systemui has stopped" message. I wiped everything and did a factory reset and everything was fine as long as I used the Trebuchet or Google Now launcher that was included in the build. I rebooted several times and everything was great. THEN I re-installed Nova Launcher and things were fine until I rebooted, then I got the "Unfortunately, the process com.android.systemui has stopped" message upon reboot. I restored the nightly and it booted fine and allowed me to change the launcher to Google Now and I have rebooted several times, all successful. So I have to believe the culprit is the Nova Launcher and I guess I'll keep the Google Launcher now and look into other launcher options.
[Xoom Android Development] Alxoom33:
I use Nova.Prime with no problems

Try clearing.Nova.data and reeboot.
[Xoom Android Development] brewer75:
I had deleted my Nova Launcher app so I downloaded it again from the Play Store just to give it a fair try based on your post. I deleted the data in the Settings menu and didn't even restore my Nova Launcher config that I saved on my SD card in case it was corrupted somehow. Then I rebooted only to find the same "Unfortunately, the process com.android.systemui has stopped" message I have been getting for a couple of weeks. I changed my launcher back to Google Now and it is working as it should. I am pretty certain that Nova Launcher is causing MY problems and it is something that has happened within the last couple of weeks. So based on my experience, I'm going to try other launchers for now.
[Xoom Android Development] m3adow:
I downloaded the newest Everest Nightly ( EOS-full_everest-20140928.222343.zip ), but mobile Data isn't working. I haven't even found a way to unlock my SIM card with a PIN, can't connect to any mobile net either. What am I doing wrong?
[Xoom Android Development] brewer75:
Since I have identified a problem using Nova Launcher (free) and no problems with Trebuchet or Google Now Launcher, I tried Apex Launcher to see if it would work on my Xoom. Sorry to say Apex Launcher gave me the same "Unfortunately, the process com.android.systemui has stopped" message so I wiped everything but the SD card, did another factory reset in TWRP and I'm back to using Google Now Launcher, but at least my Xoom is booting properly and I can continue to flash new nightlies!
[Xoom Android Development] hochoch:
awesome! i had problems w/ Nova on my old phone, but only when I restored a backup of my desktop. I'm pretty sure it also keeps some info on the SD card tho. did you try installing nova/apex without the sd card to see what happens? You should also search for "tesla" using es explorer to make sure you get rid of any old data from nova, SD maid might not be a bad idea either - could be some garbage on the external that's causing issues.
[Xoom Android Development] brewer75:
OK, in the continuing saga of trying to figure out what was messing up my Xoom, why the downloads weren't workable, and why I was getting the "Unfortunately..." message (see previous posts), I believe I have finally figured out the problem. I have determined that the problem is not Nova Launcher as I had first thought but it looks like it was my gapps. I have been using PA Full Modded Gapps and I would delete the apps I didn't want (e.g. Browser, email, exchange, android keyboard, telephony apps, etc.) with no problems. However, for some reason, after the 9/14 Wingray nightly, I started receiving the "Unfortunately..." message and I blamed Nova Launcher (see earlier posts). I have now determined that I can now delete SOME of the unwanted gapps but NOT all of the ones I used to delete, specifically NOT the telephony gapps. So, I may try other smaller Gapp packages and add gapps to them instead of deleting items but I'll probably just keep taking out the few items I really don't want. I have flashed a couple of new nightlies and have now re-installed Nova Launcher and everything is working smoothly! :good:
[Xoom Android Development] dkahs23:
Anyone tried the latest?
[Xoom Android Development] RedWingsFanEd:
I have been with no problems yet.
[Xoom Android Development] brewer75:
I had been having problems with previous builds I flashed but got that all sorted out (I think). I flashed the 10/2 Wingray build a couple of days ago and it is working fine. :good:
[Xoom Android Development] bigrushdog:
Guys did the last build available get Ota support? Go to settings/about/Eos updates and see if something new and fantastic happens.
[Xoom Android Development] brewer75:
I just tried what you suggested and maybe I'm missing something but I don't see anything different than before. When I selected EOS Updates it opened the downloads.codefi.re/teameos/nightlies/MOTOROLA/wingray screen with all the updates listed from July 20 through Oct. 2.
[Xoom Android Development] TheMan0790:
I saw the commits on the Team EOS GitHub page, but when I tried it, it brought me back to the downloads website as it did before.
[Xoom Android Development] Alxoom33:
Nice! Like the built in updater BRD. Thanks Man!
[Xoom Android Development] brewer75:
I just downloaded and flashed the 10/6 Wingray nightly and I too like the build updater. I reset the check frequency to daily instead of weekly so I don't miss any of your fantastic work! :good: