Fixes (attempt to fix) mobile radio active bug - https://code.google.com/p/android/issues/detail?id=165558
I applied this fix (http://review.cyanogenmod.org/#/c/98843/) as Xposed module.
This is test version, don't upload it anywhere!. If it fully works, I will upload it to Xposed repo and share source code.
Source code:https://github.com/pylerSM/MobileRadioActiveFix
APK: https://github.com/pylerSM/MobileRadioActiveFix/blob/master/MobileRadioActiveFix.apk?raw=true
@pyler when was this fix merged into cm source? I am running blisspop and my rom development has been halted. This would be useful for me!
I am running BlissPop v3.3 20150524
May 20.
It has been merged on may 17, so it would be merged into my rom I think. And check msg no. #295 on Google issue tracker
----
I don't know if the dates correct or not
---------- Post added at 05:24 PM ---------- Previous post was at 05:17 PM ----------
Going to try this cause yesterday I was traveling and used mobile data all the time and my battery fell short very fast
---------- Post added at 05:31 PM ---------- Previous post was at 05:24 PM ----------
Installed and activated. No bootloops or anything.
Now I Will report if there's any improvement
So if I'm running stock rom, this will improve battery?
This running on 5.1.1?
theSutphin said:
So if I'm running stock rom, this will improve battery?
This running on 5.1.1?
Click to expand...
Click to collapse
Highly unlikely. This has been merged into many ROMs based off CM12.1 and the issue is exactly the same. Looking at Reddit shows this commit hasn't done much if anything to be honest.
This fix comes from Google developers, not from CM.
Thanks! Trying it on...
Thanks a lot!
Trying it on an Xperia Z3 Compact with latest 5.02 update (it was crazy with this bug). I disabled fast dormancy also, which helped me with the previous build, but if the phone starts sleeping I'll let you know. And thanks, amongst thousands crying for help you are the only one stepping up and attempting to fix it, successful or not you deserve kudos!
Testing it too on a Sony Xperia Z3 Compact running Android 5.0.2 on Xposed 3 alpha4.
Tested on my Galaxy Alpha 5.0.2, seem to be working !! Seems no more cell stanby battery drain on battery stats. Thanks for this.
pacorola said:
Thanks a lot!
Trying it on an Xperia Z3 Compact with latest 5.02 update (it was crazy with this bug). I disabled fast dormancy also, which helped me with the previous build, but if the phone starts sleeping I'll let you know. And thanks, amongst thousands crying for help you are the only one stepping up and attempting to fix it, successful or not you deserve kudos!
Click to expand...
Click to collapse
And it seems to be working!!!!
Doesn't seem to work on xperia z1 running 5.0.2
For the most part it seems to be working, since most apps no longer show exhorbitant use of mobile radio. Now I just have 2 rogue apps: Maps (no idea why) and Google Play Services, which I narrowed down to google play newsstand, as in my account's sync preferences it seemed to keep syncing all the time. Disabled it's sync and will report back to see if it results that helps, but I can confirm that after installing the module my phone SLEEPS! Yayy!
It seems not to be working on Xperia ZL Lollipop 5.0.2
Mobile Radio Active is still too long to let phone in deep sleep..
It seems to works well on Samsung Note 3. No more cell standby in battery stats.
Doesn't work
works wonders on my Note 4 (N910C), thank you!
Testing it on a Nexus 5 with stock Android 5.1.1
Possible causes of the mobile radio bug
Thanks for your work!However,it seemed that the module didnt do anything to my phone
SO I did some experiments today...
I think I have found out a possible fix for the mobile radio bug...I disabled all the google play services in the following pics today, then I found that the battery drain of the mobile network reduced a lot, though the mobile radio activate still remained.
HOWEVER, I dont know which is the exact service caused the bug, maybe you guys can figure out that
CAUTIONISABLING THE FOLLOWING LIST OF SERVICES WILL ALSO DISABLE THE RELATIVE GOOGLE SERVICES,IF YOU NEED TO USE THE SERVICE, THEN YOU SHOULD NOT DISABLE IT.
Well,I suddenly find that I cant post outside links so I just TEll you the names.
I just disabled the services with the tags like CAST,APP,KID,GAME,PEOPLE DETAIL,CAR,REPORT,WEARABLE AND THE INDEXSERVICE,INDEXWORKERSERVICE
HOPE MY POST WILL DO SOME HELP TO YOU :victory:
testing with Z2. seems to be working .. will stay more time for testing
Related
This thread is intended for concentrating all the bugs you find in the new L7 II KK stock ROM. This will help the good people here find solutions and/or create better ROMs based on this one
I'll start:
It seems that the notification LED is buggy. LED is lit in yellow when connected to a charger even if battery charging option is disabled. Then when trying to control the LED by enabling "Downloaded apps" with LED control apps such as Light Manager, LED doesn't seem to work properly (as it did in JB).
Mmmm
Hello everybody!
I think that someone experienced in ROMs (Really me not hahaha) need to clean this rom 'cuz there are a lot of things that makes KitKat work laggy or buggy sometimes, we'll appreciate it hahaha
Digdis said:
I'll start:
It seems that the notification LED is buggy. LED is lit in yellow when connected to a charger even if battery charging option is disabled. Then when trying to control the LED by enabling "Downloaded apps" with LED control apps such as Light Manager, LED doesn't seem to work properly (as it did in JB).
Click to expand...
Click to collapse
yes thats true,led is buggy,and when i recieve a notification the led does not notify me of anything.
im using a flsable zip that i created by following a tutorial,my base rom is from v20a europe open kdz file,and everything worlks for me ,except for the led,and for some other people that live in my same city cant make or receive phone calls and with the sms its the same thing.
kalel29 said:
yes thats true,led is buggy,and when i recieve a notification the led does not notify me of anything.
im using a flsable zip that i created by following a tutorial,my base rom is from v20a europe open kdz file,and everything worlks for me ,except for the led,and for some other people that live in my same city cant make or receive phone calls and with the sms its the same thing.
Click to expand...
Click to collapse
For me LED notification light works perfectly fine, though yellow color appears sometime for no reason, but it isn't as annoying as it was on Jelly Bean.
Although, I noticed that stability this ROM offers is rather inferior. I'll start to work on V20a kernel from today, because LG always screws with kernels from my experience.
Good thing that we don't need any porting work.
---------- Post added at 09:31 AM ---------- Previous post was at 09:28 AM ----------
Juaaanchi said:
Hello everybody!
I think that someone experienced in ROMs (Really me not hahaha) need to clean this rom 'cuz there are a lot of things that makes KitKat work laggy or buggy sometimes, we'll appreciate it hahaha
Click to expand...
Click to collapse
Always use third party launcher, like Nova and etc.
Think of this: all things LG included is named as bloatware by my book. So delete them and avoid them.
Regarding the notification led problem, I would like to ask anyone here with p710 to check whether this issue happens there as well. Just wanna make sure this is not a compatibility issue between the p710 rom and the p714 hardware. Otherwise, I really can't understand how LG would release a stock rom with such a fundemental feature not working well.
Digdis said:
Regarding the notification led problem, I would like to ask anyone here with p710 to check whether this issue happens there as well. Just wanna make sure this is not a compatibility issue between the p710 rom and the p714 hardware. Otherwise, I really can't understand how LG would release a stock rom with such a fundemental feature not working well.
Click to expand...
Click to collapse
With some effort, it is possible to fix such problem.
I'll add this to my to-do list.
Hey hey
airidosas252 said:
For me LED notification light works perfectly fine, though yellow color appears sometime for no reason, but it isn't as annoying as it was on Jelly Bean.
Although, I noticed that stability this ROM offers is rather inferior. I'll start to work on V20a kernel from today, because LG always screws with kernels from my experience.
Good thing that we don't need any porting work.
---------- Post added at 09:31 AM ---------- Previous post was at 09:28 AM ----------
Always use third party launcher, like Nova and etc.
Think of this: all things LG included is named as bloatware by my book. So delete them and avoid them.
Click to expand...
Click to collapse
I would be awesome if you try to improve this kernel rom, cuz I agree with you.
Yes, I deleted all the LG things that come, and used Nova Launcher, but it wasn't as smooth as in Jellybean, the transition were laggy. To use KitKat I'll wait for a rom. Thanks for answering me!
My phone is p713 using p710 stock rom. Here is my problem:
1. Open NFC Tap and pay in setting causing force close.
2. lgNfc.apk causing high cpu usage
3. Can't turn on Bluetooth in status bar or quick toggle in setting, sometimes causing bootloop/restart. I can only turn on bluetooth from 'Bluetooth tether' toggle in sub setting.
4. Some language is not available, especially mine Bahasa Indonesia/Indonesian language.
Some news I gathered:
Looks like GPU clock scaling is screwed. Jelly Bean didn't had such problems, and scrolling was smoother than on Kitkat. I will try to add additional GPU clocks and see if such problem would dissapear.
I think I'll drop my compiled kernel link in this thread, if it gives better results, so that anyone could test it.
---------- Post added at 01:42 PM ---------- Previous post was at 01:36 PM ----------
twitah said:
My phone is p713 using p710 stock rom. Here is my problem:
1. Open NFC Tap and pay in setting causing force close.
2. lgNfc.apk causing high cpu usage
3. Can't turn on Bluetooth in status bar or quick toggle in setting, sometimes causing bootloop/restart. I can only turn on bluetooth from 'Bluetooth tether' toggle in sub setting.
4. Some language is not available, especially mine Bahasa Indonesia/Indonesian language.
Click to expand...
Click to collapse
Just delete that lgnfc.apk and high cpu usage will dissapear, if you have root, of course.
RAM managmend is sh**.
It closes Opera mini which still has few MBs.
No apps running in background etc...
Some bad news,
I've succesfully added some additional GPU clocks and is runs a bit better, but the thing is: after compiling the kernel, wi-fi stops working. And no matter, if original or my kernel is running, logcat shows ton of errors about adreno 200.
EDIT:
Found a solution how to bypass vermagic checking. Now WI-FI is Working. Will post kernel here. :>
Just flash it through CWM and you're good to go. :>
Great job, but do you know any ways to have root&cwm without having to flash the whole system again? It would be delightful
shiftyHungary said:
Great job, but do you know any ways to have root&cwm without having to flash the whole system again? It would be delightful
Click to expand...
Click to collapse
I'll look into it.
Anyway, I think it's possible to integrate both su binary and Superuser.apk into the ramdisk. Don't know, if it gonna work, but will try out.
Love having GPU clocked at 400 Mhz and getting Temple Run 2 run smoother.
That would be cool, but right now I'm on stock KK, and cannot reach recovery anyways your work on the kernel is just awesome, I don't know anything about working with kernels.
An idea: maybe you could add some CPU governors like smartassV2, interactiveX, hyper
Microphone Problem
I have a microphone problem. After the V20A update, other person can't hear my voice unless I quickly double touch "Speaker" on the screen.
Actually I had this problem on Jelly Bean as well but on Jelly Bean I was using Soundabout app in which you can disable wired headset microphone detection. On Kitkat, this function doesn't work. A year ago I sent my P710 to warranty because of this problem. They changed motherboard and microphone but the problem is persistent. The fact that I solved this problem in the past by using an app gives me the idea that this problem is related to software not hardware.
So is it only me or are you experiencing this problem as well? Do we have any solution to this? I am really frustrated and considering to buy a new phone guys...
shiftyHungary said:
That would be cool, but right now I'm on stock KK, and cannot reach recovery anyways your work on the kernel is just awesome, I don't know anything about working with kernels.
An idea: maybe you could add some CPU governors like smartassV2, interactiveX, hyper
Click to expand...
Click to collapse
Me neither. I just use some tutorials just to progress further with my kernel project.
I'll quickly add some more governors, since it is not a big deal.
The hardest thing to do was to find how to bypass vermagic checking, but now everything is much easier.
I've succesfully raised kernel version to 3.4.1. Now compiling 3.4.2. :>
---------- Post added at 08:45 AM ---------- Previous post was at 08:42 AM ----------
fcan said:
I have a microphone problem. After the V20A update, other person can't hear my voice unless I quickly double touch "Speaker" on the screen.
Actually I had this problem on Jelly Bean as well but on Jelly Bean I was using Soundabout app in which you can disable wired headset microphone detection. On Kitkat, this function doesn't work. A year ago I sent my P710 to warranty because of this problem. They changed motherboard and microphone but the problem is persistent. The fact that I solved this problem in the past by using an app gives me the idea that this problem is related to software not hardware.
So is it only me or are you experiencing this problem as well? Do we have any solution to this? I am really frustrated and considering to buy a new phone guys...
Click to expand...
Click to collapse
This problem was in Jelly Bean as well. Looks like people got lazy at LG and didn't fix it. Well, we'll look how to fix this.
Update:
I've succesfully upped the kernel version upto 3.4.2 (Android shows 3.4.1, but I've patched with 3.4.2, so don't mind this), Wi-Fi still working strong.
Added Superuser with su binaries to kernel ramdisk. When you flash this kernel, you'll have root (need testing), because mine is already rooted.
I've included full ext4, ntfs support.
NOTE:
We can pronounce this kernel as an alpha version, because much things aren't implemented and some bugs aren't fixed. USE WITH CAUTION!
airidosas252 said:
Update:
I've succesfully upped the kernel version upto 3.4.2 (Android shows 3.4.1, but I've patched with 3.4.2, so don't mind this), Wi-Fi still working strong.
Added Superuser with su binaries to kernel ramdisk. When you flash this kernel, you'll have root (need testing), because mine is already rooted.
I've included full ext4, ntfs support.
NOTE:
We can pronounce this kernel as an alpha version, because much things aren't implemented and some bugs aren't fixed. USE WITH CAUTION!
Click to expand...
Click to collapse
Man - just totally appreciate your work here.
Just to make sure before flashing the kernel - it should work the same for P714 as well, right?
Digdis said:
Man - just totally appreciate your work here.
Just to make sure before flashing the kernel - it should work the same for P714 as well, right?
Click to expand...
Click to collapse
You can try, but I don't know, if it would work.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Device: i605 (Verizon Note 2)
Hey all! I am here to bring you the latest version of AOSPA-Legacy to the Verizon Galaxy Note 2! This is always compiled from the latest AOSPA-Legacy sources compiled with the CyanogenMod kernel. I have added some new features to the AOSPA source, but there are no extra apps in the final build.
NOTICE:
This is an unofficial build that I made for myself that I am sharing with all of you. I have a set use for my phone and therefore cannot test everything. Because of this, your warranty is now void. I am not responsible for any damages this ROM does to your phone, but just know I only upload after testing on my phone. Results may vary. Also, this ROM will be updated when I get around to it. I do not have the infrastructure to build nightlies on this computer (it's a laptop btw), and will only update to add new features/fix bugs, maybe weeklies, haven't decided yet. Perhaps I could become this device's new maintainer since everyone seems to be gone, but I'll get to this later.
Without further hesitation, let's get to it!
INSTRUCTIONS:
MAKE SURE YOUR BOOTLOADER IS UNLOCKED!!
Reboot into either the latest TWRP/Philz Recovery
Wipe Data, Caches, etc.
Install this Rom (Download Below)
Install PA-Gapps
Wipe caches again (eh, why not?)
Reboot
???
PROFIT!
Downloads
AOSPA-Legacy 4.6 Beta 6 (Build date: 11/19/14) --> HERE
(Check Second Post for Changelog and Experimental Builds!)
Get your GApps here! --> THREAD
BUGS
Google Chrome v39 always starts in floating mode (fix in second post!)
I can't seem to get a GPS lock, will definitely look into this
Stock Flashlight app doesn't work, anything from the Play Store does though
Anything else from CM/PA that's been a problem on this phone
You tell me (please!)...
THANKS!
AOSPA-Legacy -- For the amazing ROM and sources (Github)
CyanogenMod -- For the kernel sources (Github)
DreamFX -- For Unofficially/Officially fixing the VA/PA texting issue (NOT RELATED TO THIS ROM! But without this I wouldn't have played with AOSP/CM again!) (Link to fix)
UPDATE:
(Downloads in 1st post!)
(Experimental build downloads are under their build dates)
11/22/2014
Experimental Build! (Should still stable, just need some feedback on these 2 new features) -> Download
Added Dynamic System Bars!!! (You'll find this under Settings->Display)
Added Mobile Network Battery Saver Mode(Automatically switches to 2G Network after the screen is for 30 seconds [unless a music streaming service is active] and sets it back to 3G/4G when the screen is turned on!)
11/19/2014
Added a swipe to switch between Quick Settings and Notifications
Added Quiet Hours
COMING SOON!
The new Card-Based Recent Apps
Gerrit is down but being fixed, so I am not able to cherrypick these two items. Hopefully PA can resolve this soon and they will be added.
GOOGLE CHROME UPDATE: There seems to be an issue with the latest build of Google Chrome (v39) where the app will always start in floating mode. To return to full screen Chrome, clear app data after updating from the Play Store and every time you open Chrome pull up the Recents Menu (default is long press home button) and select Chrome again. It will now be full screen. This seems to be an issue for all of AOSPA.
Another fix is to stay on Chrome v38 and not update. Link To apk
Weird issue after installing
Not sure if it is related to this ROM or not but I had not encountered this previously under any other ROM. Installed this last night - wiped everything with all the normal steps. Also installed the latest PA GAPPS (the link in the first post - installed the Full version). Restored most of my apps with TB and everything went as normal. This morning, the phone, while just sitting on my desk, made a noise (maybe like I got a notification). I picked it up and it was pretty much loading and displaying things from different apps and videos on my phone without any input from me. I could not get it to respond to any button presses and was even having issues trying to power it down until I just pulled the battery. I re-loaded one of my backups from another ROM and everything appears to be back as it was and I've not experienced the same issue at this point. Can't say 100% it was this ROM but thought it better to at least note it.
chameo53 said:
Not sure if it is related to this ROM or not but I had not encountered this previously under any other ROM. Installed this last night - wiped everything with all the normal steps. Also installed the latest PA GAPPS (the link in the first post - installed the Full version). Restored most of my apps with TB and everything went as normal. This morning, the phone, while just sitting on my desk, made a noise (maybe like I got a notification). I picked it up and it was pretty much loading and displaying things from different apps and videos on my phone without any input from me. I could not get it to respond to any button presses and was even having issues trying to power it down until I just pulled the battery. I re-loaded one of my backups from another ROM and everything appears to be back as it was and I've not experienced the same issue at this point. Can't say 100% it was this ROM but thought it better to at least note it.
Click to expand...
Click to collapse
Hmmm...That is a very strange issue indeed! Did you install a custom kernel? Were you running any Xposed Modules? Would you be willing to try this ROM again and report if it happens again? Thanks!
Sent from my Galaxy Note II using XDA Free mobile app
I did not install an alternate kernel- usually I find it pays to stick with the one that came with any ROM I install. AGNi kernel always seemed to give me one problem or another. But I digress. I might try to install again to see if I can replicate but it was a little disconcerting as it looked like it was opening apps and displaying data I had entered - almost like some sort of bot. Don't keep much on the phone of a personal nature and it is no longer a work phone since I retired this summer - mostly a toy of sorts so I just try the various ROMs out there.
Won't get to it tonight but i'll let you know when I re-install.
Sent from my Surface Pro 3 using Tapatalk
---------- Post added at 08:50 PM ---------- Previous post was at 08:46 PM ----------
Sorry - didn't answer your other question. I did install Xposed installer. Only active module I used was Gravity and changed the battery icon and lockscreen background. I also have Greenify and Wanam Kit active but did not actually use either one to modify anything.
Sent from my Surface Pro 3 using Tapatalk
chameo53 said:
I did not install an alternate kernel- usually I find it pays to stick with the one that came with any ROM I install. AGNi kernel always seemed to give me one problem or another. But I digress. I might try to install again to see if I can replicate but it was a little disconcerting as it looked like it was opening apps and displaying data I had entered - almost like some sort of bot. Don't keep much on the phone of a personal nature and it is no longer a work phone since I retired this summer - mostly a toy of sorts so I just try the various ROMs out there.
Won't get to it tonight but i'll let you know when I re-install.
Sent from my Surface Pro 3 using Tapatalk
---------- Post added at 08:50 PM ---------- Previous post was at 08:46 PM ----------
Sorry - didn't answer your other question. I did install Xposed installer. Only active module I used was Gravity and changed the battery icon and lockscreen background. I also have Greenify and Wanam Kit active but did not actually use either one to modify anything.
Sent from my Surface Pro 3 using Tapatalk
Click to expand...
Click to collapse
Well, on my honor, I did not put a bot into this. I'm running the same build I posted and have not had that issue.
Sent from my Galaxy Note II using XDA Free mobile app
Really didn't mean to imply or suggest you did - I was more amazed on what I experienced and was hoping maybe someone else might have some explanation. I think I have installed every Note II ROM that has been out there since I got the phone 2 years ago so I'm not shy in regards to flashing new ones. I appreciate the effort all you developers put into this so again no blame intended.
Sent from my Surface Pro 3 using Tapatalk
chameo53 said:
Really didn't mean to imply or suggest you did - I was more amazed on what I experienced and was hoping maybe someone else might have some explanation. I think I have installed every Note II ROM that has been out there since I got the phone 2 years ago so I'm not shy in regards to flashing new ones. I appreciate the effort all you developers put into this so again no blame intended.
Sent from my Surface Pro 3 using Tapatalk
Click to expand...
Click to collapse
Don't worry about it! I didn't mean to come off as so defensive, I was simply trying to stamp out anymore thoughts of there being a bot.
Has anyone else experienced this issue?
Sent from my Galaxy Note II using XDA Free mobile app
Thanks for adding me to the thanks list. I really appreciate it. Will try out soon. Thanks for this.
Reflashed ROM - No repeat
I did reinstall the ROM last night since I wanted to try to replicate the overall process I followed and I wanted it to sit overnight. I got thru this afternoon without the same problem occurring. I did not activate the Xposed framework so none of the modules were active either. Other than that I re-installed basically all the apps I had installed the initial flash. All went well although I did have the SMS "unable to send issue" happen (it seems to happen every so often after I reflash a new ROM - doesn't seem to be ROM specific) so I ended up following the usual process as outlined by DreamFX and restoring a different ROM. I have consistently found the Unofficial Aokp ROM by apophis9283 to be the most stable ROM for me - I'll try yours again when the next release is out there.
DreamFX said:
Thanks for adding me to the thanks list. I really appreciate it. Will try out soon. Thanks for this.
Click to expand...
Click to collapse
No thank you man! Let me know how it goes!
Sent from my Galaxy Note II using XDA Free mobile app
chameo53 said:
I did reinstall the ROM last night since I wanted to try to replicate the overall process I followed and I wanted it to sit overnight. I got thru this afternoon without the same problem occurring. I did not activate the Xposed framework so none of the modules were active either. Other than that I re-installed basically all the apps I had installed the initial flash. All went well although I did have the SMS "unable to send issue" happen (it seems to happen every so often after I reflash a new ROM - doesn't seem to be ROM specific) so I ended up following the usual process as outlined by DreamFX and restoring a different ROM. I have consistently found the Unofficial Aokp ROM by apophis9283 to be the most stable ROM for me - I'll try yours again when the next release is out there.
Click to expand...
Click to collapse
While testing a few builds I realized the fix for the texting issue wasn't permanent, but it is fixable again. Thank you for trying out this ROM again!
Once Paranoid Android's gerrit is back up (I'm getting 404 errors for everything. :/) I'll cherry pick a few of the new PA features and have a new build up!
Sent from my Galaxy Note II using XDA Free mobile app
This ROM is great. I really like it. Running smooth and fast. So far no problems at all.
Although I'm still on cyanogenmod, it's good to see there's continued development on our device. Great job Dev
rippedwarrior69 said:
This ROM is great. I really like it. Running smooth and fast. So far no problems at all.
Click to expand...
Click to collapse
Glad to hear it! Thanks for trying this out!
Update: There seems to be an issue with the latest build of Google Chrome (v39) where the app will always start in floating mode. To return to full screen Chrome, clear app data after updating from the Play Store and every time you open Chrome pull up the Recents Menu (default is long press home button) and select Chrome again. It will now be full screen. This seems to be an issue for all of AOSPA.
Sent from my Galaxy Note II using XDA Free mobile app
twitish said:
Glad to hear it! Thanks for trying this out!
Update: There seems to be an issue with the latest build of Google Chrome (v39) where the app will always start in floating mode. To return to full screen Chrome, clear app data after updating from the Play Store and every time you open Chrome pull up the Recents Menu (default is long press home button) and select Chrome again. It will now be full screen. This seems to be an issue for all of AOSPA.
Sent from my Galaxy Note II using XDA Free mobile app
Click to expand...
Click to collapse
I'm on Carbon rom until I try yours this weekend. Of course it does this for me and is annoying as hell. It appears to have something to do with all kitkat aosp roms compabilty. My brother is lucky enough to have lollipop and it's not doing this on lollipop.
---------- Post added at 07:54 AM ---------- Previous post was at 07:52 AM ----------
I'm really hoping this rom doesn't have that ok Google crackle that plagues most aosp roms for our device.
DreamFX said:
I'm on Carbon rom until I try yours this weekend. Of course it does this for me and is annoying as hell. It appears to have something to do with all kitkat aosp roms compabilty. My brother is lucky enough to have lollipop and it's not doing this on lollipop.
---------- Post added at 07:54 AM ---------- Previous post was at 07:52 AM ----------
I'm really hoping this rom doesn't have that ok Google crackle that plagues most aosp roms for our device.
Click to expand...
Click to collapse
Unfortunately the Google Now activate tone does "crackle" on this ROM, however when it talks or makes any other sounds it's clear.
Sent from my Galaxy Note II using XDA Free mobile app
twitish said:
Unfortunately the Google Now activate tone does "crackle" on this ROM, however when it talks or makes any other sounds it's clear.
Sent from my Galaxy Note II using XDA Free mobile app
Click to expand...
Click to collapse
Darn that stinks. Thank for confirming.
I am going to try this ROM out. I will let you know if I have any issues. Thank you for giving is another choice.
Thanks for bringing this up for us, very exciting.
I know this is just getting started, the top features I am hoping to see are:
Quiet hours
Profiles
Long press back button to kill
1px battery bar
swipe between notifications/quick settings
Just my wish list for the cherry picks, but everything seems smooth so far!
Q&A for [ROM][LP][5.0.2][UNOFFICIAL]BlissPop v1.8 - Updated 01/23/2015
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.
Before posting, please use the forum search and read through the discussion thread for [ROM][LP][5.0.2][UNOFFICIAL]BlissPop v1.8 - Updated 01/23/2015. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Torch and camera
torch don't work, camera take a shoot will crash
zeronatdo said:
torch don't work, camera take a shoot will crash
Click to expand...
Click to collapse
Torch working for me. Google camera from play store works as a replacement for the broken stock camera.
dandrumheller said:
Torch working for me. Google camera from play store works as a replacement for the broken stock camera.
Click to expand...
Click to collapse
Thanks, i will try :good:
GPS still isn't working
I dirty flashed from 1.8 to 2.0 but the gps still doesn't work.
edit: i used the gps tool box app and actually it works now, but it still takes a long time to lock onto GPS, anyway thanks for this rom!
omgitslink said:
I dirty flashed from 1.8 to 2.0 but the gps still doesn't work.
edit: i used the gps tool box app and actually it works now, but it still takes a long time to lock onto GPS, anyway thanks for this rom!
Click to expand...
Click to collapse
Agreed, GPS locks seem slow. Might be what we are stuck with given the cm12 fix.
Havent been on any other gproj ROMs to compare.
Google camera
Does all functions work in the google camera (panorama, photo sphere and lens blur)? Right now I'm using CM12 official with Solid Kernel and only regular photo and video is working.
ryupunk said:
Does all functions work in the google camera (panorama, photo sphere and lens blur)? Right now I'm using CM12 official with Solid Kernel and only regular photo and video is working.
Click to expand...
Click to collapse
Sure, go and find something not working why don't you.
I hadn't tried any of them. Sphere and pano only show black screens, apparently not working. Lens blur is functional
dandrumheller said:
Sure, go and find something not working why don't you.
I hadn't tried any of them. Sphere and pano only show black screens, apparently not working. Lens blur is functional
Click to expand...
Click to collapse
Actually, that's a problem with all the lollipop roms that I have tried for the e970 (and most of the KK, except for some the MAKO based). Seems that our camera is quite difficult to please....
BTW dandrumheller, it seems that you have tried most of the roms out there for our device, which one did you find more stable? At the time I'm using the official CM12 with Solid Kernel and in my opinion is really good (except for the camera and the bluetooth address, which aren't dealer breakers for me). Thanks.
ryupunk said:
Actually, that's a problem with all the lollipop roms that I have tried for the e970 (and most of the KK, except for some the MAKO based). Seems that our camera is quite difficult to please....
BTW dandrumheller, it seems that you have tried most of the roms out there for our device, which one did you find more stable? At the time I'm using the official CM12 with Solid Kernel and in my opinion is really good (except for the camera and the bluetooth address, which aren't dealer breakers for me). Thanks.
Click to expand...
Click to collapse
I actually haven't tried many of the Lp roms. Candy5 has been the most stable and battery efficient for me. Had some issues with bsod on beanstalk 5.0, though 4.4 versions were excellent. Blisspop has been quite stable, but uninspiring in terms of battery life. My phone hates solid kernel - tons of freeze and crash issues. In general I seem to have better luck with mako based roms. Have not tried CM12 yet.
dandrumheller said:
I actually haven't tried many of the Lp roms. Candy5 has been the most stable and battery efficient for me. Had some issues with bsod on beanstalk 5.0, though 4.4 versions were excellent. Blisspop has been quite stable, but uninspiring in terms of battery life. My phone hates solid kernel - tons of freeze and crash issues. In general I seem to have better luck with mako based roms. Have not tried CM12 yet.
Click to expand...
Click to collapse
Cool. I might try Candy5 and see how it goes. Thanks for you answers!
I'm having an issue where the contact names aren't showing up in the stock messenger, or gosms (haven't tried at other). The full number shows, but never the names. I've tried clearing caches and data on contacts and messengers. Tried resyncing the contacts from Google. I've double checked the privacy guard settings. Basically, I've searched around and tried everything I can think of, but still no luck! So I figured I'd ask the experts! Any ideas???
Ive noticed a few other minor issues. ...
I've had the problem with not being able to move the download, as someone mentioned above. Ive had to connect to PC, transfer from phones internal storage to the PC, then back to EXT SD card in the phone.
The 2/13 build does seem to be a little harder on the battery, and runs a lil warm (also mentioned above). I haven't had any crashing issues, but can feel the temp difference over the average.
Possibley related to the heat and battery issues; I noticed that there are two interfaces for the CPU/GPU clocking and scheduling, under the Performance section of System Settings. Maybe there's a conflict happening there? From memory, I don't remember the "Device Control" section being there in the previous build. It seems redundant to have both. Although Device Settings is much more robust, and I would prefer it be integrated instead of keeping the old, minimal interface. Some adjustments to Device Settings, while disabling the other minimal settings on boot, seems to have helped with heat and battery drain a little bit.
No problems with GPS, that I've noticed
Titanium Backup v6 has problem gaining root access in all cm12 ROMs I've tried. To fix, go to Titanium BU Preferences, scroll to bottom, select Troubleshoot Options (or something like that), and highlight/select the option to force the app to use the SYSTEM busybox, not the one baked into Titanium BU. Restart the app, and root works. Also worth mentioning is that you may have to enable root access under Developer Options in System Settings before any app can gain root. Otherwise, no issues with root, or Super SU.
Hi,
After using Beanstalk 4.4 for several months, finally I tried first LP based ROM BlissPop...so far it seem good, only couple of crashes in last week, few issues are present that are highlighted already (like camera panorama not working...battery life affected).
Since last couple days, the strange issue is being encountered, when i get a call, phone rings but there is no interface to receive the call, i then have to go to call screen and there it says "return to the active call" when i click, i get to the screen where i can receive the call. This started happening without any updates so not sure what caused it? I even tried latest version of ROM but same issue present.
Any ideas?
P.S: thanks to everybody who contributes to this excellent site, i have been a regular reader of the site but got to post something today for the first time.
dandrumheller said:
I actually haven't tried many of the Lp roms. Candy5 has been the most stable and battery efficient for me. Had some issues with bsod on beanstalk 5.0, though 4.4 versions were excellent. Blisspop has been quite stable, but uninspiring in terms of battery life. My phone hates solid kernel - tons of freeze and crash issues. In general I seem to have better luck with mako based roms. Have not tried CM12 yet.
Click to expand...
Click to collapse
---------- Post added at 07:35 AM ---------- Previous post was at 06:49 AM ----------
Okay, it turned out to be a feature that some one must have activated on my cell (my little kiddo likes to tinker with my cell)
In App Notification section, Dialer was blocked and that was causing it to not show up whenever i got a call.
Its working great now
idreamido said:
Hi,
After using Beanstalk 4.4 for several months, finally I tried first LP based ROM BlissPop...so far it seem good, only couple of crashes in last week, few issues are present that are highlighted already (like camera panorama not working...battery life affected).
Since last couple days, the strange issue is being encountered, when i get a call, phone rings but there is no interface to receive the call, i then have to go to call screen and there it says "return to the active call" when i click, i get to the screen where i can receive the call. This started happening without any updates so not sure what caused it? I even tried latest version of ROM but same issue present.
Any ideas?
P.S: thanks to everybody who contributes to this excellent site, i have been a regular reader of the site but got to post something today for the first time.
Click to expand...
Click to collapse
system control issue
I went through all 9 pages of the thread and didnt notice anyone else having this issue. In 2.2 under performance and then system control app when one goes to features and then vibration intensity it just force closes on me...is anyone else having this issue? Any suggestions on what I can do to fix?
So I'd like to see what was being discussed in the normal thread for this great rom but the following link isn't working and since I'm a forum baby I'm not allowed to post in the grownup thread... Can anyone help me out with this? Does anyone check this side of the thread?
http://click.xda-developers.com/api...ww.reddit.com/r/oneplus/comm...updateservice/
---------- Post added at 10:43 PM ---------- Previous post was at 10:39 PM ----------
Also, the last build(the one before latest) ... The vibration control in performance>device control was fixed and working.... In the latest build it's broken once again and force closing every time I select it. Just wanted to mention in case no one is aware of it.
So if 4.8.15 is the latest build why does the ota update app found in the app drawer ask me to update to the latest version so my configuration will be appropriate for ota updates? Is there something specific I have to do in order for that feature to work properly?
Lol is this thing on?
In the latest build, was the performance tab in settings cut out of the build?
---------- Post added at 02:40 PM ---------- Previous post was at 02:33 PM ----------
MitchRapp01 said:
In the latest build, was the performance tab in settings cut out of the build?
Click to expand...
Click to collapse
It contained the free app that allowed you to do all kinds of different things with the phone...I forget what it was called....I know part of the file name was x.nameless rom.com
You can try kenvinjoa kernel or nitro kernel
Does this build allow encryption?
I did the whole manual update to Lollipop, unfortunately, my phone keeps searching for GPS when I use apps that need it.
The problem is I like to use a boating app, and I go far enough offshore that I do not get data. Btw, I get this issue with any app that needs GPS, including Pokemon Go!
After searching online, it appears to be a bug in Lollipop itself.
Either downgrade, of go to Marshmallow if I can find a decent daily driver.
Anyone else have similar issue?
leroadrunner said:
I did the whole manual update to Lollipop, unfortunately, my phone keeps searching for GPS when I use apps that need it.
The problem is I like to use a boating app, and I go far enough offshore that I do not get data. Btw, I get this issue with any app that needs GPS, including Pokemon Go!
After searching online, it appears to be a bug in Lollipop itself.
Either downgrade, of go to Marshmallow if I can find a decent daily driver.
Anyone else have similar issue?
Click to expand...
Click to collapse
My Mate2 did the same thing...mostly after google updated a bunch of stuff. Just started doing it about a month or so ago.
Haven't touched it (all stock) in about a week. Got my new Mate8 about 4 days ago
"Searching for GPS" bug, might need to downgrade to KitKat
Try this:
http://forum.xda-developers.com/showthread.php?p=68572626
See post 35!
More details of my experience in that thread. Wife just pre-ordered an iPhone 7, probably out of pity, for me. One day I showed her my Google Maps and set it to drive home. No sound, no directions, but it quickly discerned origin and route home, when we got home it said "you have arrived," but the map, even though the pointer updated position throughout the drive, still showed the route line from the origin!
Sent from my iPad using Tapatalk
I've never had this issue on any ROM
Found a workaround
I was experiencing exactly the same issue! Not only that but it seems like this issue has popped up on reddit and latest amazon reviews too. Seems to have started occurring after July of this year for many people. I haven't determined the root cause, but it seems like it's affecting too many people to be a hardware issue. Some things I tried that DIDN'T work:
* Flashed latest Cyanogen snapshot, although I like it a lot more than stock
* Tweaked the /system/etc/gps.conf file for my region
Finally I found that my phone time significantly drifted off atomic time, noticed it could be a whole second off. After reading online about GPS technology, it seems having an accurate client atomic time should improve GPS performance. I used an app called ClockSync (with root is easier) to make sure my time was accurate and turned off syncing time with cell tower. It worked!! Using a GPS testing app (GPS Status & Toolbox) I can lock on to my position reliably in < 10 seconds. This is still running on Cyanogen.
I'm in love with this phone, so happy I don't have to buy a new one.
fenwaysnow said:
I was experiencing exactly the same issue! Not only that but it seems like this issue has popped up on reddit and latest amazon reviews too. Seems to have started occurring after July of this year for many people. I haven't determined the root cause, but it seems like it's affecting too many people to be a hardware issue. Some things I tried that DIDN'T work:
* Flashed latest Cyanogen snapshot, although I like it a lot more than stock
* Tweaked the /system/etc/gps.conf file for my region
Finally I found that my phone time significantly drifted off atomic time, noticed it could be a whole second off. After reading online about GPS technology, it seems having an accurate client atomic time should improve GPS performance. I used an app called ClockSync (with root is easier) to make sure my time was accurate and turned off syncing time with cell tower. It worked!! Using a GPS testing app (GPS Status & Toolbox) I can lock on to my position reliably in < 10 seconds. This is still running on Cyanogen.
I'm in love with this phone, so happy I don't have to buy a new one.
Click to expand...
Click to collapse
I tried to install CM13. I failed miserably. Then I started by playing the Pokémon Go game and observing the erratic character movement. Then played with the GPS settings. Turning off High Accuracy and leaving on Device Only still is working, except inside structures that block GPS signal. Tried High Accuracy while visiting San Francisco this last weekend and started having issues there, so back to Device Only for me.
Thank you for sharing what has worked for you!!!!
Sent from my MT2L03 using Tapatalk
I found the latest Cyanogen snapshot I tried (cm-13.0-20160823-SNAPSHOT-ZNH5YAO0M5-mt2) too unstable. I started to experience random reboots every day, even while using Google maps turn-by-turn navigation. Restored back to official lollipop build (MT2-L03C00B322) from my backup (that was factory restored before backing up). Now it's suddenly working without any workarounds! I have no idea why it's working now. If you are considering dumping your phone for a new one, you could try a factory reset first to make sure it's not a hardware issue. :/
---------- Post added at 05:26 AM ---------- Previous post was at 05:19 AM ----------
jzchen said:
I tried to install CM13. I failed miserably.
Click to expand...
Click to collapse
It was definitely not straightforward, I ran into several issues. First, TWRP recovery was complaining about invalid file system format so I switched to Cyanogen recovery to flash system. Second, I was getting constant Google services has crashed messages. Found out I needed to install it right after, before rebooting first. Third, I was stuck in boot-loop during Cyanogen startup. A hard reset finally fixed it.
fenwaysnow said:
I found the latest Cyanogen snapshot I tried (cm-13.0-20160823-SNAPSHOT-ZNH5YAO0M5-mt2) too unstable. I started to experience random reboots every day, even while using Google maps turn-by-turn navigation. Restored back to official lollipop build (MT2-L03C00B322) from my backup (that was factory restored before backing up). Now it's suddenly working without any workarounds! I have no idea why it's working now. If you are considering dumping your phone for a new one, you could try a factory reset first to make sure it's not a hardware issue. :/
---------- Post added at 05:26 AM ---------- Previous post was at 05:19 AM ----------
It was definitely not straightforward, I ran into several issues. First, TWRP recovery was complaining about invalid file system format so I switched to Cyanogen recovery to flash system. Second, I was getting constant Google services has crashed messages. Found out I needed to install it right after, before rebooting first. Third, I was stuck in boot-loop during Cyanogen startup. A hard reset finally fixed it.
Click to expand...
Click to collapse
That's a lot to deal with!!!
As of yesterday I am back to High Accuracy, and just as you note everything seems fine, particularly with regards to GPS.
I guess if I want to have Android 7, I'll save up for a phone that comes with it, unless I learn how to manually do it myself. (I was once a CECS major, about 16 years ago...)
Thank you again for sharing your experience! I hope we can all go back to enjoying our exceptionally large screens....
Sent from my MT2L03 using Tapatalk
Hi guys
I have an issue where my accessibility apps keep turning themselves off all the time, anyone has experienced anything similar or know why this would be happening??
Screenshot uploaded
I have the same problem with fluid N.G, it worked great for a long time and now keeps turning off few times a day
With 182 I have not seen any issues. Fluid is working perfectly. Had many issues with previous updates.
Sent from my LYA-L29 using Tapatalk
I have the same issue. My Huawei Mate 20 Pro (EMUI 9.0), keep switching off the accessibility service. I have tried a few solutions that I've found on the internet, but it has not helped. I hope someone has a solution. As it is I can't use many of my apps like Universal Copy or Type Machine. Incredible frustrating!
Thank you in advance for any help.
Same issue her cant find a solution yet
---------- Post added at 07:41 PM ---------- Previous post was at 07:36 PM ----------
I think I find a solution.
- in battery optimizations change settings to manual an allow all settings
- in optimizations settings dont allow application to battery optimization
- in recent applications lock application so it cant be closed
Anybowdy found solution? Services switches off as soon as running app closes. Every time I close app I have to go in accessibility settings