Related
Has anyone tried Ingress with the M8 yet. I'm curious how the GPS performs with all the metal in this phone.
InfinitiGuy said:
Has anyone tried Ingress with the M8 yet. I'm curious how the GPS performs with all the metal in this phone.
Click to expand...
Click to collapse
No issues here. The GPS really shouldn't be any different for ingress than other apps. Though the ingress compass appears permanently broken. Other apps have no problem with the compass but ingress can't get it right no matter what I do.
InfinitiGuy said:
Has anyone tried Ingress with the M8 yet. I'm curious how the GPS performs with all the metal in this phone.
Click to expand...
Click to collapse
I have no issues at all, not even with the compass. I feel like its not using the right drawables, buttons and other UI elements seem oversized but GPS, etc. work great.
Edit: The LTE coverage around here is great and I don't have to deal with the drop-back to 3G (which basically kills ingress) like I had to with the One S. That, plus the slightly larger battery makes this a much better Ingress phone than my old one.
Turn the back of the phone to the sky!
l7777 said:
No issues here. The GPS really shouldn't be any different for ingress than other apps. Though the ingress compass appears permanently broken. Other apps have no problem with the compass but ingress can't get it right no matter what I do.
Click to expand...
Click to collapse
I got the compass to work with the m8 in Ingress! All you have to do is point the back of the phone directly up. After trying that orientation I tried some others and as it turns out, landscape works too. Keep in mind for all of these *working* orientations, the top of the phone is your direction vector.
I doubt anyone will play by walking around with their m8 turned screen down (and walking backwards), but the landscape orientations might help
are you all having any issues with Ingress after 1.54?
I can't see myself anymore. The arrow and circle are both gone.
yakayu said:
are you all having any issues with Ingress after 1.54?
I can't see myself anymore. The arrow and circle are both gone.
Click to expand...
Click to collapse
That happens randomly on every device once in a while. My M8 works awesome for Ingress. Great GPS & LTE & my compass work perfectly in any orientation. With Flar2's ElementalX & a couple of tweaks, I get 5+ of Ingress screen on time.
BTW, that issue I've never had on the M8, but N7 & N5. A wipe of cache & dalvik with a reboot usually fixes it.
yakayu said:
are you all having any issues with Ingress after 1.54?
I can't see myself anymore. The arrow and circle are both gone.
Click to expand...
Click to collapse
Make sure you do a full power down of the phone (Turn off Fast boot in the Power menu) and bring it back up. I only see this issue when I switch SIM cards and doing a full power off fixes it for me.
app restart while opening media files and passcodes
Hey guys,
I'm having issues when trying to open media files or submitting passcodes.
The app restarts to scanner. Tried several things: set chrome to default browser, made sure YouTube is working, but nothing seems to do the trick.
Have a rooted M8, almost stock Rom..
Anyone ideas what problem might be ?
akanninga said:
Hey guys,
I'm having issues when trying to open media files or submitting passcodes.
The app restarts to scanner. Tried several things: set chrome to default browser, made sure YouTube is working, but nothing seems to do the trick.
Have a rooted M8, almost stock Rom..
Anyone ideas what problem might be ?
Click to expand...
Click to collapse
Mine is stock non-rooted. No issues here.
Hey people,
my OnePlus 3 loses much energy (up to 3 percent in 5 Minutes) if it’s inside my pocket (!) - especially then if I move at the same time.
I have already disabled the gesture functions - however, the problem remains.
Actually the problem can only be reproduced in my pockets
- latest Stock-ROM
- no root or other deep system changes
Any ideas how to narrow down this issue?
Best Regards,
Chris
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
Well me getting same problem.. still not figured out issue.
Sent from my ONEPLUS A3003 using Tapatalk
dont use it as your pocket vibrator then...
have you checked the smart lock? it can keep your phone unlocked while you carry it.
Hastaloego said:
dont use it as your pocket vibrator then...
have you checked the smart lock? it can keep your phone unlocked while you carry it.
Click to expand...
Click to collapse
Hahaa ;p
well, smart lock is not active in my phone...
Does it only happen when the screen / fingerprint scanner are against your body? Maybe they are detecting skin through your clothes and constantly trying to do something?
binners said:
Does it only happen when the screen / fingerprint scanner are against your body? Maybe they are detecting skin through your clothes and constantly trying to do something?
Click to expand...
Click to collapse
This. I think this is causing the issue. If you are slightly warm/damp/moist (someone reading hates that word ), it will try and scan your leg. My guess is perhaps it's not checking the ambient/proximity sensor to see if it's in the pocket or not.
I had this issue on the OnePlus 2 as well, although not as bad.
binners said:
Does it only happen when the screen / fingerprint scanner are against your body? Maybe they are detecting skin through your clothes and constantly trying to do something?
Click to expand...
Click to collapse
thebcooper said:
This. I think this is causing the issue. If you are slightly warm/damp/moist (someone reading hates that word ), it will try and scan your leg. My guess is perhaps it's not checking the ambient/proximity sensor to see if it's in the pocket or not.
I had this issue on the OnePlus 2 as well, although not as bad.
Click to expand...
Click to collapse
Thanks guys!
I'll try to wear the phone outward inside my pocket to see whether the problem still occurs.
Btw, i did some tests via "GSam Battery Monitor" and figured out the main-process which is producing the problem:
It's the "kernel". Does the kernel controls one of the mentioned sensors (ambient/proximity sensor) ?
MagDag said:
Thanks guys!
I'll try to wear the phone outward inside my pocket to see whether the problem still occurs.
Btw, i did some tests via "GSam Battery Monitor" and figured out the main-process which is producing the problem:
It's the "kernel". Does the kernel controls one of the mentioned sensors (ambient/proximity sensor) ?
Click to expand...
Click to collapse
Just be more wary of the screen being knocked/bumped!
Yeah that handles hardware as far as I know (might also be under other processes if they use it too though)
Alright, thanks for your quick feedback.
I guess i will reset my phone now...
I'm pretty sure it's the fingerprint sensor. Really sad to see that OP3 has this issue too, this started happening to me on OP2 too after the marshmallow update. They made the fingerprint scanner much more sensitive, greatly improving it's speed but this started happening. The workaround is to keep the phone in your pocket screen facing outwards...
I have the same problem. It should be fixable via system update to not activate the fingerprint sensor while the proximity sensor detects something.
Or am i missing something here?
Same issue here
Same issue. It's kind sad that OP can't handle this to prevent waking up using proximity sensor like it happens with duoble tap. I hope that they will release an update soon.
Is there anything in settings called "pocket mode"?? a friend has a THL phone that has pocket mode which stops the phone from doing anything when it detects its in a pocket
Nope, I've searched whole settings and there no option like 'pocket mode'.
same issue and the screen is showing the message "too many attempts. try again later" i can't use my smartwatch because the phone make a call or sent a message it self in my pocket.
I've created an e-mail to support with issue describe. Will update thread while getting reply.
Yes this is a bad bug which OP need to fix asap.
So what's the solution to the problem, finally?
MagDag said:
Hey people,
my OnePlus 3 loses much energy (up to 3 percent in 5 Minutes) if it’s inside my pocket (!) - especially then if I move at the same time.
I have already disabled the gesture functions - however, the problem remains.
Actually the problem can only be reproduced in my pockets
- latest Stock-ROM
- no root or other deep system changes
Any ideas how to narrow down this issue?
Best Regards,
Chris
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
Click to expand...
Click to collapse
We simply keep the phone face up in our pockets? That seems like a quick fix we shouldn't have to live with...
ArjunRanaOO7 said:
We simply keep the phone face up in our pockets? That seems like a quick fix we shouldn't have to live with...
Click to expand...
Click to collapse
You would think that priority would be given to the proximity sensor. If triggered it would disable the finger print input.
Hi guys.. I need some help..
I bought a 7t just 5 days back.. I didn't noticed it in the beginning but as I started using it more I noticed that there are black curves appearing on both lower side of screen at e of unlocking.. they first appear a bit bigger then reduce the size and then disappears..
But they don't appear always only few times particularly when I unlock it after sometime.. I think of it as a defect as it doesn't look some animation or something but yes a bug maybe.. So I plan on replacing this device but before that I thought about taking expert advice here.. I could've gone to service centre as well but there are none of them in my state..
Plz help.. I am attaching a pic here from the video cuz I was unable to upload mp4 file..
simplifieden said:
Hi guys.. I need some help..
I bought a 7t just 5 days back.. I didn't noticed it in the beginning but as I started using it more I noticed that there are black curves appearing on both lower side of screen at e of unlocking.. they first appear a bit bigger then reduce the size and then disappears..
But they don't appear always only few times particularly when I unlock it after sometime.. I think of it as a defect as it doesn't look some animation or something but yes a bug maybe.. So I plan on replacing this device but before that I thought about taking expert advice here.. I could've gone to service centre as well but there are none of them in my state..
Plz help.. I am attaching a pic here from the video cuz I was unable to upload mp4 file..
Click to expand...
Click to collapse
That's the Google assistant short-cut button. Not an issue or a bug
vicky2131 said:
That's the Google assistant short-cut button. Not an issue or a bug
Click to expand...
Click to collapse
Hey, Thanks but I don't have Google assistant installed and even if it why do they appear only sometimes and then go away?
simplifieden said:
Hey, Thanks but I don't have Google assistant installed and even if it why do they appear only sometimes and then go away?
Click to expand...
Click to collapse
Google assistant is built into your phone. And what I think might be the reason for it to appear at times is that you haven't used that gesture and the phone is waiting for you to use that gesture ( its shown because it needs to let the user know that swipe from right or left corner will bring up the Google assistant)
I use my assistant regularly so it doesn't show me the gesture animation nowadays.
So I have a very weird issue and I'll try to explain the best I can;
For some reason, ever since the S10+ I've had issues with Samsung phones, I think its something to do with the proximity sensor that's now under the glass, I'll explain as I'm getting similar and more issues on my S20 Ultra.
So last year when I had an S10+ and when I was on a call, which I mainly use my left ear (I think my right ear is a few db less so I use my left) I would quite frequently seem to activate the menu (top right) and therefore end up pressing things with my ear, unbeknown to me, sometimes I'd add a 2nd person to the call or simply put the other person on hold! This happened a lot and I was close to sending it off for repair even though I used apps to test to ensure the proximity sensor was working correctly but in the end, I sold it and got an OnePlus 7 Pro, which I didn't have an issue with. During my time with the S10+ I noticed that even though I held the earpiece to my ear I could see the screen light up and that's where I think I'd end up pressing the screen accidentally as I've just explained.
Roll on to now where I'm facing similar issues but also I'm finding if I need both of my hands and therefore use my left shoulder to keep my phone against my ear the call disconnects as if I'm hanging up. Now it seems a straightforward resolution which is not to do that but I've never had this issue before and I've tested it out quite a bit when I do this the screen isn't on and my face is nowhere near the end button!! It's really driving me crazy at the moment and annoying my other half who's normally on the phone to me when this happens!!
Anyone got any suggestions or thoughts, does it happen to anyone else or am I just being stupid??
I haven't gone down the route of resetting the phone yet but I'm going to consider it.
T.I.A
Hi..don't have such an issue, but when i talk with someone longer, i turn off the screen with the Power button and so it stays the whole time black during call....
S20U-Exynos
Xode said:
Hi..don't have such an issue, but when i talk with someone longer, i turn off the screen with the Power button and so it stays the whole time black during call....
S20U-Exynos
Click to expand...
Click to collapse
I did that the other day, however, when I moved the screen away I saw it light back up....
maverick1103 said:
I did that the other day, however, when I moved the screen away I saw it light back up....
Click to expand...
Click to collapse
Yeah,weird a bit, try to go into the secure lock screen settings and do as i did...maybe it helps ..... like i wrote before, my screen stays black whatever i do while i talk...
View attachment 5012913
S20U-Exynos
Xode said:
Yeah,weird a bit, try to go into the secure lock screen settings and do as i did...maybe it helps ..... like i wrote before, my screen stays black whatever i do while i talk...
S20U-Exynos
Click to expand...
Click to collapse
Thanks, I've already got that enabled, will just have a play around.
maverick1103 said:
Thanks, I've already got that enabled, will just have a play around.
Click to expand...
Click to collapse
Hi , do you make it work? I have the same problem with my Samsung A71, I have been using all kinds of apps a no one make it work.
Sent from my [device_name] using XDA-Developers Legacy app
vrgolin said:
Hi , do you make it work? I have the same problem with my Samsung A71, I have been using all kinds of apps a no one make it work.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Not yet, still having issues.
Any time the screen turns off and I turn it back on, I have to wait 30 seconds to a minute before the touch screen is responsive at all. I've tried using my fingerprint or removing all screen security and that doesn't seem to make a difference. Has anyone else run into a similar issue? Any idea on how to fix it?
zebinadams said:
Any time the screen turns off and I turn it back on, I have to wait 30 seconds to a minute before the touch screen is responsive at all. I've tried using my fingerprint or removing all screen security and that doesn't seem to make a difference. Has anyone else run into a similar issue? Any idea on how to fix it?
Click to expand...
Click to collapse
What android version are you running? Do you have many apps installed? Have you tried restoring back to factory defaults?
I believe it started after upgrading to 9 manually a few weeks ago. But I've tried a few different ROMs with the same situation. I have not rolled back to 8 to test that yet. It happens right out of the gate without installing any additional apps as well. I've done multiple full wipes, including unlocking the bootloader that for sure wiped everything with no change to the situation.
zebinadams said:
I believe it started after upgrading to 9 manually a few weeks ago. But I've tried a few different ROMs with the same situation. I have not rolled back to 8 to test that yet. It happens right out of the gate without installing any additional apps as well. I've done multiple full wipes, including unlocking the bootloader that for sure wiped everything with no change to the situation.
Click to expand...
Click to collapse
Fastboot upgrade? If not, i'd download 9 stock RETAIL and just flash it all with fastboot
Ok, I'll try that when I get a chance. we'll see if it works.
marcost22 said:
Fastboot upgrade? If not, i'd download 9 stock RETAIL and just flash it all with fastboot
Click to expand...
Click to collapse
I just re-flashed via fastboot 9 stock RETAIL found here. Looks like I'm still having the same issue as before with the touch screen not being responsive after turning the screen back on. Even if it's only been off for half a second, it will still not be responsive for a minute
Any further ideas? Or is there a better location to get the RETAIL image for XT1710-01?
zebinadams said:
I just re-flashed via fastboot 9 stock RETAIL found here. Looks like I'm still having the same issue as before with the touch screen not being responsive after turning the screen back on. Even if it's only been off for half a second, it will still not be responsive for a minute
Any further ideas? Or is there a better location to get the RETAIL image for XT1710-01?
Click to expand...
Click to collapse
This is gonna sound weird, but have you changed your screen at all?
marcost22 said:
This is gonna sound weird, but have you changed your screen at all?
Click to expand...
Click to collapse
Actually, yes. Just after getting the phone, it was dropped and the screen had to be replaced. The fingerprint sensor has been loose ever since then too. But this was never an issue until flashing a new ROM
zebinadams said:
Actually, yes. Just after getting the phone, it was dropped and the screen had to be replaced. The fingerprint sensor has been loose ever since then too. But this was never an issue until flashing a new ROM
Click to expand...
Click to collapse
did you have someone else replace your screen? If so, and it might sound weird, they might have installed an LCD screen instead of OLED; and then modified the stock rom for that. You might not know, but OLED and LCD have very different power profiles, so when turning LCD on you can just blast it, meanwhile oled you need to slowly bring the power up. This is what might be causing your issues
marcost22 said:
did you have someone else replace your screen? If so, and it might sound weird, they might have installed an LCD screen instead of OLED; and then modified the stock rom for that. You might not know, but OLED and LCD have very different power profiles, so when turning LCD on you can just blast it, meanwhile oled you need to slowly bring the power up. This is what might be causing your issues
Click to expand...
Click to collapse
Yeah, I had someone else install the screen for me. How would I go about checking if its LCD vs OLED? And do you know what would need to be modified in order to fix it if it is LCD?
zebinadams said:
Yeah, I had someone else install the screen for me. How would I go about checking if its LCD vs OLED? And do you know what would need to be modified in order to fix it if it is LCD?
Click to expand...
Click to collapse
You would need to remove the screen. Otherwise you can use something like AOD and check if the whole display lights up vs only the clock or whatever. On an LCD screen the whole display will light up a tiny bit vs complete black on OLED.
You would need to modifiy the dtb's and kernel, but it's something i would be able to do for you
marcost22 said:
You would need to remove the screen. Otherwise you can use something like AOD and check if the whole display lights up vs only the clock or whatever. On an LCD screen the whole display will light up a tiny bit vs complete black on OLED.
You would need to modifiy the dtb's and kernel, but it's something i would be able to do for you
Click to expand...
Click to collapse
It looks to me like OLED to me with only the clock lighting up. I could still take the screen off at some point to verify if needed.
Thanks for all of your help by the way
zebinadams said:
It looks to me like OLED to me with only the clock lighting up. I could still take the screen off at some point to verify if needed.
Thanks for all of your help by the way
Click to expand...
Click to collapse
I don't know if it's the reflection, but is there some bleed around the clock? Like is the dark areas lighter compared to the rest of the screen?
marcost22 said:
I don't know if it's the reflection, but is there some bleed around the clock? Like is the dark areas lighter compared to the rest of the screen?
Click to expand...
Click to collapse
I think it's just the reflection? Here's a shot of my Nexus 6p right beside it and I think they look basically the same.
The phone is used almost exclusively for kids videos so it's not the end of the world if I never get it fixed, but at the same time, it would alleviate some frustration when I'm helping my daughter turn a show on.
zebinadams said:
I think it's just the reflection? Here's a shot of my Nexus 6p right beside it and I think they look basically the same.
View attachment 5544389
The phone is used almost exclusively for kids videos so it's not the end of the world if I never get it fixed, but at the same time, it would alleviate some frustration when I'm helping my daughter turn a show on.
Click to expand...
Click to collapse
Yeah, to me it still looks significantly brighter around the clock
marcost22 said:
Yeah, to me it still looks significantly brighter around the clock
Click to expand...
Click to collapse
Ok, I'm willing to try modifying the ROM if that'll get rid of the stupid touch screen delay. How difficult is it? I know you said you would be willing to do it for me, but if it's not something that will persist through an update (I had been running AICP) and it's something that I could learn to do, all the better. If that's not realistic, that's fine as well.
zebinadams said:
Ok, I'm willing to try modifying the ROM if that'll get rid of the stupid touch screen delay. How difficult is it? I know you said you would be willing to do it for me, but if it's not something that will persist through an update (I had been running AICP) and it's something that I could learn to do, all the better. If that's not realistic, that's fine as well.
Click to expand...
Click to collapse
[REFERENCE] How to compile an Android kernel
Introduction Hello everyone, I will be going over how to compile a kernel from beginning to end! Prerequisites: A Linux environment (preferably 64-bit) Knowledge of how to navigate the command line Common sense A learning spirit, there will be...
forum.xda-developers.com
Is a great guide, you'd need to follow the clang guide tho, as our kernel IS clang-compiled, and i recommend repacking the boot.img
You'd need to change this line
kernel_motorola_msm8953/msm8953-albus.dtsi at 7befedacd91b84ed737b691671c088c89e394f66 · AICP/kernel_motorola_msm8953
Contribute to AICP/kernel_motorola_msm8953 development by creating an account on GitHub.
github.com
In your source to be
qpnp,qpnp-labibb-mode = "lcd";
If i'm right, after doing that and flashing it the issue will be fixed. Otherwise when you try to turn on the display it will cause a kernel panic
You would need to reflash this boot.img after every update, and redownload sources everytime i do something to kernel.