yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] dweaton:
Maybe this applies to my problem somehow - especially the part about being out of memory? I went back through the entire thread again and did find this post that the end result problems sounds like mine. Note I have the BNRV200 so I only have 8gb of memory.

steven676	Old

31st January 2014, 11:16 AM

#44

Senior Member - OP

Thanks Meter 2343

Posts: 569

Join Date: Nov 2011

Quote:

Originally Posted by highnoteuser View Post

Thanks for the reply. I'm not a dev, so I don't understand how this would save disk space on an install that does not install these two apps. I do make custom GAPPS packages and, like most, put GoogleHome in system/app. This causes it not to work in all GAPPS that use that structure (most) and in some cases, when a command to remove Launcher3 is in place it will cause the system to hang after doing the CM Account setup.

I came up with a workaround by having the GAPPS updater-script delete your GoogleHome.apk before installing the functioning one, but most other GAPPS are not setup that way and wont work.

I would suggest that line of code be removed so more of the popular GAPPS packages will work with our Nook.

That's exactly the intended result, though -- GoogleHome is more than 12 MB, and if we were to let the larger Google apps packages install it, many eMMC installs would run out of space before finishing installation (which causes problems like not having the Play Store and not being able to add a Google account). If nothing tries to install GoogleHome, the symlink is harmless -- the system will ignore it. I agree that this is an ugly hack, but it's better than dealing with a flood of questions about why the Google apps are broken from users who didn't install the "official" package.

Thanks to these disk space limitations on eMMC, we're just not going to be able to support Google apps packages that attempt to install GoogleHome as the only launcher. (If you really want the Google launcher, I believe CM is looking at shipping a stub for it in the base system -- that would be much smaller because it would omit the wallpapers in the GoogleHome package. If you're really, really, really insistent on shipping the GoogleHome stub including the Google wallpapers, then delete the symlink before installing, but don't complain if your system breaks after installing it.)

ThanksThanks

REPLY Multi-Quote This Message

QUICK REPLY
[Nook Color Android Development] dweaton:
Will repartioning with different sized partitions help, or is this in an area that can't be resized?
[Nook Color Android Development] leapinlar:
It can be resized if you know what you are doing. There are no zips that anyone has made to do it. If you look at the work in progress thread there was some discussion about doing that for CM11.
[Nook Color Android Development] steven676:
Yeah, as you've guessed, it looks like /system is full. I'd suggest trying the 20140105 Google apps package before doing anything more drastic, though -- there have been complaints about the newer one from other people running devices with small /system partitions. (I also need time to look into the growth of the base system -- you'll notice the compressed OTA package grew close to 7 MB between CM-11.0-M7 and -M8.)
[Nook Color Android Development] bowguy:
Issue with 7/24 nightly

Installed the 7/24 nightly via CyanDelta and after booting it locked into a "process.android.phone has stopped" loop. I hit the OK button over a dozen times (it was constant) and finally had to force a power down and went back to 7/23. Has anyone else run into this?
[Nook Color Android Development] hwong96:
CMUpdater 7/24 nightly running fine. Still has the hidden clock bug where upon reboot the clock shows in center and default locations.
[Nook Color Android Development] steven676:
A note about Google apps ...

I've updated the second post upthread to indicate that you should not use the latest "official" CyanogenMod Google apps package (20140606) on eMMC installations. That package contains more than 100 MB of additional bloat over the older 20140105 (now called "small" on the CM wiki page) package, mostly in apps that you can download from Market (Google Play Books/Magazines/Music/Games/Movies, YouTube, Google+, Google Maps and Street View).
[Nook Color Android Development] pastordl:
There is an alternative that will allow the larger Gapps over on the CM11 work in progress forum. A couple of repartitioning zips give a larger /system size of 1.1 Gb. More than enough for what is needed currently. This is the link: http://xdaforums.com/showpost.php?p=54401912&postcount=4177.
[Nook Color Android Development] steven676:
I'd gently suggest not doing this unless you're feeling quite adventurous; you're going to have to wipe backup and restore the entire device to do it, and you're likely going to have to repartition again down the road.
[Nook Color Android Development] pastordl:
Thanks Devs for fixing the double unhidden hidden clock in the status bar after reboot problem in the 7/27 nightly.
[Nook Color Android Development] pastordl:
Wallpaper choice disappearing again

7-27 nightly wallpaper choice in Nova working fine. 8-1 wallpaper defaults to blue rocks with large white "O". Any attempt to change results in reboot and back to the same blue rocks and large white "O". Reverted to 7-27 for now.

Edit 1:Same wallpaper problem with 8/3. Did check and saw that a change was made to trebuchet between the dates noted above. Guess I'll have to wait till I see more changes there to try to update again.

Edit 2: Installed M-9 can pick any wallpaper I want and it stays. Yippee, Yahoo, Thanks.

8/6 ok also.
[Nook Color Android Development] bowguy:
That happens to me once a while. Never had it reboot when changing wallpaper. Odd. I am on 8/1 with no issues fwiw
[Nook Color Android Development] e.mote:
Hi all,

Let me first thank all the folks who are still keeping the NookC ticking: Steven676, fattire, the tireless leapinlar, and all the contributors. It's a bit amazing the 4-yr-old guy--an eternity in tablet time--is still able to run the latest software and apps. Let's hope for another 4 years...OK, maybe not that long.

I recovered my NC from the "give to Goodwill" scrapheap and decided to give the ol' Ook another go. Installing CM10 was a bad move, as poor Ookie became slow enough to be unusable, and it sat languished ever since. Checked in to the old haunt here and saw CM11 is a go. Repartitioned, installed, and everything works (more or less). It's not exactly snappy, but good enough to be fully functional. Despite minor glitches, CM11 in present state is stable enough.

Questions:

I have 5GB /data, which is sufficient for me. I'd like to have the SD slot in its normal role, ie have /sdcard defaulting to /storage/sdcard0 and not sdcard1. As it is, Play Store installs work w/o the SD card, but sideloaded apps break. How do I restore /sdcard back to sdcard0? Am assuming it's a symlink somewhere.

From the other CM11 thread, I'm assuming that the envision repartition is to enlarge /system to accommodate the larger GApps, and to combine /data and /media into one partition (removing p8). Will the (external) SD's role stay the same, ie be the default for app installs? If so, what would p7 (data & media) be used for? Per previous Q, can I change this default to revert back to the internal SD?

Please excuse if these are basic knowledge. I'm not too familiar with Android stuff.
[Nook Color Android Development] e.mote:
Progress report to those who care...searched on my own questions above, and int/ext sd swap was built into CM7 and 9, but apparently with JB multiuser and now KK's SD changes, the old workarounds broke. Earlier in this thread, aperezdc suggested a patch to CM for user-settable switch; Steven676 pointed to a couple of existing requests for same; but in checking on their status, both have been abandoned. Searched same issue for other devices on CM11 (but flipped, as those folks want to default to ext); found no user solution that works across reboots.

Scanned through the CM11 WIP thread and found no mention of this issue. Am assuming that previous config for NC still holds, ie ext sd will be default primary going forward. My current resolution is to wait for the repartition and see if a solution is provided, else resort to running a script to remount after each reboot.

Thanks again to all involved.
[Nook Color Android Development] leapinlar:
If you look through the CM10.1 thread, you will see where steven676 did patch the ramdisk so that by putting a line in a property file, it switched the SDs. Look for posts by me. I don't know if that carried over to CM11.
[Nook Color Android Development] e.mote:
leapinlar, I'm assuming you're referring to your post here,

http://xdaforums.com/showpost.php?p=45615175&postcount=90

I tried this, and it doesn't look to work on CM11. aperezdc has found same (http://xdaforums.com/showpost.php?p=50063043&postcount=80); another neg here (http://xdaforums.com/showthread.php?t=2564398).

I've expanded search on this storage swap issue to other devices on KK/CM11, and the only workaround seems to be by running an init script on boot.

I appreciate the input all the same. I want to thank you particularly for your yeoman work in helping all the Nook newbies. Anyway, am hopeful steven676 or another will come up with a better solution than the above workaround.
[Nook Color Android Development] leapinlar:
I don't have CM11 on encore, but I do on HD and it shows the correct vold switchable pair line in build.prop but does not work because the HD does not use vold to mount sdcard0, it uses fuse. Does the encore CM11 build.prop have the correct switchable pair statement shown in my referenced post on the CM10.2 thread?
[Nook Color Android Development] e.mote:
>Does the encore CM11 build.prop have the correct switchable pair statement shown in my referenced post on the CM10.2 thread?

It does, although the order was swapped

ro.vold.switchablepair=/storage/sdcard1,/storage/sdcard0

I was unsure if the ordering mattered, so I switched it for sdcard0 to be first, as per yours,

ro.vold.switchablepair=/storage/sdcard0,/storage/sdcard1

But it still fails.
[Nook Color Android Development] leapinlar:
Go to terminal emulator and type su followed by mount. It should give you a listing of all the mount points. How are sdcard0 and sdcard1 mounted? By vold or fuse?
[Nook Color Android Development] EAK128:
This is how it looks on my NC running cm11

rootfs / rootfs ro,relatime 0 0

tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0

devpts /dev/pts devpts rw,relatime,mode=600 0 0

proc /proc proc rw,relatime 0 0

sysfs /sys sysfs rw,relatime 0 0

none /acct cgroup rw,relatime,cpuacct 0 0

none /sys/fs/cgroup tmpfs rw,relatime,mode=750,gid=1000 0 0

none /sys/fs/cgroup/memory cgroup rw,relatime,memory 0 0

tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0

tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0

tmpfs /mnt/fuse tmpfs rw,relatime,mode=775,gid=1000 0 0

none /dev/cpuctl cgroup rw,relatime,cpu 0 0

/dev/block/by-name/system /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0

/dev/block/by-name/userdata /data ext4 rw,nosuid,nodev,noatime,user_xattr,acl,barrier=1,data=ordered,noauto_da_alloc 0 0

/dev/block/mmcblk0p7 /cache ext4 rw,nosuid,nodev,noatime,user_xattr,acl,barrier=1,data=ordered 0 0

/dev/block/mmcblk0p2 /rom vfat rw,sync,noatime,nodiratime,uid=1000,gid=1000,fmask=0117,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0

/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0

/dev/block/dm-0 /mnt/asec/com.speedsoftware.rootexplorer-2 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0

/dev/block/dm-1 /mnt/asec/com.teslacoilsw.launcher.prime-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0

/dev/block/vold/179:49 /mnt/media_rw/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

/dev/block/vold/179:49 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

/dev/fuse /storage/sdcard1 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0

/dev/block/vold/179:8 /mnt/media_rw/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
[Nook Color Android Development] e.mote:
Maybe you can tell me. There are two entries for sdcard0 (I didn't have a card inserted), one says vold and the other says fuse.

/dev/block/vold/179:8 /mnt/media_rw/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
[Nook Color Android Development] leapinlar:
Try putting switchable pair as

/mnt/media_rw/sdcard0,mnt/media_rw/sdcard1

and the persist statement set to 1

The fuse to /storage/sdcard1 and 0 may be interfering. I'm just guessing here.

Edit: and e.mote, you are trying the swap without an SD inserted? Have you tried it with?
[Nook Color Android Development] e.mote:
Thanks for the brainstorm, even though it didn't work. Per your prompting, I did put a SD card in and reboot--but the point in defaulting to internal is not needing to have a card inserted. I tried it both with and without.

Rather than defaulting to /storage/sdcard1, it now defaults to /sdcard, which apparently is still linked to /storage/sdcard1.
[Nook Color Android Development] steven676:
New test kernel (L3 clock changes)

Trying to get some of the unreleased stuff off my hard drive ...

Here's a new test kernel for everyone to try out. The changes here involve adjustments to clock speeds on the SOC:

The L3 (memory bus) clock speed is reduced from 200 MHz to 166 MHz (-16%);

The maximum MPU (CPU) overclock is increased from 1100 MHz to 1200 MHz (+9%); the default MPU clock remains 1000 MHz.

Hopefully these changes should result in increased stability, particularly on devices where the existing 1000 MHz and 1100 MHz overclocks were unstable; see the dev thread for details. Unfortunately, I expect that performance will be down as a result of cutting memory bandwidth.

Please test, particularly if you have a device that's experiencing crashes or SOD at 1000 MHz with 3.0 kernels.

Instructions: from recovery, flash the attached ZIP file over a CM11 nightly.

Source code: https://github.com/steven676/ti-omap-encore-kernel3/tree/da8a2ef9d7b0306909dd2930d148871e2eb20566; this is also currently the tip of the encore-omap3-3.0.y branch in my kernel repository.
[Nook Color Android Development] EAK128:
Just flashed. Running nice and smooth, I don't really notice a slowdown. The only issue so far I came across is YouTube is not playing the videos, the first video played, but after that nothing, keeps saying connection to server lost. Let me know if you need any logs.

edit; never mind about the YouTube issue, it got resolved after a reboot.
[Nook Color Android Development] PowSniffer0110:
This is a known youtube problem while playing in HD. Google will not fix it. SD works fine
[Nook Color Android Development] pastordl:
New kernel

Works fine at 1000 mhz but slower. Total lock up when attempting to run any app after changing OC to 1200 mhz. Must use use 10 second power off to reboot. This unit has run better ie: more stable @ 1000 mhz with prior kernels. Have reverted to the regular kernal.

Updated to 11/11 Nightly everything ok. Then added new kernel, same story runs fine, but slow @ 1000mhz. Running [MENTION=1348102]1200[/MENTION]mhz app lock up the tablet. Thought it might be worth a try.
[Nook Color Android Development] bowguy:
Problem with Nightlies after 11/08?

Is anyone else having this issue? I am on 11/08 with no problems.

http://xdaforums.com/showpost.php?p=56702823&postcount=680
[Nook Color Android Development] EAK128:
Just flashed 11/11 with no issues.

As far as the test kernel, had some battery drain issues so decided to go back to the old kernel.
[Nook Color Android Development] hliew88:
Test kernel seems to be working great for me after a full day of usage on 11/8 nightly. I notice the slight drop in performance when multitasking (running low on memory), but the boost back to 1.2GHz is welcome when starting apps, transition smoothness, waking, etc. I also used to have SOD's with the Interactive governor (max 1.1GHz), but I used Interactive again since last night (max 1.2GHz) - no SODs anymore!
[Nook Color Android Development] highnoteuser:
I use the recommended GAPPS in the post on my phone and did a few tweaks to the updater-script and addon.d to remove a few of the useless CM apps. Works great on my phone, but gives me the "unfortunately, setup wizard has stopped working" error. The stock GAPPS will boot fine so I'm not sure why the seemingly harmless changes I've make will work on my phone, but not the Nook. Any dependencies or other ideas?

Edit: My script was set to uninstall CMAccount and Launcher3 and to install Google Home. I changed it to not delete those two apps and it booted up fine, but Google Home is still not an option and neither is the Sunbeam wallpaper apk that was loaded. All of that worked perfectly on my phone...
[Nook Color Android Development] bachikho:
cm11 is much slower than cm7 for daily use with nook color
[Nook Color Android Development] Mr-Glass:
Is there a work around for rebooting into recovery? I have used both CWM and TWRP.. A lot of the time I miss the manual button push resulting in a normal reboot...

edit...just a note - I do have advanced reboot selected in dev options, just not working when reboot to recovery selected.
[Nook Color Android Development] EAK128:
Another issue I noticed today is WiFi doesn't reconnect after waking up the nook from sleep, when you have never selected during sleep. Toggling WiFi off and on fixes it.
[Nook Color Android Development] ibilln:
For me, it's faster, a bit.
[Nook Color Android Development] Homer_S_xda:
Thanks! Here is the direct linky to the page: http://techerrata.com/browse/eyeballer/twrp

Homer
[Nook Color Android Development] tp2215:
Yeah, actually I have to agree. I have been running it since last night and have been getting great performance! There may be an occasional extremely small lag but considering all things, it is running great! Way better then cm10.2 was.Its very usable for a daily driver.
[Nook Color Android Development] Homer_S_xda:
I can vouch that the EMMC Recovery one works.

Homer
[Nook Color Android Development] highnoteuser:
For some reason I keep ending up with a 0 byte file of Hangouts and GoogleHome in system/app Any ideas?

TWRP works good but did not work with CM updater. I had to manually turn it off from a blank screen. When it came on it did finish the script though.
[Nook Color Android Development] meteorrock:
How is the ART function? If we are getting bootloops with some devices, <steven676> could disable that or hide it from being clicked on. I am sitting on a .zip wondering if I should flash. Too many conflicting reports coming in on whether which recovery will work or not. I know this build is in Alpha, just wanting to help.

People are going to try to fiddle with that function whether or not you tell them not to. The developers could re-add that feature when they feel more confident it will work without hangups. Just an opinion I wanted to add just in case it could of been overlooked.
[Nook Color Android Development] ibilln:
No conflicting reports on recoveries really. See post #18, or, the one two back.
[Nook Color Android Development] eyeballer:
There is an updated version of CWM 6.0.4.7 here: http://techerrata.com/browse/nook/recovery

This updated includes a patch from steven676 to prevent users from being about to wipe the /rom partition as it's bad news when you do...

https://github.com/CyanogenMod/andr...mmit/c5d03055a672b740e7c0972cac9635b5dba4614c
[Nook Color Android Development] Homer_S_xda:
Is there a corresponding update to your TWRP?

Homer
[Nook Color Android Development] eyeballer:
Not required.
[Nook Color Android Development] steven676:
That's to be expected -- we're intentionally pointing these at /dev/null to save disk space. You can install them to /data if you'd like.
[Nook Color Android Development] steven676:
Good news: January 31 and later nightlies should include patches (1, 2, 3) which should speed the bootanimation -- and as a nice side effect, the rest of the boot as well (bootanimation was using 50% or more of the CPU and a large part of main memory). (The new upscaled half-resolution boot animation won't look nearly as pretty, but I think that's a small price to pay for reducing bootanimation CPU usage 90% or more.)
[Nook Color Android Development] bigbob23:
I wondered about that. Is the patched version the one with ALT in the file name?
[Nook Color Android Development] highnoteuser:
Thanks for the reply. I'm not a dev, so I don't understand how this would save disk space on an install that does not install these two apps. I do make custom GAPPS packages and, like most, put GoogleHome in system/app. This causes it not to work in all GAPPS that use that structure (most) and in some cases, when a command to remove Launcher3 is in place it will cause the system to hang after doing the CM Account setup.

I came up with a workaround by having the GAPPS updater-script delete your GoogleHome.apk before installing the functioning one, but most other GAPPS are not setup that way and wont work.

I would suggest that line of code be removed so more of the popular GAPPS packages will work with our Nook.

Thanks again for an awesome ROM, it runs so much better than 10.2 for me!

*Edit: I understand how this could help for apps available in the play store that can be installed to data, but GoogleHome is not one of those apps.
[Nook Color Android Development] CyanoLou:
Yes, The download file seems to be the right size. But is says bad file and kicks out and fails on install, like it can't find the file on the sd card (even though I navigated to it). I have been dirty flashing (Cache + Dalik). Is a clean install required for M12 onwards? Any help is appreciated.

** I downloaded from a computer to external microSD, reinserted the card into the nook color. The file was found and flashed (latest nightly).
[Nook Color Android Development] bowguy:
See

http://xdaforums.com/showpost.php?p=56782698&postcount=690
[Nook Color Android Development] Henk Poley:
The "Reboot and Install" option appears to point to the file being on "sdcard0". While the cmupdater directory is on "sdcard1". This give an error on the automatic installation through CWM recovery. If you pick the zip file by hand it will work fine.

Might want to fix that :)
[Nook Color Android Development] Henk Poley:
On latest CM11 (with the above kernel) I get "Unfortunately, the process com.android.systemui has stopped" when I start in Safe Mode.

Might be totally unsupported on the Encore for some reason, but odd that a feature that's supposed to run with less problems is causing problems.

Kernel with the new memory clock settings does not run stable at 1200MHz for me. Never ran very well at that speed anyways.
[Nook Color Android Development] Henk Poley:
Also, the screen still (:P) periodically flashes when in standby. It's very short, you might not notice it. Did that on CM7.2 already.