Related
Hello. I have a problem with sound in my kaiser with Android. I tried 2 systems [Cynanogen mod 6 (Froyo) and Myn's Warm Donut], 4 radios (from 1.71 to 1.65) and 2 kernels. Sound never appeared. Why?
what zimage or nbh you using if you are using a older one it might have problems
Did you mean kernel? the newest from this page:
http://it029000.massey.ac.nz/vogue/files/?C=M;O=D
it may be that you have muted the media volume in settings.
No. I don't have any sound. Not only media. When someone calls to me, I cannot hear him too and this person cant hear me too.
Audio issue
I have the same problem. I tried different builds and nothing helps. Any suggestions??
Just a thought, but have you tried flashing a stock rom, then flashing to nand again? Flashing a stock rom clears the entire nand, leaving no possibility of stray bits of data left from custom roms.
I have to say, I get the same thing, but with a slight variation. Sound works for me up until i make at least one call (but could happen before that). Once I make that call, either during the call, or after, the sound is gone. I too had myn's donut, and then frayo, and both times, the exact same problem. I will try to flash the stock rom, and then back to android, but it is a problem that I also share.
This is my first post on xda, so please be nice!
<refresh>.
Mu_aawiyah said:
I have to say, I get the same thing, but with a slight variation. Sound works for me up until i make at least one call (but could happen before that). Once I make that call, either during the call, or after, the sound is gone. I too had myn's donut, and then frayo, and both times, the exact same problem. I will try to flash the stock rom, and then back to android, but it is a problem that I also share.
This is my first post on xda, so please be nice!
Click to expand...
Click to collapse
Yeah, flashed it back to a the most recent stock rom, and then back to andriod.. how works perfectly. Sorry i didnt tell you guys earlier.
I think it was to do with the radio thingy-ma-jig. I flashed it with winmo 6.1 from htc website, and then back again.
Now i'm runnying frayo.
I flashed the newest stock rom from htc site too, then 1.65 radio, but it didn't help :/
Wagierek said:
I flashed the newest stock rom from htc site too, then 1.65 radio, but it didn't help :/
Click to expand...
Click to collapse
That is most likely because you didnt flash it right. take the .nhb from it, plug it into your sd card and flash it from sd. try that.
I'm not stupid. I always flash anything like that-not via CustomRUU-because I have damaged my USB socket and now my Kaiser cannot be recognized by computer.
PS: Today when I booted my Kaiser, next to ANDROID word, I saw "handset status changed to 1". When I rebooted, it didn't show. What's this?
Wagierek said:
I'm not stupid. I always flash anything like that-not via CustomRUU-because I have damaged my USB socket and now my Kaiser cannot be recognized by computer.
PS: Today when I booted my Kaiser, next to ANDROID word, I saw "handset status changed to 1". When I rebooted, it didn't show. What's this?
Click to expand...
Click to collapse
Well, with regards to how I got it fixed (the detailed explanation), i flashed it with a custom winmob rom initially, but surprisingly, the same problem i had with android was happening with the winmob. I could make a call after reboot, but after that call, the sound completely died, and the camera did not work. So i tried to flash with the latest stock rom. I've uploaded the actual roms i used on my public drop box folder here => "i tried posting the link, but because i'm new, it wouldnt allow me...pm me"
I am not a professional on flashing, rather i am a beginner. My tytn 2 is a european T-mobile version. I tried to flash it, it did it half way...then stopped! I tried to do it again, but then it just said "...loading..." and would not go past it. But when i booted to my custom rom, it was still there, but the problems had gone. I guessed that it flashed the radio, and nothing else.
When i then went to android, it worked perfectly.
That was my journey.
I hope that helped... maybe.
Unfortunately, it didn't help.
Any other ideas?
I solved mine by changing radio ROM,but i lost sound and camera in windows,any ROM that fit both android and windows???
What version did you flash?
1.65.14.06
Me too!
I flahsed froyo last night and didn't test after makng calls. I'm having the same issue (lose sound after a phone call). I followed the sticky guide and sim unlocked the radio before flashing (which I think I had already done before). I will try changing radios when I get home to see if this resolves the issue and post my results.
Update: I flashed 1.71.09.01 on my ATT Tilt and this fixed the issue. Now sound and camera work great. Phone runs faster also!
Hey guys, I've looked at other threads but I just can't seem to find the solution. I've installed the new Cyanogenmod. I've installed the ROM and when the phone reboots, I keep getting the 'Touch Android to begin'-screen. No matter what I do, nothing works. I've done full swipes, reboots, tried to only install CM7 (where before I had the Radio and Google Apps as well). Nothing seems to work. Any ideas?
First give some info:
what recovery are you using
s-on or s-off
what hboot - bravo or cm7
how is your sdcard partitioned
i was using CyanogenMod 7 and never got problems.
So, your phone works normally but every time you reboot you have to do the setup from beginning?
Or, does it freeze on the "touch the Android..." screen?
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!
Hi XDA people,
This is my first post in XDA and its a problem i am facing. Whenever i switch to GSM/WCDMA Mode and start using the 3G internet, the phone restarts with 5 - 7 vibrating alerts. I did searched this forum before posting and got similar posting for HTC Buzz
BIG ISSUE: 3G problem..!!
http://forum.xda-developers.com/showthread.php?t=1823816
Went through that and found out that by updating the radio this problem can be fixed, so went ahead to find the udpated radio and hboot and updated them using RUU, got a tutorial for the same in XDA forums
So updated Radio from 7.53.39.03M to 7.54.39.28M
Hboot : 1.08.0000
But the problem is still there, as soon as i switch it to 3G mode, i can see the H symol comes up for the GPRS and the network changes to R (Roaming- no clues why this happens but i am fine with this as long it works.) and within minutes it restarts making 5-7 vibrating alerts before rebooting.
can someone help me with this, is there a way to fix this for HTC Wildfire S (Marvel)
Kernel : [email protected] #2
Android version : 2.3.5
Htc Sense : 2.1
Software Number : HenseMod 7
tonan791 said:
Hi XDA people,
This is my first post in XDA and its a problem i am facing. Whenever i switch to GSM/WCDMA Mode and start using the 3G internet, the phone restarts with 5 - 7 vibrating alerts. I did searched this forum before posting and got similar posting for HTC Buzz
BIG ISSUE: 3G problem..!!
http://forum.xda-developers.com/showthread.php?t=1823816
Went through that and found out that by updating the radio this problem can be fixed, so went ahead to find the udpated radio and hboot and updated them using RUU, got a tutorial for the same in XDA forums
So updated Radio from 7.53.39.03M to 7.54.39.28M
Hboot : 1.08.0000
But the problem is still there, as soon as i switch it to 3G mode, i can see the H symol comes up for the GPRS and the network changes to R (Roaming- no clues why this happens but i am fine with this as long it works.) and within minutes it restarts making 5-7 vibrating alerts before rebooting.
can someone help me with this, is there a way to fix this for HTC Wildfire S (Marvel)
Kernel : [email protected] #2
Android version : 2.3.5
Htc Sense : 2.1
Software Number : HenseMod 7
Click to expand...
Click to collapse
it happened to me, the only solution I found was flash the backup of my original Rom Sense PREROOT, turn on 3G and check that it worked.
Then without turning off the 3G flash another rom clean (a bit like the problem of the gps).
is a bit long but I was going crazy, my Willy sometimes restarted.
it may be useful with my HTC Buzz it worked ... but you're rooted?
quack75 said:
it happened to me, the only solution I found was flash the backup of my original Rom Sense PREROOT, turn on 3G and check that it worked.
Then without turning off the 3G flash another rom clean (a bit like the problem of the gps).
is a bit long but I was going crazy, my Willy sometimes restarted.
it may be useful with my HTC Buzz it worked ... but you're rooted?
Click to expand...
Click to collapse
Yes i am rooted, also i dont have any stock backup
I read in the forums that in HTC buzz if you update to an older radio then wipe cache then update to a higher radio version it fixes it, but i need to find out if that would work for MARVEL, and what would be versions that i should switch to.
thanks for the help
tonan791 said:
Yes i am rooted, also i dont have any stock backup
I read in the forums that in HTC buzz if you update to an older radio then wipe cache then update to a higher radio version it fixes it, but i need to find out if that would work for MARVEL, and what would be versions that i should switch to.
thanks for the help
Click to expand...
Click to collapse
tonan791 said:
Hi Eventcom, i went through the forum and found that you too had this same problem of bootloop after switching to 3g. I see that you have Buzz, just wanted to know will this simiar fix (update older radio, wipe cache, update to newer radio) can be applied on HTC wildfire Marvel as well.
I have posted my question after a lot of search, got similar threads for BUZZ but none for MARVEL, can you please help.
http://forum.xda-developers.com/showthread.php?p=31998311
Click to expand...
Click to collapse
Well, I don't know anything about the Marvel. Both phones are quite different besides their names and enclosure.
Anyway I don't think that your phones radio will be touched when flashing a ROM or restoring a nandroid backup or that you could wipe, clear or format your radio partition - so in theory it could work with the Marvel, too.
A short explanation about the whole thing: The Buzz has well known issues with the radio (no GPS or BT, WiFi probs) - even directly after rooting and flashing the first custom ROM. There's also a chance that something might go wrong or get messed up when flashing different ROMs, installing tweaks etc. and the problem is that the radio resides on a separate partition which can't be wiped or formatted. All this sounds pretty logical to me but I'm not a developer so I might be totally wrong
The solution seems to be to flash a different radio (older/newer doesn't matter) to "overwrite" the current one - and sometimes reflash the current ROM again.
The problem I had has been hard to spot and even harder to solve. Luckily I found out that switching on 3G initiated the reboots (after quite a while and by accident, really). I made a lot of tests and could put it down to that (WiFi, 2G had no probs - phone rebooted only when switching to 3G or switching on data when 3G has been activated/chosen).
Furthermore I found the "solution" by accident, too: I reflashed the current radio without any success. Then I also tried an older radio - no success. So, as a final attempt, I started to download a RUU to reset the phone to factory condition.
The download server has been awful slow - it took ages to download the file - so I (almost randomly) decided to flash the previous radio again.
I couldn't believe it: that did the trick. (Luckily) I rebooted again, switched on data and 3G and noticed that the phone didn't reboot anymore.
So if you're able to flash a different radio - just give it a try. For the Buzz you need to be S-OFF to flash a radio - no idea about your phones.
I'd be glad if that would work for the Marvel, too :fingers-crossed:
I found this tread
http://forum.xda-developers.com/showthread.php?t=1485345
if you do not solve in any other way you could give it a try
I do not know the Marvel, but the Buzz htc are not all the same, the same solution to different results :silly:
eventcom said:
Well, I don't know anything about the Marvel. Both phones are quite different besides their names and enclosure.
Anyway I don't think that your phones radio will be touched when flashing a ROM or restoring a nandroid backup or that you could wipe, clear or format your radio partition - so in theory it could work with the Marvel, too.
A short explanation about the whole thing: The Buzz has well known issues with the radio (no GPS or BT, WiFi probs) - even directly after rooting and flashing the first custom ROM. There's also a chance that something might go wrong or get messed up when flashing different ROMs, installing tweaks etc. and the problem is that the radio resides on a separate partition which can't be wiped or formatted. All this sounds pretty logical to me but I'm not a developer so I might be totally wrong
The solution seems to be to flash a different radio (older/newer doesn't matter) to "overwrite" the current one - and sometimes reflash the current ROM again.
The problem I had has been hard to spot and even harder to solve. Luckily I found out that switching on 3G initiated the reboots (after quite a while and by accident, really). I made a lot of tests and could put it down to that (WiFi, 2G had no probs - phone rebooted only when switching to 3G or switching on data when 3G has been activated/chosen).
Furthermore I found the "solution" by accident, too: I reflashed the current radio without any success. Then I also tried an older radio - no success. So, as a final attempt, I started to download a RUU to reset the phone to factory condition.
The download server has been awful slow - it took ages to download the file - so I (almost randomly) decided to flash the previous radio again.
I couldn't believe it: that did the trick. (Luckily) I rebooted again, switched on data and 3G and noticed that the phone didn't reboot anymore.
So if you're able to flash a different radio - just give it a try. For the Buzz you need to be S-OFF to flash a radio - no idea about your phones.
I'd be glad if that would work for the Marvel, too :fingers-crossed:
Click to expand...
Click to collapse
Thankyou Eventcom, i will try the method, i am searcing for the Radio to downgrade and upgrade too, i did find a link here in xda will search for that again and see if that resolves my problem, thankyou for the details, appreiciate it
Hey guys, its my first post on here and I was hoping to get some help with my device. (Yes, I've searched extensively over the internets. No, I can't find anything related to this issue for the One X)
So let me start from scratch. About a month or so ago, my phone started rebooting randomly, I have been using ViperX 2.7.1 by Team Venom since day one of getting my phone and only started experiencing these issues after upgrading my hboot to 1.31, switching to MaXimus and returning back to ViperX. If it was the occasional reboot, I wouldn't be half as annoyed as I am this very moment. Unfortunately, my phone does not ring when I get a call. Does not ring, screen doesn't even turn on, does not notify, nothing. I called it from another number, did not ring, tried turning the screen on, did not turn on, just rebooted. This does not happen all the time, but has been happening a lot recently. So far, I have fresh installed ViperX numerous times, (wiped cache, factory reset, wiped dalvik cache and full wiped from the ViperX aroma installer) thought maybe an app was misbehaving so fresh installed from the play store instead of Titanium Backup. Even tried switching ROMS but I can't for some reason. Tried installing CM10 the other day, didn't go past the white screen. The good people on androidforums.com told me that I need a different boot.img for newer hboots so I got that, but the CM ring at startup freezes followed by a reboot. Switched to ViperX 3.2 (JB) couple days back hoping this issue wouldn't follow me here as well, but alas, it still has. Then yesterday, I thought upgrading my hboot and wiping my phone the way up'ing the firmware does might fix it, so I up'ed my hboot to 1.39. (strangely though, I still have my files on my sdcard) I followed this guide: http://forum.xda-developers.com/showthread.php?t=1920060 Only step I couldn't follow was the adb reboot oem-78, I got some strange error (did not happen when I up'ed to 1.31) After getting 1.39, I flashed ViperX 3.2 again but I still have this error.
I'm completely out of ideas and am really close to giving up and selling my phone. Any help/advice on what I could do would be greatly appreciated!
Original post: http://androidforums.com/international-tegra-3-one-x-all-things-root/667919-random-reboots.html
Disable AOSP lockscreen in tweaks.
stifler05 said:
Disable AOSP lockscreen in tweaks.
Click to expand...
Click to collapse
Woah, no way. Is that it? It worked perfectly fine before I up'ed my hboot to 1.31 (always used the AOSP lockscreen). Have you encountered a similar issue? I'm trying this out now, will keep you posted.