Related
This is the development thread of CyanogenMod 9.
Currently there is no ROM available, but I'm working hard to get you one
Please do not ask for ETA's and I will not tolerate posts like "when will be ready 100%, when will be stable and etc". Also, if anyone disrespects the thread, not counting if they are disrespecting devs or normal users, you will be reported! You have been warned.
For questions etc, please go to Discussion-thread...
After spending a lot of time to research and trying to solve things I'm gonna stop working on this for some time untill some more resources are available ...
Special thanks to:
Andy572
lupohirp
Currently working:
- default Audio
- GSM
- WiFi
- Touchscreen
TODOs
- fix sensors and sensor service
- fix bluetooth / dbus
- fix camera
- fix video
- fix audio and add fmVolume
- fix fm radio
- fix wired headset function
- fix bluetooth headset function
- fix usb (in vold service and kernel)
- fix general bugs as posted on CAF and CyanogenMod
for later use
* for later use
So ICS cyanogen sources are finally all up?
Excellent news! Awaiting for this
Awesome!!! Can't wait! Thanks arjen
Sent from my LG-P509 using xda premium
Using nightlies here
Simply Awesome if u do it..all d best to U..Hope u support this like Mik did..
I'z doesing that too! well,to be honest,I'm working on CAF ICS sources right here right now
Your PC specs? I can build ics in 40 mins with 6gb ram and an i7
Specs of the machine I'm currently working on are lower Guess buildingtime is about 90-110 minutes.
It's still busy on the build, had to fix a few things so far.
Will see how far it goes and what more needs to be done. For now it's been going for 60 minutes...
How big are the sources?
cause i'm getting them and i want to know if i can go to sleep till they are down
Andy just said ICS for our phones it's impossible, so don't get your ups high.
No, that's not what Andy said, for now it's impossible to have hardwareacceleration,
CM9 will still run on our phones. It will only support 2D for now.
_Arjen_ said:
No, that's not what Andy said, for now it's impossible to have hardwareacceleration,
CM9 will still run on our phones. It will only support 2D for now.
Click to expand...
Click to collapse
hey guys have you seen mu hw3d fix in phoenix thread??? hw3d they call adreno 200 lib correctly and i can go into th gui....problem is hwcomposer.so libraries that when called from launcher they go in bootloop and crash phone!! howewer i'm trying a bug bump....merging right now AOSP sources with cyanogenmod!!we need only a good hwcomposer!
Hope it will work eventually...
Build did not complete last night due to a power faillure
Will look at it again when Real Life Work is done
_Arjen_ said:
No, that's not what Andy said, for now it's impossible to have hardwareacceleration,
CM9 will still run on our phones. It will only support 2D for now.
Click to expand...
Click to collapse
that's really good news. I think 3d does not matter much for those of us who don't play many games.
great news well its always been great with p500 as we get almost every port and great supoort from dev.
best of luck for project..
server3249 said:
that's really good news. I think 3d does not matter much for those of us who don't play many games.
Click to expand...
Click to collapse
this is some wrong, please read here @all:
http://forum.xda-developers.com/showpost.php?p=19998704&postcount=476
Ok,
got CM9 compiled succesfully, wil test booting later today (or perhaps tomorrow)
Am really busy on webshops at the moment.
_Arjen_ said:
Ok,
got CM9 compiled succesfully, wil test booting later today (or perhaps tomorrow)
Am really busy on webshops at the moment.
Click to expand...
Click to collapse
Hope you get it in the first shot or atleast easily in a few tries
Sent from my LG-P500 using xda premium
Here's a bit of info you may want on this project for how we do things differently:
CLICK HERE to find out more about the new team working on this project since our TeamEOS merger.
No features you don't need which slow the device down, or put your data at risk of being stolen. If you want to give it away, it should be your decision.
A fast and clean install with no UX decisions made for you. You make the ROM whatever you would like.
A team constantly exploring totally new feature sets and optimizations geared toward you, the user
We utilize a plethora of optimizations in a build system unlike any other:
Each build has a toolchain built for your device at the time of build. No more generic toolchain android builds.
Consistently updated upstream toolchain module source with our custom backports, fixes, and optimizations applied in a patch at build time.
Fully built utilizing Link Time Optimization (another custom ROM first). Feel free to google this one a bit to get an idea of the performance gain.
Many repositories have code fixes, cleanups, and many minor optimizations which are too generous to even speak of here.
Optimizations are toggled on and off based on device for the best experience we can acheive for your device without sacrificing any stability
Many Qcom optimizations and AOSP master (upstream) optimizations and fixes using device specifications to determine usage.
Fully built utilizing strict aliasing and isognu++11 mode.
Full "-O3" build. To those who don't know, this is the highest "optimization level" available in gcc that sets many other flags.
Important Links:
Download Nightlies - We have a very in depth review system, so these should be considered stable.
Download Weeklies - These are built once a week on Monday.
Download GApps
Download SuperSU installer
Kernel Source
Interactive and Rolling Changelog
Bug Tracker
Instructions:
In the same recovery session, flash the following:
Flash rom
Flash GApps
Flash Superuser zip
Reboot
Thank you for choosing codefireXperiment,
Yippee! First AOSP build with fully functional IR Blaster! I use the HTC implementation so any IR control app must use the HTC IR api. I tested with this app.
http://forum.xda-developers.com/showthread.php?t=2271113
Blaster mode and Learn mode are fully functional and stable. This is the first non-Nexus device I've done AOSP on so bear with me for a bit. The build is rock solid stable and I dare any build to try and out-benchmark me ;D
one more for good measure
This is truly a wonderful suprise!!
This is truly a wonderful suprise!!
Welcome bigrush!
This sounds cool! Thanks for the hard work. Im gonna give this a shot tomorrow.
gunna take this for a spin. sounds pretty solid.
or so i thought.
AAAARG...
keeps spittin out "Warning: no file_contextsassert failed.....Followed by various prop errors about the phones model"
anyone got any idea whats goin on?
Are the APN for ATT in this ROM or do I have to put them in myself
Sent from my HTC One using Tapatalk 2
Does cfx have the same janky animation and sluggishness of other AOSP roms for the One when compared against a Sense or GE ROM?
If anyone could fix aosp/optimize for device specific hw on non-nexus devices its you.
Sieze said:
gunna take this for a spin. sounds pretty solid.
or so i thought.
AAAARG...
keeps spittin out "Warning: no file_contextsassert failed.....Followed by various prop errors about the phones model"
anyone got any idea whats goin on?
Click to expand...
Click to collapse
I'm getting this same error too. Anybody know what's up yet? Probably something simple lol
Are you guys flashing with cw or twrp? Don't worry about the file context warning. I may have to disable device assert in installer script.
bigrushdog said:
Are you guys flashing with cw or twrp? Don't worry about the file context warning. I may have to disable device assert in installer script.
Click to expand...
Click to collapse
im using CW touch 6.0.3.3
running a backup atm but once finished il flash TWRP and see if it works.
Ok. So it fails to flash on cw then?
bigrushdog said:
Ok. So it fails to flash on cw then?
Click to expand...
Click to collapse
yup. it flashed with out a hitch on TWRP...
Sieze said:
yup. it flashed with out a hitch on TWRP...
Click to expand...
Click to collapse
Ya we compile the project with twrp recovery. I'll confer with my associates about tweaking or killing device assert in release tools. Also, I gotta drop a global device build too. First aosp build with IR Blaster and this board gets hardly any traffic! I personally run the build on my m7tmo so any derp gets my attention. There's little minor issues here and there but nothing major. Bluetooth OBEX is derped project wide but should be fixed soon.
bigrushdog said:
Ya we compile the project with twrp recovery. I'll confer with my associates about tweaking or killing device assert in release tools. Also, I gotta drop a global device build too. First aosp build with IR Blaster and this board gets hardly any traffic! I personally run the build on my m7tmo so any derp gets my attention. There's little minor issues here and there but nothing major. Bluetooth OBEX is derped project wide but should be fixed soon.
Click to expand...
Click to collapse
well initial response to laying my finger and moving it on the screen. amazing. i didnt think id feel or tell much a difference in response. but holy S#!7 so smooth and stuff happens when its supposed to aka as soon as i touch the icon its open...
(ノ^_^)ノ also the boot animation is pretty frickin sweet.
also the benchmark has me drooling.
Quadrant Standard: 6749
also im really frickin liking this ROM
Hahaha don't lie! The boot anim sucks ass man! Ya all this ui jitter talk I hear, I'm just not getting all that with our build. If the build sucked I wouldn't run it. And I sure as hell wouldn't publish it. Thanks for the kind words. More win in the pipeline.
bigrushdog said:
Hahaha don't lie! The boot anim sucks ass man! Ya all this ui jitter talk I hear, I'm just not getting all that with our build. If the build sucked I wouldn't run it. And I sure as hell wouldn't publish it. Thanks for the kind words. More win in the pipeline.
Click to expand...
Click to collapse
well hey credits due where its earned right? but yea im still crappin my pants at how there is absolutely no lag at my finger tip.
Hands down the best android experience ive ever had. i can trully feel the power of my device in my hand in all its glory.
Grab that IR app and program your TV man. Dude dropped source for the app so maybe I'll do some IR toggles or something
Sieze said:
yup. it flashed with out a hitch on TWRP...
Click to expand...
Click to collapse
I will also try with twrp tomorrow morning. I personally don't prefer one over the other so if twrp is what works then twrp it is!
mikexmayhem said:
I will also try with twrp tomorrow morning. I personally don't prefer one over the other so if twrp is what works then twrp it is!
Click to expand...
Click to collapse
Flashed with twrp. Still gave error but said successful. After reboot everything looks just fine. Great ROM!
So with the Sony binaries and Marshmallow sources released, I figured it was worth trying a build.
I don't have my Z3C on me so no idea how well it'll work (entirely untested, I just know the build finished without errors) but here you go. Roasted Marshmallow, hot off the build server.
EDIT: Modem and sound both appear to be broken so no sound, poor battery life, poor performance and no cell connection.
Lol at the down sides.
Thanks for building anyway.
Bug?
Sent from my D5803 using Tapatalk
softroid said:
Bug?
Sent from my D5803 using Tapatalk
Click to expand...
Click to collapse
Read the op
Gairtial said:
So with the Sony binaries and Marshmallow sources released, I figured it was worth trying a build.
I don't have my Z3C on me so no idea how well it'll work (entirely untested, I just know the build finished without errors) but here you go. Roasted Marshmallow, hot off the build server.
EDIT: Modem and sound both appear to be broken so no sound, poor battery life, poor performance and no cell connection.
Click to expand...
Click to collapse
******possibly ignore, thought I was on Z5C thread*******
Hi @Gairtial
Great work!!
I have been trying to get Android M to compile for the past 24 hours with no luck.
Did you just follow -exactly- the "How to build AOSP Marshmallow for unlocked Xperia devices" instructions on Sony developer world or did you use patches etc that are not mentioned there?
I diverted from the instructions slightly by only adding Sony, suzuran, kitakami and all the kernel links to the .repo/local_manifests/sony.xml as well as only adding qcom../../../ and build,kernel,kitakami, suzuran & system to /Vendor, as I only plan to build for the Z5C.
That wouldn’t be the cause for my errors do you think?
Thanks in advance!
Regards
joeisgood99.
Thread closed
Rule 5
http://forum.xda-developers.com/z3-compact/orig-development/aosp-6-0-1-marshmallow-build-t3225542
Plus this is not original development work.
compared to say the grand x max+? also which is most stable rom besides stock for lo3? thanks for replys
also to root i have unlock it?
Yes
I've had a lot of good phones. Original Note and LG G2 among the best. I still use my Mate 2 as a daily driver. Totally love it. It will be a sad day when it stops working.
Off the top of my head (which may be really outdated), spec-wise and price-wise, I think the Mate 2 is better than any other of its competitors. Again, I haven't been paying much attention lately, so I might be out of the loop quite badly. But for a nearly 4,000 mAh battery and, thanks to some amazing people on this forum, quite a few custom ROMs, I have absolutely no complaints. I'm not replacing this anytime soon. My previous phone was used for either 3 or 4 years.
Just be glad you weren't here from October 2014 to June 2015.
Lol true. Got my own cm ROM made. And working on compiling omni ROM. Shm has several ROMs for it. And cm has L and MM as well. Way better device with stock ROM replaced.
usps says my phone will come monday, YAY!
Moody66 said:
Lol true. Got my own cm ROM made. And working on compiling omni ROM. Shm has several ROMs for it. And cm has L and MM as well. Way better device with stock ROM replaced.
Click to expand...
Click to collapse
I've actually been using the stock ROM for the past month or so, maybe longer. Actually not that bad, I like EMUI. However, I am missing some features of custom ROMs, like swiping notifications on the lockscreen getting rid of them instead of opening them, and being able to change the DPI without everything breaking.
Also, Xposed apparently doesn't work on B322? I haven't tried it myself, but that does suck if true. I used several modules back on B128.
Edit: Does anyone know if there's a way to get the Huawei camera app on CyanogenMod? I think I'm gonna switch back, but the stock camera is garbage, and Google Camera has a weird preview issue in portrait (image is squashed, but turns out fine after it's captured).
Sent from my MT2L03 using Tapatalk
Just hope something doesn't so wrong. I have one rebooting from Bluetooth being turned on and they won't replace it.
am i supposed to update the phone or anything before unlocking?
You need to be on B322
And if it is CC or wind. Unlock the carrier lock before flashing CM etc
Moody66 said:
You need to be on B322
And if it is CC or wind. Unlock the carrier lock before flashing CM etc
Click to expand...
Click to collapse
i got it now im on b322 and i have the recovery installed now im rom shopping..
Gratz. Several to choose from. Welcome aboard.
Moody66 said:
Gratz. Several to choose from. Welcome aboard.
Click to expand...
Click to collapse
someone mentioned candy 6 rom? but i dont see it in the dev sections below
Its in general section.
leo5111 said:
someone mentioned candy 6 rom? but i dont see it in the dev sections below
Click to expand...
Click to collapse
https://www.androidfilehost.com/?w=files&flid=48310
Candy 6 and CM13 are both excellent!
kimtyson said:
Candy 6 and CM13 are both excellent!
Click to expand...
Click to collapse
Indeed! Only thing to note with Candy Six is that live wallpapers seem to be broken at the moment, and Clock consistently crashes every time I try to open it. That may or may not have something to do with the Layers theme I installed though.
Alucai Vivorvel said:
Indeed! Only thing to note with Candy Six is that live wallpapers seem to be broken at the moment, and Clock consistently crashes every time I try to open it. That may or may not have something to do with the Layers theme I installed though.
Click to expand...
Click to collapse
No crashes for me at all. I don't use live wallpapers. Drains battery.
kimtyson said:
No crashes for me at all. I don't use live wallpapers. Drains battery.
Click to expand...
Click to collapse
well i have allways been into the live wallpapers
Konverged Kernel for LG V20 [H918]
Kernel to help turn the LG V20 into a more useful convergence device (PC/mobile functionality). Great for chroot Linux installs.
Features:
SYSV IPC (usable under permissive SELinux)
Misc binfmt
SultanXDA verified boot flag mod (not functioning under suhide)
ALSA Sequencer for MIDI
Added @savoca's KCAL MDSS color calibration module
Overclock frequencies have been added from flar's elementalX OnePlus 3 kernel
NTFS R/W, HFS+, UDF/ISO, CIFS and NFS file system support
Realtek USB WiFi and memory card reader drivers enabled.
USB printer driver support
Charger current boost override using 500, 900 or 1500mAh for allowing phone to charge when using generic USB 3.0 Type-C docks with OTG and DisplayPort. Use under root shell to activate. Example: 'echo 900 > /sys/module/qpnp_smbcharger/parameters/force_current'.
Source is forked from jcadduono's kernel tree.
Flash in TWRP:
Konverged v0.3 for LG V20 H918
[Note: This is kernel is compiled for the LG V20 H918 (US T-Mobile). I'm not responsible for any damage done by flashing this kernel on your device, whether the intended model (h918) or not. Flash at your own risk!]
XDA:DevDB Information
Konverged, Kernel for the LG V20
Contributors
sollapse
Source Code: https://github.com/sollapse/android_kernel_lge_msm8996/tree/konverged-7.0/
Kernel Special Features:
Version Information
Status: Testing
Created 2016-12-01
Last Updated 2016-12-22
Im just going to put this here and call it 1st!
sollapse said:
Charger current boost to 1500mAh for allowing the phone to charge when using generic USB 3.0 Type-C docks with OTG and DisplayPort. Use 'echo 1 > /sys/module/qpnp_smbcharger/parameters/force_highcurrent' under root shell to activate.
Click to expand...
Click to collapse
First off, thank you for working on and sharing this Kernel.
Second, I quoted only the part that has grabbed my concern, has this been thoroughly tested?
DarkestSpawn said:
First off, thank you for working on and sharing this Kernel.
Second, I quoted only the part that has grabbed my concern, has this been thoroughly tested?
Click to expand...
Click to collapse
Well the only device I have tested extensively using this method was on my Oneplus One. I used a similar method to allow the phone to accept the full charge while in OTG. That was in September of last year and OTG was used fairly often by me until a couple weeks ago. Not a thorough, engineering based method for testing yet the phone worked fine for me. They are some safe guards I'll add to the hack to make sure a powered accessory (dock) is plugged in first. I however settled on using 1500mAh at 5V which is the same rate as a standard charger for what I've researched so far. I could probably drop it to 900 or 500mAh even.
For the LG V20, I'm using a Mokin Type-C dock with charging/OTG and HDMI by the way.
what variant lg v20 is this for?
elliwigy said:
what variant lg v20 is this for?
Click to expand...
Click to collapse
Sorry for the delay. This is H918 T-Mobile. I will update the title and post. I've added some CPU overclock tables and KCAL to my branch as well but have not got around to compiling it. The charger code has also been tweaked to allow selecting the charge rate to 500, 900 or 1500mAh. I'll try to release the update tonight or tomorrow.
sollapse said:
Sorry for the delay. This is H918 T-Mobile. I will update the title and post. I've added some CPU overclock tables and KCAL to my branch as well but have not got around to compiling it. The charger code has also been tweaked to allow selecting the charge rate to 500, 900 or 1500mAh. I'll try to release the update tonight or tomorrow.
Click to expand...
Click to collapse
all good.. i have a vs995 converted to a us996 unlocked variant lol
elliwigy said:
all good.. i have a vs995 converted to a us996 unlocked variant lol
Click to expand...
Click to collapse
I have the same thing elliwigy, I'm going to give this a shot as I'm having a pretty significant problem with my kernel crashing right now. I'll update if I get this up and running.
:::EDIT:::
Flashed, appears to be working. I had to go back and do step3.bat and boot2.img flash afterwards though.
Will update if it crashes in deep sleep state which is what the stock kernel did after flashing US996 stock deODEX rom.
:::EDIT2:::
Still getting Kernel Crashes. However could have been due to a process error during root and bootloader unlock.
Lonewolf17a said:
I have the same thing elliwigy, I'm going to give this a shot as I'm having a pretty significant problem with my kernel crashing right now. I'll update if I get this up and running.
:::EDIT:::
Flashed, appears to be working. I had to go back and do step3.bat and boot2.img flash afterwards though.
Will update if it crashes in deep sleep state which is what the stock kernel did after flashing US996 stock deODEX rom.
Click to expand...
Click to collapse
my post was days ago lol ive been on konverged for ~2 days already working just fine except reboot takes a bit longer as need to sleep both screens for it to start working (the display)
elliwigy said:
my post was days ago lol ive been on konverged for ~2 days already working just fine except reboot takes a bit longer as need to sleep both screens for it to start working (the display)
Click to expand...
Click to collapse
I can see that.
But for anyone else lurking in the thread, it helps that someone confirms that it works.
However I would note that my phone is still extraordinarily laggy, I still get vibration and red triangle message each boot.
Any thoughts bud?
Lonewolf17a said:
I can see that.
But for anyone else lurking in the thread, it helps that someone confirms that it works.
However I would note that my phone is still extraordinarily laggy, I still get vibration and red triangle message each boot.
Any thoughts bud?
Click to expand...
Click to collapse
my phone is perfectly fine no lag at all lol. the vibration for me stopped even before using the kernel..also, the red triangle message on each boot will never go away
elliwigy said:
my phone is perfectly fine no lag at all lol. the vibration for me stopped even before using the kernel..also, the red triangle message on each boot will never go away
Click to expand...
Click to collapse
Thanks bud. All I'm left with then is process error in the rooting and unlocking steps.
Dang... Gotta wait till I can flash back to stock and retry from the beginning. These kernel crashes are happening more frequently. Can't find a stock ROM for VZW.
Quick side question for anyone lurking.
I don't think Sprint roms will work for VS995 but we did get the US996 to work for VZW users. Any other ROMS compatible? Or is that trail and error also?
I appreciate your help elliwigy. And to all our awesome devs and contributers.
Just saying thanks. This seems to have fixed many of the issues with my LS997 rooted on DirtySanta.
Lonewolf17a said:
Thanks bud. All I'm left with then is process error in the rooting and unlocking steps.
Dang... Gotta wait till I can flash back to stock and retry from the beginning. These kernel crashes are happening more frequently. Can't find a stock ROM for VZW.
Quick side question for anyone lurking.
I don't think Sprint roms will work for VS995 but we did get the US996 to work for VZW users. Any other ROMS compatible? Or is that trail and error also?
I appreciate your help elliwigy. And to all our awesome devs and contributers.
Click to expand...
Click to collapse
you can use the us996 since it seems you wont be able to keep vzw firmware if it wont boot... you can redo the process but use us996 rom.. also, i dobt think we should clutter this thread with dirty santa talk.. use that thread
esqueue said:
Just saying thanks. This seems to have fixed many of the issues with my LS997 rooted on DirtySanta.
Click to expand...
Click to collapse
Yep. Me too. In fact, I would almost dare to say that my phone is running even better than it did before I rooted! There's absolutely zero lag now, everything is working (except for WiFi calling I think), it boots fast, battery life is excellent, etc.
Very very happy right now!
Sent from my LG-LS997 using Tapatalk
Guys was there a revision on this kernel? I see 0.3 now in the download and I think I flashed the original. Using VS995
Changelog?
Also, the size of 0.3 is like 1/2 of the original one? Is this correct
mvincent said:
Guys was there a revision on this kernel? I see 0.3 now in the download and I think I flashed the original. Using VS995
Changelog?
Also, the size of 0.3 is like 1/2 of the original one? Is this correct
Click to expand...
Click to collapse
Yeah, I've updated the kernel with some additions and changes. Should have made an announcement post. Main changes are KCAL color control, CPU overclock frequencies (1728/2265, for little and big cores respectively) and finer control over charging current for docks. The zip is correct, yet it's still compiled for the H918 but if it works heyyy!
Do I need to flash the new one or how does this work?
Latest went smoothly on my h910
Sent from my Pixel using Tapatalk
Does this kernel have f2fs support?
Also, THANK YOU! It fixed any issues with the Sprint rooted phones I had for the most part Still no FM radio support, though.