Hello First of all everybody,
I have an awesome idea for Development of Samsung Galaxy Player ( 4.0 as well as 5.0). I have little experience in Board Configuration ( Device Profile) making and I want to use this to develop ClockwordMod Recovery for Samsung Galaxy Player. But I cannot do this alone. I need someone more so that he can help me out in problems and also Compile CyanogenMod 7.1 from Source using the Device Profile that WE will make. After this is done we will have a cool Recovery for SG Player. Their should be some to test it as well because I am not having a Galaxy Player ( I AM A SOCIAL DEV [learner] who wants to develop a Low Activity Device).
Those with little experience in Android Compiling and other things can drop me a PM if INTRESTED. or Post here..
PS- You have knowledge in Android and have a Good Internet Connection to download CM Source coz I don't have it in my Country. ALSO I NEED THE HARDWARE CONFIGURATION DATA FOR Galaxy PLAYER like CPU, TOUCHSCREEN, SENSORS etc DETAILED. I AM ALSO SEARCHING FOR IT..
IF THIS TURNS OUT SUCCESSFUL - NEXT MISSION = CYANOGENMOD 7.1 FOR GALAXY PLAYER
By CWM I meant CWM 5.0 and not 3.0 which is already working..
Hi
As I am unable to post my question to the development thread (due to low nr of posts) I would like to ask for advice here.
I am currently running munjeni's Unoficial Cyanogenmod CM 11 ROM on my Xperia Go.
Thumbs up for the developers. The ROM is much smoother and responsive than the Sonys original JB 4.1.2.
The only consern I have is the lack of the Sony's FM radio application. Is it possible to integrate the Sony's FM radio to the ROM or provide a seperate apk to install.
The tools should be available according to Sony:
http://developer.sonymobile.com/201...leased-as-open-source-and-sensor-hal-updated/
I really miss the option to listen to the analog radio.
I have the same problem: can anyone help us?
Thank you!
As we all know that CM roms the CM team make it ... it already has many bugs so while we build it for our devices we just get new bugs so why don't we start building rom from android source that google shared it this source it already hasn't any bugs like CM so it will be better to start into building roms...""YOU MUST KNOW THAT YOUR DEVICE GALAXY STAR HASN'T ANY SUPPORT ANY MORE FORM SAMSUNG "" ...
/**********************************************\
THE MOST IMPORTANT THING ::RGANIZATION:::
we must organize our self to know what are going to do .... and devide working ... some developers work on kernel and others do other works and testers and we comunicate with each others ....:angel::angel::angel:
/***********************************************\
and a cups of tea and bring your BRAIN ....
if you have any advice plz write it here
LahKeda said:
As we all know that CM roms the CM team make it ... it already has many bugs so while we build it for our devices we just get new bugs so why don't we start building rom from android source that google shared it this source it already hasn't any bugs like CM so it will be better to start into building roms...""YOU MUST KNOW THAT YOUR DEVICE GALAXY STAR HASN'T ANY SUPPORT ANY MORE FORM SAMSUNG "" ...
/**********************************************\
THE MOST IMPORTANT THING ::RGANIZATION:::
we must organize our self to know what are going to do .... and devide working ... some developers work on kernel and others do other works and testers and we comunicate with each others ....:angel::angel::angel:
/***********************************************\
and a cups of tea and bring your BRAIN ....
if you have any advice plz write it here
Click to expand...
Click to collapse
That is if we had devs
The source has to be proper if we or any1 has to do something.
nice advise
nice advise man :good:
Hi,
I work in the security and privacy field and would like to start development of a new lightweight ROM with strong security and privacy controls but to be honest I don't have a clue where to start. I am experienced in flashing ROMs onto Android devices (currently have CM on my Nexus 4 and Galaxy Tab 2 as well as Beanstalk on my old HTC Desire Bravo) but have not yet built a custom ROM.
Ideally I would like to build the lightest possible ROM for HTC Desire (as this is my device for experimenting) but there are a number of features/restrictions I would like to include.
I see a lot of ROMs on this site (which I am sure are very good) and some generic guides on how to build ROMs but I need some more specific information. I need to know how to build a kernel which disables access to certain things (such as regular voice calling - this ROM should only permit VOIP calls) - how to strip out all the apps and services I don't want or need, how to include the apps I want installed by default (such as droidwall) and I have yet to come across such a resource.
Ideally I would like to strip the ROM down to the bare minimum required to allow a functioning device with data connectivity and then build it back up with the functionality I need.
Could anyone point me in the right direction?
Hi
I can Need you. You can Port roms .i have a project with Android 5.0 for Mid and Low End devices please join US We can work together but i Need more Rom porter and Kernel builder
Link:http://forum.xda-developers.com/che...oid-lollipop-5-0-rom-low-mid-devices-t2925685
Thanks from Germany
I DO NOT OWN THE ROM.
The developer of this rom is kumajaya on MIUI forum and thanks to him for his work.
MISSION:
Embarrass Xiaomi because refuse to release Redmi 2 kernel source
BUG:
Before you install this ROM, check your device magnetic sensor. Currently YAS537 not supported!
Still under development, built from sources, no hidden sources, not a binary dirty hack ROM
The following will not be supported in this thread:
- Custom Kernels
- Mods, including CPU management mod or any strawberry mod
- Modified system files
- Xposed
If you reuse even a part of my work here, a proper credit is a must, keep it open source also a must
Download:
Cyanogen and TWRP recovery: https://goo.gl/cDJQXI
CyanogenMod 12.1 ROM: https://goo.gl/zhGZjQ and https://goo.gl/5sqZGp
For better Google experience, install TK GApps Nano: http://forum.xda-developers.com/android/software/tk-gapps-t3116347
Don't create any mirror without a permission!
Cyanogen recovery above just like a standard AOSP recovery without a lot of features compared to TWRP, but you can temporary boot it using "fastboot boot cyanogen-recovery-wt88047.img" command to check if CyanogenMod 12.1 ROM possibly working on your device variant.
Don't even try this ROM on Redmi 2A variant!
Sources:
CyanogenMod source tree: [url]https://github.com/CyanogenMod[/URL]
Kernel source: https://github.com/kumajaya/android_kernel_cyanogen_msm8916
Device specific source: https://github.com/kumajaya/android_device_wingtech_wt88047
Vendor binaries: https://github.com/kumajaya/proprietary_vendor_wingtech
Changelog:
Device specific source: https://github.com/kumajaya/android_device_wingtech_wt88047/commits/cm-12.1
Kernel source: https://github.com/kumajaya/android_kernel_cyanogen_msm8916/commits/cm-12.1-amss-1.0.2-wt88047
Vendor binaries: https://github.com/kumajaya/proprietary_vendor_wingtech/commits/cm-12.1
Credits:
Google, AOSP, Cyanogen, CyanogenMod community, Qualcomm's CodeAurora @balika011, @zwliew, @Flour_Mo
Introducing me: XDA Recognized Developer, CyanogenMod contributor
My wife, she always believed I could restore back her device in minutes
Some tools: Kate (text editor), Kompare (diff viewer and generator), qgit (git GUI)
Smarfren Indonesia for Andromax Q source code
Micromax India for Yuphoria and Yureka source code
Current status:
Boot to Android, this is my first ROM that really boot on the first try
Touchscreen works, all hardware button mapped correctly
No screen flicker, fluid graphics
Voice call and SMS works, data over WiFi and GSM works (radio config in build.prop fix previous GSM issue)
Vibration and screen rotation works
All sensors seem works including GPS and compass but light sensor still need a fine tuning
Both camera working, the author found a super clean solution
No boot animation (fixed, kernel issue) Disable splash screen break Android boot animation but if I enable it, Cyanogen recovery covered by Tux the penguin logo in the center. The workaround solution, move Tux to the top right of the screen
No sound (fixed, kernel and user space issue) This also fix slow boot because of logcat flooding. BUG: Speaker output ignore headset jack insertion, sound out from both speaker and headset
Bluetooth file transfer fail (~42MB zip, failed at 17%) WiFi file transfer way faster
FM radio works
WiFi hotspot works
YouTube and local video 720p works
LED driver working great, multi color and blink
Remember, no contribution from Xiaomi yet. That's the reason why I try to avoid "Xiaomi" string in my source as possible but Wingtech.
I use CyanogenMod resources as much as possible, including common MSM8916 device tree and kernel. Maintain device source tree and leave common part to CyanogenMod community. I'll strictly follow CyanogenMod coding style and source structure. This is about source code quality.
AGAIN, I DO NOT OWN THE ROM.
Will try it soon. And I hope Xiaomi will release the kernel like Redmi 1s.
kumajaya and zwliew are the most stable CM12.1 roms for our phone. I hope they reach 100% full working version in near future.
Thank you both!
Can you upload the changelog for the latest [30/09/15] build. Also is the YAS537 supported
How about some screenshots?
What is the point of this thread when the original poster already has one on XDA?
Sent from my Nexus 7 using Tapatalk
crzlloid said:
Can you upload the changelog for the latest [30/09/15] build. Also is the YAS537 supported
Click to expand...
Click to collapse
There is a link in my post about the changelog and the YAS537 is still not yet supported.
zwliew said:
What is the point of this thread when the original poster already has one on XDA?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Sorry, but I have already talk to kumajaya about it. Then he ask me to help him on requesting an official sub-forum for our device. Anyways, if anyone here oppose me about posting this thread, then maybe I should delete this.
wow, using this in 2020, 5 years later.