yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Accessories] Tarototh:
greetings! Thanks for the response! I love xda.

So after some back and forth with seidio they claim the extended door is available in colors even though amazon and their own site don't show colors. They say i have to voice call to special order the white or other color door. So this is great news.

Before I order i need to confirm some things if you would be so kind. Firstly, in other xda posts this battery door is the one listed as draco compatible:

​BVY35SSGS3

However seidio's site doesn't return a match on this part number when you do an internal site search, though if you search via google you get a link to a forgotten page on their website with no image... interesting. This item is about 15$.

Now I also see this door on seidio's site:

Product Code: CSR5SSGS3-BK

Which is called the "surface" . is this comparable to the one listed above? it's double the price.

their site also has a kickstand model which I am hoping will work. I know you don't know for sure but looking at the screenshots they provide what is your best judgement? Do you think it would fit? It has the step down design near the edges but still looks a little thicker. Maybe I could still squeeze the draco around it??

DILEX™ Extended with Metal Kickstand for use with Seidio Innocell® 3500mAh Super Extended Life Batteries - Black

MSRP: US$34.95

Product Code: CSK3SSGS3XK-BK

Finally, should I just go with the innocell 3500mah battery they sell or do you recommend another battery brand to fit this door? I'm ok with not having a zerolemon 7000 battery.

I appreciate anyone's help

www seidoonline "dot" com

sorry i still not allowed to post links.
[Windows Mobile Development and Hacking General] Matthew:
1) Hi, we works with Pocket PC 2003 (Embedded Visual C++ 4.0). Our target is perform a data call over integrated cellular line. We read that the right mean is TAPI (XDA-Developers forum) because COM2 seem to be owned by RIL layer. We wrote a test program which handles a data call answer. We get the serial port handle returned by "lineGetID()" function for current data call, but when we try to use it through standard communication APIs ("WriteFile()" and "ReadFile()") it doesn't work (no data is read or write from port handle, but there aren't errors returned by APIs). Same code seems to work fine on a HP IPAQ 2210 with a Compact Flash GSM/GPRS card. How can we transfer data so?

2) We noticed a phone answering process is alive (CPROG.EXE) that takes calls' control. We kill this process when we make our tests, but it backs to life after some minutes. How can we take real calls' control?

3) Is the integrated cellular modem Hayes compatible? Is there a way to directly send AT commands to integrated cellular modem?

4) DCB structure "PortDCB" we pass to "SetCommState()" is the following:

PortDCB.DCBlength = sizeof (DCB);

PortDCB.BaudRate = 9600;

PortDCB.fBinary = TRUE;

PortDCB.fParity = TRUE;

PortDCB.fOutxCtsFlow = FALSE;

PortDCB.fOutxDsrFlow = FALSE;

PortDCB.fDtrControl = DTR_CONTROL_ENABLE;

PortDCB.fDsrSensitivity = FALSE;

PortDCB.fTXContinueOnXoff = TRUE;

PortDCB.fOutX = FALSE;

PortDCB.fInX = FALSE;

PortDCB.fErrorChar = FALSE;

PortDCB.fNull = FALSE;

PortDCB.fRtsControl = RTS_CONTROL_ENABLE;

PortDCB.fAbortOnError = FALSE;

PortDCB.ByteSize = 8;

PortDCB.Parity = NOPARITY;

PortDCB.StopBits = ONESTOPBIT;

Is it correct?

Can anybody help me?

Matthew
[Windows Mobile Development and Hacking General] Matthew:
This DCB params seem do right job....

PortDCB.BaudRate = 115200;
PortDCB.fBinary = TRUE;
PortDCB.fParity = FALSE;
//PortDCB.fParity = TRUE;
PortDCB.fOutxCtsFlow = FALSE;
PortDCB.fOutxDsrFlow = FALSE;
PortDCB.fDtrControl = DTR_CONTROL_ENABLE;
PortDCB.fDsrSensitivity = FALSE;
//PortDCB.fDsrSensitivity = TRUE;
PortDCB.fTXContinueOnXoff = TRUE;
//PortDCB.fTXContinueOnXoff = FALSE;
PortDCB.fOutX = FALSE;
PortDCB.fInX = FALSE;
PortDCB.fErrorChar = FALSE;
PortDCB.fNull = FALSE;
PortDCB.fRtsControl = RTS_CONTROL_DISABLE;
PortDCB.fAbortOnError = FALSE;
PortDCB.ByteSize = 8;
PortDCB.Parity = NOPARITY;
PortDCB.StopBits = ONESTOPBIT;

problem one shuold be solved ...Hi
[Windows Mobile Development and Hacking General] cesarbremer:
Your DCB parameters worked fine.

Hi Matthew.

Your parameters worked fine with my application, i was teting an IMate and you helped me a lot with my next product version.

Thank you.

Cesar Bremer Pinheiro

Bremer Serv. Emp. Ltda.

Raseac Division.

http://www.raseac.com.br
[Windows Mobile Development and Hacking General] riazi:
Dear Matthew,

Hi,

I created a similar application to make a call from one PPC to another using data link. The problem is my program couldn't detect incoming calls. Would you please help me solve this issue?

Do you have any source code that I can learn from it? Also which method did you use? TAPI? COM port? RIL?

I'm very confused. Please help....

Best regards,

A. Riazi
[Windows Mobile Development and Hacking General] nutitija:
Why is your baudrate 115200 when a CSD connection through TAPI is only at 9600 ?
[Windows Mobile Development and Hacking General] IIIu30uD:
cause it's TAPI

you can't select bearer capabilities

if you wana select rate use RIL or direct access to COM-ports
[Windows Mobile Development and Hacking General] kiranj:
mathews help!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

hi,

i am facing a similar problem cant send data through writefile api on cellular line

these r code snippets form my cod e

if(dwReturn =lineOpen (

g_hLineApp, // Usage handle for TAPI

g_dwCurrentLineID, // Cannot use the LINEMAPPER value

&g_CurrentLineInfo.hLine, // Line handle

g_CurrentLineInfo.dwAPIVersion,

// API version number

0, // Must set to zero for Windows CE

0, // No data passed back

LINECALLPRIVILEGE_NONE, // Can only make an outgoing call

0, // Media mode

NULL))

g_MakeCallRequestID = lineMakeCall (g_CurrentLineInfo.hLine,

&g_hCall,

szDialablePhoneNum,

0,

NULL);

dwRet =lineGetID(g_CurrentLineInfo.hLine, 0, 0, LINECALLSELECT_LINE, lpVarString,TEXT("comm/datamodem"));

till this its ok it returns a valid comm handle

after that it sends th data over the connected call but doesnt receive anythinga t the other end ...

the problem might be to give a call handle and LINECALLSELECT_CALL in linegteid func tion i tried it but when i use it fails saying cannot obtain the handle .......now i don understand whether its the problem of not obtaining a handle or whether linehandle will work but problem is in communication ...

plz help and add some code snippets for the communication
[Windows Mobile Development and Hacking General] OdeeanRDeathshead:
firstly have you set up the following...

LPLINECALLPARAMS CallParams;

CallParams=(LPLINECALLPARAMS)malloc(sizeof(LINECALLPARAMS)+1024);

memset(CallParams,0,sizeof(LINECALLPARAMS)+1024);

CallParams->dwTotalSize = sizeof(LINECALLPARAMS)+1024;

// This is where we configure the line for DATAMODEM usage.

//its important to note that if you attempt to make a call

//using LINEMEDIAMODE_DATAMODEM, the line must be opened in

//that way to begin with or nothing will happen. ie open lines

//corresponding to what you plan to makecall with.

CallParams->dwBearerMode = LINEBEARERMODE_VOICE;//over voice call

CallParams->dwMediaMode = LINEMEDIAMODE_DATAMODEM;//data transmition

//LINEMEDIAMODE_INTERACTIVEVOICE;//for voice

//specify that we only want to use a call that is not alreay in use.

//Otherwise it can take over calls that are in progress

CallParams->dwCallParamFlags = LINECALLPARAMFLAGS_IDLE;

//specify to use the first address

CallParams->dwAddressMode = LINEADDRESSMODE_ADDRESSID;

CallParams->dwAddressID = 0;

next check the line you want to use and make sure...

if(lpDevCaps->dwBearerModes & callModeData)//datamode

