yashsingh1/xdaforums huggingface dataset:
[Moto Z2 Play  ROMs, Kernels, Recoveries, & Other D] mezcla:
Sorry, I was full of work and completely forgot. I don't remember very well 'cause I flashed it time ago, probably ALBUS OPSS27
[Moto Z2 Play  ROMs, Kernels, Recoveries, & Other D] marcost22:
Just like the other poster

Please people PLEASE, read the full post. Issues with bluetooth, rebooting and telephony are caused by improper firmware
[Moto Z2 Play  ROMs, Kernels, Recoveries, & Other D] alphaandomega:
Sorry, I didn't express myself properly. Everything installs fine, it's just that I can never get to the Welcome screen, I just see the Lineage logo for about 20 minutes and then it finally says the file has failed because it must be corrupted, etc. If that's the message you need, I'll try to get to it and attach a picture.
[Moto Z2 Play  ROMs, Kernels, Recoveries, & Other D] marcost22:
Yeah that'd be helpful
[Moto Z2 Play  ROMs, Kernels, Recoveries, & Other D] romulofarias37:
can you tell me if the default motorola apps (motorola gestures, moto actions, moto screen) and moto mods from tv+drums exclusive to brazil work well?
[Moto Z2 Play  ROMs, Kernels, Recoveries, & Other D] marcost22:
Moto actions + Moto gestures are integrated, moto screen (i'm assuming is something like attentive screen) is not, however AOD is. Mod support for the TV mods is there, the apps isn't and can be downloaded from the play store, however i've gotten conflicting reports on whether it works. I have no idea about the drums mod
[Moto Z2 Play  ROMs, Kernels, Recoveries, & Other D] dib.1012:
I have been using 18.1 with my Moto Z2 Play for a while now and it worked well.

Today I installed the latest update/Nightly (lineage-18.1-20230426-nightly-albus) with the Updater. After reboot, the phone says "SD-Card is missing" and "finishing system update". But nothing finishes, and I can not open any apps anymore. I left it like that for a few hours, but nothing changed.

I then sideloaded last months version (20230326) and the message about the SD-Card is gone, the apps open again (at least I see that there are notifications from the apps), but after entering my pin the screen goes black, and after 2 seconds I am in the lock screen again. It looks like the desktop/launcher/... is crashing, so everytime I fall back into the lock screen.

I then sideloaded todays version (20230426) again, and I get the SD-Card message again, so everything as before...

Any hints, anything I could try?
[Moto Z2 Play  ROMs, Kernels, Recoveries, & Other D] marcost22:
There might be a non-zero possibility someone merged something into the ROM-side that broke stuff. Let me ask around a bit
[Moto Z2 Play  ROMs, Kernels, Recoveries, & Other D] dib.1012:
That would be great, thank you!

Is there any way to get the previous version working again? Probably not, but I am without a phone right now and not at home, so....
[Moto Z2 Play  ROMs, Kernels, Recoveries, & Other D] marcost22:
While saving your data? Not that i know of
[Moto Z2 Play  ROMs, Kernels, Recoveries, & Other D] davidbfg:
Hey, one of the problems I've always had trying to move over to lineage with this phone is how it's unable to invert the fingerprint navigation. It is an option I would have expected to see a toggle for in the Moto gestures.

I got the z2 play with the intent of keeping it for a very long time so I have a backup of the same model that I'm using for development. I just finished building lineage on my system and wanted to know where I could start looking to implement a toggle for this.

Thanks.

The second issue would be that the battery never seems to last like it does for the stock Rom's but I'm pretty far from being able to fix that.
[Moto Z2 Play  ROMs, Kernels, Recoveries, & Other D] marcost22:
Hi!

We use Lineage's vendor.touch implementation for handling it, you can find the generic hal at

https://github.com/LineageOS/android_hardware_lineage_interfaces/tree/lineage-18.1/touch/1.0 and locally in the path hardware/lineage/interfaces/touch

Our implementation of it lives at device/motorola/albus/touch. I'd start looking there.

That's a secondary effect of running a newer OS with the same hw, we are stretching it thinner and thus running at higher frequencies more often. Since android 9 GApps have gotten explosively more bloated (running non-gapps vs gapps is a 2h SOT difference) and so has the OS. I've done some kernel optimizations to try and mitigate this, but there's only so much i can do, given the fact that we are stuck on 3.18 which is an awful kernel to be using
[Moto Z2 Play  ROMs, Kernels, Recoveries, & Other D] davidbfg:
I've got something started https://github.com/David-bfg/androi...mmit/fcc3e0ce185ec36b70f49b4166a7a4b210839a6d

Looks like IFingerprintNavigation only has interfacing functions for disabling navigation logic. Could use some more notes on where the code for that is in the haystack. Could probably continue this thread on github to keep this channel clear. Thanks for your assistance.
[Moto Z2 Play  ROMs, Kernels, Recoveries, & Other D] marcost22:
I'm not the most useful when it comes to userland interfaces (i lurk in the kernel mostly and this was done with help from some of the nash devs) but i'd check other devices implementation for guidance maybe?

android_device_xiaomi_sagit/touch/KeySwapper.cpp at 3d78781b490366e21fc1da712671ad2bdd016140 · LineageOS/android_device_xiaomi_sagit

Contribute to LineageOS/android_device_xiaomi_sagit development by creating an account on GitHub.

github.com

Or even this commit

op3: touch: Implement key swapper interface · LineageOS/android_device_oneplus_oneplus3@16215e0

Apply minor clean-ups while at it Change-Id: I007624124997b46a0ed2961b938cd488efad45f2

github.com
[Moto Z2 Play  ROMs, Kernels, Recoveries, & Other D] davidbfg:
The TLDR; just follow this post if you ever need Inverted navigation do this.

https://xdaforums.com/t/swapping-back-and-recent-apps-buttons-in-lineageos-14-1.3630450/

I worked on implementations looked at the interfacing functions for IFingerprintNavigation and researched the mechanisms used in stock. The IFingerprintNavigation actually has other methods available those are get and setNavigationConfig. It is named promisingly but it seems to pass an object full of timings for how responsive the sensor is to touch. Makes sense once you realize this is an API from the fingerprint sensor manufacturer not Motorola.

nash: Add fingerprint navigation support · LineageOS/android_device_motorola_nash@ee0f70a

* Imported from berkeley-dev's kirin970-common tree, and edited. * Opt to not use Moto's OneNav solution and instead just listen for keycodes without a middleman listener. * This likely...

github.com

I stumbled onto this commit to try and glean how anyone figured to use IFingerprintNavigation in the first place.

I noticed in keylayout/uinput-fpc.kl it had the original key functions.

- key 621 SYSTEM_NAVIGATION_RIGHT
- key 620 SYSTEM_NAVIGATION_LEFT
+ key 620 BACK VIRTUAL
+ key 621 APP_SWITCH VIRTUAL

It appears that the stock solution started with those keys triggering generic navigation controls. Then somewhere in software the Moto OneNav solution picks up those events and triggers the appropriate action. Then if the software is triggering the nav buttons it can easily swap the actions without modifying the read only partition to change these values.

While I'd like to make my life easier and anyone else who is looking to swap the nav buttons; it seems that the on screen nav bar is already a solution to fix this for today's and future devices. Those of us getting the most of our old devices can just modify the read-only partition to set it how we like.
[Moto Z2 Play  ROMs, Kernels, Recoveries, & Other D] mrtz.raw:
I have tried to install the 18.1 version but I will always get a Bootloop. I installed the 15.1 Version it worked fine. I installed an unofficial 16.0 version and it worked. Then I tried to install the 18.1 and always Bootloop. I have read that I need 16 or higher to install 18. But still no suckses. What could be the problem.
[Moto Z2 Play  ROMs, Kernels, Recoveries, & Other D] mrtz.raw:
Can you tell me how you have done it. I have encountered the same problem with the Bootloop when I tried to install the 18.1 version
[Moto Z2 Play  ROMs, Kernels, Recoveries, & Other D] plumax81:
Hi, haven't good results..... still one sim..
[Moto Z2 Play  ROMs, Kernels, Recoveries, & Other D] enkidu101:
Hoping somebody sees this, and has an idea what I can do. Generally, this ROM is working fine. But I have one problem... Sending plain TEXT messages doesn't work. Sending voice messages or pictures via text works fine.

Any ideas? I did try Google, but couldn't find anything helpful (so far).
[Moto Z2 Play  ROMs, Kernels, Recoveries, & Other D] snuk182:
Bootloop as well.

UPD: Reflashed again, carefully following the official instructions. Bootloop. The Rom at the official download page is unusable.

UPD2: Have found an older build in the archive.org, which does work. Attached. Missing features of this build:

* No Fingerprint touch-to-wake

* Device encryption leads to a bootloop (disk is encrypted though, but no decryption pattern is requested on boot)

UPD3: Overall is stable enough for daily use. The touch sensor disappears sometimes, but this might be a hardware problem (I've been assembling my unit from separate parts of a very random origin.)
[Moto Z2 Play  ROMs, Kernels, Recoveries, & Other D] scooller:
i have Bootloop as well, the version the work well it lineage-16.0-20201209-UNOFFICIAL-albus with android 9
[Moto Z2 Play  ROMs, Kernels, Recoveries, & Other D] Vegan_T-Rex:
Noob Question: I have dotOS 5.2.1 (android 11 too) installed on my moto z2 play, is it possible to change the ROM I'm using to this one while keeping the app data?
[Moto Z2 Play  ROMs, Kernels, Recoveries, & Other D] fuserh:
impossible to install android 11, (lineageOS or e/OS) the system restarts in a loop, this happens even if encryption has not been activated, forced to downgrade to android 8 (e/OS with e-0.20-o-20211210151039-dev-albus.zip)

I think the fault lies with the bootloader (version-bootloader: moto-msm8953-C0.CD) and I can't find anything to change the bootloader version (nothing on the motorola website).
[Moto Z2 Play  ROMs, Kernels, Recoveries, & Other D] marcost22:
That bootloader version corresponds to Android 8.

It's not impossible to install, you are refusion to follow instructions and are trying to use Android 11 with an incompatible firmware
[Moto Z2 Play  ROMs, Kernels, Recoveries, & Other D] fuserh:
that's what I thought, change the bootloader version but I can't find the most recent versions to download.
[Moto Z2 Play  ROMs, Kernels, Recoveries, & Other D] marcost22:
lolinet mirrors - firmware, software, iso etc.

lolinet mirrors - powered by h5ai

mirrors-obs-2.lolinet.com
[Moto Z2 Play  ROMs, Kernels, Recoveries, & Other D] fuserh:
thank you and after downloading ALBUS_RETAIL_9.0_PPS29.133-30_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

is it ok for motorola model XT1710-09 ?

i don't want to install android 9 but just change the bootloader version...for now (then we'll see about e/OS)

I extracted boot.img and bootloader.img ....

if I only fastboot flash boot boot.img won't my data be erased ?

isn't there a md5sum or sha256sum check beforehand ?
[Moto Z2 Play  ROMs, Kernels, Recoveries, & Other D] marcost22:
It's not only a BL thing but a modem thing for using Android 9+ roms, and you cant use A9 modem with A8.

It's ok for all models, and sorry but i don't know the checksum
[Moto Z2 Play  ROMs, Kernels, Recoveries, & Other D] fuserh:
ok so when I flash boot.img and bootloader.img android won't boot anymore?

never mind, the aim is to get the latest version of e/OS (android 11) working.

to check file integrity, i'll do two successive downloads and see if md5 and sha256 are identical on both downloads.
[Moto Z2 Play  ROMs, Kernels, Recoveries, & Other D] marcost22:
Boot img contains only the kernel and ramdis, flashing that does absolutely nothing

You also need to flash non-hlos as that contains the modem

TBH i'd flash the entire image and boot into A9 so that the modem can update EFS/persist partition properly
[Moto Z2 Play  ROMs, Kernels, Recoveries, & Other D] fuserh:
thanks, I'm going to install flasher completely and test android 9 before installing e/OS.
[Moto Z2 Play  ROMs, Kernels, Recoveries, & Other D] fuserh:
it's ok, android 9 works correctly

with adb I see: M8953P_52.61.07.98R ALBUS_EMEADSDS_CUST

I'm now going to install e/OS
[Moto Z2 Play  ROMs, Kernels, Recoveries, & Other D] fuserh:
e/OS version android 11 now works very well except that:

when switching off the device, it goes directly into fastboot mode (android 9 didn't have this symptom) so I boot the device from fastboot mode...this isn't too annoying as everything else is ok but I don't know what the reason is
[Moto Z2 Play  ROMs, Kernels, Recoveries, & Other D] fuserh:
The obstacle course:

-install twrp-3.4 (newer twrp cannot be installed) to reformat all partitions and remove residues.

but beware: twrp seems to be a sideloader, but then e/OS gets stuck on its startup logo

-then remove twrp by flashing the recovery available on e/OS

https://images.ecloud.global/dev/albus/

but it's impossible to boot from the recovery, so you're back on the fastboot in a loop

-so I flashed an older recovery: this one: recovery-e-1.1-r-20220628200015-dev-albus.img

and miracle: e/OS installs correctly and no longer gets stuck on its logo

and shuts down correctly. magisk root also flashed correctly.

e/OS (Android 11) updates the Z2 play again

bootloader version now shows M8953P_52.61.07.98R

note: I don't know if this older recovery can update if the system is encrypted, I'll check on the e/OS forum.

forum if this experience could be useful.
[Samsung Galaxy Tab S7 / S7 Plus Questions & Answer] david576:
Hi,

I have recently updated my device to the latest software update and since then the device keeps restarting randomly.

I have managed to enter recovery mode, however none of the features listed. I have tried wiping data, wiping partition. Each time I selected one it would say wiping cache or wiping data and hang there until the next random reboot. The wiping task has never completed.

After this each time the device restarted it booted into recovery mode and I was unable to leave as none of the features there worked.

Then I left it on the charger overnight and now there is nothing on the screen. I tried force restarting it, then entering recovery mode and download mode without success.

The screen remain black.

When I plug the device in to the PC it shows up under the Other devices. The following image shows exactly how it shows up.View attachment 5636055

When I hold the Volume down and Power button, the device disappears momentarily then reappears which would suggest it has restarted.

Is there a way to fix this issue?
[Samsung Galaxy Tab S7 / S7 Plus Questions & Answer] azascan:
Sounds very similar to what happened to my 8 year faithfully working Nexus 7 tablet. One day I had it charging on my PlayStation and I rebooted the Nexus and it the PlayStation walked away when I came to use the tablet it wouldn't do anything (no sound either) but when plugged into a computer it was recognized. I figured I fried it so I didn't look to far into if fixing was even a possibility .
[Xperia Z5 Q&A, Help & Troubleshooting] xperia-dev:
Hello, I recently dusted off my Z5 and would like to make it my daily driver. I need help with the direction on which ROM to use. I want to get the security updates, but also want to preserve the original Sony camera processing software, so the photo taking quality stays the same as in stock. What would you suggest to try?
[Touch HD General] marcel808:
I had a Tytn II then a Touch Pro before switching to the Touch HD. I was VERY worried after reading all the negative issues raised on this forum:

1. poor screen brightness

2. unable to play movies well

3. GPS lag in tomtom

4. poor battery performance

5. on screen keyboard not great

All I can say is I've had the Touch HD for a week now and its FANTASTIC.

1. Screen brightness is very good. At least as good as the iThingy (the wife has one of those). Out the box the HD comes with brightness on auto so itsn't that bright.

2. I took 5 movies from my PC, all mpeg4 AVIs (no 720p or course) ,24fps,around 660x360 in resolution, bitrate around 1000kbps....not converted for a phone in anyway, as they were when I downloaded them. All but one played absolutely perfectly. Only one is very slightly jumpy but perfectly watchable (bitrate too high).

3. I use GPSGate so maybe that helps but I have zero lag on the GPS in tomtom. With the big screen it looks amazing. so much easier to read than on the Touch Pro.

4. For me, battery is better than the Touch Pro. I haven't tried watching endless videos yet but I get 2 days out of a battery using phone, a bit of GPS, some wifi, some mp3s.

5. keyboard isn't perfect but its ok. there are plenty of other better keyboards you can download.

So lets try and be a bit more positive guys :)

I accept its not the perfect phone but until the tegra chips and wm7 appear, its as good as it gets and I love it!
[Touch HD General] xdaman85:
Yes i agree, this is the best (in my opinion) windows mobile out there.

I love the screen,

only problem i have is that alot of applications/games are not compatable with the display, but im sure there will be updates to run these apps soon
[Touch HD General] indup:
marcel where do you have the screen brightness set to?
[Touch HD General] marcel808:
Today I changed the brightness to maximum when on battery. I'll see how that goes over the weekend to see what effect it has on battery.

But I found the auto brightness fine. I'm in the UK so don't get a lot of chance to test it in bright sunshine :(
[Touch HD General] nin2thevoid:
Love the brightness and resolution, hate the viewing angle... Slightly off angle and it's very yellowish and unsharp, hence the IPhone and such look better in video's... Facing the screen however, it's awesome, a contender for any screen.

I never compared with the Pro, only the Diamond (yes much longer battery life, both bigger battery and good software optimization), but my power usage still drains the device pretty fast :) Regular usage easily gets me a couple of days though.

Just got TouchPal... The only non-hardware keyboard ever that really blew me away. I can type AT LEAST as fast on that as on my Blackberry Pearl, and that is a big statement.

TouchPal is 100% compatible with WVGA/Touch HD and even has a Diamond/HD/Pro skin.

Couldn't have said it better myself. The only thing that I got left on my wishlist (after having had Nokia, Samsung, Blackberry, several HTC's and an iPhone) as Windows Mobile 7 and the Tegra platform. WM7 looks very, very promising though. I hope it will be compatible with the HD, it's really totally different from the current WinMo interface.
[Touch HD General] mlalahoi:
According to the working programs post the list of apps that works is ten times longer than the apps that don't. Those few odd apps will be ported or upgraded quickly as this device is quite popular, IMHO.

+1 for enjoying an awesome device and not ragging on tiny little features.. no device is perfect and they will never make a perfect one, there's just so much more money in making nearly-perfect things ;)
[Touch HD General] orb3000:
Completly agree mate!

Shie-shie
[Touch HD General] Philio25:
I agree, it's an awesome phone, getting boring reading endless threads about tiny things that aren't perfect and iPhone comparisms.

Best phone I've ever had and used IMO.

P.S. If people love the iPhone so much why are they on a WM forum?? :)
[Touch HD General] donbronzi:
I'm glad this thread was created. I am sick of people slating this phone.

'The video playback isn't as good as my 40" HD panasonic tv' or 'it hasn't got a Dpad' or 'the screen isn't bright enough' or 'its got a gps lag'.

!!!!GET OVER IT!!!!​

This is the best touch phone on the market all things considered, and the best thing is with time it'll get better due to the nature of HTC and WM. I've had this phone for 4 days now and still can't put it down, not opnly does it run smooth but looks sooooo sleek and stylie. I've already posted this statement in another post but

let the haters hate and the doubters doubt, what they want is either in the past or i the future. HTC HD WHAT A GREAT DEVICE!
[Touch HD General] rizwan157:
best mobile out there right now love it. I've had tytn11, iphone, diamond, blackberry storm but HD is simply the best. I did have my reservations, especially after reading alot of negative reviews including some opinions here but after few days playing around with it I'm very pleased.
[Redmi Note 11 Pro+ 5G (peux)/POCO X4 Pro 5G (veux)] BR4UTAL:
Hi, I've been using the Poco X4 Pro for a month now, it's been a smooth ride though the development for the device is very slow and almost non existent as of now since kernel sources have not been released

