yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] masterslacker:
1% battery mod?

Thanks Team EOS for such amazing work and clearing up all the little bugs from the past few weeks! I been on build 141 since it came out, and I haven't had any apps slowing down or crashing like they used to since 128. Keep up the great work!

I have a question / request: Is there any way you could add in support for 1% battery mods?? I've been trying for the last few hours to do it myself, and all I've manage to succeed in doing is removing the battery icon. Here's what I've tried so far:

- I've tried decompiling the SystemUI.apk and framework-res.apk, modifying the necessary stat_sys_battery.xml and stat_sys_battery_charge.xml files in the res/drawable folders, and adding all the images into the drawable-mdpi folders. I then recompiled the files, made a CWM flashable file, and flashed it. The system boots ok, no force closes, but I get no battery icon at all (and I checked the settings to make sure the check mark is on).

- I tried using UOT Kitchen to do the modifications for me, but I get the exact same symptoms - no icon at all, but no force closes or bootloops.

So, I'm not sure what I'm doing wrong. Is it possible to get something like a 1% battery mod baked directly into the rom? It would be awesome if that could happen.

Thanks Team!
[Xoom Android Development] Legato Bluesummers:
There is the 1% mod baked into the rom. Always has been. Mine says 37% right now. Motorola phones have the 10% issue. Not the Xoom

There is an option under interface to display battery text instead of just the pic. That's what I do. I'd rather see 37% then a partially full bar.

--Sent from GlaDos baked potato
[Xoom Android Development] Taysider:
I get it sometimes, more so when I'm using Google reader, currents and Gmail

Sent from my Xoom Powered by EOS 3 using Tatptalk 2
[Xoom Android Development] Eun-Hjzjined:
I do the same with my xoom. I don't get any problems when doing that. Is the music local or is it coming in over wifi, eg digital radio?

I had an issue with di.fm on 139 but its gone now on 141.
[Xoom Android Development] vimesUK:
Didn't there used to be an option to set that would reduce the brightness as well as increase it when using the Auto function for the light levels...?

I could have sworn that this had to be set in the developer settings for the Xoom to reduce its light levels when using the Auto brightness function...?
[Xoom Android Development] okantomi:
Thank you kcrudup and all of the eos Xoom team!

You're keeping my Xoom alive...well, better by far than when it was brand new!
[Xoom Android Development] elsworth1983:
Cheers Team Eos just got back from my holiday from Wales and the 1st thing i did was DL 141 ;) running great
[Xoom Android Development] masterslacker:
Thanks, but that's not what I am referring to. I am aware of the option to have the battery percentage show as text next to the icon. But it just that - text. What I was asking for is to change the current icons from a set of 16 (8 discharging and 8 charging) where each icon is shown for a range of percentages, to a set of 202 (101 discharging and 101 charging) where each icon is shown for a single 1% level. The current images could be duplicated for each 1% level as needed, as long as the XML files are edited properly to make use of them.

If that support was built directly into the rom, I could make my zipthemer package and flash my theme (including battery images) whenever a new build comes out, without having to do a crazy amount of decompiling of packages. Without that support, I'm stuck with generic battery icons that have no detail on them (I'd have to use the text option to get that detail).

If anyone from Team Eos wants to look into it, great! If you want more detail, I can give all the manipulated images and XML files, and it would look exactly the same as it does now. Just PM me for more information.
[Xoom Android Development] FAR1007:
SD Card Won't Mount

Hey this has probly been covered but did not see it. I have a root wifi only xoom. I flashed the Jelly bean build 137, then I updated clockworkmod from 4.0.0.4 to 5.8.3.1 and now I am unable to see or mount the internal card or view updates on my SD card. Any help is much appreciated.
[Xoom Android Development] bigrushdog:
I've been meaning to put some focus on battery. Put other mods have taken priority. However, you could help by getting together the needed xml, and maybe 3 or 4 icon sets. But keep in mind, this mod borderlines with the theme engine world. But get the resources together and we'll go from there.

Edit: oh btw do try our gnex and nexus7 builds. Aokp kicks ass for sure but our benchmarks blow them out the water. :D
[Xoom Android Development] bigrushdog:
Try twrp. Or start putting updates on internal storage. MicroSD cards on phones is dying out.
[Xoom Android Development] runandhide05:
I have some nice xlms for 1-100 animation for charging and what not I'll put a link up in a min

here is the xml for @drawable for 1% with a nice little addition for charging animation

