Develop Bugs

[DEV] [BOTH] ubuntu on Galaxy Tab (natively)

I have been working on getting ubuntu running natively with the netbook gui (unity) on the galaxy tab (7" touch display at this resolution is ideal). Kernel and filesystem are almost complete, but I need one last piece of the puzzle, if anyone has the galaxy tab hardware keyboard and know how to flash a kernel with heimdall could they join irc.droid-life.com/#modadroid-galaxy-tablet and catch my attention (lilstevie there too)
Here is a screenshot of netbook-launcher-efl running on the tab
Ubuntu Desktop 2D
LXDE
e17 Illume-home (phone/tablet)
EDIT1: Ubuntu is now booting into a shell more coming soon
EDIT2: screen shot
EDIT3: added 2 extra screenshots
EDIT4: updated name to follow new rules.
Coming soon is a CDMA kernel and Images

Kernel Image 0.1 POC - 2.6.32.9 (non update1 international kernel):
this should work for all GSM devices:
Internal SD (mmcblk0p3) install:
mmcblk0p3

Wow..Surely looking forward to this one..Keep us updated and good luck

This will complete the Tab

Great News!
Sent from my GT-I9000 using Tapatalk

wow....marked

is it possible to dual boot?

Anyway to get the netbook edition of Ubuntu instead of the full desktop version? Seems like it would be better with the smaller screen.
From the Tab.
www.twitter.com/ayman07

that's what he's doing (unity)
Sent from my Legend using XDA App

Great news mate! Hope there will be dualboot optinion for Android and Ubuntu

lilstevie said:
I have been working on getting ubuntu running natively with the netbook gui (unity) on the galaxy tab (7" touch display at this resolution is ideal). Kernel and filesystem are almost complete, but I need one last piece of the puzzle, if anyone has the galaxy tab hardware keyboard and know how to flash a kernel with heimdall could they join irc.droid-life.com/#modadroid-galaxy-tablet and catch my attention (lilstevie there too)
EDIT1: Ubuntu is now booting into a shell more coming soon
Click to expand...
Click to collapse
Anything any of us can do? I know my way around linux, I can code a bit. I can host anything, too

TheGrammarFreak said:
that's what he's doing (unity)
Sent from my Legend using XDA App
Click to expand...
Click to collapse
completely missed that line lol.
@OP
video of it working please!....when theres actually a GUI

edzilla said:
Anything any of us can do? I know my way around linux, I can code a bit. I can host anything, too
Click to expand...
Click to collapse
well at the moment I am trying to sort out some kind of interactivity (shouldnt be too much work, just playing around with the back and forth with fs images, 2GB takes a while to push to the device
ayman07 said:
completely missed that line lol.
@OP
video of it working please!....when theres actually a GUI
Click to expand...
Click to collapse
video of it working will arrive once i have interactivity

MartanCJ said:
Great news mate! Hope there will be dualboot optinion for Android and Ubuntu
Click to expand...
Click to collapse
Dualbooting isn't much of an option at the moment, unless with some bootloader hacks we can separate boot modes to boot the boot partition with no keypress or recovery position with keypress, as at the moment it just triggers a different init script in the initramfs, ubuntu has some differences at a kernel level

lilstevie said:
I have been working on getting ubuntu running natively with the netbook gui (unity) on the galaxy tab (7" touch display at this resolution is ideal). Kernel and filesystem are almost complete, but I need one last piece of the puzzle, if anyone has the galaxy tab hardware keyboard and know how to flash a kernel with heimdall could they join irc.droid-life.com/#modadroid-galaxy-tablet and catch my attention (lilstevie there too)
EDIT1: Ubuntu is now booting into a shell more coming soon
Click to expand...
Click to collapse
Great job !!!!!
Dual boot . . . What a dream
Sent from my GT-P1000 using Tapatalk

lilstevie said:
Dualbooting isn't much of an option at the moment, unless with some bootloader hacks we can separate boot modes to boot the boot partition with no keypress or recovery position with keypress, as at the moment it just triggers a different init script in the initramfs, ubuntu has some differences at a kernel level
Click to expand...
Click to collapse
I'm going to have a look at this today for my Meego install, the Android init isn't passed anything by the kernel so it must look at some /dev or /sys entry to work out whether a recovery boot was requested.
I've certainly had no real problems replacing the Android init with an init script and exec'ing the renamed Android init from that to get a normal boot, the question is now how to make it useful by reading the bootstate.
As an aside, I see you were asking about the keyboard, I'm also interested in this as I have the same issue as you - i get a login prompt but can't login. I was thinking that getting a usb keyboard to work would be nice, but otherwise I'll have to make sure I bring the network up and either start adb or insmod an ethernet gadget driver (assuming such a thing will work with the Samsung patches).
Anyway keep up the good work

lardman said:
I'm going to have a look at this today for my Meego install, the Android init isn't passed anything by the kernel so it must look at some /dev or /sys entry to work out whether a recovery boot was requested.
I've certainly had no real problems replacing the Android init with an init script and exec'ing the renamed Android init from that to get a normal boot, the question is now how to make it useful by reading the bootstate.
As an aside, I see you were asking about the keyboard, I'm also interested in this as I have the same issue as you - i get a login prompt but can't login. I was thinking that getting a usb keyboard to work would be nice, but otherwise I'll have to make sure I bring the network up and either start adb or insmod an ethernet gadget driver (assuming such a thing will work with the Samsung patches).
Anyway keep up the good work
Click to expand...
Click to collapse
sounds like you are stuck in a similar position to me, any driver that is not the samsung android eth gadget does not want to compile for me, the path that i am taking is trying to get the wlan module loaded and using a script to associate it to my wifi network.
On another note started working on fbdev black screen, but something none the less

any progress on this?

Bump
From the Tab.
www.twitter.com/ayman07

wow
not at all bothered about dual boot on this project..
im absolutely excited about ubuntu working as a native os though, that would be amazing, if its anything like 'Dcordes' ( '@htc_linux' ) build for the HD2 this will be a real winner for the Tab, all the phone functions need to work too like texts and gsm, i guess if HD2 can do it then Tab can too..
looking forward to the projects future

[App] 2BOrange - Install any kernel (Voodoo, SpeedMode, Infusion...) without computer

____________________________________
2BOrange
____________________________________​
Hi everybody,
I have made a free application to install any kernel on your SGS very easily.
The idea is that there is a website where kernel are uploaded with a script and an application to:
- search
- download
- install it on your phone.
The application and the website are not limited to install kernell but I think it is a good way to try it.It can execute any script in the android shell.
So I have made some script for some kernel, there are so much that I have not the time to make one for each of them.
To make a script is very easy, I have attached an example of one I have uploaded on the website. If you need to attach a file, put it in a zip and upload both (the script and the zip) through the upload form on the website,
The address of the website is:
http://www.2borange.com/
A general thread on XDA (not dedicated to kernel on SGS) about the application:
http://forum.xda-developers.com/showthread.php?p=14875954#post14875954
You need to create an account to upload but it is not mandatory to just search, download and install a kernel.
Please keep me informed if everything work or not. I have only test it on my phone.
For the author of the kernels: I am sorry to have not yet informed you of the sharing of your great work, I will do it for sure when I will have done enough test to offer you an interesting way to share your work.
For the user: if you have time, don't hesitate to upload some scripts, it is free and easy to do...
Thank you for everything,
Michael
LIST OF KERNEL AVAILABLE AS OF JUNE, 27:
- Galaxian
- Infusion Kernel Faster Fusion Reaction
- Semaphore Kernel JVH - JVP
- SpeedMod Gingerbread
- TalonDEV
- TEGRAK lagfix- Voodoo kernel installer
- Voodoo kernel JVP
Don't hesitate to upload some new firmware. A model of script is provided below as attachment

niceee something to look foreward to

Neldar's SGS Kernel Flasher
is not locked to any web-site.
Sent from my GT-I9000

O-T said:
Neldar's SGS Kernel Flasher
is not locked to any web-site.
Sent from my GT-I9000
Click to expand...
Click to collapse
This allows you to actually find a kernel, download it and flash it as well. The Kernel Flasher is just for kernels already on your sd card.

O-T said:
Neldar's SGS Kernel Flasher
is not locked to any web-site.
Sent from my GT-I9000
Click to expand...
Click to collapse
Thank you for your message.
I did not know about this application. I have read the description and I can tell you the purpose of mine is totally different.
I have understood that Nedar application is to install a Kernel that you have already downloaded and copy on your SDCARD.
The purpose of my application is to download automatically a script and a zip file, and execute the script.
So there are 2 main differences between these two applications:
- my application get files you need directly from the cloud (Internet), so it is like a deposit of files
- my application is not limited to kernel installation, it is just a usefull example to show people how it works, but it can do more, really lot more tasks.
However, because the application of Nedar is dedicated to one particular task, it has option I have not yet implemented in mine. By example, I have not yet construct a script to backup the kernel in an update.zip file, which could be very usefull.
So they are really very different. I hope I will be able to construct more script, but may be the biggest difference with any dedicated application is that anyone can participate to my project without any knowledge in Java programation.
You just have to know a little bit about shell to be able to share your work with others.
THAT IS THE REAL PURPOSE OF THIS APPLICATION : SHARING!

Amazing concept!
Thumbs up for the foresight for such a nice project. If enough effort is put I can see in next couple of months, the whole, ROM, Kernel, Modem flashing automated.
Right from finding the correct software till installing them and may be some debugging and fault finding as well!
Will definitely donate in case the project takes off the way it should!
Great work Snoopy!

Loving the concept of this!
As omzworld was saying, if this grew into a script that could automatically install your ROM/kernel/modem etc. that would be awesome, especially for people who are new to flashing.
Now, here's another suggestion that may or may not have been thought about already..
Is there any way to make the app look at your phone and use that as a basis for roms, kernels etc. ? If that was possible, anyone and everyone would be using your app to flash because they would know that bricking their phones would be almost impossible.

omzworld said:
Amazing concept!
Thumbs up for the foresight for such a nice project. If enough effort is put I can see in next couple of months, the whole, ROM, Kernel, Modem flashing automated.
Right from finding the correct software till installing them and may be some debugging and fault finding as well!
Will definitely donate in case the project takes off the way it should!
Great work Snoopy!
Click to expand...
Click to collapse
lttldvl said:
Loving the concept of this!
As omzworld was saying, if this grew into a script that could automatically install your ROM/kernel/modem etc. that would be awesome, especially for people who are new to flashing.
Now, here's another suggestion that may or may not have been thought about already..
Is there any way to make the app look at your phone and use that as a basis for roms, kernels etc. ? If that was possible, anyone and everyone would be using your app to flash because they would know that bricking their phones would be almost impossible.
Click to expand...
Click to collapse
Thank you for your interest.
The thing I need now is not money, donation,etc... but report of test and ideas of improvment.
By the way, I only have a samsung phone, and I am wondering if there are possibilities to install kernel in other phone only by using the shell, have you an idea ?
Second question: have you an idea how to proceed to install an entire ROM through the shell ? I suppose the phone has to be rebooted before installation begin and lauche in a recovery mode, but how to make it automatic like in ROM Manager?
Thank you for your help!

omzworld said:
Amazing concept!
Thumbs up for the foresight for such a nice project. If enough effort is put I can see in next couple of months, the whole, ROM, Kernel, Modem flashing automated.
Right from finding the correct software till installing them and may be some debugging and fault finding as well!
Will definitely donate in case the project takes off the way it should!
Great work Snoopy!
Click to expand...
Click to collapse
What is the way it should take for you?
I need ideas

lttldvl said:
Loving the concept of this!
As omzworld was saying, if this grew into a script that could automatically install your ROM/kernel/modem etc. that would be awesome, especially for people who are new to flashing.
Now, here's another suggestion that may or may not have been thought about already..
Is there any way to make the app look at your phone and use that as a basis for roms, kernels etc. ? If that was possible, anyone and everyone would be using your app to flash because they would know that bricking their phones would be almost impossible.
Click to expand...
Click to collapse
I have already included a kind of filter based on brand, model of phone and firmware version plus sdk version, do you think it could be more precise?

Fixed script on server, should work on every phone now

Hey snoopy33, why do you have not yet updated this page?

Cannibal Open Touch v2.1 (latest update: 12/1/2012)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Project Open Cannibal presents...
Cannibal Open Touch v2.1 for Amazon Kindle Fire (first generation)​
About Cannibal Open Touch:
Cannibal Open Touch is the next generation of custom recoveries. Jam-packed with cool and useful features, it can handle just about anything you can throw at it.
Warning: Does NOT currently support KitKit
Main Features:
1. Theme support
2. Touch screen button controls!
3. GooManager support!
4. Advanced Backup
5. Delete old backups!
6. Persistent settings
7. User-defined backup locations!
8. ADB Sideload
9. Touchscreen calibration
10. Backported “retouch binaries” patch for ICS/JB compatibility
11. Backported extfs tools for better ICS/JB management
Why the name Cannibal Open Touch?
Because we can. The name also embodies everything that Cannibal Open Touch is. It is no longer just a variant of ClockworkMod Recovery, it is it's own recovery by itself. Combining features from ClockworkMod 5, Team UtterChaos' Sony Xperia recovery, AmonRa 3.0.6, Xionia CWMA and a heaping helping of our own special enhancements it is truly revolutionary.
What to do when an error occurs:
DO NOT simply say "xxxx doesn't work" as that is highly unhelpful and will probably be ignored. Instead, post the recovery log! To grab a log when an error occurs, simply open a terminal (or command prompt if on Windows), "cd" to an easily accessible directory and execute:
Code:
adb pull /tmp/recovery.log
Paste the log as an attachment (don't paste the text inside, as it can be quite lengthy), or paste it on pastebin.com.
WARNING!
If you are upgrading from a previous version of Cannibal Open Touch you must delete the settings.ini file located in the cotrecovery folder on your sdcard!
Flashing instructions:
Flashing instructions can be found at the download link below.
Main Recovery Screenshots:
Main Gallery (external link) (Nexus 7 screen shots; will update soon)
Available Themes:
Themes Gallery (external link) (Again, Nexus 7 images shown here)
Download Cannibal Open Touch v2.1:
Note: The below link is an external link to the Project Open Cannibal forums. We do not require registration to download any public release, but we'd sure appreciate it if you stopped by to say hello
Cannibal Open Touch Download (external link)
For those of you who are either uncomfortable or incapable of using fastboot for some reason webdroidmt has done an updated Smirkit 2.1 for y'all, please see the original Smirkit release page for usage instructions.
XDA:DevDB Information
Cannibal Open Touch v2.1, a Tool/Utility for the Amazon Kindle Fire
Contributors
Sblood86, drewwalton19216801, thenameisnigel
Version Information
Status: Stable
Current Stable Version: 2.1
Stable Release Date: 2012-12-01
Created 2013-09-04
Last Updated 2013-11-28

Good to see you posting COTR here! Thanks.
Mike T

Just made a nandroid & it seemed faster than 2.02, maybe placebo. :laugh: Didn't flash any roms , as I don't have anything new to flash...yet! I like the overall simplicity and the functions in plain language terms.
Couple of questions, where can I read up on how to install a theme? Is that something that the COTR android app does or will do? Also, as stated in the OP, I deleted my current .ini file but can I still restore older COTR nandroids, say from 2.02 with this version? I'm figuring yes but want to be sure.
Thanks again for an alternative to TWRP. Btw, when the skull logo first came up, I thought I got a virus or something. LOL Looks cool.
Mike T

webdroidmt said:
Just made a nandroid & it seemed faster than 2.02, maybe placebo. :laugh: Didn't flash any roms , as I don't have anything new to flash...yet! I like the overall simplicity and the functions in plain language terms.
Click to expand...
Click to collapse
I can't imagine what would effect speed but cool
webdroidmt said:
Couple of questions, where can I read up on how to install a theme? Is that something that the COTR android app does or will do? Also, as stated in the OP, I deleted my current .ini file but can I still restore older COTR nandroids, say from 2.02 with this version? I'm figuring yes but want to be sure.
Click to expand...
Click to collapse
Previous backups should work just fine yes as for themes we don't have a lot yet but there is an outline for creating them on both github and the POC forums. The apps capabilities are limited to Drew's java capabilities as I find java to be; well, it's unsavory, we'll leave it at that
To that end I'm not sure but maybe.
webdroidmt said:
I thought I got a virus or something.
Click to expand...
Click to collapse
Love it!

Thank you Sblood86 this is a great Christmas gift awesome work. Updated index.

I assume this replaces twrp. Would I install this along side twrp? Will firefirefire offer a choice of recovery?
Sent from my Amazon Kindle Fire using xda app-developers app

Sblood, is there a way in settings to change the time? Thanks.
Mike T

webdroidmt said:
Sblood, is there a way in settings to change the time? Thanks.
Mike T
Click to expand...
Click to collapse
Not at this time (no pun intended); requires an offset which varies a bit by location so it's a bit of a hack. Haven't done it yet but we may add a function for it in the future.

Sblood86 said:
Not at this time (no pun intended); requires an offset which varies a bit by location so it's a bit of a hack. Haven't done it yet but we may add a function for it in the future.
Click to expand...
Click to collapse
Thanks for your reply, obviously it would be nice for proper timestamping of the nandroids, as now it reads 5 hours ahead for me.. But even without that, I've previously been enjoying using COTR and this new version with themes gives me a little something extra to play with.
Started messing around with the themes I d/l from the git, took the devildroid one and substituted the devildroid background out with the droid jellybean machine that's been floating around the web. Simple but looks pretty nice, I like green :laugh: and gives me a better idea how to work with the themes going forward. Gonna' work with the HTML color picker to see what other combos I can come up with.
Btw, just for the heck of it, I updated my smirkit with COTR 2.1 and flashed it instead of fast booting it.
Anyway, thanks again for this update.
Mike T

Ixthusdan said:
I assume this replaces twrp. Would I install this along side twrp? Will firefirefire offer a choice of recovery?
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
There can be only one.

flashable zip?

smirkit with COTR 2.1
For those not comfortable using fastboot, I've updated smirkit with COTR 2.1. You can find the download link on the smirkit thread here:
http://forum.xda-developers.com/showpost.php?p=34974869&postcount=325
Mike T

portezbie said:
flashable zip?
Click to expand...
Click to collapse
Hmm; suppose it wouldn't be a bad idea I just didn't really consider it lol...
webdroidmt said:
For those not comfortable using fastboot, I've updated smirkit with COTR 2.1. You can find the download link on the smirkit thread here:
http://forum.xda-developers.com/showpost.php?p=34974869&postcount=325
Mike T
Click to expand...
Click to collapse
I almost messaged him in regards to that but I knew he didn't have a KF so I figured we'd leave it be lol
Edit: linked to the OP as well.

great work, but..
I love new stuff and really want to try this -- it sounds great -- but with the past mis-flash issues with all versions of CWM and similar problems with many of the later TWRP versions on the KF device, I'm, to say the least, a little gun-shy. (the name also adds to my unease - but so would a pink unicorn heh)
Perhaps when I see folks posting multiple (2-3) successful flashes of different roms with this, I will jump on board with both feet. As clunky or ugly as it is, TWRP 2.1.1.1 works flawless for me and has for months so, as much as I like the latest/greatest, I'm holding off for now.
Many thanks to the OP and all the other fine Android developer volunteers here as well. :highfive: Your efforts are immensely appreciated - especially when you innovate a new solution like this one. Unfortunately I'm a relative android n00b and have scant confidence in unbricking my device should that occur, and even, as low as prices are, less ability to replace it as I'm on fixed income that almost covers living expenses. Sorry..

dadeo1111 said:
I love new stuff and really want to try this -- it sounds great -- but with the past mis-flash issues with all versions of CWM and similar problems with many of the later TWRP versions on the KF device, I'm, to say the least, a little gun-shy. (the name also adds to my unease - but so would a pink unicorn heh)
Perhaps when I see folks posting multiple (2-3) successful flashes of different roms with this, I will jump on board with both feet. As clunky or ugly as it is, TWRP 2.1.1.1 works flawless for me and has for months so, as much as I like the latest/greatest, I'm holding off for now.
Many thanks to the OP and all the other fine Android developer volunteers here as well. :highfive: Your efforts are immensely appreciated - especially when you innovate a new solution like this one. Unfortunately I'm a relative android n00b and have scant confidence in unbricking my device should that occur, and even, as low as prices are, less ability to replace it as I'm on fixed income that almost covers living expenses. Sorry..
Click to expand...
Click to collapse
I'm on board with you, I've become complacent with the ease of use the developers have granted us with flashing roms for the Kindle Fire. Much of what I learned when I first started messing with the Kindle Fire has been left in a dusty part of my brain because I haven't needed to use it. If I was still able to confidently unbrick the KF (or at least know i'd have a good shot at it) i'd give this recovery a try, but my confidence isn't there and neither is my funding for a new KF should I void the warrenty.

dadeo1111 said:
I love new stuff and really want to try this -- it sounds great -- but with the past mis-flash issues with all versions of CWM and similar problems with many of the later TWRP versions on the KF device, I'm, to say the least, a little gun-shy. (the name also adds to my unease - but so would a pink unicorn heh)
Perhaps when I see folks posting multiple (2-3) successful flashes of different roms with this, I will jump on board with both feet. As clunky or ugly as it is, TWRP 2.1.1.1 works flawless for me and has for months so, as much as I like the latest/greatest, I'm holding off for now.
Many thanks to the OP and all the other fine Android developer volunteers here as well. :highfive: Your efforts are immensely appreciated - especially when you innovate a new solution like this one. Unfortunately I'm a relative android n00b and have scant confidence in unbricking my device should that occur, and even, as low as prices are, less ability to replace it as I'm on fixed income that almost covers living expenses. Sorry..
Click to expand...
Click to collapse
isaiahhhhh said:
I'm on board with you, I've become complacent with the ease of use the developers have granted us with flashing roms for the Kindle Fire. Much of what I learned when I first started messing with the Kindle Fire has been left in a dusty part of my brain because I haven't needed to use it. If I was still able to confidently unbrick the KF (or at least know i'd have a good shot at it) i'd give this recovery a try, but my confidence isn't there and neither is my funding for a new KF should I void the warrenty.
Click to expand...
Click to collapse
I understand the reluctance but also can state fairly plainly that IF you had been following CWM issues closely you would know that the only issues that CWM ever had with the kindle was Flashing 3.y kernels (resolved a long time ago with the first iteration of my recovery {before we renamed it}) and the super bricks with the ICS+ based recovery (solved by removing the EMMC wipe calls); this is a gingerbread hybrid so the last of those 2 isn't even remotely possible...
A fairly moderate amount of research would prove both of those statements; I would NOT release something that I wasn't confident worked. The only risk to bricking your devices while using this recovery is improper usage and/or flashing or doing something you shouldn't be doing...
Just to reinforce that statement I haven't used TWRP since last December when I rooted my Kindle Fire; it has always ran a variation of CWM or similar and guess what; it still works
I also have a jellybean based recovery for us; works flawlessly (I've been running it on my kindle for months without any emmc crashes {yes I do have the faulty samsung emmc so if there were still erase issues I would have a brick sitting on my desk; again, I don't }) apart from USB mass storage (which is the only reason we released the hybrid instead of the jellybean based recovery).
Now I know you guys are going to make up your own minds and so forth and I wouldn't ask for anything less; part of the reason I love Android devices is the Open Source nature and the fact that you aren't required to use one specific program so if you don't like the recovery that is entirely your right. Having said that I'd hate for fear to be the only thing that kept y'all from trying something new; read the recovery discussion in Hashcode and DooMLoRDs old recovery threads if you would like to know more on the subjects, also my CM7 thread discusses the my original iteration of CWM based 'hybrid' (gingerbread-ics) recovery (the release of which overshadowed as Hashcode released his ICS based recovery at the same time and people did have issues with it do to kernel wipe errors: these never occurred for those using the hybrid recovery and I'm sure you guys could find a few people to confirm that).
One final thought; instead of looking for posts saying it works, try finding one saying it doesn't (I personally never post when something works as it's implied in the fact that noone has screamed out saying it doesn't)
Edit: I forgot to mention we released 3 dev previews and a release candidate of this to our beta testers at the POC forums long before a public release (the rc was actually only out for a week but that was mainly to make sure we hadn't broken anything {layout related} since dev3).

COTR
A vote of confidence here for COTR. Don't get me wrong, I like TWRP with all its features, "pretty" UI and I especially like renaming my backups from within the recovery. But I had posted back in the summer that TWRP was becoming consistently unreliable for me in flashing ICS & JB roms, usually resulting in a flash failed error. At first I thought it was just bad downloads but this was with the MD5 matching and it would eventually flash after rebooting and reflashing on the second or third try. In a nutshell, every time I flashed a rom, I wondered if it was going to flash or bomb out on me.
With CWM not being a viable option, I was very happy to see Sblood release COTR and I've been using this as my recovery since August. I like supporting Sblood's work but more importantly I have confidence that my zips are going to flash every time as long as they are not corrupt.
Let me just say, I'm a flashaholic. I generally test just about every rom in this forum and I'm running nandroids just about every other day. Matter of fact, I maintain 3 different roms on this forum with 3 different Google accounts...they're cheap :laugh: Since I've been using COTR, I've not had one bad flash and I've backed up and restored more times than I can count without issue.
Now, if only the next version of COTR allows for renaming the nandroids. LOL Actually, I see from the COTR forum that it's on the to-do list. Well, that's my two cents and I guess we should all use what we're comfortable with in the long run.
Mike T

Looks promising. I flashed it using my favorite tool dd and it worked so far with my own unsigned zip file that resets all my custom tweaks via goo manager. I haven't tried any other features yet.

How do we make it portrait?
Sent from my Nexus 7 using XDA Premium HD app

firered365 said:
How do we make it portrait?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
It's controlled in the screen firmware and driver controller in the kernel; simply put, you don't/can't. Sorry.

[ROM][LINARO][29/09/13][4.3]-SentinelROM v5.00-CM10.2 Source - Fast, Stable[GPL]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Welcome to SentinelROM for Nexus 10. Based on CM10.2. Android 4.3
This ROM is based on CyanogenMod 10.2 with all the features you get in a CM10.2 ROM, plus the following features.
Compiled with Linaro toolchain for enhanced performance.
Aroma Installer for additional tweaks and options
Zip Aligned
Compiled from latest CyanogenMod 10.2 source
Improved Web Browsing performance
Improved 3D gaming performance
Improved battery life
Additional theming and UI customisation
FAST support via this page and our Facebook Page
________________________
This ROM has been built to enhance the CyanogenMod 10.2 experience, with faster gaming and web browsing performance (no choppyness in Chrome too!).
Countless hours have been spent making tweaks to settings to squeeze the most performance I can find out of this ROM while still providing excellent battery life and without the dangers of overclocking and kernel level tweaking.
I compile this ROM and Kernel from the latest CyanogenMod source code, add my various tweaks and adjustments, then test for stability, so you get all the benefits of CyanogenMod 10.2, plus my tweaks and extras, all without the instability and inconvenience of flashing CyanogenMod nightlies (which are not designed specifically for the Nexus 10 like my ROM is.
The kernel source is available from the CyanogenMod's GitHub.
________________________
________________________
None that I am aware of. Please report any issues in this thread or on the Facebook page.
Note: On CM10.1 ROMs, to access the internal SD card on your device via USB on your PC, please go to "Settings" - "About Tablet" and tap on "Build Number" repeatedly to unlock "Developer Options". Now go to "Developer Options" and enable "Android Debugging".
________________________
If installing for the first time:
To install this ROM you will need to have an unlocked bootloader and a custom Recovery such as TWRP or ClockWorkMod installed (personally I recommend TWRP, I have had issues with restoring backups using CWM). If you haven't yet unlocked your bootloader and installed a custom recovery, I recommend downloading and installing the Nexus 10 Toolkit.
Copy the downloaded SentinelROM zip to your Internal Storage.
Boot into your custom recovery
Back up your stock ROM
Factory Reset and wipe Cache and Dalvik Cache
Wipe System Partition
Install the ROM
Install GAPPS
Reboot. First boot can take up to 5 minutes.
Important: CyanogenMod statics is switched off by default in this ROM. After installation you will be asked if you want to turn it on, please leave it off.
Note: Use of titanium backup to restore apps and data from another ROM is not recommended, and is the source of 90% of user issues, especially when it comes to battery life. Do so at your own risk.
You may flash other kernels as you wish via recovery. Remember to also flash the correct libraries for any 3rd party kernels.Instructions will be given by the Kernel author. NOTE: Updating the ROM via OTA will also overwrite any custom Kernels you have installed.
________________________
Thanks very much to all those who have answered my questions through the process of creating my own ROM, you know who you are.
CyanogenMod for their outstanding work. Full credit to them for the bulk of this ROM.
The Linaro team for their amazing toolchain.
________________________
29/09/13:
SentinelROM v5.00 - ROM and Kernel compiled with Linaro from CyanogenMod 10.2 source
Choose from an increasing range of Premium Themes for SentinelROM here.
Please don't forget to hit the Thanks button too
GAPPS
http://goo.im/gapps >Check the lastest package available on top
MD5Sum: check the md5 of the files before flashing it
Other Kernels
For extreme performance, give KTManta Kernel by ktoonsez a go. It improves gaming performance significantly, but your device will get quite hot.
I'm going to do some more testing and may include it in later builds.
________________________
Please visit my FAQ's page before asking questions in the thread. Chances are the answer is already there! I'm always happy to help out with any other questions.
________________________
NOTE: Unless otherwise stated, the following mods are developed by SentinelROM users and therefore I can only offer limited support for problems caused by using them.
Tablet UI for SentinelROM v4.70 - Kindly donated by SentinelROM user brGabriel - Flash via Recovery. To restore to stock, reflash SentinelROM and wipe cache.
________________________
I hope you enjoy my ROM. If you do, please consider a donation to the CyanogenMod team. If you really like my build, please consider a donation to me as well. Donations go towards flowers for my wife so she lets me keep developing, and of course, additional devices so I can add to my list of supported devices.
As always, you flash my ROM at your own risk. By unlocking your bootloader and flashing any custom ROM, you are potentially voiding your warranty. I'm in no way responsible for any damage to your device caused by flashing this ROM or any other tweaks/mods discussed in the following posts.

New development, announcements and pipeline work will be posted on our Facebook page, so be sure to 'like' us if you like SentinelROM
29/09/2013:-
v5.00 -
*Compiled with new Linaro toolchain v4.8 for a further performance boost.
*Updated to latest Mali graphics drivers for improved performance and stability.
*Updated to latest CM10.2 source (Android 4.3)
*Adds all the latest CM features.
[NOTE: You must wipe your System and Dalvik caches after upgrading. GAPPS Must be re-installed after updating. Please view the instructions here.
26/06/2013:-
v4.80 -
*Compiled with new Linaro toolchain v4.8 for a further performance boost.
*Updated to latest Mali graphics drivers for improved performance and stability.
*Updated to latest CM10.1 source (Android 4.2.2)
*Adds all the latest CM features.
[NOTE: You must wipe your System and Dalvik caches after upgrading. GAPPS Must be re-installed after updating. Please view the instructions here.
Click to expand...
Click to collapse

Nexus 10 Gaming performance - Need For Speed Most Wanted
Setting up LMT Pie Controls.

Re: [ROM] 28/01/13 - SentinelROM v3.00 - CM10.1 Base - Fast, Stable, Themed
I'm going to have this installed and be your first reviewer faster than you can say s*** on a shingle
Sent from my Nexus 10 using xda app-developers app

Left bar include ? Y say y will look on it ;o)

Re: [ROM] [28/01/13] - SentinelROM v3.00 - CM10.1 Base - Fast, Stable, Themed
I spent 4 hours yesterday trying to get it working and had to give up for this build. I could do it for AOSP but can't get it to work on CM10 base. Ill keep trying though.
Sent from my EndeavorU using xda premium

Is there a tabletUI option for this release?

I looked at Tablet UI as an option, but the consensus is that it's depreciated and support will become less and less over time, so I decided to leave it out with this ROM.

Re: [ROM] [28/01/13] - SentinelROM v3.00 - CM10.1 Base - Fast, Stable, Themed
What does he mean by that is he talking about the action bar or the menu button that appears on the right?
Anyhow I had an idea that maybe I could work on some modifications that I would like on this ROM without having to ask you for it, but I am very new at it and all of the guides I have found are either out of date or are poorly written so I didn't understand how to do it. Do you think you could direct me in the right direction to get started? I would really appreciate it, thank you very much.
Sent from my Nexus 10 using xda app-developers app

Yeah he means moving the navigation bar at the bottom so that the Back, Home and Running buttons are off to the left hand side.
I figured out how to move them and it works perfectly in SentinelROM AOSP, but it seems that CM10.1 is using some weird scaling in the systemUI to fit the large screen of the N10. Even when I modify the XML to adjust the alignment to the far left, it sits about 3 quarters of the way across. From what I can tell, as far as the systemUI knows, this is the edge of the screen and the rest of the area is deadzone. I'll spend some more time later in the week working on it.
Anyone else is always welcome to make mods and tweaks (anything that works with this ROM should also work with other CM10 based ROMS). I welcome and encourage it in the spirit of open source! Hey this whole ROM is pretty much a CyanogenMod Kang.
You just need to package them up as flash-able zips that can be flashed via recovery. If I like them, I'll include them in future builds with your permission
To make mods you will need 7-ZIP, Notepad++ and APKTool. You just need to extract the APK you want to edit using APKTool, then make your modifications using Notepad++, then compile using APKTool and merge your modded resources with the original APK in 7-Zip. Then you just need to push the modified APK to your device (I use Android Commander for that). Compiling into a flash-able zip is a little more tricky but there are plenty of guides around.

Hello,
I have got a brand new Nexus 10 ... normally I am a HTC-Guy
Does CM10.1 or your Rom have EQS on the right curtain?
I tried to find out at the CyanogenMod Homepage ... but without success
Thank you
Robert
EDIT:
I think I found the answer ... YES

the_real_fosgate said:
Hello,
I have got a brand new Nexus 10 ... normally I am a HTC-Guy
Does CM10.1 or your Rom have EQS on the right curtain?
I tried to find out at the CyanogenMod Homepage ... but without success
Thank you
Robert
EDIT:
I think I found the answer ... YES
Click to expand...
Click to collapse
Eqs include and works perfect

Gapps
Hello,
sorry for newbie questions, but in the thread of Craigacgomez he linked a GAPPS (GoogleAppsPack-4.2.1-JOP40D.zip)
with a filesize of 150MB, when I go to the link from 1.Page:
GAPPS
http://goo.im/gapps >Check the lastest package available on top
MD5Sum: check the md5 of the files before flashing it
There is a zip file for "me" (gapps-jb-20121212-signed.zip) with only 90 MB
Why is the size so different?
Bye
Robert
p.s.
now I installed your rom with gapps-jb-20121212-signed.zip, but I have very few EQS
Can I somewhere set up, what I want to control with EQS?

Re: [ROM] [28/01/13] - SentinelROM v3.00 - CM10.1 Base - Fast, Stable, Themed
Thanks for the nice little simple guide at the hell of a lot easier to understand than all the other ones I found. If I have any problems with making it it flash able, even with looking at the different guides out there. I know I can come to you, thank you. My goal is to incorporate be modifications that allow me to modify the bottom bar, the Quick Settings bar with the message settings app, the notification LEDs, and to be able to make my ROM updatable over the air. I bet this will be a very difficult thing to achieve but nothing easy is worth doing.
Sent from my Nexus 10 using xda app-developers app

Hello,
me once again
Is it possible to spread the dock icons further?
Because they are very close together.
Bye
Robert

the_real_fosgate said:
Hello,
sorry for newbie questions, but in the thread of Craigacgomez he linked a GAPPS (GoogleAppsPack-4.2.1-JOP40D.zip)
with a filesize of 150MB, when I go to the link from 1.Page:
GAPPS
http://goo.im/gapps >Check the lastest package available on top
MD5Sum: check the md5 of the files before flashing it
There is a zip file for "me" (gapps-jb-20121212-signed.zip) with only 90 MB
Why is the size so different?
Bye
Robert
p.s.
now I installed your rom with gapps-jb-20121212-signed.zip, but I have very few EQS
Can I somewhere set up, what I want to control with EQS?
Click to expand...
Click to collapse
Hi mate,
EQS is completely configurable from Settings - System - Quick Settings Panel
I'm not sure why the GAPPS package is smaller, but it's the one CyanogenMod recommend with any CyanogenMod based ROMs and I haven't had any problems. with it.

Re: [ROM] [28/01/13] - SentinelROM v3.00 - CM10.1 Base - Fast, Stable, Themed
I suggest installing Nova launcher it is amazing you can customize so many things that is ridiculous. I installed that one and uninstalled the one that comes with the ROM and I couldn't be happier.
Sent from my Nexus 10 using xda app-developers app

the_real_fosgate said:
Hello,
me once again
Is it possible to spread the dock icons further?
Because they are very close together.
Bye
Robert
Click to expand...
Click to collapse
I'm working on this. Again this seems to be a "feature" of CyanogenMod at the moment and has to do with how the screen is scaled on the N10 to fit the larger screen. You'll notice that the icons remain the exact same width when you rotate to portrait. I believe there is some missing code somewhere in the launcher and systemUI which stretches to fit the screen.

asweiler said:
I suggest installing Nova launcher it is amazing you can customize so many things that is ridiculous. I installed that one and uninstalled the one that comes with the ROM and I couldn't be happier.
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
Any lag on the home screen and menus when using Nova? I always found it to lag my other devices, but haven't used it much on the N10.

asweiler said:
Thanks for the nice little simple guide at the hell of a lot easier to understand than all the other ones I found. If I have any problems with making it it flash able, even with looking at the different guides out there. I know I can come to you, thank you. My goal is to incorporate be modifications that allow me to modify the bottom bar, the Quick Settings bar with the message settings app, the notification LEDs, and to be able to make my ROM updatable over the air. I bet this will be a very difficult thing to achieve but nothing easy is worth doing.
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
All the code for the bottom bar is in SystemUI.APK, it also ties in with code in Settings.APK which allows you to configure it's buttons.
As for OTA, I don't think you'll be able to do that because you need a server which you can poll and check updates against. At the moment most of the original CyanogenMod code is still there, I've just deleted references in the layout.xml for settings.apk so they do not show up in the menus. I'll have a look at some stage to see if I can modify the code to simply point to my own server, but I doubt it will be that straight forward.
I got an invite yesterday to list my ROM on RomManager, so I'll look into that as an option for now. I don't rank it high on the list of things to do though as it does not affect ROM functionality at all. I'd rather work on improving other things

[ROM][Linux] Ubuntu Touch Preview on TF300T [WIP]

I am working on porting the latest upstream version and will update this post as things start working.
Things to do:
[DONE] Create boot image that boots into the Ubuntu Touch rootfs.
[DONE] Create Android container started by Ubuntu.
[WIP] Customize configurations and work on kernel and android system to make things work properly (e.g. audio).
[TODO] Setup apparmor security.
Testing, debugging and optimization...
Any help is welcome!
The information and images below are very out-of-date.
The port of Ubuntu Touch to our beloved TF300T is more or less working now.
Please see section "Known Issues" below.
And please read the instructions carefully, including the linked threads, before doing anything to your tablet that might result in a very expensive paper-weight.
Known Issues
Just listing major issues that are specific to the TF300T port.
This is not the place to discuss general issues with Ubuntu Touch.
Camera is broken.
Dock not fully supported.
There are probably more; please follow this thread and report any new issues you find.
Downloads
Please read the section "Installation" below carefully, if you are not sure what these files are.
That section also contains verbose information on the different bootloader versions.
The binaries are generated automatically by Jenkins.
Generally they are not tested and may be broken.
Please report any issues in this thread, so they can be fixed and broken binaries can be removed.
Bootloader 4.2
These are the latest binaries that should be up-to-date with respect to Canonical's binaries.
Well, sometimes allow a day or two...
Android Base-System
The Android base-system is a stripped-down version of CyanogenMod 10.1 with some additional patches.
This is, where the major effort for porting Ubuntu Touch goes into.
Ubuntu Touch Root FS
This is the Ubuntu Touch file system.
Flashing this ZIP will preserve network settings and the phablet home directory, if you had installed Ubuntu Touch before.
It should work for all devices, however a stripped-down version with some changes for our TF300T is provided.
Please see the list of changes below.
Media Files
These media files are part of Canonical's root fs, but they rarely (never?) change.
Splitting the media files into a separate image significantly reduces the size of the rootfs that receives regular updates.
Unless you manually remove /data/ubuntu, these files will persist re-flashing the rootfs.
Bootloader 4.1
These are out-of-date and are no longer being maintained.
They will be kept, till dev-host deletes them (30 days after the last download):
Android Base-System
Ubuntu Touch Root FS
The rootfs for bootloader 4.1 also includes the media files. There is no separate download.
Android Source Code
The patched repositories of the Android/CyanogenMod/Ubuntu source trees are available on GitHub.
For details, please see section "Building the Android Base-System from Source" below.
Ubuntu Touch Root FS Changes
The "official" Ubuntu Touch root fs does not quite work on our TF300T yet.
So a stripped-down version with the following changes is provided:
Run amixer on boot to fix mixer levels.
Disable save/restore of alsa settings.
Split media files into a separate image.
Remove several big and unnecessary files.
The official Ubuntu Touch image does work, but for these issues:
Flashing with TWRP fails.
For details, see the bug report on launchpad.
There is no sound, unless you adjust alsa mixer levels manually.
Rebooting from Ubuntu goes into a boot-loop.
When Ubuntu is properly shut down, it saves the current alsa settings.
Restoring them on the next boot crashes the system and causes the boot-loop.
Note that rebooting from Android or using adb works fine.
If you happen to run into the boot-loop, use the TWRP file manager (in the Advanced menu) to remove /data/ubuntu/var/lib/alsa/asound.state.
Installation
Please read the following instructions carefully, and make sure you understand each step and what it will do to your tablet.
The steps are working for me, but you are ultimately responsible, for what you are doing with your own tablet.
I will not be responsible, if you brick your tablet, or if your wife gets angry at you for being too preoccupied with your tablet.
Step 1: Unlock Your Tablet
If you want to give Ubuntu Touch a try, your tablet needs to be unlocked.
There are lots of threads helping with this, please use search to locate this information.
Step 2a: Which Bootloader Do I Have?
Unfortunately, Asus has released several incompatible bootloaders.
To find out, if you can use this port of Ubuntu Touch, go to the bootloader screen by holding the power and vol-down keys.
Once you see the bootloader screen with three or four icons in the center, check the long version number at the top of the screen.
It looks something like: "WW_epad-10.6.1.15.3-20130416".
The first two letters are your SKU and should not matter.
The version number following "epad" is what will be referred to in the following.
Version 10.6.1.15.3
This is the latest version from Asus, generally referred to as "bootloader 4.2" in the XDA forums.
The latest Ubuntu Touch binaries are developed and tested on this bootloader, so you should be fine.
Version 10.6.1.8
This is an older version of the bootloader 4.2.
The latest Ubuntu Touch binaries might work for you, though upgrading your bootloader is recommended (see below).
This version is known to cause issues with the latest TWRP recovery, so be careful.
Version 10.4.2.20
This is the old incompatible bootloader, generally referred to as "jb bootloader" or "bootloader 4.1" in the XDA forums.
The latest Ubuntu Touch binaries will not work for you, upgrading your bootloader is strongly recommended (see below).
Older binaries that work with this bootloader are still available for download though.
Any older version not listed
Your bootloader is really out of date and you should upgrade as soon as possible (see below).
Any newer version not listed
You are on uncharted territory. Proceed with care!
Let us know about your experience in this thread!
Step 2b: Upgrade Your Bootloader
If you have not yet installed bootloader 10.6.1.15.3, it is recommended to upgrade.
Please check the following threads (and several others; search might be helpful):
[GUIDE][26/04]Update/Recovery/Root/Downgrade Android 4.2.1 on Unlocked/Locked Devices
[HOW-TO] Upgrade or Downgrade to any stock JB Firmware
Step 3: Install TWRP Recovery
You need a custom recovery installed for flashing the Ubuntu Touch binaries.
Please check the following thread for getting and installing TWRP recovery:
[RECOVERY][TF300T/TG] TWRP 2.5.0.0 Touch Recovery!
Step 4: Backup and Wipe Your Android System
Before flashing Ubuntu Touch, you need to wipe some parts.
It is strongly recommended to make a backup of your Android system too.
Check section "Restore Android" below on how to restore it.
If you are running CyanogenMod 10.1:
Use TWRP to backup "boot" and "system".
Backing up "data" is not strictly necessary, but recommended.
Wipe "cache", "dalvic cache" and "system".
In TWRP 2.5 you should use "Wipe -> Advanced Wipe" and check the respective boxes.
Note that this will not wipe the contents of your "/sdcard" Android folder.
If you are not running CyanogenMod 10.1, but another ROM:
Use TWRP to backup "boot", "system" and "data"
Wipe "cache", "system" and "data".
In TWRP 2.5 you should use "Wipe -> Advanced Wipe" and check the respective boxes.
Note that this will not wipe the contents of your "/sdcard" Android folder.
Step 5: Flash Ubuntu Touch
If you want a clean start or you had installed Ubuntu Touch for bootloader 4.1, please remove /data/ubuntu manually before flashing.
You can use the TWRP file manager in the Advanced menu for that.
If you want to upgrade from a previous Ubuntu Touch for bootloader 4.2, please see section "Upgrade Ubuntu Touch" below.
Flash the following images (see above for downloads):
ubuntu-touch-system-XXXXXXXX-tf300t-bl4.2.zip
ubuntu-touch-rootfs-raring-XXXXXXXX-tf300t-bl4.2.zip
ubuntu-touch-media-XXXXXXXX.zip
Step 6: Reboot Your Tablet
Note that there is no boot animation yet, so the screen will be black, till the shell is starting up.
This make take some time, please be patient!
Restore Android
Boot into TWRP recovery.
Wipe "cache" and "dalvic cache".
Select the last backup done before installing Ubuntu Touch.
If you were running CyanogenMod 10.1:
Restore "boot" and "system".
If you were not running CyanogenMod 10.1, but another ROM:
Restore "boot", "system" and "data".
Reboot your tablet.
Upgrade Ubuntu Touch
Generally, the system and the rootfs can be upgraded individually.
However, sometimes Canonical introduces breaking changes, that require them to be upgraded together.
Upgrade ubuntu-touch-system-XXXXXXXX-tf300t-bl4.2.zip
If you are running an older version of that ZIP, you can just flash the new one.
If you have returned to your Android system, please follow "Backup and Wipe Your Android System" under "Installation" above before flashing the new ZIP.
Upgrade ubuntu-touch-rootfs-raring-XXXXXXXX-tf300t-bl4.2.zip
You can flash this ZIP anytime.
Network settings and the phablet home directory will be preserved. This includes the media files from the separate ZIP:
If you want to start clean, remove /data/ubuntu manually and re-flash both rootfs and media.
Upgrade ubuntu-touch-media-XXXXXXXX.zip
You can flash this ZIP anytime.
It will just overwrite existing files and add new files; old files will not be deleted.
If you want to start clean, remove /data/ubuntu manually and re-flash both rootfs and media.
Building the Android Base-System from Source
Basically you can follow the guide for building CyanogenMod with one exception.
Initialize your CyanogenMod source repository with:
Code:
repo init -u git://github.com/f69m/android -b phablet-10.1-tf300t
You can also run this command in an existing repository.

Thats great, but ...
f69m said:
Current Status:
Ubuntu Touch is booting and can be accessed via adb, but the screen stays black.
Click to expand...
Click to collapse
I have the exact same issue even on the official build released for nexus 4 ... The current release of Ubuntu is just such a mess, nothing more than a buggy preview with loads of fake apps and content, and very limited functionality.
I'd love to see Ubuntu on tf300, but I would say (in my humble opinion,) lets wait for a better release, and then we'll get started.

Shu. said:
I have the exact same issue even on the official build released for nexus 4
Click to expand...
Click to collapse
Oops, that is intersting, thanks!
I'd love to see Ubuntu on tf300, but I would say (in my humble opinion,) lets wait for a better release, and then we'll get started.
Click to expand...
Click to collapse
Agreed, if your interest is to have something to play with.
On the other hand, I'd like to see, what is already there and possibly help improve it by contributing to Canonical. And any work we do now will speed up porting, once there is a better release available.
Just trying some more Kernel tweaks after looking at the TF700 port that seems to work (see http://forum.xda-developers.com/showthread.php?t=2162472).

Re: [DEV] Porting Ubuntu Touch Preview to TF300T
Shu. said:
I have the exact same issue even on the official build released for nexus 4 ... The current release of Ubuntu is just such a mess, nothing more than a buggy preview with loads of fake apps and content, and very limited functionality.
I'd love to see Ubuntu on tf300, but I would say (in my humble opinion,) lets wait for a better release, and then we'll get started.
Click to expand...
Click to collapse
Agreed but I have gotten it up and running on my nexus 4 without much issue, its cool for about 20 min( being generous) but then you realize you can't actually do anything. I feel that its gonna be an awesome platform especially for a transformer tablet though if it goes where they say it will. Full Ubuntu when docked and then touch when not....sounds like what these tablets were made for.
Sent from my Nexus 4 using xda premium

Still not working build ? (
It's pity, i would like to try it, I know, that there is only something functions, but I can try the UI, and how it is look like
Maybe someone from TF700 thread who port it for TF700 can help us.

matonka007 said:
Still not working build ? (
It's pity, i would like to try it, I know, that there is only something functions, but I can try the UI, and how it is look like
Maybe someone from TF700 thread who port it for TF700 can help us.
Click to expand...
Click to collapse
Just checked the wiki.ubuntu.com/Touch/Devices site, looks like someone has committed to porting it. Though I wouldn't be in a rush to get it just yet seeing as it barely functional. I guess time will tell where this leads.

ColMustard said:
Just checked the wiki.ubuntu.com/Touch/Devices site, looks like someone has committed to porting it. Though I wouldn't be in a rush to get it just yet seeing as it barely functional. I guess time will tell where this leads.
Click to expand...
Click to collapse
lol, if you looked at the developer on the wiki you would realize that the developer on it is the originator of this post

Re: [DEV] Porting Ubuntu Touch Preview to TF300T
doubljdog said:
lol, if you looked at the developer on the wiki you would realize that the developer on it is the originator of this post
Click to expand...
Click to collapse
Yes I realized that after I posted this. Just pointing out that someone has committed to porting this.
Edit: Thanks for pointing out the obvious though,I'm sure nobody else would have figure this out
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD

So, is there someone working on it, or not?
I installed the one from tf700 on my tf300 and it works decent, except wi-fi, so I'm guessing its not that hard, but i'm not a dev..so...

How did you load the patch in your make file? I am adapting your patch to my device.

secosan said:
So, is there someone working on it, or not?
Click to expand...
Click to collapse
Yes, I am working on it, and so are some others.
I installed the one from tf700 on my tf300 and it works decent, except wi-fi, so I'm guessing its not that hard, but i'm not a dev..so...
Click to expand...
Click to collapse
That is interesting, thanks!
What happens on the tf300t using the CM tf300t base code is a segmentation fault.
The nv video drivers send a null file pointer to fputc() in the Ubuntu libc.
Just trying to do a quick fix, by building my own libc that silently ignores the null pointer, but that is sure not a final solution.
Eventually we need to figure out, where the null pointer comes from and avoid it.
I'll let you know, how it works, once the lenghthy ARM compilation has finished and I had a chance to try it.
WLAN is working fine, BTW, just the display is black.

giveen said:
How did you load the patch in your make file? I am adapting your patch to my device.
Click to expand...
Click to collapse
Are you referring to my patches on GitHub?
Not quite sure, what you are asking for.
Anyhow, the patches for the package makefile and for the kernel are on GitHub
https://github.com/f69m/ubuntu-touch-tf300t.
The changes to the Android repository manifest are described on
https://github.com/f69m/ubuntu-touch-tf300t/wiki/Build-Ubuntu-Touch-for-ASUS-Transformer-TF300T
Apart from those patches it is really the same as building CyanogenMod. Just faster, as only a part of the CM tree is built.
Does that answer your question?

Canonical started the daily building of Ubuntu Touch, good news I tryied the build for TF700 too, but it have bad DPI.
PS: f69m, I do not know about developing, but if I can help you write.

Re: [DEV] Porting Ubuntu Touch Preview to TF300T
f69m said:
Are you referring to my patches on GitHub?
Not quite sure, what you are asking for.
Anyhow, the patches for the package makefile and for the kernel are on GitHub
https://github.com/f69m/ubuntu-touch-tf300t.
The changes to the Android repository manifest are described on
https://github.com/f69m/ubuntu-touch-tf300t/wiki/Build-Ubuntu-Touch-for-ASUS-Transformer-TF300T
Apart from those patches it is really the same as building CyanogenMod. Just faster, as only a part of the CM tree is built.
Does that answer your question?
Click to expand...
Click to collapse
I was referring to the screen res patch, but I figured it out from your guide.
The problem I am having that my kernel not compiling with Ubuntu options even though I sent them in my defconfig.
They should be working but they are not.
Sent from my Nexus 7 using Tapatalk 2

What is this link?
http://ubuntuone.com/06vcR0nyoTd9DYb2OgRSlT
Is on https://wiki.ubuntu.com/Touch/Devices as Android Base image, it is your build f69m ?

matonka007 said:
What is this link?
http://ubuntuone.com/06vcR0nyoTd9DYb2OgRSlT
Is on https://wiki.ubuntu.com/Touch/Devices as Android Base image, it is your build f69m ?
Click to expand...
Click to collapse
Definitely not my build, I have no images out yet, but mine should be coming soon!
The entry in the device table was not added by me.

Woohoo, I am seeing something!
The Ubuntu package build for my patched libc is still running tests, but I pulled the libc.so binary from the build directory.
This is a manual hack right now, I need to repackage the root FS for flashing and then will make it all available via Dropbox.
Hope that will allow quick downloads for everyone.

It sound great
Yes, Dropbox is good choice
And http://d-h.st/is not bad for sharing files

f69m said:
Woohoo, I am seeing something!
The Ubuntu package build for my patched libc is still running tests, but I pulled the libc.so binary from the build directory.
This is a manual hack right now, I need to repackage the root FS for flashing and then will make it all available via Dropbox.
Hope that will allow quick downloads for everyone.
Click to expand...
Click to collapse
Oh and then also please dont forget to update the install instructions on the official ubuntu page and here because on Ubuntu it links to your building guide on Github

-angel* said:
Oh and then also please dont forget to update the install instructions on the official ubuntu page and here because on Ubuntu it links to your building guide on Github
Click to expand...
Click to collapse
Of course, l will make sure to update everywhere, once the image is released, though the entry in the Ubuntu wiki was not done by me.
Got a flashable filesystem now, but that version is crashing on me. Must be something small I am overlooking atm.
So taking a little break and then will finish with refreshed spirit.