Develop Bugs

Anyone else having complete "fail" on latest CM7?

Way back in the 30's I was getting fantastic results with CM7 and tiamets kernel. I recently wanted to go back to it until the Sense 2.1 guys ironed out a few more bugs for me to comfortably daily drive them. I installed n63....had issues 7.0.3.1.... had issues.... n65.... had issues.
By issues I mean random restarts, force closes, 3g won't stick, overall signal for 1x was horrible, no amount of gps fixing would keep my gps locked in or lock better than 20 meters and mms won't work.
I tried stock kernel, tiamets, SZ ect.... clean install, clean wipe, reinstall apps from market vs restore from TB. Tried the mms fix, gps status app, msl reset trick, you name it I have tried it. My phone does not like CM7 right now at all. It's like feeding a baby strained carrots.
I was just curious if anyone else is having similar "no amount of tweaking will fix it" issues. I had to go back to Konis just for some sanity after 3days of this. I know all these Roms that are not based on actual Evo source are experimental but can a guy get some CM love?! lol

I am having pretty much the same issues on my evo. Tried just about the same tweaks to try to rectify them. Right now I'm going to under clock and see if it helps. I noticed a lot more things residing in memory after a restart than usual, including fota kill which is a cm product. All I think I can do now is fire up catlog and see if anything is obvious. I'm no genius so likely I'll just send it in and hope for the best. I was almost sure my hardware was failing, but now not so much.

Haven't had any issues gonna try the latest stable build of cm7 I always use amon 2.3 for a full wipe a lot of the time that fixes issues for people .

ginjeet said:
I am having pretty much the same issues on my evo. Tried just about the same tweaks to try to rectify them. Right now I'm going to under clock and see if it helps. I noticed a lot more things residing in memory after a restart than usual, including fota kill which is a cm product. All I think I can do now is fire up catlog and see if anything is obvious. I'm no genius so likely I'll just send it in and hope for the best. I was almost sure my hardware was failing, but now not so much.
Click to expand...
Click to collapse
Well, n66 after a day on tiamets 4.0.1 kernel seems stable. Let me know how the undervolting goes. I tried vipers v2 and it started freezing after about 20 minutes. The -50 script did the same thing. -25 actually worked out pretty well right up until this morning. My alarm went off and I hit snooze and it threw it into constant reboot.
I'm going to run just n66 with 4.0.1 all day no script and see what I get. I dunno what has changed for my phone but it seems to have leveled out. *knocks on wood*
Sent from my PC36100 using XDA Premium App

So far on the 7.0.3.1 build GPS works like a champ market mms and everything camera and such you tube app plays everything on hq. Picky at time at times tho on HQ.

blizzard1017 said:
Way back in the 30's I was getting fantastic results with CM7 and tiamets kernel. I recently wanted to go back to it until the Sense 2.1 guys ironed out a few more bugs for me to comfortably daily drive them. I installed n63....had issues 7.0.3.1.... had issues.... n65.... had issues.
By issues I mean random restarts, force closes, 3g won't stick, overall signal for 1x was horrible, no amount of gps fixing would keep my gps locked in or lock better than 20 meters and mms won't work.
I tried stock kernel, tiamets, SZ ect.... clean install, clean wipe, reinstall apps from market vs restore from TB. Tried the mms fix, gps status app, msl reset trick, you name it I have tried it. My phone does not like CM7 right now at all. It's like feeding a baby strained carrots.
I was just curious if anyone else is having similar "no amount of tweaking will fix it" issues. I had to go back to Konis just for some sanity after 3days of this. I know all these Roms that are not based on actual Evo source are experimental but can a guy get some CM love?! lol
Click to expand...
Click to collapse
Are you u using amon 2.3

Cm7 is running great for me. Used nightly 65 for a week with no problems. Flashed 7.0.3.1 2 days ago and it is running like a champ with sz 2.1.0 cfs. Did GPS fix back on nightly 30 something and it has been fine ever since. Maybe you just made your phone mad and its retaliating lol. I do have the receive mms problem though . Tried multiple fixes for it with no luck.
Update* just received an mms with 7.0.3.1 and it worked

A1Lonestar said:
Cm7 is running great for me. Used nightly 65 for a week with no problems. Flashed 7.0.3.1 2 days ago and it is running like a champ with sz 2.1.0 cfs. Did GPS fix back on nightly 30 something and it has been fine ever since. Maybe you just made your phone mad and its retaliating lol. I do have the receive mms problem though . Tried multiple fixes for it with no luck.
Click to expand...
Click to collapse
What recovery are you using man? Anything better using nightly 66 advantage wise?

reaper24 said:
What recovery are you using man? Anything better using nightly 66 advantage wise?
Click to expand...
Click to collapse
Well 66 plays nicely, but I think the mms bug where you can't receive, but using 3.3.7/4.0.1 with bsm v2 and it plays nicely.

teh roxxorz said:
Well 66 plays nicely, but I think the mms bug where you can't receive, but using 3.3.7/4.0.1 with bsm v2 and it plays nicely.
Click to expand...
Click to collapse
Well, I just went back to Koni's..............again. I was running 66 all morning with 4.0.1 and no script and while everything was working ok the battery was draining somewhat fast. It wasn't a wake issue and I even tested an hour or so on PRI177 with the same results. The battery was tolerable because Mondays are really busy for me so I know on a normal day I wouldn't complain but my data connection still drops to 1x a lot and I think the drain might have something to do with the connection searching constantly.
If I can get that Viper script moving along and figure out the data and signal drop I think I am getting somewhere.
@reaper, yes I am using Amon Ra latest and greatest.
Off topic, I love the Nand backup option. My Vibrant only uses Clockwork and even then it was not fully functional. Some of the basic options would brick the phone.

