Develop Bugs

[DISCUSSIONS][TESTING][ROM][UNOFFICIAL] CyanogenMod 13 ALPHA Build

This is a test build I take no responsibility for what this may or may not do to your device.
Click to expand...
Click to collapse
NEED TESTERS
currently i don't have the device to test i will be getting my device in the next week .
Click to expand...
Click to collapse
1. Install CWM Recovery
2. Do Full Wipe If coming from another ROM
3. Flash ROM
4. Flash Google Apps (my recommendation is to install minipal gapps due to /system partition size limits)
5. Reboot
Click to expand...
Click to collapse
]Not Booting
Click to expand...
Click to collapse
Code:
[B]Source[/B]
Here are the device tree :
Device Tree (from cm13 Nexus 9) : https://github.com/vickdu31/android_device_xiaomi_mocha
Kernel Tree (from Xiaomi KK) : https://github.com/vickdu31/android_kernel_xiaomi_mocha
Vendor Tree (old Xiaomi KK) : https://github.com/vickdu31/android_vendor_xiaomi_mocha
Thank you
@faust93 for cwm
XDA:DevDB Information
CM-13, ROM for the Xiaomi Mi Pad
Contributors
Rohit99, tank0412, vickdu31
ROM OS Version: 6.0.x Marshmallow
Based On: CyanogenMod
Version Information
Status: Testing
Created 2016-12-10
Last Updated 2016-12-13

Reserved

Edit 1:initial build didn't boot for me, no adb can't get log

Ok im gonna try it.
If you want, i can leave logcat for you

OoSTARTERoO said:
Ok im gonna try it.
If you want, i can leave logcat for you
Click to expand...
Click to collapse
Can get logcat? Try please.

Ofc, it doesn't boot. And don't create threads without testing.

Sudeep Duhoon said:
Can get logcat? Try please.
Click to expand...
Click to collapse
unfortunately....I couldn't get logcat too...

Sudeep Duhoon said:
Can get logcat? Try please.
Click to expand...
Click to collapse
we can't get logcat. It doesn't boot, i mean there are problems with kernel or init scripts or both. Kernel needs patches.

Nihhaar said:
Ofc, it doesn't boot.
Click to expand...
Click to collapse
As I thought

Prebuilt kernel from cm11
Sudeep Duhoon said:
As I thought
Click to expand...
Click to collapse
hey can i use prebuilt kernel from cm11 source @Nihhaar

Rohit99 said:
hey can i use prebuilt kernel from cm11 source @Nihhaar
Click to expand...
Click to collapse
Always try to build kernel with source. I think you can't, but you can try.

Please edit the link in OP, its me who miswrote it... : /android_device_xioami_mocha --> /android_device_xiaomi_mocha

You need to fix up SELinux and the init scripts. Taking a shield tablet device tree, renaming things to mocha and changing the fstab isn't enough. As far as I can tell the shieldtablet device tree also has dependency on a shield common tree. There's also no value in creating a new thread each time you push new commits
Our kernel from Xiaomi is also pretty useless without commit history. The device tree is also from shield tablet, not Nexus 9.
We also have a tree for building TWRP with OmniROM that you can compile TWRP 3.0.2.0 with.

What kernel repo is upstream one for tegra android? Like CAF for quallcom.
I've tried to merge xiaomi changes on l4t kernel https://github.com/HighwayStar/android_kernel_xiaomi_mocha
Merged dts files and arch/boot/march-tegra with some required drivers, but still cant boot it. Found somewhere here that l4t kernels is not for android, but for GNU/Linux, but what kernel is for android?
Cyanogenmod's shield kernel?

highwaystar_ru said:
What kernel repo is upstream one for tegra android? Like CAF for quallcom.
I've tried to merge xiaomi changes on l4t kernel https://github.com/HighwayStar/android_kernel_xiaomi_mocha
Merged dts files and arch/boot/march-tegra with some required drivers, but still cant boot it. Found somewhere here that l4t kernels is not for android, but for GNU/Linux, but what kernel is for android?
Cyanogenmod's shield kernel?
Click to expand...
Click to collapse
git://nv-tegra.nvidia.com/linux-3.10.git
I used rel-tn8-l-r7-shieldtablet8 to make a start on doing this. You could also use android_kernel_shield from CyanogenMod repo as it comes from the same place. But it will have a lot of extra commits for things not useful for mocha.
Here's what I have so far:
https://github.com/harrynowl/nvidia_tegra-3.10

