Hi dudes, so im trying to get the T9 dialer from CM9 onto 4.1.1 ROM for the Galaxy Nexus..
This is far as i got:
It all works 100% BUT the app names have changed to "true" and "false" lol
I know its because the androidmanifest is pointing to the wrong value but im not sure how to fix it... can anyone point me in the right direction?
Cheers
attatched is the Contacts.apk working with the wrong app names
I'm driving into work. I'll look when I get in.
Sent from my Galaxy Nexus using xda premium
lithid-cm said:
I'm driving into work. I'll look when I get in.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Awesome bro I gave up after my mouse went flat and i chucked it out the window lol. You might have an issue decompiling it also, if you do its because of the manifest... sure you'll figure that out though.
Sent from my Galaxy Nexus using Tapatalk 2
CdTDroiD said:
Awesome bro I gave up after my mouse went flat and i chucked it out the window lol. You might have an issue decompiling it also, if you do its because of the manifest... sure you'll figure that out though.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Why not just zip up the source code? I am grabbing apktool now, but shouldn't be a reason with this being aosp after all.
Line:
Code:
<application android:label="@bool/config_use_two_panes" android:icon="@mipmap/ic_launcher_contacts" android:name="com.android.contacts.ContactsApplication" android:taskAffinity="android.task.contacts" android:hardwareAccelerated="true">
Needs to change
Code:
@bool/config_use_two_panes > @string/contactsList
=====
Line:
Code:
<activity android:theme="@style/DialtactsTheme" android:label="@bool/config_editor_field_order_primary" android:icon="@mipmap/ic_launcher_phone" android:name=".activities.DialtactsActivity" android:enabled="@android:bool/config_bluetooth_wide_band_speech" android:taskAffinity="android.task.contacts.phone" android:clearTaskOnLaunch="true" android:launchMode="singleTask" android:screenOrientation="portrait" android:windowSoftInputMode="stateAlwaysHidden|adjustNothing" android:uiOptions="splitActionBarWhenNarrow">
Need to change
Code:
@bool/config_editor_field_order_primary > @string/launcherDialer
=====
Line:
Code:
<activity android:theme="@style/PeopleTheme" android:label="@bool/config_editor_include_phonetic_name" android:name=".activities.PeopleActivity" android:clearTaskOnLaunch="true" android:launchMode="singleTop" android:uiOptions="splitActionBarWhenNarrow">
Need to change
Code:
@bool/config_editor_include_phonetic_name > @string/people
=====
Line:
Code:
<activity android:theme="@style/ContactPickerLayout" android:label="@bool/config_use_two_panes" android:name=".activities.ContactSelectionActivity" android:clearTaskOnLaunch="true" android:launchMode="singleTop" android:uiOptions="splitActionBarWhenNarrow">
Need to change
Code:
@bool/config_use_two_panes > @string/contactsList
That should be it. Enjoy.
lithid-cm said:
Why not just zip up the source code? I am grabbing apktool now, but shouldn't be a reason with this being aosp after all.
Click to expand...
Click to collapse
Heres the decompiled version, Ive also included the modified AndroidManifest.xml that it needs to install the app (But wont decompile)
The manifest in the source is the CM9 one
lithid-cm said:
Line:
Code:
<application android:label="@bool/config_use_two_panes" android:icon="@mipmap/ic_launcher_contacts" android:name="com.android.contacts.ContactsApplication" android:taskAffinity="android.task.contacts" android:hardwareAccelerated="true">
Needs to change
Code:
@bool/config_use_two_panes > @string/contactsList
=====
Line:
Code:
<activity android:theme="@style/DialtactsTheme" android:label="@bool/config_editor_field_order_primary" android:icon="@mipmap/ic_launcher_phone" android:name=".activities.DialtactsActivity" android:enabled="@android:bool/config_bluetooth_wide_band_speech" android:taskAffinity="android.task.contacts.phone" android:clearTaskOnLaunch="true" android:launchMode="singleTask" android:screenOrientation="portrait" android:windowSoftInputMode="stateAlwaysHidden|adjustNothing" android:uiOptions="splitActionBarWhenNarrow">
Need to change
Code:
@bool/config_editor_field_order_primary > @string/launcherDialer
=====
Line:
Code:
<activity android:theme="@style/PeopleTheme" android:label="@bool/config_editor_include_phonetic_name" android:name=".activities.PeopleActivity" android:clearTaskOnLaunch="true" android:launchMode="singleTop" android:uiOptions="splitActionBarWhenNarrow">
Need to change
Code:
@bool/config_editor_include_phonetic_name > @string/people
=====
Line:
Code:
<activity android:theme="@style/ContactPickerLayout" android:label="@bool/config_use_two_panes" android:name=".activities.ContactSelectionActivity" android:clearTaskOnLaunch="true" android:launchMode="singleTop" android:uiOptions="splitActionBarWhenNarrow">
Need to change
Code:
@bool/config_use_two_panes > @string/contactsList
That should be it. Enjoy.
Click to expand...
Click to collapse
I know thats what i figured, sorry should have been clearer, my issue is i cant recompile with that AndroidManifest...
CdTDroiD said:
I know thats what i figured, sorry should have been clearer, my issue is i cant recompile with that AndroidManifest...
Click to expand...
Click to collapse
Are you using apktool, sources? When you say recompile.
lithid-cm said:
Are you using apktool, sources? When you say recompile.
Click to expand...
Click to collapse
Yea using apktool 1.4.3
java -jar apktool.jar b Contacts
To get it to install on the device i used the 4.1.1 manifest from my original Contacts.apk and the META folder for signing, otherwise it wont install, and for some reason i dont understand it seems to change the manifest on install or something crazy... either that or im just to tired and missing something lol
SO it will only recompile if i use the CM9 Contacts manifest
heres the pastebin of the recompile
http://pastebin.com/yQLnVeSy
Ah right its because of the MANIFEST.MF that im using that is screwing it up...
but how do i get around that? Thanks for your help by the way mate
CdTDroiD said:
Ah right its because of the MANIFEST.MF that im using that is screwing it up...
but how do i get around that? Thanks for your help by the way mate
Click to expand...
Click to collapse
I guess I don't understand why you are making it harder then it is. This is aosp, you should be using an aosp base, making your changes and compiling. This isn't a sense, blur, touchwiz or miui. Sources are available and there is no reason to use apktool. Chances are it's a bug, I would go about it the right way and just build the app from source. If you need my help to work out issues with apktool, I can't help you. I would though be more then happy to help you build it the right way.
lithid-cm said:
I guess I don't understand why you are making it harder then it is. This is aosp, you should be using an aosp base, making your changes and compiling. This isn't a sense, blur, touchwiz or miui. Sources are available and there is no reason to use apktool. Chances are it's a bug, I would go about it the right way and just build the app from source. If you need my help to work out issues with apktool, I can't help you. I would though be more then happy to help you build it the right way.
Click to expand...
Click to collapse
Ok i didnt even think of it for some reason, ill compile it from source and see how i go... Thanks mate
Related
Hello Guys and Galls,
I want to change the background of Settings.apk from black to white. I use the FroyoMod Rom http://forum.xda-developers.com/showthread.php?t=815595.
If change
Code:
<application android:label="@string/settings_label" android:icon="@drawable/ic_launcher_settings" android:taskAffinity="">
to
Code:
<application android:theme=[COLOR="Red"]"@android:style/Theme.Light.NoTitleBar"[/COLOR] android:label="@string/settings_label" android:icon="@drawable/ic_launcher_settings" android:taskAffinity="">
in AndroidManifest.xml.
I use ApkManger to decompile and compile. The (de)compiling is without any errors.
After compile with ApkManager i do the follow:
- open original Settings.apk and unsignedSettings.apk with 7-zip
- delete AndrodManifest.xml in original Settings.apk
- copy AndroidManifest.xml from unsignedSettings.apk to original Settings.apk
- copy the modified original Settings.apk to the phone in /system/app
- chmod 644 Settings.apk
- chown root:root Settings.apk
So now if I start Settings nothing happens, nothing, not even an fc.
This is was logcat says:
Code:
com.android.settings has no certificates at entry AndroidManifest.xml
What I´m doing wrong?
Try one of the many apk re-packaging tools on this forum. Ive used apktool but there are some front ends built for it
From something awesome
killersnowman said:
Try one of the many apk re-packaging tools on this forum.
Click to expand...
Click to collapse
tigger-gg said:
I use ApkManger to decompile and compile.
Click to expand...
Click to collapse
By the way if I change any other xml file in /res there are no such problems.
tigger-gg said:
I use ApkManger to decompile and compile.
Click to expand...
Click to collapse
dur
i read this on the mobile and did not see that....
solving the problem? because I would be interested
Me too, I'm having a problem recompiling an AndroidManifest.xml with apkmanager 5.0.1., it won't install unless I use an original AndroidManifest.xml file first, then I can flash right over it. At first I thought it was a the change I made in the file, but I just decompiled and compiled an unmodified version, and it did the same thing. So its the compiler.
Settings.apk is a signed system app. It will refuse to run unless signed by the same key as the rest of the system apps. Just replacing a single XML in the APK will cause a signature mismatch.
Best bet? I'd say make your change, then use a kitchen like dsixda's to resign the whole system with the test key (I think this is a menu option).
Yep your whole system has to have the same signature. I did this edit for a rom a while back, but I made the settings transparent instead of white background by using Theme.Wallpaper.NoTitlebar. Just sign your whole rom together with testkeys and all should be good until another system app gets changed/modified and the signatures don't match again.
Sent from my PG06100 using Tapatalk
Thanks to Gene Poole and one_love_420, I will try your instructions.
If your after quickly signing a whole load of apk's, I wrote a command line front end to do all the hard work for you.
You can even generate your own private key.
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums
Moving to Q&A
BUMP to top
Please big problem been fighting for weeks
any one know anything about this!!
So anybody find a solution yet? Seems to be the binary text conversion.
It is the signitures in manifest.inf fyi
I've got adw launcher decompiled and I would like to change startup defaults. To start out I'd like to change the startup main dock style from 3 to 5. Can someone tell me which xml file and variable holds this value?
config_main_dock_style is in res/values/config.xml -- atleast according to CM7's version.
https://github.com/CyanogenMod/andr...er/blob/gingerbread/res/values/config.xml#L77
FaultException said:
config_main_dock_style is in res/values/config.xml -- atleast according to CM7's version.
https://github.com/CyanogenMod/andr...er/blob/gingerbread/res/values/config.xml#L77
Click to expand...
Click to collapse
Thanks for the reply. it turned out to be:
Code:
<string name="config_main_dock_style">2</string>
located in values/strings.xml
jocala said:
Thanks for the reply. it turned out to be:
Code:
<string name="config_main_dock_style">2</string>
located in values/strings.xml
Click to expand...
Click to collapse
Ah. Must be a different version.
Fellow Android chefs, I need some help.
Up to Android 4.1.2 you could easily change the Settings background by replacing the framework-res/res/drawable-nodpi/background_holo_dark.png. This png was also responsible for background in SystemUI, Mms and some other apps.
From Android 4.2.0 Google changed this behavior. They've hardcoded it in the /framework-res/red/drawable/background_holo_dark.xml and have moved from png resource to color - gradient or solid.
This is the content of background_holo_dark.xml:
Code:
<?xml version="1.0" encoding="utf-8"?>
<shape
xmlns:android="http://schemas.android.com/apk/res/android">
<gradient android:startColor="#ff000000" android:endColor="#ff272d33" android:angle="270.0" />
</shape>
I have a problem reverting this change back to the pre-4.2.0 behavior, means - I want to use the background_holo_dark.png instead of the coded color in the xml.
Any thoughts?
Are images referable in xml files?
I know nothing of ROM development, I'll try not to be nuisance, but here goes...
Can you store the .png you want to use somewhere suitable, and then refer to it in the /framework-res/red/drawable/background_holo_dark.xml file?
for example (pseudo code, n00b remember )
Code:
<image = /where/ever/the/image/is/stored.png
</image>
Hope this helps (at least a bit)
Thanks for the reply. Yes, I know that I need to point in the xml to the png, but I don't know the right format that's xml expecting.
brainmaster said:
Thanks for the reply. Yes, I know that I need to point in the xml to the png, but I don't know the right format that's xml expecting.
Click to expand...
Click to collapse
Oh, I see. Sorry I couldn't've been of more help.
---edit---
Wait a moment, I confess I don't think I read your Q properly: I didn't realise it was coded into framework-res.apk, I assumed it was contained within Settings.apk .
HTCDreamOn said:
Oh, I see. Sorry I couldn't've been of more help.
Click to expand...
Click to collapse
No problem. I appreciate the effort.
Sorry for intruding but take a look here. See the last part of post 36. If you still don't get it, just PM Uber.
http://forum.xda-developers.com/showpost.php?p=36079807&postcount=36
Sent from my Nexus 7
veeman said:
Sorry for intruding but take a look here. See the last part of post 36. If you still don't get it, just PM Uber.
http://forum.xda-developers.com/showpost.php?p=36079807&postcount=36
Sent from my Nexus 7
Click to expand...
Click to collapse
Thanks, gonna take a look.
The next question would be - how can i delete xml through the VRTheme System?
Note: THIS IS A DEV thread, not a "I WANT THIS ROM NAU" thread
Local Manifest
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="photon"
fetch="git://github.com/photon-dev-team/" />
<!-- CM Removals -->
<!-- remove-project name="CyanogenMod/android_frameworks_base" / -->
<!-- remove-project name="CyanogenMod/android_system_core" / -->
<!-- remove-project name="CyanogenMod/android_vendor_cm" / -->
<!-- CM Replacements -->
<!-- project path="frameworks/base" name="dragonzkiller/android_frameworks_base" / -->
<!-- project path="system/core" name="dragonzkiller/android_system_core" / -->
<!-- project path="vendor/cm" name="dragonzkiller/android_vendor_cm" / -->
<!-- Photon-Dev-Team Stuff -->
<project path="vendor/moto" name="proprietary_vendor_motorola" remote="photon" />
<!-- Local Projects -->
<project path="kernel/tegra" name="dragonzkiller/daytona-kernel" revision="gb-2.6.32.9" />
<project path="device/moto/daytona" name="iPonyRadio/android_device_moto_daytona" revision="jellybean" />
<project path="vendor/moto/daytona" name="dragonzkiller/android_vendor_moto_daytona" revision="ics" />
</manifest>
Alright, so if you want to help, make sure you have a properly setup CM build enviornment
Code:
mkdir cm11
cd cm11
repo init -u https://github.com/CyanogenMod/android.git -b "cm-11.0"
mkdir .repo/local_manifests/
curl -L -o .repo/local_manifests/daytona.xml -O - L https://raw.guthub.com/iPonyRadio/android_local_daytona/ics/local_manifest.xml
repo sync (this will take a while)
. build/envsetup.sh
brunch daytona
Yoink
This thing is ridiculous
building returns a different error each time
Http://pixelperfectserver.tk/daytona.txt
Been playing around with my x2 back on stock since I have a different main phone. Its not as bad as I remember once you gain root and uninstall the Verizon bloatware.
That being said, I'm looking forward to see what comes of this.
Sent from my LG-LS970 using xda app-developers app
Watching this thread for sure. My X2 has long been shelved but I might break it out for fun if we get a reasonable Alpha build out of this.
I don't have the time nor expertise to help with the build, but I'm always willing to test drive, especially on a device I don't use, and I'm pretty good with logcat.
Thanks for the build thread and good luck!
ajbiz11 said:
This thing is ridiculous
building returns a different error each time
Http://pixelperfectserver.tk/daytona.txt
Click to expand...
Click to collapse
bootable/recovery/minui/../../../device/moto/daytona/recovery/graphics.c:186:5: error: conflicting types for 'gr_text'
http://osxr.org/android/ident?_i=gr_text
meh?
ajbiz11 said:
Note: THIS IS A DEV thread, not a "I WANT THIS ROM NAU" thread
Local Manifest
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="photon"
fetch="git://github.com/photon-dev-team/" />
<!-- CM Removals -->
<!-- remove-project name="CyanogenMod/android_frameworks_base" / -->
<!-- remove-project name="CyanogenMod/android_system_core" / -->
<!-- remove-project name="CyanogenMod/android_vendor_cm" / -->
<!-- CM Replacements -->
<!-- project path="frameworks/base" name="dragonzkiller/android_frameworks_base" / -->
<!-- project path="system/core" name="dragonzkiller/android_system_core" / -->
<!-- project path="vendor/cm" name="dragonzkiller/android_vendor_cm" / -->
[/CODE]
Click to expand...
Click to collapse
You may be able to get dragonzkiller to help you if he is not already working on such or collaborate with him.
Please excuse my noobishness.
When I use the command
repo sync
I get fetch errors for refs/heads/cm-11.0
When I do repo sync -f
I get an error : revision refs/heads/cm-11.0 in proprietary_vendor_motorola not found
The subsequent
brunch daytona
then it fails because the daytona device is not found.
I assume I have to do a rather simple change to a manifest, but being the complete noob I am, I would appreciate
some assistance.
polymath257 said:
Please excuse my noobishness.
When I use the command
repo sync
I get fetch errors for refs/heads/cm-11.0
When I do repo sync -f
I get an error : revision refs/heads/cm-11.0 in proprietary_vendor_motorola not found
The subsequent
brunch daytona
then it fails because the daytona device is not found.
I assume I have to do a rather simple change to a manifest, but being the complete noob I am, I would appreciate
some assistance.
Click to expand...
Click to collapse
Try rm -rf .repo
then the repo init with -f on the end
If not, I may look into it later
smallzfsu said:
bootable/recovery/minui/../../../device/moto/daytona/recovery/graphics.c:186:5: error: conflicting types for 'gr_text'
http://osxr.org/android/ident?_i=gr_text
meh?
Click to expand...
Click to collapse
Dead link
Now that the holiday is pretty much over I'm getting back on my PC...so...YAY!
unimatrix725 said:
You may be able to get dragonzkiller to help you if he is not already working on such or collaborate with him.
Click to expand...
Click to collapse
Tried PM-ing him long ago, still nothing back...
ajbiz11 said:
Tried PM-ing him long ago, still nothing back...
Click to expand...
Click to collapse
he didnt really ever like PM's...
this thread makes me wish i didnt trade the dx2 in for the 5$ at verizon when i bought my gnex lol...or id try and give this all a shot and see what could be done..best of luck friends
pattyboi:) said:
he didnt really ever like PM's...
this thread makes me wish i didnt trade the dx2 in for the 5$ at verizon when i bought my gnex lol...or id try and give this all a shot and see what could be done..best of luck friends
Click to expand...
Click to collapse
Yeah, I figured
And the Nexi will always be a better device than the X2
Also...I've decided to take baby steps towards cm11...I'm working on 10.1 right now
I got it to a point where I need a boot-hijack.zip....I see nothing about one anywhere...
ajbiz11 said:
Yeah, I figured
And the Nexi will always be a better device than the X2
Also...I've decided to take baby steps towards cm11...I'm working on 10.1 right now
I got it to a point where I need a boot-hijack.zip....I see nothing about one anywhere...
Click to expand...
Click to collapse
give me one sec i think i might no where there is one
EDIT: http://d-h.st/1jF :credit to Bluphant
here you go buddy,this is made specifically for cm10.1 already,so that might help a lil,ill try and help you find you anything you need ,i just dont have a test device lol
pattyboi:) said:
give me one sec i think i might no where there is one
EDIT: http://d-h.st/1jF :credit to Bluphant
here you go buddy,this is made specifically for cm10.1 already,so that might help a lil,ill try and help you find you anything you need ,i just dont have a test device lol
Click to expand...
Click to collapse
Alright
Now to see if this will work with the compile by putting it in the OUT dir like the compiler is asking, or if I need to modify the makefiles to zip the device/moto/daytona/hijack/hijack-boot/
ajbiz11 said:
Alright
Now to see if this will work with the compile by putting it in the OUT dir like the compiler is asking, or if I need to modify the makefiles to zip the device/moto/daytona/hijack/hijack-boot/
Click to expand...
Click to collapse
start with having the make compress the hijack. also make clean each time, a pain in the ass as it forces a complete restart but it will hopefully produce more consistant errors. though dont take this for truth, im just making a wild guess from my attemps at building cm10
Lrs121 said:
start with having the make compress the hijack. also make clean each time, a pain in the ass as it forces a complete restart but it will hopefully produce more consistant errors. though dont take this for truth, im just making a wild guess from my attemps at building cm10
Click to expand...
Click to collapse
hi guys, saw the project you all are working on. i'm one of the guys over on dx working on the kk build/development. i know that the dx and the dx2 are different devices with different configurations, but i'm coming here for a possible lead or inspiration on what i need to do to help with our project. http://forum.xda-developers.com/showthread.php?p=48051920 is the link showing our current attempts.
i stumbled across this thread at a good time i think. the issue we're running into does deal with the hijack-boot.zip.
make: *** No rule to make target `home/davidmcleod/android-cm11.0/out/target/product/shadow/hijack-boot.zip', needed by `/home/davidmcleod/android-cm11.0/out/target/product/shadow/obj/ETC/hijack-boot.zip_intermediates/hijack-boot.zip'. Stop.
we keep on running into this same error. any ideas?
palmbeach05 said:
hi guys, saw the project you all are working on. i'm one of the guys over on dx working on the kk build/development. i know that the dx and the dx2 are different devices with different configurations, but i'm coming here for a possible lead or inspiration on what i need to do to help with our project. http://forum.xda-developers.com/showthread.php?p=48051920 is the link showing our current attempts.
i stumbled across this thread at a good time i think. the issue we're running into does deal with the hijack-boot.zip.
make: *** No rule to make target `home/davidmcleod/android-cm11.0/out/target/product/shadow/hijack-boot.zip', needed by `/home/davidmcleod/android-cm11.0/out/target/product/shadow/obj/ETC/hijack-boot.zip_intermediates/hijack-boot.zip'. Stop.
we keep on running into this same error. any ideas?
Click to expand...
Click to collapse
How did you get it to work before?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Lrs121 said:
How did you get it to work before?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That would be a good question. Everything appears to be setup the same as GB and ICS, but it doesn't create the zip. We know its a rule thats missing somewhere, its just a matter of tracking down the correct file that should have the rule in it.
Woah. what luck. I just got a nexus 5, and I was wanting to learn the interals of android. Gave my dad my s3 for his droid x2 to dev on.
I guess i will check this thread out every once and a while
Hi there. Not sure if it's the right section. I have a question for you guys.
Let's say that sometimes I need to compile one file.
With make I usually do:
make out/target/product/some/boot.img
Obviously this will not work in the complex hell of makefiles we have in android.
How can I do that?
Also I noticed there are $(hide) prefixes in almost any makefile. Is there an env variable to turn it off (debugging purpose)?
Is there a list of all generic env variables commonly used when compiling android?!
Thanks guys!!!
Sent from my XT1053 using XDA Premium 4 mobile app
If you want to make Settings for example type:
Code:
. build/envsetup.sh
lunch yourdevice-eng
mmm packages/apps/Settings
This will build Settings only, you can also make apps only when you'll use mm instead.
If you don't want to use the debugging build, simply lunch the userdebug target.
eagleeyetom said:
If you want to make Settings for example type:
Code:
. build/envsetup.sh
lunch yourdevice-eng
mmm packages/apps/Settings
This will build Settings only, you can also make apps only when you'll use mm instead.
If you don't want to use the debugging build, simply lunch the userdebug target.
Click to expand...
Click to collapse
Thanks! I'll try and let you know.
If my rom has only the -eng build, how I can manually turn off the debugging stuff and optimize it for speed like the -O3?
DAddYE said:
Thanks! I'll try and let you know.
If my rom has only the -eng build, how I can manually turn off the debugging stuff and optimize it for speed like the -O3?
Click to expand...
Click to collapse
While working on a ROM, I personally always use -eng. For releases, I sometimes compile -userdebug, but only rarely. But if you want to, just re-compile with -userdebug
Optimizing with compiler flags (-O3) is something completely else. Such compiler flags are set within the Makefile(s), and not as a terminal command. But before playing around with compiler flags, I'd suggest you to do some heavy reading before
laufersteppenwolf said:
While working on a ROM, I personally always use -eng. For releases, I sometimes compile -userdebug, but only rarely. But if you want to, just re-compile with -userdebug
Optimizing with compiler flags (-O3) is something completely else. Such compiler flags are set within the Makefile(s), and not as a terminal command. But before playing around with compiler flags, I'd suggest you to do some heavy reading before
Click to expand...
Click to collapse
Thanks for the explanation, I was just wondering why both cyanogen and omni roms compiled by me are slow as hell
Also, I see that before on other roms when you click around sometime appear a red rectangle around the border of the screen... is that a debug thing?
Again thanks!
DAddYE said:
Thanks for the explanation, I was just wondering why both cyanogen and omni roms compiled by me are slow as hell
Also, I see that before on other roms when you click around sometime appear a red rectangle around the border of the screen... is that a debug thing?
Again thanks!
Click to expand...
Click to collapse
hehe, welcome to an old "-eng-bug" when you compile -eng, strictmode somehow goes crazy
you can fix it by adding the following line to your build.prop:
Code:
persist.sys.strictmode.disable=1
laufersteppenwolf said:
hehe, welcome to an old "-eng-bug" when you compile -eng, strictmode somehow goes crazy
you can fix it by adding the following line to your build.prop:
Code:
persist.sys.strictmode.disable=1
Click to expand...
Click to collapse
Awesome! Thanks man!