Database Info

[Q] Problem with GPS after flashing revolution XE ROM

Yesterday I flashed the Sensation Revolution XE ROM 3.6.2 and the recommended radio. Today my GPS is really screwed up. It is taking about 15 minutes to make a connection. The phone will very quickly pick up 9 or 10 satellites but will not connect. I installed the Faster Fix app and that seems to help pick up the satellites faster, but still no connection for 15 to 20 minutes. Anyone else with this problem and is there anything I can do short of going back to the stock ROM?

stev32k said:
Yesterday I flashed the Sensation Revolution XE ROM 3.6.2 and the recommended radio. Today my GPS is really screwed up. It is taking about 15 minutes to make a connection. The phone will very quickly pick up 9 or 10 satellites but will not connect. I installed the Faster Fix app and that seems to help pick up the satellites faster, but still no connection for 15 to 20 minutes. Anyone else with this problem and is there anything I can do short of going back to the stock ROM?
Click to expand...
Click to collapse
Do you know what ril you have with that recommended radio? I have heard that the radio and ril's need to correspond to work efficiently. Also keep in mind that kernel's also have a factor as well.
My hunch is that it's the kernel that the rom is using.

The kernel version is 2.6.35.14-sensation-faux 123-v0.2.1+.

I just discovered the MD5 checksum from the file on the download site and the file on my computer do not match. What can I do about that and how can that happen?
Sorry they do match - I was checking the zip file not radio.img

I know for a fact that faux kernels do not play well with the gps.conf files (well for me anyway, Im on tmous). Have you tried other kernels or even reverted to stock kernel. Reboot and try to get a lock.
I use gps status app to see if I can get locks and works for me.

kpjimmy said:
I know for a fact that faux kernels do not play well with the gps.conf files (well for me anyway, Im on tmous). Have you tried other kernels or even reverted to stock kernel. Reboot and try to get a lock.
I use gps status app to see if I can get locks and works for me.
Click to expand...
Click to collapse
I can get a lock, but it takes a very long time - maybe 15 - 20 minutes. I would like to go back to the stock kernel and downloaded the file to my PC, but the instructions for flashing are very vague to me:
How to use:
1. Download kernel package
2. Flash in recovery
3. Done!
4. You can adjust OC settings using Daemon Controller application (find it in your app drawer)
1. should the package be downloaded to the PC or the phone? And should it be extracted?
2. How exactly does one "Flash in recovery"

stev32k said:
I can get a lock, but it takes a very long time - maybe 15 - 20 minutes. I would like to go back to the stock kernel and downloaded the file to my PC, but the instructions for flashing are very vague to me:
How to use:
1. Download kernel package
2. Flash in recovery
3. Done!
4. You can adjust OC settings using Daemon Controller application (find it in your app drawer)
1. should the package be downloaded to the PC or the phone? And should it be extracted?
2. How exactly does one "Flash in recovery"
Click to expand...
Click to collapse
Flashing a kernel is very much like flashing your rom. Just download the kernel, which would be a zip file. DO NOT extract it. Then put the zip file on your SD card. Keep a current copy of the faux kernel to rever to it or have a nandroid handy before flashing anything!
Go to recovery, clear cache partition AND dalvik cache (under advance). Don't worry your apps and settings won't get erased. Then after those two steps, go to install from zip from sd card.
Choose the kernel and flash from there. Once the script has completed installing, just reboot the phone.
Try out your phone to ensure you can use it first off. Then if it looks, feels ok, then try out the gps in an open area with a direct line to the sky. Let me know if it helps!
FYI: for what it's worth, I don't mess with overclocking at this point. Just a personal preference.

This is not looking good. After flashing the kernel the phone will not boot up. It has a white screen with htc letters on it and it's been like that for several minutes now.
What do I do now?

stev32k said:
This is not looking good. After flashing the kernel the phone will not boot up. It has a white screen with htc letters on it and it's been like that for several minutes now.
What do I do now?
Click to expand...
Click to collapse
Some times the boot screen shows for a while when installing a new kernel and after clearing the caches. Is it boot looping? If not then, go back to your pc, bring up a dos window. type in adb reboot recovery. That should bring you up to clockwork recovery. And revert back to the prior kernel or just flash the rom over with just a cache wipe and dalvik cache.
If the dos screen doesn't recognize the phone, simply take the battery out, put it back in and hold the power and volume down button at the same time. That brings you into recovery as well.

OK, I'm back in business. I reinstalled the ROM and the phone booted up. Now about that kernel. Should I just try again or is there a plan B?

stev32k said:
OK, I'm back in business. I reinstalled the ROM and the phone booted up. Now about that kernel. Should I just try again or is there a plan B?
Click to expand...
Click to collapse
Did you get the stock kernel from here?
http://forum.xda-developers.com/showthread.php?p=16419842#post16419842
Plan b would be replacing the gps.conf file on the phone. Are you up for it?
http://forum.xda-developers.com/showthread.php?t=1262652

stev32k said:
Yesterday I flashed the Sensation Revolution XE ROM 3.6.2 and the recommended radio. Today my GPS is really screwed up. It is taking about 15 minutes to make a connection. The phone will very quickly pick up 9 or 10 satellites but will not connect. I installed the Faster Fix app and that seems to help pick up the satellites faster, but still no connection for 15 to 20 minutes. Anyone else with this problem and is there anything I can do short of going back to the stock ROM?
Click to expand...
Click to collapse
Hi, stev32k
I was having the same problem with you initially when using ARHD 3.6.2. I tried many methods including your mentioned faster fix app but to no avail. Even modifying the gps.conf file did not help. Later on i went to flash radio and kernel but that did not change anything.
After searching all around, I found out the solution to my problem by accident. As some of my Apps were having FC's with superuser, i decided to uninstall the superuser updates and revert back to the old version. Coincidentally, after the uninstall of the updates, my GPS lock on timing became super fast and within 20 seconds a lock.
I thus came to the conclusion that somehow, superuser version 3.0.5 causes some GPS locking problem. Perhaps you might want to try to remove this update too and see how it goes?
Let me know if this solves your problem too.

thunderskain said:
Hi, stev32k
I was having the same problem with you initially when using ARHD 3.6.2. I tried many methods including your mentioned faster fix app but to no avail. Even modifying the gps.conf file did not help. Later on i went to flash radio and kernel but that did not change anything.
After searching all around, I found out the solution to my problem by accident. As some of my Apps were having FC's with superuser, i decided to uninstall the superuser updates and revert back to the old version. Coincidentally, after the uninstall of the updates, my GPS lock on timing became super fast and within 20 seconds a lock.
I thus came to the conclusion that somehow, superuser version 3.0.5 causes some GPS locking problem. Perhaps you might want to try to remove this update too and see how it goes?
Let me know if this solves your problem too.
Click to expand...
Click to collapse
I am also having problems with superuser. It seems to be the update because when I uninstall the update it quits force closing every time it's called on. Someone mentioned going to a version 2.?, but I can't any of the earlier versions. I would be grateful if you could post a link to one of the older versions.
I have not tried GPS since uninstalling the update, but will give it a try later and let you know if it helped.

kpjimmy said:
Did you get the stock kernel from here?
http://forum.xda-developers.com/showthread.php?p=16419842#post16419842
Plan b would be replacing the gps.conf file on the phone. Are you up for it?
http://forum.xda-developers.com/showthread.php?t=1262652
Click to expand...
Click to collapse
Yes, I got the file from the place you linked to and I am up to replacing the GPS config file. Will give that a shot shortly.

I think I can confirm thunderskain's problem with the GPS / superuser interference.
I uninstalled the superuser update, turned on GPS, then started GPS status. It found 6 satellites and got a lock in 19 seconds while inside. I repeated turning GPS off and on and call up GPS status 5 times without the superuser update and the lock times were never more than 19 seconds and a couple were under 10 seconds. The average was 10 seconds, the high was 19, the low was 5.
Next I rebooted, opened up root explorer and it got superuser permission. Then I repeated the GPS on/off and calling up GPS status 5 times. The lock times ranged from 81 seconds to 11 seconds. The average was 45 seconds.
Next I tried to remove and allow superuser permissions until superuser started giving the force close errors then repeated the same testing procedure of turning GPS on and off and measuring lock times. For 5 repeats the average was 65 seconds the high was 97 and the low was 29 seconds.
The final test was to remove the superuser update, reboot the phone and repeat the testing procedure again. This time the average of 5 tries was 12 seconds, the high was 23, and the low 4.
As a result of this I am convinced the Superuser app is interfering with the GPS function. I cannot explain why the lock times were in the 15 minute range yesterday and the longest today was in the 90 second range. That's a big difference so something else was going on yesterday that is not happening today.

stev32k said:
I think I can confirm thunderskain's problem with the GPS / superuser interference.
I uninstalled the superuser update, turned on GPS, then started GPS status. It found 6 satellites and got a lock in 19 seconds while inside. I repeated turning GPS off and on and call up GPS status 5 times without the superuser update and the lock times were never more than 19 seconds and a couple were under 10 seconds. The average was 10 seconds, the high was 19, the low was 5.
Next I rebooted, opened up root explorer and it got superuser permission. Then I repeated the GPS on/off and calling up GPS status 5 times. The lock times ranged from 81 seconds to 11 seconds. The average was 45 seconds.
Next I tried to remove and allow superuser permissions until superuser started giving the force close errors then repeated the same testing procedure of turning GPS on and off and measuring lock times. For 5 repeats the average was 65 seconds the high was 97 and the low was 29 seconds.
The final test was to remove the superuser update, reboot the phone and repeat the testing procedure again. This time the average of 5 tries was 12 seconds, the high was 23, and the low 4.
As a result of this I am convinced the Superuser app is interfering with the GPS function. I cannot explain why the lock times were in the 15 minute range yesterday and the longest today was in the 90 second range. That's a big difference so something else was going on yesterday that is not happening today.
Click to expand...
Click to collapse
Thanks Nice to know it helped. Hoped this superuser bug can be fixed soon in the new updates.

stev32k said:
Yes, I got the file from the place you linked to and I am up to replacing the GPS config file. Will give that a shot shortly.
Click to expand...
Click to collapse
Would this help?

kpjimmy said:
Would this help?
Click to expand...
Click to collapse
Yes, I think that will help. Now how do I install it?

stev32k said:
Yes, I think that will help. Now how do I install it?
Click to expand...
Click to collapse
I'm guessing its a normal apk install. Meaning put the sucker on the sd card and click install with root explorer or the like.

kpjimmy said:
I'm guessing its a normal apk install. Meaning put the sucker on the sd card and click install with root explorer or the like.
Click to expand...
Click to collapse
Thanks, I was just kidding. I used easy install and it's already installed.

Wifi calling, MIUI, and CM7

Okay so I Wifi calling doesn't work on MIUI because of the newer sim card, but CM7 does work and MIUI is CM7 based.
But the miui build for g2x comes from a native CM7. My guess is that something is done to CM7 to get it working in the g2x code tree that could be done to the miui g2x port?
I will research it, but there might be coders that have better resources than I do.
Either way, this has to be possible and we should make it happen.
Sent from my LG-P999 using XDA App

+1
Sent from my LG-P999 using xda premium

derekedw said:
Okay so I Wifi calling doesn't work on MIUI because of the newer sim card, but CM7 does work and MIUI is CM7 based.
But the miui build for g2x comes from a native CM7. My guess is that something is done to CM7 to get it working in the g2x code tree that could be done to the miui g2x port?
I will research it, but there might be coders that have better resources than I do.
Either way, this has to be possible and we should make it happen.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Sadly it doesn't work that way. Developers tried everything. But we're not stopping till we get it working.

G2x doesn`t get along with the newer sim cards! I changed 10 sims for 2 weeks until I found Sim TM9073. This is the right sim for our phone! Wifi Calling is flawless with it! I`ve been using CM7 since I got the phone last summer!
It`s not easy to find that specific sim card, when you tell the people at the store what you are looking for, they don`t really know what you are talking about....

all reps I spoke to months ago said they don't make the old sim cards anymore so you wont be able to get one from a store. I was able to grab a brand new old style sim fro. ebay and solved my wifi calling problem months ago hit up ebay and see if you can find one. make sure its brand new never been activated.

derekedw said:
Okay so I Wifi calling doesn't work on MIUI because of the newer sim card, but CM7 does work and MIUI is CM7 based.
But the miui build for g2x comes from a native CM7. My guess is that something is done to CM7 to get it working in the g2x code tree that could be done to the miui g2x port?
I will research it, but there might be coders that have better resources than I do.
Either way, this has to be possible and we should make it happen.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Wi-Fi calling is working perfectly on miui, it has nothing about newer SIM !

cgigate said:
Wi-Fi calling is working perfectly on miui, it has nothing about newer SIM !
Click to expand...
Click to collapse
You got Wifi calling to run on MIUI with new sim card? Please tell how...I have tried installing the wifi calling apk to /data/app and also tried pushing it to /system/app and got nothing but FC's either way...someone please enlighten me here. Thanks!

pettigrew95 said:
You got Wifi calling to run on MIUI with new sim card? Please tell how...I have tried installing the wifi calling apk to /data/app and also tried pushing it to /system/app and got nothing but FC's either way...someone please enlighten me here. Thanks!
Click to expand...
Click to collapse
I've heard that if you have a T-Mobile tech support rep use the command "Send MSISDN To SIM" which is located in IHLR (or it was when I used to work there years ago), that it will fix it. However, I have not wanted to navigate their now horrible phone support to get far enough to have someone do it.

Are you guys using t-Mobile wi-fi calling app or something else?
Sent from my MIUI LG-P999 using Xda Premium

"G2x doesn`t get along with the newer sim cards! I changed 10 sims for 2 weeks until I found Sim TM9073."
Mine is Tm9073 but MIUI is not working but its working for my wife's G2x.
So SIM TM9073 is not guaranteed.
So for now: I am using CM7 (nightly) until this is fixed.

alright. i'm not a android dev (i am a programmer but another language than java). here is what i found in my testing and how i was able to get wifi to work..perhaps others can confirm. the problem is delvik cache and wifi being enabled when the phone is restarted.
here is how i was able to get wifi to work on mine consistently (some of the miui dev should take it from here and see if they can resolve the issue).
1) turn off wifi on the phone
2) shut down phone
3) boot into clockwork mod
4) clear delvik
5) reboot phone
6) enable wifi
7) wifi calling works
you will have to do this every time you reboot the phone otherwise wifi calling will not work.
i also tried to see if the issue was resolved by "fix permissions" and it was not. here were my test (also note..when i say reboot recovery...i shut down the phone then go to recovery..not recovery from restart script).
1) wifi on...reboot recovery..delvik clear..reboot-- no wifi calling (invalid sim)
2) wifi on..reboot recovery..permission fix..reboot -- no wifi calling (invalid sim)
3) wifi on..reboot recovery..delvik clear + permission fix..reboot -- no wifi calling (invalid sim)
4) wifi off..reboot recovery..delvik clear..reboot = WIFI calling
i going to also try the following
wifi off..reboot recovery..fix permission..reboot and see if that does anything.
**update** wifi off...reboot..-- just did this one and wifi calling doesn't work..invalid sim.
and i'm going to assume that if you do both with wifi off it will work.
a possible solution: someone create a script for shutdown/restart that turns off wifi (also save a variable stating that wifi was enabled) and also create a script for startup that clears delvik and enables wifi if it was on previously (not sure if you can save a variable on the next reload).
Update: this last go around was strange...i think there is also something with the state of wifi at the time the phone is rebooted. if you never turn on wifi then different settings need to be changed at bootup. i'll mess with it some more to confirm.

That didnt work for me......

lithivm said:
That didnt work for me......
Click to expand...
Click to collapse
what were your exact steps? did you have wifi ON when you turned off your phone? if not you will have to do a 2nd wipe with wifi OFF then turn on wifi. Its very finicky but it does work.
The last version 2.1.20 works the first time but messes up when you reboot unless you do wipe of delvik cache. I would also wipe cache aswell.
if you leave your wifi on, then just a single wipe works..if you are messing with your wifi to on and off state it sometimes require 2 wipes...with the same wifi state on the reboot (hope that makes sense).

jblah said:
what were your exact steps? did you have wifi ON when you turned off your phone? if not you will have to do a 2nd wipe with wifi OFF then turn on wifi. Its very finicky but it does work.
The last version 2.1.20 works the first time but messes up when you reboot unless you do wipe of delvik cache. I would also wipe cache aswell.
if you leave your wifi on, then just a single wipe works..if you are messing with your wifi to on and off state it sometimes require 2 wipes...with the same wifi state on the reboot (hope that makes sense).
Click to expand...
Click to collapse
This method confirm works.
The wifi calling can be turned on but could not be turned off.it still shows as invalid sim so i could not change the state of the on off switch.

What got to work for me was this:
With Wifi turned-off, Reboot straight into Recovery
Wipe Dalvik Cache in Advance Settings 3x (Three Times)
Hopefully when you reboot and you click on the Wifi Calling app it says either Turned OFF or Disabled. That's how you know you won't get the INVALID SIM error.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If it says Checking Sim, Then Repeat the Steps above again and it may take a couple tries which I had to do cause it didn't do it the first.
I remember back in the days of when MIUI first came out and I had a N1 & an NS the guys at MIUIandroid would recommend wiping 3x whenever you do updates. I guessing because a single wipe for some reason still leaves something behind.
Try That Out Fellows and Hopefully It works for some of you.

GFam4 said:
What got to work for me was this:
With Wifi turned-off, Reboot straight into Recovery
Wipe Cache 3x (Three Times) in CWM
Wipe Dalvik Cache in Advance Settings 3x
Format Cache 3x in Mounts
Hopefully when you reboot and you click on the Wifi Calling app it says either Turned OFF or Disabled. That's how you know you won't get the INVALID SIM error.
If it says Checking Sim, Then Repeat the Steps above again and it may take a couple tries which I had to do cause it didn't do it the first.
I remember back in the days of when MIUI first came out and I had a N1 & an NS the guys at MIUIandroid would recommend wiping 3x whenever you do updates. I guessing because a single wipe for some reason still leaves something behind.
Try That Out Fellows and Hopefully It works for some of you.
Click to expand...
Click to collapse
do you have problems on reboot? or does it stay consistent?
also when you say wipe 3x are you saying BEFORE you install the ROM or after you install it and see that you have "invalid sim"?

jblah said:
do you have problems on reboot? or does it stay consistent?
also when you say wipe 3x are you saying BEFORE you install the ROM or after you install it and see that you have "invalid sim"?
Click to expand...
Click to collapse
With MIUI Rom you kinda have to expect inconsistency. If you've been following any Wifi Calling topic for the G2X with MIUI ROM you know its 50/50.
My Scenario basically is saying that If you currently are running MIUI Rom and IF it worked after intial install. Then when you rebooted (for whatever reason) and you get the Dreaded "Invalid Sim" error then my Steps that i followed helped me to get my Wifi Calling to work again.
The 3x wipe is after the install of rom if you lost the ability to use Wifi Calling. Now it doesn't hurt to do it (3x wipe) before if It may help you get Wifi Calling to work.

Just tried it again with just Wiping Dalvik Cache 3x in Clockwork Recovery. It was a success!! This is the 5th time I've tried it and hasn't failed yet.
I am currently running Stormmagedon's MIUI 2.1.20 with Faux .48 kernel and I have sim card # TM9073
Hope This Helps Someone.

GFam4 said:
Just tried it again with just Wiping Dalvik Cache 3x in Clockwork Recovery. It was a success!! This is the 5th time I've tried it and hasn't failed yet.
I am currently running Stormmagedon's MIUI 2.1.20 with Faux .48 kernel and I have sim card # TM9073
Hope This Helps Someone.
Click to expand...
Click to collapse
Are you wiping after each reboot? also at the time of reboot are you leaving wifi on or off? i got it to work but i think i'll have to keep wiping at every reboot. also since we are on miui...i don't have a camera app anywhere (using stock miui.us)..what is everyone using as their camera app for miui?

jblah said:
Are you wiping after each reboot? also at the time of reboot are you leaving wifi on or off? i got it to work but i think i'll have to keep wiping at every reboot. also since we are on miui...i don't have a camera app anywhere (using stock miui.us)..what is everyone using as their camera app for miui?
Click to expand...
Click to collapse
Yes if you reboot your phone you will have to do the 3x wipe of dalvik cache again. I usually just leave my phone on all the time. I've been doing this with Wifi Off dunno if it makes any difference if ON or OFF. As far as camera, i have both CM7 & MIUI cam. Check the other Roms out there. Im on Stormageddon 2.1.20 and he has both cameras and Wifi Calling. Some MIUI roms leave out the Wifi Calling because of the issues.
Hope This Helps.

Sweet Chiid Of Mine Q&A Thread

In an effort to keep SCOMs dev thread clean and streamlined please post all of your questions here.
Thanks

No luck with your suggestion hechoen. Running GR again (even though I did that before this flash) and will reflash. Checked the MD5 and that's good.

im still experiencing lagging with scrolling. i did gremlin remover then flashed ROM and it was smooth, but when i rebooted the phone, it started lagging with scroling again. if i do a factory reset from CWM, do i have to reflash the ROM or just reboot after the do the factory reset?

native
Just reboot. I'm running into some issues as well. It seems to only happen after I power down and reboot. Very odd. So factory resest from CWM, reboot and play with the phone. Don't restore any apps yet. If it seems smooth reboot the phone. Let me know whether the lag reappears after the second reboot.

hechoen said:
native
Just reboot. I'm running into some issues as well. It seems to only happen after I power down and reboot. Very odd. So factory resest from CWM, reboot and play with the phone. Don't restore any apps yet. If it seems smooth reboot the phone. Let me know whether the lag reappears after the second reboot.
Click to expand...
Click to collapse
i already restored the apps at the beginning with TB and it was smooth, but after the reboot, it started lagging with scrolling again.

Kyndig66 said:
No luck with your suggestion hechoen. Running GR again (even though I did that before this flash) and will reflash. Checked the MD5 and that's good.
Click to expand...
Click to collapse
That's what worked for me. One other thing that I think has worked for some on other ROMs with this issue is to turn on bluetooth and while it's doing it's thing reboot the phone. If that doesn't work get a log to erikmm and he'll let you know what else to try.

hechoen said:
That's what worked for me. One other thing that I think has worked for some on other ROMs with this issue is to turn on bluetooth and while it's doing it's thing reboot the phone. If that doesn't work get a log to erikmm and he'll let you know what else to try.
Click to expand...
Click to collapse
Tried that before posting my Q in the SCOM thread. Tried a myriad of combinations also. It used to be a problem for a lot of people at one time. It never occurred with vb final fixed or unnamed. If this next go doesn't work, I'll get a log.

native
I'm having the same thing happen. After second reboot laggy and super unresponsive. If someone else running this wants to reboot and see if they pick up lag as well it would be appreciated. If no one else is having this issue it has to be one of the apps that we are restoring causing it. I'm still trying to figure it out myself.

hechoen said:
Where do you get this stuff? I've reset from inside the OS on plenty of occasions and never had anything bad happen. My next suggestion to native if this doesn't work was gonna be to factory reset it from inside the phone.
Click to expand...
Click to collapse
Every phone I have had the devs state to never do a factory reset from the setting menu. My last phone there was many people with broken phones because they used the privacy menu reset. I dunno I just prefer not to waste 300bucks wiping data improperly. I also would hate to see somebody post doing it broke their phone.
If you can safely wipe data from the privacy menu then I stand corrected.

Kyndig66 said:
Tried that before posting my Q in the SCOM thread. Tried a myriad of combinations also. It used to be a problem for a lot of people at one time. It never occurred with vb final fixed or unnamed. If this next go doesn't work, I'll get a log.
Click to expand...
Click to collapse
I just tried bluetooth with wifi on and it hung on turning on. Rebooted and it worked. Both wifi and bluetooth. Now if I can figure out why restoring and rebooting is causing lag I'll be really happy.

just had my first reboot and its lagging again. the reboot happened by itself

hechoen said:
I just tried bluetooth with wifi on and it hung on turning on. Rebooted and it worked. Both wifi and bluetooth. Now if I can figure out why restoring and rebooting is causing lag I'll be really happy.
Click to expand...
Click to collapse
Wierd. Im lagging also and i havent restored anything. Only apps i installed are log this and xda. Working on logs for eric.
Sent from my SGH-T959V using xda premium

hechoen said:
Now if I can figure out why restoring and rebooting is causing lag I'll be really happy.
Click to expand...
Click to collapse
What method are you using to restore?
When I updated to unamed v2 I had three reboots after restoring some apps. I wiped reflashed and installed them one at a time until it rebooted. Then removed that app and continued. No reboots. So I wiped ran gremlin remover. Flashed again installed the offending app. No reboots. I installed the app prior to the offending one and bam reboot. Come to find out the issue was created by a update to the two apps not properly updating. I did a fresh install from the market and have had no problems.

Anybody having issues with little to no volume in calls? I have tried data/factory reset from cwm and also fixed permissions.
FYI, I just flashed the rom again to see if that will fix it. soaking in now.

OK so here's what I've come up with to fix the lag issue for me. Flashed the rc2 kernel and lag is gone. I've rebooted a number of times to make sure this is the case and every time quad runs at full FPS. I've restored all my apps with TB and have this running perfectly smooth. So a guess would be something with the new kernel or SuperSU. Again this is a guess. But if you want to run SCOM V3 lag free and have TB restore all your stuff for now reflash the RC2 kernel.
EDIT: Scratch that theory. Lag is back. I should have never doubted are kernel devs. For those of you getting logs that use ADB here's a great guide.
http://forum.xda-developers.com/showthread.php?t=1378491
This may work in terminal emulator as well. I'm short on time today so I'm going to reflash and not reboot anymore! Just hang in there and it will get figured out.

Thanks for the info on the Kernel being the possible culprit.

Sorry about all the problems guys but im running v3 no lag but im checking on it still
for bluetooth issue raver just told me to try turn bluetooth on and reboot phone
---------- Post added at 05:48 PM ---------- Previous post was at 05:37 PM ----------
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
check it out just reflashed and got both to turn on ok
and no lag after 3 reboots

erikmm said:
check it out just reflashed and got both to turn on ok
(
Click to expand...
Click to collapse
Not sure why, and I don't care why, but both bt and wifi are working concurrently for me after the 3.5 flash. The bt device doesn't connect unless i go into bluetooth setting and press the paired device, which is fine. Thanks erik!
Edit: Device connects like usual now. Guess I didn't wait long enough.

v3.5 installed
Downloaded and installed v3.5 on my phone last night. All functions seem normal and working great. I have OC'd to 1.3 and have no issues with battery temp.
If I may, Erik has been especially patient and extremely helpful. I did have an issue with a previous version of SCOM and he was readily available and willing to help out. It is very comforting to know that as some great dev's leave the SGS4G community some other good/great dev's are coming in to fill the void. Erik, I appreciate your hard work and your ROM reflects your passion and hard work. You ROCK!

After a horrific 15 hour period of pulling my hair out, I finally got my phone out of a hardbrick apparently initiated by installing Sweet Child O Mine v3.5. Here's how I got there:
1. When flashing SCOM v3 (following OP precisely), the phone randomly rebooted (around 90% of Aroma installation).
2. When attempting to flash again, Aroma Installer gave a warning saying it did not recognize my phone as a SGS4G. I clicked the checkbox and installed anyway. ROM worked.
3. When trying to upgrade to SCOM v3.5 late last night, I wiped all data and flashed. Got the same warning as before. This time, didn't install.
4. Tried using Gremlin 1-Click before attempting again... Kept getting stuck on factoryfs.rfs. Had to pull the battery multiple times to try to get it to work, but eventually it caught.
5. Tried flashing SCOM v3.5 again... crapped out before Aroma Installer could finish. I started again, got the unrecognized device warning again.
6. Went back to Gremlin 1-Click again... this time, could not get it to catch! Phone was stuck in softbrick.
7. After multiple attempts, decided to try Heimdall 1-Click, to no avail. Checked off "flash bootloaders" and after 3rd attempt, phone went hardbrick (screen wouldn't turn on no matter what I did).
Stayed up until 5 am trying to fix it, but put it aside to work on it again today. Here's how I finally fixed it:
1. Found RaverX3X's 1-Click somewhere on the forums... removed CWM and put me back on Samsung Utils
2. Downloaded all the files from FB's GB Ext4 starter pack page.
3. Managed to get the phone to yellow triangle by: Pulling and replacing battery->Holding Vol + and Vol - ->Inserting USB
4. Ran Odin as Admin, but had to use a different cable and port to get computer to see the phone
5. Finally back on stock KJ6.
Hopefully all that info above will help someone in trouble like I was.
Now I have a new problem: I want to flash SCOM v3.5 again, but I'm afraid of getting soft/hard-bricked again!
To be honest, I dislike the color scheme and the mismatched icon set in SCOM, but it has two things going for it:
1. Smooth as butter (surprisingly, smoother than RaverX3X's VB final for me)
2. Battery life when NOT using phone is amazing (left the phone for a few hours yesterday, didn't move a single percent). The battery drains fairly quickly when phone is in use, however.
So, how do I instally SCOM v3.5 without falling into the same problems? Or, alternately, what other ROM is comparable in terms of smoothness and idle battery life?

OnePlus One Malfunction? Help please

G'day people I've run into something pretty weird with my OnePlus One. I installed the CM12 nightly and booted it up, ran it for a few hours then got ghost touches and the screen became unresponsive at times.
So, having my usual backup of CM11S, I wiped and restored to the latest backup I had and everything was weird. I kept getting ghost touches and reduced responsiveness, and sometimes it would just randomly malfunction and not unlock and just keep the screen off.
Rebooting clears up the problem for about 5 minutes and then it comes back at full blast.
I tried installing the last CM11S update via flashing Calkunins stock XNPH44S zip and still I have all these weird issues that wasn't there before I flashed the CM12 nightly.
Has anyone come across this problem or is it just me and my device? It's seriously a cause for concern, and I'm posting this to both XDA and the OnePlus forums in hopes of getting some sort of help and relief in this situation.
Any assistance is appreciated and I thank you in advance for taking the time to read this.

reflash cm12 nightly and try again.
perhaps use fastboot to flash the partitions .
You might need to find a copy of the first cm11s rom and try that one. I have a feeling your one of the unlucky with firmware sensitivity.
Which date is your phone from? (its on the box)
Sent from my A0001 using XDA Free mobile app

GO back to completely factory fresh, via fastboot commands.
If you still have problems, it's a hardware issue then.

kthejoker20 said:
GO back to completely factory fresh, via fastboot commands.
If you still have problems, it's a hardware issue then.
Click to expand...
Click to collapse
not entirely true, there are different screens, that could be the issue. It was reported in boeffla kernel thread. sesrch throught it and it might contain something useful to try.
also open a support question, Oneplus needs to know how annoying their poor choice of different lcds are
Sent from my A0001 using XDA Free mobile app

bachera said:
reflash cm12 nightly and try again.
perhaps use fastboot to flash the partitions .
You might need to find a copy of the first cm11s rom and try that one. I have a feeling your one of the unlucky with firmware sensitivity.
Which date is your phone from? (its on the box)
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
I'll try to flash CM11S via fastboot to see if it clears up the issue. For now, the date I got mine is 2014-07-16. Shipped to me after 12 days (International shipment via courier)

UPDATE
Flashing CM11S via fastboot resolved all issues as far as I can tell.
Will remain on the lookout for the bugs in the future but for now I'm happy to say it worked for me.
Thank you all again for the advice and guidance, it was appreciated.

GLad it worked for you.
I love when other posters try to punk you when you try to help people.

kthejoker20 said:
GLad it worked for you.
I love when other posters try to punk you when you try to help people.
Click to expand...
Click to collapse
Nobody was trying to "punk" you. There are usually several different potential causes for the same symptom, all he was doing was highlighting that and adding extra information in order to help further (in the case that flashing the stock images didn't help, which has happened many times). He was also trying top help the OP. Calm down.
Transmitted via Bacon

timmaaa said:
Nobody was trying to "punk" you. There are usually several different potential causes for the same symptom, all he was doing was highlighting that and adding extra information in order to help further (in the case that flashing the stock images didn't help, which has happened many times). He was also trying top help the OP. Calm down.
Transmitted via Bacon
Click to expand...
Click to collapse
I thought it was the partition thing too because I had almost the same problem on my HTC Amaze back in 2014, and flashing the OEM RUU helped with sorting things out.
But as for the random screen touches, flashing everything from fastboot helped for only a few hours. The symptoms came back after a while, specifically when I replaced my music and pictures. I'm thinking that I may have a corrupted file on it somewhere but I doubt it'll cause a malfunction like that.
So I tried flashing Franco Kernel, and it seems to have cleared it up..... for now.
It's so frustrating thinking that my device may be defective

UPDATE #2
Flashing Franco Kernel didn't help. Symptoms came back within a couple hours. Will try a custom ROM, specifically AOPK (because I want to )
If that doesn't fix the issue then I've just got to face the fact that I have a defective device (somehow)

Bump
Nothing worked. I contacted the manufacturer but they seem to think doing a factory reset will help. It didn't.
Flashing CM11S via fastboot doesn't help
I really think this is a hardware issue that just emerged from nowhere, probably due to lack of premium or standardized quality adhesive.
There's a really long thread over at the OnePlus forums about a guy who found it was a grounding issue and took some adhesive tape to insulate the area near the proximity sensor (I think? I'll include the link in here somewhere)
Honestly, OnePlus impressed me....at first. But I cannot use a phone that's not working properly.
https://forums.oneplus.net/threads/...-hint-it-was-never-a-software-problem.186235/

Same problem here... I had the first ghost touches after having installed CM12 Nightly.
I was using CM12 built by Daleski75 so far without any issue. The problem does not appear on a regular basis and when it does, a reboot seems to fix it, at least for a few minutes/hours.
I'll try a clean install when the stable version is out (don't really want to wipe now and once more in two/three weeks).
@rdar_93: Did you find a solution? Are you going to send the device back to OnePlus? If it is actually a hardware issue, that will be enough for me, no more OPO. Sending the device back to China after 2 months of use and having to pay for the shipping is not acceptable.
Edit: It's getting worse... I am gonna wipe soon. Here is a short video: drive.google.com/file/d/0B-EYHGTB15_wS1JXdXlmZXVsT0k/view?usp=sharing
I can't post link for now so you'll have to copy and paste it in your browser.
Edit2: After a full wipe and the installation of the latest nightly, the situation seems to be better, even though I will have to use the phone a bit more to see if it happens again. By the way, I lost dt2w and the gestures don't work well, if not at all... When I draw a V, nothing happens, when I draw a circle, the phone behaves as if I did a double tap. Weird. Again, this happens after a wipe+latest nightly installation+wipe again (to be sure ).

sylvain15250 said:
Same problem here... I had the first ghost touches after having installed CM12 Nightly.
I was using CM12 built by Daleski75 so far without any issue. The problem does not appear on a regular basis and when it does, a reboot seems to fix it, at least for a few minutes/hours.
I'll try a clean install when the stable version is out (don't really want to wipe now and once more in two/three weeks).
@rdar_93: Did you find a solution? Are you going to send the device back to OnePlus? If it is actually a hardware issue, that will be enough for me, no more OPO. Sending the device back to China after 2 months of use and having to pay for the shipping is not acceptable.
Edit: It's getting worse... I am gonna wipe soon. Here is a short video: drive.google.com/file/d/0B-EYHGTB15_wS1JXdXlmZXVsT0k/view?usp=sharing
I can't post link for now so you'll have to copy and paste it in your browser.
Edit2: After a full wipe and the installation of the latest nightly, the situation seems to be better, even though I will have to use the phone a bit more to see if it happens again. By the way, I lost dt2w and the gestures don't work well, if not at all... When I draw a V, nothing happens, when I draw a circle, the phone behaves as if I did a double tap. Weird. Again, this happens after a wipe+latest nightly installation+wipe again (to be sure ).
Click to expand...
Click to collapse
I contacted them and they sent me a program to use. It uses fastboot to flash CM11S and probably fix the partitions that are messed up (I'm making an assumption)
UNFORTUNATELY I'm stuck in a bootloop.
I'm so angry, disappointed and depressed at the same time. I paid about $2500 TTD (in my country) which is probably the equivalent to somebody's rent. I had to work a month to save up the money to buy this and it turns out that the device is faulty after a certain amount of time (or at least mine was)
This is BS.
They said to send them a snapshot of what went on with the fastboot thing, so I figure I"ll upload it here too.

rdar_93 said:
I contacted them and they sent me a program to use. It uses fastboot to flash CM11S and probably fix the partitions that are messed up (I'm making an assumption)
UNFORTUNATELY I'm stuck in a bootloop.
I'm so angry, disappointed and depressed at the same time. I paid about $2500 TTD (in my country) which is probably the equivalent to somebody's rent. I had to work a month to save up the money to buy this and it turns out that the device is faulty after a certain amount of time (or at least mine was)
This is BS.
They said to send them a snapshot of what went on with the fastboot thing, so I figure I"ll upload it here too.
Click to expand...
Click to collapse
I guess you didnt unlock bootloader first
Which when you do wipes the phone so you loose all your stuff.
possible workaround is fasboot on custom recovery and then flash the zip that sets unlock status and circumvents the whole format thing
Sent from my A0001 using XDA Free mobile app

bachera said:
I guess you didnt unlock bootloader first
Which when you do wipes the phone so you loose all your stuff.
possible workaround is fasboot on custom recovery and then flash the zip that sets unlock status and circumvents the whole format thing
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
I actually did unlock my bootloader.
PS I also got tired of seeing CM11S try to boot up so I flashed ColorOS (because it's the only rom I had on my laptop. Why not download another 4.4.x AOSP rom? Unstable wifi at school)
So yeah, wifi is not turning on. Gonna try the program again. I wonder if it would work this time?
The conditions aren't as different as before, could work, right?
Honestly I want to wait but they take so long to reply.

UPDATE
After flashing ColorOS I decided to go back and try doing the CM11S via fastboot commands. Still got a bootloop but hey I got the correct fastboot logo now in case if it made a difference.
So I did the compulsory flashing commands when I went from Color to CM11S and still bootlooped.
So I booted into fastboot again
fastboot oem unlock (supposed to unlock bootloader and reboot if it's locked, no reboot if unlocked [assumption])
then rebooted into fastboot again, ran the batch files OnePlus sent to me which essentially flashed CM11S just like you would over fastboot, but with added modems etc.
Successfully booted into CM11S without issues, WiFi works again and so far no symptoms as yet.
Will keep this post updated if anything happens.
My screenshots of the batch file commands OnePlus sent would be found in the attachments.

UPDATE 2
So I think it's fixed permanently this time.
I'm not sure though. It hasn't done anything weird. I will copy my music and photos to see if that would cause anything to happen

I would stay away from os since it messes up partition and people ran into data drop out and modem issues.
Cm11s Roms are the way to go on this hardware.

FYI, when you flash CM12 the radio is overwritten with an alpha/beta radio which causes (well, caused for me) THE EXACT issues OP was having in CM11/S. The CM12 radio (as far as I can tell) ONLY works with CM12 - making going back a PITA.
If you have the baseband in this thread (see screenshot in first post) then that means you are on the experimental radio and are going to have a bad time if you aren't on CM12.
I flashed the latest OTA radio found here and all was right with the world (at least where my OPO was concerned ).

hp13 said:
I would stay away from os since it messes up partition and people ran into data drop out and modem issues.
Cm11s Roms are the way to go on this hardware.
Click to expand...
Click to collapse
I would like to go back to CM11s to check if the situation is better. I tried to flash the lastest CM12 build and it seems to be better but still not as good as before
When I do a wipe and then flash the ROM in TWRP, there are some "folder already up to date", which I would like to avoid. What I would like to do is doing a complete clean install of either CM12 or CM11s plus rewriting the partitions,... So that I'm sure if the problem is still here it is due to an hardware issue.
Is there any chance someone can help me with this? Even with a link... I searched for "write partition" without any luck :-/
Thanks !
EDIT: Do you think the OnePlusRecovery Tool can help me with this?

Gps broken

i have a nexus 5 that is completely stock. I used to have it rooted but decided to go back to stock for lollipop. I am running android 5.1. Since I have had lollipop I have zero gps capability. I feel like I have read every thread on the subject and tried every suggestion, but I can never get the gps to lock.
I have tried the. Card stock gps antenna fix, didn't work.
I tried factory reset
I tried device only
I have used gps test and fix
I have used gps status and toolbox
I tried safe mode
I tried mapquest
Bottom line my gps doesn't work at all, it used to, but not anymore. Any ideas on what to do?

Same thing here and I also tried most of what you describe --- 5.1 (LMY47D), clean install (no OTA).

Select high accuracy

What does GPS status show? Flat lines for all satellites? What is the setting you're using for downloading the assistance data?

I used GPS Test and GPS Status -- here are two screenshots: i.imgur.com/o2B5QCk.png
Meanwhile I flashed LMY47I and re-installed everything from scratch. It still feels sluggish but now I can get at least a GPS fix after a couple seconds. Hope it stays this way.

ThDeK said:
I used GPS Test and GPS Status -- here are two screenshots: i.imgur.com/o2B5QCk.png
Meanwhile I flashed LMY47I and re-installed everything from scratch. It still feels sluggish but now I can get at least a GPS fix after a couple seconds. Hope it stays this way.
Click to expand...
Click to collapse
The only solution seems to be this one: https://www.youtube.com/watch?v=QBpNtWvY454 (confirmed here)
I also tried several tricks and nothing works.

What is the easiest way to do a complete wipe and flash to the latest version of android to see if that will fix it?

jongordo8 said:
What is the easiest way to do a complete wipe and flash to the latest version of android to see if that will fix it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
The above hardware trick worked for me though (and optimizing the gps.conf file for my region/country).

Primokorn said:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
The above hardware trick worked for me though (and optimizing the gps.conf file for my region/country).
Click to expand...
Click to collapse
Thanks for the tip...optimizing the gps.config file is something I have not doen. Can you provide speifics n how you go about doing that? I will try that before I wipe it and start fresh.

jongordo8 said:
Thanks for the tip...optimizing the gps.config file is something I have not doen. Can you provide speifics n how you go about doing that? I will try that before I wipe it and start fresh.
Click to expand...
Click to collapse
Read this: http://forum.xda-developers.com/showthread.php?t=1239713
Until 'Extra Suggestion.....' I didn't try Leo AGPS Injector BTW.

I just wanted to update everyone...I wiped the phone clean and flashed the phone to the latest stock. GPS issues remained, so I rooted it and tried the GPS.config tip and it didn't help either. Then I downloaded FasterGPS and used it (basically does the same thing the GPS trick linked above does) and now it works again. It takes about a minute for it to lock so it isn't super fast to lock, but it works and I have not heard the GPS signal lost since I did FasterGPS.
Thanks for all the advice and suggestions.