Only for HTC One S C2!!
This is a discussion thread, about the progress on 3.4 kernel development for cyanogen mod, and other aosp based roms. There is posibility that testers will be needed...
reserved...
Logcat Error
There is one error in logcat, which appears all the time:
Code:
I/auditd ( 7220): Starting up
E/auditd ( 7220): Failed on audit_set_pid with error: Protocol not supported
I/auditd ( 7220): Exiting
Possible this is causing any kind of problems?
I'm happy to try kernel porting for you guys but for that we will need a hangout group ....
You already have me, I'll write you when I have some spare time, you can also involve Robin he's willing to help
Gesendet von meinem HTC One S mit Tapatalk
It looks like things are moving into the right direction. But I am leaving for London today so I won't be able to test until my return.
Good luck!
Sent from my HTC One S using XDA Free mobile app
qzem said:
It looks like things are moving into the right direction. But I am leaving for London today so I won't be able to test until my return.
Good luck!
Sent from my HTC One S using XDA Free mobile app
Click to expand...
Click to collapse
Nice, have a good time in London then
qzem said:
It looks like things are moving into the right direction. But I am leaving for London today so I won't be able to test until my return.
Good luck!
Sent from my HTC One S using XDA Free mobile app
Click to expand...
Click to collapse
League of Legends Championship Series in Wembley stadium?
I can volunteer as a tester.
Sent from One
Tried porting new framebuffer drivers from CAF. Attached to the bottom of this post are the kernels with the new framebuffer drivers (one for PAC and one for CM11). All I need to know is whether or not it boots. Graphical glitches do not matter.
Also, I don't plan on getting too involved in the development here as I don't own the device.
Spii said:
League of Legends Championship Series in Wembley stadium?
Click to expand...
Click to collapse
No, just sightseeing .
Sent from my HTC One S using XDA Free mobile app
Sultanxda said:
Tried porting new framebuffer drivers from CAF. Attached to the bottom of this post are the kernels with the new framebuffer drivers (one for PAC and one for CM11). All I need to know is whether or not it boots. Graphical glitches do not matter.
Also, I don't plan on getting too involved in the development here as I don't own the device.
Click to expand...
Click to collapse
Hey, first of all thanks for doing this. Your work is highly appreciated! :good:
About the kernel: I've flashed the CM Kernel, first it was bootlooping but I somehow booted it successfully into Safe Mode
And Screenshot is working
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
EDIT: At the 3rd loop it's booting successfully!
Spii said:
Hey, first of all thanks for doing this. Your work is highly appreciated! :good:
About the kernel: I've flashed the CM Kernel, first it was bootlooping but I somehow booted it successfully into Safe Mode
And Screenshot is working
EDIT: At the 3rd loop it's booting successfully!
Click to expand...
Click to collapse
I can't believe it actually booted on my first attempt without the device It probably bootlooped because you're on a very recent build of CM, and I used the ramdisk of a CM build made 3 months ago. New framebuffer drivers means that graphics are overall much smoother and display glitches are gone. They also allow you to use display-caf instead of display-legacy.
Sent from my Nexus 5 using Tapatalk
i would be glad if u add me to hangouts group
Tried to install the CM11 file but failed.
Error is
assert failed: getprop("ro.product.device") == "villec2
E:Error executing updater binary in zip '/sdcard/downlo......
Error flashing zip........
sunnyvijay said:
Tried to install the CM11 file but failed.
Error is
assert failed: getprop("ro.product.device") == "villec2
E:Error executing updater binary in zip '/sdcard/downlo......
Error flashing zip........
Click to expand...
Click to collapse
Yep, but don't worry I will include the updated Kernel in the ROM anyways, just wait for that
Thanks.
However could not wait and googled to fix the updater-script and was successful.
It was bootlooping but after 6th loop the phone was on and working
The Kernel Version in the About reflects 3.4.750Sultan-CAF-msmfb-g08a97af-dirty
Sultanxda said:
I can't believe it actually booted on my first attempt without the device It probably bootlooped because you're on a very recent build of CM, and I used the ramdisk of a CM build made 3 months ago. New framebuffer drivers means that graphics are overall much smoother and display glitches are gone. They also allow you to use display-caf instead of display-legacy.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Is there any progress on kernel? Or you don't have time to work on it?
Sent from my HTC One S using XDA Free mobile app
qzem said:
Is there any progress on kernel? Or you don't have time to work on it?
Sent from my HTC One S using XDA Free mobile app
Click to expand...
Click to collapse
All of the completed source is on my GitHub.
Kernel: https://github.com/sultanxda/android_kernel_htc_liberty-villec2
Device tree: https://github.com/sultanxda/android_device_htc_villec2
Vendor tree: https://github.com/sultanxda/proprietary_vendor_htc
Media-caf: https://github.com/sultanxda/android_hardware_qcom_media-caf
Display-caf: https://github.com/sultanxda/android_hardware_qcom_display-caf
Note that for display-caf and media-caf all you need are these patches:
For display-caf: https://github.com/sultanxda/androi...mmit/d8374d512958a02f05cac8261dc419efedde07c9
For media-caf: https://github.com/sultanxda/androi...mmit/67e47694cb00e70916b97e4308e1d8eef21f192f
Otherwise media-caf and display-caf are exactly the same as the CyanogenMod versions.
Now you guys have hardware vsync and the latest framebuffer drivers, along with the latest display and media HALs
Thanks a lot!! :good:
Syncing and compiling
Related
Hi All,
Here is the AOSP 4.2.2 for our wonderfull Galaxy Royale:
Alpha :
--deleted--
Alpha_2(30-Dec-2012):
--deleted--
4.2.1 Beta(5-Jan-2013):
http://www.mediafire.com/?3ecwnx5jfsy3mc5
4.2.2 V1(1-May-2013)
http://www.mediafire.com/download.php?1zi7cc4q2jjklws
4.2.2 V2(14-May-2013)
http://www.mediafire.com/?om1lbovupmun0qt
Root Fix (Only for 4.2.1 Beta) :
http://www.mediafire.com/download.php?19enpwdyc8szoob
Installation:
Download the zip
Wipe data/factory reset
Wipe cache
Wipe Dalvik cache
Format system
Install zip
For 4.2: Install gapps
http://goo.im/gapps/gapps-jb-20121212-signed.zip
For 4.2.2 Install gapps
http://goo.im/gapps/gapps-jb-20130301-signed.zip
Reboot
Changelog for V2:
- Updated with the new AOSP source(JDQ39E)
- Fixed clock Lockscreen overlap
- Battery Status Fixed
Bugs:
- Video Recording in Stock Camera App
- Menu and Back LED lights are not getting on. But using BLN app u can get the notification light
- Menu button to unlock(For few people it may be a feature)
- All CM10.1 Bugs
- If you want to add anything then report your bugs to general thread
General Thread for discussion and feel of the ROM:
http://forum.xda-developers.com/showthread.php?t=2048371
Source:
https://github.com/karthik050782/AOSP_4.2.2_I9103
Credits:
Adam77root
CM team for RIL
Vikesh (donator and for maintaining General Thread)
saura_tirupathi(donator)
txingu (donator)
And many for the help
Screenshots(Based on 4.2):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Every custom modification to devices have risks. Flash this at your own risk!
If you get errors. Resync the repo. Because yesterday I was going to compile Liquid Smooth and got many errors while sync the repo.
Sent from my Galaxy Nexus using xda app-developers app
Thanks buddy! Will try to resync the repo! Me too faced the same problem with CM10 for many times.
Hope there is no extra steps to follow for AOSP!
Edit: Reached home, deleted the framework folder.. did the repo sync again... now compilation started... let us c...
There is a lot not in pure aosp source that has to be added. Plus , you must modify the android.mk and test runner android.mk in frameworks base to split into two jar files. Framework.jar and framework2.jar, otherwise it will error on the jar size. Pull what needs to be added hardware and external from cm.
Sent from my SGH-I927 using xda premium
Thanks dman! Can you please provide some link? Got error coz of the overlay present in device... for testing I have removed from device folder... after it went fine...
Now, Coz of disk space, it got stopped... compiling again...
Sent from my GT-I9103 using xda app-developers app
You have to add the overlay resources into the base source also...
Sent from my SGH-I927 using xda premium
http://github.com/TheCollective/android_frameworks_base/commits/android-4.2_r1
Look at the commit to split the framework jar
Sent from my SGH-I927 using xda premium
Thanks Dman!
I have compiled it with the source and got the ota zip file.. Now, i will add the framework, hardware, libhardware changes to CM and will re-compile.
Is there any changes need to be done for Kernel. I am using same CM10 kernel and I have the boot.img in OTA zip file.
No need to change the kernel. It's good to go.
Sent from my GT-I9103 with CM10
Thanks Adam!!! I am reading many threads about 4.2.. Hope it will boot after patching framework, hardware, libhardware..
Best of luck! AOSP is pretty hard to fix.. I had a pretty tough time fixing up stuff on my Galaxy SL (ICS).. It first booted with Broken RIL and Touchscreen and frameworks are broken .. Best of luck though!
Thanks Adi, SamsungRil.java is not present in AOSP... I will look into your github, which will helpful for building..
Hope i won't brick my device
karthik050782 said:
Thanks Adi, SamsungRil.java is not present in AOSP... I will look into your github, which will helpful for building..
Hope i won't brick my device
Click to expand...
Click to collapse
No you most likely won't brick.. Look into CM githubs and manually apply the SamsungRIL and other necessary RIL patches,you may need patches for touchscreen also to work if Galaxy R is using Legacy Touchscreen(?) .. First thing.. get it to boot.. then we can work on fixing the other stuff... Can help you out. I got latest AOSP Source synced up and I have some experience of building AOSP.
Sure Adi! Will try today with adding the required one and will disturb in chat
Not got much time!! But tried to boot with the zip file without any patches... It gave symlink error, then discussed with Adi_pat and replaced the META_INF folder from CM10 again got the same symlink error.
Tried to find the log in cache/recover/log and nothing is there only the wiping log is there... last_install doesn't have anything...
So, did the patches(framework, ril and also did some patches by following the crespo thread) and compilation is going on...
karthik050782 said:
Not got much time!! But tried to boot with the zip file without any patches... It gave symlink error, then discussed with Adi_pat and replaced the META_INF folder from CM10 again got the same symlink error.
Tried to find the log in cache/recover/log and nothing is there only the wiping log is there... last_install doesn't have anything...
So, did the patches(framework, ril and also did some patches by following the crespo thread) and compilation is going on...
Click to expand...
Click to collapse
Modify the script a bit, whay symlink errors do you get? Remember many binaries are not compiled by default in AOSP which are there in CM(Look at external/ folder) So obviously some symlinks might fail!
Sent from my GT-I9003 using xda premium
Yeah, i did that... but few binaries are not present in CM also, but not sure why those are present.
Anyway to identify on which line we are getting this error?
karthik050782 said:
Yeah, i did that... but few binaries are not present in CM also, but not sure why those are present.
Anyway to identify on which line we are getting this error?
Click to expand...
Click to collapse
Ok I will compile it myself later today when I get time and will see myself. Will send it to you for testing.
Sent from my GT-I9003 using xda premium
If I get Symlink errors, I turn my phone off ,, enter again recovery and install it again. It always works for me.
Sent from my Galaxy Nexus using xda app-developers app
Sorry for spam you here but can you help with this ERROR in building 4.2?
http://pastebin.com/Tdu9VUg9
CyanogenMod 10.1 Unofficial
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ReadMe:
This is a beta build of cm10.1 with the new htc 3.4 kernel (compliments of intervigilium)
BUGS:
video only works on 480
slight to moderate battery drain getting better with each build.
REQUIRED:
The latest htc jellybean firmware head to this thread to upgrade firmware. Please direct all questions and issues concerning upgrade there.
DOWNLOADS:
STOP DO NOT FLASH UNTIL YOU READ THE ENTIRE OP
cm_10.1_20 June Download
CM_10.1_19 June Download
CM_10.1_18 June Download
CM_10.1_14 June Download
CM_BETA_2 Download
CM_BETA 1 Download
THANKS/CREDIT
HUGE HUGE thanks to Intervigilium for sharing his booting kernel source with us..
Cyanogenmod team
please help me justify all the time spent on these roms to my wife by considering a small donation$droyd$
How to properly run an ruu
in order to run the new 3.4 kernel you will need to install the latest jelly bean firmware.. This is how i did it and the easiest way i know how..Please do not sharp shoot my directions as i am dooing this off sheer memory so it may be a little fuzzy ... If you dont under stand something you can find it with a little google search ... lets get started:
I will not be held responsible for your phone do at your own risk
required items:
A windows computer.( you can not to my knowledge run an ruu with linux)
fastboot installed on your pc ( adb/fastboot)
the 2.35 or similar depending on your provider but you want to stay in the ice cream sandwich version ruu designed for your phone make sure it is the correct one or it will not work and may cause severe damage..(i have no link for this as i will not be the reason you flashed the wrong one sorry your on your own finding it)
htc usb drivers easiest way to install is htc sync (htc sync will automaticly install the drivers you need)
SETTING THINGS UP:
You will need to extract the ruu if it is in zip format(it needs to be a basic exe file(i always just keep it on my desktop for easy access)
boot your phone into boot loader and select fastboot this is where everything will happen.
navigate to where you have your fastboot installed in your terminal on your pc.
ITS TIME TO MAKE IT HAPPEN
using a usb 2.0 cable(3.0 will not work) connect your phone and wait for it to say 'fastboot usb'
Now lets re lock the boot loader type ' fastboot oem relock your phone should reboot
navigate back to boot loader select fastboot again
now while in fastboot usb go to your selected ruu and double click it (this will take some time to load)
follow the on screen instructions to navigate through the ruu..
if you get errors you probably didnt get the right ruu for your device.
Thats it now you will be 100% stock
GETTING THE UPDATE:
boot your phone wait a few minutes and check for ota updates in about phone.
you will likley not get the jellybean update first so be sure you take the couple updates and that you are running jellybean sense before you root again.
YOU ARE DONE
I do not recommend going and flashing the jellybean ruu because if you have problems you can not flash an ruu lower than your current hboot
NOW ROOT YOUR PHONE
I Highly Highly recomend getting kernel tuner and disableing vsync in misc..... all jitter lag freeze gone.... i will disable it in source asap...
No screen tearing and full fps seem great!
please disable vsync its un believable
Downloading now, thx for the great work
Sent from my HTC One S
proxuser said:
Downloading now, thx for the great work
Sent from my HTC One S
Click to expand...
Click to collapse
Disable vsync in kernel tuner..
Sent from my One S using xda premium
Please disregard the android.com camera and mirror ... Forgot to remove em... Won't forget next time..
Sent from my One S using xda premium
I wish I could have One s S4 instead of S3 Looks great
Donated 10$ will donate more later
Great work thank you
Donate guys
I'm so happy you guys have collaborated on this.
It was literally yesterday I posted in the Q&A asking when we might see Linux 3.4 for AOSP. Everyone else I have seen using 3.4 has seen vast improvements compared to older versions.
I will be more than willing to test this everystep of the way, in fact I'm about to flash it right now!
EDIT:
Wiped everything about 5 times, flashed in recovery, rebooted flasheed boot.img in bootloader, rebooted and it was still on splash screen after about 5 minutes?
Dirty flashed and working now
This and a Sense 5 port coming?! Things are moving quite fast now for our loved device. Can't wait to try a stable release.
Awesome rom !!!!
Enviado desde mi One S usando Tapatalk 2
CazeW said:
This and a Sense 5 port coming?! Things are moving quite fast now for our loved device. Can't wait to try a stable release.
Click to expand...
Click to collapse
Something else might just be coming soon...
I am experiencing very regular reboots roughly every 10 minutes.
What voltages is it running stock 1150mV for all frequencies? My phone is very sensitive but still excited to help get this thing going!
usaff22 said:
Something else might just be coming soon...
Click to expand...
Click to collapse
Tell it :$
RichardW1992 said:
I am experiencing very regular reboots roughly every 10 minutes.
What voltages is it running stock 1150mV for all frequencies? My phone is very sensitive but still excited to help get this thing going!
Click to expand...
Click to collapse
Did you get kernel tuner and disable vsync..?
Sent from my One S using xda premium
$droyd$ said:
Did you get kernel tuner and disable vsync..?
Sent from my One S using xda premium
Click to expand...
Click to collapse
Certainly did, and it has successfully disabled. Just getting very frequent reboots. I might try another fresh install but I think its just my phone being extra temper mental.
RichardW1992 said:
Certainly did, and it has successfully disabled. Just getting very frequent reboots. I might try another fresh install but I think its just my phone being extra temper mental.
Click to expand...
Click to collapse
Its the kernel at this point ..its not quite stable yet... Although it is the kernel made by htc for our phone there are a lot of factors here... Try ondemand gov.. Tinker in kernel tuner this is beta so if you find a way to make it more stable please tell... Disable hw overlays and those things in dev options like we used to..
Sent from my One S using xda premium
Once I start building linaro I will post in the second post if any one wants to try custom versions otherwise in each ROM I will only add what's committed to repo to keep it stock for every one...I know that's the way you cm users like it.... All cm all the time lol.
Sent from my One S using xda premium
bigxie has released a fully working ROM here: http://forum.xda-developers.com/showthread.php?t=2341395
-------------------------------------------------
THIS IS COMPLETELY EXPERIMENTAL. FLASH AT YOUR OWN RISK.
After getting a full dump, here are some flashable zips for both the odexed and deodexed versions of the stock image.
Note. It does NOT have a boot.img, you may have to test other images. I have not had time to test that these work, but they are straight out of a Google Edition device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Odexed - Download
Deodexed - Download
/Shen
RESERVED
RESERVED
is it Christmas already?!
gonna try and boot it up
Sent from my HTC One using Tapatalk 4 Beta
I see this comming... dual boot Stock and Sense :laugh:
Installing now. Full wipe with tbalden's kernel. Crossed fingers!
EDIT1: Not installing. Something is wrong with the update-binary.
shishir95 said:
Installing now. Full wipe with tbalden's kernel. Crossed fingers!
EDIT1: Not installing. Something is wrong with the update-binary.
Click to expand...
Click to collapse
what's the error message you get?
Sent from my HTC One using Tapatalk 4 Beta
shishir95 said:
Installing now. Full wipe with tbalden's kernel. Crossed fingers!
EDIT1: Not installing. Something is wrong with the update-binary.
Click to expand...
Click to collapse
Will check once I get home. Can you post the error line?
Omg.....
Sent from my HTC One using Tapatalk 4 Beta
EclipzeRemix said:
what's the error message you get?
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
Code:
E: Error eecuting updater binary in zip '/sdcar...
Error flashing zip '/sdcard/Phone/odexed.zip'
I'm going to try to install again using a known working update-binary (CM10.1). Copying over to phone via sideload currently. Will update
EDIT: OKAY. Boots fine. TWRP gave me a weird "no OS installed, are you sure you want to reboot" thing, but it booted up fine. WiFi doesn't seem to work yet, but data's fine. I swapped out the update-binary in this zip with one from a CM10.1 zip and changed the relevant lines in the updater-script to make sure it installs without error. All it needs is a WiFi fix.
EclipzeRemix said:
gonna try and boot it up
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
Sorry for being a Noob. What is the different between this ROM and other. What is the Advantage of it. Please....Thank you
ongxa said:
Sorry for being a Noob. What is the different between this ROM and other. What is the Advantage of it. Please....Thank you
Click to expand...
Click to collapse
it's vanilla android
Sent from my HTC One using Tapatalk 4 Beta
deepbeech said:
Testing for stability is definitely required.
Click to expand...
Click to collapse
its a system dump, it should be really stable from the start.
Bugs so far:
WiFi doesn't seem to work
Clicking on the mobile data Quick Setting in the notification shade force closes Settings
Installation of ROM is broken out of the box
Its vanilla with sprinkles
Can anyone confirm a required hboot for this? Also side load flash or recovery better?
Sent from my ONE CM10.1
Does the GE version have a different radio?
Sweetness. Will wait for an update / bug fix.
shishir95 said:
Bugs so far:
WiFi doesn't seem to work
Clicking on the mobile data Quick Setting in the notification shade force closes Settings
Installation of ROM is broken out of the box
Click to expand...
Click to collapse
how so? shouldnt it be bug free since he built it with the system dump from the GE?
hello00 said:
how so? shouldnt it be bug free since he built it with the system dump from the GE?
Click to expand...
Click to collapse
WiFi and data are broken because of permission issues
Sent from my HTC One using Tapatalk 4 Beta
hello00 said:
how so? shouldnt it be bug free since he built it with the system dump from the GE?
Click to expand...
Click to collapse
Theoretically, maybe. There are always bugs. Those are the only things I've noticed so far though. Everything else seems to work beautifully, minimal lag, etc.. I'm expecting a new kernel to fix the WiFi, or maybe OP forgot to include a few .lib files, fix permissions, or a myriad of other things. I'll look into it later today, but so far it works well enough for a DD (minus WiFi... )
AOSP/Code Aurora Vanilla Android 4.4.2 for Moto G
This build is based on sources directly from Code Aurora which is AOSP plus all Qualcomm specific enhancements and optimization.
Build instructions can be found here: https://github.com/razrqcom-dev-team/android_local_razrqcom/tree/aosp-caf-8226
Device tree is here https://github.com/dhacker29/android_device_motorola_falcon
This build has been optimized to be a one build for all variants (xt1032, xt1033, xt1034 and cdma as well should work).
I accomplished this through a little magic in the init.mmi.rc to set ro.hw.radio based on the ro.boot.radio value, from there I use init.mmi.radio.sh to set the appropriate build.prop values based on the radio detected to be stock for the device.
Known Issues: Canera does not work
Download: Latest Downloads HERE
Gapps: http://d-h.st/eWW
ClockWork Mod Recovery for 4.4 bootloader: CWM6046-MotoG44.img
TWRP 2.6.3.1 for 4.4 bootloader: TWRP2631_MotoG44.img Touch is fixed for the most part but occasional reset to main screen. I am working with Dees Troy to get a fix.
xt1033 needs the 4.4.2 modem to work with this rom
Recovery flashable 4.4.2 modem: MotoG_4.4.2_modem.zip
If you wish to return to stock via back up and not fastboot here is a flashable 4.3 radio for xt1033
Recovery flashable 4.3 modem for xt1033 MotoG_4.3_xt1033_modem.zip
Remember this is a AOSP stock android build so if you want root you need to flash the Super{User/SU} of your choice.
Also, There is no gapps backup script so they need to be reflashed with each update.
Click to expand...
Click to collapse
Changelog:
1-25-14: Fixed dialer force close
Added custom audio routing
Fixed in call audio
Click to expand...
Click to collapse
Enjoy!
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thank you will try this, this weekend. You're doing great work for the moto G?
Witty witticisms
Hi I just tried flashing this on my xt1032 and CWM hung during the install, I left it for about 10 mins before forcing a reboot.
On another note I would like to say thanks for all the work you are putting into this phone
Sent from my XT1032 using xda app-developers app
That's odd I've not had any error flashing. Which cwm?
Sent from my Moto G using xda app-developers app
Your 6.0.4.6 build, I have also had this problem when trying to flash slimkat and gummy
Sent from my XT1032 using xda app-developers app
Same in here, on the latest CWM 6.0.4.6 from a1pha.
Me too. CWM6.0.4.6
Sent from my XT1032 using XDA Premium 4 mobile app
flashed ok for my on CWM6.0.4.6
I just tried flashing again and it worked. It took almost 9 mins to flash ( I did time it this time lol, but it seemed much longer). It did look like CWM had hung but then without the blue bar going up it came up with install finished.
So be patient people and sorry for the false alarm.
Sent from my Moto G using xda app-developers app
---------- Post added at 02:55 PM ---------- Previous post was at 02:53 PM ----------
debaj said:
Same in here, on the latest CWM 6.0.4.6 from a1pha.
Click to expand...
Click to collapse
Cwm 6.0.4.6 is built by dhacker29 a1pha created the first cwm 6.0.4.5 and his since removed his build and linked dhacker29's build
Sent from my Moto G using xda app-developers app
Thanks the clarification, sometime today I'll try it again.
Kind of laggy, but that's alpha after all
No signal in dual sim, FC in com.android.phone when accessing mobile network. Sim Toolkits FC too.
Logcat radio attached
busquet said:
Kind of laggy, FC in com.android.phone when accessing mobile network
Click to expand...
Click to collapse
Same problem with my xt1032
Sent from my Nexus 7 using xda app-developers app
Could this sources be used to build aosp-based roms?
@dhacker29 can you share what caf branch and manifest you used?
and thanks for all the great roms, hopefully i get my hands on a unreleased rom source so i can contribute too
Build instructions added to OP
Every thing is laggy to you guys.......... I don't know why I waste my time.
Thank you for this! I've been waiting for a pure AOSP build!
dhacker29 said:
Every thing is laggy to you guys.......... I don't know why I waste my time.
Click to expand...
Click to collapse
sorry, man, didn't mean that, just stating some stuff about the rom! I admire your effort in making these builds for us, and it's amazing you are getting them to work in every Moto G version!
I wish I could understand a bit more of building Android and all, I'm really looking forward to this. I'll try to do my best to test and learn how to cooperate with you, guys!
Enviado de meu XT1033 usando Tapatalk
busquet said:
sorry, man, didn't mean that, just stating some stuff about the rom! I admire your effort in making these builds for us, and it's amazing you are getting them to work in every Moto G version!
I wish I could understand a bit more of building Android and all, I'm really looking forward to this. I'll try to do my best to test and learn how to cooperate with you, guys!
Enviado de meu XT1033 usando Tapatalk
Click to expand...
Click to collapse
No worries I guess I am to micro focused on getting things to work I don't use games and audio I am busy compiling lol so I don't notice any lag. I fixed the phone force close and audio should be straight new builds in a few.
New build up fixed the phone fc and in call audio. Still only one sim working on dual sim versions for now.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CM11 for the Nexus Q
"The Nexus Q Lives on"
Features:
HW acceleration support for videos, including in XBMC
LED Support
Download: HERE
Source: HERE
Great work! Which audio output does it use?
Unb0rn said:
Great work! Which audio output does it use?
Click to expand...
Click to collapse
I am only able to test HDMI as I don't have anything else for the other outputs.
Don't know if it's only me, but there are too many bugs for me. Some settings causes FCs(like the one in "Buttons" section), recents menu causes some graphics artifacts, trying to change wallpaper causes FC, StickMount 3.10 damaged filesystem(I am unable neither to mount/unmount anything after reboot, nor deleting it's working folder in /sdcard(even with adb)). Still it was worth trying!
Unb0rn said:
Don't know if it's only me, but there are too many bugs for me. Some settings causes FCs(like the one in "Buttons" section), recents menu causes some graphics artifacts, trying to change wallpaper causes FC, StickMount 3.10 damaged filesystem(I am unable neither to mount/unmount anything after reboot, nor deleting it's working folder in /sdcard(even with adb)). Still it was worth trying!
Click to expand...
Click to collapse
buttons fC because their are no buttons. And use otg helper instead of stickmount.
I'm wanting to try this, but I'm curious what kind of LED functionality does this have?
Sent from my SM-G900T using XDA Premium 4 mobile app
dts924s said:
I'm wanting to try this, but I'm curious what kind of LED functionality does this have?
Sent from my SM-G900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Probably safe to assume that it at most has the same hooks as previous version of cm where you can set a persistent LED color and that's about it.
Sent from my Nexus 5 using Tapatalk
wow so far this is the best and most stable CM ROM I've used for the Nexus Q!
Please please keep the updates coming, we could cherry pick a few mods to get the LED ring more functional and allow connecting a mic etc?
this is amazing, thank you very much!
New build link in OP! Enjoy
Any way to get an amp build for this version ?
what's new in the new build?
THE_KINGDOM said:
what's new in the new build?
Click to expand...
Click to collapse
New stuff
flash messed up
When I tried flashing this rom, I got the Installing update... prompt, then I got the message:
set_metadata_recursive: some changes failed
E:Error in /sdcard/0/Download/cm-11-20140803-UNOFFICIAL-steelhead.zip
(status 7)
Installation aborted.
I saved a backup before I tried flashing, but now I can't even get my Q to boot up normally or to recovery, I only get a black screen and scrolling blue LED light on my Q.
Any ideas what I can do to fix this?
Moose0704 said:
New stuff
Click to expand...
Click to collapse
What new stuff? I don't see any apparent changes. Anything we should be aware of? Why update?
Well done!
This is really well done. Seems very stable to me. @Moose0704, is there any chance you would consider applying to be the device maintainer for steelhead on the official CM project?
dts924s said:
When I tried flashing this rom, I got the Installing update... prompt, then I got the message:
set_metadata_recursive: some changes failed
E:Error in /sdcard/0/Download/cm-11-20140803-UNOFFICIAL-steelhead.zip
(status 7)
Installation aborted.
I saved a backup before I tried flashing, but now I can't even get my Q to boot up normally or to recovery, I only get a black screen and scrolling blue LED light on my Q.
Any ideas what I can do to fix this?
Click to expand...
Click to collapse
I know you solved this, but for anyone else with this issue, be sure you are on an updated recovery.
I used the recovery from this thread: http://forum.xda-developers.com/showpost.php?p=49102621&postcount=1
New build posted in OP, enjoy
Can I cast regularly (as if the Q actually were a chromecast) with this rom or do I have to use xbmc?
Sent from my Nexus 5 using Tapatalk
Volatyle said:
Can I cast regularly (as if the Q actually were a chromecast) with this rom or do I have to use xbmc?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes, with this: http://forum.xda-developers.com/showpost.php?p=55935384&postcount=1
Btw, ROM is working fine. See sometimes a few graphical glitches, mostly in the overview screen.
I was able to install the app and things are kind of working but it appears the Q is having trouble with the actual "playing" of what is casted. Perhaps the issue is I'm on eithernet. I know the ADT-1 can also be spotty with casting when hooked up via eithernet.