yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] Alxoom33:
Those were the quadrant scores that were considered "too low" with 172. I used the modified CM10.1 kernel and got much lower quadrant scores around 1800. If everyone recalls we were talking about cm10.1 and My Android running at speeds approaching 4000 compared with EOS4 174 running at 2700, see pages 116_120.:p

175 running smoothly as is! Team EOS keep doing what you were doing! Thank you!!!:good:
[Xoom Android Development] hochoch:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Crt is not working for me, no clue why not. I love it so much too! :(
[Xoom Android Development] TheMainCat:
I forgot to post the Quadrant score on just base 175 in my previous message.....1775. Quite a difference.
[Xoom Android Development] drewski_1:
CRT not working here either, but not a big deal for me
[Xoom Android Development] matt4321:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Weird, works for me and I did a dirty flash from blackbean 7
[Xoom Android Development] Booga Booga:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Neither for me. Flashed dirty.
[Xoom Android Development] thewelt1:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Just flashed 175 faster but my wifi symbol dosnt turn blue when connected just stays grey..
[Xoom Android Development] Droidem:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Flash the radios?

Sent from my HTC6435LVW ViperDNA
[Xoom Android Development] thewelt1:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

How do I flash the radio never had to it before..?
[Xoom Android Development] runandhide05:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

That indicates to connection to google services.

Don't need to flash radio on a WiFi only tablet
[Xoom Android Development] petrossa:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Happens to me too since first nightly. Sometimes turning on radio helps for some reason :what:

Sent from my Xoom
[Xoom Android Development] peebo:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

are there any plans to include exfat support on this tablet?
[Xoom Android Development] wiltgen:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Keyboard is weird on 175. I can swipe using stock keyboard but if I type a single key the keyboard closes itself down. Any clue?

Enviado de meu Xoom usando o Tapatalk 2
[Xoom Android Development] bigrushdog:
Exfat should mount.
[Xoom Android Development] bigrushdog:
Ok. Did we come to any kernel conclusions? Do I:

Keep the eos kernel?

Or

Plead with my colleagues to let me use:

Cm kernel or

Shield kernel

What's it gonna be?
[Xoom Android Development] FormerPalmOS:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

This time the CM10.1 kernel and nightly 175 came right up. Still no idea why it didnt go smoothly last time I tried. I replaced the nightly zip boot.img with the boot.img from the latest CM10.1 nightly, wiped system and caches then flashed the new zip and gapps.

CRT works fine. Wifi icon works normally. Play store works fine. In other words I am not seeing any of the issues reported by others with 175.

That said, I haven't had time to test anything else out but just navigating around the homescreen and a few apps it doesn't feel any faster. I don't bother with Quadrant or any other benchmarks.

Seems the CM10.1 kernel doesn't support undervolting. That's a show stopper for me. So I will be going back to the boot.img in the nightly 175.
[Xoom Android Development] alex94kumar:
How do quadrant scores on ShieldKernel compare to stock? CM10.1 kernel?
[Xoom Android Development] ATZ-007:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

This is a known problem. Just download another keyboard from Play Store.
[Xoom Android Development] lepa71:
What is the CRT?
[Xoom Android Development] FormerPalmOS:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

If we are talking about the same thing, its a gee-whiz-bang animation option when the screen turns on or off that mimics the look of a CRT monitor turning on or off. Maybe it's just for those of us old enough to remember what one of those looks like ;)
[Xoom Android Development] TheMainCat:
From what I am seeing, not sure a big difference is there between the EOS kernel and anyone elses. It's true I get higher scores when using the 10.1 kernel, but if I didn't know what a quadrant score was, I wouldn't be able to really tell the difference. Both are snappy on 175, no real FC's that I experienced, and battery life was about the same. Everything that is supposed to work, does (CRT animation too) and things that are known issues, still don't work (like stock keyboard).

IMO I would leave things the way they are and move focus back to tweaks and enhancements and put this kernel discussion to bed.
[Xoom Android Development] Torqd505:
I have tried the CM kernel with 175. Can't really tell the difference in normal activities. Everything I tried that worked before still works now.

I ran a few quadrant scores on both kernels and CM scored 15-20% higher on average.

My Xoom is not OC'd. Governor is interactive/deadline

I don't see any real benefits but either one is fine with me.

BRD it's your call.
[Xoom Android Development] lepa71:
Is there a place to change I/O scheduler in EOS control center?

BTW CRT off and on works on mine.
[Xoom Android Development] FormerPalmOS:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Don't think so. I use SetCPU which enables overclock control, undervolt control, governor selection and tweaks, and I/O scheduler selection.
[Xoom Android Development] FormerPalmOS:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

CIFS is working now so I can truly make iPad owning sheeple jealous...
[Xoom Android Development] bigrushdog:
Sometimes no action is the best action. Frankenstein stays for now.

Ya I really recommend a third party kernel control program. The built in controls are rather dated and lacking. But I've been focused on other issues. There's no io scheduler change atm but that's pretty essential. I'll see what I can do when time permits.
[Xoom Android Development] Alxoom33:
Not cm kernal not any faster.

Perhaps look at the Shield kernal, as My Android is very fast. However, need more testing to see if actually faster in the EOS4 Rom environment or if the speed difference is due to something other than the kernal. BRD you're the man :)
[Xoom Android Development] bigrushdog:
Here's the thing with quadrant. It's score is heavily weighted towards nand io. So if data is mounted with noatime nodirtime nobarriers you will get a high score. We use some of those flags but we also use a few others that make io not necessarily faster but smarter. This is some stuff kcrudup cooked up back in the day. So for now, we'll put the issue to bed. Not to say we won't revisit it again. Android is a journey, not a destination. God that was cliche :p:rolleyes:
[Xoom Android Development] TheMainCat:
Speaking of CIFS...how did you get it to work. Been messing with it and not having any luck getting the mounts to recognize.
[Xoom Android Development] Alxoom33:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Wow BRD that was heavy! The struggle makes the journey all worth while;]
[Xoom Android Development] FormerPalmOS:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

