yashsingh1/xdaforums huggingface dataset:
[Barnes & Noble Nook Tablet] nandroid123:
latest snapshot for my B&N NOOK acclaim boot loops for me

latest snapshot for my B&N NOOK acclaim boot loops for me

This is what I tried the latest snapshot: cm-12.1-20151117-SNAPSHOT-YOG7DAO1K6-acclaim.zip

Constantly boot loops.

Had to revert back to this: cm-12.1-20151007-SNAPSHOT-YOG4PAO331-acclaim.zip

This is the gapps I'm using. Works fine with the 20151007 rom : open_gapps-arm-5.1-pico-20150923

What am I doing wrong ?

Any major changes in the recovery's ?

What is the recommended gapps ?

Had to revert back to this: cm-12.1-20151007-SNAPSHOT-YOG4PAO331-acclaim.zip

This is the gapps I'm using. Works fine with the 20151007 rom : open_gapps-arm-5.1-pico-20150923

Is there anyone using these old nooks anymore ?

Would it be possible for someone to post links to ROM's and GAPPS that are working on their 16gb B&N acclaim nook ?

That would be really appreciated. Then I can determine if it's my hardware or just my install.

thanks
[Barnes & Noble Nook Tablet] nmyshkin:
Tasker profiles not running?

I haven't seen any mention of Tasker (maybe I missed it) but I just can't seem to get it to run an App-triggered profile. I'm running 12.1-20151117 SNAPSHOT, just freshly flashed from a prior CM 10.2.1, so quite a change for me.

I've turned on the Tasker-JB setting in Accessibility. I'm using the same profile as on the earlier CM version to force landscape a local newspaper app that is locked in portrait (I use Rotation Locker as a Tasker plugin). In the notification bar I always see "no active profiles" for Tasker.

The Tasker developer has suggested a few options for Android 5.0+ (none of which have worked) including adding a line to the build.prop file and detecting the app via a change in the Window name rather than by its start.

I'm stuck. I can write a task (as opposed to the profile) which is able to manually rotate the page so it's not like the process doesn't work, but CM 12.1 seems to be ignoring or blocking Tasker profiles for me.

Edit: well, I have a kludge for at least one task--forcing landscape for some reluctant apps. Turns out running Rotation Locker in "Auto" mode as a persistent process does the trick. Who would have thought? As for the rest...meh
[Barnes & Noble Nook Tablet] nandroid123:
latest snapshot for my B&N NOOK acclaim boot loops for me

Well at least nmyshkin you have the latest snapshot working on your nook. Can you tell me if it is a 16gb nook ?

Also would you mind sharing the particular gapps that you have loaded ?

I have tried everything I can think of to get this latest running and cannot.

thanks
[Barnes & Noble Nook Tablet] nmyshkin:
If you run through this thread you'll see that it wasn't smooth sailing for me either :o

I have a 16 GB NT and--I don't know if this matters--it was repartitioned at my local B&N store right after I got it off of ebay and before I did my initial flash of CM 10.2.1 about a year ago. There seem to be a number of posts about the size of the GApps package w/CM 12 and maybe the stock partitioning is why. Just a guess. I ended up using the open gapps "nano" package and had no problems with that. I'm relieved to be missing a lot of nonsense I will never use.

If you're in a bootloop I don't know what to tell you that others have not already suggested. If it were me I'd flash back to my previous successful OS, and try the instructions in the thread I mentioned above. Read through the thread and you'll see some successful CM 12.1 file combinations others used. Just pretend you're a dufus like me and do it the lame way: prepare and SD card and pretend you're flashing from stock (and ignore the "unable to mount /bootdata" messages from TWRP!)
[Barnes & Noble Nook Tablet] chrmhoffmann:
There will be M nightly builds now.

Chris
[Barnes & Noble Nook Tablet] nmyshkin:
cLock widget, Lockscreen, Browser issues

Still in shakedown mode with cm-12.1-20151117-SNAPSHOT-YOG7DAO1K6-acclaim. Maybe these are known issues and/or maybe I've just missed something and someone can set me on the right track.

1. the cLock widget does not seem to update am/pm correctly. It gets stuck on one or the other. After fooling with this for awhile I finally stopped the app, cleared its data and cache and started over. Worked great (the time stamp even finally showed up in the weather--yay!) for 12 hours. "Solution": hide am/pm indicators.....

2. As with CM 10.2.1, the lockscreen just doesn't seem to self-activate very often. I have to manually invoke it with the power button. It does seem to be more consistent when the tablet is charging. Is there a setting somewhere or could an app running in the background be interfering with this?

3. As often as not when the stock browser is opened it throws out an error:

net:: ERR_NETWORK_CHANGED

Never got this before with the stock browser in CM 10.2.1. I researched it a little but most of the info is for Chrome running on PCs and seems to point fingers at connection settings/routers, etc. Refreshing the home page (Google) "solves" the problem, but is a nuisance.

Any help?
[Barnes & Noble Nook Tablet] champ1919:
Boots on the 8gig. Having a heck of a time getting gapps on it though. Error 70, unable to make a log and some other stuff. ... I'll keep trying to find a package. Maybe a bad download or something.

Auto rotate only likes landscape.. it will auto on lock screen, but, once unlocked, flips back to landscape.

Time to start a new thread? ;)
[Barnes & Noble Nook Tablet] chrmhoffmann:
Agreed. M thread started.

Chris
[Barnes & Noble Nook Tablet] nandroid123:
cm-12.1-20151117-SNAPSHOT-YOG7DAO1K6-acclaim NOT STABLE

I am having a heck of a time with cm-12.1-20151117-SNAPSHOT-YOG7DAO1K6-acclaim.

Most of the time is boot loops.

When I can get it to settle down I have the same errors and problems of the previous snapshot. ie black screen. shuts down in hibernation.

Lately the wifi on the nook will crash my wifi router requiring a reset ?!??! that was the last straw for me.

Not a stable release. Did anyone actually test this for a while before calling it stable ?

Anyway that is my conclusion until I hear from others that have it working properly.
[Barnes & Noble Nook Tablet] nmyshkin:
I more or less have it up and running the way I'd like (16 GB tablet, coming from CM 10.2.1) but it was scary at first, starting with huge app icons on the default LCD density setting and the near approach of a finger to the screen starting up 5 or more apps. Made setup a nightmare. I changed the LCD density, fooled with this and that over a few days, doing reboots, and gradually things calmed down. Icon size returned to normal so I could go back to the default LCD density, touch response became normal. Fewer black screens.

