Database Develop

Compile ADWLauncher

Hi everyone,
I cloned AOSP 2.2 sources
and then I replace Launcher2 folder in packages/apps with ADWLauncher from AndersWeb's github
Then "Make Launcher" returns me this:
Code:
target R.java/Manifest.java: Launcher2 (out/target/common/obj/APPS/Launcher2_intermediates/src/R.stamp)
target Java: Launcher2 (out/target/common/obj/APPS/Launcher2_intermediates/classes)
packages/apps/Launcher2/src/com/android/launcher/Launcher.java:1221: cannot find symbol
symbol : variable SOURCE
location: class android.app.SearchManager
appSearchData.putString(SearchManager.SOURCE, "launcher-search");
^
packages/apps/Launcher2/src/com/android/launcher/MyLauncherSettings.java:58: method does not override a method from its superclass
@Override
^
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
2 errors
make: *** [out/target/common/obj/APPS/Launcher2_intermediates/classes-full-debug.jar] Erreur 41
Here is the result from standalone branch:
Code:
target R.java/Manifest.java: Launcher (out/target/common/obj/APPS/Launcher_intermediates/src/R.stamp)
aapt: warning: string 'pref_dialog_drawer_background_alpha' has no default translation in packages/apps/android_packages_apps_Launcher/res; found: el es
aapt: warning: string 'pref_summary_drawer_background_alpha' has no default translation in packages/apps/android_packages_apps_Launcher/res; found: el es
aapt: warning: string 'pref_title_drawer_background_alpha' has no default translation in packages/apps/android_packages_apps_Launcher/res; found: el es
Warning: AndroidManifest.xml already defines versionCode (in http://schemas.android.com/apk/res/android); using existing value in manifest.
Warning: AndroidManifest.xml already defines versionName (in http://schemas.android.com/apk/res/android); using existing value in manifest.
Warning: AndroidManifest.xml already defines minSdkVersion (in http://schemas.android.com/apk/res/android); using existing value in manifest.
target Java: Launcher (out/target/common/obj/APPS/Launcher_intermediates/classes)
packages/apps/android_packages_apps_Launcher/src/org/adw/launcher/Workspace.java:1773: method does not override a method from its superclass
@Override
^
packages/apps/android_packages_apps_Launcher/src/org/adw/launcher/Workspace.java:1778: method does not override a method from its superclass
@Override
^
packages/apps/android_packages_apps_Launcher/src/org/adw/launcher/Workspace.java:1784: method does not override a method from its superclass
@Override
^
packages/apps/android_packages_apps_Launcher/src/org/adw/launcher/Workspace.java:1793: method does not override a method from its superclass
@Override
^
packages/apps/android_packages_apps_Launcher/src/org/adw/launcher/DesktopIndicator.java:212: method does not override a method from its superclass
@Override
^
packages/apps/android_packages_apps_Launcher/src/org/adw/launcher/DesktopIndicator.java:217: method does not override a method from its superclass
@Override
^
packages/apps/android_packages_apps_Launcher/src/org/adw/launcher/DesktopIndicator.java:221: method does not override a method from its superclass
@Override
^
packages/apps/android_packages_apps_Launcher/src/org/adw/launcher/MyLauncherSettings.java:101: method does not override a method from its superclass
@Override
^
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
8 errors
make: *** [out/target/common/obj/APPS/Launcher_intermediates/classes-full-debug.jar] Erreur 41
Could you help me?
thx

You should remove the override lines,
And for froyo, there's no an official system branch made by myself. I'd need to remove a few code parts, cause in froyo, the search widget is no more needed inside the launcher.

AnderWeb said:
You should remove the override lines,
And for froyo, there's no an official system branch made by myself. I'd need to remove a few code parts, cause in froyo, the search widget is no more needed inside the launcher.
Click to expand...
Click to collapse
Okay.
Thank you very much.
Hope you'll release the sources for FroYo soon

leonnib4 said:
Okay.
Thank you very much.
Hope you'll release the sources for FroYo soon
Click to expand...
Click to collapse
The actual standalone branch is froyo compatible, you just need to remove the overrides if you don't build within eclipse.

AnderWeb said:
The actual standalone branch is froyo compatible, you just need to remove the overrides if you don't build within eclipse.
Click to expand...
Click to collapse
thanks!
10chars

Hi leo, its nice to see that we are working and struggling in the same stuff, great minds think alike and it seems they mess alike too ^^
Anyway nice work both of you.

Since the repo was updated,
I only had to remove some @overides as AndersWeb told me and everything was fine.

[Q] COMILE ERROR : undefined reference to `__bad_udelay'

Is there anyone to give advice to me this compiling error?
When compile with CFLAG '-O2' option, it's successful but '-O3' can't be.
Compile Error message :
drivers/built-in.o: In function `mcsdl_delay':
Kernel/drivers/input/keyboard/melfas_download.c:1779: undefined reference to `__bad_udelay'
Kernel/drivers/input/keyboard/melfas_download.c:1779: undefined reference to `__bad_udelay'
Kernel/drivers/input/keyboard/melfas_download.c:1779: undefined reference to `__bad_udelay'
Kernel/drivers/input/keyboard/melfas_download.c:1779: undefined reference to `__bad_udelay'
Kernel/drivers/input/keyboard/melfas_download.c:1779: undefined reference to `__bad_udelay'
make: *** [.tmp_vmlinux1] Error 1
Compiling infor is following;
- galaxy S M110S
- Toolchain :codesourcery 2010.9-51 arm-none-eabi-
- compile option : -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs \
-fno-strict-aliasing -fno-common \
-Werror-implicit-function-declaration \
-Wno-format-security \
-fno-delete-null-pointer-checks \
-mcpu=cortex-a8 \
-mfpu=neon -mfloat-abi=softfp
- KBUILD_CFLAGS += -O3
The body of 'melfas_download.c' about 1779line
Code:
//============================================================
//
// Delay Function
//
//============================================================
static void mcsdl_delay(UINT32 nCount)
{
#if 1
udelay(nCount); //1 Baseband delay function
#else
UINT32 i;
for(i=0;i<nCount;i++){
}
#endif
}

problem when build LKM

Here is a loadable kernel module for HTC Sensation XL (runnymede-crc-2.6.35).
/*
* mydebug.c
* System Call sys_open dubugging
*/
#include <linux/kernel.h> /* Needed for KERN_INFO */
#include <linux/module.h> /* Needed by all modules */
#include <linux/init.h> /* Needed for macros */
#include <asm/unistd.h>
#include <linux/linkage.h>
#include <generated/autoconf.h>
#include <linux/in.h>
#include <linux/init_task.h>
#include <linux/ip.h>
#include <linux/kernel.h>
#include <linux/kmod.h>
#include <linux/mm.h>
#include <linux/skbuff.h>
#include <linux/workqueue.h>
#include <linux/sched.h>
#include <linux/stddef.h>
#include <linux/string.h>
#include <linux/syscalls.h>
#include <linux/tcp.h>
#include <linux/types.h>
#include <linux/version.h>
asmlinkage ssize_t (*orig_open)(const char *pathname, int flags);
asmlinkage ssize_t hooked_open(const char *pathname, int flags)
{
printk(KERN_INFO "SYS_OPEN: %s\n", pathname);
return orig_open(pathname, flags);
}
static int __init root_start(void)
{
unsigned long sys_addr = 0xc003b104; /* System.map */
unsigned long *sys_call_table= (unsigned long *)sys_addr;
orig_open = sys_call_table[__NR_open];
sys_call_table[__NR_open] = hooked_open;
return 0;
}
static void __exit root_stop(void)
{
unsigned long sys_addr = 0xc003b104;
unsigned long *sys_call_table= (unsigned long *)sys_addr;
sys_call_table[__NR_open] = &orig_open;
}
module_init(root_start);
module_exit(root_stop);
-------
When I buid it, the error shows below,
make -C /home/scott/runnymede-crc-2.6.35/ M=`pwd` ARCH=arm CROSS_COMPILE=~/android-ndk-r7b/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi- modules
make[1]: Entering directory `<home>/runnymede-crc-2.6.35'
CC [M] /<home>/workspace/debugkit/mydebug.o
cc1: warnings being treated as errors
/<home>/workspace/debugkit/mydebug.c: In function 'root_start':
/<home>/workspace/debugkit/mydebug.c:44: error: assignment makes pointer from integer without a cast
/<home>/workspace/debugkit/mydebug.c:45: error: assignment makes integer from pointer without a cast
/<home>/workspace/debugkit/mydebug.c: In function 'root_stop':
/<home>/workspace/debugkit/mydebug.c:55: error: assignment makes integer from pointer without a cast
make[2]: *** [/<home>/workspace/debugkit/mydebug.o] Error 1
make[1]: *** [_module_/<home>/workspace/debugkit] Error 2
make[1]: Leaving directory `/home/scott/runnymede-crc-2.6.35'
make: *** [default] Error 2
Anyone can give me a help for it?

2 things...
you should change in the menu : warnings being treated as errors...this will stop building the kernel also if its only a warning
also you can have probs with the toolchain...you can try this:
http://forum.xda-developers.com/showpost.php?p=23367049&postcount=112
with kind regards

[Q][Kernel][DEVS] 3.0.8 Kernel Question

Please HELP
I ported SIO,
THis is what i get:
Code:
block/sio-iosched.c:315:3: error: unknown field 'elevator_queue_empty_fn' specified in initializer
block/sio-iosched.c:315:3: warning: initialization from incompatible pointer type [enabled by default]
block/sio-iosched.c:315:3: warning: (near initialization for 'iosched_sio.ops.elevator_activate_req_fn') [enabled by default]
make[1]: *** [block/sio-iosched.o] Error 1
make: *** [block] Error 2
I only dont understand elevator queue empty. I think i should add a queue for it?

You porting SIO from where?
Do you know the basic of C language?
Read this GNU GCC.

nicholaschw said:
Please HELP
I ported SIO,
THis is what i get:
Code:
block/sio-iosched.c:315:3: error: [B]unknown field[/B] 'elevator_queue_empty_fn' [B]specified in initializer[/B]
block/sio-iosched.c:315:3: warning: initialization from incompatible pointer type [enabled by default]
block/sio-iosched.c:315:3: warning: (near initialization for 'iosched_sio.ops.elevator_activate_req_fn') [enabled by default]
make[1]: *** [block/sio-iosched.o] Error 1
make: *** [block] Error 2
I only dont understand elevator queue empty. I think i should add a queue for it?
Click to expand...
Click to collapse
I'll explain.
Code:
//Test Application
typedef struct _user{
const char* name;
const char* password;
char age;
} user;
int main(){
//And we initialize it
struct _user someUser = {
//Lets initialize the variables
.name = "James Bond",
.password = "007",
.age = 21,
//Lets be rebel and break it
.unkownVariable = "Unkown Value"
};
//You are calling a field thats not there
//Exit Gracefully
return 0;
}
The code you tried porting into your kernel is made for a different kernel (not 3.0.8) or you simply forgot a inlcude somewhere,

xonar_ said:
I'll explain.
Code:
//Test Application
typedef struct _user{
const char* name;
const char* password;
char age;
} user;
int main(){
//And we initialize it
struct _user someUser = {
//Lets initialize the variables
.name = "James Bond",
.password = "007",
.age = 21,
//Lets be rebel and break it
.unkownVariable = "Unkown Value"
};
//You are calling a field thats not there
//Exit Gracefully
return 0;
}
The code you tried porting into your kernel is made for a different kernel (not 3.0.8) or you simply forgot a inlcude somewhere,
Click to expand...
Click to collapse
Jackpot. I ported from 2. 6. 3. 5. Help me. Everything is ready in github
Sent from my LG-P970 using Tapatalk 2

nicholaschw said:
Jackpot. I ported from 2. 6. 3. 5. Help me. Everything is ready in github
Sent from my LG-P970 using Tapatalk 2
Click to expand...
Click to collapse
Try looking at what the headers look like to look for the difference that broke it. It's possible that they just changed the name and just renaming it could fix. Its also possible that they made crucial design changes and it will stay broken unless you port it from another kernel with very similar headers. I'm going to be busy now for a few hours so I can't check it now.
Sent from my LG-P970

how to inflate a layout which is in the res directory of my own module?

Hi everyone:
how could I use View.inflate() to inflate a layout which is in the res directory of my own module? I want to add this layout into the target app’s view container.
I had tried to generate a fakeId for this layout xml resource file by this way:
Code:
fun initZygote(startupParam: IXposedHookZygoteInit.StartupParam?) {
MODULE_PATH = startupParam?.modulePath
}
fun handleInitPackageResources(resparam: XC_InitPackageResources.InitPackageResourcesParam?) {
val modRes = XModuleResources.createInstance(MODULE_PATH, resparam.res)
ID_MENU = resparam.res.addResource(modRes, R.layout.menu_littlespider)
}
then I use this ID_MENU to to inflate it:
Code:
override fun handleLoadPackage(lpparam: XC_LoadPackage.LoadPackageParam?){
findAndHookMethod(C.View, "inflate", C.Context, C.Int, C.ViewGroup, object : XC_MethodHook() {
override fun afterHookedMethod(param: MethodHookParam?) {
if (param == null) return
val context = param.args[0] as Context
var targetViewId = param.args[1] as Int
if (targetViewId == 2130904238) {
var targetView = param.result as LinearLayout
val layoutParser = context.resources.getLayout(InitResourceHooker.ID_MENU)
val menu = LayoutInflater.from(context).inflate(layoutParser, null)
//val menu = View.inflate(context, InitResourceHooker.ID_MENU, null) as LinearLayout
targetView.addView(menu, 0)
}
}
})
}
sadly,it gives me an error,#0x7eb8f41b is my FakeId :
Code:
android.content.res.Resources$NotFoundException: Resource ID #0x7eb8f41b
can anyone show me is it possible to inflate this layout?
thanks a lot!

吃泡面的猫儿 said:
Hi everyone:
how could I use View.inflate() to inflate a layout which is in the res directory of my own module? I want to add this layout into the target app’s view container.
I had tried to generate a fakeId for this layout xml resource file by this way:
then I use this ID_MENU to to inflate it:
sadly,it gives me an error,#0x7eb8f41b is my FakeId :
can anyone show me is it possible to inflate this layout?
thanks a lot!
Click to expand...
Click to collapse
Hint: use getResourcesForApplication
Background: Xposed hooks run in the context of the hooked app.

Also, you can inflate layout without adding it to hooked app resources provided you create instance of LayoutInflater using your xposed app context.
Code:
Context ctx = context.createPackageContext("your_xposed_app_pkg_name", Context.CONTEXT_IGNORE_SECURITY);
LayoutInflater inflater = LayoutInflater.from(ctx);
inflater.inflate(R.layout.your_layout, parent);
The thing is, layout can contain only such elements that are known to hooked app classloader.
E.g. you won't be able to inflate layout that contains some custom views that were defined within your app, as inflater created within hooked app won't be able to resolve them.

C3C076 said:
Also, you can inflate layout without adding it to hooked app resources provided you create instance of LayoutInflater using your xposed app context.
Code:
Context ctx = context.createPackageContext("your_xposed_app_pkg_name", Context.CONTEXT_IGNORE_SECURITY);
LayoutInflater inflater = LayoutInflater.from(ctx);
inflater.inflate(R.layout.your_layout, parent);
The thing is, layout can contain only such elements that are known to hooked app classloader.
E.g. you won't be able to inflate layout that contains some custom views that were defined within your app, as inflater created within hooked app won't be able to resolve them.
Click to expand...
Click to collapse
Hi, i wonder if i can inflate layout which is in res directory of my app target?