yashsingh1/xdaforums huggingface dataset:
[OnePlus 9] Rayekk:
I have an extremely big problem, maybe someone could help me here?

So today I tried to flash diffrent OOS version on my OnePlus 9, I did it with fastboot, after the command "fastboot reboot fastboot" the screen on the phone went blank and there was a sound on the computer as if the phone was still connecting and disconnecting. Now, the phone does not respond to the buttons, the charger, I cannot enter the fastboot, only the EDL mode works, but I cannot use the MSM because it does not detect the phone, I get the "sahara communication failed" notification all the time, previously the same MSM version was working.

Probably the most important thing is that it turned out that the OOS I tried to flash was actually ColorOS, I didn't pay attention to it, I don't know how it happened.

I feel like an idiot, I'm afraid that I will not save this phone myself and that the repair service will also not accept it under warranty, any suggestions?
[OnePlus 9] ctonylee1965:
https://xdaforums.com/t/msm-cannot-...a-sahara-connection-error-check-this.4308601/
[OnePlus 9] ctonylee1965:
See link below. Worked for me I was in same position.
[OnePlus 9] Rayekk:
Thank you very much! Tbh I can't understand how and why it works, but it worked!
[OnePlus 9] ctonylee1965:
Make sure you look at the rest of the instructions to get back on global from Indian.
[OnePlus 9] Wolverine619:
Brother what is your phone model is it Chinese (Le2110)? or another model ?
[OnePlus 9] syphax06:
bro i have the same issues , did u found any solution & can you help me plz
[OnePlus 9] TikiThePug:
See if these steps work for you: (last post)

https://xdaforums.com/t/display-becomes-unresponsive-after-oos-12-update.4382277/post-86199305
[OnePlus 9] DerBaLu841:
Hey, i have hardbricked my OnePlus 9 and now i have the connect and disconnect-problem in the EDL-Mode. My Model is a Lahaina and i hope it is the same like a Lemonade or a OnePlus 9. I was on the latest Android 12 for the OP 9 before it gets bricked. How i bricked my phone: First i have unlocked the Bootloader and after that i was trying to boot into TWRP. The bootscreen from TWRP comes and the screen gets black and then into boot dump mode. okay, then i installed this: https://xdaforums.com/t/fastboot-rom-pc-required-op9-stock-oos-11-2-2-2aa.4275727/unread and the message <awaiting any device> shows up and i disconnected my phone. After that my phone just shows black and on the pc it just shows up the "QDLoader" (yes, the driver is installed) . How i could bring my phone back to life and fix the partitionproblem/connect & disconnect problem. The MSM just shows "Status of Connection: N/A" and "Waiting for device". I am using an Laptop with Windows 10 on it and an intel chipset.

I think i have killed the partitioning of the oneplus by downgrading from A 12 to A 11. Thanks for your help. By the way: I have downloaded the MSM with Indian OS and I have still the same problem.
[OnePlus 9] kischde:
I´ve got exactly the same situation and problem as DerBaLu841... Anything to do for now or is the OP9 finally hard bricked now..?
[OnePlus 9] DerBaLu841:
Check this out:

https://xdaforums.com/t/msm-cannot-...ection-error-check-this.4308601/post-86528671
[OnePlus 9] AlexDybala:
Hi! Have you telegram? Can I ask to you help with the method you posted?
[Xiaomi Mi 11 Ultra] kuba319:
hello, so I have my 11 ultra for a few months, so far i used:

- nillkin 3d max - glass had a negative effect on the sensitivity of touch

- uv mocolo - it was perfect but my euti has peeled it off (maybe my fault is bad spreading of the glue?)

- hydrogel (I don't remember the brand) is okay but it slowly peels off through the case and I'm also annoyed by the greasing of the screen

do you have any recommendations? I am thinking about giving glass from mocolo one more chance.

thanks :)
[Xiaomi Mi 11 Ultra] shadowstep:
THREAD LOCKED

As per the Forum Rules:

Kindly use the existing thread for continuing discussion: https://xdaforums.com/t/tempered-glass-screen-protector.4280291/

Regards,

shadowstep

Forum Moderator
[OnePlus 6 Questions & Answers] boom1995:
Hi there guys,

yesterday i wanted to update from Android 10 to Android 11 stable, the problem is that i accidentaly installe Android 11 Open Beta 3.

Now i tried to manually download the OTA full package for Android 11 stable but it doesn't work, the system doesn't let me install it.

