Related
I Am Not AFFILIATED with the CyanogenMOD Team.. Any Comments by me are not the views of CyanogenMOD!
Please Read ENTIRE Post
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.
****THIS IS A TESTING PHASE ROM THERE WILL BE ISSUES.****
This is an Beta 5 release & Based on Slayher CM7 Build, but you should find it stable for everyday use.
**Known Issues**
~ Join Contacts don't work correctly
~ APN Lost on Airplane Mode
~ Render FX Not working
~ Youtube Fast Forward is Broken
~ volume+ might have issue.... see this Post
~ Changing CPU Governor can sometimes cause CPU1 from not going Offline
~ NFC Does not work
INSTRUCTIONS:
- First time flashing CM 7 to your Galaxy S2 (or coming from another ROM)?
1. Unlock/root your device and install Clockwork Recovery via ROM Manager
2. Do a Nandroid backup!
3. Flash DARKSIDE.SUPER.WIPE_EXT4.zip Wipe Utility
4. Install Rom
- Second time flashing
1. Flash DARKSIDE.SUPER.WIPE_EXT4.zip Wipe Utility
2. Install Rom
~ If Coming from ICS
1. Flash DARKSIDE.SUPER.WIPE_EXT4.zip
2. Flash Rom
Download:
T-Mobile T989 SGS2:
Nightly 4/21/2012 -> CM7_373R7.zip
CM7_373R6.zip
AT&T SkyRocket I727 SGS2:
CM7_373R6_ATT.zip
Right, lets try this again, shall we?
The OP has kindly provided another thread for you to ask questions in and generally post pointless crap like 'thanks', 'downloading!', 'awesome' etc.
This thread should be reserved for bug reports and constructive feedback for the OP.
I get the following when I try to flash the rom:
Installing Update...
assert failed: getprop("ro.product.device") == "hercules" || getprop("ro.product.device") == "hercules" || getprop("ro.product.device") == "hercules" ||
E:Error in /sdcard/CM_373_Kang.zip
(Status 7)
Installation Aborted
It seems to happen with all CM7 roms but most other roms work fine for me.
retrotim said:
I get the following when I try to flash the rom:
Installing Update...
assert failed: getprop("ro.product.device") == "hercules" || getprop("ro.product.device") == "hercules" || getprop("ro.product.device") == "hercules" ||
E:Error in /sdcard/CM_373_Kang.zip
(Status 7)
Installation Aborted
It seems to happen with all CM7 roms but most other roms work fine for me.
Click to expand...
Click to collapse
What is your recovery version?
Crazy4G1 said:
What is your recovery version?
Click to expand...
Click to collapse
CWMR Touch v5.5.0.4
retrotim said:
CWMR Touch v5.5.0.4
Click to expand...
Click to collapse
are you using the super wipe? Try flashing the regular recovery from ROM manager
Sent from my SAMSUNG-SGH-I727 using xda premium
Try updating to the newest recovery which is v.5.8.1.3, you may need to update rom manager too.
retrotim said:
I get the following when I try to flash the rom:
Installing Update...
assert failed: getprop("ro.product.device") == "hercules" || getprop("ro.product.device") == "hercules" || getprop("ro.product.device") == "hercules" ||
E:Error in /sdcard/CM_373_Kang.zip
(Status 7)
Installation Aborted
It seems to happen with all CM7 roms but most other roms work fine for me.
Click to expand...
Click to collapse
Try Install Zip from SD card -> Toggle Signature Verification in CWM. The exact error that I frequently used to get when trying to flash ROMs escapes me, but that typically always solved the problem for me.
*i'm not responsible if your android device turns into a paperweight
Hey eugene just in case you didn't see in the other thread but
Settings>CyanogenmodSettings>Application>Use Internal Storage CHECKED
mounts internal to I'm not sure where.
I believe you have /sdcard as internal and /sdcard/ext or something else for external(not sure since I don't rock an external)
Just saying D: ..Probably insignificant but I checked it since I'm used to doing so only to find out it was mounted fine to begin with.
I beleive on cm emmc is external and sd card is labeled as internal
darkamikaze said:
Hey eugene just in case you didn't see in the other thread but
Settings>CyanogenmodSettings>Application>Use Internal Storage CHECKED
mounts internal to I'm not sure where.
I believe you have /sdcard as internal and /sdcard/ext or something else for external(not sure since I don't rock an external)
Just saying D: ..Probably insignificant but I checked it since I'm used to doing so only to find out it was mounted fine to begin with.
Click to expand...
Click to collapse
Sent from my SGH-T989 using XDA App
monkeypaws said:
I beleive on cm emmc is external and sd card is labeled as internal
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
The post above yours is correct.. I fixed it so market apps work correctly.
Hey Eugene,
Found a few issues :
Keyboard settings do not allow for adjusting long press delay.
Flashlight not available in notification widget. Torch works fine.
XDA app free wont allow saving of favorites. Probably related to sdcard issue.
Car Home is borked.
Battery Charge on lockscreen says 'Sorry try again' I have always show battery stats enabled.
No option for personalized voice searching.
negativefx said:
Hey Eugene,
Found a few issues :
Keyboard settings do not allow for adjusting long press delay.
Flashlight not available in notification widget. Torch works fine.
XDA app free wont allow saving of favorites. Probably related to sdcard issue.
Car Home is borked.
Battery Charge on lockscreen says 'Sorry try again' I have always show battery stats enabled.
No option for personalized voice searching.
Click to expand...
Click to collapse
Confirmed charging lockscreen status issue over here.
KonstantinKeller said:
Confirmed charging lockscreen status issue over here.
Click to expand...
Click to collapse
lmao! Sorry try again........
yeah I made a few bugs fixing others... awe hell...
Eugene... here is my findings
Scrolling lags or struck on first scroll then back to normal. I am using bounce and glow option.
Lockscreen shows charging % though its discharging. I have enabled to show percentage all the time.
Just an information.
Home button not working in first flash.. fixing permissions fixed the issue
Rom is snappier and the other functions I have tested are working. Nice rom..thanks for your hard work.
Sent from my SGH-T989 using Tapatalk
This thread has been pretty good so far but I had to reiterate this point elsewhere, so it seemed like it was worth mentioning here too:
There seems to be some confusion about this, so lets spell it out...
The following are appropriate posts for this thread:
Bug reports (though please check before posting - there's no point reporting a bug that 10 other people have already mentioned)
Solutions/fixes for bugs/issues
Information clearly contradicting a pre-existing bug report (if there's a reason why you're not having the same problem, that may help the OP work out why the bug is occurring)
The following are not appropriate reasons to post in this thread:
Questions
Suggestions/feature requests
General feedback ("No problems here", "3 days no issues" etc)
Thanks (not that anyone should be posting just to say thank you when there is a thanks button but it seems some people are incapable of using it)
Other non-contributory posts
Posts like those should be in the companion thread for this ROM.
Issues I ran into:
Clicking on 4G Settings in Settings causes FC of Settings
Device Settings says Galaxy S (instead of Galaxy S II) Settings up top, and all of the settings are disabled, including ability to control button lights
Settings => Cyanogenmod settings => Interface => Render effect has no effect
Cyanogenmod-style swiping the notification bar to adjust brightness does not work, even with auto-brightness disabled
Other issues I've seen others mention already that I can confirm:
Airplane mode wipes out the APN list
NFC doesn't work
Settings => Cyanogenmod settings => Application => Use Internal as /sdcard is working opposite of expected
Settings => Cyanogenmod settings => Interface => Notification power widget => Widget buttons => Toggle LED flashlight is unavailable
Instead of 4g I have an "H" where my 4g normally is. Every once in a while 4g pops up for a few seconds.
Sent from my SGH-T989 using xda premium
2 bugs I noticed in Slayher's CM7 A2 that are still present in this:
After charging all night the battery will report to drain ridiculously fast until I reboot the phone -- simple workaround, reboot every morning when I unplug it
LauncherPro folders are missing icons on boot, workaround, restart launcherpro after rebooting in the morning
Otherwise, overall MUCH faster at stock speeds than Slayher's A2 with Synergy OC to 1.83. If you want a logcat from while the battery is draining fast or anything else I can provide from this phone, just let me know. Thanks!
Edit: Had to go back to Slayher A2, Battery drain on this ROM was insane (about 10% per 2 hours). Might have been me.
Edit 2: I flashed again because I want this to work so much. Going to run JuiceDefender and figure out what's draining the battery.
The issues i have:
-When i restored me SMS messages (12000) of them SMS app wont open any of the threads
-When i tried downloading GoSMS or Handcent to try them the market said "Error Cannot Purchase"
Other then that this rom is perfect, any help here?
I will post logcat right now
Edit:
I have figured out how to fix both these, For anyone using SMS Backup and Restore if you have a large amount of SMS ie over a few thousand after restore open up the sms app and try to open a thread and let it sit, it may ask to fc or wait click wait. In my case 12000 MSGs took about 15 mins.
To fix the market i had to reboot and let the market sit open for a while? Not sure why.
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.0 (Ice Cream Sandwich), which is designed to increase performance and reliability over stock Android for your device.
Please make sure you have a backup that you can restore if you run into problems.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 any of us for messing up your device, we will laugh at you.
* Collectively, and at the same time.
*/
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 9 your device, 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 9?
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:
Please see our blog at http://www.teamchopsticks.org for installation, download links and release notes.
Installation and Download: http://www.teamchopsticks.org/p/install-guide.html
Release Notes: http://www.teamchopsticks.org/p/release-notes.html
Contributing/Building: http://www.teamchopsticks.org/p/contributing.html
FAQ/Troubleshooting: http://www.teamchopsticks.org/p/faq.html
The CyanogenMod team and TeamChopsticks would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
Donations are appreciated, but not required.
Reserved
Reserved
3rd reserved
reserved
Does auto-rotation work, or do we have to flash the fix?
And a massive roar of cheers erupts.
On topic: why do we have to use cwm touch? I've had some very bad experiences with stability on touch and I'm not entirely comfortable using it as my recovery. What's special about this rom that makes cwm touch mandatory?
Sent from my SAMSUNG-SGH-T989 using XDA
zander21510 said:
And a massive roar of cheers erupts.
On topic: why do we have to use cwm touch? I've had some very bad experiences with stability on touch and I'm not entirely comfortable using it as my recovery. What's special about this rom that makes cwm touch mandatory?
Sent from my SAMSUNG-SGH-T989 using XDA
Click to expand...
Click to collapse
Yes, unless you want boot loops, you MUST use CWM Touch. Sorry.
Hey guys this is still early still a few major bugs
https://github.com/TeamChopsticks/cm_device_samsung_msm8660-common/issues?state=open
I just don't want to see 6 pages of questions . Read the OP and Flash this is no Q and A thread.
Thanks
I'm loving the how the development for this phone has gotten. From a few Gingerbread ROMs to CM9, CM7 ,MUIU v4 and ICS
Sent from my SGH-T989 using Tapatalk 2
I get this when installing download the rom three different times!
assert failed: getprop("ro.product.device") == "
hercules" ll getprop("ro.build.product") == hercules
E:Error in /sdcard/update-cm-9-20120426-SNAPSHOT-hercules-alpha1-signed.zip
(Status 7)
Installation aborted
Using CWM touch
Made a CM9 q and a thread.. someone had to!! Lets keep this piece open!
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
MissMayI said:
I get this when installing download the rom three different times!
assert failed: getprop("ro.product.device") == "
hercules" ll getprop("ro.build.product") == hercules
E:Error in /sdcard/update-cm-9-20120426-SNAPSHOT-hercules-alpha1-signed.zip
(Status 7)
Installation aborted
Using CWM touch
Click to expand...
Click to collapse
MissMay: Either you aren't using a T989 or your aren't use CWM Touch 5.5.0.4. This build won't install on a Skyrocket.
topprospect said:
MissMay: Either you aren't using a T989 or your aren't use CWM Touch 5.5.0.4. This build won't install on a Skyrocket.
Click to expand...
Click to collapse
Im using a T989 and the CWM touch thats linked to the rom
MissMayI said:
Im using a T989 and the CWM touch thats linked to the rom
Click to expand...
Click to collapse
MissMay, mikeyman77 may have linked the Skyrocket CWM touch in his OP. Install this one and see if it helps:
http://forum.xda-developers.com/showthread.php?t=1510478
I will ask him to update the OP.
topprospect said:
MissMay, mikeyman77 may have linked the Skyrocket CWM touch in his OP. Install this one and see if it helps:
http://forum.xda-developers.com/showthread.php?t=1510478
I will ask him to update the OP.
Click to expand...
Click to collapse
That fixed it!!! Thank you
Rom is so fast
Bugs as noted no more no less so far. I really hate the gg but cm9 is fun to play with.
Can I use cwm touch 5.8.1.3. It's touch but not the one posted
Sent from my SGH-T989 using Tapatalk
bbobarino said:
Can I use cwm touch 5.8.1.3. It's touch but not the one posted
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
as long as its the touch version for the t989 (Hercules) it will work. we found that non touch recoveries would cause boot loops 100% of the time.
I'm glad we finally got this released Please do report bugs that are reproducable guys. and PLEASE post logcats.
If you are willing to report bugs, understand we may call on you to do more in-depth trouble shooting and one of our team members will walk you through this.
You can PM me directly if you think you have something to help. Not to be rude, but lets not waste any ones time so contact one of the team members only if A) the bug is reproducible and not already listed, and B) if you are willing to take some time to give us logs and info.
i think the OP dl link is down
I'm curious, is it just me or is there no in-call audio? (Doesn't seem to work for me. I did turn off gps, which perhaps it has the same problem as the first cm7, but after rebooting and even shutting down with it on, still no in call audio.) Did I have a bad flash perhaps?
Minus the few graphics glitches, this seems very nice. Also, yaldak's fix for autorotation works on this as well.
I've done everything that it says to do in the install directions, I've read through the troubleshooting, nothing works. I persistently dead end with this:
AROMA INSTALLER version 2.56
(c) 2012 by amarullz xda-developers
ROM Name : Dirty RootBox
ROM Version : v2.0
ROM Author : mlaws90
Device : grouper
Start at : Sun Mar 15 12:15:40 1970
==========================
====Dirty RootBox v2.0=====
=======By:mlaws90=========
=========AROMA==========
=======Pie Controls=======
Build Date: Sat Feb 16 13:15:24 CST 2013
>>-Checking Device...
script aborted: assert failed: getprop("ro.product.device") == "grouper" || getprop("ro.build.product") == "grouper"
assert failed: getprop("ro.product.device") == "grouper" || getprop("ro.build.product") == "grouper"
Installer Error (Status 7)
End at : Sun Mar 15 12:15:40 1970
I'm downloading this from the link that I found here. I'm trying to upgrade from Root 66 (JB 4.1.1), I've wiped EVERYTHING off my phone (excluding the internal and external user storage) and I still have this issue. For s$&ts and giggles, I tried installing DRB over R66 and still get the same error. It doesn't matter what options I do or don't select, or what kernel I choose. I even bothered to trip the counter and try flashing from ODIN - which left me staring at the GS3 boot logo for an hour before I decided to abandon and restore my back up.
How do I make this work on my SGH-T999?
Is your recovery up to date?
Sent from my SGH-T999 using xda premium
seattlestexan said:
script aborted: assert failed: getprop("ro.product.device") == "grouper" || getprop("ro.build.product") == "grouper"
assert failed: getprop("ro.product.device") == "grouper" || getprop("ro.build.product") == "grouper"
Click to expand...
Click to collapse
Looks like you are trying to flash a rom that isn't for your phone. Looks like it's actually for a tablet. Lucky for you the author put an assert check in before the flash. Because you almost bricked your phone.
Aerowinder said:
Looks like you are trying to flash a rom that isn't for your phone. Looks like it's actually for a tablet. Lucky for you the author put an assert check in before the flash. Because you almost bricked your phone.
Click to expand...
Click to collapse
True.
I don't get it. I see ROM's listed as for the T999, then they either don't work, or they end up being for something else. I was looking for a good JB4.2.2 ROM, and this was listed for the T999.
I just want a good 4.2.2 ROM with plenty of options for personalisation. I'm thinking that's too much to ask for. Codename Android is the closest to what I want, but it doesn't work with the T999 apparently.
Any suggestions?
Here are your choices for 4.2.2: http://forum.xda-developers.com/forumdisplay.php?f=1690
I've been using CM 10-10.1 since it became available.
seattlestexan said:
True.
I don't get it. I see ROM's listed as for the T999, then they either don't work, or they end up being for something else. I was looking for a good JB4.2.2 ROM, and this was listed for the T999.
I just want a good 4.2.2 ROM with plenty of options for personalisation. I'm thinking that's too much to ask for. Codename Android is the closest to what I want, but it doesn't work with the T999 apparently.
Any suggestions?
Click to expand...
Click to collapse
PAC is pretty heavy in the customization field and it is a 4.2.2 ROM.
Sent from my SGH-T999 using Tapatalk 2
[UPDATED][2015][HOW-TO]Everything you need to know and do to your Captivate Glide by Stormdude124!
Hello, I see a lot of people wondering how to root the captivate glide,what ROMS are active and want to use a custom ROM but can't figure out how to do it. Well, here is a awesome guide that's easy to follow! When your done don't for get to drop a thanks if I've helped!
[ROOTING/AND OR UPDATING TO LATEST OFFICIAL UPDATE]
(of course when you make any modifications to your phone I'm not responsible but I am here to help!
I'm not discouraging you to do this,because this makes your phone awesome, but you know the drill :3 )
Firstly you need to update your firmware to 4.0.4 UCLJ3,You technically don't have to do this step,but this is the guaranteed way to successfully do it and have no issues. Here's two simple ways you can do it:
*If you are rooted /have the Rodgers version and want to update:
If you are on 2.3.5 android firstly, Update to official ICS 4.0.4 via ODIN.If you have Rodgers version you need root anyways .Click the button to show more and why:
Okay so you have the Rodgers version of the phone and you want root right?
Well your in luck! It does require having a custom ROM first...The reason is because the pre-rooted 2.3.5 ODIN flashable ROM is dead and I have yet to find one.If you want to be on official ICS Do this:Flash TWRP>backup your ROM>Install CM11 from recovery(it is pre rooted thats a plus!)>backup your /efs(this contains your unique IMEI number) with efs pro>then flash the 4.04 offical firmware via ODIN below this>restore your /efs. (if it was lost of course)If you want to stay on your custom ROM theres no probem with that,but if you have problems with signals or anything just flash this in recovery.
If you have any questions regarding this method check this thread out first.Anyways please follow the guide for step by step instructions on how to do everything and have the required files!
Rooted at&t version you don't have to do anything special just update normally *Sweet tits it already uploaded to my Google Drive! now its available to anyone Links are below this [I'm pretty sure if you have Rogers version you can update with this as well,but you need to have root to have your /efs partion backed up because in some cases it was reported lost.]
Firmware:
ICS 4.0.4 UCLJ3 Mirror 1 SamMobile(needs account) Mirror 2 My Google Drive (anyone can access no account required and fast speeds!-a txt file is included if you need more help you out on flashing it )
and here's also a guide on how to flash it!(if you are following this guide please use Bubor's TWRP as it is needed for KitKat ROMS)
*If you are not rooted /at&t version and want to update:
you can simply use Kies
If and after you updated though Kies,make sure you uninstall Kies before you install ODIN.
Basically follow this youtube video and install TWRP not CWM!!!
I can't stress how important it is to Have TWRP, CWM will simply not work,but if you installed CWM its not hard at all to change! Just flash this in CWM and your recovery will change to TWRP
http://www.youtube.com/watch?v=Cn879wTAXi4
If on mobile or non flash device click here
While watching this video please flash TWRP!!!!!
You should now be fully updated and rooted!!!
[BEFORE YOU FLASH]
This is not necessary if you are staying on your current network,but if you want to unlock your phone to another network,It would be cool to see this first: http://forum.xda-developers.com/showthread.php?t=1860003
------------------------
[FLASHING]
Here is a list of currently active ROMS (as of 1/24/14)
(Bubor's, grtsarav's,and xdajog's ROMS) The only bugs which are in JB+(4.1+) include,No Bluetooh Headset (everything else works fine,BT speaker file transfer ect.) Fixed camera Rotation,meaning when you take a Picture it will always be rotated at 90 degrees,just rotate them in gallery.
Anyway the ROM I use is CRdroid 4.4.4,but if your looking for something a little more Stock based use sediROM.
But i'm not the one to tell you what ROM to get! Try them all! Or try just try one! What ever you like! All I know is you'll enjoy the life and freedom with a custom ROM!!!
*Please read if you have a JellyBean ROM* all Jellybean ROMS haven't been updated in awhile.If you would like a ROM that is guaranteed to have updates please choose a KitKat branch or use sediROM (which is ICS 4.04)
-----------------------------------------------
Lollipop (Android 5.0-5.0.x)
Alsas Fix -It is baked into the ROM,download terminal emulator to activate
CyanogenMod 12 5.0.2 Last Update: 03/02/15
Current Status: Stable
-Root: can be enabled in development settings,enabled by tapping build number 5 times!
Bugs: Unfortunately if you want to use this ROM you sacrifice your camera.²Apparently apps that didn't work in 4.4 work fine in this build,meaning you can use latest google now ect.
----
KitKat (Android 4.4-4.4.4)
Note:* the alsas fix (aka skype fix) has its own version for 4.4.3 and 4.4.4,here's the link for 4.4.3*
Here's the link for 4.4.4
*Freshly updated 4.4.4*
CyanOgenMod 11 M12 (KitKat 4.4.4) Last update:01/13/15 Current Status: Very Stable
OMNI ROM (Kitkat 4.4.4) Last update:12/23/14 Please go to Test Directory for this version (window mode feature) Current Status: Very Stable
P-A-C Man ROM RC1 (KitKat 4.4.4) Last update:12/23/14 Current status: Very Stable
grtsarav's ROM:
*updated to 4.4.4*
crDroid Simple (KitKat 4.4.4) Last update: 10/02/14 Current status: Very Stable
Note:* the alsas fix (aka skype fix) has its own version for 4.4.3 and 4.4.4),here's the link for 4.4.3*
*Here's 4.4.4*
]
>All 4.x.x ROMS<*It has came to my attention that some apps aren't compatible with our phone anymore.This is due to a bug in the Nvidia GPU and NEON Instructions that our CPU is not compatible with.
Below I have provided the latest versions of affected apps that work with our phone:
Google Now (Search) 3.3.11.1069658-If GNL Says you need a newer version of search downgrade it
Google Now Launcher-Use this If The latest GNL says you need a newer version of search
Youtube 5.3.32-Some say the latest version works,but it crashes constantly.This one doesn't.
Google Camera 2.2.024 -Tested works great!
Google Maps 6.14.4 -the latest works but there's a bug in the NV Graphics that gives you a black screen when you leave the app and comeback to the same session o_0
4.4.x Gapps package from 03/16/14-Okay we lucked out here,I couldn't find an old Gapps package any where on the web containing compatible Google Now and guaranteed no F/Cing apps ,then I check an old folder I had on my phone.What do you know? I have the file saved from way back
If you installed a newer version of these apps that didn't work,just uninstall the updates and install the one provided!
also If you find an app no longer compatible with this phone let me know and I'll post an older version that does!
Ice Cream Sandwich (Android 4.0-4.04)
xdajog's ROM
(Private beta testing completed.)
SediROM v1.6*1.6.21* (Ice Cream Sandwich 4.0.4) Current Status: Very Stable
Last update:01/08/15 Compatible with enterprise apps
Now has the option to turn root (su) off or on!
NO SKYPE OR ALSAS FIX NEEDED!
Everything works including Bluetooth headset
Very Recommended ROM!
Please report bugs promptly so he can give you the best experience
-----------------
ROMS that haven't been updated in awhile:
Jelly Bean (Android 4.1-4.3)
P-A-C Man ROM (Jelly Bean 4.3.1) Last update:02/25/14 Current Status: Support probably ending soon...
CyanOgenMod 10.2.1 (Jelly Bean 4.3.1) Last update:02/25/14 Current Status: Support probably ending soon...
(Discontinued as of January 2014) OMNI ROM (JellyBean 4.3.1)
-------
For older ROMS click here
you must change the assert tag to flash in TWRP:
@Bubor:You may want to install older rom, you must change assert tag in rom zip file META-INF/com/google/android/updater-script:
Code:
assert(getprop("ro.product.device") == "i927" || getprop("ro.build.product") == "i927" ||
getprop("ro.product.device") == "SGH-I927" || getprop("ro.build.product") == "SGH-I927" ||
getprop("ro.product.device") == "SGH-I927R" || getprop("ro.build.product") == "SGH-I927R" ||
getprop("ro.product.device") == "SGHI927" || getprop("ro.build.product") == "SGHI927" ||
getprop("ro.product.device") == "SGHI927R" || getprop("ro.build.product") == "SGHI927R" ||
getprop("ro.product.device") == "n1" || getprop("ro.build.product") == "n1" || abort("This package is for \"i927,SGH-I927,SGH-I927R,SGHI927,SGHI927R,n1\" devices; this is a \"" + getprop("ro.product.device") + "\"."););
Click to expand...
Click to collapse
--------------------------------------------
Custom Kernels: (Not required! If you don't know what this is,skip this section!)
GraKernel by Grarak compiled by bubor
Fixes some wifi issues,sleep of death, and stable over clock (when you first flash go to system settings>preformance>processor>change maximum CPU frequency to 1200mhz (stock is 1000mhz)
If you want to go back to 4.0.4 stock the easy way just click me
------------------------------
[HOW TO FLASH VIA TWRP] (which you should have!!!!)
If you already flashed a custom recovery to your phone via odin heres what you do:
1: save all data, shutdown your phone
2: hold vol down and power
3: let go of power
4: your phone should now say "booting into android recovery"
5: you should now be in recovery
6: firstly, click "Backup"
7: Back up the desired Partitions
8: Swipe to Back Up
9: Let back up complete (can take some time depending how much stuff is backing up)
10: Return to the main menu
11: Locate "Wipe"
12: Swipe to Factory Reset (before you freak out it, DOES NOT WIPE YOUR INTERNAL AND EXTERNAL SD CARDS!)
13: Locate "Install'
14: Find your ROM (if you downloaded your ROM from your phone it is usually in /sdcard/download)
15: "Swipe to install zip"
16: Let your ROM install (it will take some time)
17: Congratulations you have a new ROM on your Cappi!
---------------
[F.A.Q] {new question added 5/30/14}
Q: A new update has been released for my phone do I need to Factory Reset my phone?
A: No just flash on top of it but make a backup first just in case the update has problems
Q: I'm coming from a different ROM (like OMNI ROM) can I restore my /Data or flash on top of my current ROM?
A: No, if you are doing something like that I would use Titanium Backup to backup your data and apps
Q: I'm coming from stock do I need to unlock my bootloader to install custom ROMS?
A: No all you have to do is have a custom recovery and you're good to go!
Q: I see I need to backup my EFS, is it really necessary?
A: Not really but, its not a bad idea to do it,download this,if you need a step by step guide click here
Q: Do I need to flash any Custom Kernels, GAPPS ect.?
A: All Bubor's ROMS have everything built in,but grtsarav's ROM requires a GAPPS package
more info on his ROM page
Q: I have the Rogers version of the i927 do I need to do anything special?
A: No all the ROMS are universal
Q: Why can't I just flash TWRP and a ROM without updating to 4.0.4 ICS first?
A: You could, but we say update first you can avoid unknown issues with Baseband (that's like sleep of death dropped calls ect.)
----------------
[MISC.]
>Only do if you flashed a GApps package not including search<*If you want 'Ok Google to work on your ROM and offline voice data:
1: Download this:en-US.zip
2:Install:HAVE GOOGLE NOW INSTALLED!
1:Extract with your favorite extracting app (i used root browser) to /data/data/com.google.android.googlequicksearchbox/app_g3_models
2:use rootbrowser and check every premission by long pressing file:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then:
*This also gives you offline voice typing (System>Language and input>Google Voice Typing)Enable it
I recommend You use Google keyboard by Google it integrates both in one awesome keyboard here's play link
*How to enable voice typing
1: Have google keyboard and Google Now (In playstore its called Google Search)
2: Make sure you have Voice Search enabled:System>Language and Input-Check Google Voice
It should look like this:
3:Now go somewhere where you can open Google keyboard and long press the comma left of the space bar
4:A box should come up saying "Input options"
5:Click Google Keyboard Settings
6 :Check Voice input key like this:
8: Finally your outcome should be this:
------------------------------------------------
-UPDATED 3/25/14- *How to get a fully functional GNL (Google Now Launcher) it all works!
It's been released on Google Play!
Known issues: the always listening feature may make all sounds lag when using "Stock libs" (original sound drivers in "windows terms").Skype fix (tiny alsas) fixes this. Just type command from terminal when making a call,that's what I do.
read "Skype Fix" below for more info and how to install it
Older Versions(might need older Google Now?)
First Release
Second Release
------------------
*How to install Google's Documents UI (Google's new file explorer)
Download the apk >here<
1: after you downloaded the apk copy and paste into System>app
2a: if you are on CyanogenMod it will ask you if you want to over write the file,tap yes
2b: set the permissions to r-w-rr
3: reboot and watch the magic
-----------------
[KITKAT ONLY]
*How to have a custom wallpaper on your favorite KitKat ROM:
-Before we get started CRdroid has Custom wallpaper setting built in after build 5-
-CM11 also has it now where you can set a custom locksceen wallpaer (settings>themes>lockscreen wallpaper)-
Anyways if your ROM doesn't support it here's how to get it:
1:Basically you need to have XPOSED Frame work,you can get it freshly updated here
2: After you install Xposed Frame work installer,install and reboot
3: There are two routes you can take,you can download GravityBox and have more customization,but it does break some CM settings (theoretically its not supported, but I've used it and it works perfect,it also adds the AM/PM feature).The other route is Xposed lockscreen,which basically the title states what it does,customize your lock screen!The only feature it has is custom wallpaper for lockscreen
4: you can fetch GravityBox here and Xposed lockscreen here
5: MAKE SURE you activate your module you choose and don't have both active at the same time!
-------------
[SKYPE FIX]
*How to use Skype or VOIP apps with ease this also fixes the lagging sound issue with Google now/launcher! This Will work on any of our KitKat based ROM's:
1: flash This zip in Recovery:4.4.2 ROMS: >here<
4.4.3 ROMS: >here<
4.4.4 ROMS >here<
2: After you flashed that,reboot into system
3: Open Terminal Emulator (it's included in CM,but if you don't have it click here
4:in terminal type "su" to get root premissions
5:Run "alsas" command to switch audio stacks,at anytime to switch between GSM (regualr calling) and voIP (like skype ect.)
Notes:When you first flash the zip it will switch it to voIP-aware,CHANGES ARE PRESISTANT,meaning to have GSM calling you need to run the command from terminal everytime you want to switch between the two
-
For JellyBean ROM's (4.1-4.3)
1: Download this zip
2: Flash zip from recovery
3: The first time you flash the zip it will change it to voIP aware (so you can use skype or any other voip calling app)
4:to use GSM calling,simply flash the zip again! Basically flash when your done using Skype!
---------------
FINNALY
If any other questions need to be asked feel free to comment below (probably the best place its a nice area!)
or PM me if necessary! If you want to report any bugs about any of our Developers ROMs please, and I mean PLEASE report only new bugs that haven't been reported!
---------------
[CREDITS]
*Bubor*-For ROMS,Recoverys,and for keeping the Captivate Glide alive!!!
*grtsarav*-For your ROM and helping the community with your port!!!
*xdajog*-For Giving the community a good choice of ICS!!!
*dman3285*-For giving us an easy way to return to stock
*Darkshado*-For showing us how to network unlock our phone
*dbrannon79*-How to backup EFS
*TheTechnologicalKing*-Supplying youtube video
*KennyG123*-For stickying this thread so people can easily find it!
*Other Respectable Devs*-as I add new apps I can't really add all of them at once,so this is my thanks for the applications you've made!
--------------
[UPDATES & ADDED APPLICATIONS]
Please view this to see how far we've come >>>
01/26/14 uploaded a version of EFS pro backup (the version provided by dbrannon79 would not work on the glide anymore because too new)
02/01/14 some polishing and simplification also added link to Google keyboard.Will update more later tried updating from phone so may be a little off. Will add how to flash TWRP from ODIN from this thread (eventually no external threads!) User feed back would be awesome! If something needs a change or you want me to add something let me know!
SD:2/01/14 Changed links to google (when will microsoft learn?)Will make an updated video on how to ODIN TWRP when I have more time ; Thanks for user input:*dragonfire613*
02/05/14 Updated Google Experience Launcher to latest version Ripped straight from update! It's Now called "Google Now Launcher"
LTD 02/05/14 Tweaked some stuff
02/08/14 added link to Samsung Kies;Made guide more user friendly!
02/15/14 added when ROMs were last updated; added how to get Google's ''Documents UI" on any KitKat device (haven't tried on JellyBean?)
Bubor updated CyanogenMod 10.2.0 to 10.2.1
02/17/14 added how to have a custom wallpaper on your favorite KitKat ROM
02/23/14 added Skype fix thanks *mrk2815* for telling me,thanks also to S-trace for simplifying skype fix on ROMS!;Added JB fix
02/25/14:updated header
03/08/14: ROM updates
03/12/14 ROM updates
03/16/14 ROM updates and added grtsarav's ROM
03/17/14 ROM updates and tweaks
03/24/14 ROM updates and updated info about flashing TWRP,all versions are up to date and ready for KitKat!
03/24/14 tweaks about GAPPS,updates about GNL
03/27/14 New ROM!
04/03/14 ROM updates and ROM Stability updates!
04/08/14 PAC ROM 4.4 Moved to development section,as of now,it will be maintained
04/14/14 Some useful info
04/18/14 ROM updates
05/02/14 ROM updates
05/05/14 ROM updates and some info regarding JellyBean ROMS
05/16/14 Added the latest version of Google Now that works on our device right now
05/17/14 Changed The Google Now link to my Google Drive
05/26/14 ROM updates
05/28/14 Thanks Adam77Root for showing me the hide tag!
05/30/14 ROM updates
06/06/14 ROM updates.We're now on 4.4.3!!! Added how to flash older ROMS
06/11/14 All of our KitKat ROMS are 4.4.3 now
06/20/14 We have a new ROM check it out! Its ICS
06/28/14 My birthday was yesterday! ROM updates Most ROMs are updated to 4.4.4;Clean up
07/08/14 Updated List of current ROMs; Sorry I did't update I was on vacation
07/19/14 SediROM has entered public beta phase
07/20/14 Fixed a slight error
07.22/14 xdajog's ROM update and new info about SediROM
07/27/14 Bubor's ROM updates
07/29/14 We got stickied!!!
08/06/14 grtsarav's crDROID ROM updated,go flash today!
08/23/14 SediRom Updated to RC2 You know the drill!
09/03/14 Tried to simplify on how to update to latest firmware,I fixed the dead links to download the firmware,its from sammobile let me know if it works
09/04/14 Big Big update hope this helps out! don't forget to drop a thanks! that makes my day!
09/08/14OMNI ROM and PAC ROM got updated! What are you waiting for? go flash it!;Fixed some stuff to do with Rodgers version
09/18/14 CM11 got updated,now it has great battery life;PAC ROM updated to RC1,also on any ROM the latest YouTube doesn't work you must downgrade.I will supply the latest version that does when I have time
09/19/14 CM11 updated to M10,more about what's new in M10 here
09/20/14 added links to latest versions of certain apps that can't be updated anymore
09/24/14 Google Camera was added to that list.Also I got my hands on a 64 bit PC so LS ROM is coming soon...when I am home to install linux and setup the build environment of course!
09/25/14 Added a version of google maps;Got a hold of my captivate,tested Google Camera version I posted. It works Perfectly! Updated Lockscreen wallpaper info
10/02/14 crDROID ROM got updated,so flashy flashy
10/03/14 Added a Gapps package that is 100% compatible with our phone no F/Cing apps :good:
10/20/14 Sorry I didn't update this sooner,I've been very busy with my new job!All of Bubor's ROMs are updated! go flash and see whats new!
11/11/14I have added a poll so our developers can know which roms were actually using
01/15/15 Updated every ROM! Sorry I haven't been posting been very busy at my new job! I'll try not to be behind!
Changed to 2015!
04/22/15Got my Cappy back to test with. Played with cm12 added. What bugs I have discovered and updated to the latest Dow loads!
Extra Tips
[ hide]-FUTURE USE-.[/hide] You read the whole guide? Wow! thank you for your time!!!
stickied on 07/29/14
I hope I simplified your day! If you don't understand anything,please don't hesitate to ask any questions. I am friendly
I won't get mad if you post a noob question (all I ask is to read the comments first and see if your question has already been answered!)
The skydrive link is dead
That's Microsoft they are changing to onedrive or something I'll fix it around 1pm CST
Sent from my Kitkatified I927 running CM 11
Try this link right now: https://skydrive.live.com/redir?resid=99E32AEC5C18FA3!5344&authkey=!AHFGJKAOM68Ou4w&ithint=file,.zip
I'm going to switch all to Google drive
Sent from my Kitkatified I927 running CM 11
stormdude124 said:
Try this: https://skydrive.live.com/redir?resid=99E32AEC5C18FA3!5344&authkey=!AHFGJKAOM68Ou4w&ithint=file,.zip
I'm going to switch all to Google drive
Sent from my Kitkatified I927 running CM 11
Click to expand...
Click to collapse
OP Updated with new links and information
For the love of god mention somewhere that you need google search installed before you do anything trying to make voice typing active when offline... that would have saved me hours of headache right there. (I know it's probably obvious to most people, but for dumb noobs like myself, we need to know)
Okay noted XD
Sent from my Kitkatified I927 running CM 11
Does anyone know if the most current OMNI-Rom has multi-window enabled? Or is it only the test rom?
I think its just the test version
Sent from my Kitkatified I927 running CM 11
OP updated for February!
OP updated for March!!!
IEMI removed
I purchased imported unlocked galaxy glide from ebay india , after some day it locked itself. I get it unlocked in local market and it was working fine.
A day suddenly its iemi number changed to generic iemi and as these phones are blocked in india , so its not working here.
Plz guide me what to do?
I am ready to use custom roms but how to back my iemi with unlocked phone?
Plz help
Man, I really hope you backed up your IMEI before you installed your custom ROM
Sent from my SGH-I927 using Tapatalk
stormdude124 said:
Man, I really hope you backed up your IMEI before you installed your custom ROM
Sent from my SGH-I927 using Tapatalk
Click to expand...
Click to collapse
yes i do have all efs files with me
okay awesome! download this
and restore your files,if you need step by step let me know!
CWM ROM flash error status 7
stormdude124 said:
okay awesome! download this
and restore your files,if you need step by step let me know!
Click to expand...
Click to collapse
While flashing CM-11 Kitkat ROM using CWM, it gives an error status 7.
I tried deleting the assert clause as given here http://forum.xda-developers.com/showthread.php?t=2522762
But it give the same error status 7 : set_metadata_recursive changes failed
Somewhere I read that I need to use CWM 6.0.4.5 +. Help me out. Or give some link to latest CWM.
You need to use TWRP (team win recovery project) in the guide it states to flash TWRP not cwm,your in luck though,you can flash twrp through cwm, flash this: http://dualhoki.vim.hu/bubor/dev/twrp-i927/twrp-2.6.1.zip
Then try flashing cm 11
Sent from my SGH-I927 using Tapatalk
omnirom
Hello guys, i have a few question about omnirom, what settings is good for performance in settings>performance>memory ?
and for what is SWAP int-sd card? it's good for performance? or just space?
Tabo8226 said:
Hello guys, i have a few question about omnirom, what settings is good for performance in settings>performance>memory ?
and for what is SWAP int-sd card? it's good for performance? or just space?
Click to expand...
Click to collapse
If you don't know what settings will be good, don't touch them, they're mostly for fine-tuning system built-in app killer. You hardly can have much profit from changing them, only if you need a bit more RAM badly.
SWAP int-sd card is for using your sd card as internal memory (so you can install apps there). You should use it if 4 gb of internal memory is not enough for you (as it is for me as I'd like to install couple of 1-2 gb games). You will lose performance with swap if your SD card is less that 10 speed class.
Given that BT doesn't work in the newer ROMS (JB & KK), I regrettably had to revert back to 4.0.4. I found that I needed to replace the recovery with CWMR from TWRP in order to install one of DMAN's ICS ROMs. TWRP failed to install the 4.0.4 ROM.
After replacing the recovery, it is probably a good idea to backup the new ROM (JB or KK) using CWMR so that you can restore it if desired at a later time.
This may be a dumb question bit I can't seen to find the answer. I've seen gee roms and ls970 roms. What's the difference between the two? Why should I choose one over the other?
Sent from my LG-LS970 using Tapatalk
spleef said:
I can try ...k so the ls970 is official cm sources shelnutt2 put together based off the gproj is usable only on the sprint lgog
The geehrc (international lgog) and the geespr (sprint lgog) are based in the mako and put together by xboxfanj... currently x has combined the two sources (geehrc and geespr) into one source (gee) for both making the one zip built with gee flashable on both variants...
The whole cwm twrp issues are the differences n each sources and or ROMs way to build the updater script...
And yes some roms play nicer with cm sources than they do aosp sources and vice cersa.. so saying that cm is well obviously cm based sources where as xboxfanj sources are closer to or are aosp
Hope I'm at least somewhat making sense
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
xboxfanj said:
LS970 ROMs are built from CM's Nexus 4 4.2.2 hybrid with stock 4.1.2.
GEE/SPR/HRC are built from the Nexus 4 4.4.2 source (more up to date and optimized) with only changes for our hardware such as NFC.
geespr is sprint only, geehrc is international only, and gee combines the two so both devices can run the same build. Gee is the future of mako-based ROMs and eventually, there won't be any geespr or geehrc roms. Those are being phased out.
Click to expand...
Click to collapse
Hope this helps...its from the Liquid Smooth thread.
Sent from my Optimus G using xda app-developers app
elvyrorie said:
This may be a dumb question bit I can't seen to find the answer. I've seen gee roms and ls970 roms. What's the difference between the two? Why should I choose one over the other?
Sent from my LG-LS970 using Tapatalk
Click to expand...
Click to collapse
let's see If I can get this right...
Our phone is a bit confusing because the developers couldn't agree on one name.
The official names from the stock ROM build.prop:
Code:
ro.product.model=LG-LS970
ro.product.name=geehrc4g_spr_us
ro.product.device=geehrc4g
Just before Team CodeFire unlocked the many Optimus G variants, the first new name the they came up with for our device was "geebus".
And then many names followed...
Example from CM11 updater script:
Code:
assert(getprop("ro.product.device") == "geebus" || getprop("ro.build.product") == "geebus" ||
getprop("ro.product.device") == "geebusc" || getprop("ro.build.product") == "geebusc" ||
getprop("ro.product.device") == "geehrc" || getprop("ro.build.product") == "geehrc" ||
getprop("ro.product.device") == "geehrc4g" || getprop("ro.build.product") == "geehrc4g" ||
getprop("ro.product.device") == "gee_sp" || getprop("ro.build.product") == "gee_sp" ||
getprop("ro.product.device") == "geehrc_sp" || getprop("ro.build.product") == "geehrc_sp" ||
getprop("ro.product.device") == "geehrc4g_spr_us" || getprop("ro.build.product") == "geehrc4g_spr_us" ||
getprop("ro.product.device") == "ls970" || getprop("ro.build.product") == "ls970" ||
getprop("ro.product.device") == "jeebus" || getprop("ro.build.product") == "jeebus" ||
getprop("ro.product.device") == "jeebusc" || getprop("ro.build.product") == "jeebusc"
The confusion behind "gee" and "ls970" is because there are two main ANDROID bases for us and they are incompatible with each other.
<History>
While Team CodeFire were rolling with the "geebus" name, early attempts to port AOSP and CyanogenMOD to the many Optimus G variants used the Nexus 4 (Mako) ROM & kernel as a base with optimus g stuff mixed in.
Since we were the odd man out with the 13MP camera, our name had to change to be more specific; back to "geehrc4g" and then "geespr".
The "hybrid Mako" base was a little unstable and camera auto-focus was not working for us.
CyanogenMOD requires that everything works to become OFFICIALLY supported.
The "gproj" team working on OFFICIAL CyanogenMOD status for the international variant (e975) used their own device as a base and was the first to become officially supported by several months.
Team CodeFire followed suit and scratched (but not abandoned) the hybrid mako base and used our own device (ls970) as a starting point for the remaining variants.
We also changed name from "geespr" to "ls970" because CyanogenMOD requires you to use your device's model name (or because the code base change, IDK).
While things became rock stable we were still having the camera auto-focus problem (but was not a stopping issue).
ls970 and e970 became officially supported by CyanogenMOD with the "ls970-common" base.
The e975 variant has the same camera as we do and their auto-focus works.
We moved to the "gproj" base while still keeping a few device specific things separated for the other variants (like camera drivers).
Some developers use the CM/gproj base to port ROMs to our device and usually refer to "ls970"
Some developers also used the hybrid Mako base to port ROMs to our device and and usually refer to "geespr" (and now "gee")
The hybrid Mako base (still not abandoned) has become rock stable and has the auto-focus problem fixed.
More recently the hybrid Mako base developers have unified the code for some of the variants and now we are "gee".
</history>
So which is generally the more stable of the two?
Sent from my LG-LS970 using Tapatalk
elvyrorie said:
So which is generally the more stable of the two?
Sent from my LG-LS970 using Tapatalk
Click to expand...
Click to collapse
I've read it depends on your phone lol. Some have better experience with gproj based ROMs others have better experience with Mako based ROMs...
Sent from my Optimus G using xda app-developers app
MikeEx said:
let's see If I can get this right...
Our phone is a bit confusing because the developers couldn't agree on one name.
The official names from the stock ROM build.prop:
Code:
ro.product.model=LG-LS970
ro.product.name=geehrc4g_spr_us
ro.product.device=geehrc4g
Just before Team CodeFire unlocked the many Optimus G variants, the first new name the they came up with for our device was "geebus".
And then many names followed...
Example from CM11 updater script:
Code:
assert(getprop("ro.product.device") == "geebus" || getprop("ro.build.product") == "geebus" ||
getprop("ro.product.device") == "geebusc" || getprop("ro.build.product") == "geebusc" ||
getprop("ro.product.device") == "geehrc" || getprop("ro.build.product") == "geehrc" ||
getprop("ro.product.device") == "geehrc4g" || getprop("ro.build.product") == "geehrc4g" ||
getprop("ro.product.device") == "gee_sp" || getprop("ro.build.product") == "gee_sp" ||
getprop("ro.product.device") == "geehrc_sp" || getprop("ro.build.product") == "geehrc_sp" ||
getprop("ro.product.device") == "geehrc4g_spr_us" || getprop("ro.build.product") == "geehrc4g_spr_us" ||
getprop("ro.product.device") == "ls970" || getprop("ro.build.product") == "ls970" ||
getprop("ro.product.device") == "jeebus" || getprop("ro.build.product") == "jeebus" ||
getprop("ro.product.device") == "jeebusc" || getprop("ro.build.product") == "jeebusc"
The confusion behind "gee" and "ls970" is because there are two main ANDROID bases for us and they are incompatible with each other.
<History>
While Team CodeFire were rolling with the "geebus" name, early attempts to port AOSP and CyanogenMOD to the many Optimus G variants used the Nexus 4 (Mako) ROM & kernel as a base with optimus g stuff mixed in.
Since we were the odd man out with the 13MP camera, our name had to change to be more specific; back to "geehrc4g" and then "geespr".
The "hybrid Mako" base was a little unstable and camera auto-focus was not working for us.
CyanogenMOD requires that everything works to become OFFICIALLY supported.
The "gproj" team working on OFFICIAL CyanogenMOD status for the international variant (e975) used their own device as a base and was the first to become officially supported by several months.
Team CodeFire followed suit and scratched (but not abandoned) the hybrid mako base and used our own device (ls970) as a starting point for the remaining variants.
We also changed name from "geespr" to "ls970" because CyanogenMOD requires you to use your device's model name (or because the code base change, IDK).
While things became rock stable we were still having the camera auto-focus problem (but was not a stopping issue).
ls970 and e970 became officially supported by CyanogenMOD with the "ls970-common" base.
The e975 variant has the same camera as we do and their auto-focus works.
We moved to the "gproj" base while still keeping a few device specific things separated for the other variants (like camera drivers).
Some developers use the CM/gproj base to port ROMs to our device and usually refer to "ls970"
Some developers also used the hybrid Mako base to port ROMs to our device and and usually refer to "geespr" (and now "gee")
The hybrid Mako base (still not abandoned) has become rock stable and has the auto-focus problem fixed.
More recently the hybrid Mako base developers have unified the code for some of the variants and now we are "gee".
</history>
Click to expand...
Click to collapse
Mostly correct, but there's a couple things I'd like to point out. #1: Geebus was not used on ROMs; it was only used by Tyler on the first recoveries. Also, Team Codefire is really only relevant for the recovery and bootloader unlock; Device sources were made primarily by synergy, Shelnutt2, rlasalle15, houst0nn, chadouming, and I. The first ROMs based on the stock kernel were geehrc_sp or geehrc4g_spr_us. Soon after this, the Canadians (chadouming, Houst0nn, and Thracky) found that mako kernels booted and worked fairly well on their phones, but along with dvhexer, they had to change some things for our device, such as NFC. Unfortunately for the US variants, our firmware was too different for this to work. Using Canadian firmware did work, but flashing partitions isn't always the safest. Luckily, LG's JB firmware fixed this issue and allowed us to use mako-based kernels. Everything was going well, until we found that people had EFS issues. Seth made a script that would backup EFS and allow you to restore and also created a workaround telephony framework. After that, the only major issue was autofocus. At this point, there were four device repos: Canada, Sprint, AT&T, and International). Meanwhile, Ricardo at CM created a hybrid of stock and the current mako sources (4.2) for the International variant (e975). A couple months later, Seth rebased to his sources, still 4 device sources, but this time named based on model numbers (e973, e970, e975, and ls970) Around this time, I created TeamPlaceholder, with houst0nn, chadouming, and bbelos to create a kernel and device sources based on the latest Qualcomm CodeAurora jb_2.5 sources. Performance was awesome, however, we never got 13MP camera to work, so none of these builds were widely released, however, this is where I created the names for geeb and geespr, mainly out of laziness because having to type geehrc4g_spr_us every time I wanted to build was a pain. As a team, we were also able to merge the AT&T and Canadian variants by enabling SD support for both, since it doesn't negatively impact anything and is the only difference, is just less general maintenance. and meant we only needed to make 3 builds. Eventually, Google also rebased to jb_2.5 for their 4.3 mako kernel, so we scrapped TPH and worked on that, adding only the necessary hardware specific changes from stock (as opposed to all of LG's stock changes, which GPROJ did). Performance was just as good as TPH, everything worked (except autofocus, which was fixed a few months ago by faust93), all was well. Throughout this time, we have updated to the most recent AOSP, since it is fairly easy because we did not deviate much from it, however, gproj did not rebase to jb_2.5 or the AOSP 4.3 kernel, so they are a bit behind us in terms of optimizations. Google did a much better job on the 4.3 kernel than 4.2, so as such, mako-based ROMs should have a bit better performance and are generally more up to date. KitKat was fairly easy to merge into our sources, so we did so fairly quickly. At this point, Chadouming, houst0nn, and I maintained mako based sources, however, both of them jumped ship, leaving me in charge of most source maintenance. In this time, I became the official Vanir maintainer and have made some kernels. Eventually, I noticed that if the Nexus 5 could run GSM or CDMA on the same sources, we could too, so a month ago, I decided to merge our device and the International variant (geehrc) into one device: gee, using the Nexus 5 sources as reference, meaning that there are only two device sources now on our device: gee and geeb, so all variants can run one of two builds This means that it takes no extra work for someone on AT&T to maintain a ROM for the Canadian variant and vice-versa, same goes for the International and Sprint variants. It has led to great collaboration between the variants and all of you have benefited.
TL;DR: There are two different paths you can take: One closer to stock, but based on an older Nexus 4 4.2 kernel (Gproj) or one with the latest and greatest Nexus 4 4.4.2 sources with only the bare essentials of stock (camera, NFC, etc.)
If you choose stock and Nexus 4 4.2 based, you pick the ls970 ROM.
If you choose Nexus 4 4.4.2 based, you pick the gee ROM.
EDIT: One thing to note: This is the history of the Sprint variant; there are other great devs for the AT&T and International variants, such as arcardinal and dvhexer, but they did not work across all variants, so it's not quite as relevant to us.
@xboxfanj awesome explanation bro!
Sent from my LG-LS970 using xda app-developers app