So I installed PixelExperience Rom on my phone with OrangeFox, and it worked fine. The issue is when I reverted back to the original Miui Rom. My speaker sound lags and after a while of use, goes silent. It doesn't matter what app I'm using, The phone services are also offline. I used multiple Miui versions; 12.0.6.0, 12.5.5.0, 11.0.10.0, 11.0.3.0.
Update: I used the 13.0.2.0 SJWMIXM and it's running fine so far. here is the ROM link if anyone faced the same issue
https://bigota.d.miui.com/V13.0.2.0.SJWMIXM/curtana_global_images_V13.0.2.0.SJWMIXM_20220725.0000.00_12.0_global_eb85230cd5.tgz
Related
This issue was mentioned before, but there isn't any recent or working solution. So...
My lower microphone doesn't work, neither in calls nor in recording applications It's very very quiet. Changing ROM, kernel, nuking the rom doesn't fix this, however sometimes the microphone works fine. Upper microphone also works fine (could be checked by switching to loadspeaker).
Does changing the charging board will fix this or the issue is elsewhere (on MB ie)? What board should I buy (new china one, used original)? What revision is best (2.2, 2.3 (this one I currently have). Or maybe the problem lays somewhere deep in the software (audio menu is ofcourse blocked)?
Is this problem even exist on the official rom?
Zile995 said:
Is this problem even exist on the official rom?
Click to expand...
Click to collapse
Actually I didn't try one. But I tried:
- CM 10.1
- AOSP Neatrom 5.0
- Neatrom from 5.9 to 6.3 (problem first occured sometime after updating to 6.0, but I could have nothing in common)
Also tested serval Dorimanx kernel, Apolo 4.13 and 4.14, latest Philz and nothing...
Try to flash stock firmware over odin. First do the full wipe in recovery and then boot phone to download mode.
My partner's S III recently developed a problem using the standard Samsung 4.3 OS, it kept halting in the the middle of an application and later started continuously rebooting. As the phone was as far as I was aware, out of warranty and someone suggested there could be a s/w issue, I decided to root the phone and install a custom 4.4.2 ROM (I initially went for the one of the cyanogenmod 4.4.2 ROMs), to see whether that would resolve the problem. Initially, the ROMs I tried all generated error messages and failed to install,until I tried the Revolutioniary S5 V2 ROM, which installed perfectly.
However, it states that iti is a 4.3, rather than 4.4.2 ROM. I ran the ROM for 5 days without any major issues, so decided to try the V3 ROM, as ir was stated that this was 4.4.2 in a number of articles.. Again the ROM installed really quickly and without a hitch. However, again the ROM said it was 4.3, and as soon as I tried to install applications (well it was the third install, Skype if I remember), and the phone turned itself off. Then it started continuously rebooting, which is what was happening before the V2 ROM was installed. managewd to stop this by removing and then putting back the battery, and managed to get the V2 ROM installed again. Ther are three questions:
1) Does anyone have any idea what the initial problem might have been?
2) Why did the V3 ROM actually cause the problem to reoccur?
3) Is there a genuine 4.4.2 release of the Revolutionary S5 ROM (which I am genuinely impressed by and happy with), and will it work with my phone? (specific model i9300)?
[email protected] said:
My partner's S III recently developed a problem using the standard Samsung 4.3 OS, it kept halting in the the middle of an application and later started continuously rebooting. As the phone was as far as I was aware, out of warranty and someone suggested there could be a s/w issue, I decided to root the phone and install a custom 4.4.2 ROM (I initially went for the one of the cyanogenmod 4.4.2 ROMs), to see whether that would resolve the problem. Initially, the ROMs I tried all generated error messages and failed to install,until I tried the Revolutioniary S5 V2 ROM, which installed perfectly.
However, it states that iti is a 4.3, rather than 4.4.2 ROM. I ran the ROM for 5 days without any major issues, so decided to try the V3 ROM, as ir was stated that this was 4.4.2 in a number of articles.. Again the ROM installed really quickly and without a hitch. However, again the ROM said it was 4.3, and as soon as I tried to install applications (well it was the third install, Skype if I remember), and the phone turned itself off. Then it started continuously rebooting, which is what was happening before the V2 ROM was installed. managewd to stop this by removing and then putting back the battery, and managed to get the V2 ROM installed again. Ther are three questions:
1) Does anyone have any idea what the initial problem might have been?
2) Why did the V3 ROM actually cause the problem to reoccur?
3) Is there a genuine 4.4.2 release of the Revolutionary S5 ROM (which I am genuinely impressed by and happy with), and will it work with my phone? (specific model i9300)?
Click to expand...
Click to collapse
1) Not doing a full wipe/ formating system cache data etc or not using the latest recovery or combination of both
2) Not doing a full wipe/ formating system cache data etc or not using the latest recovery or combination of both
3) No
Also I find if switching between 4.3 roms and 4.4 roms (which I do alot) it is good idea to backup internal sd card and to format it (not all the time just if phone becomes really slow or has random reboots)
Hello guys,
as the title says I am currently with the mobile data connection not being established on custom ROMs, the official MIUI ROM works fine. Before trying to go to LineageOS 14.1 I ran this 13.1 ROM for quite some time successfully.
This is what I did since trying to migrate to Andoid 7.1:
I flashed the latest MIUI Global Dev ROM, this locked my bootloader again, so I tried this for installing TWRP and custom ROMs with locked bootloader and this for unlocking the bootloader unofficially. Both methods generally worked, but mobile data did work on neither of them (I checked for the correct APN).
So I tried to go back to the LineageOS 13 ROM (clean flash, since I accidentally deleted my backup) I used before, but it also does not work on that version anymore.
Does anyone have any idea what the issue could be or how I could possibly find out what causes this?
Edit: I am now actually back to the latest MIUI Global Dev and hoping that I am able to unlock the bootloader officially eventually. But any tips on the issue above would still be appreciated.
Edit 2: On the 8.0 NitrogenOS mobile data does work. I first thought that it yet had to be an APN problem, so I copied the settings from this ROM to the LineageOS 14.1 ROM and deleted all other APNs, but that actually did nothing, it still did not work. So I guess I will stay on 8.0 for now, although I wanted 7.1 because of XPosed.
Edit 3: Suddenly stopped working on Android 8. Seems to work on the first boot after flashing a Android 8 ROM and then not anymore. Going back to MIUI...
This post helped me with the issue. After a soft reboot mobile data just works fine even after enabling/disabling airplane mode.
triplec0re said:
This post helped me with the issue. After a soft reboot mobile data just works fine even after enabling/disabling airplane mode.
Click to expand...
Click to collapse
Did you find a persistent method to solve the problem?
I have the same problem but Mobile Data only works after first boot and first soft reboot - than never ever.
BTW it works on MIUI ROMS without any problem.
b0mb said:
Did you find a persistent method to solve the problem?
I have the same problem but Mobile Data only works after first boot and first soft reboot - than never ever.
BTW it works on MIUI ROMS without any problem.
Click to expand...
Click to collapse
I did just recently find a persistent method. Read here: https://forum.xda-developers.com/showpost.php?p=70887635&postcount=9
Hi guys
My mido vibration stopped working a week back abruptly. I didn't flash anything new back then.
Tried diagnosing it with change of vibration motor (with a technician) as well but the new one didn't work either. He did attempt a temporary replacement of its underlying chip as well but again it didn't resolve the issue.
Attempted clean reflash RR. Then clean reflashed Havoc 2.9 build as well.
After reflash in both the builds, didn't install Magisk (just to be sure some version could have been conflicting with the motor may be)...No solution
Attempted firmware upgrade to notably stable versions 10.2.3 and then downgraded to 9.6.3 as well. No solution still....
Could anyone advise what I could attempt next..?
Current environment: Havoc 2.9
No magisk installed as of now.
Nothing works.
Magisk 20.1 was installed but removed now... Still doesn't work...
Please help.
So, I install lineage os every one's and a while to test it and see if it is ok for me, I always revert to stock but that's not the point, one problem that I have is that the phone gets VERY HOT. One day I installed lineage and when I finished the setup process, the phone was so hot I couldn't hold it comfortably, while when I finish the setup on the stock rom the phone is just warm. Is there any way to make the phone run cooler? Is the phone getting hot because the software is too much for the processor? . I haven't installed lineage os for about two months now so I may try it again at some point. Is anyone else having the same problem?
No that's not normal, it's not supposed to heat up much.
Maybe you you didnt flash it properly, it's recommended to install it like this.
forum.xda-developers.com/lg-g5/development/rom-unofficial-lineageos-17-1-g5-t4039807/post81972297#post81972297
Also check before flashing if your camera works on the stock lg rom,
If it doesnt you have to downgrade to stock marshmellow, and then upgrade back to oreo to fix it.
dylank said:
No that's not normal, it's not supposed to heat up much.
Maybe you you didnt flash it properly, it's recommended to install it like this.
forum.xda-developers.com/lg-g5/development/rom-unofficial-lineageos-17-1-g5-t4039807/post81972297#post81972297
Also check before flashing if your camera works on the stock lg rom,
If it doesnt you have to downgrade to stock marshmellow, and then upgrade back to oreo to fix it.
Click to expand...
Click to collapse
Thanks for answering,
This is how I install it. The camera on stock oreo is working normally so I don't need to install stock Marshmallow. So, I firstly unlock the bootloader and then install lineage os 15.1 with no gapps. After that I upgrade to lineage os 16.1 again with no gapps. Now I uninstall lineage 16.1 and I am doing a clean install of official lineage os 17.1 WITH gapps. The reason I do this is because if I install lineage 17.1 instantly the cameras and sensors don't work. Unfortunately I don't remember the temperatures that I got but I remember that one day I woke up with 20 C and after 15 minutes of some web browsing and social media it went up to 40 C (there's a slight chance that I'm wrong since I don't remember the exact temperatures as I said)
Strange i didn't have those problems when flashing properly,
Do you also use nano/pico opengapps?
You could also give crDroid Android 5.12, a try maybe that will work well, but it's android 9 instead of 10.
I think you need to flash it in the same way as lineage.
dylank said:
Strange i didn't have those problems when flashing properly,
Do you also use nano/pico opengapps?
You could also give crDroid Android 5.12, a try maybe that will work well, but it's android 9 instead of 10.
I think you need to flash it in the same way as lineage.
Click to expand...
Click to collapse
I originally used nano opengapps but I started using stock because I use most of the gapps anyway but I will try crdroid 5.12 at some point to see what happens.