Related
After upgrading to mango(and performing a reset to use my fancy new SD card) i am no longer able to enable auto dim. Every time I try, it just disables itself. I can manually set the brightness options but just can't get auto dim to work.
Have you guys run into this?
Weird, that shouldn't happen.
You can try another hard reset (from settings).
That's what support was saying, but I don't want to re-install everything again.
I am having the same issue post mango day firmware update. I am also having an issue with the proximity sensor not working. Hard reset did not correct either.
Sent from my SGH-i917 using XDA Windows Phone 7 App
I´m having the same issue, please right in microsoft answers page (the are some posts about that but I cant add the link) so we can find a solution or call microsoft attention
---------- Post added at 09:06 PM ---------- Previous post was at 08:20 PM ----------
Do you guys think this could be fix by the registry editor????
After I upgraded my Focus to Mango, I still have auto dimm.
Just tried a hard reset still not working. Do you guys have SD Cards?
Hey people, not sure if i'm the only s5 user whose experiencing this but sometimes when i wake my phone up, the touch capacitive buttons do light up but the screen stays black. any idea why?
snazer said:
Hey people, not sure if i'm the only s5 user whose experiencing this but sometimes when i wake my phone up, the touch capacitive buttons do light up but the screen stays black. any idea why?
Click to expand...
Click to collapse
I would reflash the stock rom you have atm and data factory reset afterwards or try a data factory reset first and see if that fixes your issue.
Known bug. Supposedly fixed in recent firmware updates. More details in existing threads.
Or simply circumvent the issue entirely by upgrading to a good third party screen saver.
If you're ambitious, you could also try the following edit, which may help.
Make a backup first, then try editing build.prop
Code:
mot.proximity.delay=0
ro.lge.proximity.delay=25
.
gee2012 said:
I would reflash the stock rom you have atm and data factory reset afterwards or try a data factory reset first and see if that fixes your issue.
Click to expand...
Click to collapse
I have tried factory resetting my phone but it doesnt help. Thanks anyways
fffft said:
Known bug. Supposedly fixed in recent firmware updates. More details in existing threads.
Or simply circumvent the issue entirely by upgrading to a good third party screen saver.
If you're ambitious, you could also try the following edit, which may help.
Make a backup first, then try editing build.prop
Code:
mot.proximity.delay=0
ro.lge.proximity.delay=25
I have added mot.proximity.delay=0 but i couldnt find ro.lge.proximity.delay=25. Is there any other way to fix this problem. I have to pull my battery out couple of times a day and its starting to get to me.
.
Click to expand...
Click to collapse
and now my mulitasking buttons are not working. any idea why?
snazer said:
Hey people, not sure if i'm the only s5 user whose experiencing this but sometimes when i wake my phone up, the touch capacitive buttons do light up but the screen stays black. any idea why?
Click to expand...
Click to collapse
I have the same issue... do you still get this issue? For me, sometimes, the screen does not wake up only the capacitive keys... I have to press the power button again to turn it off and then press power again to turn it on.
me too
Hi,
I'm having the same problem.
It was intermittent for a short while and a battery pull would fix it, now it's permanent.
I get capacitive buttons, I can boot into recovery or download.
I can hear touches on the screen and the annoying at$t boot sound is back since I used Odin to reflash to stock.
I think I have to take this phone to a service center and see if they will exchange it.
I'm worried that there may be traces of towelroot but from the thread that provides stock firmware and instructions for Odin it would seem that I'm good.
Has anyone had any luck with this issue or have any other tips to try?
I'm bummed because I just applied a glass protector and it looks like I'll have to get another.
Not to mention having to drive to the center.
Thanks.
With the new 1.100 motherboard version the problem is solved. It's a hardware defect. Maybe it will be fixed in next fw versions with some voltage or timing setting changes but a mobo change will definitely solve it.
For the record:
The at$t service center reflashed my phone and the screen works again.
IDK why flashing stock with odin did not work for me.
I can see from the post above mine that the problem might come back, I'll insist on a replacement if it does.
still getting the issue but for me I just need to press power 3 times for it to wake up; no need to remove battery
---------- Post added at 06:05 PM ---------- Previous post was at 06:03 PM ----------
Levus said:
With the new 1.100 motherboard version the problem is solved. It's a hardware defect. Maybe it will be fixed in next fw versions with some voltage or timing setting changes but a mobo change will definitely solve it.
Click to expand...
Click to collapse
how can i find out what mobo I have?
---------- Post added at 06:51 PM ---------- Previous post was at 06:05 PM ----------
fffft said:
Known bug. Supposedly fixed in recent firmware updates. More details in existing threads.
Or simply circumvent the issue entirely by upgrading to a good third party screen saver.
If you're ambitious, you could also try the following edit, which may help.
Make a backup first, then try editing build.prop
Code:
mot.proximity.delay=0
ro.lge.proximity.delay=25
.
Click to expand...
Click to collapse
just rooted going to try this one thx
You can use the samsung phone info app from the market...
I haven't solved this issue as well... Please,did anyone of u guys solve this problem? If u did,please,tell me what to do... My screen stays black,only capacitive buttons lights,and I must press power button 5,6 times to wake up the screen. It's really annoying... :/
No solutions yet ???? I have this problem too...
walidhiphop said:
No solutions yet ???? I have this problem too...
Click to expand...
Click to collapse
It is lollipop 5.0 memory leak bug!
Also on CM12 (based on lollipop 5.0.2) problem occurs sometimes.
qubbus said:
It is lollipop 5.0 memory leak bug!
Also on CM12 (based on lollipop 5.0.2) problem occurs sometimes.
Click to expand...
Click to collapse
I'm having issue even using Kitkat 4.4.2
ZaKaTRoN said:
I'm having issue even using Kitkat 4.4.2
Click to expand...
Click to collapse
I also have the same problem, after lots of struggling I found little solution (it worked for me...), Just disable ur S-Health App, this app cause blank screen issue(this app uses sensors). Respond here if it worked for you.
knightrider558 said:
I also have the same problem, after lots of struggling I found little solution (it worked for me...), Just disable ur S-Health App, this app cause blank screen issue(this app uses sensors). Respond here if it worked for you.
Click to expand...
Click to collapse
Thanks for your reply, but it didn't work.
No problem, tomorrow i'm buying s6, Phone House give me 210€ for my s5.
ZaKaTRoN said:
Thanks for your reply, but it didn't work.
No problem, tomorrow i'm buying s6, Phone House give me 210€ for my s5.
Click to expand...
Click to collapse
Great decision just get rid of these sam devices -_- , last try did you change the runtime system?
knightrider558 said:
Great decision just get rid of these sam devices -_- , last try did you change the runtime system?
Click to expand...
Click to collapse
I have upgrade every new software phe (spain), even lastest btu (united kingdom) because is newer than phe.
Also i sent twice to technical service.
One more time... I hate my s5!!!, hehe.
ZaKaTRoN said:
I have upgrade every new software phe (spain), even lastest btu (united kingdom) because is newer than phe.
Also i sent twice to technical service.
One more time... I hate my s5!!!, hehe.
Click to expand...
Click to collapse
hahah... but this solution worked for me
I can't seem to find an answer...I tried posting on the JDC Team thread but it goes so fast, I think it has been passed over.
I am having a problem with Bluetooth. Within the last couple days (not sure when it actually happened) I can no longer activate the Bluetooth toggle. When I try it, it thinks for a second or two and then nothing...if I reboot and try and activate it, it moves to the on position but within 10 seconds it switches back off.
Is this a new problem? What is weird is on my wife's phone it is working fine. I am using the jflte version of the Optimized CM 12.1 by JDC Team..
If this is a known problem, please advise what I can do to fix as I want to be able to use the Bluetooth in the car.
Thanks in advance.
melon2112 said:
I can't seem to find an answer...I tried posting on the JDC Team thread but it goes so fast, I think it has been passed over.
I am having a problem with Bluetooth. Within the last couple days (not sure when it actually happened) I can no longer activate the Bluetooth toggle. When I try it, it thinks for a second or two and then nothing...if I reboot and try and activate it, it moves to the on position but within 10 seconds it switches back off.
Is this a new problem? What is weird is on my wife's phone it is working fine. I am using the jflte version of the Optimized CM 12.1 by JDC Team..
If this is a known problem, please advise what I can do to fix as I want to be able to use the Bluetooth in the car.
Thanks in advance.
Click to expand...
Click to collapse
Probably hardware failure.
Lennyz1988 said:
Probably hardware failure.
Click to expand...
Click to collapse
I don't think so. My bluetooth was perfect and fine with touchwiz 4.4.2 GNG8 rom. Now with CM12.1 "optimized" is not usable at all.
I still need to find any alternative rom because it's a big issue for me.
---------- Post added at 11:08 PM ---------- Previous post was at 10:40 PM ----------
I reasearched a bit on this topic.
I flashed XXUHOD7 bootloader and modem and now bluetooth it's not crashing anymore:
http://forum.xda-developers.com/showpost.php?p=50965837&postcount=2627
I'll try it with my helmet headset tomorrow and I'll let you know.
Did you fix your Bluetooth with the new bootloader and modem?
Bluetooth issue
fear_factory84 said:
I don't think so. My bluetooth was perfect and fine with touchwiz 4.4.2 GNG8 rom. Now with CM12.1 "optimized" is not usable at all.
I still need to find any alternative rom because it's a big issue for me.
---------- Post added at 11:08 PM ---------- Previous post was at 10:40 PM ----------
I reasearched a bit on this topic.
I flashed XXUHOD7 bootloader and modem and now bluetooth it's not crashing anymore:
http://forum.xda-developers.com/showpost.php?p=50965837&postcount=2627
I'll try it with my helmet headset tomorrow and I'll let you know.
Click to expand...
Click to collapse
thank you, I did the modem flash and my problems with Bluettoth simply gone. Thank you so much.
melon2112 said:
I can't seem to find an answer...I tried posting on the JDC Team thread but it goes so fast, I think it has been passed over.
I am having a problem with Bluetooth. Within the last couple days (not sure when it actually happened) I can no longer activate the Bluetooth toggle. When I try it, it thinks for a second or two and then nothing...if I reboot and try and activate it, it moves to the on position but within 10 seconds it switches back off.
Is this a new problem? What is weird is on my wife's phone it is working fine. I am using the jflte version of the Optimized CM 12.1 by JDC Team..
If this is a known problem, please advise what I can do to fix as I want to be able to use the Bluetooth in the car.
Thanks in advance.
Click to expand...
Click to collapse
I had a similar problem where I would try and turn on my bluetooth, and it would immediately switch off, almost like it couldn't find the hardware.
I fixed it by disabling System Profiles in Settings. The currently active profile said "turn bluetooth off", which I think was disabling it. Rebooted with no profiles and bluetooth seems to be fine.
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/
Hi guys. I have a problem with the fingerprint reader. I am running microg (19-20221204-microG-fajita) which is build on lineageos 19.1. Here are the symptoms.
After each OTA update and after each restart, fingerprint simply stops to work, so I need to use PIN instead to unlock the phone. And I need to delete the actual fingerprint (as it simply stops to work) and add a new fingerprint.
When adding a new fingerprint, first 4 readings (I mean while adding it) go OK. Then on 5th, it stops to recognize my finger, need to wait approximately 10-15 seconds (I can keep touching the reader or just wait, doesn't matter) and then it starts to be responsive again and I am able to finish the addition of a new fingerprint. This is consistent, happens each time when I am adding a new fingerprint.
After adding a new fingerprint, in 99,9% of times, I cannot use it as the phone does not recognize my freshly added fingerprint.
This last comment is pretty tricky. After some time (seems random, cannot tell what it depends on) and only some times, it simply starts to work. When it starts to work, it keeps working consistently until the next OTA or restart.
Tried to google, tried to asked for a help in a kind of similar bug report (https://gitlab.com/LineageOS/issues/android/-/issues/4642). No luck. Can you direct me, what the issue could be? Thank you.
If you still got the problem i might have a solution for you. So reply to this comment.
bilered said:
If you still got the problem i might have a solution for you. So reply to this comment.
Click to expand...
Click to collapse
Hi, no progress with this issue. And I am not the only one, another user wrote in another thread about the same problem. So any advice would be appreciated.
ivanovic2 said:
Hi, no progress with this issue. And I am not the only one, another user wrote in another thread about the same problem. So any advice would be appreciated.
Click to expand...
Click to collapse
Okay so if you got telegram then add me @bilered It'll be better to help you though with it
I only have trouble with the fingerprint sensor while using extra dim mode.