Harrynowl said:
git://nv-tegra.nvidia.com/linux-3.10.git
I used rel-tn8-l-r7-shieldtablet8 to make a start on doing this. You could also use android_kernel_shield from CyanogenMod repo as it comes from the same place. But it will have a lot of extra commits for things not useful for mocha.
Here's what I have so far:
https://github.com/harrynowl/nvidia_tegra-3.10
Click to expand...
Click to collapse
Oh, intresting, cloned same url, but started other branch l4t/l4t-r21.5.
What status of your tree? Cant boot? We need minimal bootable kernel to be able to get dmesg and make further progress.

highwaystar_ru said:
Oh, intresting, cloned same url, but started other branch l4t/l4t-r21.5.
What status of your tree? Cant boot? We need minimal bootable kernel to be able to get dmesg and make further progress.
Click to expand...
Click to collapse
Untested, been doing device bring up. That kernel won't work yet anyway it's missing atmel, synaptic and battery firmware. (Plus the code that goes with it)
Some devs have one that gets to recovery but only 1 CPU core can come online and the CPU gets a bit hot. Unfortunately their commit history is hard to follow so I've not had a proper look at it yet

My my...it's been a while since I've seen a cringe-worthy dev thread on XDA. So OP just used the device tree from Nexus 9 (a 64-bit device with a different processor and nothing in common with the Mi Pad other than the fact that they use Nvidia SoCs and are both tablets), unmodified KITKAT kernel sources from Xiaomi (which takes work to make it boot, even on KK) and KITKAT userspace blobs to compile the ROM, and for some reason decided to share it without testing. The 10-post rule is meant to keep such people out of the development sub-forums, but obviously that's not working.
I do not understand why the moderators are allowing this thread to remain open. It's just a thread by a wannabe dev offering a non-bootable ROM that has the potential to brick the devices of many newbies who may decide to try this.
This thread is even more useless than the other "DEVS-ONLY" thread someone else made. Honestly, the entire Mi Pad forum is filled with people who either expect Android 7.1.1 to magically appear on their tabs just because Xiaomi released outdated kernel sources or just wanna create threads like this for the "thanks or whatever". The never ask for ETA rule seems to just float over their heads.
Now to some useful information. I believe, even if we patch the kernel enough for it to theoretically boot cm13, it probably won't, considering the outdated userspace blobs for the Mi Pad. Unless someone has the knowledge to take their tab apart and figure out how to get UART data, it will be virtually impossible for the mi pad kernel to boot any new version of Android. I heard another interesting approach taken by some russian devs at the Xiaomi forums. They've managed to port the kernel from the Nvidia shield (and apparently it's booting). Now this would mean we can use the userspace blobs from the Shield to at least get the ROM booting (most peripherals won't work, but that's step 2). I do not know whether they use GitHub or if they've even open-sourced their work, but now we know that it's possible, so that could be a possible method of approach.
EDIT: LOL. I just read the OP again. The "dev" expects donations to help him work harder. This from a person who posted his way into somehow compiling his first Android build without even having the damn device.

drakonizer said:
My my...it's been a while since I've seen a cringe-worthy dev thread on XDA. So OP just used the device tree from Nexus 9 (a 64-bit device with a different processor and nothing in common with the Mi Pad other than the fact that they use Nvidia SoCs and are both tablets), unmodified KITKAT kernel sources from Xiaomi (which takes work to make it boot, even on KK) and KITKAT userspace blobs to compile the ROM, and for some reason decided to share it without testing. The 10-post rule is meant to keep such people out of the development sub-forums, but obviously that's not working.
I do not understand why the moderators are allowing this thread to remain open. It's just a thread by a wannabe dev offering a non-bootable ROM that has the potential to brick the devices of many newbies who may decide to try this.
This thread is even more useless than the other "DEVS-ONLY" thread someone else made. Honestly, the entire Mi Pad forum is filled with people who either expect Android 7.1.1 to magically appear on their tabs just because Xiaomi released outdated kernel sources or just wanna create threads like this for the "thanks or whatever". The never ask for ETA rule seems to just float over their heads.
Now to some useful information. I believe, even if we patch the kernel enough for it to theoretically boot cm13, it probably won't, considering the outdated userspace blobs for the Mi Pad. Unless someone has the knowledge to take their tab apart and figure out how to get UART data, it will be virtually impossible for the mi pad kernel to boot any new version of Android. I heard another interesting approach taken by some russian devs at the Xiaomi forums. They've managed to port the kernel from the Nvidia shield (and apparently it's booting). Now this would mean we can use the userspace blobs from the Shield to at least get the ROM booting (most peripherals won't work, but that's step 2). I do not know whether they use GitHub or if they've even open-sourced their work, but now we know that it's possible, so that could be a possible method of approach.
EDIT: LOL. I just read the OP again. The "dev" expects donations to help him work harder. This from a person who posted his way into somehow compiling his first Android build without even having the damn device.
Click to expand...
Click to collapse
I agree, this device has no development threads. Only 2 give me thanks and here's my donation link threads.
They have indeed used GitHub, but I don't believe they want to share the repo just yet so I won't post it publicly. It has many problems to sort and also sadly, they didn't keep the commit history from Nvidia as it was initialised via zip DL. It does boot to recovery though.

Harrynowl said:
I agree, this device has no development threads. Only 2 give me thanks and here's my donation link threads.
They have indeed used GitHub, but I don't believe they want to share the repo just yet so I won't post it publicly. It has many problems to sort and also sadly, they didn't keep the commit history from Nvidia as it was initialised via zip DL. It does boot to recovery though.
Click to expand...
Click to collapse
Oh! I didn't realize we were talking about the same person/team. I'd love to start developing for this device. In fact, I'm working on KEXEC-hardboot and Multirom right now, but I'd like to follow what you guys are doing and contribute as much as I can. Is there an IRC channel/IM app you guys use for communication? If so, I'd appreciate it if you could PM the info.

ROM ❯ PIXEL 3a ❯ UNOFFICIAL ❯ ProtonAOSP 11

ProtonAOSP • Pixel 3a
Android 11 ROM​
ProtonAOSP is a minimal custom Android 11 ROM focused on UI/UX and performance, with a touch of privacy.
Instead of customization it is focused on more smoother experience.
Installation
1. Unlock Bootloader
2. fastboot flash boot boot.img
3. Reboot to factory and factory reset
4. adb sideload rom.zip
5. Reboot​Note:- Rom already comes with gapps included so no need to flash them
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Download Here​Known issues
No eSIM support(I plan to add in next build)
Join the Telegram group for support
Kernel source code
ROM source code
This is just a side project, I may or may not maintain it in future.
A huge thanks to @kdrag0n for the amazing rom and the work done on this rom.

Reserved

I was just thinking how much I'd love to see this for the 3a.
Couple of things though;
1) Where's the device tree source and vendor blobs?
2) Its unfortunate that you baked in the google crap, one of the great things about custom builds is to get rid of that.

