ARCHIVED: [ROM] - gROM 2.2 - 10/16 - GB - With Flash - Yes, FLASH!

[biglance]

Scott, I've been using the beta you posted for almost a week now and it's working well. I enabled the A2SD via the A2SDGUI program in the market and it's rockin and rollin. I don't have the insufficient space issues with the market that I did previously. I did do a full backup of my microSD and restored back to the card after having Xionia format a 1GB partition for apps.

There is one thing that has been a bit of a bother, and I think it's a GB issue related to the audio. I use Waze for GPS and PocketCasts for podcasts during my daily commute. When the Waze app does a screen refresh, the audio will stutter. Like I said though, I think it's related to some of the GB audio problems and not the specific software, because it worked just fine with Android 2.2.

Again, awesome work man!

 

[Aerizeon]

There is a rare-ish problem where the wifi will falsely label itself as connected, but with no signal, and no actual connection. This especially happens when a program tries to change the state.

Also, typing seems more error-prone now: i frequently get double or triple letter hits.

Other than that, it's an awesome ROM.

[Edit]

The keyboard bug seems to be most prominent when overclocking, although my phone doesn't show any other signs of instability.

 

[docgoat1987]

here ya go scott the themes i made

 

[donbudafuko]

here ya go scott the themes i made

You got pics?

 

[docgoat1987]

i have pics of the blue one but the orange one i havent gotten pics yet

 

[kofasetic]

Things were sailing along smoothly until this morning. My SD Card is not recognized or needs to be re-formatted. I did neither and pulled the battery, Booted. Same thing. Connected to computer to see if computer can detect but no dice. So i rebooted into recovery mode, reads Xionia CWMA v1.2518.6, and wiped cache, rebooted device and nothing. Booted back into recovery, did a 'wipe & factory reset' and it is stuck on the 'android' screen as if I do not have this ROM installed. Can't access SD Card.
Should I reformat card via '-mounts & storage'?
What to do?
Thanks in advance to the help.

 

[Dassin]

Anyone else stroll having touch screen sensitivity issues?

I am. I have tried upgrading to GB three times since the official patch came out, and I have downgraded three times back to my old Froyo ROM three times because of the screen sensitivity. I honestly don't care about having new features if the phone is not usable Hopefully this issue will be fixed. If not, I'll never upgrade to GB

 

[scrosler]

Scott, I've been using the beta you posted for almost a week now and it's working well. I enabled the A2SD via the A2SDGUI program in the market and it's rockin and rollin. I don't have the insufficient space issues with the market that I did previously. I did do a full backup of my microSD and restored back to the card after having Xionia format a 1GB partition for apps.

There is one thing that has been a bit of a bother, and I think it's a GB issue related to the audio. I use Waze for GPS and PocketCasts for podcasts during my daily commute. When the Waze app does a screen refresh, the audio will stutter. Like I said though, I think it's related to some of the GB audio problems and not the specific software, because it worked just fine with Android 2.2.

Again, awesome work man!

Very cool. Next revision I will make an official A2SD version and a Non-A2SD version. Also to make life easy... Can you link me the app in the market you are referring to? I would like to take a look at it.

The keyboard bug seems to be most prominent when overclocking, although my phone doesn't show any other signs of instability.

I am. I have tried upgrading to GB three times since the official patch came out, and I have downgraded three times back to my old Froyo ROM three times because of the screen sensitivity. I honestly don't care about having new features if the phone is not usable Hopefully this issue will be fixed. If not, I'll never upgrade to GB

Some people say that! lol

Things were sailing along smoothly until this morning. My SD Card is not recognized or needs to be re-formatted. I did neither and pulled the battery, Booted. Same thing. Connected to computer to see if computer can detect but no dice. So i rebooted into recovery mode, reads Xionia CWMA v1.2518.6, and wiped cache, rebooted device and nothing. Booted back into recovery, did a 'wipe & factory reset' and it is stuck on the 'android' screen as if I do not have this ROM installed. Can't access SD Card.
Should I reformat card via '-mounts & storage'?
What to do?
Thanks in advance to the help.

Thats not good. Do you have a differnt SD card you can use?

 

[hlxanthus]

Things were sailing along smoothly until this morning. My SD Card is not recognized or needs to be re-formatted. I did neither and pulled the battery, Booted. Same thing. Connected to computer to see if computer can detect but no dice. So i rebooted into recovery mode, reads Xionia CWMA v1.2518.6, and wiped cache, rebooted device and nothing. Booted back into recovery, did a 'wipe & factory reset' and it is stuck on the 'android' screen as if I do not have this ROM installed. Can't access SD Card.
Should I reformat card via '-mounts & storage'?
What to do?
Thanks in advance to the help.

Will sd card mount from recovery > mounts and storage > enable mass storage?

 

[biglance]

The Market app I'm using is A2SDGUI - https://market.android.com/details?id=com.elgubbo.a2sdGUI

 

[ka5023]

Couple of things:

1) Charger issue. For me upgrading to ZVH caused any generic "USB Port" charger to stop charging, including my dual-port Griffin 1A. I think they changed the bootload code to be too strict on certain USB wire characteristics.

2) Screen sensitivity. I have a real issue with tap-holding, seems as though the screen likes to deregister touches a bit too much. Again, probably bootload firmware related. (which is why they haven't re-released GB for a month after the pull)

3) Default OCing. My Optimus just hates being OC'ed. I had the darndest time with any ROM with a default OC kernel, symptom of which usually is endless reboot-during-boot cycle. Which is why I was stuck on a ROM releases that didn't OC by default. But I finally found a workaround. You need to have three things:

a) Latest gROM release
b) gROM 1.1
c) Drew's kernel zip

Flash gROM 1.1 first, then without reboot do a NAND backup. Then proceed to flash the latest gROM, but then do an advanced restore, and restore BOOT from said backup. What this does is use a BOOT that does not contain any instructions to the kernel to OC. But it also causes mismatches between kernel and modules, which causes issue with, say, WiFi. So you need to flash Drew's kernel on top so that both boot kernel and modules are in sync.

Unfortunately, you need to make sure you do the boot-restore/kernel reflash steps on any reflashes, or at least until maintainers stop releasing OC'ed "releases" by default. Yes, lots of Optimus have no issue running at 748 or above (my first Optimus ran ~770ish but tended to reboot on high load with _any_ OC), but there are others that will end up not being able to run the majority of alternate ROMs because of it. I personally had issues with later releases of both ThundeROM and Reborn because I couldn't find non-OC kernels that I could flash over.

-- Starfox

 

[kofasetic]

Well looks like the sd card was corrupt. I installed a different card and flashed with the latest gROM and now phone is back to life.
Thanks

 

[scrosler]

The Market app I'm using is A2SDGUI - https://market.android.com/details?id=com.elgubbo.a2sdGUI

Thanks I will take a look at it!

Well looks like the sd card was corrupt. I installed a different card and flashed with the latest gROM and now phone is back to life.
Thanks

Good, thats what I was hoping... I mean.. You know... Compared to what COULD have been wrong, lol

Couple of things:

3) Default OCing. My Optimus just hates being OC'ed. I had the darndest time with any ROM with a default OC kernel, symptom of which usually is endless reboot-during-boot cycle. Which is why I was stuck on a ROM releases that didn't OC by default. But I finally found a workaround. You need to have three things:

a) Latest gROM release
b) gROM 1.1
c) Drew's kernel zip

Flash gROM 1.1 first, then without reboot do a NAND backup. Then proceed to flash the latest gROM, but then do an advanced restore, and restore BOOT from said backup. What this does is use a BOOT that does not contain any instructions to the kernel to OC. But it also causes mismatches between kernel and modules, which causes issue with, say, WiFi. So you need to flash Drew's kernel on top so that both boot kernel and modules are in sync.

Unfortunately, you need to make sure you do the boot-restore/kernel reflash steps on any reflashes, or at least until maintainers stop releasing OC'ed "releases" by default. Yes, lots of Optimus have no issue running at 748 or above (my first Optimus ran ~770ish but tended to reboot on high load with _any_ OC), but there are others that will end up not being able to run the majority of alternate ROMs because of it. I personally had issues with later releases of both ThundeROM and Reborn because I couldn't find non-OC kernels that I could flash over.

-- Starfox

Or you could just use the included "No Frills CPU control" to set the clock speed back to 600. Might be quicker than all that. Or am I missing something in the goal you were trying to acheive?


-Scott

 

[ka5023]

Or you could just use the included "No Frills CPU control" to set the clock speed back to 600. Might be quicker than all that. Or am I missing something in the goal you were trying to acheive?


-Scott

The goal is to make it through the boot so that No Frills can do it's thing. Latest version of ThundeROM/Reborn, and from my initial attempt on gROM 2.2 does not allow me to go through a complete boot without my (current) Optimus rebooting. This particular Optimus just does not take to being OC'ed at all. gROM 1.1 had no issues since the kernel wasn't overclocked by default.

-- Starfox

 

[scrosler]

The goal is to make it through the boot so that No Frills can do it's thing. Latest version of ThundeROM/Reborn, and from my initial attempt on gROM 2.2 does not allow me to go through a complete boot without my (current) Optimus rebooting. This particular Optimus just does not take to being OC'ed at all. gROM 1.1 had no issues since the kernel wasn't overclocked by default.

-- Starfox

Damn for real? You cant even get into the OS clocked at 748? If that is the case, I will post a non O/C'ed RAM disk for download so you dont have to do all that. But really? Cant even make to the OS? Damn. That stinks man!

 

[B-rye33]

Hello out there. I was just wondering if there was a way to get wifi hotspot or teather working? I read somewhere on this thread that one in the market works. I'm sorry if I missed it being mentioned already, but is there a fix for this, or what app works? I updated my girls phone to g rom and she uses
hotspot for her clients at work, so I'm in the dog house right now. Somehow I didn't realize it was broke. Any help is appreciated. Thank you in advance. -B-rye
Sent from my PC36100 using Tapatalk
Edit: found it. My bad. (in or around post 1091) thanks, later.

 

[ColoradoSteve]

Quick question -

I just installed gROM on my wife's Optimus.

On bootup - after the LG logo, her phone has a blue android robot with a circling flame. My phone has the word Android with different shades going through it.

I'm pretty sure that I used the same files for both. What's causing the difference?

 

[noc6285]

Is there a way to change the settings for the Power Control Widget or does anyone know of a good app for power buttons?

Thanks

 

[yazyazoo]

WiFi Tether doesn't work for me. I downloaded Open Garden WiFi Tether and then it worked. However I want the Original one to work because it might be able to let me connect my HP Touchpad to my phone via infrastructure vs ad hoc.

Is there a reason the original on gRom doesn't work?

Thanks

 

[noc6285]

WiFi Tether doesn't work for me. I downloaded Open Garden WiFi Tether and then it worked. However I want the Original one to work because it might be able to let me connect my HP Touchpad to my phone via infrastructure vs ad hoc.

Is there a reason the original on gRom doesn't work?

Thanks

I think b-rye mentioned that wifi tether was discussed around post 1091. I know it has been discussed before here. Try searching the thread. I just use Wifi tether from the market and it works fine for me.