Hi guys,
This is the SpeedMod kernel for the Samsung Galaxy Note GT-N7000 ICS.
This kernel is only for Samsung ICS ROMs.
This kernel has MMC_CAP_ERASE disabled, which should prevent the "hard brick" bug.
http://forum.xda-developers.com/showthread.php?t=1633943
Be extra careful if using CWM to flash stuff from another kernel. Make sure you are really on a *safe* kernel before using CWM to wipe/restore.
Disclaimer: USE IT AT YOUR OWN RISK OF PERMANENTLY BRICKING YOUR PHONE.
SpeedMod's core features are:
- Super stable: No undervolting, overclocking or potentially unstable modifications
- Fast and smooth: Compiler and code optimizations
- Excellent battery life: Remove unecessary logging and debugging
>>> CLICK HERE for more info and the DOWNLOAD links.
>>> CLICK HERE for the Frequently Asked Questions list.
Current features:
Root and CWM:
- Automatically installs root (su) but can be disabled
- Includes CWM Recovery
Screen and misc tweaks:
- MDNIE screen sharpness tuning (improves text readability)
- MDNIE color tuning (reduces over-saturation of color)
- init.d, TUN, CIFS, IPV6 Privacy support
Performance:
- CPU governor tweaks: increase responsiveness
- IO tweaks
- Read ahead tweaks
- Compiled with optimizations using Linaro GCC toolchain
- Switched to SLAB instead of SLUB
- Optimized GPU DVFS
- Optimized CPU hotplug
- ARM CPU topology support
- SCHED_MC multi-core aware scheduler
Turned off unnecessary logging for better smoothness and efficiency:
- Disabled Android Debug Logger / logcat
- Disabled Samsung debug
- Disabled various kernel debugging, statistics and tracing options
>>> CLICK HERE for the CHANGELOG.
Instructions on how to enable logcat and disable auto-root are in the 3rd post (below).
>>> CLICK HERE for more info and the DOWNLOAD links.
Reserved for source code patches.
Here is how to change some of the kernel configurations:
[HOW TO ENABLE LOGCAT]
If you are a developer or want to re-enable logcat for whatever reason, do this:
adb shell
su
mount -o remount,rw /system
echo ANDROIDLOGGER >> /system/etc/tweaks.conf
mount -o remount,ro /system
[HOW TO DISABLE AUTO-ROOT]
Create a file called ".noautoroot" in either /system or /data. This will disable the auto root installation. This example, shows how to remove root completely:
adb root
adb shell
mount -o remount,rw /system
rm /system/xbin/su
rm /system/app/Superuser.apk
rm /data/app/Superuser.apk
touch /system/.noautoroot
mount -o remount,ro /system
sync
reboot
[HOW TO RE-ENABLE AUTO-ROOT]
adb root
adb shell
mount -o remount,rw /system
rm /system/.noautoroot
mount -o remount,ro /system
sync
reboot
Hi hardcore
really thanks for your work
this is only for stock rom? work in aosp rom like CM9?
thanks
thanks for the new Kernel
but which way to flash?
flash via CMW or Mobile Odin, or even with both methods?
thanks for answer in advance
hara74 said:
thanks for the new Kernel
but which way to flash?
flash via CMW or Mobile Odin, or even with both methods?
thanks for answer in advance
Click to expand...
Click to collapse
I am only uploading the Odin tar version for now. Due to the hard brick bug being related to CWM wipes, I recommend using Odin (PC).
hara74 said:
thanks for the new Kernel
but which way to flash?
flash via CMW or Mobile Odin, or even with both methods?
thanks for answer in advance
Click to expand...
Click to collapse
Odin dude. It's a .tar file
Gesendet von meinem GT-N7000 mit Tapatalk 2
hardcore said:
..... This kernel has MMC_CAP_ERASE disabled, which should prevent the "hard brick" bug.....
Click to expand...
Click to collapse
This sounds great. Can't wait for feedback.
Sent from my Samsung Galaxy Note using XDA Premium App
thanks for the quick answers!!!
but can I use Mobil Odin, or is it not recommended,
because I always try to flash Kernels this way.
with Odin-PC I have no experience, but if is the only way, if have to READ again
hara74 said:
thanks for the quick answers!!!
but can I use Mobil Odin, or is it not recommended,
because I always try to flash Kernels this way.
with Odin-PC I have no experience, but if is the only way, if have to READ again
Click to expand...
Click to collapse
U can flash it via Pc Odin or Mobile Odin. It dosen't matter, cause its the "same".
Gesendet von meinem GT-N7000 mit Tapatalk 2
hara74 said:
thanks for the quick answers!!!
but can I use Mobil Odin, or is it not recommended,
because I always try to flash Kernels this way.
with Odin-PC I have no experience, but if is the only way, if have to READ again
Click to expand...
Click to collapse
Just flashed via Mobile Odin, no problem. Will observe for stability until tomorrow.
Im on LPF stock, no CWM since before.
Zapped through server hops to XDA forums
n3tcod3 said:
U can flash it via Pc Odin or Mobile Odin. It dosen't matter, cause its the "same".
Gesendet von meinem GT-N7000 mit Tapatalk 2
Click to expand...
Click to collapse
its not the same...when you flash with PC Odin you will get yellow triangle
custom bootanimation support please
eybee1970 said:
its not the same...when you flash with PC Odin you will get yellow triangle
Click to expand...
Click to collapse
that's why I've written it in quotation marks. But u can remove the triangle.
Gesendet von meinem GT-N7000 mit Tapatalk 2
Huuuuuuuuurrrrrrrrrrrrrrrayyyyyyyyyyyyyy !!
Now somebody please wipe data 50 times please.
(And if you superbrick)
The whole community will remember your sacrifice.
My gratitudes in advance.
now we just need a few brave souls to wipe from recovery with this kernel
jokes aside, I'm really excited that solutions are being developed but I'm waiting for things to unfold a bit more
so yeah don't be tempted to actually wipe from recovery unless you have a note to spare.
Boy124 said:
Huuuuuuuuurrrrrrrrrrrrrrrayyyyyyyyyyyyyy !!
Now somebody please wipe data 50 times please.
(And if you superbrick)
The whole community will remember your sacrifice.
My gratitudes in advance.
Click to expand...
Click to collapse
1+
Its so smoother thsn franco kernel
great work hardcore
Hey, lets get the guys who (sort of) recovered from the brick here to test it out , they can always try their fix again if something goes wrong:
http://forum.xda-developers.com/showthread.php?t=1667886
how can we make sure that it doesn't have this bug other then wiping 1000000000 times??
Related
hi can some one tell me how to Enable JIT on my Optimus One.
I need a very simple guid.
Thy.
imapjonny said:
hi can some one tell me how to Enable JIT on my Optimus One.
I need a very simple guid.
Thy.
Click to expand...
Click to collapse
Root your phone
Install custom recovery
Download flashable zip that enables JIT
flash it
kite86 said:
Root your phone
Install custom recovery
Download flashable zip that enables JIT
flash it
Click to expand...
Click to collapse
I'm pretty sure that he wants a easy and detailed guide.
Domenic.
1. Does Z4Root work on this work?
2. What is a good custom recovery to use? does cwm work?
imapjonny said:
hi can some one tell me how to Enable JIT on my Optimus One.
I need a very simple guid.
Thy.
Click to expand...
Click to collapse
Once you've got the custom recovery on it's easy. Copy the jit enabling zip file to the root of your sdcard, reboot into recovery and choose flash zip from the recovery menu.
yes z4root is working!
I need a giud how to install custom recovery to
imapjonny said:
I need a giud how to install custom recovery to
Click to expand...
Click to collapse
http://androidforums.com/getitnowma...ry-optimus-one-p500-thunderg.html#post1896517
To use copy flash_image and recovery-RA-GNM-thunderg-1.1.0.img to the root of your sdcard.
To flash: via adb shell or terminal type this from root # shell
Code:
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
# cat /sdcard/flash_image > /system/bin/flash_image
# chmod 755 /system/bin/flash_image
# mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock1 /system
# flash_image recovery /sdcard/recovery-RA-GNM-thunderg-1.1.0.img
# reboot recovery
Key combo to boot custom recovery from powered off is vol_down + home + power and release keys at LG splash.
Click to expand...
Click to collapse
I m realy new in this scene
what is adb shell and where can i get it ?
imapjonny said:
I m realy new in this scene
what is adb shell and where can i get it ?
Click to expand...
Click to collapse
You can download Android SDK - this shell is part of this development tool
imapjonny said:
I m realy new in this scene
what is adb shell and where can i get it ?
Click to expand...
Click to collapse
Or root and get terminal app.
Either way, I tweaked mine for a vm.heapsize of 48mb.
JIT sure is handy but what about GPU accel?
I have flashed with jit zip.
I test the phone before,
with linpack,average result 3.5M
After flash with jit,actual result 7.8M
During the normale use i don't see evident boost performarce,
but for me is a good update.
Bye.
Sorry, but I thought Android 2.2 had the JIT compiler built in? It's turned off on the Optimus T?
This is my wife's phone, and in general it has good performance. But Angry Birds runs a slow on some of the screens. I was wondering if enabling the JIT compiler might help.
BTW, I've rooted the phone already to modify the SMS send limits.
Froyo normaly make active jit,
but on O1 this feature is not active by default.
If you have rooted the phone,install the recovery menu and flash with jit zip.
greno1 said:
But Angry Birds runs a slow on some of the screens. I was wondering if enabling the JIT compiler might help.
Click to expand...
Click to collapse
No that does not help, I have tested that. Removing the ads with adfree android seems to help a little bit, but generally the phones cpu has not enough power for angry birds.
The Angry Birds developers are working in a lower spec version that will run on 600mhz Arm6 processors more smoothly.
Just in case, figured someone would want it at some point.
dl-dropbox-com/u/13427114/signed_thunderc_thungerg_jit_disable.zip
(add http and replace - for dots)
Noejn said:
Just in case, figured someone would want it at some point.
dl-dropbox-com/u/13427114/signed_thunderc_thungerg_jit_disable.zip
(add http and replace - for dots)
Click to expand...
Click to collapse
you can also delete /data/local.prop and reboot too.
Or, flash this one which will not only enable JIT and change the vm.heapsize to 48mb but also enable hardware acceleration. Homescreen should be snappier.
dl"dot"dropbox"dot"com/u/13427114/mone/o1_jit-hwacc_enabler.zip
(add http and replace "dot" for .)
how should i install this? (Searched over the net and couldn't find how to install)
Will this increase my gaming and mobile performance ??
I have lg official 2.3.3 Rom, With franco kernel and also have SetCpu installed.
globeent1980 said:
how should i install this? (Searched over the net and couldn't find how to install)
Will this increase my gaming and mobile performance ??
I have lg official 2.3.3 Rom, With franco kernel and also have SetCpu installed.
Click to expand...
Click to collapse
Its enabled by default
Sent from my LG-P500
Team Win Recovery Project 2.3, 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.3.1.0:
-Unmount system after boot to prevent some status 7 symlink failed errors on zip install
-USB Mass Storage code improvements
-Better handling of mounting storage during boot for some devices
-Fixed a problem with sizes of images (boot & recovery) after resetting defaults
-Fixed size errors during backup for some devices on recovery, etc.
-Fixed a problem with restoring backups when multiple archives were present
CHANGELOG for 2.3.0.0:
-Rebased onto AOSP Jelly Bean source code
-Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
-ADB sideload functionality from AOSP is included in 2.3, see this link for more info
-Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
-Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
-Faster boot times
-Added charging indicator while in recovery (only updates once every 60 seconds)
While this update may not bring a host of new must-have features, this update is a significant re-write of much of the core TWRP code. AOSP Jelly Bean recovery source moved to mostly C++ code and now all of the "TWRP" code is fully rewritten into C++ as well. Now that we've laid this groundwork, we're in a much better position to pull in future AOSP recovery updates as well as implementing more great new features.
Since TWRP 2.3 is based on AOSP jelly bean sources, TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder.
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app
For downloads and instructions please visit our TWRP website and choose your device in the dropdown menu
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 30 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.
ReverendJKR posted a great video on TWRP and Goo Manager working together.. Much more to come with this relationship
http://youtu.be/OA0S275XO3U
Oh man. Awesome!
Looks nice...looking forward to trying it out.
This looks very slick!
Sent from space
Can this recovery be used on any phone/tablet?
Sent from my Desire HD using xda premium
Super cool, thanks guys, I am now into Nook Color... HD2, AMAZE 4G...
Jainyankee1993 said:
Can this recovery be used on any phone/tablet?
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
We have a list of supported devices on the main twrp2 page: http://teamw.in/project/twrp2
So I see you got that stuck in recovery bug all worked out ehh? nice work.
eyeballer said:
TeamWin is proud to present TWRP 2.0 for Nook Color!!
Click to expand...
Click to collapse
Congrats TeamWin... this is supercool.
eyeballer one of the install steps is to push "kernel" to uRecImg but there is none? Am I missing something obvious?
hm, anyway to install this on an existing install?
Midnitte said:
hm, anyway to install this on an existing install?
Click to expand...
Click to collapse
Right from their page? Though idk what kernel they are talking about.
Download the above file. Connect your Nook Color to the PC via the USB cable. This assumes you have working ADB.
Execute the following:
adb shell busybox remount / -o rw,remount
adb shell busbbox mkdir /boot
adb shell busybox mount /dev/block/mmcblk0p1 /boot
adb push twrp-encore-2.0.0RC0.ub /boot/uRecRam <--- You can change uRecRam to uAltRam for alternate boot.
adb push kernel /boot/uRecImg
adb shell busybox umount /boot
Click to expand...
Click to collapse
RileyGrant said:
eyeballer one of the install steps is to push "kernel" to uRecImg but there is none? Am I missing something obvious?
Click to expand...
Click to collapse
Nburnes said:
Right from their page? Though idk what kernel they are talking about.
Click to expand...
Click to collapse
Sorry guys, the page is updated now with the kernel link. However, we just use a stock AOSP kernel so if you had CWM on emmc already you don't need to push the kernel since it's the same.
eyeballer said:
Sorry guys, the page is updated now with the kernel link. However, we just use a stock AOSP kernel so if you had CWM on emmc already you don't need to push the kernel since it's the same.
Click to expand...
Click to collapse
Actually what I thought, thanks for clarifying man .
Oooh, i look forward to trying this.
I was not having success installing this on emmc with the adb instructions probably because busybox was not set up the same way.
So I tried an different approach which was to use the NookColor UMS app to mount the boot partition so it shows up as a USB drive on PC called boot. I then just renamed uRecRam to uRecRamOld and copied in twrp-encore-2.0.0RC0.ub and renamed that to uRecRam. I didn't bother copying the kernel as per the previous posts.
Rebooting into recovery then brought up the TWRP recovery which looks very nice to use. Also works off the power up N after emmc recovery selected as expected.
Clockwork has given me good service but I think I'll be using this going forward.
bobtidey said:
I was not having success installing this on emmc with the adb instructions probably because busybox was not set up the same way.
So I tried an different approach which was to use the NookColor UMS app to mount the boot partition so it shows up as a USB drive on PC called boot. I then just renamed uRecRam to uRecRamOld and copied in twrp-encore-2.0.0RC0.ub and renamed that to uRecRam. I didn't bother copying the kernel as per the previous posts.
Rebooting into recovery then brought up the TWRP recovery which looks very nice to use. Also works off the power up N after emmc recovery selected as expected.
Clockwork has given me good service but I think I'll be using this going forward.
Click to expand...
Click to collapse
I had to do the same thing. Kept getting an error that "applet not found" for busybox in adb.
Thanks for the alternate method.
This is a much better implementation of our hardware in backup.
Thanks TeamWin.
Nburnes said:
Right from their page? Though idk what kernel they are talking about.
Click to expand...
Click to collapse
It wasn't there before! I swear! /thanks
Hm, is usb storage working for anyone?
The only thing I don't really care for is... and I know I am doing things in a unique way....
I have SASD with CM7 on it... verygreen's recovery as alt-boot and replaced CWM with TWRP as recovery mode on the uSD... when in TWRP and reboot... it boots stock on eMMC instead of a normal boot... it should do a normal boot (uSD first)
KERNEL IS ONLY FOR KUMQUAT. XDA DEVDB SHOWS SOLA ALSO FOR P,U AND GO ! DO NOT CROSSFLASH
Hello.
As we (me and Gava97) built succesfully SlimKat 4.4.2 (we will share it in the next hours) , i would like to share the kernel included in the out folder.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
The kernel contains Team Win Recovery Project but i am not sure that it will work.
Link
1st boot image :- http://d-h.st/uB7
Warning
We'll try to keep this project up with slimkat nightlies but if we see that it's too difficult,we will leave
Flash
Install fastboot drivers
Open flashtool
Flash icon > fastboot mode
Select kernel to flash
Choose dir where you downloaded boot.img
Connect phone in fastboot mode (hold vol up + connecting usb cable)
Choose "Open"
Wait kernel flashes
Boot in cwm (When [IF] showing sony logo,press volume down button continously)
Report us !
Credits
munjeni
New Maclaw
XDA:DevDB Information
[RECOVERY] Team Win Recovery Project [ALPHA], a Kernel for the Sony Xperia Sola
Contributors
DroidModderXtreme, Gava97
Kernel Special Features: TWRP KERNEL
Version Information
Status: Testing
Created 2014-02-19
Last Updated 2014-02-18
DroidModderXtreme said:
XDAevDB Information
[RECOVERY] Team Win Recovery Project [ALPHA], a Kernel for the Sony Xperia Sola
Click to expand...
Click to collapse
Sorry i am not trying to be a troll but this is not for xperia u?!?!?!
@ribben xda shows xsola also for xu,p and go
Tried, but can't access recovery.Stuck on boot logo ( not boot animation).
Sent from XU powered by KitKat.
PuiuMarius2000 said:
Tried, but can't access recovery.Stuck on boot logo ( not boot animation).
Sent from XU powered by KitKat.
Click to expand...
Click to collapse
Thanks for report
Sent from my GT-I9300 using xda app-developers app
DroidModderXtreme said:
Thanks for report
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
the kernel basically works, you can use the device normally. but when trying to access to recovery occurs the bug that @PuiuMarius2000 has said.
Sent from my Xperia U using Tapatalk
What can you say about 3.4 kernel?
I'm not asking for eta, I'm just curious and I want to know if there are problems or not (as I hope)
Thanks
Inviato dal mio Xperia U utilizzando Tapatalk
@alematt we will work on it when slimkat and slimbean will be ready for daily usage
Here you guys go- http://d-h.st/7Ln
This will boot directly in recovery instead of normal booting. If someone just wants to get a taste, you can flash it. Touch is buggy/not-working and this won't boot into system. I know exactly how to fix that but my internet speed is capped. So it'll take sometime for me to fix it but I'm sure of getting this work
Cheers,
AJ
Abhinav2 said:
Here you guys go- http://d-h.st/7Ln
This will boot directly in recovery instead of normal booting. If someone just wants to get a taste, you can flash it. Touch is buggy/not-working and this won't boot into system. I know exactly how to fix that but my internet speed is capped. So it'll take sometime for me to fix it but I'm sure of getting this work
Cheers,
AJ
Click to expand...
Click to collapse
works but must repeatedly pressing the touch menús to access them.
PD: and sometimes this take owned by itself and enter to menu backups jeje
Kobalto07 said:
works but must repeatedly pressing the touch menús to access them.
PD: and sometimes this take owned by itself and enter to menu backups jeje
Click to expand...
Click to collapse
Yes this problem with touch also happens in XGo, XP(don't know about xsola, never tried for it but it will be in it.) But its secondary problem. First thing should be getting this booted correctly. I've made a build which will most probably boot in recovery and normally but I need someone to PM me if they want to try since this could be dangerous. If someone wants PM me but I shouldn't be blamed if something goes wrong. Know how to fix your device.
Cheers,
AJ
Here it is(tested and working)- d-h.st/p2b
It will boot perfectly boot into system.
Will also boot in recovery when power button is pressed.
Added both vibration and led to indicate when power button has to be pressed(LED not tested)
Touch is a complete mess don't complain about it I know about that.
Completely changed the ramdisk structure to make it boot. The original ramdisk has been shrinked to lowest possible size(and recovery has been removed from it instead is triggered differently) and both the original recovery and recovery-ramdisk have been triggered separately with a init script to control the boot and all of that is then packed as the master recovery.
Cleaner way and easier to change recoveries with it. Just replace ramdisk-recovery.cpio with any of your recovery in the same format from any kernel to do so.
Somethings I would appreciate if users can do-
Give the logs in /cache/recovery/
Since touch event logging is not yet enabled yet(I'll enable it later in the source) so I think it'll be hard to fix it for now but I'll do my best.
Check if ADB works in recovery. -> OK not working. Will check it.
If you could help me solve the bugs with touch in any way it'll be nice
Thanks everyone.
Cheers,
AJ
Abhinav2 said:
Here it is(tested and working)- d-h.st/p2b
It will boot perfectly boot into system.
Will also boot in recovery when power button is pressed.
Added both vibration and led to indicate when power button has to be pressed(LED not tested)
Touch is a complete mess don't complain about it I know about that.
Completely changed the ramdisk structure to make it boot. The original ramdisk has been shrinked to lowest possible size(and recovery has been removed from it instead is triggered differently) and both the original recovery and recovery-ramdisk have been triggered separately with a init script to control the boot and all of that is then packed as the master recovery.
Cleaner way and easier to change recoveries with it. Just replace ramdisk-recovery.cpio with any of your recovery in the same format from any kernel to do so.
Somethings I would appreciate if users can do-
Give the logs in /cache/recovery/
Since touch event logging is not yet enabled yet(I'll enable it later in the source) so I think it'll be hard to fix it for now but I'll do my best.
Check if ADB works in recovery. -> OK not working. Will check it.
If you could help me solve the bugs with touch in any way it'll be nice
Thanks everyone.
Cheers,
AJ
Click to expand...
Click to collapse
can i test on slimkat?
Matoxxi said:
can i test on slimkat?
Click to expand...
Click to collapse
It should
Cheers,
AJ
Abhinav2 said:
It should
Cheers,
AJ
Click to expand...
Click to collapse
the device starts well :good: ,and goes well in recovery, but it is a problem that goes by itself to backup menu ( must repeatedly pressing the touch menús to access them too)
Kobalto07 said:
the device starts well :good: ,and goes well in recovery, but it is a problem that goes by itself to backup menu ( must repeatedly pressing the touch menús to access them too)
Click to expand...
Click to collapse
I said I'll work on it And actually it doesn't goes into backup menu but if you observe it closely it keeps on touching the center part of the screen. So it is to be fixed
Cheers,
AJ
@Abhinav2 hit me if you need any sort of help
recovery.log from xperia go
here are recovery.log taken from xperia go twrp (compiled by me). hope it could help
wan5xp said:
here are recovery.log taken from xperia go twrp (compiled by me). hope it could help
Click to expand...
Click to collapse
wan5xp said:
Does anyone have any idea which partition is fotakernel partition?
Click to expand...
Click to collapse
Thanks for log. I'm glad to see that you added touch logging event flag. I had such log from my XP. I'll try to debug it Also I think you are trying the elf extract method the one with FOTA partition. Most probably because your kernel isn't booting to recovery if I'm not wrong. I can help you with that if not already solved. I have the boorec-device and basic structure for kernel ready. Just use the kernel I shared for Xperia U with XGo. Extract the ramdisk and got recovery ramdisk from sbin of your compiled kernel. Extract my kernel and replace ramdisk-recovery.cpio with the one from your kernel(it'll be in gz format. Just extract it to cpio and rename accordingly). Next you can edit bootrec from ramdisk in sbin folder and remove the vibration triggering lines and recovery extracting since I added already in init script and both normal ramdisk and recovery ramdisk will work separately. The lines would look something like this-
Code:
# trigger vibration
echo '200' > /sys/class/timed_output/vibrator/enable
# disable button-backlight
echo '0' > /sys/devices/platform/nmk-i2c.2/i2c-2/2-0040/leds/button-backlight/brightness
# disable LEDs
echo '0' > /sys/devices/platform/nmk-i2c.2/i2c-2/2-0040/leds/red/brightness
echo '0' > /sys/devices/platform/nmk-i2c.2/i2c-2/2-0040/leds/green/brightness
echo '0' > /sys/devices/platform/nmk-i2c.2/i2c-2/2-0040/leds/blue/brightness
cat /dev/input/event2 > /dev/keycheck &
sleep 3
kill -9 $!
if [ -s /dev/keycheck -o -e /cache/recovery/boot ]
then
rm -r /cache/recovery/boot
stop ta_rmt_service
stop rmt_storage
stop tad
stop cspsa
mount -o remount,rw rootfs /
umount -l /system
umount -l /data
umount -l /cache
umount -l /storage
rm -r *.rc
rm -r /etc
rm -r /tmp
mkdir /etc
mkdir /tmp
cd / && gunzip < /sbin/recovery_ramdisk.gz | cpio -i -d
chroot / /init
fi
Optional step for slimming the kernel- Also you can remove recovery_ramdisk.gz from sbin and recovery binary. Then you must also remove everything symlinking to it directly or indirectly as it'll all become useless. If you want I can do that stuff for u
Cheers,
AJ
Do you mind to share your device tree?
[kernel][v3.5] leanKernel: minimalistic kernel (1/28/16)
leanKernel is not for everyone.
My philosophy is to keep the kernel footprint as small as possible by trimming as much fat as possible, and at the same time keeping it stable, power efficient, and fast. leanKernel is designed to be a drop in replacement for stock kernel, and so it tries not to deviate too far from stock.
You will find that it's lacking some of the bells and whistles of other custom kernels, so if you like features you came to the wrong thread.
Here's a longer post on what leanKernel is about.
Also folks, please read the FAQ before asking questions.
INSTRUCTIONS
If you like to stay as close to stock as possible: 1) Download and flash the normal leanKernel build here (find the latest zip file) in recovery. 2) Reboot and enjoy better performance and battery life (hopefully). That's it! There's no need to flash stock kernel first, or to wipe caches.
If you like to customize, read through the feature list below, the FAQ (post #2), the changelogs, and optionally the entire thread. Then you'll know what to do.
DOWNLOAD (flash in recovery)
v1.x is for Android 5.0, and v2.x is for Android 5.1
main download
mirror (may need to refresh browser to see latest)
PREREQUISITE
Unlocked bootloader, custom recovery installed
Push bullet channel: imoseyon
FEATURES
custom voltage control - use your favorite app
updated to latest 3.10 Linux
interactiveX - screen_off_maxfreq support (default 2.2Ghz)
sw crypto drivers updated (to use arm NEON instructions) for better encryption/decryption performance. Sequential 180MB/s reads, 60MB/s writes (using dd)
latest Linaro gcc 4.9 toolchain (optimized for a15 - thanks to Christopher83)
fat trimmed and various performance tweaks
f2fs support (updated to latest source from Samsung)
force encryption turned off (changed to encryptable)
overclocked to 2.9ghz (experimental - available as a separate build for now)
underclocked to 223mhz (experimental - available as a separate build for now)
Async Fsync
init.d support
cpu-boost control - enable/disable via lkconfig
lkconfig script for customizing leankernel (open terminal app, become superuser, then type "lkconfig" without quotes)
patched mpdecision to prevent changing min/max freq provided as flashable zip (in util directory)
color control (thanks to @savoca)
charging led support
a lot of unnecessary stuff removed from stock kernel
some components updated to Linux 3.18
random generation optimization including e/frandom support
pc/usb charging with boosted current ~300-400mA
some selinux fixes, selinux is enforced by default - staying true to stock (you can easily disable using lkconfig)
SLUB allocator updated to Linux 3.18
wake gesture control from flar2, modified for leankernel (also disabled in-call)
vibe strength control
much of the code is up to date with latest from CodeAurora
(mostly for devs) /sys/module/selinux/parameters/force_audit sysfs node to audit all/hidden selinux denies.
power aware cpu scheduling
faux sound enable/disable by sysfs (and lkconfig)
wakelock control (smb135x, wlan_rx, msm_hsic and sensor_ind)
leanKernel core control script
user option to prevent mpdecision/msm_thermal from changing min/max frequencies: frequency mitigation preventer
supports kexec for multirom
LKCONFIG
You can use lkconfig script to make custom changes to leanKernel (along with popular apps like Kernel Tweaker and Trickstermod). To run lkconfig, open terminal app, "su" (without quotes) to become superuser, enter, and then type "lkconfig" without quotes, then enter.
Code:
[email protected]:/ $ su
[email protected]:/ # lk
leanKernel configurator
---
0) display current settings
1) cpu frequency control
2) wake gesture control
3) wakelock control
4) charging led
5) rgb/picture control (advanced)
6) rgb/picture control (simple)
7) vibe strength
8) power saving mode for cpu scheduler
9) faux sound control
10) selinux mode
11) min/max freq change prevention
21) check top 10 wake locks (ie. wakeup sources)
please enter a number (or press enter to exit):
CHANGELOG
https://github.com/imoseyon/leanKernel-shamu/wiki/Marshmallow-ChangeLog
Thanks to @guitarshredder87, @Wera750, @akellar, and @grisha1 for testing test builds!
XDA:DevDB Information
Leankernel: Minimalistic Kernel, Kernel for the Nexus 6
Contributors
Imoseyon
Source Code: https://github.com/imoseyon/leanKernel-shamu
Kernel Special Features:
Version Information
Status: Stable
Created 2014-11-26
Last Updated 2016-01-31
FAQ
I'm having trouble waking the phone sometimes. Help!
We haven't really figured out exactly what's causing it - but there seems to be evidence that it's not limited just to leanKernel. One thing to try: if your ROM has a feature that prevents accidental wakeups, disable it!
I can't seem to get min and max freq to stick! What are these mpdecision zip files in the util directory?
* Read this post: http://forum.xda-developers.com/showpost.php?p=58135730&postcount=1474
* Short version: This is actually by design of mpdecision. If you want this behavior to change, I recommend that you 1) flash latest stable leankernel, 2) flash the custom no-freq mpdecision, and then 3) disable cpu-boost via lkconfig. Do not disable mpdecision if you go this route. Also, if you flash ROM, you must re-flash custom mpdecision. To go back to normal, flash the stock mpdecision file.. Launch lkconfig, choose core control, and choose one of the options in core control.
Will flashing leankernel decrypt my phone storage?
If you're already encrypted, then it will stay encrypted after flashing kernel, *until* you format data. Once you format you will stay decrypted until you decide to encrypt again (see below). If you're already decrypted, leanKernel will not force encrypt automatically.
What do I do to encrypt again?
There are several ways to do this. One way (easiest for me at least) is to adb in (or in terminal emulator):
Code:
[email protected]:/ # start encrypt
You will see the phone hot boot and once it comes up you will be encrypted again. Keep in mind that if you want to decrypt again you'll have to wipe.
How do I check the PVS BIN of my cpu?
Code:
[email protected]:/ # cat /proc/cpu/msm_acpu_pvs
The number you get should range between 0 and 15 (inclusive). If you ended up with 15 congratulations. If you ended up with 0, go get it exchanged! Stock frequency/voltage table: http://pastebin.com/ZyGA9Tec
Which kernel control app do you recommend?
When v1.0 gets released it should come with "lkconfig" for tweaking some of the options. Otherwise, I tried Trickster and KernelTweaker, and they both seem to work ok.
What are ondemandX and interactiveX?
ondemandX and interactiveX are very very close to "stock" ondemand and interactive governors, respectively. The only difference is screen_off_maxfreq sysfs support. This means that it gives you the ability to limit phone's max frequency when screen is off. This feature could be effective in reducing battery usage, especially if you have a misbehaving app (or two) that consume cpu cycles while screen is off. The default value is 2265600 - if you change the value to your top speed you're effectively disabling the feature and restoring stock behavior completely. You can use an app like Trickster or Kernel Tweaker to modify screen_off_maxfreq.
HELP! I messed up with lkconfig - how do I go back?
Do not fret. Flash lkconfig_cleaner.zip from the "util" directory.
(If you want to do this manually), reboot the phone into recovery, mount /data, and delete everything in /data/data/leankernel. Once things are back to normal, re-run lkconfig to re-do your settings.
What is cpu-boost?
Read this post: http://forum.xda-developers.com/showpost.php?p=57215289&postcount=535
What is the best RGB setting?
http://forum.xda-developers.com/showpost.php?p=57265483&postcount=620 (old)
http://forum.xda-developers.com/showpost.php?p=59092146&postcount=3017 (new)
What is power aware scheduling?
Read this post: http://forum.xda-developers.com/showpost.php?p=58313978&postcount=1651
I missed your kernel when I switched to N5. Glad to have you here
hmm.. a kernel. since its the first one posted here, im trying it out
Hell yeah. Ready to flash
Sent from my AOSP on Shamu using XDA Free mobile app
If I flash this it will decrypt right cool
digweed4me said:
If I flash this it will decrypt right cool
Click to expand...
Click to collapse
It should not decrypt if you're already encrypted, unless you re-format/wipe. But no guarantees.
Imoseyon said:
It should not decrypt if you're already encrypted, unless you re-format/wipe. But no guarantees.
Click to expand...
Click to collapse
What app should we use to control? I remember you used to have your app right
holy **** Imoseyon. you made my Thunderbolt usable way back when. so glad to see you developing for the N6 now
digweed4me said:
What app should we use to control? I remember you used to have your app right
Click to expand...
Click to collapse
Flashed it and yes decrypted thanks a lot
IMO!! Good to see ya again man. Can't wait to run your work again.
Appreciate it!
digweed4me said:
What app should we use to control? I remember you used to have your app right
Click to expand...
Click to collapse
You mean lkconfig? Yeah that's coming later (along with a whole lot more).. If you're talking about f2fs, you'd want to use custom recovery but TWRP for shamu doesn't support f2fs yet - i had to do everything manually.
Imoseyon said:
It should not decrypt if you're already encrypted, unless you re-format/wipe. But no guarantees.
Click to expand...
Click to collapse
i am still encrypted, and did not decrypt after flashing. so, all worked as it should.
Can we flash on stock ROM or is a custom ROM required?
So let me see if I get this straight: I'm on stock, unlocked bootloader, rooted, and encrypted (as far as I know--I never decrypted), so if I flash this it won't decrypt my device? I was kinda hoping it would.
Secondly, I'm good to flash this with stock ROM? I'm hoping for a bit better battery life.
Thanks devs! I got a feeling development for our device is gonna be NUTS!!
You don't buy a Mustang for the gas mileage.
nycdiplomat said:
Can we flash on stock ROM or is a custom ROM required?
Click to expand...
Click to collapse
I'm on a stock ROM.
pathtologos said:
So let me see if I get this straight: I'm on stock, unlocked bootloader, rooted, and encrypted (as far as I know--I never decrypted), so if I flash this it won't decrypt my device? I was kinda hoping it would.
Secondly, I'm good to flash this with stock ROM? I'm hoping for a bit better battery life.
Thanks devs! I got a feeling development for our device is gonna be NUTS!!
You don't buy a Mustang for the gas mileage.
Click to expand...
Click to collapse
wipe before flashing, youll be decrypted. if you dont wipe, you stay encrpted.
pathtologos said:
So let me see if I get this straight: I'm on stock, unlocked bootloader, rooted, and encrypted (as far as I know--I never decrypted), so if I flash this it won't decrypt my device? I was kinda hoping it would.
Secondly, I'm good to flash this with stock ROM? I'm hoping for a bit better battery life.
Thanks devs! I got a feeling development for our device is gonna be NUTS!!
You don't buy a Mustang for the gas mileage.
Click to expand...
Click to collapse
AFAIK, there's no way to decrypt without having to wipe unfortunately. Going the other way (unencrypted to encrypted) is super easy though, and no data loss.
nycdiplomat said:
Can we flash on stock ROM or is a custom ROM required?
Click to expand...
Click to collapse
im on rastapop, an aosp based custom rom.
simms22 said:
wipe before flashing, youll be decrypted. if you dont wipe, you stay encrpted.
Click to expand...
Click to collapse
Thanks for your quick response. Wipe what tho? Cache, dalvik, and what else? Hope you don't mean all my data.
You don't buy a Mustang for the gas mileage.
CM11 M for d605
it is based on Varcain kernel and device tree, much thanks for your work and releasing source code!
Just woke up from my slumber, because I realized, that my domain expired and links get broken.
Sorry, but nothing new, only links fix
Kernel
what is new:
More free ram, over 35MB
Screenshot: http://forum.xda-developers.com/attachment.php?attachmentid=3146159&d=1422877546
Added new cpu governor - Interactive, default scheduler is noop
Kernel modules for zRam, usb storage, gamepads, and others
Support for USB-OTG with external charger, based on ziddey's work for Mako
Source: http://forum.xda-developers.com/nexus-4/orig-development/usb-otg-externally-powered-usb-otg-t2181820
Fixed offline charging
zRam control
what is that:
Very simple app, setup zram by yourself and watch stats. zRam settings won't survive reboot!
After creation zram device, for short time, one value in stats is temporally broken because no data .
Screenshot: http://forum.xda-developers.com/attachment.php?attachmentid=3146160&d=1422877546
Framework
patched framework and settings for usb flashdisk
few UI colors changes
Install
Wipe data and cache. Then just flash archive in recovery.
Download: http://46.28.109.28/cm.zip
Source
Somehow stable source code is on my github, PM me for questions.
https://github.com/puresoul
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU Affero General Public License for more details.
OTG will work only with external charger. So you need something like that.
shall I wipe something after installation? if something goes wrong, will cmw recovery start anyway(i've installed v3 today)?
You may wipe cache and dalvik cache, but it is not needed to wipe something. Nope, installation process will not touch recovery partition.
cescom said:
shall I wipe something after installation? if something goes wrong, will cmw recovery start anyway(i've installed v3 today)?
Click to expand...
Click to collapse
Puresoul_CZ said:
You may wipe cache and dalvik cache, but it is not needed to wipe something. Nope, installation process will not touch recovery partition.
Click to expand...
Click to collapse
It works perfectly also without any wipe (i was too happy to try this that i forgot to wipe), thanks! :fingers-crossed:
No problem, thanks.
Puresoul_CZ said:
No problem, thanks.
Click to expand...
Click to collapse
Great work for RAM:good:, but i've gone to the gallery and sdcard is not recognised anymore
I have the same problem. Where I can find zRam settings?
Could you include rtl8192cu driver with your build?
edit: everything is now bundled together as a whole rom.
dundee81 said:
I have the same problem. Where I can find zRam settings?
Click to expand...
Click to collapse
Ok, thx What about mounting sdcard?
please send me dmesg log
immediately after reboot type in terminal, su; dmesg > /cache/dmesg.log
and send me that file
Thanks
Puresoul_CZ said:
please send me dmesg log
immediately after reboot type in terminal, su; dmesg > /cache/dmesg.log
and send me that file
Thanks
Click to expand...
Click to collapse
where can i send it?
Using terminal emulator, shall i use adb? because terminal emulator takes a lot to start
yes, adb is way batter
cescom said:
where can i send it?
Using terminal emulator, shall i use adb? because terminal emulator takes a lot to start
Click to expand...
Click to collapse
i suspect kernel modules, but for sure need to check log.
this may be the case, i forgot to add the permision file. Update: http://frame.jailbrake.cz/boot_v2.zip
boot_v2
I don´t read sd card
Puresoul_CZ said:
this may be the case, i forgot to add the permision file. Update: http://frame.jailbrake.cz/boot_v2.zip
Click to expand...
Click to collapse
set perm:some changes failed (cwm)
did you flash boot.zip or boot_v2.zip?
sinnombrexxl said:
I don´t read sd card
Click to expand...
Click to collapse
check please file handheld_core_hardware.xml
if exists at /system/etc/permissions/handheld_core_hardware.xml
here is that file: http://frame.jailbrake.cz/hch.zip
cescom said:
set perm:some changes failed (cwm)
Click to expand...
Click to collapse