yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] Flak:
noanalytics remix is a hyperlink... follow through to enlightenment.
[Nexus 4 Android Development] IronCityMZ3:
Perhaps a question that may get me flamed a bit but does this have a no limit tethering fix for T-Mobile? I have a note 3 and the roms mention it. My girlfriend has my old nexus 4 and I would like to put this rom on it. I haven't seen any mention of it. If you could let me know I would appreciate it.
[Nexus 4 Android Development] Sir_gpm:
I think if you have rooted and unlocked bootloader nexus 4 with any custom rom, you are free to go. I dint know about the limit, maybe you can apply a patch to this rom. Or maybe its a limitation in the service.
[Nexus 4 Android Development] alleyezondisromo:
Any chances for a lollipop edition?
[Nexus 4 Android Development] sylentprofet:
Yup. Just updating codebases. Should be within the next week or two. Keep posted!
[Nexus 4 Android Development] dirtfarmer7:
How do I download this rom? There is no link in the OP. The OP says Latest download hosted by XDA-DevDB,, but there is no link on how to access DB.
[Nexus 4 Android Development] ppguerr:
http://xdaforums.com/devdb/project/dl/?id=7877 here bro. Cheers!
[Nexus 4 Android Development] dirtfarmer7:
Thanks! They did some remodeling around here, I was a little lost :o
[Nexus 4 Android Development] sylentprofet:
OP updated to Lollipop 5.0.1

Check out news at the top of the post!
[Nexus 4 Android Development] all43:
Fantastic can't wait to give it a run!
[Nexus 4 Android Development] HiM@L:
is it synced with lastest changes from SAOSP ?
[Nexus 4 Android Development] Derangedpony:
Any mirrors? Can't get current to work on my phone.
[Nexus 4 Android Development] sylentprofet:
XDA File Host is back up, so everything is also located there. MediaFire still works too.

Minor update 12/15/2014, attention all flash-addicts, this means you!
[Nexus 4 Android Development] dirtfarmer7:
I was using your original bare bones rom for months and loved how smoothly it worked, it's outstanding battery life, and that there were no bugs in it.

I just downloaded the lollipop version and it doesn't work. I get " unfortunately set up wizard has stopped working" message. The setup wizard has to run before you can access your home screen. Any tips on how to get this working?

Thanks for working on this updated version!
[Nexus 4 Android Development] sylentprofet:
Thanks for the support!

Did you do a clean install (wipe data/cache factory reset)? Most issues I've run into are caused by doing a dirty flash over an older version of the ROM.

I just clean flashed the 12-15-14 version myself (along with the rest of the zips in the Installation Guide) a couple hours ago and it's running smooth, no issues so far.

Let me know if you can't get it working, I know there's a lot of changes being made to the source code right now so something might be a little bit off. New builds will be coming more often now that I'm on winter holiday from class and Lollipop is gaining momentum. Stay tuned!
[Nexus 4 Android Development] sos42:
็How to set Exchange email.

Thanks
[Nexus 4 Android Development] dotnetnightmare:
Using TWRP under wiping go to the advanced menu and select system for wiping. After wiping "system" and the normal ones, install this & it starts without errors.
[Nexus 4 Android Development] jtwebfusion:
I had a similar issue. The setup screen appeared with no status bar. I started over by advance wiping everything, then only flashing the ROM. Once it booted up, I went back into recovery and flashed SuperSU, and gapps individually. Hope that helps.

---------- Post added at 12:26 PM ---------- Previous post was at 12:23 PM ----------

Only issue I'm noticing is that it takes several attempts to clear recents. Anyone else having that issue?

I love having LTE enabled from the start. Its a royal pain to get it enabled on the other Roms.
[Nexus 4 Android Development] dirtfarmer7:
Ha, I switched from TWRP to CWM just to flash this, I don't think it installed properly, because CWM asked if I wanted to root everytime I tried to reboot from recovery, where do I get supersu in a flushable zip file? ........

In going to try again this weekend, I put a new ssd in my computer and don't have ADP set up yet.

Thanks for all the tips!!!
[Nexus 4 Android Development] AnaguaMateus:
Does this LTE works on Europe?

And is possible to work with this Rom with dual boot?
[Nexus 4 Android Development] jtwebfusion:
I got so tired of cwm creating a /sdcard/0 partition, that I switched back to twrp.

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

