Related
ok i get this issue everytime i install a new hero rom on my MT3G.
i will be trying to call someone and it will start ringing but then the audio gets cut off, orr it will complete the call and the audio gets cut off during the call. point is Audio gets cut off and i am unable to make proper calls. and sometimes my phone will even reboot when this happens.
i dont have this issue on the stock rom or cyanogens roms. So i know it has to do with the hero roms and not me or my phone.
I really love the hero roms but this problem makes it impossible for me to enjoy them.
someone please help me out.
*Edit: i had posted a thread about this a while back and found a hero rom that didnt give me this problem, JACxHEROSki-v1.7r2, but when i ventured on to other hero roms the problem occured once more.
Im swearing off Hero Roms until someone can figure out this problem, or until i start having Hero withdrawals lol
ok im getting some people viewing this post but no feedback, thankss alot guys
Try eVil's rom..
I want to know when will the sound problem be fixed completely? im currently using fresh 1.5 because all of the 2.1 have problems with the sound.. when someone calls i cant hear them and they cant hear me! i cant be resetting my phone everytime this happens. the fix that they have dont work also it might prevent it from happening so often but all my calls are important... does any one know when this will be fixed fully or why is this happening? how to prevent it ? mayb its the cdma settings? Thanks alot
The audio problem for the effected phones will be fixed when official 2.1 comes out.
i found whats causing it.... so who has a nice rom with the older kernel before .29 .. wats the kernel ? lol
The issue is caused by audio drivers in the kernel not resetting. we do not have the source for .29 kernel so there is no fix. we dont know why this effects some people and not others. Since the audio drivers do not reset it does not allow anything to read them. so it continues resetting and resetting and this causes the cpu to be pegged by the constant retry and retry.
Any 1.5 or overclocked 2.1 Rom
The audiofix posted by avalaunch worked briliantly for me. I have not had the issue once since he posted his fix about two weeks ago.
Also just so you know, zens my touch Rom did not have the audio issues for me. Just be sure to reboot after the first boot to completely get everything working.
which fix the audiofx or audiorc?? or u on the newest one for testers? i hate the my touch roms omg lol whats the older kernel version
wait another thing could it be because we didnt update the radio ?? or u guys doubt that 1?
I have had the audio issue with every ROM i had used until i flashed the Dachdroid 2. Ever since i have not had any kind of issues with phone freezing or caller not hearing me when i answer. Its very strange, but i wanted to post to see if any of the Devs can find out the differences between whats in this ROM and all the othersthat would make it work. Again i have had audio issues with all except this one.
What is this Audio problem?
I've run ROMs with both the .29 and hacked up .27 kernels.
Is this a bluetooth audio problem? Or handset audio?
The problem occurs randomly, for me at least. It's an issue I've had as others have that no audio at all comes through after an unknown time. I notice mine is triggered when I get off the phone with someone, I get 'call lost' and then all my audio is gone and have to reboot to get audio back. It affects BT and handset for me.
Iv never had the problem and iv changed my radio quite a few times. I think im on my 4th radio.
Maybe later at night you could flash a 2.1 rom, change to a newer radio and give it a few test to see if it works.
Flipz has alot of radios and I think the stock one on his site.
(IF anyone trys flashing a radio this is really the only way you can brick your phone. DO not flash any radio unless it says CDMA htc hero. All of them are on flipzmode website. You cant go wrong if you get them from him.)
the issue will hopefully be fixed when they release 2.1 officially. and im still looking into the issue a little at a time. 99% of people reported that one of the two updates put together fix it.
the only other cause could be a hawrdware issue. like the moved one resistor on the board and this causes something in the kernel to restart drivers. idk that is a very very very simple thought. but anyways like i said hopefully it get fixed!
Dont know if this is related but its absolutely killing me
Just today the headset icon popped on and wont go away. I cant hear anything when using the phone because its stuck in this mode. I plug in headphones and the voice dialer starts. I can hear through the headphones, but taking them out does nothing.
Anyone have any info on this or if there is anything I can do?
yea thats y im on fresh 1.5 i hate the 2.1 simply because of the audio problem coming from the headset !!! andn darch droid2? does everything work correctly like camera ect ... i hope its not that dam mytouch theme that 1 sucks ill try tonight
killacammiami said:
yea thats y im on fresh 1.5 i hate the 2.1 simply because of the audio problem coming from the headset !!! andn darch droid2? does everything work correctly like camera ect ... i hope its not that dam mytouch theme that 1 sucks ill try tonight
Click to expand...
Click to collapse
yeah...Ive come to the conclusion that 2.1 is just not going to work for me...went back to fresh 1.1 and everything is good. Its funny though, Ive been on 2.1 since all of the work was done and never had a problem until now. Ive been on damn near every 2.1 rom and didnt have an issue. Now all of the sudden the handset icon shows up and I cant hear anything unless I put in headphones. Tried all of the audio fixes and searched the entire net looking for a resolution. Hopefully the official comes soon. I am definitely going to miss 2.1.
No1Lives said:
Just today the headset icon popped on and wont go away. I cant hear anything when using the phone because its stuck in this mode. I plug in headphones and the voice dialer starts. I can hear through the headphones, but taking them out does nothing.
Click to expand...
Click to collapse
That's more than likely a mechanical problem. Take it in to Sprint.
posguy99 said:
That's more than likely a mechanical problem. Take it in to Sprint.
Click to expand...
Click to collapse
I would think so too, but I went back to fresh 1.1 and its fine...
I'd go back, but then I'm stuck with not being able to receive picture messages. So far I get the audio problem every other day, and it's a simple reboot.
DexSade said:
I'd go back, but then I'm stuck with not being able to receive picture messages. So far I get the audio problem every other day, and it's a simple reboot.
Click to expand...
Click to collapse
a simple reboot ? a simple headache lol idk about u guys i dont want to have to restart my phone when i just got a call that i couldnt answer !! ..... is there any newer roms with the older kernel?? because i dont understand the whole kernel thing...
This audio loss issue is reason number one why all of the people who say "Who cares when HTC and Sprint release 2.1? We already have it!" are just total idiots.
Looking to stick an android rom on my hd2, wondering if you guys can help me out looking for one. which is this smoothest running and has the least issues. whether its 2.1, froyo with or without sense. thanks yall
thatg said:
Looking to stick an android rom on my hd2, wondering if you guys can help me out looking for one. which is this smoothest running and has the least issues. whether its 2.1, froyo with or without sense. thanks yall
Click to expand...
Click to collapse
Any build that I have used from Darkstone has been smooth and fast. You can download the latest "clean" froyo build or the "sense" themed froyo build here:
http://gamesquare.co.uk/froyostone.htm
Imho, the clean froyo build is a bit faster.
i used the max energy co0kie energy ROM for win mo, used hardspl 3, the latest radio, and used the latest froyostone sense build, and the jmz dual boot .cab, everything is working pretty good... when i turn the phone on, i can boot co0kie energy win mo, or android 2.2. now im pretty happy with my device
pbleonidus said:
i used the max energy co0kie energy ROM for win mo, used hardspl 3, the latest radio, and used the latest froyostone sense build, and the jmz dual boot .cab, everything is working pretty good... when i turn the phone on, i can boot co0kie energy win mo, or android 2.2. now im pretty happy with my device
Click to expand...
Click to collapse
awesome. your voice calling and speakerphone are working? i almost have the same setup as you except i'm using chucky's rom. voicecalling works perfectly. no echoes no robotic voices. i may try energy rom some time this week although i like chucky's + gtx white theme.
ryan562 said:
awesome. your voice calling and speakerphone are working? i almost have the same setup as you except i'm using chucky's rom. voicecalling works perfectly. no echoes no robotic voices. i may try energy rom some time this week although i like chucky's + gtx white theme.
Click to expand...
Click to collapse
i havent been able to try any sort of calling on the android os yet, but everything works great on co0kie energy win mo os...
pbleonidus said:
i havent been able to try any sort of calling on the android os yet, but everything works great on co0kie energy win mo os...
Click to expand...
Click to collapse
cool, let me know if the voice calling works.
btw, here's a thread over on the android hd2 development section consisting of a growing a list of the fastest and most stable build+ rom combinations including a running list of what does/doesn't work on some builds
http://forum.xda-developers.com/showthread.php?t=749110
this should help the OP of this thread as well.
calls sound great, speaker phone works, camera works, camcorder works, bluetooth turns on (havnt tested any pairing yet) flash works, everything seems to work execpt the folowing:
flashlight only works on brightest setting
and when i put the phone to sleep, the keypad led lights stay on, but i read from froyo on a different build that this happens to some people, it could also be a problem with the .cab i installed on win mo, i have it set that whenever win mo is being used/ doing something, the leds stay on, instead of shutting off after 10 seconds, so it could be win mo still is doing some task, like running sense (i have the sense version of android) and thats why the stay on... ill try to figure out the problem soon. (and this doesnt happen when running win mo...)
pbleonidus said:
calls sound great, speaker phone works, camera works, camcorder works, bluetooth turns on (havnt tested any pairing yet) flash works, everything seems to work execpt the folowing:
flashlight only works on brightest setting
and when i put the phone to sleep, the keypad led lights stay on, but i read from froyo on a different build that this happens to some people, it could also be a problem with the .cab i installed on win mo, i have it set that whenever win mo is being used/ doing something, the leds stay on, instead of shutting off after 10 seconds, so it could be win mo still is doing some task, like running sense (i have the sense version of android) and thats why the stay on... ill try to figure out the problem soon. (and this doesnt happen when running win mo...)
Click to expand...
Click to collapse
i'm experiencing the same exact thing but the froyostone dev has stated that this is a known issue and it will be fixed upon the next build
would the next build the fix is in be the agust one, or the next one as of todays date? because yesterday the agust build came out, and i beleive that is the one i have installed, is there a way for me to check which release date i have?
Shubcraft cm6 v1.2 is very fast and stable and 98% off the things work on it...and i think the theme is pretty neat...
Sent from my HTC HD2 using XDA App
pbleonidus said:
calls sound great, speaker phone works, camera works, camcorder works, bluetooth turns on (havnt tested any pairing yet) flash works, everything seems to work execpt the folowing:
flashlight only works on brightest setting
and when i put the phone to sleep, the keypad led lights stay on, but i read from froyo on a different build that this happens to some people, it could also be a problem with the .cab i installed on win mo, i have it set that whenever win mo is being used/ doing something, the leds stay on, instead of shutting off after 10 seconds, so it could be win mo still is doing some task, like running sense (i have the sense version of android) and thats why the stay on... ill try to figure out the problem soon. (and this doesnt happen when running win mo...)
Click to expand...
Click to collapse
I would suspect that whatever the CAB is you have installed probably changes a register (not registry) in the micro controller that controls the keypad and its lighting. As long as this microcontroller doesnt get a reset signal or power loss it is going to keep that register set even when booted into android.
As far as i know when using HARET WinMO is no longer running, but please correct me if im wrong, ive tried to find some detailed info on how HARET works, but haven't found much to date. I always wondered if android was truly running all on its own, or if HARET was something like a vmware translating android calls to winmo api calls with winmo still running the show under it all
Before you boot into Android make sure the bottom keys aren't lit. That's keep your keys from turning on at all in Android.
Sent from my HTC Desire using XDA App
d0ug said:
I would suspect that whatever the CAB is you have installed probably changes a register (not registry) in the micro controller that controls the keypad and its lighting. As long as this microcontroller doesnt get a reset signal or power loss it is going to keep that register set even when booted into android.
As far as i know when using HARET WinMO is no longer running, but please correct me if im wrong, ive tried to find some detailed info on how HARET works, but haven't found much to date. I always wondered if android was truly running all on its own, or if HARET was something like a vmware translating android calls to winmo api calls with winmo still running the show under it all
Click to expand...
Click to collapse
Yes, haret completely shuts down winmo and boots linux. There is nothing else running when you're using android.
Dual Boot
Can someone help me? I am trying to dual boot but it is not working. I read somewhere that you need to change HKLM/init launch 52 to Launch 62 but there is no Launch 52 on my phone.
Well this is for people. Who dnt know yet but if u use a ROM (windows) ROM u can run android on it. But first the ROM needs to be android capable... like for instance I'm usein a gtx ROM I forgot the name but its a gtx.. but anyways... wen u run haret. Nd wen it boots up into android use the android for long period of time before locking. The screen lyk around 50 mins... or u can have the music playing in da back ground.. it will prevent it from the SOD... ive been running the android build. Of matte nd froyo 1.7 for 24hours.. nd still no lag or SOD .. idk if it works wid all builds of android. But it work's. With the matte nd froyo
Srry. If I'm spelling. Matte or mattec wrong..
"...But first the ROM needs to be android capable...." yeah right
Bull,normally it doesn't matter wich ROM u use. Another thing is the Radio version.
Sent from my HD2 using XDA App
for me if i use android like 3 to 5 times after screen of death it will stop and it wont screen of death ever but when i have to reboot into windows it will do it over again wierd
I use an autoboot set for six seconds, it prevents sense from completely loading and I have found that to prevent sod for me using an energy rom 2.10 radio and warrenb's android build. If I go into windows I reboot and go into android with the autoboot. I never boot android from within windows.
Sent from my HTC HD2 using XDA App
hi i have tried to install various versions of android on my hd2 but all seems to have common problem touch screen freezing for few seconds and then works properly. i am using radio v 2.14 and currently using stock win rom but tried other roms too. Can you guys tell me the solution for this problem and suggest a rom with upgraded win version but stock looks as there are many roms out there and its hard to find the one, which is least buggy , have stock looks and runs android well.
Yeah bro i know how you feel.. it kinda sticks when you press the end call key, stays black screen for a few secs before responding, its not a killer prob but we would like to see a fix.. anyone got one