96carboard said:
I was just thinking how much I'd love to see this for the 3a.
Couple of things though;
1) Where's the device tree source and vendor blobs?
2) Its unfortunate that you baked in the google crap, one of the great things about custom builds is to get rid of that.
Click to expand...
Click to collapse
1. Soon I'll push source
2. I do have microg build for sargo as it is my main device, but not for bonito, so I did not post here on xda, if you want it join the support link group in the thread. Regarding google crap, for some users flashing gapps externally had less fluid experience so I did it.

I hope soon will be very soon, since I'm only interested in building myself anyway.
Have you spoken to @kdrag0n about adding in your source and making this "official"?

96carboard said:
I hope soon will be very soon, since I'm only interested in building myself anyway.
Have you spoken to @kdrag0n about adding in your source and making this "official"?
Click to expand...
Click to collapse
Device source
Vendor Source
Note:- I have few extra proprietary stuff added in vendor for Google Fi and stuff to work for users out the box which lineage does not have added in their vendor, so if you really want less vendor blob use lineage vendor. It will work without any issue, I think kdrag0n also uses them.
Regarding official builds, I don't have the same infrastructure as him(reason why I only posted gapps build here, it takes lot of time to maintain both gapps and non gapps build) nor the time to maintain it officially. as said in thread, this is my side project which I thought to share it with community. If things work well in future and I feel like doing it official, I may ask kdrag0n. Also idk if he is accepting new device as he is maintaining all the official devices alone by himself.

