Related
Hi, I've installed GProfile on my phone twice - it works well enough, but each time I've had massive battery drain - is there anything I can change/anyone else had a similar experience?
Thanks.
Are you using the latest version? I read this was fixed on a later version. Also do you use anything like SEVEN or any data intensive applications?
Thanks for replying.
Not sure about which version I'm using, I THINK it's 6.2? Not running any intensive apps though.
How can I add some ringTones to GProfile???
Hi friends...
I would like to add some new RingTones from my PC to my Pocket PC.
I can copy them to /documents/ringtones and it's working for WM6.5 to add new ringtones to windows...
but I can't add them to my Gprofile (G Profile) menu and I can't choose my favorite ringtone in Gprofile.
I'm using Gprofile 1.1 built 1123 (the last version until now)
help me plz, where can I add new ringtones for my Gprofile???
Hey guys,
take it easy and go to the developers website with forum. There will get help for all quesyions and you can read so many stuff.
main page = www.ageye.de
forum = forum.ageye.de
Today on sunday at 08:43 european time the website is under Maintenance Service...
EDIT:
Since 19:00 european time the website is back (the moment where i have this tested, possible the site was back much earlier)
Hi!
I've also had the massive battery drain issue with G-Profile. According to the developer it's ROM related, so I guess it works on some ROMs and not on others. Maybe it has something to do with which WinMo build it's running. Also it can be related to what kind of profiles you're using. Those which are network dependent (auto switch on location for example) naturally draws more battery.
The latest G-Profile version is build 0401 (1st of april 2010). I've tried it on two Energy ROMs, one with WinMo 21905 and MaxSense back in June and one recently with WinMo 21682 and CHT 2 beta. I guess it's not a CHT/MaxSense issue since both of them had the massive battery drain even with no network activated profiles or auto switching (about 40-50% less battery in the morning after just lying in standby mode overnight with all radios except phone turned off).
So, all you people using it please tell me which ROM you're using and if it works or not. And also what kind of profiles you're using. I really like this app and will use any ROM to get it to work.
Cheers,
Tummen
ok so i know that its a Rom,
but how do i get it.
whats the benefits of it?
i mean whats all the hype about it?
please give me information about it =)
I also need to know where i can get the link fro
Should be on first page of development forum. Read OP for all info about the ROM and link will be there too.
[ROM][WTF][BBQ] CyanogenMod-6 - No Sense at ALL! - V6.0.0 (08/28/2010)
[INFO] Unofficial Cyanogen Mod 6.1 Nightly Thead/FAQ (Updated 9/23)
Basically, it's a fully open-source ROM that strictly adheres to the AOSP (believe it or not, while Android is FOSS, or Free Open Source Software, Sense is not, making it non open-source ROM. It's kinda like a moral high-ground, if you will).
100% of the CyanogenMod source code can be viewed on their Github
If you have a feature request, odds are it can and will be implemented in the next version (or if you're more daring, in the Nightly. See below)
If you have a bug report, you can issue it directly to the CM team on their issue tracker. Most bugs are fixed by the next version (and are progressively tested in the Nightly)
Features many speed, battery life, and UI tweaks not found in Sense ROMs, making it also very flexible, especially for skinning.
Has such features as the ability to force roaming-only mode (good for those who don't live in a city with good Sprint coverage, or work in such a location), no carrier-specific bloatware, and many other heavily requested items (for example, the next release will be featuring camera features that outshine even Sense's camera, such as continuous auto-focus, manual focus area, autofocus, and all of this even while recording video).
Has developers and a large community you can get help from, via forums, Twitter, or IRC.
Is recompiled from source every night, so the latest features, bugfixes, and improvements can be tested and tried by users, allowing for a better full release version.
Listed in ROM Manager, meaning that it's extremely easy for people to pull down release candidates, full versions, nightlies, etc.
Some other tweaks/features:
Has the Bluetooth bitpool setting fixed, so audio on BT headphones/headsets sounds superb.
Has the Stagefright AAC fix so AAC streams (Pandora before v1.4, Slacker, XiiaLive, etc.) don't sound like 32kbps MP3's.
Allows for 0, 90, 180, and 270 degree viewing, and you can turn off certain angles via the settings.
Nightlies are currently running a .34 kernel (faster, better battery life, etc.) and hopefully will have .35 or later in time for the official release of CM6.1 or 6.2.
Has a better Bluetooth stack which allows for the use of Wiimotes as gaming controllers, Bluetooth keyboards and mice, and other devices.
FPS unlocked
Both cameras take pictures and record videos.
kernel speed tweaks
Custom version of ADW launcher
Expanded Spare Parts app
DSP settings
Torch flashlight uses camera flash, includes widget
Additional settings and tweaks for Contacts, Dialer, and MMS (maybe more)
There's really a ton of features and things to find in there (like for example, they just added a feature where you can hold down the Back button to force-close the topmost application in case it locks up). You can see new updates as they're created by following the CMSrc bot on Twitter which posts all of the updates as they happen from Github.
And you know what, if you don't like it, fine, that's your opinion. You can always go back to stock, or whatever you want. No pressure.
EDIT: And let me say one more thing: On Stock, I got about 4 hours of battery life at work (-110dB signal, 20-60% Time without Signal). I get about 6-10 hours on CyanogenMod with the Snap 7.6 kernel, same exact environment, with more usage.
Dang,thanks guys.
Sent from my HTC EVO
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
Samsung 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.
Currently, this is tentative support.
Tentative support is based upon reports from users of this device who decided to use the patch and report back on their own.
Reports indicate great success.
Works awesome and the mod has helped me getting a GPS fix in just 40 seconds that too from inside a building. I lost the quick fix since updating from a stock ROM to CM 10 AOKP but I see this has better performance than the stock ROM too. A must try for anyone. Besides, the best part about this mod is that the one file that is replaced if not giving satisfactory results can be reverted back to the old one without a fuss.
---------- Post added at 11:05 PM ---------- Previous post was at 10:32 PM ----------
Umm, a question to the dev and anyone who has any info on this, has GLONASS been disabled on the FXP or CM ROMs for the Xperia S?
a4rocks said:
Works awesome and the mod has helped me getting a GPS fix in just 40 seconds that too from inside a building. I lost the quick fix since updating from a stock ROM to CM 10 AOKP but I see this has better performance than the stock ROM too. A must try for anyone. Besides, the best part about this mod is that the one file that is replaced if not giving satisfactory results can be reverted back to the old one without a fuss.
---------- Post added at 11:05 PM ---------- Previous post was at 10:32 PM ----------
Umm, a question to the dev and anyone who has any info on this, has GLONASS been disabled on the FXP or CM ROMs for the Xperia S?
Click to expand...
Click to collapse
I have no clue as to what a particular ROM does to GLONASS support in devices that do support it. However, this patch does not alter GLONASS usage whatsoever on a device. This only alters the GPS side of the location functionality.
This does assist in better performance of GPS/GLONASS combinations because it decreases the GPS response time which works in tandem with GLONASS when GLONASS is enabled within your device's code -and- functioning through its receiver.
crypted said:
I have no clue as to what a particular ROM does to GLONASS support in devices that do support it. However, this patch does not alter GLONASS usage whatsoever on a device. This only alters the GPS side of the location functionality.
This does assist in better performance of GPS/GLONASS combinations because it decreases the GPS response time which works in tandem with GLONASS when GLONASS is enabled within your device's code -and- functioning through its receiver.
Click to expand...
Click to collapse
Ok so a couple of hours of research into GPS and GLONASS gave quite a bit of interesting insights. GLONASS does work on CM10 JB as tested by GPS Status. Phew, there is so much to learn. Its actually interesting tech. However, I see that GLONASS is not as active or quick as it used to be on the Stock Sony ROMs. Any way you could try and tweak that crypted?
a4rocks said:
Ok so a couple of hours of research into GPS and GLONASS gave quite a bit of interesting insights. GLONASS does work on CM10 JB as tested by GPS Status. Phew, there is so much to learn. Its actually interesting tech. However, I see that GLONASS is not as active or quick as it used to be on the Stock Sony ROMs. Any way you could try and tweak that crypted?
Click to expand...
Click to collapse
I really don't have experience with GLONASS. If there are configuration files (.conf or .xml), I can look into it. You'd have to private message me the contents though.
Just to reiterate, this patch does not affect GLONASS with any device. It only benefits GPS and in combination helps with locks that are either GPS or a mixture of GPS and GLONASS data.
Why go through all this mess when you can download a-gps data directly from the 'GPS Status' app.
I get a fix in 2-4 seconds when outside and 8-9 seconds when inside my home.
You can even set the app to update the a-gps data daily.
Thanks for your time but this method is just of no use!
devilsneck said:
Why go through all this mess when you can download a-gps data directly from the 'GPS Status' app.
I get a fix in 2-4 seconds when outside and 8-9 seconds when inside my home.
You can even set the app to update the a-gps data daily.
Thanks for your time but this method is just of no use!
Click to expand...
Click to collapse
You proved your ignorance in how aGPS works. Good for you!
Downloading the almanac isn't the only thing that resolves GPS issues. Sure, you're lucky and get a great lock time. How good is your accuracy, though?
From that, this is for people with problems as the OP post discusses. Do I suggest someone use it if there isn't an issue? NO.
Before you post on some development thread, make sure you're ignorance isn't showing.
devilsneck said:
Why go through all this mess when you can download a-gps data directly from the 'GPS Status' app.
I get a fix in 2-4 seconds when outside and 8-9 seconds when inside my home.
You can even set the app to update the a-gps data daily.
Thanks for your time but this method is just of no use!
Click to expand...
Click to collapse
First of all, you may be using the stock ROM and as I reiterate again, stock ROMs have better GPS fix times than CM ones. Sony must have optimised them nicely but since I upgraded to Jelly Beam CM, I was having issues with respect to quick fix on location. In fact, no one even looks at GPS fixes around unless there is something drastically wrong. Good that you don't issues but please do not berate someone else's work for something that is of no use to you but a lot of use for other mates with Xperia S and JB.
a4rocks said:
First of all, you may be using the stock ROM and as I reiterate again, stock ROMs have better GPS fix times than CM ones. Sony must have optimised them nicely but since I upgraded to Jelly Beam CM, I was having issues with respect to quick fix on location. In fact, no one even looks at GPS fixes around unless there is something drastically wrong. Good that you don't issues but please do not berate someone else's work for something that is of no use to you but a lot of use for other mates with Xperia S and JB.
Click to expand...
Click to collapse
First off, I'm not on stock, I'm using PA's latest JB build.
Anyway, as I said, I didn't mean to diss the member's work.
I respect the time he has put into it.
I'll just leave you guys to yourself, apoligies for pointing out something easier.
Peace.
---------- Post added at 08:17 PM ---------- Previous post was at 08:02 PM ----------
crypted said:
You proved your ignorance in how aGPS works. Good for you!
Downloading the almanac isn't the only thing that resolves GPS issues. Sure, you're lucky and get a great lock time. How good is your accuracy, though?
From that, this is for people with problems as the OP post discusses. Do I suggest someone use it if there isn't an issue? NO.
Before you post on some development thread, make sure you're ignorance isn't showing.
Click to expand...
Click to collapse
I have pretty good accuracy, I use my GPS daily.
I only posted cause I was having the same problem and I fixed it by updating the a-gps data.
Somebody try it first maybe and report back if it helps?
Im sure you know more about GPS than me,
So Im sorry if I came along as a douchebag and thank you for your great contribution!
:good:
devilsneck said:
First off, I'm not on stock, I'm using PA's latest JB build.
Anyway, as I said, I didn't mean to diss the member's work.
I respect the time he has put into it.
I'll just leave you guys to yourself, apoligies for pointing out something easier.
Peace.
---------- Post added at 08:17 PM ---------- Previous post was at 08:02 PM ----------
I have pretty good accuracy, I use my GPS daily.
I only posted cause I was having the same problem and I fixed it by updating the a-gps data.
Somebody try it first maybe and report back if it helps?
Im sure you know more about GPS than me,
So Im sorry if I came along as a douchebag and thank you for your great contribution!
:good:
Click to expand...
Click to collapse
aGPS almanac data renewal downloads is less than 10% of the issue most of the time.
If you open up my configuration file, you will notice that there are tons of variables and each are customized. I created sections explaining the general synopsis of var sets...
Now we have a (near) complete configuration. I tossed in that near because there could be surprises I haven't found, but this thing has brought devices back to life that had no GPS. In fact, ASUS ripped my work on the Transformer series and put it in their official ROM updates without a gracias whatsoever.
Lets then consider internet mobile data networks. I offer something more. GPS Status queries the same address in the gps.conf to update the aGPS data. Well, compare them. I provide a CDN (content delivery network) that provides xtra.bin data rather than Qualcomms overloaded server. This has brought about great resolutions in general latency and timeouts of downloading almanac data.
This is directly on subject with your little mention.
From that, I created and maintain an DNS pool of Stratum II time servers rather than NTP.ORG cable modems because of the same network testing observations.
Over 20 mobile carrier networks around the world were tested.
There's gotta be a reason why my patch has tens of thousands of direct downloads, millions of queries per month, etc.
EDIT: The dev of GPS Status and I are considering a joint effort to bring his APK and my work together in a Google Play environment. If we do it, it'll be early 2013. He knows APK side and bringing GPS readings to the forefront. I know the backend process.... Sounds like a good mix...
Crypted, my GPS isn't communicating at all with Google Maps. While GPS status is properly tracking, there is no location in Google Maps. Data connection only helps in tracking the same. What may be wrong here?
Sent from mein wünderbar Xperia S
a4rocks said:
Crypted, my GPS isn't communicating at all with Google Maps. While GPS status is properly tracking, there is no location in Google Maps. Data connection only helps in tracking the same. What may be wrong here?
Sent from mein wünderbar Xperia S
Click to expand...
Click to collapse
Uninstall, then reinstall Maps. If all other apps are working fine with GPS, then the problem lies somewhere within the GMaps receiving and processing of the data.
crypted said:
Uninstall, then reinstall Maps. If all other apps are working fine with GPS, then the problem lies somewhere within the GMaps receiving and processing of the data.
Click to expand...
Click to collapse
I will try other apps but reinstalling, checking unchecking GPS options, clearing cache and dalvik cache haven't helped at all. It's strange because in any case, it is not even interfacing with the GPS.
Any fixes you can suggest?
Sent from mein wünderbar Xperia S
a4rocks said:
I will try other apps but reinstalling, checking unchecking GPS options, clearing cache and dalvik cache haven't helped at all. It's strange because in any case, it is not even interfacing with the GPS.
Any fixes you can suggest?
Sent from mein wünderbar Xperia S
Click to expand...
Click to collapse
Did you completely uninstall Maps and reinstall it after a reboot?
And, did you try another ROM?
Sent from my Galaxy Nexus using xda app-developers app
I haven't tried another ROM but I guess I will. And I definitely completely un installed, rebooted and reinstalled. The fact that this is so weird that I could not find any solutions elsewhere has made me mad. I actually kinda love this ROM. I will try another navigation application in the mean time but if you have a prospective solution, it would be absolutely awesome
Sent from mein wünderbar Xperia S
a4rocks said:
I haven't tried another ROM but I guess I will. And I definitely completely un installed, rebooted and reinstalled. The fact that this is so weird that I could not find any solutions elsewhere has made me mad. I actually kinda love this ROM. I will try another navigation application in the mean time but if you have a prospective solution, it would be absolutely awesome
Sent from mein wünderbar Xperia S
Click to expand...
Click to collapse
As I said before, it's a GMaps library issue from what you described. It could be ROM related since you stated that GPS Status is perfectly on target and GMaps uninstall didn't work.
If this randomly began happening with everything working 100%, something may have corrupted in one of your NANDFlash partitions....
crypted said:
As I said before, it's a GMaps library issue from what you described. It could be ROM related since you stated that GPS Status is perfectly on target and GMaps uninstall didn't work.
If this randomly began happening with everything working 100%, something may have corrupted in one of your NANDFlash partitions....
Click to expand...
Click to collapse
And is the NANDFlash partition recoverable? :crying:
crypted said:
aGPS almanac data renewal downloads is less than 10% of the issue most of the time.
If you open up my configuration file, you will notice that there are tons of variables and each are customized. I created sections explaining the general synopsis of var sets...
Now we have a (near) complete configuration. I tossed in that near because there could be surprises I haven't found, but this thing has brought devices back to life that had no GPS. In fact, ASUS ripped my work on the Transformer series and put it in their official ROM updates without a gracias whatsoever.
Lets then consider internet mobile data networks. I offer something more. GPS Status queries the same address in the gps.conf to update the aGPS data. Well, compare them. I provide a CDN (content delivery network) that provides xtra.bin data rather than Qualcomms overloaded server. This has brought about great resolutions in general latency and timeouts of downloading almanac data.
This is directly on subject with your little mention.
From that, I created and maintain an DNS pool of Stratum II time servers rather than NTP.ORG cable modems because of the same network testing observations.
Over 20 mobile carrier networks around the world were tested.
There's gotta be a reason why my patch has tens of thousands of direct downloads, millions of queries per month, etc.
EDIT: The dev of GPS Status and I are considering a joint effort to bring his APK and my work together in a Google Play environment. If we do it, it'll be early 2013. He knows APK side and bringing GPS readings to the forefront. I know the backend process.... Sounds like a good mix...
Click to expand...
Click to collapse
Apk on google play would be awesome!
a4rocks said:
And is the NANDFlash partition recoverable? :crying:
Click to expand...
Click to collapse
I don't know how it works for your device as it's different in each model, but usually in those instances it flushes out corrupted GPS cache within a few days.
You really need to test another ROM if other navigation apps (not Google's or any relying on GMaps API) fail you.
Thanks to the mods for moving this. Sorry i posted it in the wrong place - oops!
Hey everybody. In a blatant and self serving attempt to try and cultivate interest and support in a phone that I have just purchased, I thought I would post a mini review here with a little bit of info
Seriously though, if, like me, XDA as usually your one stop shop for everything phone related and you're considering buying one of the many offerings available directly from China these days, getting the right info can be hard. Sure, some info is available on other sites, but often online translation tools are necessary and it's hard to get a clear picture of what you can really expect from a prospective purchase.
I've been reading about various Chinese devices for over a year now, quietly waiting until I was sure I could get a reasonable level of performance for my money before buying one, all the while nursing my ageing HTC Sensation through daily use. I have a Samsung Galaxy Note 2 as well, but that has a broken screen so it is purely used as a mini media PC connected to a TV these days. I also have an Nvidia Tegra Note that offers great performance at a very reasonable price.
I am uncertain how much waffle you guys will want to wade through so I'll list some basic specs and then provide a few pros and cons as I see them, plus a few very basic tips that I've stumbled on in the first week, some of which will apply to similar devices that use vey similar ROMs. If you want more info, please ask.
Forum member oxiroxt has had a fairly mixed experience with their G4S, including hardware problems. details are in post 1175 here: http://forum.xda-developers.com/showpost.php?p=59463919&postcount=1175
Here are the basic specs:
Jiayu G4S -
16GB ROM 2GB RAM - MediaTek Octacore A7 MT6592 SoC @1.7Ghz with Mali 450 GPU.
Dual sim card standby (one Micro SIM Card)
GSM 900/1800MHz (see screenshot below of MTK Engineer Mode which shows more bands available, including GSM850 - I haven't tested this band though)
WCDMA 900/2100MHz
Android OS: 4.2.2
4.7 inch, IPS multi points corning Gorilla II OGS touch Screen (I have my doubts about the Gorilla Glass as I have a couple of small scratches already)
Camera: Front camera 3.0 Megapixels. Back camera: 13.0 Megapixels with CMOS flashlight, auto focus
Stereo FM Radio
Gravity Sensor, Proximity Sensor, Light Sensor
3000mAh battery
Dimensions: 133×65×10(mm)
What's in the box:
1 x Phone
1 x Battery
1 x AC Charger Adapter
1 x USB Cable
Pros:
Price - Only £137 delivered to UK via DHL - price is falling all the time at the moment too.
Screen - Pleasing colours, better outdoor visibility than I expected.
Call quality - good, with noise cancellation microphone on rear of device (call quality better than HTC Sensation)
Performance - over 27,000 points in Antutu, nice and fluid in use. Not as quick as Tegra Note or Snapdragon 800 of course
Battery life - over five hours of screen on time in a sixteen hour period, with 37% battery remaining. I have hit eight hours of screen time twice.
Build quality - less creaky than my Note 2
Supports USB OTG
Supports USB Mass Storage when connecting to PC
Compact size - at only 65mm wide, one handed use is practical for most people.
GPU performance is not great - only two thirds of the Samsung Galaxy S4, but it's ok for Modern Combat 4. It scores 61FPS on in Epic Citadel on high detail setting (Ultra High setting unavailable).
Pre-rooted - Root can be toggled under Settings/Security (love this feature in a stock ROM)
SD card slot
Dual SIM
Removable battery
Notification Light - three colour, RGB
Cons:
Lack of developer support here on XDA for now
No MHL for TV out
Caller ID mismatch bug
Camera below expectations - certainly worse than tweaked HTC Sensation camera
Possible wifi bug - affects things like wireless streaming if the screen is off
Deodexing ROM to work with files not 'standard' procedure
GPS - connects quickly but accuracy is still behind Qualcomm's efforts these days (much better than the old HTC Touch Pro/Raphael though!!)
Internal SD only approx. 9GB with internal storage just under a further 4GBs (It should be possible to repartition this by altering EBR1 and EBR2, but I haven't tried. iOcean have done this on their latest ROM for the X7S, decreasing phone storage to 1GB and increasing internal SD card to about 13GB - May 2014).
Screen has some backlight bleeding around bottom edges - sensitivity slightly lower than I'm used to but by no means bad.
Most sites claim 64GB Micro SDXC support - this is wrong, exFAT is not supported so you'll need to format the card to Fat32 for it to work.
English US - if you're in the UK and you change the language to English, you'll be stuck with US English language and location. To get around this you will need to toggle root on in settings/security, download Morelocales2 from the Play Store and then use it to change over to EN GB. I've edited the build.prop too.
Xposed - doesn't work at the moment due to the way the ROM is compiled (if I've understood correctly). Head over to that thread for basic details of a workaround to deodex the ROM, or download one of the customs ROMs based on stock that has been deodexed.
No 4G
Buttons are not backlit
There were issues with Facebook and Whats App but apparently all is now OK - sorry I don't use these so I haven't tried. Earlier versions of Facebook apparently work.
Recovery, Drivers for PC, Flash tools etc:
Jiayu.es app - Recoveries and tools are available from several sources, but at the time of writing the easiest way now is to download the Jiayu.es app. This now has downloads for the stock recovery, CWM, Stock ROM (European version with ASOP keyboard as opposed to Baidu which comes on the phone if you buy directly from China) as well as drivers for PC and the necessary tools to flash the ROM from a PC.
Mobile Uncle Tools - I used this to flash CWM recovery and tweak a few things before I discovered the Jiayu.es app. You can use this to back up your IMEI (NVRAM) which I highly recommend as the loss of IMEI is something I have read about frequently when people are flashing similar devices.
ROMs:
Before flashing any ROMs, I recommend using MTK Droid Tools to create a backup of your device on your PC. This includes backing up your IMEI number and every other partition. If you hit trouble you can restore your device to factory fresh. Head over to gizbeat for a tutorial and video.
Unfortunately at the moment I don't have time to try lots of ROMs (boooo!) which is frustrating, but it's also a mark of the fact that I'm just able to use the Jiayu stock ROM without too many compromises.
As the device gains in popularity there are now more an more ROMs appearing in various forums around the web. At the moment, there are a few basic choices to make. First, there are the stock ROMs 'officially' released by Jiayu. The stock ROMS are installed using SPFlashtools. Secondly there are deodexed versions of the stock ROMs that will allow you to run the Xposed framework and mods like the excellent Gravitybox. Thirdly there are ports of other ROMs, such as MIUI of ColorOS. The last two types will be installed through recovery, for which you need a custom recovery such as CWM.
One of the stock ROMs as well as both a stock recovery and CWM Recovery are available through the Jiayu.es app.
For me, the main source of ROMS remains NeedROM. There are now several recoveries, the stock ROM as well as ports of MIUI, ColorOS, YunOS and so on. This is the place I usually check first as the site is well organised and in English which makes it easier for me: http://www.needrom.com/phone-roms/jiayu/g4s/
There are now a number of ROMs available here, including at least a couple of MIUI here:
http://www.592zn.com/ (use Google Translate to browse the site if needed and to find the threads relating to the Jiayu G4S
Jiayu forum:
http://bbs.ejiayu.com/forum-184-1.html
Some of mite_jan's posts with recommendations/ROM related links (press thanks if you appreciate his links):
http://forum.xda-developers.com/showpost.php?p=52989103&postcount=50
http://forum.xda-developers.com/showpost.php?p=53133246&postcount=90
http://forum.xda-developers.com/showpost.php?p=53270549&postcount=134
http://forum.xda-developers.com/showpost.php?p=53284249&postcount=141
http://forum.xda-developers.com/showpost.php?p=53361043&postcount=180
Two Hidden Tweaks in ROM:
1. A limited set of developer options was already available in settings when I first booted my G4S (Stay Awake, USB Debugging, Allow Mock Locations), but if you want access to the whole lot you can repeatedly tap the Android Version section under Settings/About Phone. This will take you straight to the developer options page. By default all animations are turned off so I used this to turn them on. You will still only have access to limited developer options once you exit this page, so you will have to get tapping the next time want to go back into it.
2. An 'Advanced Settings' option in Settings menu will appear if you repeatedly tap the Build Number under Settings/About Phone. This new menu allows you to tweak the transparency separately for lockscreen, main interface and the status bar itself. There's also and option to toggle the volume key wake feature, but this doesn't do anything for me - the volume buttons always wake the phone.
General Blurb:
So far, I feel like my money has been well spent, though I'm only a week into ownership. The screen in particular has exceeded my expectations with pleasant colours and reasonable outdoor visibility (better than HTC Sensation, but not great). Whites look 'white' as opposed to having the slightly yellowy hue that has affected all the devices with AMOLED screens that I've used, not to mention the poor offering on my Tegra Note. There's more backlight bleeding around the edges than I would like though which is a pity. This is certainly not the case with all Chinese devices - the iOcean X7S, for example, has a much better screen from that point of view. Call quality has exceeded my expectations and, as with other similar devices, the firmware offers various ways to manage the dual SIM functionality. As well as binding specific contacts to a particular SIM, you can also independently choose which SIM is used for SMS, voice calls, data and video calls. You can also be prompted to choose which SIM to use on the fly each time if you prefer. Only one SIM can use WCDMA at a time, but you can choose which SIM that is without physically swapping the SIMs or rebooting the phone. I thought battery life might be poor with two SIMs in, especially as I live in a marginal area for one of the networks I use, but so far battery life has been pretty good in general use. I was surprised to get over five hours screen time and still have well over 30% battery left. Intensive games and videos can drain the battery more quickly though of course.
Build quality also appears to be pretty good for a budget device. It's certainly less creaky than my partner's Note, my Note 2 and any other number of Samsung devices that I've used. The petite dimensions are also great. The thickness of 10mm simply isn't an issue for me, especially given the generous battery under the hood. For the first week there were no noises from it at all, though there is a tiny creak from one corner of the battery cover now after many many cycles of removing and replacing it as a result of messing about with it.
The main issues I've faced so far are the fairly weak 13MP camera that introduces a lot of noise and offers poor detail in spite of a wide range of tweaking options within the app itself and a caller ID mismatch bug revolving around MIN_MATCH criteria . The latter means that if you store a contact's telephone number in domestic format (e.g. 07707 123456) then send them a text message, any reply you receive from them will be prefixed with the international country code and will be put into a separate thread. If you store their number with the international dialling code, when they call from the same country, the phone will not recognise their number. So far the easiest bodge is to store both formats for each contact, then remember to send SMS to the number will international prefix. Both these issues are deeply annoying from my perspective. See here for an explanation of the caller ID problem: http://forum.xda-developers.com/showthread.php?t=2268120
There does also appears to be a bug with wifi - if you stream films wirelessly to your TV the screen will have to remain on, which is the first time I've had this issue.
Performance is genuinely fluid if not up to Tegra 4 or Snapdragon 800 standards, but it's certainly better than the Galaxy Note 2. The one area that confuses me is GPU performance. I very briefly had an iOcean X7S which has the same SoC but a 1080p screen rather than the Jiayu's 720p. To my surprise the Jiayu actually scores lower in Antutu in this area. My guess is that either this is a SoC from a different BIN compared to those going into the 1080p devices, or something else is going on to artificially limit performance. On balance, for the money, performance is fantastic and is better than other phones being offered in the UK from retail outlets at over twice the price. Personally I miss some of the features of HTCs Sense based ROMs, but not enough at the moment to shell out over £500. This is now my daily driver and unless it dies prematurely I think I'll have it for up to a year (dependent upon whether or not I get fed up with the camera). Within a year my gut feeling is that similar devices with 4G will be ready for main stream adoption In much the same way that sections of the motorcycling community enjoy having a flagship bike and a small capacity run around to hack, tune and mess around with, I kind of hope more XDA users will start to buy devices like the Jiayu G4S and mess around with them. I know MediaTek have been useless at releasing the source code which is a massive stumbling block, but we can still have a bit of fun with them, eh?
*UPDATES*
Battery life - on one occasion I reached just under 35 hours of up time, with 7 hours 52 minutes of screen time, with 9% battery left. Usage was a mix of a few phones calls, some text messages, two email accounts, web browsing, about thirty minutes of Shadowgun, around an hour of streaming music via A2DP and about two hours of listening to music on headphones.
Multi tasking is good when web browsing and listening to music (as it should be). Playing a game like Shadowgun whilst using a Moga Pro controller AND streaming music via Bluetooth is also absolutely fine.
Bluetooth - Bluetooth range is better than on my Tegra Note, HTC Sensation and Note 2 when streaming music. The actual quality of audio via Bluetooth is not the best. It's noticeably worse than the Note 2.
Audio quality out of the headphone jack is also not great. The built in equaliser helps a lot, but it really doesn't sound much better than Bluetooth to me.
Camera - somehow, I have dust inside the outer lens already (the outer lense being part of the sealed camera unit). UPDATE I hovered the dust out!!
As for the images themselves, I've found setting sharpness to maximum and turning off face beautification helps improve images a bit. User 'coffee' over at MTKForums.com reckons the Camera FV-5 app is great at getting the best out of the sensor in the G4S, especially if you save the images in lossless PNG format. I haven't tried it yet.
GPS - after using GPS Test to get the first lock (go outside, set the option within the app to keep the screen on and update AGPS data), subsequent locks have usually been very quick. Unfortunately accuracy in apps like Co-pilot has been very hit and miss for me. On a few occasions my location is shown on an adjacent road that is over 50 metres away. In one instance restarting the device solved the problem. I've recorded a few tracks whilst cycling using Endomondo Pro and these have been fine apart from one occasion where I stopped and went in a shop and it added a mile onto my journey!
Notification LED - this is a three colour red, green, blue unit, so you should be able to set the colour for different notifications using a third party app. I haven't tried this yet.
Charging bug - the LED will glow green when the battery is only 90% charged. The iOcean X7S has exactly the same issue.
Text/Font not being visible - if you can't see text in certain apps (Such as Titanium Backup), open the Themes app and switch to the 'System' theme.
Wired Headset - I don't have the official Jiayu Headset but I've tried Samsung and HTC's more recent offerings. The play/pause button on the Samsung headset works, but the volume buttons skip tracks instead. Play/pause works on the HTC headset, as do next/previous track, but fast forward and rewind do not. I haven't tried making calls with them yet. As there are a couple of different standards for four pole 3.5mm headsets that each have the 'ground' and 'microphone' in different positions, you will need to have the right type for the correct functionality.
USB OTG - In addition to flash drives and a small bus powered 80GB hard drive, I've also tried a 1TB WD Passport Ultra formatted to fat32 (also bus powered). Unfortunately the G4S was unable to power it. Some other devices such as a Samsung Galaxy Tab 3 are able to. If you connect the drive to a powered USB hub, then connect the hub to the phone it works fine.
ROM UPDATE 20140422-121442 - For me, the caller ID bug remains To be more exact, if I text someone using the national telephone format (e.g. 07707 123456), when they respond the message is sent with the international dialling prefix (+44 for example) and their SMS will be placed in a different thread.
This ROM uses the same format that original phones imported from China have, i.e. it comes with Baidu IME input as opposed to the one available from Jiayu.es which has the ASOP keyboard. There are a few other differences between the Chinese and Worldwide releases. The kernel and radio etc are the same as the last two releases. I used the ext4_unpacker tool available here on XDA to have a look inside the system.img of the new release and the old release, and I think many of the libs are the same too.
One small bug that seems to be fixed is that call history times in the dialler now displays properly, rather than being obscured by other parts of the dialer.
The volume key wake toggle option in the advanced setting area still does not work (you can't prevent the volume keys from waking the phone).
With most of the themes, the problem where text in some apps is invisible remains the same. Use the 'System' theme to get around this.
USB OTG.....continued - Sadly the CSL DVB-T mini Android TV Stick doesn't work with the G4S out of the box.
FIX - First, turn on superuser/root access in settings/security. Then download Chainfire's USB Host Diagnostics from the Play Store. Run the app, then hit Start Diagnostics. You will be prompted to plug in a USB OTG device. I used a OTG adapter and a memory stick. After the diagnostics have run and you have been asked whether or not you want to upload the results, you will be prompted that USB OTG is not working and that it might benefit from attempting a fix. Let it run the fix and then reboot the phone. The CSL TV dongle will now work
I guess this will probably also help with other USB OTG problems you might encounter.
http://www.amazon.co.uk/CSL-Receiver-Smartphones-Interface-Smartphone/dp/B00DZR3OKS#productDetails
Sample photos courtesy of user ykassana http://mtkforums.com/viewtopic.php?f=5&t=842
Jiayu G4S Original Rom Caller ID Mismatch
Caller ID Mismatch is a common problem in chinese roms, for Jiayu G4S follow these steps:
1. Using root explorer to edit the build.prob file inside /System
add this line at the end of the file
ro.init.phonenumber_match= 7
2. Go to settings >> App >> All >> Contacts Storage >> Clear Data >> Reboot
Good Luck
nightcap79 said:
Caller ID Mismatch is a common problem in chinese roms, for Jiayu G4S follow these steps:
1. Using root explorer to edit the build.prob file inside /System
add this line at the end of the file
ro.init.phonenumber_match= 7
2. Go to settings >> App >> All >> Contacts Storage >> Clear Data >> Reboot
Good Luck
Click to expand...
Click to collapse
Thanks very much for posting. I stumbled on that suggestion a few days ago, but unfortunately it doesn't work on this ROM : (
How come the buttons are not back lighted? I've asked two sellers and they claimed that buttons are back lighted. Are you sure? Maybe there is an option to enable?
Can you make a memory test with AndroBench application?
Thank you for a little review anyway. Keep us up to date with your experience and more observations with this phone.
g4s software issues?
Hi,
I've bought this phone too and I'm facing some issues, http://forum.xda-developers.com/showthread.php?p=52629345
Specifically, incompatibility with the following applications:
Facebook (crash after less than a second of usage)
Firefox (crash after few seconds of usage)
Babbel (crash only after you've logged in, and once you've done it crash as soon as it starts)
google agenda
Have you tried these apps?
Any hint on this thread http://forum.xda-developers.com/showthread.php?p=52629345 ???
Doman said:
How come the buttons are not back lighted? I've asked two sellers and they claimed that buttons are back lighted. Are you sure? Maybe there is an option to enable?
Can you make a memory test with AndroBench application?
Thank you for a little review anyway. Keep us up to date with your experience and more observations with this phone.
Click to expand...
Click to collapse
The buttons definitely aren't backlit on my one. I've no idea if they will be in on examples made later on. I read somewhere that on last year's G4 basic and Advanced models someone found a way to get them to work. I honestly don't know if the hardware is even capable on this year's models.
I'll look into Androbench.
drpete_doyoubnb said:
Hi,
I've bought this phone too and I'm facing some issues, http://forum.xda-developers.com/showthread.php?p=52629345
Specifically, incompatibility with the following applications:
Facebook (crash after less than a second of usage)
Firefox (crash after few seconds of usage)
Babbel (crash only after you've logged in, and once you've done it crash as soon as it starts)
google agenda
Have you tried these apps?
Any hint on this thread http://forum.xda-developers.com/showthread.php?p=52629345 ???
Click to expand...
Click to collapse
Sorry, no, I haven't used any of these apps so I can't give any feedback.
My partial review (in spanish), another bug, and a thankful message
Ouzo said:
Hey everybody. In a blatant and self serving attempt to try and cultivate interest and support in a phone that I have just purchased, I thought I would post a mini review here with a little bit of info
Seriously though, if, like me, XDA is usually your one stop shop for everything phone related and you're considering buying one of the many offerings available directly from China these days, getting the right info can be hard. Sure, some info is available on other sites, but often online translation tools are necessary and it's hard to get a clear picture of what you can really expect from a prospective purchase.
I've been reading about various Chinese devices for over a year now, quietly waiting until I was sure I could get a reasonable level of performance for my money before buying one, all the while nursing my ageing HTC Sensation through daily use. I have a Samsung Galaxy Note 2 as well, but that has a broken screen so it is purely used as a mini media PC connected to a TV these days. I also have an Nvidia Tegra Note that offers great performance at a very reasonable price.
I am uncertain how much waffle you guys will want to wade through so I'll list some basic specs and then provide a few pros and cons as I see them, plus a few very basic tips that I've stumbled on in the first week, some of which will apply to similar devices that use vey similar ROMs. If you want more info, please ask.
Here are the basic specs:
Jiayu G4S -
16GB ROM 2GB RAM - MediaTek Octacore A7 MT6592 SoC @1.7Ghz with Mali 450 GPU.
Dual sim card standby (one Micro SIM Card)
GSM 900/1800MHz
WCDMA 900/2100MHz
Android OS: 4.2.2
4.7 inch, IPS multi points corning Gorilla II OGS touch Screen (I have my doubts about the Gorilla Glass as I have a couple of small scratches already)
Camera: Front camera 3.0 Megapixels. Back camera: 13.0 Megapixels with CMOS flashlight, auto focus
Stereo FM Radio
Gravity Sensor, Proximity Sensor, Light Sensor
3000mAh battery
Dimensions: 133×65×10(mm)
What's in the box:
1 x Phone
1 x Battery
1 x AC Charger Adapter
1 x USB Cable
Pros:
Price - Only £137 delivered to UK via DHL - price is falling all the time at the moment too.
Screen - Pleasing colours, better outdoor visibility than I expected.
Call quality - good, with noise cancellation microphone on rear of device (call quality better than HTC Sensation)
Performance - over 27,000 points in Antutu, nice and fluid in use. Not as quick as Tegra Note or Snapdragon 800 of course
Battery life - over five hours of screen on time in a sixteen hour period, with 37% battery remaining
Build quality - less creaky than my Note 2
Supports USB OTG
Supports USB Mass Storage when connecting to PC
Compact size - at only 65mm wide, one handed use is practical for most people.
GPU performance is not great - only two thirds of the Samsung Galaxy S4, but it's ok for Modern Combat 4
Pre-rooted - Root can be toggled under Settings/Security (love this feature in a stock ROM)
SD card slot
Dual SIM
Removable battery
Cons:
Lack of developer support here on XDA
No MHL for TV out
Caller ID mismatch bug
Camera below expectations - certainly worse than tweaked HTC Sensation camera
Possible wifi bug - affects things like wireless streaming if the screen is off
Deodexing ROM to work with files not 'standard' procedure
GPS - connects quickly but accuracy is still behind Qualcomm's efforts these days (much better than the old HTC Touch Pro/Raphael though!!)
Internal SD only approx. 9GB with phone storage just under a further 4GBs
Screen has some backlight bleeding around bottom edges - sensitivity slightly lower than I'm used to.
Most sites claim 64GB Micro SDXC support - this is wrong, exFAT is not supported so you'll need to format the card to Fat32 for it to work.
English US - if you're in the UK and you change the language to English, you'll be stuck with US English language and location so you'll need to toggle root on in settings and download Morelocales2 from the Play Store and change over to EN GB. I've edited the build.prop too.
Xposed - doesn't work at the moment due to the way the ROM is compiled (if I've understood correctly). Head over to that thread for basic details of a workaround to deodex the ROM.
No 4G
Buttons are not backlit
Recovery, Drivers for PC, Flash tools etc:
Jiayu.es app - Recoveries and tools are available from several sources, but at the time of writing the easiest way now is to download the Jiayu.es app. This now has downloads for the stock recovery, CWM, Stock ROM (European version with ASOP keyboard as opposed to Baidu which comes on the phone if you buy directly from China) as well as drivers for PC and the necessary tools to flash the ROM from a PC.
Mobile Uncle Tools - I used this to flash CWM recovery and tweak a few things before I discovered the Jiayu.es app. You can use this to back up your IMEI (NVRAM) which I highly recommend as the loss of IMEI is something I have read about frequently when people are flashing similar devices.
ROMs:
In addition to the stock ROM in the Jiayu.es app, you can also find a recovery and ROM on http://www.needrom.com/
There are also various ROMs including at least a couple of MIUI here: http://www.592zn.com/
Two Hidden Tweaks in ROM:
1. A limited set of developer options was already available in settings when I first booted my G4S (Stay Awake, USB Debugging, Allow Mock Locations), but if you want access to the whole lot you can repeatedly tap the Android Version section under Settings/About Phone. This will take you straight to the developer options page. By default all animations are turned off so I used this to turn them on. You will still only have access to limited developer options once you exit this page, so you will have to get tapping the next time want to go back into it.
2. An 'Advanced Settings' option in Settings menu will appear if you repeatedly tap the Build Number under Settings/About Phone. This new menu allows you to tweak the transparency separately for lockscreen, main interface and the status bar itself. There's also and option to toggle the volume key wake feature, but this doesn't do anything for me - the volume buttons always wake the phone.
General Blurb:
So far, I feel like my money has been well spent, though I'm only a week into ownership. The screen in particular has exceeded my expectations with pleasant colours and reasonable outdoor visibility (better than HTC Sensation, but not great). Whites look 'white' as opposed to having the slightly yellowy hue that has affected all the devices with AMOLED screens that I've used, not to mention the poor offering on my Tegra Note. There's more backlight bleeding around the edges than I would like though which is a pity. This is certainly not the case with all Chinese devices - the iOcean X7S, for example, has a much better screen from that point of view. Call quality has exceeded my expectations and, as with other similar devices, the firmware offers various ways to manage the dual SIM functionality. As well as binding specific contacts to a particular SIM, you can also independently choose which SIM is used for SMS, voice calls, data and video calls. You can also be prompted to choose which SIM to use on the fly each time if you prefer. Only one SIM can use WCDMA at a time, but you can choose which SIM that is without physically swapping the SIMs or rebooting the phone. I thought battery life might be poor with two SIMs in, especially as I live in a marginal area for one of the networks I use, but so far battery life has been pretty good in general use. I was surprised to get over five hours screen time and still have well over 30% battery left. Intensive games and videos can drain the battery more quickly though of course.
Build quality also appears to be pretty good for a budget device. It's certainly less creaky than my partner's Note, my Note 2 and any other number of Samsung devices that I've used. The petite dimensions are also great. The thickness of 10mm simply isn't an issue for me, especially given the generous battery under the hood. For the first week there were no noises from it at all, though there is a tiny creak from one corner of the battery cover now after many many cycles of removing and replacing it as a result of messing about with it.
The main issues I've faced so far are the fairly weak 13MP camera that introduces a lot of noise and offers poor detail in spite of a wide range of tweaking options within the app itself and a caller ID mismatch bug revolving around MIN_MATCH criteria . The latter means that if you store a contact's telephone number in domestic format (e.g. 07707 123456) then send them a text message, any reply you receive from them will be prefixed with the international country code and will be put into a separate thread. If you store their number with the international dialling code, when they call from the same country, the phone will not recognise their number. So far the easiest bodge is to store both formats for each contact, then remember to send SMS to the number will international prefix. Both these issues are deeply annoying from my perspective. See here for an explanation of the caller ID problem: http://forum.xda-developers.com/showthread.php?t=2268120
There does also appears to be a bug with wifi - if you stream films wirelessly to your TV the screen will have to remain on, which is the first time I've had this issue.
Performance is genuinely fluid if not up to Tegra 4 or Snapdragon 800 standards, but it's certainly better than the Galaxy Note 2. The one area that confuses me is GPU performance. I very briefly had an iOcean X7S which has the same SoC but a 1080p screen rather than the Jiayu's 720p. To my surprise the Jiayu actually scores lower in Antutu in this area. My guess is that either this is a SoC from a different BIN compared to those going into the 1080p devices, or something else is going on to artificially limit performance. On balance, for the money, performance is fantastic and is better than other phones being offered in the UK from retail outlets at over twice the price. Personally I miss some of the features of HTCs Sense based ROMs, but not enough at the moment to shell out over £500. This is now my daily driver and unless it dies prematurely I think I'll have it for up to a year (dependent upon whether or not I get fed up with the camera). Within a year my gut feeling is that similar devices with 4G will be ready for main stream adoption In much the same way that sections of the motorcycling community enjoy having a flagship bike and a small capacity run around to hack, tune and mess around with, I kind of hope more XDA users will start to buy devices like the Jiayu G4S and mess around with them. I know MediaTek have been useless at releasing the source code which is a massive stumbling block, but we can still have a bit of fun with them, eh?
Click to expand...
Click to collapse
Hi Everyone, as this is my first post in this forum, I would like to say thanks to everyone involved for your efforts and good job, focused on helping the Internet Android community.
Second: I would like to thank Ouzo for pointing pros and problems actually ocurring to this model, maybe this helps on finding solution.
Third, i can say than spanish customers are finding problems with hands free during calls: The person at the other side of the line hears his own echo. Maybe it's easy to tune microphones, but still no solution here.
Also have big problems with gps acuracy and position "jumps" while using google navigation in big cities with narrow streets.
Last, i would like to share my review of this model, it's in spanish but you can easily translate it
http://bitsandriffs.blogspot.com.es
Regards.
salimeldjinn said:
Hi Everyone, as this is my first post in this forum, I would like to say thanks to everyone involved for your efforts and good job, focused on helping the Internet Android community.
Second: I would like to thank Ouzo for pointing pros and problems actually ocurring to this model, maybe this helps on finding solution.
Third, i can say than spanish customers are finding problems with hands free during calls: The person at the other side of the line hears his own echo. Maybe it's easy to tune microphones, but still no solution here.
Also have big problems with gps acuracy and position "jumps" while using google navigation in big cities with narrow streets.
Last, i would like to share my review of this model, it's in spanish but you can easily translate it
http://bitsandriffs.blogspot.com.es
Regards.
Click to expand...
Click to collapse
Thanks very much indeed. I'm just updating the first post. GPS accuracy is one of my issues too. It locks quickly but it often gets confused about what road you are on (I use co-pilot), even in fairly open spaces like motorway junctions. This is exactly like Qualcomm devices a few years ago. Have you tried any of the tweaked files available in the Jiayu ES app? I haven't yet, but I will.
I haven't tried hands free calling at all yet, only stereo Bluetooth. Have you tried tweaking any of the values available in the MTK Engineer mode/app? If you are not familiar with it there are various descriptions of what some of the parameters do around here somewhere.
Great review - it's interesting that we're both finding the same issues.
For the camera, I found setting sharpness to Max and turning off the beautification feature helps a little.
Doman said:
How come the buttons are not back lighted? I've asked two sellers and they claimed that buttons are back lighted. Are you sure? Maybe there is an option to enable?
Can you make a memory test with AndroBench application?
Thank you for a little review anyway. Keep us up to date with your experience and more observations with this phone.
Click to expand...
Click to collapse
AndroBench results:
Internal SD card:
Sequential Read - 57.35 mb/s
Sequential Write - 16.83 mb/s
Random Read - 11.97 mb/s
SQLite Insert - 62.03 TPS
SQLite Update - 76.33 TPS
SQLite Delete - 79.68 TPS
Browser - 250 msec
Market - 223.25 msec
Camera - 255 msec
Camcorder - 566.75 msec
Data partition (phone storage) ext4:
Sequential Read - 57.66 mb/s
Sequential Write - 21.33
Random Read - 13.17
Random Write - 0.77
SqLite Insert - 68.04 TPS
SQLite Update - 77.76 TPS
SQLite Delete - 78.61 TPS
Browser - 79 msec
Market - 256 msec
Camera - 135.5 msec
Camcorder - 310.5 msec
From a more real world point of view, when I copy large amounts of data from my MicroSD card to internal memory, it writes large files at about 25 mb per second, and large quantities of smaller files at about 12 mb per second. Not exactly fast.
Software and loudspeaker call issues
Ouzo said:
Sorry, no, I haven't used any of these apps so I can't give any feedback.
Click to expand...
Click to collapse
Yep, I imagine.
I've downloaded and re-installed the ROM provided by Jiayu.es, but the problems persists.
About Facebook: has anyone (or you, Andrés), tried to install it? Does it works smoothly to you or to anybody?
The suspect is simply that some libraries / platform are missing, it could be easily fixed just knowing which ones they are. Please, give a try to install facebook and let me know if it works fine for you, thanks!
Beside that, I can confirm that in Italy too (phone shipped from China) having a call in loudspeaker is giving the problem of echoing on the caller. As well, on this point looking for a solution.
Any hints on any missing libraries (for facebook, google agenda, firefox and other apps not working) and loudspeaker issue are welcome!:fingers-crossed:
Caller ID is fixed in new firmware (available on needrom).
avalanchej said:
Caller ID is fixed in new firmware (available on needrom).
Click to expand...
Click to collapse
Awesome, thanks for the heads up. Hopefully I'll get a chance to try it in the next few days
Updated the first post with some more info/observations
My bad, there is still a problem with Caller ID in SMS app. But when someone calls it's ok.
avalanchej said:
My bad, there is still a problem with Caller ID in SMS app. But when someone calls it's ok.
Click to expand...
Click to collapse
No worries, for a minute I thought the ROM had been compiled differently and the .jar.jex files had gone , then I realised everything is the same. Poop. No Xposed framework for us yet then.
Hi all. Could you please check if your rearspeaker makes noise when you are playing games with low volume or even without sound enabled. The noise is starting and stopping with apps/games that should make sound (also with video players, if you make video sound to silent, speaker still make little noise at my end)
Thanks for checking
Gesendet von meinem JY-G4S mit Tapatalk
but-888- said:
Hi all. Could you please check if your rearspeaker makes noise when you are playing games with low volume or even without sound enabled. The noise is starting and stopping with apps/games that should make sound (also with video players, if you make video sound to silent, speaker still make little noise at my end)
Thanks for checking
Gesende von meinem JY-G4S mit Tapatalk
Click to expand...
Click to collapse
Mine makes a slight hiss before and after a sound. For example, if I have a notification sound that is quiet, the rear speaker hisses for a second or so before playing the notification. If this is what you mean, then yes, I have the same thing. i can't check if this happens when the phone is on silent because I'm in a noisy environment, but I think it does what you describe.
Notifications also sound from the rear speaker when headphones are plugged in which really annoys me too (Samsung devices do this too).
Thanks for the confirmation ouzo. Are you running the stock rom or any other (miui for example). Would like to know if this is software related or if the soundchip is just buggy
Cheers
Gesendet von meinem JY-G4S mit Tapatalk
but-888- said:
Thanks for the confirmation ouzo. Are you running the stock rom or any other (miui for example). Would like to know if this is software related or if the soundchip is just buggy
Cheers
Geseet von meinem JY-G4S mit Tapatalk
Click to expand...
Click to collapse
I'm on the latest stock ROM available from Needrom. I think the same thing happened on the first two stock ROMs. Bear in mind that the kernel has been the same on all three versions, and possibly the various libs too. There are quite a few little bugs throughout the ROM, which is a shame. The biggest issue for me remains the performance of the camera. I'm still enjoying it though : )
hey guys.
i was thinking about my gnex, which is not in use for long time
i got the car kit and was thinking to use it as navigation + music (both full offline usage) without a sim card
maybe with here maps and spotify (i would download stuff at home over wlan)
the question is, what software background would be the best for it - needs to be stable and best compatibility for bt streaming + gps
i have no idea what to use here. maybe some car landscape special rom, if there is something?
plz help me
thx in advance
really nobody with suggestions?
maybe some real light weight rom running very stable and smooth and device stays cold with gps (<- very important)
doesnt matter what android
and some apps e.g. launcher that are very useful for car usage
Well, I might think of an AOSP-like ROM as they are not that "heavy" and I would consider a underclock of the CPU somewhere around 1Ghz because this will make the device run colder. I don't think that this would affect performance as youcare using it only for Spotify and GPS. ROMs I recommend are: 4.2 Stock(one of the best android versions for our GNex) and ShinyROM(AOSP-like KitKat ROM with minor improvements). Hope I helped out
Sent from my RCT6573W23 using XDA Free mobile app
ye this is a good beginning
now maybe some apps which might help as well
like some full landscape launcher **** or what ever. no idea
For car use I recommend Car Dashoid app from Play Store. My dad uses it often and I think it is very useful.
Sent from my RCT6573W23 using XDA Free mobile app