yashsingh1/xdaforums huggingface dataset:
[One (M8) Android Development] RevPhoto:
Kernels

Anyone successfully using any other kernels with this rom? I was looking at Excalibur but it seems it doesn't work so I was wondering what might?

Thanks, awesome ROM guys!
[One (M8) Android Development] crazyvash1:
Maybe i will have to reflash and try again. For me data would just cut out it would just show bars with "!" on it even a reboot wouldn't fix it.
[One (M8) Android Development] mattie_49:
I clean flashed and haven't seen that issue with this rom.. 5.1 minimal gapps and xposed and about 10 modules active as well.
[One (M8) Android Development] mcwups1:
Really? How do you toggle sound? I have to do it through power menu.

Also, this has been on a few ROM'S I've tried, but when phone is at 100%, the green light turns off.

Sprint M8 Converted HK 4.25.654.14
[One (M8) Android Development] mattie_49:
My volume buttons up and down. Not sure if that's what you mean
[One (M8) Android Development] kerryh420:
Hi,

I have firmware 4.17..605..5 (verizon) and android version (which I am pretty sure) is 5.0.1. I am unclear if I am able to flash this (or any other) ROMS That are based upon 5.1.X. Previous experience and logic say no, but I can't tell from reading some of these posts if some users are on 5.0.1 or 5.1.x . Do I need to upgrade to 5.1x ( I assume done with the OTA update)?

So to clarify my question(s):

Can I flash this ROM being on 5.0.1 RUU? OR, do I need to be on 5.1.x?

My understanding is that once you upgrade OTA you can not revert back...(ie: go from 5.0.1 to 5.1.x) can anyone confirm if this is True or False? (this is my first HTC, all my other exp is based off of motorola where the reverting was not possible)

Maybe it's just my imagination but, I am seeing more emphasis put on the build (or OS) number rather than the android version number...(ie: build 4.17.604.5 vs 5.0.1, or 5.1.x) Does this come into play when flash this particular ROM?

Thanks you guys
[One (M8) Android Development] nightcervant:
Guys that you used your camera to take pictures? The Google Room does not inspire me just ... : /
[One (M8) Android Development] Roarmaster:
For the second issue, I like to use a third party app like lux auto brightness that adjusts screen brightness depending on the amount of ambient light. It also has an auto night mode that tints your screen to warmer colours after sunset to make it easy on the eyes. Definitely one of my favourite apps :)
[One (M8) Android Development] GohanBurner:
Anyone else know why the notification light no longer lights up when new notifications come through? It still vibrates, but no light indicator. Anyone else having this issue?
[One (M8) Android Development] massaquah1:
Yes, I had issues with the notification light since the beginning (stock rom and Viper rom).

I solved it by using Light Flow.
[One (M8) Android Development] mcwups1:
Just curious...

How can I make pie look normal?

Sprint M8 Converted HK 4.25.654.14
[One (M8) Android Development] PippoX3:
Yep, seems not good... Unfortunately latest CM changes did messed all the stuff... But actually can't do any...I'm off until 6th August, then I'll take a look... Sorry.

Inviato dal mio HTC One utilizzando Tapatalk
[One (M8) Android Development] PippoX3:
Recently CM revert proximity check on incalls, then I was forced to remove another proximity patch too...But effectively its worst than before... I'll fix next weeks.

Inviato dal mio HTC One utilizzando Tapatalk
[One (M8) Android Development] dnkjordan:
Seeing some weird behavior this morning. I am unable to select some options on popup screens. Some apps won't let me authorize super user and when I try to manually install an apk I can select cancel but not install. Any idea how to correct this?
[One (M8) Android Development] Roarmaster:
Are you running any screen filter apps? Since I run lux auto brightness, I had to temporarily disable it in order to install apps and give superuser access. Although, ever since the new lux update, it seems to disable itself when installing apps or asking for root.

