Related
I am having problems with my XDA (T-Mobile Phone Edition). Here are the symptoms:
- The system runs extremely slowly (it takes several seconds for the start menu to come up, for instance).
- So, I soft-reset the device.
- The T-Mobile splash screen comes on with version info (4.01.16), but with an *empty* R and G above them. (No radio version displayed, and no whatever-G-stands-for displayed).
- I wait.
- I wait some more.
- After waiting about 20 minutes, the Today screen finally comes on. Again, the system is extremely slow, and the phone part does not work at all.
- If I try to boot into the Wallaby boot loader, I get the dreaded "GSM Error".
A little more info:
I had upgraded to 4.01.16 at a ROM kitchen about a week ago, as well as upgraded the radio stack to the latest T-Mobile (6.25.02 I believe.). The system was running fine until yesterday.
When I first discovered the issue yesterday, I tried several attemps to reboot, then finally had to resort to a hard-reset.
The hard-reset succeeded, then I reinstalled all my applications, settings, and data. I did a couple of soft-resets to be sure it was working. It was.
This morning, I noticed the extreme slowness issue again, and soft-reset the device, and the same thing happened.
So, I happened to be near my local T-Mobile retailer, and explained the issue. He played with the device for awhile and was on the phone with a technician from T-Mobile. He hard-reset the phone and declared it fixed.
He did say he had to change the internet settings from internet3 to internet2. My internet had been working fine all week, and I'm sure I was on internet2, but in his words, "If you are on the wrong internet setting, you can't connect to the internet, the phone, or anything." Now I know he's either full of it, or misinformed, although he was extremely helpful and pleasant.
So....the question is: What *is* going on with my phone? I saw a reference on this board to something called repair.zip, but I didn't see it associated with any particular symptoms, so I'm hesitant to try it yet.
I'm 90% sure that my phone isn't permanently fixed, so I'm putting this out to the gallant men and women of xda-developers for insight.
Thanks!
-Jason-
Windows Mobile 2003 has a realy nasty bug that microsoft is aware of and is providing a hotfix for.
WM2003 tends to not delete any notifications it collects from applications.
On Soft-Resets there are even more notifications wich in addition to the not deleted notifications from before add up and add up to more and more slow down the OS.
My advice since i'm extremly lazy and don't want to search for the exact link for the fix:
Go to this kitchen: http://xda.weblink.net/
And check the following 3 options:
create 'System Tools' subfolder under 'Programs'
- Check Notifications (Version 1.6 ) (29 kB)
- Notification Clear Fix (Version 1.1 ) (5 kB)
Registry hacks and defaults
- Fix 'multiple resets make device slow' bug (not A.30.0x)
while the first one gives you an application to manualy delete outdated notifications, the second one seems to be the official MS fix for the problem, while the 3rd seems to be an inofficial fix from the good guys here at XDA dev.
always worked for me
OptimismPrime said:
My advice since i'm extremly lazy and don't want to search for the exact link for the fix:
Go to this kitchen: http://xda.weblink.net/
And check the following 3 options:
create 'System Tools' subfolder under 'Programs'
- Check Notifications (Version 1.6 ) (29 kB)
- Notification Clear Fix (Version 1.1 ) (5 kB)
Registry hacks and defaults
- Fix 'multiple resets make device slow' bug (not A.30.0x)
Click to expand...
Click to collapse
Funny thing is, I'm pretty sure that I selected these options when I cooked my ROM. Looking in my startup folder, I see clear_notify.exe.
And I'm not entirely convinced that it is the problem related to the notifications bug anyway. What I'm seeing is that the entire GSM functionality seems to have been blown away somehow, and the device is acting as if something were cranking at 100% CPU.
Hi ...
I faced what you are talking about long time ago ... this is purely RSU problem and especially if the "Debug/Calibrate" option of the GSM is triggered by mistake or due to ROM bug.
Try to do GSM reset from the bootloader GSM menu ... it may take many times to stop this symptom ... but don't try to change the band!
Good luck.
JasonLP said:
I am having problems with my XDA (T-Mobile Phone Edition). Here are the symptoms:
- The T-Mobile splash screen comes on with version info (4.01.16), but with an *empty* R and G above them. (No radio version displayed, and no whatever-G-stands-for displayed).-Jason-
Click to expand...
Click to collapse
you have problem of your XDA GSM radio stack!
cgigate said:
you have problem of your XDA GSM radio stack!
Click to expand...
Click to collapse
How do I resolve this?
Thanks!
-J-
when you see "GSM Error" from bootloader.
it means you have bad radio stack upgrade, you need send to T-mobile to exhchange. so first thing you need send it back.
if they cannot help you, I could help you to repair it at a fee!
cgigate said:
when you see "GSM Error" from bootloader.
it means you have bad radio stack upgrade, you need send to T-mobile to exhchange. so first thing you need send it back.
if they cannot help you, I could help you to repair it at a fee!
Click to expand...
Click to collapse
Anybody else have any suggestions?
old boy this is a problem that is solved here daily. Search for "radio stack" on this site. You are sure to find the solution
Famous "GSM error" after upgrading,
The best way is to send to your service provider to repair (exchange) , see All USA based sad Radio Stack (Failed) users
you may see some solutions in the forum, but most of them not working (not duplicable) , it could make XDA worse. some people lucky, most people not.... search keyword "GSM Error".
Is there a way to program a softkey to turn on the flash to use as a flashlight? this would be cool.
TIA
There is software that will do it but over time you will damage the flash by doing this.
Where can we find this program?
5 seconds in a google search for "pocketpc flashlight" returned several hits. Why don't you try it.
Although there are a lot of hits for using the *screen* as a flashlight, there are few for using the LED flash on the back of the phone.
Of the few I've found (like VJCandela), none have worked for the LED flash on the Wizard.
famewolf said:
5 seconds in a google search for "pocketpc flashlight" returned several hits. Why don't you try it.
Click to expand...
Click to collapse
Don't be so mean famewolf.
famewolf said:
There is software that will do it but over time you will damage the flash by doing this.
Click to expand...
Click to collapse
In all honesty should the "flash" be even called flash? The camera sucks as is and the so called "flash" doesnt do crap except help me light things up.
Yea i want a program to turn on the LED flash when im not using the camera.
Also what do you guys mean by flash in the first few posts??? The screen or actual LED.
I think famewolf's post refers to apps that illuminate the screen and usually display a white image, as a simulacrum of a flashlight. These are ok, but could do with being superlit with an app like VJLumos II (which does NOT work on the Wizard AFAIK, untested).
However, the "flash" LED, which is unlikely to cause skin cancer or sunspots, is probably what the original poster wanted to control.
This can be controlled through software.
At least on the Universal, it's brighter and more focused then just using the screen, but is known to burn out after prolonged (hours) of use.
Hence it's probably more appropriate to describe its use as being in flashes, as opposed to a reference to its meagre candescence.
V
Ok. So does VJCandela work with an 8125?? Also, can someone tell me a free app that will use the screen as a flashlight. I see a bunch of apps but none of them are free. Has anyone tested VJLumos II on there Wizard/8125??
I atually meant to ask this. Several times, I've noticed the flash LED lit up without me doing anything. I first noticed it about 5 days ago. Yesterday, upgraded to 2.26 ROM and still the LED turns on at seemingly random intervals.
Anyone had this problem?
hiazle said:
I atually meant to ask this. Several times, I've noticed the flash LED lit up without me doing anything. I first noticed it about 5 days ago. Yesterday, upgraded to 2.26 ROM and still the LED turns on at seemingly random intervals.
Anyone had this problem?
Click to expand...
Click to collapse
i upgraded to 2.26 rom 2 days ago and havent had this issue yet....
No issues with that either.
So yes i would like to be able to control the LED not really the screen. I'd be ok if the LED busted but not my screen.
VJCandela doens't work on the Wizard. I've never had one in my hands so haven't been able to test the hardware and support it
V
freeyayo50 said:
Ok. So does VJCandela work with an 8125?? Also, can someone tell me a free app that will use the screen as a flashlight. I see a bunch of apps but none of them are free. Has anyone tested VJLumos II on there Wizard/8125??
Click to expand...
Click to collapse
Wizard tested! Not working, at least I could not manage...
Dats sux . Has anyone tried VJLumos II on a 8125 as well??
Same applies, VJLumos I/II was never written for or tested on the Wizard. The idea could and should work, but I'd need to have a wizard to test it and refine it on first
VJLumos I might work, but that's not recommended.
V
Ok, thanx Jay. They need to have those apps support more phones
shogunmark said:
hiazle said:
I atually meant to ask this. Several times, I've noticed the flash LED lit up without me doing anything. I first noticed it about 5 days ago. Yesterday, upgraded to 2.26 ROM and still the LED turns on at seemingly random intervals.
Anyone had this problem?
Click to expand...
Click to collapse
i upgraded to 2.26 rom 2 days ago and havent had this issue yet....
Click to expand...
Click to collapse
Actually the problem started before I upgraded to 2.26, but I upgraded thinking that flashing my ROM would fix the problem. It might be hardware related (it's bee dropped a few times). But I guess I got the flashlight feature for free.... just have to wait for the LED to burn out.
I have the 8525 with WM6 installed. About 1 in 40 times, the End Call option doesn't display that the call ended (on my side). I attempt to still talk to the other person but I can't hear them, though. After about 2 minutes later, it finally ends the connection. I must do a soft reset to temporarily fix it; the only drawback is that the most previous call isn't shown as being made.
About 1 in 80 times, the call attempts to be made, but doesn't connect at all. I try to End Call, but it seems to "freeze" the screen. The "Close screen" seems to help, as in 30 seconds the device finally quits trying to connect.
Another thing I noticed, after the phone freezes, the antenna signal drops to zero and then returns to about 2 - 3 bars of signal, about 5 seconds later. I'm not sure if that is the cause of the phone hanging, or not. Is there any kind of software to resolve this issue? It's really annoying! Thanks for any help!
is that a cooked rom or official? what's your radio version and carrier?
I'm thinking u need a different radio verson...(u must have hardspl to flash another radio version)...
I got the 8525 as a reconditioned from AT&T about 3 weeks ago. It came with WM5, and I had the above calling issues back then too. I then was informed on the boards here to upgrade to WM6, which I downloaded from HTC, via the AT&T website link.
As for programs, I removed the AT&T "bloatware" via the hard reset trick. Later, I installed S2U2, HTC Streaming Media, HTweakC2.1b, and the PTTFix software. One other program on the 8525 is OCN8 -- for my iBlue 737 Bluetooth GPS device. There are no other files that I can recall, except maps, songs, internet .jpgs, and (camera) pictures/videos.
Settings:
ROM Version: 3.62.502.3
ROM Date: 10/11/07
Radio Version: 1.54.07.00
Protocol Version: 32.86u.7020.23H
I do appreciate and try to understand all of the replies that I receive, and I do try to respond within a timely manner. I understand that people are busy and may have other careers as well. However, the thing that makes me pull my hair out is when someone starts to assist my problem, then just ditches the thread after my reply, without so much as an "I'm sorry, but I'm not able to solve your problem" at the minimum! Normally, I give a 48 hour window for the helper or any more helpers to reply before I get frustrated, but it's been way past that timeframe now!
I've noticed that phenomenon on 3 of my prior posts, each are on different subjects. It seems that after the first reply, no one but the original helper responds! If that original helper is busy, or just forgets about the thread, then I'm screwed over.
Sorry to rant, but I tried looking all over the boards for the best Radio program. All I seem to find is best ROMs, but not really Radios. I've seen 2 other Radio programs in signatures, but I'm not sure what one would be best for my purposes. I've seen mention of 1.47.30 & 1.47.00.10 in some members' signatures, but I'm hesitant to just "trial and error" one, for fear it would damage my device. I currently have the WM6 default 1.54.07.00 version, but it freezes up on making some calls and more often on ending a current call.
Anyone else for ideas or opinions on what Radio program to use? Please back up your opinion with facts when possible. I am not an expert on the device, just a new user who is afraid to ruin my investment.
Much thanks to all who read this post and reply to it!
Hi, just saw your thread & did not know U were still hanging....
I would try radio 1.48.00.00 first, then 1.47.00.10 or 1.50.00.00 if necessary. Seem's a lot of at&t users liked 1.48 from what I noticed (don't forget hardspl - use mrvanx guide in the Mobile 6 forum section)...
Here's the 1.54 thread with pro's, con's, and 1.48 at&t comments...
http://forum.xda-developers.com/showthread.php?t=334697&highlight=radio+1.48
galaxys said:
I would try radio 1.48.00.00 first, then 1.47.00.10 or 1.50.00.00 if necessary. Seem's a lot of at&t users liked 1.48 from what I noticed (don't forget hardspl - use mrvanx guide in the Mobile 6 forum section)...
Here's the 1.54 thread with pro's, con's, and 1.48 at&t comments...
http://forum.xda-developers.com/showthread.php?t=334697&highlight=radio+1.48
Click to expand...
Click to collapse
Thanks for the reply! I will do the hardspl first, then try to install the 1.48.00.00 Radio. I'll report back with details in a day or two.
My current Image Version is 3.62.502.3, and I am attempting to update it to 3.54.255.3.
I keep having errors while trying to install Radio Version 1.48.00.10 to my 8525, after opening RUU_Inside.exe on my laptop. I've even tried to install it from my microSD card, but I get the tri-color screen instead of the white background with text screen, shown in the online example. The 8525 ActiveSyncs to the computer fine, and the screen shows:
"Updating the ROM image on your PDA phone ...
Please do not remove the USB connection from the PDA Phone or launch any program during the update process.
Remember the operation will take about 10 minutes."
As soon as the above grey box pops up, ActiveSync drops after that box appears, then I get the following message:
"Error [260]: CONNECTION"
I've installed Hard-SPL v.7 onto the 8525 already. Not that it seems to make a difference, I believe, but other programs that are on it include: WMXL 8525 Keyboard Fix, S2U2 1.16, Resco Explorer 2008, PTTFix, MunduRadio, & HTweakC 2.1,
not sure, but did a "search" for error 260 & seems to be your pc usb port:
(use xda google search for any questions)
http://forum.xda-developers.com/showthread.php?t=368624
btw, u are using XP & not Vista on u'r pc.
My laptop has XP (Media Center Edition). I did a search as well, but it was dated back to 2007; I wondered if there was a newer fix than the one on that page, as it referenced the prior version of Hard-SPL. From the sounds of it, I have to install WM5 again, change the radio version (which was the only thing I need to adjust, as the voice calls have been a pain since day one), then reinstall all of my programs again.
I've heard people create ROMs. However, the radio settings can't be included in them . . . or am I off-base with that presumption? I am not that experienced to cook my own ROM, as I am still learning the nuances.
Well I broke down and went on AT&T's online chat. Sounds like there is no software to install to fix the issue. I hoped the radio version switch would help, but I couldn't get it to install! I guess it's back to the Replacement Depot on Sunday. I should return my device to WM5, which I hope to find the thread for on the board.
If interested, here's the key parts of the conversation:
Me: Hi, my 8525 is giving me trouble making and ending calls. It sometimes hangs, and doesn't quit trying to place the call. Once I reset it, it's fine until I try to end the call, it hangs up the call, but not showing so on my side
AT&T: Can you try hard shocking the phone for me please? A hard shock is taking the battery out while the phone is still powered on, and then power the phone back on once the battery is back in the phone.
Me: I received it as a reconditioned from the AT&T depot in Pittsburgh, PA. About 20 minutes later, it did the same thing, so I upgraded to WM6 and still the same issues
AT&T: If you continue to have these issues with this phone, you will need to take the phone back to the Device Support place where you got it from.
Me: Is that a common issue?
AT&T: Sometimes it is with at reconditioned phone.
. . .
AT&T does not have an update for the Windows Mobile 6 at this time. However you may check out HTC website at www.htcamerica.net/support/default.html and see if they have an update for this software for this phone.
Me: So it's the phone, not the software?
AT&T: Yes that is correct. There is a defect within the phone that is causing these issues. If you continue to have these issues with this phone, you will need to take the phone back to the Device Support place where you got it from.
Me: Are you able to explain what causes it that the Device Center doesn't catch it
AT&T: I am not sure what causes this issue.
Me: Like should there be anything done to prevent that from happening?
AT&T: It is hard to tell with reconditioned phones. It may be something that can be fixed and it may not. If the hard shock does not fix this issue and the Device Support cannot, then you will be given another phone.
ohpfan said:
My laptop has XP (Media Center Edition).
I've heard people create ROMs. However, the radio settings can't be included in them . . . or am I off-base with that presumption? I am not that experienced to cook my own ROM, as I am still learning the nuances.
Click to expand...
Click to collapse
Ok, your signature is looking good and that is some conversation with good old at&t...bla bla bla
To answer your question above, the chefs cooked roms do not include radio (because everyone around the world uses a different one). But, the Official WM6 rom's do (posted wiki & wm 6 section). So, why don't u flash the official wm6 since u have hardspl now? This in itself may resolve u'r issue (if u don't get the driver pc 260 error)! why would u want to flash wm5?
I was going to return my 8525 to the Service Depot where I got it, is why I mentioned returning it back to WM5 status. However, I wanted to see if it could be fixed by software first, but considering the above online AT&T chat, I am definitely going to get it replaced again. So, I want the 8525 to not show my "3rd party software" to ruin the warranty. I had the 8525 to individually remove the CABs under Remove Programs, and then I did a Clear Memory to default for good measure. Hopefully the Service Depot won't say anything about the device being altered that way.
Oh yea, I am going to get it replaced on Thursday. I will try to get them to give me a new one, not a reconditioned. That is, if there are even any new ones around anymore! It'd be a miracle if they gave me a new 8925 Tilt instead . . . lol I know -- keep dreaming! Wish me luck with a new 8525 though!
Well, I exchanged my current 8525 for another reconditioned one. The repair guy actually asked if I heard of the xda website (for help with my device!), lol!! He didn't go into detail about what this site does, just asked if I heard about it, and I affirmed that I did. Possibly he found traces of programs that changed settings, but he didn't rat me out. He sounded like he was confident that he fixed the phone dialing issues, but gave me a new one "just in case".
As soon as he gave it to me, it booted right up, without the calibration screen. He flat out told me to calibrate it, but it didn't appear. I was trying to see if it would act up with the dialing again, but noticed it didn't save the numbers on my SIM! I then decided to get rid of the bloatware via the Clear Programs and that lead to the calibration screen, finally.
So far it seems to work fine! I made about 6 calls this time and they seem to end properly. There is a slight 30 second or so delay when I press the button with the "red phone symbol" [end call] before the screen lights up again though. Is that normal?
Oh, I've only loaded up S2u2 so far. I will reinsert the others onto my memory card today sometime before work.
Again, so far so good! Only real issue I see is that the ringer volume is very low when the device is in the carrying case I have it in. I will search on here for a ringer volume changer, soon!
Glad U were able to get another phone!
"red phone symbol" [end call] before the screen lights up again though. Is that normal?
No, should end in a few seconds...doesn't seem it's even assigned to the phone (U can use Schaps Advanced Config tool to do this and many more good tweeks).
galaxys said:
No, should end in a few seconds...doesn't seem it's even assigned to the phone (U can use Schaps Advanced Config tool to do this and many more good tweeks).
Click to expand...
Click to collapse
The "end call" does it's job, just that the screen is dim then it takes like 30 seconds to brighten again to show that the call is ended. Possibly it's something I have set up wrong. I notice the blue backlight for the keypad doesn't light up until a minute of my typing on it for a text; it's like a delayed reaction.
(I have the unlimited text/pix/vid plan, as of this past Thursday.) A bit off-topic, but are the Yahoo, AOL, & MSN IM programs considered a text or do they use kilobytes of data? I could use the programs over the Wi-Fi if I had to, but I don't want to pay extra for data kilobytes.
Lastly, I have never downloaded the Schaps Configuration. What all settings should I change? I know it's mostly based on personal preference, but what are some common alterations using it? For instance, I set the alarm to wake up to, but it's only a short beep sound. If I really was sleepy, I would probably sleep right through it! Does this program (or any others) configure any song on my device to be the alarm? I've already done that to the ringtone (where the first 30 seconds of any song is my ringtone).
ohpfan said:
The "end call" does it's job, just that the screen is dim then it takes like 30 seconds to brighten again to show that the call is ended. Possibly it's something I have set up wrong. I notice the blue backlight for the keypad doesn't light up until a minute of my typing on it for a text; it's like a delayed reaction. check in Settings>System>Backlight & Keyboard Backlight.
(I have the unlimited text/pix/vid plan, as of this past Thursday.) A bit off-topic, but are the Yahoo, AOL, & MSN IM programs considered a text or do they use kilobytes of data? I could use the programs over the Wi-Fi if I had to, but I don't want to pay extra for data kilobytes. I don't use them, but it should be treated as MMS text.
Lastly, I have never downloaded the Schaps Configuration. What all settings should I change? I know it's mostly based on personal preference, but what are some common alterations using it? For instance, I set the alarm to wake up to, but it's only a short beep sound. If I really was sleepy, I would probably sleep right through it! Does this program (or any others) configure any song on my device to be the alarm? I've already done that to the ringtone (where the first 30 seconds of any song is my ringtone).
Schaps has a number of Performance, Power, UI settings, etc., but no alarm ringtones. U may not need Since u'r using HTweekC.
Click to expand...
Click to collapse
see info above...
Seems sun_dream found yet another build, hes saying is pretty fast, i cant wait till he releases it, heres the link to his blog post
edit:heres a mirror thx to homam_france
He has sent me a beta, which I will be testing sometime between today and tomorrow. I will post some feedback on this. Stay tuned!
I hope the shell won't distort the OK and X Buttons anymore
egzthunder1 said:
He has sent me a beta, which I will be testing sometime between today and tomorrow. I will post some feedback on this. Stay tuned!
Click to expand...
Click to collapse
Great, I just installed Xplode's R3. But i want to try it too.
egzthunder1 can i test it too?
i better get my BA fix up ASAP, the hardware buttons are not so responsive, it seems I am going to be busy flashing
Well,
Day 1 after flashing sun_dream's latest. So far, very fast and stable. Here are the main points (in my opinion anyways)
*Titanium seems a lot more responsive than before (I still don't like it though )
*The removal of windows and menus animations make the device respond faster overall.
*Unbelievably responsive kinetic scrolling.
*The honeycomb is actually usable now!!
*Settings were put back into categories (Personal, System, Communications).
*Battery life seems good, no major drainage.
*"OK and X" bug fixed and working fine!!
*Wifi nice and steady (still need to test PIE8 and Iris Browser).
*Transparent Top bar looks awfully nice! (too bad the programs replace it with the Black bar)
Things I did notice were as follows:
*The Wifi icon seems to be getting cut off from the bottom down. In other words, you can only see half of the icon.
*Power in the Power Settings doesn't show a percentage anymore.
I still need to do some further testing (e-mail setup, etc), but overall this rom is superb!
Will report back later.
Good Job Sun!!!!!
he sent me a beta too but got a big problem...my cradle ain't working anymore!
red_hanks said:
he sent me a beta too but got a big problem...my cradle ain't working anymore!
Click to expand...
Click to collapse
You can always use mtty and flash via SD.
hey Egz...I'd like to try that but I need my cradle so I need to go to a local phone store first thing tomorrow. I tried to fix the cradle myself but ended ruining it more so how is the 2117x build vs xplode's r3? 21169 x2 is so buggy so I flashed my BA back to wm6.1....
red_hanks said:
hey Egz...I'd like to try that but I need my cradle so I need to go to a local phone store first thing tomorrow. I tried to fix the cradle myself but ended ruining it more so how is the 2117x build vs xplode's r3? 21169 x2 is so buggy so I flashed my BA back to wm6.1....
Click to expand...
Click to collapse
I havent' had a chance to test xplode's R3, but sun's is a very nice rom (so far anyways). I still have to test BT (headset and GPS).
One thing I did notice also, is that it seems that data transfer via AS is a lot faster than in previous builds... I guess M$ finally did something right
You can read the rest of my review in my previoius post. Good luck with your craddle situation
A little further testing...
*I purposely soft reset the device and it took approximately 1 minute to wake up completely and loading PointUI Home 2. So, it has a very fast wake up time!!
*I set up my g-mail account with no problem.
*I don't use SMS, so I cannot test that.
*Lock application seems a bit faster and more responsive than in older builds.
*PIE is a bit faster, but I still have other browsers that I like to use. I will test YouTube later (with both PIE and Iris).
Left to do...
*Test BT connection with headset, and GPS (Pharos BT receiver).
*Test IR/BT data transfer... (I have to find another BT and another IR enabled device to do this)
*Must finish going through the settings to ensure that they all work.
Will do more later...
ok seems like 2117x is a lot stable vs the older wm6.5 builds..waiting for your BT test result...
red_hanks said:
ok seems like 2117x is a lot stable vs the older wm6.5 builds..waiting for your BT test result...
Click to expand...
Click to collapse
BT = Bluetooth?
if so, it's always a trouble-maker
i found strange issue with lockscreen, when you have locked your device and pressed power (entered standby) and recieve a call the answer lockscreen part does not show upon device resume, this bug does not happen when device is locked and not on standby - you may try the scenario yourself, i think that this bug is present in 21169 too (no matter sun or my roms)
tested various rom configurations, rebuilded about 20 times this rom, but this nasty bug stays
as of now I am very contented with wm6.1 v3.02 by sun_dream. I need to use my BA so I think I will just wait for a more stable build of wm6.5
Well, I tested (tried to pair really), my GPS receiver, but no dice... For some reason, the device either looses connection or just flat out does not recognize the pass-code. The BT headset, on the other hand hasn't given me too much trouble. It paired up nicely...
@xplode,
I'll give it a shot, but I don't normally use my BA as a phone (unless I am traveling)... which I will do on Monday, so I'll let you know then.
Still stable and no SR so far, except for one time when I was using wifi and my device went into power saving mode (turned off the screen) and afterwards, it would only have a black screen... had to SR there. I tried to recreate the situation on a few occasions with no luck... I guess it was a one time thing.
More reports to come..
well i had the same thing today, blackscreen - only fixed with hard reset
soft reset gets me back to the black screen
This appears to be a secret and private talks thread
Why are others kept in dark about the build 2117x? Once its disclosed that such a build exists, every one gets interested in trying it. If there is a reason for keeping it hidden from others for the time being, better use private messages. Just my two cents.
if we just talk about it, Microhell can't do something about it... now if we link to it here DIRECTLY, then xda-developers is in Trouble.
April 1 said:
This appears to be a secret and private talks thread
Why are others kept in dark about the build 2117x? Once its disclosed that such a build exists, every one gets interested in trying it. If there is a reason for keeping it hidden from others for the time being, better use private messages. Just my two cents.
Click to expand...
Click to collapse
@April 1,
The reason is rather simple. If you release something that has bugs and things (something you would consider a pre-release), you will have an enormous amount of people asking the same questions over and over and over and over.... and over again (kinda like it is right now but worse).
It is a lot easier to develop something when the beta testers are finding all the minor things and not hitting themselves on the face with major bugs that might require hard resets and stuff.
We are not trying to keep anyone in the dark (that is why we are reviewing this build), but sun_dream will release it when he deems it is ready for public use. So far, he has not made mistakes (at least not many) in his ability to judge when a rom is suitable for release.
Just be patient... this should be out soon
Let us track the OPEN issues on Android HD2, we will only discuss problems dealing with android alone, issues arised due to radio, WinMo rom and a specific android rom should be ignored.
AFAIK we still have 3 main Problems
1. GSensor/ Touchscreen Freeze.
Related Files in Android : \system\bin\akmd,\data\misc\AK8973Prms.txt and \system\lib\hw\sensors.xxxxx.so
(xxxxx = htcleo or default or qsd8k or ace or bravo based on the build)
This issue is not noticeable unless you a play game which uses Gsensor (Eg Abduction, NFS Shift ...)
This thread has lot more details about this issue and it could be a possible solution for you (it does not work for me though)
http://forum.xda-developers.com/showthread.php?t=803242
Possible Workaround :
1. Disable Auto-Rotate screen in Settings -> Display
2. Run the following commands in Terminal
mv \system\bin\akmd \system\bin\akmd2
killall akmd
To Restore
mv \system\bin\akmd2 \system\bin\akmd
Basically you are renaming the file 'akmd' which is responsible for the sensor to work
2. Data Disconnects
Related Files : \system\lib\libhtc_ril_wrapper.so
This thread has lot more details about this issue and it could be a possible solution for you (it does not work for me though)
http://forum.xda-developers.com/showthread.php?t=794309
Possible Workaround :
1. Switch Mobile Network OFF and then ON (Add a widget [Widget -> Settings -> Mobile Network])
2. Switch Airplane Mode OFF and then ON (Add a widget [Widget -> Settings -> Airplane Mode])
[EDIT]:
Guys looks like we got a fix.. this wrapper seems to work flawlessly as of now... you can try it here...
http://forum.xda-developers.com/showthread.php?t=824413
Just download 0.3 file and replace the file at /system/lib using root explorer
3. Occasional Black SOD and Accuracy in Auto Brightness
Newest kernals seems to have this issue, where the display stays black while the keypad lights glow.
Related Files : \system\lib\hw\lights.xxxxx.so
(xxxxx = htcleo or default or qsd8k or ace or bravo based on the build)
Possible Workaround :
1. Show the Sensor of your phone to some bright light source and your display will be back
2. Disable Automatic brightness in Settings -> Display-> Brightness
I will update this thread with Solutions as and when the developers fix it.
Whatever i have written is limited to my knowledge, it could be wrong, if so please correct me, Most of the vetarans know these issues and the work arounds, i have just put everything together for the new comers and to remind the developers of the existing bugs
Mods feel free to move the thread to General if need be.
Hi depakjan, This is great, thanks for tracking these issues.
can people confirm this "occasional bsod"?
i haven't seen it since light-sensor is calibrated.
i think the bsod is fixed with 2.12 radio and above..
Actually BSOD was introduced in the new lights file... it does not occur frequently... also if you have not upgraded you wont have it obviously...
depakjan said:
Actually BSOD was introduced in the new lights file... it does not occur frequently... also if you have not upgraded you wont have it obviously...
Click to expand...
Click to collapse
Just so people don't get confused.
BSOD normally refers to the Blue Screen Of Death on boot and should be fixed in the latest kernels.
The black screen due to no back-light is an issue with the auto-brightness and, AFAIK, only happens on CM6 builds that haven't had the correct levels setup.
I could be wrong though as I personally only used it for a few days for testing purposes.
Sent from my HTC HD2
hastarin said:
Just so people don't get confused.
BSOD normally refers to the Blue Screen Of Death on boot and should be fixed in the latest kernels.
The black screen due to no back-light is an issue with the auto-brightness and, AFAIK, only happens on CM6 builds that haven't had the correct levels setup.
I could be wrong though as I personally only used it for a few days for testing purposes.
Sent from my HTC HD2
Click to expand...
Click to collapse
I second that explanation ... and the auto backlight levels in CM builds may actually work better than Desire builds if tweaked properly... atleast for me the reaction time of the sensor is much faster ... accuracy still a problem
Accuracy is still a problem, so is Black SOD .. i have been getting this in Mdeejay's Revolution, HD .. latest ones...
it so happens when you have been talking over your phone for a long time(which blocks the sensor from light).. and then when you are finished with the call it wont wake up... maybe it did not sense light ... but after you show the sensors over a bright light source.. it comes back..
i have seen couple of posts and users mentioning about this...
lets see if everyone agrees that there is no Black SOD, i will modify the post for accuracy..
Support of HTC extended battery
I have tried a few android builds, but none of them seemed to support OEM HTC 2300mAH extended battery - after android booted up in the dual boot process, the HD2 powered-off by itself. I read some posts that acknowledged the problem, but I have not come across any android build that resolved this issue... Did I miss them? Thanks.
Can we also add tracking of Idle / Screen Off Battery Drain? Target is 5-8ma, some builds run at 100ma.
Is anyone's market busted?
Most apps won't install, but some do just fine. This started last night. I tested on 4 roms now and all exhibit identical behavior. This was NEVER an issue before.
(the stupid mount/unmount trick does nothing)
However, once they've d/led I can install them manually. Except for google voice. It refuses to install LOL. Google must have screwed something big here.
badmonopoly said:
Is anyone's market busted?
Most apps won't install, but some do just fine. This started last night. I tested on 4 roms now and all exhibit identical behavior. This was NEVER an issue before.
(the stupid mount/unmount trick does nothing)
However, once they've d/led I can install them manually. Except for google voice. It refuses to install LOL. Google must have screwed something big here.
Click to expand...
Click to collapse
There has been an issue internationally with access to the market for a while now. People were able to browse the market as normal but upon trying to install anything nothing would happen. This has been mentioned on several threads over this forum already and the problem is an intermittent one (obviously based on what server you connect to when trying to download anything).
Led Notification is not functioning, especially on Sense build.
backlight drivers are not working , it don't dim light when left without use (it closes the screen ) , as well as light sensor , doesn't dimm light only brightens the screen
jcc266 said:
I have tried a few android builds, but none of them seemed to support OEM HTC 2300mAH extended battery - after android booted up in the dual boot process, the HD2 powered-off by itself. I read some posts that acknowledged the problem, but I have not come across any android build that resolved this issue... Did I miss them? Thanks.
Click to expand...
Click to collapse
Try replacing the kernel from one of the Sense builds with my Alternative kernel.
Sent from my HTC HD2
hastarin said:
Try replacing the kernel from one of the Sense builds with my Alternative kernel.
Sent from my HTC HD2
Click to expand...
Click to collapse
. . . can I just 'tip my hat' to you hastarin . . . you 'd' man
And I'm hopeful that all the devs and chefs will have these problems solved before too long.
Viv la HD2 Android!
Reno_79 said:
There has been an issue internationally with access to the market for a while now. People were able to browse the market as normal but upon trying to install anything nothing would happen. This has been mentioned on several threads over this forum already and the problem is an intermittent one (obviously based on what server you connect to when trying to download anything).
Click to expand...
Click to collapse
What doesn't make any sense is that the app successfully downloads, but either stalls when it needs to d/l or tries to install and tell me it was unsuccessful.
hastarin said:
Just so people don't get confused.
BSOD normally refers to the Blue Screen Of Death on boot and should be fixed in the latest kernels.
The black screen due to no back-light is an issue with the auto-brightness and, AFAIK, only happens on CM6 builds that haven't had the correct levels setup.
I could be wrong though as I personally only used it for a few days for testing purposes.
Sent from my HTC HD2
Click to expand...
Click to collapse
I've found the backlight problem occurs (generally) if I unlock/lock the phone fairly quickly in a short space of time (and yes, I've only seen this on Hyperdroid 1.6 & 1.7, both CM6 builds). It's not consistently reproduce-able though, I can go several days without it happening, then have it happen a couple of times in a single day.
The touch screen is still active though, and swiping the unlock brings the screen back to normal brightness levels.
Tyrion84 said:
Led Notification is not functioning, especially on Sense build.
Click to expand...
Click to collapse
Works for me..could be your build ....try some other build...
hoss_n2 said:
backlight drivers are not working , it don't dim light when left without use (it closes the screen ) , as well as light sensor , doesn't dimm light only brightens the screen
Click to expand...
Click to collapse
this is already covered in the third point as accuracy
Works for me..could be your build ....try some other build...
Click to expand...
Click to collapse
Hi!
I wonder what "works for me" means. What exactly are your leds doing? On all builds i tried so far the left green led flashed about one time a minute green and nothing happened when the phone was charging. Are there some hidden settings or a special program for hd2 leds?
Cheers,
Otto