Database Develop

[WIP][KERNEL][KEXEC] JB ROMS For Droid 3 [03/06: BT/SPEAKERPHONE FIX]

Jellybean 4.2.2 for the Droid 3
[ CURRENTLY THIS ROM REQUIRES A ROM-SLOT1 INSTALL IN SAFESTRAP ]
[ ALL Jellybean 4.2.x ROMs should be using 20130301 GApps: http://goo.im/gapps ]
OFFICIAL CyanogenMod 10.1 (Android 4.2.2): [NIGHTLIES]
http://www.get.cm/?device=solana&type=nightly
[03/06] - BT/Speakerphone Fix in next nightly(thanks DHacker)
[02/26] - HWcomposer API 1.0 (JB-MR1 compliant)
[02/26] - HD codec fixes
[02/26] - Kernel updates / bugfixes for clock management, battery drain and stability
[02/26] - Android 4.2.2 merged into CM10.1
[01/23] - MMS fix (sending from native Messaging app)
[01/20] - Keyboard Backlight fixes (tied to the front button backlight for now)
[01/18] - Fixed incoming call bug
[01/16] - Fixed bluetooth for device starting. Audio is still bad.
OLDER CyanogenMod 10.1:
http://goo.im/devs/Hashcode/solana/cm10.1/
AOKP (Android 4.2.2): [B5]
http://aokp.co/supported-devices/?id=58&device=solana
Official release: [GETTING REBUILT FOR BOOT ISSUE]
[03/06] - BT/Speakerphone Fix -- need to get a new build up(thanks DHacker)
[03/05] - Official Release Build #5
[02/26] - Official Release Build #4
[02/26] - HWcomposer API 1.0 (JB-MR1 compliant)
[02/26] - HD codec fixes
[02/26] - Kernel updates / bugfixes for clock management, battery drain and stability
OLDER AOKP:
http://goo.im/devs/hashcode/solana/aokp/
CyanogenMod 10:
http://goo.im/devs/hashcode/solana/cm10/
USING WITH GSM INFORMATION FOUND HERE (by Skreelink):
http://forum.xda-developers.com/showpost.php?p=34057016&postcount=1
ICS BUILDS:
CyanogenMod 9:
http://goo.im/devs/hashcode/solana/cm9/
** NOTE: I Kept the HD Codecs alive in this build. I realize they are laggy and need work to reduce the memory impact.
KERNEL NOTES:
This is the same kexec kernel used in the CM9 builds, so expect all of the same issues (see below):
- No Camera

UPDATED: 2013-02-26
CURRENT DROID 3 DEVELOPMENT:
CAMERA NOTES:
** I would never expect the camera to be fully functioning. I am working several avenues to get a functional camera on the Droid 3, but they're all sketchy at best. Just know that if you choose to flash custom ROMs w/ newer OS versions: You won't have a camera.
** Did I say don't expect the camera to be fixed? If it was to be fixed, trust me, you'll see me all over the boards, twitter and the social universe telling people about it.
** There are other devs now working on the kexec kernel and it's possible that they can get some basic camera functionality through kernel drivers. It's quite complicated and there are no public data sheets which describe the sensor functions in great detail for our devices.
** Don't expect the camera to be fixed.
CHANGES OVER THE LAST MONTH:
BATTERY LIFE / KERNEL BUGFIXES:
https://github.com/STS-Dev-Team/kernel_mapphone_kexec/commits/3.0.31
- Several internal clocks which were left active are now turned off as they should be. (since they're un-used)
- IPI/LOCAL timers were re-enabled in the kernel. These are interrupt driven timers which help trigger various drivers for updates.
- Bugfixes to allow other lower level functions to run in the kernel as well like gpmc
- I've fixed the kernel bootlog recovery driver (/proc/last_kmsg) so that this now works in our kexec kernel. This is a copy of the last kernel bootlog from a prior boot. So if you crash, please reboot and pull /proc/last_kmsg with adb and send me a log via email: hashcode0f at gmail.com
- Removed a hack to initiate the sound driver, causing it to stay active all of the time in the background. It now starts normally and suspends normally. (Thanks to kfazz for the fix).
JB-MR1 DEVICE UPDATES WITH OMAPZOOM:
https://github.com/STS-Dev-Team/android_device_motorola_solana/commits/jb-mr1
- hwcomposer now updated to API1.0
- domx (HD codec) code updated to the latest sources
CHANGES OVER THE NEXT MONTH:
- I'm taking the kexec kernel back to the beginning and re-merging Motorola's changes with the Texas Instrument changes that are needed to run the kernel on the Droid 3: memory allocations, HD codec binary changes, etc.
- This process is already 3-4 weeks in the running, and will be another 2-3 weeks before it's done.
- Once that kernel source is ready for prime-time, I'm going to swap the Droid 3 over to the new kernel source.
WHY DO THIS?
- By taking the time to create a full kernel history (from omapzoom) and integrate the Motorola changes into it, I can then migrate the kernel sources forward in a nice orderly manner cherry-picking new kernel commits directly from Omapzoom.
- This should make for a much cleaner / more stable kexec kernel in the future. And allows other devs to see where I'm going w/ kernel development so that they can add to it. Each file shows how it was edited and by who so it's more transparent where Motorola made their changes to the original TI kernel.
BATTERY DRAIN AND WHEN WILL IT BE "FIXED":
- The current kernel cannot put the UART ports to sleep like a normally booted kernel can. There is an issue that happens during kexec where the clocks associated w/ the UART ports become stuck in a full enabled mode. Any attempts to place them in suspend or disable hangs the kernel. It's being looked at. Right now the device never really 100% suspends. Hence higher than normal battery usage.
"OFFICIAL" ____ (AOKP/CM) MEANS WORKING CAMERA/BLUETOOTH AUDIO RIGHT?
- No. Actually "official" just means you can repo init the source straight from either AOKP/CM and build the device w/o worrying too much about extra sources or patches, etc.
- "Official" also means automated builds for the device (in some fashion). Currently for AOKP it's every 2-3 weeks and for CM it's nightly. These have the benefit of including any changes to the ROM automatically.
- The device doesn't get any more devs
- The device isn't magically fixed or more stable
Just thought I'd toss that in

How do I get from safstrap 1.0.8 using mavrom 4.5 to test this baby. Fairly detailed please. I have eta 906 btw.
Sent from my DROID3 using Tapatalk 2

Wohhhhaaaa thank you !!!!!
downloading ......
i will see how its work in Europe

Dude awesome. Thanks so much! Does the camera work?
Sent from my xt862 using xda app-developers app

duncan254 said:
How do I get from safstrap 1.0.8 using mavrom 4.5 to test this baby. Fairly detailed please. I have eta 906 btw.
Sent from my DROID3 using Tapatalk 2
Click to expand...
Click to collapse
From the experience of various users, all one needs is an update of safestrap to 2.0 and the flash of the kexec ROM. I did this over stock, CM7 and CM9. Many other users have gone from other ROMs - including some version of mavrom.
---------- Post added at 04:36 PM ---------- Previous post was at 04:30 PM ----------
MrObvious said:
Dude awesome. Thanks so much! Does the camera work?
Sent from my xt862 using xda app-developers app
Click to expand...
Click to collapse
Nope. Or should I say not yet...

Do I need to uninstall safestrap 1? What happens to my current nonsafe stock rom?
Sent from my DROID3 using Tapatalk 2

duncan254 said:
Do I need to uninstall safestrap 1? What happens to my current nonsafe stock rom?
Sent from my DROID3 using Tapatalk 2
Click to expand...
Click to collapse
I think that the steps to follow would be something like
1) Go back to non-safe/stock
2) Uninstall safestrap 1.08 from there
3) Install the new one
4) Go to safe mode and finally
5) Flash the build and admire that precious CM9 bootanimation
That's what I would do anyway, I didn't have to since the first safestrap I've ever installed was the 2.0/kexec version
Enviado desde mi GT-I5510 usando Tapatalk 2

