CM7 Kang 2011-11-05 + aeroevan BFS - Verizon Droid Incredible 2

I have been working on fixing the bugs in cyanogenmod that cause the data issues when using BFS kernels.
The CM7 nightly build is here: http://www.multiupload.com/0Z3Z8M5FE7
and my v0.6 bfs kernel is here: http://www.multiupload.com/ZOAMV7NQBI
If nothing seems to be broken, feel free to review http://review.cyanogenmod.com/#change,9829 and http://review.cyanogenmod.com/#change,9734

aeroevan said:
So I still can't post to the development forum, but I have been working on fixing the bugs in cyanogenmod that cause the data issues when using BFS kernels.
The CM7 nightly build is here: http://www.multiupload.com/0Z3Z8M5FE7
and my v0.6 bfs kernel is here: http://www.multiupload.com/ZOAMV7NQBI
If nothing seems to be broken, feel free to review http://review.cyanogenmod.com/#change,9829 and http://review.cyanogenmod.com/#change,9734
Click to expand...
Click to collapse
I may work on flashing this this week, I'm on miui but missing me some cm7. Is this having the youtube and mms issues cm has?
Sent from my Incredible 2 using xda premium

Loaded Saturday morning, been running fine. No data drops.MMS, YouTube, data anamation
arrows, compass works. Haven't tried any flash videos.
Running smarta** at 245/1113. Getting 2200 - 2500
on quadrant. (If that matters)

I think I finally fixed all of the possible data issues:
Updated cm7 nightly kang: http://www.multiupload.com/UI6MOP5OSD
which includes http://review.cyanogenmod.com/#change,9829 and http://review.cyanogenmod.com/#change,9850
That should cover every corner case where data could be lost due to the dnsproxyd cache (this was a bug in AOSP, so all AOSP roms will have this bug until the fix is applied).
I also have a test build for v0.7 of my kernel (which should fix zram enable issues): http://www.multiupload.com/WDSSQ85LJM I also rewrote my updater-script, so let me know if there are any issues (I've only tested on my cm7 kang build).

Working well for me so far. Using the 0.7 Kernel, CompCache up and running. No data loss issues so far today. I think all may be well

can i flash this over my current cm7 nightly?

Been running for a day now, haven't noticed any depreciated performance/battery.

haven't really followed your kernels, but have you addressed the low call volume issue that plagues the built in kernel?
if so, I'll jump on and start testing immediately.

Yes areoevan kernels have the vol. fixed.Been running them since the first one he released.

from the dates of the changes and the fact they've been merged, I assume all new nightlies have the new changes (minus the kernel part) correct?

dnoyeb said:
from the dates of the changes and the fact they've been merged, I assume all new nightlies have the new changes (minus the kernel part) correct?
Click to expand...
Click to collapse
133 and 134 nightlies have the changes incorporated.

ok, so. i flashed this. the is the best my compass has acted since i flashed CM7, the in call volume is perfect. I'm getting really good Quadrant scores(for whatever that is worth), data dropping in and out seems to be gone. It wouldn't connect to WiFi right away, but eventually did.
My question is; what is the difference between this kernel and the .06 cfs version?

Umm ok So that was weird... Delete please.

What's weird?
Sent from my Incredible 2 using XDA App

Mt reply was to another topic, and somehow ended up here

PacerguyDon said:
Mt reply was to another topic, and somehow ended up here
Click to expand...
Click to collapse
yea, that's weird.

Related

quick question about cm7

