yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] brendy:
Ive been running CM10.2 for a week or two now and have to say I love it, it is fluid and have only had very minor amounts of app closure, glass clock seems to be one. One thing I have found is that messaging seems to be taking up 30-40% of my batter life which is odd as I use it maybe once or twice a day max which made me think about using a task manager, I presume when this rom was made, there is no inbuilt task killer like the 4.1.2 stock rom (long press gives the options to swipe open apps or click on piechart to empty ram).

That would be great if it was available. Keep up the fantastic work.
[One (M7) Original Android Development] tjsooley:
Anyone know the status of usb host? I am on 9/10 and USB host is still not working. :(
[One (M7) Original Android Development] hillbeast:
Nothing can match the Sense camera. Simple as that. Focal is getting there, but it Sense still has a significant advantage, especially in quality on that front camera. If camera is important, stay on Sense or GE.

Don't use a task manager to solve battery issues. Task managers actually are worse for the battery because then the app has to reopen itself and use even more CPU cycles.
[One (M7) Original Android Development] J0ker 82:
Guys I have a problem with whatsapp PTT audio. After i do a PTT it sounds VERY low...

Do you have any idea how to fix it?
[One (M7) Original Android Development] sabret00the:
Today's build has no sound for WhatsApp voice notes.
[One (M7) Original Android Development] J0ker 82:
I tried last build and PTT messages works for me...just with a low audio volume
[One (M7) Original Android Development] formula84:
I don't see any commits for the m7 that would impact sound... The only commits I see are kernel side but they are for another device DNA that share the kernel in some regard but when built for the m7 it should ignore anything done in the kernel source for the DNA I believe.
[One (M7) Original Android Development] adyscorpius:
Speak into the rear mic. Then it is as loud as you want it to be.
[One (M7) Original Android Development] fohdeesha:
flashed the nightly last night, 9/11, and woke up today and my internal storage was gone. pictures, ,music, app files, gone. WTF?

what the hell do I do to get this back? why the hell did it do that?
[One (M7) Original Android Development] kennypow3rs:
No idea. Did you wipe it by accident? What recovery? If TWRP did you hit wipe data or advanced wipe? I've done this before by accident in TWRP but never had my data wiped by just flashing a ROM update or a nightly on top another one.

Really think back, its very possible you accidentally wiped. As far how to recover it no idea....

Use a file explorer to look in both sdcards the legacy and the emulated (0) to make sure its really gone.
[One (M7) Original Android Development] fohdeesha:
Absolutely not. Wiped cache and dalvik only in clockwork like I always do. it booted into the new nightly fine when I was done and all my storage was there, I even viewed the gallery before going to bed, and everything was there. I did not reboot or power cycle the phone at all, and plugged it in to charge when I went to bed. woke up and now when I browse to internal storage, there was only one or two folders there. Same in both emulated and legacy.

I've pretty much accepted I'm not going to get any of it back, the only things that weren't backed up were 5 or 6 pictures I have taken since I last did a backup of the internal storage.

No idea what happened and it's kind of worrying me that it's going to happen again
[One (M7) Original Android Development] konman795:
I am so paranoid about losing my pictures... I have it set up to upload to my gdrive and dropbox on data connection.
[One (M7) Original Android Development] LorD ClockaN:
USB OTG fix has been found and working!

link to patch:

http://review.cyanogenmod.org/50323
[One (M7) Original Android Development] goldenratio:
This really sounds to me like filesystem corruption, and/or failing flash storage in your device. If it were me I'd back up what's left, and then format /sdcard from recovery.
[One (M7) Original Android Development] _saiko:
Anyone tried playing some graphic intensive games?

I tried to play HungrySharkEVO and it is crashing. Seems like a memory usage/alloc issue.

I'm on the 9/12 nightly, SOFF/unlock via revone using the 3.06 based firmware (radio 4A.18.3263.15_10.38h.1157.04L).

Here's the log:

(...)
I/Unity ( 6600): LoadGameMonolithic: Master scene loaded.
I/Unity ( 6600):
I/Unity ( 6600): (Filename: ./Runtime/ExportGenerated/AndroidManaged/UnityEngineDebug.cpp Line: 54)
I/Unity ( 6600):
I/Unity ( 6600): destroy LoadingScreen
I/Unity ( 6600):
I/Unity ( 6600): (Filename: ./Runtime/ExportGenerated/AndroidManaged/UnityEngineDebug.cpp Line: 54)
I/Unity ( 6600):
W/Adreno200-GSL( 6600): <sharedmem_gpumem_alloc:1286>: sharedmem_gpumem_alloc: mmap failed errno 12 Out of memory
E/Adreno200-GSL( 6600): <ioctl_kgsl_sharedmem_alloc:1458>: ioctl_kgsl_sharedmem_alloc: FATAL ERROR : (null)
I/ActivityManager( 718): Process com.fgol.HungrySharkEvolution (pid 6600) has died.
I/WindowState( 718): WIN DEATH: Window{41f86558 u0 com.fgol.HungrySharkEvolution/com.jirbo.unityadc.UnityADCActivity}
W/WindowManager( 718): Force-removing child win Window{426ade70 u0 SurfaceView} from container Window{41f86558 u0 com.fgol.HungrySharkEvolution/com.jirbo.unityadc.UnityADCActivity}
W/ActivityManager( 718): Force removing ActivityRecord{4218bab0 u0 com.fgol.HungrySharkEvolution/com.jirbo.unityadc.UnityADCActivity}: app died, no saved state

Also, somewhere around 8/30 nightly i think, root can't access /storage/emulated/0, but only through /mnt/shell/emulated ?
[One (M7) Original Android Development] kennypow3rs:
I havent gotten HungrySharkEvo to work on ANY 4.3 roms, (sense, gpe and CM 10.2). It only works on 4.2.2 for me.
[One (M7) Original Android Development] tiny4579:
What did you flash from? It's possible that they didn't get moved to the new sdcard location? Are they in /data/media?
[One (M7) Original Android Development] fohdeesha:
flashed from the previous nightly as I have been. Like I said after flashing it booted and operated perfectly fine, I could still see and access all my files. While I was sleeping they disappeared. I've dealt with flash block corruption previously on an S1 and know what that's like, this is not it. I formatted the internal storage and copied my files back over, they're all operating fine now and I can get to them. really have no idea what would have made that happen....
[One (M7) Original Android Development] cschmitt:
Just had another random reboot, second one in a couple of days.

[ 3305.854783] c0 0 Kernel panic - not syncing: swapper/0 PC:dpm_drv_timeout+0x50/0x60 LR:unwind_frame+0xc0/0x46c
[ 3305.955195] c0 0 [MDM][COMM] mdm_panic_prep: setting AP2MDM_ERRFATAL high for a non graceful reset
[ 3306.355928] c0 0 set_restart_reason: set restart reason = 776655aa
[ 3306.355958] c0 0 set_restart_msg: set restart msg = `KP: swapper/0 PC:dpm_drv_timeout+0x50/0x60 LR:unwind_frame+0xc0/0x46c'
[ 3306.355989] c0 0 Rebooting in 5 seconds..
[ 3311.364565] c0 0 Restarting Linux version 3.4.10-CM-g54ed6f4 (build02@cyanogenmod) (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Thu Sep 12 04:24:39 PDT 2013
[ 3311.364595] c0 0
[ 3311.364626] c0 0 Going down for restart now
[ 3311.364656] c0 0 msm_restart: Kernel command line: poweron_status=1 reset_status=0 board_m7_ul.disable_uart3=0 diag.enabled=0 board_m7_ul.debug_uart=0 userdata_sel=0 androidboot.emmc=true androidboot.pagesize=2048 skuid=0 ddt=20 ats=0 dap=6 androidboot.lb=1 uif=S000 td.sf=0 td.td=0 td.ofs=328 td.prd=1 td.dly=0 td.tmo=300 hlog.ofs=628 un.ofs=694 imc_online_log=0 androidboot.efuse_info=4FSL androidboot.baseband=4A.19.3263.13 androidboot.cid=CWS__001 androidboot.devicerev=3 androidboot.batt_poweron=good_battery androidboot.carrier=ATT androidboot.mid=PN0712000 androidboot.keycaps=qwerty androidboot.dq=PASS androidboot.mode=normal androidboot.serialno androidboot.bootloader=1.44.0000 lscd=0x1 wificd=0x1 androidboot.nledhw=0 androidboot.ddrmid=(0x6) acpu.footprint=0B010101 zygote_oneshot=on kmemleak=off rpm_debug.enable=0 console=ttyHSL0,115200,n8 androidboot.hardware=qcom user_debug=31
[ 3311.364778] c0 0 msm_restart: restart by command: []
[ 3311.364809] c0 0 Powering off MDM...
[ 3313.368227] c0 0 Power off MDM down...
[ 3313.368227] c0 0
[ 3313.368258] c0 0 [K] Restarting Linux version 3.4.10-CM-g54ed6f4 (build02@cyanogenmod) (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Thu Sep 12 04:24:39 PDT 2013
[One (M7) Original Android Development] SleemLDJ:
does this mean OTG will now work on cm10.2?

http://review.cyanogenmod.org/#/c/50323/
[One (M7) Original Android Development] LorD ClockaN:
Yes, read at least 1 page back..
[One (M7) Original Android Development] davidlaugor:
Hello!!

i installed this ROM yesterday. All works good!! but only i have a problem. With viber and Tango apps, don't find me all the contacts i have. With whatsapp or chaton or line, dont have this problem, but with viber and tango, only find me of my agenda a few contacts, and i had with arhd more.

I transfer my contacts by .vcf file, beacuse i like to registred all my phone contacts in my phone memory, and after that this .vcf file i sync to the cloud. and i imported all my contacts by a .vcf file to my phone yesterday with cyanogenmod 10.2, this can be the problem???

i dont know how to fix it.

Thanks!!
[One (M7) Original Android Development] davidlaugor:
And other thing, If google account activated, then only is google is avaiable for saving contacts? i can not save in my phone memory??
[One (M7) Original Android Development] popy2006:
bump...
[One (M7) Original Android Development] sabret00the:
Anyone having issues with WhatsApp messages not coming through until you go into WhatsApp?
[One (M7) Original Android Development] raulongo:
It happens to me in my Volvo S60 too. Bluetooth audio skips like half second, randomly. It's a bit annoying. I tried with Sense and nothing happened. Maybe we have to wait for that to be solved...

---------- Post added at 01:29 PM ---------- Previous post was at 01:24 PM ----------

Everything is A-OK here. WhatsApping with my GF and everything seems to be fine.
[One (M7) Original Android Development] jasalta387:
Hi there,

Still me having troubles to get my phone on any network on the WCDMA 850MHz band.

I flashed the GE radio (4A.18) and got no differences. I even did a factory reset and reverted to CM 10.1 to no avail.

I'm about to conclude that my m7ul (mid PN07100) does not have the hardware to run on that band. This is puzzling because in all books it says that this device does support that frequency band.

Anything you can think of? I'm S-OFF, but did not change yet to supercid (which is irrelevant imho).
[One (M7) Original Android Development] ainen:
I saw someone mention in another post that the green tint on the front facing camera is gone. However, I tried this ROM within the last week and it was still present. Has a commit been merged that fixes this?
[One (M7) Original Android Development] _saiko:
Seems the green tint is still there on the front camera.

On a different note, the loud ringtone/notification issue is also still present. Of the approx 7-8 steps of loudness the last 4 are identical while the lowest isnt really that silent.
[One (M7) Original Android Development] nonmindo:
Why are there NO "known issues" lists ANYWHERE for 10.2, some people don't have time to be searching and reading through every page keeping track of what has been fixed, then broken again and then fixed again. Obviously there are still issues and thats to be expected, but a simple list of what might be expected would nice, especially when you are looking at other roms that use a CM base and in their "known issues" section they say "any issues found in CM10.2" and link to this page.

Do both cameras work without issue?

Can you record Full HD?

Is IR still missing the needed files to work on CM?

Are there any issues with audio routing of any sort?

Does A2DP work without issue? (can you connect to car stereos and bt speakers)

Is BT 4.0 BLE working?

Are there any signal / wifi issues?
[One (M7) Original Android Development] kennypow3rs:
Because its easy to search and every one knows its still nightly status. If you don't have time to search you don't have time to root and flash roms...

Lord has a homebrew 10.2 build with working IR.

Bluetooth works fine with car stereos.

Full HD works fine on front and rear cam.

Try out A2DP for yourself and let us know.

http://mobile.10.2.cmxlog.com/?device=m7ul
[One (M7) Original Android Development] nonmindo:
I understand these are nightlies and searching isn't that easy when you're on mobile, it is also time consuming, plus if you don't know what the known issues are how can you search to see if "x" has been broken/repaired. I have been around for quite a while and the is the only thread I have been to in quite some time that does not list the known issues. Posting the changelog also doesn't do much except state what was recently fixed.

I'm also not the only one that has asked for a "known issues" post either so it's not like its something that is only desired by one user

I don't know where this snooty attitude of "if you don't have time to search you don't have time to root and flash roms" comes from either.

Some people don't have the time to sit and read/search through 200+ pages of posts, prior to switching to a rom to make sure it will work for them as a daily, and I don't want to hear the "if you need a daily then you shouldnt be flashing nightlies" garbage either, I have ALWAYS been able to find out what known issues there are for a rom, then decide if its at daily driver or not, then also using the "known issues" post been able to tell if it will work for my individual daily driver needs, without having to spend time searching through hundreds of posts. 90% of the time after the initial big issues are taken care of the nightlies dont usually get worse or break previously working things, though it does happen from time to time

It takes a great deal of time to come from one rom to another, especially if going from sense to aosp base

make sure you have space on your storage for all of the Ti backups

you have to back up all your apps with titanium

find and download the new rom you want

wipe everything

install the rom

setup all of your accounts

restore all the apps

set the settings of the rom

and in the case of this rom, unless you have a bunch of time to read 200+ pages on top of all of the above things, hope that everything works because no one is willing have common courtesy and post a small list on the OP of what is known to be broken.

I do thank you for answering my specific questions about the things I was concerned about.
[One (M7) Original Android Development] LiquidSolstice:
It's funny that you should talk about "snooty attitudes".

The thing about "nightly" builds is that they change....every night. If you need to be further spoonfed, that means that what works today might break tomorrow. What breaks today might be fixed tomorrow. Who's going to maintain that list? You? The automated buildbot that compiles and uploads these things? The CM team? Random users? Things change in the nightly builds so fast and sometimes for reasons that aren't clear at first. There is no "hey this works" and "hey this doesn't work" list because that list will change. If WiFi works today, who's to say some level of optimization in the kernel tomorrow doesn't accidentally break it?

No one here is concerned about what you've "always" been able to do. We seriously don't care. Just because things in this thread aren't the way you're used to doesn't mean you have to throw a tantrum over it. If you don't have the time to read or search, then we don't have the time to hold your hand and tell you what you want to know.

And seriously? That idiotic list of things that you just HAVE to do? If the rooting and reflashing game is starting to become hard work to you, please do us all a favor and go away. You are not contributing a single piece of code to any of the builds you're flashing, so please don't piss and moan about how "hard the flashing process is". I mean, come on. Cry me a river.

You either search yourself or before you go through that list that seems to be causing you so much anguish, you make a very simple and respectful post asking if things have improved and if someone who's already flashed the nightly can tell you, boom, you have your answer.

You *want* so much but you give nothing, and you can't even give an ounce of thought to your own desires and why they're unrealistic. You're the generation of XDA users that's killing this forum, and it actually disgusts me that someone who's been given so much for free still has something to moan about. If you don't want to guess what is working/not working or test for yourself, you know where the Stock based Sense ROMs are. Please use those until you're ready to sit at the dinner table with the adults.
[One (M7) Original Android Development] kennypow3rs:
To be honest I didn't have an attitude but as LS things change daily which is why I offered you the change log which shows what's happening overnight. Figured it could help you. But its too many things to list. The ROM is stable enough for a daily but still not to be considered stable or even a release candidate because there are many things they're working on. Pretty much everything you need is working at the moment. Group text isnt but there's free text apps for that. Proximity is funky too while on a call. I would think since you been around since 2008 you'd know enough to find what you need on your own...
[One (M7) Original Android Development] nonmindo:
Post hidden

First off, I understand fully what a "nightly" is, and further I understand that one thing might work one day, then be fixed the next, as I stated previously "...the nightlies don't usually get worse or break previously working things, though it does happen from time to time"

Second, I wasn't asking for a list for myself only, I was trying to get one posted up for others that have asked as well, to help people as that is just as important as actually doing the development on the ROMS/Kernels/Mods, It wasn't a request for EVERY thing that has been broken and fixed then broken again, it was a simple request for what major outlying issues there still are, Like IR for example, while yes, in this instance at this point its pretty much common knowledge that IR will only work with the proper files that HTC had to release(as I learned earlier, thanks to kennypow3rs, there is a homebrew with it), but its still something that has not been working from the beginning, and someone that may be WELL versed in programming on another device like say, Samsung, might have just come over to the HTC side of things and need / want to know what major things are broken in case they might perhaps be able to repair the issue...

Third, idiotic list of things that you have to do?? really? because I'm sure there are a bunch of things you NEED to have working on your device, just because your list might be different than mine doesn't negate the fact that it's time consuming. There is NOTHING hard about the "flashing game, nor did I EVER say that the "flashing process is hard", simply that it is TIME CONSUMING. If MY desires are so "unrealistic" then why is it possible for so many OTHER developers and ROM maintainers to list the "known issues" for their roms?

As far as being "someone who's been given so much for free still has something to moan about". I NEVER ONCE said that the developers (CM Team) were slacking on anything nor did I ever say that they OWED me anything, I made a request for someone to list the known things to save time, not because I don't know what I'm doing, or that this or that is TOO HARD...Since CM 4 I have Donated to the CM Team MULTIPLE times, as well as to countless other developers over the years for their hard work and dedication. Some people contribute in other ways than just providing code, some like to know whats broken so they can advise others who may be interested in a rom on what issues they may encounter, someone who may be even less educated than themselves.

I remembered a thread from my SIII, that happens to have a "known issues" section....Do you know who created the OP? Cyanogen (Steve Kondik) himself.. I think that if he would take the time to post up a "known issues" section that, maybe....just maybe, he understands the value behind having it posted, clearly, YOU do not

OFFICIAL CM10 GSIII "known issues"

Ohh, look, ANOTHER "known issues" post in an [OFFICIAL] CM thread

OFFICIAL CM10.2 GS4 "known issues"

pfft..."unrealistic"
[One (M7) Original Android Development] phab3k:
when I flashed this morning's build it uninstalled gmail for sure and possibly some other apps, gmail for sure, but not 100% about the others.
[One (M7) Original Android Development] nonmindo:
Thank you for still assisting after the unfortunate reply from LS. Yes, you are right, being a Sr. Member I should, and I DO know enough to find what I need, however, Time is not something I have, and not just me, there are others in situations like mine, where they know how and what needs to be done to find out what they need, but simple don't have the time. I apologize for assuming your previous reply had any implied attitude.