[BETA][2014.12.16] SuperSU v2.40
[Nexus 4 Android Development] keikun007:
you could base it on Frank build, it's by far the best lollipop build to date

plus, awesome job
[Nexus 4 Android Development] aburyan1:
Downloaded the lollipop and flashed it with no issue, prefect and smooth.

Q- what the best kernel to use with this ROM for best battery performance ?
[Nexus 4 Android Development] KevBri:
HD Voice

[MENTION=2645562]sylentprofet[/MENTION] What is the "HD Voice Hack?" Just a build.prop edit or something else? Have you confirmed that it works? Thank you!
[Nexus 4 Android Development] sylentprofet:
[MENTION=1976209]KevBri[/MENTION] From what I've read on the internets (I could be wrong), there's a few requirements for HD Voice to work. I think on T-Mobile US (the network I have most experience with) as per this article http://xdaforums.com/nexus-4/help/hd-voice-support-t1963885 VoLTE should work, with the 4G hybrid radio and amr-wideband enabled. I've been told by friends that my voice sounds clearer, but note all the requirements in the second post of that link.

Some interesting tests are suggested ie playing frequencies that would be cutoff by the normal codec, but I haven't gone to that extent. Any suggestions/feedback would be welcome!
[Nexus 4 Android Development] KevBri:
Hmm, thanks for the info. I'm also on T-Mobile. I would be amazed if we could get VoLTE working on this phone. Wouldn't an easy test be to just watch if your phone switches from LTE to H while on a call? Every time you call, the phone has to switch to HSPA because of the lack of VoLTE, then back to LTE as soon as the call is over. If VoLTE is working, you shouldn't see that switch. What does your phone do?
[Nexus 4 Android Development] sylentprofet:
I meant to say HD Voice instead of VoLTE, I was doing some reading on the subject while writing my response and wires got crossed. But anyway, it might be possible for VoLTE to work also. I'm having issues differentiating what exactly defines HDV vs. VoLTE and what is actually going on in terms of the voice streams and codec used. Lots of reports floating around with not much empirical data. This article says HDV is just an umbrella term for general audio-enhancing capabilties, many of which are built-in to VoLTE.

As I mentioned before, AMR-WB is enabled so, *shrug*. The audio quality of a call hinges on so many variables you'd really just have to test it for yourself, in your own unique use situations.
[Nexus 4 Android Development] KevBri:
I am also a bit confused by the two terms. It seems like HDV is possible on our phones and provides some enhancement, but VoLTE is a bigger step up. The guys in this thread seem to think it would require new radio firmware. I guess the best people to answer this question would be the developers who created the hybrid radios. However, you'd think if VoLTE were possible, they would have written that in already, ya know?

I used Viber for the first time recently, which is a VoIP app and holy smokes was the call quality amazing. It was very noticeably improved, like the person was next to me, and I would imagine VoLTE would be of similar clarity.
[Nexus 4 Android Development] bluefoxreg:
LTE & GPS won't play together?

Hi first of all thanks for sharing this great rom!

I'm just wondering if anyone else is experiencing the same issue that if I'm using the LTE data (ie using skype chatting etc) then my GPS would not be able to navigate. I vaguely remember there's other discussions on this issue but couldn't find any fixes for this.

Is the only alternative to have GPS working properly while using skype is switching back to the regular none LTE radio?
[Nexus 4 Android Development] firegoblin:
Google maps force close on app startup. I'm coming from a clean install. I tried clearing cache and data with no success.
[Nexus 4 Android Development] sylentprofet:
Works fine for me... What radio are you using?
[Nexus 4 Android Development] :
Tried this ROM out during the JB/KK days, worked flawlessly. Trying it again for LP, and was just wondering which hybrid ROM would be best for T-Mobile's LTE network? I didn't use hybrid ROMs back during Kitkat because I didn't really know too much about it and its benefits.
[Nexus 4 Android Development] cantinaNW:
Fix for blank screen on call problem?

Hi,

Great rom so far! I've only ever had stock until today, because I upgraded to 5 (and straight to 5.0.1) and discovered I lose control of the phone during any call. What a great Stock Rom! So I'm trying bareBones rom now but am having the same issue. Everything else seems to work, wifi, gps, camera, LTE (tmobile) it's great. The specific issue is when the phone engages in a call the screen goes black. Pushing the power button twice will get a very quick flash of what looks like the proper in-call screen, before going back to black. If I get lucky and happen to be pressing on the End Call button at the moment the screen is blinking on/off, then I can end the call and phone operation goes back to normal. Does anyone have any pointers?

Thanks.

---------- Post added at 11:49 PM ---------- Previous post was at 11:15 PM ----------

It's something to do with the proximity sensor which is always showing value of 0. I'll tinker with it to see if it's hardware or software.
[Nexus 4 Android Development] sylentprofet:
I haven't experienced this at all.

When I release a ROM, I try to test it as extensively as possible before making it publicly available. A problem affecting usability like that wouldn't make it into production.

Did you be sure to do a clean flash? I hate to sound like a broken record, but most of the time anyone has a weird problem like this, it's because they didn't Factory Reset (wipe data and cache) before installing the ROM. A "dirty flash" is the easiest way to get stupid issues like this to pop up.
[Nexus 4 Android Development] cantinaNW:
It was definitely hardware. I had replaced the front bezel and screen. Unfortunately there were manufacture defects in the new screen/bezel which were creating IR leakage between emitter and sensor (my best guess at the problem) so I jammed a small piece of plastic in there to "plug the hole" between sensor and emitter and it's working well now.
[Nexus 4 Android Development] sylentprofet:
Ahh cool, thanks for the report back.

Just released an update for the new year, seems snappy so far after a day of use.

How difficult was replacing the bezel/screen, if you don't mind my asking? Just out of personal interest.
[Nexus 4 Android Development] cantinaNW:
It was quite easy. I bought the bezel and lcd / touch assembly all-in-one so didn't have to deal with the lcd. The most tricky part for anyone will be slowly unsticking the battery from its large swath of tape. I used a cut up credit card as a thin wedge. (don't bend the battery) The rest of it is simply unscrewing screws, popping out the connectors and pieces, then placing the pieces into the new frame and reassembling. All told took me maybe 30 minutes going slow, following a youtube video of the process. I had previous experience attempting to repair the broken touch screen of this phone (which failed and I ruined the good LCD). The time consuming bit which added a couple hours was the lack of quality - pay the extra $10-$20 to get a nice front assembly so you won't have these issues I had such as IR leakage, lack of tape, lack of power led diffuser, an incorrectly drilled screw hole, and lack of component cushions. The correct 2 tiny screwdrivers and a soft guitar pick help.
[Nexus 4 Android Development] dbldown7:
I don't think this is specific to this ROM. Just looking for some help.

Phone was running fine on Frank 22 cadavers for about 2 months, then last night my kids were playing angry birds and the phone shut down, tried to reboot, but hung on swirling blobs of color. Rebooted to recovery, wiped cache and Dalvik cache, fixed permissions... still no luck. Decided I was screwed, so I wiped system and installed SIMPLE AOSP hoping to retain/backup text messages before clean install. Phone booted, but SMS were lost. Downloaded Barebones, rebooted to recovery, factory reset, wiped cache/Dalvik/system. Installed Barebones. Booted. Rebooted to recovery, installed Gaaps, SuperSU, new bootanimation, and Titanium backup zip that I had created a few months ago...

Everything boots fine except my phone can't access internal storage. Using Root Explorer, no folders. Using Google Photos app, no photos. I assumed that something in the process had wiped my internal storage, but folders are still there when I look in recovery.

Any ideas? Any help?
[Nexus 4 Android Development] wirapuru:
Wifi connectivity + apps sync @ 5.0.2

Did someone notice a less responsive wifi detection/decision-to-connect-to-better-signal from 5.0.1 to 5.0.2?

Plus, before updating it to 5.0.2 real-time sync apps like Gmail i.e. were updated almost instantly, as soon as I turned on Wifi or Cellular Data (I always turn them off when I go to sleep, and turn them back on when waking up). Now, with 5.0.2, they'll update only after several minutes - not much but it was very noticeable since before it was instant. I'm actually opening the apps and forcing refresh when I need to check overnight messages, and indeed they'll update like they needed a manual refresh.

I'm asking here because

#1: I really had very little experience with bb/LP5.0.1, aprox. one month, but it was an amazingly almost-perfect experience, I was really in love with this ROM (btw thank you so much [MENTION=2645562]sylentprofet[/MENTION] I'll surely donate soon), everything blazing fast and smooth. But since it was so little time with it, it *could* have been lucky days. So I can't tell for sure if 5.0.2 is the "culprit".

#2: although I have some tech knowledge I'm far from knowing enough to properly analyze changelogs, both from bb and Android itself, and I know sometimes minimal internal tweaks aren't even mentioned - so, a big maybe here, it was something not mentioned affecting those aspects?

#3: to update from the exactly-one-version-before-5.0.2 to Jan/15th's 5.0.2-based I only wiped caches 2x, updated ROM + SuperSU, wiped again then booted. Maybe anything got dirty on there?

Anyways, sorry about the big wall of text, I'm actually only interested to know if anyone had similar issues since 5.0.2, so to know it'd be the cause. They're really not that critical, but after experiencing such great performance on the previous version it kept me scratching my head.
[Nexus 4 Android Development] slack04:
I've been having this same problem since flashing this ROM, about a month ago. Did not have any problem before on stock rooted 4.4.2. The problem is annoying but the ROM is so much better than anything else that I have just had to live with it. (I've left a few accidentally blank voicemail messages as a result...).

Can you explain how you determined that it was a hardware problem and how you fixed it? My Nexus 4 is unaltered; never had to replace anything but the screen protector.

Thanks!
[Nexus 4 Android Development] sylentprofet:
One of the optimizations I implement is reducing the frequency at which the WiFi radio scans for new signals.

By Android default it's set to 15 seconds. Which works out to 5760 scans in a 24 hour period.

I figure most people don't change where they are more often than every five minutes, so I bump that interval to 300 seconds (5 minutes), which works out to only 288 scans in a day. Huge difference.

Soooooooo, it kinda comes down to a battery life versus convenience thing. I can try dropping it down to a 1-3 minutes and see how that works for everyone, but I don't want to hear any complaints about "worse battery life" haha.
[Nexus 4 Android Development] wirapuru:
This is great, thanks for clarifying that, now it makes sense. And - at least for me - it's even better, I agree with your thoughts on the unnecessary 15sec scan interval, the tradeoff isn't worth the battery, I really just wanted to know if it was something I've done here or not.

Thank you again! :good:
[Nexus 4 Android Development] cmb6:
Have other people had more wifi dropouts after switching to this ROM, or switching to Lollipop? This is the first 5.0 ROM I have used as a daily driver. Everything has been great, except I do lose the wifi connection more often than I had with Jellybean or KitKat ROMs.
[Nexus 4 Android Development] cantinaNW:
Sorry, this'll be a bit more terse because the forum logged me out while attempting to submit my first version.

Download app "Sensor Box for Android" and use the Proximity Sensor inspector (plant icon).

Use this app while playing with the proximity sensor without a screen in front of it. This means, you'll have to open up the phone, unscrew the mainboard, and dislodge the proximity sensor without unplugging anything. Once the sensor is out (but still plugged in) then you can verify by putting your finger in front of it and watching the app output if it's working or not.

To fix it was a pain. I found a black wrinkle-free section of sheet of plastic (got mine from a small shipping bag) and cut a small segment out. Do you see the left hole of the proximity sensor from front of your phone? the strip length needs to be slightly less than the circumference of that hole (yes, tiny!). The width of the strip needs to be the depth of that hole, which isn't very deep. You'll see once you dislodge the proximity sensor. Very carefully curl the strip in your fingers so it's almost matching the shape of the hole, without creasing the strip. Then use a small screwdriver to push the strip into the hole so the strip is pushing outward on the inside of the hole. The goal here is to line the hole with an IR blocking material to prevent leakage between emitter and sensor once you reinsert them into these holes. This is all best to do while the phone is on because it'll take a few tries until it seems to be working. I just kept poking and repositioning until it 'magically' worked. Good luck! Check out youtube for disassembly tutorials - it's not too hard.
[Nexus 4 Android Development] motherninja:
After updating to the latest release, my Nexus 4 are capable of catching the H+ signal (before that it only capable to display the H signal), although I never flashed any newer radio. My questions is, why is this possible?

*EDIT:

Damn, I just read the updated changelog, the OP has just sold his Nexus 4 :(

I think I need to upgrade my phone too, its been 1,5 years with my Nexus 4, this is the longest smartphone I ever use and owned.
[Nexus 4 Android Development] wirapuru:
Hm, oh damn :\ welp I guess onto finding another ROM then, I'm sad as well because this was my favorite as soon as I installed it.

EDIT: lmao, I see you've sold yours as well ;P my bad
[Nexus 4 Android Development] motherninja:
Yes, yes, yes... I sold my Nexus 4 too and got it replaced by Zenfone 5 :D

I think it's time for me to get some refreshment after almost 1,5 years with my Nexus 4. It is not broken, everything still working fine, even the casing is still looks like new, but I can't resist the temptation of ASUS ZenUI after some of my friend and co-workers bought Zenfone 4 & 5 :fingers-crossed:

BTW, I sold my Nexus 4 with this ROM and the buyer is fine with it, he said it looks just like the stock Android with more functionality :good:
[Nexus 4 Android Development] wirapuru:
Aaw I'll be totally honest with you that I'm totally envious of you :3 right now I don't even think on replacing mine - not only because I'm still in love with it even after almost 2 years but because I can't $$ right now as well heh - but if I would it'd be a Zen, so slick, welp good luck with yours, best regards and experiences with it!
[Nexus 4 Android Development] dasdreHmomenT:
Well, too bad that this is the final version. I loved your approach and have been rocking your ROMs for the last year.

Thank you so much and have fun with your new device!

P.S.: I hope someone picks this up for the N4, a barebones ROM is highly valued, especially for (now) older devices.
[Nexus 4 Android Development] get2easy:
Black Screen when i Call a contact

After the installation of your Rom and apps, I have a black screen with out and in calls. Is this a any bug or what??

Is this a lollipop problem

If nothing else can make.

Sorry for my english.
[Nexus 4 Android Development] nitin.chobhe:
Hello all!

Can someone please upload the last build on some other server? The links in download section does not work. I tried twice the download breaks after around 90-92 MBs. And the speed never goes beyond 25 KBs.

I'm desperate to flash this rom on my mako... (Even after knowing that there won't be any next versions of this rom)

Thanks!
[Nexus 4 Android Development] nitin.chobhe:
Today I was able to download it without any problems. May be yesterday there was an issue with the server :silly:
[Nexus 4 Android Development] spider623:
Since this needs to be minimal, any chance for rro support, it really has no overhead
[Nexus 4 Android Development] alleyezondisromo:
I wish we could have this rom in 5.1 edition
[Nexus 4 Android Development] sylentprofet:
Instructions in the OP updated. There is a fresh build that works with T-Mobile LTE (I'm on their network). Just go to the dialer and enter *#*#4636#*#* and under Phone Info select LTE/GSM.

Settings stick fine after reboot. It's just a one time thing.
[Nexus 4 Android Development] faddyie:
So far so good. flashed PA GAPPS (lightest). One question. Can i flash the motoX 4.4 optimazation zip file onto it.

Thanks
[Nexus 4 Android Development] eng.Colombo:
trying it now...so far so good ! =D

could you include the moto x patch in the next version ? it works fine, and grow up the benchmark values! and the game expirience too...

it will be a very nice way, a very light rom with optimizations !

keep your work !
[Nexus 4 Android Development] faddyie:
OP or any body, pls confirm if motoX zip can be flashed on it
[Nexus 4 Android Development] godsonbx:
Got a fail when trying to install. Any reason why? Did a clean wipe and everything.
[Nexus 4 Android Development] sylentprofet:
Try redownloading it. Might have been an error/interrupt during download, it definitely works fine here.
[Nexus 4 Android Development] sylentprofet:
Just flashed the Moto x zip on my Nexus 4 running Styper 11/24 bld 2, phone boots fine. Works fine so far, haven't tested in terms of performance but so far so good.
[Nexus 4 Android Development] gorilla p:
Can anyone confirm which kernel is to be used with this? I'm assuming any kit kat kernels should work?
[Nexus 4 Android Development] Carlosmadiam:
I use hybrid 33/84, been using it for a while, first of all to have LTE you need a SIM card for LTE, also to have LTE sticking after a call and reboots, I edited a line on the build.prop file from:

telephony.lteOnCdmaDevice 0

to

telephony.lteOnGsmDevice 1

Works like a charm, I use ES file explorer, make sure you set permissions, or use ROM toolbox build.prop editor, no need to change permissions on this one, reboot your phone then go to settings, more, mobile networks, network mode and choose LTE GSM WCDMA, reboot if you want, profit, BTW I use it on Telcel Mexico, don't know if it works on other carriers...
[Nexus 4 Android Development] sylentprofet:
This ROM is LTE enabled by default, no need to edit the build.prop. Just follow the directions in the OP (*#*#4636#*#*) and you're ready to go!