Develop Bugs

Loudspeaker and screen rotation

Hi Guys!
I already posted this in the specific SM-G935F thread, but maybe my two problems are not device-specific and some user of other phones had this issues or have an idea what cause my problems.
After searching in the internet and many forums I think that I am the only person in this world, who have this problems.
My Phone: Samsung Galaxy S7 Edge (SM-G935F/hero2lte)
Important: These two problems don't occur with the stock rom and everything worked.
I tested this by installing the original samsung rom (Android 6 and 7).
Also with Superman-ROM these problems don't occur.
Only with LineageOS and RessurectionROM (based on Lineage) I have this problems.
What I did (or not):
- ODIN: Installed latest version of TWRP
- TWRP: Installed SuperSU 2.83 and "dm-verity-disabler"
- TWRP: Installed latest LineageOS-Build (Full Wipe) + latest GApps (Pico) + addonsu-arm64
- I did not install any other apps in Lineage
- I did not change any settings
-> I have a clean version of LineageOS on my phone.
Problem 1:
During calls, when I turn on the loudspeakers, I can hear the other person, but I can not be heared by the other person anymore.
Then I turn off the loudspeakers and everthing switches: the other person can hear me now, but I can not hear the other person.
When I'm turning the loudspeakers again it will switch again (I hear the other, I'm not heared).
And so on, and so on ...
Problem 2:
Screen rotation from portrait to landscape mode ONLY works with the gallery and the icons of the camera.
In any other app (Browser, Messages, Settings ...) the screen stays in portrait mode.
And yes, I checked in the settings if screen rotation is active.
I found a solution with the app "Rotation Lock Adaptive", which automatically rotates the screen how it should be.
But that is unsatisfactory, I don't want a additional app to do core-function.
I don't believe the problems occur due hardware issues or what do your think? Beeing on stock rom everything works fine.
Greetz,
Isenberg

Really nobody has an idea what could cause my problems?

Isenberg said:
Really nobody has an idea what could cause my problems?
Click to expand...
Click to collapse
I have not
I experience the exact same problems. Flashed lastest stock-firmware (excluding system & data) and the latest official lineage os.
Sometimes rotation works, but most the time not.

black display and unresponsive on pie roms

Hi, I'm facing this issue with my oneplus 3 on custom roms based on android pie..it still happens and has become very difficult for me to use. im very eager to use pie on my device :/ .I've tried Havoc 9.0, Nitrogen OS 9.0, Pixel Experience and even skydragon but it still happens. Whenever the phone goes to sleep or i lock it, and then when i try to wake it up from the lock using either fingerprint or power button, the screen lights up in black and the two capacitive buttons light up, i can hear a lock screen sound also, but the display stays black. but the rom works like it should until the display doesnt turn off.. i have to reboot the device completely to solve it.. currently im on oxygen os 5.05. someone please help

Is your display original or has it been replaced? I have same problem because i replaced broken original LCD with cheap one from eBay.

I agree too facing the same issue and it's seems to be because of the duplicate display panel. I too replaced my display panel with a duplicate one recently and facing this issue (pressing the power button, but screens turns to black but pressing the power button again and again turns it on) since then. Not only pie ROM but also on Oreo custom roms. Only pie ROM that seems to be working is Nitrogen OS. There may be some problem or mismatch with display drivers. Also the profiles like SRGB and others are not working.
No problem on OOS 5.0.6

yeah man.. its a duplicate display :/ is there any workaround for this?

I asked in a telegram group. A person said a commit is required for third-party display to work.
I am not too much in development thing. So if anyone from you can search for it. That could help.
---------- Post added at 06:04 AM ---------- Previous post was at 05:55 AM ----------
http://github.com/LineageOS/android...mmit/8e9f68f01764d96669f6040bf9ae0c8ea4ec55e1
A person on telegram gave me this link to the commit.

I forwarded the commit and the message to Dev of Havoc OS. He said he will ask the holy angel for what he can do.
Hope he looks after it.

@pantu99 @stepi1
The latest skydragon rom comes with the fix for the panic we are facing. You can test it. I can't test right now.
Let me know too, if it works or not.

Piyush lalwani said:
@pantu99 @stepi1
The latest skydragon rom comes with the fix for the panic we are facing. You can test it. I can't test right now.
Let me know too, if it works or not.
Click to expand...
Click to collapse
great ! i shall test it right away.. hope it works.

just installed the latest build of the rom.. nope still the same issue..
pantu99 said:
great ! i shall test it right away.. hope it works.
Click to expand...
Click to collapse

pantu99 said:
just installed the latest build of the rom.. nope still the same issue..
Click to expand...
Click to collapse
Seems some additional commits are required.
Can you ask developer of Franco kernel about the comitts maybe he can help.

Piyush lalwani said:
I agree too facing the same issue and it's seems to be because of the duplicate display panel. I too replaced my display panel with a duplicate one recently and facing this issue (pressing the power button, but screens turns to black but pressing the power button again and again turns it on) since then. Not only pie ROM but also on Oreo custom roms. Only pie ROM that seems to be working is Nitrogen OS. There may be some problem or mismatch with display drivers. Also the profiles like SRGB and others are not working.
No problem on OOS 5.0.6
Click to expand...
Click to collapse
So OOS 5.0.6. doesn't have any issues with cheap display replacements?

j03x2 said:
So OOS 5.0.6. doesn't have any issues with cheap display replacements?
Click to expand...
Click to collapse
Yes I am using it currently. And Franco kernel also doesn't has any problem.
Other kernel give problems.

NitrogenOS also works. Guys please find a workaround, very hard to find better displays in market

Installed NitrogenOS 8.1 with fk-r39-anykernel2.zip (Franco Kernel) and everything works just fine now.
Interestingly, the problem persists in TWRP (I cannot let the display sleep during backup or restore otherwise, I cannot switch the display back on).

j03x2 said:
Installed NitrogenOS 8.1 with fk-r39-anykernel2.zip (Franco Kernel) and everything works just fine now.
Interestingly, the problem persists in TWRP (I cannot let the display sleep during backup or restore otherwise, I cannot switch the display back on).
Click to expand...
Click to collapse
Nitrogen OS pie didnt had the problem with stock kernel too
Try it.
Fkr39 why not the latest?

Piyush lalwani said:
Nitrogen OS pie didnt had the problem with stock kernel too
Try it.
Fkr39 why not the latest?
Click to expand...
Click to collapse
There is no suitable version of Xposed framework for NOS 9 (pie).
Fkr44 (latest version of the kernel) showed more lag time before the screen turns on (like 2-3 sec).
Had the best experience with the older kernel.

Any fixes or working rom guys ? I really want pie in my OnePlus 3

Have you tried Resurrection Remix?
I had a similar issue with Havoc even with the original screen. So far, RR has been fine.

Android pie

Which is the best pie Rom?

[email protected] said:
Which is the best pie Rom?
Click to expand...
Click to collapse
The one that suits your needs?
Try some and find out

I have only one device so if I mess that up. I am screwed.
So better to know from someone who has used.

Cr droid! Best stable pie rom!

Easy easy liqid remix

Thankyou all for the responses.

There is no stable Pie ROM yet.
All of them have broken keystore, so certificate based VPN's won't work.
But if you don't use VPN i can recommend AEX or crDroid.

I tried two Pie-ROMS (crDroid 5.0[24-12-2018] and Havoc-OS-v2.0-20190101) and with both I had several issues:
1) could not install Magisk 18.0 - fixed by installing TWRP 3.2.2 build from Linage 15.1 here: https://androidfilehost.com/?fid=5862345805528044694
2) could not get LED flashlight in Havoc running, third-party apps also did not work - just no response, don't know how to approach a fix/error search
3) camera(s) always force-closed on start, tried natively installed and gcam-ports - restarts, removing pins + restarts, flashing extra zip (https://forum.xda-developers.com/le...enovo-p2-kuntao-main-camera-fix-hal3-t3819258) did not work
4) could not connect to my hidden SSID 5GHz WIFI, although hidden extra option when entering login information was checked - this is especially frustrating, as I have no idea how to solve this
5) Update2: and with AOSP, I cannot write with Open Camera or other third party apps to the SD card.
If anyone has suggestions how to fix any of these, you are welcome!
Update: I also tried AOSPExtended6.1-Unofficial which did not show issues 2-3.

abprie said:
I tried two Pie-ROMS (crDroid 5.0[24-12-2018] and Havoc-OS-v2.0-20190101) and with both I had several issues:
1) could not install Magisk 18.0 - fixed by installing TWRP 3.2.2 build from Linage 15.1 here: https://androidfilehost.com/?fid=5862345805528044694
2) could not get LED flashlight in Havoc running, third-party apps also did not work - just no response, don't know how to approach a fix/error search
3) camera(s) always force-closed on start, tried natively installed and gcam-ports - restarts, removing pins + restarts, flashing extra zip (https://forum.xda-developers.com/le...novo-p2-kuntao-main-camera-fix-hal3-t3819258) did not work
4) could not connect to my hidden SSID 5GHz WIFI, although hidden extra option when entering login information was checked - this is especially frustrating, as I have no idea how to solve this
If anyone has suggestions how to fix any of these, you are welcome!
Click to expand...
Click to collapse
Thankyou for deep insight. I wanted to install but after checking the thread and your comment I think I have to wait.

Fingerprint gestures occasionally stop working in new ROM versions

A month ago or so I updated my CrDroid 5.3 to a newer version and I noticed that sometimes my FP gestures stop working. I then flashed LineageOS, same thing. Also tried AospExtended and Resurrection.
In each ROM the gestures work for a few moments and then the button just stops registering. I need to press and hold it for a few tries, like 10 seconds or so. It then starts working again, but stops again moments later.
So I wonder if I am the only one with this problem. I clean flashed each new version. I wonder, does it maybe have to do with some new security update regarding fingerprints? I can imagine all ROMs include the newest security patches.

Same here. It's a weird bug! sometimes clearing the cache will fix it, sometimes not.

Anyone have a permanent solution?

I have been using Bootleggers 4.3 (12 Sep. 2019) version for few days and it hasn't have this bug. I was also facing home button gesture issue in Havoc 2.8 and wanted to try a new ROM.

alirazaagha said:
I have been using Bootleggers 4.3 (12 Sep. 2019) version for few days and it hasn't have this bug. I was also facing home button gesture issue in Havoc 2.8 and wanted to try a new ROM.
Click to expand...
Click to collapse
Thanks, I'll check this one out.

alirazaagha said:
I have been using Bootleggers 4.3 (12 Sep. 2019) version for few days and it hasn't have this bug. I was also facing home button gesture issue in Havoc 2.8 and wanted to try a new ROM.
Click to expand...
Click to collapse
In the latest version of Havoc and Syberia, this error has been fixed

alirazaagha said:
I have been using Bootleggers 4.3 (12 Sep. 2019) version for few days and it hasn't have this bug. I was also facing home button gesture issue in Havoc 2.8 and wanted to try a new ROM.
Click to expand...
Click to collapse
Dude. That ROM doesn't even have FP gestures. I just wasted my time on installing it. Its colors are also oversatured and it doesn't even have other color profiles. Why did you suggest it..?

kerelberel said:
Why did you suggest it..?
Click to expand...
Click to collapse
Because I'm still using it and there is no problem for me so far

alirazaagha said:
Because I'm still using it and there is no problem for me so far
Click to expand...
Click to collapse
It doesn't have FP gestures..

kerelberel said:
It doesn't have FP gestures..
Click to expand...
Click to collapse
I installed BL first time with nano gApps and there was no problem. I later tried Evolution X ROM for a change and didn't like it for few reasons. Then came back to BL. This time, I installed Pixel gApps. During setting up the phone, I misspelled my email address and when I tried to adjust it by going back, the FP didn't work. I rebooted the phone and since then, there is no problem. TRY REBOOT ONCE!
You can correct colors through Kernel Adiutor though.

I run LineageOS 16, and sometimes after a update, the FP gestures are not working. In LOS there is a menu to switch it on/off. Switching it off and then back on resolves the issue for me (but in the recent updates, I didn't encounter the issue, maybe it was fixed).

[clark] Unofficial 18.1

It's that time of the year....
Recovery: download (6th Mar '21)
Gapps: download (16th Feb '21)
Lineage 18.1: download (8th Mar '21)
Please report stuff that doesn't work in this thread.
Update: 8th March
Recently fixed:
Bluetooth
Setting a lock screen
AUX / Line Out
Encryption
Gallery speed
Limitations of the current Lineage version:
VoLTE is disabled (will unfortunately not be able to fix that easily)
Dual SIM is not working (for devices that have Dual SIM)
Speakers do not sound as good as on stock
Camera is not as good as stock
Battery life when the screen is on is better on stock than on Lineage
------------
For developers:
device: https://review.lineageos.org/c/LineageOS/android_device_motorola_clark/+/304226/2
kernel: https://review.lineageos.org/c/LineageOS/android_kernel_motorola_msm8992/+/304218/1
vendor: https://github.com/chrmhoffmann/proprietary_vendor_motorola/tree/lineage-18.1
Note: Credits go to the usual lineage team from whom the device benefits enormously. Also the previous device maintainers have done a great job and we're still benefiting from that. E.g. the camera reverse engineering.

chrmhoffmann said:
It's that time of the year....
Recovery: download (16th Feb '21)
Gapps: download (16th Feb '21)
Lineage 18.1: download (16th Feb '21)
Please report stuff that doesn't work in this thread.
------------
For developers:
device: https://review.lineageos.org/c/LineageOS/android_device_motorola_clark/+/304226/2
kernel: https://review.lineageos.org/c/LineageOS/android_kernel_motorola_msm8992/+/304218/1
vendor: https://github.com/chrmhoffmann/proprietary_vendor_motorola/tree/lineage-18.1
Click to expand...
Click to collapse
Hello Chris, first of all, thanks for continuing on 18.1. I installed the rom and it booted fine. The set-up was buggy and laggy an kept crashing on setting up screen pattern. So I can't set screen pattern/pincode/password. Also I installed some apps from play store like whatsapp,gmail, telegram and they are doing fine. The phone gets hot and battery drains fast. Ambient display is a bit buggy, it's not working everytime. Anyways for the first build it's quite good. Thanks again
Maybe anybody else can also test?

Yes, setting up lock screen is broken. Will fix it in next build.
Chris

!

[QUOTE = "chrmhoffmann, post: 84511557, member: 361777"]
Да, не работает настройка экрана блокировки. Исправлю в следующей сборке.
Крис
[/ ЦИТИРОВАТЬ]
Dear Chris, everything is superb, but the function of broadcasting the screen in the quick settings menu does not work when connected (miracast) the phone is overloaded

I think bluetooth headsets are broken.
Chris

chrmhoffmann said:
I think bluetooth headsets are broken.
Chris
Click to expand...
Click to collapse
I can confirm that, it connects with my Haylou GT1 Pro but no sound.

Fixed. Uploading new build that fixes bluetooth and screen lock.
Note: If you have previously tried to setup lock screen, you will have to reset device (factory reset/wipe). Otherwise the device will crash right after bootanim stops. Sorry for that!!!

chrmhoffmann said:
Fixed. Uploading new build that fixes bluetooth and screen lock.
Note: If you have previously tried to setup lock screen, you will have to reset device (factory reset/wipe). Otherwise the device will crash right after bootanim stops. Sorry for that!!!
Click to expand...
Click to collapse
Thank you Chris, bluetooth and screen lock are fixed!

chrmhoffmann said:
Fixed. Uploading new build that fixes bluetooth and screen lock.
Note: If you have previously tried to setup lock screen, you will have to reset device (factory reset/wipe). Otherwise the device will crash right after bootanim stops. Sorry for that!!!
Click to expand...
Click to collapse
Can it be dirty flashed or should we do a clean install? It's cumbersome working with LOS recovery so the less I have to deal with it the better. Other than recovery it's a nice smooth rom. Thanks again

Wheels564 said:
Can it be dirty flashed or should we do a clean install? It's cumbersome working with LOS recovery so the less I have to deal with it the better. Other than recovery it's a nice smooth rom. Thanks again
Click to expand...
Click to collapse
I did a clean install, you can try dirty flash.

moviefirst said:
I did a clean install, you can try dirty flash.
Click to expand...
Click to collapse
I did a clean install. Since I have two of these phones I'm using this one for testing purposes for now and have 14.1 on the other one for daily use. At some point I'll change over to the 18.1 phone. I really like that dark theme is enabled on this rom that 14.1 never had It helps save battery.

which version of magisk will work?

Could someone test Netflix?

chrmhoffmann said:
Could someone test Netflix?
Click to expand...
Click to collapse
Seems to work fine in the U.S. on wifi. I'll let it run for a while to make sure it's stable. It appears to be running 1080p.

chrmhoffmann said:
Could someone test Netflix?
Click to expand...
Click to collapse
Netflix working here in the Netherlands, but the phone is lagging and takes time to open apps. Also I think battery was better in 17.1

In the camera I've noticed there's no icon to save to sdcard. also unless they've change snap camera I can't get the back or home button to come up to exit camera. I have to long press the power button to get access to home icon.

[email protected] said:
which version of magisk will work?
Click to expand...
Click to collapse
Latest version 21.4 works.
Wheels564 said:
In the camera I've noticed there's no icon to save to sdcard. also unless they've change snap camera I can't get the back or home button to come up to exit camera. I have to long press the power button to get access to home icon.
Click to expand...
Click to collapse
.
Swipe down from top to see home button. Save to sd card did not work on 17.1 so he removed the icon. Thanks for helping me find new forum!
Link to gapps is not working here.
Sorry for partial reposting this from 17.1 forum. Seems very functional on WiFi. Phone does not read VZW SIM on boot and can't pick up APN. I had to choose VZWINTERNET APN. Then LTE works for 30 seconds. Data drops for maybe a minute, then falls back to 3G which works. If LTE worked I think we would be golden.
Also get "DM config update keeps stopping" error. Not sure if this is related to SIM. I used NikGapps but don't think it is related.
Photos can not access SD card but Files has no problem. Edit. My bad. Photos works fine.

kb8no said:
Latest version 21.4 works.
.
Swipe down from top to see home button. Save to sd card did not work on 17.1 so he removed the icon. Thanks for helping me find new forum!
Link to gapps is not working here.
Sorry for partial reposting this from 17.1 forum. Seems very functional on WiFi. Phone does not read VZW SIM on boot and can't pick up APN. I had to choose VZWINTERNET VPN. Then LTE works for 30 seconds. Data drops for maybe a minute, then falls back to 3G which works. If LTE worked I think we would be golden.
Also get "DM config update keeps stopping" error. Not sure if this is related to SIM. I used NikGapps but don't think it is related.
Photos can not access SD card but Files has no problem.
Click to expand...
Click to collapse
Get a logcat when your trying to use LTE for Chris. I don't have a sim in my 18.1 phone or I would.

Link to MindTheGapps from OP is obsolete and updated link found on LOS link. I used NikGapps before and started over with clean flash using MindTheGapps but found it made no difference. Phone still does not read VZW SIM on boot and can't pick up APN. I had to again manually choose VZWINTERNET APN. Then LTE works for 30 seconds. Data drops for maybe a minute, then falls back to 3G which works and I get about 2 Mbps. Continue to get error "DM config update keeps stopping". I now believe this is related.
Has anybody yet tried TWRP from 17.1 thread?
Advanced restart is missing from developer options.
Addendum: I put in my ATT SIM. It found the APN and imported it correctly. It started LTE and similarly died. Data never came back at a lower rate.