I apologize in advance if this has been suggested before, or if it's a completely off the wall idea that will never work.
Has anybody attempted to build for Dream from the morrison source provided by motorola? Could we not just do the edits before building, and add support for the method Dream uses to start wifi? I know it doesn't include all the cool blur stuff, but it does nativly supports those apps. So shouldn't we be able to add them after building?
We have yet to get bluetooth on hero roms, but HTC was never kind enough to provide the source. So we have always been working with prebuilt roms. Android is by nature platform independant, so is it just a matter of nobody wanting to put in the work? Or has motorola changed so much that it would be too challanging to accomplish this?
Related
Hi guys,
this is more a android-related question but I don't know where else to ask...my question is pretty simple though:
Are the graphics (standard wallpaper, standard icons, standard app-drawer button etc.) of the standard google-android (no sense etc.) copyright protected?
Or are they part of the open source project?
THanks a lot guys!
the only parts that should be google exclusive are the images in the google apps, so anything in a cyanogen release should be considered safe (or most anything at least, since a few are technically tmobile). i state cyanogen since he is not allowed to use the proprietary bits so most everything in his rom should be from the AOSP.
thanks...i should have though of that myself.
I need a straight answer as it's possibly the one thing I can't figure out.
For eclair, NCommander fixed camera, but camcorder and video were broken from a straight build from AOSP.
CM later fixed these, but I never quite figured out how. Then everybody else started getting the camera fixed on their roms (by pulling a couple libs, I assume), but I myself couldn't figure out how the heck it was done, where an alternate source was available, or even an explanation of exactly what was broken/how it was fixed, etc. Same went for video playback/hw acceleration.
Now, on froyo, camera is broken again and NCommander's camera won't work either. It's been fixed by other people, but when I ask around, there seems to get a reluctance and I never really get an answer (and don't give me the "you're not asking the right question" line, I'm being pretty straightforward).
I need somebody here who has some knowledge as to why/how camera/hw is not working and how to fix it. I don't need libs. I need to know how to get the thing built from AOSP, why it breaks, and what I should look out for in the future, should it break again.
As far as I can tell, the problem is that the qcomm proprietary parts are outdated (for dream, last were 1.6 and eclair/froyo break compatibility with those libraries). Those libraries have to be linked-to at compile time of other hardware-libs and without the correct library, it won't build right.
What I don't get is: 1. which parts are missing, 2. where are people getting them from, 3. how do you add them to AOSP (other than PRODUCT_COPY_FILES) to get camera and all hw working right (including 3d acceleration).
Or maybe the project aurora community is better able/willing to help...
Bump. Totally interested. If OP already got an answer, please share.
Jubeh sorry I can't help you out I'm not a dev or a chef so I can't really give you any help. But I am interested in how your progress is going with this rom?
I found two sources for hardware files for the msm7k on our phones, including the camera and hw3d driver for dream. Also, building camera for AOSP seems to be fixed now. I'm just waiting from my battery to get here so that I can test. ebay parts from hong kong take forever.
I've searched all over today, but I have only found a couple of threads on the issue, none of which seemed to give a clear answer. I now have my first Android phone (Atrix). I love the customization potential of the platform, but it seems a little choppy at times on the graphical side of things. What I want to know is this: is it possible to create an Android rotation effect, such as the iPhone has when switching between portrait and landscape modes? Can this be achieved with simple root access and development, or would it take a custom kernel? Are there any themes or ROMs which provide this possibilty. I know I can't run a custom kernel on the Atrix, but I'd still like to know, for future referenece. Thanks!
Only thing I've ever heard is that as it's a feature of honeycomb do we may see it added either in honeycomb roms or ported into gingerbread from honeycomb. Obviously we'd need Google to release the code first.
Sent from my DHD
Okay, thanks. That's good to know.
Since the Moto X and other recent Droids are available for root now, I'm wondering: will hackers be able to modify Touchless Control settings? Or is that a closed source part of Android that no one can touch except for Motorola?
Or at least, will we be able to write code that's specifically for the context and voice processors that are unique to the new Motorola phones?
I've never hacked around with Android ROMs but it seems to me that the addition of these processors could mean a playground with a lot of potential to hackers. Wouldn't mind taking a stab at it myself
It likely won't be possible. The best we may get is to at least be able to take the custom touchless binaries and compile them into a custom ROM so that we get all the benefits of stock x8 functions in custom ROMs. But I doubtthat code will be released fforttweaking. Compile the binaries is the most I'd expect which is enough for me, but we may not even get that.
Hi,
We have a scenario where we need to integrate multiple unity builds into single Android project. Currently we are facing issue while integrating multiple unity projects into native android app. So my first question is like whether is this functionality possible ? If yes, please let us know how to proceed on that, or else please provide documentation for the same.
Looking forward to hear from you.