Database Develop

Multi-Touch Keyboard

This is the DX keyboard and has been successfully put onto the fascinate, credit goes to adrynalyne for putting this together. This version should not give you FC errors when you reboot the phone
Needs to be flashed with clockwork!
UPDATED 10/12/10

I'm sorry how do you install this?
Edit: found out how.

cool thanks.. i was looking for this!

How exactly is multi-touch useful on a keyboard?

d12183 said:
How exactly is multi-touch useful on a keyboard?
Click to expand...
Click to collapse
Don't you type with 2 fingers? There you go

taypotts said:
Don't you type with 2 fingers? There you go
Click to expand...
Click to collapse
Well yeah... but wouldn't you be able to do the same without multi-touch?

d12183 said:
Well yeah... but wouldn't you be able to do the same without multi-touch?
Click to expand...
Click to collapse
take a non-multi-touch keyboard and press one key then try to press another key. It will only pick up on the first key that you press.
You can type with 2 fingers but it's like you have to use one finger at a time fairly slow.

shauder said:
This is the DX keyboard and has been successfully put onto the fascinate, credit goes to adrynalyne for putting this together. This version should not give you FC errors when you reboot the phone
Needs to be flashed with clockwork!
UPDATED 10/12/10
Click to expand...
Click to collapse
Updated original post

shauder said:
This is the DX keyboard and has been successfully put onto the fascinate, credit goes to adrynalyne for putting this together. This version should not give you FC errors when you reboot the phone
Needs to be flashed with clockwork!
UPDATED 10/12/10
Click to expand...
Click to collapse
I am getting force close (something about a latin file). Any solutions?

SAME HERE FORCE CLOSES! Thanks now need to restore with odin.
Dammit

larry996 said:
SAME HERE FORCE CLOSES! Thanks now need to restore with odin.
Dammit
Click to expand...
Click to collapse
Clear the Dalvik cache. It works you guys are just doing something wrong.

i'm getting force closes too...i assure you i did precisely what it said... install with cwm. how do i get rid of this?
**edit*
nevermind....it's gone

Will this work with the vibrant? Running a custom rom?
Sent from my SGH-T959 using XDA App

I don't see why not.

I had this up and running on my phone and now its gone. Could changing the tw launcher have deleted it? I just tried to flash it but it didn't work
Sent from my voodoo powered fascinate

Keys are tiny!
Sent from my SGH-T959 using XDA App

I originally installed the .apk of this keyboard and got FC's. I cleared the entire devlik cache and installed this .zip via clockwork and I'm still getting FC's. Any ideas?

Alright I figured it out. FOR THOSE OF YOU HAVING A FORCE CLOSE WITH "LATIN" IN THE NAME, these are the steps that I took (if you've already flashed via clockwork):
I AM NOT RESPONSIBLE FOR ANY DAMAGE DONE TO YOUR PHONE, this is just how I fixed this issue.
1.) Go into system/app and DELETE your DXkeyboard.apk
2.) Go into data/devlik cache and delete the line that has "DX.." in the name (i forgot what its called)
the above two steps thus far are what I DID, they may not be necessary.
3.) unzip the dxkbd file that was in the OP on your desktop
4.) go into "system" and you'll see "app" and "library"
5.) copy the .apk file and .so file from "app" and "library" respectively and put them on your sdcard
6.) using root explorer, move the .so file to system / lib
7.) using root explorer, move the .apk file to system / app
8.) DELETE "latinIME" apk and odex
9.) DELETE latintutorial (or something like that, its right under latinIME odex i believe)
10.) reboot

With the exception of deleting things, thats precisely what the package in the op does.

adrynalyne said:
With the exception of deleting things, thats precisely what the package in the op does.
Click to expand...
Click to collapse
I couldn't get the first post or the CW zip to work, but following the steps from that last post finally got it working.

[MOD/HOW-TO] Remove hard key vibes via android.policy.jar

