yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer Android Development] timduru:
So anyone have been testing the new live Keyboard switch layouts ? :)

Just to make sure they are working now at least for those listed ?

I'll remove the other ones and push that if that's the case. :)

I've done a bit of testing, and I'd say that EOS4 is actually giving you the "real" chip mac address. :)

The rom still contains everything for the "old mac override logic" and everything seems correct, the nvram path is ok in the kernels and points to /data/misc/wifi/nvram.txt

wifimacwriter is called correctly and updates the macaddr param in the nvram.txt file based on the previous value it finds in the file that is in the p5 partition.

The thing is just that the kernels are using the more recent brcmdhd driver now (which give better results) instead of the old brcm4329 driver asus / some roms are using, and that driver is not reading the macaddr param from the files, I don't see traces of that in the new dhd driver code.

So either it was a feature that was only in the previous brcm4329 driver, or that it was added by asus I'd say, so that they can override the chip's mac address with their own vendor range.

The brcmchip has already a unique mac hardcoded inside, so it should be that one that is used I'd say now.

Looking in the kernel logs after booting the new dhd driver just seems to be doing exactly that, it uses its hardware internal one.

The "real" mac is actually that one. The other one seems to have been overriden by asus ;)

So it's a feature not a bug ;P

The new driver is freeing the real mac and booting out the asus overriden address ;P

Long live the new mac address ! ;)

Well anyway, the important thing is that it stays consistent from boot to boot and unique inter-device.

It seems to do that here as long as you use a rom that is using the same driver, ie the brcmdhd one, it should keep the same macaddr.

The goal is just to have a unique value per device, each vendor has a unique range, and then the vendor chooses a unique addr for every device, so that's normally what broadcom has done.

There should be ways to do the same mac override in the new dhd driver, but not sure if it's really worth it.

as less and less users are going to use the stock roms, and more and more kernels are migrating to the latest dhd driver,

so I'd say that we'd be better not to touch it and simply use the new driver logic and the brcm chip real mac address.
[Eee Pad Transformer Android Development] koutsouk:
I tried Tim. Greek works ok now! One thing i can nit find is how to put tones in the words. Both with or without dock. I think that greek keyboard does not have tone button or something with combination . am i correct?
[Eee Pad Transformer Android Development] hardy81:
Today it seems this fixed the browser instability. Should be "advertised" heavily since probably most people don't have a chance to read through this whole thread.
[Eee Pad Transformer Android Development] timduru:
Good, thanks for the report :)

No idea for the "tone", not sure what that is, and never seen the greek keyboard :)

Maybe the browser was not fully stopped when you tried yesterday or something, and rebooting picked up the setting correctly.

Good that it works then :)

It's in the Tips link in the 2nd post and my sig.
[Eee Pad Transformer Android Development] Ivanovic:
Απ: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

My fellow Greek man is referring to intonation! E.g η and ή

On the road using my HOX
[Eee Pad Transformer Android Development] Quintasan:
Selecting Polish language from EOSCC WORKS, try things like alt+o (should give you ó) but there is no Polish in asusec. In other words, removing Polish from EOSCC will introduce a regression
[Eee Pad Transformer Android Development] inigoml:
Fantastic, Tim!! Working like a charm, at least with English (UK) and swapping with Spanish.

By the way, I'm still atonished by the "Spanish (Laos)" keyboard... :eek: If my geography doesn't fail, Laos is located beside Vietnam and Camboya, and if my history doesn't fail also I can assure Spain NEVER has a colony or territory in Laos... Philipines was for 400 years part of Spanish Crown but Laos... never! :) I'm pretty sure nobody natively speaks spanish at Laos... :laugh:

Perhaps a mistype error... and Laos is LATAM (Lationamerican).
[Eee Pad Transformer Android Development] aspros21:
Try flashing stock ics stock kernel again, after restoring your backup and before reboot. Does yous ics backup has included the kernel you had?

---------- Post added at 03:26 AM ---------- Previous post was at 03:14 AM ----------

Here: http://public.timduru.org/Android/tf101/eos4/#main
[Eee Pad Transformer Android Development] alberteske:
EOS4.2.1-tf101-20130101_previewB103.zip

B103 is UP! :good:

