Hey,
I´ve got a brand new Elephone P9000 and was wondering about the high battery consumption in idle mode. So I connected the phone to the Android Device Monitor and I wondered why they read out some kind of sensor every 200ms.
Code:
05-27 23:54:18.896: D/SettingsInterface(940): from settings cache , name = turn_silent , value = null
05-27 23:54:18.896: D/SettingsInterface(940): from settings cache , name = callsilent , value = null
05-27 23:54:18.896: D/SettingsInterface(940): from settings cache , name = alarmsilent , value = null
05-27 23:54:18.897: D/SettingsInterface(940): from settings cache , name = musicsilent , value = null
05-27 23:54:18.897: D/SettingsInterface(940): from settings cache , name = mediasilent , value = null
05-27 23:54:18.897: I/fanzhuan(940): onSensorChanged front----> -0.106 0.087 9.883
05-27 23:54:19.096: D/SettingsInterface(940): from settings cache , name = turn_silent , value = null
05-27 23:54:19.096: D/SettingsInterface(940): from settings cache , name = callsilent , value = null
05-27 23:54:19.096: D/SettingsInterface(940): from settings cache , name = alarmsilent , value = null
05-27 23:54:19.096: D/SettingsInterface(940): from settings cache , name = musicsilent , value = null
05-27 23:54:19.096: D/SettingsInterface(940): from settings cache , name = mediasilent , value = null
05-27 23:54:19.096: I/fanzhuan(940): onSensorChanged front----> -0.111 0.075 9.894
Could that be an expensive operation that causes the battery drain?
Finger print sensor
Sent from my E6653 using Tapatalk
mrbubba999 said:
Finger print sensor
Sent from my E6653 using Tapatalk
Click to expand...
Click to collapse
Hello everyone, I think the problem of the battery runs out quickly is due only to the data network (3G 4G). For disabling this, even the battery lasts 20 hours (with fingerprint sensor activated, GPS enabled, the display brightness at maximum). On the contrary, in the same conditions but with the activated data network, the battery lasts 7 - 8 hours. Besides the new P9000, for work I use a P8000 that goes to great in all respects). I keep in mind the effects of ROM developers. (Hopefully soon come out an update without these bugs). PS: thanks to google translate )
sorenzo said:
Hello everyone, I think the problem of the battery runs out quickly is due only to the data network (3G 4G). For disabling this, even the battery lasts 20 hours (with fingerprint sensor activated, GPS enabled, the display brightness at maximum). On the contrary, in the same conditions but with the activated data network, the battery lasts 7 - 8 hours. Besides the new P9000, for work I use a P8000 that goes to great in all respects). I keep in mind the effects of ROM developers. (Hopefully soon come out an update without these bugs). PS: thanks to google translate )
Click to expand...
Click to collapse
To me it's exactly the same ! If a disable the sim card the battery life nearly double.
About this update, has an expected release date ?
So the 3G/4G radio is the culprit? But disabling it kind of defeats the point of it being a phone. Unless there's a method of changing the poll interval without it affecting the phones functionality? Maybe a dev can chime in.
Related
The trouble is that as I exit from iGo app it always reset my backlight settings to default state. Whatever settings I set up (automatic backlight on/off), they will be inevitably set to default values by iGo (1 minute before dim). BTW, it does not update settngs if I minimize iGo instead of exit. There is no backlight settings in iGo app other than level of backlight. If anybody knows or guesses what the reason might be please advise
put thin in your sys file
[power]
backlight_sync_with_OS=0
backlight_slow_api=0
backlight_day=100
backlight_night=100
backlight_day_battery=100
backlight_night_battery=100
backlight_manage_values= 1
backlight_max = 10
backlight_min = 1
Backlight reset
Thanks for this. It was a problem I also had, so I will give it a go.
vacis said:
put thin in your sys file
[power]
backlight_sync_with_OS=0
backlight_slow_api=0
backlight_day=100
backlight_night=100
backlight_day_battery=100
backlight_night_battery=100
backlight_manage_values= 1
backlight_max = 10
backlight_min = 1
Click to expand...
Click to collapse
It works. Thanks a much!
So after a week on cm7 i've decided to go back to my zckpa chinese rom. cm7 is not that stable for now, and most of its features i can get with zckpa rom. but the thing that still bugging stock/custom rom based on stock is sod. from my experience its caused by wifi, when the phone get out of known wifi range and it constantly scanning, it get sod. then i found this little app that solve my sod problem. u need to be rooted to try this btw.
1- edit build.prop file, add this line in it
Code:
wifi.supplicant_scan_interval=300
and save it. 300 means 5 minutes, but u can use other value eg 600 which is 10 minutes. by doing this we limit phone scanning wifi interval.
2- install wififixer from market. set it:
"set wifi usability" i use "max battery"
tick on "enable wifi lock"
"wifi sleep policy" to "never"
and i've never got sod for almost a week
btw i dont use android default wifi scanning, i just let wififixer do its job in the background. not just its solve my sods problem, it also gave me stable connection, no constant signal dropping for me now
an0nym0us_ said:
So after a week on cm7 i've decided to go back to my zckpa chinese rom. cm7 is not that stable for now, and most of its features i can get with zckpa rom. but the thing that still bugging stock/custom rom based on stock is sod. from my experience its caused by wifi, when the phone get out of known wifi range and it constantly scanning, it get sod. then i found this little app that solve my sod problem. u need to be rooted to try this btw.
1- edit build.prop file, add this line in it
Code:
wifi.supplicant_scan_interval=300
and save it. 300 means 5 minutes, but u can use other value eg 600 which is 10 minutes. by doing this we limit phone scanning wifi interval.
2- install wififixer from market. set it:
"set wifi usability" i use "max battery"
tick on "enable wifi lock"
"wifi sleep policy" to "never"
and i've never got sod for almost a week
btw i dont use android default wifi scanning, i just let wififixer do its job in the background. not just its solve my sods problem, it also gave me stable connection, no constant signal dropping for me now
Click to expand...
Click to collapse
im still trying to figure out why wifi scanning will cause sod.
well theres another file, /system/etc/firmware/wlan/qcom_cfg.ini which control wifi driver in stock rom. cm doesnt have this. its content is:
Code:
# This file allows user to override the factory
# defaults for the WLAN Driver
# Enable IMPS or not
gEnableImps=1
# Enable/Disable Idle Scan
gEnableIdleScan=0
# Increase sleep duration (seconds) during IMPS
gImpsModSleepTime=600
# Enable BMPS or not
gEnableBmps=1
# Enable suspend or not
# 1: Enable standby, 2: Enable Deep sleep, 3: Enable Mcast/Bcast Filter
gEnableSuspend=3
# Phy Mode (auto, b, g, n, etc)
gDot11Mode=0
# Handoff Enable(1) Disable(0)
gEnableHandoff=0
# CSR Roaming Enable(1) Disable(0)
gRoamingTime=0
# STA MAC Address - This will be used until NV items are in place
# Each byte of MAC address is represented in Hex format as XX
NetworkAddress=000AF58989FF
# UAPSD service interval for VO,VI, BE, BK traffic
InfraUapsdVoSrvIntv=0
InfraUapsdViSrvIntv=0
InfraUapsdBeSrvIntv=0
InfraUapsdBkSrvIntv=0
# Disable RSSI FW filtering
gEnableFWRssiMonitoring=0
# Make 1x1 the default antenna configuration
gNumRxAnt=1
# Beacon filtering frequency (unit in beacon intervals)
gNthBeaconFilter=50
# Enable WAPI or not
WAPIIsEnabled=0
# Flags to filter Mcast abd Bcast RX packets.
# Value 0: No filtering, 1: Filter all Multicast.
# 2: Filter all Broadcast. 3: Filter all Mcast abd Bcast
McastBcastFilter=0
gEnableLogp=1
#SoftAP Related Parameters
# AP MAC address
gAPMacAddr=00deadbeef11
# 802.11n Protection flag
gEnableApProt=1
#Enable/Disable UAPSD for SoftAP
gEnableApUapsd=1
# Fixed Rate
gFixedRate=0
# Maximum Tx power
gTxPowerCap=30
# Fragmentation Threshold
gFragmentationThreshold=2346
# RTS threshold
RTSThreshold=2347
# Intra-BSS forward
gDisableIntraBssFwd=0
# WMM mode: Auto(0) or QBSS(1) or No-QoS(2)
WmmIsEnabled=0
# 802.11d support
g11dSupportEnabled=1
# Country code
gAPCntryCode=USI
#Short Guard Interval Enable/disable
gShortGI20Mhz=1
#Auto Shutdown Value in seconds. A value of 0 means Auto shutoff is disabled
gAPAutoShutOff=0
#Enable OBSS protection
gEnableApOBSSProt=0
# Frames Processing Minimum Threshold
gMinFramesProcThres=0
# Listen Energy Detect Mode Configuration
# Valid values 0-128
# 128 means disable Energy Detect feature
# 0-9 are threshold code and 7 is recommended value from system if feature is to be enabled.
# 10-128 are reserved.
# The EDET threshold mapping is as follows in 3dB step:
# 0 = -60 dBm
# 1 = -63 dBm
# 2 = -66 dBm
# ...
# 7 = -81 dBm
# 8 = -84 dBm
# 9 = -87 dBm
# Note: Any of these settings are valid. Setting 0 would yield the highest power saving (in a noisy environment) at the cost of more range. The range impact is approximately #calculated as:
#
# Range Loss (dB) = EDET threshold level (dBm) + 97 dBm.
#
gEnablePhyAgcListenMode=128
END
# Note: Configuration parser would not read anything past the END marker
but i dont have any slight idea what those value means
I know this thread is repeated everywhere, but I thought I'd start it up for our GNote forums
What are your Tasker profiles? I just found out how to use Tasker yesterday and I find myself loving it.
Mine are as follows:
1) Incoming Calls - Decrease volume to second lowest setting (I have loud friends)
2) Turn wifi on at home automatically
3) Open PowerAmp when headphones are plugged in
4) Send a "Happy Birthday!" text to various people on their birthdays.
5) Alert me when battery is full to 100%. Really useful if you don't want to overcharge your battery.
What about you guys?
Mute at work locations
Pandora + Bluetooth in car
Wifi at home
100% Battery alert
Auto-off unpaired Bluetooth
Regulated auto-sync based on battery
Long-press search changed to notification drawer open
Screen timeout change for various apps
Data off and screen timeout change for ad-supported games
I posted a couple just recently in this thread...
http://forum.xda-developers.com/showpost.php?p=23151996&postcount=25
Here's a C&P for the lazy....
______________________________________________
Car Profile
Enter Task
1) Disable PIN Security so I don't need to unlock my phone while in the car (one less distraction)
2) Set Media Volume to 15
3) Turn Wifi off
4) Change Display timeout to 30 minutes (nice for google maps and viewing the album art of the streaming music)
5) Turn on GPS IF power is connected to phone
6) Start recording video with DailyRoads Voyager ( A car DVR program in case of an accident so you then have Objective evidence)
7) Play the THX sound after a couple seconds to make sure the Bluetooth audio streaming is working right
Car EXIT task
1) Stop Recording Video for DailyRoads Voyager (DRV)
2) Wait 5 seconds
3) Kill App - DRV
4) Perform Task - PIN ON
5) Secure Settings - Disable GPS
6) Display Timeout - 2 min
7) WiFi - Turn ON
8) Bluetooth - Off
9) Display Brightness - Set to 150 out of 255
Other fun stuff
Home VAR %STATUS_HOME
Set VAR for when I am near my home micro-cell as the signal radius is small and specific to my house. I use this since the phone part is always on and I don't need to use GPS to determine location which uses more juice. That VAR is then used to turn on wifi when I arrive at home, disable PIN again, Flash "Welcome home", set WiFi sleep to Never. The Exit task for when I leave home turns PIN ON and sets the WiFi sleep policy to Never While Plugged"
Power VAR %STATUS_POWER
I have 2 seperate profiles for when I am connected to AC or USB power. The AC one sets the power VAR to 2 while the USB one sets it to 1. Both are used for other tasks and profiles, like the car one above requires AC connection so my GPS doesn't drain my battery even while connected. I have it flash "AC connected" or "USB connected" to let me know if the phone is receiving the correct amount of juice. When both of them exit they set the Power VAR to 0 and flash "Power Disconnected"
Sleepy Time
Profile conditions
1) Time - From 00:01 to 06:30
2) State - Home VAR = 1 (so this doesn't happen when I am out and about somewhere at night)
Enter Task - In case I'm tinkering with the phone in bed and don't want to keep the wifey up with a blazing screen and vibrations when clicking buttons. Also prevents annoying sounds at night by disabling data sync and muting all but the Alarm audio.
1) AutoSync -OFF
2) Flash "Good night"
3) Display brightness at 0
4) Screen Filter set to 25%
5) Perform Task - Alarm Audio only
Alarm Audio only task above
1) Alarm Volume - 4
2) Flash "Alarm Audio Only"
3) Haptic Feedback - Off
4) Notification Volume - 0
5) Ringer volume - 0
6) System volume - 0
7) Media volume - 0
Exit Task
1) AutoSync - On
2) Display Brightness - 255
3) Screen Filter - 100%
Quick Stats - This has two parts. One is the Notification that tells me a bunch of info I like to know like Battery level, Screen timeout, screen brightness and CPU govenor. The second part is launching a menu whe nI click on the the notification that has the commonly used Screen brightness & timeouts I use. I need to add some audio options in there too. I re-discovered that menu was there the entire time and didn't see the + button add more items to the menu. Iwas over complicating it by trying to use Scenes as a pop-up menu. Still need to learn more about Scenes.
Part 1 - Quick Stats Notification
State - Orientation Face Up (I use this state so if I want to refresh the stats all I do put the phone face up. There is automatically a time stamp so I can know when the stats were last updated)
Task - Notify Quick Stats
1) Notify - with Battery level, Screen timeout, screen brightness and CPU govenor variables as the text.
Part 2 - Notification Bar Tool
Event - Notification Click
Task - Quick Stats Menu
1) Menu with options for display brightness at 0, 100 or 255. Display timeout options for 30 secs, 2 min, 10 min and 30 min
Remote PIN Disable - This is for in case I forget my pin this will disable the PIN likew used in the Car and Home profiles. It is triggered by receiving a text from certain people with a specific phrase.
Event - Text with specific phrase under Content
Task - PIN OFF
Where Are You - Here's a 3 part setup. If I can't find my phone I again send a text with a specific phrase that then cranks up all volume settings to MAX and repeat "The Most Annoying Sound in the world" by Jim Carrey from Dumb & Dumber. The text sets a VAR called %SHUTUP to 1. When %SHUTUP = 1 it triggers Part 2. Once I find the phone to set the VAR back to 0 I shake the phone.
Part 1 - Where Are You Status
Event - Received Text with specific phrase
Task - Variable Set - %SHUTUP = 1
Part 2 - Where Are You Status
State - Variable Value = 1
Task - Where Are You Audio
1) Perform Task - Crank It Up (sets all volumes to MAX)
2) Flash - "I'm over here!"
3) Music Play - Annoy.wav
4) Wait - 15 sec
5) Goto - Top of Loop IF %SHUTUP = 1
Part 3 -Shutup Shake
Event - Shake
Task
1) Variable Set - %SHUTUP = 0
2) Flash "SHUT UP!!!"
A couple more but they are straight from the Tasker Wiki
I'm definitely going to have to do those. Right now, all I understand is the basics of Tasker (no where near Variables) but I'll follow your instructions.
Thanks especially for "Where are you"
A few I use....
1). Pocket Lock - Detects when phone is upside down in my pocket and activates WidgetLocker.
2). Read Caller Aloud - Incoming caller name said aloud so I can decide whether I want to answer without looking at my phone.
3). Night Mode - From 00:00 to 06:00 Puts phone into silent mode, plus checks whether Wifi, Data, GPS, or Blutooth are on, and turns them off if they are.
4). Battery Low - When battery gets to 15%, and it's not connected to a charger, Says "Battery low, connect charger" and turns off Wifi, BT, Data, GPS.
5). Music Player - When headset is plugged in, loads music app.
6). Home - Gets general location from cell tower, activates Wifi, disables Data & GPS. Exit Task disables Wifi, and enables Data.
7). Work - Gets general location from cell tower, disables Wifi, Data, GPS, BT, and Auto Replies to sms that im working and will reply when i can.
I'm pretty new to tasker, but have been pretty bored lately and have been working on an addition to my Work profile.
This profile will, use variables to save up to 5 peoples numbers and how many times each has txted me, and txt each of them back, using their names from my contact list in the body of each txt.
So lets say BOB txts me once, his number will be added as a variable, and it will begin counting the txts from him. On the first txt he is send a txt saying, something like. "Sorry BOB, im at work, will reply when i can".
Then DAVE txts, he will be assigned to Sender2, and have a txt sent to him like above, with the second Counter and Number (%CNTR2 and %SNDR2).
BOB, realizing it's an auto-reply, decides to be funny and spam txt me, thinking he will get a reply every time. However, tasker counts his incoming txts, (%CNTR1) and when it reaches a value of 10, send just one more txt saying something like (Thats 10 txts you've sent, seems Im still unavailable).
Profile: Auto Reply
Variables:
%SNDR1 <---- BOBs cell number
%SNDR2 <---- DAVEs cell number
%SNDR3
%SNDR4
%SNDR5
%CNTR1 <---- BOBs txt counter
%CNTR2
%CNTR3
%CNTR4
%CNTR5
%TXTVAR <---- Counter determining whether a txt received is from someone new or a number already saved.
Enter Task:
Code:
1). GoTo label Sender1 if %SMSRF ~ %SNDR1
2). GoTo label Sender2 if %SMSRF ~ %SNDR2
3). " " etc.
4).......
5).....
6). If (%SNDR1 ~ 0) then SetVariable %SNDR1 to %SMSRF
7). If (%SNDR2 ~ 0) and (%TXTVAR = 1) then SetVariable %SNDR2 to %SMSRF
8). If (%SNDR3 ~ 0) and (%TXTVAR = 2) then SetVariable %SNDR3 to %SMSRF
9)........etc.
10).
11). If (%SMSRF ~ %SNDR1) <-------- Label Sender1
Variable Add (%CNTR1 + 1)
If (%CNTR1 = 1)
Send SMS (Tells this person eg. BOB I'm at work)
Variable Add (%TXTVAR + 1)
Else If (%CNTR1 = 10)
Send SMS to %SNDR1 (Thats 10 txts you've sent me)
Endif x2
12). If (%SMSRF ~ %SNDR2) <-------- Label Sender2
Variable Add (%CNTR2 + 1)
If (%CNTR2 = 1)
Send SMS (Tells this person eg. DAVE I'm at work)
Variable Add (%TXTVAR + 1)
Else If (%CNTR2 = 10)
Send SMS to %SNDR2 (Thats 10 txts you've sent me)
Endif x2
13). If (%SMSRF ~ %SNDR3) <-------- Label Sender3
Variable Add (%CNTR3 + 1)
If (%CNTR3 = 1)
Send SMS (Tells this person eg. EMILY I'm at work)
Variable Add (%TXTVAR + 1)
Else If (%CNTR3 = 10)
Send SMS to %SNDR3 (Thats 10 txts you've sent me)
Endif x2
14). ......Etc.
15). ......
I'm still working on it, deciding whether to have the variables reset as they are all filled, 1 at a time, or to make them reset every hour or so. Also whether to make another profile purely for resetting those variables, or add them to this task. Bearing in mind that on my phone it gets rather annoying to manage/edit the task since its currently at 78 lines long.
As I said I was bored.
If anyone is interested in this I can post a backup xml of this somewhere.
TriggerSpasm said:
BOB, realizing it's an auto-reply, decides to be funny and spam txt me, thinking he will get a reply every time. However, tasker counts his incoming txts, (%CNTR1) and when it reaches a value of 10, send just one more txt saying something like (Thats 10 txts you've sent, seems Im still unavailable).
[...]
As I said I was bored.
Click to expand...
Click to collapse
Bored indeed. Anywho, look into arrays in Tasker, that'll make this tracking stuff much easier. Track all of that stuff in one array vs a bunch of different ones. Might clean up the code a little, make it easier to erm.. relieve more boredom?
khaytsus said:
Bored indeed. Anywho, look into arrays in Tasker, that'll make this tracking stuff much easier. Track all of that stuff in one array vs a bunch of different ones. Might clean up the code a little, make it easier to erm.. relieve more boredom?
Click to expand...
Click to collapse
Thanks, I certainly will.
Using Tasker http://www.pocketables.com/forum//showthread.php?t=9680
Scripted Backups using Tasker and TWRP http://www.pocketables.com/forum//showthread.php?t=11435
Beginner’s guide to Tasker http://www.pocketables.com/tag/beginners-guide-to-tasker
Tasks to:
(1) Take photos and email them when a specific text message is received
(2) Lock and password protect the phone when a specific text message is received
(2) Use different keyboards depending on the open app or screen orientation
Coming from the captivate I remember having the sgs tools app that had all the codes you could enter to get into certain menus..such as GPS, service mode, gsm and so on...do we have the codes and where can I find them
Sent from my SGH-I777 using XDA
devoured321 said:
Coming from the captivate I remember having the sgs tools app that had all the codes you could enter to get into certain menus..such as GPS, service mode, gsm and so on...do we have the codes and where can I find them
Sent from my SGH-I777 using XDA
Click to expand...
Click to collapse
http://bit.ly/x96GD8
gsrrr said:
http://bit.ly/x96GD8
Click to expand...
Click to collapse
Noiceeee....lol
Sent from my Ice Cream Sandwich
gsrrr said:
http://bit.ly/x96GD8
Click to expand...
Click to collapse
Back on topic. Try and see which ones work/don't work.
*#1234# = Firmware Version.
*#2222# = H/W Version.
*#8999*8376263# = All Versions Together.
*#8999*8378# = Test Menu.
*#4777*8665# = GPSR Tool.
*#8999*523# = LCD Brightness.
*#8999*377# = Error Menu.
*#8999*327# = EEP Menu.
*#8999*667# = Debug Mode.
*#92782# = PhoneModel. (Wap)
#*5737425# = JAVA Mode.
*#2255# = Call List.
*#232337# = Bluetooth MAC Adress.
*#5282837# = Java Version.
#*4773# = Incremental Redundancy.
#*7752# = 8 PSK uplink capability bit.
#*7785# = Reset wakeup & RTK timer cariables/variables.
#*7200# = Tone Generator Mute.
#*3888# = BLUETOOTH Test mode.
#*7828# = Task screen.
#*#8377466# = S/W Version & H/W Version.
#*2562# = Restarts Phone.
#*2565# = No Blocking? General Defense.
#*3353# = General Defense, Code Erased.
#*3837# = Phone Hangs on White screen.
#*3849# = Restarts Phone.
#*3851# = Restarts Phone.
#*3876# = Restarts Phone.
#*7222# = Operation Typ: (Class C GSM)
#*7224# = !!! ERROR !!!
#*7252# = Operation Typ: (Class B GPRS)
#*7271# = CMD: (Not Available)
#*7274# = CMD: (Not Available)
#*7337# = Restarts Phone. (Resets Wap Settings)
#*2787# = CRTP ON/OFF.
#*2886# = AutoAnswer ON/OFF.
#*3737# = L1 AFC.
#*5133# = L1 HO Data.
#*7288# = GPRS Detached/Attached.
#*7287# = GPRS Attached.
#*7666# = White Screen.
#*7693# = Sleep Deactivate/Activate.
#*7284# = L1 HO Data.
#*2256# = Calibration info? (For CMD set DEBUGAUTONOMY in cihard.opt)
#*2286# = Databattery.
#*2527# = GPRS switching set to (Class 4, 8, 9, 10)
#*2679# = Copycat feature Activa/Deactivate.
#*3940# = External looptest 9600 bps.
#*4263# = Handsfree mode Activate/Deactivate.
#*4700# = Please use function 2637.
#*7352# = BVMC Reg value (LOW_SWTOFF, NOMINAL_SWTOFF)
#*2558# = Time ON.
#*3370# = Same as 4700.
#*3941# = External looptest 115200 bps
#*5176# = L1 Sleep.
#*7462# = SIM Phase.
#*7983# = Voltage/Freq.
#*7986# = Voltage.
#*8466# = Old Time.
#*2255# = Call Failed.
#*5187# = L1C2G trace Activate/Deactivate.
#*5376# = DELETE ALL SMS!!!!.
#*6837# = Official Software Version: (0003000016000702)
#*7524# = KCGPRS: (FF FF FF FF FF FF FF FF 07)
#*7562# = LOCI GPRS: (FF FF FF FF FF FF FF FF FF FF FF FE FF 01)
#*2337# = Permanent Registration Beep.
#*2474# = Charging Duration.
#*2834# = Audio Path. (Handsfree)
#*3270# = DCS Support Activate/Deactivate.
#*3282# = Data Activate/Deactivate.
#*3476# = EGSM Activate/Deactivate.
#*3676# = FORMAT FLASH VOLUME!!!
#*4760# = GSM Activate/Deactivate.
#*4864# = White Screen.
#*6833# = New uplink establishment Activate/Deactivate.
#*3273# = EGPRS multislot. (Class 4, 8, 9, 10)
#*7722# = RLC bitmap compression Activate/Deactivate.
#*2351# = Blinks 1347E201 in RED.
#*4472# = Hysteresis of serving cell: 3 dB
#*2775# = Switch to 2 inner speaker.
#*9270# = Force WBS.
#*7878# = FirstStartup. (0=NO, 1=YES)
#*3757# = DSL UART speed set to. (LOW, HIGH)
#*3838# = Blinks 3D030300 in RED.
#*7878# = FirstStartup. (0=NO, 1=YES)
#*3838# = Blinks 3D030300 in RED.
*2767*226372# = Camera Reset. (deletes photos)
#7263867# = RAM Dump. (On or Off)
samsung mobile code. – - – sound code.
Samsung phones.
Dial *#6984125*#
Test menu dial *#9072641*# (You need this one i think.)
Click 5 Audio – 2 AP volume config
Tune Headset volume:
*#9072641*# – 2 EAR config – 3 Ringtone volume – Stap 6 tune it to 10
Tune movie volume:
*#9072641*# – 3 SPK config – 3 Ringtone volume – Stap 6 tune it to 10
Thanks, I think you are cute too.
lots of xoxo
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Dont be dicks you too.
I don't have sufficient posts to add a reply to the LMT Launcher thread since it's in the development section, so I'm posting here.
I'd really like to get ISAS working on the EVO 4g LTE, as it's a great feature. Here are my details:
Details
- State: rooted, s-off, TWRP 2.5 installed
- ROM: CM 10.2 nightly (2013-09-01)
- LMT v. 1.912 installed
LMT Settings
- Activate TouchService = on
- Autostart TouchService checked
- Set TouchService mode = Gestures, ISAS, and pie
- Set gesture input = 2 (see below)
- Relevant output of
Code:
getevent -p
Code:
add device 8: /dev/input/event2 # hence setting 2 in gesture input above
name "synaptics-rmi-touchscreen"
[...]
0035 : value 0, min 0, max 1100, fuzz 0, flat 0, resolution 0
0036 : value 0, min 0, max 1750, fuzz 0, flat 0, resolution 0
- Min bbox = 1
- Activation area thickness = 80
- According to the LMT thread, I should divide the max outputs above by my screen resolution (1280 x 720) to get the right x/y % settings for ISAS, which I've done:
--- Touchscreen to screen factor X = 1100 / 720 = 153%
--- Touchscreen to screen factor Y = 1750 / 1280 = 137%.
Lastly, I've set ISA 1 and ISA 2 (bottom left and bottom center) to open Apollo music player just to test things out. I can get it to work, but I have to hold the phone face up with one hand and violently flick the screen up from the bottom left with my index finger to get it to open. It is not a usable gesture in the least. Trying in vain with the speed I can produce with just my thumb while holding the phone produces no result.
Can someone chime in on any settings that might affect this?
Pie works properly, as do gestures (though if I have a gesture like two finger swipe to the left/right, it cycles my homescreen page at the same time as catching that I passed a gesture to LMT), so it would seem that the general configuration is sound. I just can't figure out why I need to swipe the ISA so darn fast. There's no way I could swipe that fast with my thumb; only holding in one hand and doing it at about 70% of my top possible speed gets the ISA to work.
Thanks for any input/suggestions! Feel free to ask for any other output.
jwhendy said:
I don't have sufficient posts to add a reply to the LMT Launcher thread since it's in the development section, so I'm posting here.
I'd really like to get ISAS working on the EVO 4g LTE, as it's a great feature. Here are my details:
Details
- State: rooted, s-off, TWRP 2.5 installed
- ROM: CM 10.2 nightly (2013-09-01)
- LMT v. 1.912 installed
LMT Settings
- Activate TouchService = on
- Autostart TouchService checked
- Set TouchService mode = Gestures, ISAS, and pie
- Set gesture input = 2 (see below)
- Relevant output of
Code:
getevent -p
Code:
add device 8: /dev/input/event2 # hence setting 2 in gesture input above
name "synaptics-rmi-touchscreen"
[...]
0035 : value 0, min 0, max 1100, fuzz 0, flat 0, resolution 0
0036 : value 0, min 0, max 1750, fuzz 0, flat 0, resolution 0
- Min bbox = 1
- Activation area thickness = 80
- According to the LMT thread, I should divide the max outputs above by my screen resolution (1280 x 720) to get the right x/y % settings for ISAS, which I've done:
--- Touchscreen to screen factor X = 1100 / 720 = 153%
--- Touchscreen to screen factor Y = 1750 / 1280 = 137%.
Lastly, I've set ISA 1 and ISA 2 (bottom left and bottom center) to open Apollo music player just to test things out. I can get it to work, but I have to hold the phone face up with one hand and violently flick the screen up from the bottom left with my index finger to get it to open. It is not a usable gesture in the least. Trying in vain with the speed I can produce with just my thumb while holding the phone produces no result.
Can someone chime in on any settings that might affect this?
Pie works properly, as do gestures (though if I have a gesture like two finger swipe to the left/right, it cycles my homescreen page at the same time as catching that I passed a gesture to LMT), so it would seem that the general configuration is sound. I just can't figure out why I need to swipe the ISA so darn fast. There's no way I could swipe that fast with my thumb; only holding in one hand and doing it at about 70% of my top possible speed gets the ISA to work.
Thanks for any input/suggestions! Feel free to ask for any other output.
Click to expand...
Click to collapse
Can you go into debug mode with 777 as described in the op? Then create a logcat containing starting the touchservice, doing some isas and stopping it again? Then just send me the log via pm and I can check what's wrong.
Btw: Min gesture score and min path length are also affecting isas. What did you configure for these?
Sent from my Nexus 4
@noname81: sorry, should have done the logcat from the beginning. I actually did look through it myself and couldn't figure out how to discern what LMT picked up from the unsuccessful ISA attempts. It seemed like it either worked (a line about a trigger event) or didn't.
In any case, yes, I should have just made one, and I'll send it along shortly.
With respect to any other settings, if they aren't mentioned, I left them alone. So min score was at 70% and min path was at 7. I changed the response to a debug overlay and anytime it activates, I've never seen a score of less than 95%. I did fiddle with making it something like 20% and setting the path at 2 to try and make it really easy to trigger; no luck.
I've now restored defaults, so my post is accurate for the logcat coming your way.
@noname81: links to logs sent (appears I can't attach files yet). Thanks for the assistance.