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
Related
After flashing the DeFrost series of ROMS (I am not saying they are the cause of this issue..) from 0.8 to 1.0 ---
I've got an issue where the screen switches itself off during a phone call and never turns on again, unless I pull out the battery and reboot it.
I've just tried flashing Pays BS and RS ROMs and they still to have this issue?
Could it be a problem during flashing just screwed over soomething inside the phone? (Prox. sensor maybe?)
Thanks for your help.
*****EDIT****
I've just found out that if i place the handset (whilst during a call) in very bright sunlight or bright artificial light --- then the screen does re-display.
It's strange however, I'm outside during midday and the screen still is off whilst placing a call. It only registers that the phone is away from my face near a very bright light source.
I've found this issue is faced by many people usually after ROOTing their device(s).
A 'USB-Brick' like issue possibly? (Proxy-Brick lol)
I will attempt to hand in my now HBOOT 0.80 ROOT'd desire to Telstra for warranty tomorrow.
I am now pretty sure that this problem is random and occurs when rooting/flashing a cust. ROM through recovery.
Hi, my Desire HD just automaticly turn on speaker everytime i call someone or recieved a all.
I did some searching and people say turn it off may help. I tried to turn it off (no fast boot) remove the battery, and it still turn on auto speaker
I also realized that sometimes when i turn it on, carpanel automaticly launch. So this might be some problem with carpanel. I turned off the auto option in "dock" section of the setting. Still doesnt change anything
I think the proximity sensor have problems. So i tried some test with it. It's still fine
Can someone help me with this? i even tried hard reseting my phone, it doesnt help
What rom are you using? I had the same problem once, reflashing fixed it.
Sent from my Leedroid powered pocketsized supercomputer using XDA App
I'm using stock ROM , when turn on it says the branding is SFR something. I havent rooted my phone or install any other ROM ever
Well then you could try recalibrating the g-sensor from settings -> display.
Sent from my Leedroid powered pocketsized supercomputer using XDA App
You may have flip for speaker switched on. Go to Settings>Sound and then under Incoming Calls uncheck the option for Flip for Speaker.
abhishekagrawal said:
You may have flip for speaker switched on. Go to Settings>Sound and then under Incoming Calls uncheck the option for Flip for Speaker.
Click to expand...
Click to collapse
That was what I was aiming for. The g-sensor thinks the phone is upside down when in fact it isn't, recalibrating should fix this.
mrhahn98 said:
I'm using stock ROM , when turn on it says the branding is SFR something. I havent rooted my phone or install any other ROM ever
Click to expand...
Click to collapse
ok try this my friend, take battery out, sim out and sd card out, wait a few minutes thn put everything back together and power on the phone, should solve the problem, all the best.
Sent from my Desire HD using XDA App
Hi all. thanks you so much for the support.
I've tried all the above, like turn off carmode, turn off flip for speaker...etc. take out the battery, sim card, sd card. It's still the same. After some digging, i found a topic about this on the DHD forum. They said it was an USB problem. i tried to plug it in to the USB and wiggle it a little bit and carmode/speaker auto turn on and off time to time. I was about to give up and when i'm on my way to return it. It suddenly come back to normal, no problem, tested with the USB cord. This is so weird !!!!! but i'm glad that it's gone away
mrhahn98 said:
Hi all. thanks you so much for the support.
I've tried all the above, like turn off carmode, turn off flip for speaker...etc. take out the battery, sim card, sd card. It's still the same. After some digging, i found a topic about this on the DHD forum. They said it was an USB problem. i tried to plug it in to the USB and wiggle it a little bit and carmode/speaker auto turn on and off time to time. I was about to give up and when i'm on my way to return it. It suddenly come back to normal, no problem, tested with the USB cord. This is so weird !!!!! but i'm glad that it's gone away
Click to expand...
Click to collapse
My other half had exactly the same thing on her Desire, turns out it was dirt/ fluff in the USB socket!
I have the same problem with my DHD, since I don't have the warranty for my set, is there a way around it. Like some sort of app which turns the speakers off when u make or recieve the call. That can make my life easier.
This problem started with my phone too..I tried all above such as changing rom,usb trick,sim+battery+sd remove,calibrating g-sensor ...Only thing i did not try is changing radio..If it wouldnt help me ,i dont know what to do since i dont have a warranty too..Its really annoying..
DHD speaker selfactivating
Those problems /carmode and speaker selfactivating/ started shortly after OTA 2.3 update.I honestly don't remember how I've managed the carmode issue,but initially I was able to solve the speaker selfactivating by pulling out the headphones' plug during a phone call.That did it for a once or twice,as the result lasted for a day or two.After reading the tricks suggested above I tried them with no success until pulling out the phone end of the usb during a phone call while connected to the pc in debug mode.So far I've made a few calls and it looks OK.
I don't want to scary you, but when I had the same problem I found only one solution which works- restore to factory settings... Its a pity...
Hi ,
I have the same problem on my Desire Z. I have had the phone for more then 6 months.
I was running stock: - no problem !
I was running Virtuous Sense 1.0.1 for about 3 months: - no problem !
Yesterday I got this: it auto turns on the loud speaker when I answer or dial.
Flip for speaker is turned off, G-Sensor is calibrated !
I have updated to Virtuous Sense 1.0.2 : same problem !
I have wiped off everything and flashed Virtuous Unity 1.24.0 : TWICE !
Same problem
Sorry for posting under DHD, I did not want to open a new topic on DZ forum , but I will if I must, this is driving me crazy !
I have solved this after wiping all data and flashing the rom again (3rd try !
I told it, there is only one solution- restoring factory settings...
same problem without OTA
Got the same problem since 2 weeks without having done any changes at all to my DHD (still on 1.72.405.3)
+ Car panel starts randomly when connected to USB for charging
+ Phone speaker always on regardless what I tried before
So, I really do not think this is a rom related issue but more a "aging" problem like the GPS connectivity.
Anybody any idea, why the USB plug should be respobsible for this strange behaviour?
I'm not sure this is a USB related issue. It may be the audio jack. My problems started after unplugging the headphones while listening music, to answer the phone.
same problem here ...
My phone also started having the same problem since today morning!
EDIT: So I tried to remove battery, then cleaned the micro-usb port and the headphone port and the issue seems to have disappeared atleast for now. Don't want to do a factory reset as have too much data and apps on phone.
EDIT 2: So as it turns out it was Go SMS Pro problem that was causing the issue since its update 2 days back. The developer has released a new version in Market now claiming to solve the issue.
Anyways whatever issue it is hope it does not return.
Having an issue with my htc desire (it has a stock desire rom)
Basically when my phone goes to sleep the screen remains blank and I cannot seem to get the screen active
when I try to wake up the device as per norm the buttons light up however the screen remains blank..
the phone still seems functional (volume works, etc) however it does not respond to being 'woken up'
I have have done all sorts to try and resolve the problem, this includes checking sd card for errors, resetting phone.
Im a loss to what could be causing this, the phone is a right pain to use now, I go on a call and then screen dims but never recovers, however can still continue with the call.
I have to pull out the battery and restart the phone to have the screen 'wake'
I have looked at these threads of people with similar issues but no one has put up a solution.
http://forum.xda-developers.com/showthread.php?t=980022
http://forum.xda-developers.com/showthread.php?t=892100
Tried testing the sd card for errors still have the problem.
Different SD card still have the problem
I tested it with the sd card removed and still have the same problem.
In airplane mode I still have the problem
With different sim I still have the problem
Tried two new roms, still have the problem (previous to this I had not changed roms in months).
Any ideas? How did other people fix this?
Strangely though after leaving it overnight it woke once the first time this morning. Now back to not waking.
Please help
hi,
another desire owner wrote the same issue on the QA forum...
seen a revealant linked posted by a member...
http://forum.xda-developers.com/showthread.php?t=892100
at first sight seems to be a sd card issue... also have a look on sdfix thread
http://forum.xda-developers.com/showthread.php?t=1010807
happens to me but just once, i just pull out the battery.
looking forward about sd card tweeking
hope this help
As I said it happens whether or not there is an SD card in the phone. And with different SD cards so I do not see how it could be an SD card problem.
Fixed it now. I took it apart then put it back together.
marioxmario said:
Fixed it now. I took it apart then put it back together.
Click to expand...
Click to collapse
I have similar problem here...
Our case is that we can't wake a phone after deep sleep..Touch screen is just not responding. We can see a caller (when somebody is calling) and screen but touch screen is not responding.
After we lock it and unlock it again via Power button, all is just fine...
We caused that by disassembling and assembling the Phone..There was some dust behind digitizer, so we had to clean it...
There must be some strange thing that is not behaving as it should when U proceed
to disassembling and assembling..
So Guys out there...be carefully and think twice before you make decision to disassemble your Desire...
See my reply in another thread.
Stamgastje said:
See my reply in another thread.
Click to expand...
Click to collapse
I realize now that problem that you had, has nothing to do with mine, because I have this issue, with or without Sim card..
Hello. My problem is with the phone's vibrator. 2 or more weeks ago I got the same problem, when I dropped my phone from the bed tot the floor (aprox. 40 cm height), it stopped vibrating for feedback, messages and calls. At that time, I thing I either turned it off and removed battery or just do a reboot, but it started working again until 3 day ago. Since then it stopped working completely. I tried turning it off, reboot, removing the battery for 15 min., nothing worked. I have no vibration feedback (for example when I type a phone number or message), no message receiving vibration, no incoming calls vibration and not even when I turn on/reboot the device does my phone vibrate(it was a small vibration when you turned on the phone). Today I thought I should first try to change my ROM prior to trying to replace the faulty vibrator, but when I selected to reboot to recovery, my phone rebooted and vibrated at the beginning, so I thought the bug is gone. I went back in to the phone and I had: vibrate feedback (typing a phone number), message vibrate, didn't have time to test the call vibration because after I received 2 messages the vibration stopped once again. So now I'm baffled: is it because of the ROM, is it a glitch/bug from the motherboard or is the vibrator almost "dead"? If anyone had this issue and can help me fix the bug I would be really thankful. If I have to replace the vibrator, it wouldn't be a hard thing to do and I would do it if I know this will fix the problem forever.
My phone is S-OFF, rooted, with AcesMod007 ROM. Thank you.
I have installed CM10 | Jelly Bean 4.1.2 - v2.8 by vijendrahs and still no vibration, so it must be from the motherboard or the vibrator itself. I might try to replace it and see if this solves the problem.
No one has encountered this problem until now? No thoughts on this? I've searched for this bug and found some applications that should remove this bug, but they didn't work for me, so I am still open to any suggestion. I still have to wait up to 3 weeks until the vibrator arrives.
L.E.: I've just noticed another anomaly: my phone jumps from 82%-85% battery to full when I'm charging it. Might this have something to do with the vibrator? How can I fix this problem? Thanks.
Tried all kinds of applications that would force the vibrator, but with no success. I am still looking for a solution.
I have no guarantee so I have to fix it myself. I saw that other peoples with the same problem had sent the phone back to HTC for a replace. One of them actually stated that HTC had replaced first the motherboard (with no success) and then the vibrator module. I hope that replacing the vibrator would solve the problem.
I've solved the problem. I decided to open it up, thinking it is a hardware problem, and take a look at it. I've blended the two legs a bit more to make sure they get a perfect connection to the the motherboard and voila. It is working fully.
Hello Forum,
seems that my DHD has an irreparable error.
But i've still a little hope that maybe someone of you guys out there can point me into the right direction to repair the phone again.
What happened:
on December, 20. for no apparent reason the Display started flickering approximately 2 cm from the top.
The upper Part (the first 2 cm from the top of Display) was showing the normal Picture, on the lower Part the Picture was flickering at irregular time intervals, but the touch gestures were still working without any Problems.
Setup at that Time:
- Latest 4ext Touch Recovery
- Latest MIUI.us Rom by bliind
- Custom DPI set to '190' (with ROM Toolbox)
- Max CPU Speed set to 1200 Mhz (with Set CPU)
(Had this setup working fine without any issues for approx. last 2 Months...)
Last change i did before the error occured: Set Custom Boot Animation with Rom Toolbox
The Flickering started not immediatly after setting the new boot Animation but i think 2 days and some reboots later...
Actions that i've already tried to solve the Problem:
1. Shut down the Phone, pull out the Battery, wait some Minutes, reboot the phone.
-> The flickering was gone and the Display looked normal after reboot.
2. After some time I took the Phone out of my pocket and the flickering was there again like before.
Tried to set DPI back to original value '240'
reboot the Phone
-> The Flickering still was there and it seemed to me that the responsiveness of the touch was slightly slower than normal.
3. Reboot into Recovery
Nandroid Backup all Partitions to SD-Card
wipe all partitions except SD-Card
new, totally clean flash of latest MIUI.us Rom by bliind
Reboot the phone
-> The flickering was gone; responsiveness of the screen normal as it was always before.
4. restore all apps; put the phone on the charger over night. everything worked fine again.
on the next Morning this strange flickering was there again; the Touchscreen was very slow responsive in the flickering area
Managed once more to reboot into recovery, but the flickering was now even in the Recovery and on the boot screen.
-> The Touch got more and more unresponsive.
Could no more start a new ROM flash out of Recovery.
5. Tried to access the phone via aahk tool and restored last stock ROM
-> After Reboot the DHD vibrates (like it usually does for startup)
the screen shows a bunch of black and white Stripes that chnge their Color when the Boot Animation should show up,
and later again when the lockscreen should appear.
It makes the boot jingle and i can send Commands via adb.
but Touch commands doesnt work, (tried to put in the Pin blind, but it shows no reaction)
Stupid, but I can't change it: my Warranty and the extra Insurance that i purchased for the DHD ended just 2 weeks before on 6. December.
6. Disassembled the whole phone with Help of you tube disassembling Guide, carefully cleaned all contacts and assembled it again.
-> nothing changed; same behavior like before disassembling.
What can I do? Any ideas except of small rasping and stirring into the soup? :crying:
Can it be only the display? Maybe the Graphic Chip?
Any other ideas?
thank you for reading this all and i appreciate any suggestion that might give my DHD a new spirit of life
Greetings from Cologne
I know it's not what you want to hear, but that sounds like a graphics or display hardware problem...
bananagranola said:
I know it's not what you want to hear, but that sounds like a graphics or display hardware problem...
Click to expand...
Click to collapse
Thanks for your reply!
That was the same what I thougt after disassembling and cleaning with no result.
Cause it seems to me that the Display is still working, but the Signal that's coming in is broken.
I alsready supposed that the Graphic engine is broken.
Just had a little Hope that someone might had the same Problem and got it solved,
before I start practice for mobile phone throwing competition...
i suggest another ROM JB used to cause my DHD flickering (earliear versions)
My DHD was with same problem 1 year a go, and that usually happen when i played games like Angrybirds or Asphalt, or when the device temperature was high.
I was worry at that time, thinking that the device was gone.
Take the same solutions that you had (except disassemble the phone) but they're only temporary.
By that time i decide root the device and install a new rom, (nothing to loose had i think) and Revolution HD was my choice.
After that my DHD didn't flick any more.
I didn't ever know what was the origin of that flickering but for me, that was the big solution.
I'm using Viper Venom 1.2.3 for now, and still with no flickering insues.
So, my advice for you is... give a try to other rom's and kernels, maybe you resolve your insue has i did.
Good luck with that.
Sent from my HTC Desire HD using xda app-developers app
Thanks for you Answers guys,
the Problem i have is, that my DHD does show only sripes even if I try to boot into Recovery, I can't see anything and am not able to start a flash process...
cause i have installed 4ext touch recovery i need the screen to wipe and flash a new ROM.
But i will try to flash an CWM - Recovery through ADB and then to start the flash Process blind by tapping the buttons...
let's see what will happen. There's nothing to loose...
For now, cause I was sitting without a mobile phone at all, I've ordered a cheep one from Amazon... - Huawei U8510 (Ideos X3) -
And oh WONDER!!!: I've got a fully functioning phone with CyanogenMod 7.2 and all the stuff i use my phone for is working without any Probs..
And the whole thing has 2 years of warranty at a cost of € 80,-
only the Display for my HTC would cost € 40,-
so I'm thinking of selling the broken phone on ebay and let anyone try to repair it who is able to....
but I will give it a try to flash another ROM.
Already downloaded the JellyTime R30...
Hello unbeteiligter,
seems that my DHD has nearly the same issues, but with some extra problems.
It seems to be broken since today morning. I wiped the phone and restored the backup I made the afternoon before, and then the first vertical stripes occured. I wiped it and flashed the same rom (CodefireX 4.2.1) again. Same issues. Now I tryed to flash a GingerBread Strock Rom. Even the same issues, and even more shocking is that this problem also occurs in the bootloader, recovery, splashscreen and bootanimation.
Stupid situation, today my Warranty ended.
What can I do? Previously I tougth this is a software problem, but now I think it might be a hardware issue.
Thanks in advance!
daniel_DHD said:
Hello unbeteiligter,
seems that my DHD has nearly the same issues, but with some extra problems.
[...] and even more shocking is that this problem also occurs in the bootloader, recovery, splashscreen and bootanimation.
Click to expand...
Click to collapse
Seems to be the same like my DHD. But for me it ended up 2 Weeks after end of Warranty!
daniel_DHD said:
Stupid situation, today my Warranty ended.
Click to expand...
Click to collapse
The T-Mobile Customer Support told me, that they would have accepted the case as Warranty, if my DHD had ended up during the first week after End of Warranty. Don't know where you bought yours, but maybe there's a small chance for you to get Warranty Support through their obligingness.
If I were you I would try this...
daniel_DHD said:
What can I do? Previously I tougth this is a software problem, but now I think it might be a hardware issue.
Click to expand...
Click to collapse
If your dealer don't accept your Warranty Call, I can't give you much Hope... Sorry for you...
... would imagine you should look for a new phone...
That's what I did....
Similar problem
I have also got a similar problem. Had my phone for two years and have also just hit the same problem. Flashed a new ROM, everything was working fine, then all of a sudden top half of the screen is displayed correctly, the bottom half is always flickering. This occurs in the bootloader as well. Anyone would think that HTC decided to make sure the phone only works for two years and a few weeks after the warranty expires to make sure it experiences problems.