http://downloads.timduru.org/android/tf101/eos4/
[Eee Pad Transformer Android Development] cimbike:
And also B82 kernel.
[Eee Pad Transformer Android Development] inigoml:
UK keyboard working. These are step I followed:

1- Delete all your keyboard preference selection from Android Settings (unselect any keyboard layout you have. In my case, spanish and English US as it's quite similiar to UK one)

2- Go to EOS Control Center->System->Devices and select English UK as your hardware keyboard layout.

3- Reboot
[Eee Pad Transformer Android Development] kukky:
and where can i find changelogs?
[Eee Pad Transformer Android Development] timduru:
New 4.2.1 preview version B103

Preview B103 Main changes:

- resync with gerrit

- BT perms fix

- Increase atmel touch size to allow Capacitive pens to register

- launcher & misc optimizations

- system_server should be back to ~0% cpu if autorotation is off

- Add 48k-in sampling rate support for Skype

- Change recording mode switching logic in case of mic-in & out stream overlap (Skype issue)

- update ntfs-3g to 2012.11.07 + android fixes

- Display build version in Settings

- Fix recent apps rotation detection issue if not in autorotation mode

Have fun and for those who had the few issues listed, report if it works now or not.

If it doesn't, follow the report procedure and send a new logcat.

I can now use Skype with the auto echo thingie... :)

Preview version main Info & Download links

How to install

Main changes for the preview

Changes on teameos gerrit

4.2.1 Preview known issues & Workarounds

How to report an issue

What to include in the report

Hey, no picking in the directory ;P

Nah don't use that, it's just the first #82 EOS kernel for the 1st 1st preview version from weeks ago when the preview zip didn't have a flashing kernel blob.

I'll just delete that actually and clean up the dir a bit *g* ;)

Audio is the same than on EOS3.

If you want to increase it just use the K.A.T app

I post them on the main preview page when they are ready ;)

http://public.timduru.org/Android/tf101/eos4/

Better not link directly to the download directory but to the main page that contains all the info. :)
[Eee Pad Transformer Android Development] sidneyk:
Actually, that's an older kernel. Should probably either use the kernel it comes with or latest Timduru kernel.

[EDIT] Oops, timduru beat me to it above.
[Eee Pad Transformer Android Development] edd080:
When upgrading from B98 to B103 do i still need to flash gapps ?

Thanks for the help..
[Eee Pad Transformer Android Development] sidneyk:
If you follow the recommended procedure which includes wiping /system, then, yes, you'll have to reflash gapps.
[Eee Pad Transformer Android Development] edd080:
If I read correctly on Tim's page; when upgrading from 4.2.1 B98 to 4.2.1 B103 there is no need to do a full wipe..

Updating from EOS 4.2.1 #XX to #YY:

You can skip the full wipe step
[Eee Pad Transformer Android Development] mrwolf85:
I don't understand why every time I flash over a newer update of eos4 I must re flash gapps! Is a bug or a right thing?

Thanks

Inviato dal mio Transformer TF101 con Tapatalk 2
[Eee Pad Transformer Android Development] sidneyk:
Correct. But it does say to wipe /system and caches, which isn't a full wipe because it leaves your apps and data in place. Gapps are stored in /system, thus the need to reflash them since they are not included in the ROM.

---------- Post added at 03:08 AM ---------- Previous post was at 03:07 AM ----------

See above.
[Eee Pad Transformer Android Development] mrwolf85:
I already saw, but I usually whipe only cache and dalvik, I not whipe system so my gapps may not be delayed every time, but when I start the tabled after an upgrade my connection with Google account is lost and the only way to have back is to re flash the gapps!

Inviato dal mio Transformer TF101 con Tapatalk 2
[Eee Pad Transformer Android Development] sidneyk:
The thing is that most custom ROMs are wiping /system as part of their flashing script anyway. I don't know if this is true with eos4, but it is the recommended procedure and if you just figure you'll have to always reflash gapps anyway then you'll only have to wait once through the upgrade process instead of twice.

---------- Post added at 03:45 AM ---------- Previous post was at 03:38 AM ----------

I concur, photosphere is crashing for me, too. Both on version B98 and B103.
[Eee Pad Transformer Android Development] alberteske:
Skype

Skype buit in microphone is working with B103!

