yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] SilentAce07:
No, I see why you are confused but thats not how it is.

If you dirty flash CM over a working rom (touchwiz, AOSPA, etc), then it clears the activation issue.

If you clean flash it, the activation problem occurs.

However, to the point made earlier: It is not that data is being deleted when clean flashed that causes the problem. Why do I know this? Because a dalvik/cache wipe AFTER the activation bug occurs fixes the issue for the next boot.

That being said, it doesnt make sense when the problem occurs. If it occurs during a shut down, a sudden battery pull from a first boot should bypass the issue for the next boot.

If it were during the start up of the phone, however, it shouldn't make a difference if you wipe dalvik/cache before the boot because the problem would be occuring after.

So, yeah. I'm at a loss. Maybe the problem occurs when the phone itself turns on BEFORE recovery boots, therefore when a recovery initiated cache/dalvik wipe occurs, it wipes the issue and the phone boots straight from there.
[Verizon Samsung Galaxy S III] V3TTOO:
I did a clean install from stock 4.1.2 to 3/20, then did a dirty flash over that to 3/21. No issues and I have restarted several times.

Edit:

Can someone that is having this issue try something for me, if you have time to kill. Odin to stock, doesn't matter which, just end up at 4.1.2. Once there, try to do the Root/Unlock/Recovery(NEW METHOD IN CM10.1 THREAD). Once there, download the latest Masta build and gapps to the SD card, go to recovery, wipe data/cache, then format /system /data /cache and /sdcard. Make sure not to wipe /external_sd, as that is your card. Once that is done, install the ROM and gapps. This is pretty much what I did. Can someone check if that fixes the issue?

Or am I completely off, and the issue only happens when you do a wipe data/cache when going to another ROM?

---------- Post added at 03:54 PM ---------- Previous post was at 03:37 PM ----------

Handcent got updated and it works on 4.2 ROMs. That is all. :silly:

---------- Post added at 04:30 PM ---------- Previous post was at 03:54 PM ----------

Hey, I see you are still doing the Linario builds. Do you see a noticeable difference?
[Verizon Samsung Galaxy S III] V3TTOO:
Running todays build, and the screen was stuck on off, no lights at all.

Did a hard reset. That is VolDown + Home + Power. Easier than battery pull. And this proves the phone was still on.
[Verizon Samsung Galaxy S III] luv2increase:
Yes definitely. I'd stick with the 3-15 build with ktoonz linaro 3-14 kernel. That gives the best performance on our phones for now until Linux 3.4 kernel and based ROMs improve a bit.

For now, 3.4 offers no improvement over 3.0. It is just less refined, slower and has more bugs. Who wants that?

Sent via Crossbreeded, 100% V6 Supercharged. KT747'd 3-14 and Linaro Built Unofficial 3-15 and finally Odexed - OC'ed 2.1Ghz
[Verizon Samsung Galaxy S III] Chris123NT:
On 3/21 now, seems pretty good. Experimenting with the KT747 3.4 kernel, see what the battery life is like with this kernel. I remember it being very good in the past on CM.
[Verizon Samsung Galaxy S III] wrippel82:
Getting a little frustrated.. Getting serious random reboots with this and the official.. With the newest gapps.. Anyone else getting these? I should note that I'm on mb1 modem.
[Verizon Samsung Galaxy S III] Chris123NT:
You using the stock kernel or one of the custom ones?
[Verizon Samsung Galaxy S III] cammykool:
What was the last known good build?
[Verizon Samsung Galaxy S III] Reborn627:
I was running the 3-16 build until yesterday when I flashed the 3-21 afternoonly. I haven't had an issue yet. Still trying to get a feel for the battery life but otherwise I have no complaints... Well, I have one but it's a long standing issue with JB. I'm hoping that the bluetooth Map issue is solved at some point. Not major but it'd be nice to have working.
[Verizon Samsung Galaxy S III] mastamoon:
Have you log catted your issue and submitted it to the bug tracker? Make sure your using official.

