Please limit this thread to development comments and questions!
The users thread is for all other posts.
When in doubt, post in the users thread.
After many long nights of banging our heads against keyboard, the CM7 port is finally shaping up.
In addition to nightly releases, we may from time to time be releasing test builds here for your feedback and enjoyment. If you find issues please feel free to post here in this thread. Leave all other feedback for the user thread.
Where to get progress news:
I will tweet progress from time to time.
Twitter: @dalingrin
We are usually in #nookie on freenode.
You can always check the Cyanogen [email protected] http://github.com/cyanogenmod
Current Issues
DO NOT FORMAT YOUR SD CARD IN CM7. DUE TO A VOLD ISSUE THIS WILL FORMAT YOUR /BOOT INSTEAD OF THE SD CARD!
****Should be fixed in nightly 13****
-Standy battery life is not as good as stock
Because of a kernel bug CM7 does not fully sleep. The result
is ~1% battery drain per hour while the screen is off. With normal use I usually go
1 - 2 days between charging.
***fixed in 2.6.32 builds***
-A few apps do not scale to full screen
In order to get Market and Maps to work fully the lcddensity has to be
set to something other than 160 causing a few apps not to scale properly.
-Wifi slow to reconnect at times
****fixed****
-Video playback is slow
****fixed****
-Default rotary lockscreen does not fit screen
****fixed****
-Market partially works
****fixed****
-Bluetooth does not work
****Update**** Bluetooth now works in CM7.
Bluetooth is working seemingly perfect except for the range. Unfortunately, the range is terrible.
Depending on the device you are paried with, the range is between 1-5ft. Any ideas on how to
fix the range issue would be much appreciated.
-Do not use SetCPU profiles
If you enable SetCPU profiles it will become a runaway process eating 100% cpu.
Setting your cpu clock can be done in Cyanogenmod Settings. Under Performance->CPU Settings
-Internal storage partition is not mounted on boot and is not shareable via USB
****fixed****
Download and Install
MUST USE 3.0.1.0+ RECOVERY:
This is installable ONLY with an ext4 aware Clockwork Mod Recovery.
*** Also it is critical to be aware that installing CM7 will write to the internal emmc of your device. You are advised NOT to try it. But if you choose to do so, understand you do so entirely at your own risk. Read sections 15-17 of the GPL for the gist of this disclaimer. There is no warranty or claim of usefulness or fitness for any particular purpose. No one but you shall accepts responsibility for what may happen if you download or try to use this development software. ***
Download for CM7:
Nightlies:
http://mirror.teamdouche.net/?device=encore
Install instructions:
http://forum.xda-developers.com/showpost.php?p=11452450&postcount=19
Post Reserved.
Developer Tips
(Standard do-at-your-own-risk-and-responsibility disclaimers apply.)
* For those developers building from source:
In $OUT, you'll find a few files:
recovery.img --> rename to uRecRam
kernel --> rename to uRecImg
Now you've got the ext4 clockworkmod for mmc built from source.
* Also, there's also a script in $OUT called:
sd_ramdisk_packer.sh
Assuming this works, it should repack your $OUT/root (mmc ramdisk) into a uRamdisk that can be used with a bootable SDcard. The stuff in /system would go in the /system partition of the SD card (p2).
The result: a bootable CM7 on SD. It may not be wise to distribute as Cyanogenmod for encore is a fast-moving target-- unless you plan to create a new one every day or something.
* If you don't like the buttons at the top for some reason, there's the SoftKeys app as well as Button Savior.
* There is a slightly-themed u-boot.bin in device/bn/encore/prebuilt/boot/. It is simply a recompiled u-boot from BN's source.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Info about emmc geometry
If your emmc is hosed and you want to start COMPLETELY from scratch, understand that the underlying geometry (before any partitions are created) of your emmc must be set up correctly on OMAP machines such as the nook before any partitions are created.
You can read more about that stuff here. If you are booted into an "emergency" SD card and have a totally hosed emmc, you can use fdisk to format /dev/block/mmcblk0 to the correct geometry, and then create the partitions one at a time, with a vfat partition as your /boot partition (p1). Then put mlo, u-boot.bin, uImage, uRamdisk, uRecImg, and uRecRam in /boot (p1) and you should have a bootable system.
Read the link above about SD/MMC formatting for OMAP3. Your nook is an OMAP3621, so you gotta get that geometry right, otherwise it won't boot. Luckily, the instructions on using fdisk are pretty good.
More info:
your emmc: /dev/block/mmcblk0
your sd: /dev/block/mmcblk1
Partition Info
the partitions you should have created are at:
/dev/block/mmcblk0p1 == /boot
/dev/block/mmcblk0p5 == /system
etc
/boot, /rom, and /media are of type "vfat"
/system, /data, and /cache are of type "ext4"
/factory (p3) isn't used by cm7
partition 4 is just there to allow you to create partitions 5-8
Sample instructions for copying files from cm7 update.zip on local computer to emmc /boot
You should be able to copy those four files simply by getting the lastest cm7, unzipping it on your computer, then once you boot into your bootable SD card, do:
Code:
COMPUTER> adb shell
# mkdir /data/bootmountpoint
# mkdir /data/systemmountpoint
# mount /dev/block/mmcblk0p1 /data/bootmountpoint
# mount /dev/block/mmcblk0p5 /data/systemmountpoint
# exit
COMPUTER> adb push mlo /data/bootmountpoint/
COMPUTER> adb push u-boot.bin /data/bootmountpoint/
COMPUTER> adb push uImage /data/bootmountpoint/
COMPUTER> adb push uRamdisk /data/bootmountoint/
COMPUTER> adb push my/path/to/sdcard/system /data/systemmountpoint/
Man, everyone makes better (prettier) release threads than I do.
oups, to delete
I can mount SD card find from my PC on Ubuntu.
Some apps don't show up on search, only one worth noting right now is Dolphin browser. I can find all kinds of add-ons, but not the app itself.
The lockscreen defaulted to the slider, but when I rebooted it went back to rotary. I went to settings and changed it back to slider.
Edit: Also to note is when I first launch the market, I get a force close on search function unless I use menu->search first. Will try fix permissions. Edit: fix permissions doesn't work, I must use menu->search the first time.
Edit 2: Beautiful Widgets shows up in market but says it isn't there when I try to install.
I had no trouble mounting SD to my PC (windows 7 64). I don't remember which now, but many apps showed in market, allowed me to install, but when I tried to 'open' from their market page I was told they weren't there - just opening my app drawer showed them and they worked fine. Something in market for that one.
screen on/off notification
is the screen on/off setting working?
I've also been able to mount to sd via Ubuntu and OS X.
Is there any way to get/use the recovery without using a burn to SD method?
going to try it out now... thanks dalingrin
i notice the file name is the same as the first test release. hopefully i have the right file.
-edit-
so yes i did have the correct file. lockscreen fix works and am still able to change it to rotary although it 'appears' to be set on rotary already.
market works... so far i have not found anything missing.
i have not been able to connect to usb. first connect got me a failed driver install and i don't see any usb mounting option in settings. -edit- just tried again and now it works? probably a windows thing.
dalingrin said:
Fixes that need testing
-USB storage mounting
We need folks to test mounting your sd card from within CM7 onto your computers.
-Market Access
This build contains a partial fix for Android market filters. I don't expect all apps to be available yet but I'm not sure what is and not available in the current build.
-Default lockscreen
I have submitted a patch upstream to change the default lockscreen from rotary to the traditional slider. This is because the rotary lockscreen does not scale for the nook. This patch required changing some mechanics in CM and needs testing. In particular, it needs to be verified that the initial lockscreen is the traditional slider but can still be changed in Cyanogenmod Settings.
Click to expand...
Click to collapse
zpure awesomeness! I can't wait for the bugs to get ironed out
here is a problem I have noticed. When I try to buy and app I get a force close and I cannot purchase an app.
UPDATE: I installed the newest market 2.3.2 and it does the same thing. I did the wipe cache, force stop on market and framework services, rebooted and still cannot purchase apps. Gotta be something in the build that is causing it to stop. I can download free apps just fine and the apps I already purchased.
jkurl said:
here is a problem I have noticed. When I try to buy and app I get a force close and I cannot purchase an app.
Click to expand...
Click to collapse
just checked this and i get force closes as well.
It's a beautiful thing. Thanks for the great work, guys!
I flashed the update from the original version that thecubed released and can report the following market bugs:
Astrid, Facebook, and Flixster do not show up in the market.
In the market, clicking on All Games / Top Free leads to a loading circle that never completes (no results ever get shown).
So there seem to be 2 different RC1s (both called the same thing) plus a single nightly. Which one should we be testing?
No maps, Facebook, or pulse in market running release from this thread
FletchF said:
So there seem to be 2 different RC1s (both called the same thing) plus a single nightly. Which one should we be testing?
Click to expand...
Click to collapse
OK, I gather it went like this:
old RC1->first nightly->this newer RC1
so, test the RC1 from this thread until newer nightlys start to appear.
These are the only apps I use I can't see in the market:
imdb
minimalistic text
google maps and street view
simi clock
wolframalpha
speedtest.net
I tried adb pushing all of them but wolfram from my htc desire. Imdb, minimalistic text and simi clock work, speedtest and google maps force close.
I also pushed Cyanbread.apk to /system/app and selected it from theme manager, it also seems to work great.
In the market, clicking on All Games / Top Free leads to a loading circle that never completes (no results ever get shown).
Click to expand...
Click to collapse
That only happens sometimes for me. Most of the times it works without problems.
(edit) Oh, and mounting the sd card also works ok.
Related
####NO LONGER SUPPORTED####
Links have been updated to the last release and are working
###############################
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The NookBuntu Dev Team
devastatorx | penkia | lincore | munday | luciferii
CREDITS: munday for his initial work on this project, penkia for the wifi and touchscreen fixes. The guys who pulled off the vnc trick to get us thinking about how to make this a full fledged linux tablet. All the great developers for the nook and every other device.
*DISCLAIMER*
I'm not responsible, blah blah blah...if you are trying this...your warranty cherry was popped long ago
Q & A - This area will be updated as questions arise
Q: Why the skip from alpha 0.1 to beta 0.3?
A: Alot of testing and fixes were implemented behind the scenes. These images were not released due to usability issues. We wanted this release to be one that could serve as a daily build. And this comes relatively close.
Q: Will this mess up my current configuration?
A: If your current configuration runs from the eMMC, then no. It runs solely from the uSD card. As long as you don't mount your eMMC inside NookBuntu and start messing around with it, it should be fine.
Q: Is this awesome?
A: Yes, it is so awesome that if I were to speak anymore than a few lines about it's awesomeness, computers would become self aware, sheep would begin counting people, and pong would turn into tetris...
Q: Will this run from the internal memory?
A: This is being planned for a future release and currently only runs from the SD card. DO NOT FLASH IT TO THE eMMC!!!
A NOTE ABOUT DONATIONS - Please read
No we do not ask for donations or accept them. We do this because we are as passionate as anyone in this communtiy about the tech we use.
If you would like to donate, please instead consider donating to the following charity
The National Breast Cancer Foundation - https://www.nationalbreastcancer.org/donate/
My sister was recently diagnosed with stage 3 breast cancer. I ask that if you do wish to donate, please do so in her honor. If you wish to make a donation in her honor please pm me for details (name and whatnot). Thank you!
################################
NookBuntu Beta 0.3
################################
Screens
Working
Boot into NookBuntu when the device is powered on (no adb necessary!)
Network manager - this is still being worked on, use the method listed in the instructions below
Touch screen
On screen keyboard auto slide out on text input area focus
Audio
Not Working
Home button
Volume buttons
Multi-touch
Bluetooth
Hardware acceleration
Accelerometer
Charging
Installation instructions
DOWNLOADS
NookBuntu Beta 0.3 - Download
md5: bfe2206fbfd7f402cd1c95c61b13dc83
NookBuntu Boot Partition - Download
md5: 316f8d6d44cb3d2c4a13f01da63c302e
We will need to make a bootable SD card for this. As of right now I have an 8gb card and will be uploading a burnable image soon...but for now this method will work.
Download this script and save it somewhere you have easy access to.
Download: SDMAKER
Ok so you have all the files right? Right?? ...right
Let's get that SD card prep'd for our NookBuntu installation.
1) Open up a terminal and cd to where you saved the file sdmaker.sh
2) Insert your soon to be nookbuntu sd card into your pc and find out where your sd card is mounted i.e. /dev/mmcblk0 or wherever. REMEMBER what it was (for me it is /dev/mmcblk0)
3) Type the following command hitting enter after each line
Code:
sudo chmod +x sdmaker.sh
sudo ./sdmaker.sh /dev/yoursdcard
4) Let this command run and finish out, it is formatting your sd card to correctly have a boot and filesystem partitions
5) Once this has finished you should have two new partitions show up, either mounted already at /media/boot and /media/Angstrom or should be able to mount the new partitions in your file manager. If they aren't mounted go ahead and mount them.
Let's regather. You have two folders open on your desktop, one titled "boot" and the other titled "Angstrom". Are you with me? Good.
6) Untar/7zip/Unzip whatever...decompress the file nookbuntu-0.3beta.tgz anywhere you would like.
7) cd to the directory where you extracted the files. There should be a folder titled "system" Go ahead and cd into that directory.
8) Now we need to copy all of the contents to the Angstrom partition on your SD card
Code:
sudo cp -r * /media/Angstrom
This will take awhile, get something to drink.
9) After that has finished lets copy over the boot partition. Go to where you downloaded the file "nookbuntu-boot.7z" and extract it. Now CD to nookbuntu-boot. Are you with me? Let's copy those files over!
Code:
sudo cp -r * /media/boot
10) After that has finished we need to setup your wifi so it will work. So let's edit the one of the files we just put on your sdcard (use whatever text editor you would like:
Code:
sudo gedit /media/Angstrom/etc/wifi/w2.conf
In your text editor you will have something like this:
Code:
ctrl_interface=/var/run/wpa_supplicant
network={
ssid="WiFiNetworkName"
scan_ssid=1
key_mgmt=WPA-PSK
psk="yourWPAkey"
}
We need to change a few things to be able to connect to your home wifi.
Change the following:
Code:
ssid="WifiNetworkName"
to
ssid="YourSSID"
Obviously replace "YourSSID" with whatever your actual SSID is.
Chances are you are using WPA encryption...well if you aren't...you should be. Assuming you are we need to set up so we can send the key to the router when we connect.
See this line?
Code:
psk="yourWPAkey"
Change "yourWPAkey" to...you guessed it....your WPA password
Save the changes and exit.
11) Unmount the sdcard from your computer
Code:
sudo umount /media/boot
sudo umount /media/Angstrom
12) Take the Sd card and put it in your nook while it is powered off.
13) Power on your nook and give it a few mins...voila! NookBuntu should have loaded!
These next steps are for getting wifi up and running you can do this from an ADB shell or from the terminal inside NookBuntu or make it into a script for future use.
Enter these commands (hitting enter after each line unless otherwise noted)
Code:
killall wpasupplicant
ifconfig tiwlan0 up
killall connmand
wpa_supplicant -Dwext -i tiwlan0 -c /etc/wifi/w2.conf & dhclient
You should shortly be associated to your home network!
Enjoy NookBuntu! Make sure to thank all the great devs who have a hand in this project!
-devastatorx
Change log
Beta 0.3
Network Manager (semi working at the moment, should be fixed in next release) - penkia
Audio Working - devastatorx
On screen keyboard when focusing on a text input area - penkia
Boot into X when the device is powered on - Lincore
New base image - devastatorx & penkia
**reserved too
Wow, going to bed tonight, but I am definitely trying this tomorrow, I hope this is inevitably usable on the nook color, that steps up it's usability as a tablet.
Just a suggestion for the Mods, we should have a second forum for ubuntu on the Nook, that way it doesn't clutter up the android development and then it can expand and be organized for developers of linux vs android, might draw some more interest into this!
Honestly can't wait to try this though, good work
Holy ****, it finally happened. Downloading now!
It's gonna be a loooong day at work today of not doing any work and messin' with my nook!
Thanks for this!
Racks
I'm going to wait a bit before giving this a shot, but seriously, thanks! I'm excited about the possibilities. Do you think our hardware will be prohibitive to using this in the long-run? I know it's really early, so if that's a silly question, feel free to disregard it.
junkrobot said:
I'm going to wait a bit before giving this a shot, but seriously, thanks! I'm excited about the possibilities. Do you think our hardware will be prohibitive to using this in the long-run? I know it's really early, so if that's a silly question, feel free to disregard it.
Click to expand...
Click to collapse
At this stage it is difficult to say as not everything is working (no hardware acceleration, sound, etc)
As of right now the device runs pretty smoothly for what it is and is more responsive than it was when using the vnc method. I will be working more on the build this weekend and hope to establish a development team to keep things moving forward with consistant fixes and updates.
With a good, dedicated development team we should make some exciting progress in the near future.
Sent from my PC36100 using XDA App
I think it'll be good to note what's not working on the initial post, that way if a dev wants to help, at least they know what to look for and try to solve
racks11479 said:
It's gonna be a loooong day at work today of not doing any work and messin' with my nook!
Thanks for this!
Racks
Click to expand...
Click to collapse
I thought I was the only playing with my nook at work, now I don't feel so bad. haha.
@devastatorx, you are the man!!! Thanks so much, I can't wait to try this out.
So this is actually an Angstrom distro?
bassrebel said:
I think it'll be good to note what's not working on the initial post, that way if a dev wants to help, at least they know what to look for and try to solve
Click to expand...
Click to collapse
I will update the OP. I just wrote it last night at about. 12:30am and then let the file upload over night and hit post on my way out the door this morning. So it was a little rushed.
Sent from my PC36100 using XDA App
starkruzr said:
So this is actually an Angstrom distro?
Click to expand...
Click to collapse
Negative. This is a ububtu installation. The script just names that partition "Angstrom".
Sent from my PC36100 using XDA App
Ubuntu 10 or 11? Unity would be most worthwhile for our devices . And bugger all, I guess I'm going to have to pick a new microSD.
Ubuntu 10. As of right now there are some path issues so I am unable to get the unity-2d gui to load. Will have this fixed in the next release.
Sent from my PC36100 using XDA App
Ophbalance said:
Ubuntu 10 or 11? Unity would be most worthwhile for our devices . And bugger all, I guess I'm going to have to pick a new microSD.
Click to expand...
Click to collapse
Unity would be rather nice. Especially if we can get GPU acceleration working.
Perhaps this is a silly question, but... have you given any thought to packaging updates in some form that doesn't require downloading the entire distribution again? Yes, I can see there being issues if you don't apply them sequentially if it comes out in a zip of some kind... but it'd save you/us a ton of bandwidth. Maybe if it's all in SVN or GIT?
I'm stuck here:
Code:
sudo cp -r * /media/boot
It says "/media/boot" is no directory
MAD PROPS keep up the good work this is what android is all about might have to buy another nook color one to install in the car and one to use every where else .
Arbelzapf said:
I'm stuck here:
Code:
sudo cp -r * /media/boot
It says "/media/boot" is no directory
Click to expand...
Click to collapse
What OS are you using? The drive may be mounted elsewhere and my instructions are based off of the drives first partition being mounted at "/media/boot" and the second partition mounted at "/media/Angstrom". If this is not where the partitions are mounted then adjust the instructions for where you have them mounted or remount the device's partitions to these folders.
This should help...but I'm not saying this to be a jerk or anything...this is an Alpha and is in no way intended for daily use. Only those comfortable in Linux, and feeling adventurous should give this a go. Future releases (beta and onward) should be stable enough and easy enough to install for daily use.
To address the updates question:
I may implement a kind of crude package system after I get to a stable enough release to call it a beta. Such packages will include the modified system files and an install script to set the new update up. But like I said, that probably won't be until beta.
Say hi to "CyanoBoot" -- a 2nd bootloader/w menu aka "ub2" - (WIP)
“CyanoBoot”
(aka a "second bootloader")
Quick Guide
by fattire
(@fat__tire on Twitter)
Alpha 0: "I don't have a NT" Edition
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(Thanks to indirect for the image.)
What is CyanoBoot?
CyanoBoot (working title) is a “second bootloader” in early development, which is based on the open-source “u-boot” project, as further customized by BN & Bauwks. It is similar to the bootloader provided by Bauwks but has additional enhancements to make booting unsigned partitions easier and to generally enhance the booting experience on the Nook Tablet (aka “acclaim”) device.
CyanoBoot is intended for use with the forthcoming CyanogenMod 9, but it can also be used to boot CM7 or Ubuntu Linux or even the stock firmware (provided of course you are not legally or contractually bound from doing so. I haven’t read or agreed to any BN user agreements, so can’t speak to this.)
CyanoBoot includes an on-screen menu system, the ability to boot into three basic modes (normal, recovery, and “altboot”), configuration options, fastboot, and more.
The same version of CyanoBoot should start from both SD card and emmc (although it must be packaged and installed differently for each.) It should work on both the 1gb and 512mb RAM models. NOTE: It has been reported that some devices may require a USB cable to be plugged in to boot from SD Card. If true, this issue is not understood and is not addressed, nor is it likely to be.
NOTICE: CYANOBOOT (WORKING TITLE) IS HIGHLY EXPERIMENTAL AND IS NOT INTENDED TO BE USED BY NON-DEVELOPERS AND/OR THOSE UNWILLING TO ACCEPT FULL RESPONSIBILITY FOR ANY UNTOWARD CONSEQUENCES OF USING (OR ATTEMPTING TO USE) THE SOFTWARE. ALL SUCH ACTIVITY MUST OCCUR *ENTIRELY AT YOUR OWN RISK* AND YOU ACCEPT ALL CONSEQUENCES FOR DOING SO. THE USE OR ATTEMPTED USE MAY HAVE UNINTENDED RESULTS, INCLUDING BUT NOT LIMITED TO LOSS OF DATA, DAMAGE TO HARDWARE, AND/OR EXPLOSIVE DIARRHEA. CYANOBOOT IS NOT ENDORSED, AFFILIATED, SPONSORED, NOR ASSOCIATED WITH THE "DAS U-BOOT" PROJECT, GOOGLE, BARNES AND NOBLE LLC, TEXAS INSTRUMENTS, DENX., NOR ANY OF THEIR PARTNERS, OWNERS, EMPLOYERS, AFFILIATES, CLIENTS, SUBCONTRACTORS, OFFICERS, DIRECTORS, ADMINSTRATORS, INFORMATION PROVIDERS, ETC. EXCEPT INSOFAR AS THEY HAVE PROVIDED AND LICENSED SOURCE CODE TO BE FURTHER MODIFIED AND DISTRIBUTED. SEE THE RELEVANT GNU PUBLIC LICENSE FOR LICENSING DETAILS AND OTHER DISCLAIMERS. THIS SOFTWARE IS OBVIOUSLY INTENDED FOR USE ONLY BY THOSE WHO ARE AUTHORIZED TO DO SO.
Whew!
LIST OF THINGS
Started with “UB1” (aka u-boot, “first boot”) source code
Includes changes to support new 512MB model
Includes Bauwks’ repairs to fix “locked bootloader” malware
Many duplicate UB1 functions removed
One-build-boots-all (emmc or SD card, custom OS or stock)
Boot device indicator (top-left corner)
Bootcount indicator (top-left corner)
On-screen feedback to let you know what it’s loading.
Console-based boot menu
Support for key-combo shortcuts for menu/recovery
Alternate “Altboot” multiboot support allows 2nd OS.
Emmc setting for default boot profile (normal/altboot)
Emmc setting for default boot device (emmc or sd)
Emmc setting for automatic bootcount clearing
Boot fallback for stock firmware (0 bytes + sec. header)
Boot fallback for bauwks’ uboot (256 bytes)
Numerous visual enhancements
Unused bulky images removed (smaller file)
FASTBOOT support (w/menu selection)
On-screen build timestamp so you know version
Perhaps much more, or maybe not
There are likely bugs all over the place, but this is how it's supposed to work:
Key Shortcuts
Hold down home (“n”) key for the menu.
Hold down home (“n”) + “power” to have UB1 start recovery. If UB2 is also installed, it should respect this key combo and continue to load recovery.
The default behavior if no keys are pressed is to boot “normally”-- if booting from emmc, the boot partition (p4) from emmc will be booted. If booting from SD the boot.img on SD file will be booted.
The Boot Menu
Use the Home (“n”) key to navigate through the menu options. You can select an option with the power key.
The option you choose will override any other configuration you have made.
NOTE: Just so you don’t ask-- the reason the home and power keys are used to navigate through the menu rather than the volume up and down keys is due to a required driver not being included with u-boot 1. While the home and power keys use a very simple “gpio” method to detect if they are pressed, the volume keys are more like keyboard keys and thus are more difficult to detect. (The Nook Color bootloader, in contrast, did have the appropriate driver, so volume key detection was possible.)
Boot Indicators
Since you can boot from either SD or EMMC, it may be difficult to ascertain which version you are starting from.
Never again. You can now see whether you have loaded CyanoBoot from EMMC or SD by lookin at the top left corner:
“E” -> CyanoBoot is starting from emmc
“S” -> CyanoBoot is starting from SDCard
The # that follows this indicator is the current “bootcount”. After 8 unsuccessful boots or so, stock behavior is to run recovery with a reflash instruction. See below for instructions on clearing the bootcount at every boot automatically.
Fastboot (used for development)
For those familiar with “fastboot”, you can select the fastboot option from the CyanoBoot menu to go into fastboot mode. You can then (hopefully) flash to the boot or recovery partitions via USB cable using a command such as:
$ fastboot flash boot boot.img
Installation (SD Card boot)
(If you are preparing your own SD card for booting, you should be aware that for OMAP devices such as the acclaim, the SDcard must be formatted using a very specific configuration, which is detailed elsewhere.)
For SD Card, CyanoBoot is packaged inside a “flashing_boot.img” file to be placed in the first vfat partition of the SD-card along with the signed “mlo” and “u-boot.bin” files from the 1.4.2 update.zip.
(I'm told the mlo file may be called called MLO_es2.3_BN in the BN update.zip and should be renamed to “mlo”.)
Next, the boot (“boot.img”), recovery (“recovery.img”) and/or alternate boot (“altboot.img”) image files may optionally be placed in this partition.
Installation (EMMC boot)
To boot from emmc, the “flashing_boot_emmc.img” file, which contains a packaged version of CyanoBoot, should be put at byte 0 of the third partition (recovery) and ALSO at byte 0 of the fourth partition (boot). Then, the boot/recovery partitions must be shifted “to the right” (to make room for Cyanoboot) so that it starts 512Kb in from the start of the file. Use a padding of zeros so that the boot image contents begin exactly at 512Kb.
The boot and recovery partitions are expected to use this offset. For the alternate boot from emmc, the “altboot.img” may be the identical file used in an SD-boot, placed into the /bootdata vfat partition without any offset.
NOTE: Again, use the flashing_boot_emmc.img file for emmc boot partitions, *not* flashing_boot.img, which is for SD card boot.
Offset Info
Again, when used on the emmc, CyanoBoot must be placed at byte 0, at both the boot and recovery partitions. The “actual” boot.img and recovery.img that would normally be at byte 0 of those partitions should be moved so that it starts 512Kb in.
Always use this offset in recovery (p3) and boot (p4) partitions. In other words, put CyanoBoot at offset 0 and then pad with zeros, then put the normal boot.img or recovery.img at offset 512.)
On SD Card, the “boot.img” and “recovery.img” files should have no padding or offset or anything. Use as normal. This is similar to how “uImage” and “uRamdisk” files are used on the NookColor, only use a single file for both with a header in front.
Installation Summary
One more time. Here are the locations for the boot images:
SDCARD
(p1-vfat)/boot.img file (no offset/padding)
(p1-vfat)/recovery.img file (no offset/padding)
(p1-vfat)/altboot.img file (no offset/padding)
EMMC
(p4-/boot partition)<- CyanoBoot at byte 0, boot.img contents at 512.
(p3-/recovery partition)<- CyanoBoot at byte 0, recovery.img contents at 512.
(p6-vfat)/bootdata/altboot.img (no offset/padding, same as SDCard)
Configuration
You can control the "default boot" behavior (ie, what happens when you don’t hold down any keys). If you are a developer that does not want to constantly clear the bootcnt, you can also cause CyanoBoot to clear the bootcount automatically at every boot. To do this, three configuration files may be added to /bootdata (partition 6) on the emmc.
CONFIG #1: BOOT DEVICE
This will cause CyanoBoot to always boot from the emmc boot partition rather than SD. In this way, you can boot “through” a bootable SD card to whatever is on the emmc.
To Make Default Always Boot To EMMC
$ echo -n “1” > /bootdata/u-boot.device
CONFIG #2: ALTBOOT
Aside from the normal boot and recovery boot, a third boot option is available, called “altboot” (alternate boot). This is a kernel/ramdisk pair that can be used for a third firmware, an overclocked kernel, or whatever you like. If you choose the “altboot” as a default and it does not exist, your boot will fail.
As discussed above, the altboot.img file goes in the following location:
SDCard: file on p1 called “altboot.img” (no special padding or offset)
EMMC: file at /bootdata/altboot.img (no special padding or offset)
To Make Default Always Boot to “altboot”
echo -n “1” > /bootdata/u-boot.altboot
CONFIG #3: CLEAR BOOTCOUNT -- You can automatically zero out the bootcount with every boot. To set this:
To Make Default Automatically Clear BootCount
echo -n “1” > /bootdata/u-boot.clearbc
NOTE: A version of “Nook Tablet Tweaks” is planned to automate the above options much as Nook Color Tweaks does for the encore device in CM7.
Thanks/Credits
Thanks to chrmhoffman, nemith, xindirect, Celtic, and loglud for testing, as I don’t have a device and have never actually run this. Thanks to j4mm3r for the first encore menu code. It was pretty much rewritten for acclaim, but the first menu was invaluable in showing me how to add the code for the console. Thx to pokey9000 for stuff that helped get fastboot working.
Also thanks to BN as well as all the talented u-boot developers at Denx and elsewhere for the GPL’d code upon which this was based.
http://www.denx.de/wiki/U-Boot is where you can find the main u-boot project.
Also, a huge thanks to Bauwks for his code contribution as well as for making this possible in the first place!
Remember, this is all experimental. I'll try to update this post if there's something that needs to be updated.
(source)
If you have an issue, be sure to mention the timestamp at the bottom so everyone knows which version you're using. There will be bugs.
reserved for future expansion
Awesome
Hi,
Congratulations fattire. This is amazing work.
It boots the CM9 nicely.
Rgds,
Chris
I just gotta say, I laughed pretty hard when I read: Alpha 0: "I don't have a NT" Edition
Thanks
Wow
wow wow and we can use fastboot on the nook Tablet too? awesome
~ Veronica
Yep.
Works fine. Sometimes I have to re plug device though. But it speeds up things incredibly.
Chris
lavero.burgos said:
wow wow and we can use fastboot on the nook Tablet too? awesome
~ Veronica
Click to expand...
Click to collapse
Sent from my GT-I9000 using XDA App
Great work! Especially thanks for mentioning GPL software and folks behind it - that's thanks to them Android, Nook, Kindle, and even this bootloader were at all possible. So, where's source for the changes you made to this GPL software? Thanks again.
It's in the same directory. I'm going to make it a little clearer in the OP and I think maybe better organize the link to be in a subdirectory. So heads up that the links will change... ...changed.
fattire,
This looks great! Is it extensible to other devices like CWM recovery? I'd love to see this on the Transformer/Prime. Ubuntu on those devices replaces recovery, so it would be great to have a 2nd bootloader to get past these limitations. Also, it would be cool to see CyanoBoot on other devices like the NC and Touchpad. The TP has moboot but I think there's something to be said for consistency in this area.
Awesome work!
-mm
Yes, it'll work with CWM, TWRP2, or any other recovery. That's the point
Looks like the prime is a tegra3-based system. I don't know much about the bootloaders for Nvidia machines-- the nice thing about OMAP3/4 from Texas Instruments is that the u-boot bootloader works great, and is open source so you can extend it and stuff. While the bootloader for transformer is now unlockable I don't know that they give you the source, do they?
That said, from CM on the Qualcomm-based touchpad I know that a similar 2nd-level boot menu can be added AFTER the bootloader. Take a look at
the excellent moboot (lead developer is jcsullins) for an idea of how to add a very flexible menu that slips between the bootloader and the kernel. You can see it in action on youtube-- just look for any TouchPad cm7 or cm9 video where it boots up and you can select between CyanogenMod, WebOS, or one of the recovery images.
Hope that helps!
Mistar Muffin said:
fattire,
This looks great! Is it extensible to other devices like CWM recovery? I'd love to see this on the Transformer/Prime. Ubuntu on those devices replaces recovery, so it would be great to have a 2nd bootloader to get past these limitations. Also, it would be cool to see CyanoBoot on other devices like the NC and Touchpad. The TP has moboot but I think there's something to be said for consistency in this area.
Awesome work!
-mm
Click to expand...
Click to collapse
fattire said:
Yes, it'll work with CWM, TWRP2, or any other recovery. That's the point
Click to expand...
Click to collapse
Sorry, I was trying to ask if CyanoBoot would be available on multiple devices the same way CWM is. I understand it allows the booting of recovery images. What I did not realize was that uboot was tied to the TI OMAP platform, so you're answer was very helpful. Thank you!
Gonna be honest, I'm pretty sure this is for flashing roms such as how cwm allowed me to install cm7-teamb but I'm not sure. Also I saw someone say it flashes cm9? Sorry I'm just trying to get a feel at what this would really be used for, no offense intended.
fattire said:
It's in the same directory. I'm going to make it a little clearer in the OP and I think maybe better organize the link to be in a subdirectory. So heads up that the links will change... ...changed.
Click to expand...
Click to collapse
Thanks! Why not push it to github? (At least I had a look thru your repos on github yesterday and didn't see anything related, sorry if I missed something.)
Thanks for the awesome work fattire.
Here are the problems I found:
I manage to include cynoboot in recovery & boot but then there's device no found error using adb. Am I missing some drivers? (I am using WinXP)
because of that fastboot is not working too.
and then once enter fastboot mode. I can't get out unless I power off (n button can't navigate)
Hi,
you can use "fastboot reboot" to reboot the device. I didn't have an adb problem. Are you saying you try to adb into the device when in the menu? This doesn't work as there is no android running. I guess on windows you have to install android SDK first to get the drivers.
Rgds,
Chris
chrmhoffmann said:
Hi,
you can use "fastboot reboot" to reboot the device. I didn't have an adb problem. Are you saying you try to adb into the device when in the menu? This doesn't work as there is no android running. I guess on windows you have to install android SDK first to get the drivers.
Rgds,
Chris
Click to expand...
Click to collapse
I mean if I boot up the rom (I'm running MIUI) with the boot.img that includes cynoboot, then adb does not work (device not found). If I boot with the original boot.img, then no problem with adb
And fastboot command does not work for me either (I have android sdk installed)
I'll try the sdcard version later.
sungod88 said:
Gonna be honest, I'm pretty sure this is for flashing roms such as how cwm allowed me to install cm7-teamb but I'm not sure. Also I saw someone say it flashes cm9? Sorry I'm just trying to get a feel at what this would really be used for, no offense intended.
Click to expand...
Click to collapse
It's a bootloader
cobrato said:
I mean if I boot up the rom (I'm running MIUI) with the boot.img that includes cynoboot, then adb does not work (device not found). If I boot with the original boot.img, then no problem with adb
And fastboot command does not work for me either (I have android sdk installed)
I'll try the sdcard version later.
Click to expand...
Click to collapse
Are you using the 1.4.2 mlo and a 1.4.2 kernel?
fattire said:
Are you using the 1.4.2 mlo and a 1.4.2 kernel?
Click to expand...
Click to collapse
I'm using 1.40
Sent from my LT18i using Tapatalk
cobrato said:
I'm using 1.40
Sent from my LT18i using Tapatalk
Click to expand...
Click to collapse
cyanoboot is effectively a 1.4.2 u-boot.bin as far as handling the 512 model and all that goes. I don't konw that there were significant changes that would affect usb/adb, but jic you might want everything to match up...
Oh also, as far as fastboot goes... the device vendor_id was changed from 0x0451 to the google usb vendor id that most fastboots use which is 0x18d1. The device product_id is 0x0100.
Worked for chrmhoffman and others...
After a rage filled Google search, I've finally stuck oil with putting my 64GB UHS-1 card to use.
Thank Slig for a fine tool here, I've tried it with varying success.
I didn't get Shadowgun & some EA games to move properly, Gameloft & every other huge game I had: no problem.
Tested with Stock 3.15 JB 4.1.1 (Deodexed)
Do not know the results after a new ROM flash or Titanium whatnot. You tell me how it fairs.
Main thread & needed apk:
http://forum.xda-developers.com/showthread.php?p=20668905#post20668905
slig said:
Hi all !
This is my application to bind directories located on external_sd to directories on internal memory (/sdcard/). This way You can transfer large application data directories to external_sd. Could be usefull with ex.: games from Gameloft, other like Shadowgun, applications like CamScanner.
screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Features:
* Requires ROOT !
* Aimed at specific functionality and features (not idiot-proof)
* You can create any number of Data -> Target directory pairs, mount them manually or choose to mount them on system boot (checkbox does that).
* On/Off switch controls whole mount-on-boot function.
* Diskette icon indicates if mount operation was successful, by taping it You can mount/umount entry.
* Icon changes if application is using mounted entry
* DirectoryBind can tell what application is using this entry (tap at entry in use)
* Long tap on entry (disabled) brings edit/delete window
* App auto umount all entries on USB connected and remount after USB disconnected (for now via BroadcardReceiver UMS_CONNECTED / UMS_DISCONNECTED)
* App shows notification and vibrates if auto umount on USB fails
* If mounting all checked entries (ex. on boot) app is waiting specified time (def. 60 sec) if data directory is not available (happens sometimes at boot)
* Tested sucessfully with Asphalt 6, Shadowgun, DeadSpace, CamScanner
Color statuses:
* GRAY - entry disabled
* RED - mount failed
* BLUE - waiting for data availability
* GREEN - mounted OK
version 0.2.0k
* fixed FC if screen orientation changes during copy/delete
* more extensive logging
version 0.2.0m
* ?? fixed problem with entries marked green on boot, but not mounted (repotred by stone_ship)
* ?? fixed problem with random FC on ICS (reported by Thomas)
version 0.2.0n
* auto create target directory action moved from "bind" action to "add/edit entry" action due to possible problems when data outside "/sdcard"
version 0.2.0o
* added option to control if mount service is run as sticky
*** for now older version kept in case I broke something ***
please do not test data transfer files features on sensitive data they seem to work OK but are not throughly tested
Compiled using API android 2.3.3. Attached as self-signed development apk package. No market link for now.
important info
* Remember ! All entries must be umounted before attempting to use MASS STORAGE MODE. Application will try to do it automatically on USB CONNECT. If it fails and You'll use MASS STORAGE MODE sdcard partition WILL CRASH and reboot will be required to restore normal operations ! Main cause of that is appplication using mounted folder. You have to close that application and retry to umount entry.
* This application requires *root privileges* so it has full control over entire system! Uses root privileges to invoke "mount", "umount", "lsof" and "grep" shell commands via su and it DOES NOT write anything on system partitions.
It DOES NOT apply any permanent changes to the OS, however I cannot guarantee it does not contain BUGS and security issues. I'm not responsible to any damage it can cause. Use it AT YOUT OWN RISK !
application permissions explained
WRITE_EXTERNAL_STORAGE - application automatically creates target path, copy existing files from target to data
RECEIVE_BOOT_COMPLETED - application can perform automatic bind on boot
VIBRATE - application creates notification alert with vibrations when cannot umount all locations on USB connect
READ_LOGS - dump own logcat to file
*ROOT* - invoking "mount", "umount", "lsof" and "grep" commands via su
BUGS REPORTING
As every program can contain bugs so this one too. I'm very grateful if someone find and report a bug. No report will go unattended and I'll look into each case. There is just one thing, often report even very detailed is not enough so application has built in logging (logcat) capability - it can be enabled in Preferences.
Logcat can be dumped to file from main app window: menu -> dump logcat to file
So when reporting bug please attach that file to Your post
Regards !
Slig
!!! IF YOU HAVE ISSUE WITH ENTRIES DISAPPEARING AFTER REBOOT !!!
1. In preferences check "alternate dbase mgmt" and try again
2. Report in this thread with informations
- does "alternate dbase mgmt" help ?
- are you using any taskkiller
- what ROM are you using
I need to know how many people have this issue, maybe it would be good to make "alternate dbase mgmt" default mechanism.
Sorry for that but I'm still learning and doing by best to make this app as much compatible and usable as possible. This is my first public app for android
Click to expand...
Click to collapse
Genjinaro said:
After a rage filled Google search, I've finally stuck oil with putting my 64GB UHS-1 card to use.
Thank Slig for a fine tool here, I've tried it with varying success.
I didn't get Shadowgun & some EA games to move properly, Gameloft & every other huge game I had: no problem.
Tested with Stock 3.15 JB 4.1.1 (Deodexed)
Do not know the results after a new ROM flash or Titanium whatnot. You tell me how it fairs.
Main thread & needed apk:
http://forum.xda-developers.com/showthread.php?p=20668905#post20668905
Click to expand...
Click to collapse
Can i use this for Sony Xperia Z Ultra???
cihuy039 said:
Can i use this for Sony Xperia Z Ultra???
Click to expand...
Click to collapse
In theory it should work, you just need to have root access for it to work.
DO THIS AT YOUR OWN RISK.
I AM NOT RESPONSIBLE IF YOU BRICKED YOUR DEVICE.
Do research and reading if you are uncertain about this rom.
Do not PM me about the ROM.
WHAT IS IT?
Xylon is fully transformed distribution for Android Devices. It is designed to take full advantage of the device’s hardware and to provide the user pure Android experience.
The team is constantly working on making things better for the users and is happy to do so. We, the team, believe that for one to experience the pure taste of Android, he/she should be provided with something which is fast, intuitive and fluid – That’s where we come in – To provide you that.
Xylon started as a part of the Fruits & Veggies (FNV) project, a community ROM for the Galaxy Nexus and is now set up individually but its roots are based on FNV. Remicks, the founder of the FNV – inspired Daniel MM (Daxmax, founder of Xylon) to build something that would make users love what they use. In Daniel’s words – “This is an FNV based ROM, not FNV. But it has the winds of FNV, and it has more spacious features around the Android world.”
-http://xylon.androidvenue.com/about
FEATURES:
Phone, Phablet, and Tablet UI
Customized Trebuchet Launcher
A lot of customization
Compiled with Google’s GCC 4.7 toolchain.
Linaro's compiler flags, O3 and Linaro string routine)
Kernel 3.0.66+
CWM 6.0.28
SuperSU
QUESTIONS AND ANSWERS
CHANGELOGS:
Look at XYAOSP source history for further changes, I will not post them.
02/27 – Repo synced, Initial build so there could be many bugs.
03/06 – Repo synced, kernel updated to 3.0.68 with new lowmemorykiller, font size increased a little in statusbar and Trebuchet, you can increase icon size to 120% in Trebuchet, gesture control in Trebuchet, new SuperUser (Koush's).
IMPORTANT NOTES: If you noticed null icons (no action icons) on the NavBar then you need to go to Settings > XY Tools > Navigation Bar > Menu (The vertical three dots) and Reset navbar icons/targets. For Navigation Ring to work, you need to clear data/data1 if you are on previous build.
TO DO LIST:
Lots of things
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
INSTRUCTIONS:
You need to do a full wipe (factory reset and wipe cache) if you are on a different ROM.
You need to wipe data1 and cache if you are SD booting.
You need to reinstall GAPPS after each ROM installation.
In the case you booted and all you see is black screen for a couple minutes, reboot to see if it's fix.
Initial booting can take several minutes.
Copy ROM/GAPPS into your Internal Storage on the device.
Reboot into recovery and install ROM from Internal Storage.
Full wipe can be done before or after installing ROM/GAPPS.
For SD booting, you need to make bootable SDCard first.
There are plenty of guides around.
INTERNAL ROM:
86b333d03739180e428e5cbb2cb9d706 *xylon_acclaim_2.1.1_06MAR2013_16_HD.zip
84ca9aeb88fad3ddcd127a216a34557a *xylon_acclaim_2.1.1_28FEB2013_01_HD.zip
SDCARD ROM: (Single boot) BOOT partition contents, boot.zip
134e175b18da509b37cf0897294214a6 *xylon_acclaim_2.1.1_06MAR2013_HD_SDC.zip
3b46595484586b0e0e99ca856fbb5ad7*xylon_acclaim_2.1.1_28FEB2013_HD_SDC.zip
INTERNAL GAPPS: *Might need to go to advance > fix permission in CWM before flashing GAPPS
4493696a11733e4e2a15d0026211963e *gapps-jb-20130301-signed.zip
c4a07a24e11448824b84e314600cd357 *gapps-jb-20121212-signed.zip
EXTERNAL GAPPS:
e2a80b77153a6bacd3df785742487ea3 *gapps-jb-20130301-signed-SDC.zip
36e9081e0dd29b67193d2db9441683c3 *cm-10.1-20121212-gapps-SDC.zip
RECOVERY: (TWRP 2.4.3.0 + CWM 6.0.2.8)
THANKS TO (CREDITS):
bauwks - Bootloader exploits
CYANOGENMOD
Source - https://github.com/CyanogenMod
Web - http://CyanogenMod.org
CM G+ - https://plus.google.com/+CyanogenMod
XYLON
Source - https://github.com/xyaosp
Web - http://xylon.androidvenue.com/
XYE G+ - https://plus.google.com/communities/102617491638136644864
Members:
Alex (AlexForTomorrow)
Arz Bhatia (arzbhatia)
Bluewall
Daniel MM (DaXmax)
David Vidal (Dorilife)
Varun Verma (D00mSlayer)
NOOK TABLET
Source - https://github.com/CMNookTablet, https://github.com/Kuzma30
Members:
Brandon Bennett (nemith)
Chris (chrmhoffmann)
fat-tire
Hashcode
Kuzemko Alexsandr (Kuzma30)
Kyrylo Mikos (mik9)
Rebell
KINDLE FIRE
Source - https://github.com/loosethisskin, https://github.com/KFire-Android
Members:
Aaron Davis (icemank121)
Andrew Dodd (Entropy512)
Hashcode
IngCr3at1on
JackpotClavin
Jacob (drkhd)
John Craig (x0xhellx0x)
Loosethisskin (twa_priv)
Markus Cisler (bl1nk)
Raymond Jay Golo (intersectRaven)
Scott Brady (sbradymobile)
Shujun
SGT7
Source - https://github.com/sgt7/android_packages_apps_Trebuchet
Members:
Angel666
Chirayu Desai (chirayudesai)
eaut
Humberto Borba (humberos)
jt1134
Koudai Aono (koxudaxi)
pulser
redrebel696
Scott Brady (sbradymobile)
techomancer
COMPILER
Source - https://github.com/succulent
Web - http://iamafanof.wordpress.com
HD (Succulent)
Questions and Answers
Want to clear cache manually?
Delete the dalvik-cache folder inside cache folder with root access & restart.
Is Jellybean running slow on your NT? It might be your SDCard.
microSD Card Benchmark Comparison — CrystalDiskMark
Why do I have to wipe data/factory reset?
Dirty installation can slow the OS and causes side effects due to residue files still on system.
Want to swap your internal storage (EMMC) to SDCARD?
Edit /system/build.prop, persist.sys.vold.switchexternal=0 to 1
My converted MP4/M4v isn’t working?
Use Handbrake 9.4. The current ducati firmware is outdated and doesn’t support newer MP4 codec.
How do I edit system files?
Use FileManager, settings>change access to root access, & click on lock icon, change to RO>RW
How do I take screenshot?
Hold power button + volume down
Where’s Developer options & Performance?
Click Build number several times.
Want to save battery?
Rename system/apps/phone.apk to phone.apk.bk
Change CPU performance to 800 MHz max feq. and use conservative, click set on boot
For better standby battery, go to Wifi Advanced settings > Keep Wi-Fi on during sleep > Only when plugged in
Where’s bluetooth/OTG/USB Host?
…
Do I need to install GAPPS?
Only when updating as the image comes with GAPPS
Yes, you do need to reinstall GAPPS after each update.
Don’t like Media Transfer Protocol (MTP) and want USB Mass Storage (UMS)?
Edit /system/build.prop, change persist.sys.usb.config=mtp,adb to mass_storage,adb
Older Mac might need http://www.android.com/filetransfer/
How to I view sdcard1 (SD card) with FileManager?
Go to Settings and change Access Mode to Prompt or Root.
Google Voice crashes?
Update Google Search
Don’t see folders or files when clicked on Internal Storage or SD card?
Refresh
Do I need to root the device for CM ROM?
Rooting is the ability to use superuser for root permission on a system.
Mainly for stock Android with no superuser.
All CM ROM come with superuser access.
How do I block OTA updates from BN?
You don’t need to. You are running CM software not BN.
How do I wipe data on sdcard?
The latest recovery (Orange theme) has an option “Wipe data1 on sdcard”, that is wipe P3 on sdcard.
It’s similar to factory reset, only that wipe data partition on the internal memory.
Boot animation is messed up?
Yes, for now.
What about tethering?
It’s removed since CM7, I couldn’t get to work with all the outdated patches.
[REF][TWEAKS] Kernel Governors, Modules, I/O Schedulers, CPU Tweaks, AIO App Configs
http://forum.xda-developers.com/showthread.php?t=1369817
I am stuck in a recovery boot loop?
Flash this, flashable_fix_bootloop.zip, File>Download
GAPPS, stuck at Wi-Fi Connecting…?
Patient. Just wait up to a couple minutes.
Hulu Plus not working?
You need a cracked Hulu APK so search for it on XDA. Hulu works on stock ROM.
How do I increase animation speed?
In the developer options, change animation scale to none or 0.5x.
Succulent, this is awesome. I'll test it out myself
Re: [ROM] Unofficial Xylon Acclaim 2.1.1 [XYAOSP 4.2.2] [Nook Tablet]
Amazing!
Sent from my NookTablet using xda app-developers app
Imma test it out also. Fantastic!!
---------- Post added at 02:46 AM ---------- Previous post was at 02:45 AM ----------
After testing for about an hour, I can name a few problems I came across. First thing I noticed was the text and the icons. They were blurry and was an eye strain for me. Second minor problem but the Nav icons are smaller than on the other builds. I tried youtube and the first video I tried didnt work. Just show's play button.
Keep up the great work!!
I'll try this out, thanks.
Just to be clear, only the top link is for the actual rom right? The source links are just for reference? I assume.
Anyone try it yet?
postulio said:
I'll try this out, thanks.
Just to be clear, only the top link is for the actual rom right? The source links are just for reference? I assume.
Anyone try it yet?
Click to expand...
Click to collapse
The download link is under Internal ROM towards the middle of the post.
Used this ROM for a day, not bad.
Love the customization. To me though, it feels a little laggy. Also i have been having tons of trouble playing youtube videos on it, both on the website and through the app. they either dont start at all or crash (and i still hear the audio, lol). sometimes they simply wont load.
another observation is that pretty much all the 4.2 ROMs i've tried have pretty bad battery life when compared to 2.3. This is unfortunate but doesnt render the tablet unusable. I'd say if you charge it every night, it is fine. Leave the tablet overnight, without charging, with wifi on (although i know it goes into sleep) the battery drops from 85 to 35 in about 8-9 hours, which is awful.
Personally I am going back to PA 3.1 for now, but will check back if development progresses.
I tried out Xylon: for a first build it works really well and is very responsive (even though I am running it off SD). The couple of problems I ran across are the same one I recently encountered on some other ROMs: e.g., MX Player out-of-control when playing some video in HW mode (even when the Player is force-stopped the audio still keeps going), System-UI crashes when switching to Tablet-UI.
I think this ROM has a lot of potential and is really fun to use.
Whenever I adb devices from my PC to NT, it says devices offline, how can I connect my PC & NT? I found some other threat about new adb on 4.2.2 but they didn't help.
bingoz said:
Whenever I adb devices from my PC to NT, it says devices offline, how can I connect my PC & NT? I found some other threat about new adb on 4.2.2 but they didn't help.
Click to expand...
Click to collapse
You might find some helpful pointers at http://forum.xda-developers.com/showthread.php?p=35971559#post35971559.
Also, make sure that you do have the latest update of ADB (see http://forum.xda-developers.com/showpost.php?p=38118551&postcount=9).
FWIW, I re-flashed Xylon ROM with cm-10.1-20121212-gapps-SDC.zip — not only does Google auto-restore now works but also I no longer have the problem of “System-UI has stopped” when switching to Tablet-UI.
been using this for 4 or 5 days now, seems pretty good to me, battery life is a lil suspect, but ive just uopdated to 6th march version, so will see how this goes
CWM Backups
It may be I am using a dated CWM but my 6.0.2.8 version does not correctly calculate the MD5 sums. Anyone able to successfully do backups with MD5 sums ti help me know if the issue is mine or the ROMS?
Looks cool Im going to try flashing this rom today. Thanks for all the work you put into it.
RhinoNelson said:
It may be I am using a dated CWM but my 6.0.2.8 version does not correctly calculate the MD5 sums. Anyone able to successfully do backups with MD5 sums ti help me know if the issue is mine or the ROMS?
Click to expand...
Click to collapse
6.0.2.8 is a very recent if not the latest version of CWM.
How do you determine that "6.0.2.8 version does not correctly calculate the MD5 sums"?
CWM backups
digixmax said:
6.0.2.8 is a very recent if not the latest version of CWM.
How do you determine that "6.0.2.8 version does not correctly calculate the MD5 sums"?
Click to expand...
Click to collapse
When I run the backup, the last step performs the MD5 sum and it gives an error. I had this with a backup with a different ROM as well yesterday. I didn't retry so it could have been circumstantial. I don't have this ROM installed any longer so I can't attempt another backup of it.
RhinoNelson said:
When I run the backup, the last step performs the MD5 sum and it gives an error. I had this with a backup with a different ROM as well yesterday. I didn't retry so it could have been circumstantial. I don't have this ROM installed any longer so I can't attempt another backup of it.
Click to expand...
Click to collapse
FWIW, the couple of times I encountered "MD5 errors" in doing backup using recovery were when I had insufficient space in the sdcard's first partition ("/boot") to accommodate the size of the needed backup.
The Rom seems to think that /sdcard directory is in the external sd card, So I can't download files from the internet (web browser) with out a microsd, it gives me an error "says no such directory." Is this normal for the Nook Tablet, any way to get around that?
succulent said:
....
Want to swap your internal storage (EMMC) to SDCARD?
[*]Edit /system/build.prop, persist.sys.vold.switchexternal=0 to 1
jamesgg said:
The Rom seems to think that /sdcard directory is in the external sd card, So I can't download files from the internet (web browser) with out a microsd, it gives me an error "says no such directory." Is this normal for the Nook Tablet, any way to get around that?
Click to expand...
Click to collapse
Did you try this?
Sent from my ST27i
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please OP remove my old post about Ubuntu on Tab 3...
T3buntu (Had to call it something...)
Disclaimer:
What you do with this information is up to you. If your device breaks while trying anything in here you do that at your own risc.
I cant be held responsible for anything that happens to your device.
Everything in here was tested on a Samsung Galaxy Tab3 10.1(5210) if you try anything in here on any other device thats up to you.
Most of the work is made by the Linux on Android team i have just tested and fixed some stuff.
The image is ext2, x86 but im working on a ext4, AMD64 image.
”Changelog”
1. Replaced lxde with KDE Plasma
2. Added entryś in etc/fstab for int/ext SdCards
3. Edited bootscript from the Linux on Android team so that the SdCards in the Tab is correcly mounted and works with fstab.
4. Installed "missing" packages to minimize errors.
Works:
Wifi
Battery indicator
Int/Ext SdCard
Most of the stuff in Ubuntu.
Issues:
Leftpanel is black
Slow startup, but can be fixed. I will add that later.
Some apps dont work if you start them as root.
Couldnt make jpg work as wallpaper so using png at the moment.
Rotation isnt setup since we cant use xrandr to rotate the screen..
Not tested:
GPS
ToDo
Streamline startup
Add init.d support on the Tab
Tweaking were ever possible.
Fix sound
Now for the fun stuff.
Installation:
1. Root your device. I used this Guide.
2. Install Busybox.
3. Install Linux on Android.
4. Install a VNC client of your shoice, i preferr Jump Desktop free.
5. Copy bootscript.sh to /data/data/com.zpwebsites.linuxonandroid/files/ overwrite the old file.
6. Unpack and Copy the t3buntuv1.2_20131216.img to a place of your choosing on either internal or external sdcard.
7. Make a Linux on Android widget and point it to the img file you copied in 6.
OBS !! This image is preconfigured with the user ubuntu and psw t3buntu..
8. Now click on the LOA widget you made in 7 and let linux ”bootup”
9. In your VNC client connect to localhost.
DONE ! Your now in Ubuntu..
If you want more screenspace you can uncomment
# service call activity 42 s16 com.android.systemui
In bootscript.sh this will remove the android panel. The problem with this at the moment is that to
get it back you have to restart the Tab becourse the ´am´ command to get it back ”Seg faults” on
my tab and i havnt figured out why yet.
Consider this image as alpha...
OBS !! The image file is BIG 1.4GB compressed and 4GB decompressed. Will try and make it smaller not sure how the Linux on Android team made there images so small...
LINK to imagefile
LINK to bootscript
Credits
Linux on Android team
The one that made the scripts from the start. Not sure who made them...
How about a link to get 3. Linux on Android.
I know I'm top lazy to Google.
Sent from my GT-P5210 using XDA Premium HD app
Awesome! Glad to see something! And having Ubuntu is a very cool os to have! Good work and thank you!
Sent from my SCH-I605 using xda app-developers app
Added links to Linux on Android and Busybox in first post.
Nice, but there are a few things...
The bootscript.sh contains one little, but crucial error.
At line 172, character 44, you forgot one space, which makes the mount procedure unusable:
Code:
$bbox mount -o bind /storage/extSdCard $mnt/extSdCard
Which should be:
Code:
$bbox mount -o bind /storage/extSdCard $mnt/extSdCard
Without this (for me) it failes while it's starting up.
And, another thing, my tablet reboots at the moment I have to run VNC to start the X server, even though I'm not doing or touching anything.
After reboot it doesn't start up t3buntu either.
But, very good work !!
And yes, I do have Samsung Galaxy Tab 3 10.1 GT-P5210...
RubenStauttener;48606882]Nice, but there are a few things...
The bootscript.sh contains one little, but crucial error.
At line 172, character 44, you forgot one space, which makes the mount procedure unusable:
Code:
$bbox mount -o bind /storage/extSdCard $mnt/extSdCard
Which should be:
Code:
$bbox mount -o bind /storage/extSdCard $mnt/extSdCard
Without this (for me) it failes while it's starting up.
Havnt noticed any problems here but i have added the space and updated the script since both versions works for me.
And, another thing, my tablet reboots at the moment I have to run VNC to start the X server, even though I'm not doing or touching anything.
After reboot it doesn't start up t3buntu either.
Does it reboot during script execution ? It do sound like a mem issue. Do you have widgets and such running in android ?
You can try with enabling the swapfile in bootscript.sh .
But, very good work !!
And yes, I do have Samsung Galaxy Tab 3 10.1 GT-P5210...
I've got the terminal up and running fine. But I can't VNC into it. What settings are you using for you VNC viewer?
How about native graphic support using libhybris? Or since this device use PowerVR SGX 544, is native X11 possible? Reference: https://wiki.archlinux.org/index.php/Intel_GMA3600
EDIT: https://github.com/trevd/android_kernel_samsung_santos10/tree/cm-10.2/drivers/staging/mrst/pvr and https://github.com/thomas001/cedarview-drm/tree/master/staging/cdv/pvr looks similar
Thanks for sharing but it's not working
VNC: autentification failed !
Jump Desktop: It ask a password, and I don't have this password !
Sent from Gallifrey using TARDIS
Nonta72 said:
Thanks for sharing but it's not working
VNC: autentification failed !
Jump Desktop: It ask a password, and I don't have this password !
Sent from Gallifrey using TARDIS
Click to expand...
Click to collapse
Test password: ubuntu
When run script say mnt error =/
zorrigas said:
Test password: ubuntu
When run script say mnt error =/
Click to expand...
Click to collapse
Thanks, but I already solved it :good:
Sent from my GT-5210 powered by AmatROM HD
Hi, I posted a question in the Q&A forum (them 10 posts), but I guess it really belongs here.
Tried this on my TWRP rooted UANB4 stock rom P5210, stock kernel. And I get the following with your script and image:
Code:
[email protected]:/ $
[email protected]:/ $ cd /storage/extSdCard/Img
[email protected]:/storage/extSdCard/Img $ su
[email protected]:/storage/extSdCard/Img # sh /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh /storage/extSdCard/Img/t3buntuv1.2_20131216.img
Checking loop device... FOUND
mount: mounting /dev/block/loop255 on /data/local/mnt failed: Invalid argument
Error: Unable to mount the loop device!
1|[email protected]:/storage/extSdCard/Img #
Line : $bbox mount -t ext2 /dev/block/loop255 $mnt
Do I tell busybox to overwrite the mount command?
Otherwise, excellent work, cant wait till I have it running.
*EDIT*
Turns out I just had to copy the image again, I guess my first transfer got cut off.
Totally works, thx
hey. i noticed that the last update was in April of 2014. i was wondering if there was any updates on this.
getting linux on my tablit was the #1 reason i chose to root my GT-P5210 in the first place.
Homage said:
hey. i noticed that the last update was in April of 2014. i was wondering if there was any updates on this.
getting linux on my tablit was the #1 reason i chose to root my GT-P5210 in the first place.
Click to expand...
Click to collapse
I did not try this one. I bet itworks in VNC as it tell us. Instead i did
http://forum.xda-developers.com/showpost.php?p=58175673&postcount=54
I guess I can say it work aceptable in VNC mode, definitly work nice in comand mode. I been working in a native solution but it is a hard bone for my teeth. Look in the general area.
Download link is down
I would like to run Ubuntu on my Tab 3 but the link doesn't work. Could some upload a working link please?
Hi Guys,
Anyona has this .sh script and the t3buntuv1.2_20131216.img file? if you send me im hosting and distributing free as i live i want to use for my home automatization.
THX
G
jorgen_gustavsson said:
Please OP remove my old post about Ubuntu on Tab 3...
T3buntu (Had to call it something...)
Disclaimer:
What you do with this information is up to you. If your device breaks while trying anything in here you do that at your own risc.
I cant be held responsible for anything that happens to your device.
Everything in here was tested on a Samsung Galaxy Tab3 10.1(5210) if you try anything in here on any other device thats up to you.
Most of the work is made by the Linux on Android team i have just tested and fixed some stuff.
The image is ext2, x86 but im working on a ext4, AMD64 image.
”Changelog”
1. Replaced lxde with KDE Plasma
2. Added entryś in etc/fstab for int/ext SdCards
3. Edited bootscript from the Linux on Android team so that the SdCards in the Tab is correcly mounted and works with fstab.
4. Installed "missing" packages to minimize errors.
Works:
Wifi
Battery indicator
Int/Ext SdCard
Most of the stuff in Ubuntu.
Issues:
Leftpanel is black
Slow startup, but can be fixed. I will add that later.
Some apps dont work if you start them as root.
Couldnt make jpg work as wallpaper so using png at the moment.
Rotation isnt setup since we cant use xrandr to rotate the screen..
Not tested:
GPS
ToDo
Streamline startup
Add init.d support on the Tab
Tweaking were ever possible.
Fix sound
Now for the fun stuff.
Installation:
1. Root your device. I used this Guide.
2. Install Busybox.
3. Install Linux on Android.
4. Install a VNC client of your choice, i preferr Jump Desktop free.
5. Copy bootscript.sh to /data/data/com.zpwebsites.linuxonandroid/files/ overwrite the old file.
6. Unpack and Copy the t3buntuv1.2_20131216.img to a place of your choosing on either internal or external sdcard.
7. Make a Linux on Android widget and point it to the img file you copied in 6.
OBS !! This image is preconfigured with the user ubuntu and psw t3buntu..
8. Now click on the LOA widget you made in 7 and let linux ”bootup”
9. In your VNC client connect to localhost.
DONE ! Your now in Ubuntu..
If you want more screenspace you can uncomment
# service call activity 42 s16 com.android.systemui
In bootscript.sh this will remove the android panel. The problem with this at the moment is that to
get it back you have to restart the Tab becourse the ´am´ command to get it back ”Seg faults” on
my tab and i havnt figured out why yet.
Consider this image as alpha...
OBS !! The image file is BIG 1.4GB compressed and 4GB decompressed. Will try and make it smaller not sure how the Linux on Android team made there images so small...
LINK to imagefile <===== this URL broken
LINK to bootscript <===== this URL broken
Credits
Linux on Android team
The one that made the scripts from the start. Not sure who made them...
Click to expand...
Click to collapse