Database Info

[Q] MIUI Force Close with calls

I've checked around in quite a few threads, but wasn't able to find the exact issue that i am experiencing.
Background story: Hi, my name is rob, and i'm a flashaholic. I heard nothing but good things regarding MIUI- so I went from EvilFascination to MIUI 1.6.24.
The problems that were mentioned in various threads pertained to message, losing signal, phone not receiving phone calls (similar), and things of that nature. Going through the set up of my phone, i didn't experience any drawbacks.
HOWEVER. When ever I make a call, or receive a phone call, my phone locks up with only the soft keys lit up, and only way to "fix" it, is to do a hard reset by pulling the battery...
Any suggestions/links?
Thanks!
-Rob
Phone Stats:
Phone: Samsung Fascinate
Android Version: 2.3.4
Baseband version: S:i500.04 V.EC01
Don't think I left any important facts out..?

I found an updated MIUI rom- and that seemed to fix my issue.

I also had same problem. I re flashed it from EZFroyo then Hard Reset & Done.

Anyone else who has this issue and would like the link for the updated MIUI for Fascinate click below
***due to "noob" status, i can't post the link, though if you google : Nyne Axis MIUI 1.7.22, i'm sure you'll find it. My apologies
As a forewarning, i'm not able to place my finger on it, though the GUI looks a bit different from the previous release 1.6.24
And many thanks zk9211, I'll more than likely find another bug with the rom, due to it being in beta stage, and will give your way a shot. =D

[Q] Phone keeps restarting unless in airplane mode?

Sorry in advance for starting a new thread; I looked around for someone who already had this problem, but haven't come across it yet.
As title states, my phone started getting stuck in a loop of restarting after I updated my phone to Gingerbread, then used drhonk's kernel to root it.
I have a t-mobile Galaxy S 4G.
Don't know what numbers you need, so here's all I can grab
Model #: SGH-T959V
Firmware: 2.3.3
baseband version: Y959VUVKF1
Kernel version: 2.6.35.7-t959VUVKJ1-CL611444
build number; GINGERBREAD.VUVKF1
Everything was working well, and using my data connection, I downloaded the apps I wanted on my phone from the market, including root uninstaller, to get rid of some bloatware.
Afterwards, I decided to turn on my wifi to see if the signal stregnth was any better after updating to GB.
Since then, my phone has been in a constant state of restarting, running media scanner, finishing media scanning, and then restarting.
I managed to get it into airplane mode, and that keeps the phone on, but as soon as I turn airplane mode off, the wifi starts back up and the phone begins the restarting cycle again. When I can get far enough into the phone to see the wifi settings, I have to deactivate airplane mode, and my phone freezes up when it tries to turn the wifi on, and I touch to turn it back off. Every try I've done, it restarts before it can actually turn wifi off.
Any ideas on what I can do to fix things? I would really like to have a working phone. >_<
(Also, the only bloatware I uninstalled that I can think would have anything to do with connectivity, was media hub. Beyond that, I just removed inception (This was an insurance phone, so the sd card didn't have any info on it), amazon kindle, amazon mp3, and t-mobile tv)
I am pretty new to rooting and flashing. I've been doing my research before actually doing anything, but I won't even pretend to be very smart on the subject. So please, help would be appreciated. Help, in newbie terms, even more so.
Thank you.

KF1 is really old. Try following my GB starter pack guide to make sure you're on a good ROM, and try flashing some of the newer roms, mainly ICBINB, Audiophile, Valhalla or Beautiful SGS4G. They're all based off of recent builds and you can even try all of them by putting them on your sd card and flashing each to see which one you like best.
If you're thinking you'd prefer to stay on a KF1 rom, I'd strongly recommend against it, since it's an early GB leak that still had a lot of bugs. Generally, the KH#+ builds have been a lot more stable. The latest is KJ2 now by the way.

Thank you so much for the advice, I'll go ahead and do so later today.

[Q] HTC HD2 | Phone Apk Hanging and Buzzing Issue

Firstly, I have been searching this forum for about 2 hours. I have found a few threads with the same issues, but they are either not relevant or I have tried the solutions within the threads and they have not worked. Also, the threads I have found are a few months old. I have also searched the ROM thread seen below.
ROM: [06 Nov 2011][MAG/cLK] NexusHD2-Gingerbread V3.2a (GWK74)(Android 2.3.7)[tytung_r13]
Device: HTC HD2
ROM Installation Method: MAGLDR 1.13
SPL: 2.08.HSPL
When I accept an incoming call, the phone application hangs and after about 10 seconds I get a force close notification. Sometimes this is accompanied with a buzzing sound from my speaker. In some instances I have to remove the battery to restart the phone as it totally freezes.
This happened on Android 2.3.5 (of the ROM linked above) so I upgraded to 2.3.7 (of the ROM linked above) to see if it would fix the issue. It has not. I also wiped the phone and reinstalled the ROM, and again it hasn't fixed the issue.
Also, I do not have Skype installed so it's definetely not that.
I would have posted in the ROM thread but it wouldn't let me.
Any suggestions?
Many thanks in advance. I can provide additional information should it be required.

Benetration said:
Firstly, I have been searching this forum for about 2 hours. I have found a few threads with the same issues, but they are either not relevant or I have tried the solutions within the threads and they have not worked. Also, the threads I have found are a few months old. I have also searched the ROM thread seen below.
ROM: [06 Nov 2011][MAG/cLK] NexusHD2-Gingerbread V3.2a (GWK74)(Android 2.3.7)[tytung_r13]
Device: HTC HD2
ROM Installation Method: MAGLDR 1.13
SPL: 2.08.HSPL
When I accept an incoming call, the phone application hangs and after about 10 seconds I get a force close notification. Sometimes this is accompanied with a buzzing sound from my speaker. In some instances I have to remove the battery to restart the phone as it totally freezes.
This happened on Android 2.3.5 (of the ROM linked above) so I upgraded to 2.3.7 (of the ROM linked above) to see if it would fix the issue. It has not. I also wiped the phone and reinstalled the ROM, and again it hasn't fixed the issue.
Also, I do not have Skype installed so it's definetely not that.
I would have posted in the ROM thread but it wouldn't let me.
Any suggestions?
Many thanks in advance. I can provide additional information should it be required.
Click to expand...
Click to collapse
this isnt something about your phone so try another rom or tell the developers.

linkin_p said:
this isnt something about your phone so try another rom or tell the developers.
Click to expand...
Click to collapse
thanks a lot, i have same issue...maybe i'll try another ROM

buzzing HD2
Sometimes it happens on my HD2 on diferent rooms: NexusHD2 3.2, NexusHD2 ICS 1.1, MIUI 1.12.30, MIUI 2.2.17. It is not often. Any sollution?

It's same here! I am starting to think that the problem is with my phone! I tryed meny different ROM and settings...it always the same!
It doing it 2-3 times per day.
How to fix it ?

same problem
I'm using CM9 (v2.8) android 4.0.4 and facing the same problem. I tried many ROMs but can't fix the problem. Also tried some solution on this 4rum but no help until now.
I'm going to throw my HD2.

Same here
I have the same issues with different rom using nand or nativeSD.
1 on 2 receiving call, the phone freezes with a buzzing sound. I must to take the battery out to restart the phone.

same problem
I have the same problem with my HD2!
The phone freezes after I receive an incoming call with a buzzing sound/no sound. Sometimes it shows the error message of com.android.phone process, in other cases I need to remove the battery and restart the phone.
I have tried different kind and version of ROM(for e.g. NexusHD2, MIUI, TouchWizMod v3.0) but the freezing issue is still not solved.
As far as I checked the freezing is not related to any kind of installed software.
If anybody has a solution to this problem please share with me/us. I really do not want to get rid of my HD2.
Thanks in advance.
------------------------------------------------------------------------------------------------------------------------------------------------------------
I have found the solution. The reason why the phone did not work is the Viber application. I uninstalled it a moth ago and thence everything works well. I use the WeChat app instead of Viber and my phone works like a charm.
By the way, a member of the Viber team has commented on this forum that their application does not support any kind of custom ROM currently.

Im facing the same problem,its killing me, its been worst recently ! I cant answer any call on my HD2
this problem happend first time on android 4+ roms,
I tried diffrent roms after that, but still not fixed, anyone can help us to find a solution?!
-----
anyone using CLk has this problem?!
Im using Magldr

Im having the same problem here. Found no sulition currently. ROM - tytung NexusHD2 2.5

The phone freezes after I receive an incoming call with a buzzing sound/no sound. Sometimes it shows the error message of com.android.phone process, in other cases I need to remove the battery and restart the phone.
Click to expand...
Click to collapse
hmm same here, tried some different ROMS - SD (froyo) and NANDs (2 gingerbreads, now ICS), tried these on both of my HD2s, also changed RADIO from 2.15.50.14 to 2.08.50.05 - nothing helps.
sometimes when im getting a call (usually it happens twice a week, some weeks more often, some less), i press the button and the phone/app freezes, sometimes with a buzzing sound.
after that, system doesnt respond normally, on GB sometimes it autorebooted....
also tried without viber AND tried directly after reinstalling the different ROMS with no contacts, original ringtones - also happens there sometimes!
i dont think that could be a hardware problem, because both of my hd2 phones act the same way.....
any solution since that time?

At the moment I have latest Jelly Bean by cotulla, with Cyanogenmod, and when I make a call, the screen is black (turned off) even though I don't have it close to my head and sensor is not covered. When I abort the call, it doesn't respond and stays dark with button panel highlighted for several seconds, and only after I press power button for several times it awakens. The same happens for incoming calls. The phone is not usable as phone with such things happening... That's frustrating.
So, let me sum up what people (and I) have had on the subject:
1. Various Android ROMs were tried and issue is always present.
2. In my case, stock Windows 6.5 has a very similar issue - incoming calls are even ignored! At least I had the described problem after I decided to have an "old" but working phone and reverted to the stock ROM instead of Android. Alas, the phone was still having glitches when answering.
3. We don't know exactly how many HD2 are affected by the issue but it looks like more than 1% which is pretty much to be a serious issue.
I might assume we faced an intermittent hardware issue, that does not always reveal itself, and can only be reproduced after a certain "failure". I think it's hardware dependent because my phone was working fine but suddenly ceased to do that.
I'm very sceptical about fixing this issue for me or other users. It's an obsolete phone and any mass hardware issues that is not reported by manufacturer (btw, could this be checked out?) will scarcely be considered. The whole thing makes me think we just have to switch to our phones are gaming/browsing accessories, since it just doesn't work and the issue is apparently non-trivial to be examined. I would be though glad to provide any information and logs... but who cares? Even cotulla doesn't think HD2 is worth developing any more....

[Q] Motorola Defy+ stock 2.3.6 update causes reboot when connecting to phone network

I bought a refurbished Motorola Defy+ which came preinstalled with Gingerbread 2.3.4. Out of the box, the phone was able to receive calls, although I didn't test making calls at that time.
I ran the stock Software Update from Settings, and this installed 2.3.6 on the phone. Since that point, I can no longer make or receive calls on the phone. As soon as the phone tries to make the connection, it reboots: either when making a call into the phone, at the first ring, or when dialing out. I have confirmed that it's not the dialer itself that is the problem by using different dialer apps.
I have performed a full factory reset on the phone and tried with wifi, etc turned off but it has made no difference at all. Other features of the phone are absolutely fine and I have had no unexpected reboots due to any other cause.
After searching around it seems quite a few people have had problems with their Defy+ rebooting, but this is generally either during a call or just randomly. In my case it is absolutely at the exact time that it tries to make the phone network connection and at no other time.
Could this be a hardware problem, or is it more likely to be the 2.3.6 ROM installed by the software update? If I install another ROM, is it likely to fix the problem? If so, how would I go about downgrading the phone to the 2.3.4 version?
Thanks in advance.

OK, I jumped the gun.
I hadn't actually connected to any of my mobile phone network's APNs at the time I posted the above. Now that I have configured it to connect via 2G or 3G, I get random reboots all the time.
Not that this helps or anything.

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