yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] zachf714:
The problems were only for CDMA d2s but it is fixed now by the qcril branches for the ril
[Verizon Samsung Galaxy S III] senorbuck:
Might have mentioned it and if so my apologies but you try a clean flash? I know it's a PIA... Unless that's what you're saying you did haha :P
[Verizon Samsung Galaxy S III] Reborn627:
Yip, twice. Last time I just went back to 10/15.

Ray
[Verizon Samsung Galaxy S III] senorbuck:
Bummer :(
[Verizon Samsung Galaxy S III] mikejr83:
I think I saw you say no other mods. You're not flashing another kernel, right? Just checking because I'm experiencing the same issue with my kernel and the latest builds.

I think BMS kernel fixed the issue. Try that?

Mike
[Verizon Samsung Galaxy S III] Div033:
Just updated from 10/10 to the latest and had no issues by doing this exactly:

1. Wipe cache

2. Wipe system

3. Wipe dalvik

4. Flash ROM

5. Flash DB deleter

6. Flash GPE boot anim

7. Flash 8/20 gapps

8. Profit

Using latest CWM
[Verizon Samsung Galaxy S III] Reborn627:
I've tried both way. Went stock first wiped and tried GideonX's BMS kernel. Neither worked. In fact, I just tried flashing GideonX's 10/16 kernel with the 10/15 build and got the same error. Maybe there is something that my device doesn't like about the latest kernel. I'm clueless.

Ray
[Verizon Samsung Galaxy S III] Interflop:
The only issue I'm currently having with the 10-17 build is a nasty RILJ wakelock. I can't seem to get it under control.
[Verizon Samsung Galaxy S III] Reborn627:
So, this is strange. I made a final attempt at flashing 10/17 this morning and it worked. The only thing that I did differently was flashing the db deleter before flashing gapps thanks the idea [MENTION=2855331]Div033[/MENTION]. I'm considering a flash of GideonX's BMS kernel following the same method but I'd rather not go through the full wipe again. It's just a pain to get all of the apps reloaded. Anyway, thanks for the help everyone.

Peace,

Ray

Edit: Decided to give it a shot. Followed same steps, Rom, deleter, gapps & kernel and had the same "unfortunately com.android.phone has stopped" error. Just FYI
[Verizon Samsung Galaxy S III] mikejr83:
Agggggggg! You had me so hopeful!
[Verizon Samsung Galaxy S III] Restola:
Is wiping the SMS/MMS needed for each update? I've switched back to mastamoons since I'm now having the grey data issue on the official. I wiped sms/mms yesterday when I switched to 10/15. when i updated to 10/17 this morning i had uber phone fcs, so I had to run the qril deleter again.
[Verizon Samsung Galaxy S III] Reborn627:
I hope that it doesn't become a regular thing. It is a little bit of a hassle, I usually have texts that have info I need to look back on as well as phone numbers in my call log. Restoring them is just an extra step that I'd prefer not to do. However, if the qcril commits fix the hand-off issues then I guess it's a worthwhile hassle. Sure would be nice to be able to flash another kernel though. I get quite a bit more battery out of the GideonX BMS kernel over the stock. Anyway, at least I'm current and error free right now.

Peace,

Ray
[Verizon Samsung Galaxy S III] mastamoon:
It really depends on what your coming from. My 10/15 to 10/17 would require a wipe, since in that time invisiblek fixed the upgrade process but it cant upgrade a previously upgraded (by deleting the DB's to get on 10/15) file. So you have to delete them again. From here on out, as long as I use the source with his fix it shouldnt require any more wipes. Switching back to stock or going back to 10/15 might require yet another wipe.. and then going to say todays build from there would require a wipe...

:eek:

I know its a bit of work but it will be better in the long run once this stuff gets merged. CM isnt ready to just flip the switch in the main repo, so we are testing the crap out of it. :)
[Verizon Samsung Galaxy S III] RED ZMAN:
There's been several posts over the last week in the JIRA about the Bluetooth freezing bug, for those that aren't watching it. I'm hoping this means some movement is made on it, this is the one bug that really ticks me off the most.

Keep up the good work Mastamoon, I'm probably going to upgrade to 17 tonight. But when that Note 3 Dev Edition comes out...
[Verizon Samsung Galaxy S III] Div033:
More like the BLOAT 3 am I right guys?!?!

Sorry. Enjoy your new phone!

Anyway I'm glad my anecdotal evidence managed to help. I wouldn't think that flash order would matter really but maybe it does...?
[Verizon Samsung Galaxy S III] RED ZMAN:
Hahah, so I've heard. I'm not giving up my unlimited data, I use more and more every month, and if I'm buying outright, may as well get the Dev Ed.

Rise up!
[Verizon Samsung Galaxy S III] sivarticus85:
So since when does cLock keep GPS on all the time? It's never kept it awake like that before...
[Verizon Samsung Galaxy S III] goldsmitht:
did you flash a second party kernel? A number of them will cause your phone to go into massive phone FC's.

:cyclops:
[Verizon Samsung Galaxy S III] mastamoon:
Im not seeing that at all.. not even in my list of top apps on the battery screen.
[Verizon Samsung Galaxy S III] mastamoon:
10/18 build in the OP

-- added a revert that might help Network Extender folks data

-- repo sync at 2PM EST

Weekend, woot woot!
[Verizon Samsung Galaxy S III] sivarticus85:
Weird... Oh well. It doesn't seem to be hurting battery much, but seeing GPS on all the time in my battery status is a little annoying. Thanks anyway.
[Verizon Samsung Galaxy S III] TwistingSoul:
Today's build works great, even though I had to use the deleter thing to fix the phone crashes.

Not a big deal, as I used Helium to back up my message storage beforehand.

My Adb also works after yesterday's issues. Didn't have to go into download mode or anything. Maybe due to computer shut down?

Good is good, as far as I'm concerned. Lol
[Verizon Samsung Galaxy S III] xyrcncp:
Nice, I have a Network Extender. I'm actually flashing your ROM now. I was running the official CM10.1.3 stable

The phone is downloading apps from the store now, but so far it still says "Out of Neighborhood" for the Network, "LTE" for the Network Type, "In Service" for Service state and Roaming, but it's connected to WiFi. I'm guessing that after 4.1 the phone behavior with a Network Extender is not the same?
[Verizon Samsung Galaxy S III] jalewis:
Rebooting a PC works wonders sometimes...
[Verizon Samsung Galaxy S III] khymbote:
Had an issue tonight where it wasn't letting me on home wireless. Reboot fixed it. It came up as null.
[Verizon Samsung Galaxy S III] RED ZMAN:
Been running this for hours now, and really REALLy smooth. No issues at all yet. Haven't gotten to test Bluetooth yet, but I'm expecting it is still the same. Middle Manager of Justice really tore the battery down, but I expect that from any game. Great work my man.

BTW, I'm in on the Themer beta, and it runs suuuuuper smooth with this rom.
[Verizon Samsung Galaxy S III] ef-civic:
So I'm on build 10/01. To update to latest I need to wipe dalvik, wipe system, and wipe cache to have a successful install.
[Verizon Samsung Galaxy S III] mastamoon:
That should do it. Have the db deleter zip from the OP handy just in case you get some force closes on boot. If you do use that zip be warned your texts will be deleted so back them up now if that is important to you.
[Verizon Samsung Galaxy S III] WhammyDroid:
Masta, another revert to add to the list?

http://review.cyanogenmod.org/#/c/50929/
[Verizon Samsung Galaxy S III] mastamoon:
That is for the cmInc builds. We run userdebug builds so should be fine.
[Verizon Samsung Galaxy S III] funnyperson1:
So far the 10/17 build is running nicely for me. Handoffs seem to be reasonable.

Only issue is that my network icons seem to go gray even when I have connectivity.
[Verizon Samsung Galaxy S III] HandsomeOne:
Still having data issues 1x, 3g most 4.3 roms. I have access to 3 SIII ,all do the same, sometimes data will come back sometimes it won't same on all three. CWM 6.0.3.8 all fresh installs. If i use cm-10.2-20131009-UNOFFICIAL-d2vzw-picks Version, data works on all Three. Just like i was using Cleanrom Seven. Don't know if anyone else is have issues.? Thank you for all your had work, love this rom.
[Verizon Samsung Galaxy S III] bmeek:
I've been having issues where data will be working fine, then stop for an extended period, and then restart. When data fails, i see several grey bars on the signal indicator (which goes blue with a data mode label if/when data flow resumes). I can usually get data flowing again by cycling airplane mode...

I'm running mastamoon's cm-10.2-20131018-UNOFFICIAL-d2vzw-reverts build, and I also flashed the qcril_database_deleter again for good measure.

I'll try to locate and flash the ...picks version and report if that seems more consistent data-wise.
[Verizon Samsung Galaxy S III] zachf714:
That would be because only CM has these Qualcomm Ril changes in effect / merged into a branch where as no other 4.3 ROMs do most likely because they are to lazy, I am working on bringing it up on aokp but have no clue how long it will take me
[Verizon Samsung Galaxy S III] HandsomeOne:
Thank you for that info and all your work !!!
[Verizon Samsung Galaxy S III] WhammyDroid:
Masta, on reboots I am still having to toggle the data option in order to get it to work. I am on the latest nightly from Friday. None of the ROMs have fixes the initial data connection issue.
[Verizon Samsung Galaxy S III] Stealth111:
If you are having an issue, please try his build from the 15th. Make SURE you wipe the db files with his deleter utility zip, right after flashing rom, while still in recovery. Also wipe cache and dalvik cache for good measure. When it boots, data might take a minute the first time, then it should be fine going forward. If you are running any type of non-stock config (like a different kernel), please make sure you specify that info in your posts.

Good Luck and Happy Flashing!!

Sent using Tapatalk
[Verizon Samsung Galaxy S III] goldsmitht:
Weird battery stats; haven't been off the charger for 12 hours, more like about 6.

But did switch from TW HyperDrive to 10/18 masta's about 4 hours ago. But wiped / factory reset between switching ROMs

---------- Post added at 03:50 PM ---------- Previous post was at 03:48 PM ----------
[Verizon Samsung Galaxy S III] :
So what happened to the nav bar?

Edit: On the 10/18 build. I'm also seeing borked battery stats. Screen time is not being recorded correctly.

Also, kernel default for min speed was 1100? Am I the only one?
[Verizon Samsung Galaxy S III] SymbioticGenius:
I haven't been able to successfully install the 18th build. I keep getting a status 7 error. Using cwm touch which I've been using for a while
[Verizon Samsung Galaxy S III] zachf714:
[MENTION=2963287]mastamoon[/MENTION] why did you re-add the "Remove Operator Check" pick?
[Verizon Samsung Galaxy S III] buschbarber:
I am running 4.3 and just installed the 10/20 nightly. The phone locks up at the alien screen. I had to boot into Recovery and flash the 10/14 nightly.
[Verizon Samsung Galaxy S III] bmeek:
As I reported yesterday, I was experiencing flaky data issues with the 10/18 build...

I saw a suggestion to try the 10/09 "picks" build, and have found it to be very reliable data-wise all day today. None of the white-signal-bars-with-no-data-connection...

Does the 10/15 build share the data enhancements of the 10/09 picks build? Are others having similar data issues with the current builds?
[Verizon Samsung Galaxy S III] SymbioticGenius:
Yeah I finally got Friday's build running and noticed my signal is about ten higher than on the picks build. I thought the builds afterwards included them?
[Verizon Samsung Galaxy S III] WhammyDroid:
Chris,

I had the same issue with the 15th build. I am running the stock kernel.
[Verizon Samsung Galaxy S III] funnyperson1:
I'm on the 10/17 and my signal bars go grey a lot, but if I use an app I still have connectivity. For me at least it seems like the Google services are having trouble connecting but basic connectivity is a go.

Can you verify this isn't what is happenning to you?
[Verizon Samsung Galaxy S III] bmeek:
With the 10/18 build (native kernel, etc.), the intermittent grey/white signal bars, showing no data mode label such as 3G or LTE, ALL TCP/IP traffic was interrupted for both gapps and 3rd-party apps. Attempting connections would eventually succeed, but you could feel the phone heating up and watch the battery drain in the process...

I've continued to use the 10/9 "picks" build and it's working great - my signal bars have remained blue with smooth transitions between WiFi, 3g and LTE for nearly 48 hours...

I just received the ROMdb Dev Tool notification about the new 10/21 build, but I'm holding off on flashing it for the time being (unless Mastamoon wants something new along these lines tested, of course).
[Verizon Samsung Galaxy S III] mastamoon:
10/21 build in the OP

-- repo sync [MENTION=960757]3pm[/MENTION] EST

-- removed camcorder volume fix -- merged

-- removed qcril stubbed apn revert revert

-- added vendor/cm: Clean up init.local.rc - http://review.cyanogenmod.org/#/c/52137/ cuz its mine :)
[Verizon Samsung Galaxy S III] PerCompLLC:
Something screwy with today's build. 10/18 was running great. Updated to today's build and experienced 2 reboots within ten minutes. This is with the built in kernel. Just reporting my experience...
[Verizon Samsung Galaxy S III] mastamoon:
Weird. I haven't seen that, we're you doing anything when it happened.
[Verizon Samsung Galaxy S III] PerCompLLC:
First time it happened when I opened Scramble with Friends. The second time was sending a text to my wife via Handcent. Nothing has changed with my setup...

If nobody else is having any issues I guess I'll give it another go.
[Verizon Samsung Galaxy S III] xyrcncp:
Sorry if I may sound dumb asking this, but what exactly got removed here? Just anytime I see "qcril" I think of my Network Extender :p

Also, since this is the first time I'd be updating this ROM, any special things to do before flashing an update? Wiping anything, flashing the db deleter, etc...?
[Verizon Samsung Galaxy S III] :
Running 10/21

Navbar is still gone? I tried adding the actual line of code to the build.prop with no success. I also can't get my hardware buttons to light up.

'Back' animations in settings are a bit wonky. Anything to do with this? :

At least MMS has stopped causing reboots for me. I'm coming from 10/10
[Verizon Samsung Galaxy S III] HandsomeOne:
Rom loaded fine ,no reboots.Your cm-10.2-20131009-UNOFFICIAL-d2vzw-picks rom is the only 4.3 that i don't have data issues. lock from wifi to 3g or 1x everytime no 4G in my area. I also flash cm-10-21 nightly Data does not lock and most of the time is gone completely. Thank You?
[Verizon Samsung Galaxy S III] khymbote:
Was watching trailers on YouTube this morning and my phone locked up. Had to pull battery.
[Verizon Samsung Galaxy S III] Chris123NT:
I don't see how that is possible, we have a LOT of evidence to support one of those picks DO cause data issues. So much so that Steve completely overhauled the QualcommMSIM42RIL superclass last night.
[Verizon Samsung Galaxy S III] khymbote:
Apparently navigation isn't working for me either. Anyone else have issues?
[Verizon Samsung Galaxy S III] khymbote:
I have noticed on the 8/3 it won't go to sleep on its own.
[Verizon Samsung Galaxy S III] Restola:
Masta sent me a test video and it still seems soft.
[Verizon Samsung Galaxy S III] RRF12:
Running 8/02 build runs much better than 8/01 which was very good.The only thing I had one reboot no biggie.Really sweet Rom for such a short amount of time.Everything I have tried has worked 'very good Thanks appreciate it.
[Verizon Samsung Galaxy S III] damnyouwaffles:
Yeah it's still the same.
[Verizon Samsung Galaxy S III] ejackson:
On my clean install WiFi worked fine, but I had no root access? On 8/3 build.
[Verizon Samsung Galaxy S III] Chris123NT:
Yeah root seems totally screwed on that build, and wifi doesn't always work. It definitely doesn't work on clean flashes.
[Verizon Samsung Galaxy S III] zachf714:
It has to do with K trying to enable and get working SELinux on 4.3, I saw where he was trying it in the gerrit today
[Verizon Samsung Galaxy S III] ace000724:
Did you go into developer settings and change it to adb and app under root?

That's what did it for me but I also used SuperSu.
[Verizon Samsung Galaxy S III] Chris123NT:
Yeah, he added a bunch of crap in the msm defconfigs in the kernel for selinux=y and a bunch of other stuff. Betting that's the problem since the issue still happens even without building with SELinux enabled via policy or export HAVE_SELINUX=true.

Yes, if you remember I'm the one who originally posted those instructions on page 2 of this thread (or was it page 3? meh)
[Verizon Samsung Galaxy S III] swift2989:
Just read this http://xdaforums.com/showthread.php?p=44256838 should work fine and I'm running 08/03 build

Use this link: https://copy.com?r=7PeCci when you signup to copy.com so we can both get 5GB free!
[Verizon Samsung Galaxy S III] airmaxx23:
Thanks, once Focal is working properly I'm hoping it will be a little louder.
[Verizon Samsung Galaxy S III] damnyouwaffles:
I doubt it. Its a problem with cyanogenmod not using the microphones properly. Not the camera itself.
[Verizon Samsung Galaxy S III] Chris123NT:
Check and see if your phone is deep sleeping.
[Verizon Samsung Galaxy S III] Restola:
I'm not a developer, but my understanding is the right microphones are being used. It records in stereo.

The issue is that samsung does some other process to increase volume, and CM doesn't.
[Verizon Samsung Galaxy S III] damnyouwaffles:
Hmmm. Didnt know that. Thanks!
[Verizon Samsung Galaxy S III] damnyouwaffles:
OK so after two days, it seems that android system is back to normal, the screen seems excessive with lowest brightness but Im not sure the amount of hours we are supposed to be getting with in screen time normally.
[Verizon Samsung Galaxy S III] Prack:
Invisiblek 804 build just released. Flashing now :)
[Verizon Samsung Galaxy S III] damnyouwaffles:
Let us know how it goes!
[Verizon Samsung Galaxy S III] swift2989:
Sorry bro this is the best I can do at the moment since I have had it charging this whole time let me know if that helps answer ur question.

