yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] andybones:
Let's not forget blocking mode and call/msg block :)

The problem with all of us DEVs sharing, is that our ROMs are going to be pretty much 90% identical.

(just look at changelogs, one new MOD comes, we all add it)

theming is a big aspect of differences, the main reason CleanROM is/was such a hit is because it's a simple ROM.. plain and simple, nothing "special" about it besides the fact that Scott was a very attentitive DEV, and did a great job at giving the users what they wanted and doing it with a very timely fashion.) it's basically taking the base, and adding Aroma to it to remove bloat and a few tweaks. Problem I had with that, was that I was doing all the theming and adding in all the MODs and getting really no credit (well not any as a Developer), which is why BoneStock ROM was formed.

Since all us DEVs share (which we should) our ROMs will be very close, but we all have oue own little tweaks and things we like to do.

me personally?

STOCK, STOCK, STOCK. I don't mess with the kernel the init.d scripts, and barely touch the build.prop.

Why?

because I have found that many of those things are just meaningless and or actually interfere with something and slow the ROM down.

Also, this leaves the user the option to edit the ROM if they want to play with build.prop tweaks, initi.d scripts, etc, to see what works best for THEM.

I like to give a stock base, and add in MODs that I KNOW work, and don't slow the ROM down at all.

also bringing back some of those features Verizon worked so hard to take away from us was a great accomplishment, (even though other DEVs got a little jealous, but that's not for a public post.)
[Verizon Samsung Galaxy S III] M_T_M:
So many variables on your post mate.

Bad antenna, network being revamped in your area, not allowing enough time for phone to update the signal around you....

********_***********

LA CALACA, TILICA Y FLACA!! :eek:
[Verizon Samsung Galaxy S III] andybones:
try updating your PRL.

lame but ya never know.

power down, take out battery.

remove SIM card for 2 mins, and put back in and boot.

Nothing in this ROM would hurt your signal.

It is dependent on where you live, IE how good signal you get.

The good network you get IE 3g/4g (if you are using it)

the modem = aka = radio can work great for one phone and terribly for the next, you need to experiment.

As M_T_M mentioned, too many variables
[Verizon Samsung Galaxy S III] prdog1:
I live in Houston and have done every upgrade and update that can be done to make sure they are safe and work. All good here since preorder release. Wipe, Wipe, Wipe. Mr Robinson has one of the easier root and upgrades but it is like 6 months old. Off top of my head his last one was MB1 which is good if upgrade back to MF1. Sounds like you are behind the curve. :cool:
[Verizon Samsung Galaxy S III] Nnyan:
Was on CR for the longest time. Installed all the BS 3.X and loved it but my battery life was just not good (complete clean wipe x3. Inc internal card. Multiple discharge cycles no mods or themes).
[Verizon Samsung Galaxy S III] prdog1:
Must not have done a clean wipe or restored a rogue app. I been on BoneStock testing and I still only lose about 3% while I sleep. Clean wipe is system/data/dalvik and cache. If restore all app with data it is no longer a clean wipe/flash. You just restored your problem. Battery life on this rom is comparable to CleanRom as they are same base. The difference is what you install. :cool:
[Verizon Samsung Galaxy S III] Thebear j koss:
Back to tibu restore again. I agree it's a great app but I think it's being misused...

Enough with the updates Google!
[Verizon Samsung Galaxy S III] prdog1:
Yup. I use it but never restore dirty data. App only. ;):cool:
[Verizon Samsung Galaxy S III] prdog1:
I'm right in the middle of 4G area and mine has always shown 3 bars max. That is about normal from what I have seen. The bars are never accurate. Should go by dBm value in about phone/status. Mine currently shows -98 dBm with 3 bars inside house. -98 is good for my area. usually between 100-105. Never see more than 3 bars and signal strength same on all roms. Rom doesn't affect signal strength unless on AOSP rom and will be lower due to home made RIL. . :cool:
[Verizon Samsung Galaxy S III] CeeMillz:
This might have been asked but driving to a job in the work truck makes it a little hard to search. I reflashed 3.3 clean 3 separate times and still have the same issue, data works fine but when I send a text message it automatically gives me a failed notification. I know its not the download file because its worked fine the first time I flashed. Any thoughts?
[Verizon Samsung Galaxy S III] M_T_M:
I get the same issue but at the office mate.

I don't think is ROM related since it happens to me with other ROMs also...err....no that I use any other ROMs :eek:

/me looks around for [MENTION=2586080]andybones[/MENTION] with shifty eyes :eek::D:sly:

********_***********

LA CALACA, TILICA Y FLACA!! :eek:
[Verizon Samsung Galaxy S III] andybones:
What's the issue guys, on phone, lazy today, don't wanna search.

I know.. I know.
[Verizon Samsung Galaxy S III] uber_mike:
Off topic of any issues, I just wanted to mention I've been running bonestock v1.4 since it came out and havent had a reason to upgrade because it works so great.

Thanks andybones :)
[Verizon Samsung Galaxy S III] MIKEYSAKZ:
Which messaging choice are you using touch wiz or aosp or the touch one hour bug fix version cause that's the one I use and honestly never a failed message to date
[Verizon Samsung Galaxy S III] CeeMillz:
Tried everyone, just ODIN'd back to stock root...no dice. This is so annoying...data is working fine texts just wont send.
[Verizon Samsung Galaxy S III] MIKEYSAKZ:
Did you run AOSP at any point and if so you should maybe consider a format ofyour internal memory
[Verizon Samsung Galaxy S III] CeeMillz:
I actually did, was giving 4.3 a run but i'm gonna try that now. If not i'm gonna upgrade to the One or s4 =/

---------- Post added at 08:09 PM ---------- Previous post was at 07:47 PM ----------

Nope, did a data wipe and internal storage wipe and nothing. Still failed messages. Could reinstalling rhe radios and modem maybe help?
[Verizon Samsung Galaxy S III] MIKEYSAKZ:
Meant to hit the quote button what radio are you running
[Verizon Samsung Galaxy S III] Nomad1600:
Hi folks. Past Thunderbolt user (SOAB, Thundershed, NuSense) and still using a TouchPad dual-booting webOS and OaTJB). Had my S3 for about six months, intending to ride out the warranty, but flashing withdrawals overcame that and I rooted today using casual (even easier than TBolt's one click) and landed on BoneStock (briefly considered MOAR). Easy download, everything seems to work. I credit the developer for being too good... everything works, and nothing to ask about. ;) May come up with questions as things settle in, but I have just enough knowledge to search and study before asking... and the folks here ave already provided lots of useful info, so thanks for all the help already given and in advance too.
[Verizon Samsung Galaxy S III] fishfuzz:
I have been running this (new Rev, mf1) for a while now, but as of this last release, I seem to be having more WIFI and bluetooth issues. Almost as if the wireless stack is crashing then restarting. For example, at the house, using wireless, all of a sudden, showing 4G,then moments later, the phone reconnects to the house WIFI - without changing locations.

Bluetooth is doing the same. Just before I posted this, I was listening to ATK through Sticher - then the audio disappeared. Toggled BT on and off and reconnected to the speaker, audio returns. About 5 minutes later, same thing. And it isn't limited to just my speaker - my headset has been doing the same.

Thoughts?

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] andybones:
Don't get too excited guys, just trying to get everything updated that's done, so a SMALL update is coming with the stuff that's done on the to-do list

v3.4:

Fixed Chrysis battery not showing up when chosen in Aroma (Done)

Added Street into Maps in Aroma (Done)

Remove the AdFree.apk from Aroma:Misc, and include custom Ad-blocking hosts file in ROM (Done)

