yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] herpehancock:
Figured as much. I'll leave it up to the devs haha thanks.
[T-Mobile, Samsung Galaxy SIII] joshnichols189:
Home screen rotation is for the Nexus 7. It is a maintenance release, there isn't really anything outside of expandable notifications with one finger and some Nexus 7 stuff.

Sent from my SGH-T999
[T-Mobile, Samsung Galaxy SIII] t_hsieh:
Just saw that audio routing for dock mode is in the next nightly. Looking forward to that working with my iBolt car dock.
[T-Mobile, Samsung Galaxy SIII] Cuban Cigar:
Hi, Where did you get (liquidsmooth rc4)???????? Im running the RC 3 and haven't seen any update yet......Thanks
[T-Mobile, Samsung Galaxy SIII] Exel:
10/10 builds are getting pushed out now, stay tuned. :D
[T-Mobile, Samsung Galaxy SIII] sano614:
Does anyone else's keyboard lag when composing text messages? It only happens with texts.. browser, talk, xda are perfectly fine..
[T-Mobile, Samsung Galaxy SIII] RonDigital828:
10/10 still has not hit yet.....so sad
[T-Mobile, Samsung Galaxy SIII] pezlomd:
Ive been in stock land for sometime now.. how has progress been for cm10? Anything solid?
[T-Mobile, Samsung Galaxy SIII] xidica:
I have the iBolt and have had no issues with audio from car dock mode. Started using CM10 on 9/30 nightly, currently on 10/5 or 10/6. What is the fix for?
[T-Mobile, Samsung Galaxy SIII] t_hsieh:
I wanted the ability to get the audio to route from the phone to the car. I should double check to see if this is what the fix is for, I just assumed that it was to allow routing to the car's audio system.
[T-Mobile, Samsung Galaxy SIII] SlakWReX:
This belongs in a pm sir. Please pm him.
[T-Mobile, Samsung Galaxy SIII] ew:
10/10 nightly is up
[T-Mobile, Samsung Galaxy SIII] immunityx:
4.1.2?
[T-Mobile, Samsung Galaxy SIII] xanderdad:
Yes.
[T-Mobile, Samsung Galaxy SIII] sarni84:
Is anyone running 10/10 nightly with ktoonsez kernel? If so is everything good? Didn't know if the change to 4.1.2 was a kernel change or what not. If so it probably is not compatible till ktoons updates
[T-Mobile, Samsung Galaxy SIII] Shayd93:
Do I have to wipe everything for every install or just flash new version
[T-Mobile, Samsung Galaxy SIII] paullu:
I just updated to 10/10 new build and found map keep Freeze then crashed
[T-Mobile, Samsung Galaxy SIII] xidica:
Try clearing data associated with maps. Fixed for me after seeing the issue on a previous nightly.
[T-Mobile, Samsung Galaxy SIII] tomster92:
Anyone having issues with mediaserver keeping the phone awake? Typically when playing music. Is it a cm issue or is it just me?
[T-Mobile, Samsung Galaxy SIII] chrisram88:
Daily driver!
[T-Mobile, Samsung Galaxy SIII] aNYthing24:
The phone has to be awake when playing music.
[T-Mobile, Samsung Galaxy SIII] kingpongg:
i have the ibolt too but my audio has never re-directed to the car dock with CM10. i know there have been a few commits concerning this but figured it was still a work in progress. Did you have to do anything "special" to get it working? i'm currently using the 10/10 nightly.
[T-Mobile, Samsung Galaxy SIII] oblib__:
For whoever runs into this in the future:

This was a result of restoring some system settings through Titianium Backup from JB AOKP to other Jelly Bean ROMs. Safest is just don't restore any, though many of them do work okay.
[T-Mobile, Samsung Galaxy SIII] Exel:
Damn CM10's 10/10 keeps failing when downloading. :( /lamesauce.
[T-Mobile, Samsung Galaxy SIII] xidica:
I use car home ultra, in its settings you just enable audio out via the dock. Haven't tried vanilla car docking without car home ultra.
[T-Mobile, Samsung Galaxy SIII] elesbb:
Alright i have posted about this issue with the latest nightly builds. But i thought it would have been reverted by now.

