Related
I don't have the app and I did these screens using a combo of home and back button. I'm more than positive those are the two to success.
Sent from my SGH-T959 using XDA App
draikz said:
I don't have the app and I did these screens using a combo of home and back button. I'm more than positive those are the two to success.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Most people have come to the same consensus but no one (as far as I know) has been able to reproduce the screen shot feature effectively.
yeah, i accidentally took a screen shot somehow when i was running bionix v 1.2 (i think that was the rom i was on). no clue how i did it and couldn't do it again, but it was some key combo...
Any idea how to capture videos with at least 24 fps?
Sent from my LG-P500 using XDA App
funeralthirst said:
yeah, i accidentally took a screen shot somehow when i was running bionix v 1.2 (i think that was the rom i was on). no clue how i did it and couldn't do it again, but it was some key combo...
Click to expand...
Click to collapse
Same here...
Sent from my SGH-T959 using Tapatalk
same here on bionix
I'm fairly certain it's because of lag. On the international galaxy S with froyo, you press the home button (the big thing in the middle of the touch sensitive keys) and back. This happens because the home key is not a touch sensitive key. On the vibrant the keys are all touch sensitive. I believe that they are not multitouch so you cannot hit both the home and back at the same time. So I think that somehow the home command is hanging up and the back key is pressed so it simulates the action that is supposed to give the screen shot. I think that samsung recognized this flaw and redid the commands on the galaxy tab. My tab takes screenshots by pressing the power and back.
nacron said:
I'm fairly certain it's because of lag. On the international galaxy S with froyo, you press the home button (the big thing in the middle of the touch sensitive keys) and back. This happens because the home key is not a touch sensitive key. On the vibrant the keys are all touch sensitive. I believe that they are not multitouch so you cannot hit both the home and back at the same time. So I think that somehow the home command is hanging up and the back key is pressed so it simulates the action that is supposed to give the screen shot. I think that samsung recognized this flaw and redid the commands on the galaxy tab. My tab takes screenshots by pressing the power and back.
Click to expand...
Click to collapse
sounds likely because my phone was lagging when i did it, but wouldn't that just cause a race condition? or maybe i running an i9k based kernel (i can't remember).
Your theory is probably fact. There are people with some SGS phones that claim they can take screenshots consistently with back+home while others, myself included took a screenshot accidentally and have been unable to reproduce it since. I recall that I had just upgraded to froyo.ka6 via mini kies and was adding/rearranging shortcuts to one of my home screens. I hit the home key to get back to my main home screen and I got a screen shot. Haven't been able to do it again.
Since my Vibrant came with Eclair and was later upgraded to Froyo I believe that this was a feature that just wasn't meant for Vibrant or just was overlooked when Samsung ported Froyo to Vibrant. This feature probably works reliably on phones that come stock with Froyo, not those that are upgraded to Froyo. It's almost as if Samsung wasn't planning on Froyo for the Vibrant but due to the outcry here and possibly other forums Samsung hastily modified the base Froyo and released it via kies mini.
ScreenCapture service is there, just no documentation exists on how to trigger it for Vibrant.
There is apparently one developer who has figured how to trigger the ScreenCapture service:
http://www.appbrain.com/app/screen-...tomorrowkey.android.screencaptureshortcutfree
The only screen capture app that DOES NOT require root but requires Froyo..It even saves to the same directory as ScreenCapture service. I use the free version and it works better than drocap2 or screenshot it on my Vibrant.
App looks interesting, but I don't agree with some of the permissions it requests..... like location and full internet access.
Another vote for home+back key combo taking a screenshot, and that functionality being crippled due to the all touch-sensitive vibrant keys as opposed to the physical i9000 home key. I have taken a screenshot before, and it was going back home by hitting the home button, then the app lagging and me hitting the back button to try to get out of the app.
Chalup said:
Any idea how to capture videos with at least 24 fps?
Sent from my LG-P500 using XDA App
Click to expand...
Click to collapse
Sent from my LG-P500 using XDA App
Bernardos70 said:
App looks interesting, but I don't agree with some of the permissions it requests..... like location and full internet access.
Another vote for home+back key combo taking a screenshot, and that functionality being crippled due to the all touch-sensitive vibrant keys as opposed to the physical i9000 home key. I have taken a screenshot before, and it was going back home by hitting the home button, then the app lagging and me hitting the back button to try to get out of the app.
Click to expand...
Click to collapse
I don't agree with the permissions either but it's nothing nefarious. It's ad-supported freeware, and like most adware the internet access and location permissions is to deliver targeted ads to you, such as if you're in New York you will then see ads for places near you. That's what adware is all about, no corporation cares where you are at any given time, they just want your money. There is a higher chance of success that you will respond to an advertisement that is targeted to your interests (that's what tracking cookies are for, if you browse a lot of sports related sites, most of the ads you will see will be sports related.)
The paid version has no ads btw. I wonder how effective ads are since most people I know ignore them entirely.
Anyway, after trying drocap2 and screenshotit screencaptureshortcut is still better for froyo since no root access is require and unlike drocap2 there is no 'screenshot captured' pasted on your images.
So far the best screen capture imo is Android SDK but that requires a PC. Non-PC is screencaptureshortcut.
Anyway now that one developer has figured out how to trigger ScreenCapture service I'm sure we'll be seeing more and better apps soon.
Mysterious screen shot has been happening to me too, I thought I was the only one!
Was searching for an answer to my mystery and I see this old thread, seems like I'm not the only one!!!
Is the mystery solved yet? It's been happening to me too lately, and just happened again about 20 mins ago. I don't know how I did it!
Ok so, I don't have any screen shot or screen capture apps installed on my phone. Yet sometimes mysteriously I take a screen capture. The phone says "screen captured" and it even makes an album in my gallery called "ScreenCapture" with the screen captured picture inside it.
I'm on rooted Froyo 2.2 KB5, and no screen capture apps installed.
I think the mystery involves a combination of the power button with one of the capactive buttons, but I can never reproduce it, it just happens by accident and freaks me out.
The only other time my phone has done something mysterious was when I somehow went into "safemode." Yes, "safemode" similar to Windows safemode. I have never been able to get back into safemode either.
2 mysteries of this phone I would love to solve.
SamsungVibrant said:
Was searching for an answer to my mystery and I see this old thread, seems like I'm not the only one!!!
Is the mystery solved yet? It's been happening to me too lately, and just happened again about 20 mins ago. I don't know how I did it!
Ok so, I don't have any screen shot or screen capture apps installed on my phone. Yet sometimes mysteriously I take a screen capture. The phone says "screen captured" and it even makes an album in my gallery called "ScreenCapture" with the screen captured picture inside it.
I'm on rooted Froyo 2.2 KB5, and no screen capture apps installed.
I think the mystery involves a combination of the power button with one of the capactive buttons, but I can never reproduce it, it just happens by accident and freaks me out.
The only other time my phone has done something mysterious was when I somehow went into "safemode." Yes, "safemode" similar to Windows safemode. I have never been able to get back into safemode either.
2 mysteries of this phone I would love to solve.
Click to expand...
Click to collapse
I don't think its been solved
I just downloaded an app to take screenies.
I've pretty much been experiencing this issue since I got my Xoom, but can't find any information on it. Most of the time when attempting to use the back button in the browser it does nothing. If I press it multiple times it sometimes triggers, but I usually end up multiple pages back. Anyone else experiencing this issue?
Sent from my Xoom using XDA Premium App
Try switching to Quick Controls, and see if the back button there exhibits the same behavior:
Browser | Settings | Labs | Quick Controls
Touch the edge of the screen to bring up the control wheel, then swipe to the back button. Does this also not register?
zonk7ate9 said:
I've pretty much been experiencing this issue since I got my Xoom, but can't find any information on it. Most of the time when attempting to use the back button in the browser it does nothing. If I press it multiple times it sometimes triggers, but I usually end up multiple pages back. Anyone else experiencing this issue?
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
i rarely use the browser back i use the the back button on the notification bar and have no issues with it. if the web page has re-directs before it when you hit back it will just re-direct you to the same page
I actually use the notification bar back button most of the time too, but it is the same function. I tried the thumb controls with no luck. I think it may be just the site as the others I had issue with (all heavy JavaScript) seem to work fine now.
Sent from my Xoom using XDA Premium App
zonk7ate9 said:
I've pretty much been experiencing this issue since I got my Xoom, but can't find any information on it. Most of the time when attempting to use the back button in the browser it does nothing. If I press it multiple times it sometimes triggers, but I usually end up multiple pages back. Anyone else experiencing this issue?
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
I've had this problem, too. At first I thought it was similar to the twitter issue on phones, where you have to mash back a few times to actually leave a twitter page, but it seems to happen any time I load a webpage with flash on it. I haven't really had a problem when it comes to pages without flash elements, but who knows if that's actually the problem.
Have you updated to the latest version of flash? It greatly increased the performance and decreased the strain it would cause on the CPU/browser.
I too am experiencing this bug. It doesn't do it for every site, but is getting more frequent. Did you find a fix for this? I I am running rooted 3.1
I have the same problem as well, it all seemed to start when I flashed someone CWM flashable desktop UA String fix
I've got the same thing on my Transformer, must be a bug in the browser.
I never had that problem , maybe it's because you are rooted . However , I do have this problem with gmail .
Have you all changed the browsers default (as in, by somehow changing the framework, and not the about:debug method) UA String to desktop? I have only been having this problem since I flashed someones UA String fix on my Wifi only Xoom (US). I know that changing the UA String's/browsers framework can cause some weird things to happen such as with one fix, the screen won't rotate 180° from the normal landscape view (Camera ontop and Motorola logo/name are to the top left of ur screen. Please respond if you have done a UA String change and now have the back button issue or other issues, thxs.
Sent from my Motorola A855 Engineering Dev Build using XDA App
I have not modified the browser in any way apart from rooting.
I have that bug. Going to apps / all apps and clear cache and force close browser helps it. I have a modified UA string. But having done the mod myself, I can't see how it would mess up the back button. I'm betting bug.
It does look like a bug, but seen as there at not a huge amount of seems to make me thinks it could be fixed by wiping the browser settings. Maybe some configuration somewhere got corrupted. Is there a way, say using titanium backup, to wipe just the browser settings?
Clearing the Data and Cache for the App in settings should clear all of these, if you want to reinstall the whole browser your probably going to have to reflash your ROM and clear all data and cache.
I am having this same issue I went back to completely stock and flashed tiamat 1.4.4 and it still does it! The issue occurs in both the stock browser and Dolphin HD it is extremely annoying!
i finally found a solution if you update the host list in adfree android it causes the back button to not function properly. I reverted my host list and everything works great now! I ended up uninstalling adfree though cuz its nearly useless without host list updates
I can confirm this fix, frustrating as it is you can choose this bug or ads. I personally choosenthe bug. Maybe there will be a better fix later on, maybe something to do with the ip of the hosts file
OK, I have been messing around with this and I noticed that when the back button doesn't do anything there was an iframe ad that just refreshed the iframe.
So, I changed the ip in adfree to be a pc on my lan with an apache server. It was setup to redirect all traffic from a blank page. This stopped the iframe from refreshing. Now the back button works fine
Now, does anyone with more knowhow know of a more efficient way to sort this out? I have a wifi xoom that is always at home so it's OK for me, but for others a better solution is needed
Ive got this bug too -- can you be more specific how to edit the hosts file?
I can take no credit for this ROM, as I'm only making a package for us Cappy users to try. This is the new I9000XXJVT ROM with a build date of 29 Sep.
It's has SU and is deodexed/zipaligned.
All credit goes to Ramad over at the I9000 section for putting this CWM package together. All I did was replace the kernel with DC 4.0 -Cappy edition.
His original thread is here: http://forum.xda-developers.com/showthread.php?t=1290577
Many thanks goes to:
Ficeto - for making the DC Kernel for the Cappy
Xcal - for the home button fix
fuloplori - for reminding me of the home button fix
And I am of course not responsible if your phone sprouts legs and starts running and screaming down the street.
Do not forget to apply the home button fix attached.
ROM can be downloaded here:http://www.mediafire.com/?5mflw24c7oyvc99
Thanks now can you make apex based on this?
Sent from my SGH-I897 using xda premium
yobbei said:
Thanks now can you make apex based on this?
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
LOL, if I only knew how. I'm pretty much a noob at this. Anything that takes much more than what I had to do for this, I'm lost.
Nice work could you please upload some pictures
It's a stock rom, you don't need pictures.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Good work. Now only if you can add home haptic and remove video call references, people will be all over it
watsa said:
Good work. Now only if you can add home haptic and remove video call references, people will be all over it
Click to expand...
Click to collapse
Thanks man. I was really only trying to see if this fixed the wifi issue that started in JVS, and also to try and spur the few devs that are left here on the cappy side to take this and make it their own.
I think we're going to get together and buy you a Cappy just so we can keep you around! LOL
F1reEng1neRed said:
Thanks man. I was really only trying to see if this fixed the wifi issue that started in JVS, and also to try and spur the few devs that are left here on the cappy side to take this and make it their own.
I think we're going to get together and buy you a Cappy just so we can keep you around! LOL
Click to expand...
Click to collapse
So did it solve the wifi issue?
yobbei said:
So did it solve the wifi issue?
Click to expand...
Click to collapse
The fix for me and several others was to change the DHCP lease time on my router to something other than "forever". Same applies for JVS.
If you had the problem on JVS, you will most likely still have it on JVT. Many people never had the problem on JVS to begin with and didn't have it after flashing JVT either.
watsa said:
Good work. Now only if you can add home haptic and remove video call references, people will be all over it
Click to expand...
Click to collapse
yeaaaa, home haptic would be very good, i got in a bootloop when i made my home haptic fix, :\
Wondering how to remove video reference, add home button haptic feed back and button lit on screen touch... am I requesting too much?
Grab services.jar from a rom where had those previously enabled. U'll find it under system/framework folder.
The video reference part I can't help u with, someone else pls step up
amtrakcn said:
Wondering how to remove video reference, add home button haptic feed back and button lit on screen touch... am I requesting too much?
Click to expand...
Click to collapse
Yes, any home button haptic feed back CWM fix?
Haptic feed back is easy to fix go into the system folder used root explorer or something and then go to Usr/keylayout then edit the melfas_touchkey.kl and the first four buttons change the Wake_dropped so it says Virtual...
If this helped hit thanks button
In the past week I've experienced a couple of weird things w/ my phone. I'm stock, using Go Launcher and handcent (this may or may not be relevant to my issues, but I figured it's worth noting).
First, my phone went crazy one night as I tried to respond to a text message. I was trying to respond in the text pop-up window (quick reply) when my phone just starting displaying random letters, as if I were holding a key down (I was using the touchscreen and my keyboard wasn't open). At first I thought I was having issues w/ handcent (mistyping), but as soon as I let off the backspace key the letters would resume displaying. At this point I felt as if I was competing against my phone . After a few tries I just did a battery pull and haven't had a problem since. So I was just wondering if anyone has ever experienced this before.
Second, has anyone else noticed that a space is now printed immediately after typing the "$" (it didn't used to before a week or so ago)? I don't think I changed any settings, but if anyone knows if I have, and you can tell me how to get it back to no space following the "$" I'd really appreciate it. It's just really annoying
Thanks for help, feedback, etc. in advance!
I know the space after "$" started for me after the update to the current stock version. If you swype from the space button along the bottom to the backspace it will temporarily disable auto-space until a new word is swyped it space is tapped. The rest of that never happened to me.
Sent from my SPH-D700 using Tapatalk
In both cases, were you using the physical keyboard or the screen? If the physical keyboard, it sounds like maybe the ribbon cable or the keyboard itself has been damaged.
If it was an onscreen keyboard, don't know, maybe clear data on the keyboard app?
Thanks for the tip R3537L1F3
BhRaElEfD said:
Thanks for the tip R3537L1F3
Click to expand...
Click to collapse
You're welcome, I actually found that by accident and was determined to find out how I did it XD. Glad something I found on acident helped.
Sent from my SPH-D700 using Tapatalk
Maybe there's a ghost in your house?
poit said:
In both cases, were you using the physical keyboard or the screen? If the physical keyboard, it sounds like maybe the ribbon cable or the keyboard itself has been damaged.
If it was an onscreen keyboard, don't know, maybe clear data on the keyboard app?
Click to expand...
Click to collapse
Already answered in the OP, but the attempt to help is appreciated
As for the glitch - if it has only happened once, then it was probably a fluke, a random crash of some system component. If you are able to duplicate the problem, then try to get to your computer, connect the phone and use "adb logcat" from a command prompt on said computer (not on the phone - since you probably won't be able to type into the terminal emulator any more effectively than you can in a text). Ctrl-c immediately to stop the logcat (it will run continuously otherwise), then copy and paste the output into a text file. This log information may contain clues about the cause, so paste it here (or a link to pastebin, whatever method you prefer)
Sent from my SPH-D700 using XDA
All I know is it wasn't me.
Sent from my SPH-D700 using XDA App
Hi!
I'm new to the XDA forums.
I have noticed a strange behaviour using buttons while exit applications on KitKat. The issue was not present in Jelly Bean, while I can notice it in KitKat. I thought it was a minor 4.4 bug, but it's still present in 4.4.2 too.
I am running Android 4.4.2 on a Nexus 4, no root, no system modifications at all.
Steps to reproduce the bug:
- Go to your home screen.
- Tap on battery settings from the quick settings dropdown menu;
- Use home button to come back to the home screen;
- Once again, tap on battery settings from the quick settings dropdown menu;
- This time, use back button to go back;
- Enjoy another background app opening for a second with no reason before going back to your home screen.
I cannot post videos since I'm a new user, but if you wanna check, the youtube code for it is 40Rs6vnx_Wc
Thanks in advance!
No one?
Yes, I've reproduced that but why should it be a bug? Or may be you should learn how the back button in android works? Why do you use it at all when you have the home button and the fast app switching button? It's a matter of time for the back button to be dropped down. Unless of course the "only one home button" thing is not patented by Apple so that back button has to stay. Remember what happened with the search button? It's gone for good. And really that back button is only useful in browsers or if you want to go backwards a sequence of actions inside a single app. Most apps use the back button to quit or run in the background.
Sent from my Nexus 4 using xda app-developers app
evdrmr said:
Yes, I've reproduced that but why should it be a bug? Or may be you should learn how the back button in android works? Why do you use it at all when you have the home button and the fast app switching button? It's a matter of time for the back button to be dropped down. Unless of course the "only one home button" thing is not patented by Apple so that back button has to stay. Remember what happened with the search button? It's gone for good. And really that back button is only useful in browsers or if you want to go backwards a sequence of actions inside a single app. Most apps use the back button to quit or run in the background.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
@evdrmr, thanks for the feedback.
I still don't get the hatred, but thank you for the time spent in reproducing the bug and confirming that I'm not the only one affected by this issue.
Yeah...der for me too... noticed it some time back while i was on 4.0 too... don't think its caused by 4.4.2 (rather not fixed by 4.4.2)...
And somehow, its always the gallery app for me...
quarara said:
Hi!
I'm new to the XDA forums.
I have noticed a strange behaviour using buttons while exit applications on KitKat. The issue was not present in Jelly Bean, while I can notice it in KitKat. I thought it was a minor 4.4 bug, but it's still present in 4.4.2 too.
I am running Android 4.4.2 on a Nexus 4, no root, no system modifications at all.
Steps to reproduce the bug:
- Go to your home screen.
- Tap on battery settings from the quick settings dropdown menu;
- Use home button to come back to the home screen;
- Once again, tap on battery settings from the quick settings dropdown menu;
- This time, use back button to go back;
- Enjoy another background app opening for a second with no reason before going back to your home screen.
I cannot post videos since I'm a new user, but if you wanna check, the youtube code for it is 40Rs6vnx_Wc
Thanks in advance!
Click to expand...
Click to collapse
mananbond007 said:
Yeah...der for me too... noticed it some time back while i was on 4.0 too... don't think its caused by 4.4.2 (rather not fixed by 4.4.2)...
And somehow, its always the gallery app for me...
Click to expand...
Click to collapse
@mananbond007, thanks for taking the time to checking it out
No hatred matey. It's just one of those days... You know. Last night I went to the cinema and watched The Hobbit, had only a couple of hours to sleep, woke up early... Usual stuff.
Oh, and do you know what? It could be a bug... Why don't you report it to Google or to a bug tracker? Have you checked all available 4.4.2 ROMs if they are infected with it or someone has already found a cure? Or why don't you exploit it further and write a dirty little app to gain control over people's phones through this flaw? And how the f*ck did you even find it? Sounds like an incredible amount of spare time on your hands to me. Or just a pattern based repetitive clicks due to lack of "some more important things to do"?
Sent from my Nexus 4 using xda app-developers app
Good catch. Same here on Stock 4.4.2
andr0idfreak said:
Good catch. Same here on Stock 4.4.2
Click to expand...
Click to collapse
Thank you, @andr0idfreak
In the meantime, I have filed a bug in the AOSP issue tracker. Its number is 63570.
quarara said:
Thank you, @andr0idfreak
In the meantime, I have filed a bug in the AOSP issue tracker. Its number is 63570.
Click to expand...
Click to collapse
Starred
Yes. Me too. For me it was my last opened app that appear and then gone.
evdrmr said:
No hatred matey. It's just one of those days... You know. Last night I went to the cinema and watched The Hobbit, had only a couple of hours to sleep, woke up early... Usual stuff.
Oh, and do you know what? It could be a bug... Why don't you report it to Google or to a bug tracker? Have you checked all available 4.4.2 ROMs if they are infected with it or someone has already found a cure? Or why don't you exploit it further and write a dirty little app to gain control over people's phones through this flaw? And how the f*ck did you even find it? Sounds like an incredible amount of spare time on your hands to me. Or just a pattern based repetitive clicks due to lack of "some more important things to do"?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
You my friend, are a pathetic douchebag. I need not say more.
AlwaysDroid said:
You my friend, are a pathetic douchebag. I need not say more.
Click to expand...
Click to collapse
Thank you so much about that comparison. I like it and I wouldn't be able to think of a better phrase to describe myself. And do you know why I like it so much??? ...OFC you don't. Because Kuoshik Dutta used to be called exactly the same by many people recently and still he is one of the best developers out there. That makes me feel one step closer to the gods. Off the off-topic.
Sorry but I couldn't understand what's your opinion about the bug?
Sent from my Nexus 4 using xda app-developers app
Same here, it opens the last app. Can someone provide a link so I can report the bug with that number? 63570
Same happens here. On stock 4.4.2. Hope this is get fixed.
Sent from my Nexus 4 using xda app-developers app
I don't have that bug!
According to the bug report, it looks like the bug has been assigned to a Google engineer.
Same bug here but it happens often and with many apps. Going back and a cached app appears for a second