Hi guys, I'm having a problem with my xperia play when trying to record conferences.
My camera stops after 10 minutes of recording everytime, it even shows the timer backwards when it's the last minute, I was wondering if there is any way to lift this limitation.
I'm currently using the default camera application that comes with 2.3.4 North America generic ROM.
I got a 12GB memory card with around 3.2GB free and the video files take up to 400mb per 10 minutes, so the space shouldn't be a problem here.
Any help will be greatly appreciated, thanks!
Maybe your phones is going to sleep?
Have you tried disabling sleep timeout?
Masters2150 said:
Maybe your phones is going to sleep?
Have you tried disabling sleep timeout?
Click to expand...
Click to collapse
Hmm I wasn't aware that the phone had a sleep option, I can't seem to find it. Only time outs I could find if the screen display which is set to 30 seconds, so I guess that's not it.
Where can I find the options to disable the phone from sleeping?
Thanks.
Actually thats probably what I was thinking.
One thing you could try, when it gets close to 10 minutes, push a button on your phone, nothing to make it stop recording, maybe the settings button, just something to make sure it isn't a problem like this.
Masters2150 said:
Actually thats probably what I was thinking.
One thing you could try, when it gets close to 10 minutes, push a button on your phone, nothing to make it stop recording, maybe the settings button, just something to make sure it isn't a problem like this.
Click to expand...
Click to collapse
I did that and the phone responded perfectly, even changed some options while recording but it still stops at 10 minutes. The strange thing is when it gets to minute nine the counter changes backwards to count 1 minute in red numbers then it stops recording.
Maybe try a different phone app?
Sent from my R800i using XDA App
Related
Sometimes when my phone rings I can't get it out of lock to answer the phone. When the caller hangs up only then I can answer. This is intermitant. I don't know what to do.
Running the stock ROM, and rooted with unrevoked.
michelbites said:
Sometimes when my phone rings I can't get it out of lock to answer the phone. When the caller hangs up only then I can answer. This is intermitant. I don't know what to do.
Click to expand...
Click to collapse
What ROM are you running? Rooted or not rooted? These are things you should remember to post when you're having issues. Makes diagnostics much easier
All I have done was root it. I didn't install any rom or anything. I only rooted it to get the wifi tethering.
So screen turns on, but you are not able to press "answer" when a call is incoming?
Its telling you to hang up on stock rom and go custom. Plus you have better support specially being in this community.
Just saying
Sent from my ADR6300 using XDA App
nikon_rh50 said:
Its telling you to hang up on stock rom and go custom. Plus you have better support specially being in this community.
Just saying
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I'm inclined to agree. Custom ROMs definitely go waaaaay above and beyond the stock one. I use a combination of MyBackup Root and Titanium Backup free for contacts/messages and apps, respectively. Once you go custom, you never go back
What I was trying to say is that the screen is locked when the phone rings and then when I go to answer the phone it will not unlock until the phone stops ringing. But like I said in the first post this doesn't happen all the time. I would say about 25% of the time it does this. Sooo... Thats what I was trying to say.
Are you using Google Voice?
Are you using Google Voice to direct your calls? I have 3 phones that GV directs my calls to, and I've noticed that sometimes that causes one or the other of the phones to ring "late". Sometimes the Inc, sometimes not. I don't notice an issue when someone calls my direct line to any of the phones.
I am wondering what you would get if you use an app like No Lock that disables the lock screen.
I started using it when I had a roms lock screen fighting with a launcher's lock screen. I would get stacked lock screens, but only sometimes.
Running without a lock screen is not for everyone, so think about how you use your phone before disabling this great security feature. For me, my phone never leaves my side, and I mean NEVER. And if a "friend" starts poking at my phone I start poking in their face or purse... They learn after awhile.
reisa said:
Are you using Google Voice to direct your calls? I have 3 phones that GV directs my calls to, and I've noticed that sometimes that causes one or the other of the phones to ring "late". Sometimes the Inc, sometimes not. I don't notice an issue when someone calls my direct line to any of the phones.
Click to expand...
Click to collapse
I thought it was GV also but its not I uninstalled it and it would still do it.
Manitook said:
I am wondering what you would get if you use an app like No Lock that disables the lock screen.
I started using it when I had a roms lock screen fighting with a launcher's lock screen. I would get stacked lock screens, but only sometimes.
Running without a lock screen is not for everyone, so think about how you use your phone before disabling this great security feature. For me, my phone never leaves my side, and I mean NEVER. And if a "friend" starts poking at my phone I start poking in their face or purse... They learn after awhile.
Click to expand...
Click to collapse
I'm not sure if I would like the no lock because I tend to put my phone in my pocket all the time and it would just turn on and pocket dial people. LoL
Manitook said:
Running without a lock screen is not for everyone, so think about how you use your phone before disabling this great security feature. For me, my phone never leaves my side, and I mean NEVER. And if a "friend" starts poking at my phone I start poking in their face or purse... They learn after awhile.
Click to expand...
Click to collapse
App protector sounds like a good app for you.
Sent from my ADR6300
SetCPU?
Assuming screen is off when it cannot be unlocked - but...
Are you running SetCPU w/ a low screen off profile?
If not, maybe install SetCPU, and set a higher frequency in the screen off profile settings.
SetCPU is available in the market; it's also available as a free d/l for XDA members here on XDA.
smtom said:
Assuming screen is off when it cannot be unlocked - but...
Are you running SetCPU w/ a low screen off profile?
If not, maybe install SetCPU, and set a higher frequency in the screen off profile settings.
SetCPU is available in the market; it's also available as a free d/l for XDA members here on XDA.
Click to expand...
Click to collapse
Good call, I do remember when I was revving CPU way down with screen off. When it had been off for ~1-2 hours it'd be sluggish and take a bit for the CPU to rev back up. Never used it that long though because the Kernel I'm using now does this and using setCPU just chews up battery.
POQbum said:
Good call, I do remember when I was revving CPU way down with screen off. When it had been off for ~1-2 hours it'd be sluggish and take a bit for the CPU to rev back up. Never used it that long though because the Kernel I'm using now does this and using setCPU just chews up battery.
Click to expand...
Click to collapse
Well, there's something to try then - if the kernel is making the device slow to wake, use SetCPU to bump up the screen off profile and see if the issue persists.
Couple folk note just this issue in the kernel threads.
This is a known problem I struggle with myself. You may find that you can stroke up to deny the call but not unlock. It seems that this is some kind of grounding problem. Hearing that I tried setting the phone down and swiping while I wasn't touching it otherwise with some success. I've heard a quick cycle of the power button followed by an immediate swipe down can work. Some report pressing the screen firmly before swiping works. I usually just swipe up, call back and say "sorry about that, what's up?" After all, most people are used to drops and stuff because of Iphones.
I periodically goog "incredible can't answer" looking for the golden bullet.
So, overall I'm very happy with CM7, but there's one major issue with it.
Whenever someone calls me, it takes about 5-10 seconds for the screen to turn on and the accept/reject sliders to come up...
Help? :[
nejc121 said:
So, overall I'm very happy with CM7, but there's one major issue with it.
Whenever someone calls me, it takes about 5-10 seconds for the screen to turn on and the accept/reject sliders to come up...
Help? :[
Click to expand...
Click to collapse
I dont have these problems...even afther reboot?...do you use task killer,maybe its autokilling phone
Auto-kill is off. :/
I am on CM7 and having this issue as well. Not as bad as the OP but it takes a while for the screen to be on and let me answer the call. This happened to me even before playing with the cpu speed. So I can rule that out as the culprit.
Sent from my HTC Wildfire using XDA App
Hey guys, on my nexus when im typing anything I turn it to landscape mode for the bigger keyboard and sometimes it takes ages for the screen to follow - sometimes it doesn't do it at all. Anyone else have this prob?
It is slow on purpose.
Sent from my Galaxy Nexus using xda premium
So that if you are in bed and turn sideways it doesn't just keep switching, and other similar situations.
No guys, I mean REALLY slow, as in 5-10 seconds. Sometimes I have to keep movin it around untill it turns. Today however its really playing up and not turning at all.. haha
AntonyStark said:
So that if you are in bed and turn sideways it doesn't just keep switching, and other similar situations.
Click to expand...
Click to collapse
I find that actually it's the exact opposite.
When I want it to rotate, I need to wait ages (sometimes tapping the screen while waiting makes it faster).
When I lie in bed, it very often rotates when I don't want it to, and then I wait ages for it to switch back to the previous mode.
That pretty much forces me to disable automatic rotation every time I am in the bed. Whatever they tried to achieve with this, either they failed completely or I am somehow mysteriously missing the point..
macfre said:
I find that actually it's the exact opposite.
When I want it to rotate, I need to wait ages (sometimes tapping the screen while waiting makes it faster).
When I lie in bed, it very often rotates when I don't want it to, and then I wait ages for it to switch back to the previous mode.
That pretty much forces me to disable automatic rotation every time I am in the bed. Whatever they tried to achieve with this, either they failed completely or I am somehow mysteriously missing the point..
Click to expand...
Click to collapse
Glad its not just me then. Ive just tried it again, while Im sat down and its working okay. Seems to be when Im walking about its a problem.. (and no, I dont walk leaning to one side or something.. haha)
macfre said:
I find that actually it's the exact opposite.
When I want it to rotate, I need to wait ages (sometimes tapping the screen while waiting makes it faster).
When I lie in bed, it very often rotates when I don't want it to, and then I wait ages for it to switch back to the previous mode.
That pretty much forces me to disable automatic rotation every time I am in the bed. Whatever they tried to achieve with this, either they failed completely or I am somehow mysteriously missing the point..
Click to expand...
Click to collapse
Mine has been staying, and being used to the HTC Desire spinning instantly it was a bit strange at first. As regards to the tapping, there are some modes where tapping is what rotates it and it wont until you do.
Same damn concern very annoying
Sent from my Galaxy Nexus using Tapatalk
AntonyStark said:
As regards to the tapping, there are some modes where tapping is what rotates it and it wont until you do.
Click to expand...
Click to collapse
I mean in applications like the stock Browser. I'm not 100% sure, but 99% that it rotates faster if I tap the screen as compared to just waiting.
micflair said:
Hey guys, on my nexus when im typing anything I turn it to landscape mode for the bigger keyboard and sometimes it takes ages for the screen to follow - sometimes it doesn't do it at all. Anyone else have this prob?
Click to expand...
Click to collapse
it's not slow
it's the smooth transition animation (like windows IE)
you will need some 3rd party tweak to disable it
AllGamer said:
it's not slow
it's the smooth transition animation (like windows IE)
you will need some 3rd party tweak to disable it
Click to expand...
Click to collapse
No mate, its slow. Like I have said - sometimes it wont move at all without me shaking the damn thing. Im glad its not just me though!
I had the same problem. Seems to be fixed in the the latest update I just got 2 minutes ago.
Sent from my Galaxy Nexus using Tapatalk
Dr Tone said:
I had the same problem. Seems to be fixed in the the latest update I just got 2 minutes ago.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Got the same problem, what update did you get? Whats the version?
YevS said:
Got the same problem, what update did you get? Whats the version?
Click to expand...
Click to collapse
ITL41F.I9250UGKL1
Kernel Version: 3.0.1-ga052f63
Many have the same problem concerning rotation.
On Google, search with these keywords : Galaxy Nexus slow rotation
Bonne journée!
I dont recognize this problem, my screen turns when i tilt the phone.
Bjidi said:
I dont recognize this problem, my screen turns when i tilt the phone.
Click to expand...
Click to collapse
OP is talking about the screen taking awhile to finally rotate when he tilts the phone. He isn't talking about the phone not tilting at all.
Sent from my Galaxy Nexus using XDA App
Dr Tone said:
ITL41F.I9250UGKL1
Kernel Version: 3.0.1-ga052f63
Click to expand...
Click to collapse
I have I9250XXKK1
Maybe just a regional difference?
I was just wondering if this happens to anyone else. So sometimes I go to unlock and the screen doesn't let me do anything, it happens not just when unlocking but when I'm using the phone too, it's really annoying when I'm trying to text someone back or try to answer a call. It doesn't happen all the time so I could live with it....but I'm wondering if anyone has a fix or has the same problem.
Also I have my phone rooted and g3 tweaksbox, and I turned off the knock in code..I don't know if any of these have factors.
WendyB87 said:
I was just wondering if this happens to anyone else. So sometimes I go to unlock and the screen doesn't let me do anything, it happens not just when unlocking but when I'm using the phone too, it's really annoying when I'm trying to text someone back or try to answer a call. It doesn't happen all the time so I could live with it....but I'm wondering if anyone has a fix or has the same problem.
Also I have my phone rooted and g3 tweaksbox, and I turned off the knock in code..I don't know if any of these have factors.
Click to expand...
Click to collapse
Is it lag? Does it only happen for a few seconds before it starts again?
It's not lag..I don't think unless it's a really long lag ?... I turn my screen on and off and it would still be frozen. Maybe after a few mins of turning the screen off and on again it will work...
WendyB87 said:
It's not lag..I don't think unless it's a really long lag ?... I turn my screen on and off and it would still be frozen. Maybe after a few mind not turning the screen off and on again it will work...
Click to expand...
Click to collapse
Sounds faulty i think.I'd get the phone freezing for a few seconds before it responded, but that was lag.
Aww man that would suck if it was... That's the only problem I have!
WendyB87 said:
Aww man that would suck if it was... That's the only problem I have!
Click to expand...
Click to collapse
i had this problem..it would lock up..freeze and i had to wait for a min or so to come back to life..a hard reset fixed it
Oh okay! That is good to know...I guess I'll be trying that soon
I have the same issue as well.
It's not that the screen "stopped" working. It works, except there's no update on the screen. As if the entire phone is frozen, but it's still giving me haptic feedbacks. Except, actions aren't being reflected on the UI; things like, tapping home navbar button, doesn't take me to the launcher, tapping up/back doesn't take me to the previous screen. I can lock/unlock the phone, but I'd return to the whatever page of the app that corresponds to the back/up command I previously made.
I think, the easiest way I can summarize this is that the OS stopped doing visual updates, while there's actually stuff going on despite that "stuck" screen.
Problem: Cannot turn on the screen by pressing the power button sometimes. The screen is black or very dim, I cannot tell. One can see nothing on the screen, and it doesn’t accept any touch input, either. The phone still rings if there’s an incoming call. If this happens, the following several presses (about 10 - 20) on the power button will probably lead to a reboot. The “screen auto-rotate” and the proximity sensor may fail after the reboot, but will recover after a manual reboot.
Frequency: Fewer with higher Rom version. About once per day for 4.3.
Other description:
The problem frequently happens when I just take the phone outside my house/office, and seldom happens when the phone just stays somewhere.
The problem seems to be irrelevant to the remaining battery capacity or the uptime, but it never happens when charging.
The problem seems to be irrelevant to the Apps installed.
The problem seldom happens in the first 3-4 days after flashing a Rom, but happens more and more frequently as time goes by. My guess is some cache is stuffed by some trash, which causes the problem. The phone may be fine as long as the trash can be cleaned up on a regular basis.
I manually reboot my phone at most every two days.
Solutions tried, but don’t work
Flashing official ROMs 4.0.4, 4.1.1, 4.1.2, 4.2.2 and 4.3 following the procedure “adb reboot bootloader; fastboot oem unlock; flash-all; fastboot oem lock”, without google wallet, not rooted.
Turning off the auto-brightness control, as suggested by some post on the Internet.
Does it look like it goes to standby normally or does the screen show gibberish and then turns off?
Sent from my Galaxy Nexus using XDA Free mobile app
Thymo said:
Does it look like it goes to standby normally or does the screen show gibberish and then turns off?
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
Thank you very much.
I think it's standing-by normally even through the screen is black (or very dim, I cannot tell), since it rings if there's an incoming call. I can see nothing from the screen, and I don't think the screen accepts any touch input, either.
Does this answer your question? Thank you.
Bobby_yan said:
Thank you very much.
I think it's standing-by normally even through the screen is black (or very dim, I cannot tell), since it rings if there's an incoming call. I can see nothing from the screen, and I don't think the screen accepts any touch input, either.
Does this answer your question? Thank you.
Click to expand...
Click to collapse
Thanks.
Was just asking if you had gibberish yes or no. In that case i've got a different issue than you (Suspecting f*cked GPU).
Have you tried a different ROM/Kernel combination maybe it's related to that.
Thymo said:
Thanks.
Was just asking if you had gibberish yes or no. In that case i've got a different issue than you (Suspecting f*cked GPU).
Have you tried a different ROM/Kernel combination maybe it's related to that.
Click to expand...
Click to collapse
No.
No, I just tried the official ROMs. Any suggestion?
Perhaps it's just busy in the background and running low on RAM. Give LagFix a try. Sorry can't link atm as I am on mobile...
eKeith said:
Perhaps it's just busy in the background and running low on RAM. Give LagFix a try. Sorry can't link atm as I am on mobile...
Click to expand...
Click to collapse
Thanks a lot. I'm trying it.
Bobby_yan said:
Thanks a lot. I'm trying it.
Click to expand...
Click to collapse
LagFix does NOT help in my case. Any other suggestions? Thanks.
I've also had this blank screen with calls still ring issue for as long as I can remember, nearly 2.5 yrs.
I've always suspected it's my ROM and so I'd try out another ROM'S, BUT no other ROM works like how I'd like, so I always come back to my ROM.
It doesn't happen every single day, but it does happen very often.
I've tried using apps that auto reboot daily, but eventually this blank screen issue will return.
Unfortunately I can't seem to find any solution, so I just put up with it, it's like the 1 only flaw with my ROM.
&
Not to be at all rude, but I'm really glad op has had this issue from testing other versions of Android, cause then at least I know I don't need to give up my great tablet mode ROM.
LOL
I think I've finally found a work around for this screen of death.
Using Exposed, download/install this module/extension:
Disable Proximity
http://repo.xposed.info/module/com.mrchandler.disableprox
It does exactly what it's name is and ever since then I've not once had to remove my GN battery to work again because the screen went completely dead.
NVM
Screen still goes dead.
Anyone find an actual fix to this?
isajoo,
I had pretty much the same problems with my Galaxy Nexus running CyanogenMod 11 M12.
It got better by doing the following :
Blowing dry air in the earpiece… though the proximity sensor is clearly beside it. Can't do any harm though, I guess.
Settings/Applications/All/menu/Reset applications preferences (or whatever that's called in english) : that seemed to do a lot of good to my phone ! However, it's a very unsatisfactory answer on a technical point of view, as I still don't know WHAT was precisely needed. It's a "magic wand" solution for which I can't give an explanation.
Not specifically related, but greatly helped my phone in the responsiveness area : Trimmer (fstrim) (https://play.google.com/store/apps/details?id=com.fifthelement.trimmer), an updated version of LagFix that you may already know
Hope that helped !
(I wanted to try http://www.androidlegend.com/how-to-perform-proximity-sensor-calibration-on-any-samsung-phone/ as well, but apparently, /sys/class/sensors/proximity_sensor/prox_cal does not exist on my phone…)