what is the difference between nightly and stable??
Sent from my PC36100 using XDA App
You basically just said it.
Nightly- not stable and each one builds upon the other and fixes bugs
Stable- completely working, bugs fixed, no problems besides user error
evouser22 said:
what is the difference between nightly and stable??
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Interestingly, with CM7, the nighties are themselves, very very capable and remarkably stable. Definitely stable enough to be most people's daily driver.
I run nightlues all the time and they are very stable. Much better than rls1 ever was. A full stable should be coming soon though.
Sent from my PC36100
Like the people above me said, Nightlies are compiled every night (usually) and aren't considered by Team Douche to be "stable." Oh, and if you file a bug report about something in a Nightly, expect to be burned at the stake.
RC's are a tad more stable than Nightlies (typically) and while they don't include the latest-and-greatest features all the time (ie, RC1 is now outdated and doesn't have WiMAX or the battery percentage in the status bar), you can file bug reports about them and they'll usually get solved.
Stables are just what their name says: Stable. There's rarely any major bugs in them, and when bugs are discovered, a bug report can be filed, and assuming it's not an 1D10T error, gets fixed, and integrated into the next Nightly/RC/Stable, or they'll just make a .1 release (ie, 7.0.0 to 7.0.1 and so on).
Right now though, CM is in feature freeze, so all that's going into Nightlies right now are bugfixes (for example, the WiMAX code for EVO broke a bunch of other phones in weird ways, and the Nexus One has a "wonky" bug). We'll probably see RC2 in a week or two, and then 7.0.0 stable within a month.

[Q] CM7 RC3?

Does anyone know what RC3 actually adds? I am currently running CM7 RC2 on my evo 4g and i am wandering if i should update to RC3 or wait for the final release.
As my evo was stolen today, I haven't flashed. But should include further tweaks and fixes and should have hdmi working on it for sure.
From what i see and have read the only change is the HDMI, other than that everything seems the same
I was blessed with this page the other day.
http://cm-nightlies.appspot.com/?device=supersonic
Seeing as how it fixes HDMI, will this break HDMwIn?
teh roxxorz said:
As my evo was stolen today, I haven't flashed. But should include further tweaks and fixes and should have hdmi working on it for sure.
Click to expand...
Click to collapse
Dam. Sucks to hear.
Sent from my PC36100 using XDA Premium App
I've been running CM since RC1. It keeps getting smoother and smoother and my battery life generally increases. You don't need to do a full wipe, just clear your cache and dalvik, then flash RC3 on top of RC2. It won't be a huge change, but it'll likely run even smoother, methinks.
Jam3l said:
Does anyone know what RC3 actually adds? I am currently running CM7 RC2 on my evo 4g and i am wandering if i should update to RC3 or wait for the final release.
Click to expand...
Click to collapse
I just flash the RC's, I usually don't flash the nightlies. Going to RC3 I noticed the GPS seems to track better without doing the sense fix. Other than that, I haven't really noticed anything. I think it's still worth it to flash the new one though, I'm sure there's plenty of improvements that I just haven't noticed yet.
Ive been flashing nightlies since #14 I think. Each one is better than the last. RC3 is no different. It is just a step up from nightly 31 and runs exceptionally smooth. Personally, I'm not even running it though, I only ran it long enough for nightly 32 to drop....
xhaui said:
Ive been flashing nightlies since #14 I think. Each one is better than the last. RC3 is no different. It is just a step up from nightly 31 and runs exceptionally smooth. Personally, I'm not even running it though, I only ran it long enough for nightly 32 to drop....
Click to expand...
Click to collapse
So you flashed 32 for one commit?
swyped from my cyanogenized and gingerbreaded EVO
Good Morning, After I install rc3 do i then install cm_supersonic_full-32. In another words, is nightly 32 the first nightly after you install rc3?
Mad_Dog238 said:
Good Morning, After I install rc3 do i then install cm_supersonic_full-32. In another words, is nightly 32 the first nightly after you install rc3?
Click to expand...
Click to collapse
You dont need to install RC3 before installing nightly 32 if thats what you want to use. You can just install nightly 32 over whatever CM7 version you are running now
but yes, nightly 32 is newer than RC3
Phone is Making Random Phone Calls
While at the mall with a friend, he told me that I was calling him. The crazy thing was my phone was in my car outside. The next day while at the dinner table, my phone starting ringing another one of my contacts without me even touching it.
Call this paranormal activity 4 but it has happened 2 more times since. Any thoughts? My sd card has been formatted and i did not install any of the apps found at http://forum.xda-developers.com/showthread.php?t=976913
Currently have rc2 nightly 31 installed.
I would recommend doing a complete wipe, then reflash the rom.
thegregbradley said:
I've been running CM since RC1. It keeps getting smoother and smoother and my battery life generally increases. You don't need to do a full wipe, just clear your cache and dalvik, then flash RC3 on top of RC2. It won't be a huge change, but it'll likely run even smoother, methinks.
Click to expand...
Click to collapse
I did exactly this and the market no longer works. You can download, but once an app starts to install the market fc's and doesn't install. Any ideas?
effluent said:
I did exactly this and the market no longer works. You can download, but once an app starts to install the market fc's and doesn't install. Any ideas?
Click to expand...
Click to collapse
Did you flash the latest gapps with it??
teh roxxorz said:
Did you flash the latest gapps with it??
Click to expand...
Click to collapse
Didn't know that I needed to if I was just upgrading, but after this issue I did anyway and had no effect.
Really stupid question incoming:
Does CM7 on the Evo utilize Wifi-N?
effluent said:
Didn't know that I needed to if I was just upgrading, but after this issue I did anyway and had no effect.
Click to expand...
Click to collapse
Well normally you don't, but it was an option, so still random calls? I would suggest, as earlier, do a complete wipe, then re-flash the rom with gapps.
Weird. My phone paranormaly has sent texts to random people while running cm7... scary..
Sent from my PC36100 using XDA App

Best CM7? Nightly? Stable?RC?

Which one is better. Can make up my mind. Happy Easter.
Go for nightly 54. Haven't used my phone much...92% and about 6.5hrs on battery life.
Been riding the Stable for a while. The talk following the immediate nightlies thereafter put me on hold, figure I'll wait it out until drastic changes / additions start happening.
Seems like said issues have been addressed and / or a fix is available. Stable has been running great for me, using Tiamat, and haven't really had a reason to move on.
So long as you avoid the 'bad ones' you should be good.
do you not know the difference, or are you asking what are the benifits of the newest nightly over stable? if so, here's the changelog. http://cm-nightlies.appspot.com/?device=supersonic . happy easter
Latest nightly w/ n39 GPS driver fix
aph said:
Latest nightly w/ n39 GPS driver fix
Click to expand...
Click to collapse
+1
although there are a few bugs you can find a few answers in my siggy and the rest in the xda threads.
Use Nightly 54
I have been loving Nightly 54 with gps-test.zip to fix Google Maps. Everything has been running smoother than Stable, good luck!
stable 7.0.1 is out.

[Q] This is driving me nuts..CM9/FXP123

Hi all,
Just recently flashed the new FXP123 build and the newest CM9 nightly. I am having an issue with both. As some may or may not know, the new FXP123 build came with a new kernel. This new kernel doesn't allow overclocking and seems a little sluggish.
My solution was to flash a different ICS kernel (KeICS v2, Darkforest v5, DooMKernel v3). Upon flashing a different kernel, WiFi would be broken. When I would attempt to turn it on, it just stays at "Turning Wi-Fi on..." indefinitely. When I reflashed the new FXP123 kernel, WiFi would be restored.
Are these new CM9 builds not compatible with other kernels? It seems odd that both FXP and the new CM9 nightly both have this issue. I've tried flashing the kernel before and after wiping data for a new ROM install, wiping after flashing, etc. I've tried using the different command in fastboot (fastboot -i 0x0fce flash boot <boot>.img). Nothing has worked.
Apparently FXP has changed the way wifi modules are loaded pax has said. Guess we just need updated kernels or patches. Solved?
Sent from my R800x using Tapatalk 2
Sluggish doesnt even begin to describe my experience with FXP123. It's my first time using CM9 so I can't compare it to previous builds, but holy crap is it slow.
Coming from CM7, I expected a small hit to performance but not to this extent. Everything takes 2-3 times longer to load or react on CM9 compared to CM7.
I hope this is just a problem with FXP123.
3dawg said:
Sluggish doesnt even begin to describe my experience with FXP123. It's my first time using CM9 so I can't compare it to previous builds, but holy crap is it slow.
Coming from CM7, I expected a small hit to performance but not to this extent. Everything takes 2-3 times longer to load or react on CM9 compared to CM7.
I hope this is just a problem with FXP123.
Click to expand...
Click to collapse
Try Aokp, it's latest build is based on fxp123 and is running smoothly without over clock, although I only have a few apps installed to prevent sluggishness
Sent from my Xperia Play using XDA
Nabeel_Nabs said:
Try Aokp, it's latest build is based on fxp123 and is running smoothly without over clock, although I only have a few apps installed to prevent sluggishness
Sent from my Xperia Play using XDA
Click to expand...
Click to collapse
I really love CyanogenMod and after seeing the behaviour of some AOKP devs, I'd rather not support them.
http://www.reddit.com/r/Android/comments/uj5bc/dont_bother_reporting_bugs_to_the_aokp_team_they/
Unfortunately the chat log was deleted but I'm sure if you dig into the comments, people have logs.
EDIT: I understand this is an unofficial AOKP port for the PLAY and is not developed by the assholes in the provided link (the same asshole who essentially stole a HP Touchpad and HTC resound from the dev community) , perhaps I should leave my prejudices at the door and try it.
3dawg said:
I really love CyanogenMod and after seeing the behaviour of some AOKP devs, I'd rather not support them.
http://www.reddit.com/r/Android/comments/uj5bc/dont_bother_reporting_bugs_to_the_aokp_team_they/
Unfortunately the chat log was deleted but I'm sure if you dig into the comments, people have logs.
EDIT: I understand this is an unofficial AOKP port for the PLAY and is not developed by the assholes in the provided link (the same asshole who essentially stole a HP Touchpad and HTC resound from the dev community) , perhaps I should leave my prejudices at the door and try it.
Click to expand...
Click to collapse
I agree with trying it don't let the conduct of one or two of them take away from romans amazing talent. And as you said it's unofficial, so support our devs here.
Sent from my R800x using Tapatalk 2
Pax will be releasing new ROMs and Kernals shortly I believe that hold the old WiFi modules which should work for you guys. But noticed since I flashed the last kernal provided by FXP I have seen massivve improvement. Litrally my phone was on 30% battery. Put my phone next to my bed and today morning woke up seeing the battery was only down to 25 percent. So then I put it in charge and in 1 hour I see the phone's led is green indicating fully charged and surprizingly enough it was fully charged.

[KERNEL][DEV][ALPHA] AlterNdromadus 3.0.x KitKat CM11 | AOSB | CyanKat[22/03/14]

I'm back again.
It's the Andromadus htc7x30-3.0 (andromadus_4.4 branch) source compiled by me with tweaks. At the moment I'll consider it alpha, updates will be sporadic and not necessarily better than whatever came before it.
GPL Stuff
Source
Toolchain: @Christopher83 's Cortex A8 Optimized Cross Compiler Toolchain
Branch: andromadus_4.4
Kernel Version: 3.0.x
defconfig: vision_andromadus_defconfig
And the Rest...
Instructions: Click the link below, flash in recovery (no need to wipe anything), reboot
UPDATE 22/03/14: Click "Downloads" above for latest download
Changelog
Credits: Andromadus team, and a ****ton of people who have supported open source allowing me to take stuff for this kernel, and testers (you know who you are)
XDA:DevDB Information
AlterNdromadus 3.0.x, Kernel for the HTC Desire Z
Contributors
HTCDreamOn
Kernel Special Features:
Version Information
Status: No Longer Updated
Created 2014-11-29
Last Updated 2014-11-29
RESERVED
RESERVED
Justin case
Justin case
Told ya I'd wait for it. Downloaded and about to install. Thanx
Hi, just a quick report from V17 I had yesterday :
Not good at all for me :
- always a little latency before acting. Really noticealble on wake up.
- Same wifi bug as in stock one (scratch after airplane mode)
- long black screen during synchros this morning
- multiple android.process.media alerts. I had to reboot twice.
- with all that I can't say if it save battery as all the reboot consumes a lot...
I went back on stock ROM which is really more responsive for me.
Will try V18 but tonight. I need my phone at work today!
Are logcats required or unusefull for you?
RE: [KERNEL][DEV][ALPHA] AlterNdromadus 3.0.x KitKat CM11 | AOSB [24/02/14]
Kéno40 said:
Hi, just a quick report from V17 I had yesterday :
Not good at all for me :
- always a little latency before acting. Really noticealble on wake up.
- Same wifi bug as in stock one (scratch after airplane mode)
- long black screen during synchros this morning
- multiple android.process.media alerts. I had to reboot twice.
- with all that I can't say if it save battery as all the reboot consumes a lot...
I went back on stock ROM which is really more responsive for me.
Will try V18 but tonight. I need my phone at work today!
Are logcats required or unusefull for you?
Click to expand...
Click to collapse
A lot of those problems will be because I mucked about with memory allocation, but that should be fixed on Alpha 18. Logcats are more useful than nothing, last kmsg is good too, both is perfect. I expect the WiFi thing will be a ROM problem, and as to the latency I'm not sure. I tried to implement a GPU on input thing, maybe it doesn't work too well. You don't have ART enabled do you? Regarding the media crashes, are these random or happen at a particular moment, e.g. playing music, games, videos?
Thanks alot
PS as these are alpha I wouldn't suggest anyone else using these during work
evrything seems to be a okay this way. the wifi from airplane mode is from the rom, noticed it before installing ur kernal. no lag here. battery seems to be holding up well. idk if its the kernal or because i have radio turned off but together they seem to be doing great. THANK YOU. only time i got lag was when i went from dyninteractive to powersave, but since evrything is going well just went back to dyn
Awww great to see you again my friend
Will test it tonight. Only for flinny's alpha3 or also AOSB 1.2.9 / 1.3.0?
Cheers
Blade
RE: [KERNEL][DEV][ALPHA] AlterNdromadus 3.0.x KitKat CM11 | AOSB [24/02/14]
BIade said:
Awww great to see you again my friend
Will test it tonight. Only for flinny's alpha3 or also AOSB 1.2.9 / 1.3.0?
Cheers
Blade
Click to expand...
Click to collapse
Yeah this is only for KitKat ROMs, so the ones you mentioned; it won't boot on Jelly Bean.
To everyone: if I were to compile a ROM, what would you think of a revival of cn.fyodor's AOSP 4.2.2 with added features? Or any other suggestions?
HTCDreamOn said:
You don't have ART enabled do you? Regarding the media crashes, are these random or happen at a particular moment, e.g. playing music, games, videos?
Click to expand...
Click to collapse
NO ART for me
Just Seeder
media crashs are random. Sometime related to nothing but it seems to happen when working and screen goes off
I had to wipe things and reboot twice to fix it
Will report if it comes back
V18 far betteer. But I still notice this latency with black screen which is longer during synchro
HTCDreamOn said:
Yeah this is only for KitKat ROMs, so the ones you mentioned; it won't boot on Jelly Bean.
To everyone: if I were to compile a ROM, what would you think of a revival of cn.fyodor's AOSP 4.2.2 with added features? Or any other suggestions?
Click to expand...
Click to collapse
personally I would like to see if we can get a newer kernel working, like a 3.4 release.
RE: [KERNEL][DEV][ALPHA] AlterNdromadus 3.0.x KitKat CM11 | AOSB [24/02/14]
bradley_e_smith said:
personally I would like to see if we can get a newer kernel working, like a 3.4 release.
Click to expand...
Click to collapse
Are you reading my mind ? I've already been thinking about porting 3.4 (with help) for a while. It would be hard though, so in the meantime any ROM suggestions?
@Kéno40 I'm not sure what this latency problem is, I'll compile a version without the GPU input handler implemented when I have time and see if that makes a difference. Other than that I really can't figure out why you're having a problem, it's fine for me at least. What do you mean by synchro?
HTCDreamOn said:
Are you reading my mind ? I've already been thinking about porting 3.4 (with help) for a while. It would be hard though, so in the meantime any ROM suggestions?
@Kéno40 I'm not sure what this latency problem is, I'll compile a version without the GPU input handler implemented when I have time and see if that makes a difference. Other than that I really can't figure out why you're having a problem, it's fine for me at least. What do you mean by synchro?
Click to expand...
Click to collapse
I would be interested. I have compiled the lastest flinny merged with the lastest cyanogen frameworks. It boots but the camera doesn't work. So I have been looking further, but still playing around. I need to increase my virtual linux box diskspace, so I am working on reconfiguring it b/c of lack of diskspace.
I would love to see AOSP KK rom for our device. Just plain and simple.....(thats just my opinion, dont know about others)
Thanks...
Sent from my HTC Vision using xda app-developers app
And how about BT call audio? Is it working correctly with your Kernel? It is the only think I am missing wiht all the KitKat ROMs and it is definetely Kernel drivers fault... to be honest... the only roms that had it working since GB were those of 4.2.2...
And for me it would make a big help for my phone usage, cause I spend lot of the time in the car...
HTCDreamOn said:
@Kéno40 I'm not sure what this latency problem is, I'll compile a version without the GPU input handler implemented when I have time and see if that makes a difference. Other than that I really can't figure out why you're having a problem, it's fine for me at least. What do you mean by synchro?
Click to expand...
Click to collapse
In fact I don't use the lockscreen so when I tackpad wkae it, I arrive to the homescreen. But- I notice with it a little latency / black screen for less than half a second, but noticeable.
I cut Synchro during night because of the wifi problem. On the morning I put it back. It goes to slleep (the phone, not me ! ). If I wake up, I have a 1-2 seconds black screen.
RE: [KERNEL][DEV][ALPHA] AlterNdromadus 3.0.x KitKat CM11 | AOSB [26/02/14]
bradley_e_smith said:
I would be interested. I have compiled the lastest flinny merged with the lastest cyanogen frameworks. It boots but the camera doesn't work. So I have been looking further, but still playing around. I need to increase my virtual linux box diskspace, so I am working on reconfiguring it b/c of lack of diskspace.
Click to expand...
Click to collapse
I'm gonna try Paranoid Android, CM10.2 (Android 4.3) base unless anyone has objections to 4.3, it was stable and working as far as I remember. I don't know if 4.2.2 can be used for PA anymore.
arunal_123 said:
I would love to see AOSP KK rom for our device. Just plain and simple.....(thats just my opinion, dont know about others)
Thanks...
Sent from my HTC Vision using xda app-developers app
Click to expand...
Click to collapse
I would love pure AOSP too but unfortunately I don't have the expertise to get it working, I'm gonna try something simpler.
Kéno40 said:
In fact I don't use the lockscreen so when I tackpad wkae it, I arrive to the homescreen. But- I notice with it a little latency / black screen for less than half a second, but noticeable.
I cut Synchro during night because of the wifi problem. On the morning I put it back. It goes to slleep (the phone, not me ! ). If I wake up, I have a 1-2 seconds black screen.
Click to expand...
Click to collapse
Which ROM are you using? I think these might be issues with Flinny's alpha 1/2.
a.s.j said:
And how about BT call audio? Is it working correctly with your Kernel? It is the only think I am missing wiht all the KitKat ROMs and it is definetely Kernel drivers fault... to be honest... the only roms that had it working since GB were those of 4.2.2...
And for me it would make a big help for my phone usage, cause I spend lot of the time in the car...
Click to expand...
Click to collapse
If it doesn't work with the default kernel then it won't work with this.
TO EVERYONE: UPDATE 26/02/14: Latest Download It has 369MB of memory available to user
HTCDreamOn said:
Which ROM are you using? I think these might be issues with Flinny's alpha 1/2.
Click to expand...
Click to collapse
Alpha 3 since weeks and with it, I don't have this latency.
I reflashed Am=lpha 3 over and problem's gone!
Kéno40 said:
Alpha 3 since weeks and with it, I don't have this latency.
I reflashed Am=lpha 3 over and problem's gone!
Click to expand...
Click to collapse
That's very weird, no-one else is having that problem. What kernel settings are you using?
To everyone: UPDATE (again): https://drive.google.com/uc?export=download&id=0B6rld7atb8yHYXBDdUxMX2NacU0
Also, would people want Paranoid Android based on 4.2.2 or 4.3?
HTCDreamOn said:
That's very weird, no-one else is having that problem. What kernel settings are you using?
Click to expand...
Click to collapse
It was on V18.
Tried V19, better. Less latency but tonight I had a black screen on the 1st incoming call I had and I missed it.
Went bak on Alpha3...

Categories

Resources