If you look at Gerrit you can see issues being fixed from bug tracker whenever you see JIRA.

Not saying it will happen soon but they need to know what's broke before they can fix.
[Verizon Samsung Galaxy S III] Chris123NT:
Is your experience showing better or worse battery life on 3/21 compared to 3/16?
[Verizon Samsung Galaxy S III] Reborn627:
Well, I'm pretty limited in knowledge of all of this. I'm vaguely familiar with pulling a log but that's about as far as I go. It's only this week that I've begun to learn about cherry picks & git and all of that. I believe that the MAP issue had worked in CM10 but broke when 4.2 dropped. Not sure how to log cat an issue that just doesn't function. It's not like it "loads" then crashes, it simply doesn't seem to exist. I have read that the developers that worked on Bluetooth in CM are no longer doing development work. Again, I'm very limited in my understanding of all of this. I do appreciate all of the work that those in the know have done. Thanks to all of you!

Peace,

Ray

---------- Post added at 08:59 AM ---------- Previous post was at 08:56 AM ----------

I'm not sure yet. I put a full charge on my phone at about 9:00 last night. I'm going to run it all day and see what I come up with. If I don't have to plug it in until I get home then I'll say it's at least the same. I'll keep you posted.

Ray
[Verizon Samsung Galaxy S III] luv2increase:
Paranoid Android is based off Google AOSP

Sent via Crossbreeded, 100% V6 Supercharged. KT747'd
[Verizon Samsung Galaxy S III] goldsmitht:
how about PACMan ROM? Thought it was, but can't figure out from their forum. Says it is based on all of them, but can't tell which is used for base.
[Verizon Samsung Galaxy S III] wrippel82:
Stock Kernel. Nothing different..
[Verizon Samsung Galaxy S III] luv2increase:
It is based off of CM

Sent via Crossbreeded, 100% V6 Supercharged. KT747'd and Linaro Built
[Verizon Samsung Galaxy S III] Reborn627:
OK, so I did find this http://review.cyanogenmod.org/#/c/29952/ . Does this mean that it is an issue that is currently being worked on? My guess is that it's the bluetooth.apk file that is at issue and not the ROM itself. Would it cause major problems to pull the bluetooth.apk from, lets say, the stock GS3 TW rom and replace the one being issued with CM10.1?

Ray
[Verizon Samsung Galaxy S III] mastamoon:
That commit was merged, so no more going on with it. There might be more stuff on CAF to be ported.. their site is such a PITA to navigate.. but ill look.

I think you will have bad things happen if you try to use any file from TW in an AOSP based rom. Recoverable bad things, but bad things none the less.
[Verizon Samsung Galaxy S III] Reborn627:
Yeah, I noticed that in the stock ROM there are 3 or 4 different apks for the bluetooth. Rather than just a Bluetooth.apk there is a BlutoothAvrcp.apk, BluetoothMap.apk and BluetoothTest.apk. I should have known it wouldn't be quite that simple.

Thanks,

Ray
[Verizon Samsung Galaxy S III] mastamoon:
3/22 build in OP

-repo sync @ 3pm EST
[Verizon Samsung Galaxy S III] ugachris:
Did you see that Invisiblek checked in a change for the MMS size? It got reverted, then that got reverted. Is that the same change you are making or is it different?
[Verizon Samsung Galaxy S III] mastamoon:
Yeah, it's partial that, I just upped the file size a lil bit more.
[Verizon Samsung Galaxy S III] Reborn627:
OK, here is what I've run into today. At 4:40pm my battery at was at 7% after minimal usage. Not the best battery life but I have seen worse with other CM10.1 ROMS. Now, one thing to keep in mind. I am running the Snapdragon BatteryGuru app. This weekend I'm going to disable the app and see if it really makes any difference at all. I'm not really sure if 20hours with minimal usage is in line with where it ought to be but it seems a little short to me. I'll let you know what I find over the weekend.

