[Nook HD/HD+] Ubuntu Touch 13.10 "Saucy" [Project Abandoned]

2390 · Oct 1, 2013

I've just been following the porting guide here https://wiki.ubuntu.com/Touch/Porting it says that is is updated for the 13.10 images, so when I finish, I'll let you know how it goes. If it works, I'll start a thread

Deleted member 2092952 · Oct 1, 2013

2390 said:
I've just been following the porting guide here https://wiki.ubuntu.com/Touch/Porting it says that is is updated for the 13.10 images, so when I finish, I'll let you know how it goes. If it works, I'll start a thread

yes. at the top of the guide is wip and has the todo and notes section which you will need to follow describing booting information you will need.

2390 · Oct 1, 2013

sandsofmyst said:
yes. at the top of the guide is wip and has the todo and notes section which you will need to follow describing booting information you will need.

Hmmm. Has anybody made progress on that? Could we use the boot.img from a working cm10.1?

Deleted member 2092952 · Oct 3, 2013

2390 said:
Hmmm. Has anybody made progress on that? Could we use the boot.img from a working cm10.1?

Had tried that. Made it a bit further but still failed hard. Did check adb which did not start yet, but don't remember checking for kmsg - probably wouldn't exist anyway as have not seen one yet.

2390 · Oct 3, 2013

I can't even figure out how to get the image compiled. I can't find the right files, or anything. I'll probably start from scratch when it is officially released

Deleted member 2092952 · Oct 4, 2013

If you pulled in all the files at the start of the guide (not missed anything), its all setup quite good. Don't need any .repo changes and very few code changes for building:

The problem is that you need the blobs which are obtained from unzipping the cm device build (manually; via script [via adb] appears to be a bit broken - though playing around with it can help you find the vendor directory locations?) and bt proprietary files from the internet in order compile it. These files go in specific directories inside the vendor dir.

I also needed an entire directory from google. Its actually there already but for whatever reason different and breaks compiling at the end.

...oh, some code additions too to add in device directories like the guide says.

If it asks for a file called empty or whatever it was called, just create an empty file or search and copy one of the others which are 0 bytes anyway... and that's all it needed there.

There probably are a few more files to add in along the way.

this patch was needed as well http://paste.ubuntu.com/5883021/

That might be it.

2390 · Oct 4, 2013

sandsofmyst said:
If you pulled in all the files at the start of the guide (not missed anything), its all setup quite good. Don't need any .repo changes and very few code changes for building:

The problem is that you need the blobs which are obtained from unzipping the cm device build (manually; via script [via adb] appears to be a bit broken - though playing around with it can help you find the vendor directory locations?) and bt proprietary files from the internet in order compile it. These files go in specific directories inside the vendor dir.

I also needed an entire directory from google. Its actually there already but for whatever reason different and breaks compiling at the end.

...oh, some code additions too to add in device directories like the guide says.

If it asks for a file called empty or whatever it was called, just create an empty file or search and copy one of the others which are 0 bytes anyway... and that's all it needed there.

There probably are a few more files to add in along the way.

this patch was needed as well http://paste.ubuntu.com/5883021/

That might be it.

My laptop is acting weird, but I could post the files, it whatever you need from my nook, which is on cm10.1. Just let me know what to do.

Deleted member 2092952 · Oct 8, 2013

So porting the latest builds... well, its a bit complicated. So complicated in fact that this guy for a different device doesn't want say how he did it. http://www.oppoforums.com/threads/q-ubuntu-touch.3908/page-8

I will try a bit more but so far booting remains broken and probably will remain so.

2390 · Oct 8, 2013

Here is the thread from that guy. http://www.oppoforums.com/threads/wip-dev-ubuntu-touch-13-10.6109/ we may be able to port that, since he got that working. Is that feasible?

wesnoth · Oct 8, 2013

