Related
I'm rooted and have been for a while. I just switched to Team-Nocturnals_Shoooter_RLS3.1.1 rom. I have a problem where sometimes I can't recieve messages on the stock messaging app, I notice this because I have Gingerbread Ghostly constlantly running and that app recieves the message but not the stock messging app. I also don't recieve calls every once in a while.
The first time I ever noticed this was about a month ago when I was running a Going-Green rom but it only happened when i switched to that Rom, never happened before then. So I upgraded my radio to 2.15.00.08.08 because that Rom ran so smoothly on my phone and wanted to keep it. The problem kept happening so i switched to another Rom and it happened on that one as well.
I've switched between different roms probably 5 to 8 times and I still don't recieve messages or calls sometimes and I don't know how to fix it. A while back, user on here was nice and tried helping me out by telling me it could have to do with Google voice, so i completely deactivated Google voice and its still happening.
I would really appreciate any input and info you may have on this and please help if you can. Also can I downgrade my radio? Would that help? Thanks.
What radio version do you have? The newer radios will not allow you to downgrade. But then again, you wouldn't want to downgrade your radio anyway.
When I had this issue it was because Google Voice completely F'ed my phone. My messaging wouldn't work no matter what ROM I flashed. I ended up fixing the phone by accident as I was unrooting it to take it into the store. Here is a link on what I did with mine.
http://forum.xda-developers.com/showpost.php?p=18399552&postcount=2
Follow that process and fully unroot your phone back to bone stock. Once you've got it back to bone stock try sending yourself a message and see if it works. If it does then feel free to unroot once again and reflash whatever ROM you wish. If it still doesnt work then, while unrooted, make sure your phone has accepted all of the OTA updates from Sprint and then update your profile. If it STILL doesnt work then give Sprint tech support a call and ask them what the ## code is to reset your phone's network signal. I wrote it down somewhere from when I tried it on mine but I cannot find that damn piece of paper. If NONE of that works for you then you may have to take it into Sprint. Good news though, it's already fully unrooted so you don't have to worry about the risk of the techs denying you.
Let me know if any of this helps.
I just switched to decks gingerbread rom which is the first time I've gone without sense and I've had no problems so far. Could it have to do with sense?
Sent from my PC36100 using Tapatalk
Doubtful it is sense. What rom were you using before?
I doubt it was Sense because I was having the same problem with an AOSP ROM.
I was using a lot of different sense 3.0/3.5 roms like gruesomewolfs Rom, hybrid beta 8.5, sinister Rom, I've tried almost all.
Sent from my PC36100 using Tapatalk
I'm trying synergy non-godmode for the first time now and will see if I have problems with it. It doesn't make any sense to me at all why I keep having these problems.
Im trying to avoid un-rooting then re-rooting but will do it if that fixes it.
Sent from my PC36100 using Tapatalk
Concordium said:
What radio version do you have? The newer radios will not allow you to downgrade. But then again, you wouldn't want to downgrade your radio anyway.
When I had this issue it was because Google Voice completely F'ed my phone. My messaging wouldn't work no matter what ROM I flashed. I ended up fixing the phone by accident as I was unrooting it to take it into the store. Here is a link on what I did with mine.
http://forum.xda-developers.com/showpost.php?p=18399552&postcount=2
Follow that process and fully unroot your phone back to bone stock. Once you've got it back to bone stock try sending yourself a message and see if it works. If it does then feel free to unroot once again and reflash whatever ROM you wish. If it still doesnt work then, while unrooted, make sure your phone has accepted all of the OTA updates from Sprint and then update your profile. If it STILL doesnt work then give Sprint tech support a call and ask them what the ## code is to reset your phone's network signal. I wrote it down somewhere from when I tried it on mine but I cannot find that damn piece of paper. If NONE of that works for you then you may have to take it into Sprint. Good news though, it's already fully unrooted so you don't have to worry about the risk of the techs denying you.
Let me know if any of this helps.
Click to expand...
Click to collapse
About a week ago I switched to a stock Rom and then called Sprint and they updated the profile and everything and used the ##782?? or whatever number that is lol.
Sent from my PC36100 using Tapatalk
Call sprint from a secondary phone, tell them that you are getting very delayed text messages and not receiving calls at random. have them update your profile. If that doesnt work have them reprogram your phone. had to reprogram mine when i was receiving text messages 5 hours after they were sent
lmoore55 said:
Call sprint from a secondary phone, tell them that you are getting very delayed text messages and not receiving calls at random. have them update your profile. If that doesnt work have them reprogram your phone. had to reprogram mine when i was receiving text messages 5 hours after they were sent
Click to expand...
Click to collapse
What do you mean by them reprogramming my phone? Do i need to return to stock and unroot for them to do that or can I use a stock rooted rom?
Sent from my PC36100 using Tapatalk
Concordium said:
What radio version do you have? The newer radios will not allow you to downgrade. But then again, you wouldn't want to downgrade your radio anyway.
When I had this issue it was because Google Voice completely F'ed my phone. My messaging wouldn't work no matter what ROM I flashed. I ended up fixing the phone by accident as I was unrooting it to take it into the store. Here is a link on what I did with mine.
http://forum.xda-developers.com/showpost.php?p=18399552&postcount=2
Follow that process and fully unroot your phone back to bone stock. Once you've got it back to bone stock try sending yourself a message and see if it works. If it does then feel free to unroot once again and reflash whatever ROM you wish. If it still doesnt work then, while unrooted, make sure your phone has accepted all of the OTA updates from Sprint and then update your profile. If it STILL doesnt work then give Sprint tech support a call and ask them what the ## code is to reset your phone's network signal. I wrote it down somewhere from when I tried it on mine but I cannot find that damn piece of paper. If NONE of that works for you then you may have to take it into Sprint. Good news though, it's already fully unrooted so you don't have to worry about the risk of the techs denying you.
Let me know if any of this helps.
Click to expand...
Click to collapse
Oh i have 2.15.00.08.08 radios. I used the all in one zip which has the newest radio, wimax, and something else.
Sent from my PC36100 using xda premium
scottypeterson said:
Oh i have 2.15.00.08.08 radios. I used the all in one zip which has the newest radio, wimax, and something else.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
It's always best to flash each of those separately. Flash the radio and then reboot the phone. Then flash the wimax and reboot the phone. And so on and so on. I flashed one of those all in one packages and I had problems with getting everything set properly. So I did them one by one and they worked flawlessly. I then read, afterwards, that its best to do them individually. I'm not exactly sure why....but that's what has worked best for me and apparently for the majority of other people. So I recommend going back and flashing each of those individually to make sure they all installed correctly.
Concordium said:
It's always best to flash each of those separately. Flash the radio and then reboot the phone. Then flash the wimax and reboot the phone. And so on and so on. I flashed one of those all in one packages and I had problems with getting everything set properly. So I did them one by one and they worked flawlessly. I then read, afterwards, that its best to do them individually. I'm not exactly sure why....but that's what has worked best for me and apparently for the majority of other people. So I recommend going back and flashing each of those individually to make sure they all installed correctly.
Click to expand...
Click to collapse
Ok thanks. Ill definitely get that a try and flash them separately. Thanks for your help again. Its greatly appreciated.
Sent from my PC36100 using xda premium
Dang, after reflashing the radios yesterday im still having the same problems. Looks like i may be un-rooting then re-rooting if i cant do something else that coukd fix it.
Sent from my PC36100 using xda premium
I was also just thinking this this started happening when i switched to Going-green rom but after i partitioned my sdcard and started using dtapps2sd. Is it possible that dtapps2sd could be messing with my phone to where i miss calls and messages?
Sent from my PC36100 using xda premium
I ended up getting a replacement evo 4g and now this phone is not receiving all the text messages either. I am using ghostly sms so it lets me know when i miss a message. I also tried using Handcent messaging app from the market and it misses the messages too. Anyone have any idea why?
Sent from my PC36100 using xda premium
Literally every time i check for software updates i get
"Communication failed"
The server is currently unavailable.
Your device will automatically check for an update within the next 48 hours.
Then if i check again it says device is up to date, you can check for updates again in XXhours. If i go into application manager -> AT&T Software Update and clear data, i can check for updates again but i get the same communication failed. I also tried clearing data and rebooting phone, and it still wont check.
And i can't get Samsung Kies running on my windows 7 pc for some reason, so i can't get updates from there either.
Is anyone else on AT&T experiencing these problems? Any fix for this? I really want that update that adds brightness control to the notification menu.
jefferson9 said:
I really want that update that adds brightness control to the notification menu.
Click to expand...
Click to collapse
I did not update, but hearing that update would disable local search, add new modem. Nothing about Brightness control
There is no brightness control on ATT update. I was having the same problem you were and exchanged the phone. There is no fix as far as I know for the error you are getting. It is a common issue. Search the annoyances (bugs) thread.
I don't know if the OTA update resolves your issue because they day after I exchanged mine the update came out.
Sent from my SAMSUNG-SGH-I717 using xda premium
I also haven't been able to get the OTA update. I assumed it was because I rooted and the device is listed as 'modified'. Is the update worth it?
It is in my opinion, and my usage habbits, for the WiFi stability increase that is gained.
Universal search is stripped (searches conducted on phone do not include on device results, ie contacts).
In other words, if you use the Google search by long pressing your menu button the results from your search will only be pulled from the internet.
I rarely use the search built in, so it hardly mattered to me.
Check out the developer forum for ways around the universal strip if you are rooted and want to update.
Sent from my SAMSUNG-SGH-I747 using xda premium
Well i reseated the SIM card, and removed the little blue tape from the sd slot and the SIM slot, rebooted and still not working.
I wanted to avoid rooting, since the stock software runs so smoothly and i liked being on the latest at&t software. I guess since i can't get OTA updates now theres no reason not to root.
Will this issue be fixed eventually? Or would i be better off exchanging phones while i can?
I'd exchange it. If you have faulty hardware then rooting won't do anything for you.
Peace of mind, if anything, that if you decide to root your phone is functioning as it should from the start.
Others will argue it's software issues.
But, whatever the cause, none of us paid to have a 90% functioning phone from the factory. Go get what you paid for is my take on it.
Good luck.
Sent from my SAMSUNG-SGH-I747 using xda premium
the1stSecond said:
I'd exchange it. If you have faulty hardware then rooting won't do anything for you.
Peace of mind, if anything, that if you decide to root your phone is functioning as it should from the start.
Others will argue it's software issues.
But, whatever the cause, none of us paid to have a 90% functioning phone from the factory. Go get what you paid for is my take on it.
Good luck.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Well speaking as a software engineer, i'm almost certain its a software issue, most likely with at&t's software update app, or on their servers. Mabey reinstalling the at&t software update application will help?
It sounds reasonable to me. Maybe try the method for No trip flash counter in devoplment? You would be upgrading to the newest firmware and have root and not trip the flash counter. You would still be able to check for ota updates (although should just return the status of your software is up to date since it is a totally stock ROM just with root injected). I imagine that would reinstall the software update service. Although with your knowledge you are way over my head. And whether or not when updating ROMs if that application is reinstalled is something I can't answer.
Maybe just try this first:
Settings> Application Manager> All> AT&T Software Update> Clear Data> Confirm
Power off Phone
Remove battery for at least thirty seconds.
Reinstall battery and power on device.
Try again after device boots up.
Sent from my SAMSUNG-SGH-I747 using xda premium
I've been having this same problem
I was thinking that its because of AT&T's controlled release of the OTA.
Its been so long since the release, that I can't imagine that's still true. I also agree that its probably a software thing. I have a number of the bloat apps disabled and also wonder if one or more of those would interfere with such a thing.
I'd love to hear about a resolution.
k3y0n4 said:
I've been having this same problem
I was thinking that its because of AT&T's controlled release of the OTA.
Its been so long since the release, that I can't imagine that's still true. I also agree that its probably a software thing. I have a number of the bloat apps disabled and also wonder if one or more of those would interfere with such a thing.
I'd love to hear about a resolution.
Click to expand...
Click to collapse
That's an interesting theory, I've disabled some boatware too. Have you tried enabling them? I'm going to try that now.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
So, if it's a software issue why is it two identical devices running the same software from the factory yield different results? I.e. my first device would do exactly as your original post outlines, then my replacement device had no issue checking for updates (same stock software, same device form factor).
If you search there are a lot of examples of complaints of this exact issue.
I am also very interested in this because even though there are many complaints out there, the only answers seem to be;
1) who cares this is xda and we update through Odin/cwm etc...
2) replace it.
Good luck, I hope you guys find an answer.
Sent from my SAMSUNG-SGH-I747 using xda premium
jefferson9 said:
That's an interesting theory, I've disabled some boatware too. Have you tried enabling them? I'm going to try that now.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I haven't tried enabling everything. I've tried enabling 'Samsung Push' which seemed like the likely starting point. I've been trying to do some debug on some battery drain things, so I've been hesitant to change too much at once. Also, I can basically only check every 24 hours so its slow going.
As far as the hardware issue, it just doesn't make too much sense that a hardware issue would be causing a problem because the software update would presumably be using the same hardware as the rest of the working smartphone functions. I think the explanation to one device updating and one not is more likely a server device id filtering or a user changing more than 'just the new hardware'.
Its neither here nor there though. Everyone will have there hair brained theories. Why don't we start asking what features will be on the next iphone. Seriously though, apple has to add a removable battery right? (I'm just kidding, please don't spam a million responses about how that will or will not ever happen.)
k3y0n4 said:
I haven't tried enabling everything. I've tried enabling 'Samsung Push' which seemed like the likely starting point. I've been trying to do some debug on some battery drain things, so I've been hesitant to change too much at once. Also, I can basically only check every 24 hours so its slow going.
As far as the hardware issue, it just doesn't make too much sense that a hardware issue would be causing a problem because the software update would presumably be using the same hardware as the rest of the working smartphone functions. I think the explanation to one device updating and one not is more likely a server device id filtering or a user changing more than 'just the new hardware'.
Its neither here nor there though. Everyone will have there hair brained theories. Why don't we start asking what features will be on the next iphone. Seriously though, apple has to add a removable battery right? (I'm just kidding, please don't spam a million responses about how that will or will not ever happen.)
Click to expand...
Click to collapse
You can bypass the wait time between checks by going into application managment -> at&t software update and clearing data. Then you can try to update again.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
I've had similar issues checking for updates. i gave up and pulled the first update with the USALG1 rom posted in the development forum sticky. I too have several apps disabled (actually moved out of the system/app dir) and was wondering if that possibly caused issues. I never did try updating through kies though.
My kies wont even run on my windows 7 64 bit. There seems to be alot of people having problems with kies on win7 64 bit, nothing from samsung either. So theres really no way for me to get updates
This is How I Got My Phone to Update
I should add that this was my 2nd galaxy s3 to not update. I did a factory reset hoping it would fix the issue. It didn't. I called att customer care for help b/c I was thinking maybe they just set up my account incorrectly when I first got the phone. Nothing else really makes sense. They said they couldn't help and take it to the store. I took it to an att store, and they said they don't actually do any software troubleshooting, so they just exchanged it for a new one. I tried doing the update there, it failed, so I took it home, and I force closed all the update apps, cleared all their data, and it worked as soon as I hit update. If force closing and clearing the data from the att and samsung update apps doesn't help, There may be nothing else you can do except take it in to an att shop.
AndroidLonghorn said:
I should add that this was my 2nd galaxy s3 to not update. I did a factory reset hoping it would fix the issue. It didn't. I called att customer care for help b/c I was thinking maybe they just set up my account incorrectly when I first got the phone. Nothing else really makes sense. They said they couldn't help and take it to the store. I took it to an att store, and they said they don't actually do any software troubleshooting, so they just exchanged it for a new one. I tried doing the update there, it failed, so I took it home, and I force closed all the update apps, cleared all their data, and it worked as soon as I hit update. If force closing and clearing the data from the att and samsung update apps doesn't help, There may be nothing else you can do except take it in to an att shop.
Click to expand...
Click to collapse
When you got it to work, exactly what apps did you force close and clear data? Just AT&T software update? Any others?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I force closed the At&T Software Update app and I think the Samsung Push Service. It is really the AT&T software update app that finally started downloading immediately after trying it again.
So I finally attempted the Keis connection and it worked immediately. I don't know what other problems people are having, but when I installed it on my Win7 x64 machine I had the S3 connected. After I ran the software for the first time it mentioned an update and proceeded to update it. Keep fighting the good fight jefferson9.
Hey guys, I'm new here, so this thread is probably on here somewhere, but oh well. I can't update my S3 OTA or through Kies. I know there is an update, as my friend got it fine on his yesterday (it's the one with the brightness slider in notification center). On OTA, it says communication failed every single time, then says up to date. I have tried clearing data and all that as well. And in Kies, it also says I have the latest firmware, even though I know I don't. Any ideas? I really don't want this happening when Jelly Bean comes out. Oh yeah, I'm not rooted or anything by the way, I'm still on stock for now.
I have the same exact issue. I think it has something to do with ATT and the phone not being set up right in their system. Did you by chance have an iPhone before your S3 and use the same Sim card?
Mine wouldn't find the ota on the phone. I searched around here and found a thread someone had started that has instructions on how to download the flashable zip and install it via CWM. Worked like a champ. If you are rooted this is the way you'll want to go
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Yes I did come from an iPhone. And I am planning to root soon so I might have to try that.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Hey do you mind giving me instructions on how to do that? And is there a safe way to root my phone on a Mac? And last of all, can I still get updates such as Jelly Bean on a rooted GS3 without losing root without messing anything up? Sorry I'm coming from iPhones and jailbreaking so I'm not familiar with all this.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Vanillamarble said:
Hey do you mind giving me instructions on how to do that? And is there a safe way to root my phone on a Mac? And last of all, can I still get updates such as Jelly Bean on a rooted GS3 without losing root without messing anything up? Sorry I'm coming from iPhones and jailbreaking so I'm not familiar with all this.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I've always recommended returning whatever device you have back to 100% stock (as it was out of the box) before taking any official updates. I've heard ppl say they can take them just fine while still rooted - but they lose root. Sometimes you can simply re-root, sometimes you have to wait for a new exploit to be discovered before you can root again. In light of this, I always wait a week (sometimes less) after a new OTA (Over The Air) update is released, just to be sure I can regain root immediately. Welcome to the wonderful world of Android OS!!!
[edit] to answer your post about not being able to take the last OTA update. Have you tried a factory reset? Through Android Recovery? You will lose personal settings and contacts if you dont back them up. But, it may solve your update issue. Another thing I know, that a lot of ppl do is - as soon as you buy a new device, such as the awesome Galaxy S III, is to immediately do the factory reset. (Who knows how many employees have goofed around with the new toys they just got in stock)
I had the same problem with not being able to get the OTA update on my S3. Turns out it was a bad sim. As soon as I got a new sim from AT&T everything worked fine. Wish I would have done that first cause I spent hours on the phone with AT&T and Samsung trying to fix the problem. Good luck. Hope that works for you.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Same issue here. Just spent a couple hours this Saturday at an AT&T store - end result is that they are swapping it out under the manufacture 1 year warranty.
Sim replacement did not fix it for me.
Tech support over the the stores land line says that the option to push OTA to phone is greyed out and not selectable with my account.
They are sending me a new phone so we'll see.
G-Man. said:
I've always recommended returning whatever device you have back to 100% stock (as it was out of the box) before taking any official updates. I've heard ppl say they can take them just fine while still rooted - but they lose root. Sometimes you can simply re-root, sometimes you have to wait for a new exploit to be discovered before you can root again. In light of this, I always wait a week (sometimes less) after a new OTA (Over The Air) update is released, just to be sure I can regain root immediately. Welcome to the wonderful world of Android OS!!!
[edit] to answer your post about not being able to take the last OTA update. Have you tried a factory reset? Through Android Recovery? You will lose personal settings and contacts if you dont back them up. But, it may solve your update issue. Another thing I know, that a lot of ppl do is - as soon as you buy a new device, such as the awesome Galaxy S III, is to immediately do the factory reset. (Who knows how many employees have goofed around with the new toys they just got in stock)
Click to expand...
Click to collapse
Read through the thread guys - there are other answers given besides just swapping the sim card...
Ok I'm going to try a factory reset. Wish me luck guys.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Just did a factory reset, and it didn't help at all. Now I've got to get everything back on my phone. Coming from iPhone, I will say that Apple has a heck of a lot better backup system. I do 0refer my GS3 though. Ok so any suggestions now?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
you've tried to update over cell network AND WiFi... correct? same error each time?
I'm not sure what else to suggest except trying a new sim card like someone else suggested... beyond that, a replacement device. Sorry man, wish I could be more useful...
[edit] The only other thing I can think to try would be to completely remove all your current USB Drivers for Samsung from your PC and reboot the PC, then re-install the USB Drivers, and try Kies again. If it still doesn't work, try a different PC.
Well I'm going to try a different computer, and if that doesn't work, I'm going to an AT&T store. Thanks for all the help guys.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
So I've been fighting with Touchwiz force closing quite often since the JB update. I flashed the full official ROM from Telus, as well as 2 other Telus based ROMS, all suffered from the same problem. The only thread I found pertaining to a similar issue is HERE.
Issue:
Touchwiz force-closing (stopping), when creating folders, or moving icons on the homescreen (like to delete them or move them to another homescreen).
In a nutshell, myself and 2 friends all have GS3s. 2 of us were having the issue, myself (rooted) and my friend (unrooted, completely stock), where as another friend (rooted) was not having the issue.
After much hair pulling and testing (3 different ROMS, using different computers and cables to flash, having my device flashed by my friend who was not having the issue), I came to the conclusion that Touchwiz was force closing ONLY when the App Drawer was in "Alpahbetical List" view type. When it was in a "grid" view type, there were no issues.
I was wondering if anyone else could do some testing and let me know if I'm on the right track with this.
I ask that you change your App menu to "Alphabetical List", and use it normally for a few hours or days, and let me know if you see any instances of Touchwiz force closing. If I see enough response, I'll start looking into how to place a bug report on this.
Thanks.
Did you wipe/factory reset? You should not be having issues like that if you did.I don't see any of that.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
crystalstylez said:
Did you wipe/factory reset? You should not be having issues like that if you did.I don't see any of that.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I wiped, factory reset, cleared caches, etc several times, as well as trying 3 different ROMS like I said.
The only way I could fix it was to clear data from Touchwiz Home. But the issue would still come back after a few hours.
So you are on JB, and are using "Alphabetical list" without issues??
Did you back up system and maybe restored the data wipe titanium by accident? If you have a clean install with nothing restored yet does it do this? If not install back all your apps one by one widget by widget to see what is causing this. Could be an app compatible issue. I tried to replicate your issue and could not at all.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
crystalstylez said:
Did you back up system and maybe restored the data wipe titanium by accident? If you have a clean install with nothing restored yet does it do this? If not install back all your apps one by one widget by widget to see what is causing this. Could be an app compatible issue. I tried to replicate your issue and could not at all.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Essentially a clean install, nothing installed or restored with titanium, and the issue was there. I think the only apps I had installed were Chrome browser, Go SMS (or Handcent, I tried them both because I thought maybe one of them was causing the issue), and Facebook. Other than that, I was on a stock rom (rooted).
I was just able to re-create the issue by doing the following:
1) Switch app list view type to "Alphabetical list".
2) Go to task manager, do a "Clear memory"
3) Go to homescreen, grab an icon, as if to remove it from home screen, and let it go.
Touchwiz force closes (Unfortunately, TouchWiz Home has stopped). As soon as I set it back to "Alpahbetical grid", everything works as it should.
Note: I do have a folder in the shortcut area on the homescreen (bottom, next to the Apps button), not sure if this makes a difference, but it usually starts when a folder is created...
I was able to recreate this problem on 2 Telus devices, and 1 stock Rogers device, all running JB.
Followed that and I still unable to recreate this. I also have a folder on mine in dock for email with Gmail and email in it. I am at&t though. Even though I am not sure if it matters.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
crystalstylez said:
Followed that and I still unable to recreate this. I am at&t though. Even though I am not sure if it matters.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Hmmmm, interesting. I was thinking of perhaps trying an AT&T based ROM (all I've tried were Telus based, and was able to recreate the bug on a friends Rogers device as well...). Maybe it's Canadian devices only? I did notice that it doesn't seem to be a very widespread issue. Although there was a thread about it, there were very few responses...
I'll see about flashing an AT&T ROM, but for the moment, its working properly in grid view, so I'm good with that.
Thanks for the input though!
I'm not able to reproduce this issue on my SGH-I747M (Rogers) running stock (not rooted) Android 4.1.1.
If you factory reset/wipe data on the stock ROM, configure the phone without installing any third-party apps from the Play Store (heck, don't even bother signing in with a Google account initially for this one), then set the app drawer to alphabetical list and attempt to reproduce the issue as per your earlier steps does it still occur? Just curious.
kmcckenn said:
I'm not able to reproduce this issue on my SGH-I747M (Rogers) running stock (not rooted) Android 4.1.1.
If you factory reset/wipe data on the stock ROM, configure the phone without installing any third-party apps from the Play Store (heck, don't even bother signing in with a Google account initially for this one), then set the app drawer to alphabetical list and attempt to reproduce the issue as per your earlier steps does it still occur? Just curious.
Click to expand...
Click to collapse
Thanks for trying it out.
I was actually able to reproduce it on my friends stock Rogers 4.1.1 OS.
I was able to reproduce it with a minimal install of third-party apps (mentioned in another post, I think I had Chrome, Go SMS and Facebook installed...).
Perhaps I'll give it a try if I flash a new ROM anytime soon. Right now, my device is working well, and I only figured out it was the List option causing me the problem after installing a bunch of apps and customizing. Don't feel like resetting right now just to try to reproduce it, lol.
Tested on Rogers Stock 4.1.1 root injected, no issues at all here.
Sent from my SGH-I747M using xda premium
jb 4.1
i tried to get this to happen on my gs3 but so far i have no complaints .i was running aokp for last 6 months or so and yesterday decided to go back to stock att jb 4.1 and must say i forgot how smooth tw is. i love aokp and tho i never really had any issues running tasks rom and now that he released 4.2 is fantastic!! but im likeing this new update from att its just nice to have everthing working perfect with awseome battery life charged my phone last night to full then unpluged and went to sleep . pleased to say that phone this morning 6 hrs later is still at 100 %..what i did to install was first i wiped phone completely formated everthing and then used odin to flash root66 rom insatlled booted up intsalled cmw and then just fixed parmisions. today is second day so far not one issue at all to report .. gunna hang with this for a bit let the bugs get fixed in 4.2
Also not able to reproduce this on blackjelly v1.02 (based on 4.1.1 ota).
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Ok guys and gals, this is the deal, i rooted my Note 2 GT-N7100 via Odin around 2 weeks ago, no issue, good stuff, infact the only reason i rooted was for Avast firewall and anti-theft options that come with avast as this was very useful with my last pnone, nexus...
anyhow it seened in the mean-time i was the last to recieve android 4.1.2 here in the uk, now im not useully impatiant, but curiosity got me and so via odin installed 4.1.2, though this was fine onece done it started up with the three logo, the network my sim is on, but the pnone was stock to all networks, so i believe.
A few days later still all is good, i was playing around with some apps such as Go launcher and others as Coldfustions android 3d ui tutorial had suggested on you tube, still no problems, just a little laggy, so i deleted caches as thought this my hep from the recent flash to 4.1.2 a week or so ago, well thats when things whent bad, very bad, cache deleted and pnone switched off and never came back on, just a red light next to the front facing camra, now, my pnone was clearly rooted with custom binary dowload @ 2, but strangly the system status kept switching to official to custom, looks bad right, what should i do...? many thanks ahead...:good:
Sds issue.
Can you tell the exact name of the file you flashed ?
Sent from my GT-N7100 using xda app-developers app
Sad to know that.... but have you try to boot it into recovery or download mode? Try to do it fast after you plug in your battery. It might work... Do let us know the update. Thanks
Update...
...Well i took it into the city to a local phone tech who will forward it to a samsung tech who doesn't mind a rooted phone, will cost £20 and said 100% fix:laugh: He suggested that it could be related to the s3 problems and had seen a rise in Feb in this strange activity will be around a week. I haven't tried the battery in/out as suggested, will consider in the future.
The file was from sammobile/hotfile (N7100XXDLL4_N7100H3GDLL2_N7100NEDLK1_HOME.tar.md5) will keep you all posted... thanks:good:
Kk you flashed a sds bugged rom .
You should have clarified if it could be booted or not.
Anyways I just wanted to clarify that this didn't happen due to rooting.
Sent from my GT-N7100 using xda app-developers app
...Once flashed to 4.1.2 it ran about a week, then when cleared caches it died? So to clarify it was a bugged rom or the actual flash/download that was the problem?... infact I remember in odin on pc the usb cable connection icon should be green for good to go, it was yellow as I could not find the solution as to why and still went ahead and flashed, ran like around a week and then died, maybe it was that, im still learning, a hard lessen to learn... im hoping ill get it back by the end of the week still in one piece...
Can you tell the whole name of the file you flashed?
Sent from my GT-N7100
?
All the information I could get is on this page with all the w's ...sammobile.com/firmwares/1/?model=GT-N7100&pcode=H3G#firmware[/url]) Its the 4.1.2 N7100XXDLL4_N7100H3GDLL2_H3G.zip im not to sure if thats what you want, if not could you point me in the right direction... many thanks...
Yeah it is 4.1.2 but does not contain sds patches.
Sent from my GT-N7100
Ok, not to sure what that means entirely, but why not?