Those who keep switching between ROMs and are addicted the gesture anywhere option (like me [emoji14] ) , know how annoying it is to lose all the gesture shortcuts.
Not anymore!
In Most of the ROMs, the gesture shortcuts are saved in
Code:
/data/system
folder in a file named "ga_gestures".
(IN PAC-MAN ROM IT'S IN THE
Code:
.pac/gestureanywhere
FOLDER IN THE INTERNAL STORAGE)
Before changing your ROM, copy the ga_gestures file to your sd card.
After you install a new ROM (Only the ones who has gesture anywhere)
Open the file manager in root mode, browse to the
Code:
/data/system
folder and paste the ga_gestures file WITH PERMISSIONS SET AS 0644 (rw-r--r)
(If you've switched to the Pac Rom then create a .pac folder in the internal storage and inside it, another "gestureanywhere" folder and copy the ga_gestures file here.) and enable gesture anywhere in the settings.
All your gestures will be restored
Happy flashing
Sent from my XT1521 PAC-MAN Rom using Tapatalk
Related
Quick question. It says put the file/folder in the root of your SD Card, Boot into recovery, then flash the zip file, for example Gingerbread Keyboard, but every time you boot into recovery, it just brings up Windows Mobile, help?
Gv2004 said:
Quick question. It says put the file/folder in the root of your SD Card, Boot into recovery, then flash the zip file, for example Gingerbread Keyboard, but every time you boot into recovery, it just brings up Windows Mobile, help?
Click to expand...
Click to collapse
There is no such thing as "Recovery" for us since we run off the SD card. You will have to use something like "Root Explorer" or something with root rights and copy and paste it to system>>app. Be sure to copy the lib that comes with the keyboard. That one will go into System>>lib. If you have any troubles you can PM me if you like.
P.S. Questions should go in the Q&A section, just a heads up man.
Forgot to mention. When I say copy and paste, I mean the actual app and lib that is inside the folder. You will have to unzip it first and you will see what I am talking about once you see it. One with say .apk at the end (which is the app) and one will have a .lib at the end which is the lib file.
I unzipped the file, I have a folder called "App", which as the .apk, and a folder called "Lib" which has the ".lib", so I want to copy and paste the .lib into system/lib, and the app in system/app, do I put both files on the root of my SD card first? and once I copy and past both into Root Explorer System/lib and System/app, what do I do next?
Gv2004 said:
I unzipped the file, I have a folder called "App", which as the .apk, and a folder called "Lib" which has the ".lib", so I want to copy and paste the .lib into system/lib, and the app in system/app, do I put both files on the root of my SD card first? and once I copy and past both into Root Explorer System/lib and System/app, what do I do next?
Click to expand...
Click to collapse
just reboot after that, infact just keep going on market and d/l a few things and it should update to the newer version itself, hope this helps.
just use titanium backup, I backed up the keyboard along with my apps so if I switched builds and it does't have the gingerbread keyboard, it will add it when do an app restore. One thing you have to manually select the keyboard from the app list, long press and backup.
just do an adb push it is the easiest way.
download the gingerbread keyboard (LatinIME.apk) and the lib file (libjni_latinime.so)
(assuming you have the sdk installed and you have usb debug turned on)
in command prompt, navigate to the folder that contain these two files.
then type: adb push Latinime.apk /system/app/ (press enter)
then type: adb push libjni_latinime.so /system/lib/ (press enter)
then you should have the new keyboard installed!
When I am not traveling, I have wifi coverage at work and home, and I turn off the cell radio of my Note tablet to conserve battery use. The easy way is to enable Airplane mode, and then turn on wifi. However, you would have a persistent airplane icon showing up in the status bar. This thread will provide instruction on how to remove that icon.
First, I should acknowledge this thread for posting the general approach, which I modified to work specifically for the Note 10.1 (2014) with TW-based rom.
1. Your tablet must have root access, and a root file browser. I use ES File Explorer.
2. Browse to /System/priv-app, copy the file 'SystemUI.apk' and paste it in another directory (e.g., Document folder)
3. Transfer the file to a Windows computer
4. Open the file with Winrar, do not extract. Just browse the content within Winrar.
5. Go to /res/drawable-xhdpi, look for the "stat_sys_signal_flightmode.png" file. Delete this file within Winrar.
6. Exit Winrar. It automatically save the file (SystemUI.apk). Transfer it back to the Note tablet (e.g., Document folder)
7. Use ES File Explorer, copy the (new) SystemUI.apk to "/System" folder ***(NOT the "/System/priv-app" folder)
8. Once inside the /System folder, change file permission of SystemUI.apk to rw- r- r- (R/W for owner, R only for Group and Other)
9. Move (Cut and Paste) the SystemUI.apk file from "/System" folder to the "/System/priv-app" folder
10. Restart, and you should see the little Airport icon gone forever. (Airplane mode on/off still functions normally)
This method has been tested on the xKat rom by hanspampel. However, it should work on stock other deodexed TW roms with root, since the systemUI.apk location and the way it defines the status bar icons are the same.
PS. On the web, some suggested that ROM Toolbox Pro offers the function to modify the status bar icons. I have tested that and I did NOT work at all. As far as I know, the above the only method that works at the moment.
[Update] This method does NOT work on stock ROM, as the apps are still odexed. So you couldn't just replace the SystemUI.apk with a new one by overwriting.
[Update 2] I got it to work with stock Roms, by taking a SystemUI.apk file from a deodexed TW rom (like the xKat ROM from hanspampel), and modifying it (deleting the png file). Finally, I removed also the SystemUI.odex (from the stock ROM) before overwriting the System.apk with the modified one (from deodexed ROM).
Hi devs. Hi users. Hi testers!
I made two zips that might help you in some random point of time in future.
:laugh:
Both zips are flashable via recovery. Note that I have only tested working on aosp and cm-based roms. No custom skinned-oem ROM tested. However, it would be good if you provide info on what roms they work (or not)
This zip will remove the password/pin/pattern from your lock screen and reset it to swipe-to-unlock mode.
Not tested with smart lock modes.
Link : https://drive.google.com/file/d/0BxkDSj8MtdPQQTQ4a1VWQl8wME0/view?usp=drivesdk
This zip allows you to authenticate ADB from device, without booting the ROM first. Useful for devs who need ADB access even while booting the ROM for the first time.
Things you must have :
Code:
1) A pc which you have previously used to authenticate ADB access.
2) The zip from my link.
3) Some non-noob brain. Majorly this zip is for devs.
How to proceed :
Code:
1) First we need to obtain a file named "adbkeys.pub".
1a) For windows, go to the windows drive (usually c: drive) and browse to /users/(your-username-here)/.android/
1b) For most Linux distros : go to home directory, browse to /.android/
Generally .android will be hidden by default. In that case, just enable hidden files and folders from folder view options.
2) After you get the adbkeys.pub file, open it with a text editor. You will see a code there. Copy all of that code. Or use the shortcuts (ctrl+A) and then (ctrl+C).
3) Extract my zip. You will see a file in /data/misc of the extracted zip. Open that file with text editor. Erase any previous text in my file. Or use the shortcut (ctrl+A) and then (del). Paste the previously copied code into that file. Or use the shortcut (ctrl+V).
4) Save the file, rezip the extracted folders (which are data and meta-inf).
5) Flash that final zip file from recovery.
Link for ADB zip : https://drive.google.com/file/d/0BxkDSj8MtdPQdkZNeVp6U3ppR0k/view?usp=drivesdk
Please hit thanks button if it helps you
Hi. I flashed snapdragon camera v2. But it stops.
Then i want to remove the android icon with the text com.android.cameralauncher. But i cannot find. It. I tryed flashing the uninstal. And searched with a rooted file explorer. But i still have not located the file. Who can help me?
This is also me something went wrong with my account.
60nine said:
ok... i did it this way (using ES file explorer)
1. extract the zip to sd card somewhere
2. under "system/priv-app" > create a folder called "SnapdragonCamera"
3. give the folder "drwxr-xr-x" permissions
4. copy "SnapdragonCamera2.apk" to that folder and give it "-rw-r--r--" permissions
5. copy the "lib" folder (from the zip you've extracted) to "SnapdragonCamera" folder and give it the same permissions as the parent folder has ("drwxr-xr-x")
6. inside the "lib" folder there is also "arm" folder (give it the same "drwxr-xr-x" permissions)
7. inside that "arm" folder there are two ".so" files - give them "-rw-r--r--" permissions
8. reboot
i have to say it's a nice camera and i've used quite a few camera apps so far...
at the first glance - photo quality is the same as with the xdabbeb camera, but i like the UI better...
my device details:
- LG G2 (d802) running somboons stock 30f lollipop rom
- dorimanx kernel (v5.9.2 latest)
- xdabbeb camera and advanced drivers installed
Click to expand...
Click to collapse
Yep this was also the solution for my problem
After update from nougat to oreo, I've have problem with integration updated apps in to /system.
I do it like this:
1. copy apk file from data/apk to sd card
2. rename copied apk file to name of /system apk
3. extract lib folder from apk
4. copy newer file to proper folder in /system/app or /system/priv-app and replace file in it
5. Copy lib files extracted form apk to right folder /system/lib or /system/lib64
6. Uninstall update from /data/app
7. reboot + dalvik-cache wipe
In nougat it was working, but in oreo, app after integration, breaks. It cannot be open, and app name changes to random words (ex. google docs name changes to "write com.android").
To repair integrated apps I have to perform a full /data/ wipe.
Is it a some kind of protection? How to do it properly?
TitaniumBackup and Link2SD cannot integrate updates to rom properly without errors since Lolipop.
So no one knows?
or just nobody wants to write?