yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] DanRyb:
Are you using an adblocker? I forgot the name of the one but there's one out there that blocks at the traffic level instead of the hosts file. If you're using the one that "sniffs traffic" that could be your problem. I had the same issue and had to switch to an adblocker that works based on hosts file.
[One (M7) Original Android Development] prng:
I'm using adaway which I think is just hosts files. And it says it's disabled anyways.
[One (M7) Original Android Development] goldenratio:
MMS send/receive is working okay for me.

I can confirm adblockplus breaks MMS (it's easy to reproduce); I'm not sure about adaway.
[One (M7) Original Android Development] eHabaski:
Can anyone help me with this issue?
[One (M7) Original Android Development] varunpj:
Hi, im really enjoying cm 10.2, but the music coming out of the stereo speakers dont come out evenly. The top speaker(the one near the front camera) sounds much softer than the other one. Ive tested it using poweramp and apollo. Any fixes ?
[One (M7) Original Android Development] kennypow3rs:
I could be late on this but does applying the dark theme on cm file manager completely destroy the app and render it useless for anyone else?
[One (M7) Original Android Development] Ruku1994:
It's working fine here.
[One (M7) Original Android Development] mcinty25:
i was having the same issue till i flashed the latest nightly 10/04 and it works now

http://get.cm/?device=m7ul
[One (M7) Original Android Development] Bxsteez:
Is anyone else having an issue with GPS? I can no longer get a lock.
[One (M7) Original Android Development] fohdeesha:
on 10/04 I'm getting a lock like usual, are you on 05?
[One (M7) Original Android Development] Bxsteez:
I'm on 05. I'll give 04 a shot and see if I have any issues.
[One (M7) Original Android Development] qkall:
I'm having zero gps issues. But I upgraded via cyanodelta and team7 kernel and use gps status (and xposed but that shouldn't matter)
[One (M7) Original Android Development] sabret00the:
Anyone else having issues with the radio constantly dropping out?

---------- Post added at 02:34 PM ---------- Previous post was at 01:56 PM ----------

There are some issues I've been unable to add to the wiki. Search my name in this thread.
[One (M7) Original Android Development] Ce:
I'd love to use this rom but the distorted sound is just horrible. DSP is off. Lowering the volume only makes the distortion sound less loud...but it's still there. I have no problems with the sound quality when a stock rom is installed.
[One (M7) Original Android Development] Bxsteez:
There must have been something I was doing wrong. I did a wipe before and a wipe after flashing and everything seems to work great now.

A dirty flash would not work at all.
[One (M7) Original Android Development] nxt:
Really? A few months ago, audio on HTC ONE and CM was HORRIBLE. Buzzing, distortion, crap volume/quality.

I went back to GPE stock ROM

Then they figured it out and BOOM it sounds exactly like Beats. No issues at all. High volumes no buzzing.

Make sure you're running current nightly.

P.S. I don't use any DSP manager settings or extra kernels. Just stock latest CM10.2 NIGHTLY
[One (M7) Original Android Development] formula84:
Same here audio sounds great as long as you don't enable DSP Manager. Also looking at some recent commits even this may have changed, looks like they may have fixed the distortion when using DSP Manger although I have not tested.
[One (M7) Original Android Development] Ce:
I am using the oct. 5 CM rom, pure CM and DSP off and no other software installed.

Verstuurd vanaf mijn HTC One met Tapatalk 4
[One (M7) Original Android Development] Ruku1994:
As for me audio is not bad, but I have problem with lower speaker. Is pops, and it's generally distorted. Upper one works perfectly. On GE both speakers sound great at high volume.
[One (M7) Original Android Development] qkall:
Maybe give this a go. I can no longer say if it makes a huge difference as others are claiming they aren't using mods. But I've been using it as a standard flash companion for months with enjoyable success.

http://xdaforums.com/showthread.php?t=2293589
[One (M7) Original Android Development] Ruku1994:
Just tried it out. Sadly it does not make a difference, lower speaker still produces bad sound. Maybe someday CM will work on my device as it should. Looking forward to this moment.
[One (M7) Original Android Development] qkall:
What about v4a (viper4android)
[One (M7) Original Android Development] Ruku1994:
I've already tried it. I think it's problem with my phone, maybe I have different sound hardware than the others.
[One (M7) Original Android Development] thefoss:
Yeah unfortunately this is a deal breaker for me too. I'm On TripNdroid now. The Rom doesn't have the community that CM does, and I hate the font, but it's the only AOSP rom I've found that has a descent FFC. Am I alone in this opinion?
[One (M7) Original Android Development] scutworker:
Hello,

