Ok, first up I want to apologize for being a huge noob when it comes to smart phones, the Velocity is my first.
Ok, recently upgraded to stock ICS as was told by a Telstra store it would improve battery life.
Suffice to say I now need to charge my phone 2 times during the day, even with all non essential things turned off. Also while my 4g has picked up slighly, my 3g is almost non existent.
I work in a remote town and I usually dont have the luxury of charging the phone at noon, hence a dead phone by 1pm now (used to last all day fine)
Simply, I just want to take it back to the stock gingerbread it came with so I can at least use it again.
I have read through the forums for about 7 hours now, can't find what I need (noob remember)
I did find the holiday shipped rom collection post and D/L the RUU_HOLIDAY_SENSE3_5_Telstra_WWE_2.27.841.6_Radio_3.01.4720.09_3
file.
If I run it it wont do anything because its older than what is on the phone.
Found the instructions on how to turn it into a PH39IMG.zip file and loaded to a SD card. pretty much did the same thing at the hboot menu (older file)
Found out how to turn autoloader to unlock and did that, the sd card method now runs through (every file says missing or something though) till the end, but if you reboot its still ICS.
Yes, I have seen the super guide, but it seemed to be for AT&T phones, and being that i don't know much about them, I didnt want to go through it and be wrong.
I have been told it should be as simple as dl the ruu from HTC and running it, but HTC only have the ICS ruu for telstra phones, not the old GB version.
I have emailed both HTC and Telstra asking about it and no response.
Local telstra shop had conflicting info.. one guy said they could do it, but would cost $100, a different guy said no way to go back.
I'm hoping someone can show an extreme noob how to fix this, otherwise I'll have to look at buying a new phone as its pointless having this one for just half a day!
First of all, thank you for actually taking the time to read.
Second, anything in the superguide is applicable to your phone. Just replace any instances of ATT with Telstra, and you're good to go.
What you're going to have to do, if you want GB again, is to unlock your bootloader and fastboot flash a recovery image (ClockworkMod recovery will do), and then you can get a Telstra stock ROM zip from GB and flash that in recovery.
My other suggestion would have been to do the RUU method, but you've already tried that. I'm working under the presumption that your bootloader is locked, as the RUU method is guaranteed to fail if it is.
I'm curious, however, as to why ICS is using more battery on your device than GB did. That's not normal. Do me a favor, could you either screencap or read out what it says in your Settings -> Power -> Battery Use screen when your phone is nearly dead (14% battery or just an extended usage period). Something is very abnormal if you are getting worse battery life on ICS over GB.
Thanks very much for that,
Bootloader is unlocked (I think I said autoloader before, oops) Did it via the HTC unlock tool.
For a bit more info, I had an error 140 before I unlocked, and an error 155 afterwards. I did look up the error codes and the 155 seems to be a wrong version.
Will do a screen cap when I can for you, but from reading the Telstra forums and Whirlpool, it seems there are a lot of people with the same issue and more
(lower battery life, worse signal strength, tinny speaker on calls, call drops, random reboots on charging.. I only have the first 2 issues)
Most of them are looking for fixes for the issues, well.. complaining about them mostly. I think I'm one of the few that want to return to the old version.
As i said, I dont know a lot about them, and I know GB worked for me
EDIT: Get the Telstra stock rom.. is where I got the first one from ok, or is there somewhere else?
You CANNOT run an RUU with an unlocked bootloader, but that's another story for another day.
Do you have some form of recovery on it (CWM, WCX, TeamWin Touch)? If so, it's just a matter of finding a zip of the stock GB ROM. Else, you can use Jirv311 (I hope I spelled that right)'s method of compiling the stock RUU-based ROM posted on the development forum. I know a PH39IMG flash was made for ATT users, but I would advise against using that.
Per your question about ROM source, where did you find it exactly?
Worse comes to worst, just flash a custom GB ROM instead of a stock one if you can't find it. Holiraider is hella nice and gave me plenty of battery life.
By the by, if you choose a rooted ROM, I would heavily recommend to you to use SetCPU and underclock your phone. Search the HTC Dream G1's app board (under legacy devices), and you'll find a link. It's free to XDA members. On ICS, I have no problems ending the day at 50% battery, and that's with reasonably heavy use and my 3 email accounts checking mail at highest frequency.
Rom was from
http://forum.xda-developers.com/showthread.php?t=1338919&highlight=holiday+shipped+rom+collection
The link has a telstra GB rom there.
Have also read something about radios? From what I see that is what runs the phone signal side.. some threads have said that a RUU rollback wont change the radio version.. is that correct?
Well, doing some thread hopping I think I have done a proper rollback. Using mainly the superguide and associated links, I have unlocked the phone, think I have rooted it, flashed the Kernal and flashed the rom.
For some reason the only proper RUU/roms I could find wouldn't work, so have installed holiraider. I think I did it right because its running and usable on my phone now.
Unfortunately though, the issues I got when I upgraded to ICS are still there. Bad signal and battery life.
As a guide, I used to be able to have full 3g signal anywhere inside my house, now it fluctuates wildly, if I put my wife's phone alongside mine, hers is steady full signal, mine fluctuates between 0 and 3 bars.
Battery life: If left on screen locked, it seems to last overnight (8 hours)
As soon as you use it you can see the battery metre falling.
Sending a txt messages is using 2-3%, a post on facebook is about 5%
PRE ICS: Standby time about 32 hours, usable time: about 8-9hours
POST ICS: Standby time about 8-9 hours, usable time: anywhere from 4-6 hours.
I can only think with my limited knowledge that the signal fluctuating all the time may be what is chewing up the battery? (Bluetooth and wifi both off) And maybe the ICS update 'upgraded' something that the Holiraider rollback hasnt downgraded?
Same thing happened to me upgrading from GB to ICS. Turns out GoogleBackup was causing partial wakelocks, using both CPU and radio constantly. To check for this or anything else keeping your phone from sleeping, install and run BetterBatteryStats (free for xda users) from http://forum.xda-developers.com/showthread.php?t=1179809 and look at partial wakelocks.
Otherwise try checking a process monitor to look at what is active all the time, or perhaps use DroidWall to block internet access to apps that don't require it but may be using it.
Regarding the phone's signal, you'll have to go into the network status (in settings) to get numbers (IIRC correctly anything above -106dBm is a usable 3G signal). If this doesn't help, 2G will give you a better signal but it's not ideal. Nothing should be affecting your signal if you don't change the radio however.
Only major thing in the wake locks is alarm manager.
Signal goes from about 91db to 108db. Borrowed a friends phone and sits stable on about 85db.
I think the radio would have been updated when ics was installed. Can the radio be rolled back too?
Jaximus said:
Only major thing in the wake locks is alarm manager.
Signal goes from about 91db to 108db. Borrowed a friends phone and sits stable on about 85db.
I think the radio would have been updated when ics was installed. Can the radio be rolled back too?
Click to expand...
Click to collapse
Are you talking about the HTC Clock app, or did you install a third-party app by the name of Alarm Manager? If the latter's the case, you know what to do.
If the former is the case, you might just need to go to Settings -> Applications -> All -> Clock and clear its data.
Is your friend also on a Velocity? Different phones can have different readings based on random variables like interference and antenna placement.
Yeah, its just the HTC clock app. turned off the alarm earlier and its gone from the wake lock, but battery life hasnt changed. My last post was from the phone in question and it used 8% battery to type and post it.
Had a 15min phone call today too, used up 45% of my battery ( made sure to check before and after call.)
Nope, friends phone was a moterola Defy+
Thing is, I had this phone from a few days after they released here, so have been using it since Feb-ish on stock GB with no abnormal battery problems or signal problems.
Installed ICS and problems. Rollback to GB, still problems. I'm using the phone in the same area at home that had no issues before, so its gotta be something ICS, or at least Telstra's version of ICS, did to it.Since I still have the issue, its also gotta be something that didnt rollback with just flashing the rom..
Related
I was wondering if I was missing a post. I still get random Cyanogen Shut downs. I am using 4.2.13 after a wipe and still experience random shutdowns.
The phone just goes dark and I have to power it up again.
I have read some people attribute it to locked home screen and some people while using locale.
It is quite frustrating and I was wanting to know... if there isn't a fix, what Rom should I port back to. I need to clear this up because it gets aggravating missing calls.
Give superD 1.2 a try or even dwangs ROM they both are very speedy and well stable
Try re-flashing the rom, or you can try another rom as you said...i recommend Super D or WG Build....i myself use WG Build
You might be running out of system space.
Go to console:
$ su
# df
Check the Available next to /system. 28mb should be normal, but you could always apply the 10mb ramhack. Go with CFS for stability.
Can you recreate the scenario by which the phone will reboot on it's own and get a logcat?
No I cannot recreate it, it is very random. Afterwards I cannot logcat. I have tried wipe and reinstall of alot of his roms, all of them do the same thing.
I was hoping there was a fix because it is his rom I prefer.
I guess I will try another rom and maybe the problem will resolve itself.
Brutal-Force said:
No I cannot recreate it, it is very random. Afterwards I cannot logcat. I have tried wipe and reinstall of alot of his roms, all of them do the same thing.
I was hoping there was a fix because it is his rom I prefer.
I guess I will try another rom and maybe the problem will resolve itself.
Click to expand...
Click to collapse
Try Enoms rom if you tried Super D and WG-Build Y-2.6 with no success.
The problem you have is definitely weird.
I also suggest updating your Radio, Spl and RA Dream to the latest versions.
If possible try another microSD card preferably Class 6 to see if that fixes your problem.
I've been experiencing this same thing with random shut downs. I am running 4.2.13 also.
I have tried a wipe and re-install but the problem still exists.
There doesn't seem to be any rhyme or reason to it. The only thing I can say is that it always happens after the phone has been idle and when I go to pick it up it's powered down and I then need to power it back up.
It is very frustrating becuase you're never fully aware that the phone is off until you go to use it. I don't know if it's the ROM or some program that I've installed. I've been uninstalling all recent programs but so far the problem still exists. Perhaps I'll try one of the other recommended roms.
I have tried the stock rom and Dwangs rom, so I doubt its the ROM. Also I installed minimal applications and it still happens.
Its a toss-up between battery and phone. Although my battery is an extended battery, it can happen even when the battery is at 80%+ charge.
I called T-mo and they are going to swap out my phone. When I get it I will run the stock rom for a couple days with my Extended Battery. If it continues, I will put the stock battery back in it. Then I will go back and root it. If the problem comes back, then it has to be the rom.
Brutal-Force,
I'll eagerly wait your results. Unfortunately I purchased my G1 off of ebay a year ago so if it is the phone I'm out of luck.
Out of curiosity do you use Nitrodesk Touch down for Exchange? I've had some reboots right in the middle of synchronizing my email with this program.
Thanks
No I do not. As a matter of fact, I had uninstalled almost everything in an attempt to track down the culprit.
I really do think its gonna end up being the battery. Since the phone is not an option for you, I would recommend trying out a cheap 10 dollar battery off the internet. While I can't imagine why a charged battery would do this, I have noticed by looking at a friends G1 that the phone interprets batteries in different ways. In his phone his battery never showed below 90% even though after 10 hours it would run out of battery. As soon as he put in on the charger it showed 90%.
I to had purchased one of the extended batteries shortly after purchasing the phone. It has worked fine for just about a year but perhaps it is beginning to have problems. I'll dig out the original stock battery later today and try that for a day or so and see what happens.
Thanks
I have the same problem. My phone randomly restarts. It's more of an annoyance rather than a big problem, especially since it's almost always a restart and not a shutdown. If you guys do indeed find out it's the battery do post your findings here!
Thanks
I have exactly the same symptoms. Though before I saw this post I was attributing it to the fact that I have recently dropped my phone.
I also have a spare battery (I'm using Andida instead of original now), so I'll test to see if that happens with the original too.
Hmmm..
OK so i take out my extended battery and put in the original battery and plug it in to charge since it's on the low side. The phone immediately reboots and continues to do so indefinitely.
As soon as the home screen comes up it reboots.
So I put my extended battery back in and same thing. Now I'm not sure what to think so I've backed up my SD card and performed a complete wipe and am installing a completely different ROM.
I'm hoping it was the ROM or some program and not the phone.
I'll get back later.
rckeystone said:
Hmmm..
OK so i take out my extended battery and put in the original battery and plug it in to charge since it's on the low side. The phone immediately reboots and continues to do so indefinitely.
As soon as the home screen comes up it reboots.
So I put my extended battery back in and same thing. Now I'm not sure what to think so I've backed up my SD card and performed a complete wipe and am installing a completely different ROM.
I'm hoping it was the ROM or some program and not the phone.
I'll get back later.
Click to expand...
Click to collapse
Its good that you guys are investigating the cause of this issue. I too admitingly started using CM when I first rooted my phone. I too had issues and FCs so changing the Rom was the first thing that came to my mind.
You never know maybe its the battery (see the 1700 battery thread on the many problems Andidas has had with their G1 extended batteries)
In the end I am hopeful that you find a solution and have found out sometimes its as easy as changing Roms to fix many complaints/issues you might have.
This is what I've experienced so far.
I did a full wipe of my phone yesterday and installed the AOSP ROM (went away from cyanogen) and I have installed most of my programs. So far all is great. I've had no reboots or any other issues. Since yesterday I have been using my extended battery so I know the battery is OK.
I can't say for sure what was causing my issue. I had been using cyanogen's ROM for quite some time so I don't have a reason to think it was the ROM unless it was one of the current updates.
Perhaps I just had a collection of issues that came to a head and it was time to clean the phone and start over.
Same Problem
Hi, First post here. Great site by the way.
I am having the same problem as you are. Cyanogen, manup's 2.1 (1.5) and the "official tmobile 1.6" rom would frequently reboot or shut off on me. I tried three different sd cards and completely wiped my phone everytime i went between these roms. After much frustration I unrooted my phone last week and went to stock 1.6. It was working perfectly fine but the terrible battery life convinced me to try rooting my g1 again. After going through all the steps the same symptoms came back. So in order to be able to use my phone I went back to the stock unrooted rom. I also would like to mention that before these symptoms came up I had my phone rooted since may 2009. I also tried various SPL's and recoverys while trying to resolve my problem. Thanks
Random reboots are the reason why I don't run CM roms for any length of time anymore. I do load them from time to time to check it out and what not, but more often than not, I always find myself back on a Dwang rom.
My new G1 should be arriving tomorrow, but it has been 2-3 days now with the original battery. No shut downs. While it will be nice to have a new phone (although my phone is unblemished) it will suck to have to re-root it. I am pretty certain its the battery.
I will recheck when I get my new phone set up, I will put the extended battery back in it. I am still pretty certain it is the battery though.
I used to have random reboots on Nexus One, but after updating to Froyo 2.2 (before the official release), I had noticed the random reboots to get more (like 2-3 a day), but now the phone is totally useless, it does reboot constantly, and when it's connected to Power, it reboots couple of times, then gets stack at the Nexus logo.
I have put the stock firmware back, EPE54B, and it even detected 2.2 and Google pushed me the official release and still no go (yes, I did clear cache, etc)
I loaded up the log program and checked the logs after a reboot to see if it was some sort of kernel panic or something, but it does not show anything per say.
I even tried w/o SIM or w/o memory card and the results were not conclusive, it worked for some time, then started rebooting on its own. Sometimes I notice the phone is very hot, which makes me think that it might be faulty hardware (ram, etc)
Has anyone seen such an occurence, would HTC repair the device now the bootloader is unlocked or is this just a thin paper weight ? I think I read someplace that they still honor hardware repair...
Thanks,
Houman
Mine reboot when it overheats during charging. There are several overheating threads u should check out.
Sent from my Nexus One
Just be honest
houmi1 said:
I used to have random reboots on Nexus One, but after updating to Froyo 2.2 (before the official release), I had noticed the random reboots to get more (like 2-3 a day), but now the phone is totally useless, it does reboot constantly, and when it's connected to Power, it reboots couple of times, then gets stack at the Nexus logo.
I have put the stock firmware back, EPE54B, and it even detected 2.2 and Google pushed me the official release and still no go (yes, I did clear cache, etc)
I loaded up the log program and checked the logs after a reboot to see if it was some sort of kernel panic or something, but it does not show anything per say.
I even tried w/o SIM or w/o memory card and the results were not conclusive, it worked for some time, then started rebooting on its own. Sometimes I notice the phone is very hot, which makes me think that it might be faulty hardware (ram, etc)
Has anyone seen such an occurence, would HTC repair the device now the bootloader is unlocked or is this just a thin paper weight ? I think I read someplace that they still honor hardware repair...
Thanks,
Houman
Click to expand...
Click to collapse
From what I hear, if your honest and tell google that you unlocked your bootloader they will still repair your device, I don't know about replacing it if it can't be repaired. But before you go that route try troubleshooting. Make sure you have the correct radio, not all roms come with the correct radio. Non-compatible kernals can become a issue to, if you flashed a custom kernal. I get the bootloop problem if I flash a rom without wiping, which I never do, except when the instructions say no wipe required, and then I get the bootloop issue. So try a full wipe, data, dalvik & cache, ext, and then reflash your rom.
I had random reboots up the wazoo. My phone was unlocked/rooted/running FRF93. I downgraded to other versions of Froyo and even went back to 2.1/CM and it was still rebooting.
Turns out that HTC actually puts it through a reasonable testing procedure to determine if it was in fact the user that damaged the phone. So even if it is unlocked/rooted and the phone passes the test, you will get your repair free of charge just like me. I'm currently waiting for them to ship my phone back.
Although I have heard horror stories from HTC, so I really think it depends on the moon cycle...
Like a poster above said, BE HONEST. Let them know the truth that it's rooted/unlocked but currently running a standard ROM. If they give you the standard "if it's rooted, you're going to have to pay", tell them that you're heard of their testing procedure to determine if it's the user's fault. Go to a supervisor if you have to.
Hi,
Thank you all for the responses... so I decided to leave the battery out completely for one day, then put the battery in the phone, and I did quickly use the phone to wipe it as well as wiped the storage clean... so the phone should be back to regular day 1 status other than boot loader being unlocked. I guess by putting the PASSIMG.zip which has EPE54B files, I forgot, and it also flashed over the ramon recovery as well.
Then I turned off the phone but connected it to the charger and let it charge completely, this morning I turned on the phone and it has been on w/o reboots.
So this points to either heat, radio (wireless, 3g) -- it does not have a sim in it currently, but the good news is that it's not rebooting. I think I'll play with wireless first, then add 3g then we'll see where it takes me, but if it comes to returning it to HTC/Google, I'll be honest of course.
This has by the way:
Android Version: 2.2
Baseband: 32.36.00.28U_4.06.00.12_7
Kernel 2.6.32.9-27227-g3c98b0d
Build FRF91
houmi1 said:
Hi,
Thank you all for the responses... so I decided to leave the battery out completely for one day, then put the battery in the phone, and I did quickly use the phone to wipe it as well as wiped the storage clean... so the phone should be back to regular day 1 status other than boot loader being unlocked. I guess by putting the PASSIMG.zip which has EPE54B files, I forgot, and it also flashed over the ramon recovery as well.
Then I turned off the phone but connected it to the charger and let it charge completely, this morning I turned on the phone and it has been on w/o reboots.
So this points to either heat, radio (wireless, 3g) -- it does not have a sim in it currently, but the good news is that it's not rebooting. I think I'll play with wireless first, then add 3g then we'll see where it takes me, but if it comes to returning it to HTC/Google, I'll be honest of course.
This has by the way:
Android Version: 2.2
Baseband: 32.36.00.28U_4.06.00.12_7
Kernel 2.6.32.9-27227-g3c98b0d
Build FRF91
Click to expand...
Click to collapse
Any updates? I have a similar issue
Yeah I basically think it's heat related and unrelated to the firmware, RAM, etc.... I had the phone at a very cool place and it works perfectly, and when I started using it, as it got hot, it started rebooting, and I noticed the back of the phone was very hot.
So I think nxt was right #2 in this thread.
Houman
The above observation would seem to make sense. My phone would reboot while trying to watch youtube videos sometimes, but ALWAYS within a few minutes of using it on the mains...
I have since had it sent back to HTC to have the phone repaired. I had rooted my phone just to get 2.2 however as it was a genuine hardware issue they replaced the main board and now not only does the phone not reboot anymore, the issues I had with no 3G (only Edge) have disappeared too. Happy
BANE
Hi
So I got my phone back from htc, they basically fixed it and even locked the bootloader so all is well
Just FYI
Houman
I am running the stock V10c ROM with 0405 Baseband and root.
Until recently I had little to complain about, but since last Saturday my phone has a horrible battery drain.
It turns off within 6 hours after I unplugged it even tho I did not use it and it was sitting calm in my pocket. This happend for the third time now since Saturday.
I was suspecting the recently installed Vlingo or Google+ Apps, but after removing them I still have the same issue. I recalibrated the battery yesterday but the Phone turned off again today.
I recharged it just now and it got incredibly hot like it has never been before.... this is very strange.
Anyone else experiencing something similar?
Have there been any recently updated Apps that are said to cause battery problems (Google Maps got a recent Update...)?
Any suggestions?
(I hope that damn OTA update comes soon and fixes this otherwise I'll have to update it manually or will have to install a custom ROM.)
EDIT
I flashed MoDaCo's MCR Fr19 and the Problem is gone.
I guess a factory reset would have solved my problem as well, but since I had all the work with backing up and restoring anyway I have chosen to go with a nice custom ROM.
Everything works like a charm again!
I used to get horrible battery drain, and generally the battery stats would have a mind of their own and change at random..... sometimes a phone restart would fix this, sometimes not. This was the biggest problem I had with the phone, but by no means the only problem.
I was always on stock, but since flashing the newest Modaco ROM (FR19) I've not had a single problem, the phone actually works as the piece of high-tech gadgetry I expected it to in the beginning. It's been nearly 2 weeks since switching to a custom ROM, and finally I'm loving this phone. I was reluctant to do it earlier as I waiting for the official LG updates, but after all their tardiness I decided enough was enough and went Modaco.
My advice: if you're unhappy with the phone as it is, try at the very least 1 custom ROM (both Modaco and Cyanogen are popular) and see if it improves your experience.
I have this problem too sometime
Only solution is to turn off the phone and turn and everything become normal
But after sime day if use same happens again. I suspect there is a program start to run in bg non stop
Btw i am in fear edition 12.2
Sent from my LG-P990 using XDA App
Ermmm.... correct me if im wrong, but to my knowledge v10c roms uses 622 RIL.. which has a 622 basebnd too.. why are still on 405 baseband? I really recommend 622 baseband as its the least power hungry baseband I've used since 405, but then again, some other factors might affect ur battery too.. but alot of ppl give positive comments on 622 baseband
.. shld give it a try.
Sent from my LG-P990 using XDA Premium App
Thanks for your replies!
@Crofteh
I am generally a big fan of custom ROMs and always used one on my last android phone, but I liked the stock LG ROM enough to keep it until Gingerbread would arrive. I hoped to test official LG GB without wiping and then upgrade to a GB build of MoDaCo or CM.
That is what I thought, but who knows how long LG will still need for GB.
@Netuser
Thanks, I also suspect some App to uselessly run non stop as the phone feels warm near the camera, which indicated SoC load.
@tablights
I have the unbranded German version which came with a V10b ROM and a baseband number I forgot. After updating via the LG PC tool it changed to V10c and 0405 Baseband. Since that there was no official Baseband update for my phone. As far as I know, the German Vodafone branded phones got the 622 Baseband in last weeks update.
I will try to manually update to V10e via KDZ updater since it apparently does not wipe in the procedure.
Should the issue still persist I'll give MDC r19 a try.
I think the best bet to avoid the heating problem is to remove the micro SD card. Or try another one not greater than 8G. Don't use 16G or 32G - less costly for you if it burns out.
How is that related to the SD card? My 16GB card worked flawlessly all the time.
Same here
Hi,
I had exactly the same Problem, Phone got incredibly hot, was always warm even in airplane mode and died after 5h in stand-by. I tried all Basebands, different ROMs, reseted the battery stats several times, tried charging and uncharging several times. I logged the battery usage and got it down to maybe 20mA which should give me something like 75h in standby, still the phone shut off after 5-6h. I didn't use a SD-Card so it had nothing to do with that and it didn't change with different Software so i'm sorry to report: it may be a hardware problem. Either the battery broke or the handset itself didn't survive the temperature and is now draining (you could try another battery).
I sent my in and DHL lost the packet so no more Info from my side
btw, i also had the german version bought at Amazon.
Good luck finding the Problem !
I hope it won't be necessary to send it in. At the moment I am trying to rule out all possible causes. I signed out from the google labs project that lets you download parts of maps, since I activated that shortly before the problems begun and I could imagine that constantly downloading maps could cause high battery drain.
I have no time to do a custom ROM install including all backup and restore stuff atm as I am busy writing my diploma thesis for the next two weeks. But I will try that if nothing else helps. If that does not help, I will send it back.
Did you get an replacement or a refund?
If you got a replacement, does it have any issues like backlight bleeding ?
If you got a refund, did they pay the price you bought it for or the price it costs now? Cause there is a steep difference in price from then to now.
Juice Defender?
I had the problem and the problem is solved after I install juice defender.
I'm still in the process of getting a refund.
I think they will pay what i payed. But it is exhausting getting them to do anything and while i do that I'm back to my good old and terribly slow G1
Good luck with that!
Would be nice if you could let me know how this was resolved so that I can decide what is the best way to go should things not get better.
Thanks!
Hi Guys and Gals
Hoping someone can help meor point me to somewhere/one who can please
Recently picked up an i9000 which is on the orange network and was running:
PDA: i9000bvjm5
PHONE: i9000bvjm1
CSC: i9000orajm3
everything worked just fine, i was getting tons of battery life out of it in idle, until i noticed that when i had 'anti-shake' ticked in the camera mode, it wouldnt allow me to adjust the exposure, so i contacted samsung and they told me that upgrading my firmware to 2.3.3 via Kies would solve the problem, i promptly did so and yes, it fixed the problem (hurrah!)
HOWEVER!
i now have a much larger issue with my phone in that before updating the firmware it would eat about 5% of my battery in 24hrs if not in use
Now i need to charge this thing twice a day minimum even when im not using it!!! aaaaaaaarrrggghhh!
i've shut off all unneccessary services like background data etc etc etc still no help, digging into the battery stats themselves tells me its the android OS thats eating 78% of my battery, while its idling! WTF! previous to this it was the display that ate the battery, but it cant be that when the displays off can it!
How on earth can i get back to my original firmware (eclair) or update to a newer version where this problem is fixed please?
i am a bit of a nob/noob at this so please try to K.I.S.S.
I cant live like this!!!! lol
will a factory data reset do the trick? or doesn't that affect the firmware?
Any help greatly appreciated
Yours in desperation x
Dan
If you google "Android OS bug" you'll see that this is a common problem. You said you upgraded to 2.3.3, but I believe they didn't correct this issue until 2.3.5—although I may be wrong about that.
You can update to whatever firmware you want by flashing your phone. This will void your warranty. Likewise, you can flash back to 2.2 if you so please. You can flash your device using a program called Odin or Heimdall. Search for tutorials, you'll find plenty.
As for the actual bug, in my times of testing a ROM that was susceptable to the Android OS bug, I usually just restarted my phone and saw it go away. Clearing the cache may help as well, but I really couldn't say for sure. Try a simple reboot and see if the problem persists.
big props upichie!
i had exhaustively googled this problem before troubling you guys but it appears i was using the wrong words, doh!
alas im still none the wiser ( all the guides i can find 'assume' i know too much already about their terms for things and im lost
i turn my phone off, within 5 minutes of restarting it the OS is once again draining my battery completely
i clear my cache every 5 minutes and within 2 minutes its flippin eating me again
is odin or heindall another thing i install onto my pc (not my phone?) like kies to revert back to the old firmware? eclair 2.1 i had nailed! if it aint broke dont fix it, why dont i listen to myself!
and why the funk would they release a firmware that does this in the first place?
my head is spinning with the retardedness of all this, i come from a background where testing things exhaustively is part of the job, so i cant for the life of me understand why they would launch with something that sucks sooo bad!
im also at a slight disadvantage because i have the orange firmware and slightly different settings to most who have eclair, i think
jesus wept i just dont know anymore lol i think ill just throw the thing in the bin and go back to my old sony w810i cos that lasted 7 days on battery!
funk this firmware, funk this nonsense and funk this 12 hrs battery drain when not even using it, what a funkin palava!!!!
oh and funk you too samsung for telling me to upgrade my firmware you funkers!!!!!
im going to cry now lol
No worries! We've all been there. The terminology is confusing, but once you get a good grasp of it, you realize how simple it is to know what you need to know. I'm here to help.
Odin and Heimdall are programs for your PC, although I don't believe either need to be installed (they're just standalone executables). They both are programs designed to flash a new firmware onto your phone. You simply download the firmware files (for Odin it comes in 1 to 3 files, but Heimdall if I recall correctly only uses 1 file) and then use the program to flash the new firmware.
Just so you're aware, if your Android OS is showing a high percentage, that percentage will not go away until you fully recharge the phone, as it would keep the record of the Android OS previously draining your battery.
I'm honestly not entirely sure how to help you. You could download the app called BettterBatteryStats and do some digging to find out what is causing your phone to not be able to enter/maintain deep sleep (otherwise known as a "wakelock"), but you sound slightly inexperienced and probably wouldn't be thrilled with that idea.
Alternatively, is there any option in Kies to downgrade to 2.1 again? Maybe contact Samsung and see what they have to say. You upgraded from 2.1 to 2.3 because of their suggestion, and now your phone is getting unusable battery life. It only seems logical they'd have a way to downgrade.
If you have any questions about terminology, how things work, or anything at all related to your i9000, please do not hesitate to ask! We're here to help in any way that we can.
Try to flash xxjvt with semaphore 1.8.2 kernel. If i not use my i9000 just for calls/maild and music my battery lasts 2 days with 3g and wifi on.
Try to wipe your battery stats after a full charge.
Sent from my GT-I9000 using xda premium
Hello giuys
Here I am again, getting every day more and more dissapointed in this phone
Two weeks ago (or when the update was released) I updated to 32.2.A.0.224 hoping to get a better batterylife because previous build was giving me 2h SoT and a lot of bugs like random reboots and overheat all the time
I downloaded an algerian version from XPerifirm (one of the first to was released) and everything was fine (actually there was no much improvement of wich I was looking for, but it was a little better) but one day I can't connect to home wifi, cheking some things neither bluethoot, I had to reboot several times to make it work. Last weekend I downloaded another version from xperifirm (an SA version) and flashed again w/o problem, but the issue persist (started today), actually is worst because today I can't connect at all nor wifi or bluethoot .... I tried Hotspot but can't turn it on too... The screenshots below shows what happens when try to turn on wifi, bt and hotspot
Any ideas how to fix this? I was thinking on simply root and get a custom rom, but almost every custom rom is rooted and there are some games I play a lot and can't be played with root (and root cloack and every tool doesn't work), so is not an option, I'm so frustrated with this phone, hope one of u guys can help me
thanks in advance
I guess you got the wrong modem on that rom, may be you wasn't supposed to flash it.
So, you are frustated with this phone because you flashed a version that was not supposed to be installed on your phone? You mixed up your phone, not the phone itself. You are complaining about SOT and overheating without mentioning how you use your phone. Well, i guess, if you can flass another version rom in your phone, i think you have done more than this..!
Anyway, i hope someone expert can help you. But you have to admit that maybe it is your fault and not accuse the phone
It just was an expression, but as a note, the phone is unusable since the beginning, every update mess one more thing, is the crapiest phone I ever had xD, two months later I bought a real flagship phone, but need this phone working for a not advanced user (that doesn't know or have the time to flash and install all apps over and over again), and every rom installed brings problems that make the phone useless as your post[\s], sometimes battery of 5h in standby, sometimes overheat all the time, sometimes random reboots...
Also genius, actually this phone came with the first customization I flashed, but if u didn't know, all customizations are the same, just came with some apps and market restrictions (plus carrier apps/ settings in carrier specifics) so there's no "version that was not supposed to be installed in your phone" (u can even flash between variants in the same model as long as is a single-sim variant), go home and learn something before u comment so useless things, I understand why there are so low population lately in xda, remember when ppl actually came to help QQ
Anyways, this issue was there since before in some devices (Z3+ obviously) in old updates, I was trying to get some info with that ppl to see if there's a way to solve it, but due limitations at not rooted phones I think there's no way...
Another thing, in the second last update, there's a thread about some issues bootloader/security-related if u updated via OTA, there's a problem if I try to flash am older version after that OTA was installed? because I think the phone was a little more stable before that
Sent from my SM-G935F using XDA-Developers mobile app
Hi, I recently bought this phone and found out the cell reception has some issue and due to that phone keeps on searching network and draining my battery.
I didn't start cursing sony or this phone because I knew there is some issue with the radio and it needs to be replaced and I went to service center and they told me that motherboard needs to be changed.
It's been 1 week still I am waiting but with the new motherboard I think things will be fine.
So why don't you visit sony service center and try to fix things instead of blaming them.
mohitgalaxy3 said:
Hi, I recently bought this phone and found out the cell reception has some issue and due to that phone keeps on searching network and draining my battery.
I didn't start cursing sony or this phone because I knew there is some issue with the radio and it needs to be replaced and I went to service center and they told me that motherboard needs to be changed.
It's been 1 week still I am waiting but with the new motherboard I think things will be fine.
So why don't you visit sony service center and try to fix things instead of blaming them.
Click to expand...
Click to collapse
Don't misunderstand me, I love Sony phones and used it since W300-SE years, this phone have issues, sad is, service center actually doesn't give service if u don't buy the phone with the carrier they are (it seems the carrier pay to have service of almost all brands), and they sell phones (specially flagships) overpriced (like 150usd more) so I don't buy with them, neither use that carrier, so is a little hard
Sent from my SM-G935F using XDA-Developers mobile app