Use this link: https://copy.com?r=7PeCci when you signup to copy.com so we can both get 5GB free!
[Verizon Samsung Galaxy S III] PsiPhiDan:
The screen being high makes sense. That means you aren't doing much else.

Remember, there must be something that's a relatively high number because these percentages HAVE to add up to 100, being percentages and all.

Imagine calculating what's taking your energy every day, and you were lounging around nit doing anything. You would probably see "standing" as a high number and be surprised. This is sort of like that. Low screen brightness may help, but it's still a bigger battery sucker than anything else you've done in the hour you've been on your phone.
[Verizon Samsung Galaxy S III] zachf714:
[MENTION=4949513]Chris123NT[/MENTION] I did a build after qcril got merged last night and no lte :P just 3g and 1x
[Verizon Samsung Galaxy S III] Chris123NT:
Did it have this in it?

https://github.com/CyanogenMod/andr...mmit/1e30c5e5c694f19e1d50453609b9002972d5e2eb
[Verizon Samsung Galaxy S III] Chris123NT:
That's why, it SHOULD be fixed with the overhaul steve did last night.
[Verizon Samsung Galaxy S III] zachf714:
Ok , I must have built before the overhaul ... About 8:30 pm est

---------- Post added at 01:51 PM ---------- Previous post was at 01:40 PM ----------

Is the overhaul the mr1 compat ? Or is it on a separate github
[Verizon Samsung Galaxy S III] SymbioticGenius:
Running the 18th build under battery GPS showing on the whole time, no apps seem to be keeping it on. GPS status app says it's off as well as the nav apps. Anyone else have this issue
[Verizon Samsung Galaxy S III] Chris123NT:
Yeah, MR1 compat is it.
[Verizon Samsung Galaxy S III] TwistingSoul:
I didn't have to use the db deleter when flashing the 10/21 build, though u std have to clear RomDB's data to get the notification about the build.

This here XDA app seems a bit wonky, because it's FC'ing on me when I try to thank Masta's post about the recent build, and when I try to quote someone, I have to scroll down to the post below the one I want to quote, which then allows me to select the quote I want.

Not a huge thing, that, but at least I didn't have to backup my messaging storage again before flashing. :thumbup:
[Verizon Samsung Galaxy S III] mastamoon:
Test build....

http://truelinux.net/sch-i535/mastamoon/ROMs/test/cm-10.2-20131022-UNOFFICIAL-d2vzw.zip

Can you guys test this build out? Its the new merged qcril in mainline CM + some kernel stuff that needs to get tested.

Thanks!
[Verizon Samsung Galaxy S III] kenbrownstone:
Loading now
[Verizon Samsung Galaxy S III] kenbrownstone:
I'm loading now Masta...For some reason when I to quote you it qoutes the reply above you
[Verizon Samsung Galaxy S III] funnyperson1:
Wipe data in XDA app. This fixed that issue for me.
[Verizon Samsung Galaxy S III] kenbrownstone:
This build is good for me ..Just started getting those vzwm text ago for some reason.But its a solid build
[Verizon Samsung Galaxy S III] zachf714:
[MENTION=4949513]Chris123NT[/MENTION] hey is your commit on the gerrit to revert your previous revert in opt_telephony still needed ?
[Verizon Samsung Galaxy S III] Chris123NT:
I'm not sure yet, but it does update stubbed APN to the qcril standard, but it was reverted as part of the whole craziness to figure out data issues when qcril first went into testing.
[Verizon Samsung Galaxy S III] TwistingSoul:
Wiped data and even removed/reinstalled the app, but it's still happening.

