Hmm, i wonder, is google camera port need snapdragon? or it could work on mtk?
It not works on MTK, but on some devices with MTK it works, for example, like realme and others, we need to wait until developers make a build for our device
Related
Hey guys,swimming in the digital web sea I found that Motorola uses Qualcomm Propretary Tools to build optimized DALVIK and BIONIC libraries,I found this here http://forum.xda-developers.com/oneplus-one/development/mod-optimized-dalvik-binaries-t2932417,who who made the this post ported them from Motorola Moto X (Device with the same Soc of OnePlus One) because these optimized libraries by Motorola and Qualcomm can be ported between devices with the same Soc (ex:Motorola Moto X-OnePlus One;Motorola Moto G-} Xiaomi Redmi 1S) yeaaah I wrote Xiaomi Redmi 1S(our beloved Xiaomi Redmi 1S) and I found a similar post in the Moto G thread(here http://forum.xda-developers.com/showthread.php?t=2756227) so there is a possibility of porting.So,I'm asking to all the BIGGEST developers to port these libraries,now the two questions you are thinking about are:
1)What do this libraries do?I don't want to be very technical,so I'll be very focused :They give more PERFORMANCE and BATTERY LIFE,and I can guarantee (with all the other user of these libraries on other devices) that it's true because I'm trying the on my dad's OnePlus One and the affect the device in a so positive way
2)Who will port them?We'll see who will
It's compiled proprietary blobs. They can't be ported. They just working or not working.
Actually there is no reason why it shouldn't work on CM11 based ROMs.
UPD: info from second link is actually quite interesting; maybe our dev's would try to do this (if they not already using it ofc, lol).
not sure about Dalvik as devs are moved to develop lollipop rom, so maybe ART binaries could be help...
I am trying to understand more about android to be able to get MIUI running on my bullhead device.
How is google stopping us from running Lollipop on it and can it be bypassed?
Is it possible to port a for example SD 810 rom to our SD 808? I understand it might not be the easiest but I can't find any information at all about cross chipset porting, only for MTK chipsets.
I know that this is probably not any easy task and it would probably just be easier to buy a MI device, but I got nothing to do on my vacation so thought I would try and educate myself some.
Superbia said:
I am trying to understand more about android to be able to get MIUI running on my bullhead device.
How is google stopping us from running Lollipop on it and can it be bypassed?
Is it possible to port a for example SD 810 rom to our SD 808? I understand it might not be the easiest but I can't find any information at all about cross chipset porting, only for MTK chipsets.
I know that this is probably not any easy task and it would probably just be easier to buy a MI device, but I got nothing to do on my vacation so thought I would try and educate myself some.
Click to expand...
Click to collapse
Google is stopping us by never providing firmware for lollipop. Why would they develop older firmware for a new device. If you're trying to port a lollipop rom it won't work since there is no lollipop base for the 5x.
Sent from my Nexus 9 using XDA-Developers mobile app
jd1639 said:
Google is stopping us by never providing firmware for lollipop. Why would they develop older firmware for a new device. If you're trying to port a lollipop rom it won't work since there is no lollipop base for the 5x.
Sent from my Nexus 9 using XDA-Developers mobile app
Click to expand...
Click to collapse
That's fair enough. I guess even if two devices has seemingly identical hardware there are still slight differences. Any idea if it's possible to cross port between Snapdragon chipsets? I only know computers I'm afraid and there it doesn't matter much if it's amd, intel xeon or i3 as long as the architecture is the same.
Is the A3, A5, A7 series bad for dev of ROMs and new mods on sites like this? I saw someone that wrote something about that. They mentioned it was due to the Exynos chipsets. Could have been the 2015 or 2016-series also.
No, it is misunderstanding in the early days it was like that but times changes.
Look at the s7 exynos full of dev support.
It is a new phone, give it time.
It is always like that.
Samsung release even the open source files maby it is not complete but u could port cm 13 or lineage os by yourself to the device and get things working.
Or build a kernel etc.
Twrp same it can get official but we get someone who is mainly focus on dev twrp for our devices.
I dont have much time and i will focus mainly on the stock os.
I have galaxy SM -A500f
Is thr any working custom recoveries available ??
sethukrishnan said:
I have galaxy SM -A500f
Is thr any working custom recoveries available ??
Click to expand...
Click to collapse
This is the forum of the galaxy a 2017 series.
U need to go to the normal a series thread.
Has anyone tried out the android P development preview GSI yet?
As long i read the p one was a semi / port and Qualcomm based one, dunno if it'l boot on our kirin chip
It's for snapdragon... no guarantee it will even boot or work well on Kirin chipsets.
Has there, or is there going to be a fix/patch that we can flash that will make NFC work on huawei devices for PIE GSI's?
I'm wondering if it would be possible to copy over NFC libraries from a working oreo GSI into their respective locations on a pie GSI if there is no fix, just need to find out what libraries are actually for NFC.
There's a magisk module that works.
i know theres a magisk module for kirin 655 devices, but im not sure if it will work on 960/970 devices, i guess i could try
ambitiousButRubbish said:
i know theres a magisk module for kirin 655 devices, but im not sure if it will work on 960/970 devices, i guess i could try
Click to expand...
Click to collapse
It works
HugoClaw said:
It works
Click to expand...
Click to collapse
i hope you are correct