yashsingh1/xdaforums huggingface dataset:
[Nook Touch Android Development] dombeef:
Currently running the new build *fingers crossed for no more burn in ;)* And will report on any more burn in(most likely not due to the screen blacking out and finally shutting down XD)

Good news: the burn in is basically fully gone, I can only barely see it on any refreshes on full white backgrounds, but that should probably disapear soon.

Bad glitch, when I try to go into twrp(by holding down the two bottom buttons), it doesnt, but it boots normally, except the screen doesnt function at all. A reboot fixes it, but I still cant go into twrp, maybe I am just doing it wrong?
[Nook Touch Android Development] kfazz:
did you update the uImage-recovery and ramdisk-recovery.ub files on the sd?

you're probably in recovery with the screen uninitialized. new version should fix it.

edit: try this: replace uImage-recovery with uImage from the rom.

i've been testing it, and it hasn't failed to boot properly yet.

i've updated the recovery files in the build download folder.
[Nook Touch Android Development] :
I can attest that these new ones work properly.
[Nook Touch Android Development] nmyshkin:
I've been following this thread closely but not in detail because it seems technically beyond me so far. I've rooted and modified my NST a lot and done a CM 10.2 install on my NT, but the instructions presented for this change are not quite at the level where I would feel comfortable trying this on my NST.

My question for now is: what does this get us, potentially? Even after all the modifications I've made to my NST what I really use it for is to read books. Oh, I can receive and send e-mail in a pinch, and I can (sort of) surf the web, or at least do a quick look-up of something. But for me, beyond the obvious limitations of no sound or true video, the real problem with the NST running Android 2.1 is the inability to scroll in just about any app but Opera Mobile. For example, the BBC News app and GenieWidget are nice adjuncts but you have to fight with the screen and most of the time you can't really read the entire thing because you just can't get to the "bottom" of the "page". Even FastMode or NoRefresh don't help this issue.

Does this modification help in this regard, and is it non-destructive--that is, can I just pull out the card and have things go back to the way they were? That's what's really not clear to me. From what I've read I think the answer is "no".
[Nook Touch Android Development] Deafcyclist:
I am very interested in CM11 for the NST and am actually planning on getting a NST very soon (within the next few days). I suspect that one of the main benefit of being able to run CM11 would be compatibility with many apps that require Android 4.0 or newer. And continued support for Google Play Store. It's my hope to be able to use CM11 to sync my google calendar/contact/etc... more easily than the stock ROM.
[Nook Touch Android Development] :
NoRefresh and FastMode haven't been gotten to work yet, but I'm sure they will in the [near] future. And yes, basically here's what happens:

- First, you boot from the sdcard into TWRP and flash the provided zip.

- Now, you have an sdcard that has CM11 on it which you can use any time by turning off your Nook, putting in the sdcard, and booting up. To get back to your normal ROM, just turn off your Nook from CM11, take out the sdcard, and boot back up. This can be repeated an infinite amount of times without damage.

---------- Post added at 16:21 ---------- Previous post was at 16:18 ----------

Unless you're an experienced dev, I wouldn't recommend flashing this CM11 ROM until a somewhat stable version is released (it's in its pre-alpha stage right now).
[Nook Touch Android Development] Deafcyclist:
Yeah, I am aware of that. I'm just really glad of the potential for CM11 on the NST for the reasons I mentioned above. I plan to just use stock for now until I gets more comfortable with the general flashing and rooting process on the device then and only then would I even consider trying the CM11. Likely by then, some of the issues and difficulties may be fixed.

In any case, I am willing to try being a tester and share logs and whatnot if needed when the development come to that stage.
[Nook Touch Android Development] kfazz:
i think it's safe to say we all use our nooks at least for reading books :)

my goals in producing this were to enable me to continue using the nook to read books, but also for manga, news websites, and xda.

scrolling does work, basically, but it's ghosty. A2 mode during scrolling would help a lot.
[Nook Touch Android Development] :
Amen to that. Is it looking like we may get it working soon?
[Nook Touch Android Development] :
Didn't fully realize it before, but this happens to me, too.

Can you post me the .apk for Apex, please? (/data/app)

ADB over USB also works great.

Sure. Can you wait a couple hours? I'll post again with extensive instructions then.

I bet it is. Let me test it.

That would be awesome! How 'bout it, [MENTION=2685019]kfazz[/MENTION]?
[Nook Touch Android Development] :
[MENTION=2685019]kfazz[/MENTION], I got Busybox working great on the newest build. Might want to consider including it in the next update.

[MENTION=4399146]aiamuzz[/MENTION], stock NST keyboard on CM11 doesn't look too good right now. When it installs, it replaces the CM11 stock keyboard, and then doesn't appear in [Settings > Language & input], even after reboot. :(

UPDATE - just got the softkey-changing app SoftKeyZ working nicely.
[Nook Touch Android Development] aiamuzz:
Oh !

No nook stock keyboard !!!

Can anybody get it to run ?
[MENTION=4474482]Renate NST[/MENTION] ?

[MENTION=5981373]ИΘΘK¡€[/MENTION] ... isn't Softkeyz a paid app ?

Is there any way i can switch softkeys off to gain more screen real estate(of course after configuring the hard keys for Home, Menu and RecentApps(long press may be ?))

about the apex launcher apk, its easy to download through playstore, just install this chrome extension and you are good to go ...

APK Downloader extension for Chrome and Firefox right from under google's nose !!! you'll get a download apk button besides the install button on play.google.com !!!

[MENTION=2685019]kfazz[/MENTION] ...

this build is whirring almost like a daily ROM, when it comes to crashing ?

i've hardly come across a crash, except once.

Sleep wake working like a charm. no hiccups besides the overall slowness!!!

otherwise i am happy to see so many elusive apps which were never meant for Android 2.1 actually find them running out of my SD card a.ka. [MENTION=2685019]kfazz[/MENTION] 's CM11 !!!

attaching a few app screenshots.
[Nook Touch Android Development] dombeef:
New update: no screen burn in anymore : D

Other new update while trying the new rom: the usb host just randomly turned on, and when I tried to charge the nook, caused my computer to kernel panic twice. I would sideload the old program used back in 2.1 for usb host, but I cant neither get access via adb over wifi or usb...

kfazz, any idea why this would happen with the new kernel? Any logs you want me to save that may help?
[Nook Touch Android Development] :
Yes, SoftKeyZ is a paid app, but the creator has been kind enough to provide the full version for free for the XDA community. :)

[MENTION=4399146]aiamuzz[/MENTION], to disable the soft keys, just add this line to the bottom of your /system/build.prop file:

qemu.hw.mainkeys=1

...and then reboot. (Thanks, [MENTION=4437780]dorfd1[/MENTION]!)
[Nook Touch Android Development] dorfd1:
I just tried the rom. so far it works fine but when I tried pico gapps, setup wizard kept crashing. also reboot recovery does not reboot back into twrp.

I don't know if this is appropriate to say this in this thread. CM11 on the nook is awesome but given the device's 256mb of ram, I think CM7 might work better. Either way it is cool to see more development on this device.
[Nook Touch Android Development] aiamuzz:
i would appreciate your help.

& i am waiting for your instructions on making the soft keys and notification transparent including the mapping the button keys.

---------- Post added at 05:45 AM -----UPDATE----- Previous post was at 05:32 AM ----------

[MENTION=2685019]kfazz[/MENTION] ... i loaded the SD card and connect the charger, the device booted into your ROM and it went into suspend,

i woke it be pressing the nook button and entered my pin and the device was accessible, left it for a while and it went back to sleep after 30 sec. The above issue you've mentioned, does it refer to some other thing then what i have just experienced ?

[MENTION=2685019]kfazz[/MENTION] ... & [MENTION=5981373]ИΘΘK¡€[/MENTION] ... is it possible to replace the black screen after sleep/suspend to replace it with an image, as in a folder where we can dump our screen savers and the sleep/suspend screen picks up one at random ? The EnergySistem Ereader Pro had this option, a screensaver folder where i had dumped images for use, and it worked. Like i said, i have its nandroid backup should you need to dig into it ... especially [MENTION=5981373]ИΘΘK¡€[/MENTION] ... as you seem to have enough experience to look under the hood for tweaks !!! Let me know if you want me to upload the EnergySistem Ereader Pro's nandroid backup ... its about 1.3 GB(kernel, recovery, system, etc ... complete CWM nandroid)

---------- Post added at 06:45 AM -----UPDATE----- Previous post was at 05:46 AM ----------

[MENTION=2685019]kfazz[/MENTION] ... i think after the above, my device ins't charging on this ROM ... hey i now realize ... yesterday when i was ADB'ing apps into my device on USB and installing/trying them out ... the data cable was connected to my device all along and the battery percentage was actually dropping 54, 53, 52 ... 51 % ... i ignored it thinking it must be bcos i was doing all the fidgeting and all that activity was discharging faster than it was charging ... but turns out i was wrong, as its more than an hour now that my device is connected for charging and it really hasn't made progress ... a bug or something ?
[Nook Touch Android Development] dorfd1:
if you want to disable softkeys. set qemu.hw.mainkeys=1 in build prop. and if you want phone ui instead of the 7 inch ui. run wm size 599x800 as root in a terminal and then reboot.
[Nook Touch Android Development] :
That's what I thought, but it doesn't permanently disable them.

UPDATE - I got Apex Launcher working nicely. I also finally got Reverse Portrait and Reverse Landscape mode working with the app Ultimate Rotation Control.
[Nook Touch Android Development] dorfd1:
Modify build.prop and add qemu.hw.mainkeys=0.
[Nook Touch Android Development] :
Wait, so which one disables them - qemu.hw.mainkeys=0 or qemu.hw.mainkeys=1?
[Nook Touch Android Development] dorfd1:
Sorry it is =1 not =0.
[Nook Touch Android Development] kfazz:
i don't have time for a lengthy post, but i'm been hacking on the kernel a bit.

i've pulled a few patches from encore branch that help a bit.

i also have a test build running with IMG DDK 1.12 pulled from moto360.

fixed area update in surface flinger. (forgot to add top and bottom to width and height to get rectangle end coords.)

and i have a crazy idea for compressing apks at install time, the same way the rom is compressed, but not sure if it's feasible.
[Nook Touch Android Development] :
[MENTION=2685019]kfazz[/MENTION], would you consider using the files I posted here in the next build?
[Nook Touch Android Development] aiamuzz:
thanks [MENTION=4437780]dorfd1[/MENTION] ... i tried the 'wm size 599x800' command and my tablet UI changed to a phone UI ... however when tried enabling the AutoHidingSoftKeys app & it reverted to the tablet UI ... Haven't tried to disable the softkeys yet as i am waiting for [MENTION=5981373]ИΘΘK¡€[/MENTION] 's instructions to setup my hardware buttons to replace the softkeys.

[MENTION=5981373]ИΘΘK¡€[/MENTION] ... Still waiting for your instructions to setup my hardware keys, for now using the AutoHideSoftKeys app ... its pretty nifty with the autohide and transparent features (but at the cost of the service it must be running in the background).

just finished tweaking my apex launcher settings ... about the orientation you are talking about, i feel an app separately for that purpose is counter productive as it sets off a service in the background, when we are already so pressed for RAM on our device.

Come to think of it, a landscape mode is only needed to read PDF's the fine print one's and this can easily be achieved, thanks to Ebookdroid a great app to read PDF's in landscape as well as reverse landscape, and the best thing about it is this setting is limited to the book, so once you set up a specific PDF in landscape of your choice the setting stays when you subsequently open it to read. This way PDF's that are legible in portrait mode can be read as it is.

we can understand ... we all can't thank you enough [MENTION=2685019]kfazz[/MENTION] ... for helping us out on this ROM ... looking forward to a whole new next build ... can't say i understand what you have stated though, but i am hoping it must improve our ROM to the next level ... THANKS !!!
[Nook Touch Android Development] :
So sorry for the wait on the instructions!

As stated above, sorry for the delay! Here are the instructions:

To make the soft keys and status bar transparent

- Open /system/build.prop with a root-enabled file explorer.

- Find this line:

ro.config.low_ram=true

- Change it to this:

ro.config.low_ram=false

- Save the file.

- Reboot.

To remap the hard keys for back and menu

- Open /system/usr/keylayout/twl4030-keypad.kl with a root-enabled file explorer.

- You will see four lines. These are the hard key mappings. A guide to which line goes with which key:

key 407 is the top right key.

key 412 is the top left key.

key 158 is the bottom right key.

key 139 is the bottom left key.

- Now, you just have to decide which two keys you want to be back and menu. The other two will be assigned page up and page down. For example I have key 412 assigned BACK, key 158 is MENU, key 412 is PAGE_UP and key 139 is PAGE_DOWN. You decide.

- When you're done, save it.

- Reboot.

Hey, different strokes for different folks. You're entitled to your opinion, and I'm entitled to mine. ;)
[Nook Touch Android Development] aiamuzz:
You BET !!! ... on the opinions part ...

