Database Develop

[ROM][P6800][OnHold]Ubuntu-touch dev preview(18.03.2013)

I have put this project on hold for now. I flashed latest Austrian ICS build to my device and continue using it as my Kindle reader on my travels. IF somone manages to fix the two issues with kernel, send me a message and I'll continue working with the repository. But for now I'm not thinking nor touching the subject before Easter. Thank you for participating for now
I've started porting Ubuntu-touch dev-preview to the Galaxy Tab 7.7 (3g). If you do not understand it already, you flash this at your own risk. There is now also a Ubuntu-touch specific device page here: https://wiki.ubuntu.com/Touch/Devices/p6800. I'll try to keep this thread and the Ubuntu devices page as close to each other as possible.
Big thanks to Daniel_hk for helping with boot.img Now It can be booted, but the screen is still black
Also, without working wifi and display, the preview is basically unusable... Next steps should be these:
1. Get wifi drivers working.
2. Get display drivers working.
Code:
[email protected]:/# uname -a
Linux localhost 3.0.15-CM-g1dc3074 #2 SMP PREEMPT Wed Mar 13 00:43:37 EET 2013 armv7l armv7l armv7l GNU/Linux
Repositories:
Latest release tagged with: "v0.3", not tested!
https://github.com/dun1982/android_device_samsung_p6800
https://github.com/dun1982/android_kernel_samsung_p6800
Download
cm-10.1-20130312-UNOFFICIAL-p6800.zip
Daily Ubuntu image: http://cdimage.ubuntu.com/ubuntu-touch-preview/daily-preinstalled/current/
Installation
Install CWM 6.0.2.8
Wipe data/factory reset
Wipe cache partition
Flash cm-10.1-20130312-UNOFFICIAL-p6800.zip to device
Flash quantal-preinstalled-phablet-armhf.zip to device
Reboot
Starting to use
Then it gets interesting (Black sreen for now now Run the following commands in your desktop system:
Code:
adb root
adb shell
ubuntu_chroot shell
You should have now root access inside your tabled. Continue with this wiki next
What works
Ubuntu-touch dev-preview is flashable.
It boots!
Known Issues
Kernel is based to the CyanogenMod/android_kernel_samsung_smdk4210, but it is a mess. So forked it, took code here and there (mostly from locerra's JB build).
Kernel is based 3.0.15 and no newer one available (yet).
Most of the drivers in kernel had to be turned off, because build was not succeeding...
bluetooth: Doesn't work
audio: Dock audio doesn't work.
hwcomposer: HDMI dongle doesn't work.
wifi: Doesn't work.
camera: Doesn't work.
.. and lot of kernel level bugs for sure.
Displaydrivers are not working (yet).
Release notes
Version 0.2 (13.03.2013) - Now it boots, see release notes
Version 0.1 (07.03.2013) - Intial release, nothing works
Credits
BIG THANKS to daniel_hk for solving the boot.img problem for me.
Anyone who has worked previously with the device/kernel source.
locerra (for getting CM10.1 to flashable state).

wowww!!! thank you !test now:victory::victory:

Placeholder for future.

Re: [ROM][P6800]Ubuntu-touch dev preview(02.03.2013)
Not 6810 versión?
AUs

el_campi said:
Not 6810 versión?
AUs
Click to expand...
Click to collapse
I cannot test it for anything else. The kernel sources are from CM10.1 that was in use from locerra, so in theory it should work with i815 and with p6810 as well. But I cannot give you any guarantees...
And also before I get this build to even start with my device, I do not think that sharing image would help anyone. But if you are a developer, I would like to talk with you on issues that I might have missed or done wrong. So contact me

Re: [ROM][P6800]Ubuntu-touch dev preview(02.03.2013)
any update?
Sent from my GT-P6800 using xda premium

Not much. The generated image is missing /data/ubuntu completely and that is the reason why the image does not boot. I got also flu and fewer, so I have had not that much time after the weekend to look on the issues on that.
I'm also waiting if I get any answers from Ubuntu touch emailing list regarding the problem and where to look for answers, but my quess is that it has something to do with the devices fstab file...

Good news everyone!
Just got a very good answer the problem I had with the /data/ubuntu-folder missing from the image. There was no image provided for the actual Ubuntu at all by the build-process...
When I get home from work, I'll try to find time to look into the build process if I can include the actual Ubuntu image to the ready made image and then release it after I get my device to boot. But it seems that I got the right nudge forward for this now :highfive:

Hmpf, still not booting. Now the /data/ubuntu logs are unmodified, which would point towards kernel or fstab-issue (ie. /data/ubuntu is never used...).

Re: [ROM][P6800]Ubuntu-touch dev preview(02.03.2013)
Good job :thumbup::thumbup::thumbup::thumbup::thumbup::thumbup:
Sent from my GT-p6800 using xda premium

Doh... still not working... Any ideas anyone?

Ok, new version build from different repositories (thx, danile_hk for tip).
I'll test the new image this evening when I get back to home, and I have my fingers crossed that I can get the device to boot up and even display something useful. After that I can start looking for ubuntu developemnt

New version did not work, but then Daniel_hk gave me working boot.img. So now I need to find out what the heck is wrong with my repository and fix it so that I can get working boot.img from start and also the device configuration has issues. Both repositories are currently out of sync I'm afraid

dun1982 said:
New version did not work, but then Daniel_hk gave me working boot.img. So now I need to find out what the heck is wrong with my repository and fix it so that I can get working boot.img from start and also the device configuration has issues. Both repositories are currently out of sync I'm afraid
Click to expand...
Click to collapse
Also, without working wifi and display, the preview is basically unusable... Next steps should be these:
1. Get wifi drivers working.
2. Get display drivers working.

It seems that I hit the wall (again) with the mentioned big issues.
For now, I keep some sabbatical from Ubuntu Touch things (ie. I flashed ICS Austria to my device) and use it as my Kindle reader again.
If by miracle I get more info regarding how to get the Kernel working with Ubuntu Touch, then by allmeans I continue working with this project. So far it just seems that making a working image, is out of my hands currently.

At least you had a go. Thanks for your efforts, and hope you might have another crack at it later on.
I'm feeling a little bit that way right now too, and put my ICS kernel on the back burner. I think I'm trying to multitask a little too much at times....
Yep, a break is what you need, maybe some clarity will come after you've had a chance to recharge.
Sent from my GT-I9300 using xda premium

It's very nice to see you took up the big responsibility to make this superb device to be usable again! it has great specs, really. KUDOS bro!!

Any update on this development?

ZhenMing said:
Any update on this development?
Click to expand...
Click to collapse
Not much, I have had no interest to spend time with this topic because I have been very busy IRL. After I get my new house renovated fully and get my job tasks done, I wont be spending much time with this project. Feel free to use any sources provided in this thread to further advance the subject.
But this wont go forward that much, if the GT-P6800 wont get official CM10.1 update...

It works?

[ROM/KERNEL] OFFICIAL CM10.1 + 3.0.50 Kernel for Kindle Fire 2 [CM NIGHTLIES]

*** USE AT YOUR OWN RISK! WHILE I TRY MY BEST TO PROVIDE WORKING KERNELS/ROMS, I AM NOT RESPONSIBLE IF THIS SOFTWARE OR ANYTHING I'VE WORKED ON SUDDENLY FRIES YOUR DEVICE. ***
THIS ROM REQUIRES A 2ND-BOOTLOADER / RECOVERY BE INSTALLED ON YOUR KINDLE FIRE 2. FOLLOW INSTRUCTIONS HERE:
http://forum.xda-developers.com/showthread.php?t=2100963
*** READ CAREFULLY BEFORE DOING ANYTHING ***
*** Kindle Fire 1st-gen ROMs/KERNELS are *NOT* compatible with the Kindle Fire 2.
ONLY FLASH ROMs/KERNELS that are made for the Kindle Fire 2. ***
Month "stable" Snapshot CM builds:
Monthly "Stable" Builds
Nightly CM Builds:
Nightly Builds
Latest GAPPS:
http://goo.im/gapps/gapps-jb-20130301-signed.zip
Older builds are found here:
http://goo.im/devs/Hashcode/otter2/
CHANGES:
[05/14] New audio driver (WIP)
[03/27] Reboot Recovery mode is now fixed
[01/17] Updated SGX/PowerVR driver to latest binaries from omapzoom (still showing [email protected])
[01/15] CM10.1 updates + reverted some USB changes in the kernel for sleep testing
[01/07] Battery life / sleep improvements
[01/06] Update to 3.0.50 kernel
[01/06] Update wifi firmware to R5.SP3.06
[12/16] Fixed Deep Sleep
[12/15] Added multi-profile fix
CURRENT KNOWN ISSUES:
The headphone MIC input is not functioning correctly yet. Work in progress.
Virtual keyboard input on Jellybean is terrible. Needs a protocol update or something. Fixing. For now use an alternate keyboard like Swype
KERNEL FEATURES:
[01/06] Mainline version updates to 3.0.50 updated to current with Google's kernel/common
[01/06] WLAN Firmware R5.SP3.06
[11/07] Updated to SGX/IMG DDK [email protected] for Android (via omapzoom 18 hours ago)
[11/07] WLAN Firmware R5.SP3.03
[09/05] Updated to SGX/IMG DDK [email protected] for Android
Based on TI kernel 4AI.1.7 (3.0.31 mainline) which supports 512M memory mapping needed by the Kindle Fire
DEVS
BUILDING THIS ROM:
First, read through Google's Android website about "how to setup a build environment":
http://source.android.com/source/initializing.html
Then you can setup the Kindle Fire by doing the following:
mkdir android
cd android
(Use main repo for CyanogenMod 10.1)
repo init -u https://github.com/CyanogenMod/android -b cm-10.1
repo sync
vendor/cm/get-prebuilts
. build/envsetup.sh && brunch otter2
RESERVED FOR NOTES

RESERVED

So does the mic input not work At all or is it off and on?
Sent from my SAMSUNG-SGH-I717 using xda premium

The MIC needs some kernel changes in the sound driver.

The gapps link doesn't work
Sent from my SAMSUNG-SGH-I717 using xda premium

rkingsparx81 said:
The gapps link doesn't work
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
http://goo.im/gapps/gapps-jb-20130301-signed.zip

Thanks
Sent from my SAMSUNG-SGH-I717 using xda premium

It was taking me to the gapps page on goo.im (which was intended), but I went ahead and edited it to be the latest file.

Been running since the first un-offical builds, been running the offical for a few weeks now, been running like a charm.
Just an FYI, On my device when I try to reboot to recovery, the device just reboots in to android.
Edit; Brief video for you, as you can see it reboots like normal (Sorry for the background noise!)
http://www.youtube.com/watch?v=9vyr_zya5dQ

Flashed 04.04.13 and all is good the weather on the lock screen is now displayed it didn't work for me on the 03.04.13
Sent from my Amazon Kindle Fire2 using xda premium

Yeah, one of the funny bits with installing Nightlies is that randomly stuff will break. I try and keep track of which has the most working as I'm moving along so that I can revert to a more "stable" version if needed.

Hashcode, will we get the m3 build?
Gesendet von meinem Amazon Kindle Fire2 mit Tapatalk 2

Thank you so mutch .just downloaded the m3 build. So nice to have you.
Gesendet von meinem Amazon Kindle Fire2 mit Tapatalk 2

Yeah we weren't on the original M3 list so I had to get added and for a re-run that the CM team did a day later.
From now on, we should be on the right list to get the monthly stable builds.

Hashcode, there is a little problem with the naming of our otter2 device. It shows me on the get.cm site that this is a kindle fire hd.

Yep, i reported it yesterday.
Sent from my DROID RAZR HD using Tapatalk 2

Building CM10.1 from source
Hashcode, I have successfully built CM10.1 from source for the otter2 by following the instructions in this thread and the CyanogenMod wiki. Thanks for the great work.
However, I did have a couple of issues that I had to work around. I'm not sure if it's because I did something wrong or because there is a problem. When I got to the "Extract Proprietary Blobs" section and ran the device/amazon/otter2/extract-files.sh script, I received an error message saying that the lib/hw/sensors.otter.so file couldn't be found. I poked around the filesystem on my KF2 (running CM10.1 nightly cm-10.1-20130411-EXPERIMENTAL-otter2-M3), and found that there was a lib/hw/sensors/otter2.so file.
Similarly, the file vendor/amazon/otter2/otter2-vendor-blobs.mk also contained the reference to otter rather than otter2, and caused a problem later in the build cycle.
By changing the otter to otter2 in both device/amazon/otter2/proprietary-files.txt and vendor/amazon/otter2/otter2-vendor-blobs.mk, I was able to get the build to complete successfully. Is this a known issue or did I do something wrong?
Thanks.

I noticed i only have 673 total ram with this rom...my ram has been stolen lol...I flashed from this cm10.1 to stock rom, and on stock ram shows right.. around 924 total.. but with this rom im missing ram, i only have 673 total.. Possible bug? What is the cause an how can i fix this?

Newest nightlies will include an all new audio driver in the Android OS. It works, but it's not finished (no MIC support yet).
I'll try and keep this updated as testing continues.

Did anyone else have issues with the last nightly not booting? I tried flashing 17 twice but kept letting stuck at the boot logo. Flashed 15 back again and up and running again.
Sent from my Amazon Kindle Fire2 using Tapatalk HD

[ROM][DEV] Ubuntu Touch For B&N Nook Tablet

DISCLAIMER: You should know by now that anything you do can and probably does void warranties, can and may brick your devices, etc etc yada yada.... This is my first ever attempt at a port, second ROM to ever build. The base for this is CM10.1 maintained by the official devs for the B&N Nook Tablet (acclaim), so complete props to everyone who has gone looney to get us here. This port isn't very usable and as such is no daily driver by any means.
I will try to explain the details of building as best as I can remember to anyone who wants to know. I had to comment out certain lines here and there and add my changes below them. Being new to this all, I have yet to set up a git for the sources. I just wanted to get this up as I haven't seen anyone else post this for Nook Tablet. From what I know, this should work for the 8g and 16g as this is based off the Official CM10.1 for us. Again, your risk, there are plenty of ways to unbrick this device and plenty of guides.
Discussion thread:
[ROM][DISCUSSION] Ubuntu Touch B&N Nook Tablet
For those of you just wanting to take it for a spin:
(name change as I am building using two different sets of repos, one with only a local branch based off the cm repos, and my own that I will push updates to)
Download Device Specific Build:
Build 5: ut-cm-20130610-acclaim.zip - 35.72 MB
Older Builds:
(The following builds screen displays stop working for newer Ubuntu fs builds)
Build 4: ubuntu_touch-20130529-acclaim.zip - 35.54 MB
Build 3: ubuntu_touch-20130524-acclaim.zip - 34.94 MB
Build 2: ubuntu_touch-20130513-acclaim.zip - 34.90 MB
Build 1: ubuntu_touch-20130511-acclaim.zip - 34.90 MB
Download Ubuntu FS File:
Saucy is the new Raring
http://cdimage.ubuntu.com/ubuntu-touch-preview/
Installation:
1) put both files on your sdcard by your method of choice
2) go into recovery
3) format data/factory reset <-- NOTE: If you want to save data, new builds should backup stuff, not sure what all though.
4) format system to ensure clean install
5) flash Custom build and flash Ubuntu fs file
6) reboot and pray it works.
After boot up notes:
- May have to push power button to get initial display.
-To get a chroot shell from your computer's terminal:
Code:
$ adb root
$ adb shell
$ ubuntu_chroot shell
- Keyboard does not currently work on Home screens. In Raring I would restart ubuntu-session. I do not see it in Saucy. 2013-06-15: playing around and starting the 'killprocs' service, keyboard worked afterwards.
Code:
[email protected]:/# service killprocs start
- Wifi seems to need a reboot to work correctly currently
- Added a script to change the display size.. If you do not like it or want to mess around with it, you can adjust the display through the chroot by editing the acclaim.conf file. After editing, reboot.
Code:
/etc/ubuntu-session.d/acclaim.conf
Build notes!
Build 5:
- Updated ubuntu sources, resulting display seems fixed for newer builds! (circa June 1st or maybe a little sooner)
- Honestly not sure atm if build 4 has it, but added a script to auto fix the display size (adds acclaim.conf for you), Saucy images seem to not require a reboot, Raring images do (or an ubuntu-session restart).
Build 4:
- Using wpa_supplicant 8 instead of 8_TI
Build 3:
- Wifi works with some terminal junk!
Build 2:
- Videos stopped working for some reason, need to debug.
- Apps no longer force close
- Wifi still down
Build 1:
- It boots
- Display works
- Sound Works
- Videos Work
- No wifi
- All apps force close after a couple of seconds
- No rotation
I'm new to all this git stuff, but figured I'd try it out:
https://github.com/dejello/android_device_bn_acclaim
https://github.com/dejello/android_kernel_bn_acclaim
I will be adding a wiki or readme on the device repo that shows dependencies and other edits needed to build your very own.
-dejello

Build 2! and some pics...

THIS POST IS NO LONGER REQUIRED, but kept for informational purposes
Updated - Build 3 now up!
Wifi seems to be working with some terminal junk. I followed this page as a reference after figuring out the wlan module wasn't being loaded: http://www.omappedia.com/wiki/Mac80211_based_open_source_architecture#Procedure_to_build_WLAN_and_test_on_Ubuntu_FS
NOTE: The module is apparently being unloaded after a while, possibly to do with going to sleep, not sure atm. If you have installed the terminal core app you can get back online without plugging back in..
I did the following commands and checked the browser and I was online!
Code:
[email protected]:/ # adb shell
[email protected]:/ # ubuntu_chroot shell
[email protected]:/# sudo mount -t proc proc /proc
[email protected]:/# lsmod
[I]Module Size Used by
wl12xx 189125 0
mac80211 384303 1 wl12xx
pvrsrvkm_sgx540_120 336017 34
cfg80211 181275 2 mac80211,wl12xx
compat 2718 0 [/I]
Notice: It did not show wl12xx_sdio - which has wlan0.
Code:
[email protected]:/# insmod /system/lib/modules/wl12xx_sdio.ko
[email protected]let:/# tail -3 /var/log/kern.log
[I]May 25 23:23:09 ubuntu-phablet kernel: [ 377.563903] wl12xx_set_power: 1
May 25 23:23:10 ubuntu-phablet kernel: [ 377.900939] wl12xx_set_power: 0
May 25 23:23:10 ubuntu-phablet kernel: [ 377.911682] wl12xx: loaded[/I]
[email protected]:/# ifconfig wlan0 up
[email protected]:/# tail -3 /var/log/kern.log
[I]May 25 23:25:04 ubuntu-phablet kernel: [ 492.360870] wl12xx_set_power: 1
May 25 23:25:05 ubuntu-phablet kernel: [ 492.839141] wl12xx: firmware booted (Rev 6.3.10.0.133)
May 25 23:25:05 ubuntu-phablet kernel: [ 492.864288] ADDRCONF(NETDEV_UP): wlan0: link is not ready[/I]
[email protected]:/# iwconfig wlan0 essid "tinyguest"
[email protected]:/# dhclient wlan0
[email protected]:/# ip addr
[I]......
7: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
link/ether 58:67:1a:53:b1:bd brd ff:ff:ff:ff:ff:ff
inet 192.168.2.13/24 brd 192.168.2.255 scope global wlan0
inet6 fe80::5a67:1aff:fe53:b1bd/64 scope link
valid_lft forever preferred_lft forever[/I]
Note: "tinyguest" is my test guest network with no security atm, insert the SSID of your network. I have not tested yet to see if this will work with security on.
Not sure how stable everything is, but hey, it's a dev preview so
UPDATE: I just had a realization.... After insmoding wl12xx_sdio.ko and bring the wlan0 up, I simply restarted the network manager service and now the gui shows up! I do need to check my wpa_supplicant file as I had been playing with it. <-- Fine unedited. I am also running a new minidroid build compiled using wpa_supplicant 8 vs wpa_supplicant 8_TI that I have yet to upload. I will need to see if this has any effect. I was having an issue compiling the TI version and was getting annoyed trying to figure it out New commands are as follows:
Code:
[email protected]:/ # adb shell
[email protected]:/ # ubuntu_chroot shell
[email protected]:/# insmod /system/lib/modules/wl12xx_sdio.ko
[STRIKE][email protected]:/# ifconfig wlan0 up[/STRIKE] <-- DIdn't even up it this past time, seems that restarting the network-manager service up's it.
[email protected]:/# service network-manager restart
Will be updating this post and adding a pic..

Doing great . Keep up. And why not tranfering it to nt dev thread?
Στάλθηκε από το Barnes & Noble Nook Tablet μου χρησιμοποιώντας Tapatalk 2

demetris_I said:
Doing great . Keep up. And why not tranfering it to nt dev thread?
Στάλθηκε από το Barnes & Noble Nook Tablet μου χρησιμοποιώντας Tapatalk 2
Click to expand...
Click to collapse
Thanks nothing in comparison to what you've been up to lately though. I probably should see about getting this thread moved over shouldn't I....

I'm really excited, I hope your project takes off in a big way
I admit to confusion, though - you say the base of this is the great work done on cm10.1 nightlies by the devs here, so is this actually ubuntu touch, or a skin over android? I'm not being critical, just looking to understand.
Thanks!

tmoulder said:
I'm really excited, I hope your project takes off in a big way
I admit to confusion, though - you say the base of this is the great work done on cm10.1 nightlies by the devs here, so is this actually ubuntu touch, or a skin over android? I'm not being critical, just looking to understand.
Thanks!
Click to expand...
Click to collapse
Sorry for the late reply, yes, currently Ubuntu Touch is running in a chroot on a mini build of android.
Other notes, today I started trying to figure out what exactly breaks the display on the newer ubuntu fs images.
dmesg shows ubuntu-session terminating with: "terminated with status 139". I still have an image from May 24th that works, and upon updating libplatform-api1-hybris or ubuntu-platform-implmentation-android (both of which will install the other) the display breaks with ubuntu-session terminating with: "terminated with status 127" or depending on what I've done ocassionally some other error.
More searching to follow....
UPDATE: see Build 5 notes, I hadn't fully updated my ubuntu sources apparently Display seems to work now!
PS - the git stuff isn't current atm, but the edits should still work. the wiki dealio needs work.

dejello said:
Sorry for the late reply, yes, currently Ubuntu Touch is running in a chroot on a mini build of android.
Other notes, today I started trying to figure out what exactly breaks the display on the newer ubuntu fs images.
dmesg shows ubuntu-session terminating with: "terminated with status 139". I still have an image from May 24th that works, and upon updating libplatform-api1-hybris or ubuntu-platform-implmentation-android (both of which will install the other) the display breaks with ubuntu-session terminating with: "terminated with status 127" or depending on what I've done ocassionally some other error.
More searching to follow....
UPDATE: see Build 5 notes, I hadn't fully updated my ubuntu sources apparently Display seems to work now!
PS - the git stuff isn't current atm, but the edits should still work. the wiki dealio needs work.
Click to expand...
Click to collapse
You say build 5 should fix the display not showing? I tried it and the "Current" Saucy phablet image and got nothing.
I'm about to try the Raring image and see if it works...

ajbiz11 said:
You say build 5 should fix the display not showing? I tried it and the "Current" Saucy phablet image and got nothing.
I'm about to try the Raring image and see if it works...
Click to expand...
Click to collapse
Nope...Saucy bootloops...I don't know how to get a logcat through fastboot, will look it up...

there was a period recently where they were breaking things alot with changes... I have a working version I can upload, but if they update hybris and/or the platform-api again it'll break until i update the build.
Sent from my SCH-I510 using xda app-developers app

Nook HD?
Great work! Any idea if you might get around to making a similar build for the Nook HD/HD+?

iCello said:
Great work! Any idea if you might get around to making a similar build for the Nook HD/HD+?
Click to expand...
Click to collapse
That is in my plans as I just got the HD+, not sure just yet as to when.. I need to pm verygreen or someone else and see what all I need to build cm10.1 first as I am missing something. Once I get a working build I will work on Ubuntu.
Sent from my SCH-I510 using xda app-developers app

dejello said:
That is in my plans as I just got the HD+, not sure just yet as to when.. I need to pm verygreen or someone else and see what all I need to build cm10.1 first as I am missing something. Once I get a working build I will work on Ubuntu.
Sent from my SCH-I510 using xda app-developers app
Click to expand...
Click to collapse
Alright, sounds good!

iCello said:
Alright, sounds good!
Click to expand...
Click to collapse
Ok, seems I just wasn't paying attention.. Replaced the boot image in the zip with the apparent non-sdcard version >.> CM10.1 booted so I will work on a build in a bit. For the moment though the tv is calling me

Are you planning non starting a new thread for ubuntu on the HD+?
Sent from my Nook HD+ using Tapatalk 2

Not sure atm.. If not I will update the title of this one
Sent from my SCH-I510 using xda app-developers app

So... if the Ubuntu will be available for HD+, changing a pair of things would make it for HD, is it correct?
Thank you!

dejello said:
That is in my plans as I just got the HD+, not sure just yet as to when.. I need to pm verygreen or someone else and see what all I need to build cm10.1 first as I am missing something. Once I get a working build I will work on Ubuntu.
Sent from my SCH-I510 using xda app-developers app
Click to expand...
Click to collapse
I would love this on my Nook HD (not HD+), I have ubuntu installed on all of my systems and love it over windows.
Sent from my Nook HD using XDA Premium HD app

Once I get working builds again (with the new stuff they've added for booting) I will build one for the HD for which I will need testers as I do not have an HD. Honestly did not really work on it today as I am really tired. Looks like I managed to get that one build in before they added this stuff.

dejello said:
Once I get working builds again (with the new stuff they've added for booting) I will build one for the HD for which I will need testers as I do not have an HD. Honestly did not really work on it today as I am really tired. Looks like I managed to get that one build in before they added this stuff.
Click to expand...
Click to collapse
I'll gladly test a build for Nook HD
Sent from my Nook HD using XDA Premium HD app

Ubuntu Touch Native on Kindle Fire HD 7

Hi all,
Successfully rooted, flashed, and installed jelly bean 4.3 on my kindle fire HD 7 NY following seokhun's guide here http://forum.xda-developers.com/showthread.php?t=2271909
Now wondering of anyone had tried installing Ubuntu on the kfhd. Official Ubuntu touch should be released later this month. Developer preview out now but only officially supports a few Samsung devices.
Might take a gander on how to go about installing the preview later this week. My guess is that there will have to be tweaks made to cm before it'll work properly.
See more here https://wiki.ubuntu.com/Touch/Install

It was ported to the first gen, kf2, and 8.9", I am considering trying to make a mini base like hashcode did for the 7" model, but I need to ask him a few questions probably before I start trying to flash test builds onto my own device.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
It was ported to the first gen, kf2, and 8.9", I am considering trying to make a mini base like hashcode did for the 7" model, but I need to ask him a few questions probably before I start trying to flash test builds onto my own device.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Ubuntu itself was ported or do you mean chrooted? Or do you mean your working with the developer preview of ubuntu touch? I've seen plenty of people run Ubuntu chrooted but to my knowledge its more similar to a VM on android. I've long suspected that it was possible to boot into the full desktop version of Ubuntu on android systems but haven't seen or heard of it being done. Luckilly an official build of ubuntu for tablets and phones is being released soon.

I meant the Ubuntu touch preview, we already can test it out on the other kindles but we have to use an older version of the preview because of a bug the came into play when they went to a flipped os until hashcode fixes it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

Wow, great news.
Is there anywhere I can follow progress of successful ports?

Just look at the threads in the android development sections for the kindles, there is no 7" android minibase available, but if I'm not busy I might give a shot at making one, not too sure if the kernel will compile smoothly on Ubuntu 10.04 LTS, but eh I'll maybe give it a shot sometime next week. Hard part is I have no idea about the initial stuff that runs as I'm more of a Linux pc person than a android person( even though Linux is at the base of android and Ubuntu touch.)
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

Thabks & will do. Actually just found hashcodes thread here: http://forum.xda-developers.com/showthread.php?t=2168221 and the Ubuntu device wiki here: https://wiki.ubuntu.com/Touch/Devices if anyone is interested.
Good look if you attempt to modify and build the base code yourself. Keep us updated!

Kubuntu for Nexus 5

Ubuntu for nexus with the environnement KDE!
This version is not stable and only for nexus 5.
Plasma mobile:
http://plasma-mobile.org/devices/
Installation:
https://community.kde.org/Plasma/Mobile/FlashingKubuntuPhone
Vidéo:
https://youtu.be/auuQA0Q8qpM
Envoyé depuis MIUI 6 Miui-France

nice let me try

too afraid to repartition emmc. somebody please build a kubuntu multirom rom ! this is an epic i love plasma 5 on my laptop

If my N5 wasnt my daily driver I would defiently have tried this out!

with the hopes of having a future in Zip usable MultiROM
Envoyé depuis MIUI 6 Miui-France

i couldnt resist and tried "trying it out" . backup up sdcard/ TWRPed my main rom. backed up EFS all to my laptop. Downloaded TWRP recovery and factory images (i think ubuntu repartitions sdcard ). But when i run ubuntu-device-flash it times out when downloading. Unfortunately Kubuntu people dont have instructions for offline flashing of images yet.
Also eagerly waiting for Plasma 5.4. bring a demo wayland support for laptops(at least intel hardware) that same thing which is running on Kubuntu N5 image !

Someone can share the wallpaper? Is gorgeous

Very interesant
Enviado desde mi Nexus 5 mediante Tapatalk

anyone found anything?

sarfaraz1989 said:
anyone found anything?
Click to expand...
Click to collapse
Nothing. new ..... waiting for offline images....

I watch this on YouTube and them running this on nexus 5 looks promising.
Sent from my Nexus 5 using xda premium

LILIPUTING
REVIEWS*DEALS*MINI PCS*SHOP*ABOUTContact usAdvertise on LiliputingAbout LiliputingPrivacy Statement
Plasma Mobile: Linux-based smartphone operating system
07/25/2015*at*10:14 AM*by*Brad Linder*27 Comments
There’s a new player in the smartphone operating system*space: the folks behind the KDE desktop environment for Linux-based desktop computers have just unveiled*Plasma Mobile.

Plasma Mobile is basically a mobile version of the desktop Plasma user interface. It’s free and open source software, and while there aren’t any phones that ship with Plasma Phone OS, you can download andinstall the software on a Google Nexus 5using the same tools you would use to install Ubuntu Touch.
The software is based on*the Kubuntu operating system with an Android graphics driver, the kwin/Wayland display server. Plasma Mobile isn’t tied to Kubuntu though — it should work with other operating systems. The Nexus 5/Kubuntu software is just a reference implementation that makes it relatively easy for anyone to test the software.
The software can handle typical smartphone functions, including phone calls, notifications, a customizable app launcher, and more.
There’s also support for KDE Plasma widgets, and eventually the goal is to offer a “convergence” experience that will allow you to run desktop apps on your mobile phone. While that might not make a lot of sense when you’re using a 5 inch screen, it could come in handy when you connect your phone to an external display.
If you’ve used the desktop version of KDE Plasma, you’ve basically used 90 percent of the code that can now run on smartphones. The difference is that the mobile version uses a new shell/workspace designed for smartphones. That’s where you get the app launcher, settings, task switcher, and other features.
So what can you actually do with Plasma Phone OS? In addition to Plasma apps, the software currently supports apps developed for Ubuntu smartphones, devices running Jolla’s Sailfish OS, and eventually there are plans to support Android appwith Ubuntu …*[Read More...]
Sent from my Nexus 5 using xda premium

Flashing instruction in OP is from Linux host...
can somebody help me in flashing the image from windows workstation?
Desperately want to try this out....

hiimimtayaz said:
Flashing instruction in OP is from Linux host...
can somebody help me in flashing the image from windows workstation?
Desperately want to try this out....
Click to expand...
Click to collapse
You have to flash this with linux at this time.
As soon it supports android apps im will switch in a heart beat.
Any way it seems a little risky yet.
Sent from my Nexus 5 using xda premium

Well have installed this by muitirom and at this time it is way to buggy to use in any way.
Internet not working.
Crash after crash this has a long way to go before test should start.
Sent from my Nexus 5 using xda premium

Sent from my Nexus 5 using xda premium*KDE Community Wiki
*View**View source**History
PageDiscussion
Plasma/Mobile/MultiROM
<*Plasma‎ |*Mobile
Contents
*
*
1*How to install Plasma Mobile with MultiROM1.1*Tested devices1.2*Prerequisites1.3*Install patched MultiROM manager1.4*Install Patched TWRP MultiROM recovery1.5*Finally install the Plasma Phone
How to install Plasma Mobile with MultiROM
MultiROM is useful for installing multiple ROM's on your android device, more information can be found on
http://forum.xda-developers.com/goo...tore/apps/details?id=com.tassadar.multirommgr
Tested devices
(If you test it with another devices please add it in following list)
LG Nexus 5 (hammerhead)
Prerequisites
This guide assumes that you have kernel_kexec patch applied as mentioned in above links. You can skip installing MultiROM manager application and TWRP recovery for now. (Keep reading)
Install patched MultiROM manager
Currently MultiROM manager hard codes the image server to system-image.tasemnice.eu, However thanks to user @sedrubal on Github, MultiROM Manager is patched to use kubuntu.plasma-mobile.org instead of system-image.tasemnice.eu server.
Download APK from*https://user.fablab.fau.de/~ev80uhys/multirommgr/*and install it using adb.
adb install «Path to com.tassadar.multirommgr.debug.apk»
Install Patched TWRP MultiROM recovery
MultiROM manager uses the patched TWRP recovery to finalize the installation of the operating systems. This recovery uses PGP keys to verify the Ubuntu touch images. However current recovery only have keys for the*http://system-image.tasemnice.eu*and*http://system-image.ubports.com. So it also requires patching*: Required patch is*:https://github.com/Tasssadar/Team-Win-Recovery-Project/pull/16/
Since this is not merged yet, I have uploaded patched version athttps://share.kde.org/index.php/s/OIgNSGoymLRyahg
Download it and flash it with fastboot.
adb reboot bootloader fastboot flash recovery «path to twrp-kubuntu-keys-final.img»
Finally install the Plasma Phone
Reboot to normal Android, open MultiROM manager installed in earlier step. In the Ubuntu Card, select devel or devel-proposed and click on install..
It will take while to download. After download is over, it will reboot to recovery, in recovery it will make real installation process, so drink a coffee meanwhile..*
After that it is done installing it will reboot. Before android logo is shown it will ask you to choose from Internal or utouch_devel, Select utouch_devel to boot into your plasma.
This page was last modified on 9 August 2015, at 16:42.This page has been accessed 386 times.Content is available under*Creative Commons License SA 3.0 as well as the GNU Free Documentation License 1.2.
NAVIGATIONMain pageCommunity portalCurrent eventsRecent changesCONTRIBUTOR HELP PAGESTasks and ToolsModify a pageAdd new contentPage elementsTypographical guidelinesMore markup helpTOOLBOXWhat links hereRelated changesSpecial pagesPrintable versionPermanent linkPERSONAL TOOLSLog inOpenID / Identity login
*Privacy policy*About KDE Community Wiki*Disclaimers*KDE Links*
KDE®*and the K Desktop Environment®*logo are registered trademarks of*KDE e.V.*•*Legal