Helmi Official AKU 3.5 Kitchen 1.0.4 Bugs / Patches

[BenRivera]

Originally Posted by gguruusa

Since .5, PCMKeyboard and PCM don't share the same config file. In fact, the config file is lumped into the theme file now.

PCM isn't required for PCMKeyboard.

PCMKeyboard won't start if there isn't enough memory too. If you're using the large dictionary, it can take a few seconds for it load. If you're short on memory, switch to the small dictionary.

The keyboard applet in the settings panel doesn't work to well in the 1.04 kitchen (don't know about other ROMs/kitchens). Try using SIPchange or the little keyboard icon at the bottom of the screen. It's not necessary to reset after SIPchange.

I got a copy of cab version of the SIPChage (so I didn't have to reflash)and this has resovle my issue, but it does require a couple of steps to get it to work:
Change default using SIP Change
Use WM5 - System-Input-PCM Keyboard
Soft Reset
Now it works.... PCMK 0.7 is working just fine on 1.0.4 for me.

[gguruusa]

Yeah, I just tried it and I had to reboot too. Oddly, once you select a different SIP with SIPchange and then reboot, you can switch around between that one SIP and the stock SIPs but not any other. I did have one configuration where I could switch around between all the layouts even without a reboot, but that was a few ROM builds back.

[Kolano]

Originally Posted by gguruusa

The problems with the web distribution approach are: how to include copyrighted works, bandwith, and end user customization. Until someone comes up with a way around the copyrighted works problem, don't expect a web based solution.

• Copyrighted works: Both the current and any future web based distribution approach have this same issue. Generally, we do our best to tread lightly.
  
• Bandwidth: With appropriate caching, a web DL based could save bandwidth by limiting DLs to just the components a particular set of installs required, and/or by distributing the DLs more (i.e. getting OEMs from their authors rather than PPCGeeks).
  
• End user customization: The easy solution here is the enable a local file store as part of the solution. It's not clear how one might customize a web based install, but presuming some local caches were used one could edit those files. Much of this would depend on the sort of update/healing the web DL process provides. Generally, improved methods of packaging/editing OEMs could address this.

For now I think most of the update efforts are focused on providing better ways to set and transfer selections across runs (i.e. without manual edits of option.xml files)

[gguruusa]

Added to my ftp:
Optional_PocketCM_0.11b
Optional_PocketCM_KeybaordEN_0.7
Optional_Slide2Unlock1.20

and updated (because it had a typo in the .rgu file)
Optional_pBar1.4

[TripleDES]

I'm having some strange issues that I think have already been documented in this thread. I would like to know if I don't include this when building the kitchen and just install it into flash, will I still have these problems?

Trying to see if it's worth it generating and re-flashing. Thanks!

[aamon17]

I'm having the same problem running version 1.04. Here's what I discovered with my xv6700:

After a hard reset, I activated apps one at a time, did a soft reset, called my phone & it answered AS IT SHOULD. Here's the order I enabled (entered serials) for apps:
-- SPB Mobile Shell (soft reset, no problem)
-- SPB Pocket Plus (soft reset, no problem)
-- SPB Diary (soft reset, no problem)
-- SKTools (soft reset, no problem)
-- Tweaks2k2 (soft reset, no problem)
-- CorePlayer (soft reset, no problem)
-- Installed the Wireless Sync Client (soft reset, no problem)
***** Synced my email, calendar, contacts, etc... Did a soft reset, called my phone, and IT WENT TO SPEAKERPHONE automatically whether i press the answer button or soft key, & it registers a missed call. I tried sof reseting several times, but the problem wouldn't go away. *****

I did another HARD RESET to start over from scratch, enabling apps in the same order, soft resetting, then calling my phone. It works fine up until I sync my data via Wireless Sync.

Any thoughts on why syncing would be the culprit???

[IM0001]

Ok well I am loving 1.0.4 atm. 1.0.2 had an issue where my text messaging would be incredibly slow while typing (so it would lag behind and miss keys.) no longer a problem.

It still will not allow me to send a message over 159 characters though.

Also I cant seam to get activesync from starting up. I have the fake server hack and everything that has worked from the past (on this phone with 1.0.2 and other past roms) as well as my X50v in all its versions. (and yes schedual is on manual sync)

Odd.

Otherwise im loving it atm. Much better than 1.0.2. Hope there is a 1.0.5 someday soon here.

[gguruusa]

Originally Posted by TripleDES

I'm having some strange issues that I think have already been documented in this thread. I would like to know if I don't include this when building the kitchen and just install it into flash, will I still have these problems?

Trying to see if it's worth it generating and re-flashing. Thanks!

You either need to use the Pocket Plus OEM in my ftp folder or install from .cab. Either way will yield a fully functional Pocket Plus. The OEM the comes with the kitchen is not fully funtional.

[EtherealRemnant]

Yeah so I had a whole lot of problems with the kitchen. This thread is way too large for me to go back and read all 20 some-odd pages so I will just post the symptoms and see if anyone else had them.

The biggest thing is that I kept randomly losing my radio. I'd be without my radio over half the day and not realize it until I pulled the phone out of standby and the radio powered itself back on, then blasted me with 20 or 30 text messages and the voicemail indicator.

Also, the phone kept freezing. It would freeze 50% or more of the time when I'd try to make a call. It would just say Dialing... and that was it.

Then my last problem was that the touchscreen would not always register when it was pressed. I figured it was out of alignment at first but I aligned it like four times and it kept doing it.

Keep in mind that I cooked ROMs with the kitchen defaults and my own customizations and had these problems each time.

So finally, thinking that I'd bricked my phone, I went back to the 1.27 radio thinking that might fix it. It didn't. So I dumped off the kitchen and went back to JK's 3.5 C&S Sprint ROM that I know has always worked and I've been running it all day today without a single issue.

Anyone else experience any of the above?

[luv2chill]

I can't explain your magical results with Kirvin's ROM but losing your radio is a hardware issue. There's nothing in the software that can cause that. If you're losing your radio that could cause any number of the other issues (aside from the touchscreen) so you might look at trying to get the phone replaced.