Database Info

Reboot with NO service???

Can someone explain the nature of the reboots that they are experiencing? I had a reboot on Friday but it was much more then just a reboot, after the phone was finishing powering back up I had no ability to call out as if there was no service. I tried numerous battery pulls and even had Verizon do a reset on there end, nothing helped yet I was still able to receive and send data. Finally after about an hour my service was back. Then the same thing happened again yesterday, I went through the same processes with no success yet. I have tried all the different radio choices and nothing is working, does anyone have any suggestions?
Thanks!!!
Also I am rooted and using the stock rom

Bump..........

Did you do any radio flashes? I know mine rebooted on me when I was trying to flash the GB leak from yesterday and there wasn't even a signal bar...just blank space. I reflashed my radio and everything was ok.
Edit: read the last line that I missed before. I am assuming if you are on a stock rom that you didn't flash any radios (otherwise it would have been noted). Thats the only thing that I have run across causing issues. SMH

Yes, I had similar problem
I was running the Stripped Das BAMF with the new radio (same as the one that recently came out OTA) and had this no service problem twice. Since I'm in a 3G only area, I have been using CDMA auto(PRL) and use the Phoneinfo app to change it. I tried to change the network type to something else but couldn't change it. (I presume the network type is for data, but I was trying to see if changing it would affect the service). The other options were there, but I couldn't select anything other than the CDMA auto. A battery pull fixed my problem both times.
Now I'm running BAMF Remix 1.6.3 with the new radio and everything is fine. I don't change the voltages or overclock. Yesterday as I was driving around town the phone rang, but I didn't answer it. When I got home, the phone had powered down and did a reboot.

Just an additional thought. You might try doing a data wipe/factory reset to see if that helps. Of course, you lose your settings that way, so back up first.

[Q] CPU on 100% after the first call

Hi team,
hope you can help me...I just rooted my phone, did everything what was needed before flashing a custom rom.
I tried the Android Revolution HD 2.1 custom rom, and it worked fine, but once I made my first phone call, the process com.android.phone started to consume 100% of my CPU, the phone started to be hot, battery rapidly down etc. The only thing helped was the restart and not to make phone call. I searched in the different forums, I tried the USB debugging and also to clear calendar cache, but nothing...I flashed a different kernel as well (Leddroid) but no luck...still the same issue, 100% cpu usage after a phone call.
I decided to flash another custom rom, which was Leedroid 2.2.0...was hoping that it will fix the problem, but again...phone call and cpu on 100%...the strange thing is, that this time it did not do right after the first phone call, but 2 days later. Tried to disable all the synchs, usb debugging, calendar cache etc. but still got this problem
Anybody can help please? I would appreciate

Weird..
I've noticed my phone burning my leg while its in my pocket randomly when im not using it? Maybe a bug on HTC's behalf.Download fast reboot off the market and try using that to kill all the apps, its the best one ive used and normally stops it being so hot

Thank you, but it did not help...it actually kills everything, but as soon as I make the next phone call, the CPU gets back to 100% :-(

Anybody can help please...I installed a different kernel as well, but no luck...tried stock, Leedroid kernel and still got the 100% cpu issue.

Perhaps a full wipe can help. Make a Backup before.

Thanks MysthMob...I tried that one as well...used the SuperWipe from mike and from Leedroid as well...reinstalled the custom rom, everything worked fine till the first phone call...than it went up again to 100%
I was thinking of that it is caused by any 3rd party app...I have these installed:
Advanced task killer pro
Battery widget pro
Automatic bluetooth dongle pro

You dont need a task killer! Sense has one built in called Low Memory Killer

Good to know thank you...just removed, but the problem still persist...I am tired to reboot the phone all the time I make a phone call.

If you still have problems i would send it back for repair, Maybe it has a hardware fault

Do not think so...it was working fine with stock Rom...its just in custom Roms..but with all? I flashed back stock Rom and its working fine, but I want a custom one, I think I do not need to explain why

I will probably go back to the stock rom :-(
Mike is planing to release his 3.0.1 version, maybe he will include a fix...will wait till he posts it

CM7 APN Issue is Fixed!

The APN issue in CM7 is finally fixed!
Check out the last few comments here - http://code.google.com/p/cyanogenmo...on Model Network Owner Summary Stars Priority
*I TAKE NO CREDIT FOR THIS*

Wow that's awesome thanks for the update
Sent from my LG-P999 using xda premium

That didn't take long to make it over here. Lol.
Seems good so far here.

Awesome news...loving my G2x more and more every day! Can I just download that boot.img and flash it to my existing ROM through ADB? I'm on EagleBlood 2.3.7 which is a CM7 variant.

pettigrew95 said:
Awesome news...loving my G2x more and more every day! Can I just download that boot.img and flash it to my existing ROM through ADB? I'm on EagleBlood 2.3.7 which is a CM7 variant.
Click to expand...
Click to collapse
It should work fine. The change appears to be in the ramdisk, so if your ROM didn't require anything odd from it, you should be fine. Last time I played with EB, it didn't do anything odd in there.

ttabbal said:
It should work fine. The change appears to be in the ramdisk, so if your ROM didn't require anything odd from it, you should be fine. Last time I played with EB, it didn't do anything odd in there.
Click to expand...
Click to collapse
Thanks going to flash now!!!

Which comment I should read. .?

Reading those comments, it doesn't appear it was "fixed" but rather "helped". It seems that certain reboots didn't shut down the radio "perfectly" and the stock OTA files had some top layer reboot switch, which would reboot the radio after a set time of being disconnected.... which CM lacked.
It is weird because I am running MIUI and I haven't had a disappearing APN in some time... although we don't have a functioning WiFi calling app (Invalid SIM). I just thought it was funny when ricardo threw out Kinteco (or whatever WiFi Calling APK is) as I have wondered why CM7 had bad APN issues when MIUI has bad WiFi Calling. I see they tried building a rom without Kinteco (?) and the issue persisted, so I don't know.
So now, resetting from the UI is the same as a hard reset (pwr + volup) and a battery pull. I think bootup will also recycle the radio so it properly turns up too.
Sweet. While I don't know if it is perfected, it looks like they are on top of it and should be cooked in nightlies within a few days.

First a2dp now apn fix.... Ricardo is a genius, everyone should buy him a beer!!

player911 said:
Reading those comments, it doesn't appear it was "fixed" but rather "helped". It seems that certain reboots didn't shut down the radio "perfectly" and the stock OTA files had some top layer reboot switch, which would reboot the radio after a set time of being disconnected.... which CM lacked.
It is weird because I am running MIUI and I haven't had a disappearing APN in some time... although we don't have a functioning WiFi calling app (Invalid SIM). I just thought it was funny when ricardo threw out Kinteco (or whatever WiFi Calling APK is) as I have wondered why CM7 had bad APN issues when MIUI has bad WiFi Calling. I see they tried building a rom without Kinteco (?) and the issue persisted, so I don't know.
So now, resetting from the UI is the same as a hard reset (pwr + volup) and a battery pull. I think bootup will also recycle the radio so it properly turns up too.
Sweet. While I don't know if it is perfected, it looks like they are on top of it and should be cooked in nightlies within a few days.
Click to expand...
Click to collapse
Actually, I don't think that's quite correct.
The change makes it so the ril-daemon shuts down earlier on reboot, to make sure the radio is stuck in a funny state when the system boots back up, hence the apn issue. Also, the only problem they were reporting still having is sometimes it happens when you come out of cwm and reboot back to android. I just looked at the changelogs on cm7 and it appears he's just patched this as well. Hard reset is not the same as the new reboot function. If you look at the code, you'll see he just added
on property:sys.shutdown.requested=1
stop ril-daemon
at the end of the shutdown sequence. A hard reboot is not the healthiest thing to do on our phone because it's a journaling file system, can create corruption. (It's very rare, but it happens.) This reboot is the same as regular, shutting down everything properly, just adding the stop command to the ril-daemon (the service that controls the radio chip, essentially).
First part of your post was correct, though (Plus, it's already in the nightlies. 165 has the stop ril-daemon on shutdown, and 166 it looks like will have it on rebooting from recovery as well.)
Ricardo is the man

Also, please be sure to keep an eye on the thread. Ricardo has been asking for various radio logcats from both Stock and CM7 ROMs. Everyone that knows how to do this (logcat -b radio) should pitch in with logs as he requests them.
Here's to a %100 working CM7.
And yes, beers.

mstrk242 said:
A hard reboot is not the healthiest thing to do on our phone because it's a journaling file system, can create corruption.
Click to expand...
Click to collapse
I was under the impression that a journaling file system is specifically there to protect against file system corruption. Your comment made it sound like it's riskier to hard-shutdown a journaled file system than a non-journaled one...or maybe I'm misreading you.
Quoth wikipedia:
"A journaling file system is a file system that keeps track of the changes that will be made in a journal (usually a circular log in a dedicated area of the file system) before committing them to the main file system. In the event of a system crash or power failure, such file systems are quicker to bring back online and less likely to become corrupted.[1]"

Read the sentence after. Its very rare but it happens. Ext2/3/4 filesystems are extremely robust. Much better than ntfs and the like. On most other file systems its very likely a hard reboot will corrupt data. Its super rare on journaling file systems but there is a possibility. I just wanted to point out the difference in that post not scare people into not hard rebooting if the need arises.
Sent from my LG-P999

Milestone XT701 CM9 Problem T_T

Hello everyone it has been a long time since I've posted here. I really refrained from posting here since I know everyone else is dealing with the XT720 which is different, but I have tried everything. I am so close to it finally working perfectly.
I'm currently running this CM9 ROM: http://115.com/file/c2c50r7v#updatecm9.0.0RC0umts-sholesUNOFFICIALsigned-NIGHTLY-20120605.zip
from this link: http://www.anzhuo.cn/thread-293117-1-1.html
It seems to be the godsend for my phone. Mainly cause It has been a long time since I've ran a stable ROM that can be clocked at 1.0Ghz. I don't know about the XT720 but all the ROMs that has been released can only be overclocked to 800Mhz.
I flashed the CM9 ROM and then flashed the "gapps-gb-20111216-signed" for the Google apps. For the first time in months (before I was using a CM9 and CM7 before) I finally had wifi working. I don't really use much wifi (other than updating apps) so it didn't bother me back then. Everything else was working (cept for panoramic in the camera APP which NEVER works ever). But its like Motorola was playing a sick joke on me; I couldn't download/update my apps. I loaded everything fine but when I clicked download, I just see the download bar moving, but it never finishes. Weirdly, I reflashed everything and I suddenly got the error 921 (which I proceeded to search for a solution), but then after when I tried again, the error was gone and it was back to idle download bar. I did not change anything to the phone during that period.
So now I finally have XT701 clocked at 1.0 (like back in the day) with smartass/lagfree governors, working wifi, phone, audio and everything but I can't update/download apps.
I have tried:
-clearing data/cache for google play
-clearing data/cache for download manager
-reflashing with the 3 wipes for every step
What is the problem? Does it have to do with the bands? When I first flashed the ROM i had to change the network settings to Canada(Telus) cause it was set at somewhere else. Is that the problem?
Thanks in advance

Blaze Signal Keeps Going Out Problem(On Any ROM!)

So here's my issue, my Galaxy S Blaze has been switched from ROM to ROM constantly, I have seen ROMS with modified build.props, other added features, and a bunch of other tweaks, you name it! I don't know what all those tweaks mean, I have no idea if it could affect the way my phone receives the signal but it got me so frustrated that I kept switching roms until finally then I went back to stock and am no longer am switching to another ROM.
Here's a history of the ROM switching I've made in the past couple of months:
1st - MIUI
2nd- Cyanogenmod
3rd- Gummy ROM
4th- Liquidsmooth ROM
5th- Cyanogenmod
6th- Dirty Unicorns (problems with signal started occurring right about here, and onwards)
7th- Stock ROM (hmm... nope nothing fixed.)
8th- Validus (still no, I didn't like the constant force-closing of many apps)
9th- Gummy ROM (nope, what's worse is my screen kept freezing if I had atleast 2 apps open and I slid down the notification drawer)
10th- Cyanogenmod (well, maybe switching to cyanogenmod will fix it)
11th- Gummy ROM (*sigh* switching back? Nope, still didn't help my signal)
12th- Stock ROM (you would expect it to be fixed right about here, but nope)
So what's up what is the exact problem with my signal? Here's the thing: My signal works! That's a start atleast. However, if I turn on my Wi-Fi while I'm home, I can still call/text people, all of that works. But after maybe 2 hours or so, the signal bar is still there, it's telling me it has signal and it's connected, SOMETIMES it will be empty meaning I have no signal(when I really do). But in reality, I can't receive texts, nor calls, none of that. So how do I fix it? By restarting my phone sadly, that has been the only solution for me for these past 2 months. People have complained to me because I don't answer my phone anymore, well I'm sorry my phone can't receive those calls due to this messed up signal. There are 3 other T-Mobile phones in the house that have no problem! The problem here is with my Blaze phone.
So what if I turn the Wi-Fi off for the whole day and see if it's the main thing causing the issue? Well, I did this. Turns out that the signal stays on longer than when I'm on Wi-Fi but it still goes out. I have switched SIM Cards, I have tried switching my APN: from "epc.tmobile.com" to "fast.t-mobile.com" but the problem appears to happen more quickly on the "epc" one than the "fast" one. Please help me with this, this has been frustrating me a lot lately. I'm not sure if anyone has even had the same exact problem that I'm having, I've searched online but haven't seen a similar problem.
Some of you might say, wow that is a lot of ROMS you've switched to, I'm sure there were more that I missed but that's as of recent. I can install ROMS correctly, I know how to use CWM when installing a .zip and using Odin when it's a .tar(or other supported file extensions). I've factory reset, wiped the cache, the dalvik cache, all before installing a new rom. After installing each rom, I've also factory reset and wiped the cache to make sure no other problems could affect the way the rom would work. Hopefully I did the procedure right, thanks for anyone who's willing to help me!
Right now I am running:
Baseband Version:
T769UVLH5
Kernel Version:
3.0.8-perf-T769UVLH5-CL990184
[email protected] #1
SMP PREEMPT Fri Aug 17 15:12:14 KST 2012
Android Version:
4.0.4
Another Issue is that I can't even transfer files to and from my phone when connected to my computer! This is another big issue, here are some images:
http :// i.imgur.com/xx699ss.png
http :// i.imgur.com/1wRzJpX.png
Here's what happens when I turn Wi-Fi Calling on but maybe it's just a built-in function that I forgot it had and it's probably normal:
http :// i.imgur.com/cTSqRci.png
By the way, sorry for the links just copy and paste them in a browser to and remove the spaces between the http :// and i.imgur, thanks! Unfortunately, I can't post links until I reach 10 posts. If the links don't work for you, I've also provided attachments.
Many thanks!!!

That last picture does show the proper function of Wi-Fi calling however I don't know what to say about the rest of your problems.
Sent from my SAMSUNG-SGH-T769 using XDA Free mobile app

There are two things I would recommend trying...
1. Use Blackhole System Wipe
I know you've been following all the proper steps in CWM (and I would say to keep doing so), but I've added using Blackhole, in addition to the first steps, and I always get great system performance on my phone, and my parent's phones (I put them on ProvisionMod after stock was being stupid). It works well for pre installation for ANY ROM and helps prevent pesky issues. However, chances are, your issue is baseband related and this probably won't solve it... But still! You never know! It's worth a shot!
2. Reroot your phone
I know this will be annoying and pesky... but sometimes the process goes wrong from the beginning and starts giving issues later on... When I first rooted my mom's blaze, something went wrong, despite my following all the directions, and one of her partitions was completely disabled, no matter the ROM. I redid the process of rooting her phone (not from GB though... From the ICS stock) and fixed the issue instantly! I would try these two steps first and see if they do anything! Good luck!
Sent from The Doctor's Blaze