Database Develop

A Few Noob Questions

Ordered HD7 should have in a few days.
I got the Tmobile version if that makes a difference.
1. Do the apps purchased in market for HD2 be compatible with HD7?
2. Does HD7 have the ability to act as a wifi router like the HD2 does?
3. Do they use the same charging plug?
Thank you to who ever provides answers and not flame.
I have sat here over and hour reading these threads, not clear answers to what I am asking.
I do wish some one would do a feature by feature comparison of the two phones. I got this one simply because I am tired of the lag and problems with my HD2. I know we can flash roms and all that, not to my skills or time frame, i need a phone that the developers provide what every phone should have, if this one does not offer that, then back to nokia we go .
Thank you again.

Hi,
1: No it is a completely different marketplace and apps for Windows Mobile 6.5 are not compatible with Windows Phone 7.
2: No, at the moment you cannot use the phone as a Wifi Router although that may be possible in the future.
3: I'm not too sure, the HD7 uses a micro USB port. From what I've seen it appears that the HD2 uses micro as well but I can't be sure.
If you're looking for a phone that Just works, then Windows Phone 7 is the way to go. No ROM flashes or tweaking to get it better as it's all good out of the box.
Enjoy it!

Thank you, but not good news.
I take it that the windows 7 app market is probably much smaller.
I use the wifi router feature all the time when at clients locations and need to get on line with my lap top. This is a major problem, do you know if it can be used via usb and 3G?
Thank you again.

rysky007 said:
Thank you, but not good news.
I take it that the windows 7 app market is probably much smaller.
I use the wifi router feature all the time when at clients locations and need to get on line with my lap top. This is a major problem, do you know if it can be used via usb and 3G?
Thank you again.
Click to expand...
Click to collapse
no it can not be used to tether at this time. Only for the lg and samsung has tethering been figured out. The phone is capable of it, you just have to get into a hidden menu that has not been found on the htc hd7 yet.
uhhh, the wp7 marketplace already has over 2k apps the first month...

nrfitchett4 said:
no it can not be used to tether at this time. Only for the lg and samsung has tethering been figured out. The phone is capable of it, you just have to get into a hidden menu that has not been found on the htc hd7 yet.
uhhh, the wp7 marketplace already has over 2k apps the first month...
Click to expand...
Click to collapse
Where do you see them on line? went to WM7 site, only showed me about 100 apps or so, maybe I am looking at wrong area.
Any idea of a time line or has any one heard of when we will be able to use the wifi router feature on this phone? without this feature, the phone becomes useless to me for work

rysky007 said:
Where do you see them on line? went to WM7 site, only showed me about 100 apps or so, maybe I am looking at wrong area.
Any idea of a time line or has any one heard of when we will be able to use the wifi router feature on this phone? without this feature, the phone becomes useless to me for work
Click to expand...
Click to collapse
http://www.bing.com/browse?g=wp7#toc=0

Thank you.

[Q] USB Not Recognized.

So I got my Samsung Galaxy Tab (sprint CDMA version) today and when I first plugged it into my computer the drivers installed fine. I was able to mount the sd card and transfer files with ease. I then proceeded to root the device hoping to put a new rom on it, I've got a captivate and am not a rookie at all when it comes to flashing roms via odin, cwm, etc...I first put the device into debugging mode which is where things got weird. As soon as I put the device into debugging mode and plugged it in via usb it immediately became "unrecognizable". I have the correct updated drivers for the device both from the Samsung website and via the Android SDK tools. There should be no reason why this happened. So I then took it out of usb debugging and plugged it back in and bam, again, "USB Device not recognized". I've been installing and uninstalling drivers, the device itself from the device manager, and have been trying other numerous ideas. I've been Googling and searching for hours upon hours at this point and don't know what to do next. Odin does NOT recognize the device when in download mode and the device does charge when connected to the computer. I have tried a different cord with the device and different computers and it's all the same story, works until debugging is enabled then it will no longer work no matter what. I am fairly sure at this point the device itself is malfunctioning or defected but I wanted the opinion of others before sending it back. I am pretty sure have tried everything and am doing everything right. Please help if you can, if not I still appreciate your time! Specs are listed below:
Hardware Version
P100.08
Model Number
SPH-P100
Firmware Version
2.2.1
Kernel Version
2.6.32.9

Ebicoustic said:
As soon as I put the device into debugging mode and plugged it in via usb it immediately became "unrecognizable".
....the device does charge when connected to the computer.
Click to expand...
Click to collapse
1. Just wondering, have you installed Kies before connecting the tab to your PC?
2. The SGT will not charge "normally" with a USB connection. It will trickle charge, which is very slow way of charging, and the device will not indicate that it is charging. Does your device indicate it's charging? (As stated above)
Hit thanks if I deserve it..

