yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] kennypow3rs:
All the news ive been reading about the last two days has been shocking. Im happy for Steve that CM is now a company. Its crazy how someone can wave alot of money in your face and change your core values. But that's the american dream right, get rich, buy a boat and live in a 10 million dollar mansion etc. I'm shocked with Steve but not with koush; hes been a greedy fool since releasing his apps many years ago. So what Im learning is that essentially cm will turn into a touchwiz or sense rom right? Isnt the sole purpose of CM is to free you of carrier "Chains" while adding features that arent stock and even fixing bugs on stock roms? If they're goal is to get googles approval so they can add google apps and release a play store installer and gain more users, they will have to strip alot of features (which they have) and make some things closed source. CM's core was getting everyone together and creating one awesome open sourced rom. Pretty much bringing us back to square one like having touchwiz or sense all over again. Why would i run CM if its pretty much going to have what a stock google rom has but with cyan colors; it will have strip many features to in order to get the google apps. I don't know much about all this but this is what im getting out of it all. To make a rather long story short, it seems like CM has been swallowed by the big guys and our special little gem of a rom will no longer be. I guess I wont be running CM anymore (not that anyone would care), but I will fill the void with another rom that will become what CM once was; like aokp or etc. :(
[One (M7) Original Android Development] fohdeesha:
well, that was depressing.
[One (M7) Original Android Development] Zedicus:
it does say that the distro will change. it does say that components will be removed, and CTS will become more important. if the CORE remains open and community driven then nothing will change. he will simply be taken the distro, applying his changes and offering it to the carriers. it will be another fork like CM M7ATT or CM CAPPY.

he could turn the core into a closed proprietary distro, with full CTS and full lockdown, but even then if the core of the system remains OSS then their is nothing keeping the devs of each phone to just re-add all the features that they remove to get CTS and continue down the same road. more work, yes. impossible, no.

i realize these 2 options are optimistic and the third is total lockdown and lockout of anything FOSS really. that would make me sad.
[One (M7) Original Android Development] sabret00the:
Just for the record 10.1 passes CTS. Things like not supporting UMS and external SD Cards is just dumb. Basically CyanogenMod needs to do what Mozilla done. Draw up core principles with some input from the community that's served them so well and stick to that. Mozilla is definitely the lighthouse they require here.
[One (M7) Original Android Development] Ce:
+1

What's the risk CM is more and more becoming........stock Android in order to pass the CTS? I also find it disturbing that CM is going "commercial" knowing it became what it is today thanks to a lot of "volunteers", patching and developing stuff "for free". For the time being i'm switching back to a Sense or GE rom and see what this story is doing to the development pace of CM.
[One (M7) Original Android Development] lorloff:
You can have commercial software and still be open source. Look at Ubuntu, look at Red Hat. They make money on support, not on the product. All of it is open source. CM going mainstream doesn't change the open source aspect of it. It changes some features that some people wanted. The core of the product will remain the same. Focal being removed, mixed reviews. I thought it had potential, but there were definite flaws with it. Does that mean it couldn't be released as a google play app? No, it could and just not be part of the ROM.

They have two main goals to this project. First is simple management. Yes lots of poeple develop and lots of people contribute. However if nobody is in charge (ie linux without linus) the community portion can get out of hand. So the first one is to keep it on track. The second thing is they have people that are fully dedicated to developing the product. That means quicker updates and quicker bug fixes with dedicated staff. Will they be able to do it by themselves? Absolutely not. They'll still involve the extended community. They'll rely on it. When you talk about core functionality of CM, it's the OS. Performance optimizations, features. A subset of that is the kernel and device support.

Are they monetizing CM? Of course. Is it a bad thing? Maybe. In all seriousness it should be good for the product in the long run, and still keep what everyone knows and loves today. Root will still be available, quick updates will still be available. Easier installation will be available. I think this is huge. You know ho many people would probably install with an easier way to do it than current? One click install from stock? I think that's a great idea. I look forward to seeing how this progresses.
[One (M7) Original Android Development] fohdeesha:
Did you read the full post? I'm not very experienced with the methodology behind F/OSS, but the changes the CM team is attempting to make with licensing will very much drive away the majority of the contributors that make it what it is. Not to mention the removal of several features that make CM what it is, in order to get carrier/manufacturer support
[One (M7) Original Android Development] killman2659:
That is exactly what i did. Once i see what the new CM will become i will decide if i will use it again. I also don't like how he said that CM will eventually completely remove root by default. Basically, it sounds like they are going the opposite of what their original goals were. Of course, i possibly misread what he was saying.
[One (M7) Original Android Development] sumonfd:
After flashing this rom IMEI & baseband is showing unknown

