Related
I know this isn't where i should post this but my Post Count is to low to post in the development forum. I installed RC 0.4 of CM 7 with a full wipe from .3 and up until last night everything was working fine (except the 4g/3g hand-off). Last night out of the blue it started random rebooting/boot looping. I plugged it in and went to bed. When i woke up it was on and some of my launcher settings were reset but other than that it was ok. Then today I have been experiencing more random reboots. Anyone else with this issue?
Can't post in the dev area yet either
I've had CM7 RC4 on for 3 days now and I haven't experienced any reboots yet but I'm not in a 4G area. Did you mess with the overclocking settings? Try to drop it down to 1GHz and see if that helps. Are you on the stock radio? I have mine on stock radio and it seems to work well.
I didn't overclock it any. I did use setcpu to check to make sure that that it was limiting itself to 1Gh thought, but i didn't touch anything else. My radio is the stock MR1 radio 1.16.00.0402w_1. I switched kernels to KangBang's most recent version for now, the random reboots became to much to handle.
You need go back older radio 223r, I have no problem with CM7 RC0.4 and none reboots. The CM7 author stated says use 223r radio.
slayher said:
I highly recommend The stock radio images. All the testing up to this point is based on 1.16.00.0223r Baseband
Click to expand...
Click to collapse
JBass said:
I didn't overclock it any. I did use setcpu to check to make sure that that it was limiting itself to 1Gh thought, but i didn't touch anything else. My radio is the stock MR1 radio 1.16.00.0402w_1. I switched kernels to KangBang's most recent version for now, the random reboots became to much to handle.
Click to expand...
Click to collapse
I read in the forum that you need to be 402w or before.
here: http://forum.xda-developers.com/showpost.php?p=14692504&postcount=5024
Keep in mind that the stock setting for the new release is 1.8GHz in the performance settings. I heard this stock setting was causing some problems for some.
JBass, you gave me link is not CM7 author.
You need read again - http://forum.xda-developers.com/showpost.php?p=13179476&postcount=1
I know that it wasn't from the dev but I guess I'm naive for believing the internet
Now its supported,
cant post link but on rootzwiki the post has been updated.
I'm having an annoying issue with my Charge. Whenever I try to record with the Camera the phone just freezes and reboots after about 10 seconds. Yes I'm undervolted, which is what I'm suspecting as the issue but I went into Voltage Control and set the voltages back to 0 and to no avail, it still just froze and rebooted. I tried overclocking to 1.2Ghz without undervolting that clock speed at all(1GHz and below were still all undervolted) and it still just froze and rebooted.
The weird thing is this happens on the stock undervolt settings that the kernel comes with. I'm going to assume Imnuts' just didn't have the time to test all the apps individually for stability issues when implementing his undervolt script. I know it's an issue with the kernel(almost positive it's from the undervolting itself because i had stability issues exactly like this back on EE4 when i would undervolt) because if I reboot and flash imoseyons 4.0.0 kernel recording is fixed.
edit: I just tried removing my Voltage Control boot settings so there shouldn't be any undervolting going on(aside from the stock undervolt script thats included with the kernel) and it still just freezes and reboots. I'm guessing it's either the undervolt script or the kernel itself. Anyone else have this issue? If so how'd you fix it? Thanks in advance.
just tested. i use the default uv settings, oc to 1200.
camera was able to record fine. no freeze.
mromblad said:
just tested. i use the default uv settings, oc to 1200.
camera was able to record fine. no freeze.
Click to expand...
Click to collapse
How long did you let it record? and was it on 1280/720? It usually freezes on me after about 10-20 seconds
I just tried to record.. Freezes after 4 seconds reboots just like you described. Eclipse ROM+PBJ 1.15 kernel. Oh also no overclocking at all for me
adrenaline_rush said:
I just tried to record.. Freezes after 4 seconds reboots just like you described. Eclipse ROM+PBJ 1.15 kernel. Oh also no overclocking at all for me
Click to expand...
Click to collapse
That seems to be an issue with Eclipse rom. A lot of people are having that problem and nitro is aware of the issue and says the next version will have a fix.
shrike1978 said:
That seems to be an issue with Eclipse rom. A lot of people are having that problem and nitro is aware of the issue and says the next version will have a fix.
Click to expand...
Click to collapse
While I never use the camcorder at that resolution, I tried it now and had the same freeze-up. Running tweakstock (fancy that lol) and pbj kernel - I tried this without any voltage control-style modifications. I have some vague recollection of similar issues at some other point, and for some reason I remember the class of sdcard being part of the conversation... I of course can be (and most likely am) completely off on that, just thought I'd mention it.
dwitherell said:
While I never use the camcorder at that resolution, I tried it now and had the same freeze-up. Running tweakstock (fancy that lol) and pbj kernel - I tried this without any voltage control-style modifications. I have some vague recollection of similar issues at some other point, and for some reason I remember the class of sdcard being part of the conversation... I of course can be (and most likely am) completely off on that, just thought I'd mention it.
Click to expand...
Click to collapse
I remember that class 2 cards can't do HD video, but class 4's are supposed to be able to. I never do video, but I have a class 4, so I tried to see (on Eclipse) and it crashed to the point of forcing a reboot. Not sure now if it's ROM or kernel.
just tried hd vid. on eclipse w/Imos 4.0 kernel with no problem....
Mine did the same thing and I am just using the kernel and the new eclipse
Sent from my SCH-I510 using xda premium
I have been running the pb&j 1/15 kernel and Infinity rom for a day now with no freeze-ups or reboots. I haven't messed with OC'ing or voltages, just wanted to see if the new kernel made a difference. The phone is now much smoother in operation and quicker in response. Very impressive.
I saw this post and walked around the house scanning barcodes using shop-savvy and had no issues at all. This app does a lot of stuff on top of using the camera and just flies now.
Also getting freeze-up when trying to record HD vid.
Running Tweakstock 1.1 and PBJ 0115
edit: *UPDATE* - I just flashed Imoseyon's 4.0.0 kernel to test, and HD recording worked flawlessly. So it does seem to be the kernel which is causing the issue (in my case at least). Can anybody tell me how to pull a logcat so I can send it over to imnuts?
cujo6801 said:
just tried hd vid. on eclipse w/Imos 4.0 kernel with no problem....
Click to expand...
Click to collapse
Where did you find the kernel? Everything works great except the video.
Does anyone know of a stock, rooted version?
Sent from my SCH-I510 using xda premium
shrike1978 said:
That seems to be an issue with Eclipse rom. A lot of people are having that problem and nitro is aware of the issue and says the next version will have a fix.
Click to expand...
Click to collapse
I believe it's an issue with Imnuts' 1/15 kernel, not the ROM.
cujo6801 said:
just tried hd vid. on eclipse w/Imos 4.0 kernel with no problem....
Click to expand...
Click to collapse
See anyone running Imos kernel doesn't have the issue so I don't believe that Eclipse is the problem, although it is still possible.
dwitherell said:
While I never use the camcorder at that resolution, I tried it now and had the same freeze-up. Running tweakstock (fancy that lol) and pbj kernel - I tried this without any voltage control-style modifications. I have some vague recollection of similar issues at some other point, and for some reason I remember the class of sdcard being part of the conversation... I of course can be (and most likely am) completely off on that, just thought I'd mention it.
Click to expand...
Click to collapse
Yeah I remember back when Gummy2.0 was released I had that issue. I know it's not the same thing though because whenever I would record it would give me an error message like "This SD card does not support HD video recording" or something like that and it would just close the camera app, it wouldnt just freeze and reboot.
shrike1978 said:
I remember that class 2 cards can't do HD video, but class 4's are supposed to be able to. I never do video, but I have a class 4, so I tried to see (on Eclipse) and it crashed to the point of forcing a reboot. Not sure now if it's ROM or kernel.
Click to expand...
Click to collapse
I'm positive it's not a problem with the SD card. I'm on Tweakstock so for now it's to be assumed that the kernel is the problem since cujo6801 already tested Eclipse with Imos kernel and had no problem, but adrenaline_rush tested Eclipse with Imnuts' kernel and it froze/rebooted. Pretty sure it's a kernel issue at this point.
jimc5423 said:
I have been running the pb&j 1/15 kernel and Infinity rom for a day now with no freeze-ups or reboots. I haven't messed with OC'ing or voltages, just wanted to see if the new kernel made a difference. The phone is now much smoother in operation and quicker in response. Very impressive.
I saw this post and walked around the house scanning barcodes using shop-savvy and had no issues at all. This app does a lot of stuff on top of using the camera and just flies now.
Click to expand...
Click to collapse
Try your actual Camera and attempt to record video @ 1280/720, then tell me if it reboots.
I got the freeze and reboot every time with Eclipse and PBJ at 720p. Flashed Tweakstock with PBJ and it worked. Then tried Eclipse with the ep4d kernel and that worked too. I thought it might be the camera so I copied the one from from Tweakstock into Eclipse and 720p recording worked fine undervolted and oc'd to 1200.
Edit: Tried it again since reflashing updated Eclipse and it locked at 10 seconds. Guess I was lucky last time. Shot multiple 45 second plus videos ok.
Sent from my SCH-I510 using XDA App
Just tried on mine. Eclipse with PBJT kernel, froze instantly.
Sent from my SCH-I510 using xda premium
kvswim said:
Just tried on mine. Eclipse with PBJT kernel, froze instantly.
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
Same config and instant, several attempts.
benb1974 said:
Same config and instant, several attempts.
Click to expand...
Click to collapse
Tweastock with PBJ freezes and reboots on mine too. Never froze on Tweakstock with included kernel
Checked the comments on Imnuts' kernel over at RootzWiki and i can confirm it's a problem with the kernel, in addition to that the HDMI port doesnt seem to work.
I have been getting froze screens and 1 reboot also, since running imnuts kernel. I thought it was maybe the ROM but doing a little research IM finding the kernel has an issue. I didn't try the camera with imnuts kernel but I've flashed imo 4.0 kernel and the recording does work w/o force closing on me.
Sent from my SCH-I510 using XDA App
Also be careful overclocking on PBJ, I set it to 1600 max on SetCPU, and after a few moments it froze and rebooted. When it rebooted, as soon as SetCPU was granted SU, there goes another freeze. I wasn't able to change the settings due to the freeze, and after a few reboots I was taken to the setup screen like you would see after a factory reset. But this came with random F/C errors and lots of non-functional apps. You can't do anything at this point but restart from stock+PIT and go up from there. Reflashing the ROM, kernel, restoring, even ODINing another ROM won't rid the F/C hell.
Same thing as this, when I tried to use the Voodoo screen tuner:
http://forum.xda-developers.com/showpost.php?p=21629058&postcount=176
Oh also people stated imyosen kernel was a battery drain, but it's been very good on battery so far.
I just got my G2x from my Optimus V and I'd like to flash a new ROM. I've already rooted it. What ROM is stable and as close to pure Android as possible? I hate all the bloatware that come on these phones from the carriers. I've been reading through all the ROMs in the Dev section but my head is spinning.
If you want super pure, your best bet is probably to stick with stock, since the G2x came with vanilla Android. Use Titanium Backup to freeze/uninstall all the bloat you want gone.
Sent from my LG-P999 using xda premium
CM7.2 Official with Faux v50 Kernel. I back the OC down from 1.5 to 1.2 and its suber stable and fast. To help make it even more responsive I use Auto Memory Manager (https://play.google.com/store/apps/details?id=com.lim.android.automemman) set to Aggressive. I've also used Weapon G2x but prefer CM7.2
bg1906 said:
CM7.2 Official with Faux v50 Kernel. I back the OC down from 1.5 to 1.2 and its suber stable and fast. To help make it even more responsive I use Auto Memory Manager (https://play.google.com/store/apps/details?id=com.lim.android.automemman) set to Aggressive. I've also used Weapon G2x but prefer CM7.2
Click to expand...
Click to collapse
Thanks, I actually flashed 7.2 a few minutes before I read your post How do I flash the new Kernel?
EDIT: Nevermind, got Faux 050 flashed
bg1906 said:
CM7.2 Official with Faux v50 Kernel. I back the OC down from 1.5 to 1.2 and its suber stable and fast. To help make it even more responsive I use Auto Memory Manager (https://play.google.com/store/apps/details?id=com.lim.android.automemman) set to Aggressive. I've also used Weapon G2x but prefer CM7.2
Click to expand...
Click to collapse
CM7.2 (really any CM7 based Rom) is the way to go. Stay away from ICS if you just want everything to work since Nvidia iz not releasing drivers needed for hardware acceleration on the G2x.
Few things to watch out for...
1. Memory managers/app killers are generally a bad idea for stability/battery life
2. Watch what baseband you are on. March2012 has broken bluetooth calling. You may need owain's baseband fix to patch an incompatible rom with your baseband.
3. Some CM7 users have better luck with Morfic's Trinity kernels vs Faux.
4. Lots of overclocking will likely result in stability probs regardless of your Rom/kernel combo (beware of undervolting too)
5. Stock 2.3.4 is now a viable option for stablity. + u could even overclock with Faux's 014b kernel for rooted stock.
6. Read the forums!
Get comfortable with making backups in CWM (oh you shouldn't use CWM Touch - or ROM Manager to flash anything - CWM 5.0.2.0 is fine) That way u can expriment, but restore back if it all starts going to shjt.
hairycheapo said:
CM7.2 (really any CM7 based Rom) is the way to go. Stay away from ICS if you just want everything to work since Nvidia iz not releasing drivers needed for hardware acceleration on the G2x.
Few things to watch out for...
1. Memory managers/app killers are generally a bad idea for stability/battery life
2. Watch what baseband you are on. March2012 has broken bluetooth calling. You may need owain's baseband fix to patch an incompatible rom with your baseband.
3. Some CM7 users have better luck with Morfic's Trinity kernels vs Faux.
4. Lots of overclocking will likely result in stability probs regardless of your Rom/kernel combo (beware of undervolting too)
5. Stock 2.3.4 is now a viable option for stablity. + u could even overclock with Faux's 014b kernel for rooted stock.
6. Read the forums!
Get comfortable with making backups in CWM (oh you shouldn't use CWM Touch - or ROM Manager to flash anything - CWM 5.0.2.0 is fine) That way u can expriment, but restore back if it all starts going to shjt.
Click to expand...
Click to collapse
Yup, I've been reading a lot and saw some of the things you've mentioned, but thanks for the ideas.
I haven't touched basebands, should I do anything with them?
I'm on 7.2 Stable, do I need a new kernel to OC/UC? I can't seem to get it to work as nothing comes up when I'm in the CM menus.
I'm familiar with nAndroind backups as I did them religiously on my last Optimus V phone.
EDIT: Nevermind, I flashed Faux 050 now and can OC/UV now.
Looks like you are doing fine. Congrats on figuring out how to flash a Rom/kernel.
Faux 050 stable and CM7 based Temasek rom is what I've been running for weeks now. If you don't have obnoxious static during phone calls (sounds like loud popping) - you don't have a baseband/rom compatibility issue. The baseband is just the firmware that controls the various radios in the device. Some have reported clearer calls and quicker GPS with the new (March 2012) baseband, but the hassle of upgrading to it is - well - a hassle. Also, If you use like to use bluetooth for calls, you need to NOT upgrade...
I am on the new baseband (I don't have blueteeth) and I'll sometimes need to flash the compatibility fix that enables you to run the new baseband with roms designed for the old baseband (or now, for roms/basebands on our international cousin the LG P990). Check owain's Domination thread for his "baseband fix", it will probably come in handy since some roms authors are not clear about whether their rom is for the new or old baseband.
You would just flash the fix through CWM after flashing a Rom, if you find that you have the call sound static...
You might also need a free app called "Get Ril" to fix your Radio Interface Layer. It automatically checks for compatibility and will automatically apply the RIL it detects that you would need if your calling sound has static.
---------- Post added at 01:27 AM ---------- Previous post was at 01:18 AM ----------
Also-
If you are comfortable with backing-up and restoring Nandroids, don't be afraid to at least sample some of the ICS builds. IMHO we have some awesome developers making the best of things considering the massive handicap that is presented by Nvidia withholding the drivers. ICS is getting more stable all the time. Fixes are now being incorporated that address memory-bleed issues, data-dropping, browser rotation crashes, missing APNs, and various stability improvements. Still probably not "daily driver" for most people, but you could be your own judge...
hairycheapo said:
Looks like you are doing fine. Congrats on figuring out how to flash a Rom/kernel.
Faux 050 stable and CM7 based Temasek rom is what I've been running for weeks now. If you don't have obnoxious static during phone calls (sounds like loud popping) - you don't have a baseband/rom compatibility issue. The baseband is just the firmware that controls the various radios in the device. Some have reported clearer calls and quicker GPS with the new (March 2012) baseband, but the hassle of upgrading to it is - well - a hassle. Also, If you use like to use bluetooth for calls, you need to NOT upgrade...
I am on the new baseband (I don't have blueteeth) and I'll sometimes need to flash the compatibility fix that enables you to run the new baseband with roms designed for the old baseband (or now, for roms/basebands on our international cousin the LG P990). Check owain's Domination thread for his "baseband fix", it will probably come in handy since some roms authors are not clear about whether their rom is for the new or old baseband.
You would just flash the fix through CWM after flashing a Rom, if you find that you have the call sound static...
You might also need a free app called "Get Ril" to fix your Radio Interface Layer. It automatically checks for compatibility and will automatically apply the RIL it detects that you would need if your calling sound has static.
---------- Post added at 01:27 AM ---------- Previous post was at 01:18 AM ----------
Also-
If you are comfortable with backing-up and restoring Nandroids, don't be afraid to at least sample some of the ICS builds. IMHO we have some awesome developers making the best of things considering the massive handicap that is presented by Nvidia withholding the drivers. ICS is getting more stable all the time. Fixes are now being incorporated that address memory-bleed issues, data-dropping, browser rotation crashes, missing APNs, and various stability improvements. Still probably not "daily driver" for most people, but you could be your own judge...
Click to expand...
Click to collapse
Things seem to be going well with CM7.2+Faux050. I'm waiting till the end of the month for my Virgin Mobile month to end before I start up with T-mobile $30/month plan so I won't know if calls are clear for now. I'll try gVoice sometime soon just to test it though.
EDIT: Once I'm sure this ROM/Kernel is stable I'll do a nAndroid backup and play around with some of the ICS ROMs.
Superorb said:
Things seem to be going well with CM7.2+Faux050. I'm waiting till the end of the month for my Virgin Mobile month to end before I start up with T-mobile $30/month plan so I won't know if calls are clear for now. I'll try gVoice sometime soon just to test it though.
EDIT: Once I'm sure this ROM/Kernel is stable I'll do a nAndroid backup and play around with some of the ICS ROMs.
Click to expand...
Click to collapse
I sometimes use GrooveIP with google voice. U 2? Mine works ok and I am thinking of cutting back the number of T-Mobile minutes I pay for each month. Let me know how internet calling works for you...
hairycheapo said:
I sometimes use GrooveIP with google voice. U 2? Mine works ok and I am thinking of cutting back the number of T-Mobile minutes I pay for each month. Let me know how internet calling works for you...
Click to expand...
Click to collapse
I use GrooveIP on my other phone where it doesn't work on 3G b/c VM service is so ridiculously slow. It should work on 4G though, but I won't be able to test until the end of the month.
Gotcha. Be aware too that T-Mobile's "4G" is really more like 3G in most places. I see speeds between 2-5 Mb/s. I really only use my GrooveIP at home on my relatively fast Wi-Fi so I am not going to be the best person to talk to about how well it all works on T-Mobile's data network at our "4G" speeds.
Anyhow, its been good chatting. I gotta get some sleep now. Night...
hairycheapo said:
Gotcha. Be aware too that T-Mobile's "4G" is really more like 3G in most places. I see speeds between 2-5 Mb/s. I really only use my GrooveIP at home on my relatively fast Wi-Fi so I am not going to be the best person to talk to about how well it all works on T-Mobile's data network at our "4G" speeds.
Anyhow, its been good chatting. I gotta get some sleep now. Night...
Click to expand...
Click to collapse
Well, when you come from 100-140kbps 2-5mbps is screaming fast! As long as data is reliable inside buildings around town I'll be a happy camper. It's late here too, but I can't stop playing with my new phone
I spoke too soon... Battery was at 50% a minute ago and now it's stuck on 100%. Tried rebooting and wiping battery stats but no good.
hairycheapo said:
CM7.2 (really any CM7 based Rom) is the way to go. Stay away from ICS if you just want everything to work since Nvidia iz not releasing drivers needed for hardware acceleration on the G2x.
Few things to watch out for...
1. Memory managers/app killers are generally a bad idea for stability/battery life
2. Watch what baseband you are on. March2012 has broken bluetooth calling. You may need owain's baseband fix to patch an incompatible rom with your baseband.
3. Some CM7 users have better luck with Morfic's Trinity kernels vs Faux.
4. Lots of overclocking will likely result in stability probs regardless of your Rom/kernel combo (beware of undervolting too)
5. Stock 2.3.4 is now a viable option for stablity. + u could even overclock with Faux's 014b kernel for rooted stock.
6. Read the forums!
Get comfortable with making backups in CWM (oh you shouldn't use CWM Touch - or ROM Manager to flash anything - CWM 5.0.2.0 is fine) That way u can expriment, but restore back if it all starts going to shjt.
Click to expand...
Click to collapse
What's wrong with CWM Touch? I've been using it for the past few months with no problems whatsoever.
Sent from my LG-P999 using xda premium
FatalityBoyZahy said:
What's wrong with CWM Touch? I've been using it for the past few months with no problems whatsoever.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
There were some problems flashing some things with Touch. I can't remember which right now. Maybe Trinity kernels?
FatalityBoyZahy said:
What's wrong with CWM Touch? I've been using it for the past few months with no problems whatsoever.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
It's the lack of proper ext4 support.
hairycheapo said:
There were some problems flashing some things with Touch. I can't remember which right now. Maybe Trinity kernels?
Click to expand...
Click to collapse
Hi all. I've spent more time than I should over the past week or so looking through these forums (thank you all for the amazing amount of work that's been put in), but really haven't been able to figure out the answer to the following question: What's the best configuration for this phone?
I've been running EaglesBlood, which is OK but somewhat buggy (battery drain, random turning on of phone button lights, etc). Is there any configuration that's stable, fast, and decent?
SINGH-UI + Mazout360 Kernel
I am very happy with my setup:
SINGH-UI MIUI with Mazout360's kernel
I was using Faux123's 054 kernel with lg voltage which was working very well but Mazout's kernel is newer, faster and fixes a wifi issue that was causing reboots when turning wifi-related stuff on and off. I'm still testing it for stability but so far so good.
I haven't tried the ICS and Jelly Bean ROMS.
vanilla cm7 w/ mazouts kernel
"my mind draws lots of blanks actually"
Pardon my ignorance, but I don't quite understand how one can be running cm7 (or SINGH-UI MIUI) and mazout's kernel. Aren't they different roms? I'm missing some basic understanding here.
justjackyl said:
vanilla cm7 w/ mazouts kernel
"my mind draws lots of blanks actually"
Click to expand...
Click to collapse
This is more or less how it works. The "rom" is mostly blue stuff.
natescape said:
Pardon my ignorance, but I don't quite understand how one can be running cm7 (or SINGH-UI MIUI) and mazout's kernel. Aren't they different roms? I'm missing some basic understanding here.
Click to expand...
Click to collapse
A kernel is just a layer that interacts between the ROM and the physical hardware.
Like a car:
ROM = Body
Kernel= Engine
You can pull the engine and put it in a different body.
Poor analogy probably lol
"my mind draws lots of blanks actually"
justjackyl said:
vanilla cm7 w/ mazouts kernel
Click to expand...
Click to collapse
Seems it could last for days with the right configuration. I don't know what it would be except turning off data when not in use, and turning off auto sync.
Sent from my LG-P999 using xda app-developers app
adamiscool said:
Seems it could last for days with the right configuration. I don't know what it would be except turning off data when not in use, and turning off auto sync.
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
What?
Sent from my LG-P999 using Tapatalk 2
Mazout's 218 kernel and CM7 2-1-13 works pretty well for me. Although, I think I was getting slightly better battery life on Mazout's 205 kernel.
figuratively said:
Mazout's 218 kernel and CM7 2-1-13 works pretty well for me. Although, I think I was getting slightly better battery life on Mazout's 205 kernel.
Click to expand...
Click to collapse
Agreed. Better battery on 0205.!
"my mind draws lots of blanks actually"
Thanks guys!
So if I was to try one of these configs, first I'd install the ROM, then the kernel?
justjackyl said:
Agreed. Better battery on 0205.!
"my mind draws lots of blanks actually"
Click to expand...
Click to collapse
natescape said:
Thanks guys!
So if I was to try one of these configs, first I'd install the ROM, then the kernel?
Click to expand...
Click to collapse
That is correct
dEris said:
What?
Click to expand...
Click to collapse
Apps like to sync in the background. These settings can be changed to be turned off or run at a different interval of time. The mazkrnl and cm7 nightly has gotten me beyond 24hrs of use, but I think it can go beyond that with the right settings. I believe it could last a week or more. That clear it up?
Edit: haha, I mean...I don't know if you're trolling or what.
Sent from my LG-P999
natescape said:
Thanks guys!
So if I was to try one of these configs, first I'd install the ROM, then the kernel?
Click to expand...
Click to collapse
I'm also fairly new to all this and I would just like to offer some tips:
1. ensure you have the newest baseband before doing anything
Check your phone (Settings->System->About phone) Should be March 2012 Baseband
If you don't have the new baseband, there are a few tutorials such as this one
2. Install ROM and kernel if needed
3. Install the recommended google apps zip as instructed
4. Install GetRIL from app store and use it to install matching RIL
5. I believe you should Install a cpu control app for power saving (I'm using Antutu CPU master)
You could install kernel last. ROMS come with their own kernels.
m3mb3rsh1p said:
I'm also fairly new to all this and I would just like to offer some tips:
1. ensure you have the newest baseband before doing anything
Check your phone (Settings->System->About phone) Should be March 2012 Baseband
If you don't have the new baseband, there are a few tutorials such as this one
2. Install ROM and kernel if needed
3. Install the recommended google apps zip as instructed
4. Install GetRIL from app store and use it to install matching RIL
5. I believe you should Install a cpu control app for power saving (I'm using Antutu CPU master)
You could install kernel last. ROMS come with their own kernels.
Click to expand...
Click to collapse
If you switch to the March 2012 Baseband, you WILL LOSE Bluetooth Calling on any custom ROM used. I HIGHLY advise NOT switching basebands if you are a bluetooth headset user.
New2my8125 said:
If you switch to the March 2012 Baseband, you WILL LOSE Bluetooth Calling on any custom ROM used. I HIGHLY advise NOT switching basebands if you are a bluetooth headset user.
Click to expand...
Click to collapse
+1
"my mind draws lots of blanks actually"
huh
I did not know that. I guess I should find out what's good about the newest baseband and quick one is best...
Quick Question
This post is the guide I used when upgrading my baseband. I'll use it to downgrade when I start using bluetooth audio.
m3mb3rsh1p said:
This post is the guide I used when upgrading my baseband. I'll use it to downgrade when I start using bluetooth audio.
Click to expand...
Click to collapse
its only bt call audio that doesn't work on 21y. media audio works fine.
"my mind draws lots of blanks actually"
I installed CM 7.2 and gapps with no issues, but Mazout's kernel doesn't seem to be loading. I get a "Problem loading widget" error. What might I be doing wrong?
What is the most stable version of ICS/Jelly Bean available for the Wind G2X? I read that the phone finally got an official update for ICS from LG. Where can I get this rom? What ICS Rom's have you had the best performance with? Without compromising on important features like audio/camera, etc.
Your expectations are much too high. This phone barely has cm7 working with minimal bugs. Sorry to disappoint.
LetThisNightExplode said:
What is the most stable version of ICS/Jelly Bean available for the Wind G2X? I read that the phone finally got an official update for ICS from LG. Where can I get this rom? What ICS Rom's have you had the best performance with? Without compromising on important features like audio/camera, etc.
Click to expand...
Click to collapse
Sadly, if you had an O2X (p990), you would be in business.
With the G2X (p999), you are not going to get an ICS/JB Rom without serious compromise. You either give up hardware accelleration, battery life, video recording with hackfests -- or you give up the ability to make/receive calls/use cellular data on the 10.1 from mazout, etc.. There does not exist an ICS/JB Rom that is an acceptable daily driver on the G2X - it simply doesn't exist.
I hope you didn't just buy that phone, cause you got ripped off if you wanted ICS/JB.
lotherius said:
Sadly, if you had an O2X (p990), you would be in business.
With the G2X (p999), you are not going to get an ICS/JB Rom without serious compromise. You either give up hardware accelleration, battery life, video recording with hackfests -- or you give up the ability to make/receive calls/use cellular data on the 10.1 from mazout, etc.. There does not exist an ICS/JB Rom that is an acceptable daily driver on the G2X - it simply doesn't exist.
I hope you didn't just buy that phone, cause you got ripped off if you wanted ICS/JB.
Click to expand...
Click to collapse
The words "acceptable daily driver" are opinion really. I use Tonyp's Jellybean Hackfest build 9 and the newest version of mazouts kernel and smooth performance, and battery life that lasts me through the day. It has never crashed for me or rebooted either.
But then again, I don't care about video recording so I didn't even know it didn't work. And what does not having hardware acceleration really ruin anyways? I don't really see the point of watching Netflix on a 4 inch screen anyways.
But like I said, its all just opinion. You should try a few different ROMs with different kernel combinations and see what works for you.
Sent from my LG-P999 using xda app-developers app
[Re] [Q] Most stable p999 4.0+ version?
As someone who has gone through all the ROM's for the G2X as a wind user like you, I found that Paranoid Android build 12 worked the best for me because it was the only ROM that was stable for more than a month, didn't get worse performance over time, and could actually make phone calls unlike all the other ROM's.
advise pls
Jackaro said:
As someone who has gone through all the ROM's for the G2X as a wind user like you, I found that Paranoid Android build 12 worked the best for me because it was the only ROM that was stable for more than a month, didn't get worse performance over time, and could actually make phone calls unlike all the other ROM's.
Click to expand...
Click to collapse
hey jackaro
i have 2 wind p999's in use by family members - mainly for phone calls, gmail app, photo/video cam and youtube app usage.
both phones are unrooted 2.2 as bought from wind in dec 2011. could you advise if its better to root and use paranoid build 12 or stay away from all of these ics versions and goto a 2.3/cm7 version which is more stable
planning on using both devices for daily use atleast till end of 2013
thanks for the advise
Hanesmart said:
hey jackaro
i have 2 wind p999's in use by family members - mainly for phone calls, gmail app, photo/video cam and youtube app usage.
both phones are unrooted 2.2 as bought from wind in dec 2011. could you advise if its better to root and use paranoid build 12 or stay away from all of these ics versions and goto a 2.3/cm7 version which is more stable
planning on using both devices for daily use atleast till end of 2013
thanks for the advise
Click to expand...
Click to collapse
Although I am not a Wind G2x user; (I have T-Mobile) I recommend moving off of 2.2 Froyo and moving up to at least Gingerbread 2.3 CM7 Release. If you want stablility, go with CM7. If you can deal with no video recording and HWA/minor bugs try ICS/JB.
I'm currently running eaglesblood ICS 4.0.4. Everything works exceptionally EXCEPT video recording and wi-fi calling. Everything else is awesome. The phone is faster and smoother than it was before I flashed eaglesblood. However, I do occasionally use video recording and wi-fi calling so I plan on flashing hellfire which is based off CM7. I'm sure I'll be happy being able to record videos again but honestly I'm going to miss the crisp performance enhancement that I am currently getting with ICS eaglesblood.
Pain-N-Panic said:
I'm currently running eaglesblood ICS 4.0.4. Everything works exceptionally EXCEPT video recording and wi-fi calling. Everything else is awesome. The phone is faster and smoother than it was before I flashed eaglesblood. However, I do occasionally use video recording and wi-fi calling so I plan on flashing hellfire which is based off CM7. I'm sure I'll be happy being able to record videos again but honestly I'm going to miss the crisp performance enhancement that I am currently getting with ICS eaglesblood.
Click to expand...
Click to collapse
I strongly recommend vanilla CM7 from get.cm over the Hellfire stuff.
Sent from my glorified LG pet rock™
justjackyl said:
I strongly recommend vanilla CM7 from get.cm over the Hellfire stuff.
Sent from my glorified LG pet rock™
Click to expand...
Click to collapse
Definitely agree. Stock cm7 or teaser language are the only choices worth considering. Or, and for MIUI, Singh, but wide calling g might not work depending on your SIM card.
Sent from my LG-P999 using Tapatalk 2
Yup, jackyl convinced me on the CM7 latest nightly build. I already have it downloaded but haven't flashed it yet. I also take back everything I said about EB working properly....ironically about 20 minutes after I made that post I was getting all sorts of issues with my t-mobile network. 4g unavailable and "invalid sim" errors. I eventually reflashed it and so far its working smoothly again (hopefully I didn't just jinx myself....). Right now I'm just reading up on mazout and faux kernals to decide which one I would like to flash alonside CM7.
If you think you'll miss the ICS/JB flavour, checkout the dual boot option that Mazout has put together. I'm running dual boot with the latest (well, March anyway) vanilla CM7 as a daily driver with JB 4.2.2 on the other partition, and it is awesome!
Sent from my LG-P999 using xda app-developers app
Pain-N-Panic said:
Yup, jackyl convinced me on the CM7 latest nightly build. I already have it downloaded but haven't flashed it yet. I also take back everything I said about EB working properly....ironically about 20 minutes after I made that post I was getting all sorts of issues with my t-mobile network. 4g unavailable and "invalid sim" errors. I eventually reflashed it and so far its working smoothly again (hopefully I didn't just jinx myself....). Right now I'm just reading up on mazout and faux kernals to decide which one I would like to flash alonside CM7.
Click to expand...
Click to collapse
Not to add fuel to the fire, but I like the Trinity ELPMax and T15Max series... ELP for stability/battery life, T15 for speed. Though, if you do much gaming you might not want the max as it steals some GPU memory to give to regular system memory.
lotherius said:
Not to add fuel to the fire, but I like the Trinity ELPMax and T15Max series... ELP for stability/battery life, T15 for speed. Though, if you do much gaming you might not want the max as it steals some GPU memory to give to regular system memory.
Click to expand...
Click to collapse
Trinity is ok kernels as well, although for me, Trinity series gave me more issues with gaming performance, video recording, and that dam "invalid SIM " error for Wifi calling.
These issues occured on all custom kernels, but Faux and mazkrn were less severe for me.
Sometimes I'd have to completely power cycle the phone to get the invalid sim error to clear, whereas on faux and mazkrnl I usually only have to cycle airplane mode once or twice to clear the invalid sim error, and since Pain needs wifi calling to work, I did not recommend Trinity series due to that one problem. Not saying at all that Trinity is a poor kernel, just others excel where it falls short, but its vice versa on other things.
Install Mazkrnl or Faux and than undervolt to the ELP series voltages.
Its really about user preferences, Pain, you'll just have to keep testing till you find what works for you.
Good news is you can dirty flash a kernel, just wipe cache and dalvik cache before you flash it, but you won't need to do fresh setups anytime you want to change kernels.
Sent from my glorified LG pet rock™
Nice. Yup I definitely need wifi calling and video recording to work. I don't play games on my phone often but I need the video recording to settle disputes on game battles when competing in call of duty
Sent from my LG-P999 using xda app-developers app
justjackyl said:
Trinity is ok kernels as well, although for me, Trinity series gave me more issues with gaming performance, video recording, and that dam "invalid SIM " error for Wifi calling.
Click to expand...
Click to collapse
Just to clarify, do you know of ANY kernels that don't give the invalid SIM error on MIUI? I just switched to Mazout's kernel to see what it was like. Was surprised to see that what he's calling "Ram OC" is actually the GPU carvout, so that version has 404mb Ram just like Trinity MAX series. But I still get unknown phone # in status (and thus invalid SIM from WiFi Calling)...
lotherius said:
Just to clarify, do you know of ANY kernels that don't give the invalid SIM error on MIUI? I just switched to Mazout's kernel to see what it was like. Was surprised to see that what he's calling "Ram OC" is actually the GPU carvout, so that version has 404mb Ram just like Trinity MAX series. But I still get unknown phone # in status (and thus invalid SIM from WiFi Calling)...
Click to expand...
Click to collapse
Maz actually doesn't habe a carveout.
We discovered a bug where if you flash a trinity kernel and than a maz kernel, it will display the carveout from trinity.
Is this by chance something you may have done?
As for MIUI, I didn't like any MIUI soley because I could never get wifi calling to work.
Sent from my LG-P999 using xda app-developers app
justjackyl said:
Maz actually doesn't habe a carveout.
We discovered a bug where if you flash a trinity kernel and than a maz kernel, it will display the carveout from trinity.
Is this by chance something you may have done?
As for MIUI, I didn't like any MIUI soley because I could never get wifi calling to work.
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
Ahh, that's very very odd... Yes, I did flash Maz after Trinity... Now the discussion about whether the carveout is in the init.d scripts makes a lot more sense.
It's clearly NOT in the init.d scripts... however there are scripts inside the kernel image itself that are non-binary. They are supposed to be replaced any time a new kernel image is flashed, as you're flashing the whole image and not the binary within the image... But again, the carvout is changed in the kernel makefile, not in those scripts.... so that's very odd. Of course, my failure to successfully CHANGE the carveout back when I was building my own kernels (for Tsugi) based off of Faux's work now makes more sense as well - obviously there is somewhere that it is changed also that I wasn't aware of. I wonder if that place is where Maz's kernel is picking this up.
Honestly, if I knew where else it could be changed, I'd kang the kernel and build it myself, because I prefer having the extra system RAM versus GPU ram.
The question now is, that 404mb that shows on Maz after flashing Trinity... is that much actually available, or is it a mere artifact and not really there? Because my free memory seems to hang around the same place as it did with Trinity. Makes me worry about stability if something actually tries to _use_ that memory. I wonder if that's why some users have crashing with Maz?
*thinktank mode off*
Ive been trying all day to get CM 7.2 and previous "stable" releases to work and I have had no luck, they all just get hung up on the LG loading screen and I have to reflash it and start over again. Finally decided to just go back to stock 2.3.4 and faux123 kernel.
That's weird spawn. Weapon 2.3.3 is a pretty stable rom from what I hear. Have you tried that one?
Sent from my LG-P999 using xda app-developers app