yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] nicky-xda:
compass / orientation not working?

Rotation of the home screen is working ok.

But the app "GPS Status" shows orientation, magentic field and rotation vector sensors as malfunctioning, also under the newest clean instal of LOS 15.1.

What about you others?
[Nexus 7 (2013) Original Android Development] Hatshipuh:
I had autorotation stop working entirely sometimes on previous build, no matter the setting it was stuck in portrait even when the device was in landscape all the time, but I didn't have it happen on the latest build yet.
[Nexus 7 (2013) Original Android Development] adstraylight:
I've been having this trouble intermittently, on the previous build as well as the current one (8.1). I think it occurs when the screen is activated and then turned off again in quick succession. Very hard to reliably reproduce though. It's like the sensors crash if they haven't been initialised fully before being deactivated.

I've had it happen when opening a 'smart case' (one with a magnet to activate the screen) slowly, as if the magnetic switch dithers in transition from one state to the other.

A reboot fixes it until the next occurrence, also autobrightness stops working at the same time..

It mostly happens after a period of deep sleep.

I should add that I'm using xposed, which is why I've been reticent about flagging this problem until now.

Another thing that may or may not be relevant is that I've noticed odd spikes in the battery graph.

Anyway, that's as far as I've got, hope it helps.
[Nexus 7 (2013) Original Android Development] adstraylight:
Battery graph example:
[Nexus 7 (2013) Original Android Development] adstraylight:
Just had autorotation fail, here's everything sensor related in the log:
[Nexus 7 (2013) Original Android Development] adstraylight:
To add to my last, sensors are currently working, but there's still a lot of errors and warnings in the log:
[Nexus 7 (2013) Original Android Development] Ziyan:
Those are actually normal; they happen on stock too. That's Qualcomm...

I made a lot of fixes some months ago to pass all sensor CTS tests, so overall, we're in a good shape.

That's weird, I thought I fixed that bug ages ago. I'll see if I find some time to look at it...

EDIT: does it happen if you don't use the smart case as well?
[Nexus 7 (2013) Original Android Development] adstraylight:
I don't know as it's always in the case, I'll try taking it out for a while, but maybe the previous posters can tell you...

[MENTION=2309048]nicky-xda[/MENTION] [MENTION=3975721]Hatshipuh[/MENTION]
[Nexus 7 (2013) Original Android Development] abhifx:
I had rotation along with compass failure, turns out it was a hardware problem. opened the tablet, removed the white ribbon, cleaned and reattached. everything is working so far.
[Nexus 7 (2013) Original Android Development] Hatshipuh:
I've been using a smart case all the time and as I said it happened frequently on previous build but not on the latest while still using a smart case. But then again I haven't been using the N7 as often lately.
[Nexus 7 (2013) Original Android Development] adstraylight:
I've had my tablet naked all day and been trying to make it break the autorotation, without success. So while I can't convulsively say, it seems that the trigger may well be the magnetic switch.
[Nexus 7 (2013) Original Android Development] braveheartleo:
FWIW, ever since I stopped using a smart cover for my Nexus 7 2013, I haven't had a single instance of rotation failing. This is in a span of a few months. However, I just tried using again the cover a few days ago, and from there I experienced rotation failure. This is still inconclusive proof because of the lack for tangible evidence (like the one for the infamous touch disease in certain iPhones), but I *strongly* believe the magnet from the cover has something to do with certain sensors failing in this tablet, thus rotation not working (until powered down or the mobo cable reseated, as a popular, temporary "fix" circulating online).
[Nexus 7 (2013) Original Android Development] adstraylight:
Here's a thing, I noticed when running without the case that the screen would wake when the charger was attached or disconnected. This set me wondering if there's some conflict between this and the signal from the magnetic switch when the case is closed?

I also found that even though the screen saver option was set to none, the activation point was set to 'charging' , so I set it to 'never'.

I've just checked my battery usage, and although it hasn't been on charge for some hours, it thinks that it is plugged in, but the odd power spikes I reported before seem to have gone.

I maybe making a leap here, but perhaps all these things are related? In that perhaps the screen has been trying to activate with the case closed?

Pure speculation of course...
[Nexus 7 (2013) Original Android Development] adstraylight:
Further to my last, I've also disabled screen waking on usb connection via the 'gravity box' xposed module as a possible workaround for the problem, and will report back any failure/presumed success in the coming days....?
[Nexus 7 (2013) Original Android Development] MikiGry:
Running latest experimental build. I noticed, that my flo gets very hot while watching YT. So I decided to check what's happening. Kernel Audiator shown me, that all 4 CPU cores are always online (even though this Qualcomm hotplugging thing is turned on). So I opened logcat extreme and i tons of MP decisions/core not being able to be switched off error appeared. Dirty reflash didn't help. I'm gonna do a clean flash in 4 days, but just before that I would like to know if someone else had this bug
[Nexus 7 (2013) Original Android Development] adstraylight:
Just had a look, and I don't see any errors related to mpdecision while playing YT, in either logcat or dmesg. Could you post an example?
[Nexus 7 (2013) Original Android Development] abhifx:
/OT

crap i seem to have botched usb port in this also, any recommendation for wireless charger?

HI! [MENTION=2633638]Ziyan[/MENTION], Good to see you again.
[Nexus 7 (2013) Original Android Development] MikiGry:
So it seems like dirty flash is responsible for that
[Nexus 7 (2013) Original Android Development] adstraylight:
I'd say so, or something you're modding in KA? I would also download a fresh copy of the ROM to eliminate the possibility of a slightly corrupt download.

Also make sure all your dev optiions settings are at default.
[Nexus 7 (2013) Original Android Development] MikiGry:
I haven't touched anything in KA or dev options that could cause that. As I said I will redownload and clean reflash the ROM in 3 days and report back
[Nexus 7 (2013) Original Android Development] adstraylight:
Just had 2 autorotate failures in 12 hrs....well, it was worth a try...
[Nexus 7 (2013) Original Android Development] adstraylight:
New build for Flo...so far so good:good:
[Nexus 7 (2013) Original Android Development] adstraylight:
Sorry to say, the sensors just broke again...
[Nexus 7 (2013) Original Android Development] MikiGry:
It seems like changing grovenor or enabling multicore powersaving pernamently breakes MP decisions. The only way to fix it back is to reflash the rom

Another thing

Screen is flickery on low brightness levels. On the lowest one its very flickery, little higher and its less ... on maximum brightness three is no flickering
[Nexus 7 (2013) Original Android Development] adstraylight:
More information on the sensors, a soft reboot isn't enough to reset them, only a full reboot or cold start will do.

(Flo/8.1)
[Nexus 7 (2013) Original Android Development] lightingcloud:
Hi guys, thanks for your hard work!

I've been out of the scene for a while, I came back to custom ROMs as I noticed that for *reasons* Netflix didn't show up on Google Play... I thought the reason might have been the old stock android version.

My problem is: I've been trying to install the 8.1 version, but I'm coming up with a problem with the 8.1 gapps: the installer says that the space in /system is insufficient! Am I doing something wrong? I go for the open gapps 8.1 micro pack...
[Nexus 7 (2013) Original Android Development] VictorLapin:
Pico is the only one package that'll fit AFAIK
[Nexus 7 (2013) Original Android Development] lightingcloud:
I'll just go for the 7.1 version then, no problem. :)
[Nexus 7 (2013) Original Android Development] adstraylight:
Anecdotal evidence about the sensor issue: clearing dalvik/cache seems to slow down the recurrence of the problem for a while, I'm guessing that dalvik is the key here as clearing cache alone has no discernable effect.

Hard to prove though, as the fault is intermittent.
[Nexus 7 (2013) Original Android Development] MikiGry:
Little feedback of latest (7.03.2018) build

I mostly use my flo for reading XDA and other forum + watching YT via YTvanced

Device feels very smooth and fast with some small lags here or there. Whenever it starts to lag too much i have to go to recent apps menu and clear it. After that its smooth again

Battery live

Its good. Much better with MPdecisions working :p

Todays score is 5h 44min of SOT with 1day 23h on one charge :)

Do not install kernel audiator and dont try to change any kernel setting because there is a good chace of pernamently bugging MPdecisions, with will lead to higher battery drain (since all cores all online all the time) and maximum DOT will decrease to 4h

Sensors

My flo has very common issue of randomly loosing auto-rotation due to faulty connector. I tried sticking some pices of paper between back cover and the connector to fix it but it didnt work. I do have parrot mod installed. I noiticed, that i dont have to reboot or clear cache/dalvic to bring it back because it come back on its own. All i have to do is wait. I suggest installing app called rotation controll. Whenever auto-rotation dies you will still have manual controll over it. So ROM doesnt have any problems with sensors. If You are expiriencing auto-rotate issues, than its yours tablet fault

So generally speaking. Rom is stable, fast and fluid. Geat work [MENTION=2633638]Ziyan[/MENTION]
[Nexus 7 (2013) Original Android Development] adstraylight:
I have to disagree with your conclusion that the rotation failures are due to a straight hardware fault, for the simple reason that it hasn't manifested itself during SOT.

The inconsistency of the issue is problematic though, but it is most likely to occur after long periods of deep sleep, suggesting to me that it's related to the power cycle, or more specifically the waking of the device.

I think a possible fix may be some means of routinely resetting the sensors on wake, to prevent the inconvenience to either waiting for the system to get around to doing this itself or rebooting.

I've only not had to reboot once but freely admit that I may just lack patience ?

EDIT: The answer to the query here might give a lead as to what's going on:

https://stackoverflow.com/questions...-stop-working-after-sleep-how-to-restart-them
[Nexus 7 (2013) Original Android Development] MikiGry:
[MENTION=2583740]adstraylight[/MENTION]

The problem is, that auto rotate stops working randomly. Not just after long time in deepsleep. For me it dies when im using using the tablet more often, then when im not. As i said, it comes back on its own. I dont have to reboot

Mebay its the thing, that im using parrot mod ? Its supposed to fix auto rotation issue

Parrot mod auto-rotate fix description (i had to put it as a screenshot because XDA app kept cuting it for some reason)
[Nexus 7 (2013) Original Android Development] MikiGry:
(sorry for double post, but i couldn't attach screenshot to the first one for some reason)
[Nexus 7 (2013) Original Android Development] adstraylight:
I also use parrotmod, but I'm sure that I've tried uninstalling it to see if it makes a difference....will try again just to make sure though.

Sounds like your experience is different to mine, which could imply a different cause, bit of a coincidence though...

EDIT: Just lost sensors even with parrotmod uninstalled ?
[Nexus 7 (2013) Original Android Development] abhifx:
well apart from sadness of failing sensors, work on android 9 seems to be up. dont know when our device will get the love but at least unlegacy team is working on it.
[Nexus 7 (2013) Original Android Development] adstraylight:
Yes, I've been watching gerrit with interest!?
[Nexus 7 (2013) Original Android Development] adstraylight:
Update: On reboot the tablet got stuck at the Google logo, had to reboot to bootloader, and power off. After this it booted normally.

I didn't reinstall parrotmod, and the sensors haven't failed - nearly 34 hrs uptime so far. I did have one instance of having to wait for them to wake for a couple of minutes, but that's it.

Edit: Totaly gone now, so not caused by Parrotmod.
[Nexus 7 (2013) Original Android Development] MikiGry:
Last idea. I'm using magnetic cover --> my magnetic sensor is in use all the time. Mebay that preventing sensors from going to "permanent sleep" ?
[Nexus 7 (2013) Original Android Development] adstraylight:
Could be, give it a try.. I didn't have any failures when I took the case off, but as it's hard to predict when it will happen, it's hard say when a possible solution is working.

EDIT: found an xposed module that disables the magnetic sensor, you never know.....
[Nexus 7 (2013) Original Android Development] adstraylight:
New build!

Trying with all sensors enabled again.....

Edit: nope...nothing seems to work, starting to think it must be hardware after all, bizarre that it only happens when waking the device though...
[Nexus 7 (2013) Original Android Development] lightingcloud:
Noob question time! I'm currently on unlegacy 7.1. If I wanted to update to unlegacy 8.1 I'd have to do a clean flash as if I were installing a new/different custom rom?

Edit: I don't really know what's up with this sensor issue... I'm having no problem at all and my tablet is always on, I use it in the morning when I wake up and before going to sleep. I have a magnetic cover, though...
[Nexus 7 (2013) Original Android Development] adstraylight:
I would clean flash between android versions.

Are you saying that you have no sensor issues on 8.1? It would be extremely helpful if other people could say if they're having similar problems, and when they started..
[Nexus 7 (2013) Original Android Development] adstraylight:
Latest: having restarted yet again, I'm now at 48hrs upttime....?

....and they're gone again... I don't think there's any point me posting any more about this...
[Nexus 7 (2013) Original Android Development] abhifx:
Have you tried the hardware hack? as it has resolved my issue almost permamently
[Nexus 7 (2013) Original Android Development] MikiGry:
[MENTION=2583740]adstraylight[/MENTION]

All of the sensors are gone or just a few of them ?
[Nexus 7 (2013) Original Android Development] adstraylight:
Most of the time I loose rotation, compass and light sensors at the same time. It only ever happens when the screen is off, often when charging. This is why I think it may be power related somehow. The Hall sensor (magnetic switch), and GPS seem unaffected.

Maybe I should try taking parrotmod out of doze....just a thought, worth a go anyway...

It could well be hardware, so when I think I've exhausted the software possibilities, and the Devs don't come back with anything, I'll look into that.

I've currently uninstalled the Google app as I've seen this cited as a possible cause.
[Nexus 7 (2013) Original Android Development] lightingcloud:
Sorry, because of the slow Internet connection I failed to realise it was about 8.1. I'll switch version as soon as I go back to civilization (I'm on 7.1 right now) and I'll let you know.
[Nexus 7 (2013) Original Android Development] adstraylight:
Ha! I may have just worked out the conditions for the sensors failing, it appears to happen when a change is required of the system based on sensor input soon after waking. For example, if the light level has changed since going to sleep, or I immediately turn the device to check they're still working.

So to test this theory, I've disabled adaptive brightness, and will resist the temptation play with the autorotation until I need to!

Will report with the almost inevitable disappointment soon....?

Edit: scratch that.....
[Nexus 7 (2013) Original Android Development] adstraylight:
Trying again this time with location + adaptive brightness disabled, and Nova Launcher set to default (portrait) orientation. This should hopefully prevent instant demands on all the affected sensors upon waking....

Edit: I give up...

Edit Edit: Just cleaned the contacts on the ribbon cable, will see how that goes with everything enabled....
[Nexus 7 (2013) Original Android Development] abhifx:
be careful as i have damaged my usb while doing it. i might have to rip off touch screen ribbon also to troubleshoot all the issue (touch is still dodgy).
[Nexus 7 (2013) Original Android Development] adstraylight:
Yes, I know how delicate things can be, having broken the WiFi terminals on my old grouper years ago? luckily this time things went well, and the device has been running for nearly 24hrs with no failures.

What finally convinced me was when the tablet fell over in its case, lost sensors immediately, and then was loosing them every time the screen went off.

I'm still perplexed as to why they were ok all the time the screen was active, the only thing I can think of is that they may go into a low power mode when sleeping, and the connection wasn't good enough to maintain this.

Hopefully, a couple of squirts of contact cleaner, will be the end of my woes!

Anyway, so far so good, thank you all for your patience!?
[Nexus 7 (2013) Original Android Development] abhifx:
Andrei Măceș maces already has unlegacy pie with everything working booted for Hammerhead. wondering will this help boot pie on our device. Good speed :D
[Nexus 7 (2013) Original Android Development] adstraylight:
I'm guessing that we'll see a release for mako first, but as the devices are so similar, deb/flo will soon follow...looking forward to it?

An update on the sensor situation, I'm now at 150hrs uptime, and no failures, so in my case it was definitely hardware (famous last words/tempting fate?)...
[Nexus 7 (2013) Original Android Development] abhifx:
Seems logical, but what i assumed that moving from 32bit snapdragon 800 to 600 (or s4 pro) should be easier.

Ziyan still seems busy so if other team members start working on our device, we will have to wait and watch.

also for the famous words "told ya" about the sensors.
[Nexus 7 (2013) Original Android Development] Clamor:
[MENTION=3692487]abhifx[/MENTION] [MENTION=2583740]adstraylight[/MENTION] Pie is still setting up on UA repos, I will start work as soon as possible, synchronous with Ziyan on mako.

P.S. My hh is on Pie now, it is almost same stable as Oreo.
[Nexus 7 (2013) Original Android Development] adstraylight:
Hmm, I had cause to reboot, and the sensor trouble has returned, so now I'm truly confused.....

I did see some power and wakeup stuff going into gerrit, so look forward to the next release with interest.
[Nexus 7 (2013) Original Android Development] abhifx:
good to hear! it seems even ziyan is active for mako.

i have already seen in hammerhead thread that pie is almost stable. is there any commonality between hh and razor?
[Nexus 7 (2013) Original Android Development] MikiGry:
[MENTION=3692487]abhifx[/MENTION]

Razor Flo/Deb are way closer to Mako since they share the same processor
[Nexus 7 (2013) Original Android Development] abhifx:
well as i have read elsewhere that even that is controversial as S4 pro on N7 is more akin to SD600 series. But i get it since oreo was also derived from mako. so yeah mako must be closer than hammerhead. I just wanted to know if HH development will have any influence on FLO?
[Nexus 7 (2013) Original Android Development] MikiGry:
I don't think so
[Nexus 7 (2013) Original Android Development] Clamor:
Solutions used in developing HH can be applied to other qcom devices as well. So yeah, generally all UA supported devices are tightly connected even if they use different hardware base.
[Nexus 7 (2013) Original Android Development] lightingcloud:
Is anyone else having playback issues with Netflix on latest 7.1?
[Nexus 7 (2013) Original Android Development] archish:
Any pie for flo? :D
[Nexus 7 (2013) Original Android Development] cnsultnt:
It has become very laggy for me (delay in responding to touch, Gboard takes a while to open, etc.). I did a clean flash, then restored apps from Titanium. Any suggestions?
[Nexus 7 (2013) Original Android Development] MikiGry:
1. Don't restore apps from TB (this can cause issues). Install apps manually from play store and restore their data

2. Lastest build felt very laggy for me as well. I think there is something wrong with kernel - hotplugging exactly. I'm my case flo was using 2/4 cores 90% of the time with occasional activity in 3rd core. I have never seen 4/4 cores running in that build.

Mebay install trimmer (fstrim) and run it on all partitions. This should help a bit
[Nexus 7 (2013) Original Android Development] cnsultnt:
Thanks, I had already tried fstrim. I guess I'll wait for a new version, or try another ROM.

TB doesn't backup data only; is there another tool, or you just save the Android/data directory?
[Nexus 7 (2013) Original Android Development] MikiGry:
TB backups both. But You can still install those apps manually and restore data only from TB
[Nexus 7 (2013) Original Android Development] Clamor:
A small announcement, N and O user builds with October security patches will be provided a bit later. I'm testing some blob improvements connected with Pie bringup and Oreo upgrading. And to prevent questions, NO, there are no builds for Pie at moment of writing this post, BUT we are actively preparing for releasing them same way Oreo builds were released (clean and stable;)).
[Nexus 7 (2013) Original Android Development] adstraylight:
The new build released yesterday (8.1) is running well, and seems somehow snappier than the last*, many thanks!

*Could be my imagination....?
[Nexus 7 (2013) Original Android Development] abhifx:
still makes this post more exciting even though no build for pie is posted :D
[Nexus 7 (2013) Original Android Development] cnsultnt:
Does seem more responsive, but just a bit.
[Nexus 7 (2013) Original Android Development] abhifx:
Actual things merged are on 26 oct so anything new should be in the next new build.

placebo maybe?
[Nexus 7 (2013) Original Android Development] adstraylight:
There were a few new commits in this build also, but very probable that I let myself get carried away in the post flash afterglow ?
[Nexus 7 (2013) Original Android Development] gunnerhk:
That happens to me too. It's the reason why my rom changes so much.
[Nexus 7 (2013) Original Android Development] cnsultnt:
Almost ready to give up on my beloved Nexus 7; responsiveness is gone. Would stock Marshmallow or a different ROM help? Is Unlegacy 7.1 faster than 8.1?
[Nexus 7 (2013) Original Android Development] rlw6534:
You might want to try Nougat 7.1.2, either Pure Nexus or Resurrection Remix 5.8.5 before you give up. I always seem to end up back there... ;)

I think I'll give UA 7.1 a shot next time around.
[Nexus 7 (2013) Original Android Development] MikiGry:
To avoid responsiveness loss you have to do 3 things:

1. Trim your tablet regularly

2. Watch your recent apps menu and close app, which you are no longer using

3. Scan it using SD main pro from time to time

And Your tablet should be fine :)
[Nexus 7 (2013) Original Android Development] lollyjay:
My flo 32gb is very smooth and responsive with this ROM.
[Nexus 7 (2013) Original Android Development] Clamor:
If someone still didn't notice, builds with November security patch were released ~12 days ago. They include some binary improvements and further separation of vendor staff.

[MENTION=5047191]cnsultnt[/MENTION] well, few builds ago 8.1 had microlags, but now at least I can't notice any lags. I use latest 8.1 build with micro gapps. It even doesn't heat so much as it did before on 8.1 builds.