I have been running LineageOS+MicroG on my last 3 phones but am mostly a novice. LineageOS just packages things well enough that getting it installed is pretty easy. Most recently, I updated to 17.1 on my Payton device, and voila, I've got a problem where the phone reboots after powering on. Happens much faster with the radios on, much slower with safe mode and airplane mode on. So the obvious answer is usually "flash back to stock and try again". Here come my questions... Please keep in mind I also run Linux.
1. When people talk about going back to stock, doesn't this always entail losing your data? How do those of you who use your phone as a daily driver manage this? I've not heard great things about doing TWRP backups, and the amount of configuration I have to do at new-install time is crazy.
2. While running LineageOS or other such custom ROMs... How do you get "hardware updates": upgrades to things like modem/radio firmware that are outside the realm of the OS (if there is such a thing). I've had a few problems (including the current one) that I _suspect_ are related to running old "firmware" as I would normally call it. The solutions that I _think_ I've seen for this look like they are Windows-specific and also require going back to stock or losing your data. It's puzzling to me why updating hardware would require going back to stock, unless you need to let the stock OTA updates install in order to actually GET that firmware.
1) To my knowledge and at least for me, 'we' are using Android 9 firmware with Android 10 OS. I do not expect any further firmware updates.
2) I've been told that LOS is running slower on X4 compared to other ROMs such as Pixel Experience, but I can't speak for either as I use HAVOC. I can't speak for the rebooting issue though, I haven't looked at the X4 LOS thread much.
*3) LOS to my knowledge woln't work with MicroG because it doesn't allow for spoofing. HAVOC does, and personally I was using Android 9 w/ HAVOC and MicroG so I could use the GCam but due to personal reasons I had to install GPlay and so at the same time I also upgraded to Android 10. One point at least in my experience, the phone was getting more and more difficult to use over time but rebooting the phone fixed it completely. I almost never rebooted my phone back on 9 so it caught me off guard personally.
It sounds like you might be trying to go down a more privacy centered phone like I was until recently. Personally, I liked the Android 9 w/ HAVOC and MicroG. I can give you my list of apps I used but you probably know most of them (Simple Mobile Tools, OSMAND, K9, Fennec, NewPipe, VLC ect.) The launcher would get a little buggy (context menus would stop working after a while on app icons) and for some reason the audio would start for a split second, pause, for a sec, then continue. Other than that, it was great. I used that config setup for a year.
On a completely unrelated note, AT&T will most likely not work with the unlocked X4 after a couple of years, doesn't affect me but just a heads up.
Hi, I have a Redmi 4a with a custom android 11 ROM (tried a few).
Since a few days the microphone is not working on calls. If I record a video the audio recording is ok, so the mic itself does not have problems.
Hands-free calls work (loudspeaker), but still mic is muted or very low level.
Headset works correctly, with its own mic.
I think the microphone level is too low during calls, maybe some setting got messed up, but I do not know how.
I already tried doing factory reset, cache wipe, full wipe+ROM re-flashing, changing ROM (still keeping Android 11).
Only a few apps have microphone permission: Camera, FM Radio, Phone & now Phone Doctor Plus, which I installed to control the mic and the earphones plug (all working perfectly, all available microphones).
Google Assistant is disabled.
Bluetooth is off, nothing coupled at all.
Any Idea before I wipe again and try a ROM with Android 10 (or 9, or 8, ...)
Thanks, Leonardo
leodp said:
Hi, I have a Redmi 4a with a custom android 11 ROM (tried a few).
Since a few days the microphone is not working on calls. If I record a video the audio recording is ok, so the mic itself does not have problems.
Hands-free calls work (loudspeaker), but still mic is muted or very low level.
Headset works correctly, with its own mic.
I think the microphone level is too low during calls, maybe some setting got messed up, but I do not know how.
I already tried doing factory reset, cache wipe, full wipe+ROM re-flashing, changing ROM (still keeping Android 11).
Only a few apps have microphone permission: Camera, FM Radio, Phone & now Phone Doctor Plus, which I installed to control the mic and the earphones plug (all working perfectly, all available microphones).
Google Assistant is disabled.
Bluetooth is off, nothing coupled at all.
Any Idea before I wipe again and try a ROM with Android 10 (or 9, or 8, ...)
Thanks, Leonardo
Click to expand...
Click to collapse
Are you sure it is issue on your side? Did you try it out with several ppl? Might be some issue on the other side, just a guess.
First of all, I would recommend to check out telegram channels/official sites of mentioned ROMs for latest updates.
It looks to me as if you installed some outdated ROM, because i have not heard of mic issues for couple years.
Also join tg channel for our device, where you can request assistance.
Second suggestion would be check for phone caller app from other ROMs, from LineageOS for example is usual choice (you can find it on APK Mirror) or AOSP from AOSP-based ROMs.
If you have Magisk installed, check out for "NLSound for QCom Devices" module, it is a module that includes setting sensitivity of mic a lil bit higher as well as other sound enhancing options. (NLSound Tg Channel), or try to check out whatever module for that matter.
I changed a few other Android 11 ROMS, all with the same issue. Also AOSP.
Android 10 CRdroid works better, mic level is low, it's higher with free speaking.
It looks like a sensitivity issue, maybe I have to change some mixer.xml settings?
Now I'm back to Android 11, Nusantara (unified 4a & 5a), but still the problem persists.
Installed NLSound: not better.
Can I configure mic level on NLSound? Where (or with which app) should the mic level be exposed?
You cannot configure mic sensitivity with NLSound, but during installation you can choose option to increase it. Which i thought could resolve your issue.
I honestly ran out of ideas atm, maybe someone more expirienced will join the discussion.
But while we are at it, could you specify a little bit more, how your mic stopped work properly? Because it still doesnt looks like a ROM issue to me, all ROMs are generic and share same device tree, which already has optimised settings and rarely being updated.
Was it like you installed custom ROM and mic immidiately went bananas, or you installed custom ROM, mic worked for certain amount of time, and then issue appeared?
Maybe try to reflash persist.img and firmware.img from original MIUI ROM, or roll back on MIUI(but dont lock bootloader) and check if issue is still present.
2ley said:
You cannot configure mic sensitivity with NLSound, but during installation you can choose option to increase it. Which i thought could resolve your issue.
I honestly ran out of ideas atm, maybe someone more expirienced will join the discussion.
But while we are at it, could you specify a little bit more, how your mic stopped work properly? Because it still doesnt looks like a ROM issue to me, all ROMs are generic and share same device tree, which already has optimised settings and rarely being updated.
Was it like you installed custom ROM and mic immidiately went bananas, or you installed custom ROM, mic worked for certain amount of time, and then issue appeared?
Maybe try to reflash persist.img and firmware.img from original MIUI ROM, or roll back on MIUI(but dont lock bootloader) and check if issue is still present.
Click to expand...
Click to collapse
It stopped by itself, without me doing any specific install, as far as I can remember.
I reinstalled NLSound, with mic and volume optimizations. Still not ok.
One question: can I flash persist.img and firmware.img without losing the functionality of the ROM I have now, or should I then re-flash also the custom ROM afterwards?
Thanks for the hints.
leodp said:
It stopped by itself, without me doing any specific install, as far as I can remember.
I reinstalled NLSound, with mic and volume optimizations. Still not ok.
One question: can I flash persist.img and firmware.img without losing the functionality of the ROM I have now, or should I then re-flash also the custom ROM afterwards?
Thanks for the hints.
Click to expand...
Click to collapse
Yes, you can flash persist.img and firmware.img without any concerns about ROM.
It shouldnt affect ROM functionality, it is just a pre-caution step, in case any of previous ROM's you played with made some unnecessary changes.
2ley said:
Yes, you can flash persist.img and firmware.img without any concerns about ROM.
It shouldnt affect ROM functionality, it is just a pre-caution step, in case any of previous ROM's you played with made some unnecessary changes.
Click to expand...
Click to collapse
persist.img flashed, no change.
firmware.img: cannot find it in the stock MIUI I downloaded
rolling back to older MIUI: have not done it yet, as I do not know how to avoid relocking the recovery. I never did it before and I have run out of wife's patience in the meantime
leodp said:
rolling back to older MIUI: have not done it yet, as I do not know how to avoid relocking the recovery. I never did it
Click to expand...
Click to collapse
Gotta download Xiaomi official tools for this purposes. MiFlash PRO, or Mi Unlock or something like this, dont remember the name. The one you unlocked bootloader of a phone with, same tool can also flash stock MIUI back, if i remember correctly, According to MiUnlock FAQ bootloader wont lock, unless you choose special option "Clean All and lock"
I also found this instructions to deal with sound problems, check if it will fix your problems.
Spoiler: instructions
For non root users
Code:
Go to the following path
Setting > Google > search > voice > "ok google" detection and turn off both the options.
That's it.
For root users, edit audio_platform_info.xml and/or build.prop
Code:
Navigate to the root directory of the phone
Root/system/etc/
Then look for a file named "audio_platform_info.xml" with text editor of your choice .
Now go to the bottom of the file you will see </acdb_ids> , you need to add the below line before/above that </acdb_ids>
Click and add this line
<device name ="SND_DEVICE_IN_VOICE_DMIC" acdb_id = "100"/>
Now just save the file and exit the root browser
Reboot the device now. As soon as it boots up you may check thr mic quality if its better now or not
If you're still not satisfied with it then you may follow one more step. This will turn off the voice cancellation ( it could cause echo sometimes to the listener)
For this open root browser and navigate
Root > system > build.prop file
Open it with any text editor.
Look for following lines
persist.audio.fluence.voicecall= true
persist.audio.fluence.voicerec= false
As soon as you find these lines make true to false and it should look as follows
persist.audio.fluence.voicecall=false
persist.audio.fluence.voicerec=false
Save the file and exit.
Reboot the device and check if it's working or not.
As of your wife, there is only one common fix for that issue: switch from 'default charge' mode during night to 'super charge' one, and gotta charge longer in this mode, usually it helps them to switch from 'nagging mode' to 'silence mode' for a while. Apply this fix as often as she slips from 'silence mode', because there is no permanent fix for this issue.
End of the story:
I bought for a few € the miniboard with the USB connector and the microphone, replaced the old one and the phone is working again.
The not clear behavior of the microphone with the various Android installations was due to it starting to malfunction. The last days It was always completely silent.
Thanks to all for the help and the suggestions, I learned some new things.
leodp said:
End of the story:
I bought for a few € the miniboard with the USB connector and the microphone, replaced the old one and the phone is working again.
The not clear behavior of the microphone with the various Android installations was due to it starting to malfunction. The last days It was always completely silent.
Thanks to all for the help and the suggestions, I learned some new things.
Click to expand...
Click to collapse
Hi,
so does that mean, it was a hardware issue?
my dads Samsung Galaxy M21 has exact same problem
bushu16 said:
Hi,
so does that mean, it was a hardware issue?
my dads Samsung Galaxy M21 has exact same problem
Click to expand...
Click to collapse
Yes, hardware damage
Installed it yesterday without looking, and oh god Android 12 (and the new update) is so much worse. For some reason now on 60hz my phone constantly stutters, and overscroll is literally making me feel nauseous (and it seems like you can't turn it off without turning ALL animations off), not to mention a lot of other stuff that makes using my phone uncomfortable for me.
So i looked into downgrading/custom ROMs, and thought i'd give downgrading a try. So from what i've gathered so far those are the steps i would have to take to downgrade my phone.
Enable USB Debugging on my phone through Developer Options
Install ADB and Fastboot driver on my PC from here
Download a Redmi Note 11 Global Fastboot ROM that i want from here
Download and install MI Flash Tool from here
Make sure that my phone is at 100% charge, then turn it off, and turn it on in Fastboot mode by holding Volume Down+Power.
Connect it to my PC with USB and open Mi Flash Tool
Select the ROM folder
Select "save user data" at the bottom right
Click "flash" button at the top right and wait for the install to be done
I wanted to ask people here who know a lot more about this whether those steps are fully correct, or if there's something i missed. Also some general advices would be nice.
That's weird. Updated my spesn EU version a few days ago to 13.0.2.0 and it's hard to see what's changed from 11. No new problems that I've noticed.
Could you try a factory reset before rolling back to 11?
Wilbo2016 said:
That's weird. Updated my spesn EU version a few days ago to 13.0.2.0 and it's hard to see what's changed from 11. No new problems that I've noticed.
Could you try a factory reset before rolling back to 11?
Click to expand...
Click to collapse
Overscroll is in Android 12, and i wasn't able to find any info on how to turn it off without also turning off all animations.
Notifications and any google app are ****-colored now due to dynamic theme color in Android 12, simply cause of my wallpaper, and there doesn't seem to be a way to turn it off.
Perhaps doing a factory reset would solve the stuttering on 60hz, but it wouldn't fix those
IncredibleFrog731 said:
Overscroll is in Android 12, and i wasn't able to find any info on how to turn it off without also turning off all animations.
Notifications and any google app are ****-colored now due to dynamic theme color in Android 12, simply cause of my wallpaper, and there doesn't seem to be a way to turn it off.
Perhaps doing a factory reset would solve the stuttering on 60hz, but it wouldn't fix those
Click to expand...
Click to collapse
I'm a simple user and don't use animations or fancy themes, and I don't use it for games. My phone is a tool for comms, specialised apps and internet only and updating to 12 just sort of happened with the November security release. I hope you can sort your problems as the Note 11 is an amazing phone for the price.
Its always a rule of thumb that you should factory reset your phone after an android version update. This way it runs better and smoother. Before downgrading try reseting it and the see and even if it doesn't resolve then you can try downgrading.
Mine got updated to A12 and i immediately formatted it and now using it without an issue. Though there are no huge changes as the original A12 has like material you engine but its working fine.
After updated to Android 12 EU Version i cant See any issues. My Phone even runs better and smoother than before. I didnt Do a reset.
Hi all. I need a bit of help.
Evertime my phone's screen goes off the android auto stops working. I have to drive while keep pushing the power button to it can carry on working. I have looked at all the settings I can think of but nothing seems to work. Running the latest MIUI 14.0.1 (vili) version.
Any help with a setting I can't think off please would be a great help as I travel allot.
I fixed it by disabling these options (see screenshots):
I found this workaround in another forum, it's a MIUI 14 bug, Xiaomi knows this problem, with next updates probably it will be fixed.