Battery is getting hot. 40°C/104°F every time.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Use latest System.img & Boot.img 236MB
2. Let my phone always connected via usb at my computer.
3.

What is the expected output? What do you see instead?

Battery should only get so hot if i call someone over 1 hour.
Battery should only have a temperature about 23-30°C/73.4°F-86.0°F.

What version of the product are you using?

        system-gb-20110506-snapshot.zip
        boot-gb234-110429-snapshot-236mb.zip
        gapps-gb-20110503-signed.zip 

On what operating system?

Windows 7 64-bit

Do you have logcat or dmesg ?
 (adb shell logcat > logcat.txt ^C, adb shell dmesg > dmesg.txt)

What version of the *Official LG* Firmware were before using Custom
firmware ?
(V20G, V20D, V15x, V16x etc. )

Please provide any additional information below.

Original issue reported on code.google.com by Katzen...@gmail.com on 6 May 2011 at 9:18

[GoogleCodeExporter]

yah , we musy install the universal package on CM7 or the tiny packge on CM6...
look :http://goo-inside.me/google-apps/

//So what's up with the 2.3.4 GApps?
**(Please note, YMMV with all of the following information. Nandroid is your 
friend!)**
 This is a tricky one. The problem here is that Google, unlike what they've done for every previous
 update to the G1, Nexus One, Nexus S, etc., decided to compile the Talk2.apk and libtalk_jni.so to
 be compatible only with the neon board, and ARM v7 (aka, the Nexus S), rather than every board, the
 actual Gingerbread API's, and ARM v6 and Tegra as well. So here's where this leaves us:

20110307: Technically works just fine on 2.3.4, just as it did on 2.3.3. Just 
doesn't have the Market
 updates already in it (you'll get the updates as soon as you launch the Market for the first/second/third
 time or so), nor does it have the new Google Talk. Because of this, it's still used in ROM Manager for
 AOSP ROMs such as CyanogenMod, listed as Recommended in the Google Apps listing, and is given
 at the latest/7/universal page, and the above table.

20110503: This is made directly from the 2.3.4 Nexus S OTA. The new Google Talk 
is included, but
 is not recommended for Android 2.3.3 (CyanogenMod 7.0.x), and on most devices four main bugs are present:
Google Talk FC's when switching cameras.
Contacts do not see your video, but you see theirs, and you see your own 
preview.
Contacts do not see the ability to start a voice/video chat with you, and get 
an error instead.
Incompatible with ARMv6 or Tegra devices.//

Original comment by justsad.eng@gmail.com on 9 May 2011 at 12:27

[GoogleCodeExporter]

Nice. They sort out the old devices every 2 years?

Original comment by Katzen...@gmail.com on 9 May 2011 at 12:37

[GoogleCodeExporter]

@justsad // yes. gapps site already know this issue :>

Original comment by wkp...@gmail.com on 9 May 2011 at 12:40

[GoogleCodeExporter]

Original comment by wkp...@gmail.com on 9 May 2011 at 12:42

• Changed state: FAQ
• Added labels: Type-FAQ
• Removed labels: Type-Defect

[GoogleCodeExporter]

I changed the GAPPS but my phone continue running at 37°C :(

Original comment by Katzen...@gmail.com on 9 May 2011 at 12:45

[GoogleCodeExporter]

@katzen.....
do you have your usb cable plugged in?
my phone gets warm when the cable is in.

Original comment by martij...@gmail.com on 9 May 2011 at 8:41

[GoogleCodeExporter]

my phone just warms when using wifi.I've installed the recommended gapps with 
the latest update

Original comment by justsad.eng@gmail.com on 9 May 2011 at 8:50

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

If usb cable is pluged in. or when i browser, or when i use WLAN, or just 
randomly.
or i have a whole day without this problem.
with the last gapps and with the recommend gapps.
weird.
and i don't want to erease everything with fastboot erase -w or how its called.

Original comment by Katzen...@gmail.com on 9 May 2011 at 9:22

[GoogleCodeExporter]

@katzen
and i don't want to erease everything with fastboot erase -w or how its called.

why not?

Original comment by gebroede...@gmail.com on 9 May 2011 at 9:25

[GoogleCodeExporter]

fastboot erase userdata....

Original comment by cmgonza...@gmail.com on 9 May 2011 at 10:03

[GoogleCodeExporter]

I Solved this problem with:
1. Back to 2.3.3 System with 20110307 Gapps (lucky me, I first backup my system 
use CWM..)
2. Flashing once again 2.3.4 but Not do fastboot -w. 
3. Install again Gapps, 20110307, boot.zip and others update.zip file by 
gb-recovery.img.

Original comment by SamSamb...@gmail.com on 10 May 2011 at 12:36

[GoogleCodeExporter]

I also hate having to erase userdat, it means I have to backup all my apps aand 
call llogs, only to restore shortly afterwards.
I believe I got over this issue by rebooting into recover from ROM Manager 
(win!), installing the boot image again, installing the *-vold-*.zip patch, and 
installing gapps-gb-20110307-signed.zip.

wkp, this probably isn't the right place to ask, but is it possible to package 
the system.img as an installable zip file, like you do with the boot image, so 
it too can be installed from within CWM?  Then I wouldn't need to use fastboot 
flash at all anymore, as I can reboot into CMW, then install new versions of 
OpenEVE right inside CWM.

Food for thought?

Original comment by rais...@gmail.com on 10 May 2011 at 3:06

[GoogleCodeExporter]

@rais // I also hate "fastboot -w" things. and I always try to upgrade without 
"fastboot -w" :)

-----
Yes we can make a update styled update-gb-system.zip but not easy.

boot.img is basically small enough to fit in to a update.zip.
the updater script use temporary storage and it is smaller than system.img.

this is updater-script
------ X --------
...
assert(package_extract_file("boot.img", "/tmp/boot.img"),
       write_raw_image("/tmp/boot.img", "boot"),
       delete("/tmp/boot.img"));
...
------ X --------
and.. boot.img is not a simple filesystem. so we have to use above method.

but the difference is that system.img itself is a filesystem.
so, update-gb-system.zip can be maded with extracted file structure of 
system.img ..

Original comment by wkp...@gmail.com on 10 May 2011 at 3:37

[GoogleCodeExporter]

Wow guys, I have to apologize for my terrible spelling mistakes above, usually 
I catch that sort of thing...

wkp, thanks for the explanation, I wish I was a developer and understood better 
what that means :) but I think I get the gist of it.
You're saying that the temp storage doesn't have enough space for a ~120 MB 
system image.  What I don't really understand is why it ISN'T necessary to 
extract "system.img" to storage space, or how you WOULD make a zip file 
installer out of it.

What about the Advanced Restore function in CWM?
I know you can restore only the system image for example.
Perhaps we can use this functionality to our advantage, by making a "dummy" 
recovery, then placing any new "system.img" file into the 
"\clockworkmod\backup\[date]" folder and using Advanced Recovery to just load 
the system image?
I think the only problem might be that you may need to generate a new 
"nandroid.md5" file so that CWM will allow you to open the recovery, to even be 
able to select this new "system.img"

In summary, you would have to use fastboot the very first time that you install 
OpenEVE, in order to boot into CWM Recovery and install OpenEVE in the first 
place.  But then you can install the boot and system images that support 
rebooting into CWM Recovery (overwriting the boot image with the CWM Recovery 
image), and after that, we might be able to do all further upgrades within CWM, 
which would mean we can do them while out of the house for example, or in a 
movie theatre, like I did today :D

Original comment by rais...@gmail.com on 10 May 2011 at 6:18

[GoogleCodeExporter]

     Comment 63 by SamSamb...@gmail.com, Today (7 hours ago)

     I Solved this problem with:
     1. Back to 2.3.3 System with 20110307 Gapps (lucky me, I first backup my system
     use CWM..)
     2. Flashing once again 2.3.4 but Not do fastboot -w. 
     3. Install again Gapps, 20110307, boot.zip and others update.zip file by
     gb-recovery.img.

And if you erase the boot and system area instead of flashing back?

Original comment by Katzen...@gmail.com on 10 May 2011 at 8:00

[GoogleCodeExporter]

I tried it. Will report if the steps will work.

Original comment by Katzen...@gmail.com on 10 May 2011 at 8:17

[GoogleCodeExporter]

Now the notify light won't go on in silent mode if i resieve a sms.

Original comment by Katzen...@gmail.com on 10 May 2011 at 9:04

[GoogleCodeExporter]

The notify light now works correctly.

Original comment by Katzen...@gmail.com on 10 May 2011 at 9:31

[GoogleCodeExporter]

>> Katzen: No I did'nt anything to erase both boot img nor system area. Just 
flashing it on usual way..

Original comment by SamSamb...@gmail.com on 10 May 2011 at 10:23

[GoogleCodeExporter]

I did it.
Temperature is now about 34°C.
Want Temperatures about 23°C-27°C back. :(

Original comment by Katzen...@gmail.com on 10 May 2011 at 10:36

[GoogleCodeExporter]

Katzen how is your temp now.

Original comment by ivolu...@gmail.com on 10 May 2011 at 10:37

[GoogleCodeExporter]

About 34°C. Won't go down.

Original comment by Katzen...@gmail.com on 10 May 2011 at 10:47

[GoogleCodeExporter]

Have you try do downgrade an see if it is not a hardware problem.

Original comment by ivolu...@gmail.com on 10 May 2011 at 10:52

[GoogleCodeExporter]

I think its because my phone is connected via usb at my PC.
Unplug it now.
See if its work.
Don't want a hardware problem...

Original comment by Katzen...@gmail.com on 10 May 2011 at 10:54

[GoogleCodeExporter]

32°C now :)

Original comment by Katzen...@gmail.com on 10 May 2011 at 10:59

[GoogleCodeExporter]

33°C -.-

Original comment by Katzen...@gmail.com on 10 May 2011 at 11:51

[GoogleCodeExporter]

It needs less energy i think :)

Original comment by Katzen...@gmail.com on 10 May 2011 at 11:52

[GoogleCodeExporter]

Took it out of my bag. 31°C :)

Original comment by Katzen...@gmail.com on 10 May 2011 at 11:59

[GoogleCodeExporter]

30°C
THANK YOU ALL!

Original comment by Katzen...@gmail.com on 10 May 2011 at 12:02

[GoogleCodeExporter]

@rais // the nandroid backup is suppose to backup *WORKING SYSTEM* basically.

it will not hurt your working system. I just backup and restore your working 
system.
It can be used without fastboot.exe

but distribution of system.img/boot.img is different.
it may brick your system. and you can't easily revert your phone without 
fastboot.
you can't revert your bricked system with CWM / rarecovery.img etc.

that's the difference between the fastboot and CWM etc.

Original comment by wkp...@gmail.com on 10 May 2011 at 12:07

[GoogleCodeExporter]

29°C :) I think problem is fixed.

Original comment by Katzen...@gmail.com on 10 May 2011 at 12:11

[GoogleCodeExporter]

Thanks wkp.  If I have a chance, I can try to replace the system.img in one of 
my CWM backups with your latest system.img, and see if I can restore to it.
Has anyone tried this already by any chance?

It's worth a shot right?  At least to know if it is possible.

Original comment by rais...@gmail.com on 11 May 2011 at 3:16

[GoogleCodeExporter]

Issue 115 has been merged into this issue.

Original comment by wkp...@gmail.com on 22 May 2011 at 2:46

[GoogleCodeExporter]

this happened to me today morning :s
with the latest system and boot.
it has been rebooting on it's own quite frequently (every 30min or so).

Original comment by migaxmoi...@gmail.com on 10 Sep 2011 at 1:22

[GoogleCodeExporter]

ok, this time "arm11 crash".
pressed volume down to get the log, but I don't know where the log is.
can somebody tell me how to get it?

Original comment by migaxmoi...@gmail.com on 10 Sep 2011 at 2:31

[GoogleCodeExporter]

@migaxmoi //
you can get your crash log after reboot. "adb shell cat /proc/kmsg"

anyway, what is the version of your gapps ?

Original comment by wkp...@gmail.com on 10 Sep 2011 at 4:01

[GoogleCodeExporter]

gapps version is gb-20110729.
Now the mobile ran out of battery (drained in 7h of low use).
As soon as it crashes again I'll provide a log.

Original comment by migaxmoi...@gmail.com on 10 Sep 2011 at 6:36

[GoogleCodeExporter]

ok, blue error, arm11 crashed.
battery was @ 40%, after I turned it on again it was @ 10%
here is the log

Original comment by migaxmoi...@gmail.com on 10 Sep 2011 at 11:39

Attachments:

• crash_log