Develop Bugs

Face Unlock Lag

Is anyone here experiencing this bug:
http://code.google.com/p/android/issues/detail?id=23197
The lag happens BEFORE the face recognition takes place. It's clear the lag does not come from the face recognition. Instead it's probably coming from the time it takes for the camera to launch/activate. Now, the lag is not serious, but it did tend to get worse. However, I am very very sure that when I receive the Galaxy Nexus the first day, the lag wasn't there. The camera was ready to recognize my face almost instantly. I have 4 Galaxy Nexus in my family, and I had to set up the phone 4 times, so I am pretty sure that Face Unlock starts up really quick the first day.

Honestly I think it's just Android itself. The longer you own an Android phone and the more you use it, the laggier it gets :/ .

Game4set said:
Honestly I think it's just Android itself. The longer you own an Android phone and the more you use it, the laggier it gets :/ .
Click to expand...
Click to collapse
Well, this is applicable to almost every OS. It happened to my Mac, my Windows 7 PC, and a quick search in Google reveals many iPhone users complaining about the same thing (of course, they won't admit it publicly -- but they can't hide it in a Mac oriented forums ;-))
But it doesn't feel right in this case because the lag actually seems coming from the fact that the camera or the Face Unlock app wasn't in the memory ready to be used. If this is in fact the case, there are things Google can do to improve the experience.
On a side note, if I recalled correctly, I used to see Face Unlock in my running app list, but I no longer see it now. I wonder if this has anything to do with this bug.

Yes! I've been noticing this. And it is definitely only since I got the 4.0.2 update a couple of days ago. Before that it was near instant, now it lags
Although I have to admit, it recognised my face so poorly with 4.0.1 that I had to turn it off. Now with improved face matching I can use it all the time, I just hope they fix the lag.
Maybe someone running a custom rom on 4.0.3 can confirm whether they have the lag too.

case0 said:
Yes! I've been noticing this. And it is definitely only since I got the 4.0.2 update a couple of days ago. Before that it was near instant, now it lags
Although I have to admit, it recognised my face so poorly with 4.0.1 that I had to turn it off. Now with improved face matching I can use it all the time, I just hope they fix the lag.
Maybe someone running a custom rom on 4.0.3 can confirm whether they have the lag too.
Click to expand...
Click to collapse
Face Unlock rarely has problem recognizing my face. When Face Unlock fails to work, it's almost always due to the lighting -- I could barely see my face from the camera's preview myself at those time, how could I expect the phone to recognize me? Generally speaking, if my face is right around where the dotted face outline is, and there's is enough light for me to see my face in the camera preview, Face Unlock always work for me.
I was also suspecting the 4.0.1 update was the cause of problem. I just didn't have the time to confirm it.

I get this too. I wonder if its that it has more pictures to use to analyze in 4.0.2 vs 4.0.1. It annoys me that it takes just a little too long.
---------- Post added at 11:34 PM ---------- Previous post was at 11:18 PM ----------
Does anyone with a 4.03 rom have lag on face unlock?
I bet it happens over time because we start to load apps and android naturally bumps the camera out of memory and so each time we go to screen unlock it has to load it up and start the camera which takes a bit of time.

spinkick said:
I get this too. I wonder if its that it has more pictures to use to analyze in 4.0.2 vs 4.0.1. It annoys me that it takes just a little too long.
---------- Post added at 11:34 PM ---------- Previous post was at 11:18 PM ----------
Does anyone with a 4.03 rom have lag on face unlock?
I bet it happens over time because we start to load apps and android naturally bumps the camera out of memory and so each time we go to screen unlock it has to load it up and start the camera which takes a bit of time.
Click to expand...
Click to collapse
I don't think it has to do with more pictures to analyze. I've tried clearing all the data and start from scratch, but it did not fix the problem. Also, the actual facial recognition work really quick -- if having more picture is affecting it, it will be because there're more data needed to be read to initialize the app. However, I see no reason why the app needs to load all the data before it even starts to recognize the face.

New Gnex owner here (of a grand total of 3 days). Rooted my phone my first day, flashed milestone 4, and all is good--except the face unlock screen seems to take 1-3 seconds to boot up the camera.
I don't recall it being an issue on day 1, but it is definitely now noticeable. I love the feature and would be immensely satisfied if the delay could be minimized...does anyone NOT have the lag?

givonion said:
New Gnex owner here (of a grand total of 3 days). Rooted my phone my first day, flashed milestone 4, and all is good--except the face unlock screen seems to take 1-3 seconds to boot up the camera.
I don't recall it being an issue on day 1, but it is definitely now noticeable. I love the feature and would be immensely satisfied if the delay could be minimized...does anyone NOT have the lag?
Click to expand...
Click to collapse
Yup, same here. This feature is really useful for a phone as big as the GNex -- it's not that easy to swipe unlock with just one hand. I am using 4.04 and the bug still hasn't been fixed. I have tried all kind of tweaks, and none of them work.
I suggest you to comment on the official issue tracker and "star" it. The more people complain about it, the higher the chance it gets fixed soon.

I've only started using Face Unlock for a few days on 4.0.2 and only then to impress girls. I haven't experienced any lag so far. Face Unlock takes some time to set up for me though, and I have to tilt the phone in a unnatural angle to allow the camera to see my whole face.

Same issue here, after yesterday's update to 4.0.4 the camera literally never starts. Just a blank screen with clock and no back software button. I have to press emergency dial then back to get to the pattern lock. Happens 1 in 5 times I try to unlock.

I updated my Galaxy Nexus with Jelly Bean and Google seems to put a "fix" to this bug. Before you celebrate, here's the bad news -- no, I don't think they actually "fix" the underlying problem. In Jelly Bean, when you wake your phone up to use Face Unlock, instead of seeing a black screen, there will be an "animation" that gradually transits from a black screen to the camera. Amazingly, that simple trick seems to make the lag much less annoying, to the point that I don't feel there's a lag at all.

Game4set said:
Honestly I think it's just Android itself. The longer you own an Android phone and the more you use it, the laggier it gets :/ .
Click to expand...
Click to collapse
but it will never lag after a reboot. *the first 20 mins*

zeke1988 said:
but it will never lag after a reboot. *the first 20 mins*
Click to expand...
Click to collapse
I don't know about you, but I still saw the lag sometimes after I rebooted (with ICS.)

Fix ....Ok I think I've done it but need further testing ...
Ok I think I've done it but need further testing ...
Only possible on rooted devices ..
Go to folder
/data/data/com.android.faceunlock/shared_prefs/
in your root enabled file browser (I used es file explorer)
Open the file inside
Edit delay number to 1
Save file
Then change permissions to read only by all
And ownership to root
Go 1 level up and do the same with the shared_prefs folder (perm and owner)
And again 1 up and same settings to the com.android.faceunlock
Come back here and report if it improved
Not sure if all the permissions must be like that but I went safe on it since file got replaced first few times I tried
Please do.come back here to report if it worked for you too
My delay was 1730 after changing to 1 it worked like charm once but then it changed to ~700(file got updated again) then I've changed the settings of files and folders to present override and now I did not experience the lag yet
Let me know if you need more info or more detailed instructions 0,O
Also I feel I should mention ive done it on moto g 1st gen running 4.4.4
And that minimum time for it to open is same as time it takes to swap from back to front camera in your stock camera app plus time it takes to detect light conditions and in dark places it takes longer to do that

[Q] Random Crashing

Very similar to comments here, I am having seemingly random crashes on my beloved E980. It was running perfectly fine for many months on CM10.2 + TWRP. The crashes started happening fairly soon after replacing the screen (about same time I flashed to CM11 as well). Two days ago, I used the Hyelton/Madmack .tot method and [successfully] installed two different stock firmware versions with the same results [after maybe a couple hours it will intermittently start crashing again]. I can't seem to ascertain if there are things that provoke it to crash. Sometimes it'll do it after sitting with screen off for some time, but more often it'll happen while under medium to high utilization. There is plenty of free RAM and Flash memory.
Before buying a parts phone from eBay with a broken screen and throwing parts at it I thought I’d first take it apart and see if anything jumps out at me and cross my fingers that it would just work after reassembly; I haven’t done this yet – maybe tonight. I think I've verified that it is a hardware issue at this point, but I was hoping to narrow it down a bit closer – there doesn't seem to be an abundant supply of eBay parts phones right now and I hate guess and buy an unneeded sub-component.
I also thought I’d go ahead and try to capture some log files utilizing methods found here which I have done. Attached is a Logcat file which ran until the phone crashed. I was unable to export a Dmesg log; whether in adb or terminal emulator I get “klogctl: Operation not permitted”. I tried to get a Last_kmsg log but the file is missing after rebooting from crash. I did get exports from error-free reboots before and after the crash which I’ve also attached. I browsed to /cat/proc and sure enough there was no “last_kmsg” subfolder. The phone was sitting with screen off on my desktop for maybe an hour when I heard the USB chime that it disconnected.
Has anyone got some ideas for me to try?

jimmylomax said:
Very similar to comments here, I am having seemingly random crashes on my beloved E980. It was running perfectly fine for many months on CM10.2 + TWRP. The crashes started happening fairly soon after replacing the screen (about same time I flashed to CM11 as well). Two days ago, I used the Hyelton/Madmack .tot method and installed two different stock firmware versions with the same results. I can't seem to ascertain if there are things that provoke it to crash. Sometimes it'll do it after sitting with screen off for some time, but more often it'll happen while under medium to high utilization. There is plenty of free RAM and Flash memory.
Before buying a parts phone from eBay with a broken screen and throwing parts at it I thought I’d first take it apart and see if anything jumps out at me and cross my fingers that it would just work after reassembly; I haven’t done this yet – maybe tonight. I think I've verified that it is a hardware issue at this point, but I was hoping to narrow it down a bit closer – there doesn't seem to be an abundant supply of eBay parts phones right now and I hate guess and buy an unneeded sub-component.
I also thought I’d go ahead and try to capture some log files utilizing methods found here which I have done. Attached is a Logcat file which ran until the phone crashed. I was unable to export a Dmesg log; whether in adb or terminal emulator I get “klogctl: Operation not permitted”. I tried to get a Last_kmsg log but the file is missing after rebooting from crash. I did get exports from error-free reboots before and after the crash which I’ve also attached. I browsed to /cat/proc and sure enough there was no “last_kmsg” subfolder. The phone was sitting with screen off on my desktop for maybe an hour when I heard the USB chime that it disconnected.
Has anyone got some ideas for me to try?
Click to expand...
Click to collapse
so you're saying that when you use hyelton method 2 and flash 20g that it fails while running 20g? try a different usb cable, too. EDIT - also different usb port. also watch for static electricity - I ground myself before touching cpomputer...

KrisM22 said:
so you're saying that when you use hyelton method 2 and flash 20g that it fails while running 20g? try a different usb cable, too. EDIT - also different usb port. also watch for static electricity - I ground myself before touching cpomputer...
Click to expand...
Click to collapse
No, sorry, I maybe glossed over that part. I successfully flashed to the stock firmware just fine. The phone ran well the remainder of the day.
I then rooted it, installed Titanium Backup, and then installed TWRP. I made a couple TWRP backups as I slowly started reinstalling apps with TB and Play store. Similar to the 4 or 5 times I tried re-flashing cyanogenmod, it seems to get worse and worse over time. In the past flashes I have experimented with not using TB and leaving it alone for a day or two with the same result. Since I have TWRP and many backups, I can definitely experiment further trying things.

jimmylomax said:
No, sorry, I maybe glossed over that part. I successfully flashed to the stock firmware just fine. The phone ran well the remainder of the day.
I then rooted it, installed Titanium Backup, and then installed TWRP. I made a couple TWRP backups as I slowly started reinstalling apps with TB and Play store. Similar to the 4 or 5 times I tried re-flashing cyanogenmod, it seems to get worse and worse over time. In the past flashes I have experimented with not using TB and leaving it alone for a day or two with the same result. Since I have TWRP and many backups, I can definitely experiment further trying things.
Click to expand...
Click to collapse
try process w/o twrp, please.
---------- Post added at 02:32 PM ---------- Previous post was at 02:25 PM ----------
also different cable and different usb port.

this is a bummer, man.
KrisM22 said:
try process w/o twrp, please.
---------- Post added at 02:32 PM ---------- Previous post was at 02:25 PM ----------
also different cable and different usb port.
Click to expand...
Click to collapse
Right - I was thinking the same thing. So, early this afternoon I did reflash (with "BIN_LGE980AT-00-V20g-ATT-US-APR-28-2014+0.tot") one more time and did only the following:
Skipped wifi setup, disabled "back up [and restore] data from google account". Rebooted
Went straight to app store and disabled auto download/update
Received notification that Google Play Services needed updating or something - I clicked the notification in order to read entire message and I think it just updated it?
set Hangouts as default messenger. Rebooted once again.
Then, I just tried to heavily use it. I used Maps navigation, took a bunch of rapid fire photos, Gmail, Chrome, etc. It worked great for about 3 hours until I got my first crash while taking some photos and attaching to a few rapid-fire hangouts messages. I removed the external flash card, but left SIM card and rebooted. It crashed one or two more times in the next 5 minutes. Since then it has crashed while using it maybe twice and once or twice while it should have been sleeping.
Any use in trying to capture event logs or should I just go ahead and dig out my phillips 00 screwdriver and tear into it?
I did use a different cable on the same port, but I'm confident my cables and ports are good.

jimmylomax said:
Right - I was thinking the same thing. So, early this afternoon I did reflash (with "BIN_LGE980AT-00-V20g-ATT-US-APR-28-2014+0.tot") one more time and did only the following:
Skipped wifi setup, disabled "back up [and restore] data from google account". Rebooted
Went straight to app store and disabled auto download/update
Received notification that Google Play Services needed updating or something - I clicked the notification in order to read entire message and I think it just updated it?
set Hangouts as default messenger. Rebooted once again.
Then, I just tried to heavily use it. I used Maps navigation, took a bunch of rapid fire photos, Gmail, Chrome, etc. It worked great for about 3 hours until I got my first crash while taking some photos and attaching to a few rapid-fire hangouts messages. I removed the external flash card, but left SIM card and rebooted. It crashed one or two more times in the next 5 minutes. Since then it has crashed while using it maybe twice and once or twice while it should have been sleeping.
Any use in trying to capture event logs or should I just go ahead and dig out my phillips 00 screwdriver and tear into it?
I did use a different cable on the same port, but I'm confident my cables and ports are good.
Click to expand...
Click to collapse
yup, bummer. no twrp and new cable. I'm stumped. a log would mean nothing to me - maybe hyelton.
Wondering if prob happens when it warms up and expansion causes a break in connection. yeah, man the screwdriver. Wish I could be of more help.

Its a long shot, but it could be a faulty battery. Does it crash when the phone is fully charged and plugged into the original 2amp charger? If yes, then its probably not a faulty battery. If no, and it crashes off the charger, especially with a battery <75% then it could be a faulty battery.
Sent from my LG-E980 using XDA Free mobile app

Touch input temporarially stops working until after phone goes to sleep

Sprint LG G3, the 990 version. Stock ui.
So yesterday this all started. The touch sensor suddenly stopped registering inputs. From my testing on it (this problem has happened dozens of times since yesterday afternoon) eventually after a few minutes of use the input will just stop working, but the phone functions still work. Videos and games continue to play, phone and video calls still keep running properly, and the home screen clock will keep running while the touch input is disabled. I can volume up and down, but cannot interact with the screen. The power button will not put the screen to sleep.
Eventually the screen will timeout, now I can interact with it again. I hit the power button like normal, and get a vibration, then the screen turns on and I get the dialog box to turn off or restart the phone over my lock screen, as if I long-pressed the power button. I can click away from this and start using the phone again like normal.
But it will happen again. I can get a few minutes of use usually before the touch input disables itself again.
I didn't download anything recently. I did disable notifications for my LINE app yesterday through the app drawer, but after this started I reverted that, just to be sure. Some apps might have auto updated, but this is happening in any app I use.
I have looked around lots of places, but can't find anyone else saying they have this particular problem. Any idea what is going on and how I can troubleshoot this short of trying a factory reset?

