yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dcox28:
Well I always use Phablet mode and am using it now as well. Still no dual pane

Edit - here are some screenshots. Its driving me crazy, I always have dual pane on Rootbox but not now and I am in phablet mode like always.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dcox28:
I always clean flash as well. I am on the most recent stable build that was just released. I have a D2VZW. What is weird is I never had the dual pane mode on newest nightly but always had it on the latest nightly. Now when I clean flash back to the newest nightly it is the same as now, no dual pane.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] boynamedstacy:
I am having the same issue on Verizon. No notification sounds for some apps like FB messenger. Also the screen turns on and off randomly. Coming from a fresh wipe too. Any ideas?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] XblackdemonX:
I installed the new Gapps 8-12 and now i keep getting notifications from Rootbox OTA saying there is a new version of Gapps 03-01-2013.

How can I disable these notifications? i looked in OTA settings but couldn't find anything
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yeeahnick:
Look again its there
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JRJ442:
Did you use Titanium to restore apps?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JRJ442:
To get the tablet layout or dual pane, Go to Paranoid Settings-> Apps. Now find the app you want and change the layout to 720p. And adjust the DPI for that app til you get the sizes the way you want.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] boynamedstacy:
I did, a few, yes. It's that a no no?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JRJ442:
No its definitely fine. Just a few apps don't work so well when you restore the app and app data, as far as push notifications go. Facebook messenger is one. Try wiping the app data for the ones that aren't working and see if it helps.

If that doesn't. Uninstall and redownload from the market.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] volkey:
In my case, I restored app data only, but I used mybackup pro

I'll try wiping data for Snapchat.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Alex2x3:
Also having this issue but messing with the media control button doesn't seem to help. Any other ideas?

Another really small one is I have the "start music player when headphones are inserted" checked and it also does not work.

Both issues are not to big of deals compared to how well this Rom runs but just reporting.

Great job Bajee!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] XblackdemonX:
ha ok i found the "ignore update" thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dcox28:
Thanks JRJ442, that did work. Weird how it always was in dual pane by default before but I had to mess with the DPI settings this time
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JRJ442:
You're welcome. Bajee may have changed the default settings for those apps this time around. That would be the only explanation why it was different on a clean flash really.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] raresoul77:
Screen is stuck on landscape tried launcher options and searched thru out ROM settings and can't get it back to portrait for nothing... Any ideas?

Edit: found the problem , all is good now:thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lareya:
twirlling (going around in circles box) now what?

I have a screen with a twirling around blue box and nothing else. I try to reboot to get to something else, but this just comes up? coming from a tw (clean rom 7) to rom. I am a verizon user.

now what? I try to pull battery and get to twirlling blue box. I try to hod the the three S3 buttons, and still twirling buttons. how can I get off this screen?

thanks1

ps I used goo.manager and did the clear davich, and not dirty flash..... still.... only blue box of rom box - nothing else. :(

help???

Lareya
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] N-Forced:
Did you do a full wipe in recovery first?

Sent from my pimped out phone
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bitemeoftn:
Did you just wipe dalvik? You have to wipe data/cache/advanced/dalvik cache/back to mounts and storage/format system then flash ROM then flashgapps/reboot then you should be all set.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TenderloinShadow:
Hey so I just flashed root box on my d2vzw for the first time, and I love it. I'm running the stable 4.2.2 build that was released August 4th. I've encountered some bugs though, and I'm hoping for help with them.

The big one is Halo. The whitelist/blacklist feature doesn't seem to be working at all. When I set it to whitelist, and only whitelist certain apps, it doesn't prevent non-whitelisted apps from using Halo. The same happens in reverse with blacklist. I check the box and even reboot my phone before testing it for good measure.

Could someone help me?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] queeko:
Hello everyone.. Don't know if this problem I'm having is related to rom but I noticed it happening immediately after I upgraded to v4.2.. But it seems to have affected the ability to post images in instagram.. Anyone else have this problem...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] briant1234:
I have this problem to, not sure why.

In addition, on the latest 4.2 I can't share contacts through nfc or bluetooth share, both say that the service has stopped working if i try to use them, any body else get this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bitemeoftn:
Try the halo))) app from the play store. It's an add on for halo related workings. Hope that helps!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] briant1234:
The halo))) app doesn't do anything in my case, it only allows me to pin apps, but the blacklisting still does not work:(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bitemeoftn:
Next suggestion (and it could be dumb. no offense meant by it), but did you dirty flash? Try wiping data/cache and system reflash and try again. FWIW I'm on d2vzw as well and black/white list is working as it should.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NeCr0mStR:
Old Rootbox 3.9.1

Hello,

I recently tried changing from my Rootbox 3.9.1 to CM 10.2 and also tried Paranoid Android 3.9x beta. Before I did this though I had flashed my baseband to MF1 per the Official nightly instructions with CM 10.2. I restored back to my Rootbox 3.9.1 and now my camera gives the error that the software can't connect to the camera. I was hoping since flashing Paranoid Android 3.68 stable and the camera works find, that perhaps someone would know if flashing the baseband would cause the Camera issue? I was also wondering if maybe the bootchain might need to be updated to the MF1 bootchain in order for the Camera to work.

If I could get a copy of Rootbox 3.9.1 that would be ideal since I like that Rom more than pretty much any other Rom I have used, even the newer Rootbox versions that I have used.

Please let me know if you need any additional information and the exact camera error is "Can't connect to the camera."
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JRJ442:
3.9.1 is a pretty old build. The kernels had to be updated to work correctly with MF1, so you need a recent build of any ROM for the camera to work. If you really wanna use 3.9.1, you have to flash an older modem. Like the one before MB1 probably
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NeCr0mStR:
Just found the flashable MB1 modem on Invisablek's website. I think I will try that and see where it goes for me :D

Thank you for the reply.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JRJ442:
You need the one before MB1, it isn't much different from MF1. The same problem will be there. And you need the full firmware zip. Let me get you a link

http://invisiblek.org/sch-i535/firmware/ Download the MD3 firmware. MB1 is gonna give the same issue on 3.9.1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NeCr0mStR:
On that page there are three options: MF1, MB1, MD3

Which would I want, do I flash in CWM and why would I want the firmware not the modem for this?

I used the instructions here for flashing the MF1 because of the suggestion for CM 10.2.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JRJ442:
The TZ file is what's causing the problem with the camera I believe. You need the full firmware because it contains the modem, rpm, and tz file. Invisiblek recommends flashing the full firmware now instead of just the modem. If you flash just a modem now, the TZ file from MF1 may be left behind. Then you'll still have the same camera problem. You want MD3 if you're using a build as old as 3.9.1. Anything newer and you're gonna need that MF1 firmware. CWM is fine. Flash it, no wipes necessary. Make sure your MD5 sum matches too. If I was you I'd download both MF1 and MD3 firmware so you'll have it. When you move to a 4.3 ROM you're gonna need the MF1 firmware
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] o0BlacknesS0o:
The longer I run 4.2 stable, the more unstable it becomes. I'm getting random reboots, freezes and various bugs including a constant process system not responding at every boot d2vzw
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JRJ442:
Yeah I've been getting that process system not responding for a while. Someone said it was because of a theme being used. But I'm not so sure. Have you tried a different kernel? I'm using Lean Kernel and haven't had any reboots or freezes. I also keep Disable Hardware Overlays checked just in case.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] o0BlacknesS0o:
I do run a theme so maybe it's just related to that... Stock kernel has been so reliable for me that I haven't bothered with anything else... Plus when they have nightlies being released I afflatus start stock so I can report issues... guess I could stay a bit since nightlies are down for now... I disable hardware overlays as well
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JRJ442:
Don't leave us. Lol. I almost flashed PAC today, but then I remembered the last time I did that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NeCr0mStR:
Thank you so much for your assistance on this. I appreciate the quick replay and the clear and concise information very much.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] o0BlacknesS0o:
Lol... I just meant kernel wise... I have no intentions of leaving this rom for anything else anytime soon
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NeCr0mStR:
Much moar better

Thank you so much JRJ442. I flashed the MB1 firmware because that is what I was running previously. The MD3 firmware, from what I read, had a lot of issues and I read not to flash that so I thought I would take a chance with the MB1 and go from there. Camera fixed now and all is much better. Thank you once again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JRJ442:
Glad you got it working. But I think MD3 was better than MB1. MB1 was from an OTA that borked some peoples connection. MF1 was the OTA to fix it. Just keep an eye on you data speeds and connection.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rattmann:
I know this is a simple question, but how do you change the statusbar clock style from military time to 12-hour? I had always had my phone on the 12-hour style, but earlier when I turned on my phone it turned to military style. I checked ROM Control>Clock, but didn't see any option to change it.

I am running the 4.2 stable.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] briant1234:
Thanks!, im on d2att. ill double check with my d2vzw friend before the data wipe because im hesitant about my data ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JRJ442:
Settings-> Date & Time-> 24 hour
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TenderloinShadow:
The Halo app doesn't do anything, but I think I've figured out more about the cause. It's the option that allows you to use the gestures to switch between multiple notifications. If I have that off, and can only select the most recent notification, the Blacklist/Whitelist feature works perfectly. With the notification switching option however I can select app notifications that aren't in my whitelist.

so at the moment I more or less have it working like it's supposed to :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] queeko:
What's up everyone... We'll earlier I asked that I I couldn't post images on instagram.. I confirmed it is rom.. I tried different devices.. (nexus 7 and wife's gs3 not rooted but running same version of instagram.. Hopefully this can be looked into and fixed.. Thanks love this rom..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JRJ442:
I think you should look into something on your end. Data connection maybe. I literally just posted this on Instagram 10 seconds ago
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DigitalUnderground:
Re: [ROM][4.2.1] RootBox Non-development | Discussion | Support [d2att/2tmo/d2vzw]

:o:o:o
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vrekeno:
I installed the ROM about 2 weeks ago. Fresh install after full wipe and factory reset.

It worked fine until a couple of days ago.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DigitalUnderground:
Re: [ROM][4.2.1] RootBox Non-development | Discussion | Support [d2att/2tmo/d2vzw]

That's weird... Have you tried redownloading both ROM and gapps to your pc and transferring that way, doing a clean install, and running it with 0 installed apps for a day or so and then slowly installing apps few by few to try and isolate the issue? You seem to be the only one with that problem. I ran the official release from its release date till today when I flashed today's nightly and have never had a single issue with this ROM... And I have a ton of apps and themes
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] crjjr:
play store issues

Installed the 02-08 nightly on the d2vzw. Play store popped up with updates, so I went to update the app (Carbon). Downloaded correctly but then popped up an error saying insufficient space available. I tried to install a random small app as well to see if it was just that particular app, but got the same error. I installed as directed, cleaned cache/dalvik, then booted. Also cleaned data for the play store when it wasn't working but that didn't help either. Any suggestions?

I should say that I have plenty of space available. 10GB or so of internal and 25ish of external.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
I suggest the standard re-download, FULLY wipe and re-flash.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nigmol:
Is there only me that still can't get Chronus weather to display. I've tried the imperial/metric setting but no joy
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Hannibal226:
Re: [ROM][4.2.1] RootBox Non-development | Discussion | Support [d2att/2tmo/d2vzw]

What u exactly did?

The Chronus clock u see?

Can u see the weather if u drag down the pattern/pin/slide lock?

CHEERS ;)

Sent from my GT-I9100 with RootBox
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Neverendingxsin:
Just curious is support for D2vzw dead? I ask because i saw that he closed the thread in the respective forum due to certain members not reading the OP. But if its dead then i'll start learning how to compile it on my own for D2vzw, just wanna figure out what's going on first :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nigmol:
Weather won't display on either lock screen or home screen no matter what I try. Clock displays ok
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Hannibal226:
Re: [ROM][4.2.1] RootBox Non-development | Discussion | Support [d2att/2tmo/d2vzw]

But u already activated it in settings > RootBox settings > lockscreen > cClock > weather?

Sent from my GT-I9100 with RootBox
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nigmol:
I have and I've tried the trick mentioned elsewhere of setting metric settings
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Hannibal226:
Re: [ROM][4.2.1] RootBox Non-development | Discussion | Support [d2att/2tmo/d2vzw]

Sorry for maybe a but dumb question but please don't get it personal (just try to help :P)

U r sure u have the Chronus widget on lockscreen and not the digital clock?

PS: It listen really strange because u r one of the first I heard about this kind of problem o.O

CHEERS ;)

Sent from my GT-I9100 with RootBox
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nigmol:
[ROM][4.2.1] RootBox Non-development | Discussion | Support [d2att/2tmo/d2vzw]

Yes I've tried it on lock screen snd home screen but no weather on either. I've read through both threads and has been mentioned by a number of people - and I have ticked the box for weather :)

Sent using Tapatalk
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Hannibal226:
Re: [ROM][4.2.1] RootBox Non-development | Discussion | Support [d2att/2tmo/d2vzw]

Hmm ok.

So a option u can try is to do a quick reflash with wiping (dalvik) cache (if u haven't already done)

Sent from my GT-I9100 with RootBox
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AndroidChicago:
Re: [ROM][4.2.1] RootBox Non-development | Discussion | Support [d2att/2tmo/d2vzw]

Can someone post a link to download the stable version?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xxsicknessxx:
Xposed is buggy be carefull I had it take me down and I was using it safly (following directions)

Also don't use TB backup to reinstall apps with data!! it can bug you out

Also don't replace system apps with other inverted apps, or custom apps unless you don't want support here (rules)

All stuff I did before that caused me problems :)

Also never install backups with data![/COLOR][/B]

---------- Post added at 05:26 PM ---------- Previous post was at 05:14 PM ----------

You might want to check your Data/media folder and see if its full this can cause the problem your talking about.

There should be data/media/ only things in it should be 0 folder and everything else should be emtey. If there not move them to 0 folder or delete them. Sometimes its flashing from 4.0 to 4.2 stuff gets left behind and if you have issues as some people do it could be full of junk thus you could be out space even though it wouldn't look like it sense that folder isn't used anymore

Data/media (check it out) don't delete or touch the 0 folder thats your SD card. Also get a program called sd maid

Link to SD maid playstore

Its a dangerous program so watch out but most stuff pretty easy use and safe. Scan for corpses and junk files and stuff... don't delete anything important though!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] y0yerrj0sh:
http://rootbox.ca/?page_id=12

and don't forget to flash the gapps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DigitalUnderground:
Re: [ROM][4.2.1] RootBox Non-development | Discussion | Support [d2att/2tmo/d2vzw]

Seriously? OP too much to read? Smh
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xxsicknessxx:
Now I get why you read the changelog first before posting :) is there a link in the OP showing the changelog btw?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DigitalUnderground:
Re: [ROM][4.2.1] RootBox Non-development | Discussion | Support [d2att/2tmo/d2vzw]

Lol I hope u are joking...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manicpanic:
I had an issue on d2att where it would post a black image, but it went away when I switched kernel's from kt747 to lean.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] queeko:
Thanks bro.. I'll keep trying to troubleshoot.. I'm pretty stumped though...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JRJ442:
Sorry I missed your first post. What exactly does it do when you try to post pics?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] queeko:
Aahhh... That could be it I installed updated bms kernel.. I'll install older kernel.. That will definitely fix problem.. Apologies to rom devs awesome rom.. And thanks to all that helped figure this out...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sepharite:
What's the best kernel so far, I've been using BMS and it's okay. Not the greatest battery life.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Notorious:
what version/nightly are you on?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JRJ442:
I was on 4.2 Stable. Trying out a 4.3 ROM today.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] XblackdemonX:
Leankernel or nothing
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] trvbone:
Dkp kernel...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] o0BlacknesS0o:
Hey guys... Any suggestions on how to increase the headphone sound levels... I've got volume maxed out and it's just not enough
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cr4ck3r4lif3:
The sound hacks I used on TW don't work on this rom but I use this app with a compatible kernel (using lean now) and works great. https://play.google.com/store/apps/details?id=com.teamkang.fauxsound
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xneuromancer:
Anyone have issues with system ui battery drain? I'm used to TW roms and have never had this issue before.

I used "where's my droid power" app and it has the highest percentage. I had a look in "better battery stats" as well and couldn't get any more information.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TenderloinShadow:
Hey I'm running the stable 4.2.2 build, but when I tried to use my beloved KT747 kernel with it I started getting a lot of SystemUI force closes. Has anyone else experienced this? Are there any other kernels that are known to work with this ROM?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JRJ442:
Lean Kernel and BMS work well. Just make sure you use the correct version. Gotta be a kernel for 4.2.2 and not 4.3. BMS is just doing 4.3 now, Imoseyon probably will too
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TenderloinShadow:
Yeah. Is Root Box on the 3.4 Linux kernel, or is it still based on 3.0? Because I was using the 3.4 kernel that I had been using with AOKP before I switched to Root Box.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xneuromancer:
3.4 kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xneuromancer:
Anyone having a problem with the lock screen sound? When I push the power button to lock the phone + turn the screen off, the lock screen sound is about 1 -> 1.5 seconds delayed from the push of the button. On the other hand, when unlocking the phone via the lock screen, the sound is almost in time with the home screen showing up after the unlock.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JRJ442:
I've seen that on a few different ROMs for quite a while. One of the main reasons I leave it off. I think its just the way it coded in.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] njpnc:
I used BMS kernel and no issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rattmann:
Right, thank you! With so many menus in this ROM I forget about the regular Android ones...