[HOW-TO] Enabled GSM Phone calls on the JTC Jetstream (S-OFF - ROOT - WIP)

Giblet-dono

Senior Member
Mar 24, 2009
1,455
665
113
Ok. I did play around a bit and try different things. Here is what I managed to do and get to.

1. /system/etc/soundimage - srsfx_trumedia_voice.cfg shows configuration for a lot of sound realted issues - like routing-output device, BT headset, speaker, wired headset, AUX/line out with each having blocks like hard limiter, TruEQ, CSHP and WOWHD. These settings include gain - found some set at 0.400 and others at 1.000. So I did play around a bit with the gain settings and did manage (I think) to improve the sound reception on google talk - not sure though if it actually happened or if it was just because i thought i had changed something. The souting-output device section has a lot of disallowed devices including Bluetooth A2DP - did try enabling the wired headset and seeing if anything happens but in vain - I think some of the other settings specific for the BT headset must also be altered.

2. /system/etc - some files like A1026_CFG.csv, AdieHWCodec.csv, AdieHWCodec_WA.csv, AIC3254_REG.csv, AIC3254_REG_DualMic.csv
Each of these files has some binaries set for stuff like phonecall_reciever, phonecall_headset, phonecall_speaker, phonecall_by.vr_no_ns_reciever. I could not figure any of this out so have not touched any of this.

3. /system/etc - CodecDSPID.txt and CodecDSPID_PVT.txt - both seem to have definitions for various sound+mic functions - for phone, playback, recording, voip. All except phone have values set with definitions for certain files within /system/etc/soundimage. Phone is left blank. As all of them seem to be specific for each function, I do not know what to define for the phone functions.

4. /system/etc - IOTable.txt and IOTable_XB.txt - both as I understand have binaries set for input-output with each method of input having binaries specific for it. Again as I do not understand, have not touched these.

5. /etc/permissions - tablet_core_hardware.xml - the permissions include instructions which say that GSM phones must also include android.hardware.telephony.gsm.xml which is missing from the folder. May be if we could get that file, try incorporating it and testing what happens.

These are what I found. I am not so well versed with binaries and stuff so I do not know what to do further. If anyone else who has the know how is interested can can try taking this further, will be much appreciated.

Edit: In case this is all basic stuff which has already been checked by more experienced users than me, I am sorry about repeating known stuff.

Great job on this!
I'm very unexperienced in these fields myself, so could you describe the method and tools used to get these results?
Also, could you try to get the file needed in your last paragraph, from a HTC Flyer Honeycomb rom?
 

kailashpchhabria

Senior Member
Dec 4, 2011
243
43
0
Bangalore
Great job on this!
I'm very unexperienced in these fields myself, so could you describe the method and tools used to get these results?
Also, could you try to get the file needed in your last paragraph, from a HTC Flyer Honeycomb rom?
Hi,

I used Root Explorer to just open each file with text viewer/editor and to see the contents. That is basically all I did.

Regarding getting the files needed for the last para, unfortunately I also am absolutely new at this and have no idea how to go about moving ahead with this. Was hoping someone else with more experience would be able to figure something out. Sorry about being unable to help further.

I even came across a section of files which is basically the output log for every method of input used. Like for handsfree wired headset, blootooth, keyapd, gps, etc. While trying to plug in my handsfree wired headset I got an output of headset_no_mic. All the output files are located in /sys/devices/virtual - each file has a set of folders and files. Folders seem to run in a loop - i.e. opening each folder shows contents of the parent device folder and so on. The files are power and dev - power is blank while dev shows the output for a specific instant. Coincidently even tried USB Host mode output but failed to get anything. Not experienced nor do I know much about android system to be able to understand. Would love to learn and contribute but unfortunately can't devote much time due to commitments for my studies.

Hope some one with more experience can help us out.
 

MikePierotti

Member
Dec 5, 2011
28
3
0
52
Tamuning
www.docomopacific.com
I saw these build.prop settings somewhere else

I saw these build.prop settings somewhere else but have not been able to try them out yet. I just received my refurbished jetstream today and want to fully charge it before I play around but thought someone may want to give it a go.


ro.ril.reject.cs.ss.enabled=0
ro.ril.reject.mo.used.enabled=0
ro.phone.function=1

