Search results

If you want a stable system then leave it as it is. If you want to experiment then do it but leave the idea behind that you are "optimizing" the system on this experience level.

I also never noticed reboots on this ROM (except the IPv6 crashes in previous builds). AndDiSa Do you know why com.android.quicksearchbox appeared after last update? I'm not sure whether I had disabled it or it wasn't there before but other system apps are still disabled.

You can install MatLog and use ADB to grant log access once.

Use TWRP to backup current working stock 5.1.1 image :good: Copy zip across to N7 using fast disk similar to when copying twrp over You can just copy files over USB as usual when in TWRP, don't forget to also copy md5 files over so that TWRP can check integrity TWRP Clean Wipe? :good: factory...

I just downloaded both builds at full speed from US mirrors, EU mirrors were too slow, though.

False positive: Android.Trojan.Ransom.gTGSI WallpaperPicker.apk 13 / 60 Ad-Aware Android.Trojan.Ransom.gTGSI 20180820 Arcabit Android.Trojan.Ransom.gTGSI 20180820 BitDefender Android.Trojan.Ransom.gTGSI 20180820 CAT-QuickHeal Android.Ransom.Ab434 (PUP) 20180819 Emsisoft...

Can confirm, it's fixed and I'm glad about having the latest security updates again! It's quite impressive when you think about it since the Nexus 7 is almost 6 years old. So thank you and OlliWi for your effort and persistence! :good: :good:

Just follow the instructions in the first post step by step. Here are the details for flashing the ROM (but they are almost the same for all ROMs): Install 7.1.2 Tilapia OTA-Package (Build 20180618) (md5: 873243650fe4a93a97b85486abf84cfc) Download aosp_tilapia-7.1.2-ota-eng-20180618.ds.zip and...

First log was created with the newest build after enabling Wi-Fi. It doesn't crash immediately or every time, often it takes several minutes while it tries to connect and little x on Wi-Fi icon indicates no internet access. I hope the log contains some useful bits before the soft reboot. Second...

SHA-256 F30C07781F6FD7597634DE92E13F9942E99165DFF85766CFDE3A453388C71080 SHA3-512 (for extra safety) 0041192271674264F153EEDB81E8031CDF466FD5D6761C3DB856FE603E3B60B54057744AF71B99E20016D342EC50BB19C8D87DEFC0918C59F2222F82DBA04D59 Superficial knowledge is also completely unsafe! How do we know...

Just tried newest build on Grouper, works fine while offline but crashes when it connects to Wi-Fi :( IPv6 is still an issue so I restored the backup again (January build). Is there anything we can do to help finding the troublesome changes since then or do you have an idea what the problem...

Plans for using search?

Just a reminder that you can disable cellular data access for any streaming app to prevent excessive data usage.

Installed the ZDF app and let it stream for a while, connection was stable all the time. I can't remember any disconnects while streaming with YouTube, Netflix or Spotify with both peregrine devices. It sounds like a network issue to me. Does it happen on all WiFi networks with other routers?

Standalone: Brave Opera Firefox (with uBlock Origin or AdGuard) WebView: Privacy Browser Atlas Web Browser Via Browser

Yes, since early 2017. It's pretty much mandatory when using apps like WhatsApp that won't you let set storage to SD card.

https://code.google.com/archive/p/android-developer-preview/issues/2982 This might be off topic, will switch to PM.

Which patcher did you refer to and how to repatch? That's exactly what I always did but apparently it causes the card ejection for me and I don't get why. How can cache clearing be even disadvantageous? I will try to clear caches on next update again and see if it is reproducible. Not sure if...

Updated to latest nightly but SD card got removed again after a few minutes on startup. Restored backups and and tried something different many times, was about to give up and go back to the November build but the last attempt turned out successful. It seems that NOT wiping Dalvik/Cache after...

Wiped phone yesterday and installed latest build without issues. I would try again: 1) Reboot to RECOVERY after LOS / before GApps 2) GApps pico (ARM 7.1) 3) Without GApps

TWRP 3.2.1 available: * minui fixes (cryptomilk) * Better android-8.0 compatibility in ROM trees (Dees_Troy) * Fix missing library in android-8.0 (nkk71) * Fix inconsistent SDCard naming (DevUt) * Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)...

The new and also the previous build are much better regarding smoothness and battery life. Had quite heavy lags as many users reported with earlier versions, will see how it runs with full memory/swap after some days uptime. It's a joy to use the tablet again, your effort is greatly appreciated!