I thought I'd offer my solution to disabling the hard key vibrations on the Atrix since other people might find this useful. This method differs from the other solutions in that it doesn't tamper with your Silent Mode vibrations (like StreakVibrations does) and it's code based, so it shouldn't tamper with any themes you have installed (like the framework-res.apk method). It is firmware dependent though since it's a code modification.
You'll need an android.policy.jar modified for your firmware.
What I'm doing is I'm modifying the method called performHapticFeedbackLw, and telling it to skip triggering the vibrate pattern for all effects (there are 5) except for keyboard taps. Long press vibe, virtual key vibe, safe mode disabled vibe, and safe mode enabled vibe will no longer trigger... Incidentally, does anyone know what safe mode on this phone refers to?
To use the file, you need to be on Bell, Telstra, GingerBlur, Gladiatrix or stock ATT 1.8.3 firmware, and be deodexed. Can you copy the file to your phone without being deodexed? I don't know. I'm a programmer, but an Android newbie so just to be safe it's best if you're deodexed.
Before you try anything, obviously make sure you are backed up. At least copy your existing android.policy.jar so that you can restore it if necessary.
All you need to do is either:
a) Run the novibes.bat script packaged in the zip. There are a couple prerequisites:
1. Make sure to set your USB connection to "None" on your phone.
2. On your phone, go to Settings > Applications > Development and make sure USB debugging is turned on.
3. Plug your phone into your PC and let it install any necessary drivers.
4. Then you can run novibes.bat.
or
b) Follow the steps outlined below to do it manually:
1. Replace /system/framework/android.policy.jar with the one that I've attached.
2. Make sure the permissions of the file are set to rw-r--r-- (thanks for reminding me, Meloy and for correcting, natboy!). The easiest way is to use Root Explorer, long press the file, choose permissions, and set owner: read/write, group:read, others:read. Otherwise, use Terminal and type "chmod 644 /system/framework/android.policy.jar" without the quotations.
3. Reboot.
For those not on stock Bell, I'd be willing to modify your android.policy.jar and post it here if you provide somewhere for me to download it, and specify what firmware it comes from. It's quite quick to do once you're set up so I don't mind. Alternatively, make the change yourself:
1. Download baksmali and smali (both .jars and scripts, total 4 files).
2. Copy /system/framework/ from your phone to your computer.
3. Copy all the files from step 1 to the framework directory from step 2 on your computer.
4. Unzip android.policy.jar and copy its classes.dex file to the framework directory on your computer.
5. From the command line, navigate to the framework directory and run "./baksmali classes.dex". It will create a directory named "out".
6. Open "out/com/android/internal/policy/impl/PhoneWindowManager.smali" in a text editor.
7. Search for a method called "performHapticFeedbackLw". Go to near the bottom of that method, and you will see the Dalvik bytecode representation of a switch statement:
Code:
.sparse-switch
0x0 -> :sswitch_27 #This is for long press vibe
0x1 -> :sswitch_35 #This is for virtual key vibe
0x3 -> :sswitch_38 #This is for keyboard tap vibe
0x2710 -> :sswitch_3b #This is for safemode disabled vibe
0x2711 -> :sswitch_3e #This is for safemode enabled vibe
.end sparse-switch
8. Here's an example of how you might want it to change. Basically you want to replace the original goto labels with one that causes the method to step out without triggering a vibe, and that notifies the calling method there was no vibe by returning false. The label to use is called ":cond_1d":
Code:
.sparse-switch
0x0 -> :cond_1d #This is for long press vibe
0x1 -> :cond_1d #This is for virtual key vibe
0x3 -> :sswitch_38 #This is for keyboard tap vibe
0x2710 -> :cond_1d #This is for safemode disabled vibe
0x2711 -> :cond_1d #This is for safemode enabled vibe
.end sparse-switch
9. From the command line in the framework directory, run "./smali -o classes.dex out". You now have a new classes.dex that has your modification.
10. Zip up the classes.dex with the META-INF directory from your original android.policy.jar. Rename the zip to android.policy.jar.
11. Copy the new file to your phone and reboot.
12. At this point you should be done.

Will this be possible on the AT&T atrix? I currently use the streak vibe method but I'd like this much better.
Sent from my MB860 using XDA App

n1ckr0th said:
Will this be possible on the AT&T atrix? I currently use the streak vibe method but I'd like this much better.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1079873&page=3
Check out that thread over in general. The info for how to edit framework.res is there, but there is a flashable .zip that will disable the vibrations in either stock/rooted 1.83 or Gingerblur 3.5 for you.

bearsfan172 said:
http://forum.xda-developers.com/showthread.php?t=1079873&page=3
Check out that thread over in general. The info for how to edit framework.res is there, but there is a flashable .zip that will disable the vibrations in either stock/rooted 1.83 or Gingerblur 3.5 for you.
Click to expand...
Click to collapse
thank you, but i wonder if this specific method is possible on the atrix as to retain themes and such.
interesting that its in general, development may be a better home for it.

