[Q] Permanent LOS - Epic 4G General

I just got my Epic 4G Touch today, and after changing the PRL and attempting to use roam control, my phone started to get LOS that persists after reboots and flashes. I've tried flashing back to stock, flashing back to the first backup I did, flashing the stock radio over "Phone" in ODIN, using Roam Control again, and flashing kernals that claim to reduce LOS. I've had no luck so far.
Has anyone else experienced anything like this? And if you did, were you able to reverse it?
Edit: I just tried manually disabling roaming on the networks tab, and now my LOS is gone. However, now it's saying something about registration failure. I'm trying a restore again to see if it was something I fiddled around with in the ##3282# menu.
Edit Again: Damn, that didn't work either. I'm calling Sprint and just saying that my data doesn't work anymore. Voice is working fine though.
Edit2: ****, I posted this in the wrong forum. Sorry mods.

Welcome to the world of the latest buggiest high end phone. No one knows exactly what causes the LoS orgy, but it seems exacerbated by custom modifications like rooting and custom kernels, although some on stock everything get it as well.
How did i resolve mine? I ditched it and went back to my Nexus S that works and has none of these issues. I didn't appreciate paying nearly 400 for a phone and it's near useless as a phone.
Good luck.
Sent from my Nexus S 4G

LordLugard said:
Welcome to the world of the latest buggiest high end phone. No one knows exactly what causes the LoS orgy, but it seems exacerbated by custom modifications like rooting and custom kernels, although some on stock everything get it as well.
How did i resolve mine? I ditched it and went back to my Nexus S that works and has none of these issues. I didn't appreciate paying nearly 400 for a phone and it's near useless as a phone.
Good luck.
Sent from my Nexus S 4G
Click to expand...
Click to collapse
+1 on this... Stay FAR away from Samsung if you rely on your phone as anything more than a toy to tinker with.

LOS = Loss of service?

insanity213 said:
+1 on this... Stay FAR away from Samsung if you rely on your phone as anything more than a toy to tinker with.
Click to expand...
Click to collapse
Well, Nexus S was made by Samsung and is a pretty good phone. Most manufacturers (HTC, Motorola etc) have their share of problems as well. As long as Sammy does not deal with the software side of things, it produces fine hardware. The LOS (loss of service) issue with ET4G is still unresolved though .

dohturdima said:
Well, Nexus S was made by Samsung and is a pretty good phone. Most manufacturers (HTC, Motorola etc) have their share of problems as well. As long as Sammy does not deal with the software side of things, it produces fine hardware. The LOS (loss of service) issue with ET4G is still unresolved though .
Click to expand...
Click to collapse
A regional thing perhaps? I've never had an issue like that with my Epic.

Related

Can't stand all the problems on the N1!

I am about to sell my nexus one and get a g1 again or a cliq, I can't stand my phone losing service so much, not sending text messages, and having to turn on and off just to get my service to work again, I thought this was a "super phone"!?!?
anyone else tired of the N1?
No. I don't have those problems. Maybe you can call tmobile about it and have them do a service test in your area.
are you rooted by any chance? If so, why not flash a new radio?
phiber23 said:
No. I don't have those problems. Maybe you can call tmobile about it and have them do a service test in your area.
Click to expand...
Click to collapse
^^^What this guy said.^^^
Nice first post, by the way.
definitly not having those problems
get in touch with tmobile and/or htc
Yes go to a Cliq and get more problems =P
kuchtaa said:
I am about to sell my nexus one and get a g1 again or a cliq, I can't stand my phone losing service so much, not sending text messages, and having to turn on and off just to get my service to work again, I thought this was a "super phone"!?!?
anyone else tired of the N1?
Click to expand...
Click to collapse
It is the best phone available right now and most probably, will be for the next 6 months.... the problems u described is service related, so say "I'm going to switch my service provider" instead of "I'm going to switch my phone"
You're the first person who would be switching from N1 to G1 or Cliq .....
Yeah, it's an awful phone, I'll give $250 for it just to end your frustration.
Strange, I'm on a different network, in a different country, and I too suffer from data "freeze".
only way to fix is power cycle or airplane mode and back...
faraz1992 said:
It is the best phone available right now and most probably, will be for the next 6 months.... the problems u described is service related, so say "I'm going to switch my service provider" instead of "I'm going to switch my phone"
You're the first person who would be switching from N1 to G1 or Cliq .....
Click to expand...
Click to collapse
This post is everything I wanted to say. Don't downgrade yourself to a lower phone because you are having lousy service provider issues - even though I love T-mobile, it may just not be for you. I do believe though you are trying to be a forum "troll".. (thread starter).
Well the SMS not sending (and having to reboot to fix) seems to be an issue with the OS from what I have been reading.
Meh.. I'm willing to bet that the op either needs to do a factory reset or exchange his phone if it's defective. Obviously his experience is far from typical.
Yeah I haven't had any of these issues, my N1 gets the same signal and speedtest results as my G1. If T-Mob is the problem in your area then a new phone likely wont resolve your problems, if you really think its the phone try a factory reset and see if you still have these issues or if an application you installed is causing them. If you really want to get a new phone go for it, but I think your experience will be less than stellar after using the N1. If you want to sell it let me know how much.
its kinda weird for me, I can receive all the MMS I want but my phone will not send anything MMS, via WIFI or EDGE (ATT). It all worked when I got my phone but since flashing different roms it has been reduced to only getting MMS.. APN's are correct also
any idea's?
-Charlie
Welcome to xda. Most are not having any of your issues (the Nexus Rocks). Where are u located & are u on tmob? stock rom? Provide more specifics & check out their existing threads.
its not that bad. I have a few little issues but I still love it.
trinode said:
Strange, I'm on a different network, in a different country, and I too suffer from data "freeze".
only way to fix is power cycle or airplane mode and back...
Click to expand...
Click to collapse
It's the same for me, very annoying.
Will try a new radio, if that doesn't help...I guess the N1is gone
dont forget the ****ty touch screen >/
kuchtaa said:
I am about to sell my nexus one and get a g1 again or a cliq, I can't stand my phone losing service so much, not sending text messages, and having to turn on and off just to get my service to work again, I thought this was a "super phone"!?!?
anyone else tired of the N1?
Click to expand...
Click to collapse
I sure as hell was. And you're right, until android is stable and dependable there's little about it that's super.
Keep in mind many of the issues can be fixed with software updates.
Other than the market, data, sms, browser, camera and ram issues, the others are relatively minor though admittedly abundant. I have issues daily but I stopped wanting the next iPhone (or older android version) when I stopped expecting my nexus to be as stable as Windows is on my desktop and laptop. I wanted the nexus to be a little computer which made all the shortcomings really frustrating.
But Google wants a large stake in the mobile operating system industry and the nexus is their chance to shine.
The nexus one has great hardware and its googles baby, it should receive the majority of androids attention.
So if you don't want to root the nexus, which was fun with the old g1 but now id like a phone I don't have to fix my self with weekly or even daily Rom updates (which i completely understand is an awesome and valuable option but I think those who root have very few issues and are largely intolerant of people who want fixes but don't want to root, like me : / ),
I understand that its bizarre that there are so many problems but don't jump ship, when Google finally starts addressing all of the issues you'll be satisfied. Think of this phone as beta, that's what i have learned to do, because it has enormous potential! So give it at least until Google gets an update out which really should be soon.
I don't get it.. I'm not rooted and I don't have any of these issues.. is my phone a factory freak or something?

Avoid JI6 update.

From what I gather from trolling on both XDA and the Tmo forums this update is bricking phones regardless of root, voodoo, ocfl, kernel perhaps people should avoid the update pending a more in depth investigation of what exactly is going on. If gps is needed flash the JI2 files found here and that should hold you over for now. This is a worse problem than the ones that came in the captivate and the sprint galaxy s.
Sent from my SGH-T959 using XDA App
I updated manually through odin and it worked just fine. I first went back to stock and started fresh. Gps test found six birds and locked on four thats the best I ever had sitting in front of my doorstep in a heavily wooded area. It would usually find at the most two and would not lock to any. So far so good.
Only speaking for myself.... I flashed it and it's fine. I hope this isn't just a bunch of people freaking out that phone stays at the Galaxy S splash screen for a while and remove the battery or something, thereby f*cking up something. But I don't doubt you.
How to fix your phone and apply the update:http://forum.xda-developers.com/showthread.php?t=803492
My concern comes from the overwhelming amount of people that seem to have that problem I for one I'm going to play it safe and wait til a stable rom based on this release is well released.
Sent from my SGH-T959 using XDA App
Bernardos70 said:
Only speaking for myself.... I flashed it and it's fine. I hope this isn't just a bunch of people freaking out that phone stays at the Galaxy S splash screen for a while and remove the battery or something, thereby f*cking up something. But I don't doubt you.
Click to expand...
Click to collapse
It wasn't hanging on the Galaxy S splash screen. It was hanging at the Vibrant screen. The logcat clearly shows an endlessly looping segfault.
http://forum.xda-developers.com/showthread.php?p=8525623#post8525623
I have an excerpt of the log, which is similar to another user who had the same issue.
Points of commonality so far with another user who had stock + root + brick is we both disabled the boot sounds + titanium backup + rom manager.
yespinosa said:
My concern comes from the overwhelming amount of people that seem to have that problem I for one I'm going to play it safe and wait til a stable rom based on this release is well released.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Considering that the people who contribute to the XDA and T-mobile forums represent a fraction of the installed base, "overwhelming" may be an overstatement.
"Lots" of people also report successful installs.
i flashed through odin, so did my roomie, and his friend got the ota. everything went smoothly. i think that we are not hearing nearly as many people that the update went well compared to those who have had issues. we all had root, blackbar mod, mobile ap, captivate camera, and i had gps from ji5. no problems. do a nandroid and put it in a safe place then go for it.
Worked fine for me as well.
yespinosa said:
From what I gather from trolling on both XDA and the Tmo forums this update is bricking phones regardless of root, voodoo, ocfl, kernel perhaps people should avoid the update pending a more in depth investigation of what exactly is going on. If gps is needed flash the JI2 files found here and that should hold you over for now. This is a worse problem than the ones that came in the captivate and the sprint galaxy s.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
The only people who should probably avoid the JI6 OTA, are people who fail to understand they have a responsibility for their own potential grief when they mod their phones in ways T-Mobile and Samsung cannot easily account for.
Granted we should hold T-Mobile's butt to the fire if their OTA is indeed soft bricking or hard bricking bone stock unmodified phones, but I don't see any clear evidence of this at all. And it's not too surprising either, as very few people who come here have bone stock devices, and fewer still are willing to revert to bone stock simply to test.
Rather what I see are people utilizing these wonderful forums to do wonderful things to their phones without having to have developed anything remotely approaching a keen understanding of what they've actually done. It's ridiculously easy to mod these phones without having the first clue what you're doing. This leads to many mis-perceptions which easily turn into noise.
There is a level of responsibility you have to take upon yourself if you're going to participate actively in modifying your device. For some it's just easier to deny this responsibility and quest for someone to blame. That may not always be the case, but it's clearly taking place with some few people over this OTA.
Agreed. We are an incredibly tiny segment of the universe of smartphone users out there. The vast majority of people buy an iPhone or Android make calls, sync their contacts and calendar, surf the web, email and text. If you started talking about rooting or jailbreaking they'd look at you like you're insane. The people rooting and modding their phones are a tiny minority, and we assume all the risk when we do it because this is not normal and customary use of the phone. Most people use their phones stock, and people who don't are assuming the risk of things going bad.
I'm fairly convinced after the Captivate OTA fiasco that you put your phone at real risk of not being able to get successful OTAs if you flash custom ROMs or kernels. The deepest I'm willing to go is rooting and lagfixing, but even then I know I'm playing with uncertainty.
masterotaku said:
The only people who should probably avoid the JI6 OTA, are people who fail to understand they have a responsibility for their own potential grief when they mod their phones in ways T-Mobile and Samsung cannot easily account for.
Granted we should hold T-Mobile's butt to the fire if their OTA is indeed soft bricking or hard bricking bone stock unmodified phones, but I don't see any clear evidence of this at all. And it's not too surprising either, as very few people who come here have bone stock devices, and fewer still are willing to revert to bone stock simply to test.
Rather what I see are people utilizing these wonderful forums to do wonderful things to their phones without having to have developed anything remotely approaching a keen understanding of what they've actually done. It's ridiculously easy to mod these phones without having the first clue what you're doing. This leads to many mis-perceptions which easily turn into noise.
There is a level of responsibility you have to take upon yourself if you're going to participate actively in modifying your device. For some it's just easier to deny this responsibility and quest for someone to blame. That may not always be the case, but it's clearly taking place with some few people over this OTA.
Click to expand...
Click to collapse
+1 to one of the most cogent comments I have ever seen here.
One footnote about the risks for ordinary end users: If T-Mobile's OTA process bricks a stock phone, apparently the carrier's typical procedure is to replace the phone. If the phone is not stock, the customer is probably on his own for a remedy. Pottery Barn rules are real. Smarphones are not cheap, and having your phone number tied to this handheld computer (or at least the carrier) by contract makes device failure harder to cope with.
Kubernetes said:
Agreed. We are an incredibly tiny segment of the universe of smartphone users out there. The vast majority of people buy an iPhone or Android make calls, sync their contacts and calendar, surf the web, email and text. If you started talking about rooting or jailbreaking they'd look at you like you're insane. The people rooting and modding their phones are a tiny minority, and we assume all the risk when we do it because this is not normal and customary use of the phone. Most people use their phones stock, and people who don't are assuming the risk of things going bad.
I'm fairly convinced after the Captivate OTA fiasco that you put your phone at real risk of not being able to get successful OTAs if you flash custom ROMs or kernels. The deepest I'm willing to go is rooting and lagfixing, but even then I know I'm playing with uncertainty.
Click to expand...
Click to collapse
I've flashed this phone more times than I can count at this point. Soft bricked it at least a dozen times. But all that self imposed grief has got me to where I am now, where I can (hopefully) reliably recover from just about anything. I still cross my fingers every time I crank up Odin3 v1.3, but I no longer visibly sweat!
We're fortunate in that these phones are surprisingly difficult to hard brick for the most part, and that given a bit of legwork one can recover from nearly any bad scenario.
It's better to flash stock ROM and then JI6 ROM manually like me and it works for me like a charm !
d01100100 said:
It wasn't hanging on the Galaxy S splash screen. It was hanging at the Vibrant screen. The logcat clearly shows an endlessly looping segfault.
http://forum.xda-developers.com/showthread.php?p=8525623#post8525623
I have an excerpt of the log, which is similar to another user who had the same issue.
Points of commonality so far with another user who had stock + root + brick is we both disabled the boot sounds + titanium backup + rom manager.
Click to expand...
Click to collapse
Then I don't know if what I'm about to tell you or not, but I have and use Titanium Backup and ROM Manager. Odin went through smoothly. That leaves the boot sound as the culprit. Had a couple of things metamorphed as well as mobile AP and the GPS files from JI2 installed, if that helps.
Bernardos70 said:
Then I don't know if what I'm about to tell you or not, but I have and use Titanium Backup and ROM Manager. Odin went through smoothly. That leaves the boot sound as the culprit. Had a couple of things metamorphed as well as mobile AP and the GPS files from JI2 installed, if that helps.
Click to expand...
Click to collapse
Even though you installed ROM manager, have you used it to install Recovery? Did you have a current ROM backup update.zip file created on your internal sdcard?
I'm just gonna throw my 2 cents in here...i did the update over an edge network and everything was fine..I have rooted then unroot and the ocl
Sent from my SGH-T959 using XDA App

[Q] Can someone tell me I'm not alone?

Haha I see so many people complaining about bricked vibrants, apps not working, .zip files not working right, market issues, bad battery life and screwy bugs...
Am i a lucky guy who just got one of the "few" working vibrants??
I got my vibrant on release day from a preorder at radioshack...
It was not hardware locked and came with the original firmware.
Im currently running bionix 1.9.1 with the kk oc/uv kernel, launcher pro plus and have 76 user apps installed and this rom still keeps up. 2g is kept on until i need to use 3g. (2g 12 hours, 3g on the rest)
I previously installed oclf on all roms but this rom you dont need one, even with the cpu running at 200 MHz and 1000 MHz.
I have a livewallpaper running, no led notifer on for my sms, beautiful widgets, weatherbug and youtube all on 2 hour update and my battery lasts from 7am off the charger until 10 pm when im home with about 35% remaining with brightness on the lowest setting.
My gps works on spot , unfortunately not in my basement where my room is located. Wifi and bluetooth also work perfect.
Ive softbricked once when flashing a cappy .zip and just got into recovery and performed a nandroid
So whats up how many of you guys have a awesome, powerful vibrant like me?
I guess I am also one of the lucky ones
Mine always worked fine. Not hardware locked. GPS always worked too. The only problems I've had with it have been inflicted by the user (i.e. ME)
I think most Vibrants sold are working properly. I think the representation of folks who come to this forum in search of ways to "fix" their phones is disproportionate.
your not alone
I have had no problem with my phone I have flashed it with 3 different roms and it has been awesome. The only thing I have noticed is the gps does not tell me when I have a satellite lock but is is always accurate to 10-15 meters
My Vibrant is working like how I wanted it, the only issue is definitely GPS. Although, spotty, it at least work at the moment. I just wish it is more accurate so when my phone gets stolen, I have a fighting chance to get it back (via one of the many great anti-thief programs).
mine runs great
I guess you can consider me a lucky one as well.
I got mine on a release day back in July, and aside GPS issues at the beginning I had no complaints. Running Fusion Bionix ROM, and couldn't be happier.
I will def skip the Foryo OTA even if it comes before a working Froyo ROM is available from the brilliant devs on here.
At my work there are 5 of use with Vibrants and they all run fine. Honestly people who have issues are typically going to be more vocal than people who have no issues. So it seems like there are rampant issues with the Vibrant when in fact its only a minority of people having issues.
i ordered mine the day it came out (couldn't preorder cause on an employee account). gps wasn't that great, but worked most the time. rooted it and got rid of bloatware, still just unreliability of gps. started changing things like startup/shutdown animations, ji2 gps, and stuff, no problems. started flashing roms and am on bionix 1.9.1 oc, no problems.
My box date is 7/11/2010. Mine has been rock solid and not hardware locked. Love this phone. Fast, sexy, and unbrickable. The only problems I've had were caused by my own shenanigans.
Running a custom ROM should exclude you from voting. If you have to re-engineer a device to get what you paid for, you aren't getting what you paid for....
-bZj
Mine had the hardware lock and GPS issues, but both are fixed now. I've been lucky in that everything else I've thrown at it works fine. Overclocking is fine, voodoo is fine. The thing is smooth as butter and battery life is pretty damn good now.
Remember people happy with their phones don't usually post.
Sent from my SGH-T959 using Tapatalk
I don't know what the hell happened to my phone after the update. I don't even know what to say
SpacelySprokets said:
I don't know what the hell happened to my phone after the update. I don't even know what to say
Click to expand...
Click to collapse
Then don't say anything?
I like being a smartass.
Most people won't post to say hey my vibrant is working great! Rather they would post when they encounter a problem and need help quick. I haven't had any problems that I couldn't easily fix by myself l.
Sent from my SGH-T959
My vibrant worked great, untill the last update. Now I get lag sometimes real bad.
I was real happy. Now I'm looking for roms.
down8 said:
Running a custom ROM should exclude you from voting. If you have to re-engineer a device to get what you paid for, you aren't getting what you paid for....
-bZj
Click to expand...
Click to collapse
No i don't think so , ive had android phones in the past and since the vibrant was gonna be a large seller for tmobile i expected a large development community like we are seeing and expected roms. So i bought the phone intentionally to mod it but thanks!
Also since most people on XDA have rooted their phone, you can expect they will have more problems than the average consumer. It's one of the downsides of modding. I don't think stock phones have been soft bricking only modded ones.
down8 said:
Running a custom ROM should exclude you from voting. If you have to re-engineer a device to get what you paid for, you aren't getting what you paid for....
-bZj
Click to expand...
Click to collapse
Really? I paid a premium for a device I could customize to my liking (cough-cough iPhone anyone???), well if it weren't for the dev section here I would've been very upset with the outcome.
CitrixLemon said:
Also since most people on XDA have rooted their phone, you can expect they will have more problems than the average consumer. It's one of the downsides of modding. I don't think stock phones have been soft bricking only modded ones.
Click to expand...
Click to collapse
Read the numerous posts here about JI6 OTA update from the users that just received their phone, some of them were sad pandas when they had to stare at the Vibrant screen after they click update button.
If you read enough, and comfortable enough to mod your phone soft bricking it should the least of your concern

[Q] DK28 - phone useless.

I've had DK28 installed or over a month now and used various different roms, but about two weeks ago, data ( and consequently voice and messaging) all dropped and refused to work. I've heard of several other people having this problem as well, but am surprised that more people haven't experienced this. Once data drops, rebooting, reflashing, and re-odining all refuse to restore service reliably. My only solution I've found is to re-odin to DI18. It's quite a step back however, I'm curious if people have found ways around this or it only affects certain phones..
two words, truly epic
Never had what you are talking about. I was on bonsai rom and now I'm on a new test build rom and I don't have that problem. Try bonsai rom its awesome.
Sent from my Evo Killer!!!
Did you Odin to DI18 between each DK28 flash??? Just sayin, if you loaded DK28 once, and just switched roms, even wiping etc.... that could be a problem. Sorry if you did, but just checking, you didn't type out your whole process... if you do, someone may see the common denominator, etc.... 2.2 works fine for me, other than a couple minor bugs that have been traced to kernel issues... so hopefully source will fix them.
Actually, tried Bonsai rom too, but problem persisted. I'm pretty sure it's a modem issue. You can tell it's happening, because you can see that there will be a certain amount of signal (2 bars, 4 bars, 5 bars) but no data service (indicator is also missing). Calls fail to connect, messages fail to send, and of course, data is non-existent.
I've never had a problem with DK28 and I strongly suspect that if you have, it's due to a PEBCAK error.
It's not a PEBCAK error. It's been experienced and documented by several other users:
http://forum.xda-developers.com/showthread.php?t=922428&highlight=dk28+modem+zip
I've tried about a dozen different things, but the lowest common denominator is that I've wiped my phone and used odin to restore to the stock DK28 leak to no avail. A consensus seems to form that my phone may just be moody. I've already begun steps to exchange it, although I'm far past the 30 day window...
Have you tried flashing back to the stock modem and rom, then reflashing to DK28? Instead of just flashing the DK28 modem again.
Bye bye as this is a troll thread...
Its not a troll thread.
I'm going through this right now.
Unfortunately, I'm stuck with my no-phone for a few weeks as I have no computer here >:|
Sent from my SPH-D700 using XDA App
I've been using google voice to text over wifi.
VoIP would be a great feature.
The longer I have the epic, the better T-mobile is looking
Sent from my SPH-D700 using XDA App
I had similar glitches with DK28, but they were usually resolved by rebooting the phone or turning data off/on. The last straw for me was when my daughter tried contacting me for and emergency. She was unable to get a hold of me because my phone and data had literally stopped working without warning. After rebooting the phone, I had nearly 20 voice mail messages from her and others throughout the day. The next day I want back to 2.1.
Since, I have replaced the Epic with an EVO. The epic is still in my desk drawer waiting for the day Samsung gets their heads out of their asses and update it.
saebodybuilder said:
I've had DK28 installed or over a month now and used various different roms, but about two weeks ago, data ( and consequently voice and messaging) all dropped and refused to work. I've heard of several other people having this problem as well, but am surprised that more people haven't experienced this. Once data drops, rebooting, reflashing, and re-odining all refuse to restore service reliably. My only solution I've found is to re-odin to DI18. It's quite a step back however, I'm curious if people have found ways around this or it only affects certain phones..
Click to expand...
Click to collapse
TRY THIS IT RESETS EVERYTHING IT WORKED FOR ME EVEN GOT FASTER INTERNET CONNECTION WITH 3G-4G CUZ DK28 SLOW IT DOWN AS WELL AS GPS NOT WORKING NOW IM GOOOOOD.
xda-developers > Samsung Epic 4G > Epic 4G General
easiest way to fix gps using DK28
DK28 is fine
I'm a Vibrant owner who has been setting up my gf's Samsung Epic. Immediately rooted that beast and put TrulyEpic on it. That ROM was killing her battery life in less than half a day so I switched her to the Bansai ROM and it's the same deal. Is this standard for Epic users?
Leave your girls epic on stock di18.
Not worth putting dk28 on someones phone if they can't do it themselves. There's just too many bugs, no matter which froyo rom you run
Sent from my SPH-D700 using XDA App
A_Flying_Fox said:
Leave your girls epic on stock di18.
Not worth putting dk28 on someones phone if they can't do it themselves. There's just too many bugs, no matter which froyo rom you run
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
No ****? All right, thanks man.
People think that since this problem hasn't occurred for them it must not exist. It's obviously an issue for some of us. As for remedies, I've tried, cycling data, airplane mode. All no good. The funny part is it'll pop - and work for a few hours- then go back to being an expensive mp3 player. I've even odin-ed to DI18, problem still persists. Take the phone back, give sprint hell. And while you're giving them hell, ask them where the hell our Froyo update is.
Dk28 is very buggy. Load a custom rom over it like nebula, bonsai, or truly epic. They fix almost all of the bugs and they are faster than stock
Sent from my SPH-D700 using XDA App
If this happens on DI18 as well, obviously its hardware... back to sprint... hopefully youre investing in TEP. If it is just DK28, try that GPS fix, may sound like not related, but it is just doing it the meticulous long way, which in the long run works great. I have never had a real data issue, but GPS I never got better than 10 meters or whatever, did that method, locked in 3 secs to 2 meters... crazy. I think not all the pit, modem, etc files are created equal... you may lose something in DL from some crappy free file hosting site, your flash may miss one little thing because the Samsung Drivers are crap... Theres so many variables. But the majority of people don't have any of these issues... so either you have software issues, and need to go back to stock, then it works fine... or if not, Do a tried and true method to get to DK28, and then see if it happens again. Data dropping could be so many things... location, how settings are tweaked... did you try the 'want better 4g signal' thread? It also links to a 3g fix that I think was also found to help on the EVO... just sayin... theres fixes out there, this is a totally unfinished build, what the devs have done with it is amazing.
That said, unless you want to be designated tech guy, keep her on stock. Unless she absolutely needs Flash, or wants to have 500 apps on her phone... she will probably not miss out on much, its power users and those who bought docks and HDMI cables that are really getting the shaft.

No mobile data on any aosp rom? (H918)

Very odd, I do a complete clean flash on all aosp roms available for the H918 and every single one won't allow mobile data to work. I go back to a stock rom and its fine. Has anyone encountered this? Almost as if T-Mobile locked aosp on me. Strange!
I've got the same issue on Verizon. I can get it to work for a bit but eventually quits until I do a network reset. Can't seem to find an answer in any thread and it's either always overlooked or ignored when someone mentions the problem.
Sent from my LG-VS995 using XDA-Developers Legacy app
chachh said:
I've got the same issue on Verizon. I can get it to work for a bit but eventually quits until I do a network reset. Can't seem to find an answer in any thread and it's either always overlooked or ignored when someone mentions the problem.
Click to expand...
Click to collapse
Yep I hear ya. I went back to complete stock. I had to kdz twice to get signal back on T-Mobile. I'm reluctant to root again. Believe it or not even with my phone bloated again I guess better battery life. I think routing now these days is too much hype. Fun though. But still. The thread for v20 is not much at all. And it seems like many are abandoning it and going back to stock. Not much of updates or anything. Only thing I liked was the sound mods.

Categories

Resources