Related
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.
Hey everyone,
I just put the cyanogenmod 7.0.2.1 on my HTC EVO 4G about a month ago. At first it was working fine, now it will just randomly restart not while I'm ever using it, but when it is sitting idle it will just restart at odd times. Has anyone else had this issue?
Everything else with the ROM is working awesome. Please Help.
No issues here, why don't you come up to date and flash the stable 7.0.3.1. Are you running any custom kernels by chance?
Here's the link to 7.0.3.1 just flash over your current rom and wipe dalvik-cache.
http://mirror.teamdouche.net/get/update-cm-7.0.3.1-Supersonic-signed.zip
Oh thanks, been really busy with work, and hadn't had time to check for any updates. I appreciate the help very much. DL'ing the new ROM now.
Upgrade to the newer version. Maybe it'll help? Definitely clear cache & dalvik when you update.
Evo 4G / CM 7.0.3.1 - Tiamat 4.0.2 SBC / XDA Premium
I was running CM7 and went to a different Rom because of the reboots and been fine since. Tried all the usual things but phone would still freeze and reboot. Last one I was on was nightly 65. There are also a few threads around about the ROM bricking phones that it makes crash. As usual, nandroid if things don't work out.
Sent from my PC36100 using XDA App
misterzeno said:
I was running CM7 and went to a different Rom because of the reboots and been fine since. Tried all the usual things but phone would still freeze and reboot. Last one I was on was nightly 65. There are also a few threads around about the ROM bricking phones that it makes crash. As usual, nandroid if things don't work out.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
What ROM did you go to?
misterzeno said:
I was running CM7 and went to a different Rom because of the reboots and been fine since. Tried all the usual things but phone would still freeze and reboot. Last one I was on was nightly 65. There are also a few threads around about the ROM bricking phones that it makes crash. As usual, nandroid if things don't work out.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
That's non sense, bricking phones say whaaaaat. I've been running cyanogen roms since the G1 and I've never heard of cm bricking phone's. Don't let this person talk you out of cm lol.
If cm bricks your phone you're (1) an idiot, or (2) shouldn't be rooting your phone in the first place.
dirkyd3rk said:
That's non sense, bricking phones say whaaaaat. I've been running cyanogen roms since the G1 and I've never heard of cm bricking phone's. Don't let this person talk you out of cm lol.
If cm bricks your phone you're (1) an idiot, or (2) shouldn't be rooting your phone in the first place.
Click to expand...
Click to collapse
Yeah I like the CM7 ROM, but just can't take the restarts. I am going to upgrade to the newest stable release and see if that fixes it. I would like to stay with the CM7 if at all possible.
Swype
after the update I notice swype is gone, one of the stock features I like, anyone know where to find that again?
beaukincade said:
after the update I notice swype is gone, one of the stock features I like, anyone know where to find that again?
Click to expand...
Click to collapse
Its probably still there you just have to open a text window long press the text box and hit "input method". Once you hit input method swipe will still be there if it was installed.
dirkyd3rk said:
Its probably still there you just have to open a text window long press the text box and hit "input method". Once you hit input method swipe will still be there if it was installed.
Click to expand...
Click to collapse
no its gone and won't let me use titanium backup to reinstall it either
beaukincade said:
no its gone and won't let me use titanium backup to reinstall it either
Click to expand...
Click to collapse
Do you have the latest titanium backup version? If you can't get it going the swype apk is all over the place lol. *wink wink*
Get the latest version (beta) from their site.
http://swypeinc.com/
dirkyd3rk said:
That's non sense, bricking phones say whaaaaat. I've been running cyanogen roms since the G1 and I've never heard of cm bricking phone's. Don't let this person talk you out of cm lol.
If cm bricks your phone you're (1) an idiot, or (2) shouldn't be rooting your phone in the first place.
Click to expand...
Click to collapse
I have ran many different roms and CM7 was the ONLY one that caused my phone to reboot many times a day. A quick google search can show you threads about owners who had phones that bricked after running CM7. I never said it was gospel, I just dont need my phone rebooting multiple times during the day and it was way more often when I had wimax connected. CM is a great rom but its not the second coming of Android and not worth my phone rebooting during the day.
And I am running Smooth N Sexy V1.2 A sense ROM that looks like gingerbread.
Reboots
I've been through several ROMs now and the reboot problem appears to be not a ROM issue!
Here is the story. I had started with Baked Snack, very good, but I wanted more battery and to try CM and get away from Sprint messaging update nag.
CM worked great, I updated to 7, until the reboots started to happen during heavy use of Angry birds.
So I restored to early CM 6.x, and reboots continued off and on every few days, getting progressively worse.
So I tried Warm 2.2, same issues.
I went back to CM7 and still trouble.
I went to Fresh and It was fine for a week, and then on Friday, (I noticed that Friday was significant), reboots again.
So after a month of this the reboots are so bad that I can't use the phone. I called Sprint, de-provisioned the EVO, went back to my Palm, and then unrooted and went back to Stock ROM, but with no Cell access.
The phone is stable now. As long as it's off the Sprint Cellular network!!!
All of the reboots were related to cellular activity. Messages coming in, ads being updated, calls coming in, tower switching, roaming, or worse of all, no tower signals at all.
I will post back here if the phone remains stable without cellular. But all of the research I have done on the issue has pointed to cellular access. I am on wifi and all the apps and functions are working without issues so far. I am starting a dialog with HTC to see if there is a hardware problem.
The reboots also caused heat in the general area of the SD card...don't know what else is there but I do know the cellular antennas are on that side of the phone. Leaving the battery out all night, after an off state recharge would help stabilize the phone for a while, including cache wipes and factory resets.
But once the phone had been on for a while, or Friday morning would come, the reboots would continue.
I have been a computer nut for 30+years and I solve issues for a living. I strongly suspect the radio hardware or firmware as the culprit in this reboot issue. Every other account of this has had similar connections to the radio use.
Agreed 100% , I've been rooting since the day it first became available and never bricked my phone or got stuck in a boot loop by just flashing a "rom". If I get reboots its because I either flashed a kernel or a very unstable rom. It makes me laugh that you think "CM7" is causing the reboots. You say its CM7, I say it's idiots who probably don't follow directions.
dirkyd3rk said:
Agreed 100% , I've been rooting since the day it first became available and never bricked my phone or got stuck in a boot loop by just flashing a "rom". If I get reboots its because I either flashed a kernel or a very unstable rom. It makes me laugh that you think "CM7" is causing the reboots. You say its CM7, I say it's idiots who probably don't follow directions.
Click to expand...
Click to collapse
Dude its all good, no need to call anyone an idots because we all can have different experiences. Any ROM thread in the dev section has reboot posts some have resolutions, some go to another rom and some seem to be hardware issues. Just like you have been rooting since day one like I have doesnt mean that CM7 is NOT causing my phone to reboot when no other ROM does not.
Your welcome for me allowing me brighten up your day by making you laugh, dont take your personal experiences and spread them across every user like its the ONLY experience.
misterzeno said:
Dude its all good, no need to call anyone an idots because we all can have different experiences. Any ROM thread in the dev section has reboot posts some have resolutions, some go to another rom and some seem to be hardware issues. Just like you have been rooting since day one like I have doesnt mean that CM7 is NOT causing my phone to reboot when no other ROM does not.
Your welcome for me allowing me brighten up your day by making you laugh, dont take your personal experiences and spread them across every user like its the ONLY experience.
Click to expand...
Click to collapse
Im not saying cm roms make sense look like windows 95 lol, and I also don't think cm roms would keep me from jumping ship to a 4.3" iPhone 5 neither. I'm simply saying you're pointing the finger at cm being the cause I'm saying imo its 95% user error that's all. When do you hear of experienced users complain of cm (stable) causing reboots or boot loops? Don't worry ill wait....
dirkyd3rk said:
Im not saying cm roms make sense look like windows 95 lol, and I also don't think cm roms would keep me from jumping ship to a 4.3" iPhone 5 neither. I'm simply saying you're pointing the finger at cm being the cause I'm saying imo its 95% user error that's all. When do you hear of experienced users complain of cm (stable) causing reboots or boot loops? Don't worry ill wait....
Click to expand...
Click to collapse
Once more sir, I spoke from my own personal experience. Plain and simple CM7 was causing my EVO to reboot, and especially when it was on wimax or multitasking. Even from a clean install without restoring anything except for logging into google on the device. I spent 4 days troubleshooting the issue including trying different versions and nightlies. Oh yea..and before you ask the temps were normal on the device no higher than any other time.
But yet again another know it all here on XDA. Dam i must be dumb as **** to been flashing my phone since the froyo root method was released and never had another ROM give me that type of issue. The ROM is not worth me going back to the stock RUU and swapping hardware to since that seemed to be the the last variable after my troubleshooting. Not a big ****ing deal...my phone didnt agree with CM7 like I have seen a small number of other users out there. You dont see me around ROM threads always *****ing and moaning about issues when resolutions or known issues are posted on the first page or doing any other nonsense that I will guess others on here are doing that you may be referring to.
Obvious you are one of those XDA "experienced pros" that are quick think someone has no idea what they are doing with their phone. Post count doesnt mean everything bro.
misterzeno said:
Once more sir, I spoke from my own personal experience. Plain and simple CM7 was causing my EVO to reboot, and especially when it was on wimax or multitasking. Even from a clean install without restoring anything except for logging into google on the device. I spent 4 days troubleshooting the issue including trying different versions and nightlies. Oh yea..and before you ask the temps were normal on the device no higher than any other time.
But yet again another know it all here on XDA. Dam i must be dumb as **** to been flashing my phone since the froyo root method was released and never had another ROM give me that type of issue. The ROM is not worth me going back to the stock RUU and swapping hardware to since that seemed to be the the last variable after my troubleshooting. Not a big ****ing deal...my phone didnt agree with CM7 like I have seen a small number of other users out there. You dont see me around ROM threads always *****ing and moaning about issues when resolutions or known issues are posted on the first page or doing any other nonsense that I will guess others on here are doing that you may be referring to.
Obvious you are one of those XDA "experienced pros" that are quick think someone has no idea what they are doing with their phone. Post count doesnt mean everything bro.
Click to expand...
Click to collapse
You've been flashing since froyo I've been flashing since 1.5 G1 hmmmmm let me think. I will say this though
dirkyd3rk said:
You've been flashing since froyo I've been flashing since 1.5 G1 hmmmmm let me think. I will say this though
Click to expand...
Click to collapse
You win, you obviously have the bigger nerd e peen. I should go back to a flip phone. *Bowing to phone gawd*
You wouldn't be as much as an ass if you happen to suggest ONE resolution to the rebooting.
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.
Can someone link me to some instructions that involves Either rooting my note 4 that involves flashing the modems or a stock root that will also flash all modems? Can you also recommend a ROM that you have no had any issues with for at least a year?
I'm not sure if my board is bad or if it just needs to be reflashed. My girlfriend purchased the phone and broke the screen. So before I buy a new screen for it I would like to see if the board is still good.
Board's good (if it runs, you're golden)... and I recently had this problem, too... but mine was due to a system error in whatever ROM I running at the time. Sounds like you're on stock, though? I had that issue when I was on stock (within the first like 3 days having the device). The fix was getting ahold of Sprint on chat, and making sure they had the correct SIM ICC. They fixed it, refreshed, my phone rebooted and ran thru HFA and I had the LTE. Hopefully that's all it is. As for the other questions... umm, flashing TWRP thru odin gets you in the right direction for rooting. And as far as the ROMs go, anything by db_txs_db will work. Beyond that, starr53 ROMs work extremely well. Sorry if I ramble or speak in sentence fragments. Sometimes it happens. Best of luck and lemme know how it goes!
As far as I know firmwares only have one modern and if you have an SM-N910P that is not on the latest DQ15 update then it definitely worth fixing. Good luck
So I've had this for a few days now and I've noticed it's dropped connection quite a few times, and when, IF it reconnects without rebooting, it usually gets stuck on H+.
I'm currently on OOS 10.3.0. Tried a custom ROM, same issue. Tried regarding to 9.0.11, same issue. Bought a new SIM card, same issue. I'm thinking I have to get back to the T-Mobile 9.0.16 and send this back. I'm getting sick of this. Anyone have any ideas what the issue could be?
Sorry you are having so much trouble. This won't help, but my 6T global model (not T-mo) is the best reception phone I've ever had, at least on the ATT network.
It's hard to tell whether your problem is hardware based, something to do with the T-mo to global OS transition, or something else.
I have had it a full year and have no plans to swap it any time soon. I'm stock, unrooted (first time ever), and still on Pie for now, having deferred the update until it settles in a bit.
Good luck whatever you decide to do!
Sent from my ONEPLUS A6013 using Tapatalk
Signal is still dropping!
I'm having second thoughts about this phone. Two SIM cards and several calls to my cell provider and still no fix in sight.
I'm gonna see if the Swappa seller will send me a replacement.
Sounds like a problem with the hardware and pursuing a replacement is the right move. I had similar issue with a Samsung phone years ago.
Sent from my ONEPLUS A6013 using Tapatalk
Frankenscript said:
Sounds like a problem with the hardware and pursuing a replacement is the right move. I had similar issue with a Samsung phone years ago.
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
I thought that as well when I read the first post. However, I would try one more thing.
I would break out the MSM Tool, and completely flash back to 100% stock. Then I would test it again. The issue he is describing could actually be due to a mismatch in firmware partitions. Possibly that is, I dont know that for a fact. I would give it a try. That tool has fixed countless errors that I "may or may not have" induced by poking around.
Scott said:
I thought that as well when I read the first post. However, I would try one more thing.
I would break out the MSM Tool, and completely flash back to 100% stock. Then I would test it again. The issue he is describing could actually be due to a mismatch in firmware partitions. Possibly that is, I dont know that for a fact. I would give it a try. That tool has fixed countless errors that I "may or may not have" induced by poking around.
Click to expand...
Click to collapse
I did exactly that, back to T-Mobile firmware, and the issue still existed. So I returned the device.