here
[Xoom Android Development] masterslacker:
I did try the EOS3 build on my Nexus 7, and it seemed pretty stable, and I definitely liked the tablet/phone mode changer concept for the system bars. Ultimately I went back to AOKP because I liked a few of their customization options that EOS just didn't have. Any thoughts to implementing something similar to what the ParanoidAndroid rom accomplishes where each app can be set to phone/table mode as well?

Wow! That was fast! I just finished working on mine, and attached it to this reply. It is a little simpler than yours during the charging portion - at each step while charging it swaps back and forth between the charging icon and normal icon. I checked out your charging animation xml, and it look interesting, but I think the effect will definitely vary with the icon set used. Speaking of which, I also included the standard icons (with all the duplicates necessary for a set of 202 images), as well as the circle set that I use from UOT Kitchen.
[Xoom Android Development] Sihaz:
please only make this an option if you do it - some of us prefer the nice simple battery icons. thanks as always for the best rom :)
[Xoom Android Development] waz675:
^^^^™This and also paths changed, /storage/sdcard0 is internal, /storage/sdcard1 is microSD in the actual rom so you'll need to edit file managers to reflect the new paths.
[Xoom Android Development] Taysider:
Just downloaded new gapps for 4.1.1 and working great

Check it out over at Rootzwiki

http://rootzwiki.com/topic/31532-gapps-411-424425-jro03o-gapps-package-831/
[Xoom Android Development] okantomi:
Unless I''m mistaken, non-eos gapps cause problems with eosXoom jb builds because of super limited system storage space. But good luck.
[Xoom Android Development] runandhide05:
correct(ish) for other devices its OK, because there is plenty of room on the system partition for others but XOOM has a limited amount after jellybean is on there, so eos system links many things to the data partition to allow all the gapps data to install properly
[Xoom Android Development] doumer:
Currents is working again on #141, thanks :)
[Xoom Android Development] Jimmiray007:
Nightly 141

Netflix is also working... at least for me
[Xoom Android Development] pkelly517:
has anyone seen an issue with

Settings->WiFi->Advanced->Keep WiFi on during sleep?

Mine will not stick to "Only when plugged in'. It keeps moving to Always.

Thanks
[Xoom Android Development] elsworth1983:
Just checked mine and I can highlight either one and it stays on the one I have selected? So I don't have that problem :rolleyes:
[Xoom Android Development] adityamunshi:
Im on 141 too, wifi is set to always but keeps dropping the wifi connection randomly.

Another issue ive seen is with overclock, say i set the max freq to 1600, select apply on boot and reboot. After rebooting it displays max freq as 1600 but remains stuck at 1000mhz.
[Xoom Android Development] drewski_1:
Maybe the governor throttling down the CPU?
[Xoom Android Development] adityamunshi:
Dont think so,at idle the settings menu reads something like Current 1000Mhz, Set at boot: 1600 Mhz
[Xoom Android Development] z1gackly:
This is a problem with every custom JB ROM for the Xoom. As far as I know EOS team are the only devs to have addressed this with their own gapps package. Both the Rogue CM10 builds and Codename Android builds will suffer random instabilities with their recommended gapps packages unless you make room in the system partition after flashing the ROM but before flashing the gapps. You can do this by trimming down the system/media filespace of video and audio files you don't use. I would guess flashing non-EOS gapps with EOS would require the same procedure.
[Xoom Android Development] MARIANOTE:
I have one strange issue

when i receive some notification (whatsapp, gmail....) with screen off, i cant back it on wiht the powerbutton and need to wait some seconds (10 sometimes) and then powerbutton works and screen si on.......

any idea?

Good work EOS!
[Xoom Android Development] Taysider:
I've started getting the same problem :(

Sent from my Xoom Powered by EOS 3 using Tatptalk 2
[Xoom Android Development] bigrushdog:
Yes of course. In theory it would simply be part of battery options we already have.
[Xoom Android Development] drewski_1:
Oops. Wrong thread
[Xoom Android Development] scottgti:
I've had this since #127. I have mentioned it a few times, as well as others. Seems like most people don't have this problem. It seems like the tablet crawls to a stop, becoming unresponsive. I have factory reset with no help. If I wipe system and flash #127 all is well. I have tried every nightly since.
[Xoom Android Development] nadiros:
Edit* was actually referring to your quoted text... the notifications and not waking from sleep issue.

