Develop Bugs

[Q] entire screen not being used...

hi, im not sure if anyone else has encountered this problem, but ive had my desire hd for a few weeks now and its been working great. i rooted and flashed with hd revolution and again everything worked great.
now today i flashed an updated verison of that rom and when it had rebooted i noticed that the whole screen is suddenly not being used. a few milimeters on the right hand side and top of the screen and the image is slightly squashed to fit into that space.
i rebooted a few times and did a battery pull before thinking it must be a bug in the new build of that room and restored the room i backed up just before upgrading. but the problem is is there :/
not only that is present on all boot levels, so when your booting its there and in fastboot or recovery :/
could this be a hardware problem? has anyone else encountered this?
sorry if ive not explained this very well
thanks

must be a bug... what i suggest is do a full wipe and then flash a fresh rom...see if that solves ur problem doode

not only that is present on all boot levels, so when your booting its there and in fastboot or recovery :/
Click to expand...
Click to collapse
doesn't look like its rom related @leather|face

Leather|Face said:
must be a bug... what i suggest is do a full wipe and then flash a fresh rom...see if that solves ur problem doode
Click to expand...
Click to collapse
ive tried all that :/ its very annoying :/

rtouk said:
ive tried all that :/ its very annoying :/
Click to expand...
Click to collapse
thats its a problem with ur screeen... send it for repair

Leather|Face said:
thats its a problem with ur screeen... send it for repair
Click to expand...
Click to collapse
im not sure where i would stand on that front as im rooted :/

rtouk said:
im not sure where i would stand on that front as im rooted :/
Click to expand...
Click to collapse
If you download the PD98IMG.zip for the downgrade thread and place on your SDcard, boot into bootloader (not recovery) your phone will restore itself to HTC stock firmware.

HELP! Installed rom and now earphone doesn't work (or any other roms installed either

I'm not sure what happened but this morning I installed Codename Android's rom since everyone's been speaking so highly of it. I immediately got reboots right after starting. The screen would freeze and then the phone would reboot. I figured there was something wrong so I formatted data/factory reset, formatted cache and even formatted /system and installed it again. No reboots but the earpiece would not work on phone calls (speaker phone does). I also noticed that the screen doesn't turn off when I hold the phone to my face (so the proximity sensor seems to be messed up too). So I installed another rom: Redemption Rom. Same problem. I installed GummyNex, same problem.
I even unrooted and relocked the bootloader and EVEN THEN the earpiece did not work.
I feel like this is a software issue because it happened after installing a rom AND the proximity sensor doesn't work which seems strange for both that and the earpiece to stop working at the same time...
Is there something else that I haven't tried yet? Any suggestions??
I've only had the phone for a couple days so it could easily be a hardware issue I suppose, but I wanted to check if anyone had anything like this happen to them.*
Thanks guys!

Codename Android....if everyone's so highly speaking of it how come I haven't heard of it?
- Which version of the phone you have? CDMA? I'm assuming?
- What kernel?

Codename Android is one of the most popular roms on Rootzwiki

HeliosAI said:
Codename Android is one of the most popular rom on Rootzwiki
Click to expand...
Click to collapse
This is XDA, not Rootzwiki. I googled it. Answer the rest of the questions.
Have you tried flashing another ROM? Flashing stock images provided by Google?

CDMA and stock kernel. I have it completely unrooted and relocked and the issue is still there which makes me think it's less of a software issue. Unless somehow the software issue carried over from the rom?

I tried a few other roms and the issue was still there as well.

HeliosAI said:
CDMA and stock kernel. I have it completely unrooted and relocked and the issue is still there which makes me think it's less of a software issue. Unless somehow the software issue carried over from the rom?
Click to expand...
Click to collapse
And you've checked the obvious that the headphones work on another device correct? Tried another headphone on the phone?
If you fully wiped the phone and tried it with another ROM then it's most likely a hardware problem. And maybe it was a coinicidence that it broke right when you flashed the ROM.
Go into your about phone and tell me what it says for "kernel version"

Yeah I essentially tried everything. Thanks a lot. I was hoping I'd be able to fix it but I guess I have to take a trip back to the Verizon store.
And thanks for responding. I posted this on Rootzwiki and didn't get much help.

HeliosAI said:
Yeah I essentially tried everything. Thanks a lot. I was hoping I'd be able to fix it but I guess I have to take a trip back to the Verizon store.
And thanks for responding. I posted this on Rootzwiki and didn't get much help.
Click to expand...
Click to collapse
Assure you flash stock Google images. Otherwise if they see that you unlocked the bootloader at one point in time they may charge you extra for that.
Check kernel version for me real quick though.

zephiK said:
Assure you flash stock Google images. Otherwise if they see that you unlocked the bootloader at one point in time they may charge you extra for that.
Check kernel version for me real quick though.
Click to expand...
Click to collapse
Yeah I made sure about flashing the stock google images.
Kernel:
3.0.8-gaaa2611
[email protected] #1

HeliosAI said:
Yeah I made sure about flashing the stock google images.
Kernel:
3.0.8-gaaa2611
[email protected] #1
Click to expand...
Click to collapse
Okay yeah that's stock Google kernel. Most likely hardware problem, just weird how flashing a ROM triggered a coincidence.

zephiK said:
Okay yeah that's stock Google kernel. Most likely hardware problem, just weird how flashing a ROM triggered a coincidence.
Click to expand...
Click to collapse
Yeah very weird. Thanks again man, really appreciate it.

HeliosAI said:
Yeah very weird. Thanks again man, really appreciate it.
Click to expand...
Click to collapse
Sorry I couldn't help. Good luck with your new replacement when you get it though.

Constant Reboots!! PLEASE HELP!!!!

Hi guys,
I am using a Sony Ericsson Xperia Arc and am having a lot of trouble with the device constantly crashing and rebooting.
when this first happened these are the steps i took.
i completely wiped the device (factory reset, wipe dalvik cache, wipe cache partition, format system)
i then flashed Baseband 77 using flashtool
i then flashed fxp149 using flashtool
i then flashed Baseband 77 libs using CWM
i then flashed AOKP JB M1-R1 ROM using CWM
i then flashed gapps using CWM
i the reloaded all apps from the market and not applied any backups and yet it still rebooted all the time.
Since then i have tried using
Fusion 3.8
Fusion 3.9
Fusion 4.0
FXP 148
FXP 150
Stock Kernel inside ROM .zip file.
I have also tried putting it back to Baseband 72 but it made no difference.
None of these make any difference to my issue and yet before i had the issue, I had used all of these kernels except FXP 150 and they all worked fine with no issues at all.
I then decided to go all the way back to stock firmware as it is out of the box.
so I used flashtool and flashed LT18i_4.1.B.0.587_(1254-2716).ftf
I reloaded my applications and monitored the device only to see that by the next day, the problem had returned.
I am now at the end of my tether and do not know what else i can possibly do to figure out the issue.
the device has not been dropped or damaged in any way so there is no reason for a hardware fault.
i desperately NEED this device to be working as i use it on a daily basis for my business and cannot live with out it.
IF THERE IS ANYONE OUT THERE THAT COULD PLEASE PLEASE PLEASE HELP I WOULD BE FOREVER IN YOUR DEBT!!!!!!!

i also have a logcat that i was running in the background when one of the reboots happened
not sure if that can tell anyone anything but i have it if it does

First flash stock kernel (587), after flash the rom compatible with kernel. Remember full wipe before

have you tried not to restore your apps? Maybe one of them causes the problem. I'd try to stick with the clean (stock) rom an check if it still reboots. If it does I guess your device is ready for ebay

Could be a loose battery, try a bit of paper between the battery and the cover and see if that helps.

XperienceD said:
Could be a loose battery, try a bit of paper between the battery and the cover and see if that helps.
Click to expand...
Click to collapse
thanks for the suggestion but my battery is not loose and i have tried your method but with the same results.
weaselmetal said:
have you tried not to restore your apps? Maybe one of them causes the problem. I'd try to stick with the clean (stock) rom an check if it still reboots. If it does I guess your device is ready for ebay
Click to expand...
Click to collapse
hmmm i thought if that were the case there would be others experiencing it too.
i will take your idea and post results.
thank you very much
rod555 said:
First flash stock kernel (587), after flash the rom compatible with kernel. Remember full wipe before
Click to expand...
Click to collapse
i tried this, unfortunately i had the same issues occurring.
thank you for your suggestion

Needs a trip to the Service Centre then by the sounds of it.

XperienceD said:
Needs a trip to the Service Centre then by the sounds of it.
Click to expand...
Click to collapse
yes i am starting to think that may be my next move
will i have an issue with getting it repaired since i have unlocked my bootloader, flashed different kernels and roms and rooted the device?
if so, is there any way i can get it back to official "out of the box" state?

Flash a stock ftf and get the bootloader relocked. Having it rooted is fine
Sent from my lt18 using xda premium

tangosierra_ said:
Flash a stock ftf and get the bootloader relocked. Having it rooted is fine
Sent from my lt18 using xda premium
Click to expand...
Click to collapse
any chance you could explain a little about how to do that or possibly provide links to downloads or pages of instructions?

plastic_prophet said:
any chance you could explain a little about how to do that or possibly provide links to downloads or pages of instructions?
Click to expand...
Click to collapse
Here:- http://forum.xda-developers.com/showthread.php?t=1324703
Sent from my LT15i using xda premium

i have come across something quite interesting.
i had someone look at the logcat i had running live when i had a reboot and it showed that the last thing to function before the reboot was wifi scanning. they suggested i try turning off wifi and running the live logcat again to see if any reboots occured.
it has now been just over 48 hours and i have not had a reboot at all. i know is because my terminal session is still running the live logcat.
is there anyone that could suggest why this may be happening?
i mean, i know its wifi that is causing the problem, but would that be a hardware issue that could be fixed under warranty? or something else?
any suggestions are appreciated as always

plastic_prophet said:
i have come across something quite interesting.
i had someone look at the logcat i had running live when i had a reboot and it showed that the last thing to function before the reboot was wifi scanning. they suggested i try turning off wifi and running the live logcat again to see if any reboots occured.
it has now been just over 48 hours and i have not had a reboot at all. i know is because my terminal session is still running the live logcat.
is there anyone that could suggest why this may be happening?
i mean, i know its wifi that is causing the problem, but would that be a hardware issue that could be fixed under warranty? or something else?
any suggestions are appreciated as always
Click to expand...
Click to collapse
i don't think i can help, i just wanna say that i had (have) the same problem. I said had/have because probably I still have the issue, but i don't notice it that often. Before, I had my phone set to ask for pin code, but now I have removed it to avoid being unreachable if a restart occurs. I have raised the issue long time ago, but really didn't find any answer. Other ppl had same problem with their phone (look at the thread i started about this issue http://forum.xda-developers.com/showthread.php?t=1765537)
I also have HTC desire in daily use with CM7.2, that also reboots quite often. So I don't think the phones are broken. More likely it's kenel or rom or app issue, or some combination of those.
If you can tell me how to monitor things, I can do it on both phones, maybe we will figure out what's going on.

lalek said:
i don't think i can help, i just wanna say that i had (have) the same problem. I said had/have because probably I still have the issue, but i don't notice it that often. Before, I had my phone set to ask for pin code, but now I have removed it to avoid being unreachable if a restart occurs. I have raised the issue long time ago, but really didn't find any answer. Other ppl had same problem with their phone (look at the thread i started about this issue http://forum.xda-developers.com/showthread.php?t=1765537)
I also have HTC desire in daily use with CM7.2, that also reboots quite often. So I don't think the phones are broken. More likely it's kenel or rom or app issue, or some combination of those.
If you can tell me how to monitor things, I can do it on both phones, maybe we will figure out what's going on.
Click to expand...
Click to collapse
if you open a terminal session and type:
su
cd sdcard
logcat >> logcat.txt
it will create a .txt file and put the live logcat info into it.
you need to leave the terminal running in the background to make sure it continues to update
then when you see a reboot just get the logcat.txt file from the sd card and open it in wordpad or something. (notepad doesnt display properly)
have a look at the last thing that happened before the reboot and see what it tells you
mine had info about wifi scanning and showed that it had seen ssids
next step was to turn wifi off to see if the problem stayed or resolved.
good luck!! id love to hear how it goes

[Q] My phone randomly shuts itself off?

After trying a few custom ROMs, I've decided to revert back to the old stock ROM, and unroot because I still had my warranty left. So I downloaded the latest ROM available in the Stock ROMs thread, to be specific I8150DXLM3 Malaysia. :victory:
And after flashing via odin, at random times it would shut itself off, which is rather annoying. There was a phone call from a VIP and I couldn't answer it due to the sudden disappearance. HELP. Grr! I hate the stock ROM now. The only reason I used it I really like the Touchwiz. (Don't really care that much for the warranty) Is there any custom ROM that has Touchwiz that doesn't have all the Samsung bloatware?

meeshvl said:
After trying a few custom ROMs, I've decided to revert back to the old stock ROM, and unroot because I still had my warranty left. So I downloaded the latest ROM available in the Stock ROMs thread, to be specific I8150DXLM3 Malaysia. :victory:
And after flashing via odin, at random times it would shut itself off, which is rather annoying. There was a phone call from a VIP and I couldn't answer it due to the sudden disappearance. HELP. Grr! I hate the stock ROM now. The only reason I used it I really like the Touchwiz. (Don't really care that much for the warranty) Is there any custom ROM that has Touchwiz that doesn't have all the Samsung bloatware?
Click to expand...
Click to collapse
Before going back to stock, go pristine using CWM 1st. Format data, system and everything you can see. Then reboot into download mode and flash Stock ROM back.
Odds are unless your phone breaks in hardware stage, the SSC will still know its been rooted before. But then in Malaysia they're all lazy asses so you'd wanna find the one that looks the laziest. **malaysian here

KiD3991 said:
Before going back to stock, go pristine using CWM 1st. Format data, system and everything you can see. Then reboot into download mode and flash Stock ROM back.
Odds are unless your phone breaks in hardware stage, the SSC will still know its been rooted before. But then in Malaysia they're all lazy asses so you'd wanna find the one that looks the laziest. **malaysian here
Click to expand...
Click to collapse
I already went Pristine. :crying: LOL Heyy Malaysian! :highfive:

check the status of your battery. if it is swollen you must change it. it's happened to me some weeks ago and to some many other users that hava the wonder from one year!! if it is ok simply try factory reset

my phone only shut down itself in paranoid rom..

SpadaBoss said:
check the status of your battery. if it is swollen you must change it. it's happened to me some weeks ago and to some many other users that hava the wonder from one year!! if it is ok simply try factory reset
Click to expand...
Click to collapse
Swollen?!
Haha, no. I just checked the batteryy it's not.
Although, after rooting again, and installing XXLM8 Kernel and Seeders V5 apk it works smoothly and no shut downs so far.
intralot said:
my phone only shut down itself in paranoid rom..
Click to expand...
Click to collapse
Oh.

identical situation here in the philippines,,, regarding samsung care center,,,,
i guess,, they really dont have a way to detect whether yours is rooted or installed with a custom rom,,
i've sent my phone too,, because of a power issue,, as it wont turn on,, :crying:
before that,, ive installed cow bionic rom 2,,, then it shuts down itself,, and had no other means of powering it on,,,
so ive gambled myself in bringing it to them,,,
after a week,, they've said that its a board problem,, and needed to be replaced for free ,, since its under warranty,,, but had to be with them for at least a month,,,
after a month,, theyve returned it to me,,,,, and they even didnt detect that its rooted,, has cwm recovery,,, and installed with a custom rom,,,,

santiagoruel13 said:
identical situation here in the philippines,,, regarding samsung care center,,,,
i guess,, they really dont have a way to detect whether yours is rooted or installed with a custom rom,,
i've sent my phone too,, because of a power issue,, as it wont turn on,, :crying:
before that,, ive installed cow bionic rom 2,,, then it shuts down itself,, and had no other means of powering it on,,,
so ive gambled myself in bringing it to them,,,
after a week,, they've said that its a board problem,, and needed to be replaced for free ,, since its under warranty,,, but had to be with them for at least a month,,,
after a month,, theyve returned it to me,,,,, and they even didnt detect that its rooted,, has cwm recovery,,, and installed with a custom rom,,,,
Click to expand...
Click to collapse
This is why I love Asian countries. :good:

20%
hi evrybody!
my wonder has turned off simultaniusly on 20% on Stock and on Custom Rom, Ive had the battery 2 weeks ago changed. Whats the matter?

[Q] Phone Reboot

Hi everyone,
I seem to be having a problem with my One X, for the past hour the phone has been rebooting at random moments and its really p*issing me off!!
Its running stock ICS and all of the apps are installed from the play store so i don't think i have anything on it which is messing with it.
Is there anything i can do to stop this or do i need to wait for the Jellybean update and hope it will fix it?
I also heard that it might have something to do with my HBOOT which is 1.12 and i am waiting for 3 to update it!

Try to do a factory reset from bootloader first back up all ur data as factor reset vll erase everything
If the prob still exist take it to nearest HTC care centre
If I hve helped you press the thanks button ...
sent from HTC sensation

fmsidoe said:
Hey guyz,
i had the same problem, i only unlocked the phone and flashed a rooted boot.img.
After that i had that issue with every musicplayer except if i plug my headphones in it.
I think most of u rooted the phone..
I fixed it by flashing the boot.img again, but this time i used it from coredroidroms
go to:
coredroidroms. com
download the boot.img
flash it.. and it worked for me!!
I hope it works for u guyz... gud luck!
Click to expand...
Click to collapse
I found that in xda forums. It seems that coulb be come from battery issues, try to completly discharge the battery then make a complete charge... Hope I'll helped...

cheers lads ill give both a go

Marco_El_Wray said:
I found that in xda forums. It seems that coulb be come from battery issues, try to completly discharge the battery then make a complete charge... Hope I'll helped...
Click to expand...
Click to collapse
why would he want to flash a boot.img ? he is on stock rom.thats just going to bork his phone

markb63 said:
why would he want to flash a boot.img ? he is on stock rom.thats just going to bork his phone
Click to expand...
Click to collapse
That is just one more solution to help him, it's not mine but like I said I found that in another post... in last case if nothing works why not? Maybe this solution really worked for this man. Just wanna help that's why I quoted the text