Database Users

DJ Steve Build.prop and Market (Google) Apps

Hi Steve (and everyone),
I had a question about the fingerprint of the Streakdroid Froyo we all know and love.
Is the phone essentially advertising itself as a Nexus One for the purposes of the market?
Here's my issue:
Lately, I am getting watered down versions of the new Google first party app offerings.
First it was the new "personalized search" in the new version of voice search. I simply don't get that option.
I know that's not a huge deal for everyone since many on this forum are not in the States, and that feature only supports US English for the moment anyway.
But now, on the new version of maps, the two-finger twist to rotate does not work, and nor does the whole 3D landmarks feature.
On the official blog post announcing the new version of maps, there are a number of Nexus One users reporting the same behavior.
Anyway, I'm just wondering:
Is this something that is determined by the fingerprint in the build.prop?
If so, anyone know which line(s) make up everything the market looks at?
If we are using Nexus One settings, is it possible that we're starting to be left behind by them as Google pulls back what they support on the Nexus One?
Lastly, and most importantly, do you think we can change it? Maybe we can grab the relevant lines from a build.prop from the Galaxy S?
Just an idea there. I'm willing to do the experimenting if I can get a little information to get it rolling.
Thoughts?
Thanks!

3D buildings work on Steve's 1.4.6. Try zooming in New York. Two-finger rotation does not work.

Not working for me on 1.5.1.
I dunno. I think this is something we need to address. I am gonna research more but if anyone has any thoughts please let me know.
Sent from my Dell Streak using XDA App

Works here on 1.5.1 but its slow and only works at a certain zoom level
Sent from my Dell Streak using XDA App

If you open up the build.prop you can tell that there is no reference to any other device, just the streak...
Code:
ro.product.model=Dell Streak
ro.product.brand=dell
ro.product.name=streak
ro.product.device=streak
ro.product.manufacturer=Dell Inc.
*do not change "dell" to "Dell" (capital d) it will kill the stock swype, saying something along the lines that its not authorized for your device.
I have noticed that some apps by google were not showing up in earlier (1.1 i think) builds but they are now in 1.5.1
I have no issues with the 3D feature on google maps. See google's post here and make sure your trying to do something that is supported...
Also for US users, you might want to edit the following in the build.prop
Code:
ro.product.locale.region=GB
to
Code:
ro.product.locale.region=US
Before i did this, if i wanted to share a location with Google Maps it would send the link as google.co.uk instead of google.com
It still pointed to the same thing but people would call me asking if i'm sure i sent the proper link...
---UPDATE---
Was just testing some changes in the build.prop and i noticed this
Code:
ro.build.product=passion
and passion is HTC's code name for the Nexus One
but right before it, it says
Code:
# ro.build.product is obsolete; use ro.product.device

Yeah but there is more reference to Passion. Look at the "fingerprint" entry. I think that is relevant too.
I dunno, I am pretty confident something is up with this. What about personalized voice search? You getting that ok too?
For me, the only new feature that work in the new maps is pulling down to the different perspective and I do have the option to cache GPS.
Pretty sure I am not just expecting something that is not there as my wife has a Samsung Captivate and I have compared the two. Twist to rotate works on her phone.
I also read the whole blog entry. Pretty confident I know what the new features are supposed to be.
Hmmmm
Sent from my Dell Streak using XDA App

Have you tried using entries from official build.prop?

GeorgijSapkin said:
Have you tried using entries from official build.prop?
Click to expand...
Click to collapse
From the UK-O2 build 6941
Code:
# ro.build.product is obsolete; use ro.product.device
ro.build.product=qsd8250_surf
Same thing for build 8105
Don't have the stock build.prop for the US 1.6 build 6601

Netflix .apk

I'm strongly considering this tablet, but I want to make sure it gets Netflix support. I was able to get Netflix on my Captivate (running custom GB ROM) by sideloading the .apj. Has anyone tried this on the A500? What were the results?

sarcasmo said:
I'm strongly considering this tablet, but I want to make sure it gets Netflix support. I was able to get Netflix on my Captivate (running custom GB ROM) by sideloading the .apj. Has anyone tried this on the A500? What were the results?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1066516&highlight=netflix
its been discussed in this thread, netflix is not supported at the moment