ro.max.fling_velocity=12000
ro.min.fling_velocity=8000
persist.sys.ui.hw=1
ro.ril.disable.power.collapse=1
pm.sleep_mode=1
windowsmgr.max_events_per_sec=180
ro.mot.eri.losealert.delay=1000
ro.media.enc.jpeg.quality=90
ro.media.dec.jpeg.memcap=8000000
net.tcp.buffersize.default=4096,87380,256960,409 6,16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,1 6384,256960
net.tcp.buffersize.umts=4096,87380,256960,4096.1 6384,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,1 6384,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,1 6384,256960
net.tcp.buffersize.evdo_b=4096,87380,256960,4096 ,16384,256960
ro.kernel.android.checkjni=0
ro.kernel.checkjni=0
ro.config.nocheckin=1
ro.telephony.call_ring.delay=0
persist.adb.notify=0
ro.ril.hsxpa=2
ro.ril.gprsclass=10
ro.ril.hep=1
ro.ril.enable.dtm=1
ro.ril.hsdpa.category=10
ro.ril.enable.a53=1
ro.ril.enable.3g.prefix=1
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449
ro.ril.hsupa.category=5
dalvik.vm.execution-mode=int:jit
persist.sys.purgeable_assets=1
persist.sys.use_dithering=1
persist.telephony.support.ipv6=1
persist.telephony.support.ipv4=1
ro.ril.enable.amr.wideband=1
ro.media.enc.hprof.vid.fps=65
 

MikePierotti

Member
Dec 5, 2011
28
3
0
52
Tamuning
www.docomopacific.com
I saw these build.prop settings somewhere else but have not been able to try them out yet. I just received my refurbished jetstream today and want to fully charge it before I play around but thought someone may want to give it a go.


ro.ril.reject.cs.ss.enabled=0
ro.ril.reject.mo.used.enabled=0
ro.phone.function=1

ro.max.fling_velocity=12000
ro.min.fling_velocity=8000
persist.sys.ui.hw=1
ro.ril.disable.power.collapse=1
pm.sleep_mode=1
windowsmgr.max_events_per_sec=180
ro.mot.eri.losealert.delay=1000
ro.media.enc.jpeg.quality=90
ro.media.dec.jpeg.memcap=8000000
net.tcp.buffersize.default=4096,87380,256960,409 6,16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,1 6384,256960
net.tcp.buffersize.umts=4096,87380,256960,4096.1 6384,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,1 6384,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,1 6384,256960
net.tcp.buffersize.evdo_b=4096,87380,256960,4096 ,16384,256960
ro.kernel.android.checkjni=0
ro.kernel.checkjni=0
ro.config.nocheckin=1
ro.telephony.call_ring.delay=0
persist.adb.notify=0
ro.ril.hsxpa=2
ro.ril.gprsclass=10
ro.ril.hep=1
ro.ril.enable.dtm=1
ro.ril.hsdpa.category=10
ro.ril.enable.a53=1
ro.ril.enable.3g.prefix=1
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449
ro.ril.hsupa.category=5
dalvik.vm.execution-mode=int:jit
persist.sys.purgeable_assets=1
persist.sys.use_dithering=1
persist.telephony.support.ipv6=1
persist.telephony.support.ipv4=1
ro.ril.enable.amr.wideband=1
ro.media.enc.hprof.vid.fps=65
Standby on some of these setting as I see a few changes that may need to be made already. I am working on it today and if I come across a working will let you know.
 

MikePierotti

Member
Dec 5, 2011
28
3
0
52
Tamuning
www.docomopacific.com
Ok. I did play around a bit and try different things. Here is what I managed to do and get to.

1. /system/etc/soundimage - srsfx_trumedia_voice.cfg shows configuration for a lot of sound realted issues - like routing-output device, BT headset, speaker, wired headset, AUX/line out with each having blocks like hard limiter, TruEQ, CSHP and WOWHD. These settings include gain - found some set at 0.400 and others at 1.000. So I did play around a bit with the gain settings and did manage (I think) to improve the sound reception on google talk - not sure though if it actually happened or if it was just because i thought i had changed something. The souting-output device section has a lot of disallowed devices including Bluetooth A2DP - did try enabling the wired headset and seeing if anything happens but in vain - I think some of the other settings specific for the BT headset must also be altered.

