Related
I have three tablets. Not that I owe.. one is mine, another is my sister's, and last one is my cousin's. All tablets are on VEGA-n beta 5.1. My sister's tablet is doing some unexpected things. For starters whenever it is put to sleep it shuts down instead(not right away but after a min or two it shuts down). Second, both mine and hers are on the same network, but when hers gets 10 or more feet away from the wifi source it drops connection while mine still gets excellent connection. Third while on the same network, on hers only certain apps can access the internet while others cannot. Market was working earlier(downloaded Ti backup after reflash) but her Internet Explorer was not working. Now internet explorer works but market does not, even other internet explorers other than the stock one are unable to connect online. Lastly her accelerometer stopped working/was stuck. I reflashed and wiped all data, but nothing. Its still broken.
Should I return it? I have tried all the solutions that fixed some of these problems for me but they don't seem to work on hers. Any help please?!
Wow, its great to see that you all kept the G Tablet in the family.
1. Its an issue many of us have. We feel its software related since it started to occur after flashing the Vegan Rom.
2. Could be a hardware issue for your sister's device. Back it up, wipe it and try it on the fresh install and see how it reacts. If it works fine, then its probably something software related. If it still drops, then its more likely hardware. Return it.
3. Again, faulty installation of the Rom. Back it up, wipe it, and try installing it again. Also you may want to try TNT to see if its Vegan 5.1 related (btw, it doesnt use internet explorer)
4. I would return it if these issues persist.
Hope this helps. Anyone with other advice please chime in.
Thanks,
Scott
For the powering off issue, it sounds like the button might be sticking, on mine it forces the tab off if i hold it down for even a few seconds.
Also by internet explorer, i assume you mean the android browser?
Also is your cousins tab experiencing any of the same problems?
Mine and my cousin's are alright. Only problem I've had is flash crashing occasionally and rebooting. I might try flashing TnT lite on hers and see if there's a difference.
I have to head to work will update once I work on hers more. And thanks for replying..
necromonger89 said:
Mine and my cousin's are alright. Only problem I've had is flash crashing occasionally and rebooting. I might try flashing TnT lite on hers and see if there's a difference.
I have to head to work will update once I work on hers more. And thanks for replying..
Click to expand...
Click to collapse
I have been running vegaN Beta5.1 for a while now. Used to have similar issues with power and such. I flashed Clemson 10.9.3 kernel, it is now up to 10.9.8 and the power issues went away. It also has the lag fix, and some other nice fixes. It installs just like any other rom.
Here is the link: http://forum.xda-developers.com/showthread.php?t=895825
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
Hi folks
I have a Nexus S (i9020a). It has stock 4.1.2 Jelly bean from Google (downloaded the stock image and flashed it). It worked fine for over a month.
Suddenly few days back this device got a problem. When I dial any number I can't hear any dialing sounds and even after the call has connected I can't hear the opposite person and the opposite person also can't hear me (The phone still shows as 'Dialing' though it's already connected). The same is true when I answer any call. Both parties can't hear anything.
This is solved by rebooting the phone for the first phone call only. After I reboot, the 1st phone call works fine, then this problem persists for any calls I make/receive until I reboot the phone again.
I tried flashing a different radio but this problem is still there. I tried my sim card on a different phone and it works fine, so the problem is not that too. My 3G data works just fine.
I need this phone for the next few days/weeks (hopefully not months) before my Nexus 4 gets delivered :laugh:
Thanks..
Edit: Modified the title; Probably gave the wrong meaning that the problem is solved.
<bump> Modified the title. Earlier title gave an impression that the problem is solved whereas I still have a problem.
Have you installed any apps which could somehow affect the dialler?
Unless someone else can give you a different advice, I can't think of any other option than do a full wipe and reflash.
I haven't installed any such apps.
Also, I already did a full wipe and flashed the stock image again. The problem is still there.
Don't know what else you could try, sorry mate - hope someone else can help you sort it out!
Thanks for trying. I think I will go to some hardware shop and see if they can figure out..
Try using a headset for making phone calls so that we can identify if it's really the hardware's problem.
ej8989 said:
Try using a headset for making phone calls so that we can identify if it's really the hardware's problem.
Click to expand...
Click to collapse
That's the first thing that I tried... doesnt work.
mailrachit said:
That's the first thing that I tried... doesnt work.
Click to expand...
Click to collapse
I had similar problem when RAM running out. Usually a reboot fix the problem for a bit.
What I did:
1. With Titanium Backup Pro, froze unused RAM hogging system apps, like Google+, Google play magazine,etc
2. Froze or uninstall Facebook, Word with Friends, etc which are resident and hog RAMs .
3. Install marmite kernel, free up more usable RAMs.
Hope it helps you too.
_android_ said:
I had similar problem when RAM running out. Usually a reboot fix the problem for a bit.
What I did:
1. With Titanium Backup Pro, froze unused RAM hogging system apps, like Google+, Google play magazine,etc
2. Froze or uninstall Facebook, Word with Friends, etc which are resident and hog RAMs .
3. Install marmite kernel, free up more usable RAMs.
Hope it helps you too.
Click to expand...
Click to collapse
Thanks for the suggestion!
I tried this too but doesn't work...
Try any custom ROM instead of stock ROM and a different kernel too. There could be chances that you've flashed the wrong ROM / radio too.
Sent from my Nexus S
Problem solved.
I went to a hardware store today. The guy said that it's a problem with the 3G service of my carrier (Vodafone India). The moment I enabled the '2G only' option in the Mobile networks settings area, this problem was gone. The technician said that this issue is affecting some people randomly. He said that since 3G service was launched just last year, the networks are not yet capable of handling all kinds of devices (he claims that the bug is so erratic that another Nexus S i9020a may work just fine with the very same bootloader/radio/rom which doesn't make any sense). When I said that 3G service was working fine before, he said that most probably my carrier changed some settings on their side which is causing this issue for me.
I have tried this for 6-8 hours now, making a lot of phone calls and it seems that the issue is gone. It saddens me that I am off 3G for now but at least my phone calls and basic EDGE internet works fine. I will have to work with Vodafone to solve this or simply wait for my new phone (Nexus 4) and hope it won't have the same problem..
Hi All,
I'm having same issue on 5.0.1 and on 5.1 as well.
I figured the update on 5.1 will fix this issue but it persists. I will restart and its ok for some time. After few hours when I try to take photos, it says "cant connect to camera". I did the cache clear trick doesnt help. I dont think its a hardware problem cause it works for some time rhen it shws the error. Is it possible to be a conflict with Viber app or something like this??? I'm just guessing but I really need your help as it very annoying. ALso the Music app sometimes doesnt play thefiles.
Tbh, I'm getting more and more dissapointed with every update.
Note that I'm on stock rom never rooted....
Thanks!
raperot said:
Hi All,
I'm having same issue on 5.0.1 and on 5.1 as well.
I figured the update on 5.1 will fix this issue but it persists. I will restart and its ok for some time. After few hours when I try to take photos, it says "cant connect to camera". I did the cache clear trick doesnt help. I dont think its a hardware problem cause it works for some time rhen it shws the error. Is it possible to be a conflict with Viber app or something like this??? I'm just guessing but I really need your help as it very annoying. ALso the Music app sometimes doesnt play thefiles.
Tbh, I'm getting more and more dissapointed with every update.
Note that I'm on stock rom never rooted....
Thanks!
Click to expand...
Click to collapse
Try turning off the face unlock option
I believe its turned off. I've tried everything but doesnt solve the issue. Its very annoying, I can't use the camera most of the time
This haunted me also. No one helped. I needed the camera as my wife is 8000 miles away . A hard reset works. I switched to Lite ROM and it's never happened again. It's stock and small
Sent from my Nexus 5
Any fixes? It keeps crashing and reboot doesn't fix it.
Open "Beta" build. Expect bugs. Also there's a reason this build is pulled back by OnePlus. Downgrade to OB11. Everything seems fine to me on OB11.
No issues here on OB12
silvercat said:
No issues here on OB12
Click to expand...
Click to collapse
Click pair new device. I'm getting crashes on 9.0. 3 official.
Batfink33 said:
Click pair new device. I'm getting crashes on 9.0. 3 official.
Click to expand...
Click to collapse
Same problem for me. It happens every time I update the ROM, beta or not, I have to do a clean install each time ...
Anyone has fix this Bluetooth issue in ob12?
So it's still not fixed in ob14
Has this issue just yesterday in OB14. Sudden freeze and reboot. After that Bluetooth settings crash, no lock screen and theming worked buggy. Took a backup and clean flashed. No problems so far
Hello,
I had the same crash with stable 9.04 approx one week after upgrading from 9.0.3.
Suddenly, entering bluetooth made settings app force close.
I couldn't find any solution and ended up to factory reset the phone...
elmarian756 said:
Has this issue just yesterday in OB14. Sudden freeze and reboot. After that Bluetooth settings crash, no lock screen and theming worked buggy. Took a backup and clean flashed. No problems so far
Click to expand...
Click to collapse
This happens for me every two weeks... I don't know at all why it happens. I'm thinking it could be caused by the navbar gestures, SwiftKey, cf.lumen or maybe kinscreen. Do you use one of these?
I went back to 9.0.4 because of that and it still happens.
sylvn said:
This happens for me every two weeks... I don't know at all why it happens. I'm thinking it could be caused by the navbar gestures, SwiftKey, cf.lumen or maybe kinscreen. Do you use one of these?
I went back to 9.0.4 because of that and it still happens.
Click to expand...
Click to collapse
Sorry but i use none of these. In my case the rom starts to collapse itself after a few updates dirty flashed. Some system apps not showing on ocasional boots, some sudden soft reboots and then lockscreen not showing at all, theming bugs, and Bluetooth crash. I take backup using oneplus switch and titanium and fresh install open beta, restoring all doesnt take more than 20 minutes.
My bluetooth setting crash, i couldn't connect any new devices. so i searched for solution in this forum. im on OOS 9.0.4. just before i take the plunge wipe data clean install rom, i tried the following.
I first cleared Setting App cache and data, didn't work.
then i gone into recovery and cleared Dalvik cache, didn't work.
then i used Clean Master and cleared system cache, 3gb worth, and bluetooth setting worked again!
hope this helps someone in the future.
Hello guys, i just noticed that bluetooth settings crashing ,everything was working fine for me (as long as i remember), but yesterday i was trying to pair a BT controller and it happened. So let me explain, turning on and off bt affects nothing, but when it's on and you try to go to the settings by long tap on quick settings or by the settings it crashes. when it's off you can go to the settings but once you try to pair a new device it crashes, old paired devices pair when you turn on the BT so it happens only when you try to pair a new device.
I tried to go to the 9.0.6 but it was crashing there too, so i rolled back to OB19.
I'm rooted, magisk 19.2 and twrp and with stock or smurf kernel it crashes , so i ended up pairing the controller with a third party app.
I'm sure it was working before because i paired alot of devices. I tried some "fixes" like freezing the bttestmode or clearing the cache and data of the bluetooth but none of those fixed the issue. So did anyone find a solution.
Thank you
For everyone having BT crashes, try looking at your phone Bluetooth name and check if it's blank. Usually happens to me when fsync fails and I lose my ram data.
Dzemper said:
For everyone having BT crashes, try looking at your phone Bluetooth name and check if it's blank. Usually happens to me when fsync fails and I lose my ram data.
Click to expand...
Click to collapse
You just came out of nowhere, thank you it worked when i found that there was no device name in the About Section, changed it and now it works.
Dzemper said:
For everyone having BT crashes, try looking at your phone Bluetooth name and check if it's blank. Usually happens to me when fsync fails and I lose my ram data.
Click to expand...
Click to collapse
True hero right there. Thanks man !
Dzemper said:
For everyone having BT crashes, try looking at your phone Bluetooth name and check if it's blank. Usually happens to me when fsync fails and I lose my ram data.
Click to expand...
Click to collapse
You are freaking Jesus Christ sir, whole day searching around and I was about to give up and clean flash.
Dzemper said:
For everyone having BT crashes, try looking at your phone Bluetooth name and check if it's blank. Usually happens to me when fsync fails and I lose my ram data.
Click to expand...
Click to collapse
Many Thanx