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.
Related
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...
Hi,
I currently use a custom TW based firmware for my 910F based upon POF2 firmware. I'm a software developer and developer an app that uses OpenGL ES 3.1. Now I have a problem which seems to be connected to the old version of the Qualcomm Adreno 420 drivers that came with the ROM. Every shader I want to compile fails with the error: "Built-In invariance mismatch". Those shaders worked on the same phone with all 4.4.x based ROMs before. So I now wondered if I can use Adreno 420 drivers for the Nexus 6 (Uses Adreno 420 as well) downloaded from the Qualcomm developer page (drivers from August 2015) and just flash the file to my phone? I already looked inside my system folder and the files on my phone are the same just much smaller and older versions. I'm a little scared if a break everything if i try this. So maybe someone with a little experience with Android drivers for GPUs can tell me if this will be possible?
Best Regards,
CommanderXXL
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 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