I have an un-modified galaxy Tab although it is rooted.
I haven't had any issues with it since I got it.. (Days after it was released). However, recently, whenever I am recording video with it, it stops recording randomly.. Sometimes after 30 seconds, sometimes, 47 seconds, or any other seemingly random amount of time. This is getting very annoying. I've tried saving file to both SD card and internal memory (Both have lots of space).
Any one else have this issue? Or think they know what it could be?
Edit - Upon further observation, it appears that the LED light turns off a fraction of asecond before the video stops recording all on it's own.. Not sure if this has any bearing on it but just thought I would add it.
Hate to bump this but I'm still running into this issue.
Related
Hello Guys,
a Friend bought a used i9000 on ebay for 130€ from a business man, which got a ne phone from his company and sold hin mobile on ebay and he asked me for a litte work around of his "new" phone.
Optically is the phone perfect BUT if I take a call on Android 2.3.6 display stays black (with backlight) and I can make the call. But I can't do anything more, hang up etc. If the opponent hangs up, I hear the hang up sound but display stays black and thephone wount do anything. So it's needet to pull battery, put it back and restart the phone. On doing a call, the phone has similar problems, it freezes.
After a couple of re-flashes with odin nothing changed.
So I tryed to switch to actual android OS. I flashed SlimBean 2.7. Every thing workes well. but even call-issues. If i receive a call, the phone woun't do anythin and it keeps ringing and "holds" the call for exactly 32 seconds. Now I can talk with the caller. But most callers don't wait 32 seconds to call to me If I do a call in JB I can talk from the first second on, but display freezes and I can't hang up. Thats the state for around 28 seconds and then phone will response normally and I can hang on and do everything I whant.
Even in Slim I tryed reflash a fiew times with no cahnge.
Has anyone an idea?
I think thats a hardware related problem. But in fact its possible to do a call, but only with that issues/delays. So I need a solution, that JB (SlimBean 2.7) don't "hold" the call/freezes for 32 seconds. I think because its every time 32 seconds, thats a fix value in JB. so I need something to cahnge the value from 32 secs to may be 0 oder maximum 5. But thats only guessed by me so I need help of a PRO here to solve that nerving issue.
I also tryed to install other dialers, but thats not a good solution, because the use for calling the stock rom dialer (phone.apk), damn
Please help me guys (sorry for my bad english )
UPDATE: I did read a litte in web and found, that the light sensor could cause issues in calling (start and end). So I downloaded a app whitch will show me he values of the light sensor. Ands its true, the sensor will show me whole time same values. I changed the sensor od the device of my friend and mine but that does not solve the problem. same issue.
In second Post I'll load a some Pictures of both devices up. My device shows around 30 lux and the one of my friend around 5.
UPDATE 2: After some more reading in web I found more guys with same call problem but no solution. May be it could help to disable GP2A Driver oder better only to overwrite the lightsensor value with a fix one.
UPDATE 3: OK I tested with 3 apps and the proximity sensor of the phone is broken ...now i need a solution to disable it or set a fix value in android so that the sensor is unused.
Any ideas?
UPDATE 4: I downloaded the "Hardware Disable" app from Play store and disabled GP2A.
It works for now, I just have to switch off the screen manually by pushing power button at a call and turn it on by pushing power again. But thats no problem for me anf my friend and much better as the call related freezes.
But I need at every startup to confirm to disable the sensor. So I'm looking for a permanent solution for this. Also because the device feels a little bit laggy now.
Pics
SOLUTION
So Guys I found a good working solution fpr proximity sensor delay, 32 second freeze by taking a call.
I wrote my Solution in SlimBean thread
http://forum.xda-developers.com/showpost.php?p=32809014&postcount=4406
Schould work on any ROM (GB, ICS and JB) because they all use the same Hardware .so (sensors.aries.so in this case)
Hello!
I hope this forum isn't 100% dead...
I had to take my Kaiser out of my closet because my HD2's screen broke and I can't afford a replacement. I flashed Android to it and I was surprised, how fast does it work on so weak hardware. But my problem is that I installed few apps (Next browser, Heroes 2 port - nevermind it works unplayable, exDialer, ES file explorer, updated all apps already present in ROM...), and I'm using PowerAmp to listen for music. But it simply doesn't work properly. When I turn the screen off, after a few seconds, playback stops. Did anyone suffer the same issue as me? I'm using Scoot's CyanogenMod 6 rom.
Also, I have another problem. Every time I turn on the scree, it goes white for a moment, then it shows some garbage and in the end, it shows everything properly. But it takes a while until it finishes. Maybe there's a cure for it, too?
I've notice that sometimes my photos/vídeos disappear from my cellphone.
At first I noticed with media received from whatssapp and I thout it was an app issue and don't give to much attention to it.
Now I realized that recent media disappear, and then paying more attention I notice that they disappear just after my cellphone suddenly shutdown when running low battery.
Today I had a sad story, I was recording a trial, after that while using Waze my phone just shutdown without showing the logo information "shutting down". When I charged my phone and tryed to send the videos to people in the trial they do not appear. Searching for them I discovered the files still there, but the size now is 0 kB (and I watched some of them before the sudden shutdown)
So the question is, does anyone is facing the same issue? Is there a known solution? And the most important to me, does anyone know how to recover the videos?
Since Android does not appear anymore as a common removable card I can not use anymore tools like "miniTool Power Data Recovery".
Can anyone help me?
Thanks
My SM-T815 (Tab S2 9.7 4G) has a habit of becoming completely unresponsive to all touchscreen actions for 20-30 seconds. This can happen in a wide variety of apps. I'm running stock Android 6.0.1. The hard button usually works.
Has anyone else had this problem?
I came here to see if someobody else has this problem. Apparently you do.
The Tablet freezes from time to time, screen turns black, and it becomes unresponsive for a few minutes.
I have many apps on a fast external SD, I figured this might be one of the reasons.
Strangely it has become worse the past few weeks.
trialbin said:
I came here to see if someobody else has this problem. Apparently you do.
The Tablet freezes from time to time, screen turns black, and it becomes unresponsive for a few minutes.
I have many apps on a fast external SD, I figured this might be one of the reasons.
Strangely it has become worse the past few weeks.
Click to expand...
Click to collapse
My screen doesn't go black - it just stops responding to all touches (the home button usually responds though). I also DON'T have any apps installed on the external SD card. So it sounds like we may not have exactly the same problem????
Anyone experience Camera Crash on vídeo?
I noticed that always Crash or récord a corrupted file when you start recording on low light enviroments ,the problem scalates till the phone warm Up and power off itself ,no rebooting only poweroff
Edited.
After a while trying to récord grandpha 's Party i realized that only happens with stabilitation on while have very dark enviroments,(such as night,caves or dark rooms) after deactivate the stabillitation i can récord normally.
I supose trepidation on low light forces Up the gimball crashing the app.
No Problems here. Looks like RAM errors or similar. Try to reset the phone or exchange.
I reboot the phone 5 times maybe a bug still no answer but there si no new problems