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)
Related
First off not sure if this is in the proper location, so if it is wrong, mods I apologize. Basically I am looking for a bit of help with building from several different sources to make my own custom version of a ROM. I want to (more or less) build Carbon from source with PA Prefs and possibly some additions from CM10 and AOKP. I can find plenty of info on how to build AOSP from source for a Nexus, but very little on cherry-picking commits and such from git. Here is what I have so far:
-Build Environment ready (Ubuntu 13.04)
-Complete JB 4.2.2 AOSP source
-Scott's Infuse device tree (I think)
-Carbon's Infuse source files
Let me say that I have NO intentions of releasing this as a download, I only want it for my personal use. The main things i need help with is making sure i have the proper and complete device tree, things I need to replace, and how to cherry-pick and add the PA and other commits. I'm new to building (this will be my first actual attempt), but I'm a quick study and follow directions well. Any and all help is GREATLY appreciated. Once I learn this, I may be able to build up a new ROM for everyone to try out
check out scott's beanstalk thread...post #3..i think
qkster said:
check out scott's beanstalk thread...post #3..i think
Click to expand...
Click to collapse
thanks, there was some very helpful information there. turns out i didnt have all the device files lol. now to find out how to merge code and try to build this thing.
InsaneDDay69 said:
thanks, there was some very helpful information there. turns out i didnt have all the device files lol. now to find out how to merge code and try to build this thing.
Click to expand...
Click to collapse
If you ever have any questions or errors you can't seem to get past shoot me a pm. I was in your shoes once and know how confusing everything can be at first. :thumbup:
Sent from my SGH-I997 using xda premium
FauxAffliction said:
If you ever have any questions or errors you can't seem to get past shoot me a pm. I was in your shoes once and know how confusing everything can be at first. :thumbup:
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
I'll keep that in mind. Think I'm finally figuring out how to pick, though I need to wait on my carbon source sync to try it.
Sent from my Carbon-ized Infuse
I want to see how this turns out.I'm still learning too man
Sent from my SGH-I997 using Tapatalk 2
this is what i'm getting. all the files are in the proper places, so i have no clue what i'm missing. carbon git sync bombed, so i'm trying a CM10 test run and then will work on adding tweaks and stuff. tried breakfast command and got the same result too.
[email protected]:~/cm10$ . build/envsetup.sh && brunch "infuse4g"
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/armv7-a/vendorsetup.sh
including device/generic/mips/vendorsetup.sh
including device/generic/x86/vendorsetup.sh
including device/ti/panda/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including sdk/bash_completion/adb.bash
including vendor/cm/vendorsetup.sh
build/core/config.mk:160: *** TARGET_ARCH not defined by board config: device/samsung/infuse4g/BoardConfig.mk. Stop.
Device infuse4g not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Repository for infuse4g not found in the CyanogenMod Github repository list. If this is in error, you may need to manually add it to your local_manifests/roomservice.xml.
build/core/config.mk:160: *** TARGET_ARCH not defined by board config: device/samsung/infuse4g/BoardConfig.mk. Stop.
** Don't have a product spec for: 'cm_infuse4g'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
Click to expand...
Click to collapse
still getting the same error. it appears to think i have placed the files in the wrong location. i assumed the device files (not kernel or proprietary vendor files) went into the device directory of the source. i have mine placed like this
cm10 (source code folder name)-->
device-->
samsung-->
infuse4g
when i run the lunch command i get a list of different devices to build, but none are the infuse. i could build for the I9000 and port it over, but i don't want to do it that way. this was synced from scott's cm git, and i added the following in my manifest.xml to make sure i got it right.
<!-- Add infuse4g device tree -->
<project name="scotthartbti/android_device_samsung_infuse4g" path="device/samsung_infuse4g" remote="github" revision="jellybean" />
<!-- Add Samsung Kernel -->
<project name="scotthartbti/cm_samsung_kernel_dempsey" path="kernel/samsung_kernel_dempsey" remote="github" revision="jellybean" />
<!-- Add Samsung Proprietary Vendor Files -->
<project name="scotthartbti/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="jellybean" />
Click to expand...
Click to collapse
ANY help at this point would be great. i want to finally learn how to give back to the community that has made my android owning a true joy.
Anyone have any ideas?
My Infuse is Stalking Beans
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
tell me who is trying to build cm 11 for trebon i m thinking tomorrow to start downloading source code for trebon and tell me all about errors when compyling what version of linux are you using etc... i m trying to get some info
yjosipy said:
tell me who is trying to build cm 11 for trebon i m thinking tomorrow to start downloading source code for trebon and tell me all about errors when compyling what version of linux are you using etc... i m trying to get some info
Click to expand...
Click to collapse
i'm trying
im using ubuntu 13.10 with kernel 3.11
using any other kernels gives me errors that are solved by reinstalling grub but the other kernels can't be loaded as the grub is not updated
i complied just once and it broke because of no space
now im trying a new 250 gb hdd and if i manage to finnaly boot ubuntu now i will try the damn compilation
i have the source code already downloaded so i will be lucky (on a pentium dual core 2.20, 3 gb ram ddr2 it took 270 minutes to repo sync)
p.s. of course ubuntu 64 bit but as i have ddr2 ram its slow as hell
ShadowsDie said:
i'm trying
im using ubuntu 13.10 with kernel 3.11
using any other kernels gives me errors that are solved by reinstalling grub but the other kernels can't be loaded as the grub is not updated
i complied just once and it broke because of no space
now im trying a new 250 gb hdd and if i manage to finnaly boot ubuntu now i will try the damn compilation
i have the source code already downloaded so i will be lucky (on a pentium dual core 2.20, 3 gb ram ddr2 it took 270 minutes to repo sync)
p.s. of course ubuntu 64 bit but as i have ddr2 ram its slow as hell
Click to expand...
Click to collapse
f*ck i have amd athlon p320 dual core 2.10gHz and 2gb of ddr3 ram (laptop) i hope i can compile it wirh that can you tell me is it req to have 64bit os
yjosipy said:
f*ck i have amd athlon p320 dual core 2.10gHz and 2gb of ddr3 ram (laptop) i hope i can compile it wirh that can you tell me is it req to have 64bit os
Click to expand...
Click to collapse
well.....
64bit ubuntu is a must if you want to build cm and normally 64bit is for more than 2gb ram (4 gb recommendedm 3 minimum)
but... you can try
it will run very slow to you
ShadowsDie said:
well.....
64bit ubuntu is a must if you want to build cm and normally 64bit is for more than 2gb ram (4 gb recommendedm 3 minimum)
but... you can try
it will run very slow to you
Click to expand...
Click to collapse
i had 4 gb and one card died anyway i will try it:cyclops:
yjosipy said:
i had 4 gb and one card died anyway i will try it:cyclops:
Click to expand...
Click to collapse
the problem with 64 bit OS is that you sacrifice ram for a better cpu performance (almost 10%)
and sync repo takes a lot of cpu
but you need ram to sacrifice
ShadowsDie said:
the problem with 64 bit OS is that you sacrifice ram for a better cpu performance (almost 10%)
and sync repo takes a lot of cpu
but you need ram to sacrifice
Click to expand...
Click to collapse
and how much of source code do i need to download i mean how many gigabytes
yjosipy said:
and how much of source code do i need to download i mean how many gigabytes
Click to expand...
Click to collapse
i don't remember exactly but its something between 12-20 gb
anyway the download speed is slow but then is not only the download, is the proper position of the files
---------- Post added at 09:21 PM ---------- Previous post was at 09:19 PM ----------
ShadowsDie said:
i don't remember exactly but its something between 12-20 gb
anyway the download speed is slow but then is not only the download, is the proper position of the files
Click to expand...
Click to collapse
if you manage to boot on ubuntu without any error (and im sure you will have errors) i could help you with the steps through skype or something
just saying because my ubuntu updates the kernel and then gives errors then i have to reinstall grub and then i have a nvidia drivers problem
hope you don't have nvidia
ShadowsDie said:
i don't remember exactly but its something between 12-20 gb
anyway the download speed is slow but then is not only the download, is the proper position of the files
---------- Post added at 09:21 PM ---------- Previous post was at 09:19 PM ----------
if you manage to boot on ubuntu without any error (and im sure you will have errors) i could help you with the steps through skype or something
just saying because my ubuntu updates the kernel and then gives errors then i have to reinstall grub and then i have a nvidia drivers problem
hope you don't have nvidia
Click to expand...
Click to collapse
i have one error at startup i think i can solve it easily i m using radeon hd4200 lucky me tomorrow i will install git and all other goodies
Edit:this is mine error kvm:disabled by bios
Edit2:that error hurts no one
yjosipy said:
i have one error at startup i think i can solve it easily i m using radeon hd4200 lucky me tomorrow i will install git and all other goodies
Edit:this is mine error kvm:disabled by bios
Edit2:that error hurts no one
Click to expand...
Click to collapse
did you have any unloaded kernel error?
anyway try do not update the kernel
if you are on 3.11 its ok
p.s.
i will help you with this
at obtaining the proprietary files this should do the trick
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- CM replacements -->
<remove-project name="CyanogenMod/android_frameworks_native" />
<project path="frameworks/native" name="omnirom/android_frameworks_native" revision="android-4.4" />
<!-- Local projects -->
<project path="external/webkit" name="legaCyMod/android_external_webkit" revision="cm-11.0" />
<project path="hardware/atheros/wlan" name="TheWhisp/android_hardware_atheros_wlan" revision="cm-11.0" />
<project path="hardware/qcom/display-legacy" name="TheWhisp/android_hardware_qcom_display-legacy" revision="jellybean-mr2" />
<project path="hardware/qcom/media-legacy" name="Dazzozo/android_hardware_qcom_media-legacy" revision="jellybean-mr2" />
<project path="device/samsung/msm7x27a-common" name="yazidkucrit/android_device_samsung_msm7x27a-common" revision="cm-11.0" />
<project path="device/samsung/trebon" name="yazidkucrit/android_device_samsung_s7500" revision="cm-11" />
<project path="kernel/samsung/msm7x27a-common" name="yazidkucrit/kernel_KeongBalap" revision="master" />
<project path="vendor/samsung" name="yazidkucrit/proprietary_vendor_samsung_msm7x27a" revision="cm-10.2" />
<!-- FM Radio -->
<project path="hardware/qcom/fm" name="legaCyMod/android_hardware_qcom_fm" revision="cm-11.0" />
<project path="packages/apps/FM2" name="legaCyMod/android_packages_apps_FM2" revision="cm-11.0" />
</manifest>
Then: brunch trebon
p.s. 2
the whisp has our cm11 drivers, i'm very happy
ShadowsDie said:
did you have any unloaded kernel error?
anyway try do not update the kernel
if you are on 3.11 its ok
p.s.
i will help you with this
at obtaining the proprietary files this should do the trick
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- CM replacements -->
<remove-project name="CyanogenMod/android_frameworks_native" />
<project path="frameworks/native" name="omnirom/android_frameworks_native" revision="android-4.4" />
<!-- Local projects -->
<project path="external/webkit" name="legaCyMod/android_external_webkit" revision="cm-11.0" />
<project path="hardware/atheros/wlan" name="TheWhisp/android_hardware_atheros_wlan" revision="cm-11.0" />
<project path="hardware/qcom/display-legacy" name="TheWhisp/android_hardware_qcom_display-legacy" revision="jellybean-mr2" />
<project path="hardware/qcom/media-legacy" name="Dazzozo/android_hardware_qcom_media-legacy" revision="jellybean-mr2" />
<project path="device/samsung/msm7x27a-common" name="yazidkucrit/android_device_samsung_msm7x27a-common" revision="cm-11.0" />
<project path="device/samsung/trebon" name="yazidkucrit/android_device_samsung_s7500" revision="cm-11" />
<project path="kernel/samsung/msm7x27a-common" name="yazidkucrit/kernel_KeongBalap" revision="master" />
<project path="vendor/samsung" name="yazidkucrit/proprietary_vendor_samsung_msm7x27a" revision="cm-10.2" />
<!-- FM Radio -->
<project path="hardware/qcom/fm" name="legaCyMod/android_hardware_qcom_fm" revision="cm-11.0" />
<project path="packages/apps/FM2" name="legaCyMod/android_packages_apps_FM2" revision="cm-11.0" />
</manifest>
Then: brunch trebon
p.s. 2
the whisp has our cm11 drivers, i'm very happy
Click to expand...
Click to collapse
tnx for that i think i can handle it
Edit:started to syncing
yjosipy said:
tnx for that i think i can handle it
Edit:started to syncing
Click to expand...
Click to collapse
sry, i came now from my holidays
how is it going? i want to know if i do it as well or you are ok
ShadowsDie said:
sry, i came now from my holidays
how is it going? i want to know if i do it as well or you are ok
Click to expand...
Click to collapse
well the good news is that there is still no errors and i asked help from user named Rox from ace 2 forum (who speaks my language and lives about 70km from my house ) he will help us out but the bad news is that i had to pause syncing so that means i m still downloading
yjosipy said:
well the good news is that there is still no errors and i asked help from user named Rox from ace 2 forum (who speaks my language and lives about 70km from my house ) he will help us out but the bad news is that i had to pause syncing so that means i m still downloading
Click to expand...
Click to collapse
Good job, let me know if something happens, i'll try to help as much as I can
ShadowsDie said:
Good job, let me know if something happens, i'll try to help as much as I can
Click to expand...
Click to collapse
nopeee its cheking files :victory: now tell me how to add thewisps repos to manifests
yjosipy said:
nopeee its cheking files :victory: now tell me how to add thewisps repos to manifests
Click to expand...
Click to collapse
initialize environment
$ . build/envsetup.sh
Then i think you have to get the missing repo by typing "breakfast trebon" but im sure it will not work
Then create a file with the name local_manifest.xml in the local_manifests directory. To see this directory, you have to press Ctrl-H in your file manager.
then make the manifest look like this
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- CM replacements -->
<remove-project name="CyanogenMod/android_frameworks_native" />
<project path="frameworks/native" name="omnirom/android_frameworks_native" revision="android-4.4" />
<!-- Local projects -->
<project path="external/webkit" name="legaCyMod/android_external_webkit" revision="cm-11.0" />
<project path="hardware/atheros/wlan" name="TheWhisp/android_hardware_atheros_wlan" revision="cm-11.0" />
<project path="hardware/qcom/display-legacy" name="TheWhisp/android_hardware_qcom_display-legacy" revision="jellybean-mr2" />
<project path="hardware/qcom/media-legacy" name="Dazzozo/android_hardware_qcom_media-legacy" revision="jellybean-mr2" />
<project path="device/samsung/msm7x27a-common" name="yazidkucrit/android_device_samsung_msm7x27a-common" revision="cm-11.0" />
<project path="device/samsung/trebon" name="yazidkucrit/android_device_samsung_s7500" revision="cm-11" />
<project path="kernel/samsung/msm7x27a-common" name="yazidkucrit/kernel_KeongBalap" revision="master" />
<project path="vendor/samsung" name="yazidkucrit/proprietary_vendor_samsung_msm7x27a" revision="cm-10.2" />
<!-- FM Radio -->
<project path="hardware/qcom/fm" name="legaCyMod/android_hardware_qcom_fm" revision="cm-11.0" />
<project path="packages/apps/FM2" name="legaCyMod/android_packages_apps_FM2" revision="cm-11.0" />
</manifest>
save the file then repo sync again
hope it helps
Edit: can't we talk via any messenger? because i often check xda every hour and we cant communicate that fast
hopefully we will finish this soon...
ShadowsDie said:
initialize environment
$ . build/envsetup.sh
Then i think you have to get the missing repo by typing "breakfast trebon" but im sure it will not work
Then create a file with the name local_manifest.xml in the local_manifests directory. To see this directory, you have to press Ctrl-H in your file manager.
then make the manifest look like this
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- CM replacements -->
<remove-project name="CyanogenMod/android_frameworks_native" />
<project path="frameworks/native" name="omnirom/android_frameworks_native" revision="android-4.4" />
<!-- Local projects -->
<project path="external/webkit" name="legaCyMod/android_external_webkit" revision="cm-11.0" />
<project path="hardware/atheros/wlan" name="TheWhisp/android_hardware_atheros_wlan" revision="cm-11.0" />
<project path="hardware/qcom/display-legacy" name="TheWhisp/android_hardware_qcom_display-legacy" revision="jellybean-mr2" />
<project path="hardware/qcom/media-legacy" name="Dazzozo/android_hardware_qcom_media-legacy" revision="jellybean-mr2" />
<project path="device/samsung/msm7x27a-common" name="yazidkucrit/android_device_samsung_msm7x27a-common" revision="cm-11.0" />
<project path="device/samsung/trebon" name="yazidkucrit/android_device_samsung_s7500" revision="cm-11" />
<project path="kernel/samsung/msm7x27a-common" name="yazidkucrit/kernel_KeongBalap" revision="master" />
<project path="vendor/samsung" name="yazidkucrit/proprietary_vendor_samsung_msm7x27a" revision="cm-10.2" />
<!-- FM Radio -->
<project path="hardware/qcom/fm" name="legaCyMod/android_hardware_qcom_fm" revision="cm-11.0" />
<project path="packages/apps/FM2" name="legaCyMod/android_packages_apps_FM2" revision="cm-11.0" />
</manifest>
save the file then repo sync again
hope it helps
Edit: can't we talk via any messenger? because i often check xda every hour and we cant communicate that fast
hopefully we will finish this soon...
Click to expand...
Click to collapse
yes why not my fb name is joosipp
i invited someone with that name thell me if its you
ShadowsDie said:
i invited someone with that name thell me if its you
Click to expand...
Click to collapse
nope try this www.facebook.com/joosipp
yjosipy said:
tell me who is trying to build cm 11 for trebon i m thinking tomorrow to start downloading source code for trebon and tell me all about errors when compyling what version of linux are you using etc... i m trying to get some info
Click to expand...
Click to collapse
I have successfullly ported cm11 to our device!!
But I can't upload It and share It with you due to bad internet connection (upload speed~12 Kb/s).... :crying: :crying: :crying: :crying:
This thread is for developers only and I will not be posting ROMs here.
I am posting this here in the hope that someone else has time, skills and motivation to help work on this. If so, please PM me and/or send me pull requests.
I am basing this off of the HLTE kernel because it is being very well maintained and has many huge advances from CAF.
Links:
Kernel: https://github.com/crpalmer/android_kernel_samsung_mondrianwifi
Device: https://github.com/crpalmer/android_device_samsung_mondrianwifi
Vendor: https://github.com/crpalmer/android_vendor_samsung_mondrianwifi
I am also using these dependent repositories:
Code:
<project path="device/samsung/msm8960-common"
name="CyanogenMod/android_device_samsung_msm8960-common"
remote="github" revision="cm-11.0"
/>
<project path="device/samsung/qcom-common"
name="CyanogenMod/android_device_samsung_qcom-common"
remote="github" revision="cm-11.0"
/>
<project path="hardware/qcom/display-caf-new"
name="CyanogenMod/android_hardware_qcom_display-caf-new"
groups="caf"
/>
<project path="hardware/qcom/media-caf-new"
name="CyanogenMod/android_hardware_qcom_media-caf-new"
groups="caf"
/>
<remove-project name="CyanogenMod/android_hardware_invensense" />
This was the status but since I got further faster than I was expecting, there is now a build thread which has the status there.
crpalmer said:
Current status:
* clockworkmod recovery: seems to be working fine
* CM 11 boots and the base seems to be generally not horrendously broken
Hardware status:
* display: backlight doesn't work, therefore it also won't turn back on once it turns off
* usb: adb works, nothing else tested
* WiFi: doesn't work
* everything else: haven't even looked at it, and therefore probably doesn't work
Click to expand...
Click to collapse
The source has been published by Samsung.
opensource.samsung.com
Sent from my SM-T320 using XDA Premium HD app
crpalmer said:
Current status:
* clockworkmod recovery: seems to be working fine
Click to expand...
Click to collapse
I'm interested. Do you have a version of CWM recovery that you have compiled that you can share or steps you used to build?
Thanks!
blulite said:
I'm interested. Do you have a version of CWM recovery that you have compiled that you can share or steps you used to build?
Thanks!
Click to expand...
Click to collapse
The cwmr that I am using is the one that gets built by running a full CM build using the repos I pointed toward. If you can build CM then you should be able to build a recovery that works on at least my tablet. However, I am definitely not sharing a build because of the fact that it is based on the hlte kernel and could be causing serious problems.
I'm going to try to merge the official source into the hlte kernel and see if I can get that working. If so, it will be a fair bit less risky (although it is still risky because random people like me are playing with how the hardware gets used including voltages, current, etc.).
If you were trying to build a recovery yourself, yeah, you probably ran into problems because the bootloader requires a boot.img with a device tree and the DT needs to be version 2 format which is quite new.
Updated the kernel link. It is a merge of the KK_NA source released by samsung into the hlte kernel from cyanogenmod. It builds but the display is still borked (the left hand of the screen now turns back on, but the right does not...).
If anyone was working with these repos, please do not use the original hlte fork any longer.
Yesterday CM build server compiled bunch of CM11 ROMs, even dedicated article was posted on CM blog. But there's no build for bacon. Since there are a lot of clever guys on XDA, may I ask you for help? Someone, please, do CM11 snapshot for bacon, "as is" or with newer TP drivers, nothing more. I think it can be very famous build since KitKat is still popular around Android users.
ImmortAlex said:
Yesterday CM build server compiled bunch of CM11 ROMs, even dedicated article was posted on CM blog. But there's no build for bacon. Since there are a lot of clever guys on XDA, may I ask you for help? Someone, please, do CM11 snapshot for bacon, "as is" or with newer TP drivers, nothing more. I think it can be very famous build since KitKat is still popular around Android users.
Click to expand...
Click to collapse
Great idea, but should be in the general section.. Tp drivers definitely..
Sent from my A0001 using XDA Premium 4 mobile app
Thats awesome! I would love 2 see someone give KK some attention!
I tried recently, but there are errors during building
CraZY_BoY^ said:
I tried recently, but there are errors during building
Click to expand...
Click to collapse
To bad...
I've got a day off work tomorrow. If I've got time, I'll do a repo sync and build it for you. Did a build a couple of months back of CM11 so should have most things set up still.
Nickamina said:
I've got a day off work tomorrow. If I've got time, I'll do a repo sync and build it for you. Did a build a couple of months back of CM11 so should have most things set up still.
Click to expand...
Click to collapse
Any news already?
EasyGoingXD said:
Any news already?
Click to expand...
Click to collapse
Sorry mate, I haven't forgotten - I've just been busy. I'll get on it when I can.
Nickamina said:
Sorry mate, I haven't forgotten - I've just been busy. I'll get on it when I can.
Click to expand...
Click to collapse
Get healty first thanks for reply
No luck when I tried this evening, gents. Getting this error. I've got work in the morning so no time to troubleshoot at the moment. Any ideas what the problem is?
Code:
warning: [options] source value 1.5 is obsolete and will be removed in a future release
warning: [options] target value 1.5 is obsolete and will be removed in a future release
warning: [options] To suppress warnings about obsolete options, use -Xlint:-options.
libcore/luni/src/main/java/java/util/EnumMap.java:162: error: incompatible types: Object cannot be converted to E
return type.get(new MapEntry(enumMap.keys[prePosition],
^
where E is a type-variable:
E extends Object declared in class EnumMapIterator
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
3 warnings
make: *** [/home/nicklip/android/system/out/target/common/obj/JAVA_LIBRARIES/core_intermediates/classes-full-debug.jar] Error 41
make: *** Waiting for unfinished jobs....
@CraZY_BoY^ are these the errors you got?
Nickamina said:
No luck when I tried this evening, gents. Getting this error. I've got work in the morning so no time to troubleshoot at the moment. Any ideas what the problem is?
Code:
warning: [options] source value 1.5 is obsolete and will be removed in a future release
warning: [options] target value 1.5 is obsolete and will be removed in a future release
warning: [options] To suppress warnings about obsolete options, use -Xlint:-options.
libcore/luni/src/main/java/java/util/EnumMap.java:162: error: incompatible types: Object cannot be converted to E
return type.get(new MapEntry(enumMap.keys[prePosition],
^
where E is a type-variable:
E extends Object declared in class EnumMapIterator
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
3 warnings
make: *** [/home/nicklip/android/system/out/target/common/obj/JAVA_LIBRARIES/core_intermediates/classes-full-debug.jar] Error 41
make: *** Waiting for unfinished jobs....
@CraZY_BoY^ are these the errors you got?
Click to expand...
Click to collapse
Nope, i dont remember exactly what was it, but not your error.
Maybe it's because of incorrect java version?
Code:
sudo update-alternatives --config java
sudo update-alternatives --config javac
CraZY_BoY^ said:
Nope, i dont remember exactly what was it, but not your error.
Maybe it's because of incorrect java version?
Code:
sudo update-alternatives --config java
sudo update-alternatives --config javac
Click to expand...
Click to collapse
I'm sure it's something java related. Tried a couple of quick java changes already but I'll give your idea a go when I get home. Cheers.
http://forum.xda-developers.com/showpost.php?p=61581110&postcount=570
I am using this build for 3 days now, mostly stable.
thanks to @obtained.
Aka91 said:
http://forum.xda-developers.com/showpost.php?p=61581110&postcount=570
I am using this build for 3 days now, mostly stable.
thanks to @obtained.
Click to expand...
Click to collapse
Ah wonderful! That saves me some effort! What do you mean by mostly stable? It's cm11 so I would have thought it would be rock-solid at this point.
Aka91 said:
http://forum.xda-developers.com/showpost.php?p=61581110&postcount=570
I am using this build for 3 days now, mostly stable.
thanks to @obtained.
Click to expand...
Click to collapse
Yep, we know, but we want to know how to resolve this error(s).
Make sure you are on OpenJDK 1.6:
This guide here goes through how to change versions for all components of Java.
Also your manifests file should look like this (this is what mine looks like for building 0702):
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="TheMuppets/proprietary_vendor_oppo" path="vendor/oppo" remote="github" revision="cm-11.0" />
<project name="TheMuppets/proprietary_vendor_oneplus" path="vendor/oneplus" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_device_oneplus_bacon" path="device/oneplus/bacon" remote="github" />
<project name="CyanogenMod/android_device_oppo_msm8974-common" path="device/oppo/msm8974-common" remote="github" />
<project name="CyanogenMod/android_device_oppo_common" path="device/oppo/common" remote="github" />
<project name="CyanogenMod/android_kernel_oneplus_msm8974" path="kernel/oneplus/msm8974" remote="github" />
<project name="CyanogenMod/android_hardware_qcom_display-caf-new" path="hardware/qcom/display-caf-new" remote="github" />
<project name="CyanogenMod/android_hardware_qcom_media-caf-new" path="hardware/qcom/media-caf-new" remote="github" />
<project name="CyanogenMod/android_frameworks_opt_connectivity" path="frameworks/opt/connectivity" remote="github" />
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" />
</manifest>
Manifests courtesy of @Muurahainen
Anyway, I build 0702 and uploaded it here: https://www.androidfilehost.com/?w=files&flid=33863