Okay, I have done the following things:
1. I have soldered the connection inside the phone. (Yes very nicely I might add as I solder a lot at work.)
2. I have the Sub-Zero build 75 kernel.
3. I am using Slim ICS Rom from the android development forum.
Why in the hell does the GPS lock on instantly sometimes, and other times I have to restart the phone 20 times before it will even thinking about locking on again?
What is wrong with this phone's GPS? What else can I do to get this GPS to work all the time. The programs that "clear the GPS data" or the phone code that does it, does not work. There is no message and no sign that it cleared anything. The "secret code" program just crashes of course, when I try to use the GPS clear data.
Is there anything else I can do, besides throwing this phone against the wall. I actually NEED the GPS sometimes because I travel a lot, and I can't even rely on this phone.
Here is how I understand this:
Since we never got an official release for gingerbread we won't be getting one for ICS either. The problem is that all releases for our phone for GB+ are hacked together from the source released for the other phones in the Galaxy S family. Also, since the actual guts are slightly different between models, we don't have the actual Samsung drivers for these releases on our phone.
Another problem is that the GPS chip they used on this phone sucked and was sub par at best when released. Most vibrant owners had issues.
The only way to guarantee the best GPS performance on this phone is to stick with the stock Froyo firmware. Everything else is hit or miss since we got the step child phone off the Galaxy S family.
I was lucky enough to buy my vibrant several months after release, so my GPS was revised by then and better than the release models, but it still flakes out on custom ROMs sometimes.
For now, I am on Slim 3.5, and sub zero 80 kernel.
-------------
GlobeSpy detailed this in his post here:
http://forum.xda-developers.com/showthread.php?t=1550327
-------------
I flashed the yags and experia GPS fixes, made sure to install angryGPS and faster fix.
Angry GPS settings changed to MSBASED, cold start, and Xtra=off.
In supl settings, I selected Google server.
In Fasterfix: selected custom and set to us.pool.ntp.org
After rebooting the phone, open GPS test and let it lock birds.
After that, I can exit out of GPS test and run navigation. GPS will lock later in day too.
The same settings worked on the stock slim kernel to, so sub zero isn't a requirement, but I have made it work on both kernels. In my expewrience the stock Slim kernel worked better for GPS.
Hopefully this helps, but each phone is so different, the results are not guaranteed.
It really is too bad that Samsung dropped the ball on the GPS in this phone. It's the only weak bit of the device.
Sent from my SGH-T959 using xda premium
So what are the pros and cons.... I know about the partition. Are they any other issues with the conversion? If you came back from N4 what made you come back? Cos after the SD card, NFC and LTE fix what else was broken? Thanks in advance.
Googler_1976 said:
So what are the pros and cons.... I know about the partition. Are they any other issues with the conversion? If you came back from N4 what made you come back? Cos after the SD card, NFC and LTE fix what else was broken? Thanks in advance.
Click to expand...
Click to collapse
My main reason for doing the conversion was to get hybrid ROMs like Rootbox or PACman (which weren't available natively on LGOG at the time). To me, really the only pro is a larger selection of ROMs. This isn't necesarily a better selection, just bigger - it depends on what you are specifically looking for in a ROM as to whether this makes it worth it or not.
With the available fixes already posted, there really aren't any huge cons either - GPS works, camera works, you get full internal storage and external SD support. However, there were cases I ran across where I couldn't get certain fixes working with certain ROMs - things like touch key lights not working and the like. I'm sure they are fixable in these cases, it just takes someone smarter than me to figure out how.
I think the main reason the conversion is frowned upon is that there isn't a compelling, across-all-ROMs improvement or feature that would be available on a converted device that isn't available on the 'native' track. So why risk a brick monkeying with partition layouts and potentially dangerous N4 install scripts (apparently some of them flash using partition numbers rather than names, and this will kill ya dead - gotta read carefully. I never ran across one).
I had minimal issues when running converted ( I think I was running that way for 3 weeks or so maybe?? Can't remember). Most of the issues were things that were more annoyances, rather than real usage problems. However, as my main reason for converting was to get a hybrid ROM, once houstonn brought Rootbox to the LGOG natively, I decided to come back. I'm usually a little short on time, and it was getting difficult to keep up with all the LGOG threads, plus all the N4 ROM threads, plus figuring out how to fix the ROMs for use on the LGOG. It's easy here, a one stop shop for LGOG learning, if you will...
I suspect with the native 4.2.2 stuff running around here now, there will be a steady decrease in the amount of 'development' on conversion stuff - it seems quite a bit quieter now than it was a month or 2 ago. I'd rather stay where the action is, as that's usually where the little remaining issues get solved first.
FWIW, I had no issues either converting to, or back from, N4. The threads here do a good job of spelling out the process - it's just a matter of reading through them enough times to understand what is going on and what to expect at each step.
Thanks for writing up your experience... The main reason I asked this question was... Some of the (if not all of them) AOSP Roms have major issues like if GPS works something else will be broken and if something else worksworks other is broken. But I did not see that in N4 conversion. (At least to my knowledge) I'm just talking about just pure aosp Roms. ..is this a trurt statement I'm making? Thanks in advance.
Googler_1976 said:
Thanks for writing up your experience... The main reason I asked this question was... Some of the (if not all of them) AOSP Roms have major issues like if GPS works something else will be broken and if something else worksworks other is broken. But I did not see that in N4 conversion. (At least to my knowledge) I'm just talking about just pure aosp Roms. ..is this a trurt statement I'm making? Thanks in advance.
Click to expand...
Click to collapse
I can't say for certain - most of these 'tradeoff' issues, at least from what I've seen, seem to revolve around which modem you choose to run. I believe, at the moment the only 100% no issue setup is and ICS ROM with ICS modem. I believe these issues persist whether you are on N4 conversion or native LGOG setup - but I could be wrong here.
Here's the basic breakdown - somebody correct me if I'm wrong on these, I haven't run most of these setups personally:
If you run ICS modem on JB ROM, you get broken GPS.
If you run .33 N4 modem you get good GPS and Data speeds, but occasional data drops. Also, apparently you can't make outgoing calls in LTE coverage. You can fix the data connection by toggling airplane mode. This isn't a huge issue for most people, but is for me as I use Google voice and IM apps for messaging (rather than SMS) so if I don't notice the data drop and toggle, I'm missing messages.
If you run ATT JB modem on JB ROMs you get working GPS, decent data speed, and working LTE calling. All Outgoing calls drop to a background process after initiation, so if after hitting dial you need to interact with the call, you have to open the notification drawer and then click on the call to foreground it. Does not impact actual functioning of the call. Network name is reported as 'maritime' rather than AT&T.
I think there's another N4 modem that will work with LTE (.27 maybe - somebody jump in here) so that might be another option...I haven't tried it. there is one N4 modem that breaks LTE support.
I've been almost exclusively on houstonn's RootBox since coming back to native setup - so I may have missed issues with other ROMs - I do try to keep up with all the threads though. Hopefully someone else on one of the others can chime in with other issues, if there are any, that I missed. FWIW, I have never lost GPS on my device...I'm not sure why some have and some haven't...
http://forum.xda-developers.com/showthread.php?t=2270319
One stop shopping for all your radio needs.
Thanks again both of you... t I wanted to know why and I think I got what I was looking for.. Anyway, I guess I will stick with my rooted stock JB for now till some of these issues get resolved. Thanks again for all your time.
my wife and I both have i777's, and I keep them rom'd similarly always, although I do a lot more experimenting with my own.
I recently found a few behavioral differences inbetween hers and mine, even though the most recent installs were after rom-wipe scripts, and TiBU restoraton of user apps only.
when I nfc-beam photos to hers, hers does not ask any permission, and the beam always completes successfully.
when I nfc-beam from hers to mine, It starts, then I am asked permission, and it fails after I grant permission.
the issue occurs whether we are on the same (cm) or different kernels
The only thing that I truly recall doing grossly differently with mine, is that I tried out a 4.3 rom recently, and then went back to cm10.1.3.
Once I noticed the issue, and couldn't correct it with a cleaning and re-rom, I even Odined back to stock, then started the whole process over, but still the NFC-beam/bluetooth issue remains.
currently we are on cm10.1.3 stable, I've googled the hell out of it, but others' issues don't seem to be the same, and their resolutions didn't help me.
any ideas?
Sorry, cyril, like you I've never heard of this. The best I can do is offer a few thoughts...
- The first culprit would be the CM nighty you're both running. Has your NFC problem always existed, or just since you installed CM?
- Do you both have the same battery, or is one different than the other? Specifically, are they OEM?
- Do you have anything remotely related to NFC turned off via autostart or something similar?
As you can see these are all guesses, hopefully whatever trouble you're having will correct itself.
Sent from the i777
I don't mess with cm nightlies at all; we both went from 10.1.3 rc2 to stable. I didn't notice when the issue began, because I really don't use the feature very often, and didn't even try it until installing cm.
Same battery? No clue, I haven't replaced them, I expect that they're OEM, but I'll pop them from their cases later to verify.
Nfc feature Turned off? I'm not sufficiently android savvy to have done anything intentionally, but I'll look up "android autostart" and see where it leads me...
No, don't worry about the autostart. I was referring to using a 3rd party app to control what starts up at boot; there's no way that's the cause if you're not familiar with what I was suggesting, because it's something you have to do manually.
Sent from the i777
I'm thinking of picking up a G3, but want to make sure that there's quality software to back up my hardware purchase. Are there any good Roms (or rom/kernel combinations) that anyone can recommend wherein everything pretty much works (including LTE data and USB/WiFi tether) and the artificial sharpness bug can be disabled? Marshmallow-based is preferred as I want to be able to flash one Rom and never have to worry about it again for at least a couple of years. Stock-based isn't a requirement, but it is preferable, as CM-based roms are usually lacking on hardware-specific features and optimizations.
Word on the street is that Fulmics Rom is the go-to for this criteria, but I heard somewhere between XDA and Reddit that versions 4.1 and 4.2 were the last version of Fulmics rom with properly working data for Verizon. Can anyone back this theory up?
I'm running the latest CM13 nightly build 08/02/16 and so far it seems to have fixed all issues I've had previously. Tethering and all that works, actually using foxfi tether from the phone to my tablet right now.
I have have this same question. I've been out I'd the loop for a bit with work being crazy. I am definitely looking for a good daily driver also.
Sent from my LG-VS985 using Tapatalk
@xdabbeb 's stock rooted 47A firmware with the debloat zips in the third post and if you have unlimited data, use his tethering mod in another thread either in Development or Original Development.
Sound and Vision
Nonanza said:
I'm running the latest CM13 nightly build 08/02/16 and so far it seems to have fixed all issues I've had previously. Tethering and all that works, actually using foxfi tether from the phone to my tablet right now.
Click to expand...
Click to collapse
So stock Android doesn't actually have WiFi tethering built in? Or do you just prefer Foxfi over it because of the features and functionality offered? I'm open to trying a CM or CM-based Rom as long as everything works. Now do you have access to any of the equalizer settings with that (like Viper audio) or does it require a special kernel? How is the volume level on voice calls?
roirraW "edor" ehT said:
@xdabbeb 's stock rooted 47A firmware with the debloat zips in the third post and if you have unlimited data, use his tethering mod in another thread either in Development or Original Development.
Click to expand...
Click to collapse
If I go with the G3, that'll definitely be one to try also as long as tethering works with StraightTalk.
How's the situation with audio enhancements on that Rom (Viper audio or similar) or does that require a special kernel? Is volume on calls through the device's earpiece loud enough?
Bill720 said:
If I go with the G3, that'll definitely be one to try also as long as tethering works with StraightTalk.
How's the situation with audio enhancements on that Rom (Viper audio or similar) or does that require a special kernel? Is volume on calls through the device's earpiece loud enough?
Click to expand...
Click to collapse
I don't know if the built-in (or modded) tethering will work with any other carrier besides Verizon - I seem to recall some people saying it complains that it's not provisioned for it. I'm on Verizon, so can't speak from personal experience but you'd likely have to use something third party. I also don't know for sure if people only have a problem tethering on non-Verizon if they apply the modded tethering, so try it without using the mod, and then if it doesn't work, make a TWRP backup and try with @xdabbeb 's mod.
I haven't fooled with audio mods in a long time so I can't comment on that - I know some people have used Viper and/or others on his ROMs - search his thread for "viper" and you'll probably find something. I think everything on this phone is loud to very loud depending on which channel.
Note that one feature you definitely won't have on non-stock ROMs is the laser focus of the camera. No other app can work it. The camera will work, but it won't be as good. I used to dabble with CM but for my own use, it's too much trouble so I haven't fooled with it in a year or a year and a half, except on my LG G Pad 8.3, which stopped OTAs at Android 5.0.2 and it's too sluggish with it even when debloated.
Range finding
roirraW "edor" ehT said:
I don't know if the built-in (or modded) tethering will work with any other carrier besides Verizon - I seem to recall some people saying it complains that it's not provisioned for it. I'm on Verizon, so can't speak from personal experience but you'd likely have to use something third party. I also don't know for sure if people only have a problem tethering on non-Verizon if they apply the modded tethering, so try it without using the mod, and then if it doesn't work, make a TWRP backup and try with @xdabbeb 's mod.
Click to expand...
Click to collapse
I guess we'll just have to hope for the best when the time comes. My "upgrade season" isn't going to be until early next year at earliest, but I do want to be fully prepared.
roirraW "edor" ehT said:
I haven't fooled with audio mods in a long time so I can't comment on that - I know some people have used Viper and/or others on his ROMs - search his thread for "viper" and you'll probably find something. I think everything on this phone is loud to very loud depending on which channel.
Click to expand...
Click to collapse
Good call. Sounds like someone found a zip that will work, so that should be worth a look. As long as there's some customizable equalizer that works universally for the headphone jack, that's the most important part of the audio side of things. From the reviews I've read, the loudspeaker on the G3 should be louder than the one on my Note2 and the earpiece can hopefully live up to the Note2's legacy as well.
roirraW "edor" ehT said:
Note that one feature you definitely won't have on non-stock ROMs is the laser focus of the camera. No other app can work it. The camera will work, but it won't be as good. I used to dabble with CM but for my own use, it's too much trouble so I haven't fooled with it in a year or a year and a half, except on my LG G Pad 8.3, which stopped OTAs at Android 5.0.2 and it's too sluggish with it even when debloated.
Click to expand...
Click to collapse
That is good to know. Can the stock camera app be installed on a CM-based Rom or do you have to be running a stock-based Rom? I've never experienced the G3's fancy rangefinder autofocus before, but it sure sounds like a feature that would be disappointing to miss out on.
Bill720 said:
That is good to know. Can the stock camera app be installed on a CM-based Rom or do you have to be running a stock-based Rom? I've never experienced the G3's fancy rangefinder autofocus before, but it sure sounds like a feature that would be disappointing to miss out on.
Click to expand...
Click to collapse
No - there's no hope for getting the stock camera app to work on non-stock ROMs.
I recently told someone else here the two things I would most highly miss if I switched from LG are their warranty service and the built-in LG Backup, which is extremely fast and can take the place of Titanium Backup for the most common things, but you can still want TB for restoring Bluetooth parings, etc. Quirks of LG Backup to just be aware of: http://forum.xda-developers.com/showthread.php?p=67947945.
To add what @roirraW "edor" ehT stated as far as stock ROM, I used to run rooted. Mainly, this was due to needing TiBu. But once I discovered the LG Backup tool, I now no longer have my phone rooted. There just hasn't been a need for it as the stock ROM works pretty darned well for me. Battery life is good. As long as I'm not hunting , my phone lasts the day doing normal things like making/receiving phone calls, texting, checking news, etc.
Bill720 said:
So stock Android doesn't actually have WiFi tethering built in? Or do you just prefer Foxfi over it because of the features and functionality offered? I'm open to trying a CM or CM-based Rom as long as everything works. Now do you have access to any of the equalizer settings with that (like Viper audio) or does it require a special kernel? How is the volume level on voice calls?
If I go with the G3, that'll definitely be one to try also as long as tethering works with StraightTalk.
How's the situation with audio enhancements on that Rom (Viper audio or similar) or does that require a special kernel? Is volume on calls through the device's earpiece loud enough?
Click to expand...
Click to collapse
If I recall correctly the stock ROM does have hotspot built into it, but you need to have hotspot in the plan you use for your carrier. I have the unlimited everything plan with T-Mobile currently so I don't have to use foxfi but I did pay for so I Figured why not. CM13 does have hotspot built in and it works just fine. Though I haven't tested USB tethering yet.
My call quality has been absolutely superb.
Built into the ROM is also an equalizer called AudioFX which is honestly my favourite equalizer, it gives you different options based on what you have the phone hooked up to or if you even have the phone just running audio through the speakers. I'll actually go ahead and try running Viper ( never tried it before) on here now and report back with my findings.
Edit:--------------------------------------------------------------------------------------
So Viper works perfectly fine.
I disabled AudioFX using [root] App disabler
You need to have root enabled, then the SELinux Mode Changer installed and set to permissive, then just install the Viper apk and let it install the drivers and you are good to go.
*Note I did not test installing Viper via flashing it.
sound and vision 2
roirraW "edor" ehT said:
No - there's no hope for getting the stock camera app to work on non-stock ROMs.
I recently told someone else here the two things I would most highly miss if I switched from LG are their warranty service and the built-in LG Backup, which is extremely fast and can take the place of Titanium Backup for the most common things, but you can still want TB for restoring Bluetooth parings, etc. Quirks of LG Backup to just be aware of: http://forum.xda-developers.com/showthread.php?p=67947945.
Click to expand...
Click to collapse
Yeah, after years of being screwed over by Samsung's garbage Amoled screens, I have decided that no future primary device of mine will ever have one again. It's too bad because the Note2 has been fantastic other than that stupid screen with its green tint that has to be defeated using a custom kernel (which seriously limits the already-pathetic Rom selection) and annoying burn-in that never goes away.
I also tried the One M7, which, despite its tiny screen, is actually a solid device, but the terrible camera alone is bad enough to turn me off to it. Side by side, the Note 2's camera is better in most conditions (and that's a circa-2012 device!) and I just can't justify that kind of a drop in quality from an upgrade, so the G3 is the next runner up for me. As long as its lone screen idiosyncrasy (the artificial sharpness inherent with the stock rom) can be defeated, it sounds like a win to me.
Nonanza said:
If I recall correctly the stock ROM does have hotspot built into it, but you need to have hotspot in the plan you use for your carrier.
Click to expand...
Click to collapse
Yeah, I'm not paying for something twice. That is just not an option for me, mainly out of principal. I don't tether that much, but when I need it, the ability needs to be there without any intentionally-sabotaged software getting in the way.
Nonanza said:
My call quality has been absolutely superb.
Click to expand...
Click to collapse
Good. That's what I wanted to hear. Is the volume loud enough to hear even in a loud enviroment? The reason I ask is because the Note2 is actually quite quiet by default, but there's this special Samsung feature called "my call sound" which tailors the audio output frequencies to your ear's strengths and weaknesses. It basically subjects the user to a hearing test while wearing earbuds and then applies an equalizer to the earpiece for phone calls based on the results, which makes the volume very loud, even at the lowest setting.
Nonanza said:
If I recall correctly the stock ROM does have hotspot built into it, but you need to have hotspot in the plan you use for your carrier. I have the unlimited everything plan with T-Mobile currently so I don't have to use foxfi but I did pay for so I Figured why not. CM13 does have hotspot built in and it works just fine. Though I haven't tested USB tethering yet.
My call quality has been absolutely superb.
Built into the ROM is also an equalizer called AudioFX which is honestly my favourite equalizer, it gives you different options based on what you have the phone hooked up to or if you even have the phone just running audio through the speakers. I'll actually go ahead and try running Viper ( never tried it before) on here now and report back with my findings.
Edit:--------------------------------------------------------------------------------------
So Viper works perfectly fine.
I disabled AudioFX using [root] App disabler
You need to have root enabled, then the SELinux Mode Changer installed and set to permissive, then just install the Viper apk and let it install the drivers and you are good to go.
*Note I did not test installing Viper via flashing it.
Click to expand...
Click to collapse
Bill720 said:
Yeah, after years of being screwed over by Samsung's garbage Amoled screens, I have decided that no future primary device of mine will ever have one again. It's too bad because the Note2 has been fantastic other than that stupid screen with its green tint that has to be defeated using a custom kernel (which seriously limits the already-pathetic Rom selection) and annoying burn-in that never goes away.
I also tried the One M7, which, despite its tiny screen, is actually a solid device, but the terrible camera alone is bad enough to turn me off to it. Side by side, the Note 2's camera is better in most conditions (and that's a circa-2012 device!) and I just can't justify that kind of a drop in quality from an upgrade, so the G3 is the next runner up for me. As long as its lone screen idiosyncrasy (the artificial sharpness inherent with the stock rom) can be defeated, it sounds like a win to me.
Yeah, I'm not paying for something twice. That is just not an option for me, mainly out of principal. I don't tether that much, but when I need it, the ability needs to be there without any intentionally-sabotaged software getting in the way.
Good. That's what I wanted to hear. Is the volume loud enough to hear even in a loud enviroment? The reason I ask is because the Note2 is actually quite quiet by default, but there's this special Samsung feature called "my call sound" which tailors the audio output frequencies to your ear's strengths and weaknesses. It basically subjects the user to a hearing test while wearing earbuds and then applies an equalizer to the earpiece for phone calls based on the results, which makes the volume very loud, even at the lowest setting.
Click to expand...
Click to collapse
If you have unlimited data on Verizon, and you don't flash the hotspot mod, then you have to pay Verizon to use tethering. If you don't have unlimited data on Verizon, you don't have to do anything/pay anything additional to use the built-in hotspot. Using on another carrier like Straight Talk that he is (unless I'm confusing with another thread) is a different animal though.
Bill720 said:
Good. That's what I wanted to hear. Is the volume loud enough to hear even in a loud enviroment? The reason I ask is because the Note2 is actually quite quiet by default, but there's this special Samsung feature called "my call sound" which tailors the audio output frequencies to your ear's strengths and weaknesses. It basically subjects the user to a hearing test while wearing earbuds and then applies an equalizer to the earpiece for phone calls based on the results, which makes the volume very loud, even at the lowest setting.
Click to expand...
Click to collapse
The volume has been plenty loud for me when I'm out on the streets trying to catch 'em all, with people yelling and vehicles driving by with their noisy exhaust. I haven't tested it with the train going by but I usually can't even hear myself talk while it's passing.
On a side note the speaker on the back is of fair quality as well, I'm the type of person that likes to listen to music all day and the speaker has given me no issues or moments where I feel like I'd need to invest in a wireless speaker to tote around, granted it doesn't have bass but I don't ever expect there to be a bass driver in a phone that's just silly.
The only complaint I have with this phone is that it has a tendency to overheat with my usage, like right now it's at 35°C from me streaming and typing this response. When I play Pokémon go even at night, specifically last night for example it was reaching 42°C fairly quickly even with Coolify running, still trying to determine if it's the processor or the fact that a certain company that supposedly makes 10mil a day can't be bothered to hire coders that can program and optimize on the level of 10 year olds .
Edit----
Also wasn't to happy about all the hoops one needs to jump through in order to install custom recovery and even root the device in the first place.
testing the waters
roirraW "edor" ehT said:
If you have unlimited data on Verizon, and you don't flash the hotspot mod, then you have to pay Verizon to use tethering. If you don't have unlimited data on Verizon, you don't have to do anything/pay anything additional to use the built-in hotspot. Using on another carrier like Straight Talk that he is (unless I'm confusing with another thread) is a different animal though.
Click to expand...
Click to collapse
Yeah, that was me asking in that other thread . Anybody here using their Verizon G3 on one of the prepaid carriers that can comment on the functionality?
Nonanza said:
The volume has been plenty loud for me when I'm out on the streets trying to catch 'em all, with people yelling and vehicles driving by with their noisy exhaust. I haven't tested it with the train going by but I usually can't even hear myself talk while it's passing.
On a side note the speaker on the back is of fair quality as well, I'm the type of person that likes to listen to music all day and the speaker has given me no issues or moments where I feel like I'd need to invest in a wireless speaker to tote around, granted it doesn't have bass but I don't ever expect there to be a bass driver in a phone that's just silly.
Click to expand...
Click to collapse
Sounds like the sound system on the G3 is a go :good:.
Nonanza said:
The only complaint I have with this phone is that it has a tendency to overheat with my usage, like right now it's at 35°C from me streaming and typing this response. When I play Pokémon go even at night, specifically last night for example it was reaching 42°C fairly quickly even with Coolify running, still trying to determine if it's the processor or the fact that a certain company that supposedly makes 10mil a day can't be bothered to hire coders that can program and optimize on the level of 10 year olds .
Click to expand...
Click to collapse
When you say "overheat", do you just mean that the phone starts to feel too warm?
Nonanza said:
Also wasn't to happy about all the hoops one needs to jump through in order to install custom recovery and even root the device in the first place.
Click to expand...
Click to collapse
What's the story on that?
Bill720 said:
When you say "overheat", do you just mean that the phone starts to feel too warm?
Click to expand...
Click to collapse
I mean the phone is literally getting to 100 degrees Fahrenheit and above at times which to my knowledge is not so good for a phone as the components arn't likely designed to be that hot, it will also physically feel hot and it starts to slow down.
As far as the process I had to do on my phone is as follows.
Since it was running the stock 5.1.1 firmware I was unable to get the one click root method to work ( found in another thread) so I had to
1. Use the Chinese root known as king root
2. Convert that to SuperSU and get the king root gone (apparently adds extra sketchy stuff)
3. Use the LG flash tool to downgrade to the firmware
a. Had to change device to com31 or 41 In device manager and find the proper files.
4. Then root the device with stumproot.apk
5 . them install twrp
6. Then flash the 35b bootstack along with cyanogen and the gapps.
Took me 2 hours
Hi guys,
I just bought my Verizon G3 used on Sunday night and, although I'm currently using it as a Wi-Fi only device, I thought I may still be of help.
The same night I bought it I successfully rooted, added TWRP Recovery (Used "Bump" method found in Original Android Development), and flashed a modified stock ROM (SkyDragon). Upon research and confirmation by a member, I found out that pretty much all ROMs are now pre-bumped, and flashed Resurrection Remix a day or two later.
All this bump stuff can be found here: http://forum.xda-developers.com/ver...pment/bump-unlock-lg-g3-twrp-verizon-t2900590
You need root before you add Bump'd TWRP, and after failure with a no longer functioning method, I rooted with this method: http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197
If you need the official modems or bootstacks, they can be found in these threads:
Modem & Kernel: http://forum.xda-developers.com/verizon-lg-g3/development/rom-jasminerom-v1-0-t2904641
MODEM IS ALSO IN BOOTSTACKS
Bootstacks (Don't know if there's more around): http://forum.xda-developers.com/verizon-lg-g3/development/xdabbeb-s-vs980-2-0-0-t3231279
In case you go to RR, I believe it needs 35B Modem and Bootstacks.
Now, I read here that the laser focus no longer works on custom ROMs, but I still see the red light flickering in the back (on RR ROM). So does it or not? Please un-noobify me and have mercy I haven't researched the Verizon G3 section since Tuesday.
I never tried the speaker without Viper4Android, but I think it sounds great with it.
I'm still not sure what the temperarure should be but at the moment CPU Temp Xposed moduled indicates around 140°F (60°C) and GSam Battery Monitor reports current battery temperature as 103°F (39.44°C). These temperatures seem a little high to me (CPU really), but I've never really paid attention to temp data on my other devices so I don't know what to make of it. I currently have and Otterbox case on, which does increase temperature, but not too much, as I've seen, maybe only 1-3 degrees, or maybe nothing at all...I still have to observe more.
I'm currently using RR as my daily driver and get what I believe is about 4:30 - 5:30 sot. I don't play heavy games and never have location on...need to try out with my bluetooth headset with music only. I get no discharge when I sleep the device at night (I turn everything off + 24/7 airplane mode, Greenify with Xposed, Aggressive doze from Greenify, DS Battery Saver to back it up, and soon to come wake lock and alarm modifications but probably will never arrive as I'm fine with sleep and everything off)
I was quite entertained typing that. It's probablh the most I've typed in one post here on XDA. I hope it helps you at least some and others as well. Maybe I went too far...I forgot what the OP asked while I was typing lol
Thanks for reading
EDIT: I was initially on Android 5.0.1 and 24B stock firmware
dirty_smurf45 said:
Hi guys,
If you need the official modems or bootstacks, they can be found in these threads:
Modem & Kernel:
Bootstacks (Don't know if there's more around):
In case you go to RR, I believe it needs 35B Modem and Bootstacks.
EDIT: I was initially on Android 5.0.1 and 24B stock firmware
Click to expand...
Click to collapse
Hi! Just wanted to let you know the Bootstacks contain the modem, so unless you need, for instance, a 12B Modem on 24B Bootstack, etc, there's no need to flash a modem separately. If you were going to flash a different modem, you'd have to flash it after flashing the Bootstack, since the modem in the Bootstack would overwrite any modem you previously falshed. Post #2 of @xdabbeb 's VS985 v2.0 ROM thread tells all about what the Bootstacks contain. These are the only already packaged Bootstacks. For lower than 35B, you could make Bootstacks out of 23C, 11C or 10B, but usually someone will be on at least the very last release within a major version of Android (24B and 12B).
In case I didn't tell you elsewhere, or for anyone else reading this, a 46A/47A Bootstack would be unuseable because the 46/7A modem requires the 46/7A sbl1 partition, TWRP and root require the 12B aboot (bootloader), and the 46/7A sbl1 in combination with the 12B aboot causes a QHSUSB_BULK 9008 mode brick, so that's why we have to use the 35B Bootstack with 46A and 47A. I haven't tested yet, and probably won't bother, but I'm sure the same is true of the newly released 48A.
Also wanted to let you know that root method only works up through 24B. 35B and higher require KingRoot as far as I know, and so far the same versions of KingRoot that are able to temporarily (and invasively) root 46/7A won't root 48A.
That is all.
Edit: Also, you accidentally put the root thread link in where the modem and kernel thread is supposed to be. I'm sure you were just meaning @bweN diorD 's stickied thread in the General section. I think he has up through 35B in there. "Maybe" 46A too - I forget.
Noted, noted, noted, and noted. Thanks!!
Btw I meant the modems and kernels found in the JasmineROM thread
I use PA as my daily driver. Super fast. Not just saying that because I maintain it.
Roms!
roirraW "edor" ehT said:
If you have unlimited data on Verizon, and you don't flash the hotspot mod, then you have to pay Verizon to use tethering. If you don't have unlimited data on Verizon, you don't have to do anything/pay anything additional to use the built-in hotspot. Using on another carrier like Straight Talk that he is (unless I'm confusing with another thread) is a different animal though.
Click to expand...
Click to collapse
Do you know if the behavior would be any different than it would be on a completely stock rom? I tested the stock tethering capability on an OG Droid Razzur using the bone stock rom, and (predictably enough) it won't even try to enable the hotspot feature with a Tracfone BYOD sim card and service.
Nonanza said:
I mean the phone is literally getting to 100 degrees Fahrenheit and above at times which to my knowledge is not so good for a phone as the components arn't likely designed to be that hot, it will also physically feel hot and it starts to slow down.
Click to expand...
Click to collapse
Sounds like you're working it too hard . I think any phone would increase in temperature a bit when you're taxing it, although it's my understanding from the original AnandTech review that the G3 throttles itself down dynamically even in the stock rom to keep thermals under control.
Nonanza said:
down.
As far as the process I had to do on my phone is as follows.
Since it was running the stock 5.1.1 firmware I was unable to get the one click root method to work ( found in another thread) so I had to
1. Use the Chinese root known as king root
2. Convert that to SuperSU and get the king root gone (apparently adds extra sketchy stuff)
3. Use the LG flash tool to downgrade to the firmware
a. Had to change device to com31 or 41 In device manager and find the proper files.
4. Then root the device with stumproot.apk
5 . them install twrp
6. Then flash the 35b bootstack along with cyanogen and the gapps.
Took me 2 hours
Click to expand...
Click to collapse
It's good to have it all here on one page, but a bummer that it's such an annoying process.
dirty_smurf45 said:
Hi guys,
I just bought my Verizon G3 used on Sunday night and, although I'm currently using it as a Wi-Fi only device, I thought I may still be of help.
The same night I bought it I successfully rooted, added TWRP Recovery (Used "Bump" method found in Original Android Development), and flashed a modified stock ROM (SkyDragon). Upon research and confirmation by a member, I found out that pretty much all ROMs are now pre-bumped, and flashed Resurrection Remix a day or two later.
...
Now, I read here that the laser focus no longer works on custom ROMs, but I still see the red light flickering in the back (on RR ROM). So does it or not? Please un-noobify me and have mercy I haven't researched the Verizon G3 section since Tuesday.
I was quite entertained typing that. It's probablh the most I've typed in one post here on XDA. I hope it helps you at least some and others as well. Maybe I went too far...I forgot what the OP asked while I was typing lol
Thanks for reading
EDIT: I was initially on Android 5.0.1 and 24B stock firmware
Click to expand...
Click to collapse
Thanks for sharing. Since SkyDragon appears to be based on the stock rom, it's no wonder that the rangefinder for the camera works. What's the word on disabling the artificial sharpness on that rom though? I couldn't find anything on it in a quick search of the Op or even the entire thread.
Millennium2 said:
I use PA as my daily driver. Super fast. Not just saying that because I maintain it.
Click to expand...
Click to collapse
Interesting choice. Beside the rangefinder, are there any other features or goodies that non-LG-based Roms would lack?