Database Info

[Q] Compiling AOSP Standalone apps

Hi, I've managed to edit, compile, and run the camera app on eclipse, to avoid compile the whole rom just to debug and try things.
(AOSP/CM9 to standalone app)
I just wanted to change the accesibility shutter button, but there are some issues:
I took sources from here: packages\apps\Camera (acual cm9 teamhacksung repo)
Then I removed all the AOSP references and added the correct libraries to make it work.
But the result of it was a different camera app, the differences are:
- The accesibility shutters works by default (power button) ☑
- There is no focus mode option in settings ☐
- Poor preview/picture quality ☑
- Glitched front face camera (green/black flickering) ☑
- etc ☐
(Seems like all the teamhacksung changes are not here)
Where do I need to take the sources to have our actual cm9 camera app to have the latest changes?
My objective is not to compile and finish this app in a standalone or a separated AOSP version, I just want to debug and edit stuff to see how is it working and then when I know that its working fine, push the edited files to the AOSP dir, and compile the whole rom.
Thanks in advance.
Here is the compiled .apk: http://www.mediafire.com/?9bi86dwgaln1abp
EDIT: Some issues are fixed by correcting the AndroidManifest.xml file.
EDIT2: All fixed http://forum.xda-developers.com/showpost.php?p=29418513&postcount=3

If your tree is updated and you just need to build a single part, you can use mmm
Code:
. build/envsetup.sh
lunch
mmm path/to/the/part/
So you don't have to worry about dependencies, libs etc and your sources are updated.
And if you just need to do changes in resources files, like xml files, images (like the wifi signal icon ) etc, you can add them in the overlay directory.
For example, if you need to do changes in config.xml of the Camera app:
Code:
mkdir -p devices/samsung/galaxysl/overlay/packages/apps/Camera/res/values/
and there create your config.xml, adding only the strings you want to override.

nice
Thanks, that's very useful info, so..
If I replace /device/samsung/galaxysl/overlay/packages/apps/Camera/res/values/config.xml (the only file) in my eclipse project it should work as the same app that when I do the mmm thing?
I will try that
EDIT: I've checked that config.xml and just toggle a flag (<bool name="wantsFocusModes">true</bool>)
So I just toggled that flag in my project and everything worked fine, also the alternative shutter.
The poor quality/front face bugs/glitches were becouse of my manifest file that I fixed later.
The question is: Why the accesibility/alternative shutter isnt working with the original one? The config.xml has nothing to do with the shutter >.< , maybe with permissions like this one:
<uses-permission android:name="android.permission.PREVENT_POWER_KEY" />
Click to expand...
Click to collapse
Btw my new Camera.apk works as I wanted to
Also checked this:
http://wiki.cyanogenmod.com/wiki/Loading_source_in_eclipse
and this:
To import the formatter, go to the preferences, section Java > Code Style >
formatter, then click on import and choose
development/ide/eclipse/android-formatting.xml
To import the import order, to go into Java > Code Style > Organize Import,
then click on import and choose development/ide/eclipse/android.importorder
Click to expand...
Click to collapse
Here is my Camera.apk compiled with eclipse, replace the Camera.apk in /system/app with this one. (Sorry for the size)
http://www.mediafire.com/?8plrf0hxxh02262
I was the only one with this "alt. shutter issue" right?

frapeti said:
Thanks, that's very useful info, so..
If I replace /device/samsung/galaxysl/overlay/packages/apps/Camera/res/values/config.xml (the only file) in my eclipse project it should work as the same app that when I do the mmm thing?
I will try that
EDIT: I've checked that config.xml and just toggle a flag (<bool name="wantsFocusModes">true</bool>)
So I just toggled that flag in my project and everything worked fine, also the alternative shutter.
The poor quality/front face bugs/glitches were becouse of my manifest file that I fixed later.
The question is: Why the accesibility/alternative shutter isnt working with the original one? The config.xml has nothing to do with the shutter >.< , maybe with permissions like this one:
Btw my new Camera.apk works as I wanted to
Also checked this:
http://wiki.cyanogenmod.com/wiki/Loading_source_in_eclipse
and this:
Here is my Camera.apk compiled with eclipse, replace the Camera.apk in /system/app with this one. (Sorry for the size)
http://www.mediafire.com/?8plrf0hxxh02262
I was the only one with this "alt. shutter issue" right?
Click to expand...
Click to collapse
No, you are not the only one. Actually it works, but you need to focus first.
I don't know if you built it with eclipse or mmm, but with mmm there's no png optimization and the resulting files are bigger.

