Is there a way to install older Android versions? Pre-Lollipop - LeEco Le Pro3 Questions & Answers

I need to install an Android version that uses Dalvik/Java and not ART, any way this can be done? And/or "dual boot" your phone?

No. You can use an Android emulator on your PC, on the other hand. Buying an older phone like the G2 would make more sense to me.

Maybe, but dunno if the device drivers or chipset would support anything older. Who knows, you might be able to compile a CyanogenMod build based on KitKat or something.
As mentioned above, use an emulator or dual boot Android on PC. Check out the Android x86 project and the official Android emulator.

Related

[Q] Android API Choice

This probably sounds like a stupid question BUT, when developing for Android, should I just use the latest google api/SDK available or should I install them all on eclipse? I'm grabbing them all from 2.0 onwards atm but is there any point?
No. Just get the latest. It will be able to handle the latest kernels and older ones so it would make sense to just get one (the latest one). Good luck in your development.

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] 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.

Android 4.4 x86 emulator image

Hello guys. Well, since Android 4.4 x86 image for emulator is not yet available for download from google's or intel's repositories, I built my own build. It's just pure Android 4.4 built from official repositories, no customizations. So, if you don't want to spend 5+ hours building it yourself, you can download it here:
DOWNLOAD
So i have just one question , Can I use this image to boot android on my pc via usb ?
drive2droad said:
So i have just one question , Can I use this image to boot android on my pc via usb ?
Click to expand...
Click to collapse
To be honest, I'm not sure. You could be able to use it this way, but it's not made for this purpose. If you would like to use it for this purpose, you should get ISO image or build one yourself.
How do I change this into a ISO file so I can install it to virtualbox?
Guys, this is image for x86 emulator. If you want to have an ISO image, you should compile it yourself.
I have never compiled anything before. Is there some specific way to do it and is it easy? If not then where would I get the x86 emulator to make this image work?
Updated to version 1.1 - now uses branch android-4.4_r1.1
P.S.: I will not answer any questions which could be easily found on google
So I am guessing this is for the android sdk emulator then? If that is the case then it is a little too complicating for me. Isn't sdk emulators mostly for developers and enthusiasts? I am just interested in using an image for putting it on vmware and installing it for use. Well I guess I am off to search google for such a thing and if I find it I guess I will not bother to share it as it would seem everyone knows how to use google to find things that are "simple" to find as aptnutella says. Seriously why would I be asking about such a thing if I didn't already know that it is somewhere in google if I didn't already look. I have been searching everywhere and only found things about the sdk emulator. So I suppose I will keep searching since it is suppose to be simple enough to find.
Updated to version 1.2 - tag android-4.4_r1.2
If you are Arch Linux use, you can find package in AUR.
willmon22 said:
How do I change this into a ISO file so I can install it to virtualbox?
Click to expand...
Click to collapse
sorry, slightly offtopic:
if you want to learn how to compile and x86 build go here:
http://www.android-x86.org/getsourcecode
for an 4.3 build, to install via usb, look here:
http://www.android-x86.org/download
do a new iso with link please :good:
aptnutella said:
Hello guys. Well, since Android 4.4 x86 image for emulator is not yet available for download from google's or intel's repositories, I built my own build. It's just pure Android 4.4 built from official repositories, no customizations. So, if you don't want to spend 5+ hours building it yourself, you can download it here:
DOWNLOAD
Click to expand...
Click to collapse
Download link does not work - opens a blank page

{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

Categories

Resources