Hello, I have recently upgraded from ARHD 2.13 to the latest 3.2, and I've noticed that once I connect the phone to the PS3 via USB, the phone completely freezes. This has never happened with 2.13. I have found a similar thread regarding this issue, with no solutions however. The USB freeze ONLY happens on PS3, PC works fine.
http://forum.xda-developers.com/showthread.php?p=12169141#post12169141
As you can see, it happens with Inspire 4G, and I am using DHD.
I would report this problem myself in the main thread, but I can't due to postcount limit. Could someone please confirm this and report in in the main thread?
My thoughts on this is that it might have to do with the Inspire compatibility, as ARHD 2.13 was only for DHD, if I remember correctly, and it did not have this issue at all.
Lastly, I have flashed 3.2, no-sense, advanced power menu and the 3.1 performance patch, if needed to know. Thanks alot!
Related
Hi,
maybe one of you experts would know why this happen :/
Reproduce steps:
1. Boot android 2.2, turn on the Bluetooth connectivity
2. Turn on the Nokia Bluetooth Headset BH-607, it will autoconnect
3. Now without disconnecting Nokia Headset, turn off the Bluetooth on Android
4. Desire will reboot on it's own.
SW specifics like in screenshot.
exception from logcat: pastebin. com / hsinJ4Et
Do you have ideas why this happen?
BR,
Gregory
Are you using Vlingo?
See this if you are http://vlingo-en.custhelp.com/app/answers/detail/a_id/747/p/180/session/L3NpZC9DSENIazVlaw==/sno/0
What ROM are you using?
No vlingo. But thanks for the hint to android bug.
I'm not sure whether my ROM is 2.2.1 on pure 2.2, but I think it's already 2.2.1.
I'm using Leedroid 2.2e with 2.6.32.27 from couttech 925mV/HAVS.
All details can be seen from screenshot I've made.
The interesting fact is normally Desire works fine with this Nokia BH-607 bluetooth kit. But when turning off the bluetooth connectivity (while Nokia is paired) then the Desire reboots on it's own :/
BR,
Gregory
Since you are rooted you may try making a nandroid and flashing another ROM - custom 2.29.405.2 from the dev section. Then do the same, see if it restarts again. If it doesn't it may be that this is fixed or it's just not working in your current ROM. After checking this, you can easily restore the nandroid to your state prior to the flashing.
Also, you may look if it reboots in safe mode.
Hi all!
I've been using Desire for about six months and I've changed lots of ROM's without facing serious problems...
A few days ago I decided to flash a ROM with Gingerbread and Sense UI.
So I flashed LeeDrOiD 3.0.2 (full wiped).
After flashing, I immediately tried to connect to my router, in order to sync my Gmail account and to download some apps.
I noticed that although the device was successfully connected to my router, it could not connect to the Internet.
The browser wouldn't load any site, I couldn't sync my Gmail etc...
Reflashing the ROM and rebooting the router unfortunately didn't solve the problem.
I thought it was a ROM's bug, so I rolled back to another Froyo ROM (Internet was fine here), because I had to leave for vacations and I needed a fully functional device.
Now that I returned to my home, I saw that LeeDrOiD 3.0.3 was out! I flashed it, but I got disappointed when I faced the same problem.
The device was successfully connected to my router, but I had no Internet at all.
Then I flashed AuraxTremeGinger 8.5, and guess what... Again, the exact same problem.
So I asked a neighbor to give me his router's key...
I noticed that when I was connecting to his router, I could download anything I wanted.
Meaning Internet was working just fine!
I never had this problem with any Froyo ROM, never had it with any Gingerbread AOSP ROM...
Only with ROM's which combine Gingerbread and Sense UI.
Can someone find out what's going on here, or at least give me some advice about this?
Change the wireless channel
Sent from CM7
Meaple thanks for the reply!
I changed the channel from 1 to 13 and I noticed something really strange.
If I try to load any site within 4-5 secs from the time I change the channel, the site will be successfully loaded.
After 4-5 secs, nothing will work.
Which means that I have Internet for the first 4-5 secs (from the time time I'll change the channel), and afterwards nothing...
Did you flash new radio and ril.zip for gingerbread?
Most of gingerbread roms' ril are not for GB.
S-off RCMIXv8++ cm7hboot
htc-ril2.2.0131HM
You don't need the RIL if you're using the 2.3.3 Sense ROM as it's already in it. Radio is recommended, though
Thanks for the replies!
I flashed the 32.56.00.32U_5.17.05.08 Radio (which is the recommended one for LeeDrOiD), I even upgraded to LeeDrOiD 3.0.4 but still no luck...
It's really frustrating cause I can't understand what's going on...
Hi once again!
I revived the thread, only to mention that the problem was fixed by upgrading my router's firmware.
Hello all.
I hope this is in the right section. I have tried looking here:
http://forum.xda-developers.com/showthread.php?t=896213&page=447
For any answers, but at over 400 pages it's taking a while!!
I rooted via unrevocked the other day, and flashed Redux. I quite like it but am having the following issues:
WiFi, works fine at home, picked up the signal and signed in easy as. At work however it can't detect anything. On the stock 2.2 it was fine. This is a magor as 3g here is pretty slow. If I can't get WiFi working properly I'm going to have to look for another ROM.
Sound settings in menu. FC's every time.
Camera, may not be an issue as such, but does anyone know how to disable the camera sound? It's incredibly loud and annoying.
Cheers for your help, and if this is in the wrong place please point me to the right one!
Oh just point out what I have or have not done to try and fix this:
I have restarted WiFi router. No change. It was working fine until I flashed Redux.
Works fine at home, and can detect the neighbours WiFi.
I have flashed latest radio ROM 5.17.05.23
I have reflashed Redux. But did not to another complete wipe.
Have tried rebooting and hard reset (remove battery)
Fixed the sound menu issue with a full wipe and reset.
WiFi still not picking up at work. Have flashed a new Kernel 2.6.35.8 manu 1.4
Will see if that chnages anything
For me the screen flickers when I use Android Market and scroll up and down!
Very annoying!
Ok new kernel changed nothing.
Did full wipe are reflash. No change.
Flashed Leedroid 2.2 ROM. WiFi at work instantly working fine.
So flashed Oxygen 2.3 ROM. No WiFi at work.
There is something in those 2 GB ROMs that stops my Desire seeing my works WiFi net work. Any ideas??
I would try to flash radio:
http://www.mofirouz.com/ahp/?file=htcdesire/radios/32.56.00.32U_5.17.05.23.zip
I hope you know how to do this. No warrany for any damage.
Cheers for the reply.
I have that radio already.
It seems it is a very common issue in 2.3 and is to do with hidden SSID on the WiFi.
Not sure why it affects 2.3 and not 2.2 but lots are complaining about it.
Will have to find out the SSID to connect
I seemed to have cured my SSID issue
http://www.appbrain.com/app/wigle-wifi-wardriving/net.wigle.wigleandroid
Got me straight in. Once I had connected, reconnecting works fine. I even uninstalled the app to check and it's sweet as
Device: Desire GSM
I installed insertcoin 1.1.3 on monday and it seemed to have sorted the problems I had with crashing sense.
However I did have a problem with usb detection on win7 64 at one point. I had a demand for a scan pop up- this is something that occured frequently when my camera was still crashing. I cancelled the scan and Win7 sprung me a device error. That had not happened before.
I just unplugged/replugged and the issue was solved.
The next day I saw the 1.1.3 and 1.1.4 updates solved usb tethering issues. I figured why not try and updated, then flashed the kernel (without booting).
Result: windows won't recognize the device anymore, doesn't accept android usb drivers for it (the device returned an error). It is shown as unknown device in device manager. Furthermore, after trying to connect the card can no longer be mounted by the phone.
A restart sorts it, but it's still not very satisfactory. Does anyone have the same problem?
Did I flash the wrong kernel? It said bravo...
Meanwhile I'm going to go back to 1.1.2 and stay there...
Sounds like usb brick. A guide how to fix can be found here on xda.
TouchPaled from Oxygen with Transparent XDA App
Not a phone issue
Well I went back to 1.1.2, flashed a different kernel, flashed leedroid, then back to 1.1.2.. all of which gave no joy. Same issue exactly.
However finished my sick leave and it connects fine on my work pc.
So it's probably the cable and I'll check that tonight (was a bit too ill to crawl around the back of my home desk) and report.
(for those who found this by searching I guess RMD recovery is the USB Brick fix.)
No that's not the usb brick fix, it's a recovery. By using the search one can find a guide extra for usb brick.
TouchPaled from Oxygen with Transparent XDA App
So it turns out to be a faulty cable, and that is that.
EDIT: SOLVED!!!! it was a usb brick. see last post for details.
hi all,
I have a problem with my desire.
Bluetooth won't turn on. If I try to enable BT, it says grey'ed out for like 10 secs and the goes back to unchecked.
I got this device used so I don't have many background information. All I can tell is I tried different ROMs and wiped all I could, but still no luck. I actually highly suspect this might be an hardware issues, but I'd really like to try everything before shipping back to assistance.
Here are my current specs:
htc desire amoled
bravo pvt1 ship s-on
hboot 0.80.0000
radio 5.11.05.27
rom cyanogenmod 7.1.0
kernel 2.6.37.6-cyanogenmod-geb50077
Recovery: Clockworkmod
ANY hint highly appreciated.
Got exactly the same problem.
BT worked while running the former stable CM release. I first noticed this issue when flashing latest CM. You tried other ROMs which didnt work?
Did you try other Radios as well?
I am not an expert, but I think it could be a problem of the radio. I never totally understood what the radio does, so could anybody help with this guess? I never changed Radio as there was no need for (never touch a running system).
lexo, did you try rolling back to 7.0.3 to see if BT would work again?
I was also thinking about radio, exp b\c it seems to not be a ROM-specific issue, as I have tried several: LeeDroid, InsertCoin, MIUI, as well as a stock rom.
I believe the point with radio is not necessarily about having the latest, but finding the one that works well with one's rom. Also, there is RIL, but that I don't know what it does.
No, didnt try that yet.
I use BT in my car to listen to music only so I didnt notice the issue at first. Now i am thinking about buying Galaxy Nexus, so I am not too exited about that point. But as I am willing to pass my Desire to my lil sister I would love to have it fixed.
Whats "RIL"? Think I never heard about it.
Don't know if this is relevant but had a similar problem with Bluetooth, wifi and Mobile data yesterday. None of them had connectivity!
The remedy that worked for me was to wipe the cache and dalvik, reflash CM7.1 via recovery (but remember to also flash the Google apps package) and soft reset.
No data is lost this way.
Hope that helps!
Sent from my HTC Desire using XDA App
This may not be relevant but when I couldn't enable Bluetooth on my done when I have a USB brick.....
Try the USB brick fix it may work
Sent from my HTC Desire using XDA App
update:
so far I did:
- wiped everything including dalvik and reflashed cm7 - no luck
- removed files in etc/bluetooth [read somewhere] - nuthing
- applyied a .zip update that is supposed to fix a possible USB brick - no change.
@LEXO: I think you might try the first two things I did, in your case they might work.
So now I flashed a RUU Rom and reverted to stock s-on bootloader, hboot, radio (ril, too, I believe, though I dunno how to tell ril version) and recovery.
The only thing I'm not completely sure about is the USB brick fix, but otherwise it's ready to ship to assistance.
@Reaper, can you point me to the USB fix you referred to?
guys!!! Thanks everyone, expecially reaper.
My BT is working again!!! turn out it was a USB brick, which I was able to solve fairly easy.
I had tried a usb brick fix that involved flashing a .zip, which I did. However still no BT changed so I assumed phone was not bricked after all.
Also, I always assumed usb brick would involve major cd and usb connect malfunctions, and that was not my case at all.
However it must have been that fix that didn't work, because I then followed the guide on this forum http://forum.xda-developers.com/showthread.php?t=691639: got my CID via fastboot, modified the files accordingly, put them on sd card, got temp root with visionary, issued the necessary commands with "free root system tool" terminal, rebooted, and voilà! BT is finally green.
I can't believe I made it!