Related
The project is based on Cyanogenmod 12.1.
At the moment, compiled alpha version of the firmware 12.1 CM + NPROJ.
Place it just after you make a backup of all data.
What is now present in the firmware:
Driver stock camera, no differences photos from photos taken at the drain, everything works, panorama, skype, etc. The runoff when you press the shutter release triggers auto-focus, so now it is 12.1 CM!
New initlogo.
I actually Russian, and accordingly made Russian the default language (forgive me for that please )
Disabled ADB secure.
Tweaks build.prop (to improve the quality of the photos).
Disabled block Assembly firmware, easily installed on the system, which has a size less than 2 GB (Yes, you can pick zip).
Bugs, jambs (it's not I made them):
Not working cyanogen setup wizard.
Crash software.
You can see the green demigod "AP Watchdog bark detected!" (crash software).
If you see a black demigod (this is the crash kernel), let me know.
Incorrectly read Bluetooth MAC address (Skite how to fix if anyone knows, my brain is not enough).
Source code: https://github.com/nitrogen-project
Attention! Immediately after installation to put Nitrogen Kernel!
Download: https://yadi.sk/d/GqqvKSddenX5R/Cyanogenmod/Cyanogenmod 12.1/Alpha
Aha! Thanks for this thread. It was really needed. The first ROM with true stock camera.
To bypass the cm setup wizard after installing the ROM we should mount system and go into system folder and delete cynogen setup wizard folder.
To do this on philz touch, we need an aroma file manager placed in clockworkmod/aromafm/aromafm.zip path.
Nice work @Mr.MEX, you've really got the point with this ROM.
akahroba said:
Aha! Thanks for this thread. It was really needed. The first ROM with true stock camera.
To bypass the cm setup wizard after installing the ROM we should mount system and go into system folder and delete cynogen setup wizard folder.
To do this on philz touch, we need an aroma file manager placed in clockworkmod/aromafm/aromafm.zip path.
Click to expand...
Click to collapse
Well or through twrp to delete CyanogenSetupWizard.apk
Loller79 said:
Nice work @Mr.MEX, you've really got the point with this ROM.
Click to expand...
Click to collapse
Thanks
P.S. Now compile the version from today, let's see, did they issue the green demigod's.
Well, fix WiFi (From mako N4) added.
Have to learn Russian, as I learned English forcing myself to use everything in English, why not do ok t again? Lmao. It comes with your kernel by default?
@Mr.MEX about the bluetooth mac address, there is a fix by your countryman in this thread: http://forum.xda-developers.com/showthread.php?t=2528556
apparently the problem is caused by freegee unlock. hope it will help.
If I disconnect the cellular network and WiFi lose imei ... how come?
I often appears green screen "AP watchdog detected shoulder." What causes this error?
guidoido004 said:
Have to learn Russian, as I learned English forcing myself to use everything in English, why not do ok t again? Lmao. It comes with your kernel by default?
Click to expand...
Click to collapse
Yes, but this alpha no the second alpha will be delivered.
akahroba said:
@Mr.MEX about the bluetooth mac address, there is a fix by your countryman in this thread: http://forum.xda-developers.com/showthread.php?t=2528556
apparently the problem is caused by freegee unlock. hope it will help.
Click to expand...
Click to collapse
The fix does not work on version 5.
zed923 said:
If I disconnect the cellular network and WiFi lose imei ... how come?
Click to expand...
Click to collapse
But from now on more.
st4ik said:
I often appears green screen "AP watchdog detected shoulder." What causes this error?
Click to expand...
Click to collapse
Curves hands of the guys from CM.
I've been checking the thread for whole day long. No new build? And please upgrade linux to 3.4.107. loller did it
akahroba said:
I've been checking the thread for whole day long. No new build? And please upgrade linux to 3.4.107. loller did it
Click to expand...
Click to collapse
The kernel 0.2.9 are left to compile, there's always tomorrow, and maybe if I tell dadi11 how to change the compiler (toolchain), we will collect and firmware (can't figure out how to replace the compiler).
But you do not want then pick the zip and sew it to the core.
Mr.MEX said:
The kernel 0.2.9 are left to compile, there's always tomorrow, and maybe if I tell dadi11 how to change the compiler (toolchain), we will collect and firmware (can't figure out how to replace the compiler).
But you do not want then pick the zip and sew it to the core.
Click to expand...
Click to collapse
Can you also send a pull request to cm team to add the camera libs?
Attached Wallpaper, initlogo, bootanimation - will be in the next version.
akahroba said:
Can you also send a pull request to cm team to add the camera libs?
Click to expand...
Click to collapse
They don't accept pull requests. Only through gerrit and gerrit for me it's the dark forest.
Mr.MEX said:
They don't accept pull requests. Only through gerrit and gerrit for me it's the dark forest.
Click to expand...
Click to collapse
I see. Maybe xyyx can cherry pick it from your source. I'm not sure if he cares at all :/
It's not that hard. If even I have done some commits to (pac) Gerrit you'll also give the trick [emoji14]
akahroba said:
I see. Maybe xyyx can cherry pick it from your source. I'm not sure if he cares at all :/
Click to expand...
Click to collapse
So he's euphoria compiles, CM hates...
dadi11 said:
It's not that hard. If even I have done some commits to (pac) Gerrit you'll also give the trick [emoji14]
Click to expand...
Click to collapse
Um for one thing, they don't add a vendor for the devices in the source - this may be the reason why they don't add fix for camera + need to make commits to the kernel (the driver from the runoff).
Finally!!!
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/mocha-kk-oss
Finally, now xda can see some updates/threads for mipad
Kage Yume said:
Finally!!!
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/mocha-kk-oss
Click to expand...
Click to collapse
What a good news!. I Hope someone will already working in a newer ROM for Mi Pad ...
Hello,
This is a good news!!!
Hope some developers start playing with it.
Kind regards.
nah, this monster did not survive. let it be. no one care mi pad already. release sources 2 and a half years is rubbish. forget about it.
ChooiWC said:
nah, this monster did not survive. let it be. no one care mi pad already. release sources 2 and a half years is rubbish. forget about it.
Click to expand...
Click to collapse
I agree you.**** Off Xiaomi.
Sent using XDA One
The important question is.. how broken is it?
Had to make these changes to build it. Yet not boot-able.
Makefile
-Werror-implicit-function-declaration
Drivers/tspdrv/tspdrv.c
43 #include "tspdrv.h"
52 "ImmVibeSPI.c"
93 "tspdrvOutputDataHandler.c"
95 "VibeOSkernelLinuxHRTime.c"
Drivers/staging/ozwpan/ozeventtrace.h
219 #include" trace/define_trace.h"
216 . - > /home/android/mocha/k/drivers/staging/ozwpan
Drivers/tspdrv/makefile
33 EXTRA_CFLAGS += - I$(M) -> -I$(shell pwd)
Used 4.7 Google toolchain.
Sudeep Duhoon said:
Had to make these changes to build it. Yet not boot-able.
Makefile
-Werror-implicit-function-declaration
Drivers/tspdrv/tspdrv.c
43 #include "tspdrv.h"
52 "ImmVibeSPI.c"
93 "tspdrvOutputDataHandler.c"
95 "VibeOSkernelLinuxHRTime.c"
Drivers/staging/ozwpan/ozeventtrace.h
219 #include" trace/define_trace.h"
216 . - > /home/android/mocha/k/drivers/staging/ozwpan
Drivers/tspdrv/makefile
33 EXTRA_CFLAGS += - I$(M) -> -I$(shell pwd)
Used 4.7 Google toolchain.
Click to expand...
Click to collapse
What are you trying to boot it with? MIUI?
Xiaomi have a bad habit of not using kernel base compatible with newer proprietary firmware blobs.
Harrynowl said:
What are you trying to boot it with? MIUI?
Xiaomi have a bad habit of not using kernel base compatible with newer proprietary firmware blobs.
Click to expand...
Click to collapse
Miui cn dev 6.10.13 (version can vary from 6.9.x-6.11.3, I don't remember, will update tomorrow)
Will update the build here so anyone can test it.
Based on which Android version? I'm hoping in a MIUI 8 based on Android Marshmallow for now, and future upgrade to Nougat. It will remain a dream?
Sudeep Duhoon said:
Miui cn dev 6.10.13 (version can vary from 6.9.x-6.11.3, I don't remember, will update tomorrow)
Will update the build here so anyone can test it.
Click to expand...
Click to collapse
Hello,
Is possible to build CM with this kernel?
Regards.
jlazkano said:
Hello,
Is possible to build CM with this kernel?
Regards.
Click to expand...
Click to collapse
Don't know. Never built rom.
In best of my knowledge, to build cm with this kernel, it would be difficult as we don't have device tree.
Android version upgrade is more difficult.
It boots with firmware blobs used in miui7. Works as well (nice change)
Harrynowl said:
It boots with firmware blobs used in miui7. Works as well (nice change)
Click to expand...
Click to collapse
Is this screenshoot a CM version of Mi Pad1?
Kind regards.
jlazkano said:
Is this screenshoot a CM version of Mi Pad1?
Kind regards.
Click to expand...
Click to collapse
Boots on CM11 also, if this is what you're asking
Harrynowl said:
Boots on CM11 also, if this is what you're asking
Click to expand...
Click to collapse
That is great!
If you upload the image, I could help testing it.
Best regards.
jlazkano said:
That is great!
If you upload the image, I could help testing it.
Best regards.
Click to expand...
Click to collapse
You can find my source here:
https://github.com/harrynowl/MiPad
This is only fixup so it compiles using 4.9 GCC
Sudeep Duhoon said:
Had to make these changes to build it. Yet not boot-able.
Makefile
-Werror-implicit-function-declaration
Drivers/tspdrv/tspdrv.c
43 #include "tspdrv.h"
52 "ImmVibeSPI.c"
93 "tspdrvOutputDataHandler.c"
95 "VibeOSkernelLinuxHRTime.c"
Drivers/staging/ozwpan/ozeventtrace.h
219 #include" trace/define_trace.h"
216 . - > /home/android/mocha/k/drivers/staging/ozwpan
Drivers/tspdrv/makefile
33 EXTRA_CFLAGS += - I$(M) -> -I$(shell pwd)
Used 4.7 Google toolchain.
Click to expand...
Click to collapse
Yep. I too tried the same. I built CM13 from this kernel but not booting.
https://github.com/Nihhaar/android_kernel_xiaomi_mocha/
I know xiaomi source is broken.
Hi !
Harrynowl said:
You can find my source here:
https://github.com/harrynowl/MiPad
This is only fixup so it compiles using 4.9 GCC
Click to expand...
Click to collapse
1. Could you explain whether this would allow use of the kernel with later versions of Android like Marshmallow or Nougat ?
2. If not, what would be required for it to work ?
3. As someone who is adept at compiling and editing kernels, could you recommend a few links related to compiling and editing kernels ? It would be of great help to new learners like myself.
Thanks !
Thank you !
Hi all,
I've created an issue on Motorola's kernel-msm repo that is a request for them to release the kernel sources for the G 5 Plus (Potter).
The post is here - https://github.com/MotorolaMobilityLLC/kernel-msm/issues/104
Please feel free to reply with similar requests so as to get Motorola moving on a proper GPL source release.
-Rob
bob2600 said:
Hi all,
I've created an issue on Motorola's kernel-msm repo that is a request for them to release the kernel sources for the G 5 Plus (Potter).
The post is here - https://github.com/MotorolaMobilityLLC/kernel-msm/issues/104
Please feel free to reply with similar requests so as to get Motorola moving on a proper GPL source release.
-Rob
Click to expand...
Click to collapse
https://github.com/MotorolaMobilityLLC/kernel-msm/blob/MMI-NPN25.137-15/arch/arm/configs/ext_config/mot8953-potter.config
:good:
The sources are already out....
Oh really? My bad... Can I just pull from that kernel-msm repo mentioned in the original post? Or is there a different repo just for Potter?
It looks like the source release for NPN25.137-15 is tagged here:
https://github.com/MotorolaMobilityLLC/kernel-msm/tree/MMI-NPN25.137-15/
It's a bit older than the version shipped with my phone but it could work. I'm going to see if I can compile it later.
bob2600 said:
It looks like the source release for NPN25.137-15 is tagged here:
https://github.com/MotorolaMobilityLLC/kernel-msm/tree/MMI-NPN25.137-15/
It's a bit older than the version shipped with my phone but it could work. I'm going to see if I can compile it later.
Click to expand...
Click to collapse
All the best. :good:
rayzen6 said:
All the best. :good:
Click to expand...
Click to collapse
Why'd you edit your post? I took a look at Alberto's repo and it looks like it would be compatible with our phones.
Seemed like a decent course of action to take. Did you try it yourself? Did it work? Don't just provide no reason, let's get hacking...
bob2600 said:
Why'd you edit your post? I took a look at Alberto's repo and it looks like it would be compatible with our phones.
Seemed like a decent course of action to take. Did you try it yourself? Did it work? Don't just provide no reason, let's get hacking...
Click to expand...
Click to collapse
Man yes let me mention the guy who successfully able to build with Alberto's sources. He is @i.snehal.kiran.
He has done this to compile but unfortunately for some reason he doesn't able to get the device to test. His msg is below
basically i have taken addison device tree ...just change the kernel path and defconfig name in boradconfig.mk ..makes it build boot.img
the source provided by motorola on github is full of errors..so use alberto's kernel for addison till you get official kernel from moto
https://github.com/Alberto97/android_kernel_motorola_msm8953
I edited the post bcz I thought u want to work with custom kernel for stock rom. And I thought this might not be useful.
bob2600 said:
Why'd you edit your post? I took a look at Alberto's repo and it looks like it would be compatible with our phones.
Seemed like a decent course of action to take. Did you try it yourself? Did it work? Don't just provide no reason, let's get hacking...
Click to expand...
Click to collapse
So what happened next? Did you tried something?
Edit:- btw one of the guy has replied positively on issue. :Good: I think we'll have a separate source soon.
rayzen6 said:
So what happened next? Did you tried something?
Edit:- btw one of the guy has replied positively on issue. :Good: I think we'll have a separate source soon.
Click to expand...
Click to collapse
I got as far as getting the LineageOS sources pulled for 14.1, had to do it twice since it was too big for my home directory so I had to create a new volume and run repo sync again. Took forever, but at least I have the OS sources downloaded. Now we're at the point of getting that kernel and setting up a device configuration for our device. Once we get that, then I can see if we can build and flash.
bob2600 said:
I got as far as getting the LineageOS sources pulled for 14.1, had to do it twice since it was too big for my home directory so I had to create a new volume and run repo sync again. Took forever, but at least I have the OS sources downloaded. Now we're at the point of getting that kernel and setting up a device configuration for our device. Once we get that, then I can see if we can build and flash.
Click to expand...
Click to collapse
Cool. Good work man. I'm in for testing.
Kernel sources are up
https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-NPN25.137-33
I'm just curious whether anyone has already compiled the AOSP for A13 and booted it. I noticed it had already been done/tested on OP5/5T, but wasn't sure if it had been done for P6P. I plan on trying my hand at it, but wanting to know what others may have experienced before I commit my slower internet connection to downloading the Repo.
GrapheneOS has test builds up for A13, which should be buildable using the normal approach. Also hardened with some extra security features.
Yes, on ArrowOS, temp issues however that was same day arrow started updating to 13, have not run a build since. Evolution X reboot a few seconds after setup screen loads, does not boot without gapps either.
I have tried for several days, but I'm missing something
It's a custom rom for personal use. A12.1 booted and worked perfectly but 13 reboots to bootloader
RealSchnedi - Repositories
RealSchnedi has 15 repositories available. Follow their code on GitHub.
github.com
Schnedi said:
I have tried for several days, but I'm missing something
It's a custom rom for personal use. A12.1 booted and worked perfectly but 13 reboots to bootloader
RealSchnedi - Repositories
RealSchnedi has 15 repositories available. Follow their code on GitHub.
github.com
Click to expand...
Click to collapse
Stupid question have you flashed both slots with 13 as I know boot loader won't load of you have 12 version and not updated to 13 but also it has an anti roll back in it sorry not much help
liggerz87 said:
Stupid question have you flashed both slots with 13 as I know boot loader won't load of you have 12 version and not updated to 13 but also it has an anti roll back in it sorry not much help
Click to expand...
Click to collapse
I flashed the bootloader and radio on both slots but haven't tried to change the current slot and flash the rom
But if I flash the official 13 release (only in the current slot) it boots, so, not sure if that's the problem. Anyway, I'll try it
Schnedi said:
I flashed the bootloader and radio on both slots but haven't tried to change the current slot and flash the rom
But if I flash the official 13 release (only in the current slot) it boots, so, not sure if that's the problem. Anyway, I'll try it
Click to expand...
Click to collapse
Been looking at our github, you are using anayw2001 repo for your vendor files, remove the below from Android.bp. I had Restless nights with a poop load of testing thinking it was something with a missing lib file or so when i test anay's vendor files with lots of comparison to lineage extract tools that worked. Well if your getting bootonce-bootloader error that is as reason for bootloader load.
prebuilt_apex {
name: "com.google.android.compos",
owner: "google_devices",
src: "system_ext/apex/com.google.android.compos.apex",
prefer: true,
system_ext_specific: true,
}
prebuilt_apex {
name: "com.google.android.virt",
owner: "google_devices",
src: "system_ext/apex/com.google.android.virt.apex",
prefer: true,
system_ext_specific: true,
}
alvin14 said:
Yes, on ArrowOS, temp issues however that was same day arrow started updating to 13, have not run a build since. Evolution X reboot a few seconds after setup screen loads, does not boot without gapps either.
Click to expand...
Click to collapse
Update on this for ArrowOS. After removing connectivitythernmalmanager that fixed the issue as i am getting selinux denials with it, everything works, been testing for a few days.
alvin14 said:
Been looking at our github, you are using anayw2001 repo for your vendor files, remove the below from Android.bp. I had Restless nights with a poop load of testing thinking it was something with a missing lib file or so when i test anay's vendor files with lots of comparison to lineage extract tools that worked. Well if your getting bootonce-bootloader error that is as reason for bootloader load.
prebuilt_apex {
name: "com.google.android.compos",
owner: "google_devices",
src: "system_ext/apex/com.google.android.compos.apex",
prefer: true,
system_ext_specific: true,
}
prebuilt_apex {
name: "com.google.android.virt",
owner: "google_devices",
src: "system_ext/apex/com.google.android.virt.apex",
prefer: true,
system_ext_specific: true,
}
Click to expand...
Click to collapse
I was already using your vendor from gitlab (arrow branch). It did the trick, bootloader not triggered anymore
Still not booting but it must be related to rom sources, will take a look
Thanks a lot
Schnedi said:
I was already using your vendor from gitlab (arrow branch). It did the trick, bootloader not triggered anymore
Still not booting but it must be related to rom sources, will take a look
Thanks a lot
Click to expand...
Click to collapse
Do a logcat during boot, will definitely help with that.
card13 said:
I'm just curious whether anyone has already compiled the AOSP for A13 and booted it. I noticed it had already been done/tested on OP5/5T, but wasn't sure if it had been done for P6P. I plan on trying my hand at it, but wanting to know what others may have experienced before I commit my slower internet connection to downloading the Repo.
Click to expand...
Click to collapse
There is a build of Hentai which is very good. You can even dirty flash from stock
alvin14 said:
Do a logcat during boot, will definitely help with that.
Click to expand...
Click to collapse
Thanks, I'm making some tests, not so sure it's the rom sources
Question, to build Evo and Arrow, are you using your adevtool vendor or the other one?
Schnedi said:
Thanks, I'm making some tests, not so sure it's the rom sources
Question, to build Evo and Arrow, are you using your adevtool vendor or the other one?
Click to expand...
Click to collapse
Adevtool. The other one works as well however i need to clean it up a bit.
hi guys,
@Schnedi what gapps package are you using for prime?
And does udfps work on your raven with your prime base?
Well, after a dozen of test builds, I finally made it work
Still have to fix things tho
Schnedi said:
Well, after a dozen of test builds, I finally made it work
Still have to fix things tho
Click to expand...
Click to collapse
Cool. I got oriole too boot prime yesterday too. Nice work!
What gapps package do you use? Is it on gitlab somewhere?
ny-hardcore said:
Cool. I got oriole too boot prime yesterday too. Nice work!
What gapps package do you use? Is it on gitlab somewhere?
Click to expand...
Click to collapse
I'm using this one: https://gitlab.com/spkal01/android_vendor_gms/-/tree/pyro
But removed some apps that can be installed from the store (drive, youtube, gmail, photos...)
Also, latest commit from fw/b fixes udfps
There's just a few features, I just pick the ones I use, didn't build prime to share it, so I'm not picking all of them. You can always fork the project and pick some features you use, PM me if you need any help with it
Schnedi said:
I'm using this one: https://gitlab.com/spkal01/android_vendor_gms/-/tree/pyro
But removed some apps that can be installed from the store (drive, youtube, gmail, photos...)
Also, latest commit from fw/b fixes udfps
There's just a few features, I just pick the ones I use, didn't build prime to share it, so I'm not picking all of them. You can always fork the project and pick some features you use, PM me if you need any help with it
Click to expand...
Click to collapse
Thanks for the reply, i spark gapps too by the way haha
i picked udfps myself so had it working already
i like your vendor /vendor/extras very clean setup.
i know how to fork, but no need for now
Does official lineage os exist for munch? Or at least unofficial but maintained build?
I don't think so. We must wait.
If you don't mind to build it your self, you could use the source from ArrowOS which maintained by madmax7896(thanks madmax!!!).
I've build lineage19.1 (20.0 is running) with some mods but I lack of ability to maintain/improve the ROM. So just build it and use it for fun.
We get official in next month.
zelos156 said:
We get official in next month.
Click to expand...
Click to collapse
Good to know
zelos156 said:
We get official in next month.
Click to expand...
Click to collapse
Is it planned or just a guess?
ModernWires said:
Is it planned or just a guess?
Click to expand...
Click to collapse
Planned. Just give time for that.
zelos156 said:
Planned. Just give time for that.
Click to expand...
Click to collapse
Cool, thanks for the information.
zelos156 said:
We get official in next month.
Click to expand...
Click to collapse
Thank you for the good news
zelos156 said:
Planned. Just give time for that.
Click to expand...
Click to collapse
Nice，so many ROMs based on LineageOS.
zelos156 said:
We get official in next month.
Click to expand...
Click to collapse
not to doubt your statement but can you provide a source? And if there is a telegram group or anything of that sort I would like to join so I'm always up to date.
PyrateVEVO said:
not to doubt your statement but can you provide a source? And if there is a telegram group or anything of that sort I would like to join so I'm always up to date.
Click to expand...
Click to collapse
sm8250-common: Add munch to the list of supported devices · LineageOS/[email protected]
Change-Id: Ie500a81c711a157f6707f8f25c361685072762fd
github.com
Not sure if this is a proof or not, need someone to confirm
alfZKI said:
sm8250-common: Add munch to the list of supported devices · LineageOS/[email protected]
Change-Id: Ie500a81c711a157f6707f8f25c361685072762fd
github.com
Not sure if this is a proof or not, need someone to confirm
Click to expand...
Click to collapse
Good enough for me. I've got the bootloader unlocked and might just wait until Lineage goes official before flashing anything.
Unless anyone else is finding any of the currently avilable roms stable enough for daily driver?
Any news?
PyrateVEVO said:
not to doubt your statement but can you provide a source? And if there is a telegram group or anything of that sort I would like to join so I'm always up to date.
Click to expand...
Click to collapse
I'd like to reiterate PyrateVEVO's question:
Does anyone here have reason to assume that development on LineageOS for this device is happening at the moment?
alfZKI said:
sm8250-common: Add munch to the list of supported devices · LineageOS/[email protected]
Change-Id: Ie500a81c711a157f6707f8f25c361685072762fd
github.com
Not sure if this is a proof or not, need someone to confirm
Click to expand...
Click to collapse
The Github project that is referred to by alfZKI contains kernels for various devices like lmi or alioth but not munch.
There is a common kernel repository but there don't seem to be many much munch-related commits - but that could be alright.
I've scrolled through the Telegram group https://t.me/PocoF4updates and it seems like SebaUbuntu is the central figure to make the LineageOS bringup happen.
But judging on what he had to say in 17 July (https://t.me/s/SebaUbuntuBlog?) it looks to me like he had little interest in that. His release schedule for LOS20 (17 October) doesn't contain munch either.
But I've probably looked in the wrong direction.
Can you shed more light on where development for LOS happens zelos156?
sam0jones0 said:
Good enough for me. I've got the bootloader unlocked and might just wait until Lineage goes official before flashing anything.
Unless anyone else is finding any of the currently avilable roms stable enough for daily driver?
Click to expand...
Click to collapse
SparkOS and EvolutionX both great very stable and great battery life. Definetly better then that MIUI garbage that hasn't been updated for freaking 4 months.
lotan_rm said:
I'd like to reiterate PyrateVEVO's question:
Does anyone here have reason to assume that development on LineageOS for this device is happening at the moment?
The Github project that is referred to by alfZKI contains kernels for various devices like lmi or alioth but not munch.
There is a common kernel repository but there don't seem to be many much munch-related commits - but that could be alright.
I've scrolled through the Telegram group https://t.me/PocoF4updates and it seems like SebaUbuntu is the central figure to make the LineageOS bringup happen.
But judging on what he had to say in 17 July (https://t.me/s/SebaUbuntuBlog?) it looks to me like he had little interest in that. His release schedule for LOS20 (17 October) doesn't contain munch either.
But I've probably looked in the wrong direction.
Can you shed more light on where development for LOS happens zelos156?
Click to expand...
Click to collapse
Unfortunately we have to wait. But at that moment the person who was supposed to take it gave up. I don't have enough knowledge myself to do it... We have a Los-based crdroid. This is already a very good sign.