Database Users

Network usage sprocess 0

This process keeps draining my battery like hell.
I couldnt find anything on this.
Does anyone know how to fix that?
Sent from my GT-I9000 using XDA App

Bump
Sent from my GT-I9000 using XDA App

I was told that 0 is Android C2DM process. Compulsory for Froyo. No way to remove.
Sent from my GT-I9000 using XDA App

ANGRY......................................................................
!0

But why r only some ppl experiencing this issue??
Sent from my GT-I9000 using XDA App

Bump
Sent from my GT-I9000 using XDA App

SammyGalax said:
Bump
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Even if you keep bumping it, it doesnt make it in any less in wrong forum, or well, not very good question.

SammyGalax said:
This process keeps draining my battery like hell.
I couldnt find anything on this.
Does anyone know how to fix that?
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Firstly how did you come to that conclusion?
Secondly, how do you know that process isn't doing a lot of needed work? After all, Dalvik drains a huge amount of battery too. Without it though, the phone is pointless..

SammyGalax said:
But why r only some ppl experiencing this issue??
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I have 0 but battery life is normal. Just because the bar is full, it doesn't even indicate that it took much power. You might have other factors to consider for the poor battery life.
Sent from my GT-I9000 using XDA App

Ive come to the conclusion because:
Once the process didnt show up and i had like double battery life.
The proceess also doesnt show up on every sgs, and ppl who got the process r also complaing about battery life (most of them)
I believe it has something to do with rootinga
Sent from my GT-I9000 using XDA App

Process 0 is a normal system process. Nothing to get worried about.
http://forum.xda-developers.com/showpost.php?p=9563222&postcount=4035

hardcore said:
Process 0 is a normal system process. Nothing to get worried about.
http://forum.xda-developers.com/showpost.php?p=9563222&postcount=4035
Click to expand...
Click to collapse
But the reactions differ, do only some kernel/fw have this 'bug' ?
Sent from my GT-I9000 using XDA App

Bump
Sent from my GT-I9000 using XDA App

SammyGalax said:
Bump
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
STOP BUMPING THIS! It's damned annoying.
Secondly, it may be caused by a broken application, or something else. The best way to learn more is to run proper tests. Remember, a few guys might "have this problem", but that doesn't mean the firmware is faulty. There are also people here who are saying that there is no GPS problem, and that Google Maps/MyTracks is faulty. Just because someone says something, doesn't mean it's accurate.
Process 0 may be sucking up your battery life, but if you want to solve the mystery, spend your time running tests to isolate what causes it, don't spend your time bumping a thread. .

Bump
Sent from my GT-I9000 using XDA App

Have you test to flash the rom after backing up your data ?
Maybe this could solve the problem !
Because bumping and bumping is simply useless !!

In fact, I have just tried. A full reflash, repartition on Odin using DXJPE firmware (latest SEA firmware).
Without rooting, or any apps being installed or any custom kernel, '0' process was seen active immediately after the first reboot.
Pretty much we can assume it is a designated Android process.

I'm pretty sure I read somewhere 2.2.1 hides system processes like "0" in settings, they're still there, just not shown. You can see their stats in spare parts though/

HD2 Randomly Shuts Off

My HD2 has been randomly shutting off with no apparent cause.
About 3 weeks before I used the new HD2 Tool Kit to partition the magldr to 445 and installed the same rom I was previously using which was HD2Nexus Gingerbread nand 2.8.
Since this started I have updated to version 2.9 and tried repartitioning magldr with no avail.
It has only done it once while I was while I was using it once. It normally happens while sitting in standby.
Any ideas guys? Thanks.
Sent from my Nexus One using XDA App

I made a mistake when I said shuts down, its a reboot.
Sent from my Nexus One using XDA App

halo117 said:
My HD2 has been randomly shutting off with no apparent cause.
About 3 weeks before I used the new HD2 Tool Kit to partition the magldr to 445 and installed the same rom I was previously using which was HD2Nexus Gingerbread nand 2.8.
Since this started I have updated to version 2.9 and tried repartitioning magldr with no avail.
It has only done it once while I was while I was using it once. It normally happens while sitting in standby.
Any ideas guys? Thanks.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Why such a huge partition on a Nexus ROM?
I would repartition to 150mb, then flash that ROM and see how you do (wipe everything then restore your apps)

I will try that when I get home. My thinking was the bigger the better. Wasn't thinking I maybe using up important space.
Sent from my Nexus One using XDA App

halo117 said:
I will try that when I get home. My thinking was the bigger the better. Wasn't thinking I maybe using up important space.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
The less the partition, the more space you have for installing apps and stuff. The thing is that Sense ROMs (especially DHD and Sense3) require more for the system partition so you have to flash a 300 or 450 MB partition respectively. Any AOSP ROM, including straight nexus port or CM7, doesn't need more than 150 for the system.

So I repartitioned to 150 and it, or so I think, seemed to help but it did it about an hour after and it seems to be happening more often now.
Any other things to try?

halo117 said:
So I repartitioned to 150 and it, or so I think, seemed to help but it did it about an hour after and it seems to be happening more often now.
Any other things to try?
Click to expand...
Click to collapse
Different ROM
Sent from my HTC HD2 using XDA App

So I have found the fix for the random rebooting on my HD2.
Apparently, my sim card was causing the issue, which T-mobile will replace for free. I got the new one 12 hours ago and the phone rebooted as I walked in the door, but hasn't since I put in the new sim card. I'm just happy it's finally over and the fix was FREE! Hope this helps others in the future.
Sent from my Nexus One using XDA App

halo117 said:
So I have found the fix for the random rebooting on my HD2.
Apparently, my sim card was causing the issue, which T-mobile will replace for free. I got the new one 12 hours ago and the phone rebooted as I walked in the door, but hasn't since I put in the new sim card. I'm just happy it's finally over and the fix was FREE! Hope this helps others in the future.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Good call and thanks for possibly another free solution to resets!

Random reboots alot....

Okay my girlfriend's atrix reboots almost ten times an hour.....during a phone call it reboots sending/receiving texts or just sitting there probably getting background data. I had her get a new battery cause she had some **** off brand in it....didn't work...now she told me she washed her last atrix and got it replaced so im thinking she got her sim wet and that's why its rebooting or its hardware end....phone is completely stock not rooted...any ideas? Thanks in advance
Sent from my DROID3 using Tapatalk

Unlock it root it and a custom rom fixed mine it did the same thing not as much as hers but still had a lot of random reboots on stock gb .now maybe one random reboot a month
Sent from my MB860 using xda premium

I wouldn't be so fast to unlock the bootloader. A phone that reboots that often most likely has hardware issues. Stock ROMs have issues, but not that radical.
Feed her a nice dinner and get her to come clean as to the evil thing she did to her phone. If there really have been no mishaps, get a warranty replacement. My advice is to not do anything to the phone that would make getting a replacement difficult.
Good Luck

Lol she told me what happened with her first one she gott replaced she washed it....so she got a new one that one rebooted...then she got another and its also rebooting
Sent from my DROID3 using Tapatalk

I would tell u to download a gingerbread fruit cake, moto-fastboot, and do a complete wipe including system, data, webtop, preinstall, cache and boot. (Boot=kernel) then do a fastboot reboot into recovery and flash the 2.3.4 fruit cake. If u need detailed instructions on how to do this and where to get files pm me.
Sent from my MB860 using Tapatalk

Ten times a day is a frigging lot. I used to have random reboots with group but it was more like twice a day. Sometimes it would not boot up again until I did a battery pull......but flagging to Gingerbread solved all these errors. No random reboots or any problem at all since.
Sent from my MB860 using XDA App

