Titan 6800 Green Phone Button Stopped - Mogul, XV6800 ROM Development

is there a Registry key(s) to view to check or make this button access the Phone or the functions of Dial? It stopped working on my last upgrade to 6.5, and I thought it was a problems with the new OS. I have now reverted back to 6.1 and it still doesn't work. I can't answer the phone with this hard button and I cannot bring up the dialer either. I have made the green phone button another button using HButton, and I made the green button access the Calculator using AEButton Plus. The calculator does not come up when the button is pushed, but I can make the phone come up, but not dial. This may be related to a problem when I do Phone Code Data ##3282#. The phone goes to EPST then quickly goes to the dialer so I can't do any troubleshooting. I posted this to ppcGeeks too. Help Please

Wrong Department Buddy! Moved.

jminor4326 said:
is there a Registry key(s) to view to check or make this button access the Phone or the functions of Dial? It stopped working on my last upgrade to 6.5, and I thought it was a problems with the new OS. I have now reverted back to 6.1 and it still doesn't work. I can't answer the phone with this hard button and I cannot bring up the dialer either. I have made the green phone button another button using HButton, and I made the green button access the Calculator using AEButton Plus. The calculator does not come up when the button is pushed, but I can make the phone come up, but not dial. This may be related to a problem when I do Phone Code Data ##3282#. The phone goes to EPST then quickly goes to the dialer so I can't do any troubleshooting. I posted this to ppcGeeks too. Help Please
Click to expand...
Click to collapse
My friends phone did this, all on it's own, nothing had been installed or flashed for at least 6 months prior, the button does just wear out. He called DTS support at USCC and they replaced it for free, depends on your carrier and whether it's still under warranty or not.
BTC

brought my mogul into sprint today with a bad talk button and they ordered a "new" one, prob refurbed mogul and should be here tuesday yay....
tuesday, got my refurbed mogul. condition is good so far except the keyboard double types even with my backup from my other mogul, front buttons are stiff and need to press hard to get them to function but the talk key works fine lol. Lady who activated me said "why didnt they just upgrade you to a touch pro like they usually do" DOH!!!!

Related

Vibrate Doesn't Work (using dcd 2.2.3), Verizon

So, a few days ago I flashed to the 2.2.1 (and radio 3.27) release (thanks so much for all your work dcd!). I didn't really notice until today that the vibrate function isn't working. I hopped on here and searched around and came up with nada... other than 2.2.3 was released. Flashed up to that, same thing. Everything seems to work fine other than vibrate.
Anyone have any ideas?
Are you sure the vibration motor is functioning? For instance when you power it on does it vibrate for a split second?
it doesn't, that's actually how I noticed that it wasn't working.
Did you do any registry hacks or use any apps to disable the flashing LED? The vibrate function is tied to the LED flashing and disabling it in certain ways will kill the vibrate functionality with it.
negative... I have a clean install of 2.2.3 with no hacks or modifications applied to it. in my searching yesterday, I came across references to HKLM\SOFTWARE\OEM\VIB and \HKLM\Drivers\BuiltIn\AllLEDMgr but neither of these had any impact.
I had this same issue and the only workaround that I came across was to hit ok when closing the email program instead of closing it by tapping on the X. One other workaround is if you use programs like SPB Pocket Plus, add the tmail.exe to your close exceptions and vibrate will work as normal.
Hope this helps
No problems here with Vibrate
Only programs I have loaded other than the 2.2.3 rom are SPB Phone Suite and PointUI 1.02B.
I am really hoping this is something that can be fixed, I really don't want to have to flash back to stock and get a new one under warranty.
If you soft-reset your phone, does it do that quick vibrate? If so, hardware is intact
bimmerd00d said:
If you soft-reset your phone, does it do that quick vibrate? If so, hardware is intact
Click to expand...
Click to collapse
(see above) nope, no quick buzz
N715DP said:
(see above) nope, no quick buzz
Click to expand...
Click to collapse
aye, my fault. It's still early and I haven't started reading yet. That sucks about your vib, Has to be a hardware fault. i thought i had my first contribution to XDA with this one, thanks for shooting it down.
sorry about that, I am sure you'll get one soon

Unable to answer the phone most of the time.

