Related
I hope Tytung doesn't mind me posting this up but I just wanted to inform everyone that he has just released his Kernel source for ICS so devs can help on the development for the fellow HD2. From his post:
tytung said:
As promised, I have uploaded my latest ICS kernel source to the GitHub website.
https://github.com/tytung/android_kernel_htcleo-2.6.32-ics
I changed the kernel name to ics_htcleo_r1, a neutral name.
If anyone really want to help improve this ics kernel, please fix/add the following features first and consider sending me a git pull request.
Full Hardware Acceleration.
Proper hardware encoder for camcorder to record the smooth video.
More compatible touchscreen driver for ICS to fix pinch-to-zoom issue.
Proper VPN driver for ICS.
I uploaded my kernel source to the git mainly for the collaborative development.
In other words, don't add small stuff based on this kernel and then release a new kernel with your own name.
Thank you for your cooperation!
Click to expand...
Click to collapse
Source: http://forum.xda-developers.com/showpost.php?p=22607800&postcount=3292
If any devs could help the further development of this Kernel that would mean a lot to the HD2 community Please give all your thanks to Tytung for all his hard work
Good job
Thank you tytung !
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).
Hi all!
I will try to get the Android Open Accessory (AOA) protocol into our defy/defy+.
Anybody else working on this topic?
Atm I just added the android.hardware.usb.accessory.xml file to /etc/permissions and the com.android.future.usb.accessory.jar to /system/framework (jar taken from the droid sdk API16, my fw is latest quarx CM10).
Right now I can install f.w. the ADK2012 app. So I may on the right way... but I guess that is not all the work... does anybody know if we need to add some kernel modules f.e.?
[Edit] btw... looks like we just need to add a new f_accessory.o to our usb gadget... f.e. see https://www.codeaurora.org/gitweb/q...in;h=5d9d8625e39f815673dedea353f39edccabb1fac
Best regards, Stephan
Like to know this to. If quarx managed to give us sub host, I might be able to use my duomilanove board...
Aren't there other projects for the ADK that doesn't use the protocols?
Please ask all questions in the Q&A section. Thread moved there.
Ok... I gave it a short try with the patch and quarx's linux-2.6.32 but it failed during the compiliation... but meanwhile I noticed that quarx is working on linux-3.0.8 (see its repo in github). There we have our accessory...
So I would say stay tuned for a while and let's if quarx may got this newer kernel working with our defy...
You can find all the steps needed to patch it here:
https://github.com/ezterry/manifest-gingerbread-DS/issues/32
They're saying everywere that you need 2.6.35+ kernel (don't know if it really is mandatory, kernel in the link is 2.6.34)
A kernel with the same chipset that has it enabled can be found here:
https://github.com/XDA-Bam/samsung_kernel_latona_GB
Apparently, you need to enable it in the kernel (config), add the libs to the kernel (driver/usb/f_accesory and include/linux/f_.accesory), add the lib in the framework (might be included from CM side already??), hope it will work (or debug why not).
---------- Post added at 01:21 AM ---------- Previous post was at 01:06 AM ----------
It seems that the files are indeed in the 3.0 kernel.
I already ordered a USB-host shield for my arduino a week ago, I'll try and compile a kernel with it ones it comes in the mail.
Edit:
Tried the changes I listed, will build it tomorrow (or so). Maybe then my shield might arrive to (hate waiting, stupid holidays.. )
Any place to upload it when it works?
Got something build, but it didn't include the /system/framework/com.android.future.usb.accessory.jar and got bootloop without (cause I added the /etc/permision/something_with_usb_accesory.something
Pushed the jar with adb from bootmenu (from another CM rom).
Don't have the usb_shield yet, so can't really test. Will try and install an usb_accessory app. Does someone want the build to try?
Ok, the app fails to launch.
Ok, my repo's:
Kernel: https://github.com/labsin/jordan-kernel/commits/2.6.32
Device: https://github.com/labsin/android_device_moto_jordan-common/commits/jb_2ndboot
But doesn't work. The library isn't build (in framework/base).
And it also doesn't build in the kernel... :/
Anyone??
Might it be possible to check the driver?
Edit: Found it.
It seems to many commits need to be merged in. Can't seem to find a kernel that's not based on the nexus line that has it.
If anyone is still interested in this, I managed to make an Arduino Mega ADK board with the DemoKit application work in accessory mode on my Defy
Quarx backported the USB gadget driver from 3.0.8 kernel into his 2.6.32 based kernel already a while ago. All that was still missing was the accessory configuration in init.usb.rc and the .jar and .xml files. Quarx has already merged my pull request, so in the next CM10.1 nightly with 2.6.32 kernel, USB accessory mode should work out of the box
Thnx. Already saw this actually
Hello there,
I'm looking for a way to mount nfs shares of my NAS and (debian wheezy) server in the filesystem for access of my media files.
I thought for long that it would be the most natural thing to do for my (linux based) mobile devices in a linux server environment, but it seems I'm far off.
So far I have been unable to mount these nfs shares of mine to the Nexus 7 (grouper) device running a Carbon ROM 4.4.2 Nightly Build from march this year (CARBON...20140302-0433.zip) with CifsManager, most likely due to its lack of kernel support (version 3.1.10--g90cc2cb1 bigshotrob...).
May one of you recommend a kernel that supports nfs, cifs and utf-8 for this build? I restrain from updating it as it is running smoothly and without problems (Remember? Never change a...) and I don't like to invest much time for the reconfiguration and other related stuff.
I know there is M-Kernel (http://forum.xda-developers.com/showthread.php?t=2168787) out there that claims to have exactly the requested support and compliance to the CarbonROM series. But I'm unable to sort out what version of the kernel would match my build of the ROM.
I understand that the most actual release is for versions 4.4.4, but the changelog and >200 posts I've browsed do give no hint which release was compiled for 4.4.2 ROMs.
Please note, I would ask directly in that respective thread in the development section if I could, but owing to the (imho pretty stupid) 10 post restriction of newcomers I am unable to post there.
Edit: Not necessary anymore, got my postings ...
Accordingly, my second question would be, if someone with more than 10 posts would be so kind and ask the following questions for me in the given thread?
Namely:
What version of the kernel would fit my 4.4.2 CarbonROM Build and where could I obtain it?
Does anyone had success to mount nfs shares with it (or cifs, if not) ?
Edit end
That and any alternative ways/hints to get nfs going would be highly appreciated!
Thank you very much,
Nix
Specs Summary:
Nexus 7 2012 Wifi only
Carbon ROM 4.4.2 Nightly Build (CARBON...20140302-0433.zip)
Kernel 3.1.10--g90cc2cb1 bigshotrob...
Simple. Give my kernel a shot. It uses an AnyKernel installer, which then works with both ext4/f2fs ROMs. If you don't want experimental dt2w/s2w, flash 1.6.1.
Edit
http://vp-zp.com/snuzzo/kernels/grouper/
Forgot my link lol
Snuzzo said:
Simple. Give my kernel a shot. It uses an AnyKernel installer, which then works with both ext4/f2fs ROMs. If you don't want experimental dt2w/s2w, flash 1.6.1.
Click to expand...
Click to collapse
Thank you for the reply snuzzo,
would you mind to give some details where to learn more of its features and where to find it?
Then I'll have a look at it.
EDIT:
Thanks for the link! But exactly what version do I have download for my Carbon ROM build above, if I'd decide to use it that is?
Presumably .../kitkat/Funky...??
BTW, are there some feature lists or such things? I'll probably browse the forum a bit, I suppose?
Cheers, Nix
Anykernel Installer. You can flash it on either an ext4/f2fs rom for /data compatibility
Overclock with 1.3Ghz max default
Under/overvolt
IO Scheduler additions: SIO BFQ ROW
CPU Governor additions: Lazy Lagfree Scary Lulzactive Wheatley (could be few more but thats from memory)
DoubleTap2Wake/Sweep2Wake in 1.6.2, disabled in 1.6.1(experimental)
Kexec Hardboot for MultiRom
Dynamic Fsync Control
Stock Google 4.7GCC prebuilt toolchain.
CIFS.
Theres a few other tweaks I made for overall UI performance other than that it follows CM-11.0 source. I build these for my own personal use but upload to share them for those who want what I run. You will want 1.6.2 or 1.6.1.
Snuzzo said:
Anykernel Installer. You can flash it on either an ext4/f2fs rom for /data compatibility
Overclock with 1.3Ghz max default
Under/overvolt
IO Scheduler additions: SIO BFQ ROW
CPU Governor additions: Lazy Lagfree Scary Lulzactive Wheatley (could be few more but thats from memory)
DoubleTap2Wake/Sweep2Wake in 1.6.2, disabled in 1.6.1(experimental)
Kexec Hardboot for MultiRom
Dynamic Fsync Control
Stock Google 4.7GCC prebuilt toolchain.
CIFS.
Theres a few other tweaks I made for overall UI performance other than that it follows CM-11.0 source. I build these for my own personal use but upload to share them for those who want what I run.
Click to expand...
Click to collapse
Sounds great, although most of it are books with seven seals for me
What about nfs support? And its definitely for 4.4.2 based ROMs?
Thx again,
Nix
Yes to both. It has NFS and CIFS support.
And v.1.6 is the one you'd suggest?
Nixblicker said:
And v.1.6 is the one you'd suggest?
Click to expand...
Click to collapse
Yes.
Snuzzo said:
Yes.
Click to expand...
Click to collapse
One more question, please - do I have to activate or load those modules manually or will they be loaded at bootup by default?
Where may I find them to insmod/modprobe them manually, if not?
Thanks for the help once more,
Cheerio,
Nix
They will load by default.
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