Hello Guys.
I want to Buy a Cheap Device(Which have available sources) to learn android ROM Building.
My Budget is Very Tight:crying: Rs.8000
Please Suggest me a Good Device.
Thanks in Advance.:good:
Rumorbox33 said:
Hello Guys.
I want to Buy a Cheap Device(Which have available sources) to learn android ROM Building.
My Budget is Very Tight:crying: Rs.8000
Please Suggest me a Good Device.
Click to expand...
Click to collapse
Lol, You call Rs. 8000 budget a tight budget??
That's more than enough..
Nowadays, most devices release their kernel source including device trees (Though not proper)..
As far as I can remember, I'll suggest you to buy Yu Yunique, which is quite new as of now and has very less custom ROMs as of now and has sources released..
Or you can choose any other device as you wish.
All you should do is search hard if the source is released for that phone. (All u need to do is Google to find out)
And, there are many tutorials in XDA which will easily help you learn about ROM development.
Note:
ROM development needs some/little Android knowledge depending upon what you're going to do.
To build CM from source, you need a hell lot of knowledge.
You also need a hell lot of time and patience.
To build a custom ROM based on CM, you more or less just need to follow the instructions given in that custom ROM's website.
Also you'll need a fast internet to download sources which will be like 13-16GB (this is for each ROM base)
But, porting a ROM can be quite easy compared to building from source..
So, if you're kind of new, better learn something about Android and how it works, before you buy a phone simply for development purpose, to avoid repenting in the future that you've wasted your money..
GokulNC said:
Lol, You call Rs. 8000 budget a tight budget??
That's more than enough..
Nowadays, most devices release their source including trees (Though not proper)..
As far as I can remember, I'll suggest you to buy Yu Yunique, which is quite new as of now and has very less custom ROMs as of now and has sources released..
Or you can choose any other device as you wish.
All you should do is search hard if the source is released for that phone. (All u need to do is Google to find out)
And, there are many tutorials in XDA which will easily help you learn about ROM development.
Note:
ROM development needs some/little Android knowledge depending upon what you're going to do.
To build CM from source, you need a hell lot of knowledge.
You also need a hell lot of time and patience.
To build a custom ROM based on CM, you more or less just need to follow the instructions given in that custom ROM's website.
Also you'll need a fast internet to download sources which will be like 13-16GB (this is for each ROM base)
But, porting a ROM can be quite easy compared to building from source..
So, if you're kind of new, better learn something about Android and how it works, before you buy a phone simply for development purpose, to avoid repenting in the future that you've wasted your money..
Click to expand...
Click to collapse
I have knowledge about android That's why i am asking:good:
So,What about Redmi 1S ?
Should i buy That ?
Rumorbox33 said:
I have knowledge about android That's why i am asking:good:
So,What about Redmi 1S ?
Should i buy That ?
Click to expand...
Click to collapse
Yes, it's OK.
Kernel sources are released: http://en.miui.com/thread-73469-1-1.html
How could I be able to build/port bugless Android 7 (Nougat) for MT65xx based devices (Specifically MT6582 device "Mine is Infinix Hot X507")? I am looking for building/porting a bugless Lineage OS/Resurrection Remix/AOSP/... latest release ROMs for my MT6582 device. I've no experience in building/porting Android ROMs. My question could be what are the topics/guides I need to learn from in order to have the skills of the person who is able to build/port a bugless Nougat version for my device?
It doesn't matter the topics/guides are for porting/building (also is it easy/hard), however the more convenient approach for me is the one by which I could have a bugless fully device-compatible ROM at the end.
I have good programming knowledge base and dealing with command line software. Also I will start learning Linux Kernel in few weeks after my exams.
I need your valuable help and suggestions. Thanks in advance.
Research/Outcomes till now:
■ I have read a little about porting. I understood that first I need a to-be-Port-ed ROM of another phone having the same CPU. I have found one here, but unfortunately it has some bugs. The publisher says that this version is unstable and needs someone to build it for MT6582. I'm looking for being able to have the skills to be that person .
omareg94 said:
How could I be able to build/port bugless Android 7 (Nougat) for MT65xx based devices (Specifically MT6582 device "Mine is Infinix Hot X507")? I am looking for building/porting a bugless Lineage OS/Resurrection Remix/AOSP/... latest release ROMs for my MT6582 device. I've no experience in building/porting Android ROMs. My question could be what are the topics/guides I need to learn from in order to have the skills of the person who is able to build/port a bugless Nougat version for my device?
It doesn't matter the topics/guides are for porting/building (also is it easy/hard), however the more convenient approach for me is the one by which I could have a bugless fully device-compatible ROM at the end.
I have good programming knowledge base and dealing with command line software. Also I will start learning Linux Kernel in few weeks after my exams.
I need your valuable help and suggestions. Thanks in advance.
Research/Outcomes till now:
Click to expand...
Click to collapse
First of all, chances are high you won't get a fully bugless one at the very first boot.there will be device specific files that causes minor bugs which you can only find and fix after the ROM boots successfully. This should be your primary objective,there are lot of guides for porting mediatek devices you can follow guides for marshmallow ROMs as its similar.
But i must it will be easier trying a marshmallow or lollipop roms first if youre new,anyway I wish you Good luck:good:
- Now to the ROM (trust me I know all about it)
It is based on 3.10.103 kernel so first you have to build one for your device. basic things like data aren't working in this beta release.
The publisher says he needs someone to build it for mt6582? Well,**** .
Building ROMs/kernels aren't easy but I'll tell you what is though ,stealing someone's days of work, put it in your blog without even giving some credits,this youtuber may not know about it so...I'm not gonna do anything about it
Will this build be fixed? It was ditched because of the above mentioned problem but I/other devs may release another stable build for our device(lenovo a5000) but it may or may not be available to the public
Edit :it's out now
Hello,
I'd like to get into android ROM development. But I will need help/guidance.
I've managed to build lineageos for curtana using xiaomi kernel and malachite device tree and vendor files. Don't know it it actually works as I don't have the device
.
So as I said I'd like to learn it, but as android is big I am still kinda lost in it. I know i can create something that already is, but that is not useful to the others, so that's why I am thinking about these 2 devices xiaomi note 10 or note 10 lite as they don't have any roms yet.
So if there is anyone who will be able to help and guide me through the process of getting device tree, vendor files and using (xiaomi) kernel putting it all together, I will be more than happy to buy one of those devices and go and create and support some lineageos, aosp and or pixel experience roms.
Thanks
Gajdalf said:
Hello,
I'd like to get into android ROM development. But I will need help/guidance.
I've managed to build lineageos for curtana using xiaomi kernel and malachite device tree and vendor files. Don't know it it actually works as I don't have the device
.
So as I said I'd like to learn it, but as android is big I am still kinda lost in it. I know i can create something that already is, but that is not useful to the others, so that's why I am thinking about these 2 devices xiaomi note 10 or note 10 lite as they don't have any roms yet.
So if there is anyone who will be able to help and guide me through the process of getting device tree, vendor files and using (xiaomi) kernel putting it all together, I will be more than happy to buy one of those devices and go and create and support some lineageos, aosp and or pixel experience roms.
Thanks
Click to expand...
Click to collapse
The problem is that there are no working trees yet. The only thing which is not working is the display. the display is just dead
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
Hi Everyone!
I'm very new to this topic, this is my very first time trying to build a kernel from source code. As setup i've a samsung a13 SM-A135M (which is the 4g version of a13 series), this phone by default is forced to work 32bit on a processor and hardware that has the capability to go full 64bit.
The question is:
I've inquiried the correct version and baseband that corresponds to my device, on https://opensource.samsung.com/, and they uploaded the source code of it (the baseband is A135MUBU1AVB5), so with this source code should i be able to build a 64bit version of both kernel and android OS , or this source code only works for 32 bit installations?
Thanks and Regards!
Hi, I just asked a very similar question here: https://androidforums.com/threads/i...this-problem-a13-samsung.1347411/unread?new=1
And someone's reply brought me to your thread. I don't exactly know much about coding but an experienced user said he did some searching, his answer is on my thread. As of now there is no way that he could find to get a 64bit software on the a13, hopefully this changes.
Hi!! thats right, the problem that you have is what has driven this question, although i've the source code for building the OS i'm waiting for someone more experienced to tell me if this source is able to build a 64 bit version of the OS and Kernel for the A13 phone. Hope we find this experienced person
arieleoar said:
Hi!! thats right, the problem that you have is what has driven this question, although i've the source code for building the OS i'm waiting for someone more experienced to tell me if this source is able to build a 64 bit version of the OS and Kernel for the A13 phone. Hope we find this experienced person
Click to expand...
Click to collapse
That would be great I think the a13 is great value for the price now we just need to get around the software limitations