Hi guys.
While surfing the Internet I found the open source page Samsung (do not know if you already knew about it.). In it, is the official source code for Stock ROM of all editions of the GT-S5830 (L / I / M ...)
And there is something curious, there is a source code for of a S5830V ROM. I do not know that phone is, but this is not code for Android 2.3 is for Android 4.0. To know where I'm going.
Useful?. I hope so. :fingers-crossed:
If the code is to be useful, it will be possible to develop Custom ROM more stable and fully functional. :victory: Just need a good developer invest some of your time to take a look at, something that would be greatly appreciated and if I can with a good donation.
http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=S5830
There's also many other models like the SIII / II / I, Y, S5550, etc, etc, etc
PS: Excuse my English, Google Translate I speak Spanish
Yeah, but most of Galaxy Ace here are the pure GT-S5830
I think he means that since the hardware is about the same we may able able to use some of the source code and code from the drivers to make a fully working CM9 for the GTS5830
Sent from my GT-S5830 using xda app-developers app
Yes. in fact, I think the only difference between an edition and another is just the modem, the bands used for mobile network.
Not sure, but seriously believe that these sources will serve to create fully functional CM9.
Please share
Ok, I don't know if this is important, but I found it on the README_Kernel file:
$ cd kernel/common/
$ make ARCH=arm bcm21553_cooperve_defconfig
$ make ARCH=arm CROSS_COMPILE=../../prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi- modules zImage -j`grep processor /proc/cpuinfo | wc -l`
Click to expand...
Click to collapse
BCM21553_Cooperve is the chipset of those C, M and I models, a.k.a Cooperve
I have this phone i bought it in australia lockd to vodafone network i manged to unlock it through them i posted here http://forum.xda-developers.com/showthread.php?t=1902313
I spoke to the samsung customer service rep who put me on hold to speak to the tech department he got back to me and said the V has the same chipset as the 5830i different only in the band
Im trying to flash the 5830i stock firmware throught odin and havnt done it yet
Definitely looks promising!
Downloading the code, i'll try to inspect it. ForceF said it had kernel version 140, afaik 5830is only have kernel 126
I downloaded it time ago,the kernel is for Gingerbread 2.6.35.7
The config is CooperVe for Galaxy Ace V
The config for Galaxy Ace I is totoro (Galaxy Y)
Why would they call it ICS if it's a GB build, wtf samsung :\
ZakooZ said:
Why would they call it ICS if it's a GB build, wtf samsung :\
Click to expand...
Click to collapse
Could have been a mistake...
POTATO!!!!
Related
[Q] [DEV]Wifi Monitor Mode successed on SGS2&Nexus! How about SGS3?(with source code)
Finally someone get sysfs injection successed.......
with the hard work, now SGS2 and Nexus is tested fine......
and here is the project site
http://bcmon.blogspot.co.il/
it mentioned that other phones can also compile a .ko from source code and test.........
I am curious if SGS3 can also use it.......
I know now Cyanogen is still not stable for S3, ITS NOT A GOOD CHOICE FOR S3
However I havn't compile a .ko for (siyah for s3), actually I also failed to compile another module for siyah before (nsio.ko)........I stuck with siyah...= =''
seems I got problem for this.......I dont have enough experiment on android dev, but sounds like this monitor mode injection may have chance to work on SGS3?
Anyone also try it?
IF success plz share the ideas......
"ITS JUST THE BIGGEST NEWS HAPPENS THESE DAYS"
these are mentioned in the post:
Other phones
Check out the source from http://code.google.com/p/bcmon/source/checkout
Build the KO for your device (cyanogen wiki should be helpful)
If it works please tell us and send us the compiled version so we can list it here (if it doesn't work contact us)
AirCrack binaries
We bundled useful binary executables for arm:
aircrack-ng suite
tcpdump
iwconfig
FAQ
I get "Can't find wireless tools, exiting."
Solution: Make sure you have 'iwpriv' on your system, just add soft link from 'iwpriv' to 'iwconfig' (actually it is 'iwmulticall')
available on: http://bcmon.googlecode.com/svn/trunk/bundles/utils.zip
Unzip them and run: 'chmod a+x -R aircrack misc'
Update: We added a statically linked version of aircrack-ng suite.
Now you can have fun with commands like: 'airodump-ng -i eth0'
Click to expand...
Click to collapse
ynlinchen said:
Finally someone get sysfs injection successed.......
with the hard work, now SGS2 and Nexus is tested fine......
and here is the project site
http://bcmon.blogspot.co.il/
it mentioned that other phones can also compile a .ko from source code and test.........
I am curious if SGS3 can also use it.......
I know now Cyanogen is still not stable for S3, ITS NOT A GOOD CHOICE FOR S3
However I havn't compile a .ko for (siyah for s3), actually I also failed to compile another module for siyah before (nsio.ko)........I stuck with siyah...= =''
seems I got problem for this.......I dont have enough experiment on android dev, but sounds like this monitor mode injection may have chance to work on SGS3?
Anyone also try it?
IF success plz share the ideas......
"ITS JUST THE BIGGEST NEWS HAPPENS THESE DAYS"
these are mentioned in the post:
Click to expand...
Click to collapse
Sounds promising..
Sent from my GT-I9300 using xda premium
Since galaxy s2 is using broadcom4330,so is s3, we may give a hope on it!
Just like the Xpera P & Sola I've also considered to make a Thread....for the Port Jelly Bean to Galaxy Ace 2 from Galaxy SIII Mini :fingers-crossed:
It's know that our Galaxy Ace 2 is a device with Novathor u8500 SoC chipset
and right now, i'm pretty sure that Samsung will provide Jelly Bean for our device next year. But, we also know that there out is a device with our same chipset and Jelly Bean at launch. Yes, i'm talking about Samsung Galaxy SIII Mini. I have been talking with some users on their forum and i think some information can help us to port jelly bean to our Galaxy Ace 2
So, here are some files which can help us to make a working Jelly Bean Rom on our device:
1. I want to thanks nixonik member to provide a full system dump of SGSIIIMini in here System dump.
https://docs.google.com/file/d/0B-S6...d6cDVsb00/edit
2. Jelly Bean open source code for this rom, provided by Samsung.
in HERE http://d-h.st/c1n
Now that would be really great if some devs step up to initiate this.
You might get some More Info/Help at the Guys at Xperia U,Sola,P,Go threads
Xperia U thread - http://forum.xda-developers.com/showthread.php?t=2055883
Xperia P thread - http://forum.xda-developers.com/showthread.php?t=2057087
Xperia Sola - http://forum.xda-developers.com/showthread.php?t=2047945
Xperia Go - http://forum.xda-developers.com/showthread.php?t=2058766
Awesome awesome AWESOME...now this is some great news..let's show the galaxy w users what ace 2 is worth
EDIT: And be4 ppl start wondering and sayin stuff I said that cuz I had read some complaints on galaxy w forums about w deserving jb more than ace2
Thread cleaned.
Kindly do not flame the OP for opening collaboration projects which benefit the community.
Thanks,
Jonny
I think Ace 2 and SIII Mini's SoC are not EXACTLY alike but many of us expected to use the SIII Mini for the ongoing project of porting AOSP Jelly Bean to Ace 2 but we've had no luck since many believed that SIII Mini won't help that much with the port so the project has been stalled and we've been waiting for at least an update to the S Advance (or at least a leak we could port) or an official Ace 2 update. I don't really know where this is going but I don't really have my hopes up for Jelly Bean on Ace 2, well at least not until next year.
Dr01nE said:
I think Ace 2 and SIII Mini's SoC are not EXACTLY alike but many of us expected to use the SIII Mini for the ongoing project of porting AOSP Jelly Bean to Ace 2 but we've had no luck since many believed that SIII Mini won't help that much with the port so the project has been stalled and we've been waiting for at least an update to the S Advance (or at least a leak we could port) or an official Ace 2 update. I don't really know where this is going but I don't really have my hopes up for Jelly Bean on Ace 2, well at least not until next year.
Click to expand...
Click to collapse
We just need someone to modify the ram disk.
Sorry if i spam, but when JB is a problem for now, what abou ICS port?
Sent from my GT-I8160 using Tapatalk 2
forbidden8 said:
Sorry if i spam, but when JB is a problem for now, what abou ICS port?
Sent from my GT-I8160 using Tapatalk 2
Click to expand...
Click to collapse
Since jelly bean can't be ported...how is ics supposed to?(I guess)
mojito0 said:
Since jelly bean can't be ported...how is ics supposed to?(I guess)
Click to expand...
Click to collapse
Bcoz other device's, like xperia u and other xperia phones. They have same hardware like Ace2.If the S3 mini is not... dont know; just thinking.
Sent from my GT-I8160 using Tapatalk 2
forbidden8 said:
Bcoz other device's, like xperia u and other xperia phones. They have same hardware like Ace2.If the S3 mini is not... dont know; just thinking.
Sent from my GT-I8160 using Tapatalk 2
Click to expand...
Click to collapse
Ahh yeah sorry you're right, xperia u only has ics and not jb, my bad
That wouldn't work, their kernels are different, their libs, drivers, RIL interface and wrappers are also different. They don't even use the same chipset model and have a totally different board configuration with different components. Their specifications may appear to be similar on paper but it's a different story when it comes to internals.
And Jelly Bean requires Kernel 3.x, it's something that we don't have for the Ace 2 yet and porting a whole kernel from another device running the same chipset is almost impossible. Without kernel 3.x a whole load of things won't work, that obviously includes Vsync (which is totally incompatible with the current Kernel 2.6). We don't even have the device-specific JB sources for the Ace 2 so a lot of things won't work even if someone gets JB booting. Basically what needs to be done:
(1) Get it to boot with a custom 2.6 kernel/experimental 3.0.x (if built)
(2) Fix primary/critical hardware-specific code for the novathor chipset (display, audio)
(3) Fix RIL
(4) Fix secondary hardware (sensors, bluetooth, wifi)
(5) Fix camera HAL
Gonna be hard without the device sources.
Thanks for this little explanation yowanvista and yes it is gonna be hard and what about galaxy advance ? is this devise really different from ace 2 ?
yowanvista said:
That wouldn't work, their kernels are different, their libs, drivers, RIL interface and wrappers are also different. They don't even use the same chipset model and have a totally different board configuration with different components. Their specifications may appear to be similar on paper but it's a different story when it comes to internals.
And Jelly Bean requires Kernel 3.x, it's something that we don't have for the Ace 2 yet and porting a whole kernel from another device running the same chipset is almost impossible. Without kernel 3.x a whole load of things won't work, that obviously includes Vsync (which is totally incompatible with the current Kernel 2.6). We don't even have the device-specific JB sources for the Ace 2 so a lot of things won't work even if someone gets JB booting. Basically what needs to be done:
(1) Get it to boot with a custom 2.6 kernel/experimental 3.0.x (if built)
(2) Fix primary/critical hardware-specific code for the novathor chipset (display, audio)
(3) Fix RIL
(4) Fix secondary hardware (sensors, bluetooth, wifi)
(5) Fix camera HAL
Gonna be hard without the device sources.
Click to expand...
Click to collapse
oh my god! .... Jelly bean was working on motorola defy with 2.6 kernel and TOTALLY LOCKED bootloader....
espaciosalter20 said:
oh my god! .... Jelly bean was working on motorola defy with 2.6 kernel and TOTALLY LOCKED bootloader....
Click to expand...
Click to collapse
Sure it can, even my i9001 works with CM10 but Vysnc is broken (and will always be unless a proper Kernel 3.0.x is used). However it seems pointless to use a dated kernel with a whole load of compatibility patches and reverse wrappers here and there just to fill the gaps. It would be better to use a fully fledged Kernel 3.X with everything already set in place, proper drivers and libs without having to look elsewhere trying to port & adapt specific code for the Ace 2. We'll have the official JB sources next year so it's useless to hit your head against a wall trying to figure out how to make a half-baked kernel without the required pieces of code. With the new sources development will be easier, porting CM10.1 will easier too, it's better to wait imho.
JB for Galaxy S Advance is now available
i think this might help. Galaxy S Advance is now receiving JB update. DOWNLOAD LINK
Here's the news: LINK
Only **** ! nice !!!
we still don't have kernel sources to work on it;
mkel91 said:
we still don't have kernel sources to work on it;
Click to expand...
Click to collapse
samsung release source i9070 in opensource samsung web
Sent from my GT-I8160 using xda premium
hafidzduddin said:
samsung release source i9070 in opensource samsung web
Sent from my GT-I8160 using xda premium
Click to expand...
Click to collapse
I found only gb sources on the opensource.samsung website. Where you saw jb sources?
strofo said:
I found only gb sources on the opensource.samsung website. Where you saw jb sources?
Click to expand...
Click to collapse
i9070 is s advance not our devices. but we can use it
cocafe tell me he got i9070 source kernel jb
Sent from my GT-I8160 using xda premium
soo what exactly is this new kernel? I can't find changelogs anywhere, just the file to download o:
Hi all,
i'm a noob to android, but i have nit of experience on other unix based systems.
I was wondering, why there is no custom roms for GT-S5690?
What's the problem?
Is bootloader locked some other way or is it somehow different from example Gio/GT-S5660?
There is a bunch of roms for gio..
I have one xcover, wich has no screen and covers, i thought i could use it for testing.
I think there are too less people who have a xcover, and I was actually pretty disappointed when I say there is a successor to the xcover available only in the US (Rugby Smart / Pro <-- with ICS!).
From the technical side, I don't know. Even the source code of the firmware is available at opensource.samsung.com. The Bootloader seems pretty much unlocked.
For me, the xcover is the best phone ever, it takes so much abuse. Maybe someday someone will port a newer ROM from the Ace/Gio/idk. It's a shame Samsung abandons their old phones :crying:
xkawer said:
I think there are too less people who have a xcover, and I was actually pretty disappointed when I say there is a successor to the xcover available only in the US (Rugby Smart / Pro <-- with ICS!).
From the technical side, I don't know. Even the source code of the firmware is available at opensource.samsung.com. The Bootloader seems pretty much unlocked.
For me, the xcover is the best phone ever, it takes so much abuse. Maybe someday someone will port a newer ROM from the Ace/Gio/idk. It's a shame Samsung abandons their old phones :crying:
Click to expand...
Click to collapse
I didn't were aware of successor models, now i'm very dissappointed.
I'm downloading these source codes at the moment, i'll check these out.
I'm not a developer, atleast YET..
AFAIK, hardware of s5690 is way different from any other samsung phones,
correct me if i'm wrong..
jonezy82 said:
AFAIK, hardware of s5690 is way different from any other samsung phones,
correct me if i'm wrong..
Click to expand...
Click to collapse
Seems like it's the only one with a Marvell MG2.
Let me know if you do anything interesting with the sources
Just flashed my xcover to XXLJ2 yesterday. At least it seems a bit faster now, but I have a weird bug when scrolling. If I give a list (for example settings) momentum, it doesn't stop when I put my finger on it again. But it does stop if I release the finger the second time.
jonezy82 said:
I'm downloading these source codes at the moment, i'll check these out.
Click to expand...
Click to collapse
Did the same. The GT-S5690_Platform.txt says:
Code:
How to build platform
1. Get android open source.
: version info - Android gingerbread 2.3.6
( Download site : http://source.android.com )
2. Remove external\webkit module in android open source which you got.
And then execute "clean build"
2. Copy files and modules to original Gingerbread source tree (overwrite)
3. build
- ./build.sh user
So wouldn't it be possible to download the JB sources, and compile them with the original kernel? Would be so cool.
Edit: It seems you need device specific binaries (drivers) since ICS. see: http://www.freeyourandroid.com/guide/compile-ics
Found a git https://github.com/manakeri/android_device_samsung_xcover, there is a
Code:
cyanogen_xcover.mk
file, this seems interesting. Apparently someone is trying to port it.
Edit2: In this git, there is also a "extract-files.sh"-file, which is neccessary to pull the proprietary files from the phone! With this I think we actually have everything we need to compile ICS/JB, like in the "freeyourandroid" tutorial.
I have never done this before, but someone must try it lol.
Oh look, there are more people who care about it!
http://www.droidevelopers.com/f338/14412-gt-s5690-opensource-kernel-available.html
Someone discovered my link and made a overclock kernel from the sources! This is so cool.
I hope we are going to see more :good:
xkawer said:
Oh look, there are more people who care about it!
http://www.droidevelopers.com/f338/14412-gt-s5690-opensource-kernel-available.html
Someone discovered my link and made a overclock kernel from the sources! This is so cool.
I hope we are going to see more :good:[/QUOTE
I own an xcover too a developer on another forum looked at some files i pulled using adb to try to port clockworkmod but no success. Told me the files i sent weren't standard android img but he would continue to look into it. Apparently the teamhacksungs goal is to port cyanogenmod for every Samsung device surely they can get it done. I've been waiting a long time to see some development for the awesome xcover
Click to expand...
Click to collapse
If its possible on the galaxy mini its got to be possible on xcover!. Ive tried to get involved and learn to port cyanogenmod but when it comes to git, repo, source tree, source code e.t.c e.t.c its a bit behond me for now.
Step in the right direction it seems. Fingers crossed
Hi,
I am trying to port a stable release of CM10 from Galaxy S3 to Galaxy S2 HD LTE (SHV-E120S) ... :cyclops:
But i'm facing a problem...i was able to port it and the device booted too...but the camera does not show anything....it simply shows a black screen....thats it...
I have not tested it much coz that was the first application i started and it didn't work quite well.
Then I installed the 4.3 Gallery/Camera which worked but only the camera worked. When I switch it to video mode it shows me a blurred screen...but when i played the recorded video, it actually was very clear...only the display has a fault while shooting video.
So basically, is there anyone who can tell me why am I getting a black screen...
First I thought there could be some problem with the S3 ROM itself....but since it was a stable release I dont think the S3 rom has a problem...
So it would be great, if any one could point me to the right direction....
Thanks friends...
AOSP camera's dont work perfectly on the S3 anyway.
Rather than porting, you would be better trying to build source using a device tree from your device. Surely there already exists AOSP source code for it?
"porting" rarely yields expected results.
Hi rootSu,
So if I port CM10 from some other device (other than the SGS 3) do you think that will work...(for eg. SGS II I9100)
Coz I really need a CM10 for my device....that stock is simply a battery/performance hogger...
Thanks.
rootSU said:
AOSP camera's dont work perfectly on the S3 anyway.
Rather than porting, you would be better trying to build source using a device tree from your device. Surely there already exists AOSP source code for it?
"porting" rarely yields expected results.
Click to expand...
Click to collapse
Shrewdy said:
Hi rootSu,
So if I port CM10 from some other device (other than the SGS 3) do you think that will work...(for eg. SGS II I9100)
Coz I really need a CM10 for my device....that stock is simply a battery/performance hogger...
Thanks.
Click to expand...
Click to collapse
When you talk about porting, do you mean not compiling from source code? Perhaps using something like disxda kitchen's piorting fucntion? Or do you have a Linux build server which you will use for compiling code?
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.