SYNET7LP Recognized as Model: p7901a

Discussion in 'Sylvania Tablets' started by JPardee, Apr 14, 2011.

  1. JPardee

    JPardee Member

    Joined:
    Mar 26, 2011
    Messages:
    49
    Likes Received:
    2
    Trophy Points:
    72
    Location:
    Ohio
    Tablet / Device:
    SYTABEX7
    I downloaded a few apps to try on the SYNET7LP.

    Went to run Pandora on the unit and got an unsopported model error.
    Pandora recognized the SYNET7LP as the p7901a.

    HERE is a description of teh P7901A

    I find it interesting, unless Pandoras database has a default for "unknown devices"

    Any thoughts?
     
  2. cfrockit

    cfrockit Senior Member

    Joined:
    Dec 26, 2010
    Messages:
    627
    Likes Received:
    190
    Trophy Points:
    132
    Tablet / Device:
    Sylvania SYNET7LP
    It's coded in the "build.prop". Many of the infoTM devices such as the ZT-180 are reported as well as p7901a therefore, using sites like getjar.com allow you to select a clone device and recognize it to allow downloads.

    Code:
    ro.build.product=p7901a
    # Do not try to parse ro.build.description or .fingerprint
    ro.build.description=p7901a-eng 2.1-update1 ERE27 eng.liuqi.20101026.123557 test-keys
    ro.build.fingerprint=generic/p7901a/p7901a/:2.1-update1/ERE27/eng.liuqi.20101026.123557:eng/test-keys
    
    
    Several sites discuss how modifying this property allow you to view more content from sites since they then think its a different device.

    Here's an example of how the sites database might recognize what type of device the user is using based on the contents of the "build.prop".

    AndroidFragmentation.com - The Open Android Device Knowledge Base

    unknown/dm/p7901a/carrier/Unknown

    p7901a is referenced in all of these entries -Model, Device model, Device Brand, Build number, Build fingerprint
     
    Last edited: Apr 14, 2011
  3. JPardee

    JPardee Member

    Joined:
    Mar 26, 2011
    Messages:
    49
    Likes Received:
    2
    Trophy Points:
    72
    Location:
    Ohio
    Tablet / Device:
    SYTABEX7
    Awesome information...
    Much appreciated.
     
  4. JPardee

    JPardee Member

    Joined:
    Mar 26, 2011
    Messages:
    49
    Likes Received:
    2
    Trophy Points:
    72
    Location:
    Ohio
    Tablet / Device:
    SYTABEX7
    Would anyone care to modify the "build.prop" file and email it to me?
    I'm not familiar with SDK tools, and I'm fairly new to Android OS.
     
  5. cfrockit

    cfrockit Senior Member

    Joined:
    Dec 26, 2010
    Messages:
    627
    Likes Received:
    190
    Trophy Points:
    132
    Tablet / Device:
    Sylvania SYNET7LP
    JPardee,

    Your request is risky. If someone modifies a build.prop and get's it wrong you'll have to do a complete factory reset to get the device working again. If changed incorrectly, without knowing enough it can cause the device it to stay stuck on the Sylvania screen.

    Research some of the ZT-180 sites and the Flytouch discussions to see what they are doing with it, since they're both infoTM based devices, such as making the device look like a Xoom to the database. They have had varying success.

    Useful Resources for the ZT-180 on the Internet : Zenithink ZT-180

    There's not fancy about "/system/build.prop". It's a flat ascii text file that with having root and using RootExplorer a long click on it brings up the menu, scroll down and "Open in Text Editor" and then you can change it on the device. When the file is closed a back up of the last version of the file is saved. Reboot and see if the changes work. If they don't and it fails apply a factory reset and try again.

    There are a few "finger prints" posted but use with caution.

    Good luck, but it's a risky proposition.
     
  6. JPardee

    JPardee Member

    Joined:
    Mar 26, 2011
    Messages:
    49
    Likes Received:
    2
    Trophy Points:
    72
    Location:
    Ohio
    Tablet / Device:
    SYTABEX7
    You would think more Sylvania tablet users would like this mod, to utilize more apps.

    I have noticed that a lot of Android Market apps won't work, because the device is "Unknown"
     
  7. haymond

    haymond Member

    Joined:
    Mar 26, 2011
    Messages:
    25
    Likes Received:
    0
    Trophy Points:
    60
    I couldn't get android market installed on my tablet,waiting on someone to send me link to a market that will work.slideme sucks
     
  8. JPardee

    JPardee Member

    Joined:
    Mar 26, 2011
    Messages:
    49
    Likes Received:
    2
    Trophy Points:
    72
    Location:
    Ohio
    Tablet / Device:
    SYTABEX7
    I'm going to play around with this and see what I can do.
    Here is my SYNET7LP build.prop file.

    # begin build properties
    # autogenerated by buildinfo.sh
    ro.build.id=FRF85B
    ro.build.display.id=FRF85B
    ro.build.version.incremental=eng.liuqi.20110301.15 0645
    ro.build.version.sdk=8
    ro.build.version.codename=REL
    ro.build.version.release=2.2
    ro.build.date=2011骞 03鏈 01鏃 鏄熸湡浜 15:08:33 CST
    ro.build.date.utc=1298963313
    ro.build.type=user
    ro.build.user=liuqi
    ro.build.host=liuqi-desktop
    ro.build.tags=test-keys
    ro.product.model=p7901a
    ro.product.brand=generic
    ro.product.name=p7901a
    ro.product.device=p7901a
    ro.product.board=
    ro.product.cpu.abi=armeabi
    ro.product.manufacturer=unknown
    ro.product.locale.language=en
    ro.product.locale.region=US
    ro.wifi.channels=
    ro.board.platform=imap210
    # ro.build.product is obsolete; use ro.product.device ro.build.product=p7901a # Do not try to parse ro.build.description or .fingerprint ro.build.description=p7901a-user 2.2 FRF85B eng.liuqi.20110301.150645 test-keys ro.build.fingerprint=generic/p7901a/p7901a/:2.2/FRF85B/eng.liuqi.20110301.150645:user/test-keys
    # end build properties

    #
    # ADDITIONAL_BUILD_PROPERTIES
    #
    ro.versioncode=10
    ro.debuggable=0
    persist.service.adb.enable=0
    persist.app2sd.enabled=0
    ro.suspend.unloadWifiDriver=true
    ro.config.notification_sound=OnTheHunt.ogg
    ro.config.alarm_alert=Alarm_Classic.ogg
    media.stagefright.enable-player=true
    media.stagefright.enable-meta=true
    media.stagefright.enable-scan=true
    media.stagefright.enable-http=true
    ro.setupwizard.mode=DISABLED
    net.bt.name=Android
    dalvik.vm.stack-trace-file=/data/anr/traces.txt
     
  9. novadar

    novadar Member

    Joined:
    Mar 26, 2011
    Messages:
    31
    Likes Received:
    1
    Trophy Points:
    72
    Location:
    Texas
    Tablet / Device:
    Sylvania SYTABEX7
    Very interesting Hanzi (Kanji) in that file. What appears to be the build date (ro.build.date=2011骞 03鏈 01鏃 鏄熸湡浜 15:08:33 CST) has very unusual Hanzi for Year, Month, Day. At least to me.

    Typically Year is 年. It is the same in Japanese (Nen). This one has 骞.

    When I translate the Kanji they use it returns "Rising High". One translator tool returned "Wild Ass". In broader searches, I found a few other uses of this for Year.

    Weird.

    Sorry this was a bit off topic.
     
  10. JPardee

    JPardee Member

    Joined:
    Mar 26, 2011
    Messages:
    49
    Likes Received:
    2
    Trophy Points:
    72
    Location:
    Ohio
    Tablet / Device:
    SYTABEX7
    It's ok, I don't thnk my thread is going anywhere.

    I would like to modify this to work on the Sylvania tabs.
    There are several apps that wont work, due to the properties in this file.

    360 Live, Facebook, Sirius / XM, Pandora, FaChat, NFL, and several others...
     
  11. cfrockit

    cfrockit Senior Member

    Joined:
    Dec 26, 2010
    Messages:
    627
    Likes Received:
    190
    Trophy Points:
    132
    Tablet / Device:
    Sylvania SYNET7LP
    Anyone notice that some of the devices have an updated build.prop which changes the name from the original p7901a to p7901ui?

    Old build.prop

    Code:
    ro.product.model=p7901a
    ro.product.brand=generic
    ro.product.name=p7901a
    ro.product.device=p7901a
    
    Code:
    ro.build.product=p7901a
    # Do not try to parse ro.build.description or .fingerprint
    ro.build.description=p7901a-user 2.2 FRF85B eng.liuqi.20110301.150645 test-keys
    ro.build.fingerprint=generic/p7901a/p7901a/:2.2/FRF85B/eng.liuqi.20110301.150645:user/test-keys
    New/updated device build.prop
    Code:
    ro.product.model=p7901ui
    ro.product.brand=generic
    ro.product.name=p7901ui
    ro.product.device=p7901ui
    Code:
    ro.build.product=p7901ui
    # Do not try to parse ro.build.description or .fingerprint
    ro.build.description=p7901ui-user 2.2 FRF85B eng.liuqi.20110221.141106 test-keys
    ro.build.fingerprint=generic/p7901ui/p7901ui/:2.2/FRF85B/eng.liuqi.20110221.141106:user/test-keys
    
    Simple observation would be "old" build.prop, obtained from the manual update, has a more recent date 20110301.150645 than the new one 20110221.141106 observed on devices users have returned for service/replacement.

    What are the 6 digits following the date? The time, the firmware version or something else?
     
    Last edited: May 18, 2011
  12. Xi2wiked

    Xi2wiked Member

    Joined:
    Apr 28, 2011
    Messages:
    112
    Likes Received:
    8
    Trophy Points:
    87
    Location:
    Washington
    Tablet / Device:
    Sylvania tablet
    I believe that's the internal # for the test key they used to sign
     
  13. kRR55Fg

    kRR55Fg Member

    Joined:
    Jan 24, 2014
    Messages:
    1
    Likes Received:
    0
    Trophy Points:
    35
    Help to find an insertion(firmware) on p7901ui.
     

Share This Page

Search tags for this page
android p7901ui
,

p7901ui

,
p7901ui firmware