Related
On messages especially sometimes if I type too fast (and I can type very fast ) it misses out letters or just pauses for ages.
Most of the time the first letter I type in a message gets repeated. Sometimes it just decides to repeat one letter as if the key was stuck down.
On top of this messaging and any application where the device is trying to bring up a user input component is SLOW.
Ive not seen these problems mentioned anywhere yet. Is it just me?
Lewis
No, I've got the same problem. But I don't use that keyboard all that much. The main point for me was to get a phone/PDA with WLAN built in, something I believe the 9090 was first with.
same here, it's very annoying..
with the mms app this doesn't happen, input is as fast as in 2003..
Yeah, it is a bit laggy, still acceptable for me.
isn't it possible to somehow replace the messaging module? i use the keyboard very often and this can get really annoying..
I cannot speak for everyone, but I have found a solution that works.
Apparently, the Messaging applet is not getting enough clock cycles to properly process the keyboard input.
For me, simply closing Internet Explorer does the trick. (go into Memory, and make sure it's not listed in Running Programs) Try it now.
If it still occurs, soft reset the phone, and then attempt to use Messaging. Does the problem still occur? Probably not.
Let me know if this solves the issue. I will look more into it when I get the free time.
I found the keyboard horribly slow. That's straight after resets of all kinds and definately no IE.
I have the repeating problem at times, and I never run IE or any other programs at the same time minimized. I use PocketPlus, so programs aren't minimized, they are closed.
that's no good for me, still slow..
just installed rom 1.60c in my gf's qtek 2020 and it's fast as hell! messaging too..dont understand this strange behavior on the BA..
About the keyboard repeating, you can reduce the repeat rate at the keyboard settings..
Keyboard Issue
Has anyone actually solved the problem with the messaging program?
I downgraded back to WM2003 SE because message writing was such a pain. I would like to have WM5 but if and when someone can correct the messaging application.
Any news?
Thanks
Lewis
updated my Blue Angel to WM5 today and found no problem with typing. TheGadgetGuy's probably right about the memory.
I used to have the problem if I would type to fast it would repeat a lot, example "test" would be "testtttttttttttttttttttttt", I found a way to fix it:
A lot of people have been complaining with the same problems with the thumbboard in WM2005, well I found a way to fix it. As you know if you type really fast like a lot of us do with the thumbboard it will repeat and get stuck on a letter, example "fix" turns into "fixxxxxxxxxxxxxxxxxxxxxxx" then you have to backspace it all. Well let's just cut to the chase, the way to fix it is goto your Start > Settings > System > Keyboard > and goto Repeat Settings, and turn them all the way off (To the left). Tah dah, enjoy .
^The text above is copied from Zevink.com
Had all sorts of problems with WM5, one of the most annoying was this keyboard lag... I type a lot of SMS with it so this made the device unuseable for me.
Happily went back to 2003SE
The blue angel is the biggest pyle htc ever released. That is what is wrong with the ba.
Thanks for that Mikee4fun ... not quite so helpful ...
The only hardware issue I can see with the Blue Angel is with the Radio (Both Bluetooth and WiFi) in that they both seem to be poor in range and BT unstable. That said, BT in particular, may still be a software issue as under WM5 it seems a whole lot more reliable ...
To say the BA is a Pyle (Pile?) based on the fact that an internal thrown together version of WM5 (Trust me, this is the case if you do a bit of Hex editing on a decrypted nbf file and see all the temporary bootloader code which has references to ALL HTC devices by codename) is lacking in areas is not really a solid deduction. From what I have seen of this version of WM5 which has arguably been created in weeks rather than months like version 2003SE, I would say that it is on the whole a very impressive software and hardware solution.
I only hope HTC take the decision to officially update the BA to WM5 in order to fully eliminate all the software bugs in WM2003SE as even the current version of WM5 seems to me a whole lot better than even the latest patched WM2003SE version.
I cannot see it would take them a great deal more engineering time to correct the few issues that remain such as speed tweaks and the odd driver / software update to release a very impressive WM5 version. As Maimach has already proven a number of issues were quite simple to fix (Well, for someone as clever as Mamaich anyway!!!) ...
I had poor keyboard performance (lag) - made me downgrade
Bebbo, I'm afraid that won't happen because of the wish to make people buy new hardware instead of upgrading the stuff they already have. Remember that the biggest selling point of the Wizard and Universal is the WM5. So can HTC create a good WM5? Of course! Will their customers (not us, the providers, Dangaard and Brightpoint) allow them to? Probably not.
Well about the only thing that worked on WM5 was bluetooth...
I get the damned memory error on WM2003SE.... :x
How annoying. I think I'm going back to WM2003se. WM5 isn't that great. It behaves alot like WM2003fe except buggy :S It's not worth all the hastle just for on screen soft keys.
Hey guys,
First post on the forum, so I hope I don't offend/irritate with my dumbass questions,
I successfully flashed to the Black Shadow IV rom yesterday. I installed all th e helpful cab files to restore my settings to the orange standard and got the skdcert fix for the voicemail quirk. All seems (seemed) to be running smoothly but I then stumble upon a problem.
I have found that I am resetting the device more than I should due to the fact that whenever I try to make a call, 5 times out of 10 the phone just crashes, all the buttons freeze up and the touch screen doesn't respond. On the odd occassion the buttons freeze but the screen still responds butr there's no way to drop the call. It just wont have it.
I upgraded to the Black IV shadow rom, but did not upgrade the radio which was out of the box at version 1.38.00.01. Could this be the root of the problem? I am running SPL- 2.10 Olipro.
Any ideas guys, you're the experts, I'm just a squirrel trying to get a nut.
Thanks in advance.
Gav
The 1.38 radio is pretty stable. However, if you are in the US, you might want to try upgrading it to the 1.40 radio which is AT&T optimized.
That ROM was released and is supported here: http://www.4winmobile.com/forums/htc-hermes/
Same happend to me too, I used Black Shadow IV for a week and now removed it, It is not stable.
My Jasjam hangs all the time and when conncting to PC.
Regards
Yeah, same. I used it for 3 days or so and crashed frequently. No additional programs installed either. BAD ROM
i've had nothing but a good experience with Shadow IV. ::shrug:: seems stable enough to me. it's never locked up on me and i've never had to reset except when i chose to to clear out the old memory once in a while.
as i mentioned in another thread, i have not installed any spb apps since they seem to have problems w/ WM6. i've had problems on a couple of different ROMs w/ the Spb apps.
could it be something that you've got installed and not the ROM itself? i had to do a little process of elimiation by installing basically one or two apps a day and seeing how it ran. things started going badly when the Spb apps were on there (Mobiel Shell, Time, Weather, Diary) so I haven't reinstalled them.
anyway, it could be something other than the ROM that is causing the instability.
regards,
mark
having multiple problems as well. cannot send text messages on cingular even after trying multiple fixes, frequent slowdowns, have had to soft reset at least once daily and also having problems with random lockups when charging. Going to reflash another rom.
having multiple problems as well. cannot send text messages on cingular even after trying multiple fixes, frequent slowdowns, have had to soft reset at least once daily and also having problems with random lockups when charging. Going to reflash another rom.
Am on Orange UK, and after running Black shadow for a while now I would rate it as the most stable ROM I have used. Admittedly I have only dabbled with some of the others, but have not felt the need to do more as am happy with what I have.
I did have an issue with SPB weather that others did not seem to have, but after romoving it, everything seems to be running fine. I soft reset every few days etc but I am happy with that.
Tis a bit strong to write BAD ROM with such certainty based on an individual experience, given that it works well for so many. Perhaps "This ROM did not work well for me" would be better.
Just a thought.
Sleuth255 said:
The 1.38 radio is pretty stable. However, if you are in the US, you might want to try upgrading it to the 1.40 radio which is AT&T optimized.
Click to expand...
Click to collapse
May be it is the radio rom, I have now installed radio 1.38 then Black Shadow IV and will try it for a few days and see how it works.
Also crash
Also crash and then back to Black 3.5 rom is Stable!
Still the same even with Radio 1.38, Crash when connected to PC and deep sleep in standby.
Use to have same problems while running CE-Star. Virtually permanently freezing on making/receiving calls, sending SMS and simple operations with the device.
After manualy setting chinese character set (thanks to XDA-Devs WIKI ) the ROM is extremely stable. Even trying to "destroy" the system with multiple operations (calls, internet browsing, sync, installing new soft, etc.) do not freezes it - very stable.
Suspect in your case you are using software which makes some changes to the system, consequently destabilizes the ROM
marttin said:
Use to have same problems while running CE-Star. Virtually permanently freezing on making/receiving calls, sending SMS and simple operations with the device.
After manualy setting chinese character set (thanks to XDA-Devs WIKI ) the ROM is extremely stable. Even trying to "destroy" the system with multiple operations (calls, internet browsing, sync, installing new soft, etc.) do not freezes it - very stable.
Suspect in your case you are using software which makes some changes to the system, consequently destabilizes the ROM
Click to expand...
Click to collapse
Hi,i am runing Black 3.0.1 and ce-star,like ou said freezing ,and my problem is when i use CE-STAR keyboard,it is Freezing too.where i can find the setting chinese charscter set?
thanks
Been running Black Shadow for 5 days, alongwith Radio 1.43, without any problem...
I've been running Black Shadow on T-mo US w/1.43 rom and I've had no problems.
I have been running Black Shadow since it was released and no problems so far.
chg1282002 said:
Hi,i am runing Black 3.0.1 and ce-star,like ou said freezing ,and my problem is when i use CE-STAR keyboard,it is Freezing too.where i can find the setting chinese charscter set?
thanks
Click to expand...
Click to collapse
Use WIKI and SEARCH funstion
You can go first to http://wiki.xda-developers.com/ and click on Hermes. After that use SEARCH function with keyword "chinese". Should get the following page:
http://wiki.xda-developers.com/index.php?pagename=WM5_Tweak_Language_Chinese
I am using for few days Black Shadow with 1.43 Radio, able to read Chinese Characters thanks to the described in WIKI method and no problems. Personaly I installed A4 input method as it serves me at best. I didn't change the registry manualy, but used the cab, it works perfect. Simply follow the instructions.
The only issue is that when serving internet with IE Chinese sites do not apear properly. Suppose it is needed additional fixing of the fonts in IE. Do not have time at present to explore the issue, but suppose to deal with it next week. In case you find a solution for IE please share the method on this thread-- Thanks
PS. Have tested Micrsoft Input -- simply do not works. Causes a lot of problems and destroys totaly the standard inputs
All,
I have been running this ROM for just under a week and the thing has been 100% solid - not a single problem.
I also agree with a previous statement in this thread, that to refer to the ROM as "BAD" based on a single attempt is somewhat unfair! Maybe it is this sort of thing that has forced some of the more senior Hermes developers away from this site and on to another location. Ever thought about it that way?
It is just my opinion, but we (all forum users) should do one of two things if we "chose" to use someone elses development. They are,
Acknowledge (privately or publically) the time and effort that has gone into producing something. The best way to do that is by constructive feedback even if the experience hasn't been as you expected
Say nothing if you can't make it constructive!
To place a one liner in a response with a "throw away" comment is about as useful to either the developer or the other forum users as.........well,..................no I won't go any further because it's not constructive
For the record - this version of the Black release has rectified a localised issue I was having with my WLAN that other version had not resolved.
If you chose to use it - great, join in. If not, equally great. Good luck with your chosen selection of ROM.
Rant end
marttin said:
Use WIKI and SEARCH funstion
You can go first to http://wiki.xda-developers.com/ and click on Hermes. After that use SEARCH function with keyword "chinese". Should get the following page:
http://wiki.xda-developers.com/index.php?pagename=WM5_Tweak_Language_Chinese
I am using for few days Black Shadow with 1.43 Radio, able to read Chinese Characters thanks to the described in WIKI method and no problems. Personaly I installed A4 input method as it serves me at best. I didn't change the registry manualy, but used the cab, it works perfect. Simply follow the instructions.
The only issue is that when serving internet with IE Chinese sites do not apear properly. Suppose it is needed additional fixing of the fonts in IE. Do not have time at present to explore the issue, but suppose to deal with it next week. In case you find a solution for IE please share the method on this thread-- Thanks
PS. Have tested Micrsoft Input -- simply do not works. Causes a lot of problems and destroys totaly the standard inputs
Click to expand...
Click to collapse
thanks a lot
Has anyone been able to figure out why the ATT roms are experiencing the numlock situation when on a phone call. This seems to be the only issue I have experienced on this ROM but is quickly becoming a showstopper.
Number keys stuck while in-call. Doesn't seem to be resolved yet per the Pro's
"8/04/2007 Originally Posted by schaps
Not yet, this problem also occurs on official WM6 ROMs so it doesn't help me to focus the problem.
But for sure this issue is not caused by the keyboard driver."
Put me in the list of people wanting a fix for this. I hope someone figures it out. I often like to text while using my bluetooth, and I don't enjoy having to pull out my stylus to do so.
Just wishing the talented developers some luck in figuring out the problem!
Add me to the list too ... i've looked all over but hadn't found the fix. I remember seeing it somewhere when doing my WM5 ROM upgrade (a long time ago).
Any progress on this?
I'm using Shamanix's Ultimate 1.0.
I don't need to send SMS while calling but I've got the device locked and if I need to check the Calendar during incomming call for example, I need to type my password. Would be really nice to type on QWERTY instead by stylus.
thx
This has been Fixed In More than One Rom....TNT,Vp3g's plus other Roms... I"m going to be Compiliing a List soon of Roms that do and Do not have this Fix.... Certain Schaps Rom also have this Fixed as well but not all...sometimes either he forgets or They Fix interferes with other things onthe ROM not sure....
I can definitely vouch that it works correctly in vp3g's rom.
Would be nice to know what is causing this and how exactly they managed to get it to work so we can fix this on our ROMs.
the fix is already there.
http://forum.xda-developers.com/showpost.php?p=1562185&postcount=63
I have been using cooked ROMs for so long now that I can't even remember. Only very recently have I been forced to use official ROMs becuase of unavailability of HardSPLs.
I have only had this issue with two devices the Touch Pro2 and Imagio but i'm pretty sure that it happens with other models also.
Error examples:
'a problem has occurred with fexplorer.exe'
'a problem has occurred with services.exe'
I am a flash freek and every time I load about 100+ games and about 150+ applications so before everyone starts saying that when you load so many softwares something bad is bound to happen. I have already considered that but here is why i thing the problem is with official ROMs.
- I flashed official ROM and hard reset
- I first left out all the games and only installed the applications but the problem was still there.
- I then split the applications in half and after another hard reset tried with first batch and problem was there. I hard reset and also tried the second batch and problem was there.
- I am not so desperate an i am installing softwares one at a time and then testing for 10-15 mins and then installing the next software to pinpoint the problem.
even with the last approach I cannot pinpoint which software is causing the problem. Sometimes the phone crashes after 10 applications installed and sometimes after I reach 40 applications.
Now some of you will ask and suggest if maybe the problem is with the softwares. Most of the softwares I have are from freewarepocketpc.net but how can it be the software when all these softwares are the same ones that I have been using without any issues on Cooked ROMs for months and not a single crash on the Cooked ROMs.
I have been scratching my head and trying to figure out what is that secret ingredient in the Cooked ROMs that make them so stable and what can we do to make our official ROMs stable.
At one point I though Microsoft .NET Compact Framework was the culprit and so I tired several times with and without it installed and the problem was still there so I ruled it out.
I also tried installing SDK certs on the official ROM but that did'nt fix it either.
Help me out here guys, what am I missing, whats that Secret Ingredient in the cooked ROMs that make them so stable?
Fairy dust, us cooks sprinkle a little over the rom in the building process and it makes them super stable.
Personally I have never had those two errors on a stock rom. Might I ask which brand of those phones are you using? (aka, is it an AT&T, Telstra, Verizon, etc.) Sometimes (make that 99% of the time) the carrier's version of a rom is THE WORST there can be, causing problems like that.
With that note out of the way, you have tried using it without installing anything for a bit to see if the problem still persists right? If not, it could be one, or more likely more than one application is causing it to die.
the secret words for tonight are
"disable error reporting in your ROM"
most of cooks use this secret weapon.
=)
shadowline said:
Personally I have never had those two errors on a stock rom. Might I ask which brand of those phones are you using? (aka, is it an AT&T, Telstra, Verizon, etc.) Sometimes (make that 99% of the time) the carrier's version of a rom is THE WORST there can be, causing problems like that.
With that note out of the way, you have tried using it without installing anything for a bit to see if the problem still persists right? If not, it could be one, or more likely more than one application is causing it to die.
Click to expand...
Click to collapse
For Verizon Imagio i've used the official shipped ROM
I also had the same problem on the T-Mobile Touch Pro2 with its shipped WM6.1 ROM and once the HardSPL came out, i tried with the European Pro2 WM6.5 Official ROM and that also had same problem.
Yes I tried using the ROMs without any softwares and they work just fine. So that brings me to the conclusion that the softwares that I am installing are causing this but the problem is how to pinpoint which softwares and if it turns out that a wide variety of softwares are causing this (my suspicion) then why is it happening only with official ROMs and not cooked ones?
serfer222 said:
the secret words for tonight are
"disable error reporting in your ROM"
most of cooks use this secret weapon.
=)
Click to expand...
Click to collapse
Does this mean that windows mobile is so unstable that the only way to fix it is to give an illusion of stability by disabling the error reporting?
Say it isn't so, I love WM and if things are so bad with it then I have nowhere else to go.
serfer222 said:
the secret words for tonight are
"disable error reporting in your ROM"
most of cooks use this secret weapon.
=)
Click to expand...
Click to collapse
We have a winner!
Thanks
serfer222 said:
the secret words for tonight are
"disable error reporting in your ROM"
most of cooks use this secret weapon.
=)
Click to expand...
Click to collapse
After thinking about it a few minutes I get it now. I am shocked that I spent over week testing hundreds of softwares one by one when I could have just disabled the reporting. Thanks for the secret ingredient, i'll give it a go and report back in 1-2 days how my ROM is responding. I can already notice a slight increase in speed.
I know this is blashphemy on XDA, but I have the opposite issue. I've never encountered a cooked ROM as bug free as a stock ROM. Maybe this is b/c I've never bought a carrier phone and always gone for the unbranded, unlocked device, so I've had a clean stock rom to start off with... But with every cooked ROM I've tried (and to be fair, I don't flash regularly like I used to - so maybe things are getting better), there's always something wrong even if its a minute detail like text out of place on some screen hidden away in settings that most users don't find, or lost functionality of special buttons in oem programs like Opera (that most XDAers don't know about b/c they flash the first day they get the device), or lack of proper support for landscape, or improper bluetooth implementations where A2DP doesn't work like it used to, etc.
sonus said:
I know this is blashphemy on XDA, but I have the opposite issue. I've never encountered a cooked ROM as bug free as a stable ROM. Maybe this is b/c I've never bought a carrier phone and always gone for the unbranded, unlocked device, so I've had a clean stock rom to start off with... But with every cooked ROM I've tried (and to be fair, I don't flash regularly like I used to - so maybe things are getting better), there's always something wrong even if its a minute detail like text out of place on some screen hidden away in settings that most users don't find, or lost functionality of special buttons in oem programs like Opera (that most XDAers don't know about b/c they flash the first day they get the device), or lack of proper support for landscape, or improper bluetooth implementations where A2DP doesn't work like it used to, etc.
Click to expand...
Click to collapse
I think a lot of cooks are very short-sighted on these issues. I have a habit of testing every button, every program and every feature multiple times before a ROM goes out the door, and I still miss things. Many of the factory ROM's I've used are bad in this regard as well (my Fuze connecting to a secured WiFi network for one). Cutting off the error reporting doesn't really do that much, but I've had crashes before where I had to turn it on to find a bug that was stopping the ROM from working.
Dizzy looking at ...
Man, I got dizzy by looking at your avatar.
Everyone says that.
Hey guys, i haven't ever really posted on here other than when i first got my TP2 months ago. Since then i have had 9 replacements for various things, all of which have been hardware related. Things like constant freeze-ups, always telling me i have un-read messages when i don't...anywhere. and some others but those two are the main ones. So i am asking you guys what do i need to do to stop myself from body slamming this phone across my living room? Every single phone i get has the un-read message problem. And after about a month of use they all constantly freeze. I can't stand having to do literally 8+ battery pulls a day because the phone doesn't want to work anymore.
Any ideas? What ROM are you guys all running and what seems to be the most stable? I have never upgraded a ROM before so i have no idea what i am doing there as i have always been a MAC user. However, i do have access to a PC. Any help would be appreciated.
EDIT: Another thing it does is when i get a call or text the phone will vibrate non stop until i turn it off and restart it. This also happens 2-3 time daily.
irishguy0224 said:
Hey guys, i haven't ever really posted on here other than when i first got my TP2 months ago. Since then i have had 9 replacements for various things, all of which have been hardware related. Things like constant freeze-ups, always telling me i have un-read messages when i don't...anywhere. and some others but those two are the main ones. So i am asking you guys what do i need to do to stop myself from body slamming this phone across my living room? Every single phone i get has the un-read message problem. And after about a month of use they all constantly freeze. I can't stand having to do literally 8+ battery pulls a day because the phone doesn't want to work anymore.
Any ideas? What ROM are you guys all running and what seems to be the most stable? I have never upgraded a ROM before so i have no idea what i am doing there as i have always been a MAC user. However, i do have access to a PC. Any help would be appreciated.
EDIT: Another thing it does is when i get a call or text the phone will vibrate non stop until i turn it off and restart it. This also happens 2-3 time daily.
Click to expand...
Click to collapse
What version of TP2 -- e.g, T-Mo USA, Verizon, World-Wide/Euro -- do you have?
irishguy0224 said:
Hey guys, i haven't ever really posted on here other than when i first got my TP2 months ago. Since then i have had 9 replacements for various things, all of which have been hardware related. Things like constant freeze-ups, always telling me i have un-read messages when i don't...anywhere. and some others but those two are the main ones. So i am asking you guys what do i need to do to stop myself from body slamming this phone across my living room? Every single phone i get has the un-read message problem. And after about a month of use they all constantly freeze. I can't stand having to do literally 8+ battery pulls a day because the phone doesn't want to work anymore.
Any ideas? What ROM are you guys all running and what seems to be the most stable? I have never upgraded a ROM before so i have no idea what i am doing there as i have always been a MAC user. However, i do have access to a PC. Any help would be appreciated.
EDIT: Another thing it does is when i get a call or text the phone will vibrate non stop until i turn it off and restart it. This also happens 2-3 time daily.
Click to expand...
Click to collapse
The things that you mention are not hardware problems but software. So they can be solved by flashing a new rom. I suggest you read the how to flash for noobs thread.
Try a valkyre rom and read the last pages of that thread to see if there are issues etc
A new ROM may very well help sort out your problems, but the excessive problems you have been having make one wonder if there is not some other issue. So before you go to flashing a new rom, it might be a good idea to do some troubleshooting first to try and narrow down the problem.
First, a few questions:
1)What UI are you using? (i.e., Touchflow 3d, Sense, SPB Mobile Shell, Titanium, Classic today?)
2) What programs are you installing?
3) Are you doing any registry edits? Or using custom programs that do registry edits for you? (Things like configuration tools that you installed)
While answering the questions may shed some light on why you are having problems, here is the first thing I would try that could help narrow down the issue:
1) Dissable any custom UIs (start -> settings -> today -> items tab -> select Windows default -> hit OK) then soft reset your phone. Use it for a day and see if any of the problems go away, then report back.
I've got some other ideas, but will hold out on those until looking at your responses to the others above... good luck.
Hey guys and thanks for the replies. I am on a Verizon TP2. Running the stock HTC Sense ROM that came on my last replacement. I do not have anything custom running on the phone and only have 2 apps on the phone itself (facebook and personal assistant). I have given up putting them on there since i have been replacing the phone so often. Problems are still happening.
Thoughts?
Have you tried yet dissabling sense and running for a day to see if there are any improvements? If that doesn't work, I would move on to a hard reset, then disable Sense, and see if it is better. If it was, I would re-enable sense and dissable the email and sms tabs and see....
Meanwhile, I would also be reading the newbie guide to flashing new roms... as it is really odd to be seeing these sorts of problems with nothing installed on the phone.
I am correct that you haven't installed the facebook and personal assistant programs since your last hard reset? I only ask because the product description for the personal assistant looks like it is somewhat invasive into your phone (i.e., it can track minute use and such) and could possibly be the culprit for some or even most of your issues...
irishguy0224 said:
Hey guys and thanks for the replies. I am on a Verizon TP2. Running the stock HTC Sense ROM that came on my last replacement. I do not have anything custom running on the phone and only have 2 apps on the phone itself (facebook and personal assistant). I have given up putting them on there since i have been replacing the phone so often. Problems are still happening.
Thoughts?
Click to expand...
Click to collapse
ur previous statement says your a mac guy. what a re you doing with a windows phone? thats just a recipe for disaster.....
try flashing to an NRG rom. I personally have been using cookie energy for months and never had any problems. this may be a lil too complicated for a "mac" user tho.