Since I'm out of warranty, would you suggest unlock bootloader, root it and reinstall a clean Android 11 wiping everything?

Thanks!
[OnePlus 6 Questions & Answers] kouzelnik3:
You can eventually try to wait for anything like OOS 11.0.0.1 etc. which will have newer update date that you would be able to install.
[OnePlus 6 Questions & Answers] boom1995:
In the end, i decided to unlock bootloader and to root it.

Thank anyway.
[JAMin, XDA Neo, S200 General] calypso666:
greetings to all the masters here.. im sorry if this is a noob question, but i am currently using the battery status app. and while tinkering around, i found the cpu scaling function :)

and so i began tinkering somemore and thought that if i could scale downwards when the cpu is not used, i could save some precious battery life :)

and so i did it. the lowest i could get was 87Mhz but the screen kinda like flickers abit. i was wondering if this is safe?

thank u again masters.. :cool:
[Xiaomi Redmi Note 3 Questions & Answers] longlivekate:
thanks
[Moto Z3 Play ROMs, Kernels, Recoveries, & Other De] Jleeblanch:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/

LineageOS is a free, community built, aftermarket firmware distribution of Android 11 (R), which is designed to increase performance and reliability over stock Android for your device.

LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

Introduction:

This is the Official LineageOS 18.1 thread for the Moto Z3 Play, codename beckham.

Information:

Official Wiki -> https://wiki.lineageos.org/devices/beckham

Downloads:

Builds -> https://download.lineageos.org/beckham

Bugs

Follow this guide -> How to submit a bug report

Notes

Supported GApps -> https://wiki.lineageos.org/gapps

Other

Kernel source -> https://github.com/LineageOS/android_kernel_motorola_msm8998

Contributors

@Jleeblanch, @erfanoabdi

LineageOS Source Code: https://github.com/LineageOS

ROM OS Version: Android 11

ROM Kernel: Linux 4.4.x

ROM Firmware Required: Android Pie (9.0) Stock Firmware
[Moto Z3 Play ROMs, Kernels, Recoveries, & Other De] Jleeblanch:
Reserved...
[Moto Z3 Play ROMs, Kernels, Recoveries, & Other De] CamposJ:
Using it and after an entire week now, no problems or bugs so far. I do have, however a small question: how do I make this rom to stop shortening text in icons and in the lock screen? Other custom roms will use two lines of text if the app name is too long but this one shorts it, which in some cases leads to 'not so desirable' results, like in the Wifi Analyzer App (see attached screenshots).

Changing the grid layout doesn't helped and this phone has plenty of screen resolution to avoid doing things like 'S...' instead of showing 'September' in the lock screen. Thank you very much for this awesome rom :)
[Moto Z3 Play ROMs, Kernels, Recoveries, & Other De] userx14:
First of all I'm really greatfull to have lineage supported on this phone.

One problem I encountered while installing the rom was that my phone refused to connect to anything other then GSM. So mobile data was not working.

I started from an older version of the stock rom, not the latest stock 9.0 rom.

This seems to be a somewhat known issue, u/i_guess_i_am_a_scout on reddit has written a guide on this for lineage 16 / 17.

Though for me it was sufficient to flash the modem and vendor partitions for slot a and b:

fastboot --slot a flash modem NON-HLOS.bin
fastboot --slot b flash modem NON-HLOS.bin

fastboot --slot a flash vendor vendor.img_sparsechunk.0
fastboot --slot a flash vendor vendor.img_sparsechunk.1

fastboot --slot b flash vendor vendor.img_sparsechunk.0
fastboot --slot b flash vendor vendor.img_sparsechunk.1

fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier

boot twrp, sideload the twrp-installer and latest lineage zip

After that mobile data and LTE suddenly started to work.

Another minor issue I encountered is that "Brightness control by sliding across the status bar" does set the brightness to 100% for very low brightness levels / on the very left of the statusbar-swipe. See: https://gitlab.com/LineageOS/issues/android/-/issues/3865 .

But appart from that a very solid rom, in the one month I've been using it, there were no other issues.

Thanks.
[Moto Z3 Play ROMs, Kernels, Recoveries, & Other De] userx14:
Just some ideas as workarounds:

1) Change the grid layout by long pressing on the home screen -> Styles and Wallpapers -> Grid -> 4x5

At first this applies only to the home screen and not the app drawer:

But after a reboot the appdrawer will also have the 4x5 layout.

2) You could decrease the font size in the settings, but that might make other things hard to read.

3) Use a third party launcher.

The lock screen month clipping issue seems to be localization related, on english this works fine.

