Develop Bugs

[Q]How to rotate screen?

Hi gents.
Today,I want to ask someone,how can I programm,that my software forces the screen to be rotated into landscape or back on the go(for example after starting). I try to programm something with Embedded Visual C++ SP4. Actually I don't see any problem with this,but I cannot find any source.so I will be very grateful for that.
Anyone can help me with this?
Thanks in advance.

Take a look at
DEVMODE DevMode;
memset (&DevMode, 0, sizeof(DevMode));
DevMode.dmSize = sizeof(DevMode);
DevMode.dmFields = DM_DISPLAYORIENTATION;
ChangeDisplaySettingsEx(NULL, &DevMode, NULL, CDS_TEST, NULL);
DevMode.dmDisplayOrientation = DMDO_270;
// this should force a size message
ChangeDisplaySettingsEx(NULL, &DevMode, NULL, CDS_RESET, NULL);
Jim

Thanks,that works perfectly.

OpenGL ES mess up my device

Hello
I code some games with opengl es for my winmo device. BUT: My apps won't startup after running several times (about 7 or 8 times) and I don't why.
And sometimes they just mess up my device - so I need to do a softreset by removing the accu of the phone...
Does anyone else have the same issue and already solved it?????
Thanks
Chabun

Hey guys
I really need help...
It's very strange, glGetError reports everything's running OK..
EGL does report any error, too.
And it must be OpenGLES or EGL cause on the device emulator (with vincent3D) everything's running...
Does anyone have a tip where I have to search for the fault?
Thanks

People having this problem 'solved' it by removing the call to eglTerminate.
What device/rom are you using?

Yeah, that's an bug of the egl on SnapDragon platforms (I'm using a HTC HD2 with the original Rom).
Now my app starts every time, but it crashes (and freezes the whole device) suddenly without reasons...

I'm not sure if this is a bug in the drivers as my apps work fine on HD2. Do you have this bug with my OpenGLES test apps (1.x, 2.0)?

No, you're apps run perfectly... (1.x and 2.0)
Is there sany source code avaible?
So I could compare my engine with yours to find out what's my problem.
But that my app runs perfectly (but slow ;-)) on the emulator is still a mystery...

The 1.x thread has a VS2005 project with an early version of the test. These sources are build for 1.x devices.
Try the following (maybe first in your project):
For OpengGL ES 1.x on 2.0 devices:
in egl.cs replace "libgles_cm.dll" by "libEGL.dll"
(if that's not enough try also to replace "libgles_cm.dll" by "libGLESv1.dll" in gl.cs)
In case your project is using OpenGL ES 2.0:
link/load libEGL.dll for egl and libGLESv2.dll for gl
After these changes you can't run it on the emulator anymore. But you can connect to your device. Just be sure to save everything before starting the debugger!

Hey
If I change the dll in the wrapper classes, I get a black screen with some render artefacts or other strange things....
I've downloaded your source but I can't see any difference between my engine and yours.
I'll send you a PM with my source code... (I don't want to publish my game now)
Please test it on your device, thank

Hey
sorry, I can't attach files zo a PM?!
Could you give me a mail-address where I'm able to send it to you?
I really don't want to publish it 'cause it's still not stable and finished...
chabun

Thanks..
Now everything is working...
And I will post my game as soon as I finish it, Thanks to heliosdev!!!
Chabun

A never ending fight
I thought all my issues were solved by changing the dlls...
But I was wrong, my app still freezes my device...
My game is based on a square field of tiles and it dynamically draws the field in different sizes - meaning that exactly the same code is executing. Depending on the size of the field, the draw method of the tiles is executed more times...
If it freezes my phone or not is depending on the field size, but it does not mean that more tiles (bigger field size) cause the freezing - the biggest field size works and the smallest not...
So I think I do not draw the tiles properly, cause that's the only thing that changes beetwen the field sizes.
Here is my code for drawing an image:
Code:
// Enable Alphablending
OpenGLES.Enable(OpenGLES.GL_BLEND);
OpenGLES.BlendFunc(OpenGLES.GL_SRC_ALPHA, OpenGLES.GL_ONE_MINUS_SRC_ALPHA);
// Reset the world (MODELVIEW);
OpenGLES.MatrixMode(OpenGLES.GL_MODELVIEW);
OpenGLES.LoadIdentity();
OpenGLES.Rotatef(90f, 0f, 0f, 1f);
OpenGLES.Translatef(0f, -480f, 0f);
// Set the Position
OpenGLES.Translatef(bounds.X, bounds.Y, ZIndex);
//Enable texturing and set current texture as the active one
OpenGLES.Enable(OpenGLES.GL_TEXTURE_2D);
OpenGLES.BindTexture(OpenGLES.GL_TEXTURE_2D, texture.Name);
//Aply the Color value to colorizing the active texture
OpenGLES.Color4f(Color.Rf, Color.Gf, Color.Bf, Color.Af);
//Enable the vertices array
OpenGLES.EnableClientState(OpenGLES.GL_VERTEX_ARRAY);
OpenGLES.VertexPointer(3, OpenGLES.GL_SHORT, 0, vertices);
//Enable the texCoords
OpenGLES.EnableClientState(OpenGLES.GL_TEXTURE_COORD_ARRAY);
OpenGLES.TexCoordPointer(2, OpenGLES.GL_FLOAT, 0, texCords);
// Draw the sprite.
OpenGLES.DrawArrays(OpenGLES.GL_TRIANGLES, 0, 6);
// Disable the vertices and the texCoords
OpenGLES.DisableClientState(OpenGLES.GL_VERTEX_ARRAY);
OpenGLES.DisableClientState(OpenGLES.GL_TEXTURE_COORD_ARRAY);
// Diesable texturing
OpenGLES.Disable(OpenGLES.GL_TEXTURE_2D);
OpenGLES.Disable(OpenGLES.GL_BLEND);
The vertex data and texcoords are the following ones:
Code:
static short[] vertices = { 0, 0, 0, 0, 1, 0, 1, 0, 0 ,
1, 1, 0, 0, 1, 0, 1, 0, 0 };
float[] texCoords = { 0, 0, 0, 1, 1, 0, 1, 1, 0, 1, 1, 0}
This code is executed once per frame and per image I draw... Do I simply miss calling an OpenGl-Method or is there any other fault?
Thanks for your help
Hope the never ending fight against opengl is goning to en...

Does changing short to float of the vertices and VertexPointer crash too?

The Cause Of Wake Lag [DMESG|LOGCAT|DUMPs]

Had a bit too much coffee one evening and ended up spending the night messing around trying to figure out what's really causing the annoying wake-lag after phone goes in deep sleep. Time to report back and hopefully shed some light on this bug, or how Samsung might call it, a "feature"
So, to start with I set up a Tasker profile to dump dmesg & logcat on Display On event. Then, I went through those logs and fished around and calculated how long it takes phone to:
wake up CPU from suspend
turn on the display after CPU wakes up
and, to make things bit more scientific I did 3 rounds, all with phone off usb:
external sdcard inserted
external sdcard removed
external sdcard inserted & manually wake_lock'ing the phone
Event 1: CPU wakeup
kmsg dump with phone off usb, external sdcard inserted
<6>[ 0.000000] WAKEUP_STAT: 0x80000001
<6>[ 0.000000] WAKUP_INT0_PEND: 0x2
<6>[ 0.000000] WAKUP_INT1_PEND: 0x0
<6>[ 0.000000] WAKUP_INT2_PEND: 0x80
<6>[ 0.000000] WAKUP_INT3_PEND: 0x0
<7>[ 0.000000] s3c_pm_enter: post sleep, preparing to return
<7>[ 0.000000] S3C PM Resume (post-restore)
<7>[ 0.000000] Wakeup from sleep, 0x80000001
<6>[ 0.000000] L310 cache controller enabled
<6>[ 0.000000] l2x0: 16 ways, CACHE_ID 0x4100c4c5, AUX_CTRL 0x7e470001, Cache Size: 1048576 B
<6>[24041.990920] wakeup wake lock: event1-3200
<6>[24041.991220] PM: early resume of devices complete after 0.257 msecs
<3>[24041.991354] [MHL]mhl_int_irq_handler() is called
<6>[24041.991559] s3c-i2c s3c2410-i2c.0: slave address 0x10
<6>[24041.991574] s3c-i2c s3c2410-i2c.0: bus frequency set to 390 KHz
<6>[24041.991593] s3c-i2c s3c2410-i2c.1: slave address 0x10
<6>[24041.991605] s3c-i2c s3c2410-i2c.1: bus frequency set to 390 KHz
<6>[24041.991624] s3c-i2c s3c2410-i2c.2: slave address 0x10
<6>[24041.991636] s3c-i2c s3c2410-i2c.2: bus frequency set to 97 KHz
<6>[24041.991655] s3c-i2c s3c2410-i2c.3: slave address 0x10
<6>[24041.991667] s3c-i2c s3c2410-i2c.3: bus frequency set to 97 KHz
<6>[24041.991685] s3c-i2c s3c2410-i2c.4: slave address 0x10
<6>[24041.991697] s3c-i2c s3c2410-i2c.4: bus frequency set to 97 KHz
<6>[24041.991716] s3c-i2c s3c2410-i2c.5: slave address 0x10
<6>[24041.991728] s3c-i2c s3c2410-i2c.5: bus frequency set to 390 KHz
<6>[24041.991747] s3c-i2c s3c2410-i2c.6: slave address 0x3a
<6>[24041.991759] s3c-i2c s3c2410-i2c.6: bus frequency set to 97 KHz
<6>[24041.991777] s3c-i2c s3c2410-i2c.7: slave address 0x10
<6>[24041.991789] s3c-i2c s3c2410-i2c.7: bus frequency set to 97 KHz
<6>[24041.991826] c1_enable_regulator_for_usb_mipi: enable LDOs
<6>[24041.995640] sdhci_resume_host : MMC Card ON samsung-hsmmc
<7>[24041.995723] usb udc resume
<6>[24041.995745] s3c-rtc s3c64xx-rtc: rtc disabled, re-enabling
<6>[24041.995768] wake disabled for irq 347
<6>[24041.995784] sec_jack_resume: disable_irq_wake(0)
<6>[24041.995811] s5pv310_setup_mshci_set_power : internal MMC Card ON samsung-mshc.
<6>[24041.996245] mmc0: FIFO WMARK FOR RX 0x11 WX 0x1. ###########
<6>[24042.099034] max17042 9-0036: max17042_get_soc : soc(6290)
<6>[24042.099046] max17042_need_soc_recal: HW(0xc)
<6>[24042.099058] max17042 9-0036: max17042_get_soc : use raw (98), soc (100)
<6>[24042.100197] USB3803 resumed to mode standby
<6>[24042.100395] wake disabled for irq 331
<3>[24042.103414] [IDPRAM] <dpram_power_up:3440> dpram_wakeup_init() ==> QSC_INT = LOW
<3>[24042.117319] [IDPRAM] <dpram_powerup_start:3412> Received MBX_CMD_CP_WAKEUP_START!!!
<6>[24042.117357] wake disabled for irq 332
<3>[24042.117370] [IDPRAM] <dpram_powerup_start:3412> Received MBX_CMD_CP_WAKEUP_START!!!
<3>[24042.150142] [cyasdevice.c] cyasdevice_leave_standby end mode count=8
<3>[24042.163382] cyasblkdev_stop_sdcard : cy_as_storage_stop is called - found
<3>[24042.687474] cyasblkdev_start_sdcard : cy_as_storage_start is called
<3>[24042.687687] cyasblkdev_start_sdcard : cy_as_storage_query_media is called - media count = 1
<3>[24042.687968] cyasblkdev_start_sdcard : cy_as_storage_query_device is called - found
<3>[24042.687997] [cyasdevice.c] cy_wq_function: leave standby
<3>[24042.688008] ++++++++++++ [cyasdevice.c] cy_wq_function: SD card is inserted.
<3>[24042.695242] cyasblkdev_check_sdcard : serial num = 0x0 0x0 0x22 0xac
<6>[24042.705211] PM: resume of devices complete after 713.807 msecs
<4>[24042.706250] Restarting tasks ... deb***: [battery] bat temper : 840, rescale : 651
<6>[24042.710955] sec-battery sec-battery: [test] temp_radc_value : -1065637448
<6>[24042.710974] sec_bat_get_lpcharging_state: LP charging:0
<6>[24042.710986] sec-battery sec-battery: [NA_SPR] Changed Put off Current
<6>[24042.711844] sec-battery sec-battery: sec_bat_check_temper: temp=320, adc=840
<6>[24042.715111] sec-battery sec-battery: sec_bat_charging_time_management: charging_start_time has never been used since initializing
<6>[24042.715138] max8922-charger max8922-charger: max8922_is_charging: charging state = 0x3
<6>[24042.715159] sec-battery sec-battery: soc(100), vfocv(4161), vcell(4127), temp(32), charging(2), health(1)
<6>[24042.732025] request_suspend_state: wakeup (3->0) at 24042706933965 (2011-10-18 13:40:03.113578166 UTC)
<4>[24042.737188] done.
<4>[24042.737203] Mali: OSPMM: mali_pwr_suspend_notifier : PM_POST_PREPARE
<7>[24042.742938] PM_POST_SUSPEND for CPUFREQ: 0
<7>[24042.743473] calc_bus_utilization: 0 value is not permitted
<7>[24042.743485] calc_bus_utilization: 0 value is not permitted
<7>[24042.743494] BUSLOAD is larger than 50(100)
<6>[24042.743509] s5pv310_pm_hotplug_notifier_event: restoring pm_hotplug lock 0
<6>[24042.743528] suspend: exit suspend, ret = 0 (2011-10-18 13:40:03.125093667 UTC)
Time taken: 0.752608 seconds
Click to expand...
Click to collapse
kmsg dump with phone off usb, external sdcard removed
<6>[ 0.000000] WAKEUP_STAT: 0x80000001
<6>[ 0.000000] WAKUP_INT0_PEND: 0x2
<6>[ 0.000000] WAKUP_INT1_PEND: 0x0
<6>[ 0.000000] WAKUP_INT2_PEND: 0x80
<6>[ 0.000000] WAKUP_INT3_PEND: 0x0
<7>[ 0.000000] s3c_pm_enter: post sleep, preparing to return
<7>[ 0.000000] S3C PM Resume (post-restore)
<7>[ 0.000000] Wakeup from sleep, 0x80000001
<6>[ 0.000000] L310 cache controller enabled
<6>[ 0.000000] l2x0: 16 ways, CACHE_ID 0x4100c4c5, AUX_CTRL 0x7e470001, Cache Size: 1048576 B
<6>[24498.899997] wakeup wake lock: event1-3200
<4>[24498.900032] Enabling non-boot CPUs ...
<4>[24498.900047] >made stopper
<4>[24498.905593] CPU1: Booted secondary processor
<7>[24498.906424] ++ s5pv310_cpufreq_cpu_init
<4>[24498.906452] CPU1 is up
<6>[24498.906729] PM: early resume of devices complete after 0.263 msecs
<3>[24498.906857] [MHL]mhl_int_irq_handler() is called
<6>[24498.907047] s3c-i2c s3c2410-i2c.0: slave address 0x10
<6>[24498.907061] s3c-i2c s3c2410-i2c.0: bus frequency set to 390 KHz
<6>[24498.907081] s3c-i2c s3c2410-i2c.1: slave address 0x10
<6>[24498.907093] s3c-i2c s3c2410-i2c.1: bus frequency set to 390 KHz
<6>[24498.907112] s3c-i2c s3c2410-i2c.2: slave address 0x10
<6>[24498.907124] s3c-i2c s3c2410-i2c.2: bus frequency set to 97 KHz
<6>[24498.907143] s3c-i2c s3c2410-i2c.3: slave address 0x10
<6>[24498.907155] s3c-i2c s3c2410-i2c.3: bus frequency set to 97 KHz
<6>[24498.907173] s3c-i2c s3c2410-i2c.4: slave address 0x10
<6>[24498.907185] s3c-i2c s3c2410-i2c.4: bus frequency set to 97 KHz
<6>[24498.907203] s3c-i2c s3c2410-i2c.5: slave address 0x10
<6>[24498.907215] s3c-i2c s3c2410-i2c.5: bus frequency set to 390 KHz
<6>[24498.907234] s3c-i2c s3c2410-i2c.6: slave address 0x3a
<6>[24498.907246] s3c-i2c s3c2410-i2c.6: bus frequency set to 97 KHz
<6>[24498.907265] s3c-i2c s3c2410-i2c.7: slave address 0x10
<6>[24498.907277] s3c-i2c s3c2410-i2c.7: bus frequency set to 97 KHz
<6>[24498.907313] c1_enable_regulator_for_usb_mipi: enable LDOs
<6>[24498.911022] sdhci_resume_host : MMC Card ON samsung-hsmmc
<7>[24498.911102] usb udc resume
<6>[24498.911124] s3c-rtc s3c64xx-rtc: rtc disabled, re-enabling
<6>[24498.911147] wake disabled for irq 347
<6>[24498.911226] sec_jack_resume: disable_irq_wake(0)
<6>[24498.911254] s5pv310_setup_mshci_set_power : internal MMC Card ON samsung-mshc.
<6>[24498.911690] mmc0: FIFO WMARK FOR RX 0x11 WX 0x1. ###########
<6>[24499.011495] max17042 9-0036: max17042_get_soc : soc(62e0)
<6>[24499.011507] max17042_need_soc_recal: HW(0xc)
<6>[24499.011518] max17042 9-0036: max17042_get_soc : use raw (98), soc (101)
<6>[24499.012633] USB3803 resumed to mode standby
<6>[24499.012872] wake disabled for irq 331
<3>[24499.015807] [IDPRAM] <dpram_power_up:3440> dpram_wakeup_init() ==> QSC_INT = LOW
<3>[24499.029703] [IDPRAM] <dpram_powerup_start:3412> Received MBX_CMD_CP_WAKEUP_START!!!
<6>[24499.029745] wake disabled for irq 332
<3>[24499.029758] [IDPRAM] <dpram_powerup_start:3412> Received MBX_CMD_CP_WAKEUP_START!!!
<6>[24499.052786] PM: resume of devices complete after 145.883 msecs
<4>[24499.053881] Restarting tasks ... deb***: [battery] bat temper : 861, rescale : 646
<6>[24499.062238] sec-battery sec-battery: [test] temp_radc_value : -1065637448
<6>[24499.062265] sec_bat_get_lpcharging_state: LP charging:0
<6>[24499.062276] sec-battery sec-battery: [NA_SPR] Changed Put off Current
<6>[24499.063200] sec-battery sec-battery: sec_bat_check_temper: temp=310, adc=861
<6>[24499.063395] sec-battery sec-battery: sec_bat_charging_time_management: charging_start_time has never been used since initializing
<6>[24499.063425] max8922-charger max8922-charger: max8922_is_charging: charging state = 0x3
<6>[24499.063446] sec-battery sec-battery: soc(100), vfocv(4163), vcell(4146), temp(31), charging(2), health(1)
<6>[24499.065185] request_suspend_state: wakeup (3->0) at 24499040026596 (2011-10-18 13:49:00.534295458 UTC)
<4>[24499.066690] done.
<4>[24499.066704] Mali: OSPMM: mali_pwr_suspend_notifier : PM_POST_PREPARE
<7>[24499.068161] PM_POST_SUSPEND for CPUFREQ: 0
<7>[24499.070641] calc_bus_utilization: 0 value is not permitted
<7>[24499.070652] calc_bus_utilization: 0 value is not permitted
<7>[24499.070662] BUSLOAD is larger than 50(100)
<6>[24499.070676] s5pv310_pm_hotplug_notifier_event: restoring pm_hotplug lock 0
<6>[24499.070695] suspend: exit suspend, ret = 0 (2011-10-18 13:49:00.539817042 UTC)
Time taken: 0.170698 seconds
Click to expand...
Click to collapse
kmsg dump with phone off usb, external sdcard inserted, phone wake_locked with [echo foo > /sys/power/wake_lock]
<4>[26418.987991] cpu1 turning on!
<4>[26418.988022] >made stopper
<4>[26419.001448] CPU1: Booted secondary processor
<7>[26419.002737] ++ s5pv310_cpufreq_cpu_init
<4>[26419.002787] cpu1 on end!
<6>[26419.036816] request_suspend_state: wakeup (3->0) at 26419011419814 (2011-10-18 14:21:00.505687301 UTC)
Time taken: 0.048825 seconds
Click to expand...
Click to collapse
Event 2: Display wakeup
** technically time from CPU wakeup to the event just before first signs of Tasker dumping the logs.
logcat -b main dump with phone off usb, external sdcard inserted
10-18 06:40:03.105 3200 3239 E AlarmManagerService: android_server_AlarmManagerService_set to type=1, 1318945260.000000000
10-18 06:40:03.107 3200 3243 D InputReader: Input event: value=1
10-18 06:40:03.107 3200 3243 I ScreenCaptureAction: isHomeKeyPressed(), return value = false
10-18 06:40:03.107 3200 3243 D KeyguardViewMediator: onWakeKeyWhenKeyguardShowing(26)
10-18 06:40:03.107 3200 3243 D KeyguardViewMediator: wakeWhenReadyLocked(26)
10-18 06:40:03.110 3200 3241 D KeyguardViewMediator: handleWakeWhenReady(26)
10-18 06:40:03.110 3200 3241 D KeyguardViewMediator: pokeWakelock(10000)
10-18 06:40:03.110 3200 3241 E power : *** set_screen_state 1
10-18 06:40:03.110 3200 3241 D SensorManager: registerListener :: handle = 3 name= CM3663 Light Sensor delay= 200000 Listener= [email protected]
10-18 06:40:03.115 3200 3243 D InputReader: Input event: value=0
10-18 06:40:03.115 3200 3243 I ScreenCaptureAction: isHomeKeyPressed(), return value = false
10-18 06:40:03.125 <======== LAST LINE OF KMSG DUMP
10-18 06:40:03.262 4149 4151 D dalvikvm: GC_CONCURRENT freed 509K, 50% free 3079K/6087K, external 224K/512K, paused 1ms+12ms
10-18 06:40:03.345 3200 3230 E BatteryService: TMU status = 0
10-18 06:40:03.357 3333 3333 D PhoneApp: Intent.ACTION_BATTERY_CHANGED : 0
10-18 06:40:03.357 3333 3333 D PhoneUtils: updateRAFT current state : 0
10-18 06:40:03.357 3333 3333 D PhoneUtils: updateRAFT current and requested states are same, so do nothing
10-18 06:40:03.460 3200 3237 E lights : write_int: path /sys/class/backlight/pwm-backlight/brightness, value 20
10-18 06:40:03.472 3200 3238 D KeyguardViewMediator: onScreenTurnedOn, seq = 113
10-18 06:40:03.472 3200 3238 D KeyguardViewMediator: notifyScreenOnLocked
10-18 06:40:03.472 3200 3238 I OrientationDebug: [pwm] in updateOrientationListenerLp()
10-18 06:40:03.472 3200 3238 V OrientationDebug: in updateOrientationListenerLp(), Screen status=true, current orientation=1, SensorEnabled=false
10-18 06:40:03.472 3200 3238 I OrientationDebug: [pwm] needSensorRunningLp(), return false #3
10-18 06:40:03.480 3200 3241 D KeyguardViewMediator: handleNotifyScreenOn
10-18 06:40:03.480 3200 3241 D LockPatternKeyguardView: onScreenTurnedOn()
10-18 06:40:03.540 4149 4151 D dalvikvm: GC_CONCURRENT freed 453K, 50% free 3098K/6087K, external 198K/512K, paused 4ms+20ms
10-18 06:40:03.580 29172 29172 D battery_widget_monitor: bmw_watcher got intent: android.intent.action.BATTERY_CHANGED
10-18 06:40:03.777 3332 3332 I Launcher: onResume(). mIsNewIntent : false screenOff: true
10-18 06:40:03.802 3200 3241 D LockscreenWallpaperUpdater: onResume()
10-18 06:40:03.802 3200 3241 D LockscreenWallpaperUpdater: get drawable (public)
10-18 06:40:03.802 3200 3241 D LockscreenWallpaperUpdater: get drawable (keygurardupdatemonitor private get)
10-18 06:40:03.802 3200 3241 D LockscreenWallpaperUpdater: drawable is null(keygurardupdatemonitor private get)
10-18 06:40:03.802 3200 3241 D LockscreenWallpaperUpdater: set drawable
10-18 06:40:03.802 3200 3241 D LockscreenWallpaperUpdater: wallpaper file not exist
10-18 06:40:03.802 3200 3241 D InfoWidget: onResume()
10-18 06:40:03.880 3332 3332 D Launcher: It's image wallpaper. suggestDesiredDimensions(-1,-1)
10-18 06:40:03.957 3200 3218 I OrientationDebug: [WindowOrientationListener] in enable(), now call SensorManager.registerListener()
10-18 06:40:03.957 3200 3218 D SensorManager: registerListener :: handle = 0 name= K3DH Acceleration Sensor delay= 60000 Listener= [email protected]097e0b8
10-18 06:40:03.975 3200 3218 D WallpaperService: ACTION_SCREEN_ON
10-18 06:40:03.977 3200 3218 D WallpaperService: mVisible:true
10-18 06:40:03.977 3200 3218 D WallpaperService: mScreenOn:true
10-18 06:40:03.977 3200 3218 D WallpaperService: mReportedVisible:false
10-18 06:40:03.990 3200 3207 D SurfaceFlinger: Screen about to return, flinger = 0x8ced8
10-18 06:40:04.125 3333 3333 D PhoneUtils: updateRAFT current state : 0
10-18 06:40:04.125 3333 3333 D PhoneUtils: updateRAFT current state : 0 next state : 3
10-18 06:40:04.200 3200 3218 I WindowOrientationListener: orientation = 340.22717 Tilt = 54.167904 -- -2 , 5 , 7
--------------------------------------------------------------------------------
10-18 06:40:04.275 4029 25459 W Tasker : 06.40.04#Shell: warning: run: dmesg -c: java.lang.InterruptedException
Time taken: 1.075 seconds
Click to expand...
Click to collapse
logcat -b main dump with phone off usb, external sdcard removed
10-18 06:49:00.522 3200 3239 E AlarmManagerService: android_server_AlarmManagerService_set to type=1, 1318945800.000000000
10-18 06:49:00.527 3200 3243 D InputReader: Input event: value=1
10-18 06:49:00.527 3200 3243 I ScreenCaptureAction: isHomeKeyPressed(), return value = false
10-18 06:49:00.527 3200 3243 D KeyguardViewMediator: onWakeKeyWhenKeyguardShowing(26)
10-18 06:49:00.527 3200 3243 D KeyguardViewMediator: wakeWhenReadyLocked(26)
10-18 06:49:00.530 3200 3241 D KeyguardViewMediator: handleWakeWhenReady(26)
10-18 06:49:00.530 3200 3241 D KeyguardViewMediator: pokeWakelock(10000)
10-18 06:49:00.530 3200 3241 E power : *** set_screen_state 1
10-18 06:49:00.532 3200 3241 D SensorManager: registerListener :: handle = 3 name= CM3663 Light Sensor delay= 200000 Listener= [email protected]
10-18 06:49:00.532 3200 3243 D InputReader: Input event: value=0
10-18 06:49:00.532 3200 3243 I ScreenCaptureAction: isHomeKeyPressed(), return value = false
10-18 06:49:00.540 <======== LAST LINE OF KMSG DUMP
10-18 06:49:00.612 3200 3237 E lights : write_int: path /sys/class/backlight/pwm-backlight/brightness, value 20
10-18 06:49:00.620 3200 3238 D KeyguardViewMediator: onScreenTurnedOn, seq = 116
10-18 06:49:00.620 3200 3238 D KeyguardViewMediator: notifyScreenOnLocked
10-18 06:49:00.620 3200 3238 I OrientationDebug: [pwm] in updateOrientationListenerLp()
10-18 06:49:00.620 3200 3238 V OrientationDebug: in updateOrientationListenerLp(), Screen status=true, current orientation=1, SensorEnabled=false
10-18 06:49:00.620 3200 3238 I OrientationDebug: [pwm] needSensorRunningLp(), return false #3
10-18 06:49:00.622 3200 3241 D KeyguardViewMediator: handleNotifyScreenOn
10-18 06:49:00.622 3200 3241 D LockPatternKeyguardView: onScreenTurnedOn()
10-18 06:49:00.627 3332 3332 I Launcher: onResume(). mIsNewIntent : false screenOff: true
10-18 06:49:00.632 3200 3241 D LockscreenWallpaperUpdater: onResume()
10-18 06:49:00.632 3200 3241 D LockscreenWallpaperUpdater: get drawable (public)
10-18 06:49:00.632 3200 3241 D LockscreenWallpaperUpdater: get drawable (keygurardupdatemonitor private get)
10-18 06:49:00.632 3200 3241 D LockscreenWallpaperUpdater: drawable is null(keygurardupdatemonitor private get)
10-18 06:49:00.632 3200 3241 D LockscreenWallpaperUpdater: set drawable
10-18 06:49:00.632 3200 3241 D LockscreenWallpaperUpdater: wallpaper file not exist
10-18 06:49:00.632 3200 3241 D InfoWidget: onResume()
10-18 06:49:00.647 3332 3332 D Launcher: It's image wallpaper. suggestDesiredDimensions(-1,-1)
10-18 06:49:00.680 4149 4151 D dalvikvm: GC_CONCURRENT freed 513K, 50% free 3079K/6087K, external 224K/512K, paused 2ms+39ms
10-18 06:49:00.790 3200 3230 E BatteryService: TMU status = 0
10-18 06:49:00.870 12197 12197 E com.samsung.app: [MSC]>>> WeatherWidgetProvider.java:316 [0:0] onReceive()@@@ sec.android.intent.action.HOME_RESUME
10-18 06:49:00.872 12197 12197 E com.samsung.app: [MSC]>>> WidgetIdManager.java:53 [0:0] AccuWeatherClockWidgetID_Length
10-18 06:49:00.872 12197 12197 E com.samsung.app: [MSC]>>> WidgetIdManager.java:54 [0:0] getPrefIDs() : length = 0
10-18 06:49:00.907 25729 25729 I PhotoAppWidgetProvider: onReceive
10-18 06:49:00.907 25729 25729 I PhotoAppWidgetProvider: RestartSlideShow
10-18 06:49:00.912 25729 25729 D PhotoDatabaseHelper: getWidgetIdList query count : 0
10-18 06:49:00.912 25729 25729 D PhotoAppWidgetProvider: onReceive End
10-18 06:49:00.920 7244 7244 D DigitalClock: DigitalClockAppWidget.onReceive : ACTION_HOME_RESUME is called!!
10-18 06:49:01.012 12216 26850 D Buddies--------------------------->: Service:OnReceive ACTION_HOME_RESUME called
10-18 06:49:01.045 3200 3218 I OrientationDebug: [WindowOrientationListener] in enable(), now call SensorManager.registerListener()
10-18 06:49:01.045 3200 3218 D SensorManager: registerListener :: handle = 0 name= K3DH Acceleration Sensor delay= 60000 Listener= [email protected]097e0b8
10-18 06:49:01.087 3200 3218 D WallpaperService: ACTION_SCREEN_ON
10-18 06:49:01.087 3200 3218 D WallpaperService: mVisible:true
10-18 06:49:01.087 3200 3218 D WallpaperService: mScreenOn:true
10-18 06:49:01.087 3200 3218 D WallpaperService: mReportedVisible:false
10-18 06:49:01.102 3333 3333 D PhoneUtils: updateRAFT current state : 0
10-18 06:49:01.102 3333 3333 D PhoneUtils: updateRAFT current state : 0 next state : 3
10-18 06:49:01.182 3200 3207 D SurfaceFlinger: Screen about to return, flinger = 0x8ced8
10-18 06:49:01.190 3332 3332 D dalvikvm: GC_EXTERNAL_ALLOC freed 242K, 50% free 4564K/9095K, external 13612K/13655K, paused 96ms
10-18 06:49:01.195 4149 4151 D dalvikvm: GC_CONCURRENT freed 454K, 50% free 3101K/6087K, external 198K/512K, paused 4ms+5ms
10-18 06:49:01.220 29172 29172 D battery_widget_monitor: bmw_watcher got intent: android.intent.action.SCREEN_ON
10-18 06:49:01.220 29172 29172 V battery_widget_monitor: Refreshing data on SCREEN ON
10-18 06:49:01.272 26863 26863 E su : sudb - Opening database
10-18 06:49:01.275 26863 26863 E su : sudb - Database opened
10-18 06:49:01.280 26863 26863 E su : sudb - Database closed
--------------------------------------------------------------------------------
10-18 06:49:01.285 26863 26863 D su : 10109 net.dinglisch.android.taskerm executing 0 /system/bin/sh using shell /system/bin/sh : sh
Time taken: 0.740 seconds
Click to expand...
Click to collapse
logcat -b main dump with phone off usb, external sdcard inserted, phone wake_locked with [echo foo > /sys/power/wake_lock]
10-18 07:21:00.502 3200 3243 D InputReader: Input event: value=1
10-18 07:21:00.502 3200 3243 I ScreenCaptureAction: isHomeKeyPressed(), return value = false
10-18 07:21:00.502 3200 3243 D KeyguardViewMediator: onWakeKeyWhenKeyguardShowing(26)
10-18 07:21:00.502 3200 3243 D KeyguardViewMediator: wakeWhenReadyLocked(26)
10-18 07:21:00.502 3200 3241 D KeyguardViewMediator: handleWakeWhenReady(26)
10-18 07:21:00.502 3200 3241 D KeyguardViewMediator: pokeWakelock(10000)
10-18 07:21:00.502 3200 3241 E power : *** set_screen_state 1
10-18 07:21:00.502 3200 3241 D SensorManager: registerListener :: handle = 3 name= CM3663 Light Sensor delay= 200000 Listener= [email protected]
10-18 07:21:00.506 <======== LAST LINE OF KMSG DUMP
10-18 07:21:00.597 3200 3243 D InputReader: Input event: value=0
10-18 07:21:00.597 3200 3243 I ScreenCaptureAction: isHomeKeyPressed(), return value = false
10-18 07:21:00.652 3200 3237 E lights : write_int: path /sys/class/backlight/pwm-backlight/brightness, value 20
10-18 07:21:00.655 3200 3238 D KeyguardViewMediator: onScreenTurnedOn, seq = 123
10-18 07:21:00.655 3200 3238 D KeyguardViewMediator: notifyScreenOnLocked
10-18 07:21:00.655 3200 3238 I OrientationDebug: [pwm] in updateOrientationListenerLp()
10-18 07:21:00.655 3200 3241 D KeyguardViewMediator: handleNotifyScreenOn
10-18 07:21:00.655 3200 3241 D LockPatternKeyguardView: onScreenTurnedOn()
10-18 07:21:00.655 3200 3238 V OrientationDebug: in updateOrientationListenerLp(), Screen status=true, current orientation=1, SensorEnabled=false
10-18 07:21:00.655 3200 3238 I OrientationDebug: [pwm] needSensorRunningLp(), return false #3
10-18 07:21:00.660 3200 3241 D LockscreenWallpaperUpdater: onResume()
10-18 07:21:00.660 3200 3241 D LockscreenWallpaperUpdater: get drawable (public)
10-18 07:21:00.660 3200 3241 D LockscreenWallpaperUpdater: get drawable (keygurardupdatemonitor private get)
10-18 07:21:00.660 3200 3241 D LockscreenWallpaperUpdater: drawable is null(keygurardupdatemonitor private get)
10-18 07:21:00.660 3200 3241 D LockscreenWallpaperUpdater: set drawable
10-18 07:21:00.662 3200 3241 D LockscreenWallpaperUpdater: wallpaper file not exist
10-18 07:21:00.662 3200 3241 D InfoWidget: onResume()
10-18 07:21:00.662 3332 3332 I Launcher: onResume(). mIsNewIntent : false screenOff: true
10-18 07:21:00.675 3332 3332 D Launcher: It's image wallpaper. suggestDesiredDimensions(-1,-1)
10-18 07:21:00.705 3200 3218 I OrientationDebug: [WindowOrientationListener] in enable(), now call SensorManager.registerListener()
10-18 07:21:00.705 3200 3218 D SensorManager: registerListener :: handle = 0 name= K3DH Acceleration Sensor delay= 60000 Listener= [email protected]097e0b8
10-18 07:21:00.737 3200 3218 D WallpaperService: ACTION_SCREEN_ON
10-18 07:21:00.737 3200 3218 D WallpaperService: mVisible:true
10-18 07:21:00.737 3200 3218 D WallpaperService: mScreenOn:true
10-18 07:21:00.737 3200 3218 D WallpaperService: mReportedVisible:false
10-18 07:21:00.790 3333 3333 D PhoneUtils: updateRAFT current state : 0
10-18 07:21:00.790 3333 3333 D PhoneUtils: updateRAFT current state : 0 next state : 3
10-18 07:21:00.827 3200 3218 I WindowOrientationListener: orientation = 344.90546 Tilt = 26.42323 -- -2 , 8 , 4
10-18 07:21:00.867 30117 30117 E su : sudb - Opening database
10-18 07:21:00.867 30117 30117 E su : sudb - Database opened
10-18 07:21:00.870 30117 30117 E su : sudb - Database closed
--------------------------------------------------------------------------------
10-18 07:21:00.872 30117 30117 D su : 10109 net.dinglisch.android.taskerm executing 0 /system/bin/sh using shell /system/bin/sh : sh
Time taken: 0.364 seconds
Click to expand...
Click to collapse
Totals: Power button pressed to Display turned on
1. external sdcard inserted........................ 1.828 seconds
2. external sdcard removed......................... 0.911 seconds
3. external sdcard inserted & phone wake_lock'ed... 0.413 seconds
Click to expand...
Click to collapse
We got the numbers, now what? Well, I have no idea but I'll speculate. Having phone come out of suspend with external sdcard present it takes 0.713 seconds to wake up usb, initilize + "insert" sdcard, and bring rest of internals from suspend (24041.991826 - 24042.705211), with sdcard business being the most time consuming. Removing sdcard drastically lowers the time to usb un-suspending to 0.145 seconds (24498.907313 - 24499.052786). Wakelocking the phone pretty much eliminates that time since we're preventing usb+sdcard from powering down by manually locking the suspend, which is really same thing as keeping phone on usb.
From this I concluded that if you hate wakelag, remove your sdcard. If you *really* hate wakelag, don't be taking you phone off usb
Again, this is just a result of me messing with my phone staring at the dumps for 7 hours straight wired on coffee so take this only as a report of my phone's behavior. I'm sure some dev who actually knows what the @$% these logs mean can elaborate much more on this.
edit: use this post/thread to discuss and track down what's causing wakelag and how to fix it. oh, and don't even think of quoting the op, it's huuuuge

So the question is, why is the phone removing USB and ext SD when putting the phone to sleep? Does it serve a purpose? If we remove this feature is there a potential detriment?
Sent from my SPH-D710 using xda premium

squshy 7 said:
So the question is, why is the phone removing USB and ext SD when putting the phone to sleep? Does it serve a purpose? If we remove this feature is there a potential detriment?
Click to expand...
Click to collapse
my only assumption is it's powering down the circuitry to save battery life when phone isn't used. i also wonder how one would go about prevent the suspending of usb/sdcard and, of course, measure how badly it reflect on battery consumption. i wish i knew kernel coding better, lol

frifox said:
my only assumption is it's powering down the circuitry to save battery life when phone isn't used. i also wonder how one would go about prevent the suspending of usb/sdcard and, of course, measure how badly it reflect on battery consumption. i wish i knew kernel coding better, lol
Click to expand...
Click to collapse
Hmm, do other phones do this? I admit I've never researched it, but then again I've never noticed such considerable lag.
I would think that shutting down circuitry to save battery life wouldn't be relevant since the phone isn't constantly accessing the storage media...but I wonder if it has something to do with the SD card being mounted within internal storage...do other phones also follow the /sdcard/external_sd method? Or is this a Samsung quirk?
Sent from my SPH-D710 using xda premium

WOW
what a crazy difference in time from having my 16gb microsd in the phone + not charging vs no sd card and on usb...i can't wait till we have the full explanation and resolution. samsung's nuts for not figuring this out themselves.

d94 said:
WOW
what a crazy difference in time from having my 16gb microsd in the phone + not charging vs no sd card and on usb...i can't wait till we have the full explanation and resolution. samsung's nuts for not figuring this out themselves.
Click to expand...
Click to collapse
That's the thing, it doesn't seem to be a bug per say, but by design
..
Sure, the actual amount of time it takes might be classified as a bug, but the fact that there is a delay seems intentional.
EDIT: OP, I'm going to post your logs on sprint's internal forum today and bump the topic if need be
Sent from my SPH-D710 using xda premium

So I did some digging around the kernel code and found this.
Kernel/drivers/staging/westbridge/astoria/device/cyasdevice.c, lines:
507. cyasblkdev_stop_sdcard();
508. retval = cyasblkdev_start_sdcard();
Click to expand...
Click to collapse
which are inside of the parent wb_resume function (westbridge resume from suspend function?), which apparently is responsible the 0.5 sec of wakelag here:
kmsg dump with phone off usb, external sdcard inserted
<3>[24042.163382] cyasblkdev_stop_sdcard : cy_as_storage_stop is called - found
<3>[24042.687474] cyasblkdev_start_sdcard : cy_as_storage_start is called
Click to expand...
Click to collapse
here's the full wb_resume function:
Code:
static int wb_resume(struct platform_device *devptr)
{
int retval;
int sd_status;
//cy_as_hal_print_message(KERN_ERR"%s called\n", __func__);
//cyasdevice_leave_standby();
//down(&cy_as_device_controller->wq_sema);
cy_as_hal_enable_power(cy_as_device_controller->hal_tag, 1);
cy_as_hal_enable_NANDCLK(1);
gpio_set_value(WB_CLK_EN, 1);
msleep(10);
//cy_as_hal_sleep(10);
//up(&cy_as_device_controller->wq_sema);
enable_irq(WB_CYAS_IRQ_INT);
msleep(5);
sd_status=cy_as_hal_detect_SD();
if(sd_status)
{
down(&cy_as_device_controller->wq_sema);
cy_as_device_controller->cy_work->f_isrunning = 1;
up(&cy_as_device_controller->wq_sema);
retval = cyasdevice_wakeup_thread(1);
if( retval == 0 )
{
msleep(10);
cyasblkdev_stop_sdcard();
retval = cyasblkdev_start_sdcard();
// retval = cy_as_misc_storage_changed(cy_as_device_controller->dev_handle, 0, 0);
if(retval != CY_AS_ERROR_SUCCESS)
{
#ifndef WESTBRIDGE_NDEBUG
cy_as_hal_print_message(KERN_ERR "%s : fail in cy_as_misc_storage_changed (%d) \n", __func__, retval);
#endif
}
}
down(&cy_as_device_controller->wq_sema);
cy_as_device_controller->cy_work->f_isrunning = 0;
up(&cy_as_device_controller->wq_sema);
}
if( sd_status || cy_as_device_controller->cy_work->f_status )
{
cy_as_device_controller->cy_work->f_reload = 2;
queue_delayed_work( cy_as_device_controller->cy_wq, &cy_as_device_controller->cy_work->work, 0);
}
enable_irq(WB_SDCD_IRQ_INT);
return 0;
}
so as a test, i commented out those stop & start functions (why would you stop and start sdcard again when phone is waking up?) and recompiled the kernel. after some testing i did see an improvement in wakelag but it wasnt completely gone. both internal and external sdcards seemed to work just fine after wakeups so that's the good news. the bad news is, next morning i received a phone call and the device hot-rebooted on me. that was after running viperROM for a day, but since i never had my phone reboot on me after a call i'd say it could be a result of me commenting out those sdcard stop/start functions.
tl;dr: it's possible to improve wakelag by 0.5 seconds but sadly it doesn't completely get rid of it and could possibly lead to hot reboots (still to be confirmed).

frifox said:
So I did some digging around the kernel code and found this.which are inside of the parent wb_resume function (westbridge resume from suspend function?), which apparently is responsible the 0.5 sec of wakelag here:
here's the full wb_resume function:
Code:
static int wb_resume(struct platform_device *devptr)
{
int retval;
int sd_status;
//cy_as_hal_print_message(KERN_ERR"%s called\n", __func__);
//cyasdevice_leave_standby();
//down(&cy_as_device_controller->wq_sema);
cy_as_hal_enable_power(cy_as_device_controller->hal_tag, 1);
cy_as_hal_enable_NANDCLK(1);
gpio_set_value(WB_CLK_EN, 1);
msleep(10);
//cy_as_hal_sleep(10);
//up(&cy_as_device_controller->wq_sema);
enable_irq(WB_CYAS_IRQ_INT);
msleep(5);
sd_status=cy_as_hal_detect_SD();
if(sd_status)
{
down(&cy_as_device_controller->wq_sema);
cy_as_device_controller->cy_work->f_isrunning = 1;
up(&cy_as_device_controller->wq_sema);
retval = cyasdevice_wakeup_thread(1);
if( retval == 0 )
{
msleep(10);
cyasblkdev_stop_sdcard();
retval = cyasblkdev_start_sdcard();
// retval = cy_as_misc_storage_changed(cy_as_device_controller->dev_handle, 0, 0);
if(retval != CY_AS_ERROR_SUCCESS)
{
#ifndef WESTBRIDGE_NDEBUG
cy_as_hal_print_message(KERN_ERR "%s : fail in cy_as_misc_storage_changed (%d) \n", __func__, retval);
#endif
}
}
down(&cy_as_device_controller->wq_sema);
cy_as_device_controller->cy_work->f_isrunning = 0;
up(&cy_as_device_controller->wq_sema);
}
if( sd_status || cy_as_device_controller->cy_work->f_status )
{
cy_as_device_controller->cy_work->f_reload = 2;
queue_delayed_work( cy_as_device_controller->cy_wq, &cy_as_device_controller->cy_work->work, 0);
}
enable_irq(WB_SDCD_IRQ_INT);
return 0;
}
so as a test, i commented out those stop & start functions (why would you stop and start sdcard again when phone is waking up?) and recompiled the kernel. after some testing i did see an improvement in wakelag but it wasnt completely gone. both internal and external sdcards seemed to work just fine after wakeups so that's the good news. the bad news is, next morning i received a phone call and the device hot-rebooted on me. that was after running viperROM for a day, but since i never had my phone reboot on me after a call i'd say it could be a result of me commenting out those sdcard stop/start functions.
tl;dr: it's possible to improve wakelag by 0.5 seconds but sadly it doesn't completely get rid of it and could possibly lead to hot reboots (still to be confirmed).
Click to expand...
Click to collapse
Thanks working on lag bug.
Hopefully it can be totally eliminated in near future

any more updates on this?

[MOD] SMS_MMS_SIP enabled on [ROM][Nightly][ICS/JB] TeamEos (umts_everest/MZ601)

Hi guys,
I am new to xoom, but with my little skills I have modded the Framework-res.apk for umts_everest/MZ601 on TeamEOS nighlty ICS build. I used framework from nightly build 8. If required will update this in future. I have tested SMS feature. Have not tested the SIP as I do not have access. Telephony works but as a well known fact mic and speakers are not supported yet so its almost useless.
I have tested it on latest build nightly 10 it works well, however please backup ROM before flashing.
A Word of caution, flash this MOD at your own risk, Please do not blame me for bricked devices
How to flash:
Just download the update.zip attached, copy it to SDCARD.
Enter recovery and backup the ROM first.
Now flash the MOD and reboot.
The Latest Version can be found here [Build Version 79]
Press thanks button if This helped you.

trip007in said:
Hi guys,
I am new to xoom, but with my little skills I have modded the Framework-res.apk for umts_everest/MZ601 on TeamEOS nighlty ICS build. I used framework from nightly build 8. If required will update this in future. I have tested SMS feature. Have not tested the SIP as I do not have access. Telephony works but as usual mic and speakers are not supported yet so its almost useless.
Please note that I have not tested it on latest build, so please backup ROM before flashing.
A Word of caution, flash this MOD at your own risk, Please do not blame me for bricked devices
How to flash:
Just download the update.zip attached, copy it to SDCARD.
Enter recovery and backup the ROM first.
Now flash the MOD and reboot.
Press thanks button if This helped you.
Click to expand...
Click to collapse
I've been waiting for someone to get around to this again, ever since the old Tiamat days when it was enabled. BUT (and it's a big but) can you do this mod for a different EOS build? Like Stingray perhaps #hint hint#
Sent from my Xoom using xda premium

brittoking said:
I've been waiting for someone to get around to this again, ever since the old Tiamat days when it was enabled. BUT (and it's a big but) can you do this mod for a different EOS build? Like Stingray perhaps #hint hint#
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
yeah.. Just upload your framework-res.apk from the ROM. But I can not test it you will have to do it on your own.

SMS works well with nightly 9. Thank you once again. Cheers.

finalmoksha said:
SMS works well with nightly 9. Thank you once again. Cheers.
Click to expand...
Click to collapse
Tested on Nightly 10, works well.

Can I flash to mz600? Or it only for mz601?
---------- Post added at 02:15 PM ---------- Previous post was at 01:59 PM ----------
Not working for mz600.. will post framework-res for mz600 tonight

Working great here too. Can you somehow make the voice run?

here my original framework-res.apk from MZ600 nightly build 25 (Eos-stingray_cdma-25.zip)

vouldjeff said:
Working great here too. Can you somehow make the voice run?
Click to expand...
Click to collapse
+1
Regards.

I'm sorry my friend. I am on 3 days official tour. So you will have to wait for 3 days. Mean while if I have access to a PC or laptop I will try to do it.
monyozt said:
here my original framework-res.apk from MZ600 nightly build 25 (Eos-stingray_cdma-25.zip)
Click to expand...
Click to collapse
Sent from my GT-I9003 using XDA Premium App

That would be really awesome friends, but the hardware support is required in the room and I don't have so much knowledge about that.
vouldjeff said:
Working great here too. Can you somehow make the voice run?
Click to expand...
Click to collapse
Sent from my GT-I9003 using XDA Premium App

Has anyone tried to make calls using lets say a bluetooth headset?

trip007in said:
I'm sorry my friend. I am on 3 days official tour. So you will have to wait for 3 days. Mean while if I have access to a PC or laptop I will try to do it.
Sent from my GT-I9003 using XDA Premium App
Click to expand...
Click to collapse
Okai... so for next 3 days I will post newest one from lastest build
Sent from my Xoom using xda premium

Hello,
i have build a update.zip for the nighly build 11.
Enable SMS/MMS and Telphony
Original ICS MMS.apk
Sony Bravia Engine
International Google Book
3 missing Live Wallpapers (MagicSmoke, NoiseField, Galaxy)
Speech Recorder
Regards
Rivendel

So, do i understand that correct that "normal" phone calls work with a bluetooth headset?
Rivendel said:
Hello,
i have build a update.zip for the nighly build 11.
Enable SMS/MMS and Telphony
Original ICS MMS.apk
Sony Bravia Engine
International Google Book
3 missing Live Wallpapers (MagicSmoke, NoiseField, Galaxy)
Speech Recorder
Regards
Rivendel
Click to expand...
Click to collapse

TarKin said:
So, do i understand that correct that "normal" phone calls work with a bluetooth headset?
Click to expand...
Click to collapse
As my Bluetooth Headset disappeared (ask my Kids ;-)) i could not tell you if it works with a BT-Headset. It works NOT with a Cable-Headset or BuildIn Mic/Speaker (missing Sound).
But if you have one, you could give us a note if it works or not.
Regards
Rivendel.

As far as I know sound does not work with bt headset also.
Sent from my GT-I9003 using XDA Premium App

The same problem as before:
sms > ok (using 'handcent sms' and 'go sms pro' both are almost equal.)
in/outcoming calls > ok (but with no sound)
aLogcat
Code:
D/alogcat ( 2514): starting ...
D/alogcat ( 2514): stopped
I/HeadsetService( 1340): During phone call: disable DSP.
I/AwesomePlayer( 1034): reset
I/AwesomePlayer( 1034): cancel player events
I/AwesomePlayer( 1034): cancel player events
I/AudioService( 1062): AudioFocus requestAudioFocus() from AudioFocus_For_Phone_Ring_And_Calls
D/AudioHardwareInterface( 1034): setMode(RINGTONE)
V/alogcat ( 2514): save instance
V/alogcat ( 2514): paused
I/power ( 1062): *** set_screen_state 1
D/dalvikvm( 1130): GC_CONCURRENT freed 484K, 39% free 7608K/12423K, paused 1ms+2ms
W/IInputConnectionWrapper( 2514): getExtractedText on inactive InputConnection
W/IInputConnectionWrapper( 2514): showStatusIcon on inactive InputConnection
D/alogcat ( 2514): stopping ...
D/alogcat ( 2514): stopped
D/InCallTouchUi( 1147): onDialTrigger(whichHandle = 1)...
I/AwesomePlayer( 1034): reset
I/AwesomePlayer( 1034): cancel player events
I/phone ( 1147): acceptCall: incoming...
I/AwesomePlayer( 1034): reset
I/AwesomePlayer( 1034): cancel player events
I/AwesomePlayer( 1034): reset
I/AwesomePlayer( 1034): cancel player events
D/InCallTouchUi( 1147): updateState: Too soon after last action; not drawing!
I/AwesomePlayer( 1034): reset
I/AwesomePlayer( 1034): cancel player events
I/HeadsetService( 1340): During phone call: disable DSP.
I/AudioService( 1062): AudioFocus requestAudioFocus() from AudioFocus_For_Phone_Ring_And_Calls
[B]D/AudioHardwareInterface( 1034): setMode(IN_CALL)[/B]
D/dalvikvm( 1062): GC_EXPLICIT freed 509K, 30% free 20145K/28679K, paused 3ms+6ms
D/dalvikvm( 2576): GC_CONCURRENT freed 794K, 14% free 6894K/7943K, paused 3ms+1ms
I/power ( 1062): *** set_screen_state 0
D/SurfaceFlinger( 1031): About to give-up screen, flinger = 0xa830
I/power ( 1062): *** set_screen_state 1
I/power ( 1062): *** set_screen_state 1
D/SurfaceFlinger( 1031): Screen about to return, flinger = 0xa830
D/alogcat ( 2514): stopping ...
D/alogcat ( 2514): canceling periodic saves
V/alogcat ( 2514): started
V/alogcat ( 2514): resumed
D/alogcat ( 2514): starting ...
D/dalvikvm( 1147): GC_CONCURRENT freed 912K, 10% free 9457K/10503K, paused 7ms+4ms
W/IInputConnectionWrapper( 1147): getExtractedText on inactive InputConnection
W/IInputConnectionWrapper( 1147): showStatusIcon on inactive InputConnection
D/dalvikvm( 1130): GC_CONCURRENT freed 399K, 39% free 7645K/12423K, paused 2ms+2ms
D/dalvikvm( 1062): GC_EXPLICIT freed 429K, 30% free 20109K/28679K, paused 9ms+3ms
D/dalvikvm( 2576): GC_EXPLICIT freed 19K, 14% free 6875K/7943K, paused 2ms+1ms
D/dalvikvm( 1978): GC_EXPLICIT freed 38K, 10% free 8076K/8967K, paused 6ms+1ms
I/HeadsetService( 1340): Phone status idle: enable DSP.
I/AudioService( 1062): AudioFocus abandonAudioFocus() from AudioFocus_For_Phone_Ring_And_Calls
D/AudioHardwareInterface( 1034): setMode(NORMAL)
Another aLogcat, this time made it from another android phone (calls working obv.).
Code:
I/phone ( 351): acceptCall: incoming...
D/AudioHardwareInterface( 138): setMode(RINGTONE)
E/AudioPolicyManagerBase( 138): unknown stream type
E/AudioPolicyManagerBase( 138): unknown stream type
E/AudioPolicyManagerBase( 138): unknown stream type
E/AudioPolicyManagerBase( 138): unknown stream type
D/kernel ( 130): [ 1043.450927] [voice.c:remote_cb_function] len=40 id=81
I/AudioService( 237): AudioFocus requestAudioFocus() from AudioFocus_For_Phone_Ring_And_Calls
D/kernel ( 130): [ 1043.869140] Enabled VREG "wlan" at 2900 mV
D/kernel ( 130): [ 1043.875030] Disabled VREG "wlan"
D/kernel ( 130): [ 1043.881622] Enabled VREG "wlan" at 2900 mV
D/DASH - select( 237): sensors_select_callback: select canceled by request
D/DASH - select( 237): sensors_select_callback: select canceled by request
D/DASH - select( 237): sensors_select_callback: select canceled by request
[B]D/AudioHardwareInterface( 138): setMode(IN_CALL)[/B]
I/AudioHardwareMSM7X30( 138): Routing audio to Handset
I/AudioHardwareMSM7X30( 138): Routing audio to handset with DualMike enabled
D/AudioHardwareMSM7X30( 138): new_rx = 0
D/AudioHardwareMSM7X30( 138): new_tx = 9
D/AudioHardwareMSM7X30( 138): Starting voice on Rx 0 and Tx 9 device
D/AudioHardwareMSM7X30( 138): value of device and enable is 32 0
D/AudioHardwareMSM7X30( 138): value of device and enable is 0 1
D/lights ( 237): set_light_buttons: brightness=0
D/kernel ( 130): [ 1043.890899] [voice.c:voice_auddev_cb_function] auddev_cb_function, evt_id=1, dev_state=4, voc_state=3
D/kernel ( 130): [ 1043.890930] [voice.c:voice_auddev_cb_function] auddev_cb_function, evt_id=1, dev_state=4, voc_state=3
D/kernel ( 130): [ 1043.890960] [msm7x30.c:msm_device_put] device xloud_speaker_mono_rx set 0
D/kernel ( 130): [ 1043.890991] [msm7x30.c:msm_device_put] device handset_rx set 1
D/kernel ( 130): [ 1043.890991] [msm7x30.c:msm_device_put] device freq =48000
D/lights ( 237): set_light_backlight: brightness=0
Where is AudioHardware on first logcat.
Regards.

Rivendel said:
Hello,
i have build a update.zip for the nighly build 11.
Enable SMS/MMS and Telphony
Original ICS MMS.apk
Sony Bravia Engine
International Google Book
3 missing Live Wallpapers (MagicSmoke, NoiseField, Galaxy)
Speech Recorder
Regards
Rivendel
Click to expand...
Click to collapse
Install this update using adb, right?
EDIT : Never mind, got it.

My Update.zip for Build 13
Regards
Rivendel

S20 + rooting build dalvik.vm. hip size question

dalvik.vm.heapstartsize = 32m
dalvik.vm.heapgrowthlimit = 192m
dalvik.vm.heapsize = 768m
dalvik.vm.heaptargetutilization = 0.75
256 메모리인데
저 값은 안맞는 듯합니다
빠르게 앱 구동 설정하고 싶은데요
Translation:
256 memory
That price doesn't seem right
I want to quickly set up the app operation