Hi!
Sorry for posting here, but as newby I'm not allowed to post in development section.
I have an P936 which runs fine with PAC-ROM. I only get a reset sometimes, but no BSODs. The only problem for me is that bluetooth doesn't run well. I can connect to my car hands free, but disconnecting and reconnecting doesn't work well. Sometimes I have to reboot the phone to get it reconnected.
It worked fine with WIND-kernel 1.91 but not with 2.X nor stock kernel. With the latest PAC versions (it started in May) I get a bluescreen when I flash WIND kernel 1.91, I can only use kernel 2.X.
I have now flashed CM 10.1.0 stable and it works well with Wind kernel 1.91 besides a short blue "flashing" between LG and CM boot logo. BT works well again, no problems with dis- or reconnecting.
So, as I would like to use PAC-ROM again, how can I get WIND-kernel 1.91 run with it? Or is it possible, to get the BT functionality back to kernel 2.X?
BT problem solved?!
meister61 said:
Hi!
Sorry for posting here, but as newby I'm not allowed to post in development section.
I have an P936 which runs fine with PAC-ROM. I only get a reset sometimes, but no BSODs. The only problem for me is that bluetooth doesn't run well. I can connect to my car hands free, but disconnecting and reconnecting doesn't work well. Sometimes I have to reboot the phone to get it reconnected.
It worked fine with WIND-kernel 1.91 but not with 2.X nor stock kernel. With the latest PAC versions (it started in May) I get a bluescreen when I flash WIND kernel 1.91, I can only use kernel 2.X.
I have now flashed CM 10.1.0 stable and it works well with Wind kernel 1.91 besides a short blue "flashing" between LG and CM boot logo. BT works well again, no problems with dis- or reconnecting.
So, as I would like to use PAC-ROM again, how can I get WIND-kernel 1.91 run with it? Or is it possible, to get the BT functionality back to kernel 2.X?
Click to expand...
Click to collapse
Today I could install WIND 1.91 with latest PAC and only get the short blue flash before PAC-logo. Fine! Must be the changes in CM 10.1?
The causes of short blue screen or black/blue screen forever is due to the display driver changes in kernel AND rom.
It is always suggested to use latest cm + kernel.
Otherwise not guarantee it works well.
I dont use BT.
I think BT in wind kernel should work as same as CM.
Sent from my LG-SU640 using xda premium
lyfkevin said:
The causes of short blue screen or black/blue screen forever is due to the display driver changes in kernel AND rom.
It is always suggested to use latest cm + kernel.
Otherwise not guarantee it works well.
I dont use BT.
I think BT in wind kernel should work as same as CM.
Sent from my LG-SU640 using xda premium
Click to expand...
Click to collapse
Hi Lyfkevin!
Thanks for answering. The point is that I need BT for hands-free in my car. You changed BT from 1.91 to 2.X to CM-Mode, but 1.91 is the only version that works without problems for me. In all other kernels (CM or WIND) I have problems to disconnect and reconnect.
But since CM 10.1 (and new PAC) 1.91 works again without blue screen. I had two resets (UI) in five minutes yesterday, but after that there was no reset nor BSOD or force close apps. I changed to 432/1458Mhz and badass/sio again as I had before kernel 2.X and battery was at 53% after 12 hours with some heavy testing yesterday
meister61 said:
Hi Lyfkevin!
Thanks for answering. The point is that I need BT for hands-free in my car. You changed BT from 1.91 to 2.X to CM-Mode, but 1.91 is the only version that works without problems for me. In all other kernels (CM or WIND) I have problems to disconnect and reconnect.
But since CM 10.1 (and new PAC) 1.91 works again without blue screen. I had two resets (UI) in five minutes yesterday, but after that there was no reset nor BSOD or force close apps. I changed to 432/1458Mhz and badass/sio again as I had before kernel 2.X and battery was at 53% after 12 hours with some heavy testing yesterday
Click to expand...
Click to collapse
I will consider rolling back to 1.91 BT driver.
P.S. Badass is an awesome governor (3 phase) for non-gaming uses.
lyfkevin said:
I will consider rolling back to 1.91 BT driver.
P.S. Badass is an awesome governor (3 phase) for non-gaming uses.
Click to expand...
Click to collapse
2.X with 1.91 BT driver could be great, thanks!
Today I went on testing after installing PAC-nightly p930 20130628: booting with that short blue "flash", everything went fine. Turning device horizontically/vertically when watching video resulted in crashes and two UI-resets. Changing "debug.compositon.type" to "c2d" and "debug.mdpcomp.maxlayer" to"2" in build.prop helped, no more crashes nor resets since then. Nearly four hours with watching video (and turning!), BT, GPS, Wifi. data testing, gaming a bit, benchmarking (Antutu, about 10% less performance than before) with brightness set to 25% - battery has 60% left. I think it's okay for that heavy use?!
It looks like I have found my stable daily use ROM and kernel!
meister61 said:
2.X with 1.91 BT driver could be great, thanks!
Today I went on testing after installing PAC-nightly p930 20130628: booting with that short blue "flash", everything went fine. Turning device horizontically/vertically when watching video resulted in crashes and two UI-resets. Changing "debug.compositon.type" to "c2d" and "debug.mdpcomp.maxlayer" to"2" in build.prop helped, no more crashes nor resets since then. Nearly four hours with watching video (and turning!), BT, GPS, Wifi. data testing, gaming a bit, benchmarking (Antutu, about 10% less performance than before) with brightness set to 25% - battery has 60% left. I think it's okay for that heavy use?!
It looks like I have found my stable daily use ROM and kernel!
Click to expand...
Click to collapse
Thanks for your info, I have some problem in 2.X too, but not in BT, my systemUI always can't load on reboots after 2.X . It was find in 1.X , If 1.9 is OK for CM 10.1 stable /PAC .I think I should have a try on this
Sent from my Nexus 7 using xda app-developers app
Hi @meister61
Thanks for supporting.
Check this out. Hope it helps
http://forum.xda-developers.com/showpost.php?p=43071295&postcount=648
Hi lyfkevin!
BT works flawlessly. I tried with car hands-free an laptop, connect/disconnect/reconnect directly. Great job!
When installing 2.41 first I got stuck in PAC bootlogo. Pac ran and ran and ran for about ten minutes, then I decided to reset. Second boot the same and even booting in CWM and installing 1.91 didn't work. So I decided to restore the backup I took just before installing 2.41 (yes, I'm a good guy!) abd I could boot again. I installed 2.41 again and this time I didn't set "fix permissions" in CWM. Then everything went fine! Is it possible that this was the problem? I always used to do that before...
I left the settings badass/sio and 432/1458 and the for four hours now there was no remarkable issue! Maybe I'll test other settings when I'm sure that this works stable und look after power consumption and stability.
Thanks for your great work!
Related
I have a KF, my wife uses it with CM7 and loves it.
I see that there are now stable ICS versions, and reading through various threads, I'm considering the [ROM][4/29/12] AOKP KF Edition Milestone 5. I have AOKP on my Samsung phone and really like it.
Anyone have any experience with it?
Also does it contain the newest kernel everyone is talking about, v.3, or does that have to be installed separately?
Funny, I went from from TWRP to KF a month ago as I figured that's the way everyone was going, and there was the new touch version. Now it seems I have to go back to TWRP in order to install this ROM.
I'm using it right now. It seems stable to me! I haven't ran into any problems so far. Mounting and AC charging work fine (though the battery animation didn't show it on the notification bar, the LED light shows it normally). And to properly switch off you have hold the power button rather than shutdown through the OS.
I'm reading, browsing and redditing perfectly smoothly.
Works awesome! It's the first ROM I've tried that JustWorks(c)
I was having issues with several others, and from install to boot to configure everything went smoothly.
I followed these instructions:
http://forum.xda-developers.com/showpost.php?p=25513300&postcount=341
Thanks to all involved!
spaceindaver said:
I'm using it right now. It seems stable to me! I haven't ran into any problems so far. Mounting and AC charging work fine (though the battery animation didn't show it on the notification bar, the LED light shows it normally). And to properly switch off you have hold the power button rather than shutdown through the OS.
I'm reading, browsing and redditing perfectly smoothly.
Click to expand...
Click to collapse
Are you having any WiFi connecting problems? I am using gedeROM and wifi disconnects every 10 minutes and then I have to go back into settings for it to connect again so I was wondering if there were any similar issues with AOKP.
veeman said:
Are you having any WiFi connecting problems? I am using gedeROM and wifi disconnects every 10 minutes and then I have to go back into settings for it to connect again so I was wondering if there were any similar issues with AOKP.
Click to expand...
Click to collapse
I had the gede and it had wifi problems.
AOKP wifi works flawlessly for me.
I just flashed it today coming from gedesrom and I am very impressed. Better battery life and it charges on the AC charger faster. I do run into a few trebuchet force closes every now and then, but for the most part I'd say its the most stable.
harry_fine said:
Anyone have any experience with it?
Click to expand...
Click to collapse
Yup! I got on board with the previous version, build 34, which did not contain the latest Hashcode kernel, but it was no problem flashing it on top. Worked pretty good.
And I just flashed this new version, Milestone 5, on top of the previous build without wiping data (just cache/dalvik). Works like a charm.
Also does it contain the newest kernel everyone is talking about, v.3, or does that have to be installed separately?
Click to expand...
Click to collapse
Yes. Milestone 5 has the absolutely latest Hashcode kernel, and it runs very smooth. And I like some of the tweeks and custom options in this ROM.
I have not had any crashes or problems so far. Recommended.
I've tried both gedeROM and AOKP milestone 5. Both work great, but gedeROM seemed to have cleaner graphics, AOKPs icons in the notification area seemed funky. They would overlap or be off on one side.
One more thing, and this could be more of a kernel issue, is that the Hulu app gives a "Device not supported" error for both of those ROM. Hulu did work with CM7.
Sent from my HTC Sensation Z710e using Tapatalk 2
Nope, never had a problem with Wi-Fi on either aokp or reloaded.
I've done loads of searching here, heard about the *#0011# and switching Power Saving mode off, which doesn't apply to AOSP/CM based ROMs, and tons of beating my head against the wall for the past few weeks. I have "keep WiFi awake when screen off" set to "Always." I tried setting my frequency to both 2.4ghz and 5ghz only with no luck. I have tried the stock CM kernel, ktoonsez's Kernel, Lean Kernel with none of them changing anything. I have tried an array of ROMs, including CM10 stable, CM10 nightlies, Task's AOKP, Slim, LiquidSmooth, ... the list goes on.
Long story short: my WiFi will occasionally drop connection to the network and not come back up until I turn off and turn on the WiFi again. If it drops and I go into the list of signals I get, it seems to pick up the network and have decent strength, but it will not reconnect and just says "Saved" underneath the record. How long it takes before it drops ranges anywhere from a few hours to a few seconds. It does seem to happen more often than not with low signals to the router, but I've been in the same room as a router with full bars and it will still happen. I've tried different routers, different router configurations, and different networks entirely, same deal. It does not affect my cell data, just my WiFi.
I am currently trying a stock ROM to see if it happens on stock, and so far it has not occurred. I have done full wipes of all data and clean installing a new ROM, I have tried installing stock and then dirty installing to a new ROM. Nothing seems to solve the problem. I ran a logcat when the problem occurred (lost the log, sorry) and the entry from wpa_supplicant was "AP scan failed". I am at my wits end here. Has anyone had the same problem and found a solution? None of the solutions I've found so far have seemed to work.
Edit:
Stock ROM seemed to have stable WiFi.
Completely formatted phone back to virgin stock, rerooted, installed CWM instead of TWRP (really don't think this would have a difference), factory reset, wiped data, wiped system AGAIN, wiped cache, wiped davlik, installed Task650's AOKP. WiFi seems stable again. Maybe his kernel? Maybe something during wipe? Maybe CWM vs TWRP (unlikely)? I'm unsure if the problem is even solved, honestly, but so far it seems stable. Will keep this updated. I'm going to start installing apps (not from Titanium backup this time) one at a time...
oscooter said:
I've done loads of searching here, heard about the *#0011# and switching Power Saving mode off, which doesn't apply to AOSP/CM based ROMs, and tons of beating my head against the wall for the past few weeks. I have "keep WiFi awake when screen off" set to "Always." I tried setting my frequency to both 2.4ghz and 5ghz only with no luck. I have tried the stock CM kernel, ktoonsez's Kernel, Lean Kernel with none of them changing anything. I have tried an array of ROMs, including CM10 stable, CM10 nightlies, Task's AOKP, Slim, LiquidSmooth, ... the list goes on.
Long story short: my WiFi will occasionally drop connection to the network and not come back up until I turn off and turn on the WiFi again. If it drops and I go into the list of signals I get, it seems to pick up the network and have decent strength, but it will not reconnect and just says "Saved" underneath the record. How long it takes before it drops ranges anywhere from a few hours to a few seconds. It does seem to happen more often than not with low signals to the router, but I've been in the same room as a router with full bars and it will still happen. I've tried different routers, different router configurations, and different networks entirely, same deal. It does not affect my cell data, just my WiFi.
I am currently trying a stock ROM to see if it happens on stock, and so far it has not occurred. I have done full wipes of all data and clean installing a new ROM, I have tried installing stock and then dirty installing to a new ROM. Nothing seems to solve the problem. I ran a logcat when the problem occurred (lost the log, sorry) and the entry from wpa_supplicant was "AP scan failed". I am at my wits end here. Has anyone had the same problem and found a solution? None of the solutions I've found so far have seemed to work.
Edit:
Stock ROM seemed to have stable WiFi.
Completely formatted phone back to virgin stock, rerooted, installed CWM instead of TWRP (really don't think this would have a difference), factory reset, wiped data, wiped system AGAIN, wiped cache, wiped davlik, installed Task650's AOKP. WiFi seems stable again. Maybe his kernel? Maybe something during wipe? Maybe CWM vs TWRP (unlikely)? I'm unsure if the problem is even solved, honestly, but so far it seems stable. Will keep this updated. I'm going to start installing apps (not from Titanium backup this time) one at a time...
Click to expand...
Click to collapse
I've had the same issue with all AOSP based roms. There seems to be an issue with cm 10 which is the base for all AOSP and aokp roms. The touch wiz roms I've tried have no issues and you can go into settings and disable wifi sleep with them.
ak29 said:
I've had the same issue with all AOSP based roms. There seems to be an issue with cm 10 which is the base for all AOSP and aokp roms. The touch wiz roms I've tried have no issues and you can go into settings and disable wifi sleep with them.
Click to expand...
Click to collapse
That's a shame, but I suppose at least I'm not an isolated case. I didn't figure I was considering I could find other people posting about it, but all the posts seem old and never got much attention. So far task650's AOKP seems fairly stable. I haven't had it drop out on me at home yet, though the WiFi does seem to have difficulty coming up after a boot. I suppose worst case scenario I could switch to a TW ROM, but I really like the AOSP experience better :\ (minus TW's camera)
oscooter said:
That's a shame, but I suppose at least I'm not an isolated case. I didn't figure I was considering I could find other people posting about it, but all the posts seem old and never got much attention. So far task650's AOKP seems fairly stable. I haven't had it drop out on me at home yet, though the WiFi does seem to have difficulty coming up after a boot. I suppose worst case scenario I could switch to a TW ROM, but I really like the AOSP experience better :\ (minus TW's camera)
Click to expand...
Click to collapse
In addition to having wifi issues I found all the AOSP/AOKP based roms to have screen wake issues. The camera on non touch wiz based roms is also considerably slower. For now I'm sticking with the stock virgin rom - rooted with toggle mod installed. Wifi on the AOSP/AOKP based roms seems to disable when I go to bed. Then I have disable and enable for it to reconnect. I've tried 10+ roms still haven't found that was stable with the features I want. The only I didn't try was flashing a new kernel. Maybe that will solve both the wifi and screen wake issues. I would rather the rom be stable than have tons of features and being buggy.
ak29 said:
In addition to having wifi issues I found all the AOSP/AOKP based roms to have screen wake issues. The camera on non touch wiz based roms is also considerably slower. For now I'm sticking with the stock virgin rom - rooted with toggle mod installed. Wifi on the AOSP/AOKP based roms seems to disable when I go to bed. Then I have disable and enable for it to reconnect. I've tried 10+ roms still haven't found that was stable with the features I want. The only I didn't try was flashing a new kernel. Maybe that will solve both the wifi and screen wake issues. I would rather the rom be stable than have tons of features and being buggy.
Click to expand...
Click to collapse
If you are interested in running an AOSP/AOKP ROM still, give Task650's AOKP a try. After a fresh wipe, to virgin stock, to rooted stock, wipe, and then to his ROM, it seems stable. I haven't had a WiFi drop for about 24 hrs, and it seems stable. I did have some WiFi problems on the first boot or two (WiFi wouldn't be on at boot and a tad stubborn to come on, stable after it came on), but that seems to have solved itself now... I say seem though, because like I said in my OP it can sometimes take hours to drop WiFi. He does use a kernel that isn't the CM10 kernel, so maybe that has something to do with it?
I'm loading my apps back on in waves to try and see if maybe it's an app. So far it's still stable.. I'm about to start downloading all my Spotify playlists which it typically would **** out on, so we'll see. If it starts again I'll be going back to stock.
oscooter said:
If you are interested in running an AOSP/AOKP ROM still, give Task650's AOKP a try. After a fresh wipe, to virgin stock, to rooted stock, wipe, and then to his ROM, it seems stable. I haven't had a WiFi drop for about 24 hrs, and it seems stable. I did have some WiFi problems on the first boot or two (WiFi wouldn't be on at boot and a tad stubborn to come on, stable after it came on), but that seems to have solved itself now... I say seem though, because like I said in my OP it can sometimes take hours to drop WiFi. He does use a kernel that isn't the CM10 kernel, so maybe that has something to do with it?
I'm loading my apps back on in waves to try and see if maybe it's an app. So far it's still stable.. I'm about to start downloading all my Spotify playlists which it typically would **** out on, so we'll see. If it starts again I'll be going back to stock.
Click to expand...
Click to collapse
I did give that rom a try. I had the same wifi issue when I went to bed. It also happens after the phone is rebooted. In addition I was getting the screen wake issue. Task's rom is still based on cm 10 so will have the same bugs. Maybe changing the kernel to task's own kernel or the other AOSP kernel. I'll give a try one of these days. Let me know how that works out for you.
Do you guys having this problem have "Avoid poor connections" checked in the Wifi advanced settings? I don't remember if CM10 has this, but AOKP does. I expected that this setting would cause the phone to switch to a better AP if the signal was low but it seems like it just stops Wifi data completely. After disabling this setting I haven't had any issues.
I've been running CM10 nightlies with the CM10 kernel since late November and haven't had any issues with WiFi. I am on my 2nd GS3, first one returned due to phone speaker (not the speakerphone on the back) and on that one my WiFi was sketchy. Not sure if it was a hardware problem, or CM10 merged a fix close to when I swapped out devices. Either way, I use the latest twrp recovery flashed from GooManager and Formula84 10/12 Gapps. I update daily with the CM Updater, and haven't had any issues other than what is already reported to be a bug on CM (which in all reality is, nothing, since I NEVER use Bluetooth)
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
I'm only asking for reference, this happened to me somewhat on CM10, and my roommate on his Stock GS3. Anyone with these issues using a Netgear router? We dumped ours for an Asus and haven't seen a problem since. I hate netgear so much...
goodtimes50 said:
Do you guys having this problem have "Avoid poor connections" checked in the Wifi advanced settings? I don't remember if CM10 has this, but AOKP does. I expected that this setting would cause the phone to switch to a better AP if the signal was low but it seems like it just stops Wifi data completely. After disabling this setting I haven't had any issues.
Click to expand...
Click to collapse
Avoid poor connections is always unchecked for me. I also make sure wifi is set to never sleep.
---------- Post added at 11:35 PM ---------- Previous post was at 11:33 PM ----------
thacounty said:
I'm only asking for reference, this happened to me somewhat on CM10, and my roommate on his Stock GS3. Anyone with these issues using a Netgear router? We dumped ours for an Asus and haven't seen a problem since. I hate netgear so much...
Click to expand...
Click to collapse
I'm using the linksys e4200v2 router. Never had any issues with any of my devices except after I flash AOSP/AOKP based roms. I have 8 devices connected wirelessly with no issues.
My router at home is a Netgear. Not sure about work. The weird part for me is that I didn't use to have these problems with AOSP ROMs, not that I remember anyways. It seems like a recent development in the past few weeks.
Still having decent luck with task650's ROM. It did happen to me once last night at home but it's been stable as a rock otherwise. If it starts happening more I'm gonna flash stock. If it continues to happen from there I'll consider it a hardware defect and go ***** to AT&T.
Sent from my SGH-I747 using xda app-developers app
oscooter said:
My router at home is a Netgear. Not sure about work. The weird part for me is that I didn't use to have these problems with AOSP ROMs, not that I remember anyways. It seems like a recent development in the past few weeks.
Still having decent luck with task650's ROM. It did happen to me once last night at home but it's been stable as a rock otherwise. If it starts happening more I'm gonna flash stock. If it continues to happen from there I'll consider it a hardware defect and go ***** to AT&T.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I just tried two roms (liquid smooth and tasks aokp). Had wifi issues with both of them after reboot. I decided to try two custom kernels (underwear and ktoonsez). Still experienced wifi saying not in range. The issue seems to be with the latest cm base which is used in all AOSP and AOKP roms. I hope this issue is fixed with the new cm 10.1 base. I guess I'll be stuck using only touch wiz roms now.
Found a great app that solves the wifi issue. It's called smart wifi toggler. Wifi reconnects after reboot now and remains connected when I go to sleep.
ak29 said:
I did give that rom a try. I had the same wifi issue when I went to bed. It also happens after the phone is rebooted. In addition I was getting the screen wake issue. Task's rom is still based on cm 10 so will have the same bugs. Maybe changing the kernel to task's own kernel or the other AOSP kernel. I'll give a try one of these days. Let me know how that works out for you.
Click to expand...
Click to collapse
It sounds like something is going wrong when you flashed the ROM. Task's AOKP isn't CM based (he cherry-picks from it, but builds from source), and I've never had a Wi-Fi issue with it.
Sent from my SGH-I747 using xda app-developers app
ak29 said:
Found a great app that solves the wifi issue. It's called smart wifi toggler. Wifi reconnects after reboot now and remains connected when I go to sleep.
Click to expand...
Click to collapse
Thanks for the heads up! I still have been having good luck with task650's ROM, but I will try this out on other ROMs!
guitarpunk8403 said:
It sounds like something is going wrong when you flashed the ROM. Task's AOKP isn't CM based (he cherry-picks from it, but builds from source), and I've never had a Wi-Fi issue with it.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I've been having good luck as well with tasks, but I don't know what could be going wrong when flashing a CM based ROM that is so consistent, unless it's either a hardware issue or something in their code base.
Sent from my SGH-I747 using xda app-developers app
oscooter said:
Thanks for the heads up! I still have been having good luck with task650's ROM, but I will try this out on other ROMs!
I've been having good luck as well with tasks, but I don't know what could be going wrong when flashing a CM based ROM that is so consistent, unless it's either a hardware issue or something in their code base.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
No prob. I'm finally able to enjoy tasks aokp now that I got the wifi issue solved with using smart wifi toggler. It's a great rom, with tons of features and customizations.
Hi,
I had recently flashed aokp 4.3 nightly version released on 28-09-2013. I moved from AOSP 4.3. But what happens when my phone doesn't connects with internet (wifi or data) it works like charm. No lag, no force closes, nothing.
But as soon as it connects with internet it starts lagging. Force closes all apps which i open. I tried franco kernel nighly build 391 and increased CPU frequency also but all in vain.
Just for reference i had installed Paranoid gapps for 4.3 (i think it doesn't make any difference) and recovery twrp latest.
Anyone know what this issue is all about. Is it normal and something which can be solved
Please help.
Thank You
bluedude1 said:
Hi,
I had recently flashed aopk 4.3 nightly version released on 28-09-2013. I moved from AOSP 4.3. But what happens when my phone doesn't connects with internet (wifi or data) it works like charm. No lag, no force closes, nothing.
But as soon as it connects with internet it starts lagging. Force closes all apps which i open. I tried franco kernel nighly build 391 and increased CPU frequency also but all in vain.
Just for reference i had installed Paranoid gapps for 4.3 (i think it doesn't make any difference) and recovery twrp latest.
Anyone know what this issue is all about. Is it normal and something which can be solved
Please help.
Thank You
Click to expand...
Click to collapse
From what I read it should have worked. I'm not a hater but Franco always gives me trouble, have you tried packed AOKP kernel? Its pretty sweet! I had used CM gapps but when switching to the second nightly I reinstalled with AOKP gapps.
Had to answer this when I seen ya call it AOPK lol ( edit: might have been seeing things)
Sent from my Galaxy Nexus using xda app-developers app
christopherrrg said:
From what I read it should have worked. I'm not a hater but Franco always gives me trouble, have you tried packed AOKP kernel? Its pretty sweet! I had used CM gapps but when switching to the second nightly I reinstalled with AOKP gapps.
Had to answer this when I seen ya call it AOPK lol ( edit: might have been seeing things)
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Ahh thanks for the AOPK mistake :laugh:
Ok, i tried AOKP kernel with AOKP gapps. Now its working fine without any force closes
Can you tell me one more thing. Sometimes what happens my phone suddenly gets restart if the phone gets heavy processing, now when it restarts it just stuck at "Google" logo and not comes to AOKP starting screen. I have to start the phone in recovery and clear cache and dalvik and then it starts normally that to if i put it a side for 10 minutes or so (by detaching the battery from phone)..
Can you know whats the problem is all about.... Ahh yes my phone is giving hell lots of problem
Thank Again
bluedude1 said:
Ahh thanks for the AOPK mistake :laugh:
Ok, i tried AOKP kernel with AOKP gapps. Now its working fine without any force closes
Can you tell me one more thing. Sometimes what happens my phone suddenly gets restart if the phone gets heavy processing, now when it restarts it just stuck at "Google" logo and not comes to AOKP starting screen. I have to start the phone in recovery and clear cache and dalvik and then it starts normally that to if i put it a side for 10 minutes or so (by detaching the battery from phone)..
Can you know whats the problem is all about.... Ahh yes my phone is giving hell lots of problem
Thank Again
Click to expand...
Click to collapse
If its restarting once in a while (does to me also with heavy use on stock kernel) try downloading trickstermod and see if you can change the limit %.
If you can't with stock kernel I know you can with Franco.
If that doesn't fix the problem it could even be the latest AOKP nightlies giving you an issue, I know the second last nightly (Oct 6th not Oct 10th) was causing me all kinds of issues. I just downloaded the latest (10th) and so far it seems to be going well with no restarts but I haven't gamed.
I got a question for you if applicable, do you use Google play music at all?
I keep getting songs randomly pausing or play music force closes with no notice (no toast pop up or nothing)
Sent from my Galaxy Nexus using Tapatalk now Free
There are so many recoveries available and I tried them all.. most dont even get flashed. Anyway, I ended up with the only one that seems to work for my N5120, CivZ_rev1.1-PhilZ_5. I succesfully flashed an 4.2.2 though the benchmarks are a disaster, the battery vanishes in 2 hours and the performance is a joke.. Quandrant gets me less than 2000...
That leads me to try and flash a 4.4.2.. but every single one the flash fails and gets aborted with a STATUS 7 message.. no matter the build, kind, or if it comes from the internal SD card or the External SD.. always fails. What the hell am I doing wrong and how can I flash this Tab?... I feel so frustrated.. nothing like this ever happened to me.
Thanks much for the advice..
Don't know if that helps but I had similar issues. Ended up flashing official CM11 Nightlies, the best I could find for N5120 up to now. No Pen support but the rest is working ok. Quadrant gives me a score of 5095.
For flashing the only recovery that worked for me (and I also tried many giving Status 7) was / is PhilZ Touch 6 based on Clockworkmod v6.0.4.7.
There might be more recent now but as this one worked, I sticked with it.
Envoyé de mon SM-N9005 en utilisant Tapatalk
LuMe96 said:
Don't know if that helps but I had similar issues. Ended up flashing official CM11 Nightlies, the best I could find for N5120 up to now. No Pen support but the rest is working ok. Quadrant gives me a score of 5095.
For flashing the only recovery that worked for me (and I also tried many giving Status 7) was / is PhilZ Touch 6 based on Clockworkmod v6.0.4.7.
There might be more recent now but as this one worked, I sticked with it.
Click to expand...
Click to collapse
Thanks for your advice.. PhilZ Touch v6.0.4.7 finally worked.. is crazy there are so many recoveries for the Note 8 and almost all have problems or are not compatible with KK..
I flashed the latest CM11 but I have LOTS of problems.. when the Tab is power off and charging, I get is a frozen image of the battery loading with full screen brightness but no charging animation or charging level information and basically the Tab doesn't charge and just heats up, I have issues with the menu key (left to the home button hardware softkey), I have problems with the home button that insists usually activating a double click when I only press it once, I have very long delays in locking wifi and GSM signal and several other small things that bother me.. and I come from rooted stock 4.2.2 with a costume Kernel that I could overclock the Tab to 1.9GHz.. but no Kernels available seems for 4.4.2.. the performance I get with CM11 is horrible compared to what I had with stock 4.2.2 and the battery lasts NOTHING..for me CM11 is unusable at this point and the developer doesn't bother to reply to any questions..maybe some problems are specifically with my unit and the CM11 ROM and maybe some problems because of the modem I have (my N5120 is from Hong Kong).. there are lots of other modems available but I have no idea what to try and worry make things worse..
I am curious about your experience with the other KK ROMs.. I want try to PAC, Paranoid and SlimKat..you dont like them? What problems you had with them?
Thanks again for your input
Hi,
I do agree regarding the charging "Device off" issue, but I tend to never switch my device off, so I can live with that. For the rest I do not recognize any of the issues you listed. 3G / 4G working fine, WiFi also and no problems with the hardware buttons.
By the way, mine is also HK version. I bought during my last trip to HK last year.
I tried PAC Rom, and had no major issues either, except missing Recent Apps manager. Didn't try any other ROMs up to now. I tend to prefer "basic" ROMs and add some needed stuff through Xposed. This is also the reason I decided to switch to CM11 when it became official. Haven't found the need to come back to PAC Rom since. It's not TOP but does the job for me. As you are speaking about battery, I do easily get 4 hours of Plex Video Playback over WiFi at decent screen brightness / 4 to 5 hours video Playback with MX Player and video stored on external SD-Card. Will however probably revert to TW ROM as soon as a 4.4.2 version is released to recover PEN functionality.
Did you use the official CM11 from their website? I know that there are older non official versions around (which I initially tried but had problems with).
I attached a screenshot of my about screen so you can have a look at baseband and kernel.
LuMe96 said:
Hi,
I do agree regarding the charging "Device off" issue, but I tend to never switch my device off, so I can live with that. For the rest I do not recognize any of the issues you listed. 3G / 4G working fine, WiFi also and no problems with the hardware buttons.
By the way, mine is also HK version. I bought during my last trip to HK last year.
I tried PAC Rom, and had no major issues either, except missing Recent Apps manager. Didn't try any other ROMs up to now. I tend to prefer "basic" ROMs and add some needed stuff through Xposed. This is also the reason I decided to switch to CM11 when it became official. Haven't found the need to come back to PAC Rom since. It's not TOP but does the job for me. As you are speaking about battery, I do easily get 4 hours of Plex Video Playback over WiFi at decent screen brightness / 4 to 5 hours video Playback with MX Player and video stored on external SD-Card. Will however probably revert to TW ROM as soon as a 4.4.2 version is released to recover PEN functionality.
Did you use the official CM11 from their website? I know that there are older non official versions around (which I initially tried but had problems with).
I attached a screenshot of my about screen so you can have a look at baseband and kernel.
Click to expand...
Click to collapse
Yes I downloaded from their official link (I think):
http://download.cyanogenmod.org/?device=n5120
Im running cm-11-20140525-NIGHTLY-n5120.zip
Ok, strange I'm running the exact same version.
Regarding WiFi and network issues you might want to check modem / baseband version (and kernel). Other than that I don't see why there is such a difference in behavior between your device and mine, sorry.
Envoyé de mon SM-N9005 en utilisant Tapatalk
I've found a possible "fix" for the bluetooth problem... (very frequent disconnects from Android Wear and other devices, "Bluetooth Share" crashes, etc) but I need testers.
Attached is a zip you can flash from recovery.
After trying a bunch of stuff to get bluetooth to work properly with no luck, I decided to just rip the "/system/etc/bluetooth" folder off of an official LG 5.0.2 ROM and overwrite the existing bluetooth files in CM12.1. It seems to have worked. My bluetooth hasn't crashed once since, and Android Wear has been happy and synced all day. I'm running it on my E980 with the June 1 nightly build of CM12.1 (which also supposedly has some bt fixes... but bt still crashed on it until I flashed this).
New version July 6, 2015: btpatchv5.zip
v5 is based on bt from the latest (0704) CM12.1 nightly and works very well for me;
v4 is based on the official LG 5.0 ROM and IS tested.
Changes:
>> Bundled in the Ao-Shi app (not my work, all credit to Daniel Baucom for this nifty little tool)
>> Added 3 bluetooth binary files to /system/xbin in an attempt to quell the "bluesleep" wakelock and get some deep sleep.
Let me know how it works for you... grab the download below...
*Regarding the Ao-Shi app that I've included...
If you get an occasional BT crash, fire up the Ao-shi app. Tap "Kill Bluetooth" two or three times (not just once; once doesn't work). Then, click "Revive Bluetooth". For me this usually gets BT working again without a reboot. Again, thank you to Daniel Baucom for this little gem. It even has widgets you can add to your homescreen for faster action.
Thx for sharing this information.I've got another question, aren't you having problems using 'oké googe' on your wear?. I've seems to keeping having problems on my phone,using 'oké google'
stipvroegop said:
Thx for sharing this information.I've got another question, aren't you having problems using 'oké googe' on your wear?. I've seems to keeping having problems on my phone,using 'oké google'
Click to expand...
Click to collapse
Yes... when BT partially craps out, "OK Google" gets wonky. Usually I get a total BT crash shortly after.
I have been heavily experimenting, and I might be on the trail of a true fix, but I need to test more before posting it. Keep your fingers crossed.
stipvroegop said:
Thx for sharing this information.I've got another question, aren't you having problems using 'oké googe' on your wear?. I've seems to keeping having problems on my phone,using 'oké google'
Click to expand...
Click to collapse
I've uploaded a small patch, give it a shot and see if it helps you. It has worked great for me. See the OP for the file.
Mpsantiago, where can I find the patch, and how does it work? Tnx for sharing your solution
stipvroegop said:
Mpsantiago, where can I find the patch, and how does it work? Tnx for sharing your solution
Click to expand...
Click to collapse
It's up above attached to the first post- btpatchv2.zip
All it does is transplant the bluetooth files from the official LG 5.0.2 E9XX ROM into CM12.1.
Flash it from recovery and enjoy. You'll likely have to re-flash it after any nightly upgrade (until the problem gets fixed upstream).
Ok, I've tested the patch with both my Moto360 and my BT speakers- everything seems good.
mpsantiago said:
Ok, I've tested the patch with both my Moto360 and my BT speakers- everything seems good.
Click to expand...
Click to collapse
Still good with BT, do you still have screen flickering?
dpalmer76 said:
Still good with BT, do you still have screen flickering?
Click to expand...
Click to collapse
No, screen flickering is a pretty easy fix compared to BT:
Option #1: Turn off Hardware Overlays every time you boot your device
Option #2: Install the xposed module "NoMoreOverlay"
Option #3: Modify build.prop file, change the line "persist.hwc.mdpcomp.enable" from true to false
Do I only have to flash the zip for BT to stay synced? No need to change anything else?
DanC7766 said:
Do I only have to flash the zip for BT to stay synced? No need to change anything else?
Click to expand...
Click to collapse
Just flash, that's it.
So far, BT has only crashed twice since I first started testing it, and it happened when I was goofing with it pairing different stuff- not during normal use. Both times I was able to revive it without rebooting using this app: https://play.google.com/store/apps/details?id=co.loudbit.ao_shi
I've noticed very little deep sleep while using this solution, possibly related to "bluesleep" wakelock- I'm investigating this to see if I can fix it.
EDIT: I've added a new download to the OP above; not sure if it will fix bluesleep wakelocks but I'm hopeful... I'll be testing it tomorrow... off to bed now for me!
Update
mpsantiago said:
I've noticed very little deep sleep while using this solution, possibly related to "bluesleep" wakelock- I'm investigating this to see if I can fix it.
EDIT: I've added a new download to the OP above; not sure if it will fix bluesleep wakelocks but I'm hopeful... I'll be testing it tomorrow... off to bed now for me!
Click to expand...
Click to collapse
How is this fix working to date?
dpalmer76 said:
How is this fix working to date?
Click to expand...
Click to collapse
So far, so good.
I still get an occasional BT crash, but it's maybe one or two a day instead of one every 15 minutes. I'm actually testing yet another revision to the patch with an additional tweak and another LG BT library file moved over... if it is stable I'll post it next.
Tested the latest (june 4th) version and works so far. I did notice a decrease in battery life afterwards tho, significant vs the non-working bluetooth.
This patch may no longer be needed. I flashed 20150625-NIGHTLY this morning (without patching afterwards) and so far bluetooth has been flawless.
mpsantiago said:
This patch may no longer be needed. I flashed 20150625-NIGHTLY this morning (without patching afterwards) and so far bluetooth has been flawless.
Click to expand...
Click to collapse
sim card ok?
That day I was in a rush... I basically flashed the nightly and threw the phone in my pocket. My watch got all my notification alerts no problem all morning- it wasn't until lunch time that I looked at my phone and noticed the SIM problem.
Hopefully they'll have it sorted soon, though it's still not with the latest build. If it's not fixed by the end of the week I'll probably look into ripping the BT stuff out of the latest nightly and updating this patch with it.
mpsantiago said:
That day I was in a rush... I basically flashed the nightly and threw the phone in my pocket. My watch got all my notification alerts no problem all morning- it wasn't until lunch time that I looked at my phone and noticed the SIM problem.
Hopefully they'll have it sorted soon, though it's still not with the latest build. If it's not fixed by the end of the week I'll probably look into ripping the BT stuff out of the latest nightly and updating this patch with it.
Click to expand...
Click to collapse
Are you using this with blisspop? Wakelocks still?
Sent from my LG-E980 using Tapatalk
UPDATE:
Since the CM12.1 nightly builds still have a borked SIM card (but seemingly working BT), I replaced the bluetooth guts in V5 of this patch with the ones from the latest 12.1 build instead of what I was using before (the official LG 5.0 build). I have only tested it for a few hours, but it seems solid. Have NOT checked for wakelocks or battery drain. Flash at own risk.
I've omitted the Ao-Shi app; you can install it from Play Store if you want. Alternatively, if BT ever crashes you can manually revive it without rebooting:
Settings > Apps > All > Bluetooth Share > FORCE CLOSE then CLEAR DATA; turn Bluetooth back on and it should be fine.
dpalmer76 said:
Are you using this with blisspop? Wakelocks still?
Sent from my LG-E980 using Tapatalk
Click to expand...
Click to collapse
Haven't tried with Blisspop, only with cm12.1 nightlies. It should work on any CM12.1 based ROM though. I get decent deep sleep with it. YMMV.