WM6.5 build 21501 kitchen

[Baryn]

Originally Posted by meanfishy

not to split hairs but you have listed an Apache next to your name

what does the bootloader (tri color) screen say, so we know which unlocker you used.

Thanks for pointing that out. I hadn't noticed my profile was not up-to-date for so long.

The red row in my bootloader reads "TITA100 SPL-1.04.0000"

I was under the impression that the Titan didn't need to be unlocked prior to flashing. Or, in any case, I never had to unlock my Apache. It has been nearly a year since I've been actively involved in the scene, and with a new device it's no surprise that I have lost touch.

Any advice is duly appreciated.

[gguruusa]

Originally Posted by Baryn

Thanks for pointing that out. I hadn't noticed my profile was not up-to-date for so long.

The red row in my bootloader reads "TITA100 SPL-1.04.0000"

I was under the impression that the Titan didn't need to be unlocked prior to flashing. Or, in any case, I never had to unlock my Apache. It has been nearly a year since I've been actively involved in the scene, and with a new device it's no surprise that I have lost touch.

Any advice is duly appreciated.

I refer you to my first response:

Originally Posted by gguruusa

Exactly what is supposed to go on, at first. You have one of 3 problems: device isn't unlocked, device is apache, or WMDC needs updating.

All devices since apache require unlocking.

[meanfishy]

Originally Posted by Baryn

Thanks for pointing that out. I hadn't noticed my profile was not up-to-date for so long.

The red row in my bootloader reads "TITA100 SPL-1.04.0000"

I was under the impression that the Titan didn't need to be unlocked prior to flashing. Or, in any case, I never had to unlock my Apache. It has been nearly a year since I've been actively involved in the scene, and with a new device it's no surprise that I have lost touch.

Any advice is duly appreciated.

http://forum.ppcgeeks.com/showthread.php?t=33857

this post is what you need to do step by step instructions

[quadjacks]

can anyone see this, or is it being ignored!!!


when i receive a txt and open txt message, my cursor goes to the actual message instead of the input/type field, annoying... also unless i scroll through all the new txt message in the thread, they remain as new txt, annoying!!!!! is there a fix for either?

[meanfishy]

Originally Posted by quadjacks

can anyone see this, or is it being ignored!!!


when i receive a txt and open txt message, my cursor goes to the actual message instead of the input/type field, annoying... also unless i scroll through all the new txt message in the thread, they remain as new txt, annoying!!!!! is there a fix for either?

I had the same issues, what I had to do was;

1. for the input/type field I couldn't find a solution so I found if you double click the first letter of the word you want to type on the keyboard it will put the cursor in the text field. Example; you want to say "Hey" you type HHey the 1st letter puts the cursor into the text field

2. I cook my ROMs and added "delete all / mark all as read" this corrected the unread text issues.

[quadjacks]

Originally Posted by meanfishy

I had the same issues, what I had to do was;
........

its odd cause sometimes when i cook ,mark all as read, into my roms, it works, however, the last few times to include this one, it brings up the MMS properties.

thanks for the work arounds. meanfishy. does it seem like these issues have something to do with the kitchen roms?

[meanfishy]

Originally Posted by quadjacks

its odd cause sometimes when i cook ,mark all as read, into my roms, it works, however, the last few times to include this one, it brings up the MMS properties.

thanks for the work arounds. meanfishy. does it seem like these issues have something to do with the kitchen roms?

I've recently upgraded to the Touch Pro and now on the TP I'm having a similar issue. now when I try to use the mark all / delete all it sends me to my Blue tooth add a device screen and asks if I want to search for new devices.

I never had these issues before on the titan but now that you bring the point up about the ROMs. the only variable different (besides the phone ) was the fact I had to un-install and re-install the latest Builder OS. once I did this was when the read all /delete all issues started.

[quadjacks]

also after every soft reset my backlight default back to 10secs..... argh!!

[1900]

Originally Posted by quadjacks

its odd cause sometimes when i cook ,mark all as read, into my roms, it works, however, the last few times to include this one, it brings up the MMS properties.

I'm having the same issue
conflicting menu item id's
bah humbug.

[quadjacks]

Originally Posted by 1900

I'm having the same issue
conflicting menu item id's
bah humbug.

I've since re-cooked and now the mark as read now works.