If you have some spare 5 min, could you please test?
Download (just 90kB) to sd/Lightning Launcher, apply (with merge! to not harm your current setup), take a screenshot, remove desktop added.
Please send screenshot and comment.
Thanks a lot in advance.
Originally shared by Lutz Linke
Please test: demo templates for my ZW-scaling suggestion (https://plus.google.com/+LutzLinke/posts/4UVqKs9Etut).
Pierre Hébert and all others:
I created a demo page with some Zooper Widgets on 720×1280, 320dpi and exported as template (just 96kB). This template loaded on different screen will result in incorrectly scaled ZWs (see attached screens).
So I created a few patched templates that should scale correctly directly after applying for the following devices or resolutions:
720×1280 Nexus4
768×1280 Nexus4
800×1280 213dpi, i.e. AsusPad MemoPad 7 HD
800×1280 149dpi, i.e. Toshiba AT700 10″ Tablet
1080×1920 388dpi, i.e. Samsung Galaxy Note 3
1080×1920 424dpi, i.e. Sony Xperia Z2
1080×1920 431dpi, i.e. Samsung Galaxy S5
1080×1920 441dpi, i.e. Samsung Galaxy S4, Sony XperiaZ1
1080×1920 445dpi, i.e. Nexus5
1200×1920 324dpi, i.e. Nexus7(2013)
1440×2560 538dpi, i.e. LG G3
You can download them here:
https://app.box.com/s/hdj5buwi3quqt89rwql9
You can merge to test and delete that desktop afterwards.
Formulas used are a bit different (see LLTemplateScale_V2.xlsx):
preset_widgetwidth >> x Ratio Width
preset_widgetheight >> x Ratio Height
pref_widget_scale >> x 1/Ratio DPI
preset_dpiheight >> x Ratio Height/Ratio DPI
preset_dpiwidth >> x Ratio Width/Ratio DPI
If you own a device listed above (or a similar device with matching resolution and dpi), could you please test, do a screenshot and send it to me and Pierre?
Thanks for your help!!
D5 Creation
< ![CDATA[
What about my “old” Samsung Galaxy S2?
But i am not a programmer or dev. Is this possible? If so, which info do you need?
It has480×800 Pixel, 218 ppi
]]>
< ![CDATA[
But we need to have zooper right?
]]>
< ![CDATA[
TrianguloY Uhm, yes, that’s the point. LL items themselves are scaled properly. But ZWs aren’t when restoring.
]]>
< ![CDATA[
Roger Schreuders Good point. Give me a few minutes, will add.
]]>
< ![CDATA[
Roger Schreuders Test template for S3 added, hope I did it right, bit in a hurry (am cooking in parallel): Template_ZW_480x800_218dpi_S3.zip
]]>
< ![CDATA[
TrianguloY Here’s the original thread for more info what these test templates are for: https://plus.google.com/+LutzLinke/posts/4UVqKs9Etut
]]>
< ![CDATA[
I know I know, I saw that post.
I just wanted to confirm. I don’t have zooper so I didn’t want to try until know if it were really necessary.
]]>
< ![CDATA[
TrianguloY Perhaps it also works with ZW free… I mean… The free version does not support templates, but in this case data of widgets already created is just restored. Did not try, but might work.
]]>
< ![CDATA[
Lutz Linke just a small correction. It’s S2 not S3. The rest ist ok. I try it and make a screenshot. Cool thanks.
]]>
< ![CDATA[
So Lutz wjat your saying is ypur Zooper wodgets arent scaled properly when ypu restore?..ive never had that problem
]]>
< ![CDATA[
Screenshot on mine S2. Looks somehow different.
https://www.dropbox.com/s/i0vsc1k99cca3s8/screen_20140810_1614.jpg
]]>
< ![CDATA[
Roger Schreuders Strange. Maybe I made a mistake in calculation, was in a hurry, will check.
]]>
< ![CDATA[
Jeff Ludlow When loading template in ZW, ZW recalculates scaling.
But widgets in LL template when restored on different device are not rescaled and (depending on target devices resolution and dpi) look more or less wrong. This is what in my theory could be fixed.
]]>
< ![CDATA[
Lutz Linke ah ok..so if i have an S3 and you a Nexus 5 with diff resolutions my template would be distorted on yours,the scaling
]]>
< ![CDATA[
Jeff Ludlow Exactly. Just try. The Nexus 4 is my original (despite I changed resolution to 720×1280). Import that and it’s wrong. Then the one patched for device and ZWs should be scaled properly (as good as possible, i.e. if ratio is different).
Will check that S2 template soon (about 1h) and add one for S3 (close to Nexus 4, but I think other DPI).
]]>
< ![CDATA[
Screenshot from my N7(2012). Used MemoPad 7 HD template.
https://www.dropbox.com/s/t5indbarvtvqcv3/Screenshot_2014-08-10-11-33-15.png
]]>
< ![CDATA[
Unfortunately you need zooper widget pro.
With the free version don’t work
🙁 sorry
]]>
< ![CDATA[
TrianguloY Right, in template file in “core/pages/0/items” the widget provider is “org.zooper.zwpro/org.zooper.zwlib.provider.WidgetProvider4x1”. Could possibly also be patched…
]]>
< ![CDATA[
Thanks Cory Moddelmog ! That looks good.
]]>
< ![CDATA[
Roger Schreuders seems in a hurry I patched incorrectly. Uploaded corrected templates for S2 and S3:
Template_ZW_480x800_218dpi_S2.zip
Template_ZW_720x1280_306dpi_S3.zip
]]>
< ![CDATA[
Well here we go. The first screens its only the template. Second screen i merged your template to ma desktop without the background. The third screen i touched the widget’s and zooper corrected them. Is this a correct behaviour?
https://www.dropbox.com/sh/lc3oxs6wuwehwno/AADekh0NfIPlY9gcaK5iUvS4a
It is the S2 template.
]]>
< ![CDATA[
Roger Schreuders Thanks a lot. No, this is not correct. The scaling correction-factor seems wrong 🙁 Just tested myself with old HTC Wildfire (240×320, 120dpi), to have a bigger difference in screen sizes. My tablet and phone are too similar.
I’m on it.
]]>
< ![CDATA[
Thank you guys for testing, helped a lot. The issue is the scaling factor. Simulated S2 on my tablet, scaling is merely about 90 instead of 150 as I calculated. Dpi and resolution do not seem to be the main/only factors but also ratio. Have some ideas, but need to think and sleep it over.
]]>
< ![CDATA[
I am a little confused about my S2. The speciation says it has 218 ppi see here:
http://de.m.wikipedia.org/wiki/Samsung_Galaxy_S_II
But my build.prop says 240 dpi. See screenshot:
https://www.dropbox.com/s/h3j0mn9ad8hwwzi/screen_20140811_1348.jpg
Which one is correct?
]]>
< ![CDATA[
Using the exact dpi may not be the right thing to do: Android devices are classified in dpi classes, even if this is an approximation. What about using the nearest dpi class instead of using the raw dpi value ? (list of classes can be found here: http://developer.android.com/reference/android/util/DisplayMetrics.html)
]]>
< ![CDATA[
Pierre Hébert Does not apply to my approach to patch the ZW’s data when restoring the template. I determined 5 values (preset_widgetwidth, preset_widgetheight, pref_widget_scale, preset_dpiwidth, preset_dpiheight) in the ZW widget data’s preset.json that needs to be adjusted based on exact dpi and resolution (those you already store in manifest for LL’s scaling: screenDensity, screenWidth, screenHeight).
The values stored there are based on the device the LL template was exported on, but propably won’t match on different device. That “awful hack” as you called it would adjust these values and the ZWs restored from LL template would immediately match when restoring.
From the tests the guys here posted I found my “pref_widget_scale” calculation was utterly wrong. Spent some hours last night on various tests and think I found the factors to apply. Will update the test templates this evening and post again. Worked on various resolutions and dpi’s I simulated on my tablet (Nomon’s Resolution Changer is GOLD!).
Would be awesome if you could (once the correct formulas found) implement that on-the-fly patching when restoring ZW widgets’ data. Shouldn’t be to hard, presets are just JSON-strings. Think “perfect scaling when loading LL template for EVERYTHING”!!
]]>
< ![CDATA[
You can please stop testing, the templates are not correct. Update and new post coming up this evening (in about 6h).
]]>
< ![CDATA[
After lots of testing, I just created and uploaded a new set of test templates. Please continue here: https://plus.google.com/106201536507820539535/posts/8Th6wjyShzB
]]>