superbelt said:
Sprint LG G3, the 990 version. Stock ui.
So yesterday this all started. The touch sensor suddenly stopped registering inputs. From my testing on it (this problem has happened dozens of times since yesterday afternoon) eventually after a few minutes of use the input will just stop working, but the phone functions still work. Videos and games continue to play, phone and video calls still keep running properly, and the home screen clock will keep running while the touch input is disabled. I can volume up and down, but cannot interact with the screen. The power button will not put the screen to sleep.
Eventually the screen will timeout, now I can interact with it again. I hit the power button like normal, and get a vibration, then the screen turns on and I get the dialog box to turn off or restart the phone over my lock screen, as if I long-pressed the power button. I can click away from this and start using the phone again like normal.
But it will happen again. I can get a few minutes of use usually before the touch input disables itself again.
I didn't download anything recently. I did disable notifications for my LINE app yesterday through the app drawer, but after this started I reverted that, just to be sure. Some apps might have auto updated, but this is happening in any app I use.
I have looked around lots of places, but can't find anyone else saying they have this particular problem. Any idea what is going on and how I can troubleshoot this short of trying a factory reset?
Click to expand...
Click to collapse
Boot.into safemode i cant remeber the key sequence google itll disable all 3rd party apps then if it work u know its in a app
---------- Post added at 12:52 AM ---------- Previous post was at 12:50 AM ----------
Further more if it does not help then a factory restore is in the pic. Then of that dont work try restoring stock tot.kdz method and flash tool it is possible for system to corrupt files and reset still not fix.
---------- Post added at 12:53 AM ---------- Previous post was at 12:52 AM ----------
Are u root ed stock rom cm kernals ?

TheMadScientist420 said:
Boot.into safemode i cant remeber the key sequence google itll disable all 3rd party apps then if it work u know its in a app
---------- Post added at 12:52 AM ---------- Previous post was at 12:50 AM ----------
Further more if it does not help then a factory restore is in the pic. Then of that dont work try restoring stock tot.kdz method and flash tool it is possible for system to corrupt files and reset still not fix.
---------- Post added at 12:53 AM ---------- Previous post was at 12:52 AM ----------
Are u root ed stock rom cm kernals ?
Click to expand...
Click to collapse
Hey, thanks for the reply. So I did what you said. I ended up doing a factory restore of my device.
I have had this phone since about a month after it was released two years ago. I rooted way back then, did not install any rom over it yet... and then a few weeks later my kid went and clicked through a software update one day and removed my root, so I just left it go.
Anyway, I did the full factory reset, and started setting my phone up again, and a couple times the problem resurfaced. No apps from the store yet installed, the phone just stopped responding to any touch inputs. I wait for it to go to sleep, and then wake it up to use it again.
This sucks, I guess this is forcing me to upgrade when the G5 releases. But any ideas still? I dread being stuck with the phone being buggy like this for another two months or so. It's not app related, it doesn't SEEM to be hardware based, since everything works perfect up until it just locks up. The problem happens with different batteries I use. There doesn't appear to be any physical damage to the phone at all.

Upgrade to Nougat already? Hows it working for you?

For those who have upgraded already, how did the upgrade process go and how are you liking it so far?
This is a big upgrade and I'm nervous about pulling the trigger until this is vetted out a bit.
Chris

The process went well. I had to play with the display resolution and zoom to get things looking right. I had to re install my theme store theme to get it back. Other than that, it runs great. Only a few apps not compatible with n. But I have like 400 apps. So not bad! Oh yes, I did need a couple of reboots too.

Sweet! Well... having to go five steps back first was a PITA but when finished (and thank God for the Samsung Cloud Backup System - I had just done a backup three days before this project and it saved my arse!) Once I finished the AT&T OTA of QB2, I did a Restore from the Samsung Cloud and the phone looked EXACTLY like it had with Nougat PL4! Desktop, Apps, (most) settings... awesome!

Going good, process went smooth. I'd just say plug up and stay plugged during upgrade

Just did the upgrade. I have to say guys, this was BY FAR the smoothest stock upgrade I've ever experienced from Samsung. They did a nice job on this.

I'm just running into the issue of UI Lag. The update went smooth enough though. I will also say I am having issue with video playback in chrome if I flip to fullscreen then the ability to control the video is gone and i cant minimize it i have to hit the home key to get out of the video.

I just finished installing QB2. Everything works smoothly except one annoying bug. The Activity Zone app launch not in full screen. It's like 70% of the screen. I tried to change the display resolution but the same.
Anyone having the same issue?

snugroho3 said:
I just finished installing QB2. Everything works smoothly except one annoying bug. The Activity Zone app launch not in full screen. It's like 70% of the screen. I tried to change the display resolution but the same.
Anyone having the same issue?
Click to expand...
Click to collapse
No, mine launches full screen!
---------- Post added at 03:46 PM ---------- Previous post was at 03:45 PM ----------
CFoote said:
Just did the upgrade. I have to say guys, this was BY FAR the smoothest stock upgrade I've ever experienced from Samsung. They did a nice job on this.
Click to expand...
Click to collapse
DITTO!

jimd1050 said:
No, mine launches full screen!
---------- Post added at 03:46 PM ---------- Previous post was at 03:45 PM ----------
DITTO!
Click to expand...
Click to collapse
Yes, it launch in full screen but the content of the app is not. Please see attached picture. Do you have the same?
It was full screen in marshmallow

That is quite strange, my Activity Zone is full screen, do you have your Zoom function under "Display" set to small?

Upgrade went smooth , i did it manually and not OTA , all working good with good battery life.
What i did is as follows :
1- Odin the PI2 as a base line
2- Then via recovery from the device I used "update from SD card" and upgraded to PK2
3- Then i did it again via recovery from the device I used "update from SD card" and upgraded to QB2
Download the needed files from the following thread
https://forum.xda-developers.com/s7-active/how-to/s7-active-sm-g891a-ota-updates-firmware-t3540866

I updated to the BQB2 build via OTA about a week after it became available. I'm generally pleased with it, but there are a few things here and there that make me think that perhaps I'm due for a factory reset and start over.
Battery life is slightly down for me, which doesn't match up with reports I'm hearing from others. It's not much lower, but it's noticeable.
UI seems to be slightly more 'laggy'. Reduced the animation scales in the dev options to compensate. Maybe because I was running 'Good Lock' when the update happened?
Seems like wifi connection is not 100% stable. I see the notification bar 'flicker' from time to time, and it keeps re-posting the notification about what network I'm connected to.
Seems to get warmer while charging wirelessly, to the point that it pauses the wireless charging. But, this is in a cradle in my car, with Waze running, and it's warmer than it had been for a few months so not really sure if the update is involved in this or not.
Probably one or two other smaller things that I'm not thinking of at the moment. Obviously they weren't showstoppers, since I can't recall right now.
I like that they included the mobile hotspot toggle again (finally!), but they still don't have a 'mobile data' one. System UI Tuner is still gone, although I've read some people think that's the case with Nougat in general, so not sure.
All that being said, it updated to the BQC2 build today. The wifi thing seems to be resolved, despite this being only a 'security update'. I'll let it shake out for a few days or so and see if I still think it's worthwhile to start all over.

Went smooth for me, took literally less then 2 minutes.
All my apps/settings are working flawlessly and I experienced no issues thus far.

I updated to Nougat since it was released and I can't say I'm happy. Battery looks slightly worse and at least 1 or 2 twice a week my phone slows down getting almost unresponsive. I have to restart it.
That never happened with Marshmallow. I'll try it for one more month and if not I will go back to Marshmallow. Is that still possible?

That is a good question. I know that with small version upgrades the phone keeps the original version stored for a full wipe, but on a big OS upgrade I am not sure. Hopefully someone will know. I want to say yes it can be done.

Im on QD4, loving Noguat at how quick it is. But, i hate how all the menus and settings are all bunched and i have use search to find basic things.

I actually am having some issues with my s7 active I installed the 7.0 update a few months back and never looked back because the 7.0 stock rooms great no issues except recently last week's my phone started rebooting on its own . I though no biggie cause it did every once in a while , but now it has greatly increased . What happen was it froze on Facebook messenger app when I was trying to reply to a message and would not unfreeze so I had too force restart it that is when the problems really begun. The moment I force restarted it and it rebooted and i got into hone screen i keep getting notifications that apps were crashing over and over and the phone decided to restart on its own and keep doing the same thing . So I was like wtf maybe it's a app or something so I decided to do a factory reset and clear cache and rebooted the phone looked like that fixed the problem for a whole 2 minutes then the crashing of apps and random restarts . I was tired so.i was like ok I just turned the phone off and notice that it was kinda warm and decided to go to bed and mess with it tomorrow . So when I woke up I booted the phone up and it was acting normal no crashing or anything no reboots but after 2 hours it randomly started rebooting and sometimes the apps crash bit currently the phone is working but i get random freezes and reboots all day . I have tried searching for a solution but no luck. Some people claim its a app but when I have no apps Installed and it still does it its not a app problem . Some people say it could be the mother board flus faulting out or bad battery can't send it in for repair cause I bought the phone off eBay. Is anyone else having these issues and know of a fix maybe thanks sorry for the long post.

Upgraded to BQB2 a week ago, I am very happy with everything, it's smoother, faster and manages RAM better (well I was Rooted on 6.0.1 so it was laggy) all my apps work perfectly and I've disabled many things with Package Disabler Pro, I've been testing running music, google maps chrome, whatsapp, messenger, face all at the same time, very smooth BUT I must say it does drain battery much faster than before.
Now my phone wont make it through the day, it even drains on standby, I've already flashed 7.0 twice and wiped cache, I'm still, thinking if I will keep this or go back to 6.
Yesterday alone, my battery went from 89% at 1:30am to 52% at 10:30am, only on standby. When I check Battery use my com.android.systemui is the one eating up most of it, I even set my resolution low to HD. If anybody has a solution, any help would surely be appreciated, I don't wanna go back to Marshmellow, but if I must......

Upgraded and everything was fine apparently, then I saw the huge battery drain, tried averything I found and decided to go back to marshmallow.

KGB7 said:
i hate how all the menus and settings are all bunched
Click to expand...
Click to collapse
Can you please provide screen shots?
There are 2 more ups after QD4 (side load), I need to know if I should be prepared to go that far if I proceed with QD4.

[Solved] Robin isn't using smart storage

I bought a Robin a week ago and since I have it, cloud used space is 0b, I've activated everything and still not working.
However, at the night, when I put my Robin to charge, the back four LEDs begins to blink as if the phone was making the backup.
Is anyone else having the same issue?
Edit: Razer fixed the issue, now is working perfectly

pablomancera said:
I bought a Robin a week ago and since I have it, cloud used space is 0b, I've activated everything and still not working.
However, at the night, when I put my Robin to charge, the back four LEDs begins to blink as if the phone was making the backup.
Is anyone else having the same issue?
Click to expand...
Click to collapse
I am too, the lights light up, but the apps say they're not backed up
---------- Post added at 06:38 PM ---------- Previous post was at 06:32 PM ----------
O, it says on their website they stopped the support and services on August 1st

I don't think that is the reason, plus, software support ends in February 2018

Even though the software support ends (which mainly is the device's firmware support) I think the cloud storage has been slowly shut down.
Within few weeks of announcement of the end of Robin they had shut down the cloud storage web interface login , so no surprise that the cloud storage is gone too.

But still don't think so, in Razer forums, they said they will look into that problem, and even they are thinking of updating the device to Oreo, I hope this is an error

Smart storage has been fixed, is working right now!