FWIW, My SPH-P100 Sprint Galaxy Tab has been an adventure as well. Enough so that I wish I'd known more and held out for a GSM model.
I am not even sure if Kies and/or Odin will in fact work with the Sprint GT. I've had almost no luck with a variety of attempts. Even the widely used ClockWorkMod Recovery does not include the Sprint GT among its list of supported devices. It does include the CDMA Verizon GT - and some folks have posted that they eventually got that to work.
I did get the SuperOneClick to work and setup root privileges on my tab. That part works fine. But so far I've been reluctant to experiment too much with the various tools that "almost appear that they should work" as I have too little experience with this Android tablet environment to feel comfortable that I can recover from the eventual disaster.
Am hopeful that Samsung will in fact follow through on their commitment to provide upgrade of all GTs to Gingerbread 2.3.3. If so that may be enough for my needs. I WOULD like to get the Netflix viewer app working. Is frustrating to already have a Netflix account and not be able to access it via my GT. A guy down the hall can get Netflix on his Droid X - which really bugs me! lol
IMHO, Google/Samsung/Motorola/HTC/etc. have done a horrible job rolling out Android - both on phones and tablets. Netflix really highlighted this when they decided to do device-by-device testing and certification before allowing Android devices access to their movies. Apparently the 'capabilities' inherent to various Android devices varies so much (and not just OS version) makes it difficult to roll out something as simple as Netflix access. It is frustrating. And the only "solution" so far is to wildly 'hack' your device in the hope that you'll shake something loose enough to make it work as you wished it had when you bought it.
Enough whining for now. But it has been a very frustrating and disappointing experience.

I installed Kies AFTER installing drivers and connecting the tablet and it has no effect. I also learned after googling that kies does not support the sprint cdma version though I could be wrong but many people have stated this. And the device does charge and does so very fast actually, 20% to 100% in 4 hours. I don't think it's trickling down as you say because it is very clearly charging at a fast pace. Thanks for the quick response though! And I have also tried superoneclick root and other methods i.e odin but neither can find the device. I know some people have had luck with this sort of thing after upgrading the rom and/or flashing firmware onto the device which I would love to try but unfortunately without windows being able to see the device, none of this is even remotely possible.

I think the reference to slow charging on USB is really refering to using a data USB port on a notebook or desktop computer. This is because the data USB ports are limited in how much current they will pass. My SPH-P100 will in fact charge on a data USB port - but very, very slowly. In fact if the device is ON it may just barely be breaking even.
The USB charger is certainly capable of charging at a very reasonable rate.
I'm still waiting on the 2.3.3 update that Samsung has promised. It only took them 5 months to get the 2.2.1 update out for my Fascinate! So maybe we'll see the 2.3.3 update by Thanksgiving...or Christmas...or...

[Q] How can I tell what firmware my chromecast has?

I have just received a chromecast in its box. How can I tell what firmware is on the device? If it is still original firmware I'd like to root it. I didn't see this question posted elsewhere.

You must not allow the chromecast to connect to a wifi ssid / network which has Internet.
In my case, I had an old asus (dd-wrt) router laying around. I powered it up with nothing plugged into it. No rj45 cat 5/6 cables connected. Switched my phone wifi to this wireless ssid network. Ran the chromecast app, it found the chromecast, set up the chromecast to use this no Internet network by selecting it & typing in the router's password. After setting up the chromecast, the app shows the firmware version as being 12072.
If you allow the chromecast to connect to a wifi network which has Internet, then it will quickly auto update to a firmware version which can not currently be rooted

View attachment 2246393
It's tucked away a little in the chromecast app, but this should help some.
Arrow points to the firmware version location

Medicstud007 said:
I have just received a chromecast in its box. How can I tell what firmware is on the device? If it is still original firmware I'd like to root it. I didn't see this question posted elsewhere.
Click to expand...
Click to collapse
Just get the chromcast app and select the chromecast u are using. Then look at pic below should be there.
Sent from the TermiNOTEr 2!

Thank you all my build is 12072 which means I can root it. I believe I saw a thread on here somewhere which gave more detailed instructions on how to root the device. Where is the correct file to flash to root the device without having to worry about pesky updates?

Medicstud007 said:
Thank you all my build is 12072 which means I can root it. I believe I saw a thread on here somewhere which gave more detailed instructions on how to root the device. Where is the correct file to flash to root the device without having to worry about pesky updates?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=45176635&postcount=133
I suggest you read the beginning few pages of the thread before flashing though.

Dying to know my fw version
Hello,
I've thoroughly read the instructions on how to root my Chromecast. Right after buying it, I set it up and I'm pretty much sure it got the official updates... so I ran to Best Buy to exchange it for a new one.
From thread comments, I know I have a shot at it having a vulnerable bootloader, now my problem is that OTG cables don't seem to exist where I live and I might have to go to Best Buy again to get one (long trip for a cable). Before I do that, I want to be certain that it'll work, but I cannot find where to see the build number. I somehow cannot get to the screen from the pictures.
I'm trying to set it up with a router that has no internet. Since this was a recommended method to check the build number, I thought it was possible, but so far I'm stuck with a message saying that ChromecastXXX connected to yournetwork, but cant access the internet..
At first I thought they had removed that from the Chromecast app, but I have installed the two older apks with the same results.
Could anyone tell me which step I'm missing?
I thought maybe I had this issue, but it's old and I was able to set up the previous Chromecast flawlessly.

keep on trying to make it connect even though there is no internet eventually it will give up and give you the number, thats who i got mine, it will say Chromecast XXX connected to network but cant access internet, and fail but then if you keep going it will eventually show you the build number.

BurnOmatic said:
keep on trying to make it connect even though there is no internet eventually it will give up and give you the number, thats who i got mine, it will say Chromecast XXX connected to network but cant access internet, and fail but then if you keep going it will eventually show you the build number.
Click to expand...
Click to collapse
ugh I did but it just times out and comes back to the same message. Perhaps it is a sign of a new firmware.

it will work dude eventually it will say that it went through even though clearly you havent got internet, and it will show the version number on the app , i did it through my pc not through the phone.

BurnOmatic said:
it will work dude eventually it will say that it went through even though clearly you havent got internet, and it will show the version number on the app , i did it through my pc not through the phone.
Click to expand...
Click to collapse
Thanks!. Got it working now. Somehow it never worked at home but I tried it at work where internet is filtered through mac addresses and that did the trick. Unfortunately it has an updated bootloader.

Not sure how much this will help, but I just went to Best Buy to return the 2nd Chromecast I had bought, since it came with a firmware newer than 12072. When I had purchased my first one, I hadn't done any research on rooting a Chromecast yet, and unfortunately allowed it to receive Google's OTA update. Before returning it, I took a picture of the serial number, pictured below. Tonight I decided to just get a refund at first, but then decided to take one third and final stab at getting one with a vulnerable bootloader. Thankfully, I kept the picture of the first one's serial number, and used it to compare against all of the Chromecasts that Best Buy had in stock. I only found one that began with "390...", since my originally purchased one began with "3901...". I live about an hour away from the closest Best Buy, so I decided to ask someone in Geek Squad if I could test it out to make sure it had the old firmware on it. He checked with someone else and was given the go ahead. We didn't plug it into the HDMI port, but he allowed me to plug it in to the USB port on a TV. Using the powered OTG micro USB cable I got in the mail today and a FlashCast drive I had created, I held the Chromecast button down and plugged the micro USB cable into the Chromecast. I waited to see if it the red light would go away after about 9 seconds, and VOILA, it did. I'll soon officially test it out on my TV so that I can see if the FlashCast logo comes up on the screen, and I will report back.
EDIT: Sorry for the delay in reporting back. Looks like the 3rd time was a charm, and the Chromecast I purchased last finally worked. So it looks like it's safe to at least assume that Chromecasts with serial numbers that begin with at least "390", with a range between "3901..." and "3907..." may have vulnerable bootloaders. Not to say this is the end all be all if figuring this out, but the guesswork might be if some use for now, until all the old stock gets sold completely.
Sent from my HTC One using Tapatalk

Damn. I bought my chrome cast the other day and allowed it to update without knowing any of these forums existed
sent from a LG-MS870 using Katana v3 ROM by GT

I picked up 2 chromecast's over the weekend from Best Buy (Mall of America). The first one had a 3Axxxxxxxx SN and was at 12940. The second one was a 39xxxxxx and was at 12072.
Versions with 12072 are still out there. Look for CC's with SN starting with 39 or 37.

guy4jesuschrist said:
Not sure how much this will help, but I just went to Best Buy to return the 2nd Chromecast I had bought, since it came with a firmware newer than 12072. When I had purchased my first one, I hadn't done any research on rooting a Chromecast yet, and unfortunately allowed it to receive Google's OTA update. Before returning it, I took a picture of the serial number, pictured below. Tonight I decided to just get a refund at first, but then decided to take one third and final stab at getting one with a vulnerable bootloader. Thankfully, I kept the picture of the first one's serial number, and used it to compare against all of the Chromecasts that Best Buy had in stock. I only found one that began with "390...", since my originally purchased one began with "3901...". I live about an hour away from the closest Best Buy, so I decided to ask someone in Geek Squad if I could test it out to make sure it had the old firmware on it. He checked with someone else and was given the go ahead. We didn't plug it into the HDMI port, but he allowed me to plug it in to the USB port on a TV. Using the powered OTG micro USB cable I got in the mail today and a FlashCast drive I had created, I held the Chromecast button down and plugged the micro USB cable into the Chromecast. I waited to see if it the red light would go away after about 9 seconds, and VOILA, it did. I'll soon officially test it out on my TV so that I can see if the FlashCast logo comes up on the screen, and I will report back.
Click to expand...
Click to collapse
Sorry for the delay in reporting back. Looks like the 3rd time was a charm, and the Chromecast I purchased last finally worked. So it looks like it's safe to at least assume that Chromecasts with serial numbers that begin with at least "390", with a range between "3901..." and "3907..." may have vulnerable bootloaders. Not to say this is the end all be all if figuring this out, but the guesswork might be if some use for now, until all the old stock gets sold completely.
Sent from my HTC One using Tapatalk

I can verify that 3904 "should" have the original firmware. Spent an hour looking for one, and another 45 minutes making sure that the Wifi, and my phone had no internet connection to them, and then trying to get it to connect fully, so I could see the firmware version. As soon as I switched from using the Chromecast app on my OG RAZR, to using it on my Nexus 7(2), it connected right away .It was the only one they had in the Best Buy near me, that was even close as far as serial numbers go. Time to get my brick..uhh. I mean, unlock on

I can verify that 3As all have newer firmware, thus can't be rooted. I tried two from my local Best Buy

Greetings:
I'm trying to connect without updating since I just got my CC but to no avail since yesterday!!
I'm doing the "no internet router" option but don't even see the "home screen" when I connect
the CC to my TV set!! All I see is few colored "dots"!!
Am I doing something wrong? or do I have a faulty CC?
Any input is much appreciated.
P.S= My phone is a Nexus 4
My CC's SN starts with 3805xxxxxxxxxxx

samteeee said:
Greetings:
I'm trying to connect without updating since I just got my CC but to no avail since yesterday!!
I'm doing the "no internet router" option but don't even see the "home screen" when I connect
the CC to my TV set!! All I see is few colored "dots"!!
Am I doing something wrong? or do I have a faulty CC?
Any input is much appreciated.
P.S= My phone is a Nexus 4
My CC's SN starts with 3805xxxxxxxxxxx
Click to expand...
Click to collapse
Little dots means you are in recovery mode.
Trying installing FlashCast and Custom ROM.
If you know the version is OK before you even connect it to a router and set it up you can setup the root!

mastermind278 said:
Little dots means you are in recovery mode.
Trying installing FlashCast and Custom ROM.
If you know the version is OK before you even connect it to a router and set it up you can setup the root!
Click to expand...
Click to collapse
I certainly didn't do anything to be on "Recovery" partition"!!
I'm not sure what my build/firmware is but I guess I can always
just try to go for "root" and see if it'll happen, right? I mean there
is no harm in that!! I'll get my OTG by Monday so I can try it.

[Q] Unable to recognize phone when hooked up to computers

Hey folks,
So I have a completely unmodified, stock Canadian N920W8 on 6.0.1, and no matter what I do, I cant get it to be recognized by Odin on my Win10 or Heimdall on my Mac.
I've done everything I could think of. Different cables, different ports, even different computers. Reinstalled the USB drivers, everything.
Anyone have any ideas? My phone won't fast charge, and is lagging more and more. I can't even Odin back to stock because it won't recognize. Factory Reset just cleaned out everything but nothing has changed. OEM unlock and USB debugging on, it won't be seen by the computers.
Any help? It's past manufacturer warranty, but it's still a good phone and I don't wanna lose it.

ve6ay said:
Hey folks,
So I have a completely unmodified, stock Canadian N920W8 on 6.0.1, and no matter what I do, I cant get
Any help? It's past manufacturer warranty, but it's still a good phone and I don't wanna lose it.
Click to expand...
Click to collapse
Did you install the actual drivers or just the ones that Windows installs? I use the ones that Samsung smart switch installs and I have no issues. If it is not fast charging and your computer does not recognize the phone it may not matter what drivers you use.

I used the Samsung USB drivers for Mobile Phones from Canadian support page. And that's on a fairly fresh win 10 install, too.

ve6ay said:
I used the Samsung USB drivers for Mobile Phones from Canadian support page. And that's on a fairly fresh win 10 install, too.
Click to expand...
Click to collapse
If you can I would suggest installing smart switch and see if smart switch sees your phone.

CodeNameRedNeck said:
If you can I would suggest installing smart switch and see if smart switch sees your phone.
Click to expand...
Click to collapse
I tried it on the Mac, smart switch didn't see the phone booted up. Didn't get a chance to try it in Odin mode. I'll try that tonight. And also on the PC. Any other suggestions?

ve6ay said:
I tried it on the Mac, smart switch didn't see the phone booted up. Didn't get a chance to try it in Odin mode. I'll try that tonight. And also on the PC. Any other suggestions?
Click to expand...
Click to collapse
Unfortunately not. I was hoping smart switch would see it. I would not rule out a damaged USB port.

I hope not... this is way past warranty, and I wanted to flash the thing with Khongloi's new Nougat rom... if it won't be recognized, then I can't even back it up or re-flash it to stock. Which is not a good thing...
No other suggestions, @CodeNameRedNeck ? You've been a huge help otherwise.

ve6ay said:
I hope not... this is way past warranty, and I wanted to flash the thing with Khongloi's new Nougat rom... if it won't be recognized, then I can't even back it up or re-flash it to stock. Which is not a good thing...
No other suggestions, @CodeNameRedNeck ? You've been a huge help otherwise.
Click to expand...
Click to collapse
Just to be sure. Can you transfer files from your PC to your phone and vice versa? Do you have any USB 3.0 ports? My phone seems to work better on 3.0 but still works on other types. Do you still have the Samsung cable? I know you said you have tried other cables but I used to have two cables that would not do data.

I tried with a brand new from the box cable, into four different usb 2 ports on the Mac and 2 usb 3 ports on the windows 10 PC.
No luck with it even being recognized for file transfers either.

@ve6ay, I could be wrong but I would say you probably need a new port. You should be able to pick one up relatively cheap. Good luck.

That's my thought, too, and in that case, I'll forgo anything. The contract is up in October, and it got the OTA update to 7.0, so I'm okay with it for now. I'm not into opening up her phone (which hasn't even been rooted yet) to switch out a port that I'm not confident enough to switch out.

ve6ay said:
That's my thought, too, and in that case, I'll forgo anything. The contract is up in October, and it got the OTA update to 7.0, so I'm okay with it for now. I'm not into opening up her phone (which hasn't even been rooted yet) to switch out a port that I'm not confident enough to switch out.
Click to expand...
Click to collapse
Did you try going into Developer Options and then scrolling down until you see "USB Configuration" and setting it to MTP? Or open the dialing pad and enter *#0808# and then making sure it's set to MTP, ADB and then try again.. If that doesn't work then it really is your port connection and it's actually super easy to replace and cheap too! All you'd have to do is heat the back up so you can loosen the glue up and then slowly pry the back off and then remove like 16 screws(lol) and then at the bottom you just unscrew it and easily pull the thin connection out.. I've done it several times so far although trying not to break the back glass is super hard..

The back glass got shattered in a drop last summer. So that will probably be a problem. Like I said, new phone this fall, most likely the next Note series. Though I'm tempted to go with an Exynos variant from across the ocean.

Any Value in a Dedicated Android Auto Device?

I have a spare phone that I was hoping to use as a dedicated Android Auto device but as I thought it through, I didn't feel there was really much to gain:
The phone doesn't have a SIM so I would have to enable the hotspot on my daily driver.
Since I'd want my daily driver to stay stopped up, I'd plug it in too.
Well if I'm doing all that anyway, I might was well just use the daily driver, right?
Is anyone else doing something similar with a spare phone?

Ironically, I went thru the same thing years ago with an older phone which was sitting around, no longer used because it was replaced with something newer and faster.
I have my workshop in the garage, and I found it useful to have the older phone unlocked and flashed with cyanogenmod to get the junk out of the system. Then I loaded up a 32GB microSD card full of music and audiobooks, so I can listen when I work on something on the radio in the garage. So it served as a mini-iPod like device, albeit a somewhat slow one. It worked out well, and then I later sold the phone on ebay.
Similar old, used phones I gave to young relatives - with extra bulky battery packs - so they could use them as small game machines. That worked okay.
There's some thoughts for you.