8 APR 09 - UPD 25: Mods please lock this thread! - Page 140

hairdewx · #**1391** (**permalink**) 03-12-2009, 02:52 PM

Quote:

Originally Posted by Kamokazi

I know he has another set of drivers installed already...they may be butting heads. I thought it was the Omnia driver, but I could be wrong

That may explain it. Is there a way to fix it without having to recook a rom?

jucytec · #**1392** (**permalink**) 03-12-2009, 03:52 PM

Quote:

Originally Posted by zim2323

Care to share? =)

Will upload when I get home...

reigndropz · #**1393** (**permalink**) 03-12-2009, 04:55 PM

This is a probably a simple fix so hopefully you guys can help. I installed a different clock on the kitchen and it works except that all the other tabs have that white box in the upper left corner. I think it may have to do with the background4all app, but theres no where to edit that on here. How could i remove that program if I wanted to?

Fronc · #**1394** (**permalink**) 03-12-2009, 05:02 PM

Good to have you back, Scott.

I don't know what you've got in store for us, but I just figured I'd throw in my own opinion:

I suggest beginning to implement the XBmod TF3d update from the TP2. Looks fantastic.

I've been waiting for you to come back though to ask: what is the free RAM after a fresh flash supposed to be for the Rev.B Kitchen/20931 build? I show 48mb free, and it seems kinda weak...

EDIT: thats 48mb free on reboot, not on a fresh flash, or else I wouldn't be asking. I've been running the same flash for a few weeks.

**rainfreak** · #**1395** (**permalink**) 03-12-2009, 05:12 PM

Quote:

Originally Posted by Fronc

I've been waiting for you to come back though to ask: what is the free RAM after a fresh flash supposed to be for the Rev.B Kitchen/20931 build? I show 48mb free, and it seems kinda weak...

EDIT: thats 48mb free on reboot, not on a fresh flash, or else I wouldn't be asking. I've been running the same flash for a few weeks.

That's about what I have. I am also running a rom cooked with the Rev. B Kitchen and the 20931 sys. I show 75.84MB running after a soft reset, with minial stuff in the background (though I am running the HD Manila port). But with a Sprint TP, that leaves me 115.32MB available, so I am still only using about 40% of the memory.

**scrosler** · #**1396** (**permalink**) 03-12-2009, 05:50 PM

Quote:

Originally Posted by aldojr80

We are all glad your back i really mean that i hate that i had to go cold turkey for this long. And 21018 is worth it in my opinion i have found it very stable and fast but whats with this other one your talking about something that will blow our mind.

Thanks and sorry. I have cut back my "usage" until last night. I started flashing liek freakin crazy again! The adrenaline rush..... ahhhh.... Feels good to be back "mentally" ;c)

Quote:

Originally Posted by oldman

I think that if you're going to have it available in the B2B ROM, then it should be fixed. If you want to change the B2B ROM to include 018 or 931 instead of 015. However, there are so many different OS options, I don't see a need to keep that particular version, but if it stays, it should be fixed. You do such a good job with the kitchens and OS's, you don't really want to have a "faulty" one available.

bob

EDIT: 21015 build autorun issue... Ok... I have revamped the entire boot process / kitchen anyways.... May it fix the issue? Hmmm... Just have to see...

**scrosler** · #**1397** (**permalink**) 03-12-2009, 05:54 PM

Quote:

Originally Posted by gman4471

Welcome Back!

There is also an issue with the stock battery meeter in the recent builds. While the percent over icon works fine, the stock icon does not show an accurate reading. E.g. it will say that the device is plugged in even after it has been removed from the charger for over an hour. I tried messing with the registry settings that control the battery refresh but it did not seem to make a difference.

Strangely, if you do not select a battery icon in build os, the meter functions fine although the missing cab error prevents customizations and auto config from running completely.

Missing cab error? OYou mean when you dont select a battery icon?

To use the stock battery you should choose that option. The only thing it does is install a completely empty, non provisioning cab. In other words it does nothing at all. Tricky ****y, hey?

**scrosler** · #**1398** (**permalink**) 03-12-2009, 05:56 PM

Quote:

Originally Posted by oldman

I also have a similar problem. Only, it's both ways. Sometimes it doesn't charge when it's plugged into the charger. Last time, I had to do a soft reset to get it to charge the 5% battery. Other times, like you, it registers it's being charged even after it's been removed. Other times, it's stopped charging before it's fully charged. However, I (personally) have considered this a hardware issue. I believe that there is a temperature sensor in there someplace that will stop the charging cycle if the battery gets too hot (or the temperature sensor (wherever it is) trips like a circuit breaker. I have also noticed that even in normal operation, sometimes the case feels hot. If I am correct, that warm case could possibly "trip" the breaker, preventing it from charging. I could be wrong....there could be some software connection between the two....
But now you have my two cents worth (that's probably only worth about one cent)

Bob

That is nearly dea on. The battery hase temp sensors and if you trip it I "beleive" you need to soft reset to rip it back.

But in all honesty, what you are describing and the other dude....

Not hardware, more like an app effin with the refresh of the screen or some sort of lag caused by an app.... This is my guess off the top of my head. Withouth know your exact config its really hard to say. I would only consider it a hardware problem if you load the stock ROM and it reacts the same. But even then... That sounds more soft releated than hard. Like I said, this is an off the top of my head guestimate from reading a post so you know how that can go.....

**scrosler** · #**1399** (**permalink**) 03-12-2009, 06:02 PM

Quote:

Originally Posted by gman4471

Scott, One other thing I noticed is that encryption is missing from the recent builds as well. Is there a chance that this be added back in? Many exchange server setups impose security policies that require this option

Well, that all depends. Some of the builds have encryption included thanks to Former Palm OS. The other ones dont. I dont recall specificaly but you can match the builds I have with the ones he has and those would be the ones. he created the XIP intentially to uinclude encryption for use with this kitchen. Most of your other generic XIP's floating around do not have encryption included and therfore wont work.

I decided to hide the encryption control panel as this is a dangerous options for those who dont understand. Obvisoulsy you do so here is what you do to get it back.. assuming you are runnign a build with encryption...

There is a single line in the reg that turns the control panel applet on or off. You can mod that by edting that key in the reg or by rebuild the ROM with key in the flip flopped state, 0=hide 1=show.

The key you need to mod is this one:
[HKEY_LOCAL_MACHINE\ControlPanel\Encryption]
"Hide"=dword:1

Remember this will only turn back on the control panel option. You still need to have the encryption capable SYS files to actually encrypt with it.

Let me know if this doesnt make sense. Power typing to catch up.

**scrosler** · #**1400** (**permalink**) 03-12-2009, 06:04 PM

Quote:

Originally Posted by oldman

I don't think this should be added in. Being cooked into a ROM could have unintended results for an "uninformed" user (who might think it would be cool). Or there could be a "burp" in the cooking process. However, I do think that is should be available as a CAB install for informed users who want it and know how to handle it.

Bob

I was actually going to put a cab file in the encrypted builds but never got around to it for the same reasons you noted.

I think I will do so next kitchen update... maybe... if I remember... which I havent yet... so... you know how that goes... good luck to me....

Nah, just kidding, writitng it down this time.