I have a problem with the Runnymeade AIO 6.0.5 rom.
It is fine for the first couple of days, and then all of a sudden, incoming calls can lock the phone. By locking the phone, I mean the phone is unresponsive and require the battery to be pulled to restart it. This means I dont get any indication as to when it happens as the phone doesnt ring, just locks. From the callers end, they hear the ringing but it doesnt get picked up. Has anyone else encountered this? I also saw this in the V5.x of the rom but through it was something that was gone.
The configuration I have it running under is, 1GB of EXT4 off a samsung class 6 16GB card, setup using the 4EXTRecovery, stock HBOOT.
Related
I have a problem with my O2 XDA IIs, the sound works perfectly for playing MP3's etc both on the internal speaker and on the external plugin headset!
Where's the problem? I hear you asking!
Well, the sound does not work at all when in a call, the caller can not hear me and I can not hear them, although the call is connected OK. The only time I can hear the caller or be heard is if I plug in a sync cable or put the device in the sync station, at that point it works ok when in a call. I belive this to be a power requirement as it also works when I plug in the car charger?
Does anyone have any ideas what could be causing this problem, it has only been occuring for the last few days and I have not changed anything during this time which could have caused the problem... I know that's what they all say, but it's true this time!!!
Have you tried getting rid of unusual programs running in background? (Try 'Startup Manager' to take off some startup programs) or wait until any expert put a word on it.
There are only 2 entries starting and they are both the same as they have always been, the problem does appear to be quite random, as though every time I remove the sync cable something either happens or does not happen??
Does anyone know if there are any switches or anything attached to the sync connector on the phone which might be causing the problem?
I had a problem not unlike what you describe. It started after the battery ran very low on the phone while I was away from home.
The Phone would only work while in the cradle, and wouldn't work when out. The Speaker Phone function disappeared also.
I re-flashed the ROM.
I downgraded the ROM.
Re-formatted the storage card.
Took the Phone apart looking for a switch that might be stuck.
All to no avail.
Contacted Qtek who wanted me to return the phone.
So I tried one last thing before I gave up.
I left the phone with the Battery attached to run down again. (I left it for about a week)
re-charged the phone and its been fine ever since.
The conclusion I came too was it is a software register on the phone that was corrupted and the total drain of power cleared it.
When you ran the battery totally flat did this not clear all the stored data and installed apps etc? Only I'd rather not do that if I can avoid it?
Couldnt tell you sorry, I had already lost all data/apps with the reflash/formating.
No worries, if you hear or find anything elsewhere about this problem please let me know as this is getting very very annoying now!!!
Patch
Hi guys
This is a tipical problem of the BA. I had the same problem at the begining. This are the steps to solve it:
1. Backup your data (only contacts & meetings)
2. Hard reset of the device (press micro + On/Off button + reset)
3. Install the "PDA2k_UniDirectional_Patch.sa.cab" patch
4. Do not restore a whole backup (you will have the same problem again)
So it would be work fine. If you upgrade to the lastest ROM you will get this bug fixed too.
Good luck!
Hi i have the same problem and try a diferent approach.
Upgrade radio to version 1.15.
Problem appear to be solved.
I upgrade the rom yesterday, once i have change the board, and downgrade the rom.
What is this "PDA2k_UniDirectional_Patch.sa.cab" and what does it do exactly? As I'm already using the Radio 1.15.00.
Sound Patch
This file fixes the problem when you do not listen to the person who has called you.
You can download it from:
http://wiki.xda-developers.com/uploads/PDA2k_UniDirectional_Patch.sa.cab
Heya.
I am running Android Revolution 2.0.16, Kernel 2.6.32.29_BUZZ1.3.3_OCUV with radio Radio_12.35d.60.140fU_26.06.03.24_M2.
I've been running this for ~1.5 weeks and I think this started about 1 week ago, not sure. Sometimes randomly (sometimes when I'm playing and sometimes when the phone has been idle for few hours) the phone boots. I see the white background with the green HTC logo and after a while it asks for my Pin number. Sometimes this happens once/day and sometimes it happens three times in a row. With stock it never did this.
What could be the cause?
How could I fix this?
I'm interested in Android Revolution 2.1 but can't find it after the 3.0 and 4.0 came along. I'm not ready for unofficial Gingerbread yet and 3.0 is using 1.84 for Orange and I'm not completly sure if I should use it with my unbranded Finland located phone.
Thanks for your time!
Hi. This has nothing to do with the ROM you are running it is a physical problem with the phone and is quite a common fault on the Desire HD.
It is a problem with the placement of the SIM card underneath the cover. I just stuck a bit of selotape across the SIM card to keep it in place and mine has been fine since. Other than that flash back to default and send it back under the warranty.
I don't think it's about loose Sim card. I tried to move the sim card while the phone was on the finally removed the sim card. The phone didn't boot but I got a message that said that phone can't locate sim card and I must either restart or shut off the phone.
This isn't what I mean with the restarting. It just restarts, boots, without any error message. Like I would have pressed the power button and selected restart.
Its because of the kernel, like mine your cpu seems to be sensitive to undervolt, try leedroids kernel
Sent from my Desire HD using Tapatalk
So although all DHD have the same type of CPU, each specific CPU reacts differently to UC/OV? Strange, how widespread is this? Personally I've had no problems.
Had the same random boots with revolution 3.0 and 3.1, reverted back to stock 1.72 with the same(BUZZ) kernel and same setcpu settings as I used with revolution, and reboots are gone for me
Heya. Thanks for the replies. I was thinking going back to stock too but decided to try Revolution 3.2 and it seems to work. Atleast one day without boots, but we'll see how it's in the long run.
Hi Guys,
Yesterday I was having trouble with "E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory)" error, I managed to solve this problem but ever since my calls keep dropping, oddly enough the call seems to stay connected the other end.
When I make a call it connects then drops looking at the screen for a few moments the signal has completely gone but then mysteriously comes back almost immediately, if I call my partners phone the call drops after 10-20 seconds, and if I call again the first call to her stays connected at her end, if she picks up the second call the other call goes on hold and the second call drops exactly the same.
Following the cant mount error I flashed back to Reflex 2.0.1, I didnt have the problem earlier with Reflex 2.0.0 which I did a nand with even restoring this the problem remains, I've tried insertcoin rom problems remains and also tried apps2d+ rom instead of cm7 and still problem remains.
Can anyone help?
Should flash a rooted stock froyo rom and start s-off again?
this problem was solved by fixing usb brick
heres my post fixing the problem
http://forum.xda-developers.com/showthread.php?t=1070863
I have fixed the sd card problem, its dropping calls now
I got similar error once after I flashed a align ext4 patch. I had to repartitioned the SD card to fix it.
I have repartitioned several times and tried different sd cards the dropping calls does not appear to be a sd card problem
Jonnibravo said:
I have repartitioned several times and tried different sd cards the dropping calls does not appear to be a sd card problem
Click to expand...
Click to collapse
Are you on orange by the chance? And what rom/radio are you using?
I am on T-mobile uk, I have the 32.56.00.32U 5.17.05.08, I was running Reflex 2.0.1 but I have tried stock froyo insertcoin and backed up reflex 2.0.0 which I did not have a problem with, so I think this could be because I flashed the Beta sensation rom sense 3.0, its definatley nothing to do with the sdcard, also I have usb brick and I cannoit seem to recover it with the usb brick fix, not sure if I have done it correctly though as my cid is t-mob005 not sure if thats correct.
In addition when I tried the fastboot oem boot command it rebooted the phone and siad failed status read failed too many links
Ok, I flashed a old backup of a miui rom I had and have since made a phone call for 2:30 seconds without any problems.
Can anyone help me to explain why this is happening and how I can get back to reflex without calls dropping?
ther may be a problem with the proximity sensor on the fone could be hardware/software
i was having a look over at htc forums and i found this
"
Posted by andyc120 on 15 Aug 2010 2:15 PM
After more research I was able to fix the problem on my Desire. I have a screen protector which had the smallest tiniest mark on it in the top left. The proximity sensor is two small dots at the top left of the front of the phone in the black area above the screen (you can actually just about see them when holding the screen up to the sun or a bright light).
A lot of people apparantly have had this problem when using screen protectors, or cases (I know you said you are not using a case) that cover the proximity sensor. Once I peeled off my screen protector it started working fine again.
There is an app I used to check when the proximity sensor was detecting something and when it wasn't - the app is called ProxyLightTest. Download that then mess around holding your hand over the proximity sensor and see if it has problems. I am guessing you might be using a screen protector or there might be a slight scratch on your screen over the proximity sensor that is messing with your signal. if not then maybe you'll have to send it back.
Hope this helps! Good luck."
Thanks guys I solved the problem thanks to the above poster, seems the radio is affected by the usb brick as soon as that was fixed all the problems stopped
Hello All
I have a HTC one X. I installed Cyanogenmod on it a few days ago and it was running pretty fine. Until last night my phone started to freeze a few times. So I reflashed the rom ect and it fixed it.
This morning I was messing around on this phone and it froze yet again so I held down the power button to reboot the phone.
Now the phone itself turns on but its shows a black screen. I can unlock, I can hear sounds, I can even receive phone calls and text messages and play around on the phone (but cant see anything)
I have tried plugging it in to my pc and going in to the SD card but in order to do that on cyanogenmod I will have to tun usb storage on, on the phone which i cant seem to do.
I am wondering whats going on with my phone and are there any ways to fix it or is this the end of it ?
Regards
Gentle
I am/was having an interesting problem with my SPH-L710. I was recently at the gym listening to music on my phone, and it was functioning normally. I took my phone out of my pocket and pushed the power button, but the screen wouldn't turn on. The music was still playing, so I knew that my phone didn't just freeze. There was no immediate cause for my phone to stop working (ie I didn't drop it or get it wet at the gym), although I've dropped it several times before today without incident.
I took the battery out of the phone for a few minutes and restarted my phone. The phone turned on normally except the screen wouldn't turn on. I called myself from my landline and used the normal gesture to answer my phone and confirmed that I'm able to receive phone calls and that touch controls are working. I also tried booting my phone into both the recovery and ODIN download screens. I'm not sure if I successfully booted into those modes, but I do know that my screen didn't turn on when I tried to boot into those modes.
I took the SD card out of my phone and activated my backup phone through the Sprint website. I tried resetting my SPH-L710 after deactivating it, and the screen was functioning again. I reactivated my SPH-L710, and now it appears to be functioning normally. I have no idea whether taking the SD card out or deactivating my phone actually solved my problem or if it was just coincidence.
My ROM is MD4 with root. I have Team Win Recovery Project v2.5.0.0. My phone has been nagging me to install 4.3 for a few months now, but I haven't gotten around to researching updated ROMs yet.
My phone now appears to be functioning normally. Has anybody experienced anything like this before?