yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy Note I717] thaiceman:
I haven't seen any of the known bugs with the 21 yet but I'm only at 20ish hours up time.

So far the keyboard/gallery/system ui/and random app closes are gone hell it's even waking up right.
[AT&T Samsung Galaxy Note I717] AD5GB:
Bumpy ride...

It's been a very bumpy road for PAC on quincy devices the last few weeks. CM making changes to CAF and core framework stuff is just killing us. Nightly builds stopped now for a couple days until all these code merges can get sorted out and built. It's crazy busy all and PAC is definitely not at it's best. I'm planning a fork of kernel code at some point soon and am going to work toward bringing some aspects of it up and cleaning some of it up. Not sure how this will go timeframe-wise just yet. Focus right now is getting stuff to build again. None of PACs 100+ devices are building right now...... just hang tight.
[AT&T Samsung Galaxy Note I717] :
I guess by then something exciting would be out :D
[AT&T Samsung Galaxy Note I717] pTeronaut:
A while back I posted mentioning that setting screen DPI to 200 and layout to Tablet resulted in Settings to FC whenever I attempted to open it, well, on a whim, I installed the 10-21 build and tried again. Settings still FCs. Which I at the time thought was due to the pagination of Settings that is present in the PACman ROM.

So ... I wiped and reinstalled and tried out a hunch...

When faced with the reboot request dialog that appears after changing UI mode, I canceled and went into PA Prefs' Apps, and set "Settings" layout to 720, then rebooted. Once my phone was up and running, I tried to open Settings, with success and was faced with a regular Dual-Pane settings.

D'Oh! I could have been using this ROM for a while.
[AT&T Samsung Galaxy Note I717] sp73smith:
Any idea on when builds are going to stop failing?
[AT&T Samsung Galaxy Note I717] :
The latest nightly (27/10) is out now!
[AT&T Samsung Galaxy Note I717] Teseract666:
Flashed 10/27 earlier this evening hoping it would fix my random reboots when the phone rang or when a text came in and my issues with having to toggle Bluetooth on/off several times to get it to change state. Unfortunately, now I can't even dial out, the dialer just crashes. I ran fix permissions just as a long shot, didn't have any effect, I'm restoring to backup.

Might just be my phone, but an FYI to anyone who flashes it you may want to test and make sure it works before you have to dial 911 or call your Mom or something. :)
[AT&T Samsung Galaxy Note I717] :
It's a ROM issue, other devices are also having it
[AT&T Samsung Galaxy Note I717] Teseract666:
Thanks for the heads up. Unfortunately the backup I made before flashing it somehow got corrupted and fails the MD5 check when I try to restore it. Had to flash back to an old 10/23 backup, I hope I'm not missing too much. This is what I get for messing with nightlies I guess. :)
[AT&T Samsung Galaxy Note I717] :
Do you use TWRP? TWRP is more reliable, and it can skip MD5 checks.
[AT&T Samsung Galaxy Note I717] Teseract666:
Yeah I'm using TWRP. I suppose I could try skipping the MD5 check, I just figured I'd be asking for trouble if I did.

---------- Post added at 04:03 AM ---------- Previous post was at 03:57 AM ----------

Tried skipping MD5, the restore still failed. Oh well, 10/23 is a good vintage I suppose. I've never had that happen before, it's pretty weird but that's my luck.
[AT&T Samsung Galaxy Note I717] bongra80:
27 build been working great for me but for some reason we still not having torch in our toggle!
[AT&T Samsung Galaxy Note I717] AD5GB:
They are running again though lots of work to be done yet. Phone, dialer, trebuchet, SystemUI FC's. Lots of code base changes in process for PAC right now. 3.0x kernel has been EOL'd too so I'm going to be stepping up work on it. Had I known this would become a full time job...., :D

It will start getting better very soon. I'm as impatient as everyone.
[AT&T Samsung Galaxy Note I717] AD5GB:
Yep. It disappeared again. Looking into getting it back.
[AT&T Samsung Galaxy Note I717] AD5GB:
Disable PAC in Black for the time being.....
[AT&T Samsung Galaxy Note I717] AD5GB:
Kernel Testing...

Hey all,