Here is what i want you to do. Go into developer settings, enable hold-back-to-kill, go into tapatalk, i have a shortcut to our device on my homescreen, but open up Q&A let it settle about 10 seconds. Now press and hold the back button, you will see it only goes back to the General, Q&A, Accessories, Android Development, Original Android Development, Themes and apps page and never truly kills the app.

WHY was this EVER touched again? It was working PERFECTLY! This is driving me insane. Can someone please enlighten me with a legitamate reason for touching this code? And can we PLEASE get it reverted?

EDIT: Its not just with tapatalk either, happens with a lot of apps. Market, Google Maps, are two that i have noticed in addition to tapatalk.
[T-Mobile, Samsung Galaxy SIII] PennStater:
What does that mean?
[T-Mobile, Samsung Galaxy SIII] ceroglu:
I am on 10/10 build right now it seems to be trouble free for me.
[T-Mobile, Samsung Galaxy SIII] nick1217:
Kills app for me on 10/9. Just did it...
[T-Mobile, Samsung Galaxy SIII] kingpongg:
With JB you have more advanced notifications. with 4.1.1 you used to 2-finger swipe down to expand the notification and see more details/options. With 4.2.2 you can swipe down with 1 finger. It seems you still need to 2-finger swipe up to condense the notification.
[T-Mobile, Samsung Galaxy SIII] elesbb:
Yeah its weird sometimes it works sometimes it doesn't.

thank you for testing though !
[T-Mobile, Samsung Galaxy SIII] kingpongg:
I tried with 10/10 just now and it kinda works for tapatalk. It did go back twice really quickly and then killed the app. I also went into the market->my apps and long pressed. It killed the market app no problem. Tried with gmail and g maps. no issues.

What's the last nightly you tried?

(btw- thanks. i never knew where to enable the hold-back-to-kill setting.)
[T-Mobile, Samsung Galaxy SIII] aNYthing24:
You don't need two fingers to close it. Swipe down first, then swipe up. It'll close.
[T-Mobile, Samsung Galaxy SIII] kingpongg:
Odd. I tried with care home ultra and it still didn't redirect. In the settings, it says my device isn't compatible. Which nightly are you running?
[T-Mobile, Samsung Galaxy SIII] shinigenEddy:
For those of you wondering or unsure of what the new one finger notification swipe does, here is a video that explains it very well!

http://www.youtube.com/watch?feature=player_embedded&v=a6dzMzklEd4
[T-Mobile, Samsung Galaxy SIII] Exel:
For anyone that is having problems downloading 10/10 nighty, here: https://www.dropbox.com/s/hhosnfa7utc76wh/cm10.zip

Took me forever. O.O
[T-Mobile, Samsung Galaxy SIII] kingpongg:
So it does. Cool. Thanks for the correction!
[T-Mobile, Samsung Galaxy SIII] stonew5082:
I'm going insane trying to figure out why max cpu keeps reverting down to low frequencies. Any ideas?
[T-Mobile, Samsung Galaxy SIII] qpinto:
anyone else getting random reboots and screens of death with 10/09 and 10/10? something that i have experienced this morning. clean installed both builds too.
[T-Mobile, Samsung Galaxy SIII] URPREY:
Stock kernel? A guy on G+ was having the same issue with a non-stock kernel on his N7 and RomToolBox. Not sure what the actual cause was but he was having this same issue and he believed it to be an issue with RomToolBox
[T-Mobile, Samsung Galaxy SIII] stonew5082:
Stock kernel. No matter if I use setcpu or anything else. I'm freaking out. Ben an issue for a long time.
[T-Mobile, Samsung Galaxy SIII] ew:
Internet Calling Question

I have setup and internet calling account in the phone application. In the "Use Internet Calling" setting, there are three choices:

