Hello everyone,
I don't know if this is the right place to ask, please move to the appropriate section if needed.
My question - let's say I have a rom on my device that is no longer maintained by the developer, is there any way through which I can manually update Android security patches or maybe maintain the rom myself??
** considering that I don't have any custom kernel available or its no longer updated at all.
Can anyone help me with this?
good question
Related
Hi Guys
The problem I see for most ROM developers is that they only provide full releases , so existing ROM users should reflash the whole ROM for only a few minor upgrades and the worst part is that they may lose some apps due to upgrade. like the latest HyDrOG3N-ICS upgrade which deletes all google apps and you need to flash them separately again after upgrade.
So I am going to make incremental updates for the ROM I use and share it with community. lets say I have two full releases named ver1 and ver2. is there a way to compare these ROMs and create a CWM flashable incremental update from ver1 to ver2 ?
I know it may not be as easy as it sounds , just point me to right direction and tools and I will do my homework
I would have thought the starting point is to ask the dev for his permission .
jje
My question here is a technical question , has nothing to do with dev.
Lets say I want to do it for myself
Although I dont think it needs devs permission , do all devs have official permission from google ? NO , android is an opensource project and anyone can fork it respecting the GPL. also the thing I am going to accomplish here is not modding any ROM , just incremental updates for users. the user will still get the original ROM. it is for community , not for devs
Hi guys, i'm new to Android development. I built Paranoid Android from source for TF101. The ROM was nice and i'm happy with my ROM. So now i'm so curious about what developers do regarding building a ROM and updating it.
1. If the ROM had bugs/problems, how can i analyze it and find the root cause of the bug?
2. How can i fix the bug? Do i need to edit a file in the ROM?
3. Every ROM that had updated build from source has an changelog, how can i know what is the changelog?
I'm sorry if the questions are quite noobish. I'm new with it. Thanks
Hi,
I had a question about Custom Android ROM and hoping you will guys will guide me in the right direction. I am starting a company wherein we are building a new touch screen h/w device for the fitness industry. We want this device to run on Android. Naturally we want to hire android developers to build the system. (FYI - I am not a programmer, so please don't assume I know anything about programming/android). Here are some questions, I am hoping you can answer:
1. Since this is not an app, but a new h/w device itself, I am guessing I need to modify the Android ROM and customize it to our needs...am I correct in this assumption?
2. Is there particular android rom that I need to focus on ?
3. Do folks who know how to build an app, can do this rom customization or am I looking for folks with different skillset?
4. What kind of skillsets should I look for in people before I hire them for this job?
5. Any other points that you guys can help me with, will be highly appreciated.
Thanks
Hello, I will try build my own AOSP ROM but I wanna have clarify to some questions before I do.
I readed top-to-bottom this thread, is it still usable to build Android 5.1? With some changes, of course.
I noticed the process of building do not changes a lot when is to another device, I wanna know here the process changes. On this part the user instructs to download the driver files. I wanna build the AOSP to delos3gub (Samsung Grand Quattro), which drives should I get?
Also, in "#3 Choose your Device!" at the same thread (here), the user says:
If you're on GSM, you want to use "maguro." If you're on Verizon, you want to use "toro."
Click to expand...
Click to collapse
Which should I use?
Thank you, and sorry my english
Starting from Android P, Google started the implementation of system-as-root as future of Android and Android 10 mandates all new released devices must use system-as-root...
Anyone could tell me what's the possible reason and benefit/drawback) of this system-as-root stuff?
I am not asking for how it works, Google and various sources already explain this pretty well. I just want to know why, not how of using system-as-root....
Thanks!
If this question doesn't belongs here, moderator please move to somewhere more suitable....
Hey man,
I just asked myself the exact same question, didn't find an answer yet. Do you know the benefit of SAR by now?
which forces the build to merge the root file system into system.img then mount system.img as the root file system (rootfs).
@lssong99
@Doomkopf
Important System and Security and Privacy fixes can now be sent directly to your phone from Google Play, just the same way all your other apps update. BTW a new APK-file format is used: APEX ( read: Android Pony EXpress )