CIFS Manager from Market automates this very nicely. The trick is in the options string. Lets say you have a Windows machine and your workgroup name is HOME (it should always be all caps). Your options string should be

domain=HOME,rw

the last part makes the mount read-write. Use ro for read-only.

---------- Post added at 02:06 AM ---------- Previous post was at 01:53 AM ----------

Mounting data (and the external SD Card) with noatime and nodiratime will for sure speed up access and also positively contribute to extending the media life.

For the curious, noatime tells the file system not to record the last time the file was accessed. Last change time is still recorded. Similarly nodiratime says not to update the time a directory was last accessed. Recording requires a read-modify-write to the flash media. Not recording the time saves two flash operations, granted tiny ones (one sector).

Currently the EOS ROM mounts /data with noatime but does not use nodiratime. The SD card mount does not use either flag.

---------- Post added at 02:12 AM ---------- Previous post was at 02:06 AM ----------

Feature request: Adjustable auto brightness. When auto is disabled the slider sets brightness (no change). When auto is enabled the slider works with the light sensor to bias the automatically selected brightness. The problem I am hoping to solve is that my display is too dark with auto brightness so I frequently set it manually but I would like to have it automatically adjust - just not too dark.
[Xoom Android Development] petrossa:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

All what benchmarks show is how well the benchmark is done. As a tool it is like a sledgehammer to drive small nail in. It works but that's being generous
[Xoom Android Development] kmcrane:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Auto brightness seems too light for me and I would like it to be "auto darker"

I have been requesting that in the gnex thread. Someone posted an app called Velis Auto Brightness. It's free and fully customizable. It takes over the auto brightness and has satisfied my needs.
[Xoom Android Development] runandhide05:
Ya without my cable I will need that log cat please
[Xoom Android Development] EDNYLaw:
Here 's the log http://db.tt/jLS9ui7c its the last event in the log. Let me know if you need more.

