FORUMS

OnePlus Addresses Reservation List Cheating

Jake Cooper figured out how to bump his place up on OnePlus’ reservation list and … more

OnePlus 2 Benchmark Scores Show Its Muscle

This video by FoneArena contains all the popular benchmarks being tested on the OnePlus 2, … more

Sony’s Emergence in The Middle: Is The Price Right?

Sony’s Electronics Division is not in its best days, and its smartphone … more

HTC Delivering Ads Straight to Sense Home

HTC’s 2015 has been a year marked by a desperate search for revenue.The HTC One M9 … more

No longer detected as a Truesmart

118 posts
Thanks Meter: 25
 
By fg, Senior Member on 22nd February 2014, 01:02 AM
Post Reply Subscribe to Thread Email Thread
The newly released Companion App and Kurt's Watchfaces no longer detect my NA1900 1/8 as an Omate. Companion says "This app must be run on the Omate Truesmart" and Watchfaces wants me to buy it to unlock the premium options.

I have a feeling something's changed in the build.prop, but I don't know what an original build.prop looks like.

Before I go about restoring back to factory defaults, does anyone have a stock build.prop or some other ideas I might try?
 
 
22nd February 2014, 01:56 AM |#2  
Lokifish Marz's Avatar
Recognized Contributor / Recognized Developer
Flag Olympus Mons, Mars
Thanks Meter: 3,315
 
Donate to Me
More
New patch coming out this weekend to address that.
22nd February 2014, 03:23 AM |#3  
OP Senior Member
Thanks Meter: 25
 
More
Didn't even consider this as a side-effect of the root patch. Is this related to the framework-res modification included for the backlight settings or something in the build.prop?
23rd February 2014, 02:01 AM |#4  
OP Senior Member
Thanks Meter: 25
 
More
Quote:
Originally Posted by Lokifish Marz

New patch coming out this weekend to address that.

Applied your patch, no change. Do you have an original build.prop or should I do a factory restore?
23rd February 2014, 02:28 AM |#5  
Lokifish Marz's Avatar
Recognized Contributor / Recognized Developer
Flag Olympus Mons, Mars
Thanks Meter: 3,315
 
Donate to Me
More
Quote:
Originally Posted by fg

Applied your patch, no change. Do you have an original build.prop or should I do a factory restore?

Which option did you use?
23rd February 2014, 03:10 AM |#6  
OP Senior Member
Thanks Meter: 25
 
More
option 1 first, then option 2
23rd February 2014, 03:22 AM |#7  
Lokifish Marz's Avatar
Recognized Contributor / Recognized Developer
Flag Olympus Mons, Mars
Thanks Meter: 3,315
 
Donate to Me
More
Quote:
Originally Posted by fg

option 1 first, then option 2

Walk me though exactly what you did and what the error is and when it happens. I can't get it to fail on either the EU 512/4 or the NA 1/8.

Just a heads up though, you are supposed to choose only one option as Operative install is Operative and the patch combined.
The Following User Says Thank You to Lokifish Marz For This Useful Post: [ View ]
23rd February 2014, 03:23 AM |#8  
OP Senior Member
Thanks Meter: 25
 
More
Quote:
Originally Posted by fg

option 1 first, then option 2


tried again a few times and now option 2 seems to have resolved this
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes