yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer Android Development] archcantor:
MAC Address

Hi Tim,

I don't know if you are planning on working on the MAC address not being the real device address.

In March 2012 ricardopvz said: "wifi driver is reading nvram from /system/etc/nvram_nh615.txt (/system/etc/wifi/bcm4329.cal in TeamEOS Builds) which has no mac address defined. The solution is to make the driver read it from /data/misc/wifi/nvram.txt and use wifimacwriter to write the real mac to that file. It's already fixed in my CM9 build"

I don't know if this strategy still applies to JB 4.2 but I thought I would offer it up.

Is there a file we can edit to manually set the wifi MAC address? In a terminal, wifimacwriter returns my real MAC address.

-Rick
[Eee Pad Transformer Android Development] PeQuEsan:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

Yes I did more than once in Timduru's kat kernel specific thread, some months back. He didn't see anything special, out of may be something related to Wifi, if I remember well.

I'd do it as many times as any dev asks me... In fact I've offered them some posts back various times... :(

Desde el móvil...
[Eee Pad Transformer Android Development] PMcHargue:
Thanks for the great work!

Using TWRP 2.3.2.3,

factory reset

Wiped Chaches

Flashed:

'EOS4.2.2-tf101-20130216_previewB156.zip'

'gapps-jb-20130105-EOS-TF101-ONLY.zip'

'Tim_KatKernel_94_JB4.2_Lidpatch.zip'

Installed:

'K.A.T_V1.2.5.apk'

'SwiftKey 3 Tablet'

'APEX Launcher'

I'm not too facile with the backed up stuff, so I just re-entered a lot of information when the system booted up.

I came from EOS3 #81. The new ROM, GAPPS, and Kernel work really well. Fast & stable. A great experience, and appreciated. There are a lot of things to explore in this, like the 'EOS settings -> System -> Power and Display' setting for "CRT Screen On/Off". (which I like)

Patrick
[Eee Pad Transformer Android Development] garyngkt:
I have almost the same set up except for Nova Launcher. Yes loving this B156. Good job again Tim.
[Eee Pad Transformer Android Development] archcantor:
I also am on B156 and KAT #94 and am also experiencing much better GPS performance. You do have to wait a bit after a flash to get it started. I ran the GPS status app and after several minutes I got 7+ sats and a fix. While it is starting up it looks like something is wrong as you get one sat, then it goes away, then another and it goes away, then periods of no sats, then a third and it goes away. Eventually several suddenly appear and a lock follows.

I have a Driod Razr Maxx HD. That device can get a GPS fix in an underground RF Screen Room. Too bad the TF101 has to be so dull with the GPS sensitivity. EOS has become my daily driver. I echo the appreciation for the hard work and support that goes into this ROM!
[Eee Pad Transformer Android Development] garyngkt:
I am trying to understand better the CPU Overclocking on the EOS Control Centre, my default values are Minimum : 312Mhz and Maximum : 1000Mhz, do I need to check "Set Clock Values On Boot"?. Are these values considered overclocked compared to stock ROM? Thanks.
[Eee Pad Transformer Android Development] shonkin:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

Default values are 216 min, 1000 max.

People monkey w both settings, many going w/ 312 min and 1400 max (much above this seems to result in some increase w/ SoD - Sleep of Death - incidents). But all of us who play much have to at least try the 1600 setting once. Hey, maybe on yours it will be stable!?

Blessings. Have fun.

Asus Transformer TF101 16g / 1.4ghz overclocked

EOS 4 Jellybean / Preview version #156

Kat Kernel 94 / Kat App

--

Don't blame Jesus for the Republican Party. Blame Ayn Rand.
[Eee Pad Transformer Android Development] farsight73:
At 1000Mhz is the dafult value and you don't have to set clock on Boot. But if you alter this value higher say 1200Mhz or 1400Mhz, please play around a while until you really satisfied with the new value and then tick the Set Clock Value On Boot. This will triggered the device to set at your prefered value every time you reboot your system. Never set it too high..
[Eee Pad Transformer Android Development] garyngkt:
Ok thanks. Will prob try at 1200 max first :victory:

---------- Post added at 12:09 PM ---------- Previous post was at 12:08 PM ----------

OK noted and thanks. Say if I set at 1200Mhz and play around, it will automatically be set to this speed without having to reboot?. Until I am satisfied with say 1200Mhz and then tick Set Clock Value On Boot the next reboot will have this new values?.
[Eee Pad Transformer Android Development] zAlbee:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

I experienced the same thing (posted a few pages back), when I dirty flashed from nightly 96 to Tim's B156 build. Not sure why, but even flashing Gapps multiple times wouldn't bring it back. I also saw a less smooth homescreen swipe animation (lower FPS).

Anyway, I did a factory reset (wiped data) and reflashed everything. Now it's running smoother with better battery life than any of the previous EOS 4 builds I tried. Not sure if it's related, but I started using deadline I/O scheduler instead of sio. Also, could be because I didn't install Google Currents this time. That thing seems to be syncing non-stop. :P

Finally, I must report one SOD after testing stock kernel for <24 hours, but none with KAT.

Sent from my Transformer TF101
[Eee Pad Transformer Android Development] frederuco:
Correct, no need to reboot to change your OC speed. The boot tickbox just means it will reset automatically when you boot up. If it does have stability issues or trouble booting, it will not set the values on boot (and will default to 1000 MHz) and will give a warning in the notifications about it.
[Eee Pad Transformer Android Development] sidneyk:
Stock kernel DOES overclock if you overclock it, unless it has been changed. You just have to go into the performance settings from OS control center or use a third party app such as CPU Master to do it. I haven't used the stock kernel for a few versions, but I used it a few back and it definitely can be OC'd.
[Eee Pad Transformer Android Development] garyngkt:
OK thanks frederuco. I am trying max of 1400MHz and min of 312Mhz now, Governor : Interactive. You guys are awesome and thanks for all the help.
[Eee Pad Transformer Android Development] PeQuEsan:
Yes I know... I mean that if you do nothing, max CPU freq is set to 1 GHz... You must go into EOS Performance settings and set it higher to overclock.

Well... no dev ask, but I attach logcat of one of my SODs, this night... I'll repeat the logcat so many times as it's needed if someone can look at it and find something... I just booted, set up the logcat capture and lock the tablet. Governor performance and min freq 4xx MHz... Many of "I/wpa_supplicant( 817): rfkill: WLAN unblocked" messages at the end... can't say if that's normal.
[Eee Pad Transformer Android Development] timduru:
Just a general remark as a few things surprises me in what I see in the previous discussions for the few having stability / SOD / RR issues.

I thought it was kinda obvious, but before reporting an issue, make sure it's not because you are overclocked yes.

Switch back to the default governor / freqs, don't use experimental governors like smartAss and so on

and try to see if you still have the issue before reporting.

Overclocking and playing with governors sure can generate stability issues, I thought it was kinda obvious, but it seems not ;)

It's kinda summarized in the general remark in the "How to report":

- try to reproduce your issue right after flashing and before restoring anything

But not if you don't do a full wipe as it'll catch up your previous overclock settings if you used the EOSControlCenter to overclock.

So if I see someone reporting a stability / SOD / RR issue and that he's overclocked, I'll just ignore the report, easy ;)

hmm, interesting.

looks a bit different than the other logs you had sent,

even if it still seems related to wifi though.

Maybe 4.2.2 is a bit more verbose or something.

I see that a bit before too:

NetworkInfo: type: WIFI[], state: CONNECTING/CAPTIVE_PORTAL_CHECK, reason: (unspecified), extra: "ACMT03", roaming: false, failover: false, isAvailable: true

E/WifiStateMachine( 752): Error! unhandled message{ what=131092 when=-2ms }

What kind of wifi network are you connecting to by default ?

and what are the networks available in the list of networks at your home ?

Kinda looks as if it's trying to connect to a network that makes the wifi statemachine barf.

Could you try to turn wifi off before letting your tablet sleep, and see if it wakes up or if you still have SOD.

Just to make sure: also push the power button on the tablet itself to try to wake up.
[Eee Pad Transformer Android Development] pappiedappie:
Just reporting:

I did this time a full wipe (read clean install) and mine RR are decreased to 1 after the past 48 hours (as far as I can check) instead of several RR a day !! I flashed B156 and KAT kernel 94 lidpatch, then reboot, then flashed GAPPS (not the MX stuff but the one says ' only for eos'). So for now I'm very happy with this version. Thnx Tim very much for this rom.

p.s. Because Tim mentioned that the stock app launcher could have a little lag, I immidiatly flashed apex launcher. No problems at all for this moment.

p.p.s Before going to flash I backuped all my apps with Titanium Backup and restore them with data. This worked fine for me.
[Eee Pad Transformer Android Development] mihai.enea:
All works fine for me...no RR, no SOD.

The only issue is the battery life. In 2 days the battery drained from 100% and I didn't even used the tablet.

Solutions?
[Eee Pad Transformer Android Development] frederuco:
Chances are that the WiFi is set to always on. Go to Settings - WiFi - Tap the 3 boxes in the top right, Advanced, Keep Wi-Fi on during sleep change to Always
[Eee Pad Transformer Android Development] i9apps:
Hi timduru,

I got the device from the lab a few days ago

156B works awesome and very smooth when the nab bar is hidden :)

but there is a small bug with the boot animation so for now i back to 155 which is perfect.

Thanks again for all the awesome work Tim.
[Eee Pad Transformer Android Development] JoinTheRealms:
No issues with the boot animation on my end afaik, what issue are you having?
[Eee Pad Transformer Android Development] darkvoid_66:
My wifi is always on and I get around 4 days usage with a bit of usage every day before going from 100% bat to 0%.
[Eee Pad Transformer Android Development] billouetaudrey:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

2day2h7m

5h40 screen on

Tablet 31% Dock 0%

Wifi always ON, no game, 10min video player, FB , Tapatalk, Mail, FlipBoard

Envoyé depuis mon Transformer TF101 avec Tapatalk
[Eee Pad Transformer Android Development] JoinTheRealms:
I feel 1000mhz being stock is a bit conservitive for the terga 2, mine overclocks to 1600mhz fine, had ran it stable for weeks but lowered it increase battery life(wasn't an issue anyway) 1640mhz was boarderline stable with k.a.t kernel, raymanfx's kernels were stable at 1640 due to i assume higher voltage, but i agree there is no point overclocking past 1400mhz as it seems optimal to this tablet (i.e you can notice he performance increase without noticing the battery life decrease)

Any one having issues with rr/sod make sure your using the stock cpu governor (interactive). Smartassv2 caused deep sleep/ screen off random reboots that had had a noticeable pattern on my tablet. switching back to interactive 100% solved it for me.
[Eee Pad Transformer Android Development] demod_oz:
An update to the strange screen lag that does not present itself when scrolling via the dock trackpad. It happened again on the 92 kernel.

I've attached logs, plus an animated gif showing the problem. Keep an eye on the the falcon icon in relation to my finger. its only 5 frames but you can see what I mean.
[Eee Pad Transformer Android Development] mihai.enea:
And by doing that I'm not setting it to "always" ...and in this case it consumes more battery?
[Eee Pad Transformer Android Development] frederuco:
Oops, I meant to say NEVER.

DOH!
[Eee Pad Transformer Android Development] Ralkkai:
I'm behind a few nightlies on 92 I think and am getting things needed to update, but noticed that the gapps are still from previous versions. I'm wondering if there is an updated gapps package to download or not. I'm asking becuase I am having issues with ome apps updating properly, namely youtube, and think it's from the specific gapps used to install it. I can't uninstall it properly to install a fresh version from the market.

TL;DR is there a newer gapps to download?
[Eee Pad Transformer Android Development] vietchinh:
Do oyuguys notic at smartass it get stuck at 1504 mhz ( as example) all the time?

Like its stuck at performance mode.

I'm gonna recheck it but i am sure that it is. + its fresh B156
[Eee Pad Transformer Android Development] sttovo:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

Lol, hit Thanks by accident. Sorry! I run smartassv2 at 1504. I just checked SmartCPU and I see it scaling fine through all the frequency bands.
[Eee Pad Transformer Android Development] just lou:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

Interesting. I'm currently out of the U.S. connected to a crappy hotel WiFi signal, and my TF has a SOD and a RR, both within an hour of connecting. I never, ever, get either when I'm home. My setup is simple and not extreme. 312/1200, sio, interactive. 156 with 94. If it happens again, I'll try and get a log, but my time online will be very limited.

.
[Eee Pad Transformer Android Development] evoer:
http://xdaforums.com/showthread.php?t=2012857
[Eee Pad Transformer Android Development] wilkster:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

I have seen this. I went back to interactive gov.
[Eee Pad Transformer Android Development] frederuco:
I had noticed this on B155 with KatKernel 94 that when at 1.4 and Smartassv2 that is is almost ALWAYS at 1.4 GHz. I just switched to Interactive and the problem went away.
[Eee Pad Transformer Android Development] PeQuEsan:
I just wan to clarify that I've always done my tests with clean install, not even entering EOS Performace Settings... So no overclock, obviously. I've stated that in all my reports. Hope this is clear.

Thanks to take the time to see the logcat again, Timduru.

Back in time (TeamEOS3 + first Kat Kernel versions), I tested disabling wifi, and I had same SODs... What's more, I've changed my AP twice during all tests for the last weeks... And also I always push tablet on/off button to try to wake it... I don't just sit and wait the opening the dock will do the job.

Anyway: when I get home I'll go back to 1GHz/216MHz, interactive governor, and disable wifi. Then I'll reboot tomake sure we've got a "clean" situation, start capturing logcat and lock the tablet... We'll see.

Thanks again.
[Eee Pad Transformer Android Development] vietchinh:
I have one question:

Can tim bring back the usb host API of 4.0.4 to 4.2.2? for usb BT joystick controller?

Or its impossible?
[Eee Pad Transformer Android Development] DerSandmann:
Cornerstone comes again! Could you make a cornerstone version like on the old days? https://github.com/Onskreen/cornerstone
[Eee Pad Transformer Android Development] [MajorPain]:
The issue I have with the these nightlys is I can't use my ps3 controller. No fix near it seems.
[Eee Pad Transformer Android Development] timduru:
4.2.2 gapps for TF101

Here's new 4.2.2 gapps for the TF101: gapps_4.2.2_TF101_20130219.zip

It should have Keyboard auto-correction working and no crash.

Swipe is activated but you don't have recognition.

I think it's better to go back to a non crashing gapps keyboard by default ;)

If you prefer to have swipe but no autocorrection, just flash the old gapps package for the moment.

Make sure you do it this way for testing to make sure it cleans up the previous installed gapps:

- format /system

- flash the rom

- flash gapps package

- flash optional kernel

- wipe /cache + dalvik-cache

reboot

Test& report :)
[Eee Pad Transformer Android Development] lujo_zgb:
Please delete. posted in the wrong topic. sorry
[Eee Pad Transformer Android Development] just lou:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

