got my watch yesterday and mod'ed it with the custom rom. its amazing and all, but there are things that could be more useful but they are based on the default chinese rom.
so, are there plans to build a more custom rom, with ideas and suggestions from a community?
The problem is the lack of source code. Huami didn't release the kernel source, and whilst a generic board version made for the board the watches are based on does boot (with the Huami kernel anyway), it's not ideal. Through this method it's possible to run a "stock" (AOSP) based Android 5.1, but that's useless so I'm not bothering uploading it
Related
Hi.
I am a noob, not a techy
just curios - how can your devs build ICS roms when Samsung themselves did not build/create/honed/refined the Vibrant for Android 4?
What I am trying to ask is, how can your devs manage to control the hardware via android 4, if Samsung did not supply the codes/drivers/source?
Thanks
I'm not 100% sure but I think I read somewhere you can use the source code to build a ROM and then they used the Gingerbread bootloader/kernel and from there it's debugging.... again I could be wrong.
I think they took the source, and compile the source with the characteristics of the device. then applications that do not work, modified or exchanged for other versions of other rom, like the kernel, and other modifications, which is why the rom, there are many versions which fix bugs Version earlier after many users try it. (an example of this is the ICS Passion, which is now in its version 13)
Well passion is based on cm9. Which is aosp rom using source code android releases. Basically if you have drivers for hardware and a device tree you can use that source to build for any device.
Wherelse Samsung roms are usually not directly from source but just modded firmware from Samsung leaks. Oems do use close sources drivers though, usually better and get more out of hardware.
Sent from my SGH-T959 using XDA App
Hi! This is maybe a general dev question, but I'd like to get an answer anyway:
what is exactly the link between an Android release and the kernel it works upon?
I noticed most recent releases use 3.0+ Linux kernels, and others (like the DSCs) use the Phoenix Universal Kernel, which is based on a 2.6.35... So I wonder: is ICS/JB in any way dependant on "newer" kernels?
I understand the answer must be closer to "no", since the pre-alpha build also uses a fork of the PUK, but the fact that it uses a *different version* makes me wonder how much work does it take to get a kernel ready for a newer release, and most importantly... why?
Thanks a lot! Total n00b here, but eager to know more.
Newer kernel not required at least for ICS.
All GB/ICS kernels are based on this kernel (and it's a Dell's lie about using same sources for 407 release as SoD was fixed there without switching timer source):
http://opensource.dell.com/releases/streak/4.05_and_4.07/
kibuuka successfully applied kgsl/genlock patch and it's the only thing actually needed for ICS.
List (a bit old) of changes in Phoenix kernel and later derivatives:
http://forum.xda-developers.com/showpost.php?p=25291276&postcount=3812
Hello,
So my brother bough a chinese smartphone. Many chinese apps where preinstalled and I have been able to remove them, so you wouldn't notice it is a chinese device. However it would be neat if this phone would have proper AOSP.
The current ROM is almost AOSP, minor modifications have been done. This made me curious, would one be able to compile AOSP from source, and use the original kernel (if compatible)? Is a kernel extractable from a ROM to be used in another? Do you need the sources from the manufacturer in order to succesfully build AOSP?
Please note I'm not trying to do this, I'm just curious if it could be done. I have done a fair amount of research but most of the tutorials are about compiling kernels, something I DON'T want to do.
_Roysten said:
Hello,
So my brother bough a chinese smartphone. Many chinese apps where preinstalled and I have been able to remove them, so you wouldn't notice it is a chinese device. However it would be neat if this phone would have proper AOSP.
The current ROM is almost AOSP, minor modifications have been done. This made me curious, would one be able to compile AOSP from source, and use the original kernel (if compatible)? Is a kernel extractable from a ROM to be used in another? Do you need the sources from the manufacturer in order to succesfully build AOSP?
Please note I'm not trying to do this, I'm just curious if it could be done. I have done a fair amount of research but most of the tutorials are about compiling kernels, something I DON'T want to do.
Click to expand...
Click to collapse
It is definitely possible, but will take many hours of work of you want to achieve a stable daily driver state. Usually the kernel will need modifications to make it work with the AOSP ROM.
Sent from my SGH-T999 using Tapatalk 2
Say the rom uses a kernel that works with AOSP, can one build the Android OS using the already compiled kernel from the device?
Has anyone tried to put the firmware of devices from meizu, xiaomi? For example, CM 13?Supposed to work? Support scanner available from meizu , and the seams are already stable
It's not possible to do that. Any ROM that you load into a phone must be built for that particular model. Although non-stock ROMs are available for many phones, including the P9000, they are all built using the kernel (which is the bit of code that controls the hardware - device drivers, if you like) of the stock ROM supplied by the manufacturer. So you can tweak the original ROM and sometimes add new features (if you have the skill to do it, of course, it's not a simple task), but you can't just load up CM13, for instance, from a Meizu phone.
RMcT said:
It's not possible to do that. Any ROM that you load into a phone must be built for that particular model. Although non-stock ROMs are available for many phones, including the P9000, they are all built using the kernel (which is the bit of code that controls the hardware - device drivers, if you like) of the stock ROM supplied by the manufacturer. So you can tweak the original ROM and sometimes add new features (if you have the skill to do it, of course, it's not a simple task), but you can't just load up CM13, for instance, from a Meizu phone.
Click to expand...
Click to collapse
thank you for such a detailed explanation, very grateful???
Hello everybody. I love this community and I have been lurking for a long time.
I have noticed on a foreign language forum that some people were offering a custom rom for my android 9 TV box.
The chinese box is based on a s905x3 CPU and has a mediatek wifi chip for which it is hard (if not impossible to find the wifi drivers).
The site claims that the image was made by modifying the stock rom that came with the box. Is this possible or do all custom roms need to be build from the source?
The custom rom I want to make is going to replace the launcher with kodi.
I am prepared to build the whole rom from source but I do have a couple of questions.
Since the mediatek wifi drivers cannot be found how would I go about including the binary for the wifi?
I have noticed that the box that I have uses a .ko (kernel object) module to drive the wifi chip.
Can I include these kernel objects in build? It is a shame that the kernel is built as a 32bit system. Would that mean that I can only compile a 32bit kernel if I were to reuse those kernel modules and binaries?
Another idea is to perhaps use the kernel from coreelec in my build since it seems to include a lot of drivers.
Is it possible to use a kernel from something like coreelec but use the source from AOSP for the rest of my build?
Is there anything else that I should be aware of?
Thank you all!!!!
Can anyone give me any hints to any of the questions?
Essentially I want to swap out the stock launcher for Kodi. What is the easiest way to do so?