yashsingh1/xdaforums huggingface dataset:
[HTC Rezound] CharliesTheMan:
I just got my third fix it rezound where people had similar problems. On the most recent phone, it was really slow, I mean really really slow with everything. It was also having a high heat/excessive drain problem. The guy bought two new phones because he wanted something faster. Unfortunately he had rooted his wife's phone against my advice so they were probably identical.

After I received it and saw the phones behavior I understand why he got a new phone.

The first thing I did was s off it, then I flashed a new RUU and did the entire process twice.

That eliminated almost all of the problems, performance wise it was running great. But the battery was shot. It had just suffered way too much temperature abuse. I put a new battery in it and its like a different phone, its rock solid.

I agree with the guy in the first post. If you've been fighting issues like that, and you flash a stock RUU and are still having problems after trying a new battery (as in one that wasn't in your phone back when the firmware was wonky or when you were running mismatched firmware and patching the broken stuff, send that sucker back. Get a replacement, because its an amazing device when its right.
[HTC Rezound] platinumrims:
I've had 2 this week and sent them both back. The one I have now is my second one which has a messed up front camera that I got back in February. The first one they sent me earlier this week for over 120 degrees just from charging. That was the first one I experienced with actual heat problems... The second one I got yesterday had a seriously screwed up proximity sensor so I put it back in the mail about an hour later. I sent them an email so we will see what they say I'm not really sure what I'm supposed to do, I literally do not have time to worry about a defective phone that I have spent close to 800 dollars on.
[HTC Rezound] loonatik78:
You're heat issues sound kernel related. I was able to make my phone behave the same way with a custom kernel.
[HTC Rezound] platinumrims:
No the phone I have now has no heat issues. I'm saying the CLN replacement they sent me got super hot just from charging. i sent it back lol. It was completely stock

It was revision A, the second one I got with the proximity issues was an XA, the one I currently have is an XE I got it back in Feb
[HTC Rezound] nrfitchett4:
I don't consider my phone to have heat problems, but others would. It will get to 117-118 on 4g streaming. This has been consistent across both rezounds I've had. If I switch over to wifi, phone doesn't touch 100. I think its just the 4g radio on top of everything else.

Curious to the OP, are these better temps on wifi, 3g or 4g?
[HTC Rezound] Evocm7:
Your temps are pretty much normal. Mine will stay around 110 streaming Netflix on 4g which is very good I think. But 120 is supposed to be max but is nothing for this phone
[HTC Rezound] LOBBS:
I think it definitely is a hardware rev issue. I've got one of the "good" rev B. phones and I rarely see over 100 degrees in a controlled (indoors) environment no matter how hard I push it. My wife's Rezound is a rev. XA "pink button" phone and it gets hot and does all kinds of crazy things I've never seen on mine.

I should also note mine is overclocked at 1836 while hers is bone stock never even been unlocked.
[HTC Rezound] dabombcra:
I am on my third Rezound because of heat issues. I love the phone, but this heat issue has been something a lot of us have been complaining about since the phone came out. Verizon has been good about replacing the phone, but I have lost several batteries because of the heat issue. Once the phone gets to hot, it starts cooking the batteries. At least that was what I told.

I agree that if your phone is overheating, you do want to get it replaced. My third phone heats up when I am watching NFL Redzone. I have not had it overheat like the other phones but it does get quite hot. If I had a complaint about this phone, that would be my one complaint, it gets to hot.
[HTC Rezound] nolig2278:
Mine heats up when outside and when using screen at 100, but I live in Florida with temps in the 90s, so I come Indie and cool off. It can do a lot in the heat like for short calls and taking pictures but no angry birds on the beach.
[HTC Rezound] cpurick:
Seems better everywhere. I am doing an apples-to-apples comparison, though. On my home WiFi, the old phone would get up into the 120s with continuous surfing. The replacement phone is almost 20 degrees cooler. It's comfortable to hold, and I'm not constantly wondering if my hand is getting microwaved.
[HTC Rezound] brando56894:
I'm on my second Rezound, and this one gets hot as balls. My original one didn't but I had to get it replaced because the data radio was constantly shutting off due to a botched s-off or it was failing. It will be a year next month that I've had it. I'm probably going to ditch it for one of the Nexus devices soon.
[HTC Rezound] platinumrims:
Well VZ sent me some lame email this afternoon apologizing and saying I should get another rezound tomorrow. If this one is messed up I'm taking it to the store and throwing it at someone.
[HTC Rezound] a_bug:
Just out of curiosity what exactly was the touch screen issue you had?

