yashsingh1/xdaforums huggingface dataset:
[One (M8) Android Development] jcole20:
All of these aosp/aokp/cm(aosp) (not the case with gpe) Roms are compatible with any carrier. They have no carrier data in the flashable .zips so yes they work on Sprint. I'd attempt a reflash if I were you.

Sense Roms and GPE Roms, you may notice, are 1+GB in size. These Roms are carrier specific in most cases. AOSP builds like PAC and CM are only 250+ MB in size. These Roms contain a kernel (boot.img) and system folder/image only. So... You can use any of these Roms on your device regardless of carrier.

HTC One (M8) MultiRom: ViperOne + Hypernova Kernel & CyanogenMod 12.1.1

---------- Post added at 06:03 PM ---------- Previous post was at 06:01 PM ----------

Of course there is interest... The more the merrier, however, I don't believe it's appropriate to advertise for another build in someone else's thread. But, yes, of course I'm all for something else to try out [emoji106] [emoji106] [emoji106]

Edit: I understand why you posted it... Explaining slim having similarities to the situation with PA. I mean the above not to criticize you... It's just if I was posting my build/ROM I'd be irked if someone said "I have xxxx build if anyone wants it". I hope you understand. But, don't get me wrong, if love to try your slim build. As I've stated many many times, the more development and larger the choice the more competition to spawn innovation. So, please, start a thread and share that build of yours, [emoji12] [emoji3]

Edit 2: Its been brought to my attention that you're the OP. Sorry bud I was just trying to look out for you. I thought I was rather civil but I just didn't want to distract from this great ROM in this thread. Again, the more the merrier... Phase share.

---------- Post added at 06:08 PM ---------- Previous post was at 06:03 PM ----------

I hope you're right... But what made p.a. p.a. wasn't the work that does in kk/jb. It was their ongoing innovation. A build that simply being their past development to the new android versions without their constant innovation isn't really the same. I hope if they do come back, they come back with actual coders behind them and not just someone who is merging new source. You and I both know merging and compiling a build isn't the same as actual innovative development.
[One (M8) Android Development] dopy25:
I guess that's good to know with the M8, but it's not the same for all devices. Especially the last one I had, the Optimus G. Each ROM had to be built with the carrier (model) specific sources. That is until they were all unified. And once again, not all are like that.

Also, I am talking about the very first install which of course was a clean install. I mean, I can try it again but seriously. It was a clean install.

Thanks for the tip,

Here's on for you: the other person you quoted is in fact the OP, so he built this rom from source and is asking if anyone is interested in another one he built from source in his own thread (which is unofficial, so it's acceptable to ask if there is an interest in another rom) so don't trip. I am certain he knows the rules and has good intentions.
[One (M8) Android Development] jcole20:
Lol... Yeah I didn't catch that. It had nothing to do with the rules. If you notice the edit I added immediately I mention I'm looking out for the op. Id be upset if I was the op and someone was advertising another ROM in my thread. But yeah... Every phone I've ever had has been as I described. In fact... I've owned provably 20 android devices and never seen one that wasn't as described with regards to aosp. But... To anyone that's ever worked with lg source... Especially their kernels their software is a joke. I say this as a developer on a few lge devices. [emoji12]