kkaytan said:
http://forum.xda-developers.com/showthread.php?t=1066516&highlight=netflix
its been discussed in this thread, netflix is not supported at the moment
Click to expand...
Click to collapse
Netflix is not 'supported' on my device (Captivate), but it works for me and all others that are running a Gingerbread ROM based off the i9000 source. All you have to do is sideload the .apk and sign-in.
I know others have also gotten things to work (even on a Nook Color) by spoofing the device by edititing build.prop as follows:
ro.product.model=HTC Vision
ro.product.brand=tmobile
ro.product.name=vision
ro.product.device=vision
ro.product.board=vision
ro.product.manufacturer=HTC
ro.build.fingerprint=tmobile/htc_vision/vision/vision:2.2/FRF91/277427:user/release-keys
I'm curious if anyone here has gotten creative and found a way to make things work.

sarcasmo said:
Netflix is not 'supported' on my device (Captivate), but it works for me and all others that are running a Gingerbread ROM based off the i9000 source. All you have to do is sideload the .apk and sign-in.
I know others have also gotten things to work (even on a Nook Color) by spoofing the device by edititing build.prop as follows:
ro.product.model=HTC Vision
ro.product.brand=tmobile
ro.product.name=vision
ro.product.device=vision
ro.product.board=vision
ro.product.manufacturer=HTC
ro.build.fingerprint=tmobile/htc_vision/vision/vision:2.2/FRF91/277427:user/release-keys
I'm curious if anyone here has gotten creative and found a way to make things work.
Click to expand...
Click to collapse
Well then I guess your best bet is to buy an A500 and do what you just suggested yourself.

That method does not work 100% yet from what I have been reading. Even across various roms on a supported device.
Sent from my A500 using Tapatalk

*sigh*
http://forum.xda-developers.com/showthread.php?t=1077421
Search...

jimbobtexas said:
*sigh*
http://forum.xda-developers.com/showthread.php?t=1077421
Search...
Click to expand...
Click to collapse
That thread has zero valuable information. Please read this thread (a whole 4 posts prior to your comment) before sighing and pointing me to a post that fails to respond to the clarified question I asked in the third post of this thread. I was hoping someone might have tried to push past 'not a supported device' and try some tricks.

sarcasmo said:
That thread has zero valuable information. Please read this thread (a whole 4 posts prior to your comment) before sighing and pointing me to a post that fails to respond to the clarified question I asked in the third post of this thread. I was hoping someone might have tried to push past 'not a supported device' and try some tricks.
Click to expand...
Click to collapse
I sacrificed a goat and some rotten eggs, but Bwon Samdi wasn't smiling on me and it didn't work :-D

edgie168 said:
Well then I guess your best bet is to buy an A500 and do what you just suggested yourself.
Click to expand...
Click to collapse
Totally valid suggestion. If I pick one up this weekend I'll give it a try. Obviously, HC is a different animal from GB, but you never know (and Tegra 2 differs from Hummingbird). I'll report back if I learn anything interesting.

Considering Nvidia is more focused on further fragmentation with "Tegra Zone" and working with Google for $5 movie rentals, I would not hold my breath for an official Netflix app. Seems the lack of one is by design.
Yes, the iPad is evil, but at least you have the option of iTune downloads AND Netflix. Not just the Google rentals, that seems a blatant effort to force folks to pay $5 a pop, rather than consumers use their Netflix account that THEY ALREADY PAY FOR.

New firmware update KH3 in Kies

Hi
My UK Galaxy Tab 10.1 Wifi P7510 is receiving an update today, not sure if anyone has checked for updates yet?
I used the Settings/About/Software Updates on the Tab and it said there was no updates available but when I connected through Kies it said there was an update and it is firmware KH3
Currently downloading...
EDIT: Still v3.1...

markdj57 said:
Hi
My UK Galaxy Tab 10.1 Wifi P7510 is receiving an update today, not sure if anyone has checked for updates yet?
I used the Settings/About/Software Updates on the Tab and it said there was no updates available but when I connected through Kies it said there was an update and it is firmware KH3
Currently downloading...
EDIT: Still v3.1...
Click to expand...
Click to collapse
Anything else noted yet?

Whats different in it?

I got it too. Before I go ahead, does it wipe everything?

Samsung's firmware coding is wierd. KH3 for the UK (XEU) might be newer than the recently released KI1 even though "I" would appear to be a later release then "H." For the SGS2, what appeared as a newer code released for specific regions actually contained older software. I bet KH3 is the new shipping ROM as the 32GB and 64GB 7500's just started being received by resellers at the end of last week.
This is old, but it explains Samsung's logic...
http://samsungi8510.com/forum/how-samsung-firmware-versioning-works-t235.html

Doesn't wipe anything as you do it through Kies though I may end up doing a factory reset if the FC issues continue!
gapps and something with una on the end are FC regularly, don't know the reason yet.
Text had a sharper edge to it with black haloes but after fiddling with fonts and the auto screen power it all came better aliased again so don't know the reason.
Browser has been updated, now seems smoother, better flash performance I think though flash was updated to 11 this week so hard to tell.
The browser bug has happened where the page flicks about with blank areas but clearing the cache sorted that and it didn't in the previous firmware so maybe that is just old cache ??
Live wallpaper is better for screen scrolling though still noticeable.
------------UPDATE---------
It's an update, so I will see how it goes, very very early to tell yet, things are starting to settle down...
OK, the screen is MUCH more responsive. I just tested antipaper notes and writing is very fast and accurate. A big improvement on previous firmware. I have the Autodesk drawing app too, Sketchbook Pro - working much better.

Can someone pull the build.prop? There is a "KH5" already in the dev section (build date: Aug 18) and I'm wondering how "fresh" KH3 is.

I have kh5 and use to have kme
I can say this release is much more responsive no lag at all
Its more fluid than tasks roms
I flashed via odin
So yes just dump the build props
And is recovery 3e??
Sent from my GT-P7510 using Tapatalk

Nothing for me?

I had to accept the Kies update and then the firmware for the Tab, all installed fine. I tried a few Quadrant benchmark tests and also with Linpack. To be fair, I haven't a clue what my Tab would have scored before the update, so the results are likely a waste of time. The results don't look anything special though.
Quadrant
Run 1 - 2137
2 - 2349
3 - 2420
4 - 2451
Linpack
MFLOPS: 56.391
Time 2.99 seconds
Norm Res: 3.20

gokpog said:
Can someone pull the build.prop? There is a "KH5" already in the dev section (build date: Aug 18) and I'm wondering how "fresh" KH3 is.
Click to expand...
Click to collapse
It's newer than yours, but not that fresh:
ro.build.date=Fri Aug 26 16:28:07 KST 2011
After I updated, I got force close on the Samsung UNA app. The solution was to go to apps management and clear out cache and data from com.samsung.apps.una and Samsung Apps, no more FC now.
An other side-effect is that I can't connect to Kies now. It stays at 'connected', but never actually connects... haven't found a solution yet.
Otherwise it seems ok, but not a jaw-dropping improvement from KG8..

Tyxerakias said:
It's newer than yours, but not that fresh:
ro.build.date=Fri Aug 26 16:28:07 KST 2011
After I updated, I got force close on the Samsung UNA app. The solution was to go to apps management and clear out cache and data from com.samsung.apps.una and Samsung Apps, no more FC now.
An other side-effect is that I can't connect to Kies now. It stays at 'connected', but never actually connects... haven't found a solution yet.
Otherwise it seems ok, but not a jaw-dropping improvement from KG8..
Click to expand...
Click to collapse
cant wait till this becomes a flashable odin rom
though KH5 is day and night in performance compare to KME

No update for me so if someone could upload the files, it would be great.

Stupid kies not finding my tab!
* shakes fist at Kies *

Same here, but oddly it connects to Kies just fine wirelessly. Samsung might make good hardware, but that Kies is crap.

It tells me "This version of the device cannot be updated" whatever that means. Should I return my tab?

nandihno said:
cant wait till this becomes a flashable odin rom
though KH5 is day and night in performance compare to KME
Click to expand...
Click to collapse
Kh5 and kme are day and night. LMAO!!!

ro.build.date=Fri Aug 26 16:28:07 KST 2011
Click to expand...
Click to collapse
Sounds good. Waiting for a cwm flashable update, that won't touch my bootloaders.

just upgraded to kh3 ( stock, not rooted ) myself...
no more crashes in market when scrolling the search results in the book section
touch screen feels more responsive and accurate ( mainly noticed it with keyboard usage )
alot less or no lag
apps seem to load faster.
the auto brightness seems to react abit faster ( going darker or lighter... faster )
more free memory... before it was between 80 - 127... I have 200~ now
this ain't no placebo effect... I've used this tab between 4 - 8 hours a day since the day I bought it
only thing I'm wondering now is have they fixed the "android.process.media" high cpu usage problem...

pngface said:
It tells me "This version of the device cannot be updated" whatever that means. Should I return my tab?
Click to expand...
Click to collapse
This happened to me with old version of kies. Remove kies. Resrart the tab then install the newest version for kies. Restart. Your computer and it should work

New August Images.

So today Google released new images for this month. Still with the MMB and MOB builds.

http://www.droid-life.com/2016/08/0...icks-off-today-factory-image-files-ota-files/
Sent from my Nexus 6 using Tapatalk

Encryptable boot image for MOB30W:
https://www.androidfilehost.com/?fid=24651430732235243

I never had this problem before, but I have downloaded the images and OTA zip files twice and both files fail the MD5 check. Is anyone else seeing this?
If not, maybe I need to update my MD5 checker. Any ideas or suggestions?
EDIT: Never mind, apparently they have switched to a SHA-256 Checksum, so a new checker verified that they are okay.

I see two versions:
MOB30R
MOB30W
I am going to install W, but I am curious what is R (carrier specific)?

RLBL said:
I see two versions:
MOB30R
MOB30W
I am going to install W, but I am curious what is R (carrier specific)?
Click to expand...
Click to collapse
It's MMB30R and from what I remember, the MMB versions are for specific carriers, Fi maybe?!?

JimSmith94 said:
It's MMB30R and from what I remember, the MMB versions are for specific carriers, Fi maybe?!?
Click to expand...
Click to collapse
This post explains the difference well: http://forum.xda-developers.com/showpost.php?p=67648012&postcount=13

JimSmith94 said:
It's MMB30R and from what I remember, the MMB versions are for specific carriers, Fi maybe?!?
Click to expand...
Click to collapse
From what I've read on previous posts about the 2 images, is that MMB has the old radio where as MOB has the new radio! Reason being that not all carriers have approved the new radio yet, so Google made 2 images. Since we are just flashing them and don't give a flying.....(can I say that here?) About carrier approval, just flash the MOB builds, they're newer!

JimSmith94 said:
I never had this problem before, but I have downloaded the images and OTA zip files twice and both files fail the MD5 check. Is anyone else seeing this?
If not, maybe I need to update my MD5 checker. Any ideas or suggestions?
EDIT: Never mind, apparently they have switched to a SHA-256 Checksum, so a new checker verified that they are okay.
Click to expand...
Click to collapse
They changed the type of hash? Thanks for telling me! Good info here, I would freak too! Lol
ALSO! Might as well say it here rather than making a third post in a row. How many of you guys think Android N is coming this month? I'm hopeful to see it! I'm running dev preview 5 and loving it!

H4X0R46 said:
They changed the type of hash? Thanks for telling me! Good info here, I would freak too! Lol
ALSO! Might as well say it here rather than making a third post in a row. How many of you guys think Android N is coming this month? I'm hopeful to see it! I'm running dev preview 5 and loving it!
Click to expand...
Click to collapse
I'm loving it as well but I hope they'll improve battery life because this is the only thing that keeps me away from DP5. Gonna flash August update and then see how N goes.
Envoyé de mon Nexus 6 en utilisant Tapatalk

TsarFlow said:
I'm loving it as well but I hope they'll improve battery life because this is the only thing that keeps me away from DP5. Gonna flash August update and then see how N goes.
Envoyé de mon Nexus 6 en utilisant Tapatalk
Click to expand...
Click to collapse
Oh yea! Preview 4 had absolutely SUPERB battery life, preview 5 was a bit dodgy for sure. I'm staying with preview 5 because my phone no longer hangs with my wifi network. I started hanging before loading things for a solid like, 10 seconds or more and it was drive me insane! That started with 6.0 marshmallow, that issue is gone for me in N, so that's the only thing keeping me on the new preview. I agree, battery life isn't great with it.

I think the official android Nougat arrives in four days...August 5.

electricpete1 said:
I think the official android Nougat arrives in four days...August 5.
Click to expand...
Click to collapse
Unlikely to release anything on a Friday. The 5th August date is likely just confusion around the Android Security Patch Level '2016-08-05' which all supported Nexus devices got today (or will shortly).
https://source.android.com/security/bulletin/2016-08-01.html

H4X0R46 said:
Oh yea! Preview 4 had absolutely SUPERB battery life, preview 5 was a bit dodgy for sure. I'm staying with preview 5 because my phone no longer hangs with my wifi network. I started hanging before loading things for a solid like, 10 seconds or more and it was drive me insane! That started with 6.0 marshmallow, that issue is gone for me in N, so that's the only thing keeping me on the new preview. I agree, battery life isn't great with it.
Click to expand...
Click to collapse
Well, I flashed MOB30W and the same hangs with all wifi activity. Back to N preview for me.

H4X0R46 said:
Well, I flashed MOB30W and the same hangs with all wifi activity. Back to N preview for me.
Click to expand...
Click to collapse
I'm experiencing the same wifi issues and was wondering if this update with the new radio would make a difference. Apparently not
Looks like I too will be moving on to N preview if that's solved the MM wifi issues. Thanks

ulnevrwalkalone said:
I'm experiencing the same wifi issues and was wondering if this update with the new radio would make a difference. Apparently not
Looks like I too will be moving on to N preview if that's solved the MM wifi issues. Thanks
Click to expand...
Click to collapse
It seems much more responsive with N preview. The wifi issues are infuriating to say the least. I can't wait for the final build of 7.0 mostly for this reason! Hope the preview works better for you. Post here and let us know if it fixes your issue as well!

Can anyone who has installed the new images please check and report whether the security date is showing as 8/1 or 8/5?

electricpete1 said:
Can anyone who has installed the new images please check and report whether the security date is showing as 8/1 or 8/5?
Click to expand...
Click to collapse
2016-08-05
Here's a snippet from the build.prop for MOB30W:
ro.build.id=MOB30W
ro.build.display.id=MOB30W
ro.build.version.incremental=3031100
ro.build.version.sdk=23
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=6.0.1
ro.build.version.security_patch=2016-08-05
ro.build.version.base_os=
ro.build.date=Fri Jul 1 21:17:15 UTC 2016
ro.build.date.utc=1467407835
ro.build.type=user
ro.build.user=android-build
ro.build.host=wpix12.hot.corp.google.com
ro.build.tags=release-keys
ro.build.flavor=shamu-user
ro.product.model=Nexus 6
ro.product.brand=google
ro.product.name=shamu
ro.product.device=shamu
ro.product.board=shamu
Click to expand...
Click to collapse
And MMB30R (for US AT&T users, and maybe some others)
ro.build.id=MMB30R
ro.build.display.id=MMB30R
ro.build.version.incremental=3031534
ro.build.version.sdk=23
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=6.0.1
ro.build.version.security_patch=2016-08-05
ro.build.version.base_os=
ro.build.date=Fri Jul 1 22:52:28 UTC 2016
ro.build.date.utc=1467413548
ro.build.type=user
ro.build.user=android-build
ro.build.host=vpak29.mtv.corp.google.com
ro.build.tags=release-keys
ro.build.flavor=shamu-user
ro.product.model=Nexus 6
ro.product.brand=google
ro.product.name=shamu
ro.product.device=shamu
ro.product.board=shamu
Click to expand...
Click to collapse

as others have noted, the time travel feature in this release was a nice surprise. <g>

H4X0R46 said:
It seems much more responsive with N preview. The wifi issues are infuriating to say the least. I can't wait for the final build of 7.0 mostly for this reason! Hope the preview works better for you. Post here and let us know if it fixes your issue as well!
Click to expand...
Click to collapse
Registered my device in the beta and installed the latest N preview via OTA update. From my initial use I can say the wifi is responding much better. Will test out further today when im jumping between work wifi/LTE/home wifi and see if its still smooth. But so far so good :good:

Build Number and Hardware? Updates?

My phone came with the following:
Build: NMI42B test-keys
Hardware: 1.8
So far my phone thinks it's rooted and I have not received the camera update.
Any other Build numbers/hardware the same?
Has anyone received the camera update with HDR or am I not receiving updates because of the test-keys build?

NMI54B was the update I got immediately.

imdebbas said:
My phone came with the following:
Build: NMI42B test-keys
Hardware: 1.8
So far my phone thinks it's rooted and I have not received the camera update.
Any other Build numbers/hardware the same?
Has anyone received the camera update with HDR or am I not receiving updates because of the test-keys build?
Click to expand...
Click to collapse
hardware 1.8
build NMl54b

Hardware 1.8
NMI54B was waiting when I put it on the network.
Sent from my PH-1 using XDA Labs

-Michael_ said:
Hardware 1.8
NMI54B was waiting when I put it on the network.
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
Same here. Same hardware and build.

I just got a note from support saying that build NMI64C is available, but my phone doesn't show an available update. Hoping it fixes my Bluetooth issues.

vadirtyr said:
I just got a note from support saying that build NMI64C is available, but my phone doesn't show an available update. Hoping it fixes my Bluetooth issues.
Click to expand...
Click to collapse
Did they provide a changelog?

I'm currently rocking NMI54B.

sabbotage said:
Did they provide a changelog?
Click to expand...
Click to collapse
No, I asked for one but given that it took several days for the initial response I doubt the response will be quick.

I was also told that that update was pushed over the weekend, no updates available on my phone...

imdebbas said:
My phone came with the following:
Build: NMI42B test-keys
Hardware: 1.8
So far my phone thinks it's rooted and I have not received the camera update.
Any other Build numbers/hardware the same?
Has anyone received the camera update with HDR or am I not receiving updates because of the test-keys build?
Click to expand...
Click to collapse
Mine is hardware 1.8.
Build is NMI54B

tech_head said:
Mine is hardware 1.8.
Build is NMI54B
Click to expand...
Click to collapse
I've got the same hardware and build as everyone else here and we're heading into the next weekend now. Is there anyone who has the newer build yet?

Not yet

vadirtyr said:
I just got a note from support saying that build NMI64C is available, but my phone doesn't show an available update. Hoping it fixes my Bluetooth issues.
Click to expand...
Click to collapse
I had some BT weirdness too, it does not seem to like BLE devices. Eventually mine started working with them
Garmin Fenix 5x
Bose Soundsports

Just an FYI to anyone following this thread NMI64C is rolling out now. I just checked and I'm downloading now... funny enough the device did a check at 12:35 EST today (or something like that) but it didn't kick over until now (2:10pm EST).

Ghost_1 said:
Just an FYI to anyone following this thread NMI64C is rolling out now. I just checked and I'm downloading now... funny enough the device did a check at 12:35 EST today (or something like that) but it didn't kick over until now (2:10pm EST).
Click to expand...
Click to collapse
If thats the case then hopefully I will be getting the update this afternoon. I live In Utah so I'm on mountain time. Hopefully the update fixes allot of key issues.

theandroidbot said:
If thats the case then hopefully I will be getting the update this afternoon. I live In Utah so I'm on mountain time. Hopefully the update fixes allot of key issues.
Click to expand...
Click to collapse
Just go in and check manually. That's what I did.

I have hardware version 1.8
Build Number NMI75B test-keys
I received two significant OTA updates since I received the phone (first one was about 900mb, the second one was considerably smaller).

quadcrap1 said:
I have hardware version 1.8
Build Number NMI75B test-keys
I received two significant OTA updates since I received the phone (first one was about 900mb, the second one was considerably smaller).
Click to expand...
Click to collapse
That's interesting... both you and the OP has test-keys listed next to your build number.
Mine just says NMI64C
Sent from my PH-1 using XDA-Developers Legacy app

Add me to the list of test keys. My hardware is 1.8 and my build is NMI75B test-keys. What the hell does that mean? I just received this device today from a guy on Swappa. Did he modify it somehow? Will I still be able to get OTA updates?