yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S23 Ultra] blackhawk:
Double box it, FedEx or UPS. Pack, tape well.

Take pictures from all angles right before boxing of phone. Insure it.
[Samsung Galaxy S23 Ultra] theboz1419:
It was prepaid with USPS, and they asked me if it was a phone and I said it was. Next time I will keep my mouth shut, lol.
[Samsung Galaxy S23 Ultra] theboz1419:
I was able to get T-Mobile to send me a Ground return label after calling them and actually had an awesome lady work with me to get it corrected, as the T-Mobile store could not get anything done(he tried his best)
[Samsung Galaxy S23 Ultra] maddoggin:
Just mailed mine out today using tmobile label. No issues at all. Texas!
[Samsung Galaxy S23 Ultra] theboz1419:
I think she had policy mix up in the brain syndrome.
[Samsung Galaxy S23 Ultra] cledee:
Do you have a battery label on the box?

I was able to send mine out via USPS with no issues. Also your USPS tag when it gets scanned will determine the shipping speed so whoever is telling you that doesn't know what they are talking about.
[Samsung Galaxy S23 Ultra] jcsww:
USPS took mine no problem. It went air from Virginia to Texas using the T-Mobile prepaid label.
[Samsung Galaxy S23 Ultra] Talderon:
Since it was a pre-paid, printed shipping label, I skipped the counter and just dropped it into the outgoing box AT USPS (not just a random drop box). Mine was returned and T-Mobile stated it was all good.
[Samsung Galaxy S23 Ultra] jcsww:
I always make sure I hand it directly to someone and get a receipt it was dropped off.
[Samsung Galaxy S23 Ultra] Talderon:
When you print the label, you also print a "receipt" with the package details and tracking number. I used this to verify that it was shipped, delivered and accepted.

The RMA Number, Tracking number, IMEI, Trade Details and everything else you need is all there. I didn't feel it was worth standing in line to get the same information that I already had.

I did realize it was important to drop it off directly at USPS package drop-off rather than in my mailbox or public drop-off location (Many Ace Hardware stores have a USPS location in them for basic services, I skipped them too).
[Samsung Galaxy S23 Ultra] theboz1419:
I got this on another website. She knew what she was talking about, unfortunately.

USPS issues new shipping requirements for used electronics and other hazardous materials - Postal Times

The Postal Service has issued new requirements for shipping used electronics and other hazardous materials. Effective June 6, mailers must separate all material requiring hazardous markings or labels into identifiable containers.

postaltimes.com

"Additionally, pre-owned, damaged or defective electronic devices — such as cellphones, laptops, tablets — that either contain or are packed with lithium batteries must be mailed by surface transportation using Parcel Select Ground or USPS Retail Ground, Parcel Return Service or Ground Return Service."
[Samsung Galaxy S23 Ultra] hand-filer:
Makes sense to me. A lithium battery igniting at 30,000" could be crazy scary.
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] leo_97:
Installation Instructions​

Remember, making a backup of your data before proceeding is recommended

If you are coming from Stock ROM, please refer first to the instructions below:

Install LineageOS on kuntao

If you are coming from astridxx previous build (aka lineage-19.1-20220822-UNOFFICIAL-kuntao) or my initial build (aka lineage-19.1-20230222-UNOFFICIAL-kuntao) or any version of LOS18.1 or below, you

must

perform a clean flash. Clean flash instructions:

0- Make a backup (optional, but recommended)

1- Reboot to recovery

2- Format data (will delete all your data!)

3- Reboot to recovery again

4- Wipe > Advanced Wipe:

- Dalvik

- System

- Vendor

- Data

- Cache

- Internal Storage (optional, but recommended)

5- Flash ROM ZIP, Gapps, Gapps add-ons, Magisk add-on, etc

6- Reboot to system

7- Wait until it boots for the first time (may take some minutes)

Update Instructions​

NOTE: Dirty flash from any of the aforementioned builds is

not

supported, device trees were changed. You have been warned!

For updating from one of my builds to another (aka dirty flashing), please do the following:

1- Download ROM ZIP and copy it to the phone

2- Reboot to recovery

3- Flash ROM ZIP

4- Clean cache

5- Reboot to system
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] leo_97:
ROM Screenshots​

Attached below. Others are available here.
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] leo_97:
February 27th 2023 Release​

Changelog:

- Sync latest LOS sources

- Device Tree change: Use old A12L dt instead of los

- Add Lenovo Parts menu (fp gestures, USB fast charge, in-call audio gain, screen kcal)

- Updates phone vibration strength

- Add fix to device deep sleep issue

- Many more changes

Download URLs: GDrive | SF

Dirty flash still

not

supported (tree changed), please make a clean flash
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] Sutcliffe9:
Thank you so much for keepng Lineage alive, its very much appreciated.
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] en666:
@leo_97 thank you for this new build! Installed it straight away and now the phone is running since then and also, I've flashed with battery at 67% and atm, after a quite hard usage to test out the new features, I'm on 13%. Basically, so far so good!

p2a42, twrp 3.7, rooted, unencrypted
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] bidulez:
Thank you @leo_97 !

I was frustrated that Lineageos 18.1 was no longer maintained when I saw this update!

It's amazing :-)

To all users and developers who tested and created this ROM, is it time to switch on this version ?

Or is it better to wait ?

For example, automatic update is possible after install ?
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] utwer:
No
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] leo_97:
You are welcome :)

If it's time to switch, I believe it's a matter of personal decision. Maybe you could wait the next build and then decide...

If with "automatic updates" you mean OTA updates, then the answer (as already pointed out by @utwer ) is no. But once the trees are stable enough, I hope every user will be able to just update to the newer versions flashing ROM ZIP through TWRP (just like it's done on LOS18.1)

BTW, IDK if you already saw it, but we are maintaining a monthly build of LOS18.1 which you can download from here. The source tree used there is far more tested (as it's older) than this one. Anyway, except by the encryption thing, you shouldn't have any problems using this LOS19.1 ROM as our amazing developers made an excellent job here.
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] Zdeslav:
Reg, Ive installed it and I may say it is quite good. Not tried to root it yet. Dont have direct problems with ROM and functionality, for me everything works. Camera, Location, GSM, Data, WiFi. With developer options I've turned off Animation scale on three options to OFF, and is good. Stable reliable.

MindTheGapps-12.1 works every app from Google, Phone, Contact, Gmail, maps...etc...

What I need root mostly is for Call recording (Skvalex) and Viper4Android.

Some words about twrp-3.7.0_9-0-kuntao.img,

With this I have only problems, so far I lost a few backups and I need to install it all over again a few times allready. Disappointed very. I can't rally on this when I make a nandroid ba.ckups.

Also lost backups for LOS18.1 and I am been very pis....ed off. Error 255 on System recovery, other Data, Boot, EFS, Vendor, etc.. recovery is good.

So I've installed OrageFox for Kuntao. Tried several backups to restore already and I may say I am very satisfied. Puh

What is on my mind, when I installed a Magisk 25.2, no matter of LOS 18.1 or 19.1 with very few modules, after 7-8 reboots I've got boot loops which is beyond repairable.. Try to remove modules in TWRP in file manager, uninstall whole magisk, no way, but what it is seems that DATA got corrupted some how, everytime.

There were also installed TWRP mentioned above.

Now I am with OrangeFox and I will try tomorrow to Root it and see is there any connection between Magisk and recovery software (OrangeFox or TWRP).

Reg
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] MKbis:
Tried quickly this ROM yesterday. In general all working, but didn't test much.

Few feedbacks:

-Scaler for brightness level is weird, very different from the original Lenovo roms. Anyway, not really important, but something that I noticed.

-Missing haptic feedback when using the fingerprint reader as a gesture button. Again, not critical, but I am really accustomed to it and thus I noticed immediately.

-Missing haptic feedback intensity regulation, or could not find it. It's there for general call/notification vibration, but if I remember correctly lineage could also change haptic.

Impressed that you could integrate also some lenovo features, even if of course not all of them :)

If you want me to test something more specific, please let me know. Ah, my model is the 4 GB/ 64 GB combination.

Cheers!
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] eried1:
So for 18.1 we can just flash the newer versions via TWRP and do not have to reinstall the entire ROM?
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] Zdeslav:
So,

Resolved issue of bootloops:

after you install SU like Magisk, and wan to freeze apps by Titanium Backup or Neo-Backup, Apps which causes bootloops are ROM's Phone and Massages (In my case, for 16.1, 18.1, 19.1), I freeze Audio.apk who need to be shutdown for Viper4Android app who takes audio management and freezing is OK.

