yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] andybones:
If you have root explorer, please use that.

If not, then I *think* root tool box is like the same .apk

what you want to do is:

1) go to an .apk that will let you delete files and move them from system

2) so go into that .apk

3) go to system

4) copy the app folder to your SD-Card/ or Internal storage by long pressing the app folder and selcting "copy" (make sure not to "cut" or move the folder, only copy)

5) copy the folder to SD-Card/ or Internal

6) pull the app folder from SD-Card/ Internal onto cpu, or upload it to like dropbox for me and I can diff you apps against what I have :)

also let me list my downloaded .apks (I don't have too many of these either)

Adobe reader, adobe flash bank of america, cachecleaner NG, dictionary.com, Galaxy S3 Task manager shortcut, gmail, google play music, JB 4.2 keyboard, maps, post star, street view, supersu, the weather channel, tiny compass, and youtube.
[Verizon Samsung Galaxy S III] andybones:
thanks again brother!
[Verizon Samsung Galaxy S III] jlokos:
On all roms I flash (both TW and AOSP), I change animations down to .5x and uncheck force GPU rendering. I don't know who to give credit for this. I think I first read about this on the synergy thread, but I know sbreen, hero and others also recommended this. I can't tell if it is one or other since I always do both.
[Verizon Samsung Galaxy S III] andybones:
Perfect, your input has been highly appreciated!

Thank you.
[Verizon Samsung Galaxy S III] prdog1:
Has to be hacked back in. That is the first and most asked for mod there is. It is gone by default on S4 4.2 I believe. Long press Lidroid wifi toggle and will send to same place. :cool:
[Verizon Samsung Galaxy S III] jlyle:
Everyone hated it so it was taken out.. Just hold wifi toggle for 2 seconds :cool:
[Verizon Samsung Galaxy S III] prdog1:
NINJA'd :p:laugh::cool:
[Verizon Samsung Galaxy S III] jlyle:
:banghead::banghead::banghead:
[Verizon Samsung Galaxy S III] wpcprez:
Cool that works for me. I think the last issue I have is my mms wont send when on 3g. Anyone else have this issue? It just says sending..... and I do see the 3g icon but no dice.
[Verizon Samsung Galaxy S III] prdog1:
AOSP or TW messaging. I have no clue. I have to drive 50 miles to get 3G handoff. :cool:
[Verizon Samsung Galaxy S III] wpcprez:
The tw regular mms app. Will try to install asop right now to see if that works.

---------- Post added at 07:37 PM ---------- Previous post was at 07:19 PM ----------

Ok neither work.. but 3g data seems to work fine. Strange....
[Verizon Samsung Galaxy S III] prdog1:
I only use TW but have no way to test 3G. May need to reflash. :cool:
[Verizon Samsung Galaxy S III] wpcprez:
tried reflashing from scratch again and still no go. Restored my stock rom and all is well with MMS on 3G. Strange....
[Verizon Samsung Galaxy S III] prdog1:
Search this thread. The fix is in here. Seen this one before. (no MMS on 3G) is good place to start. :cool:

---------- Post added at 11:48 PM ---------- Previous post was at 11:39 PM ----------

I found this one. I have never had a problem. :cool:

http://xdaforums.com/showpost.php?p=44208897&postcount=4718
[Verizon Samsung Galaxy S III] wpcprez:
thanks, i did see that but it didn't seem like he found his solution. I wonder if he was on 3g for some reason and he wasn't working and then 4g started working again and so did his MMS? no idea... I flashed my stock backup just to make sure I wasn't being crazy to be sure I could MMS from there on 3G.
[Verizon Samsung Galaxy S III] prdog1:
I read it as worked. It is a modded MMS to begin with so Blocking mode works. If you have it enabled may need that option. I never use blocking mode so I guess mine has always worked. Worth a shot. MMs will work on any data connection even 2G. Just has to be data for MMS :cool:
[Verizon Samsung Galaxy S III] wpcprez:
This might be totally my fault. I just noticed I am on mb1 and this is an mf1 rom. Maybe that is it?
[Verizon Samsung Galaxy S III] james:
i have a couple of questions does dlna work on this rom and if so do i install it like any other rom wipe cache and dalvik system format wipe data
[Verizon Samsung Galaxy S III] HypostaticOnion:
Well it's stock based, so if stock supports it, this should as well. Also, yes all ROM flashes are the same unless otherwise stated in the op.

If I've helped, please hit the thanks button
[Verizon Samsung Galaxy S III] Comp625:
Dumb question:

I am tempted to swap out the Stock S3 Lockscreen and replace it with the S4 Lockscreen (which was an option in AROMA).

Am I correct in remembering that I can simply go back into AROMA and swap out this (and any of the other customizable elements)? If so, how do I go about accessing AROMA?

I think it is Recovery > Install > choose the zip file on SD card. However, I am nervous about accidentally flashing the entire ROM and screwing things up.
[Verizon Samsung Galaxy S III] Thebear j koss:
Just flash and change the mods you want to change. Just don't do a factory data reset or wipe data. Recommend wiping dalvik cache. :cool:

THEMER- the stupidest thing ever to have users add widgets to their homescreens since UCCW and Zooper.
[Verizon Samsung Galaxy S III] wpcprez:
so I flashed the BR1 and it all works fine as well as MMS. Then flashed bonestock back on and no MMS again. it just sits there trying to send.
[Verizon Samsung Galaxy S III] jackdubl:
It is? Is this only in 3.4? I couldn't find it in any of the changelogs.
[Verizon Samsung Galaxy S III] HypostaticOnion:
That option is not in this ROM. You're either posting in the wrong forum, or looking at the wrong ROM on your phone. This is purely stock, with simple mods and slight theming.

(simple as in nothing super hefty that would affect performance by slowing stuff down)

If I've helped, please hit the thanks button
[Verizon Samsung Galaxy S III] Comp625:
I was mistaken and confused. S4 Lockscreen is NOT included of this ROM. I apologize for the confusion!
[Verizon Samsung Galaxy S III] MIKEYSAKZ:
What's up Andy hope all is well brother thanks again for all your hard work this thing you made us is a beast.
[Verizon Samsung Galaxy S III] ruinertt:
andy,

I'm running v3.3 and have the time zone issue with received SMS messages being out of whack with the Samsung messaging app. I traveled from EST to PST time zones and received messages (as seen in posts in this thread from earlier this year) that were three hours off (they were still on EST). When I used the generic Android messaging app, the times were correct. However, the generic Android messaging app breaks the AOSP lockscreen shortcut for messages (I even tried to rename the .apk it to whatever the name was for the samsung messaging app - still hung up on the AOSP lockscreen). I know that the shortcuts for the AOSP lockscreen are hard coded and the links for your "test" messaging client many months ago are no longer working...was there ever a fix for this issue?

I tried searching and couldn't find anything definite. I can assure you that the time zone problem is an issue, however. The Samsung SMS client is the one that has the "group" messaging mod in it if that helps.

With that said, your ROM is rock-stable...I have uptimes in excess of 30-60 days (if I don't have to power off while traveling that is).
[Verizon Samsung Galaxy S III] MIKEYSAKZ:
Reflash the rom and choose hour Aug fix text message I only run that one and works perfect
[Verizon Samsung Galaxy S III] ruinertt:
I remember seeing that there were two problems with the SMS - an "hour off" issue and then a time zone issue. This fixes the multiple time zone issue as well?
[Verizon Samsung Galaxy S III] MIKEYSAKZ:
Brother I have seen even recent releases of multiple roms with mms /SMS and I always flashed hour bug and never had any problems you should be good
[Verizon Samsung Galaxy S III] ruinertt:
I renamed the original TW sms .apk, ran the Aroma install again and did a "modify" over the top of it with the "1 hour" TW fix. It installed the new one in its place. I fly to Los Angeles tomorrow morning, so I guess time will tell if this works or not. :)
[Verizon Samsung Galaxy S III] Adamsaudio:
This app worked for me

https://play.google.com/store/apps/details?id=com.mattprecious.smsfix

I only needed it for a week when I was traveling for work, and didn't want to flash anything on the phone while on the road away from my computer.
[Verizon Samsung Galaxy S III] ruinertt:
Understood, but I didn't want to mess with yet another "bandaid" program so to speak.

I did a complete CWM Backup before I did the Aroma flash modify. I figured that if it somehow messed things up. I could return it to what it was 10 minutes previous give or take.
[Verizon Samsung Galaxy S III] wpcprez:
Anyone else have an issue with AdvancedS crashing when you make a phone call? Mine does but I just hit OK and everything is back to normal.
[Verizon Samsung Galaxy S III] :
can anybody help with mms? I know it has been answered how to fix mms over wifi but search is down!
[Verizon Samsung Galaxy S III] prdog1:
Turn on data. MMS won't go over wifi without data turned on. :cool:
[Verizon Samsung Galaxy S III] :
Thanks but wasn't there a build prop edit tht fixed mms?
[Verizon Samsung Galaxy S III] prdog1:
Believe there has been an edit in the past but was probably a smali edit. It is not in this rom. :cool:
[Verizon Samsung Galaxy S III] wpcprez:
ok I fixed this by turning off the GPU rendering of 2D in developer options. I'm surprised nobody else had the same issue
[Verizon Samsung Galaxy S III] bob24260:
I would like to thank the dev for all his hard work on this.I normally flash 2-3 times a day,but this morning I installed this and ran it all day and its given me tremendous battery life.I run my devices hard,netflix,shadowgun,etc,etc and this Rom has held up really well.

Excellent work.
[Verizon Samsung Galaxy S III] jloaiza:
Any word on 4.3?

OK i have to confess I relapsed with my crack flashing. I went over to the darker side for a quick taste of 4.3, very impressed but quite honestly at least for me I keep coming back to BoneStock there really is nothing out there like it. I feel some what spoiled thanks to Andy, I now hate having to configure everything via a ROM controller within settings. I also prefer the Samsung TW feel and look over CM. I'll stick with BS 3.4 running as is running smoother than ever. Thanks again Andy and all of you who help and have helped me out many at times.
[Verizon Samsung Galaxy S III] ayush20m:
I have long been a fan of CM but the instability always bothered me. It prompted me to look around and I am glad I discovered this ROM. I wish the default android phones would come with this kind of customization. I'm yet to finish the installation but I love it already. Will post more after playing around a bit.
[Verizon Samsung Galaxy S III] david_hume:
Andy, do you plan to make a build with the 4.3 update when it comes out? It's releasing next month!
[Verizon Samsung Galaxy S III] TokedUp:
Oh how I wish a certain Mr Bones makes a 4.3 ROM when it rolls out. I might actually come back to TW!
[Verizon Samsung Galaxy S III] prdog1:
You have to be disinfected first. :p:laugh::cool:
[Verizon Samsung Galaxy S III] SilverFox66:
I love this ROM, and have had nothing but great battery life with it.

I do have a couple small issues though, and after some searches and reading, couldnt find an answer.... so posting them here.

1 - no matter what I do or what settings I apply.... I cannot get the mic icon on the samsung or google keyboards. I am running 3.4 with no mods, and have the samsung, google and go keyboards installed, as well as google voice. Even with the google keyboard/google voice.... the button wont show up when checked to do so. Same way with samsung keyboard/svoice. The only way to get the mic to show up on the main keyboard is for me to use the go keyboard/google voice combination. If I use svoice with go keyboard, the mic button is there, but svoice wont work (not nec a ROM issue... just stating for an FYI thing). any idea on how to get the mic button on the main keyboard screen for texting etc?? I used to love the Go apps.... but they are nothing but huge ad machines now. I need to get the voice button to show up on my other keyboards, so I can uninstall the go keyboard

2 - It takes forever and several reboots, for the missed call notification on the lock screen.... to clear itself. I can have a missed call, pick the phone up and see the #1 on the green phone icon on the home screen, unlock the phone, and clear the notifications.... lay the phone down.... and when I pick it up again, it will have the same notification on it. Sometimes when I reboot the phone, I will have a notification show up that I cleared a day or 2 previously. Is there something I need to do, to make sure the notifications clear properly, when I tell it to clear them?

Thanks and keep up the great work
[Verizon Samsung Galaxy S III] athlonxp2300:
1- do you have google search installed?

http://xdaforums.com/showthread.php?t=2439411

2- for me opening the phone app for a second clears it.
[Verizon Samsung Galaxy S III] SilverFox66:
If youre referring to Google Voice Search, yes it is installed, and as I said.... works fine with the Go keyboard, but nothing else

Thank you, I will try the phone screen suggestion. Although, that seems like a workaround, not a fix
[Verizon Samsung Galaxy S III] prdog1:
Clearing the notification clears the dropdown notification only and not the missed call notification. Must open the phone app to clear missed call. Clicking the notification opens phone app and clears both notifications. The notifications are independent from each other. It is same on all TW roms. :cool:
[Verizon Samsung Galaxy S III] andybones:
Hey guys, limited time here, if I have to choose between s3/s4, I am keeping the s3 and dumping s4..

so, yes to 4.3 :)

I MAY keep my s4 and also provide a 4.3 ROM for them, but honestly I want to sell it and try out the moto X.

can't wait for 4.3 to drop for us. )
[Verizon Samsung Galaxy S III] SilverFox66:
Gotcha... and thank you! I had no clue they were separate. I figured hitting the clear button would clear it everywhere. Learn something new every day. Now, if I can get my voice search figured out lol
[Verizon Samsung Galaxy S III] prdog1:
Yea. 4.3 will tide me over for a while. Can't port ATT leak over as don't have modem and resources on most APKs are incomplete. Can't recompile most APKs with any APK tool. :cool:

---------- Post added at 12:28 PM ---------- Previous post was at 12:24 PM ----------

Must have Google Search (GNow-Not included with rom) and Google TTS enabled for mic to show up and work.:cool:
[Verizon Samsung Galaxy S III] M_T_M:
waiting already :eek::silly:
[Verizon Samsung Galaxy S III] wolfballz:
Can't wait for more awesomeness
[Verizon Samsung Galaxy S III] SilverFox66:
as far as I know, they are installed/enabled. as Ive said, voice shows up/works on the Go Keyboard, but not samsung or google keyboards. If these werent installed/enabled, and that was the issue, then voice wouldn't work with the Go keyboard, correct?
[Verizon Samsung Galaxy S III] prdog1:
Go only needs TTS as rest is built in since it has to work on any device. Doubt it is Google Search dependent. Are both these settings enabled. :cool:
[Verizon Samsung Galaxy S III] SilverFox66:
Yes, they were.... BUT...