Sent from my swagged out AOKP Xoom 1.5 Ghz 512 Mhz GPU
[Xoom Android Development] runandhide05:
hmm, not a single fail???

logcat says its connecting and disconnecting properly. let me dig a little more and il ask BRD if he sees anything
[Xoom Android Development] EDNYLaw:
Good luck, thanks man, really appreciate the hard work and dedication

Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
[Xoom Android Development] alex94kumar:
https://www.dropbox.com/s/86hffrik6b3htoz/2012-12-05-22-22-39.txt

there's a logcat as well. I also noticed the keyboard quickly goes away and pops back up when HDMI is plugged in. it happens within half a second or less but i noticed it
[Xoom Android Development] Mjamocha:
libjni_filtershow_filters.so

System/lib. rw-r-r
[Xoom Android Development] alex94kumar:
doesn't matter now lol, BRD/RnH removed photosphere from the rom altogether
[Xoom Android Development] runandhide05:
its more than just a lib, ;)
[Xoom Android Development] alex94kumar:
I bet we all wish it were that easy

---------- Post added at 11:30 PM ---------- Previous post was at 11:16 PM ----------

On another note, I got multiple users set up on the tablet. Everything is going smoothly with that, which is a huge plus. Loving that feature.

EDIT: Strange though, noticed that there are no Developer Options on secondary user accounts, even after activating it by tapping Build Number 7 times. Not sure if this is an EOS bug or a part of Android altogether

EDIT2: On the secondary account it seems all the data is the same as on the primary account.
[Xoom Android Development] Mjamocha:
Well of course its more than just a lib, I'm not a f*ckin simpleton. that was one of the lib file that was not in the zip, (mosiac, lightcycle ...were there) that fixed my photo fc's prob. Anywhooo... like'n the extra space provided by the gapps, nice.
[Xoom Android Development] alex94kumar:
RnH, if I flashed the camera app from the thread '4.2 camera working on xoom' from over in the themes and apps section, would I run into any problems?
[Xoom Android Development] adamski88:
Hello

I tried updating from wingray version 155 to 156. Downloaded it etc, done the usual, installed it, installed the latest version of gapps, it said it all went fine. However once it had loaded and optimised apps, I couldnt get past the lock screen. When i put my unlock combo in it just froze. Tried rebooting a few times with no luck, just kept freezing.

I have then tried to go back to version 155 but its getting stuck at the logo screen (i think its the eos logo, with 4 different colours)

Any help would be greatly appreciated, i really need to use my xoom tomorrow!

Thanks

Adam
[Xoom Android Development] runandhide05:
Let me rephrase,

I know that lib is for photosphere, however it ( photosphere ) is not working, so I removed unneeded libs from the gapps. I did not mean to insult.

If you care to send the the three libs that u say make photosphere working I will be more than happy to confirm it works and add it to the next updated gapp package

---------- Post added at 10:56 PM ---------- Previous post was at 10:52 PM ----------

155 to 156 must be done with a factory reset. 156 is a major update (from 4.1.2 to 4.2.1)

To return to 155 you will need to factory reset, install 155+gapps boot then restore your backup (that I hope you made before flashing 156)
[Xoom Android Development] adamski88:
:( ah that really sucks. I didn't know that, thought it would of been like any other update, given that my Xoom prompted me to do it!

I sadly didn't do a backup. Is this a complete dead end then? No way of recovering my files etc?

Is the best bet now to upgrade to eos4? Given that I will have to do a factory reset now anyway?

Thanks
[Xoom Android Development] drewski_1:
I went from 156 to 155 by restoring backup and moving /data/media/0 to /data/media (TiBu kept freezing while restoring my apps)

Seems to be working fine.
[Xoom Android Development] runandhide05:
Well u can save your apps from within twrp, using the built in file manager and just copy the apks but as for app data if u know where your looking u can save them, but if there is nothing you absolutely must have then a nice clean install can't hurt
[Xoom Android Development] dreamcwli:
You have to hack smali in GalleryGoogle.apk to make Photo Sphere camera work. You can use Google Apps in My Android 4.2.1 thread to test if it works on EOS 4.
[Xoom Android Development] drewski_1:
Just flashed 157 from 155.

It did not copy the /data/media folder contents to /data/media/0 like when I flashed 156.

Everything was still in folders in /data/media and most every new folder in /data/media/0 was empty.

Could this be related to my restoring my backup without first re-flashing 155 (3 posts up)?
[Xoom Android Development] malcolm159:
Not Compatable with xoom

Hi just flashed from 155 to 157, went ok but when trying to install bbc iplayer getting report saying not compatable with xoom player was installed on 155 and working. Any one else had this or know a workaround ??? gone back to 155 for now.

Thanks in advance.

Regards Malcolm
[Xoom Android Development] adamski88:
I guess there's nothing super important, just more of a major inconvenience.

On the topic if eos 4, should I upgrade to it? I know there are certain bugs at the min, but I'm sure they will be straightened out.

I've never done a full wipe before, do I just boot into recovery, do the factory reset then install the rom from sd card like normal?

Thanks again
[Xoom Android Development] WarLion:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

I just find out something on 175

if you turn on your torch the camara will not connect I'm unable to use the camera only when the flash led is on

is this normal?
[Xoom Android Development] petrossa:
The law of uninteded consequences

Cost me 20$ to find out, but after having set the OC'ing to 1600 the xoom triggers my infrared motiondetector. :eek:

The light in my bathroom is activate dby it, my wife started to complain it lit up all the time by itself. Obviously i did what any husband would do, dismissed it out of hand. Women and technical stuff ;)

But when it happened to myself i replaced the detector which did the same. So flash of insight, i tilted the sensor away from the tablet and now no more spontaneous combustion of lights
[Xoom Android Development] bigrushdog:
Yes. Torch must be off in order to use camera.
[Xoom Android Development] highKo:
I came from cm10.0. I didn't like cm10.1 because the scrolling speed in the launcher seems to be laggy . now I feel the same here. any reason that the launcher scrolls laggy? I noticed it in my nova prime and at stock. the app drawer is fast like in 4.1.2.

are there ways to tweak it?

I will stay at this rom, photosphere is amazing
[Xoom Android Development] Alxoom33:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

What is your oc setting and governor?
[Xoom Android Development] highKo:
im using lagfree (and tried interactive) at 1,2 ghz
[Xoom Android Development] elton.de.nascimento:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

where can i found photosphere for download?
[Xoom Android Development] drewski_1:
it's part of the Camera App
[Xoom Android Development] DefinityX:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

I'm on 174 right now... Haven't gotten to upgrade to 175.

But...

Just realized today, Bluetooth is broken for me... Completely. Won't even turn on. Will try flashing 175, fix permissions, etc tonight. If still no joy, will post a logcat.
[Xoom Android Development] FormerPalmOS:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Read this so I tried Bluetooth on 175. No issues - found and paired my evil iPhone and used it for internet access.

When you flash, this is the sequence of steps I have followed that has worked every time. Some of this might be redundant with the scripts in the zip files:

Boot to recovery (TWRP 2.4.1.0)

Wipe system, cache and Dalvik

Select ROM zip then add GApps as a second zip (install both at the same time)

Flash

Fix permissions

Reboot

This might fix whatever is breaking your Bluetooth.

Or it could be something else you have installed, but to break Bluetooth an gapps would have to be granted root access so that might help you narrow it down.
[Xoom Android Development] DefinityX:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

I did all that coming to 174 from 155. And I'll redo it here in the next hour or so.

Thanks for the confirmation I have the right steps though... And that's it's just me. :( Here's hoping it fixes it...

Odd thing: I don't have anything installed that wasn't on 155, but it could be something nasty that hasn't been properly upgraded for 4.2...
[Xoom Android Development] FormerPalmOS:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

155 to 174 would require an additional step of wiping data and reinstalling your applications. If you are still having problems on 175 make a backup, wipe data (factory reset) and go from there. Restore one application at a time and test Bluetooth after each until you find the culprit. Royal PITA I know. You don't have to wipe internal storage (what's in the /data/media folder) but I would take a hard look at what's in there as well.
[Xoom Android Development] DefinityX:
No need... 175, BT works like a charm. Booyah! Must've gotten a bug somewhere in my last download or install...

Thanks!
[Xoom Android Development] Alxoom33:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Try interactive and 1.4 ghz
[Xoom Android Development] gibbs1984:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

I'm pretty sure I saw a fix for the Netflix problem but I can't find it.

On 175 and Netflix still stops after a couple of minutes, even with the HW overlays disabled.

Is this still a problem with everyone else?
[Xoom Android Development] Alxoom33:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Netflix works OK for me.
[Xoom Android Development] FormerPalmOS:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Yup. Had a crash on 175 without HW overlays disabled. Just re-disabled that (the setting doesn't survive flashes or reboots - not sure which). Hoping the problem goes away. NetFlix working is a must-have for my wife.

I am wondering if it might be caused by network issues - packet lossover WiFi, WiFi sleep or something along those lines where for some reason the video part freezes but the audio continues.
[Xoom Android Development] gibbs1984:
Cheers, I remember it was yourself that suggested about the HW overlays last time.

I did try to enable and disable it and it didn't work although I did reboot cause I thought that might make the setting stick so I'll try without rebooting.

Definitely something with the ROM or Android 4.2 as Netflix works perfectly on my HTC One X running 4.1.1.
[Xoom Android Development] ifti_a:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Has anyone used the chrome browser fromthe play store?

I found it miles better than stock ?

---------- Post added at 10:02 PM ---------- Previous post was at 09:50 PM ----------

Also i swiped the brightness toggle to go to sound

but how do i switch it back to brightness?
[Xoom Android Development] scottgti:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

[QUOTE\] Also i swiped the brightness toggle to go to sound

but how do i switch it back to brightness?

Swipe the opposite direction to change back.
[Xoom Android Development] kuroguy:
Swipe left to right just below the volume slider

Swipe the opposite direction to change back.[/QUOTE]
[Xoom Android Development] kentedman:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Go into developer options and disable HW overlays and all three of the animations options. Makes a world of difference for the launcher and app drawer.

Sent from my Nexus 7
[Xoom Android Development] petrossa:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

I tried several 3rd party launchers, nearly all of them outperform stock by a wide margin. Presently using ADW which has no issues I could detect

Sent from my Xoom
[Xoom Android Development] xda_biscuits:
MZ604

Does this ROM work well on a Xoom MZ604 Wifi? :confused:
[Xoom Android Development] MARIANOTE:
Gapps

What gapps package works ok in 175? I have playstore crashes..... All other things work ok. Great job like allways. Gracias.!
[Xoom Android Development] waz675:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Yes

---------- Post added at 10:33 PM ---------- Previous post was at 10:32 PM ----------

Edited. Use EOS gapps specific file since xoom has little./system space so normal gapps won't play nice.
[Xoom Android Development] Muffycheeks:
Build #175 has issues, for me it's the Key Board. It disapears when I try to type. No problems with Play Store.
[Xoom Android Development] Taysider:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Goto 1st post you will see gasps for Xoom only, I think the latest is 20130105.:)
[Xoom Android Development] runandhide05:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

http://xdaforums.com/showpost.php?p=37263016&postcount=1275

And its on every Xoom thread about 20 times or more...

;)
[Xoom Android Development] waz675:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Oops I thought I was.in n7 forum before. As said, xoom has EOS specific gapps. I apologize, 3 hour sleep nights for past.2 to 3 weeks is messing with me.

Sorry!
[Xoom Android Development] Muffycheeks:
Been there done that !!! The Key Board still isn't working for me. Didn't have the problem on build #174.