n1ckr0th said:
thank you, but i wonder if this specific method is possible on the atrix as to retain themes and such.
interesting that its in general, development may be a better home for it.
Click to expand...
Click to collapse
Yes, this would work perfectly fine on ATT. You can either follow the instructions I provided, or if you like you can post /system/framework/android.policy.jar from your phone somewhere and pm me the link so I can download it and I'll do it for you. Also mention what firmware you're on. I just don't want to download hundreds of MB of firmwares which is why I didn't set one up for all the ATT firmwares.
That other method requires editing a file that is guaranteed to change with any theme you install. That means anytime you change themes you'll need to edit that .apk yourself, or wait for someone to bring the change over. android.policy.jar is unlikely to change for themes.

Ok, I've posted a version for ATT 1.8.3 that was given to me by n1ckr0th.
n1ckr0th, let me know whether it works fine or not. There should be no problem, it looked just like the other 2 versions I modified.
Incidentally, he's using GingerBlur 3.5 so anyone on stock be careful (ie. copy your original file to somewhere else on your phone). It shouldn't matter at all because from what I see, there aren't any resources to modify in android.policy.jar so GingerBlur's should be the same as stock. At any rate, it won't brick your phone if you put the wrong one on. I put Telstra's on my phone by accident and it just messed up the the graphics on screen (maybe because the addresses were all wrong for my phone). You can still use adb, or sshdroid to copy and replace with your original android.policy.jar.

please delete

meloy said:
Don't use this on AT&T 1.83!
After the replace and reboot my phone was really laggy and some applications doesn't start anymore (camera, contacs for example). After i have replaced it with the original file i have still the same problem.
My phone config:
- SBF 1.83
- rooted (GingerBreak 1.20)
- sideloading enabled (GladEnabler)
- GladiAtrix 3 b0.2 ROM
- LauncherPRO
- GingerBread Theme only
Click to expand...
Click to collapse
What? That can't be right, if you still have the same problem after copying the original file, that means that you must have done something wrong. It's a single file change, provided you returned the file to the original, it will be back to the way it was. How did you copy the file? And also, are you deodexed? As mentioned in the original post, you have to be deodexed, because I don't know the results of using it on a non-deodexed system. Your posted config makes it sound like you might not be.

Sorry, my mistake. It is deodexed, I have just forgot to set the permissions to rw-r-r, you should maybe mention this in your start post. It's all working fine now. Thanks for the good work.
By the way, your mod (android.policy.att_1.8.3.zip) has added an "reboot" function to my phone, it is working well too.

meloy said:
Sorry, my mistake. It is deodexed, I have just forgot to set the permissions to rw-r-r, you should maybe mention this in your start post. It's all working fine now. Thanks for the good work.
By the way, your mod (android.policy.att_1.8.3.zip) has added an "reboot" function to my phone, it is working well too.
Click to expand...
Click to collapse
Haha, that's good. Had me scared for a moment, I didn't want to break anyone's phone!
Thanks for the tip, I'll mention that in the original post. Oh, and what do you mean by the reboot function...? Where did you access that? I certainly didn't add it, so it might be a mod added to GingerBlur?

maledyris said:
Oh, and what do you mean by the reboot function...? Where did you access that? I certainly didn't add it, so it might be a mod added to GingerBlur?
Click to expand...
Click to collapse
When i go to the phone options i have now these selection:
- Silent Mode
- Airplane Mode
- Power off
- Reboot
Yes, i think it is a GingerBlur mod. But it doesn't bother me, it is a good feature.

meloy said:
When i go to the phone options i have now these selection:
- Silent Mode
- Airplane Mode
- Power off
- Reboot
Yes, i think it is a GingerBlur mod. But it doesn't bother me, it is a good feature.
Click to expand...
Click to collapse
Interesting, that never occurred to me. I usually go into terminal and type in reboot to reboot my phone. I think I'll add that to my phone too...

maledyris said:
Haha, that's good. Had me scared for a moment, I didn't want to break anyone's phone!
Thanks for the tip, I'll mention that in the original post. Oh, and what do you mean by the reboot function...? Where did you access that? I certainly didn't add it, so it might be a mod added to GingerBlur?
Click to expand...
Click to collapse
the reboot function is cooked into GingerBlur. for some reason my phone wouldnt boot after i replaced the file? i used root explorer and set the permissions to whats specified.

n1ckr0th said:
the reboot function is cooked into GingerBlur. for some reason my phone wouldnt boot after i replaced the file? i used root explorer and set the permissions to whats specified.
Click to expand...
Click to collapse
Hmm, how far does it get? Do you at least get to the boot animation? I notice that it may sit at the boot animation for a really long time after changing a file sometimes. Probably updating the cache or something. It's odd that it wouldn't work for you considering it's your file and it worked for meloy. How did you copy the file over?
If you try again, delete the original file, so you can be sure it's no longer there, then try the copy again.

I'm on AT&T 1.8.3. I followed instructions just as in OP (yes, including the proper setting of permissions), but I soon found a significant problem. Everytime I held down my power button in order to invoke the power options menu, instead of the menu popping up, my phone just freaked out (the screen quickly FADED to black and the phone rebooted). I did this about four times, and each time it happened exactly the same. So I brought back the original framework file, and now everything works fine.
Any ideas?

I have no problems with this mod. It works all fine.

Been waiting on this mod. Streakvibrations has me missing my notification vibes. Thank you

It gave me a red light on boot, stuck at Motorola logo for infinity. I booted into recovery and reflashed gb 3.5 to fix it. Ill try your idea of deleting it then moving the new one.
Sent from my MB860 using XDA App
EDIT: still didnt boot, had to flash again..

I'm getting the flashing red light and rebooting as well. I can't get into CWM though, going to have to flash a SBF. Only think I can think of is maybe the Dalvik cache needs to be wiped before rebooting?
Edit: I'm on an AT&T phone and used GB to deodex as well.. maybe it's not catching all the files..

lurchbyrep said:
I'm on AT&T 1.8.3. I followed instructions just as in OP (yes, including the proper setting of permissions), but I soon found a significant problem. Everytime I held down my power button in order to invoke the power options menu, instead of the menu popping up, my phone just freaked out (the screen quickly FADED to black and the phone rebooted). I did this about four times, and each time it happened exactly the same. So I brought back the original framework file, and now everything works fine.
Any ideas?
Click to expand...
Click to collapse
Are you on stock 1.83? Now that we know that android.policy.jar has some mods built into it for Gingerblur pseudo rom, the att 1.83 file I posted probably isn't ideal for stock users.
If you're on stock, maybe you could post your android.policy.jar somewhere and pm me the link to download. Then I could put together a pure stock att one when I get home.
Sent from my MB860 using XDA App

[Q] I changed provider and the simtoolkit is not present

I have JB XXLPZ and changed provider today.
From the documentation from the provider I need to set things via the simtoolkit. I don't see the icon and can't find it anywhere?
Also I have the phone rooted and am running the TZ 3.5 kernel.
Any hints or tips?

Midnight Shadow said:
I have JB XXLPZ and changed provider today.
From the documentation from the provider I need to set things via the simtoolkit. I don't see the icon and can't find it anywhere?
Also I have the phone rooted and am running the TZ 3.5 kernel.
Any hints or tips?
Click to expand...
Click to collapse
Are u sure u dont see simtoolkit in my launcher. U can check app manager see simtoolkit. I think u need turn on and turn off airplane mode
Sent from my GT-I9070 using Tapatalk 2

Midnight Shadow said:
I have JB XXLPZ and changed provider today.
From the documentation from the provider I need to set things via the simtoolkit. I don't see the icon and can't find it anywhere?
Also I have the phone rooted and am running the TZ 3.5 kernel.
Any hints or tips?
Click to expand...
Click to collapse
Install SD Maid app, press left soft button and go to settings of that app. Check "Include system packeges?". Go back, then go to tab APPCONTROL. Refrash it, then search for stk. Press on it, and tap on Start application.

dungeonshard said:
Are u sure u dont see simtoolkit in my launcher. U can check app manager see simtoolkit. I think u need turn on and turn off airplane mode
Sent from my GT-I9070 using Tapatalk 2
Click to expand...
Click to collapse
Check 10 times and I'm not in airplane mode as I can call en be called. Only data requires some settings for this provider and must be setup via the simtoolkit as per their instuctions.

shut_down said:
Install SD Maid app, press left soft button and go to settings of that app. Check "Include system packeges?". Go back, then go to tab APPCONTROL. Refrash it, then search for stk. Press on it, and tap on Start application.
Click to expand...
Click to collapse
I installed it, but it doesn't show up in the list.
Also original rooted kernel didn't make a change.
When I use ES file-explorer and go to the /system/app folder I see a stk.apk and stk.odex
I was now able to install the stk, but it doesn't show up in the app drawer. Installed size is 0KB.

Midnight Shadow said:
I installed it, but it doesn't show up in the list.
Also original rooted kernel didn't make a change.
When I use ES file-explorer and go to the /system/app folder I see a stk.apk and stk.odex
I was now able to install the stk, but it doesn't show up in the app drawer. Installed size is 0KB.
Click to expand...
Click to collapse
Hmmm. Try to delete both. And wait me to upload deodexed file.
Edit: Try to delete both apk and odex file. And to push this file from attachemt to system/app. (not to install)

shut_down said:
Hmmm. Try to delete both. And wait me to upload deodexed file.
Edit: Try to delete both apk and odex file. And to push this file from attachemt to system/app. (not to install)
Click to expand...
Click to collapse
With sd-maid I'm now able to see the app, but when trying to start it gives a "Not possible!" message...

Midnight Shadow said:
With sd-maid I'm now able to see the app, but when trying to start it gives a "Not possible!" message...
Click to expand...
Click to collapse
Reboot. You pushed this file? And did remove previous apk and odex file of it?
P.S. If you really need that app to open do this:
1. Make backup in CWM.
2. Flash stock FW with Odin. And do factory reset. Or try with factory reset first, without flashing JB with Odin again, if that do not help, then flash FW.
3. Use app for your needs
4. Root phone again
5. Install TZ 3.5
6. Restore your backup.

shut_down said:
Reboot. You pushed this file? And did remove previous apk and odex file of it?
Click to expand...
Click to collapse
I removed the previous two files and copied the one you supplied in it's place.
Ran sd-mail and was able to find the stk app. Unable to run it though.
Then reboot.
After the reboot the sd-maid app was unable to find the stk application like the original ones.

Midnight Shadow said:
I removed the previous two files and copied the one you supplied in it's place.
Ran sd-mail and was able to find the stk app. Unable to run it though.
Then reboot.
After the reboot the sd-maid app was unable to find the stk application like the original ones.
Click to expand...
Click to collapse
Read my edited post. :angel:

shut_down said:
Read my edited post. :angel:
Click to expand...
Click to collapse
Ok. Will do that tomorrow.
For now I use the Wifi hotspot functionality from my company phone.
I need to do the following:
Choose Roaming services.
Choose Selecteer Mode.
Choose Manueel.
Choose International.
Simcard gets updated.
If you know any app that can do the following then I'm all ears
Thanks and I'll update tomorrow!

Midnight Shadow said:
Ok. Will do that tomorrow.
For now I use the Wifi hotspot functionality from my company phone.
I need to do the following:
Choose Roaming services.
Choose Selecteer Mode.
Choose Manueel.
Choose International.
Simcard gets updated.
If you know any app that can do the following then I'm all ears
Thanks and I'll update tomorrow!
Click to expand...
Click to collapse
Solved!
The provider said that my simcard didn't need to be changed because it was of the newer type. So the sim toolkit was not being able to run because it detected the newer type.
Then I explained that I still had no internet. She talked me throug all the settings and they were fiine. On their website there are numerous samples per phone on how to setup this manually.
Is seems that the settings defer for some phones. They told me I had to type "internet" in the access type section while it had to be "default" what I found out by checking the phone of my wife. She has the same provider.
After changing I had my dataconnection.
Thanks for thinking with me!

Easier WiFi Tether Hack (No SQL Edits + Survives Factory Resets)

** Designed for stock Moto 98.72.22 and 98.72.22-based ROMs **
** FOR OTHER ROMS and updated stock, see post #7 **
When you do the entitlement_check SQL hack, you are modifying a string provided by MotorolaSettingsProvider.apk. But anytime you do a factory reset, you have to repeat the SQL hack. I didn't like this, so I modified the system APK to disable entitlement by default = same end result as SQL hack.
I have tested this twice without issue, so I'd say it's ready for release. Of course you need to be rooted to modify /system/app.
I did the following with Safestrap file manager and upon rebooting (no need to wipe, it seems) the Mobile Hotspot launcher worked like a charm
Also did a factory reset (data, dalvik, cache) and tethering still worked just fine!
Instructions:
0. Backup just in case!!
1. Download attached MotorolaSettingsProvider.apk
2. Reboot into Safestrap, Mount System, and then open the File Manager (under Advanced)
3. Browse to /system/app and rename MotorolaSettingsProvider.apk to *.apk.BAK (keep as a backup)
4. Browse back to the downloaded file, click it, select Move, browse to /system/app, click Select, OK
5. Browse again to /system/app, click on MotorolaSettingsProvider.apk (NOT the one ending in .BAK)
6. CHMOD permissions as 0644 (rw r- r-)
7. Rename MotorolaSettingsProvider.odex to *.odex.BAK (backup)
8. Reboot, click Thanks, and enjoy!

tried this on stock jb.no go. fc and started reading notifications. also constant network loss and re-aquire.

Ismokel said:
tried this on stock jb.no go. fc and started reading notifications. also constant network loss and re-aquire.
Click to expand...
Click to collapse
JB 246 98.72.22? I'm assuming you used a root explorer due to the FC. I recommend using Safestrap's built-in file manager (see the updated instructions).
I could also make a flashable ZIP to mitigate user-error if there is demand for it.
The last issues you mentioned are unrelated to this. The modified APK is exactly the same as the original, except for a single byte (1 -> 0) and deodexed. Oh, and a "false" to "true" in the manifest so we could manually clear data, but that didn't work out. You can decompile and compare yourself

Same issue here as Ismokel. It might be a signing issue, as I saw the same thing occur when I tried doing the mod myself and was experimenting with the different options for signing. It worked for me when I left the existing signature.
I would post my modded version, but I need to make one with only that mod first, as mine has mods to change other defaults as well.
Also, what is this JB 246 you are referring to? Wrong number? Just from a quick search, the only 246 reference I found was ICS.
You mentioned that yours worked for you without wiping data. Did you change default_entitlement_check in the xml resources or did you change something else? I was only interested in this mod to change the default and not the existing setting, but I'm still somewhat curious.

progrockguy said:
** Designed for stock Moto 246 (JB 4.1.2) and 246-stock-based ROMs **
When you do the entitlement_check SQL hack, you are modifying a string provided by MotorolaSettingsProvider.apk. But anytime you do a factory reset, you have to repeat the SQL hack. I didn't like this, so I modified the system APK to disable entitlement by default.
I have tested this twice without issue, so I'd say it's ready for release. Of course you need to be rooted to modify /system/app.
I did the following with Safestrap file manager and upon rebooting (no need to wipe, it seems) the Mobile Hotspot launcher worked like a charm
Also did a factory reset (data, dalvik, cache) and tethering still worked just fine!
Instructions:
1. Download attached MotorolaSettingsProvider.apk
2. Reboot into Safestrap, Mount System, and then open the File Manager (under Advanced)
3. Browse to /system/app and rename MotorolaSettingsProvider.apk to *.apk.BAK (keep as a backup)
4. Browse back to the downloaded file, click it, select Move, browse to /system/app, click Select, OK
5. Browse again to /system/app, click on MotorolaSettingsProvider.apk (NOT the one ending in .BAK)
6. CHMOD permissions as 0644 (rw r- r-)
7. Rename MotorolaSettingsProvider.odex to *.odex.BAK (backup)
8. Reboot, click Thanks, and enjoy!
Click to expand...
Click to collapse
I would like to know how you made the modifications to the apk. I would like to make the same modifications for my Atrix HD.

dpcsar said:
I would like to know how you made the modifications to the apk. I would like to make the same modifications for my Atrix HD.
Click to expand...
Click to collapse
has anyone tried this with SlimKat? It's the one thing that's missing from it that I've wanted so far.

ShadyDreamer said:
Also, what is this JB 246 you are referring to? Wrong number? Just from a quick search, the only 246 reference I found was ICS.
Click to expand...
Click to collapse
Whoops!! 98.72.22 is the base I used. If you took OTA updates, that could explain the boot loops. See below on how to DIY
dpcsar said:
I would like to know how you made the modifications to the apk. I would like to make the same modifications for my Atrix HD.
Click to expand...
Click to collapse
Brolzy said:
has anyone tried this with SlimKat? It's the one thing that's missing from it that I've wanted so far.
Click to expand...
Click to collapse
This mod is easy and should work on all ROMs. All you need is a deodexed version of MotorolaSettingsProvider.apk from your current/desired ROM.
Steps: after decompiling, open the following text file:
res/values/integers.xml
look for: def_entitlement_check
Change the 1 to a 0 and save.
Recompile and KEEP EXISTING SIGNATURE.
My safestrap instructions will work on your newly modified APK. (If you're going to try replacing via root file explorers, I suggest an overwriting Paste. That way you'll keep permissions in case android crashes and hot reboots. Do not delete, *then* paste. It'll likely crash before you can set the permissions.)
Good luck!

progrockguy said:
This mod is easy and should work on all ROMs. All you need is a deodexed version of MotorolaSettingsProvider.apk from your current/desired ROM.
Steps: after decompiling, open the following text file:
res/values/integers.xml
look for: def_entitlement_check
Change the 1 to a 0 and save.
Recompile and KEEP EXISTING SIGNATURE.
Click to expand...
Click to collapse
That's exactly what I did, so I don't know why your file didn't work for me. I'm using 98.72.22, too. A while ago when I did that exact mod myself it worked fine.
If you are using adb from a computer connected by USB to copy and install the apk, after using su you can use the stop command to close all apps, then you can safely move, rename, replace, or delete system apps without it crashing and rebooting. Just make sure you have it in the proper state before you reboot. If a prompt to allow su from adb comes up on the phone, be sure to allow it with no time limit in case you need to use su again before you use adb reboot to restart the phone.

ShadyDreamer said:
That's exactly what I did, so I don't know why your file didn't work for me. I'm using 98.72.22, too. A while ago when I did that exact mod myself it worked fine.
Click to expand...
Click to collapse
Curious, where did you get your APK from? Because stock is odexed.
My file also had a manifest edit (which didn't work out), but I doubt that's the issue since it works on two of my Bionics.

When I quoted the part I was replying to, I included your "All you need is a deodexed version of MotorolaSettingsProvider.apk from your current/desired ROM." line in the quote for a reason. I did that part.

[TWEAK] Remove Brightness Slider from Notification Panel

This tweak worked on the stock T-Mobile OCG ROM, and will likely work for other stock based ROM's.
I used the "SQLite Editor" app to do this tweak. Other SQLite editors should work as well.
1.Launch SQLite Editor and select "Files" and drill down into /data/data/com.android.providers.settings/databases/settings.db
2. Select "system"
3. Press the "+" option
4. Leave _id set to auto
5. Add in the name field "notification_panel_brightness_adjustment" (without the quotes)
6. Add in the value field "0" (number zero without the quotes)
7. Press save
8. Exit and reboot
If you decide at a later time you want it back, just change the value of that field to a 1 then save and reboot.

guyd said:
This tweak worked on the stock T-Mobile OCG ROM, and will likely work for other stock based ROM's.
I used the "SQLite Editor" app to do this tweak. Other SQLite editors should work as well.
1.Launch SQLite Editor and select "Files" and drill down into /data/data/com.android.providers.settings/databases/settings.db
2. Select "system"
3. Press the "+" option
4. Leave _id set to auto
5. Add in the name field "notification_panel_brightness_adjustment" (without the quotes)
6. Add in the value field "0" (number zero without the quotes)
7. Press save
8. Exit and reboot
If you decide at a later time you want it back, just change the value of that field to a 1 then save and reboot.
Click to expand...
Click to collapse
Nice find! However since I actually use the brightness slider daily, I won't be getting rid of it. Now we just need to find a way to get rid of the S Finder/Quick Connect from the notification panel.

Yoshi910 said:
Nice find! However since I actually use the brightness slider daily, I won't be getting rid of it. Now we just need to find a way to get rid of the S Finder/Quick Connect from the notification panel.
Click to expand...
Click to collapse
I can mod systemui.apk to remove them, if you want it.

mikeyinid said:
I can mod systemui.apk to remove them, if you want it.
Click to expand...
Click to collapse
Yes please
And if you could possibly look into having 6 toggles that would be greatly appreciated. Using your rom got it before the pull lol

guaneet said:
Yes please
And if you could possibly look into having 6 toggles that would be greatly appreciated. Using your rom got it before the pull lol
Click to expand...
Click to collapse
haha, yea im not a fan of having a ton of threads all with mostly the same thing. ill see what i can do about the toggles, i can for sure get rid of the other stuff.

You can also simply install Lux and turn off its persistent notification

Could this be used to do other tweaks like remove icons/clock from the status bar?

mikeyinid said:
I can mod systemui.apk to remove them, if you want it.
Click to expand...
Click to collapse
That'd be awesome. I was looking through the xml but was having trouble finding an obvious section to cut for this bar--res/layout/status_bar_expanded doesn't even appear to contain a reference to the sfinder_qconnect stuff.

teiglin said:
That'd be awesome. I was looking through the xml but was having trouble finding an obvious section to cut for this bar--res/layout/status_bar_expanded doesn't even appear to contain a reference to the sfinder_qconnect stuff.
Click to expand...
Click to collapse
its in res/values/dimens.xml. if you google it theres a few tuts how to do it.

mikeyinid said:
its in res/values/dimens.xml. if you google it theres a few tuts how to do it.
Click to expand...
Click to collapse
Thanks, I had been looking at another tutorial involving cutting a few lines from status_bar_extended, but it hadn't occurred to me simply to change its size to zero in dimens. >.<
This doesn't seem worth a whole new thread, so I've attached a systemui whose only change is the removal of the sfinder/qconnect bar. I believe you also have to delete the arm64/SystemUI.odex.art.xz file for things to work properly.
Edit for basic instructions:
Use a root-enabled file manager or console to replace /system/priv-app/SystemUI/SystemUI.apk with the attached file, and delete /system/priv-app/SystemUI/arm64/SystemUI.odex.art.xz. Make sure the permissions of the new SystemUI.apk are rw-r--r-- (chmod 644 /system/priv-app/SystemUI/SystemUI.apk at the console). Reboot and enjoy.
Caveat: you may not be able to swipe away notifications from within the region previously taken up by the sfinder/qconnect bar.

Great! Can also be done via adb:
Code:
adb shell settings put system notification_panel_brightness_adjustment 0

teiglin said:
Thanks, I had been looking at another tutorial involving cutting a few lines from status_bar_extended, but it hadn't occurred to me simply to change its size to zero in dimens. >.<
This doesn't seem worth a whole new thread, so I've attached a systemui whose only change is the removal of the sfinder/qconnect bar. I believe you also have to delete the arm64/SystemUI.odex.art.xz file for things to work properly.
Click to expand...
Click to collapse
Thanks! Works great.

teiglin said:
Thanks, I had been looking at another tutorial involving cutting a few lines from status_bar_extended, but it hadn't occurred to me simply to change its size to zero in dimens. >.<
This doesn't seem worth a whole new thread, so I've attached a systemui whose only change is the removal of the sfinder/qconnect bar. I believe you also have to delete the arm64/SystemUI.odex.art.xz file for things to work properly.
Click to expand...
Click to collapse
How would you get it to work, I tried to install it but it won't install.

teiglin said:
Thanks, I had been looking at another tutorial involving cutting a few lines from status_bar_extended, but it hadn't occurred to me simply to change its size to zero in dimens. >.<
This doesn't seem worth a whole new thread, so I've attached a systemui whose only change is the removal of the sfinder/qconnect bar. I believe you also have to delete the arm64/SystemUI.odex.art.xz file for things to work properly.
Click to expand...
Click to collapse
Worked fine, thanks !

EvoYas said:
How would you get it to work, I tried to install it but it won't install.
Click to expand...
Click to collapse
Also wondering the same. And I don't see the system ui file in arm64. Can't wait to find out though lol I despise those two buttons

EvoYas said:
How would you get it to work, I tried to install it but it won't install.
Click to expand...
Click to collapse
v2.2v said:
Also wondering the same. And I don't see the system ui file in arm64. Can't wait to find out though lol I despise those two buttons
Click to expand...
Click to collapse
You either need a root-enabled file manager or su at a console, and replace /system/priv-app/SystemUI/SystemUI.apk with the file I provided, and delete /system/priv-app/SystemUI/arm64/SystemUI.odex.art.xz, then reboot. As always, I strongly recommend making backups and of course, I can provide no guarantees, yadda yadda.

teiglin said:
You either need a root-enabled file manager or su at a console, and replace /system/priv-app/SystemUI/SystemUI.apk with the file I provided, and delete /system/priv-app/SystemUI/arm64/SystemUI.odex.art.xz, then reboot. As always, I strongly recommend making backups and of course, I can provide no guarantees, yadda yadda.
Click to expand...
Click to collapse
That worked flawlessly, thank you.

teiglin said:
You either need a root-enabled file manager or su at a console, and replace /system/priv-app/SystemUI/SystemUI.apk with the file I provided, and delete /system/priv-app/SystemUI/arm64/SystemUI.odex.art.xz, then reboot. As always, I strongly recommend making backups and of course, I can provide no guarantees, yadda yadda.
Click to expand...
Click to collapse
perfect! thank you so much

teiglin said:
Thanks, I had been looking at another tutorial involving cutting a few lines from status_bar_extended, but it hadn't occurred to me simply to change its size to zero in dimens. >.<
This doesn't seem worth a whole new thread, so I've attached a systemui whose only change is the removal of the sfinder/qconnect bar. I believe you also have to delete the arm64/SystemUI.odex.art.xz file for things to work properly.
Click to expand...
Click to collapse
Awesome! Works perfectly! Thanks so much. Just a reminder to relative noobs like myself to change the appropriate permissions in the new SystemUI file to -rw-r--r--. I forgot to do so first try, and lost both the status bar and the lockscreen. Fixed now, but had a moment or two of panic...

Painless001 said:
Awesome! Works perfectly! Thanks so much. Just a reminder to relative noobs like myself to change the appropriate permissions in the new SystemUI file to -rw-r--r--. I forgot to do so first try, and lost both the status bar and the lockscreen. Fixed now, but had a moment or two of panic...
Click to expand...
Click to collapse
BINGO. Yea i forgot to mention that in my response, as well. Always fix permissions