Related
Hey I updated to this last night and now my Gps won't get a signal. Is this a regular occurance, and how do I fix it?
Sent from my HTC Liberty using XDA App
arnienz said:
Hey I updated to this last night and now my Gps won't get a signal. Is this a regular occurance, and how do I fix it?
Sent from my HTC Liberty using XDA App
Click to expand...
Click to collapse
I have not had any issues with GPS not working on FR008. Did you do a full Wipe Data, Wipe Cache and Wipe Dalvik cache before you flashed?
I wiped the cache, but not a wipe disk.
Turns out the GPS *DOES* work, it just takes much longer to get a connection now. Which is odd :S
arnienz said:
I wiped the cache, but not a wipe disk.
Turns out the GPS *DOES* work, it just takes much longer to get a connection now. Which is odd :S
Click to expand...
Click to collapse
That's how it's supposed to work in a standalone mode. Enable Network Localization if you want faster lock and check with GPS Status app that your phone is acquiring AGPS data.
My phone is still really bad at GPS. It was fine on the stock 2.1 but after updating to Fr008 it sucks. Takes so long to get a connection that I don't even bother with the GPS anymore.
What can i do to fix this?
you can update radio firmware.
In one of my updates of my customized version of FR008, I ended up rendering WiFi unusable. I could tap the WiFi button in settings or on the Android power control to my hearts content but I kept getting an error. The only way to resolve it was to wipe the system, wipe the caches and then install my customized FR008.
Changing the radio I don't believe will work to solve this because I believe the problem was not with the radio itself, but with one of the data files already on the internal memory getting corrupted after flashing the ROM. That said, take great care in flashing the updated radio. Ensure your battery is fully charged before trying it, because a failed flash of the radio could permanently brick the phone.
Hello everyone!
I have been experiencing a strange issue with almost all the Marshmallow ROMs currently in the development section. The Phone boots, Setup Wizard runs, and in between, the screen freezes/hangs and after 5-10 seconds the phone reboots. Again the setup wizard runs and even if i'm able to complete the wizard, the phone frequently hangs and then reboots.
I had been running Paranoid Android 5.1 ROM before flashing the Marshmallow ROM and this strange issue suddenly started. I have tried to flash stock rom and then flash twrp, then flash the ROM, even wiped everything several times. Still the same issue persists. This is really getting annoying as i have tried 3-4 different ROMs and 2 GApps and still the screen freezes and then phone reboots.
And this happens only on Marshmallow ROMs as i again have currently installed Chroma 5.1.1 ROM and its running smoothly. I am beginning to think of it to be a hardware issue. Can anyone help me solve this?
imrock0 said:
Hello everyone!
I have been experiencing a strange issue with almost all the Marshmallow ROMs currently in the development section. The Phone boots, Setup Wizard runs, and in between, the screen freezes/hangs and after 5-10 seconds the phone reboots. Again the setup wizard runs and even if i'm able to complete the wizard, the phone frequently hangs and then reboots.
I had been running Paranoid Android 5.1 ROM before flashing the Marshmallow ROM and this strange issue suddenly started. I have tried to flash stock rom and then flash twrp, then flash the ROM, even wiped everything several times. Still the same issue persists. This is really getting annoying as i have tried 3-4 different ROMs and 2 GApps and still the screen freezes and then phone reboots.
And this happens only on Marshmallow ROMs as i again have currently installed Chroma 5.1.1 ROM and its running smoothly. I am beginning to think of it to be a hardware issue. Can anyone help me solve this?
Click to expand...
Click to collapse
Flash Frank ROM, Flash Tuxi Gapps from Frank's OP, no one is having any issues now. Also don't forget to do a factory reset if you can even the Internal data.
sidnoit22 said:
Flash Frank ROM, Flash Tuxi Gapps from Frank's OP, no one is having any issues now. Also don't forget to do a factory reset if you can even the Internal data.
Click to expand...
Click to collapse
I have done factory reset several times. Even flashed stock via fastboot multiple times. Done the exact same steps you mentioned. Its not only with Frank ROM actually, i tried another Marshmallow ROM and the same thing happened again.
How is it that Lollipop ROMs are running smooth and Marshmallow ROMs are crashing?
imrock0 said:
I have done factory reset several times. Even flashed stock via fastboot multiple times. Done the exact same steps you mentioned. Its not only with Frank ROM actually, i tried another Marshmallow ROM and the same thing happened again.
How is it that Lollipop ROMs are running smooth and Marshmallow ROMs are crashing?
Click to expand...
Click to collapse
seems like it's Gapps/ ROM problem (with setup wizard)
this my only suggestions:
1. try to flash Frank's M without Gapps > reboot normaly
if this worked, then it's related to Gapps issue...
if it still remains, then
2. Flash ROM, Gapps, wipe, etc.
after that back to home of TWRP > Mount > Mount system > back > Advanced > File manager > go to /system/priv-app
search for folder name related to Setup wizard/ Google setup wizard (NOT GooglePartnerSetup) > delete it > reboot
3. fingercrossed it will bring you to home screen without any problem...
good luck then :fingers-crossed:
yayakuya said:
seems like it's Gapps/ ROM problem (with setup wizard)
this my only suggestions:
1. try to flash Frank's M without Gapps > reboot normaly
if this worked, then it's related to Gapps issue...
if it still remains, then
2. Flash ROM, Gapps, wipe, etc.
after that back to home of TWRP > Mount > Mount system > back > Advanced > File manager > go to /system/priv-app
search for folder name related to Setup wizard/ Google setup wizard (NOT GooglePartnerSetup) > delete it > reboot
3. fingercrossed it will bring you to home screen without any problem...
good luck then :fingers-crossed:
Click to expand...
Click to collapse
Thanks i'll try this out when i get back home. Although i did try flashing just the ROM to see if GApps were causing the issue. Without GApps, the phone booted to the homescreen, but then after 5-10 mins would reboot itself. I don't know may be it has got something to do with temperature? Because i've noticed that the phone becomes very hot when it first boots up on a new ROM(i know its normal for it to get hot). But when i used the phone on a Marshmallow ROM when the phone was NOT hot, it went on pretty well for 20-30 mins and then again rebooted.
yayakuya said:
seems like it's Gapps/ ROM problem (with setup wizard)
this my only suggestions:
1. try to flash Frank's M without Gapps > reboot normaly
if this worked, then it's related to Gapps issue...
if it still remains, then
2. Flash ROM, Gapps, wipe, etc.
after that back to home of TWRP > Mount > Mount system > back > Advanced > File manager > go to /system/priv-app
search for folder name related to Setup wizard/ Google setup wizard (NOT GooglePartnerSetup) > delete it > reboot
3. fingercrossed it will bring you to home screen without any problem...
good luck then :fingers-crossed:
Click to expand...
Click to collapse
Here's another update. I tried the new Chroma Marshmallow ROM and it too had the same issue. The phone hangs/freezes randomly and then reboots. After trying so many ROMs, i think the issue is with hardware itself. None other has reported this issue, nor could i find it anywhere else. I guess i can say that my(and only my) nexus 4 is not compatible with Marshmallow officially and unofficially.
I don't know what kernel Frank's uses but you could always try to flash an alternate kernel. I haven't taken the jump to Marshmallow yet, but it seems TaUrUs and hellsCore support M (I currently use hellsCore with stock L).
bjb2 said:
I don't know what kernel Frank's uses but you could always try to flash an alternate kernel. I haven't taken the jump to Marshmallow yet, but it seems TaUrUs and hellsCore support M (I currently use hellsCore with stock L).
Click to expand...
Click to collapse
I'll try another kernel and ping back.
Probably lacked boot the system before you install GApps.
imrock0 said:
I'll try another kernel and ping back.
Click to expand...
Click to collapse
The FC of Setup Wizard is discussed in the ROM thread of Chroma.
You can try this because it is advised by the Dev of Chroma and supported by many others and I have succeeded with this.
Flash stock L and boot up.
Boot into TWRP (make sure you have the latest) and factory reset.
Flash Chroma 1/11/2015 and Bank's Gapps without boot/reboot in between and no wipe afterwards.
Reboot.
---------- Post added at 07:03 PM ---------- Previous post was at 07:00 PM ----------
webg3brasil said:
Probably lacked boot the system before you install GApps.
Click to expand...
Click to collapse
At least for Chroma, that is a wrong approach. No boot between ROM and Gapps flash.
Make sure you have permissions granted to all of the apps. I had similar issues, and had to do with Location and apps making calls to GPS. Would cause a reboot, and not just a force close. Try amending the Location settings as well. All else fails, capture a logcat.
Everyone thanks for your time!
I found the solution. bjb2's suggestion did the trick. I flashed TaUrUs-Mallow Kernel after Frank Marshmallow ROM and everything seems fine now. Have been running Marshmallow since a day without any issues. Still it's curious why the stock kernel gave such errors.
Thanks everyone again for your suggestions and help
I´m having problems enabling the WIFI after 4 days using the CM13.... it is very strange.
What I have tryed,
-Fly mode on - off
-Flashing the Radio
-Wiping cache with TWRP
-Factory reset
Still not working. Now after a factory reset it is still haning up on the CM13 Configuration Wizard/Assistant, when you select select a WLAN....
Here some screenshots
Does the wifi work properly on stock LP? If not, it could be a hardware issue.
audit13 said:
Does the wifi work properly on stock LP? If not, it could be a hardware issue.
Click to expand...
Click to collapse
sorry but what do you mean with stock LP?
I mean stock Lollipop (5.1.1) for Nexus 4.
https://developers.google.com/android/nexus/images
Maybe problem is with Kernel.
Hi guys, I had to give up using CM Roms since the phone reboots every time I try making a call or receive one, I understand there is some king of bug with the dialer framework included in the GAPPS package and that installing the Google Dialer from the play store should solve it but in my case i hasn't. This is what I've tried to no avail:
- Intalled Google DIaler from PlayStore/APK and set it default with all the permissions enabled.
- Installed Google Dialer apk as system app and set it default with all the permissions enabled.
- Installed the full GAPPS package.
- Removed the stock dialer and did all things above.
Hope someone can help me out here,
Thanks.
This happens when you have multiple phone dialer apps enabled. To use any other dialer than the included (when you flash Gapps Tiny or Micro which is recommended since the bigger packs replaces the CM app).
If you don't like the CM one, you should still flash a smaller Gapps and then disable CM dialer and download the one you want. If you already flashed a bigger Gapps, you should format system, cache and dalvik/arts partition and then reflash CM and then the smaller Gapps.
Should be enough to go settings, apps, click the gear weel (next to 3 dot menu), choose standard apps from this menu and determine your dailer as standard app..
This is a classical issue..
Sent from my OnePlus2 using XDA Labs
Sam Nakamura said:
Should be enough to go settings, apps, click the gear weel (next to 3 dot menu), choose standard apps from this menu and determine your dailer as standard app..
This is a classical issue..
Sent from my OnePlus2 using XDA Labs
Click to expand...
Click to collapse
Hi Sam, that's what I mean when I've set it as default.
pitrus- said:
This happens when you have multiple phone dialer apps enabled. To use any other dialer than the included (when you flash Gapps Tiny or Micro which is recommended since the bigger packs replaces the CM app).
If you don't like the CM one, you should still flash a smaller Gapps and then disable CM dialer and download the one you want. If you already flashed a bigger Gapps, you should format system, cache and dalvik/arts partition and then reflash CM and then the smaller Gapps.
Click to expand...
Click to collapse
Hey pitrus, this issue actually started while only having CM dialer installed since I mainly flash pico gapps.
Will try it again since its been like a month since I gave up on it. Let you know later.
J3RI3L said:
Hi Sam, that's what I mean when I've set it as default.
Click to expand...
Click to collapse
Well, okay.. Thanks for clarification :good:
Maybe you'd like to give Banks a shot, I think it's worth to try...
https://download.dirtyunicorns.com/gapps/Banks/
I never had this specific problem, only when it wasn't set to be default but a also only use one dailer.. The one that is default on cm based roms..
Sent from my OnePlus2 using XDA Labs
Guys I've had no luck, tried with a clean install of CM14 and still facing the same problem. Just today did a CM14.1 install and it is still present for me.
I guess that I could flash just CM and not gapps but I rely on Google services for a lot of stuff. Will keep trying though.
I'm having the exact same problem, random reboots during calls only, sometimes I don't even have time to answer. I'm running CM13 and only have one phone app, also set as default. When running stock and Cyanogen all was fine, this only started after flashing CM13.
Developemt for Cyanogen stopped that's why I switched, maybe coming from another rom is causing this? I did a full wipe when flashing and have updated to several nightlies and the problem remains. Maybe I'll try another rom and test it for a while.
Installed Dirty Unicorns a few days ago and the problem seemed to have been fixed, but yesterday it started acting out again. Is there a way to check if this problem is hardware related?
I'm now doing a factory reset and installing Oxigen hoping that'll fix this once and for all.
It's a problem related to Gapps
rtorresz said:
Installed Dirty Unicorns a few days ago and the problem seemed to have been fixed, but yesterday it started acting out again. Is there a way to check if this problem is hardware related?
I'm now doing a factory reset and installing Oxigen hoping that'll fix this once and for all.
Click to expand...
Click to collapse
It is not a hardware problem, I don't have this issue when running Oxygen OS, it only happens to me when running any AOSP based rom with Gapps installed.
Flash Oxygen from here http://downloads.oneplus.net/devices/oneplus-2/ and it will fix it, it's not the same as running CM though.
J3RI3L said:
It is not a hardware problem, I don't have this issue when running Oxygen OS, it only happens to me when running any AOSP based rom with Gapps installed.
Flash Oxygen from here http://downloads.oneplus.net/devices/oneplus-2/ and it will fix it, it's not the same as running CM though.
Click to expand...
Click to collapse
Sounds like you flashed the full version of Gapps instead of the recommended Nano or Micro which does not replace the dialer app with Googles own, try the smaller Gapps and you should be ok.
pitrus- said:
Sounds like you flashed the full version of Gapps instead of the recommended Nano or Micro which does not replace the dialer app with Googles own, try the smaller Gapps and you should be ok.
Click to expand...
Click to collapse
I've installed them all with the same result, last time I was using Pico Gapps with Seraph's CM14 and it happened eandomly, sometimes I could make and receive calls normally but a most of the time it would reboot as soon as the phone started ringing.
Currently I've tried a lot of solutions so I'm not really sure of what's wrong.
J3RI3L said:
It is not a hardware problem, I don't have this issue when running Oxygen OS, it only happens to me when running any AOSP based rom with Gapps installed.
Flash Oxygen from here http://downloads.oneplus.net/devices/oneplus-2/ and it will fix it, it's not the same as running CM though.
Click to expand...
Click to collapse
I flashed the latest OOS and now things are only a little bit better, instead of reboots I get dropped calls and a "No available network" message. This seems to happen only when I'm on a 3G or 4G network, if I change to a 2G network I can make calls without problems. This is driving me crazy, I've tried almost everything and I can't see what I'm missing.
rtorresz said:
I flashed the latest OOS and now things are only a little bit better, instead of reboots I get dropped calls and a "No available network" message. This seems to happen only when I'm on a 3G or 4G network, if I change to a 2G network I can make calls without problems. This is driving me crazy, I've tried almost everything and I can't see what I'm missing.
Click to expand...
Click to collapse
Its happening to me as well just as you describe it. It is very weird. In thinking of flashing the stock OOS 2.2.0 just to check whether it makes any diference.
Yesterday I restored my phone back to stock, but the problen remains.
This definitely has something to do with mobile data. If I disconnect mobile data I can make calls without any problem, when I'm connected to a wifi network too (I'm guessing because the phone has no need to use mobile data).
Some suggest that this might be related to VoLTE and operators not supporting it, but I can't find anyway to see if this is even exists or if its activated in OOS.
Later today I'll try Hydrogen and see what happens.
UPDATE: Flashing Hyrogen didn't solve the issue, calls keep dropping when mobile data is activated on LTE network.
UPDATE 2: Going back to OOS 2.2.1 didn't solve the problem either.
Kinda solved now
rtorresz said:
Yesterday I restored my phone back to stock, but the problen remains.
UPDATE: Flashing Hyrogen didn't solve the issue, calls keep dropping when mobile data is activated on LTE network.
UPDATE 2: Going back to OOS 2.2.1 didn't solve the problem either.
Click to expand...
Click to collapse
It seems I have solved my problem with the reboots and I think might help with your droped calls as well.
Firstly I flashed this OOS 3 firmware https://www.androidfilehost.com/?fid=24591020540821656, it comes with a hybrid TWRP, after that flashed the official CM14.1 and pico Open Gapps.
I think the firmware file did the trick or maybe it was the recovery since I haven't had a reboot in the past 2 days when receiving calls or making them.
Hope it helps
It's been a few days since I tried the last solution and so far my problem seems to be solved.
What worked for me was flashing the latest modem from H2OS 2.5 which also is supposed to enable VoLTE, but I can't confirm this since my carrier does not support VoLTE yet. To do this I first flashed CM 14.1 and then the modem, it worked fine since the first boot. Since my battery life wasn't the best in Nougat I went back to CM13 and the phone is still working fine.
Guys I am facing random reboot issue on every cm13 base Roms and even cm14 Roms..
Tried every possibility
1.Changed Roms
2. Cleared internal
OOS works pretty fine. Not even a single random reboot.
I have analysed when I switch off LTE connection phone works fine.
On LTE whenever I try to watch YouTube or any other high speed related stuff signal gets dropped, connects again and phone gives a reboot
Phone is almost unusable as it is giving me reboots multiple times in a day.
I am using Reliance Jio LTE(India)
Any suggestions please?
One guy reported the same issue on cm13 thread but havent got any resolution
I'm sorry bro.. Even I'm using reliance jio and i haven't suffered any such issue.. Try booting into your recovery and doing a fresh install, wipe dalvik and other caches.. Look if the random reboots is happening in a clean rom with no apps installed. You must have messed up with some system/root settings which may be the cause.. Also if u use titanium backup to restore apps after fresh installing a custom rom, try restore only the app and not the data. If then the reboots doesn't happen, it's more likely an app that's causing the reboots..
Also if you're installing additional zip files, verify that they aren't corrupt!
shravansp24 said:
I'm sorry bro.. Even I'm using reliance jio and i haven't suffered any such issue.. Try booting into your recovery and doing a fresh install, wipe dalvik and other caches.. Look if the random reboots is happening in a clean rom with no apps installed. You must have messed up with some system/root settings which may be the cause.. Also if u use titanium backup to restore apps after fresh installing a custom rom, try restore only the app and not the data. If then the reboots doesn't happen, it's more likely an app that's causing the reboots..
Also if you're installing additional zip files, verify that they aren't corrupt!
Click to expand...
Click to collapse
I have tried all the things.. except going full stock..
Tried to go full stock yesterday and now it seems issue is fixed..
Haven't got any random reboot.. will test it more..
ashu01 said:
I have tried all the things.. except going full stock..
Tried to go full stock yesterday and now it seems issue is fixed..
Haven't got any random reboot.. will test it more..
Click to expand...
Click to collapse
Glad you got your issue fixed in stock rom..!
shravansp24 said:
Glad you got your issue fixed in stock rom..!
Click to expand...
Click to collapse
Now even in cm13 I am not facing any issues..
ashu01 said:
Now even in cm13 I am not facing any issues..
Click to expand...
Click to collapse
That's great!