MTK6575 Based Devices Cyanogenmod - General Topics

Hi Guys I Want Someone Who Can Help Me To Build CM For MTK6575 .
I Have LG Optimus L4 II E440 Its MTK6575 Based Device And I Have Source Code .
I Think It Will Work On Other Devices .

Even if you have the source code for that device, you can't just build generically for anything with that processor as even if just one part of the device is changes that part would probably cease to function. Also when it comes to building something like that I'll see what I can do once I have a fully functional computer but the source is like 40 GB so it would be a big investment already just to download it. Which version of cm?

dreamwave said:
Even if you have the source code for that device, you can't just build generically for anything with that processor as even if just one part of the device is changes that part would probably cease to function. Also when it comes to building something like that I'll see what I can do once I have a fully functional computer but the source is like 40 GB so it would be a big investment already just to download it. Which version of cm?
Click to expand...
Click to collapse
I Think CM 10.1/10.2 Or CM 11 !
I Have Installed Lubuntu 12.04 And I Will Start Programing From There But I Dont Know From Where I Can Download The CM Build !

vikole said:
I Think CM 10.1/10.2 Or CM 11 !
I Have Installed Lubuntu 12.04 And I Will Start Programing From There But I Dont Know From Where I Can Download The CM Build !
Click to expand...
Click to collapse
I made some 1.5 based rom at one point for my g1 but I remember like...none of it. Once you read up on building android you should be fine. I'll just warn you you will be working with BIG data, probably around 40gb to download.

dreamwave said:
I made some 1.5 based rom at one point for my g1 but I remember like...none of it. Once you read up on building android you should be fine. I'll just warn you you will be working with BIG data, probably around 40gb to download.
Click to expand...
Click to collapse
Can You Help Me ??:highfive::highfive::highfive:

vikole said:
Can You Help Me ??:highfive::highfive::highfive:
Click to expand...
Click to collapse
I'll have to see. I have hard drive issues so I couldn't do it myself but I think I can guide you to a few good guides. There's a really good xdauniversity one I saw at one point I'll try to find.

Related

[Q] What device tree I can use for Qumo Quest phone

Hi there!
I want to compile CM 10.1 for my phone, but stucked with device tree and i don't know what tree to choose for this.
Phone mentioned in the subject is Qumo brending of chinese i9220 PAD 5" MT6575 (e1809c_v75) Android 4.0.3
Great thanks if anyone can help.
PS. Sorry for my English.
rippak said:
Hi there!
I want to compile CM 10.1 for my phone, but stucked with device tree and i don't know what tree to choose for this.
Phone mentioned in the subject is Qumo brending of chinese i9220 PAD 5" MT6575 (e1809c_v75) Android 4.0.3
Great thanks if anyone can help.
PS. Sorry for my English.
Click to expand...
Click to collapse
I dont think there is one for that as that is not an official version of Android. Very few China based Android phones are supported by AOSP. You may have to start it yourself if you want it. The first thing you will need to do is have the OEM post the kernel source code for the device. This will be your biggest challenge. As most China OEM dont respect the GPL laws
zelendel said:
I dont think there is one for that as that is not an official version of Android. Very few China based Android phones are supported by AOSP. You may have to start it yourself if you want it. The first thing you will need to do is have the OEM post the kernel source code for the device. This will be your biggest challenge. As most China OEM dont respect the GPL laws
Click to expand...
Click to collapse
Ok
What if there is no source of kernel? Can I use compiled kernel (3.0.13) from current firmware (4.0.3) or this is impossible?
rippak said:
Ok
What if there is no source of kernel? Can I use compiled kernel (3.0.13) from current firmware (4.0.3) or this is impossible?
Click to expand...
Click to collapse
Without kernel source your kinda out of luck. No that kernel will not work on AOSP as that 4.0.3 is not an official android version. It is a hacked together version. Your best bet would be to sell it and get something that is not a knock off.
zelendel said:
Without kernel source your kinda out of luck. No that kernel will not work on AOSP as that 4.0.3 is not an official android version. It is a hacked together version. Your best bet would be to sell it and get something that is not a knock off.
Click to expand...
Click to collapse
Just for fun: wrote to "developer" for sources.
rippak said:
Just for fun: wrote to "developer" for sources.
Click to expand...
Click to collapse
Got to write to the OEM. Only they will be able to release the kernel source. Good luck. Dont hold on to hope though. They are not forced to post kernel source like everyone else.
zelendel said:
Got to write to the OEM. Only they will be able to release the kernel source. Good luck. Dont hold on to hope though. They are not forced to post kernel source like everyone else.
Click to expand...
Click to collapse
Don't you know is it real to compile with another kernel for same CPU MT6575?
Found some links to kernel sources for other phones - seems to be working for different devices.

