yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] BillBauman:
Just to give my input on the heat/Android OS Process eating battery, etc.

On 125 I was running Ziggy's kernel, but had lag, sluggishness, not a smooth experience. So I went back to Lean Kernel, it was great, very snappy. I went to 147 and decided to try out Ziggy's kernel again. It was actually pretty decent, so I think it might have been the clean wipe and all that with the minor updates to the Ziggy kernel that made it work out okay. I had good battery life and decent performance. I then did the dirty flash to 155 and the whole thing went in the bin, basically. I tried for over a day to charge/tolerate the Ziggy kernel, but it just wasn't cutting it. I didn't try re-flashing to get the kernel to stick, I just went to Lean Kernel 1.5 for JB, and everything is back to normal again. Snappy, no heat/battery issues, etc.

I've run LK with everything from 1.8 or 1.9GHz down to 1.2GHz, all respond well. You can tell a difference in the performance, slightly, between the speeds. It isn't huge, though. I haven't tried running extended periods underclocked to see if it seems to improve battery or not. I'm always on the OnDemand governor and the deadline scheduler with my GS3 (but I'm totally open to suggestions there, especially on the I/O scheduler).

When the fully integrated >155 ships, I'll give it a shot. I do like the split screen, but it isn't a must-have for me. I may go back to 125 or 147 base for a while if an integrated, more ironed update doesn't come soon. Just my thoughts on the subject. I really had a great, stable 125 experience. 147 was a bit rocky, but I think I like some of the improvements. I do really like the toggle text improvement in 155. So, here's to hoping 155 + LK 1.5 is a smooth experience over the next day or two and I can stick with this long enough for the next big update.

Thanks to all who have reported their issues. I was glad to see it wasn't just me, and it also encouraged me to write up my update and recent experiences.

Note, long-press track skip worked up through 125. I didn't try it on 147 before going to 155 where I can verify it has been regressed. I'm sure Synergy team will be working to re-apply.
[Verizon Samsung Galaxy S III] omnia38:
I just found out that if you hold the multi-window tab icon...(while the mini drawer is open) you can drag and drop it to any of the four sides of the screen. Might not be news, but I was happy to stumble upon it.

Hit the thanks button if you like the tip.
[Verizon Samsung Galaxy S III] Hobart!:
Holy crap..lol...just tried it...thanks!
[Verizon Samsung Galaxy S III] Amazingbman:
Still no gps lock on 155 with lean kernel 1.5
[Verizon Samsung Galaxy S III] makmoneynslp:
Yezzir this is that deal
[Verizon Samsung Galaxy S III] ChrisNee1988:
Anyone run into these large things above the multiwindows. The buttons like the maximize and close don't seem to be working on them.
[Verizon Samsung Galaxy S III] dscblu:
Ive come across those myself but there not on all apps
[Verizon Samsung Galaxy S III] rocketj:
Same for me. Was working fine on r147.

Besides that running great!

Thanks Synergy Team!!
[Verizon Samsung Galaxy S III] BillBauman:
Have you tried GPS Status? It can reset and download new A-GPS data. It's helped me to get better calibration.

https://play.google.com/store/apps/details?id=com.eclipsim.gpsstatus2&feature=nav_result#?t=W251bGwsMSwyLDNd

That said, I definitely had way better lock-prior to 147 (on 125 all was awesome).
[Verizon Samsung Galaxy S III] Hobart!:
Just got bbstats and still figuring out how to read..is this normal?

Audio out_2 ???

Power management service??

And other wake lock below it...seems high???
[Verizon Samsung Galaxy S III] silver1882:
I think ziggy kernels run great never have had a problem with them. Yes my phone runs a little hot when I first flash a new rim but after it settles down no problem.
[Verizon Samsung Galaxy S III] jlyle:
Posted that about 8 pages back .. where u been ? :p

http://xdaforums.com/showpost.php?p=36399375&postcount=13198
[Verizon Samsung Galaxy S III] stargate125645:
With all the compatibilty issues people are having not using the stock kernel, particularly with exFAT, this ROM really should be offered with the stock kernel. Links to Ziggy's kernels are still readily available and can be used by anyone who wishes to do so - a lot of people are flashing other kernels anyway. I think this would make the ROM even more universally used.

(And the stock kernel offered by Ziggy does not work with exFAT, so that is not a solution. Perhaps there are other stock kernels that are compatible with this ROM that are available in the mean time?)
[Verizon Samsung Galaxy S III] eschelon:
To those flashing other kernels, that's fine, but be advised that you will lose our ramdisk hacks. A lot of kernel devs out there (not all) pack the entire boot.img into their zip, rather than just the kernel itself. Ziggy's kernel flashable zips do it the proper way by flashing over the zImage and modules, without overwriting the ramdisk.

Appeal to your kernel devs to have them look at Ziggy's flashables to see how to do it the proper way. It would be awesome if this became standard procedure for all kernel devs on XDA so that we won't have people losing out on ROM features cuz a kernel blows away ramdisk.
[Verizon Samsung Galaxy S III] Amazingbman:
I have tried this, I get no lock at all. It shows 0/25 satellites. Ty
[Verizon Samsung Galaxy S III] ryan1977:
I too am using lk 1.5 with no issues

At first it was a little laggy, but I left it alone for a good hour and it seems to have gotten settled or something cause now its very snappy as usual.
[Verizon Samsung Galaxy S III] BillBauman:
I've read about folks who lose WiFi and/or GPS on flash if it's disabled at the time they do the flash. You could try flashing backward to a previous, working version, ensure that your GPS is enabled, then re-update to the latest 147/155 flashes. That might get it back for you.
[Verizon Samsung Galaxy S III] Digital DJ:
Ok, I need help. I was running a clean flash of r147 then I dirty flashed to r155. Everything seemed to be working fine, but when I tried to restore my previous nandroid, I'm stuck in bootloop and I can't get into recovery

Edit: Effing battery was dead...lol fixed...
[Verizon Samsung Galaxy S III] jlokos:
Pull battery, press volume up, power and home key at the same time. You should boot into recovery.
[Verizon Samsung Galaxy S III] cuban11182:
Just had to take a drive and the Bluetooth would connect in my truck but no sound would come out after the call connected.

Sent from my S3
[Verizon Samsung Galaxy S III] tu3218:
Not sure if kernel part of OP was updated or not, but it was my understanding that kernel source had been released for the verizon sgs3. So is 155 still based on ziggy's kernel or JB official K3 kernel? Just curious. thanks for this.
[Verizon Samsung Galaxy S III] DieselNY:
This may be a silly question but can we remove the sim card and still flash roms?

I used my phone for my business so instead of missing calls during the flashing prcocess I want to install my sim card on my nexus and use that for calls for the next hour or so while I play with the SIII and doing nandroids and flashing etc, thanks.
[Verizon Samsung Galaxy S III] omair2005:
Besides random acore FC it's running pretty good
[Verizon Samsung Galaxy S III] keymaster911:
Yes.

Sent from a slamming S3
[Verizon Samsung Galaxy S III] enix316:
I would have no problem running ziggys kernel. Except that under a fresh install my phone would run ~45 seconds before it would go black and a battery pull was needed. It did this 4x in a row. First time I have had a problem like this with yours or anyone else's work. If this was my first time flashing I would have freaked, but I just flashed a kernel I had and all was well.

Is there anything those of us with issues can contribute to help fox the bug? Other than saying it's hot, it sux, I'm onto something else? I blame the hardware honestly. 2 phones/computers/cars can all the same parts and have different problems.

If there are any logs that would be helpful let us know. I would have to wait until tomorrow to flash anything else, on call tonight.
[Verizon Samsung Galaxy S III] mugenfa5:
I'm actually experiencing similar problem as well. I got r147 to work just fine but when I flash to r155, I can longer access torch from lockscreen. Not a major problem, just thought it was weird.

Also anyone experiencing problem with pinch to zoom. For example, I try to pinch and zoom a certain word, the screen either moves to one of the fingers that is making the pinch to zoom gesture (sort of like the screen is hopping around). I have to scroll back to the word I wanted to originally zoom at. I notice this problem occurred on build r147 but r125 didn't experience this.
[Verizon Samsung Galaxy S III] mytoy1:
+1
[Verizon Samsung Galaxy S III] Hobart!:
Esch....I posted earlier......after the video I rebooted for the first time since flashing 155 and for some reason and when it booted it came up in landscape frozen...hmmm...so I battery pulled...tried 4x same thing....so finally I booted from power off into recovery...flashed lk1.5 and it booted fine. I'm not sure why it booted each time in landscape(no matter how I held it) and froze? Kernel related? Again... It was my first reboot since flash..booted frozen in landscape until I changed kernels..Any ideas?
[Verizon Samsung Galaxy S III] Soldi3rxx:
I believe it kernel related. I went through the same thing and I flashed stock kernel. All is well now. Read a couple pages back people seem to just change kernels n everything worked out
[Verizon Samsung Galaxy S III] makmoneynslp:
Same issue here with the bluetooth but the multi view is the breaker of all and I'm an aosp guy and this I love

I just want to know can I appy themes on top of the rom
[Verizon Samsung Galaxy S III] Amphibliam:
How can I set Google now to the home button double tap?
[Verizon Samsung Galaxy S III] prdog1:
If have S-Voice enabled go to it in settings>app management and kill default. Should then be able to pick what you want.
[Verizon Samsung Galaxy S III] mugenfa5:
Mine reboots in landscape as well but doesn't freeze on me though. After like a sec in landscape mode, it reverts itself back to portrait.
[Verizon Samsung Galaxy S III] prdog1:
Not sure but may be able to use a VRTheme as it only changes PNGs and XMLs and not actual framework files unless hack required xml edits also. :cool:
[Verizon Samsung Galaxy S III] savaytse66:
For those of you having battery drain and/or heat issues, give the ROM a charge cycle or two after flashing. Any time I flash, I get severe drain the first boot, and quite often pretty high heat. This has happened on CleanROM and Synergy for me, and with multiple kernels. This release has been out less than 24 hours, so give it a day at least.

On 147, I had the worst battery drain I ever experienced on the initial discharge. Following a full recharge, I had the BEST battery life I've ever had.

It's been said before, and I'll say it again: let the ROM settle...
[Verizon Samsung Galaxy S III] theDK10:
So i haven't flashed since r73 and im taking the plunge to r147 and r155. Quick question though does esch wipe system for you or do i have to do this manually? And im using the latest twrp do i need to just hit the system wipe or factory reset? thanks in advance
[Verizon Samsung Galaxy S III] cr4ck3r4lif3:
I add a .nomedia file in each folder that I don't want the system to scan. I have never run into battery drains, or high system media issues, or the phone getting hot.
[Verizon Samsung Galaxy S III] makmoneynslp:
Nice is vrtheme located in the apps and theme section
[Verizon Samsung Galaxy S III] xxaimbkstarxx:
HElp?

When i try to flash this rom From clean install

wipe cache

wipe dalvic

format system

Then i go to install it says preparing device

Formating sytem partition

At this oint nothing else happens it tstays here for at least 20 mins
[Verizon Samsung Galaxy S III] Hobart!:
Do I just create a file called .nomedia?
[Verizon Samsung Galaxy S III] jlyle:
Are you comming from R147 ? also sounds like an incomplete download .. check or RE-DL again
[Verizon Samsung Galaxy S III] eueyj:
R155. Mine also boots into landscape but reverts to portrait after a few seconds. Haven't found any large bugs however I have a couple of questions.

I realize that the Stock Camera has been replaced with the Note 2 Camera on this. Are the extra Note2 features like Best Face etc going to be added? I'm not overly concerned but I'm pedantic with software and not having bugs. After all it's what I do for a living ;). No rush on this either I just really wanted to know whether this would be in future plans or not.

Other than that everything seems to be running well. Will get more of a chance to play around in the next few days...
[Verizon Samsung Galaxy S III] michaeldizzowns:
i have spent more time then flashing roms then useing them. haha however i have never dirty flashed.

clearly what im doing is not working no matter what i try.

coming from clean rom, i enter clock work mod.

i wipe sys/factory reset

wipe cache

wide dalvik

install 147

after i install i go to wipe cache

wipe dalvik cache

install 155

rootboot system now

choose not to flash stock recovery

it boots to the boot animation and just stays in boot loop.

can anyone help? possibly incomplete file download?
[Verizon Samsung Galaxy S III] xxaimbkstarxx:
Lag?

Ive noticed a lag on pressing the homebutton it takes like one second to recognize the button press.
[Verizon Samsung Galaxy S III] Amphibliam:
I have found that even with Lean Kernel, this ROM is quite sluggish. I'm going to try a different kernel and report back. I'm surprised by the amount of lag because it seemed so fast initally.
[Verizon Samsung Galaxy S III] jlyle:
Let it boot once after flashing 147 .then procede with the rest of your steps... should be good to go
[Verizon Samsung Galaxy S III] TheBurgh:
Where can we find ziggy's kernel if we flash something different and want to flash back
[Verizon Samsung Galaxy S III] jlyle:
In the OP ..or here

http://projects.ziggy471.com/projects/ziggy471-sgs3-jb/files

the one that came with Rom is not on his site
[Verizon Samsung Galaxy S III] DieselNY:
I still have this issue no matter what. After I plug the phone in overnight the it goes away but the second I change batteries or reboot it stars allover again as if the stats were reset. Many say its related to the massive blob files in CWM...if I was to ad a .nomedia file to the blobs folder would that cause any issue with macking nandrods and restoring from a nandroid?
[Verizon Samsung Galaxy S III] streetracer8605:
R147 gave me amazing battery life. The only bug that I found bothered me was having to turn on GPS in order for Maps to find me. I dirty flashed R155 today, and the location bug is still there, but that's the only bug I've found so far. The split screen for the apps is just awesome. Obviously I can't gauge battery life yet, but I've yet to have my phone run hot on any of the included kernels. I've occasionally had the media drain at first with a few of your roms, but that always stopped. I like to give about 3-5 charge/discharge cycles to really get a feel for battery life and rom performance. Your roms have been my favorite, and the smoothest. It would just be great if the location would worth with agps as opposed to having to have gps on.
[Verizon Samsung Galaxy S III] mikeman45:
Once you install 147 let it sit for 5 minutes then reboot once before you go to recovery and only wipe dalvik before you install 155.
[Verizon Samsung Galaxy S III] michaeldizzowns:
i swear i tried this. haha oh well. thank you.

worked great.
[Verizon Samsung Galaxy S III] Stam2000:
Everything had been running great except for Bluetooth. It's connected but get no sound

Sent from my Synergized Verizon GS3
[Verizon Samsung Galaxy S III] MrBrady:
I had a location bug on both builds as well. Although I don't think it's really a bug. I think it's a PDroid setting. I downloaded the recommended PDroid app and long-pressed on Google Search, Maps and Network Location Services and told PDroid to allow all (trust?) these apps. After that, and setting Google Location to On (in Settings) and Allow (in Accounts), location services worked fine.
[Verizon Samsung Galaxy S III] Hobart!:
You have to boot 147 first.you can't flash 1 then the other...boot 147...maybe setup and login.... Then dirty flash 155 over 147

Ninja'd..lol
[Verizon Samsung Galaxy S III] jlmr731:
With 155 Bluetooth headset does not have any sound on phone calls but i do have media sounds.

---------- Post added at 07:12 PM ---------- Previous post was at 07:11 PM ----------

On another note anyone having problems with Ziggys kernel, now not sure if he has done any under-volting BUT

On imoseyon kernel thread there has been posts on this

you can find your pvs type by

Im just curious if this has anything to do with some having no problem with ziggys kernels and others are seeing all kinds of problems.
[Verizon Samsung Galaxy S III] dave_k605:
How do you enter multi window?

Found it, awesome builds do far!

Thanks e
[Verizon Samsung Galaxy S III] keymaster911:
uploading now.. r155.. this will be glazed over with some heinz 57 love tonight.. ;)
[Verizon Samsung Galaxy S III] ChrisNee1988:
Long press the back button and pull out the tab that shows up
[Verizon Samsung Galaxy S III] Amphibliam:
Honestly, this ROM seems awesome, but I need bluetooth audio, speed, and reliability. Not to knock this ROM, but those are 3 things it currently lacks for me. I'm sure, as eschelon has said, the next build will be MUCH more stable, so I'll be back then. :) Nice job on multiwindow, definitely a cool functionality!
[Verizon Samsung Galaxy S III] radrider664:
I'll 2nd, this stopped working for me; too
[Verizon Samsung Galaxy S III] Weioo:
Hm...My phone seemed to have randomly lost sight of my external SD card. I have a class 10 32GB SanDisc HC in there... I'm confused. Did my SD card just die or something else happen? I've rebooted the phone and everything, it can't find the sd card. I'm about to pop it into my laptop and see if I can see it. Will edit post.

Update: Took out micro-SD, placed in laptop and it wouldn't show up. I think it died? Damn...I just got that sucker a couple months ago. I just started saving my Nandroid backups to it and flashing quite a few times...Did I over-work the card? Is that possible???

Edit: Yeah, apparently microSD cards die quite often....Well that's something disappointing I learned today.
[Verizon Samsung Galaxy S III] ryan1977:
Not sure what's up but everything works for me, just tested Bluetooth audio on my samsung home theatre and I works flawlessly!
[Verizon Samsung Galaxy S III] knifedroid:
Got this after running some things in multi view:

Sent from an overpriced Verizon tower.
[Verizon Samsung Galaxy S III] mchaos:
Sorry, thought it would be understood that I meant the fix for google wallet to work. NFC works fine, but in order to get google wallet to work correctly you need to flash a google wallet fix. Would be nice if it were cooked in with google wallet, and a build prop with the proper changes as a bak file that you could rename, so you can go from the right build props, to ones to register a credit card and back again...
[Verizon Samsung Galaxy S III] Aquila76:
Odd. S Voice is the only thing that launches (never asked me what I wanted to use) and the 'Clear default' is greyed out. Is there another way to remove this?
[Verizon Samsung Galaxy S III] michaeldizzowns:
ROM is gulping my battery away like no tomorrow. :(

Painfully waiting for ROM to settle down see what real performance I get

Sent from that young galaxy S3
[Verizon Samsung Galaxy S III] jlyle:
Give it time to cool / settle / and a charge cycle . it will improve :cool:
[Verizon Samsung Galaxy S III] prdog1:
Can try removing it from button by unchchecking the double click in S-Voice settings. Then open app in drawer and recheck it to re-enable button. :cool:
[Verizon Samsung Galaxy S III] cr4ck3r4lif3:
Yes. Should look like this:
[Verizon Samsung Galaxy S III] cr4ck3r4lif3:
I have the .nomedia file in the clockworkmod folder. That covers everything in this folder including the blobs folder
[Verizon Samsung Galaxy S III] Amphibliam:
So, let's make a comprehensive bug list:

-Bluetooth audio

-feels sluggish (may just be me or the kernel), especially in the widgets drawer and in settings, but I noticed with both Ziggy and Lean

-double tap for google now

-random reboots with Ziggy kernel

-weird orientations on boot

-some apps have a weird bar across the top in multiwindow like FB and FB Messenger

-some force closes with weird text after using multiwindow

-couldn't get Wallet to initialize after using the fix

-acore fc's

-lockscreen torch automatically shuts off

Anything else?
[Verizon Samsung Galaxy S III] TheBurgh:
Much appreciated
[Verizon Samsung Galaxy S III] keymaster911:
is it just me or does this r155 takes for ever to upload
[Verizon Samsung Galaxy S III] ChrisNee1988:
Upload or download?
[Verizon Samsung Galaxy S III] keymaster911:
download.. been up for the last 22hrs at work sorry
[Verizon Samsung Galaxy S III] jlyle:
5 minute Download here :):cool:
[Verizon Samsung Galaxy S III] keymaster911:
I think I just had a bad download.. because my tablet downloading it now.. in like 2 mins..
[Verizon Samsung Galaxy S III] Hobart!:
I created a new file and named it.nomedia and just put it in root of internal and external SD....is that what I do? Or do I create a folder and put file in it? I think I do first one but you ss shows permissions as rwxrwxr-x... I can't get mine to change from rwrr...am I doing it right?
[Verizon Samsung Galaxy S III] Aquila76:
Thanks, but it still isn't working. I'm not getting prompted to choose between S-Voice or Google Voice Actions. If I uncheck that box in S-Voice, nothing happens when I double-tap, and the 'clear defaults' is still greyed out. I set it back, double-tap, and S-Voice launches; 'clear defaults' still greyed out..

I was able to choose back on my r147 install, but not on r155 (I wiped to stock BLK3, loaded Ziggy's exFAT TWRP recovery, rooted & un-bootlocked, flashed r147, booted to OS, then flashed r155).
[Verizon Samsung Galaxy S III] prdog1:
Sounds like another thing broke on this build. :cool:
[Verizon Samsung Galaxy S III] BraddahBoi808:
I'll just leave this here :)

Great work Team Synergy! First time back since the ICS releases, decided to give this a try and BAM! New daily. Awesome work
[Verizon Samsung Galaxy S III] cr4ck3r4lif3:
I wouldn't put it in the root directories because you want the system to scan certain folders. I have folders full of roms, mods, tweaks that are huge that I want to keep hidden.

I don't think permissions matter but when I created another .nomedia file, the permissions were rwxrwxr-x. I believe you can only change permissions on system files
[Verizon Samsung Galaxy S III] thornev:
Rats. I can't have the same app in each of the multi windows. That would be great for a file manager app.
[Verizon Samsung Galaxy S III] Aquila76:
Not a biggie; long-press on Menu then saying 'Google' still works. Killing the double-tap cow is worth it for the multi-window steak. :laugh:
[Verizon Samsung Galaxy S III] jlyle:
Solid Explorer will :cool:
[Verizon Samsung Galaxy S III] prdog1:
If you have the Google search bar widget on homescreen you can also click on mike and go straight to voice search.:cool:
[Verizon Samsung Galaxy S III] Ryezen:
Not Bluetooth Music, Bluetooth Audio. Try making a phone call via Bluetooth, whether over your home theater system or otherwise. You won't be able to hear anything, even the phone dialing. Music works fine, just phone audio is broken over Bluetooth.
[Verizon Samsung Galaxy S III] bedroc:
Great work fellas......

I am having a bit of trouble with my regular voicemail.. when putting in the password Verizon must not be hearing the tones. Is there away to change the setting so the password is heard? Or do I just need to reflash?

current rom 147 then dirty flashed 155

Thanks
[Verizon Samsung Galaxy S III] keymaster911:
ITry this new ROM. To many bugs. I Just wait till you guys have the bugs figured out.. Thanks for sharing your hard work..

Sent from a slamming S3