yashsingh1/xdaforums huggingface dataset:
[G2 Android Development] tdawgg777:
I reflashed it also. Wiped cache and dalvik, but also reflashed rom... and everything is working good.
[G2 Android Development] ndybucky:
no sensor problems here, r24, 27/10 mahdi d802.... great kernel!
[G2 Android Development] MBurns2:
i tried the latest version on latest slimkat, i was stucked on the lg logo..how can i solve ? thanks a lot
[G2 Android Development] enr88:
Reflash the ROM, the latest slimkat are based on hybrid source For rom and kernel(4.2) that why u result in a bootloop.

For use Render Kernel u must flash KitKat Based ROM like Liquidsmooth or Aicp

Inviato dal mio LG-D802 con Tapatalk
[G2 Android Development] RenderBroken:
I believe that is becasue they are now using JB source for their kernel and I use KK. Just like the CM delima. Sorry.
[G2 Android Development] RenderBroken:
Glad to hear. This was bugging me like no other lol.
[G2 Android Development] RenderBroken:
Looking through the log, I found a CRC error. In my experience with the G2, I usually have seen reboots soon after that. Not sure what the problem is but I don't think it a widespread issue and may just be a device problem. I dont expect it to mean your phone is failing but with every memory read/write (HDD, SDD, ETC) You will always have CRC errors from time to time. BUT if you have more please share the logs. Thanks!
[G2 Android Development] MrDarkKV:
It seems to work today... Strange, I haven't changed anything.
[G2 Android Development] Ace42:
Thank as well. I learned about it awhile ago, but saw that no one was including it alongside the other qualcomm stuff. Also no issues with bacon, it definitely performs better than optimax for me at least. Raising the min cores to 2 could help those with lag, noticed it tends to have 3 sleeping cores even when I had firefox in the background.
[G2 Android Development] RenderBroken:
I tried to build it yesterday but ran into numerous build errors. There are dependencies I will have to accommodate for. I will continue to see if I can work it out. I want to try it out. Thanks!
[G2 Android Development] :
Using R24 I get spammed with the following in my logcat:

E/Sensors ( 242): sns_acm_mr.c(609):Request made to disabled service
E/Sensors ( 242): sns_main.c(1298):Error writing request. sns_err 3 error 0 qmi_err 0
E/Sensors ( 242): sns_acm_mr.c(609):Request made to disabled service
E/Sensors ( 242): sns_main.c(1298):Error writing request. sns_err 3 error 0 qmi_err 0
E/qcom_sensors_hal( 841): hal_process_sam_sensor_thresh_resp: Msg 0; Result: 1, Error: 3
E/qcom_sensors_hal( 841): hal_process_sam_sensor_thresh_resp: Msg 2; Result: 1, Error: 3
E/qcom_sensors_hal( 841): hal_sam_thresh_activate: Unable to enable thresh
E/qcom_sensors_hal( 841): hal_acquire_resources: Failed for handle 31 @ samp 20 Hz rpt 0 Hz WuFF 0 batched 0

It looks like whatever is causing this is making it so that the sensors service can never start as I get this in R23, but I never see it in R24... In R23 I see this when the service starts, R24 never prints this.

D/SensorService( 842): nuSensorService starting...
I/SystemServer( 842): Entered the Android system server!
I/SensorService( 842): LGE Accelerometer Sensor Accelerometer
I/SensorService( 842): AKM Calibration Lib
I/SensorService( 842): LGE Magnetometer Sensor Magnetometer Uncalibrated
I/SensorService( 842): LGE Gyroscope Sensor Gyroscope
I/SensorService( 842): LGE Gyroscope Sensor Gyroscope Uncalibrated
I/SensorService( 842): LGE Proximity Sensor Proximity
I/SensorService( 842): LGE Light Sensor Light
I/SensorService( 842): Gravity
I/SensorService( 842): Linear Acceleration
I/SensorService( 842): Rotation Vector
I/SensorService( 842): Significant Motion Detector
I/SensorService( 842): Game Rotation Vector
I/SensorService( 842): Orientation
I/SensorService( 842): AMD
I/SensorService( 842): RMD
I/SensorService( 842): VMD
I/SensorService( 842): Basic Gestures
I/SensorService( 842): Facing
I/SensorService( 842): Tilt
I/SensorService( 842): Gyro Tap
I/SensorService( 842): Pedometer
I/SensorService( 842): PEDESTRIAN-ACTIVITY-MONITOR
I/SensorService( 842): Motion Accel
D/SensorService( 842): Max socket buffer size 1048576
D/SensorService( 842): nuSensorService thread starting...

I can attach the full logcats, but I have tons of other spam in there since these aren't clean installs.
[G2 Android Development] Formhault:
So I was watching a YouTube video and had to stop it to go do something. I turn the screen off and 3 minutes later I come back to the phone which was warm and unresponsive.

Well, at least the screen was unresponsive. Plugged in the charger : phone vibrated and the LED turned on.

Had to force reboot. Afterwards, I launched Synapse to grab a log. But... :eek:

10/27 LS on D802. Anyone else had this happening?
[G2 Android Development] RenderBroken:
I will take a look. Thanks for the info!

At this point, since there is so much customization now, everyone needs to post what their changes are when posting about an issue. This will help narrow done possible areas for problems. I will probably just need to fix the code for making a logcat and check the others as well. I still use Syslog for ease of use.
[G2 Android Development] RenderBroken:
[MENTION=4231562]Yoinx[/MENTION]

Also is this installing R24 right on top of R23? Or a clean install of a new rom too?
[G2 Android Development] :
Dirty installing the two back and forth. Had r23, installed r24. See the issues, grabbed logs from 24 flashed 23 for logs, reinstalled 24. I try to avoid adding extra variables.

I could try on a clean rom install. But I doubt that will make a difference, as that wildvine driver is liking for doesn't exist in the g2... Its a nexus thing if I'm not mistaken.
[G2 Android Development] RenderBroken:
What Rom you using? Can you create a backup and flash an older version of the rom +R24? OR even just try to flash R24 twice. I don't know at this point

I am still pretty certain that the issue is not my kernel. If so everyone would be having the same problems. We all use the same source and ramdisk except for very few carrier specific additions or changes. But those are very minor. Still I don't mind debugging the problem. We can even work on it in this thread. I don't mind. I just want to point this out though. Thanks!
[G2 Android Development] :
Yeah. I could try mixing and matching a bit. But Netflix/sensors work with the kernel that came with the rom. The Proximity sensor worked in R23 but not R24. They're just oddities. I only hopped in on the issue since I had seen some back and forth from people posting about the issues.

It's hard to debug some of these issues with all the kernel/rom combos. I don't think it's necessarily anything wrong with your kernel. I imagine it's just something a bit off between how you're handling some things vs how the rom is expecting them to be handled.

Do you remember what kernel version you released around 20Sept? I'd like to try that one on it just to see if it works right. If so, that might help narrow down what's changed.
[G2 Android Development] Formhault:
I didn't modify anything in Synapse. :p
[G2 Android Development] RenderBroken:
I know its a pain. . . lol but that's just part of the fun and learning! Also in my line of work there are things that cannot be easily explained. For example One of our clients had a few servers. Each ran close to the same apps and such and one was a fail-over. One that ran a certain App, the App would close and error upon opening. I probably re-installed it 10 times and ran checkdisk, and sfc /scannow and many many more troubleshooting steps. The eventual fix was a new motherboard. Now in all my years I have never seen a MoBo issue cause ONLY a single program to not work. You would think there would be other issues but there weren't. This may very well be one of those times. Even weirder right now is some who complained of the same issue either re-flashed and it was fixed. idk lol And there are others of the same model with NO problem. So if it was the kernel alone It would happen to all. I thin its the kernel +rom combo. I may have to dig through their stock ramdisk to see if something is being left out of what. Thanks for your help!

Thanks bro for clarifying. I think I know the cause and its rare. Since I had added the extra steps for the GPU, I needed to adjust in other places for it. The problem was the 27MHz is not really a freq the GPU should be TRYING to use. It is the freq for sleep. The only Freq that should be used are 100MHz- 650MHz. The problem was the GPU would stall and error out. Thanks for your report!
[G2 Android Development] Matze060906:
Got my phone back from repair service... [emoji4]

