I had a similar issue when I flashed the new 3.1.1.1 zip from fastboot booted 3.1.1.1 over the October release with a custom kernel. I had to simply reflash my kernel to boot into android, and this did not wipe away the flashed TWRP. This non-booting should not happen if you were on the stock...
I'd suggest that if you can get your head around the gapps-config concept, you do that method rather than using an apk you extracted, as it is a solution that will propogate automatically when you update or clean flash (assuming the gapps-config file is still present in the location of the gapps...
Using the standard Nexus adapter I got with the phone, I get a maximum of 1100mA as per the "Ampere" app. Over USB with fastcharge turned on in FkU, I get a maximum of 600mA from a USB3.0 port on my Dell laptop. But it would depend on the source and possibly the cable too. Old cables in my...
Good news is that the google setup process does receive the 2fa code via SMS even without an SMS app, so that's not an issue.
But to install the app from TWRP, I'd recommend copying the apk to the /system partition since you already have the apk on your sdcard.
1. In TWRP make sure system is...
Sure, now that I know Slim7 doesn't have an SMS app in /system, I will be doing just that. And hopefully others who have read this conversation here. But since receiving SMSes is one of the primary uses of the phone, it's a cleaner solution if the software ensures such a loss of service doesn't...
Yeah I agree, I haven't used the aosp/default one ever since Google put theirs in the play store.
But the issue I had was that my carrier sends me SMS alerts about missed calls when my phone is turned off or not available, Eg when I'm flashing a new rom (with my twrp backups taking close to an...
I finally got around to wiping my phone and switching to slim7. Flashed beta 0.9 with the 20170202 opengapps micro, and looks like there is no SMS messaging app installed in /system. Is this likely a gapps error, where it wiped out the app while flashing itself, or is it not included in slim7...
"Works as intended", you could say ;)
http://www.androidpolice.com/2016/10/20/android-7-1-feature-spotlight-rotating-screen-navigation-bar-doesnt-move/
When you get the time for it, I believe Santhosh M has resolved that video recording issue in his AOSP ROM for our device.
You can find his device & kernel repo at:
https://github.com/sandymanu/device_nougathammer
https://github.com/sandymanu/hammerhead_nkernel
So after upgrading from 1.6 to 1.9, I realised it's quite easy to press the battery icon on the quick settings pulldown now. Earlier I would frequently end up launching Settings instead. Haven't had time to roll back and check what changed between the two builds, but I may do so if I find some...
Hey Yank! Hope you're doing well :)
I'm currently on weekly 1.6, need to find the time to backup and update to 1.7 sometime. (Or is it 1.8 already?)
Anyway I noticed it's a little difficult to accurately press the battery icon in the quick settings shade, the target is quite small and very...
Shameless post to claim post number 40000.
Anyway thanks franciscofranco for your work on the N5. I'm still holding onto mine for another 4-6 months at the least as my primary device. Will then use it exclusively as a pen-testing device :)
In that case it always pays off to wait for more experienced or less risk-averse people to try stuff out with that device. They would then test stuff out, figure out, and share solid info and instructions for the rest of xda to safely follow :)
Wow, whoever sold it to you should have restored to stock at least before handing it over. Now this thread is for the Nexus 5, but let's see. First go to contacts.google.com (and sign into your google account) on a computer and check if your contacts are over there. If they are, all you need to...
Hey since you are the DM for hh, thought I'd share an observation with you. Now this happens in both Google's stock MM and in your YAOSP builds. I have setup a secondary user on my hh to use some apps with a multiple profiles. When I switch from one user to another, WiFi and mobile data both...
Yeah lots of things can influence the compatibility of various apps on the play store, including DPI, sometimes the ROM you use, your current location (via the reported network/carrier), any funny changes the company listing the app makes in their play store dashboard, and the random...
Found some info on the interwebs about this problem. Looks like the problem isn't in either the ROM or the gapps, it's Google's fault ;) (probably)
https://www.reddit.com/r/androidapps/comments/4897ke/google_camera_app_disappeared_from_play_store/
I uninstalled the sideloaded one from...
Hey Yank555!
So I just switched to yaosp after a long time on stock (Since Marshmallow first came out), feels good to be back!
There seems to be one issue on hammerhead though, that is google camera is reported as incompatible on play store with opengapps (micro) and on slimgapps (mini)...
skvalex would like to report that recording works fine on the Moto G 2014 Dual Sim (XT1068) running Marshmallow, but not using the default settings it sets up. Changing the preset from 'Other' to 'Qualcomm MSM8226' and switching from 'Standard API' to 'CAF' is required to record both parties...
I have a Nexus 5 running stock Marshmallow, with Jit setup and running perfectly in the primary user. I have a secondary user setup too, for which calls and messages disabled. I can still answer any calls I receive while using the secondary one however. (I use it essentially to access my second...
As far as I know you are right in that the N5 doesn't have (or doesn't use?) a low power sensor core/cluster in the SD800. The DT2W issue however is unrelated, that issue is because of how the display/touchscreen power connections are wired up. ie they are powered together, not separately.
You can't push directly to /system. Push files to either /tmp or /sdcard and then run 'adb shell', su, mount system as rw, then move them over to the right place.
The easiest/cleanest would be to flash an sbf back to moto stock, root, install 2ndinit recovery, flash 2.6.3.0 recovery, then flash slim. Also you'd have to repartition your sdcard back to regular I suppose.
Good to hear :)
Me personally, I'm on Quarx's CM11 builds now. I think I'm running something from exactly a month ago. I'm using my handset only for music though, without a SIM card. Have logged into Google services to install my (paid for) music app and a few other random apps.
Why am I not...
I don't have experience with either the android-x86 project or x86 phones and the requisite x86 xposed, but I do have a suggestion for the recovery bit.
Since its a PC, you can just USB live boot your favourite flavour of Linux, mount the partition where android-x86 is installed, and manually...
I imagine it will be messy, since storing the actual length may be 'insecure' and because Play Services hooks into the code as well for Smart Lock etc.
Yep that's what I had meant when I said one needs to fully unroot the ROM first. I haven't tried any custom ROMs based on 6.0/x yet, so wasn't aware of the unSu.zip :)
I'll keep a copy of that zip for when I do flash slim6 when yank gets around to it :p
You can get the gapps package to place it in /data, just like you are doing manually now. That way no need to look for the en-gb version in the format that's placed on /system.
Well when you are wearing headphones, the only time the device would have to swap the channels is if your ears somehow swap positions and your phone somehow detects that (ungodly) swap :p
Reliability and functionality is the same as system based ones, it's just simpler to root using systemless on 6.0+ Stock, because using the system based one would still necessitate modifying boot image, that too manually (probably, I haven't seen any automated scripts for it). So might as well...
Systemless just modifies the boot image, so it shouldn't need anything special since it's designed to modify the stock boot images. That's assuming none of your kernel additions hamper that process :P
One would just have to fully unroot the ROM first I think.
Here's the thing though. The problem with dirty installs come if the code change has been significant and specifically affects something stored in /data, for example, changes to the structure of a database holding some data or setting. Typically when making such changes, the dev should code...
I can't agree with this hard enough. My original Nexus cable is in bad shape, but just the outer black sheath has torn. The inner wires, and the plugs are fine. I decided to buy a new cable anyway, and I've tried at least 5 of them so far. None of the generic ones (at least the ones available in...
Just FYI, the SuperSU 2.62-3 on MM 6.0.1 on my hammerhead with ElementalX 6.07 works just fine with Secure Settings and such apps with hardcoded paths to the su binary in /system. So one can also be on the latest SuperSU and ElementalX ;)
http://forum.xda-developers.com/xposed/xposed-android-4-4-4-t3249895
Use the solution on Page 62. That works for me on the 4th Dec nightly. Haven't bothered updating beyond that nightly, since I only use this device for music. Xposed is for the music app that sounds like pottify ;)
Oh right, I should have specified what happens if he accepts the OTA. It will download the entire huge file, fail to flash, and proceed to redownload and fail again. This repeats until it has sucked up all his data limit (if any). Happened to a friend of mine on SlimKat for mako when Lollipop...
Don't even think about accepting that OTA update :P
Typically OTA update mechanisms are disabled on custom ROMs, but sometimes it sneaks in anyway. Through Google Play Services I suspect. If you want and you are capable, you can snoop around the services available in that app and disable the...
That order is correct. Would be most convenient to flash the bootloader and radio images together, don't you think? Flash bootloader, do a 'fastboot reboot-bootloader', and flash the radio image.
You should not dirty flash. Wipe data, system, and cache. In fact, the 'best' way to upgrade is to...
Definitely official. Was never disbanded, just went on a semi-vacation so they could revamp the backend, including forming an official company for Slim.
This is just a new thread as the old one was getting quite long, and the OP wasn't around anymore. Yank555 is the maintainer now, and he has...
What shaggy said. Was knocked out cold for 10 hours, and was groggy for the next two @[email protected]
That period did coincide with night time, but I'm sure that wasn't it [emoji14]
Sent from my Nexus 5 using Tapatalk