[Q] Continuous soft ringing - Fascinate Q&A, Help & Troubleshooting

I installed the cm7 with gapp and ec09 modem yesterday. Battery was draining so I went back to stock and installed it again today morning. Around dinner time today, I heard a soft ringing coming from my phone. So soft that I could barely hear it. Nothing worked so I did a battery pull and it went away. About 2 hours later, that ringing came back.
Can anyone tell me what's wrong and a solution to get rid of it?
Thank you~

A few other people have experienced the phantom ring, but last I heard it was gone for most people using CM7 test 11. What kernel are you on, and did you come from DL09 or EB01?

I had this problem back when CM7 was in its early test builds. The problem was (supposedly) remedied back in build 6
*** Update 07/04 ***
fixed deep sleep wake-up issues
updated to latest CM code
attached fixed recoveries below
Click to expand...
Click to collapse
As stated above if you could post the build number (test #) along with your kernel that would give us a starting point.
Like JT said it was an issue with the phone not waking from a deep sleep state when receiving a call. I can tell you that on my phone with the current CM7 build, ED05 modem, and Glitches V11.1 kernel I have not had this issue surface once.

Sorry to necro this thread.
I am running CM7 on my fascinate, nightly #34, jt kernal, and using ED05.
About once or twice every ten phone calls my phone does this described continuous ringing, except its quite loud. It doesn't stop until the phone call ends, and usually I have to tell them I'll call them back so I can hear them.
Has anyone had any similar issues? I wanted to report in the CM7 thread, but cannot.
Thanks

cb3ck said:
Sorry to necro this thread.
I am running CM7 on my fascinate, nightly #34, jt kernal, and using ED05.
About once or twice every ten phone calls my phone does this described continuous ringing, except its quite loud. It doesn't stop until the phone call ends, and usually I have to tell them I'll call them back so I can hear them.
Has anyone had any similar issues? I wanted to report in the CM7 thread, but cannot.
Thanks
Click to expand...
Click to collapse
I had the same problem, I think the last nightly I had #27. that and call volume forced me to go PWGB

PWGB
xAirrick said:
I had the same problem, I think the last nightly I had #27. that and call volume forced me to go PWGB
Click to expand...
Click to collapse
Good Job mate

I just experienced this last night on JT's Vanilla Gingerbread v7 using his included Kernal. Had to pull the battery. So far it has only happened once.

I get it right before the ringtone. I had it happen when my phone was on vibrate. I have had it happen when I answered the phone it kept ringing. I am running OMFGB nightly 8/25 with Glitch's V12 beta kernel. It has only happened a couple of times but goes away. Not much of a problem.

quite annoying. my phone is on vibrate most of the time, and this happens often enough that it drives me insane.
To clarify what I mean by "it":
1. Phone continues ringing after i pick up the call
2. phone rings on its own, usually when someone is trying to reach me, but I don't actually get the incoming call. Phone keeps softly ringing till I reboot it.
{
"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"
}

I had that happen once or twice on build 35. You mentioned being on CM7 and ED05, so I assume you're referring to the ED05 radio only, correct? If that's the case I recall reading here or on rootz that since CM7 is GB-based, it is advisable to use the EC09 radio with it; ED05 is Froyo. Can't guarantee it'll solve your problem, but I personally haven't gotten a phantom ring since...
Sent from my SCH-I500 using xda premium

Holy crap, not 10 minutes after posting that, I got the phantom. Consider my previous advice worthless.
Sent from my SCH-I500 using xda premium

I installed Powerwashed GB and the phantom ring has yet to return after 5 days. I used to have it every day on CM7

Related

[Q]Wifi wont turn on

So, Ive done my due diligence in searching before I created this thread, and it seems like either Im the only one having this issue, or its new. Im guessing its probably something I did, but here it goes.
Like the title states, the wifi is not turning on. I check the box to turn it on, and it thinks and tries for about 15 seconds and then starts turning off. Im running Perfect Storm ROM now, but it was doing this with VirusROM and Twisted Sense as well. Im using the 4.4.2 kernel now, but Ive flashed a couple others with the same issue. I have tried turning on airplane mode, like has worked for other people with similar but different connectivity issues, but thats not worked. Ive restarted a few times and still nothing.
It did turn on last night, and was fine till I rebooted. Not quite sure what the trick is here, but Im stumped. Thanks in advance for any help!
Just curious are you using the 4gonoff? I know that I used the app to turn it onto 3g only (to save battery) and wifi would not turn on. When I switched back to 4g and 3g it turned on fine.
Nah, I only have 3g/4g issues at home and when I'm home I just use WiFi. I left that part alone.
Sent from my rooted Bolt running The perfect storm ROM and 4.2.2 kernel.
Bump...intermittent issues. It says unable to scan for networks then turns WiFi off.
Sent from my rooted Bolt running The perfect storm ROM and 4.2.2 kernel.
Still having intermittent issues...would love to figure out the issue.
{
"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"
}
VirusROM + 4.4.2 Kernel+ Bolt=WIN
Interesting you brought this up. I had the same issue an hour ago. My wifi wouldn't turn on. It would say searching for wifi then turn off. I thought it was my droid wall or maybe bloatware freezer so I unfroze some applications and allowed some applications with droidwall. After that nothing. I rebooted just to see if it would help and walla. It worked.
:::edit. I forgot to mention I running VirusROM AirborneTB.
Sent from my rooted Thunderbolt with VirusROM AirborneTB. Xda premium
raider3bravo said:
Interesting you brought this up. I had the same issue an hour ago. My wifi wouldn't turn on. It would say searching for wifi then turn off. I thought it was my droid wall or maybe bloatware freezer so I unfroze some applications and allowed some applications with droidwall. After that nothing. I rebooted just to see if it would help and walla. It worked.
Sent from my rooted Thunderbolt with VirusROM AirborneTB. Xda premium
Click to expand...
Click to collapse
Yeah, its been like this for me since thurs. Not sure whats going on with it, but its driving me nuts. Are you running the 2750 battery or 1400? Its not software(I flashed fresh) and if it is, its not something I did atleast. haha.
I think Imma make a backup real quick and try another rom and see if its just VirusROM. Then again, since Jcase just released the new RUU, perhaps Ill just wait for Virus to update Airborne.
I was a noob before, and didnt do fresh installs. I just flashed over the old one. lol. This time its fully cleared and factory reset before I flashed in Airborne.
stupid back button...

tegra D00 and ICS Roms

I have tried various ics roms. But seems everyone with tegra d00 cant seem to get it going. So decided to start a thread for if someone figures out how to get d00 going with any ics rom. The screen tear and cant turn screen off and get it to come back seems to be the problem i get with all the different ics roms. So from what i read its kernel issue. so any d00 fixes or tweaks please post in here.
I have the same and there is no solution for that until a proper kernel is written/ported.
Sent from my MB860 using xda premium
I have two Atrix with same tegrapart and almost same serial number (was bought and delivered together, from same shop). One of them works with the ics rom, other don't (have the screen lock corruption bug).
i have d00 with no screen tear, main problem was battery ...
i have D00 also...
no problems to get the ROMs work...
now using AtrICS v2...
except of fast battery drain, no probs so far...
same here AT&T version with d00 and no problems apart from fast drain and heating
So the real problem is not the tegrapart type? What is it then???
I can not use any of ICS roms due to screen tearing and black screen issues.
Sent from my MB860 using xda premium
dedebekri said:
So the real problem is not the tegrapart type? What is it then???
I can not use any of ICS roms due to screen tearing and black screen issues.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Mine is a d00 with same problems. I gave up using leak based ROMs for now.
I'm using Th3Bill's ParanoidAndroid latest build and that is an awesome ROM. No fingerprint, no Chrome and no VPN, but the rest works pretty well and, using the Tablet UI all the time (with 160 DPI) I have a good lapdock experience also.
[URL ="http://www.updatemymoto.com/"]
{
"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"
}
[/URL]
---------- Post added at 05:23 PM ---------- Previous post was at 05:15 PM ----------
epinter said:
I have two Atrix with same tegrapart and almost same serial number (was bought and delivered together, from same shop). One of them works with the ics rom, other don't (have the screen lock corruption bug).
Click to expand...
Click to collapse
Epinter, do you have any clues about the real reason of those problems?
[URL ="http://www.updatemymoto.com/"]
[/URL]
I have the d00 tegrapart. I've tried both AtrICS 1.0 and v2.0. Functionally everything worked great except for the short battery life and excessive heat but it had continuous reboots. The reboots would get progressively more frequest with time to where after about three days it would start rebooting about every five minutes with it just laying on my desk without me even touching it.
Lately I've been going back and forth between 2.3.6 stock and CSROM...patiently waiting for a stable build.
I don't know if anyone else has had this exact experience but I've been able to run several of the roms based on the ICS leak and as long as my atrix is plugged into my computer via usb, the roms seem to be fairly stable. Within 5 to 10 seconds after I've unplugged it, it reboots and continuously bootloops. The weird thing is that even when it's plugged into a stand alone charger it bootloops, it has to be a computer for it to be stable at all.
I have d00 and I am currently using ICS MROM. It works great so far. Battery is not draining that much.
epinter said:
I have two Atrix with same tegrapart and almost same serial number (was bought and delivered together, from same shop). One of them works with the ics rom, other don't (have the screen lock corruption bug).
Click to expand...
Click to collapse
hmm so maybe tegra part has nothing to do with it working or not. is there any other # or even clockwork version we can compare from working/nonworking d00 user?

TACHYON!!

This post is for users who aren't able to post on Tachyon's main thread
Anyway.. I posted a poll to see if anyone will participate while I try both the PMEM and ION versions (and procrastinate on homework).
Stole this from the main thread:
{
"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"
}
"We Welcomes you to TACHYON"
Don't procrastinate ! It's like when you do, next day is pop quiz on last night homework. I'm telling you, teachers have some sort of psychic ability to tell when your procrastinating. They're watching usssss lol.
Sent from my ADR6425LVW using Tapatalk 4
XAlexander_AlexanderX said:
Don't procrastinate ! It's like when you do, next day is pop quiz on last night homework. I'm telling you, teachers have some sort of psychic ability to tell when your procrastinating. They're watching usssss lol.
Sent from my ADR6425LVW using Tapatalk 4
Click to expand...
Click to collapse
My professors could care less if I fail as long as they're still paid. lol
Hey Neo,
Anyway we can get Paranoidroid's Halo baked into this ROM like the Nexus 4 guys are doing here?
Neo is a national treasure.
(phoneposting)
Talguy said:
Hey Neo,
Anyway we can get Paranoidroid's Halo baked into this ROM like the Nexus 4 guys are doing here?
Click to expand...
Click to collapse
Looking into it today
btw, PMEM here.
Tried ION then PMEM (clean flashed both) and here's what I noticed: dialer FC'ed (read the forum and noticed that this was fixed ) but the worst part was the inability to turn it back on from sleep after a few times and maybe it's me but the battery life is just AWFUL. I went to a class and it went from 40% to 5% by the end of 3 hours. Oh and the frequent random boots are quite obnoxious. I will say ION seemed noticeably faster and I would run it saying there's more overall stability. I won't give up yet I know you can iron out the bugs. Keep up the good work!
Sounds like you may not have been on the included kernel. It's not nearly as unstable as you've described and my phone has been on it for days now without a single random reboot or bsod.
IAmTheOneTheyCallNeo said:
Sounds like you may not have been on the included kernel. It's not nearly as unstable as you've described and my phone has been on it for days now without a single random reboot or bsod.
Click to expand...
Click to collapse
Hmm I'll reflash the kernel and see what happens. Oh and could you put up MD5 sums when you have the chance? Thanks
TACHYON!
PMEM versions always seem to be more stable for me.
RonnieG116 said:
PMEM versions always seem to be more stable for me.
Click to expand...
Click to collapse
You're absolutely correct and it probably the safer route; however, ION is much more stable then you think and can be incredibly responsive. Just make sure you wipe everything x5 and you'll be alright. Also, I replaced the kernel with the Funky Kernel by snuzzo. Its much more stable and it definitely worth trying.
IAmTheOneTheyCallNeo said:
Sounds like you may not have been on the included kernel. It's not nearly as unstable as you've described and my phone has been on it for days now without a single random reboot or bsod.
Click to expand...
Click to collapse
BSOD? What is this? Windows? If I wanted a BSOD, I'd go get a WinMo phone :x
flamewalker said:
BSOD? What is this? Windows? If I wanted a BSOD, I'd go get a WinMo phone :x
Click to expand...
Click to collapse
In this case it's black and not blue
WiFi Tether on Rez Tachyon
@Neo
WiFi tether in the system menu says "Error" when I try to enable it.
I tried Barnacle WiFi Tether, and it says "Waiting until Wi-Fi is disabled"
I cannot disable or enable WiFi---it's simply grayed out. Perhaps I should try a reinstall of 1.1? I confirmed that I have that rev.
Thanks again for the great ROMs!
(Woulda posted to tachyon thread but for being a NooB---I did do the admonished search for answers...)
This Rom does great on my rez. Neo always provides excellent stuff
Sent from my ADR6425LVW using Xparent Red Tapatalk 2
No Tether on 1.1.5
Froeleaf said:
@Neo
WiFi tether in the system menu says "Error" when I try to enable it.
I tried Barnacle WiFi Tether, and it says "Waiting until Wi-Fi is disabled"
I cannot disable or enable WiFi---it's simply grayed out. Perhaps I should try a reinstall of 1.1? I confirmed that I have that rev.
Thanks again for the great ROMs!
(Woulda posted to tachyon thread but for being a NooB---I did do the admonished search for answers...)
Click to expand...
Click to collapse
@Neo -- Thanks for uploading 1.1.5. I installed it and my WiFi and Tether still do not work. They worked fine on 1.1. I wiped system, cache, dalvik, and data before installing. I did not reflash boot.img since I was on 1.1 before. WiFi and tether worked great on 1.1. Perhaps I should move back to 1.1? I'm suprised that I have not seen other posts on this issue.
Any thoughts?
Something wrong must have happened for you. The kernel hasn't changed
Sent from my HTC One X using xda premium
Yea never had any of those issues running tach.
Sent from my ADR6425LVW using Xparent Red Tapatalk 2
robbnsade said:
Yea never had any of those issues running tach.
Sent from my ADR6425LVW using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
Definitely a good stable build. Wait til you see alchemy though it'll blow you away. I had it clocked to 1728 and its still running with 50%. Its as stable as tachyon, but carries the customization of pacman. The best of both worlds
Sent from my brain using xda-developers app

[Q] "Shell" app eating my battery

Hey all,
My battery life has gone to sh*t in the last couple days, and I have noticed in my battery usage settings that the top contributor to its demise is always "Shell" (screenshot below).
{
"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"
}
Here are my specs:
----------------------------
Samsung Galaxy S4 AT&T
Cyanogenmod 10.2 (09/22/2013 nightly)
Rooted
Sometimes when I reboot, "Shell" does not appear for a while, but I have not been able to pinpoint what triggers it to start. I tried wiping and reinstalling CM, but it still shows up. The battery drain is so bad, in fact, that unless I use the original wall charger that came with the phone, the battery life still decreases while charging.
I am posting this in general Android questions because I literally have no idea what is causing it. It could be a CM bug, it could be an app I installed that's doing something malicious (Lookout doesn't think so, however), or it could be something else I haven't thought of. I just wanted to see if anyone else has experienced this on any version of Android and get some help debugging. Even if you have ideas for how I can pinpoint the app/service that is causing this, I would really appreciate it.
Thanks!
aptbosox said:
Hey all,
My battery life has gone to sh*t in the last couple days, and I have noticed in my battery usage settings that the top contributor to its demise is always "Shell" (screenshot below).
Click to expand...
Click to collapse
I am experiencing the same trouble with my LG Nexus 4 with CM 10.2 nightly.
Edit: Actually it was the case with 20131001, but it seems Ok with 20131007.
Orome70 said:
I am experiencing the same trouble with my LG Nexus 4 with CM 10.2 nightly.
Edit: Actually it was the case with 20131001, but it seems Ok with 20131007.
Click to expand...
Click to collapse
Yea pretty sure it was a CM bug. I reverted to stable 10.1.3 and haven't seen the issue since. I guess that's what I have to expect for living on the bleeding edge I haven't seen anything about it in the changelogs, but if you say it's fixed, maybe I'll try the latest nightly.
aptbosox said:
Yea pretty sure it was a CM bug. I reverted to stable 10.1.3 and haven't seen the issue since.
Click to expand...
Click to collapse
I have a stock Nexus 4 ROM (rooted, but still stock), and I'm seeing 76% in "Shell" today as well, so it's presumably not related to CM.
Stock Nexus 5 and I had 55% drain over 5 hours today... What in the world is causing this? Never had this problem before.
1 day old stock nexus 5 and I'm having this issue...
Here's my post from another thread with screenshots:
http://forum.xda-developers.com/showpost.php?p=47257309&postcount=413
Anybody have a solution to this yet?
EboMike said:
I have a stock Nexus 4 ROM (rooted, but still stock), and I'm seeing 76% in "Shell" today as well, so it's presumably not related to CM.
Click to expand...
Click to collapse
What version of Android are you on? 4.3? 4.4?
aptbosox said:
What version of Android are you on? 4.3? 4.4?
Click to expand...
Click to collapse
There is no official 4.4 for the Nexus 4 yet. I'm on 4.3, JWR66Y.

[Q] Potential GPS fix for P769?

Hi all,
I am currently using AntonX's unofficial CM11 for the P769, and its great except that like CM10.2 seems to be broken. In CM10.1 it worked perfectly and same with the stock ROM as well. So I decided to pull a few files from the stock Jellybean ROM and create a flashable zip that installs the old files that have to do with GPS. It seems to work pretty well as I was able to get a pretty good fix from a cold start in less than a minute using device only location settings, but it doesn't seem to work nearly as well as CM10.1 and stock. Does anybody have any ideas on how to fix this problem (I have already tried using different gps.conf files to no avail)?
Attached below is a screenshot of my latest GPS fix in less than a minute and the flashable zip that I created.
Thanks!
View attachment GPSFix.zip
{
"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"
}
I think your files are the same as the ones already in the ROM.
What's wrong with GPS in CM10.2 or CM11 anyway? It never fails me, I always get a fix within a minute, even on a cold start.
As far as I remember GPS in CM10.1 was a little strange. I think I noticed that sometimes GPSTest was showing yellow bars but accuracy was in hundreds of feet, which actually indicated not a good lock. I may be wrong though, been a while.
Still a Problem
AntonX said:
I think your files are the same as the ones already in the ROM.
What's wrong with GPS in CM10.2 or CM11 anyway? It never fails me, I always get a fix within a minute, even on a cold start.
As far as I remember GPS in CM10.1 was a little strange. I think I noticed that sometimes GPSTest was showing yellow bars but accuracy was in hundreds of feet, which actually indicated not a good lock. I may be wrong though, been a while.
Click to expand...
Click to collapse
Yeah I think you're right that they're the same files because I was testing GPS again today and it would lock for maybe a second and then if I even moved, it would instantly drop. But this problem is definitely here because on CM10.1 and stock I would instantly have about 13-14 satellites in view, and be able to lock to about 7-9 of them in seconds, whereas now it takes about 1-2 minutes to get 10-12 satellites in view and lock to just five which instantly lose lock when the device is moved about 10ft. This is using the device only method of getting GPS so there is no use of wifi or cell signals to get the location because I have very spotty coverage. I just wanted to point this problem out as I've noticed it on other ROMs too such as BobZHome's CM11.0 and leolawliet's PenberRom5 which is also based on 10.2. Other than this little problem the ROM has been great and I thank you for your work AntonX!
On my P778g, i also noticed a diference between CM10.1.3 and CM10.2/CM11. But after some testing comparing to stock (my father has another p778 with stock rom) i discovered that the only diference is the signal strength: Under a clear sky the GPS works exactly the same but inside a house the roof is too much and the signal seems to be too weak, so it takes a lot more time to fix compared to stock. Keeping in mind that i never use the GPS inside my house this is not a big deal after all. I bet that no one is testing the GPS outside... try it.
If it wasn't winter and I paid my phone bill I'd be happy to go out now and test the GPS on my p769. I'm running omnirom tho, and I don't think it's cm based so I could have different results.
I'll post back here when I get a chance. By the way, the GPS on AOKP wasn't any better.
Sent from my LG Optimus L9 running OmniROM using Tapatalk

Categories

Resources