• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM][WIP]CM10.0.0.l0-BobZ

Did this. Got morning call. Going to restore and flash the 5/21 build.

I'm so sorry about that, I miss read your question. I thought you said that when you tried to reboot after flashing it got stuck on LG Boot Screen. You mean that after successfully booting PG's build and tried to go in to recovery you get stuck at the LG Logo, right?

I edited my first answer. You press the volume buttons a couple of times when you see the LG Logo and the menu will pop up.
 
I'm so sorry about that, I miss read your question. I thought you said that when you tried to reboot after flashing it got stuck on LG Boot Screen. You mean that after successfully booting PG's build and tried to go in to recovery you get stuck at the LG Logo, right?

I edited my first answer. You press the volume buttons a couple of times when you see the LG Logo and the menu will pop up.
lol yeah no its nothing. While I am here, what is the difference in BoBz 5/21 build and PG's 5/17 build?
 
lol yeah no its nothing. While I am here, what is the difference in BoBz 5/21 build and PG's 5/17 build?

If you want to know which one is more stable (aka with the least bugs) I couldn't tell you off the top of my head but I do know that each build has its own problems (aka minor bugs). You can look at PG's and Bobz changelog to compare. You would also have to read the thread to know specifically which has what issue.

Here's PG's Wiki Page
 
I have a question, I have searched this thread and i don't feel like it is posted yet, so I am going to ask it.

I am using 5-21, BobZ build, and want to flash PG's 5-17 build to see if the GPS is working. A couple questions:

1.) Can I flash PG's build directly from BobZ build? Should I use the unbrick guide to go back to stock first? Or is that an unnecessary step?

2.) Is GPS confirmed as working or will I be wasting my time flashing PG's build?

Any help is appreciated. Thanks :p
 
I have a question, I have searched this thread and i don't feel like it is posted yet, so I am going to ask it.

I am using 5-21, BobZ build, and want to flash PG's 5-17 build to see if the GPS is working. A couple questions:

1.) Can I flash PG's build directly from BobZ build? Should I use the unbrick guide to go back to stock first? Or is that an unnecessary step?

2.) Is GPS confirmed as working or will I be wasting my time flashing PG's build?

Any help is appreciated. Thanks :p

I don't think it is, and if it is, it's still not fully usable, so I think you would be wasting your time :p but try it anyways if you want to and have the time! :]
 
I think - and I might be wrong - that the difference between bobz's 5/21 and PG's 5/17 build is that PG added onto bob'z earlier build some fixes for like echo and stuff but the volume was still really low.
Then bob updated on 5/21 with some other fixes including the slightly higher volume for calls.

Those are as far as I know the difference between the two.
 
2.) Is GPS confirmed as working or will I be wasting my time flashing PG's build?

Any help is appreciated. Thanks :p

No dice, it seems. I'm going out on a limb here and saying that it might be a hardware issue, in the sense that the ROM and the GPS are not communicating (in a sense) very well, or at all. I've even tried messing with the gps.conf file as best as I could, but to no avail.
 
No dice, it seems. I'm going out on a limb here and saying that it might be a hardware issue, in the sense that the ROM and the GPS are not communicating (in a sense) very well, or at all. I've even tried messing with the gps.conf file as best as I could, but to no avail.

I have tried every single gps.conf edit under the sun. I even put the gps.conf from stock firmware C on my phone and that did nothing. I agree with your assessment. The issue is much deeper than any GPS settings.
 
Anyone get a weird bug on bobz latest (5/21) when calling with someone for more than 12 minutes or so when the phone locks it self (and the actual lockscreen pops up) and you unlock it just vibrates like crazy till you lock it and unlock it again. I flashed everything normal including the modem c and it only happens once per call I haven't tried it on PG's build. I flashed from version d if that info is needed.

EDIT: I was in the same call going on 50 mins and if you have snapchat open with the camera and the mass storage on and its mounted to your computer (maybe Im just doing to much at once) it will vibrate out of control as well.
 
Anyone get a weird bug on bobz latest (5/21) when calling with someone for more than 12 minutes or so when the phone locks it self (and the actual lockscreen pops up) and you unlock it just vibrates like crazy till you lock it and unlock it again. I flashed everything normal including the modem c and it only happens once per call I haven't tried it on PG's build. I flashed from version d if that info is needed.

EDIT: I was in the same call going on 50 mins and if you have snapchat open with the camera and the mass storage on and its mounted to your computer (maybe Im just doing to much at once) it will vibrate out of control as well.

I had a similar problem but it was with the lock screen...
sometimes (randomly - it seems) it'd ***** out and rumble until I turn it off and back on; unlocking and locking didn't work...

some other times it'd stop if I lock and unlock but would happen 6 or more times in a row when unlocking the device (but would stop when locked)....

My guess is that (at least the lock screen one) can be due to our default lockscreen creating a rumble when unlocking (which is common) but in the coding side of things it kills the activity before the rumble is finished if the device takes a longer amount that 'x' seconds to unlock or do what you want it to?

That's a totally noob-ish guess. I don't know if lock screens behave the same way as regular applications or if they have the same activity life management rules or whatever... I've only ever made a few android applications in my life.
 
I had a similar problem but it was with the lock screen...
sometimes (randomly - it seems) it'd ***** out and rumble until I turn it off and back on; unlocking and locking didn't work...

some other times it'd stop if I lock and unlock but would happen 6 or more times in a row when unlocking the device (but would stop when locked)....

My guess is that (at least the lock screen one) can be due to our default lockscreen creating a rumble when unlocking (which is common) but in the coding side of things it kills the activity before the rumble is finished if the device takes a longer amount that 'x' seconds to unlock or do what you want it to?

That's a totally noob-ish guess. I don't know if lock screens behave the same way as regular applications or if they have the same activity life management rules or whatever... I've only ever made a few android applications in my life.


The word S-p-a-z-e- is censored?
 
Back
Top Bottom