Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,733,899 Members 49,856 Now Online
XDA Developers Android and Mobile Development Forum

{X10}[DEVELOPMENT] - CM9.1 - FreeXperia Project

Tip us?
 
coolsid8
Old
#711  
Senior Member
Thanks Meter 35
Posts: 287
Join Date: Feb 2011
Location: India
Quote:
Originally Posted by Hzu View Post
Really? It's VERY annoying to me. Every time I rotate the phone 90° degrees clockwise, the screen gets misplaced.)

I can't give you a screen shot, as the screen looks normal in the screen shot.
Yeah there is some problem with landscape mode !!

Sent from my Xperia X10 using xda premium
The Following User Says Thank You to coolsid8 For This Useful Post: [ Click to Expand ]
 
Daffy_ed9
Old
#712  
Junior Member
Thanks Meter 0
Posts: 18
Join Date: Feb 2009
guys
im using cm9 121 since some days
everythin works as expected.
but my battery is very very fast empty.
The problem is, even with an ac charger attached iīm not geeting my battery loaded again, the phone always starts automatically when 1% capacity is charged and then turns off again after some minutes

is there any way to load another rom kernel with only 1 % of baatery load?

a factory reset and wiping stats didnīt bring anything
milad407 Old
#713  
Guest
Thanks Meter
Posts: n/a
Quote:
Originally Posted by Daffy_ed9 View Post
guys
im using cm9 121 since some days
everythin works as expected.
but my battery is very very fast empty.
The problem is, even with an ac charger attached iīm not geeting my battery loaded again, the phone always starts automatically when 1% capacity is charged and then turns off again after some minutes

is there any way to load another rom kernel with only 1 % of baatery load?

a factory reset and wiping stats didnīt bring anything
Sounds like your battery is dead

Sent from my GT-I9300 using xda premium
 
Hzu
Old
#714  
Senior Member
Thanks Meter 526
Posts: 1,478
Join Date: Nov 2010
Quote:
Originally Posted by Daffy_ed9 View Post
guys
im using cm9 121 since some days
everythin works as expected.
but my battery is very very fast empty.
The problem is, even with an ac charger attached iīm not geeting my battery loaded again, the phone always starts automatically when 1% capacity is charged and then turns off again after some minutes

is there any way to load another rom kernel with only 1 % of baatery load?

a factory reset and wiping stats didnīt bring anything
Check if your deep sleep really works.
Obsolete Stuffs:
- FXP #125 CM7.2 ROM + #125 Kernel + Google Apps .FTF for Flashtool 0.8+
- Toolset for packaging FXP CM9 kernel .FTF
- Toolset for packaging FXP CM7 kernel .FTF
- Colour bug fix for FXP 121+ CM9.0 (Fixed as of #127.)
- Patch for camera (FXP CM7.2); removed as it was fixed in release #116.
- Patch for sensors (FXP CM7.2); removed as it was fixed in release #115.
 
Hzu
Old
#715  
Senior Member
Thanks Meter 526
Posts: 1,478
Join Date: Nov 2010
Quote:
Originally Posted by Hzu View Post
Make sure that your minimum clock is not below 245mhz. Same thing happened to me.

Also, did anyone notice the strange bug where the screen gets misaligned or misplaced after some time? I noticed that this behaviour is caused by the setting 'debug.composition.type=mdp' in the build.prop. Commenting or removing this line will fix the bug at the cost of worse performance.
By removing this line will also fix the BSOD bug. I've confirmed about this. I hope FXP can look on to these bugs.
Obsolete Stuffs:
- FXP #125 CM7.2 ROM + #125 Kernel + Google Apps .FTF for Flashtool 0.8+
- Toolset for packaging FXP CM9 kernel .FTF
- Toolset for packaging FXP CM7 kernel .FTF
- Colour bug fix for FXP 121+ CM9.0 (Fixed as of #127.)
- Patch for camera (FXP CM7.2); removed as it was fixed in release #116.
- Patch for sensors (FXP CM7.2); removed as it was fixed in release #115.
 
salimdz2010
Old
#716  
Member
Thanks Meter 36
Posts: 87
Join Date: May 2010
Quote:
Originally Posted by Hzu View Post
Also, did anyone notice the strange bug where the screen gets misaligned or misplaced after some time? I noticed that this behaviour is caused by the setting 'debug.composition.type=mdp' in the build.prop. Commenting or removing this line will fix the bug at the cost of worse performance.
I replace it with

debug.composition.type=gpu
The Following User Says Thank You to salimdz2010 For This Useful Post: [ Click to Expand ]
 
Hzu
Old
#717  
Senior Member
Thanks Meter 526
Posts: 1,478
Join Date: Nov 2010
Quote:
Originally Posted by salimdz2010 View Post
I replace it with

debug.composition.type=gpu
I have no idea what the other options for the setting because I don't what it does. Do you have any ideas what it do? Does your current setting fixed all the problems I mentioned?

Thanks!
Obsolete Stuffs:
- FXP #125 CM7.2 ROM + #125 Kernel + Google Apps .FTF for Flashtool 0.8+
- Toolset for packaging FXP CM9 kernel .FTF
- Toolset for packaging FXP CM7 kernel .FTF
- Colour bug fix for FXP 121+ CM9.0 (Fixed as of #127.)
- Patch for camera (FXP CM7.2); removed as it was fixed in release #116.
- Patch for sensors (FXP CM7.2); removed as it was fixed in release #115.
 
salimdz2010
Old
#718  
Member
Thanks Meter 36
Posts: 87
Join Date: May 2010
Quote:
Originally Posted by Hzu View Post
I have no idea what the other options for the setting because I don't what it does. Do you have any ideas what it do? Does your current setting fixed all the problems I mentioned?

Thanks!
Quote:
on "gpu" , benchmark 2d & 3d score much better
I did not notice a problem

here is links

http://forum.xda-developers.com/show....php?t=1563239

http://rootzwiki.com/topic/21263-deb...ndering-speed/

http://rootzwiki.com/topic/18843-rel.../page__st__120

http://smart4u.org/forum/Thread-ICS-...eleration-defy

---------- Post added at 02:35 PM ---------- Previous post was at 02:13 PM ----------

Quote:
debug.composition.type=gpu can't be used with adreno200 gpu (missing 2d hardware). so we need to emulate that through copybit. So debug.composition.type=mdp
http://www.modaco.com/topic/352180-c.../page__st__160

Quote:
debug.composition.type=cpu
or
debug.composition.type=gpu
or
debug.composition.type=mdp
or
debug.composition.type=c2d
The Following User Says Thank You to salimdz2010 For This Useful Post: [ Click to Expand ]
 
Hzu
Old
(Last edited by Hzu; 26th May 2012 at 03:02 PM.)
#719  
Senior Member
Thanks Meter 526
Posts: 1,478
Join Date: Nov 2010
Weird. I'm wondering why I'm having these problems.

I think its because of this one app that I've installed. But maybe not, because the problems persist even when I've removed it. I'm gonna do a total clean install for the next release (again, I've did it for this release, yet...).
Obsolete Stuffs:
- FXP #125 CM7.2 ROM + #125 Kernel + Google Apps .FTF for Flashtool 0.8+
- Toolset for packaging FXP CM9 kernel .FTF
- Toolset for packaging FXP CM7 kernel .FTF
- Colour bug fix for FXP 121+ CM9.0 (Fixed as of #127.)
- Patch for camera (FXP CM7.2); removed as it was fixed in release #116.
- Patch for sensors (FXP CM7.2); removed as it was fixed in release #115.
 
salimdz2010
Old
#720  
Member
Thanks Meter 36
Posts: 87
Join Date: May 2010
Quote:
Originally Posted by Hzu View Post
Weird. I'm wondering why I'm having these problems.
try to change between these four options and see the result

debug.composition.type=cpu or debug.composition.type=gpu or debug.composition.type=mdp or debug.composition.type=c2d

Quote:
using c2d - videos get scaled using nearest neighbor instead of Bicubic, Bilinear or whichever method Android normally uses. This can be fixed by changing this line in the build.prop:

debug.composition.type=c2d > debug.composition.type=gpu

This will fix the pixelation
http://rootzwiki.com/topic/18843-rel.../page__st__110

The Following User Says Thank You to salimdz2010 For This Useful Post: [ Click to Expand ]
Tags
working camera
Thread Tools
Display Modes