The only major flaw I've found with the X4 Pro is the screen flickering, this does not seem like a software issue as I've already tried Miui IN, Miui Eu, Miui global, (Unofficial) Pixel Experience Plus, (Unofficial) Evolution X

The screen flickering is most noticable in a dark environment (basically at night) and the most annoying part is that it occurs while watching multi media content

I don't think I am the only one who has this problem as some of the people in the telegram group for the device explain the same thing

so i don't think getting a replacement will help much as it may be the same for all devices just when u notice it

I don't think there's any "fix" for now atleast

I wanted to ask do you face the same issue on your Poco X4 Pro 5G or Redmi Note 11 Pro Plus 5G?

p.s documenting this is nearly impossible as it happens at random intervals and feels much more subtle on camera than visible with naked eyes
[Redmi Note 11 Pro+ 5G (peux)/POCO X4 Pro 5G (veux)] razr96:
I haven't seen any screen flickering at all and I've watched a lot of content in a dark environment, usually at high brightness. Might be only some devices have it.
[Redmi Note 11 Pro+ 5G (peux)/POCO X4 Pro 5G (veux)] BR4UTAL:
You might be right actually, maybe it is only the Indian variant (Peux)
[Redmi Note 11 Pro+ 5G (peux)/POCO X4 Pro 5G (veux)] shaggyrogers:
Then use the stock version and wait for the update or just change the display if it is a hardware issue!
[Redmi Note 11 Pro+ 5G (peux)/POCO X4 Pro 5G (veux)] BR4UTAL:
Stock rom has the same thing. Changing display might not help actually it seems almost all devices have their screens flickering (noticable in 120hz refresh rate)

So a new display might also have the same problem?
[Redmi Note 11 Pro+ 5G (peux)/POCO X4 Pro 5G (veux)] Danny Sia:
Yup, I have same issue with you. The AMOLED screen on the Poco X4 Pro 5G did not show true black and it shows grey blacklight when the brightness on between 15% - 65%

View attachment 5643819
[Redmi Note 11 Pro+ 5G (peux)/POCO X4 Pro 5G (veux)] BR4UTAL:
dang, that seems bad but it also proves that usually the top part has the most problems
[Redmi Note 11 Pro+ 5G (peux)/POCO X4 Pro 5G (veux)] Danny Sia:
And I noticed sometimes my Poco X4 Pro 5G have a bit laggy when swiping or scrolling FB, messenger, etc... This issue happened since when its first launched.

I still don't understand why Poco did not want fix all bugs on their phone and What's the point of keep updating security patch?
[Redmi Note 11 Pro+ 5G (peux)/POCO X4 Pro 5G (veux)] Danny Sia:
Actually top part and bottom part has the most problems and I noticed it has flicking issue.
[Redmi Note 11 Pro+ 5G (peux)/POCO X4 Pro 5G (veux)] BR4UTAL:
The lags are definitely a software issue and can be fixed, for me i just got out of Miui and it's pretty smooth for daily use now
[Redmi Note 11 Pro+ 5G (peux)/POCO X4 Pro 5G (veux)] BR4UTAL:
i barely notice the bottom part when consuming multi media content (which is usually when this thing happens)

But yeah both are bad though it seems the flickering is at its worse in the top part?
[Redmi Note 11 Pro+ 5G (peux)/POCO X4 Pro 5G (veux)] 1qazwsx4:
No issues for me with anything mentioned in this thread