I had this problem with MIUI too but now that im with AospExtended and trying some tweaks to my router i have notice a huge problem with my WiFi speed with BT enable or not!
As you can see at the SS's bellow with BT enable i manage to get to a speed test (i know they aren't reliable source to test your speed) 1.8Mbps Max as with BT disabled i can get 12-14Mbps (The same as my Desktop)
Anyone know any fix for this its really frustrating cause i need my BT on for my MiBand2!!
Also as you can see with BT or not enabled the max speed of the Wifi stays the same at 150Mbps.
Im using .11n on my Router 2.4ghz channel auto even its the same with 20mhz or 40mhz!
Interesting, on LineageOS 14.1 I do not have that problem. Have a look.
kemoti said:
Interesting, on LineageOS 14.1 I do not have that problem. Have a look.
Click to expand...
Click to collapse
Thats interesting....we have different rom but what kernel did you use stock lineage?
@pikachukaki
Yes. Stock lineage kernel 3.18.31 only root magisk, no xposed.
kemoti said:
@pikachukaki
Yes. Stock lineage kernel 3.18.31 only root magisk, no xposed.
Click to expand...
Click to collapse
I will try to flash the kernel cause i don't want to reflash my phone.. Thanks for the info!!
Marshmallow roms like RR have high signal strength and range then nougat roms! Personally experienced
Related
So some newer devices have been shipped with different components from the older ones and while everything works fine on recent miui versions, most custom roms have issues. So I'm creating this thread to document all the issues caused by these new components and any solutions to them in one thread. Please reply if you have any other issues caused by the new hardware or any solutions to them.
Fingerprint
Description:
Option to add fingerprints doesn't appear even after setting pin, pattern or password on non miui based roms.
/data folder contains goodix folder with contents on miui.
Cause:
Some devices have a new fingerprint sensor manufactured by Goodix which is not yet supported by non miui based roms.
Solutions:
miui and any miui based roms such as xiaomi.eu should still work fine.
The newest build of Santosh's CM has a fingerprint patch available that will fix it.
Wait for CM to add support for the new hardware to its source code.
Battery
Description:
Battery is stuck at either -2% or 50%.
TWRP does not show battery percentage at all or constantly shows 50%.
Cause:
Possibly new battery controller hardware, by the looks of it the issue is related to the kernel, older CM kernel builds seem fine and so do newer miui builds however any rom using a new CM kernel build or based off it has the issue.
Solutions:
Fix was added to CM source code so the problem should be solved on all newer roms and kernels based on it now.
Flashing Radon 1.9 or above will fix it on any CM source based roms.
miui and other miui based roms such as xiaomi.eu should be fine.
Santosh's CM13 plust the camera fix works.
Mokee works fine.
Unofficial Ressurrection Remix works fine up until the 06/08 build.
This is the patch applied to Radon to fix the bug.
If you know of any other issues caused by newer hardware or solutions please tell me so that I can add it to this thread.[/QUOTE]
If possible, Can you also provide information about how to identify different components without changing roms?
Thank you.
dmemon said:
If possible, Can you also provide information about how to identify different components without changing roms?
Thank you.
Click to expand...
Click to collapse
Added for the fingerprint sensor, using TWRP is still probably the easiest way to check for the battery bug.
dmemon said:
If possible, Can you also provide information about how to identify different components without changing roms?
Thank you.
Click to expand...
Click to collapse
The sensor of fingerprints with aida64, it is possible to identify.
The battery only if flash the TWRP, for the present.
Santhosh's CM13 battery bug is gone if you flash his camera fix.
razr96 said:
Santhosh's CM13 battery bug is gone if you flash his camera fix.
Click to expand...
Click to collapse
Ok cool I'll add it to the post and test it out if I get a chance.
I hear of that Mokee is using Xiaomi device tree, I guess that is why it don't has the "-2% or 50%" issue...
NTRNSTR said:
Description:
Battery is stuck at either -2% or 50%.
TWRP does not show battery percentage at all or constantly shows 50%.
Cause:
Possibly new battery controller hardware, by the looks of it the issue is related to the kernel, older CM kernel builds seem fine and so do newer miui builds however any rom using a new CM kernel build or based off it has the issue.
Solutions:
Santosh's CM13 plust the camera fix should fix it.
Click to expand...
Click to collapse
The camera fix works only with Santosh's CM13, not with other CM/AOSP roms
the new kernel Radon V1.8 by Umang96 does not fix the battery problem
EkiFox said:
The camera fix works only with Santosh's CM13, not with other CM/AOSP roms
the new kernel Radon V1.8 by Umang96 does not fix the battery problem
Click to expand...
Click to collapse
I would expect it to work on all Santosh based roms, the camera fix must have modified something that flashing a new kernel overwrites, if we can figure out what the camera fix changes we might be able to get a fix for all roms.
---------- Post added at 02:11 PM ---------- Previous post was at 02:10 PM ----------
dna1982 said:
I hear of that Mokee is using Xiaomi device tree, I guess that is why it don't has the "-2% or 50%" issue...
Click to expand...
Click to collapse
Well that would explain it, but at least we have roms without the bugs, that should help figure out the problem.
any working custom kernels for -2% or 50% battery bug?
mega-samu said:
The sensor of fingerprints with aida64, it is possible to identify.
The battery only if flash the TWRP, for the present.
Click to expand...
Click to collapse
as far as i know AIDA64 is not a good way to see your fingerprint sensor it shows fpc102x for me but i have a goodix sensor, in fact i think the other ones with fpc sensors have a fpc 1035 not a 102x. i think a good was would be checking kernel log you should see the module name or checking data partition ( if you have root) or system/etc/firmware if you dont (i'm not sure about the second one but i can see some goodixfp data there)
just saying maybe it saves someone from lots and lots of confusion as i had when i bought my device
The new Radon kernel doesn't have the -2%/50% battery bug!
For the cm13 based roms : http://forum.xda-developers.com/showthread.php?p=68012485 and few posts under there is a test version for MIUI rom
Reno_kun said:
The new Radon kernel doesn't has the -2%/50% battery bug!
For the cm13 based rom : http://forum.xda-developers.com/showthread.php?p=68012485 and few posts under there is a test version for MIUI rom
Click to expand...
Click to collapse
:victory: Now we can use any Official-CM based rom. Definitely adding this to the top of the list.
Reno_kun said:
The new Radon kernel doesn't has the -2%/50% battery bug!
For the cm13 based rom : http://forum.xda-developers.com/showthread.php?p=68012485 and few posts under there is a test version for MIUI rom
Click to expand...
Click to collapse
Yep just flashed official RR with this kernel and no battery bug!
Yes, there is just the lack of the support ou goodix fp and it will be perfect !
KaciPL said:
any working custom kernels for -2% or 50% battery bug?
Click to expand...
Click to collapse
Now there are, just updated the post.
Radon V1.9 Kernel does not cause the battery bug .......
Radon V1.9 Kernel does not cause the battery bug on "MIUI 8 by Xiaomi.eu 6.7.28 | Beta".
I got a test version from @Umang96 and successfully got below 50% battery level.
Any custom kernel working with goodfix fp ??
Sent from my Redmi Note 3 using Tapatalk
I lose data connection on any cm custom rom. It goes away for 50-60sec then it gets back
And if i flash radio zip, then security options crash
LiRi2000 said:
Any custom kernel working with goodfix fp ??
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
I don't think so, still a work in progress getting it to work.
Hi guys
I have been having this issue with the S% for sometime now, Where if I reboot the phone all is fine, but after a while when I switch on my WIFI it will not automatically connect to my network.
I have the G900f variant with the latest CM13 from the unofficial branch and has crazy super kernel installed.
I have had other roms and custom kernels installed but the issue was still persistent.
Hi,
Does the issue persist when you use the included kernel of the ROM? Personally I've only seen these issues when using a custom kernel.
Saber.
Saber said:
Hi,
Does the issue persist when you use the included kernel of the ROM? Personally I've only seen these issues when using a custom kernel.
Saber.
Click to expand...
Click to collapse
I have not tried that, only because I have tried other kernels, I just thought that it would be unlikely to have all custom kernels to have the same bug.
But nevertheless I see if it will happen with stock kernel.
After two seconds always disconnects. Similar trouble has been in oneplus phone: https://forums.oneplus.net/threads/oneplus-3-issue-with-bluetooth-media-nav.453152/
Problem Only on stock rom EUI, not present custom roms what I have also tested. Any solution? Thanks!
Same problem with LineageOs 14.1. I will try with Omnirom.
What custom rom you tested?
Lineage TS rom and RR rom worked for sure
help a newb...
dadaa1 said:
Lineage TS rom and RR rom worked for sure
Click to expand...
Click to collapse
I am having the same problem with an Android head unit in my car; connects; you can even start to dial if you're quick; drops after ~2s.
RR = Resurrection Remix 7.1.2?
Lineage TS = ?
Did any other ROMs work?
Thanks.
tlyonstlyons said:
I am having the same problem with an Android head unit in my car; connects; you can even start to dial if you're quick; drops after ~2s.
RR = Resurrection Remix 7.1.2?
Lineage TS = ?
Did any other ROMs work?
Thanks.
Click to expand...
Click to collapse
I think you have to test different roms. It´s the only way. In my case I´m using lineage TS and works but if I use stock rom it drops immediately. Renault Clio bluetooth and the phone X720.
dadaa1 said:
I think you have to test different roms. It´s the only way. In my case I´m using lineage TS and works but if I use stock rom it drops immediately. Renault Clio bluetooth and the phone X720.
Click to expand...
Click to collapse
Thanks for the reply. Some folks report short battery life with Lineage TS; is it OK for you?
EDIT: Got it working! Burned my phone with ResurrectionRemix. Likely hopeless for the Alcatel phone that also didn't work but that is unimportant for me.
Brother, I have a installed Lineage OS 15.1 on my J500H.And I don’t find useful.My mobile data is not working and sometimes my wifi connection is also not working....
So can anyone share the 2 files of SM-J500H?
1.Stock boot.img
2.System.img
Md Nafis Muhtadi said:
Brother, I have a installed Lineage OS 15.1 on my J500H.And I don’t find useful.My mobile data is not working and sometimes my wifi connection is also not working....
So can anyone share the 2 files of SM-J500H?
1.Stock boot.img
2.System.img
Click to expand...
Click to collapse
Why you need these files??!
If you see that lineage os 15 is not helpful then flash other ROMs
There are many newer rom that don't have this issues like lineage 17 or bootleggers Q and pie or pie pe ikd many
And if you like to use stock then flash stock rom with use debugging on that's all
Because these custom roms have a lot of bug issues.I can't use Bluetooth and WiFi.
Even my mobile data is also hampered for custom roms.
So I want these files to flash via twrp.
Md Nafis Muhtadi said:
Because these custom roms have a lot of bug issues.I can't use Bluetooth and WiFi.
Even my mobile data is also hampered for custom roms.
So I want these files to flash via twrp.
Click to expand...
Click to collapse
All of what you said works on bootleggers Q!
Me and many other people use it right now
Btw use twrp only for custom rom or change recovery to other one
That files will not help you bro
Hi folks, what's the most stable android 11 ROM out there for PH-1 that doesn't have any major bugs?
From what I have seen. I tried Statix OS, EvoX, and PA Ruby. Statix 4.2 has low call receiver volume, on PA Ruby latest Beta mobile data doesn't work, and on EVO X, I cannot get NFC payments to work on my ING banking app. Could anyone please recommend a ROM, that doesn't have any major issues?
LineageOS 18.1 is my daily driver, the only bugs left are that recording video has low volume and chrome crashes (but this can be fixed by flashing certain modem files, available on the ROM thread)
Everything is fast and works just fine, battery lasts a bit more than stock
I prefer the OEM one.
aayushchawla said:
I prefer the OEM one.
Click to expand...
Click to collapse
It was good, that was Android 10 though, I was asking specifically for 11
surya17 said:
Hi folks, what's the most stable android 11 ROM out there for PH-1 that doesn't have any major bugs?
From what I have seen. I tried Statix OS, EvoX, and PA Ruby. Statix 4.2 has low call receiver volume, on PA Ruby latest Beta mobile data doesn't work, and on EVO X, I cannot get NFC payments to work on my ING banking app. Could anyone please recommend a ROM, that doesn't have any major issues?
Click to expand...
Click to collapse
Low call volume has been solved in latest statix.. its more stable and battey backup is good too.. only issue i had in this rom was outgoing msgs.. rest everything is good.
Vi7eta said:
Low call volume has been solved in latest statix.. its more stable and battey backup is good too.. only issue i had in this rom was outgoing msgs.. rest everything is good.
Click to expand...
Click to collapse
Hey, I'm on the latest Statix (Aug 21 build), the screen seems to have shifted to the right after flashing magisk, which is weird. Any idea how to fix this?
surya17 said:
Hey, I'm on the latest Statix (Aug 21 build), the screen seems to have shifted to the right after flashing magisk, which is weird. Any idea how to fix this?
Click to expand...
Click to collapse
This was discussed in the Statix thread (I saw your post there with the same question)... The problem exists in the last two builds (July and August). There's no fix - not yet, anyway. The suggestion from the developer was not to use Magisk.
And another problem with Statix builds from June onward is the Essential Camera crash.