Develop Bugs

[MOD] Auto-rotating Dialer + Call Screen [V3][2.3.3]

{
"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"
}
About
This is basically the stock dialer modded so that it would automatically rotate to landscape mode. (Samsung created the landscape mode for its car dock.) Update.zip files are attached. If you need it for any other version, you can either do it yourself using the information below or post your DialerTabActivity.apk (and tell me the ROM version so that others can use it too) and I'll do it for you. Requires deodexed ROM.
Changelog
v3: Respect user auto-rotate setting
v2r2: Fix bugs in auto-rotating call screen
v2: Added auto-rotating call screen
v1: Initial Relase
Technical Detail
The mod was created by editing com/sec/android/app/dialertab/DialerTabActivity.smali in DialerTabActivity.apk.
In the function onResume, replace
Code:
if-eq v0, v3, :cond_0
.line 206
invoke-direct {p0, v3}, Lcom/sec/android/app/dialertab/DialerTabActivity;->updateScreenOrientation(I)V
with
Code:
if-eq v0, v4, :cond_0
.line 206
invoke-direct {p0, v4}, Lcom/sec/android/app/dialertab/DialerTabActivity;->updateScreenOrientation(I)V
A shell script (tested on OSX, needs apktool and android tools in PATH) is also attached.
The call screen mod was created by editing several files in Phone.apk
com/android/phone/InCallScreen.smali, com/android/phone/InCallScreen$1.smali, com/android/phone/InVTCallScreen.smali
(Look for the diff file in attached source)
UPDATE: If anyone had any problems with certificates/dialer not working, I've uploaded new versions.
UPDATE2: v2r2 versions posted. The Froyo mods are untested, but should work. Please post your results.
UPDATE2: v3 versions posted. The Froyo mods will no longer be updated.
WARNING: XXJVK and XWJVB are for 2.3.3. Others are for 2.2.1. Please do not flash the wrong versions or you will experience bootloop.
Other versions available here
JVQ Odexed Version by $omator

thanks alot,now i can drive without bend my head 90 deg. when im calling hehe

this is GOLD !
many thanks and credit to you

This is nice, how do you edit the smali files? Sorry i dont have much experience yet but I already have smali and baksmali, do you use notepad or a command prompt to change the lines?
Sent from my HTC Mytouch 3g using XDA App

Any text editor, including notepad, will do. I don't use [bak]smali directly, but use apktool to extract the apk, edit using a text editor and use apktool to build it again. And then replace the AndroidManifest.xml, META-INF with the one from the old apk then zipalign before packing it into update.zip.

Big thanks..... i try with Froyo 2.2.1... Good Job

I've added a 2.2.1 version (ZSJPK). Feel free to request other versions, I have an automated shell script for creating them.

i think imho, this is the best mod EVER!!!!
lol...
*gets sgs windscreen car holder out*

owww, i've just moved to cm7. i would have loved this! good job man

If anyone had any problems with certificates/dialer not working, I've uploaded new versions. (Made a mistake in my script not replacing AndroidManifest.xml, XXJVB was okay because I did it manually.)

Cheers,i'll try it
ขอบคุณครับ

how do i install it?
i need some instructions...

Pick the update.zip which is the same as your ROM version (or you can try any near version). Then flash with CWM.

Option or something to activate this!? I've used XWJVB version flashed with CWM and the dialer in not auto-rotating! I am on XWJVB stock!Thanx!

Thank you very much
Is this mod can be applied to the in-call page ?:-
to be auto-rotatable just like the main Dialer page ?
Thanks

lazy_ursache said:
Option or something to activate this!? I've used XWJVB version flashed with CWM and the dialer in not auto-rotating! I am on XWJVB stock!Thanx!
Click to expand...
Click to collapse
You need auto-rotation on for it to work. And this is for deodexed ROMs, I don't think it works on stock.

Ok thanx! Sad that is not working also on odexed ROMs it is a fantastic mod!