a few strokes match ... a few don't ...

well !!! ... our love for our NOOK'S ... is one for sure that seems to match !!! ;)

[MENTION=5981373]ИΘΘK¡€[/MENTION] ...

the softkeys and notification bar didn't turn transparent ... i changed the setting from true to false ... do i have to do something else in the device settings after changing that ?

Sweeeeet .... the key bindings work like a charm, with back and menu back ... it feels like Heaven !!!

my thumbs were aching trying to reach for the softkeys !!! small things make a Big difference !!!

---------- Post added at 06:32 AM ---------- Previous post was at 06:15 AM ----------

about the keyboard, Last night i installed ai.type free version and its theme for lollipop ... and i must say its the closest i could come to our nook stock keyboard. the apk file is a little bit heavy almost 30mb but the keyboard experience is great ... guys you could try it ... see if the strokes match ... ;)

[MENTION=5981373]ИΘΘK¡€[/MENTION] ... i tried adding the qemu.hw.mainkeys=1 at the end of /system/build.prop file ... but that is not disabling the softkey besides the failure to make the notification and softkeys bar transparent !!! Any additional steps to disable the keys and make the notification transparent ?

An yeah i forgot to share ...

I used gparted to resize the partition on my SD card ... now my internal storage partition is more that 1GB ... i was tired of uninstalling apps for lack of space ... especially when i was testing so many apps on this ROM ... i must say works like a charm with so many apps already on my device ...

Thanks to the community and [MENTION=2685019]kfazz[/MENTION] in particular on this thread for this thread !!!
[Nook Touch Android Development] aiamuzz:
Hey, found some time to meddle with the KB app i was talking, see for yourself(screenshot attached).

can't beat this ... Enjoy !!!
[Nook Touch Android Development] :
[MENTION=4399146]aiamuzz[/MENTION],

Here, try following this guide for transparent status and navigation bars. I am going to when I have time.

Also, try adding this to build.prop instead of what I said before:

qemu.hw.mainkeys = 1

(with the spaces)
[Nook Touch Android Development] aiamuzz:
Hey thanks [MENTION=5981373]ИΘΘK¡€[/MENTION] ...

that seems a little too complicated to me ...

Now that you've helped configure my hardware buttons, getting rid of the soft key is all i am looking for ... a transparent notification would have been cool though !!!
[Nook Touch Android Development] :
Got it.

Okay, so I just tried putting this (no spaces) at the end of my build.prop file for the first time...

qemu.hw.mainkeys=1

...and it worked! It actually removed my soft keys after rebooting. Then, to get them back, I just changed it to this...

qemu.hw.mainkeys=0

...and that also worked. So, here's what I am recommending you should do:

1. Add this to the end of /system/build.prop in its own line:

qemu.hw.mainkeys=0

2. Save the file (make 100% sure it saved) and reboot. After it reboots, make sure you still have your soft keys.

3. Go back and edit /system/build.prop again. Change the

qemu.hw.mainkeys=0

you made before to

qemu.hw.mainkeys=1

4. Save the file, reboot and enjoy.

Let me know if this works!
[Nook Touch Android Development] aiamuzz:
Bingo !!!

that line was already in my build.prop from yesterday ... with a '1' flag

but i noticed that i had qemu.hw..mainkeys=1 ... two dots between hw and mainkeys ...

I however corrected that and followed your complete procedure and Wallah !!! the softkeyzzz were history !!!

thanks NOOkie ...

and guys you might want to install this app on this ROM, in the absence of a playstore this should compensate enough, especially given the fact that it is more of an ereader app store ...

except for GoogleNewsstand :( app i think i can live with this app !!!
[Nook Touch Android Development] aiamuzz:
[MENTION=2685019]kfazz[/MENTION] ...

i tested yattaro & NOOkie's 1337 ROM ... it supports SWAP ... tested on a small 64mb swapfile.

and now i tested on your ROM ... got the following error ...

swapon failed for /storage/sdcard1/swapfile

i know its not a good idea to create swap file on NAND ... but as the SDcard structure of your ROM is complicated i tried it there to see if it switches ON.

Can you please enable swap on this ROM as well ... similar to Yattaro&NOOkie's 1337 ROM ?

Hope to counter the sluggishness of this ROM for heavy reading apps, currently Kindle app ver 4.11 is not opening the book.

Would really appreciate if swap is enabled on this ROM.

Can i get the true path of /storage/emulated/0 ?

as i cd into the emulated and 0 folders ... via the terminal ... i can't list anything within them.

I would like to attempt creating a swapfile in this area (the emulated sdcard)

thanks,
[Nook Touch Android Development] :
UPDATE - SoftKeyZ has inexplicably stopped working. I got the Xposed framework installed and the modules I've tried work great. Got Apex and Nova to see which one I like best. /system/framework/framework-res.apk doesn't recompile at all after ADB pulling to PC and using apktool to decompile, even with no modifications. Without the ability to recompile framework-res.apk, I won't be able to patch it for translucency in the status and navigation bars. [MENTION=2685019]kfazz[/MENTION], any idea why this is happening?
[Nook Touch Android Development] kfazz:
you might have to pull /system/framework first and apktool -p path/to/framework/files
[Nook Touch Android Development] :
Thanks, I'll give that a try.
[Nook Touch Android Development] aiamuzz:
Looking forward to your tweaks ... NOOkie ...

were you able to do it the way [MENTION=2685019]kfazz[/MENTION] had advised ?
[Nook Touch Android Development] :
Still in the middle of my school day, so not yet. ;)
[Nook Touch Android Development] aiamuzz:
I am no techie ... but i did a little digging ...

would i be wrong if i assume the excessive ghosting could be becos of high refresh rates in kitkat ?

Source : http://en.wikipedia.org/wiki/Android_version_history

" Google announced Android 4.1 (Jelly Bean) at the Google I/O conference on June 27, 2012. Based on Linux kernel 3.0.31, Jelly Bean was an incremental update with the primary aim of improving the functionality and performance of the user interface. The performance improvement involved "Project Butter", which uses touch anticipation, triple buffering, extended vsync timing and a fixed frame rate of 60 fps to create a fluid and "buttery-smooth" UI.[96] Android 4.1 Jelly Bean was released to the Android Open Source Project on July 9, 2012,[97] and the Nexus 7 tablet, the first device to run Jelly Bean, was released on July 13, 2012 ... "

though this is listed as under Android Jelly Bean ... i am assuming that it would have continued to kitkat and beyond.

further a post on one of the thread here on the forum suggests ...

http://xdaforums.com/showpost.php?p=56377505&postcount=4

that " Android doesn't let apps control the display refresh rate, it is a system-wide setting ... "

Will tweaking the minimum and maximum refresh rates at all time like we do to manage the CPU frequency yield a better overall UI experience reducing ghosting ? basically regressing(basically undoing the whole smooth UI experience) from the project butter and project svelte changes with regard to refresh rates !!!

I don't know what i am taking is even valid concept/understanding ... Please ignore if it turns out to be utter rubbish !!! :D

[MENTION=5981373]ИΘΘK¡€[/MENTION] ... while you are at tweaking the framework is it possible to change the 'settings' theme(system wide if possible) color from white text on Black Background to a reversed color scheme (black text on white background) ... it was this way in Energy Ereader Pro(a.k.a Boyue T62) ???
[Nook Touch Android Development] :
I could, but it would be a long, long process of .png editing for that to happen. Instead, just use a light-schemed CM11 theme!
[Nook Touch Android Development] aiamuzz:
Oh ... is it ?

Didn't know it was a mountain of a task.

downloading a theme right now ...

Will these themes get additional baggage burdening the RAM, when they are implemented on the device ?
[Nook Touch Android Development] kfazz:
Edit: resp. To post #118

You're right, I'm looking into this.
[Nook Touch Android Development] aiamuzz:
Oh really .. ok ... thanks for reading ...

if any-and-all system wide animation's can be switched off including scroll animation system-wide, if our device can work only on a one-refresh-per-navigation(scroll) then that could greatly improve user experience as well as battery life.

I had swap activated on my first Android device (low end device with 256MB RAM) and it really helped back then. The stock ROM used to keep throwing memory full messages but once i loaded a CM ROM and activated swap, i could open more than 5 tabs on the dolphin browser and toggling between those tabs would not reload the page(even light multitasking between the dolphin browser and some apps would keep the pages in those tabs static and going to them would not reload the page).

I am really hoping it will help in the same way on this ROM as well. If it helps a single reading app at a time(with no multi-tasking) smoothly without lags would greatly enhance our user experience.

[MENTION=2685019]kfazz[/MENTION] ... could you enable swap on this kernel before the next build ... i could test performance over that as well, will at least know if it proves to be useful or not.

thanks for all the efforts !!!