Hello,
Currently I'm running Debian Wheezy [armel] [xfce] on my vk810. I love this app; however I would like to use the framebuffer instead of VNC.
I am also having issues properly configuring the frame buffer so that it functions. currently the device freezes when I stop the android gui and initiate the debian gui. I have yet to get it working successfully, trying multiple DPI, and frame buffer settings.
I'm thinking it would be awesome to run debian from my vk810, having the enviroment displayed through my slimport. Idealy it would be nice to assign debian a seperate framebuffer than the android enviroment so that I can use both enviroments simultaniously without using a 3rd party machine running the VNC client.
So.
Has anyone had any luck with successfully running the linux deploy enviroment through their frame buffer, if so what settings/enviroment/architecture did you use.
Is it possible to run android and linux deploy environments on seperate frame buffers? ie. Android on the device display and debian on the slimport attached display.
I'd also love to hear some feedback from those who have been successfully using Linux Deploy on their LG G Tab 8.3's. What do you find works best, what distro/arch are you running, and how are you dealing with limited arm7 support.
For those of you who do not know what Linux Deploy is, you can check it out here. If you also have a better recommendation for a linux deployment suite please share!
Thanks.
Very interested in this. Was running AntiX with Fluxbox, and now Mint on my laptop and couldn't get vnc to work at all. Must have been doing something wrong.
Anyway, having a separate partition for Linux on android would be awesome! Don't really know what I would do with it other than a decent browser and maybe gimp?
I'm willing to give it a go as well. I'm sure it will be a learning curve though.
How are you doing this with a locked boot loader? Or is it not relevant? Regards,
sleekmason said:
Very interested in this. Was running AntiX with Fluxbox, and now Mint on my laptop and couldn't get vnc to work at all. Must have been doing something wrong.
Anyway, having a separate partition for Linux on android would be awesome! Don't really know what I would do with it other than a decent browser and maybe gimp?
I'm willing to give it a go as well. I'm sure it will be a learning curve though.
How are you doing this with a locked boot loader? Or is it not relevant? Regards,
Click to expand...
Click to collapse
basically you use the already running kernal for your android system, using linux deploy or a few other scripts i've seen around the web allow you to boot an armel or armhf architecture using the already running android kernal.
To get a native debian or Arch system running on this device would be awesome, but I would just be happy with figuring out native frame buffer setup and having the ability to switch from the device screen or the slimport hdmi output.
I'm thinking this may be possible seeing how the device screen has an independent frame buffer from the slimport [fb1].
I'm personally just starting to experiment with it, I'm not that experienced but I think it has a lot of potential on the vk810, not just because of the dpi [243] but also becuase of the slimport accessibility.
crashtheface said:
basically you use the already running kernal for your android system, using linux deploy or a few other scripts i've seen around the web allow you to boot an armel or armhf architecture using the already running android kernal.
To get a native debian or Arch system running on this device would be awesome, but I would just be happy with figuring out native frame buffer setup and having the ability to switch from the device screen or the slimport hdmi output.
I'm thinking this may be possible seeing how the device screen has an independent frame buffer from the slimport [fb1].
I'm personally just starting to experiment with it, I'm not that experienced but I think it has a lot of potential on the vk810, not just because of the dpi [243] but also becuase of the slimport accessibility.
Click to expand...
Click to collapse
I'm running the 510, so it may or may not be the same, but have you looked into the kernel settings for the framebuffer? When messing around in the 510 file I remember seeing a couple of options there for the config but don't know if they are relevant or not. I will look at it again to see if there might not be something else that needs to be turned on or compiled in.
sleekmason said:
I'm running the 510, so it may or may not be the same, but have you looked into the kernel settings for the framebuffer? When messing around in the 510 file I remember seeing a couple of options there for the config but don't know if they are relevant or not. I will look at it again to see if there might not be something else that needs to be turned on or compiled in.
Click to expand...
Click to collapse
I would look into the kernal issue but I have no idea what I'm doing. You could very well be right. I'm using the stock vk810 kernal I wonder if the 510 builds are compatible, and if they are if anyone has messed with the frame buffering.
crashtheface said:
I would look into the kernal issue but I have no idea what I'm doing. You could very well be right. I'm using the stock vk810 kernal I wonder if the 510 builds are compatible, and if they are if anyone has messed with the frame buffering.
Click to expand...
Click to collapse
Well, the cool thing is that if you look in my signature below you will see a link on How to roll your own kernel, and it is literally copy and paste all the way through. The only difference for your device would be in the read me that comes with the kernel source. Specifically, the version of the google toolchain to use, and the name of your devices "defconfig" in the kernel source..
In other words, one line to change slightly, and that's about it. You should be able to get the source from lg... Same basic location as I have outlined.
Wheezy should be just fine.
on another note, I did look at my kernel source file and for the most part everything looks real good. Slim bus is the way it should be with no further options and everything enabled. Frame buffer support should all be there except for console support. Which, I don't think we need any way. There was also support for virtual frame buffer, which is used for debugging purposes and I turned off for my most recent compile just to see how it'll work because it may or may not use a little more memory. Also there was a pretty cool option for turning on one of three Linux logos for your Android during boot I may mess with that a little bit.
Seriously, you should check out the kernel building. Its all there. The only thing that isn't is the Loki support, and that should be no sweat using one of the 500 kernel zip scripts. Either of the other two active kernel developers would help you with that. I'm sure.
---------- Post added at 06:52 PM ---------- Previous post was at 06:19 PM ----------
Okay, just checked out linux deploy through your link. Looks pretty cool but I dont understand the vnc bit. Is it installing a linux image on the sdcard and then booting from that? AND where does vnc come in? is it all in the device itself?
Okay, I get it now. Am downloading now. Using Ubuntu with precise and armhf. We'll see
sleekmason said:
Okay, I get it now. Am downloading now. Using Ubuntu with precise and armhf. We'll see
Click to expand...
Click to collapse
Yeah the VNC work around is kind of gimmicky, it also is assumed as the default config. I'm sure what is being done with Linux Deploy is easily accomplished with chroot and a few scripts in android terminal, but the gui is pretty straightforward and has worked pretty well for the distro's i've tried it with. Like I said earlier our LG's have a lot of potential with the slimport and the ability to run two environments side by side.
I just started reading into your make your own kernal I'm looking forward to what I learn. Thanks so much for this resource!
Okay, couple of things...
Our devices should support armhf no problem and it will be faster than armel. Also, might want to go testing rather than wheezy even though wheezy will be stable. I'm thinking here of the packages for armhf, and I really don't have any evidence this would be better. just a thought.
Also, From what ive read (which isn't much yet), SSH is what most are using as an interface, but vnc is for the graphical environment? Eh.. okay.
Our framebuffer should support 32 bit. I don;t have a clue about most of this yet.
Tried the unbuntu distro and there were packages missing. giving it a go on Debian testing now. Probably be tomorrow before I try anything more.
Looked up other ways to install linux and only saw this and another as a viable option, with this one being the better of the two.
and, here's the skinny...Debian Wheezy was the only one that would work. I tried testing, unstable, and squeeze. I didn't feel the need to go back any further.
using the frame buffer only wouldn't help you unless all you wanted to use is the terminal environment. All of the controls are through the VNC client. This kind of makes the framebuffer environment obsolete unless you have only a specific task in a script that you want to run.
I was able to use armhf no problem it worked just fine. I also used multi VNC as my VNC client.
I understand what they did now. I think it would be easier to simply break apart their program to see what all was put into the image, make your own image on your home computer with everything that you want to have. for instance, instead of using Debian Wheezy, you can use a lite version of Debian running fluxbox, with only the apps that you think are good, and nothing else and transfer it over to your tablet. This would make the image very small. I didn't have any trouble at all with the processing power of our tablet. So that won't really be a factor, but space will.
the 1 item I discussed being off in the kernel may very well be the one that needs to be checked in order to use the frame buffer. Or it is also possible that there is only one option that he gives that allows for that and you can see that option when you set everything up. if I remember right, it was under the distribution choices? Anyway, not a very usable or useful beastie at this point is it? I downloaded gimp and Iceweasel just to try a few apps and it pretty much sucked trying to navigate around.
if you can think of some really cool reason to use it, maybe some script or useful app that doesn't require a lot of navigation I might try to build an image with it already together.
Related
After searching the forums and installing different kernel versions and quite a few froyo roms, I have found android to run very well on my kaiser. One thing really bugs me though and would prevent me from using this as a day to day OS: All over the place there seem to be artifacts, pixels that do not belong there. It really does break the overall look and feel of the system. Does anyone have an solution for this?
Yes i did search, it might be that my phrases arent correct. I just cant seem to find an existing solution for this. It has to be a display module problem, since it happens on every single rom I tested.
Thanks in advance
Sounds like you have selected the wrong panel type in the kernel.
Kaiser's were shipped with 3 different panels over the production time, you will need to play around and see whether yours works best set as 1,2,3 with atools.
Since i dont have a linux pc available right now, i opted for a kernel that was already set to panel 2. Would be really cool if the community could upload version for all 3 types. Thanks for the pointer. I might just create 3 kernels and upload them to share.
you don't have to run a linux pc to use atools to edit kernels
http://forum.xda-developers.com/showthread.php?t=783514
Yeah i havent had time to test it, I have 2 linux machines running at home. Although this line kinda made me not test it under windows:
"If you are a stupid windows user you can't use it so don't ask!"
Thanks a bunch dude
You're reading into that too much! I would assume that since you figured out how to get Android on your Kaiser you aren't stupid. There are different kinds of windows users, stupid ones, smart ones, etc.
I'm also going to assume that because you also use linux you probably aren't the stupid windows user. I use atools on windows and it works great. Try a different LCD type, it should fix your issues (although I still get some weird artifacts with both type 2 and 3 on some kernels and type 1 never works).
Okay I managed to get the problem sorted out using atools and selecting Panel 3. Now I have a booting 2.6.32 kernel, no artifacts. Rom seems a little sluggish, but I am sure if i fiddle with the kernel enough, it should show some speed improvements. Thanks for the help guys, makes me remember why I loved this place and my htc's so much
I cant seem to find any work around to compiling ICS or greater on a 32 bit linux system. As I understand, this is not supported anymore(atleast from 2.3.x and greater). I have a 64 bit windows computer though. Would any developer chime in and let me know what they would do?
I was thinking of just running(dual booting) ubuntu on my newer windows machine but did not know if this would work for this purpose. I really just wanted to build my own jb rom from AOSP and gradually expand my knowledge from there. Thanks for any input.
slimb9 said:
I cant seem to find any work around to compiling ICS or greater on a 32 bit linux system. As I understand, this is not supported anymore(atleast from 2.3.x and greater). I have a 64 bit windows computer though. Would any developer chime in and let me know what they would do?
I was thinking of just running(dual booting) ubuntu on my newer windows machine but did not know if this would work for this purpose. I really just wanted to build my own jb rom from AOSP and gradually expand my knowledge from there. Thanks for any input.
Click to expand...
Click to collapse
It's not recommended that you try building on a 32bit machine though there are modifications listed out there that *might* allow you to build AOSP from it. You are perfectly capable to dual booting Ubuntu on your Windows machine and that'll work fine. Even a virtual machine would work.
i first tried a virtual machine, that actually was harder to set up, it needed bios correction, network stuff, shared folders, guest extensions, cpu blablabla. in the end a single build took like 8 hours and the pc got so busy that i could barely move the mouse so the whole point of a virtual machine was kinda moot. installing ubuntu was easier than i thought. i wouldnt go for the newest version though. i did that and installing oracle java on 12.04 was not simple, actually that was the most confusing thing i ever had to deal with and i know computers since i was a boy.
molesarecoming said:
i first tried a virtual machine, that actually was harder to set up, it needed bios correction, network stuff, shared folders, guest extensions, cpu blablabla. in the end a single build took like 8 hours. installing ubuntu was easier than i thought. i wouldnt go for the newest version though, i did that an installing oracle java on 12.04 was not simple, actually that was the most confusing thing i ever had to deal with and i know computers since i was a boy.
Click to expand...
Click to collapse
http://www.techlw.com/2012/07/install-sun-java-6-or-7-in-ubuntu-1204.html
Pirateghost said:
http://www.techlw.com/2012/07/install-sun-java-6-or-7-in-ubuntu-1204.html
Click to expand...
Click to collapse
funny, the tutorial i got was two pages long lol. anyway, i got it working then, ics compiled flawless. along came jb, breaking in the end because of weird proguard EOF errors. that was the point i switched to 11.something, now it works again. :cyclops:
molesarecoming said:
funny, the tutorial i got was two pages long lol. anyway, i got it working then, ics compiled flawless. along comes jb and breaks in the end because of proguard EOF errros. that was the point i switched to 11.something, now it works again. :cyclops:
Click to expand...
Click to collapse
i havent had any issues with JB compiling on a few of my machines... so far. actually just sitting down now to set up my new build VM on my esxi farm... i think 16 cores + 16gb ram should do the trick....
thanks for the input. i was under the impression running ubuntu alongside windows was probably the best. i pretty much setup everything on my laptop, got to building the jb rom from source and it spit out errors at me. I realized that I was an idiot for trying it on a 32 bit system after numerous hours of setup
I am new to doing all this myself and definitely new to trying to compile my own rom. I have experience writing some code but for think or swim which has nothing to do/doesnt help me at all with android. Thanks for the quick responses. Thought it would be awesome to learn everything. gotta start somewhere.:silly:
With the release date of the Ubuntu phone Images announced, are any developers preparing to port it the the arc? I hope the spec can handle it as I would love Ubuntu to see my beloved Arc out!
http://www.ubuntu.com/devices/phone/operators-and-oems
minimal specs are :512 mb -1 gb ram+
4-8GB eMMC + SD - we dont have enoth storge we have only 1 gb....
1ghz procesor +
Will ubuntu pwned android?
Hmmm short term answer will be NO
But long term, we wont know
what is eMMC?
thelast3lack said:
what is eMMC?
Click to expand...
Click to collapse
It's internal storage
What if we use a mod like data2sd adatped for Ubuntu OS? Like the users of Asus Transformer, that used fast class 10 sd cards to dump all the system related files there? Will that be a possible solution?
Sent from my Xperia Arc S using xda app-developers app
Porting Ubuntu Phone to Xperia Arc (S)
Jet70355 said:
What if we use a mod like data2sd adatped for Ubuntu OS? Like the users of Asus Transformer, that used fast class 10 sd cards to dump all the system related files there? Will that be a possible solution?
Click to expand...
Click to collapse
It depends. You don't need to port stuff like data2sd, the best solution would be to mount some directories at the sdcard which aren't immediatly needed at boot. I want it as well, but I'm still rather unexperienced with porting os'es to ARM devices. I do know something about linux.
For example: In my (basically unused) Ubuntu installation (I run Arch Linux as main OS) 75% of the total 2.5 GiB is used by the dir '/usr'. If we could mount that on the sdcard, 1 GB is plenty for the rest. Putting '/usr' on another partition/disk is not that uncommon in linux, so it should work. Also, if you download applications, most of it goes in /usr. (other directories we have to put on the sdcard are /opt (some kind of /usr) and /home ofcourse)
Space is no problem. One of the problems is that the Xperia Arc runs on an ARMv7 processor, and the Galaxy Nexus (which will receive Ubuntu Phone on 22 feb) is ARMv9.
evertheylen said:
It depends. You don't need to port stuff like data2sd, the best solution would be to mount some directories at the sdcard which aren't immediatly needed at boot. I want it as well, but I'm still rather unexperienced with porting os'es to ARM devices. I do know something about linux.
For example: In my (basically unused) Ubuntu installation (I run Arch Linux as main OS) 75% of the total 2.5 GiB is used by the dir '/usr'. If we could mount that on the sdcard, 1 GB is plenty for the rest. Putting '/usr' on another partition/disk is not that uncommon in linux, so it should work. Also, if you download applications, most of it goes in /usr. (other directories we have to put on the sdcard are /opt (some kind of /usr) and /home ofcourse)
Space is no problem. One of the problems is that the Xperia Arc runs on an ARMv7 processor, and the Galaxy Nexus (which will receive Ubuntu Phone on 22 feb) is ARMv9.
Click to expand...
Click to collapse
I heard that the processor isn't a big problem, as it should run on wide range of devices. Something about kernels or something...
Processor
replicant101 said:
I heard that the processor isn't a big problem, as it should run on wide range of devices. Something about kernels or something...
Click to expand...
Click to collapse
'Big' is relative of course. We will need to compile everything for ARMv7, because I assume Canonical won't have repositories for every architecture possible from the start. If Canonical releases ARMv7 stuff from the start, the main problem would be to get the different components to work, just like an Android ROM. Ubuntu Phone will use Android drivers they said, so hopefully it'll work.
If there's anyone that wants this on their Xperia Arc S and wants to help as well, please contact me or post something in this forum.
I will try my best to get this up and running on the Arc, but I can't promise anything. I'm not an experienced developer.
evertheylen said:
'Big' is relative of course. We will need to compile everything for ARMv7, because I assume Canonical won't have repositories for every architecture possible from the start. If Canonical releases ARMv7 stuff from the start, the main problem would be to get the different components to work, just like an Android ROM. Ubuntu Phone will use Android drivers they said, so hopefully it'll work.
If there's anyone that wants this on their Xperia Arc S and wants to help as well, please contact me or post something in this forum.
I will try my best to get this up and running on the Arc, but I can't promise anything. I'm not an experienced developer.
Click to expand...
Click to collapse
i am ready to help, although i dont have any experience with these kinds of developement.
i have an lt18i.
I think we are waiting on ubuntu to publish the wiki page about how to port it to other devices, once its up then we can have a crack at it
It is published. unfortunately i cant sync those HUGE sources because of low diskspace left (for compiling which has been taken up by other projects). hopefully as i clean up, you may expect a build soon. I said may, not will.
disc space isn't an issue over this end, how big is it?
Edit: 15GB, thats a big download.. D:
Around 15 gigs I think. With more needed for binary compiling. It says so in the guide
Im on a 40gb download limit a month, and I've already used most of it up :/
i would love to have a port of this
but unfortunatly, i am not able to help, as i do not know how to succesfully port
Sent from my sending thing..
Stupid computer y u no fast
I'm ready to help, I'm not s dev but would be willing to test though.
Roland
Sent from my Nexus 7 using Tapatalk HD
Volunteers needed
Hello everyone, I want, just like you, Ubuntu Touch on my Xperia Arc (S). I'm willing to spend a lot of time on it, although I'm not an experienced developer, I think I might be able to do it. For the moment, I have no immediate plans to port it, I'm first trying to understand it better. I've already encountered a lot of possible problems, but thank Canonical that they have made Ubuntu Touch so easy to port. (based on CM 10.1, using the same display driver, ...)
I would like to have a list of people that want to help or test. I'm not a real fan of doing everything in a forum, so perhaps we could make a google project or so. What do you think?
As someone's who's just switched from a dual boot of linux mint / Windows 7. To Just Ubuntu, I would be interested if it were to come to our architecture, but I thought ubuntu needed dual core processors? And obviously HDMI won't be available.
Google Apps isn't native to ubuntu right? So what kind of ecosystem would we be moving to? Also there is no lockscreen which is a little concerning, but the device itself works like BlackBerrys new OS, which is nice.
Sent from my LT18i using xda app-developers app
I would test it, as I'm no developer I can't do anything else
We already have the ability to boot multiple ROMs and plenty of kernels available. Ubuntu Touch is not being built because it is based off of CM10 (4.2) which flo/deb never ran and as a result are unsupported. However, what is stopping devs from using the kernels available to boot full ARM versions of ubuntu, debian, arch or gentoo? I've looked at the nexus 7 2012 and there has been plenty of such development, even sooner after its release. Is this nexus doomed to solely run android due to the qualcomm processor it possesses?
Also, please note, I'm not looking to run linux INSIDE android (chroot method). That is possible on just about every android device known to mankind and nothing special. I want to run linux as a ROM. This has been previously accomplished on popular tablets like the nexus 7 2012, note 10.1 and the transformer prime, just to name a few.
Bump?
Do you have any links regarding a native linux implementation on the 1st gen Nexus 7? I'd like to look into it, sounds interesting.
I found two separate attempts to bring Linux on this tablet:
wiki.merproject.org/wiki/Community_Workspace/Tegra3/Nexus7 and github.com/Bogdacutu/flo-Fedora
None of them are successful yet - I guess display (or any other debug output method) is a blocker here. AFAIK Tassadar has managed to make an UART cable - delta.fratler.de/68-raiders-lost-uart/
Managed to run Bogdancutu's flo-Fedora (updated to F20 though), but I cannot get the screen to work. Any ideas/tips?
vrutkovs said:
I found two separate attempts to bring Linux on this tablet:
wiki.merproject.org/wiki/Community_Workspace/Tegra3/Nexus7 and github.com/Bogdacutu/flo-Fedora
None of them are successful yet - I guess display (or any other debug output method) is a blocker here. AFAIK Tassadar has managed to make an UART cable - delta.fratler.de/68-raiders-lost-uart/
Click to expand...
Click to collapse
The first is for the original nexus 7, seeing how it is Tegra3.
vrutkovs said:
Managed to run Bogdancutu's flo-Fedora (updated to F20 though), but I cannot get the screen to work. Any ideas/tips?
Click to expand...
Click to collapse
Mind posting a link? I can't find the thread on xda.
NVM: https://github.com/Bogdacutu/flo-Fedora
Still chroot, not exactly native, but the screen is run through X11 as opposed to a vnc server. Pretty good actually.
Here's Ubuntu on the 1st gen Nexus 7:https://wiki.ubuntu.com/Nexus7/Installation
x10knight said:
Here's Ubuntu on the 1st gen Nexus 7:https://wiki.ubuntu.com/Nexus7/Installation
Click to expand...
Click to collapse
Really not necessary, the nexus 7 2012 forum here on xda and a google search will yield that. Completely different SoC and other peripherals don't let the tutorials carry over.
dwegiel said:
The first is for the original nexus 7, seeing how it is Tegra3.
Click to expand...
Click to collapse
There is a small addition there that flo's version boots but display doesn't work. I've also found attempts to run graphics via libhybris (build.merproject.org/project/packages?project=home%3Acxl000%3Anemo%3Adevel%3Ahw%3Agoogle%3Amsm%3Anexus7) but I never managed to try Mer.
Hi guys.
I managed to get the basic linux kernel v3.16-rc6 to work on the Nexus 7 2013 (WiFi).
Turns out the debug cable I originally used (delta.fratler.de/154-nexus-7-uart-unlocked/) works perfectly fine.
I use the qcom_defconfig as base and will work my way up from there, creating a n7-device tree.
In order to get linux to talk to you via the serial port, you'll need a couple of fixups though.
Namely:
codeaurora.org/cgit/quic/kernel/skales/plain/atag-fix/fixup.S – this is due to the fact that the N7 bootloader hands over the wrong memory-mapping in its ATAGS (shifted by 2 MB)
Compile it with
gcc -c fixup.S -o fixup.o; objcopy -O binary fixup.o fixup.bin
Then merge the fixup, kernel and the dtb:
cat fixup.bin zImage dtb > bootImage
Next up, to prevent the console from freezing, you need to grab this file from the qcom repo over at linaro:
git.linaro.org/landing-teams/working/qualcomm/kernel.git/commit/a751c4d71e792784f4d9f399bfda04007a6f403d
Note that the UART-port has been renamed from ttyHSL to ttyMSM.
Here's the kernel-config I used (based on qcom_defconfig): paste.debian.net/113411/
Once the dts resembles something remotely useable, I'll post it as well
dTatham said:
I managed to get the basic linux kernel v3.16-rc6 to work on the Nexus 7 2013 (WiFi).
Click to expand...
Click to collapse
This is great! Did you manage to have ssh there at least? I don't have UART cabel, but I'd really love to help you with this
vrutkovs said:
This is great! Did you manage to have ssh there at least? I don't have UART cabel, but I'd really love to help you with this
Click to expand...
Click to collapse
Unfortunately not yet.
I'm currently having some issues getting USB to work. The patch to implement the QCOM PMIC8921 extender's GPIO ports has only been submitted 2 weeks ago and I have yet to figure out how to implement it in the devicetree - If anyone can give me some pointers to that...
I'll set up a github repo for the linaro kernel with the Nexus 7 dts this week. Once I have some rudimentary support (USB, eMMC, WLAN), I'll start upstreaming.
Still no real progress but things on the linux-arm-kernel mailing list have been moving pretty quickly so I hope we'll have a decent patch set within the next two weeks or so.
In the meantime, I wrote up a basic guide to get things started if you're interested in porting a vanilla kernel to the N7:
delta.fratler.de/168-nexus-7-kernel/
Trying Complete Linux Installer from Play Store made me personally conclude any conventional desktop Linux UI at the moment is unfit for using on gadget display. But I wonder what takes so long to simply wireless mirror screen dual view and extended desktop to dlna, Chromecast, etc 3rd party display. Phone/tablet can then function as desktop/laptop too with ultra mobile workstation also.
Verstuurd vanaf mijn Nexus 7 (2013), iPad Mini Retina of Moto G Lte
i found this but havent been able to follow the instructions fully throught
https://github.com/crondog/arch-flo
Would be awesome if anybody made a mrom out of this etc so the development could continue faster/easyer
dwegiel said:
We already have the ability to boot multiple ROMs and plenty of kernels available. Ubuntu Touch is not being built because it is based off of CM10 (4.2) which flo/deb never ran and as a result are unsupported. However, what is stopping devs from using the kernels available to boot full ARM versions of ubuntu, debian, arch or gentoo? I've looked at the nexus 7 2012 and there has been plenty of such development, even sooner after its release. Is this nexus doomed to solely run android due to the qualcomm processor it possesses?
Also, please note, I'm not looking to run linux INSIDE android (chroot method). That is possible on just about every android device known to mankind and nothing special. I want to run linux as a ROM. This has been previously accomplished on popular tablets like the nexus 7 2012, note 10.1 and the transformer prime, just to name a few.
Click to expand...
Click to collapse
Ubuntu Touch Is Available.
See MultiROM Manager.
Is there any dev out there that would be interested in bringing Ubuntu touch to our ZF2?
Quite an interesting OS and seems like it would fit in great with the x86 CPU we have available to us.
I know there are other threads requesting this no dev responded to it saying if it would be feasible or impossible to do so.
I like to do it , but you know our device is a x86-64 and ubuntu touch is a project for ARM arch , I'll check it if there is any chance !
but if you want linux in your device you can use kali nethunter , that i am makeing flashable zip for zf2 with say99's help and support .
it is based on debian just like ubuntu ...
miradli said:
I like to do it , but you know our device is a x86-64 and ubuntu touch is a project for ARM arch , I'll check it if there is any chance !
but if you want linux in your device you can use kali nethunter , that i am makeing flashable zip for zf2 with say99's help and support .
it is based on debian just like ubuntu ...
Click to expand...
Click to collapse
Thank you as long as it is attempted, I'll be happy.
Yes I have tried many of those other methods for running Linux but none work for the 16gb Ze551ml as apparently Linux deploy can't use the external SD card.
I'll definitely try out yours when it is ready!
Christopher876 said:
Thank you as long as it is attempted, I'll be happy.
Yes I have tried many of those other methods for running Linux but none work for the 16gb Ze551ml as apparently Linux deploy can't use the external SD card.
I'll definitely try out yours when it is ready!
Click to expand...
Click to collapse
now you can try it , the flashable zip file are here :
http://forum.xda-developers.com/zenfone2/development/kali-nethunter-t3329426/post65669770#post65669770
Christopher876 said:
Is there any dev out there that would be interested in bringing Ubuntu touch to our ZF2?
Quite an interesting OS and seems like it would fit in great with the x86 CPU we have available to us.
I know there are other threads requesting this no dev responded to it saying if it would be feasible or impossible to do so.
Click to expand...
Click to collapse
I know alot of you guys want ubuntu touch on the zenfone just for something different but its not worth it considering all the work that would have to be put into it just "to try something new". ubuntu touch is miles behind android
All other ubuntu phones are ARM based - if you'd try, this would be the first one on an intel chipset. I imagine there are a lot of things broken in the x64 version of the code since no one's really using it. If you do, please do check out ubports.com which has other open source ports of android device.
Personally, i own a BQ Aquarius 4.5 with ubuntu touch because i was interested enough to want to play around with it. It is a functional OS, but it lags heavily in apps. The OS is also very tightly screwed down - every app must run in user space with only write access to the user home. Interaction is limited through the ubuntu service layer, which means its quite difficult to code an app for say - whatsapp - because the service layer must sit in between you and the whatsapp API.
The major promise of Ubuntu is the convergent future - where the phone or tablet can actually run the full ubuntu API with access to all regular ubuntu apps, either old (sandboxed in lxc/lxd) or new (running natively). The zenfone can definately run both but it lacks the usb c and mhl connectivity to drive a screen directly; perhaps when miracast is implemented properly in ubuntu OS it may become interesting to port. Until then, I'm not sure its worth the effort and all the x64 bughunting.
Niropa said:
I know alot of you guys want ubuntu touch on the zenfone just for something different but its not worth it considering all the work that would have to be put into it just "to try something new". ubuntu touch is miles behind android
Click to expand...
Click to collapse
Rogier Oudshoorn said:
All other ubuntu phones are ARM based - if you'd try, this would be the first one on an intel chipset. I imagine there are a lot of things broken in the x64 version of the code since no one's really using it. If you do, please do check out ubports.com which has other open source ports of android device.
Personally, i own a BQ Aquarius 4.5 with ubuntu touch because i was interested enough to want to play around with it. It is a functional OS, but it lags heavily in apps. The OS is also very tightly screwed down - every app must run in user space with only write access to the user home. Interaction is limited through the ubuntu service layer, which means its quite difficult to code an app for say - whatsapp - because the service layer must sit in between you and the whatsapp API.
The major promise of Ubuntu is the convergent future - where the phone or tablet can actually run the full ubuntu API with access to all regular ubuntu apps, either old (sandboxed in lxc/lxd) or new (running natively). The zenfone can definately run both but it lacks the usb c and mhl connectivity to drive a screen directly; perhaps when miracast is implemented properly in ubuntu OS it may become interesting to port. Until then, I'm not sure its worth the effort and all the x64 bughunting.
Click to expand...
Click to collapse
I see. From these two answers it just isn't worth the work so I think just waiting is the best option and seeing if Ubuntu Touch develops more and if they support x86.
Never understood that this was the reason and I had always thought that it would be logical for Ubuntu Touch to support x86 rather than ARM. Thanks for these answers and clearing things up!
You're right that it might have made sense for Canonical to build on top of x64 primarily, but i believe they started the project in 2013 before there were any intel based phones on the market. Perhaps if ASUS and intel were quicker, it would have been