TTS was set to Samsung. I changed it to Google, and now I have my mic button showing up and working on all keyboards. Dont know why it wont work with Sammy, but at least it is working now. Thank you :good:
[Verizon Samsung Galaxy S III] prdog1:
No problem. Glad it is working. Google TTS is better anyway. :cool:
[Verizon Samsung Galaxy S III] studpuppy102:
Andy is my hero!
[Verizon Samsung Galaxy S III] reslor1:
Under language and input, do you have google voice typing checked?
[Verizon Samsung Galaxy S III] prdog1:
I fixed him a few hours ago. :D:cool:
[Verizon Samsung Galaxy S III] reslor1:
sorry, i missed that :rolleyes:
[Verizon Samsung Galaxy S III] prdog1:
No problem. It happens all the time. By posts looks like you are new here and welcome. Read the OP first. Then when a post you want to reply to read everything below it. I learned by reading every post in a thread before I would even flash it. My record was reading 1000 posts before flashing the rom. Takes a while but learn a lot that crosses over to all roms and devices. ;):fingers-crossed::cool:
[Verizon Samsung Galaxy S III] TokedUp:
Great news Andy. Keep us posted.
[Verizon Samsung Galaxy S III] Nomad1600:
In AndyBones we trust. :thumbup::D
[Verizon Samsung Galaxy S III] jlyle:
Cmon PRdog :D
[Verizon Samsung Galaxy S III] timofcourse:
Hi all