Edit: by disabling lux, I meant pressing the lux power button on the notifications dropdown bar, not disabling the app itself.
[One (M8) Android Development] dnkjordan:
I actually just started using lux based on an earlier recommendation from you and that was it. Though I found a work around with SuperSU. If you uncheck tapjacking protection under settings, you can apply permissions with lux enabled.
[One (M8) Android Development] Roarmaster:
Ahh thanks a lot for this, sometimes lux is pretty buggy and wont turn off for me too :)
[One (M8) Android Development] ParaDoS:
Is there a way I can access the advanced USB connection menu? I am trying to use the USSD code, but nothing happens.
[One (M8) Android Development] dnkjordan:
Over the last few days I've started getting the stock voicemail indicator every time I reboot and periodically throughout the day. I don't use stock VM, all VM is routed to Google voice. I did call *86 to verify my queue was clear and it said there were no messages but this indicator persists, showing 3. What's interesting is that when I boot into my secondary ROM, I don't get the indicator at all. Any ideas as to how to clear the VM indicator?

Edit: Fixed by factory wipe and fresh load.
[One (M8) Android Development] MJPollard:
Is the M8 version of Carbon 5.1 still being updated? The last version that was released was 7/7. I tried to get it running all day, but it kept freezing up on me, so I went back to Carbon-KK. This is my main phone, and I need it to be stable and reliable. :)

I later tried to roll my own, thinking that some recent changes may have fixed the stability issues, but after fixing a few issues relating to the main repo (involving the CM Platform SDK) and attempting to lunch the m8 device, I kept getting this error:

fatal: Couldn't find remote ref refs/heads/linaro-4.9-arm-eabi

error: Cannot fetch ArchiDroid/Toolchain

I checked ArchiDroid/Toolchain on GitHub, and there is no "linaro-4.9-arm-eabi" branch, which I'm assuming is necessary to build the Furnace kernel. At this point, I'm stuck. :(
[One (M8) Android Development] Freak07:
Dev is on vacation :)
[One (M8) Android Development] MJPollard:
Can't fault him for that. :) I'm sure he'll dive back in once he's back and settled in again.
[One (M8) Android Development] jcole20:
I'll try to compile from the OP repo. See if I can get it to build properly.

I gotta wait for pac to finish though. I can't get Bliss to compile but cm and pac are building no problem. If I get carbon to build unofficially I'll link it.

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] walker164:
Anyone able to use NFC to use Google Wallet? I've been tinkering around with it at mcds and places for a while, but can't get it to even pop-up or register. Any ideas?

Thanks!
[One (M8) Android Development] PippoX3:
The things are changing... I'm leaving CarbonROM for various reasons, this is not the right place to talk about.

New sources are updated here now: https://github.com/CarbonTEAM and I'm gonna build a rom in next hours.

Thanks alls for your support.
[One (M8) Android Development] jcole20:
ah... yeah i was syncing with ~/carbonrom/ . I had the same issue as above. :thumbsup:

Edit: yeah i can't get either repo to build. not sure what you're syncing with but it just won't build for me.
[One (M8) Android Development] MJPollard:
Good luck to you, Pippo. Will someone else be taking over m8 development when you depart?
[One (M8) Android Development] gmoe65:
Is it me or the latest build has a July date attached?
[One (M8) Android Development] tuxattack80:
The latest build is still in the works notice the X in the date. It's probably best to be a day or so out especially since cm pushed out a commit to fix audio once again, fix should show up in tomorrow's cm nightly.
[One (M8) Android Development] gmoe65:
Thanx for the Reply??
[One (M8) Android Development] netvietcomputer:
I can't find link Carbon Rom 08/10/2015
[One (M8) Android Development] PippoX3:
I'll keep to support M8. But on my own platform, now (if u mean who will support M8 on CarbonROM... haven't idea. Maybe Simon still have it).

I don't agree to be dependant on CarbonROM, I like to work and learn in a team.

So I called my board CarbonTEAM.

New build out. All the latest CM updates.

You can dirty flash from my previous rom. Make a backup always first. Thanks.
[One (M8) Android Development] netvietcomputer:
great new build out!

Is this release rom?
[One (M8) Android Development] PippoX3:
I updated dependencies on device repo. You should better remove local_roomservice, repo sync and build again ('cause remote carbon too is changed).

Did no sense make a label like nightly or weekly, 'cause haven't plans or eta. So I decided, see an enough stable release, to print as RELEASE (C1 version).
[One (M8) Android Development] fizbanrapper:
Carbon splits? So like a carbon copy?

I joke, but you do some great work. Congrats!
[One (M8) Android Development] COMpulse:
Love this ROM. Thanks for all your work.

Only issue I've found with this ROM is I can't seem to disable "double tap to wake". No matter what, if I double-tap (or sometimes requires a triple-tap) my screen, it turns on. Keeps turning on in my pocket.
[One (M8) Android Development] MJPollard:
Still needs a little work. ;) (I think the branch needs to be "lp5.1.1", not "lp5.1".)
[One (M8) Android Development] PippoX3:
You have to disable using a third part app like ElementalX Manager or Kernel Adiutor.
[One (M8) Android Development] PippoX3:
You still need to type: "repo sync --force-broken". Because you are using same work folder used before. ;)

It's all working fine here.

And if not done already: remove roomservice.xml from local_manifests
[One (M8) Android Development] MJPollard:
Thank you, Pippo, but I did all that already. The only thing I haven't done is wipe the entire build directory and start from scratch, which is my next step (and no big deal).
[One (M8) Android Development] PippoX3:
Try as I told you the sync of sources, first.

The local roomservice (after lunch) should be:

<?xml version="1.0" encoding="UTF-8"?>

<!--Please do not manually edit this file-->

<manifest>

<project name="android_device_qcom_common" path="device/qcom/common" remote="cm" revision="cm-12.1" />

<project name="android_device_qcom_sepolicy" path="device/qcom/sepolicy" remote="cm" revision="cm-12.1" />

<project name="android_hardware_qcom_fm" path="hardware/qcom/fm" remote="cm" revision="cm-12.1" />

<project name="proprietary_vendor_htc" path="vendor/htc" remote="tm" revision="cm-12.1" />

<project name="CarbonTEAM/android_device_htc_m8" path="device/htc/m8" remote="carbon" revision="lp5.1.1" />

<project name="CarbonTEAM/android_kernel_htc_msm8974" path="kernel/htc/msm8974" remote="carbon" revision="Furnace_LP5.1.1" />

<project name="ArchiDroid/Toolchain" path="prebuilts/gcc/linux-x86/arm/linaro-4.9-arm-eabi" remote="gh" revision="linaro-4.9" />

</manifest>
[One (M8) Android Development] netvietcomputer:
Will be flash

:)
[One (M8) Android Development] COMpulse:
That did the trick! Awesome. Thanks!

Bluetooth music was pretty sketchy this morning. Going to make sure the Ford Sync system in my car wasn't flipping out, but I think it was the ROM. Previous build had BT working flawless.
[One (M8) Android Development] MJPollard:
It. Does. Not. Work. Not even after going back to a clean setup. Wiping the entire directory, initializing the repo:

repo init -u git://github.com/CarbonTEAM/android.git -b lp5.1.1

Syncing the repo:

repo sync -f

Then trying to lunch m8:

. build/envsetup.sh

lunch carbon_m8-userdebug (or just omit the parameter and select from the menu)

Still the same error, fatal: Couldn't find remote ref refs/heads/lp5.1, when attempting to fetch CarbonTEAM/android_device_htc_m8. My environment is fine, it builds other ROMs just fine. It's simply not working for CarbonTEAM m8. You say you have it working, fine, I believe you, but attempting to make a completely clean build from scratch simply doesn't work. If you're doing something different, please, enlighten us. :)
[One (M8) Android Development] fizbanrapper:
-f is not the same as --force-broken

