Forums | developer.brewmp.com Forums | developer.brewmp.com

Developer

Forums

Has anyone faced serious memory issues with the Kyocera SE47?
We have been going through a series of issues such as
* CONVERTBMP using double the memory as other devices, we even tried lowering the bit depth but did nothing. I saw the same issue in a couple of other threads.
* Memory seems to get fragmented or leaked in a weird manner and we cannot really find a specific place in the code where this happens.
* The good old text flashing issue which someone recommended not to use TRANSPARENT.

If any of you is facing a similar problem or have found a solution please let me know. I would greatly appreciate that.

thanks
Veera

veeramurthy wrote:Has anyone faced serious memory issues with the Kyocera SE47?
...
* Memory seems to get fragmented or leaked in a weird manner and we cannot really find a specific place in the code where this happens.
...
someone recommended not to use TRANSPARENT.
Yes, indeed. We ran into plenty of memory issues developing for the SE47, especially when it came to loading images. Here's what we found:
- The size of the BAR that the phone could handle was at LEAST 50k less than what a phone with a supposedly comparable memory profile could handle. The phone using double the memory for displaying images would explain quite a bit, although we weren't using CONVERTBMP in our app.
- This problem lead us to use PNGs rather than BMPs to keep the size of the BAR down. However, this presented another problem:
- Whenever we tried using PNGs with a set transparent palette index, the app leaked like nobody's business. This became apparent when exiting and re-entering the app caused the phone to crash with a memory error and reboot. In the known issues for the SE47, they mention problems with interlaced PNGs. It makes me wonder if these two problems are related.
- Our solution was to use non-transparent PNGs whenever possible to save on size and use BMPs only when we absolutely needed transparency.
I Hope this helps.
Good luck!
-Matt

veeramurthy wrote:Has anyone faced serious memory issues with the Kyocera SE47?
...
* Memory seems to get fragmented or leaked in a weird manner and we cannot really find a specific place in the code where this happens.
...
someone recommended not to use TRANSPARENT.
Yes, indeed. We ran into plenty of memory issues developing for the SE47, especially when it came to loading images. Here's what we found:
- The size of the BAR that the phone could handle was at LEAST 50k less than what a phone with a supposedly comparable memory profile could handle. The phone using double the memory for displaying images would explain quite a bit, although we weren't using CONVERTBMP in our app.
- This problem lead us to use PNGs rather than BMPs to keep the size of the BAR down. However, this presented another problem:
- Whenever we tried using PNGs with a set transparent palette index, the app leaked like nobody's business. This became apparent when exiting and re-entering the app caused the phone to crash with a memory error and reboot. In the known issues for the SE47, they mention problems with interlaced PNGs. It makes me wonder if these two problems are related.
- Our solution was to use non-transparent PNGs whenever possible to save on size and use BMPs only when we absolutely needed transparency.
I Hope this helps.
Good luck!
-Matt

Yes we too have seen this behavior. You are correct that CONVERTBMP takes twice the memory that it should. It has been reported to BREW Support and their answer was to add it to the known issues about this device.

Yes we too have seen this behavior. You are correct that CONVERTBMP takes twice the memory that it should. It has been reported to BREW Support and their answer was to add it to the known issues about this device.

It shouldn't be added to the known issues, it should be addressed and fixed for cryin' out loud! It makes it next to impossible to create any halfway decent apps for that phone without hacking the system.

It shouldn't be added to the known issues, it should be addressed and fixed for cryin' out loud! It makes it next to impossible to create any halfway decent apps for that phone without hacking the system.

I am sorry but you are preaching to the choir! You sentiments are mind exactly but it is hard to get everyone ot turn their phones at this time (cat out of the bag, split milk, worms out of the can, etc.).
Does anyone know if the SE44 has the same problems? What about the bad text drawing issue too?

I am sorry but you are preaching to the choir! You sentiments are mind exactly but it is hard to get everyone ot turn their phones at this time (cat out of the bag, split milk, worms out of the can, etc.).
Does anyone know if the SE44 has the same problems? What about the bad text drawing issue too?

They could all be hot-flashed over the air without the user even knowing it. The infrastructure is there. Just no one's using it.

They could all be hot-flashed over the air without the user even knowing it. The infrastructure is there. Just no one's using it.

Unless a carrier starts throwing their weight around, OEMs (some more than others) tend not to fix issues in commercial phones. The risk they face is that the fix might cause the PID to roll, which could cause them additional headaches.

Unless a carrier starts throwing their weight around, OEMs (some more than others) tend not to fix issues in commercial phones. The risk they face is that the fix might cause the PID to roll, which could cause them additional headaches.

Isn't the trust they put in their own work refreshing. :p
Seriously, though, of course I understand their issues but some issues should just be resolved rather than swept under the rug and if they're so afraid of post-ship changes, maybe they should start QAing their firmwares a bit better.

Isn't the trust they put in their own work refreshing. :p
Seriously, though, of course I understand their issues but some issues should just be resolved rather than swept under the rug and if they're so afraid of post-ship changes, maybe they should start QAing their firmwares a bit better.