I've felt that when mine get warm/hot the touch screen is either less responsive or inaccurately processes the touch to a different location on the screen.

Is this the problem you (and apparently others) are experiencing?

I guess I'll have to see if I'm still covered to get my four replacement b/c otherwise I really love this phone (as long as I don't go to far from a power source).

A (rezondingly confused) bug

Sent from my subtle and sublime Viperized Rezound.
[XPERIA X8 Q&A, Help & Troubleshooting] emaz1ng:
Good afternoon,

I'm sorry i'm creating a new thread about an old subject, but i just can't get my X8 to work with custom kernel+rom. I've searched the forum for the same issue but none of the solutions described worked. Until this moment i had to use PCC to flash my smartphone back to normal about 10 times and it's starting to get very annoying. I've followed the devs instructions on all procedures thoroughly, rooting, bootlader unlock, flashing kernel and installing ROM, and it always gets

stuck on the kernel logo wether is it before or after flashing the rom

(unless i press the back button). To this moment, i've tried nAa-14 and alfs v09 kernel, GingerDX and Zaraki roms, followed guides step by step. I'm a newbie in the smartphones area but not when it comes to computers. Throughout my 'voyage' i had a number of bumps i had to overcome, like having the installation aborted (bad) error when trying to install a rom, which i solved by downloading the zip directly to the SDcard like described here in the forums. GGdrivers are installed, and so are the SE USB drivers, phone is recognized by PCC with no problems.

I honestly have no idea what might be wrong, and as i said, i've done a search before creating a new thread but nothing helped, or maybe i'm just missing a tiny detail. I would really like the help since this is my first smartphone and i would like to play with my new toy!

Thanks and sorry for any inconvenience.

EDIT: I forgot something. In the kernel installation guide is requested that after flashing it, to check in the phone settings if everything is ok. I can't even boot the phone after flashing the kernel (gets stuck on kernel logo) which means my problem is related to something previous to it? Maybe bootlock? I'm pretty sure i'm doing what's required.
[XPERIA X8 Q&A, Help & Troubleshooting] emaz1ng:
Appreciate the fast answer.

I get stuck on the logo wether is it before or after flashing the rom. The only way i don't get stuck is to press the back button to boot into cwm.

Yes i've tried to wipe after and before, and it didn't work. And these were the only roms and kernels i've tried.

There's no problem with hardbricking my device by the way, 11w03.

I'll have to get out for a while, but i will come back later to check all the answers, this is a priority for me at the moment :)
[XPERIA X8 Q&A, Help & Troubleshooting] stamatis:
Don't full wipe two times,either before or after,you can see this at the rom thread.

One basic detail that many forget is that you must have baseband that lasts to 15,so it would be like this xxx015
[XPERIA X8 Q&A, Help & Troubleshooting] emaz1ng:
I didnt full wipe when trying gingerdx, as you said its not requested, only wiped with zaraki. I can confirm my baseband is xxxx015.
[XPERIA X8 Q&A, Help & Troubleshooting] stamatis:
You have to full wipe,don't full wipe two times,gingerdx needs full wipe before installing the rom....
[XPERIA X8 Q&A, Help & Troubleshooting] emaz1ng:
I tried again using the correct wiping method for gingerdx and it still freezes on kernel logo. the weird thing is that it freezes the first time it boots after flashing the kernel, meaning it has nothing to do with the rom, right? and maybe even not related to the kernel itself. i'm completely clueless about this, i wish i had a friend who could do it for me, because i can't detect anything done wrong.
[XPERIA X8 Q&A, Help & Troubleshooting] stamatis:
What version of cwm are you using?
[XPERIA X8 Q&A, Help & Troubleshooting] emaz1ng:
i'm not quite sure what's the version of cwm since it installs itself along with nAa-14 kernel, but i think it was v5.0.2.8

please don't destroy my hopes of having a working custom rom on my phone :D jokes aside, i get your point, but doesn't it seem not logical that i'm the only one who can't get it to work? it's weird enough i can't boot my phone after flashing the kernel....
[XPERIA X8 Q&A, Help & Troubleshooting] emaz1ng:
i could post a video, sure, but it's pretty straightforward. after i flash the kernel, unplug the phone from PC and boot it up, IF i don't boot into cwm, it will freeze on the kernel logo, making it impossible to even check the phone settings as requested in gingerdx thread. AFTER i install the rom and reboot the phone, it will still show the kernel logo and freeze again (if i understand correctly this is not supposed to happen, what's supposed to show on the screen after the rom is installed are the normal SE logos.)

So, summing up. Flash kernel, turn phone on, freezes on kernel logo if i don't use back button to go into cwm. If i enter cwm, install rom from sdcard, reboot, it shows the kernel logo and freezes if i don't use back button again.

Don't know if it helps but the only way to turn the phone off when it freezes is removing the battery. Sometimes after placing the battery again it will automatically turn on.
[XPERIA X8 Q&A, Help & Troubleshooting] stamatis:
Dunno what's wrong,why don't you try with stock kernel and gdx,or why don't you try different rom(yea neither gdx nor gzr)
[XPERIA X8 Q&A, Help & Troubleshooting] emaz1ng:
you mean formatting partitions after flashing the kernel or before? i assume there's an option for it under cwm?

sure i can try other roms, but the fact that it freezes before installing the rom seems to point towards another problem?

the phone was bought in 2nd hand by the way, maybe there's something that could have happen before it got to me?
[XPERIA X8 Q&A, Help & Troubleshooting] Lajbymester:
You have to format the partitions after flashing the kernel. In CWM recovery, go to 'mounts and storage' and format all the partitions except /sdcard.
[XPERIA X8 Q&A, Help & Troubleshooting] emaz1ng:
Just did it and the same thing happened. Flashed nAa-14, booted into cwm, full wipe, full cache wipe, wiped all the partitions but sdcard, installed rom, rebooted and it froze on the logo. Tried again with removing the sdcard and turning the phone on, froze on logo. Flashing it back to stock using PCC atm :(

By the way, it didn't let me format sd/ext.
[XPERIA X8 Q&A, Help & Troubleshooting] ElmirBuljubasic:
Have you tryed with older version of naa? Naa 14 is buggy, naa 11 is the best
[XPERIA X8 Q&A, Help & Troubleshooting] gowthamachandran:
Try some other roms like minicm7. Do it in this order

Flash the kernel

Boot to cwm

Format system,data,cache

Fullwipe/Factory reset

Install Rom

Reboot

....wait .....

I do this every time i install a new rom..

Make sure The rom you have downloaded belongs to x8..
[XPERIA X8 Q&A, Help & Troubleshooting] emaz1ng:
I will do that right away. I will also download a few others roms (and respective kernels) and try them all out. Only one thing, I was going to download MiniCM10 and i saw this in its post:

"MiniCM10 is an unofficial port of CyanogenMod 10 for the SEMC msm7x27 devices."

What does it mean 'for the SEMC msm7x27 devices'? Is it related to bootload unlock? Because i get Setool2 Certificate instead of SEMC. Does this make my problem a little easier?

EDIT: Ok, i've just tried ICZaraki+nAa-04-ics, minicm10+nAa-jb, gingerdx/gingerzaraki+nAa 11, and guess what, none worked.... We have to start thinking this is not related with the kernel or rom maybe? Any suggestions? When i tried the nAa-11 kernel, when i booted up the phone a white led popped up instead of a green one. I'm not worried if this takes a whole month to fix, i'm up for any suggestions and ideas of any kind, just throw them at me.
[XPERIA X8 Q&A, Help & Troubleshooting] ElmirBuljubasic:
This happen with alfs too? Have you followed all istructions to unlock bootloader?

Ah please..provide logcat! Big devs like rohin,eet, etc maybe can help you with logcat
[XPERIA X8 Q&A, Help & Troubleshooting] emaz1ng:
Yep, happens with all the kernels i've used, nAa-11/14, nAa JB, ICS, etc....

Googled logcat, i understand its use, but how do you want me to use it?

Yes, bootload is unlocked, i have the "r". Or is there any chance that even with the "r" it's still locked? Anyway, i followed the guides with no problem.
[XPERIA X8 Q&A, Help & Troubleshooting] wcypierre:
you can try to use my automated tool at my siggy. Just upload the logs at here and the devs will do their jobs :D
[XPERIA X8 Q&A, Help & Troubleshooting] emaz1ng:
am i supposed to specify a device (device id?) or just log all and upload them here?
[XPERIA X8 Q&A, Help & Troubleshooting] ElmirBuljubasic:
Log all!
[XPERIA X8 Q&A, Help & Troubleshooting] emaz1ng:
Here you go. Hope it helps.
[XPERIA X8 Q&A, Help & Troubleshooting] :
What the ...

[ 10-21 23:06:13.737 5758:0x167e I/ActivityThread ]
Publishing provider com.dataviz.stargate.shregi: com.dataviz.stargate.RegistrationInfoShare
[ 10-21 23:06:13.737 5758:0x167e I/ActivityThread ]
Publishing provider com.dataviz.stargate.status: com.dataviz.stargate.RoadSyncStatusProvider
[ 10-21 23:06:13.747 5758:0x167e I/ActivityThread ]
Publishing provider com.dataviz.roadsync.tasks: com.dataviz.tasks.TasksProvider
[ 10-21 23:06:13.747 5758:0x167e I/ActivityThread ]
Publishing provider com.dataviz.roadsync.messaging: com.dataviz.stargate.MessageDbAdapter
[ 10-21 23:06:13.757 5758:0x167e I/ActivityThread ]
Publishing provider com.dataviz.roadsync.calendar: com.dataviz.calendar.CalendarProvider
[ 10-21 23:06:13.807 5758:0x167e I/ActivityThread ]
Publishing provider com.dataviz.roadsync.folders: com.dataviz.stargate.FoldersProvider

Unless I'm terribly mistaken, "RoadSync" is part of the Navigation software SEMC put into the standard 2.1.1 firmware.

Are you 199% sure you actually EVER flashed a custom ROM through CWM?

Doesn't look like as there's a custom ROM in the NAND at the moment.

Also, just for the clarity...

The Stock 2.1.1 ROM does NOT work on custom Kernels, just on the Stock Kernel.

In case you're trying to boot the Stock ROM on nAa or Alfs it will NOT work.

You have to flash back the Stock SEMC kernel and then restore the ROM through Flashtool from the FTF file.

GingerDX v029 and Rohin's GingerZaraki work on Alfs v08/v09 and nAa 14 ... GingerDX additionally works on the Stock kernel as well. The procedure on how to flash the Kernel and ROM is laid out in the respective development threads.

This doesn't look like a hardware problem; this rather looks like you're doing something VERY VERY VERY wrong.

EDIT: Looking through the logs it seems to be very obvious you're running a Stock 2.1.1 ROM on the device. However, due to the logs having not captured a dmesg from the very boot it's impossible to tell what kernel you're running - if that isn't the Stock Kernel it would explain the one or anther error and why the device "stucks".
[XPERIA X8 Q&A, Help & Troubleshooting] emaz1ng:
Thank you for the answer. I know stock roms won't work under custom kernels, those logs were made after flashing everything back to stock using PCC. The problem is probably on my side of doing things, but i've followed every single guide out there thoroughly, it's not rocket science (i think i will regret saying this).

Well, i can say i flashed a custom rom more than 20 or 30 times now, but it always freezes on kernel logo when i reboot the device.

PCC isn't enough to flash everything back to default, kernel and rom? I just checked my phone's about settings, and it's currently under SEMC kernel. 2.6.29 SEMCUser@SEMSHost #1.
[XPERIA X8 Q&A, Help & Troubleshooting] ElmirBuljubasic:
Now flash naa 14 and reboot in cwm..wipe all! System/cache/data/dalvil cache..install rom(gdx o gzr) and reboot
[XPERIA X8 Q&A, Help & Troubleshooting] emaz1ng:
unfortunately, that's what i did those 20/30 times.

Install GGdrivers, install drivers which came with flashtool, install all SE USB drivers, open Flashtool, select kernel, press back button and plug to pc, wait, unplug when it tells you, boot into cwm, full wipe, cache, dalvik, install .zip from sdcard, reboot. Exactly what i did.
[XPERIA X8 Q&A, Help & Troubleshooting] megatpanji:
did u try relock your BL?after that flash ftf file.
[XPERIA X8 Q&A, Help & Troubleshooting] :
Err... you may want to advise he better NOT re-locks the boot loader when having the unlocked loader.sin sitting in there but better follow the "How to re-lock the boot loader" guide (I can't find at the moment) to do it the right way.

And, on a second thought @emaz1ng ...

While you are struggling, your phone would be the first device which doesn't want to boot a custom ROM. :p
[XPERIA X8 Q&A, Help & Troubleshooting] emaz1ng:
trying to understand how logcat works, and if i got it correctly, i just have to follow the normal procedure on flashing custom roms, and when the phone boots up, start logcat on my terminal to output a text document in order to check for errors, right?

You mean this? http://xdaforums.com/showthread.php?t=1254225

And yes, i have realised that :( You have no idea how frustrating this has become (or maybe you do).
[XPERIA X8 Q&A, Help & Troubleshooting] :
It's not exactly "logcat", it's more like the adb utility...

But yes, you can actually do this (given you have adb.exe plus the two DLLs or the adb binary for Linux somewhere in a directory that's in your search path) ....

Windoze (just open the command prompt):

adb logcat > Downloads\logcat_capture.log

Linux:

adb logcat > Downloads/logcat_capture.log

Once the command is invoked it will start and wait for a device to connect. So... you connect the X8 via USB (if not already done), turn it on, and then either let it run into the "freeze" or boot up before you press CTRL+C to terminate adb.

Then you have everything that was outputted, from the very boot onward, recorded in the text file.

I mean, don't get me wrong ... getting adb to use to track down errors and logs is what you should be able to do without needing to rely on some "LOL" program to do the job for you. Knowing how to get it to use can possibly save your day... like... you're about to flash a new ROM and you actually forgot to copy the ZIP/ZIPs to your SD beforehand (already happened even to me ... I only realized they weren't on the SD after formatting /system).

Instead of restoring back to stock to have a working system again to copy the files you would actually just connect the USB cable and then "adb push path/file/ROM.zip /mnt/sdcard" (maybe you need to tell CWM to mount the sdcard first). Saved my day a few times.

Yes, that's the thread I was looking for ... not the easiest one to read and comprehend, but in there is the correct way to restore and re-lock the bootloader.

Oh, you have no idea about how frustrating it can be to flash lots and lots of "in-development" ROM compiles to test them out. ;)
[XPERIA X8 Q&A, Help & Troubleshooting] emaz1ng:
This is certainly becoming an interesting subject. This is one of those that make you start guessing "i bet that in the end, when someone finds out what is being done wrong, they will laugh their faces off at my noobness".

So, to have the more information possible, i've logged while:

1- The phone booting on and with stock files.

2- After flashing nAa-14 and letting it freeze (logged twice). Interesting thing is, the screen goes off when it starts logging, and it doesn't stop, literally, if i didn't stop the process it would keep going until my pc is dead. Is this normal?

3- After flashing nAa-14, factory reset, cache wipe, dalvik wipe, battery stats wipe and flashing GingerZaraki ROM. (in this case the screen did not go off and the only line in this log is "/sbin/sh: exec: line 1: logcat: not found"

Trying to post the information the most complete and organized i can. If there's anything else i can do, tell me!

Thanks for all the help!
[XPERIA X8 Q&A, Help & Troubleshooting] :
That boot looks fine... I don't see anything suspicious in there.

Looking at "boot_freeze_1|2.log"

Whoa, no wonder the boot leads you to nowhere... you have all sorts of errors about libs that couldn't be found. Example:

D/dalvikvm( 1231): Trying to load lib /vendor/lib/libmedia_jni.so 0x0
I/dalvikvm( 1231): Unable to dlopen(/vendor/lib/libmedia_jni.so): Cannot load library: load_library[1052]: Library '/vendor/lib/libmedia_jni.so' not found

BUT... Just to ensure... you are REALLY trying to run nAa 14 and a GINGERBREAD ROM (please double-check)?

The errors that start with "/vendor/lib/..." ... this looks like as you're trying to boot a ICS (or Jelly Bean) ROM, NOT a Gingerbread one. In GingerDX we don't have a /vendor directory (not in the root and also not inside /system); that only exists in ISDX or MiniCM9. :eek:

What's the name of the CWM ROM ZIP?

EDIT: Ooops, I owe you the answer about the "why would it logcat forever" ...

Well, the answer is plain and simple. Once the system had enough of not being able to load required libraries it simply commits suicide...

E/AndroidRuntime( 1337): *** EXCEPTION IN SYSTEM PROCESS. System will crash.
E/AndroidRuntime( 1337): java.lang.NumberFormatException: unable to parse '' as integer
E/AndroidRuntime( 1337):	at java.lang.Integer.parseInt(Integer.java:353)
E/AndroidRuntime( 1337):	at java.lang.Integer.parseInt(Integer.java:323)
E/AndroidRuntime( 1337):	at java.lang.Integer.valueOf(Integer.java:666)
E/AndroidRuntime( 1337):	at com.android.server.am.ActivityManagerService.<init>(ActivityManagerService.java:1501)
E/AndroidRuntime( 1337):	at com.android.server.am.ActivityManagerService.<init>(ActivityManagerService.java:135)
E/AndroidRuntime( 1337):	at com.android.server.am.ActivityManagerService$AThread.run(ActivityManagerService.java:1332)

...but some evil simply respawns it...

D/AndroidRuntime( 1353): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<

...to make it go through it's death-and-respawn cycle again instead of letting the dead rest in peace.

/EDIT

Hmm, going by the rather sparse error I'd say one of the boot scripts either doesn't like the kernel, or Rohin really forgot to include "logcat" in /system/bin therefore breaking boot (read: the script errored out and therefore breaks further boot progess). @,@

ROHIN? Where's a wild Zaraki when one needs one? :laugh:
[XPERIA X8 Q&A, Help & Troubleshooting] emaz1ng:
Here are the ROM zip files i have tried so far with nAa-14: GingerDXv029 and update-GingerZaraki-v09-shakira. FTF file named: E15_nAa-14_2.6.29.6-nAa-14

Well, at least i'm learning new cool stuff :D What else can i do?

EDIT: thanks for the clarification! now this is a community i want to be part of, just need my baby working :)