I'm working on a tool I'm calling "applytheme". Basically you create a theme.zip, stick it in an archive with the included applytheme binary and update-script, sign it, and it will update the files on any of the Dream firmwares with the ones you've provided.
There are some limitations currently:
It can't yet determine space required before-hand, so you may run out of space in the middle. If you do, you can just restore the original theme with the restoration update.zip.
It can't add files - only replace existing ones.
The original files are stored in /data/original_theme.zip, which will eat your /data space, but only the replaced files are stored.
This version is a test release and may or may not have bugs. Be sure to back up your phone before trying it.
Please consult the example for figuring out what to put in the theme.zip, but it's basically full-path-to-filename-you-want-to-update/full-path-to-file-you-want-to-replace
So if you wanted to replace "assets/images/android_320x480.png" (the boot screen) in "/system/framework/framework-res.apk", you would have a file in your theme.zip called "system/framework/framework-res.apk/assets/images/android_320x480.png".
Case matters - please use the correct case (which is usually all lowercase).
Example theme (replaces boot animation only, with a cupcakedroid):
applytheme-200902090018-example.zip
Restoration update.zip (restores from /data/original_theme.zip then deletes original_theme.zip):
theme_restore-200902090018.zip
Source code (for developers or other curious people):
applytheme-200902090018.tar.gz
EDIT: 200902082117 fixes a couple of stupid bugs in 200902081755 :/
EDIT: 200902082316 removed extraneous/incorrect free space check; noticed that the update script stuff is significantly more stupid than I'd thought - update scripts should work now.
EDIT: 200902090018 close files so space can be reclaimed during patching
Reporting problems
If one of the applytheme updates fails, while still in the recovery mode please do the following:
Press ALT+X to get to the console
Press <enter> to get to the prompt
Type cp /cache/recovery/log /sdcard/recovery.txt
Type df >> /sdcard/recovery.txt
Type reboot to reboot.
Send the recovery.txt from the SD card to zinx <AT> users.sourceforge.net with the subject "applytheme error log"
If I don't have the log (or at least the error message from the log), I can't know why it's failing, and can't do anything to fix it.
I am looking at your post but don't see the benefits of doing it like this. you would still need to do this every time you add a theme or just a image and you still need to sign it or am I just not seeing the benefits of using it
kron2 said:
I am looking at your post but don't see the benefits of doing it like this. you would still need to do this every time you add a theme or just a image and you still need to sign it or am I just not seeing the benefits of using it
Click to expand...
Click to collapse
Current themes replace the whole system.
If you change as single file in /system/app/Browser.apk (say, an icon), you have to replace the whole file.
You don't have to do that with applytheme, so you can replace the icon no matter what firmware is being run.
This would be great themes wont need to be converted any more.
manup456 said:
This would be great themes wont need to be converted any more.
Click to expand...
Click to collapse
Indeed, for example:
More Vintage Less War via applytheme (theme by manup456 )
EDIT: Oh, I should note I tested this one with RC33. Didn't bother to time the progress meter though, so just wait until it tells you to reboot with home+back.
This looks like an amazing tool! I'm surprised more people haven't checked this out.
Let me get a few things straight before I give it a shot.
Let's say I was updating some basic images in the framework-res.apk. All I need to do is:
~Download your applytheme-example.zip
~Open up the theme.zip (remove current folders inside)
~Create the folders system\framework\framework-res.apk\res\drawable\
~Add the icons I've changed, with the exact original names
~rename applytheme-example.zip to update.zip
~load onto SD card and load onto phone as usual
~success?
I don't quite understand the backup system...
When you load the update onto the phone, it backs up the images you're replacing and puts them into a \data\original_theme.zip?
Then, if for some reason you want to revert to the original theme, you simply run the theme.restore.zip on the phone and it grabs all the \data\original_theme.zip images and places them in their original location?
Also, if the theme you're installing is a few megs, then the \data\original_theme.zip will get rather large, no? Will this cause any issues?
Thanks!
The steps are a bit more like this:
Download applytheme-example.zip
create system/framework/framework-res.apk/res/drawable/
add the files you've changed
create a theme.zip with the files above - MAKE SURE IT HAS THE PATH, STARTING WITH system/
replace the theme/theme.zip in applytheme-example.zip with your new theme.zip
sign the applytheme-example.zip with the replaced theme/theme.zip
put it on the SD card as /sdcard/update.zip and update as normal
success! (unless there was a problem during patching, then it may be partially applied and you can use theme_restore.zip to fix it)
MOONSSPOON said:
When you load the update onto the phone, it backs up the images you're replacing and puts them into a \data\original_theme.zip?
Then, if for some reason you want to revert to the original theme, you simply run the theme.restore.zip on the phone and it grabs all the \data\original_theme.zip images and places them in their original location?
Click to expand...
Click to collapse
Yep.
MOONSSPOON said:
Also, if the theme you're installing is a few megs, then the \data\original_theme.zip will get rather large, no? Will this cause any issues?
Click to expand...
Click to collapse
It can get large, yes, but keep in mind that it's only the original files that have changed that get put in it. Most themes right now are much larger .zips than they actually are, because they include much more than what was changed. If it gets too large to fit, the update will just fail part-way, and you can restore using the theme_restore.zip.
You can also delete it if you don't want to restore.
If you have any better ideas for any of this, I'm definitely open to suggestion - It's not anywhere near finalized yet
Great work. Definitely a step in the right direction for generalizing themes and allowing them to work with any build without modification.
Some thoughts for the next steps... Perhaps do a once-over of the files in theme.zip and compare their sizes with the existing files? This would just about double the time it takes to install, but should catch any out-of-space issues before any replacements had been made. Alternatively, perhaps there's a way to detect failures and automatically revert and display an error?
MasterBunnyFu said:
Great work. Definitely a step in the right direction for generalizing themes and allowing them to work with any build without modification.
Some thoughts for the next steps... Perhaps do a once-over of the files in theme.zip and compare their sizes with the existing files? This would just about double the time it takes to install, but should catch any out-of-space issues before any replacements had been made. Alternatively, perhaps there's a way to detect failures and automatically revert and display an error?
Click to expand...
Click to collapse
Automatic reversion can be done.
The update stuff is too stupid to let me display an error (Seriously. There's no way to display a message to the user. All I get is the unchangeable 'Failed on line 3'.) - an error is kept in /cache/recovery/log though.
Checking the file sizes would indeed take twice as long - everything is compressed, so I'd basically be creating every file touched, but discarding the output, then creating it all again. It already takes quite some time, and it should normally have enough space free, so I would prefer to go the automatic reversion route if people don't want to have to use the theme_restore.zip after a partial update.
So I tried throwing in your more vintage theme, but I get the error failed on line 4.
I feel like a leecher posting this message, but explain to me how it's done.
APrinceAmongMen said:
So I tried throwing in your more vintage theme, but I get the error failed on line 4.
I feel like a leecher posting this message, but explain to me how it's done.
Click to expand...
Click to collapse
Should just be putting in it; can you post the /cache/recovery/log from after it fails? May need to copy it somewhere before rebooting.
I expect it's due to lack of space, but it was ok here :x
In an effort to make it a bit easier initially, I've written "toapplytheme". It takes a theme update, the update it was based on, and outputs an applytheme compatible theme.zip - You still have to put in in theme/theme.zip in the applytheme update zip and re-sign it, though.
If you use something other than the update it was based on, you're going to end up with a lot of extra and/or missing files, so don't do it.
Ex:
Code:
toat MyExcellentTheme.zip JFv1.41_RC33_light2.zip theme.zip
toat-200902091613.zip
Worked for me
I have an ADP1 w/the latest JFv1.43h, I extracted Rusty Metal (from the RC33 version, using you tool). Put it there on the example, signed it all and voila...
The only thing I noticed is that the background did not get changed, but that is a minimal issue (and easily fixed).
Great job Zinx, I don't understand why all theme designers don't use this tool.
A matter of time I hope?
DanOtero said:
I have an ADP1 w/the latest JFv1.43h, I extracted Rusty Metal (from the RC33 version, using you tool). Put it there on the example, signed it all and voila...
The only thing I noticed is that the background did not get changed, but that is a minimal issue (and easily fixed).
Click to expand...
Click to collapse
I just applied Rusty Metal to my G1 using the standard way (not this tool) and the background doesn't install with it anyways, so it's not a problem with this tool, but the theme itself simply doesn't include it.
I searched as best I could, but couldn't find a match to this particular issue.
I do have a rather weird issue with Gallery3D, that I've noticed after switching to OpenDesire, in 4.0.10 and 4.0.15.
Until recently I have been using various Sense based ROMs, where photos taken with the phone are stored in DCIM/100MEDIA and I always just used HTC's gallery app.
Now I'm on OpenDesire 4.0.15, which stores phone photos in DCIM/Camera, and uses Gallery3D to display them.
The thing is, when I try to display photos from DCIM/100MEDIA, taken earlier on various sense ROMs, Gallery3D shows some completely random photos instead. The thumbnails in 100MEDIA display correctly, but when I tap any thumbnail, it expands to the grainy fullscreen version, and is then replaced with a sharp and refined version of *another* picture.
It shows photos that I have taken with this same handset, but imported to my computer and deleted from the phone long ago. That is, photos that aren't even *on* the SD card anymore.
I have tried the following:
1. settings > apps > manage > Gallery3D > force stop + wipe data and settings
reboot
no luck
2. rename 100MEDIA to something else.
repeat 1.
no luck
3. Create new folder DCIM/Test
Copy files from DCIM/100MEDIA to DCIM/Test
The copies in DCIM/Test work well.
Hm.
4. factory reset, wipe cache + dalvik
reflash OpenDesire (4.0.15)
no luck
5. Made a flashable zip with most recent Gallery3D.apk from this thread and flashed it over the one included in OpenDesire 4.0.15
No luck (yes the update succeded, different file size )
Ok, fine, so I kind of solved the problem in attempt number 3, right? Well, yeah, except that I'm uncomfortable about my phone magically raising photos from the dead that I've deleted long ago.
Have you guys got any ideas or input?
Well, your deleted pictures aren't exactly "dead", they just aren't in the master file table of your SD once you hit delete, but they can definetly read. But to avoid going offtopic, you can simply back up your files, format the SD card and restore the files. Everything should be ok.
As to why this happened, it's possible that your Master File Table got corrupted somehow (or Android's MediaManager isn't reading it correctly). But I can't really say much since it's difficult to tell what the real cause is (perhaps you didn't "safely remove"?).
Either way, reformatting should help. And keep using Gallery3D from that post, it's one of the best around
Reason
Even i experienced the same issue,,but couldn't find the solution,,,,but i figured out why it is happening..!!
My gallery 3d app was showing the images i took long back which are no more in the SDcard..!!!how can it be possible..??
The reason is,,
>When we delete the file in the sd card,,the operating system will just mark that that memory location with some special character ,,in fact the data will appears to be deleted but truly i won't ...!!
>when we add new files to the file system that space will be overwritten ,,,by the new file...!!
>So in our case the file which appears as the thumbnail is in exact same memory lactation as the old deleted image....so the thumbnails will be stored in different location as the cache,,,,,
>this is the reason why it show the thumbnail but when we click on that,,, it shows the original data resides there....!!
> its just a bug in the Gallery app
>And it will happen only when we delete the files inside the gallery app...
>Next time try to delete the files in Some file managers like Astro
@xperiacle found a way to enable Real Floating Multi Windows on the Galaxy Note, and thanks to @THEDEVIOUS1 this mod came to our Grand.
I've tested it extensively and it works fine, look at the screenshots below.
THEDEVIOUS1 is too busy right now to make a thread about it, so he allowed me to make one here for my fellow Grand's users:laugh:
I've improved the original SystemUi that THE DEVIOUS1 gave to me (now it's lighter and more stable) and I found a way to add a minimize button and a double tap to maximize function while in Window mode, so now one can say that we have a Full Working Floating Multi Windows Mod.
I eventually found time to make a flashable zip, no more scattered files here and there. But before you flash make sure you read the installation paragraph since there are a few pre requisites.
Two thumbs up to @xperiacle the Multi Windows pioneer, without him nothing would have been possible!
DISCLAIMER
I'm not responsible for anything that may happen to your beloved Grand:cyclops: This mod works perfectly on mine but one never knows, so make sure you have a Nandroid backup in case.
INSTALLATION
It's pretty simple, but you must be rooted, and probably deodexed (I'm not sure on that one since my phone is deodexed, it may work with odexed ROMs as well).
1-Set Androidsystem's and SystemUI's DPI to 130 (it may work with other DPIs, but for sure not with 213) using app settings (link below, in the "ADDITIONAL APPS" section) or any app that can do that kind of job. In case you changed the whole phone's DPI, put it back to stock (240).
2-Set Androidsystem's resolution to 600x1024 with appsettings (it may work without this step but do it just to be on the safe side, once Floating Multi Windows have been triggered you will be able to revert it back to its default resolution if you wish so).
3-Download the attached zip, flash it in recovery, then clear cache and dalvik cache.
Reboot. The phone will boot and freeze after the Samsung logo and show a black screen, no worries, just restart one more time and you are done.
Congrats, you have Floating Resizable Multi Windows!!!
You will notice 4 icons in the notification panel, they enable 4 different view types for the windows. From left to right: cascade (minimized), dual (like the stock multi windows), triple windows, quadruple windows.
On the left there is a pin, select it to have your window to always stay on the screen and to be able to resize the window (that can be done from the bottom, the sides or the lower right corner).
Depending which phone DPI you use you may experience System UI force close, as for me I have tried with 240 (stock DPI), 220, 200, 180 and 160, it all worked (I recommend starting with stock DPI and only after you flashed the mod to try other DPIs to suit your taste). As said above I have my Androidsystem's and my SystemUI's DPI both set to 130, but it may work with other settings...
SOME MORE SETTINGS (After Flashing - Optional)
With this mod I found the flashbar being of not much use because it can't be triggered anymore (that's because the com.sec.feature.multiwindow.phone.xml has been deleted). No worries, this bar had never proven very useful anyway, I use Side Bar instead (very little RAM hungry) and so I deleted the FlashBarService.apk.
I deleted as well:
-minimode.jar in the /system/framework folder,
-com.sec.feature.minimode_tray.xml and com.sec.feature.flashbar.xml in the /system/etc/permissions folder.
If you don't delete the com.sec.feature.minimode_tray.xml you may have an ugly bar in the middle of your screen, so if you have it you know what to do
Note that you may not have the com.sec.feature.minimode_tray.xml anyway, it depends on which 4.1.2 version you run, some have it and some haven't.
After a lot of testing I found that setting Androidsystem's DPI to 108 or 110 suits me fine, and I put its resolution back to stock (but still, set it to 600x104 before you flash the mod, once it's done and once Floating Multi Windows are working you can change your settings). The phone is more responsive, and the bottom navigation bar gets very tiny, thus saving screen estate.
If your navigation bar doesn't display properly in landscape mode set SystemUi's resolution to 480x854.
You don't have any bottom navigation bar? You want it? Edit you build.prop and add the line:
qemu.hw.mainkeys=0
Reboot, done!
ADDITIONAL APPS
Now you have floating multi windows but not all your apps open in floating mode?
Use this module (all credits to xperiacle and rovo89):
http://forum.xda-developers.com/showthread.php?t=2304498
Wanna play with your apps DPI? Do you experience System UI force close?
Use this (all credits to tungstwenty and rovo89):
http://forum.xda-developers.com/showthread.php?t=2072081
WHAT'S NEXT?
This mod can, and hopefully will, be improved, cuz it's possible to add a minimize button in order to have apps to shrink to a small bar (like on a computer), and maybe to have a bottom minitray showing the apps and the icons.
Unfortunately it's easier said than done, so if anyone wants to give a hand to make this mode even better he, or she, is most welcome!
To have the minitray working one needs to have real Tablet UI triggered (plus some files added, I have them ready), which means that the status/notification bar won't be at the top anymore but at the bottom, and that notifications will be triggered from there (like on a Tablet). Alas, so far I didn't manage to get it working, I changed the phone's DPI to 160, 177, 200, 213, 220, 225, I used Xposed's Tablet Ui module, but without any luck.
Ok guys, that's all for now, if I get anything new be sure that I will update this post.
Enjoy your floating Multi Windows, and report here if you have any problems
UPDATE:
I managed to have the mini tray working :good:.
What is a mini tray?
It's a tray that pops up from the bottom navigation bar, and it's loaded with all your apps. It can be used as an app launcher, and apps can be launched in cascade, dual, triple or quadruple floating view from within the tray cuz it has the mini windows icons. So no need anymore to go to the top notification bar to change view, everything is at your finger tip in the bottom bar.
I will upload the required files and explain how to install them if some people are interested by this update, cuz my connection is very slow and I don't want to loose time for nothing:cyclops:. The thing is that the files are a bit heavy, like 30 mb, it may be nothing for your connection but for mine it feels like 30 gb!
Look at the 4 new screenshots below (the 4 last ones), and let me know if you are interested...
UPDATE 2
Allright, now the minimize button and the double tap to maximize work, see post 2 below
UPDATE 3
As said above I've remodded the SystemUI, now it's lighter (from 3.5 to 2.8 mb) and more stable. I've made a flashable zip with all the required files and tried it myself, it works straight away and no SystemUi force close (as long as you have followed the "INSTALLATION" chapter).
Report any problem here, and enjoy Floating Multi Windows
Minimize Button, Double Tap To Maximize
finally I managed to make work the minimize button and the double tab function.
Look at the screenshots below to get an idea, you will see that on the left of any window bar there's a minimize icon. If you press it the window shrinks to a small bar at the bottom of the screen.
The small bars disappear if you open a new app that was not skrunk yet and you have to click on one of the notification top bar Multi Windows icons to have them back, but if you open one of the shrunk windows then the others don't disappear.
Sounds confusing?
Yeah, maybe, but try, in fact it's easy. And handy
In window mode if you double tap the app bar it maximizes, quite handy too
The zip?
Above, in OP, there's only one zip mate,and it contains all the required files:silly:
If you are on 4.2.2 be patient, very soon I will upgrade my Grand and I will make this mod available for 4.2.2...:good:
will this one work on 4.2.2?
Thanks and cheers, great work buddy...
franksmj said:
will this one work on 4.2.2?
Thanks and cheers, great work buddy...
Click to expand...
Click to collapse
It has not been tested on 4.2.2 and frankly I don't think it will work since the modded System UI is for 4.1.2.
You can try though, but if you do so make sure you have a backup, or Aroma File Manager (it enables you to access your files from recovery, and in your case it would enable you to change your System UI back to stock in case the modded one doesn't work), or TWRP (same as Aroma, you can navigate through your files from recovery).
Good luck, and if it works please report here
Noo0ps not working on 4.2.2 and got system ui force closed
So frnds don't use it on 4.2.2
Sent from my GT-I9082 using xda premium
tiwari434 said:
Noo0ps not working on 4.2.2 and got system ui force closed
So frnds don't use it on 4.2.2
Sent from my GT-I9082 using xda premium
Click to expand...
Click to collapse
Does it boot? I mean you installed the modded System UI, you rebooted and then your phone booted?
Because if it boots with the modded System Ui installed it means that it's 4.2.2 compatible. The force close is not a big deal, I had the same on 4.1.2 until I found the right settings for DPI and resolution. The flashbar may interfere as well, and so may the TW Launcher (I replaced it with Holo Launcher HD, much nicer looking and more customizable).
But if it bootloops then it probably is not compatible.
unclefab said:
Does it boot? I mean you installed the modded System UI, you rebooted and then your phone booted?
Because if it boots with the modded System Ui installed it means that it's 4.2.2 compatible. The force close is not a big deal, I had the same on 4.1.2 until I found the right settings for DPI and resolution. The flashbar may interfere as well, and so may the TW Launcher (I replaced it with Holo Launcher HD, much nicer looking and more customizable).
But if it bootloops then it probably is not compatible.
Click to expand...
Click to collapse
When I deleted the stock system ui my phone rebooted automatically with not notification bar thn I paste given apk and reboot its boot up but giving continues system ui force close error
Sent from my GT-I9082 using xda premium
tiwari434 said:
When I deleted the stock system ui my phone rebooted automatically with not notification bar thn I paste given apk and reboot its boot up but giving continues system ui force close error
Sent from my GT-I9082 using xda premium
Click to expand...
Click to collapse
Did you set the perms (rw, r, r) for the app? If you didn't then it will force close. What you can do is download this:
http://forum.xda-developers.com/showthread.php?t=1646108
You put the file in your phone, you go into recovery and you install the zip. Then you will be able to access both your system and sd card files from recovery. Using the file manager you can copy and paste, and set properly the permissions, all from recovery.
If it still doesn't work it could be something with the DPI, or just that, as previously said, it's not 4.2.2 compatible.
Good luck
I've edited OP, cuz I managed to get the mini tray working.
Pretty nice to my opinion, have a look at the new screenshots in OP and let me know if you are interested...
OP edited (look at post 2), minimize button and double tap to maximize work
I have a problem i followed all the installation process but when i reboot i cannot pull down my notification shade, i cannot access my recent apps and system ui fc.
AjDoc said:
I have a problem i followed all the installation process but when i reboot i cannot pull down my notification shade, i cannot access my recent apps and system ui fc.
Click to expand...
Click to collapse
Did you clear cache and dalvik cache in recovery?
It could be the cause, but if it's not then it must be a problem with your DPI.
Did you install app settings (see additional settings in op, there's a link for tungstwenty's and rovo89's thread)?
If you did, just change android system' s and system ui's dpi to 130, and reboot.
Or, change the whole phone's DPI to either 213, 200, 177 or 160 (see which one works and is most suitable for your taste) using the ui switcher function in the attached app.
unclefab said:
Did you clear cache and dalvik cache in recovery?
It could be the cause, but if it's not then it must be a problem with your DPI.
Did you install app settings (see additional settings in op, there's a link for tungstwenty's and rovo89's thread)?
If you did, just change android system' s and system ui's dpi to 130, and reboot.
Or, change the whole phone's DPI to either 213, 200, 177 or 160 (see which one works and is most suitable for your taste) using the ui switcher function in the attached app.
Click to expand...
Click to collapse
I did not clear both cache and dalvik cache in recovery.
I tried the app settings and change both the android system's and system ui's dpi 130, and reboot but the same result.
I tried the FWC app when i change the phone's dpi and reboot the app is saying that the current DPI is still 240.
edit 1:
My bad i just saw that i need to clear both cache and dalvik cache in recovery.
edit 2:
so i cleared both cache and dalvik cache in recovery. still same result
Mmmmh, that's strange. Are you rooted and on 4.1.2 (sorry for the maybe stupid question, but some people read OPs very fast and miss some details)?
Did you delete the multi windows phone xml in the etc/permissions folder?
Check this thread, it's about the time when I was testing the mod, from message # 30 it started to work:
http://forum.xda-developers.com/showthread.php?t=2319592&page=3
Then read further message # 42, # 44 and # 46, and follow the settings order in # 46 (that's important), here:
http://forum.xda-developers.com/showthread.php?t=2319592&page=5
But instead of step 5 in # 46 just install the system ui and the etc/permissions from OP here. Reboot, it should work...
Everything I did is there. At the time I had set android system to a 600x1024 resolution and I found since that it's not needed, but you can try anyway. Let me know if it works and I'll update OP with some more instructions.
Regarding the floating windows manager, if it doesn't work (although it should, I have tested it again 5 mns ago now and changed my DPI, strange that it doesn't work with you) you can try with another DPI changer apk like ROM Toolbox or whatever from the market, there are heaps of such apps..
unclefab said:
Mmmmh, that's strange. Are you rooted and on 4.1.2 (sorry for the maybe stupid question, but some people read OPs very fast and miss some details)?
Did you delete the multi windows phone xml in the etc/permissions folder?
Check this thread, it's about the time when I was testing the mod, from message # 30 it started to work:
http://forum.xda-developers.com/showthread.php?t=2319592&page=3
Then read further message # 42, # 44 and # 46, and follow the settings order in # 46 (that's important), here:
http://forum.xda-developers.com/showthread.php?t=2319592&page=5
But instead of step 5 in # 46 just install the system ui and the etc/permissions from OP here. Reboot, it should work...
Everything I did is there. At the time I had set android system to a 600x1024 resolution and I found since that it's not needed, but you can try anyway. Let me know if it works and I'll update OP with some more instructions.
Regarding the floating windows manager, if it doesn't work (although it should, I have tested it again 5 mns ago now and changed my DPI, strange that it doesn't work with you) you can try with another DPI changer apk like ROM Toolbox or whatever from the market, there are heaps of such apps..
Click to expand...
Click to collapse
Yes i am rooted on 4.1.2, yes i did delete the multi windows phone xml in the etc/permissions folder,
Ok i will read all the message posted and try all of your suggested solutions. Will update you if it finally works, thanks for the help anyways.
edit 1:
so finally it works woo. all apps are now able to float. but there still some problems.
1. i still cannot pull down my notification shade
2. i still cannot access recent apps (or is it a part of the new system ui?).
3. and i will monitor if the system ui still fc.
edit 2:
this is my installation process please check if i made mistakes.
1. i change the android system dpi to 170 and system ui dpi to 130
2. then change android system resolution to 600x1024
3. delete com.sec.feature.multiwindow.phone.xml in system/etc/permissions.
4. i delete my stock system ui in the apps folder using root borwser then copy the new system ui in the same folder, then set the permission to RW, R, R
5. then clear cache and dalvik cache using clockworkmod recovery.
6. then reboot
the floating multiwindow works but as i said
1. i still cannot pull down my notification shade
2. i still cannot access recent apps (or is it a part of the new system ui?).
3 and system ui fc every now and then but not that often.
Cool, you are getting close!!:good:
The recent apps should work, and the sytem ui shouldn't close, so it means your DPI settings are still not optimal. The thing is that it's hard to give a general rule since it depends on one's phone. Mine is heavily skinned, permissions restricted and modified, and for this reason my settings may not work on somebody else's phone.
Androidsystem, I don't know about 170, at first i used 130 and it was fine. Then, after a lot of testing, I found out that 108 or 110 suits me fine, and I even could revert the screen resolution back to default (but then I changed it to 480x854 cuz with default resolution the navigation bar didn't display properly in landscape). The phone is more responsive (including the recent apps button, so maybe your problem comes from there), and the bottom navigation bar gets very tiny, thus saving screen estate.
If the above settings don't work then you will have to test by yourself and find the right dosis for your phone. Reading the links I gave you yesterday may help, and if it doesn't at least you will see that you are not the only one that struggled to get this mod working:cyclops:.
I struggled mate, believe me, but the result was worth the effort.
Check post # 2 in this thread, I just uploaded the new files to get minimize button and double tap to maximize...
unclefab said:
Cool, you are getting close!!:good:
The recent apps should work, and the sytem ui shouldn't close, so it means your DPI settings are still not optimal. The thing is that it's hard to give a general rule since it depends on one's phone. Mine is heavily skinned, permissions restricted and modified, and for this reason my settings may not work on somebody else's phone.
Androidsystem, I don't know about 170, at first i used 130 and it was fine. Then, after a lot of testing, I found out that 108 or 110 suits me fine, and I even could revert the screen resolution back to default (but then I changed it to 480x854 cuz with default resolution the navigation bar didn't display properly in landscape). The phone is more responsive (including the recent apps button, so maybe your problem comes from there), and the bottom navigation bar gets very tiny, thus saving screen estate.
If the above settings don't work then you will have to test by yourself and find the right dosis for your phone. Reading the links I gave you yesterday may help, and if it doesn't at least you will see that you are not the only one that struggled to get this mod working:cyclops:.
I struggled mate, believe me, but the result was worth the effort.
Check post # 2 in this thread, I just uploaded the new files to get minimize button and double tap to maximize...
Click to expand...
Click to collapse
ok i will play more with my setting and keep updating you. thanks for the help again
edit 1:
i forgot to tell you that my phone is odexed maybe it's factor why i cannot pull down the notification shade and cannot access my recent apps because i tried different dpi settings and i still cannot fix it. I'll just be patient and try a little harder.
edit 2:
from what i have observed the floating MW only works for me when the android system resolution is 600x1024 and up, and it works even when the android system's and system ui's dpi is default. Aso i cannot resize the floating MW, will try more settings to make my notification and recent apps to work.
edit 3:
Another thing i've observed is that when i unistall my mw apps manager module, not all apps can float.
Your phone behaves strangely, you can't resize windows, not all apps float, you can't pull the notification bar...
The only explanation I see is the fact that you're on an odexed Rom.
You know, deodexed Roms have many advantages, specially when it comes to customisation.
Maybe you should consider flashing one of the various deodexed Roms there are in the development thread, not only to have multi windows but to be able to better tweak your phone and to install some apps that work only on deodexed Roms like for example xprivacy.
It's easy, just download the file and flash it in recovery...
unclefab said:
Your phone behaves strangely, you can't resize windows, not all apps float, you can't pull the notification bar...
The only explanation I see is the fact that you're on an odexed Rom.
You know, deodexed Roms have many advantages, specially when it comes to customisation.
Maybe you should consider flashing one of the various deodexed Roms there are in the development thread, not only to have multi windows but to be able to better tweak your phone and to install some apps that work only on deodexed Roms like for example xprivacy.
It's easy, just download the file and flash it in recovery...
Click to expand...
Click to collapse
For now i'm having with the mod i installed some apps to act as my notification panel like floating notification and go toucher. Maybe i will install a custom rom if someone will integrate this mod on their rom like in moon rom and maybe also integrate pa's halo. But for now i will play more with the mod and maybe try that minimize button. . Thanks for the help
I'm quite busy at the moment (I didn't even find time to make a flashable zip for this mod), but when I have time I'll download 4.2.2 and I'll make a nice deodexed custom Rom including this mod. Don't expect fancy colors and bla bla effects though, my roms are fast, functional and efficient but I don't care about that kind of customization.
For now, apart from being busy the thing is that I wait for a bugless 4.2.2 to be released cuz I see many people complaining about the russian update.
Hopefully it will come soon, otherwise I'll download the russian 4.2.2 and see what it's worth...