I have created bootable system image. It start form sdcard. Works only base system, adbd and android into lxc (display, touch, wifi, etc don't work). If anybody can rebuild system in right way (because I used some file from cyanogenmod without rebuild, ex.: libwpa_client.so, libhardware_legacy.so) I can write how to create bootable sdcard.

UPD:

Look here: http://xdaforums.com/showpost.php?p=46312567&postcount=31

Deleted member 2092952 · Oct 8, 2013

2390 said:
Here is the thread from that guy. http://www.oppoforums.com/threads/wip-dev-ubuntu-touch-13-10.6109/ we may be able to port that, since he got that working. Is that feasible?

Guess there could maybe be a way to drop in certain files but if any of the changes for fixing boot are ones with device specific code... I might not know where to look. I still am not good with github but will check out his code over the next few days. Thanks :good:

edit: Briefly browsed the files. Some interesting bits. Will test this stuff starting tomorrow.

wesnoth · Oct 9, 2013

OK. I created bootable emmc image. All what we need is:

green loader : http:goo.gl/ki9xez,
mkbootimg: http:goo.gl/Tx4vz5",
kernel and ramdisk.img from your ubuntu-touch build directory.

Next, create boot.img with mkbootimg:

Code:

mkbootimg --kernel kernel --ramdisk ramdisk.img --base 0x80000000 --cmdline 'androidboot.console=ttyO0 console=ttyO0,115200n8 def_disp=lcd2' --pagesize 4096 -o new_boot.img

After, concat green loader and new_boot.img:
Code:
```
cat new_boot.img >> head.img
```
, and replace boot.img in zip update file with just created.
Flash zip file from recovery
Reboot device
adb push android-ramdisk.img /boot/

It work, but looks ugly.

wesnoth · Oct 9, 2013

Some photos. Image does not fill the entire screen and not fully visible. Touch and wifi works.

UPD: +1 screenshot with ro.sf.hwrotation=0; screen now is fine, but touch is rotated

jpisini · Oct 9, 2013

Looks like you are getting close. Good work.

Sent from my PC36100 using xda app-developers app

gmicalzoma · Oct 9, 2013

This is Exciting!!! For now I have settle for Stock Rom with unknown sources and root enabled (thanks lepinlar & verygreen) using Next Launcher and it runs faster than any other ROM I have tried on SDCARD or EMMC (CM 10.1, CM10.2, Carbon and Xperia Carbon) on my Nook HD+

But Ubuntu is what I'm waiting for! I like using linux on the Desktop (PinguyOS) and on Server (CentOS 6) so can't wait for Ubuntu Touch to be available for the Nook HD+!!!

Thanks in advance to all that are working hard to get this available :good:

2390 · Oct 9, 2013

Good. I don't know much about coding, but I could test. I also tend to be really obsessive so I will be researching this every day.

Deleted member 2092952 · Oct 10, 2013

Well, learned more but nearly out of ideas again. Nothing I tried from looking at that devices code has done a single thing.

Might try pinpointing the exact problem in the next few days otherwise right now possibly will wait until the next port guide revision and hope it works then.

Edit: Progress ?

The fstab file the port guide talks about wasn't being included in the android-ramdisk.img. Has to be manually added. D'oh! Guess I finally know where the note in the guide was actually talking about. Reading it still confuses me. lol.

It has lengethened the boot time from 7 seconds to nearly 11 (my timing could be off a bit). So still something going on. Still nothing in the logs. But sweet progress.

Edit: I don't know if the fstab.$device file is good or not for booting. Devs of working ports have it included yet touch chat (maining list?) public entries has someone saying to get boot working first and not to worry about that file. All my tests with it failed yet all tests without it fail.

2390 · Oct 10, 2013

Yay we got a bootable build working! We just need to get the files together and make a thread for this.

Deleted member 2092952 · Oct 11, 2013

2390 said:
Yay we got a bootable build working! We just need to get the files together and make a thread for this.

I didn't notice that before my post. lol.

wesnoth said:
Some photos. Image does not fill the entire screen and not fully visible. Touch and wifi works.

UPD: +1 screenshot with ro.sf.hwrotation=0; screen now is fine, but touch is rotated

Good stuff and good work wesnoth.

But, is that for the flipped build or old non-flipped preview? Don't see anything there for the flipped builds as the boot.img isn't all that's needed.

wesnoth · Oct 11, 2013

System in photos from other thread is flipped (android into lxc).
There are no fstab required into android-ramdisk.img.
70-ovation.rules was created with command from manual (http: goo.gl / 1XsLAC).
Other files (like bluetooth-touch-ovation.conf, ubuntu-touch-session.d/ovation.conf) was created as as copy of existed defaults.

P.S. While I have less then 10 posts, I cant create posts into developer threads. Thats why I will create them into "general" thread.
P.P.S. I will upload bootable image after fixing reversed touch (accelerometer is done)

[Nook HD/HD+] Ubuntu Touch 13.10 "Saucy" [Project Abandoned]

Senior Member

Deleted member 2092952

Guest

Senior Member

Deleted member 2092952

Guest

Senior Member

Deleted member 2092952

Guest

Senior Member

Deleted member 2092952

Guest

Senior Member

Member

Deleted member 2092952

Guest

Member

Member

Attachments

Senior Member

Member

Senior Member

Deleted member 2092952

Guest

Senior Member

Deleted member 2092952

Guest

Member

Similar threads

Top Liked Posts