Related
*** THIS IS NOT JUST ANOTHER EFFORT TO CREATE YET ANOTHER CUSTOM ROM***
Though Android is opensource, a lot of things are unknown regarding ROM development/modification. There are many custom ROMs available for Galaxy 3 (and also other phones) and lot of people are flashing them and making their phone more responsive, productive and faster; but very few people actually knew how to go about developing the ROM.
What I intend here is to find out and document correct way to build ROM for our favorite Galaxy 3, which is very popular in India.
The goal will be to develop the ROM from Android source + Drivers from stock ROM while documenting the process so that large number of people can contribute to the development.
I will shortly update the posts with what I have done.
Reserved
Can anyone help me convert system.img and userdata.img file into files flash-able by ODIN?
Thanks
Third post
Reserved for future use
Fourth post
Fourth post.. reserved
Fifth post
Reserved 5th post goes here...
looking forward to what you come up with
Making one aint difficult keeping it bug free might get sometimes
Thanks rudolf895
I have experience in Android SDK and NDK development, but I am a noob when it comes to ROM development. Thats why this effort.
I have fetched android source using repo as well as I have also downloaded source for I5801 from Samsung open source website. After this I will look into extracting drivers from stock ROM and successfully compiling it for Galaxy 3.
rudolf895 said:
looking forward to what you come up with
Making one aint difficult keeping it bug free might get sometimes
Click to expand...
Click to collapse
abhijeet.pathak said:
thanks rudolf895
i have experience in android sdk and ndk development, but i am a noob when it comes to rom development. Thats why this effort.
I have fetched android source using repo as well as i have also downloaded source for i5801 from samsung open source website. After this i will look into extracting drivers from stock rom and successfully compiling it for galaxy 3.
Click to expand...
Click to collapse
best of luck
Looking forward to it!
abhijeet.pathak said:
Thanks rudolf895
I have experience in Android SDK and NDK development, but I am a noob when it comes to ROM development. Thats why this effort.
I have fetched android source using repo as well as I have also downloaded source for I5801 from Samsung open source website. After this I will look into extracting drivers from stock ROM and successfully compiling it for Galaxy 3.
Click to expand...
Click to collapse
Do not fell shy to ask for help u need. Together we can make it better. We are with you whenever u need us.
ARMVK Dev Team
Thanks!
Thanks a lot for your support guys..
arunmcops said:
Do not fell shy to ask for help u need. Together we can make it better. We are with you whenever u need us.
ARMVK Dev Team
Click to expand...
Click to collapse
hehe, cant wait to see what you come up with, sounds promissing btw... i am also willing to help whereever i can, whereas this wont be too much in this case i guess.
good luck and thanx...
TY ..!
Thanx alot
This would be really helpful to alot of members here
interesting ! waiting ....
I applaud your thread, I myself was thinking about such a concept.
I wanna help, but I cant do that much (basic knowledge of C and basic/little knowledge of linux and adb).
I think first there should be a list of basic stuff. Like compiling the sources, extracting factoryrfs and co from your phone etc... Sometimes if you wanna start doing something and you dont know the basics you get scared off because of their apparent tremendous lack of knowledge.
I'd probably start dabbling if somebody told me how to compile the sources.
can you also specify your work environment, toolchain and such stuff, so anyone can start from zero? there is a kernel building vm image with all tools by sztupy somewhere on the forum that is eventually of interest, and there is also an extended version containing eclipse and some more tools for full android development:
http://forum.xda-developers.com/showthread.php?t=882010
hope this helps somebody...
Did you try using it? I think the scripts are specific and cant be used by us (without altercation)
no, i have absolutely no idea of kernel compilation and all that advanced stuff, but i guess it can be adapted for our use
Yup...me too in waitin line...Now i can say i dint made a mistake by buying it...
Sent from my GT-I5801 using XDA App
abhijeet.pathak said:
Can anyone help me convert system.img and userdata.img file into files flash-able by ODIN?
Thanks
Click to expand...
Click to collapse
maybe you can create a ".tar" package including all those files.. .tar is flashable in odin..
Hi all,
I am trying to make a universal CWM flashable .zip file that automagically installs drivers for the IR Blaster on the P3113. Unfortunately, I would like some help from some developers so I can learn more about how I could make this possible. I really think that if I could get some help and make this work, than I would be making a large contribution to both the developer and end-user community as not many non-stock ROMs have support for an IR blaster.
If you would enjoy to help on making this, feel free to PM me!
Thanks,
thejrcrafter
thejrcrafter2 said:
Hi all,
I am trying to make a universal CWM flashable .zip file that automagically installs drivers for the IR Blaster on the P3113. Unfortunately, I would like some help from some developers so I can learn more about how I could make this possible. I really think that if I could get some help and make this work, than I would be making a large contribution to both the developer and end-user community as not many non-stock ROMs have support for an IR blaster.
If you would enjoy to help on making this, feel free to PM me!
Thanks,
thejrcrafter
Click to expand...
Click to collapse
Look at the Code Review:
http://review.cyanogenmod.org/#/c/46770/
http://review.cyanogenmod.org/#/c/46771/
http://review.cyanogenmod.org/#/c/45069/
To see how IR is implemented. There isn't a single driver-type file/files like in windows. There is an IRda system service that is a go between, between the compiled module for IR and the applications using IR. The second part is the module that is the go-between, between the board hardware and the system service.
Its involves alot of changes in the source code. It can't be implemented into a universal flashable zip.
Luigi2012SM64DS said:
Its involves alot of changes in the source code. It can't be implemented into a universal flashable zip.
Click to expand...
Click to collapse
Oh, well that's a bummer. I was really hoping that something would come of this. Would it be possible to maybe make a package of some sort that has a shell script that embeds the IR modules into downloaded source code before you build it, so you don't have to put it in manually? That's really all that I'm hoping for, is some way to auto-embed IR support into any ROM.
thejrcrafter2 said:
That's really all that I'm hoping for, is some way to auto-embed IR support into any ROM.
Click to expand...
Click to collapse
Welcome To The Club....I think most of us 3113/5113 users would like IR to work with all ROMs
Hi everyone,
I've been working on CM for the PadFone Infinity (pretty good device, only lacking a good community) for some time, and I've started to have some results now.
I've basically been using Asus' kernel sources and a custom-made device tree. I then tried to build CM and corrected every error I encountered to try to compile ROM successfully. I eventually succeded in compiling it, but it's now that I need help the most.
Why? Because I have no kernel development knowledge at all, and I really don't want this project to die.
So, let's list what does work and what doesn't:
-Recovery compiles and works just fine. I can backup, restore, flash roms, wipe, and everything that is needed.
-ROM and kernel compile without errors too.
-ROM does NOT boot at all. Getting past the Asus logo, the screen just switches off, and phone totally looks like it's shutdown. No backlight, keys are not backlighted either.
So here is what is needed to compile ROM:
-Device Tree
-Kernel sources (modified to compile without errors)
-PadFone Infinity stock ROM (if needed. Also, there are device blobs in it, so it might be useful)
-Asus untouched kernel sources
I do have the device, so if you need anything about it (hardware info, for example), feel free to ask. I'd love to help, even though I've already made some work, I've come to a point where my knowledge will be far from enough...
Thanks everyone for reading, and maybe for helping if you are interested in this project.
Contact Faux, maybe he will be interested in maintaining a Kernel base for this device.
Bumping.
If a xda recognized developer is willing to develop for this device, I'll have one sent to him.
I really want to have CM and some dev community on this device. I started a bounty to be able to have a device sent to a dev, it seems that many people also want development on it.
I'd also bump the thread. I also interested in CM on padfone, and especially after ASUS discontinued device support :-/
mva.name said:
I'd also bump the thread. I also interested in CM on padfone, and especially after ASUS discontinued device support :-/
Click to expand...
Click to collapse
cm always need alot of work and if you don't have the device it's very difficult to have a stable build .
messi2050 said:
if you don't have the device it's very difficult to have a stable build .
Click to expand...
Click to collapse
AFAIRC, topicstarter suggested to donate a device for interested cm-developer
mva.name said:
AFAIRC, topicstarter suggested to donate a device for interested cm-developer
Click to expand...
Click to collapse
Yeah but that was from 2013 look to the post date , i can do it if the offer is still there but i doubt that
Does anyone know about this topic?
https://forum.xda-developers.com/mi-note-10/how-to/custom-development-t4018813
In short:there are same some efforts trying to get custom Roms but nothing groundbreaking yet.
I am working on the device tree right now to compile from source. Not ready yet and don't have the device in hand right now (should arrive soon) s.o. else is trying with treble images.
nchantmnt said:
https://forum.xda-developers.com/mi-note-10/how-to/custom-development-t4018813
In short:there are same some efforts trying to get custom Roms but nothing groundbreaking yet.
I am working on the device tree right now to compile from source. Not ready yet and don't have the device in hand right now (should arrive soon) s.o. else is trying with treble images.
Click to expand...
Click to collapse
I thought device tree is something that was used to be leaked from Xiaomi
As far as I can see there is no device tree published by xiaomi for tucana (our device)
Only thing we have rn is kernel source.
But we can create device tree by ourself. There are some basic guides online. Rest is compare with existing device trees for similar devices and copy&paste.
for now I have downloaded k20 device tree, removed everything k20-specific (e. G. Popup Camera) and adapt further files for our device(s)
When my handset arrives (should be today) I can start unlock procedure (should take some time to get the code AFAIK), then I can unlock bootloader, flash custom recovery and see if I can get my device to boot properly after flashing... Then comes troubleshooting.
Right now I am expecting maybe a halfway booting device or broken/missing functionality at best. But we will see
I hope soon
The more people help together the faster we can get some Roms ?
nchantmnt said:
The more people help together the faster we can get some Roms ?
Click to expand...
Click to collapse
If you have a group for this, would you pm?
No group yet, but you still get an pm
Anyone willing to collaborate is welcome to pm me as well
I have seen this Android 9 source code. Is it helpful?
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/tucana-p-oss
I thought this model would have more support and after 4 months there is no Rom. I hope that now that the price is going down more people buy it and we have more community. Thank you for what you know and develop.
ignalop1983 said:
I have seen this Android 9 source code. Is it helpful?
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/tucana-p-oss
I thought this model would have more support and after 4 months there is no Rom. I hope that now that the price is going down more people buy it and we have more community. Thank you for what you know and develop.
Click to expand...
Click to collapse
Just an incomplete kernel sources, I think is useless.
https://www.xda-developers.com/poss...-fcc-certified-snapdragon-730g-penta-cameras/
There will be a lite edition soon. The only difference on hardware is number of pixels.
If its ROM is same or almost the same to current models, we should get some progress around development.
Anything new?
UtkuAblak said:
Does anyone know about this topic?
Click to expand...
Click to collapse
Please look at the existing topics first, before opening another topic!
nchantmnt said:
As far as I can see there is no device tree published by xiaomi for tucana (our device)
Only thing we have rn is kernel source.
But we can create device tree by ourself. There are some basic guides online. Rest is compare with existing device trees for similar devices and copy&paste.
for now I have downloaded k20 device tree, removed everything k20-specific (e. G. Popup Camera) and adapt further files for our device(s)
When my handset arrives (should be today) I can start unlock procedure (should take some time to get the code AFAIK), then I can unlock bootloader, flash custom recovery and see if I can get my device to boot properly after flashing... Then comes troubleshooting.
Right now I am expecting maybe a halfway booting device or broken/missing functionality at best. But we will see
Click to expand...
Click to collapse
Well, just tell me if you need help.
Same here, I am very tempted by the Note 10 but I am waiting for an aosp rom as many people complained about the stock miui rom
Any news or update on this? Would love to buy a Mi Note 10 as their prices have gone down but with the lack of development I'm kind of leaning towards the 9t even tho I'm worried about that front camera as some have had issues. I suspect not many are developing for this device because of the high price. Hopefully whoever said something up there about the Note 10 lite gets custom ROMs going with more devs
I'm still trying here but very short on time. We have some good progress on device tree thanks to someone else (thanks Hlcpereira).
nchantmnt said:
I'm still trying here but very short on time. We have some good progress on device tree thanks to someone else (thanks Hlcpereira).
Click to expand...
Click to collapse
yes he is working on this device.
nchantmnt said:
I'm still trying here but very short on time. We have some good progress on device tree thanks to someone else (thanks Hlcpereira).
Click to expand...
Click to collapse
Awesome news! Thanks :good:
I think the development goes now straight because we have MIUI Stable based on Android 10 now.
Good luck!
LineageOS (Lineage Android Distribution) members or anyone else on this website is not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in the products you find here before flashing it! YOU are choosing to make these modifications, and if you point the finger at us for messing up your device, we will laugh at you. Your warranty will be void if you tamper with any part of your device / software.
How to Install:
1- Make a backup of your important files
2 - Unlock bootloader with this guide
3 - Flash the TWRP, link here
4 - Move Rom & Gapps (optional) into device storage
5 - Full Wipes
6- Flash Rom & Gapps (gapps are OPTIONAL)
for GAPPS:
Choose Gapps Package ARM64 > 7.1 > Micro and below: visit OpenGAPPS
If during the gapps flash it gives you an error then in the TWRP terminal or on the adb shell you have to execute this command: "mkdir /tmp/bin"
Download:
Releases · XRedCubeX/android_device_meizu_m5c
Contribute to XRedCubeX/android_device_meizu_m5c development by creating an account on GitHub.
github.com
Working:
Boots
Storages
Bluetooth
Wifi
GPS - GNSS
Audio
NOT Working:
Camera
Hotspot
Offline Charging
Special Thanks
LineageOS
Moyster for device trees
Device Tree:https://github.com/XRedCubeX/android_device_meizu_m5c
Vendor Tree: https://github.com/XRedCubeX/android_vendor_meizu_m5c
Assim que possível, irei testar!
Hi Red. I was taking a look at the ROM repository on GitHub, and saw that the default branch is now named cm-13.1. So, are you now working on an Android 6.0 ROM for the M5c?
thiagosousa777 said:
Hi Red. I was taking a look at the ROM repository on GitHub, and saw that the default branch is now named cm-13.1. So, are you now working on an Android 6.0 ROM for the M5c?
Click to expand...
Click to collapse
I have a slight indecision, now I can not carry on the Custom ROM because I do not have the right PC but when I am able to compile it, I will evaluate which one can work better
XRed_CubeX said:
I have a slight indecision, now I can not carry on the Custom ROM because I do not have the right PC but when I am able to compile it, I will evaluate which one can work better
Click to expand...
Click to collapse
I see. I would say that in the long run Lineage 14 would be more worthwhile, since Android 6.0 is becoming outdated, with no support for some apps. But really, I just wanted a ROM to replace Flyme, and its bugs. Also, many of the apps I use don't work, or don't work right on Flyme...
These days I was taking a look at /e/ OS. I've been thinking about venturing into porting this ROM to the M5c. For me it would be a challenge, since I've never done this before. But unfortunately at the moment I also don't have a PC that meets the requirements to compile the ROM
thiagosousa777 said:
I see. I would say that in the long run Lineage 14 would be more worthwhile, since Android 6.0 is becoming outdated, with no support for some apps. But really, I just wanted a ROM to replace Flyme, and its bugs. Also, many of the apps I use don't work, or don't work right on Flyme...
These days I was taking a look at /e/ OS. I've been thinking about venturing into porting this ROM to the M5c. For me it would be a challenge, since I've never done this before. But unfortunately at the moment I also don't have a PC that meets the requirements to compile the ROM
Click to expand...
Click to collapse
I find it useless, just use lineage without gapps and it will be better than /e/, then anyway I don't know where to find the manifest
XRed_CubeX said:
I find it useless, just use lineage without gapps and it will be better than /e/, then anyway I don't know where to find the manifest
Click to expand...
Click to collapse
You are right. However, /e/ has some nice features like e account synchronization, an app store, microG, and some of their apps... Of course we could get that with LineageOS, but it is interesting how /e/ already brings that well integrated and ready.
By the way, I am also looking at other non-Android systems, like Ubuntu Touch...
thiagosousa777 said:
You are right. However, /e/ has some nice features like e account synchronization, an app store, microG, and some of their apps... Of course we could get that with LineageOS, but it is interesting how /e/ already brings that well integrated and ready.
By the way, I am also looking at other non-Android systems, like Ubuntu Touch...
Click to expand...
Click to collapse
Ah beautiful those non-android systems yes, unfortunately we have to forget them because of the prebuilt kernel and unavailable sources
XRed_CubeX said:
Ah beautiful those non-android systems yes, unfortunately we have to forget them because of the prebuilt kernel and unavailable sources
Click to expand...
Click to collapse
Well, from what I've been reading the process is similar to porting LineageOS. You just need the kernel sources and the device specific binary blobs. I'm guessing you know how to get them, don't you?
And the interesting thing is that there is a layer, called Halium, that interacts directly with the hardware. And that is actually what you should port to the desired device. Then you can install any Linux system on top of this layer, like Ubuntu Touch, Plasma Mobile, etc, and these are distributed pre-compiled.
thiagosousa777 said:
Well, from what I've been reading the process is similar to porting LineageOS. You just need the kernel sources and the device specific binary blobs. I'm guessing you know how to get them.
And the interesting thing is that there is a layer, called Halium, that interacts directly with the hardware. And that is actually what you should port to the desired device. Then you can install any Linux system on top of this layer, like Ubuntu Touch, Plasma Mobile, etc, and these are distributed pre-compiled.
Click to expand...
Click to collapse
Mhh ... good, you are informed, however the vendor blobs are bull**** to take, the problem is the kernel sources but Meizu has not released them. However, some time ago I booted a Custom kernel based on ALPS (A custom AOSP from Mediatek to be clear) but the touchscreen doesn't work and I'm looking for a solution around but that I can't find
P.S: Fixing that kernel has great potential, forget android 7, you could also boot android 9 with sources, but as long as they are still working
XRed_CubeX said:
Mhh ... good, you are informed, however the vendor blobs are bull**** to take, the problem is the kernel sources but Meizu has not released them. However, some time ago I booted a Custom kernel based on ALPS (A custom AOSP from Mediatek to be clear) but the touchscreen doesn't work and I'm looking for a solution around but that I can't find
P.S: Fixing that kernel has great potential, forget android 7, you could also boot android 9 with sources, but as long as they are still working
Click to expand...
Click to collapse
I confess I didn't quite understand one thing: so how did you port LineageOS to this device? You didn't need the kernel sources?
thiagosousa777 said:
I confess I didn't quite understand one thing: so how did you port LineageOS to this device? You didn't need the kernel sources?
Click to expand...
Click to collapse
At the time I was doing this lineage, I was with the prebuilt kernel, week ago I had done this kernel port to a twrp and the touch was not working so I left the device alone
XRed_CubeX said:
At the time I was doing this lineage, I was with the prebuilt kernel, week ago I had done this kernel port to a twrp and the touch was not working so I left the device alone
Click to expand...
Click to collapse
Thanks for the clarification! It is a shame that Meizu does this (I wonder if they are not violating the terms of the Linux GPL license by distributing the kernel without publishing the modifications made to the source code).
Anyway, if a solution to this kernel problem related to the touch screen comes up, please let me know. In the meantime I'll keep reading Halium's documentation until a solution comes along, or until I get a compatible phone.
Great work!
Hello. I've been testing this ROM on my M5c and love it. The ROM is very good, fluid, lightweight... the only problem is that the camera doesn't work, as well as the cellular network data. Congratulations for the excellent work.
The ROM will no longer receive bugfixes?
pls compile
publish a release