yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] ckelly33:
+1 I've been wondering this as well. I'm not sure of the differences of 3.0 and 3.4 or why I would want one over the other (other than stability)
[Verizon Samsung Galaxy S III] tpayne2345:
Smooth.. I was skeptical at first but I too haven't had a single lockup and it's smooth and quick.. Big upgrade over 1.6.1 and KT 3.0
[Verizon Samsung Galaxy S III] jamesino:
Just flashed it. It's the fastest 3.4 ROM/Kernel combo I've used so far. But it's still not as fast as the v3.0 version of the KT747 kernel. The transitions are still lagging a bit and when scrolling up and down menus, you'll again notice lag where it was non-existant in the 3.0 kernels. But if the stability keeps up, then it's a worthy trade off.
[Verizon Samsung Galaxy S III] 760hacker:
Nightly or 1.6?
[Verizon Samsung Galaxy S III] draexo:
Just a follow up here: it looks like 3.4 kernels cause display issues just as lines in screen briefly.

Sent from my Carbonized S3 via Taptalk
[Verizon Samsung Galaxy S III] buggerritt:
They are discussing Carbon 4-8 nightly
[Verizon Samsung Galaxy S III] jamesino:
I flashed the 4/8 Carbon and 4/7 KT747.

I also occassionally get the flickering line issue (not rainbow colored, but just like grey flickering lines). I noticed it's app dependent and brightness dependent. When I have CABC enabled in the Advanced settings, it's usually worse.
[Verizon Samsung Galaxy S III] imtoomuch:
Is the 4/9 build still not booting?
[Verizon Samsung Galaxy S III] krazie1:
Can anyone say if the New 4/10 nightly Boots up?
[Verizon Samsung Galaxy S III] jamesino:
For those of you guys running interactive with KT747 kernel with the new v3.4 nightlies.

If you go into KTweaker and change the timer_rate from the default 20 000 to 10 000, you'll notice that scrolling pages becomes a lot smoother.

I am unsure how this affects battery life or stability.

But this fix bring the scrolling more or less on par with that on v3.0 kernels.

Transition animation is still laggy however relative to v3.0 kernels.
[Verizon Samsung Galaxy S III] Neverender326:
Smooth as butter

---------- Post added at 07:01 AM ---------- Previous post was at 06:58 AM ----------

Try cross breeder...I'm running ktoonservative 81mhz min and everything is smooth. I always turn off animations though.
[Verizon Samsung Galaxy S III] mapatton82:
Booted just fine here.
[Verizon Samsung Galaxy S III] draexo:
I get it when walking from power button. I suspect it's a 3.4 kernel issue

Sent from my Carbonized S3 via Taptalk
[Verizon Samsung Galaxy S III] jamesino:
I actually had this problem on v3.0 kernels too and even on stock TW. But on stockk TW, all I had to do was turn the screen off and back on and it would go away.
[Verizon Samsung Galaxy S III] bairste:
OK I am on 4/7 nightly and getting horrible battery life. For some reason the phone application is draining the battery. I am using lk 5.2.
[Verizon Samsung Galaxy S III] Wi1son:
FYI - Flashed 4-10 nightly with the 4-7 KT747 kernel during the same session. All is smooth.
[Verizon Samsung Galaxy S III] david_hume:
Is this your first boot?

Sent from my Carbonized GS3
[Verizon Samsung Galaxy S III] vzw2491:
just flashed the 4/10 nightly, booted up just fine and it's running great. seems to be running very smooth and not having any issues yet.

Also, is it just me or does anyone wish that the paranoidandroid settings would be included in this ROM? i know the xposed framework is capable of doing the same stuff, but from what I've seen in the past with other ROMs is that the paranoidandroid type settings allow for better customizations and cause less interference with other phone processes compared to Xposed framework.
[Verizon Samsung Galaxy S III] rfranken:
1.6.1

can't make a call longer than 5 seconds. hard lock and have to battery pull.
[Verizon Samsung Galaxy S III] bitemeoftn:
Really digging the new splash screen and boot animation on the new 4/10 nightly. And just for anyone wondering it's smooth and I haven't flashed a custom kernel yet I'll see how the stock one plays for a few hours.
[Verizon Samsung Galaxy S III] mapatton82:
Just so you know it is working great with LK test kernel 5.3.4, have been listening to music all morning a few phone calls and email, no issues what so ever.
[Verizon Samsung Galaxy S III] bitemeoftn:
Nice! Thanks for the info.
[Verizon Samsung Galaxy S III] rfranken:
clean install of the 4-10 nightly. I still can't install any apks.

the install button is not grayed out...but it is not clickable.

doesn't matter if on the internal memory or external sd card.

the cancel button clicks just fine.

looking for some bright ideas of what to try and fix this issue.
[Verizon Samsung Galaxy S III] krazie1:
IDK if this is the place to ask but i'll ask anyway, Does anyone know why Shadowgun Deadzone plays really smooth on TW Roms but on carbon with different kernels tested it seems kind of rough and jittery?
[Verizon Samsung Galaxy S III] mapatton82:
Most games seem fine for me, mainly Dead Trigger. Here are some things to check:

1) Make sure your not undervolting or under clocking too much

2) Make sure the governor you are using can handle the game

3) check to see if you have "Disable HW Overlays" and "Force GPU rendering" unchecked in developers options.
[Verizon Samsung Galaxy S III] david_hume:
Because there are some areas that touchwiz excels in that AOSP doesn't. Same goes for AOSP being better than TW at some areas Quadrant standard tests are useful to show this.

Sent from my Carbonized GS3
[Verizon Samsung Galaxy S III] rfranken:
within a couple hours of running the 4-10 nightly I've already had a random reboot. (stock kernel. that didn't make a difference on other nightlies so probably still doesn't)

frustrating.
[Verizon Samsung Galaxy S III] mr_bungalow:
3 days of the 4/8 nightly and the 4/7 KT Kernel and I haven's had a single random reboot. This really is as solid a daily driver as I've had on AOSP. I can't comment on the smoothness of 3.0 vs 3.4 as I only recently came from TW ROMs. I'll give a ROM 3 random reboots before I flash another.
[Verizon Samsung Galaxy S III] jamesino:
I've been on the 4/8 nightly with the 4/7 KT kernel for almost 24 hrs, no problems yet. I run interactive governor and with a little tweaking to the timer_rate, I can get this build to be almost as fast as v3.0 ROMs running the latest 3.0 KT kernel.
[Verizon Samsung Galaxy S III] keynith:
4-9 nightly a no boot.

Running the 4-10 nightly with ktoonsz 4-3 AOSP 3.4 kernal currently. No complaints so far guys. Nice work :)
[Verizon Samsung Galaxy S III] masri1987:
4/10 Nightly with ktoonz I've gotten several random reboots, mostly while on chrome

Oh i did a dirty flash from 4/8
[Verizon Samsung Galaxy S III] EGill42:
I am currently on the 4/8 nightly. I can't seem to find the power widgets option; has that been removed? Also, I have noticed one odd problem with these roms. In the settings when you press on the Language & Input option, the settings will crash. This happened initially on the 4/8 nightyl, but went away the next day for no reason I can understand.

My reason for using this option is to set the keyboard to Swiftkey, so I tend to notice this bug right away. Has anyone else noticed this before? If not, is there anything I can try and learn what a logcat is, and how to provide it to the developers.
[Verizon Samsung Galaxy S III] jamesino:
For those of you running v3.4 nightlies with the newest KT747 kernel and using the interactive governor, if you're finding scrolling to be a bit laggy and choppy, you can go into KTweaker and change the go_hispeed_load from 99 to somewhere like 40-50. Scrolling, such as up and down your inbox in Gmail, will be much smoother now.

Potential decrease in battery life since your phone is more sensitive to using its max clock rate.

---------- Post added at 07:26 AM ---------- Previous post was at 07:06 AM ----------

One small bug:

Under Settings>Statusbar>Clock and date, when you assign a Clock long/short click action to add a calendar or view calendar of today, System UI freezes.
[Verizon Samsung Galaxy S III] WettbackMartyr:
Powerwidget is still there;

Settings > CarbonRom > Powerwidget

