yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] hosmsdos:
Re: [ROM] [4.2.2] AOKP :: jb-mr1 :: build-4 :: mako

Is it possible to change the kill all button in recent apps its really ugly

---------- Post added at 01:19 PM ---------- Previous post was at 01:15 PM ----------

I have had the same exact thing using xylon ROM. I have mentioned this a lot but no body seems to notice however I don't have this issue using AOKP 5 PUB
[Nexus 4 Original Android Development] ermacwins:
+1 The the approack Paranoid Rom has taken for this is excellent.
[Nexus 4 Original Android Development] bryanlim05:
Flashed b5 ontop of b4. Everything running fine so far except that all my widgets on my homescreen dissapeared after the flash. Not a big issue, just added them back on
[Nexus 4 Original Android Development] matt1733:
yea its not working for me either when you press it normally first real glitch I've seen in this rom
[Nexus 4 Original Android Development] rizzxx7:
Re: [ROM] [4.2.2] AOKP :: jb-mr1 :: build-4 :: mako

I didn't flash the new radio since it disables LTE, am I missing or not taking advantage of something?
[Nexus 4 Original Android Development] Mnemoch:
Why? Just hold down power. I personally would never use it a tile, pain in the butt if you hit it by mistake...
[Nexus 4 Original Android Development] odeccacccp:
Yes and it also says in the OP there in BOLD FIRST LINE "These are unofficial AOKP builds. Please do not post in official AOKP threads with bugs or negative experiences possibly specific to these builds."

Please stop posting Re: B5 or other unofficial thing here, it confuses people who don't know, and take's away from discuss of t=other things. Please discuss experimental/unofficial builds where it belongs.
[Nexus 4 Original Android Development] Mnemoch:
B5 is official I thought, its on AOKP anyways...http://aokp.co/release-jb-mr1-build-5/
[Nexus 4 Original Android Development] odeccacccp:
that just came out, not even updated here.

I personally don't care, just saying.
[Nexus 4 Original Android Development] shankesh:
Works Great without any issues :cowboy:
[Nexus 4 Original Android Development] matt1733:
This rom is getting very good battery life on wifi im getting about an extra hour of screen time, im using this rom with matrix 7.5 kernel I haven't tested on mobile data much but it seems better than previous rom and kernel combos
[Nexus 4 Original Android Development] odeccacccp:
working great.

One question to make sure I am not missing it: There is no LCD Density control feature right? I need to do it manually in Build.prob right?
[Nexus 4 Original Android Development] zimphishmonger:
Mind sharing the walp[aper?
[Nexus 4 Original Android Development] partylikeaninjastar:
Calm down. He asked a question, he got an answer. All you quoted was their disclaimer not to post problems from that build in this official thread, which no one has done. All he did was kindly link to the unofficial thread so that the user who requested could try AOKP with PUB and receive support in the indicated thread If you wanted to be helpful, you should have pointed out to the person who requested it that he's using it at his own risk and any questions regarding it have to be posted in the thread in which it was downloaded..

Anyway....

Are there any plans to change the MMS/messenging app so that auto rotate will not delete the already entered text in the event that you accidentally rotate the phone? This is has always been a "feature" of AOKP on the Nexus 4 and it has been brought in the past in this thread as early as build 1. It's kind of annoying. I usually just replace the AOKP MMS.apk with the one from CM sine that one doesn't have that problem (not to mention it's better looking), but I'd rather not have to replace the APK with every single ROM flash.
[Nexus 4 Original Android Development] odeccacccp:
Thats what I said, I don't care, just pointed it out to few people posting about it. Since they got it in the unofficial thread.
[Nexus 4 Original Android Development] VaksenDK:
Yeah, I would really love to have them too, but I can't, and it is driving me crazy.

I go to togles settings in ROM Control and switch from Tiles to Traditional, the screen glitches, but is does not make the change. I still have tiles.

Any ideas?

First tried dirty flashing from build 4, then a full wipe and clean flash several times. Still no luck.

Edit: Also; when I try to enter Setup, it looks like this. Something is clearly wrong?

http://xdaforums.com/attachment.php?attachmentid=1784285&stc=1&d=1362592205
[Nexus 4 Original Android Development] Try4Ce:
AW: [ROM] [4.2.2] AOKP :: jb-mr1 :: build-4 :: mako

Tried the latest PUB build and either the A2DP quality patch is not in after all or not working. Just tried it out and got audio distortion. Back on CM10 now and audio quality is fantastic again. Will try out official b5 later on. Sry kind of a big deal for me ;)
[Nexus 4 Original Android Development] odeccacccp:
is this when you talk or listen to music?
[Nexus 4 Original Android Development] Hanny:
Sorry for posting in both PUB thread and here as I am not sure what is causing this little freaked out moment for me.

today i updated my rom to the latest build, did all the proper issue prevention such as restoring to default nav rings before flash, etc.

what I did was:

(ofc nandroid is already made)

go to TWRP recovery 2.4.3.0

wipe cache and dalvik

flash unofficial Mar5, Banks latest Unofficial Gapps 4/3, Franco r97

reboot

and then there's no signal, went to settings and see - Baseband UNKNOWN

I have had both my new bootloader and radio updated since the introduction of 4.2.2 a few weeks ago. i hvnt touched anything related to the baseband. I dont use LTE. everything about the radio were in normal usage.

So i did a simple reboot, and everything worked fine. data, wifi, bluetooth, all fine. baseband is shown correctly in settings menu. Thank god.

Just curious what made this happen... although im using the unofficial build it is simply based on build 5 and I dont think PUB optimizations would **** up the baseband. Any idea? thanks. :)

