yashsingh1/xdaforums huggingface dataset:
[G4 Q&A, Help & Troubleshooting] Denfetafrukten:
So i've been tinkering with themes for the G4 tweaksbox and i've found that resources on the lockscreen (for example, the slide-for-camera icon) are changed with the system ui theme and not the lockscreen theme - is this because the tweaksbox was originally made for KitKat on the G3 and the lockscreen was fundamentally changed with lollipop and is now pretty much a part of the systemui?

Anyway, i've made some new resources and added the correct strings to theme.xml and lockscreen-theme.xml (which turned out to be not needed) along with a animation file for them in /drawable, but i can't get the custom animation to work. I've created the file lockscreen_lock_icon_camera_animation.xml (found by decompiling the systemui.apk on my G4) and pretty much used other g4twb animation files as a template to write this in it: (The xmlns link does not have breaks in it, i put them in here because xda wont let new users post links)

<?xml version="1.0" encoding="utf-8"?>
<animation-list android:oneshot="true"
xmlns:android="http :// schemas . android . com / apk / res / android">
<item android:duration="1300" android:drawable="@drawable/lockscreen_lock_icon_camera_00" />
<item android:duration="100" android:drawable="@drawable/lockscreen_lock_icon_camera_01" />
<item android:duration="100" android:drawable="@drawable/lockscreen_lock_icon_camera_02" />
<item android:duration="800" android:drawable="@drawable/lockscreen_lock_icon_camera_03" />
<item android:duration="300" android:drawable="@drawable/lockscreen_lock_icon_camera_00" />
<item android:duration="100" android:drawable="@drawable/lockscreen_lock_icon_camera_01" />
<item android:duration="100" android:drawable="@drawable/lockscreen_lock_icon_camera_02" />
<item android:duration="800" android:drawable="@drawable/lockscreen_lock_icon_camera_03" />
<item android:duration="300" android:drawable="@drawable/lockscreen_lock_icon_camera_00" />
</animation-list>

All the files compile fine and can be found in the newly generated public.xml file but only the new resources show, not the new animation. Any ideas why?

EDIT:

Looked through my files again and turns out i forgot to add the animation file to theme.xml.

Can't find a delete button anywhere so i guess you are all free to laugh at me now
[Honor 7 General] Sideness:
Hello everyone.

I just installed Google Now Launcher and something is bothering me. The Navigation Bar at the bottom of the screen is black. Which isn't pretty. I would like to have the wallpaper going to the bottom of the screen instead.

Do you guys know how can I do that ? There is no setting possible I think...

Envoyé de mon PLK-L01 en utilisant Tapatalk
[Honor 7 General] voyager_s:
I was also unable to do this with Google now launcher. Switched to nova launcher and there is an option in nova settings to do so

---------- Post added at 09:34 PM ---------- Previous post was at 09:33 PM ----------

Forgot to mention. The transparency only works for the home screens. In the apps it goes back to the black bar. I think it's the system UI which does not allow full transparency throughout.
[Honor 7 General] themegaphoenix:
Done the same thing

Nova launcher would make it transparent

And it goes back in the app
[Honor 7 General] rowihel2012:
i hate this stock ****ty software i need miui7 or cm rom in my p8max
[General Questions and Answers] steve30x:
Ok maybe my original post was too long and wasn't read. So I started this thread in hopes I could get some help. My tablet should have 16GB storage but its only showing just over 3GB. The nand storage area on the tablet will not mount for me but is shown in the settings / storage area. when I click mount it tries to mount but less than a second later it fails to mount.

Also I was hoping either I could get help with creating a custom lolipop rom for the tablet. I will provide any of the files from the tablet needed that I can.

I've put the original post in the second post.
[General Questions and Answers] steve30x:
I got this tablet five days ago. All was going good until I used Kingoroot to root the tablet. After rooting I quickly realised that with Kingoroot installed and applied I was still not getting full root access with a few apps so I decided to try and get full root access by editing the build.prop. After editing a few settings and reboot after tweaking a setting I still wasn't getting full root access. Then I edited a wrong setting and the tablet got stuck in a boot loop.

I spent ten hours trying all kinds of tricks to push the fixed build.prop back to the tablet with no access so I asked on different forums (Including XDA) for help. Thanks to Oma over at ArcTablet (He is a member of XDA too) who helped me get CWM onto the tablet and the fixed build.prob on to the tablet I finally got the tablet to boot into the OS again. Here's a link to the forum thread where he helped me

http://www.arctablet.com/blog/forum/...-soft-bricked/

