Can i possibly know why devices owning the 6795 like the rn3 won't upgrade to CM13 ? What do the devs require so much that they can't port CM13 to the mediatek version ? I'm afraid i'm not aware of this version so much, but does it properly need android M in order to run ?
Mediatek phones are generally far more difficult to develop for because they don't like to release kernel sources and they are built for generic phones so they don't work as well
Mediatek development most currently are porting roms that is the same base as the original. If it came out with 5.0.2 then the max version for a custom rom is probably 5.1.1 and its harder to port higher android OS without any sources.
Oh, i see.. So mostly is because of the phone devs that won't release certain codes and whatever you need in order to develop the rom, right ?
Yeah blame the chipset manufacturer.
I'm no developer, but what about this info?
https://github.com/rmtew/MediaTek-HelioX10-Kernel
Related
Does anyone know anything about this tablet? My wife just got one and wanted to see if porting KitKat was possible on this device?
It comes with Android 4.2.
dsreyes1014 said:
Does anyone know anything about this tablet? My wife just got one and wanted to see if porting KitKat was possible on this device?
It comes with Android 4.2.
Click to expand...
Click to collapse
The tablet appears to be just another no-name brand tablet , the Google in the branding name is misleading as the device has nothing to do with Google (It's not at all an official Google branded product) other then it runs Android. As far as porting KitKat is concerned, it is possible but it will unforutnately be difficult without an official kernel source from the manufacture or your own knowledge of compiling AOSP KitKat or say Cyanogenmod 11 for an unsupported device.
The tablet appears to be just another no-name brand tablet , the Google in the branding name is misleading as the device has nothing to do with Google (It's not at all an official Google branded product) other then it runs Android. As far as porting KitKat is concerned, it is possible but it will unforutnately be difficult without an official kernel source from the manufacture or your own knowledge of compiling AOSP KitKat or say Cyanogenmod 11 for an unsupported device.
Click to expand...
Click to collapse
If I was able to obtain kernel source would it be possible for you or anyone to build KitKat for it? How do I obtain kernel source?
dsreyes1014 said:
If I was able to obtain kernel source would it be possible for you or anyone to build KitKat for it? How do I obtain kernel source?
Click to expand...
Click to collapse
In the case of your device you would have to contact the manufacture and ask them to provide you with the kernel source code, and even then if they did you would still have to undergo the process of extracting the files for your device and fixing any broken features that would likely arise during the KitKat building process.
Hey! I'd love to know more about kernels, but I can't find that info.
What are the differences between Android versions in Kernels? How hard would it be to port Android on some device that already has a linux kernel? (Maybe something simmilar to what this guy did, just with more info on the process) What about a device that already has an Android kernel, just for other android version?
Would it be possible to port an older android version to Nexus 5x? (I.E. Lollipop, maybe even KitKat)
EDIT:
Okay, so I know that I would have to port kernel modules from devices with same chipsets, but I don't really get it.
Hello!
I'd like to build my own rom from AOSP 8.0 official branch. I'm looking for some kind of guide but couldn't find any So, let's say I've got android source code and files from other custom rom that makes camera work. What have I to do to make my rom now? How can I build it and be sure that everything will work. Generally my target is to install android 8 on my Leeco le 2 x620 device with Mediatek chip
Any help is appreciated ^v^
LEGOL2 said:
Hello!
I'd like to build my own rom from AOSP 8.0 official branch. I'm looking for some kind of guide but couldn't find any So, let's say I've got android source code and files from other custom rom that makes camera work. What have I to do to make my rom now? How can I build it and be sure that everything will work. Generally my target is to install android 8 on my Leeco le 2 x620 device with Mediatek chip
Any help is appreciated ^v^
Click to expand...
Click to collapse
"I'd like to build my own rom from AOSP"
So you mean an aftermarket os like lineageos or carbonrom or do you mean that you take the aosp repo and compile aosp for your device? You can look in source.android.com
"source code and files from other custom rom that makes camera work"
Is that an already compiled rom? Because you won't get source code out of that
"How can I build it and be sure that everything will work"
Ya don't. Nothing can ever be 100% bugfree, it can either be from your device tree's source code, or the aosp code itself.
Generally, if there is a caf tree for your device, it's going to be 3x as hard to create an aosp tree.
It is going to be 100000x as hard to create an aosp tree that is for a newly released, new hardware requirement operating system.
Wanna know the topping of the cake? Mediatek is notorious when it comes to releasing the source (in fact, it has become a meme in the Mediatek users world) but don't let that stop you son.
You can try, but don't give up just because it won't compile the first couple of hundred times. The errors when compiling should give you a great start
Good luck.
ramiabouzahra said:
"I'd like to build my own rom from AOSP"
So you mean an aftermarket os like lineageos or carbonrom or do you mean that you take the aosp repo and compile aosp for your device? You can look in source.android.com
"source code and files from other custom rom that makes camera work"
Is that an already compiled rom? Because you won't get source code out of that
"How can I build it and be sure that everything will work"
Ya don't. Nothing can ever be 100% bugfree, it can either be from your device tree's source code, or the aosp code itself.
Generally, if there is a caf tree for your device, it's going to be 3x as hard to create an aosp tree.
It is going to be 100000x as hard to create an aosp tree that is for a newly released, new hardware requirement operating system.
Wanna know the topping of the cake? Mediatek is notorious when it comes to releasing the source (in fact, it has become a meme in the Mediatek users world) but don't let that stop you son.
You can try, but don't give up just because it won't compile the first couple of hundred times. The errors when compiling should give you a great start
Good luck.
Click to expand...
Click to collapse
Oh God, how am I meant to do this ;0 There is Lineage 14.1 project on my device. I really want to have android 8 on my phone. Thank you for all the advice.
Yes im trying the same andere without any succes so far.
Im also trying to port from a different device ROM to the stock ROM what im running now.
The chip sets are the same but the Android versions not.
It would be really Nice if some mtk ROM developer find some time in his busy life to create a ROM for our phone.
Or a guide to compile/port Android o tot oud phone.
Hello everyone.
Im new here.
I just want to ask something.
When porting roms can my base ROM and my port ROM have different android version?
Looking forward to having responses
P/s: sorry for bad engrisk )
XdaNeko said:
Hello everyone.
Im new here.
I just want to ask something.
When porting roms can my base ROM and my port ROM have different android version?
Looking forward to having responses
P/s: sorry for bad engrisk )
Click to expand...
Click to collapse
It has been a looong time since I knew about those things but if I remember your base ROM should have that same Android version as your port ROM.
And if you want an advice, please consider building a ROM from source. Troubleshooting is hell with ported ROMs. Building ROM is scary because it has commands that you don't know yet, but it's way more easy than porting. Trust me.
Here is a guide on how to build ROM from source :
https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
@XdaNeko
It's NOT the version of Android what does matter. If that would be the case then an upgrade via OTA never would be possible.
A Stock ROM always at 100% matches phone's hardware ( CPU, GPU, RAM, storage memory, etc.pp ) - it's built by OEM's / Carrier's R&D department, the guys who know best of.
Whereas a Custom ROM necessarily does NOT because it gets built by 3rd-party companies/programmers associations - who think they can do it better, but don't always have the specific Android device at hand.
Hi everyone,
After a few hiccups, I successfully rooted my Leagoo T5c, thanks to the excellent tutorial posted here. The phone works fine, thank you, but now, I'd like to know how to proceed to, say, upgrade the phone from its current Android version (7.0) to a more recent version.
Where to start?
Since this phone has a Spreadtrum/Unisoc SC9853i SoC (Intel-based), I suppose the custom ROMs and upgrade possibilities are few and far between, but I'd like to give it a shot.
I'm open to ideas, tips, tricks, voodoo moves and Santeria incantations, but I'm still a noob when it comes to Android, so please, be patient, and methodical... :good:
@UglyStuff
If you can unlock phone's boot-loader then you should be able to flash any Custom Recovery and/or Custom ROM that's suitable to 100% to phone's CPU-architecture. Who is the supplier of phone's SoC isn't of any interest at all.
Hi,
Thing is, as I said, I'm a noob when it comes to Android, so I don't want to brick my phone by trying to make it ingest a ROM that's not suitable for it.
If my phone came with a MediaTek or Qualcomm SoC, I wouldn't worry, because there are plenty of ROMs out there, custom or not, to play with, but this Spreadtrum/Unisoc SoC is a thing of its own.
It's based on Intel's Airmont architecture, and few phones or tablets use it, at least this specific version (SC9853i). Maybe I just don't understand too well how a ROM is built.
UglyStuff said:
Hi,
Thing is, as I said, I'm a noob when it comes to Android, so I don't want to brick my phone by trying to make it ingest a ROM that's not suitable for it.
If my phone came with a MediaTek or Qualcomm SoC, I wouldn't worry, because there are plenty of ROMs out there, custom or not, to play with, but this Spreadtrum/Unisoc SoC is a thing of its own.
It's based on Intel's Airmont architecture, and few phones or tablets use it, at least this specific version (SC9853i). Maybe I just don't understand too well how a ROM is built.
Click to expand...
Click to collapse
For example, I found this article where they explain how to flash LineageOS 17 (based on Android 10) on a Panasonic Eluga Ray 800 that uses the same SoC as my Leagoo T5c.
The thing is, I don't know if this is transposable to my device, though the two share the same SoC. As I said earlier, I don't want to permanently brick my phone...
@UglyStuff
The mentioned Intel Airmount SoC's instruction set architecture is x86_64 , the also mentioned Intel Spreadtrum SC9853i SoC's instruction set architecture is x86_64, too. Hence in order to upgrade yor phone's Android you need a Custom ROM compiled for x86_64 architecture. GIYF ...
OK, but since this Panasonic and my Leagoo share the same SoC, they also share the same x64 instruction set, so do I get it right if I say that the custom ROM built for the Panasonic would fit on my Leagoo, or am I missing something?
In theory it should.
OK, I guess I'll have to chance it, and use recovery in case things so south. My phone isn't compatible with Treble, according to this app. Does it mean anything in terms of installing one of the generic system images found here or not?