Related
Can someone please help me out here. I just got my SGS 2 for T-Mobile a few days ago, as I'm coming from a Sensation. The phone is rooted and I installed Juggernaut and after a few days my phone started to reboot constantly and say that network is unavailable. I would reboot into recovery and wipe and it restarted and same thing happened. I then began to reinstall ROM and it would work for a bit, then same thing would happen. I then formatted system, data, and reinstalled ROM, same problem. I then installed Beast ROM thinking it might be ROM, but same thing happened with this one. I have wiped over and over again and same problem. I got a new sim card and same thing. I re-rooted and same problems. I installed stock ROM, downloaded new stock ROM, upgraded modem, and same problems. I remove sd card, same problem. I am out of ideas and options so someone please assist me with this matter as I've never had this problem before.
Sounds like a faulty device. I'd take it back!
Sent from my SGH-T989 using xda premium
This was happening to my first SGS2 as well. It was within the 14 day buyers remorse thing from Tmobile and I was able to exchange it for a brand new one. Haven't had any issues since.
Sent from my SGH-T989 using xda premium
Well the problem with that is that I bought it off of someone. Everything had been working fine until I applied a custom ROM. I will continue to mess around with it to find a solution.
Sent from my iCrap killer
Try the new stock and see if it continues.
cbrvnm said:
Well the problem with that is that I bought it off of someone. Everything had been working fine until I applied a custom ROM. I will continue to mess around with it to find a solution.
Sent from my iCrap killer
Click to expand...
Click to collapse
Just call T-Mobile and get a warranty exchange.
Powered by the SGSII....
or try a different rom , i had those issues with juggernaut also
tigerz0202 said:
or try a different rom , i had those issues with juggernaut also
Click to expand...
Click to collapse
I did try different ROMs. I tried beast's, stock, and new stock one also, and it still continued.
Sent from my iCrap killer
cbrvnm said:
I did try different ROMs. I tried beast's, stock, and new stock one also, and it still continued.
Sent from my iCrap killer
Click to expand...
Click to collapse
well do a warranty exchange then i had the same thing happen on my first phone also ,all i ran on my first phone was stock rom and juggernaut and it kept doing it so i had to return it
tigerz0202 said:
well do a warranty exchange then i had the same thing happen on my first phone also ,all i ran on my first phone was stock rom and juggernaut and it kept doing it so i had to return it
Click to expand...
Click to collapse
I'll try out a few more things and if that doesn't work I'll exchange it. Thanks.
Sent from my iCrap killer
For the rest of u that had the same problem, were u rooted and running a custom ROM?
Sent from my iCrap killer
Nop its the phones that come faulty I had to get mines replaced because of the same problem and even the new upgrade didn't help it. Now the new one I got two days ago it's working like a champ and on beastmod
Sent from my SGH-T989 using XDA App
dtddemon said:
Nop its the phones that come faulty I had to get mines replaced because of the same problem and even the new upgrade didn't help it. Now the new one I got two days ago it's working like a champ and on beastmod
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
Ok. Thanks.
Sent from my iCrap killer
Well I think I got it working as it hasn't rebooted or lost signal today. I redid root, upgraded modem to new one, and reformatted sdcard. I rebooted the phone several times without problem, but I haven't tried wiping cache/dalvich as I'm kinda scared that this might cause some problems again but when I decide to I hope nothing happens.
Sent from my iCrap killer
cbrvnm said:
Well I think I got it working as it hasn't rebooted or lost signal today. I redid root, upgraded modem to new one, and reformatted sdcard. I rebooted the phone several times without problem, but I haven't tried wiping cache/dalvich as I'm kinda scared that this might cause some problems again but when I decide to I hope nothing happens.
Sent from my iCrap killer
Click to expand...
Click to collapse
Nevermind. Today the phone began to reboot once again and I called customer service and basically I have to go through some steps before they can replace it. So I'll see how that goes.
Did u fix.permission
Sent from my SGH-T989 using XDA App
Hey dude, let me offer you a bit of advice. Even if you bought the phone off some guy, you can still get Tmobile to send you a new one through the warranty.... just don't mention where you bought it from. What you have to do is log on to your Tmobile account and verify that under "My Device" it shows you using a GS2. This means their system shows you using that phone. Then contact their customer service through the chat, and just say that you are having a problem with the phone, blah blah blah. They shouldn't ask you where you bought it, and they should send you a new one with a return label to send this one back. Just make sure that it's stock and unrooted. Hope this helps.
Well I will be getting a replacement phone through warranty exchange afterall. Hopefully this new one works out well. Thanks everyone for ur input.
Sent from my iCrap killer
Ok, so I got a replacement phone and bought another one. I can root the phone and install roms, but no matter what rom I use, I always get no network available and constant reboots after a reboot. I have wiped completely, formated sd card and same problems. I have never had this happen on any previous phone. Does anyone have any ideas or suggestions cuz I'm completely lost on what to do. :banghead:
Sent from my iCrap killer
Very similar experience yesterday for me. Zero data, it wont read any sim card. Getting my 3rd replacement within a week.
Hey guys,
I have had my nexus for about a year now and am very happy with it, its been working very well until a few days ago.
I went to turn my WiFi on, and noticed that it was not doing anything, or rather just idleing on "turning WiFi on". My first instinct was to turn it off and on again... Nope. Reflash of ROM ... No luck . reflash or radio and kernel ... Still nothing . reverted back to completely stock, unrooted android still Nada. I am in the process of getting it sent back to Samsung, but was wondering if any of you guys would be able to help me not having to send it off for weeks to the repair center. Has anyone encountered this bug and sorted it ? Lots of threads about it but no solutions .
Cheers !
Same issue since yesterday on my GNX
I am experiencing exactly the same behavior on my Galaxy Nexus since yesterday afternoon. Curiously, also yesterday marked exactly one year since I got my hands on the then brand new Galaxy Nexus.
Galaxy Nexus in my case, *suddenly NOT being able to turn WiFi on, *having the phone while on the WiFi screen settings just stating: "Turning Wi-Fi on" but it actually never does... so, obviously, WiFi doesn't work ?
3G, phone calls, and all the rest apps,etc. do work fine. *This happened yesterday, suddenly, *I was using tethering for some time, when I finished turned tethering off and WiFi stillw worked fine.
My GN is rooted, but it is running Jelly Bean 4.2.2 stock, I have never put a 3rd party ROM in this phone.
There are many threads out there (xda-developers and others) that state that this started happening to lots of users of GN in the last few weeks, 1 month or so, *Many report having this issue on GN with a little of over 1 year.... weird!
speedking34 said:
Hey guys,
I have had my nexus for about a year now and am very happy with it, its been working very well until a few days ago.
I went to turn my WiFi on, and noticed that it was not doing anything, or rather just idleing on "turning WiFi on". My first instinct was to turn it off and on again... Nope. Reflash of ROM ... No luck . reflash or radio and kernel ... Still nothing . reverted back to completely stock, unrooted android still Nada. I am in the process of getting it sent back to Samsung, but was wondering if any of you guys would be able to help me not having to send it off for weeks to the repair center. Has anyone encountered this bug and sorted it ? Lots of threads about it but no solutions .
Cheers !
Click to expand...
Click to collapse
Try a different ROM, preferably one on a different version of Android, so if you're on 4.2 flash a 4.1 ROM.
If that doesn't work, sounds like the chip is broken (?), hell I wouldn't bother Samsung, I'd use it as an excuse to get a new phone, one with easy-to-get accessories and Qi perhaps?
Sent from my Galaxy Nexus using xda app-developers app
jimmyco2008 said:
Try a different ROM, preferably one on a different version of Android, so if you're on 4.2 flash a 4.1 ROM.
If that doesn't work, sounds like the chip is broken (?), hell I wouldn't bother Samsung, I'd use it as an excuse to get a new phone, one with easy-to-get accessories and Qi perhaps?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Did that, have flashed tons of new ROMs, Cyanogen, some others and stock, several versions of each. Seems the WiFi chip is broken or, there is something loose inthe mainboard, antennae or circuitry. Yeah, great excuse to get a new Nexus, but, anyway, I paid some good money for the brand new Galaxy Nexus it barely worked exactly one year before breaking out of nowhere.
I have read and seen some others with exactly the same situation. It seems like it is a manufacture defect on the Galaxy Nexus devices.
Well my phone won't respond to my touch at all. Everything does work, I thought it was the rom but I went into recovery but it just won't do anything when I touch it. The volume buttons work. This is so odd, never had this problem with any of my old phones. It could be the digiziter... As of now I'm going to try a few things, pull the battery for a few minutes, factory reset, install another rom. Oh yeah I'm running cm10.1 yesterday's build I belief. So guys any ideas? Tips? Suggestions? Also how could this happen? I didn't drop it last night. It was working fine expect it had to signal because I was in a basement.
Wow the oddest thing just happened. I took the battery off right, well I put it back in and turned the phone in. I unlock the phone which got me excited obviously, but shortly after it stopped working. This had to be a rom issue or damaged digiziter....
What the hell...I haven't installed or factory reset because the phone was charging. Didn't want to mess with low battery. Well I plugged it into my computer. And guess what? It effing worked! Now the touchscreen works. This is making me scratch my head. What the hell happened? How did connecting it into the computer fixed the computer? You guys have any ideas?
Phone is slowly dying, not a rom issue I don't think. Change the rom just in case to find out. Also Google the issue, it shouldn't be just this phone kinda bug.
Sent from my SGH-T999 using xda premium
I'd Odin back to Stock, root66. This way you can completely eliminate a rom, mod, kernel, etc. Run purely stock for a day or two at least and you will have a better idea as to the cause.
Sent from my SGH-T999L using xda premium
mt3g said:
Phone is slowly dying, not a rom issue I don't think. Change the rom just in case to find out. Also Google the issue, it shouldn't be just this phone kinda bug.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
It would make sense. I did, there's several people with the same issue, same phone.
DocHoliday77 said:
I'd Odin back to Stock, root66. This way you can completely eliminate a rom, mod, kernel, etc. Run purely stock for a day or two at least and you will have a better idea as to the cause.
Sent from my SGH-T999L using xda premium
Click to expand...
Click to collapse
I'll do that, before cm10 I was running miui which was buggy as hell. That rom probably left something behind. I'll Odin, thanks you two.
iwillkillyou said:
It would make sense. I did, there's several people with the same issue, same phone.
I'll do that, before cm10 I was running miui which was buggy as hell. That rom probably left something behind. I'll Odin, thanks you two.
Click to expand...
Click to collapse
Report back this is interesting, I haven't seen it on this forum yet.
Sent from my SGH-T999 using xda premium
This is quite interesting indeed. A similar ordeal kept happening when I was still on stock Touchwiz Rom. It's what forced me to look for alternative roms. I haven't had the unresponsive touchscreen ever since, so I'm interested in finding out if switching roms will solve your problem as well.
[ Sent from my WHAT!? ]
I've had a problem like this with my last two phones, both being Samsung. My phone prior to the sgs3 was the nexus s. About a year in it started randomly opening apps and pulling open the power menu. I thought it might just be the rom or battery went back to stock and got a new battery and it still continued.. So i finally upgraded to the sgs3. I just started having the same problem on my gs3. It would open the power menu and it would randomly open apps and type on the keyboard. I reverted to stock and it seemed to fix the problem on this phone. It's weird though, it's happened on both of my latest devices.
Thats just weird to me. This is the first ive ever heard of this happening on our GS3's. Hopefully its all just corrupted software or something related and a clean Odin flash will fix it.
Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
kennyglass123 said:
Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Click to expand...
Click to collapse
In wasn't asking a question, I was informing the members of our forum about this problem.
DocHoliday77 said:
Thats just weird to me. This is the first ive ever heard of this happening on our GS3's. Hopefully its all just corrupted software or something related and a clean Odin flash will fix it.
Click to expand...
Click to collapse
Andrew421 said:
I've had a problem like this with my last two phones, both being Samsung. My phone prior to the sgs3 was the nexus s. About a year in it started randomly opening apps and pulling open the power menu. I thought it might just be the rom or battery went back to stock and got a new battery and it still continued.. So i finally upgraded to the sgs3. I just started having the same problem on my gs3. It would open the power menu and it would randomly open apps and type on the keyboard. I reverted to stock and it seemed to fix the problem on this phone. It's weird though, it's happened on both of my latest devices.
Click to expand...
Click to collapse
KunoMochi said:
This is quite interesting indeed. A similar ordeal kept happening when I was still on stock Touchwiz Rom. It's what forced me to look for alternative roms. I haven't had the unresponsive touchscreen ever since, so I'm interested in finding out if switching roms will solve your problem as well.
[ Sent from my WHAT!? ]
Click to expand...
Click to collapse
I did return to stock, since then the ploblem hasn't occurred again.
iwillkillyou said:
In wasn't asking a question, I was informing the members of our forum about this problem.
Click to expand...
Click to collapse
I refer you yo the end of your first paragraph. You posted this not yo inform us of your problem, but to ask us for help with it. Even if you managed to avoid any actual "questions", if its even implying that you are asking or requesting, then it belongs in Q&A.
I did return to stock, since then the ploblem hasn't occurred again.
Click to expand...
Click to collapse
So problem solved then? Good deal! Glad to hear you got it worked out!
Sent from my SGH-T999 using xda premium
---------- Post added at 10:35 PM ---------- Previous post was at 10:34 PM ----------
Sounds like something got corrupted. I'd make a nandroid now, so you have a known good backup. Just in case.
Sent from my SGH-T999 using xda premium
iwillkillyou said:
In wasn't asking a question, I was informing the members of our forum about this problem.
.
Click to expand...
Click to collapse
You have 3 questions at the end of your post which resulted in people offering advice.
I just wanted to let you all know that even on 4.1.2 (stock and stock recovery), your note can just all of a sudden die. For no reason. I had stock malaysia ROM 4.1.2 that was released in April I believe. It was rooted, but all I used that for was Titanium Backup.
My usage of the phone was bare minimum, all I really use the phone is for Google Talk. That's actually all I was doing when all of a sudden the screen froze and the phone would not respond to any buttons or touches. Once I removed the battery it never started again. I can't get it to boot normally, or download mode or anything.
I'm in the US and i bought this off eBay back in November or something of last year, so I have no idea what to do now except get another phone.
Yes its the chipset in the phone that has a bug which can kill the phone. Alot of the note2 phones have it including mine. There is an app on market that can tell you if you got the chip in your phone but by now you already know that. Try a phone repair shop or if you want surf around the net and see if you can find a motherboard for a decent price then you could change it your self.
Sent from my GT-N7100 using XDA Premium 4 mobile app
---------- Post added at 06:50 PM ---------- Previous post was at 06:47 PM ----------
The newer roms have a software fix for the hardware bug. Dont remember if that fix is in the rom it self or in the kernel but if you had the latest custom rom on your phone then it might not have died.
Sent from my GT-N7100 using XDA Premium 4 mobile app
I was on 4.1.2 with stock rom and kernel combination. As far as everyone seems to say on this site, that is what you need to do to try to avoid SDS. In either case, my suggestion to everyone here is to just get another phone before yours dies as well.
ksc6000 said:
I was on 4.1.2 with stock rom and kernel combination. As far as everyone seems to say on this site, that is what you need to do to try to avoid SDS. In either case, my suggestion to everyone here is to just get another phone before yours dies as well.
Click to expand...
Click to collapse
My N7105 died also, simply would not boot, not even into download/recovery mode at all, no red led. Tried switching batteries, charging, pressing buttons for 30secs, etc; no response.
It was running 4.1.2 and on Perseus kernel alpha33, which was what everyone said it needed to avoid the SDS issue. My phone was even tested safe/sane via the eMMC test app.
Not 100% certain if it was SDS, but either way it was unresponsive/dead.
ksc6000 said:
I just wanted to let you all know that even on 4.1.2 (stock and stock recovery), your note can just all of a sudden die. For no reason. I had stock malaysia ROM 4.1.2 that was released in April I believe. It was rooted, but all I used that for was Titanium Backup.
My usage of the phone was bare minimum, all I really use the phone is for Google Talk. That's actually all I was doing when all of a sudden the screen froze and the phone would not respond to any buttons or touches. Once I removed the battery it never started again. I can't get it to boot normally, or download mode or anything.
I'm in the US and i bought this off eBay back in November or something of last year, so I have no idea what to do now except get another phone.
Click to expand...
Click to collapse
Ohh,Sorry for that & Thanks share this IMP Info,Have u ever Test eMMC Bug app? U have Sane Chip?U bought new phone?
No I didn't buy a new phone yet, don't have the money. I probably won't, I'll probably just use my old Nexus One. Yes I did use that app and it was insane chip. I just thought that with 4.1.2 it was safe, guess not.
Anybody know if it's safe for me to sell this phone on eBay? Obviously I'm going to sell it as is and write that it doesn't work, but I'm wondering if I do that, if someone can get it repaired, will they have access to my data that was on it?
ksc6000 said:
No I didn't buy a new phone yet, don't have the money. I probably won't, I'll probably just use my old Nexus One. Yes I did use that app and it was insane chip. I just thought that with 4.1.2 it was safe, guess not.
Anybody know if it's safe for me to sell this phone on eBay? Obviously I'm going to sell it as is and write that it doesn't work, but I'm wondering if I do that, if someone can get it repaired, will they have access to my data that was on it?
Click to expand...
Click to collapse
Oh OK,but who ever face SDS they have one common symptoms like when press power button red led blinks,is it same happening in your mobile? also they are able to go in download mod but product id will be missing but in your case u r not able to go in download mod,its confusing.
jdomadia said:
Oh OK,but who ever face SDS they have one common symptoms like when press power button red led blinks,is it same happening in your mobile? also they are able to go in download mod but product id will be missing but in your case u r not able to go in download mod,its confusing.
Click to expand...
Click to collapse
No red light. I can't get into download mode at all.
a piece of my knowledge acquired by reading the whole thread. First of all it doesn't matter if you were at 4.1.2 it should be dlk7 or higher (firsts 4.1.2 didn't have it). so do you know the number? if it was higher it could be a big problem for the affected chips :S
and secondly, there are 2 ways of SDS the first is known as "soft" which allow to enter download. the second is the hard one and the one that OP may have.
hope it helped somehow
Sent from my GT-N7100 using xda premium
aka_sirok said:
First of all it doesn't matter if you were at 4.1.2 it should be dlk7 or higher (firsts 4.1.2 didn't have it). so do you know the number? if it was higher it could be a big problem for the affected chips :S
Click to expand...
Click to collapse
Hmm ok, just curious, my dead phone was running 'HashCheck Hybrid v2.2 ZHDMB1.t0lte' with Perseus kernel. Should it have been safe or no?
aka_sirok said:
and secondly, there are 2 ways of SDS the first is known as "soft" which allow to enter download. the second is the hard one and the one that OP may have.
hope it helped somehow
Click to expand...
Click to collapse
I see, so Hard SDS it was then.
Perseus kernel has the patch for sds added.
GT N7105 with XDA Premium......that is all......
sure but i readed somewhere that to be 100% safe it has to be kernel and recovery sds patched. if you had those patched both the ones that have the insane chip must be worried :S
Sent from my GT-N7100 using xda premium
I wonder if using cyanogenmod also end up the same? I mean this problem only caused by original firmware? if both is the same is there a reasonable solution for stock users? My wife has the phone for 2 months and I want to make sure she doesn't suffer the problem from the beginning. What are the measures I can take to avoid this problem?
maluus said:
I wonder if using cyanogenmod also end up the same? I mean this problem only caused by original firmware? if both is the same is there a reasonable solution for stock users? My wife has the phone for 2 months and I want to make sure she doesn't suffer the problem from the beginning. What are the measures I can take to avoid this problem?
Click to expand...
Click to collapse
it is a hardware problem. check the version of the chip with EMMC checker, 2 months old it's quite a good notice because it means newer chip probably.
Sent from my GT-N7100 using xda premium
Well hopefully. But while investigating the issue in internet I read 1-2 guys who have so called "sane" chips but still having freezes. I don't know if they really had the same issue or they had their phones bricked in the end but that caused me to doubt the safety of sane chips. I don't know.
Enviado desde mi One S usando Tapatalk 4
aka_sirok said:
sure but i readed somewhere that to be 100% safe it has to be kernel and recovery sds patched. if you had those patched both the ones that have the insane chip must be worried :S
Click to expand...
Click to collapse
That was my understanding too, I had Philz CWM Touch (cant remember which version, but I d/led and installed it last month) installed as well.
This was the version I was running:
N7100XXDMC3 N7100OLBDMD1 - Malaysia
maluus said:
Well hopefully. But while investigating the issue in internet I read 1-2 guys who have so called "sane" chips but still having freezes. I don't know if they really had the same issue or they had their phones bricked in the end but that caused me to doubt the safety of sane chips. I don't know.
Enviado desde mi One S usando Tapatalk 4
Click to expand...
Click to collapse
Checked it and my wife's is a "sane" chip.
I've had my nexus for a while now and as much as I enjoy using it there is a really big issue that keeps coming back. The touch sensitivity on my screen is terrible. It won't recognize half of my touches from time to time and its really frustrating. I have tried fixing it using the ts files and will work for a while then it will start with its issues again.
I also flashed almost every ROM I could think of trying to see if i t fixed the issue however it did not. I always flashed the unlock for the ts after so it would not stick in the new Roms hoping that it would get better. I have also done a full factory reset and wipe without any luck. Currently I'm running Android L lpv81( the second release) and I'm not ropted. I was using 4.4.4 with twrp earlier but it doesn't matter as long as I can get this touch issue fixed.
I looked around the forum for a while and used every fix I could find but none lasted long enough for me to enjoy it. I would really appreciate any help with this, I'm not afraid to mess around with some things to fix this issue.
My stock one year old Nexus will also occasionally not respond to my touch. Not enough to be really annoying.
Sent from my Nexus 7 using XDA Free mobile app
lmacmil said:
My stock one year old Nexus will also occasionally not respond to my touch. Not enough to be really annoying.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
It happens more often than not, in fact its enough to make typing hard and or frustrating at times. I have a feeling that it's a hardware issue, but unless there's a fix I'll just had the nexus 8 when our comes out.
Pilz said:
It happens more often than not, in fact its enough to make typing hard and or frustrating at times. I have a feeling that it's a hardware issue, but unless there's a fix I'll just had the nexus 8 when our comes out.
Click to expand...
Click to collapse
Some people just can't afford to pay for every new device out there and have to deal with a malfunctioning device or try to fix it.
We're so lucky we have a community behind us that solves our problems.
Here you are:
http://forum.xda-developers.com/showthread.php?t=2428133
Pilz said:
I've had my nexus for a while now and as much as I enjoy using it there is a really big issue that keeps coming back. The touch sensitivity on my screen is terrible. It won't recognize half of my touches from time to time and its really frustrating. I have tried fixing it using the ts files and will work for a while then it will start with its issues again.
I also flashed almost every ROM I could think of trying to see if i t fixed the issue however it did not. I always flashed the unlock for the ts after so it would not stick in the new Roms hoping that it would get better. I have also done a full factory reset and wipe without any luck. Currently I'm running Android L lpv81( the second release) and I'm not ropted. I was using 4.4.4 with twrp earlier but it doesn't matter as long as I can get this touch issue fixed.
I looked around the forum for a while and used every fix I could find but none lasted long enough for me to enjoy it. I would really appreciate any help with this, I'm not afraid to mess around with some things to fix this issue.
Click to expand...
Click to collapse
It's a hardware problem. RMA if possible.
If not possible, try the TS drivers that the above post likely links.
Aerowinder said:
It's a hardware problem. RMA if possible.
If not possible, try the TS drivers that the above post likely links.
Click to expand...
Click to collapse
I might have to RMA it, I've already tried all of the ts drivers. Do I send it to Asus?
Pilz said:
I might have to RMA it, I've already tried all of the ts drivers. Do I send it to Asus?
Click to expand...
Click to collapse
I sent mine to Google.
Aerowinder said:
I sent mine to Google.
Click to expand...
Click to collapse
Is there a link to where I get the info the the RMA process? I tried googling it, but it wasn't very helpful.
Pilz said:
Is there a link to where I get the info the the RMA process? I tried googling it, but it wasn't very helpful.
Click to expand...
Click to collapse
It's been a while since I did it, but I think you start here: https://support.google.com/googleplay/answer/2411741?ref_topic=3237699/#ts=4626603,4626497