yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] cviniciusm:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Umts_Everest / MZ601 / E

Yes, build #149: http://jenkins.teameos.org/job/umts_everest/lastSuccessfulBuild/

Enviado de meu XOOM MZ605 (Android 4.2.2 pelo Team EOS 4).

---------- Post added at 09:34 PM ---------- Previous post was at 09:17 PM ----------

It's so beautiful: clang++; ISO C++ 11 and so on!

It's no just plain Java neither plain Android.

C++ is very alive!

Enviado de meu XOOM MZ605 (Android 4.2.2 pelo Team EOS 4).
[Xoom Android Development] new-noob:
installing 149 :)

Thanks Developers!

...whats the chance xoom will run multiwindow apps like some other devices?
[Xoom Android Development] abbots:
just installed 149, thanks Team EOS & BRD, all's well

did full wipe+ fac res

(dumb) question:

when I go to apps screen, home button doesn't take me back to 'desktop' ?? back button does go to 'desktop'

is that correct...?

later-------------------

ooops, problems... Play didn't install

I re-flashed gapps-jb-20130105-EOS-XOOM-ONLY, but still no Play

is that something I stuffed up... or ?

I'll try re-flashing, using cwm 6.0.2.3

later-------------------

re-downloaded EOS-umts_everest-20130318-149, reflashed

hangs on EOS color logo, logo pulsating, but after 5 minutes still on pulsating logo

how do I recover from here ?
[Xoom Android Development] hawkstorm:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Umts_Everest / MZ601 / E

Try restoring from a back up. I'm having problems with the gapps as well. None of them were working when I flashed 149. Anyone else facing the same?
[Xoom Android Development] abbots:
I've reflashed CWM recovery-clockwork-touch-6.0.2.7-wingray-signed.zip

now I'm stuck at "RSD mode 3"

all searches I find with RSD are from around 2011...
[Xoom Android Development] narin99:
Just installed V149,

Every thing is working fine...

TEAM EOS , THANKs again,
[Xoom Android Development] cviniciusm:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Umts_Everest / MZ601 / E

The same for me.

I used Goomanager to download and install build #149 and gapps with clean cache and dalvik cache, no need to factory reset or wipe something. I'm using TWRP recovery installed by Goomanager.

Enviado de meu XOOM MZ605 (Android 4.2.2 pelo Team EOS 4).
[Xoom Android Development] abbots:
getting desperate

I'm going bad to worse... in trying to recover...

I took out 'boot.img' from 149 archive and, managed to flash as below:

C:\motorola>fastboot flash boot \motorola\xoom149\boot.img

< waiting for device >

sending 'boot' (4462 KB)...

OKAY [ 0.844s]

writing 'boot'...

OKAY [ 1.766s]

finished. total time: 2.609s

C:\motorola>fastboot reboot

rebooting...

finished. total time: 0.266s

BUT, when I boot, I go to:

RSD Mode 3

*if* I keep pressing Vol- at red moto log, I end up with red moto log

suggestions ?

later>>>>>>>>>>>>>>>>

somehow, I managed to re-flash cwm 6.0.2.7 recovery, and, can boot to it

I've did fac res full wipe, flashed 149n, boot to EOS links logo, logo is pulsing, but, can't get past that...

what should I do next ?

later>>>>>>>>>>>>>>>>

apparently, if enough monkeys are given enough typewriters....

and, apparently, if I keep performing enough random actions, I can fix anything, or, whatever...

re-flash. re-format re-this, re-that re-do re-try, re-start

booting to 149n again !! now, to re-flash gapps....
[Xoom Android Development] hawkstorm:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Umts_Everest / MZ601 / E

I managed to get my gapps working by re flashing the gapps package from the forums but Google now still crashes. Is anyone else getting the same? Is there a fix?
[Xoom Android Development] romdroid.:
Which build is the most stable to date?

Anything I need to think about coming from EOS 3.0?
[Xoom Android Development] hawkstorm:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Umts_Everest / MZ601 / E

I've been using this rom since 146. It's generally been really stable aside from Google now for me. Really enjoying the rom.
[Xoom Android Development] attmakesmevomit:
Have you disabled the hotword detection on Google Now as discussed previously in this thread? If Google Now was working for you prior to the latest update, this may be your issue.
[Xoom Android Development] abbots:
I've used most of the nightlies, all are good, imho, I'd use the last one, 149

(I struck some glitches, unrelated to actual nightly, all's good on my Xoom 149n)

make sure you use compatible/recommended recovery (1st page);

'stuff' gets moved to a new sub-dir '0' after migrating, so, backups and stuff not immediately located after install

good luck
[Xoom Android Development] abbots:
keyboard folds up

lately I struck the following issue, across different apps, what's causing it?

I open a text entry box (email, browser url bar), cursor appears, keyboard pops up

I enter one or more characters, when, suddenly, keyboard folds down off screen

if I re-select entry box, after a brief delay, keyboard will pop up again

sometimes, need to do this couple times

it's almost impossible to enter any text, it seems to afflict any text entry box, what's causing this ..?
[Xoom Android Development] bigrushdog:
I'm gonna jump off a building if I see one more post on the stupid keyboard. I'm scrapping keyboard all together and throwing in the first free market keyboard I can find.
[Xoom Android Development] abbots:
please don't, we need you!!

sorry, I didn't realize the issue was with the built-in keyboard, in the past, I've never seen this problem (but I've used an alternate keyboard..)

I was trying to optimize my Xoom, hence, decided NOT to reload everything at once, just, start plain vanilla and go slowly adding stuff...

hacker's keyboard installed

apologies again! thanks for great ROM
[Xoom Android Development] bigrushdog:
Keyboard is borked on Xoom, due to gapps. Nothing we can do. Definitely run with a third party keyboard. I'm backing away from the ledge now :p
[Xoom Android Development] nkahoang:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Umts_Everest / MZ601 / E

Hacker keyboard, that is the one you need. Free, stable, control bot/console compatible

Sent from Motorola DynaTAC
[Xoom Android Development] hawkstorm:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Umts_Everest / MZ601 / E

I just found this out. Thanks!
[Xoom Android Development] narin99:
Keyboard issue is never bothering me. I always use the third party app with Thai language.
[Xoom Android Development] new-noob:
+1 for Hacker Keyboard, and no issues with latest builds

however, do you guys have lags in 149? Since the update its been strangly laggy here..
[Xoom Android Development] hawkstorm:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Umts_Everest / MZ601 / E

Not really. Only lag I'm getting is when I'm updating apps and a bit when I'm typing
[Xoom Android Development] new-noob:
Strange so, cos my 149 was laggy so went back to 148 and feels smoother...waiting on 150 ;)
[Xoom Android Development] narin99:
V 150 is out
[Xoom Android Development] hawkstorm:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Umts_Everest / MZ601 / E

Just downloaded and flashed #150. No hitches this time. The gapps worked fine after updating and the migration overall was smooth. No bugs so far and the lags during typing and updating apps is not too obvious now. Amazing work devs!
[Xoom Android Development] RJWebster:
Google Toolbar

Having loaded the 149 nightlies, first let me say "Kudos" to Team EOS! Amazing piece or work!

I am very happy with the way this ROM functions, but would like to know if it's possible to either delete or modify the Google Translate Toolbar that sits above my home screen like some sort of vulture. It's taking up screen space that I would rather put to better use.

As well, is it possible to modify the button at the bottom that takes me to to the sub-screens?

I know that I am picking at nits here, but if would make a great ROM even better.

Thanks in advance any assistance.
[Xoom Android Development] Chaosgod27:
sweep2wake feature doesn't work correctly, well it half does. It can turn off the screen but can't turn it back on. When it does there is either a white background or black with weird colours. Is there an option to turn the feature off? This is nightly 150 of course. Can do logcat if required.

Edit:

It sometimes works when turning it back on. You can catch me on IRC, as I'm usually on there when I'm online.
[Xoom Android Development] jamie_lee142000:
my device has had weird colours screen too, and now it totally stopped responding, and it also not coming up on the computer... cant do hard reboot as im missing the volume button, gunna have to wait till the battery dies... if it does.
[Xoom Android Development] Chaosgod27:
Odd, I can still hard reboot if it ever freezes and doesn't work. Since you can't do an adb reboot I guess you have to wait until the battery dies, though that might take some time. All the best.
[Xoom Android Development] hawkstorm:
I'm not sure if it's sleep2wake. But I've realized that my screen is timing out (i.e. switching off) even when i'm actively using the device since installing #150.
[Xoom Android Development] cunnie84:
Im not using sleep2wake and ive had that a few times too
[Xoom Android Development] emaxxim:
This definitely the sleep2wake feature. I try before the Elemental Kernel with s2w and the device doesn't turn on neither when pressing the button on. Please Team EOS fix this bug.
[Xoom Android Development] emaxxim:
I don't know if this could help but if you want to disable the sweep2wake you can write this in your terminal:

echo "0" > /sys/android_touch/sweep2wake

Or you can download "Sweep2Wake-Widget" from Google Play (the credit goes to Xmister).

I just install Trickster MOD and try with this tool to stop the strange behaviour of my Xoom. I'll let you know.
[Xoom Android Development] cunnie84:
Its definitely not the sweep2wake feature because i have not got the Elemental kernal on my xoom im just using the eos rom on its own im afraid its a bug in the rom, its happend now around 15 times since i installed the 150 rom, was hoping 151 would fix it until the build failed:(
[Xoom Android Development] emaxxim:
Cunnie84 I'm not clear. The Xoom (Everest model) have some problem with the kernel with the sleep2wake feature, like the last one inside the release #150 EOS Rom and the Elemental. For what I know this feature (the s2w) works only in some model of Xoom, like the Wi-Fi only. I don't know what is the problem but I post the log, sometimes ago.

Cunnie84 And trust me the s2w is in the #150 Team EOS, look some page before where is the notice of the publication.
[Xoom Android Development] Doc Franky B.:
AW: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Umts_Everest / MZ601 / E

#152 is out :)
[Xoom Android Development] hawkstorm:
Just installed #152. The rom is alot smoother. But only thing is that sleep2wake issue which seems to be exacerbated in the update. Every time I try to pull down the notification shade the screen goes blank and can take anywhere between 30 seconds to 2 minutes to respond to the power button.
[Xoom Android Development] narin99:
After installing V152, My Xoom is a very okay...
[Xoom Android Development] barttech:
Awesome, I'll be installing the latest version tonight.

Quick question, is issue 288 fixed (see bugs site - I cannot link yet, unfortunately)

Bug:

Sometimes I can see 3g connection symbol but apps can not connect to internet. If I turn airplane mode on and off then apps can connect to the internet

I attempted to provide a little bit more information, but this is the only reason I'm using stock rom right now. Very annoying bug :(

But otherwise it's a fantastic rom!
[Xoom Android Development] schrej:
AW: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Umts_Everest / MZ601 / E

I'm also suffering from this bug. If I'm loosing 3G, then the Xoom does not reconnect automatically. This is especiallyvery annoying when you are on a train ride.

Gesendet von meinem MZ601 mit Tapatalk 2
[Xoom Android Development] new-noob:
Beautiful stuff these new 152 update, my tablet goes smoother now.

Thank you dev team!
[Xoom Android Development] huskysdg:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Umts_Everest / MZ601 / E

Use a launcher as Nova or similar and get rid of things you don't like on the screen...

Enviado desde mi MZ601 usando XDA Premium HD app
[Xoom Android Development] kdx200:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Umts_Everest / MZ601 / E

Hi friends, this 152 have a lot of hangs and too much wakeup problems. Ive been using this rom since the 80 and is fantastic. Please eos boys, fix this silly problemas to get the most of our beloved xooms.

Thank you very much!
[Xoom Android Development] cviniciusm:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Umts_Everest / MZ601 / E

No problem for me.

Show us detailed information about the issues and not only complains.

Enviado de meu XOOM MZ605 (Android 4.2.2 pelo Team EOS 4).
[Xoom Android Development] argiris:
I have the same problem on mz601. When I let the device for about 1 hour without to touch it, when I try to weak it up (with sweep2open) nothing happens. Even with the start button the device does not wake up. And I must reset the device (start button + up volume). On version 150 I didn't have that problem.
[Xoom Android Development] hawkstorm:
What do you mean by show? Is there a log or something that I should post for the problem?

Similar problem here. Only thing is when I wake the device from sleep and want to check notifications of access the quick settings menu, the screen just shuts off immediately. If I have an app running it usually hangs and then the screen shuts off and the device sleeps. I tried increasing the timeout from 30 seconds to 1 minute but still the problem persists. It's been ongoing since 150 for me but it wasn't as apparent as in the latest nightly.

Also, is anyone getting problems trying to Bluetooth tether? My computer doesn't seem to be able to connect to the Xoom as an access point and I keep getting a "Bluetooth Peripheral Device" in device manager with no driver. I tried with my Atrix 2 and GNex and I'm able to do the bluetooth tether (connect as access point) without any problems. Is it the ROM or is it a driver problem in my Windows 8 Machine? Is there something that I can do to fix this? I'm using the MZ601 with a 6GB data plan to allow for tethering.
[Xoom Android Development] kdx200:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Umts_Everest / MZ601 / E

No, i have not try or use the bluetooth. Now with this 152 the only problem detected is the hang and inmediatly boot or the no-wake up.

In the 150 i have no issues.

Greets
[Xoom Android Development] hawkstorm:
Just installed #153, works alot better than #152. The screen bug seems to have toned down as per #150. But it's still there. I'm still having that issue with the bluetooth tethering - is there a fix on windows 8 for it or is it a software bug on the XOOM?
[Xoom Android Development] bigrushdog:
umts_everest Bluetooth tether fix test build. should be able to broacast a signal and connect to a signal.

download
[Xoom Android Development] realjumy:
Tethering from tablet to phone working fine. Thanks.
[Xoom Android Development] bigrushdog:
Great to hear! Try tether from phone to xoom.
[Xoom Android Development] realjumy:
Bad news, is not working from Tablet to phone, I don't realized I was using the SIM connection. SORRY. The Bluetooth logo is grey and looks like there is not real link with the tablet when tethering from tablet to phone... But tethering from phone to tablet is working fine.

When tethering from phone to tablet, I have no connection until I go to Settings, Bluetooth, I press on my phone and mark "Internet access". Then, the Bluetooth logo turns blue and works fine.

The "Internet access" option don't appears when I try to tether from tablet to phone.

Again... SORRY!
[Xoom Android Development] r@fel:
white screen when lock out

Hi guys,

Just installed build #153 (wipe cache, dalvik cache, /system), not bad at all :)

I noticed an issue when screen was off : I clicked on the power button to turn the screen on, then I got a white screen, so I was not able to draw my security schema. I disabled the schema and not reproduced since, so I guess it was no big deal :p
[Xoom Android Development] pots22:
153 ?

Hello with the 152 on the desktop when i go to the right or to the left for see the differents screen, the tabt don't react with the normal fluidity + when i type on different icons a litel time to react. (i start from a proper instalation OTA ICS + Directly The EOS 152 with a full wipe)

(compare the CM 10.1 nightly fron the 01/04/2013).

And a lot of time when the tab go in sleep mode nothing happend obligation to reboot.

My question is the 153 make ameliorations for this ?

---------- Post added at 03:09 PM ---------- Previous post was at 02:59 PM ----------

Hello again,

I'm a fanatic of EOS team, use Rom from EOS 2 to EOS 4

But i have a question for senior member, what's the best ROM ? the EOS 4 or the CM 10.1 ?

Some time when i use CM 10.1 i think it's like a fake not a real JB 4.2.2

Thank's for advance :confused:
[Xoom Android Development] hawkstorm:
I'm guessing the reboot bug in 4.2.2 is a bug in the source code in general cause i've had my GNex running stock 4.2.2 do the same with random reboots which occur from time to time. But other than that, #153 is worth the update. It's a whole lot smoother than #152 and addresses a lot of the issues.

So I just flash this fix using TWRP? It's quite a big file isn't it.
[Xoom Android Development] pots22:
153

I make a full wipe of CM 10.1

Install the EOS 153 and 1. After choose language, i choose my wifi and like the 152 stay there and block 5 minuttes and after ask me for my GMAIL acompte and continue the configuration.

2. All work perfect but the wallpaper of CM 10.1 stay?

3. For configure my APN keyboard come and go ?

Finaly i install all applications give the tab to my wife today and wait tonight what she say :laugh:
[Xoom Android Development] afpapa:
Απ: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Umts_Everest / MZ601 / E

154 is out!

Happy download to everybody!
[Xoom Android Development] hawkstorm:
Hey bigrushdog,

I tried flashing your fix. Still unable to tether. I tried using my Motorola Atrix 2 (Stock 4.0.4) to connect and tether, it could detect the Motorola XOOM MZ601 but could not utilize the internet from the Bluetooth connection. Also tried connecting my laptop to the XOOM but still the same as before.

The option for Access Point in the Connect using menu isn't there. However, I realized that the device is not being detected properly when its installed via Bluetooth - there's an unknown Bluetooth peripheral device. When I tether from my A2, there are 2 additional devices under the profile "Bluetooth MAP_MAS" and "Bluetooth Handsfree AG" .

---------- Post added at 01:50 AM ---------- Previous post was at 01:38 AM ----------

Just installed #154. The ROM seems a lot more stable compared to the previous release. the sleep2wake bug seems to have been squashed!
[Xoom Android Development] bigrushdog:
Fresh build cooking. Adhoc support from Timduru from our tf101build! Works perfect for them, should work just the same here.
[Xoom Android Development] pots22:
keyboard

Hello, the 156 is on

Is this keyboard come and go problem solved ? or never issue ?
[Xoom Android Development] realjumy:
You need to install a keyboard from the market. Is a problem with the Google Apps that can't be solved.
[Xoom Android Development] new-noob:
Hey, can anyone confirm the screen bug has been fixed?
[Xoom Android Development] abbots:
Is 'reset to factory' from booted Xoom/settings option a supported option?

After installing 156, tried 'factory reset' from settings, Xoom wouldn't boot on reboot, was stuck with Moto logo.

If it is not working, perhaps can be disabled?

Anyhow, reinstall from CWM worked, all's well,

Thanks for great ROM.
[Xoom Android Development] kdx200:
Up to now the 156 is better than 154 and 155 about the wake up problem. Only once in a couple of hours. for example the 140 was no wake up issued problema.

The new issue is the lock screen. Its always goes to non landscape mode with some menu at the bottom such as Notifications and the google bar. The unlck button works fine.

Somebody has realized that?

Thank you!
[Xoom Android Development] realjumy:
Something weird... Using the tablet when screen turns off. I need to press the power button to wake up the tablet. However, the system flows better. Thanks team EOS!
[Xoom Android Development] nec_d:
Is there any solution about the sound lag? Everywhere., in every app the sound has a delay of 100-200 msec
[Xoom Android Development] RoWeKo:
The setting of sweep2wake doesn't persist, which means the checkbox doesn't stay checked when you leave the settings. S2W works good but you can't disable it.
[Xoom Android Development] bigrushdog:
I'll push another update tonight. I thinks it's a wonky init.d script. S2W is tricky to get right without being able to test the feature.
[Xoom Android Development] hawkstorm:
Sorry to ask.... I'm a bit new to the issue.. . but what's the problem with the Google apps?
[Xoom Android Development] nec_d:
+1 for the persistence.

is working good, but with keyboards like swiftkey that letters are very close to the edge of the screen, sometimes the device is locking when typing fast.
[Xoom Android Development] realjumy:
I think that the problem is that the keyboard is not built for non-Neon compatibility. I'm not pretty sure, but is something like that.
[Xoom Android Development] hawkstorm:
Ah... that makes sense. I'm guessing the coding for it is a pain to port foe non neon compatibility
[Xoom Android Development] badaas:
http://db.tt/bWOddT4x

I'm using Xperia z keyboard lite, works brilliant ^^^

There's a thread on xda but can't remember where...

Bug: notifications toggle panel airplane mode won't toggle.
[Xoom Android Development] realjumy:
Airplane mode working fine here...
[Xoom Android Development] badaas:
It works yes, but won't toggle from notifications bar.
[Xoom Android Development] hawkstorm:
I'm assuming you mean the bar with all the toggles. I just tried it and it managed to toggle the airplane mode on and off.
[Xoom Android Development] badaas:
Must be random then as its not working here and is noted in eos bug list online
[Xoom Android Development] RoWeKo:
Thank you for the keyboard! Installed it via recovery and it's great. No need to install a keyboard from market annymore. :laugh:
[Xoom Android Development] hawkstorm:
I'm wondering... are there any non neon devices running 4.2.2? Are all tegra devices non-neon?
[Xoom Android Development] Doc Franky B.:
#157 is out :)
[Xoom Android Development] narin99:
Just intalled V 157...

Sweep2wake was gone...

I still love to have it...

edited -----

Sorry I just see how to enable it in the EOS control center...

Thats' great!!!
[Xoom Android Development] gucio1200:
Mobile data

How some1 problems with mobile data, or only i'm so lucky ?

After some time on mobile data its starting too "looks grey" and then i have to use airplane mode or turn off mobile data off nad turn in again on to up it. Is it a bug ? Wants log guyz ?
[Xoom Android Development] RoWeKo:
+1

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Xoom Android Development] kdx200:
Hi friends! Now aim on 157. In my xoom the problem with the lock screen continues. Never goes to landscape mode and the screen is horrible like if its in another resolution.
[Xoom Android Development] schrej:
+1

Additionally any dropout of connection needs a toggle of airplane mode.

Annoying during a train ride.

I'm on 157

Gesendet von meinem MZ601 mit Tapatalk 2
[Xoom Android Development] gucio1200:
Ok i think i have found sth. Set mobile data static to operator in settings to get it perm working - now i'm testing it so will say if it is solv by that. At this time xoom working whole day and didt get this problem yet.