Hello everyone!
I have a China version Redmi 3S prime (3/32GB). Bought it on Gearbest with vendor ROM. Then I flashed China EN MIUI ROM and unlocked bootloader. After that I installed MIUI from Xiaomi.EU, installed TWRP and rooted the device. Everything was running great! Phone was fast and stable, battery lasted two days with intense use (about 8h of SOT) and running 2 SIMs.
All in all a great little cracker. Now for this holiday season I needed to use GPS and that's when I started to notice problems with the Redmi 3S. Basically, everytime I use GPS with DATA CONNECTION the phone will reboot itself after a few minutes of usage, sometimes after 1 minute and sometimes after 20 minutes. I did several tests and came up to the conclusion that this only happens when I use GPS with a data connection (3G or 4G the result is the same). If I use GPS with offline maps (and data connection off) there are no reboots whatsoever. If I use GPS with online maps (Gmaps or Waze), but connected on a wifi hotspot (my wife's phone) there are no reboots as well.
Thinking it could be something from Xiaomi.eu I reverted back to the global stable EN MIUI version without TWRP and without ROOT and ran the same tests, results were exactly the same!
Has this happened to anyone else? Is this a hardware issue? Shipping the phone back to China will probably make it disapper along the way
I am thinking about flashing a CM to see if it behaves the same but don't wanna go through that hassle if most probably is an HW issue
Related
I start this thread as I would like to find out how it works and why I have a problem with it.
A-GPS in maniac's built CM7 nightly 20120616 seemed to me a great feature in case we have no data connection and need GPS.
It downloads lto.dat file to /data/location/
All other files, like gpsdata.nvs for ephemeries, LEARN_STORE.bin for last fixes, location.cfg are updated after each use of the GPS.
What I checked earlier with CM 7.2 official, with no data connection, it took ca 3 minutes for the fix (and it does not use lto.dat file)
With data connection for both builds it is only ca 10 s to fix.
But with no data connection and after downloading lto.dat file my defy with CM7 nightly 20120616 cannot fix at all - it shows up to 2 sattelites in the center of the radar, with almost the same position.
So my question would be: if there is no data connection is the device somehow forced to use lto.dat? Could be that lto.dat file somehow 'fools' the device for any reason?
You probably didn't initialize the lto.dat.
You have to do a fix after every lto-Download and after every reboot in order to initialize the lto.dat.
What i want to say is: The lto.dat doesn't work and also isn't used for the first fix after download or reboot.
You can do a fix with A-GPS (DATA ON) to speed up the process. After that, the lto.dat will be used in offline mode.
I don't know why you can't get an offline-fix after downloading as the lto-file isn't being used then. Could be coincidence.
It works for me in about 30 seconds although it is true that GPS Status shows the first 2-3 satellites in the middle with the same positions.
If you download the 30-day file and initialize it before leaving your country it should easily last for a vacation.
It works perfectly for me. After initializing an offline-fix usually takes about ten seconds...
Greetz, Unr3aL67
Sent from my Defy via Tapatalk
GPS is only reason I left cyanogen. I use car navigation often, in roaming too, and I run into BIG problems. Miui has maybe even bigger problems.
Interesting in every stock and derative ROMs GPS run perfect. Everything is is seconds, with or without data. And GPS status program find more satellites.
I would really love someone deal with this problem seriously. But I think, untill Quarx need GPS badly, this problem will not be solved completely
Questions go in the Q&A section
Thanks a lot for some explanation. Problem is now solved and in my case it turned out that the main cause was use of GPSEssentilas to check how fast I can get a fix.
And after each start of the apk it stopped working and I had to start it second time but with no success in fixing the position (I was wiping its data, reinstalling, but nothing helped).
And when I forced it to close and checked with any other map apk I use, I get a fix quite fast.
I wouldn't say that stock ROMs find more sattelites, I usually have 6 - 8 in less then 30s, no matter now with or without data transfer on - the fact is that my MTK Qstarz module have cold start up to 1min 30s without any data preloaded, but it is a better chip than defy's Broadcom and what I observed its max sattelites found was 9.
And when driving I usually use a car navigation, but in many daily cases like looking for sg during a walk or trying to meet friends phone gps is a must ;-)
Check this link for automatic lto.dat download:
http://forum.xda-developers.com/showpost.php?p=29490347&postcount=54
It works well with froyo.
In cm7/9/10, insert the code to a right file.
I have a D801 on T-Mobile running CM12, but that last part is only valid in the sense that I am running a custom ROM. CM11 or 12, nightlies or stable doesn't change the symptoms I am seeing.
Issue - my phone randomly reboots when on LTE. WiFi and HSPA don't do this .. Only LTE. I am at a loss. I have cleared and reflashed all sorts of ROM versions and when I sag cleared .. We are talking flame throwers. All data gone, ADB push the files clear.
Anyone have any ideas?
Its pretty reproducible. I had my phone on all day on 3G, apps and games and .. just the whole bit. I just now after over 24 hours of solid performance switched the LTE on and it was rebooting unprovoked within 10 minutes.
Logs or it didn't happen.
Fair enough.
How do?
I have an n9005, rooted, running 4.4.4 CM11 M12.
I have baseband N9005XXUENE3. My device is not carrier locked.
I need to stay on KK for app related reasons so can't go up to 5.x.
I have had an annoying GPS issue for the past 10+ months whereby my GPS intermittently loses most/all satellite locks during a several hour window at least once a day. A friend with a Nexus 5 running stock has the same issue, at the same time of day, no less, and this is easily replicable by us as each day the same issue will happen simultaneously for these devices.
GPS runs flawlessly at other times of day, both with and without A-GPS (eg it works fine with Airplane Mode on as well as with A-GPS, unless it is being used within one of these 'dead zone' time windows). Whenever a deadzone hits, which appears to be a similar time each day but slightly different to the day before (the 'window' is currently moving 10 minutes ahead each day, give or take a few), the GPS constantly resets itself, going from full lock to 'Looking for GPS fix' for up to 10 minutes before finding satellites, then promptly losing them again within a few minutes. This lasts for around 5 hours each day and for myself currently it makes my GPS unusable from 10am-3pm each day.
GPS Status & Toolbox shows the device connected to 0-4 satellites during these times, with no lock at all and an infinity symbol for signal upstrength. Downloading A-GPS manually refreshes the GPS and it provides a full suite of satellites for a lock.. for between two seconds and one minute, before losing all sats immediately and needing another A-GPS download.
The issue appears to be a bug that has existed in Android from at least 4.4.2 onwards and has affected a lot of people online, most of whom describe the issue as 'my GPS is broken' and get the standard responses re: A-GPS, recalibrate compass, etc. This is NOT a hardware issue as the GPS works flawlessly outside of these certain times of day. I have spent a large amount of time searching for tips and advice and it seems to be a fairly widespread problem on certain devices, but as most people rarely use GPS they don't see it as much of an issue or don't notice it happening.
Anyhow, my friend has recently flashed a different modem to his device- a stock 4.4 modem for his Nexus 5 - that appears to have alleviated his problems! He now has no GPS issues at all. I am new to Android modification in general and am looking for a 4.4 modem I can flash for my device, specs as above.
Any advice, regarding the GPS issues or a modem to use would be greatly appreciated.
Modems in modem thread General section .
As i understand Note 3 GPS is a product of the kernel not the modem but not 100% sure of that .
Have you ever tried a standard factory reset ??
JJEgan said:
Modems in modem thread General section .
As i understand Note 3 GPS is a product of the kernel not the modem but not 100% sure of that .
Have you ever tried a standard factory reset ??
Click to expand...
Click to collapse
I've only rooted this recently and tried everything without rooting that I thought may help, including multiple factory resets.
Thanks for the advice, I'll keep investigating.
I tried a lot of rom's, from Android 4 to 7. A lot of them are great. The best rom's that works for me are Lollipop rom's. They are fast, stable. Such as:
cm-12.1-20151026-UNOFFICIAL-ms013g-ver_AIO-3.zip
cm-12.1-20151107-UNOFFICIAL-ms013g.zip
cm-12.1-20160613-UNOFFICIAL-ms013g.zip
The only bug that I have with all lollipop rom's is that, wifi will go to sleep if I loose range on the wifi and come back. If I leave my home, out of wifi range, and come back. Phone will automatically connect to my wifi, but it will fall a sleep after 1min or so. So I need to restart my phone, phone will connect automatically to my wifi again and it will stay connected until I leave my home again. So, I need to restart my phone every time when I'm connecting on same wifi.. or, my wifi will fall a sleep in the stand by.
This is the only issue with lollipop. 4, 6 and 7 rom's dot have these problems.
Is there any way to fix this ?
Use motion base rom its awesome and stable.. im using it for 1 year.. plus it got the highest antutu bench mark i test all rom its score is 28000+ the other rom in 24000 below... the rom has no fc and no bugs ;all sim are working properly and as well as gps...
Im using Noble rom 2.1 rooted with magisk...
Since the first release of oreo I started using the rom as a daily driver, later on paired with a good kernel it had some good perfomance
But after some days of using the rom i started to notice a huge battery drain caused by the Mobile network standby process?
My battery was old (OEM 2014 battery) so i decided to revert back to lineageOS just after a couple of days where I haven't had any issues with that mobile network standby
Now I'm really curious what is causing this issue,drain because I am using the phone on the same settings as on 7.1 nougat, I am living in a country where all networks run on 3G,H+,2G etc. so no 4G if this can be a cause
Changed the network modes many times and tested throughout the days but there was no sucess the drain was still persist, tried updating,downgrading bootloaders swithing modems but again no sucess
If there, in the world of android is any solution, here is the thread to discuss about this issue. :fingers-crossed:
I've wondered this too. I've been running los15 on my g900v , I rooted and boot the first ROM that would work without having or remembering todomuch, I ran the first custom kernal I could find via google, and ran whatever was noted as the latest Verizon modems. its like right off the bat, smooth , consistent battery life and nice. Then the next day I noticed things would crash, my Bt temperamental at best and restarted it just to get by. if I have sync on at home, WiFi off, it just chills , if I turn sync off and drive around town, my battery life gets eaten by the unknown. I pulled some logs to see whats up with my BT but haven't got around to it yet. But my battery too is old (I literally found my s5 in the trash) and I run weird processes and tweak settings all the time just to mess with it, so that could be it to. If I see anything weird I'll let you know.
I'm struggling with this issue for months, since the first port of an Oreo custom ROM (LOS and RR) for the Galaxy A3 Duos (my device) started being developed.
From the beginning I had this problem, and what, since then, puzzles me the most is the fact that only some of us, flashing the same ROM in the same device, experience the issue. Whenever I flash any of those ROMs, even before installing any user apps (or when running in safe mode), the drain is there, which leads me to think that the culprit must be some setting: not an app, because I have none installed; not the ROM itself, because not everybody has this problem.
Unfortunately there seems to be no developers looking into this bug.
For the sake of information, I've observed two things that should help to narrow down the issue; or maybe not.
First, all the devices affected, as far as I've searched, are double SIM.
Second, the Mobile Network Standby (MNS from now on) drain is narrowy connected with the Bluetooth drain (which "also" occurs in Oreo). I've experienced the following: If, after a full charge, I don't switch on Bluetooth at all, then what drains my battery (according to Advanced Battery Usage information) is MNS. However, if I switch bluetooth on -even if only for one minute- then what apparentlyh drains my battery is Bluetooth, at the same speed as MNS did before switching bluetooth on.
Funny enough, the battery use info reports zero minutes activity for both Bluetooth and MNS. But how can a process which runs zero minutes drain 50% of the battery?? I'm afraid that the battery use information isn't reliable. But then that's very bad news, since, in such case, it might well happen that the real juice sucker is neither MNS nor Bluetooth!! We might be dealing with a "ghost" here, since we can't even trust the battery use information provided by the OS.
If someone has something with which to contribute to this research, or any ideas, please comment.
I'm having the same trouble on android 9 betas, even better, my phone gets without signal during those times and there's nothing I could do but rebooting the phone.
How can we help solve this? it looks like it's annoying a lot of people now