Related
I know there's plenty of GPS problems with this phone, but after reading that GPS works in both the roms i've tried, i think im doing something wrong. This is where i'm at:
After using both of these roms on 2 different vibrants, i can't figure out for the life of me why i cant get the GPS to do anything at all on these roms.
I've used ODIN to go back to stock, and then tried flashing the roms but with no luck.
I dont have any clue how to use Angry GPS either, so i haven't messed with that at all. If i need to change some settings within the app, please enlighten me.
Thanks for anyone who helps me with this problem. The only Rom i know of that i have 100% working GPS is with Team Whiskey's Bionix-V 1.3.1.
Anyone? I dont want to be pushy, i just wanna figure out the problem.
And on a side note, i know i posted in the wrong section.
GPS works but it is also a work in progress as no one knows what is really going on with GPS in the Vibrant. The ROM seems to have little effect on weather the GPS works but the "kernel" that underlies it is where the effort is being placed for a fix. While the GPS works on all the kernels it eventually stops working after some time. It is believed to be an issue with how Android starts and stops different services to save power.
Most users have reported great GPS using Kiss 2.2 kernel in combination with either of the Team-Passion Roms (Passion, Euphoria). The most recent kernel is Kiss 8.2. Get it here:http://team-passion.com/index.php/downloads/galaxy-vibrant
For info on each kernel see here: http://team-passion.com/index.php/forum/2-about-team-passion/283-test-kernels
Keep in mind that the developers in my opinion have been working on these ROMS and Kernels like it was their full time job. And they are determined to make GPS work consistently so give them some encouragement to hopefully keep them motivated as they are likely our only hope.
Passion is a faster more responsive but Euphoria has more customizations baked in. The kernels are interchangeable between these ROMs but they have different performance characteristics.
GPS working after deep sleep on Euphoria
After going through 10 ROMs and 20 Kernals I think I may have a semi working GPS. Running Euphoria RC2.1 with stock KB5 modem and gingerbread bootloaders. Installed these gps fixes
http://forum.xda-developers.com/showthread.php?t=1550327
Ran ultimate cleaning script then flashed Glitch then the subzero kernel in the same recovery session
CM9-vibrantmtd-Glitch-V14-B6.zip
cwm-subZero-vibrant-1.1VC_build61-CFS_BLN.zip
Lock immediately after boot with angry gps and phone has deep slept multiple times and gps picks up after granted after 50 seconds
I really appreciate the help guys, the Kiss 8.2 kernel fixed the problem in the Euphoria 2.1 ROM. I get locks within 10 seconds, and also better battery life.
So now as far as im concerned, this is the best combo there is.
droidtomtom said:
Most users have reported great GPS using Kiss 2.2 kernel in combination with either of the Team-Passion Roms (Passion, Euphoria). The most recent kernel is Kiss 8.2. Get it here:http://team-passion.com/index.php/downloads/galaxy-vibrant.
Click to expand...
Click to collapse
8.2 did the trick for me. Locked up in under 20 seconds, and I'm inside my house (by a window) Don't know about deep sleep recovery, but I'll let you know.
You really need to change to Chimera v2.2
On every Jellybean rom, I have calling issues. On some roms, call audio wont work. On the rom I just flashed, it would not make or receive calls all together. Also, this happens only after a certain period of time. And it goes from sporadic occurances to permanent. It takes about a day or two for these issues to start appearing. This is so god damn frustrating because in the beginning the rom works perfectly, I spend all my time setting it up, and then a day or so later, I get these issues that make the phone completely unusable. Its absolutely ridiculous, and If anyone has any ideas, please please let me know. I love the JB roms but they all seem to make my phone unusable after a short time.
Please help....
JB roms are still a work in progress. And your problems could be caused/made worse by your setup (apps, widgets, tweaks, etc...). If you are using different kernels/radio, it can also contribute to problems. There are just too many variables.
My answer : use an ICS rom. ICS roms are alot more stable on our phone right now.
H0rn3t920 said:
On every Jellybean rom, I have calling issues. On some roms, call audio wont work. On the rom I just flashed, it would not make or receive calls all together. Also, this happens only after a certain period of time. And it goes from sporadic occurances to permanent. It takes about a day or two for these issues to start appearing. This is so god damn frustrating because in the beginning the rom works perfectly, I spend all my time setting it up, and then a day or so later, I get these issues that make the phone completely unusable. Its absolutely ridiculous, and If anyone has any ideas, please please let me know. I love the JB roms but they all seem to make my phone unusable after a short time.
Please help....
Click to expand...
Click to collapse
I am observing similar issues. I didn't used to happen before. I mean it did happen but it was a rare thing. But now it is more often. Almost everyday I have to reflash because of loosing phone audio.
I was rocking AOCP 3.1 , Worked really sweet and then decided to update to go for AOCP 4.1 and since then no rom that I tried have saved me. In fact I had to revert back to stock. What rom are you using?
People, it's a known issue on all JB Roms.
Don't open a thread about it.
xaragen said:
I am observing similar issues. I didn't used to happen before. I mean it did happen but it was a rare thing. But now it is more often. Almost everyday I have to reflash because of loosing phone audio.
I was rocking AOCP 3.1 , Worked really sweet and then decided to update to go for AOCP 4.1 and since then no rom that I tried have saved me. In fact I had to revert back to stock. What rom are you using?
Click to expand...
Click to collapse
I have the exact same issue now, It doesnt look like any rom is saving me right now.. my phone wont make calls or receive texts at all. I was running cookies and cream 4.1.2 and everytime i flash a JB rom it just seems to get worse and worse...
EDIT: I got it back on ICS. I guess I will just have to wait to use any JB roms... its unfortunate cause I love the JB roms hahaha
I have had issues with JB as well. I, just like the OP, would experience a perfectly working phone for a day or two then **** would hit the fan for no apparent reason. The phone would start locking up, randomly rebooting, apps would fail or not load, etc etc etc.
On most ROM's I didn't even have anything installed outside of the stock apps that CAME with the ROM.
Since then I have moved to a deoxed stock ICS ROM and honestly am not looking back. ICS is fast, stable, feature packed, and JUST WORKS.
My thing with JB was it's speed...but I was also comparing a barebones JB to the stock Gingerbread that came with the phone. I wasn't aware of how fast ICS was or I would have just gone with it long before hand!
But yeah, either way it goes, for me, no matter the ROM, JB always seemed to mess up at one point or another. Got annoying. Been going with ICS for over a week now with ZERO issues what so ever. No reboots, no crashes, no freezing, no nothing.
NEVERMIND..... ICS worked for one call, and now no calls work... great....
ICS roms are very stable.
You may have flashed your rom/kernel/radio incorrectly, or made some tweaks, or installed incompatible apps... There are too many variables.
Revert back to completely stock setup and see if the problems persist.
H0rn3t920 said:
NEVERMIND..... ICS worked for one call, and now no calls work... great....
Click to expand...
Click to collapse
I'll take a stab, what gapps? Do you use a call blocker of any kind?
Sent from my Samsung-SGH-I717 using xda premium
Same. I think it's the same for a lot of people, and I think the ones who say things run great either ignore the problems or are just extremely lucky.
Switch to Padawan. It's rock solid and you get all the fanciness of jelly bean. Since switching to it I've completely lost the itch to try out random JB ROMs. I have cool animations, Google Now, and ICS Browser+. And until I rebooted earlier to mess with stuff, I was at 142 hours uptime without any problems.
I'm not calling anyone a liar, though. I just think some people ignore more or are, as stated, lucky. I've done wiped everything, went back and wiped stuff post ROM, ran 3rd party (3rd ROM party) kernels and the ones that come with it. I've set cron to fix permissions on boot. And other than gapps -- which I always flash what the dev says to -- I run about ten 3rd party apps, and that's mostly made up of solid apps -- dropbox, exdialer, ics browser+.. etc..
Padawan, or even Nebula.
These ROMs are by the same dev, and the only difference is that Nebula is based off of Canadian version, which has even less bloat. It is better than stock.
I have been on Nebula for about a week, and no random reboots, no lockup, no phone problems. Everything just works.
ddochi11 said:
Padawan, or even Nebula.
These ROMs are by the same dev, and the only difference is that Nebula is based off of Canadian version, which has even less bloat. It is better than stock.
I have been on Nebula for about a week, and no random reboots, no lockup, no phone problems. Everything just works.
Click to expand...
Click to collapse
I like padawan, and Im on it now. But i still am getting this random issue where calls do not go through. Its so aggravating that Im about to smash my phone against the wall. Its happening all the time now and when I need to make a call, I cant. god damnit
have you flashed the most recent modem?
Yes, that was my next question.
Have you at any point flashed a different kernel/radio/modem? If you have, or if you do not know, search for stock kernel/radio/modem and flash them to see if it helps.
yes, uclf6 modem but eventually it just gives out.. idk what the issue is here everything works fine for a few days and out of the blue when I need my phone i cant receive or make calls anymore its INFURIATING
yes, uclf6 modem but eventually it just gives out.. idk what the issue is here everything works fine for a few days and out of the blue when I need my phone i cant receive or make calls anymore its INFURIATING
Revert back to complete stock and see if the issue still exists.
Mobile Network Type
Ltilt2 said:
People, it's a known issue on all JB Roms.
Don't open a thread about it.
Click to expand...
Click to collapse
I have had a similar issue with the JB rom's...so far I've tried only two and seem to find the aokp_quicyatt_jb_milestone-1 rom. I have noticed issues with my phone and LTE network coverage...meaning, I can see the signal go from 4G LTE to 3G to H, then gone...I looked at the phone status settings and noticed the mobile network type with this rom is LTE:13 and with the stock ICS rom (prior to rooting and flashing) it was LTE:14...is there a way that I can change it via terminal? Thank you in advance for any help on this. The one big difference I can see so far is the battery life...much better. Any help is greatly appreciated.
Issues are known....Thread Closed & Thank You.
I searched through some threads and I couldn’t find a definitive answer on this that was recent.
I am currently running ICS Euphoria on my phone, but I recently started having issues with my phone missing calls intermittently. What happens is I will get a voicemail from a call that never came to my phone (no ring, no missed call). Since it has been awhile since ICS was released, I figured this would be a good time to upgrade to JB.
I’m looking for a slim, fast, and functional version. Don’t care about customization, just need a good daily driver. Specifically I’m looking for a ROM with decent GPS (as good as it can be on the vibrant anyway).
What do you guys recommend?
Slim bean, I know the final jb41 build had solid gps, not sure about jb42 beta builds. CM10 stable also hassolid gps.
Sent from my GT-P5113 using xda premium
Slim Bean seems to come highly recommended, but when I looked at it originally the big complaint was no GPS, maybe that has changed?
I have stayed away from CM roms since they seem to be more on the bloated side of things, but offer lots of customization. Really what I'm interested in is a fairly vanilla experience that runs fast and doesn't eat battery like crazy.
There are some flashable files that will help gps, yagf2, experia gps files and gps wrapper. IMO, slim is your best bet.
What you don't know could fill a book.
You can look at the thread I started here with the same Q and my experience: http://forum.xda-developers.com/showthread.php?t=2040685
Bottom line (for me so far) is that NONE will have a working GPS,
and if you do get a gps it will eat your battery with all the Kernel Wakelocks caused by the gps.
Again, this is MY experience, I know others have better exp, would appereciate if you could update what you found...
BTW, on Bionix (Froyo) my GPS worked OK, so I don't think it is my device, but who knows...
Interesting points guys. I have had a few different roms on this phone, and the best gps so far has been ICS euphoria.
I think I'll give slimbean a try. I still need to do the little hardware mod for the GPS as well. Hopefully this will net me somewhat reliable GPS.
I have a copy of PA 2.54-360 with ICS GPS files that jrongi1 sent me. If you would like it you can PM me.
The GPS worked great for me!
And I still got love for the streets..
Gps is tricky with our phones. Each is different it seems. I have an orriginal T959 so I did the harware fix. The hardware fix combined with my use of angrygps.apk. I use "supl.sonyericsson.com" port 7275 in both gps.conf and angrygps.
I dont have DS issues with 4.1 or 4.2 roms. never had.
I installed cm10 and kept the gps.conf that came with it, it looks working OK, not the best signal but that might be phone fault.
Its IMPORTANT to use port 7275 in the supl server and not 7276 as some other posts suggests, the 7276 port was the reason for the kernel wake locks and GPS drain...
Sent from my Nexus 7 using Tapatalk
RemICS-JB v1.0(Team Remics) has good GPS. Doesn't lock as fast at first. Then after few seconds it kick ass. Great rom may I say.
Hi all,
I have an AT&T Galaxy SII (I777) which as everyone knows has the unsupported un-open Exynos4 chipset. I am currently on CM 9.1, which I like and is pretty stable for me.
I've been watching the nightlies in the CM10, CM10.1 and now CM10.2 threads hoping to see some sort of M or RC release. I think at some point, we were close to having an RC, but I guess the decision was changed.
As you might expect, I am looking for a daily driver build that is stable because I don't have as much time now as before to flash on a daily, weekly or even monthly basis, but I would like to get close to the cutting edge of software.
I noticed that AOKP has released jb-mr1 Milestone 1 back in April 2013 for the Samsung Galaxy S2 (i9100 INTL Exynos) (I777 ported by Task650). Then Milestone 2 in July 2013 (with I777 ports). So I am very interested in this.
My question/confusion: How is it possible that somewhat stable (i.e. milestone build) AOKP is available for i9100 when we haven't had anything but nightlies by CM. I thought AOKP is partly based on CM. Have they been able to fix certain things that the CM team couldn't? Or have they decided to have milestone builds despite some known bugs/issues? Can these AOKP builds (and their counterpart I777 ports) be considered daily drivers?
Thanks in advance!
I find most of the roms I have run are suitable for a daily driver. I am a flashaholic. I tend to change my daily driver monthly if not bimonthly. Task's rom is a good one. Of late I have been running Carbon, and it runs pretty well with the included kernel. I have ran Pacrom in the past as a daily, and performed pretty well too. I find with most of the 4.2.2 roms I like the STI kernel for better battery life. I really like the 4.2.2 interface. There is no reason not to try it out. I don't have any issues with any of the features I use on a daily basis ie Bluetooth, wifi, gps, and mobile data all seem to work nicely on the roms I have used. If something starts acting wonky a simple reboot fixes any problems.
Butchr said:
I find most of the roms I have run are suitable for a daily driver. I am a flashaholic. I tend to change my daily driver monthly if not bimonthly. Task's rom is a good one. Of late I have been running Carbon, and it runs pretty well with the included kernel. I have ran Pacrom in the past as a daily, and performed pretty well too. I find with most of the 4.2.2 roms I like the STI kernel for better battery life. I really like the 4.2.2 interface. There is no reason not to try it out. I don't have any issues with any of the features I use on a daily basis ie Bluetooth, wifi, gps, and mobile data all seem to work nicely on the roms I have used. If something starts acting wonky a simple reboot fixes any problems.
Click to expand...
Click to collapse
I agree. I went from task ics to sho stock jb and i can tell that is by far, imo, the most stable rom. But it is 4.1.2, now mr cook has the official att version moded and seems to be good. I've been on pac man for about 4 months now with sti kernel and it's been great. Don't update always to the latest build because nothing is broken for me. I agree with butcher, try it out and you will see.
Sent from the second to last Galaxy
PACman Rom 23.0
STI kernel 2.38
Hi guys,
Thanks a lot for the recommendations.
This past weekend I started by flashing Task650's AOKP ROM. It seemed awesome at first, but then I ran into the following annoying issues which were non-issues with my previous CM 9.1 ROM:
I am unable to turn ring or notification vibrate off even though I uncheck all the boxes I am aware of.
Battery life *feels* worse than CM 9.1. Also, I sometimes get the sudden drop in battery percentage on phone reboot, even though I re-calibrated the battery by discharging and charging it fully.
Voice dialer using Bluetooth doesn't work/ gets stuck at Start up. It also freezes with Google Search. Seems to be a known JB issue so I am very surprised. This functionality is critical as I commute 2 hours and it's safer for me to use the Voice Dialer for calls.
Audio defaults to Bluetooth when I have both my headphone jack and Bluetooth connected. I have to unplug my headphones and plug them again to get the sound re-routed to the headphones. With CM 9.1, it always defaulted to the headphones.
I think I will try PACman next because at least I see it at RC1, which gives an indication of some sort of stability. I hope the above issues are fixed.
As a last resort, I would probably go to Shostock3.
The battery going from somewhere under fifty percent down to the teens on reboot is a known issue for any jellybean rom. I found the battery on Tasks rom not so great as well. Flashing Sti kernel helped mine drastically. Never had all the Bluetooth problems everyone else complains about. I mean sometimes it was a little wonky, but a simple phone reboot always took care of any issue with my Bluetooth. Granted I only use it once a week or so with my LG headset when I mow the grass. I am waiting on Pac to release 4.3 for our phone before I flash back to Pac.
Thanks for your reply, Butchr.
A couple of nights ago was an interesting night for me. I was already on Task's AOKP and I decided to give PAC a shot. After copying the ROM's ZIP to my internal SD card and formatting system, the flash failed because it couldn't identify my phone as an I777. So I had to comment out the first lines of the updater scripts in order to bypass the check. However, I didn't have a way to push the updated ZIP file over to the internal SD card. I tried adb but it didn't work in recovery. Also, USB mounting in recovery doesn't work, at least not with Windows.
After a couple of hours, I wound up having to flash creepyncrawly's rooted 4.0.4 build using Odin. From there, I put PAC. It seemed awesome at first. Unfortunately, it had the exact same problem with Bluetooth that is affecting 4.2.2--bluetooth audio works fine, but bluetooth dialing causes the Voice Dialer or the Google Search to hang up at startup and fail initialization. It would be awesome if this is fixed in the last build, even though it seems like a Jelly Bean issue.
Immediately afterwards, I jumped on SHOstock's 4.1.2 ROM. Here are my thoughts:
- Not a big fan of touchwiz, but it's a little better than the Gingerbread days.
- I also don't like the notification panel because it's just packed with things, not leaving enough space for the actual notification. Could be a little more compact. Even after removing the brightness adjustment section. Cannot get rid of all the quick settings buttons.
- Another thing was when I downloaded Google maps, it always force-closed when attempting to start navigation. I had to uninstall it and download the APK for the latest version of Google Maps (with the interface changes). That worked fine.
- GPS locks very quickly.
- Battery life is awesome.
- No Bluetooth dialing issue. Had to use Google Search because Voice Dialer is not packaged in it.
- There is a known issue with notification sounds sometimes getting cut off. My first alarm this morning got cut off very quickly that I didn't wake up, but the first snooze alarm was fine, and that's when I woke up (10 minutes late).
I am interested in PAC if the bluetooth problem is fixed.
I'm trying to figure out what the most stable and functional ROM is for my MDK VZW S4. I've tried to research this several times but I find that I have to essentially read through every thread for every ROM, and even then there are things that are left out. My previous phone was a Galaxy Nexus, so I was probably spoiled by the wealth of information about the various ROMs, but there's no reason we can't have a thread like this.
History of my ROM usage with my S4
I started out with Hyperdrive ROMs but later decided I just couldn't deal with TW no matter how much work the Hyperdrive guys did try to clean it up (kudos to them for the best ROM for people stuck with a locked bootloader though!).
Next up I went to Gummy ROM to try out 4.4, which honestly hasn't really impressed me. My GPS never works right, seemingly related to the compass problem? Not sure here, but this is a major deal breaker for me.
Problems I've had and seen mentioned in multiple threads; are these fixed in ANY ROM???
The above mentioned compass problems. I've read about factory calibration issues, I'm going to try a few of those fixes, but I also see a LOT of people saying this is a driver issue? Which is it?
HDR camera doesn't work, attempting to use it just makes solid black pics.
Bluetooth audio playback problems. I've heard this mentioned many times, but haven't had a chance to test myself. This only becomes a big deal for me in the summer when I'm using this feature to stream music to the stereo on my boat.
Thanks!
Dan