Base: Android-AOSP-2.3_GRH55
Kernel: [email protected] #1
Credits: Cyanogen, CM61 Nightly
Requirements.
1- Radio: 2.22.27.08|2.22.28.25
2- SPL:1.33.0013d(Dream/Sapphire )
3- Full Wipe and Erase sdcard: .-.android, .android_secure, .android, Android, LOST.DIR and temp from SDCard
4- Flash Rom from Recovery
5- Reboot
6- Register your google account with the market
7- Change the color of the clock and date from CyanogenMod Settings
8- Enjoy!
Mod Edit: Confirmed Fake, thanks XDA Moderator Jamezelle for finding this: Scroll Right to see android:versionName="2.2.1"
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest android:sharedUserId="android.uid.system" @[email protected]:versionCode="8" [B][COLOR="Red"]android:versionName="2.2.1" [/COLOR][/B]package="com.android.settings"
xmlns:android="http://schemas.android.com/apk/res/android">
@[email protected] <uses-sdk android:minSdkVersion="8" android:targetSdkVersion="8" />
<original-package android:name="com.android.settings" />
<uses-permission android:name="com.google.android.gm.permission.WRITE_GMAIL" />
<uses-permission android:name="com.google.android.gm.permission.READ_GMAIL" />
<uses-permission android:name="android.permission.WRITE_SETTINGS" />
<uses-permission android:name="android.permission.WRITE_SECURE_SETTINGS" />
<uses-permission android:name="android.permission.DEVICE_POWER" />
What not working:
so far everything works.
Ignore post
Does Wifi/Bt on yet or is that broken.
I thought 2.3 wasnt on g1 yet cause of some of the other ginger threads saying it's not supported anymore..
LOL
might try it in the morning when i remove my g1 from the ps3 lol but looking forward to this "AOSP 2.3" build
"everything works"
wonder if its a 2.2.1, cyanogen 6.1 with a theme on top and build.prop edited to show 2.3
by all means im not slagging your work. i will test in the morning and edit post accordingly
Exciting news. Will test. Thanks for the Share.
Good try
In any case a nice froyo theme.
-_-'' FROYO WITH THEME!!!!!!!!!!!
*golf clap*
Yea flashed it got to the Google sign in then it fc about framework the rest of the time good to see we atleast got a 2.3 that booted up good job!
Sent from my T-Mobile myTouch 3G using XDA App
Wait, is this actually real?
Seriously why lie?
just a suggestion: when you post screenshots of the Market, you might want to find one where the Market is working. "no matching content in Android Market". You fail, sir.
Wow, the themes not even complete -_-
The menus are white not black, the settings aren't supposed to be colored like that, and the dialer is the old one from froyo/eclair
Troll harder, bro
So can anyone give final confirm: Is this actually a 2.3 based rom, or just a themed CM?
bigmoew said:
So can anyone give final confirm: Is this actually a 2.3 based rom, or just a themed CM?
Click to expand...
Click to collapse
Themed CM
/thread
ITS NOT 2.3~~
Oh wow, thats epic-level fail
Under Investigation
Confirmed Fake: android:versionName="2.2.1"
See OP post for my edit
Related
Figured I'd make my personal AOKP builds available to the public domain. I basically took AOKP source, added CM9's MSM8660, SkyRocket, and QCOM_MEDIA source to the mix. Changed a couple XML files and voila get AOKP built with SkyRocket support.
I'm not developing anything, just compiling and making the builds available to those that want to try. I've been cherry picking fixes important for SkyRocket from the CM9 team before they're merged, too.
One thing I did notice was the Camera doesn't get built/added, but downloading a camera from the Store seems to work fine. Other than that, everything appears to be working. I'd be interested in hearing what works and doesn't work.
CM9 is my daily driver, but did this for some fun. I have detailed instructions on what I do to a stock AOKP source to get it to compile if you want them.
Thanks go out to the usual suspects...
Team Chopsticks
CyanogenMod Team
AOKP Team
I'm sure there are others, but not sure who they since I grabbed from Github sources.
Feel free to mirror. I will post updates everyday to the link below.
Latest Build
6/17 Build 38 http://d-h.st/3Go
6/15 Build 38 http://d-h.st/jCN
6/13 Build 38 http://d-h.st/Tmx
6/11 Build 38 http://d-h.st/U98
Make sure you are using the UCLE2 Radio since everything in these builds is UCLE2-based.
Build 38 Change Log
reverted tablet nav bar button padding change (back to stock ics padding now)
fix SMS/BT crash bug when no msgs exist
reworked lockscreen music layout to be cleaner
fix ugly gradient on dark holo background
added AOKP Tips widget
added statusbar autohide for tablets (for apps that need full screen)
added support for more lockscreen targets (2-8 options, your choice)
cleaned up octo lockscreen layout
fixed certain FCs with RC related to weather
Mms: fixed stripping certain Polish characters
decreased size of custom lockscreen apps to match other icons
statusbar brightness enabled by default after you wipe (sliding thumb across statusbar to change brightness)
added statusbar notification counter (RC > Statusbar General > Notification Counter)
new AOKP boot animation from @rascarlo
Out of range Bluetooth devices won't show up anymore in Settings
Browser: added option to close all other tabs (besides current)
Fixed data toggle
Removed requirement to reboot when toggling keyboard switcher (IME switcher) in statusbar
added nav bar widgets (to enable, go to nav bar settings > add toggle widgets as one of your nav bar actions/ long press actions, then add widgets -- be sure to add at least 2 for best experience)
as always, tons of fixes for devices and other backend fixes!
Installation Instructions
Here's what I do...
DARKSIDE WIPE (http://forum.xda-developers.com/showthread.php?t=1477955)
Format CACHE (Super important that you don't skip this. Darkside does something to /cache that causes CM9/AOKP to boot loop)
Install AOKP zip
Install GAPPS zip (http://goo.im/gapps/gapps-ics-20120429-signed.zip)
Reboot
Open System Settings->More (under Wireless & Networks)->Mobile Networks->Access Point Names
Select the WAP APN...
a. APN = PTA
b. Username = BLANK (delete whatever is there)
c. MMSC should be http://mmsc.mobile.att.net
d. MMS Proxy = proxy.mobile.att.net
e. Hit Menu button and select SAVE
Give it a few seconds and data should be working
Install camera app from Google Store (I'm working on getting this to compile into the build)
Build Instructions
Here's what I do starting from the root of the build directory
Setup up AOKP repo and sync it (i.e. repo init -u git://github.com/AOKP/platform_manifest.git -b ics && repo sync)
Create a file called local_manifest.xml in .repo directory with the text below.
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_samsung_skyrocket" path="device/samsung/skyrocket" remote="gh" revision="ics" />
<project name="CyanogenMod/android_device_samsung_msm8660-common" path="device/samsung/msm8660-common" remote="gh" revision="ics" />
<project name="TeamChopsticks/android_kernel_samsung_msm8660-common" path="kernel/samsung/msm8660-common" remote="gh" revision="ics" />
<project name="TeamChopsticks/android_vendor_samsung_skyrocket" path="vendor/samsung/skyrocket" remote="gh" revision="ics" />
</manifest>
Run "repo sync" again to get the above added trees
Edit device/samsung/skyrocket/overlay/packages/providers/TelephonyProvider/res/values/config.xml
Delete config_preferred_apn line and save
Edit device/samsung/skyrocket/overlay/packages/apps/Settings/res/values/config.xml
Delete has_led_flash line and save
Edit device/samsung/skyrocket/full_skyrocket.mk
Change the word "Torch" to "Camera" and save
Create a file called "skyrocket.mk" in vendor/aokp/products with the text below
Code:
$(call inherit-product, device/samsung/skyrocket/full_skyrocket.mk)
# Inherit some common CM stuff.
# $(call inherit-product, vendor/cm/config/gsm.mk)
$(call inherit-product, vendor/aokp/configs/common_phone.mk)
# Inherit some common CM stuff.
# $(call inherit-product, vendor/cm/config/common_full_phone.mk)
PRODUCT_BUILD_PROP_OVERRIDES += PRODUCT_NAME=SGH-I727 TARGET_DEVICE=SGH-I727 BUILD_FINGERPRINT="samsung/SGH-I727/SGH-I727:4.0.4/IMM76D/UCLE2:user/release-keys" PRIVATE_BUILD_DESC="SGH-I727-user 4.0.4 IMM76D UCLE2 release-keys"
TARGET_BOOTANIMATION_NAME := vertical-480x800
PRODUCT_NAME := aokp_skyrocket
PRODUCT_DEVICE := skyrocket
PRODUCT_BRAND := samsung
PRODUCT_MANUFACTURER := samsung
PRODUCT_MODEL := SAMSUNG-SGH-I727
Edit AndroidProducts.mk in vendor/aokp/products and add "$(LOCAL_DIR)/skyrocket.mk \" above stingray.mk line.
Run "source build/envsetup.sh"
Run "make clobber && lunch aokp_skyrocket-userdebug && make -j<number or processors X number of thread per processor> bacon"
These are the steps that work for me. I hope they work you as well. Let me know and I'd be happy to help.
so would i install this the same way as i do cm9 (instruction wise)?
That's correct. I'd do a full wipe and install. I've been running the 6/3 build for 24 hours with no problems. Only thing I had to do was install camera 360 and change apn to PTA.
Sent from my SAMSUNG-SGH-I727 using xda premium
Got it and loving it thank you so much for sharing
6/4 Build https://www.sugarsync.com/pf/D7693548_2736667_069288
Camera should be working in this build. Let me know.
i can confirm that the camera is working for me
InstigatorX said:
6/4 Build https://www.sugarsync.com/pf/D7693548_2736667_069288
Camera should be working in this build. Let me know.
Click to expand...
Click to collapse
Shouldn't this be in the Development forum?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
SassyMrsK said:
i can confirm that the camera is working for me
Click to expand...
Click to collapse
Is this running better than the team wafflehouse release?
Sent from my SGH-I727 using xda premium
i've never used teamwafflehouse just teamchopsticks sorry
abteer said:
Is this running better than the team wafflehouse release?
Sent from my SGH-I727 using xda premium
Click to expand...
Click to collapse
You guys are hurting my feelings here lol I will say though thanks for the nightly builds bro good work
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
IEatKittys! said:
Shouldn't this be in the Development forum?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
I'm not really "developing" anything, just having some fun compiling from AOKP/CM9 source. I'd be happy to post my build instructions if you anyone is interested.
nrm5110 said:
You guys are hurting my feelings here lol I will say though thanks for the nightly builds bro good work
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Thanks!
InstigatorX said:
I'm not really "developing" anything, just having some fun compiling from AOKP/CM9 source. I'd be happy to post my build instructions if you anyone is interested.
Thanks!
Click to expand...
Click to collapse
I think it would be helpful and/or a nice addition.
Sent from my SAMSUNG-SGH-I727 using xda premium
Might have screwed up... but how do I get my phone rooted again after installing 4.0.4?
abteer said:
Is this running better than the team wafflehouse release?
Sent from my SGH-I727 using xda premium
Click to expand...
Click to collapse
Yes and no, is it more up to date with the work being done? Yes, but are you expected to run into bugs? Yes.
The wafflehouse builds are tested, modified, played with, and released on a basis of what works, and you know in advance usually.
With nightly builds you NEVER know what the state of it will be. Data may not work on one, but work on the next nights, camera might work on one but not the next nights etc. Since these roms are in a constant state of development right now you never know what may happen.
So yes these are a bit more up to date than wafflehouse.
Better, is subjective to the build and build date.
If you really like messing with your phone and a flash junky, use the nightlies, if you want someone to help out and make sure things work stick to waffles.
is it possible that this may work on the t989?
k786 said:
is it possible that this may work on the t989?
Click to expand...
Click to collapse
You guys have your own builds silly. I'll PM you.
R4INS said:
Yes and no, is it more up to date with the work being done? Yes, but are you expected to run into bugs? Yes.
The wafflehouse builds are tested, modified, played with, and released on a basis of what works, and you know in advance usually.
With nightly builds you NEVER know what the state of it will be. Data may not work on one, but work on the next nights, camera might work on one but not the next nights etc. Since these roms are in a constant state of development right now you never know what may happen.
So yes these are a bit more up to date than wafflehouse.
Better, is subjective to the build and build date.
If you really like messing with your phone and a flash junky, use the nightlies, if you want someone to help out and make sure things work stick to waffles.
Click to expand...
Click to collapse
Couldn't agree more.
Sent from my SAMSUNG-SGH-I727 using xda premium
OP updated with 6/6 build. Got distracted yesterday.
Second post updated with BUILD INSTRUCTIONS.
At the present time, it appears that AOKP is again moving some of their git repositories around. As a result, the Team Acid build environment is "broken" until AOKP updates their repo manifest. It doesn't matter if you are doing this manually, or through Acidify.
Please read the entire thread as work-arounds have been changing from day to day.
One of the issues is that AOKP's frameworks/base and prebuilt git repos are returning
Access to this repository has been disabled by GitHub staff due to excessive use of resources. You'll need to contact support to restore access to this repository. Read here to learn more about decreasing the size of your repository.
That is something neither Team Acid nor you can resolve if you don't already have a copy of frameworks/base and prebuilt. If you do, you can call repo -f sync which will skip a given git repository if there is a failure and continue with the rest.
Here are some work-arounds for the other issues
Patch your .repo/local_manifest.xml to replace the old git repos with their new location. Mine now looks like
Check yours after sync to the TeamAcid repo, either direct or thorugh Acidify, as FB has updated the TeamAcid version
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remove-project name="AOKP/android_hardware_libhardware" />
<remove-project name="AOKP/android_hardware_msm7k" />
<remove-project name="AOKP/android_hardware_qcom_media" />
<project path="hardware/libhardware" name="AOKP/hardware_libhardware" remote="gh" revision="ics" />
<project path="hardware/msm7k" name="AOKP/hardware_msm7k" remote="gh" revision="ics" />
<project path="hardware/qcom/media" name="AOKP/hardware_qcom_media" remote="gh" revision="ics" />
<!-- Projects we're removing -->
<remove-project name="AOKP/vendor_aokp_ics" />
<remove-project name="AOKP/vendor_samsung" />
<remove-project name="CyanogenMod/android_bootable_recovery" />
<!-- Projects we're replacing them with -->
<project path="vendor/aokp" name="fbis251/vendor_aokp" remote="gh" revision="ics" />
<project path="vendor/samsung" name="teamacid/proprietary_vendor_samsung" remote="gh" revision="ics" />
<project path="bootable/recovery" name="teamacid/Team-Win-Recovery-Project" remote="gh" revision="master" />
<!-- Projects we're adding -->
<project path="kernel/samsung/galaxys4gmtd" name="teamacid/android_kernel_galaxys4gmtd" remote="gh" revision="ics" />
<project path="device/samsung/galaxys4gmtd" name="fbis251/android_device_samsung_galaxys4gmtd" remote="gh" revision="ics" />
</manifest>
<!--
teamacid's AOKP local_manifest.xml
=================================
vi: ts=4:sw=4:et:noai
-->
Also, a line snuck into the device/samsung/galaxys4gmtd code that will cause a compile error. Adding a declaration for the parameter resolved the build problem.
Check your version (git log) as FB incorporated the patch on the 18th. "Patch to fix config_backKillTimeout build issue for AOKP" is the log entry you are looking for.
Code:
diff --git a/overlay/frameworks/base/core/res/res/values/config.xml b/overlay/frameworks/base/core/res/res/values/config.xml
index 9bdf1b1..2cae795 100644
--- a/overlay/frameworks/base/core/res/res/values/config.xml
+++ b/overlay/frameworks/base/core/res/res/values/config.xml
@@ -199,6 +199,7 @@
<!-- Timeout in MS for how long you have to long-press the back key to
kill the foreground app. -->
+ <add-resource type="integer" name="config_backKillTimeout"/>
<integer name="config_backKillTimeout">1500</integer>
<!--Boolean to enable stk functionality on Samsung phones-->
I have a fix for the overlay but I will use your patch instead. I was finally working with aokp again last night and I got a build ready but still need to change a few things.
EDIT
Do you know if your overlay patch will fix the issue and build fine with CM9 instead of just AOKP? I'd like to push this to the main Team Acid repo when I can.
I didn't find any references to backKilltimeout in Team Acid AOKP. From what I could find, it's a CM-ism that isn't (yet) in the AOKP tree Team Acid is using. I didn't delete the line to try to prevent future merge issues. The AOKP overlay is different than the one Team Acid is using for CM9.
EDIT -- Checking a CM9 build with the "hack" in place now. Builds OK.
jeffsf said:
I didn't find any references to backKilltimeout in Team Acid AOKP. From what I could find, it's a CM-ism that isn't (yet) in the AOKP tree Team Acid is using. I didn't delete the line to try to prevent future merge issues. The AOKP overlay is different than the one Team Acid is using for CM9.
EDIT -- Checking a CM9 build with the "hack" in place now. Builds OK.
Click to expand...
Click to collapse
It's good that it builds. I'll try to remember to push it tonight
I saw they were re doing their repos for jellybean..a whole new start of it
Is the repo for AOKP ics branch still broken? Does anyone know when it will be fixed?
fzhh said:
Is the repo for AOKP ics branch still broken? Does anyone know when it will be fixed?
Click to expand...
Click to collapse
I've been able to repo sync using jeff's changes to local_manifest.xml.
Was broken for my attempt yesterday, said that there was no ICS... but might be fine now. And hey, there's a new build of AOKP. Guess I don't need to build AOKP today... maybe tomorrow. Heh.
Edit: Nope, still get:
error: revision ics in AOKP/hardware_libhardware not found
Click to expand...
Click to collapse
Theraze said:
Was broken for my attempt yesterday, said that there was no ICS... but might be fine now. And hey, there's a new build of AOKP. Guess I don't need to build AOKP today... maybe tomorrow. Heh.
Edit: Nope, still get:
Click to expand...
Click to collapse
The repository exists though... Are you sure you made the right changes in local_manifest.xml?
https://github.com/AOKP/hardware_libhardware
hadware_libhardware is pooched right now (2012/09/23 morning) as it only has jb and master branches. Likely an AOKP issue that Team Acid can't resolve.
FBis251 said:
The repository exists though... Are you sure you made the right changes in local_manifest.xml?
https://github.com/AOKP/hardware_libhardware
Click to expand...
Click to collapse
Same error I've gotten since the first time jeff said to fix it in the github issues thread.
Most recently, I copied and pasted the local_manifest above fully to replace mine.
But as he said... apparently they removed the ics version and are currently only offering jb and master. Joy. Wonder if master is ics, or if they just screwed it up.
jeffsf said:
hadware_libhardware is pooched right now (2012/09/23 morning) as it only has jb and master branches. Likely an AOKP issue that Team Acid can't resolve.
Click to expand...
Click to collapse
We can always try pushing the ics branch to our personal githubs and temporarily editing the local_manifest to reflect this.
As Jeff mentioned in his original post "That is something neither Team Acid nor you can resolve if you don't already have a copy of frameworks/base and prebuilt."
I don't have a copy of framework/base and prebuilt of the ics branch. I tried the Jeff's local_manifest.xml but the sync will fail at the end complaining to framework/base.
fzhh said:
As Jeff mentioned in his original post "That is something neither Team Acid nor you can resolve if you don't already have a copy of frameworks/base and prebuilt."
I don't have a copy of "framework/base and prebuilt".
Click to expand...
Click to collapse
I've uploaded my local repository of hardware/libhardware into my github profile:
https://github.com/fbis251/hardware_libhardware
You can use this by changing the line in jeff's local manifest from:
Code:
<project path="hardware/libhardware" name="AOKP/hardware_libhardware" remote="gh" revision="ics" />
to
Code:
<project path="hardware/libhardware" name="fbis251/hardware_libhardware" remote="gh" revision="ics" />
Try a repo sync after that and I think it'll all work fine.
Little farther, but the new error is 211/314:
error: revision ics in AOKP/hardware_msm7k not found
Click to expand...
Click to collapse
Wild guess here, but qcom/media will probably have the same error, since those are the 3 repos that get replaced together...
I'll try to upload those repos with the ICS branch when I'm not on my school's wifi. They seem to not like letting us ssh over their wifi. :/
Okay I got the changes made:
https://github.com/teamacid/teamacid.github.com/commit/1afa77a372a9aeec9b1c90daa6bb3224f51e9325
Someone test it out by grabbing the local manifest file:
http://teamacid.github.com/manifests/sgh-t959v/AOKP/local_manifest.xml
I still got the following error:
Fetching projects: 100% (314/314), done.
Checking out files: 100% (19168/19168), done. files: 3% (635/19168)
Checking out files: 100% (4743/4743), done.
Checking out files: 100% (9386/9386), done.out files: 17% (1628/9386)
Checking out files: 100% (3156/3156), done. out files: 31% (991/3156)
Checking out files: 100% (24618/24618), done.
Syncing work tree: 61% (192/314) error: revision ics in AOKP/frameworks_base not found
Looks like it's working happily now. Thanks!
fzhh, that means you're using the original version, without ANY of the fixes mentioned in this post (since that error is the one fixed in post 1) or the update by FBis251 ~8 hours ago. Run acidify init aokp again, to download the updated local_manifest. Or edit it yourself...
Theraze said:
Looks like it's working happily now. Thanks!
fzhh, that means you're using the original version, without ANY of the fixes mentioned in this post (since that error is the one fixed in post 1) or the update by FBis251 ~8 hours ago. Run acidify init aokp again, to download the updated local_manifest. Or edit it yourself...
Click to expand...
Click to collapse
Actually an acidify sync should take care of him (NOT repo sync, since repo sync doesn't grab the updated local_manifest.xml)
Update 2014-01-15
Well, the wait has an end! Official nightlies are out! That means I'm off the hook for building!
I'd like to thank everybody who participated by flashing, and posting in this thread. I really had a great time building CM11 for this device! Obviously, the CM team deserves the credit, they were the ones who gave us this awesome ROM!
Official CM11 nightlies can be downloaded here:
N9005
http://download.cyanogenmod.org/?device=hltexx
To flash the 2014-01-15 nightly on the N9005, you must first remove a device check for hltexx in the update script. You can do this by opening up the .zip, editing the updater-script located under /META-INF/com/google/android/, and removing the assert(...) line at the top.
Other Versions:
http://download.cyanogenmod.org/?device=hltetmo (t-mobile)
http://download.cyanogenmod.org/?device=hltespr (sprint)
http://download.cyanogenmod.org/?device=hltevzw (verizon)
Happy Flashing!!
Last Build: 2014-01-13:
The File:
http://d-h.st/J92
md5: a4bddcec13c97db0ec484f40efccc9d0
mirror: https://mega.co.nz/#!V9xzUBgZ!QGPoHBqWxKcDOuMGwpSVcTjZ2VsxsJw9EXO7tLOthWE
Disclaimer:
You flash at your own risk! I take no responsibility for your device!
Warning/Compatibility:
I have tested this on my N9005 only. I removed the assert line in the update script so it can be flashed directly w/o editing.
Changes:
Check review.cyanogenmod.org for more information.
2014-01-13:
- Anything merged by 6:30PM CET
2014-01-12:
- Anything merged by 5:00PM CET
- Battery drain issues seem to be resolved. Will give it a few days before taking it off the list.
2014-01-11:
- Anything merged by 8:30AM CET
2014-01-09:
- Anything merged by 7:00PM CET
2014-01-08:
- Anything merged by 6:30PM CET
2014-01-07:
- Anything merged by 6:30AM CET
2014-01-05:
- Stylus gestures now supported (via settings -> language & input)
- Stylus hovering icon can now be enabled (via settings -> language & input)
2014-01-03:
- http://review.cyanogenmod.org/#/c/56805/
- Updated the two others (56727 and 56730) which are not yet merged to latest patch sets.
- Touch screen issue is fixed (no more touches registered when screen is off).
- Hopefully battery drain is fixed too.
2014-01-02:
http://review.cyanogenmod.org/#/c/56727/
http://review.cyanogenmod.org/#/c/56728/
http://review.cyanogenmod.org/#/c/56730/
Confirmed Working:
- Sound
- Camera (picture & video)
- Calls/SMS
- Data 2g/3g/4g/wifi
- External SD
- GPS
- BT
- NFC
- USB OTG
- IR
- MHL
- ART
- Proximity sensor
- Light sensor
- Humidity sensor
- Thermometer
- Barometer
Known Issues:
- Touches are registered while in-call even when the screen is off
- Mic does not work in hands-free mode
- Battery drain (probably fixed)
- Compass not functioning in some apps
Installation:
1. Download .zip to external SD.
2. Flash via recovery. (I use chenglu cwm)
- In theory you can dirty flash these updates, I usually do the wipes though.
- Coming from TW you must wipe.
- If you're having issues others are not, wipe!
Gapps:
I personally use an aroma installer found here. You can select which ones you want to install. Alternatively you can find packages at cyanogenmod.org.
Enjoy!
Previous Versions:
2014-01-12: file md5: c2186c357f9c503bd8cfa941834bebfa
2014-01-11: file md5: 88395918a155ff80fe94b5c732bf950a
2014-01-09: file md5: e35b69fbcd5c2711a8595ea078152d5f
2014-01-08: file md5: adc7183daf010285e1f3b3623fe4a62b
2014-01-07: file md5: 45919a2e84e6d6afa69a820ea5449cd1
2014-01-05: file md5: ace79a7843e80f304ef5e23c71d7786f
2014-01-03: file md5: 6a2bbec972bc03623cf907c3aedbac21
2014-01-02: file md5: 9b1140bb1242e62ce78af2165d1c199e
2014-01-01: file md5: 346487b8e9f6e1fdc3b005a604f58c0e
2013-12-31: file md5: db9d51d087f032527371575958d5fad2
2013-12-29: file md5: 1e0c8e160703dabb2fb6b475af26ea55
2013-12-29: file md5: ce5cb1c86077ab1fb9074b7f278eb5c0
2013-12-28: file md5: 3511e57d57b91109329932365501f686
-----------------------------------------------------------------
Original post, 2013-12-31:
Update 2013-12-31:
Just uploaded a new build!
Noticeably, calling now works (both making/receiving)! No word on bt calling, that has yet to be confirmed.
So now it's time to list things that are *not* working rather than things that are working!
NFC --> Could anyone make a statement on that?
The File:
http://d-h.st/Qq4
md5: db9d51d087f032527371575958d5fad2
Enjoy it guys!
A big thank you to the CM team for working out all the major bugs within a few days really, and of course everyone who has contributed by commiting patches, testing, discussing, etc!
I'm not sure I'll do more builds today, as I have a few errands to run before the new years celebration! A celebration it will be indeed with CM on our notes!
-----------------------------------------------------------------
Original post, 2013-12-29 #2:
Update 2013-12-29 #2:
Just uploaded a new build! I have to go out for a few hrs, but wanted to share it quickly.
- External SD is now working
- Audio seems to be working better now (it's not near-muted this time.)
I haven't tested other things though.
The File:
http://d-h.st/ShX
md5: 1e0c8e160703dabb2fb6b475af26ea55
-----------------------------------------------------------------
Original post, 2013-12-29 #1:
Update 2013-12-29:
Just uploaded a new build! It's running better than the first one. Noticeably, the following things have changed:
- Camera works now (FC before)
- Gallery works (FC before)
- Data (3g/4g) works
- Audio works (speakers and headphones, but very quiet.)
- Calls are not working. You can call the phone, but it wont ring on the receiving side.
- External SD is not mounting. (This issue has been reported by the tmo guys already)
The File:
http://d-h.st/QaT
md5: ce5cb1c86077ab1fb9074b7f278eb5c0
Disclaimer:
You flash at your own risk! I take no responsibility for your device!
-----------------------------------------------------------------
Original post, 2013-12-28:
Good news!
I got it built, and it boots to launcher (confirmed on my n9005)! I'm only sharing this for the many flash happy out there waiting to see what cm11 feels like. The build is not a daily driver.
Sources
This is based on the official cm repos:
Code:
<manifest>
<project name="CyanogenMod/android_device_samsung_hltexx" path="device/samsung/hltexx" remote="github" />
<project name="CyanogenMod/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" />
<project name="CyanogenMod/android_device_samsung_msm8960-common" path="device/samsung/msm8960-common" remote="github" />
<project name="CyanogenMod/android_device_samsung_hlte-common" path="device/samsung/hlte-common" remote="github" />
<project name="CyanogenMod/android_kernel_samsung_hlte" path="kernel/samsung/hlte" remote="github" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" revision="cm-11.0" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-11.0" />
</manifest>
Issues:
- Camera FC
- Gallery FC
- No Data / GSM
- Probably alot more
- Model no shows up as n9000 (I flashed on n9005)
Installation:
1. Download the zip
2. Wipe and flash via recovery, (I used chenglu cwm)
The first two boots took forever (10 minutes?) now it boots relatively quickly.
Disclaimer:
You flash at your own risk! I take no responsibility for your device!
The File:
http://d-h.st/JUs
md5: 3511e57d57b91109329932365501f686
The Future
I'm on leave for a couple of days, so if testers want to attach logcats ill take a look at what i can fix.
I guess I'll sync and build daily for the next couple of days, or until a more experienced developer comes along and builds CM11
Great work, It's nice to see I would test, however im having to use my phone as a connection point..so with no data connection it could mean im stuck until I get to another connection
Goodluck and look forward to seeing more from you
SM-N9000? You have the N9005 right?
Did you apply the patch noobnl posted on the tmo thread?
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
CalcProgrammer1 said:
SM-N9000? You have the N9005 right?
Did you apply the patch noobnl posted on the tmo thread?
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
Yes, I have the N9005. I was breakfasting and brunching hltexx. Is hltexx not the 9005?
Did not see that patch, thanks for that! I'll apply it and rebuild tomorrow. Its 2AM now, I'm done for today.
PS: camera likes to hog CPU time on this build. Can kill it via terminal emu or delete the apk from system/app.
LTE working just spiffy here. I didn't need to patch or pull any files. Added muppets repo and it built smoothly.
sturmavik said:
LTE working just spiffy here. I didn't need to patch or pull any files. Added muppets repo and it built smoothly.
Click to expand...
Click to collapse
Very nice! You got the right model number too Can you post your roomservice.xml?
That patch you speak of has been merged:
http://review.cyanogenmod.org/#/c/56103/
How are camera and audio doing in your build? Were you brunching cm_hltexx-eng ? I'm gonna try that now
ponglenis said:
Very nice! You got the right model number too Can you post your roomservice.xml?
Click to expand...
Click to collapse
I just followed the instructions and copied the roomservice.xml from http://forum.xda-developers.com/showthread.php?t=2485033
ponglenis said:
How are camera and audio doing in your build? Were you brunching cm_hltexx-eng ? I'm gonna try that now
Click to expand...
Click to collapse
Yeah. Brunched cm_hltexx-eng. Had to patch updater_script as explained in the thread in order to flash my zip. Audio worked but was pretty quiet. Camera was borked in a big way. I actually nandroided back to TW because in my excitement I forgot to offload my gallery pictures and backup my sms.
But damn that was a wonderful few minutes of CM glory!
Does external sdcard work in your build? It doesn't detect properly on hltetmo and it looks like it's an issue with the hlte common repo that affects all variants.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
sturmavik said:
Yeah. Brunched cm_hltexx-eng. Had to patch updater_script as explained in the thread in order to flash my zip. Audio worked but was pretty quiet. Camera was borked in a big way. I actually nandroided back to TW because in my excitement I forgot to offload my gallery pictures and backup my sms.
Click to expand...
Click to collapse
Good, i have the same repos (except hltexx instead of hltetmo). I'm building atm, synced at around 09:15 CET. Let's see how it goes
sturmavik said:
But damn that was a wonderful few minutes of CM glory!
Click to expand...
Click to collapse
Oh yes, it's very snappy! Need to get a daily driver asap!
CalcProgrammer1 said:
Does external sdcard work in your build? It doesn't detect properly on hltetmo and it looks like it's an issue with the hlte common repo that affects all variants.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
Can confirm its not working on yesterdays build. Will report back if anything is fixed in the new build!
Psss.
Nice to see any progress.
G00D JOB.
I cant wait for a stable release.
I need the DATA & GALLERY & CAMERA and all other working ..
But it's great news - I had a Xiaomi MI2A and NOTE I and i changed to NOTE III , cant wait for 4.4.2 or CM from any kind.
Managed to get it up and running on my n9005, although it thinks its a n9000. Camera and gallery seem to be working OK, still no external storage and unable to hang up from calls....
https://plus.google.com/105753056745777397846/posts/ihc4BcfKq4z
Sent from my SM-N9000 using XDA Premium 4 mobile app
choppiii said:
Managed to get it up and running on my n9005, although it thinks its a n9000. Camera and gallery seem to be working OK, still no external storage and unable to hang up from calls....
https://plus.google.com/105753056745777397846/posts/ihc4BcfKq4z
Sent from my SM-N9000 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Oh boy, thats more good news! At this pace we'll have a daily driver before 2014!
My build showed up as N9000 too. But my build.prop was a mess. I was brunching hltexx. Now trying cm_hltexx-eng. I'ts almost done.
Anything special you did while building? I'm guessing you're using the same repos as posted here, or?
ponglenis said:
Oh boy, thats more good news! At this pace we'll have a daily driver before 2014!
My build showed up as N9000 too. But my build.prop was a mess. I was brunching hltexx. Now trying cm_hltexx-eng. I'ts almost done.
Anything special you did while building? I'm guessing you're using the same repos as posted here, or?
Click to expand...
Click to collapse
Yeah I brunched hltexx to then couldn't get it to flash so I had to change the update script from hltexx to htle in the .zip
Sent from my SM-N9000 using XDA Premium 4 mobile app
---------- Post added at 08:06 PM ---------- Previous post was at 07:59 PM ----------
Issues aside how nice does it feel to have CyanogenMod running on our phones.... Its going to kill me going back to crap wiz tomorrow when I have to go to work... ?
Sent from my SM-N9000 using XDA Premium 4 mobile app
Well the build from this morning is no good. Stuck on Samsung logo on boot.
Going to clean, sync and try again!
Just finished another build but couldn't get it to flash, I get a status 7 error, this package is for "htlexx" device; this is a "htle" which is the same as before so without changing the update script which I'm not going to do now as I have to be up for work 5 hours it won't flash....
And yes I'm using the same repos posted here to answer your question from earlier...
My first build sat on the Samsung logo for what felt like few minutes before it booted so give it time if it happens again.
Sent from my GT-N7100 using XDA Premium 4 mobile app
ponglenis said:
Good news!
I got it built, and it boots to launcher (confirmed on my n9005)! I'm only sharing this for the many flash happy out there waiting to see what cm11 feels like. The build is not a daily driver.
Sources
This is based on the official cm repos:
Code:
<manifest>
<project name="CyanogenMod/android_device_samsung_hltexx" path="device/samsung/hltexx" remote="github" />
<project name="CyanogenMod/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" />
<project name="CyanogenMod/android_device_samsung_msm8960-common" path="device/samsung/msm8960-common" remote="github" />
<project name="CyanogenMod/android_device_samsung_hlte-common" path="device/samsung/hlte-common" remote="github" />
<project name="CyanogenMod/android_kernel_samsung_hlte" path="kernel/samsung/hlte" remote="github" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" revision="cm-11.0" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-11.0" />
</manifest>
Issues:
- Camera FC
- Gallery FC
- No Data / GSM
- Probably alot more
- Model no shows up as n9000 (I flashed on n9005)
Installation:
1. Download the zip
2. Wipe and flash via recovery, (I used chenglu cwm)
The first two boots took forever (10 minutes?) now it boots relatively quickly.
Disclaimer:
You flash at your own risk! I take no responsibility for your device!
The File:
http://d-h.st/JUs
md5: 3511e57d57b91109329932365501f686
The Future
I'm on leave for a couple of days, so if testers want to attach logcats ill take a look at what i can fix.
I guess I'll sync and build daily for the next couple of days, or until a more experienced developer comes along and builds CM11
Click to expand...
Click to collapse
I think you have either patched something wrong or used some wrong source, because if you have a look in carrier settings, it gives CDMA options in the settings.
wilfredlams said:
I think you have either patched something wrong or used some wrong source, because if you have a look in carrier settings, it gives CDMA options in the settings.
Click to expand...
Click to collapse
Something was borked. Did not patch anything myself, not sure what it was. Uploading a new build now, it's running better. Camera, data (3G/4G) and sound (can't testify on in call sound yet) are working now, but its experiencing a similar issue others have reported regarding hanging up a call.
ponglenis said:
Something was borked. Did not patch anything myself, not sure what it was. Uploading a new build now, it's running better. Camera, data (3G/4G) and sound (can't testify on in call sound yet) are working now, but its experiencing a similar issue others have reported regarding hanging up a call.
Click to expand...
Click to collapse
That's cool, I will test it again when you provide the link.
wilfredlams said:
That's cool, I will test it again when you provide the link.
Click to expand...
Click to collapse
Thanks! Thats perfect! Feel free to attach logcats of bugs in action. A link to the new build can be found in the first post now! I'll be updating that when i upload new builds.
I saw a few more merges on http://review.cyanogenmod.org/ for our device, I'm starting a new build now! Hoping for sd card fixes
as mentioned here: (Android turn On/Off WiFi HotSpot programmatically) (http://stackoverflow.com/questions/6394599/android-turn-on-off-wifi-hotspot-programmatically) a comment say,the Reflection api is not working in Lollipop.
I want to know is there a way to do this in Lollipop
hlabbad said:
as mentioned here: (Android turn On/Off WiFi HotSpot programmatically) (http://stackoverflow.com/questions/6394599/android-turn-on-off-wifi-hotspot-programmatically) a comment say,the Reflection api is not working in Lollipop.
I want to know is there a way to do this in Lollipop
Click to expand...
Click to collapse
I am currently working on this and I think you need to use the WifiStateMachine class. But haven't fully verified yet.
Sent from my SM-G900P using XDA Free mobile app
Thanks
miked63017 said:
I am currently working on this and I think you need to use the WifiStateMachine class. But haven't fully verified yet.
Sent from my SM-G900P using XDA Free mobile app
Click to expand...
Click to collapse
thank you, i will try doing it and see if it worked.
and yes
hlabbad said:
thank you, i will try doing it and see if it worked.
Click to expand...
Click to collapse
by the way i you finished your project please let me know
have a nice day
The normal reflection API works
The regular reflection calls mentioned on stackoverflow works on lolipop, just make sure to have all the correct permissions. The ones I have used are:
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.ACCESS_WIFI_STATE" />
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
<uses-permission android:name="android.permission.CHANGE_WIFI_STATE" />
<uses-permission android:name="android.permission.CHANGE_NETWORK_STATE" />
Thanks @Kye2000 and @NextDroid for the help in building this rom.
I'm not on the level of actually developing roms yet, so although I can provide updated builds, I'm not going to be able to do anything about bugs myself.
Things working: Pretty much everything, including the wide angle camera
Things not working:
IR Blaster
Notable bugs:
enabling adb debugging can cause the phone to reboot.
Installation:
Wipe data/cache/system and flash
Follow instructions here to get NFC working this shouldn't be needed anymore
Just for reference: flash this if you want to disable nfc and the wakelock
Downloads:
h830 (January 16): https://mega.nz/#!jm4z1AgI!FzYyClHyWe2f3gD9g2qKk9zhjhwvSR3q2Pkdgq0TFq8
md5: https://termbin.com/w9au
h850 (January 17): https://mega.nz/#!KihVACIS!M3kSyoYAUCLvozrg0gXW5cVmSDIr_I53yP5ONq3GUpA
md5: https://termbin.com/49tl
h830 (November 14): https://mega.nz/#!3rIh1SBR!t6W28dHdpGvWbUTFRN4lU33uAzZEw3eCPyM2B5CZYpU
md5: http://termbin.com/yenw
h850 (November 14): https://mega.nz/#!y7IjCKoJ!J8eWDGs6sknjrIDsupkiJz_w-HnVRQKiyNygk9CupM0
md5: http://termbin.com/fsn0
Trees:
Code:
<project name="TheMuppets/proprietary_vendor_lge" path="vendor/lge" remote="github" revision="lineage-15.1"/>
<project name="LineageOS/android_device_qcom_common" path="device/qcom/common" remote="github" revision="lineage-15.1" />
<project name="Jolt151/android_device_lge_h830" path="device/lge/h830" remote="github" revision="lineage-15.1"/>
<project name="Jolt151/android_kernel_lge_msm8996" path="kernel/lge/msm8996" remote="github" revision="lineage-15.1"/>
<project name="Jolt151/android_device_lge_msm8996-common" path="device/lge/msm8996-common" remote="github" revision="lineage-15.1" />
<project name="Jolt151/android_device_lge_g5-common" path="device/lge/g5-common" remote="github" revision="lineage-15.1"/>
<project name="LineageOS/android_device_lge_common" path="device/lge/common" remote="github" revision="lineage-15.1" />
<project name="Jolt151/android_device_lge_h850" path="device/lge/h850" remote="github" revision="lineage-15.1" />
XDA:DevDB Information
H830 H850 Resurrection Remix 6.0.0 Unofficial, ROM for the LG G5
Contributors
Jolt420, @Rashed97, Lineage and RR teams
ROM OS Version: 8.x Oreo
Based On: LineageOS
Version Information
Status: Testing
Created 2018-05-18
Last Updated 2018-06-17
??Thanks buddies,Great, hope to be updated over the long term
Flashed it yesterday, everything running great since then.
doesnt flash on my h830 says unsupported model then list supported models (which i have)
Cannot fastcharge?
aikons said:
Cannot fastcharge?
Click to expand...
Click to collapse
I can
I seem to have a bug or turned on a setting I not sure how to undo. When I have my screen turned off the ambient display works (which is great) but when I flip the phone over so that it thinks the screen is facing downward or in my pocket, it turns off the ambient display. When I try to turn on the screen again either by double tapping or pressing the power button, it can take up to a minute for the screen to reactivate.
Another issue (though it may be just my headset), when pressing on the play/pause button of the bluetooth headphones, the phone doesn't respond to it.
But otherwise, the phone seems to work quite well. Super happy that we finally got this new version.
What gapps do I flash? I can install my own versions of google apps. Does GPS work?
jordan5100 said:
doesnt flash on my h830 says unsupported model then list supported models (which i have)
Click to expand...
Click to collapse
I had this problem originally. Install latest TWRP.
MyLGg5H830 said:
What gapps do I flash? I can install my own versions of google apps. Does GPS work?
Click to expand...
Click to collapse
Arm64 8.1, and the option of your choice. I used stock.
JuSkoch said:
Another issue (though it may be just my headset), when pressing on the play/pause button of the bluetooth headphones, the phone doesn't respond to it.
Click to expand...
Click to collapse
Bluetooth controls work normally for me.
H850 build is up!
Jolt420 said:
H850 build is up!
Click to expand...
Click to collapse
thx I will later flash the build
H850 the build is running very smooth iam suprised and the batery life is great too. At the moment i dont' see any bugs. Thx for the build :good:
For H830 everything runs super smooth too, but I did find a few bugs. Weather icon on lock screen won't show, volume panel never goes away despite custom time out selection, volume panel options shows on 2 different menus, long pressing wifi quick setting breaks the quick panel, rotation lock notification won't follow status bar color changes (a few more I can't remember right now) but I'm pretty sure this aren't G5 specific and are more RR 6.0 general bugs.
View attachment 4509915
tavocabe said:
For H830 everything runs super smooth too, but I did find a few bugs. Weather icon on lock screen won't show, volume panel never goes away despite custom time out selection, volume panel options shows on 2 different menus, long pressing wifi quick setting breaks the quick panel, rotation lock notification won't follow status bar color changes (a few more I can't remember right now) but I'm pretty sure this aren't G5 specific and are more RR 6.0 general bugs.
Click to expand...
Click to collapse
did you mean condition icon pack ?
H850 phone restarts when connected to PC
There is the bluethoot iussue?
Inviato dal mio LG-H850 utilizzando Tapatalk
Hello!
Today I tried to use the RF Signal blaster that I know worked in other roms, but for some reason it doesn't work on this ROM.
I haven't tried on any other Oreo ROM.
Could someone look into why? And perhaps a fix?
It could also just be my device.
Any help would be greatly appreciated
Amer28 said:
Hello!
Today I tried to use the RF Signal blaster that I know worked in other roms, but for some reason it doesn't work on this ROM.
I haven't tried on any other Oreo ROM.
Could someone look into why? And perhaps a fix?
It could also just be my device.
Any help would be greatly appreciated
Click to expand...
Click to collapse
It doesn't work on any oreo rom.
Is anyone else experiencing idle battery drain?