For all calls when data network is available

Only for Internet Calls

Ask for each call

The first and last item are obvious. If I choose "Only for Internet Calls", is there a way to dial an internet call?

I have searched everywhere and can't figure it out.

Thanks,
[T-Mobile, Samsung Galaxy SIII] RonDigital828:
I don't know what's it about either but I use groovie IP app and its OK but I'm wondering if this option is better
[T-Mobile, Samsung Galaxy SIII] EegoGenre:
I'm coming from the 10/09 build. Is it recommended to do a clean flash being that its going from 4.1.1. to 4.1.2.?
[T-Mobile, Samsung Galaxy SIII] kingpongg:
I flashed dirty from 10/7 and it's been fine all day so far. You can always clean flash later if you have weird issues.
[T-Mobile, Samsung Galaxy SIII] bellrb19:
Clean flash is always "recommended" with nightlies (especially with change in android versions). Whether or not you need to, I am not sure. I would say make a backup, try dirty flash, and do a clean one if there are any odd issues.
[T-Mobile, Samsung Galaxy SIII] stonew5082:
It was necessary for me. it went nuts. clean wipe fixed er'ting. except my cpu max changing randomly.
[T-Mobile, Samsung Galaxy SIII] elesbb:
Hold back to kill doesn't always work. It was working perfectly with my mod and everything then I rebooted and it stopped working. I wish they'd just revert the code to the 9/15 code.

Pair the 9/15 build with the new features from the 10/10 build would be just perfect.

---------- Post added at 11:01 PM ---------- Previous post was at 10:32 PM ----------

Also noticed it fails to kill it if you leave the app open for a little. Like with google maps, if i am not moving, and just sitting there, and i dont touch the screen for approx 10 seconds, and then press and hold the back button, it just registers a normal back action. But if i simply touch the screen, then press and hold the back button, it kills it -.- again why must they change the code when it was working perfectly?

---------- Post added at 11:19 PM ---------- Previous post was at 11:01 PM ----------

So thats really strange, when i tap the screen, not neccessarily clicking on something, it allows the app to be killed. I wonder if it sets the onscreen app to like a "background" process when there is nothing tapping the screen.
[T-Mobile, Samsung Galaxy SIII] ipnekgs:
I have tried all the steps you have mentioned to replicate your issue. My "hold back key" to kill an app works always.

You might have a hardware issue.
[T-Mobile, Samsung Galaxy SIII] dave2metz:
Does anybody have a mirror for the 10/10 nightly? I keep getting redirected when I go to get.cm . I have tried many times, but nothing. Even Goo Manager is not working correctly for me. Can anyone help or give me a mirror? Thanks a lot.
[T-Mobile, Samsung Galaxy SIII] aNYthing24:
Yep, I have no issues with it.
[T-Mobile, Samsung Galaxy SIII] sarni84:
Yes!!! i have tried a few times also one said 9 hours! the other said 11! and this is on my computer...can anyone throw up 10/10?
[T-Mobile, Samsung Galaxy SIII] aNYthing24:
Someone posted a mirror a couple pages back.

http://xdaforums.com/showpost.php?p=32633982&postcount=5668

---------- Post added at 06:44 PM ---------- Previous post was at 06:41 PM ----------

I added it to my Dropbox as well, if it goes down: https://www.dropbox.com/s/wcitauu0nsq8j1a/cm10.zip
[T-Mobile, Samsung Galaxy SIII] sarni84:
thank you i appreciate it:good:
[T-Mobile, Samsung Galaxy SIII] elesbb:
If it were a hardware issue, it wouldnt work on 9/15 then. Which it works perfectly on.

And i am using a modded framework-res.apk to change the delay time from the stock 2.5 seconds to .5 seconds. But that shouldnt be an issue at all. Plus when i revert back to the stock framework-res.apk it still doesnt fix it.

But when i flashed the modded framework it was working for awhile, no issues, then i rebooted and it stopped working again.

