Question #1: GPS
I have the Samsung Galaxy S 4G which has been long rooted and I've installed a few roms now on it. Recently I upgraded to Revolt 4+ which is my first attempt to find a Jelly Bean ROM that will work for me. Well, I love it. Only problem is that it seems it doesn't have GPS? Google Maps work but Navigation doesn't follow me which I'm guessing means it's using internet to "find" me. There's no GPS flashing icons nor are there any settings for GPS. Is there anyway to get it working or is it just not working for this ROM?
Question #2: Aries?!
Many of the roms mention "Aries's common bugs" but google searching it gives me nothing. Where can I find information about Aries?
Question #3: The latest fully-working ROM?
There are soooo many ROMs to choose from for the SGS4G that I don't know what to look for. I found and have been using THIS page but not sure how outdated/accurate it is. Anybody know the best/most recommended ROM right now that has all the main parts working? GPS, WIFI...etc? I know wifi calling always has issues but not important.
:good: to anybody who is able to help with any of the above!
Hi.
#1 All JB ROMs (meaning 4.1.2 and above) have Aries kernel.
it is faster than Herrig kernel used before, and should be more stable, but, no developer was able to make GPS work with it. so, there's currently no JB ROM with a working GPS.
#2 If you want a working GPS you will need ICS (4.0.3/4.0.4) ROM :
CM9/AOKP/Slim/MIUI/Ultragen etc.
I'm a MIUI freak so I can say I love HebMIUI which is an upgraded MIUI version I came up with. you can try it (see my signature) or any of the others I mentioned.
Slight addendum to #1. Not entirely true. Some of the earlier JB ROMs were still Herring. The various 4.2 Wifi-bugs were on Herring. Any ROM where they tell you to do the 4.1.2 JB if you wanted Wifi, it's a Herring kernel. For that matter, I believe we've only had compiled 4.2.2 and above Aries here. So if the ROM is 4.1.2 JB, it's Herring. If it's 4.2.2 without working Wifi, it's probably Herring. If it's 4.2.2 with Wifi or 4.3, it's probably Aries.
Agree on ICS/GB for GPS though. HebMIUI or Ultragen 1.01 (DO NOT USE ULTRAGEN 1.00 AND POST BUG REPORTS) are probably your best ICS options.
THANK YOU both for clearing up alot of stuff for me. Thank you x2 for itzik2sh for recommending HebMIUI. I have it installed and I love it sofar. Hopefully somebody figures out JB GPS eventually.
I'll still check back here if anybody else has anything else to throw in.
Related
Hi,
I'll be getting my brand new Xoom Wifi (EU) next week. Now that there's an ICS rom with camera and hdmi, I want to upgrade to ICS. I have some experience with rooting/flashing the Hannspree Hannspad but just to be sure. The steps to go from stock to Team Eos Wifi Nightlie (wingray/MZ604):
- root
- install clockworkmod
- flash zip from sd
Is this correct ?
Thanks
piotrusc said:
Hi,
- root
- install clockworkmod
- Nandroid backup
- Titanium backup
- Factory reset
- flash zip from sd
- Flash Gapps
- Restore your apps via TB ( without data )
Is this correct ?
Thanks
Click to expand...
Click to collapse
I am about 90% sure that's correct. Not feeling to well right now and its been a while since I flashed from stock. I am sure someone will correct me if necessary.
mobileweasel said:
I am about 90% sure that's correct. Not feeling to well right now and its been a while since I flashed from stock. I am sure someone will correct me if necessary.
Click to expand...
Click to collapse
You can use the guide, below. I recommend that you read the 1st post thoroughly and at least read the last several pages as they may be somewhat relevant to your situation.
http://forum.xda-developers.com/showthread.php?t=1249798
Thanks for pointing me in the right direction !
Don't upgrade to any ics rom if you are planing to test drive or daily use the Xoom. You will not be able to play games that have 3d. Only native apps will work (some). I think its the build and not that its a new OS...but its a nightly so you can't complain. I'm going to relock my Xoom and wait for the official release. There is no real point in using a custom rom if you are at the newest OS and the horse power is great for gaming and working. There are plenty of apps that will give you customization without root. Overclocking is not that notorious but will drain the baterry faster so there is no gain. ICS looks awesome and devs are really genious but I think the rom will not be useful until the official update comes out.
I'm coming from the Hannspree Hannspad and on that tablet I've used all kinds of roms (different Honeycomb flavors). I'm not sure I understand what you mean here. From what I've read in the forums the current build is a fully functional ICS rom. Can someone shed a light on this ?
Games or apps that require 3d doesn't work. Even soul craft that is a ics compatible game. So its not ics ...its the rom. I'm not complaining its a nightly but people saying its a functional build...well it is if you stay with the stock apps and native made apps. But for me its not. List of apps that doesn't work that I use. AutoCAD,Photoshop, gta3 , every gameloft , dead space.... some other apps work but sometimes fc or refuse to open and have to reboot. Some will say its not the rom but devs not upgrading theyr apps for ics but I have seen games working and then not in every ics build. So there's that.
Most of the application works. gameloft's game is not working currently.
I m nw on teameos aosp build29 n i m very satisfy with this rom. It is extremely smooth n fast. camera is working now too.
piotrusc said:
I'm coming from the Hannspree Hannspad and on that tablet I've used all kinds of roms (different Honeycomb flavors). I'm not sure I understand what you mean here. From what I've read in the forums the current build is a fully functional ICS rom. Can someone shed a light on this ?
Click to expand...
Click to collapse
Actually the nightly builds are quite functional for daily drivers. It depends on what you do with your Xoom. I'm not that much of a gamer, so I don't care much about that. Photoshop Touch works fine, but can't connect with Creative cloud (at least a few builds ago when I tried), most everything else works fine. Not all apps have made the changes needed for compatibility with ICS yet, so not really an Eos ICS Nightly problem.
All went smooth. Running ICS now! Heaven. Thanks a lot!
Edit: should cifs work out of the box? Using cifs manager but cannot mount shares
Edit 2: When upgrading to a new nightly: just wipe cache & flash zip ? (sorry can't post in the correct forum yet).
Since I am a newbe I can't post in the dev fourms so I will ask my question here. I sucessfully installed [DEV][CRACKFLASHERS] 4.1 Jelly Bean JRN84D (Gnex)/ JRN84C (SDK) with the WIFI update-crespo-JRN83C-preview-2012063001 but no audio is there a workaround a driver perhaps anything, I like this rom it's super fast on my Nexus S
Chris
This wouldn't belong in development anyway (starting new threads in development is for DEVS ONLY) so it's good you couldn't post there.
If you want everything working you should stay away from SDK ports. It's not what you want to hear but it's the truth. There is no source code to work from so they are often very wonky.
No, there is no audio. You have installed the latest port.
There will not be any audio fix for the port. We will have to wait for the Update from Google.
Sent from my Nexus S using xda premium
You should have read and asked around before flashing this ROM, as the previous users said and I would like to re-inforce this; SDK ROMs lack a lot of things and are not stable at all. They are not recommended, and they are basically good for previews and stuffing around.
If you really want the new Jelly Bean 4.1, then just wait a week or 2 and a stable version will come out, a custom ROM too.
If you want to revert back to a Custom ROM for now I suggest you use AOKP. It's very stable, reliable and easy to use. Make sure you don't flash a Stock ROM as this can cause problems.
Cheers
From what ive seen there is not audio yet. Devs are working hard to get it out and i appreciate it very much. :laugh:
Hello,
I currently use the official 4.1.2 unrooted on my Wingray. I want now to overclock my Xoom, and if I understood well, I need to change my kernel.
So I checked the CM10 nighly thread and I saw there many people reporting problems with the Play store reporting softwares incompatibilities ...
Is this incompatibility problem only on Stingray or also on Wingray ?
Is the CM10.1 out for the Xoom and does it still have market incompatibility issue ?
Where can I get the CM10 (or 10.1) STABLE version ? I could only find the nightly release on XDA.
I am also interested in feedbacks from people gone from official 4.1.2 to CM10 release, I am very concerned by 2D fluidity (I don't care about 3D games) and I would like to know if CM10 when overclocked shows real fluidity improvements.
Thanks !
Here is a link to a cm10 stable build. Zig has done quite a bit of cool work to it. Cm10 had a few issues I didn't like. I got the actual cm10 ROM from goo manager and the main issues I had were no lock screen flip and volume controls don't flip with tablet. Check it out if you like.
http://www.xoomforums.com/forum/jelly-bean-development/18982-rom-kang-cm10-wingray-zigackly.html
Words fails me. I am so disgusted I have ran out of expletives so I won't bother repeating them here. Seriously...voice dialer is STILL not working! This update was specifically designed to fix this bug and it is still not working. I just can't understand what is so hard about putting back in functionality that was working before in ICS and was necessary.
This is the sort of thing that gets people to switch over irrevocably to apple. This has been going on for like a year now. It is starting to feel like it is being done on purpose for God knows what reason. Does it work for anyone else?
android 4.2.2
i535VRBLK3
AOKP
What update? This phone is officially on 4.1.1 . You are not guaranteed anything by running custom software.
BattsNotIncld said:
What update? This phone is officially on 4.1.1 . You are not guaranteed anything by running custom software.
Click to expand...
Click to collapse
Fair enough. Although I never said I was guaranteed anything and apparently we are also not guaranteed to have important functionality (aka voice dialer) to work from one official release to the next. It worked fine when I had ICS it just broke when I was upgraded to JB. I would prefer not to have to root my phone to get it work, but if I waited for the official channels then I will likely have to wait until I get my next phone for a fix.
Both Google and AOKP mentioned that bluetooth issues were fixed with 4.2.2 and I was inquiring whether this worked for others as it did not work for me. Neither 4.1.1, nor 4.1.2 nor 4.2.1 nor 4.2.2 nor any of the other little hacks others have tried have worked and I know others on the official release of 4.2.2 for Nexus had similar problems so I was hoping someone might have run across a solution.
I know I sounded snarky, but I am just really frustrated.
So I do not know if this will help you but I had pacman rom and the dialer wasn't working so I reflashed, no wiping and it fixed it.
Also there is always the option of going back to the stable TW roms. Which is what I did. You can't be mad for things not running smooth when you're running custom roms that make no claims of stability.
Via my S3 CleanRom 5.6
CM-Freak said:
So I do not know if this will help you but I had pacman rom and the dialer wasn't working so I reflashed, no wiping and it fixed it.
Also there is always the option of going back to the stable TW roms. Which is what I did. You can't be mad for things not running smooth when you're running custom roms that make no claims of stability.
Via my S3 CleanRom 5.6
Click to expand...
Click to collapse
Thanks for the info, it was definitely worth a try. Alas the pacman rom did not do the trick. I had the official JB TW update and that is what broke my phone in the first place and I am not really interested in going back to ICS since I got the new phone so I can get Jelly Bean. I have also tried CleamROM and the the latest CM, AOKP and liquidSmooth 4.2.2 along with the just released gapps-jb-130301-signed.zip. No dice.
I'll keep banging away and let everyone know if I find a solution with other ROMs or tweaks.
I am not mad about custom ROMs not working properly I am mad about the official release breaking critical functionality for me.
I tried PK and PA ROMs in addition to aready mentioned. Voice dial does not work in any of them. I also tried Ktoonsez kernel - no dice. I think it's a major JB problem and there won't be any working ROM until Google fixes the issue. I just stopped trying :crying: ...
I am getting the itch to put on a custom ROM of my GS3, but I have a Fitbit One and would like for it to continue to update over the phone. I've tried CM10.1, but it appears that there is a problem with the BT4.0 and the phone doesn't want to try to connect to the fitbit. I'm not close to a computer much currently to update the fitbit.
TL: DR- Is there a working ROM where the BT4.0/BLE is working somewhat properly?
Thanks in advance.
I'm looking for the same thing. I switched back to a Stock variant to get BT4 working and the Stock ROM is total garbage after using Cyanogen Mod. I don't want to have to choose one or the other!
There is not a single ROM out there at the moment that has Bluetooth 4.0 working. Google has not released or included a lib file for it to work. Sure our devices have the hardware but the software has no clue how to utilize it. Maybe next version of android will have it.
The 4.1.2 Omega ROM was working for me. The ROM will need to be based off of Samsung's official as it will need their hacked Bluetooth stack - they worked directly wth Fitbit to get it up and running. I've since upgraded to the Omega 4.2.2 AOKP ROM and it no longer works (which I expected).
BLE
The only ROM that i've found with working BT4/BLE is the one by beanstown.. i do confirm it working just fine for my fitbit flex.
http://forum.xda-developers.com/showthread.php?t=1973982
I have a fitbit as well and I am trying to figure out what it would take to get it working with CyanogenMod. I flashed an unofficial 10.2 (4.3) and still no luck with the fitbit.
try the 4.3 version of CM in teh development section? I thought this was an added or fixed feature in teh newest version of android. not too sure though.