loSconosciuto said:
If your tree is updated and you just need to build a single part, you can use mmm
Code:
. build/envsetup.sh
lunch
mmm path/to/the/part/
So you don't have to worry about dependencies, libs etc and your sources are updated.
And if you just need to do changes in resources files, like xml files, images (like the wifi signal icon ) etc, you can add them in the overlay directory.
For example, if you need to do changes in config.xml of the Camera app:
Code:
mkdir -p devices/samsung/galaxysl/overlay/packages/apps/Camera/res/values/
and there create your config.xml, adding only the strings you want to override.
Click to expand...
Click to collapse
Million thanks for the mmm trick and the link to cm web site! It is so hard to find information on building the sources.

May i use this in JB
Sent from my GT-I9003 using xda premium

Code for your App
Can I have code that can be compiled in Eclipse? Would you please email it to me @ [email protected]

Thank you so much for posting this question
Hi first of all billions of thanks, by getting an answer I can not build Settings.apk within few min,
My question is, I want to add activity in Settings.apk, for that I have done following code in AndroidManifest.xml
Code:
<activity android:name="com.android.settings.network.AirplaneModePreference"
android:taskAffinity="com.android.settings"
android:configChanges="orientation|keyboardHidden|screenSize"
android:parentActivityName="Settings"
android:label="Advance Airplane Mode">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.DEFAULT" />
</intent-filter>
</activity>
But still, when I want to start Activity in Settings.apk I am getting following an error
Code:
Process: com.android.settings, PID: 24946
android.content.ActivityNotFoundException: Unable to find explicit activity class {com.android.settings.network/com.android.settings.network.AirplaneModePreference}; have you declared this activity in your AndroidManifest.xml (which is in Settings/AndroidManifest.xml) ?
at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:2005)
at android.app.Instrumentation.execStartActivity(Instrumentation.java:1673)
at android.app.Activity.startActivityForResult(Activity.java:4587)
at android.app.Activity.startActivityForResult(Activity.java:4545)
at android.app.Activity.startActivity(Activity.java:4906)
at android.app.Activity.startActivity(Activity.java:4874)
at android.content.ContextWrapper.startActivity(ContextWrapper.java:379)
at android.support.v7.preference.Preference.performClick(Preference.java:1139)
at com.android.settingslib.RestrictedPreference.performClick(RestrictedPreference.java:78)
at android.support.v7.preference.Preference.performClick(Preference.java:1107)
at android.support.v7.preference.Preference$1.onClick(Preference.java:172)
at android.view.View.performClick(View.java:6597)
at android.view.View.performClickInternal(View.java:6574)
at android.view.View.access$3100(View.java:778)
at android.view.View$PerformClick.run(View.java:25906)
at android.os.Handler.handleCallback(Handler.java:873)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:193)
at android.app.ActivityThread.main(ActivityThread.java:6729)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)
Do you have any idea, then please let me know, thanks alot in advance

How to decrease the number of home screens of jellybean stock launcher?

Hey guys, I need some assistance of those who know please. I decompiled the launcher2.apk of eos Xoom ROM and made changes to
res/layout-port/launcher.xml
And to
res/layout-land/launcher.xml
By deleting some lines related to launcher screens. By default they come 5, I made them 3.
<include android:id="@id/cell1" layout="@layout/workspace_screen" />
<include android:id="@id/cell2" layout="@layout/workspace_screen" />
<include android:id="@id/cell3" layout="@layout/workspace_screen" />
<include android:id="@id/cell4" layout="@layout/workspace_screen" />
<include android:id="@id/cell5" layout="@layout/workspace_screen" />
I also made launcher:defaultScreen="1" to set the default screen to be the middle one.
I compiled the apk and replaced the original one with the same permission , however' the launcher remains with 5 screens...
Can anyone please point out how to get around this?
The way I compiled is using apktool manager and deleted resources.arcs from the keep folder !!! Does this need to be signed even if it is a system apk?
As soon as this works, I thought to provide a mod for xoomers...
Sent from my MZ601 using Tapatalk 2

Guys... no one?!!
Come on.... someone must have an answer here.
I decompiled the modded launcher and found the changes I made are gone and back to 5 screens !!
Sent from my MZ601 using Tapatalk 2

Have you tried adding workspaces? I for one would like 7 instead of 5.
Off topic: are there any launchers that work like compiz fusion under ubuntu?
Sent from my SGH-I717R using xda premium

Eun-Hjzjined said:
Have you tried adding workspaces? I for one would like 7 instead of 5.
Off topic: are there any launchers that work like compiz fusion under ubuntu?
Sent from my SGH-I717R using xda premium
Click to expand...
Click to collapse
The problem is that I am trying to make the changes I do persistent . However, whenever I compile the apk, it goes back to 5 screens. If I can manage removing screens, I will be able to add more. All I need is a little help of guideness if someone knows, plz step in...
Sent from my MZ601 using Tapatalk 2

