yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] RED ZMAN:
so is there any movement or a bug tracker thread that I can monitor to see anything happening with his bluetooth bug?

it seems to be the last issue that I've got with this wrong at all. Happens on the stock kernel and lean kernel.

you just gets kind of frustrating having to force close Bluetooth share ttwo to three times to get Bluetooth to connect while driving, what's once or twice a day.

Blasted from my Samsung Galaxy SIII (CM10.1 Masta Mix).
[Verizon Samsung Galaxy S III] Reborn627:
Sorry man, I connect to Bluetooth in my car every day and haven't experienced any issues like you describe. I'm running the BMS kernel from GideonX. I'm not sure Bluetooth is handled by the kernel so that shouldn't matter. Is it for audio playback? If so what music player, streaming or local? Could be an app issue I suppose.

Ray
[Verizon Samsung Galaxy S III] halling:
0 dBm?

Hi!

This weeks builds have been given me 0 bars and 0dBm also in the menu and I wonder if this is a known issue?

I seem to be able to surf and text message anyway but it's annoying.

Do I need to do a full clean and re-install cm10.1?
[Verizon Samsung Galaxy S III] goldsmitht:
have you tried clearing cache/dalvik and fixing permissions?

might work, saves on a clean flash
[Verizon Samsung Galaxy S III] mastamoon:
new build in the OP

-- lots of old cherry picks left out - need rebasing mostly.

-- adreno blobs in

-- repo sync 830 am
[Verizon Samsung Galaxy S III] goldsmitht:
getting an early start today?

by the way, on last build i've been having a hard time sending SMS. NOT sure if it is ROM or VZW, but seem to have a lot of bars of 4G, so...

will load current build up and see what problem is. Hopefully i didn't delete previous nandroid :confused:

edit: seems like it may be VZW related; had steady 3-4 bars of 4G, but now that i rebooted, cleared cache and dalvik AND fixed permissions, seems i have barely any bars 3G and that is in and out.

Bad VZW... :p

edit 2: seems it wasn't VZW, but rather a bad reaction from my phone to LK 4.5.2exp1. Switched to LK 4.5.2 and all is fine now, so not sure why my phone didn't like the current expermimental, has liked all the rest. :confused:
[Verizon Samsung Galaxy S III] mastamoon:
Lol, yeah I didn't know if I would be able to do a build later so snuck one in this morning. ctsail410 figured out a the exact reverts needed to build vs the axe we took at it for yesterdays build.

I haven't noticed any signal issues myself. Ill keep an eye on it when I can.
[Verizon Samsung Galaxy S III] Hybridnoob:
I'm getting a different MD5. Anyone else? Just want to make sure I didn't get a bad download before I flash...
[Verizon Samsung Galaxy S III] jlokos:
I have been using LK and I haven't had any BT issues either.
[Verizon Samsung Galaxy S III] mastamoon:
Crap, could have missed copy/pasted. I'll try n check it out soon.
[Verizon Samsung Galaxy S III] mastamoon:
The md5 shown matches the calculation done on my phone. Flashed fine.
[Verizon Samsung Galaxy S III] Hybridnoob:
I'm glad I didn't flash then! I guess it was a bad download. Sorry to have you double check it...
[Verizon Samsung Galaxy S III] RED ZMAN:
I'm just using mine for the phone, I have a in dash Samsung Galaxy Tab for all my music and such.

It's the same old BT hangup problem we were having for quite some time, others get it too. Basically, after the phone has been on for awhile, a few hours lets say, you toggle BT and it turns on, but doesn't actually connect to anything. You have to go in and force stop Bluetooth Share, then it'll turn on. With the last couple of versions I've been on, I've had to do this a few times. For example, last night on my drive home, I had to force stop it 3 times to finally get it to connect. Someone else said they were still having this issue a few pages ago.

I'm using the 4/12 build and Lean Kernel of 09 April.