Just flashed r24. I'll report back tomorrow how it runs...
[G2 Android Development] RenderBroken:
Glad to hear! Let me know how it goes. You have the VS980? How are the sensors working for you? I have had a few users complain they don't work and 2 of them got them working again. D802's and VS980's seem effected but I dont see how. Any info you can provide would be appreciated. You always have given concise information.
[G2 Android Development] Matze060906:
No, I have d802. No problems with sensors. Running stock kernel settings and ls 10/10 build...
[G2 Android Development] Formhault:
Well, it is 100-450. :eek:
[G2 Android Development] Formhault:
Oh and... No bin info? :(
[G2 Android Development] :
Looks like it's something in the /data when dirty flashing. Netflix worked fine on a clean install then broke again when I restored my data.

Oh well, looks like it's time to just do a clean install and restore each app by itself.

Thanks for the help!
[G2 Android Development] RenderBroken:
Thats not quite what I meant. There are others parts for the GPU. The one that needed to be adjusted was in power control. There is an Idle state and a Slumber State. One needs to be set to 27MHz and the other to 100MHz. The problem was both were essentially set to 27MHz. It has been fixed already.

Thanks but this has been very low on my todo list. Thanks for letting me know though! Always good to have a second pair of eyes.

Thanks for sharing. This info may be just the thing to look into, see if I can find anything. I appreciate you reporting back! What about the proximity sensor?
[G2 Android Development] :
Enh... It's *working* but its really hit and miss. If I look at it in elixir, it will register a few times, then get stuck in 'near' and never switch back.

I can grab a logcat for you. Just havent had a chance yet.
[G2 Android Development] :
Hm, I was on LS 11/1 and R24, and I had a random reboot yesterday (On stock settings with bacon, non-oc build), but my case slipped off the edge of the phone, and I dropped it on a tiled floor screen first, and managed to crack my screen so bad I can't use the touchscreen. Everything else is fine, but I can't unlock my phone since I can't use the touchscreen. I'm completely broke at the moment too, so it'll be a bit before I can get a digitizer+LCD replacement. Is there any way I can still grab a log?
[G2 Android Development] RenderBroken:
Man don't worry about it. I think I already fixed the issue anyways. Can you fix it yourself? Sorry to hear that my friend.
[G2 Android Development] RenderBroken:
Also on the phone dropping note.

I drop my phone constantly. Whether it is on my lap and I get out of my car or it falls off my desk at work. The only reason my phone screen has never broke was because of my Ballistic case. It has saved my SOOOOO much money!

http://www.ebay.com/itm/Verizon-LG-G2-Ballistic-SG-Shell-Gel-Hard-Rugged-Case-Cover-Skin-Black-VS980-/231188301022?pt=US_Cell_Phone_PDA_Cases&hash=item35d3e584de
[G2 Android Development] crazy4tricks:
Just a quick update... using AICP 02/11 build.. with Your kernel.. all works perfect.. all sensors are working.. and great battery life too..

Thanks for putting great efforts for this wonderful kernel
[G2 Android Development] RenderBroken:
Use Syslog and grab a logcat along with kmsg (dmesg) Thanks bro!
[G2 Android Development] RenderBroken:
Thanks bro for chiming in! That's what I am wanting to here! What what your flash process? Just flashed on top of existing build or clean flashed immediately after flashing rom? Thanks for the Report! Also because of this, it makes me doubt the source for the problem.
[G2 Android Development] crazy4tricks:
Previously i was facing the same issues about almost all sensors.. googling for hour help me to solve by flashing modem for KitKat.. all working great now.. if needed ill upload the flashble zip.

Its a clean flash as to check whats wrong i did flash 3 different ROMs and reverted back to stock using twrp.. but in all cases sensors was dead.

Hope this helps :confused:

Edit: if you want me to test with dirty flash and other ROMs let me know. :)
[G2 Android Development] :
Yeah, I had a shock absorbant soft case that did the charm, but it must've slipped up in my pocket. I have the tools needed to do a self-repair, I just don't have the $50 to chuck out for a new digitizer and LCD. Local repair shops want $100+, which is a joke when I can simply get the parts I need for half of that. I'll definitely look into getting a balistic case over a soft gel case so the phone doesn't slip out of the case in my pocket. Thanks for the link though, bookmarked for when I'm able to fix the phone.
[G2 Android Development] RenderBroken:
Had you used R23 before trying R24? Did the problem occur directly after flashing R24? Yea every bit of info helps get us closer to the real issue. Thanks!
[G2 Android Development] Formhault:
Proximity sensor issue just reappeared. Oh and I connected to my home Wi-Fi but..m no Internet access.

Reboot solved both issues. Weird though... especially the Wi-Fi issue, which NEVER happened EVER.
[G2 Android Development] crazy4tricks:
Yes i started using your kernel from R23 and the problem was there. I just not pointed as i have bad habit to cross check before posting. I dont thinks its problem with kernel.. it is something to do with ROM and modem.. as I look in other threads as well the problem with all AOSP ROMs.

Edit: i may be wrong but according to my readings in different forums in last two days. I think and as everyone know CM has broke something while implementing pure kitkat sources. As LG has mixed sensors with baseband it might have created some conflict and we are facing this issue.. also as LG uses different vendor files for different variants it also leads to the conflict with such commits.

Though i have said the above things i am still not 100% sure on it.
[G2 Android Development] Formhault:
Hey [MENTION=5438598]RenderBroken[/MENTION]... I just realised that the rear LED lights up when receiving a phonecall. I am sure it lights up on other occasions, too...

Is there any way to control it? I dunno, maybe via some switches in Synapse? :D :D :D
[G2 Android Development] RenderBroken:
What happened to make it re-appear?

Just to make sure, The problem was also happening with R23 for you are afterwards when flashing R24? Thank man!

I have no idea :confused: Sorry bro. . .
[G2 Android Development] RenderBroken:
On another note, I am going back to interactive for default governor. Just better experience all around. I just hit 38K in Antutu with no OC.
[G2 Android Development] crazy4tricks:
For me its from there since R23.
[G2 Android Development] RenderBroken:
Ok Thanks. Then that just makes more sense that its not a problem from my kernel. Thanks for sharing! Those that are having issues still. Can I get you to restart your phone and provide me some logs? Please help me gather some info so i can pass it along to the proper channels.
[G2 Android Development] Formhault:
I dunno... Taking the phone out of the pocket? I've no idea... Glad rebooting fixed it though.
[G2 Android Development] Formhault:
Has this ever happened to anyone...? :eek:
[G2 Android Development] Ace42:
I have never seen the sdcard service at the top, nor have ever I seen gmail using more power than the screen (I disable auto sync).

Sent From Capsule Corp.
[G2 Android Development] RenderBroken:
Apparently almost all of our AOSP roms have pulled in the same upstream changes regarding the sensors issue. AICP had reverted the change so that's why AICP working fine for everyone. Just thought i would share the info given to me.

Also now that I am pretty confident about the source of this problem I feel I can move on from it, I will be building a test F2FS build and sharing with a couple testers. I already have testers arranged so please do not bombard me with requests. But if all test fine then From this point on ALL builds with have F2FS. I am also working on a way so that my kernel will automatically recognize whether or not you have already formatted your partitions to F2FS or not and mount the correct partition. This way I do not have to keep building more zips for each release.
[G2 Android Development] :
Which version though?

I'm on the 26 baseband.
[G2 Android Development] Ace42:
Will it be possible for F2FS to only be used on /system /cache /data, without affecting user data on the internal storage?

Sent From Capsule Corp.
[G2 Android Development] RenderBroken:
No, that would have to be formatted and partitioned to work with F2FS. If I remember correctly.
[G2 Android Development] TDSJR:
Hey [MENTION=5438598]RenderBroken[/MENTION]

Sorry for the OT, did you ever get a chance to check out that PA sound incompatibility? Just curious.

Thanks man, using R24 w/ no issues. Good stuff.

Really glad you stuck with this project.
[G2 Android Development] RenderBroken:
No I had not since it was a test build. I think after R25 and F2FS, I will take a stab. Also I am pretty Lax on OT. Keeps things moving forward as far as community is involved during the downtime. I have already started on R25. If I have a direction to go, I like to start on it. Just some new things to note:

CPU-Boost: You can now set the boost freq PER core. So this also means you can set it so ONLY Core0 boosts while the others do not. Just an example

Bacon Gov: Added max_freq_hysteresis. essentially makes it so during heavy load, and there is a small lull, the freq is not immediately dropped then brought back up. IE makes it stick to higher freq a bit longer.

GPU: Fixed a possible SoD where the GPU would stall out since adding the new available freqs and you can now actually use 650MHz. In R24 I couldn't get it to no matter what I did. Also now properly uses 27MHz ONLY for Slumber/sleep and not IDLE. The SoD would occur when turning phone on, the GPU would stall out stuck on 27MHz instead of Rampu up from 100MHz.
[G2 Android Development] dorimanx:
Well done DEV :)

you are on a good path to greatness.

Feel free to use any code updates from my source. :)

Android is FREE and that is the main RULE.

who want to have all to him self, should never give it to public.

I will check your

https://github.com/RenderBroken/msm8974_G2_render_kernel/blob/master/kernel/power/quickwakeup.c

