yashsingh1/xdaforums huggingface dataset:
[Windows Mobile Development and Hacking General] temparoo:
TNT Pro v4.0 & Slide 2 UnLock

I am using TNT Pro v4.0 ROM and Slide 2 UnLock works perfectly fine. I average on 20MB free RAM. I also have many programs installed and the Today screen is full too! :)
[Windows Mobile Development and Hacking General] Mr Groch:
Hi!

I have 3 problems with current release:

- Square after operator name (Screen.jpg)

- Some weird slider behaviour when sliding (Screen.jpg)

- Top windows bar disapears after closing Slider app (only soft reset works, becouse top bar is not only invisible - it is real gone) (Screen2.jpg)

Thx for you work, this is the best solution for us, WM6 VGA users - I'm hoping on you ;)
[Windows Mobile Development and Hacking General] LlamaV3:
1. I've got that too, probably easy to fix.

2. I've got a fix for that (see my last post), will probably be done tonight or tomorrow.

3. I get this too, to be honest I don't understand why this app is going into full screen the way it's being done, I can think of more simple ways. Will look at code while doing the fix for number 2.
[Windows Mobile Development and Hacking General] chrismrulz:
1. I didn't realize that, that's correct that a fix would be easy (once i work out what's causing it).

2. Can't wait to get this fixed! Hope you can get it working in my project (latest one has been uploaded). If you send me the source I could have a go implementing it in.

I've just your exe on my hx4700 and it works perfectly :)

3. I should be able to fix this too.. but that was pretty much the only way i was able to get it fullscreen (it's hard to do in cf.net).

If i can just make it go back afterwards it will be good.

It also disables the hardware buttons (except power) too which would be better if it can be taken off afterwards.

Try to get no.2 fixed first as it's alot harder to do than this.

The good thing is that i was aware of these bugs already and there aren't other bugs on all the different platforms.

also @ Mr Grotch, you might wanna try installing the iPhone font included. (copy iPhone.ttf to your windows fonts directory and soft-reset.) even though the app isn't quite fixed yet.

and out of curiosity, did you need to use the VGAPATCH version?
[Windows Mobile Development and Hacking General] LlamaV3:
I'm giving this a go now. by the way can you keep including fsengine.vb in the source package, I keep having to dig it out from old zips to be able to compile ;)
[Windows Mobile Development and Hacking General] chrismrulz:
i stopped using it a while ago though. i removed the library from the executable as it would just be pointlessly using up space and ram by including it.

unless you were enabling the code i had commented out?

btw, just decompiled your exe to have a look at the code :P

that shouldn't be too hard to implement. really hope you can do it though. (i'm wanting to use the slider app for myself too)
[Windows Mobile Development and Hacking General] LlamaV3:
Everything is in and great, unfortunately the transparency on the slider is causing me problems and I'm working around it at the minute. If it is a normal picturebox then everything is great, if it's the expanded picturebox class you're using then it doesn't leave a trail but it flickers. My solution is to provide a second buffer just for the slider, but inside the pictureboxex control. I have an annoying feeling that the background paint function in that control is going to cause me problems too.

While I was in the code I've fixed the taskbar problem. The program didn't call the showtaskbar stuff on close, so I put that call before both of the Application.exit calls and it works as it should. Also put my code in to stop the clock timer while the slider is sliding back, and restart the timer when the slider is "home" because it messes up the slide. Also fixed a new bug I found where if you moved the slider and went to touch it again it would keep sliding, now you can catch it again, move it, then it will resume sliding when you release.

I should have the finished product in about 2-3 hours, if all goes well.
[Windows Mobile Development and Hacking General] LlamaV3:
fixed the odd character at the end of the operator name label.

If (opname <> "" And opname <> "0") Then

carriername = Replace(opname, Chr(0), "")

End If
[Windows Mobile Development and Hacking General] LlamaV3:
Here's what I have so far, just leaving work and have a busy evening ahead.

I might work on it more tomorrow, but let me know how it runs on your device, I've been running it on a qvga orbit, and I have no idea what the performance will be on a vga device. The buffering might be too severe for our needs, and buffering a 640x480 screen might be overkill. I want to change the way the whole form refreshes and try to manage it all in one function, hopefully just buffering the slider portion of the screen.

Let me know what you think, I've tried to comment as much as possible on it, and I seem to have fixed the bugs mentioned so far. Might have created some more too. I've put a little seconds counter (just a flashing dot) next to the time because I like it on my device ;) and it let me know the time was still working and hadn't frozen.
[Windows Mobile Development and Hacking General] chrismrulz:
oh thanks, didn't know what the char number was and i dont have a smartphone to test it. you might need to change it to a trimend() though, just incase there should be any situation the carrier name might need to have that character in it (not including the bug).

it's looking good so far.

a few things though,

the refreshing of that icon next to the time makes it have to update the image every time the timer ticks, which flashes the image and makes it worse performance.

that needs to go back to how i had it which was updating the images only when it was needed (usually once every minute).

the FSEngine class shouldn't be included.

nothing references it anymore, as i used a whole new api for making it fullscreen.

having it included is just a waste of space and performance.

the me.refresh() seems like it could be wasting resources drawing everything twice. cos it gets drawn, then drawn again at me.refresh.

the good thing though is all the problems that you fixed.

haven't tested the buffer in vga mode yet, but running it on a vga device was still smooth.

i've just finished modifying it into my version with those first two fixes.
[Windows Mobile Development and Hacking General] LlamaV3:
yeah, that bit was just for me, and it was last minute, don't expect you to keep it ;)

it was still referenced as part of the project file, I just copied the vb file across just in case you used it, after working on the project a bit I realised you weren't using it.

The number ranges, excluding the 99 you mention, are identical to the if statements. case 85 to 89 for example is a unit of 5 (85, 86, 87, 88, 89).

yes, the idea is you have 1 graphic the size of the screen in memory, do all your drawing to that graphic in memory instead of the e graphicsargs, then when you're done just draw that big bitmap to the screen. I might split it to 2 bitmaps, 1 for the top which rarely changes, and 1 covering the slider area which will be smaller and update more frequently. As the code stands the fact that the toplock and midbar have their own paint functions wrecks it a little.

great, thanks, glad I could help, or at least clarify a few bits of the code, it was a bit of a mash up because I did it between tasks in work. btw, I think the sliding code can be improved, it shouldn't let you slide if it is out of the bounds of the sliding area, it feels a little "loose" and occasionally goes over the edge of the sliderbg by a couple of pixels.
[Windows Mobile Development and Hacking General] chrismrulz:
yeah been meaning to fix that up. just left it the way it was cos it worked.

btw, just updated source and executables with your fixes ;)

testing the vga version, the glitchy graphics on the arrow button have gone, but it still constantly flashes.

i don't think it did that when it was only qvga.

nevertheless this cuts sick on the new x50v i bought today :)
[Windows Mobile Development and Hacking General] chrismrulz:
does anyone wanna try some memory usage tests against slide2unlock now that this is at a usable state?
[Windows Mobile Development and Hacking General] mswalker:
Is there way to set Slider to automatically run when you turn the power off to the unit (like slide2unlock) so when you turn to power on, you slide the arrow to unlock the unit?
[Windows Mobile Development and Hacking General] chrismrulz:
not at the moment, but this is actually quite easy to code.

the only thing i'm tryna do is find a way to make it not eat up any resources in the background to be able to do that.

it's definitely on the list of things to do though.
[Windows Mobile Development and Hacking General] Mr Groch:
Thx, it is now working really great (with VGA patch), but still

slide button flickers when draging or when it comes back to start...

This isn't a big problem, but problem is that even after closing

slider app, about 4 mb of RAM is gone :/ Apps like Oxios memory can

free up to 3 MB after closing slider, but still about 1MB disapears...
[Windows Mobile Development and Hacking General] tigga69:
looks great, worked first time, simple to use...

just a tiny problem!

it locks the screen but not the buttons!

any chance you can add the button lock functions too.

thanks
[Windows Mobile Development and Hacking General] chrismrulz:
the latest version should lock all buttons except power.

btw what device you running it on?
[Windows Mobile Development and Hacking General] tigga69:
trinity (orange m700)

mun rom wm6 - indigo version

thanks

ps - i should add on the trinity the date is about 2 points too small. but i should know what day it is!
[Windows Mobile Development and Hacking General] chrismrulz:
if you turn cleartype on and install the iphone fonts it should be the same size as on the iphone. (and look a whole lot better)
[Windows Mobile Development and Hacking General] LlamaV3:
yup, I noticed last night that something isn't being disposed properly on exit. it might be worth writing a function to manually dispose all objects/bitmaps etc on the form before calling exit. it looks like it's having a problem due to the same thing that caused the toolbar to stay hidden, anything after that exit call isn't being run, so much for .net being able to manage itself.
[Windows Mobile Development and Hacking General] Avatar28:
I just installed this little app this weekend after getting tired of Slide2Unlock's memory usage.

I may have found a bit of a problem. I activated the slider on my phone last night (after assigning it to a HW button for activation). I then didn't use the phone for a few hours. When I turned it back on I found that Slider was no longer running. My phone was also down to about 4.5 MB of RAM. Using both Oxios apps I was finally able to get it up to about 7 or 8 MB but the rest refused to come back, requiring a soft reset to resolve it.

Anyways, I can't be sure if the issue is my ROM or Slider, as I also just installed the ROM on Friday night, but I hadn't noticed the memory leak before that really so I wanted to bring it up.
[Windows Mobile Development and Hacking General] evermick:
nice work. Hope it will get full feature same as slider 2 unlock (indicator of miss calls / messages / SMS / Wifi / bluetooth etc and also Caller ID).

Please also add a feature to start this little slider automatically when idle or suspended
[Windows Mobile Development and Hacking General] chrismrulz:
the two issues mentioned above are known and are near top priority.

i desperately need some help coding all this though as it's alot of work. (i.e. llamav3 :P)

it does what the iphone unlocking app does at the moment though, so it's come a long way already from 11 days. (only about 1 hour a day spent coding)
[Windows Mobile Development and Hacking General] LlamaV3:
I've had a look at the newest code, the clock and slideani are still anabled while the slider is moving, this still causes huge problems for my sliding smoothness (200mhz processor) so I have put my slideani.stopanimation and clock.enabled=false stuff back in while it is moving.

I've also created a big alldispose function in, which I hope catches most memory leaks, usually images that are locked into the paint event. I do a check for appclosing = false before the onpaint events, if the app is closing then it doesn't run the paint events, so the files arent in use. it runs this function before exiting the program to clean up some controls:

Private Sub alldispose()
appclosing = True
SlideAni.StopAnimation()
SlideAni.Dispose()
SliderBG.Dispose()
Background.Dispose()
BatteryStatus.Dispose()
BottomBar.Dispose()
MidBar.Dispose()
SignalStrength.Dispose()
SliderButton.Dispose()
TopLock.Dispose()
Clock.Dispose()
Me.Dispose()
GC.Collect()
GC.WaitForPendingFinalizers()
End Sub

the buffering is still being buggered up by the transparency routine, I'm rewriting the graphics from ground up using opennetcf similar to this, but that could take me ages:

http://blog.opennetcf.org/afeinman/PermaLink,guid,8fb585db-bd44-42fe-afa9-07b116c6d2ba.aspx
[Windows Mobile Development and Hacking General] chrismrulz:
about the slider still moving, it might be slow for some devices (testing it on my 3 ppcs didn't make a difference if it was on or off, except that the slider animation got much faster), but in the end it should still be moving so it's still like the iphone.

we just need to figure out how to stop the timers interacting with each other (you'd think .net already does this).

about the dispose functions, was thinking the same thing..

just a few questions about it though,

1. do we know we have everything disposed? (variables could be disposed too i think)

2. do we know if the code you have there doesn't cause any problems? (me.dispose being the form, could create problems when doing the other exit routines, etc.)

3. do we know if the code you have there improves memory issue?

no. 2 and 3 would need to be checked before changing it to the current code. (by the way, the owner of freewareppc found this and listed it so it's getting quite alot of downloaders now, so we better not make mistakes)
[Windows Mobile Development and Hacking General] LlamaV3:
I had this code running on my p3300 and it didn't cause any errors. as long as you do the check for the appclosing variable when painting, otherwise it tries to paint images you've just disposed.

give it a go and you will see. a good way to look at it is that it isn't going to make the memory problem worse.

I think you misunderstand the timer issue. my problem is that the slider moves, that is fine, but the smooth sliding motion stutters whenever the timer ticks, when the timer is disabled while sliding then everything is smooth. what spec are your pdas because mine is only 200mhz o\c to 264mhz. I'll try and record a video of my sliding motion for you later but it is a lot better if you set

clock.enabled = false

slideani.stopanimation()

slidebutton.bringtofront()

on slidebutton mousedown

and then clock.enabled=true

slideani.startanimation()

slidebutton.bringtofront()

when the slider is back at the default location on the left.
[Windows Mobile Development and Hacking General] chrismrulz:
yeah i can notice the stutter on some slow pdas.

there's issues with all the timers including the animation one.

some speed up when others start and some speed down. it varies on the speed of the processor.

but simply stopping the animation and clock on the slideback doesn't really solve the issue, and it means the time will be out of sync while you're dragging the slider and the animation wont keep going like it does on the iphone.

about the memory fix, that's good that it doesn't cause errors now we just need to know if it makes it use less memory.

mainly because if it doesn't fix the memory bug, it only means it'll take longer to shut down with no cause.

all the stuff i've added so far i've tested to make sure it actually makes it better.

i.e. only fix something if it's broke and what you're trying to do will fix it, or else we'll have to find out later from the people reporting bugs.
[Windows Mobile Development and Hacking General] LlamaV3:
it doesnt alter the fact that the iphone uses a 620mhz processor with its own built in animation routines. it makes it difficult to replicate on a pda using gdi.I'll look into a non timer method for you, might be difficult but I've used other techniques in opengl windows apps to do this (reading the system millisecond counter during the paint function).

i experienced this memory bug, close down this slider and bang 4mb of memory have disappeared. The only thing in the program I could think of was that it wasn't releasing the bitmaps that were loaded, this code releases those bitmaps before closing. This was because the paint routine uses the bitmaps all the time, and it runs even while closing. try the code yourself and see what you think, I believe I've at least 90% fixed something that was broke.
[Windows Mobile Development and Hacking General] chrismrulz:
yeah but A_C can do it with slide2unlock with gapi, which isn't all that superior to gdi.

and 620mhz isn't really needed to move a bitmap and show a little animation.

if your 200mhz processor can render webpages with animated gif's and javascript (or heck they even run snes emulators), surely it could do this.

about reading the system millisecond, just remember that it will reset after 999 so there needs to be a function keeping track of the last number and doing some conditionals.

and again, we need to check if it improves on what is on there now. especially as it'd be adding alot more code so if it doesn't fix it it would only be worse.

yeah i understand that should work to fix it.

just want to be sure. like have you actually tested it and seen the results?

i would test it out myself but my sd cards and rom are almost full and don't know where to find the free memory usage testing apps.

edit: i just tried checking free system memory before using it and it was 34.64. after using it, it only went down to 34.54. checking memory usage with memmaid (found i had it installed) showed no drop in memory at all. (??)

i think .net must be doing it's job properly in WM6 or something.. but either way sorry but it looks like i have no way of testing if it will fix anything so it's up to you guys.

edit2: just tested it the same way using the 2003SE device emulator and it went from 7.94 to 7.93..
[Windows Mobile Development and Hacking General] chrismrulz:
ok i've just updated it with llamav3's disposeall function and uploaded it.

testing it the same way as before (memory info dialog in settings, and memmaid),

it showed to actually increase the memory usage after exiting on mine by 100kb (don't know how this is even possible, probably due to something else).

but if i simply release a different version here on the 13th page, there might not be as many people downloading it and it would take a long time to be tested.

it shouldn't be that bad if it doesn't work anyway so we might aswell give it a go.

if the current version turns out worse i can change it back (just could be a little problem as i have so many versions of the slider source on my harddrive that it's sometimes hard to find which one does which).
[Windows Mobile Development and Hacking General] LlamaV3:
have you done this test with the previous version? I would be very interested, also what is your code for recording available memory?
[Windows Mobile Development and Hacking General] chrismrulz:
yeah i mentioned it in the second-last post.

on my axim x50v running wm6 (i can test on my hx4700 but it is also wm6), i did a soft reset and opened up file explorer and navigated to my iphone dir.

then i opened up settings > memory and looked at the free memory / used memory and wrote them down.

i then opened up my app with file explorer and closed it.

then went back to the memory dialog and compared it to what i wrote down from before.

it showed 100kb loss of memory using my old one,

then i did the exact same procedure with yours and it came out as 200kb loss of memory. (i'm thinking this could be todo with other apps though as i don't see how your code could add much to memory, maybe a trickle of cpu time though)

i used the latest version of memmaid aswell and it showed no changes in memory with either (after pressing refresh).

also tried using wm2003se with device emulator which showed 10kb loss of memory (with mine).

as all of these cases were different to what others have reported with 4mb drops in memory, i've uploaded it anyway to see what happens.

it seems the .net framework disposes memory differently across platforms or something..

but anyway, it worked without causing any problems so it's worth a shot.

just gotta get this new version decided on before i go on to do lots more coding cos it could take a while changing all the code later.

on another note, using memmaid to check it's memory usage while it was running said it was 1.27mb :O
[Windows Mobile Development and Hacking General] poan:
Hello

An exelent software.

Running perfect on a S100 (magacian)

But. explain for a newby: How to install. I have to tap the .exe file from file manager.

How to create a shortcut or an automatic start.

P-O
[Windows Mobile Development and Hacking General] chrismrulz:
using file explorer find the Slider.exe and hold down on it until a menu comes up with 'Copy'.

Click copy and go to where you want the shortcut to go and instead of clicking paste, click paste shortcut.

if you want it to go on the start menu, go to \windows\start menu\ and paste the shortcut there.

for coming on when you first startup the device (i think that's what you were saying), paste it at \windows\startup\.

if you meant coming up when you wake the device, i have to program that though. which needs this memory issue resolved first before i can go on to that.
[Windows Mobile Development and Hacking General] LlamaV3:
when this is done we are just going to have to close the app instead of exit it, then when it is run again get the app to just show instead of reopen. will mean a quick start but the app will constantly run in the background at the 1mb or so that you mentioned. still better than 5mb that s2u uses.
[Windows Mobile Development and Hacking General] chrismrulz:
yeah was thinking about that, and would be the easiest todo (simple me.hide() might even do the trick),

but another idea would be to make another simple app coded in native c++ that opens the slider app on the onwake event and waits for the slider to exit etc.

meaning probably only about 10kb used at most while it's using the slider app.

although it would mean 10kb ontop of the slider app's memory when it is being used but it's a much better trade-off.

i for one probably wouldn't like the idea of my 1mb app running in the background, possibly even trying to do those animations and stuff, when i wanna get good performance to run fullscreen games etc..

but a simple 10kb app monitoring for the device to wake from standby could be quite practical.

think this is what A_C has done with the ilock.exe but not too sure as it won't even run on my pocketpc to try it out.

of course this is gonna be harder to code though, but it should be worth it.

if you think there can be a sure way to make it all-in-one and put the current slider app into a suspended state and dispose of everything in memory (would def. have to properly test ram usage this time),

that could be an even better idea. but it'd definitely have to make sure the suspending routine works.
[Windows Mobile Development and Hacking General] LlamaV3:
I've actually used this slider with a_cs ilock.exe, just renamed the slider.exe and it worked. However I would like the slider to always run because it takes too long to load when you want the screen to lock. I might press the standby button on the side of the phone, and when I press it again everything is unlocked because I'm waiting for slider.exe to start. the best solution would be an option, the same way a_c has done it. you can choose if the program uses me.hide or exit