yashsingh1/xdaforums huggingface dataset:
[HTC EVO 3D] bigwillyg:
Yeah, life has been very hectic lately. I have seen some of the commits but haven't looked at the actual code in repo. I like them, especially the updated interactive. I am a relative noob so I would have known to check Google for updated code. I hope I can get around to updating my kernel this week.

As far as faster bus speed, from what I read on another site, sometimes having a properly overclocked fsb can limit you from running the faster overclock CPU speeds (1.6, 1.7). But the upside is that the lower speeds were all used to do run much much better.
[HTC EVO 3D] mrg666:
The 467+ bus made a clear difference at 1.6 and 1.7 GHz. I am using 1.7 max as default on my phone. I was afraid with the same reason about crashes from other users but there is no complaint specific to >1.5 yet. There were two reports about crashes below 1.2 GHz. I have reverted the bus speed changes at lower frequencies. They didn't make much difference anyway. I would recommend adding that higher bus speed to Buttered too.
[HTC EVO 3D] t3khe4d:
that's awesome, when things settle down here I'll flash and let you know,... long day at court with pops, man's 70 going on 21.. still partying.... SMH :eek:

so you know, I supported the notion of mpdecision possibly being unnecessary, the concept/idea of adding a "decision" before or just executing and getting back to sleep didn't make much sense, but, if doing so requires less "resources" to complete, then really that's what matters, JUICE!

so I thought, how am I going to test this out? well,.. 1st things 1st, any experiment worth it's salt can't be performed with faulty tools.

that brings me here, rather fortuitous really that you happen to be tinkering on this same phone, seems you have a rep for solid work and that's what i like to here :good: and if it is working better than you expected, well, then,... you never know what will turn up with a little scratchin' :D

shHHAAaaAADYYy!!!

SMH
[HTC EVO 3D] mrg666:
My testing today didn't show any battery savings. Plus there seems to be some impact on performance. I will give another day for testing.
[HTC EVO 3D] kickyoace:
I shall complain then when I get to 1.7 and 1.6 clocks I crash on anything graphics intensive but 1.5 it runs with no crashes at all all the crashes are a soft reboot not complete reboot
[HTC EVO 3D] mrg666:
Seriously, were you running 1.7 GHz reliably with the earlier builds?
[HTC EVO 3D] Meowdib:
Thanks for all your hard work. I appreciate it.
[HTC EVO 3D] mrg666:
So cute! Is this a hedgehog?
[HTC EVO 3D] Meowdib:
baby Beaver
[HTC EVO 3D] mrg666:
Watch your finger. They can really bite. :)
[HTC EVO 3D] Master Gowa:
I ran the 767 test build today because I'm always excited when there is a new build. Thank you for all that you put in.

Since we are on the subject... I wanted to ask a noob question. What is exactly is mpdecision? Some kernels ask (during the install) if you want the rom or kernel to handle it. From what one of the prevous posters mentioned... it sounds like it has no benefit. As you said though... most people put it in there kernel. So they must think there is something to it.

As far as my observation goes. I didn't notice any gain or loss. For me it seems to be running about the same as the previous build (which was awesome). I'm just a layman so I just run it and see how it "feels" with my normal use (which varies from day to day).
[HTC EVO 3D] kickyoace:
Before the bus increase yes I was what hardware revision do you have I have 002 it might be specific to the build and again thank you for all your hard work
[HTC EVO 3D] mrg666:
Mpdecision is a service that turns off the unused cores of a multicore cpu and turns on again when there is demand for cpu power. The whole idea is about saving battery by turning the unused cores off. Originally, this service runs in the stock ICS ROM outside the kernel. The following is what I wrote about this service and confirmed by other users.

"With the mpdecision service, second core turns off and on very frequently. This by itself causes additional work for the kernel and the single core constantly runs at higher frequencies. Without mpdecision, the second core switches off and on less frequently and it is off when the screen is off. But both cores run most of the time at the minimum frequency. Kernel becomes much more responsive and GUI becomes smoother. Testing also indicates no adverse effect on battery life"

Now, we are testing a kernel-based implementation of mpdecision. This time mpdecision is running in the kernel and we thought this would be more efficient and the benefit on the battery life can be achieved without too much drag on kernel performance.

In addition, the C-states are the low power states of the CPU when the unneeded parts of the circuitry (as opposed to complete core) inside each core are turned off and on depending on the CPU load. Switching the c-states is a faster and more efficient mechanism than turning the core on/off and it readily operates on each core. So, there are already two mechanisms other than mpdecision for saving power when CPU's are not used: C-states and scaling the CPU frequency. The CPU governors handle scaling the CPU frequency depending on the CPU load such as interactive, ondemand, etc.

We will see how it goes with the kernel-based mpdecision. So far, I have not seen any battery life improvement as we hoped but the performance didn't degrade as much as the original mpdecision either. I will keep testing for another day.

I hope this explanation makes sense.
[HTC EVO 3D] t3khe4d:
Excellent explanation!
[HTC EVO 3D] t3khe4d:
yeah, great explanation, simply articulated,... yeah don't get derailed on my account, you know what works, just thought it be nice to test and know locally using your stable kernel....

running 767 meow, doing mostly SD work, getting that 32gb10 in shape, had some clunky UI a few chokes in next launcher, at this point might be link2sd I'm doing, will let ya know after it calms down...

nice work, thank you!
[HTC EVO 3D] mrg666:
I have done the second day of test to confirm. The final result is that kernel-based mpdecison is worse both in battery life and also performance. I will not include it in the future builds. I am glad that we tested it and thank you for the request. I am also glad to see that the simpler/leaner kernel performs better.

How many battery saving methods there needs to be on top of each other to save the most battery? Since each of them comes with its own overhead, battery saving turns into battery wasting after a point. We have seen this happening and we are going back.

However, I think mpdecision can really be useful in a quad-core system. It is just too much for dual-core.

There is also the role of CPU governor we need to consider. We are using the latest interactive governor which is doing a really good job keeping the CPU at the lowest possible frequency most of the time while quickly giving the high frequencies when needed. I think the results could be different with a different governor.
[HTC EVO 3D] t3khe4d:
I too not happy with how my phone performed, the UI was very choppy, as if stopping to make a "decision" and then proceed :/
[HTC EVO 3D] mrg666:
There are sysfs parameters of mpdecision to tweak. I am sure you can adjust the parameters to make the system more responsive. Making the system more responsive will make mpdecision less effective. Removing it was the best option, imho. You can still experiment with those parameters. Please post your results if you do.
[HTC EVO 3D] t3khe4d:
haven't given up, just out-of-the-box experience was not so good. still tinkering.
[HTC EVO 3D] SkinnyBiggs:
Is the kernel capable with Harmonia?
[HTC EVO 3D] junxracr:
Re: [KERNEL] MiRaGe - for HTC stock ICS ROM - 3.0.68

Flashed on Meanrom v 2.6 and running smooth. Thank you. I also experienced your work on OV. Good to see your developing for Evo 3d now :)

I loved the OV, but this Evo 3d is amazing.
[HTC EVO 3D] wangcliff:
I love your NC ROM. Definitely I will try the kernel for my EVO 3D.
[HTC EVO 3D] mrg666:
I uploaded a minor update in the OP that fixes WiFi tethering and switches to simple FIFO net scheduler.
[HTC EVO 3D] Danger Dan:
Re: [KERNEL] MiRaGe - for HTC stock ICS ROM - 3.0.68

My phone got stuck at the bootanimation and wouldn't go past it. I have coolrom ics hboot 1.58
[HTC EVO 3D] mrg666:
Probably something went wrong with the flash procedure. You can boot into fastboot and restore the backup boot.img.

