yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] mlaws90:
Sorry I didnt understand a lot of that. But to remove the transparent bar at the bottom of the Pie, set the Style to Fast or Bare. Only Solution at the moment if you have this issue AFTER doing what I said in post #2.
[Nexus 7 Android Development] dparrothead1:
Re: [ROM][WiFi][AOKP/CM][4.2.1] Dirty RootBox v1.0 [Aroma][Per-App-DPI][PIE][02/05]

Didn't really mean for him to stop building Dirty AOKP....just a feeble attempt at humor.

400 d/l's in a 24 hour period for a v1.0.....not too shabby, M. Has to say something about your Dev reputation.:thumbup:
[Nexus 7 Android Development] mlaws90:
Not too shabby at all for an Initial release, plus Dirty AOKP it is about 750 downloads total over 24 hours. My goo.im account gives me 24 hour totals. That is amazing to this I was and android noob when I made this xda account I had gotten my first android device and haven't looked back. :)
[Nexus 7 Android Development] sebarkh:
Odp: [ROM][WiFi][AOKP/CM][4.2.1] Dirty RootBox v1.0 [Aroma][Per-App-DPI][PIE][02/05]

I was lurking xda for many hours after I got my nex 7, trying to find some decent Rom. Finally, after many flashing done... I stayed with Dirty AOKP. Only a couple days ago, RootToolbox was released and I must admit I swapped to it, from DirtyRom. Now, I can have both. :)

Sent from my washing machine...straight from the tumbler...
[Nexus 7 Android Development] dparrothead1:
Re: [ROM][WiFi][AOKP/CM][4.2.1] Dirty RootBox v1.0 [Aroma][Per-App-DPI][PIE][02/05]

Amazing...considering 165 d/l's for v1.0 Dirty AOKP!

I respect your skills.....wish I had the knowledge. Just, please, don't burn out!! :eek:
[Nexus 7 Android Development] mlaws90:
Haha yeah right, my internals are good for another couple millenia. I will get a replacement long before that, like I did around the time of Christ. ;)

Lol I actually have been getting more sleep lately, I swear!
[Nexus 7 Android Development] CharliesTheMan:
Re: [ROM][WiFi][AOKP/CM][4.2.1] Dirty RootBox v1.0 [Aroma][Per-App-DPI][PIE][02/05]

Lol this made me laugh, love it. I'm one of those rare guys that works with android on assisting devs and troubleshooting for users because I find it relaxing.

Great to meet someone else invincible :)
[Nexus 7 Android Development] jamm513:
No mlaws, i'm using AOKP right now, whit dual, panel and change any app, even no system apps (i'm using apex and nova, data apps, and change all to dual apnel), just try and see.
[Nexus 7 Android Development] mlaws90:
OK I use Xposed for DPI and dual panel settings. Next time I build and test Dirty AOKP I'll take a look, but I was told it only effects system apps here: http://gerrit.sudoservers.com/#/c/5320/

Building RootBox v1.1 soon, lots of updates.

Dirty RootBox v1.1 Changelog

Update Apex Launcher to 1.4.3 stable, newwer than 1.4.3 beta 2.

Update Holo Launcher to 2.0.2, first update from them in a while

Update SuperSU to 1.04

Update Titanium Backup to 6.0.2

Add Camera Launcher

More? Gotta check some other stuff still for updates.
[Nexus 7 Android Development] jscarano:
Re: [ROM][WiFi][AOKP/CM][4.2.1] Dirty RootBox v1.0 [Aroma][Per-App-DPI][PIE][02/05]

Anyone know how to get crt on/off working on this?
[Nexus 7 Android Development] dstryrwiz:
I was able to turn it on using one of the apks in association with Xposed, but I can't turn it off.
[Nexus 7 Android Development] Jaydizzle414:
Re: [ROM][WiFi][AOKP/CM][4.2.1] Dirty RootBox v1.0 [Aroma][Per-App-DPI][PIE][02/05]

Download closed tweakbox.apk then enable CRT then clock soft reboot in t the closed installer
[Nexus 7 Android Development] Sultan.Alkhuzaie:
Re: [ROM][WiFi][AOKP/CM][4.2.1] Dirty RootBox v1.0 [Aroma][Per-App-DPI][PIE][02/05]

