WARNING: This ROM probably still has intermittent emergency dialing issues. Do not use it for a daily driver when you're out or could need 911 or any emergency number. If you STILL choose to use it at those times, it's your own fault!
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.1.1 (Jelly Bean), which is designed to increase performance and reliability over stock Android for your device.
DO NOT USE AS A DAILY DRIVER
Code:
#include
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear
* war, or the current economic crisis caused by you following these
* directions. YOU are choosing to make these modificiations, and
* if you point your finger at me for messing up your device, I will
* laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review.
Known Issues
Probably intermittent emergency dialing issues (such as 911) like CM7 and CM9
See the rest of the issues here.
Please report new issues here:
http://code.google.com/p/vibrant-cm/issues/list
Downloads
Did you read known issues? No? Go read them.
20120816: Androtransfer.com | MD5: 19c1e1c3440ed593ed6ab98fe1ead4d2
Google Apps: gapps-jb-20120726-signed.zip
How to Install
Upgrading from CM9 or CM7
Do a nandroid backup (just in case)
Wipe & factory reset
Install from ZIP
Reboot
Upgrading from an older version of CM10
Do a nandroid backup (just in case)
Install from ZIP
Optionally install the Google Apps add-on.
Reboot
WARNING: If you use Titanium Backup to backup your apps do not backup system data or system apps.
FAQ
Q: I can't add my Google account!
A: Install the Google Apps package from CWM recovery, linked above. This is standard procedure with CyanogenMod ROMs due to licensing issues with Google.
Q: Will /datadata be in the next version?
A: Keep in mind that this is not a KANG. Read more about /datadata and why it was removed here
Q: How is this different from the other thread in the Development forum?
A: That ROM is a port of an unofficial build of CM10. This is a build of CM10 from sources for the Vibrant.
Q: Do I need the su fix from the other thread?
A: Please refrain from using fixes from that ROM.
Q: Why isn't YYMMDD up yet? It's up on the SGS thread.
A: The versions don't necessarily match up and a change in one may not be in the other.
Changelog
Code:
20120816
* Notification icon animation fix
* /data is now on OneNAND and /system is on MoviNAND (from pawitp)
* Boot animation should now not freeze. (It can still lag though)
* Better lockscreen weather timestamp
* WIPES DEVICE.
20120807
* Another libgps ABI fix
* Back to kill now works.
* Synced merged commits from [url=http://r.cyanogenmod.com/#/q/status:merged+branch:jellybean,n,z]Gerrit[/url]
20120803
* GPS no longer crashes upon toggling and hopefully will be more stable upon 911/emergencies (not sure what would've happened if you called on V8)
* AriesParts now loads.
* Synced repos (merged changes)
v8
* Synced repos (AriesParts now doesnt crash)
* GPS still broken (crashing after a few toggles, so [b]leave it on!![/b])
v7
* Synced repos
* Kernel doesn't ramp anymore while touching (will come back later)
v6
* Froyo RIL fixed (the Unknown Baseband report)
* Froyo GPS libs! (Tell me how it works)
* Kernel OC not crashing now
* Kernel frequency limited to 800mHz+ while touching
* Synced (lockscreen targets, background, etc)
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
Will be sure to try it out later today! Thanks FE.
Since I'm not much of a dev, what exactly is RIL, and what does it do?
Also, all the other functions work? Network/audio/wifi etc? DANG FE, you've been to work
Thank again to everyone who contributed to this!
edit: my chrome is acting up, what is the file size of this download?
As a reminder, I would like the other guys to not spam this thread and keep this as much as to developmental and testing as possible.
Thank FE
Sent from my SGH-T959 using xda app-developers app
Thats good news didnt boot for me either when i built it a couple days ago..
Question about the kernel ramdisk, did you simply use ICS ramdisk but with pawitps areis-common init.aries.rc and init.aries.usb.rc? or were other changes needed?
Thanks Fault xD
xriderx66 said:
Will be sure to try it out later today! Thanks FE.
Since I'm not much of a dev, what exactly is RIL, and what does it do?
Also, all the other functions work? Network/audio/wifi etc? DANG FE, you've been to work
Thank again to everyone who contributed to this!
As a reminder, I would like the other guys to not spam this thread and keep this as much as to developmental and testing as possible.
Click to expand...
Click to collapse
Audio and wifi work, all this stuff is courtesy aries-common and pawitp. (My aries-common port didn't have working audio, but had wifi I think)
RIL = Radio Interface Layer and is responsible for communicating with the baseband. So basically you'll have no GSM or telephony.
trailblazerz11 said:
Thats good news didnt boot for me either when i built it a couple days ago..
Question about the kernel ramdisk, did you simply use ICS ramdisk but with pawitps areis-common init.aries.rc and init.aries.usb.rc? or were other changes needed?
Thanks Fault xD
Click to expand...
Click to collapse
It's the JB ramdisk afaik since it's CM10; so JB init.rc etc plus copied pawitp's init.aries.rc for the vibrantmtd device tree.
@xriderx66 the file is 141MB
Sent from my SGH-T959 using xda app-developers app
Reserved.
Sent from my SGH-T959 using Tapatalk 2
Is RIL disabled for now? so we wont get kernel panic? or is there a way to load it?
Thanks
trailblazerz11 said:
Is RIL disabled for now? so we wont get kernel panic? or is there a way to load it?
Click to expand...
Click to collapse
Disabled for now in the ramdisk. (Which means flashing another kernel like Devil will accidently re-enable it) I do NOT recommend enabling it, you will get kernel panic galore...
nbhnohome said:
I love you , FaultException
Click to expand...
Click to collapse
FaultException said:
Disabled for now in the ramdisk. (Which means flashing another kernel like Devil will accidently re-enable it) I do NOT recommend enabling it, you will get kernel panic galore...
Click to expand...
Click to collapse
I asked because I had a similar issue when I compiled a kernel with Linaro 4.7, might be same with 4.6 toolchain kernel is now compilied with (right?) .
Kernel would panic and crash to recovery upon starting to load RIL.
It is fixed by compiling samsung_modemctl with 4.3.3 toolchain and using it as a prebuilt.
Hopefully that helps? or probably a different issue completely xD
trailblazerz11 said:
I asked because I had a similar issue when I compiled a kernel with Linaro 4.7, might be same with 4.6 toolchain (right?) kernel is now compilied with.
Kernel would panic and crash to recovery upon starting to load RIL.
It is fixed by compiling samsung_modemctl with 4.3.3 toolchain and using it as a prebuilt.
Hopefully that helps? or might be a different issue.
Click to expand...
Click to collapse
Probably yeah. pawitp patched modemctl already, my repo sync may have neglected to update the kernel cause I had changes. I'll try again later.
Edit: here's his patch: http://review.cyanogenmod.com/#/c/19167/
Is this related to the ROM posted for the international galaxy s posted here: http://forum.xda-developers.com/showthread.php?t=1775169 ?
go_l_den said:
Is this related to the ROM posted for the international galaxy s posted here: http://forum.xda-developers.com/showthread.php?t=1775169 ?
Click to expand...
Click to collapse
They're both built off CM10. Don't know if they're using the same aries-common, possibly.
So, installed it over ics Rom and everything works as advertised. Thanks, FE. It's more than just a teaser.
Sent from my SGH-T959 using Tapatalk 2
Awesome! Thanks! Looks insane, can't wait for cm10!:cyclops::cyclops::cyclops::cyclops:
I just flashed the CM10 teaser and Devil 1.0.0-RC3 ICS\JB kernel and RIL Cell/Data is working perfect so far and everything is silky smooth so far. Unfortunately I can't get superuser working and it just causes boot loops. If anyone wants to try the latest Devil kernel or JB gapps you can get it from his ftp @ http://devil.haxer.org/jellybean/. Thank you for the little tease FE and with Devil kernel RIL has been functional so far and once root gets fixed I will go back to CM10.
hurtz777 said:
I just flashed the CM10 teaser and Devil 1.0.0-RC3 ICS\JB kernel and RIL Cell/Data is working perfect so far and everything is silky smooth so far. Unfortunately I can't get superuser working and it just causes boot loops. If anyone wants to try the latest Devil kernel or JB gapps you can get it from his ftp @ http://devil.haxer.org/jellybean/. Thank you for the little tease FE and with Devil kernel RIL has been functional so far and once root gets fixed I will go back to CM10.
Click to expand...
Click to collapse
The su binary is not in yet. But once again, shouldn't be used as a daily driver.
Server must be jammed. Won't dl for me.
Sent from my SGH-T959 using xda app-developers app
Related
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 2.3 (Gingerbread), which is designed to increase performance and reliability over stock Android for your device.
This version is a release candidate, but you will find it stable for everyday use.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions:
First time flashing CyanogenMod 7 to the Samsung Vibrant, or coming from another ROM?
Root the device and install ClockworkMod Recovery. Instructions are available here.
Perform a NANDroid backup of your current ROM.
Format the system, data & cache partitions of your device.
Perform a factory reset.
Flash CyanogenMod.
Optional: Install the Google Apps addon package
Upgrading from earlier version of CyanogenMod 7?
Perform a NANDroid backup of your current ROM.
Flash CyanogenMod (your Google Apps will be backed up & restored automatically).
Issues?
Experience issues? Please provide the following info:
If the device was hard reboot, please provide the file "/proc/last_kmsg".
If the device was soft reboot or is "bootlooping", please run a logcat and provide the full output.
Please use Pastebin when possible.
Download Links:
Official posthttp://forum.cyanogenmod.com/topic/...or-the-samsung-vibrant-v710-rc1-26-june-2011/CyanogenMod:
Latest Version: update-cm-7.1.0-RC1-Vibrant-signed.zip
Download: Link
Mirror: Link
MD5sum: 277dad59c7b90a4fb42a7781cfa8fc6bGoogle Apps addon:
Version: gapps-gb-20110613
Mirror: Link
Mirror: Link
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
Going to ODIN and start fresh to give this bad boy the breathing room he needs!
Praise the lawd!!!! Hallelujah, praise him (the devs that is)!
second post to
-bobofosho123
I was tryin' to sound southern baptist
not to sound ungrateful, because I am. you guys are awesome. Does stable for everyday use mean gps is working?
Sent from my SGH-T959 using XDA App
Is anyone else not seeing download links?
And I can flash with GB bootloaders correct?
Sent from my T959 using XDA App
According to the other thread, the mute call problem is there still, how can this be a rc? I been using the nightly's (36) and still have the problem even with Odin'ing back to stock and back to 36.
Downloading now! Will be upgradinng directly from #36.
Sent from my SGH-T959 using XDA Premium App
Release Candidate RC - This is a proposed release candidate (current one is Gingerbread based) for the next stable release, it should be stable enough to use as a daily rom (indeed I have had no problems running it), there may be a few major bugs and more minor bugs than you would find in the stable release.
Click to expand...
Click to collapse
just because its rc doesnt make it completely stable.
so is GPS working on it now?
i imagine not
bodybombs said:
i imagine not
Click to expand...
Click to collapse
No offense but where did you come from? lol
So what's the big difference between this one and atmin rom
update-cm-7.1.0-RC1-Vibrant-signed.zip (2011-06-27 03:18:41)
morrison: remove -KANG on release builds (android_vendor_cyanogen)Bumped versions on Galaxy S phones. (android_vendor_cyanogen)fixed typo in Rogers MMS setting (android_vendor_cyanogen)Revert "libaudio: Add missing GB function" (android_hardware_msm7k)Remove weighing filter from loudness equalization (android_frameworks_base)telephony: Fix previous commit (android_frameworks_base)telephony: LGEStar: Try to ensure reconnect after network loss (android_frameworks_base)Use smooth fade in/out for effect enable/disable (android_frameworks_base)
cm_vibrantmtd_full-36.zip (20
Click to expand...
Click to collapse
Above is the changelog from Nightly 36 to RC1.
Doesn't look like any work was done on the GPS yet.
Oh well, still a great build. Thanks for the hard, selfless work to everyone involved.
Downloading now. I will upgrade straight from 36. Is this a full wipe update or will it install like a nightly?
Also, any chance of BLN being in this time?
Sent from my SGH-T959 using XDA App
r3skyline said:
so is GPS working on it now?
Click to expand...
Click to collapse
No it does not.
Trev420 said:
Downloading now. I will upgrade straight from 36. Is this a full wipe update or will it install like a nightly?
Also, any chance of BLN being in this time?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
It'll install like any nightly but if you dont want any problems, i'd suggest Full Wipe.
Sweet! GPS!
[****]
Sent from my GT-I9000 using XDA Premium App
duboi97 said:
No offense but where did you come from? lol
Click to expand...
Click to collapse
what does it matter? and was i wrong? ive been using cyanogenmod roms on 6 different phones over the course of 2 years. ive had a vibrant for a few months and as far as i have read, gps only works on jvp roms at the moment, so unless the people working on the vibrant for cyanogen failed to put something here about gps then i doubt it works
To sum it up:
BUGS:
-Broken GPS
-Call mute/unmute needed on incoming calls for people to hear you
-Poor battery life (30%-40% idle consumption every 3-4 hours without being touched)
Otherwise it's amazing. Personally I'm using it as daily.
}{Alienz}{ said:
To sum it up:
BUGS:
-Broken GPS
-Call mute/unmute needed on incoming calls for people to hear you
-Poor battery life (30%-40% idle consumption every 3-4 hours without being touched)
Otherwise it's amazing. Personally I'm using it as daily.
Click to expand...
Click to collapse
i will agree with broken gps and poor battery life compared to froyo roms. However since nightly 36 mute/unmute bug has been fixed for me, i would suggest a full wipe and reinstall to those still experiencing this problem.
Only persistant (and slightly annoying issue i have) is having to reflash gapps after each update, not a big deal however, only takes an extra 5 minutes.
Other than the aforementioned issues absolutely wonderful rom, i cannot wait to get some smart ass kernels for CM7. Been running cm7 as a daily driver since nightly #8.
Due to an issue with emergency dialing (911), the stable build is no longer supported. It is suggested you update to the latest nightly available until a new stable release is ready to receive this fix. It is very important you do not use these builds, as emergency dialing is not properly functional and could put you at risk.
-SGS Team/Team Hacksung/Teamdouche
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 2.3 (Gingerbread), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions:
First time flashing CyanogenMod 7 to the Samsung Vibrant, or coming from another ROM?
Root the device and install ClockworkMod Recovery. Instructions are available here.
Perform a NANDroid backup of your current ROM.
Format the system, data & cache partitions of your device.
Perform a factory reset.
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Upgrading from earlier version of CyanogenMod 7?
Perform a NANDroid backup of your current ROM.
Flash CyanogenMod (your Google Apps will be backed up & restored automatically).
Issues?
Please be aware that there are still issues with 911 calling for the Vibrant and possibly other Galaxy S phones in T-Mobile. The issue is specific to T-Mobile and the Samsung Galaxy S Radio Interface Layer.
Experience issues? Please provide the following info:
If the device was hard reboot, please provide the file "/proc/last_kmsg".
If the device was soft reboot or is "bootlooping", please run a logcat and provide the full output.
Please use Pastebin when possible.
Download Links:
Official post
CyanogenMod:
Latest version: update-cm-7.1.0.1-Vibrant
Download: link
Mirror: link
MD5sum: 61102edc51f82e53271281b4a2853931
Google Apps addon:
Version: gapps-gb-20110828
Mirror: link
Mirror: link
Version: Google Talk with video addon
Mirror: link
Mirror: link
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
1st great!
Sent from my SGH-T959 using XDA Premium App
2nd sweet.
To infinity and beyond
sweet.
would appreciate if someone did a mini review on this commenting on stability, battery life, performance, etc.
Both DL links arnt working...
Sent from my SGH-T959 using XDA App
Broken link :---(
Sent from my SGH-T959 using XDA App
Any chance of a known bugs list please? not sure if I want to wipe and potentially Odin my gf's phone if there's a game stopper in there.
Sent from my LG-P999 using XDA App
Finally! Im on it!
I am running Froyo 2.2.1 with GB bootloaders.
Do I need to flash back the Froyo bootloaders before flashing CM7.1?
Or can I just flash it over Froyo without touching the GB bootloaders?
Thanks!
ali4ek said:
I am running Froyo 2.2.1 with GB bootloaders.
Do I need to flash back the Froyo bootloaders before flashing CM7.1?
Or can I just flash it over Froyo without touching the GB bootloaders?
Thanks!
Click to expand...
Click to collapse
No need to flash back to Froyo bootloaders. CM7 has support for the official bootloaders and the GB ones!
Link still down...
kaizasoshi said:
Link still down...
Click to expand...
Click to collapse
These worked for me LINK... Mirror works
just click the github and its in there or use rom manager, nvm
kaizasoshi said:
Link still down...
Click to expand...
Click to collapse
Yeah it's not working, lol.
fishman0919 said:
These worked for me LINK... Mirror works
Click to expand...
Click to collapse
Thanks Bro, it worked!
Works gd no problems yet
Sent from my SGH-T959 using XDA App
what is new in 7.1.01 from 7.1?
Also, is all update of CM7 need to wiped all app?
It looks like they just added the two compass files and changed build number.
Doesn't say in OP but I assume I should ODIN stock before I flash this if I'm on Gingerbread 2.3.5 rom?
so far, so good. very smooth ROM. Thank You!!!
Since I had no permission to post a new thread, so Ive just posted a reply at the following link
from http://forum.xda-developers.com/showpost.php?p=23783120&postcount=1338
wkpark said:
This is forward ported tegra kernel 3.0.8 based on the Nvidia's ODM/NVRM tegra kernel 2.6.32.9
http://github.com/wkpark/tegra-linux-3.0.y
about ~700 commits are cherry-picked from the tegra kernel 2.6.32
almost all commits/commit logs are preserved. some commits are not needed anymore and some commits hard to merge.
anyway this is the result of my effort.
0. prepare android-common repo. it contain's minimal changes for android. the latest mach-tegra tree is removed.
1. about 4~6 hours needed to cherry-pick quick and dirty manually. I can figure out where are the hard parts.
2. fix to make it compile
* add slab.h / remove smp_lock.h / fix .unlocked_ioctl / fix DECLARE_MUTEX etc.
3. apply SU660 patch sets. fix for kernel 3.0.x
4. first try to boot => fail~ :>
5. figure out where are the trouble making points
* timer / irq / gpio / platsmp codes are changed in the kernel 3.0 => dig the log and fix it up
6. at last I can make boot su660 up! (about ~15 days needed to fix to boot up. total 300~400 times retry to boot)
----
the uploaded git repo is rebased interactively (remove some useless history, merge some hunks etc)
and I separate it into three branches
1. tegra-orig-3.0.8 = original android-common + tegra 2.6.32 patch series
- can be used the base of all other nvrm/odm based tegra kernel.
2. su660-lg-usb = tegra-orig-3.0.8 + su660 patches + lg-usb for official firmwares
3. su660-ics = tegra-orig-3.0.8 + su660 patch + ICS touchscreen patch, camera patch by rmcc
currently it works nicely with the SU660
Click to expand...
Click to collapse
and I've made a forward ported P990/P999 kernel based on the lge-kernel-star managed by arcee
(Please see http://forum.xda-developers.com/showpost.php?p=23831782&postcount=1351)
and finally
this is a bootable image for P990(under testing) and P999(not tested at all)
(See also http://forum.xda-developers.com/showpost.php?p=23834645&postcount=1353)
(all for CM9/ICS)
http://code.google.com/p/openstar2x/downloads
this is just first step toward the kernel 3.0
happy hacking~!
P.S.1: I also have forward ported working (but less stable) kernel 2.6.35 (about ~7 days needed to boot up)
this encourage me to forward port kernel 3.0. and this is the result
P.S.2: I'm not related to Nvidia nor LG
ChangeLog
03/20
1. fixed haptic feedback
03/22
1. fixed three annoying kernel WARNING/BUG messages
- irq wakeup warning with gpio-keys
- revert recent cpufreq_stat commit (already reverted in the lge-kernel-star)
- simplified platsmp.c (some parts of platsmp.c already included into the core code)
2. revert some part to original ramdisk.
- emmc/sdcard swap fix (for testing purpose)
- USB vendor ID fix included (for USB tethering)
3. included YAFFS (by vadonka with minor fix)
03/25
1. various minor bugs are fixed by pastime1971 (thanks~)
03/26
1. cleanup reboot/ram_console codes
03/27 (http://forum.xda-developers.com/showpost.php?p=24097273&postcount=243)
1. p99x: fix oops while shutdown (http://forum.xda-developers.com/showpost.php?p=24102050&postcount=249)
2. cleanup cnt32_to_63_clear()
3. [HACK] copy the warmboot information to the original reserved_buffer
area before shutdown.
03/28
1. star: fixup some minor bugs (various compiler warnings are fixed)
03/29 (http://forum.xda-developers.com/showpost.php?p=24181934&postcount=258)
1. star: add CONFIG_STAR_BATTERY_UNIT_UV to support voltage unit in uV
2. su660: adjust star_capacity_from_voltage_via_calculate()
- i think it is not su660 specifc. so Ive just applied it onto the P99x
- use star_capacity_from_voltage_via_calculate() to adjust battery capacity after singular 3G/BB/rild behavior to fix "999%" battery bug.
(there are so many posts exist on this issue e.g. http://forum.xda-developers.com/show...&postcount=211)
Source Code
https://github.com/wkpark/tegra-linux-3.0.y/tree/p99x-ics
Known Issues
* frequently boot fails with the external SD card.
- workaround : remove your external SD card.
Download
for SelfKANG3(by arcee) or it's variants. Owain's CM9 KANG custom rom.
P990
http://code.google.com/p/openstar2x/downloads/detail?name=boot-cm9-for-p990-3.0.8-vib-120320.zip for P990
http://code.google.com/p/openstar2x/downloads/detail?name=boot-cm9-for-p990-3.0.8-120322.zip for P990
P999
http://code.google.com/p/openstar2x/downloads/detail?name=boot-cm9-for-p999-3.0.8-120321.zip for P999 (not tested at all)
http://code.google.com/p/openstar2x/downloads/detail?name=boot-cm9-for-p999-3.0.8-120322.zip for P999 (not tested at all. feel free to feedback)
introduced to the G2X forum by missaellpzchvz - http://forum.xda-developers.com/showpost.php?p=23904261&postcount=1
SU660
http://code.google.com/p/openstar2x/downloads/detail?name=boot-cm9-for-su660-3.0.8-vib-120320.zip for SU660
http://code.google.com/p/openstar2x/downloads/detail?name=boot-cm9-for-su660-3.0.8-120322.zip for SU660
FAQ
Q: Does this mean we will have hardware acceleration anytime soon with ICS? (by der.einstein)
A: No. this is a ODM/NVRM based tegra kernel. all the handicap are same as the kernel 2.6.32
Nice work man!
Sent from my LG-P990 using xda premium
I just can follow owain´s attitude! Your progress on the kernel is really awesome
If you need a tester for your kernels, my smartphone is all time ready.
This sounds great!
Does this mean we will have hardware acceleration anytime soon with ICS?
Sent from my Optimus 2X using XDA
nice , i'll be trying this one out at friday oder saturday , I need the phone to be ready for day to day usage during the week
crazy_dj said:
nice , i'll be trying this one out friday oder saturday , I need the phone to be ready for day to day usage during the week
Click to expand...
Click to collapse
Most is already working. Just wifi is the big problem with this kernel but I think this will be soon fixed cause we have good developers on our side.
Very nice work! man!
works well for a first test, just had one total lockup so far, but who knows if it was even related to the kernel.
i do notice that switching between tasks seems a bit less responsive, even though 2d performance indeed seems a bit smoother.
very good for a first release! hope other devs will join in here soon
Sent from my LG-P990 using XDA
Thanks a lot for this kernel! The phone feels a lot snapier! My Wifi is working without problems but I have one question, is it possible to somehow mount the SD card as the main storage? So basicly like the standard CM Mount.
thx
wkpark said:
Since I had no permission to post a new thread, so Ive just posted a reply at the following link
from http://forum.xda-developers.com/showpost.php?p=23783120&postcount=1338
and I've made a forward ported P990/P999 based on the lge-kernel-star managed by arcee
(Please see http://forum.xda-developers.com/showpost.php?p=23831782&postcount=1351)
and finally
this is a bootable image for P990(under testing) and P999(not tested at all)
(See also http://forum.xda-developers.com/showpost.php?p=23834645&postcount=1353)
(all for CM9/ICS)
http://code.google.com/p/openstar2x/downloads
this is just first step toward the kernel 3.0
happy hacking~!
P.S.: I also have forward ported working (but less stable) kernel 2.6.35 (about ~7 days needed to boot up)
this encourage me to forward port kernel 3.0. and this is the result
FAQ
Q: Does this mean we will have hardware acceleration anytime soon with ICS?
A: No. this is a ODM/NVRM based tegra kernel. all the handicap are same as the kernel 2.6.32
Click to expand...
Click to collapse
I commend the excellent work and thank you so much for this new kernel, but I would love to know why choose a 3.0.x kernel with respect to a kernel 2.xx, I can understand a bit 'but I want better security
Robse86 said:
Thanks a lot for this kernel! The phone feels a lot snapier! My Wifi is working without problems but I have one question, is it possible to somehow mount the SD card as the main storage? So basicly like the standard CM Mount.
thx
Click to expand...
Click to collapse
Yeah, that would be awesome.
Thanks for your hard work.
I don't know exactly where, but there is a guide how to modify fstab to swap mounting just search
Odesláno z mého LG-P990 pomocí Tapatalk
My untrained eye makes me think this thing doesn't touch your vold.fstab.
If that wasn't your question and you actually want to change it, the file is located in \system\etc\vold.fstab and you can edit it with a text editor. Just swap the two lines around. (Aka, point at different targets. Any sensible person could work it out )
Edit: Also, should mention I'm flabbergasted this exists. Excellent work Mr. OP
When i flash this kernel my phone do not recognize my baseband and the battery is showing 999%. What am i doing wrong?
slebit said:
When i flash this kernel my phone do not recognize my baseband and the battery is showing 999%. What am i doing wrong?
Click to expand...
Click to collapse
It would be great if you say to us, which baseband, RIL and ROM you use
Impact7 said:
It would be great if you say to us, which baseband, RIL and ROM you use
Click to expand...
Click to collapse
I use owains kang 26 with 0824 baseband and ril 0824 (V21f, europe).
Sent from my LG-P990 using Tapatalk
slebit said:
I use owains kang 26 with 0824 baseband and ril 0824 (V21f, europe).
Sent from my LG-P990 using Tapatalk
Click to expand...
Click to collapse
First, you can install the kernel again. But wipe dalvik cache.
Hope this fix it.
Dekudan said:
My untrained eye makes me think this thing doesn't touch your vold.fstab.
If that wasn't your question and you actually want to change it, the file is located in \system\etc\vold.fstab and you can edit it with a text editor. Just swap the two lines around. (Aka, point at different targets. Any sensible person could work it out )
Edit: Also, should mention I'm flabbergasted this exists. Excellent work Mr. OP
Click to expand...
Click to collapse
I checked this already, nothing changed there! Must be sth. else. Damned I want to use this kernel but all my stuff is on the externel SD card
Impact7 said:
First, you can install the kernel again. But wipe dalvik cache.
Hope this fix it.
Click to expand...
Click to collapse
Already done that, unfortunately it didn't solve it...
Sent from my LG-P990 using Tapatalk
Yes! Very good job indeed!
Very fluid, no wireless problem here, sdcard mounted as usual, I will keep it for a while..
Many thanks! Impressive job.
m_plus kernel for Nexus 4 (mako)!
Hi All,
In an attempt to reduce the confusion related to the two versions of 4.3, I have decided to split my m_plus thread into 3 versions, a version for 4.2 (the previous thread: http://forum.xda-developers.com/showthread.php?t=2256887), a version for 4.3 JS AOSP builds (this one) and a version for 4.3 JW builds (not yet up, but will be in the future).
Disclaimer: As usual, I am not responsible for anything that may or may not happen to your device as a result of using this kernel or any other flashable zips posted by me in this thread.
Kernel Features:
Based on the latest Google Source for 4.3
Built with the Linaro 4.7.3 toolchain (2013.07)
insecure ramdisk (ro.recure=0, ro.debuggable=1)
init.d support (by flashing the full ramdisk, requires busybox installed to /system/xbin)
Undervolting support (down to 600mV)
Gamma Control support (motley, faux and franco interfaces available)
Faux Sound Control support including poweramp
dynamic fsync
simple GPU governor
Builds:
Sources: https://github.com/thracemerin/kernel-Nexus4/tree/m_plus_43_exp_JS
Warning: These builds are for 4.3 builds beginning with the letters JS only, if you flash it on a JW based build you will have all sorts of strange graphical issues.
Personal Request: If you plan to make unofficial builds with features not included in the builds posted by me, please don't link them in the thread, all this does is result in confusion especially if someone has a problem with something you have added, it is much easier for me to provide support if I know that everyone in the thread is running the same builds I am. If you want to make a kernel with these features, feel free to start another thread so that they can be discussed and supported as appropriate.
http://goo.im/devs/thracemerin/mako/m_plus_43/JS_builds/alphas
Latest:
Alpha 5:
Flashable (anykernel): m_plus_43_alpha_5JS.zip
Note: if you need the full ramdisk for init.d support/insecure ramdisk, flash the ramdisk package alpha 4 first.
What's Added:
USB force fast charge
Enable Krait Retention
Various patches and enhancements from CAF
Previous:
Alpha 4:
Note: The anykernel version doesn't include init.d support and insecure ramdisk unless your ROM already has it, if you were on alpha 3 you will retain it.
Note 2: If you flash the ramdisk version on CM, the built-in superuser will stop working, CM includes init.d support anyway.
Flashable (ramdisk included): m_plus_43_alpha_4JS_ramdisk.zip
Flashable (anykernel): m_plus_43_alpha_4JS.zip
What's Included:
all the stuff listed in kernel features
freezer patches by Colin Cross
Thanks:
Google
LG
Qualcomm/CodeAurora
CyanogenMod
_motley
faux123
show-p1984
franciscofranco
stratosk
anyone else I failed to mention (if you feel as though you deserved to be thanked by name, please PM me)
Reserved
PowerHAL Fix:
There is an issue in the stock AOSP powerHAL where the mpdecision touch boost requests are being sent to the wrong socket, as a result there will be unexpectedly poor UI performance. Show-p1984 fixed this problem in his Stockified AOSP build and I pulled the powerHAL and made it flashable for everyone. Just flash it in recovery and reboot, if you want to go back to the stock one just dirty flash your ROM. This shouldn't cause any problems on any ROM even if it has the fix already cooked in, but if it does you can just dirty flash your ROM to remove it. Thanks to show-p1984 for the fix.
43_powerhal_fix.zip MD5: c7cebad04b5f71d067df1a45c6e538f7
One More for Science!
Just flashed. I was losing wifi connection with semaphore when phone went into deep sleep. Ill report back. :good:
do you have to be rooted in order for init.d to work?
keda said:
do you have to be rooted in order for init.d to work?
Click to expand...
Click to collapse
Yep, need to have busybox installed too.
First of all, thanks for your work.
I want to make sure I understand the procedure correctly.
If I use CM10.2, I flash "m_plus_43_alpha_4JS.zip" to maintain the built in superuser.
init.d will still work, cause cm already supports it.
Right now I am on Alpha3 with SuperSU 1.51. So to update to alpha4 I can simply flash over.
If I want to go back to the built in superuser I have to reflash CM, then flash alpha4 via zip.
Is this correct?
Wont stay connected to Google services when phone goes into deep sleep, bars and signal are grey when i turn screen on. I thought Google fixed all the wifi issues with N4 in 4.3 kernel?
AcmE85 said:
First of all, thanks for your work.
I want to make sure I understand the procedure correctly.
If I use CM10.2, I flash "m_plus_43_alpha_4JS.zip" to maintain the built in superuser.
init.d will still work, cause cm already supports it.
Right now I am on Alpha3 with SuperSU 1.51. So to update to alpha4 I can simply flash over.
If I want to go back to the built in superuser I have to reflash CM, then flash alpha4 via zip.
Is this correct?
Click to expand...
Click to collapse
Dirty flash CM, then flash A4 should do it, that's what I did and it worked.
ScumDroid said:
Wont stay connected to Google services when phone goes into deep sleep, bars and signal are grey when i turn screen on. I thought Google fixed all the wifi issues with N4 in 4.3 kernel?
Click to expand...
Click to collapse
Strange, it's working fine for me now.
Thanks, just wanted to reply. Works as you said.
After the first boot I had some strange behaviour,
min cpu clock did not go below 1,026 ghz and GPU Clock did not go above 200 mhz.
A restart fixed it, incase somebody notices similar behaviour.
AcmE85 said:
Thanks, just wanted to reply. Works as you said.
After the first boot I had some strange behaviour,
min cpu clock did not go below 1,026 ghz and GPU Clock did not go above 200 mhz.
A restart fixed it, incase somebody notices similar behaviour.
Click to expand...
Click to collapse
Weird, I didn't notice that.
thracemerin said:
Strange, it's working fine for me now.
Click to expand...
Click to collapse
Mabye its an app i have installed. Kernel is flying btw, nice work.
Is it just me or the option to give location eve with wifi off is ****ing with repeaters... I have two access points in my house and when the option was on the wifi keep disconnecting... Maybe cause In some parts I can have signal from both access points... So weird
Sent from my Nexus 4 using xda app-developers app
ScumDroid said:
Wont stay connected to Google services when phone goes into deep sleep, bars and signal are grey when i turn screen on. I thought Google fixed all the wifi issues with N4 in 4.3 kernel?
Click to expand...
Click to collapse
+1 for this. i am also having same problem.
yash295 said:
+1 for this. i am also having same problem.
Click to expand...
Click to collapse
What ROM are you using?
thracemerin said:
What ROM are you using?
Click to expand...
Click to collapse
Cm 10.2 unofficial nightly.
Sent from my Nexus 4 using Tapatalk 4 Beta
yash295 said:
Cm 10.2 unofficial nightly.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
hmm...working perfectly for me, CM10.2 unofficial and this kernel.
thracemerin said:
hmm...working perfectly for me, CM10.2 unofficial and this kernel.
Click to expand...
Click to collapse
Oh yeah cm might be the problem. Sorry for the inconvenience
Sent from my Nexus 4 using Tapatalk 4 Beta
OmniROM - Lollipop Android 5.1.1 - for Samsung Vibrantmtd
What is Omnirom?
A new Android custom rom has been announced at the BABBQ (Big Android BBQ) by @XpLoDWilD, @Chainfire, @Dees_Troy & Team. For more information go to omnirom's website
Code:
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
* If you dont like this rom, Stay away from this thread!
This Rom is build with Omnirom source without changes except:
- The bigmem switch included in setting, advanced, big thanks to @xc-racer99
- The kernel, big thanks to @me
This Rom is compiled with SaberMod http://forum.xda-developers.com/android/software-hacking/toolchains-sabermod-arm-arm64-t3064459
And the kernel with Cortex-A8 optimized Linaro 4.9.4 toolchain http://forum.xda-developers.com/showthread.php?t=2098133
WHAT IS NOT WORKING?
same bug as Unofficial build from Humberos.
How To Flash:
Download the Rom for your device and copy to your phone
Reboot into Recovery
Wipe Data Factory Reset
flash Rom
flash 5.1.x GApps
Special Thanks :
the omnirom team.
@humberos, without him this rom wouldn't be possible.
@Christopher83 for is toolchain.
@sparksco for is toolchain.
@xc-racer99 for his contribution.
Download Link :
[URL="http://www.mediafire.com/download/nh4vaj6do2454qb/omni-5.1.1-20151119-vibrantmtd-HOMEMADE.zip"]http://www.mediafire.com/download/nh4vaj6do2454qb/omni-5.1.1-20151119-vibrantmtd-HOMEMADE.zip[/URL]
Last update : https://www.androidfilehost.com/?fid=24499762636001940
I don't own a vibrant, so i can't test the rom myself, if you have any issue post it here but i might not be able to fix it.
Contributors
@Coldwindofnowhere
Source Code: https://github.com/omnirom
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: AOSP
Version Information
Status: Testing
Created 2015-10-19
Last Updated 2015-12-02
>If you like my work, hitting the thanks button won't hurt you<
Reserved
What is different about this build from other Omnirom 5.1 vibrant builds?
rosco77 said:
What is different about this build from other Omnirom 5.1 vibrant builds?
Click to expand...
Click to collapse
Thanks for the awesome work and building omni rom for vibrant. The rom itself is fast and smooth while having no bugs. The one thing which makes this rom different from the omni rom is the new kernel coldwindofnowhere added which contain many new features such as governors like smartass v2, battery life extender, fast charge, big memory support and toggle in advanced menu. Also this was possibly compiled with the newest source code. This rom is very well worth a try because its a master piece and your kernel is like icing on the cake. Thanks for your support an keep up the good work:good::good:
I'm trying to come from Slimkat but I get a status 7 installation aborted error message when trying to flash. Any advice?
rosco77 said:
I'm trying to come from Slimkat but I get a status 7 installation aborted error message when trying to flash. Any advice?
Click to expand...
Click to collapse
Try both TWRP or CWM because i had no problem. However, i was already in android lollipop while flashing this rom so just try flashing a lollipop rom which works on your device such as code rom to get to the latest TWRP then try
rosco77 said:
What is different about this build from other Omnirom 5.1 vibrant builds?
Click to expand...
Click to collapse
Faster
---------- Post added at 06:38 AM ---------- Previous post was at 06:34 AM ----------
rosco77 said:
I'm trying to come from Slimkat but I get a status 7 installation aborted error message when trying to flash. Any advice?
Click to expand...
Click to collapse
If you get status 7 error, dont worry flash again if its still there navigate to reboot to recovery and flash rom.zip again. Done
Thanks for the advice guys. Rebooting recovery and flashing again still didn't work. I used cm11 kernel to go back to a slightly older version of CWM and it worked but after i booted up I was getting reboots constantly. It took me several tries just to get through the setup wizard. The reboot problem started getting better over time but it was still going on so I clocked the kernel back down to 1000Mhz and haven't had any more reboots yet but the phone has a little lag now. It was super smooth at 1400Mhz. It's still an awesome rom. This is my first time trying a Lollipop rom and so far it is my favorite rom of all time for this device. Thanks for the build OP.
The only real issue I'm having right now is I can't download anything. The wifi and network data work fine but when I try to download an app from the play store it starts but then I get an error message (can't download app error code:491). I thought I would try another gapps from the browser but when I try to download the zip it starts to download but stays at zero percent.
Any advice for me on the downloads problem? Or how I can overclock without getting the reboots?
rosco77 said:
Thanks for the advice guys. Rebooting recovery and flashing again still didn't work. I used cm11 kernel to go back to a slightly older version of CWM and it worked but after i booted up I was getting reboots constantly. It took me several tries just to get through the setup wizard. The reboot problem started getting better over time but it was still going on so I clocked the kernel back down to 1000Mhz and haven't had any more reboots yet but the phone has a little lag now. It was super smooth at 1400Mhz. It's still an awesome rom. This is my first time trying a Lollipop rom and so far it is my favorite rom of all time for this device. Thanks for the build OP.
The only real issue I'm having right now is I can't download anything. The wifi and network data work fine but when I try to download an app from the play store it starts but then I get an error message (can't download app error code:491). I thought I would try another gapps from the browser but when I try to download the zip it starts to download but stays at zero percent.
Any advice for me on the downloads problem? Or how I can overclock without getting the reboots?
Click to expand...
Click to collapse
You can try this gapps https://mega.nz/#F!G0QXXRAC!pZ063qCaa5lxdD73SarU6Q
I don't think Gapps is the problem for me. I wiped and reflashed the rom this time with no gapps and the downloads from the browser still don't work. I tried to download things from several different sources and everything stays at zero percent.
Another thing I am trying to get working is swype on the keyboard. Is that something that does not work on vibrant lollipop roms or is it working for everyone else.
rosco77 said:
Another thing I am trying to get working is swype on the keyboard. Is that something that does not work on vibrant lollipop roms or is it working for everyone else.
Click to expand...
Click to collapse
No it's a bug present on all LP roms i know, you can still you an alternative keyboard to get around this issue
Ok, thanks. I got the google keyboard off play store. It's the same keyboard and it functions just fine. I fixed the download problem by flashing a different omni lollipop rom, testing to make sure download was working then doing a dirty flash back to this rom. Works great and I think I found a new daily driver. Thanks Coldwindofnowhere.
Edit: One other thing I forgot to mention, I can't get TWRP to flash anything. It always fails. For some reason I can only get it to flash a kernel so I have to flash my CM11 kernel and reboot recovery to get into CWM then reflash the rom and gapps. This problem was present when I flashed the other version of Omni Lollipop also. Not a huge problem for me. I will just keep my CM11 kernel in the downloads folder and use that any time I need to flash something.
rosco77 said:
Ok, thanks. I got the google keyboard off play store. It's the same keyboard and it functions just fine. I fixed the download problem by flashing a different omni lollipop rom, testing to make sure download was working then doing a dirty flash back to this rom. Works great and I think I found a new daily driver. Thanks Coldwindofnowhere.
Edit: One other thing I forgot to mention, I can't get TWRP to flash anything. It always fails. For some reason I can only get it to flash a kernel so I have to flash my CM11 kernel and reboot recovery to get into CWM then reflash the rom and gapps. This problem was present when I flashed the other version of Omni Lollipop also. Not a huge problem for me. I will just keep my CM11 kernel in the downloads folder and use that any time I need to flash something.
Click to expand...
Click to collapse
Um i don't have this issue on my Galaxy , maybe it's Vibrant related ... honestly i don't know. Can you give a screenshot or just tell me what error it shows when you flash something ?
New build coming soon, it will be up in a few hours. It includes the latest omni source, my latest kernel (@rosco77 i'm pretty sure your TWRP issue will be gone) and a new toolchain. I will update the link in the OP.
Links in the OP updated !
Coldwindofnowhere said:
New build coming soon, it will be up in a few hours. It includes the latest omni source, my latest kernel (@rosco77 i'm pretty sure your TWRP issue will be gone) and a new toolchain. I will update the link in the OP.
Click to expand...
Click to collapse
Yeah
Building right now, sorry for the delay. It should be up in like 3-4 hours if i don't get any error
Link updated in the OP
Coldwindofnowhere said:
Building right now, sorry for the delay. It should be up in like 3-4 hours if i don't get any error
Click to expand...
Click to collapse
Thanks man for supporting vibrant, and take your time building the rom
@Coldwindofnowhere Can you also build your kernel 5.1.1 for vibrant. I and people here are very appreciate of that
Thanhtho96 said:
@Coldwindofnowhere Can you also build your kernel 5.1.1 for vibrant. I and people here are very appreciate of that
Click to expand...
Click to collapse
Well you can just extract the boot.img from the rom and flash it ...