Well through all the craziness I managed to find time to get my initial kernel mods integrated and tested. It's at version 3,0.100 and based heavily on parts of UBER with some updates from mainline Linux code, Google Android code and my own modifications. I'll probably not put too much into this version since 3.x is marked EOL but rather focus on newer code branches and more of my own enhancements. If you're willing to test it you can find it at the link below. (wait till the upload finishes though :D ) I've been running it several hours without issue but there are undoubtedly bugs. Feedback with details are most welcome and important to refining the thing. If possible, when making error reports include logcats, kernel settings (scheduler, governor etc.) and what you were doing when it happened. I plan to integrate this into regular builds when it proven to be no less stable than the standard CM kernel. You can alter some of the configs in the performance menu or with Trickster, Andromizer or any other similar app. More features will be in upcoming versions. Just flash the ROM as usual and have fun.

Here's the link: http://pacman.basketbuild.com/download.php?file=main/quincyatt/kernel_testing/pac_quincyatt-4.3-20131030-Android-3.0.100.zip
[AT&T Samsung Galaxy Note I717] xZeroMancerx:
Hey AD, you said this new kernel ran w/o issues but how's the screen delay ? Have you managed to fix this ? Will this kernel work with other 4.3/4.3.1 ROMs or is it specific to only PACman ROMs
[AT&T Samsung Galaxy Note I717] AD5GB:
Screen delay? You mean the one that occurs if a lock screen is used? Not sure yet. Haven't seen that on mine yet but I didn't all the time. This kernel would work on any 4.3 ROM AFAIK but is not packaged separately yet. I've integrated it into the PAC build for AT&T and TMO Note 1 devices. There may come a time very soon when moving up to 3.4, 3.7 or 3.10 where device code will need to change. Meaning drivers for hardware. The integrated approach simplifies this.
[AT&T Samsung Galaxy Note I717] xZeroMancerx:
Yes thats what I mean ad...the lockscreen issue...
[AT&T Samsung Galaxy Note I717] AD5GB:
I haven't seen that with the new kernel yet. I'm guessing its fixed.
[AT&T Samsung Galaxy Note I717] xZeroMancerx:
Ahh no Jamie's got to add a few changes to -100...pretty sure he's got a lot going on...Can't say I know of many who make developing a full time job other than scuba Steve K.
[AT&T Samsung Galaxy Note I717] AD5GB:
Try it! Been working perfectly for 3 days now.
[AT&T Samsung Galaxy Note I717] Poriotis:
Fixed you say? Well, let me do the honors of verifying that :D

I'll report back.
[AT&T Samsung Galaxy Note I717] AD5GB:
Please do! Make sure you grab the kernel_test version and not the official nightly. I have not yet integrated this source into the nightly builds.

I know I said I wasn't doing any more work on the 3.0x kernel branch but have decided to bring my kernel up to 3.0.101 - the final version. Then I'll focus most likely on 3.10.
[AT&T Samsung Galaxy Note I717] Poriotis:
I didn't get too far. After installing, all went well, adjusted settings and reboot phone. After the reboot, I installed updates and a few other apps and then reboot. Since that reboot, the phone went into a boot-loop. :( Removed the battery and tried again but no luck, got stuck on boot-loop. Eventually had to wipe and restore previous ROM.
[AT&T Samsung Galaxy Note I717] xZeroMancerx:
Actually I tried following this link but it just lead me to an empty page with an error to server but I haven't tried again so maybe that kink was worked at...BTW Jamie follows another user, I think he based his kernel source on another device,similar to our note but not the sensation. Something about adding a few changes to the -o3....check his thread,I forgot which thread

Picked from jamied81's uber kernel page

I appreciate your report because I wouldn't have noticed this issue had you not posted. It isn't actually a "bug" or a "problem" it is simply that the kernel has become outdated already. CM introduced new GPU drivers into the kernel about a week or so ago. I've updated the kernel to 3.0.101 and merged the CM gpu updates. I also changed the compiler flags to -O3 Optimization for improved performance with Linaro. [MENTION=2146390]JamieD81[/MENTION] needs to pull these last dozen or so commits. I also rebuilt my linaro toolchain to be optimized for kernel version 3.0.101 so he'll need a fresh download of that as well. If he combines all of these elements together he'll be able to produce the faster kernel yet! The only problem is the new kernel won't be compatible with the older ROMs. He may actually want to build a kernel with the gpu updates and one without updates so that you get two fast kernels that should be compatible for both old and new 4.3 ROMs. I'll leave that decision up to him. ￼

Cheers!

Cl3Kener
[AT&T Samsung Galaxy Note I717] AD5GB:
Hey,

Yeah, thanks. I talked to Jamie and am going to work with bringing my branch up to the latest. I've got to merge Chester's latest with mine and those I've added from Linux mainstream code to do that. I'm more interested though in working with the new 3.10x branch from Google. I'll have a build with 3.0.101 out there soon. Sorry about the link. All builds for our phone can be found at the link below. These new "unofficial" ones are in the kernel_testing directory - naturally. One user reported boot looping. I had that when I dirty flashed from the previous nightly but after a "factory reset" it worked fine. I still haven't seen the screen un-lock problems I had with the stock CM kernel and a lock screen enabled. Good luck!

http://pacman.basketbuild.com/index.php?dir=main/quincyatt/
[AT&T Samsung Galaxy Note I717] :
Yeah, it's not possible to dirty flash from a nightly directly to the kernel_testing nightly.
[AT&T Samsung Galaxy Note I717] AD5GB:
Actually, I was just successful 2 times now dirty flashing from nightly to a kernel_test build. Both times it rebooted itself just as it was "starting apps" after the optimization process and came up nicely. Not sure I understand exactly what happened and as usually don't *recommend* dirty flashing ever but I'll continue to fool with this and try to get a handle on what's happening. Since the new kernel is a big jump from stock, (from 3.0.89 to 3.0.101 and contains most of UBER enhancements, schedulers, governors, -O3, cortex-a8 cpu and neon fpu optimizations) it's surprising it worked so well. I'm not hearing any bad things about it and there have been several downloads so I'll assume things are no worse than stock.

Android-4.4 is coming very soon. If no negative feedback on the kernel test version is heard I'll look seriously at integrating this kernel into the regular build process.

Work is well underway on a 3.10 kernel. The kernel itself is building but not yet integrating well with the rest of the build process. I may try a separate kernel package as soon as I get compiler warnings quiet just to see if a 3.10 kernel will boot.
[AT&T Samsung Galaxy Note I717] :
I dirty flashed (and clean flashed) the latest kernel_testing from the latest nightly, and didn't work...

Device: N7005

Recovery: TWRP

Current pac_quincyatt-nightly-20131102

Any help?
[AT&T Samsung Galaxy Note I717] AD5GB:
What does it do? (or not do?) I've not had any trouble getting it to run and it runs great for me. Overclocked - swipe-to-wake - InteractiveX governor....

Oh wait. N7005 device. Hmmm..... I need to check that the config supports the N7005. Not certain what the difference is between that and the I717 and I might have removed something that device needs. Looking........
[AT&T Samsung Galaxy Note I717] :
Actually the only difference is the lack of NFC in N7005. Other than that, the devices should be the same.
[AT&T Samsung Galaxy Note I717] FlyBoy276:
Ditto, however I did not dirty flash, but did a factory reset. It gets stuck at the boot screen, continuously cycling through the 'game over - insert coin - pacman roms' screens.

Device : I717

Recovery: TWRP
[AT&T Samsung Galaxy Note I717] AD5GB:
Good info though still a puzzle. I'm running a build made early this morning with a couple kernel config tweaks. Spin lock/unlock-related. This one runs beautifully for me as well. I just put it I'm the kernel test directory. Might be worth a try though of be surprised if it changed anything.

Worth trying might be this sequence... Factory reset/flash. Clear dalvik/cache. Reboot. Allow it to optimize apps of it gets there. If it doesn't, dirty flash the same ROM and clear cache and dalvik again and reboot.

I will downgrade the l -O3 optimization and change ramdisk compression from gzip to LZA this evening and see how that works but it's unclear why this doesn't work for you all. Not one bit of trouble here. :confused:
[AT&T Samsung Galaxy Note I717] xZeroMancerx:
Is there still a screen flicker with any of the recent builds ?
[AT&T Samsung Galaxy Note I717] Really now:
I couldn't get the kernel test rom to run either. I wiped everything first but it just boot looped so I reflashed the rom and wiped caches and still had the same results.
[AT&T Samsung Galaxy Note I717] AD5GB:
Not for me.
[AT&T Samsung Galaxy Note I717] rsalib:
is it possible to get the kernel on its own instead of having to download the rom as a whole?

EDIT:

I dirty flashed 11/4 kernel testing over 11/4 nightly. works fine.
[AT&T Samsung Galaxy Note I717] xZeroMancerx:
Crazy question ? I know its been said/asked b4 but how can I get the navbar to stick ? It never enables and it seems like the save icon never works regardless of how many times its pressed..also, the back button seems to work oddly
[AT&T Samsung Galaxy Note I717] blackhawkrisen:
Having Trouble Looking for GaApps

