Related
FuguMod kernel is now available for the Galaxy Nexus.
It has been reported to work both on GSM and CDMA versions. But I can only test it on GSM version myself.
You can download them at:
http://fugumod.org/galaxy_nexus/
Source and changelog can be found here:
https://github.com/renaudallard/gnexus_kernel
IRC channel:
irc.freenode.net #fugumod
To install, just download the appropriate version for your ROM (4.0.x) and flash it with fastboot (RAW version: fastboot flash boot kernel-$VERSION.img) or flash it with CWM (CWM/zip version).
Please note that not all versions exist in CWM format.
4.0.2 version is based on official google initramfs + init.d support (is now in deprecated state, no future updates will be brought)
4.0.3 version is based on the initramfs of AOSP + init.d support. it is compatible with 4.0.4
4.0.4 version is based on the initramfs of AOSP + init.d support. it is compatible with 4.0.3
4.1.x version is based on the initramfs of AOSP + init.d support.
4.2.x version is based on the initramfs of stock kernel
4.3 version is based on the initramfs of stock kernel (use that one for CM, not reco)
4.3-reco version is based on the initramfs of stock kernel, even with install-recovery.sh enabled (so supersu can work, but if you don't have supersu, don't use it)
for experimental versions, do not flash if you are not ready for big troubles, they may not even boot, burn your phone and eat your cat.
Features:
- stackprotector
- various security enhancements
- RCU boost
- Automatic process grouping
- TUN (compiled in kernel)
- latest 3.0 linux kernel
- newer wifi driver
- gamma/color hack
- CM9 compatibility
- PaX (from r333)
- grsec (from r624)
- TouchWake from Ezekeel (from r778)
Versions
Kernels are based on the below version scheme
kernel_FuguMod_20120111_r20-4.0.3.img
20120111 is the date it has been packaged
r20 is the release number
4.0.3 is the ROM it is compatible with
Color offsets
In CM9, just use the built in function.
For other ROMs, the settings offsets are in
/sys/class/misc/samoled_color/
For example green_v1_offset
Just edit the three green red and blue color settings. Default value is 60.
It can be done on the console with a command like this: echo 55> /sys/class/misc/samoled_color/green_v1_offset
Stable vs Testing
There are sometimes kernels in testing folder. These may be very stable or may not boot at all. Be sure to have an USB cable and fastboot under the hand if you try one of these. That said, in general, if they stay into testing folder for more than 15 min, they should at least boot and work more or less. I tend to remove non booting kernels from testing folder in less than 10 min (depending a little bit on the speed testers take them), and so if you see them one hour later, you should assume they are safe enough to flash.
So, in general Stable is the safest bet, but Testing may be the best. I, myself, generally run testing one.
Deprecated folder
In general, unless you really know what you are doing, you should avoid flashing those, they are mainly there for historical reasons.
Radio drops and blueish/faded screens
Please ensure you are running the correct firmware for bootloader and baseband, like in the matrix in bottom of that page: http://source.android.com/source/building-devices.html
For those where problems persist after flashing recommended versions, try "echo 0 > /sys/kernel/debug/smartreflex/sr_core/autocomp"
OTG unmounting internal SD
Please see http://forum.xda-developers.com/showpost.php?p=24040652&postcount=174
Mirrors
bootloaders: http://fugumod.org/bootloaders-gn/
basebands: http://fugumod.org/modem/galaxy_nexus/
Check for vulnerabilities
http://www.xray.io
Compatibility with hackish style apps
All apps which require direct memory write, access to symbols or memory offsets or modules will NOT work. And, no, don't ask they won't be supported in the future.
Security
If you want good security when your phone is stolen, in addition to encryption, don't forget to turn debugging off. Also, use enpasschanger to change your encryption password, any short PIN encryption can be cracked in a few minutes easily (for example, using my script at http://pastebin.com/Mdu06RZN)
Redistribution
As per GPL, you are authorized to redistribute this kernel with any of your custom ROMs provided you give out the source code like I do. You can link to my github in your distribution site.
However, if you modify the kernel yourself, whatever the modification is (compiling it yourself with a different compiler is a modification), you are not authorized to name it FuguMod, although you can credit me and tell the base comes from FuguMod but you cannot call the kernel itself FuguMod.
Touchwake
to enable it "echo 1 > /sys/devices/virtual/misc/touchwake/enabled"
to make it always on: "echo 1 > /sys/devices/virtual/misc/touchwake/always"
Beware, touchwake is known to sometimes produce screen locks
PGM
See "Compatibility with hackish style apps". Use touchwake instead.
Lost root
Use supersu instead of superuser from chainsDD (superuser from koush seems to work fine too). Change the setting in SuperSU to ignore CM root setting if you are running CM.
Updater app
https://play.google.com/store/apps/details?id=my.zin.rashidi.android.fugumod
root on 4.3
Currently only reco version has support for root access with supersu. Keep in mind that su access is now (as of 4.3) provided by a daemon, which may drain your battery or worse. Please think about your uses for root to see what is better fit for you.
W00t fugumod on the nexus!!
Will try it, thanks for dropping this here.
I'm totally happy
Finally! A kernel we can rely on Thanks alot mate, looking forward to further developments on this. I remember FuguMod fondly on the SGSII
Nitroz said:
Finally! A kernel we can rely on Thanks alot mate, looking forward to further developments on this. I remember FuguMod fondly on the SGSII
Click to expand...
Click to collapse
You probably mean SGS1.
I'm not entirely sure how accurate setcpu is at reading frequencies, but it seems to be stuck at 700mhz after a reboot. Moving the sliders a bit allows the cpu to use the entire range of 350-1200mhz as intended. I'm on AOKP milestone 2 if it matters and using r26.
Haven't yet tried this, but maybe min frequency when booting is set to 700mhz?
when you open setcpu, is the min slider at 350mhz?
What governor are you using? Not sure it matters though, but it might so.
maybe try using cpuspy to read the usage. Also, there may be something in your init.rd limiting the frequencies
Sent from a Nexus
Yes, min and max are set at 350/1200 on the sliders, but the green text says it's at 700/1200. Governor is the default interactive. Right now, I'm only using setcpu as a tool to view my frequencies as everything is "under observation" as I've only had this phone for a week. I did a reboot last night before going to bed. When I woke up 6 hours later, batt was down to 92%. Which is a quite fast considering I only had 5 hours of sleep. That's when I noticed that frequency was pegged at 700mhz the whole time. I tried opening other apps that should ramp up the speed, but as far as I can tell, it was still at 700.
Now, as I said, I'm only using setcpu to check my frequencies so "set at boot" isn't applied. When I apply "set at boot," min/max is at 350/1200 after a reboot and CPU scales up and down properly. So does this mean the default setting of the kernel is 700/1200? The thing is, even with max at 1200. I can't seem to make it scale up to 1200.
EDIT:
nikademus said:
maybe try using cpuspy to read the usage. Also, there may be something in your init.rd limiting the frequencies
Sent from a Nexus
Click to expand...
Click to collapse
I don't seem to have an init.rd file anywhere. I did a search using root explorer.
Edit 2:
CPUSpy says I'm only using 700 and DeepSleep even after running Asphalt 6. This is after a reboot without setting anything at boot with setcpu.
j.go said:
Yes, min and max are set at 350/1200 on the sliders, but the green text says it's at 700/1200. Governor is the default interactive. Right now, I'm only using setcpu as a tool to view my frequencies as everything is "under observation" as I've only had this phone for a week. I did a reboot last night before going to bed. When I woke up 6 hours later, batt was down to 92%. Which is a quite fast considering I only had 5 hours of sleep. That's when I noticed that frequency was pegged at 700mhz the whole time. I tried opening other apps that should ramp up the speed, but as far as I can tell, it was still at 700.
Now, as I said, I'm only using setcpu to check my frequencies so "set at boot" isn't applied. When I apply "set at boot," min/max is at 350/1200 after a reboot and CPU scales up and down properly. So does this mean the default setting of the kernel is 700/1200? The thing is, even with max at 1200. I can't seem to make it scale up to 1200.
EDIT:
I don't seem to have an init.rd file anywhere. I did a search using root explorer.
Edit 2:
CPUSpy says I'm only using 700 and DeepSleep even after running Asphalt 6. This is after a reboot without setting anything at boot with setcpu.
Click to expand...
Click to collapse
OK, 4.0.3 init.rc I have been given is the one from Francisco Franco and it limits the minimum frequency to 700mhz. This will be solved in next build, in a few minutes. Although you should be able to go over 700Mhz
nikademus said:
OK, 4.0.3 init.rc I have been given is the one from Francisco Franco and it limits the minimum frequency to 700mhz. This will be solved in next build, in a few minutes. Although you should be able to go over 700Mhz
Click to expand...
Click to collapse
Ah, well that's good to hear. Maybe the conditions needed to raise the frequency are not being met. Not that I know anything about kernels...
j.go said:
Ah, well that's good to hear. Maybe the conditions needed to raise the frequency are not being met. Not that I know anything about kernels...
Click to expand...
Click to collapse
Try the latest version, I removed all Francisco tweaks.
nikademus said:
Try the latest version, I removed all Francisco tweaks.
Click to expand...
Click to collapse
All right, I'll give it a spin tonight and post how it goes. Thanks!
I think I will be upgrading my phone to 4.0.3. This would mean I would not support 4.0.2 as I would not be able to test it properly. Are there users here who need the 4.0.2 version?
great
R37 für 4.0.3 runs flawless.
I use CM9 kang by fitsnugly.
R40 also flawless on fitsnugglys CM9 kang
r41 is out, probably last release for today
I flashed the latest KANG from today and the 122211 gapps with R41.
Works like a charm so far
aosp kang built today, flashed R43 just now. booted fine first try, wifi/bluetooth are fine, data call as well, rebooted, set scheduler/gov to deadline/ondemand, min/max freq to 1.2ghz, score on antutu maxing out around 5200, 5300. with my modified stock, i hit 6200+ in those conditions.
switch back to cfq/interactive, sd write speed goes up a bit to 10.4mb/s (deadline was just under 9.4mb/s), cpu integer 1304, float 1099, pushes score up a bit but still not reaching 5400 (this is with all tests selected, 2d/3d, database..). tweaked lowmemorykiller, antutu score jumps to 5600+.
but benchmarks mean almost nothing, i know. overall it's pretty smooth, fast on bootup, ocasional "lag" here and there (but that may be Mr. Android's fault).
will report more as the kernel settles in.
thanks nikademus.
edit: just re-installed gta. it seems i have no in-game sounds at all? it's fine until it gets to the main menu though. anybody else seeing this? happening on stock kernel too, wth..
edit2: jumping on r44.
flashed R44 on the latest fitsnugly kang. all is well. as expected, as only unused modules have been removed
Hello xda,
CAMERA PATCH FOR ALL CM11
http://www.mediafire.com/download/5lw858r2ctqakd0/VideoRecordingPatch+FOR+GIO.zip
FINAL RELEASE: https://www.mediafire.com/folder/cpra0qbzxn4k4/FINAL_RELEASE
RELEASE 4.5: https://www.mediafire.com/?gd5ampsaafmrjga
RELEASE 4: https://www.mediafire.com/?8rc4wblbymy00k2
RELEASE 3: https://www.mediafire.com/?dmicnl8wnj7fyjx
I got the cpu step!
LINK: http://www.mediafire.com/download/8a67jkv4rs93x43/cm-11-20150328-UNOFFICIAL-gio+WITH+KERNEL.zip
As I promised
LINK: http://www.mediafire.com/download/b07mqnqrqmbxgbl/cm-11-20150328-UNOFFICIAL-gio.zip
Changelog:
FINAL:
Full Cyanogenmod code sync
New audio decoder (No idea)
Two Version (MSM, MSM7x27)
5/9/2015
Fix Camera recording
4/17/2015:
(RELEASE 4.5)
ADDED CPU GOVERNORS AND I/O SCHEDULERS
-Badass
-SmartassH3
-SmartassV2
I/O
-Sio
-Sioplus
(RELEASE 4)
Switched to Cm12 kernel (Net improvements, but still Cm11)
Updated Cyanogenmod Sources
4/06/2015: (RELEASE 3): Changed Cpu steps, added cpu governors, and added I/O schedulers
3/28/2015: Added cpu steps
3/28/2015 Initial Release
NOTES:
(RELEASE 4)
I need to re add all of the kernel governors and I/O schedulers.
What I noticed so far is loading website is much faster
(RELEASE 3)
CPU Governor added:
-SMARTASSV2
-SMARTASSH3
-BADASS with some algorithm
I/O Scheduler added:
-SIO
-SIOPLUS
-removed zen because I find it makes the phone slower and crappy battery
Thanks to @belyava for added gapps to my build. Here is the links to post 44
http://forum.xda-developers.com/showpost.php?p=59892898&postcount=44
Credits:
ME!
androidarmv6 for kernel and cyanogenmod
Kernel Source: https://github.com/HerroYou/android_kernel_samsung_msm
KERNEL: 3.0.31
Working:
Everything for the most part
BUGS: You tell me
*** Fixed Terminal issue
1. Backlights doesn't work
2. Video recording doesn't work (FIXED)
ISSUES: Can not pause recording, other than that it works!
FAQ:
- To enable Performance/Developer settings go to "About Phone" and tab the build number until it says "You are now a developer"
-To fix music stutter raise minimum cpu frequency to 245
I will upload a new build after I get the cpu steps to work
Release #2!
Download links fixed
100 downloads and no feed back?
And I might release something new this weekend, if I have the time.
HerroYou said:
100 downloads and no feed back?
And I might release something new this weekend, if I have the time.
Click to expand...
Click to collapse
I flashed this ROM the other day, but I couldn't stick to it because it's slow and buggy. The 3.0 kernel has not improved the ROM's perfomance. Thanks for your affords
Without gapps installed your ROM works great! no noticable lag.
From the convo in the Slim thread I have 113MB free internal space so I don't think that's the problem...
belyava said:
I flashed this ROM the other day, but I couldn't stick to it because it's slow and buggy. The 3.0 kernel has not improved the ROM's perfomance. Thanks for your affords
Click to expand...
Click to collapse
I need to put some governors into the kernel to improve performance. You enable SD swap for some more performance
orangejuice43 said:
Without gapps installed your ROM works great! no noticable lag.
From the convo in the Slim thread I have 113MB free internal space so I don't think that's the problem...
Click to expand...
Click to collapse
Check "About phone, Partition info, System."
I found a bug, video recording doesn't work.
HerroYou said:
I need to put some governors into the kernel to improve performance. You enable SD swap for some more performance
Click to expand...
Click to collapse
As stated by spyke83, Sd swap when enabled leads to random reboots. Since then I always disable it. More governors doesn't mean better performance
belyava said:
As stated by spyke83, Sd swap when enabled leads to random reboots. Since then I always disable it. More governors doesn't mean better performance
Click to expand...
Click to collapse
It doesn't reboot for me since I set it to 20% and I only added 3 governors: Smartassv2, SmartassH3, and badass with some I/O scheduler: Sio, and Zen.
And with the governor badass I added some power saving algorithm
HerroYou said:
It doesn't reboot for me since I set it to 20% and I only added 3 governors: Smartassv2, SmartassH3, and badass with some I/O scheduler: Sio, and Zen.
And with the governor badass I added some power saving algorithm
Click to expand...
Click to collapse
Alrighty, sounds good. May be you could also take a look at bug when Google Play Services are being stopped?
belyava said:
Alrighty, sounds good. May be you could also take a look at bug when Google Play Services are being stopped?
Click to expand...
Click to collapse
I never had that bug? The way that I install gapps is:
1. I install link2sd premium and connect it to my 2nd partion of 512 mb
2. turn on wifi and reboot to recovery
3. Install mardon's gapps
4. after booting turn off wifi and tell link2sd to move the google player service to the 2nd partion (move app to sd and link it)
5. Turn on wifi login
HerroYou said:
I never had that bug? The way that I install gapps is:
1. I install link2sd premium and connect it to my 2nd partion of 512 mb
2. turn on wifi and reboot to recovery
3. Install mardon's gapps
4. after booting turn off wifi and tell link2sd to move the google player service to the 2nd partion (move app to sd and link it)
5. Turn on wifi login
Click to expand...
Click to collapse
Installing gapps is not the problem. The issue comes up when when your Google Services and the Play store get updated. Then installing every app leads to a "Unfortunatelly, Google Services has stopped!" message. Wiping data and deleting the Google account doesn't help
HerroYou said:
Check "About phone, Partition info, System."
Click to expand...
Click to collapse
Oh right ok,
/System says 184MB / 206MB
So yes, it looks like there's not much space!
I guess I will try your method of installing gapps from above. I assume I just find an apk online of link2sd and install manually?
Thanks
orangejuice43 said:
Oh right ok,
/System says 184MB / 206MB
So yes, it looks like there's not much space!
I guess I will try your method of installing gapps from above. I assume I just find an apk online of link2sd and install manually?
Thanks
Click to expand...
Click to collapse
Link2SD won't link system apps. It links user (in /data) apps only
belyava said:
Link2SD won't link system apps. It links user (in /data) apps only
Click to expand...
Click to collapse
Oh right, so any idea how I would get this working?
Thank you!
This is a (lightly) modified, based on stock, kernel for the 1st gen Asus Zenwatch; repacked from the stock boot.img (by replacing zImage).
See the changelog below for changes from stock and between versions.
NOTE: This kernel is only for the MEC23S (Android Wear 1.4) build, and is still experimental. I have not tested this on the newest build (and it's likely not compatible), but I'll probably do a final build for the latest version as a sendoff.
To download the kernel, go to the Downloads tab at the top of the OP, and download the file (version)-ondemand.img.
I can provide a mirror if the DevDB download doesn't work for some people.
I'm not entirely sure what else I can test/add to this kernel (without needing root, since it's not flawless on this watch), so if anyone has some suggestions, I can try adding those things to the kernel, so for now, new builds will come as there are new features to add.
If you want to try out this kernel, I recommend that you try just booting it through fastboot first:
Code:
fastboot boot (version)-ondemand.img
If something goes wrong, I am also including the stock kernel (boot_original.img in the downloads tab).
If you decide that you want to flash the kernel, you need to unlock your bootloader first (it will wipe all your data, so backup first), then run this command:
Code:
fastboot flash boot (version)-ondemand.img
To check if the custom kernel actually loaded, run an ADB shell, and type:
Code:
uname -a
The kernel version number should have "(version)-ondemand" right after it.
Notes:
For now, I am mainly planning to test out features that I can add or modify on the kernel without compromising stability or battery life, and I will also be testing each build on my own Zenwatch.
If there is enough interest, I can try and add custom CPU governors or set a different included one as default, but since there's no way to change the governor without root, I'll need to upload separate kernel images for each new default governor.
Vibration intensity is pretty easy to increase, so if 3100 mV still feels a bit weak, I can try bumping it up a bit more, like to 3150 or 3200 mV (I don't want to risk raising it too much and damage hardware).
Building the kernel doesn't take too long, so if there are any bugs or features to be added, I can compile and upload a new kernel pretty quickly.
XDA:DevDB Information
Custom ZW Kernel, Kernel for the Asus ZenWatch
Contributors
itechnoguy
Source Code: https://github.com/iTechnoguy/zwkernel
Kernel Special Features:
Version Information
Status: Testing
Current Beta Version: v2
Beta Release Date: 2016-04-10
Created 2016-03-30
Last Updated 2016-04-10
Changelog:
v2 - 04-10-2016
Changes:
I/O Scheduler no-op added (and made default; stock kernel default was CFQ)
Compiled with Linaro GCC 4.9
Note: So far, ondemand is one of the only CPU governors other than performance that don't cause the Zenwatch to bootloop (including 3rd party governors), so for now, ondemand will remain the default (a couple of other governors, like interactive remain compiled in, but bootloop when made default)
v1 - 03-29-2016
Changes from stock kernel:
Uses the ondemand governor by default (instead of performance)
Slightly increased vibration strength (measured in mV; increased from 3000 to 3100 mV)
To-Do/Look into:
Implementing CPU (and IO schedulers?) governors without having to create a separate kernel image for each governor, meaning needing systemless root to avoid needing to reflash the system partition before an OTA
Possibly add init.d support so that scripts can change the governor on boot (without needing an app, which would probably be hard to use on the ZW's small screen)
Kernel-level support for disabling the default low-bit ambient mode (since build.prop edits don't work)
If you have the opportunity when you are looking around in there see if there is anything in the kernel that forces low bit ambient. I have tried changing the build.prop to turn it off as you would on other devices and it has not been successful.
hecksagon said:
If you have the opportunity when you are looking around in there see if there is anything in the kernel that forces low bit ambient. I have tried changing the build.prop to turn it off as you would on other devices and it has not been successful.
Click to expand...
Click to collapse
I'll look into it, but from what it looks like so far, it seems that low bit ambient mode isn't a kernel-level feature. I'll keep digging around though, and see if there is something within the kernel that controls it.
Maybe ability to disable 2 cores to increase battery life?
Sent from my SM-G925F using Tapatalk
macia10 said:
Maybe ability to disable 2 cores to increase battery life?
Click to expand...
Click to collapse
I can implement that; it's more of a ramdisk edit (as seen in tiny4579's discontinued kernel for this same watch).
I guess there's also the parameter CONFIG_NR_CPUS to set the max number of CPU cores (like setting maxcpus in the ramdisk), but on a kernel level. I'll take a look and test it out.
I've been testing a couple of builds with reduced cores, and I've been running into issues. Any dual core setup I've tried so far (either by limiting the CPUs within the kernel or just the ramdisk) seems to be unstable, causing the watch to reboot within a couple of minutes of finishing boot. I guess the ramdisk editing worked on a previous kernel/build of Android Wear, but it's causing some sort of instability on Marshmallow now.
I also tested with tri-core builds, but none of those even made it past the boot logo.
I have flashed the kernel and will run it for a few days to see if there is any battery improvment. As far as CPU goes maybe using a hotplugging governor is the way to go? Not sure if there are any modern ones out there but I recall back in the day before hotplugging was done with a stand alone module.
hecksagon said:
I have flashed the kernel and will run it for a few days to see if there is any battery improvment. As far as CPU goes maybe using a hotplugging governor is the way to go? Not sure if there are any modern ones out there but I recall back in the day before hotplugging was done with a stand alone module.
Click to expand...
Click to collapse
I've been watching the CPU usage using AIDA64, and it seems like most of the cores are inactive most of the time, so I think the kernel might already be using Qualcomm's built in hotplug driver.
I might have to add in a separate hotplugging governor, which shouldn't be too much of a problem, since the default CPU governors were just performance, ondemand, userspace, and conservative (interactive is also available, which I may make default next if a hotplug governor doesn't work well).
In terms of battery life, I noticed that ondemand does help increase idle/screen-off battery time, but screen-on time seems to be about the same as when using performance.
get about an extra day with ambient off and tap to wake. I'm at the end of day 2 with ~30% left.
I recall back when we had root that previous versions of the official software ran only single core on performance governor. I think the CPU was limited to like 800 or 1000 MHz too.
Yeah, the default max clock speed is set to roughly 787 MHz, and the minimum (in this kernel version) was at 300 MHz.
I think I may make the next build with interactive instead of ondemand, to see if interactive offers any better battery life, since hotplug governors basically refuse to compile with a newer kernel. I'm also considering making the new default minimum clock speed to 250 MHz (or lower, if it doesn't get unstable).
New build is up (v2), available on the DevDB Downloads tab (full name: v2-ondemand.img). See the second post for changes.
I just realized that my watch updated to Android Wear build MWD48B by itself, which also brings a new kernel (Asus posted the new sources a few days ago). I don't know if there's still interest in a modified kernel, but I can try building a new kernel with the updated sources (which may take a bit since I don't have access to my normal build system).
itechnoguy said:
I just realized that my watch updated to Android Wear build MWD48B by itself, which also brings a new kernel (Asus posted the new sources a few days ago). I don't know if there's still interest in a modified kernel, but I can try building a new kernel with the updated sources (which may take a bit since I don't have access to my normal build system).
Click to expand...
Click to collapse
col you have latest build already.
Partners watch has not recieved the update... But she has twrp and the OPs Kernel flashed so may be thats the reason..
Could someone confirm if going back to stock recovery on kernel will allow the update and proved instructions and downloads to restore them
lohtse said:
col you have latest build already.
Partners watch has not recieved the update... But she has twrp and the OPs Kernel flashed so may be thats the reason..
Could someone confirm if going back to stock recovery on kernel will allow the update and proved instructions and downloads to restore them
Click to expand...
Click to collapse
You'll have to restore the stock recovery to install the OTA update (I made a backup of the stock recovery from the last update here: https://drive.google.com/open?id=0B6eYQrCg9u-bUTA2d3dRdEZBbXM).
In terms of having the custom kernel flashed, I don't think that affects the update, because my Zenwatch stealth updated without me noticing (even though I had the kernel flashed), since I had the stock recovery installed, not TWRP.
I would love continued effort on a kernel but it doesn't look like this device has much life left here at XDA. If you don't personally believe you will benefit from your effort, don't make it for others.
hecksagon said:
I would love continued effort on a kernel but it doesn't look like this device has much life left here at XDA. If you don't personally believe you will benefit from your effort, don't make it for others.
Click to expand...
Click to collapse
I am considering doing one final kernel for this watch (no ETA, because I've been really busy lately), since it's very likely that Wear 1.5 will be the final update, so the kernel won't need updating past that (if it's stable, of course). It might not see much use, but it'll still be here for people that continue to use this watch past its official support life.
Guys i wanted to know amoung miui 5 ,6,7,......which has the best ram management??just got my 1s
CM
um....no...not really... miui has as good as ram management as cm. AND somtimes a bit better ram management for me miui 8 is perfect for you. I love it. But on 4.4 (miui too) and 5.1 roms when locked, you cannot recieve messenger notifications well.... led isn't blinking or absolutely no notification....only if you open messenger. on miui you lose lot more percent of battery life when sleep compared to. other roms. except this, miui 8 is best . with phantom v7 and yankactive or zzmoove governor.
Try MIUI multi rom with neon kernel. Most of chinese stuffs has been removed and it also provide features that are not available in Global versions like Global search, etc.
CM and all other roms are custom roms so are they highly customized, MIUI Multi is too customized so give it a try. Install Neon kernel and tweak settings as per your use using kernel auditor. This will solve battert drain issue.
Enjoy MIUI!
alok932 said:
Try MIUI multi rom with neon kernel. Most of chinese stuffs has been removed and it also provide features that are not available in Global versions like Global search, etc.
CM and all other roms are custom roms so are they highly customized, MIUI Multi is too customized so give it a try. Install Neon kernel and tweak settings as per your use using kernel auditor. This will solve battert drain issue.
Enjoy MIUI!
Click to expand...
Click to collapse
Is there any music bug with Neon??? Can you specify which build. And I'm presently in Xcelerate Build 7 with MiUi 6.7.7 is it better in neon+miui multi??
slst said:
Is there any music bug with Neon??? Can you specify which build. And I'm presently in Xcelerate Build 7 with MiUi 6.7.7 is it better in neon+miui multi??
Click to expand...
Click to collapse
No there's isn't any music bug any more. If you still face it then go through few comments on thread on neon kernel (you can get rid of it using kernel auditor). Its latest build of neon kernal and you can get miui 8 latest developer Multi rom here http://en.miui.com/thread-81385-1-1.html. Only issue is you will need to manually download complete package every week. If you don't need update weekly then you will get ota after each month.
I found that the neon kernel is the one which supports miui as well gets update frequently. Its been a long time that god's kernel or Xcelerate kernel were update so there base is still older than latest miui base.
IF you wanna enjoy miui then yes miui+neon is too good.
alok932 said:
No there's isn't any music bug any more. If you still face it then go through few comments on thread on neon kernel (you can get rid of it using kernel auditor). Its latest build of neon kernal and you can get miui 8 latest developer Multi rom here http://en.miui.com/thread-81385-1-1.html. Only issue is you will need to manually download complete package every week. If you don't need update weekly then you will get ota after each month.
I found that the neon kernel is the one which supports miui as well gets update frequently. Its been a long time that god's kernel or Xcelerate kernel were update so there base is still older than latest miui base.
IF you wanna enjoy miui then yes miui+neon is too good.
Click to expand...
Click to collapse
Thanks bro. Can i wipe system,cache(dalvik,cache), and flash the miui multi rom or should i clean wipe everything and flash this rom??
slst said:
Thanks bro. Can i wipe system,cache(dalvik,cache), and flash the miui multi rom or should i clean wipe everything and flash this rom??
Click to expand...
Click to collapse
You you can, you don't need to do clean wipe. If you wan to update to new version then you don't need to wipe system. Just select update package and install. Don't forget to wipe cache and dalvik cache after installing Rom or after updating. Enjoy!
alok932 said:
You you can, you don't need to do clean wipe. If you wan to update to new version then you don't need to wipe system. Just select update package and install. Don't forget to wipe cache and dalvik cache after installing Rom or after updating. Enjoy!
Click to expand...
Click to collapse
wats d overnight drain for u? im having 12% drain for 8 hours wit wifi on. (autostart 6 IMs,gmail)
slst said:
wats d overnight drain for u? im having 12% drain for 8 hours wit wifi on. (autostart 6 IMs,gmail)
Click to expand...
Click to collapse
As i checked now, last night it drained near to 8% or less, actually it totally depends on your settings. I set min cpu to 300mhz and max to 1305mhz and cpu governor to yankdemand. Also at night i enable miui's battery saver which doesn't allows apps to force start.
Yes you will to play and tweak a little bit as per your usage
alok932 said:
As i checked now, last night it drained near to 8% or less, actually it totally depends on your settings. I set min cpu to 300mhz and max to 1305mhz and cpu governor to yankdemand. Also at night i enable miui's battery saver which doesn't allows apps to force start.
Yes you will to play and tweak a little bit as per your usage
Click to expand...
Click to collapse
Using phantom beta kernel and powernap+greenify and my standby times got 2x better.
Buffcore oreo kernelSamsung Galaxy S4 i9505 (jfltexx)Release 02 - 11th June 2018
Code:
#include
/*
* Your warranty is now void.
* And other random stuff no-one reads.
*/
Intro
I had never intended releasing this as a stand alone, but had always been aware that it would work.
With BB and Side both being busy and AOSP and OptLos stalling for a bit, the kernel from RR-oreo should I think help a bit to alleviate users battery issues.
What is it?
Buffcore 2.04 - this is a fork of BB's AOSP 8.1 kernel with added fastcharge and battery saving features.
It is the kernel supplied with RR-o release 2, so isn't needed for RR users.
Code:
renamed to buffcore;
sdfat enabled;
fastcharge implemented for faster charging (up to 1900 ac / 1000 usb);
bcmhd wakelocks for rx and tx halved;
libmemcopy and libstring sped up;
io readahead to 1024k;
lower min cpu governor frequency (270);
power efficient work queues;
voltage tweaking user interface;
faster vmstat;
autosmp hotplugging replacement;
mmc crc disabled;
allow for lower cpu voltage;
reduce swapiness;
optimise divide / multiply by power of 2;
added tcp optimisation options,;
set westwood default;
force doze screen off helper;
optimise cbfillrect function;
reduce wifi wakelock times;
nohz: reduce overhead under high-freq idling patterns.
What rom is it for?
BB's AOSP oreo
Side's OptLos 15.1
Installation
Dirty (use with current rom flash)
Extract the boot.img file from the zip (It is not a flashable zip!).
Reboot rom into twrp.
Perform a nandroid backup to be safe, incase you need to go back.
Go into Install, then select Install Image for Buffcore kernel.
Reinstall your prefered root solution (Magisk, etc).
Do not wipe caches.
Reboot.
Clean (flash as part of clean install)
Extract the boot.img file from the zip (It is not a flashable zip!).
Reboot rom into twrp.
Perform a nandroid backup to be safe, incase you need to go back.
Perform clean recomended in your rom thread.
Install rom.
Go into Install, then select Install Image for Buffcore kernel.
Reinstall your prefered root solution (Magisk, etc)
Install Gapps.
Do not wipe caches.
Reboot.
Usage
Some features will need to be forced on (IF desired) and set to apply on boot with an app like Kernel Aduitor, EXKM etc. (Fastcharge, Min cpu frquency used, Power efficient work queues, Voltage tweaking, AutoSMP hotplugging).
This kernel should / will not be compatible with stweaks.
There will essentially be no support with this, if it works then it works, or doesn't.
If it helps you then it helps you, if it doesn't tough, don't moan about it.
It has had a little testing with the roms it is intended, boots fine and seems to provide some benefit.
This may not get updated either - see it as a stop gap for the moment.
Thanks
Thanks due to Drrossum, Kesaras, CR4IGY_BOY for testing for me.
BB for original kernel and Side and TsvietOK for picks.
Download
Download from AFH here BUFFcore-o-2.04-release02-20180611.zip
md5sum - d2293a1e623ddcc68946dbea7ea12869
XDA:DevDB Information
BUFFcore-o, Kernel for the Samsung Galaxy S4
Contributors
Buff99, side
Source Code: https://github.com/Buff99/platform_kernel_samsung_jf/tree/aosp-8.1
Kernel Special Features: Fastcharge, battery saving features
Version Information
Status: No Longer Updated
Created 2018-06-18
Last Updated 2018-09-13
Reserved
might as well have one, won't be writing much tho....
Very well done, master!
Perfect. I guess it's my new optlos main kernel
side said:
Perfect. I guess it's my new optlos main kernel
Click to expand...
Click to collapse
Of course, we work better and smarter together.
Since Kernels are/should be backward compatible, any reason why this shouldn't work with RR Marshmallow?
Thx!
<CuriousCat> said:
Since Kernels are/should be backward compatible, any reason why this shouldn't work with RR Marshmallow?
Thx!
Click to expand...
Click to collapse
Backwards compatibility with kernels? Not guaranteed that I know of.
When Oreo kernels use 64 bit binder, it locks out use with ROMs that don't have 64 bit binder defined.
You'd be better trying a sidecore kernel for nougat as an intermediate, if it works then try this. A kernel flash that doesn't work should be easy to recover from if have you stock one on hand ready to reflash. Remember that any mod / root that patches the kernel will need reflash.
SideCore kernel is a no go. A stock RR Nougat kernel also. Do you think some repacking with the boot.img of the RR Marshmallow would help?
<CuriousCat> said:
SideCore kernel is a no go. A stock RR Nougat kernel also. Do you think some repacking with the boot.img of the RR Marshmallow would help?
Click to expand...
Click to collapse
if they don't work, then this is a definite no-go.
I think RR marshmallow used the stock CM13.1 kernel, nothing was changed. Your viable choice would be anything cm13 compatible.
Syzrgy & Alucard spring to mind from back in the day.
Buff99 said:
if they don't work, then this is a definite no-go.
I think RR marshmallow used the stock CM13.1 kernel, nothing was changed. Your viable choice would be anything cm13 compatible.
Syzrgy & Alucard spring to mind from back in the day.
Click to expand...
Click to collapse
Alucard can't be found for MM and Synergy is very old (and not sure how stable).
Is there a way to take the (your/lineage) source and compile it to work with MM?
<CuriousCat> said:
Alucard can't be found for MM and Synergy is very old (and not sure how stable).
Is there a way to take the (your/lineage) source and compile it to work with MM?
Click to expand...
Click to collapse
just change the ramdisk using an image kitchen
side said:
just change the ramdisk using an image kitchen
Click to expand...
Click to collapse
I was thinking the same. Let me try.
Once repacked it boots but it's unstable. After running AnTuTu a few times it restarted every time. Not a good sign.
I flashed it several times on I9505 running the LOS15.1 and everytime I reboot after flash it shows the boot up screen with the phone model and then goes to Download mode. The fix for this non booting condition is to reflash the ROM.
Pecata01 said:
I flashed it several times on I9505 running the LOS15.1 and everytime I reboot after flash it shows the boot up screen with the phone model and then goes to Download mode. The fix for this non booting condition is to reflash the ROM.
Click to expand...
Click to collapse
Where is los15.1? Which rom u mean
I meant the Optimized Lineage OS 15.1 builds Version1 on which I tried to install BUFFcore-o rel02 kernel and it didn't work. But i flashed the Lineage OS 15.1 Version2 and it's all working. Good job
Is it possible to change the max frequency? Before compiling? Or manually with an root Explorer?
Just for fun
M4verick44 said:
Is it possible to change the max frequency? Before compiling? Or manually with an root Explorer?
Just for fun
Click to expand...
Click to collapse
aka overclock.
yes its possible.not suggested though.this thing is really advanced and i dont think that u will have nice results.wont be 'fun' at all
Can you add Boeffla Wakelock Blocker to this kernel? The Wi-Fi wakelocks are still annoying.
side said:
aka overclock.
yes its possible.not suggested though.this thing is really advanced and i dont think that u will have nice results.wont be 'fun' at all
Click to expand...
Click to collapse
Will you add over clocking to this kernel anytime soon? @side @Buff99?, maybe @ripee
---------- Post added at 05:34 PM ---------- Previous post was at 05:33 PM ----------
side said:
aka overclock.
yes its possible.not suggested though.this thing is really advanced and i dont think that u will have nice results.wont be 'fun' at all
Click to expand...
Click to collapse
Will you add over clocking to this kernel anytime soon? @side @Buff99?, maybe @ripee