Anybody know why Ive got the litle blue box with a ? in the middle of the screen?.... doing it on both my phone 4 with 4.1 and my gf's 3gs with 4.1?
thanks
this is my first time.... sorry so ive gotta save the wallpaper pack and send it ssh?
has anyone seen a decrease in battery life with the use of this theme?
I've noticed this also. I JUST turned off the background, going back to my default black background. I assume the bright backgrounds of slanted are the cause.
I won't know until later if that's the cause or something else about the theme. Also try raising your weather refresh time, I have it at 240 so it doesn't refresh the data till then. But I changed that a week ago, so I know that's not the cause.
Hehe... I honestly don't believe SlantedLock uses any more battery than any other lockscreen theme out there. In fact, in its locked state, I am pretty confident in claiming that it uses LESS battery than any other similar locksceen out there. I inspected lots of other themes and I know my time calculation cuts down a lot of excess operations.
The only time it performs a few more operation [and this is being VERY nit picky down to the technicality here... So nit picky I'm referring to individual lines of operation code...] would be loading the configurations from the local database, but this only occurs when you lock your phone, which I don't think is something you do too frequently to have any impact... if this has any impact at all... Further more on the nit picky tech talk, we CAN go back to the old method of configureme.js... but IMO, the possibility of the configuration screen via Safari FAR out weighs the usefulness of that miniscule performance boost that only benefits when you lock your phone.(again, if that performance boost is significant enough for any impact)
As for the random wallpaper. That happens once every hour. And it's literally less than 10 lines of code to load a local image onto screen. 24 times in a day.
Other than what I have just described to be unique to SlantedLock, other lockscreen themes does the same thing one way or another.
Think: SlantedLock = TypoPhone + WeatherFurik + [optimized]
Very thorough description Claude heh. And interesting facts, I wasn't aware this was so optimized in comparison to the others. Though I was thinking about it only checking on lock, and I do use BiteSMS, and text quiet often. Could this be causing repeated checks responding at the lockscreen?
As for the wallpaper, I just assumed it was the bright wallpapers :O, am I just being a tad paranoid with that? As I do like the wallpapers heh. Oh, and I thank you for your work on this, I get constant comments on how awesome it looks >_>b.
Sorry, I don't mean to sound conceeded and by no means is SlantedLock super duper awesomeness optimized, but I do believe it's at least on equal footing in power use and I try my best to optimize.(and I conclude this based on seeing and comparing what functions/codes are being used) In fact, there were complaints that the time would not load immediately when you hit the home button... I'm aware of that, but I think it's because of how time is being calculated... and I decided that the cut down on instructions far out weighs the half second delay, so I'm going to stick with this approach for now until i figure something out that's better.
I have had people think that some of the features SlantedLock has that they've never seen before(like the config screen) is a potential for power drain. xD It's not. Unless you open up safari to use it... then you'd be running Safari.
The brightness of the wallpaper has nothing to do with the battery use(at least I believe so). The thing that sucks battery, the back light, is still getting the same power at the brightness level you set.
As for using LockInfo and BiteSMS quick reply... You're still on the lockscreen, so SlantedLock is not doing anything special other than tick the time. It only does its thing when you lock your phone going from the home screen. And... when it's time to update your weather, then it will run through a series of internet connectivity to fetch new weather data... assuming u have internet, if not, it simply uses cached data and waits for the next update time.
yep its repeatable. becomes slow and sluggish after a minute or so
I've had to stop using this lockscreen because of this issue. I'm in and out of data areas too often and the phone becomes practically unusable. Real pity cos I loved it!
I've had to stop using this lockscreen because of this issue. I'm in and out of data areas too often and the phone becomes practically unusable. Real pity cos I loved it!
luckily for me im always next to a home wifi or i have network coverage
I've had to stop using this lockscreen because of this issue. I'm in and out of data areas too often and the phone becomes practically unusable. Real pity cos I loved it!
Claude,
Thanks for the great work you've done/are doing. Such a beautiful lock screen.
Just wondering if you could tell me where/how "day" is being defined. It seems that at night time (midnight, for example), the weather icon being displayed is the "day" icon, as it shows a sun with clouds over it ("foggy"), instead of a moon with clouds over it ("foggy_night). I've tried all icon sets, to no avail.
Thanks for the help!
The icons are not determined by my script. It's determined by the weather code that it receives from the weather source. If you look in one of the weather js files... you will see the icon name and the weather code associated with it. As some previous users have noticed, the icon sets seem to be very lacking in variety and many icons are repeated/reuse. I've decided NOT to alter this list match up simply because there seems to be a standard to these weather icons. Thus, if I were to make a single set of very detailed icon sets... it would work, but... if someone were to download an icon set from somewhere else and try to use it, it would not have the required files and will appear broken. In short... SlantedLock appears broken because I had wished to keep it consistent with the icon sets already available around the web. I had left the match up in the script easily modifiable for users to tweak at their own use.![]()