Related
AzusaROM Android Custom ROM Series
Cooked by Coburn64.
>>> Access the Coburn's Domain version of this AzusaROM topic here <<<
What's this?
AzusaROM is a version of Android that is faster, sleeker and breathes new life into your HTC Tattoo. Named after Azusa in the K-ON Anime, the ROM is powered by a custom kernel and has a lot of the bloat removed from it's 1.67.405.6 RUU Update base. Android 1.6 is at the core of the ROM.
AzusaROM is not really intended to be a CyanogenMod for HTC Tattoo. But, you could look at it that way. Please note that AzusaROM will not be based on Android 2.x bases until later on in it's development cycles. While there are 2.1 ROMs for the Tattoo available, they aren't fully completed and/or working.
ROM Status
AzusaROM is currently in public beta. It has been tested and it can be used as a every day-to-day ROM on your HTC Tattoo. Everything works on the v1.04 CoburnKernel, which is version v6.2vanillla. If you have a suggestion or an improvement, please share it and I'll see what I can do.
Current Version: v1.04
Current Version (In-Dev): Unknown
How do I use this?
You will need a HTC Tattoo that has been rooted and has a custom recovery installed. You can find tutorials about rooting the Tattoo and installing custom recovery images in this threads' forum.
Copy the file onto your HTC Tattoo's MicroSD Card, reboot into the custom recovery (I recommend Amon_RA Recovery) and choose "Apply update from ZIP." Select "AzusaROM_v1.XX_Y.zip" (where XX is the version number, and Y is a build timestamp). Watch the screen, AzusaROM will tell you what's going on.
Where do I get help?
I can be either Private Messaged on the Coburn's Domain Message Forums, XDA-Developers, emailed or you can reply to this thread. I prefer either posts in this thread or Coburn's Domain, I have both threads here and at Coburn's Domain under my watch list, which will send out daily emails of new posts in those threads.
Credits
HTC (Making the Tattoo), Optus Australia (best. Australian. Telco. Ever.) ralle.gade (I'm in his debt!), Maxisma (you rock), Benocharm (support), Cyanogen (for CyanogenMod), Donators (for all the coffee), XDA-Developers (rock solid forums, best smartphone dev forums that I've ever been to), and all other developers that I've saved from losing their sanity. And you - for using AzusaROM.
Support The Coburn!
I can't do this without funding. I'm a part-time Android Hacker and I'm also a High School student. By donating, you'll help me get better gear to continue cooking ROMs and making them better. You can always get a Coburn's Domain Plus/Pro Account and support me that way, which in turn also allows you to use Coburn's Domain services.
Can I upgrade my ROM? Eg. AzusaROM v1.01 to v1.03?
In theory, yes, but I've found it will break a few things. Please backup your data and wipe before flashing newer ROMs.
Stuff that Coburn needs to fix/do
Everything works. Yay.
See posts to follow. Space reserved for future use.
Downloads
(OLD) AzusaROM v1.0.07042010 - Not Available (Old Build)
(OLD) AzusaROM v1.01.08042010 - Available (Download Here!)
(OLD) AzusaROM v1.02.27042010 - Not Available/Unstable (See AzusaROM v1.02-1)
(OLD) AzusaROM v1.02-1.28042010 - Available (Download Here! Or Download it here (Mirror)!)
(OLD) AzusaROM v1.02-2.28042010 (UNOFFICAL BUGFIX RELEASE BY TheSSJ) - Available (Download Here!)
(RETIRED) AzusaROM v1.03.13052010 - Available (Download Here!)
(NEW) AzusaROM 1.04.29062010 - Available (Download here)
Changelog
AzusaROM v1.04 "Speed Demon"
Final AzusaROM Release unless a bug crops up.
Camera and Camcorder fully working.
WiFi is working.
BlueTooth works (can sync to my GPS, etc etc).
Busybox installed in /system/xbin
Look in /system/xbin for an easter egg.
AzusaROM v1.03-1 Kernel Update
WiFi now works.
Camera actually takes pictures.
Camcorder works fine.
AzusaROM v1.03 "Red-Hot Fireball Spitting Firecrackers"
CoburnKernel v6 custom kernel
New Theme
Rolled back to working ROM base
Tattoo-hack.ko installed along with wifi.ko in /system/lib/modules
AzusaROM v1.02-2 "Even Coburn makes mistakes..." Bugfix Release 2
Unoffical Build, but boots now!
AzusaROM v1.02-1 "Oh sh*t the kernel spazzed out" Bugfix Release
Fixed Very bad kernel black screen fault on boot - rolled back the kernel.
WiFi broke.
Quick and dirty fixes.
AzusaROM v1.02 "Popcorn"
Very basic firstaid kit script (lol)
Trimmed down the fat.
Scripts in /system/xbin
Kernel has ext4 for backwards compatibility with ext3 and ext2 partitions.
SPEED SPEED SPEED.
Sense UI trashed, replaced with aHome Mini
Most HTC Apps Removed THAT MEANS NO HTC PEEP - SORRY FANS!
"Friday" ringtone is default ringtone
Azusa now greets you at boot (new bootscreen)
AzusaROM v1.01 "Meteor"
Removed some sounds, ringtones, etc
Tested it with swap file, bullet speed!
Uses CoburnROM v1.6 core with boot from miki's ROM
New Boot Screen (Azusa in Maid outfit from K-ON anime)
Dream Theme (from HTC Dream/G1) default ringtone
Flash-proof (no bricks on flash!)
Sense UI enabled by default (may be removed in future releases)
If someone would like to mirror them or make BitTorrent torrents of them, please let me know! (My server gets about 5-10GB just from my Android ROMs, and I have 1TB to fill... )
Screenshots
Taken using my mum's camera.
what are the features and what about app2sd on this rom? :O
I haven't thought of that, I think it would be better if apps where loaded on Internal NAND Flash, faster and more reliable. If there's a lot of need for it, I'll make it available.
I'll love you if you do that
anyway what about the general features of this rom? what are the differences among yours and other roms or the official one?
the tattoo is my first android device
The differences at the moment are just some removal of some stock apps and other tidbits that I tidied up. I also got swap file working, and busybox is installed in /system/xbin.
Coburn64 said:
The differences at the moment are just some removal of some stock apps and other tidbits that I tidied up. I also got swap file working, and busybox is installed in /system/xbin.
Click to expand...
Click to collapse
I actually have a modaco r1 with a2sd but I can stay without it...i partitioned my microsd with the amon-ra recovery in 32mb swap 512 ext3 and then fat32...
do I need to repartition? Do I need the ext3 partition with your rom? what about root access?
I prefer to cook my own ROMs, I don't like to use online kitchens. It's better the trial and error way!
I read you are going to do the update for the swap...why don't you think app2sd is necessary? I don't install more than 10-15 applications but without a2sd my rom was full
Can you give me a rough estimate of what app sizes you were installing? Like Bubble Blast may be 21.04MB. Just a range, like 1MB to 10MB will also do.
EDIT: Added swap instructions to Post #2.
Coburn64 said:
Can you give me a rough estimate of what app sizes you were installing? Like Bubble Blast may be 21.04MB. Just a range, like 1MB to 10MB will also do.
EDIT: Added swap instructions to Post #2.
Click to expand...
Click to collapse
I know that after installing every app I need I tried installing raging thunder 2 (that is really slow on the tattoo) and it told me there were no space enough
I may committ suicide if this appens again
Thanks!!
Downloading it...will post comments after testing..
could you please post some screenshots? it would be really appreciated
Nice to see AzusaROM again.
Suggestion:Add app2sd.
It would be nice.
ambuj said:
Thanks!!
Downloading it...will post comments after testing..
Click to expand...
Click to collapse
Ok..So I have downloaded and installed, boot up without any problem.
However, while doing the initial seeting, it could not connect to my wi-fi router.
I tried for 30 mins, changing this and that, refreshing router but could not succeed.
So, I have reverted back to my old Modaco ROM.
may be this wi-fi is problem for me only.
If someone has done it successfully please post it here.
alberto88a said:
could you please post some screenshots? it would be really appreciated
Click to expand...
Click to collapse
Screenshots will not be of any use as visually there is no difference between stock ROM and Azuas ROM.
Can anyone tells me if AzusaROM is based on stock ROM?
or taken by a vanilla or other ROM?
Thanks.
Thanks
Hello!
I just installed this ROM... it's running fine. But, now I'm not able to get the wireless to work. It detects my network, but it's not connecting
I can see this with logcat:
I/wpa_supplicant( 709): wpa_driver_tista_driver_cmd POWERMODE 0
I/wpa_supplicant( 709): wpa_driver_tista_driver_cmd BTCOEXMODE 2
E/wpa_supplicant( 709): Set_key: Wrong Key
E/wpa_supplicant( 709): Set_key: Wrong Key
E/wpa_supplicant( 709): Set_key: Wrong Key
E/wpa_supplicant( 709): Set_key: Wrong Key
E/wpa_supplicant( 709): Set_key: Wrong Key
I/wpa_supplicant( 709): CTRL-EVENT-STATE-CHANGE id=10 state=8
V/WifiMonitor( 77): Event [CTRL-EVENT-STATE-CHANGE id=10 state=8]
V/WifiStateTracker( 77): Changing supplicant state: COMPLETED ==> DORMANT
D/WifiStateTracker( 77): Deconfiguring interface and stopping DHCP
I/wpa_supplicant( 709): CTRL-EVENT-DISCONNECTED - Disconnect event - remove key
s
E/wpa_supplicant( 709): Set_key: Wrong Key
E/wpa_supplicant( 709): Set_key: Wrong Key
E/wpa_supplicant( 709): Set_key: Wrong Key
E/wpa_supplicant( 709): Set_key: Wrong Key
E/wpa_supplicant( 709): Set_key: Wrong Key
I/wpa_supplicant( 709): CTRL-EVENT-STATE-CHANGE id=-1 state=8
Click to expand...
Click to collapse
How can I solve that?
Thanks anyway for you work ;D
weren't u working
on openeclair 1.3 or latest ?
i thought you could take me to a full working eclair planet
@Above: Yes, I was working on OpenEcliar 1.3, but I decided to roll back to v1.6 to give it some lovin'. For the fun of it, I might even do a cupcake build!
But don't worry, the AzusaROM 2.x series will be using Android 2.x bases.
casidiablo said:
Hello!
I just installed this ROM... it's running fine. But, now I'm not able to get the wireless to work. It detects my network, but it's not connecting
I can see this with logcat:
[..snip..]
How can I solve that?
Thanks anyway for you work ;D
Click to expand...
Click to collapse
Hm, that may be a permissions issue. I'll look into that later - thanks for reminding me.
Glad to hear that everything else works apart from the wifi bug. I'll update the post when I get on my development oven tonight - Gotta update it to Ubuntu 10.04 64bit Beta 2.
Hi
I had the day off, and decided to have a play with the Kitchen to see what I could come up with. After following the instructions on theunlockr.com I decided to base my rom on the OpenFire v.2.3 rom. Any issues that rom had, mine will have.
I have added a few things and changed a couple of things, but in the end, this is my first rom for a device I do not have myself. I have an HTC Desire, but noticed that the Wildfire isn't getting as much love, hence that choice. I hope to get a better understanding of what it takes to make a proper custom rom at some time in the future.
Removed:
Launcher2
Added:
Launcher Pro
Titanium Backup
Rom Manager
Fancy Widget
From the OpenFire v.2.3 post:
NO HTC APPS DO NOT WORK ON THIS ROM AND I WONT TRY TO PORT THEM (but if you try and suceed please tell me and I will maybe include them!)
This ROM is from the android source there is no HTC apps or extra apps from the start it do come with spareparts and dev tools from android source. At the moment it seems a bit slow I think that is due to animations, animations can be turned of in spareparts or in the settings menu.
Features:
- Froyo aosp 2.2.1
- Root + superuser app
- Busybox
- No htc apps!
- Some google apps
- Multi language
- Darktremor Apps2SD
- Patched market
- Usb & WIFI-thetering
- JIT
- 3 in 1 reboot menu
- It may make your phone explode! (You have been warned)
Bugs / Not working:
- Video recording working (but, bad quality)
- Cant import contacts from SIM ? no read/write acess to SIM ? (can anyone confirm or deny this?)
TODO:
- Get rid of above bugs
- HTC-camera (maybe)
Thanks to:
HCDR.Jacob - for the kernel and vendor
Yopsi - for sharing package with google apps.
danne_jo - for APN stuff, and for hosting to my ROM
Sympnotic - For his patched market app
AnantK123 - For pointing out a fix for the camera app
acavella - For hosting / making a homepage dedicated just for OpenFire
Notes:
NO HTC APPS DO NOT WORK ON THIS ROM AND I WONT TRY TO PORT THEM (but if you try and suceed please tell me and I will maybe include them!)
To get app2sd to work you need an ext partition when you have that you might have todo a full wipe and reflash the ROM to get app2sd to work
When you boot up first time choose "com.android.provision"
Anything you want to know about OpenFire can be found at the OpenFire website.
CFH [Wildfire] v1.0 Fault Log
Download:
CFH [Wildfire] v1.0.zip (58 MB)
Due to posting restrictions, I am unable to post links to the Rom. I will post it as soon as possible.
In the mean time, please leave comments below.
Thanks
Chronicfathead
Reserved for future use
Reserved for future use
What did you change? We don't need roms like those. Everyone can customize his installed rom like he wants.
Why don't you stick to a phone you have and help projects that just need help instead of reinventing the wheel over and over again?
no offense, just my personal oppinion
bl1nkk said:
What did you change? We don't need roms like those. Everyone can customize his installed rom like he wants.
Why don't you stick to a phone you have and help projects that just need help instead of reinventing the wheel over and over again?
no offense, just my personal oppinion
Click to expand...
Click to collapse
None taken.
I've had my desire for a while, and decided to root it about a month ago. I have now installed a custom rom, and I'm enjoying the fiddling around. I don't have too much knowledge, apart from experiences gained in the last week or so.
I tried talking a colleague into installing a custom rom, but he said there weren't too many for the Wildfire, so I said I'd have a play. I'm treating it as a learning curve, as I've always been interested in programming, but never really had the time. I have created a (very) small program for the Mac, and have written a few batch files but thats as far as I've taken it.
In an afternoon I've set up a Linux VM, installed all the needed software and had a play to see what I can realistically do. I see this as a first step. I'm trying to talk the wife into a Wildfire so I can have one to play with!
If the consensus is I should delete the thread, then so be it.
Chronicfathead.
AGPS Patch Incredible S 3.1 & 2.2 | GET BACK TO RAPID GPS LOCK, CAN LOCK 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.
i tried the worldwide 1.2 but it didnt change anything, still couldnt get connection on arhd.
fasterfix from the market helped, gps lock-on after about 5sec.
edit: i will try the alternative and report back.
veitograf said:
i tried the worldwide 1.2 but it didnt change anything, still couldnt get connection on arhd.
fasterfix from the market helped, gps lock-on after about 5sec.
edit: i will try the alternative and report back.
Click to expand...
Click to collapse
Did you try v1.3? It's at the top of the post under "Downloads".
crypted said:
Did you try v1.3? It's at the top of the post under "Downloads".
Click to expand...
Click to collapse
1.3 works like a charm
i'm using madmaxx's Recovery, do i still need to perform this step -->
3. Mount /system/ partition (on the main menu, select the "Mounts and storage" option, then "mount /system")
baste07 said:
i'm using madmaxx's Recovery, do i still need to perform this step -->
3. Mount /system/ partition (on the main menu, select the "Mounts and storage" option, then "mount /system")
Click to expand...
Click to collapse
Honestly, mounting should be done automatically. I've left that step in there in case someone had a really old version of CWR installed. After you run through the process, you can open gps.conf and see if it changed on the phone.
crypted said:
Honestly, mounting should be done automatically. I've left that step in there in case someone had a really old version of CWR installed. After you run through the process, you can open gps.conf and see if it changed on the phone.
Click to expand...
Click to collapse
thanks i'll try this out!
I have a weird situation. My IncS doesn't like any kind of optimized gps.conf except the stock one. My IncS was bought in Hong Kong. Whenever I use an optimized gps.conf (including this one), GPS Status shows only 1-3 sats which are located exactly at the far north position and of course it can never get a lock. Resetting AGPS data doesn't help. Once I switch back to stock version, GPS can locate sats and lock normally.
I'm not complaining about my GPS. It's useable but not as stable and quick as my previous Hero. I just don't understand why it doesn't like these new gps.conf file. BTW, the stock gps.conf looks like this:
NTP_SERVER=north-america.pool.ntp.org
XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin
SUPL_HOST=supl.google.com
SUPL_PORT=7276
Click to expand...
Click to collapse
itandy said:
I have a weird situation. My IncS doesn't like any kind of optimized gps.conf except the stock one. My IncS was bought in Hong Kong. Whenever I use an optimized gps.conf (including this one), GPS Status shows only 1-3 sats which are located exactly at the far north position and of course it can never get a lock. Resetting AGPS data doesn't help. Once I switch back to stock version, GPS can locate sats and lock normally.
I'm not complaining about my GPS. It's useable but not as stable and quick as my previous Hero. I just don't understand why it doesn't like these new gps.conf file. BTW, the stock gps.conf looks like this:
Click to expand...
Click to collapse
Yeah, it should not behave like that whatsoever. And, your phone is fully unlocked? What ROM are you using? Do you have the best/recommended radio installed?
Other's have not stated the same problem when testing for the IncS release.
Are you inside or outside? What kind of visibility do you have sky wise?
crypted said:
Yeah, it should not behave like that whatsoever. And, your phone is fully unlocked? What ROM are you using? Do you have the best/recommended radio installed?
Other's have not stated the same problem when testing for the IncS release.
Are you inside or outside? What kind of visibility do you have sky wise?
Click to expand...
Click to collapse
I am really glad you are interested in my problem.
I'm currently using Virtuous Unity 2.37 with latest radio 3805.06.03.16. I've tried other radios before.
When I use GPS Status, I try to stay in open area. It's like my phone thinks all the satellates were in the far north.
Sent from my HTC Incredible S using Tapatalk
itandy said:
I am really glad you are interested in my problem.
I'm currently using Virtuous Unity 2.37 with latest radio 3805.06.03.16. I've tried other radios before.
When I use GPS Status, I try to stay in open area. It's like my phone thinks all the satellates were in the far north.
Sent from my HTC Incredible S using Tapatalk
Click to expand...
Click to collapse
Can you verify that the gps.conf on the device is actually the one I provide? And, do you have a suplrootcert there? If so, open it as a text doc. It will be jibberish but at the top you will see if it's Verisign, Tmobile, or what company. Let me know.
crypted said:
Can you verify that the gps.conf on the device is actually the one I provide? And, do you have a suplrootcert there? If so, open it as a text doc. It will be jibberish but at the top you will see if it's Verisign, Tmobile, or what company. Let me know.
Click to expand...
Click to collapse
Yes, I can confirm your GPS.conf file is there. But I found no /etc/SuplRootCert in my phone. So is it a problem?
Sent from my HTC Incredible S using Tapatalk
itandy said:
Yes, I can confirm your GPS.conf file is there. But I found no /etc/SuplRootCert in my phone. So is it a problem?
Sent from my HTC Incredible S using Tapatalk
Click to expand...
Click to collapse
Nope, shouldn't be an issue. Just was wondering about it.
Could you try with the stock ROM plus the GPS patch? Backup first, test, revert back to your normal setup.
crypted said:
Nope, shouldn't be an issue. Just was wondering about it.
Could you try with the stock ROM plus the GPS patch? Backup first, test, revert back to your normal setup.
Click to expand...
Click to collapse
Restoring back to stock is a huge undertaking. I might try it later. In the meantime, anything else I can try?
Sent from my HTC Incredible S using Tapatalk
itandy said:
Restoring back to stock is a huge undertaking. I might try it later. In the meantime, anything else I can try?
Sent from my HTC Incredible S using Tapatalk
Click to expand...
Click to collapse
I didn't mean literal stock. There normally is a ROM for phones that is just the stock ROM deoxed or whatever. I use ARHD right now. It's available for your phone. Give it a go.
-------
Also,
In preparing for the next iteration of the GPS patch, I'm trying to get a better grasp of the suplrootcert's on various devices. So far I have Verisign and TMobile. If anyone would be willing to check their phone and let me know if they have a different one (via private message here on xda)that would be great!
You can find "suplrootcert" as a file in /etc/ just like where the gps.conf is located.
To see which you have, open it up as a text document. It will look like jibberish. But, the top portion will say a company name within the jibberish. If you don't see Verisign or Tmobile, I would like to get ahold of the one on your device!!!
crypted said:
I didn't mean literal stock. There normally is a ROM for phones that is just the stock ROM deoxed or whatever. I use ARHD right now. It's available for your phone. Give it a go.
Click to expand...
Click to collapse
Oh, before using VU, I was actually using ARHD and had the same problem. Anyway, really appropriate your help.
Sent from my HTC Incredible S using Tapatalk
itandy said:
Oh, before using VU, I was actually using ARHD and had the same problem. Anyway, really appropriate your help.
Click to expand...
Click to collapse
Did it work fine before the patch, though? Can you get a screenshot of GPS Status after running for about 2 minutes?
I'm sorry I can't quickly resolve your phones issue. I'm curious about its hardware and whether it was greatly stable beforehand, or what...
Hi!
Tried the patch 1.3, but no change. It takes about 2-5 mins to get a signal/lock.. I have always had this problem, and it disconnects easily. Donno why..
ROM: ARHD 1.1.7
BWA80 said:
Hi!
Tried the patch 1.3, but no change. It takes about 2-5 mins to get a signal/lock.. I have always had this problem, and it disconnects easily. Donno why..
ROM: ARHD 1.1.7
Click to expand...
Click to collapse
Do you have a case on it? Wifi enabled? Did you let GPS Status sit and run for several minutes? Consider doing this outside with a clear sky view maybe at a park nearby. I know, it's getting cold up in Finland.
crypted said:
Do you have a case on it? Wifi enabled? Did you let GPS Status sit and run for several minutes? Consider doing this outside with a clear sky view maybe at a park nearby. I know, it's getting cold up in Finland.
Click to expand...
Click to collapse
HEHEHE, good one!
Actually anything above 0 celsius is summer for us, how sad is that..
No case, my baby is totally naked. wifi not enabled. I´ll do the GPS status sit and run tomorrow, too dark now and the wolves are howling.
Will report back.
Thanks!!
Hello all,
I've been having some trouble with the kernel in the title, in regards to the settings not applying correctly from the Aroma installer and therefore not on boot. I have to edit the files located at /sys/android_touch/ in order to get the correct settings.
Here's the log:
Sat Jun 22 00:35:53 BST 2013
Max CPU Frequency: 1998000
Powersave bias is
Button Light Notification disabled
Sweep2wake enabled
DoubleTap2Wake disabled
Logo2Wake disabled
Pocket detection enabled
logo2menu disabled
Stock GPU
From the log, these settings are not applying correctly: Sweep2Wake (I want this disabled), Logo2Menu (I want this enabled) and also Stock GPU (it should be overclocked, not stock).
I selected all the settings I wanted during the Aroma installer but they don't get fully applied. The configuration file (located at /etc/elementalx.conf) displays all of the correct settings and has the correct permissions, so does the 99elementalx file (located at /etc/init.d/), yet it still does not apply on boot!
As mentioned, I can edit the files located at /sys/android_touch/ which solves the problem (except for the GPU overclock), but having to do this on every boot is very annoying.
I've read through the thread for the kernel and tried a few suggestions, such as changing the permissions for the /etc/init.d/99elementalx file and disabling the "Write" permission for the files located at /sys/android_touch/, but it's no good.
I'm really pleased with the kernel (except for this issue) and would not like to choose another, so if anyone can offer some help it will be greatly appreciated.
Thanks in advance.
Here are my phone's details:
HTC One M7_UL
Stock ROM + Root
TWRP 2.5 Recovery
ElementalX 1.0.1 Kernel
Android Version 4.1.2
Software No. 1.28.771.6
Shouldn't this be posted on the kernel thread instead?
ArmedandDangerous said:
Shouldn't this be posted on the kernel thread instead?
Click to expand...
Click to collapse
Apparently not, per the rules of this forum:
'Q&A, Help & Troubleshooting
What goes here:
All device/rom/kernel/mods/themes related questions and the corresponding answers
Guides, Collections, Tutorials (can also be posted in General)
What does not go here
see General section'
'Android Development
What goes here:
All discussions related to YOUR OWN development (roms, kernels, recoveries and flashable mods, exact rules for creating a thread there
see in stickies of that section)
What does not go here:
Any Questions!!!'
Plus, I'm still a new member and unable to post in development threads.
UPDATE: I decided to just go ahead and install a custom ROM, so now I'm running the Maximus7 7.0.0 ROM with the ElementalX 1.0.1 kernel and it's great, no problems (yet) and everything is running smoothly.
I also have the Maximus 7 Room and the newest (jul 13th) release of elementalx. Works perfect for me. I have a Tmo One, and I need wifi calling. This setup gives me all the customization and I still get to keep wifi calling working!
Hey guys,
We're back with another update for Remix OS Player version 1.0.110.
Here are the release notes:
__________________________________________________
Remix OS Player version: 1.0.110
Release date: November 15, 2016
Release notes:
1. Incorporated the latest Android Studio (version 2.2) which improves graphics performance significantly
2. Fixed bugs related to keyboard shortcuts and hotkeys
3. Fixed bugs related to keyboard hotkeys in full screen mode
__________________________________________________
Thanks for all your feedback and please remember to sending us feedback here:
http://bit.ly/2cPNq27
Speed
WOW is all I have to say this is the update that was so NEEDED. The speed it runs at is 1000 times better in my opinion. I actually am installing all my apps I use in the emulators I use in windows and making this the primary Windows Emulator for Android. THANK YOU for the AWESOME WORK!!
One thing I notice is the mouse has a slight delay in response. Once that is fixed, this will become my Primary for Android.
UPDATE!!
The Pinch zoom option uses Ctrl-Alt key the same as release mouse from the emulator. This causes a conflict and makes the pinch zoom almost useless. Please Fix.
Internal Storage
How do I get more than 4gb internal storage... the one game I tried to install won't just cause of lack of space.
You and me both. All the apps on my Samsung Galaxy Tab Pro (non-Samsung, of course), I had no trouble installing. Then I tried to install 'Asphalt 7', and I ran out of space.
I want to increase this space to at least 50GB. The procedure to increase internal space for Remix OS for PC will not work with Remix OS Player.
The only offline installer I can find seems to be corrupt & the downloader is giving a server error.
silver9990 said:
The only offline installer I can find seems to be corrupt & the downloader is giving a server error.
Click to expand...
Click to collapse
same here. please someone fix the download server.....
Unable to install
For the past 2 days, the installer gives me an error while trying to downlaod version 1.0.110.
Here is the message I keep getting:
Server Error
Download server experience problem, please try later. (torrent sha1sum check fail)
mohsin_75 said:
same here. please someone fix the download server.....
Click to expand...
Click to collapse
hlo63 said:
For the past 2 days, the installer gives me an error while trying to downlaod version 1.0.110.
Here is the message I keep getting:
Server Error
Download server experience problem, please try later. (torrent sha1sum check fail)
Click to expand...
Click to collapse
Same here, I also get the message,
"Server Error
Download server experience problem, please try later. (torrent sha1sum check fail)"
It's been like this for days as I first tried to download it 4 days ago, would have thought somebody would have noticed and fixed it by now...
@RemixOS_Jason
Are you aware of these downloading problems?
Kaide80 said:
Same here, I also get the message,
"Server Error
Download server experience problem, please try later. (torrent sha1sum check fail)"
It's been like this for days as I first tried to download it 4 days ago, would have thought somebody would have noticed and fixed it by now...
Click to expand...
Click to collapse
I have exact same problem and idk why
me 2 since some days now
I'm just wondering where the support team is, I've spent the last 4 days trying to get support from the various places they tell you to go to for support but there's been no response from anyone.
First question. is REMIX OS better as booted like i installed it or like the new REMIX OS player emulated over windows. Whats the diference in use and fell and for my specs does it matter.
Second question is how to put AT(@) symbol on croatian keyboard.
My specs are
LENOVO Z500
i5 3230m
6gb ram
1tb hdd now and on windows boot 120gb ssd
Gt 740m
Thx hope in fast response.
How to copy - paste a file or folder from pc to remix os player?
because there is many apk that i want to install from the pc.
I'm curious why this update thread was not stickied in the forum? Does that somehow imply it is less important or less stable than previous builds?
Is there any way to enable more resolution options for the player? I'm using it on a SP4 but only very low resolution options are showing up.
Yup, good one ! French android keyboard is back. Can't use all characters and symbol just using my laptop keys, and lots of the non letters keys are mixed up, but looks like you attained the requirement for me to talk around about you Best accessibility is a must have point. Hope it will improve again.
Thought too, as said on the updater's beta thread, I had to download and install manually.
Do we get any other update or this is the end of this app just like leapdroid
RemixOS_Jason said:
Hey guys,
We're back with another update for Remix OS Player version 1.0.110.
Here are the release notes:
__________________________________________________
Remix OS Player version: 1.0.110
Release date: November 15, 2016
Release notes:
1. Incorporated the latest Android Studio (version 2.2) which improves graphics performance significantly
2. Fixed bugs related to keyboard shortcuts and hotkeys
3. Fixed bugs related to keyboard hotkeys in full screen mode
__________________________________________________
Thanks for all your feedback and please remember to sending us feedback here:
http://bit.ly/2cPNq27
Click to expand...
Click to collapse
I still can't get my display out of tablet mode
Crolegion said:
Second question is how to put AT(@) symbol on croatian keyboard.
Click to expand...
Click to collapse
Look it up in an Extended ASCII table. I can use Alt-064 for an @ sign.