Database Develop

Huge problems with GPS!

Hello everyone.
Recently i've been having problems using GPS. Whenever i am firing up Maps / GPS Status / whatever app that uses GPS, it just won't get a GPS fix.
I also checked logcat output, and all i get is:
D/libgps ( 142): qct_gps_set_position_mode = 1, fix_frequency = 1
D/libgps ( 142): qct_gps_start
D/GpsLocationProvider( 142): Acquiring wakelock
D/libgps ( 142): PDSM_PD_EVENT_COMM_BEGIN
D/libgps ( 142): calling sAGpsStatusCallback GPS_REQUEST_AGPS_DATA_CONN
D/libgps ( 142): qct_agps_data_conn_open: internet.t-mobile
D/libgps ( 142): DeferredActionThread calling send_pdsm_atl_post_event PDSM_AT
L_EVENT_OPEN_SUCCESS internet.t-mobile
D/NetworkLocationProvider( 142): addListener(): apps.maps
W/InputManagerService( 142): Window already focused, ignoring focus gain of: co
[email protected]
D/libgps ( 142): PDSM_PD_EVENT_COMM_CONNECTED
D/libgps ( 142): PDSM_PD_EVENT_GPS_BEGIN
D/libgps ( 142): PDSM_PD_EVENT_COMM_DONE
D/libgps ( 142): calling sAGpsStatusCallback GPS_RELEASE_AGPS_DATA_CONN
D/libgps ( 142): qct_agps_data_conn_closed
Click to expand...
Click to collapse
No errors here at all. However i also checked dmesg, as i guess that a hardware related issue would show here first:
<4>[ 714.924957] msm_i2c msm_i2c.0: Warning bus was busy (2)
<4>[ 723.965454] msm_i2c msm_i2c.0: Warning bus was busy (1)
<4>[ 725.955017] msm_i2c msm_i2c.0: Warning bus was busy (2)
<4>[ 733.675537] msm_i2c msm_i2c.0: Warning bus was busy (3)
<4>[ 738.955352] msm_i2c msm_i2c.0: Warning bus was busy (1)
<4>[ 754.585418] msm_i2c msm_i2c.0: Warning bus was busy (3)
Click to expand...
Click to collapse
does anyone know what these errors mean? are they related to GPS?
I tried all of this on SuperD and FastTest, with and without default kernel (using 780MHz kernel usually)
However it made no difference.
I also tried to wipe, no luck.
And at last i took a look at the baseband, which differed by one letter from the one here:
http://code.google.com/p/sapphire-port-dream/
So i flashed that one, but, no luck!
This is seriously driving me crazy since i am not wanting to roll back to stock and send the phone in Please help!

[Q] wifi stopped working, logcat inside

he everyone,
i using my trusty with CM7.0.1 for along time, actually since CM7.0.1 was released and all was fine.
until today, when my wifi stopped working.
at first i saw that the unlock screen will no show, and after poking around i figured that it was because every time wifi was trying to be enabled it hanged and cause the phone to act weird.
trying to turn on wifi will cause it to hang, and sometimes show the "error" error on the wifi setting.
you can see my logcat during attempt to activate wifi, please help me understand what is going on here, and figure out if my wifi is toasted.
i can think of ANYTHING that i did that might have caused this, i installed nothing, changed no setting i could think of.
the only thing i can think of, is that i washed the dishes with the phone in my pocket, i do not think i got wet, but who knows.
what i did notice in the log were a few things:
1. Failed to disable WPA in the driver.
2. Supplicant not running, cannot connect
3. Supplicant died unexpectedly
4. Reset connections and stopping DHCP
5. Disabling interface
all do not sound very promising...
help please!
here are the logcat:
Code:
I/ActivityManager( 165): Displayed com.android.settings/.WirelessSettings: +383ms
D/SettingsAppWidgetProvider( 638): Widget is from a previous version... Let's update
D/SettingsAppWidgetProvider( 638): No instances yet... Wait for at least one instance to exist before adding global settings
D/dalvikvm( 638): GC_CONCURRENT freed 88K, 46% free 3016K/5575K, external 837K/1034K, paused 2ms+3ms
D/WifiService( 165): ACTION_BATTERY_CHANGED pluggedType: 2
D/WifiService( 165): acquireWifiLockLocked: WifiLock{NetworkLocationProvider type=2 [email protected]}
E/wpa_supplicant( 666): ioctl[SIOCGIFFLAGS]
D/SettingsAppWidgetProvider( 638): Widget is from a previous version... Let's update
D/SettingsAppWidgetProvider( 638): No instances yet... Wait for at least one instance to exist before adding global settings
E/wpa_supplicant( 666): ioctl[SIOCSIWPMKSA]
E/wpa_supplicant( 666): ioctl[SIOCSIWMODE]
E/wpa_supplicant( 666): ioctl[SIOCGIRANGE]
E/wpa_supplicant( 666): ioctl[SIOCGIWMODE]
E/wpa_supplicant( 666): ioctl[SIOCSIWAP]
E/wpa_supplicant( 666): ioctl[SIOCSIWENCODEEXT]
E/wpa_supplicant( 666): ioctl[SIOCSIWENCODE]
E/wpa_supplicant( 666): ioctl[SIOCSIWENCODEEXT]
E/wpa_supplicant( 666): ioctl[SIOCSIWENCODE]
E/wpa_supplicant( 666): ioctl[SIOCSIWENCODEEXT]
E/wpa_supplicant( 666): ioctl[SIOCSIWENCODE]
E/wpa_supplicant( 666): ioctl[SIOCSIWENCODEEXT]
E/wpa_supplicant( 666): ioctl[SIOCSIWENCODE]
I/wpa_supplicant( 666): CTRL-EVENT-STATE-CHANGE id=-1 state=0 BSSID=00:00:00:00:00:00
E/wpa_supplicant( 666): Failed to disable WPA in the driver.
E/wpa_supplicant( 666): ioctl[SIOCGIWMODE]
E/wpa_supplicant( 666): ioctl[SIOCSIWAP]
E/wpa_supplicant( 666): ioctl[SIOCGIFFLAGS]
D/WifiService( 165): releaseWifiLockLocked: WifiLock{NetworkLocationProvider type=2 [email protected]}
D/dalvikvm( 279): GC_EXPLICIT freed 237K, 49% free 3164K/6151K, external 3246K/3357K, paused 44ms
E/WifiHW ( 165): Supplicant not running, cannot connect
E/WifiHW ( 165): Supplicant not running, cannot connect
E/WifiHW ( 165): Supplicant not running, cannot connect
V/WifiStateTracker( 165): Supplicant died unexpectedly
D/WifiStateTracker( 165): Reset connections and stopping DHCP
D/WifiStateTracker( 165): Disabling interface
D/WifiStateTracker( 165): Reset connections and stopping DHCP
D/Tethering( 165): MasterInitialState.processMessage what=3
D/GTalkService( 311): ##### Network broadcast (connected=true) type=WIFI, state=DISCONNECTED
D/GTalkService( 311): [GTalkConnection.1] ### networkStateChanged: active and curr network type/state are the same(0/CONNECTED), ignore
D/Tethering( 165): MasterInitialState.processMessage what=3
D/GTalkService( 311): ##### Network broadcast (connected=true) type=mobile, state=CONNECTED
D/GTalkService( 311): [GTalkConnection.1] ### networkStateChanged: active and curr network type/state are the same(0/CONNECTED), ignore
D/SettingsAppWidgetProvider( 638): Widget is from a previous version... Let's update
D/SettingsAppWidgetProvider( 638): No instances yet... Wait for at least one instance to exist before adding global settings
D/CMStats ( 428): CONNECTIVITY_ACTION: noConnectivity = false
I/MediaUploader( 593): No need to wake up
D/CMStats ( 428): CONNECTIVITY_ACTION: noConnectivity = false
I/MediaUploader( 593): No need to wake up
D/dalvikvm( 311): GC_CONCURRENT freed 431K, 48% free 3201K/6151K, external 0K/512K, paused 12ms+3ms
D/WifiStateTracker( 165): Disabling interface
D/SettingsAppWidgetProvider( 638): Widget is from a previous version... Let's update
D/SettingsAppWidgetProvider( 638): No instances yet... Wait for at least one instance to exist before adding global settings
D/dalvikvm( 395): GC_EXPLICIT freed 379K, 51% free 2799K/5703K, external 0K/0K, paused 65ms
D/dalvikvm( 428): GC_EXPLICIT freed 156K, 49% free 2897K/5575K, external 0K/0K, paused 53ms
D/dalvikvm( 593): GC_EXPLICIT freed 94K, 50% free 2704K/5379K, external 0K/0K, paused 65ms
thank you!

this might be a hardware issue. Try reseating the cables on the bottom of the phone and see if it fixes your issue.
The Nexus one cables become loose after a while, I know mine did.

Bluetooth Amazon FireTV Stick Remote

I have made some progress in finding out whats wrong but no idea how to fix it.
After installing evtest I get the following:
Code:
OpenELEC:~ # cat /proc/bus/input/devices
I: Bus=0005 Vendor=1949 Product=0404 Version=011b
N: Name="Amazon Fire TV Remote"
P: Phys=00:1a:7d:da:71:13
S: Sysfs=/devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3:1.0/bluetooth/hci0/hci0:71/0005:1949:0404.0001/input/input0
U: Uniq=a0:02:dc:e0:f9:d7
H: Handlers=kbd event0
B: PROP=0
B: EV=10001b
B: KEY=10000 1110 40000800 1681 0 0 0
B: ABS=100 0
B: MSC=10
Code:
OpenELEC:~ # evtest /dev/input/event0
Input driver version is 1.0.1
Input device ID: bus 0x5 vendor 0x1949 product 0x404 version 0x11b
Input device name: "Amazon Fire TV Remote"
Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
Event code 96 (KEY_KPENTER)
Event code 103 (KEY_UP)
Event code 105 (KEY_LEFT)
Event code 106 (KEY_RIGHT)
Event code 108 (KEY_DOWN)
Event code 139 (KEY_MENU)
Event code 158 (KEY_BACK)
Event code 164 (KEY_PLAYPAUSE)
Event code 168 (KEY_REWIND)
Event code 172 (KEY_HOMEPAGE)
Event code 208 (KEY_FASTFORWARD)
Event type 3 (EV_ABS)
Event code 40 (ABS_MISC)
Value 0
Min 0
Max 255
Event type 4 (EV_MSC)
Event code 4 (MSC_SCAN)
Properties:
Property type 20 (EV_REP)
Property code 0 (REP_DELAY)
Value 1000
Property code 1 (REP_PERIOD)
Value 33
Testing ... (interrupt to exit)
***********************************************
This device is grabbed by another process.
No events are available to evtest while the
other grab is active.
In most cases, this is caused by an X driver,
try VT-switching and re-run evtest again.
***********************************************
So something is capturing the input and not letting it go through. Any idea how to fix this?