Peace,

Ray
[Verizon Samsung Galaxy S III] BlueCross:
After the new kernel was merged, this rom has become pretty buggy. Is there a reason we can't use imoseyon's lk?
[Verizon Samsung Galaxy S III] icon123:
I don't know how much it will help, but you can use imoseyon's kernel. Just make sure you get the AOSP one and v5rc5 is the newest build I believe.
[Verizon Samsung Galaxy S III] BlueCross:
Clearly I'm flashing the wrong one (v2.9). Every time I flash it, my phone refuses to reboot.
[Verizon Samsung Galaxy S III] odub303:
Clearly you need to read both threads a little more.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] BlueCross:
Clearly, you need to get on your knees and tell me you love me.
[Verizon Samsung Galaxy S III] Stealth111:
DAMN!! :eek:

Sent using Tapatalk
[Verizon Samsung Galaxy S III] Obaterista93:
Well that escalated quickly.
[Verizon Samsung Galaxy S III] Chris123NT:
Yeah that does seem a bit on the low side for minimal usage. I have a 4200 MaH battery and I got through 2 work days with medium usage which isn't horrible, but I would get through 3 on TW based ROMs. But I like CM a lot more plus BT audio streaming actually works on CM whereas on TW it crackles like hell.
[Verizon Samsung Galaxy S III] V3TTOO:
I have noticed that the battery is dying quicker than before, and I am getting issues with the phone freezing up while locked. I still get the last notification light, but not any new ones. :-/

Just noticed that I have some weird battery issues. The battery will lose about 5% instantly on the battery chart.
[Verizon Samsung Galaxy S III] Chris123NT:
Has this been happening for a while or did it just start with the 3.4 kernel?
[Verizon Samsung Galaxy S III] V3TTOO:
It just started about a week ago, once I got my phone back from repair and installed the new builds. I think the one I had before was the last one Invisablek posted when Masta was out on vacation. Think it was like 03/10 or something like that.

Just went over the thread and it seems it also had 3.4 So that is not a cause of issues, IMO.

EDIT: Can't verify if it does or doesn't have 3.4.

---------- Post added at 06:30 PM ---------- Previous post was at 06:18 PM ----------

So, I never dove into kernels. Is it just a recovery install? Anyone have any recommendations?
[Verizon Samsung Galaxy S III] Chris123NT:
Masta, FYI the longpress bug is back. I just got hit with it after just shy of 24 hours uptime. So it appears the fix is still needed.
[Verizon Samsung Galaxy S III] V3TTOO:
Ok, F this. I just installed the new one and the battery is dying quicker.... Going to the last good rom that I had (03/10) and checking if I still have issues.
[Verizon Samsung Galaxy S III] mastamoon:
Dang.. Ah well. I'm over 24 hours with no issue.
[Verizon Samsung Galaxy S III] V3TTOO:
Well, that is why I want to go to a build I know I had little to no issues with. If I still have issues, I know there is something else up.

Also, if I change ROMs, does that also replace the kernel? Does that mean I have to reinstall it with every ROM update?
[Verizon Samsung Galaxy S III] Chris123NT:
Yes, changing the ROM reverts you to the default kernel for that ROM. What kernel are you using btw?
[Verizon Samsung Galaxy S III] V3TTOO:
I did end up installing 03/10, but I am still having an issue with SMS taking forever to send. That just started today. Might try a full wipe install and see if that helps.
[Verizon Samsung Galaxy S III] mastamoon:
Most roms have a kernel included.
[Verizon Samsung Galaxy S III] Chris123NT:
Before you full wipe you could try clearing data for the messaging app and see if that helps.

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

Oh btw just saw this http://review.cyanogenmod.org/#/c/34194/

