yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] FexusPexus:
Learning as I go along... this is what Ive found so far, via adb LogCat (not sure if it relates but mentions errors for sensors and this block keeps repeating)

04-30 12:30:34.326 19272 19276 E Sensors : mag_cal.c(1603):mag_cal_sam_init: Unknown UUID(1) 61c69537-9675-40c1

04-30 12:30:34.326 19272 19276 E Sensors : mag_cal.c(1608):mag_cal_sam_init: Unknown UUID(2) bc46-fd1b43b8250b

04-30 12:30:34.326 19272 19276 E Sensors : sns_sam.c(4395):Failed to register algorithm service 16 with SAM

04-30 12:30:34.377 19272 19291 E Sensors : sns_debug_main.c(436): Debug Config File missing in EFS!

04-30 12:30:34.395 19272 19272 E Sensors : sns_init_la.c(239):Error 5 initializing sns_file_init

04-30 12:30:34.395 19272 19272 E Sensors : sns_main.c(1692):Exiting! sensor1_init failed with 5

04-30 12:30:35.669 672 3180 E SensorService: Error activating sensor 77 (Operation not permitted)
[Nexus 6  Original Android Development] esysfound:
More on Battery drain - I had to reinstall my Here maps app and about 2 GB of map data, done over my home WiFi where router is about 3 m away.

All that took about 10 minutes and drained almost 30% off my battery. Really curious if any others noticing this.
[Nexus 6  Original Android Development] SteveYoungs:
No Bluetooth audio in phone calls.

I have seen others in this thread mentioning that they are having problems with Bluetooth audio during phone calls. Like, the party at the other end can hear fine but on the Shamu end there is no audio. I'm getting that too. It only affects phone calls, things like whatsapp or duo or Messenger are all OK. Sadly for me is that 99.9% of calls I make and receive are normal phone calls with the majority of those happening in the car where Bluetooth is essential. So... a fairly critical bug for my use case.

What I haven't been able to find is any solutions. Does anyone know of a fix?

I'm the meantime I'll try to remember how to get a logcat and take one during a call. It's gotta be something simple like an audio stream not getting redirected to the right device.
[Nexus 6  Original Android Development] Sanabil:
Installed latest nightly, pixel launcher stopped working, it was working before. Now I'm using rootless launcher. It's working fine.

Ocassional stutter when swipe to right on launcher but overall navigating between apps and general usage feels a lot smooth now!:svetius:
[Nexus 6  Original Android Development] xuxu1:
[MENTION=7322060]SteveYoungs[/MENTION]

Did u tried to disable voice match? (in Google App)
[Nexus 6  Original Android Development] FexusPexus:
Hi all, so I might be wrong but I think my `/persist/sensors/sns.reg` binary file might be corrupted. Would anyone be able to assist me via doing an adb pull of their working file and sending it to me to try?
[Nexus 6  Original Android Development] maddog3030:
[MENTION=3383960]Elektroschmock[/MENTION] maybe I missed something but why were all the nightlies pulled from the download page all the way up to the 24th's?

If you have copies of these should they be discarded?
[Nexus 6  Original Android Development] dvdram:
I am not sure if this is related in any way, but there are several options dealing with BT in the developers options section. I came across those options when I needed to make my car radio show information about the music being played and the number of an incoming calls. The standard options did not work with my car radio. It took me half a dozen tries, but finally I got it to work.

By the way...
[MENTION=3383960]Elektroschmock[/MENTION]: did I really have to reboot the phone after each change in that section, like I did, or would a warm reboot have done as well, or should those changes have worked instantly? Would be nice to know for next time... ;)
[Nexus 6  Original Android Development] ChubbsMcBeef:
Thanks so much, [MENTION=3383960]Elektroschmock[/MENTION] for this awesome ROM! First time in a lonnnnngggg time that I've rooted a phone... (last time was using my old Samsung Galaxy Nexus back in 2014!)

24+ hrs now and going great on Nightly 20200429.

I can confirm that the above method worked for me in getting both the camera and flashlight to work. :o:good: Cheers!

This is the only thing I'm bummed out about... that, plus Netflix not working :silly::eek:

I plugged my phone into my Android Auto head unit, no audio on my end but receiving end could hear me fine on a standard call. WhatsApp / Messenger call worked fine though :confused:

Any thoughts?

Thanks again!
[Nexus 6  Original Android Development] SteveYoungs:
OK, that actually worked. Thank you very much! The down side, of course, is that you can't activate GA via voice anymore. I use GA a lot but I think I can live with this workaround until the bug has a real fix.