Just an update. Connected a Bluetooth keyboard and that worked fine and gave the same evtest output saying something else was grabbing the input which would mean that's not the problem with the Amazon remote.
Again, any help is welcomed!

This has been bugging me for the last day or two as well; and to be honest - still is.
The below will work but just seems "wrong" to have to use eventlircd for this...
/storage/.config/eventlircd.d/aftvsremote.evmap
(copy /etc/eventlircd.d to /storage/.config/eventlircd.d)
Code:
KEY_KPENTER = KEY_OK
KEY_UP = KEY_UP
KEY_LEFT = KEY_LEFT
KEY_RIGHT = KEY_RIGHT
KEY_DOWN = KEY_DOWN
KEY_MENU = KEY_EPG
KEY_BACK = KEY_EXIT
KEY_PLAYPAUSE = KEY_PLAY
KEY_REWIND = KEY_REWIND
KEY_HOMEPAGE = KEY_MEDIA
KEY_FASTFORWARD = KEY_FASTFORWARD
/storage/.config/autostart.sh
Bind mount because I'm too lazy to rebuild the openelec squashfs image
Code:
mount --bind /storage/.config/eventlircd.d/ /etc/eventlircd.d/
/storage/.config/udev.rules.d/99-eventlircd.rules
Code:
SUBSYSTEMS=="bluetooth", GOTO="begin-bluetooth"
GOTO="end-bluetooth"
LABEL="begin-bluetooth"
ATTRS{name}=="Amazon Fire TV Remote", \
ENV{eventlircd_enable}="true", \
ENV{eventlircd_evmap}="aftvsremote.evmap"
LABEL="end-bluetooth"

Thank you so much!!! I got a chance to enter the code today and it works perfectly! I had to repair after the initial reboot but it keeps pairing after that for all other reboots. I hope they put this into openelec from here on out.
Again thanks!

BT Calling Robotic Audio

Hi Guys,
As you may notice from my signature, I'm actually an LG G4 owner (attempting ) to assist with the development of Oreo roms for the G4. @kessaras and @steadfasterX have done a magnificent job so far and we have two bugs left - the torch tile in quick settings doesn't work (not a big deal right now, we just recommend an app as a workaround) and also we have robotic bt calling with a hands free set.
I have been browsing the hammerhead forums and noticed that this exact problem is also plaguing the Nexus 5 (and we share the same broadcom 4339 bt/wifi chipset, so I would imagine this is why we suffer from the same issue), and I was wondering whether it would be a good idea to share any ideas here as to how we could fix it - we have tweaked a lot of bluetooth settings so far but it has either made no difference or killed the bluetooth entirely.
@amaces I noticed you mentioned in your Unlegacy Android thread that you got it to work in a hardcoded and messy way - would it be possible for you to share it? I know you said it wasn't good for a production build, but if we could see how you got it working then it would definitely help us to find a proper fix.
Thanks for any help

I have that same problem. (android 8.1 or 9.0)
Nexus 5 D820

The issue is probably caused by the HIDLization and the introduction of eSCO command set. Prior to Oreo vendor specific commands(VSCs) were sent to the controller which would trigger I2S/PCM sco configuration.
When the HIDLization started the VSC for the sco configuration was removed 796523d and later on with the introduction of eSCO command setup these calls to the broadcom's libbt-vendor(pre-SCO setup) were completely removed a9152a2.
I tried retrieving retrieving these calls removed by eSCO(3/5), yet I cant get it working.
Here's what I've done so far:
system/bt stack
fb1d404
47f50f8-a2df04b
hardware/interfaces
dd21c98
The issue is either the way I attempt to send the VSC via send_command method, or in some of the methods which are supposed to notify the AG that the pre-sco is done.
So far I noticed that the code of bta_ag_ci_sco_open_continue method is never reached, but things could've went south even before this method, I dunno.
Looking at the snoop log nothing is even sent to the controller about this.
@steadfasterX @ThePiGuy if you guys are still interested in fixing this issue, you should really focus on retrieving these calls imho.

Would be good if anyone tries this c0d86fb. What I am trying is basically to avoid the need of hw_set_audio_state() call from bt stack to configurare SCO over PCM.
Should be accompanied by this commit in order to work.
 @amaces @razorloves

Hi there,
Sorry for delay. I was a bit busy today. Here is my workaround for bt issue:
1) android_hardware_broadcom_libbt
2) device tree
Honestly this workaround is terrible (explanations will be provided below) and disabled by default. You should add two parameters to vendor config in order to activate it:
1) BTHW_FW_EXTENDED_CONFIGURATION - Enable/disable the fix. TRUE/FALSE. Default value is FALSE.
2) BTHW_FW_EXTENDED_SCO_CODEC - SCO codec. Use the numeric value from the sco_codec_t enum. Default value is SCO_CODEC_CVSD.
Seems that the problem lies in firmware for our BT chip and eSCO command set. Controller have invalid audio configuration or doesn't have any audio configuration at all after firmware upload. That was not a problem before this change (Thanks @Sashko98 for research). I've tried a solution proposed by @Sashko98 but nothing changed. After a couple of days playing with different parameters in configs i noticed interesting line in logcat:
Code:
W/bt_hci:
filter_incoming_event command complete event with no matching command (opcode: [B]0xfc6d[/B])
0xfc6d is a HCI_VSC_WRITE_I2SPCM_INTERFACE_PARAM constant defined here and used inside of the hw_sco_i2spcm_config method. Seems that bt controller responds to HCI_VSC_WRITE_I2SPCM_INTERFACE_PARAM command. But why we still have an issue with audio? The answer is simple: SCO configuration can not be completed because bt_hci blocks events and callbacks are not called at all! If device uses SCO_INTERFACE_PCM bus interface then hw_sco_i2spcm_config method will send 3 commands: HCI_VSC_WRITE_I2SPCM_INTERFACE_PARAM, HCI_VSC_WRITE_SCO_PCM_INT_PARAM, HCI_VSC_WRITE_PCM_DATA_FORMAT_PARAM. Each next command will be sent only if previous was sent successfully and controller responded with correct status. Сontroller responds, but bt_hci blocks the very first event and SCO configuration fails.
We have 2 possible solutions here:
1) Understand why bt_hci blocks events... This is ideal solution, but not easy! bt_hci is a part of system bluetooth stack and bluetooth stack is huge!
2) Send all the necessary commands without waiting for response from bt controller. Yep, i know how it sounds but it works! At least for now...
I've implemented solution #2. Look at hw_config_continue_sco_setup method. It works just like the hw_set_SCO_codec method but doesn't wait for response from bt controller. Why the hw_set_SCO_codec? Because it sends one more command related to WBS before calling the hw_sco_i2spcm_config.
As i said before i think this solution is terrible. Here are my concerns about it:
1) Uncontrolled commands sent to bt controller. Who knows how long this will work...
2) Can be applied only for broadcom chips.
That's all I found at the moment. I will try to implement the solution #1, but I can't tell whether it will work. Feel free to contact me if you have any questions/ideas/improvements.
Many thank to devs who still support our old hammy! @razorloves, @amaces, @EnesSastim, @voidz777, @KiD3991, @Hannibal226, @hhrokarvi, @Sashko98 and many other! You guys are awesome! Thanks a lot for your work!!! All this would be impossible without you!!!
PS: Sorry for my terrible english

z3DD3r said:
We have 2 possible solutions here:
1) Understand why bt_hci blocks events... This is ideal solution, but not easy! bt_hci is a part of system bluetooth stack and bluetooth stack is huge!
2) Send all the necessary commands without waiting for response from bt controller. Yep, i know how it sounds but it works! At least for now...
As i said before i think this solution is terrible. Here are my concerns about it:
1) Uncontrolled commands sent to bt controller. Who knows how long this will work...
2) Can be applied only for broadcom chips.
Click to expand...
Click to collapse
If i understand correctly this is just a warning that the hci module doesn't recognize the command, which I believe is normal since the call is not made from the bt stack( which is not quite needed at this point anyway).
What is curious to me is why are the VSCs even required. I mean I tried to replicate the exact clock/codec etc.. configuration as it would've been configured if the VSCs were send, in the vnd config and there was no change at all. Probably there is something in the hcd patch about this, which would explain why my attempt in the post above works for Galaxy Note 3 and doesn't work for us.(if i am right than your hack could be considered just as extended of the hcd patch.)
Broadcom's libbt-vendor is pretty much obsolete, thus it will be easier to maintain this hack in further OS versions. Changes to bt-stack to get this work would be just too much time consuming to maintain considering that the guys from Google working on the AOSP want as less VSCs as possible.
Read this https://source.android.com/devices/bluetooth just to see how the Bluetooth works,if you plan to retrieve the VSCs to bt stack.

