yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer Android Development] josteink:
Before the screen turns off completely, the screen lock will still get activated with the screen dimmed, giving you time to slide to unlock if you want to.

I dont know how useful it is really, but it's there by default :)
[Eee Pad Transformer Android Development] jazzruby:
Let me see if I can phrase my question differently (I don't think we're on the same page).

Screen off for ~5 minutes

Nexus - touch on screen wakes it up > slide to unlock

Nexus 7 - touch on screen wakes it up > slide to unlock

TF101 - touch on screen DOES NOT wake it up only the power button wakes it up THEN slide to unlock.

Again,

Nexus(7) touch screen > slide

TF101 power button > slide

I don't mean to hammer on this but I don't think I was getting my point/question across, 'touch to wake' doesn't work, is it a bug or a limitation?

-JR-
[Eee Pad Transformer Android Development] josteink:
Fair enough. The answer would probably be that since this is something reasonably new, this is something which hasn't really been considered at all yet.
[Eee Pad Transformer Android Development] tscalia2:
I tried as well and Aroma hangs as it starts. Weird because Aroma works fine on this version of TWRP for the Verizon GS3 (d2vzw).
[Eee Pad Transformer Android Development] *Detection*:
Does Aroma work with TWRP 2.3.2.3 ?

I tried to flash it but it froze TWRP and didn't flash
[Eee Pad Transformer Android Development] tscalia2:
No, AFAIK it only works on CWM 5.8.1.8 repack
[Eee Pad Transformer Android Development] *Detection*:
Ah, nvm then, CWM kills TF's
[Eee Pad Transformer Android Development] josteink:
I've asked around. Seemingly all that's required for AROMA to work, it needs to have a kernel with a "touch screen driver". So this is most likely a kernel-issue, and not an issue with TWRP itself.

As TWRP itself depends on touch input, it would be logical to assume that it has some sort of touch screen driver already, but if it's the right one, and how things needs to be setup, I have no idea.

Anyone willing/able to provide some feedback on this? Any kernel options I should look into adding/stripping/changing?
[Eee Pad Transformer Android Development] wn1ytw:
Flashed the zip.

Rebooted to ROM EOS4 117 kk 103.

reboot to recovery and indeed I have 2.5.0.0

reboot to ROM - it boots but in notification I get triangle with 'overclocking not applied'

I went to EOS Control Center and indeed my overclock on boot to 1400 was all set back to 1000

I reset it and reboot, NG

cannot overclock until I restore my backup before installing TWRP 2.5.0.0

so I'm back to 2.3.2.3 and overclocked 1400 with nightly 117 & kk103
[Eee Pad Transformer Android Development] josteink:
Sounds strange. Technically speaking ROM and recovery should be 100% separate and unable to affect each other in that way.

Out of curiosity... did you ever try reflashing the ROM and kernel from the updated recovery?
[Eee Pad Transformer Android Development] wn1ytw:
I tried several times and each time I went to recovery I had to do a double reboot as I got this 'error'. I then tried to flash my ROM Gapps & kernal, and each time I did it wiped my apps. I tried the advanced and the 'most times tis is the only wipe you'll need.' wipes. When in the advanced I tried to NOT do a factory reset, but both times that seems to what I got. The screens/choices are not the same so probable confused me but I tried for an hour, my battery needs recharging after so many restores/flashes/reboots.

I appreciate the work but this version is not ready for general use by dummies like me!
[Eee Pad Transformer Android Development] i9apps:
Try to OC with CPU Master..working great here
[Eee Pad Transformer Android Development] josteink:
I know it's always easier to blame someone else, but I'm not experiencing this issue with my own CM10.1 builds.

That said, Tim usually knows pretty well what's going on and where. I can ask him for some feedback on this :)
[Eee Pad Transformer Android Development] wn1ytw:
Just reporting my results, I have no issues with 2.3.2.3 and am happy-just trying to be helpful. Thanks for the work. :cyclops:
[Eee Pad Transformer Android Development] timduru:
Shouldn't be linked to the recovery.

The criteria for not applying the overclock is based onto the time between the reboots. (4 mins minimum)

So if you reboot/flash too close from each other, it'll not apply the overclocking.

Wait a few minutes (It's using thtt for the test which checks that the last reboot was done more than 240 seconds ago), and reboot and it'll be applied again.

It's there to make sure you don't brick your tablet in case you overclock to a value too high and that it constantly crashes.

If it crashes right after one other crash, the overclock is reset that way and you can boot.
[Eee Pad Transformer Android Development] wn1ytw:
Thanks for the explanation and hint. I've now waited 5 minutes between each reboot and now recovery is 2.5.0.0 and overclocking works in EOS CC as usual. Thank you!
[Eee Pad Transformer Android Development] csb5731:
Could not replicate:

Started at EOS117/KK103lidpatch/whatever gapps

Wipe/Advanced: checked Dalvik, System, Cache (Not Data)

Flashed 116/same KK/same gapps

Clicked wipe Cache/Dalvik button (probably not necessary)

Rebooted

Data/Apps still there

Did the same thing back to EOS 117, worked fine, no data-loss. I think somewhere, you must have wiped data along the way.

I'll agree that the default wipe option isn't absolutely ideal for MY usage model - I am generally just applying latest EOS version over an older version without data-wiping and no issues, but it probably is for a lot/most of the flashers. The advanced wipe feature is great (though someday I am sure I will inadvertently check SDC, just because I am like that) and a little bit of a time-saver.
[Eee Pad Transformer Android Development] Alas2708:
Strange behaviour here :

wipe cache, dalvik and system

flash EOS latest nightly

flash gapps

flash kat kernel 103

wipe cache, dalvik again

boot

try to install the fixes using the kat app (mediascanner, gps and adblock) and all 3 fail...

doing the same with old recovery works fine

maybe the kernel doesn't get fully installed?
[Eee Pad Transformer Android Development] st0nedpenguin:
Sometimes the fixes only partially install here too, I just try a couple times and they eventually stick.
[Eee Pad Transformer Android Development] bfmetcalf:
I actually had kat app not work as well, wiped delvik/cache and flashed ROM and gapps again and it worked fine, thought maybe it was just the ROM, but may be recovery?
[Eee Pad Transformer Android Development] jacobsensei:
Guess there's no consensus to move this out of beta yet.

If there is a real problem, will Goo manager flash the current twrp2.3.2.3 version over this?

Is there a 2.3.2.3 zip?

Has anyone gone back?

Can't say I've had any problems with 2.3.2.3.

Just a little cautious when it comes to recoveries and bootloaders.

Running Josteink's 10.1 daylies, works great, just wanted to say thanks again for all you work on the TF101 and this recovery.

Sent from my Transformer
[Eee Pad Transformer Android Development] josteink:
Yes. And no.

But it would be fairly simple to package one.
[Eee Pad Transformer Android Development] bfmetcalf:
any word on this coming out of beta, it has been working great for me
[Eee Pad Transformer Android Development] the.teejster:
FYI,

I just used GOO manager to flash back to 2.3.2.3 from the 2.5.0.0 beta.

All seems fine.

I used 2.3.2.3 to flash josteinks 6/12 nightly build w/o issue.
[Eee Pad Transformer Android Development] stanguay:
The download link doesn't work in the OP?

Sent from my SAMSUNG-SGH-I747

---------- Post added at 07:38 PM ---------- Previous post was at 07:05 PM ----------

work ! ok
[Eee Pad Transformer Android Development] xbs:
Can't install from folders on the SD card, only files on root.

Is it normal?
[Eee Pad Transformer Android Development] josteink:
You can click on top where it says "internal storage" and you should be given a selector to choose where your ZIP files are location.

MicroSD is currently labeleed "SDC", but I'll probably do something to change that.

Basically, this is a change in the TWRP UI and no actual functionality should be lost :)
[Eee Pad Transformer Android Development] xbs:
Thing is I have a folder in the external SD card (SDC) and I can't get to the .zip files on that folder, in fact it doesn't show any folders at all, only the files that are in the root of the external SD card (SDC).
[Eee Pad Transformer Android Development] csb5731:
On the left hand side of the screen you should be able to see directories and navigate to them, at least in my case.
[Eee Pad Transformer Android Development] bsoplinger:
I too initially missed this as I was expecting directories and files to be listed together, folders then files following. It wasn't until the third time I had the browser open that I noticed the left hand pane and the directory list there.

Sent from my Nexus 7 using Xparent Purple Tapatalk 2
[Eee Pad Transformer Android Development] xbs:
Of course you can. Nevermind. Thanks.
[Eee Pad Transformer Android Development] sidneyk:
I've been using this through a few ROM flashes now and seems to be working fine. I haven't yet tried making backups or restoring them because I usually just use Titanium Backup for that. This version seems a little more responsive than the previous 2.3.x.x whatever it was. Took a little to adjust to the different wipe dialog, just have to be careful I don't accidentally wipe out my external sdcard. Keep up the good work.
[Eee Pad Transformer Android Development] bfmetcalf:
I have been using this since I started with the Domination ROM. So I have flashed probably upwards of 150 times and restored backups and all. I haven't had a single issue with it at all. It's been smooth and worked very well. I would say it should become a stable release soon :)
[Eee Pad Transformer Android Development] frederuco:
Agreed, I have been using it for the last week or so. It seems very stable, I have flashed between RootBox, Domination and EOS 4 many times trying to work out bugs and such. I have probably flashed about 20 times, and also restored older (TWRP 2.3.2.3) backups with zero issues.
[Eee Pad Transformer Android Development] stephane.papin:
But you can install it on TF101G model B70+ ?
[Eee Pad Transformer Android Development] frederuco:
I don't see why not. Other than the 3G radio, and a different SBK than the TF101, the TF101G is the same. You can run a TF101 ROM on the G version, and a TF101G ROM on the regular one.

I guess the only word of caution I would have is to make sure that you have ADB working before trying just to be sure you can get back to a working recovery by installing the recovery blob via ADB.

If I had a TF101G I would not hesitate to try it, but that is just me.
[Eee Pad Transformer Android Development] Magissia:
Hello, noticed the physical keyboard works on text fields, but wondering why it's not elsewhere (with arrows + enter to navigate ?) If it's possible to make it happens, it may save the screen from lots of fingerprints :P

Regards
[Eee Pad Transformer Android Development] josteink:
Did that use to work on 2.3.x.x though?
[Eee Pad Transformer Android Development] Magissia:
I never used versions 2.3, i was using Clockwork recovery, and physical keyboard was fully supported there. I honestly don't know if it was working before or anything.

Regards
[Eee Pad Transformer Android Development] josteink:
I honestly don't think TWRP supports full arrow-key navigation like CWM, because unlike CWM it has a lot more complex interface than just arrow up/arrow down + OK :)

I do think this is as good as it gets (at least for now). Don't quote me on that though ;)
[Eee Pad Transformer Android Development] frederuco:
Keyboard nav did not work in 2.3.X.X.

I use CWM 3.X up through 5.X with and without touch. I MUCH prefer the touch, I felt like I was going to wear out my volume rocker trying to flash a ROM using the non-touch. Even if it is arrow keys, it is much faster to touch the screen to get around.

IMO, if you are worried about fingerprints then you should get a stylus, or maybe stay away from a tablet. I have no issues with fingerprints on my screen. Rain-X helps keep them down if you are that worried about it.
[Eee Pad Transformer Android Development] bsoplinger:
I think the fingerprint comment was missing a smilie and the poster was just commenting that full use of the keyboard would be nice to have. I remember how much of a PITA using the miserable volume keys with my first non touch recovery on the Transformer. Found touch CWM and never used a non touch version again. I'm still on 2.3.whatever but keeping an eye on this thread until it seems safe. Haven't seen too many horror stories yet. ;)

Sent from my Nexus 7 using Xparent Purple Tapatalk 2
[Eee Pad Transformer Android Development] frederuco:
I jumped to 2.5.0.0 about 2 weeks ago. NEVER GOING BACK!

Love the Wipe Menu (tick what partitions to wipe rather than wiping individually). Oh, and it automatically checks that you are rooted before rebooting and offers to install SuperUser if it is not detected. Nice feature.

Also, my 2.3.2.3 backups restore just fine with 2.5.0.0
[Eee Pad Transformer Android Development] a.mcdear:
Is there anything that is known to NOT work on the 2.5.0.0 build? Just wondering why it's labelled beta? I've been using 2.3.2.3 for awhile now since it is the one that goo manager automatically installed, and so far I haven't found any issues with that version.
[Eee Pad Transformer Android Development] josteink:
Because it's not official yet, and because you want to make sure things like recovery are properly tested. That and because I was considering doing some very small changes to the build before shipping it off, but I haven't gotten off my arse to do it yet.

That said, it seems perfectly good and stable.
[Eee Pad Transformer Android Development] MassStash:
holy crap how did i miss this til now! couldn't wait to express my excitement, so i'll be going back and reading, but how the heck did you end up getting it to boot! did you have to take a bunch of stuff out like you were thinking in the main thread a while back?

~ TF101 on EOS Latest Nightly

Currently OC'ed to 1.5 with KAT Kernel 103
[Eee Pad Transformer Android Development] josteink:
The simple story is that once I started over from scratch (again), I did one major thing differently: I based it off a ICS-CM9 Android-repo instead of a more up to date JB4.1-CM10/JB4.2-CM10.1 repo. Once I got that building cleanly, I did some very small (and very targeted) alterations to the build setup and kernel to get it within the size-constraints of the TF101 recovery partition.

From there on, it was good to go. No functionality or anything needed to be sacrificed or stripped.

The long story is a bit more intricate, but you know, it doesn't really add much to the story, apart from developer-suffering ;)
[Eee Pad Transformer Android Development] ViViDboarder:
Bowing Out

Hey everyone. I've been non-existent for a while (new job) and recently sold my TF101. I just wasn't using it enough to justify keeping it.

Thanks for using Twrp and keeping me going for so long as you all did.

josteink, thanks for taking this on in my absence. Is there a thread you'd like me to point to in the OP?
[Eee Pad Transformer Android Development] MassStash:
Should he not be the official tf101 twrp maintainer now then? And just run from the twrp forum

~ TF101 on K900's AOKP

Currently OC'ed to 1.4, KatKernel 70
[Eee Pad Transformer Android Development] josteink:
Sorry to see you leave, but if you no longer have the TF101, I can't say I blame you. Thanks for the work you put down and into this.

If you want to link anywhere in your original thread, this thread seems as good as any :)

Cheers.
[Eee Pad Transformer Android Development] josteink:
I see TWRP 2.6.0.0 is out:

From http://www.teamw.in/project/twrp2

Looks cool!

But I also see some Galaxy Nexus users complaining that it is buggy:

http://xdaforums.com/showthread.php?t=1592689&page=134

What's the opinion here? Should I try to churn out a build? Or should we wait until we get more feedback that 2.6.x is stable?
[Eee Pad Transformer Android Development] Magissia:
I guess we should wait and see for now, we have a stable and good recovery partition now, i don't think it's urgent.

Regards
[Eee Pad Transformer Android Development] jazzruby:
TBH, I wouldn't mind testing 2.6 on the TF101

OTO, I tend to agree with Magissia

-JR-
[Eee Pad Transformer Android Development] jacobsensei:
2.6

Sent from my Droid Incredible
[Eee Pad Transformer Android Development] bfmetcalf:
I have heard rumors of 2.6.0.0 not running quite right on other devices as well. I would wait a bit on it.
[Eee Pad Transformer Android Development] csb5731:
Has anybody ever had their recovery become out of whack?

I've been using 2.5.0.0 (flashed the .zip) with no problem since early June other than rare wipe fails when using the “advanced” batch method, reverting to one wipe at a time always solved the issue. But I've been wiping and clean and dirty flashing and restoring nandroids back to my default setup (EOS) for 6 weeks or so with no problems. For whatever reason, before installing the new Katkiss ROM, I did it via a full wipe and then I decided to restore data from a previous EOS nandroid. It would fail. So I wiped everything and then tried to restore the same full (system, data, boot etc) EOS nandroid. It would fail too. I wiped everything, flashed an EOS ROM, KK, and gapps and tried restoring data from a nandroid made with the same setup and it would fail. Tried going through previous nandroids, and eventually only one ~ month-old backup took.

I was thinking maybe my recent nandroids, made from 2.5.0.0 were bad.

I re-installed 2.3.2.3 via Goo Manager, and tried restoring the most recent EOS nandroid (made from 2.5.0.0) that hadn't been working, and it restored with no issue. So the most recent backup was apparently fine. Dirty flashed katkiss ROM on top, works swell.

I am going back to 2.5.0.0 because I like it and appreciate the latest and greatest, just curious if anyone has had this happen before.

Cliffs

-2.5.0.0 working fine for six weeks or so

-Started getting failures restoring full nandroids and data only

-Restored to 2.3.2.3 and the same problematic nandroids (made w/ 2.5.0.0) restored just fine
[Eee Pad Transformer Android Development] MassStash:
Can't say that I've experienced this at all

~d2spr runnin' MSG & CHUBBZ V5.0.2; 'thraxed

cpu0/1: 1.512ghz | 81mhz | sleep 486mhz

Ondemand

row

mpdecision: off
[Eee Pad Transformer Android Development] adamtan:
- wrong post, should be in the official....
[Eee Pad Transformer Android Development] alberteske:
I am using it with another divice and it is really good!
[Eee Pad Transformer Android Development] simo.scorpion:
how can return with the official twrp 2.3.2.3 ?
[Eee Pad Transformer Android Development] josteink:
Flash via goomanager
[Eee Pad Transformer Android Development] frederuco:
I've never had anything fail (wipes, backup, restores or installs) on 2.5.0.0.

My 2.3.2.3 backups work flawlessly too.
[Eee Pad Transformer Android Development] simo.scorpion:
The backup of the 2.3.2.3 are compatinle to this twrp ?

Inviato dal mio GT-N7100 con Tapatalk 4
[Eee Pad Transformer Android Development] frederuco:
Yes. I have a few backups (stock rooted, revolver, LiquidSmooth, EOS, Domination, PA/CM hybrid, CM10.1) all made with 2.3.2.3 and they restore just fine with 2.5.0.0
[Eee Pad Transformer Android Development] MassStash:
2.5 working great with no issues here yet

