I was going to switch from [ROM][5/20/12] AOKP KF Edition Build 36 by Lithium 76 which works perfectly, except for no USB mass storage mode. I'm going to go t a CM9 build, but there appears to be two, and I wonder if anyone knows if there is a difference.
There is this one in the development section:
[ROM] Vanilla CM9 Unofficial builds with 3.0 kernel Trojan38
On this thread I'll put my unofficial CM9 builds. They are fully vanilla, except for the volume slider in the status bar, they are exactly the same as Hashcode builds and they include the latest CM source changes. According to this, the issues and bugs are exactly the same.
Click to expand...
Click to collapse
And then there is the ROM from Hashcode himself hiding in his Kernel thread, cm9-kfire-3.0-hashcode-05-26.
I notice that the file names are different when I download them, and the file sizes are also not the same, some I'm wondering if they are really identical as Trojan38 says.
Any takers?
hashcodes rom is here http://forum.xda-developers.com/showthread.php?t=1591850 I believe it gets all the extra bug fixes first I tried it it very smooth but if you liked aokp try this one http://rootzwiki.com/topic/23717-rom5202012unofficial-aokp-build-36-for-kindle-fire/ mass storage is working.
Vanilla is barebones just the basics
Related
So, what's the difference between "4.0.4 merged into build" vs true 4.0.4 AOSP builds?
And the same question for kernels with "4.0.4 merged into build" vs true 4.0.4 kernels?
Will it get better when the devs are going to build from 4.0.4 source from the ground up?
Cuz until now I'm not really that impressed with the 4.0.3/4 "hybrid" builds (i.e. I find LiquidSmooth v1.2 a lot smoother/ faster/ better on battery than the AOKP b29 "4.0.4 merged" build)
Just curious
It means they moved their customizations to 4.0.4????
So if you are not impressed, it has nothing to do with their merges. It has to the do with the rom itself.
adrynalyne said:
It means they moved their customizations to 4.0.4????
So if you are not impressed, it has nothing to do with their merges. It has to the do with the rom itself.
Click to expand...
Click to collapse
Thanks for your prompt answer
So - it's not the other way around, like they optimized their roms with implementing 4.0.4 optimizations?
You mean like Romanbb already took the 4.0.4 source and implemented his customizations?
Just trying to learn here
Ti2 said:
Thanks for your prompt answer
So - it's not the other way around, like they optimized their roms with implementing 4.0.4 optimizations?
You mean like Romanbb already took the 4.0.4 source and implemented his customizations?
Just trying to learn here
Click to expand...
Click to collapse
Ok so, this is how we do it, usually. We have out own customized repos, and then we sync with AOSP. So everything is the current AOSP tree it is synced to, other than the customized repos.
What we do then, is diff our changes to the current 4.0.4 code and add them back, and then re-sync our customized repos.
Some roms sync from multiple sources. For example, AOKP syncs from AOSP, custom repos and Cyanogenmod. So if CM is not updated to 4.0.4, neither is aokp, to certain degrees (I am sure CM is).
I don't know about Liquid, but we (Team BAMF) sync directly and only from aosp and our own custom repos. We just finished the switch to 4.0.4.
So if you find Liquid better, its not to do with 4.0.4 and everything to do with the rom
Cheers mate, thanks for the insight it's very much appreciated
I just looked up your thread - when will your new 4.0.4 rom be up? I'll try it - I'm ready for a shift hehehe
Ti2 said:
Cheers mate, thanks for the insight it's very much appreciated
I just looked up your thread - when will your new 4.0.4 rom be up? I'll try it - I'm ready for a shift hehehe
Click to expand...
Click to collapse
There are some things in the work (besides 4.0.4) that need to be finished yet, but I would say it won't be much longer.
adrynalyne said:
Ok so, this is how we do it, usually. We have out own customized repos, and then we sync with AOSP. So everything is the current AOSP tree it is synced to, other than the customized repos.
What we do then, is diff our changes to the current 4.0.4 code and add them back, and then re-sync our customized repos.
Some roms sync from multiple sources. For example, AOKP syncs from AOSP, custom repos and Cyanogenmod. So if CM is not updated to 4.0.4, neither is aokp, to certain degrees (I am sure CM is).
I don't know about Liquid, but we (Team BAMF) sync directly and only from aosp and our own custom repos. We just finished the switch to 4.0.4.
So if you find Liquid better, its not to do with 4.0.4 and everything to do with the rom
Click to expand...
Click to collapse
Have you released a 4.0.4 rom mate?
Stretlow said:
Have you released a 4.0.4 rom mate?
Click to expand...
Click to collapse
We have merged with 4.0.4, but we havent released an update yet, no.
Anyone working on a plain old vanilla Android 4.0 port? I'm currently using a CM9 build, but I personally prefer vanilla experiences when it comes to OS's.
I'm not certain but I remember seeing that someone had ported AOSP for the Fire a while back and it has just recently been updated with the 3.0 kernel.
Look around the development forums to see what you can find. I'm pretty sure I saw something about it either in one of the AOKP threads or the 3.0 kernel thread.
Can anyone point me to where I can find this, if it exists? I've looked everywhere.
Hashcode said:
Added the unofficial NIGHTLY server info in the OP.
Every night, this build is generated automatically from CM sources using the latest kernel.
NIGHTLY DOWNLOADS
Click to expand...
Click to collapse
there you go
It looks like CondemnedSoul's Kangdemnation v5 is the only ROM with the rotating softkey fix. Aeroevan's unofficial CM9 Rom used to have it but it hasn't been implemented in his past few releases. Also, the newer CM9 and CM10 Roms that have been released also don't have this fix (probably because they use Aeroevan's Rom as a base). Anyway, if someone can point me or set up a flashable zip file that we can install on top of the newer AOSP Roms, it'll be definitely appreciated! :highfive:
P.S.: I was told to put it here so excuse me if I posted the same question in another section :cyclops:
GeoFX said:
It looks like CondemnedSoul's Kangdemnation v5 is the only ROM with the rotating softkey fix. Aeroevan's unofficial CM9 Rom used to have it but it hasn't been implemented in his past few releases. Also, the newer CM9 and CM10 Roms that have been released also don't have this fix (probably because they use Aeroevan's Rom as a base). Anyway, if someone can point me or set up a flashable zip file that we can install on top of the newer AOSP Roms, it'll be definitely appreciated! :highfive:
P.S.: I was told to put it here so excuse me if I posted the same question in another section :cyclops:
Click to expand...
Click to collapse
If the suggestion I gave you in the other thread didn't work then there isn't currently a tool available. So maybe someone will be nice and make it for you, but I wouldn't hold my breath.
gtdtm said:
If the suggestion I gave you in the other thread didn't work then there isn't currently a tool available. So maybe someone will be nice and make it for you, but I wouldn't hold my breath.
Click to expand...
Click to collapse
Yeah I responded to you in the other thread but that was deleted from the section. The fix you mentioned only fixes the issue with the softkey lights turning off really quickly instead of turning off when the screen turns off. It references another link where you can download some libraries but it's missing the key library to make fix the issue.
Thanks anyway!
Aero did have it working in most of the older cm9 builds and if you don't mind gb I believe he has them on his cm7.2 build. At the moment I know he is working mostly on cm10 across a few devices and he just recently got married so since the soft keys not rotating doesn't prevent them from working it is kind of far down on the list of things to work on. Just have patience I am sure they will be rotating soon enough as aero has done a fantastic job so far.
Sent from my vivow using Tapatalk 2
has anyone or can anyone port a newer version of AOKP for the DHD/Inspire? like milestone 1 or whichever one is newest? I personally only like aokp and not too fond of the aosp or aospx. I flashed Pacman rom but had too many problems with it.
so if anyone can port one it would be GREATLY appreciated.
thanks a lot
DesertEagleSlim said:
has anyone or can anyone port a newer version of AOKP for the DHD/Inspire? like milestone 1 or whichever one is newest? I personally only like aokp and not too fond of the aosp or aospx. I flashed Pacman rom but had too many problems with it.
so if anyone can port one it would be GREATLY appreciated.
thanks a lot
Click to expand...
Click to collapse
You mean AOKP Android 4.2? We've just got an AOSP based 4.2 ROM, so I'd just be paitent for a AOKP based follow up. If not, maybe you can suggest it to synergy or RandomBlame? I believe RandomBlame already has a 4.2 ROM, but it's in its baby stages as of yet.
no a JB version 4.1 im back to running aokp release 7 from the github. but hasnt been a new one since like September.
DesertEagleSlim said:
no a JB version 4.1 im back to running aokp release 7 from the github. but hasnt been a new one since like September.
Click to expand...
Click to collapse
RandomBlame is on Release 30 now, look for JellyTime in the Development forum
I don't know about 4.2 AOKP, but if it's options you want you could try cfX 4.2.
I tried aosp ROMS and cfx 4.1 but I don't like them as much as AOKP for some reason. Although I have not tried cfx 4.2 yet. Was waiting for Bluetooth to work. Also I've tried jellytime aosp and I always come back to aokp. I ran Icecoldsandwich for the longest time but I want to stay on JB and not ICS. If I actually had the time (kids,work,wife) I would try porting a newer aokp over to dhd/inspire myself but I never have time. Even dropping a deuce is apparently a "team sport" according to my kids. LOL.
bump?
cfX bluetooth works now, if that is what's still preventing you from using it.
And just today: http://forum.xda-developers.com/showthread.php?t=2113047.
DesertEagleSlim said:
I tried aosp ROMS and cfx 4.1 but I don't like them as much as AOKP for some reason.
Click to expand...
Click to collapse
The reason is very obvious one
AOSP - clean unbranded stock android
AOKP - unbranded android with cleanly built in to settings menu additional features like CPU OC, status bar tweaks etc.... with everything else as close as possible to AOSP.
Sent from my HTC Desire HD using music player
prayers answered just the other day.
forum.xda-developers.com/showthread.php?t=2113047
Thank God. if I knew how to Port and had the time I would have done it myself. but major thanks go to PipelinerArd for the ROM.
Hey!
I've been wondering if i should start using the stock nightly builds over get.cm,
FXP hasn't been giving out detailed logs for the xperia arc, so i guess there are no fixes done to it? cause all i see are *latest cm 9.1/10
So do older fixes gets pushed to newer FXP CM builds or are they already fixed on the official cyanogen builds?
FXP is the team, who develops CM for Xperia devices.
So, what you see on the CM website, is made by FXP team.
You should know i guess that fxp team are the official cyanogen maintainers for xperia devices so u wudnt notice much difference in these ROMs. Regarding the nightlies, every nightly has newer fixes/patches and older fixes are naturally included as well..
Someguyfromhell said:
FXP is the team, who develops CM for Xperia devices.
So, what you see on the CM website, is made by FXP team.
Click to expand...
Click to collapse
Based on my post, you ahould know that i have understood all of that prior to this post. Please read my post and not just the topic. FXP builds haven't been pushing log fixes for the arc recently but a rebranded fw off stock cm. Get.cm has newer nightly builds buf fxp only uses a week or even later builds for their newer releases.
So i'm still confused... Is the rom of fxp the same as the nightly builds, or the same people working on those roms?
Now I'm using the nightly build, I tried it because at first i got issues with the fxp build, issues were: keyboard fc's and no wifi, but with nightly I reflashed wifi modules(lupus) after installing rom and that does seem to work, so perhaps also would work on fxp but don't know because didn't try yet. Keyboard issue persists, so i flashed xperia V keyboard which I like better anyway(swype).
I come from ultimate HD but i like cm10 more, even though battery is better on uhd. What i like is lockscreen, sms popup and ant+, etc... I don't like camera app and no out of the box digital clock widget I know some of these can just be modded and flashed over except ant+ whick is key to me because i bought a heartrate monitor.
Sorry I made it a cm10 vs uhd thread
dahakske said:
So i'm still confused... Is the rom of fxp the same as the nightly builds, or the same people working on those roms?
Now I'm using the nightly build, I tried it because at first i got issues with the fxp build, issues were: keyboard fc's and no wifi, but with nightly I reflashed wifi modules(lupus) after installing rom and that does seem to work, so perhaps also would work on fxp but don't know because didn't try yet. Keyboard issue persists, so i flashed xperia V keyboard which I like better anyway(swype).
I come from ultimate HD but i like cm10 more, even though battery is better on uhd. What i like is lockscreen, sms popup and ant+, etc... I don't like camera app and no out of the box digital clock widget I know some of these can just be modded and flashed over except ant+ whick is key to me because i bought a heartrate monitor.
Sorry I made it a cm10 vs uhd thread
Click to expand...
Click to collapse
Fxp is the team. CM are stable builds while nightly are more unstable with untested fixes and bugs.
Sent from my soon-to-be bricked Neo V