Galaxy Player 4.2 Developent - Need Help! - Samsung Galaxy Player 4.0, 5.0
Hello fellow users of the SAMSUNG Galaxy Player 4.2!
I just recently received a Galaxy Player 4.2 for free from my brother SerkTheTurk since he got a Moto G, and I am planning to use it as an experimental device for development, since it's not my main device. I've gotten a device tree from SerkTheTurk and I've synced all the repos from CyanogenMod. I just need help on what to do next. I know that Serk made a complete build but it didn't boot. I just need help on what to change on the device tree and kernel files, if anybody can help I will appreciate it a lot. (I'm not super experienced on this topic but I can do work). Thanks! :fingers-crossed:
CenterTurkHD said:
Hello fellow users of the SAMSUNG Galaxy Player 4.2!
I just recently received a Galaxy Player 4.2 for free from my brother SerkTheTurk since he got a Moto G, and I am planning to use it as an experimental device for development, since it's not my main device. I've gotten a device tree from SerkTheTurk and I've synced all the repos from CyanogenMod. I just need help on what to do next. I know that Serk made a complete build but it didn't boot. I just need help on what to change on the device tree and kernel files, if anybody can help I will appreciate it a lot. (I'm not super experienced on this topic but I can do work). Thanks! :fingers-crossed:
Click to expand...
Click to collapse
Hey, you can build cm7 from my repositorys here is the readme how to
hoerwer there a still some bugs like no deep sleep
https://github.com/ChaOS-Development/android_device_samsung_hugo/blob/master/README.txt
CenterTurkHD said:
Hello fellow users of the SAMSUNG Galaxy Player 4.2!
I just recently received a Galaxy Player 4.2 for free from my brother SerkTheTurk since he got a Moto G, and I am planning to use it as an experimental device for development, since it's not my main device. I've gotten a device tree from SerkTheTurk and I've synced all the repos from CyanogenMod. I just need help on what to do next. I know that Serk made a complete build but it didn't boot. I just need help on what to change on the device tree and kernel files, if anybody can help I will appreciate it a lot. (I'm not super experienced on this topic but I can do work). Thanks! :fingers-crossed:
Click to expand...
Click to collapse
Great to some new devs.
I'm actually porting Android 4.4 "KitKat" to the Player 3.6 and with my help you could port KitKat also to the Player 4.2.
At first you need to get familiar with Androud building, so use Google and read something about it.
PM me for more help or information.
Greetings,
Androthan
Sent from my Nexus 7 using XDA Free mobile app
Need Help With building from source
Androthan said:
Great to some new devs.
I'm actually porting Android 4.4 "KitKat" to the Player 3.6 and with my help you could port KitKat also to the Player 4.2.
At first you need to get familiar with Androud building, so use Google and read something about it.
PM me for more help or information.
Greetings,
Androthan
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
I'm a noob to developing roms but i decided to build a aokp kitkat rom for the galaxy player 4.2. I need someone to direct me to all the repo files for this device(device,kernal, and vendor repos). Someone please help me out because i would love to be running kitkat on my player 4.2. Thanks.
brewsterj98 said:
I'm a noob to developing roms but i decided to build a aokp kitkat rom for the galaxy player 4.2. I need someone to direct me to all the repo files for this device(device,kernal, and vendor repos). Someone please help me out because i would love to be running kitkat on my player 4.2. Thanks.
Click to expand...
Click to collapse
I think if there had been any full set of repo files that could build KitKat, other devs would've built it and you would've got KitKat earlier. Right now porting (instead of compiling) is the only hope I can see for GP4.2, but who knows
Sent from Google Nexus 4 @ CM11
AndyYan said:
I think if there had been any full set of repo files that could build KitKat, other devs would've built it and you would've got KitKat earlier. Right now porting (instead of compiling) is the only hope I can see for GP4.2, but who knows
Sent from Google Nexus 4 @ CM11
Click to expand...
Click to collapse
I found the repo files but i hit a wall while going to lunch, i get this.
Which would you like? [aosp_arm-eng] 17
build/core/product_config.mk:238: *** _nic.PRODUCTS.[[vendor/aokp/products/bacon.mk]]: "device/oneplus/bacon/full_bacon.mk" does not exist. Stop.
** Don't have a product spec for: 'aokp_bacon'
** Do you have the right repo manifest?
im not sure which option to choose either but i get the same thing with every one. I pm'd some developers about it and hopefully they can tell me somthing.
brewsterj98 said:
I found the repo files but i hit a wall while going to lunch, i get this.
Which would you like? [aosp_arm-eng] 17
build/core/product_config.mk:238: *** _nic.PRODUCTS.[[vendor/aokp/products/bacon.mk]]: "device/oneplus/bacon/full_bacon.mk" does not exist. Stop.
** Don't have a product spec for: 'aokp_bacon'
** Do you have the right repo manifest?
im not sure which option to choose either but i get the same thing with every one. I pm'd some developers about it and hopefully they can tell me somthing.
Click to expand...
Click to collapse
You are using the repo files for the Oneplus ONE...(codename bacon). The galaxy player 4.2's codename is "hugo". There are no 4.4 repo files for the 4.2
Sent from my XT760
so my only hope is to port?
or could i somehow build a repo file for it?
You are going to have to follow the official CM guide to port cm to a new device...to make a device, vendor and kernel tree...then you can use that to try and build AOKP...
EDIT: Here it is... http://wiki.cyanogenmod.org/w/Doc:_porting_intro If you dont find the method difficult, you can also ask Androthan for help as he has ported cm11 to the galaxy player 3.6, which is very similar to the 4.2.
Sent from my XT760
Another Guide
drakonizer said:
You are going to have to follow the official CM guide to port cm to a new device...to make a device, vendor and kernel tree...then you can use that to try and build AOKP...
EDIT: Here it is... http://wiki.cyanogenmod.org/w/Doc:_porting_intro If you dont find the method difficult, you can also ask Androthan for help as he has ported cm11 to the galaxy player 3.6, which is very similar to the 4.2.
Sent from my XT760
Click to expand...
Click to collapse
Can you point me to a guide that explains more and goes more in-depth about the process?
There are a limited number of guides for this process, this being the best imo. You should understand a few things if you're planning to undertake this project.
1. You cannot expect a guide for everything. Use google for any info that you need and ask devs. Search xda for threads that explain a similar problem.
2. If you don't have knowledge about the Android Build Process, some basic C knowledge, and have not even built a ROM that already has /device, /vendor etc. , I'd recommend not doing this, because even the best of devs reach problems while porting ROMs.
Sent from my XT760
drakonizer said:
There are a limited number of guides for this process, this being the best imo. You should understand a few things if you're planning to undertake this project.
1. You cannot expect a guide for everything. Use google for any info that you need and ask devs. Search xda for threads that explain a similar problem.
2. If you don't have knowledge about the Android Build Process, some basic C knowledge, and have not even built a ROM that already has /device, /vendor etc. , I'd recommend not doing this, because even the best of devs reach problems while porting ROMs.
Sent from my XT760
Click to expand...
Click to collapse
No, I have the knowledge(studied a bunch of stuff for hours and already have android build enviroment set up and i have a github account to access the files i need also, I have also ported using the android kitchen and a few other methods too never perfectly but i think porting it the official way would have a better result.) its just that i haven't tried porting through this method. I was following the guide all the way up until it said to get certain stuff from a file we pulled from my device using the terminal but i could never find the file. I know that repos and such go into a working folder or directory its just some stuff i just cant find.
Oh okay great then
Btw, porting with android kitchen and the whole copy paste the files from one ROM to the other to get port a custom ROM is TOTALLY different from what you're trying to do here.
I suggest you fork a repo from Androthan's CM11 for the 3.6 and start renaming it for us (our codename is "hugo", their's is "aalto" but the vendor is the same). If you can mention clearly what file you're not getting, and/or other problems you're facing, you can expect some help from the devs of the Galaxy Player (including all the players) community
Sent from my XT760
drakonizer said:
Oh okay great then
Btw, porting with android kitchen and the whole copy paste the files from one ROM to the other to get port a custom ROM is TOTALLY different from what you're trying to do here.
I suggest you fork a repo from Androthan's CM11 for the 3.6 and start renaming it for us (our codename is "hugo", their's is "aalto" but the vendor is the same). If you can mention clearly what file you're not getting, and/or other problems you're facing, you can expect some help from the devs of the Galaxy Player (including all the players) community
Sent from my XT760
Click to expand...
Click to collapse
ok i have forked the cm11 files for the 3.6 now how should i go about renaming it?(sorry for the noob question)
---------- Post added at 01:39 PM ---------- Previous post was at 01:32 PM ----------
brewsterj98 said:
ok i have forked the cm11 files for the 3.6 now how should i go about renaming it?(sorry for the noob question)
Click to expand...
Click to collapse
and this is where i got lost into the guide.
[So, if you have previously installed adb onto your computer, you can use the following command to pull this file to your computer:
adb pull /system/build.prop
Once you have the file...
Write down the value of the ro.product.manufacturer parameter. This will be your vendor name. The [vendor] is the name of the manufacturer/vendor of the device. CM has established naming conventions for most major vendors, such as samsung, htc, lge, etc. Note that in these directory names, the vendor is always lowercase and contains no spaces.
Write down the value of the ro.product.device parameter. This will be your device codename. The [codename] corresponds to the project code name of the device itself. This is almost never the sales name of the device. If you have built CM before (and again, you better have!), you should be familiar with the concept of a code name for each device. Like the vendor name, the codename is always lowercase and contains no spaces.]
Where does the pulled build.prop go? and are there any specific linux programs i would need to edit this file or any other files throughout the tortorial? I have gedit installed and its met my needs so far but do i need something more advanced to accomplish my goal?
got the repo renamed.
brewsterj98 said:
ok i have forked the cm11 files for the 3.6 now how should i go about renaming it?(sorry for the noob question)
---------- Post added at 01:39 PM ---------- Previous post was at 01:32 PM ----------
and this is where i got lost into the guide.
[So, if you have previously installed adb onto your computer, you can use the following command to pull this file to your computer:
adb pull /system/build.prop
Once you have the file...
Write down the value of the ro.product.manufacturer parameter. This will be your vendor name. The [vendor] is the name of the manufacturer/vendor of the device. CM has established naming conventions for most major vendors, such as samsung, htc, lge, etc. Note that in these directory names, the vendor is always lowercase and contains no spaces.
Write down the value of the ro.product.device parameter. This will be your device codename. The [codename] corresponds to the project code name of the device itself. This is almost never the sales name of the device. If you have built CM before (and again, you better have!), you should be familiar with the concept of a code name for each device. Like the vendor name, the codename is always lowercase and contains no spaces.]
Where does the pulled build.prop go? and are there any specific linux programs i would need to edit this file or any other files throughout the tortorial? I have gedit installed and its met my needs so far but do i need something more advanced to accomplish my goal?
Click to expand...
Click to collapse
The vendor for our device is "samsung" and the codename is "hugo"
Just fyi...when you are in the linux terminal...whichever directory you are in is where the pulled build.prop goes.
Sent from my XT760
I know I tried t post about me rereading the guide and understanding what it meant and that i have moved further into the guide but it never posted on here but i guess this whole thing was just a waste of time.
dude you should try porting from the galaxy sl i9003 because of the similar cpu stats
you would also need to create a boot image and an odin flashable recovery v 6+
Guys, I'll rewrite the stock kernel for you for booting KitKat, just give me 1-2 weeks
has this been done yet. Not to be a stickler, but this is the holdup for advancing this device. I can port the rom, just need an updated kernel with a recovery that supports. Thanks in advance.
Related
Porting ROM from Source to Unsupported Device
I'm trying to port this ROM from this git to the Desire HD. I have ported a ROM before by replacing certain system files but this seems to be a lot more advanced. I am currently here but that is only half of what I need to do. Could anyone give me some advice or a place to begin?
cruzin_cruzing said: I'm trying to port this ROM from this git to the Desire HD. I have ported a ROM before by replacing certain system files but this seems to be a lot more advanced. I am currently here but that is only half of what I need to do. Could anyone give me some advice or a place to begin? Click to expand... Click to collapse You have to add a source for building for your device. Look in my signature for gingerbread compilation and go the bottom of the guide. Just change names of directories as needed. It is easier to port a ROM that is already compiled. Look in the supported device forums of that ROM and port one.
Creating an AOSP ROM
Hey guys! My device (the HTC One X for AT&T) currently has a CM9 and AOKP port. I really wanted to get started with developing though. I wanted to create a full AOSP ROM (directly from Google) just to learn the process and get my hands dirty with ROM development (I've already done quite a few mod packs and a kernel). We have an open sourced CM9 device tree available. I've tried using that device tree for building the AOSP ROM but of course, it has errors because the AOSP source isn't CM9... So what I'm asking is how can I use this CM9 device tree with a pure AOSP ROM? Like, how exactly do I edit the CM9 device tree so that it creates an AOSP ROM? I'm aware its no easy task, but if someone could point me in the right direction it would be greatly appreciated. I'm a noob when it comes to ROM development, I've never made one before haha I have compiled ROMs before, I maintain the AOKP nightlies for the HP Touchpad. If someone could help me make this device tree work it would be awesome. Thanks! P.S. Here is the tree in case someone wanted to look at it: https://github.com/vmagro/android_device_htc_evita
Delete cm.mk Edit vendorsetup.sh (remove "cm_"). That is all you need to do, I believe. Like you know, sync the AOSP source, include your device folder amd build. Sent from my Galaxy Nexus using Tapatalk 2
mDroidd said: Delete cm.mk Edit vendorsetup.sh (remove "cm_"). That is all you need to do, I believe. Like you know, sync the AOSP source, include your device folder amd build. Sent from my Galaxy Nexus using Tapatalk 2 Click to expand... Click to collapse I found this thread and this is exactly what I'm doing. Would you be interested in answering my questions in exchange for a nice donation? I haven't had much luck getting help and being a single parent of three toddlers I really need to maximize my free time to work on this.
You also would have to delete any offending overlays from CM that are present within your device repo. As you compile you may run into errors which you could work through. 私のEVO 3Dから送信される。
dastin1015 said: You also would have to delete any offending overlays from CM that are present within your device repo. As you compile you may run into errors which you could work through. 私のEVO 3Dから送信される。 Click to expand... Click to collapse Removing overlays doesnt work here. Have many issues regarding the kernel.
hey Good luck
rohan32 said: Hey guys! My device (the HTC One X for AT&T) currently has a CM9 and AOKP port. I really wanted to get started with developing though. I wanted to create a full AOSP ROM (directly from Google) just to learn the process and get my hands dirty with ROM development (I've already done quite a few mod packs and a kernel). We have an open sourced CM9 device tree available. I've tried using that device tree for building the AOSP ROM but of course, it has errors because the AOSP source isn't CM9... So what I'm asking is how can I use this CM9 device tree with a pure AOSP ROM? Like, how exactly do I edit the CM9 device tree so that it creates an AOSP ROM? I'm aware its no easy task, but if someone could point me in the right direction it would be greatly appreciated. I'm a noob when it comes to ROM development, I've never made one before haha I have compiled ROMs before, I maintain the AOKP nightlies for the HP Touchpad. If someone could help me make this device tree work it would be awesome. Thanks! P.S. Here is the tree in case someone wanted to look at it: https://github.com/vmagro/android_device_htc_evita Click to expand... Click to collapse Were you able to port aosp device tree from cm.Please tell me how ?
Want to start with AOSP JB 4.2 - experienced developers are welcome :)
Hi all, i want to start with AOSP 4.2 for our SGS3 i9300 - is anybody interested to develop and publish a AOSP based rom with me? I'm a real application developer (C,C++,JAVA,PHP,MySQL,some Oracle PLSQL) and now its some cold out - i have time to do some nice things I think a team of 2 or 3 developers should be enough to develop on this rom, as we can use a lot from AOSP 4.1.2 ### EDIT As long as no one has found to help, here a short description of current progress: - Code is pure based on AOSP 4.2 but some snippets of CyanogenMod to bring up hardware (camera,graphics,audio) - Device is bootable (no other boot.img required anymore) - Bootanimation is working - Mount of partitions is working - Deodexing is working - adb, debuggerd and root access is working Not working: a lot - Graphic not working perfect, needs a kernel patch or a working gralloc/hwcomposer/hwconverter to work without laggy PMEM) - Camera can not be activated due to a missing function call (undefined reference, maybe it can be solved with a newer driver) - Audio: missing speaker device (Code have to reworked to work with stagefright and tinyalsa libs) - USB/internal SDCard: cant be mounted (error message sounds like the device is mounted twice, have to find the error in init process) - RIL not working (Java file from CM10 have to be integrated in frameworks/opt/telephony) Currently, i'm working on the Graphic problem and USB part to bring up the device to a stable UI
Way to go man. Good luck to you!
Good luck ...!! Im waiting Sent from my GT-I9300 using xda premium
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
hop3l3ss1990 said: 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 Click to expand... Click to collapse 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
andy572 said: 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 Click to expand... Click to collapse 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 ^^
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.
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
andy572 said: 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 Click to expand... Click to collapse Wish i could help (just started learning JAVA ) ! gl with this awesome project
Nice to see you here, I remember you from the P500 forums.
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
slaphead20 said: 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 Click to expand... Click to collapse Thank you, it would be nice if you can contact him
andy572 said: Thank you, it would be nice if you can contact him Click to expand... Click to collapse Ok, will mention it to him
andy572 said: 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 Click to expand... Click to collapse 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.
Good Luck Dude~ I haven't tried AOSP yet. Hope someday i can give it a go.:silly:
hop3l3ss1990 said: 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. Click to expand... Click to collapse 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
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?
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. Sent from my GT-I9300 using xda premium
b-eock said: 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. Sent from my GT-I9300 using xda premium Click to expand... Click to collapse 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.
That would be the proximity sensor near the top front speaker. Cant connect, adb binary in /system/bin or xbin? Sent from my GT-I9300 using xda premium
Building Unsupported Roms
Hello there forum users! This thread was created with the sole purpose of helping me (and others) find out how to build ROMs for unsupported devices. Basically, I've built AOKP from source, but the device I was building for was already supported. What I'm trying to do now if build Dirty Unicorns 4.2.2 for my device, which is not supported by the ROM. From what I've read, I've already forked the "vendor_du", " android_device_samsung_vibrantmtd", "vendor_samsung", "proprietary_vendor_samsung", "android_hardware_samsung", "android_packages_apps_SamsungServiceMode", and "android_build". How do I build the ROM for the Samsung Vibrant T959, when it is not supported. If someone has miraculously found a post that I have missed, I would appreciate it very much. Additionally, a list of commands and explanations would greatly assist me. I'm pretty new to the whole Android building thing so I thank you all for help!
Ain't nobody is going to help you ^^ I am looking for that kind of knowledge too. I would like to start building roms from source and make some modifications to CM10's kernel
check out Legion modz team thread it has a little info on it http://forum.xda-developers.com/showthread.php?t=2314836 and make google your best friend
so much way to take...
theabnormalguy said: Hello there forum users! This thread was created with the sole purpose of helping me (and others) find out how to build ROMs for unsupported devices. Basically, I've built AOKP from source, but the device I was building for was already supported. What I'm trying to do now if build Dirty Unicorns 4.2.2 for my device, which is not supported by the ROM. From what I've read, I've already forked the "vendor_du", " android_device_samsung_vibrantmtd", "vendor_samsung", "proprietary_vendor_samsung", "android_hardware_samsung", "android_packages_apps_SamsungServiceMode", and "android_build". My github account is MaxusPrimus How do I build the ROM for the Samsung Vibrant T959, when it is not supported. If someone has miraculously found a post that I have missed, I would appreciate it very much. Additionally, a list of commands and explanations would greatly assist me. I'm pretty new to the whole Android building thing so I thank you all for help! Click to expand... Click to collapse Im starting to learn to build from source. Theres many tutorials on how to get started. Ill post links when I get to my pc later. First I would get the source code for kernel on samsung. If not available get stock rom to dump required files aswell as other files needed. I dont know if this will guide you in the right direction. Just keep in mind and always remember the kernel hardware devices is different then the operating system. You juz need to learn google how to merge the to. ---------- Post added at 08:51 PM ---------- Previous post was at 08:09 PM ---------- flipinfin said: Im starting to learn to build from source. Theres many tutorials on how to get started. Ill post links when I get to my pc later. First I would get the source code for kernel on samsung. If not available get stock rom to dump required files aswell as other files needed. I dont know if this will guide you in the right direction. Just keep in mind and always remember the kernel hardware devices is different then the operating system. You juz need to learn google how to merge the to. Click to expand... Click to collapse Heres some starting links that im using starting to build from source. the samsung open source page look for your model number http://opensource.samsung.com. Obviously. you can build your own kernel. how to unpack repack img http://forum.xda-developers.com/showthread.php?t=1081239 http://www.kandroid.org/online-pdk/guide/index.html very useful link aswell as this one http://source.android.com/source/initializing.html. heres a link to identify partition tables http://forum.xda-developers.com/showthread.php?t=1959445. . Heres another link that you prolly can pull files from if needed http://www.teamandroid.com/2013/04/...kp-build-6-android-422-jelly-bean-custom-rom/ Dont take this the wrong way but i think your getting confused how roms kernels etc r built its all open source. That rom is based off of jelly bean and alls they did was change the name. Though its open source so i would assume you can repo the rom at https://github.com/. In addition if i was you i would download the rom "which you prolly already have and do some investigating.. heres another useful link http://xda-university.com/as-a-developer/porting-aosp-roms-using-source-code. Never forget google is your best friend. Fogot to mention if you aint on linux i would switch os real soon. I think this link will be ver ver very helpful https://bitbucket.org/bigwillyg/buttered_toast_shooter Is that Vibrant T-Mobile ? cuz if it is http://aokp.co/devices/vibrantmtd theres your starting point
[Q] how to use Samsung Open Source files and JB AOSP (4.1.2_r2.1)?
Hello all, I'm trying hard to figure out how one goes about compiling Android JB AOSP (4.1.2_r2.1) platform for the samsung galaxy s2 (GT-I9100M), with the source code that samsung gives you? I've setup ubuntu 14, and I see how I can run . build/envsetup.sh, and then lunch. I get all the options to build, and I see where the saumsung scripts are located, in device/samsung. I've downloaded the open source file GT-I9100M_BMC_JB_Opensource.zip, and compiled the Kernel. Now its time to build the platform. I see the folder structure, but I see no instructions. When I unzip the Platform, I see build, external, vendor, and device, which has the folder "smdk_common". If I put all files in the corisponding locations within the AOSP, I get errors, as there's only a folder "alsa-lib". (sound drivers). And if I were to compare what's in here to whats in the AOSP device/samsung folders, there's lots more info. Do I need to copy files from the default AOSP device/samsung folders and modify to suite my needs or? Can anyone point me to how-tos? I've been trying to figure this out for days! I see a lot of how tos on building with existing ROMS, and using kitchen, etc. But I just want to build samsung from scratch FIRST...
OK, so doing a lot more research, both here and google, I obviously need to create a device tree OFF of the files that samsung has released to everyone. Surely someone has done this already? I see there are a few GIT repositories that have device trees, but they are based upon existing files, etc. I'm looking to find a device tree that has all the basics, OR a "template" one i can try and work with samsungs...
technobuddha said: OK, so doing a lot more research, both here and google, I obviously need to create a device tree OFF of the files that samsung has released to everyone. Surely someone has done this already? I see there are a few GIT repositories that have device trees, but they are based upon existing files, etc. I'm looking to find a device tree that has all the basics, OR a "template" one i can try and work with samsungs... Click to expand... Click to collapse Hi, did you succeeded in your approach to build a device tree with the Samsung-opensource-files? if yes then I'll be very interested in the way you do it as I'm on the same status for a Samsung device which has absolutely no support in the hole internet (except one thread here in XDA BR SP
No I didn't. and I got no help what so ever from the people here at xda-developers. I even approached some of the people who compile the roms, and got no response from them. I suspect the only help you'll ever get from these forums is if you ask for help from EXISTING roms, or you're an "existing" developer that has years of experience. this place is not for new developers at all. a lot of brown nosing going on here.. good luck in your search! SolarPlexus said: Hi, did you succeeded in your approach to build a device tree with the Samsung-opensource-files? if yes then I'll be very interested in the way you do it as I'm on the same status for a Samsung device which has absolutely no support in the hole internet (except one thread here in XDA BR SP Click to expand... Click to collapse
technobuddha said: No I didn't. and I got no help what so ever from the people here at xda-developers. I even approached some of the people who compile the roms, and got no response from them. I suspect the only help you'll ever get from these forums is if you ask for help from EXISTING roms, or you're an "existing" developer that has years of experience. this place is not for new developers at all. a lot of brown nosing going on here.. good luck in your search! Click to expand... Click to collapse OK, thanks for your response. Thats also my experiance more ore less I have found (with some exceptions which really try to help). So I'll try to work on it, and if I succseed, I'll make a guide... maybe it will help then others BR SP
what phone is it? and yea, if you need any help,just ask me. SolarPlexus said: OK, thanks for your response. Thats also my experiance more ore less I have found (with some exceptions which really try to help). So I'll try to work on it, and if I succseed, I'll make a guide... maybe it will help then others BR SP Click to expand... Click to collapse
Its the Samsung sg-i8200 (s3 mini value edition) The previous phone was supported very well (i8190) but the i8200 has a complete new hardwarebase and its really garbage... send with my Oneplus One (bacon) SlimKat Tapatalk