yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Gatanater:
I believe it is supposed to be striped because I have the same and it kind of fits with the theme :cool:
[Verizon Samsung Galaxy S III] Kev13Dd:
Mine has always had the diagonal lines too. Have been running stock CM10/10.1 for months and always had lines

If you look at reviews of 4.2.2, they show diagonals on the dialer. So that's what stock Android has

http://www.androidpolice.com/2013/0...ely-tiny-changes-and-an-androidhome-sighting/

K
[Verizon Samsung Galaxy S III] mastamoon:
Sorry guys, no build from me today. Had some actual work to do at work! :screwy: :banghead:
[Verizon Samsung Galaxy S III] jmaeishi:
tearing and dev tool

Hi, I'm not sure if this is specific to this unoffic but guessing so.

I had problems with both 3/15 aft and 3/18 with tearing. This may not be the correct term but the screen...well it tears, all the way through. It got progressively worse through use over a few hours.

In the past, I've only seen this effect in recovery.

So, I think it must be rom since now it appears in rom (not in recovery).

Also, the tool i had in dev under system is gone or relocated.

I had a 12.12 build on 10.0 rom and that had way to stop process, limit processes.

It is relocated?

Thank you.
[Verizon Samsung Galaxy S III] mastamoon:
http://review.cyanogenmod.org/#/c/32212/

Volume fix?
[Verizon Samsung Galaxy S III] odub303:
I smell cherry pick :)

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] mastamoon:
I bet its merged by morning :) , if not... fo'sho.
[Verizon Samsung Galaxy S III] ctsail410:
Yep it worked great for me when I picked the five related frameworks_av commits. Definitely include them if they're not merged in the AM!
[Verizon Samsung Galaxy S III] mpetruzz:
Sweet!! The volume bug was killing me!! I stream music while at work and the past few days have been rough.

sent from my blue police box flying through time!!!
[Verizon Samsung Galaxy S III] ctsail410:
If anyone is desperate for the audio fix and can't wait until masta's build tomorrow, I uploaded a build here: http://d-h.st/7lu

Repo sync'd around 5:30 EST. Same basic cherry-picks and reverts as his last nightly, except for battery bar. Oh, and it's built with Linaro. Seems to be running fine for me with daily builds over the past couple weeks, but I make no promises. I also don't really see much of an improvement, but I'm probably not as much of a power user as some of you guys.
[Verizon Samsung Galaxy S III] masri1987:
What's this volume fix about exactly, call volume or bt?
[Verizon Samsung Galaxy S III] rampantandroid:
He's referring to this issue:
[Verizon Samsung Galaxy S III] aatrek:
Is there a recommended radio for use with masta's build? I switched over on Monday and I've been getting pretty poor reception ever since... but I'm not sure if it's the phone or the local tower coverage.

Here's what I'm running now:
[Verizon Samsung Galaxy S III] PerCompLLC:
It is really a matter of personal preference. (FYI, 8 different radios have been made available since the one you are running in the submitted screenshot). I think that Masta is on the latest, as am I (VRBMA2). I tend to move to the latest whenever it becomes available based on the assumption that improvements have been made - hence a new radio has been released. That said, my recommendation is to start with the latest available, test it out, and then move backwards one by one until you find the radio that works best for you.

Fyi, all the radios have been consolidated in the following thread as flashable zips (thank you invisiblek!). http://rootzwiki.com/topic/34053-modems-vrbma2-verizon-sgs3-sch-i535-recovery-flashable/
[Verizon Samsung Galaxy S III] aatrek:
That's awesome - just what I was looking for. Thanks!
[Verizon Samsung Galaxy S III] ViperRacer:
I think I narrowed down my BT problem that I have been experiencing. I use a TuneLink adapter for my car to utilize Bluetooth Audio streaming. On a previous version of Masta's builds (0122 was my fall back version) streaming on all A2DP devices worked fine. Clear audio, strong bass, no choppy sound. Some time after those builds, when the reverts were no longer applied, my audio when connected to the TuneLink seemed to have a velocity drop of 10%-30% in sound resulting if slower, lower sound pitches and skips and craks as the device would attempt to 'catch up'. I confirmed that on the 0218 build that my TuneLink device connection is still having issues while connecting to a Panosonic Clock Radio via A2DP works perfectly. Any ideas why the two would react differently? Is there settings I can adjust in flat files that could help this, or should I report it over on the CM side of things? Any help is greatly appreciated.