One question: why voice recorder is in the ROM but we do not see it as an app?
[Eee Pad Transformer Android Development] timduru:
I don't understand why you don't simply follow the procedure ;)

Upgrading from a previous EOS4 version, it just says that you can skip the full wipe, not that you can skip gapps.

So that still leaves you these steps:

Backup everything !

Go to recovery

format /system

Flash the rom

Flash gapps

Wipe cache/dalvik

Reboot

Good for Skype, finally, that was a pain to fix ;)

For voice recorder, no idea..

Maybe it's just needed by another app but is not an app itself ?
[Eee Pad Transformer Android Development] mattiadj:
Is the problem of mount and symlink fixed in newest version?

From universe with my gs3
[Eee Pad Transformer Android Development] alberteske:
I do not see it anymore for the past updates :(

---------- Post added at 11:34 AM ---------- Previous post was at 11:32 AM ----------

in the EOS gaps, Genie widget is missing.

for those who like it, I found this version that works perfectly:

http://xdaforums.com/showthread.php?t=1347792
[Eee Pad Transformer Android Development] timduru:
There's no problem as far as I know, the mounts and symlink are the way it should be in 4.2.1

you most likely need to find another way of doing it in your script.

Send me a PM explaining exactly what your script is trying to do, which exact commands it was using

and maybe I can help and see how we can do it in 4.2.1

You mean since EOS4 or was it in the first versions of EOS4 then disappeared later on ?

Isn't it part of gapps actually or something ?
[Eee Pad Transformer Android Development] edd080:
Hi Tim first of all thanks for your help and lovely updated Rom, unfortunately directorybind still does not work when I try to bind the data of an app from internal sdcard to the microsdcard, the problem remains the same, I am attaching a logcat and also a screenshot of how I am binding a particular app just to test if the binding works..

Thanks again..
[Eee Pad Transformer Android Development] timduru:
There is Polish in asusec if you flash the zip, that's the goal of the zip, when I was talking about removing it I was talking about asusec, in case it doesn't work.

I just tried it and it seems to work then: ó

I thought Polish was not working because I didn't really see any difference from english when I typed a few letters.

So that's why I need you to test or tell me which key combination to test ;)
[Eee Pad Transformer Android Development] jonnyjb:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

I guess it was in pre jelly bean I remember it, to bad it's not a feature anymore
[Eee Pad Transformer Android Development] bigrushdog:
Eos Control Center does not require root for any functions at this time. Please post logcats of any multi user related fc's in the bug tracker. Until now I have paid little attention to anything multi user related as I think the whole thing is just stupid. Nonetheless I'll get to work on it.
[Eee Pad Transformer Android Development] Yu88:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

I'm having a strange issue. I installed this awesome rom 4 days ago and everything was great, only the known issues like Google Now and SOD but with your previous replies I was able to fix them. But now I had a problem with the battery. When I connected the tab to the charger it only says charging but it never charges. Then I did a wype battery stats and now charges but is taking too much time to full charge. Has been passed 24 hours and only charges from 40% to 80%.

Some ideas? Thank you.

PS: Sorry for my English.
[Eee Pad Transformer Android Development] JoinTheRealms:
This is an unrelated issue to the rom, there are many threads in the general/questions forums with the same issue(ive had the same problem alswell) it was resolved with a new cable.
[Eee Pad Transformer Android Development] Yu88:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

Nice. Thank you. Let me check then. The curious thing is this issue happened since I flash this rom but off course it can be a big coincidence. If it is, that make this rom even more perfect and awesome.

Thanks so much guys for your wonderful job.
[Eee Pad Transformer Android Development] MassStash:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

anyone able to point to where to read on how to access data from 4.2.1 once flashed 4.2.2?

~ TF101 on K900's AOKP

Currently OC'ed to 1.4, KatKernel 70
[Eee Pad Transformer Android Development] PMcHargue:
Maybe that's the graphic that can be shown on turn off, and turn on. Forget what it's called. 'CRT effect', or some such.

Pat
[Eee Pad Transformer Android Development] JoinTheRealms:
Off the top of my head try /storage/emulated/0/0 or somewhere around there.

Does anyone know of an over clocking app that allows increasing the voltage from within android? Antutu seems to only under volt.
[Eee Pad Transformer Android Development] AngryDinosaur:
how smooth is the rom, tried other JB roms including official cm they are kinda choppy, how is this one?
[Eee Pad Transformer Android Development] Cdubzz20:
I have had this issue with this ROM as well, I used my charging cable when I was on stock ICS, and upgraded

without

connecting it via usb and then it would not charge. Nothing changed except for the ROM, I don't get this bug at all... The cable was brand new a month ago.
[Eee Pad Transformer Android Development] JoinTheRealms:
By usb you mean the usb cable connected to ac? (usb ports in pc's will charge very slowly and will not indicate that they are charging). And when you went back to ICS it started charging again? very strange if so...
[Eee Pad Transformer Android Development] chatch15117:
i just came from 81 with kat69 kernel. home screen lags with status bar. If you hide it, it's smooth. If you have browser open and status bar is showing, it does not lag. so it's only the home screen. and if you use another launcher it is smooth again
[Eee Pad Transformer Android Development] pkfox:
Hi there what's the status bar ?
[Eee Pad Transformer Android Development] JoinTheRealms:
Statusbar/ systembar = top bar
[Eee Pad Transformer Android Development] nEUTRon666:
I also got this, and i asked this many pages ago. This started with flashing this rom...says charging but doesn't....also my dock is not charging anymore...must be more than fortune that some or many people have a bad cable at the same time ?!
[Eee Pad Transformer Android Development] timduru:
Battery levels

There are cables issues that can happens,

but a few of the reports sounds more like if the battery calibration file is off,

it has been an issue as old as the first version of android.

If shouldn't matter if you're plugged in or not while flashing,

however it could matter if you're not charged 100% when you do and that you wipe the battery calibration stats.

(or do a full wipe)

Meaning that android needs to "learn" again what is the full capacity of your batteries.

It usually helps if you're at 100% and that you let it then discharge.

Usually it will catch up after a full charge / discharge cycles.

Maybe the algorithm in 4.2.2 is less reliable or takes longer time to regenerate an accurate battery stat file too.

What I would advise to do for those having the battery issues:

- Turn off the tablet

- if you have a dock: undock the tablet.

- Charge separately the dock & the tablet, leave them charging overnight for example

(

while still making sure the tablet it turned off

)

The charging should occur fine while turned off as it should be fully hardware controlled in that case and the battery calibration file won't be used.

- Once both are charged fully, if you have a dock, reconnect it.

Leave them plugged in the charger (the wall charger)

- wipe the battery stats or do a full wipe, then install / boot the rom

- use your tablet normally on charger for a few minutes

- then unplug

- keep using the tablet until it's fully discharged and android tells you to plug in the charger.

- plug the charger, and leave it plugged in until it is back up to 100%

- repeat discharge/charge cycle.

That should allow android to regenerate accurate enough battery stats.
[Eee Pad Transformer Android Development] fone_fanatic:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

Apart from the very brief initial wake lag, it is running super smooth on my end. I'm using timduru's B156 preview and his KAT kernel 94 (both can be found here). Honestly this is the smoothest and most stable my tab has ran in a long time. I highly recommend you give it a go.

As you mentioned at the end, try another launcher. I'm using apex (with apk moved into /system/app) and only have a really small insignificant amount of lag after waking the device from deep sleep.

B156 + 94kernel is running extremely well for me.

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

Is the cable plugged into the Asus wall charger or your computer (or other wall charger)?
[Eee Pad Transformer Android Development] Shesakillatwo:
If you look in this thread http://xdaforums.com/showthread.php?t=2137602 I had purchased a Non Asus Charger and had some strange behavior which folks told me could not be the ROM, so I let it go at the time even though I had ordered another replacement charger with the same results. If it is possible that this is related or that the ROM could cause charging issues with an aftermarket charger rather than the Asus, it would be cool if that could be corrected. Posted it the before I had 10 posts and forgot about it till I saw this thread. These chargers are currently collecting dust............
[Eee Pad Transformer Android Development] mgeniusm:
soooo happy

I was using external keyboard helper which was a good solution, but this is much better! Thanks
[Eee Pad Transformer Android Development] Krimbeleco:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

Hello guys....:sly:

both use the same kernel kat,Which is better between Rom B97 and Rom preview b156?

Send From my Nokia 5110 no Cllasic
[Eee Pad Transformer Android Development] just lou:
There's little difference right now. 97 contains most, if not all the changes from B156.
[Eee Pad Transformer Android Development] *Detection*:
You bought a new charger, even though the charging issues started after flashing the ROM, and didn't flash a stock ROM to test first ?
[Eee Pad Transformer Android Development] just lou:
There are also countless posts in various threads from people claiming charging issues when attempting to use non-Asus chargers.
[Eee Pad Transformer Android Development] Krimbeleco:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

and which is better,,,,

what rom are you using now....

Thx

Send From my Nokia 5110 no Cllasic
[Eee Pad Transformer Android Development] *Detection*:
Ah I know, I don't doubt that, I was just surprised that the guy didn't troubleshoot by testing a stock ROM first, before spending money

If I have a problem with my PC, I`ll troubleshoot windows first before thinking about buying new hardware :)
[Eee Pad Transformer Android Development] e154037:
Did you see Timduru's comments on battery charging(post #2597).

As he said, charging battery with tablet on is controlled by software, with tablet off is controlled by hardware.

Why don't you shut down your tablet and charge it over night. If still not fully charged, probably, something wrong with

your charger or tablet hardware. If fully charged, try to re-build battery calibration as said in Tim's post.
[Eee Pad Transformer Android Development] just lou:
I hear ya. It's funny that he posted a link to a thread where everyone told him to try a real Asus charger, but I guess he still wants to blame the ROM.
[Eee Pad Transformer Android Development] frederuco:
[ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

I think the issue is the stock browser!

:D
[Eee Pad Transformer Android Development] Quintasan:
Oh, I see, I flashed the wrong one I was like "Why the **** would you remove a perfectly working keyboard map".

For future reference you might try alt+{o, l, n, a, s, c, z, x, s, e} key combinations, they should respectively give you:

ó ł ń ą ś ć ż ź ś ę
[Eee Pad Transformer Android Development] jazzruby:
There's a relatively new kid in town: CPU Adjuster

-JR-
[Eee Pad Transformer Android Development] Shesakillatwo:
For clarification, I am not blaming the ROM or the charger, I was simply asking a question. I have two oem Asus chargers, and yes they work fine. I ordered the additional unit for my work location. The after market unit does not behave well as described, but on receiving a replacement unit that did the same thing it raised a question for me as to whether it could be something other than the charger. As you stated, I have not reflashed the stock ROM, nor have I looked to find a copy or how to do this. Sorry.

Having run repair centers and call centers for both test equipment manufacturers as well as IT organizations and coming up through the ranks from technical training I can asure you that I am well versed in troubleshooting concepts. I have seen way stranger things than code causing charger problems over my career, but I will offer my appologies out of respect to this group for asking questions before I had exhausted every possible cause.

Sincerely........
[Eee Pad Transformer Android Development] just lou:
Wait.. You actually have 2 OEM ASUS chargers that work fine, and when you ordered 2 knockoff chargers that didn't work, you're still questioning whether it could be something other than the knockoff chargers? :eek:
[Eee Pad Transformer Android Development] *Detection*:
If you have an SBK1 tablet (B6O or earlier, some B7O) you can use NVFlash to return to stock
[Eee Pad Transformer Android Development] timduru:
I finally got EOS4.2.2 to compile and boot with cornerstone :)

All the base of the multi window system is mostly working, still a few bugs here and there.

Like the services not starting hence why I had to take a photo for the screen capture *g* ;)

But not bad for a first version ;P
[Eee Pad Transformer Android Development] *Detection*:
Sweet, looks good

Just flashed the latest preview and kernel and have to say it is a lot better than the last one I tried

launcher lag is still there (It seems everyone porting 4.2.x has the same lag in their ROMs from what I've read) but the rest of it seems very nice, good job Tim cheers
[Eee Pad Transformer Android Development] Woody:
Quite impressive, indeed.
[Eee Pad Transformer Android Development] josteink:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

That's way above average cool. Saw your repo and wondered if it was anything current or working.

Guess now I know :)
[Eee Pad Transformer Android Development] alizafar:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

Wait Cornerstone is back? .. THATS AWESOME! RELEASE DATE?