Related
A new user interface idea. I have created this new user interface though i have no coding skills i do have the the skills of ideas...hope u guys make it come to alive i will add more images on how it shud work and..the graphics behind it.
Desiflare999 said:
A new user interface idea. I have created this new user interface though i have no coding skills i do have the the skills of ideas...hope u guys make it come to alive i will add more images on how it shud work and..the graphics behind it.
Click to expand...
Click to collapse
That looks like it could be accomplished with Wisbar Advance Desktop. At least I think you could get real close.
well..im talkin about a whole new ball game, meaning for example: the arrow on the bottom can be pressed and drawn up by your finger to display things like programs running or etc. its lyk using one of the cube roll type, and while the arrow is being pulled up other menus such as the one on the right will automatically go right and the clock menu will go left to make space for the Arrow screen. The arrow screen will also be lyk a notification screen, lets say a new call came, the arrow screen will automatically go up to display an incoming screen but this time it will be transparent. The left menu will work like this: Lets say the music icon is chosen, the icon will light up and that menu only the box will move left and while its moving to the left the other menus that was with will move to the right, and the clock menu will move to the left, the arrow menu will go down. and it will expand to take over the entire screen to display the music player. The orb will roll to the right. and to exit music all the user gotta do is scroll their finger from left to right the opposite direction it came from.
Desiflare999 said:
well..im talkin about a whole new ball game, meaning for example: the arrow on the bottom can be pressed and drawn up by your finger to display things like programs running or etc. its lyk using one of the cube roll type, and while the arrow is being pulled up other menus such as the one on the left will automatically go left and the clock menu will go right to make space for the Arrow screen. The arrow screen will also be lyk a notification screen, lets say a new call came, the arrow screen will automatically go up to display an incoming screen but this time it will be transparent.
Click to expand...
Click to collapse
That would be hot!!
so you've just invented..WisbarAadvancedDesktop NG.
nothin said:
so you've just invented..WisbarAadvancedDesktop NG.
Click to expand...
Click to collapse
lolz..i used photoshop
In order to truly make this a reality, you'd have to use native C code. I mean, wisbar, and flash can do it, but at the expense of a lot of system resources. If no one takes it up, maybe I'll put aside some time to code it, especially if you give me more motivation by rolling out some more screenshots of your ideas .
thundershadow14 said:
In order to truly make this a reality, you'd have to use native C code. I mean, wisbar, and flash can do it, but at the expense of a lot of system resources. If no one takes it up, maybe I'll put aside some time to code it, especially if you give me more motivation by rolling out some more screenshots of your ideas .
Click to expand...
Click to collapse
yes I will post up more images but sad thing is I don't have much experience in creating flash images but I will post images. Well thundershadow I would be glad to assist u in this project because I seen wat u can do lolz I seen ur pocketmelody and extremely impressed keep up the good work
If you post up enough images, I can give it a whirl. No promises at all, cuz I'm pretty committed to PocketMelody. But I've been dieing for a new interface that is independent of wisbar and flash, and it is my opinion that user interfaces aren't generally so dazzling that flash is a MUST use application. Most of the animations etc are simple yet effective. And the strength of their looks is in good CLEAN LOOKING static graphics (which I'm no good at making).
So, what I'm saying is, if your ideas inspire , I'll set aside some time, but again, no promises.
help
Even if i'm not so god in programming, i'd be proud to help you, whatever te way I could help
(maybe as beta tester)
don't hesitate to ask !!!
i've post some of my ideas in the Elf's forum
here's some preview
another idea i called "colour"
more samples here:
http://forum.xda-developers.com/showthread.php?t=349583&page=5
it looks to cartoon like.
The above ideas can be 90% completed with pre-existing software.
Wisbar Advanced Desktop and possibly Mortscript to help with some of the multiple dock hiding/showing. A new version might exist that lets you slide/fade in and out docks...that'll make everything visually more appealing. Once you get to that point all you need to do is create a today plug-in to show you the current running programs as icons. The today plug-in will need to have an option to create height and width settings so that it'll be perfect in a slide in dock controlled by the up arrow.
The main thing that will be missing from your idea is the touch-style movement. The up arrow will be something you click on instead of the desired finger slide.
SeanFromSoCal said:
Wisbar Advanced Desktop and possibly Mortscript to help with some of the multiple dock hiding/showing. A new version might exist that lets you slide/fade in and out docks...that'll make everything visually more appealing. Once you get to that point all you need to do is create a today plug-in to show you the current running programs as icons. The today plug-in will need to have an option to create height and width settings so that it'll be perfect in a slide in dock controlled by the up arrow.
The main thing that will be missing from your idea is the touch-style movement. The up arrow will be something you click on instead of the desired finger slide.
Click to expand...
Click to collapse
Granted, but if you really want to make it usable to a wider range of devices, you can't beat coding it natively. I've used WA/WAD on my Wizard, and after a while it gets too slow.
Lol dat looks hot
Trigger9407 said:
Lol dat looks hot
Click to expand...
Click to collapse
Buy WAD2.
The message you have entered is too short. Please lengthen your message to at least 10 characters.
Summary:
A method of executing the device lock/unlock features of Windows Mobile by using the gestures available in FTouchFlo v1.4.1.
Here's a sample video of it in action courtesy of kidnamedAlbert: http://www.youtube.com/watch?v=wjPxHroy9VU
Current Status:
I've got the basics working on my device right now, and it works quite well. Beta version is now available, where I offer a choice of install methods. Since many users already have FTouchFlo and some version of the "true" HTC Cube application with my TFloCubeCtrl, then all that is needed for this is an update to version 1.2.0 of TFloControl, and an adjustment to the FTouchFlo config file. I also have a stand-alone cab installer for just FTouchFlo and the "slide 2 lock/unlock" capability. Note: there's no cube involved in this one!
Where is it?!
*NEW* CAB installer for TFloControl + FTouchFlo + config for "Slide to Lock/Unlock" with a left-right gesture now available here: http://rapidshare.com/files/128559842/TFloControl_v1.2.0___FTouchFlo_v1.4.1.cab
Be sure to check the install/usage notes in Post #4
If you've already got FTouchFlo v1.4.1 installed, and an HTC Cube using TFloCubeCtrl, then you can just download the new TFloControl.exe and FTouchFlo.config files from the attachments, and follow the directions in Post #4
What's Next?
Currently, configuration of TFloCubeCtrl is through command-line params fed by FTouchFlo. I think this could be made better, and possibly there should be a configuration app ... since all of my FTouchFlo gestures just map to calling TFloCubeCtrl anymore, which nowadays does so much more than just control the HTC Cube!
I'm currently talking with efrost about the possibility of turning TFloCubeCtrl and it's functionality into a plug-in for the newer FTouchSL application.
I wonder what other sorts of features I could build into it as additional parameters. So far I have:
Lock
{no params} - execute the device lock
home - return to the Today screen and then lock
suspend - lock, and then suspend the device
Unlock
{no params} - unlock the device
<milliseconds> - amount of delay between the simulating the left softkey, and clicking the unlock button. I added this in case different devices needed different amounts of lag time based on processor speed. 50ms seems to work quite well on my Kaiser.
Donations:
If you like what I've done, then please ... feel free to donate to me. It definitely helps in keeping me motivated to add new features and answer questions. However, if you find this function useful, you should also consider a donation to efrost ... because without FTouchFlo v1.4.1, this little project would not exist.
Props:
efrost - for making FTouchFlo!
Matt Armstrong - creator of DeviceLock, where I first saw that the unlock process could be automated
wacky.banana - for pointing out the "bug" that clued me in that unlock was possible via FTouchFlo
kidnamedAlbert - for making a video of it in action
Background
While working on a project to bring full HTC Cube finger control to non-Touch devices, I developed an application to work hand-in-hand with efrost's FTouchFlo application. In addition to being able to control the HTC Cube, I also added a few system control functions that you could map to FTouchFlo gestures. One such system control function was the ability to engage the standard device lock, with additional options for returning the display to the home screen, and also for suspending the device. I soon realized that this was a slick was to lock your device, by just sliding your finger across the screen left-to-right. However, this then still left me with the rather lame way of unlocking the device, pressing the left softkey, and then clicking on a button on the screen. I became further annoyed when attempting to unlock the screen in bright sunlight, where it's next to impossible to find the button on the screen (at least for me!).
Where is this going?
One day, I had a small revelation. Someone had previously reported a "bug" with TFloCubeCtrl, whereby you could open up the cube, even when the device was locked. I subsequently added some code to ensure that all functions were disabled if it detected that the device was locked. But while it was reported as a bug ... the indication here was that TFloCubeCtrl would receive calls from FTouchFlo even when the device was locked. I suddenly realized that this meant that I could also add functionality to TFloCubeCtrl to unlock the device, by automating the unlock procedure.
So, does it work?
In fact ... it works just the way I had hoped. Now, with the device on, but locked with the standard WinMo device lock functionality, I can swipe my finger left-to-right, and the device becomes unlocked. You don't even see the unlock screen (on my Kaiser anyway), as it's dismissed so quickly due to the automated unlock.
And why should I care?
Well, I like it because it works well for me, and solves some of the annoyances I've had in the past. Specifically, I like the HTC Home screen ... as I'm used to it's layout, and it has everything there I need. So I like to be able to lock the device with a quick action, and have it revert to the home screen upon locking. And thanks to FTouchFlo, a left-right swipe anywhere on the screen will work (no trying to hit a specific icon). Then, to unlock, just the same swipe again is all it takes. It's a simple action, and can be done anywhere on the screen as long as it's a complete swipe across the screen ... so you don't even need to look at the screen to unlock the device. And best of all, it all works *with* the standard device lock functionality ... so even if you lock with a different method (device lock on today screen), you can still "slide to unlock". Incoming calls work the same as before ... and PIN code input should also still function normally (initial tests have shown this to be true!)
Here are some thoughts I've come up with on possible features:
Specify an X,Y to simulate a mouse click after the Today screen is shown. (In order to ensure a particular tab is also displayed)
Specify a particular application to be displayed before locking, instead of the Today screen
Vibrate when the device is unlocked (DeviceLock offered this when "easy unlock" was enabled)
Specify a particular application to be displayed after unlocking
Installation / Usage Notes
General Usage Warnings -
This app requires FTouchFlo. As such, installing this will subject your device to known FTouchFlo "issues"
Once FTouchFlo is running, it cannot be stopped without a soft reset
While FTouchFlo is running, the Transcriber SIP and Screen Alignment utility cannot be used
Some programs that are "finger friendly" themselves do not work well with FTouchFlo, and should be added to the Exclusions list in FTouchFlo.config. Some common known apps are already in the list.
After a soft reset, you must manually start FTouchFlo before you can "Slide to Lock/Unlock". Alternatively, you can create a shortcut to FTouchFlo in your StartUp folder.
CAB Install Method -
Install the CAB file on your Windows Mobile device
Be sure to install to the Device (not a storage card)
Run FTouchFlo, found under Start->Programs
Perform a left-right slide gesture to lock the device
Perform the same left-right slide gesture again to unlock the device
Enjoy
File Install Method (Advanced Users Only) -
Use this method if you already have FTouchFlo installed, and/or if you have an HTC Cube install already on your device using TFloCubeCtrl
Copy TFloControl.exe into a \Program Files\TFloControl folder
Update your FTouchFlo.config file to reflect something similar to my sample
TFloControl is the new name for the app, replacing the old TFloCubeCtrl (it does more than control the cube!)
Morning Kona. I see you have decided to go public on this, which is great!
A couple of points from me:
One of the things you are going to have to watch out for , as you develop this tool, is getting the tool to work in a consistent and predictable manner with the inbuilt WM6 pin lock facility.
Because I am security conscious, I have pin lock initialise itself half an hour after locking the device either with device lock or Slide-To-Unlock (S2U2). When using S2U2 I have found that if a call comes in after pin lock is engaged, trying to answer the call can cause unpredictable results ranging from the call being successfully answered, to S2U2 to being presented with the pin lock keyboard to unlock the device before the call can be taken, to the call being dropped altogether.
This behaviour became such a pain that I dropped S2U2 altogether in order to get a consistent method of answering calls when the device is locked in this way, ie with device lock and pin lock in operation. I note this is an area you have not tested yet, hence me advising caution here.
Another point from me: I am assuming that your lock will not work unless a version of Ftouchflo is installed? If yes does that mean that people like me who have given up on Ftouchflo and the Cube will not be able to use your tool?
Final point; early days yet but have you thought of integrating your tool with the organic lock invented by someone on here?
Hope you find these points helpful. More than happy to undertake some testing for you if you let me know what is required, etc.
Cheers
WB
will this be a lot like the unlocking mechanism from wm 7 in which you have to slide a certain way so the device unlocks. A bit confused as far as function though. I am glad you are starting a new project...
I can not say how much i'm interested in such software, even though i dont pin lock my device, but i really like to lock it cause it many times make a call or opens and drains the battery without any need..
any way .. i'm waiting .. and i believe it's gonna be great
cheers
WB,
Thanks for the input. So far ... here's what I can tell you:
wacky.banana said:
One of the things you are going to have to watch out for , as you develop this tool, is getting the tool to work in a consistent and predictable manner with the inbuilt WM6 pin lock facility.
Because I am security conscious, I have pin lock initialise itself half an hour after locking the device either with device lock or Slide-To-Unlock (S2U2). When using S2U2 I have found that if a call comes in after pin lock is engaged, trying to answer the call can cause unpredictable results ranging from the call being successfully answered, to S2U2 to being presented with the pin lock keyboard to unlock the device before the call can be taken, to the call being dropped altogether.
This behavior became such a pain that I dropped S2U2 altogether in order to get a consistent method of answering calls when the device is locked in this way, ie with device lock and pin lock in operation. I note this is an area you have not tested yet, hence me advising caution here.
Click to expand...
Click to collapse
Since what I've done here is devise a way to use gestures as a way to interact with the standard built-in Windows Mobile locking mechanism, we should be OK here. My initial tests are indicating that everything functions predictably when PIN locking is enabled. My unlock gesture works when the PIN is not yet enabled. And once the PIN screen appears, the unlock gesture basically doesn't do much ... and you have to enter the PIN to access the phone. Incoming calls are unaffected, as the standard WinMo "Incoming Call" screen appears, and a SoftKey press will still answer without requiring an unlock. This is where people's desire for functionality is probably going to differ.
wacky.banana said:
Another point from me: I am assuming that your lock will not work unless a version of Ftouchflo is installed? If yes does that mean that people like me who have given up on Ftouchflo and the Cube will not be able to use your tool?
Click to expand...
Click to collapse
Yes ... and no. FTouchFlo is currently required, as this project is intentionally a solution to work with FTouchFlo. However, the cube is not a requirement ... it doesn't even have to be installed.
wacky.banana said:
Final point; early days yet but have you thought of integrating your tool with the organic lock invented by someone on here?
Click to expand...
Click to collapse
I have downloaded Organic Lock, and will test it out. My initial thoughts ... are that it should integrate quite well with what I've done here, since it's designed to work with the built-in WinMo device locking. I'll post my results when I get to test it out.
domineus said:
will this be a lot like the unlocking mechanism from wm 7 in which you have to slide a certain way so the device unlocks. A bit confused as far as function though. I am glad you are starting a new project...
Click to expand...
Click to collapse
Perhaps ... I honestly haven't seen what WM7 is offering. In a nutshell, what I've done here will allow you to use any of FTouchFlo's gestures to lock/unlock your device using the built-in WM6 device lock. Current FTouchFlo gestures are up-down, down-up, left-right, and right-left. You basically sweep your finger across the entire length of the screen in one continuous motion. It takes a bit of getting used to, but I get it to recognize my gestures about 95% of the time these days.
solomhamada said:
I can not say how much i'm interested in such software, even though i dont pin lock my device, but i really like to lock it cause it many times make a call or opens and drains the battery without any need..
any way .. i'm waiting .. and i believe it's gonna be great
cheers
Click to expand...
Click to collapse
I currently don't really use the PIN lock feature myself ... but your scenario of the phone accidentally waking up and doing things unintentionally is a big reason I started using the device lock to lock my phone. But when I got annoyed with the unlock procedure, I wrote the "slide to unlock" part, which is really useful (to me). This is really more of a convenience feature that a real security measure. But it makes the device lock/unlock very easy to use. I just put it on my wife's phone, because her phone kept calling people while it was in her purse!
Slide to Answer
I just had a thought ... and tested it out. You can actually "Slide to Answer" as well, when a phone call comes in.
As is true with unlock, the softkey method still works ... however, if the device is currently locked, and a phone call comes in ... if you perform the unlock gesture, TFloCubeCtrl will try to initiate the unlock by pressing the left softkey, which in turn answers the call! It's really a side-effect in this case ... but it works! Interesting ... but it would probably be more useful if I could disable the on-screen buttons, and require either a hardware keypress, or the slide gesture.
Kona_Mtbkr said:
..... It takes a bit of getting used to, but I get it to recognize my gestures about 95% of the time these days.
Click to expand...
Click to collapse
Hey Kona,
Thanks for the comprehensive response to my points. The tool looks more promising every time I hear from you.
To the point about 95% accuracy this isn't too bad and, from my experience, probably on a par with S2U2. When I was playing with TouchFlo in the early days I found you could increase the consistency of the gestures by changing the sensitivity response or whatever it was called.
When are you expecting to have a beta version of the tool out for testing then?
Cheers
WB
wacky.banana said:
Hey Kona,
Thanks for the comprehensive response to my points. The tool looks more promising every time I hear from you.
To the point about 95% accuracy this isn't too bad and, from my experience, probably on a par with S2U2. When I was playing with TouchFlo in the early days I found you could increase the consistency of the gestures by changing the sensitivity response or whatever it was called.
When are you expecting to have a beta version of the tool out for testing then?
Cheers
WB
Click to expand...
Click to collapse
Yes ... changing the sensitivity settings was key for really making FTouchFlo useful. It's a balancing act between the pressure sensitivity, and the gesture delay ... which controls how long FTouchFlo waits before deciding that you're not actually doing a gesture, so it forwards the input on to the OS. It makes it a bit trickier to try to use scrollbars or to do other dragging operations (like selecting multiple items) when FTouchFlo is in use. Not sure if FTouchSL has improved on any of these items.
As for release ... we'll see how the weekend goes. It'll be easier for me to post the new app, and a sample config for those who already have FTouchFlo and an HTC Cube install with TFloCubeCtrl. But I know that isn't going to cut it ... so I'll put a "fresh install" cab together as well.
Kona,
Good idea putting an all-in-1 cab together for an easy install otherwise all you will get is a thousand questions on how to install the app and what other linked apps are required. Probably a major distraction if what you really want to know is how the user experience is progresing.
Re the sensitivity compromise, have you had a chat with Efrost as to where his latest version of Ftouchflo is now at, from a technical perspective?
This thread is now on my auto notify list, ready for your next move.
All the best.
WB
im completely interested but does this have a transparent background on the home screen like the original windows unlock screen?
if so, this if EXACTLY what im looking for.
a lock on wakeup feature would be great too.
thanks,
wacky.banana said:
Kona,
Re the sensitivity compromise, have you had a chat with Efrost as to where his latest version of Ftouchflo is now at, from a technical perspective?
Click to expand...
Click to collapse
Well, I have contacted him through PM here ... and asked about the plugin architecture for FTouchSL, to see if he'd let me rebuild my TFloCtrl app as a plugin. He seemed to be receptive to the idea ... but I haven't heard much from him since. I'm pretty sure the free version of FTouchFlo isn't going to progress past v1.4.1 ... as all efforts are now on FTouchSL. It's only like $15, so I'll probably buy a copy at some point. efrost deserves our support! Of course, I was hoping he'd give me a license for developing my plugins against, and then I could buy a copy for my wife!
I need to get a bit more insight into his plugin architecture too, however. I'm not completely sure that everything that I've done so far with TFloCtrl will work in his plugin architecture. We'll have to see.
sounds lije it will be awesome...when developed of course. i am really into being able to lock my device easily and be something i can unlock without much thought or having to look at the keyboard whilst i enter an alpha-numeric code. kinda biometrics like without the fingerprint scanner. thanks for the info and i am waiting for more news.
kidnamedAlbert said:
im completely interested but does this have a transparent background on the home screen like the original windows unlock screen?
Click to expand...
Click to collapse
Yes, in fact, TFloCtrl has no background ... or window at all. It's more of a windowless process, that sets the display to the Today screen, locks the device, and exits. You're left at the Today screen with a locked device. Hmm, that gives me an idea for a feature, bridging between another app I'm working on. An option to also simulate a click on the Today screen, to ensure a particular tab is selected upon locking.
kidnamedAlbert said:
if so, this if EXACTLY what im looking for.
a lock on wakeup feature would be great too.
thanks,
Click to expand...
Click to collapse
Well, to put in a lock on wakeup feature would require a whole separate application. At that point, I'd almost be rebuilding armstrong's DeviceLock. You should take a look at this, as I was running it for a while for just that feature. It should work just fine with my app, because he is also using the normal built-in lock functionality. He also had an "easy unlock" feature that only required the softkey press ... but it was too "easy" for me. The swipe gesture is much less likely to occur accidentally, but still can be completed without even looking at the screen! That's the biggest benefit in my mind.
Daremo_23 said:
sounds lije it will be awesome...when developed of course. i am really into being able to lock my device easily and be something i can unlock without much thought or having to look at the keyboard whilst i enter an alpha-numeric code. kinda biometrics like without the fingerprint scanner. thanks for the info and i am waiting for more news.
Click to expand...
Click to collapse
"biometrics without the scanning" ... that's a pretty good way to describe it
I think it nice, because it offers the protection from accidental button/screen presses of the device lock, but with easier unlocking ... as you said, not having to look at the screen. But in addition, I'm also hoping it'll pair well with Organic Lock, to offer the additional security that people like WB are looking for.
And as far as "developed" goes ... it's already working on my device! I'm just thinking about what features to include for a Beta 1 release ... and also I need to invest the time to put together the installation ... or else the thread will fill with "how to install?" postings. I learned my lesson last time with the TFloCubeCtrl thread.
Just an idea, stolen from the Android platform.
You could make the unlock gesture user-customizable. Maybe there could be an interface in the settings for users to "draw" their unlock gesture and practice on it. Then, if someone wants security without a password, he can use a complex gesture.
edit: That was a horrible explanation, haha, you'll get the point from this video:
http://www.youtube.com/watch?v=arXolJrLVEg
I want to start this threat to put together information in order to sort out why the device lock delay (see below) appears and how to solve it.
wm6.5 device lock app has changed from "tap here and next there" to a slider style like app you know from s2u2.
problem:
device lock is enabled
Code:
HKCU\ControlPanel\BackLight\AutoDeviceLockEnable=1
wake up the device by short pressing the power button
device lock screen is displayed instantly
it takes ~2 seconds until the slider of the device lock screen is activated and can be slided.
if you use device lock it becomes really annyoing.
there are some threads about this like this one, but the solution is not working on a Touch HD.
can anybody sched some light onthe problem why and where it appears or maybe someone already found a solution.
please post any useful information.
please do not post tips like use s2u2 or any other locking app - I do not want to use them.
the only thing i can thing of is use s2u2 or any other locking app
egoist6 said:
please do not post tips like use s2u2 or any other locking app - I do not want to use them.
Click to expand...
Click to collapse
cookiemonster55 said:
the only thing i can thing of is use s2u2 or any other locking app
Click to expand...
Click to collapse
cookiemonster, either you didn't read his post or you're a sort of a jerk.
And yes, in response to the poster, I have the same problem.
Zoltair Wright said:
cookiemonster, either you didn't read his post or you're a sort of a jerk.
And yes, in response to the poster, I have the same problem.
Click to expand...
Click to collapse
latest build 23001 still has this annoying delay
Iv noticed this too... The biggest annoyance for me is you turn the device on and the backlight isnt very bright, makes it near impossible to see the screen in daylight. Is it possible to have the backlight come on full when you press the power button?
i have this problem too. i think it is a serious bug of wm6.5
just hoping it will be fixed when the official release come out.
god i thought i was the only one, something about my config...
and i was exited about the new 6.5 lock screen,
but then it works like all the other M$ 6.5 sh!t, it doesn't
had to switch away from it
May be this help you:
http://forum.xda-developers.com/showthread.php?t=527219
A1983 said:
May be this help you:
http://forum.xda-developers.com/showthread.php?t=527219
Click to expand...
Click to collapse
thanks for your help - but that was the solution i am talking about in my first post and unfortunately does not work.
also find this intensely annoying! if you look, on my hd, in the top left corner a small windows flag appears to indicate that the slider is locked, it disappears once the slider is active, and there is a definite exact time out, i dont think its random or a load time
hope this is sorted cos its rubbish!
regards
mat
What I've done that got rid of most of the delays regarding the lock screen on my Xperia:
I got 6 cpr files from my device's /Windows directory: LS_LockScene_xxxxxxx.cpr, LS_AlarmScene_xxxxxxx.cpr and LS_PhoneAlertScene_xxxxxxx.cpr. Get files that fit the resolution of your device, they are in pairs for portrait and landscape
opened each one of them in a text editor (they are XMLs inside)
removed all "ControlSequence" sections from them (those sections are small (like 4 entries) and big (up to 21 entries). These sections are animations of arrows. Arrows will still be there after that, they just won't animate.
uploaded cpr files back to /Windows, overwriting originals
soft-reseted.
Hope it works on your devices too
lemat1 said:
also find this intensely annoying! if you look, on my hd, in the top left corner a small windows flag appears to indicate that the slider is locked, it disappears once the slider is active, and there is a definite exact time out, i dont think its random or a load time
hope this is sorted cos its rubbish!
regards
mat
Click to expand...
Click to collapse
yeah. and with 6.5 23003 onwards in the top right corner an "X" (for close) appears. only when it goes off you can access the slider.
it seems as if an app is started.
pikipirs said:
What I've done that got rid of most of the delays regarding the lock screen on my Xperia:
I got 6 cpr files from my device's /Windows directory: LS_LockScene_xxxxxxx.cpr, LS_AlarmScene_xxxxxxx.cpr and LS_PhoneAlertScene_xxxxxxx.cpr. Get files that fit the resolution of your device, they are in pairs for portrait and landscape
opened each one of them in a text editor (they are XMLs inside)
removed all "ControlSequence" sections from them (those sections are small (like 4 entries) and big (up to 21 entries). These sections are animations of arrows. Arrows will still be there after that, they just won't animate.
uploaded cpr files back to /Windows, overwriting originals
soft-reseted.
Hope it works on your devices too
Click to expand...
Click to collapse
great. that helped a lot!
now the lock screen is flickering shortly and the whole lock screen slides in once more from the bottom to the top but then the slider is instantly accessible.
from a time perspective a great improvement!
update:
basically you can delete the whole layer
Code:
<Layer ID="SlidePath" >
...
</Layer>
which removes the animation of the arrows and the arrows themselves.
do not delete this section if you do not know in which direction to slide the button
however, the delay is still ~1 second. but i think i can live with that allthough it is annoying to wait one stupid second to proceed
the delay you get when recieving a call with lockscreen on is caused by the slide to answer feature of alot of the new dialers. it conflicts with the popup call answer screen with wm 6.5. to fix this can find a dialer that doesnt have slide to answer feature. the backlight problem came from backlight.dll in the kaiser, using a new one from stock rom now and it works perfect
If you enable the enter a pin number after slide, there is no delay at all. I know this isnt a solution i hate entering a pin. however, i have a felling the pin app is running in the background and thus you dont get the flicker where it flicks from Start menu back to the lock app. Hence if you could create a dummy pin app, it could work to stop the delay.
twopumpchump said:
the delay you get when recieving a call with lockscreen on is caused by the slide to answer feature of alot of the new dialers. it conflicts with the popup call answer screen with wm 6.5. to fix this can find a dialer that doesnt have slide to answer feature. the backlight problem came from backlight.dll in the kaiser, using a new one from stock rom now and it works perfect
Click to expand...
Click to collapse
thanks for your reply. but i also have the delay when simply waking up the device by pressing the power button (without receiving a call)
xternal said:
If you enable the enter a pin number after slide, there is no delay at all. I know this isnt a solution i hate entering a pin. however, i have a felling the pin app is running in the background and thus you dont get the flicker where it flicks from Start menu back to the lock app. Hence if you could create a dummy pin app, it could work to stop the delay.
Click to expand...
Click to collapse
that's true. i replaced LS_SimplePinScene_480x800.cpr with an empty one and allthough not using pinlock, the lock app did not work at all.
What if we designed something where when you slide it calls a mortscript or something and enters 0000+OK to by pass the pin screen (assuming you set pin to 0000). Then you edit the Pin screen so it is just a clear page, so you dont even see the pin screen flash up.
Not sure if this is at all possible as im not a programmer. Just a thought
xternal said:
What if we designed something where when you slide it calls a mortscript or something and enters 0000+OK to by pass the pin screen (assuming you set pin to 0000). Then you edit the Pin screen so it is just a clear page, so you dont even see the pin screen flash up.
Click to expand...
Click to collapse
good idea. maybe someone can change LS_SimplePinScene_480x800.cpr so that it does not expect the pin from screen but is embedded directly into the cpr file?
can anybody who has a better understanding of cpr files or the lock app give us some tips?
xternal said:
Not sure if this is at all possible as im not a programmer. Just a thought
Click to expand...
Click to collapse
me neither
The menu icon on the home screen takes a lot of space. There could be 4 icons in there instead. Can it be removed and then bond to another phisical key like the press of the ball?
zenderady said:
The menu icon on the home screen takes a lot of space. There could be 4 icons in there instead. Can it be removed and then bond to another phisical key like the press of the ball?
Click to expand...
Click to collapse
Not really understanding what your asking. Are you talking about when you hit your menu button?
I am also not really understanding the question which is why I didn't respond the first time the OP created the thread.
To OP:
Please don't make multiple threads for the same question just because your not getting a response!
DirectMatrix said:
I am also not really understanding the question which is why I didn't respond the first time the OP created the thread.
To OP:
Please don't make multiple threads for the same question just because your not getting a response!
Click to expand...
Click to collapse
Ok I'm glad I wasn't the only one. This was the first thread I looked at when I got into work. Had to wipe the sleep out my eyes take a sip of coffee and try to figure out this question.
Are they talking about the app drawer and phone tab slider on a Hero ROM maybe?????
DirectMatrix said:
Are they talking about the app drawer and phone tab slider on a Hero ROM maybe?????
Click to expand...
Click to collapse
Thats what I was thinking, but not quite sure. Just waiting on OP to respond.
I think he/she means the app draw, that's the only thing that makes sense.
1) That would require a complete re-write of the app
2) It wouldn't give you enough vertical space for the icon and text
3) All the buttons are already used (shocker!) The trackball can be used to select an icon and click on it, so that would have to be disbaled.
ok thx for the answears and sorry I crated 2 threads about this one. On the first one I messed up the thread name so I thought nobody would read it. Going back, I am talking about the button that is on the bottom of the screen, the one that pulls up all the apps. That one takes a lot of space, actually a whole row where there could be other icons instead.
So I was thinking if there is a possibility to link that menu to an actual phisical key, like pressing the scrolling ball.
zenderady said:
ok thx for the answears and sorry I crated 2 threads about this one. On the first one I messed up the thread name so I thought nobody would read it. Going back, I am talking about the button that is on the bottom of the screen, the one that pulls up all the apps. That one takes a lot of space, actually a whole row where there could be other icons instead.
So I was thinking if there is a possibility to link that menu to an actual phisical key, like pressing the scrolling ball.
Click to expand...
Click to collapse
Yep, that's what I thought, read my post above, it will explain why it's pointless.
actually the ahome does put 4 new icons on that bottom part but I don't know how to bind the trackball. No it would not have to be disabled the trackball action as long as there is no icon pressed. So the drawar would be pulled when the trackball would be pressed only if no icon is pressed, otherwise the icon would start
Yes because aHome moves all the other icons closer together, which would require lots of work to get launcher.apk to do the same.
dxtop has a 5 icon dock, and can deploy launcher by holding menu key.
What is the name of the homescreen is it TouchWiz? But when i look at the process running i see TWlauncher. Is that the same thing?
How do i change the 4 apps on the bottom withouth changing homescreen. I know it can be done with launch pro but would like to stick with the default home ap. I tried to edit but it only changes the order of the screens.
Phone is rooted
I believe this was in the sticky, but I will go ahead anyway.
If you go into the application drawer and you change how the apps are displayed, then you can edit that four apps that show in the bottom slot.
jonjacobmoon said:
I believe this was in the sticky, but I will go ahead anyway.
If you go into the application drawer and you change how the apps are displayed, then you can edit that four apps that show in the bottom slot.
Click to expand...
Click to collapse
It is thanks Jonjacobmoon
@samlot I see you only have a few posts so just so you know theres a search button that will let you search all the posts. Also the Sticky is a wealth of information.
s15274n did a great job compiling all this information please use it.