yashsingh1/xdaforums huggingface dataset:
[Motorola Edge 20 Pro] supeople:
即手机长时间处于待机状态，容易触发。举个例子，如果我按住屏幕一晚，第二天醒来用指纹打开手机，就很容易触发这个bug

**Translation provided**

That is, the mobile phone is in the standby state for a long time, which is easy to trigger. For example, if I hold down the screen for one night and wake up the next day to turn on the phone with my fingerprint, it's easy to trigger the bug.
[Motorola Edge 20 Pro] thomashastings:
Translation: That is, the mobile phone is in the standby state for a long time, which is easy to trigger. For example, if I hold down the screen for one night and wake up the next day to turn on the phone with my fingerprint, it is easy to trigger this.

Reply: Interesting, I'm also leaving the screen off for each night and nothing like this has happened. I'm not using GAPPS though, which might be an important difference here. Otherwise I'd suggest trying a fresh install after a complete wipe of the phone.
[Motorola Edge 20 Pro] cococooker:
Change your Wechat battery usage from unrestricted to optimized.
[Motorola Edge 20 Pro] Maxi693:
does "Ready for" work??
[Motorola Edge 20 Pro] thomashastings:
First of all, the display output feature is working well, I've successfully used it with several type-C docks.

Second, the Ready For feature itself is proprietary to Motorola's own Android spin, so that application cannot be installed on Lineage.

However, there are some libre alternatives that can be used to achieve similar functionality: DPI can be changed using SecondScreen to match your external display, and Taskbar can enhance the experience of switching between apps opened in movable windows.
[Motorola Edge 20 Pro] Maxi693:
okey

gracias

I'll keep it in mind
[Motorola Edge 20 Pro] thomashastings:
Since you asked, I ended up trying to get it working at least for my use case (browser, e-mail, Telegram, emulators).

The best experience was just setting the correct DPI with SecondScreen, and using Trebuchet as the launcher instead of the desktop mode that can be forced from the developer options. With this approach, the external screen is fully utilized, and there's also a dock for quick window switching provided by Trebuchet.

The only downside is that multitasking is limited to 2 side-by-side applications, but most apps seem to brake when forced into windows, so that doesn't seem that huge of a problem to me.
[Motorola Edge 20 Pro] Maxi693:
Thanks for the data always use lineage os on all terminals you use now i am interested for this device.

sorry for my English written through google translate
[Motorola Edge 20 Pro] thomashastings:
No problem, I'm glad I could help :)
[Motorola Edge 20 Pro] Maxi693:
S Is there any way to make the apps full screen?
[Motorola Edge 20 Pro] thomashastings:
The simplest approach would be using this app:

Fullscreen Immersive - Apps on Google Play

The app hides the Navigation and Status Bar either systemwide or per application

play.google.com
[Motorola Edge 20 Pro] Ezreal_HD:
Greetings to all, how to fix this problem in the firmware? Ruth did not install, but the safety net test does not pass. I also have a problem with the brightness of the screen when the phone reaches below 15%, the screen starts to flicker as a result for good and goes out, as far as I could figure out the problem in the LiveDisplay itself, when you turn it off, there are no problems.
[Motorola Edge 20 Pro] thomashastings:
Safetynet requires Google applications (GAPPS) to be installed. I haven't personally tested it on this device specifically, but this is the case in general.
[Motorola Edge 20 Pro] Maxi693:
YI solved it with the magisk hide props module

The CTS profile section
[Motorola Edge 20 Pro] mikib1:
I see also Android Auto won't connect properly to the car (Seat Alhambra 2019) in a stock works perfect. But stock is not good as Lineage... And the problem is that I have no idea how to grab bug data to add for check what is the problem. It star but screen just pop up for a second and then close and car write that phone in not unlocked (but it is).
[Motorola Edge 20 Pro] Maxi693:
I have a problem how to configure the hdmi audio output? I connect it and it is heard with the mobile
[Motorola Edge 20 Pro] thomashastings:
Yes, I've noticed that as well. Since I use separate audio gear, it didn't cause a problem for me. I use this USB audio card, it's automatically detected and used by Android. This might be a viable solution for you as well.
[Motorola Edge 20 Pro] ilia3367:
(y) For our phone was released on October 04, 2022 OFFICIAL !!! Lineage OS.

Congratulations to you! 🤝

Contributors:

SGCMarkus

electimon Jhon Diaz

MoetaYuko

SebaUbuntu Sebastiano Barezzi
[Motorola Edge 20 Pro] Maxi693:
oa big step for the edge 20 pro
[Motorola Edge 20 Pro] thomashastings:
Congratulations, amazing news! Thank you for all the work in supporting this device.
[Motorola Edge 20 Pro] dannywong3:
Hi , is the function "ready for" still working ??
[Motorola Edge 20 Pro] thomashastings:
See here:

https://xdaforums.com/t/unofficial-lineageos-19.4422649/post-87315387
[Motorola Edge 20 Pro] thomashastings:
Thanks again for the great work! I've been using these builds daily since the release, the overall experience is amazing. However, I've had the weirdest stability issues since the official release that weren't there previously:

- Bluetooth disconnects devices randomly, sometimes requires a restart to reconnect

- The lockscreen freezes with a blank screen (flashlight gesture works in the background), always requires a restart to make the phone usable

I followed the official LineageOS tutorial for the install, everyting was the latest version, including the stock firmware. Is there anything more I should try?
[Motorola Edge 20 Pro] ilia3367:
These questions are not for me. I am not the developer of this ROM.
[Motorola Edge 20 Pro] :
Somenone knows how to solve this?
[Motorola Edge 20 Pro] thomashastings:
Wow, I even replied to the original question back then, and now I have the same problem... If I'm not mistaken, this means that there should be a specific official firmware that works well with Lineage. Maybe the devs could tell us, which OFW they test against?

I wish I had written down the exact version of the one that came with my device, as that worked without any issues. Now I flashed the latest one recommended by the Lenovo tool, but that produces the blank screen issue with Lineage.
[Motorola Edge 20 Pro] :
Can you say me what version worked well for you with Lineage?
[Motorola Edge 20 Pro] thomashastings:
That's the problem... I have no idea what version that was. But I'm on a RETEU version now (XT2153-1_PSTAR_RETAIL_12_S1RAS32.41-20-16-6_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml), and that is causing issues. When I have time to test, I'll try the latest RETAIL version from here: https://mirrors.lolinet.com/firmware/motorola/pstar/official/RETAIL/, as that seems the most generic.

EDIT: I messed up, the latest RETAIL and latest RETEU are the same file, so it won't matter. Maybe a previous one should be better? I'm not really sure what version would be worth trying.
[Motorola Edge 20 Pro] :
I am already using It, the only glitch I noticed is that black screen issue. This glitch is very anoying so I would not recomend using It.
[Motorola Edge 20 Pro] thomashastings:
There will be an answer eventually. I don't have much time lately, but if you do have time, you could try the latest release for a few regions from lolinet. I'd suggest the one corresponding to your own region, as well as RETAIL, RETEU_RS, and maybe RETGB. If the filenames are identical, don't bother. If the filenames are very similar, you could do an sha256 check on them to see if they are indeed different.

There are numerous tools for flashing official firmwares on Motorola devices, but let me know if you intend to do the testing and need help.
[Motorola Edge 20 Pro] :
I will not test this, lack of time either.
[Motorola Edge 20 Pro] thomashastings:
I bought my pstar during the summer, and official Android 12 support only came during August. I thought that the last Android 11 release might work better, so I installed the one corresponding to my region. I don't want to call it way too early, but it seems to be pretty stable so far.

So choose your region from here, and look for the newest release with an "11" in its name:

lolinet mirrors - firmware, software, iso etc.

lolinet mirrors - powered by h5ai

mirrors.lolinet.com

Flash that before installing LineageOS and stability should be better.
[Motorola Edge 20 Pro] :
I had this idea, but the glitch I said before was there too. It may be a problem of my device, but I don't know for sure.
[Motorola Edge 20 Pro] thomashastings:
It might be also related to the region, as the hardware itself is supposed to be the same. Except for the radios maybe, but if you nail down the rest, the radio firmware corresponding to your region can also be flashed separately.

Latest Android 11 from RETAIL is what works for my device, it may work for yours as well.
[Motorola Edge 20 Pro] LSS4181:
+1 to this. Can confirm this issue is reproducible on LMODroid 20221201 also.

I've experienced it several times since flashing and never had it before flashing the recent ROM builds, so I'm not sure what might be broken. Most likely kernel or vendor side.

If you're confident that fingerprint unlock is the culprit, then I'll keep that in mind and avoid unlocking the phone this way if possible.

Managed to get some logcats when it happens. While this is technically not LOS 19, the bug might be the same.

Spoiler content hidden.
[Motorola Edge 20 Pro] LSS4181:
Another update on the issue. Today I managed to trigger that bug another time. This time it has nothing to do with the fingerprint sensor.

Actually, fingerprint sensors may not be the real cause of the bug, as it remained functional even after the bug has been triggered.

Attaching a logcat. Though as it was not until a few minutes later did I have the chance to dump logs, some information may be lost, but those that appear important remained. Attaching this as a file as it's too big to be put directly on the post.

It seems the phone is constantly having issues with suspend/resume, and it kind of soft-rebooted itself behind the scenes the moment when the bug triggered. As the screen can no longer be successfully initialized, the soft reboot process eventually finished without waiting for the screen. At this point everything else are wokring: physical buttons, fingerprint sensors, notifications, phone calls, and so on. Just that I cannot see anything nor answer calls directly.

UPDATE: After some further usage testing, I think I can rule out anything else being the culprit. I managed to trigger the bug while making phone calls, during which the screen turn off due to proximity sensor, and at one point the screen failed to turn back on, most likely the same cause as the last few times.

So in the end the issue might be a bug that has a chance to manifest when waking up the screen, that causes the screen to simply stop responding to any command for some reasons. Not sure if this is a hardware or firmware issue, but I never had this issue before flashing recent ROMs.

LATE EDIT: It seems another old issue I'm having is still reproducible on later builds but not as often as before. The phone may occasionally reboot on its own, and unlike normal shutdown/reboot, I would not be prompted for SIM PIN when the phone rebooted this way yet SIM still works. The ramoops I got from earlier builds kind of indicated some modem-related fatal error.

Further googling kind of suggests me to use a different baseband... so definitely I may need to flash related stuffs from different FW versions or regions to see if that'll alleviate the issues I'm having.
[Motorola Edge 20 Pro] LSS4181:
A bump on the previous display issue. It is still reproducible as of LMODroid 20221224 build, but less frequent than before. So far I only encountered the issue twice since the update, and managed to obtain a logcat of the second time when it happened. It seems there's another update (20221231). Will install it and see if there is any improvement regarding this issue.

Below is a logcat excerpt filtered with glogg by the keyword "dsi". It seems everything's well until the first occurrence of a DSI PLL(0) lock failure, and from that point on all subsequent commands ended in failure, as well as attempts to re-init the panel. Eventually the system gave up initializing the panel and ignored subsequent bl_level change requests.

Spoiler content hidden.
[Motorola Edge 20 Pro] LSS4181:
Okay. Reproduced the bug on 20221231 as well. Logcat excerpt here. However, the logcat this time seems to indicate that the PLL(0) lock failure happened much later than initial occurrence of the command transfer failure, so it's probably just that the screen would suddenly stop responding to commands and that's it. The PLL(0) lock failure is merely one of the consequences when the screen stopped responding.

Spoiler content hidden.

I just noticed something in common here when I compared the previous logcats: There are exactly 72 lines of "Command transfer failed" before the system realized the panel is no longer working and tried to re-initialize the panel, which would fail eventually. The logcat doesn't really tell me what exactly these 72 commands are, however. Additionally, it seems the driver would only try to re-initialize the panel up to twice before giving up and ignoring any further commands.

EDIT: Guess today is kinda a bad day. The screen died again, just about an hour since the last time I rebooted the phone via "adb reboot". The logcat I took before rebooting looked pretty identical to this one.

EDIT 2: After a day the screen died again. Not to mention at some point the system's brightness settings became borked as well. The screen was set to max brightness regardless of actual brightness setting, and from the logcat of that boot, the bl_level values being set were either 0 or 1024. Normally it could be any nonzero value between 1-1024 when turned on, depending on brightness setting, but not this time. After rebooting the phone everything returned to normal for now, including the brightness functionality.

Could it be the 20221231 build kinda regressed? With 20221224 the screen issue was rather infrequent, but now it feels like it's back to the state like 20221201...

EDIT 3: It really feels like the 20221231 build has regressed from the previous one. I only had 2 occurrences while the system was on 20221224, but now I'm back to about 1-2 times a day.
[Motorola Edge 20 Pro] rodrimax10:
Has the black screen issue been fixed on the 20230103 build? i have been flashing lineage every week with no luck. Never had that issue before it going official.

Also, why is there not a dedicated thread for it?
[Motorola Edge 20 Pro] LSS4181:
Indeed. Guess it should deserve its own thread, though it's going to take time to review all what I've found.

Should apply to both Lineage and LMODroid as they appear to be based on the same tree. The latter keeps USB debugging turned on by default, making it more trivial to obtain information about the problem.

EDIT: Here it is. Actually, with LMODroid 20230107, I found something new in the logcat that were not present before.
[Fire TV Q&A, Help & Troubleshooting] Michajin:
I love the firesticks, but I have non stop issue is that lack of memory 8GB, that is ate up mostly by the OS. Yes, you can add a usb and format it as internal, but 90% of apps from the amazon store block external install. I always run out of room. I am unlocked and rooted. Just wondering a good app or easy way to format a external and add to internal. Anyone have any thoughts?
[Fire TV Q&A, Help & Troubleshooting] Michajin:
Anyone have any idea how to add internal memory? i have not had any luck...
[Moto G Stylus (Moto G Pro) Questions & Answers] VandalEyes:
I picked up a used Moto G Stylus in hopes that i could use it to run octoprint4a for my 3d printer. The issue that I'm running into is the USB C port seems to only want to allow me to either charge the phone or to control the printer. I'd very much like for it to beable to do both. I havent been able to find alot of info on the subject other than mention that some folks have been able to tweak the kernel on other android devices so that it would take power and also work as a host/data transfer. has anyone had any success with this? I'm on android 11 Os.
[OnePlus 7 Pro Questions & Answers] ChimmyChanga:
Hello all,

Everything was working on my rooted oneplus 7 pro, until I applied the latest OTA update. Once that was installed and the phone rebooted, my once working mobile network was no longer working. The phone says no sim card detected and every few seconds the default phone app displays the force close crash dialog. Has anyone else encountered this issue? It looks like rolling it back to the previous OxygenOS version is the only solution, but I'm not quite sure how to go about that safely. Any help would be greatly appreciated.

The device is using Magisk and TWRP

I also tried uninstalling Magisk, but that did not resolve the issue.
[OnePlus 7 Pro Questions & Answers] hammered58:
Have you tried just doing a reset in settings?

.This is how I install stock oos

You can use MSM tool to revert OOS, or you can try this step:

1. Reboot twrp/lineage recovery, format data. Reboot bootloader

2. Fastboot boot into TWRP FBEv2

3. Sideload official TWRP 3.5.2.9-0 installer (found on TWRP website). Reboot recovery

4. Copy OOS 11.zip to internal storage,or copy to otg drive,Flash OOS 11.zip. Reboot recovery again

5. Format data in OOS stock recovery & Reboot

6. After boot into OOS 11, just local upgrade rom .zip again, you will have OOS on both slots

7. If root is needed fastboot flash magisk patched boot.img
[OnePlus 7 Pro Questions & Answers] ChimmyChanga:
I'll give that a shot today. Do you have the links to MSM and OOS11.zip ? Thanks
[OnePlus 7 Pro Questions & Answers] hammered58:
Index of /list/Unbrick_Tools

I don't have the oos 11 off hand , I know you can download the latest and greatest directly from OnePlus website under support
[OnePlus 7 Pro Questions & Answers] AlexanderKrakn2:
I have the same problem i cant do nothing
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Kakashi53:
Is there any way to get 48mp camera working in Android 12 custom rom on poco f3/k40 device it's not working on both anx and gcam. There has to be a way! Can anyone help.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Techguy777:
Have you tried the new fw 13.3.03 or whatever it is? I have the anx camera magisk module working on Evox rom and cherish OS but my wifi didn't work on cherish OS so I'm on Evox rom now again.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Kakashi53:
Are you using poco f3 is the 48mp working? For me 48 mp not showing in anx camera on my ancient os Android 12
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] shadowstep:
THREAD LOCKED

As per the Forum Rules:

Please search the forum for existing/similar threads before posting a new thread. For continuing discussion, kindly use the existing thread: https://xdaforums.com/t/gcam-48mp.4383225/

Regards,

shadowstep

Forum Moderator
[Windows Mobile Development and Hacking General] hellbender_it:
Hi Guys,

Ok, i've thrown the lure on Modaco and now i try here, I'm basically looking for someone to code this idea.

I'm an Omnia lucky owner and i really love it, particularly it's versatility.

I just regret the lack of cool interfaces (put Manilla 2d aside, it's awesome, but it's like having an htc device on out phones, not very exclusive). here are two quick layouts of an idea i had today, it's practically just eyecandy stuff, maybe not the top usability around but, you know, in our life we must satisfy ourselves...

Basically i'm looking for someone to code this, if it's mildly possible, 'cause i'm a poor lazy designer, and i don't chew any "if" or any "else"...

So here they are, a portrait and a landscape view of what's laying in my mind:

the idea is to have a spinning wheel of icons, transparent if possible (png with alpha?) that can grant access to the corrisponding main ambients of a mobile shell when tapped, just like SPB mobile shell or manilla, only more "graphic". The thing is conceived to be touch driven, with hrizontal sliding to spin the icons wheel and a vertical slide to access a second menu, just in case smile.gif The background (plane + rings) should be still, just a plain image.

I plan to design the "inside" of any section if i find someone crazy enough to follow my babblings, things like a photo gallery, a media player, a weather panel, etc.... (ye ye, like manilla) ando oh yes, no windows bars for now.

If there's someone who own the knowledge to understand the feasibility of this thing, my first question is "Flash lite?" cause i like very much the idea of having something very kinetic and possibly quick, and i'm not completely new to flash to keep me from helping.

Any Thoughts ?

P.S.: i'm sorry if some phrases in my post aren't clear enough, but i'm italian and i'm not so sure about my english.

Cheers.

Hellbender.

PPS: Frak, wrong section, please can a mod move it in the appropriate one ? I'm so lame.
[Windows Mobile Development and Hacking General] Black93300ZX:
I'm not an Omnia owner, nor can I help you, but I think it's a pretty cool looking idea. As for the language, I wouldn't have guessed until you said it that you weren't a native English speaker... No worries. I hope someone can help you get this idea off the ground, maybe having a few levels of wheels (i.e. flicking up and down gets to an inner or outer wheel from the one it's at) would make it more fun to navigate. Wheel 1 is your basics, and when you select something (like programs) wheel 2 lists the programs... Quick to get back and forth and easy to sort through. Good luck!
[Windows Mobile Development and Hacking General] zeezee:
it will be difficult to remove the window bars and softkeys while keeping the touchflo.

This will have to be done in C++ (basically rework the whole frontend.) -meaning we need to know alot about each API to be able to create a flawless frontend that works with WM6.0+ backend

This will be quite a project.

I like how it looks :D
[Windows Mobile Development and Hacking General] hellbender_it:
@Black93300ZX: thank you for your kindness :)

@zeezee: so i assume that products like SPB Mobile Shell are written in C++. I would be happy with just a fullscreen app that overlays on the today screen (SPB like), non necessarily a total integration like Manilla 2D. I haven't any idea about the performance.

"...meaning we need to know alot about each API.." you mean each single app i would add to that interface ? Because i was thinking that could be initially just some sort of launcher with graphical navigation, and adding features with time.

Obviously the BEST should be to intregrate every single function inside the same graphical environment, but for starters this is far from my expectations.

For now it's a spare time project, i'll take everything community can give to help.

Hellbender.
[Windows Mobile Development and Hacking General] psychoben87:
I really like the idea, especially the concept mock up interface you have developed. However I think you might get a better reception if you try and aim to make the application available for all HTC users, aka a universal front end to the essentials much like what SPB Mobile Shell does. Sadly my programming expertise is not that great to help out, sorry.

Best of luck getting others onboard to help you out with it!
[Windows Mobile Development and Hacking General] Black93300ZX:
That's true, if you made it generic for Windows Mobile I'm sure you could find plenty of developers here who would help you out. Unfortunately, asking for help with software for a Samsung on an HTC forum may present problems. :|
[Windows Mobile Development and Hacking General] psychoben87:
I could be wrong but I'm under the impression the Omnia runs windows mobile 6.1 which iirc is the first samsung phone to use windows mobile.