So as a learning experience, I have been trying to build a ROM that hasn't been compiled for my device. I have already compiled CM10 as a trial run just to test an official build in my environment and make sure everything was set up correctly. Everything works as per the CM10 nightlies for my device. I was able to merge the CM device/kernel files into the other source and get it to compile after quite a few hours (days?) of figuring out and tracing bugs. I was then left with a build that was about 95% functional; device boots up, sound works, no real major problems that I could find. The only thing was that when trying to download certain apps from the play store, they would tell me my device wasn't compatible with the app. In other ROMs which my device is officially supported though, I have no problems with the play store.
I also noticed that my baseband was being reported as "unknown" in settings. Thinking that may have something to do with the play store, I began working on that; tracing down what in CM reports the baseband that just wasn't jiving with the ROM that I was building. After a while, I found the problem and fixed it. The new build now reported the baseband correctly, and magically the play store no longer was giving me errors. Since I now had a version where the major bugs were worked out, I wanted to change the output name of my build and change my kernel source to a different kernel. After changing that to my liking, I flashed that version onto my phone and noticed the play store was again telling me that certain apps weren't compatible with my device. Thinking maybe the kernel swap had busted my progress, I reverted the kernel changes and re-built. Still had the problem. I reverted my output name change (being the only difference now between the build that worked and now) and it was still incompatible. After flashing the new build; which should have been identical to the working build in every way, the play store was still not working correctly. I decided to flash the build that I knew was working... even the original in which all market apps could be downloaded was telling me apps weren't compatible and was acting just like every other build.
I have performed "make clean" after each build, each time I flashed my device I performed a factory reset and formatted dalvik and system. What am I missing? What does the play store use to determine compatibility? I've been told it goes by the ro.build.fingerprint in build.prop; I've tried the values used in CM10 official (which mine was in the first place, using the CM device files), CM9 official, ICS official, GB official... none of them make the play store change it's compatibility message. Also of interest, when telling me my phone is incompatible when surfing from my computer browser, it's listed the exact same as when I'm in a version of android which allows me to download.
What am I overlooking?
lordcheeto03 said:
So as a learning experience, I have been trying to build a ROM that hasn't been compiled for my device. I have already compiled CM10 as a trial run just to test an official build in my environment and make sure everything was set up correctly. Everything works as per the CM10 nightlies for my device. I was able to merge the CM device/kernel files into the other source and get it to compile after quite a few hours (days?) of figuring out and tracing bugs. I was then left with a build that was about 95% functional; device boots up, sound works, no real major problems that I could find. The only thing was that when trying to download certain apps from the play store, they would tell me my device wasn't compatible with the app. In other ROMs which my device is officially supported though, I have no problems with the play store.
I also noticed that my baseband was being reported as "unknown" in settings. Thinking that may have something to do with the play store, I began working on that; tracing down what in CM reports the baseband that just wasn't jiving with the ROM that I was building. After a while, I found the problem and fixed it. The new build now reported the baseband correctly, and magically the play store no longer was giving me errors. Since I now had a version where the major bugs were worked out, I wanted to change the output name of my build and change my kernel source to a different kernel. After changing that to my liking, I flashed that version onto my phone and noticed the play store was again telling me that certain apps weren't compatible with my device. Thinking maybe the kernel swap had busted my progress, I reverted the kernel changes and re-built. Still had the problem. I reverted my output name change (being the only difference now between the build that worked and now) and it was still incompatible. After flashing the new build; which should have been identical to the working build in every way, the play store was still not working correctly. I decided to flash the build that I knew was working... even the original in which all market apps could be downloaded was telling me apps weren't compatible and was acting just like every other build.
I have performed "make clean" after each build, each time I flashed my device I performed a factory reset and formatted dalvik and system. What am I missing? What does the play store use to determine compatibility? I've been told it goes by the ro.build.fingerprint in build.prop; I've tried the values used in CM10 official (which mine was in the first place, using the CM device files), CM9 official, ICS official, GB official... none of them make the play store change it's compatibility message. Also of interest, when telling me my phone is incompatible when surfing from my computer browser, it's listed the exact same as when I'm in a version of android which allows me to download.
What am I overlooking?
Click to expand...
Click to collapse
Hi guy.
I dev. a rom actually not supported by cyano.
And i had fixed the pb by add of permissions files in /system/etc/permissions and complete build.prop with parameters from another device who work well with market.
Fyi, i have take sgsi9000 to build my own build.prop file
I hope that will help you.
Bizcuite
Sent from my GT-N7100 using xda app-developers app
bizcuite said:
Hi guy.
I dev. a rom actually not supported by cyano.
And i had fixed the pb by add of permissions files in /system/etc/permissions and complete build.prop with parameters from another device who work well with market.
Fyi, i have take sgsi9000 to build my own build.prop file
I hope that will help you.
Bizcuite
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Thank you for your input. I don't know how much of a change there will be using the /etc/permissions files from CM, though I will try it. As for the build.prop, I use the exact same build.prop in CM and the play store works 100%.
EDIT:
I looked at /etc/permissions and the only difference between CM and the one I'm working on right now is that CM has a file called com.cyanogenmod.android.xml. I don't believe that file is needed because I'm not building CM.
Related
It seems that since Google updated Market to Google Play, I can't access or install a bunch of apps that I want.
The two that bother me right now are 'Lookout Mobile Security' and 'Firefox for Android'. If I search Google Play, neither show up in search results. If I use the browser and go directly to either Firefox's or Lookout's site to install, I get redirected to Google Play and the Install button in both cases is grayed out and nothing happens.
And I'm very unhappy that I can no longer download the apks using my computer and side load/install it.
????????????
I'm on a standard Nook Color, with the newest stable release running in EMMC:
Android version: 2.3.7
Kernel version: 2.6.32.9
Mod version: CyanogenMod 7.1.0-encore
Build No: GWK74
Everything else works fine and I have no other problems or complaints.
Can someone give me some things to try and get this working???
(is this the correct forum for this type of problem??? or can someone please direct me to the right place?? I didn't want to post this to the development forum.)
Same problem here, with last build of Mirage.
I modified the build.prop file, identifying as HTC Vision.
Playstore (in desktop) now shows HTC Vision as my device.
But still no full access to market with my nook, I can't see gmail app, for example.
I tried again to change build.prop with Nexus S as device.
Playstore has not even noticed the change.
Any hint ?
filigi said:
Same problem here, with last build of Mirage.
I modified the build.prop file, identifying as HTC Vision.
Playstore (in desktop) now shows HTC Vision as my device.
But still no full access to market with my nook, I can't see gmail app, for example.
I tried again to change build.prop with Nexus S as device.
Playstore has not even noticed the change.
Any hint ?
Click to expand...
Click to collapse
I don't have your Rom, but never had problems with Nightly Cm7 or needed to change build.prop file.
Did you try again with flashing recommended gapps for your ROM?
Unleashed from my Revolutionized Desire HD
Yes, I flashed again gapps after having wiped cache and data, and restored stock build.prop.
Now market works again.
I think I lost full market access when I changed the resolution, using LCD resolution, though this app doesn't seem to change anything in build.prop.
Maybe the solution is there: http://forum.xda-developers.com/showthread.php?t=1580827
The market has always been weird on my Nook. It randomly decides to not allow me to install some apps one day, then will allow me to install the next. Not sure what the cause is either. Just says the device is not compatible.
filigi said:
Yes, I flashed again gapps after having wiped cache and data, and restored stock build.prop.
Now market works again.
I think I lost full market access when I changed the resolution, using LCD resolution, though this app doesn't seem to change anything in build.prop.
Maybe the solution is there: http://forum.xda-developers.com/showthread.php?t=1580827
Click to expand...
Click to collapse
Any report of a fix yet? My Nook has also weirded out after changing LCD resolution!
Taken from the samiam's old cm9 thread
If you notice that some apps are missing from the market, this may be due to the fact that these ICS builds for the nook do not include support for apps which request phone permissions. Although this ideally would be fixed by developers not requesting phone permissions for their app unless it absolutely needs to be phone-specific, you can also fix it by flashing the telephony-permissions-fix.zip file located in the misc folder. You will likely want to flash this file immediately after flashing your rom.
Click to expand...
Click to collapse
greenmuggy said:
Taken from the samiam's old cm9 thread
Click to expand...
Click to collapse
Helped with a few but not what I was hoping... bit it did help
Sent from my SPH-D700 using XDA
Anything other than the standard LCD densities will not allow access to some applications. There is a list somewhere that I had bookmarked, but must have deleted it. If you search for the densities that are standard (MDPI, HDPI, etc) and set it, it may help.
Yeah, these missing apps are most likely a result of a non-standard LCD Density. To fix this, you can install a hardcoded 160 dpi play store that does not run an LCD Density check. If for any other reasons you can't access apps (different country or whatever), this hardcoded play store will let you.
See the thread with DL links here: (http://forum.xda-developers.com/showthread.php?t=1551118)
Make a backup of your vending.apk in /system/app/, and then rename the hardcoded play store to vending.apk. Place the hardcoded vending.apk in system/app/, change permissions to rw-r--r--, and reboot. Should work right away. If not, follow the additional instructions in the link above.
I take no credit nor liability for the results of following these instructions. Make backups of every file you replace and you should be alright.
Hello!
I'm attempting to modify DSPManager in CyanogenMod to add monophonic audio output for users that are partially deaf and need system-wide mono audio. I've made some basic changes so far just to add the option, and got everything building. I've already been running my own builds for a while, and making changes to stuff outside of packages/apps seems to always go fine.
When I just rebuild the DSPManager module using "make DSPManager" the build succeeds and I was able to get the .apk on my phone. However, attempting to install the .apk results in an error installing. I believe this is due to the fact that it is a system app, but I'm just guessing. With that I did a full build to hopefully pull in my changes. Flashing my new build didn't have any errors, but now DSPManager isn't even showing up in the app drawer.
There must be something I'm missing, right? I've clobbered and am rebuilding from scratch now, but I'm not sure if that will make a difference or not. Any tips or suggestions? Is this a signing issue?
Thanks for any help!
-Phalangees
I have the HTC ReZound VZW Phone still I was able to root the phone but with S-ON
I would like to upgrade to at least 4.1 android version, but...
I read a lot of the updated roms do not support HD video or the camera app does not work right.
As I said I do not have S-OFF Feature its still in S-ON mode but its rooted.
the main reason I want to modify the phone is I don't have enough ram and my phone is very slow and laggy.
I downloaded a few apps that let me toy with swap file, but it says my stock kernel does not support creating a swap file.
So is there any standard kernels that I can use currently on my current build with out having to flash roms?
Can I use a custom kernel on my current build with out losing any of my data apps that allows me to create a swap file...
That is mainly what I'm looking for here the ability to create a swap file to have a bit more ram to work with and maybe speed up the phone.
I'm fine with the 4.0.3 version of android tho I learned most new apps made today require at least 4.1 and above.
...but with out S-OFF and reading the custom roms info. I can see the camera apps and streaming HD and such things do not work. to me that stuff is essential.
So basically what I'm asking for help is a kernal I can flash on top of my current rom that allows me to create a swap file.
Unless anyone knows of any custom roms that also allow this that has a working camera app and HD streaming etc. not any bugs.
I know this is a old phone and prob most of the dev for this phone is outdated but Its still a decent phone and I'm sure lot of work has been done with the series since then.
Any help here is much appreciated.
This should work for you.
http://forum.xda-developers.com/showthread.php?t=1911297
Thank you for the reply but the site is 404 to download the kernal :/
This site can’t be reached 404
and
vp-zp.com’s server DNS address could not be found.
although the git hub seems to be online and says files are there from 3 years ago I really have no idea which files to grab or how to even use them isn't the kernel just something I download and flash threw CWM ?
Sorry, didn't think about that part. You can check out his older kernels here https://www.androidfilehost.com/?a=show&w=files&flid=370. Can't seem to find any working mirrors for newer ones.
oh alright yeah I was able to download the Funky_Kernel_v2.1 zip
I applied it after rebooting it says "Android is upgrading... optimizing applications X of 179. "
to which after the OS boots up as it normal does...
So I'm assuming the kernel worked, but... it still says your device kernel is not swap compatible... :/
meistfx said:
oh alright yeah I was able to download the Funky_Kernel_v2.1 zip
I applied it after rebooting it says "Android is upgrading... optimizing applications X of 179. "
to which after the OS boots up as it normal does...
So I'm assuming the kernel worked, but... it still says your device kernel is not swap compatible... :/
Click to expand...
Click to collapse
I picked this kernel specifically because it does have support as mentioned by the dev:
http://forum.xda-developers.com/showpost.php?p=36124568&postcount=2502
It looks like it was on 2.1. You might try a newer one and test again. It might be the app is not compatible with how he implemented the swap part. Someone in the thread mentioned using Android Tuner for it. Not sure if that might be the trick...have not messed with swap partitions in years...
yeah it shows
[KERNEL][SENSE] Funky Kernel v4.2 Post #2502
but 4.2 is not online for me the latest i could find that worked was 2.1
hmmmm
LOL it also deleted my CWM backups.. and everything on my sdcard I just noticed well ****... looks like i'll have to make a back up of the back up for if it bricks now :/ still trying to get a swap compatible kernel too
meistfx said:
LOL it also deleted my CWM backups.. and everything on my sdcard I just noticed well ****... looks like i'll have to make a back up of the back up for if it bricks now :/ still trying to get a swap compatible kernel too
Click to expand...
Click to collapse
That post was in reference to v2.1.
The A-I-O folder has newer kernels.
yea I see but 3.4 is the newest still don't see 4.2 hmmm I think 4.2 is the only version that supports swap but will find out oh **** I got my SD card working and back up in case of a brick.
I'll flash the kernel now to 3.4 its the latest I can find :/ will let u know if it supports swap tho I don't think it does.
meistfx said:
yea I see but 3.4 is the newest still don't see 4.2 hmmm I think 4.2 is the only version that supports swap but will find out oh **** I got my SD card working and back up in case of a brick.
I'll flash the kernel now to 3.4 its the latest I can find :/ will let u know if it supports swap tho I don't think it does.
Click to expand...
Click to collapse
I linked you to the point of the thread where he says he added swap. If you go back a page or two, you can see they are talking about the current version at that time, which is 2.1. So any of them after that should support. This is why I've linked to it and mentioned it.
oh I see... well I can confirm on the version I'm running now it does not support swap.
well after trying to flash kernal 3.4 it get (status 7) failed so its not working
ok ok ok
So after some time here I downloaded all the kernels on that site from version 2.0 all the way up to 3.4 and flashed from one version after another in order to what I could grab.
I think the last one that actually worked was 2.3 or 2.4 all the ones after that failed it said something about no file or dir found at tmp/something/zImage.
so I'm on a never version than 2.1 now at least. but it still is not working...
says...
your device kernel is not swap compatible.
Figure I would try and look at that Android Tuner app you was talking about I searched the market and can not find it.
so after trying every single one of Snuzzo kernels I still can not create a swap file
any Ideas?
meistfx said:
ok ok ok
So after some time here I downloaded all the kernels on that site from version 2.0 all the way up to 3.4 and flashed from one version after another in order to what I could grab.
I think the last one that actually worked was 2.3 or 2.4 all the ones after that failed it said something about no file or dir found at tmp/something/zImage.
so I'm on a never version than 2.1 now at least. but it still is not working...
says...
your device kernel is not swap compatible.
Figure I would try and look at that Android Tuner app you was talking about I searched the market and can not find it.
so after trying every single one of Snuzzo kernels I still can not create a swap file
any Ideas?
Click to expand...
Click to collapse
It's since changed names: https://play.google.com/store/apps/details?id=ccc71.at.free
I find it more likely that the app you are using is not compatible with the type of swap that was implemented by the developer. I'm not really sure. It's not really a common mod anymore and very few people are still on ICS.
Yeah I get that. I would love to be on android 4.1 or above Cyanogen looks great, but... Like i previously stated that whole camera app not working as well as the recording videos and streaming hd videos bug also that would be on my phone is too dramatic as those practical applications are very important to me. Plus I do not have S-OFF
Ok update: well I'm running S-OFF now. trying out CM KK 4.4.4 so good so far as long as I don't update Google Now and the Google App. Still cant get a swap file tho weird thought I would be able to on CM at least. I havn't tried the cam so idk if it has bugs but I can stream video so far. so I can take that off my list.
The Unlegacy Android ProjectIntroduction
Unlegacy-Android started out as the OMAP4-AOSP Project. It was created in late 2015 in order to maintain a clean and organized place for pure AOSP support for various OMAP4 devices, such as the Galaxy Nexus and the Samsung Galaxy Tab 2 series. Over time this evolved to support more than just these devices, but still maintains its roots of supporting "legacy" devices that no longer receive "official" updates: hence Unlegacy Android was born. In our opinion, these ROMs are how the official updates would look.
On top of AOSP, we only include changes which are necessary to support the hardware, be secure, and get acceptable performance. Current features for flo/deb include:
- Linux kernel 3.4.y merged in (currently 3.4.108 - mostly security patches and minor bug fixes)
- BFQ IO scheduler (official kernel 3.4 release), set up so GUI processes have the highest priority
- F2FS support from kernel 4.9 (for /data only!)
- SELinux in Enforcing mode
Installation
If you're planning to install GApps, be sure to read the second post!
Aside from these, installation and upgrading is no different than on other ROMs.
Problems
- No known issues for flo/deb yet.
If you notice anything, be sure to report it in this thread. Stability is our main concern. While I'm kind of busy, I usually read the thread and acknowledge the bug reports, even if I don't reply directly to them.
Downloads
See: http://builds.unlegacy-android.org. Our automated builds ensure that we always have the latest Android security patches merged in, without having to manually start and upload builds
We will have a built-in OTA updater (just like stock) soon (it's a work in progress)
Information about our experimental builds and progress you may find here.
Features?
There isn't much to say here - this is AOSP, if you install GApps, you pretty much get the same thing that's running on the Nexus devices (see the second post). The aim of this project is to create a fast and stable ROM - although, one could use Xposed to add extra features.
As usual, feedback is appreciated
XDA:DevDB Information
Unlegacy Android Project, ROM for the Nexus 7 (2013)
Contributors
Ziyan, Clamor
Source Code: https://github.com/Unlegacy-Android
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.4.x
Version Information
Status: Stable
Current Stable Version: 8.1
Stable Release Date: 2017-03-24
Created 2017-03-24
Last Updated 2019-04-05
Reserved
GApps
If you want to install GApps, we recommend Open GApps Micro.
An important note: as this is a pure AOSP ROM, installing GApps tends to be problematic: in order to try to avoid installation issues, be sure to install GApps immediately after installing the ROM, before booting the system for the first time. If you experience any issues with the Google applications, be sure to go into Settings -> Apps, and grant every permission to every Google application - most importantly, Google Play services.
In the case of an upgrade, be sure to re-install the GApps package, as upgrading wipes /system. You shouldn't need to re-set the permissions afterwards.
Stock-like setup
Disable the following built-in (AOSP) apps:
- Android keyboard (once you installed Gboard)
- Browser
- Calculator
- Camera
- Clock
- Email
- Gallery
Install the following apps from the Play store:
- Google Photos (https://play.google.com/store/apps/details?id=com.google.android.apps.photos)
- Calculator (https://play.google.com/store/apps/details?id=com.google.android.calculator)
- Chrome (https://play.google.com/store/apps/details?id=com.android.chrome)
- Clock (https://play.google.com/store/apps/details?id=com.google.android.deskclock)
- Gboard (https://play.google.com/store/apps/details?id=com.google.android.inputmethod.latin)
- Gmail (https://play.google.com/store/apps/details?id=com.google.android.gm)
- Google Calendar (https://play.google.com/store/apps/details?id=com.google.android.calendar)
- Google Camera (https://play.google.com/store/apps/details?id=com.google.android.GoogleCamera)
- Google Now Launcher (https://play.google.com/store/apps/details?id=com.google.android.launcher)
SafetyNet
The ROM should pass SafetyNet after installing GApps, without anything else. Keep in mind that installing extra stuff (SU, ...) might make it fail!
Rooting
You can flash the latest Magisk to get rooted.
Hello)
Please add a night mode, with the icon in the blind
boom1982 said:
Hello)
Please add a night mode, with the icon in the blind
Click to expand...
Click to collapse
I simply use Darker for night time playing in the bed personally, I reduce brightness to 65% and apply a slight yellow tint. When most websites are white, theming the framework wouldn't matter that much anyways... and we kinda want to feel like a factory image (no dark mode in them either)
@Ziyan
It's a pity)
The rom itself works fine. Good job)
@Ziyan Thanks for your efforts on these older devices. I've used your work on both Gtab 2 and Grouper before I sold them. I just downloaded 0324 builds for Flo and Hammerhead, neither one matched the MD5. I just downloaded Flo again but still no match. I haven't tried flashing any of the roms yet but figured I'd let you know.
Also, don't know if you use Netflix but it's been a problem getting a current version of the app working properly on ANY Nougat rom for Flo. Without any modifications, the Netflix app will load and give you an option to download and watch at a later time. However, if you try to just do a normal streaming of a movie or show, it will give you an error 0013. As is mostly the history of Netflix, it appears to be a drm issue. @Startrek852 was able to compile a zip with drmblobs that will eliminate the error 0013 and allow normal streaming but you lose the ability to download and watch at a later time. Although I don't use Google Movies, it's my understanding that it will not work if you flash the drmblobs.
Anyway, just wondering if "in your travels" you've heard of this Netflix issue and might possibly know of a proper fix. Thanks again.
Mike T
webdroidmt said:
I just downloaded 0324 builds for Flo and Hammerhead, neither one matched the MD5. I just downloaded Flo again but still no match.
Click to expand...
Click to collapse
This issue seems to haunt us... We'll try looking into it again ASAP. Oddly enough, every time I download, I get a match, and it flashes perfectly
webdroidmt said:
Also, don't know if you use Netflix but it's been a problem getting a current version of the app working properly on ANY Nougat rom for Flo. Without any modifications, the Netflix app will load and give you an option to download and watch at a later time. However, if you try to just do a normal streaming of a movie or show, it will give you an error 0013. As is mostly the history of Netflix, it appears to be a drm issue. @Startrek852 was able to compile a zip with drmblobs that will eliminate the error 0013 and allow normal streaming but you lose the ability to download and watch at a later time. Although I don't use Google Movies, it's my understanding that it will not work if you flash the drmblobs.
Click to expand...
Click to collapse
Play Movies works perfectly, so I'm not sure how to debug that either ways - can look into that zip later on.
Ziyan said:
This issue seems to haunt us... We'll try looking into it again ASAP. Oddly enough, every time I download, I get a match, and it flashes perfectly
Play Movies works perfectly, so I'm not sure how to debug that either ways - can look into that zip later on.
Click to expand...
Click to collapse
Thanks for your reply. Here's the D/L for the drmblobs zip if you decide to take a look. https://www.androidfilehost.com/?fid=529152257862690585
Very weird on the MD5 thing, as mentioned I downloaded it twice and on a desktop PC so it shouldn't be a mobile issue??? I'm gonna' flash it later, will report if there's a problem.
Mike T
@Ziyan
Updates come out every day ...?)
And why the cache is not f2fs?
I'm sorry that there are a lot of questions. I just made this rom basic and I want to figure it all out
p.s. That there were no problems with gapps - you need to restart the recovery after flashing the main rom
have volume wake option?
edit: stuck at "patch image "Patching system image unconditionally..."
boom1982 said:
@Ziyan
Updates come out every day ...?)
And why the cache is not f2fs?
I'm sorry that there are a lot of questions. I just made this rom basic and I want to figure it all out
p.s. That there were no problems with gapps - you need to restart the recovery after flashing the main rom
Click to expand...
Click to collapse
Our little build server likes overdoing its job and building even if the changes don't affect flo - until this is fixed, it's enough to update every 3-4 weeks or so to get the security updates, unless I make an announcement here about a change
About /cache f2fs: there's simply no point, as that partition isn't actively used by the system (other than maybe OTA updates). I usually don't support it, as it can lead to more complications than what it worth...
@Ziyan
Thank you for your reply)
I really like the way the rom works.
Only have to use a lot of additional tools to at least somehow expand the settings)))
Good work... but video recording with green lines in Google Camera 3.2, stock kernel, Nexus 5
Dear author when will you fix problems with wi fi? Wi fi does not catch nexus 5 networks
Mayrbek86 said:
Dear author when will you fix problems with wi fi? Wi fi does not catch nexus 5 networks
Click to expand...
Click to collapse
Mind giving me a bit more details regarding this? I can connect to a Wi-Fi Hotspot created with my Nexus 4 (also running Unlegacy Android 7.1) just fine, and can browse the internet with the Nexus 7 through it (mobile data activated on the Nexus 4)
Mayrbek86 said:
Dear author when will you fix problems with wi fi? Wi fi does not catch nexus 5 networks
Click to expand...
Click to collapse
Installed Build "ua_hammerhead-7.1.1-20170328", Wi-Fi also does not work. I had to install wifi-fix, now everything is fine.
Regards.
maksimus0021 said:
Installed Build "ua_hammerhead-7.1.1-20170328", Wi-Fi also does not work. I had to install wifi-fix, now everything is fine.
Regards.
Click to expand...
Click to collapse
Alright. We'll be soon opening a Nexus 5 thread as well.
Ziyan said:
Alright. We'll be soon opening a Nexus 5 thread as well.
Click to expand...
Click to collapse
Good news! Thanks for your work!
Regards.
maksimus0021 said:
Installed Build "ua_hammerhead-7.1.1-20170328", Wi-Fi also does not work. I had to install wifi-fix, now everything is fine.
Regards.
Click to expand...
Click to collapse
Where did you find this fix wi fi, give me a link?
Mayrbek86 said:
Where did you find this fix wi fi, give me a link?
Click to expand...
Click to collapse
Install via TWRP.
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1 (Nougat), 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.
*
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Unofficial LineageOS Builds
Pixel XL (marlin): https://updater.invisiblek.org/marlin
Pixel (sailfish): https://updater.invisiblek.org/sailfish
Google apps
Google apps (opengapps nano) are baked in to these builds. This is due to the A/B partition layout and complications backing up/restoring gapps between builds. This is not ideal, and is the major road block to getting this device in to official status with Lineage. I also include the Google camera app rather than Camera2 or Snap since it works much better.
Source
While I update the official LineageOS trees with completely usable source, these builds include a few more experimental things than what I would include in official Lineage builds, pending that ever happens. The device and kernel repos that these builds are based off are from my github.
Installation
The easiest way to install LineageOS is to load up twrp (see twrp thread on how to do that) and flash the zip from above for your pixel variant (marlin/sailfish). After that, the built-in updater app should handle future updates via A/B updates within android. Beware this feature is still a work in progress and can be broken at any time as well. If for whatever reason the install fails through the updater app, loading up twrp again and flashing a newer zip is perfectly acceptable.
The LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
[ROM][UNOFFICIAL] LineageOS 14.1 Nightlies for the Google Pixel (marlin/sailfish), ROM for the Google Pixel XL
Contributors
invisiblek
Source Code: https://github.com/LineageOS
ROM OS Version: 7.x Nougat
Version Information
Status: Testing
Created 2017-05-05
Last Updated 2017-05-05
How come gapps are still baked in when there are working gapps for pixel? Beans gapps works fine.
Glad to see this finally getting an XDA thread so it gets more awareness. I only knew this existed prior due to the questions and answers thread.
I know OP says it comes with nano gapps. But does that mean that it has all the essential pixel gapps. I can't find myself using the also ones. I wish there was a flashable stock gapps package
TheNewNEXUS said:
I know OP says it comes with nano gapps. But does that mean that it has all the essential pixel gapps. I can't find myself using the also ones. I wish there was a flashable stock gapps package
Click to expand...
Click to collapse
You can't flash beans full gapps? Actually it will probably just have duplicates since gapps are already installed
Having issues with youtube. Is anyone having issues?
pcriz said:
You can't flash beans full gapps? Actually it will probably just have duplicates since gapps are already installed
Click to expand...
Click to collapse
That is correct. However, the there are still those aosp apps that don't hold a candle to the Google alternatives. I am super used to flashing the stock Google package on all my phones. I guess I will just stay on stock May Factory Image until I find one with all pixel features. Lineage OS is one of the most stable ROMs that I have came across.
TheNewNEXUS said:
That is correct. However, the there are still those aosp apps that don't hold a candle to the Google alternatives. I am super used to flashing the stock Google package on all my phones. I guess I will just stay on stock May Factory Image until I find one with all pixel features. Lineage OS is one of the most stable ROMs that I have came across.
Click to expand...
Click to collapse
What apps are you looking for that can't just be downloaded from the play store? Any of the AOSP ones can be disabled, so you never see them (yea a bit of a pain but you only have to do it once per app that you replace from the play store). For instance, I install google's calendar app and disable the AOSP one. You can do the same with any other app as far as I know.
invisiblek said:
What apps are you looking for that can't just be downloaded from the play store? Any of the AOSP ones can be disabled, so you never see them (yea a bit of a pain but you only have to do it once per app that you replace from the play store). For instance, I install google's calendar app and disable the AOSP one. You can do the same with any other app as far as I know.
Click to expand...
Click to collapse
All apps are on the Play Store. I will end up disabling them I guess
invisiblek said:
What apps are you looking for that can't just be downloaded from the play store? Any of the AOSP ones can be disabled, so you never see them (yea a bit of a pain but you only have to do it once per app that you replace from the play store). For instance, I install google's calendar app and disable the AOSP one. You can do the same with any other app as far as I know.
Click to expand...
Click to collapse
That's what I do. Then things stay put when you flash an update. If you delete the app it will come back when you flash an update.
Cool beans and good to see you again invis (I've also had tenderloin, d2vzw and vs985 so you've kind of been following me around). How's the general status of the build? Any known breakages?
And btw, the changelog links on the download page don't go anywhere.
Doesn't boot for me. 15 minutes at the boot animation and all that's happened so far is that my phone is hot. Installed 20170506 over NHG47L.
Edit: ah you need to be on N2G47O.
So this is the May O build. It's been said all over the forums but just to nip it in the bud here, don't go trying to flash a different kernel that isn't signed or use Chainfire's zip to sign the kernel, otherwise you'll get stuck in a boot loop. The May bootloader update made it so it won't boot with an unsigned boot image.
@invisblek Great to see you here I've always been a big fan of your work unfortunately I haven't had a device for several years where you were making ROMs for. I'm generally not a fan of lineage but will give this a try just because you built it.
I noticed in the kernels git that you have WALT enabled across the board, but the official spec is to use PELT with EAS - new for rev 1.2. did you have a reason for choosing Walt? It isn't a big deal anyway, assuming the properties are exposed users can use ex kernel manager to turn Wall off and turn Pelt on.
Also 8 branches, 6 active you've been busy! I take it the default 14.1 branch is the kernel used in this ROM? I see all sorts of new stuff across your code and am very thankful you've came over to pixel development.
A side note in regards to build to Verizon users:. I flash the modem and radio from the L build as its May's Verizon only and I don't nearly have as many problems with signal retention. It didn't completely fix the problem but it's definitely been improved. and when I say retention I mean I'll be at the same location and my pixel will suddenly lose signal completely for a random period of time and then go back to having a signal. This used to occur very often the phone would be intolerable without Wi-Fi calling but the L build which specifies it's Verizon only must have had some changes in it to improve this.
Looking forward to trying your work. Thanks for your time and effort!
I don't use either so it doesn't matter to me, but I noticed that LiveDisplay and Color Calibration do not work at all. Neither change the screen color when you adjust them. I'm on the May 5th build right now.
@invisiblek just a heads up. I flashed today's build and Google Camera video recording at 30FPS crashes. "Camera error".
I've posted the logcat before, let me know if you still need one.
It was a full wipe including internal SD, just FYI.
I didn't install any apps or superuser. I booted up for first time and immediately tested Google Camera.
CZ Eddie said:
@invisiblek just a heads up. I flashed today's build and Google Camera video recording at 30FPS crashes. "Camera error".
I've posted the logcat before, let me know if you still need one.
It was a full wipe including internal SD, just FYI.
I didn't install any apps or superuser. I booted up for first time and immediately tested Google Camera.
Click to expand...
Click to collapse
He's already aware of it and I believe he already pushed the fix for it, I just don't think it's been merged. It's something to do with ffmpeg.
Been running or a few days now, everything is good except that the updater doesn't work. It detects updates, clicking the Download button goes to Downloading state, then Downloaded, and the Install button shows up; clicking Install goes to Installing state for a little while then back to Downloaded, and clicking Install again gives a message "an update is already in progress", and the update never completes.
I'm interested in doing my own builds for my Pixel XL, for some stuff I want to test but I'm wondering if you can tell me which SafetyNet patch you're including and what you're including to enable the blue Pixel theme and Pixel navbar.
So, I've been running the ROM for over 3 days now and I've got to say that it has been great so far. Currently using 20170508 right now, and it's all good.
Have disabled all the AOSP apps and have installed all the Google apps from the Play Store to replace them. Everything is almost the way it is on stock.
Had to install the live data wallpapers, and install the Pixel launcher as a system app to get the Now feed integration, but so far it's been like stock but with all the extra features I've wanted. Even installed the AptX codecs, and my phone still passes SafetyNet.
So far the only downsides I've seen are that Google Camera crashes upon taking a second video, haven't gotten WiFi assistant to work yet, and my phone gets a bit toasty playing music but I'm pretty sure that it is GPM being stupid again and not the ROM. But overall it has been an excellent experience.
hobbified said:
Been running or a few days now, everything is good except that the updater doesn't work. It detects updates, clicking the Download button goes to Downloading state, then Downloaded, and the Install button shows up; clicking Install goes to Installing state for a little while then back to Downloaded, and clicking Install again gives a message "an update is already in progress", and the update never completes.
Click to expand...
Click to collapse
The updater has worked just fine for me, taking me from 20170506 to 07 without TWRP installed and from 07 to 08 when I had TWRP installed. Don't if 08 to 09 is broken right now so I need to test.
admiralspeedy said:
He's already aware of it and I believe he already pushed the fix for it, I just don't think it's been merged. It's something to do with ffmpeg.
Click to expand...
Click to collapse
Yes, I was aware of that "fix". And it's already merged.
But it does not work.
Google Camera 30fps video still crashes.
I was just letting him know the fix he was told about does not work.
The fix being to remove FFMPEG from /system/etc/media_codecs.
I even tried deleting the media_FFMPG file and duplicating at /system_root/etc/.