yashsingh1/xdaforums huggingface dataset:
[HTC EVO 3D] D3ViLWithiN:
Since we are digressing i would like to f**k around too please.

It reads to me as below ...

My phone used to have a rebooting problem.

I tried your kernel and it reboots even more now.

It might be roms fault, it might only be me. But i would like to continue implying your kernel needs more work.

Well yes, it might be fixed but then it happened again while i was deeply immersed racing my rice and i could not get back to it soon enough. You know where i am going with this? Mrg666, your kernel needs more work!

Oh and you might ask for those silly logs. You know what? Lol there ain't none.

At which point the rom developer being the gentlemen he is, comes in. Points out imperfection towards the rom, respects kernel developer and leaves thinking the smartbehind would pick the cue and will live happily everafter.

Our chum comes back saying listen up folks. There's only one kernel in the world and one rom to check it with. You guys go back and fix your stuff so i could play my racing game alright. Get it?

Oh and HTC don't know their stuff too. I will go program some dna's now while y'all get your game right.

.... What is this world coming to :(
[HTC EVO 3D] mrg666:
I had just wanted to make the latest improvements available to the shooter users but it seems it is better to leave it as it is. I have deleted all of the earlier test builds and left only the latest 01112014 build available for download. It should be stable but I don't have the device and no useful feedback are coming in. So there is no point of further discussion here. It is stable or not will be left as test kernel and I will not do any additional work on the shooteru kernel anymore. Stable builds are still available in the OP, they are very well tested and proven. If you have any problems go back to the stable build.

Thanks all.
[HTC EVO 3D] Dixxhead:
Aye, thanks for all the effort.
[HTC EVO 3D] D3ViLWithiN:
[MENTION=4203114]mrg666[/MENTION]

Wait, you cant do that to me. I am going to be guilty for the rest of my life.

That came right after my post which i am just praying silently that you didnt read wrong.

It was supposed be an ironic mirror to the random guy having reboots ever so softly that he couldn't figure even when both kernel and rom devs advised.

I promise you, i just clean flashed the latest miui4.1.10. And put your sweet fixed tool chain kernel on that i grabbed the other night. And i am going to log the f*ck out of it if it tried to do anything that was not asked.

I am going to request you to reconsider because the whole community shouldn't suffer for one undersmart guy.

Please accept my clean flash jb testing apology on behalf of any or everything that offended you. I tried compensating my best :(
[HTC EVO 3D] mrg666:
No worries, you were just about to start a flame war but calmness prevailed thankfully :)
[HTC EVO 3D] D3ViLWithiN:
I am not sure if you'd like this. But I used the fixed tool chain kernel for about 36 hours and it did not give me any reboots at all. I had to uninstall only because tun.ko told me it could not find any tun modules for 4.2.2 for some reason. Great job as always!
[HTC EVO 3D] mrg666:
Thanks for confirmation, gcc problem has been resolved earlier after going back to the stable toolchain.The fixed test builds are now in the op.
[HTC EVO 3D] Dixxhead:
GCC change was from 11012014 to 13012014 or u made some more changes? Either way, running the latter since 14. and not a single reboot. Thanks :)
[HTC EVO 3D] mrg666:
gcc change was in 01112014 build. The next build, 01132014, has an additional change that improves the hotplug algorithm.
[HTC EVO 3D] thejacko:
download links doesn't work
[HTC EVO 3D] mrg666:
Links in the OP seem to be working to me. Which link is not working?
[HTC EVO 3D] TheBootloader:
You're talking about the same problem with GCC 4.8 like months ago, right?

Because I saw this on the kernel mailing list:

First post of thread: https://lkml.org/lkml/2014/1/17/218

"(Should) work with GCC 4.7": https://lkml.org/lkml/2014/1/17/395

*Perhaps* with a *slim chance* this *could* be a related problem?

I honestly don't know, but maybe it's worth to keep an eye on it. :)
[HTC EVO 3D] mrg666:
Interesting! Our problem here is most probably a similar misoptimization of bad code. But it is too late for me to debug the kernel to find where the problem is since I don't have an EVO3D anymore :(
[HTC EVO 3D] mrg666:
I have uploaded the 884 build. Please tell me camera works now :)

BTW, please also test headset, microphone, and speaker too.
[HTC EVO 3D] howpathetic:
I will test it when I get home :)
[HTC EVO 3D] mrg666:
build 888 is posted in the OP. All of the reported problems are fixed. I will keep the kernel under testing for several more days. Please test and report any additional problems.

Thanks to howpathetic for the great help with testing.
[HTC EVO 3D] LoKKeR:
What features have this kernel, i mean what offers?
[HTC EVO 3D] mrg666:
There is a link to the original EVO 3D CDMA thread in the OP. This is exactly the same kernel for GSM version. I will update the OP after testing is complete.
[HTC EVO 3D] mrg666:
There seems to be no other problems and I have updated the OP with the full post. The last test version (888) is now available as stable build.

Enjoy!
[HTC EVO 3D] :
Yeah. Pretty stable so far...

Battery life is OK. 6% in 5 hours

BTW: Check post #3 lol
[HTC EVO 3D] mrg666:
Thank you for the mirror. But please remove the test versions earlier than 888 since they have known problems that are fixed later. The stable version is same with test 888. I would remove that too.
[HTC EVO 3D] Z O X:
Hello!

Thank you for your effort.

It's working nice on Non-Sense 4.0.3.

In fact, it's the quickest kernel to enable wifi and connects fastest.

Is there any way to enable swipe2wake?

Tried th script and kernel tuner but it doesn't work ...

Thanx!
[HTC EVO 3D] mrg666:
Thanks for the feedback and appreciation. You have no need for kernel tuner with MiRaGe kernel since there is no need to tweak or tune this kernel. The wifi driver is also updated that is why it is working better than the stock kernel. I remember how problematic it was in the stock kernel.

As I wrote in the OP, I am very conservative in adding features to the kernel since i want to keep it small. Sweep2wake, force-fastcharge and other variety of governors. schedulers, etc. are not added for this reason. Let's keep MiRaGe kernel this way. This doesn't mean that I haven't done anything with this kernel. You can check my repo and you will see that there are nearly 1900 commits in the last several months. All of those commits were done to optimize and update.
[HTC EVO 3D] Snoob25:
very smooth! i always followed your cdma thread and i'm glad you published a gsm version! now i'll see how it goes with battery :D
[HTC EVO 3D] :
In fact, i hate all this stuff as well...AN DI HOPE you will not integrate this nonsense and useless stuff!

thanks fpor your work!
[HTC EVO 3D] XDA-Dev.:
Tried to flash it over Sensai !

A CRASH :(
[HTC EVO 3D] oMaRcO:
Very smooth, thanks you for this great job.

Sent from my HTC EVO 3D gsm
[HTC EVO 3D] mrg666:
I just checked and it seems that Sensai is a highly customized ROM ported from Ville C2. MiRaGe is for the stock ICS ROM and there will probably be problems with other ROMs. Having said that, MiRaGe usually works with the stock-based ROMs just fine but Sensai seems to be totally different.

Thanks for testing anyway.

_______

On a different note, everyone, please be kind to each other. :angel: You can leave the difficult questions to me. I can handle ... hopefully :p
[HTC EVO 3D] mrg666:
Smooth and good battery life always go together. If the user experience is not smooth, it means that hardware is struggling and battery will be wasted. Check the CPU stats after 1-2 days use with Nofrills. The CPU should be resting at the minimum frequency ~80% of the time with MiRaGe kernel. Do the same with the stock kernel and you will see that system is kept at higher frequencies most of the time. Here is what I have after a day of heavy use (otherwise I usually get >85% at minimum frequency)

With MiRaGe kernel at 1.728 GHz, I get better battery life than the stock kernel at 1.18 GHz. 1.5 GHz should be even better but I can't stop myself from overclocking to 1.7 since my phone can handle 1.7 completely stable.
[HTC EVO 3D] orb3000:
On topic

Please keep it up with respect, no need to be rude.

Think before posting!
[HTC EVO 3D] milestone97:
Could you recommend any Senseless ROM?
[HTC EVO 3D] mrg666:
I haven't tried any senseless rom for GSM. I use the following Sense 5 skin with the stock ROM that makes GUI more like AOSP.

http://xdaforums.com/showpost.php?p=39384673&postcount=298
[HTC EVO 3D] :
Install a launcher like nova launcher and you have a ics ROM :P I think its all about the launcher...

And google for "3.6 Sense ICS" ... it's a ICS theme for sense 3.6
[HTC EVO 3D] mrg666:
That's right. I use holo launcher HD as an other alternative. I had bought it some time ago and it stayed on my phone since then.

Your search suggestion leads to the Sade skin. The sense5 skin i have linked in my earlier post is a beta skin posted in the same thread by the same developer. I am curious if you mean another skin since I would like to try it.
[HTC EVO 3D] mrg666:
By using the following apps I have have almost eliminated sense on my phone with stock ICS ROM.

- Holo Launcher HD

- Power Toggles

- SRS Audio Effects

- Sense 5 skin

- EX Dialer

- Chrome browser with user-agent mod in /data/local/chrome-command-line

- Google Play Music

- Google Calendar

- Google keyboard

- Cyanogenmod calculator

- Clock JB+

- 4ext updater

Regarding sound enhancement with SRS Audio Effects, just freeze Music and Music Enhancer in /system/app (I use link2sd for this). And flash the file "srs_mod_for_nxt.zip" in the above link via recovery. Sound settings will appear in settings/Equalizer of Google Play Music with the same interface you can find in JB roms. I am not a sound expert but the difference in sound quality is like night and day with the SRS enhancer installed. It is also a very small package.

If you want Chrome work just like the stock browser, copy the file I linked above to /data/local/chrome-command-line. Chrome had problems with some websites not giving the mobile web page and it was resolved with this mod.

It looks like following
[HTC EVO 3D] :
Just cheded it and it seems that the skin's link is offline.
[HTC EVO 3D] sdeft:
Hi mrg666

Many thanks for the gsm kernel.

I am trying to build from git but I am getting the following errors

LD arch/arm/boot/compressed/vmlinux

/home/builds/android/android-toolchain-eabi/bin/arm-eabi-ld: error: arch/arm/boot/compressed/piggy.gzip.o: unknown CPU architecture

/home/builds/android/android-toolchain-eabi/bin/arm-eabi-ld: error: arch/arm/boot/compressed/lib1funcs.o: unknown CPU architecture

I am using the linaro android-toolchain-eabi-4.7-2013.07-x86.tar.bz2.

Do you know the reason ? I can build all other GSM kernels fine with same toolchain.
[HTC EVO 3D] helicopter88:
You're using a x86 toolchain,you need one for ARM
[HTC EVO 3D] sdeft:
are you sure ? I successfully build other kernels with the same settings and

they all work.

in my build script I am exporting as below

export ARCH=arm
[HTC EVO 3D] helicopter88:
Tool chain has x86 in its name

Inviato dal mio Evo 3D GSM usando Tapatalk 4
[HTC EVO 3D] sdeft:
Yes cause I am building on an Arch Linux X86 server.

Which is the correct toolchain to use then ?
[HTC EVO 3D] helicopter88:
yep, but usually tool chain contains the name of the arch you're cross compiling to

I use usually arm-eabi or arm-linux-gbueabi for kernels, or let Aosp inline kernel building handle it

Inviato dal mio Evo 3D GSM usando Tapatalk 4
[HTC EVO 3D] mrg666:
Like helicopter said you need an ARM toolchain for cross compiling, i.e. using an X86 computer to generate ARM binary. I use linaro tool chain for cross compiling like many other since they specifically make tool chains that produce optimized code for ARM architecture.

You can get it from linaro binary page. The linaro-12.03-gcc-4.6 toolchain is very stable/reliable and I recommend starting your development with this toolchain. After you successfully build and test the kernel, you can switch to later versions. You can also build the toolchain if you download the source code from linaro. Cristpoher83 distributes some binary packages just doing that and I use his 4.7.4 package. It is also very reliable. Don't use 4.8 packages, they are experimental and don't build reliable kernels for me yet.

You will untar the linaro package in a certain directory and you can modify the following build command according to your configuration

make ARCH=arm CROSS_COMPILE=~/android/android-toolchain-eabi_46/bin/arm-linux-gnueabi- modules -j6

Replace j6 above according to the number of cpus you have on your computer.

Also set CROSS_COMPILE based on the directory you have expanded the toolchain package in your home directory.

The configuration file for shooteru is arch/arm/configs/shooter_u_config in my repo. Copy that file as .config in the root of kernel source before starting the kernel build process with the above command

The flash package is easy. Just use what I distribute as a template and replace zImage and modules inside the package with your build.

Since you are experienced already with kernel building the rest is as usual.
[HTC EVO 3D] helicopter88:
Just use make shooter_u_config (you may need ARCH=arm,on my server it's set in env)
[HTC EVO 3D] mrg666:
You can do that too. But I sometimes I edit .config file before compiling and I don't want to edit the master configuration file.

Just to clarify, the configuration file in my repo is shooter_u_config not shooter_u_defconfig, in case sdeft gets confused. Since it is not the same stock configuration anymore I used a slightly different name.

ARCH=arm is in the command line in my post. Thanks!

Edit: Everyone, I just added the quick build instructions to the post after the OP. Go build the kernel, it is so much fun. Fork my repo and modify as you wish, it is much more fun. :highfive:
[HTC EVO 3D] sdeft:
Thank you both for your help and suggestions.

After your suggestions I tried building this kernel with the following toolchains:

1. Cristpoher83 but they were failing. This was because they are only for 64-bit distros. So I installed Arch Linux 64-bit on my VMware and now the kernel builds fine. I used the arm-cortex_a8-linux-gnueabi-linaro_4.7.4-2013.07-build_2013_07_12.tar.bz2

2. Using the Linaro 4.6 & 4.7 arm ones but also failing. This was now because they were 32-bit!. So I installed the lib32-gcc-libs lib32-zlib packages and kernel builds fine. I used the both the gcc-linaro-arm-linux-gnueabi-2012.03-20120326_linux.tar.bz2 and gcc-linaro-arm-linux-gnueabihf-4.7-2013.04-20130415_linux.tar.bz2

Which is the preferred way of building the kernel ?

Also just to understand this better how did I have other working kernels when I was using the x86 toolchain ?

One other thing that I noticed mrg when building this kernel is that I get the following warnings but as I said it builds fine now.

WARNING: drivers/net/wireless/bcmdhd/bcmdhd: 'bcmsdh_probe' exported twice. Previous export was in drivers/net/wireless/bcm4329/bcm4329.ko

WARNING: drivers/net/wireless/bcmdhd/bcmdhd: 'bcmsdh_remove' exported twice. Previous export was in drivers/net/wireless/bcm4329/bcm4329.ko
[HTC EVO 3D] mrg666:
Congratulations on your build.

By x86 toolchain, I think you mean the default toolchain distributed by google with AOSP, like the one found in prebuilt/linux-x86/toolchain/arm-eabi-4.4.3 for CM source. It is a cross-compiler too, just like Linaro toolchain. The default toolchain is for building ARM binary of AOSP code and runs on x86 (and x86-64) systems. You can still build the kernel with that toolchain. But Linaro produces better optimized binary of the kernel code for ARM.

It doesn't matter if you build the kernel whether on an x86 or x86-64 system as long as you have the suitable toolchain for each system. But compiling in an x86-64 system is preferable since it builds faster with access to larger amount of memory, provided that the workstation has more than 4GB physical RAM.

The warning above is okay, happens due to building two modules for the same hardware. They will never be loaded simultaneously and doubly exported symbols will never be a problem. Each ROM loads either bcm4329 or bcmdhd. You can just disable the one you don't need in the configuration file to eliminate that harmless warning.
[HTC EVO 3D] sdeft:
mrg I noticed that in your kernel you can not wake up the phone by customized camera button via shooteru-keypad.kl file. Does this work on the CDMA version ?

Also would it be possible to integrate sweep2wake in the kernel so that one can enable it via the defconfig if wishes so (I know you don't like it!). I tried to do it myself but it looks a bit complicated!
[HTC EVO 3D] mrg666:
I never tried assigning camera button for wake up. I use button power button for that :) But I don't see a reason why it wouldn't work. Let me double check.

I don't want sweep2wake in MiRaGe kernel. But since you are already building the kernel, it is very easy, you can do this in a matter of minutes by yourself if you check the other repositories. You can also make it available for others to use if you want. The whole point of build instructions in the second post is about this actually. You can do it. GO!

Edit : the s2w commit at johnnyslt's repo is below

https://github.com/johnnyslt/androi...mmit/01f6a15c0576eda41d0ef49e87150b087f297f33
[HTC EVO 3D] mrg666:
An update is available in the OP. There is nothing new, just updates accumulated in the last two weeks. You can check the list of commits in my repo linked in the OP.
[HTC EVO 3D] TheBootloader:
Hey mrg666!

Thanks for porting this kernel for GSM! :)

Right now I use Ryrzys Kernel which doesn't seem as optimized as your kernel, so I wanted to change to your kernel, but theres this one feature I miss:

https://github.com/ryrzy/shooter_u_ics_kernel_3.0.xx/commit/016f9b557cbb72f11f3a96e5b010e5869c2f65fa

It lowers the minimum brightness of the screen, which makes it a lot easier for the eyes to read at night. (It also seems to lower the general voltage for the screen, using less battery.)

Is it possible for you to include it in the next update?

Thanks a lot! :D
[HTC EVO 3D] mrg666:
This is a good one! I have always planned to do this but it always slipped under the other things. Thanks for reminding this. I have just did that and here is a test kernel for your testing. Please let me know if it is working as expected. I only didn't lower the max brightness because it is sometimes useful for using the phone under bright sun.

http://www.mediafire.com/download/kow91a43h10a8lw/MiRaGe_shooter_u_test_kernel_901.zip
[HTC EVO 3D] Z O X:
Autobrightness does not lower screen brightness to

minimum even in no-light condition.

Is there a way to offset or it needs kernel tweak?

Otherwise, all is good ;)
[HTC EVO 3D] mrg666:
I am sure there is a setting in the kernel for that. But I wouldn't really play with it since the auto brightness settings are like a peace agreement that nobody is really happy about it for different reasons. Other users will probably object to my favorite settings. When auto brightness is not satisfactory, I use the manual settings via Power Toggles. The ideal solution could be some sysfs parameters to tune the autobrightness. I will look into that.
[HTC EVO 3D] TheBootloader:
No problem! I just tested the lower brightness and it works as expected. Thank you very much! :D

