Related
I am starting this thread so all issues related to SlimKat Rom can be documented in one single place. Please post your Questions & Answers in here instead of in the SlimKat Rom Thread, lets try and keep that thread clean.
SlimKat ROM Thread: http://forum.xda-developers.com/showthread.php?t=2511512
All Credit goes to the developers, Please support them for continued development
I will try my best to keep the thread updated and have questions and solutions posted in the first three posts of this Thread:
How to Install SlimKat ROM
Assuming you have already rooted, unlocked boot loader and installed custom recovery. If not there are multitude guides to do so, search in the forum.
Step 1:
Download the following:
Current SlimKat ROM: http://slimroms.net/index.php/downloads/dlsearch/viewcategory/979-hammerhead
Note SlimKat Rom is in beta currently
Current SlimGapps: http://slimroms.net/index.php/downloads/dlsearch/viewcategory/978-addons4-4/downloads/dlsearch
Note Slim Gapps are also in Beta, You can choose to download the full Slimgapps or the minimalgapps thats your choice. You can also download the photosphere addon.
Current SuperSu: http://forum.xda-developers.com/showthread.php?t=1538053
Step 2:
Place the downloaded file onto your nexus 5 using the provided cable, alternatively you can also download the files directly onto your phone using the browser.
Reboot into Recovery
Wipe data/factory reset (required)
Wipe Cache Partition (required)
I also always do the following (optional)
In mounts/ Storage
Format /system (optional)
Format /data (optional)
Format/cache (optional)
These are not necessary but I have made it a habit to do so.
Once you have performed the required resets, select Flash Zip file and flash in the following sequence
Flash SlimKat Rom
Flash SlimGapps
Flash SlimPhotoSphere (optional) Note: Does cause audio lag in recorded video with some kernels also videos are darker after photosphere flash. See Q&A section
Flash Kernel ( optional: only if you want to use a custom kernel)
Flash SuperSu ( I prefer SuperSu, SuperUser does not work properly for Me)
Reboot
Now your good to go and setup your phone.
Step 3: (optional)
~ Note for ART I follow this procedure:
After Flashing, once the phone starts I skip through the setup screen
Go to Settings-> About-> tap on build 7 times to enable developer options
Go to Settings-> Developer Options -> Select Runtime --> Art
Reboot and let it finish what its doing takes 10-15 mins.
Once done setup your phone how you like.
Reserved : Guide To SlimKat Features
Features And Guide
Once I have time I will break down all the slim settings and what they do
Features Not Included
PIE - Can be installed using Xposed Framework
HALO - Can be installed using Xposed Framework
NOTE: Xposed Framework does not play nice with ART, You will need to stick with Dalvik to use Xposed.
Feature Request
I will update this as users request features but please dont request features that can be added via addons such as xposed. There is no point adding those features to the ROM, those who want them can always install via Xposed
Keyboard Automatically Switching to Numeric Keypad when a field requires numbers only
Questions and Answers
Frequently Asked Question
http://slimroms.net/index.php/faq
These Are for SlimKat 4.4.2 beta 1.95 + Slim_AIO_gapps_4.4.2 beta1.x
These will be updated/removed as SlimKat updates
DPI/ Screen Issues
[Q] What are the default DPI's
Stock Kitkat = 480
Stock SlimKat = 361
Lowest DPI working for me = 370
[Q] Water in the Google Maps app is distorted, streaked or all over the place when zoomed out
Its a DPI issue, this is how i resolved it:
Download: Rom Toolbox lite ( Free) from PlayStore
Run app -> Swipe left to switch tab to performance --> click build.prop Editor button
on this new screen-> swipe right to bring out menu on the left side of the screen
First option is LCD density Click that-->change Value to whatever you want --> click ok and reboot
once Rebooted do the following :
Settings-> Apps-> Maps-->clear data, also clear Cache--> Force Close
Open Maps and confirm everything is working.
Some users have been able to get the maps to work properly at 361 DPI, but the lowest value at which it will work for me is 370. Default Stock Kitkat DPI is 480. Default Stock SlimKat DPI is 361
[Q] Everything is too small on default SlimKat, how can i fix that
two solutions:
go into settings-->display-->font-->change font size to make it bigger
change DPI:
Download: Rom Toolbox lite ( Free) from PlayStore
Run app -> Swipe left to switch tab to performance --> click build.prop Editor button
on this new screen-> swipe right to bring out menu on the left side of the screen
First option is LCD density Click that-->change Value to whatever you want --> click ok and reboot
Default Stock Kitkat DPI is 480, stock SlimKat DPI is 361, 400 ~ 420 DPI works best for me
Recovery
[Q] TWRP asking for a password, even though user never setup a password
When TWRP asks for a password, hit cancel.
Then go to Wipe and Factory Reset.
If that doesn't work, then restart your recovery.
If that still doesn't work then try reflashing TWRP again.
Camera
[Q] What is True View in the Camera App
True view is a camera feature to show the whole field of view of the camera.
By default the field of view is stretched and cut on the sides to fit fullscreen.
http://slimroms.net/index.php/faq/slimbean/323-what-is-true-view
[Q] Why is the Camer app Missing HDR+
HDR+ and Photosphere are closed-source. AKA no way to be built from source and must be distributed as an add-on.
Flash photosphere camera if you want HDR+.
http://forum.xda-developers.com/showpost.php?p=48832042&postcount=27
Note: PhotoSphere Addon currently adds a audio lag in recorded videos and recorded Videos are much darker, Read Q&A below about audio lag when photosphere is installed, link for photosphere is in the first post ( Slim gapps/addons)
[Q] Audio Lag in recorded video after Installing Slim PhotoSphere
Flash a different kernel, that will fix the issue
confirmed fixed with trinity.
in Recovery, without wiping:
Flash ROM
Flash Gapps
Flash PhotoSphere
Flash Kernel of choice
Flash SuperSu
Reboot
NOTE: Videos are much darker when Photosphere addon has been installed
Misc
[Q] How do I access the chamber of secrets on SlimKat
http://forum.xda-developers.com/showpost.php?p=48830608&postcount=25
[Q] Where are the QuickRecord recordings stored, are they cleared at boot and are they overwritten
/data/data/com.android.systemui/files/
It's never cleared from a reboot, but yes, rewritten each time you record.
http://forum.xda-developers.com/showpost.php?p=48832011&postcount=2577
[Q] Where is the clear all in the recent apps list
Clear all is not there as it is not needed, the list just shows the recently ran apps and provides the means of switching between apps quickly. Android will kill apps when needed there is no need to kill apps
[Q] I have no Mobile Network ( not data but no coverage at all)
This applies to only those who have no mobile network i.e they do not have a signal at all on their device and it does not say no service.
You somehow wiped the radio firmware, That needs to be restored.
http://forum.xda-developers.com/showthread.php?t=2514095
[Q] What is ART and what does it do
If you really need to know what ART is then you should not be using ART.
ART stands for Android Run Time, it is an experimental run time which is being developed by google to replace the current dalvik run time. Once released users would be able to get better performance and better battery life.
Currently, as ART is in experimental stage ( I would say Alpha, not even beta) the benefits of switching to ART are minimal. Not all apps are compatible with ART and most users will not see any performance or battery life improvements.
Thats why google buried it deep into the settings. Use at your own discretion. I suggest staying with Dalvik run time till further progress has been made on ART.
Un-Answered Questions
reserved
Regarding the last Q: Modem and EFS restoration is explained here: http://forum.xda-developers.com/showthread.php?t=2514095
Sent from my Nexus 5 using Tapatalk
lyrois said:
Regarding the last Q: Modem and EFS restoration is explained here: http://forum.xda-developers.com/showthread.php?t=2514095
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks, updated the Q&A
One last question...screen recording how do I get that again...?
Sent from my Nexus 5 using Tapatalk
Galaxysm said:
One last question...screen recording how do I get that again...?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I'm not sure how to get that, I think you have to connect the device to the computer and use something in the SDK to be able to record screen, I could be wrong. Try searching for it. If I find a solution I'll let you know.
Sent from my Nexus 5 using Tapatalk
just a suggestion what do you think to move this thread to here
http://forum.xda-developers.com/custom-roms
would be more centralized and maybe more ppl would see the q&a thread
kufikugel said:
just a suggestion what do you think to move this thread to here
http://forum.xda-developers.com/custom-roms
would be more centralized and maybe more ppl would see the q&a thread
Click to expand...
Click to collapse
Yes, i think that would be better. My Apologize for starting the thread in Q&A section. Could a Moderator please move the thread to the custom rom Q&A section or if someone knows how to move it let me know and ill move it.
Thanks
Nice work.
maybe add LMT to the "Features Not Included: PIE" section
shawnbon206 said:
Nice work.
maybe add LMT to the "Features Not Included: PIE" section
Click to expand...
Click to collapse
Thanks.
I am not sure if and when PIE is implemented if it would include LMT with it therefore i left it out. I believe the xposed framework PIE does have LMT support.
Hope there are enough people here to help me out. I've been using Slim ROMs for a couple years on G-Nex and now Nexus 5. On the last couple releases I've been having issues with Google Maps not getting a GPS fix, or when it does get a fix it's off by nearly a mile. GPS Data, Waze, Gas Buddy, etc. all work fine. After spending nearly a day re-flashing the ROM, app, clearing data, etc., I finally tried another ROM (Purity) and discovered that Google Maps gets a fix in less than 10 seconds and is within 20' accuracy. I used the latest Slim Gapps on Slim 1.95 and the CM Gapps on the Purity ROM. Has anyone had similar problems?
From my Nexus 5
AquilaDroid said:
Hope there are enough people here to help me out. I've been using Slim ROMs for a couple years on G-Nex and now Nexus 5. On the last couple releases I've been having issues with Google Maps not getting a GPS fix, or when it does get a fix it's off by nearly a mile. GPS Data, Waze, Gas Buddy, etc. all work fine. After spending nearly a day re-flashing the ROM, app, clearing data, etc., I finally tried another ROM (Purity) and discovered that Google Maps gets a fix in less than 10 seconds and is within 20' accuracy. I used the latest Slim Gapps on Slim 1.95 and the CM Gapps on the Purity ROM. Has anyone had similar problems?
From my Nexus 5
Click to expand...
Click to collapse
I just reflashed slimkat on my phone, took less then 5 seconds for it to get a GPS lock. Check the following:
Settings-> locations -> mode
Make sure high accuracy is selected
Also are you using a custom kernel ?
Flash sequence for ROMs is
Slimkat ROM
Slimgapps
Kernel ( if using custom kernel)
Supersu ( supersu always comes last)
Reboot.
Sent from my Nexus 5 using Tapatalk
Anyone have any issues with the stock Slim Explorer app. I've never really used it before as I've always been an ES Explorer user but want to switch having the auto toggle TRDS modes. The app loads up but as soon as I scroll the screen the app closes and I get a "Slim Explorer has stopped" message. I've seen it in the past a handful of times I went to change DPI with it before installing ES. I did a complete clean install(ie. manually wiped everything and re-downloaded and re-setup all my apps instead of restoring them with Titanium), sha matches, so I can't think of anything else that could be the issue. Maybe it doesn't agree with Super SU???
Yep, did all that except for the SuperSU bit. I did use SuperSU on the Purity install though but haven't had any problems with the built in Superuser before. I'll nandroid back to the Slim ROM to give it a try. It was with the stock kernel.
From my Nexus 5
AndrasLOHF said:
Anyone have any issues with the stock Slim Explorer app. I've never really used it before as I've always been an ES Explorer user but want to switch having the auto toggle TRDS modes. The app loads up but as soon as I scroll the screen the app closes and I get a "Slim Explorer has stopped" message. I've seen it in the past a handful of times I went to change DPI with it before installing ES. I did a complete clean install(ie. manually wiped everything and re-downloaded and re-setup all my apps instead of restoring them with Titanium), sha matches, so I can't think of anything else that could be the issue. Maybe it doesn't agree with Super SU???
Click to expand...
Click to collapse
U mean simple explorer ?
Its working for me.
It could be super user, I've had issues with it
First post on this forum has link to supersu, download zip file flash in recovery. C if that solves the issue
Sent from my Nexus 5 using Tapatalk
AquilaDroid said:
Yep, did all that except for the SuperSU bit. I did use SuperSU on the Purity install though but haven't had any problems with the built in Superuser before. I'll nandroid back to the Slim ROM to give it a try. It was with the stock kernel.
From my Nexus 5
Click to expand...
Click to collapse
I've had issues with super user so always use supersu, but maps has nothing to do with either.
Did u check the settings?
Also sometimes you have to be outside to get a GPS lock,
Also try this:
Settings -> apps-> maps.
Clear data clear cache force close.
Reboot
Go outside and open maps c if that fixes it
Sent from my Nexus 5 using Tapatalk
OK, but it will be a while - when I went into recovery (TWRP) it asked for a password (which I haven't set) then failed to backup the existing ROM.
Sent from my Nexus 5 using Tapatalk 2
fruitsalt said:
U mean simple explorer ?
Its working for me.
It could be super user, I've had issues with it
First post on this forum has link to supersu, download zip file flash in recovery. C if that solves the issue
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I have Super SU installed and working already seeing as I use Faux kernel as well as I've always had issues(even on a SlimBean port on Evo LTE)with Superuser unmounting the system as RW. It's weird. It only happens when I scroll from within the emulated/legacy/0 storage. I can scroll within the device partition and change settings just fine.
Do you use ART??? Only other thing I can think of.
Edit: Added a screenshot to the post as well as a bug report
Hey guys ! Some days ago i saw that some peoples want slim GApps for cm11.Today,i found this thread http://forum.xda-developers.com/showthread.php?t=2547250 .Flashing this zip,you will be able to choose what GApps to flash using AROMA.All GApps are optimized for ART,but i think work without ART too.
There is also a zip called "Dismantler" (using AROMA too) which let you to choose what system apps to delete (there is over 40 apps to choose).This work for cm11.Also,work for PAC rom,Omni,Chameleon OS and AOKP,but i dont know if these must be based on 4.4.
For more info,check the thread.Thanks to @Cipher666 .
PS: i dont tried it yet,but i gonna try in some minutes because now i dont have time.But it should work.
EDIT: is working.Thanks to @adamuadamu who tested.
Anyone tried it? Work? I cant test it because now im back on 4.3....
I tried those gapps a week ago while testing kitkat.
everything worked fine for me - but I didn't install whole package - rather a close-to-minimum set
Props to @BeansTown106 for source, @GtrCraft for PureHammerhead, and KrexusROM @KreAch3R @Jax Teller for the device, kernel, vendor, and hardware trees, and @dragos281993 for PureMako
READ EVERYTHING HERE BEFORE FLASHING:
-Updating to TWRP 3.1.1-0 is recommended
-Use BeansGapps Mini https://www.androidfilehost.com/?w=files&flid=171927
-Not prerooted. SuperSU stable or Magisk stable recommended
-No camera included. Google Camera 2.5.052 recommended http://www.apkmirror.com/apk/google-inc/camera/camera-2-5-052-release/
-As of the 4/23 release the ro.opa.eligible_device=true is no longer in the system/build.prop. This will cause the Google App to use Google Now interface instead of Google Assistant. If you want to use Google Assistant use the Get Assistant - Root app on the PlayStore (choose NEW method when prompted) OR if you use Magisk theres a Google Assistant Enabler module for this.
-Want a Pixel Launcher that allows swipe up to App Drawer in landscape? Sideload the Android O Pixel Launcher from apkmirror.com http://www.apkmirror.com/apk/google...ixel-launcher-o-3952143-android-apk-download/
-Netflix casts fine but throws an Error on playback. Sideload Netflix 4.8.5 from apkmirror.com OR use the zipaligned Netflix4.8.5-signed.apk in the ROM Download folder https://www.androidfilehost.com/?fid=529152257862715472 . The zipaligned apk will never show up as needing an update on PlayStore.
-Features? Updates? Read the changelog below.
ROM Downloads: https://www.androidfilehost.com/?w=files&flid=164137
PureNexus Changelog: https://docs.google.com/document/d/1ROCTINpYR2M2QZ-uzErZSNK8gjIm_bXS6sXL83YePd0/pub
Source Code: https://github.com/PureNexusProject
Device and Kernel Source:https://github.com/krexus-partners
FLO BUILD SPECIFIC INFO:
-03/22/2017 build includes all the Pixel Gapps that the OFFICIAL Pure Nexus 3/17 builds include, EXCEPT Google Camera, Hangouts, Chrome, and Photos.
-03/20/2017 build includes all the Pixel Gapps that the OFFICIAL Pure Nexus 3/17 builds include, EXCEPT Google Camera.
KNOWN ISSUE:.
-Netflix casts fine but may throw a 0013 Error on playback. Sideload Netflix 4.8.5 from apkmirror.com OR use the zipaligned Netflix4.8.5-signed.apk in the ROM Download folder in OP. The zipaligned apk will never show up as needing an update on PlayStore.
Very good of you to take this on for good old flo Bill. Thanks man!
Mike T
Please some love for Deb too :crying:
@buffal0b1ll
Hello)
Are there any plans for updating this Rom?
Very good， just looking for one。
I'm just afraid this one won't be got closed like other thread lol. Anyway thanks for letting my fav rom fly again. :good:
After flash this Pure
Have to say, this ROM is dope
Thanks for this work
Hope this ROM dont die
boom1982 said:
@buffal0b1ll
Hello)
Are there any plans for updating this Rom?
Click to expand...
Click to collapse
ranaxda200 said:
I'm just afraid this one won't be got closed like other thread lol. Anyway thanks for letting my fav rom fly again. :good:
Click to expand...
Click to collapse
manfio said:
After flash this Pure
Have to say, this ROM is dope
Thanks for this work
Hope this ROM dont die
Click to expand...
Click to collapse
A thread full of optimists I see As long as the trees work and the kernels boot, I'm not planning on going anywhere.
Purenexus+glitch r544+supersu 2.79 sr3+google camera 2.7.008+substratum themes: all works perfectly, also night light!!! Thank you very much buffal0b1ll
Hi is it compatible with f2fs format?
Hmm, looks interesting... lets give this one a go, shall we?
lollyjay said:
Hi is it compatible with f2fs format?
Click to expand...
Click to collapse
Kernels support f2fs, firstly, not ROMs. The stock AOSP kernel with this ROM doesn't support f2fs. But if you find a custom kernel that supports f2fs you can use it and format your data and cache partitions to f2fs on any ROM. Secondly, f2fs is only faster on writes, so only data and cache partitions benefit from that file system. ROM support for f2fs (as had been popular a couple years ago) would only be to allow system partition to also support f2fs, which this ROM doesn't have. That type of support is pretty much a thing of the past because it's a pain in the ass to do since ROM zips started using block storage convention and there's no speed advantage to having system be f2fs anyway. Make sense?
I don't wanna hear about all the common f2fs issues that have nothing to do with the ROM if you do try it. These include:. Couldn't flash ROM/GAPPS because it says system partition too small, couldn't make or restore a nandroid, lost all my data because I didn't offload it first, lost all my data when my data partition got corrupted, wrong internal storage size reported, can't take photo/screenshot write to internal storage.
If you're smarter than the average problem solver and have a PC, an OTG, and enjoy offloading and moving stuff back, then the modest (if not just placebo) speed gain of going f2fs may be worth the risk of wasted time and lost data. If you're the user that uses a toolkit instead of a terminal, then I'd let that sleeping dog lie.
Your point(s) well taken. Personally I have found little to gain from f2fs., except for my old TF300T
This rom is superb!!! It contains just about everything I had ever dreamt of seeing on the lovely, old Nexus 7, from Nougat in full flow to Google assistant and Night Light. I can even watch some previously impossible TV by
using the 'hide' function in the new version 11.6 of Magisk along with Magisk Manager from the Playstore. Many thanks to the Dev for giving my Nexus 7 a new lease of life. This is super work.
this rom is great
but one problem i think.
if its possible, in next build remove some apk from system, like chrome, calendar, calculator, gboard, google fotos
please
its to free some system space
manfio said:
this rom is great
but one problem i think.
if its possible, in next build remove some apk from system, like chrome, calendar, calculator, gboard, google fotos
please
its to free some system space
Click to expand...
Click to collapse
The ROM is in sync with @BeansTown106 source with the exception of my removing Google Camera 4.x from the Gapps because it's incompatible with Flo. Removing gboard would leave you with no keyboard, see the changelog in the OP.
Are you bumping up against a full system when attempting to flash more mods?
You're welcome to remove whatever system apps you want (before or after booting) if you need more system partition space. That said, the only apps I'd consider removing from built in Gapps, if they are still in source on the next go around, would be Hangouts, Chrome, and Photos.
@buffal0b1ll
Maybe there is a meaning remove gapps from rom...
That there were no questions on this topic)
Great rom love it so quickly
Great Rom just installed on my N7 (2013) .
Sent from my LG-H850 using Tapatalk
UPDATE 18/08/2017
• Google Play Protect
• Google Connectivity Services (Update)
• Interface Optimization
• English Support (Input Language)
• WiFi (Fix Bug)
• Download ➤ https://goo.gl/CDxV8J
Let me try this, your previous ROM is not supported with Magisk 13. any information why?
I hope this one is Magisk 13 supported
--edit
Magisk 13 still not work,
Pre-routed or without root and gapps
goonoth said:
Let me try this, your previous ROM is not supported with Magisk 13. any information why?
I hope this one is Magisk 13 supported
--edit
Magisk 13 still not work,
Click to expand...
Click to collapse
In this new update there are two options of rom the first one already comes pre-routed and the second option and rom without root and without gapps
will try it
i will report it later.
wifi hot spot isnt working
robsonwaplog said:
In this new update there are two options of rom the first one already comes pre-routed and the second option and rom without root and without gapps
Click to expand...
Click to collapse
Yes, I know
But root with magisk is more reliable as I can hide root for banking apps and Po Go
Those apps will detected my phone is rooted
With root and gapps or without root and gapps!
goonoth said:
Yes, I know
But root with magisk is more reliable as I can hide root for banking apps and Po Go
Those apps will detected my phone is rooted
Click to expand...
Click to collapse
So just choose the best option for you between the two with root and gapps or without root and gapps ... ok!
Di I have to format data and system to install this version? Currently I am on your previous build.
any bugs?
Adhies99 said:
any bugs?
Click to expand...
Click to collapse
Didn't find any bugs, only sometimes I get crashes from calendar and Google app, rarely though.
Pretty stable and really fast.
[ROM] Do not need not clean anything
ionlyaskforeden said:
Di I have to format data and system to install this version? Currently I am on your previous build.
Click to expand...
Click to collapse
Not need not and just for those people who are with other rom more so you do not need to clean anything just plain fash
[ROM] I did not find any errors
Adhies99 said:
any bugs?
Click to expand...
Click to collapse
I did not find any errors, but it would be cool if you test and tell me if you find any errors to fix it
[ROM] Used the gapps and supersu optimized that i left it is much better
ionlyaskforeden said:
Didn't find any bugs, only sometimes I get crashes from calendar and Google app, rarely though.
Pretty stable and really fast.
Click to expand...
Click to collapse
Thank you comment i'll check to fix ... but you use the optimized gapps that i let
robsonwaplog said:
Thank you comment i'll check to fix ... but you use the optimized gapps that i let
Click to expand...
Click to collapse
Yes, the in version the gapps are included, but i still flashed the zip from the folder you provided.
Howerver after reinstalling the corrupted Google Apps form withing android everything works flawlessly for the most part.
If you have anything for me to try out dont hesitatem would be glad to help.
~Eden
I found two bugs
I found two bugs on this rom, the first bug is go to settings-display- saturation and color-screen optimize, when I set it to Normal mode, it works. But when I restart my phone, this setting restored to Smart adaption(although it seems circled the Normal mode, it actually Smart adaption, the same result on Screen enhance) So currently I have to check this setting every time I restart my phone.
The second bug is this rom is incompatible with ShadowsocksR( a software which can bypass the censorship in China), it keeps FC when every time when I open SSR( stand for ShadowsocksR) I have tested this software on MIUI, it works great.
Could you fix these two bugs, I would be grateful.
And here is the link of SSR, if you would like to test it.
[email protected]/shadowsocksr-backup/shadowsocksr-android/releases/download/3.4.0.6/ssr_3.4.0.6.apk
Replace @ with . instead
Can this rom support OMS for substratum?
[ROM] incompatible
maple3142 said:
Can this rom support OMS for substratum?
Click to expand...
Click to collapse
Sorry, but I can not do this ... incompatible
I am having some 4g problems with this rom. Tried to force switch to 4g no luck.
Also the camera looks a bit off, a bit of white noise and unsharp.
The rom started in chinese without the option to select a language.
Further it seems to behave fast and quick.
What about the camera quality? Is it good as stock? Or the same problem as the rest of AOSP ROMS?
Thanks fot keeping updating.
Update 02/08/2017
semm said:
I am having some 4g problems with this rom. Tried to force switch to 4g no luck.
Also the camera looks a bit off, a bit of white noise and unsharp.
The rom started in chinese without the option to select a language.
Further it seems to behave fast and quick.
Click to expand...
Click to collapse
TEST THE NEW VERSION 02/08/2017 https://goo.gl/AYzgGW
Maybe this is a very stupid question but I really have no idea why this problem occurs
My phone (HTC One S Ville mit Resurrection Remix (Android 5.1)) worked perfectly fine until last Friday.
At this date a new update of Telegram Messenger was released. I installed it and while installation of this app my phone did a restart and got stuck in a bootloop.
I restored using TWRP and retried - same problem. I also deleted the app and its data to do a fresh install - bootloop after installation.
Furthermore I noticed the exactly same behavior for the last update of WiGLE. All other apps could be updated to their latest versions without problems.
I used Google Play to update these apps.
What could be a problem for that? Is android just too old to these apps or could there be a collision with something installed on my phone/the ROM? How can I debug this?
I am not an android expert and I am very thankful for any kind of help :')
Thank you! =)
Same Problem with LG G2 mini / Android 6
Hello,
I'm facing the similar problems since a few days. Running Resurrection 6.0.1 on LG G2 Mini.
It started with installing maxdome-app at thursday, last week. Phone went into bootloop.
Wiping and or deinstalling the app in safe-mode did not work. So I restored to an older backup. This worked some time but ran into bootloop after a while ( I do not know what I've done exactly to get into this, this time).
I tried around a little. One part was a fresh install of cyanogenmod 13. This worked some time and I could find out that installing telegramm messenger had the bootloop-effect repeatable.
Sorry for not giving any help to the thread-creator but I hope we can give any more information to each other or anyone else can help?
Right now I am installing apps and backing up all the time to get some half-working system, but better ideas would be appreciated
Good to know that I am not alone
I figured out that there are a few more apps causing the bootloop. Here is a list:
WiGLE Wardriving
Telegram Messenger
pr0gramm.com app
Playstore Changelog (XPosed Module)
Statusbar Download Progress (XPosed Module)
Maxdome
I already updated Xposed Framework, Google Play Services and Google WebView to prevent incompatibilities. Problem still exists.
I updated everything as far as possible and made a backup using TWRP so I can restore my OS at any point. Further you could backup your apps using Titanium Backup. I it worth its price!
I started facing a similar problem of app updates causing bootloops on my device which was running CandySix ROM / 6.0.1. Apps causing bootlooping included Greenify and Nova Launcher. I had another device which has a factory 6.0.1 ROM rooted with Xposed and that device didn't have bootloop issues with these same versions of apps. Fortunately I was able to update the first device to a LineageOS 14.1 7.1.2 ROM and once again continue using the latest version of apps without bootlooping issues - but I never did understand exactly what was causing the bootlooping problem. That was a rather frustrating experience.
When the first bootloop happened, I was updating one single app, so I knew it was probably the one I should roll back to the previous version to fix the problem - so I didn't have to resort to a full TWRP restore.
How did you do a rollback of an app while you are in a bootloop? I would be glad to know that
Unfortunately my Device One S Ville does not get any updates anymore
In my case I can boot to custom recovery/TWRP to delete the app apk from the its /data/app folder - which basically prevents it from running when I reboot the phone. I also use an apk extractor app to save the apk of all apps I install and I also use Titanium Backup - so between those two I have copies of the older apk versions to install. You can also find older apk versions on apkmirror.com.
Depending on the severity of the bootloop, you can also connect your phone to a PC and use adb to disable/uninstall the app causing the problem if you know which one it is.
-kw said:
How did you do a rollback of an app while you are in a bootloop? I would be glad to know that
Unfortunately my Device One S Ville does not get any updates anymore
Click to expand...
Click to collapse
Thank you for your explanation! This sounds a bit more stressful to me than rather restore via TWRP but could me more time efficient for larger ROMs. I will keep this in mind
Thanks and can confirm that deleting the app folder/apk via twrp can help. I got back into my android 6 again. For me seems more that DavDroid caused it (but Telegram was suspicious, too).
DavDroid mentioned in the last update on 4th November, that they released a workaround against crash and bootloops on some custom roms
Depending on how old your TWRP backup is, restoring from TWRP is an option. But often I have not made a backup in a while or made many recent changes that I didn't want to lose, so the other ways I suggested are more time efficient in some cases.
-kw said:
Thank you for your explanation! This sounds a bit more stressful to me than rather restore via TWRP but could me more time efficient for larger ROMs. I will keep this in mind
Click to expand...
Click to collapse
Upgrade to Android 7
I can add EDS app to the non-working programs.
As far as I could install Telegram (same Version) by downloading .apk I suspect the problem is something depending with playstore. This would explain the many affected apps. But of course I don't know it for sure.
Inspired from divineBliss I upgraded to Android 7 (LineageOS 14.1) and could install everything as I wanted without problems so far. Thanks for that. Looks good, but I will wait some days after I'm convinced.
@-kw: did you try the following link for upgrading to higher android-version?
https://forum.xda-developers.com/htc-one-s/development/7-1-lineage14-1-htc-one-s-ville-t3540981
Glad you were able to update ROMs and escape the bootlooping problem
I have been running LineageOS 14.1 for about a month now without any bootlooping issues due to app updates - so I expect you won't have any issues. I did cause some dread time consuming to resolve bootlooping due to some bad substratum themes, but that's a different issue altogether .
michibr said:
I can add EDS app to the non-working programs.
As far as I could install Telegram (same Version) by downloading .apk I suspect the problem is something depending with playstore. This would explain the many affected apps. But of course I don't know it for sure.
Inspired from divineBliss I upgraded to Android 7 (LineageOS 14.1) and could install everything as I wanted without problems so far. Thanks for that. Looks good, but I will wait some days after I'm convinced.
@-kw: did you try the following link for upgrading to higher android-version?
https://forum.xda-developers.com/htc-one-s/development/7-1-lineage14-1-htc-one-s-ville-t3540981
Click to expand...
Click to collapse
@michibr:
I am very pleased with my Resurrection ROM; but this is stuck on Android 5.1. I will give a new ROM a try when I have the time for that
At this time it seems like this is the only solution of escaping the bootloop-problem
FYI
I updated to Android 7.1 RR and now I can update all my Apps without problems
I am sorry that this is the only solution I can provide, but still better than nothing
Hi all,
I'm having exactly the same problem, it all started with FB, then some other apps.
I had to reboot into Safe Mode to uninstall those apps.
I'm running on cm12.1 and I have my own reason not to upgrade to higher Android.
Am hoping someone can come out with a solution.
For now, here's my list of apps:
- Facebook (Facebook Lite is fine)
- Telegram
- Bluemail
- Local telco app
I am sorry to inform you that I did a lot of research and was not able to find any other solution than upgrading to a higher android.
The problem is with appt2 someone reported it in google's issue tracker and someone from goole descriped it in detail here's it :-
CyanogenMod has this function getPkgName (https://github.com/CyanogenMod/android_frameworks_base/blob/cm-13.0/libs/androidfw/AssetManager.cpp). It creates a ResXMLTree on the stack and points it at a buffer from an asset without making a copy. Then it closes the asset before the ResXMLTree is destroyed.
For apps built by aapt, this is benign. However, aapt2 produces UTF-8 string pools, which cause the ResXMLTree's ResStringPool(mStrings)'s mCache to become non-null in ResStringPool::stringAt (https://github.com/CyanogenMod/android_frameworks_base/blob/cm-13.0/libs/androidfw/ResourceTypes.cpp). Then ResStringPool::uninit dereferences mHeader (which is now dangling), and a crash ensues.
This crash shows up in different ways. On one Cyanogen OS device, the launcher crashes when an app built with aapt2 has been installed, but only if the manifest is large (probably due to how deallocation happens for small vs large blobs). On another device, system_server crashes at boot if an aapt2-built app is installed.
We're attempting to work around this with a custom build of aapt2 that always produces a UTF-16 string pool for the manifest. Results so far are promising.
Can this be patched somehow at the OS via xposed for all of the roms that won't get updated?
The fix for this issue is available here (CM13):
https://forum.xda-developers.com/showpost.php?p=74636021&postcount=216
CM12.1:
The fix for this issue is available here (12.1):
https://forum.xda-developers.com/showpost.php?p=74842530&postcount=464
Is this .zip patch for any device with any Lollipop 5.1.1 ROM?
Because I just installed it and my HTC one X with Resurrection Remix ROM (Lollipop 5.1.1) goes black after the HTC logo.
lescht said:
The fix for this issue is available here (CM13):
https://forum.xda-developers.com/showpost.php?p=74636021&postcount=216
CM12.1:
The fix for this issue is available here (12.1):
https://forum.xda-developers.com/showpost.php?p=74842530&postcount=464
Click to expand...
Click to collapse
Hello what is about cm11 kitkat 4.4.4 sameissue but no fix-
could anyone make a fix? Please help.