What is necessary if I want to compile a ROM?

Hi guys. 2 months ago I've came into Android World deeper than before and now I'm very fascinated. I downloaded linux, all the necessary files to compile a rom but I still don't understand some things.
My device is Redmi Note 2 and I use stock MIUI 7. As we all know mtk and/or xiaomi haven't released kernel sources (6795) so developers have to think hard how to make a rom. And there are my questions. Does kernel source is really necessary? What if I compile rom successfully and then port boot.img from stock? Will it work? However developers made some roms based on LP for this device. And I read that I need device tree and vendor, which doesnt exist for redmi note 2 or I still can't use github.
Second question which I have is: does compiling for 64 bit CPU differ from compiling for 32 bit CPU (like 6592)? If yes, could you give me some tips?
Ohh I think you can understand what I wrote
Thanks in advance and please dont blame me for silly questions
If you are looking to compile roms then you picked the wrong device to do it. They are the worst with kernel source. You can't completely compile a rom but use a patch system that does most of the work.
Yes it is different. There are some Tuts around but they are few as most don't use that type of chip.
If you really want to learn to develop then I would suggest getting a different device. One that respects the copyright and gpl laws.
zelendel said:
If you are looking to compile roms then you picked the wrong device to do it. They are the worst with kernel source. You can't completely compile a rom but use a patch system that does most of the work.
Yes it is different. There are some Tuts around but they are few as most don't use that type of chip.
If you really want to learn to develop then I would suggest getting a different device. One that respects the copyright and gpl laws.
Click to expand...
Click to collapse
Thank you for your advices. I have HTC desire 310 and I found the kernel sources. I know what I'll do in my free time
Monsterlevel said:
Thank you for your advices. I have HTC desire 310 and I found the kernel sources. I know what I'll do in my free time
Click to expand...
Click to collapse
To compile a rom u need kernel source, device tree and proprietary, bye

WIP* ( port) Linage OS LG Stylo 2 plus

