Develop Bugs

30/Jun r1 (JFB) - MoDaCo Custom ROM for Samsung Galaxy S with Online Kitchen

I'm pleased to present my MoDaCo Custom ROM for the Samsung Galaxy S! READ THIS WHOLE POST BEFORE YOU START! No, really, it contains everything you need to know. wink.gif
This ROM is the 'starting point' for my Galaxy S custom ROMs.
About MoDaCo Custom ROMs
MoDaCo Custom ROMs are based on official ROMs - either shipping or leaked. A MCR release is designed to feel as far as possible like a stock ROM, with optimisations, tweaks and complimentary additions that enhance the user experience. The aim of a MCR is to be ultra reliable for use on an everyday device.
Requirements
In order to use this ROM on your device, YOU MUST ALREADY BE RUNNING THE JFB ROM FROM HERE. Do NOT use this ROM with any other base, unpredictable things will happen, the most likely being you'll have to reflash your device via Odin.
Features Included
* Based on the JFB release
* Rooted with Superuser 2.1 by ChainsDD
* Built with the MCR build process which reduces the size and boosts the speed of the ROM
* busybox with Droid Explorer support
* Updated Google Maps
* MCR version displayed in 'About' screen
* Optional Google Voice Search
* Optional Google Voice Dialer
* Optional Fancy Widget
* Optional Beebplayer
* Optional baked in Wavesecure via the online kitchen (installed to system partition for maximum security)
Changelog
Please see 2 posts below this one for the changes in each release.
Installation
To install this ROM:
* Ensure you have the JFB ROM installed (linked above)
* Download the zip file of your choice from the links below (or the online kitchen) and copy to your SD card named 'update.zip'
* Restart your device in recovery mode by running 'adb reboot recovery' (download adb if you do not have it already, use adb-windows, adb-mac or adb-linux as appropriate)
* Select the option to apply an update zip, and select the zip file you copied to your memory card
Upgrading
No wipe is explicitly required in order to use this ROM, however if you do encounter issues of any kind, it is recommended that you wipe your device and reproduce the issue before raising it here.
Downloads
This ROM is currently only available in the online kitchen - prebakes to follow.
Thanks
It's impossible to mention everyone who contributes to the Android community by name, but to everyone out there who does great work and shares it with us all - you have my gratitude and respect.
And finally...
If you would like to show your appreciation for the ROM, please consider supporting MoDaCo by signing up for a MoDaCo Ad Free or MoDaCo Plus account, both of which also give you early access to Beta ROM releases and access to the the online kitchens.
Enjoy!
http://android.modaco.com/content/s...rom-for-samsung-galaxy-s-with-online-kitchen/

Does this ROM fix the ram issue so that all 512MB of ram is utilized?
Congrats on being the first custom rom here.

Congratulations! I don't have a phone yet but I am very pleased to see a custom rom already!

woohoo custom ROMs already. Guess I'll be getting myself the phone after all.

umm.. but in another thread people where saying that it wasn't gonna be possible because samsung encrypt their drivers etc. so this mean they did release they drivers? and there is gonna be alot of custom rooms for galaxy gravity?

Perrosky said:
umm.. but in another thread people where saying that it wasn't gonna be possible because samsung encrypt their drivers etc. so this mean they did release they drivers? and there is gonna be alot of custom rooms for galaxy gravity?
Click to expand...
Click to collapse
No I said it would be near impossible to get roms from other sources like Sense roms or Froyo on because of the driver issue. I never said you would never see custom roms. The only roms you are going to see are one's based off of Samsungs release.

Hold on, hold on. So even though Samsung released the Galaxy S' driver source code to the public, it's going to be "near impossible" to port Sense and FroYo to the phone? I may be ignorant but I'll just ask with ignorance, how do you figure?

