Develop Bugs

[How To] WM Dialer moding (tapres.dll.0xxx.mui)

Tuto: Modification of a Dialer​
Hello everyone,
This Tuto allowing to intervene directly on the resources of your dialer. Ie DLL.
Advantages: No additional resource, only those origins. So, not one gram of fat added. A Dialer 0%
The items made available or examples are from the rom of my LG KS20 QVGA (Rom KisS20 of Spocky), you've got to bring such changes to your devices.
1) Resources (DLL)
First you must know that your dialer is mainly used two resources:
The first is by "default" of WM. It tapres.dll.0xxx.mui nome. XXX is the language ID (FR = 040C -> tapres.dll.040C.mui).
The second is usually the manufacturer. It is here to provide additional functionality (type video calls), and / or skin.
The name of this DLL can be found here ->
[HKEY_LOCAL_MACHINE\Security\Phone\Skin] [HKEY_LOCAL_MACHINE \ Security \ Phone \ Skin]
"Enabled" = dword: 00000000
"ext" = "\ windows \ Your DLL.dll"
To activate one or the other DLLs just go "Enabled" = dword: 0000000 0 (DLL by default) to 1 (DLL constructor).
Every two are in the Windows directory on your PPC.
2) Images
Your default dialer is composed of the following images:
dlrback_land.png--------->Background dialer
dlrback_port.png
dlrbtndef_dwn_land.gif--> buttons for the functions call, speed dial, etc.
dlrbtndef_dwn_port.gif
dlrbtndef_up_land.gif
dlrbtndef_up_port.gif
dlrbtnend_up_land.gif----> button "Done"
dlrbtnend_up_port.gif
dlrbtntalk_up_land.gif----> button "Call"
dlrbtntalk_up_port.gif
dlrbtn_dwn_land.gif------> other keys (numbers / letters)
dlrbtn_dwn_port.gif
dlrbtn_up_land.gif
dlrbtn_up_port.gif
"Port" for the portrait, "Land" for landscape mode. "Up" for keys not pressed, "dwn" for keys pressed.
Note: The images used for the buttons' functions are identical to the keys "call status".
3) Tools
A resource editor (Restorator, Resource Tuner etc)
Unsigned MSigner and to sign your DLL amended
Drawing software (Photoshop and others)
The notepad ...
4) Modification of resources (DLL)
With the help of your editor and open your DLL go to the directory Dialog.
Resources 22500 (dialer, landscape mode), 22507 (call status landscape mode), 22509 (dialer, portrait mode) and 22510 (call status portrait) define your dialer.
Change the size and location of images of different elements. The keyboard, calling area, the SmartDial ....
Example using 0 to 9
CONTROL "", 23041, "MS_PHONE_BUTTON", 1, 122, 52, 36 ----> Size
CONTROL "", 23042, "MS_PHONE_BUTTON", 54, 122, 52, 36 ----> Implantation
CONTROL "", 23041, "MS_PHONE_BUTTON", 1 , 122 , 52 , 36 CONTROL "", 23041, "MS_PHONE_BUTTON", 1, 122, 52, 36
The first 2 values Y = X and X is the location left / right and Y up / down
Les 2 autres = taille de l'image, longueur / largeur The other 2 = image size, length / width
Save your new DLL, sign here and test.
5) Edit pictures
Nothing special ...
In my previous example the size of my images is increased to 52x36. So I created new images to this size. They replace the original (dlrbtndef_dwn_port.gif, dlrbtndef_up_land.gif, dlrbtndef_up_port.gif ...).
Open a simple image viewer, Edit -> resize -> Save 52x36
Go to the experts Edit -> change color -> Save.
6) Putting
I change my DLL tapres.dll.040C.mui as follows:
Dialog 22509
..... .....
CONTROL "", 23041, "MS_PHONE_BUTTON", 1, 122, 52, 36
CONTROL "", 23042, "MS_PHONE_BUTTON", 54, 122, 52, 36
CONTROL "", 23043, "MS_PHONE_BUTTON", 107, 122, 52, 36
CONTROL "", 23044, "MS_PHONE_BUTTON", 1, 159, 52, 36
CONTROL "", 23045, "MS_PHONE_BUTTON", 54, 159, 52, 36
CONTROL "", 23046, "MS_PHONE_BUTTON", 107, 159, 52, 36
CONTROL "", 23047, "MS_PHONE_BUTTON", 1, 196, 52, 36
CONTROL "", 23048, "MS_PHONE_BUTTON", 54, 196, 52, 36
CONTROL "", 23049, "MS_PHONE_BUTTON", 107, 196, 52, 36
CONTROL "", 23051, "MS_PHONE_BUTTON", 1, 233, 52, 36
CONTROL "", 23050, "MS_PHONE_BUTTON", 54, 233, 52, 36
CONTROL "", 23052, "MS_PHONE_BUTTON", 107, 233, 52, 36
CONTROL "", 23001, "MS_PHONE_BUTTON", 160, 122, 79, 36
CONTROL "", 23012, "MS_PHONE_BUTTON", 160, 159, 79, 36
CONTROL "", 23011, "MS_PHONE_BUTTON", 160, 196, 79, 36
CONTROL "", 23014, "MS_PHONE_BUTTON", 160, 233, 79, 36
..... .....
I also modified the original image and I let [HKEY_LOCAL_MACHINE \ Security \ Phone \ Skin]
"Enabled" = dword: 0000000 0 for do not call for anything else (DLL or manufacturer, or a skin external).
Here is the result
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