Edit: I also was hopeful that the new builds would clear up the home key issues (between 24-48 hrs the buttons all react as if they are long pressed), but alas the 0218 build just started doing it on me after 36hrs uptime, so I've fallen back to the 0122 version.
[Verizon Samsung Galaxy S III] NegativeOne:
supported codecs /different sample rates?
[Verizon Samsung Galaxy S III] yznhmr:
Not able to send pictures via text.. on Mastas 18 and maybe on 15 also. any fix, or thoughts? already cleared cleared data in messaging
[Verizon Samsung Galaxy S III] mastamoon:
Are you sending multiple pictures in a single MMS (if thats even possible) or adding a long message or sound with the picture?
[Verizon Samsung Galaxy S III] jackpot08:
I had this problem I did a clean install and flashed a new modem and it fixed. Wipe cache, system, factory reset, dalvik
[Verizon Samsung Galaxy S III] pinhead875:
When pressing home, I'm getting recent apps. Is that a CM bug? I use long press for recent apps, I want to keep it. But it's happening on single press. Can't go home! :p
[Verizon Samsung Galaxy S III] s'pht:
It's a known problem with CM 10.1 hard buttons get repeat-y after a while. If you try some of the other ones you'll notice a single press on the menu will act like you're holding it down too. The only fix I know of is to reboot though in my experience it sometimes goes away on its own; but you want to reboot anyway - I can tell.
[Verizon Samsung Galaxy S III] Recon0212:
Restart your phone. I had the same issue and a restart fixed it.
[Verizon Samsung Galaxy S III] Masterfisto:
I have this same issue sometimes to. The buttons will just go haywire and only a restart will fix things.

Sent from my Cm10.1 Galaxy S3
[Verizon Samsung Galaxy S III] RedRumy3:
That happens to me as well. I usually reboot and wipe cache and fix permission.
[Verizon Samsung Galaxy S III] mastamoon:
New build in OP.
[Verizon Samsung Galaxy S III] mpetruzz:
Is the volume fix incorporated in the latest build?

sent from my blue police box flying through time!!!
[Verizon Samsung Galaxy S III] ctsail410:
The commits were merged early this morning, so I'd assume so!
[Verizon Samsung Galaxy S III] mastamoon:
This ^ :D
[Verizon Samsung Galaxy S III] NegativeOne:
I don't know if that's the end-all here. it would be interesting to see how the config is used. I remember they had at one point hardcoded the 44100 rate, so maybe this is an override- but then I'm not sure what about this config would cause it to "sort of" work. Interested in seeing your findings though.
[Verizon Samsung Galaxy S III] PerCompLLC:
Did you decide not to include the battery bar cherry pick?
[Verizon Samsung Galaxy S III] neozen21:
Hmmm.. After flashing the latest build, there is no menu to pick what kind of reboot (system, recovery, download) anymore.

Anyone else experiecing this?
[Verizon Samsung Galaxy S III] ctsail410:
This was another change that got merged over the weekend. You need to go into Developer Options and check "Advanced Reboot" to get the menu back.
[Verizon Samsung Galaxy S III] PerCompLLC:
New documented safety feature of CM10.1. Enable the full reboot menu in developer settings.
[Verizon Samsung Galaxy S III] mastamoon:
Yeah it needed to be rebased, I didn't have time today to learn how to do it.
[Verizon Samsung Galaxy S III] PerCompLLC:
Ahhh... Cool. Thanks!
[Verizon Samsung Galaxy S III] mastamoon:
I believe one is from the a2dp audio revert builds I was doing. It's part of the fix. Putting this in alone will probably break audio in some way.
[Verizon Samsung Galaxy S III] funkymonk101:
Thanks so much mastamoon! Finally, a build of CM 10.1 with fully working bluetooth A2DP! Have only tested for about 10 minutes, but all of the obvious problems from other 10.1 builds (garbled/static audio, no audio) and the problems from the 10.0 build (lack of bass, low volume, random disconnects or not connecting) seem to be fixed here (running the 20130220 nightly). I actually didn't realize just how bad the bass/volume on 10.0 were until I installed this build.

I will keep running this as my daily driver and report back if any BT problems pop up. I use a variety of bluetooth devices (2 pairs of headphones, mic headset, pebble, car stereo, heart rate monitor), so if there are any bluetooth problems, I will probably encounter them.
[Verizon Samsung Galaxy S III] iofthestorm:
Incidentally invisiblek I think said that it was possible that it would be fixed when the new 3.4 kernel is used, which I think will be pretty soon since he did release a version that works on earlier builds but is broken on later builds (I think anything past 2/15). So hopefully it'll be gone soon.

Edit: to clarify, he said the reason no one was looking into it was because it was a kernel bug which might go away with the new kernel, not that they were specifically fixing it in the new version IIRC.
[Verizon Samsung Galaxy S III] ViperRacer:
It didn't seem to change any thing by itself. I was still getting the same results (choppy/static/slow). I even tried a full swap of the newer file for the older file and it broke all a2dp audio resulting in no sound via BT. So I'll fall back to my baseline and keep digging.
[Verizon Samsung Galaxy S III] minnysota:
I'm curious to know what kernel everyone is running with this.

After reading the LeanKernel thread, it appears that it's locking out at 1134 mhz (rather than 1500) on 4.2.2 ROMs using InteractiveX. Has anyone tried LK on Masta's latest build, or is everyone staying on the stock CM kernel?

Thanks in advance for any info. And thanks for another great build, Masta.
[Verizon Samsung Galaxy S III] goldsmitht:
Using KT747, and everything's working great! Maxes out at cover 2100
[Verizon Samsung Galaxy S III] minnysota:
What gov/scheduler are you rocking?
[Verizon Samsung Galaxy S III] kentedman:
+1
[Verizon Samsung Galaxy S III] M Diddy:
Is the reboot menu not functioning properly for anyone else?

Did a clean install, and when I select reboot from the menu, I don't get the choice to go into recovery. It just reboots the phone.
[Verizon Samsung Galaxy S III] alee:
Settings > About Phone > Tap on "Build number" 7 times

Go back to Settings and tap on Developer options

Then check off "Advanced boot"
[Verizon Samsung Galaxy S III] iofthestorm:
To add to what alee said, this was an intentional change by the CM team.
[Verizon Samsung Galaxy S III] aatrek:
Is the HDR camera stuff mentioned a few pages back included in today's build?
[Verizon Samsung Galaxy S III] Hybridnoob:
Yes, it's there.
[Verizon Samsung Galaxy S III] masterxchief:
Anyone having issues with bluetooth skipping once the screen turns off on the latest nightly?
[Verizon Samsung Galaxy S III] jlokos:
I have used LK on Masta's build and other 4.2.2 roms. I have had no issues using interactiveX and row scheduler. I have it set at 1620 and cpu spy confirms it is working.
[Verizon Samsung Galaxy S III] sivarticus85:
I do using Apollo, but PowerAmp is perfect. Good thing too since I prefer PowerAmp anyway because it supports gapless playback.
[Verizon Samsung Galaxy S III] kentedman:
Any chance of getting an option to enable the navbar? It drives me crazy that the hardware keys are backwards from all my other devices.
[Verizon Samsung Galaxy S III] ugachris:
This works for me:

http://xdaforums.com/showthread.php?t=1788780
[Verizon Samsung Galaxy S III] old&slow:
Use file explorer of your choice and go to system-->build.prop and open with text editor. Scroll down to the bottom and add the line "qemu.hw.mainkeys=0" without the quotes of course. Then reboot. ;)
[Verizon Samsung Galaxy S III] MWFD:
thanks Mastamoon, any chance you could provide the MD5?
[Verizon Samsung Galaxy S III] mastamoon:
ee555a9305f60cdadf762da88a1fcbf7 cm-10.1-20130221-UNOFFICIAL-d2vzw-reverts.zip

Got it..
[Verizon Samsung Galaxy S III] pinhead875:
Battery bar is back! Thanks, mastamoon. Downloading now.

OT: The HDR function is kind of useless without a tripod.
[Verizon Samsung Galaxy S III] ugachris:
I agree, but it looks like they are going to change this (at some point) to utilize the burst shot mode. That way the photos are taken quicker, reducing the chance of lens movement. See Steve's comment, he specifically mentions the D2:

http://review.cyanogenmod.org/#/c/32228/
[Verizon Samsung Galaxy S III] yznhmr:
no, i took a pic and added it to a text, and sent.... was sending 2 hrs..
[Verizon Samsung Galaxy S III] pinhead875:
Super cool, good find there.
[Verizon Samsung Galaxy S III] mastamoon:
Strange, since your post I have sent at least 5 mms without issue.
[Verizon Samsung Galaxy S III] minnysota:
Hey Masta –

Are you running the stock kernel? If so, what gov/scheduler are you using? I've noticed any kernel running Interactive locks out at 1134 MHz on 4.2.2.

Am I the only one who has tried LeanKernel and noticed this?

I'm trying to figure the best kernel (and settings) for these 4.2.2 ROMs.

Thanks in advance.
[Verizon Samsung Galaxy S III] mastamoon:
Yeah stock kernel, interactive and row. And yes it does prefer 1134 but does hit 1500 according to cpu spy at some times.
[Verizon Samsung Galaxy S III] jguns112:
Is there a way to get the quick pull down setting to turn off when you have any notifications regardless if they are on going or dismissible?
[Verizon Samsung Galaxy S III] invisiblek:
i know how much you guys like flashing broken, bleeding edge, crap

so here's a 3.4 kernel that will actually work on the newer cm10.1 builds (post display-caf updates)

http://invisiblek.org/sch-i535/kernels/kernel_3.4_msm-jb_2.5_02-21-2013.zip see EDIT2 below

enjoy the breakage! (although its not THAT bad)

known bugs:

- camera seems broken...umm...this was working at one point...heh

- front facing cam crashes on taking of picture

- auto brightness seems broken

- other things, i guarantee that, just cant think of them off the top of my head

as ALWAYS here is the source code: https://github.com/invisiblek/linux-msm-d2

EDIT: i'm not really looking for any feedback, especially not intending to clog this thread up, just giving you guys something to play with

EDIT2: reverted my derpish commit that broke the camera, new download: http://invisiblek.org/sch-i535/kernels/kernel_3.4_msm-jb_2.5_02-21-2013_d2vzw-2.zip

EDIT3: per GPL, the toolchain used to build this was:

$ ./arm-eabi-gcc --version
arm-eabi-gcc (GCC) 4.4.3
Copyright (C) 2009 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
[Verizon Samsung Galaxy S III] bobby janow:
Oh I'll give you feedback alright but not here. This better have my blue tint.!
[Verizon Samsung Galaxy S III] aatrek:
I've noticed that when I have my GS3 docked (in my USB car mount), the voice recognition doesn't work - it automatically jumps to the "Sorry, Didn't Catch That" message. Is this a build-specific issue, or a general CM thing?
[Verizon Samsung Galaxy S III] invisiblek:
more happy fun times

http://rootzwiki.com/topic/39296-app-chromium-browser-for-snapdragon-nightlies/
[Verizon Samsung Galaxy S III] Silvares:
Hi, I have a 64 GB SD Card formatted as exFAT. I've read that CM10.1 has issues with that format. Do you know which formats CM10.1 won't have issues with? ext4 or FAT32? I want to try to be able to have a file of more than 4GB.