Screenshots
[Nexus 4 Original Android Development] ifti_a:
Re: [ROM] [4.2.2] AOKP :: jb-mr1 :: build-4 :: mako

Are the new gapps 2013 ones ok to use with build 5

Old ones are fine, just wondering
[Nexus 4 Original Android Development] CloudTown3:
Re: [ROM] [4.2.2] AOKP :: jb-mr1 :: build-4 :: mako

I use ROM toolbox for that. Make sure you use the multi DPI playstore apk if you do change it.
[Nexus 4 Original Android Development] odeccacccp:
I see, pretty much that''s what I meant. I use build as I don;t like any controlling apps.

Thanks, I flash Slim GApps they have modded play store.

---------- Post added at 01:01 PM ---------- Previous post was at 01:00 PM ----------

New GApps are meant for 4.2.2 so Build 4 and 5 yes.

Old GApps are just old, but you can use them, you can't use new once on 4.2.1 builds.

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

Just tried to type something using gesture typing it shows the blue line but no words are appearing, any one having this problem?
[Nexus 4 Original Android Development] 999vulcan:
Could someone point me to the info about radio and bootloader? I don't want to flash the wrong stuff.

Will flashing bootloader preserve TWRP recovery?
[Nexus 4 Original Android Development] dankoman:
http://xdaforums.com/showthread.php?t=2147194

you can ignore the part about the sensor fix if you're going to flash AOKP. it already has the fixes built in.

and recovery won't be affected...
[Nexus 4 Original Android Development] Try4Ce:
AW: [ROM] [4.2.2] AOKP :: jb-mr1 :: build-4 :: mako

Listening to music. With that patch the compression distortion is as good as gone. Sounds even better than my previous One X.
[Nexus 4 Original Android Development] odeccacccp:
can you provide a link? does it work for AOKP?
[Nexus 4 Original Android Development] Try4Ce:
Its not a patch / mod you can flash via recovery. It's a commit that has to be merged before compiling a release.

It should work for AOKP, since the AOKP team actually worked out that issue. CM just cherrypicked it from the AOKP commits...

Here is the link from CM:

http://review.cyanogenmod.org/#/c/33227/

And believe me, it is definately NO placebo. Audio distortions are really as good as gone. A2DP music streaming is fantastic with my car stereo and the latest CM ROMs ...

I dont know about the official AOKP build5 tho, all I can say is that the latest PUB release doesnt nearly produce the clear audio quality while listening via A2DP than on CM10.1 so far...
[Nexus 4 Original Android Development] Hanny:
Something is up for the Safe Headset Volume modification codes!

I don't know whether I understand you wrong or not, you mean "untick it" so the safe warning is GONE and your issue is SOLVED?

I am having the complete opposite stuff... I turned the warning OFF (unticked) and I experience the issue but if i turn it back ON (back to default behaviour of JB) I cannot reproduce the bug anymore!

Anyway, thanks for your inspiration that the option is the culprit. I don't care about pressing OK when I need louder sound. I use headphones to make calls everyday and I was more annoyed by that bug. Now my phone is complete. :)

(just experienced once in about 30 trials... didnt know why but really cant reproduce that easily again. before it was 100% reproducible in EVERY trial... :D)
[Nexus 4 Original Android Development] larry_walker:
has the AOKP team made the switch, or plan to make the switch, to Koush's superuser app?
[Nexus 4 Original Android Development] partylikeaninjastar:
Re: [ROM] [4.2.2] AOKP :: jb-mr1 :: build-4 :: mako

Had a few reboots today, got the log of the third: https://www.dropbox.com/s/02vm4afsoa1hmyg/2013-03-06-11-58-03.txt

After the second reboot, I had some additional issues. When the phone started back up, the set up wizard came up asking me to put in the name of the owner. I noticed quite a few of apps were uninstalled and the Play Store was giving me error -24 on those, but I fixed that by deleting their entries in data/data. Everything seemed fine until the reboot just now when I tried to watch Hulu
[Nexus 4 Original Android Development] akz080:
if I am on Baseband version: 1700.33 on 4.2.2 AOKP Build 4 do I need to update my baseband and modem before I flash to build 5 + new gapps?
[Nexus 4 Original Android Development] odeccacccp:
-NavRing target UI just keeps crashing from first time I enabled it, did reset nothing, just crashes.

-Gesture Keyboard does not pop in words, just has the blue line.

---------- Post added at 03:35 PM ---------- Previous post was at 03:34 PM ----------

no u don't have to, but if you are not using LTE, you may want to as it's made for 4.2.2 and may or not be better for your usage and area where you are in.
[Nexus 4 Original Android Development] akz080:
ahh so if I flash to the new one its bye bye LTE?
[Nexus 4 Original Android Development] phonepersonality:
Okay...I remember around the time when the Xylon N4 ROMS first came out a lot of people were having 'Baseband Unknown' issues.

If I remember clearly; at that time it was attributed to bad flashing practices and some complications with ClockworkMod. The matter was never fully settled though. There may be more information in the Xylon Thread though. I haven't been there in a long while.

As a matter of principle, I NEVER flash a new kernel without first booting into a ROM at least once after the initial install.

I don't think it's a good flashing practice for one and it also adds another layer of complexity when troubleshooting potential issues i.e. Was the issue with the original ROM or with the new Kernel?

This is just my opinion though and I'm not putting anyone down.

All in all, I'm glad everything turned out okay.
[Nexus 4 Original Android Development] Paragon_X:
Yes .48 disables LTE but .33 allows LTE but disables Google Now service.
[Nexus 4 Original Android Development] akz080:
thanks, so not much has been proven if .48 is better than .33 other than just patching up a loophole. Thanks for the replies.
[Nexus 4 Original Android Development] phonepersonality:
Yes. The original radio will still let you access LTE networks though.

I'm optimistic though, that once T-Mobile (which is what I use) finally goes live with their LTE deployment, either a new baseband will be released that re-enables LTE or some of the geniuses on here will come up with a workaround.

Time will tell.
[Nexus 4 Original Android Development] Paragon_X:
I mentioned this a few posts back, sorry to bring it up but I was wondering if anyone still has the issue of twitter composing box being cutoff at the top and the bottom being stretched to the bottom (hidden below keyboard?). As I mentioned this was a problem aware by Roman and others but was never addressed. I hoped with Build 5 all would fix that but no luck. Also I use Falcon Pro in conjunction however I hate their widget, it's the only thing stopping me from making a complete jump, go figure.
[Nexus 4 Original Android Development] odeccacccp:
YES! stay at .33 for LTE. It works just fine with 4.2.2

---------- Post added at 03:53 PM ---------- Previous post was at 03:51 PM ----------

-LTE will not be re-enabled, it has nothing to do with the carrier, it's Federal Agency problem, Google never paid for license for it on this device.

-Baseband is not an open source, I've had number of Android devices and never anyone modifies the Radio(maybe RIL/non RIL at the very most)

So if you want LTE stay on .33, you can use it even if Lime Pie is out, you could have used GB radios if there where any.
[Nexus 4 Original Android Development] trillo69:
Has the screenshot option been removed from navigation bar? I mean, I was able to assign screenshot to buttons on navigation bar (either a button or long press action) but now I can't find the screenshot option so the only way to take a screenshot is through shutdown menu.
[Nexus 4 Original Android Development] vaa:
AW: [ROM] [4.2.2] AOKP :: jb-mr1 :: build-4 :: mako

Can anybody provide me a link to the recent stock kernel?
[Nexus 4 Original Android Development] Mnemoch:
Re: [ROM] [4.2.2] AOKP :: jb-mr1 :: build-4 :: mako

... or just press power and volume down at the same time.
[Nexus 4 Original Android Development] odeccacccp:
Re: [ROM] [4.2.2] AOKP :: jb-mr1 :: build-4 :: mako

Google awesome wipe nexus 4

Or

Faux has one in OP in his kernel thread
[Nexus 4 Original Android Development] BLADESMAN1889:
Re: [ROM] [4.2.2] AOKP :: jb-mr1 :: build-4 :: mako

I'm also getting this problem also. (I have to confess that I didn't notice it until you pointed it out :eek:)
[Nexus 4 Original Android Development] phonepersonality:
Chill my brotha.

It don't gotta be like that :)

First, radios are updated typically for version compatibility and improvements yes?

I've used .33 on 4.2.2 but can you really vouch for how dependable it will be on KLP?

Also...are you saying is that it's absolutely IMPOSSIBLE for the licensing fees and payments to be made retroactively?

You forget (or maybe don't know) that T-Mobile in the USA is working on Launching an LTE network and although the Nexus 4 is a GSM-carrier agnostic device, T-Mobile is the one provider licensed to sell the phone as part of it's stable. There's probably some Canadian carriers that are in the same position.

That's called leverage.

So I hold to my earlier statements.

If it's mutually beneficial to both parties, the licensing issue will not be a one for long.

Not to mention the fact that its not as though the .33 baseband files are gonna vanish from existence.

One can always revert to an earlier baseband if that's what's required, eh?

I think we'll be okay :)

Having said that...if you're currently taking advantage of LTE on your network, I can totally understand why you wouldn't want to change radios.
[Nexus 4 Original Android Development] capcanuck:
Re: [ROM] [4.2.2] AOKP :: jb-mr1 :: build-4 :: mako

Xda needs more users like you.. Jus sayin
[Nexus 4 Original Android Development] Psilocin:
Can someone explain what "banks gapps" are and how they differ from the official gapps? Can't seem to find a download or thread link for that.
[Nexus 4 Original Android Development] 12Fully:
Re: [ROM] [4.2.2] AOKP :: jb-mr1 :: build-4 :: mako

Yes. I feel like it's been like this for awhile but I've just now noticed it. I mainly tweet by texting though as well.
[Nexus 4 Original Android Development] phonepersonality:
Check this out: http://xdaforums.com/showthread.php?t=2012857
[Nexus 4 Original Android Development] chw2006:
So I updated to build 5 and now I don't get any signal.

Did a dirty flash, would ideally like to not start over since I just did a clean flash of build 4 last weekend.
[Nexus 4 Original Android Development] trillo69:
Yeah I know, but I can do that with stock rom, that's why I'm asking why the option of adding a shorcut option to navigation bar has been removed. It was pretty useful for me.
[Nexus 4 Original Android Development] CloudTown3:
Re: [ROM] [4.2.2] AOKP :: jb-mr1 :: build-4 :: mako

Reboot should fix that. Happened to me too.
[Nexus 4 Original Android Development] chw2006:
I rebooted numerous times and re-flashed twice.

Turns out it has nothing to do with the ROM...T-Mobile's not working around my area right now. Other people aren't getting signal either. Weird.
[Nexus 4 Original Android Development] ernadr:
One stupid question.

For flashing this rom I must first unlock the bootloader, root my phone and install custom recovery, I'm right?
[Nexus 4 Original Android Development] Koraboros:
Yes
[Nexus 4 Original Android Development] beren:
dirty flashed build5 everything seems to be ok + very smooth..

only issue is that i don't see the alarm tile anymore and if i switch from tile to traditional notification the alarm icon disappear from status bar too until i untick/tick the option in alarm app...

anyone getting same behavior?
[Nexus 4 Original Android Development] odeccacccp:
Re: [ROM] [4.2.2] AOKP :: jb-mr1 :: build-4 :: mako

Chill??? I answered your question based on read materials. You can think what you want i really dont care, i dont have lte problem, don't know why would you think I do.

You did not know the basics asking your question, instead of proposing your opinion that contradicts the facts please go to the right threads read and stop twisting my words.

I was not hot to chill, just answered how it is, its been discussed in 3 threads.
[Nexus 4 Original Android Development] Flynny75:
I had this a lot on B3... It seemed fix in B4, and is now back again in B5.
[Nexus 4 Original Android Development] :
Got the same exact thing, posted about it earlier.......

+1
[Nexus 4 Original Android Development] Hanny:
Re: [ROM] [4.2.2] AOKP :: jb-mr1 :: build-4 :: mako

confirmed not seeing the auto alarm tile anymore :) in the past yup there was one when an alarm is set
[Nexus 4 Original Android Development] Razer(x):
R: [ROM] [4.2.2] AOKP :: jb-mr1 :: build-4 :: mako

CM alarm has options like shaking and turning the phone around to disable the phone

Cab you add them on AOKP too?
[Nexus 4 Original Android Development] phonepersonality:
Good morning to you too :)

Is the acrimony really necessary?

I actually am going to think what I want. I'll be crushed that I don't have your blessing, but that's okay ;)

I don't know you and I'm pretty sure I didn't ask you a question to begin with.

I never said you had a problem with LTE or a problem of any kind for that matter.

What's the contradiction? Because I choose to disagree with you on something? Unless your name is literally 'Mr. LTE Radio', you're not the authority on all facts surrounding this matter.

I also never twisted your words. You know how I know? Because I didn't paraphrase anything you said.

As far as 'not knowing the basics', the depth of my knowledge on this matter (HINT: It's VAST) is not on trial here and I know better than to get into pointless and unproductive arguments (on the internet of all places) just for the heck of it.

We can always agree to disagree, my dearest friend.

And finally....Chill!

Having a sense of humor is a good thing. No matter what the Right-Wingers tell you :)
[Nexus 4 Original Android Development] Fille84:
Too bad the recent apps option takes forever to open after a while when theres a few apps in the list. Besides that it works great, no more reboots.
[Nexus 4 Original Android Development] odeccacccp:
try a custom Kernel, Harsh or Matri1x, you may find it smoother.
[Nexus 4 Original Android Development] Spitfire:
Should be getting my N4 today. I've looked back over several pages and I don't see too many bugs, is build 5 a daily driver? Love me some pink unicorn.
[Nexus 4 Original Android Development] sglscovill:
Re: [ROM] [4.2.2] AOKP :: jb-mr1 :: build-4 :: mako

Hahahaha, AWESOME! The perfect attitude and what a great response. You sir are a gentleman and an Android scholar!!!

This made my day.
[Nexus 4 Original Android Development] odeccacccp:
this is only official release, the one you asking about is this:

http://xdaforums.com/showthread.php?t=2146885
[Nexus 4 Original Android Development] Spitfire:
This official one is what I'm lookin for :) I assume it's good to go, just double checking.
[Nexus 4 Original Android Development] TrenchKato:
Re: [ROM] [4.2.2] AOKP :: jb-mr1 :: build-4 :: mako

Is anyone else's com.android.phone constantly force closing again on build 5
[Nexus 4 Original Android Development] Mnemoch:
Sorry, probably off topic but since this is the ROM I use I don't know where else to post it...

On B5 when I connect my Bluetooth headset my keyboard stops working correctly. If I use SwiftKey the suggestions keep blinking and the left and right cursor moving keys blink. If I use the stock keyboard the whole keyboard appears to blink with the loading animation reoccurring constantly. Typing is basically impossible as during a 'blink' the keys are not responsive. Disconnecting my headset cures it.

Any ideas? A setting on the headset maybe? I haven't used this headset for a while so not sure if it worked on any other build really and searching didn't find anything. I tried turning the voice keyboard off in case it was listening during a 'blink' but that didn't work. Reboot didn't work. etc.

Thanks for any suggestions.
[Nexus 4 Original Android Development] HyperM3:
Sounds like it wasn't a clean install. I would recommend a full wipe and re flash. This happened to me with one of the earlier builds when I did the dirty.
[Nexus 4 Original Android Development] hosmsdos:
Re: [ROM] [4.2.2] AOKP :: jb-mr1 :: build-4 :: mako

I have noticed recent app is a little slow. The thumbnails of apps does not load quickly like before I have had this issue in multiple custom ROMs. Plz can someone take a look at it. Also I think everyone here will agree to change the kill all button it looks really bad.

I am using Franco kernel BTW clean installation

Thanks
[Nexus 4 Original Android Development] HyperM3:
I can't believe people are so worked up about the kill-all button. It's just a button. It doesn't affect performance or show on the main screen. It could be a picture of dog poop for all I care. If people are nitpicking this rom to the point where the big complaint is a button you use for a split second then that means this is a damn fine rom.
[Nexus 4 Original Android Development] hosmsdos:
Re: [ROM] [4.2.2] AOKP :: jb-mr1 :: build-4 :: mako

Its not a complain. I love this ROM and I am camper. I want this to be fast beautiful and stable that's it :D
[Nexus 4 Original Android Development] Psilocin:
If I try to press the recent apps button again after it opens in build 5, it doesn't clear out all the listed background apps. It only closes the recent apps screen and goes back whatever app you were using. I don't know if the list clearing is a bug or something that has been implemented in paranoidandroid, which is the rom I just came from.
[Nexus 4 Original Android Development] Flynny75:
Its a PA feature. And personally, one I don't like, and would prefer not to get merged into AOKP (at least, without an option to disable)
[Nexus 4 Original Android Development] MoooN:
since upgrading to build 5 i cant get my calendar to work

tried different gapps packages

its synchronizing but just not showing any entries

somneone got a solution ?