Problem is, a short term goal like that can lead to massive headaches later on if not done properly.
I can't argue with that.
Maybe pulser can add some guidance to the OP. Maybe a "best practices".
Problem is, a short term goal like that can lead to massive headaches later on if not done properly.
I have build Omni for Yuga (Xperia Z)
Here is thread >> http://xdaforums.com/showthread.php?t=2494622
I will merge device from my local to github when i get some time and apart from that you are officially supporting XZ
So, let me know how i would call my build either unofficial / official
Thanks
The Sprint HTC Evo LTE (qcom One X variant) is booting and runs decently, it still needs a lot of work before it's fully functional but it's off to a pretty good start.
Device: https://github.com/Haus1/android_device_htc_jewel
S4 common: https://github.com/Haus1/android_device_htc_s4-common
Kernel: https://github.com/Haus1/android_kernel_htc_msm8960
Blobs: https://github.com/Haus1/proprietary_vendor_htc
Thread: http://xdaforums.com/showthread.php?t=2495109
Some of the proprietary libs needed to be changed from the ones on the muppets. I manually edited my roomservice.xml to include the ones from my repo but haven't added it to the dependencies list yet.
Added@Entropy512
Sony Pollux:
Device Tree
Sony Honami:
Device Tree
Rhine common tree
Kernel Tree
audio-bfam
display-mdss
Media-v412
Hey do you think this would work for the One S? If you wouldn't mind sharing which are the changed libs as well as the edited roomservice that would be great.
I tried, but had all sorts of device config errors at the build menu so maybe what you have will do the trick.
Sent from my One S using XDA Premium 4 mobile app