Database Develop

Patch Rom

do i just flash PATCH ROM over OG cause if i wipe data it says rom is bad ???

oilfieldtrsh said:
do i just flash PATCH ROM over OG cause if i wipe data it says rom is bad ???
Click to expand...
Click to collapse
Well yes you can flash over whatever you want as the updater script will format everything anyways.
And as for the ROM being bad, I don't know why, I don't wipe data, the updater script does so for me.

betatest3 said:
Well yes you can flash over whatever you want as the updater script will format everything anyways.
And as for the ROM being bad, I don't know why, I don't wipe data, the updater script does so for me.
Click to expand...
Click to collapse
i go to flash it and it says it is finding update,opening update, installing update package, then it happens installation aborted (bad).zip
and when dowloading it says "enter the last disk amount and click ok to continue"
edit : it says "can't open /sdcard/custom rom/rom.zip
(Bad)" after the opening update package installation aborted i have tried other roms and they work fine

how big is this file suppose to be cause i have been getting different numbers one time it was 256mb next was 347mb and this last time was 341mb maybe i am not getting the whole thing from the site it is downloading from

Just trying to help. When I flash a new ROM/update I get the same message what I do is, select unmount the SD card and then mount it again. then select the file and execute. All this using CWM PAID EDITION. thankfully this was part of the new ROM because now I cannot download paid apps from the play store for some reason..
side note the latest patchrom looks good only minor problems still exist.
bloatware left (ie My Verizon, 4G hotspot, family locator, etc)maybe this was intentional IDK
Home button doesn't work, unsure if there is a way to resolve this on my end.
paid apps from play store won't reload, instead of saying "purchased" it lists the price. when I click to download it takes me to the permissions popup when I press ok it errors out, free ones are fine. having the full paid version of ROM toolbox from jrummy would be great.
WHATEVER YOU DO, DON'T OPEN "SIDEBAR" APP! it asks for supersu permissions then shutdown before you can grant or deny the startup again every 5-10 seconds and repeats. I had to freeze it with ROOTUninstaller to make it stop

Reboot fixed the playstore issue. Home still inop
Sent from my VS910 4G using Tapatalk 2

Phone won't link to computer for mass storage or ADB.
No lockscreen.
Verizon logo when shutting off shifted to the left, along with app tray and grid when moving apps.
Sent from my VS910 4G using Tapatalk 2

Home Button Does Not Work on Patch ROM HELP!!!!
I was excited to flash the new Patch rom over to my Lg Revolution only to know that the home button does not work!!!
I tried reflashing and wiping everything and nothing.
The rom does look cool though, I just wish for the weather widget and to de-bing the browser
Thanks

Themrzxcvb said:
I was excited to flash the new Patch rom over to my Lg Revolution only to know that the home button does not work!!!
I tried reflashing and wiping everything and nothing.
The rom does look cool though, I just wish for the weather widget and to de-bing the browser
Thanks
Click to expand...
Click to collapse
New version coming out lator, so hold on for now.

You give up too
Sent from my Verizon Moto X

[IMG][XT1096] TotalX | root-tether-busybox-sqlite-xposed-hosts-bootanimation-dialer

***** TotalX *****​
I've built a mofo-flashable system image for the Verizon Moto X 2014 containing root, WiFi tethering, Busybox, SQLite3, Xposed, a symlinked hosts file for adblocking, a custom bootanimation, and the stock Google Dialer that has caller ID and allows you to search for business phone numbers. I also added the stock Google Messenger app. I'm currently working on getting CF.lumen to work, and AirAudio is fully functional with this image. I really didn't do much, most of the hard work was thanks to @JulesJam, @Slack3r, @slogar25, @btdownloads7, and @mikeoswego. Shout out to all of them for their hard work.
Download here:
TotalX-1.3.rar
TotalX-1.2.rar
TotalX-1.1.rar (do not recommend flashing, very buggy and drains battery)
TotalX.rar
Instructions:
Download the Xposed installer if you don't already have it, and install it to your phone but don't do anything with it. Also install AdAway 3.0.
If this is your first time flashing an image with Xposed, go into your file manager and delete /data/dalvik-cache/arm and /data/dalvik-cache/profiles. If you don't already have root, just do this step after flashing and reboot.
Wipe cache prior to flashing:
Code:
adb reboot bootloader
fastboot erase cache
Next, extract TotalX.rar to your mofo directory, flash the image with mofo, and wipe cache when its done:
Code:
mofo flash TotalX-1.1.img
fastboot erase cache
It might take a while to boot up, but at least you can enjoy the crazy new bootanimation. When it finally boots, open up AdAway and go to preferences, scroll down to "Target hosts file" and select /data/data/hosts. This sets it so that AdAway modifies the hosts file in /data/data, which is where the /system/etc/hosts file is pointing to.
If you'd like extra heavy-hitting adblocking, add XXXXXXXXXX to your hosts sources (EDIT: Don't do this, it screws up MMS). Then hit download and apply on the main screen and reboot once its done.
Install any Xposed modules you want and reboot. And here's a great module you can't get through the Xposed app: Pandora Patcher
That's it! You should be all set after that with no ads and the power of Xposed. If you have any trouble flashing, don't be afraid to post here and I'll try to help out. And if you'd like to buy me a beer, feel free to shoot [email protected] some cash on Google Wallet
Changelog:
Version 1.3:
- AirAudio is now fully functional!
Version 1.2:
- Removed build.prop edits due to HDR bug and battery drain
Version 1.1:
- Switched to @mikeoswego's base to fix busybox due to Xposed installation removing busybox for some reason
- Google Messenger app added
- build.prop edits by @trimax84
- New bootanimation taken from @motomotomotoG's collection (Geometry Dark), if you'd like any of the others from that page let me know and I'll make you an image!
- Fixed bootanimation memory leak using fix by @arter97
Version 1.0:
- Original, based on @btdownloads7's image, added Xposed, hosts symlink, 5.1 bootanimation, and Google Dialer.
Click to expand...
Click to collapse
Known Bugs:
- Upon flashing, you may experience Google Play Services constantly crashing. Still not sure what causes this. To fix it, uninstall updates for the Google Play Store and Google Play Services, reboot, and then reinstall the update. No more crashing after that.
- If you followed my instructions earlier to add http://adblock.mahakala.is/ to your hosts sources in AdAway, you will most likely be unable to send MMS. To fix this, revert your hosts file and remove this source, then reboot, reapply, and reboot again.
- Version 1.1 was very buggy due to the build.prop edits. The edits create a bug where the camera app crashes when taking pictures in HDR mode. It also seemed to drain battery at a ridiculous pace and created huge slowdowns. I fixed this in later versions and will not be editing the build.prop in future versions.
Click to expand...
Click to collapse

You are the man. I'm downloading now and will flash as soon as I can. [emoji106]

Install went as expected. I was coming from another version of this img with adaway and xposed and bb, sqlite. I cleared cache before and after install, on boot everything went good, not too long. At first everything was smooth, I was letting it settle before playing with the new dialer, then I started getting mass unresponsive apps, mostly google. I did a reboot and haven't had a repeat of the issue yet. Adaway updates fine, xposed modules load fine, and busybox is good. Google dialer is operational if a little slow feeling to me, oh and the boot animation is gorgeous as well. Great work putting this one together, to all who input.

contesauce said:
Install went as expected. I was coming from another version of this img with adaway and xposed and bb, sqlite. I cleared cache before and after install, on boot everything went good, not too long. At first everything was smooth, I was letting it settle before playing with the new dialer, then I started getting mass unresponsive apps, mostly google. I did a reboot and haven't had a repeat of the issue yet. Adaway updates fine, xposed modules load fine, and busybox is good. Google dialer is operational if a little slow feeling to me, oh and the boot animation is gorgeous as well. Great work putting this one together, to all who input.
Click to expand...
Click to collapse
hmmm.. that sound a little scary might hold off until its confirmed that this was a one off issue. But thanks for the upload!

To be fair it happened to someone else on one of the other threads with a dif image. Seems to be a one off after a reboot. Understand your trepidation though.

It actually just happened to me too. Rebooted and hasn't happened again. But yeah, it also happened to me with one of the previous builds as well, so I think it might just be a one-off problem. Will report if it happens again.

It does that with every new flash. Not sure why, but a reboot fixes that sucker.

Thanks for this! Any chance of getting this image without Xposed?

TokedUp said:
Thanks for this! Any chance of getting this image without Xposed?
Click to expand...
Click to collapse
I can do that, do you want everything except Xposed?

ClydeDroid said:
I can do that, do you want everything except Xposed?
Click to expand...
Click to collapse
YES! I had a very bad experience with Xposed once and i'll never use it again. Thanks. There's no rush though. Im on vacation so I wont be able to flash anything or donate to you until I get back home. I really appreciate it man and I promise I'll buy u some beer as soon as i get back.

Is this based off the image that has the HDR fix?

TokedUp said:
YES! I had a very bad experience with Xposed once and i'll never use it again. Thanks. There's no rush though. Im on vacation so I wont be able to flash anything or donate to you until I get back home. I really appreciate it man and I promise I'll buy u some beer as soon as i get back.
Click to expand...
Click to collapse
Alternatively you could flash this image and not use Xposed i.e. don't install the APK. Libs are't doing anything important.

Mayze23 said:
Is this based off the image that has the HDR fix?
Click to expand...
Click to collapse
Yep!

ClydeDroid said:
Yep!
Click to expand...
Click to collapse
Installed! Thanks for the Birthday Present -
As a suggestion you could modify the Build.prop to add a custom Rom Name under settings and custom details etc. That way you can really feel ownership of your changes.
Also if you really wanted you could delete Verizon Apps under the /system/app partition to remove bloatware but I understand that may be a bit tedious and undesirable. Otherwise really good build, worked well - no issues.

Haxxa said:
Also if you really wanted you could delete Verizon Apps under the /system/app partition
Click to expand...
Click to collapse
Or you could just freeze them with TiBU. If you are not going to be able to use the space for anything else, no sense in deleting them. Also some Verizon customers actually use NFL Mobile, Verizon Navigator, MyVerizon, etc.

I've had the gapps issue as well, basically neutered the phone until I forced a restart. A reboot had fixed it temporarily but it came back again a couple of times. I eventually uninstalled updates for both Play Store (gapps) and Google Play Services and re-downloaded the updates. Have been fine for a while now.
My bluetooth has also been wonky. Used to connect to my car without issue but now I seemingly have to manually connect, or even reboot the phone to get it to connect. Wasn't having these issues on previous images...
Now that I've bltched, I really appreciate the work...and the changes are worth the few headaches! Thanks!

ClydeDroid said:
Yep!
Click to expand...
Click to collapse
Do you have any interest in adding CF Lumen to your image? When I download it, it has to install a driver and that must be something that is installed on /system b/c it never gets installed. However, I don't know if drivers are something that is too complicated to bake into an image.
http://forum.xda-developers.com/showthread.php?t=2711912
There is an unrooted mode but it doesn't work near as well as the rooted mode. With the rooted mode you can get the whites to be a very nice cool-toned white w/o any yellow/pink tinge.

JulesJam said:
Do you have any interest in adding CF Lumen to your image? When I download it, it has to install a driver and that must be something that is installed on /system b/c it never gets installed. However, I don't know if drivers are something that is too complicated to bake into an image.
http://forum.xda-developers.com/showthread.php?t=2711912
There is an unrooted mode but it doesn't work near as well as the rooted mode. With the rooted mode you can get the whites to be a very nice cool-toned white w/o any yellow/pink tinge.
Click to expand...
Click to collapse
Sure, I'll give it a shot!

tjohnstone3 said:
I've had the gapps issue as well, basically neutered the phone until I forced a restart. A reboot had fixed it temporarily but it came back again a couple of times. I eventually uninstalled updates for both Play Store (gapps) and Google Play Services and re-downloaded the updates. Have been fine for a while now.
My bluetooth has also been wonky. Used to connect to my car without issue but now I seemingly have to manually connect, or even reboot the phone to get it to connect. Wasn't having these issues on previous images...
Now that I've bltched, I really appreciate the work...and the changes are worth the few headaches! Thanks!
Click to expand...
Click to collapse
That's really strange. I've only experience the gapps freaking out once, but this is worrying. I might do some research to try to figure out what the problem could be.

ClydeDroid said:
That's really strange. I've only experience the gapps freaking out once, but this is worrying. I might do some research to try to figure out what the problem could be.
Click to expand...
Click to collapse
It's been 5 hours since I did the uninstall updates and reinstall them and I haven't had any issues since. So hopefully it's a thing of the past.
Though I haven't retested the bluetooth since this morning.

Install & run Android Marshmallow on the M7 - VanirAOSP ROM - UPDATED 4/24/16

There is a way to get Marshmallow on the HTC ONE Sprint M7, it's called VanirAOSP ROM. This is a great in most ways, and it's now my daily driver, but be very careful, I almost bricked my phone a few times in setting things up. Here are some tips from what I learned.
Installation instructions (learned from this video, other sources, and hard work):
1) Unlock bootloader.
2) Install custom recovery like TRWP. If you have an old version of TWRP, upgrade it using TRWP Manager or Flashify.
3) Download latest nightly ROM from http://www.emccann.net/nuclearmistake/VanirAOSPNightlies/m7spr/.
4) Download gapps. Biker57 suggests gapps from http://www.emccann.net/dho/5-Gapps/ as it's supposed to cause fewer force closes. I believe 60arm-DHO-GAPPs.zip is the correct file name.
5) Download SuperSU. Biker57 likes SuperSU v2.64 found here http://forum.xda-developers.com/showpost.php?p=64161125.
6) Copy all 3 downloads (in .zip format) to the phone (internal storage, like the TWRP folder)
7) Enter bootloader (volume down and power button), then select bootloader.
8) Backup the current ROM, just in case things go bad like they did for me.
9) From TWRP, enter advanced wipe and select system, data, cache, and dalvik cache. Do not select internal storage as you will lose your current backup and other zips if you do (there is an exception to this, as I did it, but I nearly bricked my phone). Now slide to wipe.
10) Go to install, and first select the ROM's zip. Then choose add more zips and select the gapps zip you downloaded. Next select SuperSU. Now slide to install.
11) Be patient during install.
12) Wipe dalvik cache.
13) Reboot to system (aka phone).
14) Enable Developer Options (if you want), by going to Settings->About and hitting Build Number many times until it's enabled.
Known issues and workarounds:
-Camera app force closes after taking a picture - the picture saves, so just reload Camera app. I've also had good luck using Z Camera then viewing the preview before hitting back to reenter the camera app.
-Stock dialer FCs randomly - Install another dialer app, like True Phone.
-Facebook and Facebook Messenger force closes - use mobile website, which actually isn't too bad, or try the instructions listed here.
-Flashlight turns off after 3 seconds - use the cameras flash instead.
Known issues with no good workarounds:
-FM Radio doesn't work.
-Bluetooth audio doesn't work for phone calls most of the time.
-Switching the battery mode causes the brightness to change randomly - don't ever switch away from balanced mode
Other stuff
-You can find more about the updates made to Vanir ROM here.
-It's risky to play around with the radio, but if you want to try it they are listed here.
-Intersted in supporting Varin, you can donate here.
Please let me know if I missed anything. And feel free to copy freely if it helps others.
***disclaimer - follow at your own risk. I'm not responsible for what might happen to your phone. This is only a cheat sheet, and it's for reference purposes only.***

First off, good tutorial. :good:
Vanir is a great ROM but this Sprint ROM still has a lot of bugs in it. I've used the first Vanir Marshmallow ROM to the most recent and a plethora of bugs have been squashed. But this ROM is still not DD ready, the camera , torch, gapps, browser and settings are broken. I am not saying this ROM is bad, just that its not fully ready yet. Depending on the dev, this rom should be DD ready in 2-3 weeks, they've been releasing more often now. Thank the developer if you know him but if you're the developer, thank you.
We should try to get the dev to see if they can put up a Vanir thread with change logs and the whole shebang.

I'm glad this thread was started and the OP was done well. I've been using this ROM for a while and thought I'd pass along my thoughts and what works for me.
This rom has become my daily driver after learning how to fix a couple of issues. After the latest update of 2/18 the biggest issues of not having a cellular/data connection has been corrected. The only issues that remain for me at least are the camera and Facebook issues. Although the camera does force close it does so for me at least after the picture is taken and saved so it's all good for me. The Facebook issues are corrected by deleting a file in both the Facebook and Messenger file.
The following method works for me without boot loops or any other issues and hopefully will work for you too. I flash these all at the same time loaded in the order listed and don't forget to make a backup before you start just in case.
1 - Flash the 2/18 nightly just like you would any rom http://www.emccann.net/nuclearmistak...ghtlies/m7spr/
2 - flash the gapps found here http://www.emccann.net/dho/5-Gapps/ and select the 60arm file near the bottom.
3 - flash Super SU 2.64 found here http://forum.xda-developers.com/showpost.php?p=64161125 There are new versions, but the 2.64 has continued to work for me.
4 - Reboot
As I said earlier this works for me and I've used this method with their roms successfully a number of times. Good Luck !!

Thank the developer if you know him but if you're the developer, thank you.
Click to expand...
Click to collapse
I'm not the developer, and I don't know the developer. But I would thank him or her if I could. I'm just interested in running Marshmallow on the M7. I will update the original post as I learn more so I can hopefully help others.

anotherfakeusername said:
I'm not the developer, and I don't know the developer. But I would thank him or her if I could. I'm just interested in running Marshmallow on the M7. I will update the original post as I learn more so I can hopefully help others.
Click to expand...
Click to collapse
If you need help with thread stuff I can help, we should start a new thread completely and give it more of a ROM thread look with known bugs, work a rounds and honest opinions on it.

biker57 said:
3 - flash Super SU 2.64 found here http://forum.xda-developers.com/showpost.php?p=64161125
Click to expand...
Click to collapse
Since my device is already rooted, would I be best off to install Super SU from the Play Store, then allow the app to upgrade through TWRP?

