As the stock OS is 32bit, is it possible to compile 64 bit Android as a custom rom? I did not find any anything about this.
Never for Moto devices!
Moto uses 32-bit software always and the kernel sources are also 32-bit released by Motorola... So never can we get 64-bit roms,?
Related
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.
hi , i read detail of my device in most site with 64 bit processor like this :
Octa-core, 1500 MHz, ARM Cortex-A53, 64-bit
but when i download some Apk like SwiftKey Keyboard 64bit arm version and Try to install it , i got error and not installed at all
the Arm version install without problem .
so why This happened ?
is the 64bit processor is fake on my phone or some apps have bugs in 64bit version ? or the 64bit that Samsung mentioned is only part of main core of device software ?
we have seen a few 64bit capable samsung phones like Note 4 that never had a 64bit OS adapted.
Whether you have a 64bit or not, the 32bit installed system is your limitation, not the hardware.
PlutoDelic said:
we have seen a few 64bit capable samsung phones like Note 4 that never had a 64bit OS adapted.
Whether you have a 64bit or not, the 32bit installed system is your limitation, not the hardware.
Click to expand...
Click to collapse
is there any chance that on android 6 update , the system installed 64bit ?
or these phones just have some limit 64bit names in processor core
The 32bit version of app work nice too , i`m just curious cause sellers make 64bit cpu too big issue when we want buy
Same on A5, why we have 64 bit cpu when its not use,shame.
Arioman said:
is there any chance that on android 6 update , the system installed 64bit ?
Click to expand...
Click to collapse
I am not sure, you may want to ask the AOSP devs here if at least they have x64 builds.
As for stock sammy, i doubt it.
I just wanted to ask what's the difference between 32bit and 64bit in lenovo a6000/plus?
I already tried searching but couldnt find any topic specific to my question
I noticed most of the custom roms for this smartphone are also in 32bit. Isn't it 64bit is way better than 32bit?
Someone please enlighten me.
Thanks!
ae111james said:
I just wanted to ask what's the difference between 32bit and 64bit in lenovo a6000/plus?
I already tried searching but couldnt find any topic specific to my question
I noticed most of the custom roms for this smartphone are also in 32bit. Isn't it 64bit is way better than 32bit?
Someone please enlighten me.
Thanks!
Click to expand...
Click to collapse
Our CPU architecture is 64bit. But, the stock KK rom was for 32bit and later the Lollipop update utilised the 64bit design.
Technically, OS with 64bit would use memory and carry out processes in much better way to the full potential of CPU cores. But, in case of our device, the difference is negligible. So, you don't have to worry if a ROM is 32bit or 64bit, just flash it.
thanks for explaining!
For moto g5 plus there is 64bit custom rom will our device get 64bit to get Google camera 5.0 working.
Aby lad said:
For moto g5 plus there is 64bit custom rom will our device get 64bit to get Google camera 5.0 working.
Click to expand...
Click to collapse
Actually, g5 runs snap 625 which is a 64 bit architect processor, where as 617(just functional is each for us).
So now you may have understood that its not the rom but the support from processor.
One should have easily rom it till now. But what the use of psp in rural area[emoji16]
DgnrtnX said:
Actually, g5 runs snap 625 which is a 64 bit architect processor, where as 617(just functional is each for us).
So now you may have understood that its not the rom but the support from processor.
One should have easily rom it till now. But what the use of psp in rural area[emoji16]
Click to expand...
Click to collapse
Snapdragon 617 is also a 64bit processor but stock rom os is 32 bit same as g5 plus and htc a9 has same processor but has 64bit os .
Aby lad said:
Snapdragon 617 is also a 64bit processor but stock rom os is 32 bit same as g5 plus and htc a9 has same processor but has 64bit os .
Click to expand...
Click to collapse
True, i checked in snaps official page and 617 is a 64 bit processor, sry for posting w/o verification.
Pn developer about it, may they can reply more efficiently and tell us also what they says.[emoji6]
If you gays are not soooo lazy you have done some research on the active threads and found the the procesor is 64bit but the bus is only 32 so is not worty have a 64 bit os since the bus will need twice cicle to transport the data.
Htc a9 has 64bit os and it work fine
Moto G4 Plus 64 bit custom ROMs
Aby lad said:
For moto g5 plus there is 64bit custom rom will our device get 64bit to get Google camera 5.0 working.
Click to expand...
Click to collapse
Here it is.
https://www.xda-developers.com/moto-g4-plus-64-bit-custom-roms/
It is really nice that the developers are trying to make a x64 build for athene, but is los 15.1 the best option?
Because it is not stable by itself, and trying to make it stable AND 64 bit compatible at same time, isn't it too much effort? I understand that one way of thinking is "we can make it stable with 64 support already!", but maybe a port from 14.1, which is more stable, for 64 bit would show if it is worth or not (it will show what a 64 bits build can and cannot do, also performance), and in mean time, try to make 15.1 stable
I know that Dreamstar is doing almost all the job alone here (15.x and 64bits builds), so I'm thinking in try to make the 14.1 build port. I can code, but never did anything like that, not even close
I am running an unofficial lineage OS 17.1 ROM on my Moto X Play. The kernel used for the ROM has been open sourced and is available online. Now the Moto X Play is 64 bit on a hardware level, but Motorola forced it into 32 bit mode by installing a 32 bit OS on it. I am wondering if I can convert this kernel I found [here](https://github.com/MOTO-M8916/kernel_motorola_msm8916) to 64 bit, while still maintaining it's functionality with this lineage OS build found [here.](https://forum.xda-developers.com/moto-x-play/development/rom-lineageos-17-1-t4080411) The main reason I want to do this is because I have noticed that some apps are starting to faze out 32 bit support, and I think google is ending major 32 bit support in 2021-2022 from what I have heard. So I want to do this so I can still have the ability to use this phone in a few years, and to possibly allow other people to use this phone in a few years too. Is it possible to do this? If so, can someone explain to me how to do it or link me to a guide that explains how to do this? I already have some Linux experience as I run Linux as my main OS.