That generally works fine, especially for the same Android version. However, as Android evolves, so do the driver requirements. Yesterday’s driver may simply not work with today’s Android. Only the driver supplier (typically the likes of Qualcomm) could realistically create an updated driver. Otherwise, extensive reverse engineering would be required.
I bet that this isonly possible because someone got the drivers for display, touch, camera, radios, etc, ...in binary form from the last oem image and put in the new one. sometimes they will backport the last kernel from android 5.1 into a 6.0 image so the binary drivers still work
Indeed I use an open-source stripped down Android variant. It only required an hour of fiddling one time (to learn how to, flash it and set everything up the way you do on a new phone), works as breeze since then.
So would you please help me to find an ROM with an up-to-date Android Common Kernel for my i9300 Samsung Galaxy S3?
AFAIK, the only way to run it with working drivers for all hardware components, are ROMs which use the rusty 3.0.101 Linux kernel from back in the day and I think that is what DCKing is referring to. If you want to create a new ROM, you either have to use the old kernel and have an upper Limit of Android 7.x (in this case) or you have to accept, that not all components are supported (e.g. no GPS).
I would be glad if the situation would be different. Maybe it is different for phones you buy today?
Whether you are able to put it on your phone in a working state is then the question though. You would need drivers for all parts which might be closed source and not compatible with your build.
Right now you can get vanilla Android on most recent devices, same image for all of them thanks for the Treble project, that separated kernel and hardware drivers from Android system.
I did just that with a Google Pixel 3a, but you should be able to do that with any Google Android Device. I actually compiled AOSP and LineageOS from source.
But to keep in mind, those all have proprietary Drivers.
One thing I've noticed when surfing around various Android forums is that people who build new ROMs or port them between phones often include a list of things that do and do not work.
He says in the video that pretty much everything works, which I'm inclined to take with a grain of salt.
Previously Android phones were allowed to be released each with modified unique kernels. All new phones which ship with Android 12 however must use the same generic Android Common Kernel, and any device-specific drivers are then attached via kernel modules.
So basically from September-ish all future Android phones should be able to boot off the same image, or at least a Generic System Image.
No, it doesn't. Not through the OEM. The last version of Android was Marshmallow which is two major versions behind the most current.
Sure, you can flash it yourself to the latest version, but there's no guarantee that it'll work. In my book, not having support from the OEM on the latest possible version of Android that can be loaded on your device does not count as having access.
Might not be an option for the phone as it takes a while for alternative OSes to add support for particular hardware, so generally only older models are compatible.
not a problem at all. now your samsung or some unknown brand, who knows. I'm sure your 12 year old iphone got the latest and current bluetooth driver though.
not everyone around me is stupid. just the guy being purposely dense. you.
reply