Hello peeps,
I see there is not much activity going on between the users of Fit.
I need a list of all the people who are here and using the fit phone.
Members try to participate actively and help get past the Low Activty Barrier
Also, I wanna know who is ready to do what. These are the perspectives what I am looking for. Users can sign up for multiple posts also!
->Kernel Developement Team
-> Custom ROM Developers
-> Maintainers of Custom ROM and Helpers
-> Beta Testers
-> Mods Informer
-> Theme Creator
-> THeme Porter
-> Rom Testing
-> Custom ROM testing
-> Problem Fixes Testing
-> Doubt-clearance Member
-> DEV. Teacher!
As A initiative, I am also creating a Twitter account. Anybody who would like to create a Facebook Group for the phone's DEV and Testing team is free to do so!
Please Enroll your name below and tell us what time can you spend for what purpose!
Please Help Fit have a Bright Future! Please E-Mail us your Selected Criteria. I will add you to the mailing list. You can get all teh information on what the DEVs. are working about and stuff!
The E-mail Address of the Fit DevTeam-> [email protected]
Twitter ID-> @dev_GalaxyFit
Follow us on Twitter for all the updates on Developments
Regards,
Rohan Mallya.
I sign up for
->Custom Rom DEV.
-> Maintainers of Custom ROM and Helpers
->Mods Informer
Ok i want to be kernel developer and doubt clearance but i have to learn to develop kernel
omarhasan76 said:
Ok i want to be kernel developer and doubt clearance but i have to learn to develop kernel
Click to expand...
Click to collapse
Take your time! And, share the sources from where you are learning! Follow us on Twitter
I sign up for
->Beta tester
->ROM and Custom ROM tester
->Doubt Clearance member
Will add up responsibilities as and when I learn
spike1902 said:
I sign up for
->Beta tester
->ROM and Custom ROM tester
->Doubt Clearance member
Will add up responsibilities as and when I learn
Click to expand...
Click to collapse
Thank yoU!
Follow us on Twitter.
If you want, Just e-mail us your real name and your designation! You will be updated with amazing stuff and things
Sticky'd the the thread for you, good luck with Development.
Also for help with kernel development try my good friend Doomlord.
http://forum.xda-developers.com/member.php?u=2784807
->Beta tester
->ROM and Custom ROM tester
and whatever i learn in the process
Kernel Development
This is a general guide for building kernels and modifying them. Device-specific articles for getting the kernel source and setting up the build environment are provided in their respective sections.
Getting the kernel source
The source for your kernel must be made available by your device's manufacturer in order to comply with the GPL.
I dont know where to get it
Setting up the environment
Instructions for setting up the development environment should be included in your source code package. This should tell you the parts of the Android Open Source Project that must be in your working directory in order to allow the kernel to build. It will tell you what version as well. All of the Android Operating System source code is available at [android.git.kernel.org] and most projects are mirrored at [github.com/android]. Both are accessible via your internet browser as well as git.
Modifying the kernel
After the kernel source has been downloaded and your environment is set up, you can begin modifying the kernel. It is recommended (in most cases mandatory) that you run the standard "make xxx_defconfig" for your device before modifying the configuration.
Running
make
or
make -jX [where X is the number of operations to perform at a time]
at this point will make the stock kernel that your phone's official system has. To modify it, we can go two ways: 1) modify the file '.config' in a text editor, or 2) run
make menuconfig
for a graphical interface.
Modifying '.config' with menuconfigEdit
Typing
make menuconfig
will bring up the aforementioned graphical interface for modifying your kernel. Striking the "y" key when an option is selected (with "< >" or "[ ]" before it) will include it in the kernel. Striking the "m" key will add those options with a "< >" as a Linux kernel module (*.ko).
Adding tethering support (netfilter/iptables)Edit
Adding VPN support (TUN)
Adding Linux swap support
Adding ext3/ext4 support
Mofifying '.config' manually
The alternative to using menuconfig is editing '.config' in your preferred text editor. Options that are not to be included in the build are commented out with a "#". Options that are to be included inside the kernel image are uncommented and have the value of "y". Options with the value "m" are to be built into loadable kernel modules.
Adding tethering support (netfilter/iptables)Edit
Adding VPN support (TUN)Edit
Adding Linux swap supportEdit
Adding ext3/ext4 supportEdit
Packaging and flashing your kernelEdit
Additional stepsEdit
You may find that you want to play around with '.config', but don't want to lose your configuration. You can rename your '.config' to whatever you want and give it the suffix "_defconfig" and put it in "arch/arm/configs/" for the next time you wish to use it.
For example: if you had a kernel that had tethering and ReiserFS support, and you wanted to try enabling VPN without breaking your current setup, you could rename your '.config' to 'my_rfs_tethering_defconfig' and move it to "arch/arm/configs/". The next time you wanted to make this kernel you could run
make my_rfs_tethering_defconfig
and have your kernel configuration just as you left it.
Note that this would overwrite your kernel configuration stored in '.config'
omarhasan76 said:
Kernel Development
This is a general guide for building kernels and modifying them. Device-specific articles for getting the kernel source and setting up the build environment are provided in their respective sections.
Getting the kernel source
The source for your kernel must be made available by your device's manufacturer in order to comply with the GPL.
I dont know where to get it
Setting up the environment
Instructions for setting up the development environment should be included in your source code package. This should tell you the parts of the Android Open Source Project that must be in your working directory in order to allow the kernel to build. It will tell you what version as well. All of the Android Operating System source code is available at [android.git.kernel.org] and most projects are mirrored at [github.com/android]. Both are accessible via your internet browser as well as git.
Modifying the kernel
After the kernel source has been downloaded and your environment is set up, you can begin modifying the kernel. It is recommended (in most cases mandatory) that you run the standard "make xxx_defconfig" for your device before modifying the configuration.
Running
make
or
make -jX [where X is the number of operations to perform at a time]
at this point will make the stock kernel that your phone's official system has. To modify it, we can go two ways: 1) modify the file '.config' in a text editor, or 2) run
make menuconfig
for a graphical interface.
Modifying '.config' with menuconfigEdit
Typing
make menuconfig
will bring up the aforementioned graphical interface for modifying your kernel. Striking the "y" key when an option is selected (with "< >" or "[ ]" before it) will include it in the kernel. Striking the "m" key will add those options with a "< >" as a Linux kernel module (*.ko).
Adding tethering support (netfilter/iptables)Edit
Adding VPN support (TUN)
Adding Linux swap support
Adding ext3/ext4 support
Mofifying '.config' manually
The alternative to using menuconfig is editing '.config' in your preferred text editor. Options that are not to be included in the build are commented out with a "#". Options that are to be included inside the kernel image are uncommented and have the value of "y". Options with the value "m" are to be built into loadable kernel modules.
Adding tethering support (netfilter/iptables)Edit
Adding VPN support (TUN)Edit
Adding Linux swap supportEdit
Adding ext3/ext4 supportEdit
Packaging and flashing your kernelEdit
Additional stepsEdit
You may find that you want to play around with '.config', but don't want to lose your configuration. You can rename your '.config' to whatever you want and give it the suffix "_defconfig" and put it in "arch/arm/configs/" for the next time you wish to use it.
For example: if you had a kernel that had tethering and ReiserFS support, and you wanted to try enabling VPN without breaking your current setup, you could rename your '.config' to 'my_rfs_tethering_defconfig' and move it to "arch/arm/configs/". The next time you wanted to make this kernel you could run
make my_rfs_tethering_defconfig
and have your kernel configuration just as you left it.
Note that this would overwrite your kernel configuration stored in '.config'
Click to expand...
Click to collapse
You wrote it or Got it? :/
got it here is a source code some body download and upload it for s5670
https://opensource.samsung.com/reception.do?first=F
omarhasan76 said:
got it here is a source code some body download and upload it for s5670
https://opensource.samsung.com/reception.do?first=F
Click to expand...
Click to collapse
SUre thanks! Checking it out! I have teh SOurce code ALready!
Then upload it or we have to sign up for downloading
omarhasan76 said:
Then upload it or we have to sign up for downloading
Click to expand...
Click to collapse
Oh kay! I will upload it!
I will upload it in an hour! I am downloading the source code of Galaxy i9000! So, I will upload the Fit source code as soon as the i9000 one is over, fine?
as you told to share our researc i fond a step by step tutorial to prepare kernelhttp://forums.androidcentral.com/htc-hero-rooting-roms-hacks/8072-how-build-your-own-kernel-package-source.html
KK
Recently I decided to learn application development and building custom ROMs so i searched online for sources to learn. I found the following playlist uploaded by the user Marakana on youtube :
http://www.youtube.com/watch?v=Mf7z_mrce00&feature=bf_next&list=PLE953C0B85B50AB62&lf=results_main
There is also a book named "Learning Android" written by the same person who uploaded the videos above. I am new to android development and new to Java even,and I found these tutorials very useful ..... I am posting this because this may help someone
I sure does Help! Thank you for your contribution
krishnakanth_590 said:
Recently I decided to learn application development and building custom ROMs so i searched online for sources to learn. I found the following playlist uploaded by the user Marakana on youtube :
http://www.youtube.com/watch?v=Mf7z_mrce00&feature=bf_next&list=PLE953C0B85B50AB62&lf=results_main
There is also a book named "Learning Android" written by the same person who uploaded the videos above. I am new to android development and new to Java even,and I found these tutorials very useful ..... I am posting this because this may help someone
Click to expand...
Click to collapse
Thanks Man!
I am limited to 5 thanks per day..So, I cant thank you! Sorry!
Dude, for all your effort, I can just thank you! My Sister owns this device! It is shocking to see you in here! I thought you would be developing only for SL, S and S2 P:
---------- Post added at 04:29 PM ---------- Previous post was at 04:28 PM ----------
Is Android based on Linux?
There is 3 packages needed for any device for an original Android development:
Android source tree, preferably the original as with OEM devices but CyanogenMod or independent ports are enough too. Aka device
Kernel sources for the device. Aka kernel
Vendor proprietary drivers, which make the GPU and various sensors work. If not explicitly available for download they need to be extracted from a running device. Aka vendor
If these three packages are all available, making new roms will be easy for developers. Please co-operate to gather all of them here to be a resource for android developers.
If we could achieve this goal, I would port the Ubuntu OS for Nokia X2 and share it here with you
====
Progress:
Android source tree
No known instant or effort.
Can anyone contact to Microsoft mobile and get the Android source tree for Nokia X2 and upload it to Github?
Kernel sources
here is kernel source code for Nokia RM-1013 2.0.0.11: https://github.com/danialbehzadi/Nokia-RM-1013-2.0.0.11
Due to Microsoft mobile statement, there is no difference in kernel between 2.0.0.11 and 2.1.0.13.
DONE! :good:
Proprietary drivers
Thanks to T4ufik_Hidayat, Here is vendor packages: https://github.com/cm-nokia-x2/proprietary_vendor_nokia_ara
DONE! :good:
Nice effort
You are our only hope
As we have no real devs for this device and the device wasn't released globally, u r our only hope. I request u to build the kernel with device tree that we need so much to port any real android rom like AOSP , please. Frozentears was working on that, You can contact him as well.
Again, I request you, please make us a custom kernel so that we noobs can start porting KitKat/Lollipop for our beloved X2DS, u r our only hope because we see no other developer here for this device.
danialbehzadi said:
There is 3 packages needed for any device for an original Android development:
Android source tree, preferably the original as with OEM devices but CyanogenMod or independent ports are enough too
Kernel sources for the device
Vendor proprietary drivers, which make the GPU and various sensors work. If not explicitly available for download they need to be extracted from a running device.
If these three packages are all available, making new roms will be easy for developers. Please co-operate to gather all of them here to be a resource for android developers.
If we could achieve this goal, I would port the Ubuntu OS for Nokia X2 and share it here with you
====
Progress:
Android source tree
No known instant or effort.
Can anyone contact to Microsoft mobile and get the Android source tree for Nokia X2 and upload it to Github?
Kernel sources
here is kernel source code for Nokia RM-1013 2.0.0.11: https://github.com/danialbehzadi/Nokia-RM-1013-2.0.0.11
Due to Microsoft mobile statement, there is no difference in kernel between 2.0.0.11 and 2.1.0.13.
DONE! :good:
Proprietary drivers
No known instant or effort.
Does anyone know how to extract it? Can anyone contact to Microsoft mobile and get them and upload it to Github?
Click to expand...
Click to collapse
Here is for proprietary https://github.com/cm-nokia-x2/proprietary_vendor_nokia_ara
for Android source tree, try to use CyanogenMod.
maybe you can help people to make the complete rebuild of CyanogenMod with full fixed from bugs
danialbehzadi said:
There is 3 packages needed for any device for an original Android development:
Android source tree, preferably the original as with OEM devices but CyanogenMod or independent ports are enough too. Aka device
Kernel sources for the device. Aka kernel
Vendor proprietary drivers, which make the GPU and various sensors work. If not explicitly available for download they need to be extracted from a running device. Aka vendor
If these three packages are all available, making new roms will be easy for developers. Please co-operate to gather all of them here to be a resource for android developers.
If we could achieve this goal, I would port the Ubuntu OS for Nokia X2 and share it here with you
====
Progress:
Android source tree
No known instant or effort.
Can anyone contact to Microsoft mobile and get the Android source tree for Nokia X2 and upload it to Github?
Kernel sources
here is kernel source code for Nokia RM-1013 2.0.0.11: https://github.com/danialbehzadi/Nokia-RM-1013-2.0.0.11
Due to Microsoft mobile statement, there is no difference in kernel between 2.0.0.11 and 2.1.0.13.
DONE! :good:
Proprietary drivers
Thanks to T4ufik_Hidayat, Here is vendor packages: https://github.com/cm-nokia-x2/proprietary_vendor_nokia_ara
DONE! :good:
Click to expand...
Click to collapse
https://github.com/cm-nokia-x2/
android_kernel_nokia_msm8610-kernel source
proprietary_vendor_nokia_ara-vendor
android_device_nokia_ara- device(boardconfig.mk, other configs)
And here is the manifest
https://github.com/cm-nokia-x2/android_local_manifest
I am trying to run a program which require at least kernel version of 3.11 and so far now I cannot find any android phone devices which fullfil this requirement. Furthermore I need a list of devices for which cyanogenmod official/unofficial is available alongwith kernel source code. I would really appreciated the developers on this forum to put those devices.
Thanks alot.....
This means that developers are able to build and flash their own version of Android Pie on these devices.
The Open Devices program is our way to provide access and tools to build and test your custom software on a range of Sony devices. You can access all the resources you need through our Open Devices page on Developer World. We value our open source community and welcome you to participate in our projects via GitHub. Feel free to provide feedback on further resources you may need and where we can improve.
To get started on how to build AOSP for your device, use our build guides for instructions. Please note that this software is meant for developers and can be unstable due to its early stage. As part of our Open Devices program, the project for the Xperia 10 Plus are now available via GitHub where you can contribute and take part in our open source community.
Xperia 10 Plus GitHub project
Software binaries
Source: https://developer.sony.com/posts/xperia-10-and-xperia-10-plus-added-to-sonys-open-devices-program/
Great stuff
Dear community, I think this list is the first of its kind.
Purpose
The main purpose of the whole project is to help newcomers find the relevant TWRP and Roms for their devices and ultimately make the installation process as easy as possible. This list also serves the purpose of giving an overview of devices which can run custom android roms for people who do not have such a device yet and would like to buy one but don't know which ones to choose from.
Goal
Its goal is to contain as many devices (with name, model name and codename) as possible which also have official releases of TWRP, LineageOS, Resurrection Remix, Omnirom or Carbonrom. The list also contains some working TWRP builds and roms that I saved to a personal archive some time along the last years - mainly for older devices without newer roms and for good roms that just did not made it to an official release.
The Free-Droid project
The creation and continuous update of this list is tied to the Free-Droid project, mainly because it is scraped and put together by the same ruby code that is used inside the Free-Droid One-Click Rom Installation Assistant.
Why only these chosen roms? Can another rom be added?
The choice of roms showing in the list is constrained by these factors:
free and open source (no google apps included)
The website with the official releases can be scraped (programmatically read and evaluated) with ruby code down to the individual download links for the roms
(Preferred) The rom zips have signature spoofing support or are patchable with the NanoDroid patcher
A lot of roms fail at one of these constraints. I tried to add crDroid, but their website is pure javascript and can't be scraped easily. AospExtended was added by using the OTA API, but it turned out that the API server is way too unreliable. What might be possible and get added are mokee and /e/.
Updates
The list is automatically updated weekly and should always point to the latest available roms.