Check the cm10.1 fusion ROM thread the last couple of pages . I can do it but I don't have time

Edit : http://xdaforums.com/showthread.php?p=37561707 :)
[Nexus 7 Android Development] jscarano:
Thanks I got it working through xposed settings. :):)
[Nexus 7 Android Development] mlaws90:
To turn it off uncheck the Tweakbox Module in the Xposed Installer. That will remove the CRT off animation if you ever want to.
[Nexus 7 Android Development] KiljoyMcCoy:
hmm

the space the status bar would normally take up is unresponsive to touch some times.

like say the bottom "save" was at the bottom of the screen normally above the status bar. after enabling pie the status bar is hid and the "save" button is moved tot he bottom of the screen where the status bar use to be is unresponsive in areas that weren't button areas on the status bar that isn't showing now.

hopefully that makes sense lol

other thing i've noticed is after waking it up pie comes back invisible at times.

probably all beta bugs for pie is what i am figureing
[Nexus 7 Android Development] Sultan.Alkhuzaie:
Re: [ROM][WiFi][AOKP/CM][4.2.1] Dirty RootBox v1.0 [Aroma][Per-App-DPI][PIE][02/05]

Please can u add the picasa sync in gallery
[Nexus 7 Android Development] flyguy914:
Re: [ROM][WiFi][AOKP/CM][4.2.1] Dirty RootBox v1.0 [Aroma][Per-App-DPI][PIE][02/05]

Am I doing something wrong?I changed system DPI to 160 using root explorer, then I tried to change DPI for words with friends to default 213 so it wouldn't be in landscape but it didn't take lol, did I do it wrong?
[Nexus 7 Android Development] jscarano:
I tried changing some apps dpi and nothing worked. How do you use the per app dpi changer on this rom??? thanks
[Nexus 7 Android Development] dparrothead1:
Re: [ROM][WiFi][AOKP/CM][4.2.1] Dirty RootBox v1.0 [Aroma][Per-App-DPI][PIE][02/05]

Are you rebooting after you make the changes?
[Nexus 7 Android Development] dstryrwiz:
I had tried disabling the setting and it hadn't worked, but disabling the module did. I like the animation, but it's really bright and I decided against it, but then I couldn't turn it off, so this helps me a lot. Thank you.
[Nexus 7 Android Development] jscarano:
No . I didn't think you had too?!?!
[Nexus 7 Android Development] dparrothead1:
Re: [ROM][WiFi][AOKP/CM][4.2.1] Dirty RootBox v1.0 [Aroma][Per-App-DPI][PIE][02/05]

Try it.
[Nexus 7 Android Development] jscarano:
Alrighty. For an app like Speed test which comes up super small what dpi should I put it on? 213?

edit: I must be doing something wrong nothing is working even after reset
[Nexus 7 Android Development] dparrothead1:
Re: [ROM][WiFi][AOKP/CM][4.2.1] Dirty RootBox v1.0 [Aroma][Per-App-DPI][PIE][02/05]

213 is default DPI, so it should be good to go.
[Nexus 7 Android Development] dstryrwiz:
Did you enable the module?
[Nexus 7 Android Development] jscarano:
Oops. Let me try that and then reboot. thanks

edit seems to be working now
[Nexus 7 Android Development] Southrice:
I'm also getting invisible pie when waking up my device.

I played around with it a little more, and I noticed that If I have settings running in the background and I sleep my device and wake it back up, pie is invisible. But when I kill the settings in the background, before I sleep it, when I turn it back on pie works normally.

also, is there any way to change the status bar DPI?
[Nexus 7 Android Development] johnnyman25:
Απ: [ROM][WiFi][AOKP/CM][4.2.1] Dirty RootBox v1.0 [Aroma][Per-App-DPI][PIE][02/05]

Can someone pls post a screenshot like mine?i want to see something.thx.

Sent from my Nexus 7 using Taptalk HD

Dirty Root Box v1.0 & Franco Kernel r42
[Nexus 7 Android Development] dstryrwiz:
mlaws90, two things I've noticed with this ROM. First off, the included Xposed Installer is outdated, and secondly, something in this ROM is either breaking M-Kernel or Trickstermod as I cannot change the Max CPU Cores in Trickstermod on this ROM, and the only way I can fix it is to run the Kernel wipe zip which breaks the ROM (resets all DPI values and wipes the init.d folder). Can you please look into this? Thank you.
[Nexus 7 Android Development] mlaws90:
Somehow I double posted, idk lol.
[Nexus 7 Android Development] mlaws90:
Select Install/Update then got he modules tab and check the app settings module and reboot. Then it will work crrectly if you were having issues. It should show info under active after the install/reboot.

Change the DPI of SystemUI in Xposed App Settings.. I would do a back up before doing this, for this you must reboot to see the effects. For all other apps no need to reboot.
[Nexus 7 Android Development] johnnyman25:
thx for the info but i wanted it to see if the module is active default or not cuz i press installe/update and now letter are green.the default was -?sorry for my bad english.
[Nexus 7 Android Development] dstryrwiz:
That's not even the module, that's Xposed in general, and no, it is not installed default.
[Nexus 7 Android Development] johnnyman25:
so the screenshot i posted is the default one settings?
[Nexus 7 Android Development] dparrothead1:
Re: [ROM][WiFi][AOKP/CM][4.2.1] Dirty RootBox v1.0 [Aroma][Per-App-DPI][PIE][02/05]

When you activate the install/update button, the apps under active will be green.
[Nexus 7 Android Development] Southrice:
I've also noticed this, the option to change max CPU cores in Trickstermod is gone.

And I've been meaning to say that I was hesitant to switch over from PA to this Rom, but I'm glad I did :) found my new home ;)
[Nexus 7 Android Development] johnnyman25:
the default is green or no?i mean when u clear install the rom.
[Nexus 7 Android Development] dparrothead1:
Re: [ROM][WiFi][AOKP/CM][4.2.1] Dirty RootBox v1.0 [Aroma][Per-App-DPI][PIE][02/05]

Your screenshot is the "Installer".....this has to be activated before you can use the "xposed app settings".

When you first open the "installer" the info under "active" will be red......once you hit the install/update bar....the info will change to green. And it will prompt you to reboot.

Then you can use the"xposed app settings"
[Nexus 7 Android Development] dstryrwiz:
I emailed Trickstermod about this and this was their response:

"On that config do you have this file /sys/kernel/debug/tegra_hotplug/max_cpus? If not then that option won't show up.

--

Team Trickster Support"

They were right, the file is missing, but it confuses me as even if I reflash the kernel, the option does not come back, and I have yet to test if the file does, but I assume it won't either. I always thought ROMs and kernels were separate and wouldn't effect each other, but in this case it definitely is as the only way I have been able to get that setting back is by running the kernel wipe zip after the ROM is fully installed, but that breaks many features of this ROM including all of the init.d scripts and the per app DPI settings. This definitely is ROM related, but I have no idea what may be causing this.

---------- Post added at 11:16 PM ---------- Previous post was at 10:38 PM ----------

When I asked why the ROM would impact the kernel, this was their response. mlaws90, please take note.

"That's because of the ramdisk. The purpose of the reset zip is to reset the ramdisk to the default one likely similar to stock kernel ramdisk which includes that sysfs node for max CPU cores.

The current ROM you're using needs a custom ramdisk.

All in all this is the problem with your configuration. I think you should talk with your ROM dev or kernel dev so the former creates this sysfs node in his custom ramdisk or the latter creates a reset "
[Nexus 7 Android Development] mlaws90:
Re: [ROM][WiFi][AOKP/CM][4.2.1] Dirty RootBox v1.0 [Aroma][Per-App-DPI][PIE][02/05]

The best I can do is tell bajee11 the developer of the base of this ROM. This may be something I can do after building from source, but I will have to look into it.
[Nexus 7 Android Development] dparrothead1:
Re: [ROM][WiFi][AOKP/CM][4.2.1] Dirty RootBox v1.0 [Aroma][Per-App-DPI][PIE][02/05]

Wow!!! It's not like M is charging us anything for these ROMs. You always have the option of using a different ROM.
[Nexus 7 Android Development] mlaws90:
Dirty RootBox v1.1 is coming and there are some bugfixes, we'll have to take a look around and see what.

The trigger area(transparent bar) below the Pie Controls is now gone. Set the Pie Controls to what ever and it wont come back. :) It is not there in the notification area or quick settings.

Also be in Phablet Mode when using Pie Controls, no reason for Tablet UI while using them.

Dirty RootBox v1.1 Changelog

Build Date: Wed Feb 6 20:32:29 CST 2013

Update Apex Launcher to 1.4.3 stable

Update Holo Launcher to 2.0.2

Update SuperSU to 1.04

Update Titanium Backup to 6.0.2

Add Camera Launcher

Bug Fix for Pie Controls

Bug Fix: now screen on/off is very fast as it should be.

-Those 2 fixes make it feel more polished and enjoyable.

Dirty RootBox v1.1 is done uploading!
[Nexus 7 Android Development] aznrice2k4:
Great job dude. Blasting out these roms like it's hotcakes. BUUUTTT Don't overwork yourself too much.
[Nexus 7 Android Development] Southrice:
But he wants to use this Rom! I know I do!
[Nexus 7 Android Development] noodles2k:
Yer, that's because it was updated after this rom was released. D'oh
[Nexus 7 Android Development] mdmar:
Flashed this one yesterday and its great. One thing not working for me tho:

when applying force landscape in Spotify via Xposed setting, nohing happens when launching Spotify? Any clues here, lads?
[Nexus 7 Android Development] mlaws90:
Yup, updated in v1.1, it was a small update anyways, small fixes and translations. :)

BTW all the Pie Control bugs seem to be fixed already so if you see any let me know. I don't see any and I turned the Nav Bar back on, change the Pie settings around and I didn't see any bugs.
[Nexus 7 Android Development] g.b.a.:
i HATE you mlaws90!!!

.

.

.

.

.

i HATE you!!!

.

.

.

.

.

Why do you have to create another great ROM while the Father of all ROMs (Dirty AOKPv4.0) is still there?

.

.

.

Now we have the God of all ROMs (Dirty RootBox)!!!

.

.

.

I have to flash every hour now... Dirty AOKP -> Dirty RootBox -> Dirty AOKP -> Dirty RootBox -> Dirty AOKP -> Dirty RootBox...

.

.

.

Which ONE?!?!?!?!?!?!?!?!?!?!
[Nexus 7 Android Development] mlaws90:
Haha thats the plan, to drive you crazy ;)

But in reality it is all about preference.
[Nexus 7 Android Development] pellatarte:
Hey guys, i'm using Dirty AOKP (I love it :)) and i would like to know if it's possible with Dirty Rootbox to force the home to stay only in portrait mode but to have the other apps to rotate as usual? (Is it also available in Dirty AOKP?!)

Thanks for your help!
[Nexus 7 Android Development] johnnyman25:
goodmorning!!can i flash it over v1.0 with wipe dalvkin cache/cache only without factory reset?
[Nexus 7 Android Development] dparrothead1:
Re: [ROM][WiFi][AOKP/CM][4.2.1] Dirty RootBox v1.1 [Aroma][Per-App-DPI][PIE][02/07]

I don't blame you, it's a great ROM. But no need to be whining and demanding. I mean, if I put this much work into something and someone post telling me what's wrong...and says "dparrothead1, please take notice".......that would be the last thing I would fix. If you know what needs to be added, then add it yourself.

I've been around XDA a while now and I've seen more than one Dev get disgusted and stop building. I just don't want to see that happen with M.

Sorry, rant over....:D......and in the words of Forrest Gump ..."That's all I have to say about that".
[Nexus 7 Android Development] dstryrwiz:
I meant to take notice as it's a potentially big bug and I wasn't quoting anything from him, so I wanted him to know I was directing my post to him, not to be obnoxious. The fact that the ROM is causing kernel features not to work is a little worrisome to me, and I know I can't be the only one using M-Kernel in this group, and I would assume the same problem would exist on Franco Kernel as well, as they both use custom ramdisks and it seems this ROM may be messing with it. And the only reason I mentioned the Xposed update was because I thought it was an oversight. I used to do a bunch of beta testing for Omega_Kaos, helping him identify oversights like that, or identify bugs before he would bring the release to the public, as well as suggesting ways to make the ROM better, and it was always happily received, yet due to heavy time commitments in real life, he has stopped developing, so I had to move to a new ROM and the feature set in this ROM I really like, but I do hope to be able to use all the kernel features of M-Kernel as well, as I'm sure others would like as well.