The swift key problem was discovered and repaired a while back. While I do not use swift key, I believe the issue was solved by setting swift key as default from within the app itself, instead of from within the settings application. Try searching this thread for swift key. I know the answer lies some pages back.
[Verizon Samsung Galaxy S III] rfranken:
the random reboots on the nightlies are roughly every two hours.

if i go back to a 3.0 kernel version then i can't make phone calls.

seems other cm based roms have similar issues. i'm not going back to a 4.1 rom. what to do what to do.

battery life in a 3.0 is good

battery life in a 3.4 is real bad.
[Verizon Samsung Galaxy S III] Wrngway:
Delete
[Verizon Samsung Galaxy S III] WettbackMartyr:
Have you tried a kernel other than stock??? Have you tried a clean install??

Only asking because I clean installed 1.6 with lk and have been flashing nightlies up to 4/10 right over the top and only had a random lockup on 1.6 and not 1 since. Running lean kernel 5.2 with 4/10 nightly currently and I must say, for me it's as stable as a release! Just my 2 cents.
[Verizon Samsung Galaxy S III] mapatton82:
The latest nightly (4/11) has been working great with the latest LK 5.3.4 kernel.
[Verizon Samsung Galaxy S III] imtoomuch:
The 4/10 build ran great, but it killed my battery in no time. The Phone app showed the most battery usage which is rare. I was not on the phone at all yesterday.

The 4/11 build is also eating battery life. In less than 3 hours, my battery dropped from 100% to 62% even though I barely used my phone today. The phone was extremely warm while being unused in my pocked. Android System showed the most battery consumption.

I reverted back to the 4/8 build with a dirty flash and all is well again. My phone cooled down and the battery consumption has dropped back down to normal.
[Verizon Samsung Galaxy S III] rfranken:
yes and yes

none work any better than the others.
[Verizon Samsung Galaxy S III] mapatton82:
Were you using a custom kernel or stock? I have had 4/11 installed since this morning with LK 5.3.4 and I am at 69% after 6 hours and 41 minutes and this is with streaming Slacker radio over my bluetooth headset for at least 5 hours.
[Verizon Samsung Galaxy S III] imtoomuch:
Stock kernel. I have never used a custom kernel.
[Verizon Samsung Galaxy S III] bigee1212:
If I am dirty flashing nightlies, do I have to install gapps every time?

Is there a changelog for nightlies?

Why do so many people install custom kernels instead of using the stock?
[Verizon Samsung Galaxy S III] mapatton82:
Here is the nightly changelog: https://docs.google.com/document/d/1Zcp6iVWVw_7iH-ErnKgkYy3r5QuqV8PHFoQMb8hoBwQ/mobilebasic

As to why we use custom kernels, well some kernel devs strip down the kernel to include only what is needed to increase speed and smoothness. Also custom kernels allow fro over/underclocking and undervolting. I am sure there a ton of other benefits but I feel these are the main reasons.
[Verizon Samsung Galaxy S III] spearoid:
Re: [ROM][AOSP][LINARO] CarbonRom JB 4.2.1 [d2vzw] » Feb 6

Well it sounds like an SD card formatted in ext4 that works on AOSP would be the solution or being able to swap the internal memory with the SD card.

The point of Google music is that it is a cloud player. I can buy music on my computer and put it with the rest of my music on my computer and it automatically loads into my Google Music cloud. I can then decide which albums I want available offline from my phone.

If I wanted to manually transfer my music to a memory card I'd go dig my Sony Clie out of storage.
[Verizon Samsung Galaxy S III] xdapadogx:
Re: [ROM][AOSP][LINARO] CarbonRom JB 4.2.1 [d2vzw] » Feb 6

Went to the camera from messaging. I took the picture and it didn't show me an image of what I took after I took it. I hit the retry button and gallery fc. Not I can't connect to camera at all
[Verizon Samsung Galaxy S III] jackpot08:
Re: [ROM][AOSP][LINARO] CarbonRom JB 4.2.1 [d2vzw] » Feb 6

Great ROM.one annoyance I gave noticed on 4.2.1 Roms is that while on WiFi if I get an MMS it will disappear and not download it
[Verizon Samsung Galaxy S III] goldsmitht:
Re: [ROM][AOSP][LINARO] CarbonRom JB 4.2.1 [d2vzw] » Feb 6

Haven't seen that on any of the 4.2.1 Roms I've run
[Verizon Samsung Galaxy S III] VinBertinelli:
Re: [ROM][AOSP][LINARO] CarbonRom JB 4.2.1 [d2vzw] » Feb 6

Anybody else get Google service battery drain?
[Verizon Samsung Galaxy S III] masri1987:
i was literally about to ask this question, also GPS has been "using" battery but it isn't on , since this morning all the way to now...
[Verizon Samsung Galaxy S III] dmang83:
Google voice search keeps popping up an error "unfortunately, voice search has stopped". Even the error pop up stays on for a very short moment and disappears. Other than that, great rom! Thanks!!
[Verizon Samsung Galaxy S III] tbodner:
this has happened to me once, I just rebooted the phone, charged it, and it went away....I saw this one time before but it's either an error or something glitches.

---------- Post added at 04:50 PM ---------- Previous post was at 04:50 PM ----------

did you update google search from the play store?
[Verizon Samsung Galaxy S III] masri1987:
Re: [ROM][AOSP][LINARO] CarbonRom JB 4.2.1 [d2vzw] » Feb 6

So media services keep eating battery, gps I'm battery stats shows its on even though it's not and blue tooth requires a reboot to turn it off or else it just stays on turning off bluetoooth

On kt kernel
[Verizon Samsung Galaxy S III] kentedman:
I have notifications for email (Exchange and Gmail) set to silent and never vibrate. However, when phone is in "vibrate only" mode, it vibrates when email is received.
[Verizon Samsung Galaxy S III] huskerpat:
Re: [ROM][AOSP][LINARO] CarbonRom JB 4.2.1 [d2vzw] » Feb 6

Try bubbleupnp.
[Verizon Samsung Galaxy S III] joaquinla1:
Re: [ROM][AOSP][LINARO] CarbonRom JB 4.2.1 [d2vzw] » Feb 6

First of all AWESOME rom!! It's been working great, gps locks instantly, Bluetooth works, everything major is covered!! Thank you devs!

The only minor things I've found are:

The loud noise when you hang up

Vibration is really intense

I changed to kt kernel to use vibration strength control included but is there a way to add this to rom settings?

Thanks again!
[Verizon Samsung Galaxy S III] kentedman:
Love the centered date and time option on the statusbar. I've seen a MOD for this but it's nice to have it built in the ROM.
[Verizon Samsung Galaxy S III] jackpot08:
Re: [ROM][AOSP][LINARO] CarbonRom JB 4.2.1 [d2vzw] » Feb 6

Also the MMS quality is greatly compressed.this use to be a problem the unofficial cm10.1 but mastamoon fixed it.I was wondering if this could be implemented in this ROM?
[Verizon Samsung Galaxy S III] soapinmouth:
Re: [ROM][AOSP][LINARO] CarbonRom JB 4.2.1 [d2vzw] » Feb 6

You can screenshot by holding power and volume down
[Verizon Samsung Galaxy S III] XfrostX:
Hey, just lookin through this rom. Looks pretty good, just wondering if there were any AOSP bugs such as GPS locking or data. I ran CM for a while but ran into data issues and had to revert to touchwiz :/. Lookin for a change soon.

Thanks
[Verizon Samsung Galaxy S III] annoyingduck:
Re: [ROM][AOSP][LINARO] CarbonRom JB 4.2.1 [d2vzw] » Feb 6

How many of these are we gonna get in the upcoming weeks.... :confused:

But to answer you, this is as stable as your gonna get 4.2 wise currently. Very impressive rom, no major bugs whatsoever. All the big things and a ton of little things work as they should. These guys did their homework....
[Verizon Samsung Galaxy S III] XfrostX:
Sorry about the repeated question, I should have went through the thread more.

Thanks for the fast reply, prolly gonna try it out soon
[Verizon Samsung Galaxy S III] cregor:
Re: [ROM][AOSP][LINARO] CarbonRom JB 4.2.1 [d2vzw] » Feb 6

Maybe try reading back a few pages it would answer everything you just asked.