hope to have link up by tonight
[Verizon Samsung Galaxy S III] andybones:
everyone please check out the new KICK ASS splash in the OP thanks to Gadget!

PLEASE thank him!!!!
[Verizon Samsung Galaxy S III] akakai:
Damn that's a bad ass splash.
[Verizon Samsung Galaxy S III] fishfuzz:
If the art at the top is the splash, wow. Fitting yet well done.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] andybones:
Yea it is and its freaking amazing Gadget! Is a true master!!

Thanks again bro!!
[Verizon Samsung Galaxy S III] andybones:
link is up guys, sorry for the wait..
[Verizon Samsung Galaxy S III] APeaceofStrange:
Thanks for the update! Is the aosp theme/mods compatible with the update?
[Verizon Samsung Galaxy S III] Hobart!:
Just flashed 3.3 2 days ago. Can I dirty flash or is there anything else other than change log that was updated ? I could do without of I have to for now. .lol.. I know it's not advised to dirty flash but just got set up and flashed bandit theme..lol
[Verizon Samsung Galaxy S III] prdog1:
You could dirty flash if need the new options. Will have to reflash theme. :cool:
[Verizon Samsung Galaxy S III] Jay Evans:
File says 3.4... About says 3.3.
[Verizon Samsung Galaxy S III] prdog1:
He probably forgot to update buildprop. You can make it say anything you want with a text editor. Can make it say Jay Evans if you want. :cool:
[Verizon Samsung Galaxy S III] Jay Evans:
I know, just a heads up.
[Verizon Samsung Galaxy S III] andybones:
sorry guys there's a lot going on in life, and now 3 phones to support, things like forgetting build.prop will happen. appreciate the heads up, that's not what I'm saying, just crammed right now, doing my best. :)
[Verizon Samsung Galaxy S III] prdog1:
HaHaa. If they can root, unlock and flash roms they can edit their own buildprop. :rolleyes::laugh::cool:
[Verizon Samsung Galaxy S III] andybones:
haha SO very true, my friend!

link up on gtalk tmw, if you're free?
[Verizon Samsung Galaxy S III] prdog1:
I'm always free. lol :cool:
[Verizon Samsung Galaxy S III] tampaboy1984:
Just wanted to point out that Build Number still says v3.3 and also Aroma installer stills says v3.3
[Verizon Samsung Galaxy S III] prdog1:
Does not affect install. These are simple text edits that don't affect any rom files. :cool: :cool:
[Verizon Samsung Galaxy S III] McDastardly:
+1
[Verizon Samsung Galaxy S III] Nnyan:
With all due respect you are making a few wrong assumptions. I don't restore any data (PITA to set up all my accounts etc... but it works for me). Clean to me is wiping system/data/dalvik/cache/internal X3. Odds are its overkill but it takes no time so why not. I have a minimal set of apps that get installed as a base. I run with that for at least a full week to make sure there are no issues and to try to compare apples to apples (then nandroid as my working well base).

I have seen plenty of ROMS that use the same base give significantly different results. I have seen the same ROM run great on one phone and not so well on another (with exact build). Most CleanROMS work great on mine but there have been a few that I could not get stable. Beans is the opposite, great ROM but most just don't like my phone but a few worked great.

Anyway I even ran BS bare with No extra apps for a few days and still same results (I then installed a few battery diag apps and could not pin it down). Like I said I think I like BS better then any other I have tried but I need decent battery.
[Verizon Samsung Galaxy S III] andybones:
PrDog1 is free to his opinion on your posts, you post he trys to help, tha'ts how it works, no one can be correct 100% of the time.

If you aren't getting GREAT battery life on this ROM..

it's user error.

and by that I mean, it's something the user (you) is doing, not necessarily wrong,

but with over 2,000 downloads and only 1 person with bad battery life..

well you do the math. :)

the beauty of BoneStock is I don't mess with experimental init.d or any other battery tweaks, this is stock..

If you aren't getting good battery life, rouge app, or your battery/phone is having issues.
[Verizon Samsung Galaxy S III] texaswickedtoys:
Recently installed v3.4 and just curious about the viper audio mod it says I need to install drivers but whem it asks about cpu not sure what I should select any help please
[Verizon Samsung Galaxy S III] M_T_M:
Google your phone specs and the answer will be revealed to you mate ;)

********_***********

LA CALACA, TILICA Y FLACA!! :eek:
[Verizon Samsung Galaxy S III] texaswickedtoys:
I did but the optiins given to me by the app doby match the phones specs
[Verizon Samsung Galaxy S III] zachf714:
technically I don't think any of them match the U.S. GS3 100% because we have a krait CPU acording to the GCC compiler
[Verizon Samsung Galaxy S III] ed hit:
I have always used "Cortex A8 with neon" for FX and "Cortex" for XHIFI. This is per the original viper thread that is still kicking around in the mods section somewhere and it has worked for me. Going off memory there but check in the mods section if you wish.
[Verizon Samsung Galaxy S III] ufjay5:
Deleted
[Verizon Samsung Galaxy S III] Hobart!:
Anyone know what the msm_otg wakelock is and how to stop it? I googled it and it has something to do with usb otg something? I havnt done anything but flash last night and charge and sit in my pocket..no connecting it to usb or pc..it has used 42% of battery...stock kernel..kernel wakelock...thanks
[Verizon Samsung Galaxy S III] wolfballz:
Otg cable would allow you to plug in a keyboard, mouse, usb drive/stick. Not sure why it would be running crazy like that though and should only be running if you insert an otg cable. Maybe reflash? I will try and look up something regarding it.

Update: if using twrp recovery go into wipe, advanced wipe and at the bottom is otg-usb. Wipe that and see if it helps.
[Verizon Samsung Galaxy S III] prdog1:
Try wiping dalvik and cache and reboot to see if will reset it. Otherwise clean wipe and reflash. :cool:
[Verizon Samsung Galaxy S III] Hobart!:
Tried recovery wiping otg...it failed so I tried dalvik and cache..well see...thank you both
[Verizon Samsung Galaxy S III] Nnyan:
No disrespect meant and by no means did I mean to stifle anyone's opinion I was just stating mine. I am no DEV so I can't explain it but running the same exact apps on another ROM I have good battery life. We have 23 of these phones here but I have not tried BS 3.x on any others (using our standard app build out) yet.
[Verizon Samsung Galaxy S III] jimmyUT:
Just took the jump from 3.1 to 3.4 and its perfect as expected. However. I have this little icon that has come up over the phone bars a couple times and I have never seen it on any android phone or ROM before. Just curious what it is. It looks like a little house with two curved bars over it. Pic attached

Sent from my Zombie Wireless S3
[Verizon Samsung Galaxy S III] jimmyUT:
Also my splash screen is still the nexus one. Didnt get that cool one from the op... do I need to install that separate?

Sent from my Zombie Wireless S3
[Verizon Samsung Galaxy S III] prdog1:
Think that is pulling from someones signal extender. Notice your 1X.

---------- Post added at 08:22 PM ---------- Previous post was at 08:19 PM ----------

That is banner and not actually a splash screen as far as I know. :cool:
[Verizon Samsung Galaxy S III] Hobart!:
Ok 1 more question. ..I see spell check is an extra and is included in 3.4...as I went ro flash I see TW messaging spell check...I used aosp messaging...will it still work? Will I hurt anything if I try? Is it tw messaging only?..thanks
[Verizon Samsung Galaxy S III] prdog1:
TW only as far as I know and must have Google Keyboard installed from the market. Will work on all keyboards then except maybe AOSP messaging. Can try tho. :cool:
[Verizon Samsung Galaxy S III] jimmyUT:
What's a signal extender?

And on page 505 Andy said check out thr new splash, so I assumed it was that picture. Oh well would be a much sweeter spalsh than the x

Sent from my Zombie Wireless S3
[Verizon Samsung Galaxy S III] jackdubl:
That's a signal extender icon above your bars. I have it on my phone as well. Of course, I'm using a signal extender, which extends my 3g/voice signal strength by using my home wifi network. If you don't have one you must be connecting to a neighbor's. I think you're still secure; probably just improves your signal. Maybe not, though.
[Verizon Samsung Galaxy S III] prdog1:
Some people living in fringe areas get them to boost the tower signal. Sometimes Verizon will give you one and sometimes they charge for it. Can get at BestBuy also but they are not cheap. One of your neighbors probably has one and your phone is seeing it. :cool:
[Verizon Samsung Galaxy S III] jimmyUT:
Ah! That makes sense now. I was actually in front of my kids school and for some reason verizon sucks righ there so I can see why somenof the houses there would have one. Weird I have never caught one in all my years with android

Sent from my Zombie Wireless S3
[Verizon Samsung Galaxy S III] fishfuzz:
I thought the same thing when my phone started up. Was eagerly watching for the new view and then X. ^_^

Guess it's time to figure out how to make my own.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] texaswickedtoys:
Thanks I found it and yes its cortex a8
[Verizon Samsung Galaxy S III] wolfballz:
I tried it with aosp messenger and it didnt work with it but this spell check also works anywhere i type and not just in the messenger.
[Verizon Samsung Galaxy S III] trueParadoX_2446:
It seems my battery wont charge. when it gets low enough, the low battery warning will just keep flashing up and the battery will slowly drain even when connected to the charger. Clean flashed twice and still having this issue. Any suggestions?
[Verizon Samsung Galaxy S III] bobd2754:
HOBART! Welcome!
[Verizon Samsung Galaxy S III] andybones:
Just curious but how does

"everyone please check out the new KICK ASS splash in the OP thanks to Gadget!

PLEASE thank him!!!!"

have anything to do with the ROM :confused:

said check out new splash in OP

not new splash in the ROM

although, one *may* be in the works but please don't hold this against me
[Verizon Samsung Galaxy S III] jimmyUT:
I have never heard anyone use the term "Splash" to refer to any artwork other than a splash screen. Sorry for the confusion.

Sent from my Zombie Wireless S3
[Verizon Samsung Galaxy S III] M_T_M:
Maybe the OP's first language is not English mate. When I read his initial post about the "splash" I went to the first post and noticed the new image and knew right away what he meant :);)
[Verizon Samsung Galaxy S III] andybones:
All is good guys, didn't mean to sound like jerk, just meant for asking as to now confuse guys again :)
[Verizon Samsung Galaxy S III] fishfuzz:
Flips tables!

Splash boot or I brick phone!

Discontent over pretty picture! jk

(no worries - we weren't asking for a change, just noting how awesome we thought it the image was by expressing we were eagerly watching for it on boot)

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] wolfballz:
I think everyone will be pleasantly surprised soon... a new animation may soon be coming to a Bonestock S3 device near you.
[Verizon Samsung Galaxy S III] kazarp:
My friend's GS4 did this the other day. Fix for us was to pull battery, wipe off terminals, and put it back in.
[Verizon Samsung Galaxy S III] nsaechao:
Quick question.. Just made the jump from Bone3 to the latest version 3.4 .. So with the full battery notification off.. The is batter function is still the same.. Meaning the battery won't overcharge

using Xparent Skyblue Tapatalk 2
[Verizon Samsung Galaxy S III] M_T_M:
Nope...this is juts a notification change mate. The battery and the phone are designed from factory, not to "over charge" ;)
[Verizon Samsung Galaxy S III] ufjay5:
Quick question...my led notification light is coming on but I have it set to off. Any thoughts?
[Verizon Samsung Galaxy S III] prdog1:
I'm on 3.3 and mine don't come on. Any other apps installed that may be overriding it? Depends on the notification whether it trips the light or not. :cool:
[Verizon Samsung Galaxy S III] wolfballz:
Thanks to Andy and Gadget! for their approval I have started a boot animation for Bonestock ROM. It is a little basic so far but am currently adding more awesomeness to it and will have a updated version out soon. Also, please feel free to give ideas for additions to it. If you have an idea please PM me so we don't clog up the thread.

https://www.dropbox.com/s/f6cihvg0bevzuxy/bootanimation.zip
[Verizon Samsung Galaxy S III] zachf714:
Can I haz ur wall :P
[Verizon Samsung Galaxy S III] Hobart!:
What exactly does center clock fix do again? Does it fix overlapping of notifications over clock?
[Verizon Samsung Galaxy S III] wolfballz:
Yes it does
[Verizon Samsung Galaxy S III] Jihoonie:
And it corrects the clock color if you chose anything other than the default blue
[Verizon Samsung Galaxy S III] prdog1:
What works even better. Clear your notifications now and then. They didn't notify you for grins. :p:laugh::cool:
[Verizon Samsung Galaxy S III] illyfilly:
Which one to flash 3.4/3.5?
[Verizon Samsung Galaxy S III] blueb0x:
3.5 should put you ahead of the game
[Verizon Samsung Galaxy S III] Nomad1600:
OK, I have been on BoneStock 3.3 for a bit under a week, and have been really happy by how well it works, how stable it is, and how great battery life has been. its what Samsung should have done with the GS3 from the get go. Kudos to AndyBones.

I hope this is the correct place to pose this question (its specific to BoneStock), but if not, please move or tell me to move it. Here goes... since flashing the ROM, I have noticed that all of the Verizon apps and widgets came over and still appear on the App drawer (and one widget, the Media Hub). I am pretty sure when I flashed the ROM and went through the set up (that's Aroma, correct?), I didn't check things related to Verizon. I know I successfully flashed the ROM (says so on the About Phone), so I must have not done something correctly in set up. Also, I did not do wipes before flashing this (it was my first ROM installed after rooting). Also btw, my first experience rooting and flashing a GS3 phone (experienced with rooting a ThunderBolt and TouchPad, but they don't don't use Aroma). Lastly, if it makes a difference, I used casual to root, and I am using TWRP for recovery.

Since there is v3.4 sitting in front of me, I will get a new chance to do it correctly (making a nandroid in TWRP first): So here are my questions:

Do I normally need to wipe before going to 3.4 or can I flash the new version "dirty"?

Regardless of #1 above, should I do wipes before going to 3.4 to get rid of the Verizon bloat (since I didn't get rid of it before)?

Do most of the customizations in BoneStock happen in Aroma (setup) versus other ROMs that seem to have the customizations under Settings (and remember my experience is outside GS3)?

Lastly, does BoneStock appear in Goo manager?

Thanks in advance!!
[Verizon Samsung Galaxy S III] jackdubl:
Sounds like you didn't wipe before flashing, that's why you're getting leftover bloat.
[Verizon Samsung Galaxy S III] HypostaticOnion:
That's exactly what it is. If you didn't wipe you'll have leftover stuff especially if its from the same base.

If I've helped, please hit the thanks button
[Verizon Samsung Galaxy S III] wolfballz:
Here is another bootanimation without the fading in and out but with a cool glow. I am still trying different ideas and if you guys have some let me know.

https://www.dropbox.com/s/ud8ynxt0itsy4vi/bootanimation.zip
[Verizon Samsung Galaxy S III] Nomad1600:
Ok, that now makes sense and I won't make the same mistake again (especially good to know as I will be rooting/flashing my wife's and two daughter's phones at some point). Since I will be updating to 3.4 this weekend, I can do wipes before flashing the new version which hopefully takes care of the V-bloat. If I had done the wipe initially, would I have to wipe between upgrades?