Javalu said:
Hold on, hold on. So even though Samsung released the Galaxy S' driver source code to the public, it's going to be "near impossible" to port Sense and FroYo to the phone? I may be ignorant but I'll just ask with ignorance, how do you figure?
Click to expand...
Click to collapse
Download the source code..... ok now open it and go to GalaxyS_Kernel.tar.gz. Now in there just enter the first folder then go to modules. Go to Dpram. Open up any of those files in notepad. You should see written non-compiled code right? That is fine now go back to the module folders and go to S3cbc. Now open up s3cbc_module.o. Does that look like non-compiled code? No it doesn't. It's either already compiled or encrypted. That's what I mean

psychoace said:
No I said it would be near impossible to get roms from other sources like Sense roms or Froyo on because of the driver issue. I never said you would never see custom roms. The only roms you are going to see are one's based off of Samsungs release.
Click to expand...
Click to collapse
Quick question, does that mean any custom rom that is release will be based off the official rom they release which has Touchwiz backed in? If so, does that rule out a plain vanilla android rom for this device? Thanks for your help and appreciate the knowledge.

Papa_I said:
Quick question, does that mean any custom rom that is release will be based off the official rom they release which has Touchwiz backed in? If so, does that rule out a plain vanilla android rom for this device? Thanks for your help and appreciate the knowledge.
Click to expand...
Click to collapse
No it doesn't rule out plain vanilla android rom. Yes they will all be based on Samsung but rom makers can take out all the touchwiz garbage and throw in another launcher like adw or Launcherpro.

That's what I wanted to hear. Thanks for the help. Now if I only could decide if I should keep the Nexus One or purchase this phone..... Decisions, Decisions.

psychoace said:
Download the source code..... ok now open it and go to GalaxyS_Kernel.tar.gz. Now in there just enter the first folder then go to modules. Go to Dpram. Open up any of those files in notepad. You should see written non-compiled code right? That is fine now go back to the module folders and go to S3cbc. Now open up s3cbc_module.o. Does that look like non-compiled code? No it doesn't. It's either already compiled or encrypted. That's what I mean
Click to expand...
Click to collapse
How lame. Have other handsets had similar problems?

what are talking about .o files and unix compiled modules same on all versions of unix. o stands for object module.

Javalu said:
How lame. Have other handsets had similar problems?
Click to expand...
Click to collapse
Yes the Behold 2, the original Galaxy, and the Moment all made by Samsung have only had Samsung roms on them.
lgkahn said:
what are talking about .o files and unix compiled modules same on all versions of unix. o stands for object module.
Click to expand...
Click to collapse
So they can easily be decompiled? If it's source code why is it already compiled?

dont go too deep into specific things that we may not even need (we are not coders here) but the source code for basic hardware that we need to get things going are already there.. things like camera, wlan, etc. btw, do u know what s3cbc is for?

raspdeep said:
dont go too deep into specific things that we may not even need (we are not coders here) but the source code for basic hardware that we need to get things going are already there.. things like camera, wlan, etc. btw, do u know what s3cbc is for?
Click to expand...
Click to collapse
What about s3clcd? Here is a little copy and paste of some of the garble that was in the compiled file
screen width=%d height=%d va=0x%x pa=0x%x
I would go out on a limb and say those are video drivers. The one's that have been encrypted on all other samsung phones.
Also in s3cbc there is some code at the bottom
PVRSRV_PIXEL_FORMAT_YUY2 PVRSRV_ERROR_FIFO_SPACE char ui32ByteStride psDevInfo PVRSRV_PIXEL_FORMAT_PAL1 PVRSRV_PIXEL_FORMAT_PAL2 pfnOpenBCDevic
If you don't know the Galaxy's gpu is PowerVR SGX540 and YUY2 is a colol format for video screens
http://www.fourcc.org/yuv.php#YUY2 and Pal is of course a European video standard.

they are not encrypted, they are object codes in machine language for arm.. and why we need that again for custom roms?

Wanted to test modaco ROM but they are not free.. Any kind souls upload and share ?

well feedback on the R1 rom its clean and smooth, worked even better when i did the stall tweak posted here
http://android.modaco.com/content/s...298/got-the-stalling-problem-rooted-try-this/
the phone seriously got 2 times faster, opening apps playing game very quick .. happy as here

