Obviously this does something to the touch panel but I can't find specifics anywhere. What does the TP update include/fix? Any reason to stick with old TP??
Until source is released aosp are incompatible with the new driver, all stock based roms with 3.16 kernel should be fine
Related
I want to cook my own ROM, using osKitchen, but can only seem to download the latest official HTC ROM, based on V 3.14. It uses the 21916 Build, which has the Windows button, etc, at the top.
I would like to get hold of a 21684 Build, which has the nice buttons on the bar at the bottom of the screen and a very useful Action Button. One of NRGZ28's Energy ROMs uses it.
Problem is, I can't seem to find a 21684-based official ROM to download. Can anyone point me in the right direction?
---
Pete
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
Hello,
The initial build of Paranoid Android ROMs allowed for the total disablement of the native touch keys therefore allowing you to use only the on screen keys native to ICS. I believe the version was 1.2 as 1.3 and up no longer has this option.
Does anyone have a copy of the 1.2 version of Paranoid Android? I didn't have any issues on the ROM and I know it lacks features of what the newer Paranoid ROMs have but I love the fact that you could completely disable the touch key buttons.
Or if there are any other ROMs with the same capability (all though I doubt there is), please tell me, as I have tried all AOSP, AOKP, CM, and Sammy ROMs and have not found this feature again.
Thank you for your time!!!
AC
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
I just wanted to know if there is any flashable version of the latest security patches for any AOSP based roms? I'm currently running a CAF variant of Euphoria 1.1 on my OnePlus One and it has everything I need as far as features and I don't see any reason to upgrade to 6.0 yet. If anybody can point me in the right direction would be helpful. Even if I have to build my own version of the rom I'll do so as I do have some building experience (some, not alot).
Thanks