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!
Related
Hey,
I've just recently started Android development and I'm keen to learn as much as I can about the whole system, not just about SDK app development. As such I'm interested in attempting to build my own ROM completely from scratch. I've downloaded the Android Source (and Galaxy S source) and would like to try my luck.
First I've been mucking around creating custom ROMs with the emulator, moving apps from the Galaxy S ROM I dumped from my device onto the stock emulator ROM and testing things out.
Anyway I'm at the point where I'm wondering if it's possible to flash the stock emulator ROM onto a Galaxy S phone? I know the Galaxy S source includes a lot of device specific stuff however I'm not interested in getting the camera, bluetooth or anything hardware specific working just yet.
If I flash a ROM with a stock kernel, drivers etc. onto my phone will it work? Has anyone done this? Will it just brick my phone?
Any help would be appreciated.
Cheers,
Ben
Anyone?
Also, I know people have flashed AOSP ROMs on other phones, does anyone know if they required modifications or whether they are in fact stock ROMs?
nje, can't work. why?
1) different bootloaders
2) different partition layout
3) different (kernel)drivers
4) different vendor setup
etc.
it is possible to flash the emulator image onto a dev device (dream/sapphire) but even then a lot will not work properly!
if you want to learn about the android architecture you should start with building a kernel (there is already a thread about that here) and playing around with stuff like the (file)system and utilities...
Thanks jodue.
Yeah my long term intentions were definitely to build the Galaxy S kernel and any necessary libraries and drivers specifically necessary for the apps I decide to include in a custom ROM.
I was hoping that I'd be able to start out by tweaking a minimalistic/generic ROM (the AOSP default ROM) on my Galaxy S. However, as you've pointed out I'll have to start out with the kernel and all the device specific stuff first.
I've got quite a bit of information on building an Android/linux kernel both from the thread you mentioned and also the official AOSP page. However information on putting together a complete working ROM seems a bit sparse. Does anyone know where I can find some information on the topic?
I'm also curious to learn about the list of things jodue mentioned i.e. Android bootloaders, partition layouts and drivers (generic and Galaxy S specific). I assume detailed information about particular devices and drivers probably isn't available but if anyone even knows where I can learn detailed information about default AOSP ROMs I'd be extremely interested know.
hi!
I'm trying to implement custom brushs in my application (ARTags) and I'm stuck with MaskFilter.
I didn't manage to find any doc on it so I just downloaded android source to check how BlurMaskFilter and EmbossMaskFilter are created.
Since I'm really not comfortable with the NDK yet, I'm wondering if anyone already managed to implement a custom MaskFilter.
If not, I'm not sure which path to chose between trying to understand the source and use the NDK or try to implement the draw part of my application entirely by myself.
Thanks for your help
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.
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,
Last week, I posted a post about creating a custom flashable file for Odin. Link
As there was no response on the matter as to how to create this file, we are now taking a new approach at my company. We are looking for someone, who would be interested in assisting us towards creating a tool/file/platform (whichever as preferred by the developer), so as to assist us in the mass deployment we face down the road when our project goes live . We are looking for the most efficient and lean way of deploying the phones (a type of "plug-and-play" if possible , so flashing the phone directly out of the box would be ideal!), and basically all configuration and set up is done by us, and the client should just needs to receive the phone before usage
The configuration and set up consists in large by:
- A rooted phone without bloatware from Samsung (includes disabling all Samsung software not essential to run the core phone systems and sensors)
- Android 5.0 or later
- A custom recovery (if possible, for on-site and in-house troubleshooting and handling)
- Installation of our own app
- Custom edit of system files
Payment and time span are discussable when details are discussed and final decisions on the project reached
Thank you for your time, and we hope that someone can help us :fingers-crossed: !
gardium said:
Hello,
Last week, I posted a post about creating a custom flashable file for Odin. Link
As there was no response on the matter as to how to create this file, we are now taking a new approach at my company. We are looking for someone, who would be interested in assisting us towards creating a tool/file/platform (whichever as preferred by the developer), so as to assist us in the mass deployment we face down the road when our project goes live . We are looking for the most efficient and lean way of deploying the phones (a type of "plug-and-play" if possible , so flashing the phone directly out of the box would be ideal!), and basically all configuration and set up is done by us, and the client should just needs to receive the phone before usage
The configuration and set up consists in large by:
- A rooted phone without bloatware from Samsung (includes disabling all Samsung software not essential to run the core phone systems and sensors)
- Android 5.0 or later
- A custom recovery (if possible, for on-site and in-house troubleshooting and handling)
- Installation of our own app
- Custom edit of system files
Payment and time span are discussable when details are discussed and final decisions on the project reached
Thank you for your time, and we hope that someone can help us :fingers-crossed: !
Click to expand...
Click to collapse
Meh?