yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] goldsmitht:
Cool! NOW if i can just get everyone to GET OFF THE DOWNLOAD LINK!!! i might be able to download this faster than 41kbs/sec. Which puts it at about 92 hours, give or take a few, to get downloaded.

LOL! :p
[Verizon Samsung Galaxy S III] mastamoon:
hehe, sorry cant help ya there.. this last push showed me that 1085 users or something got the notification.. so there is a bunch of ya'll downloading at the same exact time.
[Verizon Samsung Galaxy S III] goldsmitht:
Found an issue; can't get min CPU speed off 918. Keep setting to 318, and doesn't survive leaving performance section. Back out, and it resets to 918. Tried ondemand and interactive
[Verizon Samsung Galaxy S III] mastamoon:
Yeah I think the kernel cherrypick I use does that. Phone should still use 384 as min and 1512 as max.

Use cpuspy to confirm.
[Verizon Samsung Galaxy S III] Chris123NT:
I'm starting to wonder if this is the cause of the slightly reduced battery life people are talking about.
[Verizon Samsung Galaxy S III] mastamoon:
I noticed battery getting worse for awhile, before nard put up it up.

I think the battery has to do with the data issues. Everytime you have a data drop your gonna burn battery waiting for the reconnect.

Honestly it's not all that different for me. I used to get about 4 hours screen on time before I would have to charge. Now I'm getting about 3.5 or so.
[Verizon Samsung Galaxy S III] goldsmitht:
Yeh, CPU spy shows range as 918-1518; the 318 showing is me setting it and checking the io settings.
[Verizon Samsung Galaxy S III] sivarticus85:
I noticed this as well. However, if you watch the frequency in the performance settings, you'll see it still dips below 918. I watched it for a minute or so the other day, and it was consistently hitting 384 without me having to change the min.

Edit: Attached a screenie.
[Verizon Samsung Galaxy S III] goldsmitht:
Went back to 9/20, and issue is there as well; can't set below 918 and have it stick
[Verizon Samsung Galaxy S III] sivarticus85:
3.5? Shoot I'm lucky if I get 1.5 in a day. I'm barely on it as well. After 12 hours on battery in at 35%.

Edit: Right now I'm at 63% with 33 minutes screen time, 21 minutes of music, and no data loss today. Is this consistent with anyone else?
[Verizon Samsung Galaxy S III] mastamoon:
I'll leave it out of my build tomorrow to see if battery life improves. But this commit was done by somebody that knows their way around a kernel, so I think it's by design and as long as you see 384 as your min in cpu spy, I would t worry about it much.
[Verizon Samsung Galaxy S III] mastamoon:
I guess it's what you do with those hours of screen on time. An hour of gaming or video play ain't gonna equal an hour of facebook/twitter/g+.
[Verizon Samsung Galaxy S III] sivarticus85:
Mainly just FB and here in the forms. I game on my Nexus 7.
[Verizon Samsung Galaxy S III] jalewis:
I'm at 74% after 11.5hrs, but I only have 16 minutes of screen on time...obviously didn't touch my phone much today...
[Verizon Samsung Galaxy S III] herooftimeloz:
I lost my IMEI, and nvrestore hasn't helped fix it. This started a few days ago when I tried flashing a nightly update (I tried both mastamoon's and official). After each attempt, I restored my previous working backup and waited for the next update. Are there any recent changes that may have caused this?
[Verizon Samsung Galaxy S III] Chris123NT:
If restoring to a previous ROM backup is fixing it then it isn't your IMEI.

