Database Users

New to NC; Whats the hot setup?

Hey all!
I am new to the NC community, but have quite a bit of experience working with my Samsung Fascinate. I have some minor themeing experience.
Just ordered a NC from ebay for 119 and was curious what sort of setup (ROM, KERNEL) etc are stable and working well?
What OC is stable?
Is Honeycomb worked out as fully functional?
I have done some sticky reading, and I would like to just make a bootable sdcard, and leave the Emmc alone for now.
What are the recommendations?
Thanks!

CM7 is definitely the best for this. Honeycomb did not have access to the sources and so was more of a demo.
We hope that ICS may make it onto the NC one day but for now CM7 gives a really good stable experience.
You can choose to use the latest stable CM 7.1 or choose to use one of the late nightly builds. There has been an issue with what is called SOD (Sleep of death) where the device occasionally doesn't wake up from sleep and needs a reboot. This was an issue even with 7.1 on some devices. It now appears to have been solved but requires an extra patch which should make it into a nightly soon.
Installing onto a boot SD or emmc is both easy tasks and there are plenty of guide material on this. If you are going to boot from SD make sure you use a Sandisk card (e.g. a class 4 16 or 32GB). These give much better performance when used in this role over other brands.
If you end up primarily using CM7 and not reverting to stock then I would say it is worth going full emmc. It is easy to revert to stock if you ever need to. Running from emmc gives more overall memory and makes management and back up more straightforward.
Most Nooks OC fine up to 1300 and remain stable. The boost in performance is fairly dramatic. For some reason some graphics benchmarks peak at 1200MHz and get worse if the OC is pushed higher. I guess the GPU may end up clocking lower if the main clock is pushed too far.

Thanks BOB!
I had used CM7.1 on my fascinate, but it was a short stay as it wouldn't play nice with wifi at my house. Hopefully that's not the case with the NC.
How is MIUI on the NC? From what I see it has done pretty good. Do you have any particular experience with it?
As far as kernels, what are the stable ones by name?
I have plenty of experience of writing ROMS to the internal memory with CWM so I shouldn't be too far off if I need to do that, or choose to go that route.

If you use cm7 can you still use the stock Nook Reader? or what is the reader of choice?

I believe you can only use the Stock reader in the Stock ROM. There is a standard Nook App for Android but it is not the same. Works OK for your standard reading etc but not as nice as the stock reader.
If you want to use the Stock Reader and CM& then I think your choices are ...
1) Run CM7 on the SD card and boot into Stock whenever you want to use the Stock reader.
2) Make a Stock ROM set up on a SD card, Install CM7 on emmc and reverse the procedure of 1.
3) Install a dual boot Stock and CM7 off the emmc. At start up you then choose whether to boot into Stock or CM7 and the SD card remains fully usable as data.
I did use method 3 for a while when I first started with Nook but I so rarely went into stock and I don't really need to access the stock reader that I gave up and redid the emmc as full CM7.
I did try MIUI out but I ended up reverting to standard CM7 really just to keep compatibility with other CM7s I use.

Advantages of Internal Dual boot over SDcard boot?
Been running CM7 off an SDcard for almost a year...
Considering moving too a dual boot internal setup stock 1.4.2 + CM7.2...
But not really sure of the advantages/disadvantages of dual internal vs. emmc stock + CM7 on the sdcard.
The only thing I can think of is that dual internal would allow bot stock and CM7 to use my new 32GB SD card...though I haven't decided if that's an advantage or disadvantage
I do want to keep stock around for the kids books, read in store...plus at least with the old version of CM7 I was using the Nook app didn't do well with my magazines.
Appreciate any guidance!
Charles

charles_w said:
Been running CM7 off an SDcard for almost a year...
Considering moving too a dual boot internal setup stock 1.4.2 + CM7.2...
But not really sure of the advantages/disadvantages of dual internal vs. emmc stock + CM7 on the sdcard.
The only thing I can think of is that dual internal would allow bot stock and CM7 to use my new 32GB SD card...though I haven't decided if that's an advantage or disadvantage
I do want to keep stock around for the kids books, read in store...plus at least with the old version of CM7 I was using the Nook app didn't do well with my magazines.
Appreciate any guidance!
Charles
Click to expand...
Click to collapse
I personally would stay away from dual booting on emmc. It plays with your internal partitions which is not a good idea. I would keep stock on emmc and the newly released 7.2-RC1 on SD. By making one simple change to stock you can have both systems share the 32GB card and not have to take the card out ever. The boot menu of CM7 makes it very easy to boot between the two.
Sent from my Nook Color running ICS and Tapatalk

Thanks for the reply.
leapinlar said:
By making one simple change to stock you can have both systems share the 32GB card
Click to expand...
Click to collapse
Don't suppose you happen to have a link to a post that describes that one simple change do you?
Hope to hear from some others...as it seems many use the dual boot internal...so there must be some advantages for certain scenarios.
Charles

charles_w said:
Thanks for the reply.
Don't suppose you happen to have a link to a post that describes that one simple change do you?
Hope to hear from some others...as it seems many use the dual boot internal...so there must be some advantages for certain scenarios.
Charles
Click to expand...
Click to collapse
It does have advantages, you don't have to worry about SD card switches, etc. I was just saying it is non-standard and risky to your partitions. One of the partitions, (2) is vital to your system (it has your serial #, etc in it) and since you have to write to the partition table to accomplish dual boot, you risk the possibility of corrupting it as you are setting up dual boot. But a lot of people have done it with no problem.
I don't have a link on how to make the change. It is a very simple change to one file. There is a text file in /system/etc named vold.fstab. In it there is a line that contains 'sdcard auto' in it. Change that to 'sdcard 4'. (without the quotes.) Now the hard part. You have to be rooted on emmc to have access to the file. But there are plenty of rooting threads that tell you how. You can even unroot after you have fixed the file if you want. The other way is to change the file on your PC using adb. Both methods take a little extra effort, but it is worth it to not have to swap SD cards all the time. Both systems then share the SD card storage area. By making this change, I know of no advantage to dual boot and it is much safer (and you already have the SD set up).
And you use the boot menu to select which operating system you want to boot to. That comes with CM7. (But you know that having run CM7 for a year).
Sent from my Nook Color running ICS and Tapatalk

found the link for sharing sdcard
leapinlar said:
I don't have a link on how to make the change. It is a very simple change to one file. There is a text file in /system/etc named vold.fstab. In it there is a line that contains 'sdcard auto' in it. Change that to 'sdcard 4'. (without the quotes.) Now the hard part. You have to be rooted on emmc to have access to the file.
Click to expand...
Click to collapse
Found it, http://forum.xda-developers.com/showpost.php?p=13668471&postcount=529
and it doesn't even require emmc to be rooted.
Charles

charles_w said:
Found it, http://forum.xda-developers.com/showpost.php?p=13668471&postcount=529
and it doesn't even require emmx to be rooted.
Charles
Click to expand...
Click to collapse
good job!
Sent from my Nook Color running ICS and Tapatalk

charles_w said:
Found it, http://forum.xda-developers.com/showpost.php?p=13668471&postcount=529
and it doesn't even require emmc to be rooted.
Charles
Click to expand...
Click to collapse
Seems the File Expert feature to mount system as read write is no longer included in the free version. Is there a terminal command for that?
Sent from my NookColor using Tapatalk 2 Beta-2

Sherip said:
Seems the File Expert feature to mount system as read write is no longer included in the free version. Is there a terminal command for that?
Sent from my NookColor using Tapatalk 2 Beta-2
Click to expand...
Click to collapse
The free version of ES Explorer allows mounting system as r/w.

Little update....
I have found that the best setup I have found so far is CM 7.2 RC1 (03042012) with V6 (Update 9 RC6.9) supercharger set to option 9 (super 1000HP) supercharge (link for the V6 is on Mr666's page). The ICS transitions included in RC1 are swift and with the supercharger everything is super smooth. I can say I have noticed a small increase in my battery life as well. I toyed around with the UV/OC settings and returned to the sleep of death's I was getting on 7.1. So I re-flashed and just have left everything set to default in the peformance settings that comes with 7.2. So far, no SOD"s and I have a very capable tablet.

leapinlar said:
The free version of ES Explorer allows mounting system as r/w.
Click to expand...
Click to collapse
When I set the option in ES Explorer, I get an error message that it failed to mount r/w. Possibly this is not possible without rooting emmc. In terminal I can't make the Nooksys folder.
Sent from my NookColor using Tapatalk 2 Beta-2

Sherip said:
When I set the option in ES Explorer, I get an error message that it failed to mount r/w. Possibly this is not possible without rooting emmc. In terminal I can't make the Nooksys folder.
Sent from my NookColor using Tapatalk 2 Beta-2
Click to expand...
Click to collapse
You don't need to mount it where racks said. You can mount it in /data, which you should be able to make r/w. Where it says /mnt/nooksys, substitute /data/nooksys. First go to /data with es explorer and manually create the nooksys folder (you need to set your home directory to / in es explorer before you can see /data). Then follow his steps except don't do the mkdir command since you did it manually. And wherever it says /mnt substitute /data.
Edit: you need to modify the mount command, it now needs to have appended to the end, -t ext4. - Scratch that. It's only necessary if you are trying to do it from CM9. CM7 works OK as written.

I created nooksys in data with ES. In terminal I tried:
$su
# mount -o /dev/block/mmcblk0p5 /data/nooksys
and it returns
mount: not found
Any idea how to fix?
I have cm7.2 RC-1 on SD (verygreen but boot partition was resized) and stock 1.42 on emmc (untouched except by b&n)
Sent from my NookColor using Tapatalk 2 Beta-2

Sherip said:
I created nooksys in data with ES. In terminal I tried:
$su
# mount -o /dev/block/mmcblk0p5 /data/nooksys
and it returns
mount: not found
Any idea how to fix?
I have cm7.2 RC-1 on SD (verygreen but boot partition was resized) and stock 1.42 on emmc (untouched except by b&n)
Sent from my NookColor using Tapatalk 2 Beta-2
Click to expand...
Click to collapse
What is the -o in the line for? And you manually created the folder first? And you did check the root button in settings?

All the options for Root Settings in ES File Explorer are checked. I have / set as the home directory. I created a folder named nooksys manually inside /data using ES. I closed ES and started terminal. I'm not sure what the -o is for, I found it in some other posts and I guess I was just trying to fix it myself, but the error message
mount: not found
is the same with and without the -o
Edit: also the version of ES File Explorer is the latest version per "Check Now"

Sherip said:
All the options for Root Settings in ES File Explorer are checked. I have / set as the home directory. I created a folder named nooksys manually inside /data using ES. I closed ES and started terminal. I'm not sure what the -o is for, I found it in some other posts and I guess I was just trying to fix it myself, but the error message
mount: not found
is the same with and without the -o
Edit: also the version of ES File Explorer is the latest version per "Check Now"
Click to expand...
Click to collapse
After you created the folder, did you check it. By that I mean open it? It should be an empty folder. Exit out of the folder, but leave Es explorer open. Use the home key to get back to home screen so you can open terminal. I don't know much about es, maybe it has to stay open to keep root access.
Edit: the :not found error is saying it cannot understand the mount command. Are you using all lower case? Very important. Terminal does not like upper case.

[UNOFFICIAL][TF300T] Ubuntu 11.10 v0.01 Alpha (Native)(Dual Boot)

###############-------------------------------------WARNING-------------------------------------------------------##############
I AM NOT RESPONSIBhttp://youtu.be/Zl767IukT5sLE FOR ANY REPERCUSIONS FROM FOLLOWING THE INSTRUCTIONS
LISTED BELOW. THIS INFORMATION IS PROVIDED AS IS AND DOES NOT IMPLY FUNCTIONALITY
OR SAFETY FOR YOUR DEVICE. PROCEED AT YOUR OWN RISK.
##########################################################################################
I realize this should probably be posted in the Development forum, however I am relatively new to the TF300T and xda will not allow me to post it there.
REFERENCES
Kernel and initramfs are taken from [DEV] ArchLinux on the TF300T(G) which is credited to cb22, with a few modifications of my own to the initramfs to allow ubuntu to boot.
The root filesystem is based on an image I found created by lilstevie for the tf201. From everything I researched the tf201 is nearly identical to the tf300t so it boots extremely well. If the original disk image is flashed to a microSD and the original kernel from the ArchLinux post is used the system is more stable. However my method below was adapted to work with the internal storage, and still works nearly as well.
WORKING
Power Management - Shutdown, Reboot, Battery Status
USB Host Controller
SD and microSD slots
NetworkManager
Ethernet works with a USB Ethernet adapter. I'm using an RTL8150.
Dock Keyboard
Updates Work -- I just don't recommend doing an Upgrade at this time since I haven't tried it. All my experience with getting 12.10 running
shows some problems with Unity which I cannot resolve yet.
You tell me....
NOT WORKING
WiFi -- should be working soon, just need to talk to cb22 since it works in ArchLinux
3G -- same as WiFi for TF300TG models
TouchPad -- data is visible just need driver from cb22's ArchLinux
Touchscreen -- same as TouchPad
Sound -- gets picked up by Ubuntu however no sound can be heard, likely just a setting somewhere
You tell me....
REQUIREMENTS
Asus TF300T
Requires the JB bootloader so you must be updated to atleast 10.4.2.13 Stock Firmware ONLY
--I will try and release a compatible boot blob for Cyanogen builds.
Keyboard Dock
USB Mouse
INTRO
[UNOFFICIAL][TF300T] Ubuntu 11.10 v0.01 Alpha for Asus Transformer Pad TF300T (G untested)
The system installs on the internal storage on the data partition. Installation is the same as for cb22's ArchLinux port.
Part 1 - Kernel Blob
Reboot your device into fastboot mode.
From your computer run:
fastboot flash staging hybridubuntu.blob
fastboot reboot
Your system should now reboot back to Android OS.
Part 2 - Root Filesystem
First copy the rootfs (ubuntu.tar.gz) to your device's internal SD.
Either through adb or the android terminal run the following:
su
cd /media
mkdir linux
chmod 755 linux
cd linux
tar -xzvf /data/media/linux.tar.gz
Lastly, to control which OS is booted the boot blob checks for the file .boot_linux in /storage/sdcard0 or /data/media/
To create the file just run the following commands in adb or terminal:
su
touch /data/media/.boot_linux
chmod 755 /data/media/.boot_linux
Reboot and your system will boot into the Ubuntu 11.10 Configuration followed by the desktop.
To get back into Android just remove the file from within Ubuntu and restart.
*Note the Data partition isn't getting mounted in this release so when you open the terminal run the following:
sudo mount /dev/mmcblk0p8 /mnt
sudo rm /mnt/media/.boot_linux
If anyone has any questions or problems please feel free to let me know.
DOWNLOADS
Kernel Blob - http://depositfiles.com/files/j1mlor3v1
RootFS Tar Ball - http://depositfiles.com/files/rjhu1pwuo
Root Disk Image - http://lilstevie.geek.nz/downloads/ubuntu.img.gz_11.10-0.1a_TF201_52f6273e6ad672358d2ebb181b24c200

This is going to bring a lot of excitement! Hope the development goes smoothly and you're able to work out the kinks.

Hi gjx86,
Im working with your kernel blob and root disk image: wired network works (module dm9601.ko), I can login to ubuntu via ssh.
One important issue with dock keyboard - it hangs after 5-10 min. I can kill gnome session using ssh and keyboard start again, but after few min it hangs again.
Btw, hdmi not working.
How You can use microSD as root file system:
" If the original disk image is flashed to a microSD and the original kernel from the ArchLinux post is used the system is more stable."

Why 11.10 and not 12.04? :'(

Ubuntu 12.04 Kernel and Rootfs
Hey,
I just realized that the Ubuntu porting going on for the TF700 runs on the TF300T!!
Check out this link: http://forum.xda-developers.com/showthread.php?t=1988174
There is an image for Unity2D their however so far I've found the Lubuntu to be the most stable.
I am in the process of replacing the firmware with that from the TF300T, specifically the WiFi firmware and driver needs to be rebuilt. I will post an updated TF300T kernel asap and a modded root that will allow WiFi to work.
Have fun and any feedback on issues specific to the TF300T would be great, thanks.

gjx86 said:
Hey,
I just realized that the Ubuntu porting going on for the TF700 runs on the TF300T!!
Check out this link: http://forum.xda-developers.com/showthread.php?t=1988174
There is an image for Unity2D their however so far I've found the Lubuntu to be the most stable.
I am in the process of replacing the firmware with that from the TF300T, specifically the WiFi firmware and driver needs to be rebuilt. I will post an updated TF300T kernel asap and a modded root that will allow WiFi to work.
Have fun and any feedback on issues specific to the TF300T would be great, thanks.
Click to expand...
Click to collapse
That's exactly what I'm up to... trying to make firmware and modules from cb22's arch to work with Lubuntu (I tried Ubuntu first but couldn't get past the log on screen, something about ICEAuthority if I remember correctly.
Let me know if there's anything you need help with... I'm kinda taking my first steps with linux but I know how to google! :laugh:

Touchpad and 3G works
gjx86 said:
There is an image for Unity2D
Click to expand...
Click to collapse
First of all thank you for your efforts.
The second good thing for me - tried this TF700 Unity2D image - it works. Touchpad and 3G works also for me
I did notning special - just flashed your kernel and tried several rootfs.
btw. I have extracted rootfs for Nexus 7 Ubuntu 12.10. May it be useful to post it here?
At least it boots But with rotaded screen and without Unity

This looks awesome! I'll try as soon as I can! Only thing, can you upload it to another mirror? It's quite annoying to only be able to download 1 file every 20 min from DepositFiles... Also DepostiFiles is extreamly slow. 1 hour to download...

great work guys!
I want to be able to boot Backtrack.

Just decided that I wanted to dual boot Linux, so very interested in this. Just one question: I'm assuming that as I would need to flash a blob using fastboot that I would need to be unlocked. Is this the case as it is not specified?
Thanks,
Stephen.

Another question: as it's based on cb's kernel which is based on unter's kernel I think this won't work with AOSP based ROMs I think because they have another kernel?
@pukeboy: As you need to be unlocked to flash recovery's via fastboot I think you need to be unlocked to flash kernels too

So, I have rooted my stock JB running the latest firmware. Would it be possible to flash this Ubuntu when it's already been rooted? If so, is there a chance I can destroy the bootup that I can't recover from with my ClockworkMod Recovery?

I'd really love for this to work!
It'd be a fun desktop experience
Keep up the awesome work, and no offence to the guy doing ArchLinux (which is awesome!), but ArchLinux is just too hard for me to use. I'm not much of a Linux Power User, so Ubuntu is numba 1!

Keep up the good work GJX, big up to both you and CB22 working on Arch!
By the way, isn't the mounting of the stock filesystem just a quick fix in /etc/fstab?

What about progress?
What about porting rabit's Ubuntu from TF700 thread? They have Ubuntu working now only with small bugs.

need some help
In the last two days i tried to port rabits (http://forum.xda-developers.com/showthread.php?t=2026919) native ubuntu solution to the TF300T. I followed the Instructions on this github page: https://github.com/rabits/tf700
I compiled the ASUS TF300T stock kernel code with rabbits .config file. Packed the compiled kernel together with rabits ramdisk and flashed everything to the boot partition. But i wasn't able to boot into the multiboot menu. The tablet just booted into android. Has somebody an Idea why this isn't working? Maybe in the kernel config? Do I need to change something in the ramdisk?
Thanks for your help

any news ?

Qub! said:
In the last two days i tried to port rabits (http://forum.xda-developers.com/showthread.php?t=2026919) native ubuntu solution to the TF300T. I followed the Instructions on this github page: https://github.com/rabits/tf700
I compiled the ASUS TF300T stock kernel code with rabbits .config file. Packed the compiled kernel together with rabits ramdisk and flashed everything to the boot partition. But i wasn't able to boot into the multiboot menu. The tablet just booted into android. Has somebody an Idea why this isn't working? Maybe in the kernel config? Do I need to change something in the ramdisk?
Thanks for your help
Click to expand...
Click to collapse
OK
I heave today don nasty staff
i used Kernel Blob from first post
and rabits / tf700 ubuntu 12.10 rootfs-ubuntu-12.10-0.8.0.tar.lzma (687 Mb) from http://forum.xda-developers.com/showpost.php?p=34655444&postcount=1
extracted rootfs-ubuntu-12.10-0.8.0.tar.lzma to /data/linux
flashet hybridlinux.blob from Kernel Blob
created file .boot_linux in /storage/sdcard0
rebooted tf300t
and walla ubuntu on
i heave no time to play with tf300t but i tray and started ubuntu 12.10 in 20 min.
i heave 2 hurs more to tray more
P.S. no credits to me. I joust play Lego on tf300t
P.S.S don't bee sad on me if something not leagal ( copyright ) or so
Sorry for me bad English
Edited
Simple multi boot ?
create file .boot_linux in /storage/sdcard1 (external sdcard)
remowe external sdcard - boot to android
insert sdcard - boot to ubuntu

Keshukas said:
OK
I heave today don nasty staff
i used Kernel Blob from first post
and rabits / tf700 ubuntu 12.10 rootfs-ubuntu-12.10-0.8.0.tar.lzma (687 Mb) from http://forum.xda-developers.com/showpost.php?p=34655444&postcount=1
extracted rootfs-ubuntu-12.10-0.8.0.tar.lzma to /data/linux
flashet hybridlinux.blob from Kernel Blob
created file .boot_linux in /storage/sdcard0
rebooted tf300t
and walla ubuntu on
i heave no time to play with tf300t but i tray and started ubuntu 12.10 in 20 min.
i heave 2 hurs more to tray more
P.S. no credits to me. I joust play Lego on tf300t
P.S.S don't bee sad on me if something not leagal ( copyright ) or so
Sorry for me bad English
Edited
Simple multi boot ?
create file .boot_linux in /storage/sdcard1 (external sdcard)
remowe external sdcard - boot to android
insert sdcard - boot to ubuntu
Click to expand...
Click to collapse
Which ROM did you use with this? I tried with CleanROM with no success.

I use stock 10.4.4.20 rooted and unloked .
Sent from my GT-I9100 using xda app-developers app

[DEV][WIP][Linux] Easy GNU/Linux on our tablet

Hi all!
Many of us are dreaming of having a real native desktop operating system on Galaxy Note 10.1 as a second system. Of course, the software there is not touch-optimized, but you can attach keyboard and mouse via USB-OTG and Bluetooth and imagine it's a netbook
exception13 showed us that it's possible and shared his work on in a forum and repo. X-Stranger could use it and shared compiled images of ArchLinux. But what if you want to do something more specific for your own needs and you are not such a great developer as both of them are?
My project is for all of you who want to have native GNU/Linux, who want to participate but don't know how yet. It's a guide how to build it from scratch. The problem is - I am not a superdev too and I couldn't do many things. Frankly speaking, all the remaining things seem to be small but I don't know how to overcome them. Maybe it's because I'm studying economics but not programming
Link to the guide.
I need help from anyone who knows how to overcome any of the problems on every step! Everything I managed to do by myself is already written there and currently I have a compiled kernel which is booting a partition on external SD but it freezes there.
If you have any ideas - you can just make a pull request out of Github's webinterface, if you don't know how to edit this html but know something about building Linux - you are welcome to open an issue or write it here and I will include it in the guide.
Let's make our Galaxy Note 10.1 better together!

,I just got my Note 101.1 earlier today. I'll look into the missing information and add to the webpage. Is there anything that you think I should look into first?

I actually had a question.
Looks like you have the section "Harder Way - how to prepare binaries" split into Ubuntu and Arch. Instructions for compiling the kernel are the same.
I guess my question is why the choice to show the arch kernel being compiled under arch?
Might be easier to read the guide with all the kernel compiling done in Ubuntu.
**Edit**
What I didn't originally mention is that i really like it. Hoping to help contribute as well.

darksabre_x said:
I actually had a question.
Looks like you have the section "Harder Way - how to prepare binaries" split into Ubuntu and Arch. Instructions for compiling the kernel are the same.
I guess my question is why the choice to show the arch kernel being compiled under arch?
Might be easier to read the guide with all the kernel compiling done in Ubuntu.
**Edit**
What I didn't originally mention is that i really like it. Hoping to help contribute as well.
Click to expand...
Click to collapse
Good question. The reason for that are that despite how close Arch Linux and Ubuntu are, the environments are different. Ubuntu usually has some sort of bash completion enabled by default whereas Arch Linux doesn't and of course each of them requires diferent packages installed to perform the same functions. I believe thermatk did each distro separately as to make things simpler for the end user. Pick a distro and go as each distro's guide can be tuned independent of the others.

Soul_Est said:
Good question. The reason for that are that despite how close Arch Linux and Ubuntu are, the environments are different. Ubuntu usually has some sort of bash completion enabled by default whereas Arch Linux doesn't and of course each of them requires diferent packages installed to perform the same functions. I believe thermatk did each distro separately as to make things simpler for the end user. Pick a distro and go as each distro's guide can be tuned independent of the others.
Click to expand...
Click to collapse
Doesn't really answer my question considering the end kernel will be the same regardless of the distro being used. I think you took my question as "Why are there 2 options for kernel compilation?", which wasn't what I was asking.
Looks like thermatk actually addressed the question with a page update.
It now gives separate options depending on which distro you want to end up with on your Note 10.1, in addition to separate kernel compilation options.
What I was referring to was when it was Ubuntu only instructions from kernel compilation all the way to deployment on the tablet and Arch only instructions. The kernel and linux image instructions weren't independent of each other, as they currently are.

Update
I'm really happy to hear that someone else wants to use it and contribute! :victory:
darksabre_x, you are right I separated the guide into parts yesterday because the system where you compile kernel doesn't really affect anything on the tablet.
Soul_Est, thank you for helping with questions in the thread :good:
Now I understand that tabs are not the best way to do it, will start this day from trying to rewrite this to a navbar constantly on top which lets you choose options from a dropdown.
Also yesterday got the guide to the point when one path through can get ypu to a bootable distro! You can compile kernel wherever you want, you should be on stock based rom and choose to install Arch on separate partition which probably will be a partition on SD. What you have to add at the end is
Code:
pacman -S lxde
and copy xorg.conf from X-Stranger's post. Once rebooted, you will be able to enter android:changeme and
Code:
sudo lxdm
and the gui will start if you don't have USB-OTG and keyboard you won't be able to enter password but you can poweroff from the interface's right corner :good: Attention: if gui says that it has no permissions to write logs do
Code:
sudo mount -n -o remount, rw /
and retry but do not forget to write here about it!
What are the current problems:
Why exception13 and X-Stranger both hardcoded the whole cmdline for kernel and forced it not to be changeable from bootloaders. It's easy to fix in the config but there should have been some idea or i'm paranoic?
What's wrong with LinuxDeploy, separate partitions and CyanogenMod? hiruna filed a bug but meefik seems to be away for a week. If anyone else with CM has an idea on how to overcome this maybe with some special unmount commands CM is thinking that ext4 partition is th extSdCard and mounts it so that LinuxDeploy can't install anything there (seems that it's the problem) while stock can't mount ext4 as extsdcard and is not touching the partition.
How do we make Debian/Ubuntu to boot? Both ways - for separate partition and img are stuck one the problem that not any mkinitramfs or abootimg or their combinations could get to a better state than initramfs shell. Separate partition should be easier so focus should be on it for the start.
Adapt X-Stranger's guide about booting Arch from *.img. It's there and should be tested, rewritten and easied and some whitespaces should be filled. I know there are some as i have spent many hours in Arch with little dirty hacks like
Code:
ln -s /proc/self/fd /dev/fd
that are needed but no one ever wrote that they are.
What's wrong with basic video? While we get bootable Arch if you add lxdm and xorg.conf it should work with lightdm and boot there without console commands. If you try to install lightdm you will get nothing but a black screen if you start it with
Code:
sudo lightdm
... and it should boot automatically without touching console.
Oh and why is kernel from exception13 not building at all? XD

Redesign #2
Anyone dislikes the new design idea with navbar selectors instead of tabs?
I hope it's better.
Will soon update the guide with last steps to have Arch with LXDE bootable from separate partition.
That's fun as I started this project to get Ubuntu working... :angel:
If anyone can understand what should be done with mkinitramfs to make debian/ubuntu rootfs bootable - please do it.

First success!
If you choose any pc distro, arch on sgn with lxde on a seaprate partition you will now get a fully working guide that will give you a native bootable GNU/Linux =)
That's first success for me but still i hope to get help as i don't know things I asked two posts ago and it's difficult to move forward.

XFCE problems
XFCE is booting (not in the guide yet) but for working with fingers in XFCE one should probably disable multitouch S-pen works fine.
http://lists.x.org/pipermail/xorg/2012-July/054626.html
http://xfce.10915.n7.nabble.com/Xfwm-window-borders-do-not-respond-to-touch-screen-td17348.html
Will find a way to enable onscreen keyboard on LightDM and update the guide with XFCE. Still I was hoping to make it my primary DE and they are not supporting fingers moving windows upstream :crying:

I was hoping to contribute this weekend but unfortunately my only machine is down after mucking up the /lib folder when heimdall. To add insult to injury, I have no backups. Installing Arch Linux or Debian and configuring everything to my liking again will take a few hours.
Sent from my GT-N8010 using Tapatalk 2

How to setup WiFi using wpa_supplicant.conf
How to setup WiFi using wpa_supplicant.conf​
1. Copy the "wifi" folder to "/opt"
- You will need gedit to edit the nameservers.
- You also need two dependencies before installing gedit.
- The two dependencies are : gtksourceview3-3.6.1-1-armv7h.pkg.tar.xz and libpeas-1.6.1-1-armv7h.pkg.tar.xz
2. Download them and copy over to ArchLinux
3. Install the dependencies first then gedit:
Code:
sudo pacman -U gtksourceview3-3.6.1-1-armv7h.pkg.tar.xz
sudo pacman -U libpeas-1.6.1-1-armv7h.pkg.tar.xz
sudo pacman -U gedit-3.6.2-2-armv7h.pkg.tar.xz
4. insmod the drivers:
***NOTE*** " 3.0.31-gedcc915 " is my kernel name. Change it to your
kernel name if it is different.
Code:
sudo insmod /lib/modules/3.0.31-gedcc915/kernel/net/wireless/cfg80211.ko
sudo insmod /lib/modules/3.0.31-gedcc915/kernel/drivers/net/wireless/bcmdhd/dhd.ko op_mode=0 firmware_path=/opt/wifi/bcmdhd_sta.bin nvram_path=/opt/wifi/nvram_net.txt_murata
5. Enable the wlan0:
Code:
sudo ip link set wlan0 up
6. Setup wpa_supplicant and ip address:
Code:
sudo wpa_supplicant -B -i wlan0 -Dwext -c /etc/wpa_supplicant/wpa_supplicant.conf
sudo ip addr add 192.168.1.33/24 dev wlan0
sudo ip route add default via 192.168.1.1
7a. Add nameservers:
Code:
sudo gedit /etc/resolv.conf
7b. Go to the next available line and type:
Code:
nameserver 8.8.8.8
7c. Next line :
Code:
nameserver 8.8.4.4
7d. Save it
8. Go back to the terminal and edit the wpa_supplicant file:
Code:
sudo gedit /etc/wpa_supplicant/wpa_supplicant.conf
- wpa_supplicant.conf file should be like this:
Code:
ctrl_interface=/var/run/wpa_supplicant
eapol_version=1
network={
ssid="NETWORKNAME"
scan_ssid=1
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
psk="NETWORKPASSWORD"
}
9. And finally, to connect to your network, run
Code:
sudo dhcpcd
Open up a web browser and enjoy!
:good: :good: :good:

WiFi
I am currently including WiFi in the main guide as it's something everyone needs :laugh:

Soul_Est said:
I was hoping to contribute this weekend but unfortunately my only machine is down after mucking up the /lib folder when heimdall. To add insult to injury, I have no backups. Installing Arch Linux or Debian and configuring everything to my liking again will take a few hours.
Sent from my GT-N8010 using Tapatalk 2
Click to expand...
Click to collapse
I will be happy if you join :good:

thermatk said:
I will be happy if you join :good:
Click to expand...
Click to collapse
I'll get right on the Arch Linux instructions once I get an Arch based OS installed. Hopefully that'll be tomorrow.
Written on my Galaxy Note 10.1

is this project dead ?

Equilibrio said:
is this project dead ?
Click to expand...
Click to collapse
Great job! This is awesome.
Anyone else having dependency conflicts with bluez and obexd-client?

cctoro said:
Great job! This is awesome.
Anyone else having dependency conflicts with bluez and obexd-client?
Click to expand...
Click to collapse
I did before but it really depends on what you have install at the time when you do the update.

Having a small issue
Ok, so I followed all the instructions and set the kernel up to boot from mmcblk1p2 (my ext4 partition on my sdcard I made for linux), and used dd to copy the prebuilt arch to the partition, and it boots and eveything seems to work but the wifi.... I repeated the process from the beginning all over and recompiled to make sure i didn't miss anything, but still no wifi... And since I'm using the prebuilt image copied to the sdcard for the distro, and everything works in it if i boot the .img from the internal storage and use the premade recovery, I'm assuming maybe there's something missing from compiling the kernel? In either case, if anyone has any ideas about this, please help, or if someone can make a properly compiled recovery.img that boots from mmcblk1p2, that would be super awesome.... I'm only mediocre in linux skill so any help would be appreciated!

K, so i was an idiot and forgot to copy the compiled kernel modules to /lib........ OOPS!
Arch linux distro booting from mmcblk1p2 with 1p3 as swap... all work awesome! Working on dri2 for the mali now.....
Sent from my GT-N8013 using xda app-developers app

Could you post a prepared .IMG, possibly? Thanks.
Sent from my GT-N8013 using xda app-developers app

[Q] Installing Multi-touch Patch on NookManager-Rooted NST 1.2.1

Hi,
I have a Nook Simple Touch, updated to UK version 1.2.1, and rooted using NookManager 0.5.0 with the NTGAppsAttack package.
I have installed the NoRefresh apk and am now looking to add the Multitouch mod, but I would want to keep the device's primary use for reading ebooks (so wouldn't want to loose quality there), and I wouldn't want to accidentally re-root it.
Therefore, would either of these be the right method to use, or is it possible to patch without replacing the kernel please?
http://forum.xda-developers.com/showthread.php?t=1906507
http://forum.xda-developers.com/showthread.php?t=1568560
I've found a few articles relating to multi-touch, but they seem to concern TouchNooter and NST firmware 1.1; hence why I'd like to double check before I try anything.
Cheers,

I went ahead and tried installing the multitouch.zip from a clockwork recovery image card, despite not being sure if it was even compatible with NookManager, and it said Installing and went through a process, but the device still doesn't support multitouch. At least it didn't kill it though
Could someone please point me in the right direction for adding multi-touch to a NookManager rooted NST please? I just can't seem to find the right method.

Donna80 said:
I went ahead and tried installing the multitouch.zip from a clockwork recovery image card, despite not being sure if it was even compatible with NookManager, and it said Installing and went through a process, but the device still doesn't support multitouch. At least it didn't kill it though
Could someone please point me in the right direction for adding multi-touch to a NookManager rooted NST please? I just can't seem to find the right method.
Click to expand...
Click to collapse
I'm using this kernel and it supports multitouch - http://forum.xda-developers.com/showthread.php?t=1906507 (build 174). It's not always obvious that multitouch is actually supported. So far I've only had pinch to zoom work in Opera Mobile and ADW, but it does work.

noodles2k said:
I'm using this kernel and it supports multitouch - http://forum.xda-developers.com/showthread.php?t=1906507 (build 174). It's not always obvious that multitouch is actually supported. So far I've only had pinch to zoom work in Opera Mobile and ADW, but it does work.
Click to expand...
Click to collapse
Another noob question -- I tried using Win32DiskImager to drop the uImage.img which that other thread contains onto an SD card, and then power-cycled my Nook with that card in place, but I saw no sign of an install -- is there any way to confirm that the install happened? Is that in fact the right way to attempt the install?

The uImage.img is not in fact an image that should be burned to an SD card. The file should actually be renamed to uImage and put in /boot. You either need a CWM-flashable zip or you can do it with adb (adb is quicker IMO since I don't have to prepare a CWM SD card).
Get ADB here:
http://forum.xda-developers.com/showthread.php?t=1474956
uImage instructions:
http://forum.xda-developers.com/showpost.php?p=24168019&postcount=21

Kralik said:
The uImage.img is not in fact an image that should be burned to an SD card. The file should actually be renamed to uImage and put in /boot. You either need a CWM-flashable zip or you can do it with adb (adb is quicker IMO since I don't have to prepare a CWM SD card).
Get ADB here:
http://forum.xda-developers.com/showthread.php?t=1474956
uImage instructions:
http://forum.xda-developers.com/showpost.php?p=24168019&postcount=21
Click to expand...
Click to collapse
Ah, thanks, that makes sense. In the meantime I achieved success by booting ClockwordMod and using it to install the 174 zip in its entirety. Multitouch now working, also fastmode, although the latter seems to cause glitching in CoolReader (but not in Nook Reader). . .

HELP!!!!
Kralik said:
The uImage.img is not in fact an image that should be burned to an SD card. The file should actually be renamed to uImage and put in /boot. You either need a CWM-flashable zip or you can do it with adb (adb is quicker IMO since I don't have to prepare a CWM SD card).
Get ADB here:
http://forum.xda-developers.com/showthread.php?t=1474956
uImage instructions:
http://forum.xda-developers.com/showpost.php?p=24168019&postcount=21
Click to expand...
Click to collapse
Men I try very few time to upgrade trought this method and the result is always the same, a complete failure . In the console mode when I try to push the uImage in the /media directory the message is "cannot stad ´uImage´: No such file or directory". Any advice?
PD: Yes, I rename the uImage.img to uImage and still the same message ¬¬

For rooted devices running 1.2.1, I'd recommend Latuk's kernel from http://forum.xda-developers.com/showpost.php?p=43797159&postcount=172. According to Latuk, it's based on B&N's source for the 1.2.1 kernel, plus the multitouch/fastmode/overclocking patches, plus some extra features (usb host mode) plus the fix for Class 10 SD cards.

cowbutt said:
For rooted devices running 1.2.1, I'd recommend Latuk's kernel from http://forum.xda-developers.com/showpost.php?p=43797159&postcount=172. According to Latuk, it's based on B&N's source for the 1.2.1 kernel, plus the multitouch/fastmode/overclocking patches, plus some extra features (usb host mode) plus the fix for Class 10 SD cards.
Click to expand...
Click to collapse
Full disclosure, I write this as a n00b in developer's clothing. I took the CWM-installable zip from the guevor kernel (earlier in the same thread) and replaced the uImage with Latuk's. This means CWM installable zip of Latuk's kernel. Emphasis on should as I really don't know what I'm doing here. That said, I flashed it on my nook, and I now have multitouch and haven't had any problems. Yet. Flash at your own risk, or until somebody who actually knows what they're talking about reads this and says "no that should work fine."
Hope it helps those of us who can't get adb working properly.

toolchain for building from source

Does anybody have downloaded toolchain files?
http://www.codesourcery.com/sgpp/lite/arm/portal/release1293 - links to https://sourcery.mentor.com/sgpp/lite/arm/portal/... and then to nowhere.
Even after loging.

Building the kernel? Building what?
There is the Google Android NDK for building native objects (for example libwhatever.so) or executables.

Renate NST said:
Building the kernel...
Click to expand...
Click to collapse
and u-boot from B&N sources

ucy74 said:
and u-boot from B&N sources
Click to expand...
Click to collapse
Yeah, u-boot and kernel are a bit different since they are not ELF.
I've not built those (although I have binary modified both).
Do you have a link for the latest B&N source?

Renate NST said:
Do you have a link for the latest B&N source?
Click to expand...
Click to collapse
I was tound file named "nook2_1-2.tgz" - somewhere on this forum...
I would like to add some (hardware) modules to kernel and change boot console from ttyS0 to ttyS1

ucy74 said:
I would like to add some (hardware) modules to kernel and change boot console from ttyS0 to ttyS1
Click to expand...
Click to collapse
Oh, gee. It's been so long since I've looked at the NST.
From what I remember:
ttyS0 is a 1.8V interface on that teeny connector.
ttyS1 is a 3.3V interface on the other teeny connector. (It goes through a level converter.)
See https://forum.xda-developers.com/showpost.php?p=61076373&postcount=22
Since the NST uses a separate image and ramdisk, the cmdline comes from u-boot.
Code:
commonbootargs=console=ttyS0,115200n8 initrd rw init=/init vram=16M video=omap3epfb:mode=800x600x16x14x270x0,pmic=${epd_pmic},
If you can get to fastboot then you can supply your own cmdline to experiment.

Renate NST said:
...ttyS0 is a 1.8V interface on that teeny connector.
ttyS1 is a 3.3V interface on the other teeny connector. (It goes through a level converter.)
See https://forum.xda-developers.com/showpost.php?p=61076373&postcount=22
Click to expand...
Click to collapse
I was following Your post and finally get access to both of ttyS's
Unfortunately ttyS0 RX pin in my NSTG is broken so I was swap u-boot.bin to made by mali100 one
Since the NST uses a separate image and ramdisk, the cmdline comes from u-boot.
Code:
commonbootargs=console=ttyS0,115200n8 initrd rw init=/init vram=16M video=omap3epfb:mode=800x600x16x14x270x0,pmic=${epd_pmic},
If you can get to fastboot then you can supply your own cmdline to experiment.
Click to expand...
Click to collapse
Can You paste whole Your commonbootargs phrase, also after last comma, from u-boot's printenv please?
Are You suggesting to update console by setenv commonbootargs parameters in u-boot menu editing?

There's console in xloader, console in u-boot, console in the kernel, console in Android.
They are all configured separately.
The cmdline for kernel is created in u-boot dynamically, but the tty spec is in that template.
You can just modify it.
Look for ttyS0 and change it to ttyS1
There was a whole thread on this but I can't seem to find it right now.

Renate NST said:
...You can just modify it.
Look for ttyS0 and change it to ttyS1
Click to expand...
Click to collapse
I was changing parameters by setenv in u-boot console
Code:
setenv commonbootargs console=ttyS1,115200n8 initrd rw init=/init vram=16M video=omap3epfb:mode=800x600x16x14x270x0,pmic=${epd_pmic},vcom=${vcom} androidboot.console=ttyS1
printenv
...
commonbootargs=console=ttyS1,115200n8 initrd rw init=/init vram=16M video=omap3epfb:mode=800x600x16x14x270x0,pmic=${epd_pmic},vcom=${vcom} androidboot.console=ttyS1
...
saveenv
and tablet is dead
so I was try switch back to previous settings booting with NookManager
(funny thing is: when first booting in NookManager console for ketnel booting was switched accordingly to my changed settings...)
Code:
setenv commonbootargs console=ttyS0,115200n8 initrd rw init=/init vram=16M video=omap3epfb:mode=800x600x16x14x270x0,pmic=${epd_pmic},vcom=${vcom} androidboot.console=ttyS0
printenv
...
commonbootargs=console=ttyS0,115200n8 initrd rw init=/init vram=16M video=omap3epfb:mode=800x600x16x14x270x0,pmic=tps65180-1p2-i2c,vcom=-1670 androidboot.console=ttyS0
...
saveenv
but still no success with proper boot - tablet is bricked
looks like some case before u-boot (battery (pmic), mmc?)
should I replace whole boot partition with backuped one?
There was a whole thread on this but I can't seem to find it right now.
Click to expand...
Click to collapse
I think maybe You mention this thread: [Solution]Yet another way to unbrick: unplug the battery for a while and further Aqq123 u-boot logic explanation

I'm confused what your present situation is.
You say that you blew out UART1 but then you have access to the u-boot console.
You say it's bricked, but you're not explicit where you are hung up.

Renate NST said:
I'm confused what your present situation is.
You say that you blew out UART1 but then you have access to the u-boot console.
You say it's bricked, but you're not explicit where you are hung up.
Click to expand...
Click to collapse
Sorry for being unprecise, troubles make me alvays littlebit in blue mood.
I have two nooks: working NSTG with blown uart0 RX and (currently) bricked NST.
Lets forget about NSTG - its not a topic of my mess
With the NST I was try to play with u-boot settings - swapping ttyS0 to ttyS1.
Currently, access to NST is possible only when boots from NookManager SD card.
I can break (from PC terminal) this SD boot and stay in u-boot console, change and save settings.
But after that , NST still cannot boot without SD card inserted.

So you are using an NST with a 1.8V level converter?
(The UART numbering is per the chip datasheet, starting at 1. The ttyS start at 0.)
I'm not familiar with the Nook Manager, never tried it.
Have you tried the old Noogie?
Can you see/fix what is broken on the internal EMMC?

Renate NST said:
So you are using an NST with a 1.8V level converter?
(The UART numbering is per the chip datasheet, starting at 1. The ttyS start at 0.)
Click to expand...
Click to collapse
Yes, I have level converted/available both of UARTs.
Have you tried the old Noogie?
Click to expand...
Click to collapse
Not yet. I will try to see the difference.
Can you see/fix what is broken on the internal EMMC?
Click to expand...
Click to collapse
I can mount mmcblk0p1 - boot partition via NookManager's ADB, so I assume eMMC is not broken.

ucy74 said:
I can mount mmcblk0p1 - boot partition via NookManager's ADB, so I assume eMMC is not broken.
Click to expand...
Click to collapse
Well, I meant that all the files in the boot partition are correct/ok.
If you have the console connected, then you can see where it's dying. Where?
I've had my head deep in the NTX readers (Nook, Kobo) so I've forgotten lots about the NST.
Don't you think that the NST is getting awfully old now?
Maybe time to upgrade?

If you have the console connected, then you can see where it's dying. Where?
Click to expand...
Click to collapse
I was thinking rather about wipe/replace boot partition - if the source of trouble was changing u-boot setenv.
Unfortunately I have only NSTG not NST working boot partition dumped for backup.
I was checking dumping bad NST partition against working NSTG boot backup.
There are differences in MLO, u-boot.bin, uImage, uRamdisk, uRecImg, uRecRam and romrestore.zip
This is quite predictable.
I was checking file from mdall's post - Need help for my NST to, with same differencies.
It may be question of version differ: my NST is 1.2.1 - mdall's files are from 2011...
Update:
I was prepared SD card with my bad boot partition - NST was not booting.
Then replace original MLO on SD card to MLO taken from mdall's boot files.
After that NST was booting from SD, load kernel, shows "starting up" image and finally power off failing install stg with "Install Failed" screen
So, looks like bricking may be original MLO trouble.
There will be some pmic (power chip) setup case because battery starts to charge only when boot from SD.
DONE!!!
NST is going back to life - it was the bad MLO case.
I've had my head deep in the NTX readers (Nook, Kobo) so I've forgotten lots about the NST.
Click to expand...
Click to collapse
Nook Glow Plus isn't available for sale outside US. Kobo Clara was seen in europe. Kindle wins.
Don't you think that the NST is getting awfully old now?
Maybe time to upgrade?
Click to expand...
Click to collapse
Well, question of sentiment to stuff which works, has been (at his time) well designed and had known guts...

bump
So maybe somebody has downloaded toolchain from past times to compile B&N sources.
Or can share link to downloadable one?

Try these (I haven't tested them, but they seem to be the original files):
Source: https://sourcery.mentor.com/public/gnu_toolchain/arm-none-linux-gnueabi/arm-2010q1-202-arm-none-linux-gnueabi.src.tar.bz2
Linux x86: https://sourcery.mentor.com/public/gnu_toolchain/arm-none-linux-gnueabi/arm-2010q1-202-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2
Windows x86: https://sourcery.mentor.com/public/gnu_toolchain/arm-none-linux-gnueabi/arm-2010q1-202-arm-none-linux-gnueabi-i686-mingw32.tar.bz2