But Phone and Massages which are frozen cause bootloops, so you need to return from freeze state somehow in TWRP or OrangeFox with file management or revert backup. Revert backup is easier :).

Camera; found issue when suddenly is out of work and cannot be connected to app. Also have problems with video cast Skype, Viber, Whatsapp, Telegram video is frozen. Hardly switch in Camera app from Camera mode to Video mode and vice-versa.

Clock & Info; missing dock icons and info, can't "capture" moment for reason when they disappear but after a while all is returned again.

View attachment 5867565

P2oggle, left switch button work okey in form of 0.4 version.

Reg,

thanks on the development for this 19.1 ROM.
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] leo_97:
Hello,

I've been using this ROM as my daily driver and couldn't confirm this camera bug, could you please give a few extra details? I tested on Telegram app. Which version are you using? The Play Store's one or the one from Telegram's official website? Did you give the app "While using app" permission or "Ask every time" permission for camera? Are you sure the QS Tile "Camera access" is activated (available) when the mentioned bug occurs?

Regarding the Clock widget, yes, there's a small glitch and I'm not sure on how to fix it, if it doesn't load at all, a system reboot should fix it.

P2oggle v1.2 is 100% working as far as I can tell, so you guys can try it too if you want.

I'm not sure if it's possible to "fix" the brightness slider.

If with "haptic feedback" you mean the phone vibration, you can just adjust it to your liking in Settings > Lenovo parts > Vibration strength, it should affect fp reader too, dunno if it affects call vibration but IFAIK it should.

Regards
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] Zdeslav:
Yes on latest Telegram app from web site, tried with Google Meet, Whatsapp, Viber.., always breaking connection with API/drivers. Yes I gave all permissions to Camera. If I am not giving permissions for camera, I have always noticed to confirm what I am giving, so I am excluded from this solution. And clean storage and cashe from app regular but not prevail.

But, in a while after installed a new ROM without giving SU/Root I noticed this behavior, right after I wrote earlier post up. My bad :).

Choppy startup of camera, can't easily transfer from video 2 camera and vice-versa, so I tell to my self to test intensively.

Yes after a while it is returned back without reboot. weird.

Didn't know about P2oggle v1.2 app, thx
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] leo_97:
March 29th 2023 Release​

Changelog:

- Fetch latest Device Tree sources

- Update LOS components webview & zlib

- Sync latest LOS source

- Merge March security patch

- Many more changes

Full change log available on the bottom of this post

Download URLs: GDrive | SF

Note: Please, before flashing, carefully read the instructions from the 3rd post above to avoid breaking your system.

Enjoy!
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] Zdeslav:
Big Thank you for this release. Will try it. - test
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] pirogof:
Great job, dude.

Previous versions had some buggy charging driver that left a wakelock running after each charging, and u had to restart phone each time or leave it to slowly drain battery by not going to sleep.

Somehow this problems seems to be gone in your build and that is awesome.

I've been using the build for about 2 weeks now and so far everything seems to be working fine.
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] leo_97:
April 09th 2023 Release​

Change log:

- Fetch latest Device Tree sources (lots of changes)

- Update LOS components:

-- lineage: Track the FMRadio App and dependencies

- Sync latest LOS source

- Many more changes

Full change log available on the bottom of this post

Download URLs: GDrive | SF

Note: Dirty flash is

unsupported

for this build, please make a clean flash

Enjoy!
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] bidulez:
So @leo_97 , I switched from the last official build (18.1 unrooted/encrypted) to your march build (19.1 rooted with Magisk v25.2 unencrypted + MindtheGapps + FDE.ai balanced/advanced mode for battery saving), here are my impressions after one week.

This build is more responsive with all applications, thank you for your time, without forget all dev involved 😉

What do you suggest :

- as save/restore app ?

To easy switch from build to another (after tree change for example).

I found Neo backup / Swift backup but I don't test them, or maybe full backup with TWRP, just in case

- for encrypt ?

Last time, encrypt counter blocked at 00:00:20, so I rebooted after waiting 1 hour (maybe Magisk doesn't like the process ?)

I tried uninstall/reinstall Magisk, without success.

I had to clean and flash build, and stay unencrypted, to avoid an other system break.

😇
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] Zdeslav:
Reg,

