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
Related
I'm new to the forums and a novice programmer but here's my question:
There's an app I'd like to run on my device for work. Per the play store, the app requires Android 2.3.3 and I'm running 2.2.2. I'm running the most recent version of a custom ROM on an outdated device so can't update my device's build.
I'm wondering if it's possible to tweak the app's source code and repackage it to make it run on my device. I have downloaded the .apk file and tried to install it on my phone and get a parsing error. So with the help of google I have managed to get into the source code using dex2jar and jd-gui. Problem is I don't know much about how apks are written. I found something in the 'accessibilityservice' area that seems to check the android build version, but as far as I can tell that is checking for whether the device is running ICS (if build >= 14) whereas the app is said to be compatible with older builds as well.
Anyway - how complicated would it be to port an app backwards so that I could run it on my phone? You should assume that I'm already in over my head.
Thanks.
petegw42 said:
I'm new to the forums and a novice programmer but here's my question:
There's an app I'd like to run on my device for work. Per the play store, the app requires Android 2.3.3 and I'm running 2.2.2. I'm running the most recent version of a custom ROM on an outdated device so can't update my device's build.
I'm wondering if it's possible to tweak the app's source code and repackage it to make it run on my device. I have downloaded the .apk file and tried to install it on my phone and get a parsing error. So with the help of google I have managed to get into the source code using dex2jar and jd-gui. Problem is I don't know much about how apks are written. I found something in the 'accessibilityservice' area that seems to check the android build version, but as far as I can tell that is checking for whether the device is running ICS (if build >= 14) whereas the app is said to be compatible with older builds as well.
Anyway - how complicated would it be to port an app backwards so that I could run it on my phone? You should assume that I'm already in over my head.
Thanks.
Click to expand...
Click to collapse
A LOT of things changed from pre-2.3 to 2.3 in Android, code-wise. It was a huge upgrade, and a lot of unsupported things were implemented.
It's set to run on 2.3.3 simply because it uses functions that only exist in 2.3.3 and higher.
So to backport it you'd need to get the source code, check what functions require 2.3.3 or higher, edit them to use other functions/write the code yourself. You can't just simply remove the code that checks what version of Android you're running. That won't do a damn thing.
The last part is the near impossible one, because you'd most likely have to write code that goes deep into the Android framework.
If i were you, i'd simply look for another app that can do what you need and doesn't require 2.3.3 or higher. Though there aren't many out there. Most people base their app on 2.3.3 because like 95% or higher use that version (or a higher one).
If you were to dive into this, you'd need extensive knowledge of Android, Java & backporting.
Though i'm not able to help with that, at least the backporting part.
Moonbloom said:
A LOT of things changed from pre-2.3 to 2.3 in Android, code-wise. It was a huge upgrade, and a lot of unsupported things were implemented.
It's set to run on 2.3.3 simply because it uses functions that only exist in 2.3.3 and higher.
So to backport it you'd need to get the source code, check what functions require 2.3.3 or higher, edit them to use other functions/write the code yourself. You can't just simply remove the code that checks what version of Android you're running. That won't do a damn thing.
The last part is the near impossible one, because you'd most likely have to write code that goes deep into the Android framework.
If i were you, i'd simply look for another app that can do what you need and doesn't require 2.3.3 or higher. Though there aren't many out there. Most people base their app on 2.3.3 because like 95% or higher use that version (or a higher one).
If you were to dive into this, you'd need extensive knowledge of Android, Java & backporting.
Though i'm not able to help with that, at least the backporting part.
Click to expand...
Click to collapse
Thanks for the very helpful information. I will definitely not be attempting this.
Most likely will be getting a newer phone in a few months when I'm due for an upgrade so it'll be a moot point. Until then, I'll get by.
Hi sailors out there
When I'm going to read through the available sailfish threads the question about how to set up multirom & sailfish have been asked many times. So I thought I'm writing this little guide. I describe the procedure along the nexus 4 mako. But it have to be very similar on other devices like nexus 5 for example. The important parts that differs from mako are the kernel and modem image you've to use. I will describe the easiest way in my opinion. Experienced users have more capabilities to reach the goal. I will not describe how to install twrp recovery and unlock bootloader. Both are prequesites. Please use xda search or google to get this. But this little guide want's to be simple as possible. So let's begin .
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Beginning:
First we have to detect you're actual setup and where you want to go. Because nexus 4 is up to date I think the most common goal is to run android 4.4 as primary and sailfish os as secondary. Atm I have only paranoidandroid 4.4 on my device and will show you how to get everything working.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Requirements / Download following parts:
kernel aosp: http://d-h.st/A99
kernel cm: http://d-h.st/CCn
aosp = android open source rom. Ask in you're rom thread what version you're on with the rom
cm = cyanogen mod rom. Ask in you're rom thread what version you're on with the rom
Modem for nexus4 in version 0.84: http://d-h.st/cIJ
or
through an app in play store: https://play.google.com/store/apps/details?id=com.bpear.makomodem&hl=de
sailfishOS ea4: http://releases.sailfishos.org/sfa-ea/sailfishos-mako-release-1.0.8.19-EA4.zip
cm 10.1.3: http://get.cm/get/aWH
Multirom manager in play store: https://play.google.com/store/apps/details?id=com.tassadar.multirommgr&hl=de
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Before we're going on check up the following
1. All zip's you've downloaded have to be transferred on the device
2. Apps from play store are installed
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Installation process
Reboot in twrp recovery
Flash the new kernel
Flash the modem 0.84 in twrp. Or via the modem flasher from playstore. It's you're decision.
Boot back into android
Proof the functionality in android withe the new modem and kernel. Wlan working? Bluetooth? NFC?
Open mutlirom manager. Follow the installation steps.
After some time you'll be back in android. You have now the right modem, kernel and and a twrp multirom version on you're device
After this. Please reboot back into twrp recovery
There select the advanced button.
Then the multirom button
Select add rom and mark up the entry sailfish os
Press next.
Now you can choose two zip files to flash
zip1: Select the cm10.1.3 zip file
zip2: Select the sailfish EA4 zip file
Installation process is beginning.
After this select reboot
You automatically went into multirom where you can cancel the automatic boot process for the primary rom. Then you can select which rom you want to start.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
And the most important thing is to read: http://forum.xda-developers.com/jolla-sailfish/general/qa-sailfish-n4-thread-devices-t2727330 for further question before you ask. I have described there many things to start with sailfish. If you find this useful think about to press the thanks button.
I'm a bit confused why do you insist on updating the modem? I checked my modem version and it is newer so I imagine there is no need to update. Also why use such an old version ov CM?
Just asking because I did all according to your instructions except I used newer CM build and didn't update my modem firmware as it was already newer. But for some reason Sailfish wont boot. It just hangs showing Google at start.
anttimonty said:
I'm a bit confused why do you insist on updating the modem? I checked my modem version and it is newer so I imagine there is no need to update. Also why use such an old version ov CM?
Just asking because I did all according to your instructions except I used newer CM build and didn't update my modem firmware as it was already newer. But for some reason Sailfish wont boot. It just hangs showing Google at start.
Click to expand...
Click to collapse
lol. and you ask why it won't work? It gave reasons for the instructions. Also look in the linked q&a thread at the bottom of first post. And here for you the relaese notes. Hope things becomes clear now. enjoy
Release Notes:
This release is based on SailfishOS 1.0.8.19 (Tahkalampi).
The Nexus 4 port is considered to be of alpha quality.
Though depending on your usage it might be stable enough for daily use.
Download & installation instructions:
* Install adb and fastboot
a. Debian/Ubuntu: apt-get install android-tools-adb android-tools-fastboot
b. Fedora: yum install android-tools
c. Mac OS X: Install Homebrew from http://brew.sh/, then: brew install android-platform-tools
d. Windows: See http://wiki.cyanogenmod.org/w/Doc:_fastboot_intro for instructions
MultiROM ≥v28 ability is in the image. See options of how to layout your MultiROM in #2 post below.
Alternatively, just have it as your primary ROM:
* Install Android 4.2.2 (JDQ39) to your Nexus 4
a. Instructions here: https://developers.google.com/androi...s#instructions
b. Download links can be found here: https://developers.google.com/androi...ges#occamjdq39
* Download CyanogenMod 10.1.3 for your Nexus 4
a. Perform Factory Reset and wipe contents of the /data/ partition in case of leftovers from previous ROMs
b. The file you want to download is cm-10.1.3-mako.zip
c. Download links can be found here: http://wiki.cyanogenmod.org/w/Install_CM_for_mako
* Download the Sailfish OS for Android image for "mako"
a. The file you want to download is http://releases.sailfishos.org/sfa-e...0.8.19-EA4.zip
b. Another flavour filled with demo content: http://releases.sailfishos.org/sfa-e...mo-content.zip
* Install CyanogenMod 10.1.3 on your Nexus 4
a. Follow the instructions at: http://wiki.cyanogenmod.org/w/Install_CM_for_mako
* After flashing the "cm-10.1.3-mako.zip" file, flash the Sailfish OS .zip file in the same way ("on top of it")
* Reboot bootloader, Sailfish OS should boot and be visible
We recommend reading through http://jolla.com/guide/ -- some parts may not apply to Nexus 4
HW Support status:
(Look for Nexus 4 row): https://wiki.merproject.org/wiki/Adaptations/libhybris
Click to expand...
Click to collapse
Also I stated in first post why I only described the way I've did
Ahh ok nevermind got it working once I used the older CM image. Wifi seems not to be working but I guess that is because I didn't downgrade my modem firmware. I guess I'll wait for a more stable builde or better yet buy a Jolla phone. Just like having the nexus 4 as I can test bunch of operating systems on it.
anttimonty said:
Ahh ok nevermind got it working once I used the older CM image. Wifi seems not to be working but I guess that is because I didn't downgrade my modem firmware. I guess I'll wait for a more stable builde or better yet buy a Jolla phone. Just like having the nexus 4 as I can test bunch of operating systems on it.
Click to expand...
Click to collapse
yes. that's a great benefit of this device Do you like sailfish?
With modem version 0.84 you have all parts working in sailfish and android
Ok thanks for the hint. I used to be one of the early adopters of Jolla, but couldn't use it as my daily phone so I sold it, but now that the OS has matured I think I maybe swithing back. Even though I still think Nokia N9 had far better UI experience. If only some would port N9 UI to Sailfish
anttimonty said:
Ok thanks for the hint. I used to be one of the early adopters of Jolla, but couldn't use it as my daily phone so I sold it, but now that the OS has matured I think I maybe swithing back. Even though I still think Nokia N9 had far better UI experience. If only some would port N9 UI to Sailfish
Click to expand...
Click to collapse
I feel the same, don't know why, but i just loved the N9 and the way the OS worked. I am not saying that sailfish is bad or something, but there Are somethings missing ...
v3ng3anc32002 said:
I feel the same, don't know why, but i just loved the N9 and the way the OS worked. I am not saying that sailfish is bad or something, but there Are somethings missing ...
Click to expand...
Click to collapse
They've practically done nothing since pre-release to improve and refine the UI, and so many incredibly basic features are missing (voicemail notifications, global copy and paste etc). The pulley menus are ropey and the active covers feature hasn't really been made use of much. They seem to be mainly concentrating on the Jolla Launcher for Android, which will definitely make them higher profile ... but if all their software engineers and UX guys are working on that instead of Sailfish itself, then it seems like cutting off their nose to spite their face.
I'm not a fan of Android and I can't see myself ever using WP or iOS, but the lack of progress and their production priorities are a bit dispiriting. I'm hoping that they're holding a lot of big and waited for improvements for update 1.1 (October).
Anyway, I'll keep it as my main phone for a bit longer, despite the fact that I have a Z3C coming early next week. Hope to see a decent Sailfish port for it soon.
mudnightoil said:
They've practically done nothing since pre-release to improve and refine the UI, and so many incredibly basic features are missing (voicemail notifications, global copy and paste etc). The pulley menus are ropey and the active covers feature hasn't really been made use of much. They seem to be mainly concentrating on the Jolla Launcher for Android, which will definitely make them higher profile ... but if all their software engineers and UX guys are working on that instead of Sailfish itself, then it seems like cutting off their nose to spite their face.
I'm not a fan of Android and I can't see myself ever using WP or iOS, but the lack of progress and their production priorities are a bit dispiriting. I'm hoping that they're holding a lot of big and waited for improvements for update 1.1 (October).
Anyway, I'll keep it as my main phone for a bit longer, despite the fact that I have a Z3C coming early next week. Hope to see a decent Sailfish port for it soon.
Click to expand...
Click to collapse
hope the same for the z1c, but don't how is the chance to see this port (soon or later).
Works nicely on my n4. Looking for getting gapps to run....
mudnightoil said:
They seem to be mainly concentrating on the Jolla Launcher for Android, which will definitely make them higher profile ... but if all their software engineers and UX guys are working on that instead of Sailfish itself, then it seems like cutting off their nose to spite their face.
Click to expand...
Click to collapse
This is just wrong
mudnightoil said:
I have a Z3C coming early next week. Hope to see a decent Sailfish port for it soon.
Click to expand...
Click to collapse
I bought a z1c after my N9 broke and I totally regret it. But I'll go on and try using it with Sailfish one day
paulle said:
hope the same for the z1c, but don't how is the chance to see this port (soon or later).
Click to expand...
Click to collapse
I tried using the hadk but like some other devices, there are gpu-problems with the z1c (see https://wiki.merproject.org/wiki/Adaptations/libhybris/gpu).
Keep an eye on IRC logs and on the status matrix in mer wiki
sorry for off-topic
iuno said:
This is just wrong
I bought a z1c after my N9 broke and I totally regret it. But I'll go on and try using it with Sailfish one day
I tried using the hadk but like some other devices, there are gpu-problems with the z1c (see https://wiki.merproject.org/wiki/Adaptations/libhybris/gpu).
Keep an eye on IRC logs and on the status matrix in mer wiki
sorry for off-topic
Click to expand...
Click to collapse
thank you for information, followed your links to look at. It seems there for the z1c is a lot of remaining, we will need patience.
iuno said:
I bought a z1c after my N9 broke and I totally regret it. But I'll go on and try using it with Sailfish one day
I tried using the hadk but like some other devices, there are gpu-problems with the z1c (see https://wiki.merproject.org/wiki/Adaptations/libhybris/gpu).
Keep an eye on IRC logs and on the status matrix in mer wiki
sorry for off-topic
Click to expand...
Click to collapse
Don't think I'll regret getting the Z3C, from a hardware perspective ... held one the other day, as a friend had been gifted one by Sony. It's absolutely superb. Granted, I despise Android .. but for when the Jolla ****s itself / runs out of battery / when GPS or a camera is needed / roaming / skype /outdoor use, I can suffer it until there's a Sailfish port.
Hopefully as work is already under way for the One Plus One, the identical SoC used in the Z3 & Z3C won't be too much additional work.
For all the moaning and groaning about Mediatek, I'm guessing the simplest and best port of Sailfish will probably be for the Meizu MX4, as there'll be an Ubuntu ROM for it, and libhybris is used by Ubuntu Phone ...
Also, hopefully future iterations of the HADK will smooth out some of the problems porters are facing.
mudnightoil said:
Don't think I'll regret getting the Z3C, from a hardware perspective
Click to expand...
Click to collapse
it's the same for me...
The SoC in your z3c and 1+1 is actually the same as in z1c, I guess – 8974 vs 8974ac – only higher clocked.
You should not suppose that mediatek SoCs will be easier in general just because of is one working device. Jolla runs a Snapdragon and it works perfectly, most of the devices sailfish is currently ported to run snapdragons – with very different results.
iuno said:
it's the same for me...
The SoC in your z3c and 1+1 is actually the same as in z1c, I guess – 8974 vs 8974ac – only higher clocked.
You should not suppose that mediatek SoCs will be easier in general just because of is one working device. Jolla runs a Snapdragon and it works perfectly, most of the devices sailfish is currently ported to run snapdragons – with very different results.
Click to expand...
Click to collapse
I wasn't saying Mediatek in general will be easier (though it's possible), but any device with an official Ubuntu ROM certainly will (should) be - Meizu MX4 (Mediatek) is the first of those.
P.S. The Z3C is fantastic ... though unfortunately in black as opposed to the red I ordered (it's being swapped tomorrow).
Thank you very much for these instructions. i have one question though. In order to download CM 10.1.3, it says to click that link which takes you to download CM installer app. Ive used that app before and as far as I kmow, it doesnt let you choose which version of CM you want to install, instead it just sets you up to install the newest CM 11. I downloaded 10.1.3 from their site. Either way, no big deal.
Also, which kernel do I download to install? Aosp or CM?
Thank you
Still up to date
Hi,
are these steps still up to date or should we follow a different set up guide to install the latest sailfish OS on the Nexus 4? Because most, if not all, the links on the first page end up 404...
Bluetooth sync from Jolla to Nexus 4
Flashed my Nexus 4 with the factory 4.2.2 from google with radio .48 and then flashed cm-10.1-20131003-SNAPSHOT-TREATFORCOOPER-mako-signed.zip because that seemed to be the 10.1.3 mentioned in the guides to end up flashing the latest sfos from this guide http://forum.xda-developers.com/nexus-4/development/rom-sailfish-os-community-port-t2969823.
I didn't try calling, it has 3G network working and wifi is working but I can't seem to get the contacts from my Jolla phone using the Bluetooth sync from the settings.
Anybody has some advice on this?
Just had a good look at the wiki of devices on the mer website and found out the bluetooth is not yet working on the Nexus 4...
Works perfectly on my oneplus one
Link:
mod edit - links removed
Awesome!
I cannot see this post -__- You guys banned me for no reason at all!
I'm using it already but can't install any app (which i downloaded from apkmirror and they are compatible to nougat) but i haven't encountered any other problems so far.
Nifel said:
I cannot see this post -__- You guys banned me for no reason at all!
Click to expand...
Click to collapse
What's your username there?
In the meantime you can download it here:
From MEGA:
exe
https://mega.nz/#!JbRUnZ7T!jDLr34kK_dhUjuMEE6OJJ_S76x_L9U5JtnAaZj2bpC0
iso
https://mega.nz/#!hfZ1XRaL!YJLV1wTgh0jLkRhfs-uXRrzG1sByFWzMMjQ9LVofAkw
Direct link:
exe
http://files.phoenixos.com/os/PhoenixOSInstaller-v2.0.0-Alpha-60.exe
iso
http://files.phoenixos.com/os/PhoenixOSInstaller-v2.0.0-Alpha-60.iso
Android File Host Mirror:
.exe
.iso
my nextbook
Hello everyone,
I have a hybrid tablet is the nextbook flexx 11. I installed the Phoenix OS successfully, but when booting to the OS, the screen is vertical display of the tablet rather than horizontally when the keyboard dock (both Remix OS It is very difficult to do). I tried the auto-rotate screen but failed, so still. I think it does not pick up the sensor. Please let me ask you how to fix this. Any help or comment received a sincere thanks from me.
(Very sorry for my bad english)
Thank you all.
Look forward to everyone, good day i'm too bad!
Sorry for asking but can someone upload the rom for the nexus 9?
When i play game : Liên Quân Mobile. Phoenix,it is freeze when i playing it. Dell inspiron 3542,8gb harddisk for phoenix
how to root this build???
---------- Post added at 01:52 PM ---------- Previous post was at 01:50 PM ----------
run fast on my surface pro2 but need root access to install google application.
i just tried the rooted image from bbs.studiophoenix, didn't work for me but it could be meant for 64b, i did succed to get playstore to run after copying file from Remixos install. i do run Phoenix from an ext4 usb like all other x86 android distro on a atom 32b 1g mem.
Good experience til now better than bliss
update: it does work!
Hi guys,
Can someone confirm if this can run on a PC with an external monitor connected via HDMI?
If that this possible can you let me know the steps taken to get it to work?
Thanks!
sarveshrulz said:
Trick to get play store and root.
After installation replace system.IMG in phoenix is directory with this: https://mega.nz/#!rYBRlbLY]https://mega.nz/#!rYBRlbLY
Decryption key: !4x2UmG4Xq0r96u_7h_PwfqC5OjQNHR_Gv88fIL1d2BA
Click to expand...
Click to collapse
Link for mega is wrong. Try this - https://mega.nz/#!rYBRlbLY
slawdos said:
Link for mega is wrong. Try this - https://mega.nz/#!rYBRlbLY
Click to expand...
Click to collapse
No its right, I used it
wizmart said:
Yes, rooted with phonesky !!! thanks for your tip
Click to expand...
Click to collapse
Just press the thanks button
Hi, anyone with webwiew problems ? it just keep crashing...with xdalabs and some others apps as well. i did update webwiew but nothing changed...
Edit: mybad, I did switch multiprocessor webview in developers tab, turning back solved
Read up on libhoudini. I think Nougat x86 has only partial support for it. This might be the cause of problems.
Phoenix 2 will most likely stay alpha/beta for a long time.
Hey Vioner, any word on if the Nexus 7 image will be updated to 2.0? or will it be left on 1.1? Absolutely love Phoenix as an Android ROM, the desktop interface is exactly what I was looking for in a tablet ROM. It's too bad that Canonical dropped Unity 8 and Ubuntu Touch (I understand UBports is to be picking it up and switching it to wayland) because other than Phoenix, UT was the only other ROM that have the experience I've been looking for, so it will be sad to see Phoenix drop support (though completely understood)
@ShadowEO
I've just asked Phoenix OS officials about this. We'll see what they'll say.
One thing is for sure. They base their ROMs on AOSP and AFAIK most recent branch for Nexus 7 is Marshmallow.
The reason why they released a Phoenix OS 2.0 preview build for Nexus 9 is because it has official Nougat support.
I also asked them if they plan to do any updates for Nexus 7. I'll let you know.
@ShadowEO
I've the response. Phoenix team will release new versions only for Nexus 9. Older devices support is "dead". I'm sorry
Is there Android with Google Play for Rpi 3 B +? I understand it's a new technology, but it might be found somewhere.
Thanks for Answer
I am also hoping this happens soon, haven't had any luck finding an image. Wish I knew how to update the android 3b boot code to 3b+ given you can't just run apt update like in linux.
There is no useable android build for any Pi.
Anything new around here, by the way?
Would like to get Android on my Pi B+ to build a navigation device for my car.
Yes there is an Android build " Emteria " just go to there official website it works on nougat , with Twrp installed so u can flash Gapps and get play store working !
YashR1999 said:
Yes there is an Android build " Emteria " just go to there official website it works on nougat , with Twrp installed so u can flash Gapps and get play store working !
Click to expand...
Click to collapse
Very buggy, and you have to pay for it.
Since one month (or so) Android works on the 3 B+!
See here: https://forum.xda-developers.com/showpost.php?p=77361894&postcount=25
Need support for bluetoth 4.2
Hoerli said:
Since one month (or so) Android works on the 3 B+!
See here: https://forum.xda-developers.com/showpost.php?p=77361894&postcount=25
Click to expand...
Click to collapse
Can someone do support for bluetooth 4.2 please ?
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.