Database Users

Camera failed warning

Just to let you all know who are curious as to who is experiencing this fault, i have just recieved the dreaded warning. got my phone 3 days ago from carphone warehouse in plymouth uk, unlocked. seems a pretty widespread fault. mass recall????:crying:

yes, if u read around is a hardware problem with limited S5, only fix atm is replace it.

Any info on which models you can get this problem?
I had similar error yesterday untill I rebooted my phone. Thought its problem with ART...

no, but i think it mostly from US Verizon.

Stiflerlv said:
Any info on which models you can get this problem?
I had similar error yesterday untill I rebooted my phone. Thought its problem with ART...
Click to expand...
Click to collapse
I'm on the G900F and occasionally get the camera failed warning. A reboot always fixes it.
Sent from my SM-G900F using XDA Free mobile app

plymptonpilgreen said:
Just to let you all know who are curious as to who is experiencing this fault, i have just recieved the dreaded warning. got my phone 3 days ago from carphone warehouse in plymouth uk, unlocked. seems a pretty widespread fault. mass recall????:crying:
Click to expand...
Click to collapse
Make sure you not set the phone in save model.
If you use the Go Flash Light App, unload it
If it still not work, you'd better send it to Samsung center for change.
Or you can try to boot the phone.

I had "Warning Camera Failed" problem on my SM-G900SW (S5 in Canada), along with some other weird problems.
After reading an announcement from Samsung that the problem is ROM related download the stack image for my device/provider from Samfirmware and re-flashed the phone.
The problem went away, and so did some other issues.
This is definitely a software issue IMO.

I've read that it only happens to US version of the phone when the user installs another camera app.

daoom said:
I had "Warning Camera Failed" problem on my SM-G900SW (S5 in Canada), along with some other weird problems.
After reading an announcement from Samsung that the problem is ROM related download the stack image for my device/provider from Samfirmware and re-flashed the phone.
The problem went away, and so did some other issues.
This is definitely a software issue IMO.
Click to expand...
Click to collapse
To add to this, after I flashed the stock firmware everything was fine for a few days until suddenly I was unable to turn on Bluetooth. So the camera still worked, but bluetooth stopped working.
I took the phone back to the store, showed them the problem and exchanged. In the process of exchanging it I did a factory reset to remove personal data. When the reset was done, I turned it on to make sure my accounts were gone, and lo and behold the camera and bluetooth worked again.
I still went through with the exchange since this does seem like a problem related to the storage memory becoming corrupted after a bit of use.
I've had the new one for 3 days, and so far no problems.
---------- Post added at 11:34 AM ---------- Previous post was at 11:33 AM ----------
jopat said:
I've read that it only happens to US version of the phone when the user installs another camera app.
Click to expand...
Click to collapse
Seeing as I'm Canadian, nope.

Fix for proximity sensor problem

