[Q] Strange problem with pinch/zoom - 7" Kindle Fire HD Q&A, Help & Troubleshooting

I'm experiencing some peculiar behavior with pinch to zoom functionality on my rooted Kindle FIre 2. I had originally rooted my device, changed the launcher, and was using dolphin as my browser. Flash was installed, and was functional. Pinch zoom was working.
Then something happened. Don't know what, lost root, launcher switched back to stock. Apps were still there, though. I thought it was an OTA update, but according to the version numbers, it wasn't. Plus the device is unregistered, and I was under the impression that OTA updates won't happen to unregistered devices. Thought it might have been an inadvertent factory reset. Unfortunately, I can't be sure. I looked at my device and saw the last half of a progress bar filling up. Might have hit some unfortunate sequence as I set it aside.
Anyway, (maybe unwisely) I did a factory reset, re-rooted, and put mostly everything back in order the way I had it. Problem is, pinch zoom is not working. It's works in Silk, and Chrome, but I don't generally use those (I prefer privacy and like flash). It won't work in any version of Dolphin I install, or any other browser I tried, and I've tried a lot.
So a couple related questions I guess. First, any guess what happened in the first place? Second, why would pinch to zoom work so selectively? The screen still registers two contact points, Silk and Chrome work,but nothing else. I've gone over every setting on every app, the browsers, the launcher, and the device, and I can't find anything. Could the factory reset have deleted something critical to that function that only Chrome and Silk can provide on their own? Or have I just stupidly missed some obvious setting?
Any help would be much appreciated. Thanks.

Related

Is Android supposed to be stable?

Maybe im expecting too much:
When I press gallery, almost 1/3 of the time only 1 or 2 categories come up and no thumbnails. Then i exit and press again and a few more things show up. Then i exit again and usually the 3rd time or so the app opens properly.
Also, about once every 2 weeks i press an app and it opens a different app. And this happens with multiple apps. The only way to fix it is to reboot.
I dont use a task manager
I reboot the phone every couple of days
I wipe the phone about once every 1 or 2 months
Is one of the above practices ruining my device?
I bought the phone and i havent done anything custom to it. Why does my polished 2.1 firmware work like a 5th grade science experiment?
Have occasionally noticed that the gallery app does not pick up all images and categories... something with the media scanner... try using the media scanner in the dev tools app or unmount and remount ur sd card...
Never had any problems with apps opening wrong apps... this is very strange... I have no idea why this is happening and quite frankly, I can;t think of anything which would serve as a possible solution!
Occasionally I've had the latest picture taken not show up in the gallery, but that's it. Stock O/S is great.
Never had it open the wrong app.
I don't run a task killer, don't reboot & have never wiped.
About the app opening the wrong app thing I guess its good news if I'm the only one. Is it possible that I've downloaded an app that is causing it? Or is it more likely an OS issue? it seems a little cheesy that the phone does this, if I could fix it without rebooting that would be a step in the right direction...
Likely an app you downloaded, or just something a little off about the flashing of your update, or a bad RAM memory block at the wrong place.
As for the gallery, I thought I had that issue a bit too, but I noticed that more than anything it just takes a really long time to open fully if it has been kicked out of the cache.
As for the original question posed in the thread title, Android is still Beta in a lot of ways. 2.0/1 is a huge change in many ways from 1.6. It sounds like 2.2 is going to be a bit of a change as well, but instead of changing nearly everything, it is going to build of 2.0/1 plus add in some changes. I am willing to bet that until the release after Gingerbread (the OS after 2.2, aka FroYo), not sure what the "H" release will be codenamed will we see an OS that isn't "Beta" in enough ways for me to call it non-Beta personally... then again, so far Android is less buggy than windows mobile, better than Blackberry even, and on par with iPhone OS, if not better in these regards.
Just like an OS for a computer, same holds true for a smartphone, there are going to be bugs, there are going to be bad programs/apps, and so forth.
I think you should wait for FroYo, if Android still doesn't meet your standards, root and flash some of the custom ROMs. Enom is very stock like, but fixes many of the little bugs, as does Cyan, although with Cyan you do get a few more bugs in some of the development apps and what not.
Just a thought, but maybe you're suffering from the occasional wacky touchscreen issue?
So it's not that it's just opening the wrong app, but the screen is registering a touch in a different place, it's usually most noticable when typing. If it is that, then a simple lock/unlock will solve it, no need for a reboot.

Upgraded from Fresh 2.0d to Fresh 2.1.1 without wiping, everything seems fine. Is it?

Last night after it was found out the leak and the official release were identical I loaded Fresh 2.1.1. I realized as it was loading I forgot to wipe the phone. I figured I'd let it finish and just have to redo it, but I turned my phone on anyway, just to see.
Everything seems fine. The update seemed to leave everything in tact, while running fine. (and freeing up 55mb of space for apps despite seemingly installing the same apps and leaving mine) The update worked, there are noticeable style differences in quite a few places.
My question is, is this an illusion? Am I not really running the updated versions in some areas? Are there behind the scenes things going on that make it error check and fall back to old "backward comparability" type things, make it slower, etc? Or is wiping just a "safety" thing to give you the best odds of success?
Is my phone going to burst into flames in my sleep, or did I get lucky because most incompatibility examples would be obvious?
I'm not using apps2sd.
Wiping is a safety thing, and also required if there are major changes between versions.
If it is working then don't worry about it. I have flashed 2.1 ROMs over each other before without any problems before, for example a Damageless's Rom over Flipz's. I think as long as the framework matches there is likely to be no problem.
I found one thing that doesn't work. The people app force closes every time I go to actually view a contact.
Does anyone know a good way to clear the contacts without deleting them? (If you delete them in the contact app google syncs the deletion, as it should.)
Actually it looks like it's only a problem on the contacts linked to facebook. Maybe if I can find a way to unlink them, and then link them again, without opening them, they'll be fine.
Just had to removed and re add my facebook account. Good times. So maybe people don't need to redo their phone to jump from 2.0d to 2.1.1. Give it a try.
You've inspired me to give it a try. i, however unlike you, do use a2sd and it's picky as **** so hopefully that stays in tact.
I'll post results after.

Captivate boots slow, issues. How to troubleshoot?

So, a little history...
I'm on my 2nd Captivate (unrelated issue). The boot problems didn't arise until I restored my data onto it. The first time I tried restoring system data along with my apps (which I figured was safe since I was going from 2.1 stock to the same) but that had lots of issues. So I did a factory reset, and started over. This time I just restored apps and their data, and a few specific pieces of system data (contacts, wifi APs, etc). That worked better. But later I got too aggressive with what system apps I "froze" (using Titanium Backup), and it got into boot loops I couldn't break out of. So I did another factory reset.
This time, first I carefully froze only apps I was to confirm were safe to freeze. I didn't proceed restoring my apps until I was done freezing and ensured it was booting fine. I then restored all my apps (and their data). The problem is now that it takes forever to boot... in fact, it'll go into a boot loop if I just leave it be. It seems the only way I can gain access is to try and unlock it before it's done booting, clear any "Force close" errors (sometimes takes a few tries) and given enough attempts, I can get in. But the boot takes an unbelievable amount of time, and even with my original apps is many times longer than before on my previous Captivate. Once I fuss my way in, it seems mostly fine, but something is obviously wrong and I want to get it straightened out.
Aside from doing another factory reset, and reinstalling all my apps (which takes like a day without troubleshooting after each, since batch restores in TB don't seem to work well on the Captivate so I have to do them one by one), I'm hoping there's a way to troubleshoot it in its current state and try to fix the problem surgically versus erasing and starting over. I looked at the logcat logs but got in over my head... there are so many errors and warnings and I don't know what's normal and what isn't... too many to know where to begin with searching Google.
So... advice? What tools are available? Even the logcat doesn't seem to kick in until the boot is mostly done, so I'm not sure if it can catch the problem while it's happening. One frustrating thing about Android is that is seems to have no "safe mode" or other diagnostic boot or full logging where you can methodically look at what's happening and experiment with the config. If this was a Windows, Linux or FreeBSD box I'd be in my element and able to get to the bottom of this, but on Android I feel even more crippled, locked-out and helpless than even on Windows. Urgh.
There's got to be a better way to troubleshoot and fix than endless random factory resets. This is something us anti-Windows people scold PC makers for, with all their use of "Restore CDs" for every minor and trivial software issue.
Thanks!
I can't help but think you are still disabling some essential system apps. Either that or one of your apps is causing major problems. Please list what you have frozen in tibu. Btw, the batch function works fine and is what most people on here use.
Also, what is force closing after you restore your apps.
newter55 said:
I can't help but think you are still disabling some essential system apps. Either that or one of your apps is causing major problems. Please list what you have frozen in tibu. Btw, the batch function works fine and is what most people on here use.
Also, what is force closing after you restore your apps.
Click to expand...
Click to collapse
First of all, thanks for taking a stab at this.
My frozen apps are:
* AllShare
* AT&T FamilyMap
* AT&T Hot Spots
* AT&T Maps
* AT&T Music
* AT&T Navigator
* AT&T Radio
* Daily Briefing
* Days
* Instant Messaging
* Media Hub
* Mini Diary
* Mobile Banking
* Mobile Video
* MobiTV
* Where
* Write and Go
* YPmobile
I also tried removing my MicroSD card, as well as switching back to Touchwiz (from LauncherPro). Didn't help.
Yeah the batch problem in TB is very frustrating. I'm using the pay/donate version so I'm missing out on a feature I paid for. I've been exchanging emails with Joel (the author) and we haven't figured it out yet. Batch backups work fine. Batch uninstalls also work fine (update: phone just spontaneously rebooted after about 50 or so uninstalls in a batch). It's the batch restores that seem to choke it. It's not corrupt backup files... a verify runs fine, and I can individually restore the same handful of apps one by one that will choke and hang/reboot the Captivate if attempted to restore in a batch.
The FC error I get is on boot-up, as I try to unlock the screen prior to the boot finishing. I often see "Process system is not responding".
I have aLogcat installed, if that's any use. A few questions about that:
- What's the best logging level to view on? In other words, do I care about "Warnings"?
- What errors are common, harmless, and safe to ignore?
Currently I've tried uninstalling everything down to just a few core apps. Certainly boots fine now, but I get plenty of warnings and errors in logcat.
Are u restoring just the user installed apps+data, or system apps too? Or restoring system stuff like contacts data, accounts prefs, etc?
diablo009 said:
Are u restoring just the user installed apps+data, or system apps too? Or restoring system stuff like contacts data, accounts prefs, etc?
Click to expand...
Click to collapse
I did not do a "restore system data" or any batch/bulk option in TB that restored all system data. As I recall, the only system data I restored a-la-carte (by selecting the individual item from the TB list) were:
Accounts
Bluetooth pairints
Bookmarks
Calendar
Contacts
Wi-Fi Access Points
These were all items in green in TB. I don't believe I restored anything else. Possibilities I suppose are wallpaper settings, "Country, Launguage, Time Zone"... but I definitely would not have restored anything not green.
Are these items safe? Is there any system data definitely not safe to restore? I have to wonder though, if "system data" is unsafe to even restore to the same stock OS version... why back it up at all?
I'm not a long distance from doing yet another factory reset I suppose, if it must come to that. But I'd love a way a bit more analytical/exacting to try and troubleshoot this other than "reinstall one app, reboot, see what happens" as that will take me a week to get back to where I was. I also suspect it's not just one single app that would suddenly show a huge difference after installing, but instead might be the cumulative errors from several apps and knowing how to identify that and clean them up would be useful.
Using adb logcat you can view what is occurring while the phone is booting and possibly see where it is hanging or what is causing the slow boot times. I have seen problems from restoring data such as accounts and contacts with titanium backup but does not seem that it should be an issue when using the same system though I have very little experience with the stock firmware. I know it is not an answer to your question but it seems that you are wanting to remove all the att/Samsung BS so why not flash a rom that does this as well as much more?
Sent from my ADR6300 using XDA App
Thanks for the tip about adb. I've actually not needed adb for anything yet so I've never set it up or used it. I wasn't aware that the service would be active early enough on the phone's boot process to allow it to log boot logs... nor was I even aware it could do this. I'll definitely check out how to set this up... however, if you have a free second and can point me in the right direction (FAQ, instructions, etc) it'd certainly be appreciated otherwise I'll search around and try to find it.
I could probably find other ways to restore contacts and could set my accounts up again manually but I really doubt that's the cause and the other ways are sort of a pain and imperfect. Since neither of us is really convinced that'd be it I won't bother yet until/unless you really suspect it.
I wondered how long it'd take before someone would suggest a custom ROM, this being XDA and all. Short version is I'm not really sold on the concept, as they are all based on the buggy beta leaked ROM, or 2.2 ROMs from other devices that have been hacked up to sort of work as well as possible on the Captivate. All seem to have issues... enough that I'm not really left feeling confident about them. Seems every release unleashes new issues despite addressing old ones, and all seem to have at least a handful of gremlin items that just don't work quite right. Don't have a warm fuzzy feeling, and I still feel like Samsung is going to release an official 2.2 for the Captivate within the next month or so, so I'm interested to see what comes of that. If nothing else, it'll give a better baseline for custom 2.2 ROMs. Then there's the 2.3 being worked on... now that might be interesting.
I don't really think my issue here is related to me running 2.1.
On my phone so it is a pita to search and add a link for you but search for android sdk and you will find what you need to get adb up and running.
And as far as the rom issue goes..it is your phone and I respect your concerns I just had to ask
I would think its media hub that slows it down. It will search your SD cards on every boot. I would start there first.
smokestack76 said:
I would think its media hub that slows it down. It will search your SD cards on every boot. I would start there first.
Click to expand...
Click to collapse
That's one of the apps I've frozen though.
For me the longest process while booting is the stupid media scanner upon bootup. Takes FOREVER for the phone to finally "boot" all the way up.
Been looking for a way to disable it (not really lol) and only have it scan manually to see if the boot time will improve. I'd start searching there.
Also - from what I've read nothing you did should have affected the phone. BUT - if your using Google for your Calendar and Contacts.. and they all get synced up to Google? Why bother doing the restore for those? After you sign up with the Market they get pulled back down to your phone automagically
It's definitely more than just the media scanner. I watch that. When everything is loaded up, it actually reboots in a loop unless intercept the FC. The media scanner will rerun over and over each time... far more than the standard two times.
And I use Google Calendar for my events, but I keep my contacts locally on my phone.
So what is the FC again?
Yep.. my media scanner will run at least 3 times before it stops checking everything.
Very frustrating that the software does this EVERY time I boot back into my phone - you'd think a programmer would put a check to see if it had run before or make it user configurable to scan when you want it to.
avgjoegeek said:
So what is the FC again?
Click to expand...
Click to collapse
See my second post (reply #3):
"Process system is not responding"
LOL sorry not enough coffee and a lil' guy that decided to wake up at 4a.m. = not a good mix.
Well.. did the ol' wise search of Google and came up with:
Might be a permissions issue. Easiest way to fix it is to run ROM Manager and have it fix permisions.
Run the command yourself in ADB:
Code:
Open terminal and
>su
$mount -a
$fix_permissions -r
The -r is optional, but necessary if you find orphaned apps (the app not found please reinstall message)
And reboot. That may help.
And it was also stated that you might have an errant widget/application causing the issue as well. That will be fun trying to figure out what it is.
And.. from my non-dev/non-professional experience - I have checked the logs on my phone and do see a large number of warnings on the phone - but never hindered performance.
So.. 99% of the time you can probably ignore them.
But back to the FC issue - I would try doing a restore of your apps/data again (I read where you have it back down to the "core) and then run the permission script or have ROM Manager do it for you and see if it returns.
Just an update that I think the "fix permissions" thing solved most (but perhaps not all) of my issues. Thanks so much for the tip. I've been reinstalling apps in batches and it's much better, although I see it getting bogged-down bit by bit and I can't pin down what or why.
Thing is, the apps I'm installing in these later rounds/batches shouldn't be resident all the time, shouldn't be auto-loading, and don't come up in things like Startup Cleaner or Advanced Task Killer. Nor do the various process monitors I've tried seem to have the granularity/ability to catch them while they're happening.
So things are better, but I still have some issues without a suitable means to diagnose. I don't get why just having more apps installed, but not running, should affect boot time so much. Hmm...
An inability to troubleshoot certainly rains on my love-affair with Android... not that I'm jumping to another platform anytime soon, but I really want this to work well (as well as be a good salesman to friends and family who often turn to me to show off quality technology).

Is Full Market even attainable (whack-a-mole)?

Hi,
I know that there are already a number of threads, but I was wondering if anyone knows if getting "full market" on the Gtab is really possible?
The reason for the question is that I've been working on this for awhile now, and I've tried every tweak that I've been able to find, and also some of my own, and:
1) I keep finding that I can't see some apps in market, and
2) The apps that I can see vs. not see seem to change, seemingly over time, or depending on tweaks, or sometimes randomly.
For example, earlier today, before began my latest round of tweaking, I had done the main market fix (market clear cache/force down, gsf clear data/force down, start market/get error/reboot), and with that, I could see Miren browser, but couldn't see SQL Editor, Adobe Air, Adobe Flash, or Xscope.
I then did a chance, similar to the Android ID changer posted in another thread, but I did it directly, by getting an AndroidID from a Droid, and then using sqlite3 to change the AndroidID on my Gtab. That didn't let me see more apps.
So, I changed the fingerprint in build.prop and did the market fix, and then I could see SQL Editor, but not Adobe Air/Flash, and Xscope.
Then, I set the time to 11:58PM, did the market fix, shutdown the Gtab, then waited.
When I powered the Gtab back on, after "midnight", I was really surprised that I could then see both Adobe Air and Adobe Flash. Still no Xscope, though.
Then, the latest step, I set the Gtab back to the correct time, and rebooted, and after that, I couldn't see Adobe Air and Adobe Flash, but now I can see Miren and Xscope.
It seems like chasing "full market" is really like "whack-a-mole", and so I'm starting to wonder if it's even possible to get there with the Gtab?
Sorry for going on, but this is really frustrating!!
Jim
Jim, I have been having some weird issues downloading with my Moto Droid for the last 2 days. I really think that Google is doing something with market. Oddly I seem to be having less problems with my GTab
thebadfrog said:
Jim, I have been having some weird issues downloading with my Moto Droid for the last 2 days. I really think that Google is doing something with market. Oddly I seem to be having less problems with my GTab
Click to expand...
Click to collapse
Hi,
I'm aware of the network problems (retry popup, etc.), but I've been at this (trying to get a full, consistent market) for awhile. What I related in my earlier post was just what I tried today, but this has been almost since I got the Gtab, just after Thanksgiving.
Mostly, it doesn't bother me, but earlier this week, there was post from reelportal asking to test his new app, which needed Air, which kind of got me going on this again. He had posted the Air APK, but it was still kind of bugging me.
I was really surprised to see Air appear in Market today, but then was shot down when it disappeared later.
Feel like I'm "chasing a ghost" with this (="whack-a-mole" )!!
Jim
BTW. You mentioned Droid. One of my sons has a Droid, and that has been what I was using as my 'baseline', to check if I should or shouldn't see an app. He could see every one, all the time.
That keeps leading me to believe that it is possible, which is what drives me batty about this!
Jim
See? This is the weirdness of all of this. Just posted in response on another thread:
No guarantees, but I've been messing with market, and I just got tank hero. I used Titanium backup and cleared data for market then for googleservicesframework, then started market, and bam. It was there!
Yes, it's back ... but xscope and miren are gone...
Hi,
OK, this is at least a little consistent, and so far, repeatable.
If I use TB to clear market then gsf data, then start market, I get the agreement page, then I can see Air, Flash, and Tank hero, but no xscope, miren, or startup auditor.
If I then do the regular market fix and reboot, I get miren, xscope, and startup auditor, but no Flash, Air, or Tank Hero.
I don't see the logic, but seems to be consistent.
Jim
I was trying to help someone earlier with "earthNC". Wasn't in market so I did the Titanium Market fix and it appeared.
thebadfrog said:
I was trying to help someone earlier with "earthNC". Wasn't in market so I did the Titanium Market fix and it appeared.
Click to expand...
Click to collapse
So are you seeing the same thing as I am? Doing data clear w TB, get Flash, Air, and Tank Hero, but not miren, xscope, or startup auditor, then do regular market fix get the reverse?
Does that make any sense?
Jim

stock 2.2 several questions

So I am probably one of the few that is running a completely stock unrooted nook I was playing around with the new update today and downloaded a handful of the free apps. I have several questions:
1) For some reason my Fliq Notes icon disappeared, I can still use the app perfectly fine, but it's showing a gray standard b&n icon, any way to fix this? I tried "archiving" it and installing again, no dice.
2) What is archiving anyway? I'm completely new to Android if that matters. Is it like uninstalling something in windows?
3) In the apps screen, what is that right most "refresh" looking button? Whenever I click it it just spins forever and never stops.
Overall I must say that the nook runs much smoother than it did with Android 2.1. PDFs seem to render faster, the web browser pinch to zoom is smoother as well. Flash is great!
I run a stock unrooted nook, except when I run off an SD card.
I have a similar issue with fliq calendar's icon. I have a suspicion, after reading some reviews on other sites, that this may be a fliq issue.
I agree that the whole experience is a lot smoother with the update.

Categories

Resources