yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] thegh0sts:
fair enough, i thought it was made to fix the inherent security flaw within the android OS.
[One (M7) Original Android Development] sweetnsour:
Is this considered a bug? And can anyone reproduce this?:

1. Open an app (such as settings).

2. Go to the recent apps/switcher (for me it is double tap home).

3. Press back to return to the app.

4. Press back again. I believe the intended behavior should be returning to home but instead it returns to the recent apps/switcher.

EDIT: Nevermind. A reboot fixed this. Sorry about that.
[One (M7) Original Android Development] giantbibo:
low outgoing volume on bluetooth

Hi guys, great job! Small issue i am having is very low volume on bluetooth calls. The incoming volume i was able to fix using the app volume+ but for the outgoing volume no luck yet. I am using a gmate+, the same that i used before flashing this rom and it was working fine. Please advise. Thanks.
[One (M7) Original Android Development] cschmitt:
It's broken in 10.22 and later, just tested that. Will need to check change logs to determine what broke it.

Sent from a van down by the river.
[One (M7) Original Android Development] strickyy:
How can I move the clock to the center in the status bar? Is there a toolbox or an app that gives me more options other than the ones in settings?
[One (M7) Original Android Development] tiny4579:
Try gravity box with the xposed framework.
[One (M7) Original Android Development] goldenratio:
If you're referring to fixes for the 'master key' and the 'dual signing key' bugs, that is one of the many modules offered by the Xposed Framework. You won't need those fixes on CyanogenMod 10.2 though, since they were patched in a long time ago.

There are probably like 50 other modules in Xposed. It's easy to install and use, and easy to remove if need be. You should just check it out :)
[One (M7) Original Android Development] _saiko:
Does ipv6 work for wifi?

I am not getting v6 address assigned whereas my network and other devices have no problem.
[One (M7) Original Android Development] Orginator:
So after reading some positive feedback I've figured it might be time to give cm another try.. I have to agree that it got much better and does in general run nice.. huge improvement over what it was a while ago..

But there is still room for further improvement, the launcher animation are not as smooth as those from the google edition..

Simple test case :

Go to apps drawer and slide slowly to the next page, on cm you'll notice microstutters whIle on the ge edition it's smooth as butter :)

Nonetheless, great job guys and thanks allot!
[One (M7) Original Android Development] Monsterkater:
I really love battery life on CM10.2, it's just perfect.
[One (M7) Original Android Development] fohdeesha:
Why are you using the stock CM launcher? eww
[One (M7) Original Android Development] :
I think that just the stock stuff

should be work at the best, including the Launcher :cowboy:
[One (M7) Original Android Development] Zedicus:
i still have unusably low microphone volume when recording video from the camera.
[One (M7) Original Android Development] prng:
I heard it is because the rear microphone isn't enabled or not working.
[One (M7) Original Android Development] xBIGREDDx:
This is a bit late, but I've tried stereo music from Google Music All Access and it played correctly in stereo from the two phone speakers.

(Test song was "Gone" by Kanye West)
[One (M7) Original Android Development] thegh0sts:
i use double twist as my music player and music comes out of both speakers.
[One (M7) Original Android Development] sabret00the:
The rear microphone works, it's just low as frig. To use loudspeaker, I have to pick up the phone like a walkie talkie and talk directly into the microphone. Which I find especially hilarious given the fact that when used for noise cancellation it's overzealous meaning try and use the phone on my shoulder and suddenly no one can hear a thing.

Basically, there are basic touch screen issues with this ROM and there are basic phone issues with this ROM. Unless you're essentially using it as a pocket audio/visual device, it's really not a daily driver candidate.
[One (M7) Original Android Development] tiny4579:
I'm not having touch screen issues. I think the zoom problem was fixed. I used to have that issue. Now I don't. Which phone issues are you describing? I guess I don't really use the speakerphone in mine.
[One (M7) Original Android Development] thegh0sts:
OK, I have given xposed a try with xblast + the Radiant Orange theme from nitinvaid (http://xdaforums.com/showthread.php?t=2407890)

and it works nicely...fixes the battery charge icon for me (i have it set to circle with percentage as it was still showing blue with xblast on) so the theme fixed that and now i am sporting a BF4 wallpaper to go with it.

so all-in-all very happy :D
[One (M7) Original Android Development] goldenratio:
There's something I think you guys are gonna like in the nightly changelog:

HTC IR Blaster support for AOSP

:)

Protip though... don't try to build at home right now. Cellular connectivity seems completely broken. My APN list is empty. I blame one of these:

