Bluetooth issue ("Bluetooth app keeps force closing") - Huawei P10 Lite Questions & Answers

This issue came up after Dirty Flashing CypherOS (a month ago), but still persist today with PixysOS: both the ROMs haven't any Bluetooth bugs in the source code.
I think that this could be caused by the kernel, bit since I'm not so expert in the matter I don't want to flash it before knowing what it really is.
Any idea for a solution? (Attacched logs)
Thanks in advance

Related

Official CyanogenMod for Moto X Play

When Moto X Play is getting official CyanogenMod 13? Any updates?
Nitish247 said:
When Moto X Play is getting official CyanogenMod 13? Any updates?
Click to expand...
Click to collapse
Probably never. Does it matter? No, not at all. What is better about an official version compared to the unofficial? Nothing at all.
But why? Any specific reason? All Moto phones till date have official CM.
It's my understanding cm13 will turn official some day.
Nitish247 said:
But why? Any specific reason? All Moto phones till date have official CM.
Click to expand...
Click to collapse
If you are following the cm13 thread then you would know that squid has told that he would push for the cm13 build to become official but there is no estimated time.
Sent from my XT1562 using Tapatalk
It's a matter of fixing bugs. My intention has always been to make CM13 official once it is ready. There are three bugs blocking this:
Use of WiFi assisted location causes soft reboots if you don't add additional bounds checking. I am not sure if this bounds checking should really be there or if it is a symptom of some other problem.
A mysterious issue with the new camera drivers is causing memory corruption in the audio HAL. I'm not sure of the cause (other than the crash only happening when liboemcamera is updated to the Marshmallow version). I have a crude hack to work around this, but it is not suitable for merging into official CM. This will be tricky to debug and fix properly.
The RIL needs fixing on XT1562. I don't have an XT1562, so that makes it more difficult for me to troubleshoot, but @scritch007 will be looking into this in the coming days.
squid2 said:
It's a matter of fixing bugs. My intention has always been to make CM13 official once it is ready. There are three bugs blocking this:
Use of WiFi assisted location causes soft reboots if you don't add additional bounds checking. I am not sure if this bounds checking should really be there or if it is a symptom of some other problem.
A mysterious issue with the new camera drivers is causing memory corruption in the audio HAL. I'm not sure of the cause (other than the crash only happening when liboemcamera is updated to the Marshmallow version). I have a crude hack to work around this, but it is not suitable for merging into official CM. This will be tricky to debug and fix properly.
The RIL needs fixing on XT1562. I don't have an XT1562, so that makes it more difficult for me to troubleshoot, but @scritch007 will be looking into this in the coming days.
Click to expand...
Click to collapse
Great news. Laud your hard work have a great year ahead squid2
Sent from my XT1563 using Tapatalk
squid2 said:
It's a matter of fixing bugs. My intention has always been to make CM13 official once it is ready. There are three bugs blocking this:
Use of WiFi assisted location causes soft reboots if you don't add additional bounds checking. I am not sure if this bounds checking should really be there or if it is a symptom of some other problem.
A mysterious issue with the new camera drivers is causing memory corruption in the audio HAL. I'm not sure of the cause (other than the crash only happening when liboemcamera is updated to the Marshmallow version). I have a crude hack to work around this, but it is not suitable for merging into official CM. This will be tricky to debug and fix properly.
The RIL needs fixing on XT1562. I don't have an XT1562, so that makes it more difficult for me to troubleshoot, but @scritch007 will be looking into this in the coming days.
Click to expand...
Click to collapse
Thanks! Thats' awesome! :good:
We expect lux on official CyanogenMod list soon
squid2 said:
It's a matter of fixing bugs. My intention has always been to make CM13 official once it is ready. There are three bugs blocking this:
Use of WiFi assisted location causes soft reboots if you don't add additional bounds checking. I am not sure if this bounds checking should really be there or if it is a symptom of some other problem.
A mysterious issue with the new camera drivers is causing memory corruption in the audio HAL. I'm not sure of the cause (other than the crash only happening when liboemcamera is updated to the Marshmallow version). I have a crude hack to work around this, but it is not suitable for merging into official CM. This will be tricky to debug and fix properly.
The RIL needs fixing on XT1562. I don't have an XT1562, so that makes it more difficult for me to troubleshoot, but @scritch007 will be looking into this in the coming days.
Click to expand...
Click to collapse
I tried the version from the 25th of December, and I don't have any issue with it (I own a dual sim xt1562) and only have one sim inserted, but just after the boot I was prompted for the pin code. So I won't be of any help...
I'm running the 24.11.18.lux_retasia_ds.retasiaall.en.03 retfr version as my main version, so all my partitions were updated to 6.0

