Need help out of a Jam - Nexus 7 Q&A, Help & Troubleshooting

I screwed up. My impatience to get my tablet setup again after wiping and putting cm on got the best of me. I typically just use titanium backup for game saves and launcher settings, the rest I do manually from the play store. Today I got impatient, half way through setting up I said screw it, restored everything that wasn't in red. And somehow, I permanently broke swiftkey tablet. It wouldn't load language packs anymore, so I uninstalled and reinstalled. Now it says network error constantly and refuses to download the app. Do I need to wipe and start over or is this fixable? Thanks
{
"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 7 using Tapatalk HD

Fix for the SwiftKey problem
Hi,
Try to uninstall the software the manual way.
Delete every folder of SwiftKey.
After that go to System properties / keyboard/kanguage and activate standard keyboard. (android default)
Reboot your device.
Install Swiftkey the usual way (via Playstore)

Ok will do. Btw my original post is wrong, I came from cm, now on stock 4.3.
Sent from my Nexus 4 using Tapatalk 4 Beta

May not be you.
Had the same problem with SwiftKey when I flashed 4.3.
Fresh install, or restored from TiBu, same problem downloading English package.
Due to other issues I went back to 4.2.2 for now.

Nah it was me, I had swiftkey working fine but being impatient I said screw it, restored everything not highlighted in red.
I just reinstalled the rom and did a factory reset, it's for the best, gotta be careful with tb, I know this from experience
Sent from my Nexus 4 using Tapatalk 4 Beta

danvee said:
May not be you.
Had the same problem with SwiftKey when I flashed 4.3.
Fresh install, or restored from TiBu, same problem downloading English package.
Due to other issues I went back to 4.2.2 for now.
Click to expand...
Click to collapse
Ok so you might be right. I was able to set up SwiftKey to work fine once but now even a full wipe of system didn't fix the issue. Something is messed up on their servers
Sent from my Nexus 4 using Tapatalk 4 Beta

Well I've tried it all now except wiping the sd partition. Sigh. Guess I gotta use terrible google keyboard
Sent from my Nexus 4 using Tapatalk 4 Beta

Related

Dropbox gives me a "storage full or unavailable"

Not sure what the cause is, just got my 7 yesterday.. stock rooted, aokp, doesn't make a difference- dropbox doesn't work and just gives the error "Storage full or unavailable"..
Doing a search, the only thread that mentioned it was "[ROM]| Glazed JellyBean|Version 1.1.2|Glazed Mods|Custom Animations|Speed|" and it had to do with an error in the rom, not my issue.
I've tried reinstalling the app, factory reset, flashing aokp(from stock rooted)- none have had a working dropbox, but I can't find any other posts that others have had the same issue.
I also have a few error 492 when downloading a few apps from market(like dead trigger), not sure if it is related..
Is dropbox looking for an external SD?
And "Protect usb storage" is NOT checked in developer options, just in case someone asks.
All I did was unlock bootloader, root.. nothing that should keep dropbox from working.
Although Im on stock but unlocked bootloader and rooted i have had the play store error and i just restarted and it worked fine since, dropbox i cant help mine logs in fine and i can use it perfect
Sent from my Nexus 7 using Tapatalk 2
My issue seems to be more than just drop box.. stock gallery app closes immediately after showing this:
{
"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"
}
As I said, pretty sure I didn't do anything to cause this.. I'm assuming there's a way to flash the original software that will repartition the device(like flashing HTC phones with ruu, or Samsung with Odin)?
I haven't had a lot of time to look into these things since o got it yesterday, so if anyone has a quick possible solution is appreciate it!
Edit: I'd like to know if this process([Guide] Returning to Stock and/or Unbricking your device) http://forum.xda-developers.com/showthread.php?t=1781250 actually repartitions everything.. but I decided to go trade this one out for another one rather than beat my head on a wall with an issue no one else appears to have. Still worth finding out.
Sent from my Nexus 7 using xda app-developers app

[Q] ADB connection problem - Device Offline

This is weird. I never had this problem with my Galaxy S3.
I've enabled USB Debugging on the phone.
Even toggled it off, rebooted and turned it on again.
I've also rebooted my computer and even updated SDK Toolkit.
No change in problem though.
Every time I try to connect to my phone from ADB, it just tells me the device is offline (see attached pic).
Any ideas?
{
"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"
}
Mine said that also one time before I accepted the adb connection on the phone
Sent from my A500 using Tapatalk HD
StolenVW said:
Mine said that also one time before I accepted the adb connection on the phone
Sent from my A500 using Tapatalk HD
Click to expand...
Click to collapse
I'm not getting any popup for that.
CZ Eddie said:
I'm not getting any popup for that.
Click to expand...
Click to collapse
Try this
http://www.wugfresh.com/faqs/how-to-fix-adb-device-is-listed-as-offline-on-android-4-2-2/
And if you do a Google search for
how to fix adb device offline
It comes up with other things to try
Sent from my A500 using Tapatalk HD
Thanks, I tried the info in that link but never got the pop-up asking for ADB permissions.
I did google prior to posting also. I listed in my OP what I tried (which is what my googling suggested).
I'm about to ODIN back to factory stock anyways. So I'll try again after that. Maybe I messed something up during all the bloatware removal I did yesterday.
Nope, a fresh ODIN install of stock ROM didn't help at all.
Guess I'll have to uninstall & reinstall Android Toolkit maybe.
EDIT:
Using Motochopper root tool, I finally got the popup. And made sure to select "always allow from this computer". I think that should fixit.
EDIT #2:
Nope, that didn't help at all. Still "offline".
EDIT #3:
Actually, using the ADB from Motochopper does work. It's just the ADB from my Android Toolkit that doesn't work.
Sounds like one in android tool kit is out of date
Try updating the android sdk
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

[Q] QuickRemote Problem.

So after the first week with this device I get a strange QuickRemote problem. It give me a blank page after tipping something in the app. QuickRemote.apk data/cache clear don't help. What could I do?
{
"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"
}
Clear cache and data in app settings. ...I had an issue with mine disappearing. ... this fixed it
Sent from my LG-D803 using XDA Premium 4 mobile app
xdafoundingmember said:
Clear cache and data in app settings. ...I had an issue with mine disappearing. ... this fixed it
Sent from my LG-D803 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I rldy say that the Cache and date clearing dont help
Edit: Just saw other 2 pics. No idea. Give people a bit more info to what all you did to your phone otherwise.
Steamer86 said:
Edit: Just saw other 2 pics. No idea. Give people a bit more info to what all you did to your phone otherwise.
Click to expand...
Click to collapse
If really nothing. I have even not rooted phone
I added 2 TV's and 1 Selteka Set-top Box that all. After night I wanted to turn my TV on and thats what happened...
```
deleted
Someone help...
Wipe...
stefy97100 said:
Wipe...
Click to expand...
Click to collapse
Cache and Data Cleaning DONT HELP
There was a report from a member with the exact same issue as you have, however, he said he did root and also delete one of the corresponding file, that was his problem, and soon after he move that file back into the system, QR worked as normal. Your case is kind of strange since you haven't rooted it yet.
My suggestion is factory reset.
Remember, you will lose everything, so backup first.
votinh said:
There was a report from a member with the exact same issue as you have, however, he said he did root and also delete one of the corresponding file, that was his problem, and soon after he move that file back into the system, QR worked as normal. Your case is kind of strange since you haven't rooted it yet.
My suggestion is factory reset.
Remember, you will lose everything, so backup first.
Click to expand...
Click to collapse
Done a LG Backup , transfered to my sister N4 and after factory reset made a reset of backup It seems that it worked Thanks you.
Was QuicksetSDK frozen or removed? Quick Remote needs that file to work properly.

[Q] Flashed latest CyanogenMod build, yet everything was still there

Okay, so here's a quick recent ROM history of my G2 (VS980).
I was on SlimKat for a little while, then switched to build 2014/07/09 of CyanogenMod, and just now I updated CM to build 2014/07/16.
So I backed up my ROM and apps and whatnot in TWRP, then did the default wipe, then flashed the latest CM nightly + Gapps. When I rebooted into the ROM, everything was still there. All of my apps were still there. My processor settings were still there. My lockscreen was still there. It was as if I never wiped then flashed a new ROM.
I went into the settings and it says that it's still on build 2014/07/09.
So can somebody tell me what's going on?
(Here's a picture of TWRP after I flashed the ROM + Gapps. Sorry for the crappy quality. I had to take it with my 3DS camera, since that's the only other camera I had lying around.)
(TWRP version 2.6.3.3)
{
"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"
}
In case you can't read the text in the image, here's what it says (in order):
E: Unknown File System 'datamedia'
Updating partition details
Simulating actions
Updating partition details
Simulating actions
Updating partition details
Simulating actions
Updating partition details
Simulating actions
Simulating actions
Updating partition details
Check in twrp under advanced options (i think) and make sure "simulate operations to test theming" or some thing very close to that is not checked.
Sent from my LG-D800 using XDA Premium 4 mobile app
helioXverse said:
Check in twrp under advanced options (i think) and make sure "simulate operations to test theming" or some thing very close to that is not checked.
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Alright, I'll try that. I've never had to do this before though, so just a bit confused. What does it even do anyways?
It basically runs commands with out actually changing anything so people who theme twrp can make sure the theme works 100%. I've checked it by mistake more than once when setting up recovery.
*Edit its actually under "settings". Its the last box on the list, on 2.7.0.0 anyway. I checked it just to test and get the same message as you. I hope this fixes the problem.
Sent from my LG-D800 using XDA Premium 4 mobile app
helioXverse said:
It basically runs commands with out actually changing anything so people who theme twrp can make sure the theme works 100%. I've checked it by mistake more than once when setting up recovery.
*Edit its actually under "settings". Its the last box on the list, on 2.7.0.0 anyway. I checked it just to test and get the same message as you. I hope this fixes the problem.
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I found it in v2.6.3.3, so it's all good. Thanks for the help, and I'll see if this fixes my problem.
EDIT: It did.

Broken camera or... else?

Interesting behavior lately, on my sg5. There are times (more and more often, recently) when neither Google's camera app, nor camera zoom fx show anything on the screen, as if there was no visibility through the actual camera hardware. Rebooting the phone brings back functionality, but only for a while (a few hours), after which the strange no image comes back.
I have also experienced strange "disappearances" of pictures I just took, which show up in a gallery app (the default, or quick pick), but which are nowhere to be found after closing the camera app.
Has anybody seen anything similar? I would really hate to go back to resetting to defaults - had rooted and xposed customized this phone to my liking. And - no - this behavior is not associated with any recent xposed activity / configs...
Sent from my SM-G900T using Tapatalk
Try booting to recovery and clearing the caches
*Detection* said:
Try booting to recovery and clearing the caches
Click to expand...
Click to collapse
Did that two ways: like you suggested, and - prior to that - via titanium...
Sent from my SM-G900T using Tapatalk
I have similar on stock, without root.
When I open up default camera application, there is no picture, just blank screen and phone becomes very laggy. Screen looks like this:
{
"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"
}
But it happens just sometimes.
E.g. once per 3 days and soft reboot is the solution.
Don't know the root cause Mine is SM-G900FD with BOC1 firmware.
Tried a factory reset already, but didn't help. Didn't try safe mode yet, as it might be related to some application e.g. facebook, viber, etc. which has access to camera.
Happens to my also since Lollipop on SM-G900F, tried the new stock BOC7 and now is better but it still there, the error and the blank screen. I noticed it happens more often in the evening/night. I've tried everything, wipe cache, reset camera. Hope Samsung will release a fix, no problems whatsoever on KitKat,
florio1960 said:
Hope Samsung will release a fix, no problems whatsoever on KitKat,
Click to expand...
Click to collapse
Mine (OP) is kk
Sent from my SM-G900T using Tapatalk
I see, so that will be probably different issue. Mine started also with lollipop, there were no problems on kitkat.

Categories

Resources