Related
Hi everyone,
I bought a Samsung galaxy s last week from an eBay auction. The phone was described as touch screen lag. I was thinking that flashing a new firmware will solve the problem. I got really cheap though
The touch screen stops suddenly in every 5/6 minutes and I have to lock the screen using power key and unlock again to make it working.
when I got the phone:
Non Samsung battery and chargers were used, I changed and using original ones.
Stock XXJVS firmware in it.
First I flashed stock 2.2.1 froyo and test the screen using *#0*# code. it got pass. But when I start using it, the problem was still there.
Then I flashed stock GB, same story, now slim ics, same thing.
Please someone help me, there is nothing I can do with it now.
I search few threads related to screen problem but couldn't find one with similar problem. So asking here.
mregmi121 said:
Hi everyone,
I bought a Samsung galaxy s last week from an eBay auction. The phone was described as touch screen lag. I was thinking that flashing a new firmware will solve the problem. I got really cheap though
The touch screen stops suddenly in every 5/6 minutes and I have to lock the screen using power key and unlock again to make it working.
when I got the phone:
Non Samsung battery and chargers were used, I changed and using original ones.
Stock XXJVS firmware in it.
First I flashed stock 2.2.1 froyo and test the screen using *#0#* code. it got pass. But when I start using it, the problem was still there.
Then I flashed stock GB, same story, now slim ics, same thing.
Please someone help me, there is nothing I can do with it now.
I search few threads related to screen problem but couldn't find one with similar problem. So asking here.
Click to expand...
Click to collapse
Sounds like a hardware problem to me..but it's really hard to say if it is. But it would definitely seem like it since it isn't ROM related. Maybe a water damage or faulty digitizer?
Sent from my GT-I9000 using Tapatalk 2
This happens to me sometimes very rarely though, it will be weird and hard to touch but speaking to someone with the same phone they said they had this problem to all I do to resolve the problem is lock and unlock the screen, I thought this was normal?
Sent from my GT-I9000 running remICS-UX using XDA premium
It shouldn't be normal. I am using another galaxy s for almost two years. But never had this problem in such extent, little bit lag on touchscreen when on froyo. But never after. Now with slim ics Temple run is more smooth then iphone 4.
Sent from my Galaxy S using xda premium
Kurre said:
Sounds like a hardware problem to me..but it's really hard to say if it is. But it would definitely seem like it since it isn't ROM related. Maybe a water damage or faulty digitizer?
Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for reply. When I got it first time, it was really annoying, the problem was so frequent that it was almost unusable. Now in new rom, after unlocking the screen it works little longer then before. Works like a charm when it works. So not sure this is hardware problem.
Sent from my Galaxy S using xda premium
I don't think this is a hardware or problem either, I broke the screen and replaced it and I still have the same thing when though it is very rare, so if it was the screen it should of gone after I installed the new one, btw I installed a whole new pre built front so the bevil and LCD, and my phone has never hib water damaged? Maybe its something to do with the bootloader? As that doesn't change through ROM flashes
Sent from my GT-I9000 running remICS-UX using XDA premium
mregmi121 said:
Please someone help me, there is nothing I can do with it now.
I search few threads related to screen problem but couldn't find one with similar problem. So asking here.
Click to expand...
Click to collapse
try using a LCD modder LCD density modder https://play.google.com/store/apps/details?id=com.birdapi.android.dpi&feature=search_result
@xsenman;
I did that couple of times going through Advance slim setting. That didn't change anything. Now I'll try this as well.
I change touchscreen into chainfire sensitive option in semaphore app. Still lagging.
Tried over clocking to 1200 but it freezes and automatically reboots into recovery mode. I can use only after changing to default
Sent from my GT-I9000 using xda premium
Guys its really annoying now. Its behaving strangely. I played with it few hours and found out that the screen near the home button freezes first. I cant press the dock but still pull the notification bar? then stops working whole screen. I checked the show touches in developers options setting. Sometimes it works randomly actually without touching it , I just place my finger near the screen but didn't touch and on few occasion it works opposite direction, like I scrolled down but it gone up:crying:
Is this the sensor issue? Is there any way to fix? Any idea please?
mregmi121 said:
Guys its really annoying now. Its behaving strangely. I played with it few hours and found out that the screen near the home button freezes first. I cant press the dock but still pull the notification bar? then stops working whole screen. I checked the show touches in developers options setting. Sometimes it works randomly actually without touching it , I just place my finger near the screen but didn't touch and on few occasion it works opposite direction, like I scrolled down but it gone up:crying:
Is this the sensor issue? Is there any way to fix? Any idea please?
Click to expand...
Click to collapse
try this tool to verify where the problem is , if its hardware, you have no choice but to take it to a technician
https://play.google.com/store/apps/details?id=com.gombosdev.displaytester&feature=search_result
and this
https://play.google.com/store/apps/details?id=com.vital.tst.n7000&feature=search_result
https://play.google.com/store/apps/details?id=zausan.zdevicetest&feature=search_result
xsenman said:
try this tool to verify where the problem is , if its hardware, you have no choice but to take it to a technician
https://play.google.com/store/apps/details?id=com.gombosdev.displaytester&feature=search_result
and this
https://play.google.com/store/apps/details?id=com.vital.tst.n7000&feature=search_result
https://play.google.com/store/apps/details?id=zausan.zdevicetest&feature=search_result
Click to expand...
Click to collapse
Screen+digitizer panel can be changed by yourself. For it, you just need couple of tools and little nerves
Instructions can be found from YouTube, this forum and many other places..
Sent from my GT-I9000 using Tapatalk 2
Kurre said:
Screen+digitizer panel can be changed by yourself. For it, you just need couple of tools and little nerves
Instructions can be found from YouTube, this forum and many other places..
Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse
I tried all of those apps, nothing wrong. I think I should change the screen and digitizer, I might need to go to the repair center because my hands shake (my usual problem) and hard to fix tiny things. I want to do few experiments before taking it to repair. I already put it in the freezer for two hours it was acting like crazy after.
Suggest me more...
Sent from my GT-I9000 using xda premium
Me too!
and i thought i'm the only one experiencing this kind of problem. it is exactly what i'm having on my sgs. seems to be temporarily fixed by turning the screen off and then on again, but after a while, the screen doesn't respond on the same spot as you're having.
i've managed a low level debug on screen touch response using adb logcat, and my touch doesn't really register any on adb logcat console.
they might be correct on the hardware problem, but when i'm on any gingerbread rom (2.3.6), the problem is gone.
guys, any idea what kind of drivers they're using on gingerbread for our touchscreen?
I have this too on ics, left half of screen stops responding, lock on/off sorts it....until the next time! Bugs the hell out of me!
Me too! on ICS
btw, i'm already on ics team nyx
change
flash CF KERNEL and put ICS CM9
middle screen not responding
- when in stock gb firmware (official from samsung), the touchscreen problem is gone.
- but i want the features of an ics rom, so i flashed one (first was slim ics); the problem appeared first; first guess was the custom rom was still in its early stages.
- flashed back to gb, no touchscreen problem.
- flashed new ics rom from cm9 (nightlies), problem appears again (ugh!).
- flashed backed to updated slim ics since this was the fastest and easiest to install, touchscreen problem still persist.
- found a temporary fix by turning the screen off then on again.
did a adb logcat full trace log of touchscreen input: what i noticed was the whole vertical middle part of the screen is not responding to touch; dragging touch from one side to middle is working just fine, but not starting from the mid vertical part.
the problem may sometimes go away after a while, and sometimes persist even after the temp fix. it's very intermittent indeed.
help please.
psycotrompus said:
- when in stock gb firmware (official from samsung), the touchscreen problem is gone.
- but i want the features of an ics rom, so i flashed one (first was slim ics); the problem appeared first; first guess was the custom rom was still in its early stages.
- flashed back to gb, no touchscreen problem.
- flashed new ics rom from cm9 (nightlies), problem appears again (ugh!).
- flashed backed to updated slim ics since this was the fastest and easiest to install, touchscreen problem still persist.
- found a temporary fix by turning the screen off then on again.
did a adb logcat full trace log of touchscreen input: what i noticed was the whole vertical middle part of the screen is not responding to touch; dragging touch from one side to middle is working just fine, but not starting from the mid vertical part.
the problem may sometimes go away after a while, and sometimes persist even after the temp fix. it's very intermittent indeed.
help please.
Click to expand...
Click to collapse
So your sgs touchscreen working fine on stock gb rom! It might not be a hardware problem then. We have similar problem, only difference is I have problem on GB too. I've even tried stock froyo, same story
Sent from my Nexus S using xda premium
same problem here, left part of the screen would be unresponsive at times
can fix by locking the phone through power button and unlocking it, thats why i think its a software problem.
I dont remember having this problem in GB also.
maybe something is messed up during flash?
I have the same problem with ics and jb roms from the onecosmic ics times and i had a topic http://forum.xda-developers.com/showthread.php?t=1648287
I have written here but no one seems to now what it is, i have been using ics from onecosmics first release and had the problem from that moment on, different kernels, roms etc it is still here i have flashed gb again and problem is gone, flash again with ics the middle part still acts sometimes. ?...
We should request from kernel developers and rom developers to look into it. I have tried almost everything no luck so far
When I want to turn on the display (by pressing the power button), sometimes he is not turn on. Touch keys shine, but screen not (black screen). To avoid this problem, i press power button again to turn off, and again to turn on. I am not alone with this issue.
It is a bit annoying. How resolve this problem?
Was observed in the following ROMs:
stock ICS ROM http://forum.xda-developers.com/showthread.php?p=28992763
Android Revolution HD 3.0.0
Reborn ROM
UKB X
and more...(list will be added)
p.s. If you have this issue too, write the name of the ROM.
Rude_Dollah said:
When I want to turn on the display (by pressing the power button), sometimes he is not turn on. Touch keys shine, but screen not (black screen). To avoid this problem, i press power button again to turn off, and again to turn on. I am not alone with this issue.
It is a bit annoying. How resolve this problem?
Was observed in the following ROMs:
stock ICS ROM http://forum.xda-developers.com/showthread.php?p=28992763
Android Revolution HD 3.0.0
Reborn ROM
and more...(list will be added)
So, in my opinion, the problem may be in the kernel or some application. But this is only speculation.
Need experts, to help out the problem.
p.s. If you have this issue too, write the name of the ROM and list of applications.
Click to expand...
Click to collapse
seems like its sense roms for you man. try icecold or something
Rude_Dollah said:
Was observed in the following ROMs:
stock ICS ROM http://forum.xda-developers.com/showthread.php?p=28992763
Android Revolution HD 3.0.0
Reborn ROM
and more...(list will be added)
So, in my opinion, the problem may be in the kernel or some application. But this is only speculation.
Need experts, to help out the problem.
p.s. If you have this issue too, write the name of the ROM and list of applications.
Click to expand...
Click to collapse
Please add UKB X to the list. FYI, I never have this issue in IceColdSandwich or PlayGround.
Yeah this problem is quite irritating on the stock Rom. I think it'd called a wake lock.
Sent from my HTC Incredible S using xda app-developers app
Just want to report that apart from pushing the power button, I also experienced the issue when alarms go off and calls come in. So it definitely has nothing to do with the physical button.
Strange, I haven't faced this problem on ARHD and now i m using ICECOLD Sandwich
Me neither. I've used Icecold, Playgorund, Rebirth, Virtuous VIVO and finally ARHD 3.0.0. and never faced such issue
Just tried the latest Virtuous Infinity alpha without installing any additional apps and I do experience the "turn on" issue once. So it's pretty clear now the problem is either related to hardware (less likely) or kernel, at least to me. Could be a combination of both, of course.
@vladabiber, I never had this issue before when using IceColdSandwich nor Playground too.
Since there's no problem in AOKP ROMs, I'm pretty sure it's not a hardware issue Could likely be sth with kernel but I'm not sure...
So, problem still not resolved?
Anyone have a solution?
Rude_Dollah said:
So, problem still not resolved?
Anyone have a solution?
Click to expand...
Click to collapse
I just switched from UKB X to Virtuous Infinity but the problem still happen from time to time.
itandy said:
I just switched from UKB X to Virtuous Infinity but the problem still happen from time to time.
Click to expand...
Click to collapse
I think the problem in Sense. Is there any way to tell HTC about this bug?
And how about factory reset?
Rude_Dollah said:
I think the problem in Sense. Is there any way to tell HTC about this bug?
And how about factory reset?
Click to expand...
Click to collapse
You can always report it to HTC through their customer service. But my experience tells me their CS can only tell you nothing more than resetting your phone.
Anyone been checking logcat to see if the phone recognizes its not turning on? Probably too many processes running which is causing display lag. Try plugging phone into charger, check stay awake and try turning on the screen as it may be timing out before it has a chance to turn on.
Nonverbose said:
Anyone been checking logcat to see if the phone recognizes its not turning on? Probably too many processes running which is causing display lag. Try plugging phone into charger, check stay awake and try turning on the screen as it may be timing out before it has a chance to turn on.
Click to expand...
Click to collapse
Unlikely, because if quickly push power button, screen turn on normal.
Has anyone tried doing a hard reset, I know it's foolishly, but anyway?
Yes same here. issue occurred after the stock ICS update.:crying:
Rude_Dollah said:
Has anyone tried doing a hard reset, I know it's foolishly, but anyway?
Click to expand...
Click to collapse
Yep I tried.....
Didn't work......
Someone needs to report the bug directly to HTC's inc s dev team...
Sent from my HTC Incredible S using xda app-developers app
abhijay.jagini said:
Yep I tried.....
Didn't work......
Someone needs to report the bug directly to HTC's inc s dev team...
Sent from my HTC Incredible S using xda app-developers app
Click to expand...
Click to collapse
How can I do report the bug directly to HTC's inc s dev team?
I tried to write in customer support, but they are advised only hard reset
I think, i found a solution. This problem called "deep sleep", solution is increase the frequency when phone in sleep mode with SetCPU.
Now testing in process. Detailed instructions will come later.
So I followed the steps here
http://wiki.cyanogenmod.org/wiki/Samsung_Galaxy_Tab_(CDMA):_Full_Update_Guide
and these.
http://forum.xda-developers.com/showthread.php?t=1585619
After I rebooted after using the Heimdall app, my touchscreen was acting up, so instead of sliding to unlock, it would sort of move the slider on the right. I had to swipe downward inorder to unlock and the touchscreen was just wonky.
I am trying to install Cyanogen mod using the latest stable version offered on get.cm . it sort of keeps rebooting while installing, to a cyanogenmod splash screen. Although it's not centered and I can only see a few letters. It keeps doing back to something about checking the state of bml/mtd. and now its just in that off centered splash screen. Wtf is going on?
I have the SPH-P100 version and it had gingerbread.
Hgaara said:
So I followed the steps here
http://wiki.cyanogenmod.org/wiki/Samsung_Galaxy_Tab_(CDMA):_Full_Update_Guide
and these.
http://forum.xda-developers.com/showthread.php?t=1585619
After I rebooted after using the Heimdall app, my touchscreen was acting up, so instead of sliding to unlock, it would sort of move the slider on the right. I had to swipe downward inorder to unlock and the touchscreen was just wonky.
I am trying to install Cyanogen mod using the latest stable version offered on get.cm . it sort of keeps rebooting while installing, to a cyanogenmod splash screen. Although it's not centered and I can only see a few letters. It keeps doing back to something about checking the state of bml/mtd. and now its just in that off centered splash screen. Wtf is going on?
I have the SPH-P100 version and it had gingerbread.
Click to expand...
Click to collapse
I feel for you! I had the exact same problem with my SPH-P100 yesterday. I have been running CM10 nightlies for the last month with no problem until the p1c 1121 rom. It bootlooped on me, and would not even go to CWM, so I used the 2nd option (Holy Crap), which I've used quite a few times. I had the same problems you did (slider and rebooting). I just kept reinstalling it till it worked. I'd get the CM9stable on ok (same things as you were getting, so I reran it a couple of times in a row). Then I would try to put CM10 on and it would say the partition was wrong. I was getting very PO'd there for a while. It probably took about 8-10 hours till I was able to get it back, but the CM10 is worth it.
I managed to get it running by mounting the system. Is CM10 nightly stable enough to use as a daily ROM? I'm not planning on connecting it to the Sprint network so it'll be just a wifi tablet
Sent from my SCH-I800 using xda app-developers app
I dont use the Sprint network on mine either. I love the CM10! It is pretty smooth running. I have been using the nightly CM10 roms for a month, and they get better every day. The problem I had might have just been my tab not responding correctly. I know a lot of devices have had stable CM10 roms come out in the last 2 weeks, so hopefully ours will soon!
Please mention if you are using GSM or CDMA.
gogol1996 said:
Please mention if you are using GSM or CDMA.
Click to expand...
Click to collapse
Hgaara said:
I have the SPH-P100 version and it had gingerbread.
Click to expand...
Click to collapse
OP said that.
Sent from my GT-I9300 using xda app-developers app
Hi I have been using the "captivating xperia 4.2.2 rom from sepphi for about 3 weeks and I first must say great work.
I just noticed today my camera has stopped working. Everytime i try to start the camera i get the error message" unfortanalty, the gallary has stopped" . Could anyone Tell me how to correct this? thanks in advance .
Update: I went ahead and ordered me another phone because i use the camera on my phone often, while waiting for the new phone to
arrive I thought I would give a complete erase and full install of 4.2.1 captivating one last try and what did it do but worked! LOL
It was like the 3rd or 4th try doing it the same way each time. Anyway just thought I would give the good news and thanks for everyone's help.:good: Since I have already ordered me a new phone I have this phone still listed on swappa.com for sale. see me sig for the link.
js380 said:
Hi I have been using the "captivating xperia 4.2.2 rom from sepphi for about 3 weeks and I first must say great work.
I just noticed today my camera has stopped working. Everytime i try to start the camera i get the error message" unfortanalty, the gallary has stopped" . Could anyone Tell me how to correct this? thanks in advance .
Click to expand...
Click to collapse
I get that sometimes on CyanogenMod 10.1. What I do is go to Settings>Applications, find the Gallery app, then press "Clear Data." That usually fixes the Gallery app until the next CM 10.1 update.
falcon7204 said:
I get that sometimes on CyanogenMod 10.1. What I do is go to Settings>Applications, find the Gallery app, then press "Clear Data." That usually fixes the Gallery app until the next CM 10.1 update.
Click to expand...
Click to collapse
I tried deleting the data in the app but still no luck on the camera.
It was working great but then stated giving me this error when trying to open up
the camera app only, I can view the gallery photos still though.
UPDATE: I finally decided to try a full / clean install of another rom but still no luck.
The camera app will start but the shutter graphic never opens up and i hear a "click" sound
then I get the error message. Anyone have any advice? thanks
js380 said:
UPDATE: I finally decided to try a full / clean install of another rom but still no luck.
The camera app will start but the shutter graphic never opens up and i hear a "click" sound
then I get the error message. Anyone have any advice? thanks
Click to expand...
Click to collapse
Are your Apps/Gapps up to date?
Did you install or uninstall any apps within those weeks that had effect on camera/gallery?
js380 said:
Hi I have been using the "captivating xperia 4.2.2 rom from sepphi for about 3 weeks and I first must say great work.
I just noticed today my camera has stopped working. Everytime i try to start the camera i get the error message" unfortanalty, the gallary has stopped" . Could anyone Tell me how to correct this? thanks in advance .
Click to expand...
Click to collapse
I got this error when I turned on the big mem setting without first going into the camera and changing the video quality to 480 instead of 720.....also if big mem setting is on, sometimes even after flashing a new rom big mem is still on.
Im not getting any updates needed via notifications or goo manager. I did a fresh complete delete n install of aocp 5 and hellybean lastest roms and still cant get the camera to work, very odd I must say. That being said Im totally lost on this one. I havent changed any of the memory settings that im aware of.Is it possible the camera has become defective for no reason or is it probably a software issue?
js380 said:
Im not getting any updates needed via notifications or goo manager. I did a fresh complete delete n install of aocp 5 and hellybean lastest roms and still cant get the camera to work, very odd I must say. That being said Im totally lost on this one. I havent changed any of the memory settings that im aware of.Is it possible the camera has become defective for no reason or is it probably a software issue?
Click to expand...
Click to collapse
I'd say to try going back to stock KK4 at this point, test your camera, it it works, work your way back up to the ROM you wanna use. If it doesn't, it's probably hardware.
Re: [Q] Camera just stopped working (capitivating 4.2.2)
I'm not having any luck, is there a way to confirm if it's hardware or software related?
Sent from my SGH-I897 using xda app-developers app
Re: [Q] Camera just stopped working (capitivating 4.2.2)
js380 said:
I'm not having any luck, is there a way to confirm if it's hardware or software related?
Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
I'm not so sure. Although, there might be a app for it.
When on stock, did you try it barebone? (Without restoring your apps)
Sent from my SGH-I747 using xda app-developers app
Re: [Q] Camera just stopped working (capitivating 4.2.2)
No I wasn't sure how to do that, I restored the backup. Is there a way to install a barebone stock Rom on my phone? Sorry for all the questions Im no expert by any means and just wanna find out if it's hardware or not.Any and all tips / advice are greatly appreciated.
Sent from my SGH-I897 using xda app-developers app
js380 said:
No I wasn't sure how to do that, I restored the backup. Is there a way to install a barebone stock Rom on my phone? Sorry for all the questions Im no expert by any means and just wanna find out if it's hardware or not.Any and all tips / advice are greatly appreciated.
Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
Was your phone already on 2.3 when you got it?? Otherwise, you should have Odin KK4 with bootloaders already.
Either way, here it is: http://hotfile.com/dl/137871658/d25...O_Bootloaders_Re-partition_Full_Wipe.zip.html
You'll need Corn kernel afterwards to get back on the ROM you want to use: http://forum.xda-developers.com/showpost.php?p=26710533&postcount=1
Re: [Q] Camera just stopped working (capitivating 4.2.2)
I GUESS ITS HARDWARE related, I tried all advice n still no luck. I mute the phone and when I try to start the camera It shows the camera app start(but the lens never opens on screen) but I still hear a "click" sound and then the app force closes with the error message. I have went back to the captivating 4.2.2 Rom by sephhi (my favorite for the cappy by far)and will just use the phone as is until I hear of a fix in the future. I will keep monitoring this thread if anyone finds a fix please advise asap. Thanks for everyones help.
Sent from my SGH-I897 using xda app-developers app
js380 said:
I GUESS ITS HARDWARE related, I tried all advice n still no luck. I mute the phone and when I try to start the camera It shows the camera app start(but the lens never opens on screen) but I still hear a "click" sound and then the app force closes with the error message. I have went back to the captivating 4.2.2 Rom by sephhi (my favorite for the cappy by far)and will just use the phone as is until I hear of a fix in the future. I will keep monitoring this thread if anyone finds a fix please advise asap. Thanks for everyones help.
Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
Your reply isn't very clear. Did you go back to stock KK4 and try it and that gave you the black screen? If so, yes it is hardware related and we can't fix it for you, you'll need to have it repaired. (mobiletechvideos.com might be able to)
BWolf56 said:
Your reply isn't very clear. Did you go back to stock KK4 and try it and that gave you the black screen? If so, yes it is hardware related and we can't fix it for you, you'll need to have it repaired. (mobiletechvideos.com might be able to)
Click to expand...
Click to collapse
Sorry , I have tried all suggestions and had no luck. when i say the screen goes black i meant in the camera app it goes black/grey
as it normally should but the camera doesn't open it up to show the video on screen because it crashes.
js380 said:
Sorry , I have tried all suggestions and had no luck. when i say the screen goes black i meant in the camera app it goes black/grey
as it normally should but the camera doesn't open it up to show the video on screen because it crashes.
Click to expand...
Click to collapse
Might wanna look into getting in repaired then.
BWolf56 said:
Might wanna look into getting in repaired then.
Click to expand...
Click to collapse
I guess I'll just use it as is without a camera for now , I think fixing it would cost more than I wanna pay at this time.
Anyone know how much cash I could get out of this phone if I sold it with captivating rom 4.2.2 installed on it without the camera working?
I may just sale it and purchase a new phone. Thanks:good:
js380 said:
I guess I'll just use it as is without a camera for now , I think fixing it would cost more than I wanna pay at this time.
Anyone know how much cash I could get out of this phone if I sold it with captivating rom 4.2.2 installed on it without the camera working?
I may just sale it and purchase a new phone. Thanks:good:
Click to expand...
Click to collapse
Having a custom on it won't make it more valuable. Most people like to get them clean.
Also, they were around 60$ last time I checked, I dunno now.
If you're looking to sell, PM me
Re: [Q] Camera just stopped working (capitivating 4.2.2)
I wasn't saying because it has 4.2.2 its valued more. Just was wondering the value of the phone and was stating the current Rom(and by far the best IMO) installed on it. I just recently purchased this phone GSM Network unlocked for $160.00 locally. Thanks for everyones help:thumbup:
I will take $110.00 for the phone and take a loss. I'm not techy/smart enough to attempt to repair the camera myself LOL, if anyone is interested PM me.
Sent from my SGH-I897 using xda app-developers app
Hi everyone!
I have a strange problem with my Droid 4: sometimes it stops playing sounds (or music, or ringtones), and I can't figure out if there's something in particular that triggers this. Anyway the only fix I could find is rebooting the phone.
There's another problem though: when this happens, if I try to use the phone app or the contacts app, the app itself hangs before I can do anything. If I kill the hanged app and retry a few times, the phone reboots itself.
Any idea on what could be causing this? What could I try to diagnose the problem?
I'm using a Verizon-branded Droid 4 with CM10.1.3, but I had the problem on 10.1.2 too. If it's relevant, I had to install "Tobby's mod" to enable GSM (I'm in Europe)
Many thanks for your attention!
This is the only and the known problem with droid4 on cm10.1 cm10.2 but I have a very good experience with the latest nightlies using buildprop editor to change only the telephony.lteOnCdmaDevice=0. Don't use the patch and se if it helps for you.
Sent from my XT894 using xda app-developers app
I have that property "zeroed" already, do you mean I should try reverting Tobby's mod?
Try the latest nightlies, there are some changes regarding to apns, it's updatable from cm10.1 and make only that change don't apply any patch.
Sent from my XT894 using xda app-developers app
Joril said:
Hi everyone!
I have a strange problem with my Droid 4: sometimes it stops playing sounds (or music, or ringtones), and I can't figure out if there's something in particular that triggers this. Anyway the only fix I could find is rebooting the phone.
There's another problem though: when this happens, if I try to use the phone app or the contacts app, the app itself hangs before I can do anything. If I kill the hanged app and retry a few times, the phone reboots itself.
Any idea on what could be causing this? What could I try to diagnose the problem?
I'm using a Verizon-branded Droid 4 with CM10.1.3, but I had the problem on 10.1.2 too. If it's relevant, I had to install "Tobby's mod" to enable GSM (I'm in Europe)
Many thanks for your attention!
Click to expand...
Click to collapse
I've seen this on stock, and I think it's related to bluetooth - perhaps it's not releasing the audio properly after a device disconnects?
There's an app in the Play Store called "Earpiece", and I can use that to bring the audio back when that happens by switching it on, and then switching it off again.
HTH.
Steve.
I don't use bluetooth at all, but I'll try Earpiece, thanks
the problem is that it will crash before you realize and you will loose the next call, so I don't think it is of some use.
I tried latest nightly and safestrap 3.65 (from 3.63) and I had lots of black screens, several on one day and then I realize that before, I had it working stable on cm10.1 when I found out that noop was the problem, cfq and deadline was ok (after speaking with hashcode it made the default to cfq) but it was on safestrap 3.11, but then newer versions of safestrap appeared and I updated it and from time to time it started to go bad again.
I reverted back to 3.11 and I have it working ok since 17.11.2013 (almost 2 days of stable, finger crossed)
I would ask hascode if safestrap can be a problem, but now he has retired in supporting the d4, of course this can be applied to razr
Regards
lucize said:
I reverted back to 3.11 and I have it working ok since 17.11.2013 (almost 2 days of stable, finger crossed)
Click to expand...
Click to collapse
How is it going?
For me is very good, tried 4.4, now back on cm10.2 nightlies, so
Ss3.11 and only the lteoncdma change, everything else is working fine except tha battery that is shorter than moto default
Regards.
Sent from my XT894 using xda app-developers app
lucize said:
For me is very good, tried 4.4, now back on cm10.2 nightlies, so
Ss3.11 and only the lteoncdma change, everything else is working fine except tha battery that is shorter than moto default
Click to expand...
Click to collapse
Ok, now I'm on a 10.2 nightly, with just the lteoncdma fix... Let's see how it goes
It took a while to connect to the GSM network, did this happen to you too? (The signal strength icon even changed to a question mark at one point)
I first have no sim, then no signal then I get full bars
Sent from my XT894 using xda app-developers app
I had it working nicely for 6 full days, but this morning sound went out again Better than before, but still...
I'm on the 28/11 10.2 nightly, I'll try updating again this evening
Joril said:
I had it working nicely for 6 full days, but this morning sound went out again Better than before, but still...
I'm on the 28/11 10.2 nightly, I'll try updating again this evening
Click to expand...
Click to collapse
I'm on kitkat, I think that I had it too with 28, try 27 or other, maybe stable, anyway is better than 1 or 2 days
Regards
Definitely better, yes So you're using CM11? Any problems?
Joril said:
Definitely better, yes So you're using CM11? Any problems?
Click to expand...
Click to collapse
the 05 fromm stargo is not so ok, the previous was stable, or at least I didn't had problems.
I'll try the 07, I have problems with deep sleep and I don't know why, because for now wakelocks can't be accessed on 4.4, then again is not a new install, is an upgrade from 10.2
the strange thing is that now I have another error in catlog when it goes out of sound compared to the error when it is on the gsm patch, maybe I'll try a test without changing build.prop at all, in the end it doesn't matter if the signal icon is wrong as long as it's stable.
Regards
Hey! Joril! I posted in your other thread, on another forum, about this same topic, but I figure that I'd get comfy here, since the Droid 4 "scene" has seemingly migrated from DroidForums to this website.
Anyway, I haven't been able to fix the problem. In fact, at one point, when the audio died, I went through the typical steps - I turned off Bluetooth, and reset the phone. However, when the phone was "coming back", so to speak, an "Android is upgrading" box popped up. Odd, I thought, since I didn't do anything different. Anyway, it gets through this, and... I get an UID error. Something about the UID being inconsistent with the system, and that the data partition was terribly unstable.
So, my phone was freaking out. Great. I was missing several apps, and the whole device is incredibly unstable - apps are crashing, left and right, as well as background services. It is at this point that I decide to bite the bullet and restore my phone to stock settings.
I do so. I use the Droid 4 Utility, restore the stock ROM, getting rid of Safestrap 3.11 in the process. Everything's back to normal. Stabilized. I commence to rooting the phone, installing the latest version of Safestrap, and installing CyanogenMod 10.1.3. I get it running, and... the problems remain. I still have the same audio issues. MMS is still iffy. GPS is a hit-or-miss process; every once in a while, if the planets align, a system reboot will "fix" GPS.
Anyway, that's my story. I've been doing some research - or, rather, a lot of research - and it seems to me that the audio problem was, perhaps, fixed in the latest CyanogenMod 11 build. Something about the previous code not playing well with the "Audio HAL", whatever that is, and the Audio HAL issue being consistent with other phones with the same processor, I believe - or something to do with an "MSM8660". I believe that "MSM8660" is a Snapdragon processor, but I could be wrong!
To make a long story short: CyanogenMod 10.1.3 seems to be stuck with the audio/crashing issue, but CyanogenMod 11 may fix it. I'm not ready to make the jump to CyanogenMod 11, though, not until it is FULLY stabilized and out of Experimental/Alpha/Nightly status. In that regard, I wonder how open Stargo, Hashcode, or another coder would be to patching up 10.1.3 with the GPS/MMS fixes that have been seen in the later builds? I don't know how to code, but it should be relatively simple to patch the few crippling bugs remaining on 10.1.3, using code from future builds and versions.
Jishkah said:
CyanogenMod 10.1.3 seems to be stuck with the audio/crashing issue, but CyanogenMod 11 may fix it. I'm not ready to make the jump to CyanogenMod 11, though, not until it is FULLY stabilized and out of Experimental/Alpha/Nightly status. In that regard, I wonder how open Stargo, Hashcode, or another coder would be to patching up 10.1.3 with the GPS/MMS fixes that have been seen in the later builds?
Click to expand...
Click to collapse
Right now I'm on a CM10.2 nightly and the audio issue appears a bit less than when on 10.1, I'd say once every 5/6 days instead of once every other day... Anyway I'd like to wait a bit more before trying CM11 too
CM11 has this issue also, but the error will not be the same if the build.prop has only lteoncdma modified, for me, if I apply the full gsm patch the error will appear more often and catlog will show the cpu pegged error.
the problem with CM11 (for me) is no deep sleep, the sound issue is not so important anymore