yashsingh1/xdaforums huggingface dataset:
[T-Mobile LG G2x] Pain-N-Panic:
That would be great!!!!!
[T-Mobile LG G2x] iLovPieNCake:
What exactly is broken with bluetooth? Mine works just fine with streaming to my friends car and this weekend I'm gonna test connecting a ps3 controller.
[T-Mobile LG G2x] n30wav3:
Its Bluetooth calling that doesn't work
[T-Mobile LG G2x] mansa_noob:
Two different problems.

1. Audio routing through Bluetooth on newer baseband with anything other than stock does not work.

2. The problem I described above. Has nothing to do with the baseband but with power management and keepalive.
[T-Mobile LG G2x] redmonke255:
Alright well I found I have huge battery drains when WiFi is on. I understand WiFi uses more power, I went from lasting 9 hours to lasting 14 hours with WiFi off most of the day. Thinking there's something else going on here.

I'll get a log this weekend, best way to go about doing it?
[T-Mobile LG G2x] n30wav3:
R u on cm7 or hackfest? And if on cm7 which network r u on, HSPA,HSPA+ or plain 2g/3g?
[T-Mobile LG G2x] EEngineer:
Using Mazkrnl_0323GBOCnoDS:

During a call I can not adjust volume from my Bluetooth headset. I have to use the volume buttons on my G2X.

I can adjust volume from my Bluetooth headset fine when listening to music.

Bluetooth headset = earphones only, using phone's microphone.
[T-Mobile LG G2x] redmonke255:
Cm7. Usually on hspa+, but I don't use data (2G has a lot of dead spots in my campus).
[T-Mobile LG G2x] EEngineer:
Update: after testing Bluetooth, now I'm getting a buzzing sound from the phone's speaker while not doing anything.
[T-Mobile LG G2x] n30wav3:
Oh that's why.... otherwise u would love wifi inplace of data as hspa+ data uses hell of a battery life
[T-Mobile LG G2x] redmonke255:
I said I don't use data. It's turned off.

While I don't use my phone as much with wifi off, it's not to the extent where the change in battery is four hours.

I used my phone in bed for two and a half hours only on reddit is fun. Went down to 30%.
[T-Mobile LG G2x] n30wav3:
That's what I meant .... that if u would have used data u wouldn't say wifi drains battery as data uses much much more... anyway if u r saying two hours drained it to 30% from 100%... ill say that's alot
[T-Mobile LG G2x] mansa_noob:
Maybe a rogue app? Use something to figure out who is eating the battery.
[T-Mobile LG G2x] towelboy:
Try using monitering apps such as Watchdog to see what apps are causing the most trouble
[T-Mobile LG G2x] Mazout360:
I'm done with my next experimental release, thanks to the logs I received here!...expect it to be hosted here tonight or tomorrow if there's no stability issues.

First results are promising...I updated-reworked the suspend code, changed the RCU (seemed like it was causing kernel panics as per n30wav's log) and updated the wifi driver (yeah, again) with newer functions such as TX power control (which could help saving battery). I also reworked the whole DM/block drivers to eventually update ROW (and get rid of the veeeeeery long first boot), which is why I want to make sure everything works properly before releasing a "stable" official version.

Expect the upcoming changelog to be quite big

Thanks to every tester!
[T-Mobile LG G2x] EEngineer:
Maz, you are the MAN!
[T-Mobile LG G2x] Pain-N-Panic:
Thank you much sir! Will this release be over clockable?
[T-Mobile LG G2x] justjackyl:
This is why I blocked that kid.

He don't wanna listen to no one. lol
[T-Mobile LG G2x] mansa_noob:
Thanks Maz. I am sure it would be awesome.

Out of curiosity, how do the suspend functions affect Bluetooth? With an active connection in progress does it change keepalive frequency or am I not making any sense here (wouldn't be the first time :D).
[T-Mobile LG G2x] n30wav3:
:rolleyes: feels like a dream coming true for me finally.....
[T-Mobile LG G2x] EEngineer:
Maz, I'm curious do you do anything with the camera drivers in the kernel?

My G2X's camera is very very important to me, I attend trade shows and events and use my G2X camera all the time.

I use LG Camera Pro and I think it's the best. My only issues with the G2X camera is that auto-exposure needs tweaking, and you can't use zoom while taking videos.
[T-Mobile LG G2x] Mazout360:
I know I said yesterday that I would release an experimental build today, but I have some concerns with the newer updates and there are still some inconsistencies that could lead to data corruption. I do not want anybody's phone to get bricked by a beta kernel and that's why I'll release the experimental build only tomorrow or sunday. Sorry for the delay, but I'll work on it tonight...

Oh yes!

It should not affect bluetooth. I'll need a logcat/kmsg if there's something wrong there.

Zooming works perfectly here. What ROM/kernel version are you using ?

I'll see what I can do with auto-exposure.
[T-Mobile LG G2x] Pain-N-Panic:
Take your time boss! We appreciate the update!
[T-Mobile LG G2x] EEngineer:
Thanks. The zoom doesn't work WHILE taking a video. I can set the zoom before I start taking the video.

My ROM and kernel is in my signature, CM7 Nightly-20130301/Mazkrnl_0323GBOCnoDS
[T-Mobile LG G2x] mansa_noob:
+1 to that. I just experimented with it today with the same result. Mine is cm7.2 with your experimental build kernel.
[T-Mobile LG G2x] adamiscool:
Did the zoom ever work while recording? I don't remember if it did even on stock Rom.

Sent from my HTC One (M7)
[T-Mobile LG G2x] EEngineer:
I don't know if it ever did - I don't think zoom ever worked while recording video. I've had other phones that did. It might be a limitation of the G2X.

A G2X that allows zoom while recording video would be amazing.
[T-Mobile LG G2x] pmorrsn:
I also don't think that ever worked, though I am now on faux 54.
[T-Mobile LG G2x] kesara:
That's correct. Zoom never worked while recording
[T-Mobile LG G2x] iLovPieNCake:
It's funny because it's only a software limitation. Code it in and we should have enough processing power for that to work.
[T-Mobile LG G2x] mansa_noob:
I would have bet one of the miui or LewaOS have it. I am pretty sure I have used it before. Need to look.
[T-Mobile LG G2x] Mazout360:
As promised, here's something to play with.

This is the second and last experimental build before the stable release (well I hope so). There's no "new userspace features", but it's a massive update nonetheless. There are a lot of updates concerning : RCU, librairies, processor, block, MD, wifi driver, mmc, scsi, power management, memory management and, of course, suspend/wake up functions. I never had a SOD and every reboot to system or recovery worked perfectly. Overnight battery use takes about 3-4% with WIFI enabled, so the suspend code seems to be working well.

Every build is for CM7 only. I will maintain the hackfest version when I'll be sure everything works properly.

CM7 - STOCK VOLTAGE : HERE

CM7 - STOCK VOLTAGE - No WIFI deepsleep : HERE

CM7 - OVERCLOCKABLE : HERE

Warning - This is an experimental build. New updates are now being tested for compatibility and efficiency, and there should not be any stability issues. Though, as always, I am not responsible for any damage related to the use of these kernel builds. Also, be aware that I do not test OC or NoDS versions by myself.

I will release the full changelog with the stable release, as I'm still working on new features to add.
[T-Mobile LG G2x] Pain-N-Panic:
Thank u much sir! We all appreciate your hard work!
[T-Mobile LG G2x] EEngineer:
I am physically aroused.
[T-Mobile LG G2x] mansa_noob:
No issues so far. CM7.2 stable with the OC kernel and July baseband. OC at 1.55 GHz.

---------- Post added at 06:29 AM ---------- Previous post was at 06:10 AM ----------

Dropped down to 1.4. Phone was getting too hot :).
[T-Mobile LG G2x] n30wav3:
I haven't used stock for a while but I remember that zooming while recording video has always worked on Stock roms only never on cm7... starting from froyo
[T-Mobile LG G2x] EEngineer:
Well, this has never happened before.

On Mazkrnl_0323GBOCnoDS, CM7 Nightly March 1, Screen lock is turned off. I plugged my G2X into the charger with 26% battery left. Came back maybe 20 minutes later, pressed the power button to check my phone, no response. If this is a SOD it's my first time.

Pulled the battery, Phone screen, and battery are warm. Let everything sit and cool down for 5 minutes,then re-inserted and started up. Battery shows 39%. Now, this is strange, normally when I turn the screen lock off, on boot it always resets itself and boots to the screen lock. Not this time, it boots to no screen lock.

Phone uses SetCPU, 1.1GHz max for normal usage (I have profiles that go to 1.5GHz for multimedia and cameras).

Screen Off profile is 216MHz to 503MHz.
[T-Mobile LG G2x] Pain-N-Panic:
with maz kernels i have to have my phone set to "stay awake" while charging. Otherwise it heats itself up into a SOD as you described
[T-Mobile LG G2x] m3mb3rsh1p:
Thanks for the new test release. I still can't play some games (e.g. Vector) with it, though.

It seems I have a bad phone because my battery drains very quickly. I can't get over 12 hours in airplane mode on any kernel.

It could be that I'm using bad batteries but even with my 3500mah batteries, the most I've gotten is 16 hours standby.

This is the most annoying thing about my G2x. How could LG/Nvidia screw up something so simple?!
[T-Mobile LG G2x] hairycheapo:
Sounds like you are certain it is not an issue with your battery. Are you certain that it's your hardware? Maybe a rouge app is using power? Do you have wakelocks? I use Better Battery Stats - free. The 2X2 widget displays Kernel Wake Locks (KWL) as well as Partial Wake Locks (PWL). In standby mode my wakelocks are less than 1 minute per hour. In fact, overnight my wakelocks are usually less than a minute per 8 hours.:)

The latest "experimental" build is working great so far for me. Maz - I think you've got the WiFi suspend sorted! I am running the OC version at 216-1100. I left the WiFi on overnight and only used 3%. It took 3 or 4 seconds and I was surfing the Web again - without toggling the WiFi.

Me too.
[T-Mobile LG G2x] Mazout360:
That's what I think too. Make sure the game (Vector) or any other useless/unstable app don't get stuck in memory (Settings -> Applications -> Manage applications (and services)). Something seems to be draining battery there.

Is overnight charging with the non-OC build works without "stay awake" enabled ?
[T-Mobile LG G2x] Pain-N-Panic:
I don't know but I'm not willing to test it lol
[T-Mobile LG G2x] thraizer:
Weird, I can't seem to install the oc version. It would double reboot on the blue lg logo and then once it gets to my lockscreen it would freeze and reboot again. So I tried the non oc version and it boots fine. Oh well, looks like I'm sticking to the non oc version. Where do I find the "stay awake" option when charging?
[T-Mobile LG G2x] Pain-N-Panic:
Applications > development > stay awake
[T-Mobile LG G2x] grantusmantus:
Running the latest no DS. Will report any oddities. I don't think ill have a problem though.

Thanks again Mazout.

sent from my p999

Nilla cm7 monthly

Mazouts latest.
[T-Mobile LG G2x] n30wav3:
Me too running the latest experimental OC.... will report if I find an SOD... I will need to test it for two three days to confirm
[T-Mobile LG G2x] mansa_noob:
Running latest OC experimental. Charge to 100% without SOD. Well try again to SOD tonight.

Edit: battery life seems to have been reduced a bit on Wi-Fi and active use. Wi-Fi didn't go into suspend with screen off.
[T-Mobile LG G2x] Pain-N-Panic:
Wifi definitely eating battery a little more. Battery stats showing that it wasn't suspended either with screen off. I also have frozen twice during aa reboot. Both times after booting by removing the battery and hard booting, my CPU settings were changed and maxed out to 1.5 where from having it set at 1.1

---------- Post added at 04:00 AM ---------- Previous post was at 04:00 AM ----------

I'm reading up on how to take kernel logs. Going to try catching it in a freeze while rebooting with a log going

EDIT- Currently running KMSG log. I'll post it here if anything funky happens!
[T-Mobile LG G2x] n30wav3:
Not sure if its a good thing or not wifi not dropping during suspend... for me its good as i have set my wifi policy to stay awake all the time... still i m getting a very cold and nice battery feeling with this one.... but as i said earlier... cant decide in just few hours
[T-Mobile LG G2x] mansa_noob:
Hi Maz, using the OC build it died after almost 18 hours. Wasn't being charged when it happened. It never came out of an off screen state, so not sure if it qualifies as an SOD, but just in case I am attaching the log.

Note: Will attach from web in a minute.

Edit: Log attached. Running on CM7.2 stable with latest experimental build.

Sent from my soon to be awesome android!
[T-Mobile LG G2x] Mazout360:
I forced a SOD and debugged it....bad news I'd say. I just rediscovered an oooold G2X/O2X issue (veteran users here would probably know what I'm talking about)

"cpufreq--dvfsd"

That piece of s*** was created by...guess who...no, not LG...Nvidia. Yay! And even better : it's flawed and it always was. EVEN BETTER : the original source code for most of the functions used in this "kernel task" are not available publicly. So sad.

You know what ? I'm getting pis*** right now. I worked on the radio then BAM! Nvidia. I worked on HWA then BAM! Nvidia. Now, I work on SODs and BAM! !@#%&? Nvidia again.

I'll just leave that here : www . youtube . com/watch?v=IVpOyKCNZYw

EDIT: Sorry for this post but I needed it...I'll keep working on this kernel nonetheless. If anybody has the chance to find a fix for this thing on older 2.6.32 tegra2 kernels that would help, because I couldn't figure out what's wrong exactly yet.
[T-Mobile LG G2x] C-art-toon:
Don't be sorry buddy. so frustrating each time you worked so hard the wall Nvidia smash you.... you do amazing job anyway!
[T-Mobile LG G2x] Волк:
OC Version worked fine for me.
[T-Mobile LG G2x] hairycheapo:
I too am having no problem with OC version. Somebody remind me about the Faux LG (low grade) kernel. Did it boot up using a little less maximum MHz? Maybe some people's hardware could benefit from a similar Low Grade version of this OC kernel. As though Maz doesn't already have enough to work on:eek:
[T-Mobile LG G2x] vampyro:
you are really doing a great job i think you should teach those guys from lg an nvidia.. you are way better thankz for all the time you put on our device..
[T-Mobile LG G2x] Волк:
Iirc, the LG version wasn't overclockable and was stock voltage. I believe the non-oc version is an acceptable substitute.

On a disrelated note, using wifi tethering fails with an error.

Kernel: latest experimental oc build

ROM: Teamensk latest (which is like from november)

Log cat: http://db.tt/WLNDejB3
[T-Mobile LG G2x] mansa_noob:
Maz a quick search was not very helpful. What does this thing do? All I understood was that it does dynamic voltage frequency scaling. If that is correct then this thing is at the heart of "on demand" and so occasional glitches are not surprising but exception handling is (otherwise it would not BSOD).

The Google search suggested that the issue plagued a small fraction of devices, but I have never seen anyone here state they don't have BSOD).

Anyways, assuming some have hardware that is weak and can't handle the poorly written code, can you try a little trick to see if the failure can be reproduced (on the phone that showed this issue)? The trick would be to raise the core voltage a bit and see if the issue disappears when forcing a BSOD!

May also be a different timing issue in which case reducing the voltage may do the trick.

If it works then we have a working bandaid :D.

Sent from my soon to be awesome android!
[T-Mobile LG G2x] n30wav3:
That's exactly what I wanna say. It was my log that showed the kernel panics with SOD but its been 24 hours now since I installed this kernel and I haven't exeprienced an SOD... still I will test one and a half day more.

As for the cpufreq thing.... mansa is right. According to LG it only effected only some of the devices.... which was also resolved by an update from LG later..... and also if u think if that issue still persist... shouldn't that be happening on all of the kernels? Cuz I haven't experienced any of these SODs on Trinity kernels... it was always the faux kernels which had SOD for me.... Mazo u said u deliberately forced an SOD. Maybe that's not the criteria for SODs happening to us.... I would really love to continue my testing for two more days on this one.... as I am having a feeling u have resolved the SOD due to kernel panics.

For everyone I want to mention there were always two kind of SODs I was pursuing. One when the phone was on charge with awake while charging switch off the other one was just random during call or suspend SOD. The charge one was resolved easily by keeping it awake and I am not testing that one right now... it was the other one which was pain in the ass....but i dunno why my gut says 50% m sure that it had been resolved with this new one...

One more thing Mazo... difference between urz/faux and Trinity is also the underclocking....maybe underclock helps in reducing the SOD u r talking about.... I have used both XLP and ELP for Trinity ... and never experienced any SOD.... it was always Harsh and faux..... I think there should still be a long way to go before a Dev like u should start cursing this device... I agree its ****ty... but man u r the last hope to make this at the very least a perfect GB device
[T-Mobile LG G2x] mansa_noob:
As n30wav3 said in the above post regarding two types of BSOD. I too have been testing but for both. I turned off stay awake since the first experimental build and haven't had the changing BSOD yet. The other one (phone dies with no apparent reason, I.e. does not come out of suspend) has happened on both for me. I can't understand the log due to my noobish ways but don't believe it has anything in it.

Sent from my soon to be awesome android!
[T-Mobile LG G2x] n30wav3:
I just checked ur log.... its ending is different than mine.... are u sure this wasn't an isolated incident from any app? Have u experienced the same SOD again? Also check what frequency ur CPU is on right now.....
[T-Mobile LG G2x] mansa_noob:
2 logs, both the same way (experimental builds 1 and 2). Could be an app but no way to check that (at least not easily). Frequency was set to max (1.55) in both cases, stayed at that after the battery pull.

Right now I have intentionally dropped frequency to rule out hardware not playing well with high OC state. Set to 1.1 now and waiting :).

Sent from my soon to be awesome android!
[T-Mobile LG G2x] n30wav3:
Yeah u should drop it... mine is normal 1015.... cuz as far as I can see ur log there is no odd behaviour at the end so extreme overclock might be an issue seeing that this kernel is stock voltage not underclocked... I hope u dun get SOD on 1.1 or 1015
[T-Mobile LG G2x] mansa_noob:
Damn. Just died again at 1.1G. I was so sure it won't that I did not start the kmsg logging either.

O' well. I guess next time's the charm :)

Edit: I noticed that the frequency reverted to max after battery pull. Not sure why. I have reduced it to 1015 as you suggested. Let's see what happens.
[T-Mobile LG G2x] god123456:
I found something maybe useful

http://morfic.euroskank.com/git/?p=...it;h=878aac479725a31080b7dedc6acda20ed2be89ec

this is from morfic's p999 kernel

maybe this git can answer why Trinity has no bsod

i hope this can help Mazout360
[T-Mobile LG G2x] n30wav3:
I m sure it should be but just confirming have u checked the set on boot option or not?
[T-Mobile LG G2x] mansa_noob:
Yeah, I just realized that is the case. Why else would it do that :D

Sent from my soon to be awesome android!
[T-Mobile LG G2x] Mazout360:
Oh thanks for this I'll try it.

Faux fixed SODs by removing sys_sync, making sure the kernel won't return "Scheduling while atomic" panics (enabling it forced the SOD in my case). Maybe cpufreq-dvfsd doesn't play well with overclocking too. I did a quick search on this yesterday and some older devices, such as the Vega if I remember well, had similar problems.
[T-Mobile LG G2x] mansa_noob:
Maz I don't think that it doesn't play well but rather we need to teach it to play outside the characterized and optimized range envelope.