Apparently the CM guys think it's fixed in 3.4. Boy are they in for a surprise :/ lol
[Verizon Samsung Galaxy S III] V3TTOO:
Thanks. I tried it with no success. I was using Handcent. Stock has same issue. Before today it would send almost right away. Now it takes about 8 seconds. going to do a restore to yesterday and see what happens.
[Verizon Samsung Galaxy S III] mastamoon:
I think noobnl did that as a pre-commit based on me reverting and also having thought 3.4 cleared the issue up. We talked about it for a bit in IRC today actually.
[Verizon Samsung Galaxy S III] V3TTOO:
Yeah, something is definatly up. Everything is just running slow. :(

---------- Post added at 08:22 PM ---------- Previous post was at 07:48 PM ----------

Just did a complete wipe of everything, format of the partitions. SMS sends quicker now. Using 3/10. Going to try latest and see if that helped.

---------- Post added at 08:51 PM ---------- Previous post was at 08:22 PM ----------

Updated to 03/22 and everything seems to be working better. I did notice the batter is running hotter though. Maybe it has to do with 3.4. I will keep it and see if it ends up acting weird again.
[Verizon Samsung Galaxy S III] Stealth111:
I blew back to 4.0.4. Then OTA to 4.1.2. Phone number wipe. Root. Recovery. Full wipe, clean install 3/20 Official nightly 10.1, dirty flash to 3/21 Official nightly. Things seem actually pretty good. SMS sends almost instantly for me on stock app. Overall experience seems a small bit off in various ways. I attribute that to new kernel work. No freezes, pretty decent battery life so far.

Sent using Tapatalk
[Verizon Samsung Galaxy S III] mastamoon:
@ 38 hours, no longpress button issue.
[Verizon Samsung Galaxy S III] wrippel82:
Is your phone not randomly rebooting?? Every since the 20th Every new official and unofficial give me random reboots..
[Verizon Samsung Galaxy S III] NegativeOne:
It's good to see this thread pick up again, but I'm kind of confused. There are people having random issues due to bad flashes and configuration, but....

What are the global issues?

Activation lock,what else? I can't tell if this was cleared up or not.
[Verizon Samsung Galaxy S III] mastamoon:
Hasn't so far.. :knock on wood:
[Verizon Samsung Galaxy S III] V3TTOO:
Just an update, I am running very well with no issues so far. It froze once, but so far no other issues. That last wipe helped a ton.
[Verizon Samsung Galaxy S III] Stealth111:
Same thing I just said as I walked out of the bathroom! :D.

JK
[Verizon Samsung Galaxy S III] mastamoon:
45+ hours.. No longpress button issue yet.
[Verizon Samsung Galaxy S III] enomele:
I've been having major freezing/rebooting issues as well. Even after full wipe and starting fresh.
[Verizon Samsung Galaxy S III] :
Same here. Currently using the Trinity kernel to see if that helps but have had a lockup already.
[Verizon Samsung Galaxy S III] razorloves:
just tried both of these and several other variations and still get the activation bug/switching to NV. damnit. lol. just providing feedback
[Verizon Samsung Galaxy S III] mastamoon:
Well after 50 hours of uptime, I finally got the long press bug. Meh.
[Verizon Samsung Galaxy S III] razorloves:
love the MMS recipient selector. thanks for snagging that one mastamoon
[Verizon Samsung Galaxy S III] iofthestorm:
Basically kernel 3.4 got merged into the nightlies and it has had a random reboot bug that hasn't been figured out.
[Verizon Samsung Galaxy S III] Stealth111:
Yeah, I had it happen once today. I was testing a theme issue for a dev, and was rebooting quite a bit. I haven't seen it since the clean boot of the phone and the dirty flash as discussed. However today I unintentionally left my wireless on while testing, during a reboot. What do you know, my old friend NV shows its face again. Damn it all to hell. I really think the NO SIM CARD notice when I have the error is some indication of something. It seems SO much like a timing issue of sorts. I turned off wireless and rebooted and all was well again, even through another series of reboots. I did try enabling wireless and rebooting again later in the day, and it did not happen, so it does not seem like a static change.

Just my 2 cents...
[Verizon Samsung Galaxy S III] Chris123NT:
Just had a hard lock, phone wouldn't come on when i went to wake it, but i was able to hard reset so I know it was still on. This kernel definitely needs some work, that's for sure lol.
[Verizon Samsung Galaxy S III] Stealth111:
Maybe some good news coming related to our kernel woes!

http://xdaforums.com/showthread.php?p=39496289

Sent using Tapatalk
[Verizon Samsung Galaxy S III] Chris123NT:
Anyone see the list of commits for the next nightly? Masta's afternoonly today should be pretty good, especially with the updated kernel stuff from this weekend.

Masta I imagine you're going to put the longpress fix back in?
[Verizon Samsung Galaxy S III] mastamoon:
I sure will! :good:
[Verizon Samsung Galaxy S III] Reborn627:
OK, Saturday I ran into about the same battery usage as I did on friday, about 21 hours of minimal use. Minimal use for me is a few text messages, a call or to and some email checking. Pretty limited use. Sunday was a bit different for some reason. No calls, some texting and about the same amount of email checking and I only got about 11 hours out of a full charge. It appeared as though Maps was the power hog which seems to be the new norm, for now, with the new kernel. My hope is that the updates that rolled down over the weekend on the official build, merged with Masta's great work, will bring the battery life back to a more acceptable place. I had been fortunate in that my only issue with the builds from the last week are battery issues. I never got any lockups or reboots or anything like that. I have to wonder if my limited use of phone is part of that. I don't actually use the phone as a phone very much. in a week I probably make and receive 15 calls. This may be the reason I'm not seeing many of the problems that others are. I have rolled back to the 3/12 build simply for the better battery life. I'm looking forward to the next update.

Peace,

Ray
[Verizon Samsung Galaxy S III] mastamoon:
3.5 hrs of screen on time for me. A new record on AOSP.
[Verizon Samsung Galaxy S III] Chris123NT:
I think I pinpointed my battery drain to a wlan_rx_wake wakelock which oddly enough only happens when connected to my dlink router at the one side of my house. A little googling revealed it's a known issue with the DIR-655 and android phones, and connecting to my netgear router seems to clear it up but I'll monitor it over the next day or two.
[Verizon Samsung Galaxy S III] Reborn627:
WOW! Well it certainly appears that battery drain issues in the latest updates have minimized the issue. That's terrific!

Ray
[Verizon Samsung Galaxy S III] NegativeOne:
Honestly still a little depressing. One of the ONLY reasons I'd considered going to iOS is for the screen time. Less than 4 hrs is a joke! But still good.

Masta, are you putting out a build today? If so i'll wait to flash
[Verizon Samsung Galaxy S III] V3TTOO:
So, update here. I have been on 3/21 and so far I have had a few screen lock issues. 3 times the phone has locked up. 2 while screen was on and stayed on, and one with screen off and will not come back on as well as any of the other buttons. Only thing that would work was the notification light. Just did a hard reset and that fixed it. Besides that, battery has been great and BT crackles a little here and there, especially while using the phone.
[Verizon Samsung Galaxy S III] mastamoon:
Yes, obviously I would love more screen on time.. but generally I get about 2hrs before needing to charge. 3.5hrs is amazing for a 'buggy' rom. I also got 50+ hours of uptime before I rebooted only due to wanting to kill the longpress bug.

Yes, ill be building around 3pm or so. Unless this snow forces us out of work early today :P
[Verizon Samsung Galaxy S III] Chris123NT:
Is anyone else seeing a sec-battery-monitor wakelock? Just spotted this and apparently it's the other reason for my battery drain. I got rid of wlan_rx_wake so this is the last one I'm trying to pin down.
[Verizon Samsung Galaxy S III] mastamoon:
Do you use anything else to monitor your battery.. like a widget?

I would guess its something that is constantly polling for battery info. Either a battery widget(or a widget that can track/display battery use) or whatever program you are using to track wake locks, BetterBatteryStats?
[Verizon Samsung Galaxy S III] Chris123NT:
Yeah I use BetterBatteryStats but I'm not using the widget. Could just having it installed be doing it?
[Verizon Samsung Galaxy S III] mastamoon:
I would think so. Its running in the background collecting battery stats.. telling you what percentage of battery loss each service has so I would say its constantly polling your battery stats. Its not so much the widget that is important here. I was asking about a widget only because some people run a clock/battery/system stats kinda widget that would show battery life, so I mentioned it.

Ive always kept it uninstalled/frozen till I see something weird with my battery.
[Verizon Samsung Galaxy S III] odub303:
BBS is written in a very battery friendly way. Unless you have active monitoring enabled, I would look elsewhere for causes of drain.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] mastamoon:
3/25 build in OP

