Related
Been a while since my last post
is there any modified Kernel for the Tab ? I've seen a Galaxy S runs like a fart on youtube " 1.6 Ghz "
my question is : is this kernel adjustable for the tab ? is there a running project in XDA to make this happen ?
thanks a lot
I have compiled both the AOSP (Android Open Source Project) and the Samsung Galaxy Tab open-source code, but I'm happy with JM6 so far, and I guess I am not brave enough to flash self-compiled critical components, I had enough problems with just self-compiled apps
flashed self compiled kernel resulted in panic
I flashed a the open source basekernel with the galaxy patch from samsung and got no joy. Nothing but kernel panic. Fortunately I was able to flash the original zImage back. Any insight on configuration parameters to use. I just did a stock make.
How did you load the system.img and data.img out from AOSP? I've compiled and can't figure out how to load the images.
Thanks
Im actually going to wprk on making a kernel oc'd just need a few tips ive done linux kernels before but the difference is i dobt have the source does anyone have the source to sprints firmware?
Sent from my SPH-P100 using XDA App
If anyone actually releases a stable 1.5GHz or higher kernel, I'll definitely donate $50 for the work, and I'm sure others will too.
Before you do anything: I will not be held responsible for anything bad that happens to your tablet.
Disclaimer: I do not own this device.
**Sources: Check the GT10.1 A1 kernel thread for beginner friendly V1.9 sources.
Compatibility Information: Check the file names for -stock or -cm for the appropriate version. There is no harm in using a 3G kernel on a WiFi only tablet. This makes the build process less messy. I have a WiFi only tablet and I have no problems with it.
Changelog
Voodoo sound added <-- new to V1.0
USB charging automatically enabled <-- new to V1.1
1.2GHz OC <-- new to V1.2
GPU OC'd from 333MHz to 400MHz <-- new to V1.3
1.4GHz OC <-- new to V1.4
Charging widget support, various bug fixes, cifs with utf8 somewhere along the line <--new to V1.5.9
Attempted support for GT8.9 with 1.5GHz and 1.6GHz OC <-- new to V1.6alpha
Enabled XBox controller as xpad.ko kernel module <-- new to V1.6.1
NTFS moved to kernel module instead of built in, CIFS moved to kernel module instead of built in, enabled option.ko and usb_wwan.ko for connection of 3G dongle, all nls charsets/codepages built as modules <--new to V1.6.2
Applied git patch to disable mmc_cap_erase <-- new to V1.6.4
Voltage control, cifs built in again. <--new to V1.7
Changed battery driver to p3_battery.c originally specified by samsung instead of p4_battery.c that the GT10.1 uses <--new to V1.7.1
Cyanogenmod charging mode fix (incompatible with stock rom)
Rebased on P7300_HK Sources <-- new to V1.7.3
attempted CM10 compatibility fix based on GT10.1, enabled Samsung's powersaver governor, GT10.1 450MHz cap fix <--new to V1.7.4b (based on GT10.1 sources for now since I can test all those changes. Maybe I accidentally messed up something in GT8.9 sources??)
Copied in pershoot keyboard driver for CM <--new to V1.7.5
801MB RAM available <-- new to V1.8
Rebased on pershoot's sources as of November 17 11pm EST <--new to V1.8.1
Back to samsung GT10.1 base, follow pershoot's suggestion of Nexus7 mtp drivers to fix mtp, enabled zRam <--new to V1.8.2
Reduced RAM to 785MB to account for intense 3D games, enabled KSM (check settings --> performance --> memory management), reappearance of stock versions
Rebased stock rom kernel on GT10.1 sources. <--new to v1.8.3b (stock version only)
Rebased on 7300_update1 ics sources <--new to V1.8.3c stock versions only
Fixed charging while off bug. (You can now turn your tablet off for the night and charge it), enabled userspace human interface device management for CM10.1 <--new to V1.8.4 (CM only)
V1.8.5, 1.8.6 GT10.1 specific
Added row scheduler from CM10.1 I9300 sources <--new to V1.8.7
Added XDA's grzwolf's hsic wakelock fix <--new to V1.8.8
Added frandom kernel module from GT10.1 request <--new to V1.9
See my GT10.1 thread for more info.
AAccount said:
Before you do anything: I will not be held responsible for anything bad that happens to your tablet.
Where the name comes from: This kernel is named after the imaginary character A1. A1 was a character of my creation who was powerful, thought on his feet in battles and drove an electrically powered flying SUV. In my signature is his original hand drawn logo that I drew ~10 years ago, scanned, and used gimp to touch up.
I got a request to port this kernel to the galaxy tab 8.9. Only today, did I realize that the GT8.9 sources are included in the GT10.1 sources I downloaded. Very minimal changes needed to be made to make it GT8.9 compatible. However, I do not own this device and cannot afford a second tablet (even wifi only). I tried my best to follow the same steps used to create the GT10.1 version for the GT8.9. Since I have not even booted this kernel yet, it is marked pre alpha. Feedback is much appreciated. I am compiling this kernel in good faith. You will need to flash back the stock kernel and copy in the files from a stock rom's /system/lib/modules to get back to stock. I recommend you have a stock kernel on hand ready to flash from recovery just in case...
**Sources: look for the corresponding A1 thread the the GT10.1 section. Nothing has changed at all except the .config which is directly modelled after the GT10.1 .config.
Changelog
Voodoo sound added <-- new to V1.0
USB charging automatically enabled <-- new to V1.1
1.2GHz OC <-- new to V1.2
GPU OC'd from 333MHz to 400MHz <-- new to V1.3
1.4GHz OC <-- new to V1.4
Charging widget support, various bug fixes, cifs with utf8 somewhere along the line <--new to V1.5.9
Attempted support for GT8.9 with 1.5GHz and 1.6GHz OC <-- new to V1.6alpha
See my GT10.1 thread for more info. Only missing features from GT10.1 version is the boot script support and CM versions. I'd prefer to take it 1 step at a time.
Click to expand...
Click to collapse
Hi...
I am on Overcome now, and wondering if this can be applied on my P7300 ?
If so, should I just flash it over the CWM ?
Please advice.
Thank you.
andikasaja said:
Hi...
I am on Overcome now, and wondering if this can be applied on my P7300 ?
If so, should I just flash it over the CWM ?
Please advice.
Thank you.
Click to expand...
Click to collapse
You need to be running a stock ice cream sandwich rom (Android 4.0). I think overcome rom is honeycomb (Android 3.2). Also remember this is an alpha kernel.
Seems to work fine. I'll play with it for a while before making up my mind about it.
Thanks for doing this for the 8.9.
AAccount said:
You need to be running a stock ice cream sandwich rom (Android 4.0). I think overcome rom is honeycomb (Android 3.2). Also remember this is an alpha kernel.
Click to expand...
Click to collapse
Thank you for the confirmation.
I also thought so, as it was mentioned as [Stock ICS].
Cheers...
Stupid question time! I looked at the notes on the 10.1 kernel thread, and didn't see it, but does this kernel have the game pad (usb xbox controller) support built in? I know the factory one doesnt see my controller.
bluefalcon13 said:
Stupid question time! I looked at the notes on the 10.1 kernel thread, and didn't see it, but does this kernel have the game pad (usb xbox controller) support built in? I know the factory one doesnt see my controller.
Click to expand...
Click to collapse
No it doesn't, but I'll look into it. I've looked into it. Should be included in the next version but first... I want to get feedback on the current port before releasing new versions.
Thanks mate for the built, seems to work properly, do you need some specific test,benchmarks or stuffs like that?
Thank you AAcount for porting it, will test it soon.
Kernel works very well, let's hope it improve the battery life.
Gesendet von meinem GT-P7300 mit Tapatalk 2
ceno80Under volt1 said:
Kernel works very well, let's hope it improve the battery life.
Gesendet von meinem GT-P7300 mit Tapatalk 2
Click to expand...
Click to collapse
For That we need UnderVolt, hope it will be added in next releases
you are the man
i want to thank you for this kernel voodoo support is important to me because the tab is my car stereo. flashed havent had any issues yet. if you want to add uv support thumbs up ill give it a try. thanks for taking the time to compile even though u dont have a 8.9!
just flashed this on my tab and i can report that all is working just as expected! OCd to 1.4Ghz and noticeably smoother!
really like it!
Thanks a lot for taking the time to port this for us!
A few requests for future versions:
Other Shedulers. On my razr I'm using pegasusq which is great for battery life. when the phone is asleep it shuts down one of the two cores completely! hotplug & hotplugx also do this. not sure if the galaxy tab supports something like that but it would be great!
Undervolting. moar batterrrryyyy arrrrgh
Thanks once again!
did some more testing. youtube HD videos now have a slight lag and hickups that were absent on the stock kernel.
Great ! Thanks a bunch. I will give it a try this evening.
Any chance we get a zip with the stock kernel, in case something goes wrong ?
Good idea. Please put an original kernel zip file.
Wysyłane z mojego GT-P7300 za pomocą Tapatalk 2
Just done some benchmark, no oc, but I didn't have stock kernel results to compare yet... 2d test seems very bad, I don't know if it sucks with stock one as well
chemicalbuz said:
Just done some benchmark, no oc, but I didn't have stock kernel results to compare yet... 2d test seems very bad, I don't know if it sucks with stock one as well
Click to expand...
Click to collapse
Did you force 2D gpu rendering in the developpers settings ?
I will benchmark too, before & after the update.
AAccount said:
No it doesn't, but I'll look into it. I've looked into it. Should be included in the next version but first... I want to get feedback on the current port before releasing new versions.
Click to expand...
Click to collapse
Awesome, thanks. Saw this thread as I was headed to bed last night. I'll do a nandroid and install to give it a whirl after work. If there are any issues, I know the controller worked under the Galaxian Soup pre-ics kernel, think it was motley's V3, not 100% on the kernel name.
Any chance using this kernel in JB ports ?
This kernel have support for running scripts in /etc/init.d ? (because _motley's lack it).
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.4.4.0:
-Added another libtar hardlink workaround to fix restore of some backups (usually related to Ubuntu Touch)
-More fixes for the file selector
-Switched from using busybox md5sum to a direct C function call
-Fixed capturing the exit status of tar based backups/restore - TWRP will display that there was an error if there was one again
-Update exFAT to latest commits
-Added a build flag to disable using the ioctl for screen blanking
CHANGELOG for 2.4.3.0:
-Fixed 2 bugs related to restore, one dealing with mknod failures (by bigbiff) and one dealing with restoring hardlinks (by Dees_Troy)
NOTE: If your backups weren't restoring correctly in earlier 2.4.x versions they should restore correctly now. Hopefully you didn't delete those backups. If you're still having problems, run the restore, go to advanced and copy log, then give us the log. Complaints without logs will be rightfully ignored.
-Added a scroll bar to file selectors and listboxes courtesy of Tassadar
-Added libblkid for more accurate detection of file systems and can now detect exFAT properly thanks to bigbiff
-Added a screen dim effect 2 seconds before screen off on some devices
-Finally fixed file selector crash (one of the joys of working with multi-threaded software)
-Fixed loading of screen timeout setting during startup
-Improvements and bugfixes to screen timeout code
-Fixed persistence of the 24 hour / military time setting
CHANGELOG for 2.4.2.0:
-Add screen timeout - screen will turn off automatically after 60 seconds, saves battery and prevents screen burn-in especially on AMOLED devices
-Add a brightness setting (requires device specific setup and only some devices have been added)
-Add a root checker and offer to install SuperSU if the device isn't already rooted
-Add a write buffer to libtar backups, significant improvements to speeds when backing up to exFAT target, minor improvements for other file systems
-Check and offer to fix root permissions if broken
-Add an option for a 24 hour clock display instead of AM/PM (aka military time)
-Move stock recovery reflash check to occur during the reboot cycle
-Add support for some MTK6xxx devices
-Change libtar to vfork to help prevent memory problems
-Add a "clicked" effect to most buttons, file selector, and listbox
-Improve timezone listbox to be more like file selector (per pixel kinetic scrolling, etc)
-Remove some no longer used settings (Forced MD5 sum on zips, size checking on image backups)
-Other minor bugfixes and improvements
CHANGELOG for 2.4.1.0:
-Fixed a problem with mkdosfs that formatted sdcards to 2GB
-Fixed handoff between vfat and exFAT on devices where blkid didn't detect vfat (fixes some issues with mounting sdcards)
-Fixed problems with changing working directory on MD5 creation/checking that may have prevented unmounting
-Backups will now store a copy of the backup log after the backup is completed (only if backup is successful)
CHANGELOG for 2.4.0.0:
-Using libtar instead of busybox's tar for better control over tar file creation and breaking the 2GB barrier that busybox imposes (thanks to bigbiff)
-Support for exFAT formatted sdcards (also thanks to bigbiff)
-Support for decrypting Samsung TouchWiz encrypted devices including internal and external storage (special thanks to a3955269 for figuring it out)
-Improvements to OpenRecoveryScript including displaying a proper GUI while the script is running
-Added wipe cache and dalvik after ADB Sideload
-Replaced many system calls with their native C counterparts
-Fixed bugs in file manager where it would display an empty list after moving or deleting a folder
-Fixed AOSP recovery commands to run after decryption on encrypted devices
-Improvements for building TWRP in CM10.1
-Other minor bugfixes and improvements
NOTE: 2.4.0.0 is, as always, still compatible with your older backups!
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
DEVICE SPECIFIC THREADS:
Acer Iconia A500
Amazon Kindle Fire
Asus Transformer TF101
Asus Transformer Infinity TF700T
HP TouchPad
HTC Amaze 4G
HTC Butterfly
HTC Desire HD
HTC Droid Incredible
HTC Droid Incredible 2
HTC EVO 4G
HTC EVO Shift 4G
HTC EVO 3D CDMA
HTC EVO 3D GSM (shooteru)
HTC EVO 4G LTE
HTC Hero CDMA
HTC One S (S3 C2 variant)
HTC One X (evita)
HTC One X International (endeavoru)
HTC Sensation
HTC Thunderbolt
HTC Vivid, Raider, Velocity
LG Optimus Black
LG Optimus G Sprint
Motorola Atrix 4G
Motorola Photon 4G
Nexus 4
Nexus 7
Nexus 10
Nexus S
Nexus S 4G
Samsung Fascinate
Samsung Epic 4G
Samsung Epic 4G Touch
Samsung Galaxy Nexus GSM (maguro)
Samsung Galaxy Nexus Verizon (toro)
Samsung Galaxy Nexus Sprint (toroplus)
Samsung Galaxy Note 10.1
Samsung Galaxy S2 T-Mobile USA (hercules)
Samsung Galaxy S2 AT&T USA (skyrocket)
Samsung Galaxy S3 AT&T USA
Samsung Galaxy S3 Sprint USA
Samsung Galaxy S3 T-Mobile USA
Samsung Galaxy S3 Verizon USA
Samsung Galaxy S3 International i9300
Samsung Galaxy S3 LTE 2GB i9305
Samsung Galaxy Tab 7.7
Samsung Galaxy Wonder i8150
Sony Xperia T
Asus Transformer Prime TF201
Asus Transformer TF300T/G
HTC One S (Ville)
B+N NookColor
USA ATT Galaxy Note 2
USA Sprint Galaxy Note 2
USA Verizon Galaxy Note 2
International Galaxy Note 2
USA T-Mobile Galaxy Note 2
USA ATT Galaxy Note
USA T-Mobile Galaxy Note
USA T-Mobile Galaxy Note 3
/me raises hand
Most advanced and reliable recovery! Good stuff guys
Sent from my very expensive paperweight!
What about xperia S?
great effort!
this is a great new for all xda member! :good::laugh::laugh::victory: from the list given, Samsung Galaxy S Advance GT-I9070 not listed. Can i update to this version as right now i'm using the previous version of TWRP
Really, no support for I9100 international. Any chance to this happen?
Tks
Sent from my Nexus 7 using Tapatalk HD
looking for tab 10.1
I see the gtab 7.7 but not the samsung galaxy tab 10.1... gt-p7510 wifi? P4WIFI
I hope to see support for the gtab 10.1 wifi
edbertin said:
Really, no support for I9100 international. Any chance to this happen?
Tks
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Pretty much all Samsung phones released before the SGS3 that don't have a Qualcomm SoC in them have a recovery-in-boot setup which means that anytime you install a new ROM or kernel, you get whatever recovery the developer includes in the boot image. I know that Talustus makes a kernel for the i9100 that has both TWRP and CWM in the same kernel so you can try his kernel if you want TWRP on your device.
The vast majority of devices have a separate, bootable recovery partition making it much easier for users to install and keep the recovery of their choice. I've also been working with developers here and there to help ensure that devices with recovery-in-boot are set up in a manner that allows users to install an alternate recovery, but TWRP didn't really break onto the scene until later in the i9100's development cycle making it much less likely that TWRP would get sufficient support from ROM and kernel makers.
SgtMacabre said:
I see the gtab 7.7 but not the samsung galaxy tab 10.1... gt-p7510 wifi? P4WIFI
I hope to see support for the gtab 10.1 wifi
Click to expand...
Click to collapse
Your best bet is to come by the IRC channel and find me when I have a little time. That or follow the guide to port TWRP yourself.
Dees_Troy said:
Your best bet is to come by the IRC channel and find me when I have a little time. That or follow the guide to port TWRP yourself.
Click to expand...
Click to collapse
Is there an older version that doesn't have the locks and doesn't have swipe, just plain old touch?
Can someone provide me recovery.fstab of Galaxy Tab 7.7 and HP Touchpad...please...
I think I will port twrp for aosp ROMs on galaxy s2
Need confirmation that the hard brick bug relating to secure emmc erase is patched in twrp which affect all galaxy s2 variant and also note variants
Sent from my GT-I9100 using Tapatalk 2
does it have the sds fix for S 3's?
sony Xperia S?
please add support for sony xperia s.
so i can install new rom or mods. like camera mods.
then i can donate you happily as a puppy!
cheers!
Pruikki said:
please add support for sony xperia s.
so i can install new rom or mods. like camera mods.
then i can donate you happily as a puppy!
cheers!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2172060
UI lockes up on rename directory
- Installed 2.4.3.0 on my fully encrypted GT-N7105 running WanamLite v1.1 rom (based on stock 4.1.2 XXDMB3)-
- made a full backup
- in the File manager went to /external_sdcard/TWRP/BACKUPS/42f793084d379f11/2013-03-03--16-24-29, then select
rename dir
- entered new name and swiped OK
I am now at the File Operation Complete / Succesful screen that is displayed at the end of the backup and touch screen has become unresponsive
adb still works so I could pull the log.
it seems when TWRP jumped back to that screen it expected to be in the original backup directory, except it does not exist anymore...
François
Can someone please explain how to upgrade from one version of TWRP to a newer version? I can't seem to find this info.
EDIT: I don't have access to a computer.
sk8erfrombham said:
Can someone please explain how to upgrade from one version of TWRP to a newer version? I can't seem to find this info.
EDIT: I don't have access to a computer.
Click to expand...
Click to collapse
Goo Manager. Download, install, open, hit menu, install recovery....
Hello
I was wondering if there are any Nexus 4 ROMs using JustArchi's optimizations (link). I did my best to compile OmniROM with these fixes, but I am not very experienced with Android development.
+1 to this post
Looks like our devices are too fast to use these "insignificant" compiler optimizations
I'll give my 5 cents these days to try compiling it..
Cheers
+1 for this thread.. I asked just the same thing in the general Q&A thread and nobody answered.. I'd like to see CM, ParanoidAndroid...etc.. built with ArchiDroids optimizations..
Like to see that too!
I've been searching for a rom with f2fs support + JustArchi's optimizations. Can be possible?
I created a topic earlier here
opssemnik said:
i can tell from personal experiences, its mostly placebo, tried archi´s rom on my gs3, and aside from the fact that the google camera dosent crash after first shot(witch occors on alot of roms ,even official cm, again on my s3), the rom is same speed, if not less than official cm. (on my s3 i9300)
Click to expand...
Click to collapse
Nevertheless, there are other statements that say it is faster, we can only know for sure if we benchmark this and find someone willing to compile a rom. Perhaps @legolas93 is willing to be so kind?
joefso said:
I created a topic earlier here
Nevertheless, there are other statements that say it is faster, we can only know for sure if we benchmark this and find someone willing to compile a rom. Perhaps @legolas93 is willing to be so kind?
Click to expand...
Click to collapse
yeah i saw those,luck for them, thats why best rom threads are not allowed on xda, people get different results on their devices ,i plan to compile aosp with those just to test on the n4, but i doubt i will :/
No one is going to try this anytime soon.
The code is no where near perfect and it sets up an environment where there is a lot of room for errors which will result in VERY bugy, glitchy, crashing Roms.
The code is really sloppy and so far only JustArchi is the only one that has successfully used this in a ROM with out error.
There is still a lot of going back and forth in whether this really works since android isn't 90% thumb
All this is good for is benchmark scores. Just like F2Fs its all placebo in real world performance.
With a quadcore 2 gig phone... You're not missing much.
Legecy devices will benefit in the least from this.
Sent from my SM-T217S using Tapatalk
First build is ready!
It is mako-userdebug.
I used Linaro toolchain(JustArchi's link) and JustArchi "JustArchi's ArchiDroid Optimizations V3" - https://github.com/JustArchi/android_build/commit/d8cc50d2472e497b431b5652516c9248ad7f3947
It is without Gapps (so PA Gapps must be used).
Build Env :
Debian GNU/Linux testing (with make downgraded from 4.xx because AOSP lunch require this).
AOSPA soruces 4.4.2_r1 used for the build.
No ART patches! ART will fail if you try using it.
Will test this today on my phone, and if successfully boot, I'll post a link for the ROM.
p.s : From back these days, where people find that AMD64 arch is here, Linux builds started to optimize the speed of your GNU/Linux for your specific CPU (Gentoo for example, or Debian GNU/Linux moved from i386 to i686 and after that to AMD64). Well, the tests and builds performance charfs finished with this : improvement of the speed was was something like 0.6/0.9% ... So in the real world reality do not expect much from this!
Regards ...
Edit:1
Boot failed
Next time, I'll enable the proprietary drivers in the build.
Currently new build is running with enabled prop drives settings like:
Source:http://nosemaj.org/howto-build-android-nexus-4
To use these proprietary files, comment out this line in device/lge/mako/full_mako.mk:
#PRODUCT_RESTRICT_VENDOR_FILES := true
Cheers!
This thread will be about changes i have made to the device trees for the t700,t705,t800,t805 which should in the long run make maintaining the variants a lot easier the primary changes i have done are combine all 4 of the variants into 1 kernel source as well as make a common device tree so they can inherit everything that is the same across devices.
Kernel Changes:
The Base kernel from Cyanogenmod supports klimtwifi (T700) and klimtlte (T705) to add support for chagallwifi (T800) all that is needed is to add its defconfig which is this file
https://github.com/LiquidSmooth-Dev...arch/arm/configs/deathly_chagalllte_defconfig
To add support for the Chagallte (T805) it was a little more complicated for to do but very simple for you guys for a little background T805 is exactly the same chipset as the other Galaxy Tab S's except for whatever reason Samsung decided to put a different gpu (Midgard_wk04) everyone else uses a mali_t6xx.
The stuff developers actually need to support Chagalllte are the following:
Defconfig:
https://github.com/LiquidSmooth-Dev...arch/arm/configs/deathly_chagalllte_defconfig
The GPU addition commit:
https://github.com/LiquidSmooth-Dev...mmit/c8e96e86c902cbc2b13d34e7e7158623eacf5d84
Bam that was easy now any kernel can support all 4 main variants of the Tab S
Device tree and vendor repos
First part i want to place links to all of the stuff that's needed to make a rom for each device in one place.
(Disclaimer the trees will be LiquidSmooth but it is very easy to convert them to any rom)
Klimtwifi (T700):
https://github.com/LiquidSmooth-Devices/android_device_samsung_klimtwifi
https://github.com/TheMuppets/proprietary_vendor_samsung/tree/cm-12.1/klimtwifi
Klimtlte (T705)
https://github.com/LiquidSmooth-Devices/android_device_samsung_klimtlte
https://github.com/schwabe93/vendor_samsung_klimtlte
Chagallwifi (T800)
https://github.com/LiquidSmooth-Devices/android_device_samsung_chagallwifi
https://github.com/diego-cr/android_vendor_samsung_chagallwifi
Chagalllte (T805)
https://github.com/LiquidSmooth-Devices/android_device_samsung_chagalllte
https://github.com/Andrewt12/android_vendor_samsung_chagalllte
WIP Common Device Tree:
When bringing up support for LiquidSmooth for these devices i noticed that they are all pretty much copied each other (which makes sense) but because of it there was tons of duplicated code between the devices so i decided to make a common device tree so any future code changes could be placed in one place instead of over 4 device trees. This is still a WIP because i do not have all the devices so i can not test them all in my eyes they should all work fine. The common device tree will also hopefully will be rom independent so no changes would be needed on a per rom basis. I can for sure say klimtwifi and chagallwifi work with my common tree, Chagalllte and klimtlte need to be tested still.
Common Device tree repo:
https://github.com/LiquidSmooth-Devices/android_device_samsung_exynos5420-common
Common device tree migration commits
Klimtwifi:
https://github.com/LiquidSmooth-Dev...mmit/444b4fc08f82eeeabe8e0a533539fe0c2fadd723
https://github.com/LiquidSmooth-Dev...mmit/cdf5f06c8a29bb237b964d5ee602d151c6323677
Klimtlte:
https://github.com/LiquidSmooth-Dev...mmit/8570d466e2b5b88c316c7f1576bf8ea9051c5e2a
Chagallwifi:
https://github.com/LiquidSmooth-Dev...mmit/5be51eb30283355109c65513ea209dd1d6855ff2
Chagalllte:
https://github.com/LiquidSmooth-Dev...mmit/5ff21d73a9cad3f7f9cf7f79b29bdbab0d8b2b1e
One more improvement that myself and @diegocr made was finally made a pernament fix to Chagallwifi's (T800) wifi issue he made a custom release tool in the device tree to make it so you would not have to manually patch it every time. I then took that and fixed the root of the issue which was that the vendor repo was not putting the files in the right spot. (My orig commit also did egl but that was not needed) the commit that did it is this:
https://github.com/diego-cr/android...mmit/1fc5135eda985ddc159f8465ee114e67aa5dfcae
Now into the features of my Deathly kernel
XDA:DevDB Information
[Dev Info] [Deathly Kernel] [AOSP] [Lollipop 5.1.1], Kernel for the Samsung Galaxy Tab S
Contributors
deadman96385
Kernel Special Features:
Version Information
Status: Testing
Created 2015-06-22
Last Updated 2015-06-21
Deathly Kernel
I have had a deathly kernel on most devices i own the goal of it is to get as many options and features into a kernel but still be stable. For the Tab S i took the aosp cm base and have updated it against kernel.org from 3.4.105 too 3.4.108 along with pull in a bunch of features from other exynos 5420 devices
As you read above i have made a common tree which changes the ramdisk so i have to provide two zips one with the new format one with old format currently the only rom that i personally have built with the new version is the latest klimtwifi and chagawifi all other roms will boot loop with it so use the old version
Currently i only have flashable for Klimtwifi (T700) i will generate the others once i get back from my trip.
New Ramdisk option:
http://www.drdevs.com/devs/teamliquid/Kernels/klimtwifi/New_format/
Old Ramdisk option:
http://www.drdevs.com/devs/teamliquid/Kernels/klimtwifi/Old_format/
Features of the Deathly kernel:
Will support all 4 main tab s devices (will add support for the US carrier variants if aosp is brought up)
CPU Voltage Control
CPU OverClock/UnderClock
GPU Voltage Control
GPU OverClock/UnderClock
MIF/INT Voltage Control (I will not show how to configure this if you know how too then you can)
Wolfson Sound Control Thanks to oloendithas for fixing it for stereo out
UKSM instead of KSM
Added the following IO Schedulers: fifo, fiops, sioplus, tripndroid, vr, zen, bfq (Default)
Full f2fs support updated off the mainline (Stock cm kernel has limited support)
Modified Thermal Throttling temperatures for all devices so hopefully they won't get as hot (WIP)
Android Logger disabled by default can be enabled over sysfs
Exynos thermal exposed to sysfs
WQ power efficient workqueues (Still need to apply in more places)
Frandom Support
Readahead bumped to 256 from 128
Details how to configure all of the features i will add the rest once i come back
GPU Configuration:
To configure the max or min gpu frequency you would go to either of the following files in a root enabled file browser and change the value inside
/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq_gpu
/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq_gpu
The allowed values for the files are as followed:
667, 600, 533, 480, 420, 350, 266, 177, 100
T800 owners the default min gpu freq is 100 on all roms if that causes issues raise the min freq to 266 you will probably not notice a battery decreases if that still does not work let me know i'll take a look at the code.
Reserved
Reserved
Thanks, working great on CM12.
Thank you man.. Im glad someone finely separated the device tree... And specially Happy about a new kernel that I can use in my Project Roms.
With all Credits going to you of course.. thanks again.
Hey mate, thanks for this!
I'm a little unsure about the new and old ramdisk thingy.
Running aicp on my klmitwifi, new ramdisk is cool?
Will try anyway, but let me know please!
Edit :
just checked, didn't stupidly before, Looks like the kernel is baked in your AICP rom.
Thanks again for your hard work!
Edit edit:
tried the v02 on the rom mentioned, had to revert cause I was having many ui fc.
Used new ramdisk version, could be that or I should have done a clean flash maybe?
Thanks for this, hopefully if fixes the lag issue for me on CM12 with the T800.
Thanks for all the hard work, grid .1 and .2 both worked perfect on bliss rom
Thanks, I will use your kernel on my chagallwifi SlimLP builds
Wait, does the Deathly kernel already in CarbonROM for T700 have F2FS support already? Or is that for the New Version and not yet built for klimtwifi? Thanks
SkOrPn said:
Wait, does the Deathly kernel already in CarbonROM for T700 have F2FS support already? Or is that for the New Version and not yet built for klimtwifi? Thanks
Click to expand...
Click to collapse
The f2fs version in the carbon build is not updated like it is now so i can not guarantee it works the next build will work though
deadman96385 said:
The f2fs version in the carbon build is not updated like it is now so i can not guarantee it works the next build will work though
Click to expand...
Click to collapse
OK, thanks. Hope your enjoying your time off... :good:
I'm going to backup your kernel and try ashyx's new build released today. Its closer to stock but has F2FS support also. Then I will test yours once its updated. Loving this new tab of mine, almost forgot how much fun it was trying to find the sweet spot on a device, lol. My Nexus 7 found its sweet spot a long time ago and now its just a plain ole boring tablet. hehe
diegocr said:
Thanks, I will use your kernel on my chagallwifi SlimLP builds
Click to expand...
Click to collapse
...Slim LP, for t800 maybe, where to find it?
m.
meduza2 said:
...Slim LP, for t800 maybe, where to find it?
m.
Click to expand...
Click to collapse
In SlimRoms Builders Collective
diegocr said:
In SlimRoms Builders Collective
Click to expand...
Click to collapse
...nice Do you intend to make an own SLIM LP thread?
m.
meduza2 said:
...nice Do you intend to make an own SLIM LP thread?
m.
Click to expand...
Click to collapse
Great idea, but now I have no time to keep updated
diegocr said:
Great idea, but now I have no time to keep you updated
Click to expand...
Click to collapse
Would be really great!!
I would like to see SLIM LP on my tab s A platform to exchange user experience for our specific device would be very helpful for you and us
m.
meduza2 said:
Would be really great!!
I would like to see SLIM LP on my tab s A platform to exchange user experience for our specific device would be very helpful for you and us
m.
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-tab-s/development/rom-ezio84-slimlp-t3146025