Database Users

AT-Commands?

Hi there,
maybe not a XDA specific Question but maybe s.o. could still help me.
I've got a SIEMENS emem ES75 GSM Modem wich I wanted to use as a SMS receiver for my Party next month (receive sms and project them onto a wall )
But I have some trouble controlling it using the AT-Commandset.
For example: the AT+GMM Command which should give me the name of the Manufacturer) Sometimes AT+ Commands are working, sometimes not.
As it works, I printed out the current settings using AT&V:
Code:
ACTIVE PROFILE:
E0 Q0 V1 X4 &C1 &D2 &S0 \Q0 \V1
S0:000 S3:013 S4:010 S5:008 S6:000 S7:060 S8:000 S10:002 S18:000
+CR: 0
+CRC: 0
+CMGF: 1
+CSDH: 0
+CNMI: 0,0,0,0,1
+ICF: 3
+IFC: 0,0
+ILRR: 0
+IPR: 115200
+CMEE: 0
^SMGO: 0,0
+CSMS: 0,1,1,1
^SACM: 0,"000000","FFFFFF"
^SLCC: 0
^SCKS: 0,1
^SSET: 0
+CREG: 0,1
+CLIP: 0,2
+CAOC: 0
+COPS: "T-MOBILE D"
+CGSMS: 3
Remember: it says "CURRENT PROFILE"
Then I used the AT&V Command when it did not work:
Code:
Current Settings............
E0 H0 Q0 V1
&C0 &D0 &P1 &R0 &S0
S00=000 S01=000 S02=043 S03=013 S04=010 S05=008 S06=000 S07=030
S08=000 S09=000 S10=000 S11=000 S12=050 S13=000 S14=000 S15=000
S16=000 S17=000 S18=000 S19=000 S20=000 S21=000 S22=000 S23=000
S24=000 S25=005 S26=001 S27=000 S28=000 S29=000 S30=000 S31=000
S32=000 S33=001 S34=000 S35=000 S36=000
#0 :
#1 :
#2 :
#3 :
#4 :
#5 :
#6 :
#7 :
#8 :
#9 :
Why does it output the "CURRENT SETTING" instead of the "CURRENT PROFILE"? And why can't I read the SMS? With this Setting it does not accept most of the AT+(..) commands. (AT+GMM, ...)
I sniffed the serial port communication from working applications and used the same commands and init-strings, but nothing
Any advice?

Nothing?

disable / enable Java scripts in Internet Explorer (PIE)

just fyi for somebody who needs this:
HKLM\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Security_RunScripts = 1 or 0 (enable or disable)

[Q] touch screen not responding only when sd card is present

Hi all,
I have a problem with my defy, whitout fall or update the touch screen stop responding.
After some resets & sbf flashing I've noticed that the touch screen is ok only when there is no sdcard.
I've tried over sdcards with no more success.
The sdcard is readable, I can access with adb.
Clockworkmod access the sdcard too.
With sdcard dmesg :
qtouch_force_reset: Forcing HW reset
Unable to get gpio pin num for touch_pwr_enq
touch_write: Error while trying to write 2 bytes
qtouch_set_addr: Can't send obp addr 0x 0
qtouch_process_info_block: Cannot read info object block
qtouch_ts_probe:Cannot read info block -121, checking for bootloader mode.
Without sdcard :
qtouch_force_reset: Forcing HW reset
Unable to get gpio pin num for touch_pwr_en
qtouch_process_info_block: Build version is 0x10
qtouch_process_info_block: Object 5 @ 0x00f2 (9) insts 1 rep_ids 0
qtouch_process_info_block: Object 6 @ 0x00fb (6) insts 1 rep_ids 1
qtouch_process_info_block: Object 38 @ 0x0101 (8) insts 1 rep_ids 0
(...)
Can it be a HW problem ?
What do you think I can do ?

Questions go in the Q&A section

CharlyBrok said:
Hi all,
I have a problem with my defy, whitout fall or update the touch screen stop responding.
After some resets & sbf flashing I've noticed that the touch screen is ok only when there is no sdcard.
I've tried over sdcards with no more success.
The sdcard is readable, I can access with adb.
Clockworkmod access the sdcard too.
With sdcard dmesg :
qtouch_force_reset: Forcing HW reset
Unable to get gpio pin num for touch_pwr_enq
touch_write: Error while trying to write 2 bytes
qtouch_set_addr: Can't send obp addr 0x 0
qtouch_process_info_block: Cannot read info object block
qtouch_ts_probe:Cannot read info block -121, checking for bootloader mode.
Without sdcard :
qtouch_force_reset: Forcing HW reset
Unable to get gpio pin num for touch_pwr_en
qtouch_process_info_block: Build version is 0x10
qtouch_process_info_block: Object 5 @ 0x00f2 (9) insts 1 rep_ids 0
qtouch_process_info_block: Object 6 @ 0x00fb (6) insts 1 rep_ids 1
qtouch_process_info_block: Object 38 @ 0x0101 (8) insts 1 rep_ids 0
(...)
Can it be a HW problem ?
What do you think I can do ?
Click to expand...
Click to collapse
AFAIK, it is HW related..
Best choice, get it to the SC..

Maybe I'll try to change the digitizer (20€ on ebay).
Warranty period is finish.

I want more log,
The goal is to enable logging debug in qtouch_obp_ts
I put in /system/etc/init.d/77debug
Echo 0xFF > /sys/module/qtouch_obp_ts/parameters/tsdebug
But no change at all...
What I am doing wrong ?
Envoyé depuis mon A500 avec Tapatalk

plz Need help to re-calibrate proximity sensor in note3

can someone please help me
I'm trying to re-calibrate the proximity sensor according to the instructions in this thread for note 3 N9005 .
so as the instructions I'm trying the normal method
but don't know how to convert the values in Hexadecimal.
mine offset value is :
76,196,156
& the normal value is :
0
so how to add offset value + normal value ???!!!
because the normal value is : 0
so plz if anyone know about the process to guide me for that
thanks

plz someone reply .....!!!!
I need help
my note 3 proximity sensor is not working
& I bought it just 2 months ago

still waiting for someone to help me.

Ask in that thread .

alhaseeri said:
can someone please help me
I'm trying to re-calibrate the proximity sensor according to the instructions in this thread for note 3 N9005 .
so as the instructions I'm trying the normal method
but don't know how to convert the values in Hexadecimal.
mine offset value is :
76,196,156
& the normal value is :
0
so how to add offset value + normal value ???!!!
because the normal value is : 0
so plz if anyone know about the process to guide me for that
thanks
Click to expand...
Click to collapse
You can use windows calculator to convert decimal into Hex.
Just do the following, Already replied to your private message. Already converted your offset into hex for you. just type as it is.
su
# echo -en $ '\x4c' > /efs/prox_cal
# chown system:system /efs/prox_cal
# chmod 644 /efs/prox_cal
# sync
# Reboot

Update Region from China to India Redmi Note 4 Rooted

Open Buildprop app:
https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor&hl=en_IN
Search for the below item:
ro.miui.cust_variant
If the above item is not found, then create:
* Run Buildprop
* Tap on 3 dots at top right corner.
* Tap New
Name = ro.miui.cust_variant
Value = en
Name = ro.miui.region
Value = IN
* Save and reboot.

Wow, so simply it fixed.