yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Q&A, Help & Troubleshooting] hop3l3ss1990:
Good evening,

Well how have you imagined that? Do you have build something like that before or would this be your first attempts to build up a rom from scratch? Do you know what's all necessary to contribute for that?

I would try to help you, but I have clearly to say that I haven't done anything like this before. I'm in the last term of my study of technical computer sciences, working in a company as application programmer for C/C++ and Java(Android). Due to my studies I have also some knowledge about hardware programming, down to read/writing some code in assembler. I would be interested to this if I get introduced to the topic and some help with the necessary tool chain wouldn't hurt too ^^.

greetings :)
[Galaxy S III Q&A, Help & Troubleshooting] andy572:
I have successfully built a rom in year 2010 for the LG-P500 device, based on CM7 and modified it in a strange way, so i included a lot of nice things

written from scratch - this rom was a unicate;) ... later, i developed the "Phoenix Launcher" for Gingerbread enabled devices, but its development is currently

frozen because its strange to support every or almost every device with a bugless launcher. In the last months i learned a lot about android and have to re-think about

what i'm able to do, and what i want to do. In the summer of 2011 i bought my SGS3, the first thing i was doing was to remove that samsung crap from my device and

have installed AOKP. So now it's time to do my own thing again - i want to have AOSP as i think for me its the best Android solution for myself and want to publish it

to other users who think "thats ok for me" too :)

In short, it doesnt matter if its your first rom - its enough if you know about basic things like "how is android doing all that nice things", "how to debug code", "how to fix

some bugs (even strange bugs)" and some experience with git and github. All other you can learn in a very short time - i've learned the most of things with try & error :)
[Galaxy S III Q&A, Help & Troubleshooting] hop3l3ss1990:
This all sounds interesting for me and yes I like the idea of developing a own clean rom with some cool additional stuff, too. But what would be the first steps to a new rom? Have you begun with all the administration stuff like setting up a new gitrepo, make a to do list etc...?

I think Code debugging and writing some new stuff wouldn't be a problem for me but what are you meaning excactly with "how is android doing all that nice things"? How it build up, deep level architecture? Well, I know how the "normal" Linux system is working, how modules are getting loaded into the kernel... But how this is correctly working on android I have to learn at first and if there is a chance to do that I would do it :)

Currently on my S3 is SlimBean and till that there is still no update to 4.2 I'm happy with it, but exploring something new would be pretty cool :)

Do you have an IRC chat room or something like that? I've to go offline now, my girlfriend wants more attention.^^ But If you want, I' m willing to try to contribute to the rom :)

PS. I'm sorry for my bad English and hope its understandable, but outside from here you can talk to me in German ^^
[Galaxy S III Q&A, Help & Troubleshooting] wmc90:
If you want to help the AOSP experience on our phones the best place to do it is with the CyanogenMod guys. You'll find pretty much everything based on AOSP (including people that port Vanilla AOSP and AOKP) is using a CM kernel.

They're likely working on the merge now in terms of getting CM10.1 out (with Android 4.2) but most of our CM guys are pretty burned out on working with Samsung's subpar reference material to get basic stuff working (mostly HWC). If you think you could help with this, this would be provide a massive boost to the whole community that want to run these phones on an AOSP based ROM and they would be very grateful.

Gotta warn you though it sounds like it'll be an uphill struggle to get the rest of the stuff working right; unless Samsung release some decent sources for HWC.
[Galaxy S III Q&A, Help & Troubleshooting] andy572:
Currently i have only downloaded the AOSP sources and started to integrate most of the configs. Currently it cant compile because AOSP is not AOKP/CM10

where i got the device and vendor directories, so i have to make some changes in the basic system. if it's compiling to the end, i open a fresh github account

and upload all my modifications. The compile process stops currently on audio,OMX plugins, graphics and camera - most of that are small pieces of changes