found to Neobackup been very good and easy to backup, restore, it is much slower in my case than Titanium, but we all know the history. It has a lot of functionality, automatic backup of newly installed apps, disable, enable...really good, but slow. I don't mind!

So only problem in my case was to disable APPS as they can't be disabled in A10..A11, A12..If you disable system app in Neobackup or any other app, the main system became unstable and unresponsive. So only good solution I found with coexistence was DE-Bloater from Git hub.

Some times with Magisk I get non-responsive post at boot "Phone is starting", and it is in connection with Encrypting system and Magisk, but I am non-eble to solve this eather in 18.1 and 19. LOS..

Trying to solve this as I am working with backups a lot. But 2/3 times can't make a good revert. Always Phone is starting an than after few reboots a crash. Connected with ADB logcat at boot, but except Google maps --> Programpackager didn't find, or I better can say I don't know to recognize what is causing the problem. my bad. Deinstalled Maps...nothing same problem...

Learning...

treg
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] leo_97:
I'm glad to hear that you are having a good experience.

Unfortunately, as noted by @Zdeslav on that other message, the TWRP backups are broken, try to follow the tips from his last message and please report back any successful method. The encryption should work if you clean flash the ROM after a data format, then try to encrypt. I tested this and the encryption was finished in a few minutes with almost empty phone storage (maybe you copied your data back to the phone prior to starting the encryption process? If yes, then, IFAIK, the process will take longer as it will be needed to encrypt more files).

Just for the sake of curiosity, please, do you know if this behavior happen if you install ROM without Magisk?
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] Zdeslav:
No, only with help of Magisk and Encrypted storage. without encrypted mode non Locked display even with Magisk, very rare.

Magisk+Encrypted storage (Data)+Lock (PIN/Swipe lines...) = "Phone is starting" always is on after Reboot or Shutdown. So it is non safety mode, you never know when is gona go in to the bootloop. Pure luck, so I made immediately Backup with Orange Fox, only (System, Data, Boot),

and when I returning just Wipe those two (Boot it is not necessary), do not Format Data option or it will pass to around 6 min. encrypting storage option, ((if you do it--->) next, let to be Encrypted, you need also to remove pin lock in /data/system/locksettings.db with Orange fox file manager, than reboot.

First I taught it is a Magisk modules or plugins, but it is not. In other factory GUI's happens if you disable apps with A10+ (Neobackup or Titanium backup which I tried).

Edit: Important

If you have mayor problems to return backups do this - Orange Fox / have problems with TWRP:

1. Always have full ROM LOS 18.1 or 19.1 depends what is installed SD card

2. Backups - of course😉 (Need Data, System and Boot to be backed up already)

3. Wipe all, Format data ! except SD Card !

4. Install whole ROM from ZIP

5. Restore Data & System & Boot !

6. Probably will do Encrypting system, let it do. Automatic Boot to System / can't be stopped.

7. And.... you will probably have missing apps on main Display, don't warry !

(It is option only if you setup already Locksettings for display !!!!!!

Return to Recovery, Flash Data again ! Than, while you in the Recovery do:

8. Remove /data/system/locksettings.db (it is different encryption keys) will not work after

Encrypting system, don't reboot yet

9. Flash Magisk 25.1 or Magisk 26.1 (you can upgrade later)

Magisk 26.1 and Viper4Android latest:

You can't install V4A, always stall on 11% or 22%, so no go in my case, tried 3 times.

Uninstall Magisk 26.1 from App !!!! Reboot and go to Recovery again

Than install 25..1 from Recovery (ZIP)

Boot, If you ask to install again, do it, or apk... just to work properly

Than install V4A, other modules, configure for you needs...

Than upgrade to Magisk 26.1 !!

Those ROM's LOS A11+ (e.g. LOS 18.1+)+ is memory hungry so medium quantity startup apps are welcomed.

Thank you for developing this ROM !!
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] leo_97:
April 19th 2023 Release​

Change log:

- Fetch latest Device Tree sources:

-- sepolicy: Silence tracingproxy_service neverallow denial

-- sepolicy: Allow system_app to access storaged via IPC

- Sync latest LOS source

- Merge April security patch

Download URLs: GDrive | SF

Note: Dirty flash is supported only if coming from previous build (April, 9th), if coming from any other build, please make a clean flash

Enjoy!
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] leo_97:
Hello, thank you for these instructions, may I copy/reference them on the OP?

