Related
My fellow Canadians...
I have noticed a number of issues with the latest official firmware for the Rogers captivate. I think it would be a good idea to put them all in one place and try to start figuring out what common issues exist and perhaps we can address them all at once. Please state the issue, when it seems to happen, and what if any modifications you have made to your software setup. Maybe someone will notice a pattern or trend and we can get them resolved.
Thanks!
Reserved +10 char
One major issue I have noticed is when updating apps through the 3.1.5 market. It seems to only happen when I am updating an app, not when I am installing a new app:
Sorry!
The application TwLauncher(process com.sec.android.app.twlauncher) has stopped unexpectedly. Please try again.
At which point I have to force close it.
Also, I have experienced random shut downs, I will click the power/screen lock button to unlock the phone, and it seems the phone has shut itself off. If you hold down the power button it boots normally.
Anyone else experiencing these issues?
clemmie said:
One major issue I have noticed is when updating apps through the 3.1.5 market. It seems to only happen when I am updating an app, not when I am installing a new app:
Sorry!
The application TwLauncher(process com.sec.android.app.twlauncher) has stopped unexpectedly. Please try again.
At which point I have to force close it.
Also, I have experienced random shut downs, I will click the power/screen lock button to unlock the phone, and it seems the phone has shut itself off. If you hold down the power button it boots normally.
Anyone else experiencing these issues?
Click to expand...
Click to collapse
Did you try a factory reset after you updated?
Voice for Swype
The voice command for Swype doesn't work.......
1. Speed dial no longer works. Says 'USSD code running' then closes and gives message 'unknown application'
2. GPS has stopped working completely.
As far as the launcher crashes, I don't use touchwiz. I do use Launcher Pro. It does seem to crash every so often. I've replaced all my widgets because I've read somewhere that this might help.
No random shutdowns here.
I talked to a samsung technical support rep and his captivate's swype voice input didn't work either.
iam_immigrant said:
1. Speed dial no longer works. Says 'USSD code running' then closes and gives message 'unknown application'
2. GPS has stopped working completely.
Click to expand...
Click to collapse
GPS works perfectly on mine captivate 2.3.3 and I get better reception and locking time. But GPS will stop working if you flashed a custom Kernel on it! I know that because I tried it and GPS wasn't working when I had a custom Kernel, had to flash back the stock kernel.
Edit: I just tried Speed dial and it's working perfectly, I think there is something wrong on your phone.
Nick0703 said:
GPS works perfectly on mine captivate 2.3.3 and I get better reception and locking time. But GPS will stop working if you flashed a custom Kernel on it! I know that because I tried it and GPS wasn't working when I had a custom Kernel, had to flash back the stock kernel.
Edit: I just tried Speed dial and it's working perfectly, I think there is something wrong on your phone.
Click to expand...
Click to collapse
I also don't have any issues with the GPS or Speed Dial. My only mod was rooting with the FUGU kernel.
erbsmokah said:
Did you try a factory reset after you updated?
Click to expand...
Click to collapse
I hadn't thought of that; I wonder if I'll lose my root? Come to think of it, I wonder if that's causing the launcher crashes...
Nick0703 said:
GPS works perfectly on mine captivate 2.3.3 and I get better reception and locking time. But GPS will stop working if you flashed a custom Kernel on it! I know that because I tried it and GPS wasn't working when I had a custom Kernel, had to flash back the stock kernel.
Edit: I just tried Speed dial and it's working perfectly, I think there is something wrong on your phone.
Click to expand...
Click to collapse
Got the phone from Rogers with 2.1 then upgraded to 2.2 then to 2.3.3 (all done through Kies. GPS was ok but spotty on 2.1 and much better with Froyo but hoped Gingerbread would bring more improvement.
I've tested it since Rogers released 2.3.3 and on a few occasions I've even gone to the roof of my building on a clear day and waited for 45mins!! and nothing! Not lock then lose it but NOTHING! Speed dial I can live without but I actually use the GPS quite a bit.
Since upgrading I've done a factory reset 4 times and even sent it in for repair, which came back saying "upgraded SW and factory reset" which fixed nothing.
I've just rooted (just root nothing else) and I've tried to do use the gps code but I can't even get into that!!
What can I do at this point?
iam_immigrant said:
Got the phone from Rogers with 2.1 then upgraded to 2.2 then to 2.3.3 (all done through Kies. GPS was ok but spotty on 2.1 and much better with Froyo but hoped Gingerbread would bring more improvement.
I've tested it since Rogers released 2.3.3 and on a few occasions I've even gone to the roof of my building on a clear day and waited for 45mins!! and nothing! Not lock then lose it but NOTHING! Speed dial I can live without but I actually use the GPS quite a bit.
Since upgrading I've done a factory reset 4 times and even sent it in for repair, which came back saying "upgraded SW and factory reset" which fixed nothing.
I've just rooted (just root nothing else) and I've tried to do use the gps code but I can't even get into that!!
What can I do at this point?
Click to expand...
Click to collapse
Yeah, with the 2.3.3 you can't access the gps setting by entering the code, because everything you enter the code *#*#3214789650#*#*, you'll get a message saying "Service mode has crashes blablaba...". The only that I found to bypass that was to go to market and install the app "Anycut" then launch it, select New Shortcut, Activity then choose Angry gps.
I'll look up what's the problem that causing you not to get a good gps signal.
Sent from my SGH-I896 using XDA App
Nick0703 said:
Yeah, with the 2.3.3 you can't access the gps setting by entering the code, because everything you enter the code *#*#3214789650#*#*, you'll get a message saying "Service mode has crashes blablaba...". The only that I found to bypass that was to go to market and install the app "Anycut" then launch it, select New Shortcut, Activity then choose Angry gps.
I'll look up what's the problem that causing you not to get a good gps signal.
Sent from my SGH-I896 using XDA App
Click to expand...
Click to collapse
Man I was going nuts trying that gps code. Googled and searched this forum and everything pointed to that code. Was ready to toss my phone off the roof!
Was reading these forums for the past couple weeks learning how to root/flash (just rooted today actually) to get gps working.
I'm guessing I might have to try flashing it again with the stock rom from this thread http://forum.xda-developers.com/showthread.php?t=979133 but gotta do some more reading before attempting it.
iam_immigrant said:
Man I was going nuts trying that gps code. Googled and searched this forum and everything pointed to that code. Was ready to toss my phone off the roof!
Was reading these forums for the past couple weeks learning how to root/flash (just rooted today actually) to get gps working.
I'm guessing I might have to try flashing it again with the stock rom from this thread http://forum.xda-developers.com/showthread.php?t=979133 but gotta do some more reading before attempting it.
Click to expand...
Click to collapse
I use an app called GPS Status from the market. There, in the menu under 'tools', you can 'manage A-GPS state and wipe the location info the GPS has back to scratch. Then download the assistance data from the internet. This worked well for me and I do it from time to time to keep things current.
Sent from my SGH-I896 using XDA App
clemmie said:
One major issue I have noticed is when updating apps through the 3.1.5 market. It seems to only happen when I am updating an app, not when I am installing a new app:
Sorry!
The application TwLauncher(process com.sec.android.app.twlauncher) has stopped unexpectedly. Please try again.
At which point I have to force close it.
Also, I have experienced random shut downs, I will click the power/screen lock button to unlock the phone, and it seems the phone has shut itself off. If you hold down the power button it boots normally.
Anyone else experiencing these issues?
Click to expand...
Click to collapse
How long have you had the phone? The random shut downs is not a ROM issue. I am pretty sure it is a hardware problem. It was acknowledged by Samsung. There is even a list of effected builds. I am sure you could find the build numbers with a little search. I had this problem when I first got the phone last December but had Rogers replace it. If it is the same problem, I think you will notice that the sleep of death only occurs when the battery is like above 85% or somthing like that. It has been a while so I can't exactly remember.
I can't seem to get the firmware actually downloaded. I'm going through kies and it recognizes my phone, and recognizes that I need to upgrade, starts downloading the upgrade and at 12% it disconnects. I have two screen shots here that show what I am talking about.
Any ideas?
clemmie said:
I use an app called GPS Status from the market. There, in the menu under 'tools', you can 'manage A-GPS state and wipe the location info the GPS has back to scratch. Then download the assistance data from the internet. This worked well for me and I do it from time to time to keep things current.
Sent from my SGH-I896 using XDA App
Click to expand...
Click to collapse
Tried this the entire day and still nothing. I know it's kinda cloudy out today but still nothing.
i found 2.3.3 very slow, and poorly built. no voice button in swype PEEVED me off.i was originally making my custom canadian rom off Kh2 (rogers 2.3.3) but i dropped that project and released a canadianized/rogersized KJ3 (2.3.5).
one of the best roms in the dev section. and will be updated by the end of the week with the theming all included. the pic in my sig is a link to the rom if you havent seen EFFIN EH!
Unable to update my Captivate
My captivate is still 2.2 and while connecting to Kies it says this version of the device cannot be updated.
Current version shows PDA: JL1/phone: JL1/CSC: JL1 (xxx).
I had rooted via Super one click and I can see Superuser installed. I havent used it for any purpose.
I removed my external SD card and did factory reset. No luck.
nambisan said:
My captivate is still 2.2 and while connecting to Kies it says this version of the device cannot be updated.
Current version shows PDA: JL1/phone: JL1/CSC: JL1 (xxx).
I had rooted via Super one click and I can see Superuser installed. I havent used it for any purpose.
I removed my external SD card and did factory reset. No luck.
Click to expand...
Click to collapse
flash to stock 2.3.3 using the link in my signature. YOU NEED BOOTLOADERS coming from 2.2
I can't figure this out to save my life.
WiFi calling simply doesn't work. When I try to open the app on any ROM I get an immediate FC.
I've tried the wifi calling patches. I've tried fresh ROM installs. I've tried all the kernels. I've tried reinstalling the WiFi calling apk. (Though I don't think I properly got rid of the old one first, so that might be it)
The patches REALLY don't work. When I flash those the phone boot loops forever.
It's not that the wifi calling app opens then simply doesn't work right. It won't even open. It certainly acts like a problem with the app itself, rather than than the phone's ability to properly utilize the app...but I'm just guessing.
Any thoughts?
I'm very open to proper steps to completely remove wifi calling so I can do a proper reinstall instead of just trying to install over the existing version, which is what I think I've done.
I did recently upgrade to the updated firmware, in case that's a known cause.
I can't imaging the radio has much to do with it since wifi works fine in general, just not for calling.
The goal is to get it working right on CM7 for right now.
And if this is like a REALLY noob problem that I'm missing an insanely obvious answer on.....then you get double thanks for dealing with me.
Well first off do you have the tmobile cid and the right mid? If you don't have either it won't show on first boot for tmobile sensation
I have SuperCID 11111111
Does that louse it up?
I have no idea what my Mid is
Skipjacks said:
I have SuperCID 11111111
Does that louse it up?
I have no idea what my Mid is
Click to expand...
Click to collapse
Yeah that my, as for mid look for a thread called or similar to guide to fix wifi calling
Okay...still working on this.
I put my CID back to a stock T Mobile one.
My MID is PM581000
So that's all normal. I can see the app icon just fine. It just doesn't run.
The force close error says com.android.kineto has stopped.
What could be making the process stop?
Bumping this to see if anyone has thoughts on this.
As with the Exynos-based counterparts, call recording is disabled in our ICS build. I believe this problem has been solved in those, but is it fixable here without kernel source?
Call recording is somewhat critical for my job, and while I do have an external wired call recorder set up, it's pretty patchy and inconvenient.
Probably can't be done without kernel source, which we may not see for awhile. joemeister and others are making progress on am aosp kernel made from scratch, but this also is still alpha
This call recorder from the market works without issue and I have tested and verified this it works both ways and only requires root. Try it for yourself and you'll see it works well. https://play.google.com/store/apps/details?id=com.skvalex.callrecorder&hl=en
vatipa said:
This call recorder from the market works without issue and I have tested and verified this it works both ways and only requires root. Try it for yourself and you'll see it works well. https://play.google.com/store/apps/details?id=com.skvalex.callrecorder&hl=en
Click to expand...
Click to collapse
Ugh. I installed a trial version of this I got from another thread here and the expiration was set to before I installed it so it never did anything.
Even worse, it made the app show up as "purchased" in the market, but since I didn't really purchase it, it won't download and I get a 403 error.
confirmed worked for me as well.
That's good to know. I'll figure something out then, maybe contact Google or the developer.
Hello,
Acouple days ago my GPS decided to stop working. I can no longer get a GPS fix on my phone, even if Maps says it has a fix its not accurate. (shows me driving on 3-4 roads over from where I actually am)
I have tried tightening the screws as outlined here to NO effect. http://forum.xda-developers.com/showthread.php?t=2201668
And the fix listed here
And finally manually editing the GPS.CONF file to include more specific NTP servers for the US, after that didnt work I tried an APP called FasterGPS that did more of less the same thing I did. My GPS did work for a short period after using FasterGPS but now has returned to not working at all.
Running Stock ICS with SuperUser\Root
Build 4.0.4 VRALF2
Would really appreciate some help.
nuke235 said:
Hello,
Acouple days ago my GPS decided to stop working. I can no longer get a GPS fix on my phone, even if Maps says it has a fix its not accurate. (shows me driving on 3-4 roads over from where I actually am)
I have tried tightening the screws as outlined here to NO effect. http://forum.xda-developers.com/showthread.php?t=2201668
And the fix listed here
And finally manually editing the GPS.CONF file to include more specific NTP servers for the US, after that didnt work I tried an APP called FasterGPS that did more of less the same thing I did. My GPS did work for a short period after using FasterGPS but now has returned to not working at all.
Running Stock ICS with SuperUser\Root
Build 4.0.4 VRALF2
Would really appreciate some help.
Click to expand...
Click to collapse
Maybe something software related got messed up. I noticed that you are on Build 4.0.4 VRALF2. That is quite a few versions from the latest. Maybe factory resetting and updating to the latest version out would help?
Watanuki-Kun said:
Maybe something software related got messed up. I noticed that you are on Build 4.0.4 VRALF2. That is quite a few versions from the latest. Maybe factory resetting and updating to the latest version out would help?
Click to expand...
Click to collapse
That was my next step.
However Ive been thinking of just flashing CM10.1 for awhile now so I might just do that.
Just want to see if I can get this resolved without the need to reflash.
If my phone is on for more than 10 minutes, I lose calling functionality. When I try to call someone, it freezes and the Pixel becomes unresponsive, forcing me to hold down power for 10 seconds for a reboot. After this, it works just fine for another 10 or so minutes.
I have no idea when calling functionality begins to be lost because I can still send and receive texts, but I can't make or receive calls. I don't even get a wave of missed calls or anything when it works after a reboot.
Google Assistant has it's own issues when this happens too. It won't come up with "Hey, Google" at all. When I long press the home button, Google Assistant comes up, but I just get the floating dots. Fortunately, it doesn't freeze when I try this. Restart the phone and I'm good for about 10 minutes or so. I tried installing 3rd party calling apps, but the problem persists.
Hoping this is a Pie issue and waiting for the next security patch, will likely do a sideload flash-all. Any suggestions as to what the problem is from? Could my SIM card be the problem? Any apps I could try to help narrow down the issue? I had no issues with Oreo.
Thanks in advance.
Tried rebooting in safe mode. Slightly similar results: works fine for about 10 minutes but then it's just the mic not working. I can make and receive calls with out the phone freezing, but no mic.
mbstone said:
If my phone is on for more than 10 minutes, I lose calling functionality. When I try to call someone, it freezes and the Pixel becomes unresponsive, forcing me to hold down power for 10 seconds for a reboot. After this, it works just fine for another 10 or so minutes.
Click to expand...
Click to collapse
I have a similar issue with a used Pixel I purchased. I couldn't place or receive calls, with everything else working fine. Did the prerequisite online searches with results finding most everyone experiencing this issue chalking it up to hardware but I'm still thinking software. I tried a different phone app (drupe-enabled as default) with some success, then the problem returned (a few days later, rarely get/make calls). The default google phone app (version 23.0) fails every time. Currently looking into TWRP/Root and hoping to eliminate certain default apps to experiment further. Will be keeping an eye on this post! :cyclops:
--- Three weeks later ---
Could there be an issue within google play services with phone dialer app (any/or stock app)?
After continued issues I parked phone in drawer a bit then pulled out and tinkered with a few weeks later. Tried to isolate problem using logcat and on a hunch I flashed TWRP and a custom ROM but NOT any gapps package. Sticking sim in and using the built in phone app (Resurrection Remix -com.android.dialer) it works without issue. What? I flashed gapps (correct version/etc) and sure enough the problem returned. Went back to rom minus gapps, works fine. So, with straight up stock rom - stock phone dialer fails, custom rom - it works without a gapps package but not with.
Aimless Rambler said:
I have a similar issue with a used Pixel I purchased. I couldn't place or receive calls, everything else working fine. Did the prerequisite online searches with results finding most everyone experiencing this issue chalking it up to hardware but I'm still thinking software. I tried a different phone app (drupe-enabled as default) with some success, then the problem returned (about 5 days later). The default google phone app (version 23.0) fails every time. Currently looking into TWRP/Root and hoping to eliminate certain default apps to experiment further. Will be keeping an eye on this post! :cyclops:
Click to expand...
Click to collapse
Went back to Oreo before I had the problems and... problems persist. I'm sad. I had the privilege of speaking to someone from Google Support who was very knowledgeable. Unfortunately, my best option from the rep was to take it in to one of their authorized repair places.
Are you guys on Verizon? I'm having this problem with my dad's pixel on vzw.
brkshr said:
Are you guys on Verizon? I'm having this problem with my dad's pixel on vzw.
Click to expand...
Click to collapse
AT&T
---------- Post added at 07:47 AM ---------- Previous post was at 07:45 AM ----------
mbstone said:
Went back to Oreo before I had the problems and... problems persist. I'm sad. I had the privilege of speaking to someone from Google Support who was very knowledgeable. Unfortunately, my best option from the rep was to take it in to one of their authorized repair places.
Click to expand...
Click to collapse
--- Three weeks later ---
Could there be an issue within google play services with phone dialer app (any/or stock app)?
See my updated post (# 3) for what I've tried since..
Vzw ended up replacing my dad's phone through extended warranty. I talked to Google for awhile. Multiple factory resets, factory image installs, tried older phone apks. Nothing worked.
brkshr said:
Vzw ended up replacing my dad's phone through extended warranty. I talked to Google for awhile. Multiple factory resets, factory image installs, tried older phone apks. Nothing worked.
Click to expand...
Click to collapse
Older/newer phone dialer apps didn't work for me either ... custom rom and eliminating google play services did (no gapps). I'm still tinkering with the device ... installing frequently used apps using F-droid and Yalp, will test it. Not quite sure why but it works.
I ended up flashing Lineageos for Microg, presents it's own problems in the learning experience but it works.
Nothing ever worked in the end. No, not with Verizon. Bought through Canadian carrier called Fido.
Called Google tech and they weren't overly helpful. I started a chat with a Google Tech and they suggested I take it to UBreakIFix. They did a free diagnostic test and I referenced https://support.google.com/pixelphone/forum/AAAAb4-OgUsIW_gxTpXX3s/?hl=by that thread. Said they'd fix it for free even thought I was out of warranty. Got a new motherboard and my phone works like a charm.