7) The base registry
From the registry you can almost touch any settings for your Skin, images, text, color etc..
In the example above you can see that the text is centered, the figures are white, the letters are gray. Here's how to proceed.
"Enabled" = dword: 0000000 1 ---> Skin Active
[HKEY_LOCAL_MACHINE\Security\Phone\Skin\Dialer\Landscape\dialbutton]
"MajorFlags" = dword: 00000005 -------> centered position of Figures dialer
"MinorFlags" = dword: 00000005 -------> centered position of Letters from the dialer
"MajorColor" = dword: 00ffffff -------> Color numbers (00ffffff = white)
"MinorColor" = dword: 00cccccc -------> Color Letters (00cccccc = gray)
[HKEY_LOCAL_MACHINE\Security\Phone\Skin\Dialer\Portrait\dialbutton]
"MinorFlags" = dword: 00000005
"MajorFlags" = dword: 00000005
"MajorColor" = dword: 00ffffff
"MinorColor" = dword: 00cccccc
It can also affect the style MajorRCMLStyle ...
For the "textFlags" position is defined as:
dword 0 : top left
dword 1 : top center
dword 2 : top right
dword 4 : middle left
dword 5 : middle center (default value)
dword 6 : middle right
dword 8 : bottom left
dword 9 : bottom center
dword A : bottom right
In my case I have 5, one centering vertically and horizontally (almost perfect because the numbers and letters are struggling a bit them secret ) )
"textLayoutFlags" : "textLayoutFlags":
dword 0: Numbers, then Letters
dword 1: Letters, Numbers then
dword 2: just numbers (no letters)
In my case I have 0 ...
Here are the keys to BDR that you can learn:
HKLM\Security\Phone\Skin\ =This is the main key for phone skins
DIALER = This is the main dial pad that you dial phone numbers on
LANDSCAPE and PORTRAIT = The orientation or the dialpad phone you should change the same key in both orientation to stay consistant
text = Text in the "Information Window" The one that shows last number dialed, contact info, etc.
textColor = Color of the text in the information window
dialbutton = Button that displays the numbers you dial
MajorColor = Color of the dial button digits
MinorColor = Color of the dial button text (abc, def)
MajorRCMLStyle = Size of the dial button digit, HEX values are smaller for the 1 through 20 for the largest (1a, 1b, 1c, etc.)
MinorRCMLStyle = Size of the dial button text, HEX values are smaller for the 1 through 20 for the largest (1a, 1b, 1c, etc.)
MajorFlags = Position of the number on the dial button, values are 1-13 (decimal), IE, Upperleft, bottomright, center, etc. (Hex 400 makes the text invisible)
MinorFlags = Position of the text on the dial button, values are 1-13 (decimal), IE, Upperleft, bottomright, center, etc. (Hex 400 makes the text invisible)
bmpNormal = Path to the Bitmap you see when you are not touching the keys
bmpPressed = Path to the Bitmap you see when you press a dial key
bmpFlags = Adjusts the alignment of the bitmap on the key, not commonly used
bmpTransparency = Transparency of the bitmap and ability to show through backgound image
bmpDisabled = Bitmap that displays if the button goes disabled, like "Hold" is disabled if you are not in call
erasebutton = Button that erases digits you typed (Usually the back arrow)
bmpNormal = Path to the Bitmap you see when you are not touching the keys
bmpPressed = Path to the Bitmap you see when you press a dial key
bmpFlags = Adjusts the alignment of the bitmap on the key, not commonly used
bmpTransparency = Transparency of the bitmap and ability to show through backgound image
bmpDisabled = Bitmap that displays if the button goes disabled, like "Hold" is disabled if you are not in call
VerbButton = Button (f0f0f special value will make the text invisible on the textFlags key)
textColor = Color of the "Call History" text
textRCMLStyle = Size of the "Call History" text, HEX values are smaller for the 1 through 20 for the largest (1a, 1b, 1c, etc.)
textFlags = Position of the "Call History" button on the text, values are 1-13 (decimal), IE, Upperleft, bottomright, center, etc.
bmpNormal = Path to the Bitmap you see when you are not touching the keys
bmpPressed = Path to the Bitmap you see when you press a dial key
bmpFlags = Adjusts the alignment of the bitmap on the key, not commonly used
bmpTransparency = Transparency of the bitmap and ability to show through backgound image
bmpDisabled = Bitmap that displays if the button goes disabled, like "Hold" is disabled if you are not in call
textDisabledColor = text of the disabled in the event a button goes disabled
other = Only used to define the page background
bmpNormal = Path to the image used in the background
TalkEndButton = The setting for the combined talk / end button
bmpDisabledEnd = Bitmap that displays when the End button goes disabled
bmpDisabledTalk = Bitmap that displays when the Talk button goes disabled
bmpFlagsEnd = Adjusts the alignment of the bitmap on the key, not commonly used
bmpFlagsTalk = Adjusts the alignment of the bitmap on the key, not commonly used
bmpNormalEnd = Path to the Bitmap you see when End is active
bmpNormalTalk = Path to the Bitmap you see when Talk is active
bmpPressedEnd = Path to the Bitmap you see when End is pressed
bmpPressedTalk = Path to the Bitmap you see when Talk is pressed
bmpTransparencyEnd = End of the bitmap and ability to show through backgound image
bmpTransparencyTalk = Transparency of the Talk bitmap and ability to show through backgound image Transparency
PROGRESS = This is the "In Call" page you see when on a call
VerbButton = Call History Button (special value f0f0f will make the text invisible on the textFlags key)
textColor = Color of the "Call History" text
textRCMLStyle = Size of the "Call History" text, values are HEX 1a for the smaller through 20 for the largest (1a,1b,1c, etc)
textFlags = Position of the "Call History" text on the button, values are 1-13 (decimal), IE, Upperleft, bottomright, center,etc
bmpNormal = Path to the Bitmap you see when you are not touching the keys
bmpPressed = Path to the Bitmap you see when you press a dial key
bmpFlags = Adjusts the alignment of the bitmap on the key, not commonly used
bmpTransparency = Transparency of the bitmap and ability to show through backgound image
bmpDisabled = Bitmap that displays if the button goes disabled, like "Hold" is disabled if you are not in call
other =Only used to define the background page
bmpNormal = Path to the image used in the background
TalkEndButton = The setting for the combined talk/end button
bmpDisabledEnd = Bitmap that displays when the End button goes disabled
bmpDisabledTalk = Bitmap that displays when the Talk button goes disabled
bmpFlagsEnd = Adjusts the alignment of the bitmap on the key, not commonly used
bmpFlagsTalk = Adjusts the alignment of the bitmap on the key, not commonly used
bmpNormalEnd = Path to the Bitmap you see when End is active
bmpNormalTalk = Path to the Bitmap you see when Talk is active
bmpPressedEnd = Path to the Bitmap you see when End is pressed
bmpPressedTalk = Path to the Bitmap you see when Talk is pressed
bmpTransparencyEnd = Transparency of the End bitmap and ability to show through backgound image
bmpTransparencyTalk = Transparency of the Talk bitmap and ability to show through backgound image
text =Text in the "Information Window" The one that shows last number dialed, contact info, etc
textColor = Color of the text in the information window
8) Problems
For those who have already installed a dialer skin you must delete all keys added to the registry.
HKEY_LOCAL_MACHINE \ Security \ Phone \ Skin \ DIALER (entire directory)
HKEY_LOCAL_MACHINE \ Security \ Phone \ Skin \ PROGRESS (entire directory)
For HTC but also look here, if problems in displaying and / or color persisted.
[HKEY_LOCAL_MACHINE\Software\HTC\PHONE]
[HKEY_LOCAL_MACHINE\SOFTWARE\HTC\SmartDialing]
You have to play.
Thank you to Mat for the Tuto clarification and all those involved in its improvement.
Rickou26 (Or Arthemus).

My File
@+ Rickou26

very nice tutorial
thanks a lot

Thank you sheennick123456.

Hi,
A new screnn

Thanks rickou26 , I'm gonna give it a try and make my own.

Hi,
Good, we look forward to the result
By.

tested the value for size of caracters for history call
not working on touch pro wm6.1

Hi,
Update new build 23028 or newer and VideoDialer for LG KS20.
To remove the scroll bar just to make the following change -> HKLM \ System \ GWE \ cxVScr = 0
By.

Hello,
For KS20 user :
change only this key to swap Videodialer/WmDialer
[HKEY_LOCAL_MACHINE\Security\Phone\Skin] [HKEY_LOCAL_MACHINE \ Security\ Phone\ Skin]
"ext" = "" -> Wm Dialer
"ext" = "\windows\LgePhoneExt.dll" Video Dialer
By

Good Tutorial but I have a little problem with DLL: I couldn't copy it on PC to change button size (I tried with Resco Explorer and PC Explorer).
I have a Touch HD with WM6.5 (see signature to specific ROM)
Thanks a lot ^^
D'rath

Hi,
The simplest is to retrieve the DLL directly in the source files of the ROM (OEM or SYS). WM files are identical regardless of the PPC so you can use packetages filed by Da_G.
For your problem is simply that these DLLs are identified as belonging to the ROM which sometimes blocks their copy ...
By.

Hello,
build 23420 update to MediaFire.
By.

Thank you for this tutorial, awesome work!

rickou26 said:
Hello,
build 23420 update to MediaFire.
By.
Click to expand...
Click to collapse
Your dialer is nice and slick with latest pureblack theme compatible with COM3/4 branch. Great combo

Great tuto!! I have been through this many times and have yet to have success! It seems though this tuto is pre WM6.5 so I'm wondering if the .dll that the dialer calls on has changed in WM6.5? Or maybe the .dll I need to edit is different as I have a Samsung Omnia. I made all of the changes in tapres.dll.0409.mui and changed the image sizes accordingly but the dialer does not change! Any help?? I noticed the dialog header is 0,0,320,240, in the resource, does this mean it is only for that resolution? Thanks.

Hi,
totalcommander (or resco explorer) used to copy the dll into windows and overwrite the original.
@+

rickou26 said:
Hi,
totalcommander (or resco explorer) used to copy the dll into windows and overwrite the original.
@+
Click to expand...
Click to collapse
I forgot to mention, I am a chef and I am just editing the .dll and then cooking it in. Maybe there is something I am missing there so I will try just adding the edited .dll to the windows directory. Thanks!

If the keyboard appears unchanged is that the original has not been replaced. No keyboard only appears if it is a problem signing the DLL. Also your kitchen must include this signature certificate ;-)
@ +

[Q] Camera FPS edit in bulid.prop

I am running virtuous .7.1 and cannot find these values to lock the camera to 24 or 30 fps while recoding
ro.media.enc.file.format = 3gp,mp4
ro.media.enc.vid.codec = m4v,h263
ro.media.enc.vid.h263.width = 176,1280
ro.media.enc.vid.h263.height = 144,720
ro.media.enc.vid.h263.bps = 64000,2000000
ro.media.enc.vid.h263.fps = 30
ro.media.enc.vid.m4v.width = 176,1280
ro.media.enc.vid.m4v.height = 144,720
ro.media.enc.vid.m4v.bps = 64000,2000000
ro.media.enc.vid.m4v.fps = 30
any help is greatly appreciated

