yashsingh1/xdaforums huggingface dataset:
[Nook Touch Android Development] kfazz:
just tested swap. it works, BUT... it's a really bad idea.

if you create one on external sd you'll probably be buying a new card monthly.. and if the internal well...

it could kill the internal mmc.

root@zoom2:/mnt/media_rw/sdcard1 #busybox dd if=/dev/zero of=test.swap bs=1M count = 10
10+0 records in
10+0 records out
10485760 bytes (10.0MB) copied, 0.446091 seconds, 22.4MB/s
root@zoom2:/mnt/media_rw/sdcard1 # mkswap test.swap
root@zoom2:/mnt/media_rw/sdcard1 # swapon test.swap
root@zoom2:/mnt/media_rw/sdcard1 # free
total used free shared buffers
Mem: 237476 233736 3740 0 1120
-/+ buffers: 232616 4860
Swap: 108532 11368 97164

Note: swap numbers don't match because zram is also enabled, ie swap to compressed memory pages.
[Nook Touch Android Development] aiamuzz:
hey thanks,

i know it degrades the memory card with its repeated read/write cycles as a result of the memory spread.

But thanks for enabling it ... was it already enabled or you just did it now ... [MENTION=2685019]kfazz[/MENTION] ?

I know i am being a little too optimistic here ... but i just love my nook far too much ... and i wouldn't be surprised if the more experienced folks out here think i am day dreaming ... So an ideal scenario i am really hoping for is running both your ROM and 1337 ROM out of my device ... as the day dreaming goes ... With Boot Manager ... as posted HERE ....

I know all this translates into a lot of work for all you guys !!!

thanks for trying though, even upto this point !!!
[Nook Touch Android Development] kfazz:
it was already enabled.
[Nook Touch Android Development] kfazz:
Quick hacked up Nook keyboard Demo:

i started with eclair's latinIME, renamed it to NookIME, and added res/ folder from stock keyboard.

dictionaries don't work because api changed.

i fifn't add any source changes like waveform control that stock kb uses.

and theres layout glitches.
[Nook Touch Android Development] :
I assume that by "Eclair" you mean "Nook Touch"?
[Nook Touch Android Development] aiamuzz:
Oh ! ... Then i got an error when i tried creating it ... let me retry.

[MENTION=2685019]kfazz[/MENTION] ... thanks so much this was much needed reprieve(the stock KB was sooo off for this device ... also even if i wanted to rave about ai.type keyboard as much as i want to) ... the fact remains that it(ai-typeKB) is a memory hogger not suitable for our device ... this app trades about 30-40 MB of RAM space of ai.type ... with just 2.7 MB of RAM.

Is this the stock NST/NSTG keyboard repacked with this ROM's framework right ?

or its from the other nooks(color), etc ?

the only difference is the rectangular key dimensions are traded of to square ones reducing the key tap area on CM11 ... besides that its manageable ...

And yes is there a way to switch off the kep popups ? I couldn't find it in the KB settings.

---------- Post added at 09:17 AM ---------- Previous post was at 08:25 AM ----------

UPDATE :

Yes Swap works !

I think i figured the error of my way previously.

I used /storage/sdcard1(when it should have been /mnt/media_rw/sdcard1), the path to create the swap file.

either that or i didn't use 'busybox' before the 'dd' command whilst creating he swap file.

Now that swap is enabled on this ROM,

my intented roadmap would be ...

... to create a swap partition(using gparted) towards the end(right-most-side partition) of the sdcard, I am hoping that way the deterioration to the sdcard is limited to the partition designated area only. I am hoping even if that part(patch) of the sdcard gets corrupted the rest of the sdcard hopefully will be in its pristine form.

I choose the swap partition method against a swapfile method, bcos when a swapfile is created, it could be created anywhere on the sdcard with no control where, whereas with a partition we are limiting it to a specific area on the sdcard, a contained deterioration.

As that swap partition deteriorates over time, a new swap partition can be created a little before(to the extreme right of the sdcard, just before the previously deteriorated swap partition) leaving the old swap partition un-allocated.

Repeating the above each time the swap partition deteriorates for as long as my sdcard capacity keeps it within practical limits. (Say if one creates a 128MB swap partition, then a 1.5 GB hit on a sdcard with 32GB or 16GB would be acceptable(annually, one partition a month), at least i would like to think so, considering the value it brings in the form of better and breathable user experience on our device)

I am hoping this way i can keep my sdcard damage(as a whole) to the minimum in spite of using swap, and prolong its life.

This is just my imaginative self ... as i lack in depth knowledge on the true functioning of sdcard read/write cycles and its impact on an sdcard, my imaginative theory might have holes in it ...

Please feel free to punch holes in it !!!

I just value all you guys efforts a LOT, and want those efforts to be put to good use.

Hence my dream world !!! :victory:
[Nook Touch Android Development] kfazz:
nope. eclair straight aosp 2.1 stock source.
[Nook Touch Android Development] aiamuzz:
[MENTION=2685019]kfazz[/MENTION] ... can you you attempt the same procedure with the NST/G ROM stock keyboard the way you did with stock eclair KB (yes its a little choppy compared to the stock nook KB), and see if it works ?.

thanks.
[Nook Touch Android Development] aiamuzz:
[MENTION=2685019]kfazz[/MENTION] ... I was attempting to create a 64MB swap partition at the end of my 2GB sdcard.

As the current partition structure has 4 primary partitions and a 5th partition wasn't possible (on gparted)

i backed up the apps partition through 'dd' then deleted it, then created an extended partition, restored the backed up apps partition, then i resized it for the free space it had and released 64 MB then i created a swap partition of this 64MB.

Tried booting up but the nook was frozen at the login image ... read forever screen.

Will it not work if the app partition is on a logical partition ?

Is it possible for you to create a 64 MB towards the physical end of the sdcard while uploading the next sd.img ? If its possible to do such a thing.

[MENTION=5981373]ИΘΘK¡€[/MENTION] ... any luck on the framework modd you were planning ?

In your free time could you attempt the procedure kfazz followed with the stock eclair KB, instead of stock you could try it on our NST stock keyboard ?

thanks.
[Nook Touch Android Development] :
No luck yet, sorry. :(

Sure, I'd be glad to do so when I have time. I have my final exams this Friday, so I will have ZERO free time this week. But after, when school's over and done, I should be able to make a bit of headway.
[Nook Touch Android Development] aiamuzz:
no problem ... All the best for your exams !
[Nook Touch Android Development] kfazz:
as long as the partition numbers stayed the same it should have worked. not sure if the extended partition gets a number of it's own or not. if it does you'd have to see how the new partition numbers go, and edit the fstab / init scripts / disable fsfinder / on the rom.

also, i'm not even sure that damage to an sd can be confined to a single logical area in any meaningful sense, due to wear leveling.

it'd probably be evenly spread across the whole card. ymmv.

if you have spare sdcards, it might be easiest to create a swapfile in the data partition, since it's always mounted read/write while the system is booted.
[Nook Touch Android Development] aiamuzz:
thanks for replying [MENTION=2685019]kfazz[/MENTION] ...

Yes the extended partition does get a number of its own.

further the partitions within get an incremental number in the order it was created.

Well ... my skills might fall short in editing fstab / init scripts / disable fsfinder ... i'll look into it, if i don't understand ... i will ping you for help

Will the 'wear levelling' you are talking about affect the whole card even if a single partition is extensively used in case of a swap partition ? I thought a partition was supposed to lock a cluster of memory blocks and whatever corruption that may happen due to wear&tear within that partition should be limited to those blocks only.

Well if that's not the case, then its bad news.

I thought swapfile would have that affect, and a separate partition would mitigate the wear leveling across the whole card. :crying:

Yes I have created 64MB swapfile on /data/media/0/swapfile with swappiness between 70-80 just for testing (havent set it up at boot) ... As a result for the first time i could open a book from within the kindle app(Ver. 4.11) ... on your ROM. it was choppy but atleast it opened and i could access the enhancements of the kindle reader on my NST.

will seek your help when stuck.
[Nook Touch Android Development] kfazz:
Test build #3:

Kernel Changes:

switched back to my branch, with some critical fixes from encore branch.

wifi sleep issue fixed.

boot with charger preventing suspend/charging still present.

added governors for gpu speed from never PVR DDK's 1.9+

core clock raised to 400MHz from 332Mhz

this raises ram speed to 200Mhz which is within spec,

and allows gpu to run at 200Mhz full speed instead of 133.

200Mhz opps are what most 3630s run on, bn limited the nook to 3430 speeds for some reason.

Android changes:

more hacking around with surfaceflinger

refresh rate is overridden to 20fps. instead of 58 which comes from the gralloc module.

dirty region rendering is on, but invalidations are proogated down? the whole layer stack so ie pressing a button on an app still redraws the whole view.

might drop the refresh rate in future, or try to hack some way of making it waveform dependent.

20fps is probably around how fast we can go in A2 mode around room temperature though, so that's why i picked it.

I'm posting two versions of this build:

one with hwui disabled, and one with it enabled. i recommend the disabled one, as all apps rendering with hwui eats about 30mb ram. i might try to force it off for settings, launcher, and systemui at some point.

https://drive.google.com/folderview...FuSFhGSC1KSmlxYTNQMnlCTC1qOVFnbVk&usp=sharing
[Nook Touch Android Development] aiamuzz:
Hey ... seems like a lot of changes ... downloading the hwui disabled version as per your recomendation ... do you mean the hwui enabled vesions consumes 30MB additional RAM as compared to the disabled one ?

The updating is pretty straight forward, if we are coming from build #2 ... copy both files to media and flash it ... all apps and settings from previous build will carry forward to the new build as well ... right ?

will test and report back ...

thanks [MENTION=2685019]kfazz[/MENTION] !!!
[Nook Touch Android Development] :
Remember that the new builds will overwrite your twl4030-keypad.kl file every time you update, so always keep a copy of that handy on your /media partition!
[Nook Touch Android Development] Kralik:
I think the TWRP gods must hate me. I tried using the new sd2.zip... didn't work. Manually copied uImage-recovery etc... didn't work. Tried a different Nook... didn't work. Issuing the above commands in adb did work! Not sure what else to say, or why I was having trouble with even release #1 while others weren't, but thought it might be good to know.

EDIT: Just got it to work without all the tweaking when I rebooted my second Nook with the USB cable still attached to the computer.
[Nook Touch Android Development] aiamuzz:
Hey thanks ... [MENTION=5981373]ИΘΘK¡€[/MENTION] ... figured that one AFTER i flashed build#3 ... even the softkeys need to be hidden once again in build.prop

[MENTION=2685019]kfazz[/MENTION] ... the kernel is still crashing on me ... i flashed the ROM last night just before going to bed ... let the ROM boot and let it to go on standby ... after a while the kernel crashed and the screen went to the boot image - Trigger No 1 confirmed

then i put the deevice to standby/sleep by engaging the power button ... again after sometime ... the kernel crashed, same as above - Trigger No 2 confirmed

the only difference i saw was it was occuring after a little delay unlike last time where it out more-or-less occur immediately after going to standby through both the above ways ... if this anomaly helps !

Build #2 seems to never have had this problem ... my best build so far ... my device has been on this build as a matter of days.

to avoid screen burn-ins i removed the SD card before going to bed !!! ... not that it means burn-ins are still happening ... just didn't want to risk.

thanks for all the efforts [MENTION=2685019]kfazz[/MENTION] !!!
[Nook Touch Android Development] aiamuzz:
[MENTION=2685019]kfazz[/MENTION] ...

I accidentally left my nook on this ROM in the afternoon ... in the evening i realized and jumped for it ... fearing a kernel crash and screen burn ... thankfully, i think the fix that you had put seem to work ... my screen wasn't burned in ... though it was stuck on the boot image

and the crash seems to be triggering on wake, from standby in the short term and crashes while on standby, but can't pin point on the trigger on standby ... earlier if i remember right it used to occur immediately on-sleep hope this helps to understand whats going on .

I am not leaving the sdcard loaded ... so let us know if you want to us to test anything specific ... will boot into the SDcard and confirm the results you may need.
[Nook Touch Android Development] :
Just flashed Pre-alpha build #3 on my study break - working great so far!

Good news - I had been having some issues with SoftKeyZ for a while, but this new build fixed it , so :highfive:!

EDIT - Weird issue with my hard keys, they don't register any action when pressed. In Renate's UsbMode utility, they all come up as "UNKNOWN". [MENTION=4399146]aiamuzz[/MENTION], you having this issue?
[Nook Touch Android Development] kfazz:
This is probably due to the commit I reverted to fix WiFi suspend. I'll look into it.
[Nook Touch Android Development] aiamuzz:
Thanks ... is it possible for you to realease a quick fix by recommitting that change in particular so that we can test the rest of the ROM changes in build 3 ?
[Nook Touch Android Development] tdcfpp:
You told it right: "looks like it supports ttyusb". When I created that repo I was a noob. I didn't got it working. But I'm happy to be referred here.

BTW. Good job. When I have time, I'll try to build it. Maybe I an able to be of help. Got experience in arm disassembly.
[Nook Touch Android Development] aiamuzz:
[MENTION=5981373]ИΘΘK¡€[/MENTION] ... no ... i haven't gone to the extent of USBMode, cannot confirm the same. regarding the hardkeys, the first time i tried mapping it did not work ... then i made them default and tried again it worked this time around.

& are you not facing kernel crashes ? i am facing hence i don't keep my device on this ROM, only while testing.

[MENTION=3350694]tdcfpp[/MENTION] ... welcome to the thread, we would appreciate whatever value you can bring to this ROM ... many of us here aren't techie's ... hence you guys are always welcome.

[MENTION=2685019]kfazz[/MENTION] ... is already doing a fantastic job ... for something pre-alpha ... his builds are nothing short of GREAT !!!

Besides issues arising out of our devices hardware limitation(RAM) and the fact that this is an e-ink device ... the ROM is smooth !!! Only e-ink specific optimizations are what are needed ... and he is already at it !!!
[Nook Touch Android Development] :
Huh. Guess I'll have to reflash and edit by hand, since overwriting the old ones with the new from /media seems to have broken the hard keys. :eek:

Haven't seen any kernel crashes as of now, but I've only run the ROM for a half hour at most.

UPDATE - [MENTION=4399146]aiamuzz[/MENTION], I fixed my hard key issue after I realized that the permissions on the pasted file were probably wrong (before I reflashed). :)

Just remember, whenever you copy/paste your twl4030-keypad.kl file into /system/usr/keylayout after you flash future builds, make sure that the permissions are set to rw- r-- r--, or else the Nook won't recognize the file and will render your hard keys useless.
[Nook Touch Android Development] :
[MENTION=2685019]kfazz[/MENTION], I tried what you recommended, but I still got a huge error log (see the attached .zip which has a .txt in it). I literally just decompiled framework-res.apk and attempted to recompile without making any changes.

Can you help me?
[Nook Touch Android Development] timeslip1974:
Is Google Books working with this rom yet?
[Nook Touch Android Development] aiamuzz:
No! ... as gapps is not installed on this ROM, anything that requires a google account is out of bounds.
[Nook Touch Android Development] borzeh:
Is this alpha version dangerious for device?

Nst glowlight

I need to install application that gave parsing error on eclair rom

Is this rom good for me? I know this is alpha and there is bugs , but is there any serious problem with device health?

Thank you
[Nook Touch Android Development] drnessie:
Fastmode and Video

I gather that fastmode as not yet been implemented? Does anyone have a video of this working, I'd like to see it before I try. At least it's running from SD so I can return to normal nook whenever, but I'd just like to see if it's worth it!
[Nook Touch Android Development] aiamuzz:
No Danger ... as it runs out of SDcard ... nothin on your eclair rom is touched.

If you know how to write the sd image to your sdcard ... then you can surely try ... find instruction on the post where the build #1 is posted ... and download files from build #2 ... avoid build #3 ... for now ...

sorry [MENTION=2207771]drnessie[/MENTION] ... no time to upload video, if you are apprehensive about trying a pre-alpha build ... then you might sit this out ... until an alpha/beta/stable builds are out ...

However if your curiosity seems to be getting the better of you ... then feel free to try ... as it runs only from your SDcard ... no danger as already stated above ... at the most it may not boot ... if sd image is not written properly ... remove sd card load your original sd card and you'll boot into your stock rom.
[Nook Touch Android Development] timeslip1974:
awwwwwww that`d be my entire reason for using it!
[Nook Touch Android Development] Deafcyclist:
How large of a microSD card would you recommend for trying this out? Since it is entirely run from the SD card without touching the internal memory, I am completely willing to test it out. Just need a quick guidance on how to install it though since it seems a little different from the other ROMs I have tried. I have a few 2GB and one 4GB cards I could use for this.

Thanks.

EDIT: Been trying to install the #3 zip. Keep getting error #0 in the CWM Recovery (on both the internal and SD CWM). I'm not sure where to go from here. Am I just missing something obvious here?

Thanks
[Nook Touch Android Development] :
I use a 2 GB card for this ROM.

Don't try to flash the zip in CWM! Instead, write sd2.img to the sdcard, turn your Nook off, put in the sdcard, turn your Nook on, let it boot into TWRP, mount /media, and flash the zip from TWRP. Then, tap "Reboot system" and it will boot into CM11.
[Nook Touch Android Development] Deafcyclist:
Ah, thanks. That helped a lot! Got CM11 on my SD card and your 1337 ROM running internally. This is probably the best of the both world for me until CM11 becomes more stable and optimized for NST.
[Nook Touch Android Development] :
Glad to help. If you need anything else, just post in this thread or shoot me a PM. :)
[Nook Touch Android Development] Deafcyclist:
Thank you :) I will. Currently working through various settings on the CM11 to see if I can streamline the usage and minimize the RAM hogging. Was surprised to see a number of audio related stuff still in the ROM since the NST have no mic or speaker. Like the voice recorder that I promptly disabled and whatnot. Trying to wake the screen up is a hassle though. Not very reliable so I'm trying to see if an alt lock screen would help in conjunction with certain other settings.
[Nook Touch Android Development] aiamuzz:
[MENTION=2685019]kfazz[/MENTION] ... i was waiting for the fix ... 'crash when wake from suspend' ... to test the many developments in build #3 ... this crash is annoying ... i usually test it in between my work ... and device goes to sleep between work ... waking device crashes ... looking forward to this fix. Build #2 was great and suited my testing mode(in between work) that way ...
[Nook Touch Android Development] kfazz:
The commit breaks WiFi. I've been running build 3 since I posted it and I can't reproduce the crash. What nook do you have?
[Nook Touch Android Development] aiamuzz:
oh ... sleep wake working fine for you and others here on build #3 ?

Mine is a NST-G !!!

Ok ... i tried loading the SD card and testing it a bit more,

The crashing's are around the sleep/standby/wake, the following times i encountered a crash

The device has crashed on me a few times when the device boots and i left un-attended and leave it to sleep, trying to wake it, would crash and take the device to the read forever (boot image).

Right from the first build the home(nook) button wake is not consistent, it works intermittently, So when i try to wake the device by pressing the nook button, it doesn't respond and then when i reach out to the power button, the device crashes on me, this has happened more than a few times.

The device goes to sleep on the last image, in this case the home screen. the lights go out, hinting that the device is in standby. I press the nook button, no response, i press the power button, no response, i try to enter power again and again after a few secs in between, But device does not wake. I am sure the device hasn't shut down completely, bocs if it was shutdown, pressing power button to restart would have restarted the device, but it doesn't happen so, i have to press and hold the power button for more 10-20 secs give a pause and then try restarting, and then it restarts.

A few times when i press the power button to put it to sleep, and then try to wake it, as nook button does not wake the device, a subsequent power button wake send the device to the boot screen

As you can see there is no specific pattern really, but the device crashing on me is common. Is there something that i can run which will log/record this behavior to a file for you to analyze ... a logcat or something, please let me know i'll run that and capture the crashing event.

thanks for looking into the issues faced.
[Nook Touch Android Development] kfazz:
After it crashes and reboots, see if /proc/last_kmsg exists. If so please post it. If not try suspending, then connect USB. Try waking it up. See if you have adb access. If so pull /d/gpio
[Nook Touch Android Development] aiamuzz:
Firstly after it crashes the device doesn't reboot by itself, it stays on the 'read forever' screen and probably hangs. I have to press'n'hold power button between 15-20secs then restart.

first attempt :

I loaded the sd card booted into device. after device went to sleep tried nook button to wake, ... :( ... but it crashed to the boot image as stated above. did the above and restart the device. did not find /proc/last_kmsg ... probably bcos i had to boot the device manually.

second attempt :

device was on adb wireless, I put the device to sleep(power button) then tried waking through nook button first, but it didn't respond, then i used power button to wake & screen crashed to the boot screen ... :( ... been sitting there like that, while i am typing this post. Probably frozen ... need to manually hard boot. While its sitting on the boot image i tried adb devices it showed list of devices as connected to the nooks IP, tried pulling /d/gpio ... but the command has frozen on my linux terminal.

Update : after i posted this post ... the device blinked while in the boot image ... will try to leave device in this state for some more time. hopefully i will be able to pull either or both of the files you've sought.

[MENTION=2685019]kfazz[/MENTION] ... what do you advise ?