I am on Truepure 2.9 rooted Rom.... I get a new voicemail notification every time I turn the phone on. When I go to voicemail nothing is there? I can get rid of it if I go to Apps in settings, system apps, scroll down to phone services and force close the program. It goes away for awhile and the comes back. This happened when I first got the phone with 6.0 MM, as well as 5.1.1 when I had to restore because of a soft brick, so I dont think the rom has much to do with it. Any ideas why this is happening and how to fix it? Thanks
Related
Okay, here's the sad story so far:
I have a (previously) unmodded G1, with normal T-Mobile software. Yesterday morning around 5AM I get the little notice that I can upgrade to Cupcake. Unfortunately, it's 5 in the morning, I couldn't sleep, and I wasn't thinking all that straight... so I decided to root my phone and upgrade it to 1.5 instead.
So I downgraded to RC29, got myself root access, and installed the latest Jesus Freke build. Now the fun starts. As soon as the phone boots into the JF build I get constant android.process.acore force close errors. And I do mean constant, I force close, and it pops up again, force close, pop up again ad infinatum. I reflashed a few more times, varying the order of installing the radio update and misc. stuff like that, but still no luck.
So I decide to go back to the T-Mobile build without root access. I mean, I lived without it before, and not having root is better than not having a functioning phone, right? So I download the official cupcake update from google's dev site and install that. Woohoo, no more force closing, it looks like everything works!
Orrrrr not. I can't get into Settings now. I've tried to open Settings from the home menu, from a shortcut on the desktop, and through the menu button. Every time I try to do so, it will open up a black screen (like it's starting to load the settings menu), stay there for anywhere between 1-4 seconds, then go back to the main desktop screen. Everything else on the phone works, Market, Camcorder, soft keyboard, everything. Most apps I've downloaded also seem to work. However, when I installed the Toggle Settings app and tried to toggle the GPS, it popped into the settings menu with a black screen with the Security and Location text at the top, and then promptly went back to the app without changing the GPS.
I've tried everything I can think of at this point and the almighty Google doesn't seem to have any answers, anyone else able to give me some help? It would be much appreciated.
Update and bump, because I really need some help here:
I flashed the phone back to RC30, and left it overnight. In the morning there was an OTA update to cupcake available, so I installed that. Unfortunately, even with the OTA update the settings menu still won't stay up. Any advice?
Croaka said:
Update and bump, because I really need some help here:
I flashed the phone back to RC30, and left it overnight. In the morning there was an OTA update to cupcake available, so I installed that. Unfortunately, even with the OTA update the settings menu still won't stay up. Any advice?
Click to expand...
Click to collapse
Silly question, but did you do an alt-W to wipe the phone?
yep, wiped it many times during my trials and travails.
before or after the issue with the settings menu?
I've actually tried it both ways, wiped or not wiped, the settings issue remains the same.
Ok, so my phone will not vibrate at ALL anymore. I don't want to pay the $50 to get a new one, and I don't want to have to revert back to stock and unroot and take it to Verizon to see if they can fix it.
So here's the details of what happened. I don't know if it's fixable, but I thought I'd see if anyone could offer some advice.
I was running DL30 Blackhole, very basic. Had a theme installed over it. Everything was running perfectly fine for a while. And then I was getting on the internet to do something, and connected to wifi. The wifi was through my college, so you had to login on their homepage instead of just entering a password, and the page wasn't coming up, internet was being extremely slow. So I tried turning off mobile data to see if it might force me to login to the page for wifi. Turned of 3G. Nothing happened. Turned off wifi. Turned 3g back on. Then I got a google system force close error and my phone rebooted itself.... Now I have no vibration AT ALL. No hatic feedback, no vibration for notifications. Nothing.
There was nothing even related to vibration that should have happened in this situation, my phone just freaked out. Didn't drop it or hit it on anything at all, it was laying flat on a table. So I don't know if something just fried my phone's vibration or what, but I would love it if someone out there had a suggestion for me.
I'd try just following the steps to update to super clean 2.4. some kernels act up on your version and drop the vibration. It happened to me. 2.4 is running awesome
Sent from my SCH-I500 using XDA App
Yeah I forgot to put that in the first post. I actual did a complete system wipe. Back to stock DL09, flashed the EB01 modem, and SC 2.4 over it. And still no vibration. I did all that this morning.
Also had a weird glitch where after I installed most of my apps I tried to boot into recovery and instead my phone decided to do a data wipe again, but that wasn't a HUGE issue (as long as it doesn't happen again).
Spazguitar306 said:
Yeah I forgot to put that in the first post. I actual did a complete system wipe. Back to stock DL09, flashed the EB01 modem, and SC 2.4 over it. And still no vibration. I did all that this morning.
Also had a weird glitch where after I installed most of my apps I tried to boot into recovery and instead my phone decided to do a data wipe again, but that wasn't a HUGE issue (as long as it doesn't happen again).
Click to expand...
Click to collapse
Try reverting back to stock again and prior to going back up to eb01 and superclean...wipe a few times.
I had a similar issue
Spazguitar306 said:
Ok, so my phone will not vibrate at ALL anymore. I don't want to pay the $50 to get a new one, and I don't want to have to revert back to stock and unroot and take it to Verizon to see if they can fix it.
So here's the details of what happened. I don't know if it's fixable, but I thought I'd see if anyone could offer some advice.
I was running DL30 Blackhole, very basic. Had a theme installed over it. Everything was running perfectly fine for a while. And then I was getting on the internet to do something, and connected to wifi. The wifi was through my college, so you had to login on their homepage instead of just entering a password, and the page wasn't coming up, internet was being extremely slow. So I tried turning off mobile data to see if it might force me to login to the page for wifi. Turned of 3G. Nothing happened. Turned off wifi. Turned 3g back on. Then I got a google system force close error and my phone rebooted itself.... Now I have no vibration AT ALL. No hatic feedback, no vibration for notifications. Nothing.
There was nothing even related to vibration that should have happened in this situation, my phone just freaked out. Didn't drop it or hit it on anything at all, it was laying flat on a table. So I don't know if something just fried my phone's vibration or what, but I would love it if someone out there had a suggestion for me.
Click to expand...
Click to collapse
I had a similar issue. I actually flashed my phone all the way back to stock. Still no vibrate. I think there could be an issue with the vibrate motor on the fascinate.
I say that because there was nothing I could do to bring vibrate back. All of sudden, it began working again for one day. After that one day vibrate and haptic working, it stopped working for another couple of days. Then, I dropped the phone on accident. Vibrate came back. Eventually, it stopped working again so I took the phone to verizon and they ordered me a new one.. No charge. I bought my phone in Sept 2010.
Good Luck!
Recently, whenever someone calls me, that message pops up. It constantly pops up whenever I make it go away. Decided to restart my Nexus, but it still was there. However, if I press the dialer, the error actually stops and my phone works normally. Is there a particular reason why it does this? And possibly a solution? Without factory resetting?
CellPhish said:
Recently, whenever someone calls me, that message pops up. It constantly pops up whenever I make it go away. Decided to restart my Nexus, but it still was there. However, if I press the dialer, the error actually stops and my phone works normally. Is there a particular reason why it does this? And possibly a solution? Without factory resetting?
Click to expand...
Click to collapse
Unfortunately, same thing just started happening here, with LiquidSmooth 2.9 on my Tmobile Note 2...
Started when a phone call came in, has not stopped since.
Even after reboot.
Phone is now unusable...
UPDATE - Pressing Dialer actually stops it.
It is just a bit tricky to press OK, then try hitting the dialer button quickly.
But it does seem to fix it.
Can now use phone again.
Posting here to see if more exposure would help.
Was wondering if anyone has run into this problem?
The phone was fine, rooted and everything, for a month give or take. Then all of a sudden, today, it started acting weird.
It was fine in the morning and everything, was able to use wifi, check emails, and stuff.
Then BAM, I tried to make a call, it didn't go through for the first 20 seconds or so. Then connected and a message kept popping up saying Phone is stopped or something during and after the call.
So, I restarted the phone. It restarted fine and everything, got past the 2 Samsung screens. Then hit the T-Mobile screen. and has been stuck on the T-Mobile screen for ~30 minutes now and just keeps vibrating.
It's getting quite hot, both front and back.
Any advice? Stupid Samsung making this a closed system so can't pull out the battery.
Can't even turn the phone off, only able to get to Download screen.
Weird problem.
Is there any way to pull the data and stuff off the phone at this point?
I'm thinking of going the factory reset route and do that to see what happens and see if it will fix the problem. It would probably not retain root am I correct and I would have to re-root again?
I could get into download mode and recovery fine.
I have had this issue on both at&t and t-mobile firmwares, but only while rooted.
Best thing to do is to re-flash the stock firmware again(or go to a different firmware if you'd like) but this is the reason I'm currently avoiding root. It soft bricks about a month in and is an easy fix but its annoying.
Was wondering about that too (flashing the stock firmware). But, will it wipe everything I had on there? Will any of my txt msg's and photo's or summat be lost to the ether?
Stupid question, I know, but had to be asked.
Thinking about flashing stock firmware and rooting agin for the sake of being able to do it again lol.
Well, if you flash stock, it does factory reset. That's why I have backups lol all I have to do is log into my Google account and everything is there.
buntobo said:
Posting here to see if more exposure would help.
Was wondering if anyone has run into this problem?
The phone was fine, rooted and everything, for a month give or take. Then all of a sudden, today, it started acting weird.
It was fine in the morning and everything, was able to use wifi, check emails, and stuff.
Then BAM, I tried to make a call, it didn't go through for the first 20 seconds or so. Then connected and a message kept popping up saying Phone is stopped or something during and after the call.
So, I restarted the phone. It restarted fine and everything, got past the 2 Samsung screens. Then hit the T-Mobile screen. and has been stuck on the T-Mobile screen for ~30 minutes now and just keeps vibrating.
It's getting quite hot, both front and back.
Any advice? Stupid Samsung making this a closed system so can't pull out the battery.
Can't even turn the phone off, only able to get to Download screen.
Weird problem.
Is there any way to pull the data and stuff off the phone at this point?
I'm thinking of going the factory reset route and do that to see what happens and see if it will fix the problem. It would probably not retain root am I correct and I would have to re-root again?
I could get into download mode and recovery fine.
Click to expand...
Click to collapse
Did you have security log or security update disabled as that updates and causes weird after affects.
buntobo said:
Posting here to see if more exposure would help.
Was wondering if anyone has run into this problem?
The phone was fine, rooted and everything, for a month give or take. Then all of a sudden, today, it started acting weird.
It was fine in the morning and everything, was able to use wifi, check emails, and stuff.
Then BAM, I tried to make a call, it didn't go through for the first 20 seconds or so. Then connected and a message kept popping up saying Phone is stopped or something during and after the call.
So, I restarted the phone. It restarted fine and everything, got past the 2 Samsung screens. Then hit the T-Mobile screen. and has been stuck on the T-Mobile screen for ~30 minutes now and just keeps vibrating.
It's getting quite hot, both front and back.
Any advice? Stupid Samsung making this a closed system so can't pull out the battery.
Can't even turn the phone off, only able to get to Download screen.
Weird problem.
Is there any way to pull the data and stuff off the phone at this point?
I'm thinking of going the factory reset route and do that to see what happens and see if it will fix the problem. It would probably not retain root am I correct and I would have to re-root again?
I could get into download mode and recovery fine.
Click to expand...
Click to collapse
These two threads describe exactly your issue and solution - http://forum.xda-developers.com/verizon-s7-edge/help/g930t-updates-unroots-overnight-t3426636 and http://forum.xda-developers.com/tmobile-s7-edge/help/rooted-weeks-rebooted-stuck-t-mobile-t3425814
I had the same problem, twice I had a rooted device totally lock up and had to re-do everything. But after disabling the security updates as advised, I'm currently going on two months without a problem.
Hope this helps!
For some reason after flashing to the new LineageOS 14.1 I cannot hang up after receiving calls or calling somebody. When I press the red hang up button the screen just gets stuck on "hanging up". If I kill the app and go back into dialer I am still in the call. The only way to hang up is the restart the phone which gets very annoying. Has anyone come across this issue before? I'm really liking Nougat and really don't want to go back to stock 4.4.4 KitKat.
My wife has had the same thing on her Nexus 4 running the latest LineageOS build (flashed a couple of days ago).
(edit: Resolved by going into Settings -> Apps -> Gear -> Phone - set default dialer app)
thatonesubaru said:
For some reason after flashing to the new LineageOS 14.1 I cannot hang up after receiving calls or calling somebody. When I press the red hang up button the screen just gets stuck on "hanging up". If I kill the app and go back into dialer I am still in the call. The only way to hang up is the restart the phone which gets very annoying. Has anyone come across this issue before? I'm really liking Nougat and really don't want to go back to stock 4.4.4 KitKat.
Click to expand...
Click to collapse
L03 has a dialer issue with any non official ROMs. The hardware is slightly different so the driver doesn't work correctly. I never found a fix for this.
Did anyone find a solution to this? I have flashed the Lineage OS and I am facing the same problem. Everything is working fine but I just can't hang up the call. It stays stuck on "Hanging up" and never lets me do anything until I restart the phone. Solution will be well appreciated
thatonesubaru said:
For some reason after flashing to the new LineageOS 14.1 I cannot hang up after receiving calls or calling somebody. When I press the red hang up button the screen just gets stuck on "hanging up". If I kill the app and go back into dialer I am still in the call. The only way to hang up is the restart the phone which gets very annoying. Has anyone come across this issue before? I'm really liking Nougat and really don't want to go back to stock 4.4.4 KitKat.
Click to expand...
Click to collapse
exact same problen with G706-L01 no way arround it but restarting the device every time i end a call did not happened with cyanogen mod 12