Android based on Linux - Desire HD General

Hi to all DHD users
I love my DHD, specially with all the options we have to modify (rom, etc.)
I use linux as my OS (Arch), android is based on the linux kernel.
I am a nerd and many of you in here are a little nerdie since you are here
It seems like most people are using windows as OS, nothing wrong with that, The android OS is "Linux kernel based" but most programs that are made is made for "flashing, modifying, etc." for windows:-(
I have used win, mac and linux for many years and linux is absolutely my favorite becasuse of all of its possibillities
I am no programmer and this is no linux promotion just an observation.
Thanks to all you DHD nerds

Yeah i use Linux Mint 10.
Linux ftw.

Arch linux with KDE here.

I dual boot Win 7 with Ubuntu 10.10.
The DHD is my Baby! Bless its little heart..

QtADB is a great cross platform GUI for ADB and Fastboot, I always assumed the reasons the tools tend to be windows biased is because windows users encompass the less geeky members of the android community

Related

Slight clarification for DEV's trying to port CM

THIS IS NOT A ARM DEVICE ! This is x86. Porting CM to this device would be an incredibly complex task as alot of CM code is ARM dependent. You are going about this the wrong way , these are two completely unrelated CPU architectures , you need to look at the Android X86 projects that are out there which I will link too at the end of the post.
ARM is vastly different from x86 and you can't run code designed for one on the other.
NO ROM for ARM will work on this , meaning no CM , no AOKP , no MiUi , and not even AOSP etc.
You need to work with the Android x86 sources provided by either Intel or the community x86 port.
Links :
http://www.android-x86.org
https://01.org/projects/android-intel-architecture
http://androvm.org/blog/
All these projects are FORKS of android highly modified to work on x86 !
lgstoian said:
THIS IS NOT A ARM DEVICE ! This is x86. Porting CM to this device would be an incredibly complex task as alot of CM code is ARM dependent. You are going about this the wrong way , these are two completely unrelated CPU architectures , you need to look at the Android X86 projects that are out there which I will link too at the end of the post.
ARM is vastly different from x86 and you can't run code designed for one on the other.
NO ROM for ARM will work on this , meaning no CM , no AOKP , no MiUi , and not even AOSP etc.
You need to work with the Android x86 sources provided by either Intel or the community x86 port.
Links :
http://www.android-x86.org
https://01.org/projects/android-intel-architecture
http://androvm.org/blog/
All these projects are FORKS of android highly modified to work on x86 !
Click to expand...
Click to collapse
What about use a base of stock roms and make the things work??? I know Cm its for armv, but all its adaptable,
Enviado desde mi XT890 usando Tapatalk 2
as for MIUI (there already is a MIUI port on the razr i, not complet I think, but it exist). MIUI is mostly a framework mod.. this is platerform independant AFAIK.
I don't think CM & Cie are so dependant of the SoC architecture. There's lot of différences between some ARM SoC .. maybe more than you can imagine. If CM can be adapt to so many device with so many ARM SoC witch a so différent, why not for a x86 Soc ?
I think you're a little bit pessimist here...
I didn't say it's impossible but it's more complex then a normal port for an ARM device. The issue is it requires more knowledge on the issue and will eat far more time. A CM port to x86 is a very unlikely goal for a single dev , and I'm saying this because a few months ago I discussed this issue with the people behind Android x86.
So a talented DEV will be able to achieve this but it will take time and a bigger struggle , that's why to start of developing for this device it would be more reasonable to look at Android code already ported to x86.
lgstoian said:
THIS IS NOT A ARM DEVICE ! This is x86. Porting CM to this device would be an incredibly complex task as alot of CM code is ARM dependent. You are going about this the wrong way , these are two completely unrelated CPU architectures , you need to look at the Android X86 projects that are out there which I will link too at the end of the post.
ARM is vastly different from x86 and you can't run code designed for one on the other.
NO ROM for ARM will work on this , meaning no CM , no AOKP , no MiUi , and not even AOSP etc.
You need to work with the Android x86 sources provided by either Intel or the community x86 port.
Links :
http://www.android-x86.org
https://01.org/projects/android-intel-architecture
http://androvm.org/blog/
All these projects are FORKS of android highly modified to work on x86 !
Click to expand...
Click to collapse
Sure there is some ARM dependent code in the repos but most of android doesn't really depend on the arch (like apps using the sdk dont need to be recompiled for working on the I, see play store apps). I have worked with o1 and android-x86 and there isn't really that much change from CM and android-x86, just some extra optimizations for x86 which can be added in later.
There are plenty of device on where even custom rom seems to be impossible. mostly because of a locked bootloader.
Look at the Motorola Defy. At the beginning, the development of a custom rom like CM was pretty impossible.... but they did it. They did it so far that the Defy became one of must used device with Cyanogenmod. And you now the most astonishing? It's thanks to only 2 devs.
I think bypassing a locked bootloader like the Moto one is far more tricky than adapting a CM ROM to a x86 SoC (while the device is natively unlocked).
AFAIK, android-x86 project is not so close to the Android we have on our phone.
When you develop a custom rom you can either take the AOSP source and try to put it on your phone : the tricky way. Mainly when you don't have access to the source of the drivers (ARM or x86 .. same fight)
Or you can take the official rom and mod it to reach the AOSP/CM/MUI/etc level. And I think on most device it's the way to go (unless the manufacturer release all the source code of the device.... something that never appends).
lgstoian said:
THIS IS NOT A ARM DEVICE ! This is x86. Porting CM to this device would be an incredibly complex task as alot of CM code is ARM dependent. You are going about this the wrong way , these are two completely unrelated CPU architectures , you need to look at the Android X86 projects that are out there which I will link too at the end of the post.
ARM is vastly different from x86 and you can't run code designed for one on the other.
NO ROM for ARM will work on this , meaning no CM , no AOKP , no MiUi , and not even AOSP etc.
You need to work with the Android x86 sources provided by either Intel or the community x86 port.
Links :
http://www.android-x86.org
https://01.org/projects/android-intel-architecture
http://androvm.org/blog/
All these projects are FORKS of android highly modified to work on x86 !
Click to expand...
Click to collapse
You really know what you are talking about? As others already mentioned above CM is in most a framework - porting android to x86 seems to be not such a big gap as motorola did it already and for sure you can run android on your pc - do you own an arm pc (in this case i think an rasperry pi...). The toolchain remains the same so why you make such a story out of it? Are you a razr i owner or do you just want to frighten all razr i devs and owners awaiting a CM port??
ARM architecture is different in some points but most of the work will do the compiler and to be honest i think there will be some more x86 phones in the future, intel never developed it for one or two phones....
So what is your intention with this topic??
kind regards.
lord0815 said:
So what is your intention with this topic??
Click to expand...
Click to collapse
That's what I'm wondering. Any dev that's taking on this task obviously knows it's going to take a bit of extra work. It would have been different had the OP offered some help and advice, but he just posted the obvious while making it seem like a bigger deal than it is (at least I'm guessing it's not as big a deal as he makes it seem, considering the other posts in this thread). Nothing but fear mongering and pessimism at this point. Sure, we will have to wait a bit for the devs to figure things out, but I know enough of them picked up this phone that something will eventually come. Plus, there seems to be a bit of dev interest in the Intel Yolo as well.
I don't know much about porting or developing and getting cm to run with all the necesary source and drivers is probably not easy but I do know that one of the basic options when running the build/make command for AOSP and CM is an x86 build for emulation. So basic x86 infrastructure exists does that ensure compatibility with this phone maybe not but it might help and certainly it would still require SOC and device optimization drivers but its probably the better place to start then tackling trying to port ARM based code and drivers.
However in the meantime my thinking is maybe a CM style rom could be achieved by first stripping down the rom making it "blurless" and then porting CM features especially since the latest Moto ROM's are comparatively closer to stock then sense or touchwiz. Of course I don't have the phone yet its in England waiting to be brought to me.

[Q]Building Native Debian? Nexus7 Grouper

Hi all i was think about building Debian 8 (jessie) for our nexus since the last major full desktop we had was ubuntu 13.04 anyway my question is how would i go about this and would anyone feel like helping as i have only a little rom building knowledge as im not sure really where to start for putting debian on our nexus.
I would suggest looking into armhf images, ubuntu desktop 13.04 documentation and Multirom documentation.
I'd suggest building upon ubuntu core 14.04 LTS however : http://cdimage.ubuntu.com/ubuntu-core/releases/14.04/release/
Probably much less painful ^^
Aurora

{Q} Custom ROMS (AOSP/CM) for Galaxy A8 (SM-A800F)? Any possibility in Future??

Hello all
I was wondering if there will be AOSP/CM ROM for this device, not a single ROM is available and no dev is interested to work on such a great device.
Such a totally crap device, still stucked on 5.1.1 since launch, no dev is interested in the development either, where android n announced already, we are still waiting for Android M update, i wasted my money on such a **** device, will never buy a sammy mid range in future, m totally fed up with this
I think because there are few developer with that phone and they can't test their work. You can port ROMs such as CM to you phone by your self. There are tons of guides and forums. All u need is a linux OS (such as ubuntu, debian and others) and sources.
DeadSquirrel01 said:
I think because there are few developer with that phone and they can't test their work. You can port ROMs such as CM to you phone by your self. There are tons of guides and forums. All u need is a linux OS (such as ubuntu, debian and others) and sources.
Click to expand...
Click to collapse
Ok i want to port Resurrection Remix on my A8, i need a simplest guide for android build environment startup, using windows 10, with no knowledge about programming languages such as C++ etc etc which is required to be used on Linux OS, can you plz help me, i will install ubuntu OS on my laptop, but i am worried can i install two different os in one machine, i.e. Windows 10 & Ubuntu
shubham540 said:
Ok i want to port Resurrection Remix on my A8, i need a simplest guide for android build environment startup, using windows 10, with no knowledge about programming languages such as C++ etc etc which is required to be used on Linux OS, can you plz help me, i will install ubuntu OS on my laptop, but i am worried can i install two different os in one machine, i.e. Windows 10 & Ubuntu
Click to expand...
Click to collapse
yep, I'm on kali and I use windows 10 to play games, so the only thing is: take care when partitioning. After you installed ubuntu there is a bootloader called "GRUB" and there you can choose if you want to boot windows or linux

How can you install a recent linux distro?

It looks like there are drivers for linux that support the GPU, according to the Nintendo Switch community.
Is there a way to install a modern Ubuntu/Debian distro on the box?
Any guide links?
Someone mentioned that an apt-get upgrade would break the OS. Is this still the case? I hope it won't brick the box ,..
Nvidia made a version of Ubuntu 14.04 available called Linux4Tegra. I haven't heard of anything newer.

[DEV-HELP][UBPORTS] Patching kernel with Halium to boot Ubuntu Touch GSI?

I recently came across this UBports port from @erfanoabdi that allows Ubuntu Touch to be booted as a GSI A/AB image. It requires a Halium-patched kernel though, and I don't possess the programming knowledge yet to compile a kernel and the required patches from the tree, can anybody here help with this so that we can get Ubuntu Touch running nicely on our Zuk Z2 Plus?
From what I've noticed on this forum, it seems that progress on getting this device to boot Ubuntu Touch has been helmed by @S.8506.A so I'd guess that this person already has a Halium-patched kernel they could share here. Honestly, it'd be a great win for the power-user folks among us to be able to boot Ubuntu Touch, run Android apps with Anbox when required, and even run desktop apps (so-so) with Libertine containers. Not to mention the privacy capabilities that come with booting Linux.
P.S. There's already this [Treble][GSI] Ubuntu touch for Oneplus 3/3T, note the very similar hardware (esp. identical chipset) between the op3t and z2_plus

Categories

Resources