Anyone know if this is possible yet? Any idea what special steps need to be taken to make a port like this work? I have a Nexus 6 which is 32 bit and I am trying to port MIUI lollipop. All of the lollipop roms for MIUI that I have seen are 64 bit. Any help with this would be appreciated.
In theory you can run a 32 bit ROM on a 64 bit device but not vice versa. In short, it's not possible to run a 64 bit ROM on a 32 bit device.
thanks. that is what I was afraid of
MIUI 7 runs on the Nexus 4 and 5 as well as many other popular phones, so surely not 64 bit exclusive. http://www.droidviews.com/port-miui-7-rom-available-69-devices/
No, but teorically you could just if you port libs from 64 to 32 bit.
If you use a 64bit app on a 32bit it will FC.
You must use an original 32bit base and port apps from the 64bit ROM.
That's why exists ports from Note 5 to Note 3, from S6 to S4 eccetera
64bit kernel sources for Redmi2/2A/Prime
SHARING 64BIT WORKING KERNEL SOURCES FOR OUR DEVICE
WE ALL KNOW THAT OUR DEVICE HAVE A 64BIT CPU, BUT IT COULDN'T USE THAT 64BIT POTENTIAL BECAUSE OUR DEVICE WAS LAUNCHED WITH KK WHICH DO NOT SUPPORTS x64, BUT LATER XIAOMI RELEASED L FOR THE DEVICE BRINGING SUPPORT FOR MANY FEATURES LIKE VOLTE.
BUT ONE OF OUR DEVELOPER WAS ABLE TO CREATE 64BIT KERNEL SOURCES FOR OUR DEVICE. NAME "SEIRYU-2I"
HE ALSO CREATED WORKING MIUI8 64BIT BASED FOR OUR DEVICE. [url]https://goo.gl/2l1oqZ[/URL]
FEATURES: ARM64 BASED (PHEEWW)
SENSORS WORKS FLAWLESSLY
TOTALLY SUITABLE FOR VR AND DAYDREAM
BATTERY LIFE IS NOT COMPROMISED
AVAILABLE FOR BOTH MIUI AND CM (SEPERATE BRANCHES)
HAVEN'T FOUND ANY BUGS TILL NOW
NO PROBLEMS WITH VOLTE
SURPRISINGLY FAST
WE HAVE 64BIT KERNEL NOW!! SO, I WOULD LIKE TO INVITE ALL DEVELOPERS OUT THERE TO START WORKING ON 64 BIT ROMS LIKE, LIKE TESLA, DIRTY UNICORNS, AICP, CM14, ZYPHER AND DEVELOPERS OF OTHER GREAT ROMS OUT THERE AND KERNEL DEVELOPER LIKE JERRICA, LATTE AUTMN AND OTHERS.
[url]https://goo.gl/7AT5fS[/URL]
"THE SCORES HAVE BEEN UPDATED AS PROOF, GO GUYS TEST IT OUT YOURSELF"
AND PLEASE LET ME KNOW IF I AM MISSING SOMETHING.
SORRY FOR MY BAD ENGLISH and thank you :silly:
Let's go to the future. Thanks anyway.
Dyt199412syam said:
Let's go to the future. Thanks anyway.
Click to expand...
Click to collapse
lets see if the developers will work on this....
and if you can do please ping developers about this
fix the link dude
solomonR15 said:
fix the link dude
Click to expand...
Click to collapse
Fixed bro :highfive: :good:
Thanks for sharing :good:
Hope this can get some attention from the rom devs...
https://github.com/seiryu-2i/android_kernel_xiaomi_msm8916
Slight corrections required in the post
These sources are not x64. They are ARM64
x64 refers to 64 bit Intel CISC Chips like Atom whereas ARM64 Refers to 64 bit ARM RISC chips like Qualcomm SnapDragon and MediaTek Helios
Our Redmi 2 comes with Qualcomm ARM64 chipset ( albeit running a 32 bit OS) not x64 chipset
so make the necessary corrections
taalojarvi said:
slight corrections required in the post
these sources are not x64. They are arm64
x64 refers to 64 bit intel cisc chips like atom whereas arm64 refers to 64 bit arm risc chips like qualcomm snapdragon and mediatek helios
our redmi 2 comes with qualcomm arm64 chipset ( albeit running a 32 bit os) not x64 chipset
so make the necessary corrections
Click to expand...
Click to collapse
corrections made brother ... Btw thank you
didhiy said:
Thanks for sharing :good:
Hope this can get some attention from the rom devs...
https://github.com/seiryu-2i/android_kernel_xiaomi_msm8916
Click to expand...
Click to collapse
:fingers-crossed::good::highfive:
Well thank you for posting this thread
If anyone can make this kernel better then it would be good, as I only have limited free time to see the world & don't have any PC or laptop too to work on it :crying:
Jus a lil info, well maybe not useful though, if anyone wish to port 64bit custrom like CM, then you can always pick any existing device tree for our device. Remove "FORCE_32_BIT=true" from BoardConfig.mk and put "$(call inherit-product, $(SRC_TARGET_DIR)/product/core_64_bit.mk)" on top of "$(call inherit-product, $(SRC_TARGET_DIR)/product/full_base_telephony.mk)" line inside cm.mk or device.mk. Edit any other mk files to match your needs and edit some C/C++ sources inside your device tree to match 64bit target (mostly are only type conversions).
And for blobs, you can extract it from my rom port or just use ido (redmi 3) vendor blobs (name/rename it into suitable vendor and target based on your device tree), why? It's because, it came from the same source tree as our device have, so that means it's compatible (just remove the fingerprint we don't need it). And the rest, try to find it by yourself and fix any build error by your hand (in my experience all error only comes from mismatch config & any source code inside the device tree).
cheers
seiryu
seiryu.2i said:
Well thank you for posting this thread
If anyone can make this kernel better then it would be good, as I only have limited free time to see the world & don't have any PC or laptop too to work on it :crying:
Jus a lil info, well maybe not useful though, if anyone wish to port 64bit custrom like CM, then you can always pick any existing device tree for our device. Remove "FORCE_32_BIT=true" from BoardConfig.mk and put "$(call inherit-product, $(SRC_TARGET_DIR)/product/core_64_bit.mk)" on top of "$(call inherit-product, $(SRC_TARGET_DIR)/product/full_base_telephony.mk)" line inside cm.mk or device.mk. Edit any other mk files to match your needs and edit some C/C++ sources inside your device tree to match 64bit target (mostly are only type conversions).
And for blobs, you can extract it from my rom port or just use ido (redmi 3) vendor blobs (name/rename it into suitable vendor and target based on your device tree), why? It's because, it came from the same source tree as our device have, so that means it's compatible (just remove the fingerprint we don't need it). And the rest, try to find it by yourself and fix any build error by your hand (in my experience all error only comes from mismatch config & any source code inside the device tree).
cheers
seiryu
Click to expand...
Click to collapse
Thanks for your great works :good:
seiryu.2i said:
well thank you for posting this thread :d
if anyone can make this kernel better then it would be good, as i only have limited free time to see the world & don't have any pc or laptop too to work on it :crying:
Jus a lil info, well maybe not useful though, if anyone wish to port 64bit custrom like cm, then you can always pick any existing device tree for our device. Remove "force_32_bit=true" from boardconfig.mk and put "$(call inherit-product, $(src_target_dir)/product/core_64_bit.mk)" on top of "$(call inherit-product, $(src_target_dir)/product/full_base_telephony.mk)" line inside cm.mk or device.mk. Edit any other mk files to match your needs and edit some c/c++ sources inside your device tree to match 64bit target (mostly are only type conversions).
And for blobs, you can extract it from my rom port or just use ido (redmi 3) vendor blobs (name/rename it into suitable vendor and target based on your device tree), why? It's because, it came from the same source tree as our device have, so that means it's compatible (just remove the fingerprint we don't need it). And the rest, try to find it by yourself and fix any build error by your hand (in my experience all error only comes from mismatch config & any source code inside the device tree).
Cheers
seiryu
Click to expand...
Click to collapse
lets hope .... If we could see cm 14 based on it
....
Is the cm branch in seiryu's repo good to go?
iamsubhranil said:
Is the cm branch in seiryu's repo good to go?
Click to expand...
Click to collapse
yes... it is working flawlessly . it is ported from its brother device (redmi 3) with the required changes made . and 64 bit based miui gave me 29850 score on antutu. i hope further development will start based on 64 bit architechture.
:fingers-crossed::laugh:
abhishek 9650 said:
yes... it is working flawlessly . it is ported from its brother device (redmi 3) with the required changes made . and 64 bit based miui gave me 29850 score on antutu. i hope further development will start based on 64 bit architechture.
:fingers-crossed::laugh:
Click to expand...
Click to collapse
What? how can you get this performance? I only got 20876
abhishek 9650 said:
yes... it is working flawlessly . it is ported from its brother device (redmi 3) with the required changes made . and 64 bit based miui gave me 29850 score on antutu. i hope further development will start based on 64 bit architechture.
:fingers-crossed::laugh:
Click to expand...
Click to collapse
Ya here's the point. Using just a 64bit kernel won't do anything much. The ROM has to be 64bit too.
iamsubhranil said:
ya here's the point. Using just a 64bit kernel won't do anything much. The rom has to be 64bit too.
Click to expand...
Click to collapse
yeah truly said ... But..... As the kernel got ported ... Rom can also be ported from its brother device(redmi 3) . There are lot of custom roms available on this forum for redmi 3 like our device redmi 2. They can be easily ported if done by the right person.
abhishek 9650 said:
yeah truly said ... But..... As the kernel got ported ... Rom can also be ported from its brother device(redmi 3) . There are lot of custom roms available on this forum for redmi 3 like our device redmi 2. They can be easily ported if done by the right person.
Click to expand...
Click to collapse
Hey hey one thing. SD410 is armv7 and that means it is not a true 64bit processor. SD430 in redmi3 on the other hand is a armv8 processor and that's why they are using all 64bit things. Then, why bother?
iamsubhranil said:
Hey hey one thing. SD410 is armv7 and that means it is not a true 64bit processor. SD430 in redmi3 on the other hand is a armv8 processor and that's why they are using all 64bit things. Then, why bother?
Click to expand...
Click to collapse
I guess the kernel sources has been ported from Redmi 3 (IDO) which has SD 616 and not SD 430.
As the title says, will the next android updates work on 32 bits devices or not? Custom roms support? I think gapps will only be 64bits for android O Am I wrong? I'm looking for a new cellphone should I go with a 64 bit for futureproof I wanted the nexus 6 but its 32bits...What should I do?
Pierre2324 said:
As the title says, will the next android updates work on 32 bits devices or not? Custom roms support? I think gapps will only be 64bits for android O Am I wrong? I'm looking for a new cellphone should I go with a 64 bit for futureproof I wanted the nexus 6 but its 32bits...What should I do?
Click to expand...
Click to collapse
I don't think that at all, new phones will include 32 and 64 bits devices, new android O should be released as open source and can be ported to any of them, also gapps will remain supporting of 32 and 64 bits devices.
MigoMujahid said:
I don't think that at all, new phones will include 32 and 64 bits devices, new android O should be released as open source and can be ported to any of them, also gapps will remain supporting of 32 and 64 bits devices.
Click to expand...
Click to collapse
Are you sure some people say that android O and gapps are only for 64bits based on the dev preview 1
Hello I am Jimmy and I am starting on ROM development for mobile and PC. I have a few doubts regarding that.
1> Android-x86 Oreo is the latest build on their website, But roms like Bliss, they ported Pie on PC. How to do that? I mean how to get Android-x86 pie?
2> How much average time does it take to compile the source of Android(both x86 and arm64)? [Specs for consideration: Intel Core i7-8750H 2.2 Ghz 6 cores, 16 GB RAM, Ubuntu 18.04 ]
3> What IDE/Development softwares should I use for modifying the original source code that is? Android Studio? Netbeans? Notepad++? Or what??
And a question not regarding development:
I have a device lying around my drawer. My bro used to use it until he bought a new one. Its LAVA Z60 which is based on MTK MT6737 chipset. I researched but found out that there are very few MTK devices with custom roms. Is LAVA Z60 one of em? And if so, where to get the Device Tree, Vendor, Kernel etc.. for the device? Also, note that MTK Droid tools does identify the device, but I cant create scatter file cuz there is just one item on the list with location and every other thing as 0.
Soo.. yeah thats all. Please help me if you can. Thanks in advance.
Help
First of all install this app:
https://play.google.com/store/apps/details?id=tk.hack5.treblecheck
This app show all the details about your phone.
According to this app my device is ARM32 but uses a 64-bit binder and my device uses an A/B operating system. [SM-A105F/DS]
So I just want to download custom ROM/GSI of ARM 32, 64-bit binder with A/B partition.
Lineage os 17 treble GSI:
https://sourceforge.net/projects/andyyan-gsi/files/lineage-17.x/
This link also contains information about which ROM you should download that supports your device.
Feel free to ask!!
Hope you all find it helpful?
How bug free is linage gsi on galaxy A10? And does gcam work?
Albert pallam said:
First of all install this app:
https://play.google.com/store/apps/details?id=tk.hack5.treblecheck
This app show all the details about your phone.
According to this app my device is ARM32 but uses a 64-bit binder and my device uses an A/B operating system. [SM-A105F/DS]
So I just want to download custom ROM/GSI of ARM 32, 64-bit binder with A/B partition.
Lineage os 17 treble GSI:
https://sourceforge.net/projects/andyyan-gsi/files/lineage-17.x/
This link also contains information about which ROM you should download that supports your device.
Feel free to ask!!
Hope you all find it helpful?
Click to expand...
Click to collapse
Are gapps working?And can you download games with obb from the play store?
parthibratan said:
Are gapps working?And can you download games with obb from the play store?
Click to expand...
Click to collapse
the only way to make Gcam work is developing a 64Bits Vendor and installing a ARM64 GSI
but... apparently nobody is interested in programming for our device
rockeirodohs said:
the only way to make Gcam work is developing a 64Bits Vendor and installing a ARM64 GSI
but... apparently nobody is interested in programming for our device
Click to expand...
Click to collapse
No not gcam bro...I mean google apps zip file...
Does flashing it work on lineage 17?
Albert pallam said:
First of all install this app:
https://play.google.com/store/apps/details?id=tk.hack5.treblecheck
This app show all the details about your phone.
According to this app my device is ARM32 but uses a 64-bit binder and my device uses an A/B operating system. [SM-A105F/DS]
So I just want to download custom ROM/GSI of ARM 32, 64-bit binder with A/B partition.
Lineage os 17 treble GSI:
https://sourceforge.net/projects/andyyan-gsi/files/lineage-17.x/
This link also contains information about which ROM you should download that supports your device.
Feel free to ask!!
Hope you all find it helpful?
Click to expand...
Click to collapse
I also have an 10 and want to flash a custom recovery. can you please send me an exact like of where i can download the custom recovery for my device which is SM-A107M/DS . thanks for considering if you did