---------- Post added at 06:44 AM ---------- Previous post was at 06:38 AM ----------

Thank you. Sorry if I came off demanding at all, I was just trying to call it to your attention as this definitely appears to be a ROM related issue in interacting with the kernel causing one of the two to break no matter what I do. In the meantime I'm running M-Kernel over this ROM but I question how many other M-Kernel features besides adjusting max CPU Cores may be malfunctioning behind the scenes if that feature is visibly broken.

---------- Post added at 07:31 AM ---------- Previous post was at 06:44 AM ----------

Sorry for posting another thing that I'm not quite understanding how to fix. I'm trying to update to v1.1, but if I dirty flash this, which I would assume would be allowed, all of my per app DPI settings are listed, but none are actually in effect. Am I missing something, or well I need to clean flash each time with this ROM and set up those settings fresh each time?
[Nexus 7 Android Development] ayanamirei33:
I dirty flashed v1.1 and didn't lose my per-app settings but I did have to install Xposed and reboot again...

(on another note, I hope the banging ends here.. I've had enough of that on another thread... People are just reporting bugs/problems... Not demanding anything... :D)

Love this ROM... Thanks! :good:
[Nexus 7 Android Development] dstryrwiz:
It's weird, for some reason it's showing my per-app settings, but they won't implement, and I don't understand why.
[Nexus 7 Android Development] johnnyman25:
Απ: [ROM][WiFi][AOKP/CM][4.2.1] Dirty RootBox v1.1 [Aroma][Per-App-DPI][PIE][02/07]

Here s my battery life using dirty root v1.0 and franco kernel r42.is it good?also i make 2-3 reboots.

Sent from my Nexus 7 using Taptalk HD

Dirty Root Box v1.0 & Franco Kernel r42
[Nexus 7 Android Development] mlaws90:
Make sure the Xposed Installer is installer after the update, you have to redo this on an update. Then make sure on the modules tab that the App Settings module checked.

Looks good to me. :)
[Nexus 7 Android Development] Botloos:
I flashed Dirty AOKP last week, liked it alot, gonna flash Dirty RootBox in a sec, hope im gonna love it even more!

(dont think that i will be dissapointed seeing all the loving words here...)
[Nexus 7 Android Development] luxifr:
Just wanted to applaud to the developer of this fine ROM... I had Glazed JellyBean before and was quite happy with it but it's abandonned and I wanted to upgrade to 4.2.

Now at first I tried an other ROM (which I don't want to discredit so I'm not naming it here) which, by the claims of its developer, was supposed to be the smoothest and best ROM around ("you can't find a smoother JellyBean ROM!" blabla) and it was pretty ****ty to be mild about it. Like freezing every other moment for a few seconds and stuff.

Then I tried this ROM here and what could I say? I'm amazed... You did a great job with this ROM. It's feature-loaded, stable and the fastest ROM I've used yet on my Nexus 7 (and it's been quite some). I'll keep it... Thanks man!
[Nexus 7 Android Development] mo8175:
AW: [ROM][WiFi][AOKP/CM][4.2.1] Dirty RootBox v1.1 [Aroma][Per-App-DPI][PIE][02/07]

I have a problem when tapping Brightness or "my picture" in Quicksettings. My System-UI got close when I tap it, I have this bug only on these two.
[Nexus 7 Android Development] flyguy914:
Re: [ROM][WiFi][AOKP/CM][4.2.1] Dirty RootBox v1.1 [Aroma][Per-App-DPI][PIE][02/07]

Is anyone else getting this? I have to keep one finger on the resents button and simultaneously use my other hand to be able to change between apps
[Nexus 7 Android Development] noodles2k:
Not sure there's much point in having torch.

I think that's a bug in rootbox.

Not having that here.

---------- Post added at 08:05 PM ---------- Previous post was at 08:01 PM ----------

Don't be silly :silly:
[Nexus 7 Android Development] dparrothead1:
Re: [ROM][WiFi][AOKP/CM][4.2.1] Dirty RootBox v1.1 [Aroma][Per-App-DPI][PIE][02/07]

No problems with these.