I'm on a 5060 build using the Kitchen. I have HTC Home, S2U2, and anything else that was defaulted in the settings from the basekit.
I had the same problem on DCD 3.0.1 and nue 5054 and 5059. I was told it was advanced config, so I reflashed 5059 without AC, then 5060 without it. The device worked great yesterday, but this morning I couldn't answer the phone again.
I had found something that added a change soft key setting to the systems tab, I installed that and changed the setting to messaging instead of calendar, and that's when the issue returned, so I figured it was something to do with the that. I did a hard reset but the issue still remains. My next resort is a re-flash, but I really don't want to go through all that if I can avoid it.
clamknuckle said:
I'm on a 5060 build using the Kitchen. I have HTC Home, S2U2, and anything else that was defaulted in the settings from the basekit.
I had the same problem on DCD 3.0.1 and nue 5054 and 5059. I was told it was advanced config, so I reflashed 5059 without AC, then 5060 without it. The device worked great yesterday, but this morning I couldn't answer the phone again.
I had found something that added a change soft key setting to the systems tab, I installed that and changed the setting to messaging instead of calendar, and that's when the issue returned, so I figured it was something to do with the that. I did a hard reset but the issue still remains. My next resort is a re-flash, but I really don't want to go through all that if I can avoid it.
Click to expand...
Click to collapse
What do you mean you cannot answer your phone?
The calls don't go through, you cannot use the send key, what's up?
I press the answer softkey or the hardware key, and it doesn't work most of the time. It will mute the ringer, but will not answer the call.
This has been discussed elsewhere in this forum and on brand X. I also had a problem with the phone not answering. If you believe what they say....and I've tried it and it seems to be working for me now......reload a ROM without Advanced Config. This seems to be the common thread to the problem....Now my calls answer almost immediately. Try it...see if it solves the problem
I did that. My 5060 build didn't have AC in it at all.
Do you have SPB Pocket Plus installed? I had the same problems, but it hasn't returned since I uninstalled PocketPlus...
Nope. No SPB. Only default 5060 basekit and HTC home/S2U2.
I've actually gone ahead and re-flashed back to Sprint 3.35, which sucks because I really really liked the 6.1 threaded SMS, but a phone that I can't answer doesn't really do me any good.
I'll just have to wait for an official 6.1 I guess.
clamknuckle said:
Nope. No SPB. Only default 5060 basekit and HTC home/S2U2.
I've actually gone ahead and re-flashed back to Sprint 3.35, which sucks because I really really liked the 6.1 threaded SMS, but a phone that I can't answer doesn't really do me any good.
I'll just have to wait for an official 6.1 I guess.
Click to expand...
Click to collapse
the new PocketCM comes with threaded text..
A little update.
The GPRS_bye_if_device_off registry hack is what was causing me not to be able to answer my phone. It was supposed to improve battery life.
I had ran no2chem 5060 for a few weeks without it happening, then went to DCD 3.0.4 and it didn't happen until last night, I tried that hack. Sure enough, after the reboot, that hack is what did it. I was doing this hack just to test that theory so had a back up. I restored it and now the phone works properly again.

[Question] home and call button confused

Good day,
I have updated a view Tmobile versions of the HTC Pro to a official Asia WWE rom (1.90.871.3)
I have this weird thing with only one of the pro's.
which is that the button call and home gets confused sometimes.
one moment the whey are correct.
other moment they are swiched around.
i know that the original pro has the buttons the other way around compared to the tmobiles version.
but i assume that this should not be a problem for the rom right?
but buttons are probably physically turned around.
so button 1 is still button 1 for the phone.
is there anyone who has/had this or knows what this could be?
I have this problem to. I have an original Touch Pro and sometimes when I push the home button it calls the last person I called. It is very annoying.

phone mode screen inactive during a call.

i just notticed today that wheni call my voicemail none of the phone onscreen buttons work
keypad,end call, speaker etc are all non functional. i have to press the hardware key to end call.
im using CHT EDITOR with stock TMO rom
could be 2 things related to MinimumTapTime for screen sensitivity:
1. Do you have BSBtweak installed? DO NOT change the MinTapTime setting. Revert it.
2. Did you do tweak#44 MinTapTime from SBOY2000's HD2 tweaks thread? change that value back to what it was.
didnt tweak anything ust used bsb tweaks and changed it back to normal
still same.
at the moment i cant even get to the phone screen
the phone is completely fn cracked out.
im seriously on losing my patience with this sht, 3 phones cant be all having same issues thats just impossible unless the OS is ****.
yesterday i installed the WCX ILLUMINATI SERIES HD2 EURO/TMOUS 21911 2017
rom and it worked fine
call screen worked and keypad as well
i installed the BSB tweaks and cookie tab home
and getting same thing now the whole call screen is inactive
cant even push the hardware end button to end the call
and an error popped out:
a problem has occured with cprog.exe
the phone is very buggy in general with the cookie tab and bsbtweaks
ok so i just tested with both of them setup separately and both of them make my phone screen go stupid.
with bsb tweaks it doesnt turn on at all
with cookie tab it calls but then none of the buttons work on it not even hardware end call...
god damn i hate this phone, less than a week i own it and im about to throw it at the wall.
is anything supposed to work with microsoft at all?
wtf is active about active sync? it takes 50 tries to get one connection
sorry for the language but this is relaly fn frustrating.
fuzzysig said:
didnt tweak anything ust used bsb tweaks and changed it back to normal still same... 3 phones cant be all having same issues
Click to expand...
Click to collapse
fuzzysig said:
i installed the BSB tweaks and cookie tab home ...
and getting same thing now the whole call screen is inactive ...
Click to expand...
Click to collapse
fuzzysig said:
...with bsb tweaks it doesnt turn on at all...
Click to expand...
Click to collapse
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
You returned the phone twice because you keep installing an incompatible program and getting an error????????? Then why do you keep installing that program??????????? You're giving WindowsMobile users a bad name.
*HINT 1:Check what date BSBTWEAK was made. IT IS NOT MADE FOR THE TMO USA HD2! If somehow you feel you must use it, DO NOT FIDDLE WITH THE "TAP TIME" SETTING WITHIN BSBTWEAK.
*HINT 2: DISABLE COokie's Home Tab Lockscreen, it causes more trouble than it's worth.
Quote from the BSBtreak thread:
heybhouse said:
Edwin320 said:
Hello all! ...
I installed BsB onto my phone and it worked fine. I installed it on my wife's phone, and altering the Tap Time resulted in her screen not responding to the icons (speaker phone, hold, etc) while in a call. My phone did not have that problem. I did a hard reset and reinstalled everything except BsB and her phone is now fine ...
Click to expand...
Click to collapse
"in case this helps anyone: one of the tweaks would free my phone when in a call (not the whole phone, just the phone screen) so i couldn't bring up a the keypad or go to speakerphone, etc. I figured out it was the "tap time" tweak. i'm using the usa t-mobile hd2." (pg. 117) haven't seen the menu issue but if you have it backed up might as well save time and do the hard reset. i wonder if chainfire might be the issue there.
Click to expand...
Click to collapse
why doesnt it say anything about beeing incompatible in BSBtweaks post by the author himself?
aaaaaaaaaaaaaaaaaaaaaa back at you...
dude please dont help me anymore you really suck at it
THIS>>>>>>>"DO NOT CHANGE THAT BSBTWEAK SETTING!!!!!!!!"
DOES NOT HAVE SAME MEANING AS
THIS>>> DO NOT INSTALL BSBTWEAK!!!!!!!!!!!!!!!!!!
thats if you didnt understand
Had the same problem, in BsBTweak turn off "Phone Slide Cover".
stlfx said:
Had the same problem, in BsBTweak turn off "Phone Slide Cover".
Click to expand...
Click to collapse
I hope this helps someone else.
The OP doesn't take suggestions well. He just comes on here to vent about how he can't make his phone work.

"Tap to speak" box won't close or go away

Hi guys,
I hope that this is the proper forum, if not please direct me to the correct one.
I am currently using a Sprint Samsung Galaxy S6, non-rooted.
My problem started about 48 hours ago while I was voice dictating a test message.
I was doing my regular texting with the SwiftKey keyboard microphone (problem also replicates with the Samsung Keyboard as well) and the box at the bottom of the screen would not go away. I tried to X it out, hit the back button and the home button but nothing gets rid of it other than restarting the phone.
This all seemed to start happening after the Google App update.
I rolled back to the old version and it seemed to work fine. Last night, it updated itself again and problem was back.
I have included an image of what I am talking about.
If anyone has any suggestions, I would be very appreciative!
Thanks
Mikeinstlouis
I have to same issue that just happened and same as the screenshot.
Same issue...
This is so freaking ridiculous! A Google update that does this crap?!
I too own a S6 Edge Verizon 128GB and I noticed a couple of things.
If you bring up text to speak and then power off your phone.. Once you come back... you have locked it (Until restart)
I tried the following...
1) Reset the Dalvik Cache .. No luck.
2) tried force closing TTS and samsung text to speech.. no go.
3) Uninstalling latest update to the high quality voice. .. No Go.
4) Tried holding both buttons at the Same Time... No go..
5) For quibs and giggles.. Held down the close "X" for 5 whole minutes.
********************************************
What I think is going on is a time out error in the code.
So how i am able to get around it RARELY is..
Bring it up with the microphone button
Say what I need to say then hit the X to close it as FAST AS I CAN!!
I know that with all of our phone hackers, crackers and experts that we can ALL reach a Fix on this.
Damn Google...
mikeinstlouis said:
Hi guys,
I hope that this is the proper forum, if not please direct me to the correct one.
I am currently using a Sprint Samsung Galaxy S6, non-rooted.
My problem started about 48 hours ago while I was voice dictating a test message.
I was doing my regular texting with the SwiftKey keyboard microphone (problem also replicates with the Samsung Keyboard as well) and the box at the bottom of the screen would not go away. I tried to X it out, hit the back button and the home button but nothing gets rid of it other than restarting the phone.
This all seemed to start happening after the Google App update.
I rolled back to the old version and it seemed to work fine. Last night, it updated itself again and problem was back.
I have included an image of what I am talking about.
If anyone has any suggestions, I would be very appreciative!
Thanks
Mikeinstlouis
Click to expand...
Click to collapse
Latest update have little bugs
Sent from my Nexus 5 using Tapatalk
I am also having this issue on my Galaxy S4.
---------- Post added at 02:56 PM ---------- Previous post was at 02:46 PM ----------
mrneoz81 said:
This is so freaking ridiculous! A Google update that does this crap?!
I too own a S6 Edge Verizon 128GB and I noticed a couple of things.
If you bring up text to speak and then power off your phone.. Once you come back... you have locked it (Until restart)
I tried the following...
1) Reset the Dalvik Cache .. No luck.
2) tried force closing TTS and samsung text to speech.. no go.
3) Uninstalling latest update to the high quality voice. .. No Go.
4) Tried holding both buttons at the Same Time... No go..
5) For quibs and giggles.. Held down the close "X" for 5 whole minutes.
********************************************
What I think is going on is a time out error in the code.
So how i am able to get around it RARELY is..
Bring it up with the microphone button
Say what I need to say then hit the X to close it as FAST AS I CAN!!
I know that with all of our phone hackers, crackers and experts that we can ALL reach a Fix on this.
Damn Google...
Click to expand...
Click to collapse
One way I found that I can close it is by opening the menu that has active apps, then going to RAM, next turn the phone on its side (<--- yes do that), then hit clear memory a few times. And done its gone.
Thanks! That worked on my Sprint S4! (restarting phone has also worked for me, but this is easier.)
After holding down Home button to open the menu that has active apps, the options were still covered by the text to speak box. So I had to FIRST turn phone on its side to make visible the pie chart icon on bottom left, THEN then going to RAM tab and hiting clear memory a few times. When I turned it back to portait orientation, the text to speak box was gone. Thanks!
This has been happening to me all day long. so frustrating. I am also not the tech savy one in the house and hubby is not around. So thanks for the quick answer to get rid of it until he can uninstall the new update. Thanks
What is the pie chart menu option? What is the RAM tab? And will just be a little easier for Google to fix this? Lol
same problem here
Galaxy S6, same problem, started last night (September 24, 2015) . I do know that some updates were performed last night, not sure what. How do I uninstall the update? Which one is it? Help! I use voice typing constantly, and my phone is a brick when this thing locks up. It covers all my buttons. "Restart" doesn't clear it, I have to totally power off and back on. Right now, I have disable my voice key on my keyboard so that I don't accidentally touch it while waiting for solution.
Me too - just started today after some updates yesterday.
Same here....has anyone responded with a fix yet??
THANKS!
Glad it's not just me and my Note 3, but where does google get off sending out this kind of crap? It's enough to drive me to a windows phone.
Having the same issue only way I can get ride of it is to turn off my phone
same issue on moto droid mini; have to turn off phone too! poor QA google!!!!!
Me too. Galaxy S4. Have to shut the phone down and restart it to resolve the issue.
Piece of crap
Note 4 same problem started on the 24th
Same issue, Note 4
Same issue, Samsung Note 4.
Yep me too Verizon Galaxy s6
Sent from my SM-G920V using Tapatalk

Categories

Resources