The part that bothers me the most, is WHY was it even changed? They seem to be doing a lot of that lately, changing perfectly fine code.
[T-Mobile, Samsung Galaxy SIII] sarni84:
Anyone have gapps fc on 10/10 ? And every time I go into market and try to DL something it just closes right out into home screen. I fixed perms. And fresh install
[T-Mobile, Samsung Galaxy SIII] :
Nope none of those issues ^
[T-Mobile, Samsung Galaxy SIII] gr4p3s:
Why do you want hold back to kill? It's not something you should be using regularly anyways. Not using an app? Swipe it away from the Recent Apps screen and let Android take care of it. 99% of the time, it works great.
[T-Mobile, Samsung Galaxy SIII] :
Question anyone who is using kt kernel, does some of your apps randomly close, and do you ever experience reboots?
[T-Mobile, Samsung Galaxy SIII] elesbb:
Yes ive had that with a bunch of roms not just cm10. What i did was redownload gapps and flash again clearing cache and dalvik then fixing permissions. Havent had it since i redownloaded.

Because its much easier than what you mentioned. Auto kill apps are bad. But me killing the foreground app is fine for it. Plus its a feature that I'd like to have working properly again.
[T-Mobile, Samsung Galaxy SIII] aNYthing24:
You've been obsessing over it though. Almost every other post you make is about it. It'll be fixed when it'll be fixed.
[T-Mobile, Samsung Galaxy SIII] elesbb:
I'm obsessing over it because it shouldn't need to be fixed when its been working perfectly before. Why are we trying to reinvent the wheel? Plus I'm getting a little pissed because a few people complained and carried on about the streaming using a2dp over Bluetooth to their cars or whatever. And it gets fixed in like two nightly builds. But I post log cats , diagnose the hell out of my issues, contribute to this site a lot more than some, and yet I get ignored.
[T-Mobile, Samsung Galaxy SIII] RonDigital828:
Perhaps they don't know how to fix it..yet....or its just user error....I tried it after I saw your post and it works for me....sorry that's my best answer
[T-Mobile, Samsung Galaxy SIII] elesbb:
Thank you. That's prolly the most reasonable answer I received from anyone.

It would be nice if I could talk directly with developers.
[T-Mobile, Samsung Galaxy SIII] RonDigital828:
Can u add the pop up n play feature to video player like stock ROM....I know its sounds crazy but its a nice luxury to have
[T-Mobile, Samsung Galaxy SIII] jpeps:
4g icon

Dose this have 4g icon??
[T-Mobile, Samsung Galaxy SIII] death1246:
When you fix something chances are something else will break. They are nightly aka beta releases not daily drivers.

It will be fixed when it gets fixed. And if it does something else might break.
[T-Mobile, Samsung Galaxy SIII] aNYthing24:
The simple reason is that A2DP is much more important than hold back to kill app. The CM team has to prioritize. How many people use A2DP daily, compared to hold back to kill an app? Hold back to kill app -- which by the way I have no issues with while I tested it -- isn't a feature that's important as working Bluetooth.

---------- Post added at 08:56 PM ---------- Previous post was at 08:55 PM ----------

This. Complaining about it over and over again doesn't do any good.
[T-Mobile, Samsung Galaxy SIII] elesbb:
OK I get they are nightlies. With that being said, and I've said this before, when one thing works you don't go changing it. And it goes back to the Bluetooth. That broke when they changed something but hey it got changed back. I just feel like I'm being ignored and that my efforts for diagnosing it just get shot down. I guarantee if anyone else had an issue for the past 3 weeks worth of nightly builds, and they have gone through and diagnosed it and done the proper things to resolve it, they would be just as upset as I.
[T-Mobile, Samsung Galaxy SIII] kulzboy:
Hmm im having a weird bug when using poweramp. If i enable the beep sound with the headphone buttons, the sound would automatically go from vibrate to full sound whenever i press it or skip a song from the lock screen, which is why i almost got my phone taken in class earlier
[T-Mobile, Samsung Galaxy SIII] joshnichols189:
Try the app stick it in the market. Same thing.

Sent from my SGH-T999

---------- Post added at 08:34 PM ---------- Previous post was at 08:31 PM ----------

Does anyone else have a problem with the low storage error happening when settings > storage doesn't add up to 12GB?

Sent from my SGH-T999
[T-Mobile, Samsung Galaxy SIII] elesbb:
Mine says 12.05 GB what's yours read ?
[T-Mobile, Samsung Galaxy SIII] gr4p3s:
How is hold back to kill not as bad as an auto kill app? Both kill the app prematurely, which could lead to instability as has been warned by official Android devs.

You're being obsessive over it. Your phone is not going to gain much (maybe even less) battery life by doing this instead of the official way of doing it.
[T-Mobile, Samsung Galaxy SIII] joshnichols189:
It says 12.05 but the data breakdown beneath it does not add up to 12.05 and I get the low memory error.

How are they even remotely similar? An autokill app kills an app as soon as it starts. Hold back to kill kills only your foreground when YOU tell it to.

Sent from my SGH-T999
[T-Mobile, Samsung Galaxy SIII] supitskevin:
Is the SOD an issue for only AOSP roms?
[T-Mobile, Samsung Galaxy SIII] gberger42:
Sometimes, when locked and left alone, my phone screen turns on, and then off after 3 secs, it does this about 5-10 in a row, and does it 3-5 times per day

WTF??

Using october 5 nightly but have been having this issue for well over 3 weeks now
[T-Mobile, Samsung Galaxy SIII] sarni84:
Dude all I can say is wipe and reflash....I was having problems with newest nightly and I said eff it I wiped and started over and now everything is golden. Hold back to kill works also
[T-Mobile, Samsung Galaxy SIII] :
Which kernel are you using still kt?
[T-Mobile, Samsung Galaxy SIII] elesbb:
Ive done that. Fresh install and everything. I do that all the time i have any issue and i start from scratch installing and modding things one at a time. And its weird, cause if i leave the app "untouched" for like ten seconds then it doesnt kill it, but if i simply touch the screen anywhere, then it kills it. Ive narrowed it down to something NOT on my end. I litterally only had tapatalk and root explorer installed. It was working perfectly as normal. Went to do a reboot just to re-settle everything, and boom stopped working unless i tapped the screen. Ive posted a logcat about it before. But nobody reads or cares about that so i guess i'll just stop posting issues and wait for a release candidate and create a ticket in the issues tracker for it.

I just love how a few people couldnt stream their music using bluetooth and that got fixed in a couple of nightlies. But sadly i drive a 1986 granny mobile and dont have such luxury so it would be nice to be able to use a feature flawlessly like hold back to kill that im capable of using.
[T-Mobile, Samsung Galaxy SIII] RonDigital828:
Anyone find a mic fix for Google now. Its still only working with the top mic...goodnight all
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
Even when it says application killed, you can still go back to it with long press Home. Seems like a fairly pointless feature to me. Am I missing something? Is this working as intended?

elesbb, earlier, you had asked why was the previously working code changed. As a rank amateur programmer myself, I suspect it was poorly written to begin with, and was optimized; or needed to be modified in order for something else to work. It is very rare for bugs not to surface when doing this.

I see a lot of people suggesting clean flashes. Why? The flashable zip file simply overwrites files that are in your /system directory with the ones in the zip. There is no magic, it just overwrites files that were already there. Wipe cache, wipe Dalvik, flash nightly, install gapps, fix permissions; I've never once had an issue. Not one time. Clean flashing + Titanium Backup restore seems like nothing more than a huge waste of time to me. You are restoring "dirty" files. Does not make sense to me. Surely there must be a fault in my logic.
[T-Mobile, Samsung Galaxy SIII] bigxie:
There's a misconception about the multitasking menu. It is actually not a task manager. It is a nice, fancy, graphical way of keeping track of recently opened apps.

Their presence in this menu has no correlation to whether they are in actuality, running. If you swipe away an app, it does not kill it. It just removes it from the list.

In the opposite direction, when you force kill an app (say, using long press back), it does not remove the app from this list.

The list is just a list. It is not a real time indicator of running apps.

That being said, there has been no need to micromanage your running apps and free up memory in Android for several iterations now. The system knows how to handle the memory just fine. This is especially true with our device, which has 2GB of RAM. Just go about your business and let the system handle it.

Of course, there are exceptions to this: i.e. known misbehaving app, etc, but it's a good general guideline.

EDIT: actually, it is a bit more complicated than that. It seems to really depend on how the specific app uses the info from the system, and how it decides to react to the command. More info here:

http://android.stackexchange.com/qu...-you-swipe-an-app-out-of-the-recent-apps-list
[T-Mobile, Samsung Galaxy SIII] street954:
I was under the impression that the CM team doesn't monitor this forum.

If it bothered me as much as it apparently bothers you, why dont you try posting on the CM forums? That has to be a better avenue for correction than to keep posting here, where in all honesty, no ones bug reports are being heard
[T-Mobile, Samsung Galaxy SIII] blesstheattack:
Just a heads up cm10 20121011 m2 is out, not sure of the changes from last nightly.
[T-Mobile, Samsung Galaxy SIII] IRIE4IPIER:
Quit whining like a little little girl, this is xda not group therapy. The hold back to kill feature works perfect for me, the way you know it works is you open the recent apps and you see a black screenshot, I still swipe it away from that list too. But for you to be in here challenging the work of the CM team is just flat out disrespectful and you need to take a break. Maybe they should take a break and let you and the other wannabe devs in here finish CM10.

---------- Post added at 05:03 AM ---------- Previous post was at 04:51 AM ----------

You're wrong buddy boy, go into the browser and load a page, press home and open recent apps, swipe away the browser, it will reload and sometimes even close all your tabs you had open. Do this with a game or any app, by you swiping an app away from the recent apps section, you are telling Android you don't need the app ioen anymore and Android properly removes it from memory.
[T-Mobile, Samsung Galaxy SIII] elesbb:
Thank you. This is the best explanation i have ever come across. This is so very true.

But about letting the system handle it, i dont like having things like the facebook app or other social networking apps constantly run or the market or youtube etc. So its nice to just hold back to kill.

This is mostly true, but we dont have a sub-forum for the d2Tmo on cm forums, so i dont know where to post any bugs/issues.

Dude... i dont even know where to start. You are wrong on all levels. And no where on this forum am i being disrespectful. As i said before, the reason for my tone is the fact that a few people complained about the bluetooth issue and that got fixed within a few nightly builds. That also being a reason i figured maybe i post about it again as it felt like someone was reading them.
[T-Mobile, Samsung Galaxy SIII] joshnichols189:
My hold back to kill doesn't work consistently either. And yes, I'm sure you know more than an actual dev (Bigxie).
[T-Mobile, Samsung Galaxy SIII] karmendc:
n00b question, but im asking it anyway... how do i change my "Local Profile" on my phone so when i sync my contacts on google, it syncs up correctly and i don't have to input it every single time i wipe my phone?
[T-Mobile, Samsung Galaxy SIII] stonew5082:
Huh? You mean sign into Google?
[T-Mobile, Samsung Galaxy SIII] SlakWReX:
Anyone trained and/or know the difference with the 10/11 experimental build
[T-Mobile, Samsung Galaxy SIII] karmendc:
not quite.. basically every time i wipe and re-flash my phone, my "local profile" on the gs3 gets wiped too and im tired of having to choose my user pic and put in my contact info over and over. any ideas on how to remedy this?
[T-Mobile, Samsung Galaxy SIII] scorpio_bpl86:
M2 ???

did anyone try the experimental M2

where can i find the gapps for that ?
[T-Mobile, Samsung Galaxy SIII] cbutters:
I'm also looking to upgrade my nightly and would like to know if I should flash the M2 or the latest nightly...