That's where you're struggling
[One (M8) Android Development] MJPollard:
According to repo's own help screen, "-f" and "--force-broken" are exactly the same. But that's okay because Pippo fixed the issue (see the message below), it synced just fine, so it should be all good now. :)
[One (M8) Android Development] PippoX3:
Sorry. Should I found the matter: try to repo sync again (repo sync fine?). I forgot to update roomservice.py.
[One (M8) Android Development] MJPollard:
That's what I figured. ;) The fix did the trick, and everything synced properly, save for one glitch: device/qcom/sepolicy needs to be added to default.xml (it was fixed in the CarbonROM repo). Gotta wait until I get home before I can compile it (it's 30 minutes until "get the f**k out of work" time), but I'll let you know how it went.

I do have a few questions, if you don't mind my asking:

1. Is CarbonTEAM now the official Carbon repo, or is this your own personal fork? I wasn't sure based on your earlier post.

2. I noticed that there's a kk4.4 branch. Does this mean that KitKat versions of supported ROMs can be compiled using the CarbonTEAM repo (instead of using the old CarbonDev repo)?
[One (M8) Android Development] PippoX3:
Thanks for tip (fixed). Qcom-Sepolicy was removed (for how can remember) by Carbon "bosses" request, they wont devices on manifest...

Adds that repo (was a CM commit), not an our discover. 80% of what u see on roms are CM stuff.

1) CarbonTEAM is mine and is my official. CarbonROM is official Carbon. CarbonROM got a lollipop chance thanks by me. They ask me (see as my STELIX worked fine and like) to help them and I pushed all my source. In exchange of much decisional power on team trend and choices. So it wasn't. They decide, I code and no-one helps (sometime break!) .

2) My wish is to make available again the kk code for the possible devices. Recently I build for my devices and updated the kk code. But no-one in the CarbonROM team didn't want that. Isn't ready yet, but obviously you'll have to repo init manifest with kk4.4 branch.

Hope to have satisfied your curiosity! :laugh:
[One (M8) Android Development] mrrocketdog:
i didnt understand alot of that. but i vote for KK. :thumbup:

"all i can really do , is stay out of my own way and let the will of heaven be done"
[One (M8) Android Development] fizbanrapper:
--force-sync
[One (M8) Android Development] MJPollard:
Thank you, yes.
[One (M8) Android Development] yung40oz84:
ROM running amazing! Love the stability and speed! Awesome kernel! Great work with this ROM, keep it up!
[One (M8) Android Development] candleworth7808:
There are some graphical errors like dotcase apps showing when screen wakes, or old lockscreen notifications appearing before waking. Other than that, sweet ROM.
[One (M8) Android Development] decodertje:
+1

Great ROM thnx
[One (M8) Android Development] tuxattack80:
Great ROM!! Audio still seems to be a bit off compared to CM but still a very well put together ROM! Seems like it wasn't long ago I was running carbon on my i777 lol.
[One (M8) Android Development] PippoX3:
Differences between CM and that come from faux123 audio tuning patches. Other that, all identical.

Anyway NEW Build out. https://www.androidfilehost.com/?fid=24052804347794364

Changes are: all CM updates (like usual), include new

audio mixer patch,

Slim dim behaviour on navbar, wallpaper changer on lockscreen.
[One (M8) Android Development] tuxattack80:
Great build!! Audio mixer patch did the trick! :good:
[One (M8) Android Development] aaronpw0621:
In call Proximity Control

[MENTION=2837935]PippoX3[/MENTION] while in call the screen is still active. How do I activate the accidental wake (if is implemented) ?
[One (M8) Android Development] PippoX3:
If u mean while you approach to your ear, unfortunately prox sensor is tuned too much sensible. Feature is there, but need some adjustments.