Thanks.
[Verizon Samsung Galaxy S III] invisiblek:
fat32 will work natively, but won't support your files that are bigger than 4gb

ext4 works if you use a script to mount it on boot like I do

You can flash this to add an init script to enable ext4 external sdcard mounting on boot:

http://goo.im/devs/invisiblek/ext4_sdcard_init.zip

I'll leave the formatting of the card to you
[Verizon Samsung Galaxy S III] anacree:
I'm running the build from earlier this week (the 18th I think). Last night, while charging my phone, I was using it (checking facebook, email, etc). After turning the screen off with the power button, two separate times it wouldn't turn back on. The touch buttons on the front would light up when I pressed the power button, but the screen stayed dark. If I pressed the power button again, the screen would kinda do the "old TV turning off" thing. I had to pull the battery both times and restart the phone to fix it.

Today, since I haven't had the problem, but I'm not plugged in charging. I am using the stock USB cable to charge the phone. Any ideas or anyone else had this problem? Is there a way for me to reboot the phone without pulling the battery if the screen won't turn on? Thanks.
[Verizon Samsung Galaxy S III] sk8er88:
I bet a reboot into recovery, clear cache, delvik cache, and fix permissions would do the trick. I had that happen on a much older build, and I feel like that was the fix...
[Verizon Samsung Galaxy S III] anacree:
I did that. I'll let you know if I have problems the next time I use the phone while charging :)
[Verizon Samsung Galaxy S III] mastamoon:
new build in OP :good:
[Verizon Samsung Galaxy S III] masterxchief:
Is anyone else getting this with the verge app? I read in one of the posts that host files were changed, would it cause this? It was working fine til a couple of builds ago.
[Verizon Samsung Galaxy S III] minnysota:
It does hit the max frequency, but it prefers 1134 MHz. This is a response from imoseyon on rootzwiki:

"I have this in my FAQ post (2nd post on thread):

Why does my phone spend so much time at 1134Mhz?

Two reasons: 1) thermald, and 2) power hal. You can stop thermald ("stop thermald"), although not recommended. As for powerhal, read this post: http://rootzwiki.com/topic/32286-kernel-aosp-jb-leankernel-minimalistic-kernel-jb-42x-v27-22213/page__st__1210#entry1104109

--

In short, your ROM's powerhal has the 1134Mhz hardcoded as burst frequency. If you want to change that you can use an app like trickstermod to change "hispeed_freq" to whichever speed you desire."

---------- Post added at 03:14 PM ---------- Previous post was at 03:13 PM ----------

Any big changes that you've noticed, Masta?
[Verizon Samsung Galaxy S III] mpetruzz:
I flashed carbon ROM a few days ago to try it, or course I came back to masta's builds cause they're sweet!!

Now what's happening is every few hours my phone starts to automatically download carbon ROM again! I had like 4 downloads overnight!!

What in the heck do I need to do to have that stop?? I deleted too manager cause it used to do that. What else could it be??

sent from my blue police box flying through time!!!
[Verizon Samsung Galaxy S III] mastamoon:
No features really, mostly under the hood tuning kinda junk.

Maybe they modded CMUpdater and somehow the data stuck between roms? Try wiping data for CMUpdate.
[Verizon Samsung Galaxy S III] mastamoon:
On the kernel speed side.. I do see the stuff below in power.c.. I suppose I can change that to 1512000 and see if it works normally again. Maybe ill get bored this weekend and do a build with that, or it will be Monday.

sysfs_write("/sys/devices/system/cpu/cpufreq/interactive/hispeed_freq", "1134000");

Wonder why they changed it in the first place?
[Verizon Samsung Galaxy S III] mpetruzz:
One very minor thing I noticed was in previous build when I held the back button to kill an app it would do so in a sec or so. Now I'm having to hold the back button for about 5-7 seconds for it too work.

Any way to get it too close apps faster??

sent from my blue police box flying through time!!!
[Verizon Samsung Galaxy S III] GideonX:
I'm going to assume this only affects interactive. Since init.qcom.post_boot.sh sets interactive as default, I can see why so many people are seeing this cpu speed limit.
[Verizon Samsung Galaxy S III] iofthestorm:
If it's a sysfs interface can't you just do" echo 1512000 >

/sys/devices/system/cpu/cpufreq/interactive/hispeed_freq" from a root terminal to see if that affects it? Personally I don't care as long as I don't notice my phone acting sluggish since battery life is generally better at lower clock rates but those who are curious could try that.
[Verizon Samsung Galaxy S III] V3TTOO:
Is there anything different between the latest build and the 02/15 build? I am running things very well on it, so not sure I want to deal with more volume issues by updating to a newer build.
[Verizon Samsung Galaxy S III] edwards311:
For what it's worth.... 2/20 build with KT747 kernel is running strong like bull!!!!!! Thanx Masta
[Verizon Samsung Galaxy S III] masri1987:
just did clean flash of 2/22 afternoonly and home button is taking 5-10 seconds for response... anyone else? any tips?
[Verizon Samsung Galaxy S III] bobby janow:
Uncle Tanoose.
[Verizon Samsung Galaxy S III] mastamoon:
Flash another rom and make sure it's not hardware related.
[Verizon Samsung Galaxy S III] bobby janow:
Reboot. Then reflash of needed. Not an issue.
[Verizon Samsung Galaxy S III] mpetruzz:
I wiped data and it just tried to download again. I froze cm updater and too manager. Maybe that will help. Its so friggin annoying!!!

sent from my blue police box flying through time!!!
[Verizon Samsung Galaxy S III] rampantandroid:
Just checked my uptime: On KT747/Ktoonservative I'm at 1d 0h 36m and at 32% battery still with my on screen time being just shy of 2 hours. I'm happy...

Also, on this setup I can see that I regularly hit 1512, but spend more time at 384 (and the most in deep sleep, of course.)

Funny part is that before CM10.1 and these builds I was SO SICK of AOSP's instability I was getting and wanted a Nexus phone. Now I'm quite happy since my stability is pretty good.
[Verizon Samsung Galaxy S III] masri1987:
Redownloaded and re flashed, okay for now
[Verizon Samsung Galaxy S III] masterxchief:
No one else have this happening? The app works on my other devices. Just wondering if it's my phone or rom related
[Verizon Samsung Galaxy S III] mastamoon:
Have you wiped data on the app? Adblocker installed?
[Verizon Samsung Galaxy S III] masterxchief:
Ya wiped data, uninstalled and reinstalled, no ad blocker. Does the app load articles properly for you? If it works then I'll just try a clean install
[Verizon Samsung Galaxy S III] mastamoon:
Seems to work on here on my latest build, stock kernel.
[Verizon Samsung Galaxy S III] PerCompLLC:
Yup. I'm running masta's latest as well with lean kernel 2.7. Verge app works fine for me as well.
[Verizon Samsung Galaxy S III] jmaeishi:
If anyone can help me...why do the recent 2/18 build tear, and did the stop processes feature her relocated? Before I try another ROM that screen tears horribly I should know if others experienced this. It also happened with a 2/16 build. I hope someone has answer. Thank you.
[Verizon Samsung Galaxy S III] bobby janow:
zomg will this ever end? Can we please get rid of the word "tear" from the english language?
[Verizon Samsung Galaxy S III] masterxchief:
Thanks guys, I'll clean install then.
[Verizon Samsung Galaxy S III] iofthestorm:
Uh... He's using the word correctly, I don't see the problem.

And to answer your question, no, I don't think most people experience screen tearing so you should perhaps try wiping everything and flashing again, or maybe ODINing back to stock and flashing again.
[Verizon Samsung Galaxy S III] bobby janow:
What I meant was that if you search the word tear you will come up with a thousand hits. And in 1k posts you are sure to find an answer. So stop!