Hello everyone,
I'm trying to build unofficial los15.1 for my device but I get an error that can be resolved by 'setting ALLOW_MISSING_DEPENDENCIES=TRUE' in enviroment but I don't know how how and where>
Aside from the question if I want to do this, I just want to see how far I come if I do.
Who nows where I have to put this line to solve the issue?
Related
Hi, so I'm a student learning Android app development and trying to modify the AOSP calendar to fit my needs so I downloaded the source code from git and made a project with 2.2 FroYo as the basis through Eclipse with ADT and all but I ran into a problem. So I run into:
android.provider.Calendar cannot be resolved into a variable
I did some research and found that the SDK apparently does not have the calendar code nor the database which is why I am running into these issues. So I learned from here jimblackler[dot]net/blog/?p=151 all that. He does have a solution except I have no idea what he is saying. He posted a bunch of code but I have no idea where that code is supposed to go in and I dont understand what he is trying to do with "content://calendar/calendars"
So I just decided to ignore the errors and obviously I couldn't compile it through eclipse so I made an unsigned apk and tried to install it unto the Emulator via ADB but as an unsigned apk it would not let me install it I tried to sign it by going through google's developer site but I am at lost again. I'm a noob to these things unfortunately..
I was wondering if anybody could help me out and point me in a good direction, I would be eternally grateful. Thanks.
P.S. sorry if I was being vague about the google's developer site and source code site but as a newbie I can't post links properly
My Nexus has problems connecting over bluetooth to my Car (BMW). I've found a lot of references to similair problems, and also a hint which suggests a change that could solve the problem. The hint can be found on the cyanogem forum in posting 77834, "bluetooth-connection-drops-kar-kit-bmw" (I cannot post links here).
I am running stock KitKat, and for the moment want to keep it that way. So, I decided to try the same patch on KitKat. I've managed to setup a development image in a VM, but keep running into problems compiling - my machine lacks resources (diskspace) to complete a complete build. I do not need a complete build; I need just 1 file, bluetooth.default.so, compiled. My development skills are VERY rusty, and I cannot find out how to build only this file.
I've applied the patch to external/bluetooth/bluedroid/bta/ag/bta_ag_sdp.c, run a make on the Makefile here etc - but, still no luck. The most frustrating bit is that I'm sure this is trivial, but it has been such a long time since I did any development work that I cannot seem to find a way to compile.
Can someone help me out here with hints on how to build the .so? I need bluetoot.default.so, build from the files in the external/.../ag directory, to be situated in system/lib/hw on the android system.
Hi Everybody,
I want to ask for some informations what is need to do to build SlimRom for a new device. I found a lot of informations about CM, but nothing is really in a way that I really know what I have to do at the end. So is there a Howto, which describes it a little bit more in detail? A lot of howtos was found which describe to get a build-system, and to generate something for a know device. But everybody then describes only: you have to get the vendor files, made your Board-config but only on a very high level.
What I did:
- set up a building-server on ubuntu.
- get Slim-Sources branch JB4.3, and build the version for galaxysmtd to be sure that the buildprocess is ok.
- get "Nonreallyfree"-Opensources from Samsung for my I8200, and try to put them in the right places, and try to implement all needed files in the device/samsung/i8200 folder.
Up to now I think I have everything in place more or less, but the system told me that there is no rule for make 'bacon', but lunch seems to work right with setting the variables...
Up to now I did not used the blobs of the devices. The question is, if that is needed if I have the sources from open Samsung?
I know, jb43 is not the newest, but I start here, because up to now the sources are based on that level, and the kernel have no selinux implemented... If this start point will work, then I will try to go ahead with higher versions... end goal will be Slimkat...
Any help is very much appreciated!!
BR
SP
Hello everyone.
Today I tried to compile my own CM13 build from source, but it just won't go through it.
I followed the guide http://wiki.cyanogenmod.org/w/Build_for_hammerhead completely, except I substituted "cm12.1" for "cm13.0" while initialising the source code. I've got all the required libs and packages, but it always fails at some random point. I don't think any warnings that the compiler is giving are relevant, since it always fails at a different point every time I run it. Any ideas?
Thanks for your replies already!
You could start by showing us some of those errors. Keep in mind that you will need to pass '-j1' to make to get the exact errors.
Dear S7 developers,
I know that a fix for the echo issue cannot be released here in the forums for others to download because of copyright issues, but I could potentially build the ROM myself and pull in the right files to fix the issue or is there anything blocking me from doing so? If so, has anyone done this before and can give some rough directions? A quick search didn't yield anything related to this in the forums. If this is not solved, I have to look into it myself but I'd rather keep working on my Note 10.1.
Maybe we can even go further. There are other software related projects that have to deal with copyright issues, too. They usually solve this by having a manual step for the user who is installing something so that they don't have to provide the necessary copyrighted material. Can't this be done in this case, too? Can't we prepare a ROM and have one/multiple files that need to be adb pulled by the user from their phone with the original Samsung ROM still running and then pushed back after flashing a custom ROM?
If it would be that easy, someone would probably already have solved this I guess. Still looking forward for some answers here.
Did you solve?