Related
So 2 rom teams. Savaged-Zen and Evervolv both by stock utilize the 6 bar and 100 battery mod in there themes. With the recent addition of Theme-Chooser in the roms, we've come together to make a standard for Theme Dev's to utilize these mods in their themes, and let the system be smart and know how to change it in the backend framework to properly use the mods.
To add a 6 bar mod or the 100 battery mod, add the images into the theme. and modify the below file
res/values/theme.xml
Code:
<resources>
<style name="Theme Name" parent="@android:style/Theme" />
//for signal mod set to true if not used you dont even need this line
<boolean name="extra_theme_compatibility_signal">true</boolean>
//for battery mod set to true if not used you dont even need this line
<boolean name="extra_theme_compatibility_battery">true</boolean>
</resources>
wow....i seriously cant figure out how to do this....thanks for the info tho....i never did this before so its all new to me.....im sure ill figure it out sooner or lata, cause it'll drive me crazy...thanks man
See Post 21 for guide on how to add modify your apps to appear in the launcher....
Orignal post below...
Hi,
Ok, it really annoyed me that when I flipped open the game pad I could only see the apps Sony Erricson allowed.... I have made some progress on this front, just not a 100% working fix yet
I'm not an expect, so please don't flame me if this is useless info!
Here goes the instructions....
I will warn those who have little skill in editing files this is not for you!
Here is how I added Solitare (free app from the android market) as a test to the Xperia Play Launcher....
First browse to
data/data/com.sonyericsson.semcsuite/databases
copy the to content.db file to your computer
edit the content.db
with SQLite (which you can download for free)
The info you need to edit is under browse data in SQLite, you need the pkg name of the app you want to include inside, as well as the full name of the app you are inserting… I simply replaced an app I wasn't bothered about in the launcher, my assumption would be that you can insert more by following the numbering convention used!
In the cover column you need to use -1 as the cover name and false under the menu...
then save the file
Now reboot the phone open the xperia play app, click on more games…. Then copy over the file…. I copied over the file while on more games….
Then kill the app in the settings (in mine shows as Android System), finally reopen the app and the added applications will show!
You then have the added apps you want in the launcher
Here is a screenshot of the added solitaire app as a test:
imageshack.us/photo/my-images/821/screenshot2zm.png
The big problem I have found so far is that the app very frequently ovewrites the .db For example on reboot or sometimes randomly, so at the moment it's not an actual fix...
I have attempted making the file read only but this crashes the app on opening...
But progress is progress any ideas moving forward? It would be nice to be able to slide open your play and see a bunch of emulators
Chris
AndroHero said:
Look in the database.db file in /data/data/com.sonyericsson.semcsuite/database
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
i told them all they needed to edit the database.db but no1 beleved me lol
AndroHero said:
i told them all they needed to edit the database.db but no1 beleved me lol
Click to expand...
Click to collapse
Just found your old thread, damn could have been here sooner! Oh, well progress still made
So much better knowing I can slide open my play and see all my emulators!
I've found out that once you get the hacked.db file on the play and get it to open correctly provide you press the home button and not the back button then it stays put Hopefully it should stay in place unless I accidently quit the app or need to reboot!
Still not a permanant fix, but close enough until we figure out how to stop the app replacing the edited file!
Here are two new screenshots completed with emulators hehe
imageshack.us/photo/my-images/853/screenshotye.png/
imageshack.us/photo/my-images/200/screenshot1kv.png/
The only downside is that the app blows up the icon of the edited in app, so it looks a bit pixelated - but I really don't care about that!
Chris
deepestblue said:
Just found your old thread, damn could have been here sooner! Oh, well progress still made
So much better knowing I can slide open my play and see all my emulators!
I've found out that once you get the hacked.db file on the play and get it to open correctly provide you press the home button and not the back button then it stays put Hopefully it should stay in place unless I accidently quit the app or need to reboot!
Still not a permanant fix, but close enough until we figure out how to stop the app replacing the edited file!
Here are two new screenshots completed with emulators hehe
imageshack.us/photo/my-images/853/screenshotye.png/
imageshack.us/photo/my-images/200/screenshot1kv.png/
The only downside is that the app blows up the icon of the edited in app, so it looks a bit pixelated - but I really don't care about that!
Chris
Click to expand...
Click to collapse
that looks really cool maybe a line in one of the .xml files can be changed in the .apk to get it to read from a diffrent (modded) file, then it dosent matter if it rewrites the database.db file
Could the whole db edition be done through an app?
Yes, we know, this is nothing new. We've already known about this for weeks. The problem of course is that it has to be populated manually. We've been searching for a way to do this automatically just by looking at how it works and doing what needs to be done to tell it "hey, I should be on this list" whenever it rebuilds the database.
Well so far good news, the xperia play app has yet to overwrite the file, so I guess leaving it the app open and not quiting, is possibly a very good temporary solution.
AndroHero said:
that looks really cool maybe a line in one of the .xml files can be changed in the .apk to get it to read from a diffrent (modded) file, then it dosent matter if it rewrites the database.db file
Click to expand...
Click to collapse
Unfortunately, after taking a look at the xml files no joy
There doesn't seem to be any reffrence to writing to the .db or that location...
Within the apk, there is a searchable.xml file though where the app is asking to search. So, possibly changing this so it searches for something else? hmm
The problem is if you change it to something else then I assume it would create a blank .db file! LOL But this might be a way forward... Feel free to take a look at the included xml file of the launcher here:
mediafire.com/?2eqtw1f0358omp2
Logseman said:
Could the whole db edition be done through an app?
Click to expand...
Click to collapse
Probably, if someone wanted to create such an app... But editing the .db file is not so hard, provided you are not wanting to change things all the time! I'd write up step by step instructions, so it should be fairly easy...
The problem at the moment is that it is not a full solution to our problem...
zerojay said:
Yes, we know, this is nothing new. We've already known about this for weeks. The problem of course is that it has to be populated manually. We've been searching for a way to do this automatically just by looking at how it works and doing what needs to be done to tell it "hey, I should be on this list" whenever it rebuilds the database.
Click to expand...
Click to collapse
I've had a scan though the past posts, and yes your right the .db file was known about for weeks... But unfortunately not followed though, no one actually attempted to edit the .db file nor get the edited file to work or at least not that I can see.... It's a shame really as we could have been here sooner...
Actually, I have an idea of how the app decides what should go into the database... I believe it is rather simple how the app works... The app will search installed apk, then my assumption would be that it would look at the AndroidManifest.xml of said installed apps for an xperiaplayoptimized_content tag.
An xperiaplayoptimized_content tag can be seen in the AndoridManifest.xml of two free apps on the market Cyberlords - Arcology, Happy Vikings.... I've not checked any other apps from the market, but please check more - maybe I'm wrong .
The problem is if this is how the app works and is needed in every app, it would mean adding to evey app we wanted to be included in the launcher and removing from every app we did not want to appear in the launcher, sigh...
I suppose if someone wants they could check this for certain by adding an xperiaplayoptimized_content tag to an app or removing the tag from an app and seeing what happens...
So, I'm thinking three possible options? Unless any can think of any further solutions?
a) Change how the Xperia Play app searches - possibly by editing the searchable.xml file - although I'm not sure what to change the search to?
b) Add the xperiaplayoptimized_content tag to every maifest of every app we want included - that's also, assuming xperiaplayoptimized_content is the correct tag!
c) Leave things as they are - you just lose the changed .db file on reboot or when you close the application by mistake. Perhaps even a simple app to replace .db file when this happens?
Sigh, so much work/effort for something simple - damn you Sony Erricson! LOL
Chris
Hurray, it works
Added this line:
Code:
<meta-data android:name="xperiaplayoptimized_content" android:resource="@drawable/icon" />
right before:
Code:
</application>
you can probably use the @drawable to make it any icon you want.
The happy viking game uses a resolution of 170*170 I believe.
Now is there anyone with the skills to have the android manifests modified of allready installed apps with a nice menu where you could select wich app you want to have the line added to the manifest? If that's possible at all.
Edit: updated the app I use for testing stuff so it shows up in the game launcher: http://forum.xda-developers.com/showthread.php?p=14451093#post14451093
svenk919 said:
Hurray, it works
Added this line:
Code:
<meta-data android:name="xperiaplayoptimized_content" android:resource="@drawable/icon" />
right before:
Code:
</application>
you can probably use the @drawable to make it any icon you want.
The happy viking game uses a resolution of 170*170 I believe.
Now is there anyone with the skills to have the android manifests modified of allready installed apps with a nice menu where you could select wich app you want to have the line added to the manifest? If that's possible at all.
Edit: updated the app I use for testing stuff so it shows up in the game launcher: http://forum.xda-developers.com/showthread.php?p=14451093#post14451093
Click to expand...
Click to collapse
Great work , just tested your app! Awesome we now know for certain that xperiaplayoptimized_content is the correct tag...
Ageed it needs someone skilled - but an app that acutally modifies the manifests already installed apps is far beyond what I can do
As you say I'm not even sure such a feat is possible?
An alternative may be to decompile your apps and recompile them... Apktool, should do the trick...
code.google.com/p/android-apktool/
Hmm, tempting... I think I might have a go with one app, see how long it takes to decompile, edit and recompile an app!
deepestblue said:
Great work , just tested your app! Awesome we now know for certain that xperiaplayoptimized_content is the correct tag...
Ageed it needs someone skilled - but an app that acutally modifies the manifests already installed apps is far beyond what I can do
As you say I'm not even sure such a feat is possible?
An alternative may be to decompile your apps and recompile them... Apktool, should do the trick...
code.google.com/p/android-apktool/
Hmm, tempting... I think I might have a go with one app, see how long it takes to decompile, edit and recompile an app!
Click to expand...
Click to collapse
Maybe an app along the lines of ninjamorph but more dedicated to editing the android mainifest
Sent from my R800i using Tapatalk
AndroHero said:
Maybe an app along the lines of ninjamorph but more dedicated to editing the android mainifest
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
Hi, I tried ninjamorph but it didn't actually decompile the the android manifest...
However apktool did!
So, it's a simple matter of copying your apk, decompile with apktool, add the xperia play optimized tag, recompile with apktool and then install
It's a much quicker process than it sounds, and to add the tag to an app in total takes about 15 mins with install...
If anyone wants step by step instructions let me know!
It's so much better having the apps you want in the launcher....
deepestblue said:
Hi, I tried ninjamorph but it didn't actually decompile the the android manifest...
However apktool did!
So, it's a simple matter of copying your apk, decompile with apktool, add the xperia play optimized tag, recompile with apktool and then install
It's a much quicker process than it sounds, and to add the tag to an app in total takes about 15 mins with install...
If anyone wants step by step instructions let me know!
It's so much better having the apps you want in the launcher....
Click to expand...
Click to collapse
If it isnt too much trouble,could you please post the step by step process. I would greatly appreciate it.
I picked the Xperia Play Camera Mod app, courtesy of Zoop57, to tinker a bit. svenk's suggestion left me with this error:
Code:
C:\Users\Logseman\Downloads\seb.camera.mod-1\AndroidManifest.xml:46: error: Error: No resource found that matches the given name (at 'resource' with value '@drawable/icon').
and some others chained to it. I presume we need to add something more than that line? This is the first time I actually use apktool, so I can perfectly have missed something.
apk tool should give a "res" map, if you have folders like: "drawable-h/m/ldpi" look into it, mostly it has an icon named "icon.png" but it could be named different with the camera app, if it is different change the icon '@drawable/icon' to what the file is named in the camera app. If such folders don't exist you probably have to chancgte the '@drawable' part to.
PS.
I think the line of code in case of the camera app should be:
Code:
<meta-data android:name="xperiaplayoptimized_content" android:resource="@drawable/ic_launcher_camera" />
I managed to build the app using "@drawable/ic_launcher_camera" in that field. However, after installing it, it won't show in the Xperia Play launcher with the games. Moreover, I decoded fifa.apk, which does appear in the launcher as Fifa 10, and it doesn't show that line on the Manifest:
Code:
<?xml version="1.0" encoding="utf-8"?>
<manifest android:versionCode="1034" android:versionName="1.0.34" package="com.eamobile.Fifa"
xmlns:android="http://schemas.android.com/apk/res/android">
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.READ_PHONE_STATE" />
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
<uses-permission android:name="android.permission.ACCESS_WIFI_STATE" />
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
<uses-permission android:name="android.permission.CHANGE_NETWORK_STATE" />
<uses-permission android:name="com.android.vending.CHECK_LICENSE" />
<uses-permission android:name="android.permission.DISABLE_KEYGUARD" />
<application android:label="@string/app_name" android:icon="@drawable/icon">
<activity android:theme="@android:style/Theme.NoTitleBar.Fullscreen" android:name=".Fifa" android:launchMode="singleTask" android:screenOrientation="landscape" android:configChanges="keyboardHidden|orientation">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
</application>
<uses-sdk android:minSdkVersion="3" />
</manifest>
Did you reboot the phone? The launcher doesn't refresh its database all the time. The line was there with the happy vikings game and it did work to add my touchpadtester app to my launcher.
I've uninstalled the app, reinstalled it, opened it, closed it and rebooted the phone to no avail. It won't show in the menu.
Does the camera app uses sdk version 9 or later? It should be stated in the manifest. Probably the xperia play optimized tag only works since android 2.3.2.
svenk919 said:
Does the camera app uses sdk version 9 or later? It should be stated in the manifest. Probably the xperia play optimized tag only works since android 2.3.2.
Click to expand...
Click to collapse
Hmmm... Zoop mentioned that he grabbed the latest source, so it should be 2.3.4.
Here's the manifest of his camera mod:
Code:
<?xml version="1.0" encoding="utf-8"?>
<manifest android:versionCode="5" android:versionName="5" package="seb.camera.mod"
xmlns:android="http://schemas.android.com/apk/res/android">
<original-package android:name="com.android.camera" />
<uses-sdk android:minSdkVersion="9" />
<uses-permission android:name="android.permission.CAMERA" />
<uses-feature android:name="android.hardware.camera" />
<uses-feature android:name="android.hardware.camera.autofocus" android:required="false" />
<uses-permission android:name="android.permission.RECORD_AUDIO" />
<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
<uses-permission android:name="android.permission.WAKE_LOCK" />
<uses-permission android:name="android.permission.SET_WALLPAPER" />
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
<uses-permission android:name="android.permission.READ_SMS" />
<application android:label="Camera Mod" android:icon="@drawable/ic_launcher_camera" android:taskAffinity="">
<receiver android:name="com.android.camera.CameraButtonIntentReceiver">
<intent-filter>
<action android:name="android.intent.action.CAMERA_BUTTON" />
</intent-filter>
</receiver>
<activity android:theme="@android:style/Theme.Black.NoTitleBar.Fullscreen" android:name="com.android.camera.Camera" android:taskAffinity="android.task.camera" android:clearTaskOnLaunch="true" android:screenOrientation="landscape" android:configChanges="keyboardHidden|orientation">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.DEFAULT" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
<intent-filter>
<action android:name="android.media.action.IMAGE_CAPTURE" />
<category android:name="android.intent.category.DEFAULT" />
</intent-filter>
<intent-filter>
<action android:name="android.media.action.STILL_IMAGE_CAMERA" />
<category android:name="android.intent.category.DEFAULT" />
</intent-filter>
</activity>
<activity android:theme="@android:style/Theme.Black.NoTitleBar.Fullscreen" android:label="@string/video_camera_label" android:icon="@drawable/ic_launcher_video_camera" android:name="com.android.camera.VideoCamera" android:taskAffinity="android.task.camcorder" android:clearTaskOnLaunch="true" android:screenOrientation="landscape" android:configChanges="keyboardHidden|orientation">
<intent-filter>
<action android:name="android.media.action.VIDEO_CAMERA" />
<category android:name="android.intent.category.DEFAULT" />
</intent-filter>
<intent-filter>
<action android:name="android.media.action.VIDEO_CAPTURE" />
<category android:name="android.intent.category.DEFAULT" />
</intent-filter>
</activity>
</application>
</manifest>
This is the manifest of my touchpad app:
Code:
<?xml version="1.0" encoding="utf-8"?>
<manifest package="test.play.controls"
xmlns:android="http://schemas.android.com/apk/res/android" android:versionName="0.2" android:versionCode="2">
<uses-sdk android:minSdkVersion="9" android:targetSdkVersion="9" />
<application android:label="@string/app_name" android:icon="@drawable/icon">
<activity android:label="@string/app_name" android:name="android.app.NativeActivity" android:launchMode="singleInstance" android:screenOrientation="landscape" android:configChanges="keyboardHidden|orientation">
<meta-data android:name="android.app.lib_name" android:value="touchpadndk" />
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
<meta-data android:name="xperiaplayoptimized_content" android:resource="@drawable/launchericon" />
</application>
</manifest>
This guide is basically for anyone who cooks ROMs and wants to add default widgets to any of the screens rather than the widgets HTC puts on the screens. Also if you remove some widgets from your ROM you will be left with blank screens so you can use those screens to add other widgets that are still in the ROM.
Cooking a ROM can be and is a nice experience and very educational too. After about a
year of cooking my own ROMs I decided to do what any other developer would do, learn
by trial and error and that is how I came by one my best discoveries so far, that is
where and how to place widgets in your Android ROM when you are cooking it. It is very
simple when you realise how simple it is. I don't know if anyone has it figured out
but after searching these forums for about 6 months nothing came up.
Right, let's get down and dirty with this. Here are the tools I used (anyone who cooks
ROMs should probably have them):
dsixda's kitchen - to decompile and recompile the ROMs
notepad++ - to edit various (text) files
7zip - to unzip archived files
apktool - to decompile and recompile apks
any ROM/update.zip -
other tools - will add these when they come up
Files to edit
-WORKING_******_******\system\customize\MNS\default.xml
-******widget\res\xml\***.xml
-******widget\AndroidManifest.xml
Install apktool and use it to decompress the apks for the widgets you need.
Anyway, hoping your computer is set up to use dsixda's kitchen, unpack your rom using
dsixda's kitchen (the kitchen) and navigate to
C:\cygwin\home\%user%\kitchen\%WORKING_******_******%\system\customize\MNS
Make a back up of and open default.xml with notepad++ and scroll down about half way
down till you get to
<function name="1_fx_widgets">
and that is where the widget placement begins. An example is
<function name="1_fx_widgets">
<set name="plenty">
<!--c91f1916-b3a3-4293-b989-1428041e73c4-->
<item name="package_name">com.htc.htccontactwidgets_3d_fusion</item>
<item name="widget_name">com.htc.htccontactwidgets_3d_fusion.ContactWidgetMatrix</item>
<item name="provider_name">com.htc.android.rosie.widget.provider</item>
<item name="screen">4</item>
<item name="cell_x">0</item>
<item name="cell_y">1</item>
<item name="span_x">4</item>
<item name="span_y">3</item>
<item name="property.group_name">Favorite_8656150684447252476_6727701920173350445</item>
<item name="property.sence_path">Port/People_4x3_ListView.m10</item>
<item name="property.item_path">Port/People_4x4_ListItem.m10</item>
</set>
<set name="plenty">
<!--2a59290f-8da8-4eba-a246-27a5df7c6246-->
<item name="package_name">com.htc.clock3dwidget</item>
<item name="widget_name">com.htc.clock3dwidget.weatherclock.WeatherClockWidgetView</item>
<item name="provider_name">com.htc.clock3dwidget.ClockWidgetProvider</item>
<item name="screen">3</item>
<item name="cell_x">0</item>
<item name="cell_y">0</item>
<item name="span_x">4</item>
<item name="span_y">2</item>
</set>
Click to expand...
Click to collapse
Next is to get the apk of the widget you want to use. In this case I used the clock widget which is
HtcClock3DWidget.apk. Use apktool to decompile it (7zip will unpack it but the xmls won't show up
properly in Notepad++). Go into the the decompressed folder 'htcclock3dwidget' (Windows ignores
and lowercase letters) and open 'AndroidManifest.xml'. The file should be as follows:
<?xml version="1.0" encoding="utf-8"?>
<manifest android:sharedUserId="com.htc.rosie.uid.shared" android:versionCode="300254226" android:versionName="3.0.2211151065.254226" package="com.htc.clock3dwidget"
xmlns:android="http://schemas.android.com/apk/res/android">
<skip-erased />
<application android:label="@string/app_name" android:icon="@drawable/clock" android:hardwareAccelerated="false" allowSkinChange="true">
<uses-library android:name="com.htc.android.rosie" />
<uses-library android:name="com.htc.fusion.fx" />
<uses-library android:name="com.htc.lockscreen.fusion" />
<uses-feature android:name="com.htc.android.rosie.widget" />
<receiver android:label="@string/clock_widget_provider_label" android:icon="@drawable/clock" android:name="com.htc.clock3dwidget.ClockWidgetProvider" android:exported="true">
<intent-filter>
<action android:name="com.htc.android.rosie.intent.action.UPDATE_WIDGET" />
</intent-filter>
<meta-data android:name="com.htc.android.rosie.widget.provider" android:resource="@xml/clock_widget" />
</receiver>
<service android:label="@string/clock_widget_provider_label" android:name=".idlescreen.IdleScreenClockService">
<intent-filter>
<action android:name="com.htc.lockscreen.idlescreen.IdleScreenService" />
</intent-filter>
<meta-data android:name="com.htc.lockscreen.idlescreen" android:resource="@xml/idle_screen_clock" />
</service>
<service android:name=".idlescreen.IdleScreenPreviewService" androidrocess="review">
<intent-filter>
<action android:name="com.htc.lockscreen.idlescreen.preview.IdleScreenService" />
</intent-filter>
</service>
<activity android:theme="@android:style/Theme.NoTitleBar" android:label="@string/settings" android:name=".idlescreen.IdleScreenSettings" android:screenOrientation="portrait">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
</intent-filter>
</activity>
<activity android:theme="@style/ThemeTitle" android:label="@string/app_name" android:name=".setting.HtcWWPSetting" android:screenOrientation="unspecified">
<intent-filter>
<action android:name="OpenWWPSettings" />
<category android:name="android.intent.category.DEFAULT" />
</intent-filter>
</activity>
<activity android:theme="@style/ThemeTitle" android:name=".setting.HtcClockSetting" android:screenOrientation="unspecified">
<intent-filter>
<action android:name="OpenSettings" />
<category android:name="android.intent.category.DEFAULT" />
<data android:mimeType="com.htc.widget.clockwidget/open_settings" />
</intent-filter>
</activity>
<activity android:theme="@style/ThemeTitle" android:name=".setting.ConfigWeatherClock" android:screenOrientation="unspecified">
<intent-filter>
<action android:name="OpenSettings" />
<category android:name="android.intent.category.DEFAULT" />
<data android:mimeType="com.htc.widget.clockwidget/open_settings" />
</intent-filter>
</activity>
<activity android:theme="@style/ThemeTitle" android:name=".setting.ConfigAnalogClock" android:screenOrientation="unspecified">
<intent-filter>
<action android:name="OpenSettings" />
<category android:name="android.intent.category.DEFAULT" />
<data android:mimeType="com.htc.widget.clockwidget/open_settings" />
</intent-filter>
</activity>
<activity android:theme="@style/ThemeTitle" android:name=".setting.ConfigDigitalClock" android:screenOrientation="unspecified">
<intent-filter>
<action android:name="OpenSettings" />
<category android:name="android.intent.category.DEFAULT" />
<data android:mimeType="com.htc.widget.clockwidget/open_settings" />
</intent-filter>
</activity>
<activity android:theme="@style/ThemeTitle" android:name=".setting.ConfigDualClock" android:screenOrientation="unspecified">
<intent-filter>
<action android:name="OpenSettings" />
<category android:name="android.intent.category.DEFAULT" />
<data android:mimeType="com.htc.widget.clockwidget/open_settings" />
</intent-filter>
</activity>
</application>
<uses-sdk android:minSdkVersion="8" android:targetSdkVersion="15" />
<uses-permission android:name="android.permission.WAKE_LOCK" />
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
<uses-permission android:name="android.permission.ACCESS_WIFI_STATE" />
<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
<uses-permission android:name="android.permission.GET_ACCOUNTS" />
<uses-permission android:name="android.permission.READ_SYNC_SETTINGS" />
<uses-permission android:name="com.htc.htctwitter.permission.useprovider" />
<uses-permission android:name="com.htc.socialnetwork.plurk.permission.useprovider" />
<uses-permission android:name="android.permission.WRITE_SECURE_SETTINGS" />
<uses-permission android:name="com.htc.launcher.permission.READ_SETTINGS" />
<uses-permission android:name="android.permission.MODIFY_PHONE_STATE" />
<uses-permission android:name="htc.permission.weather.USE_DATA" />
<uses-permission android:name="htc.friendstream.permission.SYSTEM_USE" />
<uses-permission android:name="htc.pluginmanager.permission.USE_PROVIDER" />
</manifest>
Click to expand...
Click to collapse
In default.xml from the (working_folder)\system\customise\mns\ the default clock widget
settings are:
<set name="plenty">
<!--2a59290f-8da8-4eba-a246-27a5df7c6246-->
<item name="package_name">com.htc.clock3dwidget</item>
<item name="widget_name">com.htc.clock3dwidget.weatherclock.WeatherClockWidgetView</item>
<item name="provider_name">com.htc.clock3dwidget.ClockWidgetProvider</item>
<item name="screen">3</item>
<item name="cell_x">0</item>
<item name="cell_y">0</item>
<item name="span_x">4</item>
<item name="span_y">2</item>
</set>
Click to expand...
Click to collapse
This is for the large default clock in HTC Sense which occupies half the screen. I decided to
go for the new clock which takes up one line at the top of the screen. Right, to edit it to get
the new clock to come up when I cook my rom in the main homescreen which is screen 3 (the
fourth screen from the far left) (the screen counting starts from 0) I need "package_name",
"widget_name", "provider_name" and "span_y".
For "package_name" this is found in 'AndroidManifest.xml' in the decompiled 'htcclock3dwidget'
folder. It is found in one of the first lines
<manifest android:sharedUserId="com.htc.rosie.uid.shared" android:versionCode="300254226" android:versionName="3.0.2211151065.254226" package="com.htc.clock3dwidget"
Click to expand...
Click to collapse
as 'package' after 'android:versionName' so the "package_name" is
'com.htc.clock3dwidget'
For "widget_name" it is a little tricky. Navigate to 'htcclock3dwidget\res\xml' and open 'clock_widget.xml'
in Notepad++. The file looks like this (it is more or less this file, lol):
<?xml version="1.0" encoding="utf-8"?>
<rosie-widget
xmlns:rosie="http://schemas.android.com/apk/res/com.htc">
<style rosie:id="clockweather" rosie:label="@string/widget_weather_clock" rosie:description="@string/widget_detail" rosiereview="@drawable/preview_clock_weather" rosie:date="@string/simple_widget_date" rosie:name=".weatherclock.WeatherClockWidgetView" rosie:configure="com.htc.clock3dwidget/com.htc.clock3dwidget.setting.ConfigWeatherClock" rosie:span_x="4" rosie:span_y="2" />
<style rosie:id="clockweather41" rosie:label="@string/widget_weather_clock" rosie:description="@string/widget_detail" rosiereview="@drawable/preview_clock_weather_4x1" rosie:date="@string/simple_widget_date" rosie:name=".ClockWeather_4x1" rosie:configure="com.htc.clock3dwidget/com.htc.clock3dwidget.setting.ConfigWeatherClock" rosie:span_x="4" rosie:span_y="1" />
<style rosie:id="clockSocial" rosie:label="@string/widget_social_clock" rosie:description="@string/widget_detail" rosiereview="@drawable/preview_clock_social" rosie:date="@string/simple_widget_date" rosie:name=".socialclock.SocialClockWidgetView" rosie:span_x="4" rosie:span_y="2" />
<style rosie:id="clockDigital" rosie:label="@string/widget_digital_clock" rosie:description="@string/widget_detail" rosiereview="@drawable/preview_clock_digital" rosie:date="@string/simple_widget_date" rosie:name=".ClockDigital" rosie:configure="com.htc.clock3dwidget/com.htc.clock3dwidget.setting.ConfigDigitalClock" rosie:span_x="2" rosie:span_y="1" />
<style rosie:id="clockDual" rosie:label="@string/widget_dual_clock" rosie:description="@string/widget_detail" rosiereview="@drawable/preview_clock_dual" rosie:date="@string/simple_widget_date" rosie:name=".ClockDual" rosie:configure="com.htc.clock3dwidget/com.htc.clock3dwidget.setting.ConfigDualClock" rosie:span_x="4" rosie:span_y="2" />
<style rosie:id="clock03" rosie:label="@string/widget_analog_clock" rosie:description="@string/widget_detail" rosiereview="@drawable/preview_clock03" rosie:date="@string/simple_widget_date" rosie:name=".Clock03" rosie:configure="com.htc.clock3dwidget/com.htc.clock3dwidget.setting.ConfigAnalogClock" rosie:span_x="4" rosie:span_y="3" />
<style rosie:id="clock2x2" rosie:label="@string/widget_analog_clock" rosie:description="@string/widget_detail" rosiereview="@drawable/preview_clock2x2" rosie:date="@string/simple_widget_date" rosie:name=".Clock2x2" rosie:configure="com.htc.clock3dwidget/com.htc.clock3dwidget.setting.ConfigAnalogClock" rosie:span_x="2" rosie:span_y="2" />
<style rosie:id="clock04" rosie:label="@string/widget_analog_clock" rosie:description="@string/widget_detail" rosiereview="@drawable/preview_clock04" rosie:date="@string/simple_widget_date" rosie:name=".Clock04" rosie:configure="com.htc.clock3dwidget/com.htc.clock3dwidget.setting.ConfigAnalogClock" rosie:span_x="4" rosie:span_y="3" />
<style rosie:id="clock05" rosie:label="@string/widget_analog_clock" rosie:description="@string/widget_detail" rosiereview="@drawable/preview_clock05" rosie:date="@string/simple_widget_date" rosie:name=".Clock05" rosie:configure="com.htc.clock3dwidget/com.htc.clock3dwidget.setting.ConfigAnalogClock" rosie:span_x="4" rosie:span_y="3" />
<style rosie:id="clock06" rosie:label="@string/widget_analog_clock" rosie:description="@string/widget_detail" rosiereview="@drawable/preview_clock06" rosie:date="@string/simple_widget_date" rosie:name=".Clock06" rosie:configure="com.htc.clock3dwidget/com.htc.clock3dwidget.setting.ConfigAnalogClock" rosie:span_x="4" rosie:span_y="3" />
<style rosie:id="clock07" rosie:label="@string/widget_analog_clock" rosie:description="@string/widget_detail" rosiereview="@drawable/preview_clock07" rosie:date="@string/simple_widget_date" rosie:name=".Clock07" rosie:configure="com.htc.clock3dwidget/com.htc.clock3dwidget.setting.ConfigAnalogClock" rosie:span_x="4" rosie:span_y="3" />
<style rosie:id="clock08" rosie:label="@string/widget_analog_clock" rosie:description="@string/widget_detail" rosiereview="@drawable/preview_clock08" rosie:date="@string/simple_widget_date" rosie:name=".Clock08" rosie:configure="com.htc.clock3dwidget/com.htc.clock3dwidget.setting.ConfigAnalogClock" rosie:span_x="4" rosie:span_y="3" />
<style rosie:id="clock09" rosie:label="@string/widget_analog_clock" rosie:description="@string/widget_detail" rosiereview="@drawable/preview_clock09" rosie:date="@string/simple_widget_date" rosie:name=".Clock09" rosie:configure="com.htc.clock3dwidget/com.htc.clock3dwidget.setting.ConfigAnalogClock" rosie:span_x="4" rosie:span_y="3" />
<style rosie:id="clock10" rosie:label="@string/widget_analog_clock" rosie:description="@string/widget_detail" rosiereview="@drawable/preview_clock10" rosie:date="@string/simple_widget_date" rosie:name=".Clock10" rosie:configure="com.htc.clock3dwidget/com.htc.clock3dwidget.setting.ConfigAnalogClock" rosie:span_x="4" rosie:span_y="3" />
<style rosie:id="clockBeam" rosie:label="@string/widget_beam_clock" rosie:description="@string/widget_detail" rosiereview="@drawable/preview_clock_beam" rosie:date="@string/simple_widget_date" rosie:name=".ClockBeam" rosie:configure="com.htc.clock3dwidget/com.htc.clock3dwidget.setting.ConfigAnalogClock" rosie:span_x="4" rosie:span_y="3" />
<style rosie:id="clockRing" rosie:label="@string/widget_ring_clock" rosie:description="@string/widget_detail" rosiereview="@drawable/preview_clock_ring" rosie:date="@string/simple_widget_date" rosie:name=".ClockRing" rosie:configure="com.htc.clock3dwidget/com.htc.clock3dwidget.setting.ConfigAnalogClock" rosie:span_x="4" rosie:span_y="3" />
<style rosie:id="clockSpinCycle" rosie:label="@string/widget_spin_cycle_clock" rosie:description="@string/widget_detail" rosiereview="@drawable/preview_clock_spin_cycle" rosie:date="@string/simple_widget_date" rosie:name=".ClockSpinCycle" rosie:configure="com.htc.clock3dwidget/com.htc.clock3dwidget.setting.ConfigAnalogClock" rosie:span_x="4" rosie:span_y="3" />
<style rosie:id="clock1x1" rosie:label="@string/widget_analog_clock" rosie:description="@string/widget_detail" rosiereview="@drawable/preview_clock1x1" rosie:date="@string/simple_widget_date" rosie:name=".Clock1x1" rosie:configure="com.htc.clock3dwidget/com.htc.clock3dwidget.setting.ConfigAnalogClock" rosie:span_x="1" rosie:span_y="1" />
</rosie-widget>
Click to expand...
Click to collapse
In my case I want to use the smaller newer clock (but any can do depending on which clock you want
to use) which is found on this line:
<style rosie:id="clockweather41" rosie:label="@string/widget_weather_clock" rosie:description="@string/widget_detail" rosiereview="@drawable/preview_clock_weather_4x1" rosie:date="@string/simple_widget_date" rosie:name=".ClockWeather_4x1" rosie:configure="com.htc.clock3dwidget/com.htc.clock3dwidget.setting.ConfigWeatherClock" rosie:span_x="4" rosie:span_y="1" />
Click to expand...
Click to collapse
The name of the clock widget I want to use is found after 'rosie:name' which is ".ClockWeather_4x1".
So for "widget_name" I use "package_name"+'rosie:name' which makes it
'com.htc.clock3dwidget.ClockWeather_4x1'
For 'provider_name' that's a bit more difficult but after trial and error I found that it is
found in 'AndroidManifest.xml' of the clock widget on the line
<receiver android:label="@string/clock_widget_provider_label" android:icon="@drawable/clock" android:name="com.htc.clock3dwidget.ClockWidgetProvider" android:exported="true">
Click to expand...
Click to collapse
so 'provider_name' is 'android:name' before 'android:exported' which is
'com.htc.clock3dwidget.ClockWidgetProvider'
This becomes
<item name="package_name">com.htc.clock3dwidget</item>
<item name="widget_name">com.htc.clock3dwidget.ClockWeather_4x1</item>
<item name="provider_name">com.htc.clock3dwidget.ClockWidgetProvider</item>
Click to expand...
Click to collapse
'cell_x' and 'cell_y' remain untouched because I want it at the top of the screen starting
from the left (you place it where you want using cell_x and cell_y). 'span_x' stays at '4'
(because it occupies 4 cells going to the left) but 'span_y' becomes '1' because it occupies
1 cell going down. The clock widget settings section finally becomes
<set name="plenty">
<!--2a59290f-8da8-4eba-a246-27a5df7c6246-->
<item name="package_name">com.htc.clock3dwidget</item>
<item name="widget_name">com.htc.clock3dwidget.ClockWeather_4x1</item>
<item name="provider_name">com.htc.clock3dwidget.ClockWidgetProvider</item>
<item name="screen">3</item>
<item name="cell_x">0</item>
<item name="cell_y">0</item>
<item name="span_x">4</item>
<item name="span_y">1</item>
</set>
Click to expand...
Click to collapse
And that's just for the clock widget. The format is more or less the same for the other widgets. By the way, if you mess up the widget won't show but the widget itself won't be affected so you can manually add it. You will notice there are settings for other widgets that don't show up on any of the screens.
Oh, I think the process works the same for all phones as long as they have HTC Sense. If anyone has any questions please please please feel free to ask. We are all here to learn. I added bookmarks widget to replace friendstream widget which I don't need and re-added weather widget to first the first screen, shifted navigation widget and fellow widgets to last screen and added htc notes widget to their screen. The power is in your hands. As I said before, I couldn't find the information I needed anywhere so I had to hunt it down in the files mentioned above using my hunch and I found it. Whatever you want or need the answers are out there, you just need to find them
I have attached some screenshots. You might notice there's nothing special to them because you can change them after installing your ROM but that's how my screens look when I install my ROM so I don't have to change them anymore.
Many many thanks go to
football
mike1986
robocik, capychimp
baadnewz
dsixda
hawke84
faux123, sebastianfm
apktool guy
and many others from back in the days of wm2003
Since you already opened the default.xml file you might as well scroll a little further down and you will come this section
<module name="Browser">
<function name="bookmark">
Click to expand...
Click to collapse
That is the section with the default bookmarks for the bookmarks widget so you can add and remove sites so they come up by default. This section looks like this by default
<module name="Browser">
<function name="bookmark">
<set name="plenty">
<!--%%File%%-->
<item name="title">HTC</item>
<item name="url">http://www.htc.com</item>
</set>
<set name="plenty">
<!--%%File%%-->
<item name="title">Google</item>
<item name="url">http://www.google.com</item>
</set>
<set name="plenty">
<!--%%File%%-->
<item name="title">Yahoo!</item>
<item name="url">http://www.yahoo.com</item>
</set>
<set name="plenty">
<!--%%File%%-->
<item name="title">Wiki</item>
<item name="url">http://www.wikipedia.org</item>
</set>
<set name="plenty">
<!--%%File%%-->
<item name="title">Twitter</item>
<item name="url">http://twitter.com</item>
</set>
<set name="plenty">
<!--%%File%%-->
<item name="title">Facebook</item>
<item name="url">http://www.facebook.com</item>
</set>
<set name="plenty">
<!--%%File%%-->
<item name="title">AccuWeather</item>
<item name="url">http://www.accuweather.com/m/default.aspx?p=htcand&loc</item>
</set>
<set name="plenty">
<!--%%File%%-->
<item name="title">Lonely Planet</item>
<item name="url">http://www.lonelyplanet.com</item>
</set>
Click to expand...
Click to collapse
I added xdadevelopers to the list but you can add more if you want or remove some too.
Had another look at that ...system\customise\mns\default.xml. Looks like the '<function name="1_fx_widgets">' section up to '<function name="5_fx_widgets">' are the scenes for the scene picker part of hts sense. Even further down are the default apps that come with each scene. All you have to do is add or change your widgets, take screenshots, add screenshots to '...\system\customise\resource\' folder, fiddle with the naming then jump into the default.xml file and take it from there. Will update as I keep testing on my phone. God help this phone, lol.
reserved for even more info
merci beaucoup, monsieur can use this for future plans
, thanks for posting it!
Hi, can you show how to enable chinese input on HTC IME?
seadersn said:
merci beaucoup, monsieur can use this for future plans
, thanks for posting it!
Click to expand...
Click to collapse
M head's pounding right now considering I have already flashed my phoned about 9 times in the past 4 hours trying to get other widgets to work by default at first boot but thanks very much for the post seadersn. I'll update it a bit more because even with this info I am a bit confused myself, lol.
hengmy said:
Hi, can you show how to enable chinese input on HTC IME?
Click to expand...
Click to collapse
hi hengmy. I am sorry I cannot help at the moment but I guess one of the other hardened developers can. Thanks for asking anyway
ok, let's have a deeper look into it. maybe i will find some time today for playing with this, too; but first: dentist ;( i hope i'm able to do anything today after massacre's over...
Right, for anybody interested, I have edited my guide a little bit more and it's a little clearer now. The guide is basically for anyone who cooks ROMs and wants to add default widgets to any of the screens rather than the widgets HTC puts on the screens. Also if you remove some widgets from your ROM you will be left with blank screens so you can use those screens to add other widgets that are still in the ROM.
seadersn said:
ok, let's have a deeper look into it. maybe i will find some time today for playing with this, too; but first: dentist ;( i hope i'm able to do anything today after massacre's over...
Click to expand...
Click to collapse
Hi seadersn. Hope your trip to the dentist went ok . I redid the guide and I hope you can make some good use out of it. Any questions you have I'll try to answer but for now stay strong my friend.
thx, thx tomorrow and friday are next dentist visits longer taking thingy; replacement of three teethes
tmr is wednesday? kk, will start my testimonials in thursday: head / brain should be free then i'll contact you; i thought that there have to be a 'master index file' for that. if, then it will be found by us
gn8, maestro
well good luck with the dentist. but getting three teeth out, you must be a hero, lol. last time i went to the dentist was about 15yrs ago. i'd rather somebody punch my teeth out, lol.
anyway, from the way i see things i think those may be the 'master index files' for the default widget placement when cooking your roms. of course you can change them back. i had got fed up with changing my widgets everytime i flashed my phone so the quest began. so now i can get widgets of my choosing onto screens of my choosing before i cook and flash my rom. so it's not really something special but will come in handy for a chef. imagine cooking your own rom and having one of those fancy analogue clocks come up by default when you install your rom (of course you can change it back) and maybe a whole set of settings widgets on, hmm, maybe the last screen, for example? and that's how you might like it but how about those become your default screens for your custom roms?
i was fed of hanging around in the shadows for so many years, lol. and again, good luck with the dentist. remember to drink loads of water
I just use sqlite editor to get widget values from favourites in HTC launch database. Easy peezy lemon sqeezey
Sent from my HTC Sensation using xda premium
richmondo said:
I just use sqlite editor to get widget values from favourites in HTC launch database. Easy peezy lemon sqeezey
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
thank richmondo. will try and look into that . right now i am continuously scratching my head to get some of the widgets to show up and all the scrolling up and down and copy-pasting stuff is doing my head in, lol. wld love to find an easier method
nice
Hope the mods find this and move it to chef central.
Does seem to work on all HTC phones.
This is an awesome reference thread.
Well done.
Rob
other languages
hengmy said:
Hi, can you show how to enable chinese input on HTC IME?
Click to expand...
Click to collapse
Not sure of input as this may require a library added to the keyboard of choice; however, languages are added fairly simply ASSUMING you use a WWE base rom. You just add the language and country code into the default.xml in the CID folder. Example WFS has their latest and greatest called the Euro... Well it has lots of English choices but not for the US; so a bit of copying.. then edit your copy set to en_US et voila it will show up (and set up if chosen) upon factory reset. Language always fist two digit code and in lowercase; Country 2nd set and in caps.
Now sometimes I should warn a rom may use multiple CID setup profiles if so you could spy it in the /resouce/ccinfo.txt file. I would advise knocking out the multiples and setting it to default unless you just feel like complicating your life. Logic path is build.prop to ccinfo.txt to the various default.xml's (which then often have external carrier .xmls referenced in UI strings) and a root of customize directory file which has build number and whatnot [verification purposes mostly]. After that, your own your own, but understanding the logic path helps me not go insane
Now... Speaking of keyboards, how you guys figure the "short" name to add lessay Hacker's Keyboard, my personal fav generic in mns default.xml.. other keyboard names are indeed short; so I'm kinda guessing its not the package name.
Sidenote to change input in some if not most keyboards you dl the appropriate language library... Hacker's has many, and swype the spacebar, add the lib in the input settings et voila. Cooking that in however... Still learning.
TIA,
Rob
Lennyuk said:
So it seems that only certain apps work with multi-screen and it is not just samsung apps.
Here I plan (with your help) to create a difinitive list of all apps that will work.
I have already noticed that some apps allow themselves to be splitscreened even when they do not appear in that list e.g. official twitter app.
Some apps you will find when you press the edit button, you can then drag them to the main list, or remove ones you do not use.
Samsung Apps
- ChatON
- Email
- Gallery
- Internet
- Messaging
- S-Note
- Video Player
Google Apps
- Chrome
- Gmail
- Maps
- Talk
- Youtube
Third Party Apps
- Facebook
- Official Twitter app
- Polaris (Viewer)
Note: you will need to be using Samsung stock keyboard to benefit from typing when on multi-screen mode, otherwise your keyboard will cover the entire bottom screen.
Click to expand...
Click to collapse
Here is all the info until now. Few days i go i received my new device N7100
Hello,
¡I just found some a nice surprise!
looking at running services, finally found that com.sec.android.app.FlashBarService its how control what app get listed in our whilelist apps to keep it on multiwindows.
XML info its saved at: /data/data/com.sec.android.app.FlashBarService\shared_prefs/flash_bar_list.xml
Code:
<?xml version='1.0' encoding='utf-8' standalone='yes' ?>
<map>
<int name="com.sec.chaton.HomeActivity" value="1" />
<int name="com.google.android.apps.chrome.Main" value="2" />
<int name="com.android.email.activity.Welcome" value="3" />
<int name="com.sec.android.gallery3d.app.Gallery" value="4" />
<int name="com.facebook.katana.LoginActivity" value="5" />
<int name="com.google.android.gm.ConversationListActivityGmail" value="6" />
<int name="com.google.android.talk.SigningInActivity" value="7" />
<int name="com.android.browser.BrowserActivity" value="8" />
<int name="com.google.android.maps.MapsActivity" value="9" />
<int name="com.android.mms.ui.ConversationComposer" value="10" />
<int name="com.twitter.android.StartActivity" value="11" />
<int name="com.infraware.filemanager.FmFileTreeListActivity" value="12" />
<int name="com.sec.android.app.videoplayer.activity.MainTab" value="13" />
<int name="com.google.android.youtube.app.honeycomb.Shell$HomeActivity" value="14" />
<int name="NUM_APP_IN_FILE" value="15" />
<boolean name="FILE_SAVE" value="true" />
</map>
After deoxing flashbarservice and jar it ive got the clear sources! Thats whats im going to share here!
Our interesting right now its allow to give new apps in the whitelist, i tried to manage a few things, like dont allow write, not autosave, and adding by myself my some of this functions in FlashBarInfo.java must to be retouched.
I need some sleep maybe tomorrow finally i can bypass the filters!
Regards,
Kasha
Nice job
Today im back at home, after the missrate searching over the frameservice from the multiwindow, everytime cfg files are changed, instead no write permission or whatever so i think that we have more troubles doing on this part.
Searching for a while a found the first idea. Look at the SystemUI & framework!
SystemUI/com\android\systemui\multiwindow is our folder.
MultiWindowControlPanel.java
MultiWindowListPanel.java
MultiWindowReflector.java
RunningTasksLoader$1$1.java
RunningTasksLoader$1.java
RunningTasksLoader.java
SplitPanelView$1.java
SplitPanelView$2.java
SplitPanelView$3.java
SplitPanelView$4.java
SplitPanelView.java
Utilities.java
Click to expand...
Click to collapse
res\layout\status_bar_multi_window_arrange.xml
res\layout\status_bar_multi_window_list.xml
Click to expand...
Click to collapse
I found some interesting info about how the system reads and class our apps.
As I said on the previous thread in the general section:
After looking around a bit, I have collected enough info about this.
If I ever get a note 2 (which I'm thinking about), I am sure I can give the user the ability to add apps to the multiwindow bar. But only if .
Anyway, I honestly wish good luck to everyone trying this .
PS. has anyone tried adding a package name into the string array, inside arrays.xml?
for example, the package name of skype, add it in the bottom, install skype and see if it appears. (It should)
Click to expand...
Click to collapse
Man I wish I could help, but I don't even have my Note 2 yet, or well the knowledge of how to do it. I wish y'all the best of luck, I know this hack for multi-window will blow up once it's finally released in the US, Canada, etc. Thanks for the time.
adding apps to the list is as easy as adding a new package name to the arrays.xml in framework-res.apk
Paul o'Brien (Modaco) posted a pic on twitter yesterday as proof of concept, he had plume and a game, subway surfers, running in multi-screen.
What we really need now is to think of the best way to handle this so that we can easily have all the apps people would want in the list:
1) one way would be to make a list of apps people use and build one giant xml list, this is not ideal but would work.
2) another way would be to have some sort of app to rebuild the xml file based on your installed apps at that time
3) the best way will be to remove the check itself completely, or point the check somewhere else so we can make a local list say on the sd card.
I hope so bad, that someone can manage it. Would be awesome and it doesn't seem to be much complicated.
Well I did just toy with the idea of making a quick dirty VRTheme update.zip to change the xml file to a new list of pre-defined items.
Then I remembered that the xml we need to edit is in /res/values/arrays.xml
VRTheme cannot update /values/ files as the apk needs to be decompiled and recompiled to edit these, no one has come up with a way to do this via an update-script yet.
So that quick fix is out the window.
Lennyuk said:
Well I did just toy with the idea of making a quick dirty VRTheme update.zip to change the xml file to a new list of pre-defined items.
Then I remembered that the xml we need to edit is in /res/values/arrays.xml
VRTheme cannot update /values/ files as the apk needs to be decompiled and recompiled to edit these, no one has come up with a way to do this via an update-script yet.
So that quick fix is out the window.
Click to expand...
Click to collapse
i dont know about VRTHEME, but in alliance ROM using ROm customizer app, one can flash the theme with *.xml files as well
I'm reading this thread and I can't wait to dive into dalvik and try to hack this.
Tonight I am getting my note 2, and I hope to learn lots by exploring this hack.
Have messed around with XMLs and decompile/recompile, also some dalvik but not much.
Paul O'Brien has managed to allow all apps to be shown, not sure what he has done yet to allow this, he said its not finished so we won't know for sure until he is happy with it and releases it, but is certainly a positive start.
grgsiocl said:
i dont know about VRTHEME, but in alliance ROM using ROm customizer app, one can flash the theme with *.xml files as well
Click to expand...
Click to collapse
APK's generally have lots of xml files, some are editable and visible if you just open the apk up as if it was a .zip, these can be changed by the methods there are availiable to do via update.zip (VRTheme or people who have since copied this idea).
some of them are hidden until you decompile the app these are generally the files in /values/.
In the case here the xml we want to edit is in /values/ so there is no existing way an update.zip could edit these.
Hi guys.I will try and help.dont have anytime on my hands these days..very slow internet as my dorms use wireless connection.I have stopped a few other mods on the Note II for about a week now including a rom i was going to upload..
Tonight i will sit down and have a look at whats given in this thread and i can try and update the list with the most popular apps around,and maybe compile a simple app in C++ that can simply add apps to the xml list without you having to open it .well will see.
I have made a new framework-res.apk with a handful of apps that I use (no games, not much point).
I will make it into an update.zip and upload it soon.
this is not a perfect fix as obviously you will only have the apps I added to the list but it might keep some of you going until we get a real fix
Look out for some pretty major news from Modaco later about this split-screen feature too
Lennyuk said:
Look out for some pretty major news from Modaco later about this split-screen feature too
Click to expand...
Click to collapse
Where can we follow modaco?
My mod is here - http://forum.xda-developers.com/showthread.php?t=1939780
You can follow modaco at Modaco.com or on twitter @paulobrien and @modaco
Lennyuk said:
I have made a new framework-res.apk with a handful of apps that I use (no games, not much point).
I will make it into an update.zip and upload it soon.
this is not a perfect fix as obviously you will only have the apps I added to the list but it might keep some of you going until we get a real fix
Click to expand...
Click to collapse
Hope its got xda app most used here probably ...thx
Sent from my GT-N7100 using xda premium
stesteste said:
Hope its got xda app most used here probably ...thx
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
sorry, I forgot about that, I added tapatalk but not xda's version
You mainly see these kinds of things in AOSP ROMs, but I'll teach you guys how to add a "Tweaks" option to the Settings app. Some people know how to do this, others don't. In the spirit of making a better community, here's the how-to. I'll be using the MIUI batterybar by PvyParts as the example. So, to add the MIUI batterybar to Settings, follow the following steps:
Note: You must have already made your ROM compatible with the batterybar mod for it to work. This guide just teaches you how to add things to it. Also, this guide works only if you have a tweaks app such as the batterybar, quickpanel settings, etc so make sure you have those apps installed.
[*]Decompile SecSettings.apk (I use Apk Manager)
[*]Navigate to /res/xml/settings_headers.xml
Add
Code:
<header android:title="@string/header_category_rom_mods" />
<header android:icon="@drawable/ic_settings_batterybar" android:id="@id/batterybar_settings" android:title="@string/batterybar_settings">
<intent android:targetPackage="com.pvy.battbar.settings" android:action="android.intent.action.MAIN" android:targetClass="com.pvy.battbar.settings.options" />
</header>
below
Code:
<header android:icon="@drawable/ic_settings_more" android:id="@id/wireless_settings" android:title="@string/more_settings" android:fragment="com.android.settings.WirelessSettings" android:breadCrumbTitle="@string/wireless_networks_settings_title" />
It'll look like this when finished:
Code:
<header android:icon="@drawable/ic_settings_more" android:id="@id/wireless_settings" android:title="@string/more_settings" android:fragment="com.android.settings.WirelessSettings" android:breadCrumbTitle="@string/wireless_networks_settings_title" />
[COLOR="SeaGreen"] <header android:title="@string/header_category_rom_mods" />
<header android:icon="@drawable/ic_settings_batterybar" android:id="@id/batterybar_settings" android:title="@string/batterybar_settings">
<intent android:targetPackage="com.pvy.battbar.settings" android:action="android.intent.action.MAIN" android:targetClass="com.pvy.battbar.settings.options" />
</header>[/COLOR]
[*]Navigate to /res/values/strings.xml
Scroll to the bottom of the file and add
Code:
<string name="header_category_rom_mods">ROM Control</string>
<string name="batterybar_settings">Battery Bar</string>
right above
Code:
</resources>
It'll look like this when finished (You can name "ROM Control" and "Battery Bar" to whatever you want):
Code:
[COLOR="SeaGreen"]<string name="header_category_rom_mods">ROM Control</string>
<string name="batterybar_settings">Battery Bar</string>[/COLOR]
</resources>
[*]Navigate to /res/values/public.xml
This is the tricky part. You will have to assign unique IDs to each mod. Additionally, you will need to assign a "drawable" type (for the picture) and a "string" type (for the name). This is what my code looks like (the red part is the unique ID (you can use mine as long as they don't conflict with any ID in your public.xml)):
At line 797:
Code:
<public type="drawable" name="ic_settings_batterybar" id="[COLOR="Red"]0x7f0203e2[/COLOR]" />
At line 4871:
Code:
<public type="string" name="batterybar_settings" id="0x7f090e3a" />" id="[COLOR="red"]0x7f0203e2[/COLOR]" />
At line 4869:
Code:
<public type="string" name="header_category_rom_mods" id="[COLOR="red"]0x7f090e38[/COLOR]" />
[*]Navigate to /res/values/ids.xml
Scroll to the bottom of the file and add:
Code:
<item type="id" name="batterybar_settings">false</item>
right above
Code:
</resources>
[*]Recompile SecSettings.apk and push it to your phone.
Awesome, great write up!
A little trick I learned that will allow you to not worry about finding a unique ID for res/public is let the system generate one for you
Add your lines to strings first and nothing else, then re-compile. Then immediately decompile the one you just built. Sounds confusing i know, but.........Now when you open up res/public the lines you just added to strings will have automatically populated with thier own unique ID and you never had to do anything. Try it
Much easier than trying to figure out which HEX ID isnt used, whats in range, or whats next.
:good:
Interesting, I used to wonder how you guys add things like that...
Didact74 said:
Awesome, great write up!
A little trick I learned that will allow you to not worry about finding a unique ID for res/public is let the system generate one for you
Add your lines to strings first and nothing else, then re-compile. Then immediately decompile the one you just built. Sounds confusing i know, but.........Now when you open up res/public the lines you just added to strings will have automatically populated with thier own unique ID and you never had to do anything. Try it
Much easier than trying to figure out which HEX ID isnt used, whats in range, or whats next.
:good:
Click to expand...
Click to collapse
So you're saying do step three first, then step two and then step 4?
Sent from my SCH-I535 using xda app-developers app
Twisted politiks said:
So you're saying do step three first, then step two and then step 4?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Crap, I am sorry if it was confusing. I didn't want to muddle up PM's thread. I would stick to his instructions if you don't quite follow what I was saying. It was meant for those that spend a lot of time running through code. Basically you can skip the part of adding IDs to res/public because once you add your info to strings the recompile process auto generates the IDs for you.
If this confuses you just stick to PMs instructions. : )
收件人： [MOD][HOW-TO] Add an item to Settings
I will try it .thx
Sent from my HTC X515d using xda premium