Hello all,
I am trying to get voice+ working, and I am almost there I believe. Cherry-picking from gerrit gives build errors, so I put the changes in by hand, and made a few more changes I found in the cm11.0 branch for SMS middleware, and got it to build. At first, if I installed the voice+ apk, I was getting permission unavailable: INTERCEPT_SMS, but now i get CANCEL_NOTIFICATIONS. The only reference to that permission I have seen anywhere is in the babel apk, so I'm wondering if it is necessary anymore in 4.4. anyone have any insight?
TIA
Shameless bump
Bumping a thread from a year and a half ago? That doesn't even relate to paranoid Android?
Related
Hello everybody,
I'm an Android app developer for some time, but from some time ago until now I have been tweaking the framework, trying to enhance, customize and maybe correcting bugs, so I'm working on the emulator, but I would like to test it on my device (Atrix).
Since I'm a newbie on this matters and I found plenty of threads and sites/blogs, I got a little confused on what are the steps to be made, specially because I would like to build from source as to have my modifications flashed. I'm aware of the hardware implications for my specific device, so I decided to use a reported working rom source code for my device, but i'm a little lost. I thoutgh to be using Cyanogem but I don't know the specifics.
Since I already have the source code AOSP, I think It would be painful to make it work on my device (drivers, kernel, so on...).
I just want (for now) see my framework modifications on device. Anyone could point me to the right direction?
I thought of using this firmware here.
Thank you all.
Hey Guys,
So I finally decided to learn what all this compiling and building from source is about.. So far I really learned to appreciate the developers on this site.. I started out trying to build AOSP and cherry pick commits, but after the build kept failing now my goal is just straight up AOSP for now..
I followed all different guides to get to the point of building it - it boots up without issue however I have no cell signal - baseband version is unknown.
I am at a lose to what to do. I do have the Google Nexus Binaries, and in the device/lge/mako/full_mako.mk I changed PRODUCT_RESTRICT_VENDOR_FILES := true to false.
I did make clobber to clean out any failed build, and rebuilt. I also can't get a kernel to build but thats a different beast so for now I am just using the stock boot.img.
Any help would be greatly appreciated..
**Edit** Only thing that may be an issue I think I used the preview binaries for nexus 4 - which I guess might be for Android L? Going to try to download the ones for 4.4 and see if that changes anything.
**Edit 2** After changing from the preview binaries to the regular 4.4.4 ones from google, I did make clobber and rebuilt android.. And I have full cell signal
Hello, I'm trying to build an app called Commotion Wireless from its source code - I didn't make this app myself, so it should be a simple case of following the instructions in the README, importing into Eclipse and exporting as a .apk. However, upon attempting to build, there are 3 errors: two saying "isIBSS cannot be resolved or is not a field" and the third with "frequency cannot be resolved or is not a field". The offending pieces of code are here:
github.com/opentechinstitute/commotion-android/blob/cm/src/net/commotionwireless/profiles/Profile.java - lines 201 and 202
github.com/opentechinstitute/commotion-android/blob/cm/src/net/commotionwireless/meshtether/NetworkStateChangeReceiver.java - line 92
Now as many of you know, stock versions of android don't seem to support ad-hoc networks, this is functionality that other custom firmware such as Cyanogenmod adds. As far as I can tell, this app is intended for cyanogenmod (as the devs state in URL1 below). Therefore I think that the definitions of "isIBSS" and "frequency" are not in the stock versions of andriod (URL2 is a patch somebody wrote that adds them), and the root of my problem is that I'm trying to build the app based upon the stock version of android that doesn't understand what "isIBSS" and "frequency" mean. I have never tried to build an android app before so have little experience, but my first instinct was that I needed to install a custom version of the android SDK for Cyanogenmod that would have the needed definitions in - however as far as I can tell, no such thing exists.
Does anyone here have any idea how I may resolve this issue? Your help is much appreciated
URL1: commotionwireless.net/developer/resources/commotion-android/
URL2: thinktube.com/files/android-ibss/patches/frameworks-base-0001-Wifi-Enable-Ad-Hoc-IBSS-network-configuration.patch
Hello everybody,
I'm currently doing some research regarding malware analysis on Android. For that I'm building AOSP images for my Nexus 4. I'm trying to add some modifications to the source code, so that I'm capable of logging all SSL requests unencrypted in a log file, but sadly I'm not successful so far.
Has anyone tried to implement something similar and could give me some hints how to do that? In my last attempt I modified the method "getInputStream()" in the file "libcore/luni/src/main/java/libcore/net/http/HttpsURLConnectionImpl.java". Regarding to a blog post from the Android devs, HttpURLConnection is one of the two available HTTP-Clients and should be used by applications.
Is this the right class for modifications or exists even better classes to intercept requests/responses? Or am I completely wrong with this approach?
Thanks in advance for any help!
I am having trouble finding decent instructions for getting the sources for a standard build for Motorola devices, specifically for athene.
I have built for Freescale products before and it usually involves some combination of repo init and patches, but that doesn't seem to be the case for Motorola.
I know the kernel and other sources are available on Github (https://github.com/MotorolaMobilityLL), but I don't see a manifest repository there. Nor can I find a device repo.
The closest thing to instructions I found was this readme (https://github.com/MotorolaMobilityLLC/readme/blob/master/MMI-MPJ24.139-23.4.txt) (xda wont let me post links, I'm too new a user here).
I am starting to suspect that Motorola is being as lazy as possible and only fulfilling the bare minimum of open source obligations, and thus doesn't provide a device repo, or manifest repo, etc.
Is that the case? I am new to running builds for standard phone manufacturers - are ROM developers around here forced to do legwork filling in what the manufacturers refuse to publish?
Or am I just missing the rest of the instructions from somewhere?
I have the same issue, did you ever manage to successfully complete a build? Thanks.
TheGreatCabbage said:
I have the same issue, did you ever manage to successfully complete a build? Thanks.
Click to expand...
Click to collapse
Nope, my impression of the situation remains the same, though I have not re-investigated. I would like if someone more knowledgeable confirmed though.
It is a shame, as I would really like a "known good" base to work off of and put in root support and remove unnecessary softwares in a legitimate way.
You *can* build LineageOS for athene: (https://wiki.lineageos.org/devices/athene/build)
I ran LineageOS for several months, but eventually switched back to stock. Has some strange issues in regards to texting (seems to only work when making a call).
Thanks for your reply. I've just managed to build Lineage OS for my device, and it seems to work ok.
I was previously using Resurrection Remix OS (which I didn't build, just downloaded a zip) and it worked very well, so if I have any issues with Lineage then I'll try to restore my TWRP backup of RR.
I wish I could use the AOSP codebase directly, though...