Develop Bugs

Service unavailable :@

Hello thought I'd post something here to see if anybody else is having this problem, On most of the pages I try to load here on xda I get
Service Unavailable
It looks like were over capacity. Please try again in a minute.
Click to expand...
Click to collapse
Does anybody know what is causing this problem? And is anyone else getting this? I seem to be getting it more and more frequently
Thanks

MacaronyMax said:
Hello thought I'd post something here to see if anybody else is having this problem, On most of the pages I try to load here on xda I get
Does anybody know what is causing this problem? And is anyone else getting this? I seem to be getting it more and more frequently
Thanks
Click to expand...
Click to collapse
Maybe we were over capacity .
svetius might be able to explain. I'm guessing it's just to stop the site overloading, even twitter has those moments

DaveShaw said:
Maybe we were over capacity .
svetius might be able to explain. I'm guessing it's just to stop the site overloading, even twitter has those moments
Click to expand...
Click to collapse
Hehe I guessed that , side note , does this have anything to do with the new iPhone-developers ?

MacaronyMax said:
Hehe I guessed that , side note , does this have anything to do with the new iPhone-developers ?
Click to expand...
Click to collapse
No idea, you are the first to mentioned it.
Dave

We're working out a few kinks with the database setup and vBulletin's handling of master/slave database servers. This shouldn't happen to often, if it does, do let us know.

I was having every other link shoot me to the over capacity page about 3am EST. Thought for a minute I clicked on my Twitter bookmark lol. Excited to see the new plans in store for the site!

Damn, site seems really overloaded last days. But at least before it just worked slow. Now it won't even open (service unavaible).
I hope admins sort that issue out

Seems like the entire world is gettin' their xda freak on before the weekend.
I have been faced with the message. No biggie though. As long as I don't loose another day of completely magical posts.
good day.

Please rest assured that we are working to address these issues. We are aware of the overcapacity issues; it has happened to roughly 1000 user requests today.
matejdro said:
Damn, site seems really overloaded last days.
Click to expand...
Click to collapse
Can you be more specific about "really"? Are you getting it once a day, ten times a day, etc?

Rooted Kernels and Loss of Service

We're trying to determine the "root" (pun intended) of the problem so if you wanna come in here and start a fight go find a local bar to do so. We need to try and locate the source of the problem so either post something useful or walk away.
There seems to be some confusion and I dont know if its being ignored or what but theres an issue with these kernels that needs to be looked into further before new ones continue to be released.
Theres an obvious problem for a good amount of people and everytime I look I see comments that there isnt a problem. So heres everything I could quickly find regarding it.
Now Im not trying to be a **** about this but I dont get how the issue is unheard of when its one of the biggest topics in this section. And so we're clear, this is happening in ALL kernels. Unfortunately its been more profound in Zedos because it seems more people went with his method.
All Im asking is before more and more kernels are released that someone at least acknowledge the problem and see if it can be addressed before more and more people root and start complaining because they were told there was no LO.S. bug
zedomax said:
data drop? dunno about that, this shizzle will not drop. It's ZEDOMAX!
Click to expand...
Click to collapse
zedomax said:
jump and we will find out. no they should be worked out. there was no data loss kinks in da first place, where did u get that?
Click to expand...
Click to collapse
________________________________________________________________________________________________________
joetemp75 said:
Man I was fine then I flashed v5 and got the no signal issue
Click to expand...
Click to collapse
SupahDave said:
Everything seemed to be fine last night but today I've had 4 separate times now where my phone has lost signal all together and needed to be rebooted to get phone/data back. When this has happened I tried going into About-->Status to see if I could see anything odd and I kept getting a FC of com.android.phone
Click to expand...
Click to collapse
jimbobtexas said:
I did. No love. I'm without a signal, period.
Click to expand...
Click to collapse
MILH0U5E said:
Got the no signal issue here too. I put it in airplane mode overnight and upon waking this morning the no signal circle was there. I had to do a reboot to get 3g and cell signal back.
Looking forward to seeing this process develop.
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
wbyrd said:
Yeah this just happened to me too, everything was fine this morning then I played a game of solitaire and after going back to my home screen I saw the circle. Rebooted phone and everything came back on. It's possible that the circle was there before I played the game of solitaire but I didn't notice until right after I quit playing.
Hopefully it gets straightened out soon. At least rebooting fixes the problem, I can handle rebooting for a little while if needed.
Click to expand...
Click to collapse
plmiller0905 said:
I can't really deal with the issue of having no service. My daughter has a heart issue and can't afford to miss a call. It's not like I walk around all day literally looking at my phone's screen seeing if I have service or not.
I did reboot...so like your's my service is back up.
But I definitely hope this gets fixed soon. I'd rather have root with broken heptic feedback than the inability to receive calls.
But I'm sure the Op the get it fixed...
Click to expand...
Click to collapse
volwrath said:
I've had a dead call issue and also tday my radios were just dead and there was a circle in the middle of the notification barr. A reboot fixed the issues each time, but I think it might be a problem. I thing newer kernels will also fix said issues. Still very satisfied
Click to expand...
Click to collapse
JLine05 said:
I am having the issue of the phone (voice) and sms not working. Strange because everything else is working fine. Does anyone have any ideas? Thanks.
Click to expand...
Click to collapse
mcflargen said:
Still seems to have the data drop issue. Popped it on the second u dropped it, was great till a min ago. least a "restart" fixes it.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
joetemp75 said:
Man I just lost data again. This sucks
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
kindaskimpy said:
I'm giving this one a try because with the zedomax kernel I kept losing 3G and CDMA calling and not even noticing it unless someone told me they'd been trying to reach me for hours. A quick reboot would solve the issue but then it would happen again.
I'll report back and let you guys know if this one is giving me the same issue.
Click to expand...
Click to collapse
bbedward said:
I did this one because losing service on the other one, haven't lost it yet but its only been a couple hours
Sent from my sprint galaxy s2
Click to expand...
Click to collapse
fordmanck said:
I tried both, i'm back on this one. I lost service with zedos twice and haven't on this at all.
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse

Telling you right now someone is going to come in here and go "this belongs in General" then a mod will move your thread and deduct 5 points from something, not sure...but just a heads up

I also see a lot of people having issues, but I'm now on day 2 of flashing Zedo V1 and have yet to experience any of these issues. Not sure what I did different, but everything just works... The only thing I did was after rooting was getting my MSL from Sprint and erased the proxy servers in the ##3282 menu.
EDIT: Ok, I just lost service 1 1/2 day after rooting... Bug finally hit me..

I dont mind it being moved and I have no clue what the deduction in "points" does but I'll deal with it.
Now Im getting much better battery but I know people are still losing service on the new OC kernel. My roommate happens to be on e the unlucky ones.

Man...thanks for posting this. Hopefully the mod doesn't close this thread. This definitely is a concern and a serious matter. I don't care if these kernels are, "use at your own risk" these kernels should've been listed as betas, and/or the bugs should've been listed and further testing should have been. If those steps were taken, I bet a lot of people would've held back from flashing them. I know I would have.
Shabby posted this earlier in the other thread (post 160):
http://forum.xda-developers.com/showthread.php?t=1267762&page=16
One thing that got to me was this morning I woke up, hoping to see a stock kernel and/or a way to return to stock. And instead, I see a new overclockable kernel. To me that's just not right. I think that you have to prioritize. That's like putting out a rom that has all data broke. Then instead of fixing it, you put out another rom...while disregarding the issues with the first rom. At least acknowledge the issue and let everyone know it's been worked on....don't just blow it off.
I know some of the devs over in the Evo forums was good about this....if something went haywire with one of their roms or mods...they were all on top of it to get the issue fixed and they also communicated with posting updates on the matter.
Like I said, hopefully the mods don't close this.
I'm definately gonna follow this thread...thanks Wingzfan

i rooted yesterday using zedomax method, did the OC kernel last night.. havent had any issues so far ..

plmiller0905 said:
Shabby posted this earlier in the other thread:
http://forum.xda-developers.com/showthread.php?t=1267762&page=16
post 160
I'm definately gonna follow this thread...thanks Wingzfan
Click to expand...
Click to collapse
Bubby does have the stock kernel pulled. I was testing it till 1:30 in the morning but he's gotta recompile it. It was bootlooping so today thats his first order of business.
As for the kernels, I flashed it by choice. I dont blame the devs for ANYTHING, Im just saying acknowledge theres a bug and lets see how to resolve it.

I've been reading through the rooted kernel threads as well prior to jumping on the root wagon and have seen several people mention that they are not rooted and have experienced the loss of service so it seems that the issue may not be exclusive to the rooted kernels...possibly a Samsung bug?

Very possible which is why im hoping we can get an idea of how man people are rooted vs non rooted having it. Now the only thing is I cant find any complaints online about nonrooted phones doing it except a few here and youd think it'd be widely discussed
Sent from a Galaxy far far away...

OrygunGal said:
I've been reading through the rooted kernel threads as well prior to jumping on the root wagon and have seen several people mention that they are not rooted and have experienced the loss of service so it seems that the issue may not be exclusive to the rooted kernels...possibly a Samsung bug?
Click to expand...
Click to collapse
Yeah...I read those too. However, I never lost any service at home with any android phone I've owned..Nexus S 4g, all Evo's, Epics etc. Then today I wake up and I have no service....maybe it is a samsung bug, but I'd rather return to stock myself to see if the issue was still there.

Stocks on its way i promise. Probly tonight actually. Bubby was really close last night. Once we get that Id be curious to see what happens.
Sent from a Galaxy far far away...

wingzfan said:
Stocks on its way i promise. Probly tonight actually. Bubby was really close last night. Once we get that Id be curious to see what happens.
Sent from a Galaxy far far away...
Click to expand...
Click to collapse
Sounds good...can't wait
Sent from my SPH-D710 using Tapatalk

This is an issue that started with mine also yesterday. But not only did I lose data but gps also. A reboot fixed it but I would like to know whats going on. I just came from the evo 3d and there was an issue that had to do with the prl so I am going to give that a shot with the 11115 prl that fixed the evo. Will post back with the results later today.

On V5, Ive only had the loss of data once in about 12 hours, versus about 3 times on Zedo V1.
I also did http://forum.xda-developers.com/showpost.php?p=17703908&postcount=11 for the hell of it to see if that helped (even though I got it at a sprint store)

For the record:
A) People have reported this issue even on the stock kernel. It is not clear where the cause is.
B) For kicks (and because it cannot hurt) I did the whole profile/PRL update thing that someone suggested. Be it luck or real benefit, I have no had the issue since.

wingzfan said:
Very possible which is why im hoping we can get an idea of how man people are rooted vs non rooted having it. Now the only thing is I cant find any complaints online about nonrooted phones doing it except a few here and youd think it'd be widely discussed
Sent from a Galaxy far far away...
Click to expand...
Click to collapse
I would think it would be widely discussed as well so that seems odd. I'm waiting to see what evolves or at least for stock kernel (an undo) before flashing a rooted one. I don't have TEP.

It's still a bit early for the issue to be too widely discussed.

dmarden said:
For the record:
A) People have reported this issue even on the stock kernel. It is not clear where the cause is.
B) For kicks (and because it cannot hurt) I did the whole profile/PRL update thing that someone suggested. Be it luck or real benefit, I have no had the issue since.
Click to expand...
Click to collapse
Nice. I was told by a helpful Sprint cust. serv. rep. a while back that you should update your PRL & Profile when you go into a new area (tavel, move, or even long commute to work) regardless of which phone you have. I would think unboxing your phone would qualify as well. It sure couldn't hurt.
---------- Post added at 06:59 AM ---------- Previous post was at 06:53 AM ----------
dmarden said:
It's still a bit early for the issue to be too widely discussed.
Click to expand...
Click to collapse
Good point. Many people would not likely research on the web/forums, instead they'd likely address the issue directly with Sprint.

plmiller0905 said:
Yeah...I read those too. However, I never lost any service at home with any android phone I've owned..Nexus S 4g, all Evo's, Epics etc. Then today I wake up and I have no service....maybe it is a samsung bug, but I'd rather return to stock myself to see if the issue was still there.
Click to expand...
Click to collapse
Ever owned a Samsung phone before?
This is my 3rd one and I swore after the last one Id never buy a Samsung phone again but I got sucked back in. Samsung is notorious for shipping phones with all kinds of bugs that should be considered showstoppers then pushing out fixes months later.
It would not surprise me at all if that was the case here. I am one of the ones having this issue and I am not rooted. Ive lost data several times after hanging up a call. The data never restores and I have to toggle 3G to get it come back.
I dont think this is a kernel issue. I think its something to do with the rest of the OS, either that or the kernel is a different problem thats just acting the same way.

Ok thats what i was hoping to find is nonrooted and rooted people who are having the issue. Now on my moment this issue was huge so i went to htc and maybe thats the case again. Maybe sammy dropped the ball again. Question is what can be done about it.
Sent from a Galaxy far far away...

Pixel suddenly dying with 15-30% battery left

Is anyone else running into this? I did a quick search, and didn't see any hits in the the Q&A section or the PureNexus ROM forum which I'm running. I think it is a somewhat common problem. The first thing google support chat asked me was if I was rooted. I said no, but is this only happening to rooted phones?

l2yangop said:
The first thing google support chat asked me was if I was rooted. I said no, but is this only happening to rooted phones?
Click to expand...
Click to collapse
I had it happen once with an unrooted phone near the end of December.

I guess I'm going to send it in... but don't want to bother flashing back to stock if I dont have to. thoughts?

l2yangop said:
Is anyone else running into this? I did a quick search, and didn't see any hits in the the Q&A section or the PureNexus ROM forum which I'm running. I think it is a somewhat common problem. The first thing google support chat asked me was if I was rooted. I said no, but is this only happening to rooted phones?
Click to expand...
Click to collapse
Was the phone cold? There is extensive conversation about this on the Nexus 6P forum, and it is much worse when the phone is cold. I had it happen cold and warm, but it happened often when it was below 30 degress F.

thacounty said:
Was the phone cold? There is extensive conversation about this on the Nexus 6P forum, and it is much worse when the phone is cold. I had it happen cold and warm, but it happened often when it was below 30 degress F.
Click to expand...
Click to collapse
no, i live in FL haha

l2yangop said:
no, i live in FL haha
Click to expand...
Click to collapse
Haha. I've been in FL when it was 35!
I was just wondering if it was the same scenario. Not that it would be acceptable.

l2yangop said:
Is anyone else running into this? I did a quick search, and didn't see any hits in the the Q&A section or the PureNexus ROM forum which I'm running. I think it is a somewhat common problem. The first thing google support chat asked me was if I was rooted. I said no, but is this only happening to rooted phones?
Click to expand...
Click to collapse
You could try flashing February stock rom, then doing factory reset, in case anything is out of kilter in software causing this.

l2yangop said:
Is anyone else running into this? I did a quick search, and didn't see any hits in the the Q&A section or the PureNexus ROM forum which I'm running. I think it is a somewhat common problem. The first thing google support chat asked me was if I was rooted. I said no, but is this only happening to rooted phones?
Click to expand...
Click to collapse
This is now widely reported and seems to be major problem affecting lot of pixel phones. Check out the number of entries in the product support page and in the android code tracker.
https://productforums.google.com/fo...!msg/phone-by-google/QiGBJRx9oxg/Xy5_pkJZDAAJ
https://code.google.com/p/android/issues/detail?id=230806 - Google has marked it as fixed and status is updated as future release which means that it is a software bug.
I also had this issue but i dont have it right now. Mine got resolved by using a non-stock and non-quick charger to charge the phone. I havent faced this issue for the past couple of weeks now. Some people had success doing it and some did not. So its more of a hit and a miss. My guess is that this is a software bug caused by the battery reporting percentage

I have this bug at the moment too. Some users are reporting that a factory reset solved it for them so I have done one yesterday. Can't say yet if it fixed the problem for me too.
You can read more here:
https://forum.xda-developers.com/showthread.php?t=3530040
Gesendet von meinem Pixel XL mit Tapatalk

lalit79 said:
This is now widely reported and seems to be major problem affecting lot of pixel phones. Check out the number of entries in the product support page and in the android code tracker.
https://productforums.google.com/fo...!msg/phone-by-google/QiGBJRx9oxg/Xy5_pkJZDAAJ
https://code.google.com/p/android/issues/detail?id=230806 - Google has marked it as fixed and status is updated as future release which means that it is a software bug.
I also had this issue but i dont have it right now. Mine got resolved by using a non-stock and non-quick charger to charge the phone. I havent faced this issue for the past couple of weeks now. Some people had success doing it and some did not. So its more of a hit and a miss. My guess is that this is a software bug caused by the battery reporting percentage
Click to expand...
Click to collapse
Thanks for you reply. I have seen reports of people sending their phone (usually the 6p but even a couple pixels) back for repair under warranty . If its a software bug and we're on the latest version of software, what could they be doing to fix it when they send it back I wonder? Make me think its hardware.

This could be indicative of a malfunctioning battery. Flashing back to bone stock would be the best troubleshooting method.

[email protected] said:
I have this bug at the moment too. Some users are reporting that a factory reset solved it for them so I have done one yesterday. Can't say yet if it fixed the problem for me too.
You can read more here:
https://forum.xda-developers.com/showthread.php?t=3530040
Gesendet von meinem Pixel XL mit Tapatalk
Click to expand...
Click to collapse
Factory reset on stock? I'm running Pure nexus and elemental x

l2yangop said:
Factory reset on stock? I'm running Pure nexus and elemental x
Click to expand...
Click to collapse
yes, on stock rom. But I think it's not rom related.
Edit, you can try 7.1.2 beta, someone wrote there should a fix in it for that problem
Gesendet von meinem Pixel XL mit Tapatalk

Had this start the last couple of days at 30%. Very annoying. Completely stock as well.

I had this problem and attempted the trouble shooting tips from Google without success. I managed to get a replacement and not had any issues since.

firephoenixctk said:
I had this problem and attempted the trouble shooting tips from Google without success. I managed to get a replacement and not had any issues since.
Click to expand...
Click to collapse
Was the replacement directly from Google? Or from your service provider.
Apparently google made a fix to this issue in upcoming updates.

AznRico said:
Was the replacement directly from Google? Or from your service provider.
Apparently google made a fix to this issue in upcoming updates.
Click to expand...
Click to collapse
The replacement was directly from Google.

Coming up to 30% soon so I'll see if it does it again. Apparently it's still happening in 7.1.2 so god knows what update it's fixed in.

I have been reporting in the Pixel community and bug report. My phone was purchased in November from the Google Store, has never been rooted, and always use the OEM charger. My phone ran great until the February patch and then began encountering the abrupt power off around 30% battery.
Android OS, Android System, and Google Play Services are always the top battery consumers. Turning off various things has had no impact. I finally contacted Google and they are giving me the run around about a replacement. The Support staff did confirm they are aware and are replacing some phones but working on a fix, which implies it is software as noted above.
I am still pushing for a replacement and will see what happens.

jonathon1289 said:
I have been reporting in the Pixel community and bug report. My phone was purchased in November from the Google Store, has never been rooted, and always use the OEM charger. My phone ran great until the February patch and then began encountering the abrupt power off around 30% battery.
Android OS, Android System, and Google Play Services are always the top battery consumers. Turning off various things has had no impact. I finally contacted Google and they are giving me the run around about a replacement. The Support staff did confirm they are aware and are replacing some phones but working on a fix, which implies it is software as noted above.
I am still pushing for a replacement and will see what happens.
Click to expand...
Click to collapse
If its happening continuously this is probably something wrong with the battery. I have two Pixel XLs and had this happen once at around 35%! I left it powered off and recharged and this seemed to do the trick. Its clearly a software problem in that instance. So this could be two distinct issues IMO.

Samsung fitness app update issue

Has anybody else noticed a huge jump in floor count since the last update?
I used to think maybe it was a bit low and undercounted but now I'm getting huge numbers for the same daily routine?

stewarta13wsb said:
Has anybody else noticed a huge jump in floor count since the last update?
I used to think maybe it was a bit low and undercounted but now I'm getting huge numbers for the same daily routine?
Click to expand...
Click to collapse
Dont know when it happened, but its totally unreliable. I can get like 50 floors during one day, when in real life I might have walked 2 stairs.

please check the barometer, I experienced the same issue and the reason was barometer

sandgod said:
please check the barometer, I experienced the same issue and the reason was barometer
Click to expand...
Click to collapse
How to fix it?
It seems to include the floors when I used lift

sandgod said:
please check the barometer, I experienced the same issue and the reason was barometer
Click to expand...
Click to collapse
What did you do, uninstall it?

torickray said:
How to fix it?
It seems to include the floors when I used lift
Click to expand...
Click to collapse
Nothing helped, i sent it to the service center

Is the "Check for Updates" button broken for anyone else?

I'm running the January 2019 image on my 3 XL and checking for updates to get the new February one to download is not working. Is anyone else having this issue?

David B. said:
I'm running the January 2019 image on my 3 XL and checking for updates to get the new February one to download is not working. Is anyone else having this issue?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=78845337&postcount=30

Mine worked. I checked on the 3rd, and it got me the update. All good here.

bobbyphoenix said:
Mine worked. I checked on the 3rd, and it got me the update. All good here.
Click to expand...
Click to collapse
Are you rooted?

David B. said:
Are you rooted?
Click to expand...
Click to collapse
Nope. 100% stock.

bobbyphoenix said:
Nope. 100% stock.
Click to expand...
Click to collapse
Huh. Perhaps it's a Magisk thing then. I will try unrooting to see what kind of results that warrants.

David B. said:
Huh. Perhaps it's a Magisk thing then. I will try unrooting to see what kind of results that warrants.
Click to expand...
Click to collapse
Doubt it, in the past it would still at least pull the update. It would often fail but at least it would try.
So they changed that and do a pre check now, or the update system is broke. I vote broke....seems to be a lot of this going around.
Or they are staggering updates more than usual.

TonikJDK said:
Doubt it, in the past it would still at least pull the update. It would often fail but at least it would try.
So they changed that and do a pre check now, or the update system is broke. I vote broke....seems to be a lot of this going around.
Or they are staggering updates more than usual.
Click to expand...
Click to collapse
Yeah that's what I thought was supposed to happen but it wouldn't be the first time that Google changes something causing things to break.