Database Develop

g1 calling out issues

I have a rooted g1. My issues is that when I call out, there is no dial tone and I can't hear the people I'm calling but they can hear me. They text me that the call went through but I can not here them. When the phone was not rooted and when I used cm 3.9.7 the phone was fine. I updated to cm 4.0.2 and the issue started to occur. Now I am currently running jacxrom r3 and it worked fine for a little bit then went back to the same issue. Does anyone have this problem? Is it a rom issue or a phone issue?
Thanks all
Meeow Meeow

I would go back to a state where it did work. Either the older CM or the factory default (or both). If you are still having issues then it's probably a phone issue.

are you running apps 2 sd, did you wipe your phone before switching, did you wipe your sdcard partitions before switching? probably has something to do with the different dialer apks messing eachother up. That's my guess anyways.

thanks for the response folks. yes to everything you guys said except going back to factory. that will be my next shot.

Do you have the newest radio installed?

yes i do...if i didnt, jacxrom wouldnt work right?? either way i do because i got it off of his thread

Random reboots

So a friend of mine gave me a htc one which works perfectly fine unless you keep wifi on while the screen is off.
It'll reboot within a minute after you turned the screen off. Did some googling, but couldn't find anything about it.
Tried different roms and kernels, but nothing fixed it so far. Currently I'm running santods gpe lollipop on kk sense firmware.
Maybe upgrading to latest sense firmware would help (which I currently can't do as I have no access to a computer)? Or do you guys think it's a hardware issue?

If it was a software issue, I think more people would have this problem. So...
Try going back to stock.

Already flashed back to stock, didn't help.
And yeah, I knew it's most likely a hardware issue, but I thought I tried asking anyway.

[Q] No sensors - Stock 5.1

Hi all
So I flashed LMY47I onto my Google play Nexus 6, and now all the sensors (brightness, prox, gyro) are disabled. These were working fine before the flash and flash went well.
A few apps from Google play agree that my phone do not have any sensors. This makes me think its not some hardware issues since these are independent sensors.
I have tried clean flash, full wipe, but no changes.
Any ideas? Search in the forum only returns some Samsung stuff.
Thanks in advance
2015/04/25 Update:
Reflashed a few different unofficial roms, as well as official 5.1.0 one last time with full wipe and factory reset. Nothing worked.
Since I feel like I've already spent enough time on this, I just gave up and called google. Quick 5 minutes phone call and a replacement is on its way! At least the service is good :good:

shinysword said:
Hi all
Thought I posted, but don't think it went through, will delete this thread if the original eventually shows up!
So I flashed LMY47I onto my Google play Nexus 6, and now all the sensors (brightness, prox, gyro) are disabled. These were working fine before the flash and flash went well.
A few apps from Google play agree that my phone do not have any sensors. This makes me think its not some hardware issues since these are independent sensors.
I have tried clean flash, full wipe, but no changes.
Any ideas? Search in the forum only returns some Samsung stuff.
Thanks in advance
Click to expand...
Click to collapse
I had the same issue originally with my pre-order unit, I ended up having to RMA it. No matter what I did, I could never get the sensors to start working again. I ended up taking a friends phone, grabbing his entire partition layout and stock dump and it still did not work.

I posted on here with what I think is the same issue. I noticed it with the accelerometer first because screen rotation stopped working, then I realized the compass wasn't working either. I hadn't noticed the light and proximity sensors, but after reading your post I checked and it seems those are broken too. I see the same thing that you are; apps seem to think my phone has no sensors at all. I checked the system logs and it seems that it throws some kind of access denied error when trying to use the sensor API. I haven't been able to fix it in 5.1, however, when I first noticed the issue I flashed the 5.0.1 image and they seemed to be working again (screen rotation worked at least) so I'm pretty sure the hardware is okay. I have just been using my phone with broken sensors, but it's really annoying.

Nopcodex90 said:
I had the same issue originally with my pre-order unit, I ended up having to RMA it. No matter what I did, I could never get the sensors to start working again. I ended up taking a friends phone, grabbing his entire partition layout and stock dump and it still did not work.
Click to expand...
Click to collapse
Hm, can you share your RMA process with Google? Did you get in touch with them through call or email?

Herohtar said:
I haven't been able to fix it in 5.1, however, when I first noticed the issue I flashed the 5.0.1 image and they seemed to be working again
Click to expand...
Click to collapse
Wow, let me try flashing back 5.0.1 and see what happens. Thanks for the info!

shinysword said:
Wow, let me try flashing back 5.0.1 and see what happens. Thanks for the info!
Click to expand...
Click to collapse
Any luck? If yes, perhaps you could try a custom 5.1 or 5.1.1 rom and see if the sensors work.
You could play it safe by flashing one of the stock-based custom roms in the development forum.
Sent from my Nexus 6 using Tapatalk

micmars said:
Any luck? If yes, perhaps you could try a custom 5.1 or 5.1.1 rom and see if the sensors work.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Have to wait until weekend. Only a business trip and don't have access to my personal computer.
That being said. Definitely a problem if stock image doesn't work... Hm... still considering RMA.
Will report back either way though!

shinysword said:
Wow, let me try flashing back 5.0.1 and see what happens. Thanks for the info!
Click to expand...
Click to collapse
shinysword said:
Will report back either way though!
Click to expand...
Click to collapse
You're welcome. It'll be interesting to see if 5.0.1 works for someone else. Up until now it looked like I was the only one who had this issue.

shinysword said:
Hm, can you share your RMA process with Google? Did you get in touch with them through call or email?
Click to expand...
Click to collapse
My RMA process was handled through ATT since it was a pre-order item from them originally. I ended up trying CM12, stock and reflashing the PIT, nothing seemed to correct it so I just wanted to get a new unit as fast as possible.

micmars said:
Any luck? If yes, perhaps you could try a custom 5.1 or 5.1.1 rom and see if the sensors work.
Click to expand...
Click to collapse
Didn't work unfortunately.
I've updated the op. Basically I just called up Google and asked for replacement.

Sorry to bump and resurrect a dead thread -- my accelerometer stopped working after I accidentally dropped it on my hard wood floor.
I was able to get it working again by dropping it from 2.5 feet onto my carpet. I know it sounds crazy and dumb -- but that was my last resort before calling Google for a replacement.
All is working perfectly now.
It happened when I dropped my phone in my Carved case. I have dropped it accidentally with a spigen case (2 layers) never had a problem. Not blaming the case but pointing out the correlation.

No push notifications

I'm sorry if I put this in the wrong thread. But I'm not sure where to put it.
Anyway,
>Nexus 6
>Rooted
>Custom rom (euphoria)
>Lollipop 5.1.1
I've had a nexus 5 and trust me, I've done my fair share of soft bricking. Over 50 times. Not even kidding. So I'm not new to rooting or anything like that. And I've rooted my nexus 6 properly. I've even unrooted it and lock the OEM and redid all of it. Thought I did something wrong so looked up a video and I did everything right. Ive tried the PNF Root (and no root) Notification fixer (even both of them together) and they don't work. I've uninstalled greenify because I know that can mess with it, I've tried removing my account and adding it back, I've honestly done anything I can think of. The only thing I haven't tried was to flash stock and see what it does. But before I had Xenon rom and before that I had liquidsmooth and before that I had Purity and they all did the same. So I don't think it's the rom. I've tried to look around and all I've found was delayed notification. They're not delayed, I'm not getting them at all.

Problem has seemed to be fixed when I flashed a different kind of gapps. I flashed Blackout gapps and they started working again. I'm not sure if that was the problem or not.

Bluetooth headset breaks up outdoors playing media but not during phone calls

I am running the lite Marshmallow ROM from this thread:
http://forum.xda-developers.com/nexus-6/development/rom-5-1lightromstock-lmy47e-03-19-2015-t3059493
I think it is pretty much a stock ROM, so I don't think my problem is specific to that ROM.
I use a Bluetooth headset to listen to podcasts. It works perfectly in my car and most of the time works fine in my house. But as soon as I step out of the car or out of the house, it breaks up terribly. Sound will break up to the point where it is not listenable. Sound will go away for many seconds, come back, break up some more. The bluetooth is unusable outdoors for media. But if I make a phone call it works fine. The problem is the same whether I use my Plantronics Explorer 50 or my Kinovo BTH220, so I don't think the problem is in the headset.
Anyone have any ideas on what is happening and how to solve the problem?

It's not a stock rom.
I looked it over, and my intuition says either reflash this rom - or flash a new rom. Many of these roms are "adjusted" here and there by well meaning folks, and yes I've flashed some roms that were really messed up.
I look at the bottom line and here is a rom that is definitely not stock with some alterations that probably are good, so maybe a reflash will get it right. 10 years of software troubleshooting here on my part. Roms do not always flash right the first time.
I have personally had this happen. It's probably a great rom, give a reflash a try.

Without getting a logcat there is nothing anyone can do except guess what the issues is.

donnyutx said:
I looked it over, and my intuition says either reflash this rom - or flash a new rom. Many of these roms are "adjusted" here and there by well meaning folks, and yes I've flashed some roms that were really messed up.
I look at the bottom line and here is a rom that is definitely not stock with some alterations that probably are good, so maybe a reflash will get it right. 10 years of software troubleshooting here on my part. Roms do not always flash right the first time.
I have personally had this happen. It's probably a great rom, give a reflash a try.
Click to expand...
Click to collapse
Thanks. It has been happening for a while, I think I've clean flashed the ROM and it still happens, but last update I dirty flashed. I'll try a clean flash and/or the stock ROM next time I get a bit of time to do it.

zelendel said:
Without getting a logcat there is nothing anyone can do except guess what the issues is.
Click to expand...
Click to collapse
I was hoping someone who had the same problem might chime in. What should I look for in the logcat?

johninor said:
Thanks. It has been happening for a while, I think I've clean flashed the ROM and it still happens, but last update I dirty flashed. I'll try a clean flash and/or the stock ROM next time I get a bit of time to do it.
Click to expand...
Click to collapse
I just clean flashed the latest version of the Lite ROM and it did not fix my problem.

donnyutx said:
I looked it over, and my intuition says either reflash this rom - or flash a new rom. Many of these roms are "adjusted" here and there by well meaning folks, and yes I've flashed some roms that were really messed up.
I look at the bottom line and here is a rom that is definitely not stock with some alterations that probably are good, so maybe a reflash will get it right. 10 years of software troubleshooting here on my part. Roms do not always flash right the first time.
I have personally had this happen. It's probably a great rom, give a reflash a try.
Click to expand...
Click to collapse
I tried a clean flash of the Lite ROM. That didn't solve the problem. I then flashed the latest factory image (MOB30W). I did not restore anything or install any apps except Google Play Music and Podcast Addict, which I am using to reproduce the problem. I still have the same problem. Bluetooth media audio is working indoors, but as soon as I step outside it breaks up and goes out completely for 20 or more seconds at a time.
I think that rules out the Lite ROM as the problem. Anyone have any ideas for me?

I googled looking for bluetooth audio breakup issues and I found a few things that were suggested to fix it. They were turning off the WiFi and and turning off GPS. I tried both and they did not help my problem. I didn't expect them to because they were fixes for people reporting general bluetooth breakup on specific devices, while I am seeing the breakup on Media Audio, but not Phone Audio.
If anyone knows of a better place to ask my question, please let me know. I've been searching and can't find an answer or a better place to ask the question.

After some research here may be a fix...
johninor said:
I am running the lite Marshmallow ROM from this thread:
http://forum.xda-developers.com/nexus-6/development/rom-5-1lightromstock-lmy47e-03-19-2015-t3059493
I think it is pretty much a stock ROM, so I don't think my problem is specific to that ROM.
I use a Bluetooth headset to listen to podcasts. It works perfectly in my car and most of the time works fine in my house. But as soon as I step out of the car or out of the house, it breaks up terribly. Sound will break up to the point where it is not listenable. Sound will go away for many seconds, come back, break up some more. The bluetooth is unusable outdoors for media. But if I make a phone call it works fine. The problem is the same whether I use my Plantronics Explorer 50 or my Kinovo BTH220, so I don't think the problem is in the headset.
Anyone have any ideas on what is happening and how to solve the problem?
Click to expand...
Click to collapse
I believe this may help. When I flash a phone, I like to use Nexus Root Toolkit, as there are different areas of the phone that can be flashed manually. When I recommended to flash your phone, the "Nexus toolkit by wugfresh" was what I use to flash with. You'll see what it can do. This is a quote from reddit: "Not long after I got my 6P I started having some severe audio problems while streaming over bluetooth. I connect to my car's stereo via bluetooth and stream GPM every time I drive, and the audio would sort of stutter and skip, sometimes 5 times within a few seconds. It was insufferable for me, as there are few things I find more irritating than skipping audio.
***If you are having similar issues, going into recovery and wiping the cache partition completely eliminated the skipping/stuttering problems for me. Obviously, I don't know the nature of any issues you may have, so YMMV, but this saved my sanity.*** I was coming close to trying to RMA it, thinking it was a hardware problem as every attempt I had at finding a software solution had failed.
This gave me sweet relief, I hope it does the same for someone else!" *** Look at the second link for the Nexus toolkit, You'll see that there are 7 - 8 different flashable areas: Boot, Bootloader, Radio/Baseband, Recovery, System, Userdata, Cache, & Vendor. *** (Make sure to get the latest wugfresh nexus toolkit 2.16)***
https://www.reddit.com/r/Nexus6P/comments/42j4r6/psa_if_you_are_having_issues_with_prevalent/
http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452

donnyutx said:
I believe this may help. When I flash a phone, I like to use Nexus Root Toolkit, as there are different areas of the phone that can be flashed manually. When I recommended to flash your phone, the "Nexus toolkit by wugfresh" was what I use to flash with. You'll see what it can do. This is a quote from reddit: "Not long after I got my 6P I started having some severe audio problems while streaming over bluetooth. I connect to my car's stereo via bluetooth and stream GPM every time I drive, and the audio would sort of stutter and skip, sometimes 5 times within a few seconds. It was insufferable for me, as there are few things I find more irritating than skipping audio.
***If you are having similar issues, going into recovery and wiping the cache partition completely eliminated the skipping/stuttering problems for me. Obviously, I don't know the nature of any issues you may have, so YMMV, but this saved my sanity.*** I was coming close to trying to RMA it, thinking it was a hardware problem as every attempt I had at finding a software solution had failed.
This gave me sweet relief, I hope it does the same for someone else!" *** Look at the second link for the Nexus toolkit, You'll see that there are 7 - 8 different flashable areas: Boot, Bootloader, Radio/Baseband, Recovery, System, Userdata, Cache, & Vendor. *** (Make sure to get the latest wugfresh nexus toolkit 2.16)***
https://www.reddit.com/r/Nexus6P/comments/42j4r6/psa_if_you_are_having_issues_with_prevalent/
http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452
Click to expand...
Click to collapse
Thank you. I hadn't found that thread when I searched. I tried the several suggestions in that thread. One was clearing caches, which, of course, I had already done as a result of testing clean installs of the ROM I use and the latest stock ROM. So that didn't solve the problem. The other suggestion was turning off bluetooth scanning in location settings. I hadn't even known that was a thing. I tried turning off bluetooth scanning and wifi scanning this morning and used my phone all day as usual. It didn't solve my problem - no change at all. I had in an earlier test turned off the GPS and that hadn't helped either.
The second link, I believe is just a different way of installing ROMS and managing related stuff. I don't think that tool is going to do anything that I didn't do by installing the latest stock ROM with the flashall.bat script.