seems interesting :)
[G2 Android Development] midan:
[MENTION=2376110]dorimanx[/MENTION] and [MENTION=5438598]RenderBroken[/MENTION] :It's nice to see two dev like you who appreciate each other when a normal let's say you are jealous of others in this field
[G2 Android Development] RenderBroken:
Thanks! :) I have been a fan of yours since my old i777(ATT S2) days! I appreciate what both you and [MENTION=3795148]neobuddy89[/MENTION] do and both your willingness to help others BUT not spoon feed them. I work to do the same with my development. Not only does it make it more interesting for me but others learn better this way and some even start their own projects. So instead of being a noob their whole XDA career, they start to learn and some even contribute! You had helped me get started a very long time ago when I was starting out building the only CM11 for the i777. Thanks!

Also for Quick Wakeup you will need:

https://github.com/RenderBroken/msm8974_G2_render_kernel/commit/c0b12c59a8c19e6317dbbe0865a4fd5b08b605ee

Kind Regards,

Zachariah
[G2 Android Development] RenderBroken:
You are soo true. I think the biggest problem with Dev's is that when we work, its mostly for free. There are some cool people out there that donate but compared to the number of hours that go into it it might as well as be free. BUT we mostly do this for 2 things. 1 Its fun and interesting to us. We know that we like certain features so why not do it ourselves if no one else is filling that gap. 2. A modicum of notoriety. We don't expect to get paid but we do want some recognition of our work. The biggest issue arises when others use your work and strip your authorship from the module and most times off of the commit itself. You can tell when someone does it on accident and when they habitually do it. An example is when everything in their github shows to be authored only by them. There are few people out there THAT good. There are others causes of strife but that's the big one. Dorimanx has always been helpful and I have learned alot about how LG's source works for the G2 by searching through his github.
[G2 Android Development] TDSJR:
Is it normal for "Current CPU Governor" to say CPU0 Gov in Synapse?
[G2 Android Development] RenderBroken:
As I had said earlier in the thread, I have had to manually code and rework bits of code to produce what you see in Synapse. I am still working on a few places. That just happens to be one of them. But thanks for reporting! I may not have known.
[G2 Android Development] thackoon:
Just installed R24 on VS980 with latest Mahdi ROM. Already loving the performance. As a new user, do people suggest messing with the kernel settings in Synapse, or are the default settings already optimized for most people? Thanks!
[G2 Android Development] 1ceb0x:
Synapse does not show that the phone goes into deep sleep but BBS does:

Also, the uptime in Synapse is wrong - 5 hours compared with the uptime from About phone: 21 hours.

Just some cosmetic stuff :).
[G2 Android Development] RenderBroken:
Yea I would say so. The default settings should give you better performance than stock kernels and battery battery life to boot!

Thanks for pointing it out. I will add it to the list of UI changes to be made. If you find more just let me know! Also I appreciate your help to the community. You help out far and above whats expected of you and REV3N and I both appreciate it.
[G2 Android Development] 1ceb0x:
My pleasure mate! R24 running like a champ here ;)
[G2 Android Development] thackoon:
Thanks Render. Can't tell you how much I appreciate all the time you put into this. I've been following this thread for a while and finally got around to clean flashing the latest Mahdi and R24. Smoothest my phone has ever run. No audio glitches, and wireless charging works!
[G2 Android Development] RenderBroken:
Glad to hear! I do agree that it has just grown better exponentially. Thanks for the kind words!
[G2 Android Development] rmsinaga:
Is it possible that max CPU freq changed by itself? I've installed R24 on my D802 Mahdi 10/27. I changed the governor to Conservative, max CPU 2265MHz & min of CPU 249MHz. There were a few times it changed to max 1497MHz by itself. When I checked in Synapse, it's changed but the default value is still stated D:2265. It's just my observation.

Thanks a lot for your work. Appreciate it a lot :thumbup:
[G2 Android Development] hailang215:
very good kernel!I hope it would quick drian my batteries out
[G2 Android Development] RenderBroken:
Yes, that is the Thermal driver overriding the Max freq. Thanks! Glad to have you.
[G2 Android Development] 1ceb0x:
It happens here as well but it is merely a cosmetic bug (the slider thinks your max is 1.4). This happens due to the thermal throttling. 1.4 is a step in throttling and when it does, Synapse thinks your max is 1.4 as well, instead of 2.3. But in reality, your max preffered is still 2.3, but until the phone does not cool down, it will show that step.

Happens in Synapse and Trickster and also happens in Blackbird kernel.