Database Info

WorldCallPlaceAndTime

Hi! Let me introduce a tiny app, available in English in the moment.
This program shows a small info window during incoming/outgoing call. It contents country, region, city (or mobile operator) and LOCAL TIME in that place (worldwide)!
See latest comments and screenshots on cyrket (I'm not allowed to insert links)
Detailed popup customization is supported
The phone base I collected and created (many errors there were fixed by hands) was only available in Russian, but today I released English base, made with help of Google Translate
I know, such translation is buggy (but still much better I expected). I hope you'll help me and other users to have a complete and accurate information about calls - just email me right from the program menu about any issues or comment here.
World time also changes (for example, Russia lost two time zones this March) and if you find any error - post here or email me

You don't need to download phone base. You may download its latest version from the app, but if you want to do it manually, unpack the zip to the sdcard's root

How accurate does it get? I don't get many international calls, but might be useful to know where a landline call from within the UK is coming from?
What happens with mobile calls from with the UK? I assume no detail at all then?

it covers both landline and mobile network all over the world, where it is possible to distinguish between numbers by area codes. just try =) there are more than 25000 records in the base
Sent from my T-Mobile G1 using the XDA mobile application powered by Tapatalk

Hi. How do you set this up?
I have placed my Country Code (00351) and set GMT to +1 and when I call from my desk to my phone, it says it's a call from India ...

afaik, country code cant starts with zeros. Please, provide full number (you may hide last four digits) and right country for you I'll check and write settings here

Erm, I think techinally it either starts with two zeros, or a + but you're asking for a single number?
For example, UK is either 0044 or +44

wow. That is new for me. I know that with one leading zero start local calls. And you say two zeros replace + . hmmm. try left country code blank, that may help, I think. and if not, please, type whole number without four last digits

Not sure if this is already obvious but as there seems some uncertainty. AIUI the correct way to state an international number is to prefix it with +. To make a call, the plus sign is replaced with the two (or sometimes three or four) digit international access code which depends on the country one is placing the call from. For Europe this is 00, for the States, 011 etc.

I'm in Portugal, and my number is +35193233xxxx. I have tried leaving it blank, but by default leaves a 7... tried with 00351, with 351 and when calls are incoming still stays it's from India.
I'll wait for further clarification and if nothing happens I'll un-install it.
By the way, it doesn't let me use the +.
Thanks

okay, and what was the incoming number? what it was looking like on the call screen? country code preset replaces leading zero or eight digit. so it doesn't interfere number detection in you case I think
Sent from my T-Mobile G1 using the XDA mobile application powered by Tapatalk

The incoming number was looking like this: 91811xxx
It's a mobile number from Vodafone.

Just got a call from Germany, and it identified the Country and city allright. Seems that it doesn't work for calls inside Portugal only...

i see eight digits and no country info in this number. if there are seven digits program says local call and do not provide any information (because there is no trusted information) in eight or more digits it tries to detect country code. it replaces leading 8 or 0 with country code from the settings - for example local russian mobile calls may look like 8916xxxyyzz - we replace 8 with country code 7 and identify it with MTS - the program even say region or city based on x or xx or xxx in the example above. but in your situation I have no idea how to detect that the call is local and country code needs to be put before the number =( I've never heard that income mobile number may be in the format you wrote - it should start with plus sign and country code or 8 or zero (Ukraine, Moldova). I'm whirled
Sent from my T-Mobile G1 using the XDA mobile application powered by Tapatalk

Any chance you can convert the database into something human-readable? I'll be glad to cross reference a bunch of Southern California area codes and prefixes so that you can get some more accurate data there.
Also, a program similar to yours got hit with a cease & desist a few months back by some patent trolls because they supposedly hold a patent on this very thing. You're in Russia though so I dunno if their reach extends to you. Just thought I'd give you an FYI.

XStylus said:
Any chance you can convert the database into something human-readable? I'll be glad to cross reference a bunch of Southern California area codes and prefixes so that you can get some more accurate data there.
Also, a program similar to yours got hit with a cease & desist a few months back by some patent trolls because they supposedly hold a patent on this very thing. You're in Russia though so I dunno if their reach extends to you. Just thought I'd give you an FYI.
Click to expand...
Click to collapse
please, email me a t r a n t . s g @ g m a i l . c o m (or from the program menu) to discuss db elements, thanks in advance.
and yeah... i've read that stuff and even contacted the author...
But, my program is better now, I think =) And I will hit 10000 downloads, I hope. That will be enough, I think, for my efforts and hand-made db =))

Uninstallation
How do i uninstall de database, can't find it but i takes 3 mb of internal memory. Anyone has a suggestion!!

castor.troy said:
How do i uninstall de database, can't find it but i takes 3 mb of internal memory. Anyone has a suggestion!!
Click to expand...
Click to collapse
Just remove the DB app. There is no way to leave DB app and remove the DB, android OS restriction (can't modify signed apk on the device)

uninstallation
So when i uninstall WorldCallPlaceAndTime.apk than de database will be removed from my internal memeory?
Castor

castor.troy said:
So when i uninstall WorldCallPlaceAndTime.apk than de database will be removed from my internal memeory?
Castor
Click to expand...
Click to collapse
Sure, man! Do it right now!

AGPS Patch Inspire 4G 3.1 & 2.2 | GET BACK TO RAPID GPS LOCK, CAN LOCK ONTO MORE SATS

AGPS Patch Inspire 4G 3.1 & 2.2 | GET BACK TO RAPID GPS LOCK, CAN LOCK ONTO MORE SATS
AGPS PATCH
REVIEW THE WHOLE THREAD BEFORE POSTING QUESTIONS.
List of officially supported devices is at the bottom of this post.
Use this if you're having GPS issues (unreliability, no functionality, etc.)
This patch provides a worldwide solution to GPS issue for multiple devices. Using a general ROM without this has resulted in 10+ minutes of GPS delay. Also, GPS lock kept being lost. By using this patch, most people experience a GPS lock within 10 seconds (2 - 20 seconds range can be expected). Typically, a device using this patch will lock onto 7 - 9 satellites. Users have reported up to 11 satellites being locked at once. Without this patch, the average satellite count is 4.
HOWTO INSTALL: (Remember to make a backup. See Notes section for what this patch does.)
Method 1:
1. Download the "ADB Push Installer". This contains all versions for the latest build and old v1.3 versions.
2. Extract the files into a specific folder.
3. Plug your device into the computer and get it ready for adb pushing. Nothing out of the ordinary required.
4. Open the batch file called "ADB Installation Script - RUN THIS" if you use Windows. Otherwise, run the Linux SH script if you use Linux.
5. Select the version you want from the list.
6. Follow the prompts to reboot. You're done.
4. Review the NOTES section.
Method 2:
1. Download the patch
2. Copy all file(s)* into /etc/ of the system (not sd-card) using ES File Explorer, Root Explorer, or some other form. You must have SYSTEM set to Mounted and Root enabled. Check your explorer app's SETTINGS to do this.
**Files will be: gps.conf & SUPLROOTCERT -OR- only gps.conf for NO-SSL builds.**
3. Reboot the device
4. Review the NOTES section.
*Files are located in the /system/ folder of the ZIP. Do not copy the other directories or folders.
Method 3 (easiest if you use a compatible version of CWR or CWM)*:
1. Download the patch
2. Boot into CWR (Clockwork Recovery)
3. Mount /system/ partition (on the main menu, select the "Mounts and storage" option, then "mount /system")
4. Flash the patch (on the main menu, select "Install zip from sdcard," then "choose zip from sdcard," and find the zip and select it)
If you receive "(Status 0) Installation aborted" this Method will not work for you. Use one of the other methods.
5. Reboot the device
6. Review the NOTES section.
*This was built for and works on Inspire 4G and DesireHD versions of Clockwork Recovery. The Google CWM Flashable Build has binaries known to work with CWM on the X8. It may work on other devices. Please message me your success if you try and flash with recovery version and phone model as part of the message.
Downloads:
SEE THE NOTES SECTION (PARTICULARLY NOTES 1,2, & 3) FOR ALL SORTS OF INFORMATION AND FACTS ABOUT THIS PATCH, WHAT EACH BUILD IS FOR, VERSION DIFFERENCES, AND KNOWN ISSUES WITH SOLUTIONS.
Recommended Builds (pick either):
Download the Google Specific No-SSL v3.1 build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific v3.1 build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Confused with all the options below? As the Notes section dictates: I recommend the GOOGLE BUILD of all devices. Other builds have changes in their SUPL server information and/or other variables pertinent to that manufacturer. These builds do not appear to operate as fast as Google build's but are available for your enjoyment.
3.x trunk Alternative Options (currently v3.1)
Download the ADB Push Installer here. (contains all current builds and v1.3 builds) (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific NO-SSL TWRP build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific NO-SSL build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific CWM Flashable build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the AT&T Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the T-Mobile Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Sony Ericsson Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
*The alternate patch removes a variable that some GPS hardware on older models cannot handle. Try this if you have problems with the standard patch.
2.x trunk Alternative Options (currently v2.2)
Download the ADB Push Installer here. (contains all current builds and v1.3 builds) (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific NO-SSL build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific CWM Flashable build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the AT&T Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the T-Mobile Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Sony Ericsson Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
*The alternate patch removes a variable that some GPS hardware on older models cannot handle. Try this if you have problems with the standard patch.
Changelog: (I'll try to keep this correct and current)
Code:
v3.1 update - New Version
introduced the NO SSL version for Google build. Shows faster performance times.
v3.1(HELP WITH THE MAINTANENCE COSTS - DONATE A FEW BUCKS)
introduced my own NTP pools
repaired the LG Alternate build (was same as standard build, compilation error)
v3.0 (HELP WITH THE MAINTANENCE COSTS - DONATE A FEW BUCKS)
based on v2.2 configuration
has my own XTRA/AGPS server instead of Qualcomm
re-added two AGPS variables from v1.3 (two beta-testers saw instant results with these re-added)
re-added on USE SUPL variable from v1.3 (two beta-testers saw instant results with these re-added)
variables are now divided into sections and sections have descriptions
Code:
v2.2 update - New Version
introduced the NO SSL version for Google build. Shows faster performance times.
v2.2 (additional builds added)
added a new SUPL version using data from Sony Ericsson
added an alternate release using LG SUPL servers
added an alternate release using Google SUPL servers
updated the ADB PUSH to include new versions
fixed broken download links for the patch
v2.2
removed local AGPS variable
removed local XTRA_SERVER variable
created LG Build with LG SUPL servers (some LG ROMs fail to work with non-LG SUPL servers)
reduced redundancy in NTP and XTRA (unnecessary entries)
added newly located SUPL server to T-Mobile build
v2.1 (encompassing changes between 1.3 to 2.1)
removed two NTP server pools
removed xtra1 server
removed multiple SUPL_HOST entries
aligned SUPL_HOST with SUPLROOTCERT in each package
increased QOS timeout from 89 to 100
removed QOS standalone timeout variable
removed extra AGPS variables
Old Versions:
3.x Trunk:
v3.0 ADB Push Installer
v3.0 Google Build
v3.0 Google Alternate Build
v3.0 Google CWM Build
v3.0 AT&T Build
v3.0 T-Mobile Build
v3.0 LG Build
v3.0 LG Alternate Build
v3.0 Sony Ericsson Build
v3.0 GPS Only Build
v3.0 GPS Only Alternate Build
2.x Trunk:
v2.1 Google Generic Build
v2.1 AT&T Specific Build
v2.1 T-Mobile Specific Build
v2.1 GPS.Conf Only Build
v2.1 GPS.Conf Only Build (alternate)
v2.0 Google Generic Build
v2.0 AT&T Specific Build
v2.0 T-Mobile Specific Build
v2.0 GPS.Conf Only Build
v2.0 GPS.Conf Only Build (alternate)
1.x Trunk:
Worldwide 1.3
Worldwide 1.3n (alternate)
North America 1.2
Worldwide 1.2
Worldwide 1.2n (alternate)
North America 1.1
Worldwide 1.1
Worldwide 1.0 (not recommended)
North America 1.0 (not recommended)
Rules For Posting Questions:
Read the Notes Section first. I will refuse to answer questions that can be answered by some reading. If it is based upon something in the Notes Section, REFER TO THE NOTE when asking.
Answer the following questions: What ROM you are using?, What kernel are you using?, What GPS apps you have installed?, Where is your general location?, Are you using a case?, Has your GPS worked fine before?, Does it work fine with some apps and not others?, What else happened around the time your GPS stopped working? -AND- Have you reviewed the Notes Section?
DO NOT criticize the user of custom third-party NTP pools and xtra.bin data as dangerous. You obviously HAVE NOT read the Notes section OR reviewed the concurrent branch 2.x to discover it offers the standard NTP pool and Qualcomm-based xtra.bin server.
Don't indulge yourself in ignornat posts. Provide information that may be relevant to helping. Simply stating "this stopped working" or "I can't get it to work" helps nothing and only annoys other readers AND those who may be willing to help you just will not do it.
NOTES Section:
This patch will work with virtually all Qualcomm, Android phones and has been reported to work with other chipsets as well. That means hundreds of devices could see a benefit to GPS performance from this patch.
This patch has various objectives to ensure stability and efficacy with GPS. Locally, the patch will replace your /system/etc/gps.conf and your /system/etc/suplrootcert if you have this file. You can compare the difference in what you have to this one to get an idea of all the changes. V3.1, onward, contains section descriptions for variables in use. Most notably, starting with v3.1 the aGPS Patch uses my own central NTP DNS pool and my own central xtra.bin server by default. The xtra.bin does have fallback servers should mine fail. But, that is very, VERY much an unlikely scenario. These two imperatives allow for better stability and speed by providing top-rated NTP servers and prime-routed network access to transmit the xtra.bin to your phone.
I recommend the GOOGLE BUILD of all trunks. However, you can use any build with any phone. You may have good luck with specific builds that do not fit your phone or carrier criteria. If you're curious, test it and see.
This works with ANY ROM unless the ROM has aGPS and/or GPS disabled in the code. This happens with CMx nightlies and some betas! I cannot fix this, neither can you.
Remember, this has to be reflashed when you update or change ROMs.
Short patch history: The 1.x trunk only flashed a modified gps.conf file which relied solely on Qualcomm and NTP.ORG. Starting with 2.x, a gps.conf and a matching SUPLROOTCERT file for SUPL server authentication is included. The 3.x trunk offers the same as v2.x but adds better sourcing for NTP data and for the xtra.bin file; it utilizes my own server to do so.
Why toss out SSL?Whether or not you have a current SUPL certificate is questionable. Some have expired. Some will expire soon. Either way, the servers may provide SSL access without proper certificates depending upon configuration. That aside, I have found that SSL and secure communications over data networks slows the response times. I see no reason to use SSL for location information. If someone has a logger to obtain your location, SSL will not assist in stopping it. The bad app will continue to obtain your information by "stealing" it and you have more problems than a simple SSL-SUPL communications leak.
NO-SSL Builds will not have a SUPLROOTCERT because these builds do not use SSL. The SUPLROOTCERT is a certificate used for authentication of SSL connections. There is no need for this file for the GPS at this point.
IF you have issues with v2.x or v3.x, your ROM might require more variables. Try the old worldwide v1.3 version in this instance.
IF you still are facing issues, it might be that your GPS hardware is very much outdated. Try any "Alternate" build to see if this helps.
CMx ROM users may not experience benefits from this patch. However, we have had good reports from CM users with one negative one. Remember to do all of the steps when flashing and the following notes are important too!
Reports indicate that this patch DOES WORK with the next iteration of Android, Jelly Bean. This patch has worked from Android 2.2 (Froyo) up through Android 4.1 (Jelly Bean). Therefore, it works with all iterations on the market. I will remove support as soon as it is confirmed to NOT work with a new version of Android.
Reports show that certain ROM's including some CM builds require a modification in the build.prop. You need to change "ro.ril.def.agps.mode = 2" or "ro.ril.def.agps.mode = 0" to be "ro.ril.def.agps.mode = 1" in order for aGPS to properly function. Only do this IF YOU ARE HAVING PROBLEMS after attempting the standard patch.
Your phone "learns" about the individual GPS satellites. This is part of the aGPS design. Don't be surprised if the first time you use GPS Status that it takes 20+ seconds to "lock".
I have read a lot that indicates that it is best to let your GPS run using any application for a while to "learn" aGPS information. I let GPS Status run for about 10 minutes (it has an option to disable the screen timeout, which I do) each "first time" to learn. I say each because I test a lot of tweaks and fully reset/delete GPS cached information to start retesting.
Remember, this has to be reflashed when you update or change ROMs. Each ROM will have its own gps.conf, normally not suited to all devices.
I use GPS Status to test my signal strength. It isn't 100% accurate, but it gives a very good sense of how the GPS is performing.
If you're wondering why GPS is slow on certain apps? Or, you show up as on a street when you're 6 meters away from it? Well, those apps process GPS data differently which is out of anyone's control except the app developer. Certain apps will force your location to a street until you pass the app error threshold. Food for thought.
DO NOT USE ANY OTHER GPS FIXING APPS with this patch. If you do, and you still have problems, I cannot help you. A number of these Apps will overwrite what my patch does dynamically.
Variables are described starting in v3.0. Open up gps.conf in a text editor to read about what variable sections are for. It isn't in-depth, but should be enough to help you get a general understanding.
Still having weak GPS reception? Take your case off. Cases have been known to affect signal, though some argue against it. Personally, I get 3 more sat's when I remove my case.
There is a reported variable that can cause some GPS units not to work as well as it should with this patch. This is very odd as it's hit-and-miss and only seems to cause problems on less than 10% of handsets. This doesn't mean it screws up anything! It's possibly an older piece of GPS hardware incompatible with this variable. Have no fear, v1.2 will remove this variable for the worldwide version. This issue is more prone to occur in DHD.
Tried taking the battery out for 30 seconds? Some have reported that their phone required the battery to be removed. First, power off the device. Second, remove the battery for 30 seconds. Third, put it back in and give it a try. I cannot explain this except for possible cache clearing.
Some Inspire 4G and DHD devices have hardware problems. There is a known problem that the spring connectors to the GPS antenna sometimes are out of place or quit touching. http://forum.xda-developers.com/showthread.php?t=1101066 provides a video on self-repair.
An error in flashing this patch means that this method will not work for you. Use one of the other methods for flashing this patch. Don't ask why or for a fix. There are hundreds of variations of recovery systems and update binaries. I do not have the time or desire to support them all. This is why I describe other install methods. Reference error: E:Error in /sdcard/android apps/agps.patch.google.build.nossl.v3.1.zip (Status 0) Installation aborted.
Location is way off? Like, not near you at all? This means your GPS is not actually being used. Try the following to resolve it: Goto Settings -> Locations and disable ALL options. Reboot into recovery. Clear Cache and Dalvik Cache. Reboot normally. Go back to Settings -> Locations and only enable GPS. Reboot once more and try your GPS again. If this didn't work, did you read all of the Notes such as the one about the battery or RIL?
Donations: If you wonder why I asked for donations, it's simple. Users of v3.x are gaining extra, noticeable benefit over v2.x. This comes at a cost to someone. I pay the bills to provide a reliable data setup to transmit the xtra.bin data file and to provide the top NTP SERVERS in one DNS pool. To help keep this going, I just ask for the user to consider a donation. Nothing more, nothing less. Thank you for your consideration.
AGPS Patch Officially Supported Devices:
Acer Iconia
Asus Transformer Prime
Asus Transformer (TF101)
Asus Transformer TF300T
HTC Inspire 4G
HTC Desire HD
HTC Sensation
HTC Incredible S
HTC Salsa
HTC Flyer
HTC Evo 3D
HTC Desire S
HTC Wildfire
HTC Wildfire S
HTC Droid Incredible 2
HTC Thunderbolt
HTC Desire
HTC Desire Z
HTC One X
LG GT-540 OPTIMUS
LG Optimus One
Motorola Triumph
Motorola Droid X2
Samsung Galaxy S II Skyrocket (SGH-I727)
Samsung Galaxy S II (I9100)
Samsung Galaxy S II (SGH-T989)
Samsung Galaxy S Plus I9000
Samsung Galaxy Nexus
Samssung Galaxy S III (AT&T, Rogers, Bell, Telus)
Samsung Galaxy S III I9300, I9305
Samsung Galaxy S 4G
Sony Ericcson XPERIA X8
* I do not officially support all devices that this patch is known to work on at this time. You may private message me your success story for official support considerations.
Thanks Section
While this has gone a long distance since its inception, I want to still send thanks to Angeldeath for permitting me to take his early work and start tweaking it for HTC Inspire 4G users. This inevitably led to what we have here today.
Thank you to all those who joined and participate in the testing community. Without their help, I couldn't get enough data to know how well this works on different devices and in various regions of this planet we call Earth.
Thank you eagleeyetom, husky69, and tamagotono for their work in building an ADB pushing environment for Windows and for Linux respectively.
If you are happy with the patch and find this thread useful, please consider pressing the "Thanks" button on any of my posts on this thread. You may also consider rating this thread with five stars if you're satisfied. You may do so just below "Search This Thread" on the right-side at the top of this post. Donations are appreciated (See last NOTE)
REVIEW THE WHOLE THREAD BEFORE POSTING QUESTIONS.

Notes and Info post
Post consolidation. I'm keeping this post open in case it's needed later.

Works well for me, especially considering it's overcast and I'm inside. Good work!

crypted said:
I will fluff this post out in due time.
Angeldeath made a great series of AGPS patches which essentially updated the gps.conf to speed up the locking process. However, those scripts are based upon regions for USA and no general support for North America.
I have created a patch that will allow for quick GPS locking across North America. I'll keep working on this as necessary to tweak it for our Inspire 4G devices.
HOWTO INSTALL:
1. Download the patch
2. Boot into CWR
3. Mount /system/ partiction
4. Flash the patch
5. Reboot
DOWNLOAD the patch here.
Thanks to Angeldeath for permitting me to take his work and start tweaking it for Inspire users across the continent.
Click to expand...
Click to collapse
AngelDeath already has a generic North America script in the OP of his thread (called North America.zip) which is what I used on a 2900 mile round trip to the Grand Canyon/Las Vegas with great results. Are you saying yours is better? If so, I'll give it a shot.

henrybravo said:
AngelDeath already has a generic North America script in the OP of his thread (called North America.zip)
Click to expand...
Click to collapse
This is old. It doesn't have any of the truly necessary components. In his version terms, you're using version 1.0 which is defunct and was never updated. He is on version 1.2 with specific USA regions only for North America.
What I did was take relevant 1.1 and 1.2 pieces and combined that into a North America generic version instead of having to flash a new region every time I traveled three states away.
Also, I have the intention to keep testing and removing/adding chunks to get it more Inspire 4G friendly. As he said, his was for HD2 but works on other devices.

I just flashed this and it works just as well and locks just as fast as the other GPS fix. Biggest thing I did was to uninstall Google maps and then reinstall in again from the market.
Since then mine has locked each and everytime with in 5-20 seconds.

If you end up traveling, you will notice a difference especially if you're using scripts designed for a specific region. The point of this is to do away with the need for region-specific flashing when traveling. Also, I'm tweaking for our particular device while I go along.

GPS Fix App I have been working on
I have been collaborating with alienmind and AngelDeath and have come up with an app.
This will modify regions on the fly or restore stock settings or do all of the US territories.
@crypted I will pm you the link to the source to do what you like with it!

This won't require any terminal changes for regions as its a quick generic patch. It's good for basic users until angeldeath finishes his app. He and i thought this a good release to do.
Sent from my Inspire 4G using XDA App

crypted said:
This is old. It doesn't have any of the truly necessary components. In his version terms, you're using version 1.0 which is defunct and was never updated. He is on version 1.2 with specific USA regions only for North America.
What I did was take relevant 1.1 and 1.2 pieces and combined that into a North America generic version instead of having to flash a new region every time I traveled three states away.
Also, I have the intention to keep testing and removing/adding chunks to get it more Inspire 4G friendly. As he said, his was for HD2 but works on other devices.
Click to expand...
Click to collapse
Ahh I see. Very good, I will start using your fix! Based on the feedback in this thread, it sounds like you've got a winner. I've updated the GPS fix in my sig to reflect this thread instead of AngelDeath. Keep up the good work kind sir!

Wow this gps.conf file is great. I just locked onto 10 satellites with my case on. Normally I have to take my case off to be able to lock onto 10. Previously, with my case on I used to get 7-8 satellites, sometimes 9 but never 10. Good job crypted.

Glad to hear it's working. If anyone else has success with it, let us know. Shouldn't be many issues with this puppy...
Sent from my Inspire 4G using XDA App

This thing worked wonders for me. I've been having a hard time with my gps lately.. Having a hard time getting a lock and keeping it locked on. This caused me to get an instant lock. Thanks a ton!

Good deal. This is a great starting point for those wanting a one-time (per ROM flashing) fix.
However, flappjaxxx and Angeldeath are working on a GUI on-the-fly app to be released officially at some point down the line. Currently, it is based on region-specific gps.conf's. I think flappjaxxx will be using this gps.conf for a general North America patch in it.
My wife hated it when I said she'd have to change her GPS patch when she landed in Boston... She isn't techie and the thought of it not "just working" was problematic. My patch is a good fix to end that nagging nightmare!!!!

Edited the first two posts. I included an extra gps.conf to flash alongside the AT&T stock file. Also, I added results that have been observed.

This is great, pretty much sending me back to the drawing board with my app!
Great job. Just out of curiosity, this should cover Canada, Hawaii and Alaska as well?
My GPS has never worked better by the way!

It should work in Canada for sure. It should also work in Mexico and several other "North American" countries.
I'm not certain about Hawaii or Alaska and would need someone out there to test it. However, in theory it should work just fine.
In fact, it should work all over and not just in North America. But, the Inspire 4G is an AT&T phone which to me means it would typically be found only in North America unless someone's traveling abroad with one.
Someone with a DesireHD could flash this and try it in Europe or elsewhere and report back.

crypted said:
It should work in Canada for sure. It should also work in Mexico and several other "North American" countries.
I'm not certain about Hawaii or Alaska and would need someone out there to test it. However, in theory it should work just fine.
In fact, it should work all over and not just in North America. But, the Inspire 4G is an AT&T phone which to me means it would typically be found only in North America unless someone's traveling abroad with one.
Someone with a DesireHD could flash this and try it in Europe or elsewhere and report back.
Click to expand...
Click to collapse
Wouldn't you need to tweak the file for European values?
Sent from A Van Down By The River!

Well, I'd want to know where I'm starting at if I were to do that. There isn't much point in tweaking files without knowing what the situation currently is and where it needs to go.
Again, this is really aimed at Inspire users at this point. But, we can do something for others if we get some results thrown this way.

Worked well for me - as good as (maybe a bit better than) AD's southeast conf file. Great fix!

[ROM] Ainol Novo 8 2.3.4 Rooted & G-Apps

[size=+3]
NEW VERSION
Ainol Novo 8 Adv 2.3.4 Rooted UK Rom Version 2.0 Click Me!!
Ainol Novo 8 Adv 2.3.4 Rooted UK Rom Version 2.0 Click Me!!
Ainol Novo 8 Adv 2.3.4 Rooted UK Rom Version 2.0 Click Me!![/size]
​
The Ainol Novo 8 is a great little tablet but has been hampered by some early quality issues and about 4 or 5 firmware revisions that have all been good at something but not everything.
Recently a 2.3.4 beta Rom appeared on the Chinese speaking boards and was a major improvement over the 2.2 releases however as always they were in Chinese as a first language and contained stuff that was no use to us English speaking types. So I decided it was time to apply a bit of magic and make my own Rom. Links at the bottom of the post. This is a direct result of my playing about with the beta firmware then bringing it all together.
Link to my blog post Nebular Nerd @ Blogspot
From the readme.txt
-----------------------------------------------------
Ainol Novo 8 Advanced 2.3.4 PreRooted English Rom
Hacked together by Nebular Nerd (Nov 6th 2011)
(If it's not broke, make it better)
aka thedaybeforetommorow (MP4Nations forums)
aka Oberth (XDA-Developer forums)
WWW: http://nebularnerd.blogspot.com
-----------------------------------------------------
About This Firmware:
--------------------
After much frustration having to de-Chinese every firmware for this amazing little tablet I set about making an English one to save time and to learn a bit more about Android, while doing so I also added in the main Google apps that everyone wants but always has trouble getting to behave. Using the current 2.3.4 beta as a base I removed, replaced and added various things to give us a decent firmware that will make you proud to show off your tablet with the unfortunate brand name. (Hands up all those who have had a schoolboy snicker when telling someone who makes it)
While I take credit for the putting everything together in one easy to use package the real credit should goto all those people I sourced the component parts from. Enjoy the firmware
Changelog:
----------
8/11/2011:
Tidied and formatted readme.txt.
6/11/2011:
Minor update to correct bug in build.prop preventing Chianfire and Tegra games from working.
5/11/2011:
1st Release.
Sources:
--------
http://tinyurl.com/63pnbl6 The base for my rom was this prerooted one. (Translated)
http://tinyurl.com/64xhw3y I used the Browser and Google Music from this one. (Translated)
http://tinyurl.com/29c6jlx The rom I currently use on my HD2 which I lifted most of the Google stuff from.
http://tinyurl.com/6y57c4s The tweaks used for the Market.
Other various sources for stuff about some of the other little tweaks.
Installation:
-------------
Flashing this is a breeze, simply copy the contents of the zip to your SD Card, insert into your Novo 8 and boot into Recovery with Power & Vol+.
Once booted perform the 3 wipes and then install the update and reboot. That's it, no need to install the AC3/DTS license or add Google apps.
If you spot the error about the factory_*blahblahblah*.aml file missing when booting into recovery mode just ignore it. I dumped the automated stuff as it bricked my unit the first time round when flashing the stock beta and I had to do a recovery with the original firmware release. All the automated bit really does is perform the 3 wipes and perform the install so why risk it when it takes only a few seconds to do.
When first booting the homescreen will go black/blank for about a minute. Don't panic this is quite normal it's just everything unpacking and setting up. Set up your wifi, add your Google account and off you go.
Features:
---------
- AC3/DTS Hardware Decoder works.
- Fast and Smooth 160dpi rom with build.prop tweaks to improve battery life and speed things up.
- 3G Modem support is present and has been confirmed working with these dongles . . .
Huawei E160 3G USB Dongle (ompudsman @ MP4Nations)
Huawei E1750 3G USB Dongle with Virgin UK sim. (GFZ @ XDA)
- Full English Rom set to UK region, no hidden Chinese menus to pop out at you. All Chinese only apps removed or replaced with english versions.
- Latest Market 3.3.11 with heavily modified build.prop to show as many apps as possible. This does actually show and install a far wider range of apps than before.
- Uses the free version of LauncherPro because it does seem the best for this Tablet, the Chinese firmwares seemed to have hard coded Chinese in the LauncherProPlus.apk The market will allow you to purchase the Plus Unlocker if you want those features.
- Preloaded with Google Browser, Gmail, Maps, Streetview, YouTube, Google Music, Latitude, Google Search, Calendar and Car Home.
- Google accounts will sync Contacts, Mail and Calendars correctly.
- YouTube plays HQ videos just fine without stutter or lag. (Assuming you have a good wifi signal)
- The stock video player plays most MPG, MP4, MKV files with AAC, MP3, AC3 audio. Plays 1080p quite happily as well if the storage device can keep up.
If you need wider format support but still with hardware decoding where possible get MX Video Player and the ARMv7 Codecs from the market.
- Most of the Games and Apps I have tried while testing work fine. Get Chainfire3D and buy the Pro key to enjoy some of the nice Tegra Games. Check my blog for compatibility of Tegra games.
- Wifi seems better under the new firmware.
Bugs: (Most of these have been documented as an issue with the base firmware)
-----
- Tablet likes to wake itself up now and then for no real reason. (Possible data connections causing it to wake)
- Sometimes the Power button does not work so you can't turn off the screen or power off. Install Quick Reboot off the market or hit the reset button.
- If the Screen is off and the Power button is not behaving another key will turn it on.
- Sometimes the Power Off dialog appears for no reason. Oddly not when in full screen games so far as I've noticed.
- Your Novo may disappear off the Market site for a while or completely. Mine went and then came back about a day later,
this is down to the modified build.prop. You can still download apps directly through the Market app on the Novo regardless.
- Some of the best apps are still not available in the market, Dolphin Browser HD, Facebook and Friendcaster to name a few. This is down to Google Market and not much seems to beat this last hurdle.
- Possible others (Let me know by posting on my blog or threads)
Disclaimer:
-----------
As with any custom firmware there is a risk of things going wrong so if it bricks your unit try a recovery image from Ainol and start again, if you are of a nervous disposition or the type of person who sues for a hobby please do not attempt to install this. The rom works fine on my unit and others have tried without issue, however mileage does seem to vary with this tablet.
----------------------------------------------------------------
{
"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"
}
(screenshot app not included)
Links to the firmware (if you want to mirror please let me know so I can add links here)
Novo 8 2.3.4a Firmware UK Edition (nebularnerd.co.uk, fixed March 2021)

Thank you!
Hi Oberth,
Thank you so very much for the hard work and effort to put something together for this fantastic tablet! We have been hoping to see some english rom's being put together for some time but the fact that this is Android 2.3.4 with all the tweaks and best bits of previous rom's is excellent!!
Will be flashing your rom shortly and report back...
update: flashed and so far so good!
- Huawei E1750 3G dongle tested with Virgin UK Sim and all working.
Also will be uploading you rom to our website which may be found in the download section of the Ainol Novo 8 webpage.
(unable to post a link yet as need more posts)
Kind Regards
gadgetfreakz.co.uk

Thanks for the feedback
I actually bought my tablet from you guys through your ebay shop under the user id thedaybeforetomorrow was most pleased by the service.
Thanks for the offer to mirror and I hope the rom performs as it should, as not everyone can/will download from rapidshare I would like to add the links for your Novo 8 page to my first post here, my mp4nation thread and my blog.
Over at MP4 I have had some feedback regarding the market, while fully functional some have complained of the speed (mainly to do with the markets new design rather than tablet performance) so I am considering for the next release maybe offering both the older 2.xx style market and new 3.x market as separate firmware downloads so people can choose. Both the latest version I have used and the older one seem to see the same amount of apps visible so it's mainly a personal preference.
Just seen your test with the 3G Dongle, going to update here there and everywhere

Oberth said:
I actually bought my tablet from you guys through your ebay shop under the user id thedaybeforetomorrow was most pleased by the service.
Thanks for the offer to mirror and I hope the rom performs as it should, as not everyone can/will download from rapidshare I would like to add the links for your Novo 8 page to my first post here, my mp4nation thread and my blog.
Over at MP4 I have had some feedback regarding the market, while fully functional some have complained of the speed (mainly to do with the markets new design rather than tablet performance) so I am considering for the next release maybe offering both the older 2.xx style market and new 3.x market as separate firmware downloads so people can choose. Both the latest version I have used and the older one seem to see the same amount of apps visible so it's mainly a personal preference.
Just seen your test with the 3G Dongle, going to update here there and everywhere
Click to expand...
Click to collapse
wow, small world!
thank you for your custom and delighted to hear you are pleased with the service
will be testing further over the next few days, for some reason we did notice that the initial firmware form Ainol played 1080p files flawlessly then slowly playback became worse over following updates although other features/fixes had been implemented.
all mentioned above seem to be as you stated regarding the initial power up and blank screen. can't say we experienced the power button problem yet, works as it should.
the new market is indeed sluggish as with other tablets, a quick search for skype didn't show the main application as most likely with some others that you have mentioned. apart from the sluggish launch, the new market design is not so bad, personally prefer it now being used to it.
Ainol did advise an official firmware was due soon, maybe a mix of that and the firmware's you have worked with will give us an even greater improvement.
loving the honeycomb boot animation!
keep up the great work, will have the firmware link etc added shortly.

The playback issues in the later firmwares linked to the AC3/DTS license not being installed or disabled entirely so playback did get worse.
Can I ask you to re-download the firmware in the first post. I tidied up the readme.txt for readability. nothing else is changed.

Oberth said:
The playback issues in the later firmwares linked to the AC3/DTS license not being installed or disabled entirely so playback did get worse.
Can I ask you to re-download the firmware in the first post. I tidied up the readme.txt for readability. nothing else is changed.
Click to expand...
Click to collapse
sure no problem at all, we have uploaded the firmware to our novo 8 pages download section and provided link to the firmware and to this page at xda.
will download new file and replace the one we have on our server.
thanks again

Thanks for that I have added your page to the links section where ever this is posted and edited my blog to mention where I bought it from.
Can I ask if you could change the name from Oberth to Nebular Nerd on your page, just matches up with the blog then. My user name from here was from years back and I wish you could change it. Part of why I edited the readme was to aka the names

Oberth said:
Thanks for that I have added your page to the links section where ever this is posted and edited my blog to mention where I bought it from.
Can I ask if you could change the name from Oberth to Nebular Nerd on your page, just matches up with the blog then. My user name from here was from years back and I wish you could change it. Part of why I edited the readme was to aka the names
Click to expand...
Click to collapse
will do
may be in touch soon regarding some ideas we have that may be of interest.
thanks again

Man, this is great!
Thank´s a lot!
Now I´m happy with my tablet.

Hello from Spain
First of all, congratulations on your work with the tablet Ainola.
I wanted to ask if you know when it will be available in Spanish.
Thanks for everything.

kinterinho said:
Hello from Spain
First of all, congratulations on your work with the tablet Ainola.
I wanted to ask if you know when it will be available in Spanish.
Thanks for everything.
Click to expand...
Click to collapse
I just checked and Spanish language is not included, maybe something for the next release
Languages included are: English (Australia / Canada / New Zealand / Singapore / UK / United States) & Chinese.

Thanks, I'll try to see how it goes anyway.
But if you can include it in the next version, would be welcome here in Spain.

kinterinho said:
Thanks, I'll try to see how it goes anyway.
But if you can include it in the next version, would be welcome here in Spain.
Click to expand...
Click to collapse
That would be down to Oberth aka Nebula Nerd but don't believe it would be that hard to do, i'm sure he will let us know

Additional Languages
Hi kinterinho,
I shall have a look into adding additional languages into the firmware and see what that requires. This beta was released with only Chinese and English language files built in but I may be able to borrow some from another rom.
The only thing that might present a problem is if LauncherPro refuses to change all it's options to Spanish in the same way the default Chinese one would not become fully English when you changed the language. I shall have to experiment and see

Cheers for the update, having a few issues.
Iplayer app now apears to suck goats since using this ??
any ideas ?

rezza.dh said:
Cheers for the update, having a few issues.
Iplayer app now apears to suck goats since using this ??
any ideas ?
Click to expand...
Click to collapse
Hi, I think you will find the BBC iPlayer app has always had issues.
Playback should be fine via the browser, this firmware plays iPlayer via stock browser although previous firmware required dolphin browser hd.

Oberth said:
Hi kinterinho,
I shall have a look into adding additional languages into the firmware and see what that requires. This beta was released with only Chinese and English language files built in but I may be able to borrow some from another rom.
The only thing that might present a problem is if LauncherPro refuses to change all it's options to Spanish in the same way the default Chinese one would not become fully English when you changed the language. I shall have to experiment and see
Click to expand...
Click to collapse
I appreciate you try it. In Spain would do well to include also the Spanish language.
I read on the post to see if there are any changes.

iPlayer is indeed pretty poor.
Yep confirming GFZ's post, it will play with the stock browser set to mobile but quality is pretty poor. I remember it running better on one the original stock roms. It could be one of a few things.
- Bug in the firmware with flash, although Youtube works through the various browsers ok. You can't use the Youtube app for comparison as it's not flash driven.
- Could be a VM Heap issue with it taking up to much space (need to play with that and see)
- Could be the higher dpi on top of the higher res causing the poorly coded app lots of effort in the upscale, dropping to the original 192dpi might cure it at the expense of fuzzy text and icons, again I need to test, not sure if dpi switchers play nice with this rom so you could at least hop between them for different tasks.
- I might try embedding it in the rom as well, The Youtube app hated being added to the tablet post flashing and performance was poor but ran just fine after being flashed in.
The problem with iPlayer for Android was that it was released only after a lot of complaints from the community at large about them only supporting the iThings. BBC were not really wanting to make it but cobbled something together just to shut people up.
Quick edit: Hit the settings button and drop the quality to low in iPlayer seems to play the same as in Browser. Not ideal I know, looking at it more closely it seems to be a buffering issue as you get a few smooth seconds and then it all grinds to a halt.

Multilanguage support
Hi kinterinho
I have been looking into and reading up on how Android handles multiple languages and it looks like it not something easy to do as it's not a case of adding files but adding stuff into the files and given the differences between roms especially 2.2 and 2.3 ones I imagine a cut'n'paste job wont do it.
However I have the beginnings of an idea, it needs some work combined with a recent opportunity that has come my way so I can't promise anything but watch this space.

Thanks you!

[Tool] Basic Network Compatibility Tester - d2vzw/d2spr/d2att

Recently I made a longwinded rant over in dev only about the importance of rom props being set to carriers correctly. This thread is to split off the actual tool itself to check from the dev only questions.
Attached to this post is an Aroma Flashable to check basic network compatibility. It also will list out hardware information such as CPU Models and if NVBackups have been ran. Not everything for network compatibility can be checked such as framework, but if you follow these steps users should have a pretty good way to check network friendliness. Devs please make sure we start paying attention to this. I will explain the basics of each check here, but if you want more geeky information on why these are important read my rant in the devs only forum here - http://forum.xda-developers.com/showthread.php?t=2231256 .Devs only - feel free to hit me up there with any porting questions, or expand on this script to make it more robust.
To test a ROM
Flash a rom you want to check
Before booting into rom, flash attached network check
Verify Settings, reboot when done
When first boot in rom, go to settings -> about phone and verify phone number, verify MMS works.
If you do all these steps, you have a fairly good way to see compatibility. Use common sense as well.
Currently Working Network Checks
ATT/SPR/VZW
*note* this is the first version with "intelligence", so some checks may not be as smart as I think they are. I believe we have coded it correctly for every scenario and have tested many stock roms, but this should just be used as a *basic* check. It is not all encompassing because we cannot check things like framework, and as such should be used as a general reference.
Explanation of Checks
**All of these screenshots are using a Verizon Device as a base. Obviously if you are using Sprint or ATT checks will look slightly different**
Page 1 - Hardware Versions
{
"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"
}
Hardware Versions-
androidboot.nvdata_backup - 1 if "reboot nvbackup" has been ran, 0 otherwise
androidboot.bootloader - Bootloader version flashed
samsung.hardware - Hardware version ID
CPU Revision - CPU model revision
Hardware - Vendor specific Hardware type of device
Unique CPU Serial - CPU serial #. Unique to device, would not be posting around
Recovery Info-
Checks what carrier recovery props have set
Page 2 - Software Prop Checks
CSC Version Info-
build.PDA - read from build.prop. PDA/CSCs/Baseband should all be matching
CSC Software Ver - read from /system/CSCVersion.txt
These are manual checks because querying baseband isnt possible in recovery
Sales Code Props-
Ril Sales Code - checks build.prop for ril.sales_code and matches to hardware
CSC Sales Prop - checks build.prop for ro.csc.sales_code and matches to hardware
This will display a --CHECK in bold if a value is incorrect. Blank values here are OK if below Sales Code CSCs are set correctly. If a value is set here it will overwrite Sales Code CSC.
Sales Code CSCs-
Device Sales Code - reads from /system/csc/sales_code.dat. Checks to hardware
Customer XML Sales Code - reads from /system/csc/customer.xml. Checks to hardware
This will display an error message in bold at the bottom of the check if one or more is off
Rom Prop Info-
product name - checks build.prop for ro.product.name and matches to hardware
product model - checks build.prop for ro.product.model
version - checks build.prop for ro.build.version.incremental. Usually matches build.PDA
characteristics - checks build.prop for ro.build.characteristics.
Google Keys-
build.description - checks build.prop for ro.build.description
build.fingerprint - checks build.prop for ro.build.fingerprint
clientid.yt - checks build.prop for ro.com.google.clientidbase.yt
clientid.ms - checks build.prop for ro.com.google.clientidbase.ms
clientid.am - checks build.prop for ro.com.google.clientidbase.am
Page 3 - Apps Check
This screen checks for the existence of ATT / Sprint / Verizon apps in a rom. A success should be only say Verizon apps on a Verizon device. Anything else is considered a failure.
Changelog
V1.4 -
Beefed up a few checks
Added help/about screen to beginning of aroma
Added dev only option - Lets devs fake a hardware ID to test how different ports will check out
Added more hardware type info. Totally useless to porting but cool stuff to know
Added logging option to end of aroma, ability to save all output to /sdcard/romcheck.txt. File has unix linebreaks so use notepad++ if on windows.
V1.3 -
Initial release in development section.
Remember this is the first version of this test script, so every case may not have been thought of. It is also only a basic scanner tool and should not be the only test you do, use common sense as well. Devs feel free to work off of this, give codechanges, report in on bugs, whatever.

TL;DNR version for non-devs: Go back and this time don’t TL;DNR the post above
Run this tool AFTER you’ve flashed any US S3 ROM and read through each result carefully. For example, if you are, say, an AT&T user, EVERYTHING should come back with the appropriate d2att info (i.e. build.prop stuff should all say only att, CSCs should all say att, there should ONLY be att apps on the last page, etc). If everything did not come back 100% att, you failed the test and the ROM you just flashed is installing incorrect files to your phone.
We need everyone – devs and users alike – to be diligent in the use of this tool. As we explained in this thread, if multicarrier isn’t being done properly and users are running ATT or SPR code on the VZW network (or any other combination) then the carriers may start getting really upset with the XDA community – which is something we really need to avoid.

Tool has been updated to v1.4 with some requested features (dumping to text file, ability to test different hw, more hardware related stats, etc). Also have updated the dev only section thread with more info on why these checks matter and some cleanup.
Enjoy

TrevE said:
Recently I made a longwinded rant over in dev only about the importance of rom props being set to carriers correctly. This thread is to split off the actual tool itself to check from the dev only questions.
Attached to this post is an Aroma Flashable to check basic network compatibility. It also will list out hardware information such as CPU Models and if NVBackups have been ran. Not everything for network compatibility can be checked such as framework, but if you follow these steps users should have a pretty good way to check network friendliness. Devs please make sure we start paying attention to this. I will explain the basics of each check here, but if you want more geeky information on why these are important read my rant in the devs only forum here - http://forum.xda-developers.com/showthread.php?t=2231256 .Devs only - feel free to hit me up there with any porting questions, or expand on this script to make it more robust.
To test a ROM
Flash a rom you want to check
Before booting into rom, flash attached network check
Verify Settings, reboot when done
When first boot in rom, go to settings -> about phone and verify phone number, verify MMS works.
If you do all these steps, you have a fairly good way to see compatibility. Use common sense as well.
Currently Working Network Checks
ATT/SPR/VZW
*note* this is the first version with "intelligence", so some checks may not be as smart as I think they are. I believe we have coded it correctly for every scenario and have tested many stock roms, but this should just be used as a *basic* check. It is not all encompassing because we cannot check things like framework, and as such should be used as a general reference.
Explanation of Checks
**All of these screenshots are using a Verizon Device as a base. Obviously if you are using Sprint or ATT checks will look slightly different**
Page 1 - Hardware Versions
Hardware Versions-
androidboot.nvdata_backup - 1 if "reboot nvbackup" has been ran, 0 otherwise
androidboot.bootloader - Bootloader version flashed
samsung.hardware - Hardware version ID
CPU Revision - CPU model revision
Hardware - Vendor specific Hardware type of device
Unique CPU Serial - CPU serial #. Unique to device, would not be posting around
Recovery Info-
Checks what carrier recovery props have set
Page 2 - Software Prop Checks
CSC Version Info-
build.PDA - read from build.prop. PDA/CSCs/Baseband should all be matching
CSC Software Ver - read from /system/CSCVersion.txt
These are manual checks because querying baseband isnt possible in recovery
Sales Code Props-
Ril Sales Code - checks build.prop for ril.sales_code and matches to hardware
CSC Sales Prop - checks build.prop for ro.csc.sales_code and matches to hardware
This will display a --CHECK in bold if a value is incorrect. Blank values here are OK if below Sales Code CSCs are set correctly. If a value is set here it will overwrite Sales Code CSC.
Sales Code CSCs-
Device Sales Code - reads from /system/csc/sales_code.dat. Checks to hardware
Customer XML Sales Code - reads from /system/csc/customer.xml. Checks to hardware
This will display an error message in bold at the bottom of the check if one or more is off
Rom Prop Info-
product name - checks build.prop for ro.product.name and matches to hardware
product model - checks build.prop for ro.product.model
version - checks build.prop for ro.build.version.incremental. Usually matches build.PDA
characteristics - checks build.prop for ro.build.characteristics.
Google Keys-
build.description - checks build.prop for ro.build.description
build.fingerprint - checks build.prop for ro.build.fingerprint
clientid.yt - checks build.prop for ro.com.google.clientidbase.yt
clientid.ms - checks build.prop for ro.com.google.clientidbase.ms
clientid.am - checks build.prop for ro.com.google.clientidbase.am
Page 3 - Apps Check
This screen checks for the existence of ATT / Sprint / Verizon apps in a rom. A success should be only say Verizon apps on a Verizon device. Anything else is considered a failure.
Changelog
V1.4 -
Beefed up a few checks
Added help/about screen to beginning of aroma
Added dev only option - Lets devs fake a hardware ID to test how different ports will check out
Added more hardware type info. Totally useless to porting but cool stuff to know
Added logging option to end of aroma, ability to save all output to /sdcard/romcheck.txt. File has unix linebreaks so use notepad++ if on windows.
V1.3 -
Initial release in development section.
Remember this is the first version of this test script, so every case may not have been thought of. It is also only a basic scanner tool and should not be the only test you do, use common sense as well. Devs feel free to work off of this, give codechanges, report in on bugs, whatever.
Click to expand...
Click to collapse
TrevE,
I see you still doing what you do best analyzing bro. I am glad people like you are still around deving with the dream team of developers on board with you. thanks will be note 2 AT&T chomping this up across the platform...

So I have a question then. I know this is the Verizon forum, but I'm going to talk about att, because it's in the description. I've also thought about going to att when/if Verizon decides to nix unlimited data. I talked to someone at att and they said I can get ANY CARRIER UNLOCKED GSM phone, international included, and use it on att. So how does that work with this tool, since it's only on att by sim?

riassan said:
TrevE,
I see you still doing what you do best analyzing bro. I am glad people like you are still around deving with the dream team of developers on board with you. thanks will be note 2 AT&T chomping this up across the platform...
Click to expand...
Click to collapse
Good to see ya around here bud been awhile note2 should be cool with some minor changes, hell I can run it on my e3d and even though it cuts screens off the basics work wherever.
countryfolk07 said:
So I have a question then. I know this is the Verizon forum, but I'm going to talk about att, because it's in the description. I've also thought about going to att when/if Verizon decides to nix unlimited data. I talked to someone at att and they said I can get ANY CARRIER UNLOCKED GSM phone, international included, and use it on att. So how does that work with this tool, since it's only on att by sim?
Click to expand...
Click to collapse
Good question - As of now were still creating a database of all the hardware versions of the device. Till now it was a bit hard for the average user to get this data.
During our trials though Esc had some testers dump info- from what weve seen so far Tmobile devices are reporting in with ATT Hardware. This is why I only have these 3 carriers supported as of now. I'm not 100% positive if /proc/cpuinfo is controlled by kernel in some way, but the only strings I've seen so far are
SAMSUNG M2_ATT
SAMSUNG M2_SPR
SAMSUNG M2_VZW
These may actually be the only 3 main board versions of the US hardware, meaning any device that reports as a M2_ATT would be able to be unlocked for use between ATT/TMO or any other network that runs a device with that hardware ID. Not 100% sure, but if we get some users posting what their CPU Hardware reads out as from other networks you can get a good idea of what type of devices there are out there working on what network.
*Edit* i guess what im trying to say, even if these are the only 3 revisions and you got a Tmobile device, it would detect it as ATT still and show you the right files to change to get a compatible rom with ATT. If its true, adding support to the apps autodetection for other carriers like tmobile is going to be a bit harder.
International GS3 is totally different hardware, exynos vs msm. The international roms usually have many carrier support built into them and do proper switching on sales code. Aslong as the ROM has ATT support in the CSC folders it means the software was written to have support and switch properly to the ATT network if your sales code is set correctly, but im not positive they do.
*Edit2* Just looked at XXELLA international gs3 firmware, it has support for these carriers. It very well may still work with another carriers sales code, but it wouldnt be recommended
Code:
ABS
AFG
AFR
ALB
ARB
ATL
BGL
BRI
BTC
BTU
CEL
CHU
CMF
CNX
COA
CPW
CYO
CYV
DBT
ECT
EGY
EIR
ERO
ETL
ETR
EUR
FWD
GLB
H3G
ILO
INS
INU
ITV
JED
KEN
KOR
KSA
LUX
LYS
MAT
MED
MET
MID
MIR
MM1
MMC
MOB
MRT
MSR
MTL
MWD
NEE
NPL
OMN
OPS
ORL
ORS
ORX
PAK
PCL
PHE
PRO
PTR
QAT
SEB
SEE
SFR
SIM
SIN
SLK
SMA
STH
SWC
TCL
TDR
TGY
THL
THR
TMC
TML
TMT
TOP
TRA
TSR
TTT
TUN
TUR
TWO
VD2
VDC
VDF
VDH
VDI
VDP
VDR
VDS
VGR
VIM
VIP
VNO
VOD
VOP
VVT
WAN
XEF
XEH
XEO
XEV
XEZ
XFA
XFC
XFE
XFM
XFV
XME
XSE
XSG
XSK
XSP
XTC
XTE
XXV
ZTO

Software Development [Dev] New "NavRadio+" ported to UIS7862 and sc9853i FYT devices.

Hi all,
I finally ported my NavRadio+ app to FYT based devices with CPU UIS7862, sc9853i and sc9863a!!
It surely don't work on Sofia and older FYT devices.
I own an Isudar V72 unit with CPU UIS7862 with MCU NOR FYT=1 but it's been confirmed to work on other FYT types too (31, 51 etc..)
A FREE VERSION FOR XDA USERS IS AVAILABLE TO ACCOMPLISH THE XDA RULES AND TO LET USERS TEST THE COMPATIBILITY BEFORE BUYING IT.
GET IT HERE:
V2.80 DROPBOX LINK
or
V2.80 GDRIVE LINK
IT DIFFER FROM PAYED VERSION JUST IN TERMS OF USER CUSTOMIZATIONS OPTIONS AND NO LOGOS SUPPORT.
If you are sure that your unit is compatible with the app you can get it on the Google PlayStore, here:
https://play.google.com/store/apps/details?id=com.navimods.radio
or on the Huawei Appgallery at this link:
https://appgallery.huawei.com/app/C107643913
Here you can see a sample video of my working progresses:
Sample Video
Here a demonstration video of the automatic assignment of Logos, station name and alternative frequencies:
Demo
It's widely customizable in the graphics and layouts:
- Wallpapers: Presets (about 30), system wallpaper, solid color, from personal images
- Color themes (20 predefined or personal adjustments)
- Night mode on / off, timed or automatic with car lights (MTC only)
- Resizable text elements and Font choice
- 3 view modes:
Vertical List (Left/Right and5,6 or 6 buttons)
Horizontal Grid (1x5, 2x3, 2x4, 2x5, 3x3, 3x4, 3x5)
Fullscreen (double tap or timed)
- Selectable inactivity timer for fullscreen activation
- Toggable StatusBar in fullscreen mode
- Toggable Clock and GPS speed in fullscreen
- Toggable Frequency slider
- Automatic and manual assignement of Logo images to the stored radio stations based on RDS id and station name scraping.
- Logos can be downloaded from internet DIRECTLY IN THE APP or sideloaded.
- Station lists can be sorted by name or frequency and saved/restored in a Json format
- Improved RDS AF function with automatic storing and merging of alternative frequencies found
- Notifications Toasts
- Selectable Radio Region
- Station editable elements : Position, Frequency, Name, Logo, Favorites
- 2 Homepage Widgets, horizontal and vertical design
- Floating widget
- Autostart on boot option
- Support 800x480, 1024x600, 1280x720 and 1920x1080 display resolutions
- Resizable Texts elements
- App full settings backup/restore function
List of available Logos by nationality, in Bold the ones with automatic Logos assignement functionality (by RDS id):
EUROPE: Albania, Andorra, Austria, Australia, Belgium, Bulgaria, Bosnia and Herzegovina, Belarus, Cyprus,Croatia, Czech Republic, Denmark, Estonia, Faroe Islands, Finland, France, Germany, Gibraltar, Greece, Hungary, Ireland, Iceland, Italy, Lithuania, Latvia, Liechtenstein, Luxembourg, Macedonia, Malta, Monaco, Moldova, Montenegro, Netherlands, Norway, Poland, Portugal, Romania, Russia, Serbia, Slovakia, Slovenia, Sweden, Switzerland, South Korea, Spain, Turkey, Taiwan, Ukraine, United Kingdom
SOUTH AMERICA: Argentina, Brazil, Chile, Colombia, Mexico, Perù
USA: Alabama, Alaska, Arizona, Arkansas, California, Canada, Colorado, Connecticut, Delaware, Florida, Georgia, Hawaii, Idaho, Illinois, Indiana, Iowa, Kansas, Kentucky, Louisiana, Maine, Maryland, Massachussets, Michigan, Minnesota, Mississippi, Missouri, Montana, Nebraska, Nevada, New Hampshire, New Jersey, New Mexico, New York, North Carolina, North Dakota, Ohio, Oklahoma, Oregon, Pennsylvania, Puerto Rico, Rhode Island, South Carolina, South Dakota, Tennessee, Texas, Utah, Vermont, Virginia, Virgin Island, Washington, Washington DC, West Virginia, Winsconsin, Wyoming
CHINA, JAPAN, MALAYSIA, PHILIPPINE
MOROCCO, TUNISIA
AUSTRALIA, NEW ZAELAND
Some pictures:
{
"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"
}

SOME TIPS AND GUIDES
- REMOVE ORIGINAL RADIO APP -​There are some issues due to original radio app coexistance. To avoid these issues the best option is to remove the original radio app from the system using the FYT_Radio_REMOVER/RESTORER tool availabe here:
DROPBOX: FYT RADIO REMOVER/RESTORER
or here:
GDRIVE: FYT RADIO REMOVER/RESTORER​
Extract the zip file on the root of a FAT32 USB disk so you have:
a folder "BACKUP_RADIO_APK"
a folder "lsec_updatesh"
a file "lsec6315update"
a file "lsec6316update"
a file "lsec6521update"
With unit powered up and android running, insert the USB and when prompted press "START".
This will reboot the unit and run some shell commands to rename the original radio app from "******_com.syu.radio.apk" into "*******_com.syu.radio.bak" so it will not be found by android.
You will see some linux commands scrolling and at the end you'll see a green text "update success!Pls remove device". Do it and the unit will reboot to android with radio disabled.
The script will also make copy of the original radio app on the USB in the folder "BACKUP_RADIO_APK" in case you need it in the future.
TO RESTORE THE ORIGINAL APP​Simply insert again the USB with same files in it and let the process run again.
Essentially everytime the USB stick is inserted, it remove the original app renaming it with .bak extension or if the .bak file exist it restore it back with .apk extension.
You can use it as many times you want.
-----------------------------------------------------------------------​
TOGGLE SCREEN NORMAL/FULL:
- Double Click on the station information toggle fullscreen on/off.
NORMAL SCREEN:
- Long press on the station information popup the "ADD Station" dialog window if the station is not in your station list. If it's already in your list, it will focus the relative station button.
- Long press on a station button bring up the "EDIT Station" dialog window
- Single press on screen arrows <> does a small frequency step fwd/back
- Long Press on screen arrows does a quick search fwd/back
FULLSCREEN MODE:
- A Single press of the arrows <> switch to next/previous station
-A Long press on station information(center of the screen) bring up the "EDIT Station" dialog window.
- In interface settings you can remove the big frequency in background if a logo is available.
- In settings you can hide status bar, activate the clock and a speed gauge
STEERING WHEELS CONTROLS:
- The steering wheels commands act exactly in the same way as the fullscreen arrows, they just need to be setup in the correct way in carsettings application.
FAVORITE LIST:
- The FAV list is the result of merging FM and AM favorites, so you can have both frequencies in the same list.
- FAV stations can be edited within the fav list but cannot be added. You need to be on fm or am list to add a station and set it to favs.
- Deleting the FAV list will just remove the fav flag from the fm/am stations but will not delete them.
- Deleting AM/FM list it will delete the FAV list too.
LOGOS:
- you can use your own station logos, you just need to know where you have them stored and browse for them when editing a station.
- To get the stations Logos from the app you have to set the nationality of the logos in the interface menu, download and extract them.
Once they are extracted you have to edit each saved station to assign the logo image to it.
- The automatic assignment of the Logos is based on the RDS id of the radio stations (pi code) and the search of the logo by RDS name.
The first method (by id) is faster and more precise but it needs that the name of the logo contain the picode of the station and for this purpose i renamed them for some of the available countries. Of course i cannot make them all and the functionality of this method depend of the availability of correctly named logo images for your country.
The second method (by name) is less accurate and it work comparing the RDS name with all available logos. If the rsult of the comparison is 100% correct the logo is autoamatically assigned. If the result are more then one logo, a dialog window popup asking you to choose it.
For USA and Canada the assignment of the logo is is done by searching the frequency of the station in the logo file name.
AF (Alternative Frequencies) handling: (Doubleclick to switch between stored AF)
AF service allows the radio tuner to tune in to an alternative frequency when the signal becomes too weak. The minimum level signal can be set in factory settings (Auto Search Stop) and has been found
that around 30 db is the best choice.
To improve even more this service I added an automatic storing of the alternative frequencies so that every time a new frequency is received, it's added in a list.
After an autoscan some radio stations can be found on different frequencies, NavRadio+ have an option (in Settings/radio) to automatically merge the frequencies in just one button populating the AF list
The frequencies available in this list can be selected using the station editor or switched one by one DOUBLECLICKING on the station button.
NOTES:
I'm the only developer of the app and I work on it every single day for some hours a day.
I try my best to develope the app at best of my possibilities and I wish at evey release that it is bug and crash free.
This is very hard to achieve, even if I have some very good friends that help me testing it.
I'm really thankful to them for their help and support.
Thank everybody who beleive in my work and thanks for understanding.
EDIT: Updated FYTRadio remover/restorer with new lsec6315update file

Great news. Thanks for your work! Will check this out and drop my feedback

On FYT 31 works well, but steering wheel control doesn't work.

stediste said:
On FYT 31 works well, but steering wheel control doesn't work.
Click to expand...
Click to collapse
SWC will work on next release.
I already found the fix for it.

I have a question for all FYT users:
While using a navigation app like maps, does the sound from the radio mix with Navigation announcements?
It mix sound when using the audio player but it doesn't do that on my unit with the original radio app.
Is this normal for fyt units??

I just installed this and tried it a bit and it works on my Atoto S8!!! This is so much better than the default radio station. Thank you so much!
It doesn't seem to have that function of combining all frequencies of the same station into one button though, but I guess that's because this is the free version? That's the big problem with the FYT-based radio apps. The way they do AF is terrible.
The steering wheel controls, and widget next and back buttons of the Agama Car Launcher aren't working but this is awesome! Can't wait for the update to the full version and I'll purchase it when it's released. Amazing!
I need to know:
- if the radio controls work, like autoscan, seek stations, etc..
This works. Autscan and seek stations. Is there anything else you wish me to test?
- if RDS informations are displayed
Yes!!
- if sound output work (you can hear sound)
Definitely. It was working great.
- if audio focus and mixing work correctly
I still didn't try this but I'll turn on navigation and drive to the supermarket in the next couple of hours so I'll try it.

Gaugamela said:
I just installed this and tried it a bit and it works on my Atoto S8!!! This is so much better than the default radio station. Thank you so much!
It doesn't seem to have that function of combining all frequencies of the same station into one button though, but I guess that's because this is the free version? That's the big problem with the FYT-based radio apps. The way they do AF is terrible.
The steering wheel controls, and widget next and back buttons of the Agama Car Launcher aren't working but this is awesome! Can't wait for the update to the full version and I'll purchase it when it's released. Amazing!
I need to know:
- if the radio controls work, like autoscan, seek stations, etc..
This works. Autscan and seek stations. Is there anything else you wish me to test?
- if RDS informations are displayed
Yes!!
- if sound output work (you can hear sound)
Definitely. It was working great.
- if audio focus and mixing work correctly
I still didn't try this but I'll turn on navigation and drive to the supermarket in the next couple of hours so I'll try it.
Click to expand...
Click to collapse
The arrows of the Agama widget has never worked on other models either.
Steering wheels controls should be working now on new version 2.16 (i updated the link in first post) download it again please.
Merge of frequencies can be done only if the unit receive the station id from RDS. right now only MTC units can do it, FYT ones need some tricks and headache:I'll see what i can do...
AF on FYT is definetively wrong handled and i don't know if i can fix it...

KoTiX2 said:
I have a question for all FYT users:
While using a navigation app like maps, does the sound from the radio mix with Navigation announcements?
It mix sound when using the audio player but it doesn't do that on my unit with the original radio app.
Is this normal for fyt units??
Click to expand...
Click to collapse
So, the original radio app in my Atoto S8 decreases sound when indications are given in Waze. Navradio works the same. The web radio app I use decreases the sound more drastically than Navradio and the stock radio app.
2.16 managed to make the steering wheel controls work! Very impressive.
I'll wait and see what you can do about radio merging and AF. What you've done is already very impressive. Thank you.
Any other test you need me to do?

Gaugamela said:
So, the original radio app in my Atoto S8 decreases sound when indications are given in Waze. Navradio works the same. The web radio app I use decreases the sound more drastically than Navradio and the stock radio app.
2.16 managed to make the steering wheel controls work! Very impressive.
I'll wait and see what you can do about radio merging and AF. What you've done is already very impressive. Thank you.
Any other test you need me to do?
Click to expand...
Click to collapse
What about bluetooth audio switching between calls and radio?

*delete*

KoTiX2 said:
What about bluetooth audio switching between calls and radio?
Click to expand...
Click to collapse
Test:
1 - Opened Navradio Free and was playing a radio station,
2 - Opened Bluetooth One (the phone app) and called someone,
Result: as expected, same behaviour as every other app. Sound from the call took over and nothing was playing on the background. When the call ended, Navradio resumed trouble-free.
A couple issues that I detected:
Issue 1:
1 - Was playing Navradio when I switched off the car.
2 - When I turned on the car, Navradio did not resume.
3 - Instead, the default Radio app started by itself on the radio station last played by Navradio.
4 - I had to start Navradio by myself.
5 - Expected to have Navradio open instead of the Radio app. Or at least to have Navradio to restart as well. Toggled option to have Navradio starting on initialization. Made no difference.
Issue 2:
1 - When Navradio is open, Radio is open in the background.
2 - If I kill Radio in the task manager, Navradio stops playing and does not restart untill I kill it and restart again.
Hope you manage to do something about AF and station merging. I'll keep my fingers crossed.

Gaugamela said:
Test:
1 - Opened Navradio Free and was playing a radio station,
2 - Opened Bluetooth One (the phone app) and called someone,
Result: as expected, same behaviour as every other app. Sound from the call took over and nothing was playing on the background. When the call ended, Navradio resumed trouble-free.
A couple issues that I detected:
Issue 1:
1 - Was playing Navradio when I switched off the car.
2 - When I turned on the car, Navradio did not resume.
3 - Instead, the default Radio app started by itself on the radio station last played by Navradio.
4 - I had to start Navradio by myself.
5 - Expected to have Navradio open instead of the Radio app. Or at least to have Navradio to restart as well. Toggled option to have Navradio starting on initialization. Made no difference.
Issue 2:
1 - When Navradio is open, Radio is open in the background.
2 - If I kill Radio in the task manager, Navradio stops playing and does not restart untill I kill it and restart again.
Click to expand...
Click to collapse
It's good that Bluetooth is ok, thx for testing it
The problems with original app cannot be solved by a third party app like NavRadio because some things are hardcoded in the syu.ms server.
To avoid this we will probably need to modify the server or to disable/remove the original app but we have time tothink about it and maybe find other ways.
For now it's better to never start the original app and close it with back button before running NavRadio.
Tomorrow I'll upload the full version of the app on PlayStore for those who'd like to purchase it and enjoy all the extra features.
The free version is already available on the store with version 2.16.

Interesting. I guess that making a modified firmware with Navradio installed as the default app might work. Otherwise I'm not sure how to bypass that. @surfer63 is the resident expert on FYT headunits. I think he might have a good idea on how to proceed further.
I tried disabling the stock radio appp, but that option is greyed out so I don't think it can be disabled.
I'll definitely get the full version tomorrow then.

Gaugamela said:
Interesting. I guess that making a modified firmware with Navradio installed as the default app might work. Otherwise I'm not sure how to bypass that. @surfer63 is the resident expert on FYT headunits. I think he might have a good idea on how to proceed further.
I tried disabling the stock radio appp, but that option is greyed out so I don't think it can be disabled.
I'll definitely get the full version tomorrow then.
Click to expand...
Click to collapse
Situation so far:
You can't disable the standard radio app and you certainly should not remove the standard radio app (with an lsec script or modified firmware).
If the unit gets a real cold boot, the FM-chip and Amplifier start before Android and that's why you always hear the radio on a real cold boot.
Removing the radio app makes it impossible to stop the radio (believe me. I've been there when removing the useless radio with a script after switching to DAB )
Also: the radio/FM-chip is actually not switched off, but the radio audio channel is muted.
The new NavRadio+:
If the new NavRadio+ can switch on/off the radio output, it could replace the standard radio. Note though that in that case you would use the free version and would still need to purchase the full version.
But that is just one step: The difficult part would be that some of the activities in the com.syu.ms should be rewritten to launch the app in case of cold boot (if only to switch it off) and when using (hardware) keys, although my FytHWOneKey app could help in the second case as well. The diffcult part is replacing the package name com.syu.music as it should be replaced by "com.navimods.radio" for the full version and by "com.navimods.radio_free" for the free version, requiring two different com.syu.ms mods. Also my FytHWOneKey can't take that over as it is really a call for the package name, which can't be double and which can't be "activity aliased".
As my FytHWOneKey is open source under GNU GPL3, that specific "activiity alias" radio part could be incorporated in both the free and full version.

surfer63 said:
Situation so far:
You can't disable the standard radio app and you certainly should not remove the standard radio app (with an lsec script or modified firmware).
If the unit gets a real cold boot, the FM-chip and Amplifier start before Android and that's why you always hear the radio on a real cold boot.
Removing the radio app makes it impossible to stop the radio (believe me. I've been there when removing the useless radio with a script after switching to DAB )
Also: the radio/FM-chip is actually not switched off, but the radio audio channel is muted.
The new NavRadio+:
If the new NavRadio+ can switch on/off the radio output, it could replace the standard radio. Note though that in that case you would use the free version and would still need to purchase the full version.
But that is just one step: The difficult part would be that some of the activities in the com.syu.ms should be rewritten to launch the app in case of cold boot (if only to switch it off) and when using (hardware) keys, although my FytHWOneKey app could help in the second case as well. The diffcult part is replacing the package name com.syu.music as it should be replaced by "com.navimods.radio" for the full version and by "com.navimods.radio_free" for the free version, requiring two different com.syu.ms mods. Also my FytHWOneKey can't take that over as it is really a call for the package name, which can't be double and which can't be "activity aliased".
As my FytHWOneKey is open source under GNU GPL3, that specific "activiity alias" radio part could be incorporated in both the free and full version.
Click to expand...
Click to collapse
NavRadio+ can switch on/off the radio output as it use the same commands of the original app.
I'll try tomorrow to remove the original app and see what happen on cold boot, maybe something has changed in these new units...
I'm pretty sure that at some point i was able to start NavRadio in place of original app at cold boot but i can't remember now how i did it and if there were other issues involved.
@surfer63 please note that now we are on Android10 where system partition cannot be mounted and you cannot make any changes even with Superuser. You need a magisk modules to make changes there i guess...
We can always use the lsec script method to modify what we need.

KoTiX2 said:
NavRadio+ can switch on/off the radio output as it use the same commands of the original app.
I'll try tomorrow to remove the original app and see what happen on cold boot, maybe something has changed in these new units...
I'm pretty sure that at some point i was able to start NavRadio in place of original app at cold boot but i can't remember now how i did it and if there were other issues involved.
@surfer63 please note that now we are on Android10 where system partition cannot be mounted and you cannot make any changes even with Superuser. You need a magisk modules to make changes there i guess...
We can always use the lsec script method to modify what we need.
Click to expand...
Click to collapse
Note that both the radio app and the com.syu.ms are in the oem partition, not in the system partition. That oem partition is also accessible on these Android 10 units. You do not have to "touch" the system partition. And yes: it requites the 7862lsec.sh script (or 8581lsec.sh script on the 9863a units, where the apps are identical).
Speaking of this: You should edit the title of this thread to "New "NavRadio+" ported to FYT uis7862 (ums512) and FYT sc9863a (uis8581a) devices".
System partitions (6315_1.zip versus 6316_1.zip) are different. The AllAppUpdate.bin is identical. You could create a "universal" installer using the lsec6315update with the 7862lsec.sh for the uis7862 units, and the lsec6316update and 8581lsec.sh for the uis8581a units.

surfer63 said:
Note that both the radio app and the com.syu.ms are in the oem partition, not in the system partition. That oem partition is also accessible on these Android 10 units. You do not have to "touch" the system partition. And yes: it requites the 7862lsec.sh script (or 8581lsec.sh script on the 9863a units, where the apps are identical).
Speaking of this: You should edit the title of this thread to "New "NavRadio+" ported to FYT uis7862 (ums512) and FYT sc9863a (uis8581a) devices".
System partitions (6315_1.zip versus 6316_1.zip) are different. The AllAppUpdate.bin is identical. You could create a "universal" installer using the lsec6315update with the 7862lsec.sh for the uis7862 units, and the lsec6316update and 8581lsec.sh for the uis8581a units.
Click to expand...
Click to collapse
/oem is a symlink of /system/oem
So mount properties behaves the same.
I got access with Superuser from my app only with the original firmware that came with the unit.
After upgrading the firmware to a slightly newer version was not possible to mount OEM or system

KoTiX2 said:
/oem is a symlink of /system/oem
So mount properties behaves the same.
I got access with Superuser from my app only with the original firmware that came with the unit.
After upgrading the firmware to a slightly newer version was not possible to mount OEM or system
Click to expand...
Click to collapse
They now use dynamic partitions.
product, vendor, system, etcetera are now all part of the superpartition unisoc.
But as far as I know /oem is still not a symlink from /system.
But I guess I have to wait till I have my own unit.
Do you still have that slightly older firmware where it was still possible? I really would like the 6315_1.zip from that one to investigate how to go back from dynamic partitions to the "old fashioned" partitions. I like to see it before I try without "proof from the past"

KoTiX2 said:
Hi all,
I finally ported my NavRadio+ app to FYT based devices with CPU UIS7862!!
It surely don't work on Sofia and older FYT devices and probably it won't work on all others.
I own an Isudar V72 unit with CPU UIS7862 with MCU NOR FYT=1 so at this stage i know it work on my unit, other users will confirm the compatiibility with other models.
I still need to work on some parts like steering wheel controls, launchers integrations etc.. but I also need to know if this free version work for all people with a compatible model.
I need to know:
- if the radio controls work, like autoscan, seek stations, etc..
- if RDS informations are displayed
- if sound output work (you can hear sound)
- if audio focus and mixing work correctly
Right now i can publish only the free version here:
DOWNLOAD NAVRADIO FREE v2.16
IT DIFFER FROM PAYED VERSION JUST IN TERMS OF USER CUSTOMIZATIONS OPTIONS AND NO LOGOS SUPPORT.
When i'm sure that this version work ok i will publish on playstore the full version.
RIGHT NOW THE NAVRADIO APPS ON PLAYSTORE DOESN'T SUPPORT FYT UNITS.
You can use only the version from this thread.
PLEASE REPORT BACK ANY ISSUE.
Thanks
Here you can see a sample video of my working progresses:
Sample Video
Here a demonstration video of the automatic assignment of Logos, station name and alternative frequencies:
Demo
It's widely customizable in the graphics and layouts:
- Wallpapers: Presets (about 30), system wallpaper, solid color, from personal images
- Color themes (20 predefined or personal adjustments)
- Night mode on / off, timed or automatic with car lights (MTC only)
- Resizable text elements and Font choice
- 3 view modes:
Vertical List (Left/Right and5,6 or 6 buttons)
Horizontal Grid (1x5, 2x3, 2x4, 2x5, 3x3, 3x4, 3x5)
Fullscreen (double tap or timed)
- Selectable inactivity timer for fullscreen activation
- Toggable StatusBar in fullscreen mode
- Toggable Clock and GPS speed in fullscreen
- Toggable Frequency slider
- Automatic and manual assignement of Logo images to the stored radio stations based on RDS id and station name scraping.
- Logos can be downloaded from internet DIRECTLY IN THE APP or sideloaded.
- Station lists can be sorted by name or frequency and saved/restored in a Json format
- Improved RDS AF function with automatic storing and merging of alternative frequencies found
- Notifications Toasts
- Selectable Radio Region
- Station editable elements : Position, Frequency, Name, Logo, Favorites
- 2 Homepage Widgets, horizontal and vertical design
- Floating widget
- Autostart on boot option
- Support 800x480, 1024x600, 1280x720 and 1920x1080 display resolutions
- Resizable Texts elements
- App full settings backup/restore function
List of available Logos by nationality, in Bold the ones with automatic Logos assignement functionality (by RDS id):
EURÓPA: Albánia, Andorra, Ausztria , Ausztrália, Belgium , Bulgária, Bosznia-Hercegovina, Fehéroroszország, Ciprus, Horvátország , Cseh Köztársaság , Dánia, Észtország, Feröer-szigetek, Finnország , Franciaország , Németország, Gibraltár, Görögország, Magyarország , Írország , Izland, Olaszország , Litvánia , Lettország, Liechtenstein, Luxemburg, Macedónia, Málta, Monaco, Moldova, Montenegró, Hollandia, Norvégia, Lengyelország , Portugália , Románia , Oroszország, Szerbia, Szlovákia, Szlovénia, Svédország, Svájc, Dél-Korea, Spanyolország, Törökország, Tajvan, Ukrajna, Egyesült Királyság
DÉL-AMERIKA: Argentína, Brazília, Chile, Kolumbia, Mexikó, Perù
USA: Alabama, Alaszka, Arizona, Arkansas, California, Kanada, Colorado, Connecticut, Delaware, Florida, Georgia, Hawaii, Idaho, Illinois, Indiana, Iowa, Kansas, Kentucky, Louisiana, Maine, Maryland, Massachussets, Michigan, Minnesota, Mississippi, Missouri, Montana, Nebraska, Nevada, New Hampshire, New Jersey, New Mexico, New York, Észak-Karolina, Észak-Dakota, Ohio, Oklahoma, Oregon, Pennsylvania, Puerto Rico, Rhode Island, Dél-Karolina, Dél-Dakota, Tennessee, Texas, Utah, Vermont, Virginia, Virgin-sziget, Washington, Washington DC, Nyugat-Virginia, Winsconsin, Wyoming
KÍNA, JAPÁN, MALAJZIA, FÜLÖP-szigetek
MAROKKÓ, TUNÉZIA
AUSZTRÁLIA, ÚJ-ZÉLAND
Néhány kép:
Click to expand...
Click to collapse
rem