anotherfakeusername said:
Since my device is already rooted, would I be best off to install Super SU from the Play Store, then allow the app to upgrade through TWRP?
Click to expand...
Click to collapse
I'm not the developer either... Just a happy ROM user
There have been some issues with certain SU not working correctly with 6.0. You can try that but I would advise you to try a proven SU version.

is Snapchat also broken
Sent from my HTC One using Tapatalk

SuperSU 2.65 through TWRP 3.0.0-0
anotherfakeusername said:
Since my device is already rooted, would I be best off to install Super SU from the Play Store, then allow the app to upgrade through TWRP?
Click to expand...
Click to collapse
I didn't install it from the Play Store, I just flashed this version (2.65) through TWRP 3.0.0-0 and it's working as expected :good:

Hello,
Flashing SuperSU through recovery is a better way, atleast for Marshmallow ROMs now. I'm using latest beta version (SuperSU v2.67) without any issues. It can be found in official SuperSU thread here.
As of camera issues, you can use 3rd party camera apps like Camera FV-5, ProShot or etc. Of course they cost few bucks but worth it. Issue doesn't solve totally in this ROM but app doesn't force close, instead freezes for few sec and then works again.
This ROM is my DD and faced no major issues so far. What I'm mostly missing is fast charge feature in kernel otherwise normally it takes plenty of hours to fully charge.
Kindly note; you have to flash gapps provided by the ROM developer. Other gapps like open gapps will endup with FC.
Thanks...
Best Regards

CRACING said:
Kindly note; you have to flash gapps provided by the ROM developer. Other gapps like open gapps will endup with FC.
Click to expand...
Click to collapse
I flashed the gapps provided by the ROM developer, but the Gmail app is force closing due to "unknown issue with Google Play services.".
Then I tried using USB OTG to read my sd card reader in TWRP, but TWRP won't mount it. The issue started right after I booted the ROM the first time; I know because I installed the ROM from my sd card using USB OTG.
I still want this to be my daily driver, because the software is so much faster that 4.3, but I'm not convinced yet.

anotherfakeusername said:
I flashed the gapps provided by the ROM developer, but the Gmail app is force closing due to "unknown issue with Google Play services.".
Then I tried using USB OTG to read my sd card reader in TWRP, but TWRP won't mount it. The issue started right after I booted the ROM the first time; I know because I installed the ROM from my sd card using USB OTG.
I still want this to be my daily driver, because the software is so much faster that 4.3, but I'm not convinced yet.
Click to expand...
Click to collapse
Their list of gapps is rather long......which one did you use and did you flash it with the rom

You guys are right. I had to flash Super SU through TWRP (which was a challenge at first without using the sc card and OTG cable).

anotherfakeusername said:
You guys are right. I had to flash Super SU through TWRP (which was a challenge at first without using the sc card and OTG cable).
Click to expand...
Click to collapse
Correct, they have to be flashed with the rom as I mentioned in post 3.

anotherfakeusername said:
I flashed the gapps provided by the ROM developer, but the Gmail app is force closing due to "unknown issue with Google Play services.".
Then I tried using USB OTG to read my sd card reader in TWRP, but TWRP won't mount it. The issue started right after I booted the ROM the first time; I know because I installed the ROM from my sd card using USB OTG.
I still want this to be my daily driver, because the software is so much faster that 4.3, but I'm not convinced yet.
Click to expand...
Click to collapse
As of error "Unknown issue with Google Play service", go to Settings -> Apps -> Google Play service -> click 3 dot button in the corner -> Uninstall updates. This should solve the problem.
As of OTG, I didn't tested it but usb connection from TWRP to pc for file transfor works fine.
Btw; You are right, ROM is indeed fast.
biker57 said:
Their list of gapps is rather long......which one did you use and did you flash it with the rom
Click to expand...
Click to collapse
Use 60arm-DHO-GAPPs.zip
anotherfakeusername said:
You guys are right. I had to flash Super SU through TWRP (which was a challenge at first without using the sc card and OTG cable).
Click to expand...
Click to collapse
Even if you install supersu from playstore, it ask to reboots to recovery to install supersu. But before you accept to reboot, you'll have to enable root access to apps in developer options. Otherwise supersu cannot reboot or go into recovery.
Anyhow, instead of going through all these, I simply flash supersu zip from recovery.

CRACING said:
As of error "Unknown issue with Google Play service", go to Settings -> Apps -> Google Play service -> click 3 dot button in the corner -> Uninstall updates. This should solve the problem.
Click to expand...
Click to collapse
Android won't let me uninstall the Google Play service update. I get blocked when trying. It claims the app is an active device administrator, but it's not listed when I click manage device administrator.

anotherfakeusername said:
Android won't let me uninstall the Google Play service update. I get blocked when trying. It claims the app is an active device administrator, but it's not listed when I click manage device administrator.
Click to expand...
Click to collapse
Deselect Android Device Manager. Later when you uninstall the update, reselect Android Device Manager.

Deselect Android Device Manager. Later when you uninstall the update, reselect Android Device Manager.
Click to expand...
Click to collapse
That worked to fix my calendar syncing issues! Thanks!
Is not updating Google Play service going to cause other problems?

anotherfakeusername said:
That worked to fix my calendar syncing issues! Thanks!
Is not updating Google Play service going to cause other problems?
Click to expand...
Click to collapse
No such problems noticed here. I use Google calendar but Android calendar also works fine.
May be you should try rebooting or wait for some time and try resync.

CRACING said:
No such problems noticed here. I use Google calendar but Android calendar also works fine.
May be you should try rebooting or wait for some time and try resync.
Click to expand...
Click to collapse
The problem isn't using Google calendar, the problem is syncing Google calendar. I tried waiting, rebooting, re-adding my account, and everything else, but that didn't help.
Only downgrading Google Play services worked, and then Google calendar synced right away.
Thanks for the suggestions. Hopefully as they update the ROM it'll get resolved more fully.

Cannot install or update applications from the Play Store since upgrading to N

I enrolled on the beta program on my Nexus 6 and allowed it to update to Android N (June build) and now I cannot install anything from the Play Store or update applications through it. I get an error every time.
I have tried:
Turning it off and on.
Disabling Play Store and clearing the cache (cannot see anywhere to uninstall updates).
What should I try next? Should I try and uninstall the Play Store and reinstall it through apk?

Clear data of Google Play Services and Play Store then try installing/updating apps.

This did not work. It still just shows "Downloading" constantly and yet nothing happens. The bar just goes across endlessly til I stop it.

It is error code 495 if that helps, I will try Googling it now...

MC1987 said:
It is error code 495 if that helps, I will try Googling it now...
Click to expand...
Click to collapse
remove google account and add again then try..

Poojan Patel said:
Clear data of Google Play Services and Play Store then try installing/updating apps.
Click to expand...
Click to collapse
Poojan Patel said:
remove google account and add again then try..
Click to expand...
Click to collapse
It still has not worked. I also turned off the data saver built into Android 7 and also turned off Opera Max in case they were affecting it.
I really don't want to flash it but I might just wait until the final launch of Android 7 in August and flash it.

MC1987 said:
It still has not worked. I also turned off the data saver built into Android 7 and also turned off Opera Max in case they were affecting it.
I really don't want to flash it but I might just wait until the final launch of Android 7 in August and flash it.
Click to expand...
Click to collapse
I always do same as i mentioned above whenever i get play store problem..there may some problem with your wifi connection.

Poojan Patel said:
I always do same as i mentioned above whenever i get play store problem..there may some problem with your wifi connection.
Click to expand...
Click to collapse
I have tried both WIFI and 4G

And I can use the internet fine so it cannot be this.

MC1987 said:
And I can use the internet fine so it cannot be this.
Click to expand...
Click to collapse
install latest version of play store and google play service and try
or
take rom backup and try on different rom

MC1987 said:
It still has not worked. I also turned off the data saver built into Android 7 and also turned off Opera Max in case they were affecting it.
I really don't want to flash it but I might just wait until the final launch of Android 7 in August and flash it.
Click to expand...
Click to collapse
Max does not route Google Play requests through compression servers as it's HTTPS. Also we're testing if it works properly before each release .

zamber88 said:
Max does not route Google Play requests through compression servers as it's HTTPS. Also we're testing if it works properly before each release .
Click to expand...
Click to collapse
Well it didn't change anything anyway. I will fresh install final release of Android N in August and hope for the best.

MC1987 said:
Well it didn't change anything anyway. I will fresh install final release of Android N in August and hope for the best.
Click to expand...
Click to collapse
I have the same problem, but what I have found that works is: starting the download.. force stopping the play store app. Tap playstore app again, then download will finish. I have to do that every download. Keeps me from switching back to MM.

no clue why anyone wants N at this point; very few things actually work on it, and MM has so many fantastic roms/tweaks/features right now..
Its only another month or so until its officially out; especially if you are N00B, you should really wait until then

