Good evening ladies and gentleman.
I have HTC Titan I (x310e) with developer unlock and I was unable install and launch Julien Schapman apps - Advanced Config Tool and RegistryEditor. I was looking for a solution and today I have that.
We have to (my movie):
1. Download xap files:
- Advanced Config Tool - http://www.touchxperience.com/forum/viewtopic.php?f=11&t=890 (working good only version 1.5.0.0 to install in settings)
- RegistryEditor - http://www.touchxperience.com/forum/viewtopic.php?f=20&t=593 (working good only version 1.1.0.0)
2. Rename extension from *.xap to *.zip.
3. Open these with system (Win7) support (not 7zip, WinRAR, etc.).
4. Cut file: WMAppManifest.xml and paste in other folder.
5. Open that file with system text editor (right click and select edit).
6. Remove line with text: "INTEROPSERVICES" and save the changes.
7. Copy this file to zip folder with app.
8. Change it back to a *.xap extension and now we can deploy him.
Enjoy
EDIT
SORRRY APP LAUNCH BUT NOT WORKING. I LOOKING FOR NEXT METHOD.
it is not possible. Interop is what is required to make the app work. So without it you can install it but it wont work hence there is no way to do what you want currently
Relatedly, this fact has been known for... ever since the Mago betas came out, I think? So, probably about half the lifetime of the OS. I guess when things are that old, it's easier to "discover" stuff that doesn't work than read the old threads.
Your phone is interop-locked. You can only install or run apps without ID_CAP_INTEROPSERVICES, unless those apps come from the Marketplace. As a general rule, if an app requests ID_CAP_INTEROPSERVICES (or other capabilities), that's because it's using it for something...
Budniu said:
Good evening ladies and gentleman.
I have HTC Titan I (x310e) with developer unlock and I was unable install and launch Julien Schapman apps - Advanced Config Tool and RegistryEditor. I was looking for a solution and today I have that.
We have to (my movie):
1. Download xap files:
- Advanced Config Tool - http://www.touchxperience.com/forum/viewtopic.php?f=11&t=890 (working good only version 1.5.0.0 to install in settings)
- RegistryEditor - http://www.touchxperience.com/forum/viewtopic.php?f=20&t=593 (working good only version 1.1.0.0)
2. Rename extension from *.xap to *.zip.
3. Open these with system (Win7) support (not 7zip, WinRAR, etc.).
4. Cut file: WMAppManifest.xml and paste in other folder.
5. Open that file with system text editor (right click and select edit).
6. Remove line with text: "INTEROPSERVICES" and save the changes.
7. Copy this file to zip folder with app.
8. Change it back to a *.xap extension and now we can deploy him.
Enjoy
EDIT
SORRRY APP LAUNCH BUT NOT WORKING. I LOOKING FOR NEXT METHOD.
Click to expand...
Click to collapse
Followed the method to insall Advanced Config. Now how can I uninstall it? Since I have 3 unsigned app limit, so I cant afford to waste a slot on an app that highly desirable but not useful.
elixir_pr said:
Followed the method to insall Advanced Config. Now how can I uninstall it? Since I have 3 unsigned app limit, so I cant afford to waste a slot on an app that highly desirable but not useful.
Click to expand...
Click to collapse
You can try to install ORIGINAL Advanced Config Tool file - you get error but uninstall actual version from the system.
At somepoint while i had the Xperia Sola, the 4.2 version of the Xperia Launcher by SeraJr constantly force closed, and eventualy all the launcers i had. Tried all solutions i could find, wipe chache wipe dalvik, use stock rom, reflash, nada. The reason, i thought, was the lack of ram, xperia sola had 512 RAM, but on xperia S the situation is different, it has 1 GB of ram and still FC then i found this
VERSION 1.
Create a Unix script file with no extension (I named it 97oom) with Notepad++ and put it in your i/system/etc/init.d/ folder and put this inside:
Code:
#!/system/bin/sh
sleep 60
PPID=$(pidof [B]com.estrongs.android.safer[/B])
echo "-17" > /proc/$PPID/oom_adj
Permissions: chmod 755 /system/etc/init.d/97oom (same as 10overclock)
You can also do it on the phone itself:
1. Make a copy of 10overclock
2. Renamed it to 97oom (I have a 98governor and a 99complete so...)
3. Deleted the text and put the text you see above
4. Set permissions
The bold text in the above code is the process name of the app that you want to protect!
You can also do this in GScript Lite with this:
Code:
PPID=$(pidof com.estrongs.android.safer)
echo "-17" > /proc/$PPID/oom_adj
This comes in handy for apps that don't load on bootup - just run a GScript for those apps
I suggest you get Busybox Installer and have it install the latest BusyBox (v1.19).
This ensures GScript doesn't spit out ugly stderr: messages.
GScript Tip: 1. Make a file (with any text editor) with the commands
................. 2. Rename it with an .sh extension (example 97oom.sh)
................. 3. Put it in sdcard/gscript folder
................. 4. Run GScript, Menu key, Add script, and click Load file, select a script and Save (leave SU checked)
Even better, you can make shortcut for any GScript.
Long press desktop > Shortcuts > GScript Lite > Select... BOOYA!
Then reboot to test!
Click to expand...
Click to collapse
I'm still testing myself, but at this point i can say that it works.
All credits go to zeppelinrox
VERSION 2
This i think is a better way to fix any launcher redraw, testet it myself and it works flawlessly. It seems that you need to patch the services.jar from the system framework in order to make the priority of the launcher from 6 to 1 (NOTE: only the launcher set to default will go to priority 1, any launcher is fine)
You can use Auto Memory Manager (AMM) to check the launcher's OOM priority
What you need:
1. Rooted ICS phone
2. Root Explorer
3. Deodexed stock or custom rom
Instructions:
1. Open up device browser http://android.mimic.ca/
2. File upload > choose file > Root Explorer > phone menu > home > system > framework > services.jar
3. This will exit to the ICS OOM Priority Charger webapp
4. Upload
5. Download > Save As "services.jar" > OK
6. Open Root explore and navigate to /sdcard/Download
7. Long tap services.jar > copy
8. Back > back > system > framework
9. Mount R/W
10. Paste > overwrite
11. Set permissions: long tap services.jar > permissions > rw-r--r--
12. Reboot
13. Use AMM app to check your launcer's OOM priority =1
14. Enjoy
All Credits for this mod UpInTheAir
After that you launcher will never be a problem
I'm not responsible for damages on your phone, use it at your own risk.
Please test and give feedback and if its ok dont forget do hit THANKS
If this was helpfull please press Thanks
Re: [MOD][FIX launcer redraws] Lock apps to memory
You can easily instal whole supercharger.
It wi be stronger, no redraws, lag free.
Sent from my LT26i
electrash said:
You can easily instal whole supercharger.
It wi be stronger, no redraws, lag free.
Sent from my LT26i
Click to expand...
Click to collapse
The V6 one?
Yess it may be, but i wated only the lock app part
Update first post, ver 2.
Force enable lockscreen rotation
Code:
setprop lockscreen.rot_override true
Force disable lockscreen rotation
Code:
setprop lockscreen.rot_override false
On devices that already can rotate, this does nothing.
Code should work on all AOSP ROMs with lockscreens that don't rotate, unless the code there has been modified.
Resets on reboot though I think
Great find. Thanks!
Thanks man, I have a DIY dock for mine and the fact I had to enter my PIN sideways everytime I unlock my device driving me insane.
Can this code be used on the fly? I'm using a app at the moment (called Rotate) which can enable, disable lockscreen rotation. however this is heavy on memory and I want to simply do this with a script in Tasker.
---------- Post added at 04:58 PM ---------- Previous post was at 04:37 PM ----------
Just ran this from terminal emulator as root and it worked! Awesome - but it is lost on reboot so I need to be able to run this as a script in tasker - scripting looks tricky in Tasker though. Open to ideas!
I have enabled rotation by modifying bools.xml file and now I get to know that JB 4.2 has different rotation texts to enable rotation!
How about Launcher?
privatesam said:
Just ran this from terminal emulator as root and it worked! Awesome - but it is lost on reboot so I need to be able to run this as a script in tasker - scripting looks tricky in Tasker though. Open to ideas!
Click to expand...
Click to collapse
If you run it from a terminal emulator, it's temporary. If you want it to be permanent, add lockscreen.rot_override=true to /system/build.prop
manumanfred said:
I have enabled rotation by modifying bools.xml file and now I get to know that JB 4.2 has different rotation texts to enable rotation!
How about Launcher?
Click to expand...
Click to collapse
On 4.1.2, you could add launcher.force_enable_rotation=true to make the default launcher rotate, but some say that doesn't work in 4.2 (I use Apex Launcher, so I haven't tried the stock launcher) and you have to modify bools.xml, as you stated. I don't know if it requires both the bools.xml edit and build.prop entry or not, though.
The build.prop change for the lockscreen works without the bools.xml edit, though.
Awesome. This worked for me on 4.1.2 as well. Thanks!
Really useful in the car since I don't have the official car dock. No more unlocking sideways!
Cilraaz said:
If you run it from a terminal emulator, it's temporary. If you want it to be permanent, add lockscreen.rot_override=true to /system/build.prop
On 4.1.2, you could add launcher.force_enable_rotation=true to make the default launcher rotate, but some say that doesn't work in 4.2 (I use Apex Launcher, so I haven't tried the stock launcher) and you have to modify bools.xml, as you stated. I don't know if it requires both the bools.xml edit and build.prop entry or not, though.
The build.prop change for the lockscreen works without the bools.xml edit, though.
Click to expand...
Click to collapse
I know that, that's why I have modified bools.xml file to enable rotation on launcher + lockscreen.
I think JB 4.2.x have also the changed code for launcher rotation...
manumanfred said:
I know that, that's why I have modified bools.xml file to enable rotation on launcher + lockscreen.
I think JB 4.2.x have also the changed code for launcher rotation...
Click to expand...
Click to collapse
Does anyone have an answer to whether they have changed the code in 4.2? I can't find a bools.xml file anywhere - and no one seems to point at it. Also, no one says exactly where the suggested code should sit in the build.prop file - at the end, in the 'build' section, at the front? And it doesn't work on android 4.2.2 as far as I can tell although the terminal emulator temporary method works. And while you're firguring that out - can you tell me a way (without an app) to get the screen to stay awake after rebooting? Why won't that option remain set in Developer Options?
dosent work for me
xaueious said:
Force enable lockscreen rotation
Code:
setprop lockscreen.rot_override true
Force disable lockscreen rotation
Code:
setprop lockscreen.rot_override false
On devices that already can rotate, this does nothing.
Code should work on all AOSP ROMs with lockscreens that don't rotate, unless the code there has been modified.
Resets on reboot though I think
Click to expand...
Click to collapse
I tried this command in the terminal and no error message came.i.e it got executed properly Then when i see the lock-screen it is always in portrait mode.
Cant manage to get it to landscape mode. My auto rotation is on.
I am on 4.2.2 and using NOVA launcher. Xperia S OPENSEMC ROM.
Any idea y i am not able to rotate my lockscreen ??
siddharthisback said:
I tried this command in the terminal and no error message came.i.e it got executed properly Then when i see the lock-screen it is always in portrait mode.
Cant manage to get it to landscape mode. My auto rotation is on.
I am on 4.2.2 and using NOVA launcher. Xperia S OPENSEMC ROM.
Any idea y i am not able to rotate my lockscreen ??
Click to expand...
Click to collapse
Run Terminal as root, type "su" (no quotes), then enter, then the command.
Cilraaz said:
... If you want it to be permanent, add lockscreen.rot_override=true to /system/build.prop
Click to expand...
Click to collapse
Thank you, this works perfectly with 4.2.2 (CM 10.1).
Here are the steps to do this, if someone is not too familiar with editing a file in the /system file system:
1. Install app "ES File Explorer", new version 3.0.0
2. In ES File Explorer, go into Tools > Root Explorer, Option Mount R/W
3. Choose /system to be mounted RW
4. Allow (permanent) Superuser permissions for this app
5. Go to /system and open file build.prop with ES Notice-Editor (this Editor will ask for superuser permission, others won't)
6. Choose "Edit" from the upper right Options in Editor
7. Scroll to the end of the file and add the line lockscreen.rot_override=true, beware of syntax corruption due to automatic grammar correction
7. Exit ES Notice-Editor, answer question "Do you want to save build.prop" with "Yes"
8. Leave ES File Explorer and restart the phone
That's it, - check after reboot that the logon lockscreen turns while you turn the phone (maybe with some delay while turning)
dark0shark said:
Thank you, this works perfectly with 4.2.2 (CM 10.1).
Here are the steps to do this, if someone is not too familiar with editing a file in the /system file system:
1. Install app "ES File Explorer", new version 3.0.0
2. In ES File Explorer, go into Tools > Root Explorer, Option Mount R/W
3. Choose /system to be mounted RW
4. Allow (permanent) Superuser permissions for this app
5. Go to /system and open file build.prop with ES Notice-Editor (this Editor will ask for superuser permission, others won't)
6. Choose "Edit" from the upper right Options in Editor
7. Scroll to the end of the file and add the line lockscreen.rot_override=true, beware of syntax corruption due to automatic grammar correction
7. Exit ES Notice-Editor, answer question "Do you want to save build.prop" with "Yes"
8. Leave ES File Explorer and restart the phone
That's it, - check after reboot that the logon lockscreen turns while you turn the phone (maybe with some delay while turning)
Click to expand...
Click to collapse
Thank you for this. I wasn't sure if there was a specific spot in build.prop where I had to insert the line. The temporary fix in Terminal Emulator worked for me, but now it sticks after boot! I was sick of having to unlock my device sideways when it was in my car mount. The only weird thing is that it smooshes my wallpaper instead of switching to the landscape orientation, but I can live with that.
laur3n.newm4n said:
... I was sick of having to unlock my device sideways when it was in my car mount.
Click to expand...
Click to collapse
Yes, the car mount in heads up position with the cables (USB-power and 3,5 audio jack) to the bottom were exactly my reason to add this option permanently, too. The position of this environment variable in the configuration file build.prop does not matter, it is just common sense to add additional lines at the end, so you can find them easily.
dark0shark said:
Thank you, this works perfectly with 4.2.2 (CM 10.1).
Here are the steps to do this, if someone is not too familiar with editing a file in the /system file system:
1. Install app "ES File Explorer", new version 3.0.0
2. In ES File Explorer, go into Tools > Root Explorer, Option Mount R/W
3. Choose /system to be mounted RW
4. Allow (permanent) Superuser permissions for this app
5. Go to /system and open file build.prop with ES Notice-Editor (this Editor will ask for superuser permission, others won't)
6. Choose "Edit" from the upper right Options in Editor
7. Scroll to the end of the file and add the line lockscreen.rot_override=true, beware of syntax corruption due to automatic grammar correction
7. Exit ES Notice-Editor, answer question "Do you want to save build.prop" with "Yes"
8. Leave ES File Explorer and restart the phone
That's it, - check after reboot that the logon lockscreen turns while you turn the phone (maybe with some delay while turning)
Click to expand...
Click to collapse
Thank you for outlining this -- it helped me remember what to do!
and kaferei
Jeffreycat said:
Thank you for outlining this -- it helped me remember what to do!
Click to expand...
Click to collapse
Indeed -- very helpful and worked for me as well!
basic build.prop editing to enable pie on sgh-i747m
Shibang said:
Indeed -- very helpful and worked for me as well!
Click to expand...
Click to collapse
Thanks for providing the info on this basic build prop prop editing !
Ive been reading CyanogenMod 10.1 – A Complete Hands-On Review & Guide
by Haroon Q Raja and really wanted to enable Pie,etc on my rooted Samsung SGH I747m. With your help I was able to edit my build prop as was suggested by a comment I picked up on to:
ro.product.manufacturer=LGE
ro.product.model=Nexus 4
This didnt make any difference. Is there something else that needs to be changed?
Samsung G3 SGH-I747M Rogers
Cilraaz said:
...
On 4.1.2, you could add launcher.force_enable_rotation=true to make the default launcher rotate, but some say that doesn't work in 4.2 (I use Apex Launcher, so I haven't tried the stock launcher) and you have to modify bools.xml, as you stated. I don't know if it requires both the bools.xml edit and build.prop entry or not, though.
The build.prop change for the lockscreen works without the bools.xml edit, though.
Click to expand...
Click to collapse
Redscorpian said:
Does anyone have an answer to whether they have changed the code in 4.2? I can't find a bools.xml file anywhere - and no one seems to point at it. Also, no one says exactly where the suggested code should sit in the build.prop file - at the end, in the 'build' section, at the front? And it doesn't work on android 4.2.2 as far as I can tell although the terminal emulator temporary method works. And while you're firguring that out - can you tell me a way (without an app) to get the screen to stay awake after rebooting? Why won't that option remain set in Developer Options?
Click to expand...
Click to collapse
No one can tell?
Some users who flashed the leaked JWR66N on their N4's report there is no full app rotation anymore in the Camera app, just the icons. So another change to feel optimistic about 4.3.
madd0g said:
Some users who flashed the leaked JWR66N on their N4's report there is no full app rotation anymore in the Camera app, just the icons. So another change to feel optimistic about 4.3.
Click to expand...
Click to collapse
Speaking of the camera, I played around with a iPad yesterday at the local store, i felt that Apple's shutter button have a better placement as compared to Google's. The shutter button is placed by the right side of the app, falls just nice of my thumb.
Beamed from my Grouper
I saw that this game is big sensation..So I was a little bit curious,and i found this
So If you wanna be a big guy in your team (friends) follow these steps (your device must be rooted!!)
1. Download this game from market
2. You need a file manager that can access root folders (ex. es file explorer)..And when you download these 2 you are ready to go
3. Run game,and play it until you crash (that will be very fast ) or immediately..
4. Just hit a home button
5. Run your's file explorer that can access root files,and in search type "flappy" and you will be navigated to "com.gears.flappybird" enter in that file
6. Then you will see folder "shared_prefs" and open that folder
7. You will see "FlappyBird.xml" and open it with text editor
8. And you will see code line
Code:
<int name="score" value = "1" /
9. Tap on options menu and tap edit
10. And instead of 1 type and number you want And tap options menu and save
11. Exit file explorer and press recent app's button and get back to the game..Tap to play again and when you crash in high score you will see the number that you type
This tutorial was made by me!
If you like it,you know what should you do
Tnx
Not on leaderboards
big noob said:
I saw that this game is big sensation..So I was a little bit curious,and i found this
So If you wanna be a big guy in your team (friends) follow these steps (your device must be rooted!!)
1. Download this game from market
2. You need a file manager that can access root folders (ex. es file explorer)..And when you download these 2 you are ready to go
3. Run game,and play it until you crash (that will be very fast ) or immediately..
4. Just hit a home button
5. Run your's file explorer that can access root files,and in search type "flappy" and you will be navigated to "com.gears.flappybird" enter in that file
6. Then you will see folder "shared_prefs" and open that folder
7. You will see "FlappyBird.xml" and open it with text editor
8. And you will see code line
Code:
<int name="score" value = "1" /
9. Tap on options menu and tap edit
10. And instead of 1 type and number you want And tap options menu and save
11. Exit file explorer and press recent app's button and get back to the game..Tap to play again and when you crash in high score you will see the number that you type
This tutorial was made by me!
If you like it,you know what should you do
Tnx
Click to expand...
Click to collapse
Well it does work. But the score doesn't appear on the leaderboards.
Not? Hmm..Try cleaning the game cache and try again..Cause it works for me..It shows if you put normal number
Sent from my HTC One X using Tapatalk 2
This method works for many games.
The reason it doesn't update on the leaderbords in Google Play is just simply because the game stores your score when you actually achieved it.
In other words; the shared preference value is only used for the dialog when you die.
Sent from my One X using XDA Premium 4 mobile app
Just Use GameCIH
That's all
i have searched but didn't find the file
sam53 said:
i have searched but didn't find the file
Click to expand...
Click to collapse
Use any root explorer and go to /data/data/com.dotgear.flappy.
Sent from my HTC One X
Nice. Thank you for sharing
Sent from my Nexus 5 using xda app-developers app