yashsingh1/xdaforums huggingface dataset:
[G2 Android Development] RenderBroken:
It looks to be ended but something with your phone does not like the newest kernel. ITs a D802 right? I have not had alot of complaints from users of that phone so I am not sure why you are having such a problem. I will build tonight with Falcon Hotplug and we can see if that is more stable. But I really want to keep msm_hotplug though. . .Still I will make the best decision for all. I hate that all our phones are so different.
[G2 Android Development] Matze060906:
D802, you can't buy another device in Germany. Some other users here with d802 have the reboots too. If the newer build won't work without reboots, I'll use R4, but I think you will fix the reboots so all d802 users can run your newer builds. Thanks for your violent effort... [emoji106]
[G2 Android Development] kewkie:
Com.android.phone force close with R12..,well my own bad tried on alegen ROM which is based on CM
[G2 Android Development] Raagh:
Alegen works perfect with render, its based on cm but it uses dr87 sources(it even comes with simplekernel)
[G2 Android Development] Matze060906:
Someone had the same problem in the Mahdi thread. I'm not sure, but I think clear data and cache from the app solves the problem. This is not kernel based.
[G2 Android Development] stewyfallingup:
I'm on Alegen v7 and I flashed render 12 and it kept flashing this error. Luckily could get back into recovery and flash the patch again.

Well it didn't even save the screen shot.

It was Android.gms. Phone or something. Kept force closing right on boot up.
[G2 Android Development] Raagh:
Yeah just saying it has nothing to do that its cm based.
[G2 Android Development] zootzoot:
I had this error on r12 . I have a d802 running Alegen v7 ROM.
[G2 Android Development] midan:
when this happens to you after you tap a notification?
[G2 Android Development] zootzoot:
It happened at first boot, I had to revert back to Alegen kernal from backup.
[G2 Android Development] abby_nitewolf:
Hello there,

Well i flashed r12 about 4 hours and it was running smooth. But.... My phone just rebooted randomly and here are some logs. Right now it's running smooth once again.

VS980 MAHDI 8/17, stock kernel settings, read ahead 1024 noop.

https://www.dropbox.com/s/eokh04e8pdihclx/2014-08-19_16.37.zip
[G2 Android Development] MaluNoPeleke:
Here is another reboot log file, hopefully it is more helpful...
[G2 Android Development] ThatKidDrew:
Hey render I've been using R12 for over nine hours with NO REBOOTS OR SODS. Haven't tried R13 but I will tomorrow, thanks for all your work. Hopefully my experience without a reboot is a good sign and a help for your development

VS980 running AICP 4.4.4
[G2 Android Development] Lawlrus:
I don't even see any R13's but I agree that R12 is running very well for me as well, no issues at all.

Also on Aicp

Sent from my Vs980
[G2 Android Development] simpsonr:
Just tried this kernel on a 8/18 build of Carbon ROM... no workie. :(

Upon bootup, I get a constant phone fc alert which never goes away.
[G2 Android Development] Lawlrus:
Carbon is based on jackpotclavins source, not dr87's

Sent from my Vs980
[G2 Android Development] phoenix_rizzen:
So, then not stock. :) Lol. Stock CPU governor is interactive, not intelliactive.

Several people have confirmed reboots with intelliactive. And Render mentioned at least once that he's considering removing that governor completely in a future build.

How's the stability on your phone when using the stock CPU governor, interactive?

Typos courtesy of my LG G2 (D803) running Mahdi-ROM.
[G2 Android Development] ThatKidDrew:
Read on page 30, Renders last comment

VS980 running AICP 4.4.4
[G2 Android Development] phoenix_rizzen:
Page numbers are useless, as everyone can set how many posts appear on a page. For example, I only see 28 pages in my view (50 posts per page).

Typos courtesy of my LG G2 (D803) running Mahdi-ROM.
[G2 Android Development] RenderBroken:
I am going to build r13 shortly. It will have a modified msm_hotplug. I am going to open wide the max_suspend_cpus from 1 to 4. I think this is the cause for some of the reboots. I will take a quick look at intelliplug to see if there are some settings I can change or not. If not I am dropping it. Its the same as interactive except way more aggressive. Just a waste of space at this point. If I were to use intelliplug then there are special functions that intelliactive uses to work with it but I don't so the benefit is lost and because I use a different hotplug it may be hurting more than helping. If reboots continue for some I will release a build using Falcon. I really do see the future of this kernel using msm_hotpluug so if i can help i I will try to use it. If problems persist then i will have to bench it for now.
[G2 Android Development] ThatKidDrew:
I did not know this, thanks

VS980 running AICP 4.4.4

---------- Post added at 06:04 PM ---------- Previous post was at 06:02 PM ----------

I'm sad to say I had my first reboot :/ phone was locked and I went to unlock it and nothing happened til it rebooted.

-Recent AICP nightly on R12

-CPU min 300 max 1.7, interactive

-Log: https://docs.google.com/file/d/0B3rK_px6FpxWUVZxREZoRHFiWGM/edit?usp=docslist_api

VS980 running AICP 4.4.4
[G2 Android Development] RenderBroken:
Still think it has to do with the hotplug forcing the cores down to 1 when screen is off and it suspends. The new build will be adjusted and we should see a better result. Thanks!
[G2 Android Development] 1ceb0x:
some stats on aicp and r12 - no reboots encountered from the installation until now. stock settings.

i musy say this is the smoothest experience ever encountered on aosp for me on this particular phone. Great job Render!
[G2 Android Development] SeVIIn:
On the latest Mahdi (D801) and haven't experienced a single reboot since flashing R12, everything is smooth as silk for the past day.
[G2 Android Development] willi_3609:
On latest mahdi. Fauxsound settings don't stick at all. Set speaker to 8 and it goes back to 4 for some reason.
[G2 Android Development] abby_nitewolf:
Here is another log. Just happened 5 minutes ago while watching a video. Mahdi 8-17 stock settings. R12

https://www.dropbox.com/s/8i2ia46fflg4i6l/2014-08-19_21.22.zip
[G2 Android Development] ThatKidDrew:
Second reboot on 11th hour of use, everything from previous comment is the same. Here's the log

https://docs.google.com/file/d/0B3rK_px6FpxWNm1nMXZUTkh2UVk/edit?usp=docslist_api

VS980 running AICP 4.4.4
[G2 Android Development] RenderBroken:
Can y'all provide all logs when you are getting this error. I don't know if its possible but I would really love a logcat. Thanks! I checked my Ramdisk and it has the proper value that I thought may be the problem so I don't know at this point.
[G2 Android Development] RenderBroken:
I think someone else was saying something about this. When I do the Sound overhaul, I will look into this issue in depth. I just don't use this so its not high on my to do list. Thanks!

I dont remember if you have said a model before, can you let me know? Thanks for the log!
[G2 Android Development] abby_nitewolf:
VS980 Mahdi 8-17, R12 Stock settings, 1024 Read Ahead Noop.
[G2 Android Development] RenderBroken:
Thanks bud, I am build for all now. I actually opted for a modified version of msm_hotplug by neobuddy89. Another Great Dev who really tries to help others too. His version is VERY close to that of myfluxi's with some notable differences. Main thing is how it handles suspend is different. Instead of using lcd notify by default it will use whatever you set it to so I set it to use Powersuspend. This way it is inline with the other suspended subsystems in my kernel. Also if you turn your screen off there is a timer before it sets the max number of suspended cores allowable. Also if You have a workload across 3 cores and you turn your screen off, it doesn't butcher the 3rd core to force it offline to meet quota. There are a number of other fail-safes added in.

