Related
minusculeShield 1.0
So after some time, I decided that the 4.3 update is worth doing slight modifications, even without the native Shield Services and PC Streaming able to be done remotely. I have gotten used to using Limelight anyways, so I decided to update my basic modified stock Shield ROM
First, I updated to the latest OTA 68, then went from there, the features are as follows:
- Two versions of the ROM, one with OTA and one without
- Includes a alternative Calculator (RealCalc), Zeam Launcher, Adblock, Xposed Framework (Along with an Xposed Module for adding a Play Store link to App info, and GravityBox for various system tweaks), MX Player, and ES File Explorer
- All but the most essential "system" apps are removed
- All "Gapps" are using Slimroms 4.3 Minimal Gapps
- Koush's Superuser/Superuser Binaries pre-installed
Same installation process as 0.5, excluding need to select Advanced Restore, you can restore like a normal Nandroid without specifying partitions
As always, make sure you wipe System, Data, Cache, and Dalvik before installing
If you have problems with the OTA-exempt version trying to OTA, if it prompts you, it will do it once, and once you "apply" the update (which it will never actually apply) the notification will go away
minusculeShield 0.5[Nandroid-Backup]
So, this is not really a ROM, but a Nandroid backup of my system without any partition but "/system."
This is almost as stripped down as the stock Shield ROM you can get. I have removed all but literally the most essential apps, and also removed the OTA functionality.
The idea for making this was that I couldn't stream remotely anymore since OTA 63, which I promptly set out to fix. I soon realized it was a problem with the Android side of things, as using it on 4.1.2 or 4.2.2 with their respective apps for that release seemed to work fine. OTA 63 (and 64, which is basically the same release, just for those who couldn't install 63) made the local streaming much less productive, as I immediately noticed lagspikes and a load of other problems, which I had never encountered before.
So, in a basic sense, this backup after installed, keeps the ability to stream remotely without troubles of performance or re-connection problems, uses a much more lightweight version of Gapps (Slimrom's version to be exact). It is based on agrabren's TweakerROM 1.1.0, which is a 4.2.2 base, and uses the original TegraZone Dashboard. It again removes OTA, so updating is not an option.
So, when you do install this backup, your internal "/sdcard" storage should no longer need the "nvidia" and "shield" folder, and you can delete those. They will most likely be recreated by some Shield services.
So on to installing and basic rundown in-case you past the above message and just want a bulleted list:
Installation:
Assumes the following:
1. Unlocked Bootloader
2. CWM installed
Installation procedure:
1. Download attached ZIP, extract to your internal SD card ("/sdcard") using the folder structure of "/sdcard/clockworkmod/backup/<extract contents of ZIP here>"
2. Boot into CWM and select backup and restore
3. Choose advanced restore
4. Choose minisculeShield, then "system"
5. Factory reset, wipe cache, data, and dalvik
6. Reboot and enjoy
Information on changes to original 4.2.2 ROM and other info:
- Removes OTA system
- Improves performance of streaming using original Dashboard, Shield Services, and Shield PC Streaming applications
- All but the most essential "system" apps are removed
- All "Gapps" are using Slimroms 4.2.2 Build 8 version
- Koush's Superuser/Superuser Binaries pre-installed
Download:
Version 0.5
Version 1.0 (OTA Enabled)
Version 1.0 (OTA Removed)
This is great. Will give this a shot today or tomorrow. Thanks!
themichael said:
This is great. Will give this a shot today or tomorrow. Thanks!
Click to expand...
Click to collapse
I'm glad, I thought people would be trampling each other to get a hold of some sort of fix to the remote streaming issue. I guess not. I know I was SUPER disappointed by the latest update for that exact reason.
Let me know if you have any problems, questions, or concerns. I am very new here, but I have been working with Android for almost as long as it came into existence. I started with Android 2.1, so I have learned a lot. I'm also a Unix (mainly the Linux variety) guy, so that goes hand in hand with Android.
I still get notification prompts for ota.
themichael said:
I still get notification prompts for ota.
Click to expand...
Click to collapse
This prompt is a one-time thing, if you attempt the install it will fail and never prompt again. I attribute this to a probably data not being cleared for the actual OTA I removed before doing the Nandroid, but I assure you, I have never gotten it again, and never had to install it past that. Basically, if you attempt the install, it will not restart, but rather just disappear, and even upon restart will just boot normally. Let me know if you've tried that what happens, as I still am using this Nandroid, and since I did indeed attempt (and fail) installing that OTA, it has never prompted again, and stayed where it was during Nandroid in terms of system apps and such
jarjarfinks said:
This prompt is a one-time thing, if you attempt the install it will fail and never prompt again. I attribute this to a probably data not being cleared for the actual OTA I removed before doing the Nandroid, but I assure you, I have never gotten it again, and never had to install it past that. Basically, if you attempt the install, it will not restart, but rather just disappear, and even upon restart will just boot normally. Let me know if you've tried that what happens, as I still am using this Nandroid, and since I did indeed attempt (and fail) installing that OTA, it has never prompted again, and stayed where it was during Nandroid in terms of system apps and such
Click to expand...
Click to collapse
Seemed to work. I'll let you know if anything changes.
same here , ive been on the evo 3d for a long time and learned alot , ill keep you posted as much as i can
milk070 said:
same here , ive been on the evo 3d for a long time and learned alot , ill keep you posted as much as i can
Click to expand...
Click to collapse
Is it me, or does the new GFE render the PC running it as "Busy" regardless of the version of the Android side? It was working prior to the GFE update 1.7.1.0, I just had to use the version of the PC Streaming, Dashboard, and Nvidia Shield Services apps in this Nandroid. It seems Nvidia has found a way to render it "Busy" the same problem I had before, no matter what ROM you use
Please test, and let me know, as I will have to find another way
Since I'm mostly a lurker and I rarely run into issues that someone hasn't already run into, I don't have the post count to post on the actual Dynamic 1.4 thread. But I'm a little stumped. I seem to have lost root, and when I run anything in SS I get multiple I/O errors referencing data/data/chainfire su files.
I came from knoxraid. Installed new safestrap. wiped. Installed 1.0 from SS then 1.4 from SS. Set up the phone. Restored apps. Set up my favorite xposed modules. All was good for a few hours then I noticed I didn't get a full screen call ID on a call. I went in to check xposed and all the modules were unchecked. I tried to install/update but it said xposed wasn't compatible with my version. So I uninstalled xposed and tried reinstalling. Now it errors on install with "Can't install, free up space and try again" I have plenty of space, but I noticed the last I/O error I get in SS refers to data/data/xposed something or other. So I did the whole wipe and start with 1.0 process over, but nothing changed. No root. And I don't know if the I/O errors are keeping SS from wiping system when it installs, so I'm wary about installing another rom just to see if it works. But I can still boot into SS.
So I'm not sure which direction to go from here.
The errors are:
E:error: I/O error
E:error opening '/data/data/eu.chainfire.supersu/logs'
E:error opening '/data/data/de.robv.android.xposed.installer'
" " " /data/data/eu.chainfire.supersu/requests
fix permissions didn't work. An extra error was "unable to chmod data/data/eu.chainfire.supersu/requests"
I can't access those files using file explorer in SS.
Well if anyone runs into a similar issue- I wasn't able to install any applications after that as well.
A wipe from stock recovery fixed it. Although it wiped a lot more than I had anticipated
Was the installation on the stock slot? That is where it needs to be. Get your post count up so you can join us!
bri315317 said:
Was the installation on the stock slot? That is where it needs to be. Get your post count up so you can join us!
Click to expand...
Click to collapse
Yeah I made sure to use stock slot. And everything was fine for a few hours. I really don't think it had anything to do with the rom. I'm leaning towards and install/enable/unistall/disable process that I was burning through on xposed, since the locked up files were su and xposed. And I had other apps downloading and installing in the background. I just gotta learn to slow down. Got everything set up today and it's running beautifully. I was on your Dynamic GPE for JB and it was my favorite. I gave the KK version of knoxraid a shot but got super excited when I saw SS had updated and I could go back to dynamic without odin.
It was fun now that it's fixed. I hadn't been into stock recovery since the old DX days. I didn't realize a data wipe from there took out just about everything on internal storage. Good thing I had the important stuff backed up.
I've been following your work for a while. And you sir, are fantastic. :good:
Q&A for [ROM][SlimKat][4.4.4] [unofficial]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Anghirrim said:
Finally tried the cast fixed version and still have boot loop. So back to version 8.
Sent from my GT-I9305 using XDA Free mobile app
Click to expand...
Click to collapse
I have the same problem with 8.4. With 8. everything works fine
IparryU said:
Cast version works perfectly fine.
Any chance you could include OmniSwitch in the next build @infrag? And possibally an option to use that as default recents? If not, no problemo!
Click to expand...
Click to collapse
Reposting here.
Proximity
Anyone else having problems with their proximity sensor?
updated modern, still getting invalid mmi
I was getting loads of chinese text through with the ussd/mmi system like trubul here, infact I made a thread about it. And also the loss of ussd code functionality with "invalid mmi code" error that he described.
Azlanhu says:
"had the same problem. Apparently, u need to flash the new modem/baseband I9305XXUFNI3 . "
Trubul seems satisfied with the solution, however when I flash the modem linked, whilst it sorts out the Chinese text, I still get invalid mmi codes all the time.
Am I missing something? Is a baseband something separate I need to flash, and if so where can I find it. Or something else?
Cheers.
I9305 (d2lte) SlimKat
I would like to know is it possible to install in Germany the SlimKat D2LTE version, or it may thereby lead to problems?
SlimKat vs SlimSaber
I know that Slim Saber Saber with the mod has been created, but I do not see quite the difference, so I would like to know your opinion of what you think are friendly for BATTERY?
Google Play No connection issue
My i9300 is stuck in a no connection issue in all the gapps, tried everything, clearing cache, data and even hard resetting
I have a rooted Slimkat 4.4.4 build8.0, stock Slimkat's kernel
Sorry for my bad english
SlimKat 4.4.4 8.6 Camera issue
Really nice rom - well done! The only issue I found so far on i9305 is that the camera does not work - it crashes when trying to access it. Even installed Camera MX but that freezes the phone completely on a black screen and a restart is required. I've noticed others were having the same issue. Are there any fixes for this?
Anghirrim said:
Hi, camera used to be fixed by just going back into CWM and wipping cache + dalvik cache. It used to work for me.
For the DPI, did you activate the root in the security option. I think you need it.
Sent from my GT-I9305 using XDA Free mobile app
Click to expand...
Click to collapse
I have the exact same issue with my camera. It was working before V8.6 but now I can't seem to fix it anymore.
No wiping of cache, even clean install (with format of /system) didn't do any good.
I also tried to extract various camera2.apk packages from older versions but I always run into the same problem
when starting up the stock camera app (other camera apps result in a freeze of the entire phone).
Unfortunately this time this does not solve my camera issue, and I assume it's the same for the others here. I even tried to replace the camera2.apk with various apks from older releases but it didn't help either. And if I try different camera software (apps) the systems just freezes completely. Any ideas?
TheDesperadoz said:
Unfortunately this time this does not solve my camera issue, and I assume it's the same for the others here. I even tried to replace the camera2.apk with various apks from older releases but it didn't help either. And if I try different camera software (apps) the systems just freezes completely. Any ideas?
Click to expand...
Click to collapse
Install CMFix from the Play Store, read the Important Instructions on the app's Play Store page & click the link to download Temasek's Restart Camera app. Do not open CMFix - first install Temasek's app & grant it SuperSU root permission. Then place a shortcut to Camera CMFix on your home screen instead of the link to the 'normal' camera. It's worked for me on all SlimKat & SlimSaber versions & with CM11.
woww thanks you
Is there a way to return to the AOSP recent apps window? The only thing I don't like on this rom is the recent apps window and how it looks and also the fact that there's a gesture instead of a clear recent apps button
Sent from my GT-I9305 using Tapatalk
nielowen said:
Install CMFix from the Play Store, read the Important Instructions on the app's Play Store page & click the link to download Temasek's Restart Camera app. Do not open CMFix - first install Temasek's app & grant it SuperSU root permission. Then place a shortcut to Camera CMFix on your home screen instead of the link to the 'normal' camera. It's worked for me on all SlimKat & SlimSaber versions & with CM11.
Click to expand...
Click to collapse
Thanks for the support. I already tried this twice though (and yes I followed the instructions to the letter) but I get the same annoying "unfortunately camera has stopped"
popping up when I then start the CMfix app.
I'm just not sure if this is a ROM issue or if this might be due to a conflict between my apps. Maybe I will try a clean wipe, of cache and system, then reboot into ROM
and see if the camera will work or not. This should tell me if it's ROM related or not.
I hate to restore everything afterwards though and to return to the issue for further investigation
I'd be glad to hear if someone else found an alternative solution!
Have you enabled root access? I would re-install the ROM having formatted system & cache & wiped dalvik and only then tried a complete wipe if that didn't work.
Finally got the camera working again
nielowen said:
Have you enabled root access? I would re-install the ROM having formatted system & cache & wiped dalvik and only then tried a complete wipe if that didn't work.
Click to expand...
Click to collapse
Yes I have, that was not the problem though I finally got it to work again, here's what I did (in case anyone runs into the same issue):
1.) Install CMFix from the Play Store + download & install Temasek Restart Camera (with root permission)
2.) Run camera CMFix --> still got the "can't connect to camera" error message
3.) Reboot to recovery, wiped dalvik, wipe cache partition & wipe data/factory reset
4.) Restored apps & system data via Titanium
5.) Run "Restart Camera" and CMFix again --> This time the camera did work again :good:
6.) Tried other camera apps --> camera is working just fine now --> uninstall Restart Camera & CmFix --> camera is still working
Also one could try installing a different GAPPS build - there is a stable one from mid September and various betas up to a day ago,
maybe that might be another cure (or cause) to fix the camera bug.
Slim install failed
hi people who can not install Slim, brings in TWRP 2.7 Failed with what have for a recovery flashed her. sorry for my english
https://drive.google.com/file/d/0B4k...ew?usp=sharing
TheDesperadoz said:
Yes I have, that was not the problem though I finally got it to work again, here's what I did (in case anyone runs into the same issue):
1.) Install CMFix from the Play Store + download & install Temasek Restart Camera (with root permission)
2.) Run camera CMFix --> still got the "can't connect to camera" error message
3.) Reboot to recovery, wiped dalvik, wipe cache partition & wipe data/factory reset
4.) Restored apps & system data via Titanium
5.) Run "Restart Camera" and CMFix again --> This time the camera did work again :good:
6.) Tried other camera apps --> camera is working just fine now --> uninstall Restart Camera & CmFix --> camera is still working
Click to expand...
Click to collapse
Hey! Tried this and the other mentioned stuff several times but still no success... has anyone heard from other ways to get the cam to work? or maybe an alteration of the quoted post?
So here is the issue.... I have a droid turbo running Resurrection Remix. I used the aroma installer to slim down the gapps installed and maximize space. All of my apps install just fine except, a game Clash of lords 2. Also i have noticed that in my outlook app i can't press on hyperlinks from emails. Any thoughts?
Im having a hell of a time with random parse errors, permission errors on apps... Narrowed my issue down to cm root option and SU not getting along, happend after flashing beta SuperSU, fixing to full wipe and test drive latest CM 13, I've yet to recover 4G and also my GPS locks when I'm sitting still, but if I travel it gets lost....
DESCRIPTION
If you have the Pixel Experience module installed on your phone and installed Google Phone from the Play Store or ever tried to use a patched Google Phone version (such as this one), you may have noticed that Google Phone force closes when you try to search for a contact or while opening the keypad. This Magisk module attempts to fix that and it works by replacing your non-AOSP contacts storage with Google's own version, the one supported by Google Phone.
IMPORTANT NOTES
Supports Android versions from Android 7 (Nougat) to Android P.
It will remove any phone/dialer/contacts/people applications from your phone (if supported) because they are incompatible with Google's Contacts Storage.
You should only install this module if you want/need to use Google Phone and Google Contacts.
TESTED/SUPPORTED DEVICES
HTC 10 (Sense based ROMs).
Note: It should work with other devices but I have no means no test them myself, I can only rely on the community to test this for me.
SPECIAL INSTRUCTIONS
Install the Magisk module as usual but DO NOT reboot your device just yet.
Go into "Settings » Accounts & Sync" and disable "Automatically sync data".
Go into "Settings » Apps" a, look for "Contacts Storage" (it's a system app) and clear application data.
Reboot your device now!
Go into "Settings » Accounts & Sync" and enable "Automatically sync data".
Google Phone should now work without force closing, hopefully.
Note: If you ever want/need to disable this module, you should also follow the procedure above (disable module, disable data synchronization, clear contacts storage data, reboot, and re-enable contacts synchronization).
DISCLAIMER
Install this module at your own risk.
Developer is not responsible for what you do on your device.
Please take all necessary precautions (like a nandroid backup) before installing this module.
DOWNLOADS
Google-Contacts-Storage-v0.0.0-TESTING.4.zip
XDA:DevDB Information
Google Contacts Storage, Tool/Utility for the XDA Community Apps
Contributors
rfgamaral
Version Information
Status: Testing
Current Beta Version: v0.0.0-TESTING.4
Beta Release Date: 2018-08-02
Created 2018-08-01
Last Updated 2018-08-02
@rfgamaral after installing magisk module and rebooting i keep getting android.process.acore has stopped.
I cannot get rid of it. By pressing ok all the time i managed to arrive to Apps but there is no Contact Storage app to clear data/cache after the reboot.
stathis95194 said:
@rfgamaral after installing magisk module and rebooting i keep getting android.process.acore has stopped.
I cannot get rid of it. By pressing ok all the time i managed to arrive to Apps but there is no Contact Storage app to clear data/cache after the reboot.
Click to expand...
Click to collapse
I also got that error when developing this module but I never got it after installing/enabling it, only after disabling it.
For some reason, the system does not recognize the /system/priv-app/ContactsProvider/ContactsProvider.apk (although the file is there). I'm not sure how to fix this to be honest, so I recommend you restore your backup to get you back to a working state. Maybe try the whole process again (makre sure you follow every single step) and instead of rebooting the system after installing the module, reboot to recovery and wipe dalvik/ART and cache. If that doesn't help, restore the device again until a solution for this problem is found.
Like I said, I also had this problem and because I live on the edge, I didn't make a backup of my system (idiot me). I had to make the system recognize the ContactsProvider.apk file and wen into recovery, deleted, copied it back from my ROM, set proper folder/file permissions, wiped dalvik/ART and cache and rebooted, the problem was gone. I installed my module again and it worked. But I'm honestly afraid to disable it and get that error back.
Which is weird because I'm replacing this file systemlessly, that's the whole point of Magisk. Maybe I'm doing something wrong, I'm no expert... We'll probably need help from someone with more knowledge on the whole Android system. But for the record, I currently have the version available on this thread installed on my phone. I have the Pixel Experience module installed and installed Google Phone from the store, it doesn't force close and all features seem to be working. I just need to get this module stable.
@stathis95194 Were you able to restore your device? I hope so... I've uploaded a new test version, didn't change much, not sure if it fixes anything.
rfgamaral said:
@stathis95194 Were you able to restore your device? I hope so... I've uploaded a new test version, didn't change much, not sure if it fixes anything.
Click to expand...
Click to collapse
Yeap I always take a nandroid before messing with the phone. Let me try the new version and report
Sent from my HTC 10 using Tapatalk
@rfgamaral soooo after flashing 0.0.4 i faced the same issue with android.process.acore has stopped popping all the time.
This time i took a different approach and didn't restore my nandroid. Instead i dirty flashed my LeeDroid rom.
Rebooted and lo and behold, stock dialer and contacts were missing and google phone was working perfectly. No crashing on searching (nearby places is working)
Now i need to test caller id and spam filter
I will keep testing and let you know.
stathis95194 said:
@rfgamaral soooo after flashing 0.0.4 i faced the same issue with android.process.acore has stopped popping all the time.
This time i took a different approach and didn't restore my nandroid. Instead i dirty flashed my LeeDroid rom.
Rebooted and lo and behold, stock dialer and contacts were missing and google phone was working perfectly. No crashing on searching (nearby places is working)
Now i need to test caller id and spam filter
I will keep testing and let you know.
Click to expand...
Click to collapse
Awesome, glad you got it working.
Now I just need to understand why installing this module crashes android.process.acore... But it's a bummer that this is happening, a little price to pay, I guess? At least until a fix is found... That and that whole install procedure which is required to avoid other different crashes because of incompatible storages.
Hi
I'm running 2.42.400.3 on U11.
I installed this and google phone from
https://forum.xda-developers.com/android/apps-games/app-google-phone-v14-0-175904292-bubble-t3708218
Dialer kept crashing so I installed your mod.
After that,com.android .phone keeps crashing.
I unistalled it and then I got acore crashing.
I restored feom nandroid but for some reason kept getting the acore crash, so I completely uninstalled magisk.
Now.... everything works. Even the dialer.
I'm really not sure what happened but.... thanks
gunnerhk said:
Hi
I'm running 2.42.400.3 on U11.
I installed this and google phone from
https://forum.xda-developers.com/android/apps-games/app-google-phone-v14-0-175904292-bubble-t3708218
Dialer kept crashing so I installed your mod.
After that,com.android .phone keeps crashing.
I unistalled it and then I got acore crashing.
I restored feom nandroid but for some reason kept getting the acore crash, so I completely uninstalled magisk.
Now.... everything works. Even the dialer.
I'm really not sure what happened but.... thanks
Click to expand...
Click to collapse
That's really weird, on so many levels... :/
Screenshot as proof :laugh: