yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] dee8905:
I believe it's normal, mine does that too, for a moment it'll say charged (I have battery status display on my uccw) but if you leave it a bit longer it'll drop down to 99% and says "Not Charging" instead of "Discharging". It's for saving the battery from over charging I guess.

I hope so, was about to flash latest update when I saw that G+ post, thankfully I checked my G+ first. :cyclops:
[Samsung Galaxy Nexus] awesome.marcus:
Re: [AOSPA 4.2.2 JDQ39] PARANOIDANDROID 3.1 (Feb28) | Expandable PIE Notifications

But there's a time that it stops and the battery still on 60%. Also the last build is the same.
[Samsung Galaxy Nexus] Kocai:
But they do cherry pick the quick settings from CM.
[Samsung Galaxy Nexus] dee8905:
Does it says "Discharging" or "Not Charging"?
[Samsung Galaxy Nexus] Pirateghost:
this should apply to pretty much every ROM out there...
[Samsung Galaxy Nexus] awesome.marcus:
Re: [AOSPA 4.2.2 JDQ39] PARANOIDANDROID 3.1 (Feb28) | Expandable PIE Notifications

It says "not charging"
[Samsung Galaxy Nexus] neerajvd:
Why this hullabaloo over people not searching before flashing or asking questions after getting bootloops?

It is not about being lazy. It is always exciting when a new version of PA arrives. Just imagine the excitement when you see an update notification from goomanager. So we just go ahead and flash it without reading the thread. Don't tell me none of you have ever done that. Do you ALWAYS read the dev comments when you flash? Are you excited about reading what the dev has written or about flashing the ROM. And if you read the changelogs, then atleast tell in the changelogs about no kernel issue.

I mean come on, who can imagine a ROM without a kernel? It never happened before so no one was expecting the bootloops. Not blaming anyone here. I agree D4rk has his own stuff to take care of. So in his absence shouldn't it be the xda members responsibility to solve the people's problems? The mistake that i do agree was made is after the bootloops, people should not just post without reading. Then, a research is necessary. And as legend says, prevention is better than cure.

Also sadly, i can see the interest dropping in the ROM downloads somehow. Might be because people are afraid of bootloops again, or afraid of asking questions. Just look at the differences in the number of downloads for 9th feb version and 27th feb version. Its been only 5 days, i know. So let us restore the awesomeness of the ROM and this thread too. Let us try and be level headed and help out D4rk until he is free enough to handle development again.

Just my 2 cents. I did not mean offense to anyone. Especially not to the developers. Just felt like sharing the users point of view. And what is the world is xda attitude!! :D:D:confused:

@Forum administrator, sorry for this non-dev related post. But i felt a point had to be made about the bootloops. Apologies. :o

Remaining on topic, is the Prevent rotation feature in PIE settings working as expected? For me its making no difference whether its checked or not.
[Samsung Galaxy Nexus] dee8905:
I can only help you so far as by guessing that it is a software problem, if it says "Discharging" then it might be hardware problem (dirty usb pin or something similar). I'm sorry but I don't wanna risk your device by saying something I didn't really understand :angel:

You may get excited and do anything without any prior learning, but if you're hitting rocks, you're on your own..you should search and search and read before you go and asks for solution, because the problems you're having might have been mentioned by the devs themselves.
[Samsung Galaxy Nexus] maddyreddy:
Re: [AOSPA 4.2.2 JDQ39] PARANOIDANDROID 3.1 (Feb28) | Expandable PIE Notifications

You should try AK, battery back up is just awesome.
[Samsung Galaxy Nexus] justsahid:
Re: [AOSPA 4.2.2 JDQ39] PARANOIDANDROID 3.1 (Feb28) | Expandable PIE Notifications

Is anybody noticing some kind of memory leak, for me when I restart the phone,available memory shows close to 300 mb but after couple of hours it drops to around 50 mb or less and then phone becomes very sluggish.

I am running the latest version now but noticed this problem in all the versions.

I hate to go away from this ROM .Any body any clue?
[Samsung Galaxy Nexus] -Jesco-:
been using the phone for 3days without restarting the phone , free ram ranging from 170mb-275mb . i think its a app thats causing the memory hog .
[Samsung Galaxy Nexus] ahmedsaber20005:
Thanks For your help i sew this at setting at rom but i do not know how to use it

Thanks :)
[Samsung Galaxy Nexus] m.is.for.michael:
It's just not what I anticipated. I would have thought that if you have per-app expand on, then exiting the app would take you back to whatever the status was before you went into that app.

When I expand the desktop, I can switch in and out of and between all my apps without it reappearing; but as soon as I go into this one where I've enabled per-app expand, the nav bar comes back when I exit.
[Samsung Galaxy Nexus] Kocai:
Re: [AOSPA 4.2.2 JDQ39] PARANOIDANDROID 3.1 (Feb28) | Expandable PIE Notifications

Ah okay. That makes sense. Maybe that's why moles said that they're going to take out auto expand mode. We had this feature before PIE right. So it's like I said, back then it made sense to disabled the expanded mode as soon as you exit the app because we didn't have PIE to navigate.
[Samsung Galaxy Nexus] m.is.for.michael:
Re: [AOSPA 4.2.2 JDQ39] PARANOIDANDROID 3.1 (Feb28) | Expandable PIE Notifications

/chin wobbles/ but I _love_ auto expand...

Sent from my brain using telepathy
[Samsung Galaxy Nexus] Ridho1:
Dont you guys experience a lags on homescreen after sometime?

I am getting sick with this. I always did a dirty flash from 2.99 to 3+. Sometimes, the homescreen lags and I have to restart the systemUI. I had posted this problem in this thread but only few peoples get the problem. Then I tried to clean install and restore my user apps using TiBu (without restoring system data). But again, the lag happens. No one?
[Samsung Galaxy Nexus] Justinhopaolo:
Re: [AOSPA 4.2.2 JDQ39] PARANOIDANDROID 3.1 (Feb28) | Expandable PIE Notifications

Change launcher
[Samsung Galaxy Nexus] Ridho1:
I have tried using Nova, apex, holo, and Stock. Dont you experience a lag on homescreen?
[Samsung Galaxy Nexus] thedudejdog:
Re: [AOSPA 4.2.2 JDQ39] PARANOIDANDROID 3.1 (Feb28) | Expandable PIE Notifications

Try just a clean install, start with flashing completely factory images. Don't use titanium. Then see if your lag is still there. If no, then go on to flash aospa. If your lag isn't there, then restore your titanium. If you start lagging then, it's one of your apps
[Samsung Galaxy Nexus] Xphazer:
When using themes, the clock doesn't go back to the theme color after exiting any app with a per app color or per app expand setting defined.

It happen in any scenario I have tried. (Any theme, launcher, UI Mode)

The issue seems to have been reported at least once before: http://xdaforums.com/showpost.php?p=36898749&postcount=24632

If I disable per-app-color (pa pref> Interface> "Enable per app color"), I can use per app expand without any issue.

Is there anyway to select default color that gets applied to what is including the clock?

No mather what color I set to anything, nothing is affecting it, still blue. ^^

Heres the problem in image.

On the left is the color the theme should be and on the right is the color it gets after exiting an app with custom per app setting defined.

Thanks!
[Samsung Galaxy Nexus] siealex:
Re: [AOSPA 4.2.2 JDQ39] PARANOIDANDROID 3.1 (Feb28) | Expandable PIE Notifications

Reboot after applying themes.
[Samsung Galaxy Nexus] Xphazer:
Nope, no luck still blue. A reboot only fix the icons. (drawer, desktop)
[Samsung Galaxy Nexus] c0mrade2:
Totally love this ROM, but I have a few questions:

is it somehow possible to increase pie above "Gigantic"? Because in phablet mode is quite small.. Or better have phablet status bar in phone mode :D

and is it possible to have pie notifications even if you're not in expanded desktop mode?
[Samsung Galaxy Nexus] Khizar:
i am using the latest build with AK Cylon V716(and nova launcher) and have no lag.. i would suggest you do a clean install if you have dirty flashed, dirty flashing seems to give me lag thats why i always clean flash and have no issues

1. no gigantic is the max size you can set PIE to

2. no you cant have phablet status bar in phone ui

3. if expanded desktop isnt enabled PIE will be set to bare, why dont you use the notifcation bar to check notifcations?

PS- next time you have questions rather than asking in the dev thread ask in the Paranoid 101 thread that is linked in my sig... click "show content" :good:
[Samsung Galaxy Nexus] cyberon:
Re: [AOSPA 4.2.2 JDQ39] PARANOIDANDROID 3.1 (Feb28) | Expandable PIE Notifications

Yep, they did, that's the reason for my heads up, this thread is full of people who clearly don't know what they are talking about, but feel the need to express themselves. :)
[Samsung Galaxy Nexus] c0mrade2:
Thanks! Is that I like having the signal bars in the status bar always under control and at the same time I love the pie notification system, expecially the screen dimming :P
[Samsung Galaxy Nexus] rfec:
Re: [AOSPA 4.2.2 JDQ39] PARANOIDANDROID 3.1 (Feb28) | Expandable PIE Notifications

Well it looks good overall, pie is easy to use and working very well.

Btw any ideas how to change pie colors and customize from where to get toggles and notifications?For example I have toggles from left, notifications on top and right...not sure why I have it on 2 places...
[Samsung Galaxy Nexus] ru11er:
Re: [AOSPA 4.2.2 JDQ39] PARANOIDANDROID 3.1 (Feb28) | Expandable PIE Notifications

Please before people get stupid with upcoming builds, there is a new g+ post for Paranoid... It mentions some very important info .... And will save a lot of headaches.
[Samsung Galaxy Nexus] awesome.marcus:
Re: [AOSPA 4.2.2 JDQ39] PARANOIDANDROID 3.1 (Feb28) | Expandable PIE Notifications

Mind if i ask.. Can you flash img file with TWRP?? Or do you have a flashable zip of the bootloader/radio?? Tnx
[Samsung Galaxy Nexus] Xphazer:
Yes you should be fine with TWRP, though you should use fasboot IMO.

Bootloader here (primelc03): http://xdaforums.com/showthread.php?t=1587498

Radio here (xxlj1): http://xdaforums.com/showthread.php?t=1405345
[Samsung Galaxy Nexus] awesome.marcus:
Re: [AOSPA 4.2.2 JDQ39] PARANOIDANDROID 3.1 (Feb28) | Expandable PIE Notifications

Ahh but as you know i dont know how to flash it through fastboot... By the way is it necessary to flash bootloader and radio if my phone just doing fine.
[Samsung Galaxy Nexus] johrie:
I'm on XXLH1 radio, i should update right?
[Samsung Galaxy Nexus] awesome.marcus:
Re: [AOSPA 4.2.2 JDQ39] PARANOIDANDROID 3.1 (Feb28) | Expandable PIE Notifications

Me too.
[Samsung Galaxy Nexus] MrBlackbriar:
I think it's important to note that the G+ post was only for Nexus 4 users. There is no new bootloader for maguro (judging by the "Last Edited"-date of the bootloader-post, primelc03 has been out for half a year and it's been quite a while since I flashed it) and I don't expect anything to get broken.

That being said, it's always a good idea to flash the latest radio (xxlj1). It doesn't matter if you flash it via CWM (or TWRP) or fastboot, do whatever you think is easier.
[Samsung Galaxy Nexus] Khizar:
how are you supposed to flash img files using twrp? :confused:

yes this is what was posted on g+, so i recommend you guys update -
[Samsung Galaxy Nexus] awesome.marcus:
Re: [AOSPA 4.2.2 JDQ39] PARANOIDANDROID 3.1 (Feb28) | Expandable PIE Notifications