I can't down the GaApps for this ROM anywhere. I tried going to the link that is provided and clicked on GaApps.zip when I was given a selection, it is not downloading through the goo.im website.
[AT&T Samsung Galaxy Note I717] Really now:
Goo.IM changed over to new servers and they don't have everything up and running yet. You should be able to download the Gapps file you need from here. https://www.dropbox.com/sh/6dqd9md1vu95eee/zZASsjlENe/gapps-jb-20130813-signed.zip
[AT&T Samsung Galaxy Note I717] Poriotis:
I tried this sequence and got it to work. However on a second reboot, I got the boot loop. :(
[AT&T Samsung Galaxy Note I717] AD5GB:
Kernel will be available separately (but not on PAC pages as it won't be official) once it boots reliably. One of the reasons people are having problems flashing other kernels on PAC (and other ROMS) is because of the way ramdisks are done. PAC has to do things a bit differently because of the size of the ROM. Some "kernel devs" don't like this but there aren't infinite hardware resources to play with. We're also looking at other options which are being tested on other devices.

Glad you're able to use the ROM. Wish I could figure out why others can't. Working on it....

A new test build will be up shortly with less aggressive optimizations...
[AT&T Samsung Galaxy Note I717] AD5GB:
The build with less aggressive optimizations is uploading now if you wish (once it's done naturally) to try that one. This is making me crazy that it's not working for you guys. It's awesome for me :(.
[AT&T Samsung Galaxy Note I717] :
There're two files, one with 'O2', and one without.

Is a dirty flash from a nightly, to either kernel_testing version possible now?
[AT&T Samsung Galaxy Note I717] AD5GB:
As a rule dirty flashing is never *suggested*. Possible - yes. Successful - maybe. It's a judgement call and personal choice. It works most times for me - sometimes not. Other's are thus far having difficulties with even clean flashes so all I can say is try if you like. I'm at a loss to understand the problem everyone's having yet but without being able to see logs, attach a debugger etc, all I can do is take pot shots at it since I cannot duplicate it.
[AT&T Samsung Galaxy Note I717] rsalib:
I have noticed most people having problems are using a newer version of TWRP recovery.

I had similar problems until I went back to TWRP 2.5.

Goodluck
[AT&T Samsung Galaxy Note I717] blackhawkrisen:
Worked Fine Until This Morning

This is a great ROM, at least last night it seemed to be. When I shut off my phone for the night and tried to boot up in the morning, it has been stuck on the bootloader since.
[AT&T Samsung Galaxy Note I717] AD5GB:
Good info for those having troubles. I'm one of the lucky ones though in that I have no trouble with 2.6.3. I've heard lots of people have though.
[AT&T Samsung Galaxy Note I717] AD5GB:
Which ROM? The regular nightly or the test kernel version. Maybe I should start a separate thread for it until I get the boot problems resolved.... :confused:
[AT&T Samsung Galaxy Note I717] AD5GB:
Haha! I finally got the boot loop! Downgraded to TWRP 2.6.0.0 and still get it. Now I can hopefully fix it. Duplicating this stuff is sometimes the hardest part.

More to come........
[AT&T Samsung Galaxy Note I717] Really now:
Thank goodness, I was starting to get an inferiority complex! :laugh:
[AT&T Samsung Galaxy Note I717] blackhawkrisen:
Regular nightly ROM. I'm not sure how to reset my phone as it won't boot into recovery now because it just keeps redisplaying the bootloader.
[AT&T Samsung Galaxy Note I717] Poriotis:
New to this stuff I suppose? :laugh:

Remove the battery and put it back

Hold both ends of the volume rocker as if you're pressing the whole thing in

While holding the volume rocker, press the power button

Once the Samsung sign comes on, let go of the power button but not the volume rocker

After it boots into recovery, you can let go of the volume rocker

BTW I used CWM 6.0.3.6 when testing PAC-Man but just upgraded to 6.0.4.3.
[AT&T Samsung Galaxy Note I717] blackhawkrisen:
Oh thank you, yes I am quiet new to this.

I am going to reinstall nightly and wipe the cache, hopefully this may fix bootloading problems? Maybe it was just a glitch?
[AT&T Samsung Galaxy Note I717] AD5GB:
Hopefully just a glitch. But yeah, give it a shot and report back.
[AT&T Samsung Galaxy Note I717] blackhawkrisen:
The bootloader is still resetting. I think I will use my old ROM until you can find a fix.
[AT&T Samsung Galaxy Note I717] blackhawkrisen:
Oops, so my phone isn't booting into any ROM that I am trying to install. I'm still able to get into CWM v6.0.3.1. I tried going into my backups, but it says no files found.
[AT&T Samsung Galaxy Note I717] AD5GB:
Did you get this resolved? You didn't wipe your backup directory by mistake, did you?
[AT&T Samsung Galaxy Note I717] Poriotis:
AD5GB, are you working on releasing another version or pac_quincyatt-4.3-20131104-Android-3.0.101-with-O2 is it?
[AT&T Samsung Galaxy Note I717] Killerfish1450:
I'm having a strange problem, the ROM boots and runs great but if I try to shutdown or just do a reboot upon restart I get a never ending black screen after Samsung logo. The only way I have found to fix is to factory reset and reflash. Any suggestions? Using latest official nightly and CWM recovery
[AT&T Samsung Galaxy Note I717] dcscorpio76:
I agree! I've had the same issue and I thought it had something to do with switching the governors until I simply cleaned flashed and then tried to boot. ROM will not boot up after initial flash which is really annoying if you're taking the time to set the ROM up and reinstall all your apps. I hope something can be done about this. I appreciate all the work that goes into these ROMs. Just giving feedback
[AT&T Samsung Galaxy Note I717] rsalib:
Try using TWRP recovery version 2.5
[AT&T Samsung Galaxy Note I717] Killerfish1450:
Does anyone have a copy they could supply? The only thing I can find is the latest 2.6, unless there is a place to get older versions that i am missing.
[AT&T Samsung Galaxy Note I717] rsalib:
They must have pulled the older versions from their download page. Hopefully someone will be able to provide one.
[AT&T Samsung Galaxy Note I717] Killerfish1450:
Nevermind, I didn't realize once you clicked to download it all the versions were available. My fault for assuming it would download the latest version once you clicked the link.

P.S. it seems TWRP 2.5 may have fixed it.

P.S.S. Has anyone noticed a problem playing .wma music files? Multiple different music players say the file is not supported, however, they all worked on the stock system fine.
[AT&T Samsung Galaxy Note I717] Poriotis:
The O2 version finally worked for me. After three boots (including the initial one), I have not encountered the boot-loop issue. So on to testing the rest of the ROM. Will report on that later.
[AT&T Samsung Galaxy Note I717] blackhawkrisen:
No I restored it and its fine now.
[AT&T Samsung Galaxy Note I717] AD5GB:
Yes, I'm actually working with the kernel more than anticipated due to issues that have surfaced. Mostly with the boot issues that you all have helped me find - that I'm not able to duplicate. I'd like to get -O3 optimization to function reliably as well. Again, ultimately is to bring the kernel up to 3.10. I'll post as soon as I have another build worthy of more testing that will hopefully be less problematic than the previous ones.
[AT&T Samsung Galaxy Note I717] AD5GB:
Appreciate all the feedback and the willingness of everyone to test. I know how frustrating these sorts of problems can be and feel for everyone that has to endure them. Lately I've had all sorts of issues that I'm trying to resolve with this. I've gone to keeping a stable nandroid on hand for when I can't recover from a test build. I get a stable nightly, set up all my apps and settings and then do a back up of it. If I get to an irrecoverable state I just restore the back up, and take another swing at it. I'm not suggesting that's what everyone do but that's what I'm doing to save time in re-installing and re-configuring all my stuff.

More to come....
[AT&T Samsung Galaxy Note I717] dcscorpio76:
Like Poriotis, I was finally able to get the O2 Build to boot after 3 attempts exact. I restored everything and now it seems the ROM is working as normal. I do however notice a considerable amount of lag and screen flicker. Also, icons disappear and the homescreen goes blank when hitting the home button from another page or app but I comes back if I tap the apps button.

I'm getting a lot of screen flicker with this build and the Wheatley governor is not solving the issue like it normally would. I admit I haven't checked off HW overlay under dev options yet. That may solve it for time being. The biggest issue I notice is the max frequencies won't stick under performance settings nor trickster. No matter what I set it to, the min freq sticks, max resets to default. Just a little feedback! Love the ROM nonetheless! I appreciate all the hard work and dedication devs!

---------- Post added at 08:33 AM ---------- Previous post was at 08:32 AM ----------

I have to admit that I've been in denial about my twrp recovery. I NEVER EVER had an issue with twrp 2.6.3 until these last few builds. I saw all the post and I was like mine works fine until I started flashing builds from 11/4 and up. TWRP 2.5 is definitely the way to go so thanks to whomever made that public knowledge. Haven't had much of an issue flashing, backing up or restoring anything with 2.5 since I reverted back. Thankfully I had it on ice on my sd card!