Related
This is a very pre-alpa build of AOKP ROM.Known serious issue are h/w buttons,not all are working correctly,use onscreen ones.More functional update will be very soon
Credits
Goes to everybody working on ICS for hero and heroc
P.S I took updater-script from HeroICS ROM,hope guys wouldn't shot me
http://www.mediafire.com/?2qb7fk2w8dyiibw
:/
ported from where? more details..
1ceb0x said:
:/
ported from where? more details..
Click to expand...
Click to collapse
This one is ported from WFS,now compiling new wersion from sources
not bad few issues\recommendations after installing:
Max speed of 710 is a bit keen (default of 691 ?)
Recommend latest Nova Launcher (1.2 - lots of bug fixes)
SuperSU rather than SuperUser
Remove pointer following boot-up
Updater script saying installing CM 4.0.3 needs edit as 4.0.4 is installed ...
Advise that gapps are not included
Please dont take this as criticism, I certainly couldn't do this (tho i might have a bash somepoint)
I'd be happy to be guinea pig for testing further builds if you'd to pm me.
awesome! glad to see you guys have an aokp port now.
about the hardware buttons, wouldnt that have to do with the /usr folder? try to replace key layout related stuff with ones from heroics, and it should work.
if you need any help let me know
Download link not work correct..and one question if i understand good this is new port from new HTC Desire C ROM....ICS 4.0.4?
Thanks
P.S.Good will be to make your tread with more exact info like ROM version images from phone,change log and e.g
What works and what not?
jogai said:
What works and what not?
Click to expand...
Click to collapse
Hardware buttons except for menu, home and back (correct me if I'm wrong) don't work. However Keynrtracker (or check here for more information and keynrtracker.apk) resolves all the buttons. The problem doesn't seem to rely in /system/usr/keylayouts, but somewhere else.
Haven't had time to try this ROM out any further.
Build now maintained under:
http://forum.xda-developers.com/showthread.php?t=1795990
helllo xda, many of you might have heard that I AM building CM10 from source and I have heard the we need the (kernel,gpu.....) drivers,
now broadcom released them and this is good.
my question is : how to use them ? pls help me
Many of u have heard?
Phone Slow? go ------>HERE<------
_____________________________________
"All my life I had one dream to achieve many many goals"
As I said earlier,
Building from source is better than porting.
But... if you're building from source , you'll be stuck having the same bugs as CM9 by whitexp has.
Sources which broadcom released (actually patch files, not actual source) are mostly meant for CM7. That's why whitexp couldn't proceed with CM9. It you see the madteam forum, and check whitexp's comment on asking proper release of sources , you'll get to know what I'm trying to say.
Also,
I did say earlier that whitexp made CM10 via sources and had end up getting the same bugs as CM9. Try fixing CM9 , if possible
tingtingin said:
Many of u have heard?
Phone Slow? go ------>HERE<------
_____________________________________
"All my life I had one dream to achieve many many goals"
Click to expand...
Click to collapse
Yes I have made a thread for that
Sent from my GT-S5360 using xda premium
Gamer R said:
As I said earlier,
Building from source is better than porting.
But... if you're building from source , you'll be stuck having the same bugs as CM9 by whitexp has.
Sources which broadcom released (actually patch files, not actual source) are mostly meant for CM7. That's why whitexp couldn't proceed with CM9. It you see the madteam forum, and check whitexp's comment on asking proper release of sources , you'll get to know what I'm trying to say.
Also,
I did say earlier that whitexp made CM10 via sources and had end up getting the same bugs as CM9. Try fixing CM9 , if possible
Click to expand...
Click to collapse
They cant work for cm10
Sent from my GT-S5360 using xda premium
mohamedrashad said:
They cant work for cm10
Sent from my GT-S5360 using xda premium
Click to expand...
Click to collapse
Maybe, maybe not. Patched blobs Broadcom made available for CM7 could be linked to specific version of libraries in CM7 that could have changed in CM9 or CM10, the only way to know is trying to build CM10 using this blobs, they must be placed somewhere under vendor/samsung/totoro/propietary/lib
You better read the whole Getting Started section here first, then the thread from Whitexp about building CM7 and adapt it for CM10.
It will be useful if you had previous experience building succesfully the Linux kernel for any architecture or something like Linux From Scratch, a good understanding of how a Linux system works is critical to be able to set up the environment and do a succesful build.
Be prepared to spend a lot of time reading, hunting and fixing missing dependencies! Good luck.
celisdelafuente said:
Maybe, maybe not. Patched blobs Broadcom made available for CM7 could be linked to specific version of libraries in CM7 that could have changed in CM9 or CM10, the only way to know is trying to build CM10 using this blobs, they must be placed somewhere under vendor/samsung/totoro/propietary/lib
You better read the whole Getting Started section here first, then the thread from Whitexp about building CM7 and adapt it for CM10.
It will be useful if you had previous experience building succesfully the Linux kernel for any architecture or something like Linux From Scratch, a good understanding of how a Linux system works is critical to be able to set up the environment and do a succesful build.
Be prepared to spend a lot of time reading, hunting and fixing missing dependencies! Good luck.
Click to expand...
Click to collapse
thanks
Hi!
It has come to my attention that videos played in this ROM (VGA+) are getting less stuttter / lag. Even without the modified libraries.
As I have checked the date when the libraries (OMX) were created, it was way back 2008.
if I applied the updated libs of the Adreno 200 for ICS ARMv6, the lag is getting obvious, its like there is a sudden freeze in frames.
I don't know for now what's going on here (libstagefright, OpenMAX, and the Adreno 200 drivers) in the cm9.1 alpha 9 rom itself.
Has anyone tried this ROM? (This came from google)
https://code.google.com/p/cm9-wildfire-s/downloads/list
maybe there is a way on putting JDroid's and Gangster41's modified files here, but for now, I don't know what files to put and what's not, coz I'm no good at modifying the libraries. (No knowledge about linux / android programming)
Everytime I put the modified OMX libs, video acceleration gets worse.
Even the Adreno 200 Lib updates for ICS! :/
hope this info somehow helps the issue on the HW acceleration for ARMv6.
I hope the solution will be found soon, so we will have a fully functional cm9!
Where did you find adreno200 libs for armv6 ics?
thepastormarty said:
Hi!
Has anyone tried this ROM? (This came from google)
https://code.google.com/p/cm9-wildfire-s/downloads/list
Click to expand...
Click to collapse
ummmm... it's our CM 9.1 from modpunk, it's core of all (almost) ICS ROMs in dev thread. I think you just don't understood something.
EdikNeznanov said:
ummmm... it's our CM 9.1 from modpunk, it's core of all (almost) ICS ROMs in dev thread. I think you just don't undertood something.
Click to expand...
Click to collapse
yeah you're right. Thanks anyway. I'll try to look deeper into the files then.
polfrank said:
Where did you find adreno200 libs for armv6 ics?
Click to expand...
Click to collapse
sorry for not replying.
somewhere in the xda afaik.
I have attached the necessary files for the ICS. (The adreno 200 drivers, dont forget to delete the libGLES_android.so.. they said, deleting that file will increase performace, as it now relies on hardware, and the OMX libraries done by gangster41)
As far from what I have read from the android devs on ics armv6, video recording was somehow possible, but in h263, ammb (vid/audio) format.
see here (http://forum.xda-developers.com/showthread.php?t=1860561&page=5)
Hello! Has there been any progress concerning this matter? I tried modifying things some time ago but I failed..
As I saw, thehacka1 has released a rom(icysnap) with better video playback(i hope it s not my idea).
Furthermore I thought that the owl project team could give a little help here, although they re focused on cm10.1 doing a good job...
Are there any chances of improvement or should I abandon hope...? :/
I copied system/lib folder from MIUI v4 by Henry_01 (which has working video playback) into SlimSandwich and video was working correctly. I just thought I should share. So, we have working video playback on ics!
This thread is for developers to discuss bringup for the 3.4 jb kernel on various devices in the Nitro HD "iproj" family. These include P930, SU640, VS920, and LU6200.
Downloaded the su640 jb sources and compiled for ijb_skt. Tried to boot on my "gimpy" p930. No boot.
Enabled console framebuffer and snapped a pic just before reboot. It's complaining about fatal regulator error (msm_rpm_err_fatal). Anyone else get this far and/or see anything similar?
If anyone wants to use a console framebuffer, here's how:
1. Enable CONFIG_FRAMEBUFFER_CONSOLE and CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY.
2. Modify console_setup() in kernel/printk.c. Delete the function body and replace it with just "return 1".
Be prepared with a camera to snap an image of the screen before it reboots.
tdmcode said:
Downloaded the su640 jb sources and compiled for ijb_skt. Tried to boot on my "gimpy" p930. No boot.
Enabled console framebuffer and snapped a pic just before reboot. It's complaining about fatal regulator error (msm_rpm_err_fatal). Anyone else get this far and/or see anything similar?
If anyone wants to use a console framebuffer, here's how:
1. Enable CONFIG_FRAMEBUFFER_CONSOLE and CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY.
2. Modify console_setup() in kernel/printk.c. Delete the function body and replace it with just "return 1".
Be prepared with a camera to snap an image of the screen before it reboots.
Click to expand...
Click to collapse
Working on bringing this up for the vs920 as that's the only one I've got.
So far I've copied the ijb_skt bits over to ijb_vzw and used a bit of grep/sed magic to replace the skt bits to vzw in the files, and add ||'s for ijb_vzw wherever ijb_skt was a condition. I'm getting successful builds But they won't boot (yet). I'll keep you updated. I'll be pushing to here as I make any changes/progress.
Got past the RPM error with a hack.
In arch/arm/mach-msm/clock.c @ clock_late_init(), remove the list_for_each_entry_safe block.
Obviously, this is just a hack. We need to figure out what's causing the issue.
Next up is the display. The kgsl driver in this kernel does not match the kgsl libs in CM10. I'm going to download the 4.1 flashable rom from this forum and see if I can update the drivers to match.
I think kgsl is happy now. Next up is the msm video driver.
tdmcode said:
I think kgsl is happy now. Next up is the msm video driver.
Click to expand...
Click to collapse
Man, You're a machine... Here I'm still trying to get something that'll boot past the LG logo lol
Got boot animation and home screen. Then it reboots after a minute or so. The shell in adb gets really laggy right before reboot. Likely causes are a kernel hardware driver failing somewhere or a massive memory leak.
I see touch events logged but by the time the home screen shows I think it's too far gone to act on them. Same with hard buttons and capacitive buttons.
Oh .. by the way I'm using CM10 not CM10.1. It matches better since it's a 4.1 kernel.
Gotta stop for the day. Here's what I've got so far...
http://androidrepo.net/roms/quattrimus/iproj/iproj-3.4-checkpoint1.diff
tdmcode said:
Oh .. by the way I'm using CM10 not CM10.1. It matches better since it's a 4.1 kernel.
Gotta stop for the day. Here's what I've got so far...
http://androidrepo.net/roms/quattrimus/iproj/iproj-3.4-checkpoint1.diff
Click to expand...
Click to collapse
Nevermind. I thought the link I just posted was for someone working on another 3.4 kernel... it wasnt.
*Edit*
I'm obviously doing something horribly wrong by trying to borrow/reuse the ijb_skt files, because I can't get a kernel that even tries to boot (gets off the first LG logo)... and don't really have the know-how to reconstruct the files.
Didn't get a chance to work on this today I was busy on another project. But I'll be back on it Monday for sure.
@Yoinx: you are going to have a harder time with the vs920 because the hardware is different and it won't boot the su640 kernel.
I do not know the approach of developing cm10 kernel from stock kernel.
According to miroslav_mm,
http://forum.xda-developers.com/showpost.php?p=42075037&postcount=40
I tried using stock 3.4 zImage + cm10 ramdisk + required libs. It boots with blackscreen
lyfkevin said:
I do not know the approach of developing cm10 kernel from stock kernel.
According to miroslav_mm,
http://forum.xda-developers.com/showpost.php?p=42075037&postcount=40
I tried using stock 3.4 zImage + cm10 ramdisk + required libs. It boots with blackscreen
Click to expand...
Click to collapse
You need to change the kgsl and msm video code to match cm10. See my patch.
tdmcode said:
You need to change the kgsl and msm video code to match cm10. See my patch.
Click to expand...
Click to collapse
The boot.img provided by @navik
Same approach, i.e. stock zImage + cm10 ramdisk
I can boot into home screen with my su640 now.
Signal, wifi work.
but laggy, blinking screen(check hw overlay setting in option can fix), no sound, no bootanimation (black screen)
----------------------------------------------------
edit:
Merged your patch
able to see boot animation
Sent from my LG-LU6200 using xda premium
LU6200 jb source is released
https://wws.lg.com/global/support/opensource/opensourceList?types=ALL&search=lu6200
lyfkevin said:
I do not know the approach of developing cm10 kernel from stock kernel.
According to miroslav_mm,
http://forum.xda-developers.com/showpost.php?p=42075037&postcount=40
I tried using stock 3.4 zImage + cm10 ramdisk + required libs. It boots with blackscreen
Click to expand...
Click to collapse
I finished my new build CM10, on 3.4 kernel, with new JB camera libs, and other new properitary stuff. Dont have any problem with 3.4 kernel on CM10 (4.1.2), I didnt patch any KGSL driver, sources from my Github working, it dont have last updates but it working. I cant upload new ROM for test now, I dont have internet at home, when I fix my provider I will upload it.
lyfkevin which display libs did you use? Did you complete build CM10 with new kernel and headers?
Take this variant:
1.) display libs: copybit.msm8660.so, gralloc.msm8660.so, hwcomposer.msm8660.so, libgenlock.so, libhwcexternal.so, libhwcservice.so, libmemalloc.so, libqdutils.so, libtilerenderer.so, and libqdMetaData.so take from official STOCK 4.1 + take Adreno libs with MetaData support from my last CM10 or from STOCK 4.1 (older version) = its working on CM10
miroslav_mm said:
I finished my new build CM10, on 3.4 kernel, with new JB camera libs, and other new properitary stuff. Dont have any problem with 3.4 kernel on CM10 (4.1.2), I didnt patch any KGSL driver, sources from my Github working, it dont have last updates but it working. I cant upload new ROM for test now, I dont have internet at home, when I fix my provider I will upload it.
lyfkevin which display libs did you use? Did you complete build CM10 with new kernel and headers?
Take this variant:
1.) display libs: copybit.msm8660.so, gralloc.msm8660.so, hwcomposer.msm8660.so, libgenlock.so, libhwcexternal.so, libhwcservice.so, libmemalloc.so, libqdutils.so, libtilerenderer.so, and libqdMetaData.so take from official STOCK 4.1 + take Adreno libs with MetaData support from my last CM10 or from STOCK 4.1 (older version) = its working on CM10
Click to expand...
Click to collapse
is your 3.4 kernel compatible with your previous cm10 builds? a lot less MBs, easier to upload.
tdmcode said:
This thread is for developers to discuss bringup for the 3.4 jb kernel on various devices in the Nitro HD "iproj" family. These include P930, SU640, VS920, and LU6200.
Click to expand...
Click to collapse
Exece me,I want to build aosp of su640 based on LG offical open sourse. I have try serverl times,but end with failure.
Should you give me some advices or guide? Thanks for your reply!
navik said:
Exece me,I want to build aosp of su640 based on LG offical open sourse. I have try serverl times,but end with failure.
Should you give me some advices or guide? Thanks for your reply!
Click to expand...
Click to collapse
You cannot do this. There are many changes to files which are not gpl .
It takes a lot of work to make an aosp ROM. You need most of the cm hardware changes and various other changes through the system. I have done it for 4.1 with only one bug: the front camera does not work. I have not tried with 4.2 yet.
tdmcode said:
You cannot do this. There are many changes to files which are not gpl .
It takes a lot of work to make an aosp ROM. You need most of the cm hardware changes and various other changes through the system. I have done it for 4.1 with only one bug: the front camera does not work. I have not tried with 4.2 yet.
Click to expand...
Click to collapse
Thanks，but I want to build aosp based on LG open sourse instead of porting.
Do you have read the guide of LG offical open sourse？It say we can build stockrom based on LG official open sourse and Google android open sourse，we just need to copy LG open sourse into android open sourse. then breakfast and lunch.but I fail，I think I didn't pick up the guide of LG open sourse 。Do you have some good advices？Thanks again！
Sent from my LG-SU640 using xda premium
Introduction
This is a test version of OmniROM with SGX DDK 1.9 graphics drivers, as well as many OMAP-related kernel updates. No, this isn't 3.4, but a LOT of TI updates were packed into the kernel. Currently, this is only for maguro, but anyone can build it for toro/toroplus with the sources.
Click to expand...
Click to collapse
Features
The ROM and the kernel has a stock feeling - no mods were added.
Most notable new features:
- SGX DDK [email protected]
- GPU governor
- Enabled 384 MHz GPU frequency (as a part of the OMAP updates)
- Tons of background changes for the kernel
Click to expand...
Click to collapse
Important notes
Camera and OMX is not working yet! This turned out to be a harder task for me to fix than implementing the new GPU drivers...
Other bugs are not known yet, but there may be some! Bug reports are welcome.
Thanks to everyone who helped me, especially Hashcode, as I used his repos as an example on how to set up things properly.
Click to expand...
Click to collapse
FAQ
How can I install this?
Just flash the ROM zip (and optionally GAPPS), and you're done.
Can I install this on top of Omni roms?
Yes, you should be able to do so without data loss.
Can I revert to non-1.9 Omni after this without data loss?
Yes.
Is this faster than the current ROMs/kernels?
As this is a stock-like ROM and kernel, not necessarily - there are no optimizations, etc added.
However, if one adds the optimizations used on current custom roms and kernels, this should be faster than them.
Can I install another kernel?
No, the new drivers require the ROM and the kernel side to match each other. Only this combination will work.
When will you fix camera?
I'm trying, but I don't have much success...
Can I help?
Sure, I appreciate any help, as I'm running out of ideas on how to fix camera and OMX.
Can I build this stuff myself?
Of course - everything needed is on my github. You'll need the following repos added to your Omni sources:
omni_android_device_samsung_tuna
omap (newpvr2 branch)
proprietary_vendor_samsung_tuna
Click to expand...
Click to collapse
XDA:DevDB Information
OmniROM DDK 1.9 Test, ROM for the Samsung Galaxy Nexus
Contributors
Ziyan
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Based On: OmniROM
Version Information
Status: Testing
Created 2014-07-13
Last Updated 2014-07-13
Where is the download link?!
Sent from my Galaxy Nexus using Tapatalk
aliesz said:
Where is the download link?!
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Click on the downloads button above the thread title
If you're on tapatalk you'll need to go to Web view..
To see the download
Sent from the "DOG" pound
Yes I found it just seconds ago
Sent from my Galaxy Nexus using Tapatalk
Also OP there 3 types of gnexes...
You might want to add to the OP which one it is for
Sent from the "DOG" pound
cujo6801 said:
Also OP there 3 types of gnexes...
You might want to add to the OP which one it is for
Sent from the "DOG" pound
Click to expand...
Click to collapse
Thanks for the suggestion, added it to the introduction text.
Amazing! I will try out tommorow
I've installed it and it feels smooth, I've not encountered any bugs yet. Have you tried removing "kitkat workarounds" from frameworks/native?
Thanks for your awesome work
Nice work! Seems a lot more responsive although it may be placebo effect.
Thanks for posting this, I'm going to try building for toroplus, since we seem to get left out of the excitement so often. My internet connection is slow and so is my computer, so you will probably have everything fixed before I get a chance to even look for bugs.
Great work! I hope you manage to get camera working soon.
Amazing work bro, wishing u best of luck !!
I'm on F2Fs otherwise would have tested this asap...
Awesome work!
Thanks for the amazing work you've brought to the gnex, but since i'm on F2FS i was wondering if you could make a F2FS compatible version of this rom?
matoushybl said:
I've installed it and it feels smooth, I've not encountered any bugs yet. Have you tried removing "kitkat workarounds" from frameworks/native?
Thanks for your awesome work
Click to expand...
Click to collapse
Yeah, but the glitches are still there. Actually, that may be a bug in android itself (it affects a lot of devices), they may have fixed it on L... and those workarounds are really not important, as the problem only comes when taking screenshots. And since android takes screenshots for the rotation animation, etc, those glitches appear there as well. The workarounds just force it to take screenshots on CPU-path, they don't change anything else.
I think they fixed it in DDK 1.12 (which is the next version after 1.9), but that's another story, as I think it does not support our GPU (but it may in the future).
apollo07 said:
Thanks for the amazing work you've brought to the gnex, but since i'm on F2FS i was wondering if you could make a F2FS compatible version of this rom?
Click to expand...
Click to collapse
Not yet, I'm focusing on camera for now
Ziyan said:
The workarounds just force it to take screenshots on CPU-path, they don't change anything else.
Click to expand...
Click to collapse
How about using SurfaceFlinger's Sync framwork now?
https://github.com/omnirom/android_...mmit/d677ae87b2466b03a6ca1cda6ee532c6ba407f8c
@Ziyan https://gerrit.omnirom.org/#/c/8141/
https://gerrit.omnirom.org/#/c/8156/ cherypick those and recompile
Ziyan said:
Yeah, but the glitches are still there. Actually, that may be a bug in android itself (it affects a lot of devices), they may have fixed it on L... and those workarounds are really not important, as the problem only comes when taking screenshots. And since android takes screenshots for the rotation animation, etc, those glitches appear there as well. The workarounds just force it to take screenshots on CPU-path, they don't change anything else.
I think they fixed it in DDK 1.12 (which is the next version after 1.9), but that's another story, as I think it does not support our GPU (but it may in the future).
Not yet, I'm focusing on camera for now
Click to expand...
Click to collapse
Ziyan, thanks for the awesome work
It 's possible to have some screenshots?