~d2spr runnin' MSG & CHUBBZ V5.0.2; 'thraxed

cpu0/1: 1.512ghz | 81mhz | sleep 486mhz

Face Melting Ondemand

row

mpdecision: off
[Eee Pad Transformer Android Development] DanRo80:
Is anyone still visiting or working in the 2.3.2.3 build thread?
[Eee Pad Transformer Android Development] josteink:
Original creator of that build and thread no longer has a TF101, so he's a goner.

This is the "new thread" I guess. I'll consider adding a 2.6.0.0 build when I get back from my vacation.
[Eee Pad Transformer Android Development] sidneyk:
Good to hear. I'm using 2.6.0.0 on my phone and it seems pretty good. Your 2.5.x.x is working great on my tf101, by the way. Thanks and keep up the good work.
[Eee Pad Transformer Android Development] DanRo80:
My .zip downloads are not showing in the Recovery. It did this when I went to 2.3.2.3 and I was hoping it was something with that build. But it is also doing it on 2.5.0.0. What am I doing wrong or what has happened that recoveries are no longer seeing my downloaded .zip files?

Thank You
[Eee Pad Transformer Android Development] sidneyk:
I was having different issues with 2.5.0.0 seeming like it got corrupted somehow, to the point where I couldn't even get into recovery anymore. I wound up using BRK's v.8 tool to nvflash back to stock, reroot and flash cwm, flash twrp 2.5.0.0 again and then I was good to go. Just make a backup first, if you can.
[Eee Pad Transformer Android Development] josteink:
Are you sure you are looking in the right place? Maybe you are downloading to internal, but browsing external SD? Or something like that anyway.
[Eee Pad Transformer Android Development] DanRo80:
I took the sd card out during this to be certain because I thought of that same possibility. But no good. I'll give the V8.0 Toolkit method an attempt when I have the time to.
[Eee Pad Transformer Android Development] MassStash:
Something to do with the 0 folder stuff perhaps?

~ TF101 on K900's AOKP

Currently OC'ed to 1.4, KatKernel 70
[Eee Pad Transformer Android Development] DanRo80:
It was precisely this. Although I figured it out days before I came back to read this. :p
[Eee Pad Transformer Android Development] MassStash:
Hope life is goin well and wonder how 2.6.0.0 is going! Haha curious if it causes any issues or just compiles right up
[Eee Pad Transformer Android Development] josteink:
No issues with TWRP per se, but Im a bit busy getting the Noname 4.3 build-environment and things setup in a nice clean way so that it will be better to work with.

It seems so far CM10.2/4.3 requires a bit more patching outside the device-tree than CM10.1/4.2 did, so it requires to be done in a bit more structured manner if you dont want to go crazy ;)

Hopefully I should have a 2.6.0.0 build up in a day or two.
[Eee Pad Transformer Android Development] MassStash:
Ah, nice! Sorry, i don't flow the development over on there on that one haha. I beard all around it was a little more tricky than versions in the past. That's kool you're puttin a build together at all tho bro!

Next day or two!? that's amazing man, and most highly appreciated. Drop it, and we shall test! You ever decide to go official with your builds?
[Eee Pad Transformer Android Development] josteink:
Thats not my decision. That would be team win and so far they are not calling. I'm oh-so dissapointed, I tell you ;)
[Eee Pad Transformer Android Development] MassStash:
Ah, Wtf! Like not responding to you? What would be the proper channel to politely assist you in being heard?
[Eee Pad Transformer Android Development] josteink:
Dude. No big deal. And it's not like I've been pestering them either. Really :)
[Eee Pad Transformer Android Development] MassStash:
Haha fer sure fer sure. Just lookin to help peeps get recognized where recognition is deserved! And it's always nice to have a project go "official"
[Eee Pad Transformer Android Development] josteink:
First off: I'm getting a Nexus 7 (as outlined more thoroughly in my ROM threads)

That said: I'll try to get this one build through before I dump my TF101 development efforts completely.

Been meeting a bit more resitance than I expected, but I doubt it's THAT big a issue.

That said: Some completely untested TWRP 2.6.0.0 builds are now up on nexfiles.

Dont flash them unless you know how to revert to another recovery from a working ROM or via nvflash.

http://nexfiles.kjonigsen.net/tf101/twrp/
[Eee Pad Transformer Android Development] josteink:
No longer untested.

I've flashed it and it loads fine. Confirmed 2.6.0.0 and confirmed not bricking your device ;)