Rom works awesome.
[Verizon Samsung Galaxy S III] mpetruzz:
Re: [ROM][AOSP][LINARO] CarbonRom JB 4.2.1 [d2vzw] » Feb 6

So I flashed liquid ROM a few weeks ago and have noticed that my phone keeps downloading the latest version in the background every few hours. I don't have goo manager uninstalled but it keeps trying to download even though I'm running carbon.

I figured I'd ask this question here since most of the team worked on liquid.

sent from my blue police box flying through time!!!
[Verizon Samsung Galaxy S III] jamesino:
I've been running the 4/8 nightly with 4/7 KT747 for almost 2 days now, not a single problem so far. Peformance is almost on par with 3.0 kernels when you tweak the governor settings a bit. Battery is a bit worse than 3.0 Leankernels
[Verizon Samsung Galaxy S III] bitemeoftn:
4/11 nightly and new 4/11 KT kernel. Perfect combo!
[Verizon Samsung Galaxy S III] tprophit:
Changelog says no gapps flash ...so does that mean the nightly doesn't preserve gapps, or that it doesn't, so we have to?
[Verizon Samsung Galaxy S III] mapatton82:
If you have flashed a nightly since the 3/26 nightly, you shouldn't have to flash gapps unless you are doing a clean install. What you saw in the changelog for 4/12 is for the SGS2.
[Verizon Samsung Galaxy S III] jamesino:
I know a clean flash is always recommended, but I'm new to this ROM and was wondering if I can get away with dirty flashing 4/11 over 4/8?
[Verizon Samsung Galaxy S III] BrUhNiGGs:
Any ideas why my phone has been running very warm lately? I'm underclocked to 1.1ghz and 81mhz. I do have a few UCCW widgets on my launcher and I'm wondering if that's it? How could I possibly track this down.
[Verizon Samsung Galaxy S III] hootyburra:
Yes, Wipe Cache and Dalvik then flash away.
[Verizon Samsung Galaxy S III] tpayne2345:
Running a nightly or stable? When I was on 1.6.1 my phone would get hot, not warm, after solid usage

I'm on 4/8 now and haven't had any problems at all, literally none
[Verizon Samsung Galaxy S III] rfranken:
The very latest lean kernel seems to be working well. Haven't had a random reboot yet. 5 hours in.
[Verizon Samsung Galaxy S III] cuban11182:
This may be a dumb question, but it's there any way I can get the My Verizon Mobile app to automatically login?

Sent from my S3 infused with 1.21 gigawatts!
[Verizon Samsung Galaxy S III] draexo:
Do what I do... Two spare batteries and lots of chargers and now I found these rounds portable chargers that work great.

Sent from my Carbonized S3 via Taptalk
[Verizon Samsung Galaxy S III] WettbackMartyr:
Don't believe so. Best you can do tho is to save your login info so all you have to do is tap "Login". The auto login is a touchwiz feature that uses a Verizon user services type app to allow for that functionality.
[Verizon Samsung Galaxy S III] BrUhNiGGs:
I'm running 1.6.1 . I'm a little iffy on going back to the nightlies because I think 3.4 is still unstable and I'm not trying to deal with the freezing
[Verizon Samsung Galaxy S III] ckelly33:
I've been avoiding nightlies too (1.6.1 + LK has been fine, but makes my phone warm).

Everyone seems to have had good luck with 4/8 so I just might flash my first nightly. I've been dirty flashing without any trouble up to this point but didn't know if that was advisable when changinf from 3.0 to 3.4 & vice versa. Does most everyone clean flash when changing between 3.0 and 3.4, or does it matter?
[Verizon Samsung Galaxy S III] tprophit:
I cleaned from 3.0 to 3.4. Other than the kt747 kernal install issues a while ago, which are fixed, have had no rebooting or screen flicker issues. Been on 4/11 for both for an hour, all good so far.
[Verizon Samsung Galaxy S III] bitemeoftn:
Going from 3.0 to 3.4 DEFINITELY clean install. I've been running the 4/11 nightly with the 4/11 kt747 kernel all day and have had zero issues. Streaming music making phone calls and playinga few games. They've even added a thermal adjustment to the kt747 kernel although I'm unsure of making any adjustments to it yet lol. Hope that helps alleviate any concerns you have with making the switch to 3.4. Happy flashing!
[Verizon Samsung Galaxy S III] pocii29:
I dirty flashed from March 26 to April 8 and running KT April 7 build. Very smooth and stable. With pegasus/zen I get 4 hours on screen over 20 hours on stock battery
[Verizon Samsung Galaxy S III] Rev. Voodoo:
I stayed on one of the March builds for a bit, then dirty flashed to 4/7 and then 4/10. The past 2 builds that I mentioned have been flawless for me. I haven't had to pull my phone out of that damned Otterbox once. No glitches that I've noticed or anything. I don't use my phone for voice much so that has not been heavily tested. I do stream a lot of music, and I use my GPS heavily for fitness tracking apps. Those features have both worked perfectly.
[Verizon Samsung Galaxy S III] PeakyBoo:
For what it's worth, I to dirty flash from 3.0 to 3.4 and I've been on nightly 's ever since. I have not had problems. That being said you can tell by the responses above , that it is split pretty much between dirty flashing and clean flashing. imo it really varies from phone to phone. Just have to try and see .

Peakyz ° S lll ° Carbon Nighly=4/11-Latest LK- Mod-DS Batt-Grnfy-Theme=Colbalt :good
[Verizon Samsung Galaxy S III] ckelly33:
Does Google Wallet work with 3.4 based Carbon?
[Verizon Samsung Galaxy S III] pocii29:
Lol using an Otterbox too... What a Damn pain in the ass when you have to battery pull
[Verizon Samsung Galaxy S III] draexo:
Only if you edit your build.prop file, which I don't recommend.:mad:

Sent from my Carbonized S3 via Taptalk

---------- Post added at 12:01 PM ---------- Previous post was at 11:57 AM ----------

Except screen jitters on occasion, I've no problems with 1.6 & 1.61 with lean kernel.

Except the face unlock issue where face unlock does not work if the phone locks with an app that is using the camera running. A battery pull fixes the issue. I am betting it does this with touch wiz too, but I'm not going back to find out.

Sent from my Carbonized S3 via Taptalk
[Verizon Samsung Galaxy S III] buggerritt:
Why are you against editing the build prop? I've done this and then after installing, setting up wallet, set it back to stock. Wallet works fine from then on. Is there a reason that this would be harmful or dangerous? I'm truly curious because I've been doing this after every ROM flash, for months now. If there's a reason not to, i want to know so i can decide if it's worth it. I really like using my phone at the register but it's not necessary.

Hopping from ROM to ROM in my Verizon Galaxy S3
[Verizon Samsung Galaxy S III] saintsantos:
Rock Solid

I'm running the 1.6.1 release of carbon with BMS kernel and haven't had a single issue so far. To say this rom is really smooth doesn't even begin to describe it. I really like the inclusion of Apollo media player (one of my favorites). Everything seems to connect fine, 4G, wifi, gps, and nfc. Great Work guys:laugh:
[Verizon Samsung Galaxy S III] draexo:
Wait! You are saying I can edit build.prop back after wallet installs??!!

Sent from my Carbonized S3 via Taptalk
[Verizon Samsung Galaxy S III] keynith:
Backup ur current before modding. Rename it build.prop.bak or make a copy and store it elsewhere, where it's safe :)
[Verizon Samsung Galaxy S III] ckelly33:
Wallet installer does it all for you. I just don't know if it still works on 3.4 kernels
[Verizon Samsung Galaxy S III] Rev. Voodoo:
It does. I've been using it on every nightly flash as well, it's part of my routine. I'm on 4/10 right now and wallet works just fine, using the installer.
[Verizon Samsung Galaxy S III] buggerritt:
Yes. I have been following the gscript buildprop edit directions (super simple) from this thread : http://xdaforums.com/showthread.php?t=2125300

I know that the install I mentioned works on 3.4 but, I am interested in this method. Do you have a link? Worst case scenario is that it doesn't work and then restore a nandroid.
[Verizon Samsung Galaxy S III] Rev. Voodoo:
THis? http://xdaforums.com/showthread.php?t=2044362 It's the installer I use on 3.4, has worked up until 4/10 at least... that's what I'm running