The tablet is now as user-friendly as it was running CM 10.2.1, except that Tasker is somewhat crippled. Some profiles will work but detection of app launch is not good. And the stock browser (which admittedly often closed unexpectedly in CM 10.2.1) has developed an extremely annoying network error on startup, which is too bad because I do favor the stock browsers. The "solution" is to install Chrome (which I don't much like). Here is additional evidence that bugs have a well-developed sense of irony. The error that the stock browser gives is ascribed to Chrome all over the internet while Chrome works just fine.

And....the $%#^& swipe lock screen is just as unreliable in this CM 12.1 build as it was in CM 10.2.1. Most of the time it never locks when the display turns off (unless it is charging). I can lock with the power button. The "feature" strikes me as pretty basic and I don't really understand why it seems to fall through the cracks, but I am mindful that even among the stock Nook Tablets there are odd variations. Mine, for example, will boot from an SD card

without

a power or USB connection. That being the case, perhaps the lock screen issue is actually a local problem and the developers tested their models and found everything to be just fine.
[Barnes & Noble Nook Tablet] nandroid123:
Thanks nmyshkin for the post. I am at my wits end with this snapshot (cm-12.1-20151117-SNAPSHOT-YOG7DAO1K6-acclaim). I also have a 16gb acclaim nook. I really hope the devs haven't tried to make some kind of compromise rom just to get the 8gb models to work with the same build. Much rather see two separate builds.

Anyway I've tried everything to my knowledge at this point. It all started with an auto update. The nook immediately started boot looping after that update completed.

Then I revert to this snapshot (cm-12.1-20151007-SNAPSHOT-YOG4PAO331-acclaim.zip) and everything is back to normal.

What changes were made on this current release that would be causing this ??

I can't think of anything that I am doing wrong. Checked and rechecked the sha1 checksums on the rom and the recovery and all seems

well with my downloads.

The only thing I can think of is the gapps.

Can you please let me know what gapps you are using and tell me where to find it ?

Thanks
[Barnes & Noble Nook Tablet] nmyshkin:
These are the GApps: open_gapps-arm-5.1-nano-20160109 found here.

It sounds to me like the variable is autoupdate. I'm sort of wary of losing that control so I've got mine turned off. I'd rather try to get the "word on the street" before forging ahead with an update that might have problems. So I'm always behind a little, but I can live with that. Although the flashing process is a little unsettling if you only do it once every year or so (like me) it does give you complete control (or as much as you can get).
[Barnes & Noble Nook Tablet] nandroid123:
open gapps

nmyshkin I am using open gapps. This one: open_gapps-arm-5.1-pico-20150923

Do you think that could be the problem ?

Should I try the nano version ?

thanks
[Barnes & Noble Nook Tablet] nmyshkin:
It might make a difference--or not. The pico package should be smaller but size is not everything :)
[Barnes & Noble Nook Tablet] nandroid123:
crashes before I can log in now

Ok I tried the open gapps nano. Now I can't even get through the registration procedure before it crashes and re-boots ???

Oh well I thought I would try.

And yes I did a clean install !!

update:

I went back and wiped everything again in the recovery.

Now I got through registration without a crash.

I will let you know what happens.

another Update:

Well it is running. Still seeing similar problems like the previous build.

Black screens. laggy and FREEZES when waking up from hibernation.

Takes forever for wifi to start etc. You know the normal stuff ?!?!

but it is running. I will see if it crashes my wifi router today. That I cannot tolerate.

Don't know if it is just my brand of router or not. TP-LINK

update

Ok this build still crashes my wireless router. EVERY TIME !

The previous snapshot which I am using on a regular basis never did this ?!?!?!

I think at this point that the DEV's let this one out of it's cage a little too soon.

Anyone else seeing this ??? This is a show stopper for me. I can't tolerate this wifi problem.

I sure hope this is fixed in the next build.

Needless to say I'm not going to mess with this one anymore ;-(
[Barnes & Noble Nook Tablet] Spearman873:
Hey guys, so I got the ROM working but its super laggy and unresponsive. My tablet even crashes sometimes.

So is there any fix?

Thanks!

I have the 8gb model
[Barnes & Noble Nook Tablet] digixmax:
Did you do "wipe /data & factory reset" before flashing ROM & GApps zip files?
[Barnes & Noble Nook Tablet] Spearman873:
I tried that a bunch of times. It's still really laggy
[Barnes & Noble Nook Tablet] nmyshkin:
I never saw any "me-too's" on this problem, but in case someone else comes along with it, I have a solution that worked for me. I can't take credit for it because I stumbled across it elsewhere.

The solution is to go to the Play Store and install Android System WebView. This is already part of the CM 12.1 package but apparently the update with the most recent market version dispatches the browser error on startup. At least it has worked for me. I'm so glad to be rid of Chrome which was laggy and buggy for me.

Now if only the lockscreen issue could be fixed as easily!
[Barnes & Noble Nook Tablet] nmyshkin:
Um....I don't see any for CM 12? Just for CM 13. Are we "done"?
[Barnes & Noble Nook Tablet] chrmhoffmann:
You should upgrade to cm 13. Older versions are no longer maintained.

Chris
[Barnes & Noble Nook Tablet] nmyshkin:
Just an update in case anyone drops by with this issue. The final solution for me was to disable the cLock widget and install Chronus Home and Lock widget. This functions seamlessly with CM 12.1, you can resize the clock digits somewhat so the widget doesn't occupy so much screen real estate, and the am/pm indicator works! Also, it turns out to have a bunch of weather options, including WeatherUnderground for which I had just gotten a personal API key for use with Kodi.

This does not solve the final issue: the screen not locking automatically on screen off, but it's one step closer to THE fix :)
[Barnes & Noble Nook Tablet] mikeataol:
delete

sorry, wrong thread
[Barnes & Noble Nook Tablet] jerrygarcia4295:
I tried SuperSU but it couldn't get root either ... I'll try changing the settings and see how it goes.
[Barnes & Noble Nook Tablet] jerrygarcia4295:
Well so much for that ... I did a complete factory reset then install from scratch ... turned on developer options, but every time I try to open it settings crashes.
[Barnes & Noble Nook Tablet] dbrickg:
Well, hah! As soon as I tried going to Developer options, I get an error saying "Settings has quit"... so that method is out. I guess I'll just go back to cm11 and wait for the SU problem to get sorted out.

---------- Post added at 02:10 PM ---------- Previous post was at 02:02 PM ----------

Yeah, sorry about that. I just tried myself, and yes, you can't get to Developer options, 'cause it crashes Settings. Grrr. Sort of a deal breaker for me. I'm back to cm11 till they work out the SU problem
[Barnes & Noble Nook Tablet] drmarble:
If you install cm-11.0 and enable root using setting/developer you can then flash cm-12.0 WITHOUT wiping and root will still be enabled. It is cm; you don't need to wipe when upgrading between versions or milestones. Only downgrading and nightlies can require wiping. If some apps act up just uninstall them and reinstall without restoring that apps settings. The basic cm install doesn't require a wipe.

I have looked at developer settings crashing. It is a problem with the backup password. I don't know why but that is what logcat says. The same error appears if you try to get to settings/backup.

Otherwise, it is a smooth working system.
[Barnes & Noble Nook Tablet] chrmhoffmann:
dev settings and setup wizard crash

Hi,

Both developer settings and the setup wizard (you see that only after wipe) were crashing...

This problem is fixed in the next nightly. If you need this urgently, update /system/etc/permissions/basic_hardware.xml from here: http://review.cyanogenmod.org/#/c/88226/

Chris

BTW: no need for supersu!
[Barnes & Noble Nook Tablet] jerrygarcia4295:
well I tried that too ... Titanium Backup for root will still not work ... can't get root.
[Barnes & Noble Nook Tablet] drmarble:
The patch to device_bn_acclaim works great. After rebuilding and flashing I can now get into developer settings. The kernel changes also work fine. All in all, this is an impressive bring-up for cm-12.0 on the acclaim. Thanks for you work.
[Barnes & Noble Nook Tablet] chrmhoffmann:
cm updater + cm recovery

Hi,

with the new recovery and the next nightly build, it should now work to download a nightly build with CM Updater (Settings->About tablet->CyanogenMod updates->Check for updates) and install it.

The fix is not great, but it should work until I figured out how this is supposed to work really.

Please flash the new recovery from here:

https://goo.im/devs/chrmhoffmann/cm-12.0/acclaim/recovery-L-acclaim-20150208.img

Chris
[Barnes & Noble Nook Tablet] dbrickg:
Yowza! SU is fixed. Developer options work. Everything seems to be working marvelously! Even Netflix works :)
[Barnes & Noble Nook Tablet] jerrygarcia4295:
I'm able to launch developer options now but I still can't get Titanium Backup to work ... says it can't get root access.
[Barnes & Noble Nook Tablet] chrmhoffmann:
Did you enable root for apps in the developer settings then?

Chris
[Barnes & Noble Nook Tablet] jerrygarcia4295:
Yes of course ... for apps and ADB
[Barnes & Noble Nook Tablet] rete:
I also experience inconsistent SU behavior.

Titanium Backup is fine, Root Explorer cannot achieve root access.

Apart from small niggles like this and the odd random hang or reboot, I'm amazed how polished this is. Big kudos to chrmhoffmann and all who's brought Acclaim this far. I don't think this old Nook Tablet has EVER run this well.
[Barnes & Noble Nook Tablet] jerrygarcia4295:
Interesting ... because mine on CM12 is very sluggish ... to the point of frustration ... I've tried every nightly so far but always go back to CM11. I've yet to get Titanium Backup to work ... I'd like to do a factory reset to see if that helps, but I want to be able to install my apps/data from backup. Any suggestions?

Update ... was was using an older version of Titanium because it was the paid version ... tried the newest download and it works as designed ... doing a factory wipe does in fact seem to improve the performance, so I'm assuming there is an app causing the sluggishness ... I'm going to install them one at a time and see what happens ... report back later.

Update 2 ... Facebook seems to be the culprit ... if I launch it everything runs doggedly slow ... if I force stop then everything becomes responsive again. Not sure if anything can or should be done, but FYI
[Barnes & Noble Nook Tablet] chrmhoffmann:
I see the same thing: Facebook app brings this tablet to the knees. Maybe running out of memory but I don't have time to figure out if this is somehow improvable.

Chris
[Barnes & Noble Nook Tablet] MrGHLover:
recovery trouble

i'm stuck on this recovery i can't install cm 11 or flash a different recovery please help
[Barnes & Noble Nook Tablet] jerrygarcia4295:
edit: oops ... that wasn't what you were asking ... you will pry have to use fast boot to flash another recovery

I'm using the latest TWRP as Alt Boot to flash these roms ... I keep the last version of CWM as the primary so I can just flash back to my CM11 backup when I want/need.
[Barnes & Noble Nook Tablet] rajsris:
I don't have facebook installed, but I have installed 50-60 apps, in addition to PA Micro GApps. The tablet is very sluggish, more so than in CM11.

EDIT: Is it possibly because of ART in Lollipop? I tried ART a couple of times on CM11 and each time, the tablet was way more sluggish than using Dalvik.
[Barnes & Noble Nook Tablet] jay_xander:
It may be sluggish due to the fact that you installed 50-60 apps. I just installed the nightly from the 12th, being the first try of CM12 on this device. In my experience, it is *slightly* more sluggish than the last milestone release of CM11. I have not many apps installed, and froze/deleted a ton more, and I'm extremely impressed with how polished this is.

Just so you know, I wiped everything (factory wipe, cache, dalvik), and from CWM 6.0.4.8 I flashed the nightly with the full sized GApps.
[Barnes & Noble Nook Tablet] MrGHLover:
i figured out the answer

i fixed it. what i did was flash the super su zip file in the recovery i had because i was also having trouble getting super suser access cause i have a apk that i use to flash recovery img files. :good::D
[Barnes & Noble Nook Tablet] Zippy Dufus:
Great work!!

@chrmhoffmann, excellent work!

Changed my cm11 build to cm12 and it built and booted first try! And it is working better this early after release than my NookHD++.

The tablet feels snappy and smooth and supports all my workflows.

Thank you!
[Barnes & Noble Nook Tablet] WnG88:
Updated tab using cmupdater to 12,and all working except Google play store. It says play services needs to update, but it doesn't, and there is no connection in play store. I have net access.

Update: Silly me forgot to update gapps..
[Barnes & Noble Nook Tablet] chrmhoffmann:
f2fs...

next nightlies will get f2fs support. You need to fastboot update your recovery (see below). Then adb into recovery and format the cache and userdata partition with mkfs.f2fs to convert to f2fs. Don't wipe first otherwise you can't adb into the recovery anymore. Doh.

BTW:

- I also plan to use emulated storage (which will require another wipe) soon.