I recently bought yureka and had a proximity sensor problem. It was always showing as distance zero.
Even when i made call screen immediately turned dark even while i was holding it into my hand.
Turns out its a loose screw. I tightened the screw which is behind the proximity sensor and it fixed my problem.
Before you do that you can test if this will work for you.
You can hold the are near your proximity sensor ( don't cover the sensor) and make a call. Make a call now. If the screen doesn't turns off automatically then loose screw is the problem with your device as well.
Hope this helped you as i saw too many posts with this problem.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Alternate solution
you can fold a small piece of paper(i am using spare sim card) and fold it few times and put it right between the back cover and proximity sensor.
whichever solution you use make sure to call the yureka customer care and report this problem and also get it fixed. as this might be temporary solution (or permanent, we will find out ) and the problem might come back.
report the problem and get the engineer to fix it. brand new phone should not have such problem.

MY proximity never works
It always shows 5.0 cm in cpuz or any other proximity sensor related app from play store.Phone screen never turns off during the call even if i place my phone on my face or ear piece.

kzrockz said:
It always shows 5.0 cm in cpuz or any other proximity sensor related app from play store.Phone screen never turns off during the call even if i place my phone on my face or ear piece.
Click to expand...
Click to collapse
My solution is for the people whose sensor is always shows 0cm. Mine was always showing 0cm. This fixed my problem.

Kapiljhajhria said:
My solution is for the people whose sensor is always shows 0cm. Mine was always showing 0cm. This fixed my problem.
Click to expand...
Click to collapse
Thanks so much kapil brother, you nailed the problem, your solution totally works, i was so worried about this problem and the solution is so simple.

My phone has same issue please review this !
after dialing a phone number and pressing the call button display goes to sleep preventing me from hanging up the call or activating loud speaker..ehh frankly i can't see anything until the other party if attended my call hangs up !
I tried to press the proximity sensor area with my hands sometimes this works and screen turns on. I have tried tightening the screw as above mentioned but it did not resolved the problem entirely but now i had to apply less force to the proximity sensor area to turn the screen back on.
PS: Pressing the power key during call does't work the screen blinks and stays in sleep mode . i've been using this brand new phone for only two days please tell me what to do.

Alternate solution worked for me .
Double sided tape with small piece of paper folded few times.

Updates are coming, Finally Some Customer Support Arrived !
Dear Amal ,
Thanks for emailing YU Support.
In response to your email, I would like to inform you that we have identified the issues with device and we will release an update in next couple of days to resolve this problem.
Further, we are planning to provide a build update soon to maximize the performance of the device.
We seek for kind understanding and cooperation..
I Hope the updates fixes the problem.
Decided to not RMA and wait for two weeks in tears:crying:
---------- Post added at 09:47 PM ---------- Previous post was at 09:31 PM ----------
Users are facing so many bugs on their Yureka, This is a compilation of those bugs with solution(possibly), this list is not in any particular order.
1. The camera app says cannot connect to the camera.
2. Camera records video in 15fps indoors and I can get 30fps only outdoors.*
3. Double-tap to Wake can't be turned off.
4. I downloaded (some) game/app and it does not works.
5. Screen goes black while calling.
6. Device keeps switching between 3G & 2G.
S. Dial *#*#4636#*#* from the phone dialer -> Open the 'Phone Information' option -> Scroll down to find 'Set preferred network type' and select the network mode you want ('WCDMA only' option for 3G).
7. Not able to access memory card through cm file manager/There is no copy/cut option.
8. Notification LED not working.
9. Wi-Fi gets disconnected.
10. I'm having network problems with a particular operator/at a particular place.
11. The animation seems really slow.
12. Google Play/Gmail/Youtube or any app from Google doesn't work over Wi-Fi.*
.13. Edit option in gallery doesn't work/It crashes.
14. Can't encrypt the phone.
15. I can't see the option to move apps to sd card.
16. I can't see names of the apps in drawer.
17. Device is rebooting constantly.
.18. Call divert doesn't work.
19. Not able to select ringtone for second sim.
20. I received a defective device.
Solution. Return it ASAP.
21. Phone over heats and battery drains too fast.
22. The earphone settings stay on even after removing earphone.
23. Camera images aren't so good.
24. Can't see sim contacts.
Cyanogen promises to fix most of these issues on coming updates.

amalmathewkutty said:
after dialing a phone number and pressing the call button display goes to sleep preventing me from hanging up the call or activating loud speaker..ehh frankly i can't see anything until the other party if attended my call hangs up !
I tried to press the proximity sensor area with my hands sometimes this works and screen turns on. I have tried tightening the screw as above mentioned but it did not resolved the problem entirely but now i had to apply less force to the proximity sensor area to turn the screen back on.
PS: Pressing the power key during call does't work the screen blinks and stays in sleep mode . i've been using this brand new phone for only two days please tell me what to do.
Click to expand...
Click to collapse
Try alternate solution.
amalmathewkutty said:
Dear Amal ,
Thanks for emailing YU Support.
In response to your email, I would like to inform you that we have identified the issues with device and we will release an update in next couple of days to resolve this problem.
Further, we are planning to provide a build update soon to maximize the performance of the device.
We seek for kind understanding and cooperation..
I Hope the updates fixes the problem.
Decided to not RMA and wait for two weeks in tears:crying:
---------- Post added at 09:47 PM ---------- Previous post was at 09:31 PM ----------
Users are facing so many bugs on their Yureka, This is a compilation of those bugs with solution(possibly), this list is not in any particular order.
1. The camera app says cannot connect to the camera.
2. Camera records video in 15fps indoors and I can get 30fps only outdoors.*
3. Double-tap to Wake can't be turned off.
4. I downloaded (some) game/app and it does not works.
5. Screen goes black while calling.
6. Device keeps switching between 3G & 2G.
S. Dial *#*#4636#*#* from the phone dialer -> Open the 'Phone Information' option -> Scroll down to find 'Set preferred network type' and select the network mode you want ('WCDMA only' option for 3G).
7. Not able to access memory card through cm file manager/There is no copy/cut option.
8. Notification LED not working.
9. Wi-Fi gets disconnected.
10. I'm having network problems with a particular operator/at a particular place.
11. The animation seems really slow.
12. Google Play/Gmail/Youtube or any app from Google doesn't work over Wi-Fi.*
.13. Edit option in gallery doesn't work/It crashes.
14. Can't encrypt the phone.
15. I can't see the option to move apps to sd card.
16. I can't see names of the apps in drawer.
17. Device is rebooting constantly.
.18. Call divert doesn't work.
19. Not able to select ringtone for second sim.
20. I received a defective device.
Solution. Return it ASAP.
21. Phone over heats and battery drains too fast.
22. The earphone settings stay on even after removing earphone.
23. Camera images aren't so good.
24. Can't see sim contacts.
Cyanogen promises to fix most of these issues on coming updates.
Click to expand...
Click to collapse
I don't face any of these bugs. All apps works fine even over wifi. Device heats only during heavy tasks and it cools immediately as well.
I am able to set ringtone for second sim.
There is copy and cut function in cm file manager app. Its sort of difficult to access. First time i used cm file manger i thought same thing.
Can access sim contacts.
Only problem i faced was proximity sensor and i fixed that myself

How did you fixed it? Can you post some pics of that ?
Kapiljhajhria said:
Try alternate solution.
I don't face any of these bugs. All apps works fine even over wifi. Device heats only during heavy tasks and it cools immediately as well.
I am able to set ringtone for second sim.
There is copy and cut function in cm file manager app. Its sort of difficult to access. First time i used cm file manger i thought same thing.
Can access sim contacts.
Only problem i faced was proximity sensor and i fixed that myself
Click to expand...
Click to collapse
Please help others by telling them how did you fixed the issue. If possible please post some pics.
Thanks in advance.

update soon?
Cyanogen promises to fix most of these issues on coming updates.[/QUOTE said:
Can we Really expect update that soon?
Click to expand...
Click to collapse

This is it!
Tightening Screws got me closer but the folded paper did it.
As for going to service center, I would prefer to disassemble and reassemble it myself rather than wait for 10-20 days for someone else to fix it

Ya i did the same thing. First i tighted all the screws and then put a small peice of 3M tape in between the back panem close to the camera.. Yureka !! Proximity issue fixed.
I hope update fixes all related problems including proximity.
My fellows at Cyanogen please hurry. Lol
Sent from my YUREKA using XDA Free mobile app

fix for proximity sensor problem
I was having the same problem of black screen during the call and found a solution on webtrickz.com. just paste the following keywords in Google search
YU yureka software update
Enter and you will find a thread from webtrickz for manually installing an update for YU yureka phone. Just follow the steps and install the update. That's it. All bugs gone.

Proximity Sensor & Dual SIM functionality Update OTA Released. (Official)
Go to Settings-about phone -check update-if its not showing any update info then Google webtricks update yureka and update my following the description on that website manually i updated myself and its working 100%.

Link to Yureka update post: http://webtrickz.com/how-to-manually-install-xnph05q-ota-update-on-yureka/

Hey Hiii all... If anybody has yu yureka and has the problem of Proximity sensor problem don't worry an update has given by company... I'm very impressed.. And Problems is too solved
Sent from my AO5510 using XDA Free mobile app

Yea the proximity issue was fixed in the update but i lost root privilege after the update ,anyone else faced this ?

knuckleduster said:
Yea the proximity issue was fixed in the update but i lost root privilege after the update ,anyone else faced this ?
Click to expand...
Click to collapse
Just flash supersu to restore root

Kapiljhajhria said:
Just flash supersu to restore root
Click to expand...
Click to collapse
Thanks for the reply ,but problem is that custom recovery is also removed ,and unable to flash super su with stock recovery ,and to update recovery by mobileuncles root is required ,dont want to backup data and then restore ,any way of doint it without media & data getting deleted?

knuckleduster said:
Thanks for the reply ,but problem is that custom recovery is also removed ,and unable to flash super su with stock recovery ,and to update recovery by mobileuncles root is required ,dont want to backup data and then restore ,any way of doint it without media & data getting deleted?
Click to expand...
Click to collapse
flash cutom recovery. using adb. flashing custom recovery should not wipe data. atleast it never did on my s3. even if used odin to do it.

Nougat 7.1.1 connectivity issues

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

Network Issue

Hey there guys! I've been facing a problem with the connectivity of one of my sim cards. At times, the range shown in one of the sim cards goes to zero no matter where you are and the only way to fix it is by rebooting or deactivating and later reactivating the sim. Is anyone else facing the same prob ? Did anyone have a solution for this?
I'm using 4gb variant with unrooted stock ROM and locked bootloader. Build .339
The issue is shown more often in sim with enhanced 4GLTE mode enabled. In my case it's idea but I've faced it even when I swapped the sim with airtel too.

I have seen this issue much in.339 patch

GliderZ said:
Hey there guys! I've been facing a problem with the connectivity of one of my sim cards. At times, the range shown in one of the sim cards goes to zero no matter where you are and the only way to fix it is by rebooting or deactivating and later reactivating the sim. Is anyone else facing the same prob ? Did anyone have a solution for this?
I'm using 4gb variant with unrooted stock ROM and locked bootloader. Build .339
The issue is shown more often in sim with enhanced 4GLTE mode enabled. In my case it's idea but I've faced it even when I swapped the sim with airtel too.
Click to expand...
Click to collapse
Bro same issues faced by you, me and thousands of other user . But still now Asus don't even accept this issue. So don't buy any other Asus phone in your life

Rommaster94 said:
Bro same issues faced by you, me and thousands of other user . But still now Asus don't even accept this issue. So don't buy any other Asus phone in your life
Click to expand...
Click to collapse
But still, considering everything else, I really love this phone. I'm quite satisfied by the specs it offers

gaurav.m3 said:
I have seen this issue much in.339 patch
Click to expand...
Click to collapse
Well it existed for me even b4 .339. Been there for a long time, not that far from the initial builds. Really unfortunate that a fix has not yet been found (at least that I know of)

I have net issue in 339

Welcome to the club. Those are some topic about on zentalk (the last in list is mine):
https://www.asus.com/zentalk/thread-256567-1-2.html
https://www.asus.com/zentalk/thread-242365-1-2.html
https://www.asus.com/zentalk/thread-255087-1-3.html
https://www.asus.com/zentalk/thread-251930-1-5.html
https://www.asus.com/zentalk/thread-236917-1-6.html
Try to open your, so they can ignore it like the others. The problem is worsend with .339. Now i also have problem in calling. Asus mod request to me the serial number, but after that the nothingness, as usual!

LineageOS 17.1 for Aquaris X / X Pro

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/