Since you 2 are not having this issue, how do you flash usually, or did you clean flash the most recent? I usually just wipe dalvik cache and cache before install.
[Verizon Samsung Galaxy S III] mastamoon:
No problem, I jsut downloaded it on my PC from the ftp site and checked the MD5 again. The number in the post matches the original file on the build box and both copies of the file downloaded from the ftp site.

:good: Better safe than sorry.
[Verizon Samsung Galaxy S III] Hybridnoob:
I'll download again when I get back home and on WiFi. Thanks again for checking!
[Verizon Samsung Galaxy S III] wrippel82:
Am I really the only one that gets random reboots no matter how many times I wipe? it's been like this on EVERY single nightly that I have tried since 3.4 Kernel was merged in. My Backup/current daily is the official M2 with the stock kernel (3.X) and all is well. just curious. I have even tried KT 3.4 and LK 3.4 and BMS with the current nighties with a fresh install and still get the random reboots. just looking for everyone else's input as I am currently frustrated. Maybe i'm missing something =/
[Verizon Samsung Galaxy S III] mastamoon:
have you posted a last_kmesg for us to look at? Download SysLog from the market. After a random reboot, open the app, check Last Kernel Log and push the file to somewhere we can look. If you have done this already, can you repost?
[Verizon Samsung Galaxy S III] jlokos:
I generally wipe only cache and dalvik before flashing. sorry I can't help any further.
[Verizon Samsung Galaxy S III] wrippel82:
No i haven't done this yet, I will do that now. Thanks!
[Verizon Samsung Galaxy S III] wrippel82:
Ok, here it is.. also seems that after reboot my phone number vanishes.. i was running the the unofficial 4-16 with the stock kernel. thanks!
[Verizon Samsung Galaxy S III] mastamoon:
Here is a test build wrippel82 and whoever. This build has the android_ram_console turned off. Not sure if its a fix or not for a random reboot, but want to rule it out. So wrippel82, please install this & wipe caches and let us know if you have another random reboot.

http://bit.ly/Z3SJQx

If anybody else wants to run this it should be fine. Repo sync as of 3:30pm EST so a bit newer than the one I posted this morning. Nothing major merged though.

** Note: turning the ram_console off will mean no last_kmsg will be generated. So dont go looking for it if you run this build and have a reboot. Just let us know.
[Verizon Samsung Galaxy S III] wrippel82:
getting it right now, thanks! ill get right back.
[Verizon Samsung Galaxy S III] wrippel82:
same, reboots every 2-3 minutes... even if let to sit with the screen off. heres the log.
[Verizon Samsung Galaxy S III] mastamoon:
Hmm.. That's a last_kmsg alright. I thought one wouldn't be generated if I disabled the ram console. Maybe what I did didn't work.

Will try again tomorrow.

If you want, go into the IRC channel and see if anybody is feeling up to troubleshooting with you. No promises though.

1-2 reboots an hour is crazy. Have you done at clean install yet?
[Verizon Samsung Galaxy S III] wrippel82:
Not with this build you posted. I just dirty flashed and cleared cach/dev.. I'll try the clean install now. Thanks for looking at it.
[Verizon Samsung Galaxy S III] goldsmitht:
How do you get to the IRC channel?
[Verizon Samsung Galaxy S III] mastamoon:
Turns out my test build yesterday was just a normal build lol. Edited the right file, but in the wrong location. New build compiling now.

You can either http://webchat.freenode.net/ and join #verizons3 or you can download a real IRC client to your phone/pc, connect to freenode and join #verizons3
[Verizon Samsung Galaxy S III] wrippel82:
Awesome! I'll check it out when you post it. Thanks!
[Verizon Samsung Galaxy S III] Hybridnoob:
I'm guessing there were problems :-\
[Verizon Samsung Galaxy S III] mastamoon:
Yeah ran into a few issues but I got it to build finally.

Here are 2 kernels to test for you guys with the bad reboots.

Kernel 1 - http://truelinux.net/sch-i535/mastamoon/Kernels/mastamoon-test1.zip - This one reverts this (https://github.com/CyanogenMod/andr...2e5495ac76a0#arch/arm/mach-msm/board-m2_vzw.c) - Memory Allocation Location

