I own a Samsung Fascinate and I have been flashing customs for a few months now. I've tried 5 or 6 different combinations and every time I flash to something other than stock, i have weird occurrences. For instance, right now I am running super clean 2.9.2 eb01 w/ voodoo and crysis theme for eb01. I flashed it yesterday and when I flashed it, I tested all of the features (text in/out, web, calls in/out, camera, bluetooth etc.) and everything worked fine. This morning I woke up to a couple of missed calls and usually I wake up with text messages from different people too, but I had none whatsoever. Also, when I flashed it yesterday, I had a 3G symbol for my web and a stable connection. I wake up this morning and the 3G has turned into a "1x" (whatever that means) and the mobile data connection seems slower than ever. In fact it is slow. I play a cool MMORPG built for androids called Pocket Legends and when I logged in this morning my ping was extremely higher than usual. The only thing that I am completely worried about are texts/calls not coming in and my mobile data connection being slow. And this same thing has happened with a few other roms/kernels I've used. The weird thing is that as soon as I flash back to stock, all the features work fine again.
My main questions are, when I first flash something, why does everything work properly for a while after I first load it, but then a few days down the road I start having problems? Is that even possible? Can a custom rom/kernel/theme change your phone whenever it wants to? I know alot of customs are unstable and usually the OP lists what's working and not working, so I've made careful choices with the ones I've picked. This has happened with all of the customs I've had for eclair and even froyo. But why do they only work properly for like a day and then all of a sudden take a sh*t on me?
*EDIT* By the way, my phone is not being used on Verizon. I have it flashed to Cricket. Would this have anything to do with it?
Related
Hello,
I am experiencing some annoying stability issue with my device. From time to time (manilla.exe and/or cprog.exe) just crash. It maybe happened 3-5 time within the last 2 month, but it is still very annoying as I missed call...
I am also using from time to time MSN messenger, which seems to be weird on my device. First it duplicated all my contact in messenger (I was able to fix this by removing my live account and setting it up again). And, sometime message arrives in the wrong window (messages from person A are coming in the conversation I am having with person B).
One day I even found my device with some black-white artifact on the screen, the only way to get rid of this was to reset my phone.
I am using the official HTC rom with only a few app installed (resco, tomtom, coreplayer, answerkeydisabler, ...).
I am now seriously concerned about the health of my phone. My previous devices (tytn, tytn II) were a lot more stable for my everyday use. Is this is "normal" or is my device faulty?
Thank you
I went through two and both had issues. The first was far worse than the second, but even the second was lacking stability (HTC Fuze version primarily using AT&T ROM, but even the custom ROMs I tried weren't completely stable).
My stock Sprint ROM TP is very stable, even with a LOAD of stuff that I have put on it. Of course as a lot of stuff is still in development, I'll have stability issues with certain apps, but once I remove them it's back to great stability.
When I just had a few things on it, it was rock stable. Maybe it's one of your apps even though they are few?
I installed serendipity 6.4 w/ hardcore speedmod about 3days ago and everything works very well,but when I get a incoming call the phone rings once and I drop signal "no service" a second or two goes by signal comes back everythings fine no missed call shown, like I never got a call...But I can make outgoing calls...plz help
Same exact problem for me, I even tried restarting fresh and doing the whole flashing process over again and still have the same issue.... I'm about to switch roms if this keeps up but I really liked Serendipity
Same problem here, same ROM, same version.
What have you guys tried?
I've flashed back to stock using ODIN and then flashed back to Serendipity again. Problem appeared to be resolved at first, but then 2 days later the symptoms started to repeat.
That made me suspect the problem was with particular apps or widgets I'd stuck on my home screen, so I tried removing my newer apps & widgets such as Facebook and NYT to no avail.
Anyone else with ideas?
I do rather like Serendipity, but will probably end up flashing back to Cognition or something to get around this. Guess I'll wait for Mikey's 2.3 to stabilize!
Update:
Flashed back to a clean Serendipity 6.4 and did not use Titanium Backup to restore my apps. It's working fine right now. In the next few days I'll restore individual apps as I need them, and see if the problem recurs.
Best theory so far is that the problem is either
a) Caused entirely by a particular app or widget
b) Caused by some sort of strange incompatibility between Serendipity 6.4 and a particular app or widget
Ok it started with my first triumph. got it 2 weeks ago lasted all about 3 days and it went dead locked up wouldnt even come on. But whle it was working the stock rom wouldnt connect to wifi no matter what i tried, reset, battery removal, airplane toggle, cleared everything the whole shot. then i installed froycream sandwich and cm7 reloaded and they both worked great the wifi connected no problem. until the phone died.
Enter phone number 2. i had to track down because there werent any anywhere for 100 miles in any direction besides the one i found in a outta the way radio shack. got home the wifi connected right away no problems on stock i thought to myself hmm musta been something wrong woth the first phone from the word go, anyway installed cwm 5.0.2.6, then installed cm7, got all my stuff set up and wifi was working fine. went to bed woke up and went to connect to wifi and nuthing again when you turn wifi on it scanns says connecting and then says disconnected every few mins or so it will try and connect but it just continues to loop. i flashed back to a backup of stock and it connects again. tried froyocream sandwich v1.3 and cm7 reloaded by whysor 3 different builds.
ok so ive been flashing back and forth and and clearing this and that and trying different things , doing things in different order, installing different builds, trying to get it to work.
in between custom roms i decided to restore back to stock and see if it would connect stock again or not. at first it didnt, then i rebooted and tried again and it finally connected...woohoo. i was actually afraid that if i changed anything i would lose functionabilty again. but i flashed froyocream sandwich 1.3 again and cfrossed my fingers and sure enuf it connected when i got all setup. i have successfully used it on and off wifi for the last half hour anyway so ill keep posting my results ive seen a few people have kinda similar probs maybe we can figure it out , im looking through logcat files to see if i can see anything funny but................
I had this problem once before, I had to boot into clockwork go into advanced & wipe dalvik cache, then flash the OC kernel again & all was well. That's if your running CM7 reloaded.
I've run into this issue also
So here's my issue, my Galaxy S Blaze has been switched from ROM to ROM constantly, I have seen ROMS with modified build.props, other added features, and a bunch of other tweaks, you name it! I don't know what all those tweaks mean, I have no idea if it could affect the way my phone receives the signal but it got me so frustrated that I kept switching roms until finally then I went back to stock and am no longer am switching to another ROM.
Here's a history of the ROM switching I've made in the past couple of months:
1st - MIUI
2nd- Cyanogenmod
3rd- Gummy ROM
4th- Liquidsmooth ROM
5th- Cyanogenmod
6th- Dirty Unicorns (problems with signal started occurring right about here, and onwards)
7th- Stock ROM (hmm... nope nothing fixed.)
8th- Validus (still no, I didn't like the constant force-closing of many apps)
9th- Gummy ROM (nope, what's worse is my screen kept freezing if I had atleast 2 apps open and I slid down the notification drawer)
10th- Cyanogenmod (well, maybe switching to cyanogenmod will fix it)
11th- Gummy ROM (*sigh* switching back? Nope, still didn't help my signal)
12th- Stock ROM (you would expect it to be fixed right about here, but nope)
So what's up what is the exact problem with my signal? Here's the thing: My signal works! That's a start atleast. However, if I turn on my Wi-Fi while I'm home, I can still call/text people, all of that works. But after maybe 2 hours or so, the signal bar is still there, it's telling me it has signal and it's connected, SOMETIMES it will be empty meaning I have no signal(when I really do). But in reality, I can't receive texts, nor calls, none of that. So how do I fix it? By restarting my phone sadly, that has been the only solution for me for these past 2 months. People have complained to me because I don't answer my phone anymore, well I'm sorry my phone can't receive those calls due to this messed up signal. There are 3 other T-Mobile phones in the house that have no problem! The problem here is with my Blaze phone.
So what if I turn the Wi-Fi off for the whole day and see if it's the main thing causing the issue? Well, I did this. Turns out that the signal stays on longer than when I'm on Wi-Fi but it still goes out. I have switched SIM Cards, I have tried switching my APN: from "epc.tmobile.com" to "fast.t-mobile.com" but the problem appears to happen more quickly on the "epc" one than the "fast" one. Please help me with this, this has been frustrating me a lot lately. I'm not sure if anyone has even had the same exact problem that I'm having, I've searched online but haven't seen a similar problem.
Some of you might say, wow that is a lot of ROMS you've switched to, I'm sure there were more that I missed but that's as of recent. I can install ROMS correctly, I know how to use CWM when installing a .zip and using Odin when it's a .tar(or other supported file extensions). I've factory reset, wiped the cache, the dalvik cache, all before installing a new rom. After installing each rom, I've also factory reset and wiped the cache to make sure no other problems could affect the way the rom would work. Hopefully I did the procedure right, thanks for anyone who's willing to help me!
Right now I am running:
Baseband Version:
T769UVLH5
Kernel Version:
3.0.8-perf-T769UVLH5-CL990184
[email protected] #1
SMP PREEMPT Fri Aug 17 15:12:14 KST 2012
Android Version:
4.0.4
Another Issue is that I can't even transfer files to and from my phone when connected to my computer! This is another big issue, here are some images:
http :// i.imgur.com/xx699ss.png
http :// i.imgur.com/1wRzJpX.png
Here's what happens when I turn Wi-Fi Calling on but maybe it's just a built-in function that I forgot it had and it's probably normal:
http :// i.imgur.com/cTSqRci.png
By the way, sorry for the links just copy and paste them in a browser to and remove the spaces between the http :// and i.imgur, thanks! Unfortunately, I can't post links until I reach 10 posts. If the links don't work for you, I've also provided attachments.
Many thanks!!!
That last picture does show the proper function of Wi-Fi calling however I don't know what to say about the rest of your problems.
Sent from my SAMSUNG-SGH-T769 using XDA Free mobile app
There are two things I would recommend trying...
1. Use Blackhole System Wipe
I know you've been following all the proper steps in CWM (and I would say to keep doing so), but I've added using Blackhole, in addition to the first steps, and I always get great system performance on my phone, and my parent's phones (I put them on ProvisionMod after stock was being stupid). It works well for pre installation for ANY ROM and helps prevent pesky issues. However, chances are, your issue is baseband related and this probably won't solve it... But still! You never know! It's worth a shot!
2. Reroot your phone
I know this will be annoying and pesky... but sometimes the process goes wrong from the beginning and starts giving issues later on... When I first rooted my mom's blaze, something went wrong, despite my following all the directions, and one of her partitions was completely disabled, no matter the ROM. I redid the process of rooting her phone (not from GB though... From the ICS stock) and fixed the issue instantly! I would try these two steps first and see if they do anything! Good luck!
Sent from The Doctor's Blaze
To begin with, I got my phone rooted with CM10 on it - I don't remember how well (or if at all) the GPS worked under that one, because I found it laggy as all crap. I went back to Gingerbread and have LOVED the increased responsiveness, but the GPS is now flaky as all-git-out.
Here is what I have tried:
Old baseband plus...
Eagle's Blood
CM7 7.2 "Stable"
CM7 7.2 Latest nightly (2013 march something, iirc)
I dropped it back to stock and let it update to the new baseband, then...
CM7.2 Latest nightly (ye gods that sounded awful. Oh, and the GPS didn't work.)
HellFire Phoenix reborn/reloaded/whatever the latest one was - I followed all of the "THIS ONE IS DEPRECATED, FOLLOW THIS LINK INSTEAD" links.
I have used the following kernels, more or less randomly, in addition to the ones that came wrapped into each ROM...
MazKrnl v1.0 rc2
Trinity T15
Trinity ELP
MazKrnl and ELP gave me sleeps of death in addition to the GPS not working.
Now, my first GPS lock after loading HFP (my latest ROM - and I am just trying T15 with it as I type this) took about five seconds and held solid. I was SO FREAKING HAPPY! But that was yesterday.
This morning, according to "GPS Toolbox" it can see anywhere from 9-11 satellites - and has a lock on all of them - but won't give me coordinates at all. This is true even after about 30 minutes sitting by a 7th-floor window.
IT'S MADDENING.
I've been googling. I tried messing with the GPS.CONF file, adding and replacing north-america ntp servers. I've tried downloading and re-downloading AGPS info from the GPS toolbox app. I flashed the "for_old_bb.zip" that I found somewhere - even though that's supposed to only affect audio - and GOOD LORD THAT WAS A MISTAKE, given that I'm now on the new bb. (The "new_baseband.zip" which is its alternative seems to have vanished utterly from the internet, sigh.) So yes, I'm down to grasping at straws.
Did I mention the maddening part?
I'm aiming to put together a for-real, once-and-for-all solution to the GPS issues here, because everywhere else it's 2-3 years old and nothing referenced anywhere has worked for me. I know this phone is a little long in the tooth, and dev has basically stopped, but am I really the only one still in this boat?
Thanks - seriously - for ANY help with this.
Update:
T15 kernel (?) caused a sleep of death over lunch.
Completely eliminating the GPS info (App "GPS Status & Toolbox" -> Settings -> Reset) and letting it sit with no internet access for oh, about an HOUR led to a post-reboot fix in a reasonable amount of time.
Oh, also I removed the "SUPL" info - per this post.
Of course, then my battery was wasted, so I'm recharging to test again later.
Honestly people - is this phone worth it? I only "upgraded" from my HTC Thunderbolt for the 4G - which, I admit, is nice when I'm not on wifi...
This phone has always had GPS issues.
The last baseband helped a bit, but it was never fully resolved.
I still use this phone, and still use the GPS on it nearly daily for tracking my hikes and bike rides.
My steps:
Run GPS Test.
If locked, great, done.
If not, wait about 10-15 seconds.
If it doesn't lock within that time, it will never lock without a reboot, no matter how long you wait.
Reboot.
Run GPS Test again.
<Repeat the above steps>
Generally I have noticed that 95% of the time, that a lock will happen after a reboot.
The other 5% of the time, you will have to reboot again.
The other annoyance for me is that during runtime, while you are using the GPS, it will just lose lock.
If that happens, you are toast. It will never come back without a reboot.
I don't even bother waiting, hoping it will come back.
As soon as it loses lock, I do a reboot.
On reboot, it generally locks right away again.