An update:
I noticed that my phone its not locked in 3g but it's locked in the same type of network that I selected before flashing a custom rom. So I flashed stock, selected 4g and flashed LOS again to "solve" my problem.
[ROM][UNOFFICIAL][P][F500,LS991,H81x,US991,VS986] LineageOS 16.0
- Thread starter steadfasterX
- Start date
I noticed that my phone its not locked in 3g but it's locked in the same type of network that I selected before flashing a custom rom. So I flashed stock, selected 4g and flashed LOS again to "solve" my problem.
Bluetooth Crashing Issues
Good evening all, hope you are well.
NOTE: I have removed the majority of this post temporarily as the Forum keeps detecting it as spam for some reason.
I'm looking to get some assistance with a bluetooth crashing error I'm getting as soon as bluetooth is enabled.
I've been using the ROM for a while without bluetooth as I think its a fantastic ROM, but I'm really feeling the urge to be able to use my Smart Watch once again, which I cannot do without functional bluetooth.
As I've been using the ROM for a while, allow me to give a full recount of actions I've taken to date to help you understand what I've done with the device.
EDIT: adding bits of this post back in so that hopefully the spam detector doesn't block my legitimate information.
Actions Taken
1.) Installed LG Up and upgraded device to latest version.
2.) USU'd my device using FWUL
2a.) Link to instructions: [LINK REDACTED due to spam detector, its steadfasterX's thread on how to USU your device.]
3.) Flashed modem from those provided in the OP.
3a.) Link to modems: [LINK REDACTED due to spam detector, its the link from the OP]
3b.) Version flashed: h815_20p_modem.zip
4.) Clean installed LoS using 23rd February build.
4a.) Link to build: [LINK REDACTED due to spam detector, its the leechbin link from the OP]
At this point I had the issue with bluetooth, but was happy other things were working fine and opted to remain on the build. I was able to install various apps I like to use and root with Magisk without any other issues.
Eventually I decided to look into the issue again due to a desire to use my Smart Watch again.
5.) Searched all posts in this thread for "Bluetooth Crash"
6.) Searched github issues for related issues in both closed and open issues.
6a.) Link to github issues: [LINK REDACTED due to spam detector, its the issues page on github from the OP.]
7.) After not finding anything that seemed actionable, I noticed we now had a March build for the ROM, so I CLEAN installed the 24th March build
7a.) Link to build: [LINK REDACTED due to spam detector, its the leechbin link from the OP]
8.) Issue persisted.
9.) Fast-forward to today... Looking into the issue again.
10.) Generated a logcat following Option B in steps 2 & 3.
10a.) Link to instructions: [LINK REDACTED due to spam detector, I got it from the FAQs of the OP.]
10b.) Link to logcat: https://paste.omnirom.org/view/023b15d7
Cheers,
-zwab
Good evening all, hope you are well.
NOTE: I have removed the majority of this post temporarily as the Forum keeps detecting it as spam for some reason.
I'm looking to get some assistance with a bluetooth crashing error I'm getting as soon as bluetooth is enabled.
I've been using the ROM for a while without bluetooth as I think its a fantastic ROM, but I'm really feeling the urge to be able to use my Smart Watch once again, which I cannot do without functional bluetooth.
As I've been using the ROM for a while, allow me to give a full recount of actions I've taken to date to help you understand what I've done with the device.
EDIT: adding bits of this post back in so that hopefully the spam detector doesn't block my legitimate information.
Actions Taken
1.) Installed LG Up and upgraded device to latest version.
2.) USU'd my device using FWUL
2a.) Link to instructions: [LINK REDACTED due to spam detector, its steadfasterX's thread on how to USU your device.]
3.) Flashed modem from those provided in the OP.
3a.) Link to modems: [LINK REDACTED due to spam detector, its the link from the OP]
3b.) Version flashed: h815_20p_modem.zip
4.) Clean installed LoS using 23rd February build.
4a.) Link to build: [LINK REDACTED due to spam detector, its the leechbin link from the OP]
At this point I had the issue with bluetooth, but was happy other things were working fine and opted to remain on the build. I was able to install various apps I like to use and root with Magisk without any other issues.
Eventually I decided to look into the issue again due to a desire to use my Smart Watch again.
5.) Searched all posts in this thread for "Bluetooth Crash"
6.) Searched github issues for related issues in both closed and open issues.
6a.) Link to github issues: [LINK REDACTED due to spam detector, its the issues page on github from the OP.]
7.) After not finding anything that seemed actionable, I noticed we now had a March build for the ROM, so I CLEAN installed the 24th March build
7a.) Link to build: [LINK REDACTED due to spam detector, its the leechbin link from the OP]
8.) Issue persisted.
9.) Fast-forward to today... Looking into the issue again.
10.) Generated a logcat following Option B in steps 2 & 3.
10a.) Link to instructions: [LINK REDACTED due to spam detector, I got it from the FAQs of the OP.]
10b.) Link to logcat: https://paste.omnirom.org/view/023b15d7
Cheers,
-zwab
Last edited:
Observations with new release
Overall result is:
1) stability is much better, but the reason for freezing/sluggish camera doesn't seem to be eliminated (albeit reboot isn't necessarily required)
2) battery consumption is clearly better
3) system UI gets slower after intensive usage of device
During the hikes flight mode active for most of the time. I use OpenCamera with DRO enabled. In former releases (including TEST2-Kernel) camera became nearly unresponsive after ~30-40 photos and I had to reboot.
ad 1)
During the first hike (13h/87 pics) absolutely no problem - dreamlike behaviour. But suddenly when taking the last 2 pics it took very much longer and music player was interrupted.
Decided to *not* reboot - force stopped OpenCamera app and started the hike next day (8h/56 pics). Every ~8 photos camera very slow, sound interupted and messages about not responsive background apps (I've activated background-ANRs in developer options). Force stop of OpenCamera necessary. So in the evening I decided to reboot, because (for me) it seemed that some kind of kernel structure was exhausted and not freed.
No problems on the third hike. But afterward, when using other apps, I noticed that starting of apps or switching apps took more time. Everything worked, but it felt much slower.
ad 2)
I use a 6000 mAh battery - with navigation and tracking I've always had a battery consumption of ~ca 12-15% in 2 hours. Now (on all three hikes, also the "problematic" second) there was ~8-10% in 2 hours. Much better!
Maybe these observatins are useful. Greets!
Installed 20200515-build and did three long hikes (13h/8h/11h) with navigation, tracking and many pictures (87/56/86) - so i dare to say something about stability of this release and the difference to previous versions.This build actually will help all devices , ilapo or not
Sent from my OnePlus 6T using XDA Labs
Overall result is:
1) stability is much better, but the reason for freezing/sluggish camera doesn't seem to be eliminated (albeit reboot isn't necessarily required)
2) battery consumption is clearly better
3) system UI gets slower after intensive usage of device
During the hikes flight mode active for most of the time. I use OpenCamera with DRO enabled. In former releases (including TEST2-Kernel) camera became nearly unresponsive after ~30-40 photos and I had to reboot.
ad 1)
During the first hike (13h/87 pics) absolutely no problem - dreamlike behaviour. But suddenly when taking the last 2 pics it took very much longer and music player was interrupted.
Decided to *not* reboot - force stopped OpenCamera app and started the hike next day (8h/56 pics). Every ~8 photos camera very slow, sound interupted and messages about not responsive background apps (I've activated background-ANRs in developer options). Force stop of OpenCamera necessary. So in the evening I decided to reboot, because (for me) it seemed that some kind of kernel structure was exhausted and not freed.
No problems on the third hike. But afterward, when using other apps, I noticed that starting of apps or switching apps took more time. Everything worked, but it felt much slower.
ad 2)
I use a 6000 mAh battery - with navigation and tracking I've always had a battery consumption of ~ca 12-15% in 2 hours. Now (on all three hikes, also the "problematic" second) there was ~8-10% in 2 hours. Much better!
Maybe these observatins are useful. Greets!
works good, but in games is very slow.. with nougat was fasterYes, works well for me! The battery life is much better
Your issue is:
"No Bluetooth Address"
Share the log from FAQ #7 and we get that fixed when I'm back from my vacation .
If u can't wait share these logs in ANY case and add your BT addr in /data/misc/bluetooth/bdaddr manually .
But ofc it would be better to wait so that can be fixed for others which going through that rare situation ..
Sent from my OnePlus 6T using XDA Labs
Hi Steadfaster,
Thanks for taking the time out to look into this, especially while you're on holiday.
The log files can be found: (square brackers inserted in the URLs to prevent the Forum anti-spammer from blocking my post)
boot_lc_kernel.txt - https[://]del.dog/motinaduki
boot_lc_full.txt - https[://]del.dog/ettingerin
boot_lc_crash.txt - Not uploaded as the file was 0KB, empty.
As for the workaround you suggested, if I create the file /data/misc/bluetooth/bdaddr which simply contains a single line with any bullsh*t Bluetooth MAC address (e.g: E0-E8-16-93-72-61) do you believe that would get things working again? Does the file expect the MAC address to be formatted with dashes like my example, or with colons? (e.g: E0:E8:16:93:72:61)
If the workaround is not as simple as I make it out to be, I'm more than happy to wait for the full fix when you return from holiday.
Cheers,
-zwab
Last edited:
H810 (recovered h812 frankenstein G4) checking in. Updated the G4 back in March and had similar perfomance problems. Been lurking on the forums for a new build and updated to May 15 build a few days ago. Just to let everyone know, everything is in working order. Phone is much more responsive and battery life is back to where it once was (got a ~6000maH battery so we packing). Did everything in order as listed expect for the checksum step, is it the terminal on the phone where you run adb command? If so it couldn't find adb command.
Nevertheless it installed properly. Big thanks to @steadfasterX and other community members that bring life to old phones.
I'm on the latest build but I have this issue for a while now. It appeared from nowhere while I was adjusting the call volume. Now it feels like max volume is like 10% of the original max volume and I barely understand the other person even though my phone should be screaming at me. How could I investigate/fix this?
No calls or text on VS986
Anyone else have this issue? Everything works on stock ROM but not with Pie. Data works, but no calls or text. Tried flashing MM modem, zero-ing out modem partitions, etc.
I followed instructions in this thread including full clean. Installed lineage-16.0-20200515-UNOFFICIAL-vs986_usu.zip and vs986_2BA_modem.zip
Additional info: It takes several minutes after reboot for mobile network to start working ("No SIM card" for the first few minutes). Calls fail with "Mobile network not available" after about a 30 second timeout.
Update: I also tried this:
Update: I found a post by steadfasterX here that says that this is a known issue, I am guessing it's referring to this, which implies that calls simply don't work at the moment.
Anyone else have this issue? Everything works on stock ROM but not with Pie. Data works, but no calls or text. Tried flashing MM modem, zero-ing out modem partitions, etc.
I followed instructions in this thread including full clean. Installed lineage-16.0-20200515-UNOFFICIAL-vs986_usu.zip and vs986_2BA_modem.zip
Additional info: It takes several minutes after reboot for mobile network to start working ("No SIM card" for the first few minutes). Calls fail with "Mobile network not available" after about a 30 second timeout.
Update: I also tried this:
- I followed these instructions for completely re-installing stock partitions and wiping everything: https://forum.xda-developers.com/verizon-g4/guide-how-to-update-firmware-usu-how-to-t3855522
- Booted stock ROM and confirmed it makes calls.
- I then I did a factory reset in TWRP and flashed lineage, addonsu and gapps (as per this thread)
Update: I found a post by steadfasterX here that says that this is a known issue, I am guessing it's referring to this, which implies that calls simply don't work at the moment.
Last edited:
Hi, the format should be
cur_etheraddr=00:00:00:00:00:00
In my case with a usu unlocked :
cur_etheraddr=00:00:00:00:00:00h815_usu
Anyway, on my notes I found:
How to find real address https://github.com/Suicide-Squirrel/issues_oreo/issues/2#issuecomment-405913133 adb shell grep macaddr= /system/etc/wifi/bcmdhd.cal | sed 's/macaddr=/cur_etheraddr=/g' > /data/misc/wifi/config Verify (while still in that adb shell): cat /data/misc/wifi/config
Regards.
akomakomakom,
Well documented problem. Search forum for details. Some vs986's do have RIL (cell service) with this ROM, and now Android2468's Potato ROM is available. At least 2 phones documented to work, mine and Android2468 has one, but don't know why most don't work. See Steadfasterx Github issue #41 for ongoing developments and maybe you can help us work on it..
tullyp
Well documented problem. Search forum for details. Some vs986's do have RIL (cell service) with this ROM, and now Android2468's Potato ROM is available. At least 2 phones documented to work, mine and Android2468 has one, but don't know why most don't work. See Steadfasterx Github issue #41 for ongoing developments and maybe you can help us work on it..
tullyp
Hi, sorry for a possible stupid question.
I used your ROM previously, which was working great, but I wanted to do a reset without Gapps, as to free myself (at least in parts) from Google. In order to this, I did a full clean install, without any errors occurring.
However I encountered one problem pushing the Services Core file to my device:
While in Android, I installed the file, according to FAQ 9 and then, as I don't have root, tried to push the file to the priv-app folder. However, I get the following error:
cannot stat 'tmp/com.google.....apk': no such file or directory. I copied the codes directly from the FAQ, so I don't have a clue, what went wrong. Can somebody give a hint? Because I'd really like to be able to use my GPS.
Cheers!
I used your ROM previously, which was working great, but I wanted to do a reset without Gapps, as to free myself (at least in parts) from Google. In order to this, I did a full clean install, without any errors occurring.
However I encountered one problem pushing the Services Core file to my device:
While in Android, I installed the file, according to FAQ 9 and then, as I don't have root, tried to push the file to the priv-app folder. However, I get the following error:
cannot stat 'tmp/com.google.....apk': no such file or directory. I copied the codes directly from the FAQ, so I don't have a clue, what went wrong. Can somebody give a hint? Because I'd really like to be able to use my GPS.
Cheers!
Hallo !
Please bear in mind that you only have to do one of the three options in FAQ #9, point 3.
Personnally, I do the following :
Have you tried it yet ? Does it work ? If it does, no need to go further.
I installed latest lineage-16.0-20200515-UNOFFICIAL-h815 with full wipe etc
open_gapps-arm64-9.0-mini-20200530.zip
Magisk-v20.4.zip
Now, restored GroundWire (Acrobits VoIP). My Push notification don't work
I googled a bit, something vague about GCM and MicroG. Can someone point me to the right direction, where I can enable Push Notification or Google cloud messages
Thank you
[/COLOR]
open_gapps-arm64-9.0-mini-20200530.zip
Magisk-v20.4.zip
Now, restored GroundWire (Acrobits VoIP). My Push notification don't work
I googled a bit, something vague about GCM and MicroG. Can someone point me to the right direction, where I can enable Push Notification or Google cloud messages
Thank you
[/COLOR]
Last edited:
You have to either install gapps or follow FAQ 9
Sent from my OnePlus 6T using XDA Labs
Thank you,
as I mentioned, I've installed open_gapps-arm64-9.0-mini-20200530.zip
Is this one qualify ? Or I have to update with "real" Gapps somehow ?
Obviously, got through every setting to see if there is a missing permission etc. Notification allowed, (Show over apps etc), all required permissions are granted, but no push. Neither with "Test push notifications" nor with real calls
Last edited:
Tried to whitelist my device, as it described here: https://www.phonearena.com/news/Reg...d-services-Android-certified-support_id104243.
P.S. Tested with https://play.google.com/store/apps/details?id=com.firstrowria.pushnotificationtester&hl=en_CA, notifications forked fine
I will target the Ground Wire now. Sorry for the confusion
Not sure if it was blacklisted, but I've got confirmation
Didn't work
Every setting in application is verified, so I did in Android settings
Two questions:
1. If I installed (at the very beginning) open_gapps-arm64-9.0-mini-20200530.zip , do I need to do (or refrain of doing) from FAQ 9?
2. Is there an application to test, verify, log etc push notification in Pie? To see where problem is
Update:
Tested with Push Notification Tester, https://play.google.com/store/apps/details?id=com.firstrowria.pushnotificationtester&hl=en_CA. This one worked just fine
I'll contact Acrobits (Groundwire) than
Sorry for the confusion
Last edited:
Installed GroundWire beta, notifications are working now
New posts
-
-
-
[MOD][XPOSED][3.1.1] CustoMIUIzer - Customize your MIUI ROM
- Latest: nikdrlecter
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone