yashsingh1/xdaforums huggingface dataset:
[One (M8) Android Development] fizbanrapper:
Ha! I know that feeling all too well!

Sound - I wonder if Sense ROMs are even capable of reaching those last two steps? I'll have to experiment a bit. If this is really just an issue where Sense has set their volume "governor" lower than AOSP, then I've just got to find the appropriate settings and make the same adjustments. Those settings are definitely going to be in a C file rather than the defconfigs though. I don't want to chase down rabbit holes trying to find new drivers etc. if the bug has been fixed, but the issue is just having too high of volume in the AOSP kernel.

WiFi- Feel free to update me on WiFi and let me know if there are any other changes, for better or worse. I did change the WiFi configuration, and those changes could have a significant impact.

Bluetooth

Some of you mentioned bugs in AOSP with bluetooth. Any problems in the new build?

Proximity Sensor

I'd also like to know if you've noticed a difference in the functionality of the proximity sensor. You mentioned that the phone doesn't properly deactivate the screen while making calls, resulting in your ear pushing buttons on your behalf. I also know that pocket detection has been poor on a lot of AOSP ROMs, which causes the phone to wake when it shouldn't.

I've experienced both issues on different ROMs, but I'm not sure if PAC builds had those problems before (they probably did). With the last build, those things are working nearly perfectly so far. I need feedback from others though, cause I can be a sucker for the placebo effect. Plus, our M8's are not all identical.

Battery

Any noticeable change in battery life? I haven't seen a difference yet, but that's meaningless. I just disconnected it from the charger about 20 minutes ago. I'm not expecting improvements here, just hoping for no significant negative consequences!

Other

What other AOSP bugs are out there? I've only had an M8 for maybe 3 months, so I'm still way behind the curve here.

The configuration modifications could have changed a lot of different device functions, so please report anything else that you think is worth noting.
[One (M8) Android Development] jcole20:
I actually just noticed proximity wasn't an issue for me on my last call... Funny you mention that. Its been gaining attention on other Roms here lately.

I do think sense isn't capable of this high of volume. That's been a comment I've had regarding the sound issue since the beginning.