Development is dead. Please delete..
Rmontoya83 said:
Good news I have a working Linage OS 13 build for the lg stylo 2 Plus GSM. Thought it was bug free still has some issues though . My PC took a dump I have the sources saved on my hard drive I will have a new PC on Feb 6 and will release the Rom For Free probably with in a few days from then. As I'm almost done porting a working lineage OS 14 for the device.
I will update the device tree on Github So I can get help from other devs to trouble shoot these issues better and collaborate works. I will also include a working recovery with the Rom for free . I am doing this in my free time so please be patient .
I will keep you posted ?
Any people interested in helping let me know.
Click to expand...
Click to collapse
I am interested in helping, I have the metropcs variant.
Latest up to date software. Due to that I have no root
LG Stylo 2 PLUS
TWRP no ROOT
cragains said:
I am interested in helping, I have the metropcs variant.
Latest up to date software. Due to that I have no root
LG Stylo 2 PLUS
TWRP no ROOT
Click to expand...
Click to collapse
You can downgrade your firmware .
Nice work let me know when the source is up at github , i may be able to help
I'm so anxious I can't wait to get my new PC! I will be compiling a lot faster. You guys are going to like this lineage OS port. Hang in there
Any screenshots?
I'm interested in this also
Pelegius22 said:
Any screenshots?
I'm interested in this also
Click to expand...
Click to collapse
Not at the moment I had the backlight on my display burn out . had to flash the stock rom back for warranty purposes and for some reason every time I try and back up via twrp the data gets corrupted.
So the only place I have a working Rom is stored on a hard drive and I get my PC back on the 6th this month so it will be up soon.
Twrp link
Rmontoya83 said:
You can downgrade your firmware .
Click to expand...
Click to collapse
No PC right now, I moved across the state, and left my PC.
Can't down grade
LG Stylo 2 PLUS
TWRP no ROOT
Got the new laptop up and running building starts tommorrow.
All souces are downloaded . I will start building the device tree tonight hopefully by end of week myself and @messi2050 will have a working lineage OS build for the ph2n. I stood up all night working on the list of proprietary files need for the build.
Now comes the hard work of adding all the required blobs to get it all functional please be patient. As we are doing this in out free time. Once the device tree is all setup it will be a lot easier to port other roms to this device such as omni aokp DU and so much more. I chose a 13 build as I'm new to this and its a lot easier to port a Rom that has many components that are stable with the version.
If you appreciate our work buy us a cup of coffee. Or hit the thanks button for the Devs working on this build .
Thanks to all the xda community.
We should work on a changelog concerning drivers for cheaper models like my tmousa k550.
(((Poll )))) custom kernel with more governors and overclock or stock kernel?
Rmontoya83 said:
(((Poll )))) custom kernel with more governors and overclock or stock kernel?
Click to expand...
Click to collapse
Custom kernel with more governors and overclock! Let me know if you need me to test, I have MetroPCS variant. Thank you also for your time and development for this amazing device!
Rmontoya83 said:
(((Poll )))) custom kernel with more governors and overclock or stock kernel?
Click to expand...
Click to collapse
Custom all the way.
I am sending this to you in hopes of curing my boredom...
Montoya, how are you getting the blobs? I have root when want it, I just don't right now. I have teamoctos synced, I have all the source code for our device. I'm not much of a programmer, but let me know I can help. I have Ubuntu with all the packages for compiling.
we need all the help we can get
Giminji said:
Montoya, how are you getting the blobs? I have root when want it, I just don't right now. I have teamoctos synced, I have all the source code for our device. I'm not much of a programmer, but let me know I can help. I have Ubuntu with all the packages for compiling.
Click to expand...
Click to collapse
@messi2050
has one repository done for device /device
i have the other kernel/
i am working on the blobs using @JackpotClavin utility tool to pull all the blobs needed for the build. once we have a stable tree we can work on building other roms.
Good news we have the the last branch to the tree built so builds will start this week sometime. We have a lot of work ahead still so be patient.
Tree source and blobs are on github.
https://github.com/RichieRich83
@messi2050
You rock brother.
Rmontoya83 said:
Good news we have the the last branch to the tree built so builds will start this week sometime. We have a lot of work ahead still so be patient.
Tree source and blobs are on github.
URL deleted I am too new.
@messi2050
You rock brother.
Click to expand...
Click to collapse
Both you and Messi are doing amazing things. When this is done, both of you are getting a cup of java (I couldn't resist Java instead of Joe or Coffee). I downloaded the jackpotcalvindonkey thing yesterday, did the make on it, but didn't get it out.
Btw, your github shows no public repos.
Well that was quick

[KERNEL] Major Linux Updates

Hello, I decided to come up with a project that aims to port higher Linux versions. When I say higher Linux versions, I mean those that are Linux 3.5 and up. The goal is to port Linux major updates as high as I can, but the main priorities are one that are LTS like Linux 3.10, 3.14 or even 3.18.
Only Android 7 will work on non-LTS versions. Oreo/pie and Android 10 support will be added only on LTS versions to lessen the conflicts when merging non-LTS versions.
What works:
Boots
Battery
Charger
Touchscreen
Display
USB
Sound
Buttons
Deep sleep
Camera
Video playback
Fingerprint
The rest of the sensors
WiFi
Bluetooth (works on Linux 3.7 and up)
Internet connection
Anything else I can't mention
What doesn't work:
You tell me
Drivers that can't be updated (yet) due to them being heavily modified by CAF and Samsung:
USB
Sound
MMC
Newer versions are more stable than the other due to the fact that I fix more bugs with every update.
The highest version as of now is Linux 3.8. I can only merge major updates during weekends due to my work.
Sources:
Linux 3.5
Linux 3.6
Linux 3.7
Linux 3.8
Linux 3.9
Feel free to open up issues and submit pull requests
It is highly recommended to delete mpdecision from /system/bin/ before flashing
Reserved
i don't understand what is this, is there some wiki i can read?
saikyom said:
i don't understand what is this, is there some wiki i can read?
Click to expand...
Click to collapse
These are kernel updates. Our device comes with Linux 3.4, but I've managed to update that up to 3.8
darrendude1 said:
These are kernel updates. Our device comes with Linux 3.4, but I've managed to update that up to 3.8
what are the benefits of updated kernel..cheers
Sent from my Unknown unknown using XDA Labs
Click to expand...
Click to collapse
Read these:
https://kernelnewbies.org/Linux_3.5
https://kernelnewbies.org/Linux_3.6
https://kernelnewbies.org/Linux_3.7
https://kernelnewbies.org/Linux_3.8
@pascua28
What a Huge Task! As Well as a Pain on the Ares!
Now, I do Have a few Q's for you.
1 IS this "Kernel Patch" Just for your beloved Galaxy S5's ?
2 Will this be for the "Basic" Kernel in an OS (e.g. LineageOS) ?
3 Wouldn't this hurt some of the "Custom Kernels" that we currently have and use?
And of course I must ask, how far do you intend to take this (e.g up and coming 5.7 ) ?
That Said, I am in! I have downloaded all the Kernels . Mostly to compare your changes. Have also saved your GitHub page.
Am wondering though, With some of these "Custom" Kernels..... Wouldn't we see much faster , smoother , and hopefully more Darn Battery with some of the Tweaks that we have with them? Or at least with some kernel manager?
Or, would these break those Kernels (now thinking about it)?
Certainly will be watching this!
Again , this is a huge task to undertake! Sure would love to see 4.1 and above for our phones. Maybe with Your updated Kernel, we could really see some major changes with our phones.... Plus, hopefully easier to Port into the likes of Android 10! ... or Of course jumping a bit here, and a bit positive, but Android 11 !
Good luck sir
godofsalt said:
@pascua28
What a Huge Task! As Well as a Pain on the Ares!
Now, I do Have a few Q's for you.
1 IS this "Kernel Patch" Just for your beloved Galaxy S5's ?
2 Will this be for the "Basic" Kernel in an OS (e.g. LineageOS) ?
3 Wouldn't this hurt some of the "Custom Kernels" that we currently have and use?
And of course I must ask, how far do you intend to take this (e.g up and coming 5.7 ) ?
That Said, I am in! I have downloaded all the Kernels . Mostly to compare your changes. Have also saved your GitHub page.
Am wondering though, With some of these "Custom" Kernels..... Wouldn't we see much faster , smoother , and hopefully more Darn Battery with some of the Tweaks that we have with them? Or at least with some kernel manager?
Or, would these break those Kernels (now thinking about it)?
Certainly will be watching this!
Again , this is a huge task to undertake! Sure would love to see 4.1 and above for our phones. Maybe with Your updated Kernel, we could really see some major changes with our phones.... Plus, hopefully easier to Port into the likes of Android 10! ... or Of course jumping a bit here, and a bit positive, but Android 11 !
Good luck sir
Click to expand...
Click to collapse
1. This is a full Linux upgrade. Nobody has ever done that to our beloved S5 cause it's a truckload of work
2. Uhm, I don't know. LineageOS is very strict on what kernel base to use, but I may propose to use this as a base when I reach 3.10
3. This project might be a good base for custom kernels since it is more updated and I will use this base too for my future custom kernels
4. As far as I can and as long as it works. Of course, I don't wanna die yet by not going too far.
Certainly, it won't break any kernel managers. You can even clone the latest source and add some custom features. It's up to you, but right now, in the process of upgrading, I won't be adding any custom features
Regards
pascua28 said:
1. This is a full Linux upgrade. Nobody has ever done that to our beloved S5 cause it's a truckload of work
2. Uhm, I don't know. LineageOS is very strict on what kernel base to use, but I may propose to use this as a base when I reach 3.10
3. This project might be a good base for custom kernels since it is more updated and I will use this base too for my future custom kernels
4. As far as I can and as long as it works. Of course, I don't wanna die yet by not going too far.
Certainly, it won't break any kernel managers. You can even clone the latest source and add some custom features. It's up to you, but right now, in the process of upgrading, I won't be adding any custom features
Regards
Click to expand...
Click to collapse
Well, Thank You. for the reply, as well as, all the information.
YES your project is a HUGE amount of work. Good guess, IS , you seem to want to take on this challenge! Good for you...
Yes, I do intend to really follow your project. Really looking forward to the great results that I hope we (you) can achieve !
Awesome...
Thanks
Hi guys! Linux 3.9 is up!
this is amazing work!
thank you very much for it.. I bet it's ugly as hell, but you learn a lot..
I'm patiently waiting for 3.10.0 since that's required by docker (running debian using Linux Deploy)
shmizan said:
this is amazing work!
thank you very much for it.. I bet it's ugly as hell, but you learn a lot..
I'm patiently waiting for 3.10.0 since that's required by docker (running debian using Linux Deploy)
Click to expand...
Click to collapse
Yeah, very tedious and requires a lot of skill
This is huge. Thank you for doing this, I will definitely be following this
pascua28 said:
Yeah, very tedious and requires a lot of skill
Click to expand...
Click to collapse
Yes, as well as time, the correct machine and layout....
Plus I believe it requires most patience than what I have!
BTW... This is great work, have not seen any issues on my S5..... (yet, but don't think that will happen though)
Thank you!
Sent from my Galaxy S5 using XDA Labs
Is this working on 5+ (katcc6)?
robla1000 said:
Is this working on 5+ (katcc6)?
Click to expand...
Click to collapse
Nope, S5 only. And at this point klte only until @pascua28 is finished bringing the kernel up to 3.10
Only working properly is klte, for now. Other variants might work but with bugs. Will fix for other variants when we get to 3.10
3.5 to 3.9 didn't work for me,I have klte
didn't work?
I ran 3.8 for weeks without any issues.. what exactly does not work?
many reboot ,i couldn't use
vlad3647 said:
many reboot ,i couldn't use
Click to expand...
Click to collapse
It's not for higher Android version.. If you have Android 9 or 10 then wait for version 3.10

[ROM] [UNOFFICIAL] LineageOS 14 for Meizu M5C [MT6737m]

LineageOS (Lineage Android Distribution) members or anyone else on this website is not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in the products you find here before flashing it! YOU are choosing to make these modifications, and if you point the finger at us for messing up your device, we will laugh at you. Your warranty will be void if you tamper with any part of your device / software.
How to Install:
1- Make a backup of your important files
2 - Unlock bootloader with this guide
3 - Flash the TWRP, link here
4 - Move Rom & Gapps (optional) into device storage
5 - Full Wipes
6- Flash Rom & Gapps (gapps are OPTIONAL)
for GAPPS:
Choose Gapps Package ARM64 > 7.1 > Micro and below: visit OpenGAPPS
If during the gapps flash it gives you an error then in the TWRP terminal or on the adb shell you have to execute this command: "mkdir /tmp/bin"
Download:
Releases · XRedCubeX/android_device_meizu_m5c
Contribute to XRedCubeX/android_device_meizu_m5c development by creating an account on GitHub.
github.com
Working:
Boots
Storages
Bluetooth
Wifi
GPS - GNSS
Audio
NOT Working:
Camera
Hotspot
Offline Charging
Special Thanks
LineageOS
Moyster for device trees
Device Tree:https://github.com/XRedCubeX/android_device_meizu_m5c
Vendor Tree: https://github.com/XRedCubeX/android_vendor_meizu_m5c
Assim que possível, irei testar!
Hi Red. I was taking a look at the ROM repository on GitHub, and saw that the default branch is now named cm-13.1. So, are you now working on an Android 6.0 ROM for the M5c?
thiagosousa777 said:
Hi Red. I was taking a look at the ROM repository on GitHub, and saw that the default branch is now named cm-13.1. So, are you now working on an Android 6.0 ROM for the M5c?
Click to expand...
Click to collapse
I have a slight indecision, now I can not carry on the Custom ROM because I do not have the right PC but when I am able to compile it, I will evaluate which one can work better
XRed_CubeX said:
I have a slight indecision, now I can not carry on the Custom ROM because I do not have the right PC but when I am able to compile it, I will evaluate which one can work better
Click to expand...
Click to collapse
I see. I would say that in the long run Lineage 14 would be more worthwhile, since Android 6.0 is becoming outdated, with no support for some apps. But really, I just wanted a ROM to replace Flyme, and its bugs. Also, many of the apps I use don't work, or don't work right on Flyme...
These days I was taking a look at /e/ OS. I've been thinking about venturing into porting this ROM to the M5c. For me it would be a challenge, since I've never done this before. But unfortunately at the moment I also don't have a PC that meets the requirements to compile the ROM
thiagosousa777 said:
I see. I would say that in the long run Lineage 14 would be more worthwhile, since Android 6.0 is becoming outdated, with no support for some apps. But really, I just wanted a ROM to replace Flyme, and its bugs. Also, many of the apps I use don't work, or don't work right on Flyme...
These days I was taking a look at /e/ OS. I've been thinking about venturing into porting this ROM to the M5c. For me it would be a challenge, since I've never done this before. But unfortunately at the moment I also don't have a PC that meets the requirements to compile the ROM
Click to expand...
Click to collapse
I find it useless, just use lineage without gapps and it will be better than /e/, then anyway I don't know where to find the manifest
XRed_CubeX said:
I find it useless, just use lineage without gapps and it will be better than /e/, then anyway I don't know where to find the manifest
Click to expand...
Click to collapse
You are right. However, /e/ has some nice features like e account synchronization, an app store, microG, and some of their apps... Of course we could get that with LineageOS, but it is interesting how /e/ already brings that well integrated and ready.
By the way, I am also looking at other non-Android systems, like Ubuntu Touch...
thiagosousa777 said:
You are right. However, /e/ has some nice features like e account synchronization, an app store, microG, and some of their apps... Of course we could get that with LineageOS, but it is interesting how /e/ already brings that well integrated and ready.
By the way, I am also looking at other non-Android systems, like Ubuntu Touch...
Click to expand...
Click to collapse
Ah beautiful those non-android systems yes, unfortunately we have to forget them because of the prebuilt kernel and unavailable sources
XRed_CubeX said:
Ah beautiful those non-android systems yes, unfortunately we have to forget them because of the prebuilt kernel and unavailable sources
Click to expand...
Click to collapse
Well, from what I've been reading the process is similar to porting LineageOS. You just need the kernel sources and the device specific binary blobs. I'm guessing you know how to get them, don't you?
And the interesting thing is that there is a layer, called Halium, that interacts directly with the hardware. And that is actually what you should port to the desired device. Then you can install any Linux system on top of this layer, like Ubuntu Touch, Plasma Mobile, etc, and these are distributed pre-compiled.
thiagosousa777 said:
Well, from what I've been reading the process is similar to porting LineageOS. You just need the kernel sources and the device specific binary blobs. I'm guessing you know how to get them.
And the interesting thing is that there is a layer, called Halium, that interacts directly with the hardware. And that is actually what you should port to the desired device. Then you can install any Linux system on top of this layer, like Ubuntu Touch, Plasma Mobile, etc, and these are distributed pre-compiled.
Click to expand...
Click to collapse
Mhh ... good, you are informed, however the vendor blobs are bull**** to take, the problem is the kernel sources but Meizu has not released them. However, some time ago I booted a Custom kernel based on ALPS (A custom AOSP from Mediatek to be clear) but the touchscreen doesn't work and I'm looking for a solution around but that I can't find
P.S: Fixing that kernel has great potential, forget android 7, you could also boot android 9 with sources, but as long as they are still working
XRed_CubeX said:
Mhh ... good, you are informed, however the vendor blobs are bull**** to take, the problem is the kernel sources but Meizu has not released them. However, some time ago I booted a Custom kernel based on ALPS (A custom AOSP from Mediatek to be clear) but the touchscreen doesn't work and I'm looking for a solution around but that I can't find
P.S: Fixing that kernel has great potential, forget android 7, you could also boot android 9 with sources, but as long as they are still working
Click to expand...
Click to collapse
I confess I didn't quite understand one thing: so how did you port LineageOS to this device? You didn't need the kernel sources?
thiagosousa777 said:
I confess I didn't quite understand one thing: so how did you port LineageOS to this device? You didn't need the kernel sources?
Click to expand...
Click to collapse
At the time I was doing this lineage, I was with the prebuilt kernel, week ago I had done this kernel port to a twrp and the touch was not working so I left the device alone
XRed_CubeX said:
At the time I was doing this lineage, I was with the prebuilt kernel, week ago I had done this kernel port to a twrp and the touch was not working so I left the device alone
Click to expand...
Click to collapse
Thanks for the clarification! It is a shame that Meizu does this (I wonder if they are not violating the terms of the Linux GPL license by distributing the kernel without publishing the modifications made to the source code).
Anyway, if a solution to this kernel problem related to the touch screen comes up, please let me know. In the meantime I'll keep reading Halium's documentation until a solution comes along, or until I get a compatible phone.
Great work!
Hello. I've been testing this ROM on my M5c and love it. The ROM is very good, fluid, lightweight... the only problem is that the camera doesn't work, as well as the cellular network data. Congratulations for the excellent work.
The ROM will no longer receive bugfixes?
pls compile
publish a release

Categories

Resources