Ferdimage said:
well feedback on the R1 rom its clean and smooth, worked even better when i did the stall tweak posted here
http://android.modaco.com/content/s...298/got-the-stalling-problem-rooted-try-this/
the phone seriously got 2 times faster, opening apps playing game very quick .. happy as here
Click to expand...
Click to collapse
How much free ram have you got? Considering flashing and rooting, but not sure if it's worth it right now. Meh 10£ isn't that much think I'm gonna give it a try.
EDIT: Just flashed, but now I don't have root access(says access denied when I try to access the /data/data folder). Thought this included the rooted PDA file or do I have to flash that again with odin?
EDIT2: Scratch that I forgot to press the allow-button on my phone after sending the Super-user request..

Modifying Android's built-in apps

Hi guys!
I'm wondering what I'd have to do if I wanted to modify the built in apps inside Android..
I've got a HTC Hero running FroydVillain 1.5.0. Let's say... I want to modify the messaging app that's included, MMS.apk. I wouldn't know how to go about this, and I have a few questions...
Firstly, what sources exactly are used for building the built in apps for a given ROM? The source code link in the FroydVillain post, for example, is just for the kernel. The rest of the OS isn't there.
Secondly, I hear that in order to modify a built in app, you need to build the entire OS. If I just download all the code from Google official repo, and compile that, will it just... work on my phone, provided I use a kernel that is specific to my phone?
Lastly, are there any tips anyone has for someone who just wants to modify a couple of the built in apps? Is it possible to build them as standalone apps? Or import them into Eclipse?
I've had a search around the forum and the internets in general, and people have asked similear questions, but I've yet to find a good answer. This thread comes to mind: http://forum.xda-developers.com/showthread.php?t=635197
If anyone could help me, or point me in the direction of any help, that'd be awesome! Thanks!!

FunkTrooper said:
Hi guys!
I'm wondering what I'd have to do if I wanted to modify the built in apps inside Android..
I've got a HTC Hero running FroydVillain 1.5.0. Let's say... I want to modify the messaging app that's included, MMS.apk. I wouldn't know how to go about this, and I have a few questions...
Firstly, what sources exactly are used for building the built in apps for a given ROM? The source code link in the FroydVillain post, for example, is just for the kernel. The rest of the OS isn't there.
Secondly, I hear that in order to modify a built in app, you need to build the entire OS. If I just download all the code from Google official repo, and compile that, will it just... work on my phone, provided I use a kernel that is specific to my phone?
Lastly, are there any tips anyone has for someone who just wants to modify a couple of the built in apps? Is it possible to build them as standalone apps? Or import them into Eclipse?
I've had a search around the forum and the internets in general, and people have asked similear questions, but I've yet to find a good answer. This thread comes to mind: http://forum.xda-developers.com/showthread.php?t=635197
If anyone could help me, or point me in the direction of any help, that'd be awesome! Thanks!!
Click to expand...
Click to collapse
1) The whole sources for everything are there
http://github.com/ninpo
2) You can import the sources to eclipse, but I think you will need to build the entire tree, as opposed to just what you change
3) Apktool lets you do smali and resource edits on an APK. Without knowing what you aim to do, it's hard to guide you specifically.

Most apps are based on the sources provided by google. I assume you are talking about Froyo Hero ROMs (i.e. FroydVillain), which apps are generally built from the source of CyanogenMod. Specifically for FroydVillain, if you look around ninpo github you will see some packages with some changes to their code, although it does seem that many of the changes in recent releases are not there. I have actually PMed ninpo about this and hopefully this is only a technicality.... I assume that the other packages and apps (most of them) he just compiled off the CM sources without changes.
In any case, if you compile an app either from the CM source or from google's original sources, it should work just to copy the apk file - just make sure you use an appropriate ROM (i.e. Froyo ROM if you built it from Froyo sources). The reason to want the CM sources, is that if they have incorporated further fixes (over the google sources) you may want them.
Finally, some more practical advice: I would start with the google sources: http://source.android.com/source/index.html since I have found these instructions and explanations easier to begin with - it should be quite straight forward to build these sources on a linux machine (or VM).
Then you can also try to tackle the cyanogen source: http://wiki.cyanogenmod.com/index.php?title=Building_from_source currently missing instructions on how to build for hero. But if you only want to copy apks out of it, you can just build a generic build (like in the google souce).
If you have specific problems, ask and I'll try to help you.
Good luck.

pulser_g2 said:
1) The whole sources for everything are there
http://github.com/ninpo
Click to expand...
Click to collapse
For example where are all the changes to the dalvik code? I do not follow closely enough the changes in Froyd to point out other things which might be missing (if at all), but there are relatively few committed changes to the CM code. Specifically the dalvik code, ninpo mentioned hundreds of changes which caught my interest and are definitively not there.
The kernel sources do seem to be up to date always - been following that one closely .

Thanks for the advice I love this forum!
What I'm trying to do, in case you're wondering, ultimately, is to modify the built-in messaging application to give the user the option of sending a message by the normal method, or by using their provider's free webtext service, something that all the carriers seem to offer here in Ireland.
So, for example, you'd press the Send button, and you'd be able to select one of those methods. (of course, you'd have to have a data connection for the webtext). There's also be an interface for entering your login credentials for your carrier's website.
I'm doing this party because it would be very useful. I also feel that it would give me a good introduction to how you'd go about modifying Android. I mean, from a programming point of view, it shouldn't be *too* hard to do. I already have a simple standalone app that I made which can send a text message via an Irish carrier's webtext service. But it's all good experience to try to modify other people big codebases.
I have a good bit of experience with web application development, but my experience with other programming is a little more limited. I usually use PHP, where there's none of this compiling nonsense. You just write scripts and off they go!
So I'm gonna go off and see if I can set up an environment where I can build.. the OS, I guess.
If I was to take the vanilla official Google sources, would they work on my phone? Or would I have to use an official Google developer phone... or the emulator? Or maybe if I stopped writing here and investigated those links you've provided, I'd know that by know.
Brb, investigating

Yeh investigating and just trying to do it is usually the best way
To clarify what I was trying to say above: All the java code is obvious very portable - one of the big advantages of java. In the case of android it is compiled to an .apk file and this file should be, at the very least, portable to all android "devices" running this android version. So the apk you build (for example from the vanilla 2.2 sources) should work on the emulator (good for initial debugging) and any 2.2 ROMs.

erasmux said:
For example where are all the changes to the dalvik code? I do not follow closely enough the changes in Froyd to point out other things which might be missing (if at all), but there are relatively few committed changes to the CM code. Specifically the dalvik code, ninpo mentioned hundreds of changes which caught my interest and are definitively not there.
The kernel sources do seem to be up to date always - been following that one closely .
Click to expand...
Click to collapse
I'm currently on "vacation" from any and all Android development for a week. I'll be back after the weekend, at which time my modifications will be cleaned up and committed to git. The kernel is always current with my latest kernel release due to GPL obligations. The extra time away has also highlighted some changes I need to make both to the kernel and to my Android modifications when I get back.

Hacre said:
I'm currently on "vacation" from any and all Android development for a week. I'll be back after the weekend, at which time my modifications will be cleaned up and committed to git. The kernel is always current with my latest kernel release due to GPL obligations. The extra time away has also highlighted some changes I need to make both to the kernel and to my Android modifications when I get back.
Click to expand...
Click to collapse
Thanks Ninpo

Kitkat 4.4 for Defy/Defy plus (MK44.2) Mokee ROM

Moderators Note about MoKee. These ROMs in the past were known for distributing adware/malware. As they claim to be "Open Source" now, you should still be cautious about flashing MoKee ROMs. Currently this ROM is under review by Moderation Staff.
Android 4.4 Kitkat for Defy and Defy+​
This is the latest Mokee ROM for our very own and never dying cell,Motorola Defy/Defy plus(Aka.jordan/jordanplus) based on the latest android OS Kitkat 4.4.
About MoKee OpenSource:
MoKee OpenSource is based on Google AOSP and CyanogenMod Android source development of a branch,
but also the country's first complete open-source Android project, users and developers around the home.
Google open source projects follow the rapid escalation, and for the user habits, improvements and enhancements.
Magic Fun Forum December 12, 2012 launch of the project, is committed to making this form of localization of open source CyanogenMod ROM.
Open source project, any interested technical experts who can participate in the development, its contribution to the force!
Project Address: http://www.mfunz.com
Click to expand...
Click to collapse
Mfunz/Mokee os Official page http://
www.mfunz.com/
Developers http://www.mfunz.com/contributors/
Forum: http://bbs.mfunz.com
Tutorial: http://bbs.mfunz.com/
thread-653126-1-1.html
Statistics: http://stats.mfunz.com
audit: http://review . mfunz.com
Github: https://github.com/MoKee
code tracking: http://issues.mfunz.com/
code tracking - Mobile: http://issues.mfunz.com/
mobi
Open source project, any interested technical
experts who can participate in the development of
its contribution to the force!
Project Address: http://www.mfunz.com
Update recovery first then flash this:
Download :http://pan.baidu.com/s/17YFiu
Gapps:?
Here is the link from the original post:
http://bbs.mfunz.com/thread-920983-1-1.html
Change Log :http://changelog.mfunz.com/
Screenshots :

As I can see you've post the 14.12 version and not the last 16.12 version which contains many bugs repaired. Can you post the last one? THX.

Guys, but why are you still using Mokee, aren't they including malware in every ROM now? :/

niksy+ said:
Guys, but why are you still using Mokee, aren't they including malware in every ROM now? :/
Click to expand...
Click to collapse
My solution is very simple Root Explorer and delete all parts of the MoKee from /system/app

niksy+ said:
Guys, but why are you still using Mokee, aren't they including malware in every ROM now? :/
Click to expand...
Click to collapse
Those Chinese apps is not exactly malware. Because is not useful for me I've uninstalled it with Titanium and recover some ROM. Also I replace the Mokee launcher and keyboard and make a very reliable and stable OS ( 4950 pts under Antutu 4.1.4).

deffyplus said:
My solution is very simple Root Explorer and delete all parts of the MoKee from /system/app
Click to expand...
Click to collapse
Those Chinese apps is not exactly malware. Because is not useful for me I've uninstalled it with Titanium and recover some ROM. Also I replace the Mokee launcher and keyboard and make a very reliable and stable OS ( 4950 pts under Antutu 4.1.4).
Click to expand...
Click to collapse
Exactly ! )
And i also use it as i dont get battery drops like in cm10.2