kwdan said:
I have the same problem, but what I have found that works is: starting the download.. force stopping the play store app. Tap playstore app again, then download will finish. I have to do that every download. Keeps me from switching back to MM.
Click to expand...
Click to collapse
Didn't work for me.

wase4711 said:
no clue why anyone wants N at this point; very few things actually work on it, and MM has so many fantastic roms/tweaks/features right now..
Its only another month or so until its officially out; especially if you are N00B, you should really wait until then
Click to expand...
Click to collapse
I got bored and didn't have access to a PC so I thought I'd try it. Surely access to the play store and the ability to install apps is one of the most basic and prioritised functions and given it's the 3rd Android N beta release I thought it would be fine.

MC1987 said:
I got bored and didn't have access to a PC so I thought I'd try it. Surely access to the play store and the ability to install apps is one of the most basic and prioritised functions and given it's the 3rd Android N beta release I thought it would be fine.
Click to expand...
Click to collapse
Actually DevPreviews have been what I would consider fine for me. Very few problems that would cause me to return to mm. 99% of the stuff I use works, so I'm good with it. I am encrypted and I manually flash different partitions when updating. I've had very few problems.

kwdan said:
Actually DevPreviews have been what I would consider fine for me. Very few problems that would cause me to return to mm. 99% of the stuff I use works, so I'm good with it. I am encrypted and I manually flash different partitions when updating. I've had very few problems.
Click to expand...
Click to collapse
Truth be told I don't know a great deal about Android yet. I can do some basic stuff that average phone owners can't like installing apks but I've never flashed anything. I'm not scared to try with a step by step guide though so I might try one later. I will see what version of CM is newest - does CM automatically update now? So when Android N is launched it will update? Or I'd have to flash it again?

Just restart the device and then try. Or force stop playstore and run it again. i'm using android N beta (NPD56N) since 7 days and i found no bugs yet! its working perfect on my nexus 6

MC1987 said:
Truth be told I don't know a great deal about Android yet. I can do some basic stuff that average phone owners can't like installing apks but I've never flashed anything. I'm not scared to try with a step by step guide though so I might try one later. I will see what version of CM is newest - does CM automatically update now? So when Android N is launched it will update? Or I'd have to flash it again?
Click to expand...
Click to collapse
I was the same way when I started with my Evo. I've come a long way since then( only less fear lol). I've learned a lot from searching first, then if I can't figure it out, there's someone on here willing to help. Trial and error is a great teacher. I don't use CM anymore. I use pureNexus.. When it comes out for N, I'm going back to it. Beanz is a great developer. Make a rom back up and start flashing.

[ROM] AOSP 8.1.0 for Sailfish

I successfully built 8.1.0 AOSP from source for Pixel (Sailfish).
This is my first ROM and there could be issues I'm not aware of.
Not Working:
Dialer keeps crashing when making or recieving phone calls
Working:
Camera and Flash
Speaker
Fingerprint sensor
LTE
Wi-Fi
Bluetooth
Auto brightness
If you encounter any other issues, please tell me and we can try to resolve them.
Requirements:
Unlocked bootloader
Newest fastboot installed and set up correctly
Stock 8.1.0 should be installed prior to flashing this
This will delete all your data, make backups of everything
Download:
https://drive.google.com/open?id=1vQRNRpSYQP2BrlCpzIpQpQNQrmlBYvTb
Installation:
Reboot your phone into bootloader
Open a terminal where the AOSP-sailfish-v1.zip is located
fastboot -w update AOSP-sailfish-v1.zip
I recommend installing F-Droid as gapps for 8.1 aren't available yet.
What I want to figure out now is why the dialer crashes when making calls and also how to make this TWRP flashable.
I also plan to update the ROM every month as new security patches become available, just like on the stock ROM.
If anyone wants to replicate the build, I just used the main 8.1.0 repo and the 8.1.0 driver images:
Code:
repo init -u https://android.googlesource.com/platform/manifest -b android-8.1.0_r1 --depth=0
https://developers.google.com/android/drivers#sailfishopm1.171019.011
Any testing and help would be greatly appreciated.
Thanks.

Great effort! Gonna try and flash it and then possibly help you debug the dialer problem.

I really want to flash this, but I cant be w/o a functional dialer. Can you try disabling the stock dialer and sideloading the dialer from the play store?

computercarl said:
I really want to flash this, but I cant be w/o a functional dialer. Can you try disabling the stock dialer and sideloading the dialer from the play store?
Click to expand...
Click to collapse
There's no Google apps available for 8.1 as far as I know, so no play store. I installed Dialer2 from F-Droid but it seems like third party apps can't replace the actual calling interface that pops up when you make or receive a call.
And I wouldn't install this on a device that you plan on relying on just yet. Wait a few days until the issues are fixed. As far as I can tell from my use these past couple hours, the only major issue is the dialer.

