i started a thread called " Data once lost wont re-connect" back in June
I still don't know what the problem is caused by but it's definitely lollipop related.
i have possibly tried every lollipop rom there is to try and it's always the same.
i'm a driver and cover the whole of Scotland, sometimes some obscure places
with no DATA signal..Once the exclamation mark was up then only a reboot would
sort out the problem and reconnect the DATA. I have tried 3 phones and they all
have the same problem. Now all the phones are on the Three network so it could
well be an incompatability between Three and lollipop??!
I have wiped the phones and put in 38r and 44s and i have not had to reboot
any of the phones this week so it looks like the problem is not apparent on KitKat.
I'm starting to enjoy the Oneplus once again !!!nearly had the samsung edge a couple
of weeks ago!!!
I was thinking that i might of been the only one with this problem untill it happened to the wife's
phone when on holiday.The daughter gave up her phone and went back to an iphone so tried hers on lollipop
and the same problem .
Hope this might help somebody out there it's been driving me insane and although i have had to forget lollipop
and go back to KitKat the phone is now back to being usable and i get my emails and whatsapp when i'm supposed to
Paul
I use Calkulin's ROM, currently on the latest, with EE and don't get this problem.
I drive a lot for my job as well, so would expect to see this if it existed.
I don't know what it could be. It all points to the Three network but why does it not happen on KitKat? There must be some issue with Three/Oneplus and Lollipop, especially as the problem is there on all three phones i have tried. After months of trying Lollpop ROMS and different Kernals i am totally stumped, but revert the phones back to 38r or 44s and everything is ticketyboo !!
I'd be tempted to put one of the phones on Calkulin's ROM, then stick an EE SIM card in (just get a PAYG for testing) and compare the results.
I presume you have double-checked the APNs are definitely the same?
Related
5/19/2013 Update: The bug might be dead! Like for real this time. See this post, post number 14 in this thread with an explanation of what to do.
10/25/2012 Update: TRY THE LATEST BUILDS OF BRUCE'S CM10 STARTING WITH THE 10/25 VERSION!
Bruce has made a change that helps differentiate between the regular data stream and the MMS data stream in an attempt to see if that was what was causing the instability issue. This is only on Bruce's CM10 Kang as of 10/25. If you are only another CM ROM, flash Bruce's (even if just for a minute or two) and see if the data bug goes away. Please report back if it did!
If this does cure it, I'm sure Bruce will share the sollution to all other devs and your favorite other AOSP ROm will have the cure shortly.
Updated 10/24/2012
This is a detailed description of the 6 million or so things that various people have attempted to do in order to rectify the blinking data connection problem plaguing T Mobile USA users on AOSP ROMs for the Sensation. This issue is non existant in Sense based ROMs.
The problem has something to do with how the Sensation authenticates itself with the T Mobile Data Network. It's not based on the cell towers as voice calling is unaffected. The theory is that the AOSP framework lacks the proper authentication certificates for part of the data network and when the phone is routed to that part of the network, it gets kicked off teh network, then continually retries to connect.
This was and issue on the Sense Gingerbread Stock ROM in 2011 but T Mobile and HTC patched it. All Sense ROMs are free from this bug. But no one knows what exactly the patch was so AOSP ROM's have not been able to be cured yet.
Short version....
Problem started for me on Bruce's CM10 rom. But it's reported on all CM10 variants and most CM9 ROM's as well.
One day I noticed that data wasn't connecting well. It would blink on and off. Sometimes it would stay on, but if I turn it off then right back on, it might go back to blinking.
The problem exists on all AOSP roms (AOKP, CM9, all versions of CM10) even after full wipes and restores of known working nandroids.
Cell signal for voice calls works perfectly. No problems whatsoever. So the phone is connecting to T Mobile. It just won't get data.
Long version....
To fix this I've tried the following...and how each does or doesn't work.
Switch to 2G networks only and switch back. Problem remains, and still blinks E on the EDGE networks rather than being solid on them.
Updated the radio. Problem remains.
Updated the entire firmware package. Problem remains.
Superwipe and flashed Sense, verify data works well. Then regular wipe and flash a fresh install of CM10. Problem remains.
Flashed clean version of CM10 and fixed permissions. Problem remains.
Made calls from the phone. Some people have reported that this helps temporarily.
Sent myself a text message. Some people have reported that this helps temporaliy.
Turn on airplane mode for a minute then go back to normal. Some people have reported that this helps temporarily.
It's not related to Wifi at all because I've created the error on fresh installs of CM10 before ever turning Wifi on.
Formatted SD card. Problem remains (and just to be sure I got the error while the blank formatted SD was removed from the device)
Checked the APN's 100 times. They are correct.
Spent an hour on the phone with T Mobile. Their tech said everything looked good on their end. He cleared the SIM and reactivated it. Problem remained.
Other people have gotten new SIM cards and found that while they helped right away, the problem eventually came back.
The only things that have shown any help to multiple users are in bold above. There are various reports of 100 other 'fixes' that people swear fixed the problem for them. But all of them involved the phone disconnecting from the network and reconnecting. That appears to be the key to get data working again temporarily. Making calls and sending yourself text messages also forces authentication on the T Mobile network without breaking the original connection.
If you want more details or want to review the logs to see if you can figure it out, logcats of the problem are located in this post! Click here for logcatty goodness!
Here is the real kicker....
Everyone once in a while...it connects. And once it's connected it'll stay connected until I turn the connection off or reboot the phone. Then it'll go back to blinking in and out when I try to turn it back on.
Just another note, the data is finicky on my old LG G2x also on TMobile with AOSP based ROMs, talk works, but cell data won't come back after going into airplane mode and out, until a reboot. It works fine on official TMobile ROMs. I suspect there may be some proprietary cell data negotiation between handset and Tmobile towers that AOSP code doesn't have.
Whyzor said:
Just another note, the data is finicky on my old LG G2x also on TMobile with AOSP based ROMs, talk works, but cell data won't come back after going into airplane mode and out, until a reboot. It works fine on official TMobile ROMs. I suspect there may be some proprietary cell data negotiation between handset and Tmobile towers that AOSP code doesn't have.
Click to expand...
Click to collapse
Okay here's an update on this for anyone who finds this thread through a search or Google or something....I'll try to describe this using the simplest terms possible so those of us who aren't cell tower engineers can understand it. (And I assume that's most of us, including me!)
The latest running theory is that the issue occurs due to the way the phone is handed off from 1 tower to another.
As you move your phone is handed off from one tower to the next. You get unregistered with tower 1 and reregistered with tower 2. That's normal.
However if you are within range of 2 towers you can't be on both. You have to be registered with 1, and that's supposed to be the stronger one. But AOSP ROMs lack a T Mobile certificate that authenticates which tower is supposed to have priority. So when the data is blinking you are getting bounced between 2 towers because the phone is trying to register with both.
The latest version of Bruce's CM10 ROM (Dated 10/10/12 and with TMOUS DATA in the rom name on the download page) supposedly includes patches that fix how this authentication works. And I only say 'supposedly' because the patches have only been up for about 12 hours so the jury is still out on how well it works. Personally I've been on it all day today and haven't had the data issue yet. But it can be days in between seeing it. So it'll take a while to know for sure that it's fixed.
If this turns out not to be the exact cause of the problem, it's something similar and a final sollution should be found soon.
Update: This have never been substantiated, and several users with the bug have reported knowing for a fact that they experience the problem when in range of only 1 tower.
Hi,
I have noticed with JB ROMS that you get 7 or 8 APN's,most of which do not apply to me.
Have you tried (making a note of your one first) and deleting all the APN's
Reboot,and just install yours.
malybru said:
Hi,
I have noticed with JB ROMS that you get 7 or 8 APN's,most of which do not apply to me.
Have you tried (making a note of your one first) and deleting all the APN's
Reboot,and just install yours.
Click to expand...
Click to collapse
That's one of the 1000 things that's been tried, to no effect. If he APN is set to the correct one the extra APN's are ignored.
Nothing that you do within the phone can cure the problem. At most, forcing the phone to re-register with the tower is the only thing that can help, and that will be temporary if it works at all.
The best bet now is to hope that Bruce fixed it with his latest additions to CM10 now that we understand what the actual problem is (or at least that we think we do)
Update....
T Mobile data is still broken. It has not been fixed yet. The latest theory may just be one more in a long line of theories that turned out to be wrong.
There are days when I really hate this phone.
Thanks for the update. I've been monitoring that thread occasionally, but it has way too much traffic for me to keep up. I was close to switching to it, but I need good battery life and reliable cell service over any smoothness benefits of JB, which is why I'm sticking with HyperNonSense ICS for now.
been experiencing this issue for a couple months myself. currently stuck in a no data bout as we speak. i'm wondering if it has anything to do with the amount of data we've used. i noticed this last bout started right around the time i passed 5gb. should also be noted i'm on the unlimited 4g plan and tether like crazy. i guess i'll know if the problem persists until my next billing cycle. for now i'm stuck with a sense nandroid and crack flashing aosp daily to see if it's fixed.
cpittman said:
been experiencing this issue for a couple months myself. currently stuck in a no data bout as we speak. i'm wondering if it has anything to do with the amount of data we've used. i noticed this last bout started right around the time i passed 5gb. should also be noted i'm on the unlimited 4g plan and tether like crazy. i guess i'll know if the problem persists until my next billing cycle. for now i'm stuck with a sense nandroid and crack flashing aosp daily to see if it's fixed.
Click to expand...
Click to collapse
I have tried the SIM swap fix. And that has apparently worked. I've been using in good for about the last 6ish hours without any problems. :good:
So i'd give that a shot if your willing.
I've been using CM10 KANG since it was available for HTC sensation. Never had the data blink issue. Recently, my phone started to have this issue. Data would simply not connect with CM10 or CM10.1 with any radio/firmware combination. I also noticed that when I travel to work, i get data say after 10 miles away from my home and it continues to work after coming back home. However, after restarting the phone, i hit the blink problem again. Wondering if its because of some cell tower maintenance/upgrade near my area.
So I was on bruce's ROM until a week ago and this never happened while on his ROM. Just upgraded to albinoman's ROM and this started happening. I have to send myself a MMS picture to get it back again. Hope this helps
Fix
Ive had this problem on and the only thing that seems to help is flashing a new ROM but then a few weeks later it returns... I realized that this only happens when I try to send an MMS message or attempt to receive them. I don't know how to stop receiving an MMS but just delete the picture message you're trying to send and your data should stop blinking on and off. Can't guarantee it'll work for you but it worked for me! GL!!
It appears as though this stupid annoying silly obnoxious bug has finally been squished, sprayed with 3 cans of Raid, and its' mangled corpse then burned to a crisp...I hope.
3 weeks ago W1ldFl0wer brought this fix to Albinoman's attention...
In the build.prop under phone>system was the following line....
ro.telephony.ril.v3=datacallapn,signalstrength
This line appeared like this on all AOSP roms for the sensation.
The fix was to add skipbrokendatacall to the line so it looked like this....
ro.telephony.ril.v3=datacallapn,signalstrength,skipbrokendatacall
Save the file, reboot, and data should spine right up and work fine. So far the peopl ewho have run into the data bug have implimented this change and BOOM, data fixed.
So if you use any AOSP ROM 4.0, 4.1, or 4.2 other than Albino's CM10.1 Kang just add skipbrokendatacall to that line and see if it fixes it. Only do this if you on in the US on T Mobile's network. If you are in parts of Europre making this change will screw up your data.
If you are using Albinoman's CM10.1 Kang ROM, he has already included this line in the build.prop for you. You just have to activate it. About 30 lines into the build.prop is the new line that reads...
#ro.telephony.ril.v3=datacallapn,signalstrength,skipbrokendatacall
Just delete the # in front of that line. (The # makes the ROM skip the line when loading everything, but lets it stay in the file so you can read it. Deleting the # means that the phone will read that line when it reboots.) Then go up to the line that says the same thing without skipbrokendatacall and delete that line entirely. Save the file and reboot. If you don't delete the original line without skipbrokendatacall, your phone will go haywire, data might not work at all, and you might inadvertantly trigger Z Day. So if you're not ready to fight in the zombie apocolypse, only leave one of those lines in the build.prop.
Hope this cures it for everyone! Again, don't make this change if you live outside the USA or are not on T Mobile's network! Doing so on other networks in other parts of the world could make things worse for your phone!
Here is the link to the post where W1ldFl0wer informed Albinoman of this fix.
http://forum.xda-developers.com/showpost.php?p=40755845&postcount=9003
I don't think W1ldFl0wer invented the fix, but he certainly is the one who made it public to Sensation users so go to that post and thank him/her bcause I might finally be able to stop obsessing over this stupid bug because of this user!!! :good:
Calls drop often. Usually within the first minute, and then every time when Im calling back after 10sec. The phone itself does not lose signal. Strange thing is, if I'm getting phone call after first/second drop, phone continues connection without problems... But Only when Im receiving a phone call not when Im trying to re-call someone.
- I tried replacing my sim and the issue persists. No problems with other phones using this Sim (even in the same locations).
These are pretty annoying issues. Anybody else experiencing them? Is there a different radio I can try for the phone? Is there any log I can access showing a reason for the call drop, or any trouble shooting I can do? This seems to be independent of WCDMA Only/Preferred/GSM/WCDMA (Auto) settings. Or if, how to change these settings?
Note: This has nothing to do with the network. I've been with the same company (Orange Europe) for about 2.5 years, and have never had this happen before. This has been consistent since I got my OnePlus (about 1 week ago)
That's true. I'm experiencing this as well for quite some time now. At first I joked and said: Hey, the NSA joined our conversation.....again. But after some time it really annoys me. This has nothing to do with the ROM or kernel as I have tried out various combinations. What I found out is that it got better after I returned to stock CM 11s with stock kernel. But it's not gone completly.
Honestly I neither know how to fix it nor what is causing the problem. Try to reflash the CM11S 25R firmware and see if it gets better. I think something is wrong with the modem software since CM11S 22R,25R and CM11 builds are using the same modem software. Maybe the announced update for the end of this month or early next month will fix this. I really hope so because a phone which is not able to hold a call, can't be considered as a real phone.
Oh im pitty You, If You'll get something just please let me know. Any advices or help will be appreciated. Maybe waiting for new CM relase will solve the problem, I do rly like this OS even with so many bugs... there is always an option. Move to stock 4.4 published by OP on official website.
Anyone else facing the same issue? Was there ever a fix for this issue? I'm on 38R and still encountering this issue
Same here.
See this thread for answers and work around. No solution as of yet.
http://forum.xda-developers.com/oneplus-one/help/dropped-calls-weak-lte-signal-t2916659
Hi!
My girlfriend owns an HTC One S which has everything on stock, indeed it has JB 4.1.1 installed. It has suffered "helicoptering" since a long time ago (just to note it).
A couple of days ago she told me that her One S wouldn't connect to her home Wifi network... So I took a look and realised that One S' wifi was enabled, but every saved connection was out of coverage...
So what do you suggest me to do? Perhaps to flash CM12 (or any Sense rom)? The phone is 3 years old and out of warranty (of course). Should I contact HTC's service?
Thanks!
russellhoff said:
Hi!
My girlfriend owns an HTC One S which has everything on stock, indeed it has JB 4.1.1 installed. It has suffered "helicoptering" since a long time ago (just to note it).
A couple of days ago she told me that her One S wouldn't connect to her home Wifi network... So I took a look and realised that One S' wifi was enabled, but every saved connection was out of coverage...
So what do you suggest me to do? Perhaps to flash CM12 (or any Sense rom)? The phone is 3 years old and out of warranty (of course). Should I contact HTC's service?
Thanks!
Click to expand...
Click to collapse
This is a random issue and it's happening also on latest ROMs (Lollipop 5.1.1 for ex). I usually restart the phone or turn on/off wifi several times. You could try flashing a newer ROM but giving the age of the device it could be a better choice to replace it with a newer device. HTC Service Center will just reset it to factory and maybe they'll flash a newer radio/firmware (but those were not officially updated for years so they'll be old also) and will take you some money...not worth it in my opinion
Rapier said:
This is a random issue and it's happening also on latest ROMs (Lollipop 5.1.1 for ex). I usually restart the phone or turn on/off wifi several times. You could try flashing a newer ROM but giving the age of the device it could be a better choice to replace it with a newer device. HTC Service Center will just reset it to factory and maybe they'll flash a newer radio/firmware (but those were not officially updated for years so they'll be old also) and will take you some money...not worth it in my opinion
Click to expand...
Click to collapse
I've unlocked it and flashed TWRP today, and after the first boot WIFI connections are ready! Now, I'm gonna flash CM 12.1 and say goodbye to all the bloatware.
Thanks for your help
russellhoff said:
I've unlocked it and flashed TWRP today, and after the first boot WIFI connections are ready! Now, I'm gonna flash CM 12.1 and say goodbye to all the bloatware.
Thanks for your help
Click to expand...
Click to collapse
Unfortunately, WiFi connections lasted some minutes... It's weird, it's like programmed obsolescence... Is there any way to make wifi work (like soldering some contacts as in One X)?
Ever since updating to 5.1.1 via OTA update on my AT&T Galaxy Note Edge SM-N915A, I have had numerous issues. The phone lags/freezes often at best, but also crashes and reboots randomly. Worse yet, it has gotten into a boot loop a few times. I have factory reset and cache-wiped numerous times and even flashed a clean 5.1.1 via odin and still have the same issues. Apparently 5.0.1 or 4.4.4 cannot be flashed via Odin once 5.1.1 is installed and I can confirm this is true as I have tried.
Is anyone else having these issues? I have seen similar reports from the Note 4 forums but they seem to be getting new firmware updates to fix the issues. My firmware is N915AUCU2COI2 and is the latest available for the SM-N915A as far as I can determine.
try to flash kernel find on xda.
sagelwwa said:
Ever since updating to 5.1.1 via OTA update on my AT&T Galaxy Note Edge SM-N915A, I have had numerous issues. The phone lags/freezes often at best, but also crashes and reboots randomly. Worse yet, it has gotten into a boot loop a few times. I have factory reset and cache-wiped numerous times and even flashed a clean 5.1.1 via odin and still have the same issues. Apparently 5.0.1 or 4.4.4 cannot be flashed via Odin once 5.1.1 is installed and I can confirm this is true as I have tried.
Is anyone else having these issues? I have seen similar reports from the Note 4 forums but they seem to be getting new firmware updates to fix the issues. My firmware is N915AUCU2COI2 and is the latest available for the SM-N915A as far as I can determine.
Click to expand...
Click to collapse
Hi. Regards. also I have the same problem. Now 5.0.1 and 5.1.1, the phone note n915a edge is frizz me and every time I restarted. I'm going through the same thing you and if you've not been able to find solution that can share. thanks
mtayabkk said:
try to flash kernel find on xda.
Click to expand...
Click to collapse
Wouldn't that require ROOT access? The AT&T variant has a locked bootloader, so no root.
sagelwwa said:
Ever since updating to 5.1.1 via OTA update on my AT&T Galaxy Note Edge SM-N915A, I have had numerous issues. The phone lags/freezes often at best, but also crashes and reboots randomly. Worse yet, it has gotten into a boot loop a few times. I have factory reset and cache-wiped numerous times and even flashed a clean 5.1.1 via odin and still have the same issues. Apparently 5.0.1 or 4.4.4 cannot be flashed via Odin once 5.1.1 is installed and I can confirm this is true as I have tried.
Is anyone else having these issues? I have seen similar reports from the Note 4 forums but they seem to be getting new firmware updates to fix the issues. My firmware is N915AUCU2COI2 and is the latest available for the SM-N915A as far as I can determine.
Click to expand...
Click to collapse
I've been experiencing the same issues since 12/19/15. I too have the N915A... and it has worked just fine up until that day. I noticed while I was out xmas shopping that it was rebooting a number of times while i stood in line waiting to check out of the store. I did not want to be that guy in line pulling apart an electronic device so i waited until I got to the car. Pulled the battery, she was a hot mess, then once it was cool I re inserted and powered the phone back up only to find it to be really laggy, a number a apps were crashing on without me touching them, random reboots, need to pop the battery, SD, and SIM to restart the phone without it getting hungup on the boot routine.
I recently used ODIN to load 'stock" 5.1.1. firmware but no luck. Not entirely sure that its N915A firmware, found it from other threads on the forum. Before knowing we could not go back to previous version, I took a whack at going back to those as well. So far I've reset the phone probably 7 or 8 times with a fresh OTA firmware install and only installing a few apps like Facebook, RSA VPN client and Team Viewer to keep variables minimal.
Ever since xmas day i stopped trying and been trolling the web for support only to here that the N915A has no root yet and other unavailable mods thus far . I have not tried to do anything else yet from a programming standpoint. I put the phone into developer mode, toggled some settings for the CPU and GPU in there so that they ran independently.Setup to be notified when an app crashed in the background. Downloaded Nova Launcher to avoid TouchWiz as I've heard that can be buggy with 5.1.1. So far the phone has been working somewhat normal. No random restarts, however if I restart it myself i may need to remove the battery for a minute to get it going again. The battery seems to be draining faster than it should, least of my worries for now. If i just let the phone do its things without trying to be a few thoughts ahead of it, it seems to process just fine.
Oddly its improving, I'm not sure why. Also, not pleased with it either but its better than having a brick atm. Intend to keep trolling the webs for more solutions until a root is dev'd and nursing this thing until it either hits the bucket again or for some weird reason gets better on its own....
Lil Grim said:
I've been experiencing the same issues since 12/19/15. I too have the N915A... and it has worked just fine up until that day. I noticed while I was out xmas shopping that it was rebooting a number of times while i stood in line waiting to check out of the store. I did not want to be that guy in line pulling apart an electronic device so i waited until I got to the car. Pulled the battery, she was a hot mess, then once it was cool I re inserted and powered the phone back up only to find it to be really laggy, a number a apps were crashing on without me touching them, random reboots, need to pop the battery, SD, and SIM to restart the phone without it getting hungup on the boot routine.
I recently used ODIN to load 'stock" 5.1.1. firmware but no luck. Not entirely sure that its N915A firmware, found it from other threads on the forum. Before knowing we could not go back to previous version, I took a whack at going back to those as well. So far I've reset the phone probably 7 or 8 times with a fresh OTA firmware install and only installing a few apps like Facebook, RSA VPN client and Team Viewer to keep variables minimal.
Ever since xmas day i stopped trying and been trolling the web for support only to here that the N915A has no root yet and other unavailable mods thus far . I have not tried to do anything else yet from a programming standpoint. I put the phone into developer mode, toggled some settings for the CPU and GPU in there so that they ran independently.Setup to be notified when an app crashed in the background. Downloaded Nova Launcher to avoid TouchWiz as I've heard that can be buggy with 5.1.1. So far the phone has been working somewhat normal. No random restarts, however if I restart it myself i may need to remove the battery for a minute to get it going again. The battery seems to be draining faster than it should, least of my worries for now. If i just let the phone do its things without trying to be a few thoughts ahead of it, it seems to process just fine.
Oddly its improving, I'm not sure why. Also, not pleased with it either but its better than having a brick atm. Intend to keep trolling the webs for more solutions until a root is dev'd and nursing this thing until it either hits the bucket again or for some weird reason gets better on its own....
Click to expand...
Click to collapse
I've heard it's a problem of upgrading to lollipop. this model has errors. hopefully at & t throw a actulizacion soon to correct these improvements
ltindi32 said:
I've heard it's a problem of upgrading to lollipop. this model has errors. hopefully at & t throw a actulizacion soon to correct these improvements
Click to expand...
Click to collapse
So that's it then? Is there really no way whatsoever to go back to 5.0.1 or even 4.4.4 kitkat from 5.1.1? I've been trying to do it for a while now but I'm new to this Odin downgrading thing.
sagelwwa said:
Ever since updating to 5.1.1 via OTA update on my AT&T Galaxy Note Edge SM-N915A, I have had numerous issues. The phone lags/freezes often at best, but also crashes and reboots randomly. Worse yet, it has gotten into a boot loop a few times. I have factory reset and cache-wiped numerous times and even flashed a clean 5.1.1 via odin and still have the same issues. Apparently 5.0.1 or 4.4.4 cannot be flashed via Odin once 5.1.1 is installed and I can confirm this is true as I have tried.
Is anyone else having these issues? I have seen similar reports from the Note 4 forums but they seem to be getting new firmware updates to fix the issues. My firmware is N915AUCU2COI2 and is the latest available for the SM-N915A as far as I can determine.
Click to expand...
Click to collapse
I also have the AT&T Galaxy Note Edge SM-N915A. Ever since I updated via OVA this June 2016 it has been freezing/rebooting on its own/crashing apps. I have found 3 SM-N915A roms but cannot revert back to these previous builds. I have tried KEIS3 via Samsung to reflash firmware but it wont recognize my device name. After 2 weeks of crashing the phone is now a joke, when it once was king. It was such an awesome phone when it was released. Now I must lay it down to sleep. I guess I will get the Note 7 Edge which should be released this August.
I just wanted to express my frustration over ATT Branded Phone and will not be buying their branded phones anymore. I will be buying international versions or unlocked phones since ATT screwed me on this one.
harondaddy said:
I also have the AT&T Galaxy Note Edge SM-N915A. Ever since I updated via OVA this June 2016 it has been freezing/rebooting on its own/crashing apps. I have found 3 SM-N915A roms but cannot revert back to these previous builds. I have tried KEIS3 via Samsung to reflash firmware but it wont recognize my device name. After 2 weeks of crashing the phone is now a joke, when it once was king. It was such an awesome phone when it was released. Now I must lay it down to sleep. I guess I will get the Note 7 Edge which should be released this August.
I just wanted to express my frustration over ATT Branded Phone and will not be buying their branded phones anymore. I will be buying international versions or unlocked phones since ATT screwed me on this one.
Click to expand...
Click to collapse
I ended up being only days left in warranty and getting a replacement. Then a few months later I switched to T-Mobile and got the SM-N915T. So far so good and just OTA updated to Android 6.0. Only negative is T-Mobile's coverage in my area is poor, but WiFi calling, unlimited data (speed limited), and unlimited Binge On media streaming at full speed are great positives. T-Mobile Tuesdays is pretty cool too I must admit :good:
Same problem on SM-N915F even persisting after the new 6.0.1 update
Me too, my note edge N915G get restart constantly after ota update to 6.1 i try to flash with odin but always fail..
Dear Forum,
My wife acquired the S6 last week and I helped her through the initial stuff of creating backup from her previous S3.
All went fine, all was where it should have been, nothing missing, great stuff.
The "Software Upgrade" utility inmediately tells you that there's an upgrade available to MM and I thought to myself "Well, that phone is from November 2015, the upgrade couldn't harm, in fact, it usually improves things", right ?
My wife asked if there was going to be an issue with the upgrade and if it would be possible to downgrade again....
So, I went to Kies3, which directed me to Smart Switch and I began the upgrade. After it was done I did a factory reset and the phone booted, all ok...so far...
I gave the phone to my wife (an avid Instagrammer) and she told me : this is not working, what have you done to my phone ? The nightmare begins for me...
1. Apparently the wifi signal was quite poor (even if sitting in front of the router). It takes some time to connect, which means that pages like Instagram, tumblr, facebook, even searches in Chrome take an eternity to load ! It didn't happen on version 5.1 apparently on her S6 (which I doubt) , and on her S3 it worked flawlessly. I have to say though that I experience the same issue on my current Z9 Max. I believe that the router (Glass Fiber connection) is quite old and not up to new standards, that's why it hangs with new phones. I only have wifi issues at home, any other router I connect to (Bars, brother home, mother home, at work) work perfectly fine. I will change the router as soon as I can, but I firmly believe it has to do with new hardware the router is not used to.
2. Mobile Data
They did not work at all... The look on my wife's face said it all "What the Eff have you done to my fresh new phone" ??? I'm asking this to myself also now...why did I upgrade this thing ? In the end I managed to get mobile data, simply by trying 3G, 2G, individual options and finally 4G worked again. But yeah, what do you do at home with a smartphone if you don't have an internet connection ?
Why did Samsung push-out this upgrade, why are they forcing messages onto the user that an upgrade is needed ? I mean, I've been using Android for quite some time and I've flashed many many Roms, installed software upgrades, I never ever faced any issue on my HTC or Nubia, all worked fine after an upgrade, at least mobile data were working always. Samsung is supposed to deliver top notch phones with top notch upgrades...how can they possibly offer/push something that might cause more trouble than joy ?
I assume a FW upgrade is needed as well, why don't they warn ?
Now the question.... if 5.1 worked fine, is there any possibility to downgrade the S6 to a previous Android version ? Would it be possible with Odin ?
I got an angry wife sitting at home , which is convinced that I only wanted to play around and didn't want to help her.
Have you guys experienced problems after upgrade to MM on the S6 ?
Cheers,
Ken