I asked RootBox if there are plans to add a second layer to pie and they said no. :(
[Nexus 7 Android Development] noodles2k:
I think the fc only happens in tablet mode.
[Nexus 7 Android Development] dstryrwiz:
Well I come from an audio engineering background and in Pro Tools if you actually see a recurring issue than it usually means the program is likely to fail entirely shortly, which would require a full computer wipe to get it working again, so when I see a bug like that which makes no sense it raises a red flag for me. I don't code for Android, so I don't know what would be causing that or how it may be impacting other kernel functions behind the scenes.

---------- Post added at 03:59 PM ---------- Previous post was at 03:57 PM ----------

I did both and no luck. I asked the developers at Xposed the same thing and got the same response, but I have no idea why it's not working then.
[Nexus 7 Android Development] noodles2k:
I bet the tech support guys just love you.
[Nexus 7 Android Development] johnnyman25:
Απ: [ROM][WiFi][AOKP/CM][4.2.1] Dirty RootBox v1.1 [Aroma][Per-App-DPI][PIE][02/07]

Guys the kernel script cleaner deletes the init.d file?i read that this script deleted the init.d file tha possibly includes rom tweaks.

Sent from my Nexus 7 using Taptalk HD

Dirty Root Box v1.1 & Franco Kernel r42
[Nexus 7 Android Development] dstryrwiz:
It does.

---------- Post added at 05:18 PM ---------- Previous post was at 05:16 PM ----------

I rarely speak to tech support as anything they can help me with I either can easily figure out myself or find quickly online, whereas any serious issues they're clueless about anyway.
[Nexus 7 Android Development] johnnyman25:
Απ: [ROM][WiFi][AOKP/CM][4.2.1] Dirty RootBox v1.1 [Aroma][Per-App-DPI][PIE][02/07]

Does this rom have init.d tweaks?

Sent from my Nexus 7 using Taptalk HD

Dirty Root Box v1.1 & Franco Kernel r42
[Nexus 7 Android Development] noodles2k:
Good work. :good: you do reimage your system rather than reinstalling everything right?

Yes it does.

I'll check the script, but if it really does completely wipe /etc/init.d the guy who wrote it should be shot.
[Nexus 7 Android Development] johnnyman25:
Απ: [ROM][WiFi][AOKP/CM][4.2.1] Dirty RootBox v1.1 [Aroma][Per-App-DPI][PIE][02/07]

I used the kernel script cleaner cuz i have issue with trickster mod not sawing cpu temp and max active cpu cores.after using script kernel cleaner and installed m-kernel cpu temp and max cpu cores was back in place.now i cant find init.d file.what can i do now?thx.

edit:so now i must dirty flash rom again to get init.d folder back?pls someone answer.. :)

Sent from my Nexus 7 using Taptalk HD

Dirty Root Box v1.1 & Franco Kernel r42
[Nexus 7 Android Development] ezas:
Re: [ROM][WiFi][AOKP/CM][4.2.1] Dirty RootBox v1.1 [Aroma][Per-App-DPI][PIE][02/07]

I can't set the Automatically lock timeout under Screen Security to anything other than 5 seconds. Is anyone else seeing the same thing?

View attachment 1712219
[Nexus 7 Android Development] Jaydizzle414:
Re: [ROM][WiFi][AOKP/CM][4.2.1] Dirty RootBox v1.1 [Aroma][Per-App-DPI][PIE][02/07]

So is there any alternative to keep all cores enabled?
[Nexus 7 Android Development] chopt51:
Re: [ROM][WiFi][AOKP/CM][4.2.1] Dirty RootBox v1.1 [Aroma][Per-App-DPI][PIE][02/07]

It says multi boot support. What does that mean? I have not looked much into multi boot but I thought all ROMS would work.

Sent from my Nexus 7 Dirty RootBox
[Nexus 7 Android Development] noodles2k:
I've found why the CPU settings aren't present in Trickster. It's due to one line in the KingBeatz script which unmounts /sys/kernel/debug.
[Nexus 7 Android Development] ezas:
Re: [ROM][WiFi][AOKP/CM][4.2.1] Dirty RootBox v1.1 [Aroma][Per-App-DPI][PIE][02/07]

You want to keep all cores enabled, or you want an alternative to being able to disable some of the cores? I assume the later, but the way you worded your sentence is vague on which you mean.