Since we don't have the code we have to fix it by adjusting the parameters it uses from outside. Typically these are voltages and transition times.

Just my g2x ;).

Sent from my soon to be awesome android!
[T-Mobile LG G2x] Mazout360:
** link removed **
[T-Mobile LG G2x] EEngineer:
Using Mazkrnl_0323GBOCnoDS

Don't know if this means anything, but my normal charging procedure is I ALWAYS charge to 100%, then disconnect the charger and turn my G2X off. I leave it off for about five minutes, then turn it on. I've never had a SOD following that procedure. Stay Awake while charging is not enabled.

The one SOD I ever got was last week when I did partial charges, not to 100%, and didn't turn my G2X off.
[T-Mobile LG G2x] Pain-N-Panic:
Why are you turning off your phone after you charge it?
[T-Mobile LG G2x] Bytetheft:
Read his post.
[T-Mobile LG G2x] mansa_noob:
Frequency vs. voltage curve -- Overclocking revisited

Sorry Maz, I am not trying to hijack your thread so if you want I can create a new one. However since I am playing with your kernel (thank you very much for it) I figured I should post here.

WARNING: Setting voltage incorrectly can have undesirable consequences, least of which is a destroyed device. In the worst case scenario you may start WWIII due to a corrupted twitter post. If you are a noob like me, read but don't follow, unless you take full responsibility for your actions.

Note: This is NOT a scientific attempt. Any success would be a complete fluke!

Looking at the frequency vs. voltage curve IMHO it seems the values may have been a tad bit higher than needed, soooo I am currently testing the following set (putting here so if someone else wants to give it a try they will have the values):

F (MHz.)	Current Voltage (mV)	New Voltage (mV) Actual Implemented (mV)

216	800	800 800

503	850	825 825

816	900	900 900

1015	980	980 980

1100	1080	1020 1030

1216	1180	1080 1080

1408	1280	1200 1205

1552	1380	1300 1305

I chose these values as a quadratic extrapolation of the 216 to 1015 range (after correcting the 503 MHz. case -- LOL). Also the actual implemented is a bit different due to the tool I am using (CPU Tweaks). I tried setting (say) 1300 but it rounds it to 1305. Not sure why.

I have attached a chart showing the curves if someone is interested.

If these voltages hold we should be able to safely overclock and reduce power doing so :angel:. The dynamic power cost is C*V*V*f, so expected savings should be significant, especially in the highest frequency range.
[T-Mobile LG G2x] EEngineer:
Stability

A regular shutdown and restart (not just a reboot) is good for your smartphone's stability, just like any computer.

I just happen to choose whenever I charge to 100% because it keeps my battery's hours-since-full-charge statistics.
[T-Mobile LG G2x] Darkknight512:
It should not be a problem at all though, uptime on my phone 215 hours and counting. No issues. Not saying there is anything wrong with your practice though, just seems a bit unnecessary.
[T-Mobile LG G2x] EEngineer:
I'm curious - would having your phone turned off for five minutes bother you?
[T-Mobile LG G2x] n30wav3:
Nahh its not that.... the only problem with this solution is that it can only be done when u are free...not when u r on the go .... quickly want to call/charge etc.... that's why a more permanent solution is needed

By the way guys.... AND MAZO... 48 hours ... NO KERNEL PANIC SOD whatsoever..... I think u have finally done it man... I know my usage and my device... it should have SODed by now.... I still have to check the SOD when charging by turning off the stay wake....but the casual suspend SOD is GONE! ..

The only thing I want to mention is slightly decreased battery..... but really I love what u did with RCU .... I am also looking at mansa's underclocking .... if mazo can confirm that it is not effecting the stability OR if he can get the same 323 OC battery life back.... I think I just found my ultimate kernel here