Develop Bugs

Possible New Update in 3 Days to Fix Bricking Issues w/ Samsung Phones

For those of you with a Samsung WP7 phone, it looks like there are some reports now about an update coming in 3 days to resolve this issue. This was posted on wpcentral: http://ow.ly/416NN

4.2.2 upgrade for AT&T GN8

So I'm starting to get a bit frustrated that I'm sitting here with the i467 and have heard nothing on any upgrades. The screen freezing is getting tiring and without an unlocked bootloader, there is no ROMs for us to upgrade to and none in development. At least we have root, but that hasn't solved our screen freezing issue.
So, my question is, does anyone have a clue on when we can expect an upgrade to 4.2.2 or maybe even 4.3? I have been searching and Googling and haven't seen a word.
Am I the only frustrated one here? Sorry to vent.

There is nothing wrong with venting. Unfortunately things are what they are. Products that are not used by a lot of users (i.e., GN8 for AT&T) don't draw too much interest from developers for obvious reasons. And you are at the mercy of AT&T for ROM update (even though Samsung develops the code).
After learning from my experience with Verizon (for Galaxy 7.7), I decided to stay away from carrier-based tablets. Battery life is better and you could use any product specific ROM developed by Samsung. For network access in non-wifi zone, I use Verizon mifi.
Sorry but you will have to wait for your ROM. Hopefully it is around the corner.

I agree completely. Next time I'm going Nexus for my LTE tablet. Unfortunately they haven't been available with LTE and we're likely only getting the 10.1 version next.

esoh said:
So I'm starting to get a bit frustrated that I'm sitting here with the i467 and have heard nothing on any upgrades. The screen freezing is getting tiring and without an unlocked bootloader, there is no ROMs for us to upgrade to and none in development. At least we have root, but that hasn't solved our screen freezing issue.
So, my question is, does anyone have a clue on when we can expect an upgrade to 4.2.2 or maybe even 4.3? I have been searching and Googling and haven't seen a word.
Am I the only frustrated one here? Sorry to vent.
Click to expand...
Click to collapse
Finally signed up just to post my views.
Getting frustrated as well with the screen freezing, I too have searched for answers and have found nothing. We are certainly stuck waiting on ATT at this point. Is there anyway to complain to ATT or Samsung? What a crock of crap that this is still happening months after release.

kmeleon77 said:
Finally signed up just to post my views.
Getting frustrated as well with the screen freezing, I too have searched for answers and have found nothing. We are certainly stuck waiting on ATT at this point. Is there anyway to complain to ATT or Samsung? What a crock of crap that this is still happening months after release.
Click to expand...
Click to collapse
Complaining is useless. All I can say is that it does eventually happen. Usually 3-4 months after Samsung releases it.

dmunjal said:
Complaining is useless. All I can say is that it does eventually happen. Usually 3-4 months after Samsung releases it.
Click to expand...
Click to collapse
I get it that complaining is useless. What I was hoping was for any info that anyone might have on any possible update. Regarding your comment, does "it" refer to the wifi version? If that's the case, the if we say that 4.2.2 was released around August, that puts our version at Nov/Dec or so?
At Royaltiger, I remember you from the 7.7 boards. I also have the 7.7 (still have it, my wife uses it). I would love to go MiFi, but I appreciate having data built into the device. I could tether from my phone too, but sometimes I'm on a call and need data on the side. In any case, I agree with you and wish I could take myself out of the carrier versions, but there are always tradeoffs.
At dmunjal, I looked at N7 but like the 8" screen much better plus the Note capabilities. I take notes on my device all of the time. In any case, there are always 2 sides to everything. I just wish that we had more info from AT&T.

Ohh....I thought 4.2.2 upgrade for AT&T GN8 already out? no?
is this LTE version? what's your model number N5XXXX?

[Q] BT Headphone problem

Hello all,
today I updated to Lillipop and everythings works fine expect bluetooth. I listen music with my Sony MTR-10RBT and G3 but ofter occur frequently short interrupts while listing music. That sucks!
I made a whipe allready but nothing helped.
It´s a known porblem?? Or have someone a solution for that? Thanks.

hmmm this was a known problem for people who switched to ART while in Kitkat. Since Lollipop uses ART, this probably is the issue. I would have thought they'd fix this before an official update though.

LG Support Fix
I've have this problem and it's highly irritating since I use my bluetooth headphones for almost 3 hours every day. I've spoken to LG support and they have suggested the only fix is to roll back to kitkat, also if I send it in for "repair", it will take 14-21 days (might have said 14 days). They also "enticed" me with the fact that 5.0.1 for the G3 will fix the problem but I'm not sure that I even described the problem in sufficient detail before lollipop was firmly blamed as the problem.
I did mention that I don't have this problem with a Nexus 4, Nexus 5, Galaxy S5 all on lollipop 5.0.0 and I proceeded to get a lecture about how those phones are probably on 5.0.1 and that's why they work, they are not, but found it surprising at how LG dodged the fact that they hadn't a clue how to fix the problem. I feel like I've been let down by LG who seem uninterested, or non committed to fixing the problem and a support function that doesn't consider their user needs or how they customers use their products. Let's face it practically, how many people can go for 14-21 days without their phone for the sake of flashing a different OS
I knew I never should have moved away from my nexus 4 which was absolutely perfect in every way, thank goodness I didn't have to contact LG for any problems for that. I hope LG realise that as of now I just won't buy any of their products because of really poor customer service and unreasonable fix times that are outside the expectations of any user given the simple nature of the fix. As mentioned above, this problem existed on the LG G3 before lollipop and they couldn't be bothered to fix it then or even warn people not to upgrade because they hadn't fixed it. I'm just glad that I haven't had my new LG telly delivered because of the christmas rush, it's now been cancelled and I'll buy something else.
Rant over....

Original Note 7

Hey guys, so....
I don't know if I'm screwed or what. I have an original notes of a not a replacement 1. I got it about a week before The 1st recall. I returned to Verizon about 4 times in the past month and a half to try to get a replacement device [ with the new battery or whatever they did to the replacements ]. However every visit I was told they didn't have my color, gray, in stock. Now it's two months out and there's a total recall on it and I have an original device. I like the phone and wanted to keep it. What the heck do I do now? I've read through some of the threads about keeping the replacement note 7 or not, but I haven't seen anybody with an original one. Is your anybody else with an original note 7 that's going to keep it? And do you guys think that development will continue after all that's happened?
TLR - I still have an original note 7, not replaced (they never had my color), Do you guys think it's safe to keep it and do you think development will continue or die off early ?
Thanks for any advice. Man I really like this stylus ....

outamoney said:
Hey guys, so....
I don't know if I'm screwed or what. I have an original notes of a not a replacement 1. I got it about a week before The 1st recall. I returned to Verizon about 4 times in the past month and a half to try to get a replacement device [ with the new battery or whatever they did to the replacements ]. However every visit I was told they didn't have my color, gray, in stock. Now it's two months out and there's a total recall on it and I have an original device. I like the phone and wanted to keep it. What the heck do I do now? I've read through some of the threads about keeping the replacement note 7 or not, but I haven't seen anybody with an original one. Is your anybody else with an original note 7 that's going to keep it? And do you guys think that development will continue after all that's happened?
TLR - I still have an original note 7, not replaced (they never had my color), Do you guys think it's safe to keep it and do you think development will continue or die off early ?
Thanks for any advice. Man I really like this stylus ....
Click to expand...
Click to collapse
I'm in the exact same situation as you. I still have the original model Note 7 and have tried multiple times to exchange it for the "safe" model. At this point given the evidence, I believe that both models are equally safe (relatively). New models and old models catching on fire combined equaled around 90 cases out of about 2,000,000. I'm not sure if the failure rate on the updated models went down, but I feel that failure rate in general is about on par with other devices.
I have read about Apple phones in the past catching on fire. The difference is Samsung tried to be super responsible in this situation by taking ownership and the media and such has definitely exacerbated the situation. Apple never took ownership of any of the battery failures that happened with their devices, and mostly blamed it on the user using 3rd party accessories and such.
I may be wrong, but I believe the issue was blown out of proportion. I'm not saying the phone is safe, but I'm also not saying that this phone is way more unsafe than any of the others.
So, given the statistics and history of the two different models, if you disable fast charging on the device I believe the two different models are on equal ground as far as failure rates go. Which are higher than they should be but still fairly low.

jal3223 said:
. New models and old models catching on fire combined equaled around 90 cases out of about 2,000,000.
I may be wrong, but I believe the issue was blown out of proportion .
Click to expand...
Click to collapse
I even thought it was less than that and I'd take those odds, I don't think theyre too bad . However, I did think that my battery was kind of sub-par; this note 7 sucks down quite a bit of juice. I was hoping at the replacements had a better battery or longer-lasting one or something ????.

outamoney said:
I even thought it was less than that and I'd take those odds, I don't think theyre too bad . However, I did think that my battery was kind of sub-par; this note 7 sucks down quite a bit of juice. I was hoping at the replacements had a better battery or longer-lasting one or something ????.
Click to expand...
Click to collapse
to bad it doesnt even matter now lol.. u guys got v1 so the only way you can get a v2 is to try n find one from a third party

elliwigy said:
to bad it doesnt even matter now lol.. u guys got v1 so the only way you can get a v2 is to try n find one from a third party
Click to expand...
Click to collapse
Is v1 any more prone to failure than v2 though? They sourced the battery from a different manufacturer for v2 to try to head off the problem and there were still fire reports. I'm thinking that the failure rate is probably the same as any other phone, only with Samsung trying to be super careful by calling a recall, actually put themselves under a microscope in the media. They even said that they could not replicate the issue in their labs. V2 was just hoping that the battery was the problem. Which it seems that it wasn't.

jal3223 said:
Is v1 any more prone to failure than v2 though? They sourced the battery from a different manufacturer for v2 to try to head off the problem and there were still fire reports. I'm thinking that the failure rate is probably the same as any other phone, only with Samsung trying to be super careful by calling a recall, actually put themselves under a microscope in the media. They even said that they could not replicate the issue in their labs. V2 was just hoping that the battery was the problem. Which it seems that it wasn't.
Click to expand...
Click to collapse
they had a lot more reports with v1.. I think it was 90+ then v2 I think is under 10... not sure if time is the culprit or not however

Question 13 DP2 rollback on OEM locked tmo

Hello all, I've done weeks of researching online how to fix this issue but have not found a solution.
I'm on a TMobile pixel 6 pro, which is sim locked and OEM locked (trying to see if tmo will sim unlock for me).
I decided to try the android 12L beta as one of the "bug fixes" were Bluetooth fixes, long story short it didn't fix the problems I was having, i opted out of beta, downloaded the "update" installed, rebooted to a prompt of no operating system found and reinstalled the beta, I tried Google's flash tool, it stated in OEM locked (can't unlock even through fastboot). I then decided to try the 13dp2 and see if I can roll back afterwards, unfortunately I get a timestamp error..
Anyone have any ideas on what I can try or if they have had a similar issue that was resolved?

Start clearing caches.
Go to settings/apps/see all.

Without your bootloader unlocked, it is impossible to roll back.

This is weird. I opted out and got an update about 5 minutes later. Twas about 15mb iirc. It wiped the phone but it's been fine for me otherwise.
Also, this problem is not uncommon. Sadly. I guess some opt out updates were almost 500mb. From what I've read, these are the ones that are causing problems.

Larzzzz82 said:
This is weird. I opted out and got an update about 5 minutes later. Twas about 15mb iirc. It wiped the phone but it's been fine for me otherwise.
Also, this problem is not uncommon. Sadly. I guess some opt out updates were almost 500mb. From what I've read, these are the ones that are causing problems.
Click to expand...
Click to collapse
There is nothing weird. People fail to read, and then reap their mistakes. It clearly states on google flash tool website NOT TO use it if you bootloader is NOT unlocked. The only thing causing issues are users not reading, and expecting others to clean their mistakes. Rules of modifying software: 1. Read. 2. Read again. 3. Read it once more. If fails, go to step 1 again. 9 out of 10 times you are not the first user experiencing an issue, and it has already been replicated and a solution provided, but people once again.... FAIL TO READ.

teegraves58 said:
There is nothing weird. People fail to read, and then reap their mistakes...it has already been replicated and a solution provided, but people once again.... FAIL TO READ.
Click to expand...
Click to collapse
Just had to respond to this as I have noticed this becoming more of an issue in society that began to swell and expand in occurrence over the last ten years. Ironically enough, I just saw an article in my Google news feed that mentioned reading a lot on the cellphone lowers comprehension by causing overactivity in the prefrontal cortex.
Now, of course, I don't mean this as an insult to the OP. But everyone needs to make a few mistakes here and there so that they can learn from them and prevent the same thing from occuring again (and in this case the primary mistake would be a lack of reading).
Oh... And yeah... I tend to do a lot of reading on my phone and so my prefrontal cortex has probably been reduced to water lol.

My stance is clear: If your bootloader is locked, you don't belong in the beta program, you shouldn't be flashing developer previews, and your rescue options are limited or not timely. You are owed zero support for something you've been explicitly warned against.

Go to T-Mobile support on Twitter. You can chat with them and they will answer you pretty fast. Then ask them if you can have your device unlocked, that you are going to Europe for 3 weeks. And they will do it right away. No questions ask. They permanently unlocked my device. And I have not even paid for it.