Hello all,
I recently rooted and unlocked my Nexus 7. And one of the first things I noticed is that I can no longer NFC Beam Panorama photos.
Before the rooting and unlocking, I beamed several panoramas from my Galaxy Nexus to my Nexus 7. As well as regular photos too.
But after I rooted it and unlocked it (No custom ROM yet, still stock Jellybean), I can only beam the regular photos. When I attempt to beam any panorama photo at all, it acts like it is receiving the beam, and waits a while, then tells me the beam could not be completed.
I am not sure if I am the first one to notice this issue, but I was unable to find anything online about it, after a good amount of searching.
Some info about my Nexus 7:
Still running the stock Jellybean that came on it.
Rooted
Bootloader Unlocked
CWM Touch Recovery Installed
Nothing else really, just standard stuff like BusyBox, and AdFree.
My Galaxy Nexus:
Rooted
Bootloader Unlocked
Running Jellybeam ROM, but one of the early stock ones, with no real customization.
CWM Recovery Installed (not touch)
More standard tools, like busybox and adfree
Nothing that I can imagine would effect its NFC capabilities.
Again, this worked 100% perfect BEFORE I rooted an unlocked my Nexus 7. So I am 99.99% sure that my galaxy nexus is NOT the problem. The only change that occurred to break this feature was the rooting/unlocking of my Nexus 7.
Any one have any ideas?
I would prefer an actual fix, as opposed to just reverting back to un-rooted, locked status.
For anyone looking for a solution to this. I figured it out.
After trying tons of things, I finally got Panorama photos to beam successfully after rotating them. Either right, or left, it doesn't matter. But just rotate the image once so its tall and skinny, instead of short and fat. This can be done in your android gallery, where you beam it from. Just press menu > rotate left or rotate right
Then just rotate it back the right way, once its been beamed.
Related
Hi.
I'm new to Nexus 7 and after a short time using it I began experiencing some strange issue with the it. While surfing the web over WiFi (note that I'm using the first Nexus 7 with WiFi only) after a short time glitching lines appear on the screen (as shown on the image attached) and some loud white noise coming from the speaker. It's stuck like this for about 30 seconds and then reboots. After reboot, everything seems normal, till it comes again. It takes 15-30 minutes of surfing and I believe the time depends on the intensity of surfing. Seems like WiFi modem somehow affects the GFX driver.
Note that I was first running android 4.1.1 and recently updated to 4.2. Updated didn't fix the problem. I've rooted the device with "Nexus 7 root toolkit v.1.5". Note sure if the rooting affected it somehow, as I rooted the device on second or third day of use.
Anyone have an idea of what could be wrong or how I might fix it? Or it's HW issue and I should turn it to Google?
Thanks!
So I'm the first and only one with such problem???:silly:
I could be wrong here but that seems like more of a hardware(warranty) kind of issue. However, I had the speaker issue after flashing a custom ROM (sparks linario 4.2.1) and I had the speaker issue (along with a host of other bugs buts that's beside the point). I flashed stock and unrooted and the problem was fixed... I know it might not help your case but I thought ide let you know. Its possible the toolkit caused the issues and flashing back to stock and rooting with another method may solve your issue (that's what I would try). But if you end up sending it in under warranty for god sakes, unroot and relock your bootloader first! Otherwise Google probably won't honor your warranty.
Good luck friend.
Sent from my Nexus 7 using xda app-developers app
Greetings folks -
After spending countless hours compares various tablets (Ipad4, Nexus 10, Asus, etc.) I decided to go w/ the Nexus 10 - and I'm not going to lie, one of the many intriguing aspects of selecting an Android 4.0+ OS device was being able to use the 'face unlock' and 'liveness check' as a quick unlocking tool (I'm well aware of the short-comings of these features, it still just intrigues me).
After fiddling around w/ my Nexus 10 for 2 days, I decided to go into settings and enable that feature. Lo and behold, it was nowhere to be found. I confirmed that my unit was running the latest version of the OS and then called in the support center to figure out was going on. Surprisingly enough, I was the first person to ever call in regarding this - but it turns out that Face Unlock is currently NOT SUPPORTED at all on the Nexus 10. For some older Tablets w/VGA cameras, but that had still upgraded to 4.0, Google intentionally made Face Unlock inaccessible due fear that the poor camera resolution would render it obsolete. How on earth could that be the case with the Nexus 10 and its 1.9 MP front facing camera?
I'm curious to know if anybody knows anything regarding an estimated release date of this feature - and rather if Google has decided to scrap it all together? I feel like the Nexus 10 should be running the most powerful, up-to-date version of the OS available so I find it puzzling that this has been left off.
I realize this is a tiny feature; however, it's something I looked forward to being able to use.
Thanks in advance!
Stock 4.2 and 4.2.1 on the Nexus 10 have Face Unlock under security. It even is an option when the tablet is encrypted, which is new in 4.2, I think.
Weird - working fine on my stock 16 nexus 10. Are you sure you're looking at the right settings. You want security then screen unlock.
It definitely, works, and always has done, as has been said, it's under security, lock screen.
If your rom does not have face unlock option and your device is rooted
Grab the FaceLock.apk from any other rom having this future
Push the file to /system/apps/ and correct the permissions to 644
Reboot and you will have facelock option in lockscreen options
Sent from my GT-N7000 using xda
Helllllo everyone!
So I apologize for being one of those people who just come here to ask questions. Unfortunately life doesn't have room for me spending time playing with my Android devices anymore, so having it 'work' is more important to me.
I am on 4.3, ParanoidAndroid 3.96. I am not on the latest because it took some time to have the app TouchControl work (with my Franco kernel), and Secure Settings etc. that I chose to just stick with it because it worked really well for me.
The problem!
I recently noticed that if I tried to switch to the front facing camera, it'd hang. After that, I would not be able to use my torch/led, and going into the camera would tell me that "The camera is not connected" or something like that. I could only fix this by clearing all the data on my Gallery, and shutting down, and then turning on again. Reboot would not work.
If I did that, I could go into my camera and use the rear camera fine. Take pictures, record video, etc. Torch works as normal. It's just that once I attempt to go into the front camera, this problem happens.
It's weird because I didn't flash anything or change any settings when this happened. I DID install https://play.google.com/store/apps/details?id=eu.mrogalski.saidit which wouldn't let me record a video while being used, but I since disabled/uninstalled it which solved that problem.
I have done a lot of googling on this problem, and noticed that I am not the only one who has this problem. For some people it seems like their phone is new, and some it just happens out of nowhere. For that reason I suspect it might be a hardware problem that can occur randomly, but it's weird that after triggering the problem, that my torch won't work anymore as well. Unless the torch is somehow tied to the camera/flash, and by triggering the problem when I try to access the front camera, it isn't able to 'call' the camera/flash anymore as a result?
I bought my Nexus 4 from Google in May 2013, so I believe I still have until May 2014 to RMA it, correct? Would I get another Nexus 4 at this point, or maybe I'd get a Nexus 5 instead?
Thanks in advance for any insight into my problem!
I know you would like to keep the rom you are on but to be on that rom you must have a custom recovery installed. So if I was you I would back you're rom up then flash something different to see if its hardware related or not . If so then return the phone.
Sent from my Nexus 4 using XDA Premium 4 mobile app
bladebuddy said:
I know you would like to keep the rom you are on but to be on that rom you must have a custom recovery installed. So if I was you I would back you're rom up then flash something different to see if its hardware related or not . If so then return the phone.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the reply.
I tried installing the latest PA rom, but came up with an error. I had the rom I was on originally still, so I tried wiping and flashing it again. Finished flashing, went and opened the camera and it still happened. Looks like it's a hardware problem then!
I guess I'll go look up a guide to flashing back to stock now.
Just got an international G2. Quite surprised to find the camera flash doesn't fire when focusing, only when the picture is taken.
Is this normal?
I'm rooted, stock rom and kernel, only changes are some G2 Xposed settings and fast dormancy disabled in service menu (if it helps to know that)...
Anyone got any info or suggestions? Cheers.
El_JimBob said:
Just got an international G2. Quite surprised to find the camera flash doesn't fire when focusing, only when the picture is taken.
Is this normal?
I'm rooted, stock rom and kernel, only changes are some G2 Xposed settings and fast dormancy disabled in service menu (if it helps to know that)...
Anyone got any info or suggestions? Cheers.
Click to expand...
Click to collapse
Mine doesn't fire when tapping on the screen to focus (do any smartphone cameras do this? None that I've used do), but it fires after I press the shutter button, and refocuses itself based on that and then gets brighter to actually take the photo.
My D802 doesn't do it, at least on aosp. But my sgs3 on aosp did.
Sent from my LG D802
Thanks for the help guys, I guess that clears that up. I've come from a Nexus 4, which does flash while focusing, so I guess my natural instinct was to assume it wasn't working properly. Cheers
Hi!
I'm absolutely new here (and to Android and everything about it) and i've only made a couple of posts in the noob thread. I felt like this should be a thread of its own due to its abnormality.
I've only very recently rooted my phone (i9505, 4.4.2) a couple of hours ago using the towelroot method. I have not flashed any custom ROM yet however I do have some Xposed Modules installed.
i've only run across some problems like repetitive rebooting (fixed) and faster battery drain (hopefully fixed by tomorrow).
However, I have one problem that doesn't seem to have any solution whatsoever anywhere in the internet; it wasn't even mentioned once.
Whenever I open the stock camera app, the touch screen becomes completely useless. I cannot touch anything; the settings, shutter, view finder to focus, absolutely nothing. The camera itself is not broken, I can still take pictures with the volume rockers. Also, I know not the entire screen is broken because one of the modules I have installed is SwipeBack, which lets me swipe from a corner and it goes back and it still works perfectly fine.
I've tried rebooting the phone and force stopping the camera but nothing has worked.
The only suspicious thing I've done is backup and uninstall all the KNOX apps, which should be no surprise.
Now I'm not particularly bothered by this as I barely use the stock camera app anyway, or any camera app besides Snapchat. I don't use my phone for taking pictures much, but it still is quite annoying.
Is there any sort of fix to this?
Thank you very much in advance!