Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you've been following my Twitter feed, you will have noticed i've finally started playing with (and enjoying) my Tab.
I've been playing with ROM updates, ClockworkMod recovery and other bits and bobs, and here is the first fruit of my labour - MoDaCo Custom Kernel r1 for the Samsung Galaxy Tab.
What? Why?
Koush has posted his EXT4 converting ClockworkMod release / kernel at XDA-Developers, however unfortunately it breaks a fair few things on the latest ROMs for international Tabs - keyboard backlights, rotation, camera and a few other bits. So, I set about compiling up my own kernel using Samsung's source, with the aim of including all of Koush's great additions plus the usual TUN and CIFS modules, as well as including things like IKCONFIG to make kernel development easy for others (particularly as I plan to upload the whole lot to github). As well as releasing for EXT4 / ClockworkMod, i've packaged it for standard RFS ROMs. The kernel / ramdisk is 'insecure' (for adb remount etc.).
This turned out to be somewhat traumatic due to the 'update1' Samsung source refusing to work on my device, but I got there in the end. So this is a prelude to the MoDaCo Custom ROM... my MoDaCo Custom Kernel.
Requirements
This kernel has been tested on a number of Tabs running a number of different ROMs with no issues. It comes in two versions - a simple 'RFS' version to use with a regular ROM, or the 'EXT4 ClockworkMod' version if you already have (or wish to) convert to EXT4.
In order to use either kernel you need to be familiar with flashing via Odin or Heimdall, although you could in theory extract the TAR file and flash using 'flash_image' I guess.
If you plan to do the EXT4 conversion, you MUST have a microSD inserted with enough space to do a backup of your system / data partitions (so this will depend on how much data is on your device).
YOU SHOULD BACKUP BEFORE INSTALLATION OR BE FAMILIAR USING ODIN / HEIMDALL FOR FULL SYSTEM RECOVERY IN CASE OF A SERIOUS ISSUE. YOU USE THESE DOWNLOADS AT YOUR OWN RISK!
This kernel is ONLY tested on a UK Galaxy Tab. It MAY work on other GSM Tabs, it almost certainly WON'T work on a CDMA Tab. If you have a non UK Tab and want to test (and know how to flash back to a regular version), then go ahead and report your results. At your own risk.
How to
RFS version
To use the RFS version (i.e. you have not converted to EXT4 yet and don't wish to)...
Download the RFS TAR file from below
Flash using ODIN (version 1.7, do not select the 'repartition' option)
Reboot, you're done!
Optionally download the kernel modules zip (for TUN/CIFS) and copy to a location of your choice
Simple huh?
EXT4 version
To use the EXT4 version (i.e. you are already running EXT4 or you wish to convert)...
Download the EXT4 TAR file from below
Flash using ODIN (version 1.7, do not select the 'repartition' option)
IF YOU NEED TO UPGRADE TO EXT4: Your device won't reboot normally - that's OK, just turn it off (hold down power button for 5 seconds)
IF YOU NEED TO UPGRADE TO EXT4: Load recovery - turn the device on with 'volume up' held
IF YOU NEED TO UPGRADE TO EXT4: Your device will now perform the EXT4 conversion - depending on the volume of your data, this can take a while, so be patient
Reboot, you're done!
Optionally download the kernel modules zip (for TUN/CIFS) and copy to a location of your choice
Downloads
DOWNLOAD
And finally
I hope this is usual for everyone - i've found this is a real performance boost (particularly with the newest ROMs) and I look forward to rolling MCR out for the Tab! I'll have the kernel in GitHub soon, after which i'll post the URL here.
Enjoy!
P
Changelog
r3 26/Jan
Additional governor / scheduler options
Battery icon fix for when device is powered off
Other minor tweaks
r2 24/Jan
Set default governor to 'on demand'
Added Fuse module (by request)
MCK version now shown in about
Updated compiler
EXT4 performance tweaks
r1 23/Jan
Initial release
Looks good!
Great too see you here!
Looking forward to the first MCR!
Does the RFS version include CWM?
On what versions will this work?
Thanks for the effort you put into this. Can you please tell on what version the base Tab must be, to make this kernel work? And also, if it will work with the protected bootloaders?
Thanks again!
Testing it now on Roger/AT&T GSM Tab i987.
It is backing up and converting to ext4 right now.
It would be helpful if you put GSM in the title, or Euro for that matter, if that's the case.
Cheers Paul,
Will give the EXT4 a whirl once I work out the pros/cons
Confirmed that it works for NA GSM Tabs. Converted everything over to ext4 and working.
No real increase in speed really. Quadrant scores are about the same...around 1000.
Gallery has some glitches were it does not show pictures the first time...have to exit and come back in.
Let's give it a shoot
Sent from my GT-P1000 using Tapatalk
rmanaudio said:
Confirmed that it works for NA GSM Tabs. Converted everything over to ext4 and working.
No real increase in speed really. Quadrant scores are about the same...around 1000.
Gallery has some glitches were it does not show pictures the first time...have to exit and come back in.
Click to expand...
Click to collapse
I get this on all my Android devices now and again if a media index is running (generally soon after a boot)...
P
paulobrien said:
I get this on all my Android devices now and again if a media index is running (generally soon after a boot)...
P
Click to expand...
Click to collapse
Really weird problem where browser (with google.com as homepage) starts to rotate itself once you open browser till it is upside down!
If you have any issues, please post your ROM version and whether you are on the latest release.
I am on XXJMF and don't experience the issues mentioned above.
P
Great work man thank you!!! Only 1 ( noob i think question ) : what exactly do the additionals zip TUN/CIFS?
Frustu said:
Great work man thank you!!! Only 1 ( noob i think question ) : what exactly do the additionals zip TUN/CIFS?
Click to expand...
Click to collapse
If you don't know what they are, you don't need them
Screenshot from r2 (coming tomorrow).
P
TheGrammarFreak said:
If you don't know what they are, you don't need them
Click to expand...
Click to collapse
Ah ok thank you ... But i m curious please tell me
Im on Roto JME v4...and only problem found is Web browser rotates itself 180 degrees when you start it up.
Frustu said:
Ah ok thank you ... But i m curious please tell me
Click to expand...
Click to collapse
http://lmgtfy.com/?q=What+is+CIFS
http://lmgtfy.com/?q=What+is+TUN
TheGrammarFreak said:
http://lmgtfy.com/?q=What+is+CIFS
http://lmgtfy.com/?q=What+is+TUN
Click to expand...
Click to collapse
Well i learn 2 new things thank you
As everyone knows mokee official release uses a old kernel build from month of may, while the latest kernel is from sept. So I have made a repack of the latest kernel. As far my primary tests everything is working so just flash it and enjoy the latest one, incase xiaomi updates their kernel and anyone uses it but mokee, I will repack again and update the thread.
Enjoy!
ps: Sorry no flashable zip available. please report any bug you may find!
Steps:
1. enable usb debugging
2. connect to pc and open adb
3. copy the downloaded boot.img file to the adb folder.
4.open cmd, navigate to adb folder and type these lines one by one.
adb reboot-bootloader
fastboot flash boot boot.img
fastboot reboot
5. after reboot, just copy the 2nd downlaoded file "pronto_wlan.ko" to /system/lib/modules/pronto and replace the existing file,
6. change the permission to rw-r-r
7. reboot and enjoy the latest kernel.
If anyone can make a twrp/cwm flashable zip, you can share here.
Download
Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
thnx to the help from
kapil.git
Thanks for the Wake Up!!
saurabhrck said:
As everyone knows mokee official release uses a old kernel build from month of may, while the latest kernel is from sept. So I have made a repack of the latest kernel. As far my primary tests everything is working so just flash it and enjoy the latest one, incase xiaomi updates their kernel and anyone uses it but mokee, I will repack again and update the thread.
Enjoy!
ps: Sorry no flashable zip available. please report any bug you may find!
Steps:
1. enable usb debugging
2. connect to pc and open adb
3. copy the downloaded boot.img file to the adb folder.
4.open cmd, navigate to adb folder and type these lines one by one.
adb reboot-bootloader
fastboot flash boot boot.img
fastboot reboot
5. after reboot, just copy the 2nd downlaoded file "pronto_wlan.ko" to /system/lib/modules/pronto and replace the existing file,
6. change the permission to rw-r-r
7. reboot and enjoy the latest kernel.
If anyone can make a twrp/cwm flashable zip, you can share here.
Download
Screenshot:
thnx to the help from
kapil.git
Click to expand...
Click to collapse
deadlyindian said:
Thanks for the Wake Up!!
Good Work Brothers !!!!:laugh::laugh::laugh:
Keep it up.....:good::good::good:
But, if I am not wrong Xiaomi has not released any kernel sources and so all of our Devs are using only headers for compiling the ROM and so they are just changing the date in headers. Does this matters in performance, or stability?
Please do correct me, if I am wrong anywhere. I am always ready to learn new things.
Best Regards
BOND
Click to expand...
Click to collapse
SuperDroid-BOND said:
Good Work Brothers !!!!:laugh::laugh::laugh:
Keep it up.....:good::good::good:
But, if I am not wrong Xiaomi has not released any kernel sources and so all of our Devs are using only headers for compiling the ROM and so they are just changing the date in headers. Does this matters in performance, or stability?
Please do correct me, if I am wrong anywhere. I am always ready to learn new things.
Best Regards
BOND
Click to expand...
Click to collapse
xiaomi has not released kernel source dts right, but they are updating kernel while they update miui rom(secure source), devs are actually using that updated kernel which is made by xiaomi. Mokee on the other hand was using a old kernel and they were not updating , so I took the liberty to update it.
saurabhrck said:
xiaomi has not released kernel source dts right, but they are updating kernel while they update miui rom(secure source), devs are actually using that updated kernel which is made by xiaomi. Mokee on the other hand was using a old kernel and they were not updating , so I took the liberty to update it.
Click to expand...
Click to collapse
You did the right thing brother and thanks (I already pressed it for both of you) for keeping us updated.
So, you mean to say that Xiaomi has updated the kernel and sources but its secured only, not public. If it is like this, would you mind linking us to those sources, because there are so many ROMs waiting for some fixed kernel sources or if you can tell us what things have been fixed, can we use single SIM with this code "
Code:
setprop persist.radio.multisim.config none
".
We, all the users, can get several ROM with almost all utmost and best features available. Please do let me know about the kernel, best if we could talk on PM.
Best Regards
BOND
The Kernel gets updates by new Miui releases...i'll give a notable example to prove that !
Before v41.1 there isn't built in Zram implemented but with new kernel (v41.1+) there is Zram Support !
SuperDroid-BOND said:
You did the right thing brother and thanks (I already pressed it for both of you) for keeping us updated.
So, you mean to say that Xiaomi has updated the kernel and sources but its secured only, not public. If it is like this, would you mind linking us to those sources, because there are so many ROMs waiting for some fixed kernel sources or if you can tell us what things have been fixed, can we use single SIM with this code "
Code:
setprop persist.radio.multisim.config none
".
We, all the users, can get several ROM with almost all utmost and best features available. Please do let me know about the kernel, best if we could talk on PM.
Best Regards
BOND
Click to expand...
Click to collapse
The source is secure to xiaomi, they are not releasing to public as of now. Don't know whats the reason for this idiotic move. Anyway I don't have the source, like anyone else, I just repacked with proper module. dts all! Will update when xiaomi releases a new update
saurabhrck said:
The source is secure to xiaomi, they are not releasing to public as of now. Don't know whats the reason for this idiotic move. Anyway I don't have the source, like anyone else, I just repacked with proper module. dts all! Will update when xiaomi releases a new update
Click to expand...
Click to collapse
so is it repack of old ramdisk and new zimage... btw can u please give me link/info about the tool which u have used to repack kernel.. i tried to make kernel unsecure once but cant make it boot... kernel size reduced ~4 mb....
deadlyindian said:
Thanks for the Wake Up!!
Is no need to set permission at pronto wlan ?
Click to expand...
Click to collapse
pgreed said:
Is no need to set permission at pronto wlan ?
Click to expand...
Click to collapse
Nope its automatically set when phone boots...
What are the features of the kernel? This for mokee only? Any version??
This kernel don't work with UNOFFICIAL version of Mokee. When just install w/o wipe dalvik/cache at the middle of boot (before launching apps) phone reboot. If wipe dalvik/cache the font used to say Android update... is very small (as density is around 400dpi!!) and after app is launched phone reboot.
pgreed said:
This kernel don't work with UNOFFICIAL version of Mokee. When just install w/o wipe dalvik/cache at the middle of boot (before launching apps) phone reboot. If wipe dalvik/cache the font used to say Android update... is very small and after app is launched phone reboot.
Click to expand...
Click to collapse
ofcourse it will not work with unofficial version. unofficial version is based on cm11 source and uses that prebuilt kernel. you have to repack it separately for that. This one is only for mokee official release which uses mokee kernel/device files not from cm11, mentioned in OP!
saurabhrck said:
ofcourse it will not work with unofficial version. unofficial version is based on cm11 source and uses that prebuilt kernel. you have to repack it separately for that. This one is only for mokee official release which uses mokee kernel/device files not from cm11, mentioned in OP!
Click to expand...
Click to collapse
No it use the 8 May kernel! (is the sychost unofficial)
Shahi00 said:
The Kernel gets updates by new Miui releases...i'll give a notable example to prove that !
Before v41.1 there isn't built in Zram implemented but with new kernel (v41.1+) there is Zram Support !
Click to expand...
Click to collapse
So you mean Roms above 41.1 have zram implemented? before that it was not available?
Shahan_mik3 said:
So you mean Roms above 41.1 have zram implemented? before that it was not available?
Click to expand...
Click to collapse
Yep...even though we have 1GB RAM it is done that way !
I am very sure that V36 don't have ZRAM and V41.1 and above have it...that's the way they found to currect RAM management !
it causes a bit battery drain & and performance regression !
pgreed said:
This kernel don't work with UNOFFICIAL version of Mokee. When just install w/o wipe dalvik/cache at the middle of boot (before launching apps) phone reboot. If wipe dalvik/cache the font used to say Android update... is very small (as density is around 400dpi!!) and after app is launched phone reboot.
Click to expand...
Click to collapse
link for mokee unofficial plz..
RohanAJoshi said:
link for mokee unofficial plz..
Click to expand...
Click to collapse
Because from Mokee site was deleted all unofficial and experimental version (I dunno why) I've upload the file elsewhere:
Shahi00 said:
Yep...even though we have 1GB RAM it is done that way !
I am very sure that V36 dont have ZRAM and V41.1 and above have it...thats the way they found to currect RAM management !
it causes a bit battery drain & and performance regression !
Click to expand...
Click to collapse
Also I wanted to know. How is it possible to get a stable cm/aosp Roms on Redmi but not on mi3?
Shahan_mik3 said:
Also I wanted to know. How is it possible to get a stable cm/aosp Roms on Redmi but not on mi3?
Click to expand...
Click to collapse
Our developer is good enough for tracking bugs that causes Random Reboots !!
Kra always did that (on previous phone too)
:good:
August 22: Rom Updated to Beta 0.6 (LP 5.1.1 r13). Latest sources.
TWRP 2.8.7 in boot: Manual brightness is fixed by changing horrendously high back light value (18x Sony's high limit) mistakenly put in by Slim team resulting in no manual brightness and overheating. This is fixed now.
Download Link: http://forum.xda-developers.com/devdb/project/dl/?id=14141
Dirty flashing is fine if you are on my previous build.
______________________________________________________________________________________________________________
August 10: Rom Updated. This is Beta 0.4 (LP 5.1.1 r9). Latest Slim changes. Updated M5 kernel with CPU and GPU overclock. Kernel size reduced by 2 mb. Also incorporated latest CM commits into device tree to address some screen flickering. http://review.cyanogenmod.org/#/c/105489/
Download Link: http://forum.xda-developers.com/devdb/project/dl/?id=13920
You can flash dirty if upgrading from the previous build, just keep in mind that if you use Xposed, you must flash it before reboot. This also applies to Supersu. Otherwise, fresh install.
___________________________________________________________________________________________________________
August 6. This is LP 5.1.1 release 9. No heat issues. Also includes M5 hardened kernel with overclocked CPU to 2457 and GPU to 600.
Download: http://forum.xda-developers.com/devdb/project/dl/?id=13858
Kernel Source: https://github.com/AOSPME/android_kernel_sony_msm8974
___________________________________________________________________________________________________________
August 3: Guys. Stay away from July 25 build. It does cause overheating. I had an episode where my phone shut down and refused to boot for an hour. I guess Slimroms still have problems. Pitty. I have removed the download link...
July 29: Update addressing wifi disconnect after 15 min of sleep and excessive battery drain caused by arp packets related wakelocks
Download and description: http://forum.xda-developers.com/showpost.php?p=62102698&postcount=15
No need to wipe anything if you were on my previous build.
_____________________________________________________________________________________________________________
July 25: Rom updated to LP 5.1.1 r8. This is my change, since Slimrom team still uses earlier releases. They have substantially improved the rom sources, so, whatever I said about them in the past no longer applies.
1. Latest Google AOSP changes
2. Latest Slim changes
3. All my regular hardened features including hardened kernel, removed nefarious IPs, full network selection in Network, disabled wifi background scanning are in
4. Modified M5 kernel
5. Twrp 2.8.7 as a Fota image. The reason I put 2.8.7 in fota is that Slimteam still uses version 2.8.6, which has major bugs. In 2.8.7 most were fixed.
Instructions: Note that the boot.img does not include any recovery to prevent a collision with fota recovery
1. In TWRP format Data, then format System/Data/Cache
2. Flash the rom (don't reboot in system unless you already have recovery in fota)
3. Reboot in Bootloader
4. Flash TWRP.img like this: fastboot flash recovery twrp.img
5. Reboot
Download links: Removed
Kernel Source: https://github.com/AOSPME/android_kernel_sony_msm8974
Credit: AOSP, Slimroms, Myself5
__________________________________________________________________________________________________
Rom updated to 5.1 version alpha. All hardened/security features are in. TWRP 2.8.6 is integrated into kernel.
Download link: http://forum.xda-developers.com/devdb/project/dl/?id=12197
Kernel Source: https://github.com/AOSP-Argon/kernel_sony_msm8974/tree/lp5.1
___________________________________________________________________________________________________
Here is the latest Slimrom Lollipop built on February 18.
Main changes:
Disabled creepy Selinux and activated Tomoyo as main security provider
Enabled all ciphers, as opposed 2 or 3 in standard releases
Enabled all hashes, digests and compression modes
Enabled all hashes for random number generation to result in a speedier device
Enabled 256 (as opposed to 128) bit encryption for device encryption
Increased weak 2048 RCA key length to 4096
Changes are implemented on kernel level and in /system/core/vold. As a result, you have a more secure and faster device with real protection for you; whereas Selinux, in my view, apart from being developed by an entity known for spying on people on mass scale, "secures" the device from you - meaning you are prevented from interfering with the constant flow of data from your device to their servers ...
Bugs: up-to-date Slimrom bugs
Credit: Slimroms
Modified Sources:
https://github.com/optimumpr/kernel_sony_msm8974
https://github.com/optimumpr/android_system_vold-1
Install Instructions:
1. Be on Kitkat, have root and recovery
2. Enter recovery, wipe Data/Cache/System
3. Flash the rom
4. Don't reboot yet: for some reason Documents.app does not appear anywhere and there is no file manager to handle app install; therefore
5. Flash Slim file manager from kitkat (see Download links at the bottom of this post), which works on lollipop.
6. Now, reboot and enjoy
Download links for Main rom and Slimfilemanager are at the bottom of this post.
Read about getting recovery on honami here: http://forum.xda-developers.com/xperia-z1/general/recovery-solution-lollypop-roms-t3000822/post58127334#post58127334
TWRP is now integrated, see post #5 for download.
Warning: I am not responsible for the destruction of your device and damage to surrounding areas. You are at your own peril. Also, if you don't care about security, stay away from this thread and get the regular version of this rom, which is available in Original Development or on Slimroms website. Comments or discussion about necessity for security, especially by those who have no idea what they are talking about, won't be tolerated. You have been warned.
DOWNLOAD LINKS:
Rom http://d-h.st/dfo
Slim File Manager http://d-h.st/Aqu0 flash it right after the rom before rebooting
XDA:DevDB Information
Slim Lollipop Hardened Secure, ROM for the Sony Xperia Z1
Contributors
optimumpro
Source Code: https://github.com/SlimRoms/platform_manifest
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked bootloader
Based On: Slimroms
Version Information
Status: Alpha
Created 2015-02-19
Last Updated 2015-08-22
Reserved
screenshoots?? http://cdn3.xda-developers.com/images/smilies/smile.gif
kriswal123 said:
screenshoots?? http://cdn3.xda-developers.com/images/smilies/smile.gif
Click to expand...
Click to collapse
Sorry, I played with the rom for a day and went back to kitkat.
The looks are the same as in the latest Slimrom LP, which is posted on Slimrom website, as well as in the original Android Development thread...
Kernel with integrated TWRP
Here is SlimLP kernel with integrated TWRP recovery. From now and on, you don't need to reflash your device when changing roms, especially from Lillipop to kitkat or deal with the FOTA partition.
Just unzip the attached file and flash it in Fastboot:
fastboot flash boot boot.img
fastboot reboot
For those of you who already have TWRP in FOTA partition, as you know, this recovery collides with the integrated recovery. So, if you have TWRP in FOTA, do this after installing my kernel:
fastboot erase recovery
fastboot reboot
This will get rid of TWRP in FOTA
Do you plan to update this ? (I am sorry I have posted in almost all your threads but all lollipop rom (Except CM12) keeps on freezing for me
and I want to use a rom with selinux disabled (so that i can use xprivacy)
I tried RR hardened and validus. Both freeze...
never saw any freeze in 4.4.4
ggs2 said:
Do you plan to update this ? (I am sorry I have posted in almost all your threads but all lollipop rom (Except CM12) keeps on freezing for me
and I want to use a rom with selinux disabled (so that i can use xprivacy)
I tried RR hardened and validus. Both freeze...
never saw any freeze in 4.4.4
Click to expand...
Click to collapse
I think Slimrom team is no longer updating lollipop 5.0. They are working on 5.1. Nor are they updating kitkat. But you can use any kernel from my lollipop roms, as selinux is disabled there. You can also use my kernel with cm12, although, I am not sure CM12 would work with xprivacy. Out of all lollipops, only SlimLP and RR5.0 work with Xprivacy. RR works straight. Validus works for me with data partition restored from RR5.0. What I did was to first install RR5.0+Xposed+Xprivacy (confirmed it worked), then backed up data, then full wipe, installed Validus , then without reboot xposed, then without reboot restored data from RR5.0 and it works...
optimumpro said:
I think Slimrom team is no longer updating lollipop 5.0. They are working on 5.1. Nor are they updating kitkat. But you can use any kernel from my lollipop roms, as selinux is disabled there. You can also use my kernel with cm12, although, I am not sure CM12 would work with xprivacy. Out of all lollipops, only SlimLP and RR5.0 work with Xprivacy. RR works straight. Validus works for me with data partition restored from RR5.0. What I did was to first install RR5.0+Xposed+Xprivacy (confirmed it worked), then backed up data, then full wipe, installed Validus , then without reboot xposed, then without reboot restored data from RR5.0 and it works...
Click to expand...
Click to collapse
I tried all of your roms.. Xprivacy worked in all of them but i have this screen freeze issue which makes my phone particularly unusable.
I think i would revert to kitkat for now. That was smooth and solid... Thanks....
Rom Updated to 5.1
See OP for SlimLP 5.1.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
my wifi kept dropping out and i cannot turn it on except rebooting, is this a known problem ?
New build is up
Rom updated. See OP for download and description.
@Diewi
I thought we could move our discussion on wifi to this thread. Here is a little dirty secret: that qcom binary file is found in kernel too. So, if you change it in /etc/firmware/, you also have to copy the changed file to your kernel's /drivers/staging/prima/firmware_bin/ directory and then recompile the kernel. As usual, the entries there will go to kernel wifi module, which is actually not a module anymore, but a built-in in kernel. Otherwise, the changes won't work. Hence, there goes your android framework messing up things...
I have done it and am back to Kitkat level of battery drain with no disconnect. Here is my file: I did return to gEnableSuspend = 3 and made some more changes.
optimumpro said:
I thought we could move our discussion on wifi to this thread.
Click to expand...
Click to collapse
Fine with that.
optimumpro said:
Here is a little dirty secret: that qcom binary file is found in kernel too. So, if you change it in /etc/firmware/, you also have to copy the changed file to your kernel's /drivers/staging/prima/firmware_bin/ directory and then recompile the kernel. As usual, the entries there will go to kernel wifi module, which is actually not a module anymore, but a built-in in kernel. Otherwise, the changes won't work. Hence, there goes your android framework messing up things...
I have done it and am back to Kitkat level of battery drain with no disconnect. Here is my file: I did return to gEnableSuspend = 3 and made some more changes.
Click to expand...
Click to collapse
Sorry, I have to disagree. Here, things are a bit different from the android framework. Please have a look at the file "CORE/HDD/src/wlan_hdd_cfg.c" of the prima driver, especially the method "hdd_parse_config_ini". The comment clearly states that the ini-file is parsed:
/*
* This function reads the qcom_cfg.ini file and
* parses each 'Name=Value' pair in the ini file
*/
This also matches my experience that modifying the cfg.ini on the device does indeed have an effect.
Just one more note: By the concept accessing external files), it should not make any difference on reading external file if you compile modules inside the kernel or as "seperate" modules. However, there exist quite a lot device drivers out there which require to be build as modules to load their firmware (due to being depend upon some "external" firmware loader etc.). The prima driver obviously does not belong to these kind drivers.
Nevertheless, those changes should be pushed upstream (cm), then they would reside in the driver directory of the kernel anyways
Regards,
Diewi
Diewi said:
Fine with that.
Sorry, I have to disagree. Here, things are a bit different from the android framework. Please have a look at the file "CORE/HDD/src/wlan_hdd_cfg.c" of the prima driver, especially the method "hdd_parse_config_ini". The comment clearly states that the ini-file is parsed:
/*
* This function reads the qcom_cfg.ini file and
* parses each 'Name=Value' pair in the ini file
*/
This also matches my experience that modifying the cfg.ini on the device does indeed have an effect.
Just one more note: By the concept accessing external files), it should not make any difference on reading external file if you compile modules inside the kernel or as "seperate" modules. However, there exist quite a lot device drivers out there which require to be build as modules to load their firmware (due to being depend upon some "external" firmware loader etc.). The prima driver obviously does not belong to these kind drivers.
Nevertheless, those changes should be pushed upstream (cm), then they would reside in the driver directory of the kernel anyways
Regards,
Diewi
Click to expand...
Click to collapse
I don't dispute that the file is being parsed, my point is that because the same file with different entries is in kernel, we really don't know how they would interact.
Update to fix wifi disconnect and battery drain
Here is a recompiled kernel as well as a separate file to flash. This takes care of wifi disconnect after 15 minutes of sleep as well as excessive battery drain caused by a barrage of arp packets that create wakelocks.
Instructions:
1. Flash WIFI_DRAIN_FIX in Recovery
2. After that reboot in Bootloader and flash kernel (unzip boot.img): fastboot flash boot boot.img
3. If you have fota recovery, don't reboot and erase fota recovery, because this boot.img has twrp: fastboot erase recovery.
TWRP 2.8.7 has a bug preventing backing up roms. So, it is no good, unfortunately. I have returned to an earlier build.
Kernel Source: https://github.com/AOSPME/android_kernel_sony_msm8974
Warning: Don't use this for any other rom, because this kernel is specific to SLimrom.
optimumpro said:
I don't dispute that the file is being parsed, my point is that because the same file with different entries is in kernel, we really don't know how they would interact.
Click to expand...
Click to collapse
I get your point, but please have a look at the Android.mk file in the directory of the prima driver. There it is clearly stated that the files in the firmware_bin sub directory are just copied to the dir "${OUT}/system/etc/firmware/wlan/prima/". Hence, the "same" file does not exist in the kernel. BTW, beware, if you modify the file directly in your kernel folder as it will not be copied to the ${OUT} directory if the file exists there already. This is a serious weakness of the android build system IMHO.
The cfg-file will be parsed when the driver loads.
Sorry, for being that insistent
Diewi said:
I get your point, but please have a look at the Android.mk file in the directory of the prima driver. There it is clearly stated that the files in the firmware_bin sub directory are just copied to the dir "${OUT}/system/etc/firmware/wlan/prima/". Hence, the "same" file does not exist in the kernel. BTW, beware, if you modify the file directly in your kernel folder as it will not be copied to the ${OUT} directory if the file exists there already. This is a serious weakness of the android build system IMHO.
The cfg-file will be parsed when the driver loads.
Sorry, for being that insistent
Click to expand...
Click to collapse
Well. This same file resides in sony_rhine_common overlay. So, what I do is put the changed file in both directories. Anyway, this is the first time on lollipop that I have absolutely no wifi disconnection. And wifi range has increased too (I increased the tx cap to 80).
I have very very strange issue (only on this slim rom)!
My charging sometime stops, and i have to reboot phone to get it back to charging. anyone has same issue?
ggs2 said:
I have very very strange issue (only on this slim rom)!
My charging sometime stops, and i have to reboot phone to get it back to charging. anyone has same issue?
Click to expand...
Click to collapse
I don't think anyone else has it. In case you are talking about charging through usb: some linux distros drop usb connections during sleep and then have trouble reconnecting, because the phone is sleeping. You may have a similar behavior in Windows...
Just a remark, It seems that the file ending is a bit messed up. Or rather missing.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MultiROM is a one-of-a-kind multi-boot mod. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.
WARNING
It is dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
IMPORTANT
1. I'm not responsible for anything, you do all this on your own risk.
2. Once you have flashed and set up MultiROM, don't flash another boot.img using fastboot or normally. Always go to "Advanced -> MultiROM" to flash ROMs/kernels or other mods.
3. If you want to uninstall MultiROM, just flash the MultiROM uninstaller.
4. I am not certainly sure about the compatibility with stock Roms, I still need to test this yet.
5. Your device must not be encrypted.
6. To all devs maintaing Stock-based ROMs: Feel free to use my patched stock kernels to add MultiROM support to your ROMs.
7. When booting another ROM, you'll notice that in some cases, you can enter the recovery of the boot.img of the ROM. Please don't use it, flash everything using MultiROM TWRP.INSTALLATION
1. Make sure you are on a rom compatible with these kernels.
2. Flash the required kernel zip.
3. Flash MultiROM_TWRP-xx-xx-xxxx.img on fota partition.
4. Flash MultiRom_xx-xx-xxxx-v31x.zip
5. Done1Adding ROMs
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs).
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android Rom
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
SOURCEs
MultiROM - https://github.com/XperiaMultiROM/multirom/ (branch old)
Modified TWRP - https://github.com/XperiaMultiROM/an...table_recovery (branch master)
Kernel w/ kexec-hardboot patch - https://github.com/aweosomeabhijeet/android_kernel_sony_msm8x27 (cm-Kernel)
CREDITs
Tasssadar
Alvinhochun - without his kexec patch, it would have been impossible for me, kudos to him :highfive:
Xperia Multirom
Myself5
Every other dev behind this
If you think my work is good, please consider a small donation
Donate to me
You might want to consider a Donation to Tasssadar, who is the Mastermind behind all of this, I just ported it to the M
Donate to Tasssadar
XDA:DevDB Information
MultiRom for Xperia M, Tool/Utility for the Sony Xperia M
Contributors
aweosomeabhijeet, alvinhochun, XperiaMultirom
Source Code: https://github.com/XperiaMultiROM/multirom/
Version Information
Status: Stable
Current Stable Version: v31x
Stable Release Date: 2015-08-13
Created 2015-08-07
Last Updated 2015-08-13
BUGs
NO BUGS as of now
LIMITATIONs
1. For MTP to work in TWRP you need to disable and enable it again.
CHANGELOG :
Code:
2015-08-13
Stable release!
Fixed minor touch issues present in the kernel by [email protected] !
2015-08-07
Beta version
Fixed erasing primary rom with secondary
Fixed wifi
2015-08-07
Initial release!
DOWNLOADS
Kernels with kexec-hardboot support :
XMS-stock-Kexec.zip(To be flashed in recovery)(not yet tested)
XMD-stock-Kexec.zip(To be flashed in recovery)(not yet tested)
XM_CM_kexec-08-13-2015.zip(has touch screen issue)
Other kernels with kexec-hardboot support:
1. NUI kernel(kudos to dev.)
Instructions to use NUI kernel
MultiROM TWRP :
recovery.img(To be flashed on fota-partition)
MultiROM-zip :
multirom-20150813-v31x-UNOFFICIAL-nicki.zip(To be flashed in recovery)
Use sdcard class 10 to boot cm11, run very smoothly
Great work, thang's ..
Sent from my waifu
Superb job @aweosomeabhijeet
And u can even add XMD in thread title bcoz it even works on it.. I am XMD user.. It's working well
@aweosomeabhijeet, to prevent compatibility issues that may occur it will be better to use boot image repacking script (e.g. with unpackbootimg and mkbootimg utilities) that will inject new zImage (it is kernel file in your out/target/product/nicki folder) in boot image than flashing raw boot.img, so ramdisk will not be overridden (as far as I understand we don't need changes in ramdisk for kexec, do we? and even if we do, it will be better to replaced only changed files, not the whole ramdisk). Noel Macwan uses that thing in his kernels, I used his script as base for my old injecting CWM/TWRP script.
---------- Post added at 21:26 ---------- Previous post was at 20:57 ----------
BTW, what kernel sources did you use for your kexec-patched kernel? Are they Sony stock ones? Aren't they from CM12.1 repo?
SUCCESS
so today i successfully flashed 3 roms on in XMD which run smoothly..the only problem i faced is patience when flashed through recovery i in usbdisk (which is obvious)..so now i dont need to wipe or format my primary rom in oder to test other builds..fabulous job @aweosomeabhijeet
Now mutlirom thread is active almost after one and half year for our xperia m...
All credits to u...
[deleted]
cucumber09 said:
@aweosomeabhijeet, to prevent compatibility issues that may occur it will be better to use boot image repacking script (e.g. with unpackbootimg and mkbootimg utilities) that will inject new zImage (it is kernel file in your out/target/product/nicki folder) in boot image than flashing raw boot.img, so ramdisk will not be overridden (as far as I understand we don't need changes in ramdisk for kexec, do we? and even if we do, it will be better to replaced only changed files, not the whole ramdisk). Noel Macwan uses that thing in his kernels, I used his script as base for my old injecting CWM/TWRP script.
---------- Post added at 21:26 ---------- Previous post was at 20:57 ----------
BTW, what kernel sources did you use for your kexec-patched kernel? Are they Sony stock ones? Aren't they from CM12.1 repo?
Click to expand...
Click to collapse
Indeed a very good idea, but I am worried about pure stock users. I think the script won't work, though I haven't tried.
They are from CM repo only, I am fixing some issues will push changes to my fork of CM kernel.
aweosomeabhijeet said:
Indeed a very good idea, but I am worried about pure stock users. I think the script won't work, though I haven't tried.
They are from CM repo only, I am fixing some issues will push changes to my fork of CM kernel.
Click to expand...
Click to collapse
We can make different zip for pure stock and for custom ROMs. But is now MR working on stock? Doesn't it have split screen bug? If yes, you should try using custom recovery graphics, and I am not familiar to C, so can't help. And BTW does stock work with CM kernel? I very doubt it. Even if it will work with stock ramdisk and CM zImage (which I doubt too, as CM kernel is built on CAF sources with some changes from stock kernel if I'm not wrong), it surely won't work with full CM boot image, so repacking script will be the best solution (I can even make it for you today if changes in initrd are not needed). And if stock will boot with CM zImage we will not have screen split bug anymore, and script also should work even with stock (as the command line is the same, and even if not, we can read it from unpackbootimg output by using `cat *.img-cmdline` for command line value in script). But building different kernels for stock and custom ROMs (all custom ROMs for our device share the same kernel source, difference is only in ramdisk, you can even boot CM11 with CM12.1 kernel if you will keep CM11's ramdisk) is better solution.
cucumber09 said:
We can make different zip for pure stock and for custom ROMs. But is now MR working on stock? Doesn't it have split screen bug? If yes, you should try using custom recovery graphics, and I am not familiar to C, so can't help. And BTW does stock work with CM kernel? I very doubt it. Even if it will work with stock ramdisk and CM zImage (which I doubt too, as CM kernel is built on CAF sources with some changes from stock kernel if I'm not wrong), it surely won't work with full CM boot image, so repacking script will be the best solution (I can even make it for you today if changes in initrd are not needed). And if stock will boot with CM zImage we will not have screen split bug anymore, and script also should work even with stock (as the command line is the same, and even if not, we can read it from unpackbootimg output by using `cat *.img-cmdline` for command line value in script). But building different kernels for stock and custom ROMs (all custom ROMs for our device share the same kernel source, difference is only in ramdisk, you can even boot CM11 with CM12.1 kernel if you will keep CM11's ramdisk) is better solution.
Click to expand...
Click to collapse
Actually you are getting it wrong!
1. We would not have any screen shift bug
2. Every ROM we boot from multirom can use it's own kernel irrespective of what kernel is installed in the device. (That's the benefit of kexec-hardboot)
3. I have a better idea for maintaing stock and all. Will upload new zip soon. I would like to use parts of your script if you don't mind.
BTW, why didn't you git clone kernel repository (it would save commit history and make your fork git-compatible with original) and then apply your patches? Otherwise, it will be harder to support your patched kernel, as it has another commit history and you if I am not wrong will not be able to merge and cherry-pick commits from CM kernel to your kernel, you will have to do it manually, which is quite annoying, or leave your kernel unupdated in future.
---------- Post added at 15:49 ---------- Previous post was at 15:45 ----------
aweosomeabhijeet said:
Actually you are getting it wrong!
1. We would not have any screen shift bug
2. Every ROM we boot from multirom can use it's own kernel irrespective of what kernel is installed in the device. (That's the benefit of kexec-hardboot)
3. I have a better idea for maintaing stock and all. Will upload new zip soon. I would like to use parts of your script if you don't mind.
Click to expand...
Click to collapse
Seems that we misunderstand each other. I talk about using other ROMs as primary, not only CM. We can do this by using kexec-ed kernel. I just offer you another method installing it, which will keep original ramdisk (if kexec doesn't need changes in it) and only replace kernel itself (zImage only, not boot image).
And I don't mind using parts of this script.
cucumber09 said:
BTW, why didn't you git clone kernel repository (it would save commit history and make your fork git-compatible with original) and then apply your patches? Otherwise, it will be harder to support your patched kernel, as it has another commit history and you if I am not wrong will not be able to merge and cherry-pick commits from CM kernel to your kernel, you will have to do it manually, which is quite annoying, or leave your kernel unupdated in future.
---------- Post added at 15:49 ---------- Previous post was at 15:45 ----------
Seems that we misunderstand each other. I talk about using other ROMs as primary, not only CM. We can do this by using kexec-ed kernel. I just offer you another method installing it, which will keep original ramdisk (if kexec doesn't need changes in it) and only replace kernel itself (zImage only, not boot image).
And I don't mind using parts of this script.
Click to expand...
Click to collapse
I know it. I have forked the repo and currently cloning. It's just in beta status and is just for giving details about the patch. I'll soon be on CM kernel and would merge all its commits and kernel would be updated always.
Don't you worry about it, I have all in mind. It takes time, I am free majorly on weekends so I won't rush on things.
I understand this and I have already made installer zip which does exactly what you are trying to tell, it uses parts of your script to replace just zImage and not whole boot.img. I still have something better coming. Just wait for few days.
aweosomeabhijeet said:
I know it. I have forked the repo and currently cloning. It's just in beta status and is just for giving details about the patch. I'll soon be on CM kernel and would merge all its commits and kernel would be updated always.
Don't you worry about it, I have all in mind. It takes time, I am free majorly on weekends so I won't rush on things.
I understand this and I have already made installer zip which does exactly what you are trying to tell, it uses parts of your script to replace just zImage and not whole boot.img. I still have something better coming. Just wait for few days.
Click to expand...
Click to collapse
Okay, that's nice. Sorry if I was too annoying.
Nice dev discussions
Sent from my waifu
itsnie said:
Nice dev discussions
Sent from my waifu
Click to expand...
Click to collapse
Dev and just-advanced-user discussion as I am not a developer. Just enthusiastic and sometimes full of curiosity user, nothing more. (BTW, we should stop OT not to make a mess in the thread)
It's not a order or request.. A small advice or suggestions.. Can you overclock ur kernel for more smoothness
kjinx01 said:
It's not a order or request.. A small advice or suggestions.. Can you overclock ur kernel for more smoothness
Click to expand...
Click to collapse
Please upload kernel.sin from build 15.5.A.1.5 if anyone here is having ftf of the same so that I can build for XMD stock devices. Thanks
Hey bro why does it take so long time to flash in recovery.. Any rom on sdcard takes abt 10 min to get flashed..??
aweosomeabhijeet said:
Please upload kernel.sin from build 15.5.A.1.5 if anyone here is having ftf of the same so that I can build for XMD stock devices. Thanks
Click to expand...
Click to collapse
here u go for it..i uploaded kernel.sin from 15.5.A.1.5 of XMD ftf stock rom
https://www.mediafire.com/?9dobzi8nu2tqzjy
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Development is Paused because AOSP is still being worked on and such.
Code:
I am not responsible for anything that happens to you or your phone or anything! You are allowed to use this kernel but It is not my fault in anyway for causing thermonuclear war or bricking your phone.
Welcome to Kermit Kernel.
Kermit Kernel is intended to be installed on AOSP and uses Anykernel2 to do so. I wanted to share my work with all of you and also provide a smooth, customisation experience for you. This project was inspired by kylothow's work on AOSP and Kernels and big thanks to him for helping me in the beginning!
Click to expand...
Click to collapse
FEATURES
- Based on DQIC Sources
- Powersuspend 1.7
- Asynchronious Fsync from HTC
- Blu_Active with modifications and such
- Boeffla Wakelock Blocker
- djb77's latest toolchain optimised for our devices
- Turn CRC off or on
- Init.d is supported
- Max and Min Frequencies for both CPU big and little have been increased
- Iron-active and Wheatley Governers
- A LOT of under the hood stuff for your user experience
I can take requests of course, don't be shy
I just want the kernel to be in favour of what seems good by users!
What is Anykernel?
You can skip this if you don't want to know how it works.
Kernels tend to have a fully built boot image ready, it just flashes everything and it may not PATCH the necassary files. This means you're gonna have to create a different boot image for different roms such S8 Ports, Note FE Ports and AOSP ROMS. Things such as compatibility maybe an issue also because new things may not be supported by old things (Newer RAMDISK on an older ROM).
That's when Anykernel comes into play. It only includes the zImage (actual prebuilt kernel), dtb (the instructions for hardware stuff), and patches used ontop of the stock ramdisk. It takes the previous/stock kernel, replaces dtb and zImage and then continues to patch the ramdisk. Voila, it's done. It makes it easier for the devs to work on the kernel and has better compatibility! It does come with it's disadvantages, It can't be flashed ontop of other custom kernels that have modifications in the ramdisk. The patch and ramdisk will cause some trouble because there interefering with each other alright!
Click to expand...
Click to collapse
How do I install this?
If you already have AOSP with it's stock kernel.
1) Reboot into recovery and flash it like normal
If you have AOSP with a custom kernel like PRIME, Prophecy or Primal.
1) Go to the AOSP ZIP you installed, extract boot.img from there.
2) Boot into recovery, flash the boot image. Don't forget to switch the option from ZIP to IMG if you can't find it in the directory you extracted it from.
3) Then go back to home screen in recovery, and go flash Excel Kernel
I really don't need to explain this in detail and such because if you got here it mean's you know how to install AOSP ROMS. It's pretty simple.
Telegram
The best possible way to reach me is through telegram and through my group! Theres two channels, one for new and the other for assistance and general things related to my kernel. (a bit of off-topic is always nice!)
This is my News Channel
https://t.me/kermitkernel
This is my Discussion Channel
https://t.me/kermittalk
Downloads
herolte: https://www.dropbox.com/s/69f1lzyh9ecz1zr/Kermit_Kernel-v1.3.0%CE%B2-herolte.zip?dl=0
hero2lte: https://www.dropbox.com/s/e95hmjfn770rwm2/Kermit_Kernel-v1.3.0%CE%B2-hero2lte.zip?dl=0
These builds have freshly been compiled, not thoroughly tested.
Old download links will be here
Old changelogs
Freshly compiled, none so far
Thanks to/Credits
Code:
- kylothow
- djb77
- morogoku
- samsung osrc
- tkkg1994
- osm0sis for anykernel2
- testers
- and everyone who helped in some way or another
I WILL improve this format. stick with it, thread will look nicer.
ik it's ugly man. liek what is this. chiiiiiilll
XDA:DevDB Information
Kermit Kernel, Kernel for the Samsung Galaxy S7
Contributors
Yuvch122, djb77, kylothow, Tkkg1994, Morogoku, Testers, Farovitus
Source Code: https://github.com/DeadlyMelqn/excel
Kernel Special Features: Boeffla Wakelock Blocker, Blu_Active,
Version Information
Status: Beta
Current Stable Version: 1.0.0
Stable Release Date: 2017-10-16
Current Beta Version: 1.3.0
Beta Release Date: 2017-10-16
Created 2017-10-17
Last Updated 2017-10-20
Reserved
I'm very interested in using your kernel just wondering about the battery life and thermal issues. Whenever I play games it just heats up like crazy in aosp and battery life suffers coz of inefficiency. Just wondering if you've fixed these issues.
In AOSP, those issues are not gonna dissappear but you should see a notable difference. Theres things like hero-common and such I cant fix.
Yuvch122 said:
In AOSP, those issues are not gonna dissappear but you should see a notable difference. Theres things like hero-common and such I cant fix.
Click to expand...
Click to collapse
I'll be trying out your kernel tonight
Ayy
Omg....Thermal issue has been pretty much fixed 0.0 however using stock settings did cause system shutdown when running geekbench. Needed to under clocked it significantly but it's so early so its amazing. Will use it the next couple of days and test for battery life
Alright, if you could tell me any sorta info related to the crash i can attempt to fix it
Yuvch122 said:
Alright, if you could tell me any sorta info related to the crash i can attempt to fix it
Click to expand...
Click to collapse
I'm sorry man. PC is broken and that's the only way I know how to get log files XD
Congrats on the kernel mate, keep up the good work
thanks bro
ToRRIIDeR said:
I'm sorry man. PC is broken and that's the only way I know how to get log files XD
Click to expand...
Click to collapse
Its alright, ill try recreating your scenario.
a few Misc questions
Hello,
What is typical battery life by default for the Kermit Kernel?
I'm not a gamer so don't do overclocking or highly intense graphics, for me good battery is essential, is there ways I can increase battery longevity?
Does the Kermit Kernel support fast charging by default or must it be enabled?
Does Kermit have support for VoLTE/HD voice and Wifi calling by default or can that be compiled in?
Lastly, does Kermit Kernel have support by default for the doubletap 2 wake feature (originally pioneered by the LG phones, the G2 I believe was first), or can it be compiled in?
Thanks.
Dave.
Hi,
First of great work! I'll be installing the kernel any minute now. I also wonder if it's possible to DT2W in the kernel. Have tried it myself but got lost fairly quick...
Keep up the good work!
Jules.
dt2w?
Hi,
I'd like to know how you atempted dt2w and where you got stuck?
DM me if you want.
What is the current status of kermit?
Thanks.
Dave.
It's in haitus
Phone dies for no apparent reason, usually twice a day. It's completely dead. I have to plug it in for the phone to respond and then I can turn it back on. Phone can be on 100% and be doing the easiest of tasks, and it will happen. Any help is appreciated.