Build freezes when building CM. - Android Q&A, Help & Troubleshooting

I am building my own version of CM for my device, the LG l90. I am replacing the CM kernel with a kernel from LG stock sources. One problem I have had is the build always freezes at this screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Anyone know what the problem is?
The specs of my VM that I use to build are as follows:
Vmware Player 7.1.2
4 CPU cores
3192mb memory
Ubuntu 14.04
Main virtual drive: 33 GB (Almost full)
Secondary virtual drive: 107 GB (I keep the CM sources here)
Could it be a problem of not enough RAM or disk space? What would have caused this problem?

I notice this whenever I do a clean build. In my case, it takes a while, but the build eventually gets past this and continues. I don't know what's so special about Email.apk, but it always seems to take forever there.

MJPollard said:
I notice this whenever I do a clean build. In my case, it takes a while, but the build eventually gets past this and continues. I don't know what's so special about Email.apk, but it always seems to take forever there.
Click to expand...
Click to collapse
Is there a way to disable building of email.apk?

zowpow said:
Is there a way to disable building of email.apk?
Click to expand...
Click to collapse
I've never seen the need to do that, but I suppose you could remove the appropriate lines from manifest.xml. Look for android_packages_apps_Email and android_packages_apps_UnifiedEmail. Better yet, create a .xml file in .repo/local_manifests (you can give it any name you like, i.e. remove_projects.xml) that contains <remove-project> lines for each of these packages (you generally don't want to modify manifest.xml directly, as that would screw up syncing the repo):
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remove-project name="CyanogenMod/android_packages_apps_Email" />
<remove-project name="CyanogenMod/android_packages_apps_UnifiedEmail" />
</manifest>
Be sure to do a repo sync -f before you rebuild. I don't know what effect removing Email.apk will have, of course -- it should just prevent the email app from being included -- but you can give it a whirl.

Related

[Tool][Win][ICS]Razr Root

I know there is other tools out there, I was bored and decided to write up a tool that runs the root script in a GUI for windows.I just wanted something to do and this is what I came up with.
Special Thanks To:
Regaw - AndroidLib
pedrotorresfilho
kholk
miloj - Exploit binary
First things first. This program runs a commands at startup. It will verify if the device is a razr, it will verify only 1 device is plugged it. It does have minor error checking. It's mainly just to look cool. While it does root again I was bored. This really isnt anything new.
NOTE: To exit the application you click the back button. This will exit the app.
The home button will take you to this thread.
The Menu button i'm not sure what to do.
The Search button i'm not sure what to do. // Will probably set it up for donation link for the guys above.
Also I know the file size is big, lol like i said i did this while being bored its more focused on the look. It uses some extra dlls etc in order to do transparency and listbox images.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[Download Link]
Download Here
+1..
another guide..
thank for sharing...
Link is online now.
Fixed a minor bug where software would crash during restart of device.
Nice tool, thanks :good:
nice tool...
downloading..
wowww.. interactive tools for root..
downloading now..
and I will tested at ICS Asia Retail..
report ASAP..
Hi!
Why is the adb process persistent? After running this aplication we cannot delete de folder or disable the adb process in background.
--Edit--
I may have found an answer: You've used a 32bit library (MS Windows (GUI) Intel 80386 32-bit). You should add a statment in OP it's for 32bit versions of windows.
Thanks
32Bit should run fine on 64bit machines, just need to place adb-killserver on shut down and that will stop adb. I will do that today.

[Q] Got 1271 errors trying to build (from source) keyguard.apk in eclipse

Hi,
i would like to build an .apk from source with eclipse, but when i port the source project of "keyguard", i've got so many errors (1271) so i can't build it !
Anyone know what can i do without correct all errors ? :/
Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thank you in advance.
After searching a bit I found the following topic: hxxp://stackoverflow.com/questions/17487777/using-internal-android-classes (can't post clickable links yet).
From your screenshot it looks like you're trying to use "LockPatternUtils" which is part of "internal android classes".
ArcaneHammer said:
After searching a bit I found the following topic: hxxp://stackoverflow.com/questions/17487777/using-internal-android-classes (can't post clickable links yet).
From your screenshot it looks like you're trying to use "LockPatternUtils" which is part of "internal android classes".
Click to expand...
Click to collapse
So what can i do ? :/
Thank you for your answer !
NOTICE: I can upload the keyguard folder if you want more informations
Could you share the project you're trying to compile, the official website if it has one? Please keep in mind that while I'm a developer I'm by no means an expert on Android. I'll give it shot but it's probably not going to do much good.
ArcaneHammer said:
Could you share the project you're trying to compile, the official website if it has one? Please keep in mind that while I'm a developer I'm by no means an expert on Android. I'll give it shot but it's probably not going to do much good.
Click to expand...
Click to collapse
Link with Keyguard (extract it)(I just changed an opacity value compared to the original one in KeyguardViewManager.jar) :
http://www.mediafire.com/download/9h1jo9i9b545zdl/keyguard.zip
AOSB Page:
http://probam.net/
AOSB Github:
https://github.com/AOSB/
Source where i downloaded Keyguard (to download it, i had to download all framework source):
https://github.com/AOSB/android_frameworks_base/tree/kitkat/packages/Keyguard
Thank you for yoru help !
Apparently there is a thread about this project from the developer: hxxp://forum.xda-developers.com/showthread.php?t=2377129
Given the Android.mk in the code tree I think you may require the NDK. Here is a tutorial for how to set this up: hxxp://mindtherobot.com/blog/452/android-beginners-ndk-setup-step-by-step/
I've not done any NDK development, so this goes way beyond my skillset.

Self compiled: Help to get rid with a Bootloop (logcat included)...

Hi guys, finally a was able to get a logcat from my device:
https://forum.xda-developers.com/chef-central/android/starting-adb-boot-process-debugging-t3559980
Righ now the device boots into optimizing apps, then gets into a bootloop when "starting apps" appears, just reboot.
Directory with all the files (dmesg, logcat, tombstone and ndk-atack debug): https://drive.google.com/open?id=0ByjBTzGuQ9FIaWJ4RjBkZ1RWSDQ
Thanks alot for your time!
Nobody? As far i google it probably is zygote dying and killing all the child process....
Tombstone added. This is when the system bootloop:
Code:
Abort message: 'frameworks/av/media/libmedia/MediaProfiles.cpp:326 CHECK(quality != -1) failed.'
I found this: https://forum.xda-developers.com/showthread.php?t=2589516
I try with a similar solution for my device (Snadragon 805) i try media_profiles.xml and media_codecs.xml from shamu and quark (twin devices) but with the same result.
Also i try with stock libmedia.so and libmedia_jni.so in vendor tree, but it bootloop in bootanimation...i'm close bun any help will be appreciated!
EDIT: I jut solve this bootloop removing the 4k profile...
Added media_profiles and media_codecs
Finally i get rid of the bootloop related to media_profiles.xml, i just delete the 4k profile, seems to work on stock but not on CM.
I'm still on a bootloop but this is more nasty...i have no idea why this happen and i cant understand the logs at all.
I just post dmesg, logcat, tombstone and ndk-stack debuged tombstone....any hel will be appreciated!
As far i see the device crash here:
Code:
/data/dalvik-cache/arm/[email protected]@[email protected] (offset 0x80b000)
I don't know but probably seems to be related with dex2oat? with jar files....
I think i put some propietares odexed jar files in a deodexed rom....but i don't know why services and frameork crash...
I was playing around with some ART config https://source.android.com/devices/tech/dalvik/configure.html
But no luck, probably the crash isn't related to ART at all...anyone see something in the logs that can help me to start to search a solution?
Thanks in advance
Finally i found the reason of the bootloop. Looking at the tombstone i found the string "antutu". Doing a "grep" in CM sources i found it's related to "Perfomance Manager Service" here "vendor/cm/overlay/common/vendor/cmsdk/cm/res/res/values/config.xml". So disabling the service in "/vendor/cmsdk/cm/res/res/values/config.xml" (with an overlay) i got my rom booting.
Code:
<!-- <item>org.cyanogenmod.platform.internal.PerformanceManagerService</item> -->
But this come with nasty consecuenses, because mpdecision goes mad and only activate one core of four....So, digging some more i found out that probably only need to disable "Performance Profiles" in source, but i have no idea how to do it...a little step, btw...
This is what i need to disable:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Android Wear apps to work with Android Read with APK Easy Tool