As far as changes go, there hasn't been anything that would cause what you're reporting, can you post a radio log?
[Verizon Samsung Galaxy S III] sivarticus85:
Check in your mobile settings if you're on NV instead of RUIM/SIM. This happened to me this weekend when I popped my sim in another phone to see if it still worked. Once I reset it and rebooted, everything came back.
[Verizon Samsung Galaxy S III] goatman101:
I also lost my imei and all phone info after flashing yesterday's official. Thank god I had a backup of a previous build. It restored and I am back to normal.
[Verizon Samsung Galaxy S III] herooftimeloz:
Sorry, I had a major brain fart and forgot to add that I was flashing BMS kernel with it. And from looking at that thread, it seems like the kernel is the culprit.
[Verizon Samsung Galaxy S III] aeroevan:
CM 10.2 + -O3/-strict-aliasing

Hi all,

If anyone is interested in a fresh build with the linaro.org changes for O3/strict aliasing: http://goo.im/devs/aeroevan/cm10.2/cm-10.2-20130923-UNOFFICIAL-d2vzw.zip

Kernel: https://github.com/aeroevan/android_kernel_samsung_d2/tree/cm-10.2-aeroevan (only a few changes over stock)

It has mastamoon's Operators change: http://review.cyanogenmod.org/#/c/50699/ but I haven't pushed the crap-ton of linaro patches (they'd need cleaning up and squashing).
[Verizon Samsung Galaxy S III] Chris123NT:
And had no data when I got to work today. But then I also had the no data connection on network extender before I left the house today too, wondering if it's the apn-conf that's doing it, I'll have to fool around later today with it.
[Verizon Samsung Galaxy S III] mastamoon:
nooooooooooooooxelevenbillionity
[Verizon Samsung Galaxy S III] mastamoon:
Just an FYI.. This a small explanation from the author of this mod.
[Verizon Samsung Galaxy S III] PerCompLLC:
According to the BMS thread, you need to flash the kernel immediately after the ROM in the same recovery session. I had the same problem with losing my data, but when I flashed the kernel in the same recovery session it actually worked. That said, the BMS kernel doesn't seem to have been updated since 9/6, so I'm on Lean Kernel instead. YMMV
[Verizon Samsung Galaxy S III] WhammyDroid:
Does anyone know why the the CMXLog is not working?

I need to get a hold of the developer who committed some of the headphone/LPA commits recently. He partially addressed the DSPManager issue I reported.

Thanks!
[Verizon Samsung Galaxy S III] cornelious1212:
Small issue but still annoying. Anyone else have the lockscreen weather not keep up with the moon/sun icon? No matter how many times I tap it it wont change. Then it will randomly go back to the correct icon, then just as randomly go back. Thus is from right now.
[Verizon Samsung Galaxy S III] PerCompLLC:
Delete.
[Verizon Samsung Galaxy S III] PwnCakes193:
You're looking for Arne Coucheron.

You can find him at review.cyanogenmod.org
[Verizon Samsung Galaxy S III] mastamoon:
Ive seen this issue come and go since cLock was added.
[Verizon Samsung Galaxy S III] ugachris:
Try this log instead:

http://changelog.bbqdroid.org/#/d2vzw/next
[Verizon Samsung Galaxy S III] mastamoon:
Everybody should just run [MENTION=2385005]invisiblek[/MENTION]'s changelog app on their phones. :)

https://play.google.com/store/apps/details?id=com.invisiblek.cm.nightlies
[Verizon Samsung Galaxy S III] cornelious1212:
I've seen it intermittently too, but it seems to have increased recently. It seriously bothers my OCD :)
[Verizon Samsung Galaxy S III] goldsmitht:
i started noticing it, along with some extra battery drain, so i just disabled weather on the lockscreen. makes it much more minimalistic, and that's the way, uh huh uh huh, i like it...

sorrry, day is dragging cold medicine is not playing good with the coffee

:silly:
[Verizon Samsung Galaxy S III] Restola:
try http://changelog.bbqdroid.org/#/d2vzw/next
[Verizon Samsung Galaxy S III] mastamoon:
9/24 build in the OP

-- added a few new cherry-picks for testing, general stuff.

-- repo sync @ 3PM EST
[Verizon Samsung Galaxy S III] fromthesticks:
No issues this far. Except my data was turned off, just turned back on in settings.
[Verizon Samsung Galaxy S III] Stealth111:
You'll be happy to know that your "picks" do NOT seem to be the cause of the extender issues. I am getting no IP even on the latest Official nightly... I flashed my phone back forth and sideways about 50 times today testing some stuff out. Saw some REALLY weird stuff while doing so, but ultimately everything settled down with the exception of the data issues.. Check out the PRL, and ICCID, heh! :)
[Verizon Samsung Galaxy S III] zachf714:
I remember toastcfm mentioning something on the gerrit about how on the toro you loose ICCID at times
[Verizon Samsung Galaxy S III] Chris123NT:
All of this seems to be caused by the 4.3_r3.1 merges in telephony, settings and base. Revert to before that and extender data works and you don't get the whacked out PRL and ICCID info.

Bottom line, it's a google bug, which means CM might never actually fix it :P
[Verizon Samsung Galaxy S III] mds96:
Hoping you or another user can tell me what the last nightly was before these got merged. I'll dig back through the changelogs in the meantime. I swear the builds on here have the best battery life out of any rom I flash! Great work on here! I don't mind sacrificing loads of customizations for stability and battery life! Thanks!
[Verizon Samsung Galaxy S III] olm3ca:
Thanks for such a great ROM, masta. One small but replicable bug: when uploading video to instagram, the phone reboots every time right after it uploads. I'm guessing this is a CM 10.2 issue in general, though.
[Verizon Samsung Galaxy S III] senorbuck:
You do the video playback stuff mentioned in OP? All my video stuff, including Instagram, is running beautifully. I did encounter the playback/reboot stuff initially but after OP stuff, all is good!
[Verizon Samsung Galaxy S III] TwistingSoul:
So, I downloaded yesterday's build with the stock kernel, and decided to perform a nandroid backup in Rom Manager by selecting "Backup Existing Rom" before telling it to wipe data/clear cache. I figured it was about time that I clean flashed my phone, as it had been a while.

The phone booted back up like normal, and I go through the setup process, and then comes the arduous task of reinstalling my apps.

Titanium Backup has always gotten stuck on one or two apps, so I decided to reinstall the apps via CWM by following these steps:

1. Boot into Recovery

2. Make a Nandroid backup

3. Wipe data/factory reset

4. Wipe cache partition

5. Wipe Dalvik Cache

6. Flash ROM

7. DO NOT REBOOT – STAY IN RECOVERY

8. Select backup and restore

9. Select advanced restore

10. Select the Nandroid backup you made above

11. Select Restore data

12. Select Yes – Restore data

13. WAIT!

14. REBOOT

Everything restored from yesterday's nandroid as expected, complete with all apps and text messages that had previously been saved.

The only thing that's NOT working is when I go to the Play store website and select an app to install from there to my phone, nothing happens. I don't get an error message on the page, and no response from my phone. I was able to do this before being an idiot and performing a nandroid restore. I have also cleared cache from Google Play Services as well as the Play Store apps in Settings>Apps>All, but with no success.

My phone is also not visible in Android Device Manager or the CyanogenMod Account websites.

My question is how can I restore the web install functionality and get my phone recognized on Android Device Manager/CyanogenMod Account again? Avoiding a full wipe would be preferable, but if there are only a few things I'd need to clear out/attempt to remove/reinstall from the Play store, I'd rather go that route.

Thanks, as always, for making such an awesome Rom, masta. I've been following this thread since it was first linked from your unofficial 10.1 rom.:good:
[Verizon Samsung Galaxy S III] zcmack:
am i missing something in the OP? all i see is
[Verizon Samsung Galaxy S III] senorbuck:
Hmm, thought there was more in the OP. Whoops! For example, when I dirty flashed the latest yesterday, I went to use Instagram and when trying to apply an effect to the video, the phone hung and rebooted. When it came up, I loaded Instagram again and everything worked fine (still does). Can you play videos in your Gallery without a reboot?

There's a cherry pick Masta has in his build that allows Instagram to run properly after you get it to crash/reboot.
[Verizon Samsung Galaxy S III] MWFD:
Can anyone tell me if there is a better build out since masta's 9/9 build for 4G stability including working 4G to 3G handoff and 3G to 4G handoff? I'm reading through lots of different issues on this thread from the past few week's (SIM issues, connectivity issues, PRL, erasing SIM info, etc.) and want to know if I should just stay on 9/9 build for now or if there is a better build to download where I won't risk having my SIM ID info erased or other pretty big bugs? I currently have 4G turned off since the handoffs are inconsistent, but want to be able to use 4G again without having to worry about losing data all the time.

Thanks in advance!
[Verizon Samsung Galaxy S III] DiGi91:
Might try it out but will probably return to M.O.A.R for now. It's one smooth TW ROM. Data handoff inconsistencies are another thing on AOSP that drive me insane, doesn't happen all the time but when it does..
[Verizon Samsung Galaxy S III] tv31284:
Hopefully this helps. The battery is only draining at around 3% an hour but I've barely been using it. There is a wake lock issue but I've no idea where it's coming from.
[Verizon Samsung Galaxy S III] mastamoon:
My phone is acting a fool. Meh.
[Verizon Samsung Galaxy S III] Chris123NT:
Google services is to blame for your problem. Make sure location reporting is OFF in maps and check your other location stuff, those wakelocks alone are responsible for 1.5 hours of awake time, take those away and your phone has a respectable sleep ratio and should be fine with battery.
[Verizon Samsung Galaxy S III] PerCompLLC:
I concur... Just snapped a few pics. Very impressive!
[Verizon Samsung Galaxy S III] Chris123NT:
Wow, that is impressive. Definitely wasn't expecting that, desterly kinda just forward ported the CM 10.1 hacks to fix camera, this is a pleasant surprise.
[Verizon Samsung Galaxy S III] damnyouwaffles:
What could possibly be causing the battery charging so slow? My phone would be almost done charging in about an hour but its only at 33 percent right now.
[Verizon Samsung Galaxy S III] mastamoon:
I'm charging my phone right now. Went from 30% to 78% in about an hour. And it's an old blackberry charger.
[Verizon Samsung Galaxy S III] damnyouwaffles:
How is battery holding up for you?
[Verizon Samsung Galaxy S III] mastamoon:
So so.. Its Ok idle, but doing anything seems to really kill it quick.
[Verizon Samsung Galaxy S III] damnyouwaffles:
Just saw this in battery stats. 2 hours in full wake lock?
[Verizon Samsung Galaxy S III] DiGi91:
Back on M.O.A.R and just went for a drive, used BT in the car with the flexsmart. Phone was back to normal temp and battery is great again. 4.3 ran great but couldn't deal with the battery drain and the fact it was charging so slow (not sure why) Either way Masta's builds are on point and I will be back on them eventually when everything is ironed out and what not.
[Verizon Samsung Galaxy S III] tv31284:
Battery is draining a lot slower but I could've sworn I had the same settings before and drain wasn't as bad.
[Verizon Samsung Galaxy S III] mikejr83:
I think the battery drain is tied to WiFi. I turned off the search functionality as preciously mentioned and was still loosing battery at an amazing rate.

For the heck of it I just plain turned off WiFi. I started that at around 37% and have only dropped 10% in the past 3 hours where before I lost 30% on my 20 min drive from work.
[Verizon Samsung Galaxy S III] damnyouwaffles:
I just charged my phone fully and then rebooted and it seems to have fixed android system. (Knock on wood.) Maybe calibrating the battery helps?
[Verizon Samsung Galaxy S III] jmichaels1982:
Love the rom

I left AOSP a long time ago due to horrendous signal and poor GPS.

Well my signal is TW equivalent and I was locked instantly inside my house, this has never happened on any TW rom.

Oh I also enabled the navbar and adjusted its buttons and I am rocking.

I haven't had any lock screen lag , because I never use it ! and phone instantly turns on !

Has anyone been able to install xposed ?

I absolutely miss AOSP and what a treat to go back to !

Thank you !
[Verizon Samsung Galaxy S III] Chris123NT:
You might be on to something there. I feel like my battery life is great except when I go driving, phone gets hot and the whole bit. I thought it was bluetooth audio, but I couldn't reproduce it on my BT speakers in my house, gonna look into this wifi thing.
[Verizon Samsung Galaxy S III] Div033:
I agree, 7/19 seems the be the best cm 10.1 build out there. Been eyeing this thread like a hawk but I don't want to lose the stability I already have. Hopefully these things get sorted out soon... I was excited to hear 4.3 would have better battery life and now feel down as everyone talks about massive drain :(
[Verizon Samsung Galaxy S III] Chris123NT:
The drain is because of various issues that still need working on. Remember a week ago our kernel wasn't even booting on 10.2.
[Verizon Samsung Galaxy S III] Div033:
Yeah I know from a practical standpoint things will definitely get better, but sometimes feels like there's a devil whispering in my ear "It will never get fixed! Gweeheheheheheeee..."

Just need to tell him to stfu.
[Verizon Samsung Galaxy S III] mastamoon:
Any of my builds from the past 2 weeks or so should have better handoffs. The fix I was using and that I put up on gerrit just got merged so official should have better handoffs on tonights nightly.
[Verizon Samsung Galaxy S III] mds96:
I agree that the ones from the past two weeks had better handoffs. These are also the ones that drop signal all together though also, correct? Please correct me if I'm wrong because I want to go back to you nightly's but it was happening to me a lot, that is why I switched until someone found a fix.
[Verizon Samsung Galaxy S III] mastamoon:
No, the hand-offs and data-drops are kind of one in the same issue. Generally these builds from the last few weeks wont leave you with no data.. Yes it still happens, some people have it worse than others, but in general, things are better than builds from 3 weeks ago or official.

Remember, forums are where people come to complain generally, not say "everything works great". So things seem pretty bad when reading through the thread, but its a small percentage of the actual user base. I know people who do not complain about it have the issue also, but for me things are OK and I believe most users fall into this category.
[Verizon Samsung Galaxy S III] Restola:
nice job getting that merged!
[Verizon Samsung Galaxy S III] mastamoon:
Thanks. :)

It has already been superseded though.. but my changes are also included in there. :victory:

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

Even if that doesnt get merged right away, my commit from today will be so should still be ok.
[Verizon Samsung Galaxy S III] airmaxx23:
I'm getting quite a bit of stuttering when scrolling on the 9/24 build. What do people suggest for kernels for this? I was using KT747 but is hasn't been updated so I've just been using the stock kernel.
[Verizon Samsung Galaxy S III] olm3ca:
Sorry for not responding earlier, work got crazy. I hadn't tried just playing videos through Gallery, but after 4-5 tries it still hangs and reboots every time. I guess this is why Instagram is crashing. One note: if I select Video Player or MoboPlayer, both apps hang and reboot.
[Verizon Samsung Galaxy S III] mastamoon:
9/25 build in the OP

-- added a bunch of audio cherry-picks, see list.

-- edited the list to show an 'added' date line, starting today obviously, not sure when the others were added so no heading for them.

-- repo sync @ 2PM EST
[Verizon Samsung Galaxy S III] mastamoon:
welp, guess ill be doing another build.. this one has the no data bug.. bbiab

dont flash yet.
[Verizon Samsung Galaxy S III] goldsmitht:
Anyone else getting "server returned error sending download file" or is it just my crappy work WiFi?
[Verizon Samsung Galaxy S III] mastamoon:
I pulled the download.. has data bug due to a test commit. Rebuilding now.. should be done in a few minutes.
[Verizon Samsung Galaxy S III] goldsmitht:
Went to the OP, and noticed the "derp" ... just wasn't smart enough to not click on download...
[Verizon Samsung Galaxy S III] airmaxx23:
I have data on the 9/25 build, I've rebooted a few times and still have it.
[Verizon Samsung Galaxy S III] khymbote:
Now you say and I flash as soon as it's posted. I still have data.
[Verizon Samsung Galaxy S III] mastamoon:
I had data but lost it.. got it back by toggling data... rebooted.. right to no data again.
[Verizon Samsung Galaxy S III] SymbioticGenius:
Since it doesn't get said enough. Thank you. I for one can say I've been daily driving Masta's builds pretty much since they began. Ups and downs of course but nothing to make me go elsewhere long term. Dirty flashed damn near all of it too. Most recently I had two semi serious issues with GPS and Bluetooth. GPS was hardware and Bluetooth required clean flash. Never ran better, no handoff issues in bad signal areas. Running 9-20 used both BMS and Ktoonsez both of which are great as long as I don't oc past 1900. Once again Masta, thank you.
[Verizon Samsung Galaxy S III] airmaxx23:
Mine is still ok, browsed the web, updated a few apps and rebooted again and it's still running fine.
[Verizon Samsung Galaxy S III] khymbote:
Hmm. I will install when you push again.
[Verizon Samsung Galaxy S III] TwistingSoul:
I was actually able to miraculously fix this issue after installing Market Helper, found in this thread:

