Database Users

UK Banking Apps not Compatible?

Anyone from the UK Manage to Installed the Natwest, RBS or Bank Control UK Apps on the U8800?
They don't show up on my phones market and on market.android.com they come up as not compatible with U8800, is this happening for all U8800 users?
Downloaded More Locale 2 and it comes back with the following info:
- Language: en
- Country: GB
So thats not a problem.
I then downloaded Market Enabler and it has the following code:
- 23410 (o2 UK)
This is also correct.
I am not sure why these apps wouldn't be compatible with the U8800, anyone got any ideas?
Was also thinking of editing the build.prop to something like the Desire but not sure exactly what needs changing.
Have tried both MIUI and CM7 and get the same results

Just looking at the build.prop in CM7 and the Market Fingerprint seems to be for the HTC Passion:
Code:
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=passion-user 2.3.5 Geno 102588 release-keys
ro.build.fingerprint=google/passion/passion:2.3.5/Geno/102588:user/release-keys
Not sure what to change it too though?

Ok tried my girlfriends blade and it allows you to install the banking apps just fine so I have a loot at her build.prop file:
Code:
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=passion-user 2.3.7 GRj22 121341 release-keys
ro.build.fingerprint=google/passion/passion:2.3.7/GRj22/121341:user/release-keys
Tried this on the U8800 and still no dice

edit the build prop and change the device from U8800 to a Desire Z. I did this for Gameloft games, don't see any reason why it couldn't work for the bank apps too.
Code:
ro.product.model=HTC Desire Z
ro.product.brand=generic
ro.product.name=libra_vision
ro.product.device=vision
ro.product.board=vision
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
replace the U8800 bits with this sort of thing.
change ro.build.product as well

flibblesan said:
edit the build prop and change the device from U8800 to a Desire Z. I did this for Gameloft games, don't see any reason why it couldn't work for the bank apps too.
Code:
ro.product.model=HTC Desire Z
ro.product.brand=generic
ro.product.name=libra_vision
ro.product.device=vision
ro.product.board=vision
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
replace the U8800 bits with this sort of thing.
change ro.build.product as well
Click to expand...
Click to collapse
Didn't work unfortunately
Changed build.prop, Cleared Market Cache and Restarted phone but no difference.

Think I have found the problem, I have got an email back from Bank Control.
I'm guessing CM7 and MIUI use incompatible encryption libs
Gutted!
Hi Chris,
Thank you for trying the Bank Control application.
The Android Market must not tell you anything about incompatible application
because it has not upper version limit in the market metadata. The app runs
fine on 3.2 even and will run on 4.0. The only known problem is version
2.3.5, which is related to Market's bug rather than the app itself. 2.3.4
and 2.3.6. are both OK. It could be the same Android Market bug with 2.3.7.
It has been mentioned here: http://www.mobot.net/android-versions.
We'll get in touch with Google.
Also, it is important to get all updates from the operator rather than form
the manufacturer and the app does not run on unofficial mods due to
incompatible encryption libs.
Thanks for reporting and bets regards
Bank Control support
Click to expand...
Click to collapse
Hope this helps others too.

[ROM][STOCK][HONG KONG - TGY] ZSLPN: still 4.0.4 :(

Couldnt find this posted anywhere here yet:
Product Code: GT-N7000ZBATGY
Latest firmware: N7000ZSLPN/N7000OZSLPN/N7000XXLRB/N7000ZSLPN
Modified: 9/21/2012 9:59:07 PM
Available via Kies, Checkfus, and Sammobile.
Sammobile Hotfile link: http://www.hotfile.com/dl/175773168/96eef3e/N7000ZSLPN_N7000OZSLPN_TGY.zip.html
Busy Downloading
Build Prop:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=IMM76D
ro.build.display.id=IMM76D.ZSLPN
ro.build.version.incremental=ZSLPN
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Thu Sep 20 00:17:49 KST 2012
ro.build.date.utc=1348067869
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEP-67
ro.build.tags=release-keys
ro.product.model=GT-N7000
ro.product.brand=samsung
ro.product.name=GT-N7000
ro.product.device=GT-N7000
ro.product.board=smdk4210
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=exynos4
# ro.build.product is obsolete; use ro.product.device
ro.build.product=GT-N7000
ro.tether.denied=false
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=GT-N7000-user 4.0.4 IMM76D ZSLPN release-keys
ro.build.fingerprint=samsung/GT-N7000/GT-N7000:4.0.4/IMM76D/ZSLPN:user/release-keys
ro.build.characteristics=phone
# Samsung Specific Properties
ro.build.PDA=N7000ZSLPN
ro.build.hidden_ver=N7000ZSLPN
ro.build.changelist=1115729
# end build properties
#
# system.prop for smdk4210
#
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=320
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
#wlan.driver.apmode "unloaded"
media.enable-commonsource=true
persist.sys.storage_preload=1
#
#System property for qemu
#
ro.kernel.qemu=0
ro.lcd_min_brightness=40
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.opengles.version=131072
ro.sf.lcd_density=320
ro.config.ringtone=S_Over_the_horizon.ogg
ro.config.notification_sound=S_Whistle.ogg
ro.config.alarm_alert=Good_Morning.ogg
ro.config.media_sound=Media_preview_Touch_the_light.ogg
hwui.render_dirty_regions=false
ro.com.google.clientidbase=android-samsung
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.error.receiver.default=com.samsung.receiver.error
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
ro.secdirenc=true
ro.secsddecryption=true
ro.secfulldirenc=true
keyguard.no_require_sim=true
dev.sfbootcomplete=0
dev.powersave_fps=0
drm.service.enable=true
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
ro.setupwizard.mode=OPTIONAL
ro.com.google.apphider=off
ro.com.google.gmsversion=4.0_r5
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt

Any 1 installed this any feedback
Sent from my GT-N7000 using xda premium

Bump
Sent from my GT-N7000 using xda premium

I did. Seeme like the new tw etc update similar to LRQ and LRT.
It does not have samsung cloud services, but is localised with Chinese keyboarss etc.
Pretty smooth.
Rooted kernel here:
http://forum.xda-developers.com/showthread.php?p=31911656

2 Bugs i can see:
1. big size Widgets (ie. 5x5,3x4,2x5) will be recognized as smaller(5x5-->5x4,3x4-->3x3,2x5-->2x4)
2. if any apps moved to USB device, the icon will be moved from folder to out side after the phone reboot.

Yea its why I had phil add his recovery to the kernel.... you guys are a bit late to the party aren't you LOL.

Just update today, the Launcher was update, got popup player, Application Menu change !!!

just saw this on samfirmware and then came here to check for feedback lol
i wonder what took samfirmware so long to show this was available since it was supposedly released on sept 21? it didn't appear on the site at least when i checked 2 weeks ago...
very disappointing update imo since it appears to be a minor one...how is it the other regions have moved onto xxLRx fimrwares and Hong Kong is still stuck with xxLPx?

nitroblu said:
just saw this on samfirmware and then came here to check for feedback lol
i wonder what took samfirmware so long to show this was available since it was supposedly released on sept 21? it didn't appear on the site at least when i checked 2 weeks ago...
very disappointing update imo since it appears to be a minor one...how is it the other regions have moved onto xxLRx fimrwares and Hong Kong is still stuck with xxLPx?
Click to expand...
Click to collapse
Anyone else getting OTA update today? I'm on LPM stock rom and use hardcore's speed mod kernel with root.
Downloaded the 84MB OTA update but failed to upgrade firmware, likely because I'm rooted.
Does anyone know what this update is? According to Sammobile twitter some devices are getting JB 4.1.1 for testing ...
The update was LPN OTA indeed, but downloaded it from samfirmware instead and flashed it with mobile Odin, afterwards reflashed speed of kernel.
Very smooth sofar, only had to re-assign all widgets and shortcuts. There is a bug indeed with x5 horizontal widgets not showing properly...

smaragdhk said:
Anyone else getting OTA update today? I'm on LPM stock rom and use hardcore's speed mod kernel with root.
Downloaded the 84MB OTA update but failed to upgrade firmware, likely because I'm rooted.
Does anyone know what this update is? According to Sammobile twitter some devices are getting JB 4.1.1 for testing ...
The update was LPN OTA indeed, but downloaded it from samfirmware instead and flashed it with mobile Odin, afterwards reflashed speed of kernel.
Very smooth sofar, only had to re-assign all widgets and shortcuts. There is a bug indeed with x5 horizontal widgets not showing properly...
Click to expand...
Click to collapse
also got it today
still 4.0.4 but we have some of the features that were raved about in the s3
but re-doing all the pages on home screen is a pain

THanks

install SuperNexus rom for a pure JB experience... 4.1.2.. LOL
my guess is that, we will be receiving the JB update somewhere in the first weeks of december.. if you can't wait, there are a lot of custom JB roms out there..

Thanks for sharing
Sent from my GT-N7000 using Tapatalk 2

easttall said:
2 Bugs i can see:
...
2. if any apps moved to the external storage, the icon will be moved from folder to out side after the phone reboot.
Click to expand...
Click to collapse
Oh my god this. I was thinking I did something wrong with my setup, as everything was fine until I started moving apps to external storage. Here is what happens when you install an app to internal and then move it to external storage (through Titanium Backup, App2SD etc.):
You just moved an app to external. Upon the very next reboot, you will get an error in the notifications tray saying "Error: app info cannot be downloaded" or something. If you click the notification, it will take you to the Play Store market link and the "install" button will be available (as opposed to "open" or "uninstall"). However if you go back into your apps menu, the app still exists on your phone, and you still can open it.
If you put the moved apps into a folder in the apps menu (stock TW), they will "move back out" and be at the very end of the apps list upon next reboot. This is reproducable. Move app to external storage, problems start occuring. Move it back (or uninstall it), and the problem disappears.
This seems to be the only problem I have noticed, but it is a pretty major problem.
Just some background info, I came from a rooted stock N7000ZSLPF 4.0.3/12.05 Taiwan ROM to this N7000ZSLPN 4.0.4/12.09.15 Hong Kong ROM (because I wanted the Samsung Chinese keyboards).
The improvements include:
A much better looking app menu icon.
Home screen scrolling left-and-right has a 3D effect instead of the simple 2D scrolling (app menu still has 2D effect).
App menu now is separated between apps and widgets.
There is no more dark patch / background behind icons created on the home screens.
Startup times (including loading of background user apps) seems to be much quicker than before (from 4.0.3 anyway).
Now... due to the nature of the move-to-external-app-bug listed above I don't think this ROM is very usable at all (unless you plan to stay within the stock 2GB app storage limit). The only way I can think of going foreward for the people that want / need the Chinese keyboard is to either:
Go back to a stock 4.0.3 ROM (lol).
Extract the keyboards, flash another 4.0.4 ROM (e.g. Germany or something) and install the Chinese keyboard over that.
Wait for an official fix for this.
I haven't figured out which path I want to undertake yet, but I may go for number 2 from above, as this "bug" of sorts is just unacceptable.
Quick Update: Re-flashed ZSLPN 4.0.4 ROM and seeing if there is any way around it, trying clear Play Store cache, cache partition, Dalvik cache etc.

[Q] Jelly Bean Mini for P705

Hi All,
I installed the [ROM][L7]Jelly-Bean Mini Project 4.1.2(Release-5) on my P705. This is by far the best Rom for my device.
I have installed V10j Baseband. I have the following issues.
1. I do not have mobile Data, I can call and sms etc but cannot access internet over Mobile Data. I only receive mobile data if I add a v20 baseband but v20 doesn't work with this Rom. the other Rom i.e Kitkat or Carbon etc are still under development and are not really stable for me.
2. No Stock Radio.
Is it possible Port the Rom above with a v20 baseband or any other alternative so I can have internet access over mobile Network?
Is it possible to include stock Radio in the next release?
Thank you for the good work done on these rom, My device is reliving with this Rom.
Kersley

kerswhite said:
Hi All,
I installed the [ROM][L7]Jelly-Bean Mini Project 4.1.2(Release-5) on my P705. This is by far the best Rom for my device.
I have installed V10j Baseband. I have the following issues.
1. I do not have mobile Data, I can call and sms etc but cannot access internet over Mobile Data. I only receive mobile data if I add a v20 baseband but v20 doesn't work with this Rom. the other Rom i.e Kitkat or Carbon etc are still under development and are not really stable for me.
2. No Stock Radio.
Is it possible Port the Rom above with a v20 baseband or any other alternative so I can have internet access over mobile Network?
Is it possible to include stock Radio in the next release?
Thank you for the good work done on these rom, My device is reliving with this Rom.
Kersley
Click to expand...
Click to collapse
Radio is not working on all custom roms

Mobile Internet
zodex said:
Radio is not working on all custom roms
Click to expand...
Click to collapse
Thanks Zodex, As long as radio is concerned that's not a problem.
The only big issue is with Mobile Data which simply doesn't work. I confirm that on v20 baseband it works flawlessly, but v20 is not supported with this rom as I don't have network. that's driving me nuts. please help. I need mobile data working.

hi !
i really think that you have to clean your phone and reinstalling ....and quietly .
download :
this V10baseband ( it's a v10K "europe")=> https://drive.google.com/folderview?id=0B2Yt4LYuF0UuSkZUanB5Sm83azg&usp=sharing
the rom
this P705 kernel here (for you !) => http://forum.xda-developers.com/showthread.php?t=2619072
in CWM :
-wipe cache
-wipe data/factory
-wipe dalvik
-mont and storage : format SDcard (not the external Sd !!! where there are your .zip downloaded previously for to flash ) + format "system" => that all ! no other !!!
...and then flash in this order : ROM + P705 kernel +v10 baseband + Gapps
reboot you phone ,do the first install ,(try it few minutes ...) and reboot it( 1 or 2 times ) for to "fix" the rom if you have problems .

3g not working
Loulou-13 said:
hi !
i really think that you have to clean your phone and reinstalling ....and quietly .
download :
this V10baseband ( it's a v10K "europe")=> https://drive.google.com/folderview?id=0B2Yt4LYuF0UuSkZUanB5Sm83azg&usp=sharing
the rom
this P705 kernel here (for you !) => http://forum.xda-developers.com/showthread.php?t=2619072
in CWM :
-wipe cache
-wipe data/factory
-wipe dalvik
-mont and storage : format SDcard (not the external Sd !!! where there are your .zip downloaded previously for to flash ) + format "system" => that all ! no other !!!
...and then flash in this order : ROM + P705 kernel +v10 baseband + Gapps
reboot you phone ,do the first install ,(try it few minutes ...) and reboot it( 1 or 2 times ) for to "fix" the rom if you have problems .
Click to expand...
Click to collapse
I am trying this right now. I haven't seen anyone having this issue before so it's probably only me. everything else works except that network data 3g etc. i am desperate.

Problem Solved
kerswhite said:
I am trying this right now. I haven't seen anyone having this issue before so it's probably only me. everything else works except that network data 3g etc. i am desperate.
Click to expand...
Click to collapse
Fantastic, it was worth asking. i did try this once and I got all my applications etc back as if nothing happened. So i restarted the whole process. Wipe all, formated the whole system and started with a clean install. after that I added the network settings for my ISP, it said that registering with the proxy server failed but I can actually see the E on my network and since I am in a no network coverage sometimes in my office so, I can confirm that this is now working.. Thank you for your time guys. Loulou - 13. thanks a lot.

kerswhite said:
Fantastic, it was worth asking. i did try this once and I got all my applications etc back as if nothing happened. So i restarted the whole process. Wipe all, formated the whole system and started with a clean install. after that I added the network settings for my ISP, it said that registering with the proxy server failed but I can actually see the E on my network and since I am in a no network coverage sometimes in my office so, I can confirm that this is now working.. Thank you for your time guys. Loulou - 13. thanks a lot.
Click to expand...
Click to collapse
if you are happy ,click ":good: tanks " at the bottom of the pseudo and avatar

3g not working
In fact it stopped working again today. I seriously dont want to start flashing everything again as it would be my 50th flash probably. Any solution for me guys?
I never have this problem with a v20 baseband. I cant post to the developper forum on jelly bean mini to request for a built with v20a baseband, anyone know whether this is possible. If yes can someone request this for me on the jbmini post?

impossible to have a custom rom 4.1.2 with a V20 baseband because they are real ICS base... but with JB adds .
your problem is very strange !
look your APN very very carefully !
on my phone i have "near" to 100 flash i think ...L7 is a good phone !
---------- Post added at 01:40 PM ---------- Previous post was at 01:32 PM ----------
test by edit ( write or replace existing) the buit.prop values with these one .....and reboot phone :
ro.ril.hsxpa=2
ro.ril.gprsclass=12
ro.ril.hsdpa.category=16
ro.ril.hsupa.category=6
ro.telephony.default_network=3
for that ,with "es.explorer" for example you can edit this build.prop.

Packet data
Loulou-13 said:
I really appreciate your great work, but I still have these issues.
There was a couple of lines missing in what you gave me. I added ro.ril.hsdpa.category=16
ro.ril.hsupa.category=6, but it still wouldn'nt work,
below is a complete paste of the build prop. can you please direct me in the right way?
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JZO54K
ro.build.display.id=cm_p705-userdebug 4.1.2 JZO54K eng.jenkins.20131006.114111 test-keys
ro.build.version.incremental=eng.jenkins.20131006.114111
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.2
ro.modname=Jelly Bean Mini Project
ro.build.date=Sun Oct 6 11:41:41 PDT 2013
ro.build.date.utc=1381084901
ro.build.type=userdebug
ro.build.user=jenkins
ro.build.host=fedee
ro.build.tags=test-keys
ro.product.model=LG-P705
ro.product.brand=lge
ro.product.name=u0_open_eu
ro.product.device=p705
ro.product.board=p705
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=LGE
ro.product.locale.language=es
ro.product.locale.region=ES
ro.wifi.channels=
ro.board.platform=msm7x27a
# ro.build.product is obsolete; use ro.product.device
ro.build.product=p705
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=u0_open_eu-user 4.0.3 IML74K lgp705-V10a.20120418.144808 release-keys
ro.build.fingerprint=lge/u0_open_eu/u0:4.0.3/IML74K/lgp705-V10a.20120418.144808:user/release-keys
ro.build.characteristics=default
ro.cm.device=p705
# end build properties
#
# system.prop for p705
#
ro.sf.hwrotation=180
ro.sf.lcd_density=200
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.rommanager.developerid=JellyBeanMiniProject
keyguard.no_require_sim=true
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.modversion=Release-5
ro.modnamever=JBMP-Release-5
ro.config.ringtone=Orion.ogg
ro.config.notification_sound=Deneb.ogg
ro.config.alarm_alert=Hassium.ogg
ro.carrier=unknown
ro.ril.hsxpa=2
ro.ril.gprsclass=12
ro.ril.hsdpa.category=16
ro.ril.hsupa.category=6
ro.adb.qemud=1
debug.fb.rgb565=0
debug.sf.hw=1
debug.composition.type=mdp
ro.opengles.version=131072
com.qc.hardware=true
persist.sys.use_dithering=0
wifi.interface=wlan0
rild.libpath=/system/lib/libril-qc-1.so
ro.telephony.ril_class=LGEQualcommUiccRIL
ro.telephony.default_network=3
telephony.lteOnGsmDevice=0
persist.sys.usb.config=mtp,adb
ro.max.fling_velocity=12000
sys.mem.max_hidden_apps=15
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=96m
dalvik.vm.lockprof.threshold=500
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
# Graphics & Misc Properties
debug.composition.7x27A.type=mdp
ro.use_data_netmgrd=true
persist.data.ds_fmc_app.mode=0
ro.staticwallpaper.pixelformat=RGB_565
ro.max.fling_velocity=12000
httplive.enable.discontinuity=true
dev.pm.dyn_samplingrate=1
dev.pm.dyn_sample_period=700000
com.qc.hdmi_out=false
debug.qctwa.statusbar=1
debug.qctwa.preservebuf=1
debug.gr.numframebuffers=3
debug.qc.hardware=true
debug.enabletr=false
debug.hwui.render_dirty_regions=false
debug.sf.hw=1
debug.egl.hw=1
persist.sys.use_16bpp_alpha=1
dalvik.vm.heaptargetutilization=0.25
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=2m
ro.adb.secure=0
persist.sys.usb.config=mtp,adb
persist.service.adb.enable=1
ro.debuggable=1
ro.adb.qemud=1
debug.camcorder.disablemeta=1
persist.sys.scrollingcache=3
# Memory
# ro.zram.default=0
persist.sys.purgeable_assets=1
# Increase SKIA decode memory capability for progressive jpg file
ro.media.dec.jpeg.memcap = 20000000
ro.media.enc.jpeg.quality=100
dalvik.vm.checkjni=0
dalvik.vm.debug.alloc=0
dalvik.vm.dexopt-flags=v=a,o=v,m=y,u=y
dalvik.vm.execution-mode=int:jit
Click to expand...
Click to collapse

It must work , but you don't feel it ( do a speed data test on 3g/h with this app for example => https://play.google.com/store/apps/...rch_result&rdid=com.fhsarl.degrouptest&rdot=1 )
and install ADAWAY apk (see XDA) too ( all blocked spams are not charged => win some bandwidtch !)

no internet
Loulou-13 said:
It must work , but you don't feel it ( do a speed data test on 3g/h with this app for example => https://play.google.com/store/apps/...rch_result&rdid=com.fhsarl.degrouptest&rdot=1 )
and install ADAWAY apk (see XDA) too ( all blocked spams are not charged => win some bandwidtch !)
Click to expand...
Click to collapse
Loulou,
I have tried this and not working at, i tried reflashing with same issues. can you propose any other rom which is as smooth as this one but with a working 3g connection.

kerswhite said:
Loulou,
I have tried this and not working at, i tried reflashing with same issues. can you propose any other rom which is as smooth as this one but with a working 3g connection.
Click to expand...
Click to collapse
CM10 official + Phenom kernel V4.4 ..... and these scripts => http://forum.xda-developers.com/showthread.php?t=2630242

LG l7 giving up Jelly Bean Mini because of the Data Issues
Loulou-13 said:
CM10 official + Phenom kernel V4.4 ..... and these scripts => http://forum.xda-developers.com/showthread.php?t=2630242
Click to expand...
Click to collapse
Can you now give me the best tips to get my device working as smooth as possible with KitKat. I can confirm that 3g data works with Kitkat and v20d baseband. This phone is my personal phone but I use it for work purposes as the company pays for the plan. So i occasionally need to look at my emails when off from the office.
I still haven't been able to install it though, trying to do a clean install now.

for KK , CM11 and others are good for daily use , according to goods feedbacks on thread ! :good:

[Q] Android TV on Nexus Q?

Anyone else curious if Android TV will work on the Nexus Q?
If it is I am definitely going to try to port a version to it.

I was just wondering about this myself.
Here's something else they just released yesterday that might be of interest to us:
Google Cast Receiver
https://play.google.com/store/apps/details?id=com.google.android.apps.mediashell

Diznario said:
I was just wondering about this myself.
Here's something else they just released yesterday that might be of interest to us:
Google Cast Receiver
https://play.google.com/store/apps/details?id=com.google.android.apps.mediashell
Click to expand...
Click to collapse
Nice, I was wondering the same thing. I haven't seen anything indicating it wouldn't work. These things might end up front and center in my livingroom again...

Google Cast Receiver APK
Diznario said:
I was just wondering about this myself.
Here's something else they just released yesterday that might be of interest to us:
Google Cast Receiver
https://play.google.com/store/apps/details?id=com.google.android.apps.mediashell
Click to expand...
Click to collapse
Nice! Anyone hosting the Apk yet? Anyone peeked inside to see the minimum API level? Or try side loading it (potentially to system/priv-app) yet to another device?
Better yet, anyone have a system dump or factory image from an ADT-1 (Android TV Dev box given out at I/O today)? I'd bet it has an unlockable bootloader, so hopefully we'll have factory restore images.

It would be cool if the Android TV firmware could be ported or the Google Cast Reciver app could be sideloaded on the Nexus Q. I hope we can do this. I love the hardware. Small and stylish and sounds great.
Does the chromecast (Google Cast Reciver app) support multi room playback?

Anyone have any updated info on this? I would be amazing if we could sideload onto a Nexus Q - it was the perfect hardware for powering my outdoor speakers (I put it in a waterproof box).

Gtvhacker have uploaded the build.prop from a ADT-1 Android TV. So we can now spoof the Play store into thinking our device is a ADT-1 Android TV. Will have a try later.
http://gtvhacker.com/index.php/ADT-1_Android_TV_Sample_Build.prop

darren1 said:
Gtvhacker have uploaded the build.prop from a ADT-1 Android TV. So we can now spoof the Play store into thinking our device is a ADT-1 Android TV. Will have a try later.
http://gtvhacker.com/index.php/ADT-1_Android_TV_Sample_Build.prop
Click to expand...
Click to collapse
I tried to change the build.prop file on my Q to spoof the Play Store but no luck. Im located in sweden and only got that the app is not available in my country.

mannberg said:
I tried to change the build.prop file on my Q to spoof the Play Store but no luck. Im located in sweden and only got that the app is not available in my country.
Click to expand...
Click to collapse
Could you copy and post your build prop please?
Sent from my OnePlus One using xda app

Moose0704 said:
Could you copy and post your build prop please?
Click to expand...
Click to collapse
I can post my build.prop when I get home (@work). But I only changed these parameters:
ro.build.version.sdk=20
ro.build.tags=release-keys
ro.product.model=ADT-1
ro.product.brand=google
ro.product.name=molly
ro.product.device=molly
ro.product.manufacturer=Google
ro.build.fingerprint=google/molly/molly:L/LPV79/1236599:user/release-keys
ro.build.thumbprint=L/LPV79/1236599:user/dev-keys
this is the my edited build.prop. Anyone that is US based that can try to spoof the Play Store?
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=KOT49H
ro.build.display.id=cm_steelhead-userdebug 4.4.2 KOT49H 7bfcd95679 test-keys
ro.build.version.incremental=7bfcd95679
ro.build.version.sdk=20
ro.build.version.codename=REL
ro.build.version.release=4.4.2
ro.build.date=Fri Jan 3 13:23:17 PST 2014
ro.build.date.utc=1388784197
ro.build.type=userdebug
ro.build.user=howard
ro.build.host=thunderbolt
ro.build.tags=releas-keys
ro.product.model=ADT-1
ro.product.brand=google
ro.product.name=molly
ro.product.device=molly
ro.product.board=molly
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Google
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=omap4
# ro.build.product is obsolete; use ro.product.device
ro.build.product=molly
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=molly-user L LPV79 1236599 release-keys
ro.build.fingerprint=google/molly/molly:1236599:user/release-keys
ro.build.characteristics=nosdcard
ro.cm.device=steelhead
# end build properties
#
# from device/google/steelhead/system.prop
#
com.ti.omap_enhancement=true
#define a property for hdmi sink channel count
dolby.audio.hdmi.channels=0
persist.hwc.primary.tv=1
# Default color is 0x00385c
persist.sys.ringcolor=14428
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.rommanager.developerid=cyanogenmod
ro.com.google.clientidbase=android-google
keyguard.no_require_sim=true
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.build.selinux=1
persist.sys.root_access=1
ro.cm.version=11-20140103-UNOFFICIAL-steelhead
ro.modversion=11-20140103-UNOFFICIAL-steelhead
ro.cmlegal.url=http://www.cyanogenmod.org/docs/privacy
ro.config.ringtone=Orion.ogg
ro.config.notification_sound=Argon.ogg
ro.config.alarm_alert=Hassium.ogg
net.dns1=8.8.8.8
net.dns2=8.8.4.4
ro.carrier=unknown
wifi.interface=wlan0
hwui.render_dirty_regions=false
ro.sf.lcd_density=213
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=2m
persist.sys.dalvik.vm.lib=libdvm.so
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt

No luck on my N7 '13 trying to pull the Cast Receiver apk using the build.prop either. It gets flagged as the wrong hardware still.

Grishka11 has posted the apk on this thread
http://forum.xda-developers.com/har...ast/apk-adt-1-cast-receiver-leanback-t2814210
Only installs on Kit Kat or Android L. Doesn't do anything on my Nexus 10 running 4.4.2. Decompiled and altered the minimum sdk version and installed it on a Jellybean Android box and again does nothing.

I got this in logcat when I installed
./adb logcat | grep mediashell
I/PackageManager( 462): Running dexopt on: com.google.android.apps.mediashell
I/ActivityManager( 462): Force stopping com.google.android.apps.mediashell appid=10093 user=-1: update pkg
W/PackageManager( 462): Unknown permission android.permission.ACCESS_DRM_CERTIFICATES in package com.google.android.apps.mediashell
W/PackageManager( 462): Unknown permission android.permission.HDMI_CEC in package com.google.android.apps.mediashell
D/BackupManagerService( 462): Received broadcast Intent { act=android.intent.action.PACKAGE_ADDED dat=package:com.google.android.apps.mediashell flg=0x4000010 (has extras) }
I/ThemeManager( 713): Handling new theme package: com.google.android.apps.mediashell
I/InstallAppProgress( 3442): Finished installing com.google.android.apps.mediashell
D/PackageBroadcastService( 960): Received broadcast action=android.intent.action.PACKAGE_ADDED and uri=com.google.android.apps.mediashell
I/IcingCorporaProvider( 898): Updating corpora: APPS=com.google.android.apps.mediashell, CONTACTS=MAYBE
Click to expand...
Click to collapse
and I cant find a running service for the cast app
./adb shell service list
Found 82 services:
0 sip: [android.net.sip.ISipService]
1 phone: [com.android.internal.telephony.ITelephony]
2 isms: [com.android.internal.telephony.ISms]
3 iphonesubinfo: [com.android.internal.telephony.IPhoneSubInfo]
4 simphonebook: [com.android.internal.telephony.IIccPhoneBook]
5 nfc: [android.nfc.INfcAdapter]
6 assetredirection: [com.android.internal.app.IAssetRedirectionManager]
7 media_router: [android.media.IMediaRouterService]
8 print: [android.print.IPrintManager]
9 assetatlas: [android.view.IAssetAtlas]
10 dreams: [android.service.dreams.IDreamManager]
11 commontime_management: []
12 samplingprofiler: []
13 diskstats: []
14 appwidget: [com.android.internal.appwidget.IAppWidgetService]
15 backup: [android.app.backup.IBackupManager]
16 uimode: [android.app.IUiModeManager]
17 serial: [android.hardware.ISerialManager]
18 usb: [android.hardware.usb.IUsbManager]
19 audio: [android.media.IAudioService]
20 wallpaper: [android.app.IWallpaperManager]
21 dropbox: [com.android.internal.os.IDropBoxManagerService]
22 search: [android.app.ISearchManager]
23 country_detector: [android.location.ICountryDetector]
24 location: [android.location.ILocationManager]
25 devicestoragemonitor: []
26 notification: [android.app.INotificationManager]
27 profile: [android.app.IProfileManager]
28 updatelock: [android.os.IUpdateLock]
29 servicediscovery: [android.net.nsd.INsdManager]
30 connectivity: [android.net.IConnectivityManager]
31 wifi: [android.net.wifi.IWifiManager]
32 wifip2p: [android.net.wifi.p2p.IWifiP2pManager]
33 netpolicy: [android.net.INetworkPolicyManager]
34 netstats: [android.net.INetworkStatsService]
35 textservices: [com.android.internal.textservice.ITextServicesManager]
36 network_management: [android.os.INetworkManagementService]
37 clipboard: [android.content.IClipboard]
38 statusbar: [com.android.internal.statusbar.IStatusBarService]
39 device_policy: [android.app.admin.IDevicePolicyManager]
40 lock_settings: [com.android.internal.widget.ILockSettings]
41 mount: [IMountService]
42 accessibility: [android.view.accessibility.IAccessibilityManager]
43 input_method: [com.android.internal.view.IInputMethodManager]
44 bluetooth_manager: [android.bluetooth.IBluetoothManager]
45 input: [android.hardware.input.IInputManager]
46 window: [android.view.IWindowManager]
47 alarm: [android.app.IAlarmManager]
48 consumer_ir: [android.hardware.IConsumerIrService]
49 vibrator: [android.os.IVibratorService]
50 battery: [android.app.IBatteryService]
51 hardware: [android.os.IHardwareService]
52 content: [android.content.IContentService]
53 account: [android.accounts.IAccountManager]
54 user: [android.os.IUserManager]
55 entropy: []
56 permission: [android.os.IPermissionController]
57 cpuinfo: []
58 dbinfo: []
59 gfxinfo: []
60 meminfo: []
61 procstats: [com.android.internal.app.IProcessStats]
62 activity: [android.app.IActivityManager]
63 package: [android.content.pm.IPackageManager]
64 scheduling_policy: [android.os.ISchedulingPolicyService]
65 telephony.registry: [com.android.internal.telephony.ITelephonyRegistry]
66 display: [android.hardware.display.IDisplayManager]
67 appops: [com.android.internal.app.IAppOpsService]
68 usagestats: [com.android.internal.app.IUsageStats]
69 batterystats: [com.android.internal.app.IBatteryStats]
70 power: [android.os.IPowerManager]
71 sensorservice: [android.gui.SensorServer]
72 SurfaceFlinger: [android.ui.ISurfaceComposer]
73 media.audio_policy: [android.media.IAudioPolicyService]
74 media.camera: [android.hardware.ICameraService]
75 media.player: [android.media.IMediaPlayerService]
76 media.audio_flinger: [android.media.IAudioFlinger]
77 drm.drmManager: [drm.IDrmManagerService]
78 batterypropreg: [android.os.IBatteryPropertiesRegistrar]
79 android.security.keystore: [android.security.keystore]
80 common_time.config: [android.os.ICommonTimeConfig]
81 common_time.clock: [android.os.ICommonClock]
Click to expand...
Click to collapse
And nothing that is named cast, mediashell or something similar in ./adb shell ps. Maybe something with the unknown permission.

I think we need those from /system/etc/permissions to keep trying. I'll let Grishka know and see if he can adb pull them. :good:

Anything new yet?

anyone have any luck on this?

[ROOTED] How to root AC83XX Head Unit MCU: TS901.151104 w/New Skins

New Skin for Radio (see the attachment).
Rooting Guide for AC83XX (AutoChips 8317,8327) (SoC) MTK 6630 - MTK 8317 - MTK 8327 - MTK 82XX
How to gain root access on your android head unit:
[0] Install Terminal Emulator and SuperUser (I used Chainfire's) from Play Store.
[1] Download Superuser.zip (from Chainfire's website) (which includes su binary file in .zip) Extract the files to a directory that you can remember later. e.g: "roo" is my folder name which includes superuser.zip files. (mnt/sdcard/roo/)
[2] Open terminal and type:
Code:
/sbin/forfan guoboneedav -i
*"guoboneedav" is the su password in that "forfan" file in "/sbin" dir. You can find sbin(sbin.rar) directory contents at the attachment
[3] Mount /system folder rewriteable if neccesary.
Code:
mount -o rw,remount,rw /system
[4] Then type to copy su binary by
Code:
cp mnt/sdcard/roo/system/xbin/su /system/xbin/
[5] Open SuperUser app that you installed before and Update Su Binary when it asks.
Congrats! You have gained root access on your android head unit.
*** Disclamer *** Flash this at your own risk. Please note that I no longer have the device. You may not use physical volume knob on some devices like Ownice C300 etc. after flashing MainUI.apk
RADIO Skin
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

The files below are the main apk and zip. - and SoC info:
AC8327
Overview
AC8327 is a feature and performance scalable platform that can support Android, WINCE, Linux based on the ARM Cortex architecture, including Cortex-A7, combined ARM9 based solutions.
AC8327 series combines broad levels of integrated interfaces and power-efficient processing capabilities all the way up to bleeding edge 3D and 2D graphics, as well as high-definition video, eg: H.265, ,to provide a new level of multimedia performance for an unbounded next-generation user experience. AC8327 series also supports HDMI/MHL interfaces to fit the trend of Vehicle-Cell phone connection. Internal audio DSPs and DAC insures the acoustic performance and cutting off the system BOM cost.
Features
- DVD/CD Integration
- Quad Cortex A7 up to 1GHz
- Mali 400 MP2
- H.265/H.264/ MPEG-4/ RMVB/ VP6/VP8/MPEG-2/AVS/VC-1
- CVBS In/ CCIR 656/601/ Video switch/YPbPr(720P)
- 5.1 channel for front / stereo for rear
- SPIDF out / I2S out
- PCM audio playback
- Dual channel Display
- TV Decoder
- Touch Screen Controller
Our devices using almost the same components and firmware with Ownice C300 head unit's.
*** Update ***
Make Viper4Android working for Head Units:
devilsoft said:
Try also the Viper4Android, and you will notice a HUGE difference in sound quality.
For anybody interested to use Viper4Android, follow this steps:
1. Install the apk from this post
2, Install viper fx drivers when prompted (Choose Super Audio Quality)
3. Restart device
4. Open Viper4Android from Launcher, go to menu, then click "Lock Effect Mode" and choose "Headset"
5. Go To Menu, click "UI Setting" and choose "Expert", to gain access to more options
6. Go to "Headset" tab, and click "Enable"
7. Enable and play with different options, according to your taste in sound
In PowerAmp, in order to enable Viper4Android, you need to uncheck "Direct Volume Control" from Settings -> Audio -> Advanced Tweaks
To start Viper FX from install-recovery.sh, use this command:
Code:
am startservice com.vipercn.viper4android_v2/.service.ViPER4AndroidService
Viper FX affects all the apps sounds (autio player, video player, bluetooth, youtube, etc), but not Radio, which is MCU controlled.
P.S.
More about Viper4Android, can be found here: http://forum.xda-developers.com/showthread.php?t=2191223
Click to expand...
Click to collapse
OT: Solutions and FAQ about most of the head units In this thread
OT: http://forum.xda-developers.com/showpost.php?p=58750777&postcount=8521
*** (16/12/16) SOC (system-on-a-chip) info MT6630
Mediatek Announces MT6630, World�s First Five-in-One Combo Wireless Connectivity SOC for Mobile Devices
Mediatek Announces MT6630, World�s First Five-in-One Combo Wireless Connectivity SOC for Mobile Devices
TAIWAN, Hsinchu � 25 February, 2014 � Mediatek today announced MT6630, the world�s first five-in-one combo wireless system-on-a-chip (SOC) to support full featured smartphones, tablets and other premium mobile devices.
The MT6630 dramatically reduces the component count and eBOM while improving ease-of-design for manufacturers by eliminating external low noise amplifiers (LNAs) and integrating the Wi-Fi 2.4 GHz and 5 GHz power amplifiers (PAs), Bluetooth PA, and transmit-receive (T/R) switch into a PCBA footprint less than 65 mm2.
Key features
Dual-band single-stream 802.11a/b/g/n/ac with 20/40/80MHz channel bandwidth
802.11v time of flight protocol support and management engines to enable higher accuracy of indoor positioning via Wi-Fi
Advanced support for Wi-Fi Direct Services and Miracast� optimization for easier pairing, increased robustness, advanced use-cases and lower power
Bluetooth 4.1 with Classic, High-Speed and Low-Energy support, and ANT+ for compatibility with the latest fitness tracking, health monitoring and point of information devices and applications
Concurrent tri-band reception of GPS, GLONASS, Beidou, Galileo and QZSS with industry leading sensitivity, low power, positioning accuracy, and the longest prediction engine
FM transceiver with RDS/RBDS
Integrated engines and algorithms for full concurrent operation and co-existence, including industry-leading throughput during LTE transmission
MT6630 delivers full concurrent operation of all 5 systems operating at maximum compute intensity with no degradation compared to single-system operation while offloading the mobile device CPU for design ease and extended battery life. As a focus on low power and digital home convergence, the MT6630 uses a configurable PA architecture to save current at commonly used power levels, including those used for Miracast� Wi-Fi Direct services. MT6630 implements advanced co-existence techniques, including for LTE to deliver industry-leading throughputs. MT6630 also supports Wi-Fi diversity for premium smartphones and tablets to improve antenna angle sensitivity and handheld scenarios.
"MT6630 makes it simple for manufacturers to bring mobile devices to market with sophisticated wireless features, lower power and uncompromised performance," said SR Tsai, General Manager of MediaTek�s Connectivity Business Unit. �MT6630 furthers MediaTek�s focus to deliver the best experiences across the digital home and mobile applications by using its unique leadership position in digital TV host processors, smartphone platforms, and connectivity.�
The small-footprint design is available in 5 x 5mm WLCSP (Wafer Level Chip Scale Package) or a 7 x 7mm QFN (Quad Flat No-Leads) and requires only 44 components, which is around half that of other integrated wireless solutions.
Mediatek MT6630 is sampling now and complements the recently announced MT6595 octa-core SOC with LTE for premium mobile devices. The first commercially available devices to use MT6630 are expected in the second half of 2014.
DEVICE INFORMATION
Manufacturers:
+ SZ MAISUN
Local Brands (Sold as) :
Navimex ... many more[/I]
SPECS:
MCU: TS901.151104
SOC: AC8317 (AC83XX)
SoC Manufacturer: ATC (Autochips, MediaTek)
AC83XX (Core x4) QuadCore 1 ghz
ARM Cortex-A7 MP Core Product Revision r0p3
Android Version: KitKat 4.4.4.
1 GB RAM
16 GB ROM
1024 x 600
Mali 400 MP, GPU
Finally got root access on TS901.151104 device: Big thanks to @Virus.VHD
Virus.VHD said:
Hi,
I've found a way to get root on this unit:
1. Open terminal and enter:
/sbin/forfan guoboneedav -i
2. You should get root console #
3. Replace /system/xbin/su with the one taken from SuperSU
4. Install and run SuperSU
5. Update su binary when asked to.
6. Enjoy!
Click to expand...
Click to collapse
I am unable to find any information about my Android Head Unit. So I've started to tinker by myself.
I've changed default launcher to Nova, then use Quick Shortcut Manager to use OEM apps (FM Radio, Factory Settings, DVD, Music app) which included in com.ts.MainUI.apk
Every oem app is included in one apk and I set shortcuts from it. (com.ts.Radio.... com.ts.Music... etc)
** Scheme of AC8317 SoC. I think that it is a MediaTek cpu.
** Device Pictures:
** Update II, UI screenshots of head unit - AC8317 SoC
Then I extract main (factory)Settings.apk (not usual android Settings.apk) , I have found the secret codes
* Boot Logo manager
5678
* Factory Settings
8888
* File Copy (?)
1234
...
0126 or 126 not working.
--
HMI: TSKJ_ 010.16.03.30.08.37
MCU:TS901.151104
--

recherche rom kk 4.4 for ac8317
Hello,
I buy a car stereo in China, but the problem and should be in 4.4.4 but is 4.2.2.
despite my correspondence with the seller sent me that if always rom 4.2.2.
you'd have a rom kitkat 4.4.4 or higher? or knew you or I can find?
I know the procedure updated its model (already realize several times).
for information, here is the build.prod contained in the last file that I send:
[# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JDQ39E
ro.build.display.id=generic_ac8317-userdebug 4.2.2 JDQ39E eng.root.20160521.100526 test-keys
ro.build.version.incremental=eng.root.20160521.100526
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.2
ro.build.date=2016年 05月 21日 星期六 10:08:07 CST
ro.build.date.utc=1463796487
ro.build.type=userdebug
ro.build.user=root
ro.build.host=ubuntu
ro.build.tags=test-keys
ro.product.model=Generic Android on ac8317
ro.product.brand=Android
ro.product.name=generic_ac8317
ro.product.device=ac8317
ro.product.board=
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=ATC
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=ac8317
# ro.build.product is obsolete; use ro.product.device
ro.build.product=ac8317
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=generic_ac8317-userdebug 4.2.2 JDQ39E eng.root.20160521.100526 test-keys
ro.build.fingerprint=Android/generic_ac8317/ac8317:4.2.2/JDQ39E/eng.root.20160521.100526:userdebug/test-keys
ro.build.characteristics=tablet // changed from tablet
# end build properties
#
# ADDITIONAL_BUILD_PROPERTIES
#
persist.sys.timezone=Asia/Shanghai
keyguard.no_require_sim=true
ro.com.android.dataroaming=true
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=pixiedust.ogg
ro.carrier=unknown
ro.config.alarm_alert=Alarm_Classic.ogg
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
dalvik.vm.lockprof.threshold=500
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.rom.fingerprint=655870745a77
I await your return and you know yours for the future.

I have this radio as well. Have you found the a7 only runs on 2 cores? Mine always says core 2 and 3 is off. Have you found a way to root it or update it?

I couldn't find any way to root it. It has its own MCU update code in the Factory Settings, if you type 0 (zero) you can access it. Another method is to reboot in to recovery via terminal app. You can download to your head unit via Play Store. Just type "adb devices" to check at first or " adb reboot recovery" (w/o quotes) to boot into recovery.
I think the device is rooted but fakes it unrooted
ro.build.tags=test-keys
That tag can be release-keys but I couldn't changed it yet.
I just found that the manufacturer of our units could be Star Navi (Shenzhen) Company.

I have the same. Developer options is not visible. I install usb debug software from play store and usb debugging on. But all root program failed. I install the supersu from play store. I received a warning that already installed the supersu.apk. How to factory setting code for root???

kehadamus said:
I have the same. Developer options is not visible. I install usb debug software from play store and usb debugging on. But all root program failed. I install the supersu from play store. I received a warning that already installed the supersu.apk. How to factory setting code for root???
Click to expand...
Click to collapse
Same here. To access developer options, you need to install an app from Play Store; called "Developer Options". Factory setting code for mine is 8888, for another codes check the first post above.

mrtnb said:
Same here. To access developer options, you need to install an app from Play Store; called "Developer Options". Factory setting code for mine is 8888, for another codes check the first post above.
TR:
"Hocam sanırım sen de Türksün. Developer Options diye bir uygulama var Play Store'da oradan açabilirsin. Cihazın markası Navimex mi?"
Click to expand...
Click to collapse
Evet Hocam. Buraya taktırmıştım. https://www.sahibinden.com/ilan/yedek-parca-aksesuar-donanim-tuning-oto-goruntu-sistemleri-multimedya-oynatici-navix-nvx-a744-android-kia-ceed-uyumlu-internetli-oem-teyp-297330384/detay/
Uygulamayı usb debugging yapmak için kullandım. ardından root yapabilirim umuduyla. kingroot,kingoroot ve bikaç tane daha denedim root yapamadım. Bir de sağdaki microsd'yi görmemeye başladı. Fabrika ayalarına dönsem düzelir mi acaba? En önemli sorunumda usbden htc one m9 u görüyor ama ipod classic'i görmüyor.

Plese more explain
Hocam bendede Navimex var nova kurunca mp3 player için falan kısa yol yapmıyorum bu paylaştığın uygulama ne işe yarıyor bu şifreler menülere girmenimi sağlıyor

alex.o said:
I have this radio as well. Have you found the a7 only runs on 2 cores? Mine always says core 2 and 3 is off. Have you found a way to root it or update it?
Click to expand...
Click to collapse
please share comminications information
hocam bana kısaca launcher yüklemeyi falan anlatabilir misin?

alp2019 said:
Plese more explain
Hocam bendede Navimex var nova kurunca mp3 player için falan kısa yol yapmıyorum bu paylaştığın uygulama ne işe yarıyor bu şifreler menülere girmenimi sağlıyor
Click to expand...
Click to collapse
To access OEM apps like FM Radio, Music Player... with another launcher you must install an app like Quick Shortcut Manager, Activity Shortcut etc. then find the main OEM apk. E.g. mine is Ts8317 (MainUI.apk)
You should see all oem shortcuts (eg: com.ts.Radio....) under your head unit's main.apk at the Activities tab. Change the shortcut's title and logo as your choice.

Thanks for letting me know about this thread. I took some pics and compared with yours and they are identical.

Quote:
Originally Posted by demirbas44
Model Numarası
AC83XX (core X4)
Android Sürümü
4.4.4
Ana Bant Sürümü
Bilinmiyor
Çekirdek Sürümü
3.4.35
[email protected] #38
tue Mar 29 16:08:55 CST 2016
Derleme Numarası
generic_ac8317-userdebug 4.4.4 JDQ39E eng.root.20160329.160958 test_keys
My device navimex brand.
I can not find compatible launcher.
I ran across an embedded application and release (radio music bt applications ..) does not see
"Benim cihaz navimex marka.
Uyumlu launcher bulamıyorum.
bulsamda gömülü uygulamlar (radyo müzik bt uygulamaları ..) görmüyor"

demirbas44 said:
Quote:
Originally Posted by demirbas44
Model Numarası
AC83XX (core X4)
Android Sürümü
4.4.4
Ana Bant Sürümü
Bilinmiyor
Çekirdek Sürümü
3.4.35
[email protected] #38
tue Mar 29 16:08:55 CST 2016
Derleme Numarası
generic_ac8317-userdebug 4.4.4 JDQ39E eng.root.20160329.160958 test_keys
My device navimex brand.
I can not find compatible launcher.
I ran across an embedded application and release (radio music bt applications ..) does not see
Click to expand...
Click to collapse
To access OEM apps like FM Radio, Music Player... with another launcher you must install an app like Quick Shortcut Manager, Activity Shortcut etc. then find the main OEM apk. E.g. mine is Ts8317 (MainUI.apk)
You should see all oem shortcuts (eg: com.ts.Radio....) under your head unit's main.apk at the?*Activities?*tab. Change the shortcut's title and logo as your choice.
TR
Dostum fm radyo, müzik çalar gibi uygulamalar? ba?ka launcher la açmak istiyorsan, Quick Shortcut Manager vb bir uygulama kur. Sonras?nda Activities sekmesinden MainUI.apk ya bas, alt?nda com.xxxxx ile baslayan alt uygulamalar var. Bunlardan istediklerini seç, Create Shortcut de. ?stedi?in launcher a eklenir art?k.

Thank you
---------- Post added at 07:22 PM ---------- Previous post was at 07:19 PM ----------
another study fm radio apk series?
Tr
Baska calisan daha estetik fm radyo apk si varmi?

demirbas44 said:
Thank you
---------- Post added at 07:22 PM ---------- Previous post was at 07:19 PM ----------
another study fm radio apk series?
Tr
Baska calisan daha estetik fm radyo apk si varmi?
Click to expand...
Click to collapse
You're welcome. I tried to install other fm apks, even tried from another mcu's but none of them work. OEM apps working with their mcu's only for now (at least our devices).
TR
Rica ederim. Başka radyo kurmayı denedim, ama hep force close hatası alıyorum. Cihazı güncelletirseniz en son radyo fena değil. Ben dün yeni yazılım yüklettim.

....

mrtnb said:
You're welcome. I tried to install other fm apks, even tried from another mcu's but none of them work. OEM apps working with their mcu's only for now (at least our devices).
TR
Rica ederim. Başka radyo kurmayı denedim, ama hep force close hatası alıyorum. Cihazı güncelletirseniz en son radyo fena değil. Ben dün yeni yazılım yüklettim.
Click to expand...
Click to collapse
yeni yazılımı nerde yüklettiniz radio dışında bir farkı var mı

Mine won't save radio station presets when the car turns off and back on, it resets the radios presets and equalizer settings. How can I fix this?

Few questions
thanks for this post to mrtnb.
I have couple of questions.
Did you handle the problem with radio app?
It's really annoying me because always firstly show up whenever headunit is boot.
I never use radio app, can I erase it?
Also, It has little white noise.. didn't you recongnize??
++ your radio app is different from mine.. did you change system app?? or is there any other firmware???