[Q] No response from sensors until reboot. - Nexus 5 Q&A, Help & Troubleshooting

My accelerometer and other various sensors stop responding randomly, making pretty much any app that requires them unusable, including games, anything with auto-rotate, the camera (photo spheres mostly) etc. All the sensors appear to fail at once and the only way to get them working again is a reboot. I'm stock, rooted, with franco kernel, and running Xposed with only gravitybox installed. I'm not sure exactly when this started so i'm not able to trace it to a particular app, but I don't think it would make much of a difference because I have tried restoring the system partition as well as removing Xposed and reverting to the stock kernel. I wasn't able to format /data and test because for some reason the nandroid backup failed when trying to back up the data partition. (not sure if this could be related...). Anyways I checked logcat and there doesn't seem to be anything helpful: there is no output at all when trying to auto-rotate etc. but I will continue troubleshooting... Does anyone know the best way to approach this or has had this happen before? This is weird and frustrating...
Here is a screenshot of Sensor Node from the play store after the sensors go dry...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Apparently proximity still works... yay?

Alias.TDP said:
My accelerometer and other various sensors stop responding randomly, making pretty much any app that requires them unusable, including games, anything with auto-rotate, the camera (photo spheres mostly) etc. All the sensors appear to fail at once and the only way to get them working again is a reboot. I'm stock, rooted, with franco kernel, and running Xposed with only gravitybox installed. I'm not sure exactly when this started so i'm not able to trace it to a particular app, but I don't think it would make much of a difference because I have tried restoring the system partition as well as removing Xposed and reverting to the stock kernel. I wasn't able to format /data and test because for some reason the nandroid backup failed when trying to back up the data partition. (not sure if this could be related...). Anyways I checked logcat and there doesn't seem to be anything helpful: there is no output at all when trying to auto-rotate etc. but I will continue troubleshooting... Does anyone know the best way to approach this or has had this happen before? This is weird and frustrating...
Here is a screenshot of Sensor Node from the play store after the sensors go dry...
Apparently proximity still works... yay?
Click to expand...
Click to collapse
If a reboot fixes it, then it's probably a software side problem. Do you have the latest CWM verson? Try using TWRP to backup.

I am on stock at the moment. I decided to try wiping /data manually and reinstalling a few apps at a time to see if I can recreate the problem
Sent from my Nexus 5 using Tapatalk

Alias.TDP said:
I am on stock at the moment. I decided to try wiping /data manually and reinstalling a few apps at a time to see if I can recreate the problem
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
As much of an effort as this is, it really is the best way to help identify the problem.

Do you use the barometer? It is a known bug that after some time the barometer and other sensors stop working.
Sent from my Nexus 5 using xda app-developers app

Yes I do have an app that constantly probes the barometer
Sent from my Nexus 5 using Tapatalk

Had the same problem using the app PressureNET. Uninstalled it and now everything is fine.
Sent from my Nexus 5 using Tapatalk

Same problem happened here around the time I installed some barometer reader. I will try to remember posting a follow up in about a week after just having deleted the app and rebooting.
Thanks so far for a possible candidate on what causes this and also thanks for starting a thread and mentioning the app used for verifying the sensor read outs.

After a clean wipe no problem until I re enabled my barometer widget...
Sent from my Nexus 5 using Tapatalk

Related

Navigation stuck on searching for gps

Ok maps it locks on, GPS status app shows sats but no fix on any of them even outside. Tried flashing the sgs3 GPS fix, the Google universal fix, and still nothing. I mean it says lock in status when I open maps, and has me in the general area, but no luck with nav. I've tried restoring backups, no dice, even with fixes. Never installed an aosp Rom. So Idk what happened this weekend worked on my way to the hotel for this trip, and I go today to set it for home and it wouldn't lock on and has nav stuck in that parking lot. Even after restores, or a full wipe and new Rom install, uninstall maps, everytime I reopen nav it's still I'm that lot and I'm not even in the same town.
Sent from my SCH-I535 using xda premium
Please call Verizon and report your issue. I just got off the phone with Tier 2 support today and they claimed to have zero reports of this problem. I told them that I had seen "many, many reports" of this problem on XDA.
But see what I don't get us I've never had this problem until this weekend. Same Rom non-stop so Idk
Sent from my SCH-I535 using xda premium
Unless you are on Verizon's paid navigation app that would be a Google problem and not a Verizon problem. Server may have been down. My Google navigation works.
prdog1 said:
Unless you are on Verizon's paid navigation app that would be a Google problem and not a Verizon problem. Server may have been down. My Google navigation works.
Click to expand...
Click to collapse
I'm still having the problem pr. Here's what I've got.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
no fix, but says fix is on or w/e it says by the time. then here's maps loading directions fine ... but here on the nav it still has me in that hotel parking lot lol. I've even let it sit for an hour without screen off no luck. It had to be some service/file somewhere not getting wiped or something Idk. Anyways I just got back from a few hour drive so I'll be checking on this in a few hours after a nap lol. Thanks for any help anyone can dig up.
Sent from my SCH-I535 using xda premium
Well that's weird, now all of a sudden it's getting a fix on some sats but my compass is reversed. And now with getting the fix the nav has reset itself. I don't get it, that hotel had to have a blocker or something ha ha
Sent from my SCH-I535 using xda premium
xM Minton Mx said:
Well that's weird, now all of a sudden it's getting a fix on some sats but my compass is reversed. And now with getting the fix the nav has reset itself. I don't get it, that hotel had to have a blocker or something ha ha View attachment 1420709
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Looks like everyone's compass is off.
Yeah I seen that in the jelly bomb thread. Grr Idk Wth is going on. But like I said it all happened Saturday.
Sent from my SCH-I535 using xda premium
Same issue here I was testing out some new ROMs and thought it may have been a bad flash. I went back and restored 4 backups full wipes and cant get any of them to lock on including stock prior to OTA update recently.
Well it looks like it was magically fixed by Verizon. Atleast for me it did.
Fix that worked for me
I had this issue. I believe I caused it by mucking around trying to make my GPS fix faster. Symptom was simple - GPS knew where I was - just did not register any accuracy (in GPS Status) and thus would not lock. Always searching for GPS in Navigation even though it put my location as pretty much where I was. I had ClearnROM at the time but I don't think that caused it at all.
I tried Faster Fix. GPS Aides (free and paid) and a custom GPS.config file. Nothing worked. Thought for sure I was going to have to exchange the phone. so I set about doing what I would have to do.
Returned phone to bone stock via ODIN (VRALF2).
Rebooted into stock recovery and wiped/data for a clean internal SD card.
Flashed radio via ODIN (VRLF2).
Accepted VZW OTA update (30MB).
Rooted with Root Debug FS.
Put EZ-Unlock and EZ-Recovery apks on my sdcard and installed them.
Unlocked the Bootloader and booted to recovery 6.0.1 once just to verify it worked.
Whalla.
GPS locks and all it back to normal.
Your mileage may vary. I did (in the process of wipe/data for clean SD card- loose all my Titanium Backups but getting Navigation to work again was worth the hassle of rebuilding my apps from scratch.
I have no intention to put any effort into tweaking the GPS settings or file again now that it's working.

REVIEW: Carbon app data backup & restore

this app is supposed to allow you to take a backup of your app data from one android device and restore it in another android device.
Background:
I have galaxy s3 (i747), galaxy note 10.1 (n-8013), asus transformer prime (tf-201)
I play games on all three devices, and would like to sync progress in all three.
All devices are stock and unrooted.
Observations:
1) the only way to sync up without buying premium version is to start carbon server on all devices, and then log onto a chrome browser from pc.
While makin backups of apps, the carbon server kept crashing.
2) i was unable to restore games progress. The system always said restore completed successfully, but when i opened the game, it was not really restored.
I tried temple run 2 and hillclimb racing.. restore did not work.
3) most serious side effect - this app does not allow device to go in sleep and causes partial wakelocks. Drains battery.
Here is a screenshot of better batterystats when carbon was installed
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I believe this app enables something in adb restore that keeps waking system to do backups.
My devices always went to sleep prior to installing this app... so this app was narrowed to be the culprit.
I uninstalled carbon from all my devices and rebooted... now my system goes to sleep!
See screenshot below, when my system is going to sleep finally!
I do not recommend installing this app.
Hope this revew helps.
Sent from my GT-N8013 using Tapatalk HD
Proof from my galaxy S3.
See attached image.. my phone drained out in 6hrs overnight with this app turned on. Uninstalling the app allows my device to sleep again.
Hi there,
I'm not sure, but it seems that a restart of the device after performing a backup can solve the problem (well okay..., that's more a workaround than a solution...). At least after a restart I had no further partial wakelocks of the *backup* listed in the BetterBatteryStats-app.
Regards
JoeS
smrsxn said:
this app is supposed to allow you to take a backup of your app data from one android device and restore it in another android device.
Background:
I have galaxy s3 (i747), galaxy note 10.1 (n-8013), asus transformer prime (tf-201)
I play games on all three devices, and would like to sync progress in all three.
All devices are stock and unrooted.
Observations:
1) the only way to sync up without buying premium version is to start carbon server on all devices, and then log onto a chrome browser from pc.
While makin backups of apps, the carbon server kept crashing.
2) i was unable to restore games progress. The system always said restore completed successfully, but when i opened the game, it was not really restored.
I tried temple run 2 and hillclimb racing.. restore did not work.
3) most serious side effect - this app does not allow device to go in sleep and causes partial wakelocks. Drains battery.
Here is a screenshot of better batterystats when carbon was installed
I believe this app enables something in adb restore that keeps waking system to do backups.
My devices always went to sleep prior to installing this app... so this app was narrowed to be the culprit.
I uninstalled carbon from all my devices and rebooted... now my system goes to sleep!
See screenshot below, when my system is going to sleep finally!
I do not recommend installing this app.
Hope this revew helps.
Sent from my GT-N8013 using Tapatalk HD
Click to expand...
Click to collapse
I had the same problem and when awake it kept my cpu pegged all the time....
Tapped from an annihilated N10.1
JoeSac said:
I'm not sure, but it seems that a restart of the device after performing a backup can solve the problem (well okay..., that's more a workaround than a solution...). At least after a restart I had no further partial wakelocks of the *backup* listed in the BetterBatteryStats-app.
Click to expand...
Click to collapse
That's because backup needs to be re-enabled via ADB, using the Helium desktop app, after every reboot (on non-rooted devices at least).
I have Helium on my non-rooted SGS3 and have noticed the same thing but I'm not convinced that it's actually affecting battery life.

[Q] Camera Error

Hi, someone have error on camera ? suddenly fails today, I rebooted it worked and now the error again
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What is the error message, do you know?
I had the same thing.. The error I have is can't connect to camera.
Any help is appreciated.
I had the same problem in the last few days. Most of the times another try to open camera app helped. But one time I had to reboot.
Ok, let's collect some information. I am on
176.44.1.falcon_umts.Retail.en.de
And I had these problems after I updated to latest KitKat version (but could be a coincidence).
Which versions are you on?
Gesendet von meinem XT1032 mit Tapatalk
Try clearing cache on the camera app
Sent from my Nexus 7 using xda app-developers app
Hi, i uninstal the google goggles app and so far I had no more error
same camera Error
Mleunam said:
Hi, someone have error on camera ? suddenly fails today, I rebooted it worked and now the error again
Click to expand...
Click to collapse
Hi I do have same camera error.
Error is "Camera Error" or "Fail to initialise"
Also tried to clear cache and tried to start camera again but all fails.
After rebooting Camera works fine.. some one should help us out to solve this problem.
My moto g is also running with 4.4.2
Camera error
I recently got the same error. It occurs maybe once a day for me and flashing my flashlight helps, but it sure is frustrating when you want to snap a quick picture.
Here:
http://forum.xda-developers.com/showthread.php?p=50591578
Sent from my XT1033 using xda app-developers app
Thank You
sakitobaki said:
Here:
http://forum.xda-developers.com/showthread.php?p=50591578
Sent from my XT1033 using xda app-developers app
Click to expand...
Click to collapse
Thank you very much !!! Camera cache clear, data clear force stop application and start again is woking fine..:good:
Again same issue
Hey guys,
Sometime above mention don't work and need to do restart only.
I believe that Motorola should work on this issue.
Same issue.. Tried everything... Camera error... This kitkat upgrade has slowed down my phone... Skyfire, times now, and many more applications force closes
Sent from my XT1033 using Tapatalk 2
Same issue here on my new phone- "Camera error: Camera error". Tried factory reset, cache clear, force stop, etc - no joy. Have now uninstalled two apps - "Flashlight" and Google Goggles. Let's see how this goes...
Very frustrating issue
EDIT: feel I should describe exactly what the issue is.
A period of time after the last reboot, the camera will stop working. When I attempt to start the camera app, I get a black screen and almost immediately the words "Camera error: Camera error" come in a dialog box. I click OK and the camera app closes.
I've tried an alternative camera app, Camera Zoom FX, but this behaves oddly. It starts up just fine, but only shows black - the image from the camera clearly isn't coming through to the app. Just black. Then, when I try to take a picture (the menus work just fine), the app force closes ("Sorry, Camera Zoom FX has stopped working.") Very strange!
As I said, I've removed some apps and will report back in a few days if it's fixed, or as soon as it breaks. My phone is fully up to date.
EDIT 2: this error has not completely stopped, but after installing the app "Camera MX" as suggested, I have been able to access the camera when needed. (Sometimes I need to start Camera MX and press the top-right "swap cameras" button, which IIRC looks like a refresh button.) Sometimes this isn't even necessary, but the issue seems better now for some reason. Maybe it's the beer.
I have now been having this issue with the camera as well as teslaled (flashlight app). I think it may have been caused by the ota update.
Hi guys
Here is a workaround for the issue
CameraMX can reset the camera resource if gets the error. So my trick is to simply start CameraMX and wait for the camera to reset. Takes
1-3 seconds and then it's fine. Better than a reboot
Sent from my XT1033 using Tapatalk
remove skype
xgt001 said:
Hi guys
Here is a workaround for the issue
CameraMX can reset the camera resource if gets the error. So my trick is to simply start CameraMX and wait for the camera to reset. Takes
1-3 seconds and then it's fine. Better than a reboot
Sent from my XT1033 using Tapatalk
Click to expand...
Click to collapse
I removed Skype and returned to work again.
:cyclops:

Are you forced to restart your phone everyday?

I'm forced to restart my phone everyday ,when I don't it becomes really laggy, the phone stutters when I scroll , when I swipe between the homescreen, when I switch between apps, I'm running stock kit Kat with Franco kernel r33, but I remember well the same used to happen when I had my nexus 4 and everything was stock I just had root .
Just closing all opened apps doesn't solve the problem .
Do you guys have similar issues?
Sent from my Nexus 5 using Tapatalk
I never had to do that with my phone.
Sent from my Nexus 5 using xda app-developers app
Nope. I restart once a week, if that. Never have any lag/stuttering/slowdown issues. Stock rooted.
Sent from my Moto X
Nope. Everything stock at the moment but I've also used Franco r33 and didn't have that problem then either. If you're just using the recent apps screen to close your apps that might not be enough since it'll only list foreground apps and not background services which would more likely be the culprit. If you aren't already, try using an advanced task killer app (I can't recommend any as I don't use them) and try killing services one by one until the lag stops so that you can figure out which app/service is causing it.
There is no reason to use a task killer or to kill all apps.
Sent from my Nexus 5 using xda app-developers app
Kreateablaze said:
There is no reason to use a task killer or to kill all apps.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Not for everyday use, no, but to diagnose which app is being a resource hog what else would you suggest?
I've never restarted my phone due to "lag." My current uptime is about 3 weeks. I'm bone stock.
Sent from my Nexus 5
Never restart. Faux r33 too
Try restoring the factory image and running it for a day or so without any extra apps. At least then you'll know if the phone is faulty. It's likely to be an app or two that are using a lot of memory, but I thought the mighty Nexus could cope with anything!
I have stock ROM, no root, since launch and I've used it everyday 24/7.
No lag problems, never had the need of rebooting it, as a matter of fact sometimes it has been on for more than a month without a poweroff or reboot.
While I've not "had to" restart my N5 due to lag, I have gotten into the habit of restarting it every night when I recharge. I started doing this when google play services (old version) was going haywire and sucking down the battery every now and then.
I only restart my phone when it's really needed (like an app requires reboot and etc)
I restart my phone maybe once every two days or so just to start fresh. Same with your computer restarting it will eliminate processes that you may have started and not ended or background processes running and so on and so fourth.
I only restart when the device doesn't sleep. I find after a day or 2 Google now keeps the device from sleeping. A reboot fixes it right up.
Never experienced lag. Running stock, gravity box, apex launcher and Franco kernel
Sent from my HammerHead
Having to restart your phone that frequently is not normal. Not that it would help a lot, but have you tried switching to ART?
OP, how many apps do you have? Anything else you modified but the kernel? Overclock, underclock, UV, etc.? Give us more infos.
I recently set up my tasker profiles for morning - morning commute - work and home. The last one I have is a nightly reboot at 4am. I just have the tendency to restart my devices daily. Memory dump and fresh start every morning never gives me any issues.
Look into it.
Sent from my Nexus 5 using XDA Premium HD app
This is what I use as my daily driver and only reboot when an app requires it or once every two weeks when I let it die for battery preservation
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 5 using Tapatalk
I never restart my phone unless there's a need to flash something (ROM update, kernel, etc.).
Also, I think my phone feels smoother than before, especially when I don't clear anything in recent apps.
So i just flashed back the stock kernel and everything went back to normal, I guess I'm done with custom kernels, I've always had bad experiences with them, I don't know if I'm really picky and other people don't notice it, but I can't believe I'm the only one who experiences lag while on custom kernels, maybe the're too agressive trying to save power?