Edit: with regards to lge source. In relation to Samsung, HTC, and Motorola (the only other ones I've worked with) there's is the most half-assed. I'll never own another lg because of this. Some of their comments are a joke... We used to joke that either they really were jokes or they grab teenie hackers off the street to work for them. Ive never owned a flagship lg device though outside of a nexus 4. Also I'm sure the op will understand considering it was MY emphatic review of his/her excellent work that has brought this recent influx of attention to this thread/ROM. Truth be told 80% of the AOSP Roms on the m8 are just cm builds with cherry picked merges of PAC/cm/DU. The OG PAC will always win by default because of this. Well that and I've been running PAC as my number 1 for 3 or 4 years. BTW... The above is/are my tip(s) for you. [emoji12]

PAC is by far the best AOSP 5.1 build. PAC, CM Nightlys, and DU are the cream of the crop here. IMO that is.

HTC One (M8) MultiRom: ViperOne + Hypernova Kernel & CyanogenMod 12.1.1 & PAC 5.1

Edit: I understand it was a clean install but there's nothing different (hardware wise) on the sprint m8. You're issue has nothing to do with your carrier. Carrier data only involves your radio info... Hardware is uniform across carriers. Outside of telling you to redownload/reflash I've got no ideas for you. An m8 is an m8. Your screen is the same screen that's on a Verizon, T-Mobile, AT&T, Cricket, US Mobile, any other us carrier.
[One (M8) Android Development] fizbanrapper:
No worries. You didn't realize I was the OP. Glad you're the kind of guy who will step up and say something when you think someone is being disrespectful. Too many people are hesitant to assert themselves.

They're definitely coming back, but it's definitely going to be different. They've reorganized and there are even fewer devices "officially" supported, almost exclusively Nexus. It's going to make AOSPA-L an even more component than it had been in the KitKat days. To me this appears to have the markings of a group who is determined to focus on actual innovation and doesn't want to be bogged down by the little changes to make it every little thing work with every app on every device. Getting those features to actually work on other devices, will fall on AOSPA-L's shoulders.

No kidding man! It's so important that proper terminology is used, but the average user does a really poor job of it. It's not their fault either.

This is also posted for the benefit of others who might be reading. The average user isn't going to bother with examining github activity to see that I haven't really created anything innovative. With my prior device, I forked CM's kernel, then cherry-picked a hundred or more commits from a bunch of other sources. It's something that's unique and took a ton of time and hard work, but that doesn't mean I was "developing". I'm not sure if contributor is even the right word, but it'd be closer.

For those of you who aren't sure, development is when you say to yourself "I bet I could do X" and then you write the code to make it happen. It doesn't count if X has been done on another device... that's not innovation. Creating something totally new is development. The code need not be 100% new, but the portion that isn't new should be cherry-picked so that proper authorship is maintained. To make up an example to illustrate, let's pretend that 5% of the heads up notification code (our development in this case) actually uses code from Omni's recent app switcher and 2% is from paranoid's PIE feature. Heads up is obviously an innovative development even though it uses some code from other ROMs.

Literally the only time I've ever heard of this is when the wrong multirom zip has been flashed. You've most likely flashed an experimental v32 build. Download the multirom manager app and install v31 from there. All should be well after that.
[One (M8) Android Development] jcole20:
Very well spoken and exactly what I was insinuating with my post. Well said. Ive been building Roms off and on for 4 maybe 5 years roughly. In that time I've compiled several kernels and Roms and created several modified roms. I can build anything... But when it comes to actual developmental coding... I'm lacking for sure. I'd love to take the time to truly learn the languages necessary but it's hard given my work schedule. Because of this I have to step back but i choose to show support for those who can do what I can't. If one was to go through my comments its clear who and what I support. I want to again thank you for your superb work and bringing my favorite ROM to the m8 [MENTION=4550510]5.1[/MENTION]. Seriously... Thank you! I truly appreciate this ROM and you bringing some more clarification to the conversation.

HTC One (M8) MultiRom: ViperOne + Hypernova Kernel & PACman 5.1

Edit: I've owned a g2/nexus 4/and nexus 5 previously. After reading your last post and seeing the difference in what's sought after on non nexus devices (with regards to the m8) this will likely be my last non nexus device. I love HTC as a company. The g2 didnt really encompass the attention to detail HTC puts into not just their devices software but hardware too. Samsung is a great company but when it comes to the actual attention to even the minor attention to detail with regards to hardware HTC has them beat. HTC makes quality hardware. I've wanted another HTC since my g2. When Verizon offered me the m8 for free a month ago I jumped on it. This is a tremendous phone but from now on in going to be strictly nexus. After the 4 and 5 I said I'd never go back to a non-nexus device... But a free m8 was hard to pass up. But anyways, nexus is definitely geared more to the eclectic power user. And with CM/newPA/newAOKP/DU geared towards it... How can you go wrong?

One more small note: I can't remember the device but HTC went so into their attention to detail that (this was 3 maybe 4 years ago) they paid an extra 15c a unit to have the interior plastic painted red to match the outer colors. This is a part of the device that will not be seen by 99.99% of the market and they still invested that much into detail. That is what made me respect and fall in love with HTC as a company. I believe it was one of the evo family or perhaps sooner for those interested.
[One (M8) Android Development] dopy25:
That's interesting. I am using the v32, but I did not know it was experimental. I used CPTB's v32(April 21) and his TWRP 2.8.6 (April 22).

I gotta hand it to you, that was the issue. I downloaded v31 and flashed it, and have no touch issues. Captain is mostly retired but I will try to let him know that his v32 has touch issues on secondary roms.

Thanks for the advice. (And rom now that I can use it).
[One (M8) Android Development] jcole20:
Found your slim builds and am downloading now. I've always been a huge fan of PAC so it'd be hard to pull me away from PAC. Good thing we have multirom.

HTC One (M8) MultiRom: ViperOne + Hypernova Kernel & PACman 5.1

Edit: After running slim I believe if I was shooting for a raw aosp experience slim>aosp but between slim and cm or slim and pac.... I'd choose PAC or cm over slim. I love choices though so it's definitely worth a try. I'd pick slim over xenon but I'm always going to choose cm aosp over raw aosp.
[One (M8) Android Development] kuceens007:
nice rom,but i have strange sound when listening music on speakers,when you turn up the wolume it starts to rattle
[One (M8) Android Development] jcole20:
This is normal for aosp builds. Viper4Android helps reduce these issues. V4A improves on the overall sound quality of the device both over speakers and via headphones. However, the speakers will not sound as good as stock sense. If you choose to try/use v4a understand you must set selinux to permissive. You can either use selinux mode changer available here on XDA or set it with terminal via su then setenforce 0. Good luck.

PS... I saw where he's apparently corrected a lot of the sound issues in his SOKP build. Perhaps that may better suit your needs/wants or maybe he can bring his code over to PAC in an update.

HTC One (M8) MultiRom: ViperOne + Hypernova Kernel & PACman ROM 5.1
[One (M8) Android Development] fizbanrapper:
FYI - I can say with certainty that there's been improvement in my own device, but that the bug is still there. Others have similar results, but some did not see any improvement.

I've only modified the cm_m8_defconfig file in the kernel so far.

My logic is as follows - I don't have access to proprietary code and likely never will, but I do have access to the source Sense kernel. Seems rational to start with the kernel to me. So instead of actually changing any code, it seems wise to first start by looking at what features are "turned on" in the Sense kernel, then as best I can, turn those same features on in the AOSP kernel.

I've got to make a few small changes at a time, because all it takes is one change to ruin the build. I also fully understand that a ton of changes were made to the actual Sense C files being compiled, which won't be picked up by the changes I'm making to the defconfig. Those are going to be really hard to find since there is no commit history to the Sense kernel sources. I'm picking the lowest hanging fruit at the moment. There's the added layer of uncertainty in that adding CONFIG_X=y doesn't mean that "X" actually even shows up anywhere else in the kernel source... so I'm sure that there are a lot of things I'm turning on that are actually not even there! I'll do some greping (?) later to try to identify those, but that's going to be a slow go.

I'm also not just changing the configs that are clearly audio related, but I'm also changing WiFi and other media configs as well. I'll be incorporating all of these changes into PAC builds soon.

And don't worry folks, I"m testing these on my own device before posting!
[One (M8) Android Development] jcole20:
[MENTION=5676253]fizbanrapper[/MENTION]

You're doing exactly what you should be. That's not just experienced development but common sense. I commend you for having a brain and not just blindly modifying as we see quite often in early developers... Hell I was guilty of it when I first started. I would compare against devices with the same chip set and blindly sync the two without knowing the why of it. I've been out the game for a few years so I've been quite standoffish with trying to compile/build again. You all are so far beyond (now) what I was doing (then) that I'm intimidated too... And I'm sure you understand that that's hard on my ego to admit. But as I've been learning the m8 scene I've found a few developers that I really admire and appreciate their work... You being one of them. All I can do is thank you for your dedication and your work. I love your builds.

With PAC the only stability issue I've found thus far has to do with LTE not enabling occasionally after toddling Wi-Fi. It doesn't happen all the time so it's hard for me to repeat but once it happens I cannot get LTE again until I do a full reboot... Soft doesn't correct it nor does toggling cell signal on and off (with airplane mode). I know the above is a long paragraph but I hope you can detect my admiration and respect and believe me I'm not criticizing you in anyway with any of my posts here. Believe me you're one of my favorite devs on this device. I have to thank you yet again for all your work and I look forward to anything you release in the future.

HTC One (M8) MultiRom: ViperOne + Hypernova Kernel & PACman ROM 5.1

Edit: and yeah we won't ever see the proprietary code... I think on an old Samsung device years ago we had fluked into getting the proprietary data (by we I mean we the developers at androidarea51.com) from Samsung but that was a one time thing and it allowed us to bring a great cm7 build to the phone but we never got propriety source again. I believe it was the Samsung precedent but it has been so many years and I've had so many devices I don't remember.
[One (M8) Android Development] clippy83:
Awesome ROM
[One (M8) Android Development] clippy83:
Found a small bug I tried to change my ringtone through audiko app and it won't change it. It says ringtone changed but when I go into settings it is still the same one
[One (M8) Android Development] fizbanrapper:
You really are too kind. It's helpful to know that hard work is appreciated. I'll try to provide a more complete response when I get a chance, but in short, I'm working on some of these issues and am not the least bit offended by anything you've said. After all it's more important for me to know what's broken than what's workin. Reporting issues is appreciated.
[One (M8) Android Development] fizbanrapper:
I hope it's resolved in future builds. I wish I could say that it's something I'll be able to work on, but it will probably get fixed well before I get a chance to take a look. I do appreciate your letting me know though.

My #1 & #2 priorities at the moment are minimizing the AOSP audio bug, and getting official MultiROM support. I've spent a decent amount of time on the audio bug lately. I haven't fixed it, but I think it seems better. I've picked the lowest hanging fruit, as best I can tell. Now I want to refocus on MultiROM and get that across the finish line.

My plate is pretty full. In addition to the above, I'm compiling 4 ROMs (3 of which are public on my AFH) while serving as an outsourced part-time CFO/Controller (situation-based) for 8 Non-Profit clients while also attempting to be a reasonably responsible dad. I'll get it all done, but might not be an ideal timeline. Sorry!
[One (M8) Android Development] Shamestick:
Have you read the multirom OP on how to use it? Or are you having more of a specific issue?
[One (M8) Android Development] xtcislove:
I cant find something about mounting the sd card.

I think this is a discussed error but i cant find it
[One (M8) Android Development] Shamestick:
If you're using v32 (from app) then ROMs installed as secondaries (at least aosp ROMs, I haven't tried any others in a long while) will have problems accessing storage. To make this not happen you just need to install the ROMs via the swap method. A search of the multirom thread should yield instructions on how to perform that, it's very easy
[One (M8) Android Development] PunkUnity:
I've installed it as primary and secondary without problems. This needs to be addressed in the MultiRom thread tho.

New build up. Unofficial with Candy Kernel. See my AFH
[One (M8) Android Development] amirfida:
Installed your latest build sonie of candy kernel running smooth so far :)
[One (M8) Android Development] sjpritch25:
I downloaded the vanir ROM from your site. Is it something you are going to start building? I'll let you know how it goes tonight. Thanks for giving us some updated PAC roms
[One (M8) Android Development] PunkUnity:
I can. But I forsee me being busy with Slim and PAC here pretty soon. That Vanir build was just for fun and is built with Candy kernel. But pm me and let's keep this forum on topic. ?
[One (M8) Android Development] ckvisme:
Yeah your Vanir build is pretty sweet.. Thx BTW

I haven't flashed Pac for a long time...

I gotta say Sonne Konig, your latest build is freaking awesome. this bad boy purrs like a kitten... and so many goodies?.

I also installed CM Neat theme.. Love it
[One (M8) Android Development] PunkUnity:
Working on building PAC with SaberMod. Almost done setting it up. Audio crap should be fixed soon. [MENTION=5676253]fizbanrapper[/MENTION] said he was getting a hold of someone about it. And I believe Candy kernel will be the default kernel as well soon... Stay tuned
[One (M8) Android Development] amirfida:
#Hype #Excitement :D
[One (M8) Android Development] fizbanrapper:
Nightly builds are targeted to resume this weekend.

The next nightly build after this is merged in

http://review.pac-rom.com/#/c/11880/

will be built with candy kernel... and every nightly thereafter.
[One (M8) Android Development] PunkUnity:
Nice. And the audio?
[One (M8) Android Development] amirfida:
Hey sonnie if ya don't mind i would like to contribute help and build the rom like you do, anyway you can help me kickstart it?
[One (M8) Android Development] PunkUnity:
Are you able to build something easy like CM already? If do hit me up. If not then I can only help you a little. There's guides put there that are pretty easy to get going with
[One (M8) Android Development] amirfida:
No i haven't tried anything like that, just saw that how much dedication you put there to put out new builds there ao i thought why not i should also try, i am aware of some basic stuff so i am not a total noob, just need someone like you to kickstart the things :D
[One (M8) Android Development] PunkUnity:
New build up.

Compiled with SaberMod 4.9.

https://www.androidfilehost.com/?w=files&flid=36760

audio may or may not have issues, let me know
[One (M8) Android Development] amirfida:
Does this include candy kernel and all the good stuff?
[One (M8) Android Development] PunkUnity:
Always includes Candy Kernel. But the audio might be weird on this build, not sure. Running another build right now with that audio commit reverted. Should help. I sent you a PM
[One (M8) Android Development] amirfida:
Ill wait for the new build then :)

I have replied to your PM :D
[One (M8) Android Development] PunkUnity:
New build up with that audio commit reverted. Should be a pretty solid build. SaberMOd-4.9 and Candy Kernel. As far as people having issues with the battery. I found that even on a clean flash, that my Ambient Display is switched to ON by default. Make sure ambient display is off and hopefully that will solve at least part of the battery drain issues. Thanks guys.
[One (M8) Android Development] fizbanrapper:
Hi guys. If you're building unofficially, just add this file to your local_manifests folder to fix CM audio (until CM fixes it for real, anyway)

This fix should work for any CM or AOSP based ROM that uses CM's caf sources and tracks CM's device tree.

http://pastebin.com/9PniuHuU

Please don't repost the above link. Please link to this post instead

http://xdaforums.com/showpost.php?p=62247716&postcount=401

The ONLY reason I ask, is so that people know who to contact in case they have questions.
[One (M8) Android Development] jxcorex28:
[MENTION=604283]Fiz[/MENTION]branrapper does file need to be compiled with the ROM, or can one extract any PAC build. Throw the file onto notepad++, rezip ROM zip then flash?
[One (M8) Android Development] PunkUnity:
one more. Last one from me until everything is fixed upstream.

https://www.androidfilehost.com/?w=files&flid=35897

Newest builds are under SABER-PAC.

My unofficial builds have Candy Kernel and are built using Saber-Mod-4.9.

I am going to try and get SM-5.1 to work again soon.

Thanks
[One (M8) Android Development] fizbanrapper:
You'd need it at compile time. It actually switches out repos for the audio hal.
[One (M8) Android Development] sjpritch25:
Geez your killing me. Good thing on a crack flasher.lmao
[One (M8) Android Development] sjpritch25:
Okay, I flashed the latest & I'm getting numerous play store errors. I used tkgapps 0802. That might be the issue, but it hasn't happened on 3 other roms

---------- Post added at 10:00 PM ---------- Previous post was at 09:59 PM ----------

Play store services I mean
[One (M8) Android Development] reV17:
He probably should have taken them down for now until he fixed them but yes the latest Sabermod nightly will do that. Set Location to off and the error will stop.
[One (M8) Android Development] ckvisme:
I flashed 8-9-15 build (by Sonne Konig) and I didn't getting any errors, but it wouldnt download from the play store (just clocking ) , so I cleared cache and data on play services and the play store then rebooted ...it's all working as it should now.

Also the sound on max volume is a little rough (but its also VERY loud...so I'm wondering if the sound issue at least on this build is just from the speakers not be able to handle that many decibels ...*1 step down from max sounds great)

I'm using PA GApps

Sprint m8

Thx for the build ☺
[One (M8) Android Development] amirfida:
Dude flashed latest nightly of saber PAC and sound is messed up :( please have a look