yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] Paulicat:
Fair enough, although the google dialer has been extracted too and added to certain gapps packages.

I was just curious if there was some completely missing feature that was unobtainable outside of the google factory images.

I'm sure there might be a missing commit here or there, but downloading and compiling a certain tag (android-4.4.4_r2.0.1 for example) and adding the proprietary parts (google dialer, google keyboard) you should be at a near identical place as what the factory images provide.

Where we will be stuck is if google doesn't provide proprietary binaries we will have to use older binaries that may introduce bugs.

Besides all that, great work [MENTION=1050103]sykopompos[/MENTION] on this port!
[Nexus 4 Android Development] ramjet73:
If you read through that thread someone mentioned that the "portable hotspot" might be missing from the AOSP ROM but I haven't confirmed that.

Again, the best way to find out is to flash a "pure" (as opposed to AOKP, PA, Slim, etc.) AOSP ROM and check it yourself.

In any case, the different/missing pieces have to be hacked in "kitchen" style and cannot be included in the source since Google doesn't make that available.

For anyone that may not be familiar with the term "kitchen" it comes from the Android Kitchen which is a tool for disassembling ROM's and their components, customizing them, and putting them back together. That tool is usually used for stock ROM's versus the AOSP based ROM's like AOKP, Slim, ParanoidAndroid, etc., that are compiled from AOSP source with source level modifications. CyanogenMod is based on AOSP but with a heavy dose of Code Aurora Forum (CAF) updates that make it more of a hybrid.

ramjet73
[Nexus 4 Android Development] Paulicat:
I will have to check my wifes phone (she's running my own build of aosp 4.4.4 on her nex4, I'm running this L) to confirm but 99.99% sure tethering is in aosp.

There really should be no functional difference between factory images and aosp (as long as you add the google parts mentioned earlier).

In other words, strip away the google parts from the factory images and you should end up with exactly what aosp provides.

Once L source is published we will most definitely have a great base to build L from seeing as we know how stable L is running through the great work done by [MENTION=1050103]sykopompos[/MENTION] on this rom.

If no L kernel is published someone will have to hack together things like project volta to get the full deal.

Nothing is impossible if you have the source!
[Nexus 4 Android Development] adstraylight:
I've now got a mental image of Syko with a big bag of popcorn....:cowboy:
[Nexus 4 Android Development] ramjet73:
They will have to publish the kernel source under GPL licensing but a lot of stuff can be buried in the binaries below the HAL interface. Hopefully that will be the same for AOSP and Nexus stock.

My bigger concern would be if Google apps and other binaries (like the dialer) aren't compatible with AOSP when hacked into the ROM. For example, [MENTION=1050103]sykopompos[/MENTION] believes that Hangouts provides a messaging infrastructure that is used by the other messaging apps in "L" but is that just the app or are there some proprietary "L" pieces below it?

Only time will tell.

ramjet73
[Nexus 4 Android Development] Paulicat:
They only need to publish if there is in fact a new "release" for nexus4. That is the ultimate hope.

The messaging infrastructure I am guessing is the MmsService.apk and yes, we will have to wait to see if that code is included in the aosp tree. It would suck massively if they remove core functionality that is supposed to be provided in aosp (basic phone features such as dialing, sms/mms is what aosp is supposed to provide) but you can't put it past any company to do whats right for themselves rather than the benefit of any community.
[Nexus 4 Android Development] ramjet73:
"L" could be the release where Google differentiates between "basic" functionality in AOSP, and "enhanced" functionality that is implemented in their ROM's with closed source, which is essentially what all the other smartphone vendors have been doing all along with their stock ROM's.

BTW, you need to make another post quickly to get off that evil number. :eek:

ramjet73
[Nexus 4 Android Development] adstraylight:
Well for my non-dev two peneth worth, I think we may be seeing which way the wind is blowing, evidenced by the not insignificant changes to the SE Linux policy that caused Syko so much of a headache. Perhaps the big G has decided they don't need the indie scene to help promote their services anymore.
[Nexus 4 Android Development] Paulicat:
Haha, didn't even notice so there goes that number ;)

Unfortunately I have to agree, this could be where things get ugly...

---------- Post added at 03:24 PM ---------- Previous post was at 03:20 PM ----------

I think most of xda would agree and say "big mistake G" if that happens...
[Nexus 4 Android Development] ramjet73:
Agree, that might be an indicator. Combined with the fact that they are now in bed with Samsung for the KNOX security it may be that AOSP stays open but the Nexus stock ROM's become more like what the other vendors (Samsung, HTC, LG, Motorola, Sony) offer with proprietary interfaces and enhancements.

The Nexus 5 has been more successful commercially than I think Google expected so they may pursue a dual strategy of developer releases (like the GPE versions from the other vendors) versus enterprise/consumer releases in the future.

ramjet73
[Nexus 4 Android Development] pirigu:
battery

Hello guys a question ... How come I consume a lot of battery? Just doing an hour of screen with Kernel Hells Core b47 ... you too? Uate What Kernel? Thank you in advance:o
[Nexus 4 Android Development] CamoGeko:
Sounds like some apps are eating your battery, the drain shouldn't be anywhere near that much!!

I'm using Unleashed kernel btw
[Nexus 4 Android Development] pirigu:
and however strange ... With Cm 11 and the same app consumption not so much
[Nexus 4 Android Development] blacknikname:
stock kernel B7
[Nexus 4 Android Development] googleygoggles:
I could use another nexus 4 [emoji6]

Just kidding, you should get it back to stock and sell it for ~$200 on eBay...
[Nexus 4 Android Development] pirigu:
thank you very much then re try to put
[Nexus 4 Android Development] CamoGeko:
I got more than that on Unleashed kernel.
[Nexus 4 Android Development] PsychoPhreak:
Thanks for the tip, it has already been flashed back to 100% stock factory 4.2.2 :)

If you change your mind and aren't kidding, message me for the clist ad with details. Figured I'd try start local (and in the community here) before heading to ebay and their fees. That and I have 0 rep as a seller, only a buyer rep. If nothing else, I'll probably use swappa and then I can link to my sig :P

I'm coming to this device from a MyTouch 4G slide, so to say it's like night and day is an understatement. And the number of posts this thread gets per day is crazy and often hilarious, keep up the good work all!
[Nexus 4 Android Development] googleygoggles:
Well... Remember when I told [MENTION=1050103]sykopompos[/MENTION] about the 5GHZ signal being weird? (~50+ pages back)

I don't know if this will help but:

Yaman is my 2.4GHZ and Yaman 5 is 5GHZ

And

The highlighted pink is my 5GHZ WiFi WAY AT THE BOTTOM even when next to the router
[Nexus 4 Android Development] adstraylight:
Step away from the printer! The vaporised ink will seep into your brain!
[Nexus 4 Android Development] sykopompos:
You guys are both right in a sense.

Pure aosp is not the same as a nexus build even with the proprietary binaries and google proprietary bits.

There is a lot of changes between the 2 and thankfully most google app packages do provide almost everything but there is still some bits that are missing in the framework and other parts that distinguish a nexus build beyond a full aosp build but I can't think of them right now.

As far as selinux.

Selinux takes a white list approach and has to be specifically added and mentioned for the function to be approved by the system. For the normal user there is not a problem, it is when you are a root user using root apps that becomes the issue.

Selinux defines a function basically in it's own sandbox and gives functions explicit directions of when it can interact with another sandbox and exactly what can be done playing with that other process.

Previously on android, only certain things where sandboxed while the rest was left in a big general sandbox for everything else, that has changed going into L. Everything even su is in it's own sandbox and the never allow rules are very very very strict (even setenforce is in the never allow rules)

Now of course we can add our own rules since selinux is open source but unless the ROM developers feel like adding explicit permission for each root app to function they will break (this is why root apps that don't work in the official preview work here) or we have to go full permissive.

This functionality of selinux gets even tighter with Knox which is basically a more advanced version of selinux which confines it even more.

Now the problem we are gonna run into in the future is how tight do they wanna make it. We can compile new sepolicies to match and make them permissive and then reload the policy but the ability of reloading the policy can be removed, it can also be tightened beyond the current sepolicy and mac-permissons that we are currently seeing also.
[Nexus 4 Android Development] ramjet73:
I guess you finally finished your big bag of popcorn. ;)

Thanks for adding your perspectives. :good:

ramjet73
[Nexus 4 Android Development] adstraylight:
I think it's too late - s/he thinks s/he's a lamp..... but then I think I'm a leopard gecko so what do I know :laugh:

Hang on I've just spotted a fly.... Yum!
[Nexus 4 Android Development] sykopompos:
I just woke up and got my first dose of caffeine so it might not be the clearest for everyone and I might have confused a few people in the process.

I just couldn't sleep last night and laid in bed tossing and turning all night plus my back has been really hurting the past couple days
[Nexus 4 Android Development] CamoGeko:
I understood quite a fair bit of it, sounds to me like Google will perhaps make the official builds harder to modify and customise.

Or have I got the wrong end of the stick here...
[Nexus 4 Android Development] sykopompos:
As far as the messaging and other things. We are working with a preview so we have Google's closed source bits and that's all.

There is still a messaging app and service in aosp/emulator/SDK that is different from our own that we will be able to use going forward with the official release. It is that it is all currently routed through Google's hangouts as it's core in the preview.

Unfortunately we are reliant on Google's unfinished apps and services in the preview because I can't get anything else in because it is incompatible with the preview currently (even trying to up-port the aosp apps to work with it)
[Nexus 4 Android Development] sykopompos:
Google has to put out a finished product for the nexus devices that showcases what the newest platform has and is capable of. It has nothing to do with tightening down security on official builds or making it harder to customize. They have a job to do and the nexus devices are their reference devices to show that, they will still be able to fastboot unlock and go about whatever we want on them.

People look at aosp as a source for custom Roms and with the intent of custom Roms, it is not. It is there as reference code for manufactures to build on and make for their devices and for developers to make patches to improve the system.

Aosp really is not for consumers or even power users, it is for developers to create a product, we just get to enjoy that in the process with custom Roms for our reference devices
[Nexus 4 Android Development] sykopompos:
Now I can do a rant and why some things bother me.

The problem I have with all the custom Roms and things of that nature is because they don't give back to the source.

Aosp is supposed to be for the benefit of us all to see it go into every device.

When custom Roms go off on their own and start making massive changes that don't give back to aosp in an attempt to distinguish themselves, we don't get collaboration back with aosp.

These changes that improve the performance or adds in cool features should be getting submitted to aosp to improve the platform not just a ROM.

That is why I believe strongly in community and about sharing back because it improves the platform as a whole and changes should be easily portable between Roms without needing a huge underlying framework that it relies heavily on for it to function. In my opinion, that excludes developers and functions that should be shared for all to enjoy and improve upon. I don't think a feature or performance should be dependent on any specific ROM and everything should be community oriented with the goal and intent of the feature or performance enhancement going back to aosp.
[Nexus 4 Android Development] ramjet73:
I'm assuming you are talking about "pure" AOSP here.

There are certainly developers for AOKP, PA, Slim, Evervolv and other ROM's compiled from modified AOSP source that would argue their versions are ready for prime time. And with the production phones running Android versions that are based on CM, including Flyme and MIUI, the underlying code is still basically AOSP even though they have more CAF code than other flavors.

But if you are saying that the AOSP source code as distributed was never intended to be a "production" ROM, even for the Nexus devices, I totally agree with that.

ramjet73
[Nexus 4 Android Development] sykopompos:
Wouldn't that be a product then?
[Nexus 4 Android Development] googleygoggles:
This caught my eye... You're mentioned here... http://nexus4root.com/category/nexus-4-roms/
[Nexus 4 Android Development] ramjet73:
And who's fault is that?

The source for most of the ROM's compiled from modified AOSP code is readily available and there is no reason why whoever maintains AOSP can't incorporate some of those enhancements. The Sonic Open KANG Project for the Nexus 4 is a mash-up of the features from many ROM flavors that wouldn't be possible if the source wasn't available for those ROM's:

It's there for the taking but the AOSP maintainers have to be interested in incorporating other developers stuff and I doubt that they are. It's known as the NIH (Not Invented Here) syndrome and may be part of the reason that CAF is getting more attention recently since that seems to be more of a community effort.

ramjet73
[Nexus 4 Android Development] sykopompos:
They have to be submitted
[Nexus 4 Android Development] ramjet73:
The "pure" AOSP ROM?

Since you can perform the basic smartphone functions with it I guess you could call it that but I've never seen anyone use it as a daily driver without modifying the source and/or adding bits and pieces from other ROM's. Perhaps if the team that maintains AOSP adopts more stuff from the enhanced versions it will become a real product in the same way that CyanogenMod has over the years.

That sounds like an excuse to me.

The githubs for the ROM's based on modified AOSP source are all readily available and if the AOSP maintainers want to enhance their product they should be pro-active about it.

You snooze, you lose. :rolleyes:

ramjet73
[Nexus 4 Android Development] sykopompos:
No, I meant all those Roms would be a product
[Nexus 4 Android Development] ramjet73:
Of course, since at least some them are shipped with production phones.

ramjet73
[Nexus 4 Android Development] sykopompos:
But then those would be products that have used aosp as a base to make a product and they used it as a reference just as intended
[Nexus 4 Android Development] ramjet73:
:confused:

Do you think there are any developers that produce a stock ROM for a production phone that don't start with the AOSP source? How else would they do it?

I really don't think Google expects any developer to look at AOSP and say "OK, I get it, now I'll go develop that from scratch with my proprietary enhancements".

Guess I'm missing your point. AOSP is not a reference hardware product like a video card. IMO it is intended to be both a reference and a base for further development. But I do agree that enhancing the base would make the additional development easier for everyone. :good:

Sounds like we may be saying the same thing different ways.

ramjet73
[Nexus 4 Android Development] sykopompos:
Actually in the case of lg, they use caf as their base but it is still aosp at it's base.

Reference is the base and yes, it is supposed to be built on.

I was talking about with custom Roms and developers using something as cm or PA or omni as their base for their projects.

Maybe I just explained it wrong when I was not awake enough to explain.

As far as aosp and being maintained. There is a process to get your code contributed, cm is using it and nobody seems to have a problem with it.

As far as the aosp maintainers just gobbling up projects and code, they have a different standard then open source because they are company backed and are liable so things must be contributed and not just added.

I meant advancements should be made on aosp and not some other custom ROM as a base and then contributed to aosp
[Nexus 4 Android Development] ramjet73:
So we do agree, at least that a richer AOSP base would make development easier for everyone. :good:

That would be ideal but I'm pretty sure that Google funds AOSP development and that may or may not suit their business and/or technical interests.

ramjet73
[Nexus 4 Android Development] sykopompos:
The open handset alliance does http://www.openhandsetalliance.com

But google leads it
[Nexus 4 Android Development] ramjet73:
Hmmm...

84 companies in that alliance. :rolleyes:

My guess is that at least some of them want to keep AOSP basic so they can sell their version of Android as part of product differentiation. Even Google doesn't reveal all their tweaks and enhancements to a new version of AOSP until they release it which is one of the reasons we will probably not see an updated preview for "L".

It's the Unix and Linux dilemma all over again. Nobody wants to sell exactly what their competitors are offering so open standards become the least common denominator.

ramjet73
[Nexus 4 Android Development] shayne77:
http://nexus4root.com/nexus-4-roms/android-l-preview-rom-for-nexus-4/
[Nexus 4 Android Development] ramjet73:
I though he was referencing this. A favorite topic of [MENTION=1050103]sykopompos[/MENTION]. :D

ramjet73
[Nexus 4 Android Development] sykopompos:
But that part is obnoxious though. I want to buy a handset based on build quality, design and the hardware. I don't buy a device based on if it runs sense or touchwiz, actually I buy based on if it doesn't have that crap.

Yes the gpe program is nice but maybe OEMS should look at instead branching their specialities into apps or a down able framework that can be bought and downloaded from the store for those that want those features.

You could then purchase and download those apps and framework that you want then, then the manufacturer can just bundle the apps in with their device but have the option to remove them
[Nexus 4 Android Development] googleygoggles:
Actually it was both but I couldn't choose which one to link... So I linked the main page where both are found (Options 2 and 3) to see which ones you would notice first :)
[Nexus 4 Android Development] Joshua Mr PC Repair:
love this one

Been using the pure white l with the L kernel and 260 DPI , I have gotten 25+ hours on one change and that's using it as a mp3 player for work and on the way to work with Facebook and twitter and IG , phone is amazing no wake locks or noting
[Nexus 4 Android Development] kittuboy:
Googley, why do I get the feeling you're that page admin?
[Nexus 4 Android Development] ramjet73:
Near "Pure" AOSP ROM for the Nexus 4

I forgot about this during our AOSP versus Nexus stock discussion earlier today but [MENTION=5334172]Gnome[/MENTION] has a 4.4.2 ROM for the Nexus 4 that is an enhanced version of the AOSP base code. He's already performed some customization so it won't be the same as running "pure" AOSP but it might give some users a feel for what the base code looks like in operation.

ramjet73
[Nexus 4 Android Development] Un Loko:
Does that instruction looks like I should wipe my phone? or am I wrong? I just updated to B7 and it wasn't necessary... It could be confusing to some users. Just a small thought.
[Nexus 4 Android Development] kittuboy:
In TWRP it is quite clear. Wiping data (in the factory reset) will only uninstall your apps but leave your emulated SD card intact.
[Nexus 4 Android Development] sykopompos:
So [MENTION=275009]ramjet73[/MENTION] does turning off journalling make for that much faster of a system? Also what downsides could come from turning it off?
[Nexus 4 Android Development] ramjet73:
It definitely seems faster to me on the Nexus 4 B7 ROM and it's most noticeable on things like the "my apps" listings coming back from the Play Store and browsing through the app drawer.

The major downside I see is possible loss of data for things like SMS messages if journaling is turned off for the data partition and a lockup or power shutoff occurs. But I haven't done that, and you would have go out of your way to do it since flashing the zip file from the simulated SD card prevents turning off journaling for the data partition because it has current activity, as indicated in the recovery.log file. I should probably just remove the data partition related portion of the zip files.

Edit: I modified the zip files by commenting out all the data partition related statements with a "# " in the first two columns so there is no chance these zip files will affect the journaling status of the data partition. However, all the statements are still there so if anyone wants to experiment with the data partition as well as the system and cache partitions, just remove the "# " from the beginning of the those statements.

ramjet73
[Nexus 4 Android Development] sykopompos:
I will have to look into that. I can understand the need for /data needing journalling but on a read only file system like /system, journalling really isn't doing much for us there
[Nexus 4 Android Development] ramjet73:
Turning journaling off for a read only partition should have little to no effect on performance so the difference is either due to a reduction of I/O to the cache partition or a placebo effect. Since we do open the system partition up for R/W access when doing maintenance with tools like Root Explorer it doesn't hurt to turn journaling off for the system partition but the effect on performance from that should be minimal.

ramjet73
[Nexus 4 Android Development] sykopompos:
True but it still has to read it so that could be the effect. It on the cache would be the more noticeable difference as you mentioned
[Nexus 4 Android Development] ramjet73:
I guess if the journal has to be checked for pending updates on reads that could be additional overhead, especially if those updates will never exist, but I'm no expert on how ext4 journaling works.

ramjet73
[Nexus 4 Android Development] perez6991:
System UI FC while playing music?

I'm not sure if this is a bug or if its been said already but when I'm using Google Play Music and have a PIN the SystemUI closes and reopens itself and sends me back to the lockscreen when trying to unlock. If I type my pin again it repeats itself, the only fix is rebooting.
[Nexus 4 Android Development] ramjet73:
Don't use PIN security with the "L" preview. It's a known bug and a pattern unlock is recommended as an interim alternative until the official release.

ramjet73