yashsingh1/xdaforums huggingface dataset:
[G2 Android Development] RenderBroken:
Thanks! Its good to get a few from the same user, it helps isolate an issue better. So thanks for posting them!

Yea, I should havea named them with "BR" or something else . . . lol BUT . . . .

I am going to release again. I am going to look at the latest logs and decided how to proceed. There are a number of commits I have right now that are groundwork fora MASSIVE Scheduler bring-up but if they are part of the problem then it throws the whole thing off sadly. But I don't think this will be the case. The plan is to get back to stable and FAST. I am tired of reboots so for now I will be reverting my work tree back to when I released R4 and then add in my major bug fixes and msm_hotplug. So this means that we can get back to stable and have a completely solid kernel.

Bug fixes are:

p ering

Radio/Mobile Data bug when coupled with Mahdi directly

SD Card mounting properly

If we are in agreement that the new hotplug is the way to go after the next release we can keep it and I will build on it. If not then I will go back to falcon_hotplug. The main reasons I like the new hotplug is:

max_screen_cpus

cpus_boosted

Fast_lane_load - Load that makes the hotplug online ALL 4 cores

min_cpus_online

io_is_busy

etc . . .

Way more control than falcon_hotplug but falcon_hotplug is simple and works freaking great! So we will see. .

Just wanted to give an update!

Regards,

Zachariah
[G2 Android Development] Matze060906:
No problem. If this will help you to fix the reboots, I'll post logs. Today dr87 will release a new build of Mahdi. I will flash it and then your new build. Hope the lags with double tap to wake and the reboots will be fixed.
[G2 Android Development] Rick O:
Are the changes for Spirit FM going to be in the latest release?
[G2 Android Development] chillstep1998:
Freeze + Reboot while editing a Textfile.

AICP, R10, Dalvik

Logs --> https://www.dropbox.com/s/fhl9721ccyqr36p/2014-08-17_19.07.zip
[G2 Android Development] TDSJR:
It would be beneficial to ALL user's and potential user's, if in addition to logs, those reporting reboots and FC's would include device, ROM info., version and any other pertinent info (I.E. clean/ART, etc). As a community, we all MAY be able to give Zach a hand fixing this issue. Flame away. ?
[G2 Android Development] RenderBroken:
I am glad you reminded me, They will be now. Thanks!

True dat! Anything you think would help go ahead and make note. Apparently there are other kernels that are having reboots so I am not sure if its also Rom related so I will do everything I can to make sure the kernel is running great. I will be releasing another build today, Hopefully we can get past this crapola lol.
[G2 Android Development] RenderBroken:
Started to upload new builds. As always report back and let me know!
[G2 Android Development] Matze060906:
Installed! Hope I'll report that it runs great... [emoji6]
[G2 Android Development] murdoch1:
mahdi 09/8 + R11

Hi. Just installed r11 haven't changed settings. Left phone on standby however went to look at phone after about ten minutes and screen was blank. Power button would not turn screen on had to do a full power on. Logs attached. I'm running on a D802
[G2 Android Development] RenderBroken:
Thanks! Nothing really to note in the logs though.

Can anyone else report?
[G2 Android Development] Matze060906:
Since flashing it runs great on d802...
[G2 Android Development] murdoch1:
Yes.... Since my last restart it's been fine and not crashed again at all. Maybe it was just a coincidence.I know mahdi will be providing an updated ROM imminently. I will leave the kernel on and install on the fresh ROM... Thanks very much for your continued hard work and support.
[G2 Android Development] simon_lefisch:
[MENTION=5438598]RenderBroken[/MENTION], had just installed R11 and had 2 reboots in a row. Didn't do anything but turn the screen off. Reboots happened about a minute or 2 after install. After first reboot, phone rebooted again a minute or 2 later. Reverted back to R4. Logs below.

First reboot: http://goo.gl/gfwQpI

Second reboot: http://goo.gl/XnLFXs

