Related
First of all I would like to state that I am running echo-rom, I would like to have posted in there but the thread is closed.
My first problem is that the expandable volume menu does not work, this happened to me before with other roms (all on TW) but I couldn't be bothered until now. Whenever I click the gear icon which should expand, it doesn't work. It works before (until I do something?). Anyway I flashed the rom yesterday and didn't bother configuring/customizing it until today. I will try to describe anything I did until the point I noticed it broke again.
I enabled xposed framework, with the modules: wanam xposed, enable battery stats for kitkat, gravitybox, app-settings and xposed torch.
I tweaked some stuff in wanam xposed and in the echo customization center.
Anyway I don't really know what caused it, if no one knows why I will try to pay attention next time when it happens.
The second problem is that whenever I try to swipe down to open my notification bar it doesn't want to work half the time. On my home screen the statusbar turns black (instead of transparent), so there is some sort of registration of touch? I proceed to let go of my finger and and then try again. I also thought that I could have misplaced my finger but I don't know why the statusbar would turn black then.
If anyone knows or has encountered this problem before please share,
much appreciated.
I dunno know but i tried exposed once with a slimrom and it messed my phone up really bad upto the point everything was force crashing. To me i think exposed is your problem. Try wiping data, cache, dalvik, and format system and boot with cwm recovery then flash official firmware for you phone. DO NOT USE 4.3 FIRMWARE IF YOUR ON A 4.4 ROM!! Look for 4.4 rom instead. Sammobile good site but need registraion and slow download for free users (about 1hour) after that try instakking. Your fav rom without xposed. Im 80% sure it will work
So I fixed it, I disabled both gravitybox and wanam xposed and after the reboot volume expand worked again, then I enabled wanam xposed again and it still worked. Either way gravitybox caused it, or it was caused by a conflict between the two.
Also the statusbar problem, my rom has an option where you double-tap the battery icon to change the style of it, I noticed by trying to swipe down from the battery icon it doesnt work. So there you have it. Problem solved
The reason is really simple. You don't read before you install the modules.
You can't use Gravitybox on a TW based rom. It's states that in the description. Gravitybox is for aosp only!
Same applies for the post from 189cutter. Wanam Xposed is only for TW based roms. Slimrom is clearly no TW based rom.
So if you want to use the modules, read if they are for your rom. Also make sure that there is no overlapping in functions, because that could cause strange problems as well.
Point taken but im never ever ever gonna use xpose or such things like it lol now im using cm m9 and its perfect lol
Hey guys.
I don´t wanted to create a thread about this but after some troubleshooting without a solution i don´t know what to do.
After i installed (i think it happens after that) kingmercians hydrogen os, i doesn´t matter which rom i use (cm13, cm12, aicp, ......) i got random reboots. I did´nt install any new app, tried it with gapps, without gapps.... Sometimes it happened right after the first boot of a new rom, sometimes while i restored via TB (no system apps!). It´s not reproducible for me.
I don´t want to make it factory fresh but i know this could be the last way.
Any suggestions?
Thanks in advance!
Trinaaa said:
Hey guys.
I don´t wanted to create a thread about this but after some troubleshooting without a solution i don´t know what to do.
After i installed (i think it happens after that) kingmercians hydrogen os, i doesn´t matter which rom i use (cm13, cm12, aicp, ......) i got random reboots. I did´nt install any new app, tried it with gapps, without gapps.... Sometimes it happened right after the first boot of a new rom, sometimes while i restored via TB (no system apps!). It´s not reproducible for me.
I don´t want to make it factory fresh but i know this could be the last way.
Any suggestions?
Thanks in advance!
Click to expand...
Click to collapse
Did you wipe before you installed new rom ? , also have to say that cyanogenmods like 12.1 and 13 are still unstable tried all myself too . I suggest you to wipe everything but not internal storage , after you installed those ROM's and gapps did you wipe ? also what gapps are you using ?
chrismomike said:
Did you wipe before you installed new rom ? , also have to say that cyanogenmods like 12.1 and 13 are still unstable tried all myself too . I suggest you to wipe everything but not internal storage , after you installed those ROM's and gapps did you wipe ? also what gapps are you using ?
Click to expand...
Click to collapse
First, thank you for your reply!
Yeah.... Every time i switch between roms i wipe everything, cache, data, dalvik and system. And after gapps, i wipe dalvik and cache.
The strange thing is, the roms i used before without any problems (installed for example razor rom which i still had on my internal memory) causes reboots. That never happens before.
Trinaaa said:
First, thank you for your reply!
Yeah.... Every time i switch between roms i wipe everything, cache, data, dalvik and system. And after gapps, i wipe dalvik and cache.
The strange thing is, the roms i used before without any problems (installed for example razor rom which i still had on my internal memory) causes reboots. That never happens before.
Click to expand...
Click to collapse
I installed H2O by king but didn't had issues I changed it because of the notification system , sometimes it took minutes untill I've got a notification on screen off ,and sometimes I had to open the app to see that I got notifications (apps like Whatsapp , Facebook messenger ), after that I installed cm 12.1 and 13 also , on both had problems on camera and rebooted every single time I opened Camera app and Wifi/Data change didn't always worked , they are still unstable I suggest you to install OxigenOS with boeffa kernel and try some of those profiles there my phone working way better than before http://forum.xda-developers.com/oneplus-2/general/unofficial-boeffla-kernel-profiles-t3289395 , or if you like custom ROM's what gapps are you using ?
chrismomike said:
I installed H2O by king but didn't had issues I changed it because of the notification system , sometimes it took minutes untill I've got a notification on screen off ,and sometimes I had to open the app to see that I got notifications (apps like Whatsapp , Facebook messenger ), after that I installed cm 12.1 and 13 also , on both had problems on camera and rebooted every single time I opened Camera app and Wifi/Data change didn't always worked , they are still unstable I suggest you to install OxigenOS with boeffa kernel and try some of those profiles there my phone working way better than before http://forum.xda-developers.com/oneplus-2/general/unofficial-boeffla-kernel-profiles-t3289395 , or if you like custom ROM's what gapps are you using ?
Click to expand...
Click to collapse
Thanks again for your clarification and suggestion!
I used open gapps mini. Used them on every rom. But yesterday i thought to go with OxySlim and the included Boeffla Kernel and yes, works like a charm! No reboots since 14 hours. Eyerything is like it should right now.
Trinaaa said:
Thanks again for your clarification and suggestion!
I used open gapps mini. Used them on every rom. But yesterday i thought to go with OxySlim and the included Boeffla Kernel and yes, works like a charm! No reboots since 14 hours. Eyerything is like it should right now.
Click to expand...
Click to collapse
Glad to help your welcome :good:
hey, i have random reboots and it always happens when I am in another location that is not my home. I thought that it was related to location and wifi but that is not the case. I clean flash and I accidentally wiped out my internal storage. My phone works now but please help
I searched around and couldn't find anyone with a similar issue.
I'm running the most recent Bliss build on my G900T Tmobile S5 using the stock kernel. I've tried (and love) Boeffla's klte kernel for CM13 on both Bliss and stock CM13 (as per his recommendation). On both builds, I encounter the same issues after flashing Boeffla kernel, and I was just wondering if anyone could offer some advice. Both test flashes are completely clean. I've tried flashing the kernel with and without gApps on both ROMs.
When I flash the kernel, I lose all of my pull-down toggles (Wifi, Bluetooth, location, etc), as well at the "gear" icon in the status bar. Additionally, no incoming notifications are displayed in the notification bar from any app, although the notification sound still fires off. I dug through the settings and the options to restore them have disappeared as well.
I also lose Bluetooth functionality and root. I tried to grab a log file to see what was happening, but the Bluetooth Share FC's would not let me do anything in the ROM after a few minutes of being powered on. Bluetooth will work fine for about 30 seconds, then start producing errors from the Bluetooth Share apk. Eventually the seetings toggle itself freezes and only restarting the phone "fixes" it. I tried re-installing root with many different apps (Chainfire's, SuperSU, etc), but to no avail.
For now, I'm back on Bliss with the stock kernel, running smoothly.
If anyone has any suggestions, please let me know! Boeffla Kernel is excellent, and I really miss intellidemand >.>
Thanks!
The Bluetooth issue is from the upstream cm13 code base it came about around 06/06 on the nightlies there are posts scattered throughout all of the builds based on cm13. So far haven't heard of a fix.
Sent from my SM-G900W8 using Tapatalk
went through all the steps properly and no matter what i do i cant get gapps to flash properly. running the latest CM13 and flashed gapps right after flashing CM13, i get to the set up screens, problem is touch screen doesn't properly function. when i hit the next button after choosing language it does respond, it shows a quick drop down from the top (looks like a notifications bar) and a little lock symbol appears on the bottom of the screen....aggravated been working on this for hours, tried multiple gapps and still the same thing, any ideas?
It is not a problem with Gapps, it is CM13 bug. The author is aware and working on it
https://review.cyanogenmod.org/#/c/153720
Hi guys, I had to give up using CM Roms since the phone reboots every time I try making a call or receive one, I understand there is some king of bug with the dialer framework included in the GAPPS package and that installing the Google Dialer from the play store should solve it but in my case i hasn't. This is what I've tried to no avail:
- Intalled Google DIaler from PlayStore/APK and set it default with all the permissions enabled.
- Installed Google Dialer apk as system app and set it default with all the permissions enabled.
- Installed the full GAPPS package.
- Removed the stock dialer and did all things above.
Hope someone can help me out here,
Thanks.
This happens when you have multiple phone dialer apps enabled. To use any other dialer than the included (when you flash Gapps Tiny or Micro which is recommended since the bigger packs replaces the CM app).
If you don't like the CM one, you should still flash a smaller Gapps and then disable CM dialer and download the one you want. If you already flashed a bigger Gapps, you should format system, cache and dalvik/arts partition and then reflash CM and then the smaller Gapps.
Should be enough to go settings, apps, click the gear weel (next to 3 dot menu), choose standard apps from this menu and determine your dailer as standard app..
This is a classical issue..
Sent from my OnePlus2 using XDA Labs
Sam Nakamura said:
Should be enough to go settings, apps, click the gear weel (next to 3 dot menu), choose standard apps from this menu and determine your dailer as standard app..
This is a classical issue..
Sent from my OnePlus2 using XDA Labs
Click to expand...
Click to collapse
Hi Sam, that's what I mean when I've set it as default.
pitrus- said:
This happens when you have multiple phone dialer apps enabled. To use any other dialer than the included (when you flash Gapps Tiny or Micro which is recommended since the bigger packs replaces the CM app).
If you don't like the CM one, you should still flash a smaller Gapps and then disable CM dialer and download the one you want. If you already flashed a bigger Gapps, you should format system, cache and dalvik/arts partition and then reflash CM and then the smaller Gapps.
Click to expand...
Click to collapse
Hey pitrus, this issue actually started while only having CM dialer installed since I mainly flash pico gapps.
Will try it again since its been like a month since I gave up on it. Let you know later.
J3RI3L said:
Hi Sam, that's what I mean when I've set it as default.
Click to expand...
Click to collapse
Well, okay.. Thanks for clarification :good:
Maybe you'd like to give Banks a shot, I think it's worth to try...
https://download.dirtyunicorns.com/gapps/Banks/
I never had this specific problem, only when it wasn't set to be default but a also only use one dailer.. The one that is default on cm based roms..
Sent from my OnePlus2 using XDA Labs
Guys I've had no luck, tried with a clean install of CM14 and still facing the same problem. Just today did a CM14.1 install and it is still present for me.
I guess that I could flash just CM and not gapps but I rely on Google services for a lot of stuff. Will keep trying though.
I'm having the exact same problem, random reboots during calls only, sometimes I don't even have time to answer. I'm running CM13 and only have one phone app, also set as default. When running stock and Cyanogen all was fine, this only started after flashing CM13.
Developemt for Cyanogen stopped that's why I switched, maybe coming from another rom is causing this? I did a full wipe when flashing and have updated to several nightlies and the problem remains. Maybe I'll try another rom and test it for a while.
Installed Dirty Unicorns a few days ago and the problem seemed to have been fixed, but yesterday it started acting out again. Is there a way to check if this problem is hardware related?
I'm now doing a factory reset and installing Oxigen hoping that'll fix this once and for all.
It's a problem related to Gapps
rtorresz said:
Installed Dirty Unicorns a few days ago and the problem seemed to have been fixed, but yesterday it started acting out again. Is there a way to check if this problem is hardware related?
I'm now doing a factory reset and installing Oxigen hoping that'll fix this once and for all.
Click to expand...
Click to collapse
It is not a hardware problem, I don't have this issue when running Oxygen OS, it only happens to me when running any AOSP based rom with Gapps installed.
Flash Oxygen from here http://downloads.oneplus.net/devices/oneplus-2/ and it will fix it, it's not the same as running CM though.
J3RI3L said:
It is not a hardware problem, I don't have this issue when running Oxygen OS, it only happens to me when running any AOSP based rom with Gapps installed.
Flash Oxygen from here http://downloads.oneplus.net/devices/oneplus-2/ and it will fix it, it's not the same as running CM though.
Click to expand...
Click to collapse
Sounds like you flashed the full version of Gapps instead of the recommended Nano or Micro which does not replace the dialer app with Googles own, try the smaller Gapps and you should be ok.
pitrus- said:
Sounds like you flashed the full version of Gapps instead of the recommended Nano or Micro which does not replace the dialer app with Googles own, try the smaller Gapps and you should be ok.
Click to expand...
Click to collapse
I've installed them all with the same result, last time I was using Pico Gapps with Seraph's CM14 and it happened eandomly, sometimes I could make and receive calls normally but a most of the time it would reboot as soon as the phone started ringing.
Currently I've tried a lot of solutions so I'm not really sure of what's wrong.
J3RI3L said:
It is not a hardware problem, I don't have this issue when running Oxygen OS, it only happens to me when running any AOSP based rom with Gapps installed.
Flash Oxygen from here http://downloads.oneplus.net/devices/oneplus-2/ and it will fix it, it's not the same as running CM though.
Click to expand...
Click to collapse
I flashed the latest OOS and now things are only a little bit better, instead of reboots I get dropped calls and a "No available network" message. This seems to happen only when I'm on a 3G or 4G network, if I change to a 2G network I can make calls without problems. This is driving me crazy, I've tried almost everything and I can't see what I'm missing.
rtorresz said:
I flashed the latest OOS and now things are only a little bit better, instead of reboots I get dropped calls and a "No available network" message. This seems to happen only when I'm on a 3G or 4G network, if I change to a 2G network I can make calls without problems. This is driving me crazy, I've tried almost everything and I can't see what I'm missing.
Click to expand...
Click to collapse
Its happening to me as well just as you describe it. It is very weird. In thinking of flashing the stock OOS 2.2.0 just to check whether it makes any diference.
Yesterday I restored my phone back to stock, but the problen remains.
This definitely has something to do with mobile data. If I disconnect mobile data I can make calls without any problem, when I'm connected to a wifi network too (I'm guessing because the phone has no need to use mobile data).
Some suggest that this might be related to VoLTE and operators not supporting it, but I can't find anyway to see if this is even exists or if its activated in OOS.
Later today I'll try Hydrogen and see what happens.
UPDATE: Flashing Hyrogen didn't solve the issue, calls keep dropping when mobile data is activated on LTE network.
UPDATE 2: Going back to OOS 2.2.1 didn't solve the problem either.
Kinda solved now
rtorresz said:
Yesterday I restored my phone back to stock, but the problen remains.
UPDATE: Flashing Hyrogen didn't solve the issue, calls keep dropping when mobile data is activated on LTE network.
UPDATE 2: Going back to OOS 2.2.1 didn't solve the problem either.
Click to expand...
Click to collapse
It seems I have solved my problem with the reboots and I think might help with your droped calls as well.
Firstly I flashed this OOS 3 firmware https://www.androidfilehost.com/?fid=24591020540821656, it comes with a hybrid TWRP, after that flashed the official CM14.1 and pico Open Gapps.
I think the firmware file did the trick or maybe it was the recovery since I haven't had a reboot in the past 2 days when receiving calls or making them.
Hope it helps
It's been a few days since I tried the last solution and so far my problem seems to be solved.
What worked for me was flashing the latest modem from H2OS 2.5 which also is supposed to enable VoLTE, but I can't confirm this since my carrier does not support VoLTE yet. To do this I first flashed CM 14.1 and then the modem, it worked fine since the first boot. Since my battery life wasn't the best in Nougat I went back to CM13 and the phone is still working fine.