{

if(lpDevCaps->dwBearerModes & callModeVoice)

{

//then check the media mode

if(lpDevCaps->dwMediaModes & LINEMEDIAMODE_DATAMODEM)

{

if(lpDevCaps->dwMediaModes & LINEMEDIAMODE_INTERACTIVEVOICE)

{

//use it

}

}

}

}

next when you get an incoming call etc get the handle......

HANDLE myTapiManager::getHandle()

{

HANDLE hModem=NULL;

CString name="";

classType="comm/datamodem";

DWORD dwSize = sizeof(VARSTRING) + 2048;

DWORD dwRet = 0;

do

{

LPVARSTRING lpVarString = (LPVARSTRING) new BYTE[dwSize];

lpVarString->dwTotalSize = dwSize;

//the commented out values are what microsoft seem to say

//but cause it to return no handle but only the device class name

dwRet = ::lineGetID(/*hOpenedLine*/NULL, 0,hCall,LINECALLSELECT_CALL /*LINECALLSELECT_LINE*/, lpVarString,

classType);

if ( dwRet == 0 )

{

hModem= * (HANDLE*) ((char*) lpVarString + lpVarString->dwStringOffset);

name= * (LPTSTR) ((char*) lpVarString + lpVarString->dwStringOffset + sizeof(HANDLE));

if(hModem==NULL)

{

MessageBox(NULL,_T("null handle"),_T("handle"),MB_OK|MB_SETFOREGROUND|MB_TOPMOST);

}

else

{

MessageBox(NULL,_T("non null handle, about to call init on port"),_T("handle"),MB_OK|MB_SETFOREGROUND|MB_TOPMOST);

hSerialHandle=hModem;

//you must initialize the port but I do not show it here

initializeIOTimeOuts();

}

break;

}

else if ( dwRet == LINEERR_STRUCTURETOOSMALL )

{

dwSize = lpVarString->dwNeededSize;

delete lpVarString;

lpVarString = NULL;

continue;

}

else

{

// handle errors.........

//

hModem=NULL;

}

}

while (1);

return hModem;

}

this works for me. One problem you may be having is the timing. If you get the handle when the call is offering it will be useless. You must ensure that the call is connected, use the LINECALLSTATE_CONNECTED for this.

cprog dose not effect the opperation of your program, only its ui.

:) :) :)
[Windows Mobile Development and Hacking General] vangelderp:
Have you looked at the zip I put in this post ?

http://xdaforums.com/viewtopic.php?t=18978

It may help you with the sending part and getting a handle to Readfile/writefile.

I have never worked on the anwering side so I know nothing on that.
[Windows Mobile Development and Hacking General] OdeeanRDeathshead:
to answer the call that is offering, use LineAnswer. I have tried LinePickup but it has not done what I want. When using lineanswer be aware that the os has already set the number of rings it will ring before the call is actually answered after you answer it. It is normally changed through the phone settings but you can do it programatically if you wish.

Also, you have not mentioned what you are doing with regards to threads. The first time I tried using tapi I spent a lot of time avoiding using multiple threads but it is impracticle. A good number would be 1 for the ui 1 for the line status and 1 for data transfer. Getting your serial handle would the require carefull synchronization.

I have not found benefit in altering any of the port settings. The time-outs for the read/write can make a huge difference though.

Have you checked if there is a class name following the handle in the LPVARSTRING? I have found that if you are doing everything correct except the timing, the name is added but not the handle. This means that the name would be 4 places sooner than it should. In that case the name is in the place where the handle should be and the call still succeeded. Try writing to the port using a string instead of a handle and see how far you get(kidding). To test it just treat the handle you have got as if it where a string and put it in a messagebox. If you can read it then your timing is off.

Lastly your problem could come from how you are setting the api version. Have you been checking the errors generated after all your api calls. There are a lot for tapi that tell you most of what is going on. I have noticed that if you are using the event method for getting line state messages from tapi (ie the correct time to grab the handle) there is something wrong with the way the api version gets negotiated. The event method is part of tapi 2.0 i think so it should be expected that an api version of at least 2.0 is a good version to aim for. For win ce 3.0 docs say that 2.0 is fully supported and parts of 2.1. This is not what actually happens though, I have found that I can't get the event method to work at all (among other things) if I don't pass a min version of 1.1 and a max version of 1.3. This is bizar because by that input tapi should not use any features above 1.3 :?:
[Windows Mobile Development and Hacking General] kiranj:
guys i ve been trying to set up call params

//Configure line device for a data modem

memset(&LineCallParams, 0, sizeof(LineCallParams));

LineCallParams.dwTotalSize = sizeof(LineCallParams);

LineCallParams.dwBearerMode = LINEBEARERMODE_VOICE;

LineCallParams.dwMediaMode = LINEMEDIAMODE_DATAMODEM;

LineCallParams.dwCallParamFlags = LINECALLPARAMFLAGS_IDLE;

//If multiple addresses on the line, use the first address

LineCallParams.dwAddressMode = LINEADDRESSMODE_ADDRESSID;

LineCallParams.dwAddressID = 0;

the problem is when i pass the lpparam instead of null it reaches to dialing the number and says disconnected: unreachable ..

There is no error while lineopen is passed with LINEMEDIAMODE_DATAMODEM as the 8th parameter i think it shoudl have given an error of media mode not supported at that point only ....but it didnt .....it opened the line fine

when i did not set the datamodem media mode in call params and rest remain as it is ..........the call works fine and is connected ....is it because the datacall facility is not supported and if it is not how can it be activated ....

lReturn = lineOpen(m_hLineApp, m_dwDeviceID, &m_hLine, m_dwAPIVersion, 0 , 0,

LINECALLPRIVILEGE_NONE, LINEMEDIAMODE_DATAMODEM, 0);

g_MakeCallRequestID = lineMakeCall (g_CurrentLineInfo.hLine,

&g_hCall,

szDialablePhoneNum,

0,

NULL); // NULL for default voice call

/**************************/

// lpCallParams);
[Windows Mobile Development and Hacking General] OdeeanRDeathshead:
Firstly, is the phone you are trying to dial a ppc. If yes... the ppc you wish to be the one that answers the call must have opened the line the same way as the dialing one, ie supporting data. If not then it will not even ring when a data call is offering and you will never know if your call was really made.

next look at lineopen.

long opnResult=lineOpen(hLineApp,

deviceID,

&hOpenedLine,

apiNegotiatedForUsedDevice,

0,//not used at all

1,//not used by tapi, but is passed back to this //application to help identify the source of the messages.

//in each line state message. It can be used

//to make sure the message is from a line

//opened by this app.

LINECALLPRIVILEGE_OWNER,// tells it can //accept calls.

LINEMEDIAMODE_DATAMODEM,

NULL);

almost the same but try LINECALLPRIVILEGE_OWNER. This must be set on the receiving end but I also set it on the dialing end.

If the media mode is not supported you will get an error message to tell so. That is the primary way my programs determine the identity of the line to use.

What is the device you are using? I have got bi-directional data transfer to work between ppc 2002 (xda I) and wm2003 se (xda mini). Before 2002 not as many features are supported.
[Windows Mobile Development and Hacking General] OdeeanRDeathshead:
also your call params may be too small

try adding a litle to the end

LPLINECALLPARAMS CallParams;

CallParams=(LPLINECALLPARAMS)malloc(sizeof(LINECALLPARAMS)+1024);

memset(CallParams,0,sizeof(LINECALLPARAMS)+1024);

CallParams->dwTotalSize = sizeof(LINECALLPARAMS)+1024;

.

.

.

.

and what about the number to dial in the call params

// Address to dial

//set its location to be after the normal end of the structure

CallParams->dwDisplayableAddressOffset = sizeof(LINECALLPARAMS);

CallParams->dwDisplayableAddressSize = strlen(szPhNumber);

strcpy((LPSTR)CallParams+sizeof(LINECALLPARAMS), szPhNumber));

then pass the szPhNumber into linemakecall, remember that ppc version

takes unicode.
[Windows Mobile Development and Hacking General] kiranj:
i am trying to pass data from pocket pc to my pc

this is whole part

LPLINETRANSLATEOUTPUT lpTransOutput = NULL;

// Call translate address before dialing.

do

{

// Allocate memory for lpTransOutput.

if (!(lpTransOutput = (LPLINETRANSLATEOUTPUT) LocalAlloc (

LPTR,

dwSizeOfTransOut)))

{

ErrorBox(TEXT("translate fails "));

goto exit;

}

lpTransOutput->dwTotalSize = dwSizeOfTransOut;

if (dwReturn = lineTranslateAddress (

g_hLineApp, // Usage handle for TAPI

g_dwCurrentLineID, // Line device identifier

g_CurrentLineInfo.dwAPIVersion,

// Highest TAPI version supported

lpszPhoneNum, // Address to be translated

0, // Must be 0 for Windows CE

0, // No associated operations

lpTransOutput)) // Result of the address translation

{

ErrorBox(TEXT("lineTranslateAddress fails "));

goto exit;

}

if (lpTransOutput->dwNeededSize <= lpTransOutput->dwTotalSize)

break;

else

{

dwSizeOfTransOut = lpTransOutput->dwNeededSize;

LocalFree (lpTransOutput);

lpTransOutput = NULL;

}

} while (TRUE);

dwSizeOfCallParams += lpTransOutput->dwDisplayableStringSize;

if (!(lpCallParams = (LPLINECALLPARAMS) LocalAlloc (

LPTR,

dwSizeOfCallParams)))

{

ErrorBox(TEXT("lineTranslateAddress open fails "));

goto exit;

}

ZeroMemory(lpCallParams, dwSizeOfCallParams);

// Set the call parameters.

lpCallParams->dwTotalSize = dwSizeOfCallParams;

lpCallParams->dwBearerMode = LINEBEARERMODE_VOICE;

lpCallParams->dwMediaMode = LINEMEDIAMODE_DATAMODEM ;

lpCallParams->dwCallParamFlags = LINECALLPARAMFLAGS_IDLE;

lpCallParams->dwAddressMode = LINEADDRESSMODE_ADDRESSID;

lpCallParams->dwAddressID = g_dwCurrentLineAddr;

lpCallParams->dwDisplayableAddressSize =

lpTransOutput->dwDisplayableStringSize;

lpCallParams->dwDisplayableAddressOffset = sizeof (LINECALLPARAMS);

// Save the translated phone number for dialing.

lstrcpy (szDialablePhoneNum,

(LPTSTR) ((LPBYTE) lpTransOutput +

lpTransOutput->dwDialableStringOffset));

memcpy((LPBYTE) lpCallParams + lpCallParams->dwDisplayableAddressOffset,

(LPBYTE) lpTransOutput + lpTransOutput->dwDisplayableStringOffset,

lpTransOutput->dwDisplayableStringSize);

// Make the phone call. lpCallParams should be NULL if the default

// call setup parameters are requested.

g_MakeCallRequestID = lineMakeCall (g_CurrentLineInfo.hLine,

&g_hCall,

szDialablePhoneNum,

0,

NULL); // NULL for default voice call

/**************************/

// lpCallParams);

plz suggest if i need to change anything but as the call is successfully connected when only media mode is not set i guess problem is not with the memory location or anything but lies with the provider not sure ...............
[Windows Mobile Development and Hacking General] kiranj:
or better maybe if u can suggest how i can do settings on my pocket pc for data calls
[Windows Mobile Development and Hacking General] vangelderp:
If you can't make a Data Modem type call, but you can make a voice call - Then are you sure you have Data Enabled on your Sim.

I'm sure I had that un-reachable error ages ago and it was due to not having Data Enabled. You have to contact your Sim provider to do that.
[Windows Mobile Development and Hacking General] OdeeanRDeathshead:
I have never included the lineTranslateAddress, i just put it in the way the user entered it( with a little error checking). If it works for voice though it must be OK.

With the sim, I have done this using 3 different sims and never had to set anything special on it. I could be lucky I guess and had sims already enabled. I doubt it though because one is 7 years old pre paid and not had any change since purchase. The second in a new pre paid and the 3rd is a full gprs enabled(not that gprs has anything to do with this). There should not be anything in the os to set either as when you do what you have done it is doing the "setup" just programatically.

I remember reading somewhere that the network had to support it but I can't be more specific.

What is your network? What is your device? what is your os?

When you say the voice call is connected what do you mean?..

1)your program at the other end answered.

2)the phone app on the other end answered.

3)your dialing end app received the connected message.

4)the returned value from linmakecall was > (-1).

5)some phone hardware on a real phone answered.

6) (my favourite way) the monitor next to your phone started buzzing, proving something was going on. Thats how I test my gprs connectivity :lol:
[AT&T Samsung Galaxy Note II] hayel70:
I have at&T Samsung galaxy note 2 sgh-i317 and the phone doesn't support Arabic language

how can I add Arabic language to my phone?

is there any rom support Arabic language?
[AT&T Samsung Galaxy Note II] anotherguy19:
http://www.gsmindia.in/forum/androi...e-2-n7100-arabic-indian-trukish-firmware.html
[AT&T Samsung Galaxy Note II] hayel70:
does it work for at&t smasung galaxy note 2 sgh-i317?
[AT&T Samsung Galaxy Note II] anotherguy19:
Not sure. Otherwise CM has Arabic support, but you will lose some spen functionality.

With existing rom to get Arabic support, go into Settings>Language and input > tap cog next to Samsung Keyboard > scroll down to download other languages.

Not only should you have have Arabic support, but also Arabic handwriting support once the pack is downloaded.

If the pack is not presemt, your ROM may have hidden Arabic support. To re-enable,

https://play.google.com/store/apps/details?id=com.wanam&hl=en
[Android Apps and Games] Eric_Eric_Eric:
With Better CyanogenMod Changelog, a changelog of your current CyanogenMod build will be displayed after the first boot after flashing the build. I used to flash, then try to find a changelog app as soon as I entered my new build for the day. Now, that task is done for me. This is extremely useful for nightly flashers of CyanogenMod. Enjoy!

Note that, after the first launch, this app will not be visible on your homescreen. It only runs after you have flashed a new CyanogenMod build.

I have provided the apk below for those without access to the Play Store, but, the Play Store is where you will get future updates faster.

Play Store: http://goo.gl/pWiyc
[Android Apps and Games] Eric_Eric_Eric:
For anybody that may have received an "unsupported device" message, I apologize. I have updated the apk, and it should now work. Let me know. Thanks!
[Nexus 4 Q&A, Help & Troubleshooting] Strelok1987i:
Last night, the battery of my N4 was getting really low, so I plugged it in. I noticed it was not charging when I plugged it in. It ended up dying completely on me. I plugged it in again later that night, and the LED started flashing red. I unplugged it and replugged it a few times, and now when I plug it in there is a solid red LED and the device is totally unresponsive. I let it sit on the charger all night and it made no difference. I was totally stock, no root, no kernel, bootloader was even still locked.

Am I going to have to RMA? I'm a college student and don't exactly have $300 sitting in my account at the moment..
[Nexus 4 Q&A, Help & Troubleshooting] nxt:
Press and hold the power button for about 10-15 seconds till the light turns off
[Nexus 4 Q&A, Help & Troubleshooting] Strelok1987i:
Sorry, I should have specified. I've tried every button combo and nothing works. The phone is totally unresponsive.
[Nexus 4 Q&A, Help & Troubleshooting] joshnichols189:
Find a torx screw and reset your battery.
[Nexus 4 Q&A, Help & Troubleshooting] username8611:
you really need to hold it for a while, longer than you think. im pretty sure when it happened to me i had to hold the power button for around 30 seconds after unplugging it. if theres still no dice then it might be ok to freak out lol
[Nexus 4 Q&A, Help & Troubleshooting] sarkozy:
This solution worked for me after no amount of charging and button pressing would get me anything. Phone was stock and charging overnight when the red LED happened.
[Nexus 4 Q&A, Help & Troubleshooting] Strelok1987i:
Reset the battery? What does that entail? Is there a guide for it or something?
[Nexus 4 Q&A, Help & Troubleshooting] Yuvin:
You've got to open up the back of your Nexus 4, then unscrew the battery connector, take it out then plug it back in. There are some tutorials around the forum if you need them. (:
[Nexus 4 Q&A, Help & Troubleshooting] Strelok1987i:
Did this, no difference. I'm a little afraid my warranty may be void now :(

Tried several different chargers, different cables, etc. Nothing works. Just a solid red LED.