Try raising your minimum cpu clock up to the 300 mhz step. Might help. I forget the exact mhz but raise it up one step and see.
[Xoom Android Development] tdarren:
Does anyone know a reason why the system partition has limited space available to custom ROM's?

Never really been explained.
[Xoom Android Development] runandhide05:
because the device was released with honeycomb and at that time the room was more than enough, two operating systems later the OS has grown in size and therefore leaves less space on the original partition size.

and without the Motorola tools that are not open to the public the device itself can not be repartitioned to increase the system partition size
[Xoom Android Development] z1gackly:
Limited forethought, essentially. Who would have expected that from Motorola?
[Xoom Android Development] TheJeeks:
141 has been A mazing so far.
[Xoom Android Development] adityamunshi:
And no chance of a possible fix in the future ? The Xoom has a bit of life left in it... :highfive:
[Xoom Android Development] rw6497:
What are the chances that we could get Sony bravia engine cooked on jellybean. It should enhance of xoom screens by a lot. I have it on my epic touch and it makes a tremendous difference.
[Xoom Android Development] lancemoreland:
Over clocking doesn't seem to be sticking after a reboot. It always reverts to 1000 MHz.
[Xoom Android Development] waz675:
Mine sticks for sure.
[Xoom Android Development] elsworth1983:
I have just had to do a full wipe :( my Xoom went really sluggy I don't know if it was due to the fact I was on 139 then jumped straight onto 141 on Friday. Everything seems fine now after the full wipe :D
[Xoom Android Development] sygys:
Just wanted to mention that my official motorola keyboard isnt working with build 141. It pairs but is does not respond to key presses. Same problem with the official mouse. I get the message that i inserted the wrong password. But didnt got any screen to put it in.

Mouse all of asudden does work
[Xoom Android Development] slab100:
Hi,

does anyone know if the "hide status bar" is available on this rom as it was on ICS?

I cant find the option

cheers!
[Xoom Android Development] villain_allain:
The 141 i think was the best so far.

I just want to know if we can change the icons to the normal xoom rom?

The one that have glow in it. Thanks.
[Xoom Android Development] epic118:
Miles better than Moto's Jelly Bean. Will be on this ROM for a while.
[Xoom Android Development] Warell:
Just installed 141, and running flawlessly so far.

Thanks a lot, Team EOS!
[Xoom Android Development] thenay844444:
Mine is fine too.

Just did a wipe cache, dalvik and batt.

Updated to 141 and latest gapps.

No issues.
[Xoom Android Development] pkelly517:
My power button is acting up. Is the 'Wake on Volume Key' option available yet?

I looked though the settings, but didn't see it anywhere. But, as I get older, not seeing something doesn't mean it doesn't exist.

---------- Post added at 04:45 PM ---------- Previous post was at 04:33 PM ----------

I guess I wasn't clear.

I can select any of the options. It even says that Never or Only When Unplugged is the current selection.

First time the sucker goes to sleep, though, it reverts back to Always, and WIFI signal is never dropped.

How accessible is this setting to the rest of the system? Can any app change it? If that's the case, then I guess I start the process of killing apps one by one until I find the culprit. But if it's more at a root level, then I start with the SuperSU apps.
[Xoom Android Development] eddyther:
I selected "only when in charge" (i am translating from spanish) and it works fine even after suspending.

There is not a single ecosystem, not the same for all of us. We all have the same rom and hardware, but with very different behaviour.

It happens since the old "win ce" times...

Try a full whype
[Xoom Android Development] pitokellie:
I can't find Google now.is it out of this ROM?
[Xoom Android Development] fleury14:
Works fine... Tap on the search bar.
[Xoom Android Development] pitokellie:
Don't have search bar
[Xoom Android Development] russtyd:
Confirmed - set #141 to 1504MHz, takes OK, reboot and says Current value: 1000 Mhz Boot value: 1504MHz.

Not seen any other issues though, and ADW launcher works very well , better than ICS which had some weird issues with menus drawn offscreen!

---------- Post added at 03:14 PM ---------- Previous post was at 03:13 PM ----------

So can we / should we use the non-EOS updated gapps?
[Xoom Android Development] runandhide05:
you should not use non eos gapps on the Xoom with eos jellbean ROM
[Xoom Android Development] drewski_1:
hold "Home" softkey down.

swipe diagonally up/right to where the white Google circle is.

you can do this in one quick motion too, but holding "Home" down the first time shows what you're aiming for.

Google Now is the stock JB "home swipe" behavior, but in EOS the behavior can be customized with the "Ring Targets" in the Interface section. there are 3 possible targets, but only #2 is pre-set (to GN)
[Xoom Android Development] scottgti:
Or there wasn't enough room in his system partition. If the home key works, great. If not, wipe your system, flash ROM and gapps again. :thumbup:
[Xoom Android Development] Dyelon:
I second the notion of implementing wake with volume key....would be useful
[Xoom Android Development] h0lyc0w:
I just got on the EOS JB bandwagon, and I must say I'm impressed with this ROM. Very smooth and stable. I came from CM9 nightlies and have waited for CM10 nightlies to officially begin. It doesn't matter now. I'm sticking with EOS.

One thing I've missed from CM9 is the option to setup profiles for things like sound, network, etc. Is this something on the EOS roadmap?
[Xoom Android Development] edd247:
has worked fine for me
[Xoom Android Development] waz675:
Your tablet msy not like 1504 during boot so defaults backnto 1k. Try setting 1200 MHz reboot and see if it sticks. If so, try next value up until it's stable.

If 1200 MHz doesn't stick,well you got a problem, my 1200 speed has been set since 141 initially came out and it's still set,just checked.

---------- Post added at 07:12 AM ---------- Previous post was at 07:05 AM ----------

I had that problem pot sabzbd page not lowdown,using new dolphin beta with 141 has fixed it plus dolphin finally doesn't crash/stop during day to day running
[Xoom Android Development] bigrushdog:
Not likely. Theres third party apps like Tasker that can do that just fine.
[Xoom Android Development] adityamunshi:
What about wifi direct? was the feature removed from JB or is it just not available for Moto Xoom ?
[Xoom Android Development] highKo:
went back from eos for some days. are the streaming issues (youtube etc.) solved in this time? was on cm10 nightlies but eos builds felt a bit smoother so that i wanna come back
[Xoom Android Development] Eun-Hjzjined:
Was going to ask this yesterday. I have some large files on my note I want to copy to my xoom, but copy to sdcard, move sdcard, move to xoom, and put sdcard back in my note seems like a few to many steps to justify a multi gigabyte transfer. Not to mention I gotta shut the dam note off to get the fracking sdcard out/in....

Running AOKPb1-30 | flaps 1.1
[Xoom Android Development] Geeba:
Hello all - I was just about to jump on the EOS ROM as the stock one is having problems...

But what is:-

"Temporary Gapps package gapps" I read in the first post? - can I not install the latest ones off Google Play when I install the this ROM?
[Xoom Android Development] dsbnz:
The EOS gapps packages have been made to fit into the system partition. Any extra Google apps can be installed after first boot via Play.
[Xoom Android Development] Geeba:
Hmmm ok... I think I understand.... :confused: maybe....

Why would I want to do that? I've never had a storage issue on the xoom? I think I would rather have just the system files in the system partition and the apps elsewhere? :confused:

Sorry for the noob questions... I flash all my phones... but dont wanna mess the xoom up..

I'm have problems finding a guide that covers flashing ROMs on a JB - GED - Wifi only? any pointers on a good guide? its not rooted ether....
[Xoom Android Development] iruiz2:
It's been repeated several times, but here it is again:

JB takes up more system space than HC or ICS, so the Xoom doesn't have all that space and Team EOS has made a version of Gapps that together with their ROM is able to fit in the systen partition. If you flash other "non-eos-friendly" Gapps, something is not going to fit and you'll get all kind of problems.

That's the reason why. :cool:

Sent from my Xoom
[Xoom Android Development] scottgti:
142 is out. :)
[Xoom Android Development] bigrushdog:
Its on jb for sure. Just not showing up on xoom. I think I know why. It should pop up in the next few nightlys or so.
[Xoom Android Development] draiken:
142 installed and working great
[Xoom Android Development] elsworth1983:
Cheers Team Eos DL 142 via goomanger now thanks again

Love the new Boot animation :)
[Xoom Android Development] z1gackly:
Actually you can if you want to, you just need to make room for them after flashing the ROM but before you flash the gapps. With TWRP it's easy.

For instance, on my wingray, I find I don't have any use for ringtones, so I delete system/media/audio/ringtones/ ... I'm also not interested in anything in the system/media/video/ folder so that goes too.

Lots of bloat in the system partition. You can always make a little room.
[Xoom Android Development] z1gackly:
New boot animation has lots of one pixel wide visual artefacts flickering around the edges of the screen for me. Anyone else experiencing this?
[Xoom Android Development] villain_allain:
Can I install 142 on top of 141?

what should I just wipe? Thank you.
[Xoom Android Development] wesamothman:
Sure you can.
[Xoom Android Development] elsworth1983:
Just rebooted and I can confirm it does have that issue not a biggy tho :p
[Xoom Android Development] dpl73:
Just to clarify for you: AFAIK the gapps package installed to system that is being referred to is the various Google applications e.g. : google play itself, google mail, etc. Apps downloaded FROM the market (play), do not get installed to system.
[Xoom Android Development] bobenhaus:
Yeah I'm having the same thing with 142 but not a big deal. Kewlio!
[Xoom Android Development] Sistema1927:
I have been with Team EOS since the beginning, and all has been great with each and every nightly. That said, my Xoom shut down by itself soon after flashing 142.

I will keep an eye on it, and try to grab a logcat should it occur again.
[Xoom Android Development] d3athsd00r:
Just had a kernel panic on 141 while downloading 142. Attaching my last_kmsg.
[Xoom Android Development] d3athsd00r:
Also, does anyone know how to overvolt, or if overvolting is still supported?

SetCPU won't let me overvolt and I can't seem to find the instructions anymore.
[Xoom Android Development] villain_allain:
Thanks btw. :)

Was the battery on 100% change icon? I always find mine charging even if its 100%.
[Xoom Android Development] z1gackly:
Excuse the potentially noob question, but what would the reason for overvolting be? I am overclocked to 1408 MHz and undervolted by 100mV on 142 using System Tuner, and this works fine once you set the boot settings for the CPU to initialise from init.d scripts.
[Xoom Android Development] waz675:
Someone may need to overvolt because a clock speed they desire can't be reached via stock. It may work for you but that's not the case for everyone.
[Xoom Android Development] Eun-Hjzjined:
Speaking ov OC..... Up till 142 I was not able to run at 1.7ghz at all. Just tried again and I'm able to, BUT, it only works for me if I'm in a game. Anywhere else and the xoom reboots after a few minutes.

Played asphalt 6 for an hour at 1.7ghz no issues, switched to pulse news, read 2 articles (maybe 5minutes) and got a hang/reboot.

Now idk if this is a factor to stability in game, but I've tweaked the kernal for deadline scheduling, always either used noop or cfq. Just decided to try it on the xoom because deadline works wonders on my note.

Running AOKPb1-30 | flaps 1.1
[Xoom Android Development] Ghost-of-the-Sun:
I'm coming from Everest builds (I have a mz601 but I don't use data anymore) and even if battery life is a little better with this rom, I notice too much battery drain when the tablet is idle.

Is it a common issue?

I thought battery drain was a problem of Everest builds but I have a similar behaviour with Wingray :(
[Xoom Android Development] uzi2:
Use airplane mode and then switch on WiFi.

Swyped from my Xoom
[Xoom Android Development] pitokellie:
Sorry I don't have Google now, can't find it had it before.I'm on 141
[Xoom Android Development] tdarren:
Yeah, go ahead and install over the top of 141. There's no need to wipe unless you are coming from a third party ROM.
[Xoom Android Development] h0lyc0w:
Are there known issues with widgets, particularly weather widgets, that fail to update periodically even though they are set to do so? I've noticed that widgets like Weatherbug, and Weather+ will not update temperatures and weather conditions except at boot. The time and date update normally.

I've searched the thread for any mention of this issue, but I didn't see any. Is this just a case these apps haven't been updated to support Jelly Bean?

I'm running release 142, if that helps.

P.S. I love the increased battery life compared to the CM9 nightlies.
[Xoom Android Development] Smokexz:
My indication LED won't stop flashing on 142.

Sent from my Xoom
[Xoom Android Development] GoldenCyn:
I apologize in advance if this has been asked; is there a built in screenshot function, or do I have to use a third-party app? If a third-party app is required, what would you guys recommend? I mainly want to screenshots of games so I can map the controls in the sixaxis app to use my ps3 controller.
[Xoom Android Development] drewski_1:
i'm pretty sure it has the stock ICS/JB screenshot by Vol Down + Power at the same time.

Xoom is at home so can't verify.
[Xoom Android Development] eddyther:
Yes. You can activate it under "interface" >" softkey settings"