So now I have CWM on the tablet and after a few more tweaks I finally got full root access. That was all good until lastnight when I was watching a youtube video and the tablet rebooted all of a sudden for no reason. The tablet refused to boot into the OS again. So I tried applying a CWM backup I had taken earlier but it stops at SDCard/Android Secure which it says does not exist.

I finally got the tablet to boot into android OS again but some apps refuse to install and some apps close straight away. Also the Nand partition will no longer mount. It shows that it exists in the settings but when I press mount it tries to mount but fails to mount less than a second later.

So to get to why I started this thread is to see if any of you guys would be kind enough to offer help here. Also maybe we could work together and get a custom rom working on the tablet. I can't find anything for this tablet online so this is a start.

If you guys need me to supply any more details then let me know. I don't know where the best place is to upload files either.
[General Questions and Answers] sindamc:
Did you managed to fix it? I know it's been a long long time but could you detail what you've done to install cwm and root?

Hope you can help me I was thinking on using this tablet as a wall panel.
[Nexus 6 Q&A, Help & Troubleshooting] NishantM:
Off late I'm noticing that whenever I turn on the display, it goes completely bright for maybe 5 seconds before adaptive brightness kicks in. Today I completely reset my phone and reflashed the latest factory image (MRA58R, I was on MRA58N previously). It was fine for a while (for a few hours) and now it has started behaving the same way. It works fine if I turn off adaptive display. This happens 90% of the time.

Has anyone else faced this?

---

I have filed a bug report, please star it.

https://code.google.com/p/android/issues/detail?id=196048
[Nexus 6 Q&A, Help & Troubleshooting] foxnutz:
I've got the same issue on 6.0 stock not rooted. I've been fiddling around with lux trying to get it to stop going to max bright in low light settings... And it seems that the light sensor is getting incorrect readings in low light and it takes a few seconds for the sensor to start showing accurate levels for the light conditions. I would love to have adaptive brightness work as it used to - don't know what changed.
[Nexus 6 Q&A, Help & Troubleshooting] Face_Plant:
Same issue here.
[Nexus 6 Q&A, Help & Troubleshooting] NishantM:
Woah. I'm not alone. So for all you guys, it started just recently?
[Nexus 6 Q&A, Help & Troubleshooting] foxnutz:
yeah. I noticed it a little less than a week ago
[Nexus 6 Q&A, Help & Troubleshooting] altimax98:
Do you use Gravity Box?

Issue came with that mod for me and even after removing it my Adaptive Brightness still doesn't work properly.
[Nexus 6 Q&A, Help & Troubleshooting] NishantM:
Hmm. Same here. Started last week. Will have to dig out what the root cause is.

Nope. I'm running completely stock, no root, even locked bootloader (for device protection feature).
[Nexus 6 Q&A, Help & Troubleshooting] foxnutz:
I am running completely stock marshmallow no root, boot loader is locked, no gravity box. Same problem.

Is there any program we can use to monitor the readings at the light sensor is receiving?
[Nexus 6 Q&A, Help & Troubleshooting] NishantM:
I have tried two apps but that doesn't seem to gather data while running in background; only works when the app is opened. Still trying to find one that does background logging.
[Nexus 6 Q&A, Help & Troubleshooting] major_daz:
I have the same issue.

And I thought it was Gravity Box.... now I wonder if it's the November patch? Since there is report from people who never root and using stock?
[Nexus 6 Q&A, Help & Troubleshooting] NishantM:
Ok, so I found an app that can log data while in background. It's called Androsensor. It also has a companion app (Androsensor Keep Awake) which helps to hold a wakelock to gather more data. I tried it and I feel it's definitely not the sensor or it's driver/binary malfunctioning, it seems to be reporting proper values. Maybe more people can try it and report back.
[Nexus 6 Q&A, Help & Troubleshooting] rudynasco:
i just bought my phone (brand new) update it right away to 6.0 and used it and having thesame issue!

that means this is google firmware problem!
[Nexus 6 Q&A, Help & Troubleshooting] foxnutz:
The reason I believed it to be the sensor was because I used lux to try and fix this and noticed when the bug was occurring, as the screen just turned on and went to max brightness, lux showed the values from the sensor above 20000. Oddly enough if I had lux update every 3 sec it would sometimes capture the actual light levels on the second update and adjust accordingly. I'll check out the app you mentioned and see what shakes out.
[Nexus 6 Q&A, Help & Troubleshooting] Pyrazol:
I'm having it too, also completely stock and unrooted, first noticed it a few days ago. A friend of mine also has it. He is also stock, I'm not sure about his root status though.
[Nexus 6 Q&A, Help & Troubleshooting] foxnutz:
Ok got some interesting results this morning using androsensor. First of all I was unable to recreate the bug while using the keep awake helper app... Which leads me to believe that there may be some issue with the sensor values being calculated/averaged by the autobrightness code/program as the device wakes up from sleep. perhaps android is shutting off the light sensor when the device goes to sleep and this causes a reset? So it appears that it's not getting wrong values rather, that the data being drawn from the sensor is reset or perhaps recalculated as the device wakes back up. Almost as if it can't remember the last light level that was observed. I uninstalled the wake lock helper and was able to recreate the bug by letting the device "sleep" (leaving the screen off for maybe 5 seconds). So while the sensor showed readings of 2 lux the screen brightness was increased erroneously until the auto brightness refreshed and then after a few updates on the sensor the correct brightness was applied to the screen. Curious results. Can anyone else try to recreate the bug using androsensor and the wakelock helper program? I'm hoping I didn't run into some user error there.
[Nexus 6 Q&A, Help & Troubleshooting] NishantM:
I too tried without the wakelock helper and got the same result which made me believe it's not the sensor that's causing it. Will try the same with the helper app and report back.
[Nexus 6 Q&A, Help & Troubleshooting] NishantM:
Just tried Androsensor with the helper and I was unable to reproduce the bug, exactly what foxnutz faced.
[Nexus 6 Q&A, Help & Troubleshooting] foxnutz:
Alright so we got some results! Just for the sake of being thorough, can anyone else replicate these results that andr0idfreak and myself saw? It seems holding a wakelock on the sensor stops this bug.

Now where do we go from here? It's been an awfully long time since I've done anything with logcat... But I think that may be our best bet to find out what's really going on here. I'll have to do some homework before proceeding. Will report back.
[Nexus 6 Q&A, Help & Troubleshooting] NishantM:
I think we should file a bug report here.

https://code.google.com/p/android/issues/list
[Nexus 6 Q&A, Help & Troubleshooting] Flying_Hellfish:
I think a bug report is probably worthwhile. I thought it was some combo of xposed and gravitybox as well but I flashed my stock system back and it's doing the same thing.
[Nexus 6 Q&A, Help & Troubleshooting] NishantM:
I have filed a bug report. Please star it.

https://code.google.com/p/android/issues/detail?id=196048
[Nexus 6 Q&A, Help & Troubleshooting] NishantM:
A Google Project Member just responded to the issue and he's asking for a bug report. I have filed it. Others please capture a bug report and attach it there.
[Nexus 6 Q&A, Help & Troubleshooting] Pyrazol:
Already done :good:

Btw: are you guys using the Muzei Live Wallpaper by any chance?
[Nexus 6 Q&A, Help & Troubleshooting] NishantM:
Nope. I was using Tapet till yesterday. Switched to Wave today, problem still exists though.
[Nexus 6 Q&A, Help & Troubleshooting] Pyrazol:
Alright, well, let's hope the Google devs come up with a fix from our logs.
[Nexus 6 Q&A, Help & Troubleshooting] Flying_Hellfish:
I am using Muzei. And as unlikely as it seems is there a chance that's the issue? Flashing back to stock (no xposed) has made the issue a little less prevalent but it still exists.

I think I'm going to go back on xposed and use gravity box to lower the normal brightness because even at it's lowest level on stock without adaptive brightness enabled it is still too bright for me in a dimly lit room.
[Nexus 6 Q&A, Help & Troubleshooting] Pyrazol:
I was just grasping at straws. Looked through my log and Muzei popped out. I think there was an update a while back (Edit: Nov 12) so I thought some Muzei feature might be wreaking havoc.
[Nexus 6 Q&A, Help & Troubleshooting] Pyrazol:
Good news, (curiously) the bug report has been accepted and someone from Google is looking at the issue. Surprisingly quick.
[Nexus 6 Q&A, Help & Troubleshooting] NishantM:
Right. Came here to post the same :D
[Nexus 6 Q&A, Help & Troubleshooting] cveres:
Bluetooth?

I have the same problem that suddenly started after I paired with an LG Watch Urbane. Previously I was not using bluetooth.

I tried turning bluetooth off, but the problem still remains. So I think it was a coincidence that I noticed the problem right after I paired the device. But I did not install any other apps or updates around that time, so it is very strange ....
[Nexus 6 Q&A, Help & Troubleshooting] repaofrefa:
This issue bothered me for a few days. I just bought the phone a week ago (brand new, never rooted). I am running MRA58N. To recreate the issue, go to settings -> Display -> turn on "Adaptive brightness" and then turn it off, turn it back on again. You will probably see the Brightness issue.

I would say 5 out of 10 times, when turning "Adaptive brightness" on, the screen will be 100% brightness for a few seconds and return to the normal level.
[Nexus 6 Q&A, Help & Troubleshooting] NishantM:
Just a heads up. Clean flashed Android 6.0.1 factory image today and the problem still persists.
[Nexus 6 Q&A, Help & Troubleshooting] Quality0528:
Exactly the same issue. Running Stock MRA58N unrooted.
[Nexus 6 Q&A, Help & Troubleshooting] NishantM:
Slightly OT. I have exchanged my Nexus 6 with a Nexus 6P. I would be getting the delivery in two days after which I won't have the Nexus 6 with me. So someone may have to take over this thread for following up with with Google guys.
[Nexus 6 Q&A, Help & Troubleshooting] Pyrazol:
I'll do what I can ;) But I suppose there's not much more we can do anyway, except wait.
[Nexus 6 Q&A, Help & Troubleshooting] NishantM:
True. Hope they fix this soon. This issue is so annoying and sometimes my eyes hurt due to the sudden blast of brightness; I usually keep the phone display pointed to an angle before unlocking the screen when I am in a darker room :silly:
[Nexus 6 Q&A, Help & Troubleshooting] pekcle:
It seems there are few posters on this thread. Are there any of you out there that have 6.0 with the November update onward that don't experience an issue with adaptive brightness? Perhaps it's not as widespread as I had thought and only affect small batches.
[Nexus 6 Q&A, Help & Troubleshooting] Pyrazol:
I can confirm the issue is *not* fixed with 6.0.1 (MMB29K). Just got the OTA.
[Nexus 6 Q&A, Help & Troubleshooting] pekcle:
Sadly, this appears to be a hardware defect. Out of the 4 I got, only one had this problem. If you're out of the exchange period, your only option is warranty repair. The small number of people reporting led me to this conclusion. I'm sure a widespread problem would have been addressed much more quickly. I'd welcome any information that can prove me wrong, but I'm exchanging mine nonetheless.
[Nexus 6 Q&A, Help & Troubleshooting] Pyrazol:
I very highly doubt that, considering it just started happening, and everyone here (plus two friends of mine) seems to have gotten the issue at the same time, directly after an OS update no less.

It's also not that surprising to me that this kind of non-showstopping bug wasn't fixed in the first update after discovery, considering that it was accepted as a bug on Dec 3 and the contents of the update, which started rolling out yesterday/today, were probably already set in stone at that time, not to mention it probably took a while for them to fix the bug, if they've even done so already.
[Nexus 6 Q&A, Help & Troubleshooting] pekcle:
I have come to a different conclusion after having experienced it on my current phone. I found a reproducible result, perhaps some of you can try it and help verify.

I found that the TWC Wi-Fi Finder app triggers this behavior like 50% of the time. Perhaps others can chime in.
[Nexus 6 Q&A, Help & Troubleshooting] Quality0528:
Just updated 6.0.1 (MMB29K), the bug is stil there. So sad!:crying:
[Nexus 6 Q&A, Help & Troubleshooting] pekcle:
I updated to 6.0.1. But mine was solved after removing an offending app. It made no sense. Definitely a bug in Android if an app can trigger this.
[Nexus 6 Q&A, Help & Troubleshooting] Pyrazol:
I don't have this app installed. So either it's something that a few other apps trigger as well... or it's placebo on your part ;)

It might as well be an app, but I'm not going to go through my 125+ apps in order to find a culprit that might not be an app after all anyway :D

Edit: Maybe all of us should post the apps that we've got installed and compare. But this kind of thing usually doesn't help, and I'm lazy, so...
[Nexus 6 Q&A, Help & Troubleshooting] pekcle:
The purpose of posting the app is because I was hoping someone could post it to the bug report to speed up the bug fix.