I guess a lot are aware of the thread http://roundandroidwatches.pr which shows how to port Android Wear apps to Android in order to run them on the Amazfit pace watch. The above mentioned threads describes the principle solution on a mobile with the help of an App "APK Editor" which works only with the paid version.
Therefore I was looking for a free and easy GUI controlled solution running on WIndows which serves the same issue which I found with "APK Easy Tool v.1.41".
1) you have to ensure that JDK and JAVA are refences by your Windows PATH variable and that they run on the same version. I am using java build 1.80.. and javac build 1.8.0....
2) You install APK Easy Tool v.1.41
after start-up you need to do the following setting for APK signing:
https://ibb.co/he7Gmb
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3) Select the downloaded APK, decompile it and modify open the APK directory
https://ibb.co/hdXcsG
4) Open the "Decompiled APK directory", step on the first level of app and open the *Manifest.xml file in a XML editor (e.g. Notepad++) and modify the data according to http://roundandroidwatches.pr
change min sdk version to, e.g.:
Code:
<uses-sdk android:minSdkVersion="7" android:targetSdkVersion="24" />
change screen resolution to:
Code:
<application android:theme="@android:style/Theme.NoTitleBar.Fullscreen" ...
remove if available hardware line, e.g. :
Code:
<uses-feature android:name"android.hardware.type.watch" />
5) Click the Compile button the APP get assigned too
6) Transfer it to the watch. I used Apk Installer 3.5 on Windows to do do on a rounded up GUI solution (of course one can use ADB shell too)
PS: I have tried this with Invaders Android Wear APP and the entire process worked with any issues and the App is running perfectly on the watch.
i will give it a try later today
Here you can find some Wear Apps which have been already converted and can be used on Amazfit.
http://amazfitcentral.com/2017/08/31/free-apps-amazfit-pace/
In addition I ported a flashlight App too. It worked but the light is not very bright: https://www.apkmirror.com/apk/googl...elease/flashlight-7-1-1-android-apk-download/

How to fix app crashing when using the showFloatWindow API on Huawei devices running EMUI before version 9.1

A number of reports were received about crashes when the showFloatWindow API is called on devices running older versions of EMUI. Let's take a look at this crash today and how we can fix the issue.
Start by integrating version 6.1.0.301 of the Game Service SDK into a project and successfully implemented the floating window function.
Then, when testing the game on devices running a version of EMUI earlier than 9.1, the game crashed when showFloatWindow API is called. The crash logs are as follows.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The error logs suggested that the issue was caused by missing layout files during layout implementation. This error suggests that c_buoycircle_window_small.xml, c_buoycircle_hide_notice.xml, and c_buoycircle_hide_guide_dialog.xml layout files were not found in this project. However, they had been saved under the layout folder as displayed in the following figure.
The next possible issue could have been that the layout files were obfuscated. So, let's check the build file to be sure:
As you can see minifyEnabled was set to true, indicating that the obfuscation function was enabled. This was also the case for shrinkResources, which meant that resource files were excluded during package creation.
One option of course would be to simply disable the shrinking of resources. By commenting out this line the game would run fine and the API call wouldn’t crash, however, the resource files are no longer compressed and will take up much more space.
To compress the resources, you can create an XML file that contains the resources tag in the project or use the keep.xml file in the res/raw directory, and specify the resources to be reserved in the tools:keep attribute as follows:
XML:
<?xml version="1.0" encoding="utf-8"?>
<resources xmlns:tools="http://schemas.android.com/tools"
tools:keep="@layout/c_buoycircle*" />
This solution allows the floating window function to work and is able to compress the resource files.
Note: If you have integrated the Game Service SDK, Huawei suggests that you add the following resources and configure the following obfuscation scripts.
@drawable/c_buoycircle*
@drawable/hms_game*
@Layout/c_buoycircle*
@Layout/hms_game*
@StRiNgS/hms_game*
@StRiNgS/c_buoycircle*
nice article

Categories

Resources