Jibraldor said:
Ten times a day is a frigging lot. I used to have random reboots with group but it was more like twice a day. Sometimes it would not boot up again until I did a battery pull......but flagging to Gingerbread solved all these errors. No random reboots or any problem at all since.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Sorry, what does "flagging to GB" mean?
Sent from my MB860 using xda premium

rlillard said:
Sorry, what does "flagging to GB" mean?
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
I meant to write Flashing to gingerbread. Sorry for the typo, I am Swyping from my phone.
Sent from my MB860 using XDA App

Funny thing is she's on the gb ota...she's outta town for the weekend I think on Monday we are gonna try a new sim that doesn't work.....another replacement....ill keep you all updated incase there's another case of this!
Sent from my DROID3 using Tapatalk

I thought "flagging" to be British slang.
The conclusion I would make from reading this thread is that while many if not the majority of frequent and seemingly random reboots are failed h/w, another failure mode is corruption of the installed kernel and/or support utilities (collectively called the OS). Re-flashing any of the various ROMs will clear the problem.
If f/w corruption is the actual problem,flashing anything requires unlocking the bootloader. If a replacement phone is an option, I would do that rather than risk unlocking the boot loader and then not being able to return it.

[Q] BAD SECTORs when connected to win7 Atrix 4G

Well, as the title states, i have "bad sectors" on my Internal HDD.
I'm going to Restore System via MOTOCAST and hope that helps.
Anyone else with similar issues?

Bad sectors are a physical flaw. Sometimes a sign of impending disk failure bot not always. I have a pc drive with bad sectors out of the box, still going strong after 2 years.
I'd try and get the phone replaced.
Sent from my MB860 using xda premium

andri2805 said:
Well, as the title states, i have "bad sectors" on my Internal HDD.
I'm going to Restore System via MOTOCAST and hope that helps.
Anyone else with similar issues?
Click to expand...
Click to collapse
I'd like to know how its connected to cm7, do you have proof? I've been running CM7 since released and have not had any such problem!
Sent from my MB860 using xda premium

msd24200 said:
I'd like to know how its connected to cm7, do you have proof? I've been running CM7 since released and have not had any such problem!
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Where did he mention cm7?/

In my case, bad sectors= bad news. My hard disk died because of that.
If you can get the handset replaced, don't waste anymore time else it might/will become unusable.

msd24200 said:
I'd like to know how its connected to cm7, do you have proof? I've been running CM7 since released and have not had any such problem!
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Guessing you misread win[dows]7 as cm7 in title
Sent from my MB860 using xda premium

xhazk said:
Bad sectors are a physical flaw. Sometimes a sign of impending disk failure bot not always. I have a pc drive with bad sectors out of the box, still going strong after 2 years.
I'd try and get the phone replaced.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Thanks, am in the process of getting my 20 day old Atrix serviced. Or should I DEMAND a replacement as I've no idea whether they'll just "reset" the HDD?
after all the BAD SECTORS warning only popped out once... How can I tell if it's truly buggered?
Sent from my MB860 using xda premium

xhazk said:
Guessing you misread win[dows]7 as cm7 in title
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Sure did!
Sent from my MB860 using xda premium

andri2805 said:
Thanks, am in the process of getting my 20 day old Atrix serviced. Or should I DEMAND a replacement as I've no idea whether they'll just "reset" the HDD?
after all the BAD SECTORS warning only popped out once... How can I tell if it's truly buggered?
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
What are you using specifically to detect disk corruptions? I'm not particularly familiar with Windows... is it a builtin tool?
Ideally you'd ask them to check for disk corruptions, but REALISTICALLY they'll usually check if its bricked or blatantly damaged... and if not send it back to you untouched. This has been my experience over the years.
So in short, never hesitate on a replacement. Your data isn't of much concern to Jow Bloe, tech specialist 17447-b.
(No slight intended toward the folks in this industry, just being practical.)
Sent from my MB860 using xda premium

After connecting via USB, both internal & SD memory usually gets detected by Windows.
You have the option to sync pics/data/view files (plus installed MotoCast PC pops up).
This time i got a warning 'MB860 contains BAD SECTORS. Run checkdisk to fix problem'.
After i did the 'Scan for and attempt recovery of bad sectors' the device seems OK...
but i get all kinds of horror stories on the net..

andri2805 said:
After connecting via USB, both internal & SD memory usually gets detected by Windows.
You have the option to sync pics/data/view files (plus installed MotoCast PC pops up).
This time i got a warning 'MB860 contains BAD SECTORS. Run checkdisk to fix problem'.
After i did the 'Scan for and attempt recovery of bad sectors' the device seems OK...
but i get all kinds of horror stories on the net..
Click to expand...
Click to collapse
That doesn't sound like a genuine Windows error to me. There is a nasty bit of spyware that is going round that does that exact error, or very similar wording.
The only way you'll know that if it genuinely does have bad sectors is by scanning the memory (sdcard/sdcard-ext), or looking in the event viewer for disk errors saying that the memory has a bad block.
Windows often pops up a "Scan and fix" window if you remove the drive (sdcard/sdcard-ext) while its working, or stick it in XP and then plug it back into 7.
Can you post a screen shot?

It hasn't happened for 6 days. It is most noticable when you use USB MotoCast and backup internal HDD.
Just like any HDD,once corrupted,takes AGES to transfer small amounts of data. (I.e 5min for the ˝final 1% / 1sec" ).
The error message is "Windows has encountered an error with your disk. The drive contains BAD SECTORS and needs to be fixed in order to continue. 1.Scan for file errors. 2.Search and fix bad sectors." Or something along those lines.
Quite upsetting!
Sent from my A70S using xda premium

Update, Motorola support replaces the main board on affected models.
Thank goodness for MotoCast backup.
Sent from my MotoMB511 using xda premium

The New leak 4.2.1 doesn't have the sudden death fix

For my surprise today my phone don't respond, I left charging with the travel adapter, no boot, no Samsung logo, no recovery no download mode, maybe Is a sudden death problem :'(
I put my battery in the my wife's S3, and the battery is fully charged.
This is my last configuration:
Wanamlite rom 6.0
Philz touch recovery 4.63
Stock kernel (rom's kernel)
Last bootloader with the red light I in the upper left corner.
Enviado desde mi E15a usando Tapatalk 2

You should have been protected from Phil recovery perhaps that line of kernel code doesn't fix SDS after all.
Sent from my GT-I9300 using xda premium

no, philz recovery would only protect him while he was in the recovery

delsus said:
You should have been protected from Phil recovery perhaps that line of kernel code doesn't fix SDS after all.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
So? what went wrong Mr. delsus?

This is very concerning but let's not jump to conclusions too fast, shall we? People would freak out.
Maybe someone can look over the leaked kernel and search for the SDS string (Movi ops or something ).
Sent from my GT-I9300 using Tapatalk 2

No source, no strings... They said. (I already asked)
Sent from my GT-I9300 using xda premium

Glebun said:
no, philz recovery would only protect him while he was in the recovery
Click to expand...
Click to collapse
Makes sense, so the real need for the fix in recovery isn't really needed, the chances of SDS in recovery are almost none existent.
Sent from my GT-I9300 using xda premium

delsus said:
Makes sense, so the real need for the fix in recovery isn't really needed, the chances of SDS in recovery are almost none existent.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Of course they are existent... What if you are running a Nandroid Backup or you're installing a new ROM...
Those two activities take more I/O Requests to the memory chip than the "Normal" usage of the phone, you are reading and writting to the memory like crazy...
So the recovery fix is completely needed my friend...

jimbo77 said:
Of course they are existent... What if you are running a Nandroid Backup or you're installing a new ROM...
Those two activities take more I/O Requests to the memory chip than the "Normal" usage of the phone, you are reading and writting to the memory like crazy...
So the recovery fix is completely needed my friend...
Click to expand...
Click to collapse
The majority of reports of SDS are whilst they are charging, also unless you flash more than 4 times a day you don't spend much time in recovery.
I haven't seen anything to say the amount of read/write requests affect SDS, its not the only thing that can make your NAND fail.
Sent from my GT-I9300 using xda premium

Must.... flash..... back..... to.... sds....safe....romm...
Oh wait, warranty .
Sent from my GT-I9300 using xda premium

How old was your phone? Are you sure your memory wasn't damaged enough before the fixes got launched?
I can't figure out why Samsung shouldn't fix it for that 4.2.1 build. Maybe to screw leakers?
Sent from my GT-I9300 using xda app-developers app

delsus said:
The majority of reports of SDS are whilst they are charging, also unless you flash more than 4 times a day you don't spend much time in recovery.
I haven't seen anything to say the amount of read/write requests affect SDS, its not the only thing that can make your NAND fail.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
But Jimbo is correct - we don't know what causes the SDS but there is a very real possibility of a higher risk on more intensive IO operations.
This does not depend on time but rather on the wear of the EMMC, it has been theorized that the wear leveler is again at fault (like on S2 superbrick)
Recovery and restore are maybe the most intensive IO operations (besides installing AND the transcoding - which is seemingly done while charging, remember the Video Player CPU usage on that state... maybe that's the reason why it manifested... but I cannot tell for sure).

htcsnap93 said:
Must.... flash..... back..... to.... sds....safe....romm...
Oh wait, warranty .
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
LOL !!!

so what about someone unpacking the kernel and find if this lines r in drivers/mmc/core/mmc.c and mmc_ops.c
https://github.com/AndreiLux/Perseus-S3/commit/54ddcbe7aff1c19c07f76a05ab45f37bcbae2951

t0n0n said:
How old was your phone? Are you sure your memory wasn't damaged enough before the fixes got launched?
I can't figure out why Samsung shouldn't fix it for that 4.2.1 build. Maybe to screw leakers?
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Now you speak of memory, comes to my mind that this rom has a swap memory partition, if you type "free" on the terminal emulator, you can see it.
I bought the phone on june 1, 2012.

delsus said:
The majority of reports of SDS are whilst they are charging, also unless you flash more than 4 times a day you don't spend much time in recovery.
I haven't seen anything to say the amount of read/write requests affect SDS, its not the only thing that can make your NAND fail.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Exactly. It is the correlation between charging and SDS which is quite apparent when analyzing the data thread that has led me to speculate that the factory charger may be responsible for this, or at the very least be exacerbating the situation. I've never used the stock charger, (mine is still in the box and I'm using the SII charger) but there are several reports of fried USB cables, etc. when using the stock charger, so I don't think it too far-fetched that they could be related somehow.

donalgodon said:
Exactly. It is the correlation between charging and SDS which is quite apparent when analyzing the data thread that has led me to speculate that the factory charger may be responsible for this, or at the very least be exacerbating the situation. I've never used the stock charger, (mine is still in the box and I'm using the SII charger) but there are several reports of fried USB cables, etc. when using the stock charger, so I don't think it too far-fetched that they could be related somehow.
Click to expand...
Click to collapse
stock charger has nothing to do with SDS its bug in the eMMC firmware :silly:

they would've issued a statement about it it though, because it would've saved a lot of phones

yahyoh said:
stock charger has nothing to do with SDS its bug in the eMMC firmware :silly:
Click to expand...
Click to collapse
Yup, the thing is, apparently there is a TranscodeService for the Video Player that is triggered to start on charge, the operation should be IO intensive. That could be a valid co-relation. But the charger itself does not have any influence from what developers have gathered, it is a defect in the eMMC firmware.

This is really an great discussion
I wanted to know if I flash with any other kernel instead of stock, will there be even problem on leak
Sent from my GT-I9300 using xda app-developers app