Develop Bugs

Android open source available.

Anyone intend to create a build for the dash if possible?
http://source.android.com/posts/opensource

I will look into this, hopefully some more people will be willing to help out...

Dang this is harder then I thought but I think it could be done...

No one has even gotten android to run on anything but a dream that i know of, and the source has been out quite a while. Our project just getting linux running on a dash is proving to be quite a lot of work. Maybe once we get linux running we can move to android. Also visit #htc-linux on irc server freenode to see current progress on porting android to other devices.

BruteSource said:
No one has even gotten android to run on anything but a dream that i know of, and the source has been out quite a while. Our project just getting linux running on a dash is proving to be quite a lot of work. Maybe once we get linux running we can move to android. Also visit #htc-linux on irc server freenode to see current progress on porting android to other devices.
Click to expand...
Click to collapse
Thanks for the information, but I truly believe it could be done because what would prevent android from being installed on a dash...
Also, no one thought linux would get on the dash; however, it is possible now... thanks for the developers...

jdoggraz said:
Thanks for the information, but I truly believe it could be done because what would prevent android from being installed on a dash...
Also, no one thought linux would get on the dash; however, it is possible now... thanks for the developers...
Click to expand...
Click to collapse
Okay your misunderstanding a few things. First of all android is just a different distro of linux. To get it to work on the exclalibur we need to be able to boot a kernel and that kernel needs to work with all of our hardware. Which is what we are working on with the linwizard excalibur project. Once we get it working with all of our hardware we can patch the android kernel with all of our work then use the android userspace (android.bin) But untill we have working drivers for the excalibur in linux its not possible to boot and use android or any linux fully... understand?

Yah I understand what your are saying...

[DEV][DEV-ONLY] Honeycomb Progress

[This is not the place to say "this is awesome" or "thanks!"]
[DEVS ONLY]
I want to start this thread to keep up the progress on the port.
the bad news is that the SDK is incomplete for now, so (like other devices)
we will have to write our own code for the OS, the nook community
has done a wonderful job writing their own libraries and stuffs, so we will have to do the same.
Instead of pursuing different goals, let's focus on one thing at a time.
since GSM and CDMA versions are already out, it seems we suffer the same bugs, so for now let's unite strength and knowledge to overcome these.
I propose that the first goal to fix is the SurfaceFlinger, so we could at least see the apps, the buttons and the notifications.
it is currently throwing this:
04-06 22:01:35.495: ERROR/Surface(2960): dequeueBuffer failed (Out of memory)
this could lead us that it might coudln't start because of some malloc malfunction or something.
also that pvrsrvinit bugs me a lot.
update:
8/APR/2011
since DiP7 could fix SurfaceFlinger and other things using a different build from the GSM kernel, we have to dig deeper
======================================
CURRENT GOAL
Rebuild Kernel
======================================​
Current approaches:
*none
Post any finding, guessing or anything, and please, please don't be afraid to ask anything you have a doubt, as a Dev you should not know everything, so we can help us each other
------------------------------------------
Google Easter egg:
while searching some info about the android.mk file , I put it on the chrome bar to search for that term, but instead I went to
http://android.mk
an easter egg web page from google lol

******TOOLS*********
How to send text and Keystrokes via ADB
http://bradchow.blogspot.com/2011/02/send-intent-and-key-event-by-adb.html
use DroidExplorer to easily access your device from your computer and makes changes from it
http://de.codeplex.com/
The Android Boot Process
http://www.androidenea.com/2009/06/android-boot-process-from-power-on.html
---Kernel Tools----
CPU Datasheet
http://forum.xda-developers.com/showthread.php?t=745877
Samsung GIT
http://android.git.kernel.org/?p=kernel/samsung.git;a=summary
PowerVR SDK
http://www.imgtec.com/powervr/insider/powervr-sdk.asp
Source code of samsung firmwares(keep and eye on this)
http://opensource.samsung.com/
Asus pad honeycomb Kernel Source
http://forum.xda-developers.com/showthread.php?t=1026528

ellokomen said:
======================================
CURRENT GOAL
Find why SurfaceFlinger is not working
======================================​
Click to expand...
Click to collapse
Mmmk.. Let me tell you a story.
A long time ago in a galaxy far away... No, that will take too long. In a nutshell, one third of the answer is here, another third is here and the rest is here. I'm not trying to be intentionally vague, I just haven't figured out how these three fit together yet.
Of course, there could also be some bit of code that I missed... some telling line in a debug log that I overlooked or some driver or library that I could have decompiled to sift through its juicy secrets. There could easily be a fix that would take seconds to add and make the whole thing fall in line...
Or we might have to work it from the ground up.
Either way it will happen. It's just a matter of whether it will happen next week, or next month.
(Watch it be a misplaced semi-colon, or a bad symlink... that's how these things go.)

updated approaches and new tools have been added

spacemoose1 said:
Mmmk.. Let me tell you a story.
A long time ago in a galaxy far away... No, that will take too long. In a nutshell, one third of the answer is here, another third is here and the rest is here. I'm not trying to be intentionally vague, I just haven't figured out how these three fit together yet.
Of course, there could also be some bit of code that I missed... some telling line in a debug log that I overlooked or some driver or library that I could have decompiled to sift through its juicy secrets. There could easily be a fix that would take seconds to add and make the whole thing fall in line...
Or we might have to work it from the ground up.
Either way it will happen. It's just a matter of whether it will happen next week, or next month.
(Watch it be a misplaced semi-colon, or a bad symlink... that's how these things go.)
Click to expand...
Click to collapse
The kernel source that you have linked to is 2.6.35.7 for the Nexus S gingerbread and is not fully maintained by samsung but rather by google.
However I do not think you are wrong that there is a problem somewhere in the kernel. The kernel that has been released for the galaxy tab is a mess of horrid code, I have had to re-write parts of kernel drivers just to get them to work under linux, I would not be surprised if similar patches are needed for honeycomb

lilstevie said:
The kernel source that you have linked to is 2.6.35.7 for the Nexus S gingerbread and is not fully maintained by samsung but rather by google.
However I do not think you are wrong that there is a problem somewhere in the kernel. The kernel that has been released for the galaxy tab is a mess of horrid code, I have had to re-write parts of kernel drivers just to get them to work under linux, I would not be surprised if similar patches are needed for honeycomb
Click to expand...
Click to collapse
you mean that you made a port of a Linux Distro into the tab?

ellokomen said:
you mean that you made a port of a Linux Distro into the tab?
Click to expand...
Click to collapse
yes click here for the thread on the port of ubuntu

Current kernel source
Do you guys have another link to the current spacemoose kernel source? The download link seems to be corrupted and won't untar. I want to get in on the fun

noobporter said:
Do you guys have another link to the current spacemoose kernel source? The download link seems to be corrupted and won't untar. I want to get in on the fun
Click to expand...
Click to collapse
here it is, bear in mind that this is for CDMA devices

Unfortunatey, we have 4 other honeycomb threads.
Not trying to be rude but spacemoose updates us in the cdma forums AND we have russian rom updates in the gsm forums.
I really dislike the idea of this thread, there is enough clutter amongst the other threads. Do we really need one more place to browse..
The first posts in the roms thread are kept updated by devs.. Is this not enough??

daml said:
Unfortunatey, we have 4 other honeycomb threads.
Not trying to be rude but spacemoose updates us in the cdma forums AND we have russian rom updates in the gsm forums.
I really dislike the idea of this thread, there is enough clutter amongst the other threads. Do we really need one more place to browse..
The first posts in the roms thread are kept updated by devs.. Is this not enough??
Click to expand...
Click to collapse
yeah but we need a place for the other devs to share their milestones, here is a place for technical discussion amongst us, to share the knowledge etc...
the other threads are flooded from non devs messages, so it´s kind of difficult to read 14 pages of information when the 80% is people complaining not making it boot

lilstevie said:
The kernel source that you have linked to is 2.6.35.7 for the Nexus S gingerbread and is not fully maintained by samsung but rather by google.
Click to expand...
Click to collapse
Yes, and it contains some support for our device (s5pc110), and some more that can be added (pvr) and the architecture necessary to fully support HC without patching the build itself. If we work only towards patching the system build to communicate with the hardware, we won't be able to run AOSP hc versions when the source drops without going through the same painstaking process of hacking the system to function (while creating numerous faults causing FCs in the process). If we build a new kernel, we can get the hardware to communicate in the way future android versions want it to and we can then do what we want with ease.

noobporter said:
Do you guys have another link to the current spacemoose kernel source? The download link seems to be corrupted and won't untar. I want to get in on the fun
Click to expand...
Click to collapse
D'oh! Nobody told me, LOL... I'll get another copy up.

spacemoose1 said:
D'oh! Nobody told me, LOL... I'll get another copy up.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1026528
hey spacemoose! the first portion of honeycomb source... The kernel source of the Asus EEE Pad Transformer... maybe it helps you with a few kernel issues, even if it's for another device... It's honeycomb!

Flokey said:
http://forum.xda-developers.com/showthread.php?t=1026528
hey spacemoose! the first portion of honeycomb source... The kernel source of the Asus EEE Pad Transformer... maybe it helps you with a few kernel issues, even if it's for another device... It's honeycomb!
Click to expand...
Click to collapse
Digging through it now.

spacemoose1 said:
Yes, and it contains some support for our device (s5pc110), and some more that can be added (pvr) and the architecture necessary to fully support HC without patching the build itself. If we work only towards patching the system build to communicate with the hardware, we won't be able to run AOSP hc versions when the source drops without going through the same painstaking process of hacking the system to function (while creating numerous faults causing FCs in the process). If we build a new kernel, we can get the hardware to communicate in the way future android versions want it to and we can then do what we want with ease.
Click to expand...
Click to collapse
Not enough really, PVR kernel module sources have been released from samsung for our device, and is available in update1 zip.
The kernel panics and we have no framebuffer from the nexus s, believe me that is the kernel I want to be running for my project, it is cleaner nicer and things are implemented overall better. unless you know of a solution for kernel debuging over usb

lilstevie said:
Not enough really, PVR kernel module sources have been released from samsung for our device, and is available in update1 zip.
The kernel panics and we have no framebuffer from the nexus s, believe me that is the kernel I want to be running for my project, it is cleaner nicer and things are implemented overall better. unless you know of a solution for kernel debuging over usb
Click to expand...
Click to collapse
Kernel debugging over USB = adb shell cat /proc/kmsg
You can make any kernel work for any device as long as you add the **** it needs. Just takes time. Working on it now.

Goal and tools updated*

spacemoose1 said:
Kernel debugging over USB = adb shell cat /proc/kmsg
You can make any kernel work for any device as long as you add the **** it needs. Just takes time. Working on it now.
Click to expand...
Click to collapse
You don't know what a kernel panic is do you?

lilstevie said:
You don't know what a kernel panic is do you?
Click to expand...
Click to collapse
I thought that linux throws a dump log when it makes a kernel panic specifying the memory address and the cause of crash

[Q] Linux Exploits on Android

Right before it was closed, twiztid99 posted a link to a Linux exploit in the Gingerbread root collaboration thread. Is it possible that this Linux exploit could be run in native code to achieve root in Android 2.3.3 on the EVO? It claims that it works for all kernels older than 3.0. No one else has mentioned this that I can see. I apologize if anyone thinks this belongs in the Q&A or general thread, but only developers are going to know the answer.
Linux Exploit Link:
http://www.exploit-db.com/exploits/17391/
Original Post
I would consider myself a programmer, but I know very little about Android, or OS programming in general. Let me know what you think. I'm assuming most Linux exploits would not be applicable to Android because they make use of libraries or applications that Android does not have, but again, thoughts?

near as i can tell, they stopped using that specific type of linux architecture (dec alpha) in the early 2000's: http://en.wikipedia.org/wiki/DEC_Alpha
edit: this probably should be in a different forum, and maybe change the title so ppl don't think u have some type of new root method or something

bender beerman said:
near as i can tell, they stopped using that specific type of linux architecture (dec alpha) in the early 2000's: http://en.wikipedia.org/wiki/DEC_Alpha
edit: this probably should be in a different forum, and maybe change the title so ppl don't think u have some type of new root method or something
Click to expand...
Click to collapse
Thanks. I didn't realize that was an architecture. I thought it was just the name of the exploit :/. I'm going to move the thread to Q&A.

How do I start developing ROMs?

I've tried out almost every ROM I could find for the VZW Galaxy Nexus. They all have their own pros, but none of them were really perfect for me.
I already know Java, so I know that should help me a lot. But I do have some general questions.
My main questions is, do I compile from source? Or do I use something like JRO03L? What exactly is JRO03L? I noticed a lot of ROMs were based off either AOSP or JRO03L, or some other ROM.
When people say their ROM is based of AOSP, does that mean they edited the source code directly?
What about drivers and stuff? Do phones even have those? How do I get them for my phone?
What percentage of ROM editing is done through source code modifying and what percentage is through Cooking?
Sorry for all the questions, I'm just kinda confused.

jtvd78 said:
I've tried out almost every ROM I could find for the VZW Galaxy Nexus. They all have their own pros, but none of them were really perfect for me.
I already know Java, so I know that should help me a lot. But I do have some general questions.
My main questions is, do I compile from source? Or do I use something like JRO03L? What exactly is JRO03L? I noticed a lot of ROMs were based off either AOSP or JRO03L, or some other ROM.
When people say their ROM is based of AOSP, does that mean they edited the source code directly?
What about drivers and stuff? Do phones even have those? How do I get them for my phone?
What percentage of ROM editing is done through source code modifying and what percentage is through Cooking?
Sorry for all the questions, I'm just kinda confused.
Click to expand...
Click to collapse
compile from source needs linux (mac osx only builds master branch);
aosp = android open source project
JRO03L, JRO03R: release tags. they mark a certain landmark in android development, normally leads to/are (pratically) the same as ota's.
yes, aosp-based roms edit source then build. why would we cook when we can build? makes no sense on a aosp supported device like ours.
on linux, just install android-sdk (includes fastboot and adb) and add it to your $PATH, and create udev rules for android devices (most distros provide this as a package). no need for drivers on linux.
http://forum.xda-developers.com/showthread.php?t=1386615
http://source.android.com/source/initializing.html
sent from my i9250

bk201doesntexist said:
compile from source needs linux (mac osx only builds master branch);
aosp = android open source project
JRO03L, JRO03R: release tags. they mark a certain landmark in android development, normally leads to/are (pratically) the same as ota's.
yes, aosp-based roms edit source then build. why would we cook when we can build? makes no sense on a aosp supported device like ours.
on linux, just install android-sdk (includes fastboot and adb) and add it to your $PATH, and create udev rules for android devices (most distros provide this as a package). no need for drivers on linux.
http://forum.xda-developers.com/showthread.php?t=1386615
http://source.android.com/source/initializing.html
sent from my i9250
Click to expand...
Click to collapse
Thanks for the links
And when I mentioned drivers, I meant for the phone hardware. Like, does android just magically work on all phones? or do some phones need something extra to work with AOSP?
Now, after I set up Ubuntu with the guides above, are there any guides to the basics of source editing? Like what do I need to do to install busybox? root android? theme?
I googled on how android 'worked' , so i can get a better understanding on how it operates, but all the results were pretty vague.

jtvd78 said:
Thanks for the links
And when I mentioned drivers, I meant for the phone hardware. Like, does android just magically work on all phones? or do some phones need something extra to work with AOSP?
Now, after I set up Ubuntu with the guides above, are there any guides to the basics of source editing? Like what do I need to do to install busybox? root android? theme?
I googled on how android 'worked' , so i can get a better understanding on how it operates, but all the results were pretty vague.
Click to expand...
Click to collapse
you need to use the right words in google to find what you need. start here, look under getting started http://source.android.com/source/index.html

simms22 said:
you need to use the right words in google to find what you need. start here, look under getting started http://source.android.com/source/index.html
Click to expand...
Click to collapse
Part of the questions you're asking OP, can be solved with information available on that link simms22 and I posted.
jtvd78 said:
Thanks for the links
And when I mentioned drivers, I meant for the phone hardware. Like, does android just magically work on all phones? or do some phones need something extra to work with AOSP?
Click to expand...
Click to collapse
obviously not, that's why i said "aosp-supported devices". devices that aren't aosp supported, need the same things we need, except in their case there's the matter of proprietary frameworks and drivers (called binaries), which we have available almost from the start.
jtvd78 said:
Now, after I set up Ubuntu with the guides above, are there any guides to the basics of source editing? Like what do I need to do to install busybox? root android? theme?
Click to expand...
Click to collapse
sure, guides @github or at any other repo. there's no better guide than being able to read source code and how the masters do it.
jtvd78 said:
I googled on how android 'worked' , so i can get a better understanding on how it operates, but all the results were pretty vague.
Click to expand...
Click to collapse
@source.android.com.
tip: you'll need to learn how to git. there's plenty of tutorials around the web.

I got everything set up from google's directions, but when I attempt to build from the source, I dont have the option to select toro.
1. full-eng
2. full_x86-eng
3. vbox_x86-eng
4. full_grouper-userdebug
5. mini_armv7a_neon-userdebug
6. mini_armv7a-userdebug
7. full_wingray-userdebug
8. full_crespo-userdebug
9. full_maguro-userdebug
10. full_panda-userdebug

jtvd78 said:
I got everything set up from google's directions, but when I attempt to build from the source, I dont have the option to select toro.
1. full-eng
2. full_x86-eng
3. vbox_x86-eng
4. full_grouper-userdebug
5. mini_armv7a_neon-userdebug
6. mini_armv7a-userdebug
7. full_wingray-userdebug
8. full_crespo-userdebug
9. full_maguro-userdebug
10. full_panda-userdebug
Click to expand...
Click to collapse
instead, do:
Code:
. build/envsetup.sh && lunch full_toro-user && make -j4 otapackage
done.

Thanks! One more question... where exactly is the finished zip?

it tells you where it is when it finishes building..
out/target/device/samsung/toro/
sent from my i9250

Building roms for Oppo N1

I understand there are some builds available on github ( https://github.com/omnirom/android_device_oppo_n1 ). Please could anyone guide on how to build it so we can test it on our devices. Thanks.

That would be a pretty in-depth guide.
Omnirom has their own wiki page that can teach you how to compile and port to your device.
http://docs.omnirom.org/Main_Page
:good:

Thank you Harfainx for sharing the guide, I'll try following it and post my finding(s) for everyone.

Omni rom has been posted on the official oppo forums already: http://www.oppoforums.com/threads/4-4-omni.7475

nospam said:
Omni rom has been posted on the official oppo forums already: http://www.oppoforums.com/threads/4-4-omni.7475
Click to expand...
Click to collapse
Sure wish he would post them here instead, or as well. I do check both forums but like to treat XDA as the "ultimate" resource.

I'm sure there will be an official Omni thread with the links here as well.
Sent from my N1 using Tapatalk

Harfainx said:
I'm sure there will be an official Omni thread with the links here as well.
Sent from my N1 using Tapatalk
Click to expand...
Click to collapse
Yeah, plodey and I will eventually get around to it... we've just been incredibly busy with getting the device running and other general omni things.
Anyone who knows me from the i777 days knows that I suck at thread maintenance.

Entropy512 said:
Yeah, plodey and I will eventually get around to it... we've just been incredibly busy with getting the device running and other general omni things.
Anyone who knows me from the i777 days knows that I suck at thread maintenance.
Click to expand...
Click to collapse
Glad to hear an official response. Thanks for the update. :highfive:

viperdream26 said:
Sure wish he would post them here instead, or as well. I do check both forums but like to treat XDA as the "ultimate" resource.
Click to expand...
Click to collapse
Maintaining a thread is more work then you would ever think
At the moment I am more then full doing that at oppoforums

I'm going to take a crack at compiling the Cyanogen Source code to take a peek at the o-click issues.
I'm fairly knowledgeable in C, but haven't done any android/bluetooth coding before, so I think I have a snowball's chance in hell.
But it'll be an interesting exercise anyway.
So I'm following random links in:
http://wiki.cyanogenmod.org/w/Development
Mainly using this:
https://skydrive.live.com/view.aspx?cid=B3BFF0D42AE1E534&resid=B3BFF0D42AE1E534!107&app=OneNote
To set up virtualBox/Ubuntu/android SDK.
Although I am a bit confused about required JDK versions.
Is there a list of prefered JDK versions for different CM versions?
I also just noticed the page for the Find 5: aka
http://wiki.cyanogenmod.org/w/Build_for_find5
So I guess I'll use that as the instructions until the actual source code pull?
- Frank

You might want to look at maxwen's github - I think he had source for a sample app for the O-Click.
https://github.com/maxwen/OClick

Entropy512 said:
You might want to look at maxwen's github - I think he had source for a sample app for the O-Click.
https://github.com/maxwen/OClick
Click to expand...
Click to collapse
This is based on the Google BLE sample. It allows pairing with the o-click and will recognise single and double clicks on the remote
Sent from my N1 using Tapatalk

I'm slowly making some progress.
I have some questions:
1) Where can I find information about how updater-script is generated?
I'd like to automatically remove that first line which is causing TWRP to complain.
2) I got a zip file but it failed to install, and just hung after reboot.
I've compared the good "signed" zip to my zip file and I seem to be missing all the vendor specific stuff.
I extracted everything and it all exists in ~/android/system/vendor/oppo/n1/proprietary .
But it's not ending up in the final zip file.
I think the problem is that ~//android/system/vendor/cm/vendorsetup.sh is choking because
there isn't an official N1 build listed on: https://github.com/CyanogenMod/hudson/blob/master/cm-build-targets
Do I have to hack my way around that?
Any help would be much appreciated.
I'm trying to research myself but it seems like information is scattered all over the place.

ChodTheWacko said:
I'm slowly making some progress.
I have some questions:
1) Where can I find information about how updater-script is generated?
I'd like to automatically remove that first line which is causing TWRP to complain.
2) I got a zip file but it failed to install, and just hung after reboot.
I've compared the good "signed" zip to my zip file and I seem to be missing all the vendor specific stuff.
I extracted everything and it all exists in ~/android/system/vendor/oppo/n1/proprietary .
But it's not ending up in the final zip file.
I think the problem is that ~//android/system/vendor/cm/vendorsetup.sh is choking because
there isn't an official N1 build listed on: https://github.com/CyanogenMod/hudson/blob/master/cm-build-targets
Do I have to hack my way around that?
Any help would be much appreciated.
I'm trying to research myself but it seems like information is scattered all over the place.
Click to expand...
Click to collapse
I'm in no way an expert and am currently in the process of setting up my first build environment now. In regards to #2, I noticed that in the vendorsetup.sh on the N1's github page - https://github.com/CyanogenMod/android_device_oppo_n1 - it sets up the lunch combos for you.
add_lunch_combo cm_n1-user
add_lunch_combo cm_n1-userdebug
add_lunch_combo cm_n1-eng
Click to expand...
Click to collapse
Could you just be using the wrong vendorsetup script or should that one run first? Like I said, I'm still very new to this but wanted to at least point this out.

mybrotherischad said:
I'm in no way an expert and am currently in the process of setting up my first build environment now. In regards to #2, I noticed that in the vendorsetup.sh on the N1's github page - https://github.com/CyanogenMod/android_device_oppo_n1 - it sets up the lunch combos for you.
Click to expand...
Click to collapse
You're right, the n1 directory's vendor explicitly lists them.
I was looking at the wrong one I guess. Or it's not being used for some reason.
My Brunch n1 is also complaining with:
The present kernel configuration has modules disabled.
Type 'make config' and enable loadable module support.
Then build a kernel with module support enabled.
which doesn't look right, but I'm taking stuff one step at a time.
- Frank