[KERNEL][Sep18]-=UNITY V9=-[2.6.35.14][OC/UV][CIFS/TUN][SLQB][NOOP][2WCR]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Features:
Based on Official GB kernel source code from HTC
Patched to .14
2-way call records - https://market.android.com/details?id=com.skvalex.callrecorder
OC up to 2016MHz (Default 245 - 1075MHz @ Ondemand)
VDD sysfs interface
Tweaked Interactive governor
Additional Virtuous/SmartAss/SavagedZen/Scary governors
Audio Boosts (20%)
CIFS
TUN
CFS
SLQB
NOOP I/O scheduler
TINY PREEMPT RCU
Full EXT4 Support
and more...
Click to expand...
Click to collapse
Compatible with:
All Sense ROM's based on Android 2.3.4 - 2.3.5 >
Click to expand...
Click to collapse
Issues:
- you tell me
Click to expand...
Click to collapse
Install:
- Flash via CWM
Click to expand...
Click to collapse
Download UNITY V9:
http://www.multiupload.com/VPFKEN5RAM
For correct work 2wcr function use CallRecorder app https://market.android.com/details?id=com.skvalex.callrecorder
Click to expand...
Click to collapse
Enjoy
Click to expand...
Click to collapse
More info & GPL:
Virtuous Home: http://www.virtuousrom.com
Virtuous Forum: http://forums.virtuousrom.com/index.php
HTC: http://www.htc.com/
Kernel GIT: https://github.com/mdeejay/msm7x30-gb-kernel
Thanks: Markinus (for teach), avs234 & skvalex (for 2WCR), Flemmard, seo and other Virtuous team, LordClockaN, LeeDroid, etc​

Changelog:
Code:
UNITY V9:
- OC up to 2.0GHz
- Tweak all governors
- New Virtuous governor
- XZ compressing
- PREEMPT_TINY_RCU
- lots minor fixes & tweaks
UNITY V8:
- Fixed VDD
- OC up to 1804MHz
UNITY V7:
- Added VDD sysfs interface
UNITY V6:
- Enabled AMR format support for CallRecorder
- Fixed support apps like "Voice Commander"
UNITY V5:
- Fixed USB for Android 2.3.4
- "Fast USB charging" hack
UNITY V4:
- Added new module for 2wcr
---- Fixed hardware amr recordings
---- Fixed stereo recordings
---- Fixed missing call recordings
- Some minor cleanups
UNITY V3:
- New OC method with 50 steps
- New acpu table
- Fixed kernel info
- Some cleanups
UNITY V2:
- Reverted new audio drivers
- Added 2WCR patch for new audio drivers
- Added Wi-Fi Calling support for T-Mobile users (Kineto GAN)
- Disabled BFQ / Enabled Deadline
- Disabled btrfs & ext2 support
UNITY V1:
- Added support HTC Desire Z & HTC My Touch 4G
- Tweaked video drivers
- CIFS/TUN/UTF set as modules
[SIZE="2"]v.23:
- Back to old video drivers (from official HTC source)
- ACPU edits
v.22:
- Improved SmartAss works with >=1600Mhz
v.21:
- new acpu table
- tweaked governors
- some cleanups
- max OC 1708MHz
v.20:
- not released
v.19:
- Updated video drivers from CodeAurora
- Added BFQ v.2-r1
- Tweak SmartAss (XBOCT)
- Increase GPU & Camera memory allocation (Lee)
- Disable write cache support
- Correct LCD panel size
- Added 1612MHz to acpu table
v.18:
- Added 2 steps in acpu table
- New universal updater script for both filesystems
- Prevent memory leak on hotplug
v.17:
- Added 2-way call records
v.16:
- Based on official GB kernel source code from HTC
- Enabled OC (1516MHz MAX)
- Removed 2-way call records patch
- Added Smartass governor
- Added interactive governor
- Added Conservative governor
- Added audio boost
- Added default V(R) I/O Scheduler
- Added default SLQB Memory allocator[/SIZE]
ACPU Table:
Code:
{ 122000, PLL_3, 5, 2, 61440, 875, VDD_RAW(875) },
{ 245000, PLL_3, 5, 1, 192000, 875, VDD_RAW(875) },
{ 307200, PLL_3, 5, 1, 192000, 900, VDD_RAW(900) },
{ 384000, PLL_1, 2, 0, 192000, 900, VDD_RAW(900) },
{ 460800, PLL_3, 5, 1, 192000, 925, VDD_RAW(925) },
{ 537600, PLL_2, 3, 0, 192000, 950, VDD_RAW(950) },
{ 614400, PLL_2, 3, 0, 192000, 950, VDD_RAW(950) },
{ 691200, PLL_2, 3, 0, 192000, 975, VDD_RAW(975) },
{ 768000, PLL_2, 3, 0, 192000, 1000, VDD_RAW(1000) },
{ 844800, PLL_2, 3, 0, 192000, 1000, VDD_RAW(1000) },
{ 921600, PLL_2, 3, 0, 192000, 1025, VDD_RAW(1025) },
{ 998400, PLL_2, 3, 0, 192000, 1025, VDD_RAW(1025) },
{ 1075200, PLL_2, 3, 0, 192000, 1050, VDD_RAW(1050) },
{ 1152000, PLL_2, 3, 0, 192000, 1075, VDD_RAW(1075) },
{ 1228800, PLL_2, 3, 0, 192000, 1100, VDD_RAW(1100) },
{ 1305600, PLL_2, 3, 0, 192000, 1125, VDD_RAW(1125) },
{ 1382400, PLL_2, 3, 0, 192000, 1150, VDD_RAW(1150) },
{ 1459200, PLL_2, 3, 0, 192000, 1200, VDD_RAW(1200) },
{ 1536000, PLL_2, 3, 0, 192000, 1275, VDD_RAW(1275) },
{ 1612800, PLL_2, 3, 0, 199680, 1325, VDD_RAW(1325) },
{ 1689600, PLL_2, 3, 0, 199680, 1375, VDD_RAW(1375) },
{ 1766400, PLL_2, 3, 0, 199680, 1425, VDD_RAW(1425) },
{ 1843200, PLL_2, 3, 0, 199680, 1450, VDD_RAW(1450) },
{ 1920000, PLL_2, 3, 0, 199680, 1475, VDD_RAW(1475) },
{ 1996800, PLL_2, 3, 0, 199680, 1500, VDD_RAW(1500) },
{ 2016000, PLL_2, 3, 0, 201600, 1500, VDD_RAW(1500) },

Is this for sense? Just wondering...
Sent from my HTC Desire Z using XDA Premium App

lainvalenajr said:
Is this for sense? Just wondering...
Sent from my HTC Desire Z using XDA Premium App
Click to expand...
Click to collapse
for sense only

m-deejay said:
for sense only
Click to expand...
Click to collapse
Understood.
Sent from my HTC Desire Z using XDA Premium App

Double post...
Sent from my HTC Desire Z using XDA Premium App

Should I use setcpu or oc daemon?

cdsbj6508 said:
Should I use setcpu or oc daemon?
Click to expand...
Click to collapse
use SetCPU or deamon

Still has the orange LED bug.
-Nipqer

Getting constant reboots after install.
*EDIT*
Wiping and trying again.

Mdj kernel for my DZ?!
*dances*

TheDeadCpu said:
Mdj kernel for my DZ?!
*dances*
Click to expand...
Click to collapse
I'm everywhere

So far I have a great perforamance with this kernel.Didnt notice orange led issue. Awesome job. Testing ...

Awww sense only? Had me all excited lol... oh well I guess ill install a sense based rom and give this kernel a shot!!
Sent from my Htcclay's SuperCM7 G2 using XDA App

Thanks for the kernel, it works pretty sweet with the stock 2.30.405.1 test leak.
One question: how can I use the 2 way call recording feature?

m-deejay said:
I'm everywhere
Click to expand...
Click to collapse
awesome release m-deejay.... i have been waiting so so so long for a sense kernel with smartass governor in desire Z section.... great yo finally have it ... one question though.... is there anyway i can make the smartass governor default governor. without using setcpu or any other program that has to run after phone is booted up
i wanna keep all the stock settings and clock speed of the kernel provided by you . i just wanna change the default governor from ondemand to smartass
can you provide me with a small file or script for that ? or tell me which file to modify

ionut.micu said:
One question: how can I use the 2 way call recording feature?
Click to expand...
Click to collapse
CallRecorder or rVoix apps

Не пашет братан
Wiped dalvik, flashed, locks up after few mins tested on insertcoin_vision sense 2.1+ 3 (1.5) . Tried on smartass n ondemand, 7xx-17xx MHz, didn't feel like trying any others ,went back to rmk's 3.0.1 kernel......Вот жопа

Hello,
I installed it and all seems ok
Thanks for the great job

added Kineto GAN to next release...
soon...

alarm manager wakelock battery drain help!

so I just installed BetterBatteryStats and under wakelock the culprit is alarm manager. I don't have any alarms on but it keeps turning on how to turn this thing off? thanks
will hit thanks for any helpful answers

Connect your phone to a computer and run this:
Code:
adb shell dumpsys alarm > AlarmDump.txt
or download GScript lite and create the following script:
Code:
cd /sdcard
dumpsys alarm > AlarmDump.txt
Note that you probably need root access for the GScript to work. The AlarmDump.txt file will be on your sdcard root directory.

Try installing startup cleaner 2 or similar to stop it starting at boot. Or uninstall it
Sent from my Desire HD using XDA Premium App

It is not really advisable to uninstall AlarmManager since it is used by a lot of applications and by android itself. Not sure you even can uninstall it.
ANywas, getting that dump file I mentioned above will show you what app was causing the most wakeups, and then you can take actions from there.

O sorry i didnt realize you meant alarm manager was a system app.
You can uninstall it using root but not a good idea.
I have not heard of this causing battery drain though.
Sent from my Desire HD using XDA Premium App

It can cause drain, but its not the AlarmManager in it self that is causing it, its the other apps that use it. Other apps use it to wake up on specific times or intervals, like if you have a weather widget that needs updating every 30 min or an application that checks your location every x min etc. Here are parts of my own AlarmManager dump and you might get the idea what I mean:
Code:
Alarm Stats:
com.google.android.gsf
20993ms running, 75 wakeups
4 alarms: act=com.google.android.intent.action.GTALK_RECONNECT flg=0x4
42 alarms: flg=0x4
29 alarms: act=com.google.android.intent.action.GTALK_HEARTBEAT flg=0x4
se.f1nally.snowstorm
547ms running, 11 wakeups
11 alarms: act=se.f1nally.yrvader.UPDATE_ALL flg=0x4 cmp=se.f1nally.snowstorm/.UpdateService
com.mobitobi.android.gentlealarm
2128ms running, 11 wakeups
11 alarms: act=com.mobitobi.android.gentlealarm.ALARM_ALERT flg=0x4
com.jb.gosms
45ms running, 1 wakeups
1 alarms: act=com.jb.schedule.private.box flg=0x4
com.blizzard.bma
2061402ms running, 0 wakeups
2611 alarms: act=android.appwidget.action.APPWIDGET_UPDATE flg=0x4
android
809072ms running, 281 wakeups
1 alarms: act=android.intent.action.DATE_CHANGED flg=0x20000004
9 alarms: act=com.android.internal.policy.impl.PhoneWindowManager.DELAYED_KEYGUARD flg=0x4
1138 alarms: act=android.intent.action.TIME_TICK flg=0x40000004
123 alarms: act=com.android.server.ThrottleManager.action.POLL flg=0x4
19 alarms: act=android.app.backup.intent.RUN flg=0x40000004
80 alarms: act=android.appwidget.action.APPWIDGET_UPDATE flg=0x4
173 alarms: act=android.content.syncmanager.SYNC_ALARM flg=0x4
com.liato.bankdroid
443ms running, 6 wakeups
6 alarms: flg=0x4 cmp=com.liato.bankdroid/.appwidget.AutoRefreshService
com.google.android.apps.maps
804ms running, 43 wakeups
43 alarms: flg=0x4 cmp=com.google.android.apps.maps/com.google.googlenav.prefetch.android.PrefetcherService
com.viber.voip
164775ms running, 618 wakeups
617 alarms: act=com.viber.voip.action.KEEP_ALIVE_RECEIVE flg=0x4
1 alarms: act=com.viber.voip.action.VERSION_CHECK flg=0x4
net.dinglisch.android.tasker
14114ms running, 104 wakeups
90 alarms: act=net.dinglisch.android.tasker.ANOFFCHECKORUM flg=0x4
14 alarms: act=net.dinglisch.android.tasker.ALARUM flg=0x4
de.devmil.minimaltext
6619ms running, 0 wakeups
64 alarms: act=updatetasker dat=minimaltextwidget://widget/id/updatetasker flg=0x4 cmp=de.devmil.minimaltext/.MinimalTextUpdateService
249 alarms: act=update dat=minimaltextwidget://widget/id/update flg=0x4 cmp=de.devmil.minimaltext/.MinimalTextUpdateService
59 alarms: act=forceupdate dat=minimaltextwidget://widget/id/forceupdate flg=0x4 cmp=de.devmil.minimaltext/.MinimalTextUpdateService
3 alarms: act= dat=minimaltextwidget:/weather/ flg=0x4 cmp=de.devmil.minimaltext/.weather.WeatherUpdateService
3 alarms: act=ForceUpdate dat=minimaltextwidget:/weather/ForceUpdate flg=0x4 cmp=de.devmil.minimaltext/.weather.WeatherUpdateService
org.koxx.pure_calendar
29ms running, 5 wakeups
5 alarms: act=org.koxx.pure_calendar.UPDATE_ALL flg=0x4 cmp=org.koxx.pure_calendar/.UpdateService
com.bigtincan.android.adfree
11231ms running, 1 wakeups
1 alarms: flg=0x4
It is part of the android os so thats why I dont think you can uninstall it. See this page for dev info on AlarmManager.

Ghazkul said:
Connect your phone to a computer and run this:
Code:
adb shell dumpsys alarm > AlarmDump.txt
or download GScript lite and create the following script:
Code:
cd /sdcard
dumpsys alarm > AlarmDump.txt
Note that you probably need root access for the GScript to work. The AlarmDump.txt file will be on your sdcard root directory.
Click to expand...
Click to collapse
where can i find the AlarmDump.txt on my computer?

kyo_udon said:
where can i find the AlarmDump.txt on my computer?
Click to expand...
Click to collapse
It will be in the root of your SDcard

Ghazkul said:
It can cause drain, but its not the AlarmManager in it self that is causing it, its the other apps that use it. Other apps use it to wake up on specific times or intervals, like if you have a weather widget that needs updating every 30 min or an application that checks your location every x min etc. Here are parts of my own AlarmManager dump and you might get the idea what I mean:
Code:
Alarm Stats:
com.google.android.gsf
20993ms running, 75 wakeups
4 alarms: act=com.google.android.intent.action.GTALK_RECONNECT flg=0x4
42 alarms: flg=0x4
29 alarms: act=com.google.android.intent.action.GTALK_HEARTBEAT flg=0x4
se.f1nally.snowstorm
547ms running, 11 wakeups
11 alarms: act=se.f1nally.yrvader.UPDATE_ALL flg=0x4 cmp=se.f1nally.snowstorm/.UpdateService
com.mobitobi.android.gentlealarm
2128ms running, 11 wakeups
11 alarms: act=com.mobitobi.android.gentlealarm.ALARM_ALERT flg=0x4
com.jb.gosms
45ms running, 1 wakeups
1 alarms: act=com.jb.schedule.private.box flg=0x4
com.blizzard.bma
2061402ms running, 0 wakeups
2611 alarms: act=android.appwidget.action.APPWIDGET_UPDATE flg=0x4
android
809072ms running, 281 wakeups
1 alarms: act=android.intent.action.DATE_CHANGED flg=0x20000004
9 alarms: act=com.android.internal.policy.impl.PhoneWindowManager.DELAYED_KEYGUARD flg=0x4
1138 alarms: act=android.intent.action.TIME_TICK flg=0x40000004
123 alarms: act=com.android.server.ThrottleManager.action.POLL flg=0x4
19 alarms: act=android.app.backup.intent.RUN flg=0x40000004
80 alarms: act=android.appwidget.action.APPWIDGET_UPDATE flg=0x4
173 alarms: act=android.content.syncmanager.SYNC_ALARM flg=0x4
com.liato.bankdroid
443ms running, 6 wakeups
6 alarms: flg=0x4 cmp=com.liato.bankdroid/.appwidget.AutoRefreshService
com.google.android.apps.maps
804ms running, 43 wakeups
43 alarms: flg=0x4 cmp=com.google.android.apps.maps/com.google.googlenav.prefetch.android.PrefetcherService
com.viber.voip
164775ms running, 618 wakeups
617 alarms: act=com.viber.voip.action.KEEP_ALIVE_RECEIVE flg=0x4
1 alarms: act=com.viber.voip.action.VERSION_CHECK flg=0x4
net.dinglisch.android.tasker
14114ms running, 104 wakeups
90 alarms: act=net.dinglisch.android.tasker.ANOFFCHECKORUM flg=0x4
14 alarms: act=net.dinglisch.android.tasker.ALARUM flg=0x4
de.devmil.minimaltext
6619ms running, 0 wakeups
64 alarms: act=updatetasker dat=minimaltextwidget://widget/id/updatetasker flg=0x4 cmp=de.devmil.minimaltext/.MinimalTextUpdateService
249 alarms: act=update dat=minimaltextwidget://widget/id/update flg=0x4 cmp=de.devmil.minimaltext/.MinimalTextUpdateService
59 alarms: act=forceupdate dat=minimaltextwidget://widget/id/forceupdate flg=0x4 cmp=de.devmil.minimaltext/.MinimalTextUpdateService
3 alarms: act= dat=minimaltextwidget:/weather/ flg=0x4 cmp=de.devmil.minimaltext/.weather.WeatherUpdateService
3 alarms: act=ForceUpdate dat=minimaltextwidget:/weather/ForceUpdate flg=0x4 cmp=de.devmil.minimaltext/.weather.WeatherUpdateService
org.koxx.pure_calendar
29ms running, 5 wakeups
5 alarms: act=org.koxx.pure_calendar.UPDATE_ALL flg=0x4 cmp=org.koxx.pure_calendar/.UpdateService
com.bigtincan.android.adfree
11231ms running, 1 wakeups
1 alarms: flg=0x4
It is part of the android os so thats why I dont think you can uninstall it. See this page for dev info on AlarmManager.
Click to expand...
Click to collapse
I have/had the same problem with that service, but after i read your post, i remembered that my Facebook, G+ and RSS feed is set to update every hour. Solution? Update manually from now on

My AlarmDump. How to interpret?
I was hoping someone can take a look at this dump and help me interpret? My battery life sucks and AlarmManager was the highest at 1 hr 1 min of partial wakelocks as reported by Better Battery Stats.
Not sure I am reading this log right, but I'm guessing we want the lower the # of wake locks the better, but the total running time for those # of wakeups is probably more important I am assuming. So "com.amazon.venezia" with 410ms running and 24 wakeups is probably using LESS battery than the "com.xfinity.tv" with 498ms running and 1 wakeups. Does that sound about right?
My dump is here since it was too big for this url:
justpaste.it/alarmdumptxt

Can you give me help in interpreting this? Just point which parts are of importance and why, maybe give a hint of how do reduce the load by Alarm.
This might be an example for others too.
Code:
Current Alarm Manager state:
Realtime wakeup (now=2012-03-26 10:13:59):
RTC_WAKEUP #17: Alarm{4095c618 type 0 com.google.android.gsf}
type=0 when=+4d3h27m53s60ms repeatInterval=596271000 count=0
operation=PendingIntent{4097f250: PendingIntentRecord{40904180 com.google.android.gsf broadcastIntent}}
RTC_WAKEUP #16: Alarm{4090c788 type 0 com.google.android.gsf}
type=0 when=+4d3h27m53s60ms repeatInterval=596271000 count=0
operation=PendingIntent{4092eed8: PendingIntentRecord{4094c838 com.google.android.gsf broadcastIntent}}
RTC_WAKEUP #15: Alarm{40a44320 type 0 com.google.android.gsf}
type=0 when=+4d3h27m53s60ms repeatInterval=596271000 count=0
operation=PendingIntent{40a33410: PendingIntentRecord{40a31cb8 com.google.android.gsf broadcastIntent}}
RTC_WAKEUP #14: Alarm{4092df20 type 0 com.google.android.gsf}
type=0 when=+4d3h27m53s60ms repeatInterval=596271000 count=0
operation=PendingIntent{4058e368: PendingIntentRecord{40574b10 com.google.android.gsf broadcastIntent}}
RTC_WAKEUP #13: Alarm{40a05f90 type 0 com.google.android.gsf}
type=0 when=+4d3h27m53s60ms repeatInterval=596271000 count=0
operation=PendingIntent{409bc5e8: PendingIntentRecord{40a05f18 com.google.android.gsf broadcastIntent}}
RTC_WAKEUP #12: Alarm{407b7f68 type 0 com.google.android.gsf}
type=0 when=+4d3h27m53s60ms repeatInterval=596271000 count=0
operation=PendingIntent{4095e550: PendingIntentRecord{40a2ecc8 com.google.android.gsf broadcastIntent}}
RTC_WAKEUP #11: Alarm{4092a308 type 0 com.google.android.gsf}
type=0 when=+4d3h27m53s60ms repeatInterval=596271000 count=0
operation=PendingIntent{405ab6a0: PendingIntentRecord{4094a640 com.google.android.gsf broadcastIntent}}
RTC_WAKEUP #10: Alarm{4098bae0 type 0 com.google.android.gsf}
type=0 when=+4d3h27m53s60ms repeatInterval=596271000 count=0
operation=PendingIntent{40928c30: PendingIntentRecord{40b34878 com.google.android.gsf broadcastIntent}}
RTC_WAKEUP #9: Alarm{40b2a8c0 type 0 com.google.android.gsf}
type=0 when=+4d3h27m53s60ms repeatInterval=596271000 count=0
operation=PendingIntent{40a03590: PendingIntentRecord{40a589f8 com.google.android.gsf broadcastIntent}}
RTC_WAKEUP #8: Alarm{40a32220 type 0 com.google.android.gsf}
type=0 when=+4d3h27m53s60ms repeatInterval=596271000 count=0
operation=PendingIntent{407ca930: PendingIntentRecord{40a321a8 com.google.android.gsf broadcastIntent}}
RTC_WAKEUP #7: Alarm{409a1c20 type 0 com.google.android.gsf}
type=0 when=+4d3h27m53s60ms repeatInterval=596271000 count=0
operation=PendingIntent{40aa09b0: PendingIntentRecord{40acd310 com.google.android.gsf broadcastIntent}}
RTC_WAKEUP #6: Alarm{40bc03c0 type 0 com.google.android.gsf}
type=0 when=+4d3h27m53s60ms repeatInterval=596271000 count=0
operation=PendingIntent{409f6e20: PendingIntentRecord{40bc0348 com.google.android.gsf broadcastIntent}}
RTC_WAKEUP #5: Alarm{4099a7d0 type 0 com.google.android.gsf}
type=0 when=+4d3h27m53s60ms repeatInterval=596271000 count=0
operation=PendingIntent{405bce00: PendingIntentRecord{40b842f0 com.google.android.gsf broadcastIntent}}
RTC_WAKEUP #4: Alarm{409a56f0 type 0 com.android.vending}
type=0 when=+12h5m50s99ms repeatInterval=0 count=0
operation=PendingIntent{4086d2d8: PendingIntentRecord{40bf6218 com.android.vending startService}}
RTC_WAKEUP #3: Alarm{40be64b8 type 0 com.android.providers.calendar}
type=0 when=+59m18s164ms repeatInterval=0 count=0
operation=PendingIntent{409c06f8: PendingIntentRecord{40be6440 com.android.providers.calendar broadcastIntent}}
RTC_WAKEUP #2: Alarm{4097c0a8 type 0 com.carl.tcpro}
type=0 when=+56m43s378ms repeatInterval=0 count=0
operation=PendingIntent{409829a0: PendingIntentRecord{40931070 com.carl.tcpro broadcastIntent}}
RTC_WAKEUP #1: Alarm{40a1a148 type 0 com.google.android.gsf}
type=0 when=+12m39s711ms repeatInterval=1800000 count=0
operation=PendingIntent{40862d48: PendingIntentRecord{409270e0 com.google.android.gsf broadcastIntent}}
RTC_WAKEUP #0: Alarm{40adda38 type 0 ccc71.bmw.pro}
type=0 when=+51s501ms repeatInterval=60000 count=1
operation=PendingIntent{4096db50: PendingIntentRecord{408dc0c0 ccc71.bmw.pro broadcastIntent}}
RTC #1: Alarm{40a18a10 type 1 android}
type=1 when=+1h46m0s382ms repeatInterval=0 count=0
operation=PendingIntent{407a5be8: PendingIntentRecord{4082f728 android broadcastIntent}}
RTC #0: Alarm{40868118 type 1 android}
type=1 when=+382ms repeatInterval=0 count=0
operation=PendingIntent{407cc4a8: PendingIntentRecord{40794130 android broadcastIntent}}
Elapsed realtime wakeup (now=+1d19h4m25s877ms):
ELAPSED_WAKEUP #8: Alarm{409b9610 type 2 android}
type=2 when=+4d19h7m48s886ms repeatInterval=0 count=0
operation=PendingIntent{4082ea00: PendingIntentRecord{4084f700 android broadcastIntent}}
ELAPSED_WAKEUP #7: Alarm{4088fe08 type 2 android}
type=2 when=+26m6s381ms repeatInterval=1800000 count=1
operation=PendingIntent{40861368: PendingIntentRecord{4088fd90 android broadcastIntent}}
ELAPSED_WAKEUP #6: Alarm{409b3a38 type 2 tv.dailyme.android}
type=2 when=+14m45s126ms repeatInterval=0 count=0
operation=PendingIntent{4098c660: PendingIntentRecord{40a1a7d0 tv.dailyme.android startService}}
ELAPSED_WAKEUP #5: Alarm{405c45a0 type 2 com.google.android.apps.maps}
type=2 when=+11m6s381ms repeatInterval=900000 count=0
operation=PendingIntent{409f7738: PendingIntentRecord{40a37f48 com.google.android.apps.maps startService}}
ELAPSED_WAKEUP #4: Alarm{409b6658 type 2 com.google.android.gsf}
type=2 when=+10m53s906ms repeatInterval=0 count=0
operation=PendingIntent{405d77e0: PendingIntentRecord{409b65e0 com.google.android.gsf broadcastIntent}}
ELAPSED_WAKEUP #3: Alarm{408e0b58 type 2 de.avm.android.laborapp}
type=2 when=+6m56s119ms repeatInterval=0 count=0
operation=PendingIntent{4099b3f0: PendingIntentRecord{4094a1e8 de.avm.android.laborapp broadcastIntent}}
ELAPSED_WAKEUP #2: Alarm{40a21b68 type 2 getjar.android.client}
type=2 when=+6m23s400ms repeatInterval=600000 count=1
operation=PendingIntent{408b0638: PendingIntentRecord{40a21af0 getjar.android.client startService}}
ELAPSED_WAKEUP #1: Alarm{40b02f38 type 2 org.forcas.netstat}
type=2 when=+45s45ms repeatInterval=120000 count=1
operation=PendingIntent{40ac23b8: PendingIntentRecord{40a2bc38 org.forcas.netstat broadcastIntent}}
ELAPSED_WAKEUP #0: Alarm{40a12ab0 type 2 de.avm.android.laborapp}
type=2 when=+41s449ms repeatInterval=0 count=0
operation=PendingIntent{40797118: PendingIntentRecord{40bba158 de.avm.android.laborapp broadcastIntent}}
ELAPSED #3: Alarm{40a7a2c0 type 3 android}
type=3 when=+30d13h45m57s978ms repeatInterval=0 count=0
operation=PendingIntent{40829828: PendingIntentRecord{4086bd30 android broadcastIntent}}
ELAPSED #2: Alarm{40a5f600 type 3 com.ebomike.ebobirthday}
type=3 when=+58m44s416ms repeatInterval=0 count=0
operation=PendingIntent{409620a8: PendingIntentRecord{40a3cd20 com.ebomike.ebobirthday startService}}
ELAPSED #1: Alarm{40bde040 type 3 android}
type=3 when=+6m48s126ms repeatInterval=0 count=0
operation=PendingIntent{4088ee20: PendingIntentRecord{4086bc58 android broadcastIntent}}
ELAPSED #0: Alarm{409ee130 type 3 ccc71.pmw.pro}
type=3 when=+964ms repeatInterval=10000 count=1
operation=PendingIntent{40be7bc0: PendingIntentRecord{40705900 ccc71.pmw.pro broadcastIntent}}
Broadcast ref count: 0
Alarm Stats:
ccc71.pmw.pro
66820ms running, 0 wakeups
1427 alarms: flg=0x4
ccc71.bmw.pro
68780ms running, 2586 wakeups
2586 alarms: flg=0x4
android
193673ms running, 99 wakeups
1 alarms: act=android.intent.action.DATE_CHANGED flg=0x20000004
2544 alarms: act=android.intent.action.TIME_TICK flg=0x40000004
256 alarms: act=com.android.server.ThrottleManager.action.POLL flg=0x4
86 alarms: act=android.appwidget.action.APPWIDGET_UPDATE flg=0x4
1 alarms: act=android.content.syncmanager.SYNC_ALARM flg=0x4
1 alarms: act=com.android.server.ThorottleManager.action.RESET flg=0x4
12 alarms: act=com.android.internal.policy.impl.KeyguardViewMediator.DELAYED_KEYGUARD flg=0x4
de.avm.android.laborapp
1380ms running, 67 wakeups
67 alarms: flg=0x4
com.google.android.apps.maps
989ms running, 85 wakeups
85 alarms: flg=0x4 cmp=com.google.android.apps.maps/com.google.googlenav.prefetch.android.PrefetcherService
tv.dailyme.android
581ms running, 44 wakeups
44 alarms: flg=0x4 cmp=tv.dailyme.android/.util.download.DownloadService
org.forcas.netstat
52392ms running, 1302 wakeups
1302 alarms: flg=0x4
getjar.android.client
2801ms running, 259 wakeups
259 alarms: flg=0x4 cmp=getjar.android.client/.global.DoStatReceiver
com.google.android.gsf
7929ms running, 171 wakeups
86 alarms: flg=0x4
8 alarms: act=com.google.android.intent.action.GTALK_RECONNECT flg=0x4
77 alarms: act=com.google.android.intent.action.GTALK_HEARTBEAT flg=0x4
com.android.vending
119ms running, 12 wakeups
3 alarms: flg=0x4 cmp=com.android.vending/com.google.android.finsky.services.DailyHygiene
9 alarms: flg=0x4 cmp=com.android.vending/com.google.android.finsky.services.ContentSyncService
com.ebomike.ebobirthday
765ms running, 0 wakeups
1 alarms: dat=custom://144190064 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
1 alarms: dat=custom://93733139 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
1 alarms: dat=custom://32458777 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
1 alarms: dat=custom://18057403 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
1 alarms: dat=custom://46870974 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
1 alarms: dat=custom://3652773 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
1 alarms: dat=custom://10856123 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
1 alarms: dat=custom://140590043 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
1 alarms: dat=custom://21657426 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
1 alarms: dat=custom://72078163 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
1 alarms: dat=custom://90129065 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
1 alarms: dat=custom://75678207 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
1 alarms: dat=custom://68478103 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
1 alarms: dat=custom://100934060 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
1 alarms: dat=custom://79279000 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
1 alarms: dat=custom://126164095 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
1 alarms: dat=custom://97334034 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
1 alarms: dat=custom://136964376 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
1 alarms: dat=custom://50472017 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
1 alarms: dat=custom://86529016 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
1 alarms: dat=custom://133364133 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
1 alarms: dat=custom://39659122 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
1 alarms: dat=custom://147790087 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
1 alarms: dat=custom://64876017 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
1 alarms: dat=custom://28858526 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
1 alarms: dat=custom://129764113 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
1 alarms: dat=custom://151390113 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
1 alarms: dat=custom://122564081 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
1 alarms: dat=custom://104534229 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
1 alarms: dat=custom://61275992 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
1 alarms: dat=custom://108134289 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
1 alarms: dat=custom://82886009 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
1 alarms: dat=custom://14456146 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
1 alarms: dat=custom://115363961 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
1 alarms: dat=custom://118964053 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
1 alarms: dat=custom://52208 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
1 alarms: dat=custom://43259213 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
1 alarms: dat=custom://36059036 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
1 alarms: dat=custom://54072054 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
1 alarms: dat=custom://25257674 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
1 alarms: dat=custom://111735023 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
1 alarms: dat=custom://57672097 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
1 alarms: dat=custom://7256099 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
com.android.providers.calendar
451ms running, 1 wakeups
1 alarms: act=com.android.providers.calendar.SCHEDULE_ALARM flg=0x4
com.carl.tcpro
15596ms running, 44 wakeups
44 alarms: act=com.carl.tcpro.UPDATE_RUN flg=0x4
com.lsdroid.cerberus
11ms running, 1 wakeups
1 alarms: act=com.google.android.c2dm.intent.REGISTER flg=0x4
From my little knowledge I would assume the first part is not important, but the Alarm Stats, and there this with most running time as "com.carl.tcpro" at the very end. But what I can do with this?
BTW: In this overnight test, most time the phone was in flight mode.
Thanks

I'm in the same boat of trying to interpret mine, so I'm not an expert...
IMO, the most important part is the "Time Running", and nothing looks too bad in yours. Since everything is in ms, even that com.carl.tcpro only ran for 15 seconds.
Does anyone know how to reset the Alarm Manager log? Mine seems to be covering like 54 days.
Also, a breakdown of what some of the most important definitions are:
"RTC_WAKEUP"
"type"
RTC #X
ELAPSED_WAKEUP #X
ELAPSED #X
etc...
Thanks!

android.intent.action.TIME_TICK
what is that? in the above posted it showed 1,000 alarms
its that not high on mine, but pretty high
exactly what is android.intent.action.TIME_TICK ?

just for everybody knowledge.
i've recently solved this problem on my sg2 aswell.
but for me the only thing that helped was flashing an old bootloader.
i was on the new ics bootloader until somehow i saw on my system info that my bootloader is unknown. i've also couldnt get the jig working, so i thought why not try to flash the old bootloader.
and yes!!!! finally the alarmManager is no longer on the toplist of BBS's partial wakelocks. and the phone is finally entering deepsleep mode whenever i turnoff the screen.

Hey,
I also have problems with the alarmmanager. A month ago my phones battery was 65% after 3 days, today I'm lucky if I have enough battery left to do a phone call at the end of a day. The last few days I really read a lot about battery draining and I think it is the alarmmanager causing the problems.
The problem is, I have a Motorola Defy mini and this phone is not rootable to get the alarmmanagers dump: http://forum.xda-developers.com/showthread.php?t=1658568&page=11
So I have no idea how to solve the problems with my phone. Do you know what I could do?

Ghazkul said:
Connect your phone to a computer and run this:
Code:
adb shell dumpsys alarm > AlarmDump.txt
or download GScript lite and create the following script:
Code:
cd /sdcard
dumpsys alarm > AlarmDump.txt
Note that you probably need root access for the GScript to work. The AlarmDump.txt file will be on your sdcard root directory.
Click to expand...
Click to collapse
Im trying to do it through the terminal emulator per the second command, but get a permission denied error in the alarmdump.txt file... any idea why?
(samsung galxy S running CM9)

ap1618 said:
Im trying to do it through the terminal emulator per the second command, but get a permission denied error in the alarmdump.txt file... any idea why?
(samsung galxy S running CM9)
Click to expand...
Click to collapse
Before typing in commands, type in "su", you need to give it access to root.

(Delete)

Ghazkul said:
Connect your phone to a computer and run this:
Code:
adb shell dumpsys alarm > AlarmDump.txt
or download URL and create the following script:
Code:
cd /sdcard
dumpsys alarm > AlarmDump.txt
Note that you probably need root access for the GScript to work. The AlarmDump.txt file will be on your sdcard root directory.
Click to expand...
Click to collapse
I executed adb shell dumpsys alarm > AlarmDump.txt, but i can't find AlarmDump.txt on root of my sdcard... What did I do wrong??

Can anybody help with this alarm dump:
Alarm Stats:
com.google.android.location
22ms running, 3 wakeups
3 alarms: act=com.google.android.location.ALARM_WAKEUP_LOCATOR flg=0x4
com.google.android.gsf
2899ms running, 141 wakeups
10 alarms: act=com.google.android.intent.action.GTALK_RECONNECT flg=0x4
3 alarms: flg=0x4
5 alarms: act=com.google.android.intent.action.GTALK_HEARTBEAT flg=0x4
123 alarms: flg=0x4 cmp=com.google.android.gsf/.checkin.EventLogService$Receiver
com.android.jrdfota
306ms running, 2 wakeups
2 alarms: act=com.android.jrdfota.TIME_NOTIFY_CHECK_VER flg=0x4
com.android.vending
592ms running, 23 wakeups
10 alarms: flg=0x4 cmp=com.android.vending/com.google.android.finsky.services.DailyHygiene
13 alarms: flg=0x4 cmp=com.android.vending/com.google.android.finsky.services.ContentSyncService
android
133548ms running, 217 wakeups
3 alarms: act=android.intent.action.DATE_CHANGED flg=0x30000004
879 alarms: act=android.intent.action.TIME_TICK flg=0x40000004
209 alarms: act=com.android.server.ThrottleManager.action.POLL flg=0x4
2 alarms: act=android.app.backup.intent.INIT flg=0x4
187 alarms: act=android.appwidget.action.APPWIDGET_UPDATE flg=0x4
6 alarms: act=com.android.internal.policy.impl.PhoneWindowManager.DELAYED_KEYGUARD flg=0x4
19 alarms: act=android.app.backup.intent.RUN flg=0x40000004
3 alarms: act=android.content.syncmanager.SYNC_ALARM flg=0x4
com.mx.browser
3271ms running, 51 wakeups
51 alarms: act=com.mx.service.SYNC_MXFAV flg=0x4
com.google.android.apps.maps
275ms running, 5 wakeups
5 alarms: act=com.google.android.apps.maps.nlp.ALARM_WAKEUP_CACHE_UPDATER flg=0x4
com.vp.alarmClockPlusDock
443ms running, 2 wakeups
2 alarms: act=com.vp.alarmClockPlusDock.ALARM_ALERT flg=0x4

[Q] Does not enter in sleep mode

I have the stock 4.0.4 rooted, I've left on at night while sleeping and I have most of the time active terminal, I do not understand why if I have coverage, the telephone have 55% of usage, but the battery drops from 82% to 76%
Please if someone could help me, I'm going crazy with this issue
I deleted the following applications of the original rom
ApplicationsProvider.apk
BackupRestoreConfirmation.apk
Bluetooth.apk
BooksTablet.apk
CertInstaller.apk
ChromeBookmarksSyncAdapter.apk
DrmProvider.apk
EmailGoogle.apk
ExchangeGoogle.apk
FaceLock.apk
GenieWidget.apk
GoogleBackupTransport.apk
GoogleEarth.apk
GoogleFeedback.apk
GooglePartnerSetup.apk
GoogleQuickSearchBox.apk
GoogleTTS.apk
HoloSpiralWallpaper.apk
HTMLViewer.apk
KeyChain.apk
LatinImeDictionaryPack.apk
LiveWallpapers.apk
LiveWallpapersPicker.apk
Maps.apk
MediaUploader.apk
Microbes.apk
Music2.apk
MusicFX.apk
NetworkLocation.apk
Nfc.apk
NoiseField.apk
OneTimeInitializer.apk
PhaseBeam.apk
Phonesky.apk
PlusOne.apk
SharedStorageBackup.apk
SoundRecorder.apk
Stk.apk
Street.apk
TagGoogle.apk
Talk.apk
talkback.apk
Thinkfree.apk
UserDictionaryProvider.apk
VideoEditorGoogle.apk
Videos.apk
VisualizationWallpapers.apk
VoiceDialer.apk
VoiceSearch.apk
VpnDialogs.apk
YouTube.apk
I installed these others in the folder / system / app
ApexLauncher.apk
DeskNotes.apk
Gallery.apk (without picasa Sync)
Gmail.apk
LightFlow.apk
Lock.apk (Screen off and lock)
Music.apk (PlayerPro Music Player)
RootExplorer.apk
Twitter.apk
Vending.apk
WeatherPro.apk
WhatsApp.apk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://dl.dropbox.com/u/19157944/Screenshot_2012-04-18-07-15-31.png
and the battery gives me the following stat
===================
General Information
===================
BetterBatteryStats version: 1.7.1.0
Creation Date: 2012-04-18 07:22:57
Statistic Type: (3)
Since 4 m 11 s
VERSION.RELEASE: 4.0.4
BRAND: google
DEVICE: maguro
MANUFACTURER: samsung
MODEL: Galaxy Nexus
RADIO: unknown
BOOTLOADER: PRIMELA03
FINGERPRINT: google/yakju/maguro:4.0.4/IMM76D/299849:user/release-keys
HARDWARE: tuna
ID: IMM76D
Rooted: true
===========
Other Usage
===========
Awake (): 4 m 11 s (251 s) Ratio: 100,0%
Screen On (): 1 m 12 s (72 s) Ratio: 28,6%
=========
Wakelocks
=========
Checkin Service (Servicios de Google): 2 m 20 s (140 s) Count:21 55,9%
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Servicios de Google): 1 m 10 s (70 s) Count:17 27,8%
RILJ (Teléfono): 8 s (8 s) Count:33 3,3%
GpsLocationProvider (Sistema Android): 6 s (6 s) Count:31 2,6%
sleep_broadcast (Sistema Android): 3 s (3 s) Count:33 1,4%
ActivityManager-Launch (Sistema Android): 2 s (2 s) Count:30 1,2%
AudioOut_1 (1013): 2 s (2 s) Count:1 1,1%
================
Kernel Wakelocks
================
No reference since unplugged set yet (): (0 s) Cntc/wc/ec)1/1/1 100,0%
=========
Processes
=========
system (Sistema Android): Sys: (0 s) Us: (0 s) Starts: 0
======================
Alarms (requires root)
======================
No reference since unplugged set yet (): Wakeups: 0
========
Services
========
Active since: The time when the service was first made active, either by someone starting or binding to it.
Last activity: The time when there was last activity in the service (either explicit requests to start it or clients binding to it)
See http://developer.android.com/reference/android/app/ActivityManager.RunningServiceInfo.html
com.whatsapp (com.whatsapp.ExternalMediaManager)
Active since: 27 s
Last activity: 27 s
Crash count:0
com.android.phone (com.android.phone.BluetoothHeadsetService)
Active since: 20 s
Last activity: 20 s
Crash count:0
fr.clockwidget.lpsense (fr.clockwidget.lpsense.UpdateService)
Active since: 27 s
Last activity: 28 s
Crash count:0
com.android.systemui (com.android.systemui.ImageWallpaper)
Active since: 19 s
Last activity: 19 s
Crash count:0
com.android.vending (com.google.android.finsky.services.DailyHygiene)
Active since: 4 m 12 s
Last activity: 4 m 12 s
Crash count:0
com.android.systemui (com.android.systemui.SystemUIService)
Active since: 18 s
Last activity: 18 s
Crash count:0
com.google.process.gapps (com.google.android.gsf.gtalkservice.service.GTalkService)
Active since: 35 s
Last activity: 4 m 11 s
Crash count:0
com.rageconsulting.android.lightflow (com.rageconsulting.android.lightflow.service.MainRunningService)
Active since: 21 s
Last activity: 28 s
Crash count:0
com.google.android.inputmethod.latin (com.android.inputmethod.latin.LatinIME)
Active since: 20 s
Last activity: 20 s
Crash count:0
com.whatsapp (com.whatsapp.messaging.MessageService)
Active since: 25 s
Last activity: 3 m 42 s
Crash count:0
com.google.process.gapps (com.google.android.gsf.checkin.CheckinService)
Active since: 4 m 28 s
Last activity: 4 m 28 s
Crash count:0

Your better battery stats log is only four and half minutes long, it doesn't match the time period you have screenshots for. I think you may have hit the "set custom ref" button when you were taking these readings or otherwise reset the recording.
While you do clearly have a wakelock issue of some sort (needs a full log to diagnose), it doesn't seem to be introducing a lot of battery drain. 6% over 7 hours is pretty great for idle drain.
Also, each entry in your battery usage is % of the amount drained, not your total battery. For these stats, you're down to 76%, so you've drained 24%.
-"Dispositivo inactivo" is the amount your phone uses to maintain its signal and power the radios. It's used 22% of 24%, so about 5% of your battery.
-"Telefono inactivo" has used 50% of 24%, or 12% of the battery.

Thanks for your response, ups, my battery stats log is only four and half minutes long, you are right, sorry for the mistake.
Yesterday I make a full restore image from google 4.0.4 and a full wipe and delete the following app of my /system/app
ApplicationsProvider.apk
BackupRestoreConfirmation.apk
Bluetooth.apk
BooksTablet.apk
CertInstaller.apk
ChromeBookmarksSyncAdapter.apk
DrmProvider.apk
EmailGoogle.apk
ExchangeGoogle.apk
FaceLock.apk
GenieWidget.apk
GoogleBackupTransport.apk
GoogleEarth.apk
GoogleFeedback.apk
GooglePartnerSetup.apk
GoogleQuickSearchBox.apk
GoogleTTS.apk
HoloSpiralWallpaper.apk
HTMLViewer.apk
KeyChain.apk
LatinImeDictionaryPack.apk
LiveWallpapers.apk
LiveWallpapersPicker.apk
Maps.apk
MediaUploader.apk
Microbes.apk
Music2.apk
MusicFX.apk
NetworkLocation.apk
Nfc.apk
NoiseField.apk
OneTimeInitializer.apk
PhaseBeam.apk
Phonesky.apk
PlusOne.apk
SharedStorageBackup.apk
SoundRecorder.apk
Stk.apk
Street.apk
TagGoogle.apk
Talk.apk
talkback.apk
Thinkfree.apk
UserDictionaryProvider.apk
VideoEditorGoogle.apk
Videos.apk
VisualizationWallpapers.apk
VoiceDialer.apk
VoiceSearch.apk
VpnDialogs.apk
YouTube.apk
and my stats are attached, and here are the battery stats of tonight
===================
General Information
===================
BetterBatteryStats version: 1.7.1.0
Creation Date: 2012-04-19 08:02:22
Statistic Type: (3)
Since 7 h 38 m 1 s
VERSION.RELEASE: 4.0.4
BRAND: google
DEVICE: maguro
MANUFACTURER: samsung
MODEL: Galaxy Nexus
RADIO: unknown
BOOTLOADER: PRIMELA03
FINGERPRINT: google/yakju/maguro:4.0.4/IMM76D/299849:user/release-keys
HARDWARE: tuna
ID: IMM76D
Rooted: true
===========
Other Usage
===========
Awake (): 6 m 8 s (368 s) Ratio: 1,3%
Screen On (): 2 m 48 s (168 s) Ratio: 0,6%
=========
Wakelocks
=========
AudioOut_1 (1013): 32 s (32 s) Count:8 0,1%
RILJ (Teléfono): 9 s (9 s) Count:65 0,0%
ActivityManager-Launch (Sistema Android): 8 s (8 s) Count:56 0,0%
AlarmManager (Sistema Android): 3 s (3 s) Count:300 0,0%
Checkin Service (Servicios de Google): 1 s (1 s) Count:82 0,0%
SCREEN_FROZEN (Sistema Android): 1 s (1 s) Count:11 0,0%
Event Log Service (Servicios de Google): 1 s (1 s) Count:16 0,0%
================
Kernel Wakelocks
================
No reference since unplugged set yet (): (0 s) Cntc/wc/ec)1/1/1 100,0%
=========
Processes
=========
system (Sistema Android): Sys: (0 s) Us: 1 s (1 s) Starts: 0
======================
Alarms (requires root)
======================
No reference since unplugged set yet (): Wakeups: 0
========
Services
========
Active since: The time when the service was first made active, either by someone starting or binding to it.
Last activity: The time when there was last activity in the service (either explicit requests to start it or clients binding to it)
See http://developer.android.com/reference/android/app/ActivityManager.RunningServiceInfo.html
com.android.phone (com.android.phone.BluetoothHeadsetService)
Active since: 20 s
Last activity: 20 s
Crash count:0
com.android.systemui (com.android.systemui.ImageWallpaper)
Active since: 19 s
Last activity: 19 s
Crash count:0
com.android.systemui (com.android.systemui.SystemUIService)
Active since: 18 s
Last activity: 18 s
Crash count:0
com.google.process.gapps (com.google.android.gsf.gtalkservice.service.GTalkService)
Active since: 35 s
Last activity: 5 m 43 s
Crash count:0
com.google.android.inputmethod.latin (com.android.inputmethod.latin.LatinIME)
Active since: 19 s
Last activity: 19 s
Crash count:0
android.process.media (com.android.providers.downloads.DownloadService)
Active since: 19 s
Last activity: 35 s
Crash count:0
Tonight goes from 15% down to 12%, much better than yesterday, but in the graphic the line of active is to much time, maybe it is, as you say, a relative % of total, and that is the reason that the line of active it's to long