There
This requires modifying Phone.apk, release will come later.
EDIT: Uploaded a v2 version for XWJVB, other versions will come later.

really cool stuff here !

I've moved to deodexed ROM for this mod! You are great! Thanx!

[Super Noob Guide] How To Decompile .apk & Recompile .apk In Just 2 Sec

This is an Easy Tutorial, How to Decompile .apk and Recompile .apk Files
Requirements
JDK (last version)
JRE (last version, usually included in JDK or Java)
Auto_Apktool 2.0.0
Here We Start-
1) Download and simply unpack Auto_ApkTool
2)Click on "autoapktoolmain.bat", prompt will open
{
"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"
}
3)put the apk you want to EDIT, in "_INPUT_APK"
4) Nw u Should Choose "option 6" for 'decompiling .apk
5) when option 6 is being selected, drag the apk from _INPUT_APK folder into the windows prompt and click enter
6) A Note window will appear, and will show IF the decompiling process has been done properly. Once you close that window, you will see the decompiled folder in _INPUT_APK folder
7) do your edits (xml, smali, or png, WHATEVER)
8) recompile with option 7 (NOTE: this time you MUST drag all the FOLDER, NOT the apk)
9) Once recompiling finished, u will Get a Dcompiled NOTE window that Shows your apk is sucessfully Compiled, Close that Window, Once open the decompiled folder, go to "dist" folder, and here you got your edited apk
10) NOW this is the Last step, since u cannot Sign System app, u will have to Copy the META-INF foldrer frm the Orginal apk to the edited apk, for more Info See the "Screen"
11) Rename the apk if Needed, and push it.

CREDITS -
Xavierjohn22 - the amazing author of AutoApktool , Hit thanks to Him Too.
&
Me
Downloads-
AutoApkTool
Click to expand...
Click to collapse
:victory: :highfive:
Note-
U can use apk tool but it is hard to use
Thats why i post these method time consuming n very easy [for noobs] lyk me..
U can also use auto apk tool 2.0.4 or higher

VTS(Virtuous Ten Studio) is easiest way to do not only de/recompiling but also accomplishing some more tasks related to android with easep how could I forget?)
Apk Multitool is also good and takes care of your edited files to be be automatically replaced in original apk, reducing the errors drastically

:good:

Guys just use vts its super super easy virtuos ten studio
Its damn too easy it has many features....
Sent from my GT-S5360 using Tapatalk 2

^^agreed
Sent from my GT-S5360 using Tapatalk 2

technosavie said:
Guys just use vts its super super easy virtuos ten studio
Its damn too easy it has many features....
Sent from my GT-S5360 using Tapatalk 2
Click to expand...
Click to collapse
I used only VTS to create the first and only s-rom,
Beautiful software indeed
--------------------------------------------------------------
By staring at this post you have waived your right to privacy
Complaints will be trolled accordingly

deathnotice01 said:
I used only VTS to create the first and only s-rom,
Beautiful software indeed
--------------------------------------------------------------
By staring at this post you have waived your right to privacy
Complaints will be trolled accordingly
Click to expand...
Click to collapse
Yes vts is best
Very Easy 2 use
Sent from my GT-S6102 using xda app-developers app

[MOD] [DEV] [JWR66V] [Deodexed] AOKP Circle Battery Percentage

