Related
Hi All
I have used SRS WOW for my Dopod 838Pro for years and loved it.
This is the one enhancement that is a must have for enjoying your music on some decent headphones - way better than HTC's native Audio Booster.
I have messed with the assortment of readily available cab variations (1.2.1, 1.5.1, the arm panel etc), reg hacks to fix the driver issue, resets etc. all for the last few days but cannot get it to run successfully on my TP2.
The issues are:
The 1.2.1 version will install, you can apply the flag reg hack (which works), reset, plug in your headphones and tweak away - great, it works!
The problem is that the TP2 will go into its screen-off sleep mode and just not wake up. You need to remove the battery for it to run again but the same thing happens - bugger!
I have also had the conflict issue with MS Voice Command not being able to start. BTW, Voice Command on TP2 is great!
So, i was wondering if anyone has it or (them both preferably) working successfully on their TP2?
I would really like this to be available for all users as it is really such a great addition to your phone.
Any input greatly appreciated (really want this)....
Cheers to all
Jabberoo
I do apologise if this is bad, but i am gonna bump this to keep it going.
I feel that an answer/solution by someone here with great skills would benefit so many of us as this is a very good little addition to the TP2.
Anyone...?
Cheers
Jabbero
Hi All
Still really interested in getting this sorted.
I have tried virtually all available WOW types listed on this site (and elsewhere) with no luck.
I tried one called called "dsixda SRS WOW English.cab" (repacked from a Chineses ROM), this actually ran for a whole day and was really promising, but then my device eventually stayed in sleep mode (like all the others) - sigh. It too caused a conflict with MS Voice Command.
So back to square one - Buger, bugger, [email protected]
Really want these 2 to work as they are a most valuable addition to a good device.
Can anyone put their genius to sorting these out for us all...?
Cheers
Jabberoo
iirc wow hd conflicts with htc audio booster. Will work flawlessly, but you will need to turn off touch flo..........
i did this on my diamond and used SPB shell instead............... Only solution i know of, sorry.
Thx Charms
I see. I was hoping there would be a way to get this happening, by way of someone's insightful genius, as it is a very worthwhile inclusion for our devices.
It's funny that, for me at least, having good sound through headphones is a key element of having this device and it is the one thing that seems underserved in general. HTC's equalizer really pales in comparison to this little cab. Equalisation of sound just doesn't do the same thing...
Maybe that is a cue for a project, disect the SRS app and make one that doesn't share its downsides...??
Cheers to all
Jabberoo
Anything new here?
I´m also still looking for a solution....
Whumpscut said:
Anything new here?
I´m also still looking for a solution....
Click to expand...
Click to collapse
Sadly no, it is staggering with the levels of ingenuity on this Forum that this issue has everyone stumped............??
It is the one add-on that makes such an enormous difference when listening to music thru headphones on virtually any device. I think now SRS even make something specifically for iPhone (bloody iphoners!)
Cheers
Jabberoo
Still no good news?
It´s a shame....:-(
It so happened that I installed the SRS WOW HD version 1.5.1.0 yesterday and it's been working like a charm - even the sms notification sounded better than before!
installed SRS WOW and it worked but it caused A LOT of problems
one, i played using the Sense player and i couldnt lower the volume although the meter was showing it was on silent the music was still blairing on my headphones
i unplugged it and plugged it back in and it works, another problem occurs, most of my music wont play anymore :/
gave up on it and i just fiddled with audio booster and got the best setting out of it.....
XERO_Racer said:
installed SRS WOW and it worked but it caused A LOT of problems
one, i played using the Sense player and i couldnt lower the volume although the meter was showing it was on silent the music was still blairing on my headphones
i unplugged it and plugged it back in and it works, another problem occurs, most of my music wont play anymore :/
gave up on it and i just fiddled with audio booster and got the best setting out of it.....
Click to expand...
Click to collapse
Which version did you install? I had a problem with SOD from an old version some time ago and had to uninstall it - just seen a new version: http://forum.xda-developers.com/showthread.php?t=584626
Haven't tried it yet, but some posts on that thread state works with TP2.
I just tried installing version 2.1 that was posted on the first post of that thread on my unbranded TP2, with Sense 2.1 and Winmo 6.5. Unfortunately, I got a standby of death within 2 hours of installing it. Hope this SOD thing gets resolved eventually.
dgco86 said:
I just tried installing version 2.1 that was posted on the first post of that thread on my unbranded TP2, with Sense 2.1 and Winmo 6.5. Unfortunately, I got a standby of death within 2 hours of installing it. Hope this SOD thing gets resolved eventually.
Click to expand...
Click to collapse
Yes, installed it myself today and had SOD before I even had chance to use it! I installed it and soft reset as instructed but then was at work and when checked my phone for email... SOD! Thought it was maybe because I had it charging off a PC without Activesync installed, reset and after checking it had rebooted, I went to lunch and it had SOD'd again on my return. Rebooted, uninstalled SRS WOW and soft reset and no SOD all afternoon.
Running latest stock 6.5 WWE ROM with Sense 2.5.
yeah, i hope the wake up gets fix...i would like to use this app....
Wow..thats all I can say. Wow because it actually produced great results and wow because it caused my phone to sleep every time the backlight went out. Uninstalled and no problem since. I was ready to take my phone back.
Seems even not necessary to uninstall, SOD went away by just un-clicking enable SRS tic box, I couldn't figure out how to un-install WOW HD anyway
Got the SOD myself using it. Took it off & everything was fine, but I task 29'd & reflashed my ROM. Wasn't taking no chances.....
Hi,
I'm struggling with the Sleep Of Death issue as well (WM 6.5.5 and SRS WOW HD 2.1). I've even found a fix for Omnia which involved a registry edit that - I'm guessing here - told the device not to hold devices "wav1" and "wav8" when going to sleep mode, but, apparently, what works for Omnia, doesn't help at all for Touch Pro 2.
Anyone who will make SRS WOW HD working on my TP without the SOD will be my hero. Any help?
i want to say this app allows me to listen to the radio while in the shower its that loud!!
when i get out the shower i cant turn my phone back on aggghhh!!!
please a fix???????
l have trying to find a android rom that Bluetooth and earpiece dose work for our touchpro2 and no answer so far.could someone tell me whether i can find it in roms from xda or neopeek now, or we have to wait?
sharemoon55 said:
l have trying to find a android rom that Bluetooth and earpiece dose work for our touchpro2 and no answer so far.could someone tell me whether i can find it in roms from xda or neopeek now, or we have to wait?
Click to expand...
Click to collapse
BT doesn't work currently on the RHOD. Hopefully soon, just don't hold your breath.
This isn't meant to replace WinMo at this stage. Read, have fun with it, read some more... Pretty much every single major issue has been reported.
..........
I want to contribute to this thread, I am a longtime user of Android on the TP2, I donated to the project when we got sound working.
Basically, I am keeping my fingers crossed for bluetooth to be the next working feature. I can get by without the camera, and the power management, for me at least is fine because I can plug my phone in all the time.
However, my job requires me to be on a bluetooth headset a lot, especially while driving, so that is my only hangup for not using Android 24/7 .
I will reiterate.
This isn't meant to replace WinMo at this stage (maybe never). Don't expect it to be able to.
arrrghhh said:
I will reiterate.
This isn't meant to replace WinMo at this stage (maybe never). Don't expect it to be able to.
Click to expand...
Click to collapse
I have more issues with WinMo than I do with Android, it has replaced WinMo for me personally. The only time I run WinMo is if I need a hands free device.
sizeth3 said:
i have more issues with winmo than i do with android, it has replaced winmo for me personally. The only time i run winmo is if i need a hands free device.
Click to expand...
Click to collapse
then go buy a vibrant or hd2
arrrghhh said:
BT doesn't work currently on the RHOD. Hopefully soon, just don't hold your breath.
This isn't meant to replace WinMo at this stage. Read, have fun with it, read some more... Pretty much every single major issue has been reported.
Click to expand...
Click to collapse
Hi aarrrghhh
Is there an idea when BT would be available/ready?
jonners59 said:
Hi aarrrghhh
Is there an idea when BT would be available/ready?
Click to expand...
Click to collapse
When it's fixed? Until someone with the knowledge steps up and takes the time to troubleshoot it...
Problem is, devs are just like us - they want to work on things that interest them. So until BT is a priority for a dev, it won't get a lot of attention. Seems a lot of focus right now is on framebuffer/graphics performance and battery life (panel init).
There was a lot of work on the camera as well, not sure where that stands - someone was able to get a functional preview on their phone tho.
Basically if you don't have the knowledge to fix it, don't ask when it's going to be fixed. These things don't just happen... Someone has to work at it to get it up and running.
New XDAndroid user, first time poster,
I've been searching through all these threads like mad, and I've discovered that there is NOT, nor is there likely ever to be, a BT working build for Rhodium. I get that, and view the XDAndroid builds as a godsend anyway. Android kicks WinMo's ass, BT or no.
I've also found that there's a buggy headset workaround (that I haven't gotten working yet) but I plan to keep trying. My question is (and I keep searching the threads but I can't find it answered) - does the headset workaround let you use a wired headset to make phone calls? I mean can I both hear and speak through the headset?
Thanks!
bndtdog said:
New XDAndroid user, first time poster,
I've been searching through all these threads like mad, and I've discovered that there is NOT, nor is there likely ever to be, a BT working build for Rhodium. I get that, and view the XDAndroid builds as a godsend anyway. Android kicks WinMo's ass, BT or no.
I've also found that there's a buggy headset workaround (that I haven't gotten working yet) but I plan to keep trying. My question is (and I keep searching the threads but I can't find it answered) - does the headset workaround let you use a wired headset to make phone calls? I mean can I both hear and speak through the headset?
Thanks!
Click to expand...
Click to collapse
Kinda OT for this thread, but try it out - let us know if it does work. I want to say it does, but I don't have a wired headset to test with.
I also never meant to give the impression that BT will never work. Just that it's not actively being worked on (to my knowledge) and won't really get the attention it deserves until a lot of the other work going on right now settles down. It's one of those things, devs work on what they want to work on... sure it sounds selfish but they're doing this for their own personal interest - not because someone else really wants the feature.
So that's the unfortunate truth. Until a dev takes an interest in fixing BT, it's not going to get fixed. Either you can gripe about it not working (which really isn't useful, and I'm not saying you are or you're the only one complaining....), or jump in and try to help!
Doesn't sound selfish at all. Devs needs to do what they're interested in doing. Devs donate their time and skills for fun and for the good of this community, not for some guy who complains that they didn't magically turn his winmo phone into a fully functional android. You want android, buy an android. Anyone who complains about the lack of BT doesn't get this.
Still can't get the damn headset working, but that's my issue. I'll keep reading and working on it.
bndtdog said:
Doesn't sound selfish at all. Devs needs to do what they're interested in doing. Devs donate their time and skills for fun and for the good of this community, not for some guy who complains that they didn't magically turn his winmo phone into a fully functional android. You want android, buy an android. Anyone who complains about the lack of BT doesn't get this.
Still can't get the damn headset working, but that's my issue. I'll keep reading and working on it.
Click to expand...
Click to collapse
if you want the headset to work, put "snd.force_headset=X" into the startup file and replace the x with a 1 for the usb headset and a 2 for the 3.5mm headset. After that, go to you phone in wm and call your voice mail with the headset in the phone. While still in the call, boot into android. It should work for music but i haven't tested calling. Unfortunately, if you do this, then the speaker wont work.
kdub94 said:
if you want the headset to work, put "snd.force_headset=X" into the startup file and replace the x with a 1 for the usb headset and a 2 for the 3.5mm headset. After that, go to you phone in wm and call your voice mail with the headset in the phone. While still in the call, boot into android. It should work for music but i haven't tested calling. Unfortunately, if you do this, then the speaker wont work.
Click to expand...
Click to collapse
Thanks kdub! I've been trying this with 3.5mm headphones, but can't seem to get it working. What's weird is, every time I go back to the startup.txt the snd.force_headset=2 line is gone, and I know I put it within the quotes.
It may have something to do with the advanced settings I put in when I boot XDAndroid. The startup.txt also seems to be different depending on those features, so maybe it rewrites it or something?
bndtdog said:
Thanks kdub! I've been trying this with 3.5mm headphones, but can't seem to get it working. What's weird is, every time I go back to the startup.txt the snd.force_headset=2 line is gone, and I know I put it within the quotes.
It may have something to do with the advanced settings I put in when I boot XDAndroid. The startup.txt also seems to be different depending on those features, so maybe it rewrites it or something?
Click to expand...
Click to collapse
If you use the startup utility, it will rebuild your startup.txt every single time. I think there's a checkbox somewheres in there to enable a manual startup.txt...
arrrghhh said:
If you use the startup utility, it will rebuild your startup.txt every single time. I think there's a checkbox somewheres in there to enable a manual startup.txt...
Click to expand...
Click to collapse
Ah, I suspected as much. Will report back if I get this thing working...
Success! Thanks everyone. By the way, by using this workaround and a cheap piece of hardware called a Bluetooth Adapter (Cardo BTA II), I was able to get Bluetooth on my Rhodium with XDAndroid running. Awesome!
Edited to clarify - the headset workaround DOES work both ways, so you get audio out and audio in.
bndtdog said:
Success! Thanks everyone. By the way, by using this workaround and a cheap piece of hardware called a Bluetooth Adapter (Cardo BTA II), I was able to get Bluetooth on my Rhodium with XDAndroid running. Awesome!
Click to expand...
Click to collapse
Ha, I guess those that really need BT now have a workaround... even if it does involve an additional piece of hardware, haha. Seem actual BT is just around the corner (no promises )
Sounds good but on my rhod100_de i'm not able to activate bluetooth. When i hit it in the settings it only grays out, says "Activating..." for some time and than goes back to previous view (white text and not checked). So there seems to be a little more work for me . I think in about a half year we have a real good android running on our Devices and can kick winmos ass
@Bieka
Nobody said that BT is working. He used an "Klinke Bluetooth Adapter". ^^
This has been bugging me since September and when I rooted and ran a custom froyo ROM I thought it would have been fixed. I am currently running Nebula ROM (1.0.7) and the voice dial/command still only works by holding the search button and it takes in audio through the phones mic even when my bluetooth is connected. I have tried with multiple headsets and still no cigar. My EVO 4g was able to voice dial/command via bluetooth once it updated to froyo. Has any body been able to get this working? Or is it just not included with the dk28 release and we are waiting for another one to get leaked? Thanks.
This is a common problem with dk28
This post is also a common problem for these forums. You are not developing anything. You are asking a question. This is what the q&a section was designed for
Android Creative Syndicate- From spontaneous ingenuity, comes creative brilliance
try vlingo, its a free app in the market, but it seemed to work before i lost my bluetooth
Azichek,
Try a DK17 ROM. It works there and was broken in DK28. As far as I know, noone knows why. You can use the DK28 modem with a DK17 ROM.
works for me on dk28, im running midnight 3.2
2sslow said:
works for me on dk28, im running midnight 3.2
Click to expand...
Click to collapse
You can press the button on your bluetooth and the voice dial app listens to your voice through your headset not the mic on the phone?
Rtalian said:
Azichek,
Try a DK17 ROM. It works there and was broken in DK28. As far as I know, noone knows why. You can use the DK28 modem with a DK17 ROM.
Click to expand...
Click to collapse
Ok, so i can keep my dk28 modem and flash a dk17 ROM such as ACS?
it works on the latest dk28 bonsai rom.
this happens to also be the fastest smoothest rom ive used since ACS on DI18. Its surprisingly good for not having the source yet. I dont know how they do it...
azichek said:
This has been bugging me since September and when I rooted and ran a custom froyo ROM I thought it would have been fixed. I am currently running Nebula ROM (1.0.7) and the voice dial/command still only works by holding the search button and it takes in audio through the phones mic even when my bluetooth is connected. I have tried with multiple headsets and still no cigar. My EVO 4g was able to voice dial/command via bluetooth once it updated to froyo. Has any body been able to get this working? Or is it just not included with the dk28 release and we are waiting for another one to get leaked? Thanks.
Click to expand...
Click to collapse
Top Voice Control works pretty well with voice confirmation but you still have to start it from the phone. I don't think there is an app that works on the Epic yet that starts with the bluetooth push button. Anyone?
Flashed midNight yesterday, the BT voice dial works perfectly. i guess it was just Nebula ROM that had the problem.
azichek said:
Flashed midNight yesterday, the BT voice dial works perfectly. i guess it was just Nebula ROM that had the problem.
Click to expand...
Click to collapse
So when you hit the bluetooth button a program opens and allows you to say a name to dial with confirmation? Or is it built in to Midnight and works like the Blackberrys? Just push the button and it says "say a command"?
That's good to hear about bonsai and midNIGHT having working BT voice dial. I was under the impression that the problem was with DK28 across the board. I wonder what they did to fix it or what was done to break it in the other ROMs. Maybe I will try one of those this weekend. I'm curious if audio from the Samsung docks works, too. Audio through the desk dock works with Quantum 1.5, but I think my car dock has a bad connection.
DK28, and I can press the action button on my plantronics discovery 925 all I want and nothing happens. However if i manually open up choice dialer, I can use voice dialing.
I don't know much about how it works, but shouldn't there be a way to reroute the REDIAL function (quick double press) with headsets to trigger an alternate action?
The phone obviously intercepts the double press and triggers the dialer to redial the last number called/dialed. I imagine it would be possible to either hack the dialer or create an app that bypasses it and directs it to another function...
Bothers me that somebody I know with a stock 2.1 DI18 Epic can use his Honda's bluetooth system to voice dial, and yet I have 2.2 and can't do anything. >.>
+1
rogerscorner said:
it works on the latest dk28 bonsai rom.
this happens to also be the fastest smoothest rom ive used since ACS on DI18. Its surprisingly good for not having the source yet. I dont know how they do it...
Click to expand...
Click to collapse
Sent from my Evo Killer!!!
Z a p i x said:
DK28, and I can press the action button on my plantronics discovery 925 all I want and nothing happens. However if i manually open up choice dialer, I can use voice dialing.
I don't know much about how it works, but shouldn't there be a way to reroute the REDIAL function (quick double press) with headsets to trigger an alternate action?
The phone obviously intercepts the double press and triggers the dialer to redial the last number called/dialed. I imagine it would be possible to either hack the dialer or create an app that bypasses it and directs it to another function...
Bothers me that somebody I know with a stock 2.1 DI18 Epic can use his Honda's bluetooth system to voice dial, and yet I have 2.2 and can't do anything. >.>
Click to expand...
Click to collapse
So none of the ROMs have this working yet? That bites. My crappy Blackberry workphone has this working perfectly and so did my old Palm Pre and Instinct. It definitely seems like somebody should have an app or mod for this.
kennyglass123 said:
So none of the ROMs have this working yet? That bites. My crappy Blackberry workphone has this working perfectly and so did my old Palm Pre and Instinct. It definitely seems like somebody should have an app or mod for this.
Click to expand...
Click to collapse
well, I only speak from the standard DK28, not the custom roms which appears some people have voice dialing working.
If nothing from Sprint by March, I may give Bonsai a shot. I am not holding my breath though for the rumored 21st for OTA from Sprint. More likely santa claus real!
2.1 or 2.2 no mods here. I've had nothing but issues trying to press jawbones command button to dial out. It's horrible that my previous Samsungs M7500 ? and the upgrade to that were more than capable. But not this phone. I do have some thoughts by Jaw that I need to read over. But this has been the one annoyance with my Epic.
Nolonolon said:
2.1 or 2.2 no mods here. I've had nothing but issues trying to press jawbones command button to dial out. It's horrible that my previous Samsungs M7500 ? and the upgrade to that were more than capable. But not this phone. I do have some thoughts by Jaw that I need to read over. But this has been the one annoyance with my Epic.
Click to expand...
Click to collapse
So no one has gotten it working where you push the bluetooth button to initiate the voice dialer? We can only hope that is one of the delays for the official release.
It does work from the headset button on Quantum 1.5, which is DK17. It sounded like others in this thread had it working with bonsai4all and midNIGHT, which are both DK28.
I'll let you know once I have midNight installed
I am having a problem where all vibration/haptic feedback will just randomly stop working completely. Then a few hours (and sometimes days) later it will randomly start working again. It will keep working again for a few hours or maybe days, and then randomly stop again. There seems to be no pattern to it.
I have no idea what is causing this. Has anyone else experienced this, or does anyone have any idea how to fix it?
This is extremely frustrating as I am someone who never uses the ringer; I just always have my phone on vibrate.
I'm running the latest stable release of CM 7.1 for the Evo 4G, but I had this happen before on stock Sense as well.
mredmond2012 said:
I am having a problem where all vibration/haptic feedback will just randomly stop working completely. Then a few hours (and sometimes days) later it will randomly start working again. It will keep working again for a few hours or maybe days, and then randomly stop again. There seems to be no pattern to it.
I have no idea what is causing this. Has anyone else experienced this, or does anyone have any idea how to fix it?
This is extremely frustrating as I am someone who never uses the ringer; I just always have my phone on vibrate.
I'm running the latest stable release of CM 7.1 for the Evo 4G, but I had this happen before on stock Sense as well.
Click to expand...
Click to collapse
I am having this same issue as well. It must be software related because the vibrate function works just fine when the phone rings. I am running CM 7.1 stable on an Evo 4G. I noticed the issue as well on CM 7.0.3.1 or whatever the latest stable build was on CM.
Does the phone ever always (or never) vibrate under a certain circumstance? i.e. incoming text, email, incoming/outgoing call, typing, etc.? Also, do you have any toggle widgets that could affect vibrate/ringer status?
I ask this because, and this may sound silly, it may be that you are modifying settings unknowingly. I've had that happen where I have my hands in my pockets and next thing I know I've accidentally got my Facebook up and running and typed half a book in the status field.
Again, I know that sounds silly but I ask because it's happened to me before.
Concordium said:
Does the phone ever always (or never) vibrate under a certain circumstance? i.e. incoming text, email, incoming/outgoing call, typing, etc.? Also, do you have any toggle widgets that could affect vibrate/ringer status?
I ask this because, and this may sound silly, it may be that you are modifying settings unknowingly.
Click to expand...
Click to collapse
That's fine, its an important clarification to make. But no, I am absolutely sure I have not changed any of the options unknowingly. As I said in the OP, ALL vibration/haptic feedback will cease to function entirely. I've often had it happen that in the middle of typing something, the haptic feedback for the keyboard will just go away. Immediately after this if I check the soft key buttons or test the vibration for notifications, none of these will produce any sort of vibration response either. Then randomly a few minutes, hours, or days later, all haptic feedback will just return. Its been an extremely strange and frustrating issue.
4nth0ny said:
It must be software related because the vibrate function works just fine when the phone rings. I am running CM 7.1 stable on an Evo 4G. I noticed the issue as well on CM 7.0.3.1 or whatever the latest stable build was on CM.
Click to expand...
Click to collapse
For me, when the vibration stops working, it stops working for everything, even when the phone rings. But that's what I can't figure out: if it is a software or hardware related issue. I was having this problem on stock Sense, and I figured if it was software related, perhaps flashing a new ROM (in my case, CM7), would fix it. However it hasn't, so I'm beginning to think if it is indeed a software issue, it must be a bug somewhere very deep within the code, otherwise it has to be a hardware issue. But if its a hardware issue, I can't figure out why it would randomly stop/start working like it does, and the thing is, most (75%) of the time, it is working. Its just the other 25% that annoys the hell out of me. That's why I thought I'd ask and see if anyone else had experienced it or found any solutions.
Its a CM7 thing I've noticed it on Xplod, Decks, and CM7 I don't really mind it cuz my ringers are loud as hell but yeah its pretty weird :shrugs:
Usually AOSP ROMs for some reason have that problem cuz on sense ROMs it never happens
infamousteeboy said:
Its a CM7 thing...Usually AOSP ROMs for some reason have that problem cuz on sense ROMs it never happens
Click to expand...
Click to collapse
Well like I said before, I was having this problem on my stock Sense ROM.....
infamousteeboy said:
Its a CM7 thing I've noticed it on Xplod, Decks, and CM7 I don't really mind it cuz my ringers are loud as hell but yeah its pretty weird :shrugs:
Usually AOSP ROMs for some reason have that problem cuz on sense ROMs it never happens
Click to expand...
Click to collapse
I've never had that problem on CM and I've been using many different versions of it for a long time. I don't know if I am lucky or what but people complain about a lot of issues that are claimed to be CM issues....yet I've never had a single one of them.
Concordium said:
I've never had that problem on CM and I've been using many different versions of it for a long time. I don't know if I am lucky or what but people complain about a lot of issues that are claimed to be CM issues....yet I've never had a single one of them.
Click to expand...
Click to collapse
Well I kinda had the same problem that he's run into on CM but I figured it out but I figured since he's had the problem on a sense ROM also then maybe its not the ROM but I jus went into everything that had the option to vibrate and turned them all on cuz I've flashed a couple ROMs and the vibration would be off I try not complain about anything about any ROM its a person hard work they've done for free I try to figure things out on my own as much as possible before I create a thread not bad talkin the OP but jus sayin you know?
I don't think that it's rom related. I've been having issues with my haptic feedback since I got the phone, even before rooting it. I think it's just a crappy vibrator. (If there's a better name than "vibrator", please someone tell me.)
I had vibration problems on my first Evo as well, it was never rooted. My second Evo was a HW004 and the haptic feedback was perfect - it was softer instead of the shock-like haptic feedback I've experienced with my 003s. My current and third Evo is also a 003, so I assumed it had something to do with the motor used in 003s.
I've just turned haptic feedback off. I thought I'd miss it, but I've gotten used to it. I still use have my phone set to vibrate for notifications and calls and I've seen fewer issues.
If you think you can go without, I'd suggest turning haptic feedback off. Otherwise, unroot and take it into Sprint. You may have more luck calling, because if you can't replicate the issue in front of them then they can't do much.
Sent from my Evo + MIUI using Tapatalk!
plainjane said:
I don't think that it's rom related. I've been having issues with my haptic feedback since I got the phone, even before rooting it...
...Otherwise, unroot and take it into Sprint. You may have more luck calling, because if you can't replicate the issue in front of them then they can't do much.
Click to expand...
Click to collapse
Yeah, its definitely not ROM related...I don't know if people aren't reading the posts, but I've said several times that this occasionally happened on stock Sense, both before and after rooting.
Dang. I didn't want to have to bring it in to get it fixed, but I guess that's what I'm gonna have to do if its a hardware problem...I was really hoping it was software related or if someone would know of a way to fix it so that I could avoid dealing with warranty services...I got suckered into the Best Buy warranty, and it turns out that even though they either give you a new or refurbished model, they make you turn yours in and wait 5-7 days for the replacement to come in instead of ordering the replacement and then doing a trade with you when it comes in. I already experienced it once before when my USB port broke... :/
Not being able to replicate the issue is my main concern since sometimes it works and sometimes it doesn't. Trying to get it to stop working at a time when I can actually run out to the store is gonna be a pain...And I really don't want to waste a trip to the Best Buy store only to have it start working again with me trying to tell the GeekSquad Agent, "I promise, I promise! It was broken just 5 minutes ago!!" I can't imagine how many of those they have to deal with....
So i installed 7.2.0RC1 on my desire and it worked perfectly for 2 days but i've noticed this morning that when im getting calls or messages the phone isn't making a noise and notifying me of this.
I checked that I wasnt accidently on silent and I wasnt, so checked volumes, all ok, and then I decided to look at the ringtones and select a different one and where each one is supposed to give you a little preview of the tone im getting nothing.
Im really at a loss, has anyone else had this problem or knows how to solve it, its handy being made aware when someones trying to contact me
I had this on the nightly prior to the RC1. Reboot and the ringtones should be back but you have to re-assign them I think.. and yeah it will probably happen again.
stankyou said:
I had this on the nightly prior to the RC1. Reboot and the ringtones should be back but you have to re-assign them I think.. and yeah it will probably happen again.
Click to expand...
Click to collapse
Tried rebooting and still nothing off previews or anything, its just kinda weird for a RC for this to happen, might have to go back down to 7.1.0 until the bugs are ironed out, thank god for nandroid.
Still might have a solution pop up here before i get round to doing that
Did you modify the rom? Change or remove ringtone files you don't need?
Even I had same problem various times. Rebooting solves the issue everytime.
I didn't modify the rom at all and rebooting doesnt solve it, come to think about it, its happening since i used a pair of headphones for the first time
Do you use any Bluetooth headset? Usually when I use mine it happens what you have described and the only quick fix was to make a reboot. I didn't tested it yet on CM7.2 RC1 but the issue was present in CM7.1 Stable.
I use Rings Extended, it`s perfect
Today I tested the CM7.2 RC1 ROM with my Bluetooth headset and so far it is working with no problems (no sound issues like you mentioned). Now I just have to see if it would also stay this way in the few days.
I also found that some users had the problem described in the first post when they were using usual cord headphones but so far I hadn't experienced any problems with them although I'm suing them almost every day since the CM7.2 RC1 ROM release day.