By the way how can i flash radio through fastboot? I really dont have idea unless its a flashable zip that can only be done with twrp. Sorry cuz i havent done amh flashing img through fastboot :(
[Samsung Galaxy Nexus] MrBlackbriar:
I'm sure a little google search will lead you in the right direction. But if you don't want to spend the time, you should just flash the .zip, there is no downside to it. You can find the .zip in the thread linked in the post I quoted. (Yes, you can flash CWM-files with TWRP.)
[Samsung Galaxy Nexus] swordfish123:
I am not sure about boot loader, but i dont think baseband is dependent on the ROM releases. I am on XXLH1 and running 4.2.2 just fine. Baseband is image for your 2g/3g/lte chipset on your phone. Noting to do with the ROM. If you are having some issues with your signals you can go ahead and flash the latest XXLJ1 baseband. A flashable zip is present in below thread

http://xdaforums.com/showthread.php?t=1405345
[Samsung Galaxy Nexus] musashihatred:
Re: [AOSPA 4.2.2 JDQ39] PARANOIDANDROID 3.1 (Feb28) | Expandable PIE Notifications

Boot loader is the same:) baseband is the only one updated.osmosis said it also, if you are to use 4.2.2 update the radio.

Ril of xxlh1 4.2.1 = lj1 4.2.2 so no need to to update ril
[Samsung Galaxy Nexus] marhensa:
Re: [AOSPA 4.2.2 JDQ39] PARANOIDANDROID 3.1 (Feb28) | Expandable PIE Notifications

so.. this is okay right?

i'm not using fasboot method to update it, i use flashable zip for the radio.

i found it somewhere in this galnex xda forum.

---

Sent from Android Device
[Samsung Galaxy Nexus] -Jesco-:
that will be fine ~
[Samsung Galaxy Nexus] Nephilim:
Yes, I

always

read the developer comments, in fact I most of the time wait for others to flash first as well to find out what issues might be present. Anyone that flashes without putting any effort into looking at changelogs or reading up on the XDA thread deserves a bricked device. XDA is about learning and sharing knowledge not looking at a picture of a rom you like, flashing it and then coming to the forums to complain about your phone not working properly when most likely the reason is a page or two back..... but..... you were too lazy to look so instead you make the claim that you cannot search on the xda app. Guess what everyone, all of our devices have a browser, the search function on the browser version of xda is just the same as on PC. Most of the time a search function is not needed if you follow the developer thread. The most you will have to do is read 5 to 15 pages back to keep up with current events on your rom or kernel.

I do not buy it when the excuse of "excitement" is supposed to justify people not reading about a rom or kernel before flashing it. These are $300+ devices, anyone that just flashes stuff on them probably should not have one. Would you put a experimental gasoline in your car or experimental brakes on it without researching them? I don't think so, why should it be okay to complain about issues when you made the choice to not even take a moment to find out what the update is all about?
[Samsung Galaxy Nexus] joelmonty:
Re: [AOSPA 4.2.2 JDQ39] PARANOIDANDROID 3.1 (Feb28) | Expandable PIE Notifications

Getting a slight lag or delay perhaps after unlocking from a pattern unlock , anyone else getting this issue it's not major but slightly annoying.
[Samsung Galaxy Nexus] ammarii:
Re: [AOSPA 4.2.2 JDQ39] PARANOIDANDROID 3.1 (Feb28) | Expandable PIE Notifications

There is something funny I dont think its a bug. The pie can appear on lock screen
[Samsung Galaxy Nexus] Nephilim:
That has always been that way.
[Samsung Galaxy Nexus] jendrassik:
Re: [AOSPA 4.2.2 JDQ39] PARANOIDANDROID 3.1 (Feb28) | Expandable PIE Notifications

The 2g-3g tile doesn't seem to work. It changes image but the network mode si not switching at all.

Is that a known bug ?
[Samsung Galaxy Nexus] Muvolt:
Re: [AOSPA 4.2.2 JDQ39] PARANOIDANDROID 3.1 (Feb28) | Expandable PIE Notifications

Give it some time... It needs some seconds to work..
[Samsung Galaxy Nexus] Nephilim:
I believe that has been fixed in the next upcoming update. They said on the G+ page that now things should be working properly because they merged the 4.2.2 binaries fully.
[Samsung Galaxy Nexus] Muvolt:
Re: [AOSPA 4.2.2 JDQ39] PARANOIDANDROID 3.1 (Feb28) | Expandable PIE Notifications

Is Cylon better than the default PA (CM) kernel? I had cylon but then I re flashed the ROM with the default kernel and it feels faster... It has some slight differences in antutu score though...
[Samsung Galaxy Nexus] DieGo316:
you need to try that for yourself, everyone has a favorite kernel, some will say franco is better, some stock is better, it depends in what suits you best.

plus PA kernel is not CM, its not longer based in CM sources
[Samsung Galaxy Nexus] madhavs:
Latest PA build dated 28th feb Maguro Has CM Kernel

I flashed AK CYLON 716 and never had any problem so far :good:
[Samsung Galaxy Nexus] Muvolt:
It says 3.0.31 - cyanogenmod in the about section...
[Samsung Galaxy Nexus] DieGo316:
well thats weird tought they were using stock kernel but its ok still try a kernel and look for the one you like the most :)
[Samsung Galaxy Nexus] britoso:
I had the previous radio and it was working fine with PA3.1, but I upgraded just so that I can have the latest version.

1) Reboot into bootloader/fastboot mode.

2) Your PC (if in windows) will ask for drivers if it cannot find them, I used the "naked" drivers from here

3) Test that fastboot can see your phone, run:

fastboot devices

If you dont see your device you may have to again reboot into bootloader mode from the on-screen menu (vol keys and power)

4) If your phone shows up, you can flash the latest radio using this command:

fastboot flash radio radio-maguro-i9250xxlj1.img

You can get the latest radio inside the google zip from here. Do not run the scripts they provide as it will flash the bootloader and ROM zips too.

Output:

sending 'radio' (12288 KB)...
OKAY [ 1.241s]
writing 'radio'...
OKAY [ 2.296s]
finished. total time: 3.537s

5) Then to reboot run:

fastboot reboot
[Samsung Galaxy Nexus] ReMuSeR:
hey guys im using kernel AK Purrity 023 but i dont know i think battery drain is awsome... is there any good kernel with nice battery life and i also have dual battery and still drains to much here is a SS what u think is it good?
[Samsung Galaxy Nexus] cmoG530:
Re: [AOSPA 4.2.2 JDQ39] PARANOIDANDROID 3.1 (Feb28) | Expandable PIE Notifications

I really want to help you out, but to be honest, I can't understand what you are trying to say.
[Samsung Galaxy Nexus] ReMuSeR:
battery drain is awsome... what a failure hahahhahaha had something else in mind ROM is awsome but my batter drain is bad i think
[Samsung Galaxy Nexus] Nephilim:
Re: [AOSPA 4.2.2 JDQ39] PARANOIDANDROID 3.1 (Feb28) | Expandable PIE Notifications

Dude, no offense but your posts do not make sense.

Sent from my AK Cylon Powered AOSPA 3.1 Galaxy Nexus
[Samsung Galaxy Nexus] ReMuSeR:
maybe that my english sucks or dunno why lol again i have the latest PARANOIDANDROID 3.1 ROM with AK Purrity 023 kernel but my battery is bad so i need help to find any solution to fix my battery Drain so is there any other kernel that i should try or ?

hope this time someone understands me :P
[Samsung Galaxy Nexus] Nephilim:
Re: [AOSPA 4.2.2 JDQ39] PARANOIDANDROID 3.1 (Feb28) | Expandable PIE Notifications

Go to the AK Kernel thread and give Cylon Kernel a try.

Sent from my AK Cylon Powered AOSPA 3.1 Galaxy Nexus
[Samsung Galaxy Nexus] britoso:
Try Auto brightness or low brightness maybe ?
[Samsung Galaxy Nexus] nikulogical:
Re: [AOSPA 4.2.2 JDQ39] PARANOIDANDROID 3.1 (Feb28) | Expandable PIE Notifications

First of all we can't see the screen on time so there's no way to judge battery life. As for the idle drain it looks normal.

If there really is abnormal drain then get better battery stats and find out what's causing it exactly.

I'm using the combo as you.

Sent from my Paranoid Maguro powered by AK
[Samsung Galaxy Nexus] 02ranger:
Re: [AOSPA 4.2.2 JDQ39] PARANOIDANDROID 3.1 (Feb28) | Expandable PIE Notifications

Like Nephilim said, try Cylon kernel. Also, if you'll look in Neph's sig there is a link to his kernel settings. I applied them on my phone with Cylon kernel (except FSYNC is still on, I'm not that brave) and it has made my battery life great. Phone is still fast and responsive too! Its worth a shot :)
[Samsung Galaxy Nexus] ReMuSeR:
aha ok i have a try just how do i apply this settings?
[Samsung Galaxy Nexus] 02ranger:
Re: [AOSPA 4.2.2 JDQ39] PARANOIDANDROID 3.1 (Feb28) | Expandable PIE Notifications

Sorry, I should've mentioned that. Download the kernel from the ak thread (click the Cylon banner in my sig) and flash it. Then use Trickster app from the Play store to apply his settings. You can test it with the free version and I "think" all the settings are available, but you won't be able to save any profiles, meaning if you upgrade to a new kernel or reflash the ROM, you have to manually reset all the kernel settings. If you like the Trickster app, its well worth buying which gives you the option to save profiles. You can set performance options as well as color profiles.
[Samsung Galaxy Nexus] qu4nd:
AW: [AOSPA 4.2.2 JDQ39] PARANOIDANDROID 3.1 (Feb28) | Expandable PIE Notifications

Use the app trickster mod from the play store...
[Samsung Galaxy Nexus] ReMuSeR:
ok all set thanks guys gona test it tomrow hows battery :)))
[Samsung Galaxy Nexus] marhensa:
4th March - UPDATE

[youtube]VnC1Wc2UHos[/youtube]

tl;dr, what's new:

- Expandable notification with one finger,

- Clear all notifications button,

- Sound to Vibrate tile toggle,

- Using SuperUser for now, no longer using SuperSU.

---

Sent from Android Device
[Samsung Galaxy Nexus] gummie:
Finally, we are now going to be integrated with SuperUser root manager.
[Samsung Galaxy Nexus] Nephilim:
Re: [AOSPA 4.2.2 JDQ39] PARANOIDANDROID 3.1 (Feb28) | Expandable PIE Notifications

Already have all that and its nice. ;)

Sent from my AK Cylon Powered AOSPA 3.1 Galaxy Nexus
[Samsung Galaxy Nexus] molesarecoming:
ah that you mean. i think we'll get some toggles. jaybob even sent me some. i need to try it out when i fetch the latest repo. it had torch, 3g, 4g and all that stuff in it from what i could grasp from the patch files.
[Samsung Galaxy Nexus] smjfosho:
hey moles, what are the future plans for this rom? as far as im concerned its pretty much perfect. any plans to add any more features, or merge things that AOKP has?
[Samsung Galaxy Nexus] molesarecoming:
theres 6 big things we need to solve

1. per-app-density -> solved

2. per-app-layout -> solved

3. force option -> semi solved

4. better prop managerment, plattform independend values, backup-mechansms

5. hybrid profiles

6. better, intuitive panel

when this is done we'll have more time for layout and rom management. i dont think it'll be so hard to add a few toggles.
[Samsung Galaxy Nexus] joakimberglund:
And here I was thinking about rolling back to get widget scaling working again :D

(yes thats more important to me then the things it broke :p)

Briliant!
[Samsung Galaxy Nexus] caurusapulus:
Hi moles, I just want to say that there's probably a little bug, dunno if it's only me but I had this also on 0.6b. I didn't said anything before cause I had this when you released the new version and so I did the upgrade.

See the statusbar down there, near the signal bars, in the attached screenshots.

It's just an issue of my carrier?
[Samsung Galaxy Nexus] opethrocks:
I finally got nova launcher to smoothen up alot. After setting nova to phone mode it is now muuuuch smoother, it almost kinda rivals trebuchet in smoothness (almost). With dpi set to 260 widgets are lookin niiiice