- This means to then abandon the internal 1GB partition. Users can choose to repartition and join the two partitions. You will need a userdata partition only.

I.e. prepare to backup ALL YOUR STUFF!

Chris

Flash the recovery to use: http://goo.im/devs/chrmhoffmann/cm-12.0/acclaim/recovery-L-acclaim-20150216.2.img

Boot the recovery.

adb into the device

adb shell

~ # mkfs.f2fs /dev/block/platform/omap/omap_hsmmc.1/by-name/cache

F2FS-tools: mkfs.f2fs Ver: 1.4.0 (2014-10-18) [modified by Motorola to reserve space]

Info: sector size = 512

Info: total sectors = 872448 (in 512bytes)

Info: zone aligned segment0 blkaddr: 512

Info: format successful

~ # mkfs.f2fs /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata

F2FS-tools: mkfs.f2fs Ver: 1.4.0 (2014-10-18) [modified by Motorola to reserve space]

Info: sector size = 512

Info: total sectors = 25292760 (in 512bytes)

Info: zone aligned segment0 blkaddr: 512

Info: format successful
[Barnes & Noble Nook Tablet] rajsris:
Can u tell us the exact adb commands to perform this format? What are the benefits of f2fs?
[Barnes & Noble Nook Tablet] chrmhoffmann:
I added the adb commands to previous post.

Chris
[Barnes & Noble Nook Tablet] Demetris:
Finally Chris awesome news buddy.
[Barnes & Noble Nook Tablet] rajsris:
I am getting ADB unauthorized errors when I boot that recovery. HOw do I authroized my computer for ADB? When I type in adb devices, it does show the device, just says unauthorized next to it.
[Barnes & Noble Nook Tablet] belfastraven:
There should be a message on the nook when that happens which asks you if you want to authorize the computer. Can you see one? Once you authorize it won't ask you again for that same recovery and computer.

---------- Post added at 05:46 PM ---------- Previous post was at 05:39 PM ----------

thanks, I am running with data and cache f2fs now. I assume that you are not going to implement f2fs in system becuase it won't make much of a difference? just curious...

Also, would it be possible in the future for you to put some kind of identifier in the recovery title ( a number or date or something)? It is reassuring to know that I am running what I think I am :)

Thanks again for this great work!
[Barnes & Noble Nook Tablet] chrmhoffmann:
adb into recovery

Hi,

I added a recovery "eng" build that allows unauthorized adb access.

This will come in handy if you have not authorized within CM or you have wiped data.

Here we go:

http://goo.im/devs/chrmhoffmann/cm-12.0/acclaim/recovery-L-acclaim-20150217-ENG.img

md5sum: 11bcc6a2227e6311a7759e2a5c08f286

Chris
[Barnes & Noble Nook Tablet] Demetris:
wow! grats on the kernel, there is no need for an after market kernel i see.

Your missing a patch here and there imo.

I"ll patch you up on gerrit soon :)

Keep up the awesome work :)

And f2fs gave a lovely speed boost! recommended ;)

Cant wait for emulated sd to be done - finally! :D
[Barnes & Noble Nook Tablet] topdawg7793:
It works beautifully! Flashing CM12 with F2FS partitions as we speak. The excitement is killing me. F2FS should keep our dear acclaims somewhat relevant!
[Barnes & Noble Nook Tablet] chimpknowskungfu:
Works nicely. Browsing experience kind of sucks for me using anything other than the stock browser. Chrome/Firefox are not as smooth.

I'm glad that Youtube works at HD resolutions.
[Barnes & Noble Nook Tablet] rajsris:
What are the commands to get rid of the internal 1GB partition, so we can proactively do this before the emulated sdcard comes in?
[Barnes & Noble Nook Tablet] rajsris:
Wow, I am amazed at how this old tablet is flying with f2fs! All traces of CM12's sluggishness are gone, and its even better than any CM11 rom.

[MENTION=1149134]Demetris[/MENTION], any chance we get BexusL now? ?