Mysterious in-call menu - X Play Q&A, Help & Troubleshooting

Hi,
recently when I took my phone away from my ear to bring up the keypad during a call I was surprised to see some white menu overlay. I pressed the back button to get rid of it in order to be able to press the keypad button because I was in a hurry which is why i can't really remember what its options were. There were two or three and I think one them said something like 'Record call' but I could be wrong there. I have absolutely no idea where it came from and what might have triggered it. Has anyone seen this, too? Could it be some kind of bug and/or some function I accidentally discovered that's not really supposed to be accessible (by geographic or other reasons)?
It looked similar to this sketch from memory:
(Sorry, can't post images because I haven't made enough posts, yet)
e35i.imgup.net/screenshot9404.jpg
Thanks!

Related

PocketNAV without stuff in upper-right?

Hello all!
Sorry if this was asked earlier; didn't find anything like it in the search.
Basically, I really like PocketNAV's functionality; I'd just like it to be invisible unless I call it (via mapped button). Is there any way to get it to display nothing in the upper-right? If I uncheck everything it still has a grey bar in the upper-right (with the time) that blocks my icons. Any way to remove this, or other program just like PocketNAV that doesn't have that problem? Thanks!
Thank you,
Michael
I use SpbPocketPlus and it doesn't put anything in the upper right corner, though that's where you go to use it. For awhile I thought it was broken and then I figured out you have to actually press and hold in order to get it to display the drop down menu. Might be just what you're looking for.

App Request : Enable keypad backlight while screen is on