FoxA said:
Device source
Vendor Source
Note:- I have few extra proprietary stuff added in vendor for Google Fi and stuff to work for users out the box which lineage does not have added in their vendor, so if you really want less vendor blob use lineage vendor. It will work without any issue, I think kdrag0n also uses them.
Regarding official builds, I don't have the same infrastructure as him(reason why I only posted gapps build here, it takes lot of time to maintain both gapps and non gapps build) nor the time to maintain it officially. as said in thread, this is my side project which I thought to share it with community. If things work well in future and I feel like doing it official, I may ask kdrag0n. Also idk if he is accepting new device as he is maintaining all the official devices alone by himself.
Click to expand...
Click to collapse
Thank you very much. I'll give that a go

Hi, just checking if there is any development planned for this one? Looks to be interesting ROM for daily use.

cichy63 said:
Hi, just checking if there is any development planned for this one? Looks to be interesting ROM for daily use.
Click to expand...
Click to collapse
sorry, I don't have the device anymore.

The link download is not working, please update it

cichy63 said:
Hi, just checking if there is any development planned for this one? Looks to be interesting ROM for daily use.
Click to expand...
Click to collapse
Here's a current source.
I don't know if it's trusted, or who the maintainer of this unofficial build is though. Just found it via telegram.
ProtonAOSP - Browse /ProtonAOSP at SourceForge.net
sourceforge.net

Nice one. It's really handy to be able to revive old, unsupported devices like the Pixel 3a, which is a perfectly usable phone and can be picked up for next to nothing.
Some of us don't care about de-googling our phones and really just want to extend their lifespan with security updates, so having gapps baked in to ProtonOASP is really nice. Especially when we're just trying to help out our non-technical friends get a bit more life out of their old phones. A consistent, familiar user experience is all they really want.
I was wondering though: Does your build (or any build of ProtonOASP) come with verified-boot signatures so that the device's bootloader can be locked down after the ROM is installed, or is CalyxOS the only option for this?
Unfortunately, Calyx are very puritanical when it comes to de-googling, and microG is just a terrible substitute for interacting with Google services. I tried it on the Pixel 3a, and it doesn't even sync the contact list from your Google account. My non-technical friend was not impressed.

GrapheneOS still has builds up for 3a, however new builds were terminated as of February. While it doesn't ship with gCrap preinstalled, installation is trivial as they've built a compatibility layer to make it work correctly (and much MUCH more securely) as user-installed software, which you can install from the program "Apps".

[ROM][DISCONTINUED] LineageOS 18.1 for judyp

This is the LineageOS 18.1 for LG V35
Download
MediaFire
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Instruction
1. Flash V30c for LM-V350N
2. boot OrangeFox --> fastboot boot ofox_judyp.img
3. Goto wipe -> format data -> type yes --> reboot to fastboot --> redo step 2
4.Copy the LineageOs zip to phone and flash it
5. Optional: Flash GApps and Magisk (Untested)
6. Reboot to system
Thanks To/Credits
@EmanuelCN
Sources
GitHub - EmanuelCN/android_kernel_lge_sdm845
Contribute to EmanuelCN/android_kernel_lge_sdm845 development by creating an account on GitHub.
github.com
GitHub - TatsuyaSou/android_device_lge_judyp: Device tree for judyp (LG V35)
Device tree for judyp (LG V35). Contribute to TatsuyaSou/android_device_lge_judyp development by creating an account on GitHub.
github.com
GitHub - TatsuyaSou/proprietary_vendor_lge
Contribute to TatsuyaSou/proprietary_vendor_lge development by creating an account on GitHub.
github.com
GitHub - TatsuyaSou/android_device_lge_sdm845-common
Contribute to TatsuyaSou/android_device_lge_sdm845-common development by creating an account on GitHub.
github.com
GitHub - EmanuelCN/android_device_lge_hardware
Contribute to EmanuelCN/android_device_lge_hardware development by creating an account on GitHub.
github.com
GitHub - TatsuyaSou/android_device_lge_common
Contribute to TatsuyaSou/android_device_lge_common development by creating an account on GitHub.
github.com
This is my first rom, if you find a bug please tell me.​

