Universal - Anybody tested XCPUScalar v2.92? - JASJAR, XDA Exec, MDA Pro General

Hi!
Newly released, here:-
http://www.pocketgear.com/software_detail.asp?id=7325
Anybody tested with their Universal? How's the stability? Can the Universal be overclock beyond 624MHz?
Thanks

won't even go to 624 on my jasjar
maybe cos its a trial...
regards

initial installation working fine. the next morning, the whole screen when into flickering. even putting it into prevent flickering filter mode also don't work.

RE
rahjinoh,
Earlier version v2.91 also exhibited similar flickering problem with my set. I thought this latest release, v2.92, should have the problem solved?
Thanks

Nope it does'nt..min still flicker..for a moment there I thought my display faulty

RE
Yah, flickering and system hangs
Apparently, after switching off everything (ie. wireless connection and power off) and re-power on flickering starts and my system hangs
On one occasion of soft reset my system hangs. On another soft reset the system was working fine but flickering started again and my system hangs after less than 5 min of use.
WELL, THIS VERSION IS OFF MY SYSTEM!!! :evil:

Still not working
2.92 like 2.91
still not compatible

Looking on their forums, it looks like 2.93 will be the one to look out for, for us Universal owners.....

sub69 said:
Looking on their forums, it looks like 2.93 will be the one to look out for, for us Universal owners.....
Click to expand...
Click to collapse
Let's hope so...

I was about to post about this too.. I installed the trial and boom, my dopod had this white screen and flickering lines of green and pink (I guess from my wallpaper)... I couldnt distinguish which is whiter, the paleness of my face or my phone. Haha.. I quickly reset and uninstalled. The end. Will never try anything so scary again..

cuteangelika said:
I was about to post about this too.. I installed the trial and boom, my dopod had this white screen and flickering lines of green and pink (I guess from my wallpaper)... I couldnt distinguish which is whiter, the paleness of my face or my phone. Haha.. I quickly reset and uninstalled. The end. Will never try anything so scary again..
Click to expand...
Click to collapse
LOL... I loved your vivid description cuteangelika...
I believe that version 2.93 is for us though...

Related

White screen in TyTN

Hi,
I bought my TyTN 6 months ago. I upgraded it to WM 6 from HTC update and and few weeks later during wirting a text message my screen went white and I couldn't do nothing. I restarted it after 15 minutes and I discovered that all data is gone. I got plain OS.
From that time the situation was accuring again, but after few seconds it was working ok and white screen was disapearing. I was using different OS versions, as well as Shap's form 3.54 up to 4.31 but it on every the situation become the same.
I contacted with HTC but still i didn't get any reply. Any idea what the problem could be? Is it the screen? Please help...
KaPeer
It's probably flex cable problem. There's been a few issues this type.
hmotwr said:
It's probably flex cable problem. There's been a few issues this type.
Click to expand...
Click to collapse
Do You know is it possible to fix it and if YES how to do this?
im having the same problem with my softbank xo1ht. if i hard reset screen returns but after about 15-30 mins screen fades to white and i cant see anything or use any function??? please advise
My screen was going white like for almost a week (coincidentally after going through airport security xray). I called for a warranty replacement and wouldn't you know it, after I called I have yet to see the white screen on the old one.
Are your hard buttons (d-pad, answer, hang up, mail, IE) failing as well? Try pushing down on your device right under the bottom right of the screen and see if it'll turn white.. or put it in standbay and press down above your d-pad and then take it out of standby and see if that fixes it..
your probably running into a hardware problem which is discussed here:
http://forum.xda-developers.com/showthread.php?t=321163&highlight=white+screen

my screen went blank

Hi,
Does anyone know why my screen just suddenly goes white?
It started when i heard someone called me. I looked at the screen and it was totally white. Pressing buttons didn't do anything. I tried soft + hard reset but the fone was still like that.
Has anyone got this problem before?
vnxichlo said:
Hi,
Does anyone know why my screen just suddenly goes white?
It started when i heard someone called me. I looked at the screen and it was totally white. Pressing buttons didn't do anything. I tried soft + hard reset but the fone was still like that.
Has anyone got this problem before?
Click to expand...
Click to collapse
i haven't had the problem but it would be helpful if we knew what kind of a phone and rom you have
my fone is cingular 8525, and I have no idea what kinda rom I have. I only unlocked it with the software available here, and still haven't had time to play with other stuff yet.
oh, and i don't think the front buttons work, btw, so when i said i hard reseted it, i was wrong.
it also seems like this problem:
http://forum.xda-developers.com/showthread.php?t=321163
Don't you think? Now I'll have to buy some tools to open this baby up. Does anyone know where I can get the right tools?
It's always best to start at the beginning. Go HERE to a page that I created for new members that has links to EVERYTHING you may need to know about fixing your phone, flashing ROMS and Radios, etc.
Best wishes,
I just fixed it i just fixed it ). I don't think the light sensor for the keyboard work anymore thou, but screw that, the phone works ).
BIG BIG THANKS to "ALKIZMO" and his post:
http://forum.xda-developers.com/showthread.php?t=321163

Stuck on "Stick Together" screen for no apparent reason

This is odd. I'm running a stock TMOUS ROM, haven't done anything out of the ordinary, and my phone froze up (which happens several times a day) so I unplugged the battery to reset and now I'm stuck at the "Stick together" screen.
All other cases of this that I've seen are from people's unsuccessful attempts at flashing a new ROM, but I'm running the stock T-mobile rom that I've been running for 2 months.
Please help. Id rather leave hard resetting as a later resort, since I dont really want to reinstall my apps and reset all of my tweaks, but if it comes to that so be it.
Oh, and the only thing different that I did was install the new bing maps mobile app that came out this morning. I did that several hours before the freeze...
Update:
I got impatient and hardreset despite my reservations to do so, and it's booting up now.
Well there's clearly no better time to flash a new rom than now... Off to the drawing board.
Take the battery out and make sure the pins are not bent, usually this is what happens when they are, the phone keeps rebooting itself but never fully starts. Gets to a tmo logo and restarts.
Edit: glad it works now, on my old one i had this problem and it was due to that...
mine did that once, took the batt out like twice more....then i just left it for like 15 mmin and it booted up
Can someone tell me if the 3 pins on HD2 for the battery are all aligned up horizontally or is 1 higher thn 2 and 3 is way up there?
Kind of like --- or _ -
goldt said:
Can someone tell me if the 3 pins on HD2 for the battery are all aligned up horizontally or is 1 higher thn 2 and 3 is way up there?
Kind of like --- or _ -
Click to expand...
Click to collapse
They all look like they're lined up even...here's a pic to make sure we're looking at it the same way
sirphunkee said:
They all look like they're lined up even...here's a pic to make sure we're looking at it the same way
Click to expand...
Click to collapse
Thanks that helps
I am having the same issue. I have dutty's rom.It had been working fine and then I got the issue where the screen wouldn't light up so I took out the battery and now it won't go past the boot screen with the stick together and doesn't even display the three things at the bottom left hand corner.
I did hard reset and still stuck on stick together, and my pisn don't appear bent.
magic_man said:
I did hard reset and still stuck on stick together, and my pisn don't appear bent.
Click to expand...
Click to collapse
How long have you been running his ROM?
sirphunkee said:
How long have you been running his ROM?
Click to expand...
Click to collapse
3-4 weeks. It was working fine and now it just shows the stick together and not the rgd at the bottom riight. I can get to the HSPL boot loader, but I don't think I have installed any programs the last week or so. I guess I could try task 29 etc, but it seems kind of strange i would have the problem all of a sudden.

Weird Android Desire build boot problem, have I damaged?

Sorry if this has already been posted about or if this is this is wrong place to ask but have used search and couldn't find anything.
I tried to boot the Desire build on my HD2 but after a few seconds teh white writing looked as if it just melted and froze which was really weird and concerned my allot.
I pulled out my battery and rebooted into windows but now I have noticed that when my white HD2 splash comes up I have a very distinct brighter part of back light I think like a smudge of light behind screen.
I did disable auto backlight when booting btw.
Can anybody explain what went wrong or if I have done any damage and will it correct itself.
Again sorry if this has already been discussed, if so can you link me to correct place.
Regards and thanks.
the "melting" is normal.. wouldn't worry about that...
nutmegy said:
the "melting" is normal.. wouldn't worry about that...
Click to expand...
Click to collapse
When I say melting I dont mean when the writing moves down screen fast etc, I mean it physically looks like the writing freezes and then white text melts away into black background.
I also have a HD1 and have used android on there allot and didn't have teh same melting look which concerned me allot as I though it was damaging the light or digitizer etc.
[edit] Just watched a youtube video of desire booting and it did the same thing so am gunna give it another go, can anybody explain the light issue though regarding teh smudge of brighter light after booting rom as its still there and concerns me a bit.
ATHiEST said:
When I say melting I dont mean when the writing moves down screen fast etc, I mean it physically looks like the writing freezes and then white text melts away into black background.
I also have a HD1 and have used android on there allot and didn't have teh same melting look which concerned me allot as I though it was damaging the light or digitizer etc.
Click to expand...
Click to collapse
Check the last visible lines of text just before this happens. Do you see something like "init panel" there? Then it should be perfectly normal.
ATHiEST said:
When I say melting I dont mean when the writing moves down screen fast etc, I mean it physically looks like the writing freezes and then white text melts away into black background.
I also have a HD1 and have used android on there allot and didn't have teh same melting look which concerned me allot as I though it was damaging the light or digitizer etc.
Click to expand...
Click to collapse
I get that too...during boot...then it comes back and continues to load Is it not continuing to boot for you at that point? Have you disabled auto-backlight dim in Winmo before launching Haret? Are you seeing the boot text fade then just yanking the batt out?
ATHiEST said:
When I say melting I dont mean when the writing moves down screen fast etc, I mean it physically looks like the writing freezes and then white text melts away into black background.
I also have a HD1 and have used android on there allot and didn't have teh same melting look which concerned me allot as I though it was damaging the light or digitizer etc.
Click to expand...
Click to collapse
Sounds like your screen crashed.. Happened a lot in the early Touch Pro Android days.
meptik said:
Check the last visible lines of text just before this happens. Do you see something like "init panel" there? Then it should be perfectly normal.
Click to expand...
Click to collapse
+1, this is just the system "shutting down" and booting back into linux, you are fine.
meptik said:
Check the last visible lines of text just before this happens. Do you see something like "init panel" there? Then it should be perfectly normal.
Click to expand...
Click to collapse
Yeah it does.
Ive just tried again, the text fades etc then just stays on blank screen and doesnt go anywhere?
Im prettt sure I turned auto back light off (unless it goes back on after windows reset), how long is it supposed to stay on the blank screen?
[edit] Just tried a second time....
Clean formatted card
Extracted desire build 5
turned auto back light off
run CLRCAD
run haret
get the linux boot text
get init panel
txt melts away
just hangs, waited for 10 mins, nothing.
Do these builds need any particular windows rom version/radio version/spl/hspl etc?
ATHiEST said:
Yeah it does.
Ive just tried again, the text fades etc then just stays on blank screen and doesnt go anywhere?
Im prettt sure I turned auto back light off (unless it goes back on after windows reset), how long is it supposed to stay on the blank screen?
[edit] Just tried a second time....
Clean formatted card
Extracted desire build 5
turned auto back light off
run CLRCAD
run haret
get the linux boot text
get init panel
txt melts away
just hangs, waited for 10 mins, nothing.
Do these builds need any particular windows rom version/radio version/spl/hspl etc?
Click to expand...
Click to collapse
There's a definite requirement for the radio version: 2.08.50.05 or higher, as long as there's a 50 in the version number. People have been getting good results with 2.10.50.28_2 and 2.12.50.02_2.
ROM version might also influence things, check the Android thread. Some people are recommending EnergyRom, I'm using Artemis right now.
I got Desire v5 running very nicely here. My setup:
ROM: Artemis v25 WWE
HSPL: 2.08
Radio: 2.12.50.02_2
meptik said:
There's a definite requirement for the radio version: 2.08.50.05 or higher, as long as there's a 50 in the version number. People have been getting good results with 2.10.50.28_2 and 2.12.50.02_2.
ROM version might also influence things, check the Android thread. Some people are recommending EnergyRom, I'm using Artemis right now.
.
.
.
Click to expand...
Click to collapse
I second that. I'm running exactly what's in my sig and I have zero problems running the v5 Desire build.
Ahh that will be my problem then, Only just got teh HD2 a couple of days ago second hand (mint condition though) and forgot to update radio, currently has 2.06.
Will update now and hopefully get something booted, will post back thanks for help.
booting problem
the fading of the white words and symbols going down is normal happens to all the hd2 that are booting up i wouldnt worry about it i did it on both my hd2s and when i click on heret it starts booting then letters fade away and the penguin for linux pops out its normal.
i have somthing else tho i dont know if you guy got this but when i open desire build v5 everything works but wen my phone goes to sleep the buttons stay on does everyone have this same pronlem or just me like i do the complete boot everything goes well smoothly i can make calls and everything but wen it goes to sleep for some reason the light on the buttons stay on while in sleep mode help me out.
i tried booting mine,
black screen
the button lights are all on
green light flashed in top section of phone (normal message indicator light)
Radio version is 2.12.51..

HD2 Black screen after a call?

Is there a fix for this? No matter what rom I use, Didn't try Froyo, but after receiving a call, the screen stays black, so I spam the hard keys to wake the screen after about a minute or so. Can anyone help?
Curiousn00b said:
Is there a fix for this? No matter what rom I use, Didn't try Froyo, but after receiving a call, the screen stays black, so I spam the hard keys to wake the screen after about a minute or so. Can anyone help?
Click to expand...
Click to collapse
I have the same problem with 2 HD2 phones. Not aways, but most of the time. I ask this question before - http://forum.xda-developers.com/showthread.php?t=1349809 , but i didn't get the answer.
May be it is hardware problem, but if it is it's gonna make me a problems every time.
If you figure it out, pls PM me.
Once in a while i have the same problem, but when I clean the screen (until it looks shiny ) and it gets better…
(I clean mostly the top of the screen)
I don’t believe it is the “solution” but works for me…
[email protected] said:
Once in a while i have the same problem, but when I clean the screen (until it looks shiny ) and it gets better…
(I clean mostly the top of the screen)
I don’t believe it is the “solution” but works for me…
Click to expand...
Click to collapse
If you push the End button (or any other button) before clean the screen, what happens. Does the screen stays black???
I think that this is a software problem, because other ways every time when I press the End button (or any other button) it will give me Nothing.
luba6ky said:
If you push the End button (or any other button) before clean the screen, what happens. Does the screen stays black???
I think that this is a software problem, because other ways every time when I press the End button (or any other button) it will give me Nothing.
Click to expand...
Click to collapse
[email protected] said:
Once in a while i have the same problem, but when I clean the screen (until it looks shiny ) and it gets better…
(I clean mostly the top of the screen)
I don’t believe it is the “solution” but works for me…
Click to expand...
Click to collapse
luba6ky said:
I have the same problem with 2 HD2 phones. Not aways, but most of the time. I ask this question before - http://forum.xda-developers.com/showthread.php?t=1349809 , but i didn't get the answer.
May be it is hardware problem, but if it is it's gonna make me a problems every time.
If you figure it out, pls PM me.
Click to expand...
Click to collapse
@all I found tht these help. The screen blacks out for about 5 seconds now... its more of a temp fix.
https://market.android.com/details?id=com.keyes.screebl.lite
And
http://forum.xda-developers.com/attachment.php?attachmentid=449922&d=1290758421
Credits go to Quiethinker over on a different thread - http://forum.xda-developers.com/showthread.php?t=1061481
Sent from my LG-VM670 using Tapatalk
black screen after recieving or making a call
Curiousn00b said:
Is there a fix for this? No matter what rom I use, Didn't try Froyo, but after receiving a call, the screen stays black, so I spam the hard keys to wake the screen after about a minute or so. Can anyone help?
Click to expand...
Click to collapse
I have the exact same problem. I am using the SD card android version. I've tried different ROMs, but with all I have this problem. When I boot into WinMo I don't have this problem at all, so it doesn't seem to be hardware related.
I can use the phone with anything else without any problem using the SD android version, only when I recieve a call or call out myself the screen blacks out and the phone seems unresponsive. After about 30 seconds to a minute the phone shows the lock screen.
I would love to work with the Android version for normal operation but because of this I still boot into Winmo within office hours...
erikgee said:
I have the exact same problem. I am using the SD card android version. I've tried different ROMs, but with all I have this problem. When I boot into WinMo I don't have this problem at all, so it doesn't seem to be hardware related.
I can use the phone with anything else without any problem using the SD android version, only when I recieve a call or call out myself the screen blacks out and the phone seems unresponsive. After about 30 seconds to a minute the phone shows the lock screen.
I would love to work with the Android version for normal operation but because of this I still boot into Winmo within office hours...
Click to expand...
Click to collapse
Your better off doing what I did. In Android, sonewhere in the settings for calling, change the sensor to off so it never blacks out. In Miui rom its in program's, then calls.
Sent from my LG-VM670 using Tapatalk
Task 29 and start fresh. Only thing that got rid of it, test when you first start the rom to make sure it works normal, then start adding your apps and such.
Or increase the 125mhz CPU settings to 245mhz under cyanogenmod settings/performance/CPU or governor settings.
Sent from my HTC HD2 using Tapatalk
my screen stay black (off) when i take the phone away from my face EVERY call as well. this is what i do and it works everytime.
1.)pull the phone away from my face (duh)
2.)starting with it facing the sky, i turn it to face the floor (when i say facing i mean screen up ... then screen down)
3.)as soon as i turn it back over (screen face up) it turns on
im thinking its a sensor issue??? either way it works and i dont go on a hardware button mash fest to turn my precious leo back on.
if this helps please send thanks ... if not tell me im crazy :-D
Curiousn00b said:
@all I found tht these help. The screen blacks out for about 5 seconds now... its more of a temp fix.
https://market.android.com/details?id=com.keyes.screebl.lite
And
http://forum.xda-developers.com/attachment.php?attachmentid=449922&d=1290758421
Credits go to Quiethinker over on a different thread - http://forum.xda-developers.com/showthread.php?t=1061481
Sent from my LG-VM670 using Tapatalk
Click to expand...
Click to collapse
I just download this apk and will try it ....
But I think it's hardware problem (may be with the sensor), because when I turn back on Win Mobile 6.5 i have the same problen ...
I think to bring the phone to service
... when I take it back will tell you what is exactly the problem ...
Task 29 then install windows, next install the right radio version , finally install the android
like dragonovus say´s try completly reinstalling android.
and please feedback here
BUILD.PROP baby!!! there is a tweak for this and i believe it works( in the prop ) dont know exact address but google "build prop tweaks" also use setCPU and set the lower number to about 350+ also try to use the end hardware button less cuz this has been addressed in another thread..... the button sticks or sum crap..... i use zmooth and never use the red end button........... good luck
Will try all, but now I use ' Screen stays on '
Sent from my LG-VM670 using Tapatalk
well ... for me Screebl Lite didn't help me
Reinstalling Windows is not necessary. Just make sure you have the right Radio and HSPL then do a task 29 before installing Android. But your problem is most likely hardware related. The end call button is most used and therefore prown the wear and tear... Try using the red end cal softbutton. I guess you only have that problem when you use the hardware button right?
In that case it's the problem with the button and not the software...
And at the end did anyone of u solved this? If u need help post reply or pm me. I think i have a solution for u.
Sent from my HTC HD2 using Tapatalk
PPKLP said:
Reinstalling Windows is not necessary. Just make sure you have the right Radio and HSPL then do a task 29 before installing Android. But your problem is most likely hardware related. The end call button is most used and therefore prown the wear and tear... Try using the red end cal softbutton. I guess you only have that problem when you use the hardware button right?
In that case it's the problem with the button and not the software...
Click to expand...
Click to collapse
Yes, man! I have the HSPL2.08 and radio 2.15.50.14 ... I think we all do. I can't use the soft buttons, because I can't see them. That's is the problem. The screen is black and won't lights up. May be I can't read you ... but I try to run back Win Mobile just to check is it from android OS or the sensor...
build.prop does not help
I tried the build.prop thing. I added those 2 lines at the end of the file:
ro.lge.proximity.delay=25
mot.proximity.delay=25
No change, still a black screen after any call.
Any other idea ? How to completely deactivate the proximity sensor ?
Fixed !
I finally fixed the issue by removing the screen protector sheet and cleaning the upper left part of the screen with a dry towel.
It works fine now. It was just a problem of the proximity sensor not being exposed enough.
I hope this helps.

Categories

Resources