but when i click on fastboot - fastboot get var all then IMEI is showing ok.

please help me.
[One (M7) Original Android Development] kennypow3rs:
Did you dirty flash from something else? Full wipe and flash again would probably fix it...
[One (M7) Original Android Development] sumonfd:
Please see the details i get from fastboot getvar all. Please help me

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.54.0000

(bootloader) version-baseband: 4A.17.3250.14

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 2.24.980.2

(bootloader) version-misc: PVT SHIP S-ON

(bootloader) serialno: HT358W90.....

(bootloader) imei: 35585905123......

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0714000

(bootloader) cidnum: HTC__039

(bootloader) battery-status: good

(bootloader) battery-voltage: 3731mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-d16dc66985

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

finished. total time: 0.046s
[One (M7) Original Android Development] wg25:
The last nightly is so small. Does it work without problems? Hang on boot or something like that?

Gesendet von meinem One mit Tapatalk 4
[One (M7) Original Android Development] picard47:
works just fine
[One (M7) Original Android Development] tiny4579:
Its because they removed focal.
[One (M7) Original Android Development] AJ:
is the IR blaster working yet ?
[One (M7) Original Android Development] cschmitt:
Not in the official builds.
[One (M7) Original Android Development] AJ:
anyone made a build that it work in ?
[One (M7) Original Android Development] dictionary:
Lord Clockans homebrew does in the other section. As does his build of aokp in that thread. Believe there are one or two other builds as well that support it. Lords homebrew is mostly all cm with some cherry pics.
[One (M7) Original Android Development] CheesyNutz:
https://play.google.com/store/apps/details?id=fr.xplod.focal

focal has made it to the market
[One (M7) Original Android Development] killman2659:
Cool, at least it will still be available. It is one very nice camera app.
[One (M7) Original Android Development] dyndragon:
Anyone notice that GPS isn't locking anymore? I use GPS toolbox and I get 0/0 satellites all the time now. Weird! 9/21 nightly. Was working fine before...

Logcat attached. Tried opening GPS toolbox and Google Maps.

Update: I reverted to 9/20 and I definitely have GPS locking satellites now. And then again confirmed that going to 9/21 GPS does not lock any satellites.
[One (M7) Original Android Development] fohdeesha:
Damn, you're absolutely right! I got 18 satellites in about 15 seconds previously, after flashing 9/21 I can't get a single one
[One (M7) Original Android Development] Chezbel:
I built from the latest CM source a few minutes ago and I got a lock in 32 seconds. Maybe something changed since yesterday, but I didn't notice any GPS related merges into git. I used GPS Status.
[One (M7) Original Android Development] fohdeesha:
Using gps status as well, can't pull a single sat on 9/21
[One (M7) Original Android Development] Bliszcur:
sorry for the noob question , how to disable 3 dot menu ?
[One (M7) Original Android Development] kennypow3rs:
I'm pretty sure its already disabled in cm and you just double tap home for menu.
[One (M7) Original Android Development] Chezbel:
Settings/buttons/Show Action Overview
[One (M7) Original Android Development] lotte67890:
GPS is back on the 22. build!
[One (M7) Original Android Development] LorD ClockaN:
Looking at gerrit, it never even left..

GPS I mean
[One (M7) Original Android Development] dyndragon:
GPS back to normal on 9/22 nightly
[One (M7) Original Android Development] snapilica2003:
Don't know if this was discussed before, but I'm getting terrible WiFi performance with these nightlies compared to stock Sense ROM.

I've got decent speedtests of 50Mbps / 6Mbps with the stock ROM. With CM I can barely get above 6Mbps / 3Mbps. Updates download in about 30 minutes (and most of the times fail).

I also get frequent disconnects (podcast downloads or nightlies downloads sometimes fail if phone goes in sleep mode). I've checked the settings and WiFi is set to be always on.

I've also checked with different networks, at work, at friends places, etc. Is this a known issue?
[One (M7) Original Android Development] lotte67890:
Which baseband are you running?
[One (M7) Original Android Development] snapilica2003:
4a.17.3250.14_14_10.39.1150.04l

I think it's the latest radio from 2.24 base. Should I try the Google Edition 4.3 4A.18.3263.15_10.38h.1157.04L baseband?
[One (M7) Original Android Development] cschmitt:
Reverted libloc_api commit in 9/22 build.
[One (M7) Original Android Development] lotte67890:
I used to have the 4a.17 and never had these problem. Now I am running 4.19... , though I have WiFi connection issues when first connecting to a WiFi even with known ones, with this ROM, in general it works better.
[One (M7) Original Android Development] MajorGaz:
I am having the same issue for a long while.

Im running the 4A.14.3250.13_10.33.1150.01L baseband.

PITA when trying to do an OTA update.
[One (M7) Original Android Development] jamiescott23:
Does anybody having issues with Volume wake? Really hate the power button, so enabled that one. In the first 60 seconds, it works but after than.. never.
[One (M7) Original Android Development] snapilica2003:
I've installed 4a.19 and it does seem to improve a bit. I do get short bursts of good wifi speed but it's never consistent. A speedtest has a short burst of 40-50Mbps then slows to a crawl at 4-8Mbps. It does seem that consistency is the problem.

This is very annoying as is one of the last things that is sub par compared to stock. The other thing would be the horrible audio quality over speakers (it seems BoomSound is not supported on this ROM yet).
[One (M7) Original Android Development] LiquidSolstice:
BoomSound is "supported". The only thing BoomSound refers to is the fact the phone has stereo out speakers. If both your speakers are playing, you very much "have" BoomSound.
[One (M7) Original Android Development] Theshawty:
Wifi connection is not related to the radio.

>> Sent from the abyss <<
[One (M7) Original Android Development] snapilica2003:
Well then it's "Beats Audio" then. Bottom line is the output from the stereo speakers is sub par over the stock ROM. There's a lot of clipping even at medium level volume. The stock ROM didn't clip the audio even at max volume.

It seems the next nightly will have some WLAN commits. Let's hope it will improve things.
[One (M7) Original Android Development] fohdeesha:
for you guys having wifi issues, in wifi>advanced are you sure you have "avoid poor connections unchecked? If not try that, I'm having zero wifi problems...getting my max line speed
[One (M7) Original Android Development] snapilica2003:
Well, for me that doesn't make any difference (except disconnecting from networks who have only one bar of signal, which is what it should do). If for others this setting does affect wifi performance then that's not the expected behavior.
[One (M7) Original Android Development] cschmitt:
It may be a router hardware/firmware/setting issue. I had a Asus rt-n16 and download speeds capped at 3Mbps, switch out the router to a rt-n66u and now get the full 60Mbps download of my internet connection.
[One (M7) Original Android Development] kennypow3rs:
If the sound isn't up to par why not go back to sense rom? Beats audio is nothing but an EQ app that runs settings in background when sound is played.There are many EQ apps in the play store that do the same thing...I personally find the sound too loud on stock roms but to each their own. I also don't get audio clips when the volume is at max...
[One (M7) Original Android Development] shortskoolbus:
Yes..doesn't work all the time.
[One (M7) Original Android Development] lotte67890:
Anybody else having issue updateing the nightlies with cyandelta and clockworkmod doesn´t "process ROM manager script"? Is there anything else witch has to be installed or configired?

thx

Lotte
[One (M7) Original Android Development] wpickel:
I used to use CWM. I am now using TWRP and having no issues with CyanDelta.
[One (M7) Original Android Development] DanRyb:
I found what worked for me is to have the screen on while streaming music to bluetooth. I stream music from Google Play Music to car bluetooth while driving (phone is plugged in and charging so for me screen on is not an issue). I downloaded an app that keeps the screen on when Google Play Music is on and now when I drive I get no audio skips or anything else. The sound is perfect for me now.
[One (M7) Original Android Development] Theshawty:
Did anyone else notice that CMXlog throws the following error message? "Error_04: Bad data or no nightlies for this device yet."
[One (M7) Original Android Development] killman2659:
I get that error too

BBQlog seems to work fine
[One (M7) Original Android Development] cristian2206:
whats the diff. from CM10.2 and GE ?
[One (M7) Original Android Development] sweetnsour:
CM10.2 is AOSP, while GE has some sense framework in it I believe (something to keep in mind if you flash custom kernels).

CM10.2 is very customizable and (from my experience) good on battery, while GE has pretty much no bugs and is very stable.

You should try both and decide for yourself :)
[One (M7) Original Android Development] alphamale99:
Just flashed the new stable version and then gapps. Did a wipe and the keyboard force closes so I can't do anything. I downloaded the newest gapps. Is anyone else having this problem?
[One (M7) Original Android Development] ainen:
The stable version is CM10.1. I'm assuming that you're using 4.3 gapps with it so that would be your problem.
[One (M7) Original Android Development] fpshah:
How do i take a screenshot on this rom.. sorry i tried everything.
[One (M7) Original Android Development] LorD ClockaN:
Power + vol -

Since forever
[One (M7) Original Android Development] popy2006:
thx for your answer.

i am also using google music while driving in car an also have the phone in an active car cradle.

The car dock software (car home ultra) i am using also keeps the display on.

but i have audio dropouts with all aosp roms :(

on sense/gpe based roms all is fine, no dropout.

Also on sense/gpe roms it doesnt matter if display is on or not.

what can ill do against those dropouts, ill want get rid of sense/gpe based roms and this is the only showstopper for me.

cu

pOpY

---------- Post added at 09:30 AM ---------- Previous post was at 09:27 AM ----------

Just one more question to you DanRyb: what radio/baseband version do you use?

I have updated my bootloader and radio a while ago to 4.3 base.

version of baseband: 4A.18.3263.15_10.38h.1157.04L

thx

pOpY
[One (M7) Original Android Development] raikesy:
I think since 4.3 the GE no longer has Sense framework, might be wrong though.
[One (M7) Original Android Development] bmtdan:
I believe a lot of the sense framework is gone but not all of it.

Don't qoute me on that though.

I think htc just removed enough so that we wouldn't be able to port our sense apps over to ge roms
[One (M7) Original Android Development] t3chn0s1s:
Could any regular users of CM provide any tips or tricks to getting CM to boot. I flashed the 9/23/13 nightly and Gapps - ran TiBU and restored only user apps and even rebooted a couple times... now all of a sudden I'm stuck on the boot animation. I was able to boot into recovery and wipe Dalvik and Cache... after optimizing all of my apps it throws me back into the CM boot animation. I don't get this. I did a bit of searching and saw this was last mentioned on like 9/06 or so. Anyone know what's up or if a slightly older build would make a difference? Or maybe it's a bad download?
[One (M7) Original Android Development] formula84:
Did you flash the full firmware.zip not just bootloader and radio? Other things in there (signal processor)... Its best to have everything at the sane version.
[One (M7) Original Android Development] kennypow3rs:
May have been a bad download. I had that issue reflashing worked. Not totally sure but to be safe I'd just wipe anyways. Try downloading 9/21, then update from inside the ROM via cm updater.
[One (M7) Original Android Development] fohdeesha:
get.cm has been wonky for me all day. won't load at all, or will barely load extremely slowly. I'm going to guess it served you an incomplete download.

I can't even get it to begin a download at all :silly:
[One (M7) Original Android Development] t3chn0s1s:
Thanks bro. It got to be so late last night that I didn't bother re-downloading... I'm gonna try my luck again today and see what happens.
[One (M7) Original Android Development] agalvin13:
I saw this

https://github.com/CyanogenMod/andr...mmit/6ad544896efefa03c4e77929944eb463c392a9fa

is group text / MMS still broken?
[One (M7) Original Android Development] DanRyb:
Hmm really wish I could help you. Leaving the screen on has been what helped me, which sounds like a kernel issue (?) but I'm not knowledge enough with tweaking kernel settings. I just know enough that making sure screen on is what helped me and I never get any "skips" or "pops" or "drops" or anything else. I'm using teaMsevenAOSP_v46 kernel is it matters to you at all and have been using their kernel for a while now. Are you using stock CM kernel? Also, I'm not using a car mode app but I wouldn't think that should matter. I'm using the radio of:

4A.18.3263.15_10.38h.1157.04P - at first glace I thought we were using the same radio but I notice mine ends in P and yours ends in L. Can't remember where I picked this up from. I'm thinking it came from the Google Edition conversion process - prior to going CM, I "fully converted" my phone to GE using the RUU in one of the threads here. Thinking the radio came with that and I'm pretty sure I left it alone.
[One (M7) Original Android Development] lostradiant:
Is anyone running into a bug where if you set your default keyboard is Swiftkey, after some time, the AOSP keyboard is automatically set to default? This doesn't happen if my default keyboard is set to the Google Keyboard. Also, I'm having another bug where if an app updates or I install an app on the Play Store, there is no notification for it.
[One (M7) Original Android Development] kennypow3rs:
Yeah it's still broken. I thought they weren't going to include it? When I get group MMS they're just blank. Its annoying. I just use textra for now works like a charm.
[One (M7) Original Android Development] agalvin13:
Pretty disappointing.

Vanir AOSP has this fixed. I just switched. Would have liked to run CM but this has gone on too long.
[One (M7) Original Android Development] kennypow3rs:
I could be wrong and I'm sure it's an easy fix and they're opting to NOT include it. I don't remember the reasoning behind it. Sucks though...
[One (M7) Original Android Development] bkosh84:
Why wouldn't they fix such a basic feature that ANY other ROM has working?
[One (M7) Original Android Development] tiny4579:
You have the source of this that it could be them opting not to fix it? It could be a hack. I haven't looked at vanirs fix.
[One (M7) Original Android Development] kennypow3rs:
Idk I did state that I could be wrong which I probably am. I just don't understand why every other rom has it (and had it a while) and cm doesn't. Sense, GPE ROMs and other pure aosp ROMs have it working.
[One (M7) Original Android Development] t3chn0s1s:
So, I narrowed down the root cause of my problem. I'm not sure if others have experienced this same phenomenon so I want to mention in hopes others may offer some info of use. So, I flashed SlimBean and while messing with the theme chooser setting a new theme my One rebooted and went into the endless boot animation screen just as it did with the 9/23 nightly of CM 10.2. If I press and hold the power button to attempt a fresh reboot it just repeated the same thing. So, I rebooted into recovery, wiped cache and dalvik and after the app optimizing was done it went right back into the boot animation again. So, this isn't a bad download or some other issue specific to CM. Not sure what it is but the Theme Chooser is definitely the culprit. Maybe it is is a CM related issue? I'm not sure if Slim is built from the same source but I'd venture to guess it is. Anyone else ever run into this?

Sent from my HTC One™
[One (M7) Original Android Development] t3chn0s1s:
Thanks for acknowledging... I honestly didn't think I was alone... searching for a subject so specific on XDA and finding corresponding results is a bit hit or miss and takes some lucky guessing as to WHAT to search for and hoping your terminology is broad enough to catch any posts that address the same sh1t.
[One (M7) Original Android Development] xBIGREDDx:
Could it be the theme you are trying?

I'm running a basic Holo Green theme, and have had no trouble with it. The other colors in that series also work fine.
[One (M7) Original Android Development] t3chn0s1s:
Maybe? But it happened with two completely different themes so I wish I could say that's it.

Sent from my HTC One™
[One (M7) Original Android Development] sabret00the:
You have to bare in mind that our maintainer isn't currently active. I'm just as frustrated, but for me it's the fact I can't do something as basic as have a conversation with loudspeaker on. But given the facts, we just need to be patient.
[One (M7) Original Android Development] Theshawty:
If it's so basic, why don't you fix it and submit it to Gerrit?

>> Sent from the abyss <<
[One (M7) Original Android Development] kennypow3rs:
What you mean not "active" lol? Why isn't he? Let's go ring his door bell and ask him what's the deal!
[One (M7) Original Android Development] Theshawty:
He's dealing with private stuff. He bought a house and that takes a lot of time. Jeez, get off the man's back.
[One (M7) Original Android Development] Ce:
Just a thought:

Apart from the fact that he has things to do at home...could CM going "commercial" have something to do with it? We don't know Codeworkx point of view.