I was wondering if anyone could help me out with a minor question. Is there a way that i can change the amount of desktops that i have in my home screen. I have 5 right now and would like to move to 3. I've seen this feature before in some themes, but my current one does not have it. Is there another way to change it to 3 screens.
Any help would be greatly appreciated it. Thanks
Most the themes are designed for a specific ROM and don't make modifications on the Launcher, it's usually left with whatever the ROM has. If you want to be able to control the amount of Home screens, you should look into using the advanced launcher, or see if there is a theme you like for your ROM using the advanced launcher.
Thanks for your advise. I'll look into the advance launcher app.
You need to edit the Launcher.apk file from source using a Linux OS (Ubuntu) and have Java 5 (not 6) installed.
Once you have everything set up right and you have downloaded the source:
Then go to Launcher.java and edit this to get three screens:
Code:
static final int SCREEN_COUNT = 3;
static final int DEFAULT_SCREN = 1;
to
Code:
static final int SCREEN_COUNT = 3;
static final int DEFAULT_SCREN = 1;
then open the layout-land and layout-port files and edit the Launcher.xml files with:
Code:
launcher:defaultScreen="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" />
then
Code:
make Launcher
I then sign it with test keys and add it to an update.zip file.
Apply it and reboot.
This won't work in Eclipse using Windows because it throws compiling errors.
Related
So I am trying to mod my first Android Sense widget - the HtcQuickLaunchWidget.apk - and am trying to figure out my way round the file structure and where to go to make certain edits. I've figured out m10 as far as I need to for repositioning/scaling, etc and I have no issue with the image editing and .9 png side of things. However I am wanting to make a small change to the date format in the widget and this is where I need help!
I have decompiled the apk and found the start of a trail in the xml files:
In res\layout\flip_clock.xml the last line is for the date element:
Code:
<TextView android:textSize="20.0px" android:textColor="#ffffffff" android:gravity="bottom|right|center" android:id="@id/date" android:layout_width="fill_parent" android:layout_height="wrap_content" android:layout_marginRight="@dimen/date_margin_right" android:layout_marginBottom="@dimen/date_margin_bottom" android:maxLines="1" android:layout_alignParentRight="true" android:layout_alignParentBottom="true" style="@style/shadow" />
So I have figured that the android:id="@id/date" tells it where to look for the information. I then tracked that to res\values\public.xml and this line:
Code:
<public type="id" name="date" id="0x7f080049" />
...which I guess provides the address for the actual information but that's as far as I can get! What does the 'id="0x7f080049"' refer to? All I want to do is change the date format from 21/10 to Fri, 21 Nov which I could have done easily in WinMo Sense but have no idea in Android!
Would someone who knows what they're talking about be so kind as to put me out of my misery and explain to me how to do it
THIS is the apk I am working with if that helps.
Many thanks,
Dunc
hello
ask the question elsewhere
by Android development for the Desire HD
show your work done
Sorry for my English
Hi guys,
today with sir PineappleOwl's permission I'm going to present you the profile pic and label mod known as lenox label....... some of you already know about it or/and might have used it..... so this guide is going to help those who want to have profile pic mod on their SystemUI but don't know how to make it........ let's get into business and as usual it's clear I'm not the owner I'm only the sharer
Requirements:
Brain
Patience
Experience
lenox.zip
How to add:
1. decompile your SystemUI.apk
2. go to res/values/ids.xml and add these lines:
Code:
<item type="id" name="lenoxlabel">false</item>
<item type="id" name="lenoxpic">false</item>
3. go to res/layout/*wherever you want* and add these:
Code:
<com.lenox.Lenox_Label.lenoxpicture android:gravity="center" android:id="@id/lenoxpic" android:layout_width="wrap_content" android:layout_height="wrap_content" />
<com.lenox.Lenox_Label.lenoxlabel android:gravity="center" android:layout_gravity="bottom" android:id="@id/lenoxlabel" android:background="#bf000000" android:layout_width="wrap_content" android:layout_height="wrap_content" />
4. now add the smalis from lenox.zip to your decompiled SystemUI
5. now recompile and than decompile again....... it's time for id matching
6. go to res/values/public.xml and find this public id:
Code:
<public type="id" name="lenoxlabel" id="*×********" />
7. take the public id and go to smali\com\lenox\Lenox_Label\lenoxlabel.smali
8. go to line 25 and replace the public id you copied on this:
Code:
const v7, 0x7f0d0144
9. now again go to public.xml and take the public id of:
Code:
<public type="id" name="lenoxpic" id="*x********" />
10. go to smali\com\lenox\Lenox_Label\lenoxpicture.smali
11. go to line 21 and replace the public id you just got on this:
Code:
const v4, 0x7f0d0143
12. done now recompile
sign
wait
13. now take Lenox_Label.apk from lenox.zip and push with SystemUI
reboot
enjoy !!!
link:
https://www.androidfilehost.com/?fid=817550096634757786
credits:
@PineappleOwl for making this awesome mod
@r2dak for giving me the guide
screenshots
Preety simple...:thumbup::thumbup:
Sent from my GT-S7392 using XDA Free mobile app
Yes
Thread updated.... Thanks to @ShadeSK for the help
Hi guys,
today I have something to share which will help you have a circled profile pic on your SystemUI like AOSP Lollipop/Zenui etc. ...... well it's lenox label but not the regular one, I moded it with CircleImageView smalis and make it Circle....... but neither lenox label nor circleimageview is mine both is made by @PineappleOwl .... and as I got he's permission for sharing this cool mod here we are......
Requirements :
1. Brain
2. Patience
3. Experience
4. Apktool or something like it
How to :
1. Decompile your SystemUI.apk
2. Go to res/layout/*wherever you want*
3. Add these :
Code:
<com.lenox.Lenox_Label.Circlelenoxpicture android:gravity="center" android:id="@+id/lenoxpic" android:layout_width="wrap_content" android:layout_height="wrap_content" />
<com.lenox.Lenox_Label.Circlelenoxlabel android:gravity="center" android:layout_gravity="bottom" android:id="@+id/lenoxlabel" android:background="#bf000000" android:layout_width="wrap_content" android:layout_height="wrap_content" />
4. Extract and attach the contents of "Circle_Lenox_Label_smali.zip" to your decompiled SystemUI
5. Recompile and decompile again
6. Time for id matching :
1. Go to res/values/public.xml and find this:
Code:
<public type="id" name="lenoxlabel" id="*x********" />
now take it's public id and go to smali/com/lenox/Lenox_Label/Circlelenoxlabel.smali and replace the public id you got on line no. 25 with:
Code:
const v7, 0x7f0d0144
2. Again go to res/values/public.xml and find this:
Code:
<public type="id" name="lenoxpic" id="*x********" />
now go to smali/com/lenox/Lenox_Label/Circlelenoxpicture.smali and replace the public id you have on line no.21 with:
Code:
const v4, 0x7f0d0143
7. Now recompile, sign, push with Circle_Lenox_Label.apk, reboot and enjoy !
Link :
Circle_Lenox_Label.apk
Circle_Lenox_Label_smali.zip
Credits :
@PineappleOwl for making everything here, I only combined them
Lenox devs
NOTES :
1. The app can't be installed as user app so you must push it to system
2. You need to uninstall the original Lenox Label app if you already have it installed
3. You can actually make CircleImageViews with this mod anywhere on your SystemUI as it has CircleImageView smalis...... just instead of <ImageView start your line with this:
Code:
<android.widget.CircleImageView
Original Lenox Label guide
Reserved
sdeepb said:
NOTES:
1. The app can't be installed as user app so you must push it to system
2. You need to uninstall the original Lenox Label app if you already have it installed
3. You can actually make CircleImageViews with this mod anywhere on your SystemUI as it has CircleImageView smalis...... just instead of <ImageView start your line with this:
Code:
<android.widget.CircleImageView
Link for original Lenox Label guide:
http://forum.xda-developers.com/android/themes/mod-lenox-label-profile-pic-label-mod-t3101642
Click to expand...
Click to collapse
Its nice bro
I 'll do that on JB TW and reports you success
mjraogr said:
Its nice bro
I 'll do that on JB TW and reports you success
Click to expand...
Click to collapse
Tested on my trend....... JB TW with no problems
Great piece of work @sdeepb keep it up!
Hello!
Im building a rom from AOSP source with some features. All is been fine on android-5.1.1_r5.
Problem started when i started merging _r6.
I decided to drop that and stay on _r5. Now i tried to merge _r8 to my _r5 sources, like this
cd <directory>
git fetch aosp (which ive directed to android.googlesource.com/<repo>)
git merge android-5.1.1_r8
All goes fine, few simple conflicts with build IDs or something.
And also ive changes on my manifest to sync android-5.1.1_r8 by default.
Now when i try to compile, i get these:
Code:
frameworks/opt/net/ims/src/java/com/android/ims/internal/ImsCallSession.java:925: error: ImsCallSession.IImsCallSessionListenerProxy is not abstract and does not override abstract method callSessionMultipartyStateChanged(IImsCallSession,boolean) in IImsCallSessionListener
private class IImsCallSessionListenerProxy extends IImsCallSessionListener.Stub {
^
Copying: /home/sicki/out//sgoptimized/target/common/obj/APPS/CertInstaller_intermediates/classes-jarjar.jar
Copying: /home/sicki/out//sgoptimized/target/common/obj/APPS/DownloadProviderUi_intermediates/classes-jarjar.jar
Copying: /home/sicki/out//sgoptimized/target/common/obj/APPS/HTMLViewer_intermediates/classes-jarjar.jar
frameworks/opt/net/ims/src/java/com/android/ims/ImsManager.java:803: error: ImsManager.ImsRegistrationListenerProxy is not abstract and does not override abstract method registrationDisconnected(ImsReasonInfo) in IImsRegistrationListener
private class ImsRegistrationListenerProxy extends IImsRegistrationListener.Stub {
^
frameworks/opt/net/ims/src/java/com/android/ims/ImsManager.java:828: error: method does not override or implement a method from a supertype
@Override
^
Copying: /home/sicki/out//sgoptimized/target/common/obj/APPS/KeyChain_intermediates/classes-jarjar.jar
frameworks/opt/net/ims/src/java/com/android/ims/ImsUt.java:358: error: method updateCallForward in interface IImsUt cannot be applied to given types;
int id = miUt.updateCallForward(action, condition, number, timeSeconds);
^
required: int,int,String,int,int
found: int,int,String,int
reason: actual and formal argument lists differ in length
frameworks/opt/net/ims/src/java/com/android/ims/ImsUt.java:385: error: method updateCallWaiting in interface IImsUt cannot be applied to given types;
int id = miUt.updateCallWaiting(enable);
^
required: boolean,int
found: boolean
reason: actual and formal argument lists differ in length
Copying: /home/sicki/out//sgoptimized/target/common/obj/APPS/LiveWallpapersPicker_intermediates/classes-jarjar.jar
Note: frameworks/opt/net/ims/src/java/com/android/ims/ImsUt.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
5 errors
My github: https://github.com/sicknemesis?tab=repositories
My manifest: https://github.com/sicknemesis/sickgreen_manifest/tree/sg-5.1.1_r8
Everything pushed after 5.1.1_r5 merge. Manifest points to r8 now just for to check that if something is missing or screwed.
Thank you very much if someone knows what im doing wrong how to fix this!
For simple minor updates, I usually just edit the manifest ([aosp_dir]/.repo/manifest.xml) and change the version string:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="aosp"
fetch=".." />
<default revision="refs/tags/android-5.1.1_[COLOR="Red"]r8[/COLOR]"
remote="aosp"
sync-j="4" />
<project path="build" name="platform/build" groups="pdk,tradefed" >
<copyfile src="core/root.mk" dest="Makefile" />
</project>
[ rest of manifest ]
Then just do a repo sync, lunch and make.
This usually works great and saves a lot of time syncing and building. If that fails, then a complete rebuild may be necessary.
Gene Poole said:
For simple minor updates, I usually just edit the manifest ([aosp_dir]/.repo/manifest.xml) and change the version string:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="aosp"
fetch=".." />
<default revision="refs/tags/android-5.1.1_[COLOR="Red"]r8[/COLOR]"
remote="aosp"
sync-j="4" />
<project path="build" name="platform/build" groups="pdk,tradefed" >
<copyfile src="core/root.mk" dest="Makefile" />
</project>
[ rest of manifest ]
Then just do a repo sync, lunch and make.
This usually works great and saves a lot of time syncing and building. If that fails, then a complete rebuild may be necessary.
Click to expand...
Click to collapse
There were changes on atleast device, frameworks, settings and contacts which i merged and pushed. And changed that revision number to sync everything else from right revision.
But now that ive searched, i see that after r5, something changed on branches. As far as i uderstand, r5 is lollipop-mr1-release branch and after that, its different branch, so merging everything from r6 - r8 to r5 base, will have conplications. And some that ive seen, r5 is actually newer than r6 actually is, because of those branch changes
Lähetetty minun Nexus 5 laitteesta Tapatalkilla
Sick1 said:
There were changes on atleast device, frameworks, settings and contacts which i merged and pushed. And changed that revision number to sync everything else from right revision.
But now that ive searched, i see that after r5, something changed on branches. As far as i uderstand, r5 is lollipop-mr1-release branch and after that, its different branch, so merging everything from r6 - r8 to r5 base, will have conplications. And some that ive seen, r5 is actually newer than r6 actually is, because of those branch changes
Lähetetty minun Nexus 5 laitteesta Tapatalkilla
Click to expand...
Click to collapse
did you manage to fix this error?
Things have been going good within the app and I have been running the app on my phone or tablet throughout the build with no issues.
All of a sudden, I have errors within the Manifest and it will not run/load on to my phone or tablet any longer.
I have googled for answers and "fixes" but have not been able to make any progress, I hope that I can get help here and get everything back in working order so I can move forward with the build.
The only thing I can think of that I did prior to seeing the errors was I may have "Alt+Enter" and chose API Google by accident at one point.
I went back and deleted all the Google things from my manifest and so forth. It was at this point I noticed the errors within the manifest.
AndroidManifest.xml
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.example.z.flowmaster">
<application ---------------------------> App is not indexable by Google Search; consider adding at least one Activity with an ACTION-VIEW intent filler.
android:allowBackup="true" --------------------------------------------- On SDK Version 23 and up, your app data will be automatically backed up and restored on app install. Consider adding the
android:icon="@mipmap/ic_launcher" ---------------------------------attribute android:fullBackupContent to specify an @xml resource which configures which files to backup. More info at ............
android:label="Backflow Master"
android:supportsRtl="true"
android:theme="@style/AppTheme" />
<activity android:name=".ActivityHome"> ------------> Element activity not allowed here / This inspection highlights unallowable XML ......
<intent-filter> --------------> Element intent-filter is not allowed here / This inspection highlights unallowable XML tags in Android rsource files & AndroidManifest.xml
<action android:name="android.intent.action.MAIN" /> --------> Element action is not allowed here / This inspection highlights unallowed XML .....
<category android:name="android.intent.category.LAUNCHER" /> --------> Element catagory is not allowed here / This inspection highlights ......
</intent-filter> ----------> Element intent-filter is not allowed here / This inspection highlights unallowable XML tags in Android resource files & AndroidMainfest.xml
</activity> --------------------------> says same as below "activity"
<activity android:name=".TestingMain" /> ---------------> "activity" is highlighted "Element activity is not allowed here."
<activity android:name=".TestingRP" /> --------------------------- This inspection highlights unallowed XML tags in Android resource files and AndroidManifest.xml
<activity android:name=".TestingDC" />
<activity android:name=".TestingPVB" />
<activity android:name=".TestingSRVB" />
<application/>
</manifest>
Assuming you are using AS, under the build tab in Android Studio, try clicking on "Clean" and then do a "Re-build"
Yes, I am using Android Studio 2.1.1
* However, I will note that at the time the error first occurred I was using 1.5.1 I believe.
After getting the error and trying a few things to rid the error, I finally just uninstalled the full program and reinstalled (new version) Android Studio.
I think I reinstalled everything correctly but I could have left something out or something is out of place I guess.
I feel like I have checked to make sure the reinstall was done correctly but that's not saying I didn't miss something...
After going to >Build >Clean Project I receive the following in my Messages "Gradle Build":
! A problem occurred evaluating project ':app'.
>Failed to apply plugin [id'com.android.application']
>Gradle version 2.10 is required. Current version is 2.8. If using the gradle wrapper, try editing the distributionUrl in C:/Users .....
! BUILD FAILED
! Total time: 0.611 secs
! 1 error
! 0 warnings
! See complete output in console
When I "Rebuild" it gives me the same as above.
Can you post the contents of your Gradle properties files here. I think this is where the issue lies "Gradle version 2.10 is required. Current version is 2.8. If using the gradle wrapper, try editing the distributionUrl in C:/Users ....."
-Project-
v Flowmaster
v app
build.gradle
apply plugin: 'com.android.application'
android {
compileSdkVersion 23
buildToolsVersion "23.0.1"
defaultConfig {
applicationId "com.example.z.flowmaster"
minSdkVersion 16
targetSdkVersion 23
versionCode 1
versionName "1.0"
}
buildTypes {
release {
minifyEnabled false
proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
}
}
}
dependencies {
compile fileTree(dir: 'libs', include: ['*.jar'])
testCompile 'junit:junit:4.12'
compile 'com.android.support:appcompat-v7:24.0.0-alpha1' ----------> This support library should not use a different version (24) than the compileSdkVersion(23) / There are some combinations of libraries, or tools and libraries, that are incompatible, or can lead to bugs. One such incompatibility is compiling with a version of the Android support libraries that is not the latest version (or in particular, a version lower than your targetSdkVersion.)
}
-Project-
v Flowmaster
v gradle
v wrapper
- gradle-wrapper.jar
v gradle-wrapper.properties
#Wed Oct 21 11:34:03 PDT 2015
distributionBase=GRADLE_USER_HOME
distributionPath=wrapper/dists
zipStoreBase=GRADLE_USER_HOME
zipStorePath=wrapper/dists
distributionUrl=https\://services.gradle.org/distributions/gradle-2.8-all.zip
-Project-
v Flowmaster
v gradle
- build.gradle
// Top-level build file where you can add configuration options common to all sub-projects/modules.
buildscript {
repositories {
jcenter()
}
dependencies {
classpath 'com.android.tools.build:gradle:2.1.0'
// NOTE: Do not place your application dependencies here; they belong
// in the individual module build.gradle files
}
}
allprojects {
repositories {
jcenter()
}
}
task clean(type: Delete) {
delete rootProject.buildDir
}
-Project-
v Flowmaster
v gradle
- build.properties
# Project-wide Gradle settings.
# IDE (e.g. Android Studio) users:
# Gradle settings configured through the IDE *will override*
# any settings specified in this file.
# For more details on how to configure your build environment visit
# http://www.gradle.org/docs/current/userguide/build_environment.html
# Specifies the JVM arguments used for the daemon process.
# The setting is particularly useful for tweaking memory settings.
# Default value: -Xmx10248m -XX:MaxPermSize=256m
# org.gradle.jvmargs=-Xmx2048m -XX:MaxPermSize=512m -XX:+HeapDumpOnOutOfMemoryError -Dfile.encoding=UTF-8
# When configured, Gradle will run in incubating parallel mode.
# This option should only be used with decoupled projects. More details, visit
# http://www.gradle.org/docs/current/userguide/multi_project_builds.html#sec:decoupled_projects
# org.gradle.parallel=true