yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Android Development] alwayslookingforanswers:
Right on will do . Thanks for the advice. Give me a few hours to finish up this other stuff and I'll get back to ya and let you know how it went. I do know one thing. I went and purchased the Note 4 before this totally awesome device. Went traded it in for this and I'm so HAPPY!!! I'll never buy another Samsung device again. Really missed doing all this. And missed the XDA community! Everyone here has always been so helpful and giving. :good: thanks a million once again.
[Nexus 6 Android Development] st3wart:
Yea I tried the new blisspop and when I flashed Vindicator it bootlooped. No worries, I flashed Broken OS and works great!
[Nexus 6 Android Development] Xileforce:
This is very helpful. Narrows it down. Might be ramdisk related. So I guess for now if u want to use vindicator don't flash the latest bliss till we figure out what's causing it lol.
[Nexus 6 Android Development] jiv101:
Speaking of that I tried to flash code_blue and I also got a bootloop
[Nexus 6 Android Development] Xileforce:
Well then....I blame bliss lol. Makes me feel a little better lol. O guess we will have to wait and see what happens. Not really sure what it would be since AFAIK blue doesn't modify ramdisk. Must be something weird in bliss.
[Nexus 6 Android Development] brando56894:
Past with a few builds after 3/2 I was having bootloops where I would have to wipe everything and start over to get it to boot. I haven't flashed any new builds in a few days for that reason lol
[Nexus 6 Android Development] alwayslookingforanswers:
Got it to install with stock rooted ROM. Flashed thru TWarp. Running great so far. Thanks for everyone's advice.
[Nexus 6 Android Development] jackpollard:
I've been running it on Resurrection Remix and its been rock solid and battery life is as good as I've ever seen it. I've not noticed any performance issues at all and it sips battery. I had many issues with Bliss and Lean kernel, but never with RR and Lean or now Vindicator.

Let me add, Bliss was an excellent rom, had more features then I knew what to do with. No knock on it, just shareing my experience.
[Nexus 6 Android Development] Xileforce:
May have to give that ROM a shot. That ks for sharing!
[Nexus 6 Android Development] jackpollard:
Thanks for taking the time to respond, I never really thought through the details as you explained, it makes sense. I'm uv'ed 25mv as of now!
[Nexus 6 Android Development] Xileforce:
Awesome! Now you will sip even less power :)
[Nexus 6 Android Development] Mistertac:
Just to let everyone know I've been on the Bliss build from 3-5 without any issues, as well as Euphoria. Two great Roms you typically can't go wrong with although sorry to hear about the latest Bliss bootloop deal. Hopefully that gets figured out in the next build or two at the most.
[Nexus 6 Android Development] Doogie1:
I've been using this solid kernel on Euphoria (Currently) as well as Slimpop. Its been exceptional! Did notice really good/stable 4g, using it with Euphoria's current build. I'm on Verizon.. I haven't powered on my Note 4, since I started realizing how all these talented Devs supporting our device.. Have made the N6, THE only device to have. Thanks ??
[Nexus 6 Android Development] jiv101:
[quote name="franciscofranco" post=59296800]Can you link us the patch with the classpath changes? It would be helpful.[/QUOTE]<br />

<br />

I believe this is what he was referring to, hope it helps http://review.cyanogenmod.org/#/c/90736/<br/>

Talking about how CM commits have changed in lean kernel thread
[Nexus 6 Android Development] Xileforce:
Thanks! Just saw that. I thought that patch might have been the issue. However imoseyon said they are potentially going to implement the new savoca color control which would likely break everything again so I may wait with IMO to see what happens with that.
[Nexus 6 Android Development] jiv101:
What's 35mhz voltage suppose to be
[Nexus 6 Android Development] LunaticSerenade:
So, my signal issue came back. Being the type to never give up on what I want, I decided to do the following:

Reflash stock and factory reset

Flash Vinidcator 1.3

Not install Synapse

Flash the UKM zip you have (had?) on android file host

Flash Vindicator 1.4

On reboot, it had the signal issue again. So I typed *#*#4636#*#, and changed the network to LTE/GSM/CDMA (Auto PRL) from WCDMA Preferred.

Boom, issue fixed.

I'm using FauxControl to change kernel settings, and while it's not as robust as Synapse, it still works.

Sooner or later I'll give Synapse a shot again, and see what happens, but it seems like 1.4 is causing the radio to set to WCDMA Preferred, and for whatever reason Synapse was locking it in.

Hopefully anyone else having this issue can do this, and have service, because 1.4 is pretty sweet.

Note: I'm on Verizon, so your network needs may vary.
[Nexus 6 Android Development] Xileforce:
500mv. That's a bug with apps that happens sometimes
[Nexus 6 Android Development] jiv101:
This worked for me... Flash latest lean kernel, boot up phone, then flash 1.4 I'm up and running on latest blisspop with synapse working.

Edit.. Phone wasn't showing data but within 30sec. It registered
[Nexus 6 Android Development] Xileforce:
Awesome thanks for sharing. Seems like the issue may be related to the new version of synapse that comes with 1.4 then. I'm unsure of what else it would be.
[Nexus 6 Android Development] LunaticSerenade:
I'm inclined to agree.

I just reinstalled Synapse, and it immediately cut service, but I was able to use the Phone Information menu to fix it.

It's a really weird issue, but at least there is a fix that isn't 'REFLASH ALL THE THINGS!'
[Nexus 6 Android Development] Mistertac:
[emoji41]
[Nexus 6 Android Development] Xileforce:
Well played....well played indeed.

Edit: also if u find ur phone isn't using deep sleep that's because of an issue with the latest play services. Nothing related to kernel.
[Nexus 6 Android Development] Mistertac:
Oh it's definitely not from this kernel or any other. Google just wanted to make sure we were all paying attention that's all.
[Nexus 6 Android Development] jiv101:
Anybody have a link for the old Play service that doesn't keep my phone awake all day
[Nexus 6 Android Development] dannieloco:
find the old versions here Google Play Services APK
[Nexus 6 Android Development] Xileforce:
Thanks for sharing! Hopefully they will get an update soon to fix it.
[Nexus 6 Android Development] Xileforce:
Ok guys. Should have an update for you today, it will include all the new lean kernel fixes plus a bunch of other patches and maybe some other cool things too :). Will also be taking a look at 5.1 stuff today as well.
[Nexus 6 Android Development] USA-RedDragon:
Hmmmm. Looks good. Wonder what these new features might include? ;)
[Nexus 6 Android Development] Roland Deschain:
Awesome; can't wait!

Question for you - would it be possible to have an intermediate minimum clock speed added between 98.3MHz and 300MHz? Say, 200MHz-ish? I've stopped using 35.8MHz because I'm more of a "max performance with battery savings where possible" kind of guy and the wake time with 35.8MHz is a little slower than with 98.3MHz, so I'm using 98.3 right now. I'm wondering if I'd see a small difference or not between 98.3MHz and 300MHz. More of a curiosity, really.

I'm running wheatley right now with intelliplug and a hysteresis value of 3 with the performance intelliplug profile. I don't know a whole lot about some of these more advanced settings. What would you recommend for governor/hotplug/minclock settings if I really want to go high performance without completely decimating my battery?
[Nexus 6 Android Development] Xileforce:
I may consider adding another step like lean has 223 :P. For you I would recommend mako hotplug. Set the load threshold to 0 which effectively disables hotplugging forcing all 4 cores on. Then I suggest using interactivex on the last two cores and Wheatley governor for the first two. You can do all of that in synapse. To enable mako just turn off intelli and mpdecision. All 4 cores won't kill battery l. In fact I've gotten 7h sot with that setup and the 8h screenshot in op was running that setup. Will eliminate lags too :)
[Nexus 6 Android Development] Roland Deschain:
I just now installed Synapse for the first time. Holy smokes, the options available are nuts. Not going to bother with Faux anymore. I assume I should have MPDecision and Intelliplug both disabled, and that combined with the load threshold being 0 is what forces the use of Mako? If you set the load threshold to 0 but keep either MPDecision or Intelliplug enabled, I assume the load threshold does nothing at that point, then? Just curious.

Thanks for the tips, I'll be curious to see how this behaves. :)
[Nexus 6 Android Development] Xileforce:
Yup. The load threshold is specific to mako. It basically tells it what the load has to be before it turns another core on. The default is 80. If u make it 0 that tells the hotplug that essentially it should online all of the cores at 0 load. Which means all the time.
[Nexus 6 Android Development] Roland Deschain:
Crap. Setting load threshold to 0 makes my phone hard-freeze (can't turn on screen, and it's burning CPU because it gets hot, have to hard-press power button to turn it off and boot it back up) within a few minutes of having turned off the screen. Through a process of elimination, it's specifically changing that slider. I can turn off MPDecision and make no other changes and it's fine, but as soon as I lower the load threshold to 0, it freezes within a couple of minutes. Thought it might be a voltage issue, but still happens even when I apply a universal +50 overvolt. I assume nobody else is having this happen?

Edit: Upon further playing around, the problem doesn't happen if I leave Intelliplug enabled, and SystemPanel still shows all four cores as staying on; so is it normal that you need to leave Intelliplug enabled? I was under the impression that mako was another hotplug to use in place of others like MPDecision and Intelliplug, but is it supplementary to be used with one of those instead?

Edit 2: Scratch that, just took longer to happen this time. Hrmph. Guess I'll give up on it until 5.1 ROMs start coming out and I'll do a clean install and see if it works for me at that point. :(
[Nexus 6 Android Development] Xileforce:
if u leave intelliplug on. then ur using intelliplug. mako only activates when no other hotplug is enabled. Im not sure whats going on for you though :/ I'll test it for a bit myself.
[Nexus 6 Android Development] elevatorguy:
Had the same issue went to check phone and it was off. Had to hold vol and power to get it to reset and come back to life first time scared the crap outta me. Happened a few times went back to 85 on the threshold and all seems back to normal. Will report back if issue is gone
[Nexus 6 Android Development] Roland Deschain:
I'm on the latest Chroma ROM, if it matters. I do have Xposed installed and working, as well. Obviously, this may not be kernel-related at all, too.
[Nexus 6 Android Development] USA-RedDragon:
*Gasp* is that kexec-hardboot in Vindicator? Leaked photos of a possible new feature?
[Nexus 6 Android Development] Xileforce:
1.5 is out! MultiRom Support(The first!!), thanks to [MENTION=5184450]jamcswain[/MENTION], new lean merged in and boatloads of other patches and optimizations! Read FAQs!
[Nexus 6 Android Development] aoaleman:
Thank you very much! Absolutely love your work!
[Nexus 6 Android Development] Roland Deschain:
Sweet. Your multi-ROM instructions seem pretty clear except for one thing; you never flash a kernel. How do we update the kernel for any given ROM then, or does flashing a kernel do it for all ROMs on the device? I guess what I'm asking is, how is changing/updating of the kernel handled if you use this app to run multiple ROMs?

Edit: Looks like it's handled within the app itself, interesting. Not sure I want to play with beta versions of something as potentially device-breaking as multiple ROM support though, haha. (Device-breaking as in, the possibility I may need to flash a stock ROM to fix things, etc.)
[Nexus 6 Android Development] alwayslookingforanswers:
Followed instructions for multi ROM install. Try to update but says unbutu is not supported. Not sure if I'm doing something incorrect or not?
[Nexus 6 Android Development] Berlino:
There is no ubuntu for shamu atm...for further installation details for MultiRom have a look here: https://plus.google.com/106544733723469872647/posts/FZ2cSzTQwBH

In settings for MultiRom-Manager you'll first have to tap 7 times on version number and then you're developer and have to change the update path for manifest url to: http://tasemnice.eu/multirom-test/manifest.json (just add "-test" into it)
[Nexus 6 Android Development] Xileforce:
Actually multi ROM is pretty safe :) as long as u don't delete ur standar normally flashed ROM. It just makes new instances completely separate. And u don't flash a kernel because it will use ur existing kernel u flashed normally. So just flash the kernel like normal in twrp to update it for all ROMs ;)
[Nexus 6 Android Development] hellsgod:
With kexec it doesn't use your existing kernel. So it depends how you install the rom :)

hells
[Nexus 6 Android Development] Xileforce:
It does because you do the remove boot.IMG thing in twrp. At least that's how it worked for me. I'm running bliss and liquid on the same kernel without flashing another one.
[Nexus 6 Android Development] hellsgod:
You can either share the kernel or not. What do you think kexec support is for? To boot a second kernel. I'm doing the multi rom thing since the N4 days, that's why I know it :)

hells
[Nexus 6 Android Development] USA-RedDragon:
It shares a kernel. But the injection of boot.img that happens after every flash is MultiROM making stub code to boot a different ROM. It loads the code just like a kernel, but in that stub, it loads the regular kernel in the context of the other ROM. Say you were to flash a kernel in the other ROM. It would be pointless. Why would it let you flash a kernel that doesn't have kexec-hardboot (almost all at this point), because that's what multirom depends on. So it runs the system kernel because a kernel is systemwide. And it is for certain compatible with kexec-hardboot

Tl;dr It shares a kernel because it has kexec-hardboot support to run a kernel STUB to run the original kernel in the context of the second ROM
[Nexus 6 Android Development] Xileforce:
Yea I'm a noob to this kexec stuff....I'll...um..just let u guys figure that out lol. All IK is it works for me xD
[Nexus 6 Android Development] hellsgod:
I've done it multiple times on mako and hammerhead. CM needs a seperate kernel on these devices, so you can run CM on these devices with the CM kernel, even if your primary rom runs an AOSP kernel.. It wouldn't boot if it would load the AOSP kernel from theses devices to boot up CM. If you install a rom in the multirom TWRP you can choose to share the kernel, or not. If its different on shamu, I've said nothing. But thats the way it worked on mako and hammerhead.

hells

---------- Post added at 07:19 PM ---------- Previous post was at 06:58 PM ----------

Just have a look in this post on the N5 forum: http://xdaforums.com/showpost.php?p=48508488&postcount=3

Can I have different versions of Android working alongside

Yes. As long as you select "Don't shere kernel" when installing the secondary ROM, the systems are separated.
[Nexus 6 Android Development] LunaticSerenade:
Flashed 1.5, and it works great.

Regarding the signal issue, I can now confirm that, for whatever reason, flashing a new kernel sets the radio to WCDMA_Preferred, and Synapse tries to lock it in.

Going to the phone information menu and changing it to whatever is needed for your carrier (LTE/CMDA Auto PRL for Verizon) fixes it though.
[Nexus 6 Android Development] Xileforce:
Thanks for sharing that! Good to know.its just a weird synapse issue :/
[Nexus 6 Android Development] Xileforce:
Thanks for all the info man! This is helpful, though I don't recall seeing an option to share kernel. Probably just missed it though. U must be a multirom pro lol
[Nexus 6 Android Development] LunaticSerenade:
For sure.

I did have a question: did you do something with the audio in this version? Because the clarity over bluetooth is incredible.
[Nexus 6 Android Development] hellsgod:
Its not done for shamu yet, so this option may come in the future, in the final release (or its really there, I haven't checked!). No I'm not a pro, its just I used that feature on mako and hammerhead in the past, booting different android versions, which needed different kernels and so on :) And I've no idea if the same thing is possible for shamu. I only talk from "older" devices ;)

hells
[Nexus 6 Android Development] Xileforce:
Helpful nonetheless. I've never used kexec before. But jamcswain just decided he wanted to port it over lol so I included it. Seems to be working fine for me using the remove boot.IMG method. I'm not sure what would happen if I didn't do that. I'll let you guys tinker around with it. BTW multirom just got updated and should tell u in the app ;)
[Nexus 6 Android Development] USA-RedDragon:
Sorry about that. Some of us in the beta got a new kernel in the new ROM while some of us were still on Vindi. So I think that caused some confusion. And yeah, most of the code is the same with the exception of not having ramoops-console or whatever it is. I had to preallocate memory in a certain address to copy the exec'd stuffs.

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

Plus I'd rather share my Vindi kernel across all builds.
[Nexus 6 Android Development] Xileforce:
I'm sure we will figure it out better in the next few days.
[Nexus 6 Android Development] dannieloco:
this must be based on the ROM then? I don't ever have a signal issue.. and its stays on LTE whenever I update the kernel
[Nexus 6 Android Development] alwayslookingforanswers:
I did all the instructions as shown. I never got redirected to the sight. Thanks for your help.

---------- Post added at 05:23 PM ---------- Previous post was at 05:15 PM ----------

Weird. When I opened Multirom app again. Everything finally updated earlier I would hit refresh and it kept giving me the same response no unbutu. But now everything is up and running fine. Thanks
[Nexus 6 Android Development] LunaticSerenade:
Possible I suppose. I'm just on stock though.
[Nexus 6 Android Development] dannieloco:
oh ic.. Im on Chroma.
[Nexus 6 Android Development] LunaticSerenade:
I guess the important thing is that I found a way to make it not an issue, so I can use the kernel I want on the ROM I want. :D
[Nexus 6 Android Development] Xileforce:
There is no Ubuntu. That doesn't have anything to do with multirom. It just is there for devices that support ubuntu. All u need is to install the two first check boxes. Those will unchecked themselves after u install unless there is an update. If u follow directions in the FAQ spot you should be just fine :)
[Nexus 6 Android Development] gamewarden234:
Wow. Where had this been hiding. Hello Vindicator good by franco
[Nexus 6 Android Development] stevepick2:
I get this message when trying to use multirom. What am I doing wrong?
[Nexus 6 Android Development] Mistertac:
Did you follow his guide in op and change the Manifest url to this :

Then go back to that screen you're on and refresh it by sliding down?
[Nexus 6 Android Development] stevepick2:
Yeah I've already done that

I installed the recovery manually and it also says Multirom is missing

Edit- finally got it to work

Giving an old Rom that I use to use on my S3 a try called infamous

Not having any luck with Roms booting
[Nexus 6 Android Development] MadBrad11:
Disabling the "bluesleep" wakelock has been working great for me and definitely seems to help battery life when connected to my LG G Watch and everything works fine. The only problem is that this doesn't also stop the "msm_serial_hs_dma" wakelock from appearing. The "msm_serial_hs_dma" wakelock always appears on my phone with "bluesleep" whenever bluetooth is connected and has similar long wakelock times. Would it be possible to also block or lower the kernel wakelocks for "msm_serial_hs_dma" as well? Thanks!
[Nexus 6 Android Development] Xileforce:
I'll look into it and maybe try it with the beta testers. Or maybe I'll see if I can just reduce it a bit. Hard to say with these wakelocks what may breaks stuff and what won't.
[Nexus 6 Android Development] MadBrad11:
That would be great! Let me know if you need someone else to test this and I'd be glad to help!
[Nexus 6 Android Development] Xileforce:
You are trying to boot a ROM from a different phone?
[Nexus 6 Android Development] stevepick2:
No, using shamu roms.

It says:

An error occured.

Shutting down MultiROM to avoid data corruption.

Report this error to the developer!

Debug info: /sdcard/multirom_log.txt

Press POWER button to reboot
[Nexus 6 Android Development] Xileforce:
Did u click the remove boot.IMG button?
[Nexus 6 Android Development] stevepick2:
No, didn't see that... Should I try it?
[Nexus 6 Android Development] Xileforce:
Kk that's probably the issue. Its towards the end of the guide in FAQs if you follow it exactly u should be golden :)
[Nexus 6 Android Development] stevepick2:
Worked! thanks :)
[Nexus 6 Android Development] Xileforce:
Awesome! Don't forget to flash gapps in that area too for the ROM! Have fun.
[Nexus 6 Android Development] USA-RedDragon:
I know its not up to par. I was hoping for a temporary solution until you came with your patch. We will merge when it comes. I took most of the code from hammerhead patches.

---------- Post added at 03:59 PM ---------- Previous post was at 03:58 PM ----------

Actually all but memory addresses came from hammerhead
[Nexus 6 Android Development] Xileforce:
Version 1.1 Is Up! Changelog in First Post.
[Nexus 6 Android Development] jaythenut:
cool downloading now :D
[Nexus 6 Android Development] afraaa:
Don't have device , but seems you have some potential to do kernel .. I'm running nexus 5 and away happy to hear about kernel makers on beloved nexus devices ... very good feedback .. i will keep my finger crossed for you keep it up man :):fingers-crossed:
[Nexus 6 Android Development] Mistertac:
Actually no I haven't ran Pure in quite some time.

I've ran Euphoria, Twisted Slim, Bliss, Liquid and I'm sure one or two more I'm just not remembering.
[Nexus 6 Android Development] Swamphound:
Thank you for this kernel. I'm trying to follow the configuration guide and have enabled lcd_panel but I must be blind because I can't see the idle/stats options for setting the C states. I'm running Chroma ROM and using the Faux app and Franco updater.
[Nexus 6 Android Development] Xileforce:
Its directly above thermal manager and directly below CPU governor. However I just thought of this, I'm using the fauxclock beta app and that may be why you don't have the option. I believe by default all of them are enabled though so its not a massive issue.
[Nexus 6 Android Development] Swamphound:
Thought about that. Just asked to join the beta community on g+. Ty again.
[Nexus 6 Android Development] Xileforce:
Awesome! And no problem, I'm happy to help.
[Nexus 6 Android Development] OverSu:
Thanks for your answer (DT2W) !

I will try this one today and give you some feedback.

Seems to be a really great kernel.
[Nexus 6 Android Development] Mistertac:
It's definitely another great option kernel-wise for us. Yesterday I had 6 hours SOT over a 10 hour period, played music ( Play Music ) over BT for about 1.5 hours, used Navigation for about 30 minutes and did a lot of browsing, Tapatalk etc.. I ended up plugging it in at 15%. Seems great to me!

As for what settings I used , I ran Interactive, FIOPS and Franco Hotplug. Only other thing I usually change is my max freq to 1.9 but who knows how much that is really helping me, maybe I'll test at stock value and see.

Anyways... Great work Xile
[Nexus 6 Android Development] rignfool:
The sysfs interface for mako hotplug on your kernel is...

/sys/devices/virtual/misc/mako_hotplug_control

To adjust... Use echo commands...

Ex:

echo 0 > /sys/devices/virtual/misc/mako_hotplug_control/load_threshold