Can anybody tell me if device encryption works on this rom?

I am running CM 10.1 and it doesn't and wondered if it has been fixed yet.

Does it work on any rom (other than stock)?

Cheers.
[One (M7) Original Android Development] formula84:
Font is easily switched, check the theme section there is a whole thread for fonts that are flashable
[One (M7) Original Android Development] shaaXo:
Anyone got an idea what the fix for the front camera is? It can probably be fixed on CM, too. I scrolled through the github repos but haven't found anything related to the front camera.

Another thing, what kind of battery life should I expect from CM-10.2 on the One? It seems I'm still draining between 20% and 25% of the battery per hour of screen on time (low brightness, wifi, light cpu usage).
[One (M7) Original Android Development] kennypow3rs:
Fix for the front camera? Not likely unless HTC releases some of their sources etc which you'd have better luck seeing a pig fly. My guess is the front camera is doomed. Again, my guess.

Battery life is different for everyone. As a moderate user from 8am to 4pm on stock cm my phone is on 40% by 5pm. With sense (stock kernel) its usually about 55% by 5pm. Usage depends on user. Try another kernel as the stock in my opinion has poor battery. That's about all you can do...
[One (M7) Original Android Development] shaaXo:
I thought TripNdroid has a better working front camera than other AOSP roms?

I guess I'll give the GPe ROM or a different kernel another try and see how it fares.
[One (M7) Original Android Development] formula84:
It Does try it out.
[One (M7) Original Android Development] thefoss:
I believe he was referring to the Front Facing camera, not the main shooter. TripNdroid does indeed have this working. What did they do right in that regard that can be reproduced in CM?
[One (M7) Original Android Development] cschmitt:
It appears to be using some parts from the GPe rom for the front camera. Similar to IR that can work in CM, but commit was squashed because it included some HTC proprietary blobs.
[One (M7) Original Android Development] formula84:
Can you point out these commits?
[One (M7) Original Android Development] cschmitt:
I was referring to the IR commit, sometime around 9/30. There are some unofficial builds that have it working.

Camera is probably the same deal if someone wanted to take the time to pull the libs, etc. from GPe rom.

My FFC is decent in regular lighting, just need to manually set the white balance in low light.
[One (M7) Original Android Development] sabret00the:
Still can't transfer files over USB using Ubuntu 13.10. The device doesn't get recognised.
[One (M7) Original Android Development] formula84:
Problem is with apps like hangouts and Skype... Face unlock these do not give you an option and always use auto... Sometimes it looks okay others I am purple /green depending on light.

---------- Post added at 06:34 PM ---------- Previous post was at 06:29 PM ----------

What would be even better is if somehow those modes could get removed so when auto is selected it does not have a chance to ever use those 2 problem ones
[One (M7) Original Android Development] cschmitt:
True. There's a white balance calibration file for the front camera at /sys/android_camera_awb_cal/awb_cal_front

Might try pulling one from GPe and see how it performs.
[One (M7) Original Android Development] formula84:
Where does this live in the compiled zip for a build... Its this something that gets generated via kernel on first boot or something? (whole sys folder)

I was going to try and pull from trip's build.
[One (M7) Original Android Development] tiny4579:
Sys is not in the Rom. It's part of the kernel userspace filesystem. It exists tor userspace to interact with the kernel.

Outputting the file could help us with tweaking it. I got in a sense mood for now so I probably won't get to it just yet being not on cm.

I checked. It's not a legible file.
[One (M7) Original Android Development] jasalta387:
I had a similar issue. I worked around it by connecting the phone behind a usb hub. Odd as it may sound, it worked for me...
[One (M7) Original Android Development] nerotix:
Isn't it possible for ppl to compile their own CM10.2 and just add the GPE camera blobs/libs so they dont have the weird issues with the front facing camera etc?
[One (M7) Original Android Development] shortskoolbus:
Just installed latest cm 10.2, not able to get gps fix. Anybody else have this problem? Sorry, using mobile app, difficult to search this thread.
[One (M7) Original Android Development] KaZo58:
i have cell data connection issues. internet disappears while chatting or browsing.. or right here on tapatalk -.- have this problem about a week. did i miss something? radio is ...1150.04L no LTE