The latest cm7 stable works great.
Sent from my PC36100 using XDA App

flashing back to sense after "GPS FIX"
I have a few issues with CM7 and I keep switching back to Sense roms because they have been stable. If I do the GPS fix and stay on CM7 will my GPS still work when and if I go back to a Sense ROM?

[Q] hdmwin + CM7 question.

does cm7 work with hdmwin, because this app used to work a few weeks ago.
then after i saw that ps3 controller were now able to be used on the evo i went home and tried it, but lucky me, the app seems broken because everytime i plug in the cable my phone just freezes.
i keep reading xda and some people say it works, some say opposite. ive tried all the kernels mentioned here(tiamat,cm nicghly, etc) and i get the same outcome. what am i doing wrong, since i didnt change anything in my phone and last month this worked.
could somebody point me in the right direction or tell me the steps on how it worked for u guys i would appreciate it.
thanks

Yes.. just download from the market and enjoy.

Yea I did downloadbit again and it still freezes...
Wtf?

I'm using the CM7 nightly 180 build with Tiamat and it works great.
When you installed HDMwIn, did it ask you to download the daemon driver?
Sent from my PC36100

It Did when I trried with app in market. I accodently pressed back because I thought it was the notification about the acceler. Kernel.
I restarted the app but it didn ask again
What should I do

oscar996 said:
It Did when I trried with app in market. I accodently pressed back because I thought it was the notification about the acceler. Kernel.
I restarted the app but it didn ask again
What should I do
Click to expand...
Click to collapse
Uninstall clear cache and data and reinstall
Sent from my Xoom using xda premium

Yea i just did that and my phone still freezes when I plug in cable
I'm using cm7 with stocck cm kernel

Same result and I tried with 2 different tvs. Where it used to work
Tried witt tiamat kernel

oscar996 said:
Same result and I tried with 2 different tvs. Where it used to work
Tried witt tiamat kernel
Click to expand...
Click to collapse
This happened to me before on 7.1 and that's why I switched to the nightly build 180 and it's been stable. IMO, it's the ROM. Back your apps with Titanium Backup and reinstall the nightly builds http://download.cyanogenmod.com/get/cm_supersonic_full-180.zip

First thanks for reply,
The rom could be one of the reasons but it worked 3 weeks ago that's why I don't understand.
I haven't tried any of the nightlys because of the bugs
There has to be another fix, it worked fine before
Th

oscar996 said:
First thanks for reply,
The rom could be one of the reasons but it worked 3 weeks ago that's why I don't understand.
I haven't tried any of the nightlys because of the bugs
There has to be another fix, it worked fine before
Th
Click to expand...
Click to collapse
Yup, I was thinking the same thing when I ran into that issue. However, since loading the nightly builds, I haven't had a glitch with any apps, especially the mirroring app. It worked before on my phone and for what ever reason, it stopped working. The nightly build isn't buggy to me. Nothing force closes on me, GPS locks quick...everything is working...

Same with me a reboot with. Hdmi cable plugged in does the job
Sent from my PC36100 using XDA App

I tried the nightly 180 and right after I flashed it when into hdmi and it worked, kinda. It wouldnt display sometimes, itwoukd work then black screen so I figured it could be the cable.
So I left it pluged and played some snes without moving the cable.
This morning I plugin the cable again and BOOM it freezs AGAIN. WTF!!!!!!!!
Could it be that a broken cable does that?, I don't think so. If it was broken it wouldn't display, not freeze the phone
Wth am I doing wrong, this is driving me crazy, I already ordered another cable.
But why did it work the first time I tried the nightly , then next day it freezes again
HELP

I tried rebooting with cable but it just freezes at htc evo screen

Any other suggestion?

I replaced my cable because it was making my phone freeze, it was workin great for couple days but now its just mirroing like static.
How can I fix that, evo cm7

After trying a few different nightly builds and installing and uninstalling I finally got HDMwIn to work on nightly 214 with sz bfs kernel but after mirroring i saw that it broke my wifi and rebooting and clearing caches doesn't fix... i've been searching for 40 minutes but all i find are really old posts or sense wireless N fixes if this happens. anyone know what to do? or do I have to flash the rom again or is it the kerenl or can i replace a file via root explorer??

I got it working by using the cm7 kernel with the 180 nightly, and replacing my cable

Glad to read you got it working. It works, but can be finicky with the latest CM7 nightlies.
http://www.youtube.com/watch?v=9U1R4NgfAgM youtube.com/watch?v=9U1R4NgfAgM
In that video, I'm running the lastest nightly, #225 (10-16-11) with Tiamat 4.10. I found if I get any static or, as you see, no video, I just unplug the HDMI cord from the Evo, and replug in.

[Q] Wifi Dropping on AOSP/CM ROMs

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.

[Q] Differences BT in WIND-Kernel?

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!

[Q] Lag problem when connecting to internet in AOKP 4.3

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