Setup:

VS980

Mahdi 8/9 build dirty flashed from 7/29

Stock kernel settings

Will flash R11 once new Mahdi build is released (which should be today according to the dr). Will clean flash new build then R11 and see if it happens again.
[G2 Android Development] Matze060906:
[MENTION=5438598]RenderBroken[/MENTION]; do we have to start newest Mahdi after flashing and then install you kernel or can we install all in one process? I know you answered this question in this thread, but I can't find it. There was an issue with the signal. You know what I mean?
[G2 Android Development] SeVIIn:
I cant run R11 at all getting constant reboots about every 20 seconds on my D801, here are the logs https://drive.google.com/file/d/0ByQU4ANsxaildDNQN2sySWpRU0U/edit?usp=sharing

https://drive.google.com/file/d/0ByQU4ANsxailUW5Rdk5zUnc1Rkk/edit?usp=sharing
[G2 Android Development] Lawlrus:
Can flash at the same time.

Sent from my Vs980 running Jackpotclavin's cm11
[G2 Android Development] simon_lefisch:
hey guys, just flashed mahdi+patch+gapps+supersu+render and had no baseband. reflashed everything but render and baseband is back. so you must still flash render after letting your phone boot the first time.
[G2 Android Development] RenderBroken:
Really, I have personally tested this and it worked fine. Maybe they freaking updated their Ramdisk AGAIN. I can't find it, what model phone do you use?

So really the only new things in this latest (compared to r4) build were

Msm_hotplug

Ramdisk changes to fix bugs

Smp patches needed for major scheduler bring up that I really, really, really want to do

So I am going to do another build, essentially it will be r4 with swapped out hotplug and new Ramdisk. If reboots are gone then I will move on very effen slowly. If reboots persist then I will go back to Falcon hotplug. If reboots still persist I give up and blame it on the new roms or just build only for my happy d800 lol (last one is not an option ?)
[G2 Android Development] RenderBroken:
Have you also been able to verify this worked? It has for me and I dont want to think I am crazy lol
[G2 Android Development] Lawlrus:
Nope, I normally boot up before I flash a new kernel. I'm going off of what render said. It was either R4 or R5 that made t so you didn't need to anymore.

Sent from my Vs980 running Jackpotclavin's cm11
[G2 Android Development] simon_lefisch:
im using a vs980. yea i thought it wouldve been ok but i checked the baseband and it said unknown. reflashed everything but kernel and baseband showed up.

i was gonna test R11 on this clean flashed mahdi build since i had dirty flashed from 7/29 to 8/9. should i hold off for your next kernel build?
[G2 Android Development] fix-this!:
Same thing happens on my d800 with aicp. Cant flash the kernel until after a full boot.
[G2 Android Development] jeff5347:
I'll flash the new mahdi then r11. Makes me very happy I have a d800 as well !!!!!
[G2 Android Development] TDSJR:
Maybe i'm off base, Has it occurred to anybody else, if you flash V4 over any of the later versions and DON'T lose paid apps, there are remnants left over from the previous build? So, would it not stand to reason that there are other remnants left over? If this is the case, unless users are clean flashing all builds, there is no telling what is left over and subsequently no real idea of whats wrong.
[G2 Android Development] RenderBroken:
Thanks, sorry, I must have not re-commited all of my updated ramdisk commits. Been juggling too many branches lately.