Thanks again for the suggestion!
[Nexus 6  Original Android Development] xuxu1:
[MENTION=7322060]SteveYoungs[/MENTION]

No Problem. :)

Many custom roms have this bug. Even xiaomi.eu roms which are "just" a modification of official xiaomi MIUI. So I think its hard to fix. :/
[Nexus 6  Original Android Development] SteveYoungs:
I had a good look through those and didn't see anything that might be related. Lost count of the different combinations of those tweaks I tried... None helped, wasn't surprised. ☺

To my mind, the problem is either the incoming media stream is not being directed to the right audio device, or something is blocking the audio device. I just now read a suggestion here to turn off voice match (GA) and that works so I think it is the latter... Audio device is blocked. (could be that GA is using the wrong media stream).

I'm keeping my fingers crossed that this is fixable from the LineageOS side because it is feasible that it may not be.
[Nexus 6  Original Android Development] mrk2815:
i dont get why lineage is draining more battery then any other android 10 rom that i have tried.literally in 10 minute of installing apps its basically dropped 30%. i started with a full charge installed lineage 17.1 may 1 build, to se what would happen an the battery drain started.i ddid not se the drain issue on any other androi 10 rom except for lineage. what gives.
[Nexus 6  Original Android Development] pinakini:
Bluetooth call is very important for me, since I use only phone app for calling. Thanks for the workaround. Disabling GA voice worked for me. A huge thanks.
[Nexus 6  Original Android Development] Sanabil:
For some reason i cannot use the multitasking button. Home and navigation key works fine. Ive wiped dalvic etc but nothing seems to fix it. Have tried multiple launchers too.

Is anyone experiencing this too?

Thanks
[Nexus 6  Original Android Development] ChubbsMcBeef:
Hey Sanabil! Try this sequence:

1. Hold the Multitask button down for about a second, or until the button changes.

2. Tap the Home button. The app window should reveal the Home screen below with the app still partially appearing at the top of the screen.

3. Tap the Multitask button to show the list of currently open apps.

4. Tap the app you want to appear at the bottom half of the screen.

5. Voila! You're now in split-screen mode.

Hope that works for you! :D:good:

---------- Post added at 08:44 PM ---------- Previous post was at 08:38 PM ----------

Thanks, [MENTION=6032361]xuxu1[/MENTION] – this worked for me also! :D:good:
[Nexus 6  Original Android Development] McMannes:
Netflix is work on your devices? i cant open
[Nexus 6  Original Android Development] ChubbsMcBeef:
Unfortunately Netflix uses something called "Widevine DRM" which restricts use of the app on devices with an unlocked bootloader / custom ROM, etc.

I'm not aware of any fix for this, but hopefully there's some kind of workaround?... anyone?
[Nexus 6  Original Android Development] githyanki:
The magisk module liboemcrypto disabler.
[Nexus 6  Original Android Development] phimeas:
Had the cellular data not working problem, too

Hi there,

after initial clean flashing the first official version of the 17.1 ROM to my Nexus 6 the cellular data connection did not come up for me, too. Flashing one of the first nightlies a few days later fixed it for the next weeks. After flashing the 20200423-nightly cellular data was gone again. Yesterday I flashed nightly 20200502 and voila, cellular data connection was there again. Until I rebooted to flash latest magisk (done by sideload from TWRP as my phone is encrypted and there is no access to /data from TWRP :( ). Cellular data connection was gone again and no matter what I tried up to resetting the whole network stack from settings: no cellular data). Didn't have these problems with LOS 16.1 at all and am pretty sure to have had the latest stock radio.img from Oct 2017 (last stock update by google). So I don't think it's one of the problems named above.

Some minutes ago I reflashed the radio.img linked in the first post of this thread. It's working again now (yi-haa) but I'm a littlebit suspicious that this will stay. At least I now have a way to kick it to work again in case, I hope...

Nevertheless let me say a big thank you for your work, making me able to permanently use my Nexus 6 as my one and only phone since 2015.

Greetings

phimeas
[Nexus 6  Original Android Development] Eazy:
Cellular data have been working since I flashed version first of may. I don't dare to flash a newer version :P Phone is working really well and I doubt there will be features added in future versions. So no need for flashing a newer version.

Edit:

By the way. I have a Swedish service provider. So not T-Mobile or Verizon. I think this problem with cellular data depends on what service provider you have.
[Nexus 6  Original Android Development] phimeas:
Well, lucky you then :). I think a not working data connection renders a phone pretty useless if you're not at wifi permanently. So I could try what I tried or buy a new phone. No need to flash radio.img when everything works well, IC. ;)

Edit:

Oh, and one reason for upgrading from stock to LOS 15->16.1->17.1 are security fixes. I usually don't flash every nightly but at least once a month to be on the safe side. Otherwise there had not been any need to upgrade to 17.1 at all. It all worked well with 16.1, too. But there are no more updates.

Didn't get that perfectly when answering the first time, sorry.

Greetings

phimeas
[Nexus 6  Original Android Development] Elektroschmock:
On my device the app needs to be started twice. After that it works fine.

https://review.lineageos.org/c/LineageOS/android_device_moto_shamu/+/275062

I was able to fix it - perhaps only partly. At least it does support L3 now. Not shure if it also supports L1, but I guess not.

We don't even have liboemcrypto anymore so disabling it doesn't make much sense.
[Nexus 6  Original Android Development] mrk2815:
does may 2 build fix tthe battery drain that some of us have been reporting.
[Nexus 6  Original Android Development] esysfound:
[/COLOR]

I thought the drill was always before flashing a completely new ROM, phone needs to have encryption removed first? Exactly so partitions can be overwritten where needed?
[Nexus 6  Original Android Development] Elektroschmock:
I don't think so. Also I didn't look into it, as I don't have it on my devices and there was no proper bug report. I know battery problems are harder do report but if I can't reproduce it - I can't fix it.

Additionally I began to ignore some of the bug 'reports' if I have the impression the reporter didn't put any effort into it. Reports like like 'feature x no worky worky. Why. Plz fix' are not uncommon. ;)

Removing encryption was never needed. Only when your data partition was encrypted with android prior 8 format data was needed to be able to upgrade to android 8.
[Nexus 6  Original Android Development] mrk2815:
Elektroschmock thanks .i will just do with it.i only updated for the fac that lineage 16. was not being updated for security updates.
[Nexus 6  Original Android Development] phimeas:
Yes, when doing a clean "upgrade" from 16.1 to 17.1 I deleted and recreated /data and then encrypted /data again after installation. In fact that means to wipe everything and newly set up the whole phone from scratch (and from titanium backups ;) done before).

Of course you don't need to do this everytime when updating to a new nightly inside 17.1 branch. For installation of magisk I have to sideload the zip in TWRP and install it from there. It's not possible to install it out of the running LOS as there is no access to /data when the phone reboots into recovery (maybe there is another way and it doesn't have to be done that complicated but it's my experience so far).

The effect I described was that cellular data connection was sustainably gone again after rebooting for installing magisk when it started to work after flashing 20200501-nightly (sorry to have called it 20200502 before, it was 20200501) five minutes before. I got no clue if it came from installing magisk or just from rebooting.

What got extremely better after upgrading to 17.1 is battery drain. My battery (changed two times in this phone's life) lasts for 2 days now while it was only one day with 16.1 :good:. Maybe this is because it's not possible to wipe cache/dalvik cache from TWRP when /data is encrypted (no matter if 16.1 or 17.1 is installed) and there are many nighlies flashed after several months. Is there another way to wipe cache/dalvik-cache?

Greetings.

phimeas
[Nexus 6  Original Android Development] maddog3030:
I installed Netflix I was having a problem having it startup, I found "liboemcrypto.so" in the system/vendor/lib renamed the extension to "bak" and Netflix works..

This was on the latest nightly lineage-17.1-20200501-nightly-shamu-signed.
[Nexus 6  Original Android Development] zapjb:
Maybe I'm a dolt but why does one want data encrypted? Fear of theft or something else?
[Nexus 6  Original Android Development] maddog3030:
Yes.
[Nexus 6  Original Android Development] zapjb:
Hey. Hey! LOL
[Nexus 6  Original Android Development] zzenyoo:
Stupid question part 94637393. Is it plausible to record phone calls in 17.1?
[Nexus 6  Original Android Development] esysfound:
Battery Performance Data

View attachment 5012575

Agree of course, but I do think battery drain is a problem. Tell what you need in the way of data to try to pinpoint it.

I can only say using AccuBattery app, running very little in background, screen brightness down to like 38% and it times out after 1 min, using "conservative" CPU setting from Ex Kernal Manager, keeping email fetches not push to once every 30 min (or an hour), and my Wifi seeking somewhat subdued (this part is a bit unclear), and almost no telephoning, very little surfing, and no streaming or downloading, I get about 5.5 hrs according to the AccuBattery app - which also says all app use is normal. My battery runs cool (no hot spots on back of phone) and it was getting close to 9 hrs before I flashed the ROM. Battery usage data from the app is in the screenshot copied here-to the right for some reason of your quote.

If there is some other way to record data that might help you, let us know. Thanks
[Nexus 6  Original Android Development] Elektroschmock:
With 5.5 h and 9 h do you mean screen on time?

I am not familliar with Ex Kernel manager, but did you try without it? Any fiddling with governors, CPU freqs and mpdecison breaks the whole batterysavings.
[Nexus 6  Original Android Development] esysfound:
Hi-no the times are sort of real world screen and processor use, on and off, and off over a typical, normal day. I think the battery app judges that.

I will play with the Ex Kernel Manager but normally using the conservative setting if anything lengthens battery life. (I think it just throttles back clock speed vs tinkering with all the multiple different frequencies but I really don't know, only that it has worked well on other ROMs, sort finding the sweet spot between performance and longer battery life over a day. I believe it was designed originally to manage the Elemental kernel, but it is just overhead software really, and can be used with any. See here: https://play.google.com/store/apps/details?id=flar2.exkernelmanager&hl=en

But it does raise a useful question - what kernel is used with LOS 17.1 and do you have a better solution to manage that vs. just stock tweaks? Thanks
[Nexus 6  Original Android Development] Elektroschmock:
Okay sorry I think I was unclear in my writing. I know what Ex Kernelmanager and Ex-Kernel is. I'm just don't know exactly what those profiles intend to do and on which sysfs interfaces the manager relies.

When Exkernel was a thing shamu was still supported by google hence all kernel were mostly the same. Only some stock tweaks like you call them where the difference. With android 8 the different kernels began to drift apart, and most where given up for various reasons. Since android 9 there is only one kernel left for shamu It's the lineage kernel. You might find other kernels, but on the inside they are the lineage kernel with a different name tag applied.

Answer your questions what this kernel is, is kind of hard, but I try.

Base Google's 3.10.40 kernel for shamu

Updated to 3.10.108

Security patches up to April 2020

Full RGB LED support. (hint hint I'm proud of this)

Binder backport from 3.18

interactive governor updated to 3.18

various fixes for a lot of subsystems

What this kernel does not and will never support

Overvolting

Undervolting

Over clocking

CPU Governors with long and funny names and ****ty function

faking of bootloader status

Okay now back to your other questions.

LineageOS does have has power profiles for you too choose from. You can choose between longer battery life and higher performance. I don't know the exact setting for each profile, but I can look them up for you if you are interested.

I recommend using these and advise against the use of any kernel manager. Those where never meant to be used on this kernel and can wreck all powersavings. Only use them if you know shamu better then me. ;)
[Nexus 6  Original Android Development] esysfound:
Hi ES-super helpful. And I for one very much like the LED features of which you are rightly proud.

If you could find out what are the settings for Balanced, and Efficiency it might help (and I could compare with the EX Kernel settings). I will disable it and just play w the Lineage settings, but I did this already - all in the Settings - Battery -Battery Saver and Performance. I tried moving from "balanced" and the lags etc. just became too great. But this was also on an earlier build, not since you tweaked this in the May nightly, so maybe it is now better. Will try again.

Appreciate very much your info, patience, and guidance on all this.:)
[Nexus 6  Original Android Development] linus207:
Hi.

Reading your concersation I am wondering - what SOT should i expect? I have freshly home-mounted shamu with never used battery. Estimations made by accubattery are preety much the same as Yours - around 6h... od course using lineage. When we can way that ROM/device is healthy?

It's hard for me to say because of my nitrogen (mimax3) daily usage. 15h SOT is achieveable.
[Nexus 6  Original Android Development] Elektroschmock:
The 5 profiles are a as follows from slow to fast. I don't know the exact names of the profiles fro mthe top of my head, but you'll figure this out:

1:

Max 2 cores online

Scaling 300 Mhz - 1.2 GHz

No Interaction Boost

No Fling Boost

No Launch boost

2:

Max 2 cores online

Scaling 300 Mhz - 2.4 GHz

Interaction Boost 2 - 4 Cores 1.5 GHz 200 ms

Fling Boost

Launch boost 3 - 4 cores 2.6 Ghz

3:

2 - 4 cores online

Scaling 300 Mhz - 2.6GHz

Interaction Boost 2 - 4 Cores 1.5 GHz 200 ms

Fling Boost

Launch boost 3 - 4 cores 2.6 Ghz

4:

3- 4 cores online

Scaling 300 Mhz - 2.6GHz

Interaction Boost 3 - 4 Cores 1.5 GHz 500 ms

Fling Boost 3 Cores 1.5 GHz

Launch boost 3 - 4 cores 2.6 Ghz

5:

4 cores online

Scaling 300 Mhz - 2.6GHz

Interaction Boost 3 - 4 Cores 1.5 GHz 500 ms

Fling Boost

Launch boost 3 - 4 cores 2.6 Ghz
[Nexus 6  Original Android Development] Elektroschmock:
Here is a XML with measured values of current consumptions:

https://github.com/lineageos/androi...works/base/core/res/res/xml/power_profile.xml

As shamus battery is way to small for its big screen SOT has never been very great.

SOT could be anything between 13 h and 3.7 h depending on what you do with your device and around 20 other factors.

In reality you won't see anything near 13 h as usually your cpu is doing something when the screen is on.
[Nexus 6  Original Android Development] torecdude:
Does anybody else experiencing AOSP keyboard spell checking errors? I don't have any problem when I write in English but in Spanish it marks almost every correct word as misspelled and offers corrections to English words (see attached file)

I have the Spanish dictionary installed as you can see in the second attached file.

Even when the selected input is "Español" the keyboard still tries to correct to English. I am posting here since I have this issue since upgrading from 16.0 to 17.1

Should I use the bug report tool to capture logs, or is this not ROM related?

Thanks
[Nexus 6  Original Android Development] H@P:
random crash

Experienced a random reboot when toggling airplane mode off->on->off (have to do this occasionally when my phone shows a question mark on WiFi; connected, no internet. Not sure if it's phone sleep issues or router, but this happened in 7.1.1 latest stock). Was showing quick flashes of LineageOS boot logo, before finally booting normally. Camera and flashlight was dead once it completed booting. Rebooting manually brought it back to normal. May 1 nightly.

If this happens again, what's the best way to capture after the fact? Are there logs that survive reboot? Rooted with Logcat Extreme installed, but am still familiarizing myself with it, and have it off for the most part.
[Nexus 6  Original Android Development] Elektroschmock:
O can't tell if it is a ROM problem or if its a Google Problem. But I can tell that this isn't a device specific problem.

If it bothers you - you can make an offical bugreport on our gitlab.

I guess a log isn't needed in that case.

Not shure if I got you right. About how many problems are we talking here? It's kind of mixed up and lacking info.

Logs can be easily taken throug adb root. Which is included. If you attach a log please tell at wihich time the bug happend I don't want to - and I can't parse through thounds of lines of log.

Take a log from logcat and dmesg
[Nexus 6  Original Android Development] H@P:
Sorry...

It was just one issue... toggling Airplane mode on then off caused a random reboot.

It very quickly flashed a part of the LineageOS boot logo over and over, but it wasn't a bootloop, because it never showed the Google logo. It did this for about 30 seconds.

It eventually showed the Google logo, then the LineageOS boot logo, and it completed booting.

At this point, camera/flashlight was dead, so I manually rebooted it, then camera/flashlight were fine.

I'm assuming I need this hooked up to a computer, logging from adb, and I have to catch it in the act. There are no stored logs that I can pull after a reboot, correct?
[Nexus 6  Original Android Development] mahir555:
So this rom is working great . My question is about all shamu roms including LOS , since Android oreo i usually experience a massive UI lag just minutes after i plug the original turbo charger and the temperature goes 43° up to 55° during summer .

Is this a non fixable problem ?

I appreciate if someone can explain why this happens.
[Nexus 6  Original Android Development] githyanki:
Charging makes phone hot, hot phones start to thermally throttle.

Fix is to move somewhere cold. Here in Canada, my phone averages around 25c to 30c while in use. If I'm outside long enough, it can get really cold. Display also lags when phone is around freezing also BTW.
[Nexus 6  Original Android Development] ThePhenomenalOne1:
Hey, I'm unable to send/receive SMS on my carrier Jio but mobile data is working fine.

Anyone else experiencing the same issue?

What could be the problem?

Also, I'm able to send/receive SMS when I put in a SIM card from a different carrier.

It was working fine for Jio on LOS 16