Tested by myself, and it works great! Deodexed 4.3 ([JWR66V) Only.
{
"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"
}
Push to /system/app
chmod 644 or set permissions to rw-r-r
Reboot to recovery
Wipe cache
Wipe dalvik
Fix permissions
Reboot to system
Enjoy!
Download here
http://d-h.st/0Zy

jackpham said:
Tested by myself, and it works great! Deodexed 4.3 ([JWR66V) Only.
Push to /system/app
chmod 644 or set permissions to rw-r-r
Reboot to recovery
Wipe cache
Wipe dalvik
Fix permissions
Reboot to system
Enjoy!
Download here
http://d-h.st/0Zy
Click to expand...
Click to collapse
Thanks mate,
did you use original AndroidManifest? I was trying and doing the same mod with other battery icons, but... well, my navbar and statusbar disappeared!
Tiwiz

tiwiz said:
Thanks mate,
did you use original AndroidManifest? I was trying and doing the same mod with other battery icons, but... well, my navbar and statusbar disappeared!
Tiwiz
Click to expand...
Click to collapse
Did you sign it with the platform key?
Also, you can do this without messing with Xposed

Quinny899 said:
Did you sign it with the platform key?
Also, you can do this without messing with Xposed
Click to expand...
Click to collapse
If you mean using original AndroidManifest and META-INF, I just used original Manifest, there was no META-INF folder from my Apktool extraction (see screenshot below): I picked up the AndroidManifest.xml from the original one and pasted it inside the build after the first generation, then I generated the APK with the old Manifest.
Tiwiz

tiwiz said:
If you mean using original AndroidManifest and META-INF, I just used original Manifest, there was no META-INF folder from my Apktool extraction (see screenshot below): I picked up the AndroidManifest.xml from the original one and pasted it inside the build after the first generation, then I generated the APK with the old Manifest.
Tiwiz
Click to expand...
Click to collapse
No, I mean signing it with the platform key with a tool like Zipsigner on the device. That's the best way, copying back the meta-inf will not work.
Sent from my Galaxy Nexus using Tapatalk 4 Beta

Quinny899 said:
No, I mean signing it with the platform key with a tool like Zipsigner on the device. That's the best way, copying back the meta-inf will not work.
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Click to expand...
Click to collapse
Unfortunately I'm totally unprepared, I read somewhere here on the forum that META-INF was enough. Would you please link me Zipsigner and/or a procedure to better understand the process?
BTW, I really appreciate your help
Tiwiz

tiwiz said:
Unfortunately I'm totally unprepared, I read somewhere here on the forum that META-INF was enough. Would you please link me Zipsigner and/or a procedure to better understand the process?
BTW, I really appreciate your help
Tiwiz
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=kellinwood.zipsigner2&hl=en
Zipsigner

Quinny899 said:
https://play.google.com/store/apps/details?id=kellinwood.zipsigner2&hl=en
Zipsigner
Click to expand...
Click to collapse
With this one, I shall not replace AndroidManifest file but sign my APK with Platform Key, am I right? Then I can redistribute it?
Thanks again,
Tiwiz

tiwiz said:
With this one, I shall not replace AndroidManifest file but sign my APK with Platform Key, am I right? Then I can redistribute it?
Thanks again,
Tiwiz
Click to expand...
Click to collapse
Use apktool, change your resources, rebuild and use this to sign it. Then you're done
Sent from my Galaxy Nexus using Tapatalk 4 Beta

[GUIDE] How to add extra option in settings.apk

EXTRA APPLICATION OPTION IN SETTINGS MENU​
This is my first thread, so please ignore my errors.
We have seen custom ROMs having some extra options in settings. This is a guide of adding these options.
This guide is for Galaxy y, but also can work for devices with similar settings.apk (like Ace, duos etc.)
Prerequisites:-
1) A rooted phone (I can't strech how important this is )
2) Backup your orginal settings.apk
3) Basic knowledge of decompiling and recompiling.
Procedure:-
1)Decompile settings.apk and apk of the app you want to put. (I am decompiling Proximity Actions)
2) Go to decompiled app folder and open AndroidManifest.xml. Note Package and Target Class. (Marked with red circle Attachment # 1)
{
"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"
}
3) Open decompiled folder of settings. Go to /res/values/strings.xml. Open with Notepad++.
Enter code <string name="prxt_ctrl">Proximity Control</string> in the end before /resources>. You can edit red coloured text to anything which you want to appear in settings. You can also give any string name, but remember it.
4) You need an icon to put in settings(You can get it from that decompiled app). Resize it to 24x24 pixels (FOR GALAXY Y ONLY)
5) Put that icon in settings/res/drawable-Idpi with any name(remember it). I have given name ic_settings_prxt
6) Go to settings/res/xml/settings.xml. Open with Notepad++
7) Add code <com.android.settings.IconPreferenceScreen android:title="@string/prxt_ctrl" settings:icon="@drawable/ic_settings_prxt">
<intent android:targetPackage="novum.inceptum.proximity" android:action="android.intent.action.MAIN" android:targetClass="novum.inceptum.proximity.PA_Activity" />
</com.android.settings.IconPreferenceScreen>
Here string is used from step 3. Use icon from step 4. Package and targetClass from step 2.
8) Save and compile Settings.apk and complete formalities of recompiling.
9) Push Settings.apk to /system/app and set permissions to rw-r--r--.
10) Enjoy
PRESS THANKS IF HELPED. I REALLY NEED IT.

