CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.0.x (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Now for the more specific stuff. Let me preface this entire thread by saying that I'm very much out on a limb here. I, as well as many others, have noticed that there are some fairly significant audio issues in CM stretching back to early CM11 builds for the M8. The general fix has always been "install v4a, and it'll work just fine". This isn't really a fix imho, it's a band-aid.
As such, I've created two repos: 4.20.x Sprint Stock, and 02/26 CM Unofficial (NOT NIGHTLY). I've uploaded the various parts that I think are going to be relevant in comparing the two code bases in the hopes that this problem can be tracked to its origin and finally fixed. The repos are on github as Stock and CM.
As far as the problems that have been noticed, it's good to remember that not all problems related to audio issues are what we're trying to address here. As an example, this is not a bluetooth thread, so bluetooth connectivity problems aren't going to be addressed even if it relates to phone calls or music playback. This is by no means a complete list and additional items should be listed as noted in posts. Some of the issues I feel that are actually related to audio problems are as such:
Distortion at loud volumes; speakers sound like crap when played loud, but not on stock or gpe
Improper playback channels; speakerphone volume level activating through phone channel rather than media channel
Sound dropouts during calls; caller can be heard but not hear M8 user (common with V4A Lolli installs)
Problem Submission: If you submit a problem to the list in your responses, please tag it as such;
PROBLEM_ITEM: [my problem description here].This will allow me to easily search the thread and add additional known issues to the list. If you submit a problem but don't see it in the list, check Post #2 for reasoning as to why the problem wasn't initially added to the list.
Inside the Stock repo is a logcat that I took while performing operations during music playback. Specifically, I started the music playback via Poweramp, opened AudioFx from inside Poweramp, changed the EQ Preset various times,returned to Poweramp, and stopped the music. I'm hoping that starting with the logcat will lead somewhere..... as I mentioned, I'm waayyy out on a limb here.
As for my device, I'm running my own builds of CM12, no cherry-picks, SuperSu, CM kernel w/ no tweaks, NO V4A. Repo sync for this build includes Settings: reorganization merge on Feb 26, 2015 7:35 AM. Anything after is not in the current build, and therefore not in the CM repo.
ALL help is greatly appreciated, unconstructive / disrespectful comments are not. Here's to hoping this goes somewhere.
Saved for Info
It's most likely not possible to fix. Boomsound drivers are closed source. Unless HTC decides to make the drivers open source, then we probably won't be able to get sound fixed on cm. [emoji80] [emoji80] [emoji80] [emoji80] [emoji80] [emoji80] [emoji80] [emoji80] [emoji80] [emoji80] [emoji80] [emoji80]
Yea... that was a statement I made in another thread responding to one of those "Why can't CM fix the audio issues already" posts. I still think that there might be a channel problem, especially with the way that the speakerphone is operating. So far though, I've not found a direct reference to the boomsound drivers in digging through the stock sources.
Rescue9 said:
Yea... that was a statement I made in another thread responding to one of those "Why can't CM fix the audio issues already" posts. I still think that there might be a channel problem, especially with the way that the speakerphone is operating. So far though, I've not found a direct reference to the boomsound drivers in digging through the stock sources.
Click to expand...
Click to collapse
I'm thinking it could be done through the kernel. But that's beyond my skill level.
probably not relevant , but all i got.lol. just found on beanstalk ROM. of course , i wouldnt know what to do with it. lmao.
"all i can really do , is stay out of my own way and let the will of heaven be done"
mrrocketdog said:
just found on beanstalk ROM. of course , i wouldnt know what to do with it.
Click to expand...
Click to collapse
no worries mrrocketdog. can you verify that you do not have audio issues on beanstalk rom? If so, think you can find mixer_paths.xml, audio_effects.xml, and audio_platform_info.xml and post links?
I found up that mixer_paths.xml is indeed used, unlike what some were saying in the other thread. and I'm starting there.
Rescue9 said:
no worries mrrocketdog. can you verify that you do not have audio issues on beanstalk rom? If so, think you can find mixer_paths.xml, audio_effects.xml, and audio_platform_info.xml and post links?
I found up that mixer_paths.xml is indeed used, unlike what some were saying in the other thread. and I'm starting there.
Click to expand...
Click to collapse
no audio issues confirmed. will look for path and report back.
"all i can really do , is stay out of my own way and let the will of heaven be done"
@Rescue9 , all i could find were these under system-lib-hw.
https://www.dropbox.com/sh/3xaqr8nlr19v6mm/AAD2VdLPQf8ijftOxZQiKmeGa?dl=0
if there is some other folder to check just let me know. i think i went thru them all. (maybe just named different?). will also go thru my cm11 nightly and look for above mentioned files. also can confirm no audio distortion on it. ran for about 2 months.
here is cm11.
https://www.dropbox.com/sh/prv441xo5mu25sj/AAAtGuWro9Jz4y3B2E8dtvm9a?dl=0
again , could not find exact files you requested , but uploaded everything with 'audio' in title.
"all i can really do , is stay out of my own way and let the will of heaven be done"
The discussion in this thread is great and definitely development related with an end goal as the rules say. However, since it's unofficial, we decided to move it to Development. Please PM me if you have questions or concerns.
Thanks,
coal686
Forum Moderator
@Rescue9, found maybe something else. beanstalk - system - media - soundimage.
https://www.dropbox.com/sh/whqk8elvgjbd7jh/AACoqdZrxrNH3C1BMn2IHzXha?dl=0
"all i can really do , is stay out of my own way and let the will of heaven be done"
Some possible Kernel help.
Not sure if this will help or not, but I'm running the CM12 based rom Resurrection Remix by: Brian Koluch
The Kernel he includes seems to fix a lot of the speaker distortion issues I was having with my M8. The Kernel is: B14CKB1RD v3.4.36 (g1069d49)
Here's his Google+ RR Community Post: https://plus.google.com/115522815889154627721/posts/d9BApKK8nbx
Maybe you guys can review that Kernel and see what's different, it has some audio commits in it.
toknitup420 said:
It's most likely not possible to fix. Boomsound drivers are closed source. Unless HTC decides to make the drivers open source, then we probably won't be able to get sound fixed on cm. [emoji80] [emoji80] [emoji80] [emoji80] [emoji80] [emoji80] [emoji80] [emoji80] [emoji80] [emoji80] [emoji80] [emoji80]
Click to expand...
Click to collapse
nothing is imposible.
What about using v4a or using a volume limiter ??
fcukmayank said:
What about using v4a or using a volume limiter ??
Click to expand...
Click to collapse
Those are band-aid solutions. The goal is to fix the problem once and for all.
CJ-Wylde said:
The Kernel he includes seems to fix a lot of the speaker distortion issues I was having with my M8. The Kernel is: B14CKB1RD v3.4.36 (g1069d49)
Click to expand...
Click to collapse
This is very informative! After playing around extensively with the config files in /etc/ I'm beginning to think that this is indeed a problem wholely related to the kernel. I remember using Quantum on my GS3 simply because the kernel fixed a number of issues.
Part of the problem that I'm facing is the fact that my M8 doesn't sound all that distorted on the high end. I feel as I'm trying to grease a squeaky wheel when I don't even hear the squeak.
I know that with the build I'm on now with the Kernel I mentioned, things are definitely more clean & clear on the speakers. I'm glad I can help a little bit.
Thanks @CJ-Wylde never knew this Brian guy built Roms for the m8. I see the kernel is a from wyldstallyn using blackbirds git.
OP maybe ask Brian on G+ if he can direct you to who built the kernel and ask them what they changed if anything that is maybe fixing the distortion
krazie1 said:
OP maybe ask Brian on G+ if he can direct you to who built the kernel and ask them what they changed if anything that is maybe fixing the distortion
Click to expand...
Click to collapse
That's a good idea @krazie1. Would you take care of that for the team. I'm still working through lines of code looking for a connection.
I did install the blackbird kernel straight over the 02/28 CM12 build I'm running now and the speakers actually sounded worse. Very distorted at half volume. I didn't even want to increase the volume fie fear of damaging them.
Rescue9 said:
That's a good idea @krazie1. Would you take care of that for the team. I'm still working through lines of code looking for a connection.
I did install the blackbird kernel straight over the 02/28 CM12 build I'm running now and the speakers actually sounded worse. Very distorted at half volume. I didn't even want to increase the volume fie fear of damaging them.
Click to expand...
Click to collapse
Here is the wyldstallyn's kernel github https://github.com/wyldstallyns
I will be flash testing the resurrection remix 5.3.7 build later when my phone charges up
Related
well Im trying to add faux sound control for yuga for omnirom for about 2 months now and it seems like without this I cant move onto my next development :\ I have been rather busy with my life, and most of people here are able to add it successfully it seems like I was able to check it the values get written but does not get read as well as expected.. so maybe someone is able to help me out here..
patch : https://gerrit.omnirom.org/#/c/3473/
Code:
[B][I][U][COLOR="Red"]WARNING![/COLOR][/U][/I][/B]
This is an ALPHA build. Everything is being worked up to come up to speed as
quickly as possible to be with its CM brother. Just be patient and all will
come in due time. But hey, at least is boots up into the system ... LOL
This is an UNOFFICIAL build of SlimKat (although built from offical SlimRom source) and by NO means is this my ROM. I am just compiling from SlimRom Source and credits go to elelinux, xda-garwyn, albinoman and all other coders who contributed to CyanogenMod device tree.
Code:
For which devices. The ROM should work with all klte versions that are qualcomm
chipsets.
Included in the build are:
kltexx,kltelra,kltetmo,kltecan,klteatt,kltedv,klteub,klteacg,kltedcm,klte
(UNOFFICIALLY SUPPORTED): kltespr,kltevzw,klteusc
Code:
IMPORTANT
* DO NOT expect daily builds. I'll build when I'm free.
* DO ask for support in this thread.
* DO NOT use this unofficial build and ask for support at the official threads.
* DO NOT be rude.
* RESPECT all users
* If u see a NOOB question and u don't feel like replying, DON'T, just ignore
that post. If u do reply, good for u.....and be nice in your reply.
Code:
[B][U]WORKING[/U][/B]
Audio
WiFi
Google Now
Bluetooth
GPS
Video playback
Audio playback
Code:
[B][U]NOT WORKING[/U][/B]
Service
Data
Calls
MMS
Hard keys
Camera
Internal/External SDcard mounting
Code:
[B][U]INSTALLATION[/U][/B]
Do NOT use superwipes
Wipe data, cache, and dalvik cache
* ((do not report bugs if you didn't full wipe))
Flash ROM
Flash GAPPS
Reboot
Report anything that is an issue
As of right now I have no way of testing NFC or IR Blaster, so I do not know if they are working on this build or not. Also on this build there is the infamous red box that appears when moving from screen to screen or app. I am going to fix that either today or tomorrow and then post the new build. The reason there is no data or cell reception is due to the APN list which will also be fixed in the next build.
I tested this on my T-Mobile G900T, so if others can please report back on their experience with this ROM on other devices that would be greatly appreciated and I will get those issues resolved as soon as possible. Thank you.
Code:
[B][U]DOWNLOADS[/U][/B]
ROM: [URL="http://d-h.st/2e0"]SlimKat 4.4.4 (QComm)(ALPHA 1)[/URL]
GAPPS: [URL="http://slimroms.net/index.php/downloads/dlsearch/viewcategory/1150-addons4-4"]Click me to pick your poison[/URL]
Great I'll try it out. I've 900F BTW
Thank you. Just remember what is working and what is not working please.
lunerceli said:
Thank you. Just remember what is working and what is not working please.
Click to expand...
Click to collapse
BTW, what the thing that you want me to report?
Just if it boots and the working list is working on your version please.
lunerceli said:
Just if it boots and the working list is working on your version please.
Click to expand...
Click to collapse
Slim minimal gapps.
1st edit: It's booting.
2nd edit: back key, home button and recent/menu key not working? Get NavBar. I like this!
3rd edit: Setting slow to response
4th edit: Stock camera has stopped. Google camera work but need to insert USB storage.
5th edit: Stock Music player not playing
6th edit: USB storage not mounted so can't test out audio/video but ringtone ringing at audio setting.
That's the issues at the moment besides of known issues. I guess i've to restore my backup now. Waiting for your new build thank you.
Ok. Thank you. I will get all of the issues fixed asap.
I'll try it tomorrow but I am also using a sm-g900t so I won't shed much light on the issues/bugs list cause its most likely to be the same as @lunerceli. Still going to flash thou, lol
Thanks for sharing your build with us.
Sent from my SM-G900T
I read your other post in the SlimRoms thread and I'd like to help a bit if I could. I'm going to flash this in the next hour after backing up my memory cards and then I'll grab you some logcats of crashing apps to save you some looking. I know enough to help, but not enough to debug so you aim me at the logs that help you and I'll get you as much as I can.
I run a SM-G900T as well so we will have similar errors. Thank you for taking the time to do this, I really like all the slim roms.
Working: (Mini Gapps)
- Booted and completed setup (hung on "Welcome..." for a bit, it got through)
- Wi-Fi
- Bluetooth/Stereo Bluetooth
- GPS (Took a minute, but did lock with "Device Only" setting chosen)
- Customization Options working (battery color, statusbar transparency, quick tile settings)
- Statusbar brightness slider
- Volume and power buttons
- Real Dark Slim (hangs for a few seconds, but it succeeds)
- Camera works with third party app (Camera ZoomFX) but crashes when taking photo since it can't save to storage (16MP!)
- Headphones (Music stops when unplugged; nice!)
- Music
- Keyboard
- Navigation Bar/Pie Controls
- Dialer
- Root Permissions (had to enable prompt in settings, but it works)
- Secure Lockscreen (Pin Number)
- Normal Apps (Browser, Calc, clock, Dialer, Hangouts, etc.)
Not Working:
- Hardware buttons (Back, Home, Menu/Recents) Tried to run a logcat here, but Android doesn't even see these other than vibration
- No Signal
- Storage (Internal and external can't be accessed) Startup Media Scan Pastebin
- Auto-brightness (Cannot be enabled) Auto-Brightness Log Pastebin
- Occasional Red Rectangle
-NFC (This, once turned on, cannot be turned off and the logcat feedback is about NFC every 7-10 seconds) NFC Feedback Pastebin
Not going to lie, this isn't far from being not only usable, but a daily driver. I'm going to see if I can pull a log later on for Auto-brightness failing and also for startup and maybe see why storage isn't being recognized and mounted. The file system sees both storage cards, /storage/sdcard0 and sdcard1 are both in the root explorer of android tuner, I just get permission denied when I try to access them.
Edit: Ran fix permissions scripts to see if it would mount the memory for me, and it did not. Also, adjusted media scan to prompt and it still didn't find anything. I'm going to try to pastebin you a log for each of the above failing. Got to work on a school assignment first though
Thank you for your feed back bro. I was on 24 hour duty last night and just spent like an hour to bring everything up and build it. I am going to work on it Friday night when I get off of work and hopefully by the end of the weekend it will be daily driveable and I can move to the next project.
lunerceli said:
Thank you for your feed back bro. I was on 24 hour duty last night and just spent like an hour to bring everything up and build it. I am going to work on it Friday night when I get off of work and hopefully by the end of the weekend it will be daily driveable and I can move to the next project.
Click to expand...
Click to collapse
There is no rush, I just wanted to get you some feedback putting things through its paces. I still intend to get you those log files if you find them helpful.
Get some sleep, this project will being be there tomorrow and thanks for tackling this for everyone in the community.
Edit: I put the logs I could get from my device in the last post next to the items in the list. Some things I couldn't pull, but you may know how. Also, and as I mentioned in the post, watching the Logcat scroll every 7-10 seconds I see the NFC log I pasted for you there. Not sure what is causing it, but NFC is toggling itself on and off.
Like I said, no rush on this I just wanted you to have it when you got around to working on it. Now it's my turn to get some sleep and if you need me to pull a log under a certain condition just quote me here and I'll get whatever you need. I'm looking forward to the next test build
Thank you for all of the info bro. I should have the next build up some time Saturday afternoon and almost everything should be fixed. Its been a while since I have done this so I am a little rusty. It is almost like riding a bike. Lol.
Build two is being compiled right now as we speak. I fixed a few things in the code so hopefully everything will work like it should. HAHAHAHA
Okay, so build two keeps stopping and ending in a segmentation fault for the framework.apk... I think I may have fixed it, but really don´t know .. LOL .. keeping the fingers crossed.
lunerceli said:
Okay, so build two keeps stopping and ending in a segmentation fault for the framework.apk... I think I may have fixed it, but really don´t know .. LOL .. keeping the fingers crossed.
Click to expand...
Click to collapse
Awesome thanks for your work! I would gladly test it when it's finished. I came from the Skyrocket a week and a half ago so I am still getting used to the Galaxy S5, but I helped the OP there for SlimKat by testing and providing logs, so just let me know if there is anything I can help with.
Well, every time I get close to getting another build done something gets in the way. I lost my system and had to set it up again. Now whenever I sync the repo it keeps not finding some of the repo saying it can't connect. Lol
lunerceli said:
Well, every time I get close to getting another build done something gets in the way. I lost my system and had to set it up again. Now whenever I sync the repo it keeps not finding some of the repo saying it can't connect. Lol
Click to expand...
Click to collapse
We appreciate that you keep on keeping on and that you keep us updated with this. Developing isn't easy, if it were we would all be making our own ROMs. Whenever you get this build out there will be testers around waiting to flash it to their devices. Me included
Sorry I haven´t posted anything in a couple of days, but I lost my system again and had to start from scratch. Some times I really have VM´s, but on my laptop I take everywhere It is too much of a pain in the ass to install Linux on the side or even straight up.
Just to update though, I am compiling the 2nd build right now and everything is going smoothly. I had to replace some of the Slim files with those from CM just to get past some build problems. I do believe that I have corrected most if not all of the not working. I am waiting for it to finish compiling and test it out before I release it to you guys. I will put up the download link regardless so that you fine ladies and gentlemen can test what and see what is going on in the development. The reason that I like to do this is so that the community can see active development and to compile the lists of what is and is not working with the ROM. I know it is a different approach to other developers, but this is just how I do it. Without you guys we as developers cannot do our jobs correctly and get a working daily driven ROM. Thank you for your support.
Mods please delete this thread. I am merging with another thread of the same topic. Thank you.
Will this rom work on G900FD as it has a qualcom chipset?
The idea behind this project is to compile a Pure AOSP ROM. The difference is I have been little by little including and testing new commits added to the for the most part unstable staging master branch code from Google AOSP that has not yet been tagged for a future Lollipop update., hence the reason for 5.0.2_Plus name. The only change added to the code that was not committed first by Google is that the ZIP can be flashed in TWRP without replacing TWRP with the Stock Recovery and that is it. At the moment because of limited testing as I do not own a Nexus 4 and all changes have been tested on the Nexus 5 felt untill a few return performance reports best to call this a beta version. With that said the same changes have made some improvments and fixed a few issues experienced by Nexus 5 users using the oficial 5.0.1 update or compiled from the AOSP android-5.0.2_r1 branch. So if start receiving comments that all has been well on the Mako build or see say 100 download without a complaint reported will remove the beta tag. I suspect this will be the case as the commits are not device related.
I honestly started the project for the Nexus 5 with the idea that maybe as a community a few developers could help work on the project so everyone had an updated version of the latest release version that included the latest fixes and had not intended on compiling for the Nexus 4. After my second release another XDA member had asked if it would be possible to make a Nexus 4 port for a friend. At that point as there had been little interest in the project by other Nexus 5 Developers I would post the Mako ota package I compiled for the user who had asked for one. I also have my own Starship Rom and am part of a new developer team so again was meant as a community project and not intended to be released as my Rom or really even released at all with the intention of being a resource for other developers to either use as the base of whatever new AOSP Rom they may intend on developing or selectively picking pieces or fixes. So going with the same idea after compiling the asked for Mako version thought why just limit the idea to just the Nexus 5 as all Nexus devices share the same code from AOSP with exception of needing to add a different set of propriety vendor blobs and choosing a different lunch command for building. So the same goes as intended for the Nexus 5. If any Nexus 4 developers would be interested in joining in on the project Just let me know and I will grant full access to the Github account and create a new branch so we can test and insure the master branch is always %100 stable if it is going to be used by other Nexus developers..
A few examples of the commits that have been added.
https://github.com/Android-AOSP/And...mmit/20063610490eabc91db5ef13a550ecbdcdc6dc1a
https://github.com/Android-AOSP/And...mmit/16c0cfd5920c6d09824d13b7ee94436de87b37e3
https://github.com/Android-AOSP/And...mmit/b9e7a844fc751b9fdda7d452dee361f15815199b
https://github.com/Android-AOSP/And...mmit/18cca2773e4f3890e2ff9ca416400d48f62b98f5
https://github.com/Android-AOSP/And...mmit/a05556633ae5a6d1db164597b93f8b6cbbdf2608
https://github.com/Android-AOSP/And...mmit/e6beb1369165f97a4df24a1d1966c41e392c44e7
https://github.com/Android-AOSP/And...mmit/be42994b5a42914071adddfd5d989950e8e47bd9
https://github.com/Android-AOSP/And...mmit/0c89e1b9395093f71cf73508553d5e4058093ec0
https://github.com/Android-AOSP/And...mmit/4c53a7872b1f37ec184801f16d39584ca3b9bcce
https://github.com/Android-AOSP/And...mmit/9d2f14442f2e1d1507dbdc6cc7b9348513a907f9
https://github.com/Android-AOSP/And...mmit/905c6e72ecdc6e170744649b78e8fbb919f71efd
https://github.com/Android-AOSP/And...mmit/1a96e2b079e8007fe965bd30cd02cb191a613510
https://github.com/Android-AOSP/And...mmit/4fcbf285db7f9e20795783b676963d42499dbd64
https://github.com/Android-AOSP/Android-AOSP_bionic/commit/eaf5aa7d22bd2f6b2eae4c81a60950f89e2d7df4
https://github.com/Android-AOSP/And...mmit/74574e8aa5a2de32e10364fd2f495023fff2a267
https://github.com/Android-AOSP/Android-AOSP_build/commit/49657b7a459ee90b3635bef989f8f9728d564068
https://github.com/Android-AOSP/Android-AOSP_build/commit/1df3707a04651966ca17796f321d23ab3ed6ed2e
https://github.com/Android-AOSP/And...mmit/6fe9c73738e9da0192971576d120802d4c094556
https://github.com/Android-AOSP/And...mmit/44c1c3235d29095c4d987d19155c7260d1a33e0f
https://github.com/Android-AOSP/And...mmit/33baf53861712c3f84606a017943e36bdc680b50
https://github.com/Android-AOSP/And...mmit/a975a08cfb30ad6b2994647c0c6f09e2abd20e28
https://github.com/Android-AOSP/external_protobuf/commit/1a96e2b079e8007fe965bd30cd02cb191a613510
https://github.com/Android-AOSP/external_protobuf/commit/4fcbf285db7f9e20795783b676963d42499dbd64
https://github.com/Android-AOSP/frameworks_base/commit/cc50afe3bdcc3adfa0f4121bf461996996e69a3e
https://github.com/Android-AOSP/frameworks_base/commit/1be740dd60f4d95e1f9ac4aac7e4d6148e3b2dd1
https://github.com/Android-AOSP/frameworks_base/commit/1cca2282dc9a3b7ecc08729af201923842ddfc86
https://github.com/Android-AOSP/frameworks_base/commit/7db1192e72b45111556631dba125a635edff3235
https://github.com/Android-AOSP/frameworks_base/commit/b29136581cc3181e59193e0b6448f0c3f5990081
https://github.com/Android-AOSP/build/commit/de655233a4308340fc71490e86fd0f218cc7fec4
https://github.com/Android-AOSP/build/commit/ab6f841841a0930c7e178a949ada39152e24540f
https://github.com/Android-AOSP/hardware_libhardware/commit/9ede7f730bca338cd3ccad8962e253f28ae17976
https://github.com/Android-AOSP/hardware_libhardware/commit/d4f431fec4136f6eeee919ac3190762fba832942
https://github.com/Android-AOSP/hardware_libhardware/commit/898bcd96e3d80e99d9200cceb4af754bae6d5f4a
https://github.com/Android-AOSP/bionic/commit/d90f39af35c1f2a9972198f92e803e3ca73ac910
Downloads
Download Rom
aosp_mako-ota-ota-5.0.2_plus_r2.0_test.zip.zip - 184.51 MB
aosp_mako-ota-ota-5.0.2_plus_r1.0_test.zip - 184.52 MB
PA-Gapps
http://forum.xda-developers.com/par...apps-official-to-date-pa-google-apps-t2943900
So far I have been using the "Mini Modular package" for testing without any issues.
Root
Root is optional but recommend SuperSU
http://forum.xda-developers.com/showthread.php?t=1538053
Have had version 2.37 in storage and had been using without issue but updated to 2,40 with last test without any issues. What can I say Im lazy that way so unless having an issue just used what works but figured most would grab the latest so thought it best to give it a test before posting.
Kernel is %100 Stock but going with past experience if mrg666 has a Kernel availible for your device it should be the Kernel you are using.
Mirage Kernel for Stock Nexus 4
http://forum.xda-developers.com/nex...el-mirage-nexus-4-stock-rom-06-04-14-t2485368
Change Log 5.0.2_plus_r2
Removed the below commit "Add ip6-localhost to /system/etc/hosts."
https://github.com/android/platform_system_core/commit/25147416bb105914c3cdf8fd65ca7cc20dae0f3e
Looks like a few apps are not fans of having an ip6 entry for localhost. Transparent Weather Widget for example can not find the device location with the enty included.
In looking for the cause of the above issue also reverted.
https://github.com/android/platform_frameworks_base/commit/e4ec09da0b4a31e23f1a19bdd1ea99e0f87cadac
Honestly reverted looking for the cause and did not remember to restore once identifying the cause. Overall is an old commit and dont think will make any difference whatsoever or would have been tagged for use in a past release so not going to bother.
As usual I am not responsible for your device and you are using anything posted in this thread at your own Risk.
This is %100 AOSP with no extra theming at all including bootanimation so no screen shots, as a Nexus User are probably aware what AOSP looks like at this point.
Don't mean to be rude, but you're still living in 2014, apparently. LOL . Classic mistake, I guess. Check the title dude.
Its cool, such a classic XDA first comment though. Could discover the holy grail and receive 15 comments about a spelling error. Adding I guess makes it that much better. Going to leave it in and see how many times your comment is over looked by someone so proud to have noticed it first, lol.
This is exactly what i have been looking for, we need more Roms like this. Thanks OP downloading now:good:
chairshot215 said:
Its cool, such a classic XDA first comment though. Could discover the holy grail and receive 15 comments about a spelling error. Adding I guess makes it that much better. Going to leave it in and see how many times your comment is over looked by someone so proud to have noticed it first, lol.
Click to expand...
Click to collapse
I hope you don't think it was something personal, man. Your title made my day. With all these exams, I've been all stressed out, and your title made reminded me of the time when I was sitting in bed with the laptop in front of me, thinking it's a long time till the exam session. LOL
Good rom so far, only thing was that data roaming was enabled by default.
dragos281993 said:
I hope you don't think it was something personal, man. Your title made my day. With all these exams, I've been all stressed out, and your title made reminded me of the time when I was sitting in bed with the laptop in front of me, thinking it's a long time till the exam session. LOL
Click to expand...
Click to collapse
I was just joking but still think it will be amusing to see how many skip past your post to point out the same. I actually test software for a living after it has been installed on an energy management diagnostic system both for new version testing and quality control before shipping and need to sign off that each system was checked out including the date. Had just recently worked on my birthday and was a highly unusually busy day but ended up signing off the date as 1976 (my birth year) on about forty systems. What is even more humorous is the amount of complaints from technicians who thought they received a system using a Nexus 7, now 9 for use as a portable User interface believed they had received software that had not been checked out since 1976. With that said most installers come from an HVAC technical school background and still use AOL as their contact email address. Lol!
nibla101 said:
Good rom so far, only thing was that data roaming was enabled by default.
Click to expand...
Click to collapse
Will look into that I'm happy to know it is working out. I basically just took my N5 source added the Mako vendor blobs and compiled using a different lunch command. Will go back and see if data roaming being enabled by default is a result of my updates or is set in general aosp 5.0.2 after work. Even though intention is keeping as pure as can be should still be looked at.
Think it would be nice if we could get a few devs together from across the current Nexus devices lineup and do our best to keep an aosp Rom available adding in the latest updates and bug fixes into the most current release for all Nexus devices. Not just for users but for other devs to use in their own aosp based work. Beleive if we could get something like that going would be pretty sweet and not all that time consuming. Still lots of updates added by Google devs every day. Some a bit more complicated then what I have done that a small group could easily bang out and test. Everything comes from the Master aosp branch that can get messy with constant new commits around the clock but think if selective in adding into latest release could be a beneficial project. So using my phrase of the week with that said I am going to build and post a version for all the Nexus devices in an attempt at gaining interest in the project. Again with that said I am torn for tonight as can try producing thr first N5 version that is sprint compatible or build for my Nexus 9. I am very much looking forwored to trying it out with jusst Simple ol aosp but at the same time feal bad for the Nexus 5 Sprint users who are all stuck on stock because other Roms are missing the aditional files added in for the radio to work. Decitions, decitions, decitions.
chairshot215 said:
I was just joking but still think it will be amusing to see how many skip past your post to point out the same. I actually test software for a living after it has been installed on an energy management diagnostic system both for new version testing and quality control before shipping and need to sign off that each system was checked out including the date. Had just recently worked on my birthday and was a highly unusually busy day but ended up signing off the date as 1976 (my birth year) on about forty systems. What is even more humorous is the amount of complaints from technicians who thought they received a system using a Nexus 7, now 9 for use as a portable User interface believed they had received software that had not been checked out since 1976. With that said most installers come from an HVAC technical school background and still use AOL as their contact email address. Lol!
Click to expand...
Click to collapse
LMAO. That was funny
flashed yesterday with nothing to complain until now
thanks for this build
edit: found first bug (maybe)
whle setting Chronus Weather and also Transparent Clock Widget
the phone couldn't find it's location.
Pop up on the screen stated....
"Cannot retrieve location!"
Network geolocation is disabled
Set a custom location or enable location
already try High Accuracy, Battery saving and Device only but it never show my location
the widget always appear with "Loading weather data"
If i choose Battery saving then Google Location Reporting will turn grey and not clickable, other two option made it clickable again but still my location show "Loading weather data"
maybe someone are having this too?
how to fix it please?
thank you very much
groovepeppy said:
flashed yesterday with nothing to complain until now
thanks for this build
edit: found first bug (maybe)
whle setting Chronus Weather and also Transparent Clock Widget
the phone couldn't find it's location.
Pop up on the screen stated....
"Cannot retrieve location!"
Network geolocation is disabled
Set a custom location or enable location
already try High Accuracy, Battery saving and Device only but it never show my location
the widget always appear with "Loading weather data"
If i choose Battery saving then Google Location Reporting will turn grey and not clickable, other two option made it clickable again but still my location show "Loading weather data"
maybe someone are having this too?
how to fix it please?
thank you very much
Click to expand...
Click to collapse
Think I got the fix and am compiling now. Hopfully have up by tonight if not morning. I am on the N5 though and have no issue with beatifull widgets finding my location or maps with navigation working which is my goto test apps along with GPS test. After reading your post tried Transparent Clock Widget and the app was not able to find my location. I did manage to fix this on my N5 so am rebuilding for Mako using the same source. Now have all the Mako Vendor proprietary blobs set up in vendor so can build either Hammerhead or Mako depending on lunch command. Still though will need testing on N4 as I am on the N5.
chairshot215 said:
Think I got the fix and am compiling now. Hopfully have up by tonight if not morning. I am on the N5 though and have no issue with beatifull widgets finding my location or maps with navigation working which is my goto test apps along with GPS test. After reading your post tried Transparent Clock Widget and the app was not able to find my location. I did manage to fix this on my N5 so am rebuilding for Mako using the same source. Now have all the Mako Vendor proprietary blobs set up in vendor so can build either Hammerhead or Mako depending on lunch command. Still though will need testing on N4 as I am on the N5.
Click to expand...
Click to collapse
will test it later
thank you for responding
groovepeppy said:
will test it later
thank you for responding
Click to expand...
Click to collapse
Know prob but had been unsuspectingly busy but compiling the what believe will fix the issue for the N4 and it comes down to the smallest commit.
Know prob but had been unsuspectingly busy but compiling the what believe will fix the issue for the N4 and it comes down to the smallest commit.
https://github.com/android/platform_system_core/commit/25147416bb105914c3cdf8fd65ca7cc20dae0f3e
Since at lease back in the 4.4 days of AOSP, the nexus 5 (and probably others) has had an issue with the camera when in video mode. There's a nasty green line that appears on the side of the video during playback.
It's an easy fix; just replace the file /system/lib/libmmcamera_interface.so with the one from the factory nexus image.
I have poured over the source code for this library, but I can't find out what it is that causes this anomaly nor why it is fixed in google's image, but not in the AOSP source. How can this have been an issue for so long? Am I the only one who runs self-compiled AOSP on my N5?
Anyway, does anybody have any idea what the cause is, or how to fix it in the source?
Hello!
I started searching to fix that issue this morning and i ran in to your post. Ive been building a while from aosp sources with minimal editing only, and i think this hasnt happened with 5.0.2 for me. Now that ive merged 5.1 into the source, i saw it happening again.
I checked few trusted developers vendors, blobs, etc. And i managed to make this:
https://github.com/sicknemesis/android_vendor_lge/commit/de6831773e3e083cef8d53f344f0a03f6a604268
As i write, im flashing and bootin a rom build with this commit and it seems its working correctly now.
All credits to original authors as seen in original commit! Hope this was the thing we are looking for and i see not lot of people check this Developer Discussion forum . I DO!
Gene Poole said:
Since at lease back in the 4.4 days of AOSP, the nexus 5 (and probably others) has had an issue with the camera when in video mode. There's a nasty green line that appears on the side of the video during playback.
It's an easy fix; just replace the file /system/lib/libmmcamera_interface.so with the one from the factory nexus image.
I have poured over the source code for this library, but I can't find out what it is that causes this anomaly nor why it is fixed in google's image, but not in the AOSP source. How can this have been an issue for so long? Am I the only one who runs self-compiled AOSP on my N5?
Anyway, does anybody have any idea what the cause is, or how to fix it in the source?
Click to expand...
Click to collapse
Wow, so the N5 was never intended to use the AOSP version of that library. I never checked the qcom binaries nor noticed that it was included there.
Thanks for this!
The Boot2Gecko people have a source fix for it:
https://bugzilla.mozilla.org/show_bug.cgi?id=1117662
https://github.com/mozilla-b2g/device-hammerhead/commit/c37663f828891cf7a49451a04f3f1ce7f7e5c054
Thanks. It appears that the same lack of patch exists in the M source. I'll try it when I get a chance.
This may be an odd question and I might be completely out of my depth. I got a swanky new set of bluetooth headphones for my Nexus 6 earlier this week so that I can surreptitiously play more games with audio at work. I noticed a handful of the games I wanted to play had incredibly bizarre sound distortions.
Doing some digging and asking elsewhere pointed me to a defect in the Unity engine that describes this exact case. (Tried to post a URL here but apparently I have too few posts. Unity Issue tracker 758142)
Apparently this is a feature that is only supported by some devices, so I was hoping there might be a way to bypass or toggle this feature until the Unity defect is fixed and some of these game makers update their apps.
Any pointers?
Okay, seemed to have figured it out myself:
Using Root Explorer, renamed /etc/permissions/android.hardware.audio.low_latency.xml to .bak and restarted
Some games not having the issue, now.
Make a backup!
spamman5r said:
This may be an odd question and I might be completely out of my depth. I got a swanky new set of bluetooth headphones for my Nexus 6 earlier this week so that I can surreptitiously play more games with audio at work. I noticed a handful of the games I wanted to play had incredibly bizarre sound distortions.
Doing some digging and asking elsewhere pointed me to a defect in the Unity engine that describes this exact case. (Tried to post a URL here but apparently I have too few posts. Unity Issue tracker 758142)
Apparently this is a feature that is only supported by some devices, so I was hoping there might be a way to bypass or toggle this feature until the Unity defect is fixed and some of these game makers update their apps.
Any pointers?
Click to expand...
Click to collapse
Only supported by some phones or only supported by some bluetooth devices?
helix139 said:
Only supported by some phones or only supported by some bluetooth devices?
Click to expand...
Click to collapse
Only supported by certain phones, apparently. Here's the relevant extract from the android configuration XML mentioned in my reply comment:
Code:
<!-- This is the feature indicating low-latency audio, as specified by the
CDD. ONLY devices that meet the CDD's requirements may declare this
feature. -->
<permissions>
<feature name="android.hardware.audio.low_latency" />
</permissions>
this could help fixing some games, but it's lowering the sound quality.
could someone give me a backup of this file ?
happy tree said:
could someone give me a backup of this file ?
Click to expand...
Click to collapse
I'm not sure I follow you. The OP talks about renaming the file to prevent it getting used. Did you try that, but delete it instead?
Anyway, you should use the version of the file that belongs to your rom. If you deleted that, just dirty-flash your rom to get it back.
If your rom comes without the file, then we must assume that the rom developer found that to be the best. Talk to your dev if he is active.
If you just dump an old version of the file into a new rom, there is no telling what will happen. But feel free to try. The contents of the file is listed in a previous post.
---------- Post added at 05:19 PM ---------- Previous post was at 04:40 PM ----------
happy tree said:
could someone give me a backup of this file ?
Click to expand...
Click to collapse
Okay, I just read some more. This file doesn't seem to change the system behavior. It just sets a flag that apps can read and that tells them that the phone supports low latency.
In the OP's case, some games used different code when they found the flag, leading to the problem. But I assume that that has been fixed long ago.
You can find the original file here:
https://android.googlesource.com/pl...ta/etc/android.hardware.audio.low_latency.xml
I looked at the folder indicated, but on my rom (Nitrogen Pie) the file isn't there. However, if I can trust the app I used (System Info for Android), the flag is set anyway. So it seems it gets set elsewhere.
thanks bro, but i already flashed the ROM again, sorry for late reply