Sashko98 said:
If i understand correctly this is just a warning that the hci module doesn't recognize the command, which I believe is normal since the call is not made from the bt stack( which is not quite needed at this point anyway).
Click to expand...
Click to collapse
This is partly true. This warning means that HCI received event for command which was not sent from bt stack. Some commands are send directly from the VendorInterface class and should be handle only here.
Sashko98 said:
What is curious to me is why are the VSCs even required. I mean I tried to replicate the exact clock/codec etc.. configuration as it would've been configured if the VSCs were send, in the vnd config and there was no change at all.
Click to expand...
Click to collapse
It is not enough to just setup the vnd config. U still need to call hw_sco_i2spcm_config or hw_set_SCO_codec. But as i described above these methods fails.
Sashko98 said:
Probably there is something in the hcd patch about this, which would explain why my attempt in the post above works for Galaxy Note 3 and doesn't work for us.(if i am right than your hack could be considered just as extended of the hcd patch.)
Click to expand...
Click to collapse
You are right! This issue can be fixed new firmware or additional firmware prepatch. But we will never receive such update) I did one experiment. Your fixes + custom firmware for our chip downloaded from here = working bt calls But this way is more crazy that my current hack)))
Sashko98 said:
Broadcom's libbt-vendor is pretty much obsolete, thus it will be easier to maintain this hack in further OS versions. Changes to bt-stack to get this work would be just too much time consuming to maintain considering that the guys from Google working on the AOSP want as less VSCs as possible.
Read this https://source.android.com/devices/bluetooth just to see how the Bluetooth works,if you plan to retrieve the VSCs to bt stack.
Click to expand...
Click to collapse
Looks like we don't need to change anything in bt stack. Seems i have found the real issue. Look at VendorInterface::HandleEvent method. Seems that this is an entry point for all events sent from controller. This method uses the internal_command to determine how the received event should be handled. internal_command is populated inside of transmit_cb which is called from the libbt-vendor. So, what happens if someone will send 2 commands one after another? First command will be recorded into the internal_command var and the second command will be recorded to internal_command var. Second command will overwrite the infrormation about first. And since the communication is made via UART, controller will sent us response for first command (which is already gone) and then response for second command. Thats why nothing works! Thats why i saw that strange lines in logcat!!!
All that means that your fix should work. U just need to improve it a bit:
1. android_hardware_interfaces. Move lib_interface_->op(BT_VND_OP_SCO_CFG, nullptr); right after the lib_interface_->op(BT_VND_OP_LPM_SET_MODE, &mode);
2. c0d86f. Call the hw_set_SCO_codec for PCM instead of hw_sco_i2spcm_config
I have not tried it myself yet. But logs and logic seems correct. Bt calls issue may be not fixed cos of initialization sequence, but all callbacks should be called correctly.
---------- Post added at 08:47 AM ---------- Previous post was at 08:37 AM ----------
Hmm, seems that based on my finding i can improve my initial solution. At least i can made controllable configuration of the SCO with all required callbacks! Will try it today...

z3DD3r said:
This is partly true. This warning means that HCI received event for command which was not sent from bt stack. Some commands are send directly from the VendorInterface class and should be handle only here.
Click to expand...
Click to collapse
The VendorInterface still comunicates with the bt stack via the hci_layer.
z3DD3r said:
It is not enough to just setup the vnd config. U still need to call hw_sco_i2spcm_config or hw_set_SCO_codec. But as i described above these methods fails.
You are right! This issue can be fixed new firmware or additional firmware prepatch. But we will never receive such update) I did one experiment. Your fixes + custom firmware for our chip downloaded from here = working bt calls But this way is more crazy that my current hack)))
Click to expand...
Click to collapse
In ideal case the hcd patch wouldn't need VSCs for such configuration, because It would've already been configured(what you tried with the custom patch just proves it). Appereantly Xperia Z3(shinano) is using its own solution by configuring the controller using bt drivers link. Perhaps this is why it is the only device I know of with BCM4339 Wifi/bt chip which didn't have any issues with bt-sco. Their code compiles perfectly with our kernel, but there are many init changes needed to happen to make it work.
z3DD3r said:
Looks like we don't need to change anything in bt stack. Seems i have found the real issue. Look at VendorInterface::HandleEvent method. Seems that this is an entry point for all events sent from controller. This method uses the internal_command to determine how the received event should be handled. internal_command is populated inside of transmit_cb which is called from the libbt-vendor. So, what happens if someone will send 2 commands one after another? First command will be recorded into the internal_command var and the second command will be recorded to internal_command var. Second command will overwrite the infrormation about first. And since the communication is made via UART, controller will sent us response for first command (which is already gone) and then response for second command. Thats why nothing works! Thats why i saw that strange lines in logcat!!!
Click to expand...
Click to collapse
If there is any race happening I think it should be handled by the VendorInterface, thought looking at the VendorInterface::HandleIncomingEvent method in vendor_interface.cc it is already handling such cases.
On Nougat the I2S/PCM interface was configured only when sco connection was established, if you look at the first eSCO commit you'll see that the initial idea was to keep the pre-SCO vendor setup link, thus I I used to be focused pretty much on bringing this back, till I understood there is no point, as it would require changes not only to the bt stack, but to Bluetooth app aswell.
As I said its just consumes too much time, not only to do it successfully, but to maintain it.
z3DD3r said:
All that means that your fix should work. U just need to improve it a bit:
1. android_hardware_interfaces. Move lib_interface_->op(BT_VND_OP_SCO_CFG, nullptr); right after the lib_interface_->op(BT_VND_OP_LPM_SET_MODE, &mode);
2. c0d86f. Call the hw_set_SCO_codec for PCM instead of hw_sco_i2spcm_config
..
Click to expand...
Click to collapse
hw_set_SCO_codec is useless at this point, as everything goes back to hw_sco_i2spcm_config to configure sample rate for the required codec. The clock rate is the same regardless of the codec.
On my local builds I moved lib_interface_->op(BT_VND_OP_SCO_CFG, nullptr); to the end of the method. Just for the tests once I put it even in VendorInterface;;Open, doesn't really matter where it is as long as it is called. The problem is that the callback methods arent reached. I tried sending BT_VND_OP_SET_AUDIO_STATE opcode command to start the whole sequene, but it doesnt get past the first send VSC(HCI_VSC_ENABLE_WBS) I believe it was, exactly due to the cbacks.