there is a similar thread. plz search before post. mods plz close this thread.
Galaxy Pop Plus'ımdan Tapatalk 2 ile gönderildi.

That guide you are talking about by PinapleOwl is different method. It is just how to add extra ACTIVITY with smali editing. Here you dont have to edit smali. Please note the difference before comment. Also this has detailed screenshots for noobs.
Sent from my GT-S5360 using xda-app
Using CWM........Busybox Commands........No I use my hands

Think the thread being referred to is
http://forum.xda-developers.com/showthread.php?t=2341389
Which has more options such as sub directory
Anyway it's a clear guide for anyone who needs simple directions

marcussmith2626 said:
Think the thread being referred to is
http://forum.xda-developers.com/showthread.php?t=2341389
Which has more options such as sub directory
Anyway it's a clear guide for anyone who needs simple directions
Click to expand...
Click to collapse
No. That guide has different Settings structure. It is for Xperia Arc where menus are classified by category.
In our Galaxy y, we don't have settings_header.xml.
Indeed both guides are similar, but I think a set of simple instructions would be helpful, so I have written this thing.

i cannot find android:targetPackage android:action etc

shadman0 said:
i cannot find android:targetPackage android:action etc
Click to expand...
Click to collapse
its the name of the apk in its manifest - decompile the target apk and look

I have Problem
marcussmith2626 said:
its the name of the apk in its manifest - decompile the target apk and look
Click to expand...
Click to collapse
Marcussmith2626 I have Build The App And Sign App After I have Place System/app and givr it permissions r w r r after reboot The Settings is Not Come in Launcher

shadman0 said:
Marcussmith2626 I have Build The App And Sign App After I have Place System/app and givr it permissions r w r r after reboot The Settings is Not Come in Launcher
Click to expand...
Click to collapse
If you have not edited Manifest of your SETTINGS APP (IMPORTANT), then you don't have to sign that APK. Just open both apks (newly compiled and original) in 7zip 7zip ONLY (Right click on apk ====> 7zip ====> Open archive)
Then drag META-INF of original apk to compiled apk and push to /system/app and change permission to 644 (rw-r--r--)

Same problem

A BIG Thanks for your help

hnkotnis said:
If you have not edited Manifest of your SETTINGS APP (IMPORTANT), then you don't have to sign that APK. Just open both apks (newly compiled and original) in 7zip 7zip ONLY (Right click on apk ====> 7zip ====> Open archive)
Then drag META-INF of original apk to compiled apk and push to /system/app and change permission to 644 (rw-r--r--)
Click to expand...
Click to collapse
OR you can patch service.jar with lucky patcher and see

Need help creating a flashable .zip

I want to achieve the following two tasks by flashing a .zip file in recovery:
1. Open the following file:
Code:
/system/etc/permissions/handheld_core_hardware.xml​
Add in the following lines right before the </permissions> closing tag at the end:
Code:
<feature name="android.software.vr.mode" />
<feature name="android.hardware.vr.high_performance" />
2. Open
Code:
/system/build.prop
Add this line:
Code:
ro.product.device=sailfish
So how can I do it?