I don't think that it's a portable/internal storage issue. What about other file managers like FX or Amaze? Same problem? At least GC seems to have issues with SAF migration: https://sourceforge.net/p/ghostcommander/bugs/42/ Did you restore app data from a backup...

Thanks for checking! Did you try to format the cards from Storage settings (format as internal then portable again)? Are you sure that these apps have storage permissions? You probably need to force stop and restart them.

I had the same problem while restoring with 3.2.0 but it finally worked for me after I tried several times. I guess the workaround was probably to create a minimal backup first or clearing "mount system as read only". Restored backup twice successfully after trying the December builds so I kept...

Can you test if 20171124 behaves differently?

Additionally you could let MatLog record the main/radio/events buffers to file (every 20-50 lines) and if you get lucky find out what's going on BEFORE it crashes.

The logs aren't really helpful, I found no crashes/errors/exceptions. 20171124 is stable on my device so I guess it has to be something else. If the reboots occur quite often I would start clean (without root) again for a day and see after which successive change (settings/apps) it gets...

No Wi-Fi connection issues here (SELinux enforcing). Updated TWRP to 3.2.0 and installed 20171201 but SD card (internal storage) was ejected after a few minutes on every reboot. Restored backup (20171124) for now but will try it again and look into the logs. Anyone else with similar problems...

I could not reproduce it and was wondering until I remembered that I disabled some system apps like Calendar, Contacts, ..., Phone and replaced them with their Google counterparts from Play Store. I guess it's the reason why the LED notification works after restart. Tested again with stock...

There are some system apps that can be disabled safely but in general it's not intended in first place. Blocked Number Storage can also be disabled on a pure AOSP system so it's not really an issue related to LOS. Your LED notification probably also doesn't work because of disabled system apps...

1) Phone notification works for me as any other LED notification, it blinks after a missed call. 2) Correct me if I'm wrong but why do you see malfunctions after disabling system apps as bugs?

Just updated to yesterday's build without issues. Made backup to USB-OTG and installed zip files from there. VLC plays video from USB just fine. So far SIM also works, calls and data connection as before.

It happened to me on different devices with lower quality cards and it didn't occur every time so you could say it is common. The whole process seems to be quite fault intolerant and has no proper error handling.

U1 or U3 model? U1 might be too slow for internal storage. You could also check it with H2testw for errors and average write/read speed in empty state.

I'm using 16/32 GB (U3) cards as internal storage, crashes are very rare. The first card (U1) on the other hand caused many troubles even as portable storage when I used HERE Maps with offline maps. Data got corrupted and the phone rebooted. H2testw found no errors on both occasions. Card speed...

Could you be more specific about the Samsung card (C10/U1/U3/...)? Did the phone reboot without moving apps?

This is not the support thread for Link2SD. It isn't needed anyway, last used it in 2014.

I can't see anything wrong here but my debugging experience is limited, though. This summary could be helpful if you want to dig further. Other people also reported reboots but they are quite rare (0-2 times a week for me) so I think that your problem is not directly related to this ROM. I...

Try to reboot to RECOVERY before installing GApps. Never had a problem with OGApps pico package that way.

This might be useful (and even better):

As ITm said it's unlikely related to the ROM since there is a firmware layer between the hardware and OS: https://android.stackexchange.com/questions/70/what-is-radio-firmware Are you sure that the SIM is broken and not the device hardware? Did you test other cards/phones?

You are right, the button does nothing: I tried LOS and Google camera. You should open a ticket and probably someone can tell us what the system lacks.

In the meantime you could use a proper player like VLC or PowerAmp, no problems with FLAC files.

You could do a full backup and a clean flash (wipe data, not storage) without GApps and see if it makes any difference.

Besides Logcat you could look into /proc/last_kmsg (requires root). If you don't have root access but platform tools: adb shell cat /proc/last_kmsg

Did you even try it? You don't need to format the card, it probably works with both modes. I wonder why you want to move apps if the card is almost full anyways. The option is already there, what exactly do you want to be implemented?

At the bottom of Developer options, works for me. Formatted the SD card as internal storage, I'm not sure if portable storage also works. But you will need a fast card for responsive usage.

I also noticed a slightly slower performance on the last September build but only temporarily. You could try to change some Apps settings in the Developer options and see if it makes any difference. My phone crashed again after 9 days uptime, screen was off while hiking. But in general the build...

Updated to 20170921, security patches are included and BlueBorne Scanner reports that the device is not vulnerable anymore. Had no issues or crashes with 20170914 in the past week.