yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] zachf714:
The md5 file isn't there but it doesn't need to be :)

Sent from my Nexus 7 using Xparent ICS Tapatalk 2
[Nexus 7 Original Development] deltantor:
TWRP works perfectly with the built in cm updater for me on my (unencrypted) device.
[Nexus 7 Original Development] Zotak:
Looks like the official 01/01 build is out.

http://10.1.cmxlog.com/?device=grouper

http://get.cm/?device=grouper
[Nexus 7 Original Development] landstander:
Cool! :) Then once the encryption bug is fixed, I should be good to go (not that it's difficult to work around as-is).
[Nexus 7 Original Development] TheDarkDefender:
Sorry, but can anyone explain clearly what an unencrypted/encrypted device means ? Is it related with settings-> security -> encryption of tablet ?
[Nexus 7 Original Development] deltantor:
When you encrypt your android device (through the menu you mentioned) you supply a pin or password that is required when you power on the device. Without that password, the device will not power on. Why use this instead of just a normal screen lock? The storage on unencrypted devices is readily accessible to somebody with physical access and the right knowledge/hardware/will. The storage on an encrypted device is not accessible without the decryption key, which is your password/pin, it just looks like gibberish. When you power on an encrypted device and supply the key, it decrypts it on the fly, making it accessible to you. Even if I were to steal your device, remove the sd card or internal memory and try to access it, I would not be able to open your files, or even see what files are there.

Disclaimer: I haven't used the encryption on android before, and this is just general knowledge regarding encryption, but it should apply in general. I do not know what side effects it has on normal use and if there is any (seriously noticeable) slowdown. You would have to get an answer from someone else on that.
[Nexus 7 Original Development] ptesmoke:
Wow... now that's interesting!
[Nexus 7 Original Development] themacroe:
Why isn't there a md5 sum if its displayed on get.cm ?

And what happened to the progress bar and android animation that looks like a native ota?

Sent from my Nexus 7
[Nexus 7 Original Development] tiagovale2:
Just flashed latest nightly and I'm stuck bootlooping... Flashed with TWRP btw. Trying go get back stock image and reflash this nightly. Hopefully was some mistake I did.
[Nexus 7 Original Development] crshbndct:
Yep. Same problem for me.

I might try to go back a couple of nightlies and try that.
[Nexus 7 Original Development] tiagovale2:
Already flashed stock... Flashed CWM too since I've been using that recovery since some time ago, instead or TWRP. Will try again last nightly.
[Nexus 7 Original Development] keyra74:
flashed latest official from 01/01 and no bootloop or else
[Nexus 7 Original Development] gusto5:
Ditto! Chronus looks awesome!
[Nexus 7 Original Development] imheroldman:
They got rid of ROM manager because they built their own updater. It had nothing to do with the recovery. If you look at their wiki and some of the cm op's, like for d2tmo maintained by cyanogen himself, they expressly say cwm is the only supported recovery. Even though others may work if you have bugs your first step will be to try with cwm

I have nothing against TWRP I'm just saying if there are issues it is not supported as a recovery
[Nexus 7 Original Development] tiagovale2:
Done, booted quite fast this time with CWM (not sure if related).
[Nexus 7 Original Development] scandalousk:
Hmm chronus doesn't seem to be working for me. Enabled everything, but it doesn't show on the lock screen....

Re–flashed and cleared all caches, but that didn't solve it. Tried switching back to swipe lock screen instead of pin and changed back to the default launcher, but that didn't fix it either. Anybody knows what might be going on? On default cm, no custom kernel..
[Nexus 7 Original Development] di3cbl:
You have to add it urself the default one isn't chronus
[Nexus 7 Original Development] shaggyskunk:
Don't know why any of you are having a problem flashing with TWRP - it works BRILLIANTLY for every single rom!!

Check to see if you have the latest version of TWRP for your device.
[Nexus 7 Original Development] scandalousk:
Doh! Thanks mate that was it. I don't function well during morning hours:p
[Nexus 7 Original Development] adstraylight:
Jenkins is doing its thing once more...long live Jenkins!

EDIT: Sorry - old news...;)
[Nexus 7 Original Development] xI mEzMeRiZe Ix:
It's due to the fact that CWM is more mature and on waaaaaaay more devices. For a Nexus device, TWRP is fantastic.

Sent from my Nexus 7
[Nexus 7 Original Development] p1tst0p:
Hey