[ROM][PORT]Full Advance 5.1.1

Port Full Advance 5.1.1
​Samsung Galaxy Captivate
Full Advance is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. Full Advance does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
* Submitting bug reports on unofficial builds is the leading
* cause of male impotence.
*/
Installation:
Coming from 5.1.1 or less ROMS
Download Full Advance-XXXXXXXX.zip to your phone
Boot into Recovery
Wipe all your data (System/Data/Dalvik Cache)
(optional, recommed for the best performnce)-> Wipe your data with fs2f <-
Flash Full Advance-XXXXXXXX.zip from your phone
(Optional)Flash Open Apps.zip from your phone
Reboot
Features
Calling Delay Reduced
Highly optimised ROM
Stable
Fastest ever and Clean
New Camera,Audiofx,etc....
Some Stuff Has Been Removed
Completly AOSP
Download
ROM
Credits to
humberos
althafvly
Thanhtho96
Important Note
Im not own this device so some one test and feedback about the rom is every thing works well or not
RESERVED!!!
I will test this in 1-2 days and let you know if it works
Edit 1: Rom boots and everything seems to work fine.
ChriZz12 said:
I will test this in 1-2 days and let you know if it works
Edit 1: Rom boots and everything seems to work fine.
Click to expand...
Click to collapse
How about the performance? any lags delays something?
This ROM works pretty well. Faster and cleaner than other. But GPS seems to be broken. Also I had troubles installing open-gapps (play services errors appeared). Only clean install ROM and gapps immidiately after that worked out. But enabling location tracking leads to force-closing google services. I remember there was a difference in gps hardware between i9000 and i897.
Thanks for the ROM though. Looking forward a gps fix.
I try port android 6.0 for captivate and bro can test?
lorendroll said:
This ROM works pretty well. Faster and cleaner than other. But GPS seems to be broken. Also I had troubles installing open-gapps (play services errors appeared). Only clean install ROM and gapps immidiately after that worked out. But enabling location tracking leads to force-closing google services. I remember there was a difference in gps hardware between i9000 and i897.
Thanks for the ROM though. Looking forward a gps fix.
Click to expand...
Click to collapse
oh yes i forgot to make change that. Thanks for notifying this to me. For making gps to work try to replace that file from your lollipop version roms to this and try flashing
i have been using it for several hours and i must say that is very stable and works better than other roms ive tried. its not crazy fast, but its good so far. havnt seen any force close. i havent tested all but su far great job. it takes its time to do its stuff but, im mean, its lollipop on a 6 year old hardware.
thanks for the rom. i was searching for something stable. ill keep testing and reporting.
Super !! Fantastic !!
This, by far, is the best ROM for Captivate. I had to rejuvenate my Captivate as my 6+ was IMPOSSIBLE to use due to the screen flicker disease. I initially tried the CM 11 - 20160815 4.4, it was awfully slow. I tried various other ROMs. SlimKat was decent but, I could not get the ATT signal to work properly.
BIG THANKS to the contributors ! Great Job!!
BTW, Great forum. I will be seen here more often.
gapps
where do I get gapps for this rom?
droyid said:
This, by far, is the best ROM for Captivate. I had to rejuvenate my Captivate as my 6+ was IMPOSSIBLE to use due to the screen flicker disease. I initially tried the CM 11 - 20160815 4.4, it was awfully slow. I tried various other ROMs. SlimKat was decent but, I could not get the ATT signal to work properly.
BIG THANKS to the contributors ! Great Job!!
BTW, Great forum. I will be seen here more often.
Click to expand...
Click to collapse
Open GApps
davidcave said:
where do I get gapps for this rom?
Click to expand...
Click to collapse
I think @Audiracecar90 was referring to Open GApps (opengapps.org). Choose "ARM", Android version 5.1, and a Variant of mini or less (TV stock not recommended I guess).
Runs pretty nice. Front facing camera doesn't work.
I have just brought my old i897 Captivate back to life after a few years of sitting around, my primary current phone broke and this is going to be my backup for a few weeks. This ROM works great, I'm just having an issue where the system partition is so small/filled up (even from a clean install) that I can't even install GApps Pico! Not sure if anyone has run into this or has a solution? Thanks!
First of all, thanks to OP and everyone involved in making this rom available. I'm not too hopeful that someone will reply seeing as development for this phone seems dead, which is understandable given its age. Anyway, after overcoming some problems (I'm new), I succesfully flashed it and, by itself, works great. However, now I'm haunted by the infamous "Google play services has stopped working" message every 10 seconds. It goes away after clearing Google Services cache's but that comes with additional problems such as notifications for apps relying on it not arriving (not to mention it's a pain having to do it with every reboot). Any permanent solution? Using GApps Pico. I think the problem might related to the fact that my /cache partition is currently using vFAT (TWRP wouldn't let me change it to F2FS or EXT4.) but I don't really know. I will appreciate all the help I can get because I can't really buy a new phone. Thanks in advance.
Also, fyi, the "Downloads" app (not the manager) FC's everytime I try to open it. Not that it matters because things still get downloaded and are accesible through x-plorer but just wanted to let you know.
Not sure about the answer to your problem, but where did you find TWRP???
I think it came embedded with this rom, I mean.. I flashed from CWM Recovery the first time and once my system was all booted up, going back to recovery showed TWRP.
Also, the stock camera app fc's whenever I try to change settings but Focus (F-droid store) works fine.
Cool....Maybe I'll try it...Thanks.
i just installed but the room does not let me sync my google account
Does anyone have this ROM? The links do not work.
LineageOS uses Android 4.4.4.4 and that is no longer permitting some of my apps to work. I need a later version of Android on my Captivate.

