Develop Bugs

[Q] Looking for anyone who can provide custom ROM

Greetings,
My name is Don and our company works in the field of mobile network testing, we are basing our solution on Qualcomm chipset. We have all the necessary licenses from Qualcomm required for decoding layer 3 messages and we understand that some phones' diagnostic mode can be enabled through diag coded (*#197428640 for Samsung).
However, we desire a more permanent solution that can be applied across multiple devices, we are looking for anyone who can provide us with a custom android firmware image for Android phones that gives USB access to its qualcomm diagnostics port and must work with QXDM. If a general solution can't be found then the ability to connect to HTC phones and some selected models would sit well with us.
I don't know if this is the right forum for this kind of posting and if it's not I apologize.

Hit a snag and need some guidance I feel dumb

Im trying to use CDMA workshop on my EVO and I cant seem to get HW Virtual Serial Port version 2.5 to create a com port. I keep getting ping reply failed port not created. I never had a problem with my rhodium but this EVO is being a pain.
Can anyone walk me through opening a Com port for the EVO? im running windows 7 home 32bit if it matters...
thanks

so no one knows how to open a com port for the evo?

If you put the phone in diagnostics mode the computer will ask you for a driver for the serial port (COM) which later you can use for CDMA
WS. So you might be misding one of the two: diag mode or port driver.
Sent from my PC36100 using Tapatalk

I have the Diagnostic drivers, which one is diagnostic mode? is that volume down and power? or ##3424#?
I know I have all my drivers. but what is the port driver?

[Q] Com Port when connected to PC?

I have a program I am fiddling with called CDMA workshop which allows you to do...well pretty much anything to any CDMA phone you have connected to the PC, from reading/writing MSLs, lock codes, ESNs, PRLs, and a host of other stuff. Works easily with feature phones, but it requires you to put what com port the phone is using so it can connect to it. It's easy on feature phones, as soon as you connect it, the phone shows up under ports and tells you what it is using. However, when I connect a smart phone, an Epic Touch in my case, it doesn't show up under that. It only shows under USB controllers and ADB Device.
Does anyone know how to pull this up? Or do they not even use Com Ports?
Thanks in advance.

Connect it to Odin. It will tell you which Com port once it is connected.
Sent from my SPH-D710 using Tapatalk

Ok, second question: is there a way to change that port, through Odin or anything else, once you find it? This particular version of the software I'm using only recognizes com ports 1-10.

Try this:
http://technet.microsoft.com/en-us/library/cc739900(v=ws.10).aspx
Sent from my SPH-D710 using Tapatalk

when i just checked odin on my pc its com3

drksilenc said:
when i just checked odin on my pc its com3
Click to expand...
Click to collapse
It changes from computer to computer depending on devices and hardware attached.
Sent from my SPH-D710 using Tapatalk

azyouthinkeyeiz said:
It changes from computer to computer depending on devices and hardware attached.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
It also depends on which USB port you plug into on the pc too mine ranges from com 0 - 3 depending on what port I'm in or if I use my hub
We are legion, for we are many
Sent from my Anonymous DeathStar in the depths of GalaXy S2

ahh makes sense i have my cable in the same port for months now

Did you get it working?
Sent from my SPH-D710 using Tapatalk

wizholt7 said:
I have a program I am fiddling with called CDMA workshop which allows you to do...well pretty much anything to any CDMA phone you have connected to the PC, from reading/writing MSLs, lock codes, ESNs, PRLs, and a host of other stuff. Works easily with feature phones, but it requires you to put what com port the phone is using so it can connect to it. It's easy on feature phones, as soon as you connect it, the phone shows up under ports and tells you what it is using. However, when I connect a smart phone, an Epic Touch in my case, it doesn't show up under that. It only shows under USB controllers and ADB Device.
Does anyone know how to pull this up? Or do they not even use Com Ports?
Thanks in advance.
Click to expand...
Click to collapse
You forgot to put your phone in SERIAL MODE ... From the dialer, type :
##8778#
then select CP instead of AP ...
Now go in your computer to DEVICE MANAGER / PORTS / and you will find a new port called something like : SAMSUNG SERIAL PORT ... You will notice that at the end of the port, you will see in parentheses you COM port number.
Good luck, and DON'T BE SHY PRESSING THAT THANKS BUTTON, under my post !!! ... I'm pretty low )

peryp9 said:
You forgot to put your phone in SERIAL MODE ... From the dialer, type :
##8778#
then select CP instead of AP ...
Now go in your computer to DEVICE MANAGER / PORTS / and you will find a new port called something like : SAMSUNG SERIAL PORT ... You will notice that at the end of the port, you will see in parentheses you COM port number.
Good luck, and DON'T BE SHY PRESSING THAT THANKS BUTTON, under my post !!! ... I'm pretty low )
Click to expand...
Click to collapse
Sweet, I'm gonna try that and I'll let you know if it works.

That did the trick! Thanks a lot, I was able to get it connected. Thanks button pressed

[TUTORIAL] Connect and Debug Moto 360 over Bluetooth

Hello all, I've been working on a couple custom apps for my Moto 360, and I'm loving it! After some digging around in the forums, I had a hard time finding DECENT threads that pertained to Bluetooth debugging for your spanky Moto wearable, so here is a quick how-to!
First thing, debugging by Bluetooth is EXTREMELY simple. This does not require you to rip apart your favorite USB cable or perform some electrical engineering Jesus magic to acquire a unique USB connection for ADB. YES, wireless debugging IS possible, and is ONLY ADB capable, NOT FASTBOOT capable!
This means: no, I'm sorry fellow wearabees, you can not root/unlock/or flash partitions through ADB or Bluetooth. It's just not possible, and quite possibly would never be possible due to safe flashing procedures. The chances of bricking a device over a wireless connection is exponentially higher than a cabled connection. This is mostly because of interference, range issues, all together nuclear fallout, or your cat is evil and likes to turn your Bluetooth connections off when you sleep at night (let's pray to Buddha this isn't the case...).
So, let's begin by adjusting a few settings on your 360 and your favorite handheld (that would be your cell phone, dummy):
** Go to your 360 settings and swipe all the way down to the bottom of your semi-circular screen to the About section. Poke your cute little watch face to open About.
**Scroll down in your About section to Build Number and tap that guy 100 times, as fast as possible! (You only need to tap it 7 times, but at least it makes developing fun). This should add a new option in your settings named Developer Options.
**Enter your developer options and enable ADB Debugging, at which point the option below this will become available.
**Select the Debug over Bluetooth option to enable what this whole tutorial is about.
**Now, do the same for your handheld. Tap that Build Number, yeah boy! (Sexual pun intended)
Great! You're one step closer to being Super Sayan! (Not really, I have no affiliation with Dragonball Z)
Ok, now we need to open your terminal/command prompt window and change directory to your ADB executable location. From this location we will need to run ADB:
adb forward tcp:4444 localabstract:/adb-hub
Click to expand...
Click to collapse
then:
adb connect localhost:4444
Click to expand...
Click to collapse
The first command forwards the ADB connection of the phone to the remote connection of the 360 by Bluetooth. The second command simply gets the connection initiated with the remote address.
Now, for safe keeping I will provide two options for giving ADB commands to your 360. The first option should be your preferred option for compatibility reasons:
adb -s localhost:4444 <add you command here>
Click to expand...
Click to collapse
This code directs the command to your specific device. Otherwise, for quick code entry, you may use this:
adb -e <add your command here>
Click to expand...
Click to collapse
This second code is a generic way of connecting to whatever debugging option is available, which doesn't always mean your 360. If you're a developer running debug apps, try not to use this command.
And that's about the basics! Super simple, and all ADB commands are available for your wearable. Don't forget, rebooting into the bootloader through ADB will require a USB connection, at which point also some Jesus magic, and let's hope you're willing to be a god for a day.
Have fun!
**
**

I've tried this and I always get an error "Cannot connect to localhost:4444 no connection could be made because the target machine actively refused it (10061)"
Any solutions? I've tried other ports as well.

Question problem with the type c - pc port

Hi everyone, I wanted to know if this problem was related to a software problem or is it my a52s broken something in hardware
when i connect a cable type-c both side on my pc the data when i connect the mobile phone to a type c port on my pc the peripheral connects and disconnects in quick succession, this only happens when i connect it to a supported type-c port
I have done several tests and I can confirm that the problem is the cell phone, with another cell phone the problem does not exist and I can reach the classic speeds of the type-c gen 2
currently the a52s mobile phone is equipped with android 11 with the one ui 3.1 with root
if someone can do some tests and verify the correct functioning of the port, I kindly ask you to write if you are on android 11 or android 12 with or without root permissions, thank you very much

Try playing with Developer options usb options.
If Developer options are already on, temporarily turn off.
Check Windows Event Viewer for error messages.

blackhawk said:
Try playing with Developer options usb options.
If Developer options are already on, temporarily turn off.
Check Windows Event Viewer for error messages.
Click to expand...
Click to collapse
already check this, on or off the dev option don't change anything. i try also the code *#0808# to change the parameters of the usb, but nothing, the problem still on.

raffybest94V01 said:
already check this, on or off the dev option don't change anything. i try also the code *#0808# to change the parameters of the usb, but nothing, the problem still on.
Click to expand...
Click to collapse
Event Viewer?

raffybest94V01
Did you conected the a52s to another pc to se if the result is the same???

TTmouse said:
raffybest94V01
Did you conected the a52s to another pc to se if the result is the same???
Click to expand...
Click to collapse
i don't have another pc with type c gen 2.
blackhawk said:
Event Viewer?
Click to expand...
Click to collapse
can you give me some apk for the event viewer ?

raffybest94V01 said:
can you give me some apk for the event viewer ?
Click to expand...
Click to collapse
Event Viewer is part of Windows built in management tools...

raffybest94V01 said:
i don't have another pc with type c gen 2.
Click to expand...
Click to collapse
According to the GSMArena listing for this phone, the USB controller only supports USB 2.0 speeds. Assuming this is correct, you will not get better speeds depending on which port of your PC you connect to, no matter how great the PC-side port and/or cable might be.