- no more GTOD revert, caused long press issue to come back.

- Optimized boot animation was merged, uncherry picked.

- repo sync @ 3pm EST
[Verizon Samsung Galaxy S III] Restola:
How's it running with that huge list of changes?

Tapatalk via CM10.1 Galaxy S3
[Verizon Samsung Galaxy S III] mastamoon:
Still have some lag/stutter when opening/closing apps. Everything else seems ok so far. Only booted for about an hour.
[Verizon Samsung Galaxy S III] PerCompLLC:
Just had a freeze during a call. Had to do a hard reset. :(
[Verizon Samsung Galaxy S III] ctsail410:
Yeah, I had a freeze while playing music over Bluetooth. Battery life was better while it lasted. My phone never seemed to deep sleep before the most recent batch of patches.
[Verizon Samsung Galaxy S III] alee:
Anyone else having problems getting Google Wallet working with the last 2 builds here? Can't get it to log into my account.
[Verizon Samsung Galaxy S III] Reborn627:
Hmm, 30 minute drive home from work using iheartradio through via bluetooth in my fiesta with no troubles. Somehow I've been able to avoid the lockup problems.
[Verizon Samsung Galaxy S III] Hybridnoob:
I'm on the latest nightly and have had a lockup on the stock kernel. The lockups made me want to venture out into kernel land. Never messed with other kernels before, so it's a new adventure for me. Here's what I've discovered thus far - On LeanKernel v5.02, I experienced a couple of lockups and terrible battery life (6-7hrs!!) with the 3/21 build, but it was really smooth. I may try LK again later, as I like that it can be updated from Terminal Emulator. The KT747 kernel is working pretty well on 3/21 and on the latest thus far. The stock kernel is really smooth most of the time for me, but seems less stable than some other choices at the moment. One thing is for sure, Masta's builds are solid!

I'll post an update if anyone's interested.
[Verizon Samsung Galaxy S III] Chris123NT:
Hmm that's weird, I'm on LK 5.02 and I haven't had any crazy battery drain. I did have a wlan wakelock but that was my router being stupid. What governor are you using on LK? I'm using interactiveX which is treating me well so far.
[Verizon Samsung Galaxy S III] betam4x:
Haven't dared tried updating from unofficial 3/13. Most stable build of CM I have ever used. Better battery life than stock as well.
[Verizon Samsung Galaxy S III] Hybridnoob:
I was using Interactivex too. I had 10 hours of battery life the first day on LK with about 3 hours screen time (not bad). The second day I definitely had a wake lock of some sort, as I had less than an hour of screen time... Anyways, just sharing my experience in case anyone else is looking to try and make this new kernel more usable on CM10.1. None of them are perfect yet...
[Verizon Samsung Galaxy S III] imtoomuch:
Does the Bluetooth audio work for you?

I am using the 3/13 build and the Bluetooth audio stutters and goes in an out when connected to the UVO system on my Kia Soul. The stock ROM worked fine with UVO. Also, the Bluetooth will not connect to my Samsung Chromebook. Otherwise, I love the ROM and the battery life seems to be great so far. Any ideas on the Bluetooth? Thank you.