It was definitely the cause and not a placebo effect. Tested it on multiple N6. I believe you are right that a few apps trigger it. Sucks that the 6p and 5x get most of the love and the bug priority is assigned to low.
[Nexus 6 Q&A, Help & Troubleshooting] Pyrazol:
I'll add it to the bug report. So after uninstalling the app you don't have the issue anymore at all?
[Nexus 6 Q&A, Help & Troubleshooting] pekcle:
Yes, that is correct. On two N6, removing the app eliminated the auto brightness problem.
[Nexus 6 Q&A, Help & Troubleshooting] Flying_Hellfish:
I had Wi-Fi analyzer installed and after removing it the issue did seem to be better last night but it still happens 50% of the time this morning so I think it may have just been placebo in my case.
[Nexus 6 Q&A, Help & Troubleshooting] pekcle:
I also have Wi-Fi analyzer installed and it hasn't given any problems. I decided to go back and retest the app giving me problems and confirmed it immediately. At the least, I'm glad it's not faulty hardware. I think that's the answer most people are looking for, especially the ones that just got it.
[Nexus 6 Q&A, Help & Troubleshooting] hackthis02:
If the Wi-Fi analyzer worked before the patch it should work after. And if an Wi-Fi analyzer can mess with the screen brightness while not running, that sounds like a OS issue.
[Nexus 6 Q&A, Help & Troubleshooting] sysfrog:
I have the same issue on my N6. I don't have the Wi-Fi analyzer app installed, but I'm a Project Fi user and Project Fi installs an app that scans for open wireless networks in the background. I'm going to try and check if this issue still occurs when I disable WiFi scanning.

I also noticed that when this issue occurs the Lux reading of the sensor is always 25457 (I used the third party "Lux Lite" app to get that reading). So it might be possible to work around this issue with a non-root Android app that controls the adaptive brightness setting based on the sensor reading.
[Nexus 6 Q&A, Help & Troubleshooting] pekcle:
I had no problems with Wi-Fi Analyzer. It was the TWC Wi-Fi Finder App that triggered it.
[Nexus 6 Q&A, Help & Troubleshooting] tehkraft:
Popping in to note that I have been able to reproduce this in safe mode (hold power to get "power off" and then long press power off)

It took a few moments of cycling adaptive brightness but this definitely eliminates third party apps as the culprit.
[Nexus 6 Q&A, Help & Troubleshooting] cyberon:
Does anyone else having this issue started recently using a smartwatch and the Android Wear application?

Can it be caused by bluetooth constantly searching for the watch?
[Nexus 6 Q&A, Help & Troubleshooting] sysfrog:
I neither use a smartwatch nor Android Wear. Just tried disabling Bluetooth, but still seeing the same issue.

---------- Post added at 02:44 PM ---------- Previous post was at 02:33 PM ----------

There were some speculations that this is caused/triggered by a hardware defect (as this only happens for a small number of people):

Some of the Nexus 6 phones have an issue where there's a small gap between the body of the phone and the display (next to the headphone connector and the SIM slot). The gap is not large, but still large enough to, e.g., insert a piece of paper (here's a picture: X://imgur.com/t7YXV0C (replace X with https)).

As the upper part of the display is where the brightness sensor is located, maybe that gap could somehow trigger the brightness issue? Does anyone else experiencing the brightness problem have this "display gap" on the phone?
[Nexus 6 Q&A, Help & Troubleshooting] cyberon:
Nope, my N6 doesn't have that gap.
[Nexus 6 Q&A, Help & Troubleshooting] pekcle:
If you really want to test it out, do a factory reset and try the same thing again. In that controlled environment, you can conclude whether third party apps, whether loaded or not via safe mode, triggers the brightness issue. I went through and tested, installing one app at a time. The fact that I could narrow it down to one app doesn't mean there aren't other apps that can cause it. I actually believe there are other apps that cause it. I verified it on more than one N6. I think it's an OS issue because it manages the hardware. Of course, yours really could be caused by hardware, but I see it as a systematic software bug in android itself. If you would dare to try that, perhaps it may help a few more people understand the scope of the issue.

Sometimes I wish Google paused a bit on the feature side and focus more on refinement. Even my N7 2013 on 6.0.1 has a consistent bug trying to disable anonymous usage reporting for TTS. Force closes every time. I lean closer and closer to jumping to the dark side each day (iOS).
[Nexus 6 Q&A, Help & Troubleshooting] veesix:
Strange enough, this happened for me right after updating to January image. I have now flashed MMB29Q, and had the issue once so far.
[Nexus 6 Q&A, Help & Troubleshooting] sprkat85:
Yeah this just started happening it bugs me so much I'm jumping to a new phone when I get to Delaware(no sales tax)
[Nexus 6 Q&A, Help & Troubleshooting] Slipknot8Wwe:
I disabled it and reenbled it and it solved the issue for me.

MellowRoms for the Nexus 6 and 5x has moved to Facebook

https://www.facebook.com/groups/212715385759035/
[Nexus 6 Q&A, Help & Troubleshooting] Matt4542:
Just started happening for me as well...