HeavyHDx said:
There's no Google apps available for 8.1 as far as I know, so no play store. I installed Dialer2 from F-Droid but it seems like third party apps can't replace the actual calling interface that pops up when you make or receive a call.
And I wouldn't install this on a device that you plan on relying on just yet. Wait a few days until the issues are fixed. As far as I can tell from my use these past couple hours, the only major issue is the dialer.
Click to expand...
Click to collapse
try https://www.apkmirror.com/apk/google-inc/google-phone/google-phone-14-0-176716531-release/ ? Sure it's not optimal, but, might get a functional dialer for the time being, until the real issue can be resolved.

It needs bunch of dependencies which cannot be installed this way. Eg Dialer framework
It appears though if this https://forum.xda-developers.com/android/apps-games/app-google-dialer-t3557412
works better. You do get few crashes, but only once, the second time you try same thing, it works.

Couple of questions:
1. When you say this will delete all data, do you mean that internal storage will also be wiped?
2. Is it rootable? And if so, any idea whether SuperSU or Magisk is needed?
Thanks.

just wondering, why would I want to use this over stock?

jmiller3342 said:
just wondering, why would I want to use this over stock?
Click to expand...
Click to collapse
No additional services running, no gapps prerolled in, bare minimum. Think of this as LineageOS 15.
My plans are to run it, install the smallest gapps I can to get gmail and calendar working, install Elemental X and Magisk to hide unlocked bootloader.
Fast and Lean.

pavanmaverick said:
Couple of questions:
1. When you say this will delete all data, do you mean that internal storage will also be wiped?
2. Is it rootable? And if so, any idea whether SuperSU or Magisk is needed?
Thanks.
Click to expand...
Click to collapse
1. Yes this will wipe everything. Back up all files that you want to keep.
2. I've tried SuperSU which fails at patching sepolicy and Magisk which results in a bootloop.

HeavyHDx said:
I've tried SuperSU which fails at patching sepolicy and Magisk which results in a bootloop.
Click to expand...
Click to collapse
Not sure which version you tested, but https://forum.xda-developers.com/pi...-12-5-2017-t3715120/post74749046#post74749046 talks about what ver seems to work on 8.1 stock.

HeavyHDx said:
1. Yes this will wipe everything. Back up all files that you want to keep.
2. I've tried SuperSU which fails at patching sepolicy and Magisk which results in a bootloop.
Click to expand...
Click to collapse
Ah, thanks for the update. Do you think it'll be okay if I use TWRP to wipe Cache, Data and System, and then install this ROM, but without the "-w" option? The internal storage shouldn't affect the ROM, right?

pavanmaverick said:
Ah, thanks for the update. Do you think it'll be okay if I use TWRP to wipe Cache, Data and System, and then install this ROM, but without the "-w" option? The internal storage shouldn't affect the ROM, right?
Click to expand...
Click to collapse
Yeah should work just fine. Just delete the userdata.img from the zip (there's basically nothing in there anyway)

Any plans of a Marlin release?

HeavyHDx said:
Yeah should work just fine. Just delete the userdata.img from the zip (there's basically nothing in there anyway)
Click to expand...
Click to collapse
All right! Gonna try it out over the weekend. Will report back...

AlexBrookes said:
Any plans of a Marlin release?
Click to expand...
Click to collapse
I can build and upload it real quick, but I wouldn't be able to test anything.

HeavyHDx said:
I can build and upload it real quick, but I wouldn't be able to test anything.
Click to expand...
Click to collapse
I'd be willing to test it. Thanks!

computercarl said:
No additional services running, no gapps prerolled in, bare minimum. Think of this as LineageOS 15.
My plans are to run it, install the smallest gapps I can to get gmail and calendar working, install Elemental X and Magisk to hide unlocked bootloader.
Fast and Lean.
Click to expand...
Click to collapse
oh cool . thanks brah

Have you guys tried going to the default apps section and setting Phone as the default dialer? Fixed it for a few other ROMs i've tried that ran AOSP bases for other devices, might be applicable here.
EDIT: No-go, wierd.

HeavyHDx said:
I successfully built 8.1.0 AOSP from source for Pixel (Sailfish).
I recommend installing F-Droid as gapps for 8.1 aren't available yet.
Thanks.
Click to expand...
Click to collapse
Gapps are kicking around now...
Check 'em from here ( https://forum.xda-developers.com/pi...os-15-1-pixel-xl-marlin-t3725985/post74976717 )