Sorry for the thread hijack. As you were. Lol
[Verizon Samsung Galaxy S III] zachf714:
Alright I'll keep it in then until we know for sure. On another note have you noticed the new GPU drivers causing problems with animations
[Verizon Samsung Galaxy S III] xyrcncp:
Thanks.
[Verizon Samsung Galaxy S III] Chris123NT:
Yeah I've been noticing it on and off on d2 and jf.
[Verizon Samsung Galaxy S III] zachf714:
I think it was the caf merge on the 15th but am not sure because there is another caf merge that edits it again 3 days later
[Verizon Samsung Galaxy S III] mastamoon:
10/22 build in the OP

-- CM merged qcril into main

-- NAVBAR is back!

-- removed all RIL cherrypicks/reverts for clean slate

-- added a bunch of kernel cherrypick for testing

-- changed a build.prop to get rid of the back button animation issue when more than 1 screen deep

-- repo sync @ 3:30PM EST
[Verizon Samsung Galaxy S III] Chris123NT:
Did that animation bug affect swiping recent apps off the screen as well?
[Verizon Samsung Galaxy S III] mastamoon:
I rarely do that so I didnt notice any issue there. Ill check if its working on my build in a minute.
[Verizon Samsung Galaxy S III] zachf714:
You changed it to disable hw overlays right ?
[Verizon Samsung Galaxy S III] mastamoon:
Set debug.composition.type to gpu I'm guessing it's probably the same thing but sticks through reboots and I have it set on my builds by default.
[Verizon Samsung Galaxy S III] mastamoon:
Works fine on my build.
[Verizon Samsung Galaxy S III] zachf714:
Yup same thing
[Verizon Samsung Galaxy S III] MG386:
10/22 running great, feels smoother/ more buttery than previous few, not sure if kernel tweaks are responsible or not, but running great. Thx.
[Verizon Samsung Galaxy S III] kenbrownstone:
What do I need to do to get hangouts to work on newest build. Its says Google play services isn't avalible for my device
[Verizon Samsung Galaxy S III] zachf714:
YouTube is probably broken for you guys ... These top 3 reverts are needed to fix it modifying the MDP driver is a bad idea when modifying timeout (yes this is my kernel but my kernel is basically cm kernel with picks that they have turned down merged ) https://github.com/zachf714/android_kernel_samsung_d2/commits/fenderkernel-jb-mr2
[Verizon Samsung Galaxy S III] mastamoon:
YouTube works for me, what are you seeing?
[Verizon Samsung Galaxy S III] zachf714:
It just wouldn't load a video, so I reverted those and boom