Great news indeed!
The LM-V350N variant was already mentioned, what about the other
Spoiler: LG V35 variants
LM-V350ULM
LM-V350AWM
LM-V350EM
LM-V350EAW
- are they supported yet?

Nexus-3 said:
Great news indeed!
The LM-V350N variant was already mentioned, what about the other
Spoiler: LG V35 variants
LM-V350ULM
LM-V350AWM
LM-V350EM
LM-V350EAW
- are they supported yet?
Click to expand...
Click to collapse
Hi,
The rest don't have Android 10 and you need to flash korean firmware (v30c) via LGUP. On 9, you'll get a bootloop.

Kyrimeas said:
Hi,
The rest don't have Android 10 and you need to flash korean firmware (v30c) via LGUP. On 9, you'll get a bootloop.
Click to expand...
Click to collapse
Would this work for my device?

Andy2004 said:
View attachment 5388313
Would this work for my device?
Click to expand...
Click to collapse
If it's a korean a10, it'll work.
I know at&t has a10 too but I don't have how to test it.

Any bugs?

misha67 said:
Any bugs?
Click to expand...
Click to collapse
Usb Tethering and VoLTE are not working.
EDIT: The fingerprint is not working
I'll try to fix it

非常感谢，我会看着你的

Auto Brightness and Network have question.Looking forward to your repair

If I flash this, will I still be able to go back down to Android 10 with LGup?

thandlovsky said:
如果我刷这个，我还能用 LGup 回到 Android 10 吗
Click to expand...
Click to collapse
thandlovsky said:
如果我刷这个，我还能用 LGup 回到 Android 10 吗？
Click to expand...
Click to collapse
哦f course

2535449410 said:
哦f course
Click to expand...
Click to collapse
of course

thandlovsky said:
If I flash this, will I still be able to go back down to Android 10 with LGup?
Click to expand...
Click to collapse
of course

вin thank you for your work! I have 350n - is this firmware suitable for him? what does not work?

Wow, this release really is surprising
Has anyone tried crossflashing to korean formware then installing this ROM?
does it fix some of the issues that can come from the crossflash

电池容量为3000

I take it your V35 has to be bootloader unlocked correct?

X-Nemesis said:
I take it your V35 has to be bootloader unlocked correct?
Click to expand...
Click to collapse
Yes, it must be unlocked because you will not be able to enter recovery

k.stahanov73 said:
вin thank you for your work! I have 350n - is this firmware suitable for him? what does not work?
Click to expand...
Click to collapse
VoLTE, usb tethering are not working. Fingerprint has been fixed in the latest version. Sometimes the screen does not turn on when AoD is on.
ghylander said:
Wow, this release really is surprising
Has anyone tried crossflashing to korean formware then installing this ROM?
does it fix some of the issues that can come from the crossflash
Click to expand...
Click to collapse
I have v350awm but I had no problems with korean firmware.

Thank you very much for making this rom!
I can confirm it working with Magisk 23.0 and GAPPS (MindTheGapps-11.0.0-arm64-20210412_124247)
and even Xposed is working!
(EdXposed from Magisk repository - Riru_-_EdXposed-v0.5.2.2_4683-master(4683) + riru-v25.4.4-release
Only issue i have noticed is that waking up the phone
- some issue with Always On Display maybe, sometimes screen remains black,
need to push power button several times,
for now i just disabled AOD and will see how it will function.
I love that the rom adds names of apps to the file name of screenshots, like in MIUI,
very useful for quick finding screenshots
Wi-Fi perfect, BT perfect,
pity that the LineageOS recovery is, well, inferior to TWRP / OrangeFox,
but, overall i think this ROM is so good it will be as my primary usage Android
Oooh, i miss the camera from LG, miss the good touch focus, is there any port of that LG camera for v35 - this Lineage?

Development [CLOSED] LineageOS 20 BETA for OnePlus 9Pro LemonadeP Android 13 - NOV. 12, 2022

This is a BETA build for NEW Lineage 20, Android 13. Possible bugs may be present. Let me know!!
MSM to Android 11 if you want to start clean, then flash either CrDroid or Nameless c63 firmware to begin.
This is based on the Android Open Source Project. It can be used without any need to have any Google application installed. It does still include various proprietary hardware-specific code.
Gapps must be flashed separately and are not included in this ROM.
All the source code is available in the Github repo here.
Thanks go to Github and LineageOS for their source code and device specific code. I couldn't have built this without it!!!
The ROM uses the LineageOS source code, device specific code and proprietary blobs. I made other minor changes and used compression to lower the file size of the ROM, creating more space in the internal storage with minor reduction in performance. Updated daily with minor changes.
You may use another recovery however you will receive a signature verification error. You can simply ignore and choose yes and flash it anyway. You will need to do this with gapps and magisk.apk to root.
DOWNLOAD ROM & GAPPS HERE
#1 REBOOT TO BOOTLOADER
#2 FACTORY RESET: fastboot -w
#3 REBOOT TO RECOVERY
#4 SIDELOAD ROM IN RECOVERY
adb sideload lineage-20-20221112-UNOFFICIAL-lemonadep.zip
reboot recovery
adb sideload lineage-20-20221112-UNOFFICIAL-lemonadep.zip
reboot recovery
#5 SIDELOAD GAPPS: NikGapps-core-arm64-13-20221109-signed.zip
#6 REBOOT TO SYSTEM
#7 REBOOT TO LINEAGE RECOVERY IF YOU WISH TO ROOT
SIDELOAD MAGISK.APK
adb sideload magisk.apk
#8 REBOOT TO SYSTEM
Updates available in built in updater. settings, system, updater.
You can change preferences to check for updates daily.

Sounds interesting......even though I love stock, this is tempting!

TheGhost1951 said:
Sounds interesting......even though I love stock, this is tempting!
Click to expand...
Click to collapse
I'm with you man. I'm on stock too and Lineage is my least favorite ROM. I'm just trying to help others who like it and diagnose and fix a annoying bluetooth bug.

Is possible to post screen shots. plz
OOS camera included. And Oneplus setting

break.cold said:
Is possible to post screen shots. plz
OOS camera included. And Oneplus setting
Click to expand...
Click to collapse
Come-on guy, do your research like the rest of us here.....Google, bing, xda....search. put forth the effort and the reward is greater

What (and where) are the changes you made to Bluetooth connectivity? Does this solve the longstanding problem of "stuttering" audio on Bluetooth phone calls?

MJPollard said:
What (and where) are the changes you made to Bluetooth connectivity? Does this solve the longstanding problem of "stuttering" audio on Bluetooth phone calls?
Click to expand...
Click to collapse
I don't have it listed anywhere. I dumped the firmware from stock and pulled the bluetooth and implemented it into this. I tested it and didn't notice any issues but I went back to stock. Lineage is not my thing. All I can say is to test it out and report any issues and I'll continue to work on any problems that may exist.

09/27 update posted

10/01 update posted

TheSayaMan said:
10/01 update posted
Click to expand...
Click to collapse
Changelog?

Beytullah61 said:
Changelog?
Click to expand...
Click to collapse
Changes in regards to bluetooth connectivity only.
LineageOS/Bluetooth at main · MikeSaya1/LineageOS
Contribute to MikeSaya1/LineageOS development by creating an account on GitHub.
github.com

10/09 update posted. More bluetooth improvements.

TheSayaMan said:
10/09 update posted. More bluetooth improvements.
Click to expand...
Click to collapse
10/15 posted. October security patch.

Thread changed from LineageOS 19 Android 12 to LineageOS 20 BETA Android 13

Can you build for oneplus 9?

imbasador said:
Can you build for oneplus 9?
Click to expand...
Click to collapse
Yes, I'm working on it

Because of the lack of interest on this. This thread will be closed.

Thread closed at the OP's request.

Question Official Lineage OS

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.