Was there a new nightly that was pulled, or did Goo just lie to me? I got a notification for a ROM update but it said there are no updates when I checked it. ;)
[Eee Pad Transformer Android Development] droyd4life:
Still Lagging.

Running B156 with Kat kernel. Still lags in the homescreen. Looks disgusting. When I hide the status bar it's smooth but other than that its super laggy. Any fix?
[Eee Pad Transformer Android Development] anarox:
I turned off Wifi optmization and alot of my flicker went away, even thou the Catlogs never showed any indication that it was a problem. Oh well, maybe the flicker comes back in a day or two. My hardware is at fault somehow
[Eee Pad Transformer Android Development] mariox26:
i use last version of sixaxis controller with no problem on game with ps3,is already fixed.
[Eee Pad Transformer Android Development] anarox:
the new version is for jb 4.1.1 , could work on team eos 3 4.1.1 rom?
[Eee Pad Transformer Android Development] JoinTheRealms:
@ A developer

I found something that could be causing the u.i lag at home screen could it have anything to do with the gpu being forced to render compositioning on the home screen? if the setting to force gpu compositioning is enabled the u.i lag becomes apparent throughout android, rather than just the homescreen. Have no idea how to test it out more but does seem to be link.
[Eee Pad Transformer Android Development] just lou:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

Get rid of the stock launcher.
[Eee Pad Transformer Android Development] PeQuEsan:
Ok. Test done with default performance settings and wifi off... Same SOD after some hours of deep sleep. Here you have the logcat Timduru. Hope you can see something new.
[Eee Pad Transformer Android Development] jab0321:
Saying that the results of people's work is "disgusting" is a pretty rude statement. Also this is a known issue that just cropped up again on 4.2.2. If it is really upsetting, then you should try flashing B155 which has very smooth everything, or you can use a different launcher which also is suppose to fix the lagging.
[Eee Pad Transformer Android Development] droyd4life:
Dude i tried nova, stock AND TREBUCHET! They all lag unless I hide the navigation bar
[Eee Pad Transformer Android Development] evoer:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

Somethings wrong with your device ,0 lag here...maybe start over fresh?
[Eee Pad Transformer Android Development] Radiofodder:
I've started fresh over. You're aware he's talking about the preview B156 right? Mine is choppy in a few apps with the navigation bar active: Chrome Beta (not the regular version!), Google Play Music and every launcher I've tried so far.

I did a factory reset along with cache wipe before flashing the rom. It wasn't like this on an earlier version, so it has to be something different. I'd be impressed if this is fixed though.

Keep up the great job EOS!
[Eee Pad Transformer Android Development] anarox:
Chrome beta is even slower than the regular version, the regular version is stable but takes alot of memory and drains the battery. Stock Browser with stick it player for youtube is the most awesome browser experience I have had ever. Stick it video player can run youtube mobile so it scales perfectly
[Eee Pad Transformer Android Development] farsight73:
Keep faith.. all these lagginess in 4.2.2 will eventually be fixed. Just the matter of we're the end user to be more passion along the way.

However, I've not experience any severe lag. Everything seemed working really great here..
[Eee Pad Transformer Android Development] evoer:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

Same here
[Eee Pad Transformer Android Development] JoinTheRealms:
This, what im calling "u.i" lag is a verry little amount of lag and hardly an issue whatsoever but other then that slight problem this rom is 99% perfect for me
[Eee Pad Transformer Android Development] garyngkt:
I'm having a good time with 4.2.2.
[Eee Pad Transformer Android Development] just lou:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

Then you have issues unrelated to the ROM.
[Eee Pad Transformer Android Development] JoinTheRealms:
All launchers other than stock run much smoother then even eos3 for me with the nav bar off, its a small price to pay for the smoothness you get out of it (replacing it with gmd gestures or lmt are better alternatives anyway)
[Eee Pad Transformer Android Development] garyngkt:
I am also testing out without NavBar and using LMT control gestures
[Eee Pad Transformer Android Development] shonkin:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

Tim,

First, let me say some of the newest comments here apparently come from either jerks or trolls. Hope you don't get too discouraged by such nonsense.

Second, I did the install as instructed and all looks good at present. But one small question. I have always installed 1. Rom 2. KAT Kernel 3. gapps. Is your instruction re installing the optional kernel *after* gapps a change or have I been doing it wrong all this time? And/or just how much does the order matter?

Again... THANKS for a great Rom keeping our TF101s happy.

Asus Transformer TF101 16g / 1.4ghz overclocked

EOS 4 Jellybean / Preview version #156

Kat Kernel 94 / Kat App

--

Don't blame Jesus for the Republican Party. Blame Ayn Rand.
[Eee Pad Transformer Android Development] alizafar:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

Love the release #153

However its a heads or tails game here with my tf101,sometimes its responsive other times its superlaggy

BTW I am using lmt and gmt with nav disabled.

Launcher is apex

Clock rate is 1400 to 1500

Lag free io

Received reboots every 8-9 hours or randomly while watching youtube

Good news is that the DSP problem is reduced but a certain value and is good but not perfect

Bad news is that the GPU is down clocking randomly with the CPU please check the kernel.

I hope this help trying to make our tf101 the best of what it already is :)
[Eee Pad Transformer Android Development] frederuco:
I have tried it both ways, and it does not matter in my experience.

But, I think it is listed this way because you MUST flash the ROM first, then 99% of users will need the GAPPS. Since the kernel is optional, it is listed 3rd.
[Eee Pad Transformer Android Development] JoinTheRealms:
As per tim's instructions put clock speed and governor back to stock (1000mhz max 300mhz min, interactive) and see if the problem persists as overclocking is basically unsupported as it opens to many variables causing the problem.

Edit: For me just changing the governor back to interactive stopped random reboots completely.
[Eee Pad Transformer Android Development] jays473:
It dont matter if gapps first then kernel or kernel fisrt then gapps...same end result
[Eee Pad Transformer Android Development] fone_fanatic:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

Flashed B156 and Kat Kernel 94 2 days ago. So far one of the most solid builds I've been on. No more SODs or RR! I'm not overclocked or any other system "tweaks".

Also using the older EOS 20130105 GAPPS.

I would consider this a complete and final build :D
[Eee Pad Transformer Android Development] pappiedappie:
agree +1
[Eee Pad Transformer Android Development] sindamc:
Ive been using this build since it went out and i must say... besides some small lag... i didnt had any bug till now!

I think you can pass it to a [STABLE] :D
[Eee Pad Transformer Android Development] miltosz:
I have a TF101 with stock ICS 4.0.3, and would like to flash the Team EOS 4 ROM.

I've never done any flashing on an Android device before.

Could someone kindly point to me what detailed steps I need to follow for install the new rom?

Thanks!!!!