Recent content by zarquon7

Will this guide also work on the Nook HD? (Using the equivalent Hummingbird files, of course).

For what it's worth, I went from v23 to v28 with no Google issues, but I imagine that experiences vary on a case by case basis. Probably wise to err on the side of caution...

I went ahead and tried it, and yes, 2.8.3 is fine. Don't know about the dirty flash, I did a clean install and formatted /data just in case. Everything seems to be working well so far.

Is TWRP 2.8.3 ok to flash #28? And would it be unwise to dirty flash from #23?

I've wondered about this as well; at first I thought it was because of root, but AFAIK, Google has been allowing playback on rooted devices for a long time now. I'm not sure if this worked or not on previous ROMs I've used, until the recent deal between Google Play and Disney, I had no video...

I never figured out what was happening here, but I turned off zip verification and flashed B4 anyway. All seems fine; perhaps the file wasn't actually signed? Another, probably trivial question: in the screenshots in the OP of this thread, the highlights in the settings app are red; mine are...

Checksum good, updated to TWRP 2.8.0.1; still fails zip signature verification.

Checksum is fine, still fails the zip signature. I'm using Geass' f2fs TWRP, is there a newer f2fs compatible version?

I tried to flash Beta 4 just now; it fails the zip signature verification. OK to turn that off in recovery? Or might I have a bad download?

I've been trying to flash this, but I keep getting "zip signature verification failed". Tried the regular and linaro versions, and re-downloaded them in case I had a corrupted file; still get the error...

I did not know that (the part I bolded); does that mean I can skip the part about about installing an F2FS kernel afterwards, and just install it along with the ROM as usual?

Best recovery/kernel for F2FS? I've been happily using this ROM for some time now, my TF300 has never worked better! Now I'd like to try converting to F2FS. The most concise instructions I've found are back in the 2nd post in the Geass kernel thread; does all that still apply, or is there more...

I'm using _that's (v9 I believe); I should also point out that, despite the thread we're in, I'm not currently running CROMi-X, this is just the only place I saw that particular graphic glitch mentioned. I was running it, but I flashed CROMBi-KK a few days ago. I don't think I noticed that...

I don't see an option in Trickster to set the GPU clock speed...

In my case it doesn't really happen often enough to bother me; should I be concerned that it might be damaging the device?