I recently loaded this ROM and while its working great for the most part, I have run into a couple issues. Apologies if these have already been reported.

The first is related to the roaming notification. When this pops up in the notification center, hitting it crashes the android phone process. The other is that hitting the Weather lock screen option (Im not using AOSP lock) causes Settings to crash.

Thanks!
[Verizon Samsung Galaxy S III] david_hume:
I never had these issues when I ran this ROM. Try to wipe cache, dalvik cache, and then fix permissions. Report what happens.

If that doesn't work, then try to reflash the ROM.
[Verizon Samsung Galaxy S III] prdog1:
I agree. Sounds like dirty flash and fix permissions may help for a while. Never know what else is broke till run into it. Fix permissions does nothing for a clean flash. Only works to fix broken UIDs from dirty flashing from noncompatible base or noncompatible app data backup. I never use it but I always clean flash. I wipe till she cries and squeaks. :cool:
[Verizon Samsung Galaxy S III] david_hume:
I usually don't dirty flash either. I'm always a clean flashing person, which is why I generally don't have any issues in any ROM I run other than what the dev posts I'm the bug section.
[Verizon Samsung Galaxy S III] prdog1:
HaHaa. That the name of the game. On MikRoms all roms wiped whether you wanted to or not. We had no issues that everyone didn't have. Dropped the size of threads and time trouble shooting dramatically. I have flashed thousands of times and never used fixed permissions except when testing patched ports. :cool:
[Verizon Samsung Galaxy S III] Juice3250:
It seems the bigger the size of thread, the more people you find who have dirty flashed or not followed the instructions given.
[Verizon Samsung Galaxy S III] timofcourse:
So if you use the normal swipe lockscreen you both are able to access the Weather settings? I just redownloaded and reflashed and still have this issue.
[Verizon Samsung Galaxy S III] prdog1:
Works here. I have been able to break it before but don't remember how. Think it was some theme mod I was doing. :cool:
[Verizon Samsung Galaxy S III] david_hume:
Always was able to access it. Sadly, I can't show it because I'm on an AOSP ROM.
[Verizon Samsung Galaxy S III] timofcourse:
What qualifies as a "dirty" flash? I use the TWRP "factory reset" prior to every ROM install which is supposed to wipe data, cache and dalvik.

Beyond the wipe, I downloaded the BoneStock zip from the main download link and copy it to my phones external SD card before the install.

There something beyond this that should also be done Im missing?

Thanks.
[Verizon Samsung Galaxy S III] prdog1:
Recommend wiping system also. That is where the old rom is. Especially if coming from AOSP base. :cool:
[Verizon Samsung Galaxy S III] timofcourse:
Wiped system, data, cache and dalvik, reinstalled and still having the crash issue when selecting weather under the lock screen options.
[Verizon Samsung Galaxy S III] prdog1:
Don't know. I flashed it clean just to test it and mine worked fine. :cool:
[Verizon Samsung Galaxy S III] timofcourse:
So I just did an md5 check and found its not matching what it should be. Ive downloaded 3 times from the "main" link and get the following as the hash instead: 0A104A8580BBB0FCDBECF8F2543D2E91. Any chance this could be causing the issue?

I kicked off the download from the mirror but its taking hours to complete. Any chance someone could download the main download and verify the md5? Anyone know of another download link to try?

Thanks!
[Verizon Samsung Galaxy S III] prdog1:
MD5 you are getting looks right. The one in the OP is bad. :cool:
[Verizon Samsung Galaxy S III] timofcourse:
Ah crap. And here I thought I finally had an explanation as to why this was occurring....
[Verizon Samsung Galaxy S III] 5ft24:
Are you loading any themes etc?
[Verizon Samsung Galaxy S III] skyss07:
Is it ok for this rom to flash the KT747 kernel?
[Verizon Samsung Galaxy S III] david_hume:
Yes
[Verizon Samsung Galaxy S III] Mystique:
I get a ton of bizarre wakelocks with kt..

Find the dkp kernel.

Has a custom "freelunch" governor..

Simply amazing..

17 hours of phone life, trick or treating with the kids (walking around three hours) about 30 pictures, 60 sms, 10 mms, 45 minutes of phone, 20 minutes of waze gps..gtalk (not hangouts) with the wife all day..

Had 45% LEFT when the night was done.. Stock battery..

Dkp, freelunch..

No one ever cleans out the modules directory when they start flashing kernels, or keeps track of what is in init.d..

Then they have random complaints about things in the future..

Don't be that guy..

If the dkp kernel thread isn't interesting enough.. Find the lean kernel thead..

That is another one that does not cause a million freaky wakelocks..

Dkp has frandom() so if you are using crossbreeder they will fight to make entropy..

Hope this helps.
[Verizon Samsung Galaxy S III] skyss07:
oh, thanks for the suggestion man.
[Verizon Samsung Galaxy S III] david_hume:
Just make sure to flash the 4.1.2 kernel because he has AOSP kernels as well.
[Verizon Samsung Galaxy S III] skyss07:
I'm using it now and observing it. Thanks for the suggestion
[Verizon Samsung Galaxy S III] Mystique:
Tethering..

Looks like it needs to be enabled via the lidroid menu toggle..

Using the built in vzw..

Trevor mod never worked for me.

Not looking to tether the constantly.. just the random occasion.

Is the lidroid toggle the only way?

Or simplest way that works?

I'm one of those unlimited data people, which I understand is a problem, but I never understood why..

Thanks in advance.
[Verizon Samsung Galaxy S III] prdog1:
Toggle is always the easiest way. Verizon just hijacked your native tether. Toggle accesses at framework level. The Verizon app is only a skin on top of the framework. Not a real app. Toggle accesses from framework and bypasses the overlay. We can hack the whole thing and make work in settings but all app MultiWindow breaks it so requires another hack so no reason to hack. Not worth the trouble. I run 20GB/month or more on the Lidroid toggle. We are working on hack for 4.3 now. if want to and feel better using the app the TRev mod is outdated. The original Android Tether app Trevs is based on has been updated and available for JB. Trev built when was not compatible with JB. :cool:
[Verizon Samsung Galaxy S III] Bleezyd:
So when I downloaded the file, it says 3.4 version but when I look on my phone it says version 3.3. Is this just something the dev did not update? I am running the 3.4 version if I dowloaded it on 10/29 and the file says 3.4, right?
[Verizon Samsung Galaxy S III] M_T_M:
Not trying to be a pompous jerk about this but...if you search this thread you will see that the OP did not make the release number change on ROM but it is indeed 3.4 :p:silly:
[Verizon Samsung Galaxy S III] david_hume:
Edit the build version in build prop and your problem will end. Andy mentioned that he forgot to change the version number when he made 3.4
[Verizon Samsung Galaxy S III] Mystique:
Someone should make a sed script that changes that for people.. s/water/wine

;)
[Verizon Samsung Galaxy S III] prdog1:
Only takes edit the Buildprop and put in a flashable. That we leave to the rookies. Not worth our time. That is Buildprop101. :p:laugh::cool: