FORUMS

Analysis & Opinion

Top Forum Discussions

Nook Touch kernel hacking

602 posts
Thanks Meter: 3,470
 
By texasice, Retired Recognized Developer on 5th October 2011, 08:23 PM
Post Reply Subscribe to Thread Email Thread
1st February 2012, 03:04 AM |#61  
Senior Member
Flag California
Thanks Meter: 515
 
More
It'd be nice if we could get one of these kernels running with underclock below 300 and overclock above 600. Just an idea though.
 
 
24th February 2012, 07:44 PM |#62  
Senior Member
Thanks Meter: 21
 
More
Quote:
Originally Posted by sokoow

Positive side effect of all of this is that now I've quite rich kernel with :
- CFQ iosched
- reiserfs/ext4/ntfs enabled
- DroidWall support (iptables match target)
- Group process scheduling
- UTF8 enabled (can't switch to it entirely cause B&N stuff uses non utf all around the place)
- half of kernel debugging off
- PM debug off
- fastfpe works quite fine
- ondemand cpu governor

If anybody was interested in config or binaries then give me a shout please. I really need somebody to give me a hand with SGX and WLAN sources in order to push it forward.

Is this modified kernel stable for normal, day-to-day use? How difficult would it be to install this modified kernel on a rooted NST? Are you able to sync with google contact with no additional hack?

I really miss droidwall. Google contact would be a huge bonus :) I can follow instruction but I'm not a developer/hacker :(

Thanks!
25th February 2012, 12:45 PM |#63  
Renate NST's Avatar
Recognized Contributor / Recognized Developer
Boston
Thanks Meter: 880
 
More
Getting all the debug messages on the graphic systems turned off would make life easier when dealing with logcats. Filtering always makes you lose something important.

Also: I got my old Microsoft USB GPS block to spit out stuff using USB host mode.
The baud rate on the driver defaults to 9600. I got my NMEA data, I just need to get a LocationProvider.

http://forum.xda-developers.com/show....php?t=1457971
Last edited by Renate NST; 26th February 2012 at 06:00 PM.
27th February 2012, 12:41 AM |#64  
Member
Thanks Meter: 13
 
More
Guys what a cliff hanger this thread is, everyday I wake up hoping you guys got all the bits put together, and that we all can install custom roms, and icecream, and... :)~~
5th March 2012, 09:27 AM |#65  
Junior Member
Flag Dublin
Thanks Meter: 6
 
More
All,

I'll try to post all needed files together with some instructions as a separate thread. Hopefully will manage to do it later this week. I've been using it for quite a while now - seems to be stable. Hopefully we'll move it a bit further, but it's already hard as there's half of sources missing.

Greetings, Karol
The Following User Says Thank You to sokoow For This Useful Post: [ View ]
6th March 2012, 04:20 PM |#66  
Senior Member
Thanks Meter: 22
 
More
no-refresh implementing?
Any chance of implementing "always on" and "contrast settings" for no-refresh from http://forum.xda-developers.com/show....php?t=1502723
Last edited by mrWax; 6th March 2012 at 04:24 PM.
25th March 2012, 01:09 AM |#67  
darkguy2008's Avatar
Senior Member
Flag Caracas
Thanks Meter: 232
 
Donate to Me
More
Hey guys, I read the whole thread and this all seems very interesting.

I know a lot of coding, but alas, compiling a kernel always makes me rip my hair off because it never works .

Anyways, I'd be really glad if someone here could provide me a small guide on how to get on compiling the B&N source code (nook2_1-1.tgz) and installing it on my device (or SD card, as I saw on a post around the first pages)... I see lots of theories and verbose info, which is useful, but nothing that I can really understand.

Like... a toolchain? what's that? how do I get it? I've heard about codesorcery, okay cool, which one to download? latest one or the one it says in the OMAP wiki? what to do after I download & extract it? where to put the B&N source code?... stuff like that, you know...

Not everybody knows how to compile this, yet they know how to code. I could give you guys a hand in this as I want a custom ROM for my NST, but it's impossible if I can't build a ROM/kernel for saving my own life, and there is no step-by-step guide, as most stuff assumes the user already knows things :/.

Thanks in advance!
- DARKGuy

---
EDIT: Nevermind, I found this -> http://nookdevs.com/Nook_Simple_Touch/Kernel . Let's see how it goes...

---
EDIT 2: Okay, compiled very well, woo-hoo!

I need to find out how to put it in though. I'm making a SD card now to give my compiled images a try, however, I have a question:

The only way to modify init.rc is to unpack the already-built uImage? isn't there a way to edit it before compiling? how are those files generated anyways, if they don't exist in the filesystem?

---
EDIT 3:

I also followed the instructions here: http://forum.xda-developers.com/show...7&postcount=44 to build a bootable SD card. It seems to boot, but it doesn't mount /system correctly.

ADB seems to work, but it doesn't output anything:

Code:
darkguy@cave:~/dev/nst/src/fullImg$ adb devices
List of devices attached 
XXXXXXXXXXXXXXXX    device

darkguy@cave:~/dev/nst/src/fullImg$ adb logcat
- exec '/system/bin/sh' failed: No such file or directory (2) -
Any ideas?
Last edited by darkguy2008; 25th March 2012 at 02:33 AM.
26th March 2012, 05:39 PM |#68  
darkguy2008's Avatar
Senior Member
Flag Caracas
Thanks Meter: 232
 
Donate to Me
More
BumpBumpityBump.

I hate bumping, but I'm not the only one in this thread.

Also, I checked the mmcblk0 & 1 with fdisk -l when inserted into the nook and both numbers and sizes are the same.
27th March 2012, 05:56 PM |#69  
darkguy2008's Avatar
Senior Member
Flag Caracas
Thanks Meter: 232
 
Donate to Me
More
Bumpin'TheBumpityBumpBump thread.

Man, this thread is active like hell. It sure motivates me to keep working on this -.-"
The Following User Says Thank You to darkguy2008 For This Useful Post: [ View ]
27th March 2012, 06:21 PM |#70  
Senior Member
Thanks Meter: 137
 
Donate to Me
More
Quote:
Originally Posted by darkguy2008

EDIT 2: Okay, compiled very well, woo-hoo!

I need to find out how to put it in though. I'm making a SD card now to give my compiled images a try, however, I have a question:

The only way to modify init.rc is to unpack the already-built uImage? isn't there a way to edit it before compiling? how are those files generated anyways, if they don't exist in the filesystem?

init.rc is in the uRamdisk not the uImage and uRamdisk doesn't get generated when you compile the kernel, but when your make build a complete android system. So the easiest way is to unpack the uRamdisk, make your changes and repack it.
Quote:

---
EDIT 3:

I also followed the instructions here: http://forum.xda-developers.com/show...7&postcount=44 to build a bootable SD card. It seems to boot, but it doesn't mount /system correctly.

ADB seems to work, but it doesn't output anything:

Code:
darkguy@cave:~/dev/nst/src/fullImg$ adb devices
List of devices attached 
XXXXXXXXXXXXXXXX    device

darkguy@cave:~/dev/nst/src/fullImg$ adb logcat
- exec '/system/bin/sh' failed: No such file or directory (2) -
Any ideas?

I never tried it this way. The easiest solution is to create a noogie sd-card and replace the uImage on the /boot-partition. If I remember correctly it should also be possible to put your kernel and a uRamdisk from the nook (not the one included in noogie) on the sd-card, this way the uRamdisk and the uImage from the sdcard are used, the rest of the system gets booted from the internal memory.
The Following User Says Thank You to mali100 For This Useful Post: [ View ]
28th March 2012, 02:30 AM |#71  
darkguy2008's Avatar
Senior Member
Flag Caracas
Thanks Meter: 232
 
Donate to Me
More
O hai!

Thanks for the prompt reply! here are my comments ^^.
Quote:
Originally Posted by mali100

init.rc is in the uRamdisk not the uImage and uRamdisk doesn't get generated when you compile the kernel, but when your make build a complete android system. So the easiest way is to unpack the uRamdisk, make your changes and repack it.

Oh okay, that explains a lot. It seems I was unpacking the wrong files which were so hard to unpack I couldn't unpack them. I guess the uImage is a binary kernel not able to be unpacked? I tried lots of cpio/gunzip commands and scripts online to unpack u-boot files but they didn't work .

I have a question now though: In order to get the uRamdisk, I need to build an android system. The thing is... B&N didn't give sources for an android version, it seems. They only gave sources for a kernel, which is okay but it isn't enough (I think??) to build an android filesystem from the ground zero, right?

I'm wondering, if I want to build Eclair (for example, which is the current working version in the NST), which config should I use? I've seen I could use something like "encore" or "zoom2" (as the same build.prop in the NST states, "zoom2") to build /system and mix it with B&N's kernel? or am I wrong? my objective is to build, aside from a kernel, a pure android ROM too.
Quote:
Originally Posted by mali100

I never tried it this way. The easiest solution is to create a noogie sd-card and replace the uImage on the /boot-partition. If I remember correctly it should also be possible to put your kernel and a uRamdisk from the nook (not the one included in noogie) on the sd-card, this way the uRamdisk and the uImage from the sdcard are used, the rest of the system gets booted from the internal memory.

Hm, but that would still run /system from the nook. My idea was to make a SD that would boot -and- use the files from itself instead of touching the NST's files. That way, I could happily work on a custom android version without having to mess with my NST's filesystem and risk messing it up and having to restore it again with dd.

Read More
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes