Development [ROM][OFFICIAL][lemonade][13] LineageOS 20

[Not-Aus]

super_empty.img , vbmeta.img in which step should I use and how ?

https://wiki.lineageos.org/devices/lemonade/install

 

[mattie_49]

super_empty.img , vbmeta.img in which step should I use and how ?

You don't use these images to flash build whatsoever. Download boot,vendor_boot,dtbo images and of course latest build. Be on latest op stock firmware. Flash first 3 partitions in fastboot. Reboot recovery ,factory reset. Sideload build .

 

[shadabkiani]

super_empty.img , vbmeta.img in which step should I use and how ?

Just ignore them. The important stuff is boot.img, vendor_boot.img and dtbo.img.

You can use super_empty.img to wipe the super partiton from a fastboot command if you want, but you don't need to. Similarly, vbmeta.img is used to diable verity, but not needed.

 

[D7M]

thx guys

 

[Baerbeisser]

Uhm, all links to firmware on https://lineageosroms.com/lemonade/ are either "not found" or "403 forbidden".

 

[shadabkiani]

Uhm, all links to firmware on https://lineageosroms.com/lemonade/ are either "not found" or "403 forbidden".

This is not the official site. And all the builds there are so outdated.

The official link is in the first post. Here it is again:

LineageOS Downloads

download.lineageos.org

Secondly, separate firmware flashing is not needed anymore. The latest builds' ROM zips include the firmware. Just flash the boot.img, vendor_boot.img, dtbo.img from bootloader. Then boot to recovery. Wipe data/factory reset. Then sideload ROM zip. After that, if you want to install GApps as well, then you MUST select reboot to recovery, then sideload GApps zip.

 

[Baerbeisser]

Thanks!

 

[TimmyP]

Found a bug. Probably a bigger issue, but this re-triggers it consistently. Its really strange so bear with me:

Set up screen cast to your tv, just so you know it works. Stop screen cast. This is not part of the bug, it just involves screen casting being triggered by something.

-Go to settings, system, updater (make sure its not in your recents, need to be "fresh").
-Click the back button in the upper left, then again, then click in the search field... this enables screen cast for some reason, at least on my phone, every-time (icon on status bar). I'm pretty sure there are a few other things that start it, but this is the one way Ive found to consistently reproduce this strange issue.

OP9 latest LineageOS btw.

 

[TimmyP]

FYI this rom has charge limit now.

 

[CaptainElwood]

Has anyone experienced that after a few hours on non-usage (e.g. at night) access to Google accounts is running into trouble?
Play Store, Google, ... are not able to access/show your Google data, like if you didn't log-in.
After a reboot everything works well again.
I tried MindTheGApps and BiTGApps.
I'm on the latest nightly, but have had that problem since I've switched from LOS 19.1 to 20. Tired factory resets too.

That sounds like the bug they actually pulled the builds for this phone until it was fixed. What build are you on?

Unlike the previous few comments, I am on the latest build with zero issues. I didn't root and everything works great, including video calls (use MS Teams for work). The only thing that isn't great is that I feel like the automatic brightness sensor is delayed, it eventually darkens the screen but not before it blinds me.

 

[downhere]

That sounds like the bug they actually pulled the builds for this phone until it was fixed. What build are you on?

Unlike the previous few comments, I am on the latest build with zero issues. I didn't root and everything works great, including video calls (use MS Teams for work). The only thing that isn't great is that I feel like the automatic brightness sensor is delayed, it eventually darkens the screen but not before it blinds me.

... that was in January... and got fixed.
I'm on current build, no issues.

 

[shadabkiani]

That sounds like the bug they actually pulled the builds for this phone until it was fixed. What build are you on?

Unlike the previous few comments, I am on the latest build with zero issues. I didn't root and everything works great, including video calls (use MS Teams for work). The only thing that isn't great is that I feel like the automatic brightness sensor is delayed, it eventually darkens the screen but not before it blinds me.

You replied to months old post... There had been tons of posts after that, and that issue has long been fixed. It was called binder issue.

 

[NewDayRising]

Regarding charge limit, is anyone experiencing this? https://gitlab.com/LineageOS/issues/android/-/issues/5965

 

[TimmyP]

Yeah that's my report haha.

I also just filed a new one because stereo does not reverse when you flip the phone in landscape.

 

[shadabkiani]

Regarding charge limit, is anyone experiencing this? https://gitlab.com/LineageOS/issues/android/-/issues/5965

I'm not on LineageOS currently, but on crDroid right now, however, I thought this happened to me too. I set to 70% and battery charging stopped at it. But when I started using, it was stuck at 70% for quite a long time despite prolonged usage. I thought it was just placebo, but now I know it was a bug indeed. That happened when I put the phone on charge during the night. But didn't happen again. Maybe battery is slowly charging after that limit, but doesn't show up in percentage.

 

[NewDayRising]

I'm not on LineageOS currently, but on crDroid right now, however, I thought this happened to me too. I set to 70% and battery charging stopped at it. But when I started using, it was stuck at 70% for quite a long time despite prolonged usage. I thought it was just placebo, but now I know it was a bug indeed. That happened when I put the phone on charge during the night. But didn't happen again. Maybe battery is slowly charging after that limit, but doesn't show up in percentage.

Whatever it's doing on wireless, it's consistent, because rebooting holds the same number set in charging control whereas that isn't always the case with apps/modules like Advanced Charging Controller. Even apps like DevCheck show the same number. I think trickle charging on wireless is the culprit. The only time I use wireless charging is at night. Or planned to, before this bug, since ACC had issues with wireless charging, too.

Were you using LineageOS when you had the issue, or crDroid? Stock kernel? (Stock as in the kernel with the ROM, or, say blu_spark?)

 

[TimmyP]

Are we sure the phone has charging control support on its wireless charging controller? I could not get ACC to work with it, and I couldn't do it "the manual way" with a custom Magisk module (and Tasker). Both attempts worked fine with wired, and wired works fine in Lineage as well.

Can someone, at least for me since Im relatively new to this phone still, confirm that we have control on wireless? I never tested on stock or other roms. Went straight to Lineage.

 

[shadabkiani]

Whatever it's doing on wireless, it's consistent, because rebooting holds the same number set in charging control whereas that isn't always the case with apps/modules like Advanced Charging Controller. Even apps like DevCheck show the same number. I think trickle charging on wireless is the culprit. The only time I use wireless charging is at night. Or planned to, before this bug, since ACC had issues with wireless charging, too.

Were you using LineageOS when you had the issue, or crDroid? Stock kernel? (Stock as in the kernel with the ROM, or, say blu_spark?)

Currently I am on crDroid, and ACC isn't working 100% well either. I had been using ACC since forever, you know. But recently, when this charging control feature is introduced into custom ROMs for OnePlus 9, ACC isn't doing its job perfectly. I use ACC v2022.2.22.1 because the later versions are bugged. I keep the setting to 65% max charge with 50s/10s charge/pause ratio. It has always worked for me, but with charging control feature (even if it's off) in ROMs now, it doesn't work correctly. I always use USB voltmeter with my charger, so I can physically monitor the actual power being delivered; and not from some phony app like Ampere with incorrect data. I can tell you that charge/pause ratio works fine. My charger charges at 17W for 50s, then pauses for 10s at less 1W. Previously, charging would stop at 65% and then go to less than 1W for direct AC usage; battery wouldn't charge beyond 65%. But now, even though it still does the same behavior of charge/pause until reaching 65%, but the difference is that after 65%, charging would be less than 1W and it would keep on trickle charging. For example if I keep it plugged in overnight, it would charge to maybe like 75% or 80% or more.

In short, ACC isn't working quite right with the charging control feature in ROMs. With charging control off, ACC doesn't seem to stop charging, and it would keep on charging beyond max percent set, although very slow after that, less than 1W. I would try a different and later ACC version and let you know.

Edit: Sorry I missed your question. I was on some other ROM, can't remember. I haven't used LineageOS in ages, but the fearures in most other ROMs are based off of LineageOS so I think issues are related. I don't use custom kernels either. Currently I'm on crDroid. I also don't have wireless charger. I'm just sharing my experience my wired charging, maybe that would help you guys better understand the issue.

 

[shadabkiani]

Are we sure the phone has charging control support on its wireless charging controller? I could not get ACC to work with it, and I couldn't do it "the manual way" with a custom Magisk module (and Tasker). Both attempts worked fine with wired, and wired works fine in Lineage as well.

Can someone, at least for me since Im relatively new to this phone still, confirm that we have control on wireless? I never tested on stock or other roms. Went straight to Lineage.

What ACC version are you using?

 

[NewDayRising]

Currently I am on crDroid, and ACC isn't working 100% well either. I had been using ACC since forever, you know. But recently, when this charging control feature is introduced into custom ROMs for OnePlus 9, ACC isn't doing its job perfectly. I use ACC v2022.2.22.1 because the later versions are bugged. I keep the setting ...

Okay, this is a detailed level of use far and above what I was used to. I came from a Mi Mix 2s using IPC to set charging percentages, which worked both wired and wirelessly without issue, but when I moved to the OP 9, IPC had become abandonware and wouldn't install. I used the version of ACC referenced above, but wireless charging was always flaky, or never even worked, as far as I remember. At least on wired charging, the new feature is solid and consistent. Beyond that, I don't know where to look for a resolution.

Thanks for all the additional information.