yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] zaclimon:
Depends on what build and kernel you took. You would be better taking latest stable builds to see if it works, then if it doesn't come back. I'll try to see what's the problem.

Envoyé depuis mon Nexus 7 avec Tapatalk 4
[Nexus 7 (2013) Android Development] GTMoraes:
Stock ROM works nice. I'll try PAC ROM with Faux kernel (I'm using ElementalX 1.8)

It's also worth noting that the device did not even heat up during the whole benchmark. It used to get hot on 1/3th of the 1st pass (there are three passes)

Sent from my Nokia 1100 using Snake II
[Nexus 7 (2013) Android Development] mohammed510:
Same on PAC + faux

Real boxing is not as smooth as b4

CPU/GPU throttle maybe ??

Try PAC man kernel

Edit: same on PAC man kernel

Real boxing is not smooth,

Noticed that CPU temp doesn't go above 60 C

Edit 2: stock PAC kernel is fine.
[Nexus 7 (2013) Android Development] GTMoraes:
I couldn't even boot on Faux kernel. It glitches the hell out even before the mainscreen.

I've used the "flo-jb-kernel-CAF-007m_r2.zip" file. Can you confirm me this is the right one? [MENTION=4475938]mohammed510[/MENTION]
[Nexus 7 (2013) Android Development] mohammed510:
The normal version will boot the rom

The CAF version which is for CM roms will not boot!!
[Nexus 7 (2013) Android Development] Krowbarr:
No, you need to use the non CAF Faux kernel. Pacman is AOSP.

☞Owner/Operator Samsung E4GT running Dirty Unicorns 4.3.1 Powered by Blasphemy!

We were born in a time where if something was broken we would fix it and not just throw it away
[Nexus 7 (2013) Android Development] GTMoraes:
Oohhh.. so that's why no kernel worked here.

omg so many options now lol
[Nexus 7 (2013) Android Development] zaclimon:
Yeah if you used a caf kernel, then naturally you need to shift to an aosp compatible one. (like elementalx or faux for aosp)

Envoyé depuis mon Nexus 7 avec Tapatalk 4
[Nexus 7 (2013) Android Development] GTMoraes:
Well, after some tests:

Full wipe, then Stock ROM: Works fine

Full wipe, then Stock PAC-man ROM: Glitches

Full wipe, then PAC-man ROM with Faux123 kernel: Takes a little longer, but glitches.

PAC-man ROM with Faux123 kernel w/ tweaks: a lot, I mean, A LOT less glitchy. But glitches.

So I guess it's the PAC-man who's the culprit? Missing video drivers, GPU thermal throttling too exaggerated or something?

----

Moar tests!

It seems to be the thermal throttling.

Although I've set it to throttle on 70ºC, it seems to be throttling around ~55ºC, even though the default throttling is at 60ºC. It is set to throttle at 70ºC but seems like it's ignoring it.

I've increased the CPU voltage to reach the said temperature faster, and indeed it happened faster.

Even setting to über temperatures (throttle at 110ºC), it still throttles around 55ºC. Is it hard-defined somewhere into the ROM?
[Nexus 7 (2013) Android Development] mohammed510:
Or the app is just not fully compatible with android 4.3.1 yet?!

Stock pac man is fine here

I had some graphical glitches with faux only.
[Nexus 7 (2013) Android Development] GTMoraes:
Unlikely, as I tested with a 4.3.1 stock ROM and it worked!

I edited my previous post, read there! Seems like the thermal throttle messed up

----

I've DISABLED thermal throttling, and it is still throttling it. It's even saying "overtemp" when it reaches 60ºC
[Nexus 7 (2013) Android Development] mohammed510:
Yes I've been there

Just flash stock pac man and everything should be back to normal like mine did

You might want to reboot twice and forget about Anomaly 2 :D
[Nexus 7 (2013) Android Development] borxnx:
Foot in mouth, did not read last page
[Nexus 7 (2013) Android Development] GTMoraes:
I've tried forgetting about it, but every other graphic-intensive game/app will demonstrate the same glitch one time or another!

Anomaly 2 just makes it happen faster.

I'm still getting issues with default PAC kernel, as I said before =\

I've tried to make the thermal throttling virtually disabled (set to throttle at 110ºC), but no dice.

The only one that works flawlessly is the stock ROM, and I don't want to use it =(

----

oooo, I set it to throttle at 60ºC and rebooted. It didn't glitch during the benchmark!

omg, I think it only applies after reboot

----

SystemUI FC bug..

In the past, when it FC, it used to be able to recover itself. Now it'll be FC'ing until you reboot =(
[Nexus 7 (2013) Android Development] BWA80:
Hi!

I've installed the latest RC with a full wipe now 3 times and tried to restore my titanium backups, but everytime i try to restore it just hangs at 0% and does nothing...

Anybody have any idea why?

Thanks!
[Nexus 7 (2013) Android Development] katsooba:
Hi guys,

on latest nightly i noticed something "new" happening with the rom when connecting my DAC.

i know no USB audio is supported, but i keep trying that maybe on some nightly it will come on.

untill now i was connecting my DAC to the N7 and nothing happened, device just worked usualy, but no sound from speakers nor DAC, meaning something is recognized, but audio is not getting routed through the dac.

the new symptom is - when i try to play mp3\vid\youtube when dac is connected, the vid\song is just stuck on freeze, no movement or sound whatsoever.

this is the dac i use

http://hifimediy.com/index.php?route=product/product&product_id=83

its working on my pc and even on my families older nexus [2012] so i dont think its the DACs fault.

the reason i think its a new symptom is because maybe the audio\usb got touched, which means its a good thing :) maybe progress is being made!

cant wait for the USB audio to start working.
[Nexus 7 (2013) Android Development] BWA80:
Ok,

I installed supersu app from the store and tried to restore TB again, now it worked. There is somekind of problem with PAC stock superuser on the latest RC?

Edit:

Installed latest nightly and TB is restoring, i'll stay on this if it feels good.
[Nexus 7 (2013) Android Development] zaclimon:
As I've said some pages ago, USB audio depends on the kernel and we use the stock kernel so it will not support it as of now. I'm trying to find how CM made it possible.

Envoyé depuis mon Nexus 7 avec Tapatalk 4
[Nexus 7 (2013) Android Development] borxnx:
Foot in mouth again. I should really start making sure I've read the entire thread. FML
[Nexus 7 (2013) Android Development] GTMoraes:
hey [MENTION=4217103]zaclimon[/MENTION], I'm still getting some weird glitches on games around here, and everything points out to thermal throttling.

Although I've set the thermal threshold to 70ºC, it throttles at precisely 55ºC (as noted "throttled" on Faux app)

Who in the world is forcing this value?! Does PAC ROM have any hardcoded setting regarding to that?

---------- Post added at 02:53 AM ---------- Previous post was at 02:15 AM ----------

Hey, why is "Disable HW Overlays" option marked? That's the whole Project Butter out of the window with this little box marked. I'm experiencing a LOT less glitches (sometimes none at all) with it unmarked. But everytime I reboot, it is marked again
[Nexus 7 (2013) Android Development] SilentException:
Hi, just flashed this yesterday and I'm amazed at all the customization options there are. Currently setting everything up but hit a few brick walls on the way :)

I cannot seem to disable "Google Pacman" app in the settings. Button is grayed out. Why is that? I don't need this game...

Are there Animation Control settings that I can use to get as close to stock as possible? Amount of options and combinations in that screen is overwhelming. For now I used 250ms Animation Duration only and it's better but there is too much window sliding IMHO.

It would be nice to be able to revert to stock Nexus boot/restart/shutdown animations. I understand the PACMan is the theme here but these animations feel a bit silly, nhf. You either love it or hate it, that's why I'm asking for simple switch to stock :)

And lastly, after going from app to home, widgets seem to disappear from time to time and my home screen is empty. They draw themselves after going in the app drawer and back but it's probably something you should look at. I'm using PIE and it seems to be happening only when PIE is enabled.
[Nexus 7 (2013) Android Development] GTMoraes:
Hey.

About the animations, you can always go to Developer options on system tab and edit the animation speed there. Also, everything else there is for debugging, so there's no need to fiddle around, as it may only make your device slower.

You can change the boot animation. Google for Nexus 7 2013 boot animation and choose your flavor

I'm using PIE and I never experienced this bug. Try using a different launcher perhaps?
[Nexus 7 (2013) Android Development] SilentException:
Spoke too soon, it does not seem related to pie. Also happens without it. I think I have pretty good idea when the bug happens (running default launcher)

1. From app drawer open app or open app switcher and select running app.

2. Press home.

3. Home will be visible without widgets

4. Going to app drawer and then back redraws widgets.
[Nexus 7 (2013) Android Development] BWA80:
Hi!

Is there anyway to speed up screen rotation? It would be nice that it would rotate immidietly.

Thanks!
[Nexus 7 (2013) Android Development] goldflame09:
um........... no

sorry it takes a whole 1 second for it to rotate

edit: to be honest, it does that so if i slightly tilt my device, it doesnt rotate on me

---------- Post added at 05:57 PM ---------- Previous post was at 05:49 PM ----------

no issue here
[Nexus 7 (2013) Android Development] SilentException:
Vid showing the problem:

https://db.tt/Qkt7BAZO
[Nexus 7 (2013) Android Development] goldflame09:
does that only happne with pie? and are you using trebuchet?
[Nexus 7 (2013) Android Development] SilentException:
Same thing happens without PIE. Launcher is ROM default, Trebuchet yes.
[Nexus 7 (2013) Android Development] goldflame09:
can you try another launcher and see what happens?
[Nexus 7 (2013) Android Development] SilentException:
Nova is working OK. So the culprit is Trebuchet?
[Nexus 7 (2013) Android Development] goldflame09:
i would say so. stick with another launcher for now
[Nexus 7 (2013) Android Development] JoeBruin32:
I've had this exact problem in every release of PAC DEB I've tried. I just assumed this was a known bug everyone was dealing with. Guess I should try a new launcher too.
[Nexus 7 (2013) Android Development] agentafter:
The way I solved the provlem of the launcher not redrawing was changing my launcher. Now I use Apex, and it works flawlessly.
[Nexus 7 (2013) Android Development] TriforceKommando:
Anyone else has this? (See at the lower end of the display)

The navbar consumes some space from the active app. Fullscreen Mode can help with this, but is there any better solution where I can still use the navbar in the app?

Im on pac_flo-nightly-20131021

Regards!
[Nexus 7 (2013) Android Development] GTMoraes:
I had an app that you could slide the navbar up and down, but I found out that using PIE is rather more useful (specially setting it to always stay on your dominant hand)

Can't really reminisce the app name, but I used Xposed to hide the actual navbar.

The app icon had a black background with a red "home" button (the one on navbar).

It featured fully customizable buttons actions and icons, and used virtually no resources.

Try googling for auto-hide navbar
[Nexus 7 (2013) Android Development] TriforceKommando:
The thing is: I don't want to hide the navbar, just to see the app. :D

On a Samsung i9100 with PAC it work normally..
[Nexus 7 (2013) Android Development] jdagreek:
why did the files size on the latest Nightly shrink so much ?
[Nexus 7 (2013) Android Development] goldflame09:
Focal was removed. dl it from playstore if you want it
[Nexus 7 (2013) Android Development] dobbs3x:
I had a similar bug on pac rom on my HTC one m7spr phone. If I waited a little bit the icons seemed to come back eventually but, using nova launcher I didn't have the problem. Sounds like a base problem?
[Nexus 7 (2013) Android Development] jdagreek:
focal is not 100 MB something else must have been removed also ?
[Nexus 7 (2013) Android Development] Krowbarr:
I don't think latest nightlies are building correctly. Obviously would have to be more than 100mb.

Owner/Operator Nexus 7 2013

We were born in a time where if something was broken we would fix it and not just throw it away
[Nexus 7 (2013) Android Development] zaclimon:
Looks like something is wrong indeed because the 02/11 nightly should be 168 MB instead of 143. Perhaps it's a bad upload.
[Nexus 7 (2013) Android Development] goldflame09:
the 11/02 build is 160ish mb. thats normal. last nights wasnt so im checking it now
[Nexus 7 (2013) Android Development] Poke_N_PDA:
so I'm trying to back everything up and get back to stock for 4.4. However, I've got multiple users and I'm having issues. I found the multi-user root settings, but I've having serious issues as the Play store keeps crashing in my secondary user. WTF? I've reboot and it still did it.
[Nexus 7 (2013) Android Development] zaclimon:
Well what do you want to backup first? Because by the looks of it, it seems like you want to backup your play store app which looks strange o.O

Envoyé depuis mon Nexus 7 avec Tapatalk 4
[Nexus 7 (2013) Android Development] Poke_N_PDA:
I needed play spot to get the backup apps on her profile. I got that working, but now I'm hiring another problem. PAC settings don't work. For some reason PAC disables the tee button menu key by default. Now I can't get into the titanium properties because I can't get the menu button enabled. I am so tired of this rom.
[Nexus 7 (2013) Android Development] zaclimon:
Geez I think i'll put something regarding the 3 dots on the OP. But to enable it go onto general UI, then check enable 3 dots menu overlay. You should have the menu thing in titanium.

Envoyé depuis mon Nexus 7 avec Tapatalk 4
[Nexus 7 (2013) Android Development] katsooba:
Is it so hard to go under settings and look for the options?

First thing i did after flashed the pacman rom was clicking on every possible option on setting just to get to know the rom.

took me 10 mins to round it all up.

How can you be tired when you are so lazy
[Nexus 7 (2013) Android Development] Poke_N_PDA:
Maybe spend more time reading my post and less time insulting me. Notice where I said "PAC settings aren't working"? I do apologize that I didn't elaborate, but here's the deal. I can't change this setting in my wife's profile because PAC settings are completely blank. In her profile, I go to settings, swipe to the right, and it is completely blank. Unfortunatly I can't take a screenshot because I can't get to the settings to enable it.

Finally, what I'm tire of is the insane amount of bugs in this rom. Listen, I know that lots of people spend LOTS of time working these things and we get it for free. I'm not ungrateful, I'm just moving on that's all. This rom will require a lot more time to really be stable, so I'm moving on. Is that so bad?

---------- Post added at 07:07 PM ---------- Previous post was at 06:57 PM ----------

Thank you for very polite and helpful response. However, my issue isn't that, it's that the PAC settings in settings is completely blank on my wife's profile. For mine (the primary), it is fine, but her's is having serious issues. trebuchet is crashing constantly, I had to unistall all updates to get the play store to work, and I still can't get PAC settings working. FYI, I'm running the 1102 nightly. I was running the 1026 stable build.

FYI, I do want to say thank you for your hard work and please don't take any offense to my frustrations. I can't imagine trying to do this myself. You have accomplished quite a lot getting these roms merged.
[Nexus 7 (2013) Android Development] zaclimon:
Trebuchet that is always crashing is not normal something probably gone wrong somewhere, I don't know if you can confirm that but can you test am earlier build to see if the issue repeats itself? (looks it was fine before running the newer nightly)

As for the secondary user settings issue, I'll ask the devs to see if the said user can get access to them. AFAIK the nightlies can be around the edges regarding features and bugfixes.

EDIT: I got a response for the secondary user issue, well it's not really an issue as the user should not be able to access PAC settings. Sorry for any inconvenient caused by this.

Envoyé depuis mon Nexus 7 avec Tapatalk 4
[Nexus 7 (2013) Android Development] Poke_N_PDA:
First off, thank you again. You are being exceedingly helpful. It's amazing for a dev to take such an interest in helping a user.

As for the info, that is really interesting. I have to say I'm curious how I'm supposed to change this setting for my wife so I can use the menu options. I've long since changed it for my profile, but that does nothing for her's. Weird.
[Nexus 7 (2013) Android Development] zaclimon:
I've found a workaround that worked for me. If you have root access for the second user, you can download xposed framework then use the modaco module here:

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

It has an option to activate the 3 dots menu which I confirmed worked with titanium backup.

Hope it helps!! :p
[Nexus 7 (2013) Android Development] gchild320:
:banghead:
[Nexus 7 (2013) Android Development] goldflame09:
Comments like this are unneeded ;)
[Nexus 7 (2013) Android Development] GTMoraes:
Hey, is it the ROM or the Kernel who's enforcing the "Disable HW Overlays" in Developer Settings? This setting enabled is, in short, disabling the Project Butter, as it is giving graphic intensive apps unnecessary glitches.

At every reboot, This setting is ticked. Why is that?

Tapatalked thru my Sexy Nexy7
[Nexus 7 (2013) Android Development] zaclimon:
I don't know in which nightly you're in but as for myself, it isn't tickled at boot. The kernel doesn't have a role in this. Have you tried flashing another build or wiping data? Perhaps it's something you did or something related to the rom that is enabling it by default.

Envoyé depuis mon Nexus 7 avec Tapatalk 4
[Nexus 7 (2013) Android Development] GTMoraes:
That's weird. I'm on 10/31 build, installed fresh. I didn't install any ROM modifying apps and only used the resources it presented to me.

Idk what might have triggered it. How can I find it out?

And I think I found a little bug: Setting DPI manually for any app on Hybrid Settings (with expert mode enabled) forces the color setting, even if it's unmarked. You can see the enforcing on that on /system/etc/paranoid/properties.conf and looking for the app you've just modified.

A workaround for it is to wipe the color info manually on the .conf file.

Tapatalked thru my Sexy Nexy7
[Nexus 7 (2013) Android Development] Poke_N_PDA:
Ok, because I was still having problems even with your suggestions (you've been awesome BTW) I just went a different rout and paid the 3 bucks to get my backup pro. I haven't restored it yet for my wife, but I think it will work. Thanks for all your help again!!!!
[Nexus 7 (2013) Android Development] deeevan:
I'm experiencing both of these. I updated my conf file thinking your comment meant the 2 issues were related :p

I'm on the 10/26 RC build. I wiped data and system before installing ROM and gapps. I'm thinking it must be settings related if we're both seeing and others aren't.

Edit: I took a guess at what would affect HW overlays and disabled PIE. The setting stuck after reboot and was lost after re-enabling and rebooting. Will do further testing as see if it's a specific setting like having the PIE control following my finger instead of centred.
[Nexus 7 (2013) Android Development] GTMoraes:
Hehe, they are two different bugs.

I've did what you said, disabled PIE, rebooted (actually went through a different bug. I'll detail it later) and the Disable HW Overlays wasn't ticked.

