I think that a porting ss possible but the windows 8 preview platform releas today is not for ARM acritecture right?
As soon as possibile hope that some devel will be a windows 8 port for folio 100.
let me know what U thinking.
thanks.
Yes, I heared for it but not arm version . I saw a post that say that windows 8 arm version will be for TEGRA 2(and some others arm processors)!!!
Hmmm, Windows is ugly in my opinion (sorry, I'm a Linux fan)... But, anyway, I don't think it's good for Folio as the RAM requirements won't fit... Heard it need at least 1Gb of RAM
That and Windows 8 won't be open source. That mean you can't do any porting work(with system you can do something but with kernel nothing)
I see that Ubuntu is being developed and ported to the nexus 9 and I was wondering if any device could start work with Linux Mint 17 or 17.1 not earlier versions... instead as it is a much better os than Ubuntu. It would be amazing if it was to happen... Since after all nvidia has made the tegra drivers more open now.
Also
MAKE IT EAST TO UPDATE RELEASES ROFL
Thanks
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.
I have Samsung A10.It has 64 bit chipset though it it is running on 32 bit android.Can i get this mobile to use 64 bit android by flashing google gsi for arm64.
No, it won't run arm64 gsi
Why ?It has a 64 bit chipset which is needed to run arm 64
Abdul Hadi01 said:
Why ?It has a 64 bit chipset which is needed to run arm 64
Click to expand...
Click to collapse
But it doesn't have the necessary libs inside the device to run 64bit GSI. Samsung removed them and only left 32bit available.
Hello, I would like someone to please recommend me a custom rom to install on my samsung A10s (a107m). I have not been able to find support information on official pages such as Lineage Os. I have everything soon, download FWUL and TWRP together with Magisk, I just need a compatible rom. Thank you in advance and I hope someone can help me ... or I better change my device
I had great luck with some of these. Haven't tried them all.
https://t.me/s/eureka_roms