I am going to re-build one more time tonight. Depending on its results I will just go back to when R4 was released and make my few updated commits and then go back to SMP patches at a later date. Just really throws off my long term plan. Thanks Gents for your help.
[G2 Android Development] simon_lefisch:
I've thought that as well. With Mahdi, I usually flash the patch then render and would still get reboots. The only version that has been stable for me is R4. No reboots, no SOD's. Completely stable. I've also dirty flashed from, say, R10 to R4 and don't have probs. Which to me says it doesn't matter about flashing clean or dirty. I could be wrong tho.
[G2 Android Development] RenderBroken:
Its possible. BUT mainly the new kernel will overwrite the old one. Still it would not hurt to do a clean flash
[G2 Android Development] fix-this!:
Im still on r4. Should i wait for the new build then or flash r11?
[G2 Android Development] bleached45:
I was just looking into this. I'd wait for the next build. It will be a little closer to R4 but will help render set up closer to where he wants to be with more stability. Afaik R4 was the last stable (I'm still on it) and I think the next build should be on that level of stability.
[G2 Android Development] RenderBroken:
I had just received a pm from Dori and he had said he had issues with msm_hotplug before. I am about to build using falcon_hotplug to see if the reboots persist. That would suck if that fixes it since it would have been a MAJOR waste of time along with that I wanted to use msm_hotplug. Only one way to tell and that is to build! lol
[G2 Android Development] Lawlrus:
Thanks for your persistence. This phone is much much more finicky then what other devices seem to be.

A pro being a pretty huge learning experience versus some ezmode phone.

Con is the cost of drywall mud to fix the holes you beat in it with your head.

Sent from my Vs980 running Jackpotclavin's cm11
[G2 Android Development] fix-this!:
Deep sleep is great on r4 but the battery drains really quick when the screen is on. Hoping we can get back to r1 or r2 battery life in a future version. Thats my only request.
[G2 Android Development] RenderBroken:
Sorry, I had been multi-tasking too much and I did nor merge in my Ramdisk Update so R11 still has the old Ramdisk so you are right. FML! lol So R12 will have the fixed Ramdisk and you can flash my kernel properly.
[G2 Android Development] BlakeSm:
D800, Mahdi 8/17, r12 flashed. Will report back with logs if there are any issues. :good:

Edit: Getting reboots, can replicate them by turning screen off a couple of seconds after it boots up.

Edit: Log below
[G2 Android Development] BlakeSm:
Heres the log
[G2 Android Development] simon_lefisch:
[MENTION=5438598]RenderBroken[/MENTION] that's what happened to me on R11
[G2 Android Development] RenderBroken:
I had pulled the download.

So I had found either the cause of e reboots or one of them. I do believe it to be the cause though. I ran a build using a modified version of msm_hotplug and that's what was causing it to reboot. As soon as the suspend process started it would reboot. I did the exact same build but swapped out the hotplug with falcon hotplug and no problems at all. So the past few days have been a major waste of time. I can , however, proceed with me intended scheduler bringup like I wanted. So that is some good news. I will try to get new builds out to everyone later today.
[G2 Android Development] 1ceb0x:
Great. I knew this was the best day for me to return to AOSP after fixing my phone :). Good job mate. My AICP G2 waits for your kernel and my setup will be complete.

Cheers!
[G2 Android Development] quang61:
Any opinions running it on F320 please ? So far so good... :)
[G2 Android Development] 1ceb0x:
ehm... which version you talk about?

i see r12 for d800 only.. anyone tried it?
[G2 Android Development] quang61:
Hehe... Funny ! Just try R11 .. ,still no sd card :(
[G2 Android Development] 1ceb0x:
lol... the last official one is R4....
[G2 Android Development] jastonas:
I can't find any information on what ROMs are supported by this kernel. I flashed on CM11 and I got stuck in a bootloop.

Now I use Mahdi, is there anyway it will work?
[G2 Android Development] quang61:
Sorry, i mean r11...
[G2 Android Development] 1ceb0x:
it works on mahdi. on cm11 is a hit or miss. some users discovered it works, some not...
[G2 Android Development] RenderBroken:
R11 was using the old ram disk. I did not update it when I was restacking my commits for that release. Try r10 and SD card will work fine. R12 should be back to stable for all along with the bug fixes. Msm_hotplug was causing the reboots. I don't thing it was just that module but in connection with the rest of the phone it didn't play nice.
[G2 Android Development] 1ceb0x:
i took the plunge to test R11 on a freshly AICP installation. will report back after i fiddle with it :).
[G2 Android Development] quang61:
Happy to know about fixing sdcard already... I can wait till stable one arrive [emoji1]
[G2 Android Development] RenderBroken:
Yea this whole ordeal has been a complete ball drag lol. I will get it sorted out.
[G2 Android Development] crnkoj:
Ah, don't give up :) your one of the friendliest devs on xda ;)
[G2 Android Development] 1ceb0x:
no problems whatsoever for me on aicp.... no reboots, no sods and it has been like 16 hours or so from the installation. i'm confused. running on 2g/3g all the time. will test on wifi later a bit.
[G2 Android Development] jpaulwaite:
Hey buddy. R11 causes repeated hard reset on vs980.
[G2 Android Development] hovanhuang:
maybe it's my device.

R12 on D800 Mahdi 8/9. no sound, DSM manager keep stopping.
[G2 Android Development] 1ceb0x:
4g? it might be something related to LTE imo..
[G2 Android Development] Lawlrus:
[MENTION=5438598]RenderBroken[/MENTION]

Have people been giving you modem logs along with the last kmsg? Or just last kmsg?

I know the Verizon sod's back on 4.2 kernel sourced KitKat aosp roms were because of the modem panicking. Maybe this is something to look into?

Sent from my Vs980 running Jackpotclavin's cm11
[G2 Android Development] jpaulwaite:
4g what? The device? What the hell are you talking about?
[G2 Android Development] 1ceb0x:
are you on LTE or 3g connection?
[G2 Android Development] blacklight1025:
It did the same for me. I think he said he's switching out the msm hotplug see if that was the problem. Honestly, R11 is the only one I really had problems with. Strange.
[G2 Android Development] RenderBroken:
OK So I have re-setup a new branch and I am finally back to stable. I was also having issue with FM Radio Patches causing my audio driver to crash thus whenever the phone would suspend it would crash to either SoD or reboot. So I will have to work with that Dev before continuing. I plan on releasing a new build tonight that should be stable for all, use the new hotplug, fix the different bugs from the beginning. IF all can confirm that its good for them and their carrier model I will continue.
[G2 Android Development] RenderBroken:
The issue lately was definitely something in the new code causing it to suck ass. I have looked at the modem logs before when I know its a modem crash and they did not provide much to go on. I do know most of the time if its a modem reset it will list that as a reboot reason at the bottom of a last_kmsg. Thanks for brain storming and assisting though! Doesn't hurt to have help from all places!
[G2 Android Development] 1ceb0x:
no issues on wifi as well. guess i am just a lucky bastard. thanks for R11 mate.
[G2 Android Development] RenderBroken:
NP, R12 is about to be uploading. I had not heard any problems with Wifi during the fiasco.
[G2 Android Development] RenderBroken:
Also r12 will be uilt with MSM_Hotplug and r13 will be built with Falcon_Hotplug.

This way we can compare the two. To see if msm_hotplug will cause instabilities or not, etc Other than the hotplug there will be really not differences between the 2 builds.
[G2 Android Development] quang61:
Thanks Render... I waited longtime to run your kernel. Just flash r12...sdcard already here.. No issues jet [emoji1]

From F320L / mahdi 817
[G2 Android Development] Boot_Derran:
So far so good. Only problem now is a lot more audio glitches. Some of which occur w/screen on. It would happen while streaming or just listening from the player. Beyond that there have been no symptoms of those annoying reboots.
[G2 Android Development] Matze060906:
Just installed R12. Will run it with default settings and will report no reboots (I hope)... [emoji2]
[G2 Android Development] hamisgood:
R12 doesn't seem to work for the F320S. Attached a screenshot of the error I get after flashing the kernel.
[G2 Android Development] Matze060906:
Try to wipe cache and dalvik. If this don't solve the problem download it again and flash again...
[G2 Android Development] MaluNoPeleke:
I think I could solve this problem with switching to Intelliactive governor
[G2 Android Development] quang61:
Run for me... Feel a little bit hoter than original mahdi

From F320L / mahdi 817
[G2 Android Development] hamisgood:
Redownloded it already and it still does not work. First time happening for any of the Render kernels. Guess I gotta wait for R13.
[G2 Android Development] 1ceb0x:
no problems on aicp so far running r12. snappy as hell :)

---------- Post added at 08:58 AM ---------- Previous post was at 08:48 AM ----------

go to settings - apps - phone app - clear data/cache. should work after. it is not a kernel issue, sorry!
[G2 Android Development] hamisgood:
Doesn't work for me still. Don't think it's the zip file corrupted as I managed to extract the files without an error. I never had to wipe anything before flashing a kernel.
[G2 Android Development] 1ceb0x:
R12 for me was great so far. anyone else wants to chime in their findings?
[G2 Android Development] Matze060906:
Running on R12 since 6 hours without reboots... [emoji2]
[G2 Android Development] markjh:
Same here, R12 stock settings and since 3 hrs no reboot.

Gesendet von meinem LG-D802 mit Tapatalk
[G2 Android Development] Matze060906:
I forgot to say that I'm running latest Mahdi on d802...

---------- Post added at 12:53 PM ---------- Previous post was at 12:37 PM ----------

Bad news: reboot by taking the phone into sleep...

https://docs.google.com/file/d/0BwVur07uzqm6aWY2Wkt6ZmhJNDQ/edit?usp=docslist_api
[G2 Android Development] Saythis:
R12 on Mahdi is running perfectly. No reboots so far for about 6 hours.

Sent from my LG-VS980
[G2 Android Development] MaluNoPeleke:
Also no reboots with R12 on a D802 with Mahdi 08/17
[G2 Android Development] Matze060906:
Am I the only one with a reboot? [emoji33]
[G2 Android Development] quang61:
Noop.. Me too [emoji1] kumpel@

From F320L / mahdi 817
[G2 Android Development] RenderBroken:
Can you provide more information? Like Phone Model, Rom, etc. Can you provide logs too? Thanks!

Same here, could you also provide logs? Most likely a logcat will help the most but the others don't hurt either. Thanks.
[G2 Android Development] RenderBroken:
Log did not really show anything but thats just how it is sometimes. Thakns though. If you have another def let me know!

Did you get a log? Thanks!
[G2 Android Development] RenderBroken:
ACtually what rom you running? Vanir? I may have to add in a BOOTCLASSPATH to make it work right. I had to completely redo my Ramdisk so I may have missed it. Thanks!
[G2 Android Development] Matze060906:
The problem was: Syslog haven't root rights before. I flashed newest Mahdi yesterday and haven't started syslog...
[G2 Android Development] chillstep1998:
Reboot when I woke phone up.

AICP latest nightly

R12

Cpu: 96MHz-2.3GHz Intelliactive

GPU: 200MHz simple_ondemand

Read-Ahead:4096

Io-sched: row

Logs --> https://www.dropbox.com/s/pypwjz34s2hbjs2/2014-08-19_15.44.zip
[G2 Android Development] blacklight1025:
No reboots, idk what you changed, but its working for me! VS980, mostly stock settings. RAB 1024 and some small scheduler, governor and minfree settings, and changed multi core power savings to 2.
[G2 Android Development] Matze060906:
Second reboot by changing governer to intelliactive...

https://docs.google.com/file/d/0BwVur07uzqm6d2xMMnBvUTVqc2c/edit?usp=docslist_api
[G2 Android Development] Raagh:
Hey [MENTION=5438598]RenderBroken[/MENTION] news flash

I ve started building AICP from source a few days ago(finally after a clean ubuntu install)

Managed to build without issues.

Learned how to fork some of their repos

Made some small modifications(changed dpi,removed apps, add new apps) and push the changes to my github.

Still building without issues.

Im searching how to change everything that is set in the build.prop to D806( im using d802 sources but my phone is a d806{exactly the same phone}), so it d be nice to set everything as it should be.

Also d love to start building using Sabermod/Linaro toolchains, but well one thing at a time.

When you manage to solve the issues that the kernel is facing i ll start learning how to replace aicp 's kernel for yours.

In the mean time good luck and dont give up :).

If anyone is starting in the android development community or simply wants to share some info please pm we could all start a hangouts conversations or something like that.

Raagh
[G2 Android Development] Saythis:
Well, as soon as i went to listen to some music with Spotify and the screen was off I got an sod..

Sent from my LG-VS980
[G2 Android Development] markjh:
Still no reboot! Running it for like 8hrs now. Mahdi 8/17 stock settings. Thanks ☺

Gesendet von meinem LG-D802 mit Tapatalk
[G2 Android Development] RenderBroken:
One thing people need to keep in mind is I have it set so when the screen is off the hotplug driver forces it so only 1 core is online. So if that is the case. I don't believe 96MHz is going to cut it. I would bumb it to 422MHz since it does this now.

Thanks for the log! I may drop intelliactive or find a way to make it work with this kernel without issues. Thanks.

Sounds Great! You are allowed to have Dev discussions in the thread if you need a place to talk. I am always willing to help!

Same as above, hotplug forces only 1 core online when screen is off, so if you dont have a high enough freq it may have issues like this. I may go ahead and open it back up. If you all want to do so just go to:

/sys/module/msm_hotplug/max_suspend_cpus

and change it from 1 to 4. Or whatever you want. I use ES to change these really fast and easy.

As always let me know how it goes! Thanks. I am pretty happy with the speed and stability of this build. I have had no issues like always but its been freaking fast! Thanks Guys.
[G2 Android Development] hamisgood:
I'm running on TeamEOS as it's the one of the two only AOSP ROMs, and the only one with audio not skipping for me.
[G2 Android Development] quang61:
Sorry, i don't have.. But what i got is more a SOD than a reboot

Till now I'm happy with r12..battery 33°C 5,5h SOT, smooth, quick.. Audio ok... Good job [emoji106]

From F320L / mahdi 817
[G2 Android Development] RenderBroken:
Thats good to know. I will add in the BOOTCLASSPATH and that should fix your problem.
[G2 Android Development] RenderBroken:
So the plan is for the next few releases is to 1 do my major Sheduler bringup, 2 MDSS (Screen Drivers) Bringup, 3 Major Sound (N5) Bringup. Maybe not in this order but this is the plan!
[G2 Android Development] Matze060906:
And the next one will have falcon hotplug? What is the difference to msm hotplug?
[G2 Android Development] MaluNoPeleke:
Have you seen my syslog report via PM?

Was it helpful?
[G2 Android Development] RenderBroken:
They are very different from each other. msm_hotplug just gives a greater control and I feel that it gives a better mid to high end performance where falcon does amazing at the lower end. By that I mean whether you are reading a book or playing a game or multitasking. Lower to higher performance demand.

Not really but thats how they are sometimes. There are some that help tons. Just have to keep gathering them. Thanks brother.
[G2 Android Development] quang61:
Awesome !!

From F320L / mahdi 817
[G2 Android Development] Matze060906:
[MENTION=5438598]RenderBroken[/MENTION]: another reboot...

https://docs.google.com/file/d/0BwVur07uzqm6MWhCb3B3NEd1LUk/edit?usp=docslist_api
[G2 Android Development] RenderBroken:
It just doesn't like you. And your settings go are at stock?
[G2 Android Development] Matze060906:
Settings are all stock. After I switched to intelliactive the phone rebooted. But trickster haven't set kernel settings on boot.

I hope this Odyssey of reboots ends with the next build. I want run your kernel on my phone!!!