Enabling PIE was enough to tick it again, a reboot wasn't necessary. My guess it's that the PIE dev was debugging something and forgot this enabled.

And the other bug I'm experiencing, but Idk if it's related to the ROM or Kernel. If I press the power button and quickly press it again (while the screen turning off animation is being displayed or shortly after), it doesn't wake up anymore.

Actually I think it does wakes up, because I received a notification and I heard the sound, and pressing the power button once again made the LED to blink, to reminder a notification (like if the screen were off normally). Pressing power button again makes the LED stop blinking as if the screen was on.

Only way to definitely wake it up is to press and hold the power button for a restart.

Could someone try to reproduce this?

-----

Even I had a hard time trying to reproduce it, so I made a video. I'll upload soon.

It seems to happen shortly after/before the screen lock.

Tapatalked thru my Sexy Nexy7
[Nexus 7 (2013) Android Development] deeevan:
I flashed the 11/04 nightly, toggled PIE off and on and Disable HW Overlays stayed off.
[Nexus 7 (2013) Android Development] GTMoraes:
Updated and the bug is still there. Is yours Developer Settings enabled?

Tapatalked thru my Sexy Nexy7
[Nexus 7 (2013) Android Development] deeevan:
I just rebooted and it's back. It just doesn't enable when you enable PIE (which I'd never noticed until you told me)
[Nexus 7 (2013) Android Development] GTMoraes:
God, I played Asphalt 8 here and I wanted to throw the tablet on the wall.

Please, someone try to play it (it's free now, Idk for how long). It'll lag and glitch the whole race. I've made sure that Disable HW Overlays wasn't ticked, but it still glitched.

Does this ROM use generic graphic drivers or something?

----

Setting it to Medium settings reduces the glitches, but an occasional lag and glitch still happens.

Heats up and throttle more than the stock ROM too.

Are those AOSP/CM ROMs using different drivers than the Stock ROM or is it just me?

Tapatalked thru my Sexy Nexy7
[Nexus 7 (2013) Android Development] Bumper03:
I'm using it with ElementalX kernel (oc'd to 1728 MHz, otherwise everything is default ) and the Asphalt 8 runs smoothly with high settings.
[Nexus 7 (2013) Android Development] goldflame09:
Guys this is just i small little FYI, but dont expect your issues (if you have any), to be taken as seriously. For your issues to be taken as seriously, you must be on the stock kernel and have tried a data wipe to solve your issue. Thank you

Im not saying you [MENTION=5001786]Bumper03[/MENTION] are having issues, this is just a heads up for all of you.
[Nexus 7 (2013) Android Development] GTMoraes:
For me, it happened on Faux123 kernel and PAC stock kernel (reflashing the ROM reinstalls the stock right?)

The stock N7 ROM didn't heat or stutter during several passes of a heavy benchmark, in which PAC heats up 1/4 the way and stutters a little (with Enable HW Overlays disabled) on the first run.

Idk what to do. I don't wanna leave PAC

Tapatalked thru my Sexy Nexy7
[Nexus 7 (2013) Android Development] goldflame09:
And thats fine, its just fir those who haven't tried on stock kernel at all.

As for that problem, it may be ram but I doubt it. Pac does take more ram than most roms and absolutely more than stock
[Nexus 7 (2013) Android Development] GTMoraes:
I don't think so. The game runs on medium settings but just glitches on max, which I presume it could run maxed on stock...

I've always got plenty of free memory. It's 2gb for God's sake lol.

Are the drivers generic?

Tapatalked thru my Sexy Nexy7
[Nexus 7 (2013) Android Development] goldflame09:
Updated:

New flo and deb stable builds are up. should have no problems but you never know....

enjoy. links are in op
[Nexus 7 (2013) Android Development] deeevan:
Is this right?

md5sum pac_flo_4.3.Build-1_20131105-191851.zip

912cdcc8f5c0d1ccf9df0cf5653eb495

I get 'Unfortunately the process com.android.phone has stopped' on start up, and I can't proceed.

First attempt: Dirty flash

Second: Wipe data/system reset, format /system, install zip

Third: Redownload, repeat steps from second attempt