2. /system/etc - some files like A1026_CFG.csv, AdieHWCodec.csv, AdieHWCodec_WA.csv, AIC3254_REG.csv, AIC3254_REG_DualMic.csv
Each of these files has some binaries set for stuff like phonecall_reciever, phonecall_headset, phonecall_speaker, phonecall_by.vr_no_ns_reciever. I could not figure any of this out so have not touched any of this.

3. /system/etc - CodecDSPID.txt and CodecDSPID_PVT.txt - both seem to have definitions for various sound+mic functions - for phone, playback, recording, voip. All except phone have values set with definitions for certain files within /system/etc/soundimage. Phone is left blank. As all of them seem to be specific for each function, I do not know what to define for the phone functions.

4. /system/etc - IOTable.txt and IOTable_XB.txt - both as I understand have binaries set for input-output with each method of input having binaries specific for it. Again as I do not understand, have not touched these.

5. /etc/permissions - tablet_core_hardware.xml - the permissions include instructions which say that GSM phones must also include android.hardware.telephony.gsm.xml which is missing from the folder. May be if we could get that file, try incorporating it and testing what happens.

These are what I found. I am not so well versed with binaries and stuff so I do not know what to do further. If anyone else who has the know how is interested can can try taking this further, will be much appreciated.

Edit: In case this is all basic stuff which has already been checked by more experienced users than me, I am sorry about repeating known stuff.
I have noted a lot of files are missing on the Jetstream. I am working to see if I can find compatible ones from other builds and will see if copying these onto the device makes any diff.
 
  • Like
Reactions: kailashpchhabria

onasre

Senior Member
Nov 7, 2008
53
8
0
Thank you , worked for me ...
But whats the point of having this without Voice " useless " !!! i saw in another thread about Custom ROM which has phone function enabled by default but is it without voice too !!?
 

Giblet-dono

Senior Member
Mar 24, 2009
1,455
665
113
Thank you , worked for me ...
But whats the point of having this without Voice " useless " !!! i saw in another thread about Custom ROM which has phone function enabled by default but is it without voice too !!?
Well.. we are waiting for a developer.. because I am not skilled enough in coding to enable voice.
We know it's possible..
Because the Flyer got it enabeled!
 

maxrfon

Senior Member
Nov 30, 2004
294
182
0
Let me put my 50 cent here(IMXO):

The modem is the one in charge for making calls.
The OS CPU just sends a command to the phone CPU via AT or RIL interface and here you have the call, but the speaker and the microphone are connected to the OS CPU, thus - no way unless you solder the missing ones to the modem's in/out .
 
  • Like
Reactions: kokonomutsu

Giblet-dono

Senior Member
Mar 24, 2009
1,455
665
113
so even install anything we wont be able to use for calls because mic will not work ?
I'm sorry overhaste reaction
Yes we might be able to, we don't need any soldering.
The calls ARE actually getting made with the method in first post!
BUT! The sound does not work.
This is due to libraries inside Android.

We MIGHT just get it to work with AOSP (Showp-1984 still workign on it)
The same way the Samsung Galaxy tab 10.1 did not come with call support, but can be enabled with AOSP (and even normal roms now)
Plus that the HTC Flyer also can use phone calls so... it's VERY possible we will eb able to use this in teh future
 
Last edited:

uyducu02

New member
Feb 18, 2010
4
0
0
HELPME

So to make and receive phonecalls on you 3G Jetstream:

Prerequisite:

1) 3G JetStream
2) S-Off (get yours from HTCDev now!)
3) Root (get yours from DoomLord)

Using root explorer or your favorite text editor edit the build.prop file under /system/build.prop
You could also use Prop edit (free in the market).
edit the following lines:

Code:
ro.ril.reject.cs.ss.enabled=0
ro.ril.reject.mo.ussd.enabled=0
ro.phone.function=1
To enable Bt Headset profile change the following:

Code:
ro.bt.profiles	= 4270403
service.brcm.bt.ag_supported = 1
Save your changes and reboot your device.
Look under the programs menu you will see the phone app .
You will now be able to make and receive calls.
WITHOUT SOUND!

Tested on AT&T HTC Jetstream With Dutch "Hi" simcard!
If this helped you Just Thank me !

Reports are rolling in that calling works but sound doesn't work, not through speaker/Bluetooth or normal.
As I have only found these buildprop tweaks, I don't really know what's going on behind it!

Enjoy!
..
hi,I'm doing everything written here ..but when I say save (build prop).
gave an error message ... Message: failed saving prop builder
please help me.thanks
[email protected]