edit:

Screenshot

Gesendet von meinem One mit Tapatalk 4
[One (M7) Original Android Development] serkanhiziroglu1998:
I really want to use a stable holo uied (aosp?) rom but whatever rom I've tried was not stable for me in htc one including arhd gpe rom, cm nightlies.

HTC One cihazımdan Tapatalk 4 ile gönderildi
[One (M7) Original Android Development] polishpt:
sorry for off-topic, but how can i get status icons like the ones on you screenshot?

Thanks
[One (M7) Original Android Development] KaZo58:
it's from themes. i have this one: MIUI v5 - CM 10.2 Theme
[One (M7) Original Android Development] pechano:
Carrier?

I had the exact same problem when I installed CM (nightly 1002 I think). Thought it was the unstable nightly, but I was getting the same issue in the latest stable, which was CM 10.1.3 and not 10.2. So I figured it had to be something else.

When I originally bought my One and turned it on for the first time, I could choose between several carriers and I offcourse picked CallMe, which is the one I have. Now, when I installed CM, this was not possible. It defaulted to Telia's network (which is the large network that CallMe uses, but with other APN settings). Things seemed to be ok, but I was losing connectivity all the time, even getting dropped calls. Apparently there is a file called apns-conf.xml in /system/etc/ that contains carrier and APN info. I have a feeling that this list of carriers is tailored towards American carriers and only the biggest of the European ones. I at least could not find my carrier in it, only Telia. I can see that you are from Germany, so perhaps you have the same problem as me. I changed the settings according to CallMe, and now everything works as good as it did with Sense. So check it out.

TLDR: Check that your APN settings match the ones your carrier specifies.
[One (M7) Original Android Development] KaZo58:
I had the right APN settings. now i deleted all my APNs in the list. My carrier doesn't need it. let's see if it works better now.

Gesendet von meinem One mit Tapatalk 4
[One (M7) Original Android Development] TKH1218:
Question for T-mobile users

I'm a T-mobile user.

I've noticed that there is a stable build for the t-mobile variant

But before I flash it onto my device I wanted to ask if wifi-calling is enabled and working for the nightlies/stable builds

I'm very dependent on the wifi-calling so I was concerned. If anyone can give me an answer, much thanks to you.

Thank you
[One (M7) Original Android Development] willew4:
The wifi-calling is only available using the T-Mobile version of Sense. Unfortunately, it is not available in CM, or other roms.
[One (M7) Original Android Development] shortskoolbus:
So I realized that I can't get a GPS lock if I have Wi-Fi and mobile networks turned off under settings, but all other location settings on. If Wi-Fi and mobile settings is on, get a GPS lock right away.

Anybody else having this problem?
[One (M7) Original Android Development] sa_ma:
Without data "wifi or mobile" there is no Assisted GPS (agps) info , without agps it will take much longer to get a lock
[One (M7) Original Android Development] shortskoolbus:
Thanks for the feedback. But actually it will search for hours with no lock, was pretty much instant when I was still on 10.1.3
[One (M7) Original Android Development] qkall:
Have you tried GPS status?
[One (M7) Original Android Development] sabret00the:
Damn, I'm gonna have to source one. Thanks for the tip.
[One (M7) Original Android Development] Ce:
I just need some help to find out what the status of CM 10.2 development for the One is.

As a "non-developer" the changelogs don't mean anything to me, i just don't understand them. On the other hand some bugs "survived" a lot of nightly's. To name two: first, the sound from the external speaker is very distorted even at low volume (speaker is not defective, works fine on Sense Rom) and second, touching the screen with one finger (to scroll for example) triggers a zoom action.

I don't want to sound rude and I do respect the work of the developers and the fact that they develop for free in their spare time...but for someone like me it almost

seems

10.2 development for the One is on a very slow pace. I know what "nightly's" means and that I have to deal with bugs that can come...go...and come back. That's absolutely no problem. But I used CM on a lot of devices and it always felt like "two steps forward and one step back". Not with the One. If feels more like "sometimes a very small step forward".

the last CM I used was the oct. 11 one. Removed it immediately because of the horrible sound quality of the external speakers. I was really afraid to blow up those little speakers (with and without DSP)
[One (M7) Original Android Development] flatzki:
Nice to see xposed worked on 4.3.1 ( latest nightly ) we need a transparent statusbar module for cm and centerclock module. Maybe we need a module for Mord options on powermenu
[One (M7) Original Android Development] sensationfan623:
Having a small problem. The display timeout doesn't seem to work. My phone's display stays on indefinitely unless I power it off manually. And the display turns on whenever the proximity sensor is uncovered. I can't find any settings to change this unless I missed it somewhere?

If someone could offer some advice I would appreciate it

Edit - I don't mind the proximity sensor thing, but the other is an issue. Just thought they might be related
[One (M7) Original Android Development] flatzki:
Oha custom power module works in cm 10.2 (4.3.1) u have 3 way reboot and Screenshot app.
[One (M7) Original Android Development] formula84:
To anyone that would like cm or any other aosp rom to have properly working ffc check out my post here... Pretty interesting that a simple value in build.prop could impact this.

http://xdaforums.com/showthread.php?p=46412023
[One (M7) Original Android Development] knudsen81:
will the software updater still work after change of build.prop???
[One (M7) Original Android Development] formula84:
No idea only way to know is to try
[One (M7) Original Android Development] knudsen81:
Okay but i have not edit my build.prop yet
[One (M7) Original Android Development] thracky:
What exactly is this post supposed to do?
[One (M7) Original Android Development] spyker88:
What radio firmware version is recommended for cyanogenmod? :laugh: I am using at the moment (4.3/3.22.1540.1/Developer Edition OTA) Radio_4A.20.3263.16_10.38k.1157.04L / P :cowboy:
[One (M7) Original Android Development] cschmitt:
I'm on the same radio, works fine on AT&T.

---------- Post added at 05:44 PM ---------- Previous post was at 05:33 PM ----------

Crazy that a build prop could make any difference, but I tried it and FFC seems much better.
[One (M7) Original Android Development] formula84:
I was shocked as well I can't believe I figured that out by chance, it had been bothering me so much. So happy I can get consistent front camera across aosp builds now.

---------- Post added at 06:56 PM ---------- Previous post was at 06:47 PM ----------

I would also love it if someone with more knowledge could explain how a value change in the build prop could cause the camera to do that.
[One (M7) Original Android Development] nerotix:
What u mean with consistent front camera? U were able to remove the green/red tint or something? If so, please share ur knowledge in a few steps<3
[One (M7) Original Android Development] tmckenn2:
OMG. I cannot believe that worked. That has been my only complaint about CM. (The front facing camera that is) and now it works. Not as good as the GE ROM I loaded the other day, there is a lot more noise/ the picture isn't as sharp but at least its use able.
[One (M7) Original Android Development] killman2659:
Yes, did you read his post? ;)

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

Gonna flash CM now, thanks for the FFC fix :good:
[One (M7) Original Android Development] nerotix:
Yeah I did.. so all who did was what he said in the post @ TripNDroid? Which is:

You have = ro.product.device=m7

CM has = ro.product.device=m7ul

Correct?
[One (M7) Original Android Development] killman2659:
I believe that is it.
[One (M7) Original Android Development] formula84:
Yes all you have to do is change that one value in build.prop and it fixes the tint and makes it a cleaner picture.
[One (M7) Original Android Development] DarkRazorZ:
I can confirm the FFC trick works as well
[One (M7) Original Android Development] Epipsychidion:
Thank you to formula84 for the FFC work around! And of course to the entire CM Team for their awesome work too
[One (M7) Original Android Development] oddlyshapedstickman:
Wow, how on earth does the build.prop effect the FCC that profoundly?
[One (M7) Original Android Development] cschmitt:
Kind of like how setting lpa.decode=false fixes the skipping in bluetooth streaming for some BT devices.
[One (M7) Original Android Development] JDAapps:
I think it's just that m7ul was not a valid value for that property. While the build.prop file may seem simple/harmless, it defines the properties of the device and the build. These values are fetched by the code, and used for their respective features/functions. If the camera was checking "if (ro.product.device == m7) { // fix ffc }", then it wouldn't apply the fix with m7ul or m7att as the value. Even AT&T Sense uses m7 for that value, not m7att for example.

Great find though!
[One (M7) Original Android Development] LorD ClockaN:
I suspect that camera lib checks for device name and it wanted to be m7, not m7ul, att, spr etc etc
[One (M7) Original Android Development] cschmitt:
Here's a simple script that fixes up ro.product.device and ro.build.product in build.prop during CM ROM updates. Rename the attached file to 51-buildprop.sh, copy to /system/addon.d, and chmod 755. Spares having to manually edit build.prop after every flash.
[One (M7) Original Android Development] sabret00the:
There are no adverse effects to the build prop change elsewhere? If so, has the change been submitted to CyanogenMod?
[One (M7) Original Android Development] tiny4579:
Cm split the devices a while back. A proper change should be submitted. We need to submit a change to the camera code and add the device ids. I'm going to try to find the code. If it checks for m7 then it was the split of devices causing the ffc issue. This points to a hack somewhere that fixed the color in the first place.

Edit: on second thought if the camera calibration is in the binaries, I'm not sure what can be done as a proper fix.
[One (M7) Original Android Development] knudsen81:
Does some1 have the right gallery to get picasa to show up i gallery ???

Edit got the gallery apk from google ed.
[One (M7) Original Android Development] LorD ClockaN:
Another line can be added to build.prop like I did here:

http://gerrit.zips.net/424

and than you have double lines, but =m7 is the later one and that one is applied..

I'm sure CM won't agree with that

edit:

still need to confirm if this method is working though

edit2:

disregard the link.. not working that way.. will do it in another way soon
[One (M7) Original Android Development] VistaX:
Soft keys worked on cm10.1, but I can't get it to work on cm10.2. Anyone knows why? What's different from 10.1?
[One (M7) Original Android Development] cschmitt:
There's already a ro.cm.device=m7ul property. Couldn't that be used for the CM device specific builds, leaving the other properties set to m7 as they are in HTC builds?
[One (M7) Original Android Development] tiny4579:
That sounds like a good idea. I guess we'll see what cm does. I think ro.product.device impacts recovery flashing though.
[One (M7) Original Android Development] LorD ClockaN:
no, the main one is ro.product.device

and it's set once you start compiling and you start with brunch m7ul.. if you start with m7att it will be named m7att, so there is no way to set it to m7 and have all variants of the phone supported for compiling IMHO..

I edited mypatch in that link with your idea and I'll leave it like that

check out PS3

edit: even though it doesn't get applied at boot.. need to find the derp..
[One (M7) Original Android Development] cschmitt:
It gets applied when the rom is flashed via updater, not at boot.
[One (M7) Original Android Development] LorD ClockaN:
I want it to get applied at boot, but applying at flash is also good idea
[One (M7) Original Android Development] goldenratio:
Huh, yeah... wow. I just took some comparison photos with the FFC before and after editing the build.prop, and it's night and day. :laugh:
[One (M7) Original Android Development] xBIGREDDx:
My T-Mobile MyAccount app just gave me this notice.

I guess this is too stable? :p
[One (M7) Original Android Development] Jediritter:
Installed this cfw, because I had problems with InsertCoin (phone keeps shutting off)

Wiped data, cache + dalvik

Installed CM10.2 + gapps

Didn't install Titanium Backup, just installed all old apps over the play store

Worked for me 2 days and just got a message in whatsapp, trying to open it and phone instantly shuts off and won't boot right now.

Is it possible to get any logs why this happends?

I guess its maybe because my glas is slightly broken (one crack over the display), but touch and lcd is working fully.
[One (M7) Original Android Development] popy2006:
Is the lpa.decode=false already merged into the nightlys?

Also waiting impatiently for an Bluetooth Audio dropout fix.

Want to use CM10.2 as my daily driver ;)

thx

pOpY
[One (M7) Original Android Development] cschmitt:
It's not merged and probably never will be. Low power audio is supposed to work, so disabling it is considered a hack. There have been recent commits that address many of the Bluetooth issues, but my experience is that lpa is still broken and simply disabling it has cleared up the skipping without any noticeable effect on battery life (or anything else.)

I use a script to disable lpa in build.prop when CM is flashed.
[One (M7) Original Android Development] tjsooley:
What is the status of IR support in official?
[One (M7) Original Android Development] marvin_666:
It's possible to add Russian on dialer buttons and search contacts with Russian names how it was in 10.1 builds?
[One (M7) Original Android Development] kennypow3rs:
No official support yet. Just use the regular tv remote like normal people. :good: