yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] digitalcircuit:
UVC camera via USB OTG support recently-ish broken?

When I first tried upgrading to LOS 15.1 on either the 2018-03-24 or 2018-04-16 build, I recall getting a USB webcam to work (old laptop UVC camera connected via USB OnTheGo cable). I reverted to LOS 14.1 at the time due to the L1 Widevine DRM issues; the camera worked fine in LOS 14.1 too.

However, as of the latest nightly, 2018-07-17, the UVC camera support appears broken. Plugging in/unplugging the camera reliably results in a strange logcat error message:

07-19 06:46:47.928 8081 8081 W Notification: Use of stream types is deprecated for operations other than volume control
07-19 06:46:47.929 8081 8081 W Notification: See the documentation of setSound() for what to use instead with android.media.AudioAttributes to qualify your playback use case

And Android doesn't offer to start either the open-source UVCCamera app nor IP Webcam.

What should I troubleshoot next? Other logs to check? Rebuilding the boot image, reverting some of the kernel configuration changes since then..? I tried directly booting the old boot image but LOS had trouble starting, appearing to hang at boot animation; I suspect some change between then and now make it incompatible.
[Nexus 6  Original Android Development] Elektroschmock:
I guess I can't be of much help, because I don't have a UVC camera. The warning in your log shouldn't be the reason for the camera not working.
[Nexus 6  Original Android Development] wavedashdoc:
New power Hal is awesome! There is a small but noticeable bump in overall feel of the phone. Pulling down the notification shade, scrolling, transition animations all look better. I will say that heavy multi tasking really heats the phone up and I think that has to do with using higher governor speeds to compensate for the cores hot plugging. For the next release could we have an option to disable the core hot plugging and run all 4 cores online?

This is really the best release yet. ? I hope this is implemented and tested throughout the Shamu ROM scene.
[Nexus 6  Original Android Development] Event_Horizon:
Guys please help.. help in the name of God of android...

My Shamu.. precious.. cute.. powerful.. phone going into its worst phase, I have everything thing normal till the day I flashed the twrp recovery 3.2.2.0, sh*t happened, randomly my shamu getting turned off, then on trying to booting it up.. battery showing nil... Then after 1-2 mins if boots manually, then again cycle starts on random basis,, returned to twrp 3.1.20 cleaned re flash 5 times but still problem persists.... Anyone please...
[Nexus 6  Original Android Development] kraehetest:
That should be the case in the performance profile.

---------- Post added at 03:15 PM ---------- Previous post was at 03:11 PM ----------

I had the same problem at the weekend, but the battery was dead. I had tried a lot until it went again. Try switching the device off with a long press on the power switch with or without charger.
[Nexus 6  Original Android Development] Event_Horizon:
Hi,

I too thought the same.. but after turning it on I found it has 47% left battery power, it got something else...
[Nexus 6  Original Android Development] nemanja066:
Try to delete buggy magisk and root with the recommended su addon. Clean install!

I have 5-5.5h SoT, 1day on battery. Sync on (2 account), wifi+data, 50% brightness...

New polarcell battery
[Nexus 6  Original Android Development] Elektroschmock:
I didn't see any abnormal heat generation, and I don't think hotplugging would be the reason for it.

Edit:

I just did some math, and from the numbers it doesn't make sense to force all cores to on. A core running at 300 Mhz has a base 'cost' of 72 mA and doesn't contribute much to performance. With those 72 mA you could run another core at full speed instead of ~1,9 Ghz

In my tests forcing all cores to on had a noticable impact on battery.

Hotplugging is good enough to online cores if the load goes up.

Yes, performance profile is also forcing all cores to max. speed. So it only serves a very limited purpose.
[Nexus 6  Original Android Development] kraehetest:
I have tried. The only thing i have not wiped, is the internal storage.

Tomorrow I will made a full backup and format erverything.

I also reflashed the modem, recovery and bootloader.
[Nexus 6  Original Android Development] ExpectedCrayon:
Do you use Magisk?
[Nexus 6  Original Android Development] kraehetest:
Yes, but I tried it with and without.
[Nexus 6  Original Android Development] ExpectedCrayon:
Hm... I'm not sure then. I have L1 and I use Magisk. Did you flash Magisk at the same time you flashed the OS? Only other thing I can think of.
[Nexus 6  Original Android Development] Taranis:
5,5 h is great assuming that we are talking about whole day. :D

But as I wrote, it was just YouTube in browser on lowest brightness on WiFi, nothing installed + new battery + no sim card. So yes, I expected like 7 hours in such scenario. It's possibly the one of the lightest usage. I was getting at least 7 hours in such scenario on old

broken

, original battery.

I'm now measuring SOT for mixed usage (whole day) and battery stress test. It looks promising for now.

Elektroschmock, great work BTW! And don't blame me if I wrote anything wrong, I'm using P2 as main phone. I constantly get there at least 10 hours with BT on, many apps, WiFi+4G :D Nexus will be used by my brother.

--

About heating: my Nexus got a little bit colder with new battery and 1707. Of course it gets hotter while doing some intensive stuff or using it longer, but it's still less hot than previously. I changed battery, because I was getting random shutdowns below 50%.

--

Widevine DRM: I got L1 on 1707 with Open Gapps Pico. Nothing else. Wiped everything in recovery. No root or magisk. DRM checked by DRM Info app.
[Nexus 6  Original Android Development] kraehetest:
I flashed it right after the OS. I also tried it afterwards. I don't understand why it suddenly doesn't work anyway. I think last week or the week before everything was still going on. I didn't do anything great new either.
[Nexus 6  Original Android Development] Darkwing_Duck:
I've always heard that the BT is a wonky calculation, but not sure I believe it. After 28min from a full charge, at 88%. On the efficiency profile none the less.
[Nexus 6  Original Android Development] Elektroschmock:
No worries, you didn't say anything wrong. I just didn't know if you thought 5,5 h is good or bad. Looking at the current consumption of shamu's hardware 7 h SOT seems the maximum possible.

Our cpu is an energy hog. The newer big-little cpus are much more battery friendly.

Ok, let me rephrase it. :) There is a miscalculation for BT's energy consumption which I wasn't able to track down yet. On my devices I can't see any real drain and I did current measurments on board level.

I know of some users who suffer from real drain, but fixing this is close to impossible because a bad, paired BLE device could keep your shamu awake forever.
[Nexus 6  Original Android Development] digitalcircuit:
Re: UVC camera via USB OTG support recently-ish broken?

To be fair, plugging a USB webcam into a phone via USB OTG is not commonly done :) Thank you for the guidance on ignoring the warning.

Sometime soon (maybe within a week) I'll revisit the old LOS 15.1 builds and try to manually git bisect the changes. I'm not sure how to do that across the many repositories in LOS, but hopefully I can at least narrow it down a specific configuration change or commit. I'm guessing it'll have to do with the shamu kernel configuration cleanups, or maybe the shamu device tree changes, narrowing the range of selections down to two repositories. Kinda, since everything's interconnected.
[Nexus 6  Original Android Development] kraehetest:
An update to my DRM problem. I have now installed the original Google Factory Image. It's still level three. I don't know what went wrong with my device. Maybe a hardware defect.

Or if the DRM key is on a partition, then it is no longer there.
[Nexus 6  Original Android Development] dbrickg:
I'm not sure what you mean by USB OTG, but I have a little webcam with a USB output, and I just plugged it into the USB port on my phone, and it works just fine. I installed some webcam app, CameraFi, awhile back, and that popped up when I plugged the camera in to the phone
[Nexus 6  Original Android Development] digitalcircuit:
Re: UVC camera via USB OTG support recently-ish broken?

You are correct, there's no issues with USB On-The-Go and UVC cameras. Pardon [MENTION=3383960]Elektroschmock[/MENTION] for the hassle!

I suspected my camera soldering job was faulty at first (I did liberate it from an old laptop), yet it worked fine on my desktop and laptop. However, just now, after fiddling with the connections some more and checking dmesg, it works with the Nexus 6, too... I guess the USB hardware in the phone is less tolerant of reliability issues. Apologies for the false alarm, I feel rather silly now.
[Nexus 6  Original Android Development] Taranis:
Hi! I did whole day mixed usage battery test (w/o SIM card unfortunately), but I got to 5,5h SOT at 1℅ of battery. I think it's nice. 3,5h of YouTube (low brightness), 45 mins of Angry Birds at full brightness, 22 mins of Chrome on auto, 1 Antutu test... So I expect it will last 3-4 hours on mixed usage with 4G.

I found (just) one issue. At first boot (configuration) connecting to WiFi seemed "jerky" (connecting/disconneting few times). At other wipe I couldn't find 2.4GHz WiFi, but only 5GHz at longer period. Now, after using it in normal OS I had similar situation and in addition to that today during web browsing my WiFi was disconnected 1 or 2 times. That never happened on my other phone or other devices at home.

I also had weird glitch with AOSP web browser and going into full screen mode (like expanded desktop) on YouTube.com.

That's it. No more issues found. It gets 100k in Antutu, while my main phone gets 80k :D I think I will keep this ROM for my brother instead of stock/14.1. Really nice working for such device. Good work!

Of course, I have flashed latest Google image before.
[Nexus 6  Original Android Development] MiroALG:
does this score good ?? runing latest lineage os
[Nexus 6  Original Android Development] duttyend:
Set GPU Renderer

Dear Elektroschmock, according to this article, do we need to set it to OpenGL (Skia) (currently, it is set to OpenGL (Default) on my device, I don't know if it is because I come from CM14) ?
[Nexus 6  Original Android Development] Albert52:
Lineage recovery, Changelog 19

Elektroschmock can you please help me out.

I am currently running lineage 15.1 with OpenGapps on my Shamu using TWRP as recovery and I am verry happy with it.

Reading changelog 19 I learned that now there is a Lineage recovery that should be installed with MindtheGapps.

My question is, should I reinstall Lineage 15.1 but now with MindtheGapps on my cleaned Shamu in order to switch to Lineage recovery? Wipe data etc.

As I understand it Lineage recovery is necessary in the near future.
[Nexus 6  Original Android Development] SteveYoungs:
AIUI, this won't affect Shamu, it is for more recent devices that have the 'A/B' partitioning setup.
[Nexus 6  Original Android Development] Elektroschmock:
Just a quick heads up:

I'll be away the next 3 weeks and will only have limited internet access.

So no need to worry that I have abandoned our beloved shamu.
[Nexus 6  Original Android Development] Sanabil:
Good luck bro
[Nexus 6  Original Android Development] Albert52:
Enjoy your well earned holidays
[Nexus 6  Original Android Development] quizzina:
Does it mean that we will not have updates for 3 weeks?

In any case enjoy your holidays
[Nexus 6  Original Android Development] jardincorenda:
Thanks for all the hard work you do on the phone and firmware. Enjoy your break.
[Nexus 6  Original Android Development] kraehetest:
Of course not. There are still weekly updates. Only no Nexus 6 specific improvements.
[Nexus 6  Original Android Development] dbrickg:
downloaded and installed the 20180724 nightly. looks good so far
[Nexus 6  Original Android Development] ExpectedCrayon:
Same here. Very smooth.
[Nexus 6  Original Android Development] ExpertMC:
Does anybody have working instant apps? I am using OpenGapps Stock and they don't work. It just opens a link in chrome even though it is enabled in the google settings.
[Nexus 6  Original Android Development] foladar:
Using the newer update with power settings, I assume it's safe to run the phone in Quick or Performance all the time, or due to it keeping the cores at specific speeds, should it generally not be? Thankful for the new power settings though, hoping it runs smoother in PoGo
[Nexus 6  Original Android Development] mrk2815:
Elektroschmock you need a break and a vacation from time to time.
[Nexus 6  Original Android Development] Treatcon:
I keep mine in performance and it's just fine. Good battery life, but I don't play any games on my phone. I have tablets for that :cyclops::svetius:
[Nexus 6  Original Android Development] paulmerrill:
I think this "bug" is the effect of an old battery, but just in case it isn't...

I notice that when my battery gets to around 45%, give or take, I'll get a power off (phone turns off with no warning, just boom off). If I then reboot, battery is still at 45% and will now last all the way down to 0%.

So do we think this is a defect or an old battery?
[Nexus 6  Original Android Development] nemanja066:
From time to time, I get a FC from some application (I didn't notice when it happened). This causes a 'chain reaction' and almost all other applications show FC when I start them. Sometimes it work without a reboot (by itself), but usually must restart. Does anyone still have this problem, to know if it's on my side? I've always worked with TB restore (maybe that's the reason)?

Thanks. :highfive:

Both!
[Nexus 6  Original Android Development] paulmerrill:
I've never seen this problem. However, what does FC mean?
[Nexus 6  Original Android Development] nemanja066:
FC - Force Close - Crash. :fingers-crossed:
[Nexus 6  Original Android Development] paulmerrill:
Yes, figured it was force close about 10 min later. I don't think it was an FC in my case, it was definitively a power problem. It may even be a problem with the battery percentage. I switched to popcorn kernel as a test and the % immediately dropped from 35% to about 12%, so perhaps it is a defect?
[Nexus 6  Original Android Development] mrk2815:
have my device with old battery about 3 years old and its gotten below 40% and no force close or shut down.so dont know what to tell you.also have another nexus 6 and that is on another rom and that does not show that issue when it dipps below 40%. So dont know what to tell you.
[Nexus 6  Original Android Development] Lagarde:
This is an old battery thing, though not all of them get it. Mine does this and took me forever to figure out. For me, it's around 30%, and it won't stay on if I reboot it. The impression I got is that if you get a power spike (ie, all 4 cores decide to draw sudden bursts of power), it crashes when it's below 40ish %.
[Nexus 6  Original Android Development] ExpectedCrayon:
Definitely a battery thing. I have this problem as well. Tried to replace my battery, but when I popped open my phone the screws were stripped so I couldn't get to the battery and take it out. I found that putting on battery saver mode when I'm around 40% prevents the phone from shutting down before the battery fully drains. Unfortunately, the phone runs like trash when I have to do that.
[Nexus 6  Original Android Development] paulmerrill:
Thanks and that makes sense.
[Nexus 6  Original Android Development] skookum1:
Love the ROM. I've tried all the popular oreo roms and Lineage is my favorite. Though I have had issues since upgrading to oreo with bluetooth not auto connecting about 80% of the time. This happens with every rom i've tried, was just wondering if this is just the way it is or if anyone experienced this and fixed it? Maybe it's time to upgrade my car stereo? Google comes up with many hits but no real fixes to be seen.
[Nexus 6  Original Android Development] ulibube:
I saw problems like this in the past that were related to Gapps.
[Nexus 6  Original Android Development] Lagarde:
Edit: Got confirmation elsewhere that it's not worth the hassle.
[Nexus 6  Original Android Development] Bigb12:
I need to flash the radio on verison. I don't have pc access currently, and have twrp installed. Can I get a how to on how to flash the radio img in twrp? Thanks.
[Nexus 6  Original Android Development] ktmom:
There is a thread with recovery flashable zip files [URL="https://xdaforums.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052" ]here[/URL].

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[Nexus 6  Original Android Development] foladar:
Since updating to LineageOS 15.1, my phones been turning off <40% randomly. Since going to the newest update with the "battery settings" it's been doing it a lot more. Once at 100% (charging overnight), once at 44% and now at 58%. I've done the battery re-sync stuff, but it's not dead because the phone turns right back on. 14.1 was fine. What's the deal with 15.1? Really wanted to use this for a few more months but it doesn't seem to be working out.. it's even laggy when it does work most times now.
[Nexus 6  Original Android Development] Sanabil:
Good sot .
[Nexus 6  Original Android Development] dansblackcat:
Exact same issue here. Most replies point to it being a battery issue but I'm not convinced.

Mine never had an issue on the official rom.

When my phone turns off I can turn it straight back on, all appears normal but as soon as I unlock it it turns off again.

I can use the torch from the lock screen and it's fine but as soon as I try and unlock it it shuts off again.

After it shut off for the fourth time in a row I booted into recovery and cleared dalvik and cache. After that the phone worked fine until the battery actually went completely flat. Probably unrelated but I thought I'd mention it
[Nexus 6  Original Android Development] razorloves:
As some of you already noticed, the build failed today. But not just shamu... all devices did. There was a problem with the server that sign's the zips.

The problem has been fixed and all builds restarted, so we should have a new build available later today. :good:
[Nexus 6  Original Android Development] Lagarde:
Be thankful you can't see my happy dance over here. Thanks!
[Nexus 6  Original Android Development] m4au312:
Thanks for the reply, I found this on the other thread. Do you think this will work? since the rom is based on the N6F27M from google. thanks! :good:

https://xdaforums.com/nexus-6/development/kernel-n6f27i-n8i11b-encrypt-t3652995
[Nexus 6  Original Android Development] jbaumert:
Possibly, but I wouldn't advise it. I'm sure there are a lot of updates and patches that have been applied since the last "Google" release.

That said, read through this post: https://xdaforums.com/showpost.php?p=61015828&postcount=902 - It is actually really easy to tweak the included boot.img in the LineageOS zip to remove the encryption. One note: There are two places in the Lineage boot.img to change to encryptable.

So... If you managed to read through all that. I went ahead an included a "tweaked" boot.img of the latest LOS release to get you started.

lineage-15.1-20180402-nightly-shamu_image-new

Flash with fastboot or TWRP using the "Install Image" option BEFORE booting the ROM for the first time.

Enjoy!!
[Nexus 6  Original Android Development] m4au312:
OMG you are so nice. thank you so much. I need to learn to do it myself, stop being lazy... Thank you so much!! :good:
[Nexus 6  Original Android Development] SteveYoungs:
It worked fine in 14.1, no reason to suspect that it won't in 15.1.
[Nexus 6  Original Android Development] razorloves:
https://lineageos.org/An-April-Apology/
[Nexus 6  Original Android Development] ExpertMC:
Build just failed on sign... AGAIN.

EDIT:

Seriously, every build successful before shamu. Then shamu and every build after it failed to sign... Why must this happen to us?
[Nexus 6  Original Android Development] 8zabi:
[MENTION=3383960]Elektroschmock[/MENTION] [MENTION=614507]razorloves[/MENTION]: if the weekly build is not coming is it possible to build just the new kernel for us?
[Nexus 6  Original Android Development] barbara-luise:
Could someone please explain for the newbies what’s going on here?
[Nexus 6  Original Android Development] Popo001:
Nothing to be worried about.

It's just that the build we should have today/yesterday has failed because of a signature problem . Actually, builds have been launched again and our one will finally just be delayed.
[Nexus 6  Original Android Development] asci77:
why this one is Beta

i installed LOS on my parents mobiles years ago.

There the Problem was the Bootloader, LOS was easy.

I switched from Pure Nexus, so in twrp i wiped data and caches, flashed LOS img and gapps, reboot.

All not well... 30 GB used?

My Software is counterfeit?

the vendor key not right?

Factory reset, so i get 64 GB...reboot...still 30 GB used.

In twrp format storage, after boot i got the 64 GB, but now lineage is password protected so i cant flash anymore...

connnect Pebble smartwatch....reboot all the time... after flight mode and pebble off and turning on 1 at a time it worked

getting rid of that stupid april prank was also annoying

So now i have solved all, execpt the vendor key and that i have to reformat all if i want to make an update... this schould never have been out of beta!!!

If i would have been a first time user chances are high i directly go back to factory image and never look for custom roms again.

And LOS is the one OS most newbies look for.

Btw, why should i be using the radio and bootloader img from the ones linked below that are already extracted? I never did this , also this time not, i just flashed LOS and gapps as told on the lineage website.
[Nexus 6  Original Android Development] Elektroschmock:
As written a gazillion times before:

Vendor image missmatch is caused by a commit which went in just before the automatic build was triggered.

I wasn't able to react that fast because i don't watch gerrit all the time. I have a paid job an LineageOS is just a hobby.

If you already have the latest bootloader and radio image and TWRP there is no need to flash them again.

Counterfait warning was a bad april fools. This is nothing device specific so don't blame me for this.
[Nexus 6  Original Android Development] Popo001:
About the space storage problem : sometimes (happens to me as well) you forget that the backups made in TWRP take a lot of space and are sometimes not visible in android storage analysis. Hope it's just that.

I agree like almost everybody the April joke was poor taste and LOS team already apologies for that, let's move on.

About the vendor problem, the maintainer said it has been already fixed, and nothing was to worry about. Just patiently wait for the next build.

About the smartwatch, I don't have any so I can't help.

All in all, the build is pretty solid and i think the maintainer wanted to make the community happy and launch a build as quick as possible. So he shouldn't be blamed. All the more the few bugs the build has were precised in OP.
[Nexus 6  Original Android Development] nilesh0205:
Hi, If this was regarding my question, I am a complete noob, I dont have any development experience to debug the issue. If someone can guide me how to check for logs and provide them to developers then I am happy to do so.

Thank,

Nilesh.