pgreed said:
As I can see you've post the 14.12 version and not the last 16.12 version which contains many bugs repaired. Can you post the last one? THX.
Click to expand...
Click to collapse
On the official site i am getting 14/12 build only....if u get some link do send me,i'll add it to the post

pgreed said:
Those Chinese apps is not exactly malware. Because is not useful for me I've uninstalled it with Titanium and recover some ROM. Also I replace the Mokee launcher and keyboard and make a very reliable and stable OS ( 4950 pts under Antutu 4.1.4).
Click to expand...
Click to collapse
And how is it that it's "not exactly malware"? Is it just partially malware? Almost malware? Maybe malware? Or is a "variant of Android/TrojanDownloader.Adload.B trojan" really just not that bad?
And then when people caught on to it they also modified the keyboard app too... but nah... can't be that bad, since they are actually fixing many bugs that aren't being taken cared of by serious developers that contribute directly to XDA, right? Oh wait, their change log doesn't really reflect anything different than what's already being taken care of by other developers who are actually compiling and programming for our Defy...
As a tip, you can and should delete those apps before flashing (with 7zip), that way they aren't ever run on your phone; once you flash the first thing that will start up will be the keyboard.

Antiga Prime said:
And how is it that it's "not exactly malware"? Is it just partially malware? Almost malware? Maybe malware? Or is a "variant of Android/TrojanDownloader.Adload.B trojan" really just not that bad?
And then when people caught on to it they also modified the keyboard app too... but nah... can't be that bad, since they are actually fixing many bugs that aren't being taken cared of by serious developers that contribute directly to XDA, right? Oh wait, their change log doesn't really reflect anything different than what's already being taken care of by other developers who are actually compiling and programming for our Defy...
As a tip, you can and should delete those apps before flashing (with 7zip), that way they aren't ever run on your phone; once you flash the first thing that will start up will be the keyboard.
Click to expand...
Click to collapse
that it is also possible

Antiga Prime said:
And how is it that it's "not exactly malware"? Is it just partially malware? Almost malware? Maybe malware? Or is a "variant of Android/TrojanDownloader.Adload.B trojan" really just not that bad? ... be the keyboard.
Click to expand...
Click to collapse
maybe the correct term is adware? For the rest: I found that ROM to be the most stable, battery efficient and with all the settings I need. 'till now the rest of 4.3 custom ROMs do not comply with the above needs and the 4.4.x is not enough mature. The only problem with Mokee 4.3 is that SistemUI slowly growing which suffocate the RAM and need periodical reboot -but that appear to be common to 4.3.x . Those grow seems to be closely related to apps installation and update.
---------- Post added at 08:09 PM ---------- Previous post was at 08:00 PM ----------
abhinavvaidya90 said:
On the official site i am getting 14/12 build only....if u get some link do send me,i'll add it to the post
Click to expand...
Click to collapse
Hm .. the 16.12 version seems not to be public yet!

pgreed said:
maybe the correct term is adware? For the rest: I found that ROM to be the most stable, battery efficient and with all the settings I need. 'till now the rest of 4.3 custom ROMs do not comply with the above needs and the 4.4.x is not enough mature. The only problem with Mokee 4.3 is that SistemUI slowly growing which suffocate the RAM and need periodical reboot -but that appear to be common to 4.3.x . Those grow seems to be closely related to apps installation and update.
Click to expand...
Click to collapse
Hardly the point. First of all, the fact that they have to hide it in an app most people will need to start up the ROM is shady at best. Second of all, regardless of how AV companies label the malicious software they find, a trojan downloader is essentially a backdoor for the app developer to open it and to deliver a payload that can behave differently than just "adware", without the user's consent or knowledge. That fact alone should make people think twice before installing/using this ROM, especially once people are aware that the developer's intentions are not necessarily intentions that promote the improvement and development of Android.
People can choose what they want, just my two cents on why we are tolerating malware, adware, trojans, or whatever you want to call it. There are a lot of people who also frequent these forums who won't know how to delete the malicious apps before flashing, regardless of whether they should be able to or not.
It's different when you have to mod things to your liking or to improve functionality, but hidden and persistent malware/adware placed by the developers themselves...?
We shouldn't have to tolerate that...

Antiga Prime said:
Hardly the point. First of all, the fact that they have to hide it in an app most people will need to start up the ROM is shady at best. Second of all, regardless of how AV companies label the malicious software they find, a trojan downloader is essentially a backdoor for the app developer to open it and to deliver a payload that can behave differently than just "adware", without the user's consent or knowledge. That fact alone should make people think twice before installing/using this ROM, especially once people are aware that the developer's intentions are not necessarily intentions that promote the improvement and development of Android.
People can choose what they want, just my two cents on why we are tolerating malware, adware, trojans, or whatever you want to call it. There are a lot of people who also frequent these forums who won't know how to delete the malicious apps before flashing, regardless of whether they should be able to or not.
It's different when you have to mod things to your liking or to improve functionality, but hidden and persistent malware/adware placed by the developers themselves...?
We shouldn't have to tolerate that...
Click to expand...
Click to collapse
Completely agree with you. Personally I think this ROM should be banned from XDA, where piracy and even promoting your paid themes isn't allowed. For me it is unimaginable that a trojanned ROM can be posted. discussions about how easy it is to remove don't matter, like you said. Hence I have reported to the mods.
@ others: Yes people can choose what they want, like antiga said, but on XDA the choice of installing trojans shouldn't even exist. There are shadier websites one can visit to get their trojan fixes.

Thread currently closed
Ok, 2 things.
1) Thread moved to General, as it's just links to the MoKee site, as it appears the OP is not an official maintainer, and just posted links. As such it does not qualify as development.
2) Thread is currently closed pending investigation of current MoKee practices.
In the past MoKee had been known to included adware in their apps. Did they include Malware? Depends who you talk to. However, MoKee was discouraged at XDA, along with MIUI ROMs which also operate under a similar principle.
However, MoKee claims to be "Open Source" and their github seems to reflect that.
It is advisable however, to remove any suspicious apk's just to be safe until a disposition is made. And considering it's a Chinese ROM with a past reputation, might want to change keyboard apk's as well
Thread closed for the time being.
MD

Jb 4.1.2 aosp

I have been learning how to work in the android environment for a little while now, and want to move onto learning how to create roms from AOSP rather than other peoples existing work. This would allow a lot more freedom. The current dream is to create a JB 4.1.2 rom from AOSP, then release it as a base rom to allow anyone else to rip it up just as they want. Once developed it could be used to show examples of how to use apktool and others to customise your own rom.
Potentially the process could be documented here so that other people could build there own. I don't know how many people still use this phone, but it would be a good learning process.
So is anyone else interested? Currently I know next to nothing so we would be starting from there

I
mcgi5sr2 said:
I have been learning how to work in the android environment for a little while now, and want to move onto learning how to create roms from AOSP rather than other peoples existing work. This would allow a lot more freedom. The current dream is to create a JB 4.1.2 rom from AOSP, then release it as a base rom to allow anyone else to rip it up just as they want. Once developed it could be used to show examples of how to use apktool and others to customise your own rom.
Potentially the process could be documented here so that other people could build there own. I don't know how many people still use this phone, but it would be a good learning process.
So is anyone else interested? Currently I know next to nothing so we would be starting from there
Click to expand...
Click to collapse
I'm up.. :thumbup:

MScorporation95 said:
I
I'm up.. :thumbup:
Click to expand...
Click to collapse
Awesome, as a progress report I have so far managed to download and install the sdk, with JB4.1.2 APIs. Next I'm going to read, this is going to be a nice slow burner.

mcgi5sr2 said:
Awesome, as a progress report I have so far managed to download and install the sdk, with JB4.1.2 APIs. Next I'm going to read, this is going to be a nice slow burner.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2091353

MameTozhio said:
http://forum.xda-developers.com/showthread.php?t=2091353
Click to expand...
Click to collapse
Super! Thank you

@mcgi5sr2
Thanks! Good idea!!! :victory:
I believe you already know about that, but just in case:
- Guide Ride-From a Newbie to a Dev: http://forum.xda-developers.com/showthread.php?t=2281656
- Complete Android ROM development and essential tutorials: http://forum.xda-developers.com/showthread.php?t=1661770
- Rickys Rom Kitchen 2.0/Android Everything Tool 10.0: http://forum.xda-developers.com/showthread.php?t=2200660

bratusm said:
@mcgi5sr2
Thanks! Good idea!!! :victory:
I believe you already know about that, but just in case:
- Guide Ride-From a Newbie to a Dev: http://forum.xda-developers.com/showthread.php?t=2281656
- Complete Android ROM development and essential tutorials: http://forum.xda-developers.com/showthread.php?t=1661770
- Rickys Rom Kitchen 2.0/Android Everything Tool 10.0: http://forum.xda-developers.com/showthread.php?t=2200660
Click to expand...
Click to collapse
Thanks Bratusm,
I am still dreaming of a Vanilla for as many Androids versions as I can muster, however I have been informed it is a complete nightmare for our device, so the first step I am taking will be learning to build CM10, if I can get anything like the stability Lloir and Maxwen got, I'll use that learning to go forward, either with a Slim build or another. I doubt I will release much work as it will fall short of what others have achieved, but I will be available to help others as I learn along the way. I am already thinking of adding a what is tutorial for the SlimRom I've messed with, along with a guide to apks compiling and decompiling. The idea is to make an easy route for anyone who wants to learn what I have so far, and then they can take it and smash up other peoples roms to there hearts contents just like me

mcgi5sr2 said:
Thanks Bratusm,
I am still dreaming of a Vanilla for as many Androids versions as I can muster, however I have been informed it is a complete nightmare for our device, so the first step I am taking will be learning to build CM10, if I can get anything like the stability Lloir and Maxwen got, I'll use that learning to go forward, either with a Slim build or another. I doubt I will release much work as it will fall short of what others have achieved, but I will be available to help others as I learn along the way. I am already thinking of adding a what is tutorial for the SlimRom I've messed with, along with a guide to apks compiling and decompiling. The idea is to make an easy route for anyone who wants to learn what I have so far, and then they can take it and smash up other peoples roms to there hearts contents just like me
Click to expand...
Click to collapse
:highfive::highfive::highfive:

bratusm said:
:highfive::highfive::highfive:
Click to expand...
Click to collapse
One step closer, just built my first CM10 from source, using Maxwens and Lloirs work. There is always hope that I will be able to pull off more. tbh I'll be sitting down with some pen and paper and drawing out a map of what the blazes everything is next!

For when a Replicant ROM for this mobile phone?

Hi.
Like me, people that own this mobile phone need to wait for huge efforts from people like Arco to develop a ROM with the last android version and the whole bug fixes and improvements of the OS.
After all that, we need to trust what developers could have done inside that same ROM, the same we get in this 'black market' and pray they didn't do any kind of malicious developments, this, if the source code/blobs didn't come with them already. Forgetting about the security side, if we look at the new features and upgrades of the same OS, again, we will need to wait for people like Arco to get time to develop all we want. So, my question is:
What need to be done for people that use this mobile phone to have the Replicant Android version?
Web references:
- replicant.us
- fsf.org/blogs/community/donate-to-replicant-and-support-free-software-on-mobile-devices
- linux.com/news/embedded-mobile/mobile-linux/759834-fully-free-android-rom-advances-to-jelly-bean/?&co=f000000013912s-1248979074
- wired.com/wiredenterprise/2013/10/replicant/
:good:

vcatpt said:
Hi.
After all that, we need to trust what developers could have done inside that same ROM, the same we get in this 'black market' and pray they didn't do any kind of malicious developments, this, if the source code/blobs didn't come with them already. Forgetting about the security side....
Click to expand...
Click to collapse
Seriously, do you expect this to be different with a Repilcant ROM?
There will be still a Dev behind this who will compile the ROM, add bugfixes and so on.
So if you are afraid of malware being added by a Dev, you can simply download the sources and compile your own ROM. No matter this is CM or Repilcant.
CM is open source and you can watch the entire code to what a Dev has done to it. There is no conspirancy and there is no need to become paranoic.
Therefore I do not see a single reason why a Replicant ROM should be better compared to Arcos CM releases.

I can't explain me better than the references I post in the first post. But for sure, if every project follow the philosophy that Replicant uses, development could improve so much about the SECURITY and so much about the TIME for the news features/improvements, is ridiculous what people need to wait to get an upgraded software (no question about any developer here ofc). And I know life is not perfect, but at some point things need to be done in a credible and systematic way, and this android variant with the name Replicant seems fine to me.
honeyx said:
Seriously, do you expect this to be different with a Repilcant ROM?
There will be still a Dev behind this who will compile the ROM, add bugfixes and so on.
So if you are afraid of malware being added by a Dev, you can simply download the sources and compile your own ROM. No matter this is CM or Repilcant.
CM is open source and you can watch the entire code to what a Dev has done to it. There is no conspirancy and there is no need to become paranoic.
Therefore I do not see a single reason why a Replicant ROM should be better compared to Arcos CM releases.
Click to expand...
Click to collapse

hum..
http://redmine.replicant.us/projects/replicant/wiki/SamsungGalaxyBackdoor
https://www.fsf.org/blogs/community/replicant-developers-find-and-close-samsung-galaxy-backdoor