WARNING THIS ROM IS SO FAR FROM DONE. IF YOU BRICK YOUR PHONE IT IS NOT MY FAULT. BOTTOM LINE YOU HAVE BEEN WARNED!! NO NOOBS!!!!!!!!!!!! THE SCREEN FLICKERS BLACK ALLLOOOTT AND DOES NOT HAVE NATIVE TOUCH (ITS ALMOST LIKE A MOUSE.)
ONLY FOR OVERCLOCKABLE ADMIRES!
KNOW BEFORE FLASHING YOU WILL BE GOING BACK TO WHAT EVER ROM YOU HAVE AS OF NOW. MAKE SURE TO MAKE A BACKUP you will need it
THIS ROM IS PORTED FROM THE SAMSUNG PREVAIL (STILL SAYS PREVAIL IN ABOUT PHONE) IT IS NOT BUILT FROM SOURCE
PHONE CALLING WORKS
EVERYTHING ELSE IS NOT WORKING AS OF NOW. THIS IS VERY MUCH A WORK IN PROGRESS
BUT I AM PUTTING IT UP FOR A FEW REASONS. I WOULD LIKE PEOPLE TO SEE ICS IN ACTION. EVEN WITH THE SCREEN PROBLEMS YOU CAN STILL PLAY WITH ICS. I HAVE BEEN TRYING TO WORK WITH THE KERNEL TO GET THE TOUCHSCREEN TO WORK BUT AM FOR FROM FINSHING. PLEASE TO ANYOTHER DEVS TAKE A LOOK AND SEE IF YOU CAN FIX ANYTHING.
Device(s): Galaxy Nexus, Nexus 7, LG Esteem, LG Revolution, LG Connect, LG Spectrum, Huawei Mercury
Carrier: T-Mobile
Thanks: 195
Thanked 4,315 Times in 1,789 Posts
the touchsreen is kernel related as the touchscreen driver src needs edited. The keymapping files will be needed too as they are diff for each device.
__________________ Official Donate link if you like my work and would like to show your appreciation and support. All donations are greatly appreciated!!
Wait....this might sound really stupid since im pretty stupid...but is the cm9 or a theme with your 2.3.6 rom
Its cm9 android 4.0.3. PG i would really love your help in point me the right way if you know anything on the topic. If i could get this thing to stop flickering this would be semi usable.
Color me stupid, as well, but can someone explain what "kang" is? I assume its some kind of port or something? I don't know, I only ever saw it here and I also saw it on the threads for CM9 on the Optimus S.
Color me stupid, as well, but can someone explain what "kang" is? I assume its some kind of port or something? I don't know, I only ever saw it here and I also saw it on the threads for CM9 on the Optimus S.
I might not be right but i think it is like porting but mostly like dragging and dropping files ... Replacing / copy nd paste....
Device(s): Galaxy Nexus, Nexus 7, LG Esteem, LG Revolution, LG Connect, LG Spectrum, Huawei Mercury
Carrier: T-Mobile
Thanks: 195
Thanked 4,315 Times in 1,789 Posts
Quote:
Originally Posted by Boraichee
Its cm9 android 4.0.3. PG i would really love your help in point me the right way if you know anything on the topic. If i could get this thing to stop flickering this would be semi usable.
yea the flciker is prolly due to the display drivers (adreno I believe) and the touchscreen drivers not been edited. Sounds like you have touchscreen_legacy (which it needs to be) set tho hence it acting like a mouse pointer atm.
Color me stupid, as well, but can someone explain what "kang" is? I assume its some kind of port or something? I don't know, I only ever saw it here and I also saw it on the threads for CM9 on the Optimus S.
From what I understand, to kang is to take the work of another and include it into your own work/ROM without crediting the source. In the case of ICS Kang ROMs, I believe it is all people dropping each other's work into one ROM without worrying about crediting people and simply pushing out new features to the ROM.
Device(s): Galaxy Nexus, Nexus 7, LG Esteem, LG Revolution, LG Connect, LG Spectrum, Huawei Mercury
Carrier: T-Mobile
Thanks: 195
Thanked 4,315 Times in 1,789 Posts
Quote:
Originally Posted by gaazakid876
I might not be right but i think it is like porting but mostly like dragging and dropping files ... Replacing / copy nd paste....
a dirty port fits that description.
A real port, that being one built from src, requires config files edited for the intended device, the correct props pulled from the device, and it all massaged n buttered up to work correctly with each other. This is still quite a under taken even if using a kanged repo as a base. Not to mention there is no getting around the kernel edits/hacks. IMO almost anyone can do a dirty port if they put the time into it, but it takes a lil skill and knowledge to build from src.
Color me stupid, as well, but can someone explain what "kang" is? I assume its some kind of port or something? I don't know, I only ever saw it here and I also saw it on the threads for CM9 on the Optimus S.
Dont worry bro...I was thinking the exact same thing
Device(s): Galaxy Nexus, Nexus 7, LG Esteem, LG Revolution, LG Connect, LG Spectrum, Huawei Mercury
Carrier: T-Mobile
Thanks: 195
Thanked 4,315 Times in 1,789 Posts
Quote:
Originally Posted by SacredBloodlin
Color me stupid, as well, but can someone explain what "kang" is? I assume its some kind of port or something? I don't know, I only ever saw it here and I also saw it on the threads for CM9 on the Optimus S.
Quote:
Originally Posted by Cuzuaintme
From what I understand, to kang is to take the work of another and include it into your own work/ROM without crediting the source. In the case of ICS Kang ROMs, I believe it is all people dropping each other's work into one ROM without worrying about crediting people and simply pushing out new features to the ROM.
Yea purdy much the word kanged means to rip off some ones else work and not give due credit. Cm lessened the meaning as most unofficial CM ports are technically kanged, but its hard to not give CM crdit as everyone knows who makes CM lol. Dev's just port it different devices, usually from source, but you do have those who 'port' precompiled CM ROM's from other devices. Which IMO is stupid because its src is readily available.
A real port, that being one built from src, requires config files edited for the intended device, the correct props pulled from the device, and it all massaged n buttered up to work correctly with each other. This is still quite a under taken even if using a kanged repo as a base. Not to mention there is no getting around the kernel edits/hacks. IMO almost anyone can do a dirty port if they put the time into it, but it takes a lil skill and knowledge to build from src.
One thing i am good with is building kernels so working on the drivers want be to hard on me. so i need to edit the touchscreen lib files on the system side of things. then the drivers on the kernel level? BTW i do intend to give full credit were it belongs. I never think of kanging as stealing..
Last edited by Boraichee; July 20th, 2012 at 10:26 PM.
Device(s): Galaxy Nexus, Nexus 7, LG Esteem, LG Revolution, LG Connect, LG Spectrum, Huawei Mercury
Carrier: T-Mobile
Thanks: 195
Thanked 4,315 Times in 1,789 Posts
Quote:
Originally Posted by Boraichee
One thing i am good with is building kernels so working on the drivers want be to hard on me. so i need to edit the touchscreen lib files on the system side of things. then the drivers on the kernel level? BTW i do intend to give full credit were it belongs. Ive never think of kanging as stealing..
no need to touch the libs, look in the defconfig for the touchscreen used, and you can look for a thread on XDA on the edits, or even check my github for the commits on my cm9 esteem kernel.
A real port, that being one built from src, requires config files edited for the intended device, the correct props pulled from the device, and it all massaged n buttered up to work correctly with each other. This is still quite a under taken even if using a kanged repo as a base. Not to mention there is no getting around the kernel edits/hacks. IMO almost anyone can do a dirty port if they put the time into it, but it takes a lil skill and knowledge to build from src.
yea the flciker is prolly due to the display drivers (adreno I believe) and the touchscreen drivers not been edited. Sounds like you have touchscreen_legacy (which it needs to be) set tho hence it acting like a mouse pointer atm.
I looked online and saw adreno200 pics drivers in the form of lib files on xda. I added them to the build and it broke the screen all together.
I've been messing with kernel source and trying to back port the screen drivers. I might put up the build I took the picture with but its far from usable. Sucks the screen flickers so much because so much else is working.
Device(s): Samsung Admire (admiral beast with My Admiroid uot theme, Lg motion 4g debloated and 4.04
Carrier: MetroPcs Locked Boots
Thanks: 479
Thanked 45 Times in 32 Posts
Borichee do you have a gtalk or a FB account so i can follow you and pick your brain. kudos on your set goal. amazing how you just "poof" Cm9 coming to an admire near you.lol keep it up and no pressure, all your work is ubber stable and clean. I buy you a beer sometime, pm me.
The Following User Says Thank You to adanmex For This Useful Post:
A real port, that being one built from src, requires config files edited for the intended device, the correct props pulled from the device, and it all massaged n buttered up to work correctly with each other. This is still quite a under taken even if using a kanged repo as a base. Not to mention there is no getting around the kernel edits/hacks. IMO almost anyone can do a dirty port if they put the time into it, but it takes a lil skill and knowledge to build from src.
how do i get all massaged and buttered up? lol....
Not much been trying to get the screen running. Ill post the zip for the hell of it to let all of you flash junkies your fix. Even thou the screen flickers like crazy it is cool to see ics on the admire. Ill post it in a bit but flash at your own risk..
The Following 4 Users Say Thank You to Boraichee For This Useful Post:
Device(s): Samsung Admire, Motorola Xoom, Lg Esteem
Carrier: Not Provided
Thanks: 83
Thanked 47 Times in 43 Posts
Quote:
Originally Posted by Boraichee
Not much been trying to get the screen running. Ill post the zip for the hell of it to let all of you flash junkies your fix. Even thou the screen flickers like crazy it is cool to see ics on the admire. Ill post it in a bit but flash at your own risk..
Not much been trying to get the screen running. Ill post the zip for the hell of it to let all of you flash junkies your fix. Even thou the screen flickers like crazy it is cool to see ics on the admire. Ill post it in a bit but flash at your own risk..
Is The Cm9 Rom Fixed?No Flashing?Running Smooth?If So Where Can I Get The Link To The Rom?
Calm down there buddy, If you read, then you would know that there's still a flicker problem. So no, It's not fully working, but Bo's going to put up an Alpha that we can play with soon.