[ROM][JB] Team EOS 3 *JELLYBEAN* Nightlies - Stingray / MZ602 / US 4G ONLY

Status
Not open for further replies.
Search This thread
By:
Advanced…
K

kcrudup

Senior Member
Mar 27, 2007
1,517
749
San Francisco Bay Area
pamaguin said:
Yes there is no LTE in my location
Click to expand...
Click to collapse
This is actually good to know. So, have you ever used your device in an LTE area ever, and is the SIM card still in your Xoom?

Also, could you power off, pull out your SIM card, reboot and see if you get data to pass?

This is much appreciated, and points to the Authentication portion of LTE being the culprit (but I'll need more info to be sure). If we can narrow down just which of the many changes are necessary to get data to pass on our devices, that'll save us a LOT of work (and increase reliability), vs. having to hack the entire layer.
 
E

EtchG

Member
Oct 9, 2011
38
0
Connecticut
pamaguin said:
Yes there is no LTE in my location and I my Xoom has been upgraded; got a free dock too

And as for the Logcat, you will need to give me instructions on how to and I will not be able to get to it till after midnight. I have to go to work right now

Sent from my Xoom using Tapatalk 2
Click to expand...
Click to collapse

Your screen looks like mine when I flash 107. Can you actually get to anything online?
 
A

atlmatt

Senior Member
Feb 14, 2009
178
11
I live in a 4g area and had data until I upgraded from one on the 1st nightly builds. I will do a complete wipe, reload eos build 100 and flash eos3 107 when I get home and see if It works, I'll get you a log cat as well.


Not sure if it was 4g or not, I signed in to my Google account and then setup WiFi so I know it connected to the internet
Sent from my Xoom using xda premium
 
pamaguin

pamaguin

Senior Member
Sep 24, 2010
235
7
I am sending this over data and I've rebooted my Xoom
aefdc564-2cda-2648.jpg


Sent from my Xoom using Tapatalk 2
 
H

hchxoom

Senior Member
Apr 27, 2011
427
89
kcrudup said:
This is actually good to know. So, have you ever used your device in an LTE area ever, and is the SIM card still in your Xoom?

Also, could you power off, pull out your SIM card, reboot and see if you get data to pass?

This is much appreciated, and points to the Authentication portion of LTE being the culprit (but I'll need more info to be sure). If we can narrow down just which of the many changes are necessary to get data to pass on our devices, that'll save us a LOT of work (and increase reliability), vs. having to hack the entire layer.
Click to expand...
Click to collapse

Kenny... wasn't it after 100 that we started needing to flash the new radios? Is it possible that those of us that moved beyond 100 need to actually go backwards to old radios in order to get connectivity now on JB?
 
pamaguin

pamaguin

Senior Member
Sep 24, 2010
235
7
kcrudup said:
This is actually good to know. So, have you ever used your device in an LTE area ever, and is the SIM card still in your Xoom?

Also, could you power off, pull out your SIM card, reboot and see if you get data to pass?

This is much appreciated, and points to the Authentication portion of LTE being the culprit (but I'll need more info to be sure). If we can narrow down just which of the many changes are necessary to get data to pass on our devices, that'll save us a LOT of work (and increase reliability), vs. having to hack the entire layer.
Click to expand...
Click to collapse

Yes I've used my Xoom in a LTE area

Sent from my Xoom using Tapatalk 2
 
E

edjm711

Senior Member
Oct 8, 2010
123
12
Do any of you using your xoom on 4G have the new share everything plan? There is a known issue with reactivation if you were on the old plan, and switched to the new plan then reset and had to reactivate. Esn and iccid show in Verizons system but it won't work. Even swapping Sims doesn't work. Via tier 3 ts

Sent from my SCH-I535 using xda app-developers app
 
K

kcrudup

Senior Member
Mar 27, 2007
1,517
749
San Francisco Bay Area
hchxoom said:
Is it possible that those of us that moved beyond 100 need to actually go backwards to old radios in order to get connectivity now on JB?
Click to expand...
Click to collapse
No, the RIL in JB is currently the same as that in ICS. The issue here isn't the radios (as evidenced by the fact that we have signal strength, in-service-kind status (i.e., LTE/eHRPD/CDMA) and SIM-card number (IMSI)). It appears the JB API changes mean we need to authenticate a different way now (as CDMA like what pamaguin" has service with authenticates a different way (via IMSI/MEID only).

---------- Post added at 01:11 PM ---------- Previous post was at 01:09 PM ----------
pamaguin said:
I am sending this over data and I've rebooted my Xoom
Click to expand...
Click to collapse
Was your SIM card in after you'd rebooted? (That was actually what I'd needed to know).

(Also, which keyboard is that?)

---------- Post added at 01:12 PM ---------- Previous post was at 01:11 PM ----------
edjm711 said:
Do any of you using your xoom on 4G have the new share everything plan?
Click to expand...
Click to collapse
I'm not on a Spend Everything plan.
 
  • Like
Reactions: GavinMazey
G

G8orDroid

Senior Member
Mar 19, 2008
175
36
kcrudup said:
No, the RIL in JB is currently the same as that in ICS. The issue here isn't the radios (as evidenced by the fact that we have signal strength, in-service-kind status (i.e., LTE/eHRPD/CDMA) and SIM-card number (IMSI)). It appears the JB API changes mean we need to authenticate a different way now (as CDMA like what pamaguin" has service with authenticates a different way (via IMSI/MEID only).

---------- Post added at 01:11 PM ---------- Previous post was at 01:09 PM ----------


Was your SIM card in after you'd rebooted? (That was actually what I'd needed to know).

(Also, which keyboard is that?)

---------- Post added at 01:12 PM ---------- Previous post was at 01:11 PM ----------


I'm not on a Spend Everything plan.
Click to expand...
Click to collapse

I can confirm pamaguin's assertion that you can get 3g, but you must change to "CDMA only". I did this this morning but work got in the way of posting.

His keyboard looks to be Thumb Keyboard 4. Which coincidently,is what I'm using.

I know I don't have many posts here, but you may have seen me elsewhere as G8orDroid. I have a pretty good grasp on what I'm doing.

Sent from my Xoom using Tapatalk 2
 

Attachments

  • uploadfromtaptalk1342124788813.jpg
    uploadfromtaptalk1342124788813.jpg
    14.9 KB · Views: 163
Xezuka

Xezuka

Senior Member
Sep 10, 2010
125
12
Columbus
If anyone is having trouble connecting to Wifi, simply try a factory reset within recovery, reinstall the rom+gapps, then reboot and attempt again.

Worked for me! :good:
 
G

G8orDroid

Senior Member
Mar 19, 2008
175
36
Yes, my status screen does say "CDMA - EvDo rev. A:6", just as his does. I am in a 4g area though, kinda towards the fringe of it, but I don't usually have any problem getting 4g on my Xoom or my Maxx.
 
A

Asphyx

Senior Member
Dec 19, 2007
2,158
378
Android Wear
Google Pixel Watch
kcrudup said:
So all I can say is "stay tuned"- nobody wants LTE data working on JB more than I do, so even if we have to hack up the telephony layer like a Christmas turkey while we wait for VZW to get their **** together, we're going to do what we can to get it working (the fact that we can at least see the radios, get on the air, and see the LTE mode is highly encouraging).
Click to expand...
Click to collapse

Well Google announced they would push a JB OTA to Xoom devices later in the month, Won't that help get you the bits you need to get the radios fully working?
 
K

kcrudup

Senior Member
Mar 27, 2007
1,517
749
San Francisco Bay Area
dlundy said:
Yes, my status screen does say "CDMA - EvDo rev. A:6", just as his does.
Click to expand...
Click to collapse
VERY helpful- thanks.

I am in a 4g area though, kinda towards the fringe of it
Click to expand...
Click to collapse
Which Metro area are you, and how long have they had it?

Apparently (and I likely have some of this wrong, so don't quote me) when VZW started deploying LTE, in order to not have to throw out old CDMA equipment they came up with a middle solution called "eHRPD", which allows LTE to authenticate via CDMA first. I'd imagine they'd use that solution in large Metro areas first (I'm currently in Silicon Valley (the San Jose, CA area)) where there's already a large CDMA base that would be expensive to replace outright.

I'd be happy to get even CDMA-only data until we get this solved, so I'm looking to see what I can do to perhaps force that as an interim solution.
 
C

cadiken

Senior Member
Mar 19, 2010
127
22
bigdave240 said:
checked and it is 5.4.0.2 when you look at yours does it say that it is writable for sdcard1?
Click to expand...
Click to collapse

Just checked and no it doesn't. It did before went to sleep last night. I made a backup and restored using both Titanium and Rom Toolkit and both worked. All I did today was format /system, re-flash rom and gapps. Sorry bro. Rom Toolkit still works though I just checked.
 
K

kcrudup

Senior Member
Mar 27, 2007
1,517
749
San Francisco Bay Area
Asphyx said:
Well Google announced they would push a JB OTA to Xoom devices later in the month
Click to expand...
Click to collapse
Yes, but I'm willing to bet that's probably only going to be for the Wingray (MZ600/WiFi-only) devices, which is where we already are. Remember the 5-month delay in getting the ICS build for the MZ602 from Verizon? VZW, for better or for worse, likes to certify the **** out of anything that goes on their network.

(What might help us is if there's a JB LTE handset out there, where we could maybe pull some of the VZW Telephony proprietary APKs from.)

Besides, even if by some miracle the Stingray (MZ602/LTE) build is also ready by the end of the month, I'm an impatient motherfscker and I WANT IT NOW!! :D
 
B

bigdave240

Senior Member
Nov 6, 2007
398
46
cadiken said:
Just checked and no it doesn't. It did before went to sleep last night. I made a backup and restored using both Titanium and Rom Toolkit and both worked. All I did today was format /system, re-flash rom and gapps. Sorry bro. Rom Toolkit still works though I just checked.
Click to expand...
Click to collapse
thanks. not too worried. just a few glitches in this new ROM. I am sure it will get worked out eventually.
 
Status
Not open for further replies.

Similar threads

teameos
  • Locked
[ROM][Nightly][ICS] Team Eos WiFi Nightlies (Wingray/MZ604)
Replies
4K
Views
1M
KennyG123
KennyG123
teameos
  • Locked
[ROM][JB] Team EOS 3 *JELLYBEAN* Nightlies - Wingray / MZ604 / WIFI ONLY
Replies
3K
Views
674K
bigrushdog
bigrushdog
teameos
  • Locked
[ROM][JB] Team EOS 3 *JELLYBEAN* Nightlies - Umts_everest / MZ601 / EU 3G ONLY
Replies
2K
Views
412K
teameos
teameos
teameos
[ROM][Nightly][ICS] Team Eos US 4G Nightlies (Stingray4G/MZ602)
Replies
2K
Views
354K
Mjamocha
Mjamocha
teameos
[ROM][Nightly][ICS] Team Eos European 3G (GSM) Nightlies (umts_everest/MZ601)
Replies
1K
Views
409K
Z
Zarosky

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 45
    teameos
    teameos
    Team EOS XOOM​
    JB 4.1.1 Stingray MZ602​
    NIGHTLIES​

    Continuing on from the success of the EOS ICS roms, we present to you EOS3, based on JELLYBEAN!

    It is the goal of Team EOS to develop and maintain the highest performing and most stable AOSP based rom for an array of platforms. The launching point for this development effort is the Motorola XOOM.

    For the latest news on Team EOS Xoom releases make sure you follow @teameos on twitter and on IRC on Freenode in #xoom.

    --
    NOTE: Team EOS, it’s members, friends, dogs, cats, and associates are in no way responsible for any loss of data or device functionality. Use this at your own risk!
    --

    A quick note on Nightlies: NIGHTLIES ARE DEVELOPMENT BUILDS. They are automatically generated every now and then, and represent the compilation of the latest commits to the code repository. While every effort is made ensure that the commits that are accepted are stable and do not have a negative impact to the overall performance and function of the builds it is not possible to test every aspect of a commits impact to the overall repo prior to it’s inclusion in a given build. As a result it is entirely possible that instabilities may be introduced as a result of a given days commits. That is the nature of the nightly system, and the risk that is taken using the latest code changes to the project.

    EOS Xoom is an AOSP based rom. It is developed and maintained by Team EOS and is the culmination of our own in house development efforts.

    Team EOS Xoom Nightly builds: http://goo-inside.me/devs/teameos/roms/eos3/nightlies/stingray/

    G-Apps Package
    Because this is an AOSP based rom Google Apps are not included in the base rom. To install Google Apps please flash the following package after installing the base rom:

    Temporary Gapps package gapps
    --
    Features:
    Because these are nightly builds the included features are constantly evolving, we do not provide a change log manually. Instead please see the changes on jenkins for your build.
    For the most up to date and comprehensive listing of the changes included in this rom please visit http://review.teameos.org

    Kernel:
    Tiamat ICS Xoom kernel
    Support for OC;Under/Overvolt
    Governors: lagfree, interactive, conservative, ondemand, userspace, performance

    Kernel Note: In compliance with GPL kernel source can be found at: https://github.com/solarnz/Tiamat-Xoom

    --

    Installation Notes:
    These builds are designed to be installed from your favorite recovery (Solarnz R4c, Rogue, Clockwork)
    Perform a full wipe (read Factory Reset) prior to installing this over ANY ICS based rom.

    BUGS!
    If you find strange or otherwise unexplained errors please report them here: https://bugs.teameos.org/ Please include logcats and as thorough a description of the issue and what lead up to the issue as possible. With out this we will be unable to track down these errors.

    Changing the Stock Motorola Dual Core Boot Logo Splash Screen:
    While not a necessary feature of the Team EOS ICS builds make sure you check out the Team EOS Motorola Xoom Boot splash utility in the Android Market:

    EOS Motorola Xoom Boot Splash


    Want to contribute to the Eos rom? Well you can!
    Just follow http://teameos.org/?page_id=6 to checkout our source code, and information on how to submit changes for review.

    Welcome to the XOOM evolved. Welcome to Team EOS.
    View
    20
    K
    kcrudup
    electroman987 said:
    ... which I think I already know the answer, can I just wipe caches ...?
    Click to expand...
    Click to collapse
    Nah, just leave your caches be.

    Really. If the Framework thinks they need to be redone, they'll wipe and rebuild them on their own ("Android is updating apps"). It should only be necessary as a last resort (i.e., the machine instantly reboots upon first boot, or immediately returns to the Boot Animation, or apps immediately FC or don't come up at all).

    Ditto wiping, unless you're coming from HC. I'm just trying to spare you guys from unnecessary wiping and (Now, that being said, for those who don't mind wiping I've got a filesystem change for /userdata that requires wiping, but will speed up access to the flash and reduce lag, sometimes greatly. Stay tuned, as I'll be announcing that in a day or so after I button it all up and make it ready for Prime Time).

    ---------- Post added at 07:02 PM ---------- Previous post was at 06:33 PM ----------

    So, about the reboots: For the longest time (around October '11), the TeamEOS kernels for the Xoom have been overclocking the GPU from 300MHz to 400MHz; it worked great and we never really got anyone complaining about it. Right around the time we got JellyBean, however, we ended up in a "perfect storm" of video issues: (1) apparently JB uses the GPU far more than ICS, putting more strain on it at 400MHz, and (2) I'd added into the kernel an optimization that came from NVidia to remove a CPU<->GPU synchronization aid that was deemed unnecessary (and probably innocuous under ICS) with a standard-speed GPU.

    So, some of you guys got spontaneous reboots (especially when watching YouTube, with certain animated wallpapers, and/or watching videos), and eventually, so did I. After tracking it back, first I'd turned down the GPU speed back to 300MHz, but that didn't fix it for everyone, so I reverted back the NVidia patch, and at the same time turned back the GPU speed to 400MHz- unfortunately, that fixed one possible reboot source but brought back another.

    So, it's now obvious that we've got to be stock-clocked in the GPU for JB now, so we're going to revert back to that. I've known this for a couple of days, but haven't pushed the change until I'd not only tested it on my own Xoom (as I did continue to see reboots myself before my fix) and to verify that there were no other isuses (as I've upgraded the compiler for- and the way we build- the kernel).

    Look for a permanent fix in the next day or so. In the meantime, for those I've asked to PM me if you're seeing reboots, I'll have a link up soon for a boot.img that you can "fastboot flash boot" on (unfortunately, no update.zip-able image).

    BTW, if you're a Benchmark Whore (like me :)) you'll notice ~20% or so decreased scores in graphics-based testing. I'm gonna miss my 29.8 NenaMark score, but I'd miss stability while watching YouTube even more!

    I thank you guys for sticking with TeamEOS throughout all this, and be assured that quality and stability is always Goal #1 with us, as if it doesn't work, y'all won't use it.


    (TL;DR: I know what the problem is, have fixed it, and you'll all have it soon.)
    View
    14
    K
    kcrudup
    Guys, there's a kernel on the way that not only fixes the random reboots with video (I'll post up the gory details tomorrow) but also brings back the Video optimization I was talking about earlier and the 400MHz GPU speed as before.

    I've been quiet these last few days nailing down both the random-reboot (which is actually a "lockup") issue, plus the issue where sometimes you can hit the power button but the device doesn't respond.

    I'm 99.9% sure I have the reboot issue down (it was something that wasn't even where I was looking for it), and the changes I've made to eliminate the power-button-on issue are also going to generally make the device more responsive as well. I had a 2-1/2 hr YouTube HD video running from start to finish without a single issue.

    Again, sorry for the inconvenience, but rest assured that I've been on it since it'd started to happen (my Xoom is my daily driver too)!
    View
    13
    K
    kcrudup
    bigrushdog said:
    You guys should be maxing out that thanks button for kcrudup.
    Click to expand...
    Click to collapse
    Ya know what's funny? I couldn't care less about those, and even have Thanks counts turned off in settings. :)
    View
    12
    K
    kcrudup
    bigdave240 said:
    Since flashing 128 i have had my xoom go into a stuck state twice where it looks like it has gone into standby but wont wake up and gets hot like it is running something while in that state. Only way to wake it has been a reboot. Anything you need me to look at?
    Click to expand...
    Click to collapse
    <grumble>

    Yeah ... next time this happens, if you have "adb" can you do:
    Code: 
    adb shell vmstat
    for about a minute or two and send me that output? I know exactly what happened, I'll bet- you were caught up in an "I/O Storm", and the machine never got to service your PowerOn request before the screen-off timer kicked in (so the screen never came on). Your machine was probably running just fine, otherwise.

    The other thing I'm working on lately is fixing lag caused by a combination of our using a relatively-older kernel (2.6.39.4), our slow EMMC flash disk, and believe it or not, not enough RAM (732MB isn't really enough anymore as the size of the OS and Apps increase to fill the vacuum).

    Have you noticed that when the Xoom first boots, everything is so fast, then after a while, things start to slow down? Well, what's happening is that when RAM begins to fill with Apps, libraries and disk data, the system does what it can to page out memory that's not needed (disk-cache data that hasn't been used in a while, parts of programs that haven't been executed in a while (which can be reloaded from disk if necessary) and if all else fails, there's a "low-memory-(app)-killer" that runs in the kernel and forcibly shuts down apps (this is the reason why sometimes you'll switch back to a large-memory-footprint app like the Browser, and the tabs will all have to reload).

    A lot of that involves what's called "paging" back and forth from the EMMC flash disk. When the stale data gets written out, we're doing writes to the flash filesystem- and those operations can take a LONG time (relative to the speed of reads, and of the CPU) and because of the way the flash disk works, while that slow write is happening, no reads (which are a lot faster) can run- so when the memory starts to get full of running programs (and/or is doing a lot of I/O (especially write I/O)) the system ends up slowing down:

    - dirty data is being written out, while
    - new programs (or parts of programs that were paged out and now need to run) are being read in, while
    - the system is spending CPU cycles trying to scan memory and free blocks

    so we end up in a condition called "thrashing". I've been spending a LOT of time trying to reduce this as much as I can: I've been working on doing ANYTHING I can to get the write thruput up, and have been tweaking both the V(irtual) M(emory) parameters and the I/O Scheduler parameters in an effort to keep the number of random writes down, to prioritize reads over writes, and to avoid "I/O Storms", where we spend a lot of time hitting the flash disk.

    it's a lot of work, mostly due to the limitations of the device and kernel I have to work with, but it's coming along. Unfortunately, it still hits me, too (I can't run "Google Earth" with Hi-Res images and sync "Google Currents" at the same time without running into the same issue you do) but I'm making progress- I've got unreleased patches that are working much better than stock, and as soon as I'm satisfied with them, they'll go into a nightly.
    View

New posts