How do you end calls with the Tablet Dial pad???
I can not hang up when making a call, I see the DIALPAD tab on bottom, bring it up, no END CALL option, exit DIALPAD app, phone still ringing
Hit your "menu" button (the middle of the 3 capacitive buttons). It will bring up options such as End Call.
No END CALL when menu button is pushed, I have HOLD, MUTE, SPEAKER, and BLUETOOTH options only. I am running 240 density. Is it being cut off? What are the available options when MENU button is pressed? Thanks in Advance
yes 99% sure its being cut off with 240 density
if your lucky, maybe you can rotate the phone and see the whole menu that way, probably not though.
Will going to the STOCKPHONE option solve my problem?
Someone on another forum posted a JPG of the menu options, and I only get the bottom 4 options, it is weird because I get the #5-dialpad above the HOLD, MUTE, SPEAKER, BLUETOOTH, but missing the menu options between.
Yeah, it gets cut off at 200 and above. I tried it with 200 and you can barely see the end call button. I'm sure on 240 it is just gone completely.
stockphone solves this problem, yes. if you want to keep the 240 density, you might have to go back to that.
Added stockphone to install.txt, problem solved.
My eyes like 240 and the stockphone seems a little more user friendly. Thanks to all for the help and interest, 1.70 solved my problem with the menu settings being all black at 240. I don't think I will move from 1.70 unless there are any other problems encountered. Life is Good with all my apps working smoothly.
txaggie85 said:
Added stockphone to install.txt, problem solved.
My eyes like 240 and the stockphone seems a little more user friendly. Thanks to all for the help and interest, 1.70 solved my problem with the menu settings being all black at 240. I don't think I will move from 1.70 unless there are any other problems encountered. Life is Good with all my apps working smoothly.
Click to expand...
Click to collapse
Ditto. I'm on 200, not 240, but I love that the menu works properly (not all blacked out) and that all my apps and widgets work great. No issues.
Although ... I might have to try Honeycomb if Steve gets it working properly.
Related
i saw a post about ringer delay for AT&T user and they just need to disable the dialer and the problem solve but what about us sprint users? Here is the original post about that http://forum.xda-developers.com/showthread.php?t=449417
i tried to disable the dialer on registry but still get 2-3 second delay before my Touch Pro actually ring.
Download and install DiamondTweaks. There is an option to disable the ringer delay. Works well.
convert your ringer to .wav file
temperamentalman said:
Download and install DiamondTweaks. There is an option to disable the ringer delay. Works well.
Click to expand...
Click to collapse
The ringer delay that this changes is the pause between when the ringtone ends and it repeats. Not the delay from when the LED starts flashing (because a call arrived) till the phone actually starts ringing.
If you wish to turn off the HTC dialer and use the WM Dialer, simply goto the following registry entry,
[HKEY_LOCAL_MACHINE/Security/Phone/Skin]
"Enabled" = dword:1​change the Enabled value from 1 to 0 which will disable the HTC dialer.
I vote for converting to WAV files as well.
If you would like to complain to Sprint about it, the following is the thread I started on Sprint's forum regarding this very subject.
http://forums.buzzaboutwireless.com/baw/board/message?board.id=SmartPhones&thread.id=5304
Thanks smotrs...
Know anyway to get the light sensor to turn off the screen when on a call (Sprint) other than S2U2?
temperamentalman said:
Thanks smotrs...
Know anyway to get the light sensor to turn off the screen when on a call (Sprint) other than S2U2?
Click to expand...
Click to collapse
Depends on what you may have done (adding programs, etc..) to your phone. By default, our devices will turn the screen off to conserve battery while a call is in session. However, if you have added one of the S2A dialer GSM versions which was taken from the Touch HD, that feature was disabled because of the InCall curtain. The CDMA versions (my signature and others) were taken from the Sprint Diamond ROM that was released and still contains the necessary code to turn off the screen display while the call is in progress.
Smotrs...just HR'd and installing now. I haven't tried that one, and actually think I ended up with the GSM version I WAS using.
I'll let you know how it works.
Thanks...
Well, it still sits there while the screen "times" out. I thought the light sensor was supposed to dim the screen almost immediately. I'm on the call for 30-40 seconds before it dims, and then cuts off.
Is this a Sprint thing?
temperamentalman said:
Well, it still sits there while the screen "times" out. I thought the light sensor was supposed to dim the screen almost immediately. I'm on the call for 30-40 seconds before it dims, and then cuts off.
Is this a Sprint thing?
Click to expand...
Click to collapse
It should Dim after about 10 seconds (or whatever you have in the backlight Advanced setting under Battery). After about 40 seconds or so (same location) it should turn off the screen.
At least that's what mine does, just verified it again. Sounds like maybe your values are too high. After a HR they usually are by default.
Somehow it was at 30 (dim) and 1 min (off). That is a little high. Changed it to 10 / 40. We'll see what that does.
Thanks for the tip. I'll keep you posted.
Seems to now be working the way you explained!!! Thank you for the help!
Is there anything else out there, other than S2U2 that allow FULL SCREEN Caller ID pictures??? I don't want to reinstall that because the dialer is actually working right. I just miss full screen caller ID.
Thanks again.
That I don't know, sorry.
Eh...it's ok. I'd much rather have a dialer that works than a full screen picture of my ignorant brother.
you can also change the Slot Cycle Index in the epst settings... you'll need your MSL though
it's under "Modem Settings"
What is slot cycle and where are these settings? How do I find my MSL? I don't see "Modem Settings".
not trying to be an ass, but i suggest you do some searching. there is plenty of info on the subject
check out this thread - http://forum.ppcgeeks.com/showthread.php?t=48775&highlight=epst+poll
or here - http://forum.ppcgeeks.com/showpost.php?p=625185&postcount=14
and here - http://forum.ppcgeeks.com/showthread.php?t=42730&highlight=epst+poll
I don't think you are an ass...I'm thinking thanks for the threads!
I know search is my friend LOL
lol, no prob man...
Changed the SCI to 1. We'll see if that helps. There is always "0"!
I'm also seeing mixed reports/opinions on ACCOLC - Access Overload Class. Mine was defaulted at 8 on Sprint. People say leave it alone. People say set it lower. Others say set it higher.
i found that setting SCI to 1 is good enough, i'm able to catch my calls and haven't noticed decreased battery life from it so that's where mine stays.
Hello. I recently found an app, that can change your LCD density on the fly. The only problem that I have found, quite large actually, is that the dialer and phone are not working. I cannot place any calls whatsoever.
Now I really want this to work properly, because Ace looks just amazing at a density of 145. So I'm wondering, is there any fix available?
Edit: I have added a few screens, so that you can see the difference.
i dont quite understand
can you upload screenshort?
thanks
Changing the density may cause some market apps too to not work. Mostly your dialer will look screwed/don't work. Can you post a screenshot (back button + home button) for the 145? How does it look?
It looks like this: black screen when launching phone/dialer app or when someone is calling and then Force Close.
Oh, and the problems I mentioned.
Dialer force close
Changing the LCD density below 160 will cause your dialer tab to FC or to the extent that it wont show up. So i never recommend.
Change the dailer
Yea i had the same prob but it looks so much better that i wanted to continue with it solution use another dailer (many available on the markey ) hope that helps
I have changed the dialer, but the phone service is not working. When I try to call someone it just gives me a FC of the phone app.
what other dialer you've use?
Dialer 1, GO Dialer... It doesn't matter, the phone service still won't work and I can't receive or make calls.
Yea my bad
Did test it fully so didnt see the prob till later...sorry abt that
Managed to get to the dailer the the phone app crashes as said above
Have been looking around but no solution as yet
Both the on-screen keyboard and the menu keep annoyingly popping up on my Viewpad7. It is driving me crazy.
At some point I thought it had to do with how I moved the device around, but I still think it's a random thing. It was/is a problem before and after loading it with a custom rom.
Is this a known hardware (or software?) bug ? If so, is there a cure for this? I have looked for settings, but was unable to find them. Thank.
SWVer=3.16K
MODEL=FM6-0001
HWVer:103
Android 2.2.2
Hi
Have the same problem and some other users here too.
Seems the Touchscreen/Softkeys are faulty and have to be replaced.
I bought mine 1 week ago and day by day it went worser. I didn't upload a custom rom so far, so it's a stock problem.
Now every 2nd time I take the device it vibrates and menu/keyboard keeps popping up/down. Looks like, the "menu" softkey does his own business, right?
Also the G-Sensor/Compass seems to be defective for me - after a few hours I have to calibrate always.
I made some videos, look at this thread:
http://forum.xda-developers.com/showthread.php?t=1258052
Where have you bought yours?
Regards
With my device it was when I held it in landscape mode and touched the bottom part of the right side or the rightmost part of the bottom of the device itself. It was also HWVer 103. You will most likely have to get the screen and soft keys replaced like I did.
Sent from my ViewPad7 using XDA App
Or, it could be just be a "normal" thing with Froyo OS itself, I've noticed it on 2 newer build - both ITE enabled - in U.S. market.
SWVer=3.41
MODEL=FM6-0001
HWVer:107
Android 2.2.2
This happened only on certain Apps - even when Auto Rotation under Settings are turned off, it will switch to the "opposing" mode and won't go back once it make that orientation change, i.e. YouTube whereas Angry Birds will stay landscape all the time. Device has been calibrated & sensors working, as I had no issues with GPS status & Maps, etc.
Should be a simple fix or patch on the OS or custom ROM .... BTW, I'm running the stock, rooted 2.2.2 ROM while waiting for an OC one with the ITE kernel working to boost the Quadrant scores, LOL.
Ours seems to be more a hardware problem since it happens anywhere, with autorotation on or off, after a complete hard reset (without any additional apps installed) and simply by touching the case itself (not the screen)...
astuermer said:
Ours seems to be more a hardware problem since it happens anywhere, with autorotation on or off, after a complete hard reset (without any additional apps installed) and simply by touching the case itself (not the screen)...
Click to expand...
Click to collapse
Hmmm, interesting after I checked out a few YouTube videos & it sounded like it's all HWVer 103 yet running Froyo 2.2.2. Is the device ITE enabled as I noticed that the pop-up keyboard is "standard" whereas mine has Swype style keybaord with ITE.
It's a pain to get it returned, exchanged & repaired at the authorized factory service center and be without the use for 2+ weeks, unless one's within a 30 days period & can send it back to the place of purchase for a new one (could take just as long)
Another post mentioned a new stock ROM just being released, it might be worth an effort or try to flash it (FM6-3350-0-1008-A01.nb0) upon downloading & using the SUTL3 app to do it - would need to root it again - if one is brave enough (since it's going back for repair/exchange anyway?)
BUT, I'm guessing whether this newly released stock ROM is for ITE devices vs. non-ITE ones with HWVer 103, 106 and 107's ???
The button clicking by itself or when under vibration is an HW fault.
pulling the back off and wedging some paper near the touch IC to keep pressure on it has fixed mine.
Brought it back to the store for repair. I think they put a new screen and cover (back) on it. Works like a charm.
flez1966 said:
The button clicking by itself or when under vibration is an HW fault.
pulling the back off and wedging some paper near the touch IC to keep pressure on it has fixed mine.
Click to expand...
Click to collapse
Can you describe more precisely how and what did you do or can you (better) do some photos?
Did you pulled off a back cover and inserted a piece of paper somewhere?
Need to experiment
Software solution
This is a solution from a user 'retrochip' from 4pda.ru forum
(Link to original post in Russian and i'm not able to post is here)
1. Root your device (can be done with Gingerbreak)
2. Find out codes for Menu button and Search button (229 and 217)
3. Edit configuration file /system/usr/keylayout/qwerty.kl (you can use RootExplorer)
In qwerty.kl:
Find text:
key 217 SEARCH WAKE_DROPPED
and change to:
key 217 MENU WAKE_DROPPED
Find text:
key 229 MENU WAKE_DROPPED
and change to (just comment it with #):
#key 229 MENU WAKE_DROPPED
Save and reboot.
Now Menu button isn't active and Search button works as a Menu button.
No annoying random popping keyboard anymore.
This has killed my all soft buttons, now the only option is to fix it in adb, because screen keyboard doesn't appear in terminal, I need to touch menu then screen keyboard.
hello,
newbee here. I have acquire a sansung galaxy S2, and have a lot of fun with it.
trouble started when it rebooted at night. I figured out that some update or application crashes were the cause of it.
I think i rid of most of the issues, and got it pretty stable.
To avoid future complication, I even rid of the startup sound, but I can not rid off the vibration (especially the one when shutting down....)
I think it is part of the basic settings, and I did a lot of researches... no luck
Apps like Silent boot would not work either....
Do anyone know if it's even possible ?
If impossible, is ICS having the same issue, or can this be tuned ?
(i just can't believe no one thought of making that optional ...)
Please help me...
I'm on ICS and don't have that. It is part of system settings - sound. It usually is affected by the mode you have your phone set to (like if you have sound set to Sound and Vibrate or just Vibrate, etc). Try changing to just sound and see if that stops it from vibrating (or just silent mode with no vibrate).
Can also try to untick Vibrate on screen tap.
ICS is sweet... can't go back to GB... what you waiting for?!
Sorry, but this does not work (phone is rooted)
. tried vibration off no luck
. tried silent mode no luck
Is there someone who knows where is configured the vibration settings ?
I mean in which filesystem (full path if possible) ... ?
note: Official Samsung ICS for Unlocked Phones will come soon... unless there is a safe ROM and method to install it. For now I would concentrate on my Vibration issue.
Firstly, be patient. People will try to help you, doesn't mean the first answer fixes your problem.
As I stated... ICS does not have this problem. Phone makes no sound and no vibrate, if you set it that way on ICS.
How about give us more information. You said you're rooted but on GB. Are you using any different type of kernel other than stock? Like Siyah 2.xx?
As the filesystem where you can doodle with removing vibrations... I will leave someone with more experience to deal with that (even if I know the path)... in case I advise you something that can screw things up after.
*you might want to reset the phone - as the system notification/vibration settings should have done the trick.
hello
I upgraded to 4 versions of ICS.
Each one of them did not correct the issue : it still vibrate when shutting down the phone. (darkyrom, OCA, Pure and a "4.0.4" version having a clever 3 way option to launch (Nova, TW and Apex)).
I did not reset the settings yet but I will give it a go.
I will the thread updated.
That's a very strange bug then. The settings to control that though, is not with the launchers but with System Settings.
Maybe try this:
System Settings - Volume <inside there you have 4 settings. Try changing System to very low or all the way off. Then go to the whatever mode you have it set to (like Silent Mode or whatever)... and select Mute.
Then the lower categories of System... uncheck all of them: Keytones, Touch sounds, Screen lock sound, Vibrate on screen tap.
See if that works. If it does, then can narrow it down to one of those settings.
Thank you very much
The simplest things are not always obvious to the common....
It works, the vibration disappeared when /SOUNDS/VIBRATION SETTINGS/Vibrate on touch was set to the lowest. Meantime, the little vibration at startup disappeared as well. Now the phone can crash, update and reboot at night without waking me up ! .. a good logcat reader (just in case) running in background will help cleaning up when some error occurs....
Once again, thank you: that drove me mad.
Glad that worked. You're right, sometimes the simplest things are not always obvious, for everyone ;-)
LeFrog1310 said:
Thank you very much
The simplest things are not always obvious to the common....
It works, the vibration disappeared when /SOUNDS/VIBRATION SETTINGS/Vibrate on touch was set to the lowest. Meantime, the little vibration at startup disappeared as well. Now the phone can crash, update and reboot at night without waking me up ! .. a good logcat reader (just in case) running in background will help cleaning up when some error occurs....
Once again, thank you: that drove me mad.
Click to expand...
Click to collapse
I have chinese copy of Nexus One phone, android 2.2.1 and I don`t have VIBRATION SETTINGS tab in my menu, I can only turn vibrate on and off,
and I don`t have SOUNDS on SETINGS, I enter in AUDIO PROFILES to menage vibration,
how to turn off vibration on power on and off?
I have a minor niggle but wonder if it's due to something I'm doing wrong. I have full backup's of my TA partition and flash custom and stock rom's as and when I choose. I just have an annoying issue when i turn my screen back on it shows garbage pixels on the screen and slowly draws the screen til the bottom and then flashes to a properly drawn screen. Can I remove it or learn to live with it?
srdempster said:
I have a minor niggle but wonder if it's due to something I'm doing wrong. I have full backup's of my TA partition and flash custom and stock rom's as and when I choose. I just have an annoying issue when i turn my screen back on it shows garbage pixels on the screen and slowly draws the screen til the bottom and then flashes to a properly drawn screen. Can I remove it or learn to live with it?
Click to expand...
Click to collapse
My test device - that I picked up very cheep as it had been dropped and the SIM reader no longer works - displays the same issue, I had always assumed it was because of the fall it had.
Sorry if that doesn't help you
like this?
http://youtu.be/oyv5QmD5uQA
Exactly the same issue thanks
Same here but my phone is allways in case and i never dropped it. Oh and factory reset or flashing another ROM is not solution.
Any ideas?
I can only guess that either the RAM fills up with the screen off and once it starts to clear when the power button is pressed it suddenly can draw faster, or it's because the CPU and GPU clock down and slowly ramp up on wake. I'll change my performance settings see if that changes things?!
I've changed the settings in performance. So goto settings, performance, profile and select performance instead of balanced or power save. This seems to have sorted the re-draw issue on the lockscreen, any change I'll let you know. Now I just need to get a basic knowledge coding/cooking rom's and start delving further into android!!
srdempster said:
I've changed the settings in performance. So goto settings, performance, profile and select performance instead of balanced or power save. This seems to have sorted the re-draw issue on the lockscreen, any change I'll let you know. Now I just need to get a basic knowledge coding/cooking rom's and start delving further into android!!
Click to expand...
Click to collapse
So it's actually software problem right? Not damaged screen or something inside the phone.
Jecmenn said:
So it's actually software problem right? Not damaged screen or something inside the phone.
Click to expand...
Click to collapse
seems that way i now get it one in ten times I press the power button otherwise it just instantly appears with no redraw, just seems like lag
srdempster said:
seems that way i now get it one in ten times I press the power button otherwise it just instantly appears with no redraw, just seems like lag
Click to expand...
Click to collapse
mine is a hardware issue. you will see that it is currently on cm12 but it has done that on Stock, 4.4.x custom and 5.0 CM/AOSP as well. It will only do this if it hasn't be used for a few hours.