Database Info

[ROM][UNOFFICIAL][ALPHA][s2ve/p] Cyanogenmod 12.0

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.0 (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* I am 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 this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo.
Device-specific source code for the Samsung Galaxy S2 Plus are available from https://github.com/luk1337/android_device_samsung_s2vep,
https://github.com/luk1337/android_device_samsung_s2ve and https://github.com/luk1337/android_kernel_samsung_galaxys2plus-common.
Compatibilitiy Patches: https://github.com/luk1337/build_tools/tree/cm12
(Please give credit if you use them in your ROM and if you fix something, please submit patches.)
Do not submit bug on CyanogenMod issue tracker
Downloads
ROM: https://s.basketbuild.com/devs/LuK1337/CM12
Google Apps: For now, find your own package
What works?
Wi-Fi
Bluetooth
RIL (Calls, SMS, Mobile Data)
Sensors (Accelerometer, Compass, Light, Proximity, etc.)
Camera (photo)
Video playback
Audio (playback & recording)
GPS
Everything else not listed under "known issues"
Known Issues
screenrecord does not work
FM Radio does not work
Sometimes wake up causes music stutter
Video recording does not work
.wav playback does not work (.mp3 works fine)
SELinux is in permissive mode
Wi-Fi HAL (i.e. Scanning MAC Address Randomization) not implemented
Sim Tool Kit (STK) not fully working
Video in YouTube app sometimes freeze
Bluetooth headset isn't working
Does not work on 4.1 stock ROM's bootloader, please upgrade to 4.2 before flashing
Installation
Make a backup!
If you were on CM 10.1 or a stock ROM prior to 4.2, upgrade to 4.2.
Install ClockworkMod recovery with SELinux support
Reboot into recovery
Wipe data if coming from stock or another non-CM ROM (You may get a "staus 7" error if you fail to wipe.)
Install the ROM
Optionally install the Google Apps Addon
To upgrade to a newer build, simply flash the zip. There's no need for data wipe or flashing Google Apps again.
Changelog
20141116: Initial release
FAQ
Can you include Feature X into your ROM?
No. This ROM will have CyanogenMod's feature set.
Can you include S-Note/S-Planner/MultiWindow/Insert Samsung App Here?
No. This is an AOSP ROM and cannot have TouchWiz applications.
Can you include call recording?
No. CyanogenMod does not include call recording to avoid potential legal issues.
Can you add Feature X to the stock ROM?
No. I don't work on stock ROMs.
What kernel does this ROM use?
A slightly modified version of the stock kernel, the source code is linked above.
I've heard that Broadcom doesn't release source, how can you make this ROM?
Contrary to the popular belief, userspace driver source code is not always required to make an AOSP-based ROM as long as the proprietary binaries shipped with the device does not modify the API too heavily (or is from a very different version of Android). Instead of modifying the source code of the drivers, the Android source code was adapted to be able to use the proprietary binaries.
Can I use your ROM as a base?
http://source.android.com/source/licenses.html
Most of Android/CyanogenMod is licensed under the Apache License with other small parts licensed under other open-source licenses. Which means that you may modify and redistribute without asking for permission as long as the proper credits is given and it is not misappropriated as being the official CyanogenMod. (In other words, you must say that it is based on pawitp's unofficial CyanogenMod, but is not related to CyanogenMod in any other way.)
Can contacts be saved to phone/SIM?
No. It is not supported in AOSP-based ROMs.
Can I send files over Wi-Fi Direct?
Yes, but you must use third-party applications. The implementation provided on Samsung ROMs is not an open standard. AOSP/CM does not provide a native way to send files over Wi-Fi Direct.
Can I mirror your ROM?
You're free to, but I will not list it in this post.
Is overclock (OC) available?
1.3 GHz OC is available in Settings -> Performance -> Processor (enable developer mode first). Higher frequencies are not enabled since benchmark does not show additional benefit.
Will feature X from a previous version of CM be implemented?
I don't know, probably will be, eventually. I don't really involve myself in the feature-set side of CM.
Will you add OTA support?
No.
I cannot add APNs
Make sure you set the correct MCC/MNC code, the APN will not appear otherwise. Also make sure to use menu -> save (back button means discard).
Reporting Bugs
You are allowed to report bugs only in this thread.
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. The following is a useful format to follow.
Code:
What is your--
Phone model (s2ve or s2vep):
Radio (baseband):
CM version:
CM Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
CMSettings/Performance settings (other than stock):
ART Runtime:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Thanks
- The CyanogenMod team for providing a great ROM. Without all the compatibility work which went into it, this ROM would've been much harder to make
- CoolDevelopment, pawitp and other s2ve/p and i9082 devs
XDA:DevDB Information
[ROM][UNOFFICIAL][ALPHA][s2ve/p] Cyanogenmod 12.0, ROM for the Samsung Galaxy S II Plus
Contributors
LuK1337
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.0.x
Version Information
Status: Alpha
Created 2014-11-16
Last Updated 2014-11-16

NOTE: I'm still building s2ve, I'll upload it later.

Can't wait
can't wait for test! so excited

Awesome
PLease dont forget the Non NFC edition.. keep up the good work

essuraj said:
PLease dont forget the Non NFC edition.. keep up the good work
Click to expand...
Click to collapse
you can easily flash P-recovery and enjoy the dev's work

Hy, please upload today a download link for CM12, i really want to try it as faster as i can. :fingers-crossed::fingers-crossed::fingers-crossed:

Sheldd said:
Hy, please upload today a download link for CM12, i really want to try it as faster as i can. :fingers-crossed::fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
It will be uploaded today,just be patient!

Sheldd said:
Hy, please upload today a download link for CM12, i really want to try it as faster as i can. :fingers-crossed::fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
Buy me SSD or better PC then I would build it faster.

LuK1337 said:
Buy me SSD or better PC then I would build it faster.
Click to expand...
Click to collapse
Oh, sorry, i don't want to be ungrateful,but i'm really excited and i want to try it...:angel:

LuK1337 said:
Buy me SSD or better PC then I would build it faster.
Click to expand...
Click to collapse
First of all: thank you so much for this amazing work! I can't wait to try!
How long do you think will it take?
Because for me the day ends in 3-4 hours

So i can't add contacts to my phone or sim ?

About Gapps?
Thank you very much : LuK1337!
Does somebody know what Gapps we must use in this rom?

I think we can use this:
https://s.basketbuild.com/filedl/gapps?dl=gapps-lp-20141109-signed.zip

Newku said:
So i can't add contacts to my phone or sim ?
Click to expand...
Click to collapse
You can save contacts on Phone but not on sim.

NW2000 said:
I think we can use this:
https://s.basketbuild.com/filedl/gapps?dl=gapps-lp-20141109-signed.zip
Click to expand...
Click to collapse
Ok. Thank you!

LuK1337 said:
You can save contacts on Phone but not on sim.
Click to expand...
Click to collapse
thank you very much luk

Can We flash with normal cwm, exept 6.0.5.1?

it looks pretty good.
i tended to think that we wouldn't get that soon cm12, but luk is the best dev,also,grand duos devs.
we wait for ur build uploaded.
thank you man.

LuK1337 said:
[*]Install ClockworkMod recovery with SELinux support
[*]
Click to expand...
Click to collapse
Does it work with PhilzTouch by hacky?

I can't wait :victory: :victory:

[ROM][UNOFFICIAL][5.1.1][I9105/P] Cyanogenmod 12.1 [2016/07/21]

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1.1 (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* I am 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 this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo.
Device-specific source code for the Samsung Galaxy S II Plus are available from:
https://github.com/andixlm/android_device_samsung_galaxys2plus-common
https://github.com/andixlm/android_device_samsung_i9105
https://github.com/andixlm/android_device_samsung_i9105p
https://github.com/andixlm/android_kernel_samsung_galaxys2plus-common
Compatibilitiy Patches: https://github.com/doriandiaconu/build_tools/tree/cm-12.1/patches
Do not submit bugs on CyanogenMod issue tracker
Downloads
ROM: https://basketbuild.com/devs/DorianDiaconu/CM12.1
GApps: http://opengapps.org
What works?
RIL (Calls, SMS, Mobile Data)
Wi-Fi
Bluetooth
GPS
Camera
Video playback
Audio (playback & recording)
Sensors (Accelerometer, Compass, Light, Proximity, etc.)
Everything else not listed under "Known issues"
Known Issues
There are no major hardware issues
Installation:
Make a backup!
If you were on CM 10.1 or a stock ROM prior to 4.2, upgrade to 4.2.
Install ClockworkMod or TWRP recovery with SELinux support. Older CWM will result in a "status 7" error.
Reboot into recovery
Wipe data if coming from stock or another non-CM ROM (You may get a "staus 7" error if you fail to wipe.)
Install the ROM
Optionally install the Google Apps Addon
FAQ
Q: Can you include Feature X into your ROM?
A: No. This ROM will have CyanogenMod's feature set.
Q: Can you include S-Note/S-Planner/MultiWindow/Insert Samsung App Here?
A: No. This is an AOSP ROM and cannot have TouchWiz applications.
Q: Can you include call recording?
A: No. CyanogenMod does not include call recording to avoid potential legal issues.
Q: What kernel does this ROM use?
A: A slightly modified version of the stock kernel, the source code is linked above.
Q: I've heard that Broadcom doesn't release source, how can you make this ROM?
A: Contrary to the popular belief, userspace driver source code is not always required to make an AOSP-based ROM as long as the proprietary binaries shipped with the device does not modify the API too heavily (or is from a very different version of Android). Instead of modifying the source code of the drivers, the Android source code was adapted to be able to use the proprietary binaries.
Q: Can I use your ROM as a base?
A: http://source.android.com/source/licenses.html
Most of Android/CyanogenMod is licensed under the Apache License with other small parts licensed under other open-source licenses. Which means that you may modify and redistribute without asking for permission as long as the proper credits is given and it is not misappropriated as being the official CyanogenMod. (In other words, you must say that it is based on pawitp's unofficial CyanogenMod, but is not related to CyanogenMod in any other way.)
Q: Can contacts be saved to phone/SIM?
A: No. It is not supported in AOSP-based ROMs.
Q: Can I send files over Wi-Fi Direct?
A: Yes, but you must use third-party applications. The implementation provided on Samsung ROMs is not an open standard. AOSP/CM does not provide a native way to send files over Wi-Fi Direct.
Q: Will you add OTA support?
A: No.
Video Review:
Reporting bugs
You are allowed to report bugs only in this thread.
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. The following is a useful format to follow.
Code:
What is your:
- Phone model (I9105 or I9105P):
- Radio (baseband):
- CM version:
- CM Download URL:
- GApps version:
Did you:
- Wipe:
- Restore with titanium backup:
- Reboot after having the issue:
Are you using:
- A task killer:
- A non-stock kernel:
- CMSettings/Performance settings (other than stock):
- Other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Thanks
- The CyanogenMod team for providing a great ROM. Without all the compatibility work which went into it, this ROM would've been much harder to make
- @pawitp
- @CoolDevelopment, @LuK1337, @GHsR and other I9105/P and I9082 devs
If you like it, use it and don't forget to press the "Thanks" button or send me a beer via PayPal.
XDA:DevDB Information
CyanogenMod 12.1, ROM for the Samsung Galaxy S II Plus
Contributors
doriandiaconu
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
ROM Firmware Required: 4.2.2
Based On: CyanogenMod
Version Information
Status: Stable
Created 2016-04-19
Last Updated 2016-07-21

So what is new from the 15th January build??

insanix said:
So what is new from the 15th January build??
Click to expand...
Click to collapse
Dorian after update,rom freeze in samsung galaxy screen.

Nice job, i will try it now :fingers-crossed:
Edit: It's how anastasiszn said, phone freeze and "Samsung GALAXY SII Plus GT-I9105P" screen xD

I'll fix it today as soon as i get home
Sent from my GT-I9105P using XDA Free mobile app

anastasiszn said:
Dorian after update,rom freeze in samsung galaxy screen.
Click to expand...
Click to collapse
Yeap! Freeze in boot screen

I fixed it. Now uploading.

doriandiaconu said:
I fixed it. Now uploading.
Click to expand...
Click to collapse
Not fixed, still freezing at boot

Yes not fix
Στάλθηκε από το GT-I9105P μου χρησιμοποιώντας Tapatalk

Guys, it might've been a source bug.. It wasn't syncing properly. Now it looks ok.
I'm doing my homework tomorrow again.

*hint hint*

Hmm, downloaded the build last night, but no results, stuck at boot splash screen(the one that says the model name). I'll check it out today, see if it got fixed. Cheers!
EDIT: Nope, still keeps the splash screen. See if you can fix it somehow, i'd love to see the new build, really.

Booting issue fixed.
Sorry it took me so long. Now we have an up-to-date version of CM12.1. Enjoy!

Hello!
Just wondering if i can use this ROM for the non-NFC version of the phone (gt i9105)? If so is there any step that must be followed in addition to the ones already mentioned?

RaXeDge said:
Hello!
Just wondering if i can use this ROM for the non-NFC version of the phone (gt i9105)? If so is there any step that must be followed in addition to the ones already mentioned?
Click to expand...
Click to collapse
Yes you can. Flash nfc destroyer after flash rom

cracker12 said:
Yes you can. Flash nfc destroyer after flash rom
Click to expand...
Click to collapse
I tried it but got a status 7 error saying that the device is a s2ve and not a sv2ep. And could you also provide the link for the nfc destroyer? Thank you

RaXeDge said:
I tried it but got a status 7 error saying that the device is a s2ve and not a sv2ep. And could you also provide the link for the nfc destroyer? Thank you
Click to expand...
Click to collapse
Install twrp for 9105p and try again. Nfc destroyer: https://s.basketbuild.com/filedl/devs?dev=GHsR&dl=GHsR/galaxys2plus/NFC-DESTROYER_LOLLIPOP.zip

What changed in this version?
Hi Dorian,
Can you tell me what changed in this version, 28/5/2016
thx,
Rene

Can anyone connect to wps ?
Στάλθηκε από το GT-I9105P μου χρησιμοποιώντας Tapatalk

After a day of use my phone freeze when i open bassicaly apps like dialer or messaging and i need to take out my battery.

[UNOFFICIAL][ROM][10.0/9.0] LineageOS 17.1/16.0 [violet][Q/PIE]

Introduction
A spinoff thread from the previously-supported-official thread by Atman.
This thread will contain my unofficial builds for violet. On the 16.0 version, the only real fix (so far...) have been the fingerprint scanner sepolicy denials. I aim to do monthly/bimonthly builds to keep up to date with security patches, as so far I haven't encountered any other issues (let me know).
On the 17.1 version, I have slowly figured out how to make it work, but it is highly experimental.
The 16.0 ROM is stable (I use it as my daily driver).
If you find any bugs, please do take screenshots, give a way for me to replicate it on my device, and send a logcat. If you're super smart, use a logcat and filter for the keyword so I don't have to do even more digging
Please don't tell me to use PE/Mokee commits.
Yet another update. I've got 17.1 builds working without having to resort to cheap tricks and commits (sort of).
Flash instructions
Same as usual:
Reboot to fastboot and flash recovery with fastboot (You have to use the TWRP linked below. Other versions likely won't boot.)
Reboot to recovery TWRP
Wipe to format data, wipe again to wipe system and cache (not necessary if you're updating, only if you're switching ROMs)
Flash firmware (ADB sideload) (this step is dated. The newer builds have a higher target firmware so you should try to flash without the firmware first, then flash the firmware if the ROM doesn't work.)
Flash the ROM (sideload)
Flash GApps, Magisk, etc. as necessary
Done
Downloads (16.0) (STABLE)
Firmware (Dated firwmare)
Recovery (TWRP)
11-Jun-2021 build (with 05-May-2021 security patch), and MD5 Digest
For previous builds see below
Downloads (17.1)
Here's the 17.1 ROM. Here's the md5 hash. It has the March security patch.
It currently does not boot. If you would like to try and help with development, flash the ROM, and then flash the Chinese Q firmware on top of it (this can be downloaded from xiaomifirmwareupdater). Be warned that there is a risk that the newest android keymaster may re-encrypt your device, which in the worst case may require you to format data and/or reflash recovery and/or flash a fastboot MIUI rom. So, it's a bit risky, but likely won't be an issue.
Credits, Sources, etc.
Too many to mention. Atman Shah for getting this device supported earlier last year. ThE_MarD (Marc Bougoin) for other help. Various other names I've seen - Bruno Martins, Weikai Kong, Wang Han... all of the Lineage dev team. I'm sure I'm missing many people who have been involved in the project. I am new, and very much a latecomer to all of this.
Device Tree: https://gitlab.com/mzha/android_device_xiaomi_violet
Kernel Tree: https://gitlab.com/mzha/android_kernel_xiaomi_violet
Other things see my gitlab: https://gitlab.com/mzha
A telegram group to discuss development for 16.0/17.1: t.me/lineageos_violet
Previous builds
07-Nov-2020 (incl. Oct-2020 security patch), with 07-Nov-2020 MD5 Hash
13-Jul-2020 (incl. Jul-2020 security patch), with 13-Jul-2020 MD5 Hash
11-May-2020 (incl. May-2020 security patch), with 11-May-2020 MD5 Hash

Good to see some devs showing interest on this os
will you be adding any customisation? or does it continue as pure lineage os?

e2vinay said:
Good to see some devs showing interest on this os
will you be adding any customisation? or does it continue as pure lineage os?
Click to expand...
Click to collapse
Pure LineageOS. There's more than enough customised ROMs for violet already in my opinion... and I also don't have that much time

hcnulma said:
Pure LineageOS. There's more than enough customised ROMs for violet already in my opinion... and I also don't have that much time
Click to expand...
Click to collapse
That's great
by any chance will you consider adding signature spoofing support? that would be really great. it would help many users go for microG instead of gapps
I completely understand you're starter.
great work. good luck.
Thank you

e2vinay said:
will you consider adding signature spoofing support?
Click to expand...
Click to collapse
No, but there are a few alternatives:
Merge the changes from this RFC and build it
Download the spoofer from https://download.lineage.microg.org/violet/, or get the (ed)Xposed module, or other possibilities...

Will be official Lineage Os?

Can we expect los 17 soon?

himanshu fulmali said:
Can we expect los 17 soon?
Click to expand...
Click to collapse
As per OP: I'm waiting on both Android 10 firmware blobs + kernel to be released by Xiaomi... I'm not sure how the other ROM devs get around this, if it's easy to forward-port or not. But for now, only LOS 16.

Heyyo @hcnulma good to see you got your thread up and going!
As for 17.1? You can work with your current kernel and cherry-pick the fixes that other maintainers of violet are using and same for the device tree and vendor blobs.
As an example, LeEco msm8996 devives are using kernel source code from Marshmallow just rebased on a CAF Q Tag for our kernel since we never got anything newer...
Even once Xiaomi release their kernel source code for Android 10? It would probably take quite a bit of work to shave it down to what you specifically need and then importing it on top of a fresh CAF tag for the kernel or even more work to try and inplement it into uour current kernel.
To get official builds of LOS 16.0 going again for violet you would need to show that you are capable of fixing any major bugs that arise as well.
https://wiki.lineageos.org/submitting_device.html
anywho, hope this information helps bud!

hcnulma said:
As per OP: I'm waiting on both Android 10 firmware blobs + kernel to be released by Xiaomi... I'm not sure how the other ROM devs get around this, if it's easy to forward-port or not. But for now, only LOS 16.
Click to expand...
Click to collapse
I am pretty sure you can use the pixel experience device tree and kernel to compile the ROM just like every other rom

Thank you. If he is stable enough I will use it to build RR PIE

Zjh0094 said:
Thank you. If he is stable enough I will use it to build RR PIE
Click to expand...
Click to collapse
It's definitely stable...
prajwal2001 said:
I am pretty sure you can use the pixel experience device tree and kernel to compile the ROM just like every other rom
Click to expand...
Click to collapse
From what I understand, using their kernel tree will mean I'll have to change a lot of references in my own device tree, and using their device tree on top of that is essentially just building PE, not Lineage.
In any case, I did find the Snapdragon 675 (ie sm6150) kernel trees for Q in several places, https://github.com/sm6150-dev/android_kernel_xiaomi_sm6150 and https://github.com/PixelExperience-Devices/kernel_xiaomi_sm6150. I'll take a closer look into this...
I did find the most recent CAF kernel under sm6150 here, but there seems to be an issue of this not showing up in /quic/la... Something will be resolved. Hopefully.

Request to create group for discussion in Telegram

hcnulma said:
It's definitely stable...
From what I understand, using their kernel tree will mean I'll have to change a lot of references in my own device tree, and using their device tree on top of that is essentially just building PE, not Lineage.
In any case, I did find the Snapdragon 675 (ie sm6150) kernel trees for Q in several places, https://github.com/sm6150-dev/android_kernel_xiaomi_sm6150 and https://github.com/PixelExperience-Devices/kernel_xiaomi_sm6150. I'll take a closer look into this...
I did find the most recent CAF kernel under sm6150 here, but there seems to be an issue of this not showing up in /quic/la... Something will be resolved. Hopefully.
Click to expand...
Click to collapse
you won't have to make any changes in the kernel as far as I know and as for the device tree you just have to make some changes according to the ROM
as every ROM uses the same device tree
and you won't be making pe instead of lineage as the same device tree and kernel are used in every Q ROM except EvoX which uses crimson kernel

hcnulma said:
It's definitely stable...
Click to expand...
Click to collapse
Thanks. I will use it as my benchmark to build RR pie.
---------- Post added 15th February 2020 at 12:03 AM ---------- Previous post was 14th February 2020 at 11:57 PM ----------
hcnulma said:
In any case, I did find the Snapdragon 675 (ie sm6150) kernel trees for Q in several places, https://github.com/sm6150-dev/android_kernel_xiaomi_sm6150 and https://github.com/PixelExperience-Devices/kernel_xiaomi_sm6150. I'll take a closer look into this...
I did find the most recent CAF kernel under sm6150 here, but there seems to be an issue of this not showing up in /quic/la... Something will be resolved. Hopefully.
Click to expand...
Click to collapse
/quick/la/msm-4.14

prajwal2001 said:
you won't have to make any changes in the kernel as far as I know and as for the device tree you just have to make some changes according to the ROM
Click to expand...
Click to collapse
It is precisely the device tree that I'm worried about. From experience, PE has a lot of platform-specific stuff that Lineage doesn't (and the same the other way), and also from trying to figure out the fix to 16.0 I realised there's a lot of context/definition differences between the two device trees. I'd still give it a look, but I suspect it might be easier to just modify the current 16.0 device tree.
RupeshRN said:
Request to create group for discussion in Telegram
Click to expand...
Click to collapse
https://t.me/lineageos_violet.
Zjh0094 said:
/quick/la/msm-4.14
Click to expand...
Click to collapse
Yeah I already figured it was msm-4.14. Have already cloned it but am also considering cherrypicking changes that other devs have done to their kernel trees from 16.0 -> 17.1 as opposed to starting with the CAF kernel. A work in progress.

Sir I'm noob but mokee dev released android 10 and i think mokee and los are pretty same, will he not help you if you contact him?

An update on where I am:
I'm not sure whether to use the PE or Mokee vendor trees. Neither of them have much resemblance to 16.0 tree I have so cherry picking changes will be a nightmare.
The PE vendor tree has a lot of device-tree-specific commits, which will make it a headache to untangle later on. The Mokee vendor tree also has a lot of differing firmware files, though is a bit more similar to the LOS tree.
I'm doing a bit of experimentation to figure out which one will last better in the long run, since I can't seem to get my hands on any MIUI Android Q firmware blobs.

An update on where I am:
I'm not sure whether to use the PE or Mokee vendor trees. Neither of them have much resemblance to 16.0 tree I have so cherry picking changes will be a nightmare.
The PE vendor tree has a lot of device-tree-specific commits, which will make it a headache to untangle later on. The Mokee vendor tree also has a lot of differing firmware files, though is a bit more similar to the LOS tree.
I'm doing a bit of experimentation to figure out which one will last better in the long run, since I can't seem to get my hands on any MIUI Android Q firmware blobs.

Yet another update. I've got 17.1 builds working without having to resort to cheap tricks and commits (sort of).
Here's the 17.1 ROM. Here's the md5 hash. Needless to say, it's very experimental, not stable in the least (expect to get past boot maybe 70% of the time) - I'm getting very mixed results when experimenting myself. Nevertheless, try it out, see what you get. Install it the same way as usual. Keen to get as many eyes on this as possible

[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

Development [ROM][Official][Weekly] LineageOS 19.1 for Edge S / Moto G100

LineageOS is a free, community-built, aftermarket firmware distribution of Android 12, which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 this ROM
* 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.
*
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Important information:
This thread is for LineageOS 19.1 builds for Edge S / Moto G100. The following will not be supported here:
Custom kernels
Mods
Xposed
We don't support Xposed and any logcat which includes an Xposed module will be ignored. You're kindly invited to not report bugs if you:
Flashed a custom kernel
Installed or did mods from untrusted sources
Modified system files
Tips:
I have not implemented dynamic model detection yet, so the displayed model is always "Edge S" regardless of your actual hardware, this is not a bug.
Installation:
https://wiki.lineageos.org/devices/nio/install
Source code:
https://github.com/lineageos
Credits:
LineageOS Team & Contributors
Code Aurora Forum
Special thanks to Electimon, this work is heavily based on his prior ones.
......
Changelog & Download:
2022/2/20 initial release:​https://yukomoe-my.sharepoint.com/:...NPj4EdAKJwWzcBuIHXiDPzmHiNUB05M37v-Q?e=cUvmJQ​
Video over LTE (ViLTE) probably doesn't work
2022/3/13:​https://yukomoe-my.sharepoint.com/:...hPgpSvGHD7EuUBsAbKHzrf_9ppXNgZVLT5wg?e=0ZdHA4​
Sync latest source and update to Android 12L
2022/3/20:​https://yukomoe-my.sharepoint.com/:...BOs1iw7RXB0BIBbBDtvTA9T96hu4wmM0Z2_g?e=9mDL0e​
Sync latest source
Fix Wifi display
Fix status bar height for certain apps
Add indicator for fingerprint sensor
Less aggressive high refresh rate scheduling
Display color composition tweaks
Other minor changes
2022/3/21:​https://yukomoe-my.sharepoint.com/:...ZOo1OD0OKzDakB8OVvEsdgCJodeQh0d77r5Q?e=FKUfy7​
Emergency fix for crash when recording fingerprints for the first time
2022/3/27:​https://yukomoe-my.sharepoint.com/:...9Ai-nTJsfs95EBs2qLuwuRCyppY0KGRa8XLQ?e=cRjujv​
Sync latest source
2022/3/27 and later official release:​https://download.lineageos.org/nio​

The size of ZIP file only 746M? i remember the size of 19 alpha version is 2G.

Thanks
seems to work good!
was unable to enter recovery using the official LOS recovery but using Electimons LOSRecovery the install went ok

Nice.

Very good ROM, but few points:
1. Location not working
2. Please allow fingerprint unlock only when power button is pressed, like in stock ROM.
3. Please allow three finger swipe screenshot.

delete

dianlujitao said:
LineageOS is a free, community-built, aftermarket firmware distribution of Android 12, which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
Click to expand...
Click to collapse
This is the same phone for this build correct? I ask because the information on the pages are completely different.
Motorola Moto G100 - Full phone specifications
www.gsmarena.com
Info about nio variants | LineageOS Wiki
wiki.lineageos.org

Ryu945 said:
This is the same phone for this build correct? I ask because the information on the pages are completely different.
Motorola Moto G100 - Full phone specifications
www.gsmarena.com
Info about nio variants | LineageOS Wiki
wiki.lineageos.org
Click to expand...
Click to collapse
I Don't quite get your question
the links both refer to the moto g100/Edge S codename "nio" phones
there is no notable difference between device descriptions between the links
and yes this build is for that phone

henkery said:
I Don't quite get your question
the links both refer to the moto g100/Edge S codename "nio" phones
there is no notable difference between device descriptions between the links
and yes this build is for that phone
Click to expand...
Click to collapse
There is a difference in the stated amount of RAM and SoC used. I thought it could be an entry error but I wanted to make sure.

Ryu945 said:
There is a difference in the stated amount of RAM and SoC used. I thought it could be an entry error but I wanted to make sure.
Click to expand...
Click to collapse
ah I see what you mean now
the SoC stated is the same but there does not exist a 12gb version of the g100, this must be a mistake on gsmarenas side

henkery said:
ah I see what you mean now
the SoC stated is the same but there does not exist a 12gb version of the g100, this must be a mistake on gsmarenas side
Click to expand...
Click to collapse
Snapdragon 870 5G and Snapdragon 870 are not two different SoCs?

henkery said:
ah I see what you mean now
the SoC stated is the same but there does not exist a 12gb version of the g100, this must be a mistake on gsmarenas side
Click to expand...
Click to collapse
Pretty sure the 256gb version is paired with 12gb ram

Ryu945 said:
Snapdragon 870 5G and Snapdragon 870 are not two different SoCs?
Click to expand...
Click to collapse
yes ，it's same

does it not support matriel you？

dianlujitao said:
LineageOS is a free, community-built, aftermarket firmware distribution of Android 12, which is designed to increase
Click to expand...
Click to collapse
I unlocked the boot loader and installed the recovery in both slots. Then I told the bootloader to boot into recovery. It doesn't work. It just freezes. I just see it go the the Motorola log and freeze.

Ryu945 said:
I unlocked the boot loader and installed the recovery in both slots. Then I told the bootloader to boot into recovery. It doesn't work. It just freezes. I just see it go the the Motorola log and freeze.
Click to expand...
Click to collapse
Using whichever working recovery for the first install is okay. It's tricky to develop a universal working recovery image due to how a/b works.

Thanks for the new Build!
for the gapps users out there, you will have trouble finding a working gapps version as the sdk version has been upped and no public gapps package out there supports it yet but you can workaround this by just changing the supported sdk to 32 in the gapps props file

Is location working now?

los19.1 bug found：wifi display not working，plugs device and boot the phone，usb will not working

[20.03.2022]
So I'm after my first tests and:
1. texting/calling/internet wifi/5g works
2. the speed is very good
3. gps is catching relatively fast, you have to wait few seconds in application
4. turn to mute (gesture) - there is no vibration reaction that phone is muted.
I haven't noticed any bigger bugs, we will see how it will behave during the day,