Sashko98 said:
In ideal case the hcd patch wouldn't need VSCs for such configuration, because It would've already been configured(what you tried with the custom patch just proves it). Appereantly Xperia Z3(shinano) is using its own solution by configuring the controller using bt drivers . Perhaps this is why it is the only device I know of with BCM4339 Wifi/bt chip which didn't have any issues with bt-sco. Their code compiles perfectly with our kernel, but there are many init changes needed to happen to make it work.
Click to expand...
Click to collapse
I know another device - LG G2. Own bt driver can work, but it looks very complicated to me...
Sashko98 said:
If there is any race happening I think it should be handled by the VendorInterface, thought looking at the VendorInterface::HandleIncomingEvent() method in vendor_interface.cc it is already handling such cases.
Click to expand...
Click to collapse
I don't see any race conditions here. Just a simple mistake. Only one variable is used instead of queue. Maybe this interface wasn't designed to handle such cases...
Sashko98 said:
On Nougat the I2S/PCM interface was configured only when sco connection was established, if you look at the first eSCO commit you'll see that the initial idea was to keep the pre-SCO vendor setup [url=https://github.com/LineageOS/android_system_bt/commit/86f1b61e614b4110d953b91d1eee3812802c1f34#diff-91f58eb08ce9dea17af6a8fd5d3b313aR478]link
Click to expand...
Click to collapse
Sashko98 said:
, thus I I used to be focused pretty much on bringing this back, till I understood there is no point, as it would require changes not only to the bt stack, but to Bluetooth app aswell.
As I said its just consumes too much time, not only to do it successfully, but to maintain it.
Click to expand...
Click to collapse
Fully agree with you. Maintaining all those changes will be painful...
Sashko98 said:
hw_set_SCO_codec is useless at this point, as everything goes back to hw_sco_i2spcm_config to configure sample rate for the required codec. The clock rate is the same regardless of the codec.
Click to expand...
Click to collapse
Who knows. I'm using it cos BT_VND_OP_SET_AUDIO_STATE command actually call hw_set_SCO_codec and not the hw_sco_i2spcm_config. hw_set_SCO_codec sends one additional command to enable/disable WBS. It may be not necessary for Nexus 5, but it can be necessary for other devices. In any case i think we should make this behavior configurable.
Sashko98 said:
On my local builds I moved lib_interface_->op(BT_VND_OP_SCO_CFG, nullptr); to the end of the method. Just for the tests once I put it even in VendorInterface:pen(), doesn't really matter where it is as long as it is called. The problem is that the callback methods arent reached. I tried sending BT_VND_OP_SET_AUDIO_STATE opcode command to start the whole sequene, but it doesnt get past the first send VSC(HCI_VSC_ENABLE_WBS) I believe it was.
Click to expand...
Click to collapse
This is very strange. Look at my logcat (LOS wit BT fix):
Code:
06-18 09:06:15.850 I/bt_hwcfg(7282): hw_config_continue_sco_setup: set SCO related hardware settings
06-18 09:06:15.850 I/bt_hwcfg(7282): hw_config_continue_sco_setup: set SCO codec: 0x1
06-18 09:06:15.850 D/[email protected](7282): buffer_alloc_cb pts: 0x9f483e60, size: 14
[B]06-18 09:06:15.850 D/[email protected](7282): transmit_cb opcode: 0xfc7e, ptr: 0x9f483e60, cb: 0x8b2cfcf9 - First opcode from hw_set_SCO_codec[/B]
06-18 09:06:15.850 I/bt_hwcfg(7282): hw_config_continue_sco_setup: set SCO I2S/PCM codec: 0x1
06-18 09:06:15.850 D/[email protected](7282): buffer_alloc_cb pts: 0x9f483e60, size: 15
06-18 09:06:15.850 I/bt_hwcfg(7282): hw_config_continue_sco_setup: I2SPCM config {0x0, 0x0, 0x0, 0x4}
06-18 09:06:15.850 D/[email protected](7282): transmit_cb opcode: 0xfc6d, ptr: 0x9f483e60, cb: 0x8b2cfcf9
06-18 09:06:15.850 D/[email protected](7282): buffer_alloc_cb pts: 0x9f483e60, size: 16
06-18 09:06:15.850 I/bt_hwcfg(7282): hw_config_continue_sco_setup: SCO PCM configure {0x0, 0x4, 0x0, 0x0, 0x0}
06-18 09:06:15.850 D/[email protected](7282): transmit_cb opcode: 0xfc1c, ptr: 0x9f483e60, cb: 0x8b2cfcf9
06-18 09:06:15.850 D/[email protected](7282): buffer_alloc_cb pts: 0x9f483e60, size: 16
06-18 09:06:15.850 I/bt_hwcfg(7282): hw_config_continue_sco_setup: SCO PCM data format {0x0, 0x0, 0x3, 0x0, 0x0}
06-18 09:06:15.850 D/[email protected](7282): transmit_cb opcode: 0xfc1e, ptr: 0x9f483e60, cb: 0x8b2cfcf9
06-18 09:06:15.850 I/bt_hwcfg(7282): hw_config_continue_sco_setup: finish
06-18 09:06:15.850 D/[email protected](7282): firmware_config_cb result: 0
06-18 09:06:15.850 D/[email protected](7282): OnFirmwareConfigured result: 0
06-18 09:06:15.850 I/[email protected](7282): Firmware configured in 0.635s
06-18 09:06:15.850 D/[email protected](7282): OnFirmwareConfigured: lpm_timeout_ms 1500
06-18 09:06:15.850 I/bt_hci (7282): event_finish_startup
06-18 09:06:15.850 D/[email protected](7282): buffer_alloc_cb pts: 0x9f495958, size: 23
06-18 09:06:15.850 I/bt_core_module(7282): module_start_up Started module "hci_module"
06-18 09:06:15.850 D/[email protected](7282): transmit_cb opcode: 0xfc27, ptr: 0x9f495958, cb: 0x8b2cf4f9
06-18 09:06:15.850 D/[email protected](7282): OnFirmwareConfigured Calling StartLowPowerWatchdog()
06-18 09:06:15.851 D/[email protected](7282): sco_config_cb result: 0
06-18 09:06:15.851 D/[email protected](7282): OnScoConfigured result: 0
06-18 09:06:15.851 D/[email protected](7282): buffer_free_cb ptr: 0x9f483e50
[b]06-18 09:06:15.851 D/[email protected](7282): internal_command_event_match internal_command.opcode = FC27 opcode = fc7e - First event from bt controller[/b]
06-18 09:06:15.851 I/bt_osi_thread(7282): run_thread: thread id 7330, thread name bt_workqueue started
06-18 09:06:15.851 D/[email protected](7282): event_cb_ called
06-18 09:06:15.851 W/bt_hci (7282): filter_incoming_event command complete event with no matching command (opcode: 0xfc7e).
06-18 09:06:15.851 I/ (7282): [0618/090615.851280:INFO:btu_task.cc(107)] Bluetooth chip preload is complete
06-18 09:06:15.851 I/ (7282): [0618/090615.851843:INFO:gatt_api.cc(948)] GATT_Register 81818181-8181-8181-8181-818181818181
06-18 09:06:15.851 I/ (7282): [0618/090615.851972:INFO:gatt_api.cc(968)] allocated gatt_if=1
06-18 09:06:15.852 I/ (7282): [0618/090615.852038:INFO:gatt_api.cc(161)] GATTS_AddService
06-18 09:06:15.852 I/ (7282): [0618/090615.852094:INFO:gatt_api.cc(265)] GATTS_AddService: service parsed correctly, now starting
06-18 09:06:15.852 I/ (7282): [0618/090615.852276:INFO:gatt_api.cc(948)] GATT_Register 82828282-8282-8282-8282-828282828282
06-18 09:06:15.852 I/ (7282): [0618/090615.852333:INFO:gatt_api.cc(968)] allocated gatt_if=2
06-18 09:06:15.852 I/ (7282): [0618/090615.852402:INFO:gatt_api.cc(161)] GATTS_AddService
06-18 09:06:15.852 I/ (7282): [0618/090615.852455:INFO:gatt_api.cc(265)] GATTS_AddService: service parsed correctly, now starting
06-18 09:06:15.852 I/bt_bte (7282): BTE_InitTraceLevels -- TRC_HCI : Level 2
06-18 09:06:15.852 I/bt_bte (7282): BTE_InitTraceLevels -- TRC_L2CAP : Level 2
06-18 09:06:15.852 I/bt_bte (7282): BTE_InitTraceLevels -- TRC_RFCOMM : Level 2
06-18 09:06:15.852 I/bt_bte (7282): BTE_InitTraceLevels -- TRC_AVDT : Level 2
06-18 09:06:15.852 I/bt_bte (7282): BTE_InitTraceLevels -- TRC_AVRC : Level 2
06-18 09:06:15.852 I/bt_bte (7282): BTE_InitTraceLevels -- TRC_A2D : Level 2
06-18 09:06:15.852 I/bt_bte (7282): BTE_InitTraceLevels -- TRC_BNEP : Level 2
06-18 09:06:15.852 I/bt_bte (7282): BTE_InitTraceLevels -- TRC_BTM : Level 2
06-18 09:06:15.852 I/bt_bte (7282): BTE_InitTraceLevels -- TRC_HID_HOST : Level 2
06-18 09:06:15.852 I/bt_bte (7282): BTE_InitTraceLevels -- TRC_PAN : Level 2
06-18 09:06:15.852 I/bt_bte (7282): BTE_InitTraceLevels -- TRC_SDP : Level 2
06-18 09:06:15.852 I/bt_bte (7282): BTE_InitTraceLevels -- TRC_SMP : Level 2
06-18 09:06:15.852 I/bt_bte (7282): BTE_InitTraceLevels -- TRC_HID_DEV : Level 2
06-18 09:06:15.852 I/bt_bte (7282): BTE_InitTraceLevels -- TRC_BTAPP : Level 2
06-18 09:06:15.852 I/bt_bte (7282): BTE_InitTraceLevels -- TRC_BTIF : Level 2
06-18 09:06:15.853 I/bt_osi_thread(7282): run_thread: thread id 7331, thread name btu message loop started
[B]06-18 09:06:15.853 D/[email protected](7282): internal_command_event_match internal_command.opcode = FC27 opcode = fc6d - Second one[/B]
06-18 09:06:15.853 D/[email protected](7282): event_cb_ called
06-18 09:06:15.853 W/bt_hci (7282): filter_incoming_event command complete event with no matching command (opcode: 0xfc6d).
06-18 09:06:15.853 D/[email protected](7282): internal_command_event_match internal_command.opcode = FC27 opcode = fc1c
06-18 09:06:15.853 D/[email protected](7282): event_cb_ called
06-18 09:06:15.853 W/bt_hci (7282): filter_incoming_event command complete event with no matching command (opcode: 0xfc1c).
06-18 09:06:15.853 D/[email protected](7282): internal_command_event_match internal_command.opcode = FC27 opcode = fc1e
06-18 09:06:15.853 D/[email protected](7282): event_cb_ called
06-18 09:06:15.853 W/bt_hci (7282): filter_incoming_event command complete event with no matching command (opcode: 0xfc1e).
06-18 09:06:15.853 D/[email protected](7282): internal_command_event_match internal_command.opcode = FC27 opcode = fc27
06-18 09:06:15.853 I/bt_osi_thread(7282): run_thread: thread id 7332, thread name module_wrapper started
06-18 09:06:15.853 D/[email protected](7282): internal_command.bc called
internal_command.opcode doesn't match to the opcode received from bt controller. All events related to sco configuration will be handled by HCI. But HCI doesn't know anything about these commands and events (filter_incoming_event command complete event with no matching command in the log). Actually FC27 is HCI_VSC_WRITE_SLEEP_MODE. Seems that someone else sends this opcode to controller. I think that this can happens only after firmware configuration. We can try to postpone call of the initialize_complete_cb_ until sco configuration finish.

z3DD3r said:
This is very strange. Look at my logcat (LOS wit BT fix):
internal_command.opcode doesn't match to the opcode received from bt controller. All events related to sco configuration will be handled by HCI. But HCI doesn't know anything about these commands and events (filter_incoming_event command complete event with no matching command in the log). Actually FC27 is HCI_VSC_WRITE_SLEEP_MODE. Seems that someone else sends this opcode to controller. I think that this can happens only after firmware configuration. We can try to postpone call of the initialize_complete_cb_ until sco configuration finish.
Click to expand...
Click to collapse
Its probably because you sent the VSCs directly from libbt-vendor, rather than sending an opcode command from VendorInterface, which then sends VSCs, and thus the VendorInterface considers the last internal opcode(BT_VND_OP_LPM_SET_MODE in this case) saved, as the next opcode commands which are being received.
If these logs bug you so much, just edit small part of the bt_vendor_brcm.c and include named by you opcode command which points to the hw_config_continue method, then call it from the VendorInterface.
If you do this then you should partially revert your commit, and set the firmware configuration as it was before, but then again it doesn't matter where the I2S/PCM interface is configured, what matters most is that it is configured.

Sashko98 said:
Its probably because you sent the VSCs directly from libbt-vendor, rather than sending an opcode command from VendorInterface, which then sends VSCs, and thus the VendorInterface considers the last internal opcode(BT_VND_OP_LPM_SET_MODE in this case) saved, as the next opcode commands which are being received.
If these logs bug you so much, just edit small part of the bt_vendor_brcm.c and include named by you opcode command which points to the hw_config_continue method, then call it from the VendorInterface.
If you do this then you should partially revert your commit, and set the firmware configuration as it was before, but then again it doesn't matter where the I2S/PCM interface is configured, what matters most is that it is configured.
Click to expand...
Click to collapse
Seems that we a talking about different things. It really doesn't matter where the I2S/PCM interface is configured. It matters when!
Good news!
I've managed to improve initial solution!
Commit:
78d62ad58da101371822cee107f7759841d2744b
Changes:
No more memory leaks.
No more uncontrolled commands to bt chip. Each sent command receives callback and handles it appropriately.
Ability to configure codec configuration through the vnd config. We can use only i2spcm or wbs+i2spcm.
@razorloves, what do you think about it?
I can share a test build if anyone is interested.

