So I was reading a discussion about 64-bit exynos processors and a guy mentioned about sth intresting. What do you think, is this possible?
You are writing: The chip's firmware and drivers are running on a "CAL".
So I suppose it is not hardware limitation.
Could this change when they (or someone else) update their firmware, so that it becomes 64bit capable?
Click to expand...
Click to collapse
From all the various threads I've read making the exynos run 64-Bit is bootloader dependant. As the bootloader is closed source I think only Sammy can so it. I stand to be corrected on it though
sawdoctor said:
From all the various threads I've read making the exynos run 64-Bit is bootloader dependant. As the bootloader is closed source I think only Sammy can so it. I stand to be corrected on it though
Click to expand...
Click to collapse
If it is sammy dependent as you say, they won't make the exynos run 64-bit to keep it equal with Snapdrogon version since 805 is 32-Bit. Each processor has their our pros and cons depending on custom staff, performance and even a chance 64-bit support. It's really hard to choose...
Related
Hi everyone.
Devs, please read this: http://www.xda-developers.com/developments/mozillas-boot-to-gecko-running-on-a-samsung-galaxy-sii/
Is it possible for X8?
It looks like a nice OS, and i think that maybe it would be possible to make a custom bootloader that'll bypass android and directly boot into Boot-to-gecko. That would be waaay to cool
I haven't looked at the Boot to Gecko source (not even sure if Mozilla open sourced it yet), but chances are that this is meant for ARMv7 / TEGRA series CPUs
Since it's based on the underpinnings of Android I don't think that a change of the boot loader is really necessary, but it might require some efforts to port it to the ARMv6 series (unless Mozilla doesn't use ARMv7 specific code).
EDIT: On a second thought ... with this we're most likely back to old problem of DRIVERS for the X8.
B.Jay said:
I haven't looked at the Boot to Gecko source (not even sure if Mozilla open sourced it yet), but chances are that this is meant for ARMv7 / TEGRA series CPUs
Since it's based on the underpinnings of Android I don't think that a change of the boot loader is really necessary, but it might require some efforts to port it to the ARMv6 series (unless Mozilla doesn't use ARMv7 specific code).
EDIT: On a second thought ... with this we're most likely back to old problem of DRIVERS for the X8.
Click to expand...
Click to collapse
Yeah, you're right here, we just have to cross our fingers that Mozilla will use ARMv6 Compatible code.
About the drivers. Well, some of us, with older x8's have unlocked bootloader, so it shouldn't really be a problem. Plus, we have really good devs. Problems would be for those persons that have 11W29 + Phones
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 just bought a new Galaxy Tab 4 10.1 tablet and the model number is SM-T533. From what I've seen, the only difference is that the processor is a 64-bit snapdragon 410, vs the 32-bit snapdragon 400 from the other models. Does anyone know if ROMs for T530NU are compatible?
Thanks in advance .
only difference is that the processor is a 64-bit snapdragon 410, vs the 32-bit snapdragon 400
Click to expand...
Click to collapse
Not only ! This is a main and key difference
repey6 said:
Not only ! This is a main and key difference
Click to expand...
Click to collapse
Yeah, I know. I'm just wondering if the T530 ROMs are compatible or even if they can be installed at all. Maybe I'll have to wait until devs compile a version for this processor.
There is no custom recovery as far as I know as there is no source code for kernel. No way to root either unless you are on very old firmware.
I guess most people don't care about which driver is included in ROMS as new ROMS are always coming out or being improved upon and with all of the details and specs being listed, driver versions are never mentioned. Is the v84 driver all that we can hope for, nothing newer? I've flashed countless ROMS an never saw anything newer.
Driver versions do matter, I wish they would be listed somewhere in the ROM description.
Somebody has to develop these drivers. You can't just go to a website a download them like nvidia drivers.
And as far as I know, Qualcomm only release the source code for the chips, leaving the development up to whoever is interested.
Is there not an updated driver newer than v84 that already works with the S4? The S4 has gotten official Lolipop OS upgrades, isn't there better drivers already made to work?
Surely Marshmellow OSs have better drivers. Are those drivers not able to be used on the S4? I understand someone has to do the work, but every other aspect of custom roms are being made to function, are GPU drivers just being overlooked as not being important enough to spend time on?
I don't know how this works. But if they could I think they would.
Obviously, Qualcomm has to update the drivers, as it's their chip. So maybe they dropped support for the Snapdragon 600 chips. I don't know.
Tommy807 said:
Is there not an updated driver newer than v84 that already works with the S4? The S4 has gotten official Lolipop OS upgrades, isn't there better drivers already made to work?
Surely Marshmellow OSs have better drivers. Are those drivers not able to be used on the S4? I understand someone has to do the work, but every other aspect of custom roms are being made to function, are GPU drivers just being overlooked as not being important enough to spend time on?
Click to expand...
Click to collapse
drivers from another GPU wouldn't be any use to us.
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.