Kernel 2 - http://truelinux.net/sch-i535/mastamoon/Kernels/mastamoon-test2.zip - This one disables the ram_console

Try kernel 1 first, if you have a reboot, try kernel 2.

Thanks!
[Verizon Samsung Galaxy S III] Hybridnoob:
Thanks! Test with 4/17 build?
[Verizon Samsung Galaxy S III] mastamoon:
yeah thats fine. Just cant use them on official as its built with the newer adreno blobs in mind.
[Verizon Samsung Galaxy S III] Hybridnoob:
Ok, cool. Didn't know if you had a newer build coming to test against.
[Verizon Samsung Galaxy S III] wrippel82:
random reboots every 5 minutes with test 1... heres the log. I should have noted that it was a dirty flash.. just cach/dev and permissions fixed.
[Verizon Samsung Galaxy S III] d1ez3:
Quick question not directly related to the unofficial build, but I installed a wallet installer which edited my build prop, and my phone thinks (says) it is a galaxy nexus, and I lost my recovery ability when I tried to update it.

Can anyone tell me exactly what the phone says in settings>about phone>Model Number? so I can edit my build prop back to normal.

thanks!
[Verizon Samsung Galaxy S III] mastamoon:
SCH-I535
[Verizon Samsung Galaxy S III] slambert27:
SCH-I535
[Verizon Samsung Galaxy S III] mastamoon:
4/18 build in the OP

-- Emoji Button is back.

-- repo sync at 3:30pm
[Verizon Samsung Galaxy S III] invisiblek:
I was wondering if anyone was going to mention anything....

http://xdaforums.com/showpost.php?p=36855847&postcount=999

also - i'm not exactly thrilled about two separate cm10.1 threads, its just messy

these test builds imo still belong in the official thread since that's exactly what development is for
[Verizon Samsung Galaxy S III] NegativeOne:
invisible, it may be the case that they exhibit different problems than the official;I think it would be confusing to merge them :(
[Verizon Samsung Galaxy S III] PerCompLLC:
invisiblek, I don't disagree with you. But I think the mods kind of put the fear of God into folks on the "official" thread, and so many people were complaining that mastamoon's builds weren't "official" (in typical XDA fashion) so they shouldn't be listed, hence the reason this one was created (again, just my assumption). That said, you have really provided a lot for this device and CM, and you obviously know what the hell you are doing, so I tend to side with you... :good:
[Verizon Samsung Galaxy S III] invisiblek:
Right but now I need to come here to see if my patches affect anything when that's the point of a development thread such as the official one.

TBH: if this thread is going to exist, it doesn't belong in original development anyway, nothing original is being done here.

Glad to hear data is working better though
[Verizon Samsung Galaxy S III] mastamoon:
Listen, I don't care where the builds I do go. We moved them out of official because people were butthurt that they weren't "official".. we move them into an 'unofficial' and people are still butthurt.

Again, I don't care where they go. If a MOD tells me to put them in the official, ill put them back there. Want me to make a thread in the non-original development section, ill do that. Would it be better if I gave it a fancy name to hide the kang like other 99% CM roms?

:eek:
[Verizon Samsung Galaxy S III] k1ska:
I quite like the name Mastakang! :D
[Verizon Samsung Galaxy S III] Restola:
Ah forum politik fun :)

Thanks masta and invis for your work. Whatever helps you guys works for all of us I think.

Tapatalk via CM10.1 Galaxy S3
[Verizon Samsung Galaxy S III] yznhmr:
Still not able to send pics via text..I can receive them.. any help?

I did a clear data on both GO SMS and in the stock messaging..

Please help..

I am now on 1/17.. but have had this prob for a couple weeks..
[Verizon Samsung Galaxy S III] mastamoon:
What baseband/modem are you using?

System Settings > About Phone > Baseband Version
[Verizon Samsung Galaxy S III] bdanders:
Bluetooth

I'm still having a problem with Bluetooth freezing up at "Turning Bluetooth off..." after cycling on and off a couple of times. Is this an issue that's getting any attention?
[Verizon Samsung Galaxy S III] odub303:
Yes it is. For now you can resolve by force closing Bluetooth Share.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] yznhmr:
K3

Also getting reports of high feedback when using the handset to talk (not speaker)
[Verizon Samsung Galaxy S III] dpaine88:
My hand offs are much better on 1-17.

Not quite on the level of touchwiz but close
[Verizon Samsung Galaxy S III] mastamoon:
Did you restore data to keep your SMS/MMS between flashing roms?

Honestly I would do a backup, factory reset, and do a selective restore and NOT touch SMS/MMS in your case.
[Verizon Samsung Galaxy S III] PerCompLLC:
Or use an app like SMS Backup (free in the playstore) to backup and restore SMS/MMS as it only backs up and restores messages and nothing else.
[Verizon Samsung Galaxy S III] travisX:
Masta, you're the gd man.

Hand offs seem to be much improved on the 1-17 build! I flashed from the 1-14 build, if I remember correctly.

Thanks for everything you do!
[Verizon Samsung Galaxy S III] bobby janow:
Mine are actually better. I'm getting data where I had none also. Was a couple of months ago but still. Nice to have you back dpaine ;)
[Verizon Samsung Galaxy S III] wakeslayer:
I am running your unofficial 1-14 build, and when I press home button from anywhere it only shows me previews I want it to take me home. Any ideas? I also have Nova Prime but I have it set for home button to take me home.
[Verizon Samsung Galaxy S III] gJon:
This is a known issue with CM. A reboot should fix it.
[Verizon Samsung Galaxy S III] yznhmr:
ok Ill try this.,.
[Verizon Samsung Galaxy S III] s'pht:
Hey Masta any chance you can try http://review.cyanogenmod.org/#/c/36007/

pulled from http://xdaforums.com/showpost.php?p=40422790&postcount=1385
[Verizon Samsung Galaxy S III] mastamoon:
Yeah ill include that tomorrow if it's not merged.
[Verizon Samsung Galaxy S III] rampantandroid:
Any word on how often it reboots? Will either leankernel or KT fix the reboots?

Thanks!
[Verizon Samsung Galaxy S III] mastamoon:
I set the random reboot flag to on so I can't tell ya. :p

Try the test 2 kernel from few posts up. May or may not help, looking for feedback.
[Verizon Samsung Galaxy S III] jsaxon2:
I tried the test 1 kernel but rebooted after about 5 minutes. I then installed the test 2 kernel and haven't had a problem yet. Been only about 2 hours but still better than 5 minutes.
[Verizon Samsung Galaxy S III] goldsmitht:
I'm running tonights regular, with LK 5.4.2 and NO issues at all
[Verizon Samsung Galaxy S III] dpaine88:
Got a reboot 30 min after flashing latest build
[Verizon Samsung Galaxy S III] jsaxon2:
Flash the test 2 kernel, seams to be working for me.
[Verizon Samsung Galaxy S III] WhammyDroid:
Running 4/18 build with 4/11 KT kernel. No random rebooting.
[Verizon Samsung Galaxy S III] biyobe:
I've tried this, get the 1st boot up following to hold the RUIM/SIM and then next reboot right back to the activation screen issue... man was hoping this thing gets fixed. I've been clear from the activiation bug up until yesterday. argh!!
[Verizon Samsung Galaxy S III] ausman89:
Try this:

Reboot into recovery and wipe both caches (cache and dalvik) and then flash the LHE modem and rpm and reboot.

Doing that has both worked for me and razorloves.

LHE Modem: http://truelinux.net/sch-i535/modems/VRLHE.modem.zip

LHE RPM: http://www.invisiblek.org/sch-i535/rpm/VRALHE.rpm.zip
[Verizon Samsung Galaxy S III] airmaxx23:
I had to do a lot messing around with this to get it stop for me. There is something in the OP involving removing the SIM and changing the CDMA setting that worked for me along with clearing cache/dalvik.
[Verizon Samsung Galaxy S III] biyobe:
but does the activation come back on reboots or different ROM flashes? Trying to find a way to not have to continually "fix" it. Weird thing is i have data and voice coverage, just doesn't want to hold the correct network settings.

---------- Post added at 11:10 AM ---------- Previous post was at 11:08 AM ----------

ya tried those couple options and no luck. trying to get the files downloaded to go back to stock/rooted and then back to JB and hopefuly that will fully fix me... that posting in the OP shows if you don't have data, which i'm fully functional, just get that activating screen on every reboot and my phone number shows as 000-000-5124. On fresh ROM installs it shows the correct ## and works fine w/o the activation screen.. only on reboots
[Verizon Samsung Galaxy S III] goldsmitht:
this will sound dumb, but after you fix it and boot once, and it right, try making a nandroid of that fixed version, and THEN don't reboot system, restore fixed version.

there is something in the boot sequence that isn't allowing the ROM to maintain the correct settings. MAY fix it if you just boot the corrected version.

but then, ymmv. hope this works, and is way easier than going back to stock.

:cyclops:
[Verizon Samsung Galaxy S III] ausman89:
so far it has been a continual fix, and I feel good that it will stay "fixed". I've went through multiple reboots with no issues. I don't remember if I have flashed another rom yet, but i think ravorloves has.

also, i didnt try it yet, but razorloves said that if he tries to flash back to the BMB1 modem, it breaks things on every reboot, so there is a good chance that the LHE version just plays nicer.
[Verizon Samsung Galaxy S III] biyobe:
so i could then just install the new ROM, it boots up fine with everything "working", go back into TWRP, nandroid backup, nandroid restore THEN reboot and cross fingers?? :highfive:
[Verizon Samsung Galaxy S III] goldsmitht:
good luck! and do NOT know why this is. I had the problem installing a couple of different ROMs (All CM based) but recently installed Chameleon and nada, zip, nothing, praise the lord and pass the potatos... no activation bug or nothing. do not know why.

just know that when i tried this the first time, it worked. afterward, do NOT do a clean flash on any ightly, and it should keep. Has for me.

and i'm on MB1, have been, so not sure that is the issue. :confused:
[Verizon Samsung Galaxy S III] biyobe:
nope... that didn't work, argh ;)
[Verizon Samsung Galaxy S III] airmaxx23:
I had a data connection as well but the fixes in the OP got rid of the activation screen for me. I fixed permissions and clear cache/dalvik as well.
[Verizon Samsung Galaxy S III] razorloves:
as ausman89 has said above, yeah it's a continual fix. I've rebooted dozens of times and flashed numerous nightlies and it stays fixed. Just try it and see. Might work for you like it has worked for others. If it doesn't work you can flash right back to your current rpm and modem. No harm done.

Before you boot into recovery to do it, just make sure you fix the setting and be sure that your number is showing in About phone-Status
[Verizon Samsung Galaxy S III] mastamoon:
http://bit.ly/XLT4Gt

Here is the 4/19 build.

-- new wifi drivers from the s4 source that dropped today

-- cherry pick mentioned above to fix audio issues playing music in mortplayer

-- repo sync @ 6:45 pm EST
[Verizon Samsung Galaxy S III] goldsmitht:
WiFi drivers, as in connecting to WiFi, or WiFi tethering.

:D: thumbup:
[Verizon Samsung Galaxy S III] biyobe:
Damn... just went through all of this and still getting the activation issue... ugh!!

Originally Posted by Deevious88

Hallelujah! My phone has voice AND data back! (thanks to the posters above)

How to get voice AND data back:

1.) Odin the root66.tar file from http://xdaforums.com/show....php?t=1762204 (the torrent version downloads MUCH faster)

2.) Open the dialer and enter *2767*3855#