Sometimes when is already covered by ear it wakes beacause not perfectly covered, less sensitivity is the way.
[One (M8) Android Development] ulmcity:
Kernel

Can i use any other kernel with this rom?
[One (M8) Android Development] aaronpw0621:
Yes I mean while I approach ear and while phone is touching ear while in call. You say needs adjustment. Can you explain how I adjust the sensitivity please?
[One (M8) Android Development] COMpulse:
NavBar dimming is pure win.

As someone with sensitive eyes, the NavBar brightness has always been a problem for me. Being able to colorize the icons was a big help. And now being able to dim the NavBar icons as well is even better.

Is there any way to make the NavBar background always black, instead of it colorizing to match the current app?
[One (M8) Android Development] kickassdave:
Proximity sensor wide awake during calls. A day at the office today making various calls to head IT and me completing various tasks while on the phone then being unable to hang up was not fun...
[One (M8) Android Development] PippoX3:
NEW Build out.

Includes: all the AOSP/CM updates, NavRing customizable, Slim recents.

Sorry for proximity sensor. I'm going to tune it.
[One (M8) Android Development] nightcervant:
Thx for update, whatsapp voice work now?
[One (M8) Android Development] PreslandBoy:
Great ROM! One problem...

I love the ROM, by far the best i've ever flashed. Only problem is that I can't seem to disable double tap to wake. Going into settings and disabling it seems to have no effect.

Save me from the endless butt dials! Thanks :D
[One (M8) Android Development] PippoX3:
You have to disable by thirdy part app like ElementalX o Kernel Adiutor (I'll remove option from display settings, useless).

NEW Build out 2015_08_19.

Changes: all the latest AOSP/CM updates, Proximity sensor can be disabled by InCall interface, and I merged some proximity sensor improvements. I'm testing this build since yesterday and I wasn't able yet to reproduce the prox sensor issue while call... let me know, please.

(I changed bootanimation, it's LP stock at 60fps)
[One (M8) Android Development] yung40oz84:
You are on a roll! And by the way, the builds are amazing! Been running as daily driver since the CarbonTEAM switch
[One (M8) Android Development] PippoX3:
LOL

[IMG="LOL"]http://inerdtia.com/wp-content/uploads/2014/11/LogoAlone@2x.png[/IMG]
[One (M8) Android Development] ccatalin:
Sorry for the noob question, now I'm running on release 20150814-1948 an i want to upgrade to 20150819-0644. I just dirty flash the ROM and the GAPPS or I need to backup and then restore.
[One (M8) Android Development] jxcorex28:
Just wipe dalvik and dalvik cache. There's no need to reflash gapps after a dirty flash. TiBu downloaded app,and not system apps. You'll get a ton of FCs
[One (M8) Android Development] dnkjordan:
Every time I dirty flash a new build I have to flash GAPPS again. This is the only AOSP ROM I've used that I have to do that with. It's only a minor inconvenience (and I flash the latest version of Banks GAPPS when I do)but it's annoying if I forget and have to go through the optimization step twice.
[One (M8) Android Development] TheNewNEXUS:
I had a huge bug on my verizon htc one m8 on the 8/19 build. As I was using it for a day, all was perfect except the proximity sensor. Then all of the sudden when I using my phone, this mysterious small circle appeared dead center in the screen. I was wondering what it was. It looked like there was a mouse pointer in there. I was shocked. I couldn't touch the screen. I turned it off. I hard reboot it. In the end, I had to format the data, and use an old back up.
[One (M8) Android Development] shawnaye:
CircleFright?
[One (M8) Android Development] victou42:
I used this rom for now a very long time, i do all the updates but everytimes i'm looking for the changelog without success, am i a noob or there isn't changelog ?
[One (M8) Android Development] jluva420:
Best no sense rom I ever used on my phone bro. All works amazing well but I seem to have a massive sleep drain while playing music. I come from Scotts Cleanrom 3 which I can go to bed with 40% and wake up with 34% of battery left. This one I went to bed with 50 woke up to a dead phone with 0 battery left when I plugged it in. Any suggestions would be great. I am on base from tigerstowns amazing work.
[One (M8) Android Development] MJPollard:
[MENTION=2837935]PippoX3[/MENTION], a scripting error might have been introduced recently. I synced up my source tree, and when I lunch/make, I keep getting this message:

/bin/bash: line 0: [: 1080_carbon: integer expression expected

It appears to compile successfully, but that message is odd. Just thought you'd be interested. ;)
[One (M8) Android Development] PippoX3:
It's just a warn. I temporarely renamed old bootanimation, waiting for move it.
[One (M8) Android Development] MJPollard:
That's what I figured (I remember reading that you'd changed the boot animation), but I wanted to make sure. Can't be too careful, after all. :)
[One (M8) Android Development] GohanBurner:
Is anyone building KitKat anymore? I have a KK Carbonrom from 6/20, wondering if there is any builds later than that.
[One (M8) Android Development] MJPollard:
I was building them for a while for the M8 and SGS3, but KitKat repo updates have pretty much stopped (and the few that have appeared for CM11 don't have anything to do with either device). See this post for links to my last Carbon-KK builds (dated 7/12), which is likely about as up to date as you're ever going to be with Carbon-KK.
[One (M8) Android Development] MJPollard:
[MENTION=2837935]PippoX3[/MENTION], hope everything's going well for you. I noticed that the CarbonTEAM repo hasn't been updated for quite a few days; I figure you've been kinda busy and haven't had the opportunity to do so (which I can certainly sympathize with!). I only mention this because it appears that some recent CyanogenMod code changes have broken the ability to build the CarbonTEAM ROM, and I've been itching to try to get it running on the Samsung Galaxy S3 (d2att). No biggie, I have nothing but time, I'm not going anywhere; just thought you ought to know about it. ;)
[One (M8) Android Development] lisaamybeth:
Hi just wondering if you ever found the cause to this ? Only thing wrong for me too. Appreciate a reply if you can find the time. Cheers
[One (M8) Android Development] vance74:
Battery issues.

I just came from another CM based Rom and I really love this one. One thing though it seems to be a heavy battery drainer. Will that stabilize after a few full charges and drains?
[One (M8) Android Development] vance74:
Does Furnace 1.1.2 work with Carbon Rom? I am just wondering if anyone is using it or knows if it's flash able over 1.1.1 included in this ROM.
[One (M8) Android Development] PippoX3:
Me and CarbonROM has joined again finding new targets. I moved all my stuff in a branch apart aboard of CarbonROM (take a look to https://github.com/CarbonROM/android/tree/LP5.1.1). Chris/MySelf5 is keeping update the official branch (lp5.1 with cm navbar), where you find the most updated stuff.

I'll update again branch LP5.1.1 (with slim navbar) next days. Thanks.
[One (M8) Android Development] MJPollard:
Ah, so then, you're saying the CarbonTEAM repo is now dead in favor of CarbonROM? Just wanted to make sure I'm understanding you correctly. :) Looking forward to seeing more of your work on the CarbonROM repo.

(Could you possibly persuade your other team members to include the navigation bar customization that you included in CarbonTEAM? It's far more flexible and sophisticated than the one in CarbonROM, which is still the one found in CyanogenMod. If/when that happens, I'll jump over to CarbonROM in a heartbeat.)
[One (M8) Android Development] PippoX3:
CarbonTEAM isn't dead, is joining to CarbonROM. I wish to join my stable base with the actual CarbonROM updates and new features (like multi window and others).
[One (M8) Android Development] Crackaf3tt:
Smooth ROM so far. My only problem is my phone waking up. I've turned off double tap to wake and yet it still unlocks in my pocket.