• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Problem: i7500 Randomly Shutting Itself Off

D

Deleted User

Guest
1.) Model Number ? Galaxy
2.) Firmware Version ? 1.5
3.) Baseband Version ? I7500XXIG8
4.) Kernel Version ? 2.6.27 hudson@andy #1
5.) Build Number ? 76XXCSDCBALUM6375

Also do you have a T-Mobile Data plan on your
PayAsYouGo or FlexPay Plan? No

Carrier ? Unlocked phone. Used on O2 bill pay in Ireland

Country you are using your phone in ? Ireland

Hey all. I got my Galaxy last week. Having a problem with it in the past few days. At random intervals it powers itself down. It usually powers itself up, but this morning it didn't....so I slept in for work because I had no alarm!

I got the phone on Friday, and upgraded to firmware 1.5 straight away, so not sure if the problem is a firmware one or not...can anyone help?
 
Hmm someone in another forum said its a problem with the new firmware :-/

And I got the info from:

the::unwired forum / FIRMWARE: Samsung prepares for Samsung GT-I7500 Galaxy ROM Update

Content:

***** Update not recommended!!! *****

The update will

1. Kill your modem functionality
2. Make the device unstable (a couple of spontaneous reboots a day)
3. Make some apps on the market unavailable (allegedly those with copy protection enabled)
4. Not bring *any* obvious improvements

All these issues have been extensively discussed on O2 Samsung Galaxy - I7500 Forum - Android-Hilfe.de and do not reflect just a single person's experience.


So again:

***** DO NOT UPGRADE THE DEVICE WITH FIRMWARE VERSION I7500VIAIG6 *****
 
Upvote 0
Hejj I got the same problem (mentioned it before in a different topic)

My galaxy also killed itself very often (not to power on anymore) for me to notice only when i tried to on the phone :(

anyway it happens more often when i got Bluetooth on.

Must say that after the update it almost seems to have gone.
 
Upvote 0
rosboy, were u able to get PC studio to work? I keep getting unsuported device, even in USB debug mode :(

Eventually. I saw the the other forum that you have Win7...I have the same. It won't work with that. I had to install Vista as a secondary boot OS option. It would then only work when I enabled the USB debug mode.

I successfully updated the firmware (even though I now wish I hadn't!), but now the software says the phone is unsupported. It shows the phone icon and the two drives, but I can't access the phone.
 
Upvote 0
I tried it on XP as well, but after the update :(

I've just restored the factory defaults. The phone is much quicker now. Much more responsive than when I had the newer firmware installed.

I still can't connect to NPS using XP though. It sees the phone, but it comes up as an unrecognized device.

I'll try it on Vista when I get home from work to see if it works ok.

And I got the info from:

the::unwired forum / FIRMWARE: Samsung prepares for Samsung GT-I7500 Galaxy ROM Update

Content:

***** Update not recommended!!! *****

The update will

1. Kill your modem functionality
2. Make the device unstable (a couple of spontaneous reboots a day)
3. Make some apps on the market unavailable (allegedly those with copy protection enabled)
4. Not bring *any* obvious improvements

All these issues have been extensively discussed on O2 Samsung Galaxy - I7500 Forum - Android-Hilfe.de and do not reflect just a single person's experience.


So again:

***** DO NOT UPGRADE THE DEVICE WITH FIRMWARE VERSION I7500VIAIG6 *****

Thanks Chrisp7. Unfortunately I upgraded without researching (as far as I'm aware upgrading firmware is the right thing to do 99 times out of 100), so was left with the problem. Hopefully its resolved now. Will know in a few days and will let everyone know.

Thanks also for the link to the other forum. Will keep an eye on that one as well as this one.
 
Upvote 0
I've just restored the factory defaults. The phone is much quicker now. Much more responsive than when I had the newer firmware installed.

I still can't connect to NPS using XP though. It sees the phone, but it comes up as an unrecognized device.

First of all, hi to everybody, i'm glad to join this community.

@rosboy I don't think reseting to factory settings will downgrade you to the old firmware, thus the problem with "unsupported device" is still there. Seems that everybody who upgraded are getting this message now.. as if till there's no newer update wouldn't be supported again.

But of course is more responsive.. You've got rid of all the junk you've been installing/uninstalling! :)

I've got the same problem of the Galaxy turning off and on at random times, and without asking for the PIN number. Sometimes when installing an application, sometimes after havey use.... sometimes while laying on the table. And it also started AFTER the update.

Just one thing: mine doesn't shut off but reboots

@FLT i guess when it completely shuts off it's because it has ran out of battery (probably to battery consuming resets during the night). As it hasn't happened to me... can anyone confirm that after switching it on again it has no or really little battery?

But, just as a side opinion, battery life has improved a lot. So i still prefer those little gaps when i can't use the phone (matter of seconds) but at least being able to use it longer.

It's not the way I want it to be, but it is still better... and I hope/demand it will get fixed soon.

Greetings from Germany!
 
Upvote 0
I have background data off, and auto sync off. I dont get any resets anymore, and i get alot better battery life - but of course no auto syncing!

I noticed when the wifi is on, and you're on a 3g call, it disconnects you when it tries to sync (probably dropping what it thinks is a 3g data connection to use the wifi).

There is a restore partition and a restore ramdisk. This is what restores the phone when you do a factory reset. When you update the firmware, this gets replaced with the latest restore for that firmware. This is so when you ever do a factory reset again you get back to the same latest firmware again.

You can extract these ramdisks from the firmware update file, but unfortunatly there wasnt a firmware file for the first firmware. And if there was we could just have used that to downgrade!

Another way to get the old ramdisk would be to root an old firmware phone, and dd the partition to a file on the sdcard and pull it off. But the current way to root the phone requires a modified restore ramdisk and so requires you to overwrite the ramdisk on the phone with a new one. Since we only have the ramdisk from the new firmware that we can modify in the first place, its chicken or egg situation :(

The last way is to root an old firmware phone - which would end up with new restore partition, but OLD firmware running on the actual phone. Then take a system dump. Share this system dump and restore it to other peoples phones.

Someone posted a system dump on xda dev, but it wasnt a complete one - this is because at the time they werent looking to do a downgrade but to copy new android stuff from the samsung build.

I'm not sure if this method would work for sure (i.e. does the restore procedure generate phone specific info on the phone?).

All in all it looks like its just easier to wait for a new firmware!
 
Upvote 0
My phone (updated, baseband=I7500XXIG8) also reboots in average once per day. It always happens when I'm not using it - I hear the boot sound from my pocket.

It doesn't seem to be connected with wifi, gps, 2g or 3g.

Just now it rebooted, and came to life with more battery than before. This particularly drives me nuts, cause while I find it reasonable to believe that this rebooting can be fixed with firmware update, the battery behavior is simply scaring me. The battery also shows wrong temperature (currently 2.3 degrees Celsius, room temperature is 25 degrees). Ok, I read somewhere that this is due to wrong Fahrenheit to Celsius conversion (which is, well, stupid), but for Li-Ion batteries temperature management is important. I just hope that this stupidity happens only in gui and that there is no freaky temperature management code in kernel...

Back to reboots.

I thought that it has something to do with apps that I installed. So far I uninstalled Steel, Obscura, Useful Switches, but it did not help.

After last reboot I uninstalled also Astrid, will see what happens.

Basically I uninstalled all apps which had - or at least I thought they might have - deeper influence on the phone, registering handlers for various intents. The only "deep" application I still have is Calling Card (intercepts outgoing calls, I need it for calling abroad). Reboot never happened during call, I said already that it always reboots in my pocket. No difference between trousers and shirt pocket, I'm getting paranoid...
 
Upvote 0
Hmm... now I remember: during startup - cannot remember was it before or after I enterd the pin - I got the message "core.android is not responding. [Force close] [Cancel]".
I clicked on cancel, and everything was ok.
I gues the phone was only busy starting up all processes. I never had crash core.android... yet.

Current uptime: 17 hours.
 
Upvote 0
I just rebooted again... there goes my astrid-is-guilty theory...

After entering pin, I was greeted with an "android.process.acore not responding". This time I clicked on force close, and home screen restarted.

So I was wrong in my last post - it was not "core.android".

It restarted after 18:45 hours. Battery: 87% - ~30 minutes before reboot it was around 82%...
 
Upvote 0
Hi, I installed the new firmware too without noticing the drawbacks it has, and now I'm suffering them. First of all, when I start the phone, I cannot even insert my PIN because the phone's touchscreen starts locked (as usual) but the lock/unlock button will do nothing!!! How could I do? This is only my second day with the phone, please someone help! :-(
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones