|
||||
Definitely not 160+ issue ...
Quote:
It worked when I had my phone flashed to the Bell Mobility "stock" ROM (iirc) but has not worked since I got back into the self-cooking game with 1.0.1. ...tom |
|
||||
Ok I have 2 sorta major issues. 1 being that the CPU is stuck at 100% useage but I cannot find out whats causing it. Im using Vidya Task Manager and its showing the CPU at 100 which i can believe, but there is no process using the cpu cycles. 2nd is that the Data connection will not work. It keeps giving me a No Modem at this number error. I am going to check the forums for a fix on this because I know ive seen it before.
It seams that the CPU is stuck at 100% after a restore with SPBBackup. When I first got the rom installed and insalled the apps it ran pretty good. Bummer its not working as well as my first 3.5 rom. |
|
||||
ok....
Well all of a sudden when trying to recook a new rom to test the sprint vision issue.. and the dang creatos keeps throwing me an error message saying temp\dump\dpst.dpst already exist. Didnt do this yesterday. just my luck with this replacement phone I sware. im going back to my older working 3.5 untill i can figure this out.
|
|
||||
OK Verizon users affected by this SMS thing, can you please replace this file in the OEM_Helmi_Addition folder in \OEM and build a ROM to test to see if the problem is resolved?
Are users on any other carrier experiencing this same issue? I encourage everyone (who has a text messaging plan, anyway) to test the ability to send and receive SMS to and from your own carrier and other carriers. If you are having the same issue the verizon users are experiencing you can try this file as well, but please report in here so I can know which carriers are affected. |
|
||||
HT_SMS_Providers.dll vs. SMS_Providers.dll?
What is the difference between the 2? Palm SMS configures things to use SMS_Providers.dll - the kitchen has both versions, but HTC_SMS_Providers.dll seems to win.
They both seem to have the same exported functionality ... any one know the difference (and why there are 2 in the kitchen!?). Thanks, ...tom |
|
||||
Re: ok....
Quote:
And just FYI, dupe file errors in BuildOS are the easiest to troubleshoot because they tell you right in the error message what the problem file is. So then you just go to the kitchen, click the search button, and search for that file name--it will show you all the places the file exists. So you can conclude logically that you selected two OEMs which are mutually exclusive. Ideally buildos would be updated to allow some OEMs to have radio button controls instead of checkboxes (meaning it forces you to select only one from that category), but until (and if ever) that happens you just have to be careful about what boxes you check. The app is bare bones and doesn't really do any handholding. As for your 100% CPU issue, I would be hesitant to use backup apps. I have never trusted them to fully restore everything the way it was, and it sounds like you're seeing such an issue here. But you should also try another task manager (I suggest and can't speak highly enough about dotfred's superb app "Task Manager", which is selected by default in the kitchen) to verify that your CPU truly is pegged and not just an erroneous reading from that app you're using. |
|
||||
Yea...
The problem with buildOS is that it is giving me that error when I have not chosen more than one carrier. I created about 4 roms yesterday successfully to prove this. Today was a different story. I tried just deleting the OEM that was triping it up. (Yes one of the other carriers I didn't choose) and it ran into the error on the next carrier. I will mess with it more tomorrow. Might just need to reextract everything again.
As for the backup + 100% issue. I have a feeling you are right even though it is the latest 1.6.1 of spbbackup. It worked like a charm with my older 3.5 rom, but every time I restored with this one it is pegged at 100% with no sign of what's causing it. It does make it kind of suck since I like to keep my stuff intact for when the unforseen hard reset comeith, but the main thing I need safe are my text messages and this rom did supply me with multiple ways to save them. My biggest issue right now is my vision issue. I'm getting the No Modem at the dialed number error and its not the rom's fault. (Im back on the stock 2.2 atm as well as tried my old 3.5) I feel it might be something to do with the fact that I broke the rule of making sure I have a stock rom on my PPC when I bring it in for service. I had to be without service for 2 days on my phone and decided to prepair it for the day I get it back. Well the # codes she needed she couldn't get to ( and I'm still identifying the ones in the new roms menu ) I got it home with her instructions to get the phone working, but there must be something else she needs to do to get vision working. (or something just on their end.) Ok well sleep time now. see you all in the morning. |
|
||||
Re: Palm threaded messaging
Quote:
This was getting on my nerves a bit since it makes the 'reply' button totally useless, so I decided to try and go back to the Alltel rom and everything works fine. But when I re-upped to 3.5 it does the same thing again, mangling the message and from fields of SMSs. I aborted the carrier customization on the first upgrade (and completely cleared the extrom before the second upgrade, so it didn't even offer to try the carrier junk). There is something somewhere in 3.5 thats trashing the SMS from field, but I don't even know where to look. BUT, if one of you really smart guys wants to tell me what to try, I'm more than willing to give it a spin here and see if it fixes the problem. (I'm assuming its not doing this to ya'll or you would have more than likely seen it by now, or you just don't pay attention to incoming texts.) |
|
|
|