I'm currently running the 20121227 nightly, where is then auto updater for CM that I see being mentioned, should my n7, have updated automatically?

Cheers
[Nexus 7 Original Development] shaggyskunk:
Uhm, go to settings - about tablet - Cyanogenmod Updates - select which you want - hit refresh - oh, and read a bit more, ok, A lot more ;)
[Nexus 7 Original Development] DemosZevasa:
Nightly build broken today on Jenkins...

BTW: with cm updater do I have to reflash gapps?

Edit: [/home/jenkins/android/workspace/android/jellybean/out/host/linux-x86/obj/EXECUTABLES/tblgen_intermediates/tblgen] Error 1

Dunno what it means, but its the same error as before...
[Nexus 7 Original Development] shaggyskunk:
No, you don't need to flash gapps.
[Nexus 7 Original Development] d.kozzer:
I'd like to know this as well - it definitely says that you can set it up to flash another zip (eg a kernel), and I know gapps are apps, but if they're /system apps, I would think a gapps re-flash would be needed.

e: nm, shaggyskunk answered the question
[Nexus 7 Original Development] zachf714:
The problem is koush never updates it. Its still not updated to support 4.2

Sent from my Nexus 7 using Xparent ICS Tapatalk 2
[Nexus 7 Original Development] shaggyskunk:
For what it's worth - koush did update rom manager to support 4.x, but unless there's been some pretty substantial changes, I doubt that it will regain it's popularity.

You're almost certainly better off choosing and flashing your own roms, kernels, etc (with the exception of cm updater, if you're currently on cm) with TWRP or Skaters CWM.
[Nexus 7 Original Development] tiny4579:
That's false. Cwm is on 6.0.2.3. And they addressed the /0 folder issue.

I am a twrp user though.
[Nexus 7 Original Development] zachf714:
Well..... That's not what i read on tf101 forums a week ago ... There are issues fixed in twrp to that's cwm has not fixed

Sent from my Nexus 7 using Xparent ICS Tapatalk 2
[Nexus 7 Original Development] gianptune:
Those of you using TWPR, have you ever browsed their git and read the code? It looks like it was written by somebody that is still learning or doesn't have much experience with c/c++. I can appreciate the fact that they are learning, and they are willing to share their work with the world. But recovery is something that should always work. It is your failsafe to keep your $200 toy from turning into a brick. It isn't something you want written by somebody who is still learning how to code.
[Nexus 7 Original Development] shaggyskunk:
Three different devices, countless different roms, kernels etc, and never had a failure using TWRP, and that's just me - Can you point to a single failure using TWRP, that was not user error? If you can, then I'm pretty sure that a similar failure can also be found with CWM.
[Nexus 7 Original Development] keyra74:
nope 6.0.2.7 on my nexus 7 :)
[Nexus 7 Original Development] TheDarkDefender:
+1
[Nexus 7 Original Development] gianptune:
@shaggyskunk

But you still haven't read the source code for it have you? I don't think you'll find anybody that understands c/c++ well that will read the code and say it is great. It compiles, and it seems to work. But it is not the quality of code I would trust a device that costs hundreds of dollars to.
[Nexus 7 Original Development] adstraylight:
There's another thing that should be bourne in mind, the bootloader. I found that I was getting extremely long reboot from recovery times, to the point that I thought I was caught in a bootloop with the older 3.41 Bootloader, this was solved by updating to the most recent version, 4.13. This issue came up in the M-kernel thread btw.

To obtain the bootloader img file, download the latest factory image, unpack with 7-zip (you'll need to upack the archive within the archive btw), then flash with either fastboot or via a toolkit such as Wugg's.
[Nexus 7 Original Development] landstander:
Code quality notwithstanding, until CWM supports encrypted /data (which I don't expect to see anytime soon) it's entirely useless for my purposes. TWRP, on the other hand, has the significant advantage of actually working.
[Nexus 7 Original Development] tiny4579:
Issues fixed in TWRP that are not fixed in CWM? How vague.

Well, it looks like CWM is quite active:

https://github.com/CyanogenMod/android_bootable_recovery/commits/cm-10.1

I'm just saying they're still actively working on recovery.
[Nexus 7 Original Development] JeremyNT:
It can't damage the device. Worst case is you fire up fastboot.

And is cwmr even fully open source? Last time I looked he was selling some kind of upsell version with touch support (which is a basic feature in twrp).
[Nexus 7 Original Development] bigbiff:
Hi, I was hoping you could delineate the issues you see with code style so that we can learn from your experience.

Thanks for your help.
[Nexus 7 Original Development] Dees_Troy:
At this point both CWM and TWRP boil down to some kind of GUI that drives some basic command line utilities such as tar and dd for backup and use primarily AOSP code for installing zips. The hard part is coming up with the correct commands for wiping and backup/restore. It's hardly rocket science. Neither should scare you. Writing code is an art, not a science. Maybe I don't follow all the standard naming conventions or use all of the preferred methods for C/C++ but that doesn't make it poor code and we're continually improving our code base.

Personally the only thing that scares me about recovery are the builds of CWM that random people build using koush's web-based recovery builder. You have people that know nothing about compiling, source code, or recovery using it and sometimes the results can be pretty non-functional.

TWRP is fully open source, so if there's something that you don't like you can download the source, change it, and submit your changes upstream. TWRP is technically not supported by the CM team, but that doesn't make it a bad recovery and if you need recovery-related support then you can certainly come to us. Thanks to landstander I actually have a Nexus 7 in my hand that I can use as a testbed to troubleshoot issues.

Now, I have no idea why this thread turned into a discussion of what recovery is better when the discussion in this thread should be focused on CM10.1. I would suggest that people get back to discussing the ROM and not the various recoveries that are available.
[Nexus 7 Original Development] bass0324:
Is anyone else having issues on the recent builds with terminal emulator force closing all the time?
[Nexus 7 Original Development] mskpop:
Anyone else getting force closed when trying to download files through browsers?
[Nexus 7 Original Development] aggrophobik:
Yes. I just deleted the .apk and re installed from Play Store.
[Nexus 7 Original Development] bass0324:
Sweet, at least I know its not just me. Did the same and it works now, thanks!
[Nexus 7 Original Development] thracemerin:
There's a patch to fix it submitted to gerrit, something about the shared library being bad, should be merged in a day or so.
[Nexus 7 Original Development] aggrophobik:
Oh nice, thanks for the info.
[Nexus 7 Original Development] hazwheel:
The OP says DO use twrp
[Nexus 7 Original Development] adstraylight:
I think the fact that there's little discussion about the ROM, must be a tacit thumbs up for CM10.1. ;)

What I'd like to see is the frameworkres.apk reworked so that the old gradient fix zips work again. Apparently it's just a matter of removing two xml files and restoring the original png files. I've gotten used to having a solid black settings screen.
[Nexus 7 Original Development] tdizzle404:
+1 I know it has been disputed ,but I get countless bugs with cwm recovery I've always downloaded the updates to check them out, but I always go back to twrp because I get bugs with cwm that no one else can duplicate.
[Nexus 7 Original Development] mskpop:
Does anyone else have trouble downloading files from the browser app?
[Nexus 7 Original Development] TheAtheistReverend:
No problems here.
[Nexus 7 Original Development] drakenabarion:
All this talk about different recovery systems somewhat has confused my as a new user (so new, the N7 hasn't quite arrived just yet - hopefully tomorrow!!! :D). I already have all the relevant files downloaded and ready for installation, so right now I have just two concerns. :)

1) Are both TWRP and CWM compatible with the new 4.2.1 layout from the official update? I read some people saying that CWM isnt and TWRP is, but others saying both are.

Well, I've had years of experience with CWM on my i9000 and it wouldnt be like CWM if it wasnt updated to completely support a new layout within a few days of a new layout's release. I assume the same is true on the N7. As for a choice between different recovery systems, I may just try both. I would imagine that in the end, they are different paths to the same functionality.

2) I also read in a few places (not just this thread, I did a small search online) that boot time would be much much slower if CM10.1 is installed on a N7 with the 4.1 bootloaders. So in that case I guess I want to doubly confirm that both recovery systems can handle the 4.2.1 system layouts - which I think they do and everything will be fine. :)
[Nexus 7 Original Development] shaggyskunk:
TWRP kicks butt - Fast, Reliable, Great UI, Current. Haven't had a single issue, on my devices, (skyrocket, n7 & n2) multiple Android versions, multiple roms. ;)
[Nexus 7 Original Development] :
TWRP is my first choice! I can't agree more! Running it on my n10, n7, n4, galaxy nexus and n1 without any problems or concerns.

Gesendet von meinem Nexus 10 mit Tapatalk 2
[Nexus 7 Original Development] omgmrj:
Tablet UI?

I'm still on the 12/15/12 10.0 nightly. From searching this thread, it's my understanding that there's still no Tablet UI, correct? Does anyone know if there are plans to add this to 10.1 and beyond, or does the newly-separated settings and notification shades complicate this matter too much?

I know there are other CM10.1-based ROMs such as SmoothROM that have kept tablet UI, but I'm looking to stay with the official CM.
[Nexus 7 Original Development] adstraylight:
If your N7 comes with 4.2 pre installed, then you will already have the latest bootloader, even so CM10.1 will boot from older versions, it just might take a while to reboot from recovery.
[Nexus 7 Original Development] KaZo58:
flashed latest twrp with toolkit first time on stock 1 month ago. i did no update but yesterday i found out, twrp was removed or something else happened.. so i asked on official irc chan they told me, cm recommends officialy cwm. i flashed it last night + cm10.1 1.1.13 nightly first time on my n7. it works fine yet. so the recovery war should be stopped ^^

isn't there a separated discussion thread for this rom?

Gesendet von meinem Nexus 7
[Nexus 7 Original Development] agentfazexx:
Trying to use the Chronus clock on the 1/1 build, doesn't seem to be showing up. Neither is weather. Am I doing something wrong? I'm using a 5x5 pattern lock if that matters.
[Nexus 7 Original Development] shaggyskunk:
What "war", people are free to use whichever they want ;)

What do you mean, TWRP was removed?
[Nexus 7 Original Development] scandalousk:
I asked the same question a few pages ago. You have to add them by adding a new widget to the lock screen and select chronus.
[Nexus 7 Original Development] taylor.fowler:
And enable calendar and weather in settings> system> lockscreen widget(or something like that)

It's not a very intuitive spot....
[Nexus 7 Original Development] agentfazexx:
Yeah I got it. Not a good spot indeed. lol
[Nexus 7 Original Development] drakenabarion:
I don't quite have the device yet but, I am going to jump in here and make a guess that "/System/recovery-from-boot.p" still exists/existed and therefore rewrote the bootloader and recovery upon the next reboot. (Of course it could have been another reason, this is just a guess).
[Nexus 7 Original Development] shaggyskunk:
And remember to swipe up the other clock, that way only Chronus is there ;)
[Nexus 7 Original Development] AndIKnow:
My N7 keeps freezing every once in a while and the only way to fix it is with a hard reboot. Anyone else having the same problem? I had it on the 31st nightly so I updated to the 1st and it just happened again. Suggestions?

Sent from my Galaxy Nexus
[Nexus 7 Original Development] xavier86:
I ran into this today also. I'm still looking into it. But you really can't expect stability with a nightly ..
[Nexus 7 Original Development] scidon37:
If you know how to fix it, why don't you submit a fix to gerrit?

It has been said many times in this thread that there are no plans to include tablet ui. The point of CM is to keep the interface as close to AOSP as possible. It's like saying that you want vanilla cake, but only if it's chocolate.

It's there because it's not only a lockscreen, but also a home screen widget.

Sent from my Nexus 7
[Nexus 7 Original Development] cub0ne:
ineed to make a back up of my apps using titanium back up. need to perform factory reset before flashing the update. got like 18gig games and apps. too lazy to redownload everything lol. hopefully this update is not that buggy.
[Nexus 7 Original Development] scidon37:
Is this a statement or a question?

Sent from my Nexus 7
[Nexus 7 Original Development] zachf714:
I know for some devices it is still being actively worked on but devices like the tf101 the reboot back to recovery bug that locks you into recovery until you run fast boot commands to kick it out. Twrp fixed that

Sent from my Nexus 7 using Xparent ICS Tapatalk 2
[Nexus 7 Original Development] AndIKnow:
Happens a lot actually.. Never been like this on previous CM versions. Maybe I'm just paranoid but it is annoying sometimes. Just gonna have to wait I guess.

Random reboots and freezes I mean ;)
[Nexus 7 Original Development] manekineko:
That's hardly an apt analogy.

CM changes plenty of things on the interface, like the status bar customizations, or the notification drawer power widget. It's more like saying you want vanilla cake, with chocolate sprinkles.
[Nexus 7 Original Development] buffal0b1ll:
+1
[Nexus 7 Original Development] scidon37:
You're right, I probably went too far with that analogy. But it has been discussed in great length that there will be no tablet ui. If you want it, you'll have to go to another ROM, or build your own.

Sent from my Nexus 7
[Nexus 7 Original Development] chronoquestion:
Is anybody else having issues getting movies from the store to playback in HD? Both my Nexus 7 and Galaxy Nexus have this problem while running CM 10.1 while my Nexus 10 does not have this issue and plays movies in HD just fine.
[Nexus 7 Original Development] Lillz:
seems to work right, but now I have no quicks settings. Try to pull down to the right, nothing. Went into system settings < quick settings and theres no option to enable it.
[Nexus 7 Original Development] manekineko:
You flash gapps? The quick settings are part of that oddly enough.
[Nexus 7 Original Development] themacroe:
I have been getting a black screen of death my music may still be playing but the screen will not turn back on unless I hold the power button until it resets

Sent from my Nexus 7
[Nexus 7 Original Development] krazyflipj:
That's with stock kernel? Any changes in clock speeds?
[Nexus 7 Original Development] themacroe:
Yes with the kernel that's included with cm I have not modified anything

Sent from my Nexus 7

---------- Post added at 01:05 AM ---------- Previous post was at 12:35 AM ----------

Browsing Facebook and my device just shut off it scared me and I thought that it would not turn back on

Official cm 10.1 from get.cm 2013 build help please

Sent from my Nexus 7
[Nexus 7 Original Development] AndIKnow:
My apps keep freezing and the screen becomes unresponsive. The only way out of it is a hard reboot. No idea what's causing it though. I thought it was because I was using it too much.

2013 build here as well.

Sent from my Galaxy Nexus
[Nexus 7 Original Development] marvi0:
Hmm so it appeares quiet a couple of people have been having lock ups and random reboots, even after hard resetting or wiping, any ideas or advice on how to solve this before I flash please.?
[Nexus 7 Original Development] shaggyskunk:
I was running 2013/01/01 Without any problems. If you are having trouble, boot into recovery, fix permissions - If you are still having issues, factory reset, wipe system, cache and dalvik - flash rom and gapps.

There's nothing wrong with the build. ;)

FYI, the 01/03 build on getcm is up.
[Nexus 7 Original Development] cammel:
Sorry about this question, but I'm new to the N7, just bought it.

What are the most important bugs about cm 10.1 right now? I'm trying to figure out if I should use my n7 on stock 4.2.1 or to use cm10.1

Thanks a lot in advance! (and please don't flame me!) :D:D

Enviado desde mi GT-I9300 usando Tapatalk 2
[Nexus 7 Original Development] shaggyskunk:
There, consider yourself flamed ;)

I personally don't think that there's anything of consequence, certainly nothing to worry about ;)
[Nexus 7 Original Development] scidon37:
Read the last few pages, there are bug reports.

Backup stock, flash cm, if there are bugs that you can't live with restore your backup and wait for them to be fixed.

Sent from my Nexus 4
[Nexus 7 Original Development] TheAtheistReverend:
I agree with the above post, but I have had no problems whatsoever running the January 1st build. None.

Always have a backup. Always.
[Nexus 7 Original Development] markzero:
sleep tile killed my grouper?

what I have:

12/27 nightly, "grouper" 32gb, no kernel change or anything, and started with almost a full charge

Had been working fine for several days, including sleep (momentary push of power button) and hard power off.

what I did:

Added the sleep tile under quick settings.

Later, used it.

what I got:

Device no longer responds -- holding down power for 10 seconds, 30 seconds, and over a minute doesn't force reboot, with or without charger plugged in.

what I've also tried:

Holding down power+volume up for a minute, nothing, regardless of whether plugged in.

Holding power+volume down, same.

Holding power+both volume buttons, same.

searched thread before posting using:

sleep, reboot -- nobody else seems to have had this problem

Anything else I should try before I think about either popping the back to try to disconnect/reconnect the battery?

edit: also, per advice on the Asus website, tried leaving it alone on the charger for (ok, maybe less than) an hour.

edit #2: popped the back, pulled battery cable, reconnected, closed it up. Still won't come up at all, whether hitting power momentarily, holding it for 30 seconds, or trying both power and volume up. Is it toast?

edit #3: may be coincidental; someone else says sleep tile works fine on their device.
[Nexus 7 Original Development] corumuk:
Tough break, hope you get it fixed.

Does your computer detect the device when connected?

You could try using wug's toolkit to flash back to stock...

http://xdaforums.com/showthread.php?t=1766475
[Nexus 7 Original Development] markzero:
Thanks, I'll try the toolkit when I'm back at home on my Windows box. (Loved that toolkit, btw; it's how I rooted it the first time.)