http://review.cyanogenmod.org/#/c/52620/

http://review.cyanogenmod.org/#/c/52614/

http://review.cyanogenmod.org/#/c/52619/
[One (M7) Original Android Development] thegh0sts:
nice! very nice!
[One (M7) Original Android Development] kingofthebraves:
Can anyone give some comparisons between GE roms and CM or AOSP roms based on speed, stability and battery life? :)

I know CM or AOSP probably has more bugs but battery life is the most important criteria for me right now.
[One (M7) Original Android Development] alandd86:
hi guys ,, i just want ur feedback about the latest nighties ist stable as a daily driver ..or what is not working ?

thnxx all..
[One (M7) Original Android Development] sectorek:
it's stable!
[One (M7) Original Android Development] guteseite:
Mic audio of video cam is still very, very low and no stereo recording :mad:
[One (M7) Original Android Development] raydekok:
Having problems. Phone sometimes drops signal and it looks like 4g is missing in latest nightly.
[One (M7) Original Android Development] thegh0sts:
definitely stable and the battery life of this rom is great - i'm getting between 36 to 40 hours per charge...better than what i was getting on my S3.
[One (M7) Original Android Development] scutworker:
Has the problem of low sound/noise during a call been sorted out yet?

What other glitches remain?
[One (M7) Original Android Development] Theshawty:
This sounds awesome! http://review.cyanogenmod.org/48638
[One (M7) Original Android Development] thegh0sts:
got mentioned in the previous page.
[One (M7) Original Android Development] kennypow3rs:
If battery life is REALLY important use a sense ROM. None of them can compare I cannot achieve the same battery on ANY other ROM. In terms of battery based on ROM I'd rank them like this.

Sense

GE

Aosp/CM
[One (M7) Original Android Development] thegh0sts:
i'm curious as to the time zone of get.cm?
[One (M7) Original Android Development] h4xdaplanet:
Having an odd problem on the latest nightlies - if I am connected to wifi, no text messages come in and I'm pretty sure I'm not receiving calls. As soon as I get off wifi, all my texts come in. Full signal - running m7tmo
[One (M7) Original Android Development] jasalta387:
Don't get misled by the battery percentage left after comparable usage: I've seen that Sense (like Touchwiz with Samsung) use a non-linear formula to tell the remaining battery life. At the beginning battery percentage is dropping quite slow, but when you with low battery every percent unit lasts less time than when you have an almost full battery. CM/AOSP uses a linear count: 1% of battery translates to the same usage time at any level. This is what tells me my experience.

Best way to compare is to look at the screen and standby times together (assuming that the same apps are installed in the different ROMs).

In the end, you have to choose the ROM that gives you the best experience.
[One (M7) Original Android Development] tiny4579:
That shouldn't be happening. I haven't updated in a few days so I wouldn't know if I had the same issue but I got a couple texts last night when connected to wifi. CM was moving around APN and stuff the last few days so that may have been a factor. Did you try today's nightly? It should be sorted out now.
[One (M7) Original Android Development] tiny4579:
It is true that Sense has some different power management rules than AOSP. For example, Sense registers a full charge at 100% while AOSP registers it at 90%.

I've always noticed slower battery drain on Sense than CM/AOSP and it could be what you're saying. However, with the recent changes to CM, the way the frequencies scale has been drastically changed. I noticed that the CPU scales to 1728 a lot easier than Sense and it's still not quite as smooth but almost. I think this is due to the kernel not being optimized for mpdecision/pnpmanager/thermald. Actually, CM doesn't use pnpmanager.
[One (M7) Original Android Development] cschmitt:
[MENTION=3500210]tiny4579[/MENTION] - any insight into what broke the call log for Google voice calling in the 10/22 and following builds? In 10/21 and prior calls made using GV were logged using the number dialed, but after 10/21 they are now logged using the intermediate number used by GV to place the outgoing call. I checked the 10/20, 21, 22 commits and couldn't find anything that would have appeared to have broken this.
[One (M7) Original Android Development] kennypow3rs:
I agree with you. But based on MY actual usage and standby time sense for ME has better usage. So better its almost night and day. Its all about how the person uses their device. Personally, I hate sense roms (on AICP right now) but for battery its a no brainer.
[One (M7) Original Android Development] tiny4579:
I'm not really sure. I don't use Google Voice. This commit seems suspect:

https://github.com/CyanogenMod/andr...mmit/569019bd219be7f314af12c8ecc16f94e66095e5

I don't think it's necessarily the culprit but there were a lot of changes recently to support Multi-sim. Maybe this merge broke something with Contacts and Google Voice.
[One (M7) Original Android Development] h4xdaplanet:
I am on the 20131029 nightly right now and noticed I was having issues this morning. As soon as I come off wifi everything seems to work fine. I can also send texts and calls without a problem while on wifi but not receive anything.
[One (M7) Original Android Development] LorD ClockaN:
5-6 packages got merged with qcril branch and there were a lot of commits so hard to pinpoint which one broke it
[One (M7) Original Android Development] goldenratio:
Check and see if you have the proper APN selected, or for that matter, if there are any APNs in the list at all.

When I tried building at home yesterday with all the latest commits, cellular was completely broken for me... there were no APNs in the list. Not sure if it has been fixed by a later commit.
[One (M7) Original Android Development] h4xdaplanet:
There are APNs in the list with the "Fast" tmo apn selected - and I don't see any strange settings in the APN setup - looks normal
[One (M7) Original Android Development] cschmitt:
I have a feeling this is what broke the call logging: https://github.com/CyanogenMod/andr...mmit/8f916caa483a38596cfa629dd91de49f30e27086

Here's a bit of a debug trace of a GV call showing how the GV gateway URI is being logged incorrectly:

D/PhoneUtils( 1245): placeCall '3338739822' GW:'tel:+16872088111' CallType:0
...
D/CallLogger( 1245): - callLogType: 2, UserData: com.android.internal.telephony.CallerInfo@95d4a920 { name null, phoneNumber non-null }
D/PhoneUtils( 1245): modifyForSpecialCnapCases: initially, number=xxxxxxxxxxxx, presentation=1 ci com.android.internal.telephony.CallerInfo@95d4a920 { name null, phoneNumber non-null }
D/PhoneUtils( 1245): checkCnapSpecialCases, normal str. number: +16872088111
D/PhoneUtils( 1245): modifyForSpecialCnapCases: returning number string=xxxxxxxxxxxx
D/CallLogger( 1245): getLogNumber: +16872088111
D/CallLogger( 1245): - onDisconnect(): logNumber set to:xxxxxxxxxxxx, number set to: xxxxxxxxxxxx

The problem is these two lines added in CallLogger.java:

if ((o == null) || (o instanceof CallerInfo)) {
ci = (CallerInfo) o;
+ } else if (o instanceof Uri) {
+ ci = CallerInfo.getCallerInfo(mApplication, (Uri) o);
} else {
ci = ((PhoneUtils.CallerInfoToken) o).currentInfo;
}

logCall(Connection c, int callLogType) is calling getCallerInfoFromConnection(c) to get the CallerInfo, which is looking at the user data of the connection and now since the userdata is a instance of Uri ('tel:+16872088111') its is using that to log the call instead of falling through to the else clause and using the CallerInfoToken.currentInfo as the CallerInfo (which would be the 3338739822 number actually dialed in the placeCall() method.)

Then logCall() calls getLogNumber() which cleans up the Uri by calling number = PhoneNumberUtils.stripSeparators(number); and then logs and returns it.
[One (M7) Original Android Development] LorD ClockaN:
Could be.. best to report to CM bugtracker. I ain't using CM so not on me to report
[One (M7) Original Android Development] mattman83:
Backup location was fine. It sees the data, hit restore and it just sits there forever. Does not crash out or error, just sits there trying until you kill the app.. Tibu was fresh install from market on a clean installed rom, so no old configuration messing with stuff.

M.

---------- Post added at 05:59 PM ---------- Previous post was at 05:58 PM ----------

Flash gaps from bottom of first page, not the op. Cid stuff is on GE roms, nothing to do with cm.

M.
[One (M7) Original Android Development] jwtrockz1998:
Is this stable? and does it include the new focal app?
[One (M7) Original Android Development] Asdoos:
Yes ! and also Yes
[One (M7) Original Android Development] jwtrockz1998:
Ok cool, just a few more questions does the audio and camera work well as those are the things that I use the most?
[One (M7) Original Android Development] Asdoos:
For me all "main" stuff works fine!...(WIFI, BT, 3G, Camera and so on)
[One (M7) Original Android Development] jwtrockz1998:
Ok cool I think I might give it a flash then, SOz one more question but does texting work now? And calling works rigt
[One (M7) Original Android Development] Asdoos:
For some user swiping is bugged on google keyboard.

But try it by yourself. You should be amazed!
[One (M7) Original Android Development] gmbhneo:
Thanks, flashing the other Gapps worked fine.
[One (M7) Original Android Development] anrichp:
Trebuchet

Is anyone experiencing problems with Trebuchet crashing on odd occasions?
[One (M7) Original Android Development] SanTos0250:
yep, but now i use nova laucher...
[One (M7) Original Android Development] yeeson:
Apex Launcher no problem
[One (M7) Original Android Development] riverajuan:
This can grow on you. I am already missing the 10.2 nightlys
[One (M7) Original Android Development] razer1224:
Follow my G+ Community

Where you get nightlys
[One (M7) Original Android Development] formula84:
I was also having this issue, chasing the location but not moving the backups when prompted worked for me, try it. I did the Preferences -> backup location -> detect whole device -> chose the path with legacy in the name -> do not move when prompted -> menu -> reload application -> $
[One (M7) Original Android Development] superfire71:
ok got
[One (M7) Original Android Development] formula84:
Screen shot
[One (M7) Original Android Development] mattman83:
Thankyou this works :)

M.
[One (M7) Original Android Development] gilbus:
Another feature of is 4.3 is surround (virtual) sound for nexus 10 and 7, because these devices have dual speakers. Will this feature be ported to our device as we do we have this wonderful speakers or is it kind of device specific? :D

Gesendet von meinem HTC One mit Tapatalk 4 Beta
[One (M7) Original Android Development] Hedi86:
I have not tried the current ROM, but will do it in the near future. I would be interested, does auto-update work already?
[One (M7) Original Android Development] razer1224:
No it doesn't work

You gotta download nightlys
[One (M7) Original Android Development] cschmitt:
Nightly build, so no joy on opening a Jira ticket. Wouldn't expect you to report, only relaying the cause. Maybe maintainers will have pity and read the thread...
[One (M7) Original Android Development] erniev:
Im also having problems with the latest nightlies where i cant sent text messages but i cab receive them just fine. the last nightly i was able to use withuot a problem is cm-10.2-20131024. any ideas?
[One (M7) Original Android Development] tiny4579:
I don't know. I did a self build today and sent a text and received one just fine.
[One (M7) Original Android Development] guteseite:
IR Smart Remote is not working since last nightly
[One (M7) Original Android Development] superfire71:
Yeah, me either. They added IR, and it busted:(
[One (M7) Original Android Development] tjsooley:
Doesn't work on pac nightly either
[One (M7) Original Android Development] tiny4579:
So the cherry picked it worked but they broke it when they merged it?

Now they have to fix it or revert it. I have a theory patchset 8 is the problem.

And to check. This is even the smart ir remote that has the built in ir support to get it working on aosp?
[One (M7) Original Android Development] superfire71:
Yes, using smart IR remote. Worked on 10/29, broken 10/30
[One (M7) Original Android Development] kingofthebraves:
Yeah I noticed this as well with my s4, after 30 or 40 percent it goes down way fast
[One (M7) Original Android Development] tiny4579:
Works for me on a build I did earlier today. I just confirmed I have the same merge they did last night. No other changes were made to fix it and they didn't merge any patches since last night for IR.

I'm using the latest ColorTIgerApps Smart IR Remote and it works.

Ahh, I think I know. Check if the three files are present in your build:

/system/app/CIRModule.apk

/system/framework/htcirlibs.jar

/system/lib/libhtcirinterface_jni.so

I believe it worked for me because those files got copied over by the build. I'm not sure if the build bot pulled them prior to the build.
[One (M7) Original Android Development] superfire71:
Hmm, what is strange is the 10/29 build is without those files and tigerApp smart IR works. 10/30 build has those files, and smart IR not working
[One (M7) Original Android Development] tiny4579:
Well, the Smart IR app has them packaged so it's not too surprising that it would work with the files missing.
[One (M7) Original Android Development] superfire71:
I deleted the files you referenced from the 10/30 build, and Smart IR now working.
[One (M7) Original Android Development] goldenratio:
I tried building at home again today and I still can't get cellular to work and all APNs are missing.

I sync'd from the 10.2 branch of the repo, cleaned up my build environment... basically started from scratch and the resulting ROM just doesn't work for cellular connectivity. If I revert to my last build from 10/27 everything is fine.

I have a Google Edition HTC One with an AT&T SIM. I blame this commit:

http://review.cyanogenmod.org/#/c/52620/

... but then again I could be wrong. My APN list is literally empty though.
[One (M7) Original Android Development] thegh0sts:
the pie controls look pretty neat: anyone tried LMT launcher with CM10.2 on this phone?
[One (M7) Original Android Development] madLyfe:
group msgs broken again in last nightly..
[One (M7) Original Android Development] goldenratio:
So is anyone running the latest nightly not having problems with SMS/MMS or mobile connectivity in general?
[One (M7) Original Android Development] metalk9:
I've noticed that after running this ROM for several days without a reboot, the UI starts to get a bit laggy. Rebooting fixes the problem. Could be a misbehaving app though I guess.
[One (M7) Original Android Development] wg25:
Here the same...

Gesendet von meinem One mit Tapatalk
[One (M7) Original Android Development] thegh0sts:
i wonder if it's possible to have the alarm go off when the phone is turned off?
[One (M7) Original Android Development] scutworker:
No, it's not 'cos when the phone is off, its shut down and nothing runs except the internal clock.

This is a feature I miss on smartphones, my old Sony Ericsson was able to do this and very useful it was too.

Now, I just use aircraft mode.
[One (M7) Original Android Development] dumbo octopus:
stock sense rom allows the alarm to go off even when the device is turned off.

~dumbo.
[One (M7) Original Android Development] thegh0sts:
which leads me to think if it's something that can be written into the rom that allows for it. this feature would be awesome to have back.
[One (M7) Original Android Development] scutworker:
Really? I never knew that. That's not with that fastboot thing on is it where the phone isn't off in a traditional since?
[One (M7) Original Android Development] dumbo octopus:
works regardless.

~dumbo.
[One (M7) Original Android Development] Msoerensen:
Do we have a time estimation on when Android 4.4 will come to CyanogenMod? I know it may be a bit early to say anything about it.. Just very much looking forward to 4.4. :)
[One (M7) Original Android Development] Mucky2:
It will Come with CM11

Gesendet von meinem One mit Tapatalk
[One (M7) Original Android Development] tiny4579:
When it's ready.

Remember no ETAs. They haven't even started merging into a satging branch yet. If you check their Google + page you can get a better idea on what they need and are planning to do.
[One (M7) Original Android Development] Theshawty:
Would the screen be too small with a navbar?
[One (M7) Original Android Development] XxJibblesxX:
4.4 kitkat will be tricky considering all the apps in kitkat are pretty much Google made
[One (M7) Original Android Development] tiny4579:
How do closed apps that will probably be on the play store hamper porting kit Kat?
[One (M7) Original Android Development] XxJibblesxX:
Not so much porting kitkat. Would cyanogen just use a updated version of jelly bean messaging app as stock for example?
[One (M7) Original Android Development] tiny4579:
Not sure. But even before hangouts was introduced messaging wasn't really updated since ics/jb. I would think they'd take the AOSP one and maybe improve it. It's up to the user to use the closed Google one or the AOSP app.
[One (M7) Original Android Development] goldenratio:
Milestone 1 for CM 10.2 is coming tonight:

http://www.cyanogenmod.org/blog/cyanogenmod-10-2-m1-release

the build should be here later after the buildbots are done:

http://download.cyanogenmod.org/?device=m7ul&type=snapshot
[One (M7) Original Android Development] LorD ClockaN:
If you check android git than you'll see that they've made KitKat branch of mms app, so don't know if the app will be available or working

~~ Flowed from my HTC One using IceCold rom ~~
[One (M7) Original Android Development] thegh0sts:
that's pretty quick and very welcome!

EDIT: WOO HOO! the M1 rom is up :D
[One (M7) Original Android Development] KaZo58:
which timezone are they using on get.cm? and yesterdays (01.11.) build is only 1,4kb. snapshot is released under 'nightly' :D

Gesendet von meinem One mit Tapatalk
[One (M7) Original Android Development] thegh0sts:
doesn't matter: the M1 Snapshot is already up.
[One (M7) Original Android Development] Theshawty:
M1 snapshot is already up but branded a nightly.

EDIT: thegh0sts was faster. :p
[One (M7) Original Android Development] fohdeesha:
It's a good amount larger than the nightlies. Who wants to flash it first? :angel:
[One (M7) Original Android Development] thegh0sts:
i'm downloading and flashing it soon :D can't wait....just treat it like a normal flash yes? :p

EDIT: Phone updated fine and is now running the M1 Snapshot :D

generally, how long is the gap between snapshots?
[One (M7) Original Android Development] Theshawty:
A month, IIRC.
[One (M7) Original Android Development] thegh0sts:
sounds good, saves me from having to flash every few days :D

EDIT: M1 Snapshot is fine...flash away!