yashsingh1/xdaforums huggingface dataset:
[HTC EVO 3D] mrg666:
Maybe notification bar open/close is not sufficient. Try swiping the system monitor page back and forward. Also try to open system monitor as early as possible and see if the second core panel is completely blank. I have reduced the second core hotplug threshold. Let's give one more try. I will turn on debugging and will ask more detailed data next.

http://www.mediafire.com/download/4aqg7bg0pxpki4l/MiRaGe_shooter_jb_test_kernel_4.zip
[HTC EVO 3D] SketchyStunts:
the instant my phone booted i opened system monitor, swiped back & forth between pages & the 2nd core remained blank
[HTC EVO 3D] mrg666:
I have turned on debugging in the following test kernel. It would be great if you can post dmesg after boot. Let me check what is going on with the second core

http://www.mediafire.com/download/85y2ctbg855e353/MiRaGe_shooter_jb_test_kernel_5.zip
[HTC EVO 3D] SketchyStunts:
it will be a minute before I can get a dmesg but upon flashing test 5, the second core will become active :)

EDIT: https://www.dropbox.com/s/mpae9sxle6zwkuv/dmesg.log

---------- Post added at 02:31 PM ---------- Previous post was at 02:21 PM ----------

that 2nd core is bouncing around quite a bit sitting there
[HTC EVO 3D] catbert77:
Same results as Sketchy with the kernels just posted.

'Twas so snappy that I can't believe there wasn't a core running before. It feels crazyfast now.
[HTC EVO 3D] mrg666:
Thank you very much for your help. I can also see in your dmesg that second core is turning on and off now. So here is the test build(s) with fixed autosmp and also compiled with gcc 4.8 based latest linaro toolchain.

ICS kernel: http://www.mediafire.com/download/da4lo1pdqf1f4k0/MiRaGe_shooter_test_kernel_01092014.zip

JB kernel: http://www.mediafire.com/download/hkyrcctyb1xnh45/MiRaGe_shooter_jb_test_kernel_01092014.zip
[HTC EVO 3D] SketchyStunts:
No, thankyou! I got to flash 7 kernels today :) :cowboy:
[HTC EVO 3D] kr338r:
flashed this last one & clocked in

@ 11994 on Antutu

(best bench ever for this old dog).

many, many thanks for your efforts!
[HTC EVO 3D] somekid15:
Do you think you could post a kernel link for the test build WITHOUT 2nd core working,tried it and got amazing battery and I wanna get back on it
[HTC EVO 3D] mrg666:
LOL, I never thought a buggy build would have been preferred. You can park the second core with the following command.

echo 1 > /sys/kernel/autosmp/conf/max_cpus
[HTC EVO 3D] somekid15:
Do I enter that in terminal with su?
[HTC EVO 3D] mrg666:
Yes you can use in the terminal.
[HTC EVO 3D] somekid15:
Thanks man it worked

---------- Post added at 11:42 PM ---------- Previous post was at 11:13 PM ----------

Does this kernel not have vsync?
[HTC EVO 3D] mrg666:
You tell me? :)
[HTC EVO 3D] SketchyStunts:
Been running strong with no issues so far.
[HTC EVO 3D] somekid15:
Using kernel tuner I don't see either vsync or sweep2wake, and there's only 2 governors for use. Also 3d GPU can only be set to either min or max no in between
[HTC EVO 3D] Obeezy562:
Read the OP it will answer every single question u have.
[HTC EVO 3D] pbailey212:
I can confirm, the second core was not running on the previous build, but it is on the current one.
[HTC EVO 3D] t3khe4d:
you could try using device profiles like in android tuner, a module found in the xposed repository.

I use the pro ver. for tweaking and haven't found a better tool.

I set profile to turn off data & wifi when screen turns off, i get AWESOME batt life.

1st image is without profile

2nd img is with profiles :D

these are of kernel 101
[HTC EVO 3D] mrg666:
Do you guys think we can move the latest test build to OP as stable now?
[HTC EVO 3D] SketchyStunts:
I had 1 reboot this morning at starbucks, not sure if it was kernel related or not.
[HTC EVO 3D] mrg666:
Reboots are most of the time kernel related. I am not moving these to OP in that case. Can you post last_kmsg?
[HTC EVO 3D] SketchyStunts:
https://www.dropbox.com/s/8igyij44zcnvzhb/last_ksmg.log
[HTC EVO 3D] mrg666:
This is a clean log. If you have not rebooted a second time after crash, the crash is due to hardware failure and you might need to reduce the cpu frequency.
[HTC EVO 3D] SketchyStunts:
I'm running it as is but i'll drop it a little. Not surprising it being a hardware issue, this is 4th 3D. lol
[HTC EVO 3D] Master Gowa:
Tried the 1/9 ICS test kernel and things seemed fine during use. Left my phone plugged in and went to sleep. Woke to it stuck on the boot animation.
[HTC EVO 3D] mrg666:
Based on the two instability reports, I have reverted the toolchain to the previous version. There cannot be any reason to deal with the code anymore since the two changes I made will not cause this instability. In addition the rest of the code base has been proven to be stable since a very long time. So the only reason could be the new gcc-4.8 based toolchain which had problems before. I thought it would have been improved by now, apparently hasn't. So here are the last test builds. I will not delete the previous test builds, feel free to continue with them if they are working fine for you.

In short 0109 and 0111 test builds are the same code built with different toolchains

ICS kernel: http://www.mediafire.com/download/uocpq0ofsl7082u/MiRaGe_shooter_test_kernel_01112014.zip

JB kernel: http://www.mediafire.com/download/3uw8c8xakgldwcz/MiRaGe_shooter_jb_test_kernel_01112014.zip
[HTC EVO 3D] Sultanxda:
GCC 4.8 causes some kernels to not boot entirely, and on my old HTC Sensation, GCC 4.8 even affected userspace noticeably (kernel panic when opening certain apps).
[HTC EVO 3D] mrg666:
Thanks, Sultan. We had this problem several months ago and I thought they had fixed it by now. Apparently not yet. Maybe they will never fix it for the older arm cores. Mako kernel with krait core has no problems with 4.8-based linaro toolchain.

I did some drastic changes in autosmp. It would be great to have your comments.
[HTC EVO 3D] Sultanxda:
I'm not sure if it's related to older ARM cores; I compiled the stock Nexus 5 kernel from Google with the newest official Linaro GCC 4.8 toolchain and it didn't boot. Compiled it again with Linaro GCC 4.7 and it booted.

Awesome! I'll be sure to try your new changes :)
[HTC EVO 3D] mrg666:
Problem could be the gcc optimizations as well.
[HTC EVO 3D] Master Gowa:
Is it possible to make an ION version of this kernel? Or is that a total rewrite?
[HTC EVO 3D] mrg666:
Johnnyslt added ION in his MiRaGe-based kernel for CM11 in the GSM forum. I could just port his changes in but I don't want to try without a device.
[HTC EVO 3D] Ch1ngl1ng:
If you ever needed a tester, I would certainly be up for it :P
[HTC EVO 3D] SketchyStunts:
me as well :)
[HTC EVO 3D] TeChNoC4AzY:
Mrg666 how are you updating this kernel still if you were going to get rid of your evo 3d? I'm not being smart, just remember you saying this in an older reply here. :)
[HTC EVO 3D] pbailey212:
I'm always up for testing as well
[HTC EVO 3D] mrg666:
Thanks for the help offer. But starting to test a different kernel while there are still problems with the kitkat based Roms will make the stabilization of those Roms more difficult. Kernel development is also difficult without a stable ROM. So it is better for everyone if we leave the kitkat Roms alone for now.
[HTC EVO 3D] somekid15:
Would this help with the GCC errors?

http://xdaforums.com/showthread.php?t=2106644
[HTC EVO 3D] mrg666:
Thanks, gcc problem has been resolved earlier after going back to the stable toolchain. I actually use that toolchain in your link and it has been working well. The fixed test builds are now in the op.
[HTC EVO 3D] simon21:
Anyone having their touchscreen not be responsive with this kernel? Sometimes my touch screen doesn't work, but starts working again when I put it to sleep and wake it up.
[HTC EVO 3D] jlmancuso:
Sounds like your digitizer is going out. This is a very common issue the the Evo 3d/V.
[HTC EVO 3D] tvall:
I began to have that exact problem running hood Pope with its stock kernel, after I shattered the bottom of my screen. And after spilling coffee on it, it got worse and developed 2 deadzones that refuse to respond.

your digitizer may be near death. I hear its a common issue with the evo 3d.
[HTC EVO 3D] mrg666:
Aw man! How can you do that to a lovely EVO3D. When I sold mine, it was like new, not a single scratch on it. I hate that lucky guy who bought it.
[HTC EVO 3D] SketchyStunts:
I've had to replace several digitizers on several of my minty 3D's due to dead spots. I'd get sooooo angry when they start to fail.
[HTC EVO 3D] tvall:
shattering I blame on the headphones I was using. They refused to stay in my ear. Accidentally stepped on them once and the evo fell about 2.5 feet and landed on the lower left corner on the metal rim. bought my nexus a week later.

The coffee, I fell asleep with it on the table, woke up with it in a puddle of coffee. Cameras No longer work, and touchscreen is almost impossible to use.

Traded it to my brother for 2 ipods and a DS lite. One of the ipods is running Linux and a gameboy emulator. The DS is sitting on a shelf.
[HTC EVO 3D] jlmancuso:
I still have mine. Besides the digitizer issue only the metal beauty ring around the camera is pulling up. Both are easy fixes but since I have moved up to another phone I just have not got around to fixing it.
[HTC EVO 3D] Alanman13:
Here's one for everybody. Periodically, after plugging my phone in to charge, my red charging light doesn't turn on unless I wake up the phone. It charges after that just fine though.

I'm running the latest mirage jb test kernel and dastin's hood pope. I don't know what could be causing it, and it doesn't happen all the time either. Maybe only when the screen has been off for a while and the phone is in deep sleep mode?

Curious if any one else has encountered this or if this is the right place.
[HTC EVO 3D] t3khe4d:
have you tried a different charging cable & charger?
[HTC EVO 3D] Alanman13:
Yes. I have tried 3.
[HTC EVO 3D] rootlinux:
Nicely done.

Thanks for your contribution and hard work.
[HTC EVO 3D] bigsupersquid:
Yay!

I was digging for a kernel source for the evo 3d v since I just got one as a 'new' toy...

Imagine my surprise when the dev who made the most stable GB for the optimus V shows up as my top search result once I phrased it correctly.

Awesome, and thanks for sharing.
[HTC EVO 3D] hossman:
Will you be developing something.....the op v days were great:beer:
[HTC EVO 3D] bigsupersquid:
Big foot steps to follow in over here, but yes.
[HTC EVO 3D] hossman:
The few of us left will be truly grateful:thumbup:
[HTC EVO 3D] mrg666:
Great to see you here and hear you are forking the MiRaGe source. I am sure everybody will be happy when you share your work. I will check your repo for sure. Unfortunately, I don't have the evo 3d anymore but let me know if I can help in any way.
[HTC EVO 3D] pbailey212:
Good to have you here. I'm curious to see what you have in store. I troll the ov threads once in a while and I was shocked on how much development that phone still gets.
[HTC EVO 3D] bigsupersquid:
by the time most of the other OS/V developers had dropped off I got more into android instead of just linux and assembly, and a couple new people showed up interested. Thekraven was a huge help too. So... there's still quite a little going on for the V considering its age and 'obsolescence.'

This phone, I got as a toy, plain and simple. Waiting on delivery to play with it. I like 'legacy' devices... they suit my price range preference. I just can't justify spending hundreds on a phone... and this one has some nice specs, really.

Minimum, I'm gonna try to build the kitkat I'm using now with the added armv7 features and code, for this.

Nice to have a good kernel to start from, and there's enough ROMs in the forum here to hijack good device folder contents.

I have app ideas too... the only way I can think of to make any dough programming (other than underpaid desk-slave) is apps. This'll give me 3 devices to test on now.
[HTC EVO 3D] jcfunk:
Mrg666 can you help I tried to compile MiRaGe kernel but I got an error.

C drivers/gpio/gpiolib.o
CC drivers/cpufreq/cpufreq_conservative.o
CC fs/locks.o
/sd-ext/btkernel/shooter-mirage/drivers/cpufreq/cpufreq_conservative.c: In function 'dbs_check_cpu':
/sd-ext/btkernel/shooter-mirage/drivers/cpufreq/cpufreq_conservative.c:366:32: error: expected ';' before ')' token
/sd-ext/btkernel/shooter-mirage/drivers/cpufreq/cpufreq_conservative.c:366:32: error: expected statement before ')' token
make[3]: *** [drivers/cpufreq/cpufreq_conservative.o] Error 1
make[2]: *** [drivers/cpufreq] Error 2
[HTC EVO 3D] mrg666:
It seems you need to remove ')' before ';' at the end of line 366 of the file drivers/cpufreq/cpufreq_conservative.c. Since i never used conservative governor that typo was never fixed.
[HTC EVO 3D] jcfunk:
I used shooter_config to compile. I followed the directions in your second post , the only thing I did different was edit to make file so that it would not cross compile. Since I'm building the kernel my evo 3D
[HTC EVO 3D] mrg666:
Conservative governor is not enabled in shooter_config. I suggest double check what you are doing.
[HTC EVO 3D] jcfunk:
Your right, don't know why it's trying to compile. Going to git source instead of using zip download.

UPDATE:

Git worked, was able to compile.
[HTC EVO 3D] nobreak1970:
Using the latest test build, seems ok.

Any further development on this kernel. :)
[HTC EVO 3D] johnnyslt:
Request !!!

mrg666, do you think you can port v4l2 camera drivers to our Evo 3D kernel and camera sensor? The changes are on CAF, maybe you can give it a try if you have the time and mood ? We need it to make camera work on JB 4.2.2 with ION memory allocation.
[HTC EVO 3D] mrg666:
I am not sure, let me check how it works. I will post an update if I can.
[HTC EVO 3D] PhatWebah:
Another Follower

Like many of the other replyers in this thread, I used your CM7 ROM for my Optimus V; turning a relatively useless POS into a beast! When I first got my EVO 4g V (aka EVO 3D), I followed this thread and I tried a bunch of different ROMs until I settled on Harmonia. I like it, but it is nothing special. I have also applied other mods to arrive at my current configuration:

Baseband: 1.06.00.0426

PRI: 1.53_145

PRL: 60690

HBoot: ENG S-OFF 1.04.2000

Recovery: 4EXT Touch v1.0.0.5 RC8

I have been experiencing problems with text messaging and roaming, but most of the time the phone works well. However, I do not love the ROM and have been itching for a change of scenery. I never really used the stock ROM and would like to try it now, with your kernel. I would like to have the newest stock ROM, but I would not want to loose any of my current modifications. If you have the time and knowledge can you answer a few questions for me:

1. Will your kernel work with the above modifications?

2. If so, can I flash the newest Stock ROM without loosing S-OFF? ENG HBoot? Updated PRL? Updated Radio?

3. What recovery works best with a stock ROM?

4. Where would you recommend I get the stock ROM?

Thank you in advance for your contributions to this community!
[HTC EVO 3D] mrg666:
I don't think MiRaGe kernel would have any problem with your modifications.

There is no RUU yet that will give you the latest 2.95 stock ROM at one step. You will need to flash the one-and-only RUU that will give you the 1.13 build of the stock ROM. Then, you can apply the two OTA's one by one (1.14 and 2.95). But you will need to restore your settings and apps after this since the procedure will wipe your phone completely. So do a backup first.

The question is: will you stay with the stock ROM? If you are not going to stay with the stock ROM, it is not worth going through all this and wipe the stock ROM again. You can just apply the radio, etc firmware with the zips prepared by ramjet and keep your settings and apps. See this thread for more details and download links.

I use 4ext with the stock recovery. You can download and install the 4ext updater from this link. The updater will download and install 4ext recovery. The other option is TWRP. You can download the recovery image from this link. And flash it with Flash Image GUI. This is my preferred method but you will see other TWRP flashing methods at their site.

You can find the 2.95 stock ROM (someone has packaged it, not official, minus radio, firmware, etc) at the same forum where I gave you a link above for the update thread. But if you do the RUU > OTA1 > OTA2 method you will have the latest "official" stock ROM anyway. Alternatively, you can also flash the unofficial 2.95 stock ROM and apply the firmware zips separately. There are multiple other paths that you can follow.

You can find more detailed information at XDA and androidforums. Just check the stickies.
[HTC EVO 3D] THC Butterz:
I really like this kernel so far and am trying to develop my first rom right now using this wonderfull kernel
[HTC EVO 3D] PhatWebah:
You are a gentleman and a scholar. I think I will take the time and install using the stepped method you describe. I'm planning on sticking to the stock ROM for a while. I'm not too worried about loosing apps, but I do have one more quesiton. At what point in the procedure should I flash Gapps? I'm assuming after the OTAs?

I just was wondering what you mean by one and only, I found a link to RUU 1.13 on this thread. Were you referring to a specific RUU.Will this (or any) RUUs replace my HBoot?
[HTC EVO 3D] mrg666:
Gapps is not necessary with the stock ROM neither after RUU nor OTAs. Gapps is only used with custom ROMs since Google does not allow its apps distributed by others without permission.

There is only one RUU and you can get it here.

Assuming you are with Virgin Mobile

, choose the exe file with the name starting with "RUU_Shooter_ICS_35_S_Sprint_WWE_VM".

This is important: don't flash the wrong RUU otherwise you can brick your phone.

RUU and OTAs will be replacing your Hboot. You will also need to relock your bootloader before applying the RUU. You can unlock again after the last OTA and root again. But I am not the real expert with these RUU and OTA topics, I am sure you can get better answers from ramjet if you ask him in the thread I have given in the link. Ramjet, if you see this and feel necessary please comment.
[HTC EVO 3D] ramjet73:
I agree with everything you said but just want to add a couple things.

The HTC ROM Upgrade Utility (RUU) checks the customer ID (CID) before flashing and the Evo V is SPCS_002 while the Evo 3D is SPCS_001 so you shouldn't be able to flash a complete RUU for the wrong phone but I wouldn't suggest even trying. ;)

Also, since there have been two over-the-air (OTA) updates for the Evo V since the one and only RUU, S-ON users have to flash a zip file to downgrade their main version (mainver) before running the RUU if they took the November OTA and cannot flash the RUU at all if they took the March OTA since the hboot was upgraded from 1.57 to 1.58 and the RUU process doesn't allow hboot downgrades.

Hopefully a VM RUU will become available soon that includes the March updates and then all S-ON users will be able to flash that.

For Sprint S-ON users that took the March OTA setting the mainver to a low value should still work to install the ICS 2.89.651.2 RUU since the hboot version stayed at 1.58.

Hope that helps. :)

ramjet73
[HTC EVO 3D] mrg666:
This is the expertise I was talking about. Phetwebah, follow ramjet from now on. You will be in good hands. I can better help with the kernel.
[HTC EVO 3D] PhatWebah:
I admit that I am slow, but I try :)

Ramjet, I have been trying to figure this out for hours now and I'm sure it is something stupid, but I cannot figure out why fastboot gives me this error when trying to lock:

I tried flashing the lock .zip from this thread and I get this error:

Lastly, I tried to just run the RUU anyway thinking maybe I was locked, but it wasn't showing "RELOCKED" because I have HBoot 1.04. It stalls while trying to reboot into the bootloader and I get this error:

But I know the connection is fine. I am at a loss. Do I need to upgrade the HBoot first? If so, to what? 1.50? 1.57? 1.58? Would you recommend just flashing the unofficial from this thread and worry about firmware later?

I'll reiterate my current configuration:

ROM: Harmonia

Baseband: 1.06.00.0426

PRI: 1.53_145

PRL: 60690

HBoot 1.04.2000 (PG8610000): SHOOTER XC ENG S-OFF RL

Recovery: 4EXT Touch v1.0.0.5 RC8

What I want is the newest stock ICS ROM with the recommended FIRMWARE/HBOOT/RADIO/RECOVERY and MiRaGe's kernel. I would like to be rooted and I would like to avoid having to do the wire trick again (it took me forever cuz I'm a tard). I don't really care about S-OFF or S-ON unless it benefits me somehow. Any help would be greatly appreciated.

PhatWebah
[HTC EVO 3D] ramjet73:
You don't need to lock the bootloader when S-OFF to run the RUU so don't worry about that.

As far as your 171 error goes, I recommend running the RUU with the phone in "fastboot usb" mode and it's always a good idea to issue the "fastboot devices" command to make sure the phone is found before flashing the RUU.

Another thing that can cause a "171" error is an intermittent USB cable so if you have another one it might be a good idea to try that.

The RUU will hang sometimes after flashing the stock hboot when a custom hboot like ENG 1.04 is installed. If that happens, just cancel the RUU app through task manger and restart it without touching the phone and it will usually complete on the second attempt.

ramjet73
[HTC EVO 3D] PhatWebah:
You are the best, You!

Thank You for all your help.
[HTC EVO 3D] mrg666:
FYI, I have tested the MiRaGe kernel today with S-OFF JBear HBOOT 1.57 and there were no problems.
[HTC EVO 3D] pbailey212:
Re: [KERNEL] MiRaGe - for HTC stock ICS ROM - 3.0.70

Did you finally s-off your phone?
[HTC EVO 3D] mrg666:
Yes, finally. Nandroid restores with 4ext recovery were taking too much time. Smart flash feature of 4ext never worked for me. With every nandroid restore, I had to fix the bootloop by flashing the boot image separately in fastboot.
[HTC EVO 3D] bigwillyg:
Re: [KERNEL] MiRaGe - for HTC stock ICS ROM - 3.0.70

Lol. Once you're s-off you will wonder how you got on without it.
[HTC EVO 3D] hossman:
Re: [KERNEL] MiRaGe - for HTC stock ICS ROM - 3.0.70

I just flashed blurom......your kernel works perfect with it as well
[HTC EVO 3D] 33hfl:
working perfect

FYI

flashed your kernel and it is working beautiful

ROM-- Tribs_SolidROM_Sense3.6_StockGUI_ver3.9

HBOOT--- 1.58

S-OFF (juopunubear)

Recovery--- 4EXT

Installed last Sprint OTA ( see Ramjet73 thread) not full ota installation

Thanks for your hard work
[HTC EVO 3D] mrg666:
Re: [KERNEL] MiRaGe - for HTC stock ICS ROM - 3.0.70

You're right. S-off is so much more convenient. Still so many other users don't go beyond a simple root which is sufficient for just a kernel upgrade. Delaying s-off was an opportunity to test the kernel.
[HTC EVO 3D] mrg666:
I have synced with Linux 3.0.71 and additionally backported several mach-msm/cpuidle, mach-msm/pm updates from codeaurora msm-3.4. The new build is in OP. Enjoy!
[HTC EVO 3D] bigsupersquid:
this is the most recent reference I've seen to a mirage build.

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

I noticed that the kernels for dastin's cm11 and liquidsmooth both use mirage as a base too.
[HTC EVO 3D] pbailey212:
Re: [KERNEL] MiRaGe - for HTC stock ICS ROM - 3.0.71 - 03282013

You almost made it a week :D I'm downloading now. Just don't tell my wife, I'm supposed to be packing.

Edit: right as I hit submit my wife called and added more things to my "honey do" list. I think she is spying on me.
[HTC EVO 3D] mrg666:
You are funny. I am also doing kernel development here instead of other things waiting to be done and some of them, similarly, on the "honey do" list.

This weekend will be busy. You know what I mean ;)
[HTC EVO 3D] bigwillyg:
Re: [KERNEL] MiRaGe - for HTC stock ICS ROM - 3.0.71 - 03282013

Question for you mrg666. How complicated is it to enable sysfs support for the scroff_freq variable? My kernel allows you to set the max screen off CPU freq via cmdline options in aroma but it cannot be changed through an app like kernel tuner because it appears to not have that sysfs support.