- remove the battery and reinsert

- press volume down and power until fastboot comes up

- connect the phone to your PC with USB cable

- use the command "fastboot flash boot boot.img"
[HTC EVO 3D] Danger Dan:
Re: [KERNEL] MiRaGe - for HTC stock ICS ROM - 3.0.68

I did that twice last night because I thought the same thing bad flash but I had to flash back to Mac. Maybe it was a bad download. I'll try and redownload
[HTC EVO 3D] mrg666:
If you can send the last kernel message after recovering that might help understanding what is going wrong. You can upload it somewhere and post a link here.

Since you are not using stock ROM and my kernel comes with any-kernel-updater, there can be problems in a custom ROM since the initialization in the ramdisk of that ROM is reused for the new kernel.
[HTC EVO 3D] Danger Dan:
Re: [KERNEL] MiRaGe - for HTC stock ICS ROM - 3.0.68

Ok I'm at work for another 7 hours so ill have to do it when I het home
[HTC EVO 3D] wjason:
Re: [KERNEL] MiRaGe - for HTC stock ICS ROM - 3.0.68

WiFi error on mean Rom 2.6
[HTC EVO 3D] mrg666:
That is expected as I posted in OP. But this is good to know. Thanks for trying and reporting.
[HTC EVO 3D] pbailey212:
Re: [KERNEL] MiRaGe - for HTC stock ICS ROM - 3.0.68

Not complaining, just informing. Wifi doesnt work for harmonia, or mobster, or midnight. I have been trying to test all stock bases roms. I will jeep tedting when I get time
[HTC EVO 3D] mrg666:
Can you check dmesg and post what is the message right after turning WiFi on? Otherwise WiFi is running completely fine on the stock ROM. Actually, it is showing exactly the same problem of delayed reconnection after wake up. I am testing a fix right now.
[HTC EVO 3D] hossman:
Re: [KERNEL] MiRaGe - for HTC stock ICS ROM - 3.0.68

I've noticed that flashing this kernel through recovery breaks WiFi (just says error under WiFi) but if you use flash image, as the op states, WiFi is fine.

I noticed this on harmonia and jmz and a couple others.

As for the delayed reconnection, I keep WiFi on during sleep, and I still get superb batt life

Thanks mrg!
[HTC EVO 3D] pbailey212:
Re: [KERNEL] MiRaGe - for HTC stock ICS ROM - 3.0.68

You are right. It does work with flash image GUI thanks for pointing that out. Well I'm now running mobster HD with mirage. I'm sure I won't be disappointed.

Do you want my dmesg.txt from flashing with 4ext recovery and not having working wifi?
[HTC EVO 3D] mrg666:
This is helpful, thanks!

I am working on fixing the delayed (sometimes never) WiFi reconnections. Hopefully, there will be a fix so that we don't need to keep it awake all the time. Mako drivers don't have that problem but WiFi tether is not working with them. The problem is that the Mako driver is not compiling when I enable -DAP_ONLY option required for tethering.

I will also check the flash script file to see if there is something wrong to cause problem with the recovery flash method. Which recovery do you guys use? I will be testing with 4ext 1.0.0.5 rc9. For now, stick with the excellent Flash Image GUI :)
[HTC EVO 3D] mrg666:
Dmesg would be helpful, thanks! Glad that you got it working.
[HTC EVO 3D] pbailey212:
Re: [KERNEL] MiRaGe - for HTC stock ICS ROM - 3.0.68

I'm on 4ext 1.0.0.5 r8 and here is my dmesg https://www.dropbox.com/s/vbdypgjuq8nuiml/dmesg.txt
[HTC EVO 3D] mrg666:
Thanks, this explains the problem.

<3>[ 152.971008] bcm4329: version magic '3.0.62-ck1-MAC-v3.5+ SMP preempt mod_unload ARMv7 ' should be '3.0.67 SMP preempt mod_unload ARMv7

Somehow, the bcm4329.ko module was not copied to /system/lib/modules when flashed in the recovery. Kernel is complaining about not finding the correct version. I will check the flash script and binary and verify with 4ext recovery after fixing WiFi. Flash Image GUI is more convenient anyway.

BTW, you are still using 3.0.67 build. You can download the latest build which is 3.0.68.
[HTC EVO 3D] pbailey212:
Re: [KERNEL] MiRaGe - for HTC stock ICS ROM - 3.0.68

Noted and updated
[HTC EVO 3D] Danger Dan:
Re: [KERNEL] MiRaGe - for HTC stock ICS ROM - 3.0.68

Used flash image GUI and no flaws. WiFi works everything. Thanks
[HTC EVO 3D] optimusv45:
yes, it is.
[HTC EVO 3D] mrg666:
The new build of MiRaGe is available

- Synced with Linux 3.0.77

- Enabled hardware assisted crypto engine in the kernel

- minor updates from CAF

- kernel_based mpdecision is NOT included after testing results

The download link is in the OP.

Enjoy!
[HTC EVO 3D] t3khe4d:
LOL

say any idea why I'd get these scores then, then test again and only get around 7K ??
[HTC EVO 3D] mrg666:
Let me quote from my previous reply to a similar question here

"The inconsistency of Antutu benchmark (and others) is mainly due to background processes of Android. In the background, Android speculatively loads apps and also kills them when memory is needed. Additionally several/many sync processes run in the background. On top of all, there is htc's mpdecision task constantly stopping the second core, if you have not deleted it. Android does so much more in the background than the desktop operating systems. This kind of inconsistency is normal and expected. If you want to benchmark, the best time is after keeping the system awake for several minutes without opening too many apps, disabling sync can also help. I check the cpu load of running background processes using System Monitor lite and freeze the unneeded ones using link2sd."

So what you see is completely normal because Android tries to be smart, doesn't sit there and wait for you to do something.
[HTC EVO 3D] t3khe4d:
OK my bad, thanks.
[HTC EVO 3D] mrg666:
It is not your bad. I was quoting from another MiRaGe thread in another forum.

Actually, it is still bad that you missed this :D
[HTC EVO 3D] hossman:
Any word on the new project:D
[HTC EVO 3D] mrg666:
I haven't given up with the AOSP project but, I don't know how, kernel development accelerated again. I thought the kernel development was winding down.
[HTC EVO 3D] hossman:
Lol....word is getting out your kernel saves batt.....:cool:
[HTC EVO 3D] Master Gowa:
Your kernel gets more awesome by the day. Question though. I used the test kernel with mpdecision in it. When I update to today's build should I flash the mpdecision_delete.zip again?

--- Edit.

The link to the mpdecision_delete.zip now points to the 5/5 kernel build.
[HTC EVO 3D] mrg666:
Thank you!

No, you don't need to delete mpdecision again. The mpdecision was in the test kernel and the new kernel will replace it without mpdecision.

Fixed!
[HTC EVO 3D] t3khe4d:
There's no "decision" needed. :thumbdown:

3.0.77 :thumbup: thus far.

Sent from my HTCEVOV4G using broken xda app-developers app
[HTC EVO 3D] t3khe4d:
Awesome so far.

3.0.77-0508 running smooth, UI is great, no lags, thank you.

Q? mrg,

Have you any luck with the weather live wallpaper freezing?

I've poked around and didn't find any answers on why it freezes. Cool paper to bad it chokes.
[HTC EVO 3D] mrg666:
Since I use holo launcher hd, I can't even use sense live wallpapers. In any case, I don't think kernel could be a problem for the live wallpaper but I tried magic smoke wallpaper and it works fine. Try to clear the data of that live wallpaper and restart it; might help.
[HTC EVO 3D] t3khe4d:
hmm, yeah didn't think it was the kernel, in fact it runs the ani real smooth, it's when it loops it seems to lock, thought maybe you'd heard somethings regarding the paper. figured the ani was like the bootani, just a series of img flipping.

I run Next Launcher for the eye candy,... my eyes have a sweet tooth :eek:

another good one for cpu/gpu is magic fluids.
[HTC EVO 3D] gwzapata:
Kernel for 4.2.2

Do you have a kernel for 4.2.2 I can try it out? I am on Virgin Mobile, Dirty Unicorns, hboot 1.50.
[HTC EVO 3D] mrg666:
There is no standard for "4.2.2 kernel". The 4.2.2 variations in this forum are not compatible among each other. Each can have different kgsl, bluetooth, camera, sound, etc drivers. Some of them implement ion, some of them use pmem. MiRaGe boots with some of them (e.g. Dirty Unicons and Evervolv), camera works on some, not on others. KGSL driver and ION implementation on some of the ROMS are incompatible and WFTN does not even boot although it was booting two-three releases earlier. So if you are using a 4.2.2 ROM, sticking with the default kernel would be your best bet.

Also, I was going through agraben's thread and I have seen what he went through and final sad situation due to some other kernel developer interfering with his ROM development. I would do everything I can to avoid causing such a situation. Guys, I wrote this so many times already and included in the OP as well.

USE THE DEFAULT KERNEL OF YOUR CUSTOM ROM. MiRaGe IS FOR STOCK ICS ROM.

I will only support a custom ROM through its developers if they ask for it.
[HTC EVO 3D] bigwillyg:
Just a note, there is more to the agrabren situation then what is in that thread. The thread only presents his side and doesn't explain everything else that lead to it (kanging, backstabbing, lying, all by team cm devs).
[HTC EVO 3D] mrg666:
Bigwilly, I have nothing against you. But I have read enough to decide how a (no name calling) developer Chad Goodman is. Please keep anything related to him away from my thread. I said and I am done with this. I had to take a side and I am on the other side.

Wherever I look and find something useful done (by agraben, showp1984, faux123, and other names you listed) for this community, you come back to say something bad about them. This is wrong and needs to stop.
[HTC EVO 3D] t3khe4d:
mrg?

I've read a lot of threads so I may be mistaken, did I read somewhere you did kernel work for the Optimus V ?

the reason I ask is that was my last phone and I may put it back in service for my mom, thought I'd hook it up before I did.

if you did, or know where to look it would be much appreciated.

thanks :)
[HTC EVO 3D] hossman:
Android central for sure
[HTC EVO 3D] mrg666:
The kernel is not same kernel since the devices are different. But you can find MiRaGe (both kernel and ROM) for Optimus V using one of the following links

http://xdaforums.com/showthread.php?t=1703152

http://forums.androidcentral.com/op...2-rom-kernel-mirage-cm7-2-iho-04152013-a.html
[HTC EVO 3D] t3khe4d:
oh, figured as much, I'm savvy on build2device specifics.

hey man that's great thanks, I'll check those out when I get the chance here soon, yeah great phone, VERY reliable, good entry transition phone from flip2smart.

:good: thanks mang!

PS

people,... save the drama for FB... geeess :/

... no txting on the dance floor. :P
[HTC EVO 3D] bigwillyg:
Well...I will leave it there for the sake of not ruining your thread (not my intent or interest). On an on topic note, I was informed that you had a fix or patch for Wi-Fi connect. I couldn't immediately identify it in your repo and wanted to ask what fix that was.
[HTC EVO 3D] mrg666:
The fix was for the reconnection problem of bcm4329 wifi driver. The stock wireless driver was frequently having difficulty with reconnecting or even reinitializing after wake-up. The solution was keeping wifi always on. Bu,t yet again, reconnection was still a problem after leaving the wifi area and coming back in.

I have backported the bcm 4329 driver from CAF msm-3.0 kernel. Please check the directory, drivers/net/wireless/bcm4329, in my repo. If you copy everything from that directory, you should be good to go. By checking the history of commits in that folder you can also get the patches but it can be a little confusing since I tried other fixes and moved the directories for cleaning up the messy directory structure of original HTC source. Just to make sure, you might want to confirm that the user who informed you is using the bcm4329 driver not bcmdhd. I didn't fix anything in bcmdhd.

I would be happy to collaborate/interact with you anytime. Thank you for your understanding.
[HTC EVO 3D] hossman:
Maybe its just me, but your intelligence blows my mind.

Thanks for the great stuff mrg:beer:
[HTC EVO 3D] mrg666:
Thank you!

I am just pretending to be :)
[HTC EVO 3D] kickyoace:
Delete plz sorry
[HTC EVO 3D] t3khe4d:
mrg?

thought I'd work on my brownie points here and jump in on the sweep2wake debate a few posts back,...

I didn't think much to say anything on it because I had no practical experience only theory but today I ran into a scenario,

a scenario that many will undoubtedly run into often, one I could have used today for sure, NAV & car audio,

it would appear to be easier to operate the phone while mounted without having to gorilla grip it to wake it up,...

I think it's a much more useful option that can be toggled, then a dangerous Li-ion bomb charger. :laugh:

just a thought. :confused:
[HTC EVO 3D] mrg666:
Well, it is really hard to resist when you ask but I will :) I don't want to add sweep2wake feature. Are there any gorilla grip practice guides? :)

The navigation keeps the screen on all time. You can also set your phone to keep the screen on when connected to power in the developer settings. And there are many applications in the play store to keep screen on when some apps are running.

You can always fork my repo and add any feature you want. I would be more than happy if you do so. Create a thread here and give a different name if you want. We can collaborate. It is not really that difficult. Post your questions here and I can help with them

I would be very happy to remove fast-charge if nobody is using it. Actually, I build a special version for my phone without fast charge every time.
[HTC EVO 3D] hossman:
I don't want fastcharge

Could you post your special version as well??:beer:
[HTC EVO 3D] mrg666:
There was only one request for fast charge. Including you and me, the people who didn't care/want are in the majority. So I have reverted the fast charge commit.

Edit:

The new 05112013 build is available in the OP

- Synced with 3.0.78-rc1. Since the patch is tiny, I didn't wait for the final release which will be the same

- added msm thermal management to decrease overclock risks and eliminate errors in the kernel log from HTC source - "Thermal: failed to read out thermal zone 1"

- backported msm random number generator fixes from CAF msm-3.4

Enjoy!

PS: I have also tried the new Linaro gcc 4.8 toolchain. It was not ready yet. I will keep testing.

PS-2: I have forgotten reverting dynamic button back light patch since it was not working. I have rebuilt and uploaded again. If you have downloaded before this edit please download again. Sorry.
[HTC EVO 3D] busventinc:
Thanks for posting the kernel message. I checked the kernel log and the following is the reason for boot error.

[BATT][tps65200] TPS65200 shutdown

The battery driver simply tells the kernel to shutdown. This is the first report of this kind for MiRaGe kernel. If you want to correct the error, I need some more information. Are you using the standard battery? Was charge too low or the battery too hot? How old is your battery?

You can also continue at the MiRaGe thread if you want to follow up on this specific problem.

__________

Digitalhigh,

The kernel log also tells that thermald binary does not exist in MIUI. Please get the latest build from my thread since it includes the kernel-based thermal management.

No I am not using a standard battery it is a sensation battery but compatable I also flashed the your latest kernel on blurom with flashgui and had no errors only received error through.miui

---------- Post added at 12:58 PM ---------- Previous post was at 12:55 PM ----------

Battery is fairly new about a month had full charge light was green
[HTC EVO 3D] mrg666:
Can you try the latest build in my thread just to make sure missing thermald is not the cause?