Database Develop

How do you use Compcache with linux-swap as a backup

How do you use Compcache with linux-swap as a backup? I dont understand the thread correctly that explains it I already have compcache.

You have to edit the userinit.sh file. Open it with notepad, then change the line to look like this:
insmod ramzswap.ko memlimit_kb=32000 backing_swap=/dev/block/mmcblk0p3;
then reboot, and you should be good.

blackfire1 said:
How do you use Compcache with linux-swap as a backup? I dont understand the thread correctly that explains it I already have compcache.
Click to expand...
Click to collapse
There are two ways to use an existing linux-swap as a backup to Compcache.
Let linux manage compcache and the linux-swap partition/file directly
Let compcache manage the linux-swap partition. *As of this writing, cyanogen has only included the .5 series of compcache which will not support a linux-swap file.
You need to first create the compcache swap device. I assume you are running a cyanogen kernel and you have compiled modules. Also I assume you know what your swap partition or swap file is called. e.g. A swap file looks like /system/sd/swapfile.swp, a swap partition looks like /dev/block/mmcblk0p3.
1. Linux managed:
Pros: Supports linux-swap file. Relies on established linux swapping priorities.
Cons: compcache wastes space as incompressible data remains in the compcache swap. Linux uses compcache until its full, then places everything in the backing swap.
First we enable the compcache swap device.
Code:
insmod /system/modules/lib/modules/2.6.29-cm/compcache/xvmalloc.ko; #load the compcache memory allocator
insmod /system/modules/lib/modules/2.6.29-cm/compcache/ramzswap.ko disksize_kb=24576; #create a compressed swap device with disk size 24576 kB
mknod /dev/ramzswap0 b 253 0; #initialize ramzswap0
swapon /dev/ramzswap0; #turn on compcache swap first so it has higher priority. (defaults as -1)
Next we either enable the swap file or the swap partition.
If you have a swap file then the next line is.
Code:
swapon /system/sd/swapfile.swp; #turns on second swap as priority -2, lower priority than above.
or
Code:
swapon /dev/block/mmcblk0p3; #turns on second swap as priority -2, lower priority than above.
To check to see whether it works, you will type:
cat /proc/swaps/
and see either
Code:
# cat /proc/swaps
Filename Type Size Used Priority
/dev/ramzswap0 partition 24464 6584 -1
/system/sd/swapfile.swp file 31596 0 -2
or
Code:
# cat /proc/swaps
Filename Type Size Used Priority
/dev/ramzswap0 partition 24464 6584 -1
/dev/block/mmcblk0p3 partition 31596 0 -2
2. Compcache .5.3 managed:
Pros: compcache can attempt to maximize compressed data in compcache and intelligently allocate to backing swap.
Cons: Relies on newer algorithms. Does not support swap files yet.
When cyanogen updates to compcache .6.x, you can use the swap file, until then, its just the swap partition.
Code:
insmod /system/modules/lib/modules/2.6.29-cm/compcache/xvmalloc.ko; #load the compcache memory allocator
insmod /system/modules/lib/modules/2.6.29-cm/compcache/ramzswap.ko [b]backing_swap=/dev/block/mmcblk0p3 memlimit_kb=24576; [/b] #create a compressed swap device with disk size 24576 kB #NOTE! Memlimit currently ignored in current build. Default to 14 megs (15% memory)
mknod /dev/ramzswap0 b 253 0; #initialize ramzswap0
swapon /dev/ramzswap0; #turn on compcache swap, this includes the backing swap which should be invisible to linux.
NOTE: There is no need to enable any other swaps afterward unless you want a linux managed backing swap
If you type
cat /proc/swaps/
you will see:
Code:
# cat /proc/swaps
Filename Type Size Used Priority
/dev/ramzswap0 partition 24464 6584 -1
Use
cat /proc/ramzswap
and if you don't have a backing swap you will see.
Code:
# cat /proc/ramzswap
DiskSize: 24468 kB
NumReads: 1260
NumWrites: 2042
FailedReads: 0
FailedWrites: 0
InvalidIO: 0
PagesDiscard: 0
ZeroPages: 113
GoodCompress: 74 %
NoCompress: 3 %
PagesStored: 1929
PagesUsed: 630
OrigDataSize: 7716 kB
ComprDataSize: 2482 kB
MemUsedTotal: 2520 kB
if you do, it should say
Code:
# cat /proc/ramzswap
DiskSize: 31250 kB
MemLimit: 14680 kB
NumReads: 5186
NumWrites: 9229
FailedReads: 0
FailedWrites: 0
InvalidIO: 0
PagesDiscard: 0
ZeroPages: 578
GoodCompress: 100 %
NoCompress: 0 %
PagesStored: 5313
PagesUsed: 1425
OrigDataSize: 21252 kB
ComprDataSize: 5532 kB
MemUsedTotal: 5700 kB
[b]BDevNumReads: 1185
BDevNumWrites: 2145
[/b]
3. Miscellaneous Notes:
As I typed this I realized I was pulling information from the .6.x tree and the .5.x tree. It's possible that the syntax for compcache has changed.
Also, if anyone wants to update the wiki with this, I'd appreciate it. I don't feel like formatting for the wiki right now.

Wow, excellent answer. Wiki material for sure - if no one's gotten it a little later, I'll take care of it. Gotta pretend I'm actually working awhile first.

overpower said:
2. Compcache .5.3 managed:
Pros: compcache can attempt to maximize compressed data in compcache and intelligently allocate to backing swap.
Cons: Relies on newer algorithms. Does not support swap files yet.
When cyanogen updates to compcache .6.x, you can use the swap file, until then, its just the swap partition.
Code:
insmod /system/modules/lib/modules/2.6.29-cm/compcache/xvmalloc.ko; #load the compcache memory allocator
insmod /system/modules/lib/modules/2.6.29-cm/compcache/ramzswap.ko [b]backing_swap=/dev/block/mmcblk0p3 memlimit_kb=24576; [/b] #create a compressed swap device with disk size 24576 kB #NOTE! Memlimit currently ignored in current build. Default to 14 megs (15% memory)
mknod /dev/ramzswap0 b 253 0; #initialize ramzswap0
swapon /dev/ramzswap0; #turn on compcache swap, this includes the backing swap which should be invisible to linux.
Code:
# cat /proc/ramzswap
DiskSize: 31250 kB
MemLimit: 14680 kB
NumReads: 5186
NumWrites: 9229
FailedReads: 0
FailedWrites: 0
InvalidIO: 0
PagesDiscard: 0
ZeroPages: 578
GoodCompress: 100 %
NoCompress: 0 %
PagesStored: 5313
PagesUsed: 1425
OrigDataSize: 21252 kB
ComprDataSize: 5532 kB
MemUsedTotal: 5700 kB
[b]BDevNumReads: 1185
BDevNumWrites: 2145
[/b]
3. Miscellaneous Notes:
As I typed this I realized I was pulling information from the .6.x tree and the .5.x tree. It's possible that the syntax for compcache has changed.
Also, if anyone wants to update the wiki with this, I'd appreciate it. I don't feel like formatting for the wiki right now.
Click to expand...
Click to collapse
I don't see adding memlimit_kb=24576 after backing_swap=/dev/block/mmcblk0p3 having any effect-- as you see, it is still limiting the size to 15% of the physical RAM.

Compcache Problems On xROM 1.5r4

Why do i get this output when testing? What the heck am i doing wrong.
I want some compcache with backing swap love too!!!!!!!!!
=== CompCache status ===
CompCache version 0.6+
Compcache enabled
CompCache: MemLimit 16384(system) 8192(user)
CompCache: BackingSwap /dev/block/mmcblk0p3(system) /dev/block/mmcblk0p3(user)
!!! Unable to set compcache cc_swappiness to user specific "60"
Current system value is "28"
=== CompCache status output ===
BackingSwap: /dev/block/mmcblk0p3
DiskSize: 100564 kB
MemLimit: 16384 kB
NumReads: 1
NumWrites: 0
FailedReads: 0
FailedWrites: 0
InvalidIO: 0
NotifyFree: 0
PagesDiscard: 0
ZeroPages: 0
GoodCompress: 0 %
NoCompress: 0 %
PagesStored: 0
PagesUsed: 0
OrigDataSize: 0 kB
ComprDataSize: 0 kB
MemUsedTotal: 0 kB
BDevNumReads: 0
BDevNumWrites: 0
find: /system/app/*.odex: No such file or directory
find: /data/app/*.odex: No such file or directory
#

anybody????????????

I think xROM is ignoring my userinit.sh and user.conf, because when I type "free" in to the terminal it shows the size of my swap partition under swap, rather than my compcache size :-S What command are you using to retrieve those values?

[Q] Many mount points

Hello XDA! I have a LOT of mount points which looks very strange. The following ones are repeating many many times:
/dev/loop0 /data/ext2data ext2 rw,noatime,nodiratime,errors=continue 0 0
/dev/loop0 /data/data ext2 rw,noatime,nodiratime,errors=continue 0 0
/dev/loop0 /data/system ext2 rw,noatime,nodiratime,errors=continue 0 0
/dev/loop0 /data/dalvik-cache ext2 rw,noatime,nodiratime,errors=continue 0 0
/dev/loop0 /data/app ext2 rw,noatime,nodiratime,errors=continue 0 0
Click to expand...
Click to collapse
see the attached mount.zip (txt inside, unzipped it is 120 kb!) for a full mount output. I suspect it is a reason my I9000 lags (I've applied ryanza lag fix)
(didn't find a thread on this topic)
Thanks,
-Nodir

Use OCLF from the market. This was fixed ages ago.

Tried to uninstall the lag fix, but it bricked: stocked at the boot screen (reboots indefinitely). Factory reset (from volume up + menu + power) doesn't help.
Now trying to restore it using [HOWTO] Froyo FW I9000XXJPM: Upgrade via Odin, Root, Recovery 2e, Lagfix! (can't post a link)
UPDATE: it is OK. I've reflashed it. 2.2 is nice!

mods please close thread

closed

How to compile TWRP recovery?
I followed the guide here http://rootzwiki.com/topic/23903-how-to-compile-twrp-from-source/
To summarize...
1. Install Linux
2. Set up CM10 build environment - this is sssssooooo easy and there are loads of guides available with just a simple google search.
3. Repo sync
4. Build standard cm10 from source
5. Delete the contents of the ~/android/system/bootable/recovery and replace with https://github.com/TeamWin/Team-Win-Recovery-Project/ - i just clicked on the download zip button on the top left and unzipped into the folder but am sure there is a proper way of doing this... zip clone???
6. gedit ~/android/system/device/samsung/galaxys2-common/recovery.rc and add: export LD_LIBRARY_PATH .:/sbin
7. gedit ~/android/system/device/samsung/n7000/BoardConfig.mk and add the following to the bottom of the file
#twrp
DEVICE_RESOLUTION := 800x1280
8. cd ~/android/system
9. make -j3 bootimage (if you have a quad core processor make -j5 bootimage)
10. you can find your boot.img at ~/android/system/out/target/product/n7000
11. Copy to SDCARD and flash with mobile odin
12. Done!!!!!

good work. appreciate the effort you have put in.
looking into it now.

Finally here, good work. Will try it as i'm already using TWRP in my N7.
Enviat des d'es meu Nexus 7 amb so Tapatalk2

im using TWRP to flash rom for N8013 and work great.Thanks

nice to see u
subscribed.

You Should pm entropy
Sent from my GT-N7000 using Tapatalk 2

I have sent him a PM
Sent from my GT-N7000 using XDA Premium HD app

timstanley1985 said:
Team Win Recovery Project 2.3 for Galaxy Note (CM10 only)
If you do not know what TWRP is, click here first...... now you know what TWRP is (and how very cool it is!!!) we can continue.
Foreword:
I have looked at those with devices with TWRP with envy for the entire time i have owned a Galaxy Note and have been waiting patiently for an experienced Dev to compile a version for the N7000. After a year of ownership this has not happened so i have decided to go ahead and do it myself!!
Why have you called this a proof on concept?
For a few reasons:
1. I am not an experienced Dev... i have built CM6, 7 and 10 from source and done all the usual tweaks to my android devices but that is where my experience ends. This in itself is no big deal in its self but leads me to point 2...
2. This recovery may have MMC_CAP_ERASE / Brick Bug! I do not know how to check if it is present or not! Until an experienced Dev confirms MMC_CAP_ERASE has been fully suppressed you should assume this recovery is dangerous. As soon as an experienced Dev confirms the recovery is safe i will update this post. If it is confirmed it is not safe i will remove all links
3. I unfortunately to do not have time to maintain this recovery. As Samsung recoveries are included in the boot.img (kernel) it will mean the recovery will need recompiling every time a change is merged to the kernel in CM10. As development is still very active on the N7000 kernel i cannot make the commitment to recompile this that often
4. I am not a kernel Dev therefore i can only compile stock kernel with TWRP recovery. We all love (me included) a custom kernel with all the normal tweaks, OC etc. etc. I will never be able to achieve this so want to use this as the seed for somebody else to take and use to build there own custom kernel with TWRP recovery
5. It needs more extensive testing.... I have been playing with it for an hour this morning and everything seems to work fine but needs more testing.
I have included how to compile TWRP in post two... did i hear someone say enough talking, i want to try this out!!!
How to install
I have attached the boot.img at the bottom of this post.
1. Download
2. Copy to SDCARD
3. Flash with Mobile Odin
4. Enjoy!!
Please remember: This recovery may contain MMC_CAP_ERASE / Brick Bug! I do not known how to check! It is built from CM10 sources and there are TWRP ports for other devices so should be safe but i cannopt be positive! Use at your own risk!
Experienced Dev's: Any feedback on whether this recovery is safe would be VERY gratefully received!
As soon as any confirmation of this recovery being unsafe i will remove link immediately!
Click to expand...
Click to collapse
Based on item #4 (this is using a stock kernel repacked with a new recovery) - it will not be safe for flashing things.
For wipes and backups, it depends on exactly how you built it. Run strings on the binary...
Code:
strings recovery |grep MMC
If you see
Code:
warning: %s: Wipe via secure discard suppressed due to bug in EMMC firmware
The recovery binary is safe to do wipes/backups with, but as said above, if you used a stock kernel, it will be dangerous to flash ZIPs.
Also, of course, as this is a galaxys2-family device, the moment you flash anything containing a new kernel, TWRP will be gone.

Sorry, I should have been clearer. When I say stock kernel I mean stock CM10 kernel. This recovery is built by deleting the /bootable/recovery/ folder and replacing it with TWRP recovery. The rest of the build is standard CM10.
Sent from my GT-N7000 using XDA Premium HD app

Some usage feedback: I found it quite hard navigating through a folder filled with many sub-folders and files to select what I want to flash...quite jerky UI and a lot different from the experience I get on my TWRP-recoveried tablet.
But great initial release dev - really, well done!

And is this Heimdall flashable or do you strictly recommend Odin only? I have never used Odin since it is blackbox and everyone I knew has been recommending Heimdall. I know the former is designed to best-case mimic the latter, but just want to cover all my bases.

Heimdall will work
Sent from my GT-N7000 using XDA Premium HD app

timstanley1985 said:
Heimdall will work
Sent from my GT-N7000 using XDA Premium HD app
Click to expand...
Click to collapse
Alright will give it a go. Thanks for the quick reply.

alharaka said:
Alright will give it a go. Thanks for the quick reply.
Click to expand...
Click to collapse
Yeah, so maybe I did not understand entirely but when I flashed I got a success with Heimdall 1.3.1 CLI on OS X (10.6.8).
Code:
my-bacbook-pro:~ root# heimdall flash --recovery /Users/myusername/Downloads/boot.img --verbose
Heimdall v1.3.1, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Manufacturer: "SAMSUNG"
Product: "Gadget Serial"
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 021B
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 83
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 02
max packet size: 0200
polling interval: 00
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 131072
Downloading device's PIT file...
PIT file download sucessful
Uploading RECOVERY
0%File Part #0... Response: 0 0 0 0 0 0 0 0
2%
File Part #1... Response: 0 0 0 0 1 0 0 0
5%
File Part #2... Response: 0 0 0 0 2 0 0 0
7%
File Part #3... Response: 0 0 0 0 3 0 0 0
10%
File Part #4... Response: 0 0 0 0 4 0 0 0
12%
File Part #5... Response: 0 0 0 0 5 0 0 0
15%
File Part #6... Response: 0 0 0 0 6 0 0 0
18%
File Part #7... Response: 0 0 0 0 7 0 0 0
20%
File Part #8... Response: 0 0 0 0 8 0 0 0
23%
File Part #9... Response: 0 0 0 0 9 0 0 0
25%
File Part #10... Response: 0 0 0 0 A 0 0 0
28%
File Part #11... Response: 0 0 0 0 B 0 0 0
31%
File Part #12... Response: 0 0 0 0 C 0 0 0
33%
File Part #13... Response: 0 0 0 0 D 0 0 0
36%
File Part #14... Response: 0 0 0 0 E 0 0 0
38%
File Part #15... Response: 0 0 0 0 F 0 0 0
41%
File Part #16... Response: 0 0 0 0 10 0 0 0
44%
File Part #17... Response: 0 0 0 0 11 0 0 0
46%
File Part #18... Response: 0 0 0 0 12 0 0 0
49%
File Part #19... Response: 0 0 0 0 13 0 0 0
51%
File Part #20... Response: 0 0 0 0 14 0 0 0
54%
File Part #21... Response: 0 0 0 0 15 0 0 0
57%
File Part #22... Response: 0 0 0 0 16 0 0 0
59%
File Part #23... Response: 0 0 0 0 17 0 0 0
62%
File Part #24... Response: 0 0 0 0 18 0 0 0
64%
File Part #25... Response: 0 0 0 0 19 0 0 0
67%
File Part #26... Response: 0 0 0 0 1A 0 0 0
70%
File Part #27... Response: 0 0 0 0 1B 0 0 0
72%
File Part #28... Response: 0 0 0 0 1C 0 0 0
75%
File Part #29... Response: 0 0 0 0 1D 0 0 0
77%
File Part #30... Response: 0 0 0 0 1E 0 0 0
80%
File Part #31... Response: 0 0 0 0 1F 0 0 0
83%
File Part #32... Response: 0 0 0 0 20 0 0 0
85%
File Part #33... Response: 0 0 0 0 21 0 0 0
88%
File Part #34... Response: 0 0 0 0 22 0 0 0
90%
File Part #35... Response: 0 0 0 0 23 0 0 0
93%
File Part #36... Response: 0 0 0 0 24 0 0 0
96%
File Part #37... Response: 0 0 0 0 25 0 0 0
98%
File Part #38... Response: 0 0 0 0 26 0 0 0
100%
RECOVERY upload successful
Ending session...
Rebooting device...
But I rebooted and was back in ClockwordModRecovery 6.1.2. Did I misunderstand the directions? Sorry, my first time using Heimdall to write to my device; last few times I just detect'n'dump-ed to avoid destroying my phone because it was unnecessary.

If I was you just download mobile Odin lite from xda and flash with that. It's very easy that way
Sent from my GT-N7000 using XDA Premium HD app

timstanley1985 said:
If I was you just download mobile Odin lite from xda and flash with that. It's very easy that way
Sent from my GT-N7000 using XDA Premium HD app
Click to expand...
Click to collapse
I'll give that a try. Who knows what the deal is then.

alharaka said:
I'll give that a try. Who knows what the deal is then.
Click to expand...
Click to collapse
Ok, so I configured Mobile ODIN Lite (thanks for the pointer, by the way, amazing app I thought I had to pay for when I saw it a few weeks ago; had no idea I could test a lite version on XDA, sweet). So, installed it and got the N7000 add-on. What partition do I work with: Hidden?

Just click open file, select the boot.img and then scroll down and click flash image.
You click yes to confirm and then it will flash and reboot
Sent from my GT-N7000 using XDA Premium HD app

timstanley1985 said:
Just click open file, select the boot.img and then scroll down and click flash image.
You click yes to confirm and then it will flash and reboot
Sent from my GT-N7000 using XDA Premium HD app
Click to expand...
Click to collapse
Sorry for all the silly questions, and thanks again. I just wanna be sure since the recovery, well, makes mistakes less serious and I rely on it heavily. Once that is broken fixing my phone will get much more technical than I have time for.

[KERNEL] [test] [MM 6.0 Stock ROM] Frankenlenok (AW2 test kernels on post #86)

Introduction
This is a kernel for LG Watch R built from stock sources (android-msm-lenok-3.10-marshmallow-mr1-wear-release branch) with some minor tuning and modifications for now. I'll probably add more features and optimizations but for the time being is pretty much stock on steroids.
This kernel is for stock ROM MEC23G
Disclaimer
Although I try to test it and keep it as stable as possible some of the changes can be considered experimental stuff, so don't blame me if it acts weird or goes up in flames.
Features
Multicore enabled
Bricked Hotplug (cores are plugged/unplugged based on load, when screen is off only 1 core is active. Read this post)
Power efficient workqueues
CPU Touch Boost
/dev/frandom support
Optimization flags
UBER Toolchain 4.9
Installation instructions
Download the boot image, reboot into bootloader and flash with fastboot:
Code:
fastboot flash boot boot.img
Alternatively you can test drive it without flashing:
Code:
fastboot boot boot.img
Download
Latest version is v0.4.1
https://www.androidfilehost.com/?w=files&flid=52516​
Full and updated source code available on github.
Donations
I don't deserve that much credit for this kernel, I just try different combinations and make minor modifications to see which one appears to work better. However, I spend many hours working on this and doing extensive testing, if you feel like helping me out I'd appreciate some tiny donations to cover some minor expenses. Thank you!
​
Thanks To/Credits
flar2
franciscofranco
showp1984
intersectRaven
AudioGod
XDA:DevDB Information
Frankenlenok, Kernel for the LG G Watch R
Contributors
dirtyhank
Source Code: https://github.com/dirty-hank/frankenlenok
Kernel Special Features:
Version Information
Status: Testing
Created 2016-03-21
Last Updated 2017-04-09

Changelog
v0.4.1 (2016-03-31)
Fix wrong kernel image
v0.4 (2016-03-31)
CPU max frequency cap to 1GHz
Touchboost frequency decrease to 787MHz
Hotplug thresholds tuning
CPU frequency set to 300MHz when screen off
v0.3 (2016-03-26)
Switch to interactive governor by default
Switch to noop scheduler by default
Remove CPU max frequency cap
CPU Boost
v0.2 (2016-03-23)
Bug fixes
Power efficient workqueues
/dev/frandom support
Minor optimizations
v0.1 (2016-03-21)
Optimization flags
Bricked Hotplug

Reserved

I've flashed you kernel and testing it now. For now it's running smooth. Is there a way to see if all cores are active ?

Cameo164 said:
I've flashed you kernel and testing it now. For now it's running smooth. Is there a way to see if all cores are active ?
Click to expand...
Click to collapse
I do via adb shell. Here's how:
Enable Developer Options: Go to Settings->About and click 7 times on the build number
Enable ADB debugging: Go Settings->Developer options
Connect Watch to computer and run"adb shell"
Check Watch and allow adb access to the computer
Run this command from the adb shell:
Code:
while sleep 1; do cat /sys/devices/system/cpu/cpu[0-3]/online | xargs echo; done
This command will show you the 4 cores online status every second. Here's an example of my watch turning on, launching Google Maps (one of the most demanding apps) and then settling in and going back to sleep:
Code:
1 0 0 0
1 0 0 0
1 0 0 0
1 1 1 0
1 1 1 0
1 1 1 0
1 1 1 0
1 1 0 0
1 1 0 0
1 0 0 0
1 0 0 0
1 1 0 0
1 1 0 0
1 1 0 0
1 0 0 0
1 0 0 0
1 1 0 0
1 1 0 0
1 0 0 0
1 0 0 0
1 0 0 0
1 1 0 0
1 1 0 0
1 1 0 0
1 1 0 0
1 0 0 0
1 0 0 0
1 1 0 0
1 1 0 0
1 0 0 0
1 0 0 0
1 0 0 0
1 1 0 0
1 1 0 0
1 0 0 0
1 0 0 0
1 0 0 0
1 0 0 0
1 0 0 0
As you can see up to 3 cores are used when Google Maps is launching, then alternates between 1 and 2. In my experience 4 cores are rarely online and since only 1 core is online when the screen is off I haven't noticed a big battery drain, actually my battery life is slightly better than stock kernel and the device is way smoother with multicore.

Cameo164 said:
I've flashed you kernel and testing it now. For now it's running smooth.
Click to expand...
Click to collapse
Same here =)

Sorry, but i cant get root with your kernel.
i followed this steps, but doesnt rooted .
-flash boot vía adb
-flash supersu 2.65 vía twrp
When i open kernel auditor, i havent root?

jordirpz said:
Sorry, but i cant get root with your kernel.
i followed this steps, but doesnt rooted .
-flash boot vía adb
-flash supersu 2.65 vía twrp
When i open kernel auditor, i havent root?
Click to expand...
Click to collapse
Can you send me the recovery.log after you install SuperSU? Usually /tmp/recovery.log

jordirpz said:
Sorry, but i cant get root with your kernel.
i followed this steps, but doesnt rooted .
-flash boot vía adb
-flash supersu 2.65 vía twrp
When i open kernel auditor, i havent root
Click to expand...
Click to collapse
I did this and it worked for me,
use the tool from
http://forum.xda-developers.com/g-w...l-windroid-universal-android-toolkit-t3048122
and unlock the bootloader and then follow the fastboot flash. Remember this will reset your watch.
Regarding the batter usage: approximately less than 1% when idle. and around 2 % during the day.
There is little bit of time lag in showing the notification i am not sure if its related to kernel.
@dirtyhank will let you know after testing a bit more

I've uploaded a new version that should fix the root issue from TWRP.
v0.2
Bug fixes
Power efficient workqueues
/dev/frandom support
Minor optimizations

dirtyhank said:
I've uploaded a new version that should fix the root issue from TWRP.
v0.2
Bug fixes
Power efficient workqueues
/dev/frandom support
Minor optimizations
Click to expand...
Click to collapse
I can confirm, my lg R is rooted now. Thank you sir?

jordirpz said:
I can confirm, my lg R is rooted now. Thank you sir?
Click to expand...
Click to collapse
BTW, just curious, what do you use root for? I couldn't use my smartphone unrooted but the watch is just the opposite, I've never felt the need to root it.

dirtyhank said:
BTW, just curious, what do you use root for? I couldn't use my smartphone unrooted but the watch is just the opposite, I've never felt the need to root it.
Click to expand...
Click to collapse
Well, i use advanced settings for watch , and i need root.

I just flashed the kernel an hour ago. First impression is really good, my watch is definitely faster then on stock. So thanks a lot for your work!

another good news about android wear
http://forum.xda-developers.com/android-wear/general/android-wear-v1-5-adds-proper-support-t3343124

New version:
v0.3
Switch to interactive governor by default
Switch to noop scheduler by default
Remove CPU max frequency cap
CPU Boost
After some testing I've decided to go with interactive governor, CPU boost and no cap for max CPU frequency. I haven't noticed a negative effect on battery life and the smoothness is unbelievable. Give it a try and let me know how it works for you.

Been having a problem with the watch since switching to Franken kernel where the watch will freeze with screen off and hard reset (holding the button down) to restart the watch is the only way to resolve. Anybody else experiencing this?
Cheers,
B.D.

Great, a new kernel dev for Watch R. Love it.
Will try your kernel

BostonDan said:
Been having a problem with the watch since switching to Franken kernel where the watch will freeze with screen off and hard reset (holding the button down) to restart the watch is the only way to resolve. Anybody else experiencing this?
Cheers,
B.D.
Click to expand...
Click to collapse
I'd wipe cache.

Come on guys, I'd appreciate some feedback