Hey everyone! Got this thing on a super deal the other day ($50 brand new!) and couldn't pass it up. Naturally the first thing I want to do is tweak and mod it
To be completely honest, I didn't spend much time running stock on it to determine a baseline for battery/performance. I ran for a bit on kitkat and it seemed pretty laggy. With the mods I made it runs very smooth (for good reason, you'll see why).
Battery life seems on par with whatever everyone else is getting (on the short amount of research I did) http://i.imgur.com/vjefGL8.png
Check below to find out what version you should be running.
* download *
http://www.invisiblek.org/dory/kernel/
* install * -- must be OEM unlocked -- be sure to check your current version in settings and pick an image below that matches it
Download a zip from the link above and flash via TWRP (md5sums below)
OR
Download an img from above (md5sums below)
To flash:
Code:
adb reboot bootloader
fastboot flash boot <name of image file>
fastboot reboot
To test: (this doesn't actually flash it, just boots it to try out, simply reboot to get back to whatever kernel/ramdisk you have before)
Code:
adb reboot bootloader
fastboot boot <name of image file>
* changelog *
(img md5sum: 931830de150ca3c3ec83b8355c81abae)
v8 - 12/08/2016 - M1D64S
- [RAMDISK] Updated ramdisk from M1D64S
v7 - 11/16/2016 - M1D64K *** NOT COMPATIBLE WITH PRE-M1D64K ROMS ***
(img md5sum: b7879d15261d08920d0fb2445c08e03e)
- [RAMDISK] Updated ramdisk from M1D64K (so it actually boots with M1D64K). This will effectively make this image unusable on any build prior to M1D64K
- [KERNEL] Hack to force selinux in permissive mode in the kernel. This is necessary for mpdecision to work correctly
v6.1 - 02/22/2016 - MEC23G
(img md5sum: 04cf3b464be402fe3f393d94bb75066d)
- [RAMDISK] CPU governors set back to 'ondemand' until we get kernel source and can add custom governors
v6 - 02/22/2016 - MEC23G
(img md5sum: 96f4b59ea14dc9bf32966b602cffd72e)
- [KERNEL] Pure stock kernel image from google (we have to wait for kernel source)
- [RAMDISK] Merge in MEC23G ramdisk changes
- [RAMDISK] Remove install-recovery.sh service so twrp persists
- [RAMDISK] Fstab: support for either squashfs or ext4-formatted /system partition
- [RAMDISK] Added the necessary bits for systemless root (you can flash the SuperSU zip from Xmaster24's thread before or after the image)
v5 - 11/03/2015 - LCA43
(img md5sum: ab8b4d327682177bdfe984c0897696ff)
(zip md5sum: 02dedf601e47553ea87744cebc76019d)
- [KERNEL] Add adaptive low memory killer
- [RAMDISK] Enable adaptive low memory killer
v4 - 09-01-2015 - LCA43
(img md5sum: ce35db73d354c30b02b95feeaf0e8823)
(zip md5sum: cb6c08bfd1dcd2a12a7985d02fbfa8aa)
- [RAMDISK] Updates from LCA43
- [RAMDISK] Reverted to stock gpu governor/frequencies
v3 - 07-21-2015 - Never announced
(img md5sum: 81d2ee08e4ab2286c4062966a3041f34)
(zip md5sum: f09d69895fe1a47120b99350027690b8)
- [RAMDISK] Used msm-adreno-tz gpu governor and unlocked all frequencies. Never officially released because it wasn't tested too long and didn't really do much anyway.
v2 - 06-06-2015 - Initial 5.1.1 Release
(img md5sum: f5a6a61207968c31a2f0f6bcb84419b9)
(zip md5sum: 4bb6625a97e1ca11f0e03eeb355262b4)
- [KERNEL] Rebased v1 mods on aosp/android-msm-dory-3.10-lollipop-mr1-wear-release
- [RAMDISK] update to 5.1.1 ramdisk
- [RAMDISK] allow cpu to scale above 787mhz
v1 - 04-13-2015 - Initial 5.0.2 Release
(img md5sum: 127c036c629e0171ca64a4ea0b2e33f7)
(zip md5sum: e118f8f76a2b95685ae1e06a4588997f)
- [KERNEL] Based on latest aosp source
- [KERNEL] Compiled with Christopher83's linaro 4.9 toolchain
- [KERNEL] LZ4 compressed kernel
- [KERNEL] Couple MMC tweaks care of arter97
- [KERNEL] Disabled a bunch of debugging
- [KERNEL] maxwen's Smartmax Governor added and set as default after boot (performance gov while booting)
- [KERNEL] Increased vibe intensity care of arter97
- [KERNEL] Several misc security patches
- [RAMDISK] Enable all four cores and add mpdecision to hotplug them (see below for more info). mpdecision kanged from v4xx (g pad 7.0, same soc)
- [RAMDISK] Boot with Performance governor, all four cores and noop i/o scheduler (switch to smartmax/row/mpdecision after boot)
* mpdecision *
mpdecision is a daemon that runs on most (all?) qualcomm chips. Its job is to hotplug cores as they are needed. LG (or google?) forces cores 1-3 off on this device leaving just core 0 to fend for itself and no mpdecision to ever turn these other cores on. While this in theory should save battery life, it also makes your quadcore wrist computer run as a single core. I've taking the mpdecision daemon from the LG G Pad 7.0 (another device I own that has the same chip as the G Watch) and shoved it into the ramdisk so we can do hotplugging. You may ask: "won't this cause battery drain?". My answer is maybe. Since stock is forcing only one core usable, sure it seems like it would take less battery than being able to use all four, but what if everything you did on your device now takes 4 times as long (exaggeration, but say twice as long)? That, to me, could arguably cause more battery drain. In the end, I felt it was something worth trying, and from initial use I don't notice any major additional battery drain, plus the device runs buttery smooth. I've also added the smartmax cpu governor which should keep the frequency down and conserve battery life.
* source *
kernel: https://github.com/invisiblek/android_kernel_lge_dory/tree/invisiblek
ramdisk: https://github.com/invisiblek/dory_ramdisk
will flash in the a.m. glad to see work being done!
this is nice i have ben waiting for a kernel. im getting sick of the notificiation of update. so i was planing to return to stock. but now with a kernel ) yeah.
any one could make a easy noob installer? like the other rom/ kernel have?
So far kernel working great,
Thanks man for you work.
Sent from my SM-G900T using Tapatalk 2
Seems to run hot, also killed battery within only a few hours could be the mpdecision
This is awesome keep up the good work buddy
I'm just waiting on some more thoughts before trying this kernel as I use it extensively throughout the day and night. I have tried 4 cores with Gohma and noticed battery drain, however 2 cores worked great. If options for 2 & maybe 3 cores enabled were possible I would be very interested.
Moguledyouth said:
I'm just waiting on some more thoughts before trying this kernel as I use it extensively throughout the day and night. I have tried 4 cores with Gohma and noticed battery drain, however 2 cores worked great. If options for 2 & maybe 3 cores enabled were possible I would be very interested.
Click to expand...
Click to collapse
The thing is, with the kernel+mpdecision combo, you have 4 cores available, but they're only online if you need them. Just grabbed Gohma and it looks like he's forcing two cores on all the time, where even with the 4 cores available using my method, most often you're only going to have one online.
invisiblek said:
The thing is, with the kernel+mpdecision combo, you have 4 cores available, but they're only online if you need them. Just grabbed Gohma and it looks like he's forcing two cores on all the time, where even with the 4 cores available using my method, most often you're only going to have one online.
Click to expand...
Click to collapse
but would it be possible to have a version that has only 2 cores available? I am just curious if that would be possible, so that it's core1 on always and core2 comes on as necessary?
Moguledyouth said:
but would it be possible to have a version that has only 2 cores available? I am just curious if that would be possible, so that it's core1 on always and core2 comes on as necessary?
Click to expand...
Click to collapse
It probably is possible, but why would you want to? The watch will only use all four kernels when needed, and you likely aren't using your watch for any serious computing, so I doubt all four cores will be engaged for more than a second or two at a time.
Apoplectic1 said:
It probably is possible, but why would you want to? The watch will only use all four kernels when needed, and you likely aren't using your watch for any serious computing, so I doubt all four cores will be engaged for more than a second or two at a time.
Click to expand...
Click to collapse
Thanks for the info, I'll give this a shot tomorrow and put it through one of my average day's use and update here this weekend on my personal experience.
So I installed this kernel yesterday afternoon, I did notice a significant battery drain vs arter kernel. I use the tilt to wake feature and noticed that with this kernel the slightest arm movement was turning the screen on thus draining the battery faster.
More disturbingly, I now have found this morning that I can no longer connect to my watch through adb at all. I am still trying to figure out if I can get this back to any state where I can even connect to my watch at this point!
**Update** I was able to get back into fastboot mode manually using the pinout method, which enabled me to install the arter97 kernel again. After a reboot my watch connected to my computer as it normally should and adb registered my device again.
On the tilt to wake constant false responses, I know this sounds strange, but could this kernel be too fast and that is why it is turning on as much as it is or maybe some values can be changed to alter that? I'm not a developer by any means, so I do not know what is and isn't controlled or can be manipulated directly in the kernel. Also I'm not sure what needs to be fixed in the kernel to get proper adb support, but at least for me, the arter97 kernel has it but this one seems to need something.
Moguledyouth said:
More disturbingly, I now have found this morning that I can no longer connect to my watch through adb at all. I am still trying to figure out if I can get this back to any state where I can even connect to my watch at this point!
Click to expand...
Click to collapse
odd. i am able to connect via ADB with no problem.
drewski_1 said:
odd. i am able to connect via ADB with no problem.
Click to expand...
Click to collapse
Same here
Sent from my SM-G900T using Tapatalk 2
Hey, this seems interesting and promising! And since Ghoma does not update his ROM in the near future from what I heard (sadly) I hope this will be a great replacement.
I'll report how it went in a few days if I'm not so stupid to forget about this ;P (I know myself far too well, heh)
Awsome kernel man, i gat 3.5 days
Battery life is good man thanks for this gift.
Sent from my SM-G900T using Tapatalk 2
gavilan2010 said:
Awsome kernel man, i gat 3.5 days
Battery life is good man thanks for this gift.
Sent from my SM-G900T using Tapatalk 2
Click to expand...
Click to collapse
What are some of your settings for your watch (such as always on or tilt to wake)?
lyrical1278 said:
What are some of your settings for your watch (such as always on or tilt to wake)?
Click to expand...
Click to collapse
Screen off tilt to wake...yup yup
Sent from my SM-G900T using Tapatalk 2
For some reason when having this kernel installed and using the latest version of the Android Wear app on your smartphone new apps won't sync to the watch.
I now restored to stock with the Restore Tool and now it'll sync again but is laggy as hell again
EpicLPer said:
For some reason when having this kernel installed and using the latest version of the Android Wear app on your smartphone new apps won't sync to the watch.
I now restored to stock with the Restore Tool and now it'll sync again but is laggy as hell again
Click to expand...
Click to collapse
Yeah it does sync, but now u dont have the notification on your pull down notification background saying smartwatch is connected. U can open android wear and u will see is connected.
Sent from my SM-G900T using Tapatalk 2
Related
Google just moved out the 2.6.32 kernel from the experimental git repo to the msm repo. This means that google thinks they are stable now.
There are currently two 32 branches:
android-msm-2.6.32-nexusonec
http://android.git.kernel.org/?p=kernel/msm.git;a=shortlog;h=refs/heads/android-msm-2.6.32-nexusonec
android-msm-2.6.32
http://android.git.kernel.org/?p=kernel/msm.git;a=shortlog;h=refs/heads/android-msm-2.6.32
I've compiled both and I'm finding the nexusonec branch more stable than the 32 branch. The 32 branch causes issues with the gallery and camera app not recognizing the sd card. Everything seems to work fine in the nexusonec branch (sdcard, wifi, BT, camera, etc). Speed is definitely faster than 29.
For those who are interesting in flashing the 32 zimage, they can d/l it here:
http://drop.io/xdp6104#
Right now the kernel is just a stock config, meaning no tethering or anything else. Only change I've made from stock is to use the deadline I/O scheduler. I'm sure cyanogen will add those other goodies when he releases a new version.
Very nice: cant wait for a Enomther rom with this new Kernel
nice....
ive compiled a nice cyanogen kernel 2.6.32 already
just need to get the wifi module compiled correctly and we are gtg!
Does this mean that they've fixed some of the power saving regressions people were seeing with 2.6.32 before?
Installed on my Nexus with enomther 1.61: works nicely
Tot mem 395448K, Free 265916K
Does this still have the charging issue that blocks the battery to charge when it goes under 90%...???
eug89 said:
Does this still have the charging issue that blocks the battery to charge when it goes under 90%...???
Click to expand...
Click to collapse
86% now and charging..
eug89 said:
Does this still have the charging issue that blocks the battery to charge when it goes under 90%...???
Click to expand...
Click to collapse
It wasn't an issue per-se it was a 'feature'
The problem was caused by downgrading to older kernels after using 2.6.32. Certain hardware states that were set by the new kernel telling the battery not to charge weren't being un-set by the new kernel, and the older kernel didn't even know about them. They patched the newer kernel pretty quickly after getting feedback so that it removes the hardware state when shutting down, I believe. So, yes, it's 'fixed'
FettsVett said:
It wasn't an issue per-se it was a 'feature'
The problem was caused by downgrading to older kernels after using 2.6.32. Certain hardware states that were set by the new kernel telling the battery not to charge weren't being un-set by the new kernel, and the older kernel didn't even know about them. They patched the newer kernel pretty quickly after getting feedback so that it removes the hardware state when shutting down, I believe. So, yes, it's 'fixed'
Click to expand...
Click to collapse
Thanks, i called it issue because i didn't know how to call it but i knew that it was meant to be a sort of new feature of the 2..6.32 kernel and I wanted to write above 90% and not under 90%... did a bit of a mess
woahhh its way faster
thanks dwang
will do some thorough testing and post back soon.
edit: Hmmm having some trouble with fastboot... unable to push wifi via adb?
anyone else encountering this?
Are you trying to push the ko module on fastboot mode?
This kernel is FAST and SNAPPY! HIGHLY RECOMMENDED!
boqonx said:
Are you trying to push the ko module on fastboot mode?
This kernel is FAST and SNAPPY! HIGHLY RECOMMENDED!
Click to expand...
Click to collapse
yeah. iirc thats where you do it right?
Let the OS run, then push through adb. Can't do it when it's on recovery either because the /system/lib is not mounted. Wifi should work even without a restart.
yep just did that
i think i was just confused on where to use adb
it still works so all good. this kernel is zippy.
Damn right This thing flies now! Scrolling through messages is MUCH smoother. Seen a lot of tearing when scrolling on CM's kernel.
I released my undervolted version of CM's in the other thread. He changed the scheduler from anticipatory to deadline as well.
Will try! Had any reports on instabilities yet?
Dwang: great job on the deadline scheduler suggestion. It really does make the whole experience smoother.
Can someone write the exact adb command to push it?
Code:
adb remount
adb push ./bcm4329.ko /system/lib/modules
himmatwala said:
Can someone write the exact adb command to push it?
Click to expand...
Click to collapse
Hi.
I'm facing a "hard to solve" issue with my Atrix 4G...
It is a non-ATT (international). Using RSD Lite, I flashed the Retail SBF and it worked OK, battery life was "normal" and the phone was cold most of time.
I then unlocked the bootloader flashing the IHOP SBF then using moto_fastboot method. Installed Clockworkmod Recovery and flashed the HomeBase rom with the updates.
What happen is: The phone starts to get very warm and the battery is drained very quickly (couple of hours).
Using the SetCPU, I could verify that the CPU does not scale down automatically. It's always at 1300Mhz, it doesn't matter if the phone is idle or not.
I can reduce the CPU speed using the SetCPU but the processor is with the two cores active all the time and it never reduces the speed below the limit set in SetCPU.
I thought it may be a problem with my phone, so I flashed the retail SBF again and I could verify that, bakc with the retail rom, CPU is scaling down correctly. It goes up to 1000Mhz when requested but stays ~300Mhz when phone is idle.
I did the BL unlock/motofastboot/clockwordmod/ procedure again and tried with different roms (Aura, Alien, RedPill, etc) always cleaning up the Cache/UserData/Dalvik and using the faux 1.3Ghz unified kernel but got no result, on every 2.3.4 rom I flash, the CPU is always at the maximum speed set by the kernel or limited by the SetCPU.
I've found a similar problem on this thread: http://forum.xda-developers.com/showthread.php?t=1190634. and did the same investigation but I was not able to identify any aplication that is making the CPU usage to be constantly high (even tried killing all Apps, not result).
Any ideas what I can do/try to solve this issue?
Thanks a lot.
That happened to me too!! I just reflash the rom wiping everything and the cpu started acting normal
Try to use fastboot to wipe if ur using CWM
Sent from my CM7 Motorola Atrix 4G
For me turning off the phone and back on worked, if not for you then try wiping the usual stuff before reflashing a rom or back up
Feom what I've seen, this is often caused by the webtop. Most ROMs don't touch the webtop, and it seems for some people, this causes problems. I fixed my issue by installing a ROM that (I believe) wiped the webtop. That ROM was deprecated a long time ago so I don't know if it's still available. I'd take a look at the Developer forum. There are some webtop files you can download that reportedly fix the issue. You might also try using fastboot to erase the webtop.
Sent from my MB860 using XDA App
@vibrantuser
Thanks. Yes, I tried flashing and re-flashing couple of times, no luck whatsoever...
@Ilkinansr92
Thanks for the tip. Will try that and see how it goes.
@ronii1123
Will try that this weekend I'll report about progress.
@frelnik
Thanks for the tip. It makes sense as the retail SBF re-flashed the Webtop area and all roms I tried doesn't touch it. I'll try to get a webtop image and flash it using the fastboot or the CWM method. If you can point a link to any that may work, I'll really appreciate it.
Thanks a lot.
I installed the ROM from here to fix my issues. Every ROM thereafter was fine:
http://briefmobile.com/download-android-2-3-4-gingerbread-for-motorola-atrix-4g
I believe I've heard some people had success with the webtop CWM from here:
http://forum.xda-developers.com/showthread.php?t=1169457
I do wonder if erasing the webtop would be enough. You could try
fastboot erase webtop
faux123 said:
Just a quick Info dump:
Just going through the code and realized why SetCPU failed to keep the clock frequencies set properly. SetCPU has NOT been designed to work with dual core properly. It only sets the scaling_max_frequency for cpu0 (master CPU) and not for cpu1 (slave). When under load, cpu1 gets awaken by the system, but it's frequencies are still the old 1.3 GHz and since Tegra2 is a synchronous SMP design, the scaler would use the highest frequency again (this case 1.3 GHz). This is why after playing games, or apps that needed the 2nd cpu would cause the system clock to revert to original default 1.3 GHz even when you set it via SetCPU to something lower.
This is not easy to fix, when SMP is involved. I have tried a few hax already and still unable to tame the 2 headed beast. I will continue to work on it or find an alternative solution to SetCPU's issues
Click to expand...
Click to collapse
quoted from Faux himself, there's a bug in his kernel that prevents us from underclocking it. should be fixed in the next release.
Alcapone263 said:
quoted from Faux himself, there's a bug in his kernel that prevents us from underclocking it. should be fixed in the next release.
Click to expand...
Click to collapse
That's a separate problem, I think. My understanding is that the OP's issue is the CPU is always running at the maximum speed. It never clocks down to the slower speeds when idle. The issue with Faux's kernel and SetCPU is that no matter how you set it, when stressed, the CPU runs at the maximum speed the kernel is capable of, not the speed you set in the app. The CPU does clock down when idle, but will ramp up to 1.3 GHz even if you set it to only 1 GHz in SetCPU. I've experienced both issues.
You have to set it at 800 mhz for it to stick. For some reason setcpu only recognizes under clocking under 1 GHz, otherwise it presumes that it's running at the 1 GHz stock speed without registering the overclock, therefore thinking the stock is 1.3 GHz! I'm not sure but I would have a guess and say that it's something to do with the unchangeable governors? Hope this makes sense lol
Sent from my OC Atrix running homebase 4.7, simplicity themed using xda premium
[SOLVED] CPU not Stepping Down - Warm Phone
frelnik said:
I installed the ROM from here to fix my issues. Every ROM thereafter was fine:
http://briefmobile.com/download-android-2-3-4-gingerbread-for-motorola-atrix-4g
I believe I've heard some people had success with the webtop CWM from here:
http://forum.xda-developers.com/showthread.php?t=1169457
I do wonder if erasing the webtop would be enough. You could try
fastboot erase webtop
Click to expand...
Click to collapse
Hey freinik.
I cleaned up the webtop and reflashed the Home Base rom I was using.
Perfect!
CPU is now scaling correctly. Your suggestions was exactly what was needed.
After cleaning the webtop (using the fastboot erase webtop) the issue was solved.
Thanks a lot.
Think in having the same issue with my international atrix alien rom.
Can you provide clear instructions on how to remove webtop and what will it affect if any by removing it?
Hope you can help.
Sent from my mobile
@ultim
Hi, Thanks for asking.
I erased my webtop using the moto fastboot command line, you can get it here:
http://forum.xda-developers.com/showthread.php?t=1138092&highlight=fastboot
After installing, reboot you phone and enter the "fastboot" mode (holding volume down until the "fastboot" text appears, then press volume up.
Once on fastboot mode, connect your phone to the USB port and run:
moto_fastboot erase webtop
It should erase your webtop partition.
It normaly helps to clean the cache/data, you can do that by running:
moto_fastboot -w
You can then, reboot the phone.
moto_fastboot reboot
If you're using Linux, moto_fastboot should be run as superuser, you can do that by using sudo, ie. sudo moto_fastboot reboot.
Hope this helps.
@Nyx_ Thank you for the instructions. My battery life is so much better now. Before application 'X' (i assume its webtop) would use about a third of my battery all the time.
Thanks for this. I recently discovered the same thing was happening to my phone and deduced that the webtop was causing this. I was using faux's newest kernel. I then related the stock kennel and everything was file after that, no cleaning of the webtop was needed.
Sent from my MB860 using xda premium
Ok I tried some new roms and started noticing a pattern in that BLN was behaving erratic.
By erratic I mean this.
If I set the LED's to stay on, they will turn on but then raondomly go off for a second or so and then come back on again, there was no pattern except it took longer to happen after a phone reboot and when the usb plugged in from pc.
If I set them to blink and I set the off period for longer than 4 seconds, then after they go off for the first or send time then after just 1 second they come back on again but only if I set the off to more than 4 seconds, weird.
In these cases was testing on freshly installed roms with wiped user data.
One of the roms was based on stock which made this even stranger as BLN works 100% perfect on stock rom with cf-root, the rom was based on cf-root b84 so I chanced it to downgrade it to cf-root b82 and bam BLN fixed.
So the issue is down to a fubar kernel.
Now CM's stock rom doesnt support BLN, so on the CM roms I was using the blackhawk rom which has the exact same symptons as cf-root b84, seems only cf-root b82 works properly.
Here is the changelog for cf-root b83 and b84.
CF-Root-S5830-v3.7-b84.zip (12.55 MB)
BUGFIX: Invisible boot animation.
Install CF-Root-S5830-v3.7-b84.zip via "CWM recovery" first and then install b84-fixed.zip via "CWM Manager - Flash kernel"!
CF-Root-S5830-v3.7-b83.zip (12.38 MB)
- Untested since on CyanogenMod 7.2 firmware for now
- Using b82 recovery image
- CPU and system bus overclock enabled
- GPU driver backported from 2.6.35-11 kernel source
- interactive, interactiveX, smart*ss, and smart*ssV2 governor
- Samsung on the fly governor setting disabled
- WiFi driver taken from DXKPD
Click to expand...
Click to collapse
I dont have b83 but am about to flash mythICS which is based on b83, my gut guess is the bug was introduced in b83 as b84 only has a tiny changelog.
What I am asking is if someone can either do me a kernel for CM based on the above information (so dont include new GP driver, dont disable on the fly governor, dnt add new wifi driver) and see if the result is a fixed kernel, or if anyone has instructions on how to build my own kernel based on CM's sources.
I dont really need a new kernel for stock based roms as I can just downgrade to b82 cf-root to fix them.
Also is this better in dev section or here?
confirmed b83 is indeed borked and b82 also fixed on mythICS.
So I need a b82 for CM
Hello friends. So I am officially stumped. I have an issue with my kernel bootlooping. The interesting thing is, eventually it boots. After about 5-10 minutes of bootloop, it just boots. Weird right?
See, I merged a lot of code with my kernel and I'm not sure what is causing the bootloop. Here is my source: https://github.com/Snepsts/kernel_e980
It started on the add intelli-plug commit (which also includes intelli-thermal) it is probably important to mention disabling intelli-plug and thermal (and only one of each) all have the same outcome. I have also tried wiping the board back to its original state. I'm assuming its one of the core changes or nr_running changes. But I cannot find any way to get a log of the issue as it is not in a stable state during bootloop to give me logs from adb. I also cannot compile intelli-plug without the changes I made. And I really want to have it. I have looked for code I may be missing but cannot find any. I have made many different test kernels and taken the ramdisk and config from the latest official cm build for my device. Does anybody have any ideas? If you need anymore info please let me know. Thanks for any help in advance.
Sent from my LG-E980 running Carbon KitKat & E980 Kernel+
LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Wiki.
Important Info
DON'T USE TWRP 3.0.2-0 OR OLDER WITH LINEAGEOS. IT DOES NOT WORK CORRECTLY. USE VERSION 3.2.1.0 HERE
Current lineage 15.1 shamu nightlies are based on the N6F27M October 2017 update from google.
So you should be using the radio and bootloader img from that update.
If you already have those you don't need to flash them again.
They can be extracted from the factory image on google's site here.
Or you can use the ones linked below that I already extracted:
radio-shamu-d4.01-9625-05.45+fsg-9625-02.117.img
bootloader-shamu-moto-apq8084-72.04.img
IMPORTANT NOTE FOR VERIZON USERS: Google released a separate October 2017 security update (NGI77B) just for verizon users that has a different radio. So you'll want to flash it. I repeat, THIS RADIO IS JUST FOR VERIZON USERS.
radio-shamu-d4.01-9625-05.51+fsg-9625-02.118.img
You can use fastboot to flash the bootloader and radio.
More information and installation instructions can be found on the LineageOS wiki here.
Download Links
LineageOS OFFICIAL: https://download.lineageos.org/shamu
As you will see it is no longer available and there will be no new OFFICIAL builds as shamu has been promoted to LineageOS 18.1.
Seems an archive of the official 15.1 builds is here. To check official signature you can follow this guide
LineageOS UNOFFICIAL: lineage-15.1-20220301-UNOFFICIAL-shamu.zip
Includes the now (no longer official from now on as per comments here) non official February 2022 security bulletins.
Here is its md5sum.
Google apps: MindTheGapps or OpenGAPPS <= nano
HEADS UP:
When you initially install LineageOS, be sure you flash the gapps package with your ROM. If you boot your ROM, then go back and try to flash gapps after, you're gonna have a bad time.
If you are migrating from an OFFICIAL build to the UNOFFICIAL build you have 2 options:
Wipe data and do a clean install of UNOFFICIAL build
Dirty flash thanks to an intermediate MIGRATION build
First flash the MIGRATION build (lineage-15.1-20200501-MIGRATION-shamu.zip md5sum), boot to it and then flash the UNOFFICIAL build and boot to it.
SU addon zip: Addon Install zip / Addon Removal zip
NOTE: LineageOS does not come with root, so this is now provided for those that want it.
The install zip is a one time flash, like gapps.
Meaning, it persists when updating to a new LineageOS nightly.
Changelog
Builddate: 2018.07.17
Changes:
[new] Full featured, binderized power HAL with support for following power profiles:
- Power save => Maximum of 2 cores online, max. freq limited to 1,036 GHz
- Bias power => Up to 4 cores online, max. freq limited to 1,036 GHz
- Balanced => Up to 4 cores online, no freq limits
- Bias performance => Up to 4 cores online, min freq limited to 1,19 GHz
- Performance => 4 cores online always at 2,6 GHz
[new] Core hotplugging through new mpdecision
Known Issues:
[bug] Trusted voice is not working and probably never will
[bug] TWRP is not able do decrypt your data if you encrypted it with lineage-15.1
[bug] Not every app is compatible with the expanded desctop feature. If you have ranndom problems to turn on your device
disable expanded desktop for the app
Older Changelogs:
Builddate: 2018.06.19
Changes:
[new] Full RGB brightness support
Builddate: 2018.06.12
Changes:
[new] LineageOS's Trust
[new] Spectre V1 patches
[new] june security fixes
[fix unconfirmed] Camera app 'missing' on some devices
Builddate: 2018.05.28
Changes:
[new] Option to check proximity sensor before device is woken up with dt2w
[new] Stereo recording in all available formats
[fix] DRM is now L1
[fix] SU hiding is now working properly
Builddate: 2018.05.21
Changes:
[new] New BT power management driver with less wakelocks
Builddate: 2018.04.30
Changes:
[new] Stereo recording
[new] Ability to edit apn regardless of carrier
Builddate: 2018.04.23
Changes:
[fixed] DRM now working on L3
Builddate: 2018.04.16
Changes:
[fixed] Netflix not working: DRM issue
[fixed] Camcorder audio too low
[new] Get rid of forceencryption
[new] BCL not turning of core 2 and 3 at ~40 % battery anymore
We're limiting the max frequency instead
Builddate: 2018.04.12
Changes:
[fixed] Double touch to wake
[fixed] Power HAL loading
[fixed] Vendor image mismatch notification popping up every boot
[new] Optimized boot latemounting of data and cache
Known Issues:
[bug] Netflix not working: DRM issue
[bug] Camcorder audio too low
[bug] Trusted voice is not working and probably never will
Builddate: 2018.04.02
Known Issues:
[bug] Vendor image mismatch notification popping up every boot. Just ignore it
[bug] touch to wake is not working
[bug] Trusted voice is not working and probably never will
XDA:DevDB Information
LineageOS, ROM for the Nexus 6
Contributors
Elektroschmock, Elektroschmock, dwardo
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
Version Information
Status: Nightly
Created 2018-04-04
Last Updated 2020-11-14
Thank you for your support...
I am getting this message on every reboot https://ibb.co/gUBVux
I have downloaded N6F27M from google but there is no vendor.img in the zip file
aqatramiz said:
Thank you for your support...
I am getting this message on every reboot https://ibb.co/gUBVux
I have downloaded N6F27M from google but there is no vendor.img in the zip file
Click to expand...
Click to collapse
It's nothing you should worry about...just ignore it.
It will be fixed with the next nightly.
You might want to add the info about "vendor image" + "counterfeit april fools joke" + "double tap 2 wake not working yet" + into the op under known issues or something. I see those questions posted over and over again in the old thread and other communities
People should use TWRP 3.2.1.0 with LOS 15.1
https://dl.twrp.me/shamu/
First of all, thank you very much. I'm using my Nexus 6 only as a secondary device but I'm happy to upgrade it to LineageOS 15.1 now
Does it support FBE or direct boot? I'm already running LOS 14.1 and not quite sure if encryption changes upon a data wipe
While on a phone call adding another call, then merging the two results in dropping both lines.
Install:
Wiped, lineage-15.1-20180402-nightly-shamu-signed.zip, opengapps super, magisk.
Logcat: https://drive.google.com/file/d/1XQbvCKna63HG1rPdNP3VoBXwznAxEaib/view?usp=drivesdk
never mind
mugendon said:
Yap, just what the op says in red letters
Click to expand...
Click to collapse
What I meant is advice people from beginning ro use 3.2.1.0 because there are in between version too.
Is the SU addon zip coming anytime soon?
You can get 'double tap to wake' working if you enable it via something like EX Kernel Manager.
Sent from my Nexus 6 using XDA Labs
---------- Post added at 01:44 PM ---------- Previous post was at 01:38 PM ----------
rodritoledo94 said:
Is the SU addon zip coming anytime soon?
Click to expand...
Click to collapse
https://forum.xda-developers.com/ne...om-cm14-1-nexus-6-shamu-t3514362/post76101587
Also, Magisk works great on this ROM.
Sent from my Nexus 6 using XDA Labs
someone is experiencing a problem with huge battery drain via Google Play Services?
i have clean install with full wipe (installed factory image -> twrp -> full wipe -> LOS 15.1 + OpenGapps)
and 2nd problem is strange "beep" after incoming/outgoing phone call
Running perfectly (using opengapps nano and magisk 16.1).
- Had one reboot 48hrs ago and nothing since.
- Some lag in a couple spots, but may still be settling in.
- Netflix, you have to roll back to v4.6.
- Battery drain is identical to 14.1 for me (edit: Meaning no bad drain at all...it's ideal)
- Had some minor signal issue with cell calls in spots that are normally good, but that could be weather/sunspots/aliens.
- Had no issue removing the LOScoins alert.
rodritoledo94 said:
Is the SU addon zip coming anytime soon?
Click to expand...
Click to collapse
It's better to use Magisk on Android 8+.
Lagarde said:
Running perfectly (using opengapps nano and magisk 16.1).
- Had one reboot 48hrs ago and nothing since.
- Some lag in a couple spots, but may still be settling in.
- Netflix, you have to roll back to v4.6.
- Battery drain is identical to 14.1 for me
- Had some minor signal issue with cell calls in spots that are normally good, but that could be weather/sunspots/aliens.
- Had no issue removing the LOScoins alert.
Click to expand...
Click to collapse
Using micro, everything is working great.
...
Another report for all good. I upgraded from the latest 14.1 nightly: Updated TWRP; Wiped system, dalvik, cache; flashed 15.1 nightly and then mind_the_gapps; boot once, then reboot to TWRP and flash Magisk. Apps all still work; all good! Thanks for the great build!
Been using this for 2 days now. A couple of issues:
Biggest issue is Netflix issue. Also heard YouTube TV isn't working, but I haven't had the opportunity to test it.
Stutters when unlocking. Also when switching between apps using the multitask button (or whatever it's called).
I haven't run into any other problems (outside the ones listed in OP).
ExpectedCrayon said:
Been using this for 2 days now. A couple of issues:
Biggest issue is Netflix issue. Also heard YouTube TV isn't working, but I haven't had the opportunity to test it.
Stutters when unlocking. Also when switching between apps using the multitask button (or whatever it's called).
I haven't run into any other problems (outside the ones listed in OP).
Click to expand...
Click to collapse
This is because DRM Widevine L1 or L3 hasn't been implemented yet. Other Oreo Roms have however. Netflix and YouTube check for this now.
Any suggested kernel for the Lineage 15.1?
My phone started stuttering (As per CPU-z it looked like two cores were offline when the battery was low) and I thought of trying PureZ Kernel 5.2, but with that my phone got stuck at the boot logo for hours. Reinstalled Lineage 15.1 to fix that and wanted to check with others before trying a new Kernel.
wavedashdoc said:
This is because DRM Widevine L1 or L3 hasn't been implemented yet. Other Oreo Roms have however. Netflix and YouTube check for this now.
Click to expand...
Click to collapse
Do you know if there are plans to implement it?
---------- Post added at 05:43 PM ---------- Previous post was at 05:41 PM ----------
manish_bhaumik said:
Any suggested kernel for the Lineage 15.1?
My phone started stuttering (As per CPU-z it looked like two cores were offline when the battery was low) and I thought of trying PureZ Kernel 5.2, but with that my phone got stuck at the boot logo for hours. Reinstalled Lineage 15.1 to fix that and wanted to check with others before trying a new Kernel.
Click to expand...
Click to collapse
I'm waiting for Franco Kernel. There isn't an Oreo version yet, but the dev said he intends to make a version for Lineage 15.1 Shamu on his Google + a few days ago.