wesamothman said:
The problem is that I am trying to make the changes I do persistent . However, whenever I compile the apk, it goes back to 5 screens. If I can manage removing screens, I will be able to add more. All I need is a little help of guideness if someone knows, plz step in...
Sent from my MZ601 using Tapatalk 2
Click to expand...
Click to collapse
ok you have it right, however i can 99.99% guarantee you that your problem is with apkmanager
becasue there is no why that once you make the changes that the changes will "revert" back to that what is was previously
use good old fashion cmd or terminal ( if on linux) or even simpler build it from the source,
however if you insist on using apktool use these ( which are moddified for ICS/JB) https://dl.dropbox.com/u/25886627/apktoo_8.15.12.zip
only follow these steps to the "T"
put the zip anywhere, open cmd ( command promt)
and CD to C:\were\extracted\zip\is\
and then take the framework-res.apk and the Launcher2.apk
and place both in the same folder you extraacted zip to
now in cmd type
apktool if framework-res.apk
followed by
apktool d Launcher2.apk
now this will decompile the apk to :\were\extracted\zip\is\Launcher2\
make changes
back in cmd type
apktool b Launcher2
now navigate to :\were\extracted\zip\is\Launcher2\build\apk\
copy the original Launcher2.apk from :\were\extracted\zip\is\ to :\were\extracted\zip\is\Launcher2\build\apk\
OPEN not extract the apk with 7zip ( or any archive manager) and now click and highlight from the :\were\extracted\zip\is\Launcher2\build\apk\ the res folder the classes.dex file and the resouces.arsc and drag them into the root of the Launcher2.apk that is open in 7zip
now that is the ready file to be sent to device
about signing...
system apps you dont sign becasue you dont have the authers signing tools, so if you try to simple sideload it an error of mismatching keys will prevent the app from installing
becasue we are flashing it ( or adb push) signing is not needed.
now i have not looked at the launcher as far as the amoutn of home screens ( done some customization for my own use on the n7) but what you have said you did should without a doubt work

runandhide05 said:
ok you have it right, however i can 99.99% guarantee you that your problem is with apkmanager
becasue there is no why that once you make the changes that the changes will "revert" back to that what is was previously
use good old fashion cmd or terminal ( if on linux) or even simpler build it from the source,
however if you insist on using apktool use these ( which are moddified for ICS/JB) https://dl.dropbox.com/u/25886627/apktoo_8.15.12.zip
only follow these steps to the "T"
put the zip anywhere, open cmd ( command promt)
and CD to C:\were\extracted\zip\is\
and then take the framework-res.apk and the Launcher2.apk
and place both in the same folder you extraacted zip to
now in cmd type
apktool if framework-res.apk
followed by
apktool d Launcher2.apk
now this will decompile the apk to :\were\extracted\zip\is\Launcher2\
make changes
back in cmd type
apktool b Launcher2
now navigate to :\were\extracted\zip\is\Launcher2\build\apk\
copy the original Launcher2.apk from :\were\extracted\zip\is\ to :\were\extracted\zip\is\Launcher2\build\apk\
OPEN not extract the apk with 7zip ( or any archive manager) and now click and highlight from the :\were\extracted\zip\is\Launcher2\build\apk\ the res folder the classes.dex file and the resouces.arsc and drag them into the root of the Launcher2.apk that is open in 7zip
now that is the ready file to be sent to device
about signing...
system apps you dont sign becasue you dont have the authers signing tools, so if you try to simple sideload it an error of mismatching keys will prevent the app from installing
becasue we are flashing it ( or adb push) signing is not needed.
now i have not looked at the launcher as far as the amoutn of home screens ( done some customization for my own use on the n7) but what you have said you did should without a doubt work
Click to expand...
Click to collapse
Thx a million times. I will do as said
Sent from my MZ601 using Tapatalk 2

Hi runandhide05. First allow me to send you a bigggggg thank you for your apktool. It really was apktool problem.
I did as you suggested, still, didn't work from the first time (modified to 3 screens) although the changes were persistent this time. so, in addition to the above files, i had to modify the following as well:
workspace.xml in layout-sw720dp
and public.xml in res/values in which I had to delete
<public type="id" name="cell4" id="hex val xxxxx" />
<public type="id" name="cell5" id="hex val xxxxx" />
So, now I tested with these changes and I got 3 screens
I will try to do 1 screen, and 7 screens.
Thanks again. you are truly appreciated.
EDIT: 1 Screen is successful too. I will try 7 soon.
EDIT: 7 Screens is successful too
I will try to write a flashable zips for them and post them as mods ...

wesamothman said:
Hi runandhide05. First allow me to send you a bigggggg thank you for your apktool. It really was apktool problem.
I did as you suggested, still, didn't work from the first time (modified to 3 screens) although the changes were persistent this time. so, in addition to the above files, i had to modify the following as well:
workspace.xml in layout-sw720dp
and public.xml in res/values in which I had to delete
<public type="id" name="cell4" id="hex val xxxxx" />
<public type="id" name="cell5" id="hex val xxxxx" />
So, now I tested with these changes and I got 3 screens
I will try to do 1 screen, and 7 screens.
Thanks again. you are truly appreciated.
Click to expand...
Click to collapse
ah, sorry completely forgot about the public XML. glad u got it
Sent from my Galaxy Nexus using Tapatalk 2

runandhide05 said:
ah, sorry completely forgot about the public XML. glad u got it
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Dear runandhide, your brilliant advises/expertise is what helped me getting these mods in place. Thx again trillion times and I shall never forget that. I will finalize the flashable zips as mods in dev forum for xoomers of team eos jellybean interest.
Sent from my MZ601 using Tapatalk 2

Awesome work. Pm me when you have 7 screens cwm.zip
EOS3 N132 @ MZ604 [XDA HD]
Stock ICS @ SGH-i717R [XDA Premium]

Eun-Hjzjined said:
Awesome work. Pm me when you have 7 screens cwm.zip
EOS3 N132 @ MZ604 [XDA HD]
Stock ICS @ SGH-i717R [XDA Premium]
Click to expand...
Click to collapse
It will available today on DEV Forum. 1 screen, 3 screens, 5 screens (default) and 7 screens.
Keep an eye on the dev section.

Here is the link for the mods. 1,3,5,7,9 screens mods added.
http://forum.xda-developers.com/showthread.php?p=30306937
Sent from my MZ601 using Tapatalk 2

[GUIDE] Make Google Camera save at 100% Quality (4 MB) photos [TW][AOSP][ALL PHONES]

Introduction
Google Camera uses media_profiles.xml file where the Image quality is never set to 100 except if you're using a custom ROM where it is set by the ROM developer.
As a consequence, Google Camera and maybe other camera apps that works similarly, saves photos at around 600 kb in Galaxy S4. This is a lot of compression and may disappoint users who prefer the Google Goodie.
All thanks to @Alberto96 who brought this into light in his amazing ROM GearCM (Don't forget to thank him :highfive: )
Note: ROOT is Required
The Guide
Head on to system/etc and get the file "media_profiles.xml". You can back it up for your convenience.
You can use a PC for quick Find and Replace.
Open the file via an editor and find the code:
Code:
<ImageEncoding quality="90" />
<ImageEncoding quality="80" />
<ImageEncoding quality="70" />
(Tip: just search "ImageEncoding" and you'll get right there as the quality values can be different)
You'll find this three line code at two places and will be similar at both the places.
All you have to do is make it like this:
Code:
<ImageEncoding quality="100" />
<ImageEncoding quality="95" />
<ImageEncoding quality="90" />
Change to this code at both the places and save it. Then obviously put this file and replace it with original one at system/etc
Make sure and check if the permissions are rw-r--r--
Reboot and Enjoy taking Full Quality and Uncompressed photos from Google Camera :victory:
Don't forget to press Thanks button if you find this useful
Source: @Alberto96 's Github commit (https://github.com/GearCM/android_d...mmit/ba2f5d83665197b17bc68b9480986430e5d7ef3a)
All credits goes to him :angel:

thank for this TUT i really hate to use google camera for it quality in AOSP and CM rom but next time i diffidently use it when install AOSP or CM rom

[video] [Guide] enable WhatsApp calling feature.. any device (4.4+)

video link https://www.youtube.com/watch?v=8RlIxhEJEOw
STEPS:-Install the latest apk (Of course)
Open any root explorer (es file explorer preferred )
and navigate to /data/data/com.whatsapp/shared_prefs/com.whatsapp_preferences.xml
Add these 2 lines anywhere in the file but within the <map></map> and save
<boolean name="call" value="true" /> <string name="call_allowed">all</string>
now force stop WhatsApp and open it again .... and you are done
Not able to post kink but video id = 8RlIxhEJEOw
Edit if any one can post link then plz add that video...thanks

Seems no one interested

Seems like not working.
I got the call tab, but anyone I'm trying calling to, it's just getting disconnect immediately.
(all the people I tried have the updated version)

How to find and edit AndroidManifest.xml on android 10 non-root after the installatio

How to find and edit AndroidManifest.xml on non-rooted android 10 after the installation of the APP,
do we even have AndroidManifest.xml at all on the app folder, or that's just a file in the pkg that's being used to install the program with certain parameters.
I am trying to edit
<application>
...
android:allowBackup="true"
...
</application>
so I can make a backup of the app's datas via Hellium
THanks