Related
I've come to notice that no one REALLY knew how to fully disable screen rotation on WM devices.
Some offered 3rd party apps to get the job done, some only knew how to disable automatic rotation, but when the device went into standby and woke up again - the screen rotated back. So that didnt really work.
So if you're as desperate as i was about screen rotation,
this is what you need to do:
1. Get dotfred's free taskmanager HERE, and run it.
2. Go to "Devices" tab, and look for "MIS1:" device (oem_misc.dll)
3. Long-Tap on it, and tap on "Stop"
4. Long-Tap on it again, and now choose "Set Manual"
EDIT: This should be enough. try flipping your screen/sliding your keyboard and see if the screen changes orientation.
Now put your device on standby, and turn it on again. If orientation stays the same - you're done. If not - try steps 5-7, although they seem to be irrelevant.
5. Go to "Notifications" tab, and look for "Notifications\NamedEvents\VCPowerWakeupEvent"
6. Tap on it to make it selected
7. Disable it
(In dotfred's taskmanager, there should be a button for disabling it, but for some reason some devices couldn't see the button icons, although the buttons are still clickable. Under the notifications list there is an empty light-blue line - the buttons are there, eventough you can't see them.
The disable buttons is somewhere i the middle of that light-blue line, just tap the center until a message box popps up and asks if you'd like to disable this notification - Tap on yes.)All those steps are a one time deal - they stick even after an SR.
This has been tested on htc universal and works great.
The screen will keep its orientation even if you flip your screen, take out your built in keyboard, or turn the device off and back on.
The only time your screen will revert back to the original orientation is when you soft reset your device.
Hope this helps
So now, if you need something to help you rotate your screen on demand, you could use this small app that i've made.
its called ScreenRotate.exe (naturally), and you use it like this:
usage: ScreenRotate.exe <command line argument>
0 : Rotete to angle 0
90 : Rotete to angle 90
180 : Rotete to angle 180
270 : Rotete to angle 270
CW : Rotate clockwise
CCW : Rotate counter-clockwise
MIRROR : Mirror the current angle
If nothing will be specified at command line, nothing will happen.
.NET CF 2 is needed.
I really recommend using it along with FTouchFlo.
This way, to rotate the screen manually, you just need to drag your finger the way you want the screen to be shown, from top to bottom.
I find it quite comfortable while driving...
Those are the changes you'd need to change in FTouchFlo to make it work with ScreenRotate:
DownUpApp:\Program Files\FTouchFlo\ScreenRotate.exe
DownUpAppCmdLine:mirror
LeftRightApp:\Program Files\FTouchFlo\ScreenRotate.exe
LeftRightAppCmdLine:cw
RightLeftApp:\Program Files\FTouchFlo\ScreenRotate.exe
RightLeftAppCmdLine:ccw
Thank you so much... I have been looking for this for sooo long.
This is the perfec way to make it stick in either Portrait / Landscape.
There have been many users such as myself who have wanted our devices to stay in landscape and this is the perfect hack.
Thanks again... Cheers
BTW -> Tested and works on my Hermes
Just added it to the Hermes Wiki (Can be found under regisrty tweaks although it's not a reg tweak)
happy to hear that!
you're welcome mate.
I have a tytn hermes with satin black and in the notifications tab there isn't any notification named "Notifications\NamedEvents\VCPowerWakeupEvent". I have searched in the notifications tab in task manager and also in the notification queue in memaid. So when i soft reset the device everything goes back where it was (auto rotate screen). Any help? Thank's
EDIT: It is working perfectly even without this notification. I just tested it. So everything OK! ThanX again
zalaros said:
I have a tytn hermes with satin black and in the notifications tab there isn't any notification named "Notifications\NamedEvents\VCPowerWakeupEvent". I have searched in the notifications tab in task manager and also in the notification queue in memaid. So when i soft reset the device everything goes back where it was (auto rotate screen). Any help? Thank's
EDIT: It is working perfectly even without this notification. I just tested it. So everything OK! ThanX again
Click to expand...
Click to collapse
actually, you're right.
i guess the notification has nothing to do with it,
i don't remember what made me think it does.
i'll edit the hack accordingly.
thanx zalaros
Unfortunatelly I have found 2 bugs. I have a tytn hermes with black satin medium installed. The first bug is that with mis1 unloaded the device can not connect with the pc anymore. When I plug the device it is just being charged but active sync won't open at all. The second bug is that I can not load mis1 again. No matter what I have tried the device mis1 won't be loaded again if I had unloaded it. Any ideas?
Ok i found a way to reload this specific device (mis1).
1. Run taskmanager.
2. Go to "Devices" tab, and look for "MIS1:" device (oem_misc.dll) (it is unloaded if you have done everything described on the 1st post)
3. Long-Tap on it, and choose "Set Manual"
4. Long-Tap on it again, and choose "Set Automatic"
5. Soft reset your device
zalaros said:
Unfortunatelly I have found 2 bugs. I have a tytn hermes with black satin medium installed. The first bug is that with mis1 unloaded the device can not connect with the pc anymore. When I plug the device it is just being charged but active sync won't open at all. The second bug is that I can not load mis1 again. No matter what I have tried the device mis1 won't be loaded again if I had unloaded it. Any ideas?
Click to expand...
Click to collapse
I have the same syncing problem
Doesn't seem to work on my Tilt/Kaiser-Dutty 6.0..
Any other ideas?
redlynr said:
I have the same syncing problem
Click to expand...
Click to collapse
Just solved!
The ActiveSync troubleshooter (menu: Help/Troubleshooter for ActiveSync) offered to clear the "Enable advanced network functionality" check box. While trying to do that, an error message "Failed to disable RNDIS ..." was popping up every time. As per this suggestion, I removed virtual COM ports from Bluetooth settings and then it was possible to clear that check box.
Immediately thereafter ActiveSync woke up on the PC and offered to create a new partnership (because I deleted everything in frustration earlier). No problems for half a hour.
Then I left the administrator account and logged on as the usual limited user. ActiveSync again was unable to connect until the advanced functionality check box was restored. Does it seem that those both accounts will require different settings? Dunno, I haven't checked yet.
On my Wizard, with the TNT Rom (August 08), I don't see the device MIS1, and I don't see the event in the TaskManager.
Any ideas how to disable screen rotation, when I slide the keyboard?
Thanks in advance
Sprint HTC Touch Pro ROM 1.03.651.4
The MIS1 solution did not work for my phone (Sprint HTC Touch Pro ROM 1.03.651.4), but I found that this does:'
HKLM\System\GDI\Rotation\CamAppActive = 1
Presumably the device thinks the camera is active and thus doesn't rotate the display.
Obviously this will return to 0 after soft reset, so I used TaskMgr 2.9 to export the entry, then added a startup shortcut to import this entry with the /silent flag.
UPDATE: This fix interferes with data entry in Opera. When I try to type into a google search box, I get one character, the box looses focus, and I gotta tap on it again to type any more. Severely annoying. Goes back to normal when I change CamAppActive back to 0, and close and reopen the keyboard. I may make an exe to toggle or just make two reg import shortcuts.
Way cool!
Works for me too on a Kaiser, with old Dutty ROM.
How in the world did you figure it out? Look at that key?
Thanks, Jeff
It made perfect sense, but admittedly I tried changing everything under "Rotation" before I tried that one.
Item #21 on this list clued me into that area of the registry:
http://forum.xda-developers.com/showthread.php?t=398265
El Zilcho.
Bupkis. I've been knocking my brains out trying to disable autorotation, but still have manual enabled. (I've got some apps that play nice only in landscape, and some only like portrait. Also, I'd like to be able to slide my keyboard out really quick-like to enter some quick text, then slide it back w/o messing with screen orientation.) I tried the MIS1 disable, but no-go for me. Also tried messing with the Rotation entries, specifically the SlideKey key, but apparently that value is volatile and changes with each slide. Oh well! Unless there's a way to lock the SlideKey value so it can't be changed, that'd fix my issue. Hmm.
EDIT: Forgot to mention. I've got the Tilt (8900 I guess?) with vanilla OEM 6.1 ROM, modded only for no-bloat. (Did the old battery trick after reset/reinstall to prevent bloatware.)
EDIT: After I typed this up, figured I'd try using Settings>Screen (or somesuch) to just fix perspective. Still auto-rotates. KaiserTweak and Advanced Config can't get it to stick on one or the either, either. Editing registry turns up same results. Settings right now say it's fixed at 0 degrees but it still autorotates.
Late-breaking edit, 14-JUN-10: Got rid of it a few months ago anyways, moved to a Rhodium. No D-pad, so no more worries about those games that didn't like rotation, as they needed the D-pad to work anyways, and the TP2 doesn't have one.
Doesn't work on touch pro 2
http://forum.xda-developers.com/showthread.php?p=5928161#post5928161
That's what I resorted to!
Wow
Wow, pretty hard core fix! On the Sprint Touch Pro 2 Stock 6.1 my reg entry above only works to prevent rotation when the keyboard is slid out, it will not help with the autorotation provided by the sensor. I however put together some .reg files, with my perceived essential fixes including disabling sensor rotation:
http://forum.xda-developers.com/showthread.php?t=651166
So, following post 'step by step' didn't change anything with my screen rotation settings. still automatically rotates all the time when I don't want it too...really frustrating. This is about the 4th hack I've tried with no success. Does anyone know what the proper solution is for the HTC Rhodium? I'm running stock AT&T Tilt 2 Rom WM 6.5.
I know there are programs you can install to take over rotation control...I'm just looking for a reg change or service hack or something to stop auto rotate from ever happening.
Thanks to anyone who knows the answer!!
My screen goes crazy. During a call up to my ear it flips to horizontal, changes out of key pad view and not always to mute/speakerphone... keys view, sometimes to contact info, and can be a nightmare to get back to "end call." I've found times when the caller hung up but the TP2 put them on hold and kept my time going.
Any programs and or reg hacks to:
1) stop the horizontal flip when placed to an ear, and
2) keep it in keypad mode or general call mode?
Real pain when dialing into a system that requires keypad responses. Everytime I put it back to my ear I have to go through a crazy sequence to get back to the key pad.
This is my only complaint wth this phone, it's not easy to use as a phone!
Thanks.
I have the same problem when dialing into VM, or into any call queue. I looked through the registry a bit. Didn't see anything obviously labeled.
yeah me too. Only thing I could find was using Gyrators' exception list to not rotate the phone, but it wasnt 100% reliable. I would *LOVE* to find a way to stay in keypad mode too.
Hi All - I guess I'm just jumping on the bandwagon but I have the same issue and find it annoying. I loaded the 'incall screen tweak' but that didn't work. Any help more seasoned members than I could offer would be greatly appreciated.
Cheers!!!
I had the same issue too, whenever I put my phone up to my ear (left handed) it would go into landscape. The fix is simple but you have to edit a registry setting. I'm going by memory here, so please forgive the vague info
1) make sure to backup your reg info
2) using your favorite reg edit program, goto
HKCU\Software\HTC\HTCSENSOR\GSensor\Whitelist
3) now this is the part I kind of forgot, you need to find a string with the DATA value that includes "phone" or "dailer"
4) delete that string
5)soft reset and give it a try, the phone shouldn't go into landscape whenever you turn it during a call.
AstarteSV said:
I had the same issue too, whenever I put my phone up to my ear (left handed) it would go into landscape. The fix is simple but you have to edit a registry setting. I'm going by memory here, so please forgive the vague info
1) make sure to backup your reg info
2) using your favorite reg edit program, goto
HKCU\Software\HTC\HTCSENSOR\GSensor\Whitelist
3) now this is the part I kind of forgot, you need to find a string with the DATA value that includes "phone" or "dailer"
4) delete that string
5)soft reset and give it a try, the phone shouldn't go into landscape whenever you turn it during a call.
Click to expand...
Click to collapse
OK, I went where you said, but no dialer, and only phone entry is:
Phone/Lock/Compose/Picture
String= Dialog
And deleting this stopped "lefty" in call flipping? Doesn't make sense to me. Doesn't seem to only control dialer or phone.
Please confirm or anyone out there please help. I don't want to delete something don't understand.
Can I simple change Dialog to something like "Zero" or "0"?
MLT2004 said:
OK, I went where you said, but no dialer, and only phone entry is:
Phone/Lock/Compose/Picture
String= Dialog
And deleting this stopped "lefty" in call flipping? Doesn't make sense to me. Doesn't seem to only control dialer or phone.
Please confirm or anyone out there please help. I don't want to delete something don't understand.
Can I simple change Dialog to something like "Zero" or "0"?
Click to expand...
Click to collapse
That's it! forgot what the process name was, but yeah, deleting that stopped the phone from trying to change to landscape during a phone call. Deleting that will tell the G-Sensor not to change the orientation of the phone's screen during a phone call, however it also tells it not to change the orientation during a picture (which wasn't a big deal for me cuz I can change it when I view them in windows). You can always look up the process in google or even the forum search tool if you're still scared.
If anyone else is interested I tried a "partial" delete of the suggestion above. I created a new string leaving out the Phone.
Lock/Compose/Picture
String= Dialog
deleted old string with phone/....
So far no more "lefty" crazy problems, and pictures seem to appear in landscape.
Here's hoping all is OK!
MLT2004 said:
If anyone else is interested I tried a "partial" delete of the suggestion above. I created a new string leaving out the Phone.
Lock/Compose/Picture
String= Dialog
deleted old string with phone/....
So far no more "lefty" crazy problems, and pictures seem to appear in landscape.
Here's hoping all is OK!
Click to expand...
Click to collapse
Awesome, good job!
I installed Gyrator 2. Just create a new event with the phone as the application. Nothing for orientation, nothing on stylus, and rotate screen for actions. Then promote the event to the top. Highlight your new phone event and select orientation, it will have a check mark and a number one next to the event. It hasn't failed on me yet and I use the key pad all day long with my job!
I just upgraded to the Verizon official WinMo 6.5 and the registry hack doesn't seem to work anymore, and I'm having issues getting Gyrator to work, has anyone resolved this issue for WinMo 6.5?
AstarteSV said:
I just upgraded to the Verizon official WinMo 6.5 and the registry hack doesn't seem to work anymore, and I'm having issues getting Gyrator to work, has anyone resolved this issue for WinMo 6.5?
Click to expand...
Click to collapse
I haven't had any of the issues with the 6.5 upgrade that were mentioned with 6.1. Haven't needed to add S2U2 since the screen lock is built in and the phone is much more responsive when placed to the ear and then moved away to access the keypad. It's not perfect but vastly improved over 6.1...
I guess my point is try it the way it is with 6.5 and see if you thinks its better. leave gyrator and reg hacks aside for a few.
(please delete the other thread)
N1 suffers from one simple but debilitating hardware limitations - lack of hardware buttons.
Since trackball clicking is rarely used, it would be nice to assign a different function to it.
The first function coming to mind has to do with the fact that the device is a phone -
make trackball into a "Send" button.
This is what it should do:
1) whenever not in the dialer app, clicking trackball should bring up/start the dialer.
2) when in the dialer app, and a phone number was entered, clicking trackball should dial the number.
3) when there's an incoming call, clicking the trackball should answer the call.
I know some people with arthritis who would kill for such an app.
Thanks.
If such an app. were to be created, how about the case where the foreground process requires the use of the trackball click? Then every time you clicked it, the phone dialer would load.
I also don't personally thing the Android APIs would allow such a global hook (w/o root), but I'm not the best dev. out there so I'll let the more experienced respond to that one.
jayshah said:
If such an app. were to be created, how about the case where the foreground process requires the use of the trackball click? Then every time you clicked it, the phone dialer would load.
Click to expand...
Click to collapse
Well, that's the whole point.
You mean like a game? So far, games might be the only programs where you HAVE to use trackball for functionality.
I think all other programs allow touch screen input in place of the trackball.
Since I never use the trackball for anything, and I've seen a number of comments with the same sentiment (ie "trackball is useless"), I'd gladly trade the entire trackball function (including moving the cursor with the ball) for the ability to have a hardware "send" button.
I'll personally pay 50 dollars to a man/woman who can make this work. Then they can collect the money from thousands of market goers who'd would prefer a useful hardware button over a useless one.
Just a small bump.
why is this in the development section?
/sarcasm
jesus people your right stuff like this should be posted next to / under/ above threads like Cyanogen and Amon_RA
And how would you handle the movement of the ball when it rolls? I find when in recovery, it doesn't take much for the trackball movement to register and overshoot the options I am aiming for if not careful. Obviously a sensitivity setting would be the recourse for such a dilemma but still...or were you thinking that anything beyond buttonOn (false function obviously) is ignored?
Technically you could go as far as to have the tracball pressed trigger the dialer. From there you can scroll to call log, contacts, favourites using the trackball and then scroll down if you so desire.
I do find it odd that the phone has this hardware button and rarely is it actually used.
I think being able to touch the trackball and force the phone out of sleep is a sound expectation for this phone...the fact it isn't there is odd.
just get a sense or blur rom, that fixes everything
PsychoKilla666 said:
just get a sense or blur rom, that fixes everything
Click to expand...
Click to collapse
hahaha...
in other news, plenty of people have no interest in senseUI
One more bump.
Someone should really write this program.
Using the trackball to bring the phone in and out of sleep would drain your battery. That trackball is way to easily pressed (ie in your pocket) to be of any use as that function, but I would love the phone/send function. Would be wonderful as I hate having a phone shortcut on my homescreen.
Would be willing to pay or donate as well.
APrinceAmongMen said:
Using the trackball to bring the phone in and out of sleep would drain your battery. That trackball is way to easily pressed (ie in your pocket) to be of any use as that function, but I would love the phone/send function. Would be wonderful as I hate having a phone shortcut on my homescreen.
Would be willing to pay or donate as well.
Click to expand...
Click to collapse
Thank you. One of very few people who seem to understand this problem.
Anyway, the community's reluctance to implement this feature is a seeming indication of difficulty to do it. Maybe Android OS isn't that flexible; or maybe it's just too new, so people haven't really learned yet how to do things with it.
After all, the Win Mobile OS has been around for ages, and sure enough, as soon my Sprint Touch Pro2 was released, I had an app to rebind all the keys to whatever function I wanted.
Perhaps, in the future, we will see an Android app like the one I want. But, to my greatest disappointment, it may be years...
bump bump bump
I'll bump it one more time.
Any progress with this feature?
Another month has passed...
Has any developer figured out if it'd even be possible to make an app like that?
Thanks.
Can I disable in any way middle button (home/window/start) on my device? Is there any registry value to disable this button? Or maybe some hack? I have LG E900 with installed MFG app. In this app I can see that it can test use of hardware buttons, so probably it's possible to block this middle button in some way.
I'd need to decompile and examine the MFG app, but yes, it's probably possible.
Out of curiosity, why that key in particular? Usually, people are complaining about Search (or sometimes Back) much more.
I wan to create application that user cannot leave. I already found that I can disable Search button. Back button is no problem, because WP7 SDK support cancelling using it.
Don't forget to also block camera, volume, long-press on Back (which the SDK does not officially let you block), and power...
No offense, but if you can't come up with a better use case than that, it's going to be really low on my priority list. I've currently got (not really in order):
Re-implement SetKMode for HaRET.
Fix HtcRoot on multi-threaded apps.
Enable full-unlock on stock ROMs with HtcRoot.
Enable custom policies with HtcRoot.
Explore the AppMgr databases, see what I can learn and what I can tweak.
Find an interop-unlock that works on gen2 HTC (and hopefully others).
Find a way to use HtcUtility (a working version, for HtcRoot) on up-to-date stock ROMs.
Explore modifying ROM files using HtcRoot.
Release the next version of Root Webserver.
Update my MultiTaskToggle app.
Polish up and release my AppDataBackup app (and PC utility).
Release XapInstaller app for stock ROMs (HtcRoot).
Figure out what the hell is going on with DllImport (P/Invoke - some marketplace apps can use it?!?).
... I'm honestly losing track. I know there's more. Some are small and silly, some are huge and will take months.
Mendoza32 said:
Can I disable in any way middle button (home/window/start) on my device? Is there any registry value to disable this button? Or maybe some hack? I have LG E900 with installed MFG app. In this app I can see that it can test use of hardware buttons, so probably it's possible to block this middle button in some way.
Click to expand...
Click to collapse
you can't disable middle button (home/window/start) but you can turn off vibrate with Registry code :
Code:
[HKEY_LOCAL_MACHINE\Software\OEM\KeyState]
"application_btn_vibrate3"=dword:1
text1 said:
you can't disable middle button (home/window/start) but you can turn off vibrate with Registry code :
Code:
[HKEY_LOCAL_MACHINE\Software\OEM\KeyState]
"application_btn_vibrate3"=dword:1
Click to expand...
Click to collapse
Can I do this with a locked phone?
thanks
text1 said:
Code:
[HKEY_LOCAL_MACHINE\Software\OEM\KeyState]
"application_btn_vibrate3"=dword:1
Click to expand...
Click to collapse
This entry does not power off vibration but sets the duration of the vibration at 1ms
This little app acts as a replacement or companion to the default systembar on tablets. It can hide and restore systembar on most Android 3.x and 4.x devices.
Also like similar apps it requires root.
Unlike "GMD Hidebar" or "Hide Bar" which are recommended for simply using the device in "Kiosk mode" this app is meant to be more like an replacement for the systembar. It provides two configurable softbuttons which can be configured in position, size, color and transparency or can be completely disabled.
Several actions can be assigned to the buttons. Each button holds up to three actions, one for short, one for long click and one for swipe above the button. Possible actions:
Nothing: Um, yeah.. this does... nothing. Not sure why I implemented this.
Go back: Acts as the known "back" button to navigate back within apps.
Go to homescreen: Shortcut to directly go to homescreen... just like at the original systembar
Show recent apps: Will show a little panel to quickly switch between recently used apps. Unfortunately the well known "swipe to kill" function of the original can't be implemented because the necessary permission is only granted to apps with systems signature.
Restore systembar: An action to quickly restore systembar. With the latest version this can also be done by notification.
Show notifications: The second most important feature of the systembar. It shows a panel displaying the notifications. It is a complete reimplementation so some features are not available for now. The basic function works well on most devices.
Open apps menu: Older apps usually display their menu-button within the systembar. This action now can open the menu for those apps.
Pie Menu: Opens a configurable Pie Menu next to the touch area. This menu can be configured individually for each event.
This free version is fully functional and should be absolutely sufficient for most users. For lazy ones like me, who don't want to manually hide'n'restore systembar each time, there is a "plus"version available which automatically hides systembar for selected apps.
Oh, and yes, the free version shows a little advertisment for the plus version once in a while... if you want to get rid of it: just click this advert three times and it won't appear again. If you didn't buy the plus version after visiting it's store entry three times you probably won't ever.
please feel free to post critics, bug-reports, requests and suggestions
changelog:
1.0:
Initial release
1.1:
Improvement: wallpaper restoring much faster
Added settings for position and design of toucharea.
1.2:
Implemented panel for recently used apps
Added option for hiding systembar on boot
1.3:
Bugfixes
1.4:
Implemeted notification to quickly hide systembar
Added second touch area to use more actions
Touch areas now can be hidden completely
Fixed recentspanel not being hidden on buttonclick
Fixed toucharea not appearing under rare circumstances
1.5:
Implemented Notificationspanel
Added new action to access applications menu
Touch areas now always being composed correctly
Fixed apps malfunction on some devices (pfff.. the damn wrong environment issue most root-app-developers stumble upon)
1.5.1
Bugfixes
German translation
Visual feedback on buttonpress
1.5.2
Added information about battery, wifi and bluetooth in notificationpanels header
Support for big notifications in JellyBean
Changed unit for size of toucharea to dip (density independent pixel)
Fixed lost ability to accept calls on some phones
Added about- and contact-info
1.5.3b
No new features for now...
Service running more reliable. Should always restart after crash, manual or oom-kill
Removed full!screen from recent-apps-list (people swipe'n'killed full!screen from that list and wondered why it wouldn't work anymore )
1.6b1
few bugfixes.
New action: Pie Menu... this opens a Pie menu next to the touch area which can be freely configured for any event.
New event: Swipe... a third action can be assigned to the button which will be invoked when swiping over the button.
New extended options: activate them within the apps Options menu to freely change color and feedback of touch areas or to change long click timeout.
1.6
just bugfixes
Works good, I just need the notification area back and it's perfect!!
Works great for me.
Suggestions:
Multi colors
allow back button to exit the recent apps. Could not find any way to exit the recent apps when selected.
Sweet, this works for ICS too? Gonna try it out now.
synergeticink said:
Works great for me.
Suggestions:
Multi colors
allow back button to exit the recent apps. Could not find any way to exit the recent apps when selected.
Click to expand...
Click to collapse
Thanks for your feedback.
The recent apps panel should be closed when tapping on back button or anywhere alse outside the panel.
Well there is indeed a issue when "short click action" is set to something else than "Go back". Then tapping on button does not hide the panel. Did you mean this? I'll fix that.
I just got a message the wallpaper-workaround does not work at all on one device.
Since the wallpaper-issue was one of my main topics I am eager to solve this.
At least me and some testers never ran into this problem: if anyone else experiences this, please drop me a line. I need to collect some information to delimit that issue.
update:
the latest version now introduces the missing Notifications Panel.
At least for me the missing access to notifications was the only reason to ever restore the original systembar. So now it nearly always stays hidden.
A little drawback: new notifications so far are only being reported by sound. My own tablet doesn't have a LED and Vibro, so I personally am not missing this.
Hope you like it!
Great little app and I would be happy to shell a couple of bucks for it, one suggestion if I may though: it seems to be the case that all those who develop this kind of on-screen button apps forget to put a feedback for when the button is being pressed (momentary change of color preferably).
Since your app seems to be of the most complete offerings I think it would be great if you were to implement it in a given future. Android devices are often no strangers to lag so a feedback of any kind (that the button was actually pressed) I think it would improve the usability by quite a lot and hopefully it is easy to be implemented too...
Again thanks for this great app, here's looking forward for future updates
Stevethegreat said:
..., it seems to be the case that all those who develop this kind of on-screen button apps forget to put a feedback for when the button is being pressed (momentary change of color preferably).
Click to expand...
Click to collapse
Seems that those developers hardly ever imagine to operate an Android device with somthing else than their big Wurstfinger-thumbs
When I use the app I don't see the buttons since they are completely covered by my fingers. But you are right, when using eg. one of those attach-to-TV-Android-sticks which are operated by mouse and keyboard, and having systems touch sounds disabled, there is no feedback at all.. It's pretty easy to implement such optical feedback, soon to be done.
thanks for your suggestion.
Tsorn said:
Seems that those developers hardly ever imagine to operate an Android device with somthing else than their big Wurstfinger-thumbs
When I use the app I don't see the buttons since they are completely covered by my fingers. But you are right, when using eg. one of those attach-to-TV-Android-sticks which are operated by mouse and keyboard, and having systems touch sounds disabled, there is no feedback at all.. It's pretty easy to implement such optical feedback, soon to be done.
thanks for your suggestion.
Click to expand...
Click to collapse
Thanks
Not much else to suggest -I guess- sort from allowing more actions (through the press of the buttons) but that can be done later... oh and a way to have the buttons accessible regardless of being fullscreen or not (for those who'd love to have "hot corners" at all times)... oh and a minor bug report now that we're at it: upon reboot the app gets superuser permission but does not procede to enable the service (even though I have "enable at boot" selected).
Again thanks for this great app, loving it so far
This works really well on the Nexus 7. I was using GMD gesture control and i had remapped my volume buttons so they could be used as back and home but this is much handier. I can now have my buttons back.
Many thanks
I bought the paid version.
I have been looking an app like this for a while, tried others but this is perfect for what i want.
Top job!!
The latest version includes visual feedback for button-press. I chose a not to flashy color, hope you like it. I am thinking of implementing the before suggested user-colorable buttons but this may take some time...
Stevethegreat said:
Thanks
... oh and a minor bug report now that we're at it: upon reboot the app gets superuser permission but does not procede to enable the service (even though I have "enable at boot" selected).
Click to expand...
Click to collapse
mhh, I could only confirm this behaviour when setting SuperSu to prompt for granting su-access to the app. Which su-Manager are you using?
Did you set your su-Manager to automatically grant access to full!screen? This is necessary because the timeout waiting for su-access is set to 10 seconds... Since full!screen uses that accessibility-service it gets loaded at very early stage... far before other apps get loaded. Depending on how long it takes to fully load the system the timeout might occur even before the su-Manager gets a chance to Display it's confirmation-dialog.
Tsorn said:
The latest version includes visual feedback for button-press. I chose a not to flashy color, hope you like it. I am thinking of implementing the before suggested user-colorable buttons but this may take some time...
mhh, I could only confirm this behaviour when setting SuperSu to prompt for granting su-access to the app. Which su-Manager are you using?
Did you set your su-Manager to automatically grant access to full!screen? This is necessary because the timeout waiting for su-access is set to 10 seconds... Since full!screen uses that accessibility-service it gets loaded at very early stage... far before other apps get loaded. Depending on how long it takes to fully load the system the timeout might occur even before the su-Manager gets a chance to Display it's confirmation-dialog.
Click to expand...
Click to collapse
I was usuing "superuser" so maybe that was why; once I've installed superSu the issue went away and now it boots with my system I've I asked it to
As for the visual feedback it works great but it goes away a bit too soon (Google's own feedback lasts quite a bit longer when one presses -say- the home button) and also it's less than visible when one uses low opacity. I like how the color is discrete though, great choice :good:
All in all I'll recommend this to friends what a great app
BugReport:
While using the app, SnapChat wont work. It FCs. When turning off fullscreen, it works.
Edit: To be to the point; One can take a picture with snapchat and put a comment on it, but when you press "send" it FCs.
dmbardal said:
BugReport:
While using the app, SnapChat wont work. It FCs. When turning off fullscreen, it works.
Edit: To be to the point; One can take a picture with snapchat and put a comment on it, but when you press "send" it FCs.
Click to expand...
Click to collapse
installed this SnapChat on my tablet and could send and receive pictures without problems. I am just to blind to find a place to enter a comment to the picture!?
Anyway, I doubt I could do anything about another app complaining about missing systembar or something...
Is it a phone you installed the app to? ... there are some problems known with phone devices like not receiving calls anymore.. may be it's some related problem. :-/
Tsorn said:
installed this SnapChat on my tablet and could send and receive pictures without problems. I am just to blind to find a place to enter a comment to the picture!?
Anyway, I doubt I could do anything about another app complaining about missing systembar or something...
Is it a phone you installed the app to? ... there are some problems known with phone devices like not receiving calls anymore.. may be it's some related problem. :-/
Click to expand...
Click to collapse
You just click the screen for adding a comment.
Anyhow, yes. Its a phone. Its my Xperia V.
I got quite a few apps tho, so it might just aswell be any other app aswell.
But I found it to good to be a coincidence when I disabled fullscreen and then it worked.
The FC still happends when I dont comment btw.
But it might be SC complaining ofcourse. But its no problem, I just added an invisible button to get the systembar back before I take pictures with SC.
Your app is the only one working properly btw. the lower left and right buttons that you've added are perfect. I can make them small and invisible wich makes it perfect. GREAT job!
Keep up the good work.
I'd like the option to have the notification bar on, but the onscreen buttons off, with just the corner buttons etc., if that makes sense. I like having the notification bar on, I think it's useful. Apologies if there is a way to do this already, I couldn't seem to find it.
It would be good if it rearranged the app icons too to fill the extra space better.
Or alternatively, I would like notification on, original onscreen buttons on but transparent with screen visible behind them, that would be a good option too, I think.
Thanks for the app though.
TheGSL said:
I'd like the option to have the notification bar on, but the onscreen buttons off, with just the corner buttons etc., if that makes sense. I like having the notification bar on, I think it's useful. Apologies if there is a way to do this already, I couldn't seem to find it.
It would be good if it rearranged the app icons too to fill the extra space better.
Or alternatively, I would like notification on, original onscreen buttons on but transparent with screen visible behind them, that would be a good option too, I think.
Thanks for the app though.
Click to expand...
Click to collapse
Unfortunately that not possible at all... at least not without patching original systemUI. Buttons bar and notifications bar are created by the same process. Disabling this process obviously means disabling both bars. I might implement an internal UI similar to the original systemUI some day. But thats at the end of a long list of wishes and suggestions I got so far, because it would take much, much work.
Re: [App][3.x][4.x] full!screen - App to hide/replace Systembar
Hi, this program is almost perfect for me, but I have a question: given that it's oriented towards tablets, ¿do you foresee any problem using it in a phone?. I've installed the free version in my Xperia T and it seems to work alright, but I want to be sure.
--
Enviado desde mi móvil.