My issue hasnt been Wi-Fi its been the handover to cell when Wi-Fi disconnects/toggles. That seems to be a lot better (no issues thus far, but I won't know for sure for another day or so).

Bluetooth I'll have to test later this afternoon.

As far as any other issues the only bug I've found has to do with PAC Settings -> Buttons -> Recents Long Press Action . This appears to be customizable but selecting it doesn't bring up any options. I don't have any need to use this but just a heads up.

Outside of the above... By far the best build to

date.

Edit: I didn't comment on battery because it is way too soon to tell.

Edit 2: Above I said "since the beginning" but like you I've only had this device a short while. Roughly 5-6 weeks.

Edit 3: the battery life is significantly better thus far.

HTC One (M8) MultiRom: PACman 5.1.1; SOKP 5.1.1; CyanogenMod 12.1.1 (Nightlys updated weekly); ViperOne M8 w/Hypernova Kernel
[One (M8) Android Development] dopy25:
Regarding MultiRom:

Many people use it and it is drastically gaining popularity. If there are any bugs (I only see it on the newest (V32), there are a ton of users that would appreciate the time you spend on it. There are not many people working on it, but tons using it. I for one would be very grateful, much as I am that you built PAC. I was looking into building myself because I love the ROM. And the fact that you are building other ones is just super!

I only hear sound distortion at high volume as well.

I have noticed slow speeds on WIFI (slower than LTE) and that is not the case on Sense.

I had an issue where I lost service altogether and had to reboot. No calls out or in, no texts out or in.

The only thing I notice with proximity sensor is that it is sensitive. I need it right against my head or buttons will be pressed.

I did notice a keyboard issue (built in AOSP) on the SOKP build that is not present here. I am not sure how I have full use of the AOSP keyboard here but not in SOKP (and others cannot use full function in either ROM). Perhaps it has something to do with a build.prop entry?

The reason I think that is because I can toggle data in pac but not SOKP, and the keyboard here but not there.

I am on Sprint with the HK version. Latest FW, I ran the last OTA for version 654.14. Both ROMS are installed as secondary.

Also, I am using the 5/17 build, about to flash 5/19. 5/20 (didn't realize it was just after midnight when you posted it)
[One (M8) Android Development] jcole20:
I've not had the speed issue mentioned but I draw off a 5g band generally... Could be a fluke? The aosp keyboard does not have working gestures for me but only a few Roms have this working [MENTION=4550510]5.1[/MENTION].1 on my end.

The latest build seems to be much better BTW.

HTC One (M8) MultiRom: PACman 5.1.1; SOKP 5.1.1; CyanogenMod 12.1.1 (Nightlys updated weekly); ViperOne M8 w/Hypernova Kernel
[One (M8) Android Development] dopy25:
[MENTION=5676253]fizbanrapper[/MENTION] I can't seem to get a loud volume from my bluetooth headset. When the call starts, I can hear. But it immediately drops the volume to a level that is barely heard.

I updated to the 5/20. dirty flash since 5/13. I can clean flash and try a few calls. It would have to be later though.
[One (M8) Android Development] fizbanrapper:
Thanks for the feedback everyone!

Tonight's build includes a change from LZ4 compression to XZ for the kernel and ramdisk. LZ4 is huge, and the kernel was approaching its size limit. Tonight's build also includes a bump from 5.1.1_r2 to 5.1.1_r3.

That's a small bump in AOSP revisions, but I don't want to change too many other things until I get to test it out. For my part, I thought battery life went from awesome to awful after the recent changes. Hopefully it's better in tonight's build. We'll see.

It was a 3-ROM night, as I also posted new builds for SOKP and Slim.
[One (M8) Android Development] fizbanrapper:
Can't speak to anything else just yet, but tonight's build is snappier than last night's.

I'm curious if the smaller kernel has fixed any of the other bugs.
[One (M8) Android Development] Broodn:
Downloading now :D
[One (M8) Android Development] jcole20:
Man... You're killing me releasing these at midnight est lol...

Downloading....

On a side note... Much much better battery life and sound quality but I had a random reboot to bootloader today while driving. First time I've had that happen.

HTC One (M8) MultiRom: PACman 5.1.1; SOKP 5.1.1; CyanogenMod 12.1.1 (Nightlys updated weekly); ViperOne M8 w/Hypernova Kernel

Okay.. So your latest build is great. It appears with the last two builds that the Wi-Fi to cell handover issues I was having are gone. The handover is much quicker now. Awesome [emoji106] !!!

The proximity issue is improved... Still not perfect as if you're walking the motion is apparently waking the device occasionally but it's better than pretty much every aosp ROM I've used.

Obviously sound has immensely improved. This ROM is slowly becoming hands down the least buggy and most reliable aosp rom..

I can't comment on battery on this one yet bit so far seems good.

I'm noticing small animations and stuff that weren't there a week ago. Overall ive only seen one feature/tweak not working and that's the recent button I mentioned. Honestly fizbanrapper you're perfecting this ROM and you're doing a hell of a job. Thank you... I know it's not just for me but seriously this is an awesome rom. Glad to see pac like this.

Edit: 2 hours off charger from 100% with 87 minutes screen on time I'm at 90%. So an hour and a half roughly for 10% on Wi-Fi on Tapatalk and Chrome. Very very good stats. :)
[One (M8) Android Development] bombo_b:
Smoooooth

Hi , I have tried the rom on my sprint M8 and I can tell its soooo smooth. I like the feel of it and sound is so loud. I also love the FX equalizer.

But unfortunately it doesnt detect my simcard and this is a no go for me since I am using the Sprint M8 on gsm. its sad that I had to go back to sense Rom. :crying:
[One (M8) Android Development] n1234d:
I'm going to say that that limiting the volume will be an instant fix. Another thing is that sense definitely reaches those volumes, and sometimes more. Thing is, sense automatically reduces the volume when there's lots of bass and chances of distortion. On vocals, the speakers absolutely blow you away with the loudness.. Also, it sounds like the mid bass is boosted quite a bit, and sub bass is reduced. Also, the mids sound a little boosted too.. You must test on sense, in quite scenes in movies or vocals in songs, just hear how loud it gets. It doesn't do the same in aosp, so limiting the volume introduces a potential problem of speakers being too soft on these quiet scenes or songs.
[One (M8) Android Development] jcole20:
The very first thing I noticed coming to aosp was how much louder the volume was. I have a db meter somewhere to verify. Perhaps there's an app that can log the outgoing intensity. You're right about senses limiter but I'm not sure you're right about it being louder... I remember thinking damn I'm gonna blow these speakers when I first flashed aosp.

HTC One M8 MultiRom: PACman 5.1.1 & DirtyUnicorns v9.3 (5.1.1)

---------- Post added at 12:30 PM ---------- Previous post was at 12:26 PM ----------

I've got no clue how audiofx is working for you... It doesn't do a thing on my end. Even after a ruu. I wonder if it has to do with the HK adsp at this point. I'm so tired of not being able to figure out why it's not working on my m8 but was at one point. It has to be hks adsp. I can't think of any other piece of the puzzle.

HTC One M8 MultiRom: PACman 5.1.1 & DirtyUnicorns v9.3 (5.1.1)
[One (M8) Android Development] n1234d:
Well I guess that may be right too. The thing is, it sounds louder because it dynamically increases the volume on these quiet scenes.. It would be absolutely Flippin insane if this worked on aosp. Also, does everyone else have stereo audio from speakers or just mono?
[One (M8) Android Development] bombo_b:
Well it seem to have been a placebo effect due to excitement on the rom.:rolleyes: the equalizer really does nothing :(
[One (M8) Android Development] sjpritch25:
Is PAC compatible with rro layers themes?
[One (M8) Android Development] SiK TL:
No. It uses the CyanogenMod theme engine.
[One (M8) Android Development] NiXiNiX:
How did you guys get past the "google play service" error?

I used my gapps on several other roms (Bliss, DU, Liquid) and they worked just fine.
[One (M8) Android Development] fizbanrapper:
It was only an issue in the very first builds, and then again in the very last build. No clue why it happened in the first builds, but the last build was due to kernel configuration.

I'll (hopefully) be posting a build shortly, which should address the issue.
[One (M8) Android Development] fizbanrapper:
Special builds will be made for PAC-man featuring the kernel from CandyROMs! Please see the second post in the thread for link!

This kernel should have the same bug fixes I had been working on, but they've done a ton of other things to improve the kernel. A lot of these things I could do on my own, but it'd take me twice as much time and be half as good. Their kernel is simply far better than mine and I very much appreciate their offer to allow me to build my ROMs with it. Thanks to [MENTION=5066258]rc420head[/MENTION] and [MENTION=5795145]javelinanddart[/MENTION] !

I anticipate that most of my personal builds will be incorporating their kernel, since jenkins will start spitting out a plain vanilla CM-based kernel (that's the way I'd prefer to keep it, too).

Well I hope you all enjoy the latest! Feel free to provide your opinions.
[One (M8) Android Development] fizbanrapper:
Battery life should improve with the new kernel. If it doesn't, tweak the settings!

Ditto for performance!
[One (M8) Android Development] javelinanddart:
Lol not you again! xD ;)

It's all open source bro, feel free to use it
[MENTION=1615671]Zarboz[/MENTION] did a lot of the initial work on it too

Just glad to see our work being used
[One (M8) Android Development] yung40oz84:
Tried to install the latest version with the CandyRom kernel and go a bootloop and corrupted internal memory, had to format :crying:
[One (M8) Android Development] fizbanrapper:
Thought the same thing when I saw your name in the commits! :)

While I don't need permission legally, out of courtesy I won't use it if I don't have permission.

Thanks for adding the Zarboz mention and thanks for your hard work!

I'll probably use your kernel in future SOKP builds too.
[One (M8) Android Development] javelinanddart:
Did you modify the ramdisk so the mpdecision and thermald binaries don't interfere with inbuilt msm_mpdecision and msm_thermal?

Or remove the binaries entirely?
[One (M8) Android Development] yung40oz84:
Is nobody else having boot loops and issues with latest build with Candy kernel in it? Mine boot looped and I tried twice with different Gapps and same result and second time corrupted internal
[One (M8) Android Development] fizbanrapper:
How?
[One (M8) Android Development] fizbanrapper:
Maybe this is related? Not sure yet. Sorry!
[One (M8) Android Development] yung40oz84:
Related too?
[One (M8) Android Development] fizbanrapper:
The ramdisk issue mentioned in the post above yours.

It flashed just fine for me, but that was a dirty flash on a secondary ROM. That could make a difference.
[One (M8) Android Development] jcole20:
Lol I flashed candy kernel from their latest build long before this new info. It doesn't bootloop for me but sysui crashes. I didn't mention it because candy is going to push those vanilla builds from what I was told in the kernel beta group in part of. Also masstash is going to build an aosp kernel that I'm currently waiting to beta test. Hypernova + Franco m8 aosp ;) ...

Also [MENTION=5676253]fizbanrapper[/MENTION] I'm so glad this ROM that you've built is beginning to get the respect it deserved. Good for you bud.

HTC One (M8) MultiRom: PACman 5.1.1; SOKP 5.1.1; CyanogenMod 12.1.1 (Nightlys updated weekly); ViperOne M8 w/Hypernova Kernel
[One (M8) Android Development] fizbanrapper:
What firmware are you on? I'm on 4.28.
[One (M8) Android Development] javelinanddart:
init.qcom.rc modification, cherry-pick it from candy m8 tree
[One (M8) Android Development] jcole20:
Vzw latest to us is 4.17.605.5

HTC One (M8) MultiRom: PACman 5.1.1; SOKP 5.1.1; CyanogenMod 12.1.1 (Nightlys updated weekly); ViperOne M8 w/Hypernova Kernel

---------- Post added at 12:30 PM ---------- Previous post was at 12:27 PM ----------

I think it's great that you are wanting to help by allowing him to use your kernel for unofficial releases. And even better that he asked permission. Kudos to both of you.

HTC One (M8) MultiRom: PACman 5.1.1; SOKP 5.1.1; CyanogenMod 12.1.1 (Nightlys updated weekly); ViperOne M8 w/Hypernova Kernel
[One (M8) Android Development] krazie1:
Awesome to hear more kernel choices will be making a debut for the M8 & AOSP, PAC 20150520 is running great here.
[One (M8) Android Development] kickassdave:
Can't properly boot with candy kernel version. Phone freezes then reboots during optimisation process. Tried multiple wipes, rewiping cache etc. No luck. Flashed version from 20th and all good again.
[One (M8) Android Development] jcole20:
I'm downloading your PAC build w/candy from 2-22 my post before I had just pulled the boot.IMG out of candy ROM and flashed it on to PAC and sys ui fcd ... We'll see what this does.

HTC One (M8) MultiRom: PACman 5.1.1; SOKP 5.1.1; CyanogenMod 12.1.1 (Nightlys updated weekly); ViperOne M8 w/Hypernova Kernel
[One (M8) Android Development] Broodn:
Tried the one with the Candy kernel an it won't boot. It optimizes the apps reboots then reboots an does the same thing over again.
[One (M8) Android Development] jcole20:
I just flashed PAC w/candy kernel its showing fizbanrapper@fizban (guess you merged their kernel code) and it booted fine and is running fine. Only noticeable difference is weather in notification isn't working by default you have to change location to high accuracy obviously. Just flashed though I'm gonna play with it some. I'm running it as my primary though idk if anyone who hasn't gotten it to boot is running as secondary.

HTC One M8 MultiRom: PACman 5.1.1 & DirtyUnicorns 5.1.1

Edit: wow... I think the candy kernel needs more CPU governors. Jesus I bought trickster mod to really see what all this kernel has in it and there like 20 different governors. I don't have a clue what to pick... Lol

Edit 2: I hate to say this but thus far battery life has been horrible with the candy build (5-22).
[One (M8) Android Development] fizbanrapper:
It's the name of my machine & my username in ubuntu. Yeah I swapped my kernel repo out, and replace it with candy's source.

Yeah there are still bugs in PAC, which is why they haven't started nightlies yet. It's actually the first time they've permitted builds prior to official release. Some bugs will get squashed, then pop up again.

I pushed the commits to start 5.0 nightlies a few days ago. If there are any Jenkins issues, this should help me to make sure they get ironed out prior to 5.1 release. Builds should be starting soon.

Didn't get a chance to do anything last night.

Sorry to anyone who is having problems with the new build.

I like abyss plug so far. I prioritize battery life over performance. Just watch the frequencies when changing governors. Some have reset the min frequency, and you have to reset the frequency limits to get it to stick.
[One (M8) Android Development] jcole20:
Yeah I knew that was your machine I was just mentioning it because obviously you're not just placing a boot.img in you're building w/kernel.

I've had battery issues this morning... I'm going to switch to your gov. Currently I'm running smartassv2 and dropped 10% in 20 min. Which is faster than what I normally see.

Hmm, my battery issues have to be the max/min bug you mentioned. It's locked at ~1200 min and ~1900 max. I changed min to ~600 and ~2500 max. What's your min setting by chance?

HTC One M8 w/MultiRom: PACman 5.1.1 & DirtyUnicorns 5.1.1
[One (M8) Android Development] fizbanrapper:
Screen wake features in this kernel are also different. That can affect battery life too.

You've really got to look at the frequencies on the info tab. Watch how they behave at idle. Then swipe up and down on the screen, to get it thinkin. Observe how it responds, then how it scales back down.

Use warp timers to reset the timers after a governor change. This will give you a better picture of time in frequency state.
[One (M8) Android Development] jcole20:
I'm going to play around and really go through it but I can tell you reducing the min from 1267 to 652 has already made a HUGE difference. My battery isn't draining 1% every 2min now.

HTC One M8 w/MultiRom: PACman 5.1.1 & DirtyUnicorns 5.1.1

Regarding the new ROM+candy kernel the following setup has been absolutely awesome....

TricksterMOD Donate Version:

Frequency Lock On

CPU Governor abyssplugv2

Minimum Frequency 652800

Maximum Frequency 2572800

Max Screen Off 1036800

I have a lot more settings I use but these are my cpu frequency settings. I've tried a few different governors but my battery life is insane with this setup. Performance is good as well.

Edit: man... Honestly this build 5-22 PAC + Candy is running so well it's crazy... But in call my phone is constantly clicking like I'm making selections. That's the only issue I have. That clicking on call is driving me crazy. Outside of that the battery life is absolutely insane and performance is exceptional.

Oh and if you're using tricksterMOD I highly suggest users do not force enable fast charge. This makes the system highly unstable on my end.
[One (M8) Android Development] fizbanrapper:
I drop my min the whole way down to 268 (I think that's the lowest. I'm certain that its the only one below 300). I think I keep my max around 1.7. I never play games and very much appreciate a long-lasting battery, even if there are performance costs.

Anyway, I've uploaded two new builds. The one in the main directory has no kexec-hardboot patch. It is (essentially) stock CM kernel. The other is a Candy Kernel build. I've picked the commit mentioned by javelinanddart, which (fingers crossed) may help with the issue some of you were having with the ROM not booting properly. There was some candy-specific stuff in there too, so I had to make changes to what was cherry-picked. I'd rather not push the commit until I get some feedback on how it's working out. I'm hoping that the issues from earlier were eliminated.

Please do follow along and read the last two pages if you're flashing the Candy kernel version. The Candy kernel is fantastic. It's a great custom kernel, but like all great custom kernels, it requires customization!!! There are also little quirks that can really kill your battery and/or performance if you don't know what you're doing. Again, custom kernels require that you know more than the average user. Don't blame the kernel just because you don't know how to use it. My battery life and performance have both been amazing, but it wouldn't help for me to just give you my own settings and then try to make those work. You don't have the same apps, usage pattern, and other general expectations and requirements that I do.

There are battery bar commits on gerrit, but they haven't been merged in yet. I really like that feature, so I'm excited about that! Other ROMs have had it for a long time now.

I was on a camping trip with the family this weekend, so I didn't get much accomplished. I did manage to get these two PAC builds out, fixed an error that should get PAC 5.0 nightlies rolling, and have an SOKP build that's compiling at the moment. Going to bed and won't get to upload it until morning though (assuming all goes well, that is).

Hoping to crank out a slim build tomorrow night.
[One (M8) Android Development] Broodn:
The new build with Candy kernel booted up no issues. Thanks
[One (M8) Android Development] fizbanrapper:
So glad to hear it. Especially since you were one of the people who had issues with the last build. I really didn't want to have to stop using their kernel!

I was too impatient to wait for the battery bar commit to be merged in, so I just cherry-picked the commits off of Gerrit and ran another build. It's the 5/26 build in the Candy Kernel folder. I haven't flashed it yet, but I'm downloading it now.

Another hiccup on the 5.0 nightlies. LZ4 is a no-go on PAC's jenkins machines, so the build failed last night. Pushed the commits this morning, to change from LZ4 to XZ compression/decompression. I'm assuming those will be merged in tonight and I'll get to see what the next error is...

SOKP build didn't work, but I really didn't have much time to look at it. I'm going to do a make clean tonight, and if I have the same problems afterwards, I'm going to reach out to the other maintainers to see if they're having issues. It looks like they're working on some significant changes.
[One (M8) Android Development] mcwups1:
I don't see any downloads.

Sprint M8 Converted HK 4.25.654.14
[One (M8) Android Development] jcole20:
[MENTION=5676253]fizbanrapper[/MENTION] idk if you've synced the new candy commits that help with the proximity sensor but if you haven't please do. I hate to suggest stuff like that to the Dev in charge but the in call issues are very annoying. Outside of that it's been rather flawless. Gonna check out the new build in a few. Thank you again.

HTC One M8 w/MultiRom: PACman 5.1.1 & DirtyUnicorns 5.1.1

---------- Post added at 10:12 AM ---------- Previous post was at 10:12 AM ----------

2nd post in the thread not the first

HTC One M8 w/MultiRom: PACman 5.1.1 & DirtyUnicorns 5.1.1
[One (M8) Android Development] fizbanrapper:
Yes, the commit was picked up in the most recent build.