http://xdaforums.com/showthread.php?t=2146216

Strange the things one finds when trolling the interwho for hours on end, only to wind up back in these here fine XDA Forms. :cool:
[Verizon Samsung Galaxy S III] mastamoon:
9/25 build is back up again...

-- removed that commit that seemed to cause a data drop issue... for me.

Sorry bout that!
[Verizon Samsung Galaxy S III] mastamoon:
not sure how rom dashboard is handling this.. so im going to push another update via the service.. ugh.
[Verizon Samsung Galaxy S III] jalewis:
Has the LPA issue been taken care of? I know you suggested a fix, but I've been slammed at work and haven't had a chance to mess with anything, so I'm still running 9/09...
[Verizon Samsung Galaxy S III] mikejr83:
I got two notifications after the first pulled build. Seems to be working fine from my end. :p
[Verizon Samsung Galaxy S III] khymbote:
I had to clear the data to get the 2nd build to download.
[Verizon Samsung Galaxy S III] mcdevil58:
I've been having random reboots on the last two builds, is anyone else experiencing this?
[Verizon Samsung Galaxy S III] senorbuck:
See, just flashed today's build. Flashed, booted, tried to make a video in Instagram and it fails to when applying effects. Eventually, the phone reboots while in Instagram. After it rebooted, went into Gallery and watched a video. That plays fine. Started Instagram from scratch, created a video, and everything works as it should and operates 100% until the next flash.
[Verizon Samsung Galaxy S III] mcdevil58:
I also noticed starting with yesterdays build that all my files were moved to the emulated/0/0 folder instead of just sdcard0. Has anyone else noticed this?
[Verizon Samsung Galaxy S III] MG386:
I've been on all the dailys, and have not had that issue. Is your recovery up to date?
[Verizon Samsung Galaxy S III] mds96:
Very good point, and well said! Thank you for clearing it up for me! Looks like I'll be coming back very soon! Keep up the great work!
[Verizon Samsung Galaxy S III] Chris123NT:
This may fix the handoff issues:

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

It got Shareef'd though lol, I just built with it so I'll see if it fixes me up for the drive to work tomorrow. Extender data is still FUBAR but that seems to be another issue completely.
[Verizon Samsung Galaxy S III] Stealth111:
HAH! Better than getting punched,right? :)

ROFL

Sent using Tapatalk
[Verizon Samsung Galaxy S III] Chris123NT:
Look at IRC lol :p
[Verizon Samsung Galaxy S III] zachf714:
Go figure lol.. Maybe he will learn to let the Chris work if it fixes the handoffs xD