THIS WAS POSTED IN THE skyrocket forum but since we share the same problem I post this here as well .
Part A_
1_ On the GNOTE 's Gallery a Simple hack to allow full size of 'wallpaper'
here it is : http://www.mediafire.com/?84yb70al1fewdhk
there is a known bug you need to select portrait size then you can reselect the landscape size
Using the Intl NOte's Gallery is bug free and allows that feature.
(not sure if this gallery will work well for the skyrocket users )
(but I dont think its needed either if you guys need a modified gallery I will post how to modify it also )
Part B_
_framework.jar\smali\android\service\wallpaper\WallpaperService$Engine.smali
find :
method doOffsetsChanged()V
then
find :
Code:
.line 735
const/high16 v1, 0x3f00
.line 736
.local v1, xOffset:F
const/4 v2, 0x0
.line 737
.local v2, yOffset:F
const/4 v3, 0x0
.line 738
.local v3, xOffsetStep:F
const/4 v4, 0x0
.line 739
.local v4, yOffsetStep:F
:try_start_0
iget-boolean v9, p0, Landroid/service/wallpaper/WallpaperService$Engine;->mPendingSync:Z
replace with
Code:
.line 735
:try_start_0
iget v1, p0, Landroid/service/wallpaper/WallpaperService$Engine;->mPendingXOffset:F
.line 736
.local v1, xOffset:F
iget v2, p0, Landroid/service/wallpaper/WallpaperService$Engine;->mPendingYOffset:F
.line 737
.local v2, yOffset:F
iget v3, p0, Landroid/service/wallpaper/WallpaperService$Engine;->mPendingXOffsetStep:F
.line 738
.local v3, xOffsetStep:F
iget v4, p0, Landroid/service/wallpaper/WallpaperService$Engine;->mPendingYOffsetStep:F
.line 739
.local v4, yOffsetStep:F
iget-boolean v9, p0, Landroid/service/wallpaper/WallpaperService$Engine;->mPendingSync:Z
note that the line numbers might not be the same .
if you use this in your rom please mention my name somewhere
a simple thanks goes a long way a coffee even further
I will continue to help as much as I can. We have a skyrocket and note so i am trying to pinpoint what exactly is different side by side
I'm not home right now, but I pulled the TW Launcher from the Captivate KK4 2.3.5 update. The dpi was all off, of course, but scrolling worked.
Also, I decompiled Launcher Pro as well since scrolling works on that launcher.
As soon as I'm back in front of a computer I can upload them for reference, if needed.
I am pretty sure onky 2.3.6 has the issue on the skyrocket
(scrolling works fine on ours.. 2.3.5)
Will upload files asap
Sent from my SAMSUNG-SGH-I717 using XDA App
heads up its fixed
DAGr8 said:
heads up its fixed
Click to expand...
Click to collapse
Nice work, incredible.
Send it over if you want someone to test it.
EDIT: and what was the solution?
EDIT 2: Saw your other post. Nice find DAGr8.
lactardjosh said:
Nice work, incredible.
Send it over if you want someone to test it.
EDIT: and what was the solution?
Click to expand...
Click to collapse
very easy
OP updated .
i shodul have comsidered looking at the intl note but I didnt believe they had it working .
I tried the bravia engine mod for the intl note this morning (that actually works on our phone) and noticed the intl note's gallery had the landscape feature for the wallpaper , so I went straight for it .
Sweeeet
Now i can move on to the Next items on my list. ...bluetooth reconnect (though mine is working fine now i think)
Sound issues
Top notch man I knew someone more experienced could find the solution! It would have taken me weeks
Sent from my SAMSUNG-SGH-I717 using XDA App
DAGr8, are your changes backwards?
My framework.jar has the smali code you're saying to change it to already.
Just out of curiosity, what's the procedure for recompiling and recompiling stuff like that? I do non-android related Java coding, so I know crap about androids internals, but I'd love to take a hacking surgical knife to things someday.
lactardjosh said:
DAGr8, are your changes backwards?
My framework.jar has the smali code you're saying to change it to already.
Click to expand...
Click to collapse
rofl yes they are . I edited it now
Dagr8,
I replace the Galary3D with the stock one and set permission. Restarted the phone but i still don't find the option for portrait or landscape mode when choosing wallpaper as my S2. Did i miss any step?
Thanks
sweetboy02125 said:
Dagr8,
I replace the Galary3D with the stock one and set permission. Restarted the phone but i still don't find the option for portrait or landscape mode when choosing wallpaper as my S2. Did i miss any step?
Thanks
Click to expand...
Click to collapse
im confused a bit here , you have askyrocket right ?
and what gallery were you using prior to this one ?
you shoudl use the 2.3.5 gallery ,
Face Of Boe said:
Just out of curiosity, what's the procedure for recompiling and recompiling stuff like that? I do non-android related Java coding, so I know crap about androids internals, but I'd love to take a hacking surgical knife to things someday.
Click to expand...
Click to collapse
Man, I'm with you bro. I'm almost done with my Network Security degree, and sometimes I think I should have gone for programing instead, but I think is easier to find a job on Networking. A little direction on how to get things started would be nice, so DAGr8 wouldn't have to do all the job by himself.
Thanks for all your awesome job.
Sent from my SAMSUNG-SGH-I717 using xda premium
DAGr8 said:
im confused a bit here , you have askyrocket right ?
and what gallery were you using prior to this one ?
you shoudl use the 2.3.5 gallery ,
Click to expand...
Click to collapse
No i don't have the skyrocket. Now i'm confused. I thought just replace the file you provide(option A) in Mediafire to the stock Galary3D Note to be able to enable to choose scrolling wallpaper.
sweetboy02125 said:
No i don't have the skyrocket. Now i'm confused. I thought just replace the file you provide(option A) in Mediafire to the stock Galary3D Note to be able to enable to choose scrolling wallpaper.
Click to expand...
Click to collapse
no the fix is much more 'complex' . requires framewokr.jar edits , you can flash my rom its built in now . all the gallery allowed you to do is to have a landscape wallpaper instead .
sweetboy02125 said:
Dagr8,
I replace the Galary3D with the stock one and set permission. Restarted the phone but i still don't find the option for portrait or landscape mode when choosing wallpaper as my S2. Did i miss any step?
Thanks
Click to expand...
Click to collapse
see the part I put in bold ? thats why I thought you had an s2
DAGr8 said:
no the fix is much more 'complex' . requires framewokr.jar edits , you can flash my rom its built in now . all the gallery allowed you to do is to have a landscape wallpaper instead .
see the part I put in bold ? thats why I thought you had an s2
Click to expand...
Click to collapse
hahah Got it. Yes i do have the ATT S2 2.3.4 and it has the option to choose portrait/landscape. Misunderstood bro...
****x76 said:
Man, I'm with you bro. I'm almost done with my Network Security degree, and sometimes I think I should have gone for programing instead, but I think is easier to find a job on Networking. A little direction on how to get things started would be nice, so DAGr8 wouldn't have to do all the job by himself.
Thanks for all your awesome job.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
What I did to pull it and do the edits was to adb pull /system/framework/framework.jar then edited the lines in a text editor, then just adb pushed <location of edited file> (to) /system/framework/framework.jar
Hope it helps
EDIT::::
This is what I did, figure I'd explain on it.. adb pull /system/framework/framework.jar
That pulled it into my android platform-tools.
then I had to decompile the framework .jar I used the android apk tool to decompile it by in cmd (file location of the android apk tool) apktool d framework.jar ./out
which made a file called out. out>smali>android>service>wallpaper then find WallpaperService$Engine.smali
I edited the .smali in notepad.. Follow Da_g's OP to edit the lines. (For me the lines were the same as his, but may not be for you).
after you've edited it, save it then you have to recompile it.
back to cmd; apktool b -f -d out it'll recomplie it all to out>dist> framework.jar
then you need to adb push the framework back to system/framework/framework.jar
for me i used root explorer to make the /system R/W its quicker for me then doing it in adb shell.
Hope it helps those confused and I mean no disrespect to Da_g for positing this, just hope this would save some time for those that dont know how to do it.
And Da_g, if I posted this in the wrong place, Sorry, just let me know and I'll remove it.
Excellent!
dkirchik said:
What I did to pull it and do the edits was to adb pull /system/framework/framework.jar then edited the lines in a text editor, then just adb pushed <location of edited file> (to) /system/framework/framework.jar
Hope it helps
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I717 using XDA App
Dagr8...just a heads up...the skyrocket gallery already allows for lanscape and portrait. ..and scrolling has not been an issue
Again..it may be a 2.3.5 vs 2.3.6 issue but our skyrocket does both with no modifications needed
Sent from my SAMSUNG-SGH-I717 using XDA App
Related
How do you change the "Personalize" button on the rosie launcher to another function?
For example, how could I set it up to launch a browser or some other program?
Thanks
-Scott
there is a thread in themes and apps that has it, not on a comp right now otherwise i would give you a direct link, but its called remapped rosies, and it has browser, MMS, camera, etc.
just head over and i'm sure you'll find it.
hope this helps!
oh btw you need to be rooted and on a deodexed rom for it to work.
FaithCry said:
there is a thread in themes and apps that has it, not on a comp right now otherwise i would give you a direct link, but its called remapped rosies, and it has browser, MMS, camera, etc.
just head over and i'm sure you'll find it.
hope this helps!
oh btw you need to be rooted and on a deodexed rom for it to work.
Click to expand...
Click to collapse
Thanks, but I am looking for the actual code that you modify so I can make the changes my self.
scrosler said:
Thanks, but I am looking for the actual code that you modify so I can make the changes my self.
Click to expand...
Click to collapse
just take the a file of his thread, and a clean systemUI.apk from a 2.3.3 rom and make a diff of both files.
Thats teh way i've done this.
j4n87 said:
just take the a file of his thread, and a clean systemUI.apk from a 2.3.3 rom and make a diff of both files.
Thats teh way i've done this.
Click to expand...
Click to collapse
Yeah, thats what I am doing now....
Its actually rosie.apk but I know what you mean....
scrosler said:
Yeah, thats what I am doing now....
Its actually rosie.apk but I know what you mean....
Click to expand...
Click to collapse
oh, yeah sry, rosie.apk for sure.
If you need help, just ask
Ok, here is what I did...
I downloaded a Rosie.apk that uses Launchkey because I figured it would be in easy string to search for and it was....
I found this @ \smali\com\htc\launcher\Launcher.smali
Code:
.line 5538
new-instance v2, Landroid/content/ComponentName;
const-string v3, "com.beansoft.launchkey"
const-string v4, "com.beansoft.launchkey.Redirect"
invoke-direct {v2, v3, v4}, Landroid/content/ComponentName;-><init>(Ljava/lang/String;Ljava/lang/String;)V
invoke-virtual {v1, v2}, Landroid/content/Intent;->setComponent(Landroid/content/ComponentName;)Landroid/content/Intent;
Now, I figured it would be as simple as searching for the similar strings in an unmodified roise in the same file but I keep pulling up blanks.
I know I am close... but I dont get it....
I just want to take the unmodified rosie and give it that function instead of pulling up personalize...
Any thoughts?
I am in the same boat. Hopefully if you get this down, please share. Thanks!
Gonna quote most of SteelH's [How To] post opener:
This reference guide is to tell you what to edit to disable Geo-Tagging by default for the EVO 4G LTE in Camera.apk. It is not an all-inclusive how-to on adb, decompiling/recompiling apks, etc. There are already several very good sources right here on XDA for that information. This can manually be turned off/on by the user, but this is intended for rom developers who want it off by default.
Decompile Camera.apk and look for \com\android\camera\DisplayDevice.smali:
Code:
.method public static isDisplayGPSindicator()Z
.registers 1
.prologue
.line 1110
const/4 v0, 0x[COLOR="Red"]1[/COLOR]
return v0
.end method
Change const/4 v0, 0x1 To const/4 v0, 0x0
Final Should Look Like:
Code:
.method public static isDisplayGPSindicator()Z
.registers 1
.prologue
.line 1110
const/4 v0, 0x[COLOR="Red"]0[/COLOR]
return v0
.end method
For the convenience of the community, I have attached 2 zips (Odex & Deodex - v. 1.13.651.1) with the modifications already in place. Also includes 'Shutter Sound Toggle.'
What exactly is the point of this? Wouldn't it just be easier to toggle it off? Unless this was cooked into a rom.
husker91 said:
What exactly is the point of this? Wouldn't it just be easier to toggle it off? Unless this was cooked into a rom.
Click to expand...
Click to collapse
Rydah805 said:
This can manually be turned off/on by the user, but this is intended for rom developers who want it off by default.
Click to expand...
Click to collapse
lol
fachadick said:
lol
Click to expand...
Click to collapse
Ahh I do seem to have missed that part of the post haha
husker91 said:
Ahh I do seem to have missed that part of the post haha
Click to expand...
Click to collapse
It's all good though!
I was trying to find a way to have the LED notifications keep flashing even after I turned the screen on as I have a flip cover and never see them otherwise. I couldn't find a solution online so figured I'd try to do it myself. My solution seems to work so I thought I'd share.
First you will need a deodexed ROM. I'm using a deodexed version of the Stock Australian Optus ROM.
1. Decompile services.jar (found in /system/framework) with APKTool or similar.
2. Edit the NotificationManagerService.smali found in android\server as follows;
Find the lines
iget-boolean v5, p0, Lcom/android/server/NotificationManagerService;->mScreenOn:Z
if-eqz v5, :cond_43
and change the if line to
goto :cond_43
** cond_43 may have a different number, change as needed.
3. Recompile and push the new services.jar
4. Reboot into recovery and wipe the cache
5. That's it!
Hope that helps someone looking for the same solution I was.
Sent from my GT-N7105 using xda app-developers app
you can also do this with this app light flow available in play store. this has an option for led notification will continue flashing when the screen is on. however root is mandatory.
Thanks vsinha71 but Light Flow has some issues on the note 2 where activating it also activates the talk back.
Sent from my GT-N7105 using xda app-developers app
Has there been a fix for this yet on VZW? Someone in the sprint forum has made a fix for the auto-correct and also made it so it takes less time for the sticky keys.
They didn't make a fix, they are using the updated keyboard or had an ota to fix it.
adrynalyne said:
They didn't make a fix, they are using the updated keyboard or had an ota to fix it.
Click to expand...
Click to collapse
eclipxe said:
Hey all, this is my first mod, but it was driving me crazy that the stock samsung keyboard didn't support auto-correct - and the timeout delay was way too long.
I'm working on an auto-patcher in the next couple of days.
EDIT:
I attached the APK: /system/app/
Make sure to set the proper permissions, then reboot.
The code changed is below
Here's a first stab at fixing both, would love some feedback.
1. To change the long press delay
In PointerTracker:
Code:
###################################################
# Change the long press delay to 200ms from 500ms #
###################################################
.line 498
const/16 v0, 0xc8
.line 499
.local v0, delay:I
packed-switch p1, :pswitch_data_0
.line 504
const/16 v0, 0xc8
.line 507
:goto_0
int-to-long v1, v0
return-wide v1
.line 501
:pswitch_0
const/16 v0, 0xc8
2. To add auto-correct
In SwiftkeyQwertyLatinInputModule
Code:
.line 312
:cond_3
##################################################
# Add support for auto-correct on word separator #
##################################################
#check if the user has entered text
iget-object v7, p0, Lcom/diotek/ime/framework/input/AbstractInputModule;->mComposing:Ljava/lang/StringBuilder;
invoke-virtual {v7}, Ljava/lang/StringBuilder;->length()I
move-result v7
if-lez v7, :cond_10
iget-object v7, p0, Lcom/diotek/ime/framework/input/AbstractInputModule;->mEngineManager:Lcom/diotek/ime/framework/engine/InputEngineManager;
iget-object v8, p0, Lcom/diotek/ime/framework/input/AbstractInputModule;->mComposing:Ljava/lang/StringBuilder;
invoke-interface {v7, v8, v9}, Lcom/diotek/ime/framework/engine/InputEngineManager;->getCharSequence(Ljava/lang/StringBuilder;I)I
invoke-virtual {p0}, Lcom/diotek/ime/framework/input/SwiftkeyQwertyLatinInputModule;->updateSuggestion()V
invoke-virtual {p0}, Lcom/diotek/ime/framework/input/SwiftkeyQwertyLatinInputModule;->setComposingText()V
##################################################
# End support for auto-correct on word separator #
##################################################
#move clearCandidateList from beginning of processWordSeparator to after we do correct
:cond_10
invoke-virtual {p0}, Lcom/diotek/ime/framework/input/SwiftkeyQwertyLatinInputModule;->clearCandidateList()V
#code below is not changed - just for reference
iget-object v7, p0, Lcom/diotek/ime/framework/input/AbstractInputModule;->mEngineManager:Lcom/diotek/ime/framework/engine/InputEngineManager;
iget-object v8, p0, Lcom/diotek/ime/framework/input/AbstractInputModule;->mCandidates:Ljava/util/ArrayList;
invoke-interface {v7, v8}, Lcom/diotek/ime/framework/engine/InputEngineManager;->getSuggestion(Ljava/util/ArrayList;)I
.line 313
Click to expand...
Click to collapse
So this is an updated keyboard?
+1
If we can get autocorrect working on the Sammy keyboard I would be a happy camper. It is the only thing that prevents me from using it (and jumping between swiftkey and thumb keyboard).
I stand corrected. But it is fixed in the updated keyboard, yes.
adrynalyne said:
I stand corrected. But it is fixed in the updated keyboard, yes.
Click to expand...
Click to collapse
Why would this crash on a deodexed VZW/AT&T rom? It doesn't seem like the keyboard would have anything to do with the carrier. The APK is just for the keyboard too, which is also weird
I just posted the VZW version of the APK (from CleanRom 4.0.5 ACE) in the hopes that he can modify it too. Not sure why they are carrier specific.
spiff72 said:
I just posted the VZW version of the APK (from CleanRom 4.0.5 ACE) in the hopes that he can modify it too. Not sure why they are carrier specific.
Click to expand...
Click to collapse
You should quote the guy i posted in my post. The work looks practically done since he tells you exactly how to do it. I"m pretty sure just needs to be tweaked a bit to work with VZW, but have no clue.
I installed the APK from that other thread on my system, even tried going to a dif nandroid backup of a different deodexed rom, both times the keyboard fails to load up (it is just a black square like normal, with no keys) and it FC
kimdoocheol said:
Why would this crash on a deodexed VZW/AT&T rom? It doesn't seem like the keyboard would have anything to do with the carrier. The APK is just for the keyboard too, which is also weird
Click to expand...
Click to collapse
There are libs needed as well.
I didn't really have time to get the 4.1.2 keyboard working, so I did this for you guys.
adrynalyne said:
I didn't really have time to get the 4.1.2 keyboard working, so I did this for you guys.
Click to expand...
Click to collapse
Thanks, are we supposed to flash this? I tried flashing it and my keyboard won't even slide up/FC.
I tried changing it to APK and no go either.
kimdoocheol said:
Thanks, are we supposed to flash this? I tried flashing it and my keyboard won't even slide up/FC.
I tried changing it to APK and no go either.
Click to expand...
Click to collapse
Yes it is to be flashed.
I don't support other people's roms so if you are on clean rom sorry. I only tested this with a Verizon rom and it does work.
adrynalyne said:
Yes it is to be flashed.
I don't support other people's roms so if you are on clean rom sorry. I only tested this with a Verizon rom and it does work.
Click to expand...
Click to collapse
that is what I figured, i was looking inside and am guessing you need to be odexed?
Thanks though for your effort, you should post in in the themes and apps section. i think a lot of people would like something like this
hopefully someone can port it to CleanROM later then....
Isn't cleanrom based off of 4.1.2? Doesn't 4.1.2 have the fix from Samsung???
would this patch work with beanstown? it's based off stock verizon
jblist90 said:
would this patch work with beanstown? it's based off stock verizon
Click to expand...
Click to collapse
It should.
adrynalyne said:
Isn't cleanrom based off of 4.1.2? Doesn't 4.1.2 have the fix from Samsung???
Click to expand...
Click to collapse
Nope. Running this ROM and the Sammy KB will show the assumed correct word in blue in the middle of the suggestion row, but if you press space, it just inserts what you typed (even when the suggested word is the word that really is correct). I don't know if this is operator error on my part, but this is the same thing it was doing when I was stock unrooted.
adrynalyne said:
Isn't cleanrom based off of 4.1.2? Doesn't 4.1.2 have the fix from Samsung???
Click to expand...
Click to collapse
Nope, sadly. adrnyalyne, did you post in the other thread about the less time for sticky keys, or did you just fix the autocorrect?
spiff72 said:
Nope. Running this ROM and the Sammy KB will show the assumed correct word in blue in the middle of the suggestion row, but if you press space, it just inserts what you typed (even when the suggested word is the word that really is correct). I don't know if this is operator error on my part, but this is the same thing it was doing when I was stock unrooted.
Click to expand...
Click to collapse
You are right. Go into the settings for the SS keyboard and you will see that it gives you the Swift Key option as to what space bar is SUPPOSED to do. I have mine ticked to replace the word, but it doesn't do that. I have also tried unticking it and same result. it really sucks.
Confirmed working with auto correct on beans
adrynalyne said:
It should.
Click to expand...
Click to collapse
JBeXX said:
Confirmed working with auto correct on beans
Click to expand...
Click to collapse
I can also confirm it works! This was prob the only flaw I had with this phone, thanks!
Adrynalyne...would you mind if Beans incorporated this into his Rom?
EDIT:
Turns out, at least on Cleanrom based on 4.1.2, using the Xposed per-app dpi settings module, the "Freestyle Windows Mode" (thanks to BlackBass595 for finding this name) a.k.a (I think) Cascade View can be enabled by setting Android System to a resolution of 600x1024 or higher. No need to change dpi (can leave at 0, which is default) if you don't want to (Thanks to Gahh Its Lee who spent some time testing this to determine this).
**This will not work with TouchWiz as your launcher, as it force closes with any change in resolution or dpi** (Apex, Nova, etc. all are fine)
If you're on Cleanrom ACE and want to try:
Install the Xposed Framework app from here.
http://forum.xda-developers.com/showthread.php?t=1574401
Grab the Xposed App Settings and install:
http://www.villainrom.co.uk/forum/microdownloads/xposed-app-settings.5/viewfile
Run the Xposed Framework Installer, choose "install/update".
Navigate to the "Modules" tab and check off Xposed App Settings to activate the module.
Reboot.
Open Xposed App Settings in app drawer, select Android System. Turn per-app settings on with the toggle, set resolution to 600x1024 or higher and save. Reboot.
Cheers.
______________________________________________________________________________________________
OP:
Using Cleanrom ACE and Xposed framework to run per-app dpi settings, not sure if the latter makes any difference.
The first of the 2 apps I drag into multiwindow often, but not always, let's me "pin" and resize it. I can't figure out why it isn't an option for all apps? If anyone can shed some light on how this works I'd appreciate it.
It's a really cool feature, used it to "pin" and reduce the size of Xbox smartglass remote so I could control the Xbox while still having most of my phone screen operating as normal.
Sent from my SCH-I605 using xda app-developers app
Bump.
Do I just suck at search (I tried) or does no-one know what I'm talking about?
I can't find anything about this anywhere, except that it was supposed to be an upcoming feature in the Verizon LTE Galaxy Note 10.1 - which is why I was surprised to see it in 4.1.2 which CleanROM ACE is based on.
EDIT:
So, I definitely suck a *little* bit as searching. This thing is called "Cascade View" and someone was asking about it in the AT&T forums:
http://forum.xda-developers.com/showthread.php?t=2093306
But at least no one in that thread seemed aware that it is in fact an available feature (guy was on Cleanrom also).
Feature is detailed by Samsung in:
http://developer.samsung.com/s-pen-sdk/technical-docs-09
Still would love to know how to get all of my apps to work as free windows if anybody knows.
Never knew about this..I would like to know how to do this as well
Jaybenosa said:
Never knew about this..I would like to know how to do this as well
Click to expand...
Click to collapse
Edited OP with info for trying this out yourself. I didn't notice this when on Jelly Beans (4.1.1) so I think it's 4.1.2 only.
Great find! Just got it working. Set 240DPI with 1024x600 layout for Android System and SystemUI. Looks great, and made an amazing phone ever more amazing. Thanks!
this is really cool.
do you always have to drag two windows into multiwindow, pin one of the apps, and then exit the other app to get this to work? it would be a lot more useful if i could just pin directly from multiwindow without having to drag two apps.
kimdoocheol said:
this is really cool.
do you always have to drag two windows into multiwindow, pin one of the apps, and then exit the other app to get this to work? it would be a lot more useful if i could just pin directly from multiwindow without having to drag two apps.
Click to expand...
Click to collapse
Unfortunately yes, for now. I'm hoping someone out there figures out how to port over the multi window dock from the Samsung tablets as they have button toggles for launching apps as a free window or in split view. I thought there might be a flashbarservice.apk that coukd simply be replaced but sadly it wasn't so simple.
If I ever find or see that someone else has figured out a way, I'll update here.
Sent from my SCH-I605 using xda app-developers app
Also worth noting is this doesn't work with touch wiz launcher.
blackbass595 said:
Also worth noting is this doesn't work with touch wiz launcher.
Click to expand...
Click to collapse
Thanks, added that to the OP. Too bad that didn't work for you though.
So, I tried grabbing a 10.1 rom to see if I could bring over some stuff and inject it into Cleanrom, but didn't have much luck as I don't know what all the dependencies are for multiwindow. Maybe if I spent enough time, but there might be an easier way.
I think the best solution would be to modify flashbarservice.apk so that it launches apps in freestyle and pinnable window mode by default. I decompiled the apk and dug around the smalis but I can't make heads or tails of it. Each line of code seems to do so little, and I can't find one where I can set "FREE_STYLE" or "FREE_AND_PINUP_STYLE" as a modifier for the launch intent, rather than "SPLIT_ZONE_A" or "SPLIT_ZONE_B" which it must default to. The Samsung SDK also keeps referencing SMultiWindowManager which I don't see a trace of.
No idea. Maybe something that actually knows something about coding apps could figure it out. It'd be really awesome to open up the apps in the window mode, just like a computer. There's even a button to maximize them to full screen lol.
tarheeldan said:
Thanks, added that to the OP. Too bad that didn't work for you though.
So, I tried grabbing a 10.1 rom to see if I could bring over some stuff and inject it into Cleanrom, but didn't have much luck as I don't know what all the dependencies are for multiwindow. Maybe if I spent enough time, but there might be an easier way.
I think the best solution would be to modify flashbarservice.apk so that it launches apps in freestyle and pinnable window mode by default. I decompiled the apk and dug around the smalis but I can't make heads or tails of it. Each line of code seems to do so little, and I can't find one where I can set "FREE_STYLE" or "FREE_AND_PINUP_STYLE" as a modifier for the launch intent, rather than "SPLIT_ZONE_A" or "SPLIT_ZONE_B" which it must default to. The Samsung SDK also keeps referencing SMultiWindowManager which I don't see a trace of.
No idea. Maybe something that actually knows something about coding apps could figure it out. It'd be really awesome to open up the apps in the window mode, just like a computer. There's even a button to maximize them to full screen lol.
Click to expand...
Click to collapse
Easy... Look for the smali code that says "use this for freestyle in other roms" ...you're welcome. Lol
I noticed that sometimes I could get the the pin to appear by swiping down at the very top of the window.
Sent from my unlocked & underclocked Galaxy Note 2
sleevasteve said:
I noticed that sometimes I could get the the pin to appear by swiping down at the very top of the window.
Sent from my unlocked & underclocked Galaxy Note 2
Click to expand...
Click to collapse
Interesting. I tried, I can't seem to get it to work with my clumsy fingers though.
blackbass595 said:
Easy... Look for the smali code that says "use this for freestyle in other roms" ...you're welcome. Lol
Click to expand...
Click to collapse
LOL. I wish!
I got Eclipse and the ADT package and tried my hand at messing with the smalis. The AppListWindow and CenterBarWindow both have lines with what I'm looking for but I don't know enough about what the code does to know what to change. Plus, when I tried exporting the APK from Eclipse and loading it on the phone it force closed so I don't think I even know how to re-compile it properly.
There's no references to the resizeable window mode in CenterBarWindow.smali, only the split zone:
_________________________________________________________________________________________________________
.line 739
move-object/from16 v0, p0
iget v12, v0, Lcom/sec/android/app/FlashBarService/CenterBarWindow;->mFocusZoneInfo:I
sget v13, Landroid/sec/multiwindow/Constants$WindowManagerPolicy;->WINDOW_MODE_OPTION_SPLIT_ZONE_A:I
if-ne v12, v13, :cond_0
_________________________________________________________________________________________________________
In AppListWindow though, the resizeable window option is referenced:
__________________________________________________________________________________________________________
line 352
.local v2, taskInfo:Landroid/app/ActivityManager$RunningTaskInfo;
iget v4, v2, Landroid/app/ActivityManager$RunningTaskInfo;->windowMode:I
sget v5, Landroid/sec/multiwindow/Constants$WindowManagerPolicy;->WINDOW_MODE_OPTION_COMMON_RESIZE:I
and-int/2addr v4, v5
if-eqz v4, :cond_1
__________________________________________________________________________________________________________