3.) DONE! Voice and data should be fixed (it fixed it for me at least, and I had tried EVERYTHING else)

From there just Odin back to Jellybean following http://xdaforums.com/show....php?t=1974114 and you're golden...
[Verizon Samsung Galaxy S III] mastamoon:
I believe they are one in the same.
[Verizon Samsung Galaxy S III] airmaxx23:
Everything is working nicely, thanks for the build.
[Verizon Samsung Galaxy S III] kentedman:
Once you get wallet installed and setup just use the wallet installer app to rebuild your buildprop. Wallet will still run.

Sent using xda app-developers app
[Verizon Samsung Galaxy S III] razorloves:
That's not a fix for the activation issue. Just the rom reflash and lhe modem are, from what people have reported
[Verizon Samsung Galaxy S III] WhammyDroid:
FYI: I could not get the 4/19 KT kernel to boot with the 4/19 build by masta. For now, only the stock kernel will boot.
[Verizon Samsung Galaxy S III] RED ZMAN:
Will Lean Kernel work with it?

I think I'm going to completely wipe my phone today and install the latest version, I've got to get rid of this Bluetooth bug. It's really starting to p*** me off.

Hey Masta, any chance that the Bluetooth drivers from the s4 will work on ours? Lol

Blasted from my Samsung Galaxy SIII (CM10.1 Masta Mix).
[Verizon Samsung Galaxy S III] goldsmitht:
Got Moon's 4/19 working great with LK5.4.2; no issues at all
[Verizon Samsung Galaxy S III] mastamoon:
I believe invisiblek might have been checking that out yesterday. I saw some mention of it in IRC. Nothing in Gerrit yet.

About kernels not working. There are a few kernel reverts needed to build/boot with the newer adreno blobs. If your kernel builder of choice is syncing with cm, their kernels at some point will fail to work with this build going forward.
[Verizon Samsung Galaxy S III] WhammyDroid:
Masta, then how do we get the GPS commit addressed? That commit is the only reason why I am running this build. If it would get addressed by CM, I would happily move back to the official release. Would invisiblek be willing to ifdef that?

I wish I could do it however I am not a programmer by any means. My best programming is writing SQL statements.
[Verizon Samsung Galaxy S III] mastamoon:
It's on the list of things to do. Run stock kernel lol
[Verizon Samsung Galaxy S III] Hybridnoob:
4/11 KT kernel still works though (if you don't want to run stock)
[Verizon Samsung Galaxy S III] WhammyDroid:
Are the wifi drivers in the kernel or in the ROM? I thought it was in the kernel. If true, I would be reverting that commit by running the 4/11 kernel.
[Verizon Samsung Galaxy S III] mastamoon:
Yes they are (in the kernel) .
[Verizon Samsung Galaxy S III] mastamoon:
4/20 <//////////#~ build in the OP

-- emoji button commit got merged

-- repo sync at 1:30pm EST
[Verizon Samsung Galaxy S III] odub303:
Also a number of kernel commits, including a change to the row scheduler that will have the effect of speeding up the boot process :).

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] Reborn627:
Fresh, clean flash of 4/19 build with the stock kernel running perfectly. Cleared system, data & caches and its running fantastic! Not a single hickup yet. Gonna run it for a couple of days before flashing an update to put it through a charge cycle or two. Thanks Mastamoon, your hard work is appreciated.

Peace,

Ray
[Verizon Samsung Galaxy S III] loldi:
I have a (possibly stupid) question: will the nightlies compiled AFTER 3/13 -- ones with 3.4 kernel -- not work with a 3.0 based version of another kernel? I'm running 3/13 right now with the last 3.0 KT747 kernel and it's running beautifully. However, I got significantly worse battery life/performance when upgrading to the 4/10 (last time I tried it) build with a 3.4 version of KT747.
[Verizon Samsung Galaxy S III] odub303:
They will not work. If you want to run the older kernel, that is the latest build you can run.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] s'pht:
The audio changes are working great, on 4/20 mort functions perfectly.