Develop Bugs

help

I'm in a pretty bad situation. I don't know why it happened, but my phone screen went crazy so i took out my battery and tried rebooting. on the "tmobile mytouch 3g" the screen is fine and clearly ledgible, but once it boots up into the rom it goes crazy and is unreadable. I can't fix this because its fine for the hboot but when you try to go into recovery you can't see your screen, and therefore can't flash a different rom.. help? i'm running cm6.1, i had it overclocked to like 700

mr.johnsexydavis911 said:
i had it overclocked to like 700
Click to expand...
Click to collapse
There sir, is your answer.
EDIT: Since I'm sure I'll get flamed, let me explain why I say this. Our processor might be rated at 800mhz (while it's down-clocked to 600mhz), but that doesn't mean it can operate at 800mhz once it's built into a tiny device like a phone. Not to mention being along side a GPU which puts out a significant amount of heat as well. It's likely the device was being stored under less-than-ideal conditions and there was a run-away process eating up CPU. Result? Damaged GPU.

thanks... i guess haha. is there anyway to fix it?

mr.johnsexydavis911 said:
thanks... i guess haha. is there anyway to fix it?
Click to expand...
Click to collapse
The hardware is damaged - it's the risk you run when overclocking. You'll have to see if you can return it to T-Mobile under warranty and hope they don't figure it out. Is that ethical? No, but neither is charging $550 (retail) for a mid-grade phone and not delivering Froyo on-time.

You can try flashing the stock nbh in the dev forum. Thats done by simply placing it on the root of the sdcard and then booting into hboot.
Edit: I should clarify that I am not suggesting this as a fix, but as a way to try and get the phone to stock before trying a warranty switch.

nbetcher said:
The hardware is damaged - it's the risk you run when overclocking. You'll have to see if you can return it to T-Mobile under warranty and hope they don't figure it out. Is that ethical? No, but neither is charging $550 (retail) for a mid-grade phone and not delivering Froyo on-time.
Click to expand...
Click to collapse
Just curious, at what mhz would you recommend is safe for overclocking and do you know if the Slide is underclocked? For example the Slide claims to have a 600mhz processor, is the processor set to 600 max by default or is it set to something like 528mhz max? Thanks in advance.
P.S. Long time no talk Betch. How you've been?
Black myTouch Slide w/stock rom
www.GoTeamFriday.com

There are 3 kernels that you can use to overclock above 600 but below 800. One is 728? and the other is around 787. Most people are able to safely oc to 806 but it would seem you are definitely not one of them (some can go over 900). The last one allows you to oc to any normal speed you want, from underclocking at 245 to oc up to around 900. You have to set the boot speed via the 00banner file though.
If flashing the nbh file in Hboot doesn't work I would suggest (if you have insurance) running it over with your car or drop it off something really high. I don't believe they check the software, most likely because they couldn't since the hardware would be fubar.

[Q] Too much heat, reboot often

Hi,
I have a problem with Desire HD with Android Revolution Rom 2.0.11. Temp is over 40 Celsius when I upload videos and photos and frequent reboot is unavoidable. I set in SetCPU max 1036 min 245 (on demand). I tried perflock Disabler but it said no perflock to disable.
HTC Desire HD with Android Revolution ROM 2.0.11
Radio 12.28e.60.140f_26.04.02.17_M2_SF
Radio S-OFF, ENG S-OFF
ClockWorkMod v 2.5.1.3

SetCPU profile
I forgot to say that I have a profile for SetCPU,
if(temp>45) then change CPU to 245 min to 576 max, but hopefully, the temp never reaches to 45 (I think).
Regards,
Francesco

I think the highest I got mine was 32c using overclocking. What are the ambient temperatures over there? Assuming you don't sit in the blazing sun you either have a faulty kernel (try other Rom) or hardware issues. You did not plastic wrap your HD either right?
Sent from my Desire HD using XDA App

May need a new batt

Or it can be that the radio isn't compatible with your device!

xdauser2000 said:
I think the highest I got mine was 32c using overclocking. What are the ambient temperatures over there? Assuming you don't sit in the blazing sun you either have a faulty kernel (try other Rom) or hardware issues. You did not plastic wrap your HD either right?
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Room temperature is quite normal. My phone temperature is also around your 32C during normal usage. But temperature increases when I upload photos and videos and playing chess. Today I send a few photos by email and then temp went up to 39C.

paulcoop007 said:
May need a new batt
Click to expand...
Click to collapse
My DHD is just bought and I used it for a month. Even new battery might have defect? Anyway, I'll check for new battery replacement if nothing makes better. Thanks.

tolis626 said:
Or it can be that the radio isn't compatible with your device!
Click to expand...
Click to collapse
It is recommended radio by Mike1986 and I did correctly to upgrade radio version.

OOkk...Well,you can check everything by installing current widget.It will monitor the electric current of your battery.
First off,how is your battery life?Are you experiencing any drain?And have you tried different roms?Maybe it's the rom.A bad flash maybe or a corrupted download(mike's rom is fine from what I know,haven't tried it myself yet).

In my opinion this has to be a hardware issue.
Not even my device gets >over< 34° Celsius at 1,8 ghz after 3h watching youtube with full brightness.

tolis626 said:
OOkk...Well,you can check everything by installing current widget.It will monitor the electric current of your battery.
First off,how is your battery life?Are you experiencing any drain?And have you tried different roms?Maybe it's the rom.A bad flash maybe or a corrupted download(mike's rom is fine from what I know,haven't tried it myself yet).
Click to expand...
Click to collapse
I have battery life improvement after I flashed Revolution ROM. I didn't do anything wrong when I flashed the ROM.
Here is how I get new ROM.
Radio S-OFF first
http://forum.xda-developers.com/showthread.php?t=857537
Then I asked in radio thread whether I can do ENG S-OFF
http://forum.xda-developers.com/showthread.php?t=889093
then ENG S-OFF
http://forum.xda-developers.com/showthread.php?t=855403
Then I flashed Revolution ROM 2.0.11
Everything seems fine. MD5 checks are verified. But I cannot find the problem. But it was a bad flash, I have no choice to flash ROM again.
If it is hardware problem, I cannot go and ask customer service to check since warranty is voided. Battery replacement might be one option.
You have mentioned awidget about monitoring but I have no idea and I cannot find that widget in Market or file sharing cyber lockers. Any clue?
Thanks,
Francesco

Laus007 said:
In my opinion this has to be a hardware issue.
Not even my device gets >over< 34° Celsius at 1,8 ghz after 3h watching youtube with full brightness.
Click to expand...
Click to collapse
You are lucky to possess such beautiful performance device. Somethimes I'm thinking of buying durable phone with beautiful look and sophisticated features. But I have a feeling that none I have bought so far.

francescoandrio said:
I have battery life improvement after I flashed Revolution ROM. I didn't do anything wrong when I flashed the ROM.
Here is how I get new ROM.
Radio S-OFF first
http://forum.xda-developers.com/showthread.php?t=857537
Then I asked in radio thread whether I can do ENG S-OFF
http://forum.xda-developers.com/showthread.php?t=889093
then ENG S-OFF
http://forum.xda-developers.com/showthread.php?t=855403
Then I flashed Revolution ROM 2.0.11
Everything seems fine. MD5 checks are verified. But I cannot find the problem. But it was a bad flash, I have no choice to flash ROM again.
If it is hardware problem, I cannot go and ask customer service to check since warranty is voided. Battery replacement might be one option.
You have mentioned awidget about monitoring but I have no idea and I cannot find that widget in Market or file sharing cyber lockers. Any clue?
Thanks,
Francesco
Click to expand...
Click to collapse
Well,the widget is CurrentWidget,you can find it FOR FREE in market!
Now,if it's a hardware problem don't panic,warranty issues can be sorted out.If you are unlucky enough to have hardware problems,you will have to flash a 1.32 RUU.ENG S-OFF will be gone with RUU and you will have to manually S-ON your radio(More info on jkoljo's radio s-off tool's thread!Credits to him!).After that I believe you'll have no problem with warranty!
francescoandrio said:
You are lucky to possess such beautiful performance device. Somethimes I'm thinking of buying durable phone with beautiful look and sophisticated features. But I have a feeling that none I have bought so far.
Click to expand...
Click to collapse
Well,that depends.His device can handle high frequencies(And that is really cool btw! ).Mine can handle an unstable 1881MHz @1500mV(bad! ).But it is really stable up to 1728MHz.However,my device can do really well with low voltages.For instance,I am running stable @825mV for 245MHz and @1425mV for 1497MHz with LeeDroid's kernel,which I think most devices can't handle.So I have lower power consumption than average!
Every CPU is different,that's what I want you to understand.Although it did sound like I am boasting!

tolis626 said:
Well,the widget is CurrentWidget,you can find it FOR FREE in market!
Now,if it's a hardware problem don't panic,warranty issues can be sorted out.If you are unlucky enough to have hardware problems,you will have to flash a 1.32 RUU.ENG S-OFF will be gone with RUU and you will have to manually S-ON your radio(More info on jkoljo's radio s-off tool's thread!Credits to him!).After that I believe you'll have no problem with warranty!
Well,that depends.His device can handle high frequencies(And that is really cool btw! ).Mine can handle an unstable 1881MHz @1500mV(bad! ).But it is really stable up to 1728MHz.However,my device can do really well with low voltages.For instance,I am running stable @825mV for 245MHz and @1425mV for 1497MHz with LeeDroid's kernel,which I think most devices can't handle.So I have lower power consumption than average!
Every CPU is different,that's what I want you to understand.Although it did sound like I am boasting!
Click to expand...
Click to collapse
Ok, I found CurrentWidget in the market and I have installed on my DHD. I have opted to log everything it can. I'll post the log file before next charge. Currently, I have hot DHD in my hand temp running from 37-40. A few seconds ago this widget shows 558mA. I don't use SetCPU and the clock must be 1GHz (default). Does it tell something to you?

Is the PowerVR 540 just to slow for this screen?

Hello,
i am wondering, i have used my Galaxy Nexus for some time now at stock GPU clock and it was not a pleasant experience. I came from a device with the PowerVR540 but only 800x480 (Nexus S).
This phone had no trouble to keep up with rendering stuff, it was fast and (nearly) everything was fluent.
The Galaxy Nexus on the other hand can't keep up with frames in many stock apps at landscape and especially not in the browser..you can see that it drops below the 27 fp/s minimum for the human eye (no discussion about this 27 please).
I have now overclocked my GPU from 307 to 512 mhz, the result: It's like my Nexus S, everything (well, not everything) is sooo fast and it works great.
Is the PowerVR540 in the Galaxy Nexus just to slow for it's 1280x720 screen?

This has been asked many times, the gpu us actually one of the better chips out there. For your apps slowing down all I suggest is updating all your apps to latest version and make sure your running the latest version of your rom if your using Google stock or a custom rom. Youl also find over clocking your gpu will just use more battery for small gain. It was explained better in one if the custom kernel threads. If you ask my opinion Google knows best what hardware to use in their flag ship devices and now I'm running 4.0.4 stock rooted my phone is absolutely perfect.
Sent from my Galaxy Nexus using Tapatalk

I don't know, Google doesn't seem to know their hardware...my apps are up to date but my problems are with stock apps. I have used 2 GN and it was the same on both...lags, lags, lags...maybe some don't notice them (or just ignore them) but it's a horrible experience for me...i am just wondering why this phone isn't using a PowerVR543MP2...

bluefisch200 said:
I don't know, Google doesn't seem to know their hardware...my apps are up to date but my problems are with stock apps. I have used 2 GN and it was the same on both...lags, lags, lags...maybe some don't notice them (or just ignore them) but it's a horrible experience for me...i am just wondering why this phone isn't using a PowerVR543MP2...
Click to expand...
Click to collapse
Are you on a custom rom or stock? Stock 4.0.4 rooted has solved a lot of the small lags I found, try updating to it is my advice.
Sent from my Galaxy Nexus using Tapatalk

Stock 4.0.4...it's just that my Nexus S was somehow faster then the Galaxy Nexus...i expect better performance when i upgrade...not the other way around

bluefisch200 said:
Stock 4.0.4...it's just that my Nexus S was somehow faster then the Galaxy Nexus...i expect better performance when i upgrade...not the other way around
Click to expand...
Click to collapse
Nexus s has a lot less pixels to push, the resolution is no where near as high so that would be my guess.
Sent from my Galaxy Nexus using Tapatalk

[Q] no signal on wake

(UPDATE- I searched and found this is a known issue: code.google.com/p/android/issues/detail?id=28133)
I9250 on ST
Radio XXLA2
North central US
I travel to a lot of very rural areas for work. Often while in these areas I will unlock my phone and see no service. A minute later I may have up to 2-3 bars showing and I'll receive vm and sms notifications. I've tried different kernels and ROMs with no change.
Sent from my Galaxy Nexus using Tapatalk 2

I had this problem when using Juice Defender. Any chance you are using it?

No juice defender or even any similar app running.
Sent from my Galaxy Nexus using Tapatalk 2

untruestory said:
I9250 on ST
Radio XXLA2
North central US
I travel to a lot of very rural areas for work. Often while in these areas I will unlock my phone and see no service. A minute later I may have up to 2-3 bars showing and I'll receive vm and sms notifications. I've tried different kernels and ROMs with no change.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
i started noticing the same issue recently...no service when i press the power button (on the lockscreen)...shortly after i unlock my phone, service/data restores...not sure if its kernel related as i believe (not 100% sure) that it happened around the same time i switched from glados to popcorn
i am also on XXLA2....in NYC

You all need new radios lol.. Try the radios thread in general section and flash as many as you need until you find whats works for you..
Id start testing uglc1 wich are the lastests basebands..
Galaxy Nexus AOKP m5 Franco kernel m3

msedek said:
You all need new radios lol.. Try the radios thread in general section and flash as many as you need until you find whats works for you..
Id start testing uglc1 wich are the lastests basebands..
Galaxy Nexus AOKP m5 Franco kernel m3
Click to expand...
Click to collapse
ive tried different radios before...UGLC1 included...went back to XXLA2 which gives me the best signal
this issue has only recently started happening...like i said, maybe related to the kernel because it started happening around the same time...not sure

msedek said:
You all need new radios lol.. Try the radios thread in general section and flash as many as you need until you find whats works for you..
Id start testing uglc1 wich are the lastests basebands..
Galaxy Nexus AOKP m5 Franco kernel m3
Click to expand...
Click to collapse
Its not the radios, I have seen some posts in kernel threads about minimum CPU clock speed.
If you are using 192mhz bump it to 384mhz and see if that helps if not then try 729mhz. I've seen people sort it by doing this.
Those are Franco clock speeds but you get the idea.

nodstuff said:
Its not the radios, I have seen some posts in kernel threads about minimum CPU clock speed.
If you are using 192mhz bump it to 384mhz and see if that helps if not then try 729mhz. I've seen people sort it by doing this.
Those are Franco clock speeds but you get the idea.
Click to expand...
Click to collapse
ive read that the min cpu speed and even low VOLTAGES can affect signal stability as well....but i didnt change any of that.. currently its at 384 mhz and the default voltages on the popcorn kernel...the problem just started out of nowhere..its been fine for the past 2 weeks or so...just started happening like 2 days ago

no signal on wake
jdiddy_ub said:
ive read that the min cpu speed and even low VOLTAGES can affect signal stability as well....but i didnt change any of that.. currently its at 384 mhz and the default voltages on the popcorn kernel...the problem just started out of nowhere..its been fine for the past 2 weeks or so...just started happening like 2 days ago
Click to expand...
Click to collapse
I too experience the same issue. I am currently running aokp_maguro_build-36and have tried various basebands and now currently back at I9250UGKL1 .
I have been installing AOKP builds with the same behavior in that it goes to sleep the radio stays sleeping unless I reboot. I have the min CPU set to 700 mhz.
I have been reading the forums for weeks but cannot find anything where someone has fixed this. I love everything about the Galaxy Nexus with exception of this.

I've tried several ROMs and kernels. They make NO DIFFERENCE at all, including using stock.
Sent from my Galaxy Nexus using Tapatalk 2

blanktree said:
I too experience the same issue. I am currently running aokp_maguro_build-36and have tried various basebands and now currently back at I9250UGKL1 .
I have been installing AOKP builds with the same behavior in that it goes to sleep the radio stays sleeping unless I reboot. I have the min CPU set to 700 mhz.
I have been reading the forums for weeks but cannot find anything where someone has fixed this. I love everything about the Galaxy Nexus with exception of this.
Click to expand...
Click to collapse
Try cm rom
Sent from my Galaxy Nexus using XDA

untruestory said:
I've tried several ROMs and kernels. They make NO DIFFERENCE at all, including using stock.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Try different radios. Ive noted that the radio is not changed when I flash different roms.
Sent from my Galaxy Nexus using XDA

jdiddy_ub said:
ive tried different radios before...UGLC1 included...went back to XXLA2 which gives me the best signal
this issue has only recently started happening...like i said, maybe related to the kernel because it started happening around the same time...not sure
Click to expand...
Click to collapse
Id say try a Stable rom(not nightly) like AOKP Milestone 5 or stock.. And see if the problem persist.
After flashing new roms do a wipe of everything.. Dalvik/sd/cache/system
Galaxy Nexus AOKP m5 Franco kernel m3

msedek said:
Id say try a Stable rom(not nightly) like AOKP Milestone 5 or stock.. And see if the problem persist.
After flashing new roms do a wipe of everything.. Dalvik/sd/cache/system
Galaxy Nexus AOKP m5 Franco kernel m3
Click to expand...
Click to collapse
i am already on AOKP MS5...i flashed the stable jame bond kernel last night...havent seen the issue since...hopefully that solved it

Aite cheers
Galaxy Nexus AOKP m5 Franco kernel m3

Since its not the radios, the kernels, or the ROMs, then what else (other than a hardware defect) could be creating this problem?
Anyone?
Sent from my Galaxy Nexus using Tapatalk 2

Me too experiencing the same issue. Currently I'm on AOKP B37, and the bug is still there. The funny thing, is that despite no signal icon on wake, the phone is still on air and accepts calls. I've installed the No Signal Alert app, which hasn't registered any signal loss so far, but I know it works fine (I used it before on my old Galaxy I5800, which was loosing service). Very strange...

That is odd. I've missed calls in areas I should have gotten them. I'm hoping they hurry up and release a fix.
Sent from my Galaxy Nexus using Tapatalk 2

Signal Loss
I've been having the same issues for about a week or two now. Actually sent a phone back in and had it exchanged out because of this. Yes, I tried all radios and tons of different roms. Same result for all. And I mean I tried ALL THE RADIOS, so quit suggesting that.
And I also swapped out a phone, redid my things, and now getting back to same issues again.
However, my observations.....
I never had issues from Dec thru about a month ago. Then had a Rez for two weeks, then back to GNexus. First thing I did was load most current CM9. Played well for the whole day I had it at that. Then I realized I had forgot to update radios. Before (month ago) it was still at leaked 4.0.4 radios, however when I looked em up, the official 4.0.4 radios were posted. So I dabbled with them instead. But I also saw the bootloader update and blah blah, so I did the whole shabang for official 4.0.4, then rerooted and cm9'd. This was where problems began....at this point is when I started having exact same problems as OP. So I went back to old radios. Same problems. Then different radios. Same problems. Then different roms. Same problems. Then rolled all the way back to completely stock 4.0.2 image file. Bootloader, radios, recovery, everything. SAME PROBLEMS STILL.
Thats when I swapped out the phone.
New phone comes. I redo everything again, but just use official 4.0.4 radios rather than the bootloaders and blah blah but still with CM9. All is good. Then I wanna play with the full official 4.0.4 OTA update. So I do all of it. All if fine but I realize hey, battery life sucks again now. Back to CM9. Then I reroot and rom. And holy ****, all the problems are back again now with signals. New roms, same problems. Literally everything I had problems with before is all back again.
So I'm wondering if this obviously has something with OFFICIAL 4.0.4 image/bootloader/recovery or whatever the hell is being written when I'm doing that flashing.
Thoughts?

Your case might have some other cause. Did you try swapping your sim card?
Meanwhile, I was able to find a workaround. Just raised the min CPU freq. from 350 to 525. Since then there was not a single signal loss so far. Battery drain increase in idle mode ain't registered as well. I'm on AOKP b37 currently.
Here are the steps to take at least on AOKP (other roms may have similiar settings available):
Go to ROM control in the settings menu.
Open the Performance
Set the Min CPU to 525
Ensure, that Scaling govenor is set to Interactive
Enable the Set on boot option
Hope, it works for you too. Good luck!
Отправлено с моего GT-P7500 через Tapatalk

[Q] Flash third-party ROMs with 2.5GHz ver M8?

I have a long time doesn't flash third-party ROMs since One X, and now I got One M8 for a month, everything is great!
That makes me want to try third-party ROM again.
But as I known, lots of ROMs is based on WWE version to develop, and it's use MSM8974AB (2.3GHz)
And...I'm Taiwanese, so obviously my M8 is use MSM8974AC (2.5GHz)
Some information I found, says that these two different model using a different CPU voltage table.
And I don't know I can use these ROMs or not because the kernel is different.
Does anyone using 2.5GHz version M8 and tried the ROMs on this forum?

Yeah, it works fine.

BenPope said:
Yeah, it works fine.
Click to expand...
Click to collapse
Thanks for ur reply, now mt mind is easier now.
But I still get little worry that because voltage table is different.
Is that may cause CPU get problem easier in the future?

I highly doubt the voltage table is not looked up by the cpu type. Do you have any evidence for this?

BenPope said:
I highly doubt the voltage table is not looked up by the cpu type. Do you have any evidence for this?
Click to expand...
Click to collapse
Actually, this information is from Taiwan's forum and that guy who told me this message is a developer, too.
Maybe he checked kernel and sure that voltage table is different.