Related
Ever since I flashed 5.0 to my 900V, my battery life has gone significantly down. Now this can be expected to some extent as I can no longer use Amplify to control NlpCollectorWakeLock (which is one of a few wakelocks going to town on my battery). One of the others is bluedroid_timer, which is part of bluetooth. I did some searching and I saw some other people with the same issue, but no answers. I use a Moto 360 on a daily basis, use bluetooth streaming in my car, and use bluetooth headphones at the gym, so turning off bluetooth isn't really an option. Bluesleep is another one that is spending a lot of time running. Anyone have any ideas? I've read a few threads where people mention this problem, but no one has posted any answers yet. Here is an album of my wakelocks.
Did you ever figure this out? I'm experiencing a very similar issue.
I'm not rooted, so I can't see the specific wakelocks but it's absolutely Bluetooth related, even with all device profiles deleted. If I have the BT radio on, my battery gets hammered and the phone never goes into deep sleep, turn the radio off and all is normal.
MattE303 said:
Did you ever figure this out? I'm experiencing a very similar issue.
I'm not rooted, so I can't see the specific wakelocks but it's absolutely Bluetooth related, even with all device profiles deleted. If I have the BT radio on, my battery gets hammered and the phone never goes into deep sleep, turn the radio off and all is normal.
Click to expand...
Click to collapse
I just started experiencing this as well. I'm on a T-Mobile S4, running a GPE rom. It started happening in the last month, not exactly sure when. I ran a rooted TouchWiz stock rom before that and I don't recall ever seeing it.
So you're running fully stock? I was curious if I installed some weird app or software package that messed with things, but if you're running stock that would seem to rule that out..
dirkdigles said:
I just started experiencing this as well. I'm on a T-Mobile S4, running a GPE rom. It started happening in the last month, not exactly sure when. I ran a rooted TouchWiz stock rom before that and I don't recall ever seeing it.
So you're running fully stock? I was curious if I installed some weird app or software package that messed with things, but if you're running stock that would seem to rule that out..
Click to expand...
Click to collapse
yup, Galaxy S5 with current Verizon build of Lollipop, not rooted, just Nova launcher and my usual apps. Since the bluetooth battery issue, I've tried reboots, clearing cache partition, deleting all BT device profiles, etc. Everything short of an FDR, which I don't have time for right now.
MattE303 said:
yup, Galaxy S5 with current Verizon build of Lollipop, not rooted, just Nova launcher and my usual apps. Since the bluetooth battery issue, I've tried reboots, clearing cache partition, deleting all BT device profiles, etc. Everything short of an FDR, which I don't have time for right now.
Click to expand...
Click to collapse
Thanks for the reply.
In lots of google searches, seems like many have this issue, but i couldn't find a solution anywhere, nor any consistency among devices. Seems that some custom kernels fix the issue.
But if you want to submit bug reports here, there's an official Google bug report thread on the issue that is alive:
https://code.google.com/p/android/issues/detail?id=87778
dirkdigles said:
I just started experiencing this as well. I'm on a T-Mobile S4, running a GPE rom. It started happening in the last month, not exactly sure when. I ran a rooted TouchWiz stock rom before that and I don't recall ever seeing it.
So you're running fully stock? I was curious if I installed some weird app or software package that messed with things, but if you're running stock that would seem to rule that out..
Click to expand...
Click to collapse
dirkdigles said:
Thanks for the reply.
In lots of google searches, seems like many have this issue, but i couldn't find a solution anywhere, nor any consistency among devices. Seems that some custom kernels fix the issue.
But if you want to submit bug reports here, there's an official Google bug report thread on the issue that is alive:
Click to expand...
Click to collapse
Thanks! the Google bug report is an interesting read, we're definitely not alone in this. I'm gonna try a few things based on what I read there and report my findings.
MattE303 said:
Thanks! the Google bug report is an interesting read, we're definitely not alone in this. I'm gonna try a few things based on what I read there and report my findings.
Click to expand...
Click to collapse
My solution was a particular app was causing it. Same for another user if you read the thread.
The app for me was MyRadar. Another user had a problem with Gas Buddy.
Both of these apps were recently updated to add bluetooth permissions.
dirkdigles said:
My solution was a particular app was causing it. Same for another user if you read the thread.
The app for me was MyRadar. Another user had a problem with Gas Buddy.
Both of these apps were recently updated to add bluetooth permissions.
Click to expand...
Click to collapse
I did see that and I am a GasBuddy user. There was also mention of NFC, that was the first thing I looked at. Experimenting now with GasBuddy removed.
I'm not rooted so I can't check for individual wakelocks, I have to just run it for a while, then look at the "Awake" bar graph in the stock Battery app, so it takes while to see if anything changed. I really wish Google would give us the choice whether to let 3rd party apps see the detailed battery stats, locking that down made it so much harder to diagnose this kind of thing without root.
Glad you got yours sorted out!
dirkdigles said:
My solution was a particular app was causing it. Same for another user if you read the thread.
The app for me was MyRadar. Another user had a problem with Gas Buddy.
Both of these apps were recently updated to add bluetooth permissions.
Click to expand...
Click to collapse
I understand your issue completely, but why in the world does gas buddy need bt permissions? ? ?
Sent from my SM-G900V using Tapatalk
ldeveraux said:
I understand your issue completely, but why in the world does gas buddy need bt permissions? ? ?
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
No idea, but it's mentioned on their Playstore page in a recent app update:
4.6.6
Get deals while you are filling up by turning on Bluetooth.
Click to expand...
Click to collapse
---------- Post added at 12:14 PM ---------- Previous post was at 11:43 AM ----------
so far it's looking like GasBuddy was the culprit in my case. I've been running several hours with GasBuddy removed, both NFC and Bluetooth are on, and battery usage/wakelocks appear normal.
I'm gonna give it a day or so to see if the problem spontaneously returns, then re-install GasBuddy and see what happens.
MattE303 said:
No idea, but it's mentioned on their Playstore page in a recent app update:
---------- Post added at 12:14 PM ---------- Previous post was at 11:43 AM ----------
so far it's looking like GasBuddy was the culprit in my case. I've been running several hours with GasBuddy removed, both NFC and Bluetooth are on, and battery usage/wakelocks appear normal.
I'm gonna give it a day or so to see if the problem spontaneously returns, then re-install GasBuddy and see what happens.
Click to expand...
Click to collapse
Definitely a GasBuddy issue on my phone, "Awake" bar graph becomes a solid block soon after installing GasBuddy, and returns to normal after uninstalling it. I've repeated this test a few times.
MattE303 said:
Definitely a GasBuddy issue on my phone, "Awake" bar graph becomes a solid block soon after installing GasBuddy, and returns to normal after uninstalling it. I've repeated this test a few times.
Click to expand...
Click to collapse
I started experiencing the issue with excessive wakelocks from Bluedroid_timer on my stock Nexus 6 about a month ago. Noticed my battery life dropped significantly as a result. Used Permission Friendly Apps to see which apps were using BT and if I happened to install any around the time this problem began. Only new apps indicating BT connectivity were GasBuddy and Netflix. No idea why GasBuddy needs BT but I'm pretty sure I installed it about the same time the wakelock issue began. Good to know someone else saw the same thing. Just uninstalled it and waiting to see if the wakelocks stop.
I cannot seem to fix it. I have searched threads here and on other forums, poked around the Google forums and I have tried everything mentioned and I cannot get it to go away. It comes and goes at random too. I have yet to flash an older radio, if anyone could provide me with one then I could give that a shot, but I cannot believe that I am in the minority here.
Oh and I have completely factory reset my phone and it does not help. Rooted running PureNexus.
tluley51 said:
I cannot seem to fix it. I have searched threads here and on other forums, poked around the Google forums and I have tried everything mentioned and I cannot get it to go away. It comes and goes at random too. I have yet to flash an older radio, if anyone could provide me with one then I could give that a shot, but I cannot believe that I am in the minority here.
Oh and I have completely factory reset my phone and it does not help. Rooted running PureNexus.
Click to expand...
Click to collapse
That's means your router has no Internet not the phone. It's your WiFi router losing its Internet connection. Without seeing your setup I can only speculate as to the exact issue.
Gizmoe said:
That's means your router has no Internet not the phone. It's your WiFi router losing its Internet connection. Without seeing your setup I can only speculate as to the exact issue.
Click to expand...
Click to collapse
There are 2 problems with that. All my computers and other phones in the house do not have this problem, so it definitely is not the router. Also, I am not always connected to my home router. I will be on my commute to work (no wifi) and it will happen. Hell, it will happen AT work and we have an enterprise network with update to date Cisco switches and APs.
tluley51 said:
There are 2 problems with that. All my computers and other phones in the house do not have this problem, so it definitely is not the router. Also, I am not always connected to my home router. I will be on my commute to work (no wifi) and it will happen. Hell, it will happen AT work and we have an enterprise network with update to date Cisco switches and APs.
Click to expand...
Click to collapse
Rma then. It's not normal.
Gizmoe said:
Rma then. It's not normal.
Click to expand...
Click to collapse
Funny thing is, I am back to unrooted stock and it instantly goes away. I was having the issue last night and into this morning on my home Wifi, on my way to work, then at work on LTE and when on the Wifi. I reverted the phone back to stock and now all is well. Why would a custom rom have something to do with not connecting to Google Services??
tluley51 said:
Funny thing is, I am back to unrooted stock and it instantly goes away. I was having the issue last night and into this morning on my home Wifi, on my way to work, then at work on LTE and when on the Wifi. I reverted the phone back to stock and now all is well. Why would a custom rom have something to do with not connecting to Google Services??
Click to expand...
Click to collapse
There could be many reasons. Custom Roms are modified and usually have custom kernels. Lots of stuff can go wrong. It's the risk of flashing custom Roms. I find with the 6p, stock rooted is the best. There isn't anything you can't do between xposed and root access. Each time I try a rom I have radio issues to be honest. I just stay stock.
That's a good call. Really the only thing I want root for is theming and double tap to wake, both can be achieved without custom rom (I believe)
Although I use Android Pay and even with systemless root, I am unable to get it to work....So maybe I should stay stock for awhile, but that is for another thread.
Appreciate your help, Gizmoe!
tluley51 said:
That's a good call. Really the only thing I want root for is theming and double tap to wake, both can be achieved without custom rom (I believe)
Although I use Android Pay and even with systemless root, I am unable to get it to work....So maybe I should stay stock for awhile, but that is for another thread.
Appreciate your help, Gizmoe!
Click to expand...
Click to collapse
I think Google has updated the safetynet API that prevents Android Pay working with Systemless root. I had it working until the latest update of Android Pay.
tluley51 said:
I cannot seem to fix it. I have searched threads here and on other forums, poked around the Google forums and I have tried everything mentioned and I cannot get it to go away. It comes and goes at random too. I have yet to flash an older radio, if anyone could provide me with one then I could give that a shot, but I cannot believe that I am in the minority here.
Oh and I have completely factory reset my phone and it does not help. Rooted running PureNexus.
Click to expand...
Click to collapse
I see you are running Pure Nexus, seems you are not the first to have an issue with wifi. Beans has suggested a potential fix.
SlimSnoopOS said:
I see you are running Pure Nexus, seems you are not the first to have an issue with wifi. Beans has suggested a potential fix.
Click to expand...
Click to collapse
Unfortunately, I had tried that. I am not even sure it is Wifi related though as I was getting the ! on my cell signal as well when I wasn't even on wifi.
tluley51 said:
Unfortunately, I had tried that. I am not even sure it is Wifi related though as I was getting the ! on my cell signal as well when I wasn't even on wifi.
Click to expand...
Click to collapse
Hmm, that is unusual. Is this all occurring with the matching Vendor.img to the Pure Nexus build you are using?
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Hmm, that is unusual. Is this all occurring with the matching Vendor.img to the Pure Nexus build you are using?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Yes, it was. I have reverted back to stock unrooted and I am no longer having the issue. I did not want to do this, but unfortunately I have to actually use my phone as a phone and need the basic functionality that I was losing with the continuous issue.
tluley51 said:
Yes, it was. I have reverted back to stock unrooted and I am no longer having the issue. I did not want to do this, but unfortunately I have to actually use my phone as a phone and need the basic functionality that I was losing with the continuous issue.
Click to expand...
Click to collapse
I suggest trying another rom and testing that out. May help you isolate the problem. Perhaps its has to do with 2.4 ghz vs. 5.0 ghz Wi-Fi networks, either can be forced in Wi-Fi settings. Or it may be a conflict with a mod in Pure Nexus if this does not occur on another rom.
Sent from my Nexus 5X using Tapatalk
Hi,
Since I updated my nexus 6p to 7.1.1 I experiencing a lot of network drops and call issues.
Does anyone have the same problem?
Not at all. What baseband version is showing in settings? angler-03.78 is the current baseband. Other than that, confirm your APN profile is the same as it was before you had issues.
3.78 here, and same APN.
The problem still persist after reflashing the stock firmware (trough flashfire)
asafba said:
Hi,
Since I updated my nexus 6p to 7.1.1 I experiencing a lot of network drops and call issues.
Does anyone have the same problem?
Click to expand...
Click to collapse
Yes, I've had several connectivity issues regarding LTE. Multiple instances of getting the "LTE" logo showing pretty good signal strength but with the little "x" next to it showing there is no actual connection.
I've also had some calling weirdness where I try to take an in coming call but other person can't hear me. When I try to call them back it goes straight from "dialing" to hangup right away.
I sideloaded the 7.1.1 update and I'm on Verizon so I'm not terribly surprised there are some issues. I don't have any fixes or suggestions, just letting you know you're not alone
Haha thanks, I'm in Israeli carrier so if it a carrier related issues, it's a big problem for me.
Can we use an older modem?
asafba said:
Haha thanks, I'm in Israeli carrier so if it a carrier related issues, it's a big problem for me.
Can we use an older modem?
Click to expand...
Click to collapse
Nope that might cause bootloops
I have the same problem.. After a fresh reboot first few minutes the phone just drops and connects to signal all the time. Can't even make a 10 second call (sometimes it manages to get call started and then just cuts off as it drops signal). Then after a few minutes phone shows full signal all the time but it cant make/recieve a call(it says number not available)... tried everything that I could on software level so I guess its something wrong with the antenna in my phone. I'm taking it back to the shop where I bought it from for a repair.
Vref said:
Yes, I've had several connectivity issues regarding LTE. Multiple instances of getting the "LTE" logo showing pretty good signal strength but with the little "x" next to it showing there is no actual connection.
I've also had some calling weirdness where I try to take an in coming call but other person can't hear me. When I try to call them back it goes straight from "dialing" to hangup right away.
I sideloaded the 7.1.1 update and I'm on Verizon so I'm not terribly surprised there are some issues. I don't have any fixes or suggestions, just letting you know you're not alone
Click to expand...
Click to collapse
Some people on Verizon in the Cortex ROM thread reported that flashing radio 3.75 fixed their connectivity issues. I didn't have this issue and am using the latest radio so I have no personal experience with this fix.
---------- Post added at 12:16 AM ---------- Previous post was at 12:09 AM ----------
asafba said:
Haha thanks, I'm in Israeli carrier so if it a carrier related issues, it's a big problem for me.
Can we use an older modem?
Click to expand...
Click to collapse
Some people in Cortex Rom thread had similar issues and reported that flashing radio 3.75 fixed the problem. Cortex ROM is stock based so if it didn't cause a boot loop for them it probably won't cause one for you--but that might depend on the ROM you are running and whether or not your bootloader is locked. I'm running the latest radio so I can't personally vouch for this as a fix.
jhs39 said:
Some people on Verizon in the Cortex ROM thread reported that flashing radio 3.75 fixed their connectivity issues. I didn't have this issue and am using the latest radio so I have no personal experience with this fix.
---------- Post added at 12:16 AM ---------- Previous post was at 12:09 AM ----------
Some people in Cortex Rom thread had similar issues and reported that flashing radio 3.75 fixed the problem. Cortex ROM is stock based so if it didn't cause a boot loop for them it probably won't cause one for you--but that might depend on the ROM you are running and whether or not your bootloader is locked. I'm running the latest radio so I can't personally vouch for this as a fix.
Click to expand...
Click to collapse
Appreciate it. Unless you can flash just the radio with the bootloader locked it's gonna be a no go for me. Had to unroot, relock, and go back to straight outta the box stock when I got hired at my new company.
Sent from my Nexus 6P using XDA-Developers mobile app
Received the January security patch today. Haven't found any bugs yet.
There are no new bugs for me as well but the current one remain like the cache one. But my phone's performance has definitely improved a lot. It's finally quick now and I have not experienced any lags since 2 days.
Slow emmc, auto brightness won't go below 19%
no notification from download manager
Front facing camera flash isn't working
viniciusvm1 said:
Front facing camera flash isn't working
Click to expand...
Click to collapse
flash is working over here
LucasBarrios11 said:
flash is working over here
Click to expand...
Click to collapse
Same here, except the fact that the flash stays on for the whole time when I switch to the front cam.
[email protected] said:
Same here, except the fact that the flash stays on for the whole time when I switch to the front cam.
Click to expand...
Click to collapse
same here but i thought that's the normal behaviour
Unreliable data connection, after the latest update my phone has been dropping data connection constantly, especially when the screen is off. It could be my ISP, but it started right after the update, before it was working fine.
When will they fix the cpu the 4 core min freq is 1401 mhz it should be 633mhz. .need to restart the phone to fix it but after some time problem shows up again
When increasing or decreasing the volume sound, the window doesn't disappear automatically till I touch other part of the screen
Front flash not working
Emmc not fixed
Headphone volume not fixed
And some users facing bootloop after updating
So looks like the update is pretty good ?
---------- Post added at 12:54 PM ---------- Previous post was at 12:49 PM ----------
@viniciusvm1 It wasn't working for me but clearing the data for camera app fixes the issue
Notifications suddenly going mute and doesn't work untill I restart the device. The ringer is not affected though. I have seen this bug right after attending a call, sometimes with bluetooth headset paired . ( Don't know if that's causing it, but everytime I encountered this was after a call.) It used to even happen earlier at times... Does anybody has a fix for this? Anybody esle experience this? Thanks in advance!
They have pulled the January update.
psichokillah said:
They have pulled the January update.
Click to expand...
Click to collapse
Do they really not test the update before releasing it?? This was very sloppy and unprofessional and I can't believe an Android One phone experienced something like this, since it's backed by "Google" and whatnot.
No wonder many of the bugs are still unfixed, this feels like the development team is probably made up of one or two developers who have 13 other projects in parallel.
Shame.
psichokillah said:
They have pulled the January update.
Click to expand...
Click to collapse
Even after releasing the 'January Update' at the end of the month, they had to stop the updates? Damn. Imo, they are focusing too much on MIUI and not on Android One.
Hello,
I've just wanted to know who already tried to install Lineage 17.1 on bardock(pro)?
I'm still on Lineage 16 and a little bit afraid to change in such early state.
What are you experience?
Especially with TWRP an Lineage 17.1?
Let me know...
Xtaner said:
Hello,
I've just wanted to know who already tried to install Lineage 17.1 on bardock(pro)?
I'm still on Lineage 16 and a little bit afraid to change in such early state.
What are you experience?
Especially with TWRP an Lineage 17.1?
Let me know...
Click to expand...
Click to collapse
I installed yesterday on regular Aquaris X and it couldn't detect the SIM card. It was actually the first time I installed LOS or any custom ROM on this phone (I've done it on other phones) so I was afraid I did something wrong, but I just installed 16 and it works fine. So... avoid for now I guess
very well ... we have an open thread for this topic in which we talk about our experiences with this rom that I can already tell you is going very well.
https://www.htcmania.com/showthread.php?t=1546131
---------- Post added at 06:24 PM ---------- Previous post was at 06:20 PM ----------
Sorry for not putting concrete data because I do not speak English and I go with the translator and it is a lot of work.
rikysub said:
very well ... we have an open thread for this topic in which we talk about our experiences with this rom that I can already tell you is going very well.
https://www.htcmania.com/showthread.php?t=1546131
---------- Post added at 06:24 PM ---------- Previous post was at 06:20 PM ----------
Sorry for not putting concrete data because I do not speak English and I go with the translator and it is a lot of work.
Click to expand...
Click to collapse
Thank you for the info.
But unfortunately I do not speak Spanish and the google translator does not work very well.
So if anybody of you got experience with LOS 17.1 and Aquaris X (Pro) please share your experience.
Xtaner said:
Thank you for the info.
But unfortunately I do not speak Spanish and the google translator does not work very well.
So if anybody of you got experience with LOS 17.1 and Aquaris X (Pro) please share your experience.
Click to expand...
Click to collapse
I went in there to ask about my problem, people with Pro are saying it is working fine.
Can't get any feedback on regular Aquaris X though...
Xtaner said:
Thank you for the info.
But unfortunately I do not speak Spanish and the google translator does not work very well.
So if anybody of you got experience with LOS 17.1 and Aquaris X (Pro) please share your experience.
Click to expand...
Click to collapse
For me it works good so far, everything except the HW-Overlay. I have to disable it to prevent severe screen tearing in 3D apps.
Unfortunately I have no idea how to contact the developer Quallenauge to report this issue.
I've just flashed
lineage-17.1-20200620-nightly-bardockpro-signed.zip
[Magisk, no GAPPS]
Here are some bugs I've found:
- LTE+ is not working anymore
- Some translation is still missing
I will keep you up with informations. But so far its working good.
Media sound output through the speaker fails from time to time and a reboot fixes it. SafetyNet fails (CTS profile). Beside that, quite stable at the moment.
I've just flashed
lineage-17.1-20200725-nightly-bardockpro-signed.zip
[Magisk, no GAPPS]
Here are some bugs I've found:
- LTE+ is not working
- Some translation is still missing
- Media sound output through the speaker fails from time to time (thx to grisu59964)
- Timer is not working probably. Sometimes the start or stop button is missing
- Calender widget is missing
Justed flashed:
lineage-17.1-20201003-nightly-bardockpro-signed.zip
[Magisk, no GAPPS]
Working great so far.
Here are some bugs I've found:
- LTE+ is not working
- GPS is not working if screen is not active
Xtaner said:
Justed flashed:
lineage-17.1-20201003-nightly-bardockpro-signed.zip
[Magisk, no GAPPS]
Working great so far.
Here are some bugs I've found:
- LTE+ is not working
- GPS is not working if screen is not active
Click to expand...
Click to collapse
- LTE+ is working for me.
- I have also not experienced issues with GPS and inactive screen.
And if someone want to contact the developers directly, send me a pm for a link or search for "aquaris-dev". (I have not the post count to link them directly here! ^^)
sonriab said:
- LTE+ is working for me.
- I have also not experienced issues with GPS and inactive screen.
And if someone want to contact the developers directly, send me a pm for a link or search for "aquaris-dev". (I have not the post count to link them directly here! ^^)
Click to expand...
Click to collapse
Thx man!
It seems that my phone got some problem.
Maybe its about Afwall or the firmware.
I've just flashed: lineage-17.1-20201024-nightly-bardockpro-signed.zip
And now the phone randomly reboot.
And when I'm calling someone with the german carrier O2 after 5-10 minutes, the call is terminated and all connections get lost for one second.
Then everything comes back again.
Xtaner said:
It seems that my phone got some problem.
Maybe its about Afwall or the firmware.
I've just flashed: lineage-17.1-20201024-nightly-bardockpro-signed.zip
And now the phone randomly reboot.
And when I'm calling someone with the german carrier O2 after 5-10 minutes, the call is terminated and all connections get lost for one second.
Then everything comes back again.
Click to expand...
Click to collapse
Hi,
yep, I faced exactly the same:
I have flashed the same ZIP and my phone started to reboot randomly.
I hope it is a bug in the build, I'll try one of the recent builds. Lets see and hope.
Hi, I've got the same problem with interruption of phone calls after 5-20 minutes with Vodafone an Telekom as well. The connection is lost for one second on SIM 1 and tested also on SIM 2. The problem exists since about 3-4 months. I' ve updated Lineage 17.1 almost every weekend, but the problem still exists. I reported the bug already 2 weeks ago on GitLab, but no one of the developers read the report so far ... The phone also reboots randomly, mainly while using internet functions as mentioned in the previous post. The phone is still great, so I hope those things will be fixed.
I have re-installed it using lineage-17.1-20201114-nightly-bardockpro-signed.
No reboot loop anymore.
Updated to a newer build, still ok.
Walter LinOS rookie said:
I have re-installed it using lineage-17.1-20201114-nightly-bardockpro-signed.
No reboot loop anymore.
Updated to a newer build, still ok.
Click to expand...
Click to collapse
I had problems with this version as well... Do you have also the mentioned problems with interruption of phone calls?
---------- Post added at 06:12 PM ---------- Previous post was at 06:08 PM ----------
Xtaner said:
Thx man!
It seems that my phone got some problem.
Maybe its about Afwall or the firmware.
I've just flashed: lineage-17.1-20201024-nightly-bardockpro-signed.zip
And now the phone randomly reboot.
And when I'm calling someone with the german carrier O2 after 5-10 minutes, the call is terminated and all connections get lost for one second.
Then everything comes back again.
Click to expand...
Click to collapse
Hey, could you solve the problem with the interruption of phone calls?
danemyte said:
I had problems with this version as well... Do you have also the mentioned problems with interruption of phone calls?
---------- Post added at 06:12 PM ---------- Previous post was at 06:08 PM ----------
Hey, could you solve the problem with the interruption of phone calls?
Click to expand...
Click to collapse
Hey!
No,the problem is still present.
It's totaly random.
Sometimes it appears after 1 min., sometimes after 20 min.
Maybe some problem with the old baseband firmware ? I don't know.
Xtaner said:
Hey!
No,the problem is still present.
It's totaly random.
Sometimes it appears after 1 min., sometimes after 20 min.
Maybe some problem with the old baseband firmware ? I don't know.
Click to expand...
Click to collapse
Hi, my phone calls get interrupted randomly as well. Running 17.1-20201219-NIGHTLY-bardockpro. I read @danemyte 's gitlab issue. I don't know if my contacts put down the receiver too quickly but mine didn't seem to try and re-establish the connection after a moment. All I could do was redial. It happens in about every phone call, it happened 3 times in a 45 minutes call.
All the rest works well without any issues and I am still really happy with the phone so I also hope it will be fixed. Can I provide any helpful information? My log looks quite cluttered with information. Do you apply any filters before posting logs?
kteatime said:
Hi, my phone calls get interrupted randomly as well. Running 17.1-20201219-NIGHTLY-bardockpro. I read @danemyte 's gitlab issue. I don't know if my contacts put down the receiver too quickly but mine didn't seem to try and re-establish the connection after a moment. All I could do was redial. It happens in about every phone call, it happened 3 times in a 45 minutes call.
All the rest works well without any issues and I am still really happy with the phone so I also hope it will be fixed. Can I provide any helpful information? My log looks quite cluttered with information. Do you apply any filters before posting logs?
Click to expand...
Click to collapse
Hi, I also have to redial the contact after the connection interrupts. I also don't know how to filter the log. I wished someone one Gitlab would read the issue and could work on it. I'm also happy with the phone. Anyway, from time to time it reboots randomly, but it's getting better after every update.
Dear All, I send an Email with an request to solve the problem to some developers/reviewers directly per mail, which are named here: https://review.lineageos.org/c/LineageOS/android_lineage-sdk/+/298359/