Search Apps page immediately after boot - SlimRoms Q&A

Hello!
I recently flashed Slimrom6 on my Samsung S5 and I am super-freaking happy with it. My phone runs smooth as slik and it's a dream using this minimal and lightweight ROM.
However, there's a slight problem - more like a small annoyance. After every boot, the first thing that happens when the screen is unlocked is that a "search apps" page pops into view and obscures the home screen. Pressing the hardware back key dismisses it, no problem - but why does this search apps-page appear? Can it be turned off? It's been there since I flashed, so I really don't think it has anything to do with anything else that I installed later on, like Xposed Framework etc.
Anyone else having this issue?
Setup:
Samsung Galaxy S5 klte (SM-G900F)
Recovery:
PhilZ Touch 6.26.2
Clockworkmod v6.0.4.7
Android Version:
6.0.1
Slim Version:
Slim-6.0.1.build. 1.17-WEEKLY-20161223-0435
Baseband Version:
G900FXXU1POH1
Kernel Version:
3.4.17-g12167bc
Build Number:
slim_klte-userdebug 6.0.1 MOB31K fbe83acac7 test-keys
Any help is greatly appreciated!

Related

[Q] Pre-production Nexus 7

Hi guys, need some help here. I bought a BNIB Nexus 7 8GB off craigslist and it turns out it's some kind of pre-production/demo unit. It runs smooth and does exactly what I need it to do but there are some minor annoyances in the system and it'd be great if I can load a stock rom onto it. Does anyone know how I can update the SW so it'll be running stock rom? I've tried the "Flash Stock + Unroot" option in Nexus Root Toolkit but when the DOS menu pops up it just fails everything and gets stuck in fastbook. I had to do a hard reset to boot it back up and nothing changed. If someone can give me a hand here that would be wonderful.
Here's some info in "About Tablet":
Android Version: Jellybean
Kernel Version: 3.1.10-00002-gcb40deb (Dated May 8th)
Build Number: nakasif-userdebug JellyBean JRN38 349871 dev-keys
You got a dev ROM.
Flash stock nexus image and you're golden.
Will the next nexus have a longer screen?

Unable to get leankernel to run

So I've recently rooted and installed a custom rom on my phone for the first time with success. My phone is the T-Mobile Galaxy S3 N900T. I'm running C-Rom-KK-v7.1-20140622 which is based on 4.4.4 and it's great. I've been trying to find a custom kernel that I can load onto it to help increase the battery life, hence why I heard LK was really good for that, unfortunately every time I flash the kernel it just reboots to a black screen. The LED buttons will sometimes light up, but nothing else happens, and I'm forced to wipe and reinstall c-rom. I'm really looking forward to getting a custom kernel to work and any help would be appreciated.
OneDarkNite said:
So I've recently rooted and installed a custom rom on my phone for the first time with success. My phone is the T-Mobile Galaxy S3 N900T. I'm running C-Rom-KK-v7.1-20140622 which is based on 4.4.4 and it's great. I've been trying to find a custom kernel that I can load onto it to help increase the battery life, hence why I heard LK was really good for that, unfortunately every time I flash the kernel it just reboots to a black screen. The LED buttons will sometimes light up, but nothing else happens, and I'm forced to wipe and reinstall c-rom. I'm really looking forward to getting a custom kernel to work and any help would be appreciated.
Click to expand...
Click to collapse
Been a while since I scanned the N3 forum however, check that the ROM is compatible with the Kernel and If the Kernel does indeed run on the 900T - when I had my N3 T-Mo users used to have to flash a fix to boot N9005 kernels.

[Q] [Help] - Touch screen not working after kernel/ROM flash

Hello,
I flashed a 4.4.4 KitKat ROM (Google Play Edition) on my phone and it comes with a custom kernel and the touch screen doesn't respond to touch after flashing it. If I change the ROM back to the previous ROM I had then it works fine but that's not the point. If I flash any custom kernel then my Galaxy S4 GT-I9505 touch screen stops working until I restore the stock kernel.
Is there a way around this or a fix for this because I'm finding it very difficult to find anyone else having this problem. I've done quite a bit of searching and so far nothing is similar to what I have. I'd like the use this ROM because it's much better than the other GPE ROM I'm currently using, but if I can't use the touch screen it's not worth it really.
This ROM is designed for the GT-I9505 and that, if I haven't already mentioned, is the device I'm using.
Any suggestions?
Thanks in advance.

Problems with my I9505 - encryption

Hello,
First post so big hello to everyone
I've recently startet experiencing issues with my Galasy X4 - issues always appear after encrypting device. Description:
- Device working fine on Ressurection Remix , CyanogenMod 12 and Stock ROM fine just after flashing (stable, all functionalities OK)
- My company email enforcing encryption or phone, straight after this process I cannot use my device (process goes without any problem, device rebooting). For example on stock rom I'm experiencing problem with NFC service all the time crashing, on CyanogenMod and Ressurection Remix Gapps process all the time stop responding etc. I cannot use my phone after encryption process ass all the time its crashing and I can only press OK all the time.
Is anyone aware of that kind of the issues? Any advices howto avoid them? Please let me know if you need any more details.
My Galaxy is S4 I9505 (LTE) bought in UK EE carrier
Stock firmware used:
http://www.sammobile.com/firmwares/download/38084/I9505XXUGNI2_I9505EVRGNI2_EVR
http://www.sammobile.com/firmwares/download/48203/I9505XXUHOD7_I9505EVRHOD1_EVR
Remixes used:
https://download.cyanogenmod.org/get/jenkins/113878/cm-12.1-20150613-NIGHTLY-jfltexx.zip
http://forum.xda-developers.com/gal...-0-2-ressurection-lollipop-5-2-7dark-t2994283
Many thanks for any suggestionso on this one.
P.S.
I'm using for flashing Odin / Heimdall ... because some reason Kies does not reconize my device - so I cannot go back to stock rom using it. Strange thing that going on stock 4.4 ROM is that when Im trying to perform update it says me that my device was modified - dont know is it imporant. Of course on stock firmwares I'm not using root (on ressurection & cm I installing CWM)

Note 3 (N9005) auto rotation does not work for any CFW

Dear Community,
I hope that this is the right place to post and any of you can help me.
My (aktual) Hardware/Software bits:
Galaxy Note 3 (SM-N9005)
Android: 5.1.1
Baseband-Version: N9005XXUGBOD3
Kernel-Version 3.4.108-f2fs-temasek-cm12.1-hlte-v1.25+
temaseksnappy #1
Temasek unofficial version V16.4
Build: LMY48J test-keys
Recovery: twrp 2.8.7.0-hlte-4.4
My actual problem is the following: My Note 3 by default had a 4.4.2 OFW on it, which I early upgraded to Lolipop 5.0.1. Everything works for the OFW 4.4.2 and 5.0.1 fine. As soon as I try to flash it with a CFW like CM11, CM12, CM12.1, CM12.1 (temaseksnappy), Gummy 4.4.4 I am losing the feature of auto rotation.
Of cource I did a clean flash, wiping DALVIK/CACHE/DATA and system, double time even one befor the flash, one after.
I also tried to put the battery, sim and sd out for few min before rebooting, while autorotation is manualy turned off.
Even a MODEM I flushed to fix this issue, but without success. Nothing helps but going back to OFW.
My last try was downgrading to the original 4.4.2, including baseband trieing from there to go to any CFW (CM11) as well as from OFW 4.4.2 -> OFW 5.0.1 -> CFW 5.1.1 (http://forum.xda-developers.com/galaxy-note-3/development/hlte-spr-vzw-temaseks-unofficial-t2953375)
There was also a post about a possible missing or broken lib in /system/lib which I replaced
Nothing helps (libGNU... something). This helped me alreay once in OFW after kicking out all the junk apps, but this is a different storry and not related anyhow.
Is there anybody out there who has the same problem or even better knows a solution?
My shot would be that:
1) CM has a problem with my particular hard-/software (Kernel, Baseband, Recovery, whatever) as I just tied CM or at least CM based CFWs.
PLEASE HELP.
Thank you very much in advance.
After about almost a year I cam back, giving again a try to CM, However I still have the same issue. Finally Anybody please!
Do you have the same issue with touchwiz 5.1.1 and 6.0.1?. Not the cm/aosp roms which aren't samsung based.
Sent from my SM-N920C
Rosli59564 said:
Do you have the same issue with touchwiz 5.1.1 and 6.0.1?. Not the cm/aosp roms which aren't samsung based.
Sent from my SM-N920C
Click to expand...
Click to collapse
Hello,
Thx for your reply. Right now I am on CM13 (temasek hlte v9.6)
http://forum.xda-developers.com/galaxy-note-3/development/hlte-spr-vzw-temaseks-unofficial-t2953375
This might should be specially compiled for sm-n9005 like mine.
Everything expect rotation works fine. However The accelleration is also working fine as I tested with "sensor test". Even the integrated camera App is rotating, however the rest is not.
In addition I downloaded "adaptive rotationfree", If I set it "stock Auto" nothing happens, but if I set it to "force auto" the rotation will work exacly once and then stops undtil I force it to portrait again.
What do you mean exactly with "touchwiz"? Is this jus a different kernel or a whole CFW?
As I wrote in the frist post I tried already a lot of CFW and ALL had this issue, but the OFW ;(
What shell I flush to get this working, which is not OFW?
BIG THX for YOUR HELP
Touchwizz is the firmware that comes with the stock Samsung firmware .
Also in custom Samsung based roms .
Hello,
thx for the tip with TouchWiz vs aosp. At the moment I am running "DarkLord N5 Release Candidate 2.12" which can get find here: http://forum.xda-developers.com/galaxy-note-3/development/rom-darklord-s6-port-alpha-t3083087
This Rom is TouchWiz Based and guess what ....
Autorotation works.
However I do not understand what the problem realy is and would prefer to run cm13 insteat. I mean even samsung devices got a accellerator within which works also fine with AOSP software, showing numbers moving while turning the phone. In addition for example on the post http://forum.xda-developers.com/galaxy-note-3/development/hlte-spr-vzw-temaseks-unofficial-t2953375 it is said that this is explicite for note 3 including the model n9005. So ...
Can anybody point me to the problem or even better to the fix?
Is there any chance CM would fix this?
Regards

Categories

Resources