yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] sivarticus85:
This is actually normal. I don't remember where I saw it here in the forum, but the kernel does go to 384, but CPU reporting apps like No Frills and CPU Spy aren't reporting accurately. Mine does the same thing, but I'm sure I wouldn't be able to go all day and have 3 hours screen time if the CPU never dropped below 918.
[Verizon Samsung Galaxy S III] goldsmitht:
Switched to interactive and now seems to be dropping down to 384, so it may be the ondemand isn't working right
[Verizon Samsung Galaxy S III] jalewis:
I haven't encountered that issue at all with the built in tethering and I used it for a few hours two different times over the weekend.
[Verizon Samsung Galaxy S III] vdefender:
Could someone explain the data wipe issue with TWRP? Is this an issue specifically with TWRP and CM10.2, or is it an issue with TWRP even on 10.1? Right now I'm on CM10.1, I want to switch to 10.2 but I really don't want to use CWM. When I flash CWM I can't seem to get it to do a nandroid backup, it just fails. But TWRP works fine for nandroid backups. It's very weird.
[Verizon Samsung Galaxy S III] goldsmitht:
what issues? None here, that i have found.

tips: if flashing 10.2 over 10.1, then i would wipe data and clean flash latest Mastamoon's Unofficial. in TWRP, just go to the wipe button, and swipe the bottom button. This will factory reset your phone, but will NOT wipe the SDCard.

then flash the latest and current gapps.

then if you want to flash nightly updates to 10.2, just wipe dalvick and cache and flash nightly. Or i wipe the dalvick, cache, and system (I think, can't get into phone at the moment) but this will also require you to flash gapps as well. completly dirty flashing (dalvick and cache wiped only) does not require you to re-install gapps everytime, but has resulted in a few missing apps on occasion.

:cyclops:
[Verizon Samsung Galaxy S III] mastamoon:
10/15 build in the OP

-- nav bar cherrypicks needed rebase --left out

-- checking out the qcril+caf repo for even more winz?!1one

-- using AOSP GCC 4.8 toolchain

-- repo sync @ 2pm EST

If your data doesn't come up right away on first boot, either let it sit for a bit or maybe try a reboot. Mine seemed to hesitate on first boot, but eventually came up (2 minutes) and has been quick after reboot since. YMMV
[Verizon Samsung Galaxy S III] goldsmitht:
what are you running for govenor and I/O schedular? I had some issues with ondemand not dropping below 918 (see screenshots somewhere above) so i switched to interactive / row. was just curious if you had seen this or what you were running

thanks again, handoffs have worked great and was getting better service (placebo?) in some areas!

:highfive:
[Verizon Samsung Galaxy S III] mastamoon:
I run stock settings.

The 918 thing is a false reading. It is caused by the inkernel mpdecision cherrypick. I left that out for this build just because I havent run in a bit without it and wanted to see the effects if any. It probably will never get merged so if it doesnt make a big enough difference im going to drop it from my builds.
[Verizon Samsung Galaxy S III] senorbuck:
My data came right up after flash 'n boot. :good:
[Verizon Samsung Galaxy S III] mastamoon:
Great! I figured it was my location more than anything, but just wanted to put a warning on there JIC it wasnt.
[Verizon Samsung Galaxy S III] sbenson1226:
Is there any way to get the front facing camera to work outside of the stock camera without it crashing and rebooting the device?
[Verizon Samsung Galaxy S III] vdefender:
What you've described is what I want to do but in the OP, Mastamoon gives a warning not to data wipe if using TWRP. Is that an outdated warning?
[Verizon Samsung Galaxy S III] goldsmitht:
Not sure, unless faulty reading is limited to ondemand only. Interactive shows it dropping down to 384, as well as 918 and 1518
[Verizon Samsung Galaxy S III] thelangosta:
I know that data issues(the RIL mainly) have been kind of a problem but, is it possible that the lte radio in our phones is just buggy. I am on TW right now and was in an area that I know has 4g even though my phone was only showing 3g. I toggled data but nothing changed so I then rebooted and lo and behold the 4g icon pops up with three bars. Soo, even on TW, data hand off is a problem!?!? Does a logcat show the data handoff? Kmesg? Would it even help with CM development to see the logs from a TW rom? Sorry for the ramble...
[Verizon Samsung Galaxy S III] Hybridnoob:
That seems a little overkill and rarely necessary.

On one of my phones, I clean installed CM10.2 by performing a factory reset. I have since updated the ROM using CMupdater and not wipe any caches, without issue or loss of apps.

On my other S3, as a test, I just used CMupdater to upgrade to CM10.2 over top of CM10.1. I didn't wipe anything and had no issues. Additionally, I flashed the the 4.3 GApps. I've had no issues with that phone despite doing several nightly updates and have never wiped cache and dalvik since upgrading to CM10.2. The only time I did a factory reset was when clean installing CM over TW.

I used to wipe cache and dalvik often, but this writeup convinced me to drop my old habits:

http://forum.cyanogenmod.com/topic/74526-how-do-i-update-cyanogenmod/#entry402538
[Verizon Samsung Galaxy S III] senorbuck:
Noticed this too. For example with Instagram, front facing pic attempt makes the phone go black and reboot. Stock camera is fine.
[Verizon Samsung Galaxy S III] TwistingSoul:
Seconded. I waited maybe less than a full minute, and data came right back.
[Verizon Samsung Galaxy S III] Atamagaokashii:
I haven't been on data yet but I'm seeing improved signal from what it usually has been since all this ril stuff started happening...
[Verizon Samsung Galaxy S III] Atamagaokashii:
I realize this probably isn't rom related but... I was just streaming a TV show to my phone on moviedroid and my phone is reading at 117° F. Not good right? I can't think of anything I've done... I'm ocd to the limit of the stock kernel no UV. Wtf?
[Verizon Samsung Galaxy S III] V3TTOO:
The FC I get is com.android.phone, not .telephone. Anyways, just restoring back to where I was. I'll wait to see how things are when I come back from Vegas.
[Verizon Samsung Galaxy S III] lostwhat83:
My phone gets up to 120 sometimes. I think it is just these phones or both of us are just lucky I suppose.
[Verizon Samsung Galaxy S III] PerCompLLC:
Were you using a custom kernel by chance? I know that BMW, LK and KT747 haven't been updated with the latest AOSP kernel and will produce exactly that error (if they boot at all). That is exactly what I experienced with the latest LK. To fix I booted into recovery and just flashed the latest masta unofficial over the top (dirty). Worked like a charm for me...
[Verizon Samsung Galaxy S III] titanshadow:
I had an issue with TWRP where a data wipe hosed my phone. Basically there seems to be some kind of problem when it formats the data partition and it doesn't happen all the time or on every device.

I don't know about the 10.1 or 10.2 issue as I only used TWRP until I had to redo my phone. If you're not having issues, I wouldn't worry unless you plan to wipe your phone completely.

I also found that using a 3rd party service to remote wipe my phone (like Lookout and Google Device Manager) failed to initiate the wipe at all on TWRP.
[Verizon Samsung Galaxy S III] RED ZMAN:
I haven't updated in about a month, do I still need to delete those database files if I flash the latest version?
[Verizon Samsung Galaxy S III] senorbuck:
Did some searches and this seems to be a CM issue if I'm not mistaken? I can't honestly recall if this ever worked with 3rd party camera apps.

---------- Post added at 09:58 AM ---------- Previous post was at 09:45 AM ----------

So, just had the phone reboot randomly. Was wifi tethered, phone rebooted, got the com.android.phone error that I couldn't bypass (had to pull battery). Booted up the phone and I was roaming. Roaming went away and I had a connection again. Data wasn't working, checked network settings and my CDMA subscription setting had changed to NV. Changed it back to RUIM/SIM and rebooted. Back to normal.

I only tend to have these issues when tethered :( Trying to gather some logs for ya'll.
[Verizon Samsung Galaxy S III] jalewis:
When I flashed 10-15 I waited over 10 mins and never got data. I rebooted and started having FC issues. Reflashed, formatted system, etc with no luck. Ended up flashing 10-7 and it booted with no FC issues and data...
[Verizon Samsung Galaxy S III] mastamoon:
I just had this pop up on a build I did this morning... tried reflashing the same rom and wiping caches.. neither worked. Then I flashed my qcril-dbdeleter.zip thing in the OP and it stopped all the FC's. Boots fine now.
[Verizon Samsung Galaxy S III] goldsmitht:
were you using stock or other kernel?
[Verizon Samsung Galaxy S III] adammwhiles:
I had the exact same issue. After flashing I let it sit for about 30 minutes and still no data. I toggled data/airplane mode etc. and no luck. Rebooted a handful of times, no luck. Dirty flashed and no luck, clean flashed again, no luck. Data was completely dead regardless of what I did. Ended up going back to a TW rom for the time being. This was stock everything just the way it is.
[Verizon Samsung Galaxy S III] mastamoon:
Wow that was a bad one. :(

Did you check to see if your imei and other info was missing? Maybe it wanted a NV/RUIM toggle?
[Verizon Samsung Galaxy S III] mds96:
Just dirty flashed 10/15 over 10/11 and had LTE within 10 sec after the "Android Is Upgrading" popup, and no fc's of any kind. I've also rebooted a few times with no data issues or fc's upon boot up.
[Verizon Samsung Galaxy S III] sivarticus85:
Had a nasty lockup and freeze last night. Using bluetooth audio in my car, I received a call from my wife, and when I answered the call using the car controls, my radio and phone both froze. I couldn't turn either one off, and ended up having to pull the battery on my phone. Not sure if it was my car or the phone acting up. Clean flash on stock kernel. Any thoughts?
[Verizon Samsung Galaxy S III] zachf714:
Looks like the caf branch is a bad idea .. I actually did a build last night and it wouldn't even boot , I don't know if I should point it to that or kernel patches but at this point I am not sure
[Verizon Samsung Galaxy S III] kenbrownstone:
Is link down for the 10/15 build?
[Verizon Samsung Galaxy S III] mastamoon:
Works for me.. http://bit.ly/16e09Ra
[Verizon Samsung Galaxy S III] mastamoon:
My builds are all booting fine. Are you sure you have the full list of new repos/branches in your local manifest?
[Verizon Samsung Galaxy S III] zachf714:
Yeah, I also made some kernel changes so that may have done it
[Verizon Samsung Galaxy S III] kenbrownstone:
Weird my phone stays on 0% the whole time
[Verizon Samsung Galaxy S III] mastamoon:
Its downloading fine on my PC.. try the non shortened link here.. http://truelinux.net/sch-i535/mastamoon/ROMs/CM10.2/cm-10.2-20131015-UNOFFICIAL-d2vzw.zip
[Verizon Samsung Galaxy S III] kenbrownstone:
My phone must be messed up.I've used down loader Pro...ES downloaded...and stock loader and none will load it.....but no problem.....I will work on it later
[Verizon Samsung Galaxy S III] mds96:
I'm not sure what would cause this, but I will have someone call me a couple times while I'm BT'd to my car stereo when I get off of work tonight. Sorry I can't help right now. Maybe Masta has an idea of why that would happen. Stock kernel, 3rd party kernel, OC'd, UV'd??
[Verizon Samsung Galaxy S III] senorbuck:
Of course this happened again. When not capturing logs... So random.
[Verizon Samsung Galaxy S III] sivarticus85:
I posted that I'm on stock kernel. I don't OC or UV at all. I don't really mess with that stuff.
[Verizon Samsung Galaxy S III] jalewis:
Stock kernel.

---------- Post added at 03:41 PM ---------- Previous post was at 03:38 PM ----------

I'll try that if tonight's build does the same thing.
[Verizon Samsung Galaxy S III] Stealth111:
:confused: ...............................................................................:rolleyes:
[Verizon Samsung Galaxy S III] mastamoon:
having some technical difficulties with the build box today so no build.. Sorry :D
[Verizon Samsung Galaxy S III] Desterly:
This is somewhat true.

The problem is our camera blobs are ancient (no newer ones have been released) and have many features not enabled in them that are now required for both the newer kernel as well as newer userland.

In order to get the front facing camera working we had to hack in a bunch of commands to the gallery to enable these features.

until we either get updated camera blobs or we write a camera wrapper, most 3rd party camera items won't work correctly.
[Verizon Samsung Galaxy S III] MWFD:
Please forgive me if this has been covered before, but I've searched various threads/forums and couldn't find a guide or way to do this for CM 10.2 on Verizon GS3. I just want to know if there is an easy way/flashable zip that will allow for a transparent notification bar? I am running Chris' unofficial 10/6 build. This build has had the fewest issues for me with 3G to 4G handoffs as well as 4G down to 3G. Thank you.
[Verizon Samsung Galaxy S III] mds96:
Use Xposed Framework Installer and download the XBlast Tools Module. I use it for Transparent Status Bar, and Transparent Notifications

---------- Post added at 10:22 PM ---------- Previous post was at 10:19 PM ----------

Sorry, I couldn't test tonight. Just got home from work, tired as hell! Maybe tomorrow sometime
[Verizon Samsung Galaxy S III] sbenson1226:
Is there anything we can do to expedite this? I imagine this is pretty low priority but I'd be more than happy to help out with testing.

This and the Bluetooth toggle bug are the only two issues I have on this entire ROM, pretty impressive for software that was never meant to grace our screens.
[Verizon Samsung Galaxy S III] goldsmitht:
kernel changes?

I know there were some kernel changes, but i also just noticed that ondemand will now take the 384 setting and it holds. And noticed that i am getting more than just a couple ranges used. Before it was 918 1512 and sleep, now getting a lot more.

not sure if this was intentional, but it works

---------- Post added at 08:16 AM ---------- Previous post was at 08:15 AM ----------

what's up with bluetooth toggle? Mine works with my earbud; sometimes have to go in and clear it after an upgrade, but most of the time, i toggle bluetooth on phone first, then turn on my earbud, and it will normally connect right away

:cyclops:
[Verizon Samsung Galaxy S III] Chris123NT:
Masta dropped the mpdecision cherry-pick for the kernel so that's probably why things went back to normal for you.
[Verizon Samsung Galaxy S III] sbenson1226:
Same bug that's always been there in CM on this phone... When you're connected to a Bluetooth device and toggle Bluetooth off, it gets stuck and never turns off. Once this happens you cannot reconnect to your Bluetooth device until you either reboot or force close it under all apps.
[Verizon Samsung Galaxy S III] SymbioticGenius:
Clean flash fixed that for me two weeks ago.
[Verizon Samsung Galaxy S III] goldsmitht:
I haven't seen that in a while; what version are you on?
[Verizon Samsung Galaxy S III] sbenson1226:
Clean flash of the latest.
[Verizon Samsung Galaxy S III] MWFD:
Tanks mds, I appreciate the advice. Now that I've installed Xposed Framework and installed the Module, will I have to 'undo' any of these mods/changes if I flash to a new version of masta's or Chris's unofficial ROM? Or will I be able to do a dirty flash (I always wipe cache and dalvik cache) like I normally do to a new nightly without running into issues since I've added this module?

Thanks!
[Verizon Samsung Galaxy S III] Atamagaokashii:
All you'll have to do is open xposed and reinstall the framework with every flash then soft reboot unless you lump in other changes that require reboots like viper, etc.
[Verizon Samsung Galaxy S III] Zacharybinx34:
Is there a way to make so my phone doesn't play my alarm clock through my bluetooth. If I leave it connected, it plays through that, and since I don't sleep with my bluetooth on that's not very useful.
[Verizon Samsung Galaxy S III] mds96:
You're welcome! Do exactly as the postee above said and you should be fine! Let us know if ya have any problems or questions!
[Verizon Samsung Galaxy S III] mastamoon:
10/17 build in the OP

-- weather picks got merged -- removed from CP list

-- navbar picks still need a rebase on the new qcril repos... wont be coming back till then

-- 2 new picks to help with data issues in certain situations

-- repo sync at 3PM EST
[Verizon Samsung Galaxy S III] Reborn627:
I know this is quick, even before Mastamoon has posted the update here but I'm getting "com.android.phone has stopped" straight out of flash and persistent after a reboot. Just FYI

Ray

Edit: Posted as Mastamoon was posting apparently :-/
[Verizon Samsung Galaxy S III] MWFD:
When you say 'reinstall the framework', do you mean that before I flash the new nightly, I need to open Xposed app > Framework > click Install/Update? I know that AFTER I flash the new nightly, I'll likely need to reinstall/enable the modules that I've added (so far just XBlast) to get my status bar, colors, etc. back the way I like, but I want to know what I need to do to get back to 'stock' nightly so that I won't have any issues flashing the new nightly.
[Verizon Samsung Galaxy S III] sbenson1226:
Same here, I can't get past my lock screen.
[Verizon Samsung Galaxy S III] senorbuck:
Working fine for me. I dirty flashed the build, then gapps, then the .db deleter thingy and rebooted. No issues.
[Verizon Samsung Galaxy S III] sbenson1226:
This thing?
[Verizon Samsung Galaxy S III] Reborn627:
I clear dalvik, cache & system every time and flash gapps with each new update. Deleted the .db 3 flashes ago so I wouldn't think I'd need to again. Strange, I tried twice with the same result.

Ray
[Verizon Samsung Galaxy S III] senorbuck:
Yessir! :good:
[Verizon Samsung Galaxy S III] MG386:
10/17 working great here.

Format cache/dalvik/system

Flash ROM/gapps/boot animation/qrildb deleter
[Verizon Samsung Galaxy S III] Mattish13:
10/17 working fine here too. Wiped cache and dalvik cache, flashed Rom only. Sent texts without crashes.
[Verizon Samsung Galaxy S III] mastamoon:
Sorry guys.

Depending on what build you were on before you might have to do the db wiper thing more than one time for a bit till these repos get merged and official.

If you were on official or a build before this past week, you probably didn't have to wipe cuz invisiblek fixed the db upgrade process.

If you were on one of my last few builds you where you previously had to wipe the db's, you likely have to wipe them again as when the we're wiped and recreated the first time it was only half corrected.

If your on today's build and future builds you probably won't have to wipe the db's again. But at some point you might when this all goes official or the decide to fix the database upgrade differently.

Hope that halfway makes sense and sorry I didn't warn ahead of time. Though the OP plainly states that if you get FC's you need to flash that zip or wipe the databases manually.

^_^ ;)
[Verizon Samsung Galaxy S III] mds96:
Yeah the database deleter zip did the trick for me also!
[Verizon Samsung Galaxy S III] sbenson1226:
Fixed here as well, thanks.
[Verizon Samsung Galaxy S III] TwistingSoul:
Maybe it's my Wi-Fi, or my impatience, but the download via the RomDB app, or even directly from the thread in the OP isn't getting past 1%.

Is there a fair bit of congestion on the servers, maybe?
[Verizon Samsung Galaxy S III] mastamoon:
Very possible.
[Verizon Samsung Galaxy S III] mastamoon:
Though I just tested it on my phone via wifi and was downloading at over 3700kb/s so it might just be you :)
[Verizon Samsung Galaxy S III] TwistingSoul:
I was thinking the same thing, so I downloaded it on my PC, which completed in about 30 seconds, then copied it over to the same download folder your other stellar builds are saved to from RomDB.

I installed it via CWM, now I'm getting constant messages about com.android.phone having stopped, so I'm going to flash back to your 10/15/2013 build.

This is all stock kernel, btw.

I'll next download the .db deleter thing to see if that may be the cause, though I don't remember the phone process crashing due to that potentially corrupted file.
[Verizon Samsung Galaxy S III] mastamoon:
It will fix.
[Verizon Samsung Galaxy S III] Atamagaokashii:
No. You don't need to go back to stock to flash nightlies. If you choose to dirty flash the new nightlies all you have to do is open xposed->click framework->click install/update->reboot/soft reboot (your preference) _AFTER_ you flash.

This is because when you flash a ROM you are overwriting the changes xposed makes to the framework to allow the modules to run.

As long as you are dirty flashing you don't need to do anything else.
[Verizon Samsung Galaxy S III] Reborn627:
I tried 6 ways to Sunday to get this working with no success. Even cleared data with system,cache and dalvic and system with the same result.real PIA. So,I'm back to the 10/15 waiting for all my apps to load,oh what joy! No sure why it's worked for me. Oh well.

Ray
[Verizon Samsung Galaxy S III] khymbote:
Yep tried to just wipe system and cache like I normally do and I couldn't get past the phone.com crashing.
[Verizon Samsung Galaxy S III] mastamoon:
The db deleter didn't clear it up?
[Verizon Samsung Galaxy S III] Reborn627:
Nope,tried 3 times. Even went in through recovery to manually delete the dbs and it still didn't work. Each time I booted to the 10/17 build I got the "unfortunately com.android.phone stopped working" after it rebuilt the dalvic cache. Each time I tapped ok the error came back making the phone unusable.

Ray
[Verizon Samsung Galaxy S III] mastamoon:
Wow. Hmm.
[Verizon Samsung Galaxy S III] Reborn627:
Yeah, that's kinda what I said. First time I've had any real trouble. Guess I was bound to at some point.

Ray
[Verizon Samsung Galaxy S III] mastamoon:
What recovery? Flashing any other mods?
[Verizon Samsung Galaxy S III] Reborn627:
TWRP and no,I'd never cheat on you lol!

Ray
[Verizon Samsung Galaxy S III] mastamoon:
Latest twrp?
[Verizon Samsung Galaxy S III] jalewis:
After my no data and FC issues with 10-15 (ended up back on 10-10), just dirty flashed 10-17 and got data within 30 seconds and haven't seen any issues.

Still haven't had to remove those db files...although it sounds like they're what caused my issue Monday...

Thanks for your work masta.
[Verizon Samsung Galaxy S III] Reborn627:
2.6.3.0
[Verizon Samsung Galaxy S III] mastamoon:
K. Perplexed
[Verizon Samsung Galaxy S III] TwistingSoul:
I'm also using the latest CWM (and stock kernel, as previously noted), but after the last post about the deleter file not working to fix this issue, I'll hold off on 10/17 for now.

Also, I now seem to have lost my adb connection to my phone. The folder /data/misc/adb/ is completely blank, and I have no idea how to fix that connection so that ADB is usable again and visible on Windows 7.

I've tried revoking, disabling/enabling ADB (though oddly enough, I have no option to switch from MTP to PTP (Camera) when the ADB options are enabled in my Developer section), but nothing is seeming to restore my ADB access.

I have the latest SDK files, and I've confirmed my ADB version is 1.0.31.

Curiouser and curiouser...
[Verizon Samsung Galaxy S III] mastamoon:
Reboot in download mode, plug into pc, unplug, reboot.
[Verizon Samsung Galaxy S III] TwistingSoul:
Thanks. I'll try that when I get home tonight.
[Verizon Samsung Galaxy S III] PwnCakes193:
So what's the benefit of swtiching to the QCRIL branch? As far as I'm aware the issues should only be affecting d2vzw and such.
[Verizon Samsung Galaxy S III] zachf714:
Fixes data drops ... And it also caused data drops on d2spr ... It will also be the new base for the Qualcomm ril across the board for cm
[Verizon Samsung Galaxy S III] PwnCakes193:
Is it only for CDMA devices though? Debating on switching to it but I can't really tell the benefit as of yet on GSM and such.