Lownita said:
I want to achieve the following two tasks by flashing a .zip file in recovery:
1. Open the following file:
Code:
/system/etc/permissions/handheld_core_hardware.xml​
Add in the following lines right before the </permissions> closing tag at the end:
Code:
<feature name="android.software.vr.mode" />
<feature name="android.hardware.vr.high_performance" />
2. Open
Code:
/system/build.prop
Add this line:
Code:
ro.product.device=sailfish
So how can I do it?
Click to expand...
Click to collapse
Find an existing zip so you can see the structure of the file. SuperSU would be good so it uses a shell script rather than the Android mess.
You can use the sed built in to busy box to do the rest. Just call it from your shell script.
Sent from my ONEPLUS A3000 using Tapatalk

Lownita said:
2. Open
Code:
/system/build.prop
Add this line:
Code:
ro.product.device=sailfish
Click to expand...
Click to collapse
You do not need to spoof it as a Pixel for Daydream. Just the additions to /etc/permissions will work.

SpasilliumNexus said:
You do not need to spoof it as a Pixel for Daydream. Just the additions to /etc/permissions will work.
Click to expand...
Click to collapse
Hey man, thanks for answering!!!!! I already checked your magisk module for OP3T as I was thinking about using it with my current RR rom!! Spoofing as Pixel because I read that it is important for some apps to work: https://www.reddit.com/r/oneplus/comments/5spgpb/how_to_make_your_op3t_daydream_capable_requires/

Lownita said:
Hey man, thanks for answering!!!!! I already checked your magisk module for OP3T as I was thinking about using it with my current RR rom!! Spoofing as Pixel because I read that it is important for some apps to work: https://www.reddit.com/r/oneplus/comments/5spgpb/how_to_make_your_op3t_daydream_capable_requires/
Click to expand...
Click to collapse
Nope, I've tested it on OxygenOS, RR, and LineageOS (currently running), and it's not needed at all
Also, having interest in creating a flashable zip which inserts those lines you wanted in OP as I did not want to keep adding them manually when I do a ROM update, I've did a bit of research and figured how to do it:
This one searches for the word "mode" and inserts
Code:
<feature name="android.software.vr.mode" />
below in /system/etc/permissions/handheld_core_hardware.xml
Code:
sed -i -r 's/(.*mode.*)/\1\n <feature name="android.software.vr.mode" \/>/g' /system/etc/permissions/handheld_core_hardware.xml
This one searches for the word "high_performance" and inserts
Code:
<feature name="android.hardware.vr.high_performance" />
below in /system/etc/permissions/handheld_core_hardware.xml
Code:
sed -i -r 's/(.*high_performance.*)/\1\n <feature name="android.hardware.vr.high_performance" \/>/g' /system/etc/permissions/handheld_core_hardware.xml
As those words are the only ones in that XML, it made the process pretty easy. I'm still new to using sed, so maybe someone will come up (hopefully) with an even better solution. I haven't created a flashable zip yet as I'm not home, but tested these commands in TWRP and they run perfectly.
Credits to John WH Smith on Stack Exchange for the solution: http://unix.stackexchange.com/quest...-a-new-line-after-the-test-message1-using-sed
And jherran for the replace: http://unix.stackexchange.com/quest...tribute-to-existing-xml-file-using-sed-or-awk

Flashable ZIP attached.
EDIT: Screenshot.
{
"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"
}
Spoofing it as another device will make the Daydream apps available if you do these edits on a device that is already set up and synced with your Google account
If you do the XML edits on a clean install BEFORE booting to Android, no spoofing is needed in build.prop.

SpasilliumNexus said:
Flashable ZIP attached.
Click to expand...
Click to collapse
Thanks a lot! I just tested without sailfish spoofing in buildprop and the app called "Within" didn't work properly. After I added the line back, it worked again!