I just deleted old safestrap and installed new one on safe system. Everything appears fine. However, the dl is not working.
Sent from my DROID3 using Tapatalk 2

GSM on Movistar Argentina network is working fine (850 mhz/1900mhz UMTS). SMS is ok too.
The GSM level indicator is stuck in the middle. *#*#INFO#*#* Phone information says Signal Strength 0dBm 97 asu. Seen this before in previous ICS builds. Signal indicator works fine in non-safe 906.
Wifi seems solid. Netflix and mp4 video is working
Guess we "just" need audio and camera now.
Thanks Hash and kexec team
EDIT: Oh, and I forgot to say F*CK YOU MOTO!

Amazing! :good:

THANK YOU CM9 TEAM!
and hash and jonpry

I'm a bit confused as to why the phone doesn't work in my tests - I get a force close whenever I try to make a call and attempting to call the phone results in "number unavailable".
rojocapo reports it as working on GSM in argentina, so I wonder what the difference might be.
I've tried *#*#info#*#*, which shows the phone on GSM auto, switching to GSM only doesn't seem to help - and of course I cleared cache+data before flashing.

rojocapo said:
GSM on Movistar Argentina network is working fine (850 mhz/1900mhz UMTS). SMS is ok too.
The GSM level indicator is stuck in the middle. *#*#INFO#*#* Phone information says Signal Strength 0dBm 97 asu. Seen this before in previous ICS builds. Signal indicator works fine in non-safe 906.
Wifi seems solid. Netflix and mp4 video is working
Guess we "just" need audio and camera now.
Thanks Hash and kexec team
EDIT: Oh, and I forgot to say F*CK YOU MOTO!
Click to expand...
Click to collapse
By GSM you are referring to voice calls, or to voice calls plus data connection? And if data connection is alive in this build, did you need to configure the APNs?
Enviado desde mi XT860 usando Tapatalk 2

thingonaspring said:
I'm a bit confused as to why the phone doesn't work in my tests - I get a force close whenever I try to make a call and attempting to call the phone results in "number unavailable".
...
I've tried *#*#info#*#*, which shows the phone on GSM auto, switching to GSM only doesn't seem to help - and of course I cleared cache+data before flashing.
Click to expand...
Click to collapse
Is doing the '#info' stuff the same as going to the Network Settings and clicking on the right radio button? For me, the default is CDMA/WCDMA and selecting GSM Auto does the trick, but not without a reboot.

My phone now seems to be bricked. Believe it or not, I was inside the XDA app and suddenly the phone locked up. No response to the touchscreen or hard keys. I did a battery pull and the I don't even get the Motorola dual-core logo any more.
The phone was on USB charge all the time during the KEXEC tests.
I'll try with another battery and a wall charger.
EDIT: NEVERMIND, battery was at 0%. Plugged it to the wall charger for a while an now it booted up. Maybe USB charging is not working ok? Strange...

rojocapo said:
My phone now seems to be bricked. Believe it or not, I was inside the XDA app and suddenly the phone locked up. No response to the touchscreen or hard keys. I did a battery pull and the I don't even get the Motorola dual-core logo any more.
The phone was on USB charge all the time during the KEXEC tests.
I'll try with another battery and a wall charger.
EDIT: NEVERMIND, battery was at 0%. Plugged it to the wall charger for a while an now it booted up. Maybe USB charging is not working ok? Strange...
Click to expand...
Click to collapse
I have problems with usb charging on all roms. Only works in usb mass storage mode.
Sent from my XT860 using xda premium

the_linkin3000 said:
By GSM you are referring to voice calls, or to voice calls plus data connection? And if data connection is alive in this build, did you need to configure the APNs?
Enviado desde mi XT860 usando Tapatalk 2
Click to expand...
Click to collapse
thingonaspring said:
I'm a bit confused as to why the phone doesn't work in my tests - I get a force close whenever I try to make a call and attempting to call the phone results in "number unavailable".
rojocapo reports it as working on GSM in argentina, so I wonder what the difference might be.
I've tried *#*#info#*#*, which shows the phone on GSM auto, switching to GSM only doesn't seem to help - and of course I cleared cache+data before flashing.
Click to expand...
Click to collapse
By GSM I am referring to voice plus data connection. I always use an app called HiAPN to automatically detect my APN settings by reading the network id from the SIM card. The app was complaining about "no SIM card inserted", so did INFO and set the network to GSM auto. After a reboot HiAPN set the APN correctly and data was working.
I was also getting the "number unavailable" message before setting the network to GSM auto and rebooting.

rojocapo said:
My phone now seems to be bricked. Believe it or not, I was inside the XDA app and suddenly the phone locked up. No response to the touchscreen or hard keys. I did a battery pull and the I don't even get the Motorola dual-core logo any more.
The phone was on USB charge all the time during the KEXEC tests.
I'll try with another battery and a wall charger.
EDIT: NEVERMIND, battery was at 0%. Plugged it to the wall charger for a while an now it booted up. Maybe USB charging is not working ok? Strange...
Click to expand...
Click to collapse
LOL! Yeah, and the battery indicator is broken.

Bobbar said:
LOL! Yeah, and the battery indicator is broken.
Click to expand...
Click to collapse
Yup, it's broken.
BTW, I tried the Razr Beats patch and I still have no sound.

[XPOSED] Mobile Radio Active Fix

Hey Guys, i have a Note N910C updated to lollipop, and as usual google has fuc*ed up again, the Cell Standby takes alot of battery because it doesnt end the connection. @pyler made a fix as an exposed module, i have tested it on my Note 4 and the Battery Life is Great after using it!!
Description:
When mobile data (2G or 3G) is switched on, all the internet apps continue to consume battery and keep the mobile data active unless they are force stopped. On kitkat, this didn't happen because apps stopped using mobile data whenever their transaction was over. But here in lollipop, they don't seem to stop ever and cause a huge battery drain.
Click to expand...
Click to collapse
Source: https://code.google.com/p/android/issues/detail?id=165558
Fix:
http://forum.xda-developers.com/xposed/modules/xposed-mobileradioactivefix-t3132956

Ather said:
Hey Guys, i have a Note N910C updated to lollipop, and as usual google has fuc*ed up again, the Cell Standby takes alot of battery because it doesnt end the connection. @pyler made a fix as an exposed module, i have tested it on my Note 4 and the Battery Life is Great after using it!!
Description:
Source: https://code.google.com/p/android/issues/detail?id=165558
Fix:
http://forum.xda-developers.com/xposed/modules/xposed-mobileradioactivefix-t3132956
Click to expand...
Click to collapse
How did you use xposed on touchwiz??

SirHydarnes said:
How did you use xposed on touchwiz??
Click to expand...
Click to collapse
Arter

jinosong said:
Arter
Click to expand...
Click to collapse
huh?

SirHydarnes said:
huh?
Click to expand...
Click to collapse
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3113463

just for aosp or for touchwiz as well?
Inviato dal mio SM-N910F utilizzando Tapatalk

It was fixed in CM long time ago, but Google has yet to implement it....maybe android 6.0 has the fix

Ather said:
It was fixed in CM long time ago, but Google has yet to implement it....maybe android 6.0 has the fix
Click to expand...
Click to collapse
aint it fixed in 5.1.1 ?

repo version is also available : http://repo.xposed.info/module/com.pyler.mobileradioactivefix

ziotom2 said:
just for aosp or for touchwiz as well?
Inviato dal mio SM-N910F utilizzando Tapatalk
Click to expand...
Click to collapse
If you are on 5.1.1 Touchwiz and have ARM7 32 bit snapdragon 805 like SM-N910P, there is no xposed framework yet.
You would have to go to AOSP like CM12.1 which didn't work out for me.

wanam released xposed for 32bit samsung devices

any bug experience like people cannot hear my voice on call? i can hear them but they cant

Ather said:
It was fixed in CM long time ago, but Google has yet to implement it....maybe android 6.0 has the fix
Click to expand...
Click to collapse
Has 5.1.1 fixed it in n910c or not yet?

hey guys now I can't permanently keep the data to " wcdma only" by going in phone testing (*#*#4636#*#*) remember that?
perhaps it is because of the "mobile active radio fix"
Xposed module because it was working fine earlier but even though now I have tried disabling module and uninstalling module but I can't change it to wcdma only, it keeps fixed on gsm only.
even though in setting I have it set to 3g preferred but because of poor reception many time it goes to 2g and back to 3g it is very irritating.
btw I am able to use 3g, can anyhody tell me how to fix that with fixing of mobile radio active bug
or is it a problem with the cm12.1 itself, btw I'll post in both forums

Is this only Google app problem? Cause every time Google positioning goes to sky when mobile data is turned on.

The module causes reboot on s6 edge MM. Was working fine on lollipop
Sent from my SM-G925F

I also wanted to give it a try and installed it on MM (CM13). Sadly, I also only get a rebooting device.
Battery drain is Huge from Mobile radio and it is Active almost all the time. Maybe a total different bug?

FlipSchwip said:
I also wanted to give it a try and installed it on MM (CM13). Sadly, I also only get a rebooting device.
Battery drain is Huge from Mobile radio and it is Active almost all the time. Maybe a total different bug?
Click to expand...
Click to collapse
There's another thread with un youssef version
Sent from my SM-G925F

GPS issue's on OnePlus 3 fix needed

So I know allot of users experience GPS issues.
So I was a regular of freedom OS due to a louder voice on Google maps issue I decided to install the regular OOS beta.
Constantly having GPS issues, with allot of different roms.
So I flashed back to official 4.1.6 and what happens today on the freeway, jup GPS stopped again. Could this be a magisk issue?
So I tried topnttp and GPS test. Nothing worked. What did you do to get GPS properly to work again.

I constantly lose fix on latest OpenBeta. Getting tired of it, I dont even remember when it worked properly.

Works fine here, absolutely no problem at all.

The problems seems to be related to the beta ROMs. So it would be an easy fix to install another ROM ??*
Gesendet von meinem ONEPLUS A3003 mit Tapatalk

Neo0 said:
The problems seems to be related to the beta ROMs. So it would be an easy fix to install another ROM ??*
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
Click to expand...
Click to collapse
I still have issue's on GPS also with 4.1.6 are you guys use 4G ?
If yes can you check if you still have issue's on 3G?

Darkje said:
I still have issue's on GPS also with 4.1.6 are you guys use 4G ?
If yes can you check if you still have issue's on 3G?
Click to expand...
Click to collapse
Works flawless on both..

Neo0 said:
The problems seems to be related to the beta ROMs. So it would be an easy fix to install another ROM ??*
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
Click to expand...
Click to collapse
Puddi_Puddin said:
Works flawless on both..
Click to expand...
Click to collapse
And you are actually using it right. Not just turn it on check gmaps and jup it works ... Your really drive a car or whatever for let's say 30min to a hour or so.

Darkje said:
And you are actually using it right. Not just turn it on check gmaps and jup it works ... Your really drive a car or whatever for let's say 30min to a hour or so.
Click to expand...
Click to collapse
Yes, I use it as navigation alot. Other then some calibration issues it is fine.

Darkje said:
And you are actually using it right. Not just turn it on check gmaps and jup it works ... Your really drive a car or whatever for let's say 30min to a hour or so.
Click to expand...
Click to collapse
I'm using it for runtastic and for navigation very frequently without problems.
Gesendet von meinem ONEPLUS A3003 mit Tapatalk

I'm on a custom ROM with OB firmware and there are problems on GPS fix with waze (vertex). Could it be related to the firmware ?

I was able to fix my GPS issues by switching Location to High Accurate. Works great after this

_millig_ said:
I'm on a custom ROM with OB firmware and there are problems on GPS fix with waze (vertex). Could it be related to the firmware ?
Click to expand...
Click to collapse
Could be, I think it has something to do with 4g. For some reason.
QUOTE=qbanlinxx;73417288]I was able to fix my GPS issues by switching Location to High Accurate. Works great after this[/QUOTE]
I don't think it is fixed, I think the issues will return. Then you switch and reset te connection and it will work for a while.

After installing the app GPS Status and clearing A-GPS data it worked for me. Before i had a few problems. (I'm on the latest beta/Experience OS ROM)

GPS is working as long you are connected to 4G or 3G. If you drive in a zone where the phone has to switch from 4G to 3G or where is no signal, GPS stops working.
Like other users who say, they have no problems: I also have no problems. I can drive in my city for hours without problems. But if I drive outside of city zone, problems start.

For those having GPS problems.
I have written this guide that might help you guys.
[GUIDE] How to FIX your GPS | Slow/Not Working/Not Fixing/Not Finding GPS [OP3/T]

LineageOS 13 from Dinolek

Dinolek has published his newest Lineage OS for Redmi note 2:
You can download it from here:
https://github.com/HermesRepos/android_device_xiaomi_hermes/releases
Bugs:
FM Radio (doesnt work)
Signal problems?
Bluetooth stuck sometimes?
Enforcing selinux
?

Many thanks
Sorry for my bad English
Many thanks for you Guys. I'm installed this Rom and it look good.
But could you pls advice how can I have "double tap to wake up screen (like other Rom - RR)".
And second, Music player is not working on my phone. It doesn't play any songs, just next next.. from start to end of playlist. Kindly tell me how to fix this bug.

i got "Restricted access changed" notification and no signal.

redminote2 said:
i got "Restricted access changed" notification and no signal.
Click to expand...
Click to collapse
Do you always have bad reception, or just in this rom?
First, set up the same apn you got in miui. Miui und lineage have different default apns, so it might not work out of the box.
If it is the same after that, let us know.
(ps have the same issue, but I always got horrible reception no matter if miui or los so it is hard for me to test)

M47Z said:
Do you always have bad reception, or just in this rom?
First, set up the same apn you got in miui. Miui und lineage have different default apns, so it might not work out of the box.
If it is the same after that, let us know.
(ps have the same issue, but I always got horrible reception no matter if miui or los so it is hard for me to test)
Click to expand...
Click to collapse
only in this ROM, in MIUI no issue.
i found work around in my device, if you in network mode 4G (LTE) change it to 3G, then when normal change it back to 4G. you have to do this every time your device restart.

Hello All, does this ROM still in development and with many bugs?
Still looking Android 6 or up for my old Redmi Note 2...thanks
Sent from my Nexus 6 using Tapatalk

Is there any news about the development?

Im getting a fair bit of phoning home to China, EU/UK rom

So ok first off, i really do love this phone. I got it for the camera and for content creation and its great for it...
I had a Redmi note 4 before, and for a couple of years Ive been using a firewall since reading about a lot of chinese phones sending large amounts of data to china.
Now yes my old phone did phone home A LOT. So thats why i installed noroot firewall to keep an eye on things.
And literally every service phoned home. Many services that have no right connecting to the internet.
Now come 10t, i read that because this is an offical EU phone with EU rom and not a grey import, it should be following all the EU rules on data collection... So basically turn everything off it shouldnt contact home.
Trouble is..... even though I have turned most of the things off (outside updating service) many of the apps still phone home... Analytics, MSA DOWNLOADs, file explorer, mi remote, compass, clock security.... and other framework services. All phoning home to servers in china.
Ive not really done a deep dive into exactly what service is sending what data. But Why would downloads connect to a chinese IP every time i download something off the app store.... Or open Chrome?
Well using firewall now to keep things locked down.
Has anyone else seen this kind of activity on EU phones? Is anyone making a clean rom that remove this kind of sus activity?

That's what you have to deal with if you want to use MIUI.
Why not root the phone and flash Lineage?

d3smond said:
That's what you have to deal with if you want to use MIUI.
Why not root the phone and flash Lineage?
Click to expand...
Click to collapse
thats on the cards tbh...
is Lineage fully ported yet? With everything working?

NutsyUK said:
thats on the cards tbh...
is Lineage fully ported yet? With everything working?
Click to expand...
Click to collapse
Yes everything is working except DT2W.
There is minor bugs that will be fixed.
It's very stable.

d3smond said:
Yes everything is working except DT2W.
There is minor bugs that will be fixed.
It's very stable.
Click to expand...
Click to collapse
Some 5ghz wifi bands aren't working
Auto rotate doesn't work
Bluetooth connection to audio devices fails after a call
Screen doesn't wake up when someone calls in like 90% of calls
Lineage Recovery bootloops
And yes dt2w doesn't work. Those are not minor bugs...

calinorg said:
Some 5ghz wifi bands aren't working
Auto rotate doesn't work
Bluetooth connection to audio devices fails after a call
Screen doesn't wake up when someone calls in like 90% of calls
Lineage Recovery bootloops
And yes dt2w doesn't work. Those are not minor bugs...
Click to expand...
Click to collapse
Don't know about 5ghz, I haven't have any issues with 5ghz. It's fixed in the latest version? At least it says so in the notes.
Auto rotation works fine for me. Have't noticed the issue with screen not waking up during incoming calls but I rarely receive or make calls.
I only used my bluetooth in ear for listening to music, not for calls but I se someone wrote it can be fixed by lowering volume a bit.
Lineage recovery bootloops if you flash it to recovery but if you fastboot boot the img it will boot fine every time.

d3smond said:
Don't know about 5ghz, I haven't have any issues with 5ghz. It's fixed in the latest version? At least it says so in the notes.
Auto rotation works fine for me. Have't noticed the issue with screen not waking up during incoming calls but I rarely receive or make calls.
I only used my bluetooth in ear for listening to music, not for calls but I se someone wrote it can be fixed by lowering volume a bit.
Lineage recovery bootloops if you flash it to recovery but if you fastboot boot the img it will boot fine every time.
Click to expand...
Click to collapse
That's all workarounds, that's why I say these are not minor bugs. I had all of those problems. I had 5ghz problem because my wifi router was set to a channel lineage couldn't read. Lowering volume, and turning bluetooth on/off couldn't fix it for me, only restart worked. Auto rotation and blank screen during calls were also my problems. Well to end offtopic, I'll wait for stable pe or similar rom before switching from global rom. I have pihole set up as blocking firewall at home so it helps a ton with phoning home...

ive also tried using noroot firewall, which worked fine on my old phone. but no matter the battery saver settings, it keeps getting shut down by the phone... So thats not secure.

NutsyUK said:
ive also tried using noroot firewall, which worked fine on my old phone. but no matter the battery saver settings, it keeps getting shut down by the phone... So thats not secure.
Click to expand...
Click to collapse
Did you try to turn off MIUI OPTIMIZATION in Developer option?

Developer options? I can't find that...

Ahh found them... Had to enable them first... Been a while forgot about that.