Towards the UberROM! - Android Q&A, Help & Troubleshooting

Hello!
Now, who am I, I am a dude who got sick of his android phone and decided to take the initiative!
Well, you see, many many Android users get sick of their phones, of the bloatware by the manufacturers and their user interface, we got tired of not getting the updates and falling back!
So what do we do, we root and probably install a Custom ROM, pretty good eh, android is about choice after all!
So, what happened..I tried doing the same, didn't get satisfaction from the ROMs available for my phone, and now I am stuck
As they say, if you want something done, do it yourself, which is why I decided to take upon myself the responsibility of making a Custom ROM for the user, I want to leave the source code out there, for everyone and anyone to tinker with it and port it to his phone, and I wanted to create the ROM the Android master race deserves...created by a user for users
You might think "This is all wonderful, but where do I come in?"
You, sir, are the user, you are the one this project is created for, and I need your help
I need you guys to help me create this ROM, I need you to tell me what you want to see in that ROM (Marshmallow), I want you to tell me what features are needed and what features are desired, what do you guys think Android M lacks and what shouldn't be touched, what should I improve and what should be left alone, I need your help to make something you would want to use.
HEY, ANDROID IS ALL ABOUT CHOICE AFTER ALL, AND I WANT YOU TO MAKE THE CHOICE!
P.S.:If you could name your phone, what UI or CustomROM you're running (or any CustomROMs you have used before) and tell me what features were implemented there and I should recreate or improve, the pros and cons of your ROM
P.S.S: I know I am asking for too much here, but as you might have thought, this looks like lots of work.
If you are interested in helping or being part of the UberROM project (name subject to change), tell me here, if you're a dev with experience on porting ROMs and tinkering with the AOSP, let me know, I could use all the help I could get!
Thank you!

Related

Rom Help with unique phone

Hey guys,
I will be getting an android 4.0 phone from china here in a couple days. It doesnt support updates, or anything and I'd like to get Jelly Bean on it. I also have a Captivate I'd like to start developing roms for. I need the simplest explanation of how to make custom roms from aosp for either phone, or if there is another way, or if someone would like to take on the job that'd be great as well. any and all help is greatly appreciated.
>>>>>SEARCH<<<<<
(That's the simplest thing you can do)
If the phone from China is really that unique the chance of you going from knowing nothing about developing to making a working JB ROM (which would require writing drivers) is next to zilch. But if you really want to learn and are willing to put in the effort there is an endless supply all over the internet (and within the hundreds of other threads like this).

tips and pointers to start devin>>

i had always meant to do some developing but the drop in activity i realized when i moved from the sensation to the rezound really compelled me to start plus i have some work that i really have to do and really dont want to do so you know how it goes. Anyway to it
i started by googling how to build android roms which lead me to xda university giving me a nice expaination as to the various parts of android which i was already familliar
another search lead me to the offical how to build android from source page. i had a few concerns so i thaught i would ask here
i have knowlage building various web applications(php,js,ect) and not the let the fromework so this for me kinda apps i like thinking and innovating. i have a little experience with c++(i was at the stage of learning a gui when my old laptop crashed) so i think i have atleast good enough programming experience to catch on to java at a nice pace. Am currently reading and following googles nice little guid on developing android. Am in the process of setting up work envo (already got ubuntu 12.04 up). and thaught i would just leave a post here to see if anyone had any advice for me?
what i wanna do is be able to port for us,build original roms AOSP they call it for us, build and or port sense roms for us and eventually get to the point where i can get us sense5 or help neo(or any other dev) help us get sense 5. oh and i think i would like to build/modify kernels as well. oh oh and being able to invent exploits to get root or s-off for devices i might get in the future.
Question: while i was reading i was seeing where the buiding process was doing alot of synceing with google servers ect. i dont actually want to submit whatever garbage i might write to them while am testing so im still on the right track following the guid here correcto??
short version: I wanna build android custom roms ect not just edit files and put it out am i on the right tract following the guid here (i already know a lil programming)? http://source.android.com/source/initializing.html
any advice/resources/links welcomed
oki am on the page that says "building and running" i dont see anything for our device am guessing thats because development from aosp has stopped for us and thats where ppl like neo and cyanogen make thier magic. what is the next tut or read for me?
Try this. You could always pull Neo's CM 10.2 repos instead of the 10.1.
http://signatures.mobile-overload.com/wp-content/uploads/2013/07/sig-cm-5.png

[Q] Helping a dev with rom

Hi,
I've been using XDA for a while now, and with the help of many amazing devs I've managed to flash custom roms to all my older devices no problem! Recently I've been waiting for a dev to make changes to an existing kitkat rom, to fix a bug and I'm becoming a little impatient. I know everyone has their own lives to attend so I'm not complaining, rather I'd like to try and help this dev with the problem as I have quite a lot of experience with Android apps. I've read up on the CM wiki the sort of things that are involved in debugging roms etc. so I know that I'll only be able to help with the framework (as I know no C/C++).
So my question is, are there any ways I can help them, and will my help be appreciated considering the skills I have? I also have a decently fast computer too so I have a feeling I could help with building the rom.
Thanks.
Roarster31 said:
Hi,
I've been using XDA for a while now, and with the help of many amazing devs I've managed to flash custom roms to all my older devices no problem! Recently I've been waiting for a dev to make changes to an existing kitkat rom, to fix a bug and I'm becoming a little impatient. I know everyone has their own lives to attend so I'm not complaining, rather I'd like to try and help this dev with the problem as I have quite a lot of experience with Android apps. I've read up on the CM wiki the sort of things that are involved in debugging roms etc. so I know that I'll only be able to help with the framework (as I know no C/C++).
So my question is, are there any ways I can help them, and will my help be appreciated considering the skills I have? I also have a decently fast computer too so I have a feeling I could help with building the rom.
Thanks.
Click to expand...
Click to collapse
Ask them. Or ask their permission to use their ROM as a base, make some actually meaningful modifications, and release it. But as too your "skills" I didn't see you state what they were, and if you have to ask then probably not. Don't stop reading/learning though, you'll only get more knowledgeable.
thewadegeek said:
Ask them. Or ask their permission to use their ROM as a base, make some actually meaningful modifications, and release it. But as too your "skills" I didn't see you state what they were, and if you have to ask then probably not. Don't stop reading/learning though, you'll only get more knowledgeable.
Click to expand...
Click to collapse
Ok, I was thinking along the lines of making modifications and then pushing them to a git repo. Maybe they don't have one, I'll go ahead and ask. As for my skills, I was saying in my last post that I have quiet a lot of experience developing Android apps. Do you know what % of rom editing is Java based vs C/C++?
Roarster31 said:
Ok, I was thinking along the lines of making modifications and then pushing them to a git repo. Maybe they don't have one, I'll go ahead and ask. As for my skills, I was saying in my last post that I have quiet a lot of experience developing Android apps. Do you know what % of rom editing is Java based vs C/C++?
Click to expand...
Click to collapse
There is no hard/fast guide on what "rom-editing" is. Are you wanting to contribute to kernel development? Better know a lot of C. Wanna roll a cool application for a ROMs special settings? Java is what you want. What I'm getting is you know more Java, so why don't you write and application that you think will solve a problem, then talk to a developer about including it in their ROM?

Concentrate on 1 ROM

Hello,
I'm not android dev (i wanna be, but idk where to start) and I appreciate your work guys there. But, can you just concentrate on 1 ROM, that will work properly-sh?
Pepa489 said:
Hello,
I'm not android dev (i wanna be, but idk where to start) and I appreciate your work guys there. But, can you just concentrate on 1 ROM, that will work properly-sh?
Click to expand...
Click to collapse
That will never happen and the reason is quite obvious. Simply put, the way I see it is that each user has different needs of the ROM he chooses and you can't just add every feature of every custom ROM into a single ROM because then the ROM would be heavy and kind of bloated. That's just my personal opinion though. Also, it's difficult to organize all the developers and make them work under one project because like a user, each developer has different opinions and programs his own way.
jimakos98 said:
That will never happen and the reason is quite obvious. Simply put, the way I see it is that each user has different needs of the ROM he chooses and you can't just add every feature of every custom ROM into a single ROM because then the ROM would be heavy and kind of bloated. That's just my personal opinion though. Also, it's difficult to organize all the developers and make them work under one project because like a user, each developer has different opinions and programs his own way.
Click to expand...
Click to collapse
First of all, I'm talking about MTK. This post was moved from dev mtk thread. It's totaly different world. Kernel is broken AF, but they are still compiling new ROMs that arent working well (Magnetometer, Proximity, RIL, Fingerprint...). I know it's mainly my fault that i bought a MTK phone :/
Dude's got point but it's hard to just 'merge' all the projects out there. It's easier for the devs to manage the work themselves, even if the quality of their work would be higher if they incorporated. Working with other people is not suitable for every person and obviously the motivation to do it for the sake of better results is not enough to make them do it.

don't read this post & don't waste time

:good:
First of all your post's title is very misleading, edit it.
Look brother, it's inappropriate to make posts like this. Developers do all the hard work for free, but they have a life too. It takes time, skill & a lot of trouble shooting to develop a ROM. So just give them some time, okay?
If we keep nagging them, the devs might feel annoyed & lose their interest in developing for our device completely. Tell me, is that what you want? The problem is we only want to take everything for free, giving nothing in return - not even a little bit of patience!! That's not how the world works.
Android 10 isn't out for this device yet, but we already have 4 Android Q based custom ROMs for A3. You can try those in the meanwhile.
No hard feelings bro, just wanted to share my thoughts with you. Thank you.
evanB70 said:
First of all your post's title is very misleading, edit it.
Look brother, it's inappropriate to make posts like this. Developers do all the hard work for free, but they have a life too. It takes time, skill & a lot of trouble shooting to develop a ROM. So just give them some time, okay?
If we keep nagging them, the devs might feel annoyed & lose their interest in developing for our device completely. Tell me, is that what you want? The problem is we only want to take everything for free, giving nothing in return - not even a little bit of patience!! That's not how the world works.
Android 10 isn't out for this device yet, but we already have 4 Android Q based custom ROMs for A3. You can try those in the meanwhile.
No hard feelings bro, just wanted to share my thoughts with you. Thank you.
Click to expand...
Click to collapse
i used miui before & bored of stock rom limited features.. used two custom rom they aslo limited features.
that's why want miui or Oxygen os. nobody give any attention if i ask for this two rom
sorry.. i give up ?
soliman.sohan said:
i used miui before & bored of stock rom limited features.. used two custom rom they aslo limited features.
that's why want miui or Oxygen os. nobody give any attention if i ask for this two rom
sorry.. i give up ?
Click to expand...
Click to collapse
I see. Stock android is not everyone's cup of tea. You see, this phone runs on stock android, so every custom rom for this device is going to be based on stock/AOSP. You probably won't get that cartoonish MIUI for this device. GSIs? May be. But those things are always riddled with bugs. Talking of Oxygen OS, there isn't a whole lot of deference between Android One & OOS. Besides, you'll lose the ability to use your cameras to their full potential - a common problem with custom roms in general.
You really should have gone with CC9e instead of A3.
I, for one, enjoy clean, fluid & bloat-free Android. Every feature you get on MIUI can be duplicated on stock rom with the help of some useful apps & a bit of creativity
Basically, stock android is like soft clay. You can customize it to any shape you like (granted, it does require some effort); you can't say the same for 3rd party skins like MIUI.
I thought that after more than 2 years since Mi A1, people finally learned that if they want MIUI, they need to buy a phone with MIUI and not Android One. What puzzles me even more, Xiaomi offers EXACTLY the same device with/without MIUI, yet people jump on the Android One train and complain.. Sorry for being off-topic, but I'm amazed by this behavior since the beginning of Xiamoi's Android One line
evanB70 said:
I see. Stock android is not everyone's cup of tea. You see, this phone runs on stock android, so every custom rom for this device is going to be based on stock/AOSP. You probably won't get that cartoonish MIUI for this device. GSIs? May be. But those things are always riddled with bugs. Talking of Oxygen OS, there isn't a whole lot of deference between Android One & OOS. Besides, you'll lose the ability to use your cameras to their full potential - a common problem with custom roms in general.
You really should have gone with CC9e instead of A3.
I, for one, enjoy clean, fluid & bloat-free Android. Every feature you get on MIUI can be duplicated on stock rom with the help of some useful apps & a bit of creativity
Basically, stock android is like soft clay. You can customize it to any shape you like (granted, it does require some effort); you can't say the same for 3rd party skins like MIUI.
Click to expand...
Click to collapse
sorry to say you don't realy know indeep about miui.. use oos or miui 1year with using then full feature then you will get your own ansr.. stock is simple & powerful
& one thing if you use telegram you can understand between what's & telegram..just think miui is telegram & stock is like whatsapp
and sorry guys.. if you think i am not respecting dev
i will sell a3. & next time will not post like this
(for new law in our country i can't buy mi cc9e or better version for money)
??

Categories

Resources