PS: JFYI, if you guys are wondering, I'll be releasing April's LOS18.1 & LOS20 builds for kuntao soon, stay tuned. I didn't do it already because I've been busy with personal life lately and had some issues with the build server (already solved it), thanks for understanding.
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] Zdeslav:
Yes of course !!

Just fix lapsus in text from Magisk ver. 25.2--->25.1, and 26.2--->26.1 / sorry :geek:

Thanks again for fixing developing ROM!
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] leo_97:
May 09th 2023 Release​

Change log:

- Fetch latest Device Tree sources:

-- Bump graphene camera version to 62

-- devicesettings: Protect broadcast to fingerprint gestures

-- rootdir: Remove permission restrictions to the socket file

- Sync latest LOS source

- Merge May security patch

Download URLs: GDrive | SF

Notes:

- Magisk v26.x can be flashed through TWRP as usual, and IFAIK it works even without the "additional setup", so you can ignore it (trying to install Magisk via its app doesn't work, it keeps flashing boot image indefinitely)

- If clean flashing from other ROM or previous android versions, a format data might be required

- Starting from this release, only the most updated build will be available on Google Drive (due to storage limitations). Source Forge will remain normal, so if you need a past build, refer to the URL from first post, thanks for understanding.

Enjoy!
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] bidulez:
Hi @leo_97 , big thank you as usual :)

NB : The changelog is from april build

Can we flash to this build from previous (April) build rooted with Magisk 26.1 and encrypted (19-20230419-UNOFFICIAL-kuntao) ? 🫣
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] leo_97:
Thanks for pointing it out, just updated it :)

Yes, I did it myself and it worked fine. But remember, it's always a good idea to have a backup, just in case.
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] leo_97:
June 12th 2023 Release​

Change log:

- Fetch latest Device Tree sources:

-- parts: Update few parts icon

-- vendorsetup.sh: Use depth=1

-- Remove pixel_2016_exclusive

-- Bump graphene camera version to 63

- Sync latest LOS sources:

-- Additional zstd cmdline tools

-- zstd compression support for rsync

-- 2023-06 ASB patching: packages/apps/Traceur

- Merge June security patch

Download URLs: GDrive | SF

Notes:

- Magisk v26.x can be flashed through TWRP as usual, and IFAIK it works even without the "additional setup", so you can ignore it (trying to install Magisk via its app doesn't work, it keeps flashing boot image indefinitely)

- If clean flashing from other ROM or previous android versions, a format data might be required

- As stated on previous release notes, only the most updated build will be available on Google Drive (due to storage limitations). Source Forge will remain normal, so if you need a past build, refer to the URL from OP, thanks for understanding.

Enjoy!
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] eried1:
Once again, great work to stay up to date on all three or even four (counting the old 17.1 tree?) versions!

👏​
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] eried1:
Dirty flash = OTA via TWRP? Or does it mean current ROM is replaced and all old data will be removed?

Have only done clean flashes in the past.
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] leo_97:
Dirty flash means flashing one build while having a OS already installed.

Let me give you an example. Imagine I have 2 builds (named "old" and "newer"). Clean flash means installing one build (old for instance), configuring the OS (via setup wizard), etc then having a working OS. Dirty flashing in this case would be to download the "newer" build, rebooting to TWRP, flashing it directly then rebooting to system. In a normal workflow, this process should give an updated working OS, already setup, with all applications running.

However, sometimes the DT (device tree) or the upstream sources may be incompatible. In this case, dirty flashing could render to bugs/glitches/boot loop/etc so the OS won't work properly anymore.

I hope I could explain in a clear way ;). Another reference I found on the web for you guys regarding this is here.

BTW, sorry for the late reply
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] eried1:
No worries. I thought so. Just a pain to have to start over all over after each update - to be on the safe side, I guess.
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] leo_97:
Yes, I see your point. Perhaps you can try some backup & restore solution (e.g. Titanium backup) or something else... The LOS18 tree is/was the official one, IIRC, this one (comparing the Lineage DTs only) is the most stable one.