But I guess that is not really an issue specific to the z3 play, so you probably should report it as a lineage bug report so it can be fixed for all devices.
[Moto Z3 Play ROMs, Kernels, Recoveries, & Other De] Jleeblanch:
Glad you figured it out, which there is a message on the install page stating to make sure you're on the latest firmware before flashing the rom. Mobile data was only an issue for CDMA users in early builds of 17.1/16.0. I was missing a flag on our board config that fixed that.

As for your guide, it doesn't make any sense to flash the vendor partition, you mostly just need what gets symlinked there (i.e. fsg, modem, dsp). Vendor get overwritten during the rom installation. In your case, you were probably on a firmware version lower than the firmware version beckham's device specific blobs are from and the rom didn't agree. Regardless, I am glad all worked out in the end.

I am aware of the Brightness issue and am working on a solution. I can confirm it also happens on Evert and Lake as well.
[Moto Z3 Play ROMs, Kernels, Recoveries, & Other De] userx14:
I'm not really sure which one of the flash commands fixed it in the end, it could very well only be the flash modem command.

I also started looking into the brightness issue. I'm not very experienced when it comes to android development. But if I'm right the code that controlls the status bar brightness should be here. I've experimented a bit and found that the problem occurs in the padding zone on the left, where there is left 15% of the status bar which should return the lowest brightness value.

In this case the newBrightness is set to:

int newBrightness = mMinBrightness;

and

mMinBrightness = context.getResources().getInteger(com.android.internal.R.integer.config_screenBrightnessDim);.

EDIT:

I've searched through through other device's code (Moto E 2015) and some seem to configure this value inside this device specific config file.

But how to find out what this should have as a value and why does it work for the normal brightness slider but not for the status bar swipe?
[Moto Z3 Play ROMs, Kernels, Recoveries, & Other De] Jleeblanch:
The config option is found in our sdm660-common tree which we currently have set to "1". Default value found here is "10", which digging into stock is what is used.

I've already made the necessary changes in the common tree, I just have yet to have a chance to build and test. I legit just moved to Georgia from Vermont this past weekend. In the coming days I'll be hard at work on my supported devices in hopes to work out the remaining minor bugs.
[Moto Z3 Play ROMs, Kernels, Recoveries, & Other De] userx14:
Thanks for the information,

please don't interpret my posts here as impatience, so please take your time.

I just saw this minor issue as a possibility to get my feet wet with the lineage source.

Can I help by trying to build a version with a the modified sdm660 tree file where config_screenBrightnessDim is set to 10 and test if this fix works?
[Moto Z3 Play ROMs, Kernels, Recoveries, & Other De] Jleeblanch:
No worries! Any and all help is always appreciated, one of the benefits of open source is anyone can contribute 😊

That's totally up to you! All the info you need to build is on the Lineage Wiki. I believe I pushed the changes to my personal github if you wanna pick them. If you wanna experiment yourself, removing that line I linked in sdm660-common (and the relevant comment above it) is what you would want to do to revert the value back to "10" as it'll just use the value in frameworks/base instead.

If you have any questions, don't hesitate to ask! Lemme if that works or not or even if it changes the behavior even slightly. We may even need to play with the value a bit.
[Moto Z3 Play ROMs, Kernels, Recoveries, & Other De] userx14:
Well, after downloading for 5h and compiling another 5h I was able to create the new zip file.

For me the 'extract proprietary blob' part of the wiki didn't work, when executing ./extract-files.sh it got some files, but for others it reported errors:

- vendor/lib64/sensors.iio.so
- product/priv-app/ims/ims.apk
- system/app/MotoSignatureApp/MotoSignatureApp.apk
!! system/app/MotoSignatureApp/MotoSignatureApp.apk: file not found in source
- system/priv-app/ModFmwkProxyService/ModFmwkProxyService.apk
!! system/priv-app/ModFmwkProxyService/ModFmwkProxyService.apk: file not found in source
- system/priv-app/ModService/ModService.apk
!! system/priv-app/ModService/ModService.apk: file not found in source
- system/priv-app/MotCamera2/MotCamera2.apk
+ keeping pinned file with hash 260df16116b0e9f5144114454533bcda35f669e7
- system/priv-app/ProjectorApp/ProjectorApp.apk
!! system/priv-app/ProjectorApp/ProjectorApp.apk: file not found in source

not sure if I was missing a setting, this result was with "USB debugging" and "Rooted debugging" enabled in the android settings.

But extracting the files from a official zip file worked out.

EDIT:

After some testing with different brightness xml values, the lowest value that still works is 2.

This is also the lowest brightness achievable with the default brightness slider.

EDIT2:

Strange, with the integrated brightness settings I can reach lower brightness, so it should be a value less than 2. But 1 did break the brightness adjustment, so there is probably a deeper problem.
[Moto Z3 Play ROMs, Kernels, Recoveries, & Other De] Sanras:
Hey, I'm still running official LOS 17.1 on my Z3. Does this build still have a working Moto Camera 2 like 17.1? I heard from other custom ROM users on Motos that it crashes for them on 18.1. if the Moto Camera 2 app is working fine, then I'll go ahead and upgrade.
[Moto Z3 Play ROMs, Kernels, Recoveries, & Other De] userx14:
Hi @Sanras,

for me the "camera 2" app is working on the most recent build of LOS 18.1 .

There is a toast "dlopen failed libmcf-jni not found" which pops up on occasionally on start, but it does not seem to affect the functionality.

If you are using TWRP booted from fastboot, you could do a full system backup before flashing, just in case.

Greetings

userx14
[Moto Z3 Play ROMs, Kernels, Recoveries, & Other De] Sanras:
Ok, that's good to hear! Thank you for the information.
[Moto Z3 Play ROMs, Kernels, Recoveries, & Other De] cruzdl:
The first time I installed LineageOS 18.1 I accidentally deleted all the stock rom files and GPS, GSM and bluetooth didn't work. I went back to stock rom and installed LineageOS 18.1 again without deleting all the files and the only thing that still doesn't work is Bluetooth. Still not able to resolve.
[Moto Z3 Play ROMs, Kernels, Recoveries, & Other De] userx14:
@cruzdl

Strange, for me bluetooth works.

Maybe you used a different version for your stock rom or your device is different?

I have an xt1929-8, and I'm not sure if the emmc and ram size is the only difference between the versions.

Is it correct that you created the issue https://gitlab.com/LineageOS/issues/android/-/issues/4057 ?

When I have bluetooth disabled with the quick settings I also get bluetooth adress not available, but when I switch bluetooth on I have an bluetooth address that is the same as the Wifi mac address, but the last digit is one lower.

Do you have the a Wifi mac address there when you have Wifi active?
[Moto Z3 Play ROMs, Kernels, Recoveries, & Other De] HyperChrisX:
Curious if anyone has either of the camera mods working with this? I have both the Hasselblad and 360 mods and neither seem to work, with the camera just defaulting back to the built-in one or crashing.
[Moto Z3 Play ROMs, Kernels, Recoveries, & Other De] Belarios:
Does anyone have any tips for diagnosing VoLTE? I'm on Tracfone MVNO with Verizon.

I saw this guy went back and reflashed the stock rom and then his started working on Mint MVNO with T-Mobile.

https://www.reddit.com/r/LineageOS/comments/qacid8

So Lineageos and Z3P are VoLTE capable.

I reflashed the full set of partitions from the latest RETUS stock zip a few times. I did get VoLTE most of the time, but not always. I'm not sure what that means if VoLTE doesn't always work with the same stock rom. I have never been able to get it with Lineageos loaded.

I'm using the recommended APN. VoLTE is enabled in settings. But I always get CDMA-1rtt for voice. During a call, I lose data.

I'm not sure how to mess with the carrier config. Maybe I should try to extract the carrier config from the stock rom and check it against the lineageos rom?
[Moto Z3 Play ROMs, Kernels, Recoveries, & Other De] telly01:
Camera Mods dont work. I have the Hassleblad myself. Works on the stock rom not the Lineage 18.1.
[Moto Z3 Play ROMs, Kernels, Recoveries, & Other De] telly01:
I saw the lastest Weekly update added SD card encryption.

I flashed this morning. When I formatted the sd card the phone hung. But Rebooting and firmatting internal again was a success. I have rebooted and powered down a couple times and it all looks great!!!

This is a huge feature for me!

XT-1929-4 32GB
[Moto Z3 Play ROMs, Kernels, Recoveries, & Other De] guckuck:
Hi,

I just installed the latest version 18.1-20211215 on my 1929-8. So far, everything seams to work.

I also installed MindTheGapps (11.0.0-arm64-20210920_084011). I could not install OpenGApps (ARM64, 11.0, nano). I told my: The package is for 11.0 and I need one for 9.0. I don't know why. Maybe I need another bootloader? I only installed the recovery version from LineageOS as descriped here: https://wiki.lineageos.org/devices/beckham/install

So, the problem is, that there is no Google Play Store installed. Is the only way to use a store like F-Droid?

Should I test something on the 1929-8?

Best regards and thanks for the help

Kay
[Moto Z3 Play ROMs, Kernels, Recoveries, & Other De] guckuck:
So, after trying it again, I could install OpenGapps. I use the same file. But, there are still no google apps visible. :-(

Before, I tried to install trwp, without success ((bootloader) Invalid partition name recovery)

Edit: So, all good things are three, I tried it the 3rd time with MindTheGapp, now the Google Apps are there. :)
[Moto Z3 Play ROMs, Kernels, Recoveries, & Other De] giobbe71:
hi guys, i've just installed the rom but mobile data doesn't work... i usually have 4G in the preferred network type, but in this rom is not present, I tried all network type present in selection but none of them works

my operator is vodafone italy

any ideas? thanks
[Moto Z3 Play ROMs, Kernels, Recoveries, & Other De] pietrotti97:
This issue happened to me 2 or 3 times. You just need to reflash stock rom (for what I know, for unknown reasons the modem partition just corrupts from time to time while flashing custom roms).

Follow this THIS guide to restore the phone and check if it's working normally after. Then just reflash whatever custom rom you like and you're good to go

HERE you can find all the Z3Play stock firmware, just download the one you had stock ( for my z3play it was RETEU )
[Moto Z3 Play ROMs, Kernels, Recoveries, & Other De] inc_xda:
Where I can find stable version of ROM, not a nightly?
[Moto Z3 Play ROMs, Kernels, Recoveries, & Other De] jeferson1979:
A nightly is a stable ROM
[Moto Z3 Play ROMs, Kernels, Recoveries, & Other De] StefTT:
gday need some help just flashed this custom rom and i'm not get wifi or mobile service flash other roms same problem HELP PLEASE ANYONE!!!!

followed guids step by step still no WIFI or MOBILE SERVICE
[Moto Z3 Play ROMs, Kernels, Recoveries, & Other De] StefTT:
Hey guys is this thread dead what up or u guys hard at work? If so keep the great work guys, I'm running the latest version of this Rom it's smooth and snappy???
[Moto Z3 Play ROMs, Kernels, Recoveries, & Other De] StefTT:
Having low phone speaker issues any fixes?
[Moto Z3 Play ROMs, Kernels, Recoveries, & Other De] Tarmen:
First of all: Thank you for providing continuing updates to the 18.1 LineageOS for the beckham platform.

I' m running into three issues:

1- Bluetooth devices are invisible within apps, even though Bluetooth is on and the same device *can* be found and paired within the Android system menu.

2- The image preview within any camera app I have tried will stay as background image for the device screen until the device has been rebooted. This behaviour seems independent of launcher used (tested under Trebuchet and OpenLauncher)

3- The digital clock widget frequently disappears (tested under Trebuchet and OpenLauncher).

Long-touching the surface where the clock used to be, makes it appear again. Note that the Analog clock does not suffer from this same issue.
[General Questions and Answers] chuck0652:
I have a gateway tpa60w that works but is no longer useable because the OS is outdated and no longer supported, (ver. 3.2.1) I have joined this group for help.

How can I update it, all the links are 10 + years old and not working. I need step by step instructions and downloadable update files, can anyone help ?

If i understand I need to make the tab think its an iconia a500 first again not sure how and need step by step help

thanking you all in advance
[General Questions and Answers] Deleted member 1890170:
Updates get rolled out by OEM if they deem it necessary. Hence ask them for updates.
[General Questions and Answers] chuck0652:
Gateway was acquired by Acer Inc. in 2007. I can not find any help from Acer or gateway on line
[Touch Diamond, MDA Compact IV General] hkpeople:
How do add over 15 PEOPLE in TF3D?

Can I add over 15 PEOPLE?
[Touch Diamond, MDA Compact IV General] liamhere:
i think i am correct in saying

you can't....unless somebody knows otherwise
[Touch Diamond, MDA Compact IV General] acabbie:
I too, would like the facility to add more picture contacts.........sadly i lack the techie know-how to actually do anything about it :(
[Samsung Galaxy M02s] mdkhairulislamnabil:
Can't seem to find any customs for m01s ? Any news on when it'll be arriving?
[Samsung Galaxy M02s] Deleted member 11822153:
I have been waiting for customs on my galaxy m01s too, but unfortunately, no guides on it. This device is quite underrated.