View Single Post
  #1110 (permalink)  
Old 09-27-2008, 01:19 PM
Whosdaman's Avatar
Whosdaman
VIP Member
Offline
Location: Lake City, Florida
 
Join Date: Dec 2007
Posts: 2,402
Reputation: 4662
Whosdaman should be added to the payroll for their contributionsWhosdaman should be added to the payroll for their contributionsWhosdaman should be added to the payroll for their contributionsWhosdaman should be added to the payroll for their contributionsWhosdaman should be added to the payroll for their contributionsWhosdaman should be added to the payroll for their contributionsWhosdaman should be added to the payroll for their contributionsWhosdaman should be added to the payroll for their contributionsWhosdaman should be added to the payroll for their contributionsWhosdaman should be added to the payroll for their contributionsWhosdaman should be added to the payroll for their contributions
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Send a message via AIM to Whosdaman Send a message via MSN to Whosdaman Send a message via Yahoo to Whosdaman Send a message via Skype™ to Whosdaman
Re: [UPDATED 9/26/08] v1.3 WDM's 2D Diamond ROM

Quote:
Originally Posted by detroit_doug View Post
ive have had a similar issue in every Manila/Touchflo ROM so far also I have found that editing the background graphic to reduce its size and not its quality has eliminated the issue in my phone so far. Not saying its a correct fix but even on V1.3 on initial install it was OK, after reboot and another reboot it occurred over and over so I disabled Touchflo, copied over a smaller file named HH_FW_Background.png and re-enabled TF and the whole interface is faster as well as after reboot after reboot there is no longer the memory issue

If you want WDM - send me the original and I will reduce it and you can test it and verify this and include this in your next ROM to determine if it is the UI graphics and look causing issues, if nothing else less file size will definatly open up more memory regardless

Detroit Doug
You know...I think I did fix it, cause I cannot duplicate that error at all anymore on v1.4 (When I post it, see if you can)
__________________
Reply With Quote