yashsingh1/xdaforums huggingface dataset:
[Motorola Atrix HD] davemani5:
I suppose I'm still a bit lost/confused. I understand the process to return to stock Br0adband outlined but I cant currently boot into ANY OS. I was able to boot into Cyanogenmod 10 but after installing an incorrect kernel (see earlier post) it either freezes at the cyanogenmod loading screen or just keeps rebooting.

I couldnt find a similar kernel for CM 10.1 for my device (which I'm guessing will solve my problem but who knows). Closest I saw was the github cyanogenmod android kernel page for my device but I dont know how to build it into a zip. I think this may also be a red herring.

I've tried re-installing CM 10.1 and doing a factory reset from CWM but so far nothing i've done has seemed to work. Oh I also tried to restore a backup image but no luck :(.

I'd happily welcome any advice (like is finding a kernel for CM 10.1 the right thing to do to fix this?)
[Motorola Atrix HD] deeje00:
You have to just flash the stock firmware through rsd man. Stock kernel Is included.

Sent from my PACMAN MATRIX HD MAXX
[Motorola Atrix HD] davemani5:
Thank you. I got a bit confused with all the CWM installs and everything. I will go through the guide at http://xdaforums.com/showthread.php?t=2231249 .

Quick question though, will this still keep my phone bootloader unlocked, keep CWM and keep rooted? Or will this reset all that? I just would hate to redo everything :(
[Motorola Atrix HD] deeje00:
Your bootloader will remain unlocked so all you'll have to do is put cwm back on the flash a rooted rom or a superuser.zip for the stock rom.

Sent from my PACMAN MATRIX HD MAXX
[Motorola Atrix HD] SoftSynth:
I just went through the same thing with the carrier problem after CM 10.2 (without the kernel issue) on my Atrix HD, and a clean stock RSD Lite flash as referenced by the guide above corrected it quite nicely.
[Kindle Fire Q&A, Help & Troubleshooting] BupycNet:
This is dont work on CM 10.2

Operation not supported on transport endpoint. I need trim for faster performance. Disk is work slowly.

idias?
[Sprint Samsung Galaxy S III] escalavee:
I want to switch from Sprint to Net 10. I rooted using Odin, but I can't find anything telling me if I need to flash recovery to unlock it or if just achieving root is enough. I have looked everywhere! Thanks.
[Android Q&A, Help & Troubleshooting] Thelgow:
Hey guys, random question here,

I have the softtoken app for Squaresoft's Final Fantasy XIV.

Initially I was looking to set this up on multiple devices like my Galaxy S1, Kindle Fire and Bluestacks on the PC.

No problem with the blizzard authenticator.

For the Square app, when you launch it, it's as if fresh install, doesn't load up my key.

I also had a problem on my phone stuck in recovery boot loop.

I backed up the whole nand, restored an old nand, it came up, restored the new nand, and that booted again.

The square app worked off the nand restore.

Any idea what Titanium may be missing or what I can pull out for a "full" backup?
[LG Optimus L9 P760, P765, P768, P769] donk165:
Hi guys, can you post your favourite MIUI themes to share with everyone.

I like 'bluejaku v5' and 'BlueV5'. I'm looking for a holo style if there is one.

(Links soon :P)
[LG Optimus L9 P760, P765, P768, P769] kuba725:
You said you are looking for some holo theme. Here is "HoloV5" catch link : http://en.miui.com/thread-2850-1-1.html
[LG Optimus L9 P760, P765, P768, P769] artit:
GrayG.V5 and Black_V5 is nice for dark theme.
[LG Optimus L9 P760, P765, P768, P769] iqbal Khan:
is it work on lg p765 ? help me bro
[LG Optimus L9 P760, P765, P768, P769] Giancop92:
best theme is ios 7 v1.2
[Verizon Samsung Galaxy S III] lieffring:
If anyone has it I would appreciate it I want to try a few kernels for battery life.

Thanks .
[Verizon Samsung Galaxy S III] Ibonic:
I'll post the link in a second. You can always download a ROM with an Aroma installer and pull the zip directly from the ROM itself.
[Nexus 4 Original Android Development] hasanandnexus:
Woww greatt, thanks mirage
[Nexus 4 Original Android Development] Maelstr0m:
many thanks Mirage!

Does JSS come with caf video driver or it can be flashed on non-cm roms without problems?

Inviato dal mio Nexus 4 con Tapatalk
[Nexus 4 Original Android Development] alen1901:
Good to see new kernel which goal is simplicity, not many of them are here. ;) ill try it when clean instal comes to repertoar. just one question, you didnt mention -O3 and gcc 4.8.2, so i asume you didnt use them? Thanks. :)

Poslano sa mog Nexus 4 koristeći Tapatalk
[Nexus 4 Original Android Development] mrg666:
I haven't updated the video driver from CAF ... yet. I will do after the 4.4 update if Google hasn't done yet.

Kernel is compiled with gcc 4.7.4 using -O2 optimization. gcc 4.8 was not giving me reliable builds yet. I will switch when 4.8 becomes stable. I have tried O3 optimization in the past and I didn't see any benefit of it. Plus, O3 optimization caused reliability issues especially with the latest gcc compilers.

MiRaGe should be compatible all AOSP-based ROMs, as long as the same user-space libraries are used with the stock 4.3 ROM. I can't claim universal compatibility since even stock JSS and JWR builds need different kernels.
[Nexus 4 Original Android Development] C.T.Richter:
Would you consider making a ZIP?

I found your kernel to be quite interesting, but I don't really like flashing via IMG file.
[Nexus 4 Original Android Development] ak:
you can download one of 1000 kernels around here and replace the kernel.img ... and wholà you have a zip version.
[Nexus 4 Original Android Development] playya:
Can't agree with you more but the problem with so many people on xda is that they rarely even open up a zip file to see how it operates. Guarantee most of the people will shy away simply because of the lack of a zip. Again I agree its not that hard to do but lets be honest here most have problems searching so taking a boot.img and putting it in a zip probably aint happening :D
[Nexus 4 Original Android Development] mrg666:
I have just uploaded the alternative flashable zip files. I will remove the image files since they are in the zip files now.
[Nexus 4 Original Android Development] QUIETLYloud:
Just flashed on slim and lost root... Just a heads up
[Nexus 4 Original Android Development] mrg666:
LOL that's right!
[Nexus 4 Original Android Development] mrg666:
That can't happen due to flashing the zip files in the OP since there is nothing in the zip file that touches /system, it is not even mounted.
[Nexus 4 Original Android Development] DontPushButtons:
Gonna give it a go on Vanir. I'll report back of my root gets effected. Happened a lot with 4.3 when it first came out
[Nexus 4 Original Android Development] mrg666:
I am using CWM 6.0.4.4. It is constantly suggesting to restore my root although it is not lost. If this is what is mentioned here, just ignore it; root is not lost. SuperSU, su keep working. Actually, I am losing my patience with CWMT lately. Maybe it is time to switch to TWRP.
[Nexus 4 Original Android Development] DontPushButtons:
I'd say it's long overdue to switch to twrp lol. Ever since I switched to twrp back on my rezound, I have NEVER looked back to cwm. Not to say cwm isnt/wasn't great.. But you know how it is lol.
[Nexus 4 Original Android Development] mrg666:
I just don't like the "overdesigned" interface of TWRP. It is too fancy for my taste. But as long as it works when needed, it would be fine with me. I don't boot into recovery so frequently anyway since I flash the kernel in fastboot or Flash Image GUI.
[Nexus 4 Original Android Development] C.T.Richter:
Oddly enough, I lost root. I'm currently running the latest version of Paranoid Saberdroid.
[Nexus 4 Original Android Development] mrg666:
Is it just what the recovery says? I use the stock JWR ROM and root is preserved when I flash although CWMT falsely complains about it.

Edit: I just tested with TWRP as well. Root is still preserved.
[Nexus 4 Original Android Development] C.T.Richter:
Using TWRP there is no error message, it just says it was installed successfully.

I just tried it on a clean install, and the same thing happened.
[Nexus 4 Original Android Development] mrg666:
Maybe we could try sending flash drives to you with a pigeon :silly:

Everyone, I have uploaded the new stable builds in the OP. Tests didn't show any problems and PMEM removal is safe for stable builds.

- PMEM removed completely. Although PMEM wasn't used, it was still dangling around in the kernel, MiRaGe is pure ION now.

- msm_cpufreq updates from CAF: most importantly increased the WQ priority of msm_cpufreq.

- autosmp: increase wq priority and decrease hotplug load limit. This increases responsiveness for smoother user experience. The impact

on battery life should be minimal.

Enjoy!
[Nexus 4 Original Android Development] C4SCA:
Why not use amazon's drones? Haha

sent from my Nexus 4 tasting for the first time KitKat.
[Nexus 4 Original Android Development] tvall:
In the latest stable kernel, everything is feeling a little laggy. Some apps take a noticeable time to load. But I've only been using it for a few hours. Will report back again after a day or so of use.

And we don't have many pigeons here. Do you think pelicans would work?
[Nexus 4 Original Android Development] mrg666:
I haven't seen any lag. Actually, just the opposite, there is improvement in smoothness. Post a dmesg if you can.
[Nexus 4 Original Android Development] ihancioglu:
It is very good performance kernel,but needs some battery savings. It takes %6-7 on night without data,sync, etc.
[Nexus 4 Original Android Development] mrg666:
6-7% discharge overnight sounds reasonable/good to me. If you let WiFi turn off while sleep, it could be even lower. Can you post your battery use screenshot?
[Nexus 4 Original Android Development] ihancioglu:
Thanks for the answer , I don't want to compare , but %0-1 consumption on Semaphore with same configuration. Yes Wifi is turned off already while over the night.

Just let the device this night and will post screenshot tomorrow with latest version.

My night profile is Stock image, ART enabled , Data-Wifi-Sync-BT-GPS off, 2G network mode

Thanks.

---------- Post added at 11:46 PM ---------- Previous post was at 11:38 PM ----------

Also logcat is filled up with

E/PowerHAL( 633): touch_boost: failed to send: No such file or directory

What we can do for this messages?
[Nexus 4 Original Android Development] mrg666:
Please have a look at the battery stats and feel free to post it here. I can take a look at it to see if there is anything standing out.

Ignore the powerhal messages, they are harmless. This was discussed earlier in other threads for different kernels too. See here
[Nexus 4 Original Android Development] ihancioglu:
As far as I remember there were no power hal messages in previous versions. Is this related root? There are no root and busybox installed right now.
[Nexus 4 Original Android Development] Mercado_Negro:
Thanks for sharing your work with us, truly appreciated.

Just flashed this in SlimKat and it boots just fine though I lost root access. As many other ROMs, SlimKat uses Superuser. I've seen this before in at least one more kernel, franco.Kernel. According to Kufikugel, SlimKat developer, this is caused by the lack of SELinux compatibility on the kernel side. I've also tried franco.Kernel on stock, using Superuser and same thing happens. Only SuperSU solves this but SuperSU is much more flexible when it comes to rooting because it disables several SELinux features (not bad but defeats the whole purpose of having SELinux on Android now). I'll be flashing KOT49H factory images tomorrow to confirm this on your kernel using Superuser but maybe you can tell me more about this, if possible.
[Nexus 4 Original Android Development] mrg666:
MiRaGe has exactly the same SELinux configuration with the stock kernel; there is no difference regarding SELinux. When you flash MiRaGe, the install script only replaces the boot image, /system and /data are not even mounted or modified. So losing root can not be related to kernel. It must be related to something that Android configuration in Slimkat is doing. Maybe the init scripts or superuser are checking a preferred kernel and disabling some features when they find a different kernel. So I can't help with this problem since I don't use SlimKat.

Koush's supersu has created problems/incompatibilities for me on different devices and I have switched to SuperSU sometime ago. I have never looked back since then. IMHO, the most important security vulnerability in a device is the user and there is no way to fix it. So SuperSU with a careful user is as safe as anything else.

Thank you for the feedback. Please let us know if you find how SlimKat is disabling root with a different kernel. That is just strange.
[Nexus 4 Original Android Development] mrg666:
The hal messages were there since I disabled touch boost feature in the kernel two months ago. IMHO, touch boost is a totally absurd and adhoc way of improving the responsiveness of the kernel. Instead of working on the efficiency of the kernel and improving latency of the CPU governor, they just added another mechanism of frequency control - with strings. So it was eliminated in MiRaGe in the first step of clean up.
[Nexus 4 Original Android Development] tvall:
If the rom is using koush's superuser integrated, it likely has some modifications to init.rc and a /init.superuser.rc script to start the su daemon. Supersu and koush's flashable zip instead use /system/etc/install-recovery.sh for that task.

Since mrg's zips flash an entire boot image with a aosp based ramdisk, superuser's daemon doesn't start. Simple solution would be to use the install-recovery.sh script. Or you could extract his kernel from the boot.img and put it in your roms.

[MENTION=4203114]mrg666[/MENTION] I believe the lag I was having before has gone away. I tried to reproduce it but everything started behaving smoothly again. I love it when problems fix themselves.
[Nexus 4 Original Android Development] nithin1992:
I understand that you want to keep the kernel simple but do you have any plans on adding s2w in the near future? I wanna try and reduce the use of the power button. I'd totally understand if you chose not to, just wanted to put this request out.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Mercado_Negro:
Thank you very much for your replies. Indeed, it works on full stock (KOT49H) using Superuser so the problem must be exactly what you mentioned. Could you please elaborate on how to use the install-recovery.sh script? I tried flashing Superuser again in SlimKat and it didn't work either. I'd really appreciate your help.
[Nexus 4 Original Android Development] mrg666:
Insightful explanation. Thanks! I could prepare an any-kernel updater zip but I also modify the init scripts to eliminate some bloat such as mpdecision, thermald, touch boost ... Let me try to find if there is a way to add a couple of lines in the init scripts to check if the super-duper-most-complicated Superuser is there to satisfy its most sophisticated requirements.

Yay! I thought so. I can't believe the smoothness of my Nexus 4 sometimes. On top of that, Google gave us at least %50 performance boost with ART. It is like a new phone upgrade after switching to ART.
[Nexus 4 Original Android Development] tvall:
I haven't switched to ART yet. Read about issues with it when 4.4 was first released and decided to wait for bugfixes. Does it work better in 4.4.1?
[Nexus 4 Original Android Development] Mercado_Negro:
Indeed, that was a good explanation of the problem.

To be honest, at this point, it's just more curiosity than anything else. It was intriguing why flashing a kernel would break root on some ROMs, including SlimKat.

Having said that, I wonder why ROMs modify these files/paths and not simply use the script.

Anyways, thanks for looking into this, I'm glad I brought this up here and learned something :)
[Nexus 4 Original Android Development] mrg666:
It is now 4.4.2 actually. And ART is working without any problems with all of about 60 apps here including whatsapp. It is totally worth switching to.
[Nexus 4 Original Android Development] mrg666:
The kernel update packages below are using any kernel updater method, i.e. preserving the original ramdisk by injecting the zImage into the existing boot image. So, they should not break the root in SlimKat. I took the update scripts and binaries from mathkid95's zip package so thanks to mathkid95.

I have tested on my N4 with stock ROM and it works. Can you please try with SlimKat and let me know?

non_oc kernel: Non-OC kernel: http://www.mediafire.com/download/p0t20xudhgb580k/MiRaGe_mako_kernelup_KOT_121713.zip

overclocking kernel: http://www.mediafire.com/download/jsqci49je9yqi1a/MiRaGe_mako_oc_kernelup_KOT_121713.zip

PS: these are the same kernel as in the OP just rebuilt today.
[Nexus 4 Original Android Development] mrg666:
Your question went unanswered in between the other discussions. I am not a fan of such mods as s2w and fastcharge. So they will not be included in MiRaGe. But the source code is available in the repo and you can add those patches if you are able to build yourself. Let me know if you need a hand with building the kernel.
[Nexus 4 Original Android Development] Mercado_Negro:
Root Access is preserved now after flashing these two anykernel versions. For reference, this is what I did:

1) Restored a Nandroid I made last night before flashing your kernel,

2) Flashed the non-oc version in TWRP 2.6.3.3 and booted just fine, root access worked flawlessly,

3) Then restored again my Nandroid, flashed the oc version and booted fine as well, root access also worked flawlessly. This is the setup I'm using at the moment.

I've been monitoring cores with System Monitor and it's pretty interesting the behavior, seems really efficient and 1,6GHz is used only when it's *really* needed which makes it even more interesting. Another interesting fact is it seems to prefer to online all 4 cores instead of stepping up only a couple of them. If I may ask, why did you take this decision? Is it oriented to efficiency or something else? I've read onlining/offlining cores all the time use more resources and seeing that most of the time so 4 cores are hotplugged, I assume this is not a battery oriented approach.

Anyways, thank you very much for spending time on this, I'm glad there's someone else out there willing to develope his own kernel, we don't see that a lot.

Have a great day/night!
[Nexus 4 Original Android Development] mrg666:
Thanks for confirming that root is retained after flashing the any-kernel updater. This is also the confirmation of tvall's explanation. Thanks to him again.

It is really hard to assess how many times each core is turned on and off by just looking at system monitor app since it is not really applying much of a load to the system. MiRaGe is using a different hotplug driver, autosmp, I had developed. There is a debug and statistics part of the code that is disabled in the production version that I normally use for everyday. I have the debug feature turned on while testing the kernel and I see that approximately core-0 is 100%, core-1 40%, core-2 12%, core-3 is 5% online of the total time.

I have optimized autosmp to reduce its overhead on the system as much as I can. The workqueue code in MiRaGe is backported from Linux 3.7 so that the patches that enhanced the hotplug efficiency can be used. And the load calculation in autosmp is done inside the code to improve the efficiency; it doesn't rely on msm-rq-stats and reads the load average from sysfs. Also, the workqueue priorities of cpufreq and autosmp are increased to improve the responsiveness. I tried to find a balance between battery life and responsiveness of the kernel and I think that balance is okay in MiRaGe right now. In summary, autosmp is quick in hotplugging the cores and the kernel is optimized to reduce the penalty (overhead) of hotplug events to enhance both battery life and responsiveness. Please have a look at the repo and let me know if you have any questions,
[Nexus 4 Original Android Development] mrg666:
[MENTION=4647411]nithin1992[/MENTION]

After your PM, I have added the build instructions in the second post now (just a modified copy/paste from my shooter kernel thread). Have a look and feel free to post here if you have any questions.
[Nexus 4 Original Android Development] Mercado_Negro:
I was using the flying monitor from System Monitor which stays on top of all applications while browsing via Tapatalk, G+, texting in Hangouts, Whatsapp, Facebook messenger and BBM. Also played a game, Dead Trigger 2, and that's what I saw but I don't have numbers to back this up.

I guess a few days of using it will tell more, thanks again.

By the way, can we change the default vibration intensity (haptic feedback strength) using TricksterMod? I've always preferred this at 100 and not 70 as default.
[Nexus 4 Original Android Development] mrg666:
I am not sure, I have never used TricksterMod. You can give it a try but if you are looking for a "tweaker" kernel, I am sorry, MiRaGe is not that one.
[Nexus 4 Original Android Development] Mercado_Negro:
Yes, it works. Fixed_gain also works. These are the only two things I was interested in (these parameters are also available on the stock kernel, which makes sense). Thanks.
[Nexus 4 Original Android Development] Mercado_Negro:
I played Dead Trigger 2 today for an hour or so and when I quit the game, the device was very laggy for 5 minutes, more or less. It was really hot but that's not new, it's also the case when using any other kernel.

I'll flash the non-oc version now to see if it also happens there.
[Nexus 4 Original Android Development] jawz101:
[MENTION=4203114]mrg666[/MENTION]

this always gets me but I forget which Linaro download is the toolchain:

android-toolchain 4.8 android-toolchain-eabi-4.8-2013.11-x86.tar.bz2

linaro-toolchain-binaries 4.8 gcc-linaro-arm-linux-gnueabihf-4.8-2013.11_linux.tar.xz

but when I go into where any of these the path isn't quite like your example:

your example:

...<toolchain folder>/bin/arm-linux-gnueabi-

but these 2 downloads don't refer to gnueabi. rather androideabi- and gnueabihf- respectively.

...<android-toolchain4.8>/bin/arm-linux-androideabi-

...<linaro-toolchain-binaries4.8>/bin/arm-linux-gnueabihf-

ideas?
[Nexus 4 Original Android Development] mrg666:
It is linaro-toolchain-binaries-4.8 and select the link for Linux. It will be bin/arm-linux-gnueabihf- when untar the archive.
[Nexus 4 Original Android Development] jawz101:
Thanks. That's the one I was thinking. The "hf" at the end throws me off

---------- Post added at 07:37 AM ---------- Previous post was at 07:33 AM ----------

I just realized hf = hard float
[Nexus 4 Original Android Development] mrg666:
I have synced with the mainline Linux 3.4.y repo and merged the patches up to 3.4.74 in MiRaGe repo. This is not a trivial work since MiRaGe repo was not exactly at 3.4.0 level, many of the siginificant patches in the mainline Linux repo was already applied, many of the other patches had conflicts, and some of them were not even applicable.

So here is the MiRaGe test kernel and I would appreciate if you can try and let me know if there are any problems. After such a large departure from the stable code base, I will give this test build at least one week time until it is proven stable.

http://www.mediafire.com/download/0rsmpsgv3p7xprg/MiRaGe_mako_test_kernel_KOT_121813.zip

http://www.mediafire.com/download/cp6s1s8udcuttrs/MiRaGe_mako_oc_test_kernel_KOT_121813.zip
[Nexus 4 Original Android Development] jawz101:
have the new 4.4.2 binaries been incorporated?

I've had problems with OmniROM, Purity, Franco Kernel & mrg kernel since 4.4.2 rolled out and keeping a solid bluetooth connection to my car stereo. If it disconnects once I have to pair my phone again because my stereo won't connect again.
[Nexus 4 Original Android Development] mrg666:
If you mean the binaries in the ramdisk, yes, they are in the boot.img. It was done the day after Google released the 4.4.2 system image.