Database Info

SK4G Software FLAWED!

What the hell is going on. I tried resetting and everything, even exchanged the device and the new one is doing the same thing! Also vibrating and force closing it is getting on my nerves! The followig seems to happen after a while I am TIRED of having to turn of my phone and turn it back on! ~ I go to play a .mp3 it says " FIle type not supported"...My .mp3 ringtone does not work the phone just vibrates the selected ringtone doesnt work. I got too take a picture or record video it says "Camera Failed"....I get a visual voicemail....the "play" button is grayed out and I have to turn off phone turn it BACK On just to check my voicemail. Also occassioally my sms wont work either. I turn my phone off and on every morning and throughout day I notice this and its getting REAL annoying !

Well first off, this isn't a software flaw, this is specific to you, as we have many users here including myself who are using these phones daily without the issues you are describing.
You had said that the issue was with an mp3, can you upload that somewhere for us to test on our phones?
As far as the camera and visual voicemail, I've never heard of that issue before, perhaps you ended up with a bad phone again?

I am getting the frequent force close with messaging. I also have had problems with the camera and idk about the mp3 stuff I haven't put any ringtones on the phone yet. This is getting really annoying I agree.

I don't have any issues with mine? Have you guys done anything like rooting or flashing anything?

Nope, completely stock. The most I have done is take a screen shot lol.

hmm maybe some have a defect? It's not all SK4g's though, as some of us have no issues at all. I would suggest getting it replaced by T-Mobile, as this is a factory defect. not sure why that happened to you guys. has anyone else had these issues and found any fixes?

That's kinda tough the hearest t-mobile is like 4 hours from here /:
One of my friends who went with me on the trip to get the SK also got one and he says he's never gotten a force close so you may be right. But could it have anything to do with the amount of texts I send/receive? Because I have to admit it is pretty excessive. The failing to send messages when I am receiving one simultaneously is expected, but not the force closes in my opinion.

It shouldn't force close on you. I know mine fails to send every once in a while too, as I text a lot (kinda the reason I got the phone). failing to send isn't as big of a deal, as it notifies you and you just have to click resend. Not entirely sure why it's force closing though? I wonder if a logcat might help? if you have adb installed, you can try adb logcat and see what shows up when you force close? if we can find the issue there, it might be fixable from our end. all depends on where the flaw lies/if it's just a bad apk somehow or if there's an actual hardware issue or something.

I'll do a log next time there is a fc, I'm having another issue or it may be related, but this one is with WidgetLocker I believe. Sometimes when I go to unlock the phone it'll freeze up and then I dont know how to explain it, but it almost seems like it resets but it really doesnt. The phone will blackout for a little then the homescreen will pop up and service will gone for a while until the cards are read just like if I rebooted.

That might be a function of WidgetLocker, I used it on my old G1 and it always hung and black screened at me.

sduvick said:
That might be a function of WidgetLocker, I used it on my old G1 and it always hung and black screened at me.
Click to expand...
Click to collapse
Yeah I know it does that from time to time, but on my previous phone it wouldn't do that reboot thing where it would lose connection then resend my latest text messages once it reconnected.

I'm not sure why it's doing that. My guess would be that the issues are caused because the SK4G doesn't use a normal lock screen. widgetlocker uses some modification of the system file for the lock screen, and perhaps it's not sure what to modify? just my 2 cents.

sduvick said:
I'm not sure why it's doing that. My guess would be that the issues are caused because the SK4G doesn't use a normal lock screen. widgetlocker uses some modification of the system file for the lock screen, and perhaps it's not sure what to modify? just my 2 cents.
Click to expand...
Click to collapse
That's what I was thinking too, I'm gonna uninstall it for a bit and see if anything changes.

is anyone else having an issue with notification volume? everytime i reboot my SK, my notification volume gets pushed all the way down to nothing, so i don't get a sound notification for texts, emails, etc, until i move the notif. volume back up in my settings. i did root with the one-click for the Epic 4G.

This is a new UI so alot of the apps i.e. widgets you may put on will cause issues. If you like certain apps contact the dev so your device is supported correctly. Still to new to get mad at it till sum of the bugs get worked out. I did notice a couple of times when I left screen on in pocket on accident that when I go to use it again it doesn't respond to any touch but can move courser around till rebooted then its ok. If some don't already know the sk4g is almost the same as the epic. The sk4g is still a badass phone for 100bucks.

Same as the OP
I know this is a little old, but I've experienced the same problem as the OP so it seems they are not alone with this problem.
I actually tried two different newly formatted SD cards (because I thought it may have been the SD card), and still would have the problem. Then I actually did swap phones about a month ago and it seemed the problem would now take several days to resurface instead of several hours. And I could deal with that.
Since the OTA update about 2 weeks ago, the phone has been back on it's original BS as the OP posted and it's driving me nuts. I actually missed some emergency calls last night because the mp3 ringtone didn't work so I'm finding a solution to this issue today or trashing this phone.
My belief is that there is something interfering with the phone's ability to read the SD card for media. Because other apps I have that save to the SD card or read from it work fine. So I'm going to master reset it and not download any of my apps and see what happens when I set an mp3 ringtone. If it makes it through the day with no hiccups, I'll slowly add back one app at a time until hopefully I can find the culprit.
bipoler if you'd like, we can exchange via PM what apps we both have downloaded and see if we have some in common that may be problems.
I'll post back with any progress.

I've been having the problem with ringtones not working, just getting silence when I get a call. for me it seems to happen when I set a ringtone from the app Zedge, I don't think it happens when I use ringtones from the Android System, which would make sense if the issue is related to reading the sdcard. gonna go back to a system ringtone and see what happens today.

Yeah my phone had all those problems, but I installed the Lightning rom and all those problems went away, except for the ones about messages failing...I text A LOT

Lightning ROM
Thanks for that info on the Lightning Rom. I will check that out. Phone has been working flawlessly all day with the mp3 ringtone and no extra apps besides the master reset. I might give it until the morning before I start putting them back on.

On stock id install so many apps that ran on the background that id get delay from opening closing swiping and turning onthe phone.. so I wiped it installed a custom rom and just kept the essentials.. havnt had a problem since... well.. occasionly ill have to odi but that's on purpose
Sent from my SK4G

[Q] CM7 Notifications go silent

Hi everyone, I was just wondering if anyone else has had a problem with notifications going silent on CM7?
I searched and found a couple of threads about the issue, but no fix or workaround was mentioned.
I had the problem before on my EVO as well, so I wonder if it's an app I'm installing. The only constant between the 2 phones was CM7. I have tried updating to the nightlies and it still occurs.
Basically, I boot up my phone. Get a message or email notification and all is working well. I then go about my day and notice I have a few more messages but no sound was made. Now notifications will remain silent until I reboot once more, and the cycle starts all over again. Sometimes they work longer, sometimes I get 1 notification and all others are silent again.
What I've tried:
I tried messing with a profile to see if that was causing issues. No go...
I have tried switching to Oxygen which worked great but I had to switch back to CM7 because MMS did not work for me at all on that rom. MIUI also worked well but I have some contacts I like sending directly to VM and their DND did not allow that, just silent ring and answer/hangup, so back I go to CM...
Can anyone help me out?
Thanks so much!

I did notice the same thing on my Nexus S 4G! I was running CM7, as well. And a reboot seemed to fix it.
Never solved what caused it, but it didn't happen often enough to where it was a big concern of mine.

Yea a reboot fixes it for me too, but then it will happen again. I wonder why that is. Maybe it's something I'm doing?

Did you guys ever find a solution for this aside from rebooting? This has happened to my samsung infuse (running on infused 1.5) a few times already and it is pretty frustrating. I believe it's happened a few times on the stock rom as well. I've tried uninstalling programs one by one to see if I can find the culprit, but no dice. It just doesn't happen consistently enough for me to pinpoint the app or problem. Thanks in advance!

[Q] Incomming Calls Hanging?

Hey there. I got a bit of a problem with my Nexus S, which I've had since January. I didn't notice it much at first, but now it's worse than ever. When someone calls and I push the button to pick it up, the buttons disappears, as if it takes it, but it keeps ringing. Then sometimes, after about 5 seconds, it still takes it. Problem is that most of the time when it does this, I can't hear the person in the other end, but they can still hear me. This is only a problem on incoming calls, not outgoing.
The reason why I ask for help now, is that I noticed when installing a SDK build of ICS, I didn't have this problem, everything was all right. But today, when installing a AOSP build, it starts doing this again.
This problem persists across wipes, and different radio images.
My belief is that there must be some system files in the SDK builds that fixes this problem.
If anyone has a suggestion on how to fix this, other than me digging through system files and trying to replace random files and see if it works, please tell!
Regards, Adam Honoré.

If you feel like you need a better explanation, Please tell.
I can upload a video demonstrating it.

Gonna bump this with new info.
I forgot to mention that after calls, when I press the hangup button, it just stays there for about 10 seconds before hanging up.

[Q] Popping after any sound (P5100, CM10.1)

Hello,
my tablet is producing a very loud "pop" noise when speaker turns off (ie. after any sound). Galaxy Nexus seemed to have the same (hardware) issue, but I believe that mine is caused by software, as it started after I flashed CyanogenMod 10.1 (latest nightly). I'm running following setup right now:
DhollmenCM (but I flashed cyanogenmod over it, not sure if it's still here)
CyanogenMod 10.1 latest nightly
GApps for CM 10.1
Before installing CM everything worked well (but the original ROM is **** and I need profiles). How am I supposed to fix this?

I've had that before as well. Do you by chance have any audio enhancing software installed besides DSP Manager? Programs like Volume+ are notorious for this.

DSP Manager has everything disabled, nothing else is installed.

First I would try to remove DSP just to see if that's the problem.
Here is a simple app that I use to remove apps that the ROM's have in them that I don't want. I usually do it after I flash because I don't feel like opening the ROM on the computer and removing them ahead of time.
https://www.dropbox.com/sh/u4wijb1zwzdd3pn/4TyYtOpd1x
If removing DSP doesn't solve your issue and you didn't have this problem previously, I would reflash wiping "everything" before flash, including data. Since at that point there would be no way to be certain what is causing it. I don't believe the kernel could be the problem as I am running CM10.1 and the Dhollmen kernel as well and don't have any issues.

I have reflashed everything many times - with no effect. After removal of DSP there's no difference too.

pzduniak said:
I have reflashed everything many times - with no effect. After removal of DSP there's no difference too.
Click to expand...
Click to collapse
But did you wipe the system before flashing?
This is critical to make sure you have a clean installation, without it there are pieces that get left behind and cause all sorts of issues. If you have wiped, then it sounds like you have developed a hardware issue. Did it get dropped any time recently?

pzduniak,
I don't know if you're still having this problem, but I ran into this problem too. It was driving me nuts. It started happening when I was playing Pixel Dungeons.. then crept to my alarm and popped every time sounds played. I tried the DSPManager thing to no avail, but I tried this and so far have not heard any popping. I'm still testing, but I went into system>build.prop (I'm on a Sprint Galaxy S3, so just find build.prop on your device). In build.prop (make sure you're rooted so you can make changes), change the line that says lpa.decode=true to false. reboot and try that out. I researched very little about lpa.decode, but I remember having a problem in stock with battery drain and lpa.decode.. I dont know if it's true at all but give that a shot and let me know if the pops go away!
Good luck!

mtran2988 said:
pzduniak,
I don't know if you're still having this problem, but I ran into this problem too. It was driving me nuts. It started happening when I was playing Pixel Dungeons.. then crept to my alarm and popped every time sounds played. I tried the DSPManager thing to no avail, but I tried this and so far have not heard any popping. I'm still testing, but I went into system>build.prop (I'm on a Sprint Galaxy S3, so just find build.prop on your device). In build.prop (make sure you're rooted so you can make changes), change the line that says lpa.decode=true to false. reboot and try that out. I researched very little about lpa.decode, but I remember having a problem in stock with battery drain and lpa.decode.. I dont know if it's true at all but give that a shot and let me know if the pops go away!
Good luck!
Click to expand...
Click to collapse
I had been having this popping problem for a while now, and Google brought me here. I went ahead and changed the lpa.decode to false like you suggested and it worked like a charm! Thanks mtran2988!

[Q] Hearing small glitchy sounds when pressing screen (no special pattern)

Hi there
First some specs:
Nexus 4
PA3.99-RC2
Franco.kernel.plus 188.
SuperSU root
Latest gapps
I have tried asking in the the Paranoid Android Google+ discussion forum, but no useful answers yet. This is x-posted in N4 forum as well, but I thought asking here in general could give give answers from people with other devices too.
The problem:
When I use my phone I get random glitchy/clicky sounds from the top speaker (I'm pretty sure it's from there). It's a very quick glitch/click, and then it stops. It doesn't happen in a specific pattern, meaning that it's not like it comes whenever I press the back button or anything - it just happens sometimes. Sometimes more often than other. When I try to recreate the sounds (tapping a lot of menus, settings, apps, etc.) I find it difficult to recreate. It is REALLY random, perhaps mostly after I haven't used my phone for a while, and I turn it on!
Have anyone tried this, and knows a solution? It didn't annoy me at first, but now it really does.
As far as I remember it started when I upgraded to PA3.99. However, I have tried RC-1 and RC-2 and I have also tried stock kernel, Hellscore kernel and different Franco-kernel versions.