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?
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!
After installing and playing with two 2.17.651.5 based ROM's, it's hard to give up the new base because it is so fast and efficient. That said, 2.17.651.5 changed a lot, and tweaks are limited at this point. I thought I'd share a couple of tweaks I put together that work well on the three updated Evo 3D's I have access to. I've been running these and enjoying them for a couple of days so I though others may find them useful while we wait for OC kernels and other goodies that are compatible with the new base.
BE AWARE OF WHAT THESE MODS DO BEFORE YOU INSTALL
They are designed for Evo 3D's that have had both the firmware and ROM base updated to 2.17.651.5
Even though these are simple boot tweaks, use at your own risk
New Jan 23, 2012
awakenings v0.5: WiFi scan interval now 5 min w/screen off and 1 min w/screen on for even more battery savings
As with any tweaks, please do a Nandroid backup prior to installing these. While you could just re-flash your ROM of choice to uninstall them, be safe and do a backup first.
Both of these mods can be installed over an Evo 3D 2.17.651.5 base ROM with just a cache/dalvik wipe.
awake-v05-1.2Ghz-E3D-2.17.651.5.zip
Base: 2.17.651.5 only
ROMS: Works on both odexed and deodexed 2.17.651.5 ROMs
Status: confirmed working
These are my awakenings tweaks. They activate full-time dual core operation while the screen is on and single core underclocked operation while the screen is off. Most of these tweaks have a good history in the CleanROM thread (thanks Scott) and they've been adapted to the new base. Here's the breakdown of what it does:
Dual cores online while screen is on
Single core and underclocked while screen is off
(new in 0.5) WiFi scan interval: 1 min while screen on, 5 min while screen off
CPU parameters optimized for the new base/kernel
Dimmed capacitive lights
Uses a consolidated list of tweaks, reviewed and added from other sources
Cleans out (empties) your init.d folder if you have one to avoid conflicting tweaks
init.d support is NOT required: all tweaks are in init.post_boot.sh!
To uninstall, reflash your ROM.
Performance improvements have been measured in the 2% to 12% range (depending on the benchmark). This latest base is difficult to improve upon as it is already fast, but dual core operation does reduce lag in some situations and I believe creates a smoother, snappier UI even on the 2.17.651.5 base. Please do not use these awakening tweaks on ROM's that have the old base: the CPU parameters are specifically optimized for the 2.17.651.5 ROM and kernel (for now).
cbatt-E3D-2.17.651.5.zip
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Base: 2.17.651.5 only
ROMS: Works ONLY on deodexed 2.17.651.5 ROMs
Status: confirmed working
Very cool circular battery meter with 1% increments plus text percentage. I found this battery meter here at XDA and the install script says it was created by vinchenzop. So credit to vinchenzop: I just took it and ported it into the new 2.17.651.5 base.
7-in-1-power-E3D-2.17.651.5.zip
Base: 2.17.651.5 only
ROMS: Works ONLY on deodexed 2.17.651.5 ROMs
Status: confirmed working
7-in-1 power menu w/ability to restart into recovery, bootloader, and more. Thanks to Scott from www.scottsroms.com for the file from CleanROM Reborn. I only take credit for making it flashable!
ext-QS-and-more-E3D-2.17.651.5.zip
Base: 2.17.651.5 only
ROMS: Works ONLY on deodexed 2.17.651.5 ROMs
Status: confirmed working
Thanks to mwalt2 for this. Here's a flashable version of the Extended Quick Settings mod which does the following:
Adds Media Volume, Brightness, and Auto Rotation to the Quick Settings Menu
Removes "Recent apps"
no GPS reticle
proper 3G/1x icon
Mike
__________________
Some of my other creations (mostly digital photography software):
http://www.ddisoftware.com
Good to see you start on your own
Sent from my PG86100 using Tapatalk
Extended settings
Thanks for this! I've been screwing around trying to get extended settings to run but I ain't smart enuff.....
Anyway to get them for this new base?
ozzie1p said:
Thanks for this! I've been screwing around trying to get extended settings to run but I ain't smart enuff.....
Anyway to get them for this new base?
Click to expand...
Click to collapse
Not yet. Some things that dig deeper into the UI like that are going to take time. I plan to go slow and whatever flashable stuff that I make that I think others might benefit from, I'll add them to the OP as I go.
Mike
Nice to see more mods popping up for the 3d
Nice!! DL now
Glad to see your tweaks thread Mike!
Awesome! Time the flash! thanks Mike.
Sent from XDA Premium on my EVO 3D
Will these work in the new base odexed?
Sent from my PG86100 using Tapatalk
Seems to work great so far. Just loaded it up.
Chauleyboii said:
Will these work in the new base odexed?
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Sent from my PG86100 using XDA App
Way to go Mike, running CleanRom Reborn currently. I think its about to get a little better lol
Thanks!!!
Thanks for this.
Phone's ringin', dude.
Running these with joelz/vins 3.5 warm... Running REALLY well... Thanks!
Chauleyboii said:
Will these work in the new base odexed?
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
To be honest, all my tests have been on deodexed versions but it should work fine on odexed as well.
Mike
Thank you Mike, you deserve all the credit for your hard work.
Just don't forget us at Cleanrom!
Circle Battery mod worked on odexed for me
running both tweaks on odexed version....
a ok!
Was pulling 2400s in quadrant before tweak. Pulled 2780 after! Love the battery mod.
ozzie1p said:
Thanks for this! I've been screwing around trying to get extended settings to run but I ain't smart enuff.....
Anyway to get them for this new base?
Click to expand...
Click to collapse
I've attached the mods I did to SystemUI.apk. It's stock 2.17.651.5 with GPS recticle removed, recent apps removed from pulldown, changed to display 3G/1x properly, and extended quick settings added. It's only for deodexed ROMs and you'll have to figure out how to push/copy it to /system/app (I use adb when I was testing it).
If you want to just get the extended quick settings, you just delete the following from QuickSettings.smali in SystemUI.apk (decompile with apktool).
Code:
.line 79
iget-object v2, p0, Lcom/android/systemui/statusbar/preference/QuickSettings;->mSettingItems:[Lcom/android/systemui/statusbar/preference/StatusBarPreference;
aget-object v2, v2, v7
invoke-virtual {v2, v7}, Lcom/android/systemui/statusbar/preference/StatusBarPreference;->setEnable(Z)V
.line 80
iget-object v2, p0, Lcom/android/systemui/statusbar/preference/QuickSettings;->mSettingItems:[Lcom/android/systemui/statusbar/preference/StatusBarPreference;
aget-object v2, v2, v8
invoke-virtual {v2, v7}, Lcom/android/systemui/statusbar/preference/StatusBarPreference;->setEnable(Z)V
.line 85
sget-boolean v2, Lcom/android/systemui/statusbar/StatusBarFlag;->HTC_QS_TASK_MANAGER:Z
if-nez v2, :cond_0
.line 86
iget-object v2, p0, Lcom/android/systemui/statusbar/preference/QuickSettings;->mSettingItems:[Lcom/android/systemui/statusbar/preference/StatusBarPreference;
aget-object v2, v2, v10
invoke-virtual {v2, v7}, Lcom/android/systemui/statusbar/preference/StatusBarPreference;->setEnable(Z)V
.line 92
:cond_0
iget-object v2, p0, Lcom/android/systemui/statusbar/preference/QuickSettings;->mSettingItems:[Lcom/android/systemui/statusbar/preference/StatusBarPreference;
aget-object v2, v2, v11
invoke-virtual {v2, v7}, Lcom/android/systemui/statusbar/preference/StatusBarPreference;->setEnable(Z)V
Question Would this work with anthrax r9 ? Thanks also running warm 544 thanks
Sent from my PG86100 using xda premium
@mwalt2
Damn, very nice! Thanks for that.
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
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!
Hello xda'ers,
is me again, sorry to bother but today I bring to you a famous mod from AOKP: back longpress to kill.
HOW TO:
1. we need to decompile android.policy.jar;
2. then let s edit android.policy.jar/smali/com/android/internal/policy/impl/PhoneWindowManager.smali
3. adding fields on "# instance fields" (red is what you add):
Code:
# instance fields
.field mAccelerometerDefault:I
.field mAllowAllRotations:I
.field mAllowHdmiRotation:Z
.field mAllowLockscreenWhenOn:Z
.field final mAllowSystemUiDelay:Ljava/lang/Runnable;
[COLOR="Red"].field mBackKillTimeout:Z[/COLOR]
[COLOR="Red"].field mBackLongPress:Ljava/lang/Runnable;[/COLOR]
.field mBootMsgDialog:Landroid/app/ProgressDialog;
...
.field mLockScreenTimeout:I
.field mLockScreenTimerActive:Z
[COLOR="Red"].field mLongPressBackKill:Z[/COLOR]
.field private mLongPressOnHomeBehavior:I
...
4. add a new instance in the last lines of .method public constructor <init>()V to recall our new subclass (red is what to add):
Code:
...
[COLOR="Red"] new-instance v0, Lcom/android/internal/policy/impl/PhoneWindowManager$KillConcept;
invoke-direct {v0, p0}, Lcom/android/internal/policy/impl/PhoneWindowManager$KillConcept;-><init>(Lcom/android/internal/policy/impl/PhoneWindowManager;)V
iput-object v0, p0, Lcom/android/internal/policy/impl/PhoneWindowManager;->mBackLongPress:Ljava/lang/Runnable;[/COLOR]
new-instance v0, Lcom/android/internal/policy/impl/PhoneWindowManager$25;
invoke-direct {v0, p0}, Lcom/android/internal/policy/impl/PhoneWindowManager$25;-><init>(Lcom/android/internal/policy/impl/PhoneWindowManager;)V
iput-object v0, p0, Lcom/android/internal/policy/impl/PhoneWindowManager;->mScreenLockTimeout:Ljava/lang/Runnable;
.line 5754
return-void
.end method
5. now we need to take a look in .method public interceptKeyBeforeDispatching(Landroid/view/WindowManagerPolicy$WindowState;Landroid/view/KeyEvent;I)J
Code:
:cond_13c
const/16 v39, 0x3
move/from16 v0, v21
move/from16 v1, v39
if-ne v0, v1, :cond_15a
move-object/from16 v0, p0
iget-boolean v0, v0, Lcom/android/internal/policy/impl/PhoneWindowManager;->mHomeKeyConsumedByScreenshotChord:Z
after :cond_13c we need to add some code (note: :cond_13c may be different depending on your compiler) and we will get:
Code:
:cond_13c
[COLOR="Red"] const/16 v28, 0x4
move/from16 v0, v28
move/from16 v1, v21
if-ne v1, v0, :cond_mi
if-nez v8, :cond_mi
.line 1741
and-int/lit8 v28, v11, 0x20
if-nez v28, :cond_mi
.line 1742
move-object/from16 v0, p0
iget-object v0, v0, Lcom/android/internal/policy/impl/PhoneWindowManager;->mHandler:Landroid/os/Handler;
move-object/from16 v28, v0
move-object/from16 v0, p0
iget-object v0, v0, Lcom/android/internal/policy/impl/PhoneWindowManager;->mBackLongPress:Ljava/lang/Runnable;
move-object/from16 v1, v28
invoke-virtual {v1, v0}, Landroid/os/Handler;->removeCallbacks(Ljava/lang/Runnable;)V
.line 1743
add-int/lit8 v28, v11, 0x20
move-object/from16 v0, p2
move/from16 v1, v28
invoke-static {v0, v1}, Landroid/view/KeyEvent;->changeFlags(Landroid/view/KeyEvent;I)Landroid/view/KeyEvent;
.line 1744
const/16 v28, 0x0
move/from16 v0, v28
move-object/from16 v1, p0
iput-boolean v0, v1, Lcom/android/internal/policy/impl/PhoneWindowManager;->mBackKillTimeout:Z
.line 1752
:cond_mi[/COLOR]
const/16 v39, 0x3
move/from16 v0, v21
move/from16 v1, v39
if-ne v0, v1, :cond_15a
move-object/from16 v0, p0
iget-boolean v0, v0, Lcom/android/internal/policy/impl/PhoneWindowManager;->mHomeKeyConsumedByScreenshotChord:Z
6. into the same method look for: .line 2495:
Code:
.end local v9 #e:Landroid/os/RemoteException;
:cond_45c
const/16 v39, 0xd4
move/from16 v0, v21
move/from16 v1, v39
if-eq v0, v1, :cond_46c
const/16 v39, 0xd5
move/from16 v0, v21
move/from16 v1, v39
if-ne v0, v1, :cond_489
we ll add a code here too, getting:
Code:
.end local v9 #e:Landroid/os/RemoteException;
:cond_45c
[COLOR="Red"] const/16 v28, 0x4
move/from16 v0, v28
move/from16 v1, v21
if-ne v1, v0, :cond_mirko
.line 1863
move-object/from16 v0, p0
iget-boolean v0, v0, Lcom/android/internal/policy/impl/PhoneWindowManager;->mBackKillTimeout:Z
move/from16 v28, v0
if-nez v28, :cond_mirko
if-eqz v8, :cond_mirko
if-nez v29, :cond_mirko
.line 1864
move-object/from16 v0, p0
iget-object v0, v0, Lcom/android/internal/policy/impl/PhoneWindowManager;->mHandler:Landroid/os/Handler;
move-object/from16 v38, v0
move-object/from16 v0, p0
iget-object v0, v0, Lcom/android/internal/policy/impl/PhoneWindowManager;->mBackLongPress:Ljava/lang/Runnable;
move-object/from16 v39, v0
invoke-static {}, Landroid/view/ViewConfiguration;->getGlobalActionKeyTimeout()J
move-result-wide v40
invoke-virtual/range {v38 .. v41}, Landroid/os/Handler;->postDelayed(Ljava/lang/Runnable;J)Z
.line 1865
const/16 v28, 0x1
move/from16 v0, v28
move-object/from16 v1, p0
iput-boolean v0, v1, Lcom/android/internal/policy/impl/PhoneWindowManager;->mBackKillTimeout:Z
.line 1875
:cond_mirko[/COLOR]
const/16 v39, 0xd4
move/from16 v0, v21
move/from16 v1, v39
if-eq v0, v1, :cond_46c
const/16 v39, 0xd5
move/from16 v0, v21
move/from16 v1, v39
if-ne v0, v1, :cond_489
7. add the new subclass attached in the directory of the smali we edited
LSJ back to kill
I found really hard do it from scratch because samsung is using longpress back to show/hide the flash bar (for multiwindows feature), so i decided to use that method simply switching the subclass from $10 (flashbar show-hide) to $killconcept (back to kill).
This meant back to kill works only when mutiwindows is on, so i needed to recall the subclass even when multiwindow was off.
following the diff:
-1 switch $10 subclass to $KillConcept subclass
find
Code:
.line 1618
new-instance v0, Lcom/android/internal/policy/impl/PhoneWindowManager$10;
invoke-direct {v0, p0}, Lcom/android/internal/policy/impl/PhoneWindowManager$10;-><init>(Lcom/android/internal/policy/impl/PhoneWindowManager;)V
iput-object v0, p0, Lcom/android/internal/policy/impl/PhoneWindowManager;->mBackLongPress:Ljava/lang/Runnable;
will become
Code:
.line 1618
new-instance v0, Lcom/android/internal/policy/impl/PhoneWindowManager$KillConcept;
invoke-direct {v0, p0}, Lcom/android/internal/policy/impl/PhoneWindowManager$KillConcept;-><init>(Lcom/android/internal/policy/impl/PhoneWindowManager;)V
iput-object v0, p0, Lcom/android/internal/policy/impl/PhoneWindowManager;->mBackLongPress:Ljava/lang/Runnable;
this will let u use back to kill ONLY when multiwindows is on. So let s make it for every case, multiwindows on and off.
find
Code:
.line 6320
:cond_91a
move-object/from16 v0, p0
iget-boolean v0, v0, Lcom/android/internal/policy/impl/PhoneWindowManager;->mIsMultiWindowUIEnabled:Z
move/from16 v27, v0
[B][U]if-eqz v27, :cond_68[/U][/B]
move-object/from16 v0, p0
iget v0, v0, Lcom/android/internal/policy/impl/PhoneWindowManager;->mEnableMultiWindowUISetting:I
move/from16 v27, v0
[B][U] if-eqz v27, :cond_68[/U][/B]
focus on bolded underlined conds, we need to switch them with cond_951 so we will have:
Code:
.line 6320
:cond_91a
move-object/from16 v0, p0
iget-boolean v0, v0, Lcom/android/internal/policy/impl/PhoneWindowManager;->mIsMultiWindowUIEnabled:Z
move/from16 v27, v0
[B][U]if-eqz v27, :cond_951[/U][/B]
move-object/from16 v0, p0
iget v0, v0, Lcom/android/internal/policy/impl/PhoneWindowManager;->mEnableMultiWindowUISetting:I
move/from16 v27, v0
[B][U] if-eqz v27, :cond_951[/U][/B]
cond_951 may be different depending on your compiler, but we need to recall the cond that gives this:
Code:
.line 6325
[B][U]:cond_951[/U][/B]
move-object/from16 v0, p0
iget-object v0, v0, Lcom/android/internal/policy/impl/PhoneWindowManager;->mHandler:Landroid/os/Handler;
move-object/from16 v27, v0
move-object/from16 v0, p0
iget-object v0, v0, Lcom/android/internal/policy/impl/PhoneWindowManager;->mBackLongPress:Ljava/lang/Runnable;
move-object/from16 v28, v0
invoke-static {}, Landroid/view/ViewConfiguration;->getGlobalActionKeyTimeout()J
move-result-wide v29
invoke-virtual/range {v27 .. v30}, Landroid/os/Handler;->postDelayed(Ljava/lang/Runnable;J)Z
goto/16 :goto_68
add the attached subclass and recompile.
NOTE: is in beta phase, has to be improved so if some dev wanna help me in debugging is welcome.
Let me be the first to say thanks for your efforts on this Mirko and welcome to the NeatROM crew
Mirko ddd said:
Hello xda'ers,
is me again, sorry to bother but today I bring to you a famous mod from AOKP: back longpress to kill.
You can find the how to into my github here
It really easy to do and port an any other samsung rom, simply check out github commit, it s very clear.
I made it for salesale's neat rom, u can find a flashable zip here
Would be appreciate to make a nandroid backup, just in case.
If u have requests for other roms please ask to your rom developer to contact me.
Cheers
Credits to:
AOKP
CM
xda sharing
Click to expand...
Click to collapse
this mod will be a great addition, mate..
Thanks Mirko. Installed on NeatromLite 3.5 and so far works as expected. Especially Tapatalk app annoyed me much - after closing it always stayed as running process for nothing. Now I can get rid of this by one long press. Great.
I gonna observe if it doesn't influence badly any other features of the rom (there were some issues with similar feature in Jkay's mod). Regards
Sent from my GT-I9100 using xda premium
Mirko, flashed Sale's Neatrom lite v3.3 (LPX). your mod works very well but i think better idea is "long press to kill ALL apps". With your mood I can kill only the latest application where I am.
Thanks
Sorry for my English
This is exactly what was i looking for. Thank you very much
I used the guide with Chameleon-ROM and it worked like a charm. But is there a way to change the longpressduration til the app gets killed?
- geroxx -
Great work Mirko. You got 5 star from me.
Been waiting for long time for this!
Thanks very much, agree that a kill all button is needed for recent applications when the home button is held down though!
But very happy with this mod, thanks!:thumbup:
NeatROM -The Best!
Salesale - True Super-Dev!
ApriliaM3 said:
Let me be the first to say thanks for your efforts on this Mirko and welcome to the NeatROM crew
Click to expand...
Click to collapse
thanks Aprilia
maanz said:
this mod will be a great addition, mate..
Click to expand...
Click to collapse
Since i cannot build my own rom at least i give a little of mine in many others xD
Many40 said:
Thanks Mirko. Installed on NeatromLite 3.5 and so far works as expected. Especially Tapatalk app annoyed me much - after closing it always stayed as running process for nothing. Now I can get rid of this by one long press. Great.
I gonna observe if it doesn't influence badly any other features of the rom (there were some issues with similar feature in Jkay's mod). Regards
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
code is not 100% perfect but is bugless, tested almist 2days with logcats
friccc81 said:
Mirko, flashed Sale's Neatrom lite v3.3 (LPX). your mod works very well but i think better idea is "long press to kill ALL apps". With your mood I can kill only the latest application where I am.
Thanks
Sorry for my English
Click to expand...
Click to collapse
well that s the mod, to kill all app check out my systemui with kill all recents, or clear ram with task manager
geroxx said:
This is exactly what was i looking for. Thank you very much
I used the guide with Chameleon-ROM and it worked like a charm. But is there a way to change the longpressduration til the app gets killed?
- geroxx -
Click to expand...
Click to collapse
yes timeout can be set into smalis
078gregory said:
Great work Mirko. You got 5 star from me.
Click to expand...
Click to collapse
thx Greg
bobdoblo said:
Been waiting for long time for this!
Thanks very much, agree that a kill all button is needed for recent applications when the home button is held down though!
But very happy with this mod, thanks!:thumbup:
NeatROM -The Best!
Salesale - True Super-Dev!
Click to expand...
Click to collapse
Answered two posts ago
Inviato dal mio GT-I9100 con Tapatalk 2
This is exactly what was i looking for. Thank you very much
I used the guide with Chameleon-ROM and it worked like a charm. But is there a way to change the longpressduration til the app gets killed?
- geroxx -
Click to expand...
Click to collapse
Originally Posted by Mirko ddd
yes timeout can be set into smalis
Inviato dal mio GT-I9100 con Tapatalk 2
Click to expand...
Click to collapse
looking forward to the smali edits, mate..:good:
078gregory said:
Great work Mirko. You got 5 star from me.
Click to expand...
Click to collapse
+1
I love you <3 (no homo )
maanz said:
looking forward to the smali edits, mate..:good:
Click to expand...
Click to collapse
ooh ok mate how many ms we have to set? i think is good enough, faster would be annoying because we could kill app mistaking, slower.. would be annoying too, but hey, i m not the boss here :silly:
salesale said:
+1
Click to expand...
Click to collapse
5+5=10! where are my 10 stars? all fallen? make a wish! mmh, i made my wish but.. (check out my signature to better understand Salesale )
sniper said:
I love you <3 (no homo )
Click to expand...
Click to collapse
nice to see tdunham friends here, you are welcome!
Good job buddy. Thanks for the heads up
Sent from my GT-I9100 using Tapatalk 2
I've been waiting for this! Thanks Mirko.
Could you add battery bar mod to your to do list?
Mirko ddd said:
ooh ok mate how many ms we have to set? i think is good enough, faster would be annoying because we could kill app mistaking, slower.. would be annoying too, but hey, i m not the boss here :silly:
Click to expand...
Click to collapse
let's ask the guys here, how long in ms would they want the longpressduration till the app gets killed.. that would be good, mate.
Goldieking said:
Good job buddy. Thanks for the heads up
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
vrts said:
I've been waiting for this! Thanks Mirko.
Could you add battery bar mod to your to do list?
Click to expand...
Click to collapse
you're welcome.
battery bar mod u mean aokp style or miui style?
I sincerily see this feature har to port without using romcontrol stuffs and miui stuffs.. if i remember well leomar made it for gingerbread, i will take a look, but i don t promise anything about :silly:
Mirko ddd said:
yes timeout can be set into smalis
Inviato dal mio GT-I9100 con Tapatalk 2
Click to expand...
Click to collapse
thanks
However i am not really good in java-developing. So can you please tell me which values i must change to set the timeout.
- geroxx -
geroxx said:
thanks
However i am not really good in java-developing. So can you please tell me which values i must change to set the timeout.
- geroxx -
Click to expand...
Click to collapse
really no need to be good in java developing
if u take a look in the code (differences posted on github, u used to get it on chamaleon) u will have to focus on:
Code:
iget-object v0, v0, Lcom/android/internal/policy/impl/PhoneWindowManager;->mBackLongPress:Ljava/lang/Runnable;
move-object/from16 v39, v0
invoke-static {}, Landroid/view/ViewConfiguration;->[B][COLOR="Red"]getGlobalActionKeyTimeout[/COLOR][/B]()J
this means we are recalling a method with this path:
Landroid/view/ViewConfiguration
so it s in framework jar/android/view/Viewconfiguration.smali
Open this smali file and look for the method getGlobalActionKeyTimeout
method say:
Code:
.method public static getGlobalActionKeyTimeout()J
.registers 2
.prologue
.line 669
[B]const-wide/16 v0, 0x1f4[/B]
return-wide v0
.end method
let s focus on bolded, this is the value in ms (i guess)
0x1f4 it s the time.
I really have problems with ex numbers so i google it and see this corresponding to 500ms (half second)
So we have two ways we can follow:
or edit the method
or repace this method with a convenient one (which have the timeout we want)
first is an asshole thing, because we will change the timeout of other things like power menu timeout, presshome timeout etc..
Second is more handy, so we can use an existing method (so no need to create nu) to our aim.
Let s investigate to find a nice timeout time :highfive: (Mirko wth are u talkin 'bout )
If I can you a can, only need to waste some time and have a passion for
Hope this will help you, for questions i m here, but don t forget to thank (i ignore people who don t support my efforts)