i have to make - i think, tomorrow (its monday in germany here) i can upload all and then we can start to develop on :)
[Galaxy S III Q&A, Help & Troubleshooting] haydar100:
Wish i could help (just started learning JAVA ) ! gl with this awesome project
[Galaxy S III Q&A, Help & Troubleshooting] ivan1real:
Nice to see you here, I remember you from the P500 forums.
[Galaxy S III Q&A, Help & Troubleshooting] slaphead20:
Xda user krarvind should be able to give you some useful hints, you will have to contact him through the RD forum as his pm is locked down, or I could possibly put him in contact with you
[Galaxy S III Q&A, Help & Troubleshooting] andy572:
Thank you, it would be nice if you can contact him :)
[Galaxy S III Q&A, Help & Troubleshooting] slaphead20:
Ok, will mention it to him :)
[Galaxy S III Q&A, Help & Troubleshooting] hop3l3ss1990:
How it's going forward? :)

Maybe it could be useful to publish the github link when it's ready and some more information like staus, on first post :)

In the next days I have some trouble with my exams ( in two weeks I'm completely finished with my studies ^^) but I think if there is something to do I'll find some time to work on. :)
[Galaxy S III Q&A, Help & Troubleshooting] sox978:
Good Luck Dude~

I haven't tried AOSP yet.

Hope someday i can give it a go.:silly:
[Galaxy S III Q&A, Help & Troubleshooting] andy572:
current state:

- patched android/build so we can compile the kernel within the main compile process

- patched android/build main.mk file so we can use OpenJDK or Oracle JDK

- added android/vendor/aokp and android/vendor/samsung tree from AOKP (its the most useful directory structure)

- added android/hardware from AOKP so we have all that Exynos things that are needed, even by AOSP

- modified android/frameworks/native/include so a OMX Plugin header can be found

- modified android/libhardware and patched gralloc module

currently it compiles to the Webkit library, most of all apps, libs and binaries are building without errors - the next problem

to solve is the PRODUCT_COPY_FILES ****: nothing of proprietary files are copied to the android/out directory, seems like

a bug in android/build too.

For only 2 days trying to compile to the end without errors its a very good cut :D
[Galaxy S III Q&A, Help & Troubleshooting] andy572:
here we go: it compiles to the end and a flashable "JOP40" zip could be created :)

tryed to flash, but it gives errors in CWM: have to remove the recovery folder and the recovery.sh file from etc folder in the ota zip file, but it doesnt boot up - got a black screen only.

do we need a new or patched kernel instead the CM10 smdk421x one?
[Galaxy S III Q&A, Help & Troubleshooting] b-eock:
Well does it have all the closed source libraries fron the phone? If not, it wont boot. Dont think i am calling you stupid, you obviously know what you are doing, but maybe you forgot. Idk. Check that. Try running a log cat and debug that.
[Galaxy S III Q&A, Help & Troubleshooting] andy572:
Thanks for the hint, yes i have all files included - i cant connect to adb, i see only small colored point on the top left side and a sensor

is red blinking (the one to the right of the speaker.
[Galaxy S III Q&A, Help & Troubleshooting] b-eock:
That would be the proximity sensor near the top front speaker. Cant connect, adb binary in /system/bin or xbin?
[Galaxy S III Q&A, Help & Troubleshooting] zoot1:
We hope you will get well soon..don't worry about development your health is more important..
[Galaxy S III Q&A, Help & Troubleshooting] maddes1402:
Get well soon, gute Besserung :(

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Q&A, Help & Troubleshooting] krakkhor:
Gute Besserung

Gute Besserung Meister.

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Q&A, Help & Troubleshooting] Mrboxfacetramp13:
Get better soon

:cowboy:
[Galaxy S III Q&A, Help & Troubleshooting] rock4hell:
Get well soon bro
[Galaxy S III Q&A, Help & Troubleshooting] rock4hell:
Hey bro how's your health any news ?:confused:
[Galaxy S III Q&A, Help & Troubleshooting] UrbanDrawer:
Hey man, feeling better?

I know it's bad to ask for ETA's but it's been four months since last post.
[Galaxy S III Q&A, Help & Troubleshooting] orbine:
Get well soon brother.
[Galaxy S III Q&A, Help & Troubleshooting] UrbanDrawer:
Dead thread, so sad.
[Galaxy S III Q&A, Help & Troubleshooting] andy572:
adb is in /system/bin.

but, i think i know about the reasons:

1.) not patched the system/vold directory

2.) boot.img is in secure mode (but debug is enabled - its a userdebug build)

will try to fix that first :)
[Galaxy S III Q&A, Help & Troubleshooting] b-eock:
Ok good luck. Anything else?
[Galaxy S III Q&A, Help & Troubleshooting] andy572:
Found some things that i have patched in adb and init.rc too ...

The bad - i sit in my job and cant test all that fixes^^

i have created a github account for working in a team: https://github.com/S3AOSP.

beware: the repo "android_manifest" isnt modified - its currently the copy of the original only, have to be modified to match

our modifications. all other uploaded stuff is very patched and works - its the state of my first complete build from the last night :)

i hope, the adb fixes i found can solve the muted debugger, otherwise i have to search again for a solution.

maybe, another reason for not seeing adb might be a mistake in the boot.img - later when i'm back @home i try to boot with a "old" boot.img
[Galaxy S III Q&A, Help & Troubleshooting] atilla88:
Very interesting stuff here,

I wish you guys good luck with this project
[Galaxy S III Q&A, Help & Troubleshooting] andy572:
changing the boot.img from another rom brings nothing - still a black screen only, no boot animation :(
[Galaxy S III Q&A, Help & Troubleshooting] w1nter456:
There is some hard time to patch, the kernel version is 3.4 in nexus 4. Moreover, Samsung hwcomposer is broken and undocumented. I think Andy you should try talk with xplodwild for more details. He is quite friendly and helpful in this matter.
[Galaxy S III Q&A, Help & Troubleshooting] andy572:
Found my own mistake: boot.img from SuperNexus and AOKP are working, the problem was my adb driver on my windows machine^^

now i got debug output, the device can boot (even with disabled SEAndroid) - only surfaceflinger and audio is crashing. This is OK for

now because i have only patched the gralloc module, nothing frameworks/base or frameworks/av nor the audio module which are essential to

work with devices :)

So the next step for now is to find out, how we have to patch that UI things so we can boot to the GUI ;)

### EDIT

Today i added support for missing SecTVOut library, possibly it was crashing the mediaserver and later surfaceflinger.

Currently i'm compiling from fresh patched source tree - i hope, i can boot to some later points instead of "init" and sensors only :)

... wish me luck please :D
[Galaxy S III Q&A, Help & Troubleshooting] andy572:
Found some interesting things why i cant boot to the UI:

1) SGS3 needs the TVOutLibrary to boot, its a proprietary system service provided by samsung. this service needs to connect to the framebuffer device and here we

need a working gralloc (have that fixed yesterday and now its starting to the next error: "cant open device /dev/fb")

2) A sh*t bug in the AOSP repo's: the files in /system/usr/share/zoneinfo are not built because they doesnt exists - here we need to get the missing files from

another AOSP bionic repo: not from android-4.2_r1 (as this is the public branch of android) but from jb-dev :D ...otherwise, the system is crashing complete and nothing

can be started by the android runtime.

now the surfaceflinger service is waiting,waiting,waiting ... needs a working hwcomposer which i can find in CM10 repos - with all that things fixed

i think (or better to say "hope") after my next build i can view a booting screen instead of a black box where is labeled "Samsung" :D

### EDIT

sensors are working but the (unimplemented fix for) camera - the logcat looks very good now
[Galaxy S III Q&A, Help & Troubleshooting] scheichuwe:
As for "working" hwcomposer and such:

Did you already read this one?

https://plus.google.com/u/0/101093310520661581786/posts/DHg5z62CHHu
[Galaxy S III Q&A, Help & Troubleshooting] andy572:
Wooohoooooooo ... booted 4.2 to the UI successfull (even with a lot of errors, but) - it goes forward:)
[Galaxy S III Q&A, Help & Troubleshooting] brenogbi:
Great man!!
[Galaxy S III Q&A, Help & Troubleshooting] Arjen:
Hi Andy,

Sure looks like you have too much time ;)

Btw, thanks for learning me a lot in your Optimus One days :D
[Galaxy S III Q&A, Help & Troubleshooting] andy572:
Haha, right :D its some cold out and i'm almost in holiday :)
[Galaxy S III Q&A, Help & Troubleshooting] wednesday13:
Good luck. Looking forward to this
[Galaxy S III Q&A, Help & Troubleshooting] haydar100:
Would be nice if we could follow your project in a development thread
[Galaxy S III Q&A, Help & Troubleshooting] andy572:
Currently its more a work in progress: there is no complete and stable boot to the home screen. When its done, i open a development thread

and someone can help to fix bugs :)
[Galaxy S III Q&A, Help & Troubleshooting] haydar100:
:) awesome
[Galaxy S III Q&A, Help & Troubleshooting] jenzy1985:
New News ??? Great Projekt

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Q&A, Help & Troubleshooting] andy572:
Currently not, just working on hwcomposer/libsecion and gralloc problem to get a stable UI. currently it's crashing with "not enough memory"

from ICS gralloc module
[Galaxy S III Q&A, Help & Troubleshooting] andy572:
Graphic is up and running stable, with NEW drivers, patched and bugfixed by me.

Android 4.2 has removed PMEM memory allocator and is now using ION for faster UI - now, our beloved i9300 is using ION and its

fu**ing fast.

Next step to fix: integrate the RIL component so i can login to my phone :laugh:
[Galaxy S III Q&A, Help & Troubleshooting] b-eock:
Do you think that the TeamHackSung could use the new HwComposer?
[Galaxy S III Q&A, Help & Troubleshooting] delsus:
If you make any good progress with this before CM10.1 is released it may be a good idea to contact TeamHackSung and give them your drivers, hwcomposer etc so we ca get a stable CM10.1 as well.

Brilliant job, I'll be keeping up to date on this thread, I want 4.2...
[Galaxy S III Q&A, Help & Troubleshooting] andy572:
Its a modified hwcomposer and gralloc module by me, and a patch found on CM gerrit for the surfaceflinger, where the HWC version check needs to

be disabled to work with. This way isnt the best because here we make it impossible to look forward for newer code where a version check is needed,

but as a temporay workaround it is ok^^

i'll submit my cleaned code (currently its freaky code from testings :D) on weekend to my github account.
[Galaxy S III Q&A, Help & Troubleshooting] kroat999:
why not work together with xplodewild and entropy
[Galaxy S III Q&A, Help & Troubleshooting] haydar100:
watch out guys ! we got a genius over here :good:
[Galaxy S III Q&A, Help & Troubleshooting] Entropy512:
Why are you pushing to github and not submitting to gerrit???
[Galaxy S III Q&A, Help & Troubleshooting] Theshawty:
This is some interesting shizzle. I'll be sure to keep an eye on this! :D
[Galaxy S III Q&A, Help & Troubleshooting] Skander1998:
Nerdgasms reaching dangerous levels :D
[Galaxy S III Q&A, Help & Troubleshooting] Arkanius:
A new challenger appears!

Nice work andy!
[Galaxy S III Q&A, Help & Troubleshooting] yangsuli:
Hi,

I would like to help if you still need some labor.

I wouldn't call myself "experienced" but I do have to hack into Android in order to do my daily work (which is related to Android IO behavior). I just got a Galaxy S3 on hand, so I haven't tried build a ROM from source code and flash it into my phone yet. I did try to change the stock ROM (namely the init.rc to change the mounting behavior) and got that to work though.

Please let me know if you think you could use my help :)

Suli
[Galaxy S III Q&A, Help & Troubleshooting] yahyoh:
WOW :cool:
[Galaxy S III Q&A, Help & Troubleshooting] bala_gamer:
This is interesting and this is the reason I love this community. Keep up the great work :beer:

《posted from samsung rom》
[Galaxy S III Q&A, Help & Troubleshooting] Stevemeister:
Maybe you should work together with Entropy/Xplodwild/Codeworkx and submit your work to Gerrit. Could speed up the process...
[Galaxy S III Q&A, Help & Troubleshooting] rock4hell:
amazing thanks

+1
[Galaxy S III Q&A, Help & Troubleshooting] zack037:
is it possible to make ur device UI viewable via ur dekstop/laptop?

kinda like an emulator, what happens to ur device screen will show up to ur desk/laptop.

is it possible to add that as a mod on 4.2 if it do-able? :fingers-crossed:
[Galaxy S III Q&A, Help & Troubleshooting] Flynny75:
You mean like miracast? or ADB?
[Galaxy S III Q&A, Help & Troubleshooting] andy572:
I dont know if it works, but there is a app in the playstore for that ;)

https://play.google.com/store/apps/details?id=org.onaips.vnc&hl=de

BTW: I want to provide a pure AOSP ROM, no additions - this is, what AOSP users want to have ;)
[Galaxy S III Q&A, Help & Troubleshooting] Theshawty:
How are you faring with this, if one may inquire?
[Galaxy S III Q&A, Help & Troubleshooting] andy572:
just write me a PM or here in the topic - i'll read it :)
[Galaxy S III Q&A, Help & Troubleshooting] Theshawty:
You misunderstood ;)

In simpler terms, I asked how it's going. Awesome that you got graphics working :D
[Galaxy S III Q&A, Help & Troubleshooting] haydar100:
wondering how you fixed the graphics. when will you push it on github? might learn something out of this :)
[Galaxy S III Q&A, Help & Troubleshooting] zack037:
Well VNC isnt that really reliable, but u got the idea =)

since u building it from scratch, why not make it as one as one of the new 4.2 feature?
[Galaxy S III Q&A, Help & Troubleshooting] avocco:
Are you serious? This guy is already devoting all his free time trying to get an AOSP ROM working for us, yet you want him to do even more stuff considering he's starting from scratch?

How about I give you a hand with this one, buy yourself a book on C / C++ coding. Learn the basics, write a large program and when it fails to compile and you have to shift through lines and lines of code, trying to find out what's wrong. You will find whats wrong and fix it but it will fail again. This process will get repeated again and again and again. Its pure trial and error. Only after all that will you understand the monumental task you asked the developer today.
[Galaxy S III Q&A, Help & Troubleshooting] b-eock:
People that don't know code nor how to code are the people who respect developers the least. They don't get it. They won't until they do what you said and learn, write, trial and error. Profit
[Galaxy S III Q&A, Help & Troubleshooting] zack037:
There is no need to be angry about it, im just stating out an opinion.. i know how hard it can be...
[Galaxy S III Q&A, Help & Troubleshooting] sharingan92:
@andy572

May i ask what recovery you are using as i know AOSP 4.2 requires the latest TWRP or CWM 6.0.1.9 to flash the rom correctly due to changes in the infrastructure

im what Willis was talking about
[Galaxy S III Q&A, Help & Troubleshooting] andy572:
i'm using 5.8.4.3 and its working, dunno why - i dont have modified the recovery nor installed a new one :D
[Galaxy S III Q&A, Help & Troubleshooting] sharingan92:
Hmm weird over on the gnex forums people were ****ty because they lost files but didn't know that Google had made changes to the infrastructure but anyway maybe were lucky lol

im what Willis was talking about
[Galaxy S III Q&A, Help & Troubleshooting] avocco:
I'm not angry just shocked at your question. Its like going up to a car mechanic and saying "Wow! That's a nice car your building there bro, since your building it from scratch wouldn't it be better if it could fly?"
[Galaxy S III Q&A, Help & Troubleshooting] Skander1998:
-End the fighting after this line or you will be reported and you will probably go for a vacation.-

This is in the General section, but it is for developers or users to contribute or ask legitimate questions, not for noobs to fight in.

We need a developer Q/A forum just like the note1 forum.
[Galaxy S III Q&A, Help & Troubleshooting] Dav_prime:
Please don't tar all of us non-coders with the same brush. I for one have an enourmous amount of respect for the devs and wish I had leaned to code in the past so that I could contribute.

We are all frustrated with the state of AOSP on the S3, my frustration is directed squarely at samsung for witholding sources and documentation. In fact in light of this I am amazed (and greatful) that devs have stuck with it this long to give us the roms and tweaks we can all enjoy.
[Galaxy S III Q&A, Help & Troubleshooting] dogans:
I'm very excited to see this project. I hope you can get AOSP working for us Andy, especially since you cracked the graphics issue :)

Great job!
[Galaxy S III Q&A, Help & Troubleshooting] stiggy2012:
Hi Andy,

Thanks very much for your hard work on this. I recently got an SIII having ran out of patience with Google over the Nexus 4 debacle, and was surprised to find there isn't a decent AOSP build currently available.

I'm not much of a coder, I can only really "write code" in BASH with a little Python/Perl knowledge so I'm not sure I'd be much help on fixing issues/getting stuff to work.

However I am a pretty good Linux sysadmin! So if you'd like and when you feel the codebase is ready, I can happily setup a Jenkins CI service for nightly builds? Might be easier to get more devs on board too if we have open codebase available in github and a CI server building automatically on check-in?

Thanks,

Steve
[Galaxy S III Q&A, Help & Troubleshooting] norpan111:
Wait, is that something cm10 could have use of? Fixing graphics I mean

Skickat från min GT-I9300 via Tapatalk 2
[Galaxy S III Q&A, Help & Troubleshooting] cmajetic:
cm10 works quite good, maybe the cm10.1 devs can use some things but I'm not sure if anyone from the cm team will work on cm10.1 for this device anymore...
[Galaxy S III Q&A, Help & Troubleshooting] FadeFx:
I think if Andy can get his build running there will be a cm10.1 as well, and if not, he could apply to cm team as device maintainer and do it by himselfs. At least if he has the passion to do so.

_________________________

tapatalked from GalaxyS
[Galaxy S III Q&A, Help & Troubleshooting] Theshawty:
If Andy succeeds which I think he will, then the CM team will have a solid base. :D
[Galaxy S III Q&A, Help & Troubleshooting] vinaybaboo:
Phoenix AOSP for LG P500 devloped by you was awesome. Was the daily driver during the good old days of Optimus One. Hope you do the same magic here too.

All the best Andy.:thumbup::thumbup::thumbup::thumbup:
[Galaxy S III Q&A, Help & Troubleshooting] Stevemeister:
Maybe you should check Gerrit more often. Codeworkx already did a lot of commits and stuff, hope they dont do stuff double.
[Galaxy S III Q&A, Help & Troubleshooting] norpan111:
But they are working on cm10.1 according to google+, cm10 isn't running very smooth for me. Known issue as well

Skickat från min GT-I9300 via Tapatalk 2
[Galaxy S III Q&A, Help & Troubleshooting] d4c:
Well done bro keep up the good work :)
[Galaxy S III Q&A, Help & Troubleshooting] Mrboxfacetramp13:
Wish that this was already available
[Galaxy S III Q&A, Help & Troubleshooting] UrbanDrawer:
How's the porting going?
[Galaxy S III Q&A, Help & Troubleshooting] xukaisheng:
Thanks for all your hard work.:)