[Q] Front camera problems, even in safe mode

Hi there,
Since a few days, I'm having troubles using my front camera. It all started after upgrading to 5.1.1 (and using SnapChat afterwards), but now I can't get rid of it.
When I switch to the front camera (in SnapChat, or in the standard camera app), the camera might switch to front camera and show the images for a few seconds, or it might not switch at all. After that, the screen gets frozen. Then, it depends: the screen just stays frozen, or turns green/blue/glitched, or I get a message that my camera can't be found.
This also happens in safe mode, with or without clearing cache & data, and also happens after a full reset, even after downgrading to 5.0.1 again.
What is strange, is that sometimes my camera app opens with front-face camera enabled, and then everything works fine. However, when I switch to my back camera (which always functions correctly) and then back to the front-face camera, then it's the same all over again.
I have googeled a lot, yet found no threads that exactly describe my situation. Most threads suggest trying the camera in safe mode and presume that it works in safe mode. Mine doesn't.
Does this sound like I need to return it (I still have waranty), or is it a software bug nonetheless?
This is an image of my glitched screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ad Fundum said:
Hi there,
Since a few days, I'm having troubles using my front camera. It all started after upgrading to 5.1.1 (and using SnapChat afterwards), but now I can't get rid of it.
When I switch to the front camera (in SnapChat, or in the standard camera app), the camera might switch to front camera and show the images for a few seconds, or it might not switch at all. After that, the screen gets frozen. Then, it depends: the screen just stays frozen, or turns green/blue/glitched, or I get a message that my camera can't be found.
This also happens in safe mode, with or without clearing cache & data, and also happens after a full reset, even after downgrading to 5.0.1 again.
What is strange, is that sometimes my camera app opens with front-face camera enabled, and then everything works fine. However, when I switch to my back camera (which always functions correctly) and then back to the front-face camera, then it's the same all over again.
I have googeled a lot, yet found no threads that exactly describe my situation. Most threads suggest trying the camera in safe mode and presume that it works in safe mode. Mine doesn't.
Does this sound like I need to return it (I still have waranty), or is it a software bug nonetheless?
This is an image of my glitched screen:
Click to expand...
Click to collapse
method 1 on http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
be advised that there was a camera bug on 5.1 and below, so you should actually flash LMY48B factory image following the steps on the thread linked above.
beekay201 said:
method 1 on http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
be advised that there was a camera bug on 5.1 and below, so you should actually flash LMY48B factory image following the steps on the thread linked above.
Click to expand...
Click to collapse
Thanks for the response!
I am currently on 5.1.1 (build LMY48B), flashed using the above methode (and even did another factory reset afterwards), yet the problem is not sobled.
Ad Fundum said:
Thanks for the response!
I am currently on 5.1.1 (build LMY48B), flashed using the above methode (and even did another factory reset afterwards), yet the problem is not sobled.
Click to expand...
Click to collapse
Try to uninstall ANY apps that make use of the camera (except Google Camera/AOSP camera) and disable Trusted face on Smart Lock if you're using it.
Quick update: it was a hardware failure. A friend of mine had a quick look at my nexus 5, opened it up (he's in the repair business) and played a bit with the connector of the front camera, and everything works fine now.
So for those who are reading this: if you're like me, and are still having problems even in safe mode and after a factory reset, then a hardware failure might be the problem.
To beekay201: still thanks a lot for the replies, much appreciated!

Categories

Resources