Related
Hi everyone, I've got this really weird NFC problem. I have of course searched all over the web and the xda but I haven't find any solutions.
In short,
The Android Beam works perfectly (I transferred some photos to and from a Galaxy S4 over to my One X -endeavoru) but the phone can't recognize tags.
I have tested with several NTAG203 and some other smart card I had laying around.
I installed paranoid android 3.65, 4BETA, CM11 Nightly but it still doesn't respond in the proximity of an NFC tag. The crazy thing is that I can still Beam stuff to and from the Galaxy S4!!!
Detailed story,
About a year ago I was testing the NFC scanner and it worked just fine; it was able to scan all sorts of tags but now nothing happens.
Last week I began working on an app that needs to scan tags in order to work. And it was then that I encountered this problem. At that time I had Sense 5 and hadn't root or done anything "special" to the phone. When I went over to the settings, I found that Beam settings had somehow disappeared. So I did a reboot then factory reset and data wipe but nothing worked. I thought that maybe there's some issue with the kernel so I unlocked the bootloader from htcdev.com, rooted the phone, and installed paranoid android 3.65. But not even that worked. I also tested with PA 4 beta and CM11 Nightly but it still didn't work.
Any help would be appreciated! :good:
Thanks!
Hi all,
I just installed LineageOS 15.1 on my Moto G5 XT1677. While my phone boots up fine, I am having an issue with the camera. It works in the camera app and in Whatsapp, I can use the cam in the messaging area. However, if I open the Whatsapp web section to scan the QR code, the image display is extremely slow and I am never able to get it to scan the code. Is this a known issue and if so, is there a fix for it? Please help as I didn't have this problem in OS 14.
Another issue I noticed which isn't a major problem is that once the location is enabled, the icon in the status bar doesn't go away even after the location is disabled.
Also did the location feature change in any way between 14 and 15.1? I was using a cab hailing app that used to work fine in 14 but in 15.1, it fails with an error that it is unable to access the location even though it is enabled. Any clarification on this would be welcome.
Thanks a lot and let me know if you need any more information.
aksnitd said:
Hi all,
I just installed LineageOS 15.1 on my Moto G5 XT1677. While my phone boots up fine, I am having an issue with the camera. It works in the camera app and in Whatsapp, I can use the cam in the messaging area. However, if I open the Whatsapp web section to scan the QR code, the image display is extremely slow and I am never able to get it to scan the code. Is this a known issue and if so, is there a fix for it? Please help as I didn't have this problem in OS 14.
Another issue I noticed which isn't a major problem is that once the location is enabled, the icon in the status bar doesn't go away even after the location is disabled.
Also did the location feature change in any way between 14 and 15.1? I was using a cab hailing app that used to work fine in 14 but in 15.1, it fails with an error that it is unable to access the location even though it is enabled. Any clarification on this would be welcome.
Thanks a lot and let me know if you need any more information.
Click to expand...
Click to collapse
Even there are some workarounds for the camera in Oreo and Pie CustomROMs, I don't think it will be ever fully fixed (mostly due to the missing blobs).
In the WhatsApp, use the split screen mode to scan the QR code.
Idk about your location issues as location was always working fine for me. However, did you set your location settings to "High accuracy"?
Andrej_SK said:
Even there are some workarounds for the camera in Oreo and Pie CustomROM's, I don't think it will be ever fully fixed (mostly due to the missing blobs).
In the WhatsApp, use the split screen mode to scan the QR code.
Idk about your location issues as location was always working fine for me. However, did you set your location settings to "High accuracy"?
Click to expand...
Click to collapse
Hey, thanks so much for responding. So is this a known problem with the camera? Is this because 15.1 is 64 bit instead of 32 bit or is it because of something else? I'd really like to know. Would upgrading to 16 fix the problem or would it still persist?
As for the location, I tried both modes, battery saving and high accuracy. Neither of them worked. Coupled with the camera issue, I think the only real fix might be to go back to 14.1
aksnitd said:
So is this a known problem with the camera? Is this because 15.1 is 64 bit instead of 32 bit or is it because of something else? I'd really like to know.
Click to expand...
Click to collapse
Mostly yes. Every CustomROM for Moto G5 based on Android 8.0+ is 64bit, while the StockROM is still 32bit only (both stock Nougat and stock Oreo).
Would upgrading to 16 fix the problem or would it still persist?
Click to expand...
Click to collapse
Camera? Nope. There are still some workarounds for the camera in Pie CustomROMs though (e.g. this one https://forum.xda-developers.com/g5/themes/perfect-gcam-5-1-moto-g5-cedric-t3890519).
Location? I can't tell, sorry.
Hi!
I've finally updated to android pie with ACIP 14.0. Everything runs smooth and a lot of issues that I was experiencing caused by my old ROM (CM11) are solved now and a lot of new apps are finally working as expected.
The only issue that I was hoping also to solve with the upgrade to pie, are the date and time problem related with the GPS after the rollover. In the part of Europe where I'm living the Rollover took place the 3th of November. Since then, when I get a fix, the time stamps read by the GPS sensor are off by 19 years. That is not a huge issue, because the navigation is working, but is preventing me to use some tracking app, especially Strava.
I've tried to reset the GPS with the GPS Fix app, and also to clear cache and data, but nothing seems to work.
Is there someone out there who is experiencing the same problems? Does anyone have an idea how to solve it?
Many thanks,
Valde
Valde_91 said:
Hi!
I've finally updated to android pie with ACIP 14.0. Everything runs smooth and a lot of issues that I was experiencing caused by my old ROM (CM11) are solved now and a lot of new apps are finally working as expected.
The only issue that I was hoping also to solve with the upgrade to pie, are the date and time problem related with the GPS after the rollover. In the part of Europe where I'm living the Rollover took place the 3th of November. Since then, when I get a fix, the time stamps read by the GPS sensor are off by 19 years. That is not a huge issue, because the navigation is working, but is preventing me to use some tracking app, especially Strava.
I've tried to reset the GPS with the GPS Fix app, and also to clear cache and data, but nothing seems to work.
Is there someone out there who is experiencing the same problems? Does anyone have an idea how to solve it?
Many thanks,
Valde
Click to expand...
Click to collapse
Hi.
Thanks for your hint. I didn't noticed this issue so far but can confirm it with lineage 17. It seems to be really fresh.
I don't have much hope this can be fixed easily. At first we have to find out where the date gets calculated wrong. Most likely this happens in the gps chip firmware. Then we have nearly no chance.
Maybe doing the calculation on our own in a middle layer (kernel driver or HAL).
But at first some research is needed to make well-grounded statements.
115ek said:
Hi.
Thanks for your hint. I didn't noticed this issue so far but can confirm it with lineage 17. It seems to be really fresh.
I don't have much hope this can be fixed easily. At first we have to find out where the date gets calculated wrong. Most likely this happens in the gps chip firmware. Then we have nearly no chance.
Maybe doing the calculation on our own in a middle layer (kernel driver or HAL).
But at first some research is needed to make well-grounded statements.
Click to expand...
Click to collapse
Hi 115ek,
Thanks for your reply. Do you know if Sony is still supporting the Z1c for major issue? I was looking for a firmware upgrade related to this problem, but I didn't find anything. If i search the Xperia website with my IMEI for updates it states "Sorry, the information is currently not available. Please try again later. " . Do you have any hint?
Thanks,
Valde_91 said:
Hi 115ek,
Thanks for your reply. Do you know if Sony is still supporting the Z1c for major issue? I was looking for a firmware upgrade related to this problem, but I didn't find anything. If i search the Xperia website with my IMEI for updates it states "Sorry, the information is currently not available. Please try again later. " . Do you have any hint?
Thanks,
Click to expand...
Click to collapse
No, forget about sony support. The device is too old.
We have to find a solution on our own. Live with it, fix it or buy a new device.
Most likely even sony can't do anything about it because they also just bought the GPS chip + its firmware from a supplier...
115ek said:
No, forget about sony support. The device is too old.
We have to find a solution on our own. Live with it, fix it or buy a new device.
Most likely even sony can't do anything about it because they also just bought the GPS chip + its firmware from a supplier...
Click to expand...
Click to collapse
Hi,
Could be spoofing app a workaround for this issue? I've tried many of the one available on the market, but I didn't find any that allows to spoof the date and time but not the position. Does anyone have any idea if there is an app out there that could work?
Many thanks!
Although the issue was fixed some weeks ago, I think it's worth to mention it here. Maybe someone else will stumble over this thread later on.
The issue is described here and affects many legacy devices.
@jason972000 fixed it by editing the GPS HAL. Basically the missing 1024 weeks are added to the timestamp, when it is considered to be lying in the past. The fix for amami (Z1 compact) can be found here.
LineageOS 16.0 and 17.1 as well as AICP 15.0 now include the fix and will show a correct timestamp.
A few days ago Xfinity Mobile (or Samsung? I'm unsure) started pushing OTA update G965USQU7DTA5 (One UI 2 upgrade with Android 10).
I successfully updated mine SGS-9 but got stuck on wife's SGS-9 Probably, first attempt of download on this phone was interrupted (my wife went to store, and download was paused 'cause of no WiFi). But after that it's always stopped on 25% and saying "Couldn't download update: Unable to update the software. A network or server error occurred. Try later again". It's a bug in buggy Samsung software updater, I'm 100% positive, but how to fix that stuff without resetting the phone?
Phone is NOT rooted or unlocked; I googled for "offline update" instructions for stock, locked phones but can't find good, clear instructions.
Any suggestions, guys?
P.S. I've never done phone reset on SGS-9, how it works? Is it quick and safe enough? My wife's phone don't have sideloaded and/or pirated apps, everything by original, Google- & Samsung way.
Update: I resolved my issue by updating phone from PC, using Samsung's "Smart Switch" application - everything went smooth and easy.
P.S. Big thanks to this guide: https://thedroidguy.com/how-to-fix-...not-update-to-latest-software-version-1097987
Update 2: My question received no answers, even no attention but I still believe in people (generally)
So, after update to Android 10 on SGS9, my wife found what the new camera app is kinda downgrade: she doesn't likes new video mode full screen chooser (instead of "scroller") and some other small things. By the way, I clearly understood her: for example, on her SGS9 (updated via PC) video has, by default, bigger zoom than mine SGS9! It's kinda ridiculous but I understand, some parts of the software was written by Korean guys
My question is: could you provide some tips how to install stock camera app from the previous firmware (Android 9), without flashing back old firmware (I suspect what Sam-damn-sung and X****&nity will not support Android 9 anymore)?
Thank you!
P.S. I know how the google search works; I know even more - how xda-dev search works too but I can't find exact answer to my question, sorry!
sensboston said:
Update 2: My question received no answers, even no attention but I still believe in people (generally)
So, after update to Android 10 on SGS9, my wife found what the new camera app is kinda downgrade: she doesn't likes new video mode full screen chooser (instead of "scroller") and some other small things. By the way, I clearly understood her: for example, on her SGS9 (updated via PC) video has, by default, bigger zoom than mine SGS9! It's kinda ridiculous but I understand, some parts of the software was written by Korean guys
My question is: could you provide some tips how to install stock camera app from the previous firmware (Android 9), without flashing back old firmware (I suspect what Sam-damn-sung and X****&nity will not support Android 9 anymore)?
Thank you!
P.S. I know how the google search works; I know even more - how xda-dev search works too but I can't find exact answer to my question, sorry!
Click to expand...
Click to collapse
I think it's more no one has xfinity. I was one of the few and first to have xfinity when I got my s8. xfinity is a weird setup compared to most phones. I had to ditch em when they charged me like 3 or 4 times in one month, it took me almost 4 months to get a refund.
With root you might be able to get the old camera working possibly. Or gcam I'm no developer so I wouldnt know the exacts. And I still run my xfinity s8 ???
When I use the LTE network of the chip inserted in drawer 2, the Waze and Google Maps applications do not recognize the GPS. Only on the chip inserted in drawer 1. Would it be a limitation of the hardware itself? I'm using Android 10 with August patch.
I tested when i read this. And GPS doesn't work for me either on SIM2. That's a strange bug.
I tested it on Android 10. I don't know how it is on Android 9, and I don't intend to downgrade it. The functions of Android 10 as the gestures I like.
However it seems that this is a general error, because a friend has already used the Mi A2 Lite with the android oreo and had the same problem.