Related
This thread is for everyone who compile's Cyanogenmod Kang build's from source and would like to post/share with everyone. If you want your build included in this post just pm me and I will update this post asap.
Warning these are unofficial CM7 build's (with myself cherry-picking comments from CM's Gerrit for testing) which may have unfinished mods and/or broken code that is continually changing, ONLY THOSE WHO KNOW WHAT THEY ARE DOING SHOULD FLASH THEM. Don't file bug reports on the Cyanogenmod issue tracker from any of these build's. Please don't bother cyanogen or #teamdouche as you have been warned these build's are unofficial and come with no support except on this thread. If you have any question's try searching as your question might have been already asked and answered. Note: I, nor is anyone else is/are responsible for any bricks or problems you may encounter.
I no longer have a G2 as I gave it to my mom, but will update this periodically. Sorry for the delay I have been super busy with the move, my new job and fixing this house I am now living in.
All credit goes to cyanogen & #teamdouche, thank them not me as all I do is compile
Items from CM's Gerrit that I cherry-picked:
* Give me time
Last Commit repo synced before building-
* Enable access to Audio Effects Settings
I understand that this build is unofficial and I take no responsibility if you brick your phone- Will be update in about an hour and half as I plan on running it when I get home
Please visit @cmsrc, CM's Gerrit or Nightly Device Changelog for a complete list of changes or commits.
Also those who don't know a Kang is an unofficial nightly that someone builds from CM's github.
I will update this post as often as needed to stay current or change as necessary.
Hey everyone, here are the kangs and cherry picks that i will be providing. I want to thanks plasmadragon007 for allowing me to post here.
Everything in the above post applies to here. We will most likely be making these at a different time of day with possible different commits. I do not own a g2 but i do have a couple of decent guys willing to test each kang before posting. If they are not available, i will let you know that the build has not been tested. I do this because i enjoy it and want to. I hope you enjoy it also.
All credit goes to cyanogen & #teamdouche.
Items from CM's Gerrit that I cherry-picked:
Lockscreen background http://goo.gl/5p5Np
you can find my builds on Euroskank http://goo.gl/U7xx6
Hey Guys,
I figured i would share this.
All credit goes to cyanogenmod team. and cyanogen for being a killer coder
All Builds + recoveries can be found here. I have included a date + md5sum
http://xdafiles.net/rhcp/
More Builds/Gapps can be found here:
gridlock32404 - cm7rc0 built by gridlock will be http://www.crackflashers.com/ cause of dropbox excessive traffic, will build new ones tonight if new commits
I uploaded it just now.
You will need to flash CWRecovery 3.0+. Which can be found at
http://xdafiles.net/rhcp/
This has been all built from source.
You need to put your phone in fastboot.
1) fastboot flash recovery recovery.img
2) reboot into recovery
3) backup your current rom
4) adb push the zip
5) flash the zip
As for gapps I can not post any gapps here. (Hint Paul obrians dump of the nexus S)
Notes: I am not responsible for any bricks or problems you may encounter I am just sharing this. If you follow the step you will have 2.3.1 on your phone.
Please help the devs who put this togther for us. fix some bugs. If you know how.
so far, It seems the video has been fixed up a bit. and the wifi works. So, Far the only thing not working video cam. (which is under works so i hear)
Also. Protected apps do not show since this is 2.3.1 (You can fix this by modding your build.prop or wait for google to add 2.3.1)
Thanks and I hope you enjoy this. Please someone mirror the build. I dont think mediafire will keep it up.
If you want to see protected apps. You need to edit your build.prop in system with the following:
Code:
ro.build.description=soju-user 2.3 GRH55 79397 release-keys
ro.build.fingerprint=google/soju/crespo:2.3/GRH55/79397:user/release-keys
This is built from current src as of 30 mins ago.
So, there is a few video fixes and others.
You can read the updates at: http://r.cyanogenmod.com/#q,status:merged,n,z
I appreciate it man. I just moved and I don't have an internet connection yet. It's hard to repo sync on a 1mbps Android tether.
Is there any difference between this one and the other one?
Sent from my HTC Vision using XDA App
smjfosho said:
Is there any difference between this one and the other one?
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
This one is more recent, with the newest commits.
Is your link supposed to point to recovery.img?
bivio said:
Is your link supposed to point to recovery.img?
Click to expand...
Click to collapse
Thanks. I mistyped fixed now.
Camcorder still borked?
rhcp0112345 said:
Hey Guys,
I figured i would share this.
All credit goes to cyanogenmod team. and cyanogen for being a killer coder
The rom can be found at: http://www.mediafire.com/?15l284rnq1zjt1h
I uploaded it just now.
You will need to flash this with CWR 3.0. Which can be found at
http://mrcellphoneunlocker.com/recovery.img
This has been all buit from source.
You need to put your phone in fastboot.
1) fastboot flash recovery recovery.img
2) reboot into recovery
3) backup your current rom
4) adb push the zip
5) flash the zip
As for gapps I can not post any gapps here. (Hint Paul obrians dump of the nexus S)
Notes: I am not responsible for any bricks or problems you may encounter I am just sharing this. If you follow the step you will have 2.3.1 on your phone.
Please help the devs who put this togther for us. fix some bugs. If you know how.
so far, It seems the video has been fixed up a bit. and the wifi works. So, Far the only thing not working video cam. (which is under works so i hear)
Also. Protected apps do not show since this is 2.3.1 (You can fix this by modding your build.prop or wait for google to add 2.3.1)
Thanks and I hope you enjoy this. Please someone mirror the build. I dont think mediafire will keep it up.
Click to expand...
Click to collapse
the link to the recovery img is broken because it says reovery not recovery
Im in no rush. Im just going to wait for the cyanogenmod team to fully finish it & wait for RC1.
Vandale said:
Im in no rush. Im just going to wait for the cyanogenmod team to fully finish it & wait for RC1.
Click to expand...
Click to collapse
Sure your not Thats why your watching these threads like everyone else, including me!!
Downloading now, Thanks for the build!
Been waiting for this all day. Thank you!
[ROM]cm7 gingerbread flavor
[Recovery]clockwork 3.0.0
Glad everyone likes.
My pleasure
Sent from my HTC Vision using XDA App
do you know if usb issue was addressed in this build
Have not tested it. Nor do I see any commits. So I assume same issue.I don't mount usb so doesn't bother me. I use adb
Sent from my HTC Vision using XDA App
is the "unknown" thing still showing up in phone number? its the only thing keeping me from sticking with Gingerbread @[email protected] silly, i know.
having problem flashing the img help
I get an assert failed error trying to flash the ROM, too bad I was really looking forward to trying CM7 .
cough..... cough http://forum.xda-developers.com/showpost.php?p=10083640&postcount=151 cough..... cough... man I'm really sick
I am in need of a kernel with loop enabled. I am in the newest OTA, if one doesn't exist I could use some help compiling one from the newest source, I have everything I need to do it on my Linux machine I am stuck trying to find which makefile to edit and where the .config file containing CONFIG_DEV_BLK_LOOP is located.
If it matters at all I would much rather compile my own kernel so I can learn something new.
Thanks for any help guys!
Sent from my White Evo 4G
Really!? I am not lazy or dumb, I have gone through a lot of kernel threads and it is not stated wether or not loop is enabled, all I am looking for is a kernel close to stock with loop enabled, come on guys I know someone here knows of one, if not is ANYONE willing to work with me while I learn to make one?
matthewjulian said:
Really!?
Click to expand...
Click to collapse
LOL. I'm on the more technical side, program for a living and have compiled a share of Linux kernels in my life, and I'm not quite sure what you are referring to. Sadly most of the sharper devs pretty much handle these forums in a one-way manner, they put out stuff, but they rarely read other people's posts. There are plenty of people that like to help out, but most of those folks aren't going to know anything about compilation.
The makefile you need to edit is in the root of the kernel source. The very first one that you see.
I am referring to loop devices support, this enables me to boot ubuntu on my Evo, it is one line of code that needs to be un-commented and changed to "CONFIG_DEV_BLK_LOOP=y
I am just lost,I was following this tut here http://htcevohacks.com/htc-evo-hacks/how-to-build-your-own-htc-evo-4g-android-kernel/
but the directions seriously slack off from step 11 onward, any ideas?
Do you by chance want to install Ubuntu on your phone? I think I saw something pertaining to that in some instructions I browsed over a while back.
lithid-cm said:
Grab the latest HTC source code:
edit the makefile:
Code:
CONFIG_DEV_BLK_LOOP=y
Then compile the kernel. There are plenty of how tos for kernel compiling. Let me know if you need more direction.
Click to expand...
Click to collapse
I have all the files I need, I was following the tut at htcevohacks.com but the instructions seriously slack off & there are numerous makefiles in multiple folders on top of that I can't seem to find what file contains the line config_dev_blk_loop, could you point me to a more complete walk-through please, oh and I am on the latest OTA with the newest kernel and radios.
Bump for desperation,chewed up almost 3 days of my time...
Sent from my White Evo 4G
Bump for this simp
Ok, well I guess I am gonna just have to PM each Dev individually about each individual kernel, damn all I need is a how-to or tut on kernel compiling (which the search function apparently can't find) or someone that knows of a 2.2 kernel with loop devices enabled. Oh well.
I'm pretty sure netarchy kernels are loop back enabled. Ask around there maybe.
Sent from my PC36100 using XDA App
nukedukem said:
I'm pretty sure netarchy kernels are loop back enabled. Ask around there maybe.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
YAAY! LMFAO, I will ask there, sorry I'm excited but I have been trying to get this working for a while; I would much rather learn to build it myself but I will take what I can get for now.
IF ANYONE knows where there is an in-depth tutorial on how to compile a kernel from the newest source I would be extremely appreciative, THANKS
Did you ever find or get your Complie to work? I tried for a while to compile the stock Kernel, then gave up. I took a stab in the dark and flashed a stable netarchy kernel. unfortunatly that Kernel didn't have Loop devices enabled (Pulled Config file and Unzipped it) I like the Kernel I am running but need to find a way to get ubuntu running.
Netarchy does have loop enabled, I am running Netarchy ___(will find which version later can't remember) but yeah I am running Lakia Linux
now(network security testing, think Backtrack 3) as well as another new Linux image from a guy here, anyways I think you need Netarchy universal cfs havs less no sbc 4.2.2
Sent from my White RLS5 Evo
THIS THREAD IS FOR DEVELOPERS ONLY!
Please do not post your problems with ROM here.
Post your ideas about working on ICS or CM7 and your problems with compiling sources or similiar.
I posted my p350 sources on github:
https://github.com/pax0r
You will find an instruction how to download mine soruces and compile it by yourself at:
https://github.com/pax0r/android_device_lge_pecan
Here we can speak how to improve this ROM ( 7.2 ) and also how to work on ICS. On my github you can find branch "ics" - it is somehow releated to my work on ICS but it's not complete.
So let's make our device EPIC!
For the begining I will post my problems releated to working on P350:
The problem I have with 7.2 release is that BT is not working - drapalyuk fixed it somehow in last release but I don't know how. If any one have idea what was changed from 1910 to 2010 drap release please let me know!
Also I started to port .35 kernel for our phone - but it's not working yet. Kernel boots and console via adb is usable at this moment but Android itself does not start on it. I will post more in this topic later.
now syncing the source
hi pax0r,
I'm trying to build CM 7.2 using your guide and source code but I notice a couple of issue that maybe create problems to someone beginner like me:
1) if you run ./extract-files.sh on a phone with CM 7.2 (vivekkalady) the extraction will fail on 3 files: libloc-rpc.so, libloc.so, libcommondefs.so. Maybe they are located in a different path.
2) I think this line of code in extract-files.sh is wrong:
Code:
adb pull /system/lib/hw/gralloc.default.so ../../../vendor/$MANUFACTURER/$DEVICE/proprietary/lib/hw/gralloc.default.so
it should be:
Code:
adb pull /system/lib/hw/gralloc.default.so ../../../vendor/$MANUFACTURER/$DEVICE/proprietary/lib/hw/gralloc.pecan.so
to avoid issue later.
I'd like to try to compile ics. What do you think is missing to make it works?
Best Regards,
Gabriele
hi pax0r,
the market crash few times at the begin but after I reboot it seems to be fine.
I attached the logcat.
Gabriele
megasoft78 said:
hi pax0r,
I'm trying to build CM 7.2 using your guide and source code but I notice a couple of issue that maybe create problems to someone beginner like me:
1) if you run ./extract-files.sh on a phone with CM 7.2 (vivekkalady) the extraction will fail on 3 files: libloc-rpc.so, libloc.so, libcommondefs.so. Maybe they are located in a different path.
2) I think this line of code in extract-files.sh is wrong:
Code:
adb pull /system/lib/hw/gralloc.default.so ../../../vendor/$MANUFACTURER/$DEVICE/proprietary/lib/hw/gralloc.default.so
it should be:
Code:
adb pull /system/lib/hw/gralloc.default.so ../../../vendor/$MANUFACTURER/$DEVICE/proprietary/lib/hw/gralloc.pecan.so
to avoid issue later.
I'd like to try to compile ics. What do you think is missing to make it works?
Best Regards,
Gabriele
Click to expand...
Click to collapse
Thanks for your contribute
For me there are no missing libs - I was running it on 7.1 so mby Vivek 7.2 is missing them?
About gralloc - there should be two libraries gralloc.default.so and gralloc.pecan.so
About ICS I have no idea yet and now no time to look at it - studies, work and 7.2 rom is everything I can do at once ;P
pax0r said:
Thanks for your contribute
For me there are no missing libs - I was running it on 7.1 so mby Vivek 7.2 is missing them?
About gralloc - there should be two libraries gralloc.default.so and gralloc.pecan.so
About ICS I have no idea yet and now no time to look at it - studies, work and 7.2 rom is everything I can do at once ;P
Click to expand...
Click to collapse
I think the problem about missing libs is related with vivek 7.2 rom.
it's strange but I can't see gralloc.pecan.so. Anyway I'll check it this evening.
I was able to build everything using your tutorial but now I want to try with ICS. I need a bit of searching on internet.
Thank you for your work,
Gabriele
Hm I've checked it and it fact there were no gralloc.pecan in extract - it was obviously a bug, I pulled everything from device, then I was making some refactoring and I didnt check it after that. I will push commit with fixes today.
Thanks for pointing it!
I see a keylayout headset push, how did you make the headset button works? I replaced both keylayout (qwerty with the haptic fix and 7k), but the dammed button still with problems =/
Thanks
PD: The new implementation of gralloc will fix the dammn warning of prelink? (on the log)
I'm not sure if this keylayout will make headset work as I don't have one but it was suggested that it may help but this need test. New gralloc is because it is open source comparing to the original propriety one and I'm testing its speed - it is at least the same so I will leave it
To solve a problem with prelink there should be a prelink.map created but I dont know exatly how to build one. It is not a critical error but with prelink.map the boot process could be faster.
I still didnt fixed copybit ;/
If you have some idea how to help refer to this post:
http://forum.xda-developers.com/showpost.php?p=21592280&postcount=28
EDIT: copybit fixed
hey could some one with the headset use this app:
https://market.android.com/details?id=aws.apps.keyeventdisplay
click headset buttons few times and post output of this app (if any)?
BTW do the headset buttons works on Vivek ROM?
Let me compile it with the new changes and I will try
At least, I'm currently using 7.1.0 (your 7.1.0) and nothing happens. (EDITED)
call\music button problem
paxor can u rectify the call\music button for wired headset
Can you compile ICS with your new files and send it to me ??
I will try to port ICS with your new files
Hey pax0r, are you sure with the fix? Compiled, installed... but I get a weird screen on menu =S
Thanks
I get a minor success at porting .35 kernel for p350. It boots and works but it still to bugged to public release. However if you have any dev experience you can grab it here https://github.com/pax0r/lge-kernel-msm7x27 and help me fix it!
I don't know exactly how Android handles GUI, IDK how to help right now, but I just can told you about the bug when android it's displaying interface.
Can you upload your compiled ICS so that we can tweak it to get it working!
I've removed my built version and now my source code wont even build :/
Hi Pax0r! well, i want to become a dev, i have some kind of linux knowledgement and have a good willing to learn, could you please point me out to some basic tutorials about building from cyanogen source? i've searched myself in the wiki but i didnt saw anything about lg pecan, any information you can give me, I will study it and maybe then become of help in dev community! thanks in advance!!
There is not much info about anything for P350 as it is not very popular device. Everything you need to start building CM for P350 is here, in mine Readme file:
https://github.com/pax0r/android_device_lge_pecan/blob/gingerbread/README.mkdn
Everything else you need to get by yourself =p but I will try answer all your questions
I learned everything by checking avaibale info for similar devices (MSM7227 board, for example: LG P500, ZTE Blade) and source codes.
Presenting the latest development version of the TeamWin Recovery Project's touch recovery for the HTC Wildfire S. TeamWin Touch Recovery now has official builds available through TeamWin and GooManager for the Marvel. With any luck MarvelC support will soon follow. Please visit the TWRP and TeamWin pages for more information.
Compiled for and tested on the original GSM Marvel. Always awaiting more testing from CDMA Marvel users. This software is provided without support or warranty: use it at your own risk.
Known Issues:
Fails on a handful of new GSM Marvel devices with updated/incompatible hardware, locking at the initial HTC splash screen.
Change Log:
XX:XX XX/8/2012 - Initial release of TWRP v2.2.2.0: Upstream code changes resolve the issues with formatting SD-EXT and partitioning the SD-Card. Includes the initial release of a revised 320x480 default theme with cleaner action pages, slightly larger buttons and more spacious checklists. First stable, full-featured and issue free release of TWRP for the HTC Wildfire S. Previous buggy versions have been removed from the revision history and can no longer be downloaded.
17:35 19/08/2012 PDT - Second release of TWRP v2.2.1.5: Issues with offmode charging resolved thanks to kalaker.
23:32 17/08/2012 PDT - Initial release of TWRP v2.2.1.5: Upstream code includes changes that resolve issues with the system rebooting during backup operations.
03:00 06/08/2012 PDT - Initial release of TWRP v2.2.1.4: Upstream code includes a handful of nice little bug fixes including a resolution for the mount issues.
23:05 05/08/2012 PDT - Minor aesthetic tweaks to the new theme.
02:29 05/08/2012 PDT - Third release of TWRP v2.2.1: Includes a carefully scaled v2.2 theme enabling the latest release's advanced features.
22:59 28/07/2012 PDT - Second release of TWRP v2.2.1: Corrected a glitch in my build environment that could have lead to issues and then forked it for dedicated platform builds. First dedicated MarvelC build.
23:58 27/07/2012 PDT - Initial release of TWRP v2.2.1: Compiled from the most recent code provided by: TWRP, Cryptomilk and the CyanogenMod ICS-Release branch.
22:55 09/07/2012 PDT - Maintenance release of TWRP v2.1.8: Reconfigured and shrank the kernel in order to utilize a less aggressive form of compression than LZMA. Switched from the CyanogenMod ICS branch to ICS-Release.
12:35 09/07/2012 PDT - Initial release of TWRP v2.1.8: Built using the ICS branchs of the CyanogenMod and Cryptomilk Marvel sources. Oversized image required LZMA compression.
To Do:
Build flashable .ZIP
Download Links:
TWRP for GSM HTC Wildfire S (Marvel) v2.2.2.0 (Preview Release) - Image - Mirror
MD5: 34f201ec8c8b0f0d2eae64c88ac3d888
TWRP for CDMA HTC Wildfire S (MarvelC) v2.2.2.0 (Preview Release) - Image - Mirror
MD5: 7c4d137a37098900ff3b2a9412ee8994
This is not the place for support.
I apologize in advance for what may seem abusive but, as it has been laid down here in the RULES it stands to reason that I'm decently covered.
THIS IS NOT THE PLACE FOR YOUR QUESTIONS! THIS IS!
In my infinite generosity I've created a place where users can get answers to frequently asked questions and seek support from one another. As an added bonus it will save you from my wrath. Please limit all discussion in this thread to development issues. I've started you off with some installation instructions as that was the first issue. I will update and check in as necessary. Enjoy!
You need to have the HTC drivers installed.
Then in cmd type:
fastboot flash recovery recovery.img.
Place the img file in the same folder as the adb files, so you won't have to specify a path.
Good luck,
Awesome work btw. :laugh:
WoefulDerelict said:
I apologize in advance for what may seem abusive but, as it has been laid down here in the RULES and I CLEARLY stated there would be ABSOLUTELY NO SUPPORT in my original post, it stands to reason that I'm decently covered.
THIS IS NOT THE PLACE FOR YOUR QUESTIONS! Ignorance and stupidity will not be tolerated.
In my infinite generosity I've created a place where users can get answers to frequently asked questions and seek support from one another. As an added bonus it will save you from my wrath. I've started you off with some installation instructions as that was the first issue. Enjoy!
Click to expand...
Click to collapse
If you're not going to support this, then this dosent belong in the Dev section... it can go in the General section or Apps section. Only Supported work belongs in the Dev section.
He means he wont be answering any questions in this thread.............he created another thread for discussion in the general section
Semantics...
Red5 said:
If you're not going to support this, then this dosent belong in the Dev section... it can go in the General section or Apps section. Only Supported work belongs in the Dev section.
Click to expand...
Click to collapse
I believe the issue here is entirely one of semantics. In my lexicon support encompasses the magical realm of end-user hand holding. In no way do I feel it is necessary or reasonable to expect a user manual with warm and fuzzy walk-troughs of every possible thing you could want to do and some friendly advice with a hug every time the user has a problem with their FREE software. I certainly don't plan to offer any of the above.
I do; however, plan on maintaining my work. I'm quite interested in information that would allow me to improve the image or resolve a reproducible issue. I also have no qualms discussing the work with other developers, providing updates as the code base evolves, accepting proper issue reports or feature suggestions. I'd simply prefer to avoid getting bogged down by questions that could easily be answered by visiting the project's home page or querying Google. I find it quite counter productive to wade through user prattle when I'm trying to fix an issue or collaborate with another developer.
Hello.
Is this recovery version work on Marvel with black CWM Recovery effect (new graphics hardware) ??
I'm not sure what you're asking.
marchelius said:
Hello.
Is this recovery version work on Marvel with black CWM Recovery effect (new graphics hardware) ??
Click to expand...
Click to collapse
This should be compatible with any HTC Marvel based Wildfire S. I believe they are all based on the same SOC. The kernel should have support for all MSM7227 based graphics hardware.
WoefulDerelict said:
This should be compatible with any HTC Marvel based Wildfire S...
Click to expand...
Click to collapse
Should be, but it isn't. After flash, my phone stuck on white screen with green HTC logo after attempt to enter in recovery...
Works perfectly on my phone. Mine is the A510e.
The joys of platform fragmentation.
marchelius said:
Should be, but it isn't. After flash, my phone stuck on white screen with green HTC logo after attempt to enter in recovery...
Click to expand...
Click to collapse
SomeDudeOnTheNet said:
Works perfectly on my phone. Mine is the A510e.
Click to expand...
Click to collapse
I suppose the plus side is that I have some confirmation that the software works on other A501e devices. If you're going to report something as not working could you at least go to the trouble of including your device's identifying information? A510b/e, SPL and Radio versions would be a great start.
WoefulDerelict said:
I suppose the plus side is that I have some confirmation that the software works on other A501e devices. If you're going to report something as not working could you at least go to the trouble of including your device's identifying information? A510b/e, SPL and Radio versions would be a great start.
Click to expand...
Click to collapse
OK.
HTC A510e
Android 2.3.5
EQDKP v4.7
Kernel 2.6.35.10-ga66971c
47.23e.35.3038H_7.57.39.10M
S-ON, unlocked via HTCDev
Main branch broken with CM9 on Marvel since updating to 2.2 code.
TWRP updated their main branch to v2.2 today. While I was hoping for the resolution of current issues their changes break my build with CM9. I'm stepping through the changes presently to see if I reason out what changed between 2.2 and 2.1.8 to cause the issue and correct the it. Stay tuned for more updates.
More please...
marchelius said:
OK.
HTC A510e
Android 2.3.5
EQDKP v4.7
Kernel 2.6.35.10-ga66971c
47.23e.35.3038H_7.57.39.10M
S-ON, unlocked via HTCDev
Click to expand...
Click to collapse
Could I get the HBOOT, MICROP and Radio version from your SPL? Hold the volume rocker and power button down while turning on the device to access the bootloader for that information.
IF these Frankenstein devices exist I'm going to need a profile of the revised hardware in order to correct the issue along with some proud owners to test fixes as I don't have access to one. The Marvel I was given is based off the original hardware profile and TWRP2.1.8 works fine when built with CM9 and the cryptomilk.org MSM7227 kernel. I'll do what I can to fix it but, I'm currently trying to resolve build issues with the new 2.2 release. I'm hoping this new code base along with a revised kernel will resolve many of the current issues.
It's ALIVE!
The problem is it's behaving like I brought it to life with a couple bolts of lightning. To say that it has issues would be overly kind but, it boots and I can navigate around. I'm currently trying to track down all the shorts making 2.2 twitch. Stay tuned.
Fresh revision.
Finally managed a clean build from the latest source. I'd love for some brave MarvelC users to give it a test before building a flashable .ZIP for the general public.
WoefulDerelict said:
Finally managed a clean build from the latest source. I'd love for some brave MarvelC users to give it a test before building a flashable .ZIP for the general public.
Click to expand...
Click to collapse
Thanks but theres a few issues
1. Theme isn't updated
2. On-screen keyboard wont work due to current theme
3 l. Swipe to start backups/restoring wont work due the theme.
More or less this is just like the previous twrp until themes are resized etc
Sent from my Wildfire S A510e using Tapatalk 2
Yea, I knew that.
eoghan2t7 said:
Thanks but theres a few issues
1. Theme isn't updated
2. On-screen keyboard wont work due to current theme
3 l. Swipe to start backups/restoring wont work due the theme.
More or less this is just like the previous twrp until themes are resized etc
Sent from my Wildfire S A510e using Tapatalk 2
Click to expand...
Click to collapse
This was already noted in the original post as the last entry under the known issues header. I maintain this for a reason. Thankfully the themes are XML based and updating it shouldn't be ridiculously difficult. Once I've gotten the issue list stable and nailed down where they are all rooted I'll see what I can do to tackle this and the formatting errors as they seem to be the largest TWRP specific issues I could correct. I wager the XML theme business will be relatively quick and painless.
WoefulDerelict said:
This was already noted in the original post as the last entry under the known issues header. I maintain this for a reason. Thankfully the themes are XML based and updating it shouldn't be ridiculously difficult. Once I've gotten the issue list stable and nailed down where they are all rooted I'll see what I can do to tackle this and the formatting errors as they seem to be the largest TWRP specific issues I could correct. I wager the XML theme business will be relatively quick and painless.
Click to expand...
Click to collapse
Yeah the themes are XML based but the image editing will be the worst part
Sent from my Wildfire S A510e using Tapatalk 2
eoghan2t7 said:
Yeah the themes are XML based but the image editing will be the worst part
Sent from my Wildfire S A510e using Tapatalk 2
Click to expand...
Click to collapse
I'm trying to imagine that being easy. I'm not totally inept in Adobe or AutoCad products so I'm sure I can toss together something in a week or so. Depends on how much the real job needs my time and brain meats.
Hello all. I have recently been striking out so far as KF development goes. I was going to start a new thread in the development forum, but I didn't think it was appropriate to do so yet as I have nothing to show for my efforts. Let me know if that should change.
What I've tried lately:
* Compiling cm11 with the latest sabermod tool chain (that is, 5.2). Results: numerous errors related to multiple definitions of functions. I have yet to figure out why.
* Compiling cm11 with the 3.4 kernel with what I think are the changes needed for otterx. Results: it compiled and installed. It boot loops.
* Compiling cm11 with the 3.4 kernel. Results: it compiled and installed. It boot loops.
* Downloading cm10.1, per the instructions in Hashcode's thread, in order to play with the 3.4 kernel in a working environment. Results: git repository errors. Unable to download.
I think the next thing I will investigate is the possibility of getting USB video to work so we can plug a web-cam into our KFs. Good idea? Bad idea? Does anyone care?
Can anyone here offer any assistance with any of this? Thank you.
Greetings.
Well, I finally got cm-10.1 to download and I dumped the kernel_omap_otter-common-p-android-omap-3.4 source into the tree. It compiled almost without effort. It also boot loops. Sorry. Perhaps 3.4 is never meant to happen. Perhaps this kernel tree simply doesn't work. Whatever the case, I think I'll work on something else for now.
Hi folks.
I'm still not ready to upload anything new yet, but if things work out, I'll soon be starting a new thread in the development section. News:
* I've compile CM11 with UberTC as an experiment. It has the feeling of being slightly smoother than Sabermod.
* I've noticed issues with several programs/games not working. I think things may be too optimized. I'll experiment with using less aggressive compiler options to see if that improves things. If not, I may install gapps to see if that solves anything.
* My latest experiment has been to configure the kernel for USB webcams. I've tried using the app Dashcam. It works (insert evil laugh), but only for a few seconds (insert sigh). I'm not sure if it's the app, my USB hub (sadly I can't seem to locate my OTG Y-cable), or over optimization. For now, though, here is a selfie taken with a USB webcam attached to my KF.
Cheers.
Good news everyone.
So I tried a different USB webcam and it works without issue. So, I guess the first camera is at fault - I've seen other mentions of the Logitech C250 having issues with the uvcvideo driver. I have yet to find a solution, though. Maybe the issues have been fixed in newer kernels and I should try porting those drivers.
Anyway, now to add some more USB camera drivers and see if I can get them to build as modules. Or maybe I'll try getting the HAL interface to work so that the camera can be used by things like the Camera app or Skype. I'll keep you posted.
Cheers.
Any luck recompiling CM 11?
Sent from my Amazon OtterX using XDA Free mobile app
BobJayJr said:
Any luck recompiling CM 11?
Sent from my Amazon OtterX using XDA Free mobile app
Click to expand...
Click to collapse
Not as far as getting the webcam to be seen as a camera. I have done some research, but more needs to be done.
I did recompile it with the Uber toolchain just for myself. I think it was ever so slightly faster than the SaberMod build. I haven't uploaded it as I noticed that my messing around with the default themes makes some apps nearly unreadable.
I've recently been working on an update for CM-12.1. Since that's done, and it works well enough, I started a new thread, "Random Builds and Development", in the development forum. Further updates will be there.