cyanogenmod

Textures not rendering in 2.3.3

纵然是瞬间 提交于 2019-12-02 08:12:57
I ran into somewhat of a stressful issue today while wokring on my game for android and was hoping someone would have some insight. My friend has used cyanogenmod on his Droid incredible to root and install gingerbread 2.3.3. I tried booting up the game on his device and it seems to be running but everything is white. Being as my glClear is black, I'm assuming that this means the bitmaps and/or textures are not loading correctly. I've tried putting my textures in all of the different dpi folders, tried setting the max API level to 8 for froyo, tried setting the platform for the project in the

android源码分析网上随笔记录

自古美人都是妖i 提交于 2019-12-02 07:15:52
百度查“android源码分析工具”时发现有一篇知乎文章: 巨人的肩膀 AOSP项目官方: https://source.android.com/source/index.html 这个一定要先读. 项目介绍, 代码下载, 环境搭建, 刷机方法, Eclipse配置都在这里. 这是一切的基础. Android官方Training: https://developer.android.com/training/index.html 这个其实是给App开发者看的. 但是里面也有不少关于系统机制的介绍, 值得细读. 老罗的Android之旅: http://blog.csdn.net/luoshengyang 此老罗非彼老罗. 罗升阳老师的博客非常有营养, 基本可以作为指引你开始阅读AOSP源码的教程. 你可以按照博客的时间顺序一篇篇挑需要的看.但这个系列的博客有些问题: 早期的博客是基于旧版本的Android; 大量的代码流程追踪. 读文章时你一定要清楚你在看的东西在整个系统处于什么样的位置. Innost的专栏: http://blog.csdn.net/innost 邓凡平老师也是为Android大牛, 博客同样很有营养. 但是不像罗升阳老师的那么系统. 更多的是一些技术点的深入探讨. Android Issues: http://code.google.com/p/android

Profiling android-ndk plain C/C++ executable

坚强是说给别人听的谎言 提交于 2019-12-01 21:23:58
问题 What is the best way to profile plain C/C++ android executables on a rooted android device? android-ndk-profiler seems to support only ndk libraries linked to Java. Any suggestions? Thanks 回答1: I was faced with the same question recently. After looking into several alternatives I decided the best option (the one I made to work, at any rate) was to build Valgrind for Android. This page describes how to build Valgrind for Android. See also my GitHub project for a slightly different build

Profiling android-ndk plain C/C++ executable

有些话、适合烂在心里 提交于 2019-12-01 18:54:47
What is the best way to profile plain C/C++ android executables on a rooted android device? android-ndk-profiler seems to support only ndk libraries linked to Java. Any suggestions? Thanks I was faced with the same question recently. After looking into several alternatives I decided the best option (the one I made to work, at any rate) was to build Valgrind for Android. This page describes how to build Valgrind for Android. See also my GitHub project for a slightly different build procedure, usage notes and prebuilt Android ARMv7 binaries. Android NDK profiler work by GCC compiler trick so

Host-based Card Emulation, any guidance please?

若如初见. 提交于 2019-12-01 12:49:38
I'm new to this field, I got a Nexus S ( CyanogenMod11 = Android Kitkat 4.4.2) And I need to use HCE (Host-Based Card Emulation) mode in order to emulate a contactless card. Any guidance on the steps and the tips I need to follow in order to accomplish this? ( - Do I need to program the simulated Secure Element? put it on cloud? ) P.S: I have to use the new Reader Mode also, because my app is going to be read by another Android NfC-enabled phone and not by an NFC reader. Thank you. Michael Roland Before CyanogenMod 11, CyanogenMod supported its own host-based card emulation functionality. You

CM12 build failed for oneplus one

萝らか妹 提交于 2019-12-01 07:12:31
问题 I am following this wiki http://wiki.cyanogenmod.org/w/Build_for_bacon to build cyanogenmod 12 for oneplus one. Build fails with the following error. brunch bacon including vendor/cm/vendorsetup.sh Looking for dependencies ============================================ PLATFORM_VERSION_CODENAME=REL PLATFORM_VERSION=5.0.2 CM_VERSION=12-20150505-UNOFFICIAL-bacon TARGET_PRODUCT=cm_bacon TARGET_BUILD_VARIANT=userdebug TARGET_BUILD_TYPE=release TARGET_BUILD_APPS= TARGET_ARCH=arm TARGET_ARCH_VARIANT

repo init a particular commit

我的梦境 提交于 2019-12-01 06:52:17
Im building the Cyanogenmod 9 (Android ICS) system for a Nexus S phone (samsung crespo). The problem is that if I do: repo init -u git://github.com/CyanogenMod/android.git -b ics The repo inits to the latest commit of ICS, in which the manifest does not include some device/samsung/ projects I need (specifically https://github.com/CyanogenMod/android_device_samsung_crespo ). How do I repo init to a particular commit? In my case I want the last commit using the google android-4.0.3_r1 branch. Is this one: https://github.com/CyanogenMod/android/commit/5f5da775f570f2995c8ff2db98e6c8b40852911c If I

repo init a particular commit

丶灬走出姿态 提交于 2019-12-01 03:21:49
问题 Im building the Cyanogenmod 9 (Android ICS) system for a Nexus S phone (samsung crespo). The problem is that if I do: repo init -u git://github.com/CyanogenMod/android.git -b ics The repo inits to the latest commit of ICS, in which the manifest does not include some device/samsung/ projects I need (specifically https://github.com/CyanogenMod/android_device_samsung_crespo). How do I repo init to a particular commit? In my case I want the last commit using the google android-4.0.3_r1 branch. Is

Insufficient permissions for device in Android Studio Workspace running in openSUSE 13.2

萝らか妹 提交于 2019-11-29 19:50:14
I have a rooted Motorola Defy+ running a Cyanogenmod v11 custom ROM (nightly build) created by Quarx . Using Android Studio Workspace,(ASW) v.1.1.0, when I try and debug on this device, I get ????????????[null] listed in the Choose Device window, with the Logcat window showing insufficient permissions for device I would really like to use this device and ROM for debugging purposes. When I enter lsusb from the command line I get, Bus 002 Device 002: ID 22b8:431d Motorola PCS This is the correct device id for Motorola units. I have installed 51-android.rules and 71-android.rules in /etc/udev

Building Vanilla AOSP Rom with CM repos?

只谈情不闲聊 提交于 2019-11-29 17:24:40
I'd like to know if I can build a pure Vanilla 6.0 ROM with CyanogenMod repos for my device. Here they are: Device Kernel Should I do some particular edits (excluded adding my device to "lunch")? Thank you :) A quick try could be changing $(call inherit-product, vendor/cm/config/common_full_phone.mk) to $(call inherit-product, build/target/product/full.mk) . This will use the AOSP default PRODUCT_PACKAGES (e.g. UI stuff like SystemUI, Launcher2 or platform relevant stuff like libpowermanager) which are mandatory for a working device (and some more, e.g. phone functionality). You can also use