I also modified Powersuspend with the help from Dorimanx so that it no longer uses Hybrid mode (Panel and autosleep) since there are some users out there that have their panel stuck in Blank. Really it is not needed anyways. Also added a sysfs for Debug mode for powersuspend so you can see whats really going on. Since I had already removed a metric F ton of logging I though it would not hurt to see what the suspend process is doing.
[G2 Android Development] RenderBroken:
R13 is easily the fastest build so far. . .
[G2 Android Development] 1ceb0x:
downloading and will report later. thank you for your hard work Zach!
[G2 Android Development] Matze060906:
You understand it wrong. I had tried to set the governer to intelliactive and got instantly a reboot. After reboot I had stock settings (interactive) and run on it. After a few hours I got another reboot.
[G2 Android Development] ThatKidDrew:
Flashed R13 successfully and now I'm going to sleep, will test and compare throughout the day tomorrow. Thanks again for all your work ?

VS980 running AICP 4.4.4
[G2 Android Development] Boot_Derran:
Delete
[G2 Android Development] Matze060906:
Just flashed R13. I'll report back in a few hours...
[G2 Android Development] RenderBroken:
Let me know if you guys have any issues with newest build. I don't know if I am having a SoD issue or not. Just a heads up.
[G2 Android Development] 1ceb0x:
had a reboot on R13 when i connected my phone to my PC. i had like 12% or 10% battery left. here are the logs, Render!

d802 running AICP.
[G2 Android Development] Boot_Derran:
https://docs.google.com/viewer?a=v&pid=explorer&srcid=0BxJqm36wo3AyUlB3ajNubTVYVG8
[G2 Android Development] murdoch1:
R13

Reboot after screen off running on D802 with stock settings mahdi 17/8.
[G2 Android Development] 1ceb0x:
had a sod during deep sleep. going back to r12 for now.
[G2 Android Development] hamisgood:
[MENTION=5438598]RenderBroken[/MENTION], I'm still getting the Android.phone has stopped error on my F320S on TeamEOS when flashing R13. This issue only started from R12.

Edit: I can't get a logcat as the process error keeps popping up and interrupting any actions. Mobile data doesn't connect during this period as well.
[G2 Android Development] SeVIIn:
Again, everything is running great on the latest Mahdi with R13, completely free of reboots and SODs thus far.
[G2 Android Development] 1ceb0x:
Can you state your settings?

I noticed i had deadline as scheduler and changed to row - so far so good.
[G2 Android Development] SeVIIn:
I've taken a unique approach to make sure I have a clean test each time. First I flash the kernel in recovery and boot up then uninstall tricker or any kernel tweaking utilities, after that I reboot back into recovery wipe dalvik and cache and boot back up again. Lastly I reinstall trickster and make sure every setting is at the default. So, right now I am running with deadline.
[G2 Android Development] Raagh:
What are exactly modem resets? Sorry can not help you :(, maybe [MENTION=5232783]dr87[/MENTION] or [MENTION=4316709]savoca[/MENTION] can .

Sent from my D806
[G2 Android Development] 1ceb0x:
No one posted battery screenshots so far so i was thinking i should break the ice.

mahdi 28/06 + R1 of this kernel, Dalvik and stock settings :).

Thank you Render!
[G2 Android Development] reas0n:
I can confirm the kernel works on fabioio's CM :) But it seems like it's faster on Mahdi, i think it's the main ROM which the kernel has to be the most compatible, right, [MENTION=5438598]RenderBroken[/MENTION]?
[G2 Android Development] chrisexv6:
Does this kernel use any changes that might cause the dreaded black lines on the display?
[G2 Android Development] RenderBroken:
NICE!

Yes and No.The kernel should work on any compatible rom the same. The differences come when the Rom has different Ramdisk needs and errors occur. If you can upload the boot.img I can take a look at its ramdisk.
[G2 Android Development] Raagh:
Black lines are caused most likely by heat, not kernel changes