TLS Wifi login problems -- Cloudpath

Hey guys,
I'm just looking for someone to point me in the right direction. Basically, my school has this web portal logon thing called Cloudpath (formerly xpressconnect) that requires you to log on to the portal's network in order to follow the instructions in your web browser for your specific OS. The problem arises with Android. It requires you to download an app, which does all the nitty gritty certificate installation and configuration for you. However, whenever I try this on a CUSTOM ROM (LOS-based and DU), I end up in a connecting loop. I never get connected to the secured network even though the certs appear to be installed correctly. I've tried using the app and doing it manually by downloading the certs myself. This only occurs on custom nougat roms, but works on stock MM (I haven't tried MM roms, because I want nougat).
As far as I know this problem only affects this phone after I install the rom and OpenGapps. Some of my peers have LOS and have gotten it to work, so I'm the only one, and the tech staff have no idea what to do. I don't have the log file on me, but if you need it, I can post it (they're pretty long, but seem to be detailed up until the connection part which just flops between CONNECTED and DISCONNECTED).
Is this a problem with the modem or the roms themselves? I was going to wait until the nougat kernel blobs got integrated to LOS, before trying again as I don't want to use the experimental build because it's a month old now. This problem has been around since at least January of this year. If there is a non-los based nougat rom, I would be glad to try that too. otherwise, I'm at a loss and I need some direction.
Any help is appreciated!
Seeings as how all of our Nougat ROMs are a mixed bag of partial MM and part Nougat still, and all custom ROM's for the MXPE use LoS's device tree, I am thinking this is a ROM issue, probably with some binary blob we don't have yet. The kernel source just released a few weeks ago, give it time and custom ROM's will get better (we think), and if the MXPE ever gets official Nougat, we will probably have better binary blobs too.
If it works on stock Marshmallow, it obviously isn't a radio thing, because your Nougat ROM's use the same radio firmware.
I don't have much else to say, but I would try a custom Marshmallow ROM and see if it works... if it fails as well, the problem is something in the LoS core device tree and it will need some developer's special attention (good luck with that, since we are considered to have a stable device tree it takes some work to get it changed), but if it works, chances are good that once custom Nougat ROMs get updated more it will likely work.
In a last ditch effort. I tried flashing the experimental build after posting this article, and it actually works! Now, this isn't the ideal situation given that there are some bugs (that I haven't run into yet) and that this build is a month old now. But for now, I'm satisfied. I just hope these blobs get integrated to official LOS soon.
Progress on that is here: https://review.lineageos.org/#/q/project:LineageOS/android_device_motorola_clark
If there are any roms out there that are considered stable and have these implemented now, I would appreciate it, otherwise, I think I'll be set for a little while. Thanks for your help!

Bluetooth call issues with every AOSP rom

Hello everyone,
Sorry if this is obvious or a known bug but i've searched through a dozen of AOSP threads and found nothing satisfying.
So here's the story :
- I have clean flashed LineageOS 14.1 official 20180110 a week ago but i have those distorted voices when called over any bluetooth device (tried car and BT Speaker). On their thread someone says that it actually has been fixed in 20180103 build but the problem is still present though we're already one build ahead since then.
- Anyway, I decided to change my rom and try out AOKP. I clean flashed it today. Working fine, except for that exact same bug.
- Tried AOSPExtended, same thing.
So do all AOSP roms have this bug? I can't believe it since apart from 1 or 2 posts in Lineage's thread nobody seems to care in any AOSP rom.
If (and i hope so) the answer is no : could a kind soul show me some good AOSP rom without this problem?
Thanks for caring
Same for me on Galaxy S7 (herolte G930F).
Tried newest LineageOS and AOKP - directly after setup. No other changes made. Music over bluetooth works as expected. Phone calls imposible.
I found a Video here which shows exactly what happens:
Google: "s7 edge lineageos bluetooth Youtube":
https://www.youtube.com/watch?v=utDsXrCY5N0
Also some other People seem to have the same problems. See other thread (Post #1999):
https://forum.xda-developers.com/ga...ial-lineageos-14-1-galaxy-s7-t3529197/page200
Thanks for the infos !
I didn't see the post 1999 is LOS thread, seems like the build.prop is a good fix but unfortunately it doesn't work on latest LOS build.
Will try on AOSPExtended with the same editing on audio_hal property.
EDIT : Works on AOSPExtended ! Didn't try AOKP yet
Hi can you please explain how did you fix this ? happen exactly the same for me, thanx

Samsung M30s Randomly Restarts After Software Updates - Potential solution?

Hi,
My M30s started randomly restarting after a software update. I could not find solutions here when I searched but it appears a lot of people on the internet having been facing similar issues for quite a few months now. The Samsung community forums are full of multiple messages and Samsung is pushing people to get to their phones to the service centers and are getting the motherboards replaced for free if the warranty is valid (or at a cost of INR 9,000 otherwise).
In any case, I found another poster on the Samsung forums who seems much more tech savvy than I am. And he seems to have solved the problem on his phone by changing 2 lines of code in the Linux kernel wand rebuilding the OS afterward.
Like I said, I am not tech savvy enough for this, but I thought I would post the link here because I could not find this particular fix here.
Re: READ THIS IF YOUR SAMSUNG GALAXY M30S KEEPS RANDOMLY FREEZING AND RESTARTING AUTOMATICALLY
To add a bit of my research into this problem: My phone (SM-M307FN) is rebooting many times every single day due to a Linux kernel issue which has been already fixed a long time ago in the mainline version. I am still running Android 10, because that's the latest version (M307FNXXU2BTC6) of the...
r2.community.samsung.com
(Here is the text from the post in case you are not able to open it)
-----------------------------------------------------------------------
To add a bit of my research into this problem:
My phone (SM-M307FN) is rebooting many times every single day due to a Linux kernel issue which has been already fixed a long time ago in the mainline version. I am still running Android 10, because that's the latest version (M307FNXXU2BTC6) of the OS Samsung has released on their open-source portal. I can use this source code to fix and rebuild the OS to prevent the issue from happening.
The issue and the fix is well known among the Samsung M30s community. It's two lines of code that need to be changed to prevent at least one of the common reasons for frequent reboots.
It takes a lot of work for a private user to fix those two lines of code, because Samsung releases source code that's non-trivial to compile and actually run on your device afterwards.
Samsung's Android 11 still ships with the same old kernel version (4.14.62) as their Android 9 (4.14.62), released back in 2018. There might have been some fixes between 4.14.62-19694174 and 4.14.62-20748039 introduced by Samsung in the meantime.
Regardless, this fix is not part of the source code for M307FNXXU2BTC6 (linked above) that's been released by Samsung in June 2020. Therefore, it doesn't seem like Samsung is actually applying all fixes to their kernels.
The kernel itself should have been upgraded to a higher version - at least to 4.19 - to fix bugs that's been plaguing users of Exynos 9611 chips running on Linux v4.14 for a long time.
Samsung: Please apply this fix to your Android kernels and push the update to your customers. Thank you!
References about the "fix NULL pointer deref in smaps_pte_range()":
Mainline Linux kernel fix:
[4.19,248/361] mm: /proc/pid/smaps_rollup: fix NULL pointer deref in smaps_pte_range()
https://lore.kernel.org/patchwork/patch/1010971/
Google Android Linux kernel backported this change in 2019 :
https://android.googlesource.com/kernel/common/+/043c92bd0517e0018cb6307390eb9c36b864fb9f
--------------------------------------------------------------------------------------
EDIT: After more hours of experimenting I have managed to compile a kernel with the patch mentioned in this post. I can confirm that I faced no reboots since I flashed my phone with this new kernel. Hence, I can confirm this fix really prevents frequent reboots.
superstarksa said:
Hi,
My M30s started randomly restarting after a software update. I could not find solutions here when I searched but it appears a lot of people on the internet having been facing similar issues for quite a few months now. The Samsung community forums are full of multiple messages and Samsung is pushing people to get to their phones to the service centers and are getting the motherboards replaced for free if the warranty is valid (or at a cost of INR 9,000 otherwise).
In any case, I found another poster on the Samsung forums who seems much more tech savvy than I am. And he seems to have solved the problem on his phone by changing 2 lines of code in the Linux kernel wand rebuilding the OS afterward.
Like I said, I am not tech savvy enough for this, but I thought I would post the link here because I could not find this particular fix here.
Re: READ THIS IF YOUR SAMSUNG GALAXY M30S KEEPS RANDOMLY FREEZING AND RESTARTING AUTOMATICALLY
To add a bit of my research into this problem: My phone (SM-M307FN) is rebooting many times every single day due to a Linux kernel issue which has been already fixed a long time ago in the mainline version. I am still running Android 10, because that's the latest version (M307FNXXU2BTC6) of the...
r2.community.samsung.com
(Here is the text from the post in case you are not able to open it)
-----------------------------------------------------------------------
To add a bit of my research into this problem:
My phone (SM-M307FN) is rebooting many times every single day due to a Linux kernel issue which has been already fixed a long time ago in the mainline version. I am still running Android 10, because that's the latest version (M307FNXXU2BTC6) of the OS Samsung has released on their open-source portal. I can use this source code to fix and rebuild the OS to prevent the issue from happening.
The issue and the fix is well known among the Samsung M30s community. It's two lines of code that need to be changed to prevent at least one of the common reasons for frequent reboots.
It takes a lot of work for a private user to fix those two lines of code, because Samsung releases source code that's non-trivial to compile and actually run on your device afterwards.
Samsung's Android 11 still ships with the same old kernel version (4.14.62) as their Android 9 (4.14.62), released back in 2018. There might have been some fixes between 4.14.62-19694174 and 4.14.62-20748039 introduced by Samsung in the meantime.
Regardless, this fix is not part of the source code for M307FNXXU2BTC6 (linked above) that's been released by Samsung in June 2020. Therefore, it doesn't seem like Samsung is actually applying all fixes to their kernels.
The kernel itself should have been upgraded to a higher version - at least to 4.19 - to fix bugs that's been plaguing users of Exynos 9611 chips running on Linux v4.14 for a long time.
Samsung: Please apply this fix to your Android kernels and push the update to your customers. Thank you!
References about the "fix NULL pointer deref in smaps_pte_range()":
Mainline Linux kernel fix:
[4.19,248/361] mm: /proc/pid/smaps_rollup: fix NULL pointer deref in smaps_pte_range()
https://lore.kernel.org/patchwork/patch/1010971/
Google Android Linux kernel backported this change in 2019 :
https://android.googlesource.com/kernel/common/+/043c92bd0517e0018cb6307390eb9c36b864fb9f
--------------------------------------------------------------------------------------
EDIT: After more hours of experimenting I have managed to compile a kernel with the patch mentioned in this post. I can confirm that I faced no reboots since I flashed my phone with this new kernel. Hence, I can confirm this fix really prevents frequent reboots.
Click to expand...
Click to collapse
Amazing work brother, everyone is facing this restart problem but you can help
Can you compile the latest kernal(4.14.113) and share it with our M30s community.
razs.originals said:
Amazing work brother, everyone is facing this restart problem but you can help
Can you compile the latest kernal(4.14.113) and share it with our M30s community.
Click to expand...
Click to collapse
Like I said in my post, I am not tech savvy enough to do this. And I am wondering if this problem has been widely reported even. This is the place I expected to find lot of buzz but i dont see any
Everyone is upset with this Samsung's reboot problem. Anyways we users will find a solution.
I am a M30s owner. I have done this on my phone and it's a temporary fix. Atleast try this and wait for the official fix. It's better to have something than nothing.
How To Fix Restart Issue On Galaxy M30s, M31, M31s, A50, A50s? (Updated) - SamsungSFour.Com
How To Fix Restart Issue On Galaxy M30s, M31, M31s, A50, A50s? (Latest Method)
www.samsungsfour.com

Categories

Resources