yashsingh1/xdaforums huggingface dataset:
[One (M9) Android Development] darkoj2007:
Sdk22 or sdk 23? Maybe its stupid question but dont want to flash the firmware again and again. Thank you very much :)
[One (M9) Android Development] iggdawg:
SDK22. I believe 23 is for 6.0
[One (M9) Android Development] dlads:
I have a guide in the themes and apps section. Could be the general section, can't remember. I Have had it working before. No issues. And yes on this ROM.

Edit: here it is http://xdaforums.com/showthread.php?t=3120711
[One (M9) Android Development] markjh:
New build works great, but smart screen isn't working. GSM that is.

Gesendet von meinem HTC One M9 mit Tapatalk
[One (M9) Android Development] BazmanFoo:
Anyone else back to having BT issues on the latest GSM build? Can't connect to my Moto 360 again and also getting No SIM Card error after reboot.

EDIT: Also, anyone know if the new C-Apps Packages are compatible with this ROM? I assume they are?
[One (M9) Android Development] eminembdg:
I use my 360 everyday, no Bluetooth issue. Also no SIM card issues
[One (M9) Android Development] BazmanFoo:
Are you using the GSM build from Nov 21st though?
[One (M9) Android Development] TLK3:
Anyone else have problems with the 'back' navigation key not always working unless a double press action is assigned? Even though the double press action is not being activated?
[One (M9) Android Development] dincdoes.me:
Couldn't wait for BT fixes I missed this just bought a an aid cable only use bt while driving for music.

Can't remember if it was this rom or the now official cyanogenmod that I was having issues with talking while on speaker phone.

Keep up the great work!!
[One (M9) Android Development] Rogi1997:
Is IR working here?

Gesendet von meinem HTC One M9 mit Tapatalk
[One (M9) Android Development] rc420head:
Should be

------------------------------------

CandySiX coming soon
[One (M9) Android Development] artizanoil:
I am unable to connect to LTE, I only see it once in a while. I am on the newest GSM build. Network is always going from H to H+ which is slow to keep connecting and disconnecting. I am with Bell Mobility Canada. CDMA / EV-DO (3G): 850 / 1900 Bell LTE (4G): 1700 / 2100, I just went back to stock and it works fine in LTE Now. Do I need to use a different build? T-mobile or Sprint or enable something else on the GSM Build?

Bell (including Virgin Mobile, PC Mobility)

2G

CDMA 850/1900

EVDO 850/1900

3G (and fake 4G)

HSDPA 850/1900

HSPA+ 850/1900

UMTS 850/1900

WCDMA 850/1900

1x EV-DO CDMA2000

4G

LTE 1700

Edit : I figured It Out

I created a APN and put in all the settings manually and it works perfect now. Even though the APN was already there I used my custom one now
[One (M9) Android Development] Rogi1997:
For me it don't work[emoji51]

Gesendet von meinem HTC One M9 mit Tapatalk
[One (M9) Android Development] rc420head:
Ok I'll look into it

------------------------------------

CandySiX coming soon
[One (M9) Android Development] artizanoil:
I just want to say I am really impressed with this this ROM. I have been using custom ROMs a long time with aosp being my favorite. These ROMs have always been buggy and missing a lot of features. Candy ROM is super fast, stable and simple to use. I was back on stock for about 10 mins and cannot handle it. Thanks a lot for all your hard work and such a amazing ROM.
[One (M9) Android Development] Rogi1997:
Thanks

Gesendet von meinem HTC One M9 mit Tapatalk
[One (M9) Android Development] S2kT68m:
Could this help?

https://github.com/task650/vendor_htc/commit/d5403819db93aa1e2865b5c36e8c432d6c22eed7
[One (M9) Android Development] rc420head:
Oh thats what I missed was the libs, I got the cir app but forgot the libs... Derp Thanks

------------------------------------

CandySiX coming soon
[One (M9) Android Development] weinberk:
Multi-Carrier??

I'm eager to give this a whirl. I'm coming from a Verizon M8 (and Verizon M7 before that, and Verizon Dinc2 before that). All have previously run CM, with my current M8 running nightlies (and doing just fine). Thanks for all of the hard work that it's clearly taken to make AOSP / CM a possibility for VZ M9 users. :good::good:

Questions:

1) Multi-Carrier

I know I am supposed to download the Verizon specific version to get this working on my VZ M9. Does this mean that other carriers won't work on the phone? On occasion, I'll toss in an international sim into my M8 when I travel (say for inexpensive data in Mexico). Last year, this worked great without changing anything other than (I don't remember) the APN settings. Now that the M8 is being retired and replaced by this M9, I'd like to continue being able to do a sim swap without having to flash another ROM in the event of travel or simply wanting to use another domestic SIM in the US. Will Candy5 let me do that?

2) Basic CM question (a bit off topic)

I'm assuming that the CM versions here https://download.cyanogenmod.org/?device=himaul won't work on Verizon like the generic M8 ones do? I can't find much of anything saying one way or the other.

Thanks again
[One (M9) Android Development] dom_mnml:
is there any option to activate the arrowkeys while tiping??

maybe i'm to stupid to find it ^^
[One (M9) Android Development] Rogi1997:
Is there a flashable file of candy5 kernel?
[One (M9) Android Development] philicibine:
I extracted and flashed the boot.img
[One (M9) Android Development] rc420head:
1. I'm not sure of you flash the gsm it will work with gsm sim, I believe the zip won't flash as it will say "your flashing himaul zip you have himawl"

2.cm only supports gsm at this time

------------------------------------

CandySiX coming soon
[One (M9) Android Development] weinberk:
Thanks RC-

Last night I tossed an AT&T sim into my VZ phone. Voice worked fine, but I got no LTE and no data even on 3g. Didn't have much time to test further, but I know that trying to flash the current CM GSM version won't work on the himawl.

We know that it's possible to have a "universal ROM" where multiple carriers are supported. CM did it with the m8 and (I think) Viper did it for the m9. CandyRom has the different roms for different carriers based on CM. Clearly at least one dev at CR knows the differences between what's needed for each carrier. Does it make any sense for a CR dev to use that knowledge to look at how CM did the universal thing for the M8 and translate that logic to the CR m9 source to make a universal CR? I can't be the only one who has the need to switch sims, and it would simplify distribution too - one rom for all. Just kinda thinking out loud here, but I feel like it would be a benefit to all.

Last, I stumbled on your (or what I assume to really be your) unofficial cm12.1 build for the himawl from Nov 18 https://www.androidfilehost.com/?fid=24269982086998847 I can't find a thread on this though. Can you confirm this is yours? Bugs? Can you shed any insight on what you changed from the official himaul version (GSM) of CM to get this to work on the himaWL?

Thanks so much for your time. Happy thanksgiving!
[One (M9) Android Development] rc420head:
No I don't have a thread for my cm-12.1 builds, it has working BT.

As for using Verizon build with gsm sim I think if you switch the build.Prop with gsm one it might work, I'll make a Flashable zip for you to try

------------------------------------

CandySiX coming soon
[One (M9) Android Development] weinberk:
Please let me know if we start getting too OT here....

So you are also doing plain non-Candy CM12.1 builds for the Verizon M9? Seems like that would be a very valuable resource for the community if made more public. CandyRom is cool as far as I can tell, but I haven't used it enough to know if it's for me as a daily driver, so far, so great. I am missing being like being able to update with CM nighties when I feel like it, I can add some of the tweaks on my own, and I worry about not having universal carrier support as a VZ user.

I'd love to know what you're doing to get the GSM source modified to work on VZ. If it's just some build.Prop changes, build, and flash, I wonder if we could have a universal ROM sooner than I expected.

Maybe some kind of switcher app to change build.Prop on a working phone? CM12.1 on the m8 just does the switch automatically, but I definitely don't have the necessary experience to even begin to guess at how. The build.Prop in the m8 zip says "ro.carrier=unknown" fyi. (also just noticed that MM is available for the m8 now - of course just a couple days after I moved to the m9...)

My gut tells me that it this auto switching functionality exists in the CM version for M8 that it should be able to exist for the M9 too, but clearly there's a reason they didn't do it - maybe lack of demand or something's very different. I have faith the [ if I keep basically saying the same thing over and over :o ] one of the devs here will just say, "oh that's easy, I'll just do it."
[One (M9) Android Development] rc420head:
There will Not be unified builds, cm has said they will no longer be doing that

------------------------------------

CandySiX coming soon
[One (M9) Android Development] weinberk:
That's a shame. Did the CM devs indicate why is? To be ale to switch carrier technology without having to reflash was awfully nice.
[One (M9) Android Development] calebcabob:
Kernel

Until [MENTION=5795145]javelinanddart[/MENTION] and I can get Candy's hima kernel to behave a little better, you may wanna check out the latest Smoocha kernel, which I think is getting better and better! Thanks to [MENTION=1986924]chadouming[/MENTION]!!:good::good::good:
[One (M9) Android Development] calebcabob:
Ya, too many conflicts brah. It's not happening.
[One (M9) Android Development] eminembdg:
Think I'll try that kernel out. Even with Wi-Fi off and scanning off Wi-Fi is showing to be constantly on in battery settings
[One (M9) Android Development] weinberk:
Breath unheld for universal.

I still wonder if the verizon version will work on LTE/GSM with an overseas sim when out of the US. No way of testing that, and when I have to travel I won't have the luxury of just being hopeful.... I'm a little optimistic being that I was able to get voice calling working here in the US with an AT&T sim with the VZ rom though.

Might you be able to put me in touch (maybe via PM so not to flood this thread) with the dev(s) who know what's different about each version of CR for the different carriers. Maybe it's just something that can be changed on the fly??
[One (M9) Android Development] weinberk:
2 things.

First a question for calebcabob. Is there a reason that the first post isn't updated with this new Verizon release? Is there a way for us to see what the latest release is without having to look through the whole thread or remember where we left off last? It doesn't seem like the 11/16 update shows up in the OTA app. Edit: found this- https://www.androidfilehost.com/?w=files&flid=36944 is that the best place to look? maybe link to that directly from the first page??

Second, I'll second the importance of VoLTE with Verizon. On my previous M8 when on Verizon's LTE network, I could be using it for tethering, a call could come in and I could continue being tethered with access to the net while talking on the phone, same is true of the VZ M7. However, it appears that to have talk and data concurrently on the M9 that you MUST have VoLTE. Read this: http://xdaforums.com/verizon-one-m9/help/data-calls-t3078739 (and other notes around XDA and the web).

Apparently we only have one radio in the M9 (or only 1 can be used at a time). With the m8, 2 radios could be used at once, one to carry calls over 1x and one for data over LTE. Without VoLTE there's no calling and data at the same time on the single use radio M9. Seems like a step backwards. Advanced calling sounds good, BUT if you drive out of an LTE area while on the phone, the call will drop unlike the M8 which would keep the call because it wasn't using LTE at all.

edit: found this interesting too http://www.droid-life.com/2015/03/1...e-and-data-now-works-on-nexus-6-with-verizon/ but note the edit at the end where it says you >might< need to enable Advanced Calling 1.0 in the web portal. boo for us who are in spotty LTE areas.
[One (M9) Android Development] weinberk:
Running the 11-16-2015 VZW release.

Firmware 3.10.605.7 (from dottat)

Did a factory reset from TWRP

Then installed Nov 16

At boot (and immediately after every boot, not just the first one), I get:

Unfortunately, the process com.android.systemui has stopped.

Had the Nov 3 version running before, installed the same way, without this issue.

Haven't tested much, but the system seems to recover from this error and looks great otherwise.
[One (M9) Android Development] bacon612:
In dialer, dial *#*#4636#*#*

Got to phone and scroll down. Select LTE/gsm Prl

That should work with gsm sims when u are travelling. Just make sure you switch it back when u come back to vzw.

Don't mess with anything else in this menu. You can screw up your radio.
[One (M9) Android Development] johnandbodhi:
everything here is running smoothly...candy v4.1 himaul 11/23 w chads kernel v1.5...question i have though is there any way to enable wake motions?
[One (M9) Android Development] calebcabob:
If you're talking about double tap to wake, or things like that, the answer unfortunately is no...not yet.
[One (M9) Android Development] calebcabob:
Ya, its just a bug right now. And ya, I believe it recovers completely after that first error...working on it.
[One (M9) Android Development] johnandbodhi:
thanks..no prob..everything is great here on my end
[One (M9) Android Development] eminembdg:
Yea, only once upon reboot do you get that system ui process stopping, it'll recover and be fine on it's own tough
[One (M9) Android Development] Jhonys:
If you try to skip songs using on screen buttons then it crashes every few songs you skip.
[One (M9) Android Development] calebcabob:
Hmm...OK thanks
[One (M9) Android Development] scott7175:
Do I need to switch the apn to get data on tmo m9 also Wi-Fi doesn't work on my end
[One (M9) Android Development] TLK3:
Or it could be a theme issue. Resetting to default system before flashing new version of ROM might be helpful. Or if you've already flashed, check for theme updates, else switch themes. Worked for me.
[One (M9) Android Development] eminembdg:
Thanks. I haven't used any themes though
[One (M9) Android Development] Conkreet908:
Guess I am not only one with this issue but my WiFi works fine. I am able to make calls but no data access through T-Mobile.
[One (M9) Android Development] weinberk:
Back button

11/16 rom. Latest firmware. Verizon

I can have a long press of the back button FC / kill the current app by setting this in Candy Interface, navigation bar, long press. If that's set, it works, but I have to double tap back to perform a regular back.

If I set long press to "no action", the the back button works with a single tap, but long press don't force close the current app. I have also tried the dev mode settings to long press kill, but that didn't work- I am guessing that Candy's navigation button setting is intercepting the command.

Anything I could be doing wrong / anything I can try?

Thanks
[One (M9) Android Development] scott7175:
I got it working I switched the APN to the T-Mobile ipv6 and for the WiFi it was my bad I fat fingered the password
[One (M9) Android Development] lilhaiti:
Try setting back button kill app in Developer Options and see what happens.

I don't have that problem btw I am just giving you other options to try.
[One (M9) Android Development] weinberk:
I had already tried wit the back button long press setting in Developer Options both on and off. BUT - your post gave me an idea - thank you. I turned of developer options altogether and POW it started working normally once I reset he navigation bar buttons to FC the current ap.

And to test, I turned developer mode back on (without changing any settings within it) and the back button required a double tap to go back again.

Super minor problem and totally fixable by disabling dev options, but it does sound like a bug...
[One (M9) Android Development] rc420head:
Yeah the dev option shouldn't be there. I'll remove it

------------------------------------

CandySiX coming soon
[One (M9) Android Development] weinberk:
But wait, the Dev Options are useful / necessary....

For example, how else can you turn ADB debugging on and off? If my memory serves, Candy5 comes with ADB debugging turned on (isn't that pretty dangerous???). No biggie, I can just turn it off >>in Developer Options<<

I feel like you should leave the option or those of us who want to enable developer mode the option to do so. Instead, maybe we can figure out why the back button doesn't work if navigation bar button options of long press back to FC is enabled? Or just make it an accepted thing that if you leave dev options ON, then back needs double tap to work if FC is enabled on long press.
[One (M9) Android Development] rc420head:
Lol no just make long press to kill not show in dev options

------------------------------------

CandySiX coming soon
[One (M9) Android Development] weinberk:
Ah, that makes more sense, but note that it doesn't matter if long press kill in dev options is enabled or disabled. Either way, if I set long press back to FC in Candy5's navigation bar options and if dev options is ON (not the long press kill, but dev options in general), then I get the double tap of back requirement. Turn off dev options (at the top of dev options to make it go away from settings altogether, then back long and tap operations are normal.
[One (M9) Android Development] andybones:
Verizon Wireless latest 3.10.605.7 firmware, Long press back to kill working fine here.

Great job on the ROM!
[One (M9) Android Development] Conkreet908:
I can confirm that it works. You Rock
[One (M9) Android Development] weinberk:
That's because you're a deity and the rim is petrified that you'll tear it apart of it doesn't work for you!:laugh:

Mine stopped working again with dev options completely disabled. I have to double tap back to kill. Thought I had gotten to the bottom of it, but I guess not. No setting changes between it going from working and not.

Curious Andy, are you getting back to kill working using the dev options or with Candy's navigation bar options, and if with the latter, are dev options in general enabled? Thanks
[One (M9) Android Development] andybones:
In the Candy nav bar options.

I suggest for the time being to use long press home to kill apps?

I do notice that when I have love press back kill app off that it does click out of apps faster than when long press kill is on.

So I may be have the issue you are describing but not as badly or noticibably.

Can you back out of any app or do you have to double tap every single time?

I have noticed in some apps it will take 2 taps, but this is very rare, and I did move it to long press home to kill apps for the time being.

So, I am having the issue, but not the one I thought you are having which from what I read is you can't even back out of anything.

For example with long press back 2 kill on I can tap once and get out of playstore everytime. but in root explorer, some times it will take a double tap so I moved it to home long press to kill for now

:)
[One (M9) Android Development] weinberk:
As soon as I sat home long press to be FC I started having trouble just single clicking the home button, basically the same issue as with back.

it's not all of the time, but it is most of the time I'd say. I've done it with the stock email client with exchange, Facebook, photos from Google, the camera built-in - sometimes those apps go back just fine sometimes I have to double tap to go back . It's not the end of the world or anything, but it is an annoyance, and I know we're striving for perfection here :)

While we're talking about this area of the ROM, I'm confused by the long press delay option on that screen. It says more delay or less delay, but I can't figure out which way I would slide the slider to have it be less sensitive i.e. I would have to hold it longer for it to work . I see no difference between having all the way to the left and having it all the way to the right
[One (M9) Android Development] andybones:
if you want it to take long to kill the app you slide it to the right for more delay. is you want it to kill app with less time, well slide it to the left less side.

(slide it all the way to the left less side and kill an app, then slide it all the way to the right and kill an app you will see the difference)

:cool:
[One (M9) Android Development] weinberk:
Pandora

I can't get Pandora to play any music! Verizon, latest 3 kernel, Nov 16 ROM.

The app launches, and I'm able to log into my account. I see my playlists and settings. Once I choose a station a song comes up, end it appears to try to play but it just sits there after a few seconds it goes to another song no audio. It'll keep doing that until it hits an ad . The ad does play. then the whole cycle repeats itself.

I have not spent a lot of time on this, but I know I haven't had Pandora working yet with this wrong. That includes re-flashing for another reason. note that xposed is installed and running along with xprivacy. I disabled Pandora restrictions as a test . That didn't make any difference, and I'm not surprised since ads do play.

Anyone else? Any thoughts on what I might be able to try?
[One (M9) Android Development] redwood02:
Confirmed here, vzw, 20151103 build, no xposed or xprivacy. Same behavior with Pandora. FWIW other music apps seem to work normally.
[One (M9) Android Development] EvoGuy2010:
The issues is probably codecs and it hasn't been fixed on the CM side for a while. Sprint variant has been facing this issue along with its inability to play html videos online. That said, your best bet is simply waiting for candy 6 or just flashing back to Sense. Heck, this rom would be my daily driver for a while now if it was perfect in functionality.

[No one ever gives me the thanks... Make my thank meter not be 0 at least lol]
[One (M9) Android Development] 123421342:
Where are the updated gsm builds? Buildbasket only shows from 11/3
[One (M9) Android Development] dom_mnml:
candy5 2015-11-21
[One (M9) Android Development] scott7175:
https://www.androidfilehost.com/?fid=24269982087001484
[One (M9) Android Development] calebcabob:
I've got a new Verizon build I can post, but I'm not too happy with the kernel...that's why I haven't posted it yet. But if you guys want to use a different kernel with it, I can link u.

EDIT: It has another Bluetooth fix
[One (M9) Android Development] calebcabob:
How goes the Fluent ROM building? Taking a break for a bit? ;)

It's very nice to have you here:good:
[One (M9) Android Development] repl1ca:
New Sprint build from the other day: https://www.androidfilehost.com/?fid=24269982087008660
[One (M9) Android Development] jtommyj:
I'll give it a try for sure. What kernel would you recommend?
[One (M9) Android Development] andybones:
Still going well, but yea def a much needed break from Sense for a bit, very nice to be here, amazing job on the ROM!
[One (M9) Android Development] calebcabob:
I'll run and post a build in a couple hours with some new kernel tweaks.
[One (M9) Android Development] dbarrett480:
anybody else having issues with a system ui force close after reboot?
[One (M9) Android Development] Rogi1997:
[emoji121]

Gesendet von meinem HTC One M9 mit Tapatalk
[One (M9) Android Development] BazmanFoo:
Its been reported many many times. They're working on it. Not a huge priority I'd imagine since its not a big deal for most of us
[One (M9) Android Development] calebcabob:
New Verizon build!

•SystemUI FC upon boot-up (think I fixed it...hopefully)

•Kernel tweaks for better battery

•Bluetooth fixes

candy5-release.v4.1-20151202-OFFICIAL-himawl.zip

EDIT: Recommended kernel settings:

Big cores - Conservative (already default)

Little cores - Power Save

I haven't noticed any lag with these settings - and battery life seems way better now:)
[One (M9) Android Development] frankinstine:
SystemUI FC on gsm rom startup, great ROM running good... On 11/21 build
[One (M9) Android Development] calebcabob:
I'll run a new GSM build later today