Related
I have a BT338 bluetooth GPS adapter it will not get a lock on and I have been looking for a flash program for it to see if I can reflash it.
I followed a link from a site to this sites ftp server that used to have it but it looks like it has been taken down.
Does anyone know if flashing is possible and if so does anyone have a program to do so?
Thanks for any help.
Packrat,
I have had a BT-338 for two years and I love it. I don't recall that I was ever able to find a method to upgrade the firmware. I will watch this thread in case some one has an answer.
On the other hand, I did have problems when I first got this unit. If I played with changing setting between WAAS/normal and/or Sirf/NMEA modes, sometimes this thing was not get a lock. To fix it I would use a laptop tool to reset the unit to factor setting. I think it was GPSInfo connecting via a BT dongle.
Let me know if this might help and I will look into the exact detail if you need it.
whbell said:
Packrat,
I have had a BT-338 for two years and I love it. I don't recall that I was ever able to find a method to upgrade the firmware. I will watch this thread in case some one has an answer.
On the other hand, I did have problems when I first got this unit. If I played with changing setting between WAAS/normal and/or Sirf/NMEA modes, sometimes this thing was not get a lock. To fix it I would use a laptop tool to reset the unit to factor setting. I think it was GPSInfo connecting via a BT dongle.
Let me know if this might help and I will look into the exact detail if you need it.
Click to expand...
Click to collapse
Thanks for the reply, I tried to reset it to factory via the SirDemo program, but that didnt help. Hopefully I can find a way.
Yes reflash is possible...
You can use SirfDemo and SirfFlash
The procedure is almost the one described here....
http://web.mac.com/tomtastic/site/log/Entries/2007/6/18_Holux_GPSlim236_boot_mode.html
You can download the needed tools here...
http://www.falcom.de/support/software-tools/sirf/
To flash
- First you have to connect your bt-338 using SirfDemo.
- In Action/ Transmit Serial Message select NMEA and send this message
'PSRF100,0,38400,8,1,0' without quotes. This will put the GPS in SIRF Mode.
- After that choose Action / Transmit Serial Message select SIRF this time and send '94' without quotes. This will put the GPS in boot Mode.
- Disconnect now SirfDemo using the button and start SirfFlash without powering down the GPS.
- Choose the correct port and 38400 Baud and - very important -select 'external boot mode'. Browse for the new firmware .bin file and select 'program flash'.
- Execute and enjoy.
Cheers!
I have now (finally!) successfully read the firmware from my two BT338 and a TomTom Mk2 BT mouse. Also important to notice is the following:
- Address Range is 0x0 to 0x7ffff (4 times an "f") resulting in a 512kB bin file.
- Any other speed than 38400 will NOT work!
Did not dare yet to flash actually... I have now:
TomTom Mk-II
GSW3.0.2TomTom1.1_3.0.00.03-C3P1.02b
BT338 (NaviLock labled in Germany)
GSW3.0.2_3.0.00.03-C16P1.02a
GSW3.1.1LowV_3.1.00.07-C23B1.00
I know there must be newer one for BT338 as you can see from the FAQ at Globalsat USA at: http://www.usglobalsat.com/gpsfacts/bt338_gps_facts.html
The mention even different versions there (QA 38):
BT-338_GSW3V3.1.1LowV_F-GPS-03-0506222 and
BT-338_GSW3.1.1TO_F-GPS-03-0510032
I noticed that reading out the SW sometimes delivers different results after 7d008 when some time has passed. I suspect that some data is stored there which may vary over time (satelite positions, routes or whatever may be stored depending on the time).
bye
tobbbie
I can report success now in upgrading my BT338 from the old (3.0.2) FW to the later one (3.1.1) I have retrieved from my other BT338.
Main gain for me is the availability of geoid correction for the height.
Anynone has a later firmware for the BT338 or the TomTom MK2?
You can PM me if you don't want to post here.
bye
tobbbie
GSW3.0.2TomTom1.1_3.0.00.03-C3P1.02b
Hi tobbie,
have you managed to get some new firmwares , I am searching if there is a new one for the tomtom ( there is still some issues between the treo and the tomtom related to the bluetooth stack ). Is there a way to use the BT-338 or a part of the BT-338 firmware in the tomtom ?
thanks
Laurent
look here: http://www.gpspassion.com/forumsen/topic.asp?TOPIC_ID=27925&whichpage=11
please read all posts and follow the wohle story. My TomTom MkII currently runs the 3.2.2 of the latest BT338.
Thanks tobbie,
I have red the full thread, downloaded your dumps of the firmware, and dump my tomtom firmwarewith the sirf tools.
I have compared the dump from your tomtom and mine ( same version 302 ) and they are quite different beiginning in 6D008 :
your firmware :
6D008 : 06 3E 00 00 01 00 00 00 41 46 31 41 39 53 D8 19 ....
my dump :
6D008 : 20 C6 00 00 99 00 00 00 41 46 31 41 39 53 D8 19 ....
Is this part a variable part ( so may be a factory reset and a new dump will give a more comparable result ), or is there a real difference for two same version of the firmware ??
Can you tell me for upgrading the firmware of the tomtom have you used the full 3.11 firmware from 0 to 7FFFF or have you used a dump from 0 to 79999 ?
seeing the various problems some got after flashing their units I am a bit worried before flashing mine..
thanks
Laurent
Just do a system reset of your device and dump it again.
Depending how fast you are getting it into bootmode you have some data there (and not all default empty data). Doing the same after some time (e.g. after a fix was established) will again deliver different data there.
I think the main thing here is that the WHOLE data are dumped and then later flashed to another device. This may also be the rootcause of the failure to use the 0-79999 dump - where after 79999 data may confuse the device to get back online (very sad - it already cost 2 devices one BT338 and one TomTom MkII).
I have used my own dumps to crossupgrade from BT338 to TomTom and the 3.2.2 from antineutrino. After some back and forth I am on 3.2.2 again currently for all devices (living with the green-LED off until a fix).
BTW: I am quite sure that the bluetooth part is not touched by these updates.
The names of the devices as they are recognized on bluetooth are not changing after a FW update.
thanks tobbie ,
as I need this gps in the coming next weeks, I will not take the chance to do the upgrade just now. I will wait a quiter period of time to try it ( so if I brick it I will have time to make a replacement ).
thanks, I will come back for detailled instructions in some weeks.
Laurent
Hi Tobbbie,
I have a Globalsat BT 338, I would like to update the firmware. I downloaded your dumps from http://www.gpspassion.com/forumsen/t...5&whichpage=11, the 3.1.1 version.
Do I understand well that even exists a 3.2.2 version?
If yes where could I find it?
Thanks
patek
It's in the same forum a few post further down - it comes from another member there - just look it up.
Edit: just checked - it seems only the 3.2.4 of the BT368 is there.
I have edited my old post there with a new link that has all info - also for short here:
http://rapidshare.de/files/41287744/Firmware_Globalsat.zip.html
Please read the GPS passion forum entries very thoroughly - it MUST be complete dump that you insert - anything less than 512kB will kill your device (as a poor forum member there had to suuffer)..
Tobbbie,
Thank you for your prompt answer,
I checked my software version, Sirfdemo says: GSW3.1.1LowV_3.1.00.07-c23B1.00 - the same what yours was before upgraded.
I read your opinion about changing to 3.2.2 :
>As mentioned earlier I have yet to discover advantages of 3.2.2 or 3.2.4 over 3.1.1. I >think some trickle power options are more flexible and the DGPS could work - but so far I >could never get a DGPS fix.
So do you think is it worth enough to upgrade? (green lamp!)
Is the WAAS enabled in the 3.2.2 ? (maybe silly question)
Thanks
tobbbie said:
It's in the same forum a few post further down - it comes from another member there - just look it up.
Edit: just checked - it seems only the 3.2.4 of the BT368 is there.
I have edited my old post there with a new link that has all info - also for short here:
http://rapidshare.de/files/41287744/Firmware_Globalsat.zip.html
Please read the GPS passion forum entries very thoroughly - it MUST be complete dump that you insert - anything less than 512kB will kill your device (as a poor forum member there had to suuffer)..
Click to expand...
Click to collapse
hmm, i haven't used my trusty bt338 in quite some time, i might upgrade it just to see what happens..
In amss.bin you can find several AT Commands...
Few short tested by me:
AT+DEVEXTMEMINSCHK?
Hmmm. returns only 2
No idea, I thought something for Memory...
AT+USERMEM
Returns 0k or maybe okay
AT+HEADERINFOSHOW?
Shows for instance the Memory name...
MemoryName:KAC007021M(S8500)
Btw... This is exact what we can read on Application Processor Chip.
1 hint that RAM is integrated with S5PC110 Processor...
Best Regards
TRY at your own risk. I have no idea what could happen.
s8500 support several types of at commands.
First type is common at commands set (70 commands), including AT+CPIN, AT+CMGR etc
the second (samsung specific, 171 commands) has many useful commands like etc
s8500 support 293 at commands (including common commands like AT+CPIN, AT+CMGR, and samsung specific like AT+IMEITEST, AT+CPU also)
complete list in attachment.
Do not use if you do not know what the command is for
AT+PRODUCTCODE?
Result:
AT+PRODUCTCODE? +PRODUCTCODE: GT-S8500BAADBT
If I enter:
AT+PRODCODE
Result:
Invalid Parameter
Hmmm. I'm not up to date in using AT commands.
Is it maybe possible to change Product Code via AT Command?
How is the correct Syntax for AT+PRODCODE ?
There are more interesting Commands.
Best Regards
P.S.:
I was only in Kies Mode, maybe other results in Debug Mode possible...
AT+DEVCONINFO
MN(GT-S8500);BASE(GT-S8500);VER(S8500XXKK7/S8500OXAKK7);HIDVER(S8500XXKK7/S8500OXAKK7);PRD(GT-S8500BAADBT);SN();IMEI(3xxxxxx3);PN();TZVER(20111025);CON(AT,MTP);HVID(Osp:2097153,IntSys:2097154);LOCK(NONE);LIMIT(FALSE)
Oh, not realized before... few changes...
On previous bada 1.x... looks like this:
MN(GT-S8530);VER(S8530XXJL2/S8530OXFJK3);HIDVER(S8530XXJL2/S8530OXFJK3);PRD(GT-S8530BAASEB)
MN should be manufacturer I think... this is very funny text string.
Best Regards
Edit 1.
My fault... MN is Model Name...
Ooh, this reminds me of the days when I had a SonyEricsson T68 and K750.... Good ol days ... One thing missing from those days .. Our samsung wave telephones don't do the Bluetooth HID protocol...
How do you send these commands?
Can you post output from:
AT+DGLOCK
AT+LVOFLOCK
AT+DETALOCK
?
How do you send these commands?
Click to expand...
Click to collapse
You can choose... there are hundrets of Tools, or write your own Terminal...
Few Tools I've used for this...
Revskills very often...
WinComm
QuB...
.
.
AT+DGLOCK
AT+LVOFLOCK
AT+DETALOCK
Click to expand...
Click to collapse
I'm little wimpy old man as you know...
But as I have 0 info about this... I'm scared to lock something and brick my handset...
No idea how to unlock ...
I'll investigate more...
Google research etc. and report later more... I'll try to be on the safer site...
About DELTA files/FOTA...
http://www.megaupload.com/?d=Z53R1IVX
I have upload few of S8500.
Maybe we find Commands or way to install manually these *.cfg Deltas...
Maybe AT Command also work...
Best Regards
Edit 1.:
Found this... untested yet:
Code:
AT+FOTALOC
AT+FOTAREADY
AT+FOTASTART
Edit 2...
Or maybe more such DEV Commands...
GetFotaEngineVer
Get FOTA Engine Version
Edit 3...
Maybe for Update... beter search for something like this:
SML_DM_FUMO_STATE
Or SCOMO
SCOMO Download Complete go to ui event 1...
SCOMO...Warning!!!! Delta Over Size
DownloadAndUpdate...org.openmobilealliance.dm.firmwareupdate.devicerequest
http://www.openmobilealliance.org/t...ram/docs/ets/oma-ets-fumo-v1_0-20061215-c.pdf
I'm sure LVOFLOCK gets level of lock - doesn't overwrite anything
The same about DETALOCK (detailed lock)
Just don't remember what was the code for DGLOCK, so don't use it for now if u're scared. You won't find these in google I think, these are Samsung specific, maybe only Mocha specific.
//edit:
Btw, many of AT commands goes to AMSS, but only what AMSS do is calling Mocha function in AP corresponding to AT command and returning result. For eg LVOFLOCK make AMSS invoke Bada function (also accessible from QuB) GetLevelOfLock and get it's return value. Can you compare result of these 2 maybe?
http://electronix.ru/forum/index.php?act=attach&type=post&id=46875
Tested by me...
AT+FOTALOC?
: Others
This seems location... folder... Others
AT+FOTAREADY?
COPYRETRY
But AT+FOTASTART seems correct...
Handset reboots... like if I delete *.cfg files...
Hmmmmmmmmm.
Will log with WinComm... maybe then more info...
Best Regards
At+preconfig=2,tmb
at+lvoflock=1,0
at+factrst=0,1
at+lvoflock=0,0
600 pages FOTA OTA Command with explain :
http://www.scribd.com/doc/63560940/47/FOTA-Commands
http://www.google.fr/url?sa=t&rct=j...sg=AFQjCNFTQzBSwRrZg82TEZSOleqClg4dbA&cad=rja
AT+FOTASTART 2400258.cfg
Error...
AT+FOTASTART after Download of package, not start downloaded update.
Maybe wrong syntax or FOTA of Qualcomm part only... amss.bin...
I can't see anything with WinComm... maybe next try with QXDM... if amss related...
@ Tigrouzen
Many thanx for helpfull Links.
Best Regards
adfree said:
AT+FOTASTART 2400258.cfg
Error...
AT+FOTASTART after Download of package, not start downloaded update.
Maybe wrong syntax or FOTA of Qualcomm part only... amss.bin...
I can't see anything with WinComm... maybe next try with QXDM... if amss related...
@ Tigrouzen
Many thanx for helpfull Links.
Best Regards
Click to expand...
Click to collapse
But i remember some time Samsung change this thing like not AT+FOTAUIMODE but
AT&FOTAUIMODE
Now its work but no Carrier
In our wave AT+CPIN doesnt work but AT&CPIN works
Code:
AT+FOTALOC?
AT+FOTAREADY?
AT+FOTASTART
Short tried on bada 1.0... JE7 Firmware...
All 3 output was Error...
Okay, not included in amss...
2400258.cfg also as text String in apps_compressed...
Will play little bit with Delta... then move to XXJL2...
Best Regards
Little progress...
AT+DEVCONINFO
Code:
MN(GT-S8600);VER(S8600XXKJC/S8600DBTKJ4);HIDVER(S8600XXKJC/S8600DBTKJ4)...
My S8500...
Best Regards
Did you get S8600 fw on your S8500 !!!!
Man this JTAG playing could kill your phone
Best Regards
Nah, he got FW ID from S8600 on S8500, while S8600 ShpApp & RC may be possible to run on S8500 and vice versa, rather no way about other things. ;P
"DEVCONINFO"="MN(GT-S8600);BASE(GT-S7250);VER(S8600XXKK5/S8600DBTKL1);HIDVER(S8600XXKK5/S8600DBTKL1);PRD(GT-S8600HKADBT)
Click to expand...
Click to collapse
Many thanx to S8600 user for nice info.
Best Regards
AT+SECUKEY +SECUKEY:"DXDxxxxxxxxxxxx=="
OK
AT+AUTHKEY +AUTHKEY:FAIL
OK
AT+DEVAUTH +DEVAUTH:SUCCESS
OK
AT+CERTKEY +CERTKEY:"X5Mxxxxxxxxxxx=="
OK
AT+PASSWORDINPUT +PASSWORDINPUT:SUCCESS
OK
Found Commands in WsSyncml.so, see here:
http://forum.xda-developers.com/showpost.php?p=21541765&postcount=4
No idea yet, what it is.
Best Regards
b.kubica said:
complete list in attachment.
Click to expand...
Click to collapse
Nice post b.kubica
Are you aware of the Qualcomm commands?
AT+CLAC lists these extra commands:
$QCSIMSTAT
$QCCNMI
$QCCLR
$QCDMG - Diagnostic Mode initiation.
$QCDMR - Diagnostic Mode (Baud) Rate. at$qcdmr=? shows available baud rates, at$qcdmr? shows current baud rate
$QCDNSP
$QCDNSS
$QCTER
$QCSLOT
$QCPINSTAT
$QCPDPP - Packet Data Protocol authentication Parameters - see w w w . shapeshifter . se/2008/04/30/list-of-at-commands/
$QCPDPLT
$QCPWRDN
$QCDGEN
$BREW
$QCSYSMODE
$QCCTM
$SUSBC
$NWMDCHNG
$SHPSLEEP
Not sure what they do. All I've found so far is at$qcsysmode restarts the phone with what looks like a file list coming out on the serial port. BREW is the Qualcomm application language.
Does AT_OWANCALL exist in the ROM? That is sometimes used to set up UMTS/HSDPA connections.
Does anyone still have the 1.0 apk?
I upgraded to 1.1 now it will not find my sprint modem and problems here and there.
Here you go..... [removed]
taqulic said:
Here you go..... http://db.tt/jnAqmyXk
Click to expand...
Click to collapse
Thank you so much, to bad I can only give you one thanks :laugh: , now everything is working again. I dont know what the dev changed on the update but something did dealing with the sprint modem..etc. and it all went down hill.
Seems like someone else had that problem too.... thought I read it in the reviews..
taulic,
please be so kind and remove the public access to the APK file.
The original package is fixed now.
Note that the program itself is free of cost but not free to copy. If people run into trouble I will provide older versions when asked.
Regards,
Author of PPP Widget
JFDee said:
taulic,
please be so kind and remove the public access to the APK file.
The original package is fixed now.
Note that the program itself is free of cost but not free to copy. If people run into trouble I will provide older versions when asked.
Regards,
Author of PPP Widget
Click to expand...
Click to collapse
Done.
PPP works once, then ned to re-installed
taqulic said:
Done.
Click to expand...
Click to collapse
Hi There,
The app works fine when I install it first, my dongle i being recognized no problem. However if I disconnect, and unplug the dongle and try to connect again, the widget shows "no modem found".
I have tried forcing the app to stop, uninstall stickmount as I thought there was clash between both apps and still it doesn't work. the only work around I v found is to re-install the app, which is not very convenient when on the go and needing internet in the first place to be able to access it.
Would you be willing to provide me the APK installer as I am quite happy to install the app whenever I need it, or maybe suggest a workaround?
you have done a fantastic job by the way
G
file is no longer available
Will you please re-upload the file (PPP wedget 1.00 APK) in drop box since the hyperlink says (The file you are looking for has been deleted or moved). Thank you very much
You should first, email the author of the app and see if he can help you with your problem.
I'm not sure I still have the app in backup... as I only save them for so long. (But I'll check).
For those people having problems with this app, there is a forum and active discussion
Here, click forum link at bottom of page.
http://www.draisberghof.de/android/pppwidget.html
Will you please email this file; thanks
Unknown Zone said:
Thank you so much, to bad I can only give you one thanks :laugh: , now everything is working again. I dont know what the dev changed on the update but something did dealing with the sprint modem..etc. and it all went down hill.
Click to expand...
Click to collapse
Dear "Unkown Zone", will you please email this file (PPP Widget 1.00); thanks
Please email link
Unknown Zone said:
Does anyone still have the 1.0 apk?
I upgraded to 1.1 now it will not find my sprint modem and problems here and there.
Click to expand...
Click to collapse
If you have older version of PPP Widget 1.00 (apk file), please post a link. I have tried many changer.bat options since your last post; both uberoid v11 and 12.1. Nothing seems to work so far to make the ZTE-MF190 work again since upgrade from stock ROM. Tried 2 look for this file however no success. Thank you.
Deleted.
samsung note i717 no drivers found
PPP Widget version 1.3.3
USB_ModeSwitch log from Tue Sep 24 21:36:19 IST 2013
Raw args from udev: 1-1/1-1:1.0
Using top device dir /sys/bus/usb/devices/1-1
----------------
USB values from sysfs:
manufacturer ZTE, Incorporated
product USB Storage
serial 000000000002
----------------
bNumConfigurations is 1 - don't check for active configuration
SCSI attributes not needed, moving on
checking config: /data/data/de.draisberghof.pppwidget/app_tmp/19d2.fff5
! matched. Reading config data
devList 1:
config: TargetVendor set to 19d2
config: TargetProductList set to fff1,fffe,ffff
Driver module is "option", ID path is /sys/bus/usb-serial/drivers/option1
Command to be run:
usb_modeswitch -I -W -D -s 20 -u -1 -b 1 -g 2 -v 19d2 -p fff5 -f $cB
Verbose debug output of usb_modeswitch and libusb follows
(Note that some USB errors are to be expected in the process)
--------------------------------
Reading long config from command line
* usb_modeswitch: handle USB devices with multiple modes
* Version 1.2.7 (C) Josua Dietze 2012
* Based on libusb0 (0.1.12 and above)
! PLEASE REPORT NEW CONFIGURATIONS !
DefaultVendor= 0x19d2
DefaultProduct= 0xfff5
TargetVendor= 0x19d2
TargetProduct= not set
TargetClass= not set
TargetProductList="fff1,fffe,ffff"
DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
QisdaMode=0
QuantaMode=0
GCTMode=0
KobilMode=0
SequansMode=0
MobileActionMode=0
CiscoMode=0
BlackberryMode=0
PantechMode=0
MessageEndpoint= not set
MessageContent="5553424312345678c00000008000069f030000000000000000000000000000"
NeedResponse=0
ResponseEndpoint= not set
InquireDevice disabled
Success check enabled, max. wait time 20 seconds
System integration mode enabled
Use given bus/device number: 001/002 ...
Looking for default devices ...
bus/device number matched
searching devices, found USB ID 19d2:fff5
found matching vendor ID
found matching product ID
adding device
Found device in default mode, class or configuration (1)
Skipping the check for the current configuration
Using interface number 0
Using endpoints 0x0a (out) and 0x89 (in)
USB description data (for identification)
-------------------------
Manufacturer: ZTE, Incorporated
Product: USB Storage
Serial No.: 000000000002
-------------------------
Looking for active driver ...
OK, driver found; name unknown, limitation of libusb1
OK, driver "unkown" detached
Setting up communication with interface 0
Using endpoint 0x0a for message sending ...
Trying to send message 1 to endpoint 0x0a ...
Sending the message returned error -6. Trying to continue
Resetting response endpoint 0x89
Could not reset endpoint (probably harmless): -6
Resetting message endpoint 0x0a
Could not reset endpoint (probably harmless): -6
Device is gone, skipping any further commands
Bus/dev search active, referring success check to wrapper. Bye.
ok:busdev
--------------------------------
(end of usb_modeswitch output)
Checking success of mode switch for max. 20 seconds ...
Waiting for device file system (1 sec.) ...
Reading attributes ...
Mode switch has completed
Mode switching was successful, found 19d2:fff1 (ZTE, Incorporated: ZTE CDMA Tech)
Device class of first interface is ff
Now checking for bound driver ...
No driver has bound to interface 0 yet
Module loader is /system/bin/insmod
Trying to find and install main driver module "option"
Checking for active driver path: /sys/bus/usb-serial/drivers/option1
Driver not active, try to find module "option"
Can't find module "option"
Existing path found:
No way to use driver "option"
- try falling back to "usbserial"
Module "usb_serial" not found, can't do more here
Driver binding did not work for this device
All done, exiting
QUOTE=taqulic;34223799]Here.
http://www.filesend.net/download.php?f=4c6891af31cb635623fac53e094def52[/QUOTE]
Sir,
Using samsung note i717with official jb rom 4.1.2, ppp app says driver not found, device log is as above. Request you to help in this regard.
As after the stable release of Android 10 to our device, there is a "+" icon next to your network setting.
But i am just not able to get it configured.
At the beginning of the process it says.." download your sim" if u don't have a physical one and when i proceed with that option it loads for a while and pops up cannot download..SS attached.
And while doing this you have to be on a wifi network as it disables your currently inserted sim..thats that.
Are you sure it's going to work for P2XL? Was it working in any of the betas?
It happened to me in beta i guess you have to factory reset your phone and everything should be ok it worked for me just don't forget to back up your data
No need for factory resetting just download the latest sim manager from the play store or if it's not available to you yet you can also download it from apkmirror,i am referring to version D.1.5.73, now you should be able to scan a qr code to setup esim
P.S if you have any problem setting up esim keep us updated
The latest sim manager version available on apkmirror is D.1.5.71
Can you post a link to version 73? Because 71 shows same error as shown in a screenshot in the first post. Can you guys use other carrier that Google Fi on Pixel 2 xl?
xnova35 said:
The latest sim manager version available on apkmirror is D.1.5.71
Can you post a link to version 73? Because 71 shows same error as shown in a screenshot in the first post. Can you guys use other carrier that Google Fi on Pixel 2 xl?
Click to expand...
Click to collapse
Here you go
https://www.apkmirror.com/apk/google-inc/esim-manager/esim-manager-d-1-5-73-google-5793666-release/
Wow! Just wow, it works!! At least QR code scanner, I'll need to go to my operator to get a QR code to try it of course.
Great change, huuuge thanks to @kastik4, I was waiting for it in Android Q release, but problem was obviously in esim-manager.
Ok then back to the thread topic - anybody has DSDS (Dual sim dual standby) working on Pixel 2(XL)?
I checked with two of my operators.. They gave me the QR codes, but our phone isn't able to download the profiles. I keep getting "Network not activated" error.
hymnz said:
I checked with two of my operators.. They gave me the QR codes, but our phone isn't able to download the profiles. I keep getting "Network not activated" error.
Click to expand...
Click to collapse
That's exactly the same that I experienced today - I went to a Czech Vodafone and they told me that Pixel 2 isn't able to use Czech e-sims, but Pixel 3 does. I tried to reach Google, but they just ignored my call request, will try tomorrow.
Anybody was successful in downloading e-sim? Is there any physical difference or it's just a software certification? In latter case we could overcome it with software hacks.
According to Google support, it's error with network operator and I'm to check with them. Network people say p2xl isn't in their list of supported devices. WTH. I'm sure it's a software thing.
P.S. It's not going to be DSDS mode, it's DSSS mode only. Only one sim/connection active at a time
@xnova35 , did you get any response from Google?
hymnz said:
@xnova35 , did you get any response from Google?
Click to expand...
Click to collapse
@hymnz, Imagine, Google is ignoring me!! I request a call from Tips&Support section in my phone (btw it says nonstop 24/7 help), several times it confirmed me that "Specialist will call you as soon as possible" and nothing.
I searched for number I could call, but didn't find any which would lead to Pixel help. Does anybody has a number to call, preferably in US or Europe?
I didn't find any proof that Pixel 2 and 3 in e-sim are physically different. So my guess is if phone will report itself as "Pixel 3" (can be done with rooting) it could work. I was surprised that there are no "Pixel 3" Roms for Pixel 2 - all features and structure ported to our model.
xnova35 said:
@hymnz, Imagine, Google is ignoring me!! I request a call from Tips&Support section in my phone (btw it says nonstop 24/7 help), several times it confirmed me that "Specialist will call you as soon as possible" and nothing.
I searched for number I could call, but didn't find any which would lead to Pixel help. Does anybody has a number to call, preferably in US or Europe?
I didn't find any proof that Pixel 2 and 3 in e-sim are physically different. So my guess is if phone will report itself as "Pixel 3" (can be done with rooting) it could work. I was surprised that there are no "Pixel 3" Roms for Pixel 2 - all features and structure ported to our model.
Click to expand...
Click to collapse
Did you try text chatting with support? Do you have that option?
hymnz said:
Did you try text chatting with support? Do you have that option?
Click to expand...
Click to collapse
@hymnz, no, there's no chat option anymore (however it used to be there), of course I would have used it.
hmm, i'm on the latest sim manager app, but still haven't received QR code scanning feature.. any ideas?
morpig2 said:
hmm, i'm on the latest sim manager app, but still haven't received QR code scanning feature.. any ideas?
Click to expand...
Click to collapse
Install this https://www.apkmirror.com/apk/google-inc/esim-manager/esim-manager-d-1-5-73-google-5793666-release/
Any update from anyone who has tried?
I have just tried to install the latest version of SIM Manager by Google from APKMirror on Lineage OS 18.1 (Android 11) running on Google Pixel 2.
With the updated version of the SIM Manager, I was able to get the phone to display a new user interface for adding an eSIM by scanning a QR code. However, the process got stuck on the spinner animation immediately after scanning the QR code. The phone did not freeze but it would never move on to the next part of the eSIM provisioning process.
In the adb log, I could see messages like these:
Less:
W GooglePlayServicesUtil: com.google.android.euicc requires the Google Play Store, but it is missing.
which I do not understand because I *do* have Google Play Store and Google Play Services installed. I have also tried to update them to the latest versions available on APKMirror but the behavior remained the same.
During an attempt to provision an eSIM, the following messages seemed to be relevant:
Less:
I EuiccGoogle: [2] CarrierInfo.createCarrierFromJson: Received empty carrier jason string
I EuiccGoogle: [182] EuiccServiceImpl.ensureSlotIsEuiccAndActive: Passed in slotId=-1; euiccIsActive=false; targetSlotIsRemovable=false; forceDeactivateSim=false.
I EuiccGoogle: [182] EuiccServiceImpl.onGetDownloadableSubscriptionMetadataInternal: onGetDownloadableSubscriptionMetadataInternal: slotId = -1, forceDeactivateSim = false, ensureSlotIsEuiccAndActive = Pair{-1 false}.
I EuiccGoogle: [182] EuiccErrorMapper.mapErrorCode: Result: EuiccServiceError - -1
I EuiccGoogle: [182] EuiccServiceImpl.onGetDownloadableSubscriptionMetadata: onGetDownloadableSubscriptionMetadata errorCode: -1
...
E EuiccGoogle: [134] ClearcutServerLog$1.doInBackground: Cannot connect to GMS API client.
E EuiccGoogle: com.google.android.gms.common.api.ApiException: 17: API: UsageReporting.API is not available on this device. Connection failed with: ConnectionResult{statusCode=SERVICE_INVALID, resolution=null, message=null}
The part which seems suspicious is "Received empty carrier jason string" but I am not sure what it refers to exactly. It seems like getting the eSIM metadata fails for some reason.
I have root access via Magisk so I have installed the MagiskHide Props Config module, changed the device fingerprint to Google Pixel 3 and also activated the device simulation and enabled the simulation of all the related props. Then I have tried to repeat the eSIM provisioning again but the outcome remained the same.
With the root access, I believe that I should be able to somehow arrange that the regular eSIM provisioning via QR code works. But I do not know which parts need to be adjusted and how.
Does realme X support carrier aggregation?
I think this device support 2CA but i don't combinations so then i can't confirm network support. Someone who have this device please get logs https://mt-tech.fi/en/how-to-get-4g...droid-phone/#OnePlus,_Oppo_and_RealMe_devices and send these to so i can add this device to my site: https://cacombos.com/contribute
I have few Oppo devices listed already: https://cacombos.com/search?key=Oppo
U want this log?
https://drive.google.com/file/d/1Ggn5S-fiHAOXk7km7ysgH6Szff019QrH/view?usp=drivesdk
rupeshmaurya35 said:
U want this log?
https://drive.google.com/file/d/1Ggn5S-fiHAOXk7km7ysgH6Szff019QrH/view?usp=drivesdk
Click to expand...
Click to collapse
Thank you for the log but there missing some information. Can you test again but wait little bit longer so your device connect to 4G back. Also i need your device model number, you can find it on Android Settings -> About so then i can add it to my site.
Ok, here is the log
And my device is RMX1901 Global variant
And please let me know about the process if it supports 2CA .
And by the way I am using NSG but i don't have Premium licences ,so i can't load log file from NSG. I use it for band locking only.
https://drive.google.com/file/d/1HNVJ8j7JNzoy94cXSMRGLyU7jBHPyItd/view?usp=drivesdk
rupeshmaurya35 said:
Ok, here is the log
And my device is RMX1901 Global variant
And please let me know about the process if it supports 2CA .
And by the way I am using NSG but i don't have Premium licences ,so i can't load log file from NSG. I use it for band locking only.
https://drive.google.com/file/d/1HNVJ8j7JNzoy94cXSMRGLyU7jBHPyItd/view?usp=drivesdk
Click to expand...
Click to collapse
Sorry again but this log file did not again include any combos. So you have to first start log recording on Get QXDM log -> open device log. Then put your phone Airplane mode on and off. Wait minute to get your phone connected to 4G-network. Then repeat this step few times. Then you can close log and share log file.
Oh yes NSG Premium only allow reading logs and Signaling data.
I have done the same last time , check screenshot for values may be something wrong there.
rupeshmaurya35 said:
I have done the same last time , check screenshot for values may be something wrong there.
Click to expand...
Click to collapse
Looks like your settings are fine. Open logging, then put your device to Airplane mode on, wait your phone connect to 4G (1min), then put your phone back to Airplane and repeat step. This should include all data in log.
I have tried every possible band and CA is not supported in Realme X
rupeshmaurya35 said:
I have tried every possible band and CA is not supported in Realme X
Click to expand...
Click to collapse
I think Realme support only Contiguous CA but without modem log impossible verify. in cacombos.com/contribute there is instructions how to get log.
olkitu said:
I think this device support 2CA but i don't combinations so then i can't confirm network support. Someone who have this device please get logs https://mt-tech.fi/en/how-to-get-4g...droid-phone/#OnePlus,_Oppo_and_RealMe_devices and send these to so i can add this device to my site: https://cacombos.com/contribute
I have few Oppo devices listed already: https://cacombos.com/search?key=Oppo
Click to expand...
Click to collapse
LTE RRC OTA Packet
version : 20
phyCellId : 231
freq : 1251
sfn : 0
Channel : 8
ul-dcch
message -> c1 -> ueCapabilityInformation
rrc-TransactionIdentifier : 2
criticalExtensions -> c1 -> ueCapabilityInformation-r8
ue-CapabilityRAT-ContainerList
[0]
rat-Type : eutra
ueCapabilityRAT-Container
accessStratumRelease : rel12
ue-Category : 4
pdcp-Parameters
supportedROHC-Profiles
profile0x0001-r15 : true
profile0x0002-r15 : true