Related
Donning a new name in favour of the new delicious version of Android... Welcome to the ThunderKat Project!!
Heavily based of my Flaming Monkey kernel configurations and the stock AOSP kernel source, here's my standalone kernel for the Nexus 10. I will maintain this independently.
It will always remain close to the AOSP exynos kernel for manta (Nexus 10) with a few useful tweaks and additions, but will not have any OC/UV, colour controls and any advanced customisation options. It is a stable kernel and will not have frequent updates.
This kernel uses the AnyKernel method and is ROM independent. I have tested this on 4.4 (Stock & AOSP) based ROMs.
Features:
1. Linux Kernel 3.4.39.
2. Based on AOSP KitKat MR1 kernel source for exynos/manta.
3. Built using the Google ARM GCC 4.8 toolchain with -O3 CFLAGS & AFLAGS optimisations & ARM Cortex A15 build optimisations.
4. Enabled Conservative & Powersave CPU frequency governors (in addition to Interactive, Performance & Userspace). Interactive set as default.
5. Preserve correct sysfs permissions on governor change.
6. KSM (Kernel Samepage Merging) support.
7. NTFS, F2FS, EXT4 xattr (extended attributes) support.
8. Networked file systems support (NFS V3, NFS V4 & CIFS).
9. HIDRAW support (supports non-conformant HID devices).
10. Support for more input devices (keyboards, mice & joysticks) including Logitech Unifying devices.
11. Support for USB serial modems (PPPOE).
12. Support for multi-card readers (multi-lun devices). This allows you to mount multiple cards using a multi-card reader. May need an app like StickMount. (Credit @nvertigo67)
13. Removed SWAP support.
14. Removed some un-needed debugging.
15. Increased thermal throttle limits
16. Scalable CPU frequencies
Changelog [2014/08/24]:
1. Built using Graphite optimized GCC4.8 toolchain
2. Added ROW & SIO I/O schedulers
3. Set ROW as default I/O scheduler
4. Upstream F2FS changes
5. Miscellaneous I/O improvements
Changelog [2014/06/05]:
1. Update to AOSP 4.4.3 kernel source (kitkat-mr2)
2. Added F2FS filesystem support
Changelog [2013/12/15]:
1. Update to AOSP 4.4.1/4.4.2 kernel source (kitkat-mr1)
Changelog [2013/11/21]:
1. Initial release
Information:
1. Flash using a custom recovery (TWRP/CWM).
2. This kernel is ROM independent and uses the AnyKernel method. Hence it uses the current ramdisk. You may have issues if this is flashed after a kernel with a custom ramdisk. If so, reflash your ROM and then flash this kernel.
3. Needs an unlocked bootloader.
4. Make sure you have at least 50% battery charge before flashing this.
Download:
ThunderKatKernel-4.4.4-20140824 (AndroidFileHost)
ThunderKatKernel-4.4.4-20140824 (Goo.im)
Archive (4.4.x) - (AndroidFileHost)
Archive (4.4.x) - (Goo.im)
Archive (4.3.x) - Unsupported
Archive (4.2.x) - Unsupported
Source:
GitHub
Disclaimer:
While I have extensively tested this and even though it is heavily based on the AOSP kernel, you may encounter issues. I will try to help you, but I will not take any responsibility if anything goes wrong. Please exercise caution.
Credits:
Google, Samsung, CM, AOKP, PA, ktoonsez, morfic, franciscofranco, Goo.im, AndroidFileHost
Reserved. Just in case
craigacgomez said:
Reserved. Just in case
Click to expand...
Click to collapse
Very cool! I will be trying this tomorrow, will have time to play with it. Nice to see KSM in it.
Nicely done. I'm running your kernel as we speak--snappy, snappy! No issues so far. :good:
Only thing left to do now is give it a catchy name like: "The CRAIGINATOR"
Wow, great news, thanks craig!
brGabriel said:
Nicely done. I'm running your kernel as we speak--snappy, snappy! No issues so far. :good:
Only thing left to do now is give it a catchy name like: "The CRAIGINATOR"
Click to expand...
Click to collapse
Thanks...and yes, I will be renaming my ROM and kernel to something more... well, appealing... when I restart the ROM project...
Once I'm at 50% I'll be all over this like a rash
Sent from my Nexus 10 using xda premium
Great job, runs great! Only issue is it defaults to cfq scheduler on boot even when I have it set to run deadline.
More of a preference than an issue.
This kernel is really good, I was very impressed by your previous Rom and look forward to the new Rom you said will be released later in the year (hopefully!). Your hard work is much appreciated. Using your kernel with Carbon Rom right now and it seems very stable.
Sent from my Nexus 10 using XDA Premium HD app
Yep, snappy, snappy!
Sent from my Nexus 10 using Tapatalk HD
this kernel works best on my N10. no reboot, no SOD and no battery drain.
my tablet is 10 days up without a single problem or recharge! :good:
i hope it will be continued in the future!
Yes, I will continue supporting this kernel... though there will not be many updates... the aim to to remain close to AOSP, yet provide some useful tweaks and additions... I will be building a newer version soon (having problems with the cross compiler on my work laptop, else I would have done it today)...
Hi!
Can I flash this kernel to the stock ROM?
And revert back when new android version comes out to OTA update?
Thank you
teodor_ch said:
Hi!
Can I flash this kernel to the stock ROM?
And revert back when new android version comes out to OTA update?
Thank you
Click to expand...
Click to collapse
Yes, this will work fine on stock...and you can easily revert back using the boot.img from the factory images provided by Google...
Updated release in OP...
Does this have the latest wifi and or gpu drivers? I know wifi drivers are kernel level, not sure about the gpu though. Anyways, its a very nice and smooth kernel. It's been a baron wasteland in mantaland. I guess Google didn't sell many of these.
I just installed the kernel, very smooth, I was having shutdowns on Trinity latest and RootBox. Hopefully is not a ROM problem and this kernel fixes it, I really like RootBox.
Thanks for the awesome work and support.
Erik
situman said:
Does this have the latest wifi and or gpu drivers? I know wifi drivers are kernel level, not sure about the gpu though. Anyways, its a very nice and smooth kernel. It's been a baron wasteland in mantaland. I guess Google didn't sell many of these.
Click to expand...
Click to collapse
I have yet to incorporate the updated wifi and gpu kernel level drivers... I will be working on these soon...
Anyone here with sufficient kernel knowledge to merge the updated mali graphics drivers (http://malideveloper.arm.com/develo...n-source-mali-t6xx-gpu-kernel-device-drivers/)... There are a few updates that are beyond my kernel & C/C++ capabilities... like osk has been replaced by kbase... Please PM me if you can help!! Thanks!
Great work on this kernel! First time reaching 9 hours on screen time. Paired with Mr Robinson AOKP.
Qualcomm Optimized Dalvik Cache Upgrade (for 4.4/4.4.x ROMs)
Everyone is talking about ART on 4.4 right now and once it is made final I imagine it is going to be a very impressive run-time...
It isn't here yet though and thanks to kszaq over in the Nexus 4 forums we have a Qualcomm-Optimized Dalvik library that has shown compatibility with the Nexus 4, the Galaxy S3, S4, and improves performance of the Dalvik Cache!
I do not own a Optimus G, but I would like to. I also know from researching your devices that you all have a Qualcomm processor in your phones and will likely see a performance increase from these files the way other devices did.
I stumbled across this information in the Verizon S4 thread here which shows the benchmark improvements on the S4 and I figured, "why not my phone?" Turns out it worked great on my phone raising my benchmark scores and improved overall responsiveness.
In his FAQ he mentions that if you are on CM11 4.4.x, or something based on that build, that it may have an improved bionic library installed and it isn't necessary to flash it. Having said that I flashed my phone both ways and saw that optimized-dalvik alone and got the best score. Try it on your 4.4 set-ups and let us know what works best. At the very least we can fill this thread with synthetic benchmark pics!
Bottom-line
Flash these files and enjoy the responsiveness boost (4.4 and 4.4.x only)
How to install:
1.) Read the Q&A below!
2.) Copy both files (optimized-bionic and optimized dalvik) to your internal or external SD
3.) Reboot into recovery and make a nandroid backup (always)
4.) flash optimized-dalvik zip (optimized-bionic is optional)
4.) Wipe Dalvik Cache
5.) Reboot and enjoy!
Make sure to download the restore files to your phone as well so if for some crazy reason it doesn't boot you can go to recovery and reflash the stock files.
Here is the original thread and please thank kszaq while you are there: http://forum.xda-developers.com/showthread.php?t=2546120
Here is the Q&A that kszaq set-up on his post:
Before using, please read the following Q&A.
Q: Will this void my warranty?
A: Yes. Flash at your own risk.
Q: Can I use it?
A: Yes, if you're on any 4.4/4.4.x ROM.
Q: How does this work?
A: This patch consists of two files that include optimized bionic and Dalvik libraries for any KitKat ROM.
Q: What is bionic?
A: It is a vital system library that provides i.a. basic math and memory access functions to every other library and application in Android.
Q: What is Dalvik?
A: In short, Dalvik is a virtual machine in which every not-native-code app runs. You can read more about it in a Wikipedia article.
Q: How do I benefit from this patch?
A: In two ways: bionic patch provides faster memory access and optimized some of the math operations, dalvik provides optimized Dalvik Virtual Machine library that allows faster code execution.
Q: Do I need this patch?
A: It depends on what ROM you are using:
Originally Posted by xboxfanj
if you're on stock ROM, you'll benefit from flashing both bionic and dalvik patches, if you're using a custom ROM, you most probably don't need bionic patch, as these are already included in most custom ROMs. You'd benefit only from flashing dalvik patch (if it's not already included by your ROM maintainer, of course), don't use the bionic patch on CyanogenMod, PSX and probably others, because they already have more optimized versions!
Click to expand...
Click to collapse
Q: Why aren't these patches included in stock ROM?
A: As for bionic - I don't know. Maybe that's because Google didn't want to include vendor-specific optimizations in AOSP or maybe simply because Qualcomm never posted them in Android Code Review to be merged. As for dalvik - because they are closed-source. Here'a a good explanation by @xboxfanj:
Quote:
Originally Posted by xboxfanj
Part of the point of Nexus devices is that AOSP can produce nearly identical images minus GApps. Google would not use a proprietary dalvik as that is one of the core libraries. Using a proprietary dalvik would undermine AOSP. Although, an open libqc-dalvik or even just giving us that binary would be nice. Google could have a device specific extension similar to the adreno extensions onto renderscript and egl for dalvik. Proprietary dalvik won't happen, but an adreno extension could be cool.
Click to expand...
Click to collapse
Q: Where do these patches come from?
A: These have been authored by Qualcomm. Bionic patch comes from Code Aurora Forum, Dalvik library has been extracted from Moto X 4.4. ROM. Another good read by @xboxfanj:
Originally Posted by xboxfanj
CAF has all Qualcomm's bionic patches and slight dalvik tweaks, however, the dalvik patches that are used here in the Moto X and any QCOM (non-Nexus) device, are mostly closed source. If you look at the change here: https://www.codeaurora.org/cgit/quic...739455dfd3cf57
Click to expand...
Click to collapse
You will see that most of that change is supporting other libraries (libqc-opt and libqc-dalvik), which is where their optimizations are. Unfortunately, both of those are closed source. libqc-opt is included in QCOM ROM zips as a shared library, so we can use that, however, libqc-dalvik is a static library, so we can't pull that from anywhere, as it is included in the libraries themselves and not put in system. This means that our only option to get all of Qualcomm's dalvik optimizations is to use their binaries rather than building from source, since building from source would mean missing any optimizations brought by libqc-dalvik, libqc-sqlite, and libqc-skia (the last two haven't been included in any patch, but are QCOM static libraries).
TLDR: QCOM's dalvik optimizations are closed source, so we are forced to use their binaries.
Remember to thank @xboxfanj for his very useful posts!
Q: What is the reason for including installd file?
A: The installd binary is from stock Nexus 4 ROM and is included for compatibility with CyanogenMod and CM-based ROMs. This is because CyanogenMod changed installd to work with their dexopt-on-cache (see here: https://github.com/CyanogenMod/andro.../cmds/installd) and it you don't flash stock installd you'd get hundreds of FCs and unusable ROM.
Q: How do I use this patch?
A: Simple flash it over your current ROM in recovery. Remember to wipe Dalvik Cache after flashing. Full wipe is not needed.
Q: How do I revert?
A: Simply flash over your current ROM and wipe Dalvik Cache afterwards. Full wipe is not needed.
Q: Can I flash it over an ODEXed ROM?
A: Yes, but it is strongly recommended to use a deodexed ROM if you want to use Dalvik patch.
Q: How will this affect my battery life?
A: It will be at least the same, if not better. Better performance = less CPU time spent on calculations = better battery life.
Q: I don't see any performance gains in some app, why is that?
A: The dalvik patch doesn't affect apps that use native libraries, i.e. you won't see much performance gain in Chrome etc.
Q: I'm on X kernel, can I use it?
A: Yes, use it with any kernel you like.
Q: Can I use it on other devices?
A: Yes, you can use this patch on every Krait device that uses AOSP-based ROM (examples: Nexus 5, Nexus 7 2013). Don't flash it on stock ROM on non-Nexus devices, as they already include these optimizations (that includes Galaxy S4 and HTC One Google Play editions!).
Q: What if I use it on stock ROM and OTA arrives? Can I install the OTA straight away?
A: You can't. You have to revert to stock libraries first. Keep in mind that every modification to stock ROM can mean problems when installing an OTA. You should revert to fully stock ROM to properly apply an OTA. For your courtesy, there's a revert ZIP attached for KRT15S and KOT49E ROMs. Remember that the safest way it to flash system.img from a factory image before applying an OTA once you made modifications to your /system partition!
Q: Can I use these patches on 4.4.1/4.4.2 stock ROM (KOT49E/KOT49H)?
A: Yes, you can.
Q: Can I use ART with this patch installed?
A: Yes, but you won't see any performance gains. In fact, with this patch Dalvik is faster than ART. I suppose ART will supersede Dalvik in performance in the future, but not yet.
Q: Where can I see some benchmark results before I flash?
A: Head over to Nexus 4 Benchmarks thread.
Q: Do I need to be rooted to flash this?
A: No. The only thing you need is custom recovery (CWM, TWRP etc.).
Q: Do I have to flash these patches every time I install an update/new ROM?
A: Yes.
KOT49E revert ZIP == KOT49H revert ZIP
Click to expand...
Click to collapse
Thanks to:
kszaq for the files and the spectacular Q&A
Xboxfanj for his contribution to the Q&A
prsterero for trying it on his S4 first
Google for taking a company name and turning it into common household verb...and for the awesome library files that were on their device
and I want to thank everyone who takes the time to develop on XDA. All of you make our devices do amazing things :good:
So does this work?
Sent from my Optimus G using Tapatalk
hazedabeast said:
So does this work?
Sent from my Optimus G using Tapatalk
Click to expand...
Click to collapse
It did for me and several others over in the Sprint S3 thread (not to mention all those in the S4 and Nexus 4 threads). I thought you all might be able to get some use out of it too, but since I don't have your phone I was hoping you all could tell me? If you decide to test it please post your results! :good:
9000 in Quadrant, something higher in Antutu, seems to make performance a bit better.
I've been running these for awhile. Already included on PSX and I'll put them in Vanir as well.
Test: CM11 (12-19 Nightly) LGOG Stock vs. Optimized libraries using AnTuTu benchmark.
Methods: I ran the benchmark four times on stock and four times with the optimized libraries. I threw out the lowest score of each set and averaged the remaining three. Between each run, I waited for the phone to cool down to 28ºC (using an IR thermometer directed at the hottest point at the rear top of the phone). Airplane mode was enabled, screen was at minimum brightness. I am not using a custom kernel nor any kernel tweaks.
Results (See attached chart):
For those unable to view the attached chart:
Stock / Optimized / %Change
Multitask: 3760 / 3775 / 0.4%
Dalvik: 1313 / 1820 / 38.6%
CPU Int.: 2196 / 2198 / 0.1%
CPU Float: 1843 / 2045 / 11.0%
RAM Operations: 919 / 1025 / 11.6%
RAM Speed: 970 / 965 / -0.6%
2D Graphics: 1627 / 1629 / 0.1%
3D Graphics: 6174 / 5976 / -3.2%
Storage I/O: 1146 / 1155 / 0.8%
Database I/O: 628 / 628 / 0.0%
aero449 said:
Test: CM11 (12-19 Nightly) LGOG Stock vs. Optimized libraries using AnTuTu benchmark.
Methods: I ran the benchmark four times on stock and four times with the optimized libraries. I threw out the lowest score of each set and averaged the remaining three. Between each run, I waited for the phone to cool down to 28ºC (using an IR thermometer directed at the hottest point at the rear top of the phone). Airplane mode was enabled, screen was at minimum brightness. I am not using a custom kernel nor any kernel tweaks.
Results (See attached chart):
For those unable to view the attached chart:
Stock / Optimized / %Change
Multitask: 3760 / 3775 / 0.4%
Dalvik: 1313 / 1820 / 38.6%
CPU Int.: 2196 / 2198 / 0.1%
CPU Float: 1843 / 2045 / 11.0%
RAM Operations: 919 / 1025 / 11.6%
RAM Speed: 970 / 965 / -0.6%
2D Graphics: 1627 / 1629 / 0.1%
3D Graphics: 6174 / 5976 / -3.2%
Storage I/O: 1146 / 1155 / 0.8%
Database I/O: 628 / 628 / 0.0%
Click to expand...
Click to collapse
Thanks for this bro :thumbup::thumbup:
Sent from my LG-LS970 using xda app-developers app
thanks for this!:good:
Thanks!
Sent from my LG-LS970 using xda app-developers app
Will this make my LG Optimus G on Cyanogenmod 11 with ART runtime enabled run faster and smoother? Using stock kernel that came with Cyanogenmod 11 ROM.
RegKilla said:
Will this make my LG Optimus G on Cyanogenmod 11 with ART runtime enabled run faster and smoother? Using stock kernel that came with Cyanogenmod 11 ROM.
Click to expand...
Click to collapse
Q: Can I use ART with this patch installed?
A: Yes, but you won't see any performance gains. In fact, with this patch Dalvik is faster than ART. I suppose ART will supersede Dalvik in performance in the future, but not yet.
Click to expand...
Click to collapse
No.
Holy Crap! Thanks for this!
These caused my LG Optimus G to lag while surfing online multiple times so I reverted back to ART runtime and all is back to fast, flawless operation.
Crap I flashed bionic on cm 11 I didn't get any errors or anything so that's good at least.
Thanks for this
Sent from my LG-LS970
Greatness83 said:
Crap I flashed bionic on cm 11 I didn't get any errors or anything so that's good at least.
Thanks for this
Sent from my LG-LS970
Click to expand...
Click to collapse
It's not bad. Just not necessary.
Sent from my Optimus G using xda app-developers app
aero449 said:
Test: CM11 (12-19 Nightly) LGOG Stock vs. Optimized libraries using AnTuTu benchmark.
Methods: I ran the benchmark four times on stock and four times with the optimized libraries. I threw out the lowest score of each set and averaged the remaining three. Between each run, I waited for the phone to cool down to 28ºC (using an IR thermometer directed at the hottest point at the rear top of the phone). Airplane mode was enabled, screen was at minimum brightness. I am not using a custom kernel nor any kernel tweaks.
Results (See attached chart):
For those unable to view the attached chart:
Stock / Optimized / %Change
Multitask: 3760 / 3775 / 0.4%
Dalvik: 1313 / 1820 / 38.6%
CPU Int.: 2196 / 2198 / 0.1%
CPU Float: 1843 / 2045 / 11.0%
RAM Operations: 919 / 1025 / 11.6%
RAM Speed: 970 / 965 / -0.6%
2D Graphics: 1627 / 1629 / 0.1%
3D Graphics: 6174 / 5976 / -3.2%
Storage I/O: 1146 / 1155 / 0.8%
Database I/O: 628 / 628 / 0.0%
Click to expand...
Click to collapse
I am runing stock E97510h unrootrd and my antutu numbers are pretty much the same as the aforementioned optimize ones. There is no doubt that LG stock rom is fully qualcomm optimized and i wonder why nobody extracted the qualcomm libraries from our phone and we are dealing with moto X's files and aosp kitk kat roms.
atsimeri said:
I am runing stock E97510h unrootrd and my antutu numbers are pretty much the same as the aforementioned optimize ones. There is no doubt that LG stock rom is fully qualcomm optimized and i wonder why nobody extracted the qualcomm libraries from our phone and we are dealing with moto X's files and aosp kitk kat roms.
Click to expand...
Click to collapse
As I said in the thread, most Qualcomm devices except Nexus devices already have these optimizations on stock, however, most AOSP ROMs do not.
These optimizations are more OS specific than device specific (same file is used on Moto G, Moto X, HTC One, and more on 4.4), so that is why we don't use the ones from stock. Those are old and there is no reason to use them, since they are no more compatible with our device than files pulled from a 4.4.2 device.
Motorola does not change the dalvik optimization library, nor does any manufacturer because they do not have the source code for it as far as I know, which explains why they haven't made their own tweaks.
There are three versions I've seen so far on KitKat: 2.5.11 (on the Moto X 4.4 as well as GPe 4.4 devices), 2.5.15 (used on 4.4.2, such as HTC One GPe, LG GPad 8.3 GPe, etc) and 2.5.18, which I have not seen outside of leaks, but is the newest I've come across.
libqc-opt (Qualcomm's optimization library) is used in a number of ways: for the PowerHAL (power library that deals with frequencies, part of the JellyBean Project Butter Speed Enhancements), for SKIA (web browser graphics rendering), for SQLITE (don't remember exactly what this is), and Qualcomm's Performance class in framework.
The performance class I have not tested yet, but could provide some enhancements. It allows apps such as games to control your CPU frequency to make it go faster. Not sure what uses it though. I know LG's camera does, but if it's limited to OEM apps, there is no reason to implement it on AOSP. I'll keep looking into it.
In other news, new dalvik zip coming today or tomorrow in the Nexus thread with the latest optimizations from Qualcomm and AOSP. Stay tuned.
Before and after on Carbon 4.4.2
Sent from my LG-LS970 using XDA Premium 4 mobile app
Does the optimizations work on Galaxy S4 I9505 running stock odexed Touchwiz Kitkat 4.4.2 ROM? I afraid it might mess up my system.
haoyangw said:
Does the optimizations work on Galaxy S4 I9505 running stock odexed Touchwiz Kitkat 4.4.2 ROM? I afraid it might mess up my system.
Click to expand...
Click to collapse
Some people shouldn't go around modifying their Android smartphones...
haoyangw said:
Does the optimizations work on Galaxy S4 I9505 running stock odexed Touchwiz Kitkat 4.4.2 ROM? I afraid it might mess up my system.
Click to expand...
Click to collapse
LOL just read the op, please.
This thread is discontinued, use alviteri's builds: https://forum.xda-developers.com/xperia-z1/development/nougat-7-1-1-android-source-project-t3532359
This is a testing build of AOSP nougat. It's based on sources by sonyxperiadev, maintained by alviteri. (big thanks to him)
It's working quite well, just a few bugs:
>Camera doesn't focus well (tap to focus works, but it's slow)
>No deep sleep - Radio - ProxyController
Gapps included/built in
Download
Build 24. 12. 2016
Build 18. 11. 2016
Build 5. 11. 2016
Build 21. 10. 2016
Build 9. 9. 2016
Build 7. 9. 2016
Build 5. 9. 2016
Build 2. 9. 2016
Changelog
24.12.2016
>Many updates to kernel (security etc..)
>Patches to camera
>Overall update - 7.1.1
18.11.2016
>Update blobs (camera improvements)
>Patches to cam stability
-Optimized kernel + updated interactive gov
5.11.2016
>Update blobs (fix cam and proximity)
>@munjeni's charging fix and fixed detection of usb connection
Still no deep sleep
21.10.2016
>A lot of updates, security, camera, android 7.1
9.9.2016
>black (daynight) theme - activate in settings - display
>fix some mhl things
Patches:
-removed latest regulators patch
-remove camera fd
7.9.2016
>Add current values for cpus
>fix cpp for smmu dts node (camera)
Patches:
- USB: Disable regulators only when enabled
5.9.2016
>Camera KW fixes (camera still does not work well)
Patches:
- Charger: add missing properties
- Hotplug: tune the values
- Audio: remove fixed bandwidth
- Bluetooth: set BT name dynamically (I'm not really sure if this fixed bt, but it works)
- Touchscreen: enable touch size
- Wifi: use config from stock
2.9.2016
>Initial release
Patches:
- audio: kernel jack , headsethook number (first custom rom where audio jack works as in stock)
- memory: don't limit memory to 1.4 GB
XDA:DevDB Information
AOSP, ROM for the Sony Xperia Z1
Contributors
SuperLamic, davidteri91, sonyxperiadev
Source Code: https://github.com/SonyAosp
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: 236 bootloader
Based On: AOSP
Version Information
Status: Testing
Created 2016-09-03
Last Updated 2016-12-24
just for c6903?
Glex01 said:
just for c6903?
Click to expand...
Click to collapse
if you flash modem fw for other version it may work. But I don't have any other device to test.
SuperLamic said:
if you flash modem fw for other version it may work. But I don't have any other device to test.
Click to expand...
Click to collapse
Please give C6902 modem link
Thanks
Awesome one
Glex01 said:
Please give C6902 modem link
Thanks
Click to expand...
Click to collapse
I'm sorry, but I don't have any. You should be able to get that from your stock rom - /system/etc/firmware - take all modem.* and mba.* files and replace them in this rom.
SuperLamic said:
I'm sorry, but I don't have any. You should be able to get that from your stock rom - /system/etc/firmware - take all modem.* and mba.* files and replace them in this rom.
Click to expand...
Click to collapse
Sorry for OT, but does it work similiar, if i want to install some ROM, which is for Z1 compact ?
zawy. said:
Sorry for OT, but does it work similiar, if i want to install some ROM, which is for Z1 compact ?
Click to expand...
Click to collapse
Um, no. You can't install rom for honami (xperia z1) on amami (xperia z1 c). You have to compile the rom on your own or wait till any1 compiles it for you.
Awesome job brotha.I am facing Charging issue on USB port using both wall charger or PC the device doesnt detect charger plugged Any possible fix Btw Congrats for the first bootable Nougat build for z1 :highfive:
Hope this rom will be stable
Hope this rom will be stable
Charging
The phn didn't charge, is there any way to fix it.
Nougat for rhine isn't completely stable yet. Charging is broken and there are issues with deep sleep. Camera is not working and battery life isn't up to the mark. Unless you're crazy and want to use unstable software just to run the latest version of Android, I wouldn't recommend Nougat
drakonizer said:
Nougat for rhine isn't completely stable yet. Charging is broken and there are issues with deep sleep. Camera is not working and battery life isn't up to the mark. Unless you're crazy and want to use unstable software just to run the latest version of Android, I wouldn't recommend Nougat
Click to expand...
Click to collapse
"Nougat for rhine isn't completely stable yet." So is MM even after one year of development. So, I disagree with your "yet", as in my view none will ever become stable, as long as developers rely on Sony AOSP device tree and their "unified" kernel, which really unifies only bugs and failures. Again, there is only one way to possibly make MM and N stable: switch back to 3.4 kernel and CM device tree. Note that Sony MM stock for Z2 was built on 3.4 kernel. Sony real developers, the ones that do stock, didn't go with 3.10. That should tell you something,..
Is this a flashable zip?
Sent from my C6903 using XDA-Developers mobile app
santeria27 said:
Is this a flashable zip?
Sent from my C6903 using XDA-Developers mobile app
Click to expand...
Click to collapse
yep
optimumpro said:
"Nougat for rhine isn't completely stable yet." So is MM even after one year of development. So, I disagree with your "yet", as in my view none will ever become stable, as long as developers rely on Sony AOSP device tree and their "unified" kernel, which really unifies only bugs and failures. Again, there is only one way to possibly make MM and N stable: switch back to 3.4 kernel and CM device tree. Note that Sony MM stock for Z2 was built on 3.4 kernel. Sony real developers, the ones that do stock, didn't go with 3.10. That should tell you something,..
Click to expand...
Click to collapse
well, camera probably won't get stable, that's true (I don't use camera much, it's crap even on stock). But I have to disagree with overall stability - it is improving and now (with some patches) it's my daily driver...
there is a fix for charging + fine tuning for hotplug from shinano by Adam Farden. I will recompile the rom probably tomorrow.
Very nice rom! Thx for nougat
Sent from my Xperia Z1 using XDA-Developers mobile app
SuperLamic said:
well, camera probably won't get stable, that's true (I don't use camera much, it's crap even on stock). But I have to disagree with overall stability - it is improving and now (with some patches) it's my daily driver...
there is a fix for charging + fine tuning for hotplug from shinano by Adam Farden. I will recompile the rom probably tomorrow.
Click to expand...
Click to collapse
Good news sir . We are waiting :good::laugh:
New build uploaded, take a look at changelog
How much SOT?
I have a TX201LA tablet runs Android 4.2. Its a dual device 2 systems in 1. The tablet half is what i am focusing on. NOT the dock as I have windows 10 running fine on that half. The tablet is nearly useless as it is on android 4.2. I've been exploring a few options for getting an android update. My tablet runs an atom x86 cpu with 2GB of ram and is quad core cloevertrail CPU x2560. Plenty of power to run a newer android or even chromeOS, cloudready, or remixOS. I've explored those options but Bliss is the most straight forward as there are already x86 builds of Bliss. I think support should be relatively easy to add for my device.
There are a few caveats however I know ways to overcome them if I can get a rom to load.
1. I dont have a unlocked bootloader but I maybe able to unlock using zenfone 5 unlock method. Still no custom rom has ever been made for my tablet, only for similar devices like zenfone 5, galaxy tab 3 10.1, & dell venue 7.
2. Once I get it unlocked, I can load CWM or use flashfire. My tablet boots with Droidboot, which I can replace with CWN via again a zenfone 5 exploit that I have confirmed works with my tablet.
3. Would bliss load things like my LCD driver, touch screen etc? That is possibly the biggest issue. I have the kernel code here, UPDATED: http://support.asus.com.cn/Download....1LAF&p=3&s=587 OR here original: http://support.asus.com.cn/Download....01LA&p=3&s=587
3A. If the kernel code has all the HALS isnt it possible to build a Bliss rom that would be loaded via CWM/Flashfire and then boot-able?
3B. Could the Bliss team build a rom with the kernel code listed above, that I could then test? Or would the bliss team need to the device (I would think not, i hope). If a rom could be created I would GLADLY donate to BLISS.
Love to find out if this is possible. THANKS
I've been trying to update the kernel version on the HD 10 Suez 2017. I am using the sources from this link https://github.com/chaosmaster/android_kernel_amazon_suez/tree/lineage-16.0 on the master Branch I cannot get the the device to boot when building a kernel. However if I use the Android 16 branch, I can get the device to boot but I have an irregularity that I cannot seem to figure out. The screen will go black. It doesn't turn off it just goes black that's if you stop touching the screen or you stop moving the device. aside from that I have not been able to see if anything else is affected but I can get the kernel versions updated at least two 3.18.22 but I haven't continue further because of this the weirdness. I have not tried any other sources as of the moment but was wondering if anybody is run into this problem.
Would this help at all? It’s the googlesource for MTK kernel 3.18
Have you tried building lineage 17 or 18 yet?
https://android.googlesource.com/kernel/mediatek/
https://www.xda-developers.com/alldocube-x-10-5-inch-android-8-1-oreo/
Mt8176 running Oreo 8.1. Supposedly project treble compatable too. Could this mean 8.1 for the HD10 and/or treble support too?
Fix MediaTek no display bug
MediaTek has a family of SoCs that are used in (among other devices) several Chromebooks, such as the MT8173 used in the Lenovo N23 Chromebook and Acer Chromebook R13, plus the MT8183 in the Lenovo IdeaPad Duet Chromebook. We are working hard to have better upstream support for these devices, especially Enric Balletbo, who has been involved in kernel and Chromebook upstream support for a long time. The displays on MT8173 based devices were not functional when using the mainline kernel, this has been rectified with this kernel release.
The cause of this defect was a conflict between the clock and DRM drivers. He found that two different drivers - the MT8173 clocks controller driver, and the MT8173 DRM driver were using the same compatible string mediatek,mt8173-mmsys. This is a problem since in such cases only the first matched driver will be probed. The other one, in this case the DRM driver, never gets probed and so the display was not made available for use. In a collaborative effort between Enric Balletbo and the MediaTek SoC maintainer Matthias Brugger, a top level mmsys driver (Multi-Media subsystem) was introduced to register the clock and DRM drivers. See 1, 2.
Linux 5.8 probably fixed your display bug. What is the chance of moving this tablet up to android 10/11?
source:
https://www.collabora.com/news-and-blog/news-and-events/kernel-5.8.html