Database Users

Android based on Linux

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

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.

Firefox OS on 4010x (Android)?

I have an Alcatel OT 4010x, the Android version of OT Fire (I guess). Firefox OS should be able to run on my phone, right? If yes, can I request for a rom to flash in (and steps, if it's different from flashing an android rom)? Or maybe can someone please point me in the right direction? I have look around Firefox wiki page and XDA's Firefox OS page, but, it seems there's only a guide to port Firefox OS to other phones, can't find an OT Fire's rom anywhere.

Firefox OS needs Android ICS or higher
As far as I know, Firefox OS requires that you have Android ICS. XDA has some articles on how to install Firefox OS on specific devices such as HTC HD2, Samsung galaxy and Sony Xperia.

Ron Shinde said:
As far as I know, Firefox OS requires that you have Android ICS. XDA has some articles on how to install Firefox OS on specific devices such as HTC HD2, Samsung galaxy and Sony Xperia.
Click to expand...
Click to collapse
Isn't that like dual-boot or something? How about something like clean install or anything of sorts? Sorry if it's a noobish question, but, I don't really know about flashing a new OS, I only know about flashing roms of Androids.

[Q] Firefox OS on "unsupported" device?

I'm developing some apps for Firefox OS, but am currently limited to doing so on the Firefox OS Simulator. I'd like to flash Firefox OS onto a real device, but I own none of the supported devices, and of some of them I can't even find a single mention anywhere on the internet with the exception of the wiki.
Now I have this very slow Cherry Mobility Android JB (originally ICS) tablet lying around. Would there be any chance of getting Firefox OS running properly on this device, or is it a lost case? If I remember correctly, it has Linux 3.2 underneath it (the Android ROM which is currently on the tablet, I mean). Would I be able to extract the drivers from the Android ROM and use them with Firefox OS?

if you play around with the manifest xml files, you might have some success. You could have a look at the threads of the nexus (forum.xda-developers.com/showthread.php?t=1924367) or samsung ports () to get a better idea of porting. You can also have a look at B2G, might help you out.

Anyone have resources for porting ROMs?

I've been wanting to get into porting ROMs, although I'm not too sure how to go about it. I have a few in mind I'd like to attempt to bring to our device. Does anyone have any resources/links/videos on how to go about porting? Everything would be greatly appreciated

Which ROMs do you have in mind? I might be able to help.
P.S: You can look in the LineageOS porting instructions for our device, if that's going to help you!

proudlytm said:
Which ROMs do you have in mind? I might be able to help.
P.S: You can look in the LineageOS porting instructions for our device, if that's going to help you!
Click to expand...
Click to collapse
A few of the ones I've been thinking would be a good fit for this phone is the Pure Nexus Project, Slim7 (Want to get a fully working build of that going, love Slim7 haha), OmniRom, and lastly a MIUI port once I get the basics down.
I use macOS, but also have a virtual machine for both Windows 7 & 10 and Ubuntu and Fedora so any guides across any platforms help.

fireball0093 said:
A few of the ones I've been thinking would be a good fit for this phone is the Pure Nexus Project, Slim7 (Want to get a fully working build of that going, love Slim7 haha), OmniRom, and lastly a MIUI port once I get the basics down.
I use macOS, but also have a virtual machine for both Windows 7 & 10 and Ubuntu and Fedora so any guides across any platforms help.
Click to expand...
Click to collapse
I know different ROMs use different structures for device trees, but here's a guide to compiling Lineage 14.1 to the G4 Play. This guide is made for Ubuntu 14.04/15.04/16.04, but Fedora might be able to work as well as long as you can get the proper packages installed during the prerequisite steps:
http://wiki.lineageos.org/harpia_build.html
It may not help much with other ROMs, since I'm not sure if the other ROMs support using CM/Lineage based device trees to build, but this will give you the basic instructions on how to download source, get the proprietary blobs/device tree you need, and compile everything to a working zip.
As for actually making device trees for other ROMs to use during compilation, that I don't know myself, and was never really able to find out.

I build on Fedora. If you're using Fedora 25, use these steps to set up a build environment: https://gist.github.com/sultanqasim/09f19221c67c71edd099eb86c6a92467