And also thanks to you for your small kernel guide, I just built a kernel for the first time and it immediately works! :)

//edit:

Wow, so far this kernel is just awesome!

Loading times (boot and especially apps) are a lot better, more responsive / less lag, free RAM after boot (before ~320 MB, now ~415 MB)...

//edit2:

Aww.. Unfortunately I have some WiFi problems now. ;)

[Kernel] + [Power source] = [WiFi behaviour]
Ryrzy + battery = Apps and WiFi stay connected, rarely re-connect, slow pings + slight packet loss (due to powersaving i guess)
Ryrzy + charger = Apps and WiFi stay connected, immediately ping answers, no loss, full performance
Mirage + battery = Apps and WiFi disconnect when screen is off, no reconnect
Mirage + charger = Apps and WiFi disconnect when screen is off, no reconnect

So, 2 problems:

(1) Why doesnt Mirage + charger go into this "full performance mode" like Ryrzys kernel did?

(2) Why can't Mirage handle WiFi if the screen is off?

My focus is on (2). I had the phone on charger with WiFi on and that "Never disconnect" option enabled. But still it disconnects completely from WiFi after a short time (max. 20 minutes) and thats it, no reconnect or anything. Only when I push the power button to wake the phone up, then it connects again. In Ryrzys kernel that works without any problem.

Maybe it's related to this, but I never got any answer:

http://xdaforums.com/showpost.php?p=40781196&postcount=1102 (Only "edit2" is relevant)
[HTC EVO 3D] mrg666:
Thanks for the comments and testing. I wouldn't touch WiFi again since there are no significant problems with my use or other users. I hope you can fix it on your end.
[HTC EVO 3D] TheBootloader:
(I compared WiFi-related commits between Ryrzy, Mirage and ButteredToast, but I'm still not entirely sure which one caused this weird behaviour for me. Looks like for your kernel it was the change "bcm4329 drivers from codeaurora.org-msm-3.0" and for ButteredToast the completely different "WIFI: BCM4329_248: allow SYSFS control over PM=FAST/PM=MAX". All other commits just don't match the date and time, but I probably just forgot something else. :silly:)

Whatever caused this, I solved it by just reverting all WiFi-related Mirage commits, and applying Ryrzys WiFi commits instead.

Then some makefile-magic, recompile, reflash and yay it works. :D

If anybody has a similar problem and can't compile the kernel by himself, just send me a message. ;)
[HTC EVO 3D] mrg666:
So, you have essentially reverted the WiFi to older version and reverted the updates. If that is what works for you, it is totally fine, the purpose of the build instructions was this after all. As I said, there are no WiFi problems I see or receive.

Please don't build your binaries with the same name and distribute here. I would recommend you to start an alternative thread with a different build name if you want. Otherwise the problem reports will be too confusing for everyone.
[HTC EVO 3D] TheBootloader:
Exactly, dont know why but it simply works for me.

That was more an informative post, maybe somebody out there has a similar problem and finds this thread with Google. ;)

Hehe don't worry, I definitely won't post anything public with your name on it.

I simply meant that, if there is anybody who has this specific similar problem and they don't know how to build "my" specific "oldwifi-version" themselves, then I can either help them build or provide them with binaries via private message. As you said it seems to work for everyone else, so I highly doubt that there will be masses of requests (if any at all), and it shouldn't really be a problem or need its own thread.
[HTC EVO 3D] mrg666:
Why don't you get a github account, fork my repo, and commit your changes there? It would be the best you could do to help others and, who knows, you might get serious, start merging many other changes and updates later. That is how Android development projects start. Do it!
[HTC EVO 3D] invince2:
Can you add lionheart governer please :)
[HTC EVO 3D] mrg666:
Interactive is working great. Let's avoid bloating the kernel with alternatives.
[HTC EVO 3D] invince2:
Just that one :P