z3DD3r said:
Seems that we a talking about different things. It really doesn't matter where the I2S/PCM interface is configured. It matters when!
Good news!
I've managed to improve initial solution!
Commit:
78d62ad58da101371822cee107f7759841d2744b
Changes:
No more memory leaks.
No more uncontrolled commands to bt chip. Each sent command receives callback and handles it appropriately.
Ability to configure codec configuration through the vnd config. We can use only i2spcm or wbs+i2spcm.
@razorloves, what do you think about it?
I can share a test build if anyone is interested.
Click to expand...
Click to collapse
Thank you very much Man @z3DD3r
You Rock :fingers-crossed: :highfive:

z3DD3r said:
Seems that we a talking about different things. It really doesn't matter where the I2S/PCM interface is configured. It matters when!
Good news!
I've managed to improve initial solution!
Commit:
78d62ad58da101371822cee107f7759841d2744b
Changes:
No more memory leaks.
No more uncontrolled commands to bt chip. Each sent command receives callback and handles it appropriately.
Ability to configure codec configuration through the vnd config. We can use only i2spcm or wbs+i2spcm.
@razorloves, what do you think about it?
I can share a test build if anyone is interested.
Click to expand...
Click to collapse
I will try to adapt this to the LG g4 and if that works I will kiss your feet , really .. It tried since months to get that working (we have the same chipset) and tested almost everything I could think of .. But you're way ahead of me.. Thanks for taking the time to explain everything and ofc for the fix
Sent from my OnePlus 6T using XDA Labs

Hi @steadfasterX,
This should work for all devices with broadcom bluetooth chip. At least i don't see any reasons not to work... Just get the latest code of the libbt and configure your vnd config.
I think i should rebase libbt to have only one commit with actual description...
---------- Post added at 08:17 PM ---------- Previous post was at 08:17 PM ----------
Hi @steadfasterX,
This should work for all devices with broadcom bluetooth chip. At least i don't see any reasons not to work... Just get the latest code of the libbt and configure your vnd config.
I think i should rebase libbt to have only one commit with actual description...

z3DD3r said:
Hi @steadfasterX,
This should work for all devices with broadcom bluetooth chip. At least i don't see any reasons not to work... Just get the latest code of the libbt and configure your vnd config.
I think i should rebase libbt to have only one commit with actual description...
---------- Post added at 08:17 PM ---------- Previous post was at 08:17 PM ----------
Hi @steadfasterX,
This should work for all devices with broadcom bluetooth chip. At least i don't see any reasons not to work... Just get the latest code of the libbt and configure your vnd config.
I think i should rebase libbt to have only one commit with actual description...
Click to expand...
Click to collapse
Yea I strongly believe it will work especially as we have the exact same chip model.
Would be nice if you rebase but if not then not .. I can test it tomorrow first so ..
Thanks again you have no idea how long the ppl are waiting for such a fix..
Sent from my OnePlus 6T using XDA Labs

@steadfasterX, @razorloves
Rebased:
broadcom libbt
hammerhead device tree

z3DD3r said:
@steadfasterX, @razorloves
Rebased:
broadcom libbt
hammerhead device tree
Click to expand...
Click to collapse
you are incredible @z3DD3r , @Sashko98 .. it really works.. I mean.. over 1 year no one was able to solve that f*** ! You're the saviour .. :highfive:
where the hell is your f*** donation addr @z3DD3r ??? :laugh: I am serious about that q
I recognized one little thing: one letter is not coming through in both directions: Z (german spoken like "zwei") or the C like in "niCe" or "intelligenCe". Its like it gets lost. I have tested with WBS active atm and will do some further tests with maybe clock rate etc. Just wanted to let you know. its still an awesome thing and when you speak out the character very loud it comes through btw.
UPDATE:
ok with or without preferred WBS makes no diff on that lost char issue
UPDATE2:
Log with WBS pref to FALSE (issue still there): https://paste.omnirom.org/view/28af9d55
(stopping audio server, starting it, incoming call, accept call, while talking log is silent)
.. and to clarify its hard to track that "lost char" issue. I am testing with 2 headsets, 1 connected to my main phone (OP6T) and the other to my G4. I mute always one of the both and then talking the little delay in transmitting the voice allows to hear that issue when you know it. so the impact of that here is not big I think but if you have any idea what to try let me know.
.-

z3DD3r said:
@steadfasterX, @razorloves
Rebased:
broadcom libbt
hammerhead device tree
Click to expand...
Click to collapse
This is unnecessary if you want to send HCI_VSC_ENABLE_WBS just route through it. We set the codecs manually anyway.
Code:
#if (BTHW_FW_EXTENDED_CONFIGURATION_ONLY_I2SPCM_CONFIG == FALSE)
hw_config_extended_set_SCO_codec(BTHW_FW_EXTENDED_CONFIGURATION_SCO_CODEC);
#else
hw_config_extended_sco_i2spcm_config(BTHW_FW_EXTENDED_CONFIGURATION_SCO_CODEC);
#endif // (BTHW_FW_EXTENDED_CONFIGURATION_ONLY_I2SPCM_CONFIG)
This could be re-worked
Code:
#if (BTHW_FW_EXTENDED_CONFIGURATION == FALSE)
static void hw_config_extended_start(void)
{
if (bt_vendor_cbacks)
{
bt_vendor_cbacks->fwcfg_cb(BT_VND_OP_RESULT_SUCCESS);
}
}
#else
static void hw_config_extended_finish(uint8_t result)
..........................
into
Code:
case HW_CFG_SET_BD_ADDR:
ALOGI("vendor lib fwcfg completed");
bt_vendor_cbacks->dealloc(p_buf);
#if (BTHW_FW_EXTENDED_CONFIGURATION == TRUE)
hw_config_extended_start();
#else
bt_vendor_cbacks->fwcfg_cb(BT_VND_OP_RESULT_SUCCESS);
#endif
Also since you figured out the callbacks, consider using your idea on the existing methods. No need for all this re-definitions.
The changes in the device tree are unnecessary
BTM_WBS_INCLUDED was removed since Oreo
BTIF_HF_WBS_PREFERRED was removed later on on Pie
steadfasterX said:
ok with or without preferred WBS makes no diff on that lost char issue
UPDATE2:
Log with WBS pref to FALSE (issue still there): https://paste.omnirom.org/view/28af9d55
(stopping audio server, starting it, incoming call, accept call, while talking log is silent)
.. and to clarify its hard to track that "lost char" issue. I am testing with 2 headsets, 1 connected to my main phone (OP6T) and the other to my G4. I mute always one of the both and then talking the little delay in transmitting the voice allows to hear that issue when you know it. so the impact of that here is not big I think but if you have any idea what to try let me know.
Click to expand...
Click to collapse
Try setting the BTHW_FW_EXTENDED_CONFIGURATION_SCO_CODEC as SCO_CODEC_MSBC, if that doesn't work maybe try this 540b42c

Sashko98 said:
Try setting the BTHW_FW_EXTENDED_CONFIGURATION_SCO_CODEC as SCO_CODEC_MSBC
Click to expand...
Click to collapse
thx dude..
already tried that - no change
I also tried setting the SCO rate to force 8K - no change
I will test that commit asap
@Sashko98 ok I tried that commit and this resulted in outgoing = distorted sound, incoming = silence
log: https://paste.omnirom.org/view/c7134f75
.-

steadfasterX said:
thx dude..
already tried that - no change
I also tried setting the SCO rate to force 8K - no change
I will test that commit asap
@Sashko98 ok I tried that commit and this resulted in outgoing = distorted sound, incoming = silence
log: https://paste.omnirom.org/view/c7134f75
Click to expand...
Click to collapse
Send your local vnd config just in case, perhaps there is something in there which effects everything. Other possibility is the mixer_paths or the audio_platform_info.
I see that you get good logs from the ACDB loader. if Nougat or stock rom didn't have such issue establish sco connection and look for line similar to this
Code:
D ACDB-LOADER: ACDB -> send_voice_cal, acdb_rx = 22, acdb_tx = 21,
acdb_rx = SND_DEVICE_OUT_BT_SCO <acdb_id>
acdb_tx = SND_DEVICE_IN_BT_SCO_MIC <acdb_id>
Perhaps something in the acdb mapping has changed. Check if on Nougat/stock rom different acdbs are being used for receiving and transmitting, and if by any change different acdbs are used, map them via the audio_platform_info

Mi 9 restarts by itself

Hey guys,
I have a problem with my mi 9 (128gb).
I was in MIUI 11.0.6 EEA and now on the Rom Pixel Experience from 2019/12/09
The problem is on both Roms, that the phone restarts suddenly without any warning or exception.
Maybe Up to 5 Times a day.
Theres no longer Uptime for me than 6 hours.
Then it crashes and reboots again.
The only information I have is out of the logcat below.
Looks Like it comes from magisk. But it also happened without magisk.
I am afraid, maybe its a Hardware problem :-/
12-11 20:15:38.068 2859 2859 E ActivityThread: Failed to find provider info for com.google.android.gsf.gservices
12-11 20:15:38.068 2859 2922 E ActivityThread: Failed to find provider info for com.google.android.gsf.gservices
12-11 20:15:38.069 2859 2859 E ActivityThread: Failed to find provider info for com.google.android.gsf.gservices
12-11 20:15:38.070 2859 2922 E ActivityThread: Failed to find provider info for com.google.android.gsf.gservices
12-11 20:15:38.070 2859 2859 E ActivityThread: Failed to find provider info for com.google.android.gsf.gservices
12-11 20:15:38.070 2859 2922 E ActivityThread: Failed to find provider info for com.google.android.gsf.gservices
12-11 20:15:38.071 2859 2859 E ActivityThread: Failed to find provider info for com.google.android.gsf.gservices
12-11 20:15:38.071 2859 2859 E ActivityThread: Failed to find provider info for com.google.android.gsf.gservices
12-11 20:15:38.071 2859 2922 E ActivityThread: Failed to find provider info for com.google.android.gsf.gservices
12-11 20:15:38.071 2859 2859 E ActivityThread: Failed to find provider info for com.google.android.gsf.gservices
12-11 20:15:38.072 2859 2922 E ActivityThread: Failed to find provider info for com.google.android.gsf.gservices
12-11 20:15:38.072 2859 2922 I chatty : uid=10090(com.google.android.gms) lowpool[0] identical 2 lines
12-11 20:15:38.073 2859 2922 E ActivityThread: Failed to find provider info for com.google.android.gsf.gservices
12-11 20:15:38.075 2859 2859 E ActivityThread: Failed to find provider info for com.google.android.gsf.gservices
12-11 20:15:38.076 2859 2922 E ActivityThread: Failed to find provider info for com.google.android.gsf.gservices
12-11 20:15:38.077 2859 2922 E ActivityThread: Failed to find provider info for com.google.android.gsf.gservices
12-11 20:15:38.079 2859 2859 E ActivityThread: Failed to find provider info for com.google.android.gsf.gservices
12-11 20:15:38.083 2859 2859 E ActivityThread: Failed to find provider info for com.google.android.gsf.gservices
12-11 20:15:38.086 2859 2927 E ActivityThread: Failed to find provider info for com.google.android.gsf.gservices
12-11 20:15:38.095 2859 2931 E ActivityThread: Failed to find provider info for com.google.android.gsf.gservices
--------- beginning of crash
12-11 20:15:38.104 2887 2929 E AndroidRuntime: FATAL EXCEPTION: pool-3-thread-1
12-11 20:15:38.104 2887 2929 E AndroidRuntime: Process: com.topjohnwu.magisk, PID: 2887
12-11 20:15:38.104 2887 2929 E AndroidRuntime: android.database.sqlite.SQLiteCantOpenDatabaseException: unknown error (code 14 SQLITE_CANTOPEN): Could not open database
12-11 20:15:38.104 2887 2929 E AndroidRuntime: at android.database.sqlite.SQLiteConnection.nativeOpen(Native Method)
12-11 20:15:38.104 2887 2929 E AndroidRuntime: at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java:215)
12-11 20:15:38.104 2887 2929 E AndroidRuntime: at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java:197)
12-11 20:15:38.104 2887 2929 E AndroidRuntime: at android.database.sqlite.SQLiteConnectionPool.openConnectionLocked(SQLiteConnectionPool.java:505)
12-11 20:15:38.104 2887 2929 E AndroidRuntime: at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java:206)
12-11 20:15:38.104 2887 2929 E AndroidRuntime: at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java:198)
12-11 20:15:38.104 2887 2929 E AndroidRuntime: at android.database.sqlite.SQLiteDatabase.openInner(SQLiteDatabase.java:915)
12-11 20:15:38.104 2887 2929 E AndroidRuntime: at android.database.sqlite.SQLiteDatabase.open(SQLiteDatabase.java:895)
12-11 20:15:38.104 2887 2929 E AndroidRuntime: at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:759)
12-11 20:15:38.104 2887 2929 E AndroidRuntime: at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:748)
12-11 20:15:38.104 2887 2929 E AndroidRuntime: at android.database.sqlite.SQLiteOpenHelper.getDatabaseLocked(SQLiteOpenHelper.java:374)
12-11 20:15:38.104 2887 2929 E AndroidRuntime: at android.database.sqlite.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java:317)
12-11 20:15:38.104 2887 2929 E AndroidRuntime: at a.jw.a(Unknown Source:4)
12-11 20:15:38.104 2887 2929 E AndroidRuntime: at a.kw.a(Unknown Source:2)
12-11 20:15:38.104 2887 2929 E AndroidRuntime: at a.bv.c(Unknown Source:5)
12-11 20:15:38.104 2887 2929 E AndroidRuntime: at androidx.work.impl.utils.ForceStopRunnable.run3)
12-11 20:15:38.104 2887 2929 E AndroidRuntime: at a.r40.run(Unknown Source:2)
12-11 20:15:38.104 2887 2929 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
12-11 20:15:38.104 2887 2929 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
12-11 20:15:38.104 2887 2929 E AndroidRuntime: at java.lang.Thread.run(Thread.java:919)
12-11 20:15:38.107 1341 2935 I DropBoxManagerService: add tag=data_app_crash isTagEnabled=true flags=0x2
12-11 20:15:38.110 2535 2535 E ActivityThread: Failed to find provider info for com.google.android.gsf.gservices
12-11 20:15:38.110 2535 2535 E ActivityThread: Failed to find provider info for com.google.android.gsf.gservices
12-11 20:15:38.154 1341 1787 I ActivityManager: Process com.topjohnwu.magisk (pid 2887) has died: fore RCVR
12-11 20:15:38.157 1341 1787 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
12-11 20:15:38.164 2859 2931 E ActivityThread: Failed to find provider info for com.google.android.gsf.gservices
12-11 20:15:38.423 2859 2931 I chatty : uid=10090(com.google.android.gms) identical 14 lines
12-11 20:15:38.423 2859 2931 E ActivityThread: Failed to find provider info for com.google.android.gsf.gservices
12-11 20:15:38.467 2859 2931 I SystemConfig: Adding association: com.google.android.as <- com.android.providers.contacts
12-11 20:15:38.467 2859 2931 I SystemConfig: Adding association: com.google.android.as <- com.android.providers.media
12-11 20:15:38.467 2859 2931 I SystemConfig: Adding association: com.google.android.as <- com.android.providers.telephony
12-11 20:15:38.467 2859 2931 I SystemConfig: Adding association: com.google.android.as <- com.android.systemui
12-11 20:15:38.467 2859 2931 I SystemConfig: Adding association: com.google.android.as <- com.google.android.gms
12-11 20:15:38.467 2859 2931 I SystemConfig: Adding association: com.google.android.as <- com.google.android.gsf
12-11 20:15:38.481 2859 2931 W SystemConfig: No directory /product_services/etc/sysconfig, skipping
12-11 20:15:38.481 2859 2931 W SystemConfig: No directory /product_services/etc/permissions, skipping
12-11 20:15:38.655 2859 2931 E ActivityThread: Failed to find provider info for com.google.android.gsf.gservices
12-11 20:15:38.656 2859 2931 I chatty : uid=10090(com.google.android.gms) identical 1 line
12-11 20:15:38.667 2859 2931 E ActivityThread: Failed to find provider info for com.google.android.gsf.gservices
12-11 20:15:38.670 2859 2937 E ActivityThread: Failed to find provider info for com.google.android.gsf.gservices
12-11 20:15:38.670 2859 2937 E ActivityThread: Failed to find provider info for com.google.android.gsf.gservices
12-11 20:15:38.670 2535 2561 E ActivityThread: Failed to find provider info for com.google.android.gsf.gservices
12-11 20:15:38.671 2535 2561 E ActivityThread: Failed to find provider info for com.google.android.gsf.gservices
12-11 20:15:38.695 2859 2931 E ActivityThread: Failed to find provider info for com.google.android.gsf.gservices
12-11 20:15:38.702 1341 2114 W ActivityManager: Unable to start service Intent { flg=0x9000010 cmp=com.google.android.gms/.gcm.nts.SchedulerService (has extras) } U=0: not found
12-11 20:15:38.713 2535 2535 E ActivityThread: Failed to find provider info for com.google.android.gsf.gservices
12-11 20:15:38.807 2535 2535 I chatty : uid=10090 com.google.android.gms.persistent identical 67 lines
12-11 20:15:38.808 2535 2535 E ActivityThread: Failed to find provider info for com.google.android.gsf.gservices
12-11 20:15:38.809 2535 2798 E ActivityThread: Failed to find provider info for com.google.android.gsf.gservices
12-11 20:15:38.811 2535 2798 I chatty : uid=10090 com.google.android.gms.persistent identical 5 lines
12-11 20:15:38.811 2535 2798 E ActivityThread: Failed to find provider info for com.google.android.gsf.gservices
12-11 20:15:38.813 2535 2946 E ActivityThread: Failed to find provider info for com.google.android.gsf.gservices
12-11 20:15:38.814 2535 2946 I chatty : uid=10090 com.google.android.gms.persistent identical 3 lines
12-11 20:15:38.814 2535 2946 E ActivityThread: Failed to find provider info for com.google.android.gsf.gservices
12-11 20:15:39.040 2859 2937 E ActivityThread: Failed to find provider info for com.google.android.gsf.gservices
12-11 20:15:39.040 2859 2937 E ActivityThread: Failed to find provider info for com.google.android.gsf.gservices
12-11 20:15:39.056 1923 2653 E ActivityThread: Failed to find provider info for call_log
12-11 20:15:39.074 1923 2653 I chatty : uid=1002(bluetooth) e.StateMachines identical 1 line
12-11 20:15:39.096 1923 2653 E ActivityThread: Failed to find provider info for call_log
12-11 20:15:39.278 1341 1791 D ConnectivityService: releasing NetworkRequest [ TRACK_DEFAULT id=15, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 1001] ] (release request)
12-11 20:15:39.295 1923 2653 E ActivityThread: Failed to find provider info for com.android.contacts
12-11 20:15:39.402 1341 1370 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
12-11 20:15:39.889 1923 2954 E ActivityThread: Failed to find provider info for com.android.contacts
12-11 20:15:40.712 1341 1341 I Telecom : WiredHeadsetManager: ACTION_HEADSET_PLUG event, plugged in: false, : [email protected]
12-11 20:15:41.272 1341 1341 I Telecom : WiredHeadsetManager: ACTION_HEADSET_PLUG event, plugged in: false, : [email protected]
12-11 20:15:41.272 1341 1341 I Telecom : WiredHeadsetManager: ACTION_HEADSET_PLUG event, plugged in: false, : [email protected]
12-11 20:15:41.779 1341 2114 W CameraService_proxy: Could not notify cameraserver, camera service not available.
12-11 20:15:41.779 1341 2114 I CameraService_proxy: Could not notify camera service of user switch, retrying...
12-11 20:15:43.355 1341 1754 E NetworkPolicy: Missing subscriberId for subId 1
12-11 20:15:43.356 1341 1370 I DropBoxManagerService: add tag=system_server_wtf isTagEnabled=true flags=0x2
12-11 20:15:43.381 2219 2219 I TelecomFramework: : onSubscriptionsChanged - update accounts
12-11 20:15:43.381 2219 2219 I TelecomFramework: PstnIncomingCallNotifier: Unregistering: Handler (com.qualcomm.qti.internal.telephony.QtiGsmCdmaPhone) {cda9da2}
12-11 20:15:43.381 2219 2219 I TelecomFramework: TelecomAccountRegistry: setupAccounts: Found 2 phones. Attempting to register.
12-11 20:15:43.381 2219 2219 I TelecomFramework: TelecomAccountRegistry: setupAccounts: Phone with subscription id 1
12-11 20:15:43.391 1341 1787 I Telecom : PhoneAccountRegistrar: New phone account registered: [[ ] PhoneAccount: ComponentInfo{com.android.phone/com.android.services.telephony.TelephonyConnectionService}, ***, UserHandle{0} Capabilities: SuppVideo CallProvider MultiUser PlaceEmerg SimSub Audio Routes: BESW Schemes: tel voicemail Extras: Bundle[{android.telecom.extra.SUPPORTS_VIDEO_CALLING_FALLBACK=true, android.telecom.extra.SORT_ORDER=0}] GroupId: ***]: [email protected]
12-11 20:15:43.392 1341 1787 I Telecom : CallsManager: Sending phone-account ComponentInfo{com.android.phone/com.android.services.telephony.TelephonyConnectionService}, ***, UserHandle{0} registered intent as user: [email protected]
12-11 20:15:43.393 1341 1787 I Telecom : CallsManager: Sending phone-account registered intent to default dialer: [email protected]
12-11 20:15:43.393 2219 2219 I TelecomFramework: AccountEntry: Registered phoneAccount: [[ ] PhoneAccount: ComponentInfo{com.android.phone/com.android.services.telephony.TelephonyConnectionService}, ***, UserHandle{0} Capabilities: SuppVideo CallProvider MultiUser PlaceEmerg SimSub Audio Routes: BESW Schemes: tel voicemail Extras: Bundle[{android.telecom.extra.SUPPORTS_VIDEO_CALLING_FALLBACK=true, android.telecom.extra.SORT_ORDER=0}] GroupId: ***] with handle: ComponentInfo{com.android.phone/com.android.services.telephony.TelephonyConnectionService}, ***, UserHandle{0}
12-11 20:15:43.393 2219 2219 I TelecomFramework: PstnIncomingCallNotifier: Registering: Handler (com.qualcomm.qti.internal.telephony.QtiGsmCdmaPhone) {cda9da2}
12-11 20:15:43.396 2219 2219 I TelecomFramework: TelecomAccountRegistry: setupAccounts: Phone with subscription id -1
12-11 20:15:43.396 2219 2219 I TelecomFramework: TelecomAccountRegistry: Unregistering phone account ComponentInfo{com.android.phone/com.android.services.telephony.TelephonyConnectionService}, ***, UserHandle{0}.
12-11 20:15:43.398 1341 1787 I Telecom : CallsManager: Sending phone-account ComponentInfo{com.android.phone/com.android.services.telephony.TelephonyConnectionService}, ***, UserHandle{0} unregistered intent as user: [email protected]
12-11 20:15:43.398 1341 1787 I Telecom : CallsManager: Sending phone-account unregistered intent to default dialer: [email protected]
12-11 20:15:43.415 1341 1754 E NetworkPolicy: Missing subscriberId for subId 1
12-11 20:15:43.416 1341 1370 I DropBoxManagerService: add tag=system_server_wtf isTagEnabled=true flags=0x2
12-11 20:15:43.430 1341 1754 E NetworkPolicy: Missing subscriberId for subId 1
12-11 20:15:43.440 1341 1787 I Telecom : PhoneAccountRegistrar: setUserSelectedOutgoingPhoneAccount: ComponentInfo{com.android.phone/com.android.services.telephony.TelephonyConnectionService}, ***, UserHandle{0}: [email protected]
12-11 20:15:43.440 1341 1787 I Telecom : PhoneAccountRegistrar: setUserSelectedOutgoingPhoneAccount: no change to voice sub: [email protected]
12-11 20:15:43.442 2219 2219 D MccTable: updateMccMncConfiguration mccmnc='
12-11 20:15:43.445 1341 1754 E NetworkPolicy: Missing subscriberId for subId 1
12-11 20:15:43.452 1341 1754 E NetworkPolicy: Missing subscriberId for subId 1
12-11 20:15:43.463 2219 2219 I TelecomFramework: PstnPhoneCapabilitiesNotifier: handleVideoCapabilitesChanged. Video capability - false
12-11 20:15:43.483 1341 2114 I Telecom : PhoneAccountRegistrar: Modify account: [ComponentInfo{com.android.phone/com.android.services.telephony.TelephonyConnectionService}, ***, UserHandle{0}]: [email protected]
12-11 20:15:43.484 1341 2114 I Telecom : CallsManager: handlePhoneAccountChanged: phoneAccount=[[X] PhoneAccount: ComponentInfo{com.android.phone/com.android.services.telephony.TelephonyConnectionService}, ***, UserHandle{0} Capabilities: SuppVideo CallProvider MultiUser PlaceEmerg SimSub Audio Routes: BESW Schemes: tel voicemail Extras: Bundle[{android.telecom.extra.SUPPORTS_VIDEO_CALLING_FALLBACK=true, android.telecom.extra.SORT_ORDER=0}] GroupId: ***]: [email protected]
12-11 20:15:43.486 1341 1371 I ActivityManager: Start proc 3040:com.google.android.dialer/u0a100 for broadcast {com.google.android.dialer/com.android.dialer.app.calllog.LegacyVoicemailNotificationReceiver}
12-11 20:15:43.504 1341 1754 E NetworkPolicy: Missing subscriberId for subId 1
12-11 20:15:43.517 2219 2219 I TelecomFramework: : onSubscriptionsChanged - update accounts
12-11 20:15:43.517 2219 2219 I TelecomFramework: PstnIncomingCallNotifier: Unregistering: Handler (com.qualcomm.qti.internal.telephony.QtiGsmCdmaPhone) {cda9da2}
12-11 20:15:43.518 2219 2219 I TelecomFramework: TelecomAccountRegistry: setupAccounts: Found 2 phones. Attempting to register.
12-11 20:15:43.518 2219 2219 I TelecomFramework: TelecomAccountRegistry: setupAccounts: Phone with subscription id 1
12-11 20:15:43.526 1341 1787 I Telecom : PhoneAccountRegistrar: Modify account: [ComponentInfo{com.android.phone/com.android.services.telephony.TelephonyConnectionService}, ***, UserHandle{0}]: [email protected]
12-11 20:15:43.527 1341 1787 I Telecom : CallsManager: handlePhoneAccountChanged: phoneAccount=[[X] PhoneAccount: ComponentInfo{com.android.phone/com.android.services.telephony.TelephonyConnectionService}, ***, UserHandle{0} Capabilities: SuppVideo CallProvider MultiUser PlaceEmerg SimSub Audio Routes: BESW Schemes: tel voicemail Extras: Bundle[{android.telecom.extra.SUPPORTS_VIDEO_CALLING_FALLBACK=true, android.telecom.extra.SORT_ORDER=0}] GroupId: ***]: [email protected]
12-11 20:15:43.527 2219 2219 I TelecomFramework: AccountEntry: Registered phoneAccount: [[ ] PhoneAccount: ComponentInfo{com.android.phone/com.android.services.telephony.TelephonyConnectionService}, ***, UserHandle{0} Capabilities: SuppVideo CallProvider MultiUser PlaceEmerg SimSub Audio Routes: BESW Schemes: tel voicemail Extras: Bundle[{android.telecom.extra.SUPPORTS_VIDEO_CALLING_FALLBACK=true, android.telecom.extra.SORT_ORDER=0}] GroupId: ***] with handle: ComponentInfo{com.android.phone/com.android.services.telephony.TelephonyConnectionService}, ***, UserHandle{0}
12-11 20:15:43.527 2219 2219 I TelecomFramework: PstnIncomingCallNotifier: Registering: Handler (com.qualcomm.qti.internal.telephony.QtiGsmCdmaPhone) {cda9da2}
12-11 20:15:43.529 2219 2219 I TelecomFramework: TelecomAccountRegistry: setupAccounts: Phone with subscription id -1
12-11 20:15:43.538 2219 2219 I TelecomFramework: : onSubscriptionsChanged - update accounts
12-11 20:15:43.538 2219 2219 I TelecomFramework: PstnIncomingCallNotifier: Unregistering: Handler (com.qualcomm.qti.internal.telephony.QtiGsmCdmaPhone) {cda9da2}
12-11 20:15:43.539 2219 2219 I TelecomFramework: TelecomAccountRegistry: setupAccounts: Found 2 phones. Attempting to register.
12-11 20:15:43.539 2219 2219 I TelecomFramework: TelecomAccountRegistry: setupAccounts: Phone with subscription id 1
12-11 20:15:43.546 1341 1787 I Telecom : PhoneAccountRegistrar: Modify account: [ComponentInfo{com.android.phone/com.android.services.telephony.TelephonyConnectionService}, ***, UserHandle{0}]: [email protected]
12-11 20:15:43.547 1341 1787 I Telecom : CallsManager: handlePhoneAccountChanged: phoneAccount=[[X] PhoneAccount: ComponentInfo{com.android.phone/com.android.services.telephony.TelephonyConnectionService}, ***, UserHandle{0} Capabilities: SuppVideo CallProvider MultiUser PlaceEmerg SimSub Audio Routes: BESW Schemes: tel voicemail Extras: Bundle[{android.telecom.extra.SUPPORTS_VIDEO_CALLING_FALLBACK=true, android.telecom.extra.SORT_ORDER=0}] GroupId: ***]: [email protected]
12-11 20:15:43.547 2219 2219 I TelecomFramework: AccountEntry: Registered phoneAccount: [[ ] PhoneAccount: ComponentInfo{com.android.phone/com.android.services.telephony.TelephonyConnectionService}, ***, UserHandle{0} Capabilities: SuppVideo CallProvider MultiUser PlaceEmerg SimSub Audio Routes: BESW Schemes: tel voicemail Extras: Bundle[{android.telecom.extra.SUPPORTS_VIDEO_CALLING_FALLBACK=true, android.telecom.extra.SORT_ORDER=0}] GroupId: ***] with handle: ComponentInfo{com.
Click to expand...
Click to collapse
Any idea and a solution for me?
Thanks a lot
greetz

I disabled kernel panic in lspeed.

onolox said:
I disabled kernel panic in lspeed.
Click to expand...
Click to collapse
Hi,
can you give me more details please?
Where can I do that?
Thanks

Reglash the stock MIUI ROM using the global ROM on xiaomi site

andrew2401 said:
Reglash the stock MIUI ROM using the global ROM on xiaomi site
Click to expand...
Click to collapse
I tried to flash with the Xiaomi Flash Tool the EEA 11.0.5 and 11.0.6 (.tgz)
These steps didnt make it better, still reboots in different situations.
Now I am since 2 days on the Global Rom 11.0.3 , without twrp and magisk. Bootloader still unlocked.
Last night there was a reboot once :crying:
But its also the best one of my testings.
I'll keep my eyes on it... Maybe theres a simple reason for such crashes

abocksberger said:
I tried to flash with the Xiaomi Flash Tool the EEA 11.0.5 and 11.0.6 (.tgz)
These steps didnt make it better, still reboots in different situations.
Now I am since 2 days on the Global Rom 11.0.3 , without twrp and magisk. Bootloader still unlocked.
Last night there was a reboot once :crying:
But its also the best one of my testings.
I'll keep my eyes on it... Maybe theres a simple reason for such crashes
Click to expand...
Click to collapse
I had noticed such problem couple of times, don't remember with what ROM. But i flash a lot and this problem was gone. Recently i have flashed global fastboot ROM 11.0.3.0 to flash all new MIUI 11 images and clean flashed xiaomi eu 9.11.28, everything works very well, except i don't like xiaomi auto brightness and using auto brightness fix from here.

Hey Guys,
next round for me, now on Xiaomi.eu 9.12.12
Last night my phone restarted again.
Here's the reason:
-------- beginning of crash
12-17 13:03:53.969 1093 1093 F libc : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 1093 (init), pid 1093 (init)
12-17 13:03:53.994 1093 1093 F libc : crash_dump helper failed to exec
Click to expand...
Click to collapse
That Error was until now in every ROM I tried.
Maybe I should not restore any of my backups out of Google Drive , when recovering all my data!?

Try a factory reset in TWRP if you're not already. I had this issue when dirty flashing between ROMs. Yes, you may not want to, but....

ToneLa said:
Try a factory reset in TWRP if you're not already. I had this issue when dirty flashing between ROMs. Yes, you may not want to, but....
Click to expand...
Click to collapse
Thaks for your idea.
I´ve formatted the whole data, did a wipe (reset to default). Even wiped all the partitions there are.
I mean everything should be fine, when flash a .tgz File with the Mi Flash Tool, or not?
But it´s not fine for me, hangs and restarts still without a reason (can´t see a reason)

Hi, I have a Mi 9 and the random reboot problem started after the first MIUI 11 update. The phone was untouched and locked at that time and restarts happened every 30 hours of use in average without a reason.
At first, I factory cleanup my phone... but I had the same problem, then I unlocked my phone and installed xiaomi.eu but the same problem again.
Now, I don't know what to do, maybe I must buy a new phone (I dont have technical service in my country) but not Xiaomi for sure, I think it's a disposable device, a rubbish.
My son has the same phone model and no reboot problems.
Hope it helps.

Yeah, you're right.
My Phone started to do these things since the first MIUI 11 Update. I think it was 11.0.2 or sth. like that.
Actually I have flashed via twrp the xiaomi.eu Rom MIUI 11.0.5 stable.
Additionaly i removed the Google account from the Phone to be free and make sure, that the problems came not from there.
Is it possible, that googles Factory Reset Protection (FRP) is a reason for all that trouble?

abocksberger said:
Thaks for your idea.
I´ve formatted the whole data, did a wipe (reset to default). Even wiped all the partitions there are.
I mean everything should be fine, when flash a .tgz File with the Mi Flash Tool, or not?
But it´s not fine for me, hangs and restarts still without a reason (can´t see a reason)
Click to expand...
Click to collapse
Oh, well done for trying it but sorry to here this did not solve it!
I think you can rule out the ROM and the process you use, then.
The last few posts seem to think it is MIUI11 itself - this would make sense, you're looking for something in common.
I don't see it being hardware, but certainly not impossible. Have you dropped or knocked it lately? I wonder if the battery is connected OK (of course, it is likely soldered in place, so, less likely)

ToneLa said:
Oh, well done for trying it but sorry to here this did not solve it!
I think you can rule out the ROM and the process you use, then.
The last few posts seem to think it is MIUI11 itself - this would make sense, you're looking for something in common.
I don't see it being hardware, but certainly not impossible. Have you dropped or knocked it lately? I wonder if the battery is connected OK (of course, it is likely soldered in place, so, less likely)
Click to expand...
Click to collapse
Thanks for your help so far.
My last setup (yesterday) was:
- twrp 3.3.1.0
- xiaomi.eu Rom 11.0.5
- no restore, no google sing in
- no simcard
- wifi and bluetooth active
- hotspot via wifi after 15h uptime at once
Then, after about 16 hours came a random reboot again. A hour later one more.
I noticed that a clean boot (restarting oder switching the phone manually off and in) is the best way to be reach the best uptime (i know, 16hours is a joke).
Otherwise its possible, that the phone restarts 2 times in 5 minutes.
My next and last try will be:
- flash a global MIUI 10 Rom via Mi flash Tool
- Check it 24hours
- flash it again with this Rom and lock the bootloader

abocksberger said:
Thanks for your help so far.
My last setup (yesterday) was:
- twrp 3.3.1.0
- xiaomi.eu Rom 11.0.5
- no restore, no google sing in
- no simcard
- wifi and bluetooth active
- hotspot via wifi after 15h uptime at once
Then, after about 16 hours came a random reboot again. A hour later one more.
I noticed that a clean boot (restarting oder switching the phone manually off and in) is the best way to be reach the best uptime (i know, 16hours is a joke).
Otherwise its possible, that the phone restarts 2 times in 5 minutes.
My next and last try will be:
- flash a global MIUI 10 Rom via Mi flash Tool
- Check it 24hours
- flash it again with this Rom and lock the bootloader
Click to expand...
Click to collapse
Please tell us if the experiment works, thank you very much!

dstilman said:
Please tell us if the experiment works, thank you very much!
Click to expand...
Click to collapse
sure, no problem.
Now I am on the global MIUI 10.2.14 since 2,5 hours.
I skipped every Connection and Account configuration, so the phone had no connect to any other device or the internet.
Before my flashing with the Mi Flash Tool I have formatted all partitions and wiped all the data.
Btw: The Mi Flash Tool ends for me allways with an Error at the end. But the phone restarts well and everythings works so far.
Hope this is Just a Bug in the MiFlash Tool.
I already read sth. like this in other Threads.
Would be great, if this is the fix to go.
I'll keep you up to date.

At least in case you flashed a fastboot ROM this error is to be expected. Doesn't mean something has gone wrong probably rather a little bug in the flash tool.
Cheers
Toscha

Hi,
I have good news, I installed the last beta version of xiaomi.eu and my cellphone is working better, 36 hours without reboots.
Version 10 is working better for you?.
Thanks for your feedback!
Pd: 37 hours and reboot again..., this device it's a joke... Garbage

dstilman said:
Hi,
I have good news, I installed the last beta version of xiaomi.eu and my cellphone is working better, 36 hours without reboots.
Version 10 is working better for you?.
Thanks for your feedback!
Pd: 37 hours and reboot again..., this device it's a joke... Garbage
Click to expand...
Click to collapse
Sorry, I had no time the last days to give you a response.
But now I have solved it!
Edit: Its not solved! - 20191228
Very strange, but it works.
No reboot since 3 days!
The steps to win the fight:
- flash an official Android 9 ROM (e.g. MIUI 10.2.14 global) with the Mi Flash Tool!!!
- update to MIUI 11.0.3 with the internal updater
I'm wondering about the reasons, but it seems to work. There must be something special and have a difference, if you just flash a ROM with Android 10.
Looks like its not clean enough.
For my unterstanding its fatal to be on Android 9 with magisk. That is disturbung the system while updating to MIUI 11.0.x.
Hope for now, that i wont have trouble when going to twrp and magisk again with MIUI 11.0.3
Good luck, would be nice to hear your result.
Greetz

In my case when the phone reboot I see a popup that mean " find my phone was restart unexpected" or similar. I disabile find my phone but nothing. This Is the cause of this random reboot? Sorry for my english.

abocksberger said:
Sorry, I had no time the last days to give you a response.
But now I have solved it!
Very strange, but it works.
No reboot since 3 days!
The steps to win the fight:
- flash an official Android 9 ROM (e.g. MIUI 10.2.14 global) with the Mi Flash Tool!!!
- update to MIUI 11.0.3 with the internal updater
I'm wondering about the reasons, but it seems to work. There must be something special and have a difference, if you just flash a ROM with Android 10.
Looks like its not clean enough.
For my unterstanding its fatal to be on Android 9 with magisk. That is disturbung the system while updating to MIUI 11.0.x.
Hope for now, that i wont have trouble when going to twrp and magisk again with MIUI 11.0.3
Good luck, would be nice to hear your result.
Greetz
Click to expand...
Click to collapse
Great to know!!, I'm very glad that you solved the problem!. Cheers!
---------- Post added at 09:51 PM ---------- Previous post was at 09:48 PM ----------
alessio81pa said:
In my case when the phone reboot I see a popup that mean " find my phone was restart unexpected" or similar. I disabile find my phone but nothing. This Is the cause of this random reboot? Sorry for my english.
Click to expand...
Click to collapse
I have exactly the same problem, so... Is not a hardware issue, the software is the problem....