For any devs out there...
Would it or is it possible to develop an app that will keep the backlight on for the keypad ? i.e. On while the screen is on and go off when the screen goes off ?
In the dark its very annoying when using the Hero and having to fumble for the right key to press - Home, Back, Search etc.
i second that
well erm just press any key and the light will go on dude, you dont need an app for this
So you fumble and hit Home or even power off (to sleep) the screen when you only wanted to hit search or back.
Flicking the scroll wheel is the only way to light up the keys and not press the wrong one by mistake, but that tends to highlight a button, link etc... and sometimes if you hit the ball too hard, you select a screen element.
Still a pain and TBH not like any handset I used before. Backlight time out was always linked to screen time out.
You dont need to hit any key, just move the scroll wheel even slightly and lights come up. And it does need decent amount of pressure to press the scroll button, you wont accidentally press it.
er, yer, I know... but I don't want too
lets just say "even if it doesnt make sense to some people, WE want it!"
btw, there is one app "dark keys" that keeps the backlights of the keypads off all the time. this was made for the white G1. maybe it can simply be rewritten to make the reverse happen?
joemax said:
For any devs out there...
Would it or is it possible to develop an app that will keep the backlight on for the keypad ? i.e. On while the screen is on and go off when the screen goes off ?
In the dark its very annoying when using the Hero and having to fumble for the right key to press - Home, Back, Search etc.
Click to expand...
Click to collapse
+1
i'm beeing annoyed by the keys not being lit as well ...
Glad I'm not the only one
Yeah, I want it too. Thanks for bringing this up!
I think it's good idea, btw it looks cool at night. I want it too
Good idea. +1
So which dev is gong to earn a couple of $$, ££, €€ by writing this for each copy sold then ??
From what I can tell of the API docs (http://developer.android.com/reference/android/os/PowerManager.html, the SDK only allows for the keyboard backlight to be on in FULL_WAKE_LOCK state, meaning the screen will have to be full brightness.
So I don't think this request can be achieved by a pure SDK app.
How come it lights up at any screen brightness on the Hero ?
Surely its also a hardware call and not just an OS call ? These would be independent of Android and particular to each manufactures handset, else they would all be the same.
Not questioning you, but it would seem strange that its not addressable separately to the screen ???
joemax said:
How come it lights up at any screen brightness on the Hero ?
Surely its also a hardware call and not just an OS call ? These would be independent of Android and particular to each manufactures handset, else they would all be the same.
Not questioning you, but it would seem strange that its not addressable separately to the screen ???
Click to expand...
Click to collapse
I'm by no means an Android SDK expert, just posting what I found in a quick search round the docs. Happy to be proven wrong!
Lee
Of course - wasn't criticising at all
Might be able to dabble in the /sys/class/leds/ folder.
I'll take a look when I get in.
Not a dev though. Lol.
soulehmoo said:
Might be able to dabble in the /sys/class/leds/ folder.
I'll take a look when I get in.
Not a dev though. Lol.
Click to expand...
Click to collapse
Correct.
echoing a value to:
/sys/devices/platform/i2c-adapter/i2c-0/0-0066/leds/button-backlight/brightness
through adb shell turns on the backlight.
I think an SDK app could be created as a service with a broadcast receiver listening for the power state changing that just writes a positive value to the file above.
Loads of similar examples here: http://forum.xda-developers.com/showthread.php?t=565015
I'll take this on, just about got it working.
Wicked thx
You are stars (especially fullerlee)
Don't make it too expensive though

Mystery Menu

OK, this is probably a dumb question, but I can't find anything on this question anywhere. I have been playing with my stock EVO when, on a couple of occasions, a menu pops up in the middle fo the screen. I can't find any reference to this m enu in the users guide, nor can I reproduce the touches/button presses that it takes to get it to come up. But it looks interesting. It's a full color menu that covers approximately a thiord of the screen's center, with six icons. Since I can't get it to come up again, I can't recall what exact menu items are displayed, but they are icons to applications such as calendar.
Has anyone else seen this menu and know how to get it to pop up consistently?
its your 6 most recently used applications. this happens when you hold down the home screen button.
Thats your recent items menu. Hold the home key for 3-4 seconds and it lists your six most recently used apps.
Hmmmmm awesome! I didnt know that
Thanks!! I would have never figured that out.
And if you just rebooted, it says, "No recent applications."

[Q] Key remapping issues

Hello,
So... I successfully remaped the left buttons to hardware Menu and Back buttons, but the top right is giving me headaches. It's set from 4 different places (Settings>Reader, NT Mod Manger, twl4030_keypad.kl file and from Cool Reader itself) to work as page back button, but it still turns the pages forward and I can't get what is forcing it to do so. I've tried to set it as a Menu button just from the twl4030_keypad file and it works as intended, but then again, when I set it to RIGHT_PREVPAGE it goes back to be a < button...
Any ideas how to fix this?
Anyone?
I've tried to bind PREVPAGE to the other buttons, but it doesn't seems to work at all. Am I doing something wrong or what?
Maybe the problem is that too many things are trying to control the button. If you want it to function that way for Cool Reader alone, why not let everything else off the hook and let Cool Reader do its thing? Just a thought. I've not encountered problems with hardware button assignments,but then I've only ever used NTMM to do the work.
nmyshkin said:
Maybe the problem is that too many things are trying to control the button. If you want it to function that way for Cool Reader alone, why not let everything else off the hook and let Cool Reader do its thing? Just a thought. I've not encountered problems with hardware button assignments,but then I've only ever used NTMM to do the work.
Click to expand...
Click to collapse
Thanks for the reply!
It turns out that Cool Reader f*cked up somewhere. I re-installed it before, but I didn't notice that my settings were saved, so I thought the problem was somewhere else. BTW, Cool Reader's button assignment options didn't work at all - something was overriding them. What crossed my mind now was to delete the .cr3 folder and that fixed my problem.
P.S. Aaaaaand the problem is back! And I didn't even touched the Key actions... Interesting.
P.P.S. Changing the tap zones is messing with my hardware buttons... oh well.
P.P.S. So, when I change the left middle tap zone from previous to next page it also changes my top right button. Mystery solved. Right middle is also bugged.

[Q] soft-key buttons disappear (go unlit)

OK, I just acquired the Galaxy S-5 (on Verizon), after owning the Nexus-7 tablet for a year or so.
The two soft keys/buttons (i.e. 'go back' and 'show me all running apps') that are on either side of the HARD key stay lit for only a second or two, and then go away.
Is there some way to make them stay lit? (Like on android tablets such as my Nexus-7?)
(also, these two soft keys are in the OPPOSITE positions from where they are on tablets such as my Nexus-7...be nice for a consistency fix for that, too, since they go 'unlit', so you can never remember which is which) :silly:
It occurs to me that the idea for them to go 'unlit' was maybe part of some effort to reduce
battery drain. But, in this case, I for one would prefer to keep them lit ... just have them dim them down, but
please don't extinguish them!
..
Ok, I figured it out from there...
fffft said:
That's normal. Not to mention better than the way that the Nexus works.
Nevertheless you can change it in the Settings menu if you like. Just choose always on
To swap the keys, to make it more like a Nexus (are you sure that you just don't want a Nexus?), use the Xposed framework module to reassign the keys. Or you could edit the keylayout files directly. If you do a search you'll find a number of existing threads detailing how to do so.
.
Click to expand...
Click to collapse
Hmm...why would it be 'better' than Nexus, when you have to memorize/learn where each key is (other than marginal power-conservation)?
I'm sure you meant to tell me just WHERE in settings to find that tweak.
Found that info from a Google... it is here:
Settings>Display>touch key light duration.
Thx for including that 'Xposed' can do the swap of locations, but now that I've got them lit all the time, it
really doesn't matter which side is which.

Categories

Resources