Sent from my D806
[G2 Android Development] Lawlrus:
Black lines have nothing to do with ROM or kernel. Its a mfg defect.

Sent from my Vs980 running crDroid 4.4.4
[G2 Android Development] themikeyan:
had a random reboot overnight, here's the last_ksmsg. Let me know if you need anything else. Thanks a bunch, kernel runs amazingly smooth!
[G2 Android Development] RenderBroken:
Man I looked it over and it was not helpful. I had seen others along with 1 of my own and they are the same. Usually with the kernel failing it should at least produce an error message at the end. Not all the time though so it's not something I am ruling out. With the modem resets I have seen bother error messages and not error messages. This has happened to me a couple times since I got this phone. I also don't know if my phone just trips easier or if it's a real issue. I haven't seen a whole lot of people report reboots compared to the number of actual downloads. Thanks for submitting a log. Any helps provided is appreciated. I am testing some newer changes I have made that should theoretically help with this issue but don't know for absolute certain. There are still many things I have yet to learn about kernel development but hope to learn and share with the community.
[G2 Android Development] Raagh:
Dont worry with time,help and maybe some luck you ll solve this. Still using your kernel allthough a reboot from time to time, still amazing.

Sent from my D806
[G2 Android Development] Lawlrus:
[MENTION=5438598]RenderBroken[/MENTION]

If you want someone to take a look at it, send a pm to dr87 w/ the boot image and see if he can take a look at it when he gets some free time.

He's always willing to help, and I don't think I've had a single reboot since he started building with 4.4 kernel source.

He might be able to pinpoint the issue very quickly since he's much more familiar with development on this device then you are.

As opposed to you wracking your brain over it.

With all respect to your work so far though. Its pretty damn amazing since you are "fairly new to the development scene" ridiculous how well it runs for your early attempts.

Sent from my LG-VS980
[G2 Android Development] Raagh:
+1
[G2 Android Development] simon_lefisch:
Has anyone experienced any random app crashes/FC's? I had it happen on my messaging app (8sms. Once yesterday and once today) and root explorer (once today). I've been running the 6/28 build of Mahdi (clean flash) since it was released and never had anything happen like that before while on the stock kernel. I know this kernel is still in its infancy, just curious if its only me.
[G2 Android Development] Raagh:
Sorry nothing. But im using stock message app and es explorer

Sent from my D806
[G2 Android Development] BlakeSm:
[MENTION=5438598]RenderBroken[/MENTION] Two reboots, here's the logs.
[G2 Android Development] Quiox:
This is awesome! I left everything stock when I flashed the R1 last night. I'm on Mahdi 6/28.
[G2 Android Development] RenderBroken:
That's great! Thanks for sharing! That is crazy screen on time. And you had battery Saver Mode disabled.
[G2 Android Development] Quiox:
Yeah I don't normally turn it on cause I have heard that it causes some issues.
[G2 Android Development] jcmaddox1:
I decided to try it for the luls after backing up Houston's kernel... And uhm...

---------- Post added at 06:15 PM ---------- Previous post was at 06:14 PM ----------

EDIT: one issue is that I lose sound on everything but notifications. Other than that nothing is bad at all.
[G2 Android Development] reas0n:
[MENTION=4228612]jcmaddox1[/MENTION] wut? :confused: How it even works haha, PA has different commits.

Btw, using this kernel on latest Mahdi for few days, no reboots or other issues, waiting for new features.
[G2 Android Development] 1ceb0x:
quite extreme approaches you have there... anyway, deadline seems to be the stock one. thank you!
[G2 Android Development] RenderBroken:
I will be rebuilding today with Falcon Hotplug. Cant wait to see the difference. It seems to play niver with others anyways so lets give it a shot and compare! Also I will start dignifying what should be a stable build and what may be a test build. Not sure the best way since I cant test every phone so what is stable like a rock for me may not be for others. So I may just say last known stable as signified by the community. I dont know, Anyone have some ideas? I want to make it easier to get the right inf and the right build. I like to build alot and use my own build so I like to experiment and such.
[G2 Android Development] Matze060906:
I'm running R13 since 9 hours. No freezes or reboots till now...
[G2 Android Development] RenderBroken:
LOL now your stable.
[G2 Android Development] Matze060906:
Hope that. The last times I posted "no problems": 5 minutes later - reboot...
[G2 Android Development] quang61:
[emoji3] [emoji3] [emoji3]

from F320L

---------- Post added at 09:43 PM ---------- Previous post was at 09:38 PM ----------

Nice Render.. Maybe you can have a look into Vectus rom and support the poor F320 peoples some advice or a patch to run it... We will be very very appreciated about it

from F320L
[G2 Android Development] Matze060906:
And here is the reboot... [emoji35]

https://docs.google.com/file/d/0BwVur07uzqm6dE8wQjNNdWh2LTA/edit?usp=docslist_api

And the next one...

https://docs.google.com/file/d/0BwVur07uzqm6SVZJMnJIQnFVdHc/edit?usp=docslist_api
[G2 Android Development] blacklight1025:
Yea, R13 is stable for me. Been playing ffiv for 2 hours and listening to music with no problems whatsoever. Thanks again for all the effort you put into this!
[G2 Android Development] 1ceb0x:
hahahaa. next time you should not post dude!!! :d
[G2 Android Development] ThatKidDrew:
Reboot and SOD, only been on for a couple hours. R12 seemed to be more stable but we'll see how things go throughout the rest of the day. Here's the log

https://docs.google.com/file/d/0B3rK_px6FpxWV1lKXzR0c1RHSFk/edit?usp=docslist_api

VS980 running AICP 4.4.4

---------- Post added at 09:06 AM ---------- Previous post was at 09:03 AM ----------

On R12 and R13 I mostly seem to have problems when bringing the phone out of deep sleep it seems

VS980 running AICP 4.4.4
[G2 Android Development] BlakeSm:
D800, Mahdi clean 8/17, SOD and Reboot, R13
[G2 Android Development] phoenix_rizzen:
So, to clarify, R14 will have Falcon hotplug, and R13 still has msm_hotplug?

Typos courtesy of my LG G2 (D803) running Mahdi-ROM.
[G2 Android Development] Matze060906:
Yes...
[G2 Android Development] abby_nitewolf:
Just flashed r13, and 15 minutes later i got a reboot while using the system clear option on Android Assistant. Not sure if the app caused it or kernel issue. MAHDI 8-17, VS980, Stock settings.

https://www.dropbox.com/s/64z3v7i9vhi3f7e/2014-08-20_15.16.zip
[G2 Android Development] midan:
What are the best settings for this kernel,I had only one reboot the newly installed due to g +.
[G2 Android Development] bgx:
Runs R13 here over 20h without reboot on D802 with last mahdi
[G2 Android Development] SeVIIn:
Same here only on the D801 :good:
[G2 Android Development] RenderBroken:
Yes, Sir!

Just shows that no matter what EVERY phone is different, even if they are the same model. Its hard to find a balance so its nice to have a great group of followers who understand this. Thanks Ladies and Gents!
[G2 Android Development] fix-this!:
Reboots on both 12 & 13 for me. Im sure render gets frustrated. Hope we can get these resolved.
[G2 Android Development] mgear356:
Had a sod on my 15hr.. This happened after like 6hrs + of deep sleep ... There was no reboot before that

D802 here with r13 madhi
[G2 Android Development] RenderBroken:
I little, then I remind myself that I enjoy this and its all good. As long as everyone else aint complaining I am great! Right now since its the start of school and I am Tech Admin over four Elementary schools, it had been crazy getting ready. One school is being remodeled and is not even done yet and school starts Monday! Still have tons of tech work needed to be done and my tickets are up from 15 to 150 in one week. I received and email this morning about a teacher being upset about a very minor issue and it drove me nuts lol. This community had been nothing but fantastic which is probably why I have been neglecting my Moto G kernel. . . lol that and there is not enough time right now.
[G2 Android Development] 1ceb0x:
well we are all seeking a great aosp experience on this beast of device and you are probably one of our last hopes around (i like to run custom kernels on my phones - not fan of the stock kernel). keep up the good work and even though we have this problems now, i am sure they will end soon enough! good luck with your work!
[G2 Android Development] hovanhuang:
What's causing the dt2w delay? Sometimes take 10 seconds to wake up. Sometimes can't even wake up and have to use power button.

I'm on the mahdi 8/19 built. Is that a rom problem? Tried vanir and r4 r12. Same issue.
[G2 Android Development] RenderBroken:
Ah whatever! We all want to jack with our phones and make it run like a beast while having infinite batterylife! lol I love what I am doing and I know what its like checking the thread to see if there are updates.

So an update here:

Building now. Falcon hotplug incoming. For those interested in staying with msm_hotplug see below. I would like some of you with constant reboots to try below before going to Falcon hotplug if possible :)

In the mean time, those of you with reboots, Please set your max suspended cpus to 4. So in R12 and in R13 its a different sysfs to do this.

R12:

/sys/module/msm_hotplug/max_suspend_cpus (Change from 1 to 4)

R13:

/sys/module/msm_hotplug/max_cpus_online_susp (Change from 2 to 4)

I use ES Explorer with Root explorer enabled.

Please try it out and let me know if that helps your reboots! Thanks!
[G2 Android Development] RenderBroken:
Not sure but what I do know if my DT2W code hasn't been touched at all for the longest time. So I don't thing its the kernel but its possible. This is not the highest on my list but it is up there. Once stable will look into it. I do have numerous leads to look into that may shed light and help out.
[G2 Android Development] 1ceb0x:
going to reflash r13 to test it out!
[G2 Android Development] phoenix_rizzen:
That'll be me next week. Secondary school staff are in this week, and call volume on the Helpdesk is just barely manageable right now. Elementary school staff arrive next week, expecting phone to ring off the hook. Well, except for the teacher strike starting up again next week. Lol. Might be quiet after all. Not like the todo list won't continue to get longer.

Fiddling with the phone is one of the few fun things to do after dealing with teachers all day. :)

Typos courtesy of my LG G2 (D803) running Mahdi-ROM.
[G2 Android Development] willi_3609:
I see r14 on the media fire mirror. But I don't see ls or vs980.

That's just because its uploading right? Thanks render for trying to work all the bugs out in your kernel.
[G2 Android Development] 1ceb0x:
well idk if i should wait any longer than this but i flashed r13 and did what you said - put the cpus back to 4 for suspend and it seems it is holding on... also the d2tw is more responsive now than before...

i will run it more and see if i will encounter something.

before, r13 for me was unusable.
[G2 Android Development] murdoch1:
R14 + D802

I'm on latest mahdi and installed R14 early this am.

Gotta say awesome work... Not a single reboot and the phone feels so responsive. Phone goes to deep sleep and wakes up feeling refreshed and alive.. Lol.

Excellent work yet again.
[G2 Android Development] Boot_Derran:
Just ran into a reboot while I was playing KRITIKA: CHAOS UNLEASHED. I'm on AICP 8/19 for D801, R13, stock settings except read ahead 1024. I did what u said and changed the hotplug settings for max_suspend. Here's the log http://goo.gl/I1nwtS
[G2 Android Development] Matze060906:
Changed. Will this reset to default after reboot?
[G2 Android Development] 1ceb0x:
yes!
[G2 Android Development] Matze060906:
I see. Phone rebooted... [emoji35]

https://docs.google.com/file/d/0BwVur07uzqm6SVUxLVl3ZlBUU0k/edit?usp=docslist_api

I'll install R14...