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.
Hi everyone, first of all, thanks for being such nice community!
I've just received my new Mi5S, played with it for a bit and flashed xiaomiu.eu stable (because I was told to not use the 'fake' banggood global rom) , then flashed the latest xiaomi.eu dev (Android 7.0, I guess).
Everything was fine, but I tried to use the fingerprint sensor and it works very poorly, having to press more than 100 times to setup my finger, and then, it was very inconsistent to unlock.
I've tried many roms to try to understand the problem: Ressurection Remix, Xiaomi Global Stable 7.5.25 (using TWRP, flashing over "fake banggood global rom"), all have the same issue.
My question are...
Can i fix it flashing the global xiaomi image fastboot? (Maybe it's a corrupt/incompatible fingerprint firmware?)
Is there any difference from using TWRP and flashboot to flash? (I couldn't install the stable ROM after installing the dev, in order to downgrade, i restored my backup from 'fake banggood global rom', and then flashed xiaomi.eu stable // maybe the .zip doensn't come with all firmware? //
Will my bootloader LOCK if i flashboot? (my phone came unlocked from banggood).
Maybe my sensor is faulty? I guess it was working with the "banggood fake rom", but I tested briefly (it unlocked a few times, at least).
Sorry my english!
This is normal. We need to wait for Xiaomi to fix it.
I saw your post on Xiaomi eu too ?
Fingerprint for mi5s is well optimized now, it only takes 0.5 sec for me to unlock. Try to update your rom.
Well, try to record your finger horizontally.
For detailed how to, check this post http://en.miui.com/thread-439364-1-1.html
Try different techniques when registering your Fingerprint. I found applying a tiny amount of pressure on the sensor worked best for me. You don't need to press it you just have to make sure your skin is flattened on the surface.
Also a mistake I found when I saw my friend registering his fingerprint was he was registering around the center of his thumb, while in practice he used the tip of his thumb.
If done correctly I can unlock my phone scanning my thumb vertically or horizontally even though I registered it only vertically.
Try to install ZCX TWRP, mount persist partition, go to persist through TWRP file manager and rename fingerprint folder to fingerprint-old, after that, as I think, wipe needed.
Same here, have Mi 5s with MIUI 8.0.3.0 (MAGMIDI), received update to 8.5.3.0 (MAGMEID). Was happy to finally receive some update, but everything is pretty much the same. Hoped at least that the fingerprint sensor will perform a little better, but until now its even worse, doesn't respond at all. This **** sensor piss me off, before this phone I used fingerprint all the time... We get zero support from Xiaomi about this fingerprint sensor!! This is my first and last Xiaomi mobile device..
Anyway before reading this thread I considered installing different roms , maybe this stable one from Xiaomi.eu : xiaomi.eu_multi_MI5S_V8.5.3.0.MAGCNED_v8-6.0.zip
But in my understanding that didn't solve it for you, right?
quarvin said:
Same here, have Mi 5s with MIUI 8.0.3.0 (MAGMIDI), received update to 8.5.3.0 (MAGMEID). Was happy to finally receive some update, but everything is pretty much the same. Hoped at least that the fingerprint sensor will perform a little better, but until now its even worse, doesn't respond at all. This **** sensor piss me off, before this phone I used fingerprint all the time... We get zero support from Xiaomi about this fingerprint sensor!! This is my first and last Xiaomi mobile device..
Anyway before reading this thread I considered installing different roms , maybe this stable one from Xiaomi.eu : xiaomi.eu_multi_MI5S_V8.5.3.0.MAGCNED_v8-6.0.zip
But in my understanding that didn't solve it for you, right?
Click to expand...
Click to collapse
Yes, I've installed latest EU and it didnt fixed my fingerprint.. maybe we have faulty smartphones?
baron br said:
Yes, I've installed latest EU and it didnt fixed my fingerprint.. maybe we have faulty smartphones?
Click to expand...
Click to collapse
I've already solved the problem in my phone.
Look at this thread, hope will help you too:
https://forum.xda-developers.com/mi-5s/help/firmware-to-fix-fingerprint-sensor-t3653847
Hi guys.
I wanted to say something here. In this forum and elsewhere in the internet people are complaining about "Ok Google" being unavailable/greyed out.
People often recommend others to "flash NikGapps/MindTheGapps/FlameGapps" whatever else, which doesn't solve the issue and makes people waste their times.
I am not a dev, so I might be a bit mistaken, but I talked to some devs from StyxOS/LineageOS devs and they all told me it is because of something called "hotword blobs" that is needed by Android 11. Without those it doesn't work, regardless of which gapps you're using.
AFAIK, the it only works in LineageOS 18.1 for the Redmi 7 device. I tried it and it works with any Gapps (mindthegapps, NikGapps, FlameGapps and OpenGapps). Beware that the OpenGapps version is broken and a lot of stuff goes wrong with it, you shouldn't use it.
ROMs I tested where it doesn't work (only official ROMs)
- Nusantara 3.0 (Android 11)
- StyxOS
- PixysOS
- HavocOS 4.5/4.6
and a few other unnofficial ROMs
This doesn't mean there's a problem with the ROM. Except for HavocOS, which I just installed to check whether this was working, I used all the other ROM's for a few days or weeks and they're all stable.
ROM I tested where it works:
So far:
- LineageOS 18.1
- Any Android 10/MIUI ROM
If you choose LOS 18.1 be aware that SafetyNet is currently broken and MagiskHide Props won't fix it, and that flashing custom kernels will trigger all sorts of weird bugs (phone doesn't reboot/shutdown, simcard data switches itself, distorted audio, you name it).
Flashing Xiaomi.eu 12.5 causes bootloop, you need to flash disabled vbmeta for it to work. If I'm not mistaken OK Google is working in it too.
Thanks.
Thanks for your post, I have the same issue and didn't understand what was wrong.
At least now I know it isn't about Gapps.
It would be great if somebody knows how to add these blobs to ROMs not having them already.
Disclaimer
Your warranty will be void
Some carriers' Terms of Service prohibit device modifications
Modifying will trip Samsung Knox and SafetyNet, so be aware that some apps will cease to work
I AM NOT RESPONSIBLE FOR BRICKED DEVICES, FAILED ATTEMPTS AND OTHER CAUSES OF IMPROPER USAGE OF THIS GUIDE!Now that we got that out of the way, we can continue.
Unlocking the BootloaderUNLOCKING THE BOOTLOADER WILL ERASE ALL OF YOUR DATA!
Go into Settings > About Phone > Software Information
Find Build Number and quickly tap it 7 times. This will enable Developer Options
Find OEM Unlocking and USB Debugging options and enable them
Turn off the phone
Hold Volume Up and Volume Down while connecting your phone to a PC to boot into Download Mode
Read the Warning carefully to understand it and then if you want to continue press Volume Up
On the Unlock Bootloader screen, press and hold the Volume Up button one more time (This is the step that erases all of your data, if you don't want to do it, now is the time to turn back!)
After the automatic reboot, repeat steps 1. - 3. and make sure that OEM Unlocking is greyed out and enabled
Congratulations! You bootloader is now unlocked.
Flashing a Custom RecoveryCredit to @BlackMesa123 for this guide.
Rooting your Phone
Download the latest version of Magisk on your Computer
Follow the Official Installation Guide from Magisk developers
Flashing a GSI (Generic System Image)
Choose a GSI from this List
Power Off your phone and connect it to your Computer
Hold Volume Up and Power buttons, after the logo appears, release only the Power button, this will boot you into TWRP
Do a Wipe and transfer the GSI file from you Computer to your Phone
Click Install >Image Flashing, find your transferred GSI file and tap on it.
Toggle the System Image option and flash the file.
After flashing Format Data to be able to boot into your new System.
I know your Camera doesn't work, don't worry check out this Post to get it to work again.
Useful Resources
A52s bootloader/modem collection repository
OrangeFox Recovery
SafetyNet Fix for Magisk (Zygisk)
Custom ROMs: RayOS (One UI 4.1), NcX (One UI 5.0)
Mesa's Custom Kernel
Credit to @BlackMesa123 @Ryzen5950XT @ShaDisNX255 for the additional resources.
That's it! Thank you for following the guide and enjoy your unlocked Samsung.
This is very helpful thanks
Thank you for the guide. Here's some additional resources/changes that can be added in the post:
- A52s bootloader/modem collection repository
- OrangeFox Custom Recovery, same as TWRP but with a different UI
- SafetyNet and (some) Knox features can still work with the correct adjustments. See the SafetyNet fix for Magisk (Zygisk) or custom ROM's such as RayOS (One UI 4.1), NcX (One UI 5.0)
- Mesa's Custom Kernel, greatly improves device's performance
Hoping to see the list enhanced soon.
BlackMesa123 said:
Thank you for the guide. Here's some additional resources/changes that can be added in the post:
- A52s bootloader/modem collection repository
- OrangeFox Custom Recovery, same as TWRP but with a different UI
- SafetyNet and (some) Knox features can still work with the correct adjustments. See the SafetyNet fix for Magisk (Zygisk) or custom ROM's such as RayOS (One UI 4.1), NcX (One UI 5.0)
- Mesa's Custom Kernel, greatly improves device's performance
Hoping to see the list enhanced soon.
Click to expand...
Click to collapse
Thank you for the links, thread is now updated.
Quick question, with MCK, should I wipe everything before/after flashing and will it work with PE+ GSI?
kzyx said:
Thank you for the links, thread is now updated.
Quick question, with MCK, should I wipe everything before/after flashing and will it work with PE+ GSI?
Click to expand...
Click to collapse
You shouldn’t wipe anything when flashing the kernel. If the stock kernel works fine, I don’t see why mine shouldn’t
Everything is working perfectly, thanks for the guide. I installed the PixelExperience GSI but for some reason Fingerprint sensor is not working. The process is stuck on "Touch the sensor" and the sensor is not lighting up. Yes, I set the color of fingerprint sensor to White (and even tried all other colors).
I even have the following options checked
- Enable Extra Sensor
- Enable workaround for broken fingerprint sensor
- Enable workaround for white-ish screen
Any help will be appreciated, thanks.
Mian-786 said:
Everything is working perfectly, thanks for the guide. I installed the PixelExperience GSI but for some reason Fingerprint sensor is not working. The process is stuck on "Touch the sensor" and the sensor is not lighting up. Yes, I set the color of fingerprint sensor to White (and even tried all other colors).
I even have the following options checked
- Enable Extra Sensor
- Enable workaround for broken fingerprint sensor
- Enable workaround for white-ish screen
Any help will be appreciated, thanks.
Click to expand...
Click to collapse
I don't know what could be the issue, maybe try to google or try disabling and enabling the fingerprint lock again.
I have tried few GSI Roms. Here is my summary:
Android 13
- AOSP, Android 13, No image with GAPPs pre-installed and cannot seem to install it. Tried NikGAPPs, and LiteGAPPs, both didn't work
- Google GSI, Android 13, same issue
- Pixel Experience, Android 13, GAPPs pre-installed but Fingerprint sensor won't get detected.
Android 12
- AOSP, Android 12, GAPPs pre-installed, Fingerprint sensor detected (changing color to white). Will stick to it unless there is an issue detected.
Mian-786 said:
I have tried few GSI Roms. Here is my summary:
Android 13
- AOSP, Android 13, No image with GAPPs pre-installed and cannot seem to install it. Tried NikGAPPs, and LiteGAPPs, both didn't work
- Google GSI, Android 13, same issue
- Pixel Experience, Android 13, GAPPs pre-installed but Fingerprint sensor won't get detected.
Android 12
- AOSP, Android 12, GAPPs pre-installed, Fingerprint sensor detected (changing color to white). Will stick to it unless there is an issue detected.
Click to expand...
Click to collapse
Thanks for the feedback, have you tried any ROMs instead of GSIs?
You have links for them in this thread.
kzyx said:
Thanks for the feedback, have you tried any ROMs instead of GSIs?
You have links for them in this thread.
Click to expand...
Click to collapse
Nope, I tried to find a good custom rom for A52s but couldn't find any.
What about volte and hotspot on GSI pixel experience 13?
Mian-786 said:
I have tried few GSI Roms. Here is my summary:
Android 13
- AOSP, Android 13, No image with GAPPs pre-installed and cannot seem to install it. Tried NikGAPPs, and LiteGAPPs, both didn't work
- Google GSI, Android 13, same issue
- Pixel Experience, Android 13, GAPPs pre-installed but Fingerprint sensor won't get detected.
Android 12
- AOSP, Android 12, GAPPs pre-installed, Fingerprint sensor detected (changing color to white). Will stick to it unless there is an issue detected.
Click to expand...
Click to collapse
Thanks for your summary,
Is there any experience with MicroG on this device with AOSP 13?
7slaper said:
Thanks for your summary,
I'm on AOSP 13 now, but perhabs it's better to go back to 12. I'm very interested in the AOSP with the GAPPs pre-installed. Could you share a link to the file?
Click to expand...
Click to collapse
I got the image from AOSP under the official Android 12/12L section. You can find release here. The exact image I got is the system-squeak-arm64-ab-vndklite-gapps-secure.img.xz one since the standard gapps one came with an app called "superuser" which I couldn't seem to uninstall (I tried the scripts to remove supersu). This caused my banking apps to not run. That is why I installed the "secure" one and then installed Magisk and added my banking apps to the defylist.
Zhazhael said:
What about volte and hotspot on GSI pixel experience 13?
Click to expand...
Click to collapse
I think VoLTE was available as an option in one of the ROM I tested but I don't remember exactly. Currently AOSP 12 doesn't support it. Hotspot worked on every ROM just fine.
Mian-786 said:
I got the image from AOSP under the official Android 12/12L section. You can find release here. The exact image I got is the system-squeak-arm64-ab-vndklite-gapps-secure.img.xz one since the standard gapps one came with an app called "superuser" which I couldn't seem to uninstall (I tried the scripts to remove supersu). This caused my banking apps to not run. That is why I installed the "secure" one and then installed Magisk and added my banking apps to the defylist.
Click to expand...
Click to collapse
Hi Mian,
Thanks for your response. When I typed my question I realized that in the end I want to have and de-googled phone. So I changed my question in the direction of MicroG. I didn't expect you to be so quick with answering.
7slaper said:
Hi Mian,
Thanks for your response. When I typed my question I realized that in the end I want to have and de-googled phone. So I changed my question in the direction of MicroG. I didn't expect you to be so quick with answering.
Click to expand...
Click to collapse
I haven't tried MicroG in any of the ROM. I just to have as little Google apps as possible but if you do find a good guide, let me know, I will try to use a de-googled phone.
Thx, all worked.
Mian-786 said:
I haven't tried MicroG in any of the ROM. I just to have as little Google apps as possible but if you do find a good guide, let me know, I will try to use a de-googled phone.
Click to expand...
Click to collapse
I've installed MicroG. But it seems AOSP doen't allaw support system spoofs signature. Play services (GmsCore) is installed but without the spoofed signature it can't do much I guess...
I have been using AOSP Android 12 for the past week or so. Most of the things just plain works but somethings don't. Here is the list of things that are not working so you can decide if the hassle of installing GSI is worth it or not.
- Proximity Sensor is worse than it was in OneUI. Yes, it is a virtual sensor but on OneUI, it worked better. Now, it is worse. More often than not, it turns on the screen during the call. It would have been better if it simply didn't work.
- The viewport of default camera App in the AOSP displays picture in 4:3 but the camera hardware is giving out 16:9, so the viewport was squeezed. After installing GCam everything is good.
- Fingerprint Sensor simply doesn't work in-app like those in banking apps. It works on the lock screen but nowhere else.
- USB Audio Devices don't work. I have a USB-C to A OTG where I used to insert my headphones. On OneUI they used to work but here they don't. Storage devices work.
- 120 Hz felt smoother on OneUI.
Hello everyone
I managed to install LineageOS with working GApps and camera using this guide, so a big thanks to everyone who worked on flashing this phone
If anyone wants to install it, you need to:
Chose a bgN package (I installed this one : https://sourceforge.net/projects/an...UNOFFICIAL-arm64_bgN-vndklite.img.xz/download). It includes the GApps. You won't be able to install GApps after installing a vanilla (bvS / bvN) package. For some reasons, the /system partition is too small.
For unlocking camera and install magisk, just flash this kernel : https://forum.xda-developers.com/t/kernel-12-13-a528b-n-mesas-custom-kernel-r4.4490653/
I also installed magiskhide prop conf module, but I'm not sure it changed anything and the camera fix was probably already in the MCK. You can find it here anyway : https://forum.xda-developers.com/t/...safetynet-prop-edits-and-more-v6-1-2.3789228/
When I flash a custom A13 ROM, the adaptive brightness on my Poco F3 stays on 13% (only adjusts when I move the slider but then goes down later), and fingerprint sensor does not appear under the Security settings.
I have flashed full MIUI ROM both 14.0.7 and 14.0.4 and afterwards, followed the respective flashing instructions of each ROM (BananaDroid, GhostDroid, AlphaDroid, Evo-X) but each time these 2 issues occur.
On A12 custom ROM, I was not having these problems.
I hope someone can shed some light on what I can do to alleviate this.
FYI, I live in Canada and bought the phone on Ali Express which has Russian print on the box. I don't know if this makes a difference or not with the MIUI stock ROM I should flash.
Thanks for any help.
maybe install latest MIUI through fastboot and then try a13 custom ROMs?
Kusay_1 said:
maybe install latest MIUI through fastboot and then try a13 custom ROMs?
Click to expand...
Click to collapse
I tried that multiple times plus install using recovery MIUI ROM but same result.
nickelnine said:
I tried that multiple times plus install using recovery MIUI ROM but same result.
Click to expand...
Click to collapse
I heard about firmware causing trouble with fingerprint scanners, but not removing the option all together, perhaps try multiple firmwares and see if this fixes it?
About auto brightness, do you have anything covering your screen? Maybe that could be the problem
Is miui working well?
Surely if miui on a13 works, then this should be a custom Rom thing
Nothing covering the screen but I reflashed from scratch and now auto brightness works better but still not how it used to be on A12 but it's fine for now. Fingerprint scanner still not available although when I went back to MIUI 14.0.4 and 14.0.7 it was missing from there too so I'm not sure what the problem is. I do have face unlock though.