This is for developers only. No builds will be posted in this thread.
https://github.com/CM10DNA
For those who would like to work on it. I would recommend using a combination of the current HTC devices that have cm10.1 and the nexus 4 as a guide.
Any valid development related discussion can be posted here. Please no posts that aren't directly related to development (i.e. comments, thanks, etc.).
Currently working:
Display
Data (3g/4g)
SMS, MMS should work also but I haven't tested
WiFi
adb
MTP
Sensors (compass, gyro etc)
Vibration
LEDs
Audio
GPS
Bluetooth
Camera (FFC still has some issues with face detect)
Not working:
BT headset audio
Bugreport spreadsheet:
https://docs.google.com/spreadsheet/ccc?key=0AltBJkYoAZNLdEtQVTFoVkdxcWFfYXFJd05zcFYzUHc&usp=sharing
chad0989 said:
This is for developers only. No builds will be posted in this thread.
I have successfully managed to pull over the required changes from the nexus 4 for AOSP compatibility of our framebuffer and modify our panel drivers to work with it. I've pushed the source to the CM10DNA github here:
https://github.com/CM10DNA
Everything is currently in the cm-10.1-chad branches. Right now its not fully booting but does have working video (the major hurdle with CM10.1). I'm heading out of town for the next week so I won't be able to work on it.
For those who would like to work on it. I would recommend using a combination of the current HTC devices that have cm10.1 and the nexus 4 as a guide. It shouldn't be too hard to get it booting the rest of the way by not building various components (audio, camera etc) until you find the hangup.
Any valid development related discussion can be posted here. Please no posts that aren't directly related to development (i.e. comments, thanks, etc.).
Click to expand...
Click to collapse
I'm all for more development and would never want to sound ungrateful for any community contributions, but I get the impression (since I've been watching closely on XDA and IRC) that you're not working with drewx2 at all on THIS project even though it's been in the works for a while. If you were to contribute there instead of starting from scratch, we'd likely have it fully running in not time. He's only got a couple issues left and I'm not sure the framebuffer is one, but if his code-base falls short there, then you could at least improve on that.
I'd happily donate to you also if you were making contributions toward his project. Please consider that instead of going solo.
rainabba said:
I'm all for more development and would never want to sound ungrateful for any community contributions, but I get the impression (since I've been watching closely on XDA and IRC) that you're not working with drewx2 at all on THIS project even though it's been in the works for a while. If you were to contribute there instead of starting from scratch, we'd likely have it fully running in not time. He's only got a couple issues left and I'm not sure the framebuffer is one, but if his code-base falls short there, then you could at least improve on that.
I'd happily donate to you also if you were making contributions toward his project. Please consider that instead of going solo.
Click to expand...
Click to collapse
This is CM10.1, not CM10. Completely different animals even though one would think otherwise by the numbering. I have no desire to work on CM10. I appreciate your concern but please keep discussion on topic.
Sent from my HTC6435LVW using xda app-developers app
For anyone who is familiar with building CM if not Google is your friend. I have set up everything for you already. The default branch will pull cm-10.1-chad.
https://github.com/CM10DNA/android
Code:
repo init -u git://github.com/CM10DNA/android.git -b cm-10.1-chad
If you fix anything. Be sure to send a pull request back and we will take a look at it. Thank you.
Flyhalf205 said:
For anyone who is familiar with building CM if not Google is your friend. I have set up everything for you already. The default branch will pull cm-10.1-chad.
https://github.com/CM10DNA/android
Code:
repo init -u git://github.com/CM10DNA/android.git -b cm-10.1-chad
If you fix anything. Be sure to send a pull request back and we will take a look at it. Thank you.
Click to expand...
Click to collapse
I would love to take a look at, and for the guy above who thinks this is seperating the process I forked drews hub but could never get it to sync no matter what( I also have very little experience with github so it could be me). Best of wishes to you and yours on your trip. Have fun, be safe, and well. And thanks for making a new hub to play with. Last of my off topic-ness. More on topic what were your last efforts towards? It may make a good starting point.
Sent from my HTC6435LVW using xda premium
Sjflowerhorn said:
I would love to take a look at, and for the guy above who thinks this is seperating the process I forked drews hub but could never get it to sync no matter what( I also have very little experience with github so it could be me). Best of wishes to you and yours on your trip. Have fun, be safe, and well. And thanks for making a new hub to play with. Last of my off topic-ness. More on topic what were your last efforts towards? It may make a good starting point.
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
Right now it just gets to the boot logo screen. Maybe pulling a log finding out what's making it now boot fully.
Sent from my HTC6435LVW using Tapatalk 2
chad0989 said:
Any valid development related discussion can be posted here. Please no posts that aren't directly related to development (i.e. comments, thanks, etc.).
Click to expand...
Click to collapse
Sent from my HTC6435LVW using xda premium
DirtySimpleClean said:
chad0989 said:
Any valid development related discussion can be posted here. Please no posts that aren't directly related to development (i.e. comments, thanks, etc.).
Click to expand...
Click to collapse
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
^^^^This^^^^
This is the second time in 24 hours I've had to come in this thread and clean it.
Please abide by the op's request.
I do want to mention for anyone working on this that CM10.1 is distinctly different than CM10. It uses an updated display HAL, audio HAL, GPS HAL, and telephony is significantly different. You can't simply patch up from CM10.
The good news though is that our phone uses the same SOC as the nexus 4. There is no support for the n4 and the newer SoC (apq8064) in CM10, only the older msm8960 which most other HTC devices use. Hence why I keep stressing that its a much better idea to work on 10.1. Most anything we need to update we can pull almost directly from the n4.
I hope now everyone has resolved their differences and this can be worked on as a group. Like I've said anyone can pull anything from my tree and I dont care nor do I need to be credited. I just want fully working AOSP. It should be quite reasonable to achieve now that the display is working. Especially because of our similarities to the nexus.
Sent from my HTC6435LVW using xda app-developers app
chad0989 said:
I hope now everyone has resolved their differences and this can be worked on as a group. Like I've said anyone can pull anything from my tree and I dont care nor do I need to be credited. I just want fully working AOSP. It should be quite reasonable to achieve now that the display is working. Especially because of our similarities to the nexus.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Finally a noteworthy post on this topic. :highfive:
When we work as a team , the total is worth more than the sum of individuals.
Iam sure with devs like you and drew, DNA community will get fully working AOSP at the earliest.
I have the CM10DLX stuff synced already so when I get home tonight I'll switch to the -chad branch.. lol.. sorry I just thing the branch name is a little comical. Either way, have a safe trip man! BTW: Another device I was wondering may help shed some light is the Moto Droid Razr HD. While only dual core it looks like the primary difference is the gpu.. so there may be some helpful stuff in there as well.
Edit, is adb functional?
I just built and booted this and was happy to see that it got as far as upgrading my apps (but then hung when "starting apps"). Very nice.
However, I couldn't get adb to connect. I tried editing the initrd.img to set the property ro.adb.secure=0 in case is was related to securing adb, but that didn't help.
Is there some magic that you need to do? If not, how do you start to debug this?
FYI, in case someone else hits the same error that I did, I also had to do:
Code:
mkdir -p out/target/product/dlx/obj/SHARED_LIBRARIES/libmmjpeg_intermediates/
touch out/target/product/dlx/obj/SHARED_LIBRARIES/libmmjpeg_intermediates/export_includes
to get it to build.
Do you think disabling the old ion api would do much? Pretty sure mako and other 3.4 kernels use new
JoelZ9614 said:
Do you think disabling the old ion api would do much? Pretty sure mako and other 3.4 kernels use new
Click to expand...
Click to collapse
I think it could potentially break some of our proprietary libs. Audio and camera most likely. I think we should keep it the way it is for now. Once everything is working we can give it a shot to see.
Sent from my HTC6435LVW using xda app-developers app
Finally finished sync over night. Started a build before I left for work. I guess the first thing we need to sort out is getting adb working... I wonder if usb debugging is disabled by default..
Sent from my HTC6435LVW using Tapatalk 2
EmericanX said:
Finally finished sync over night. Started a build before I left for work. I guess the first thing we need to sort out is getting adb working... I wonder if usb debugging is disabled by default..
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
adb was working on my build originally. It may have gotten messed up when I pulled the init scripts into the tree. Maybe try messing with the init.usb also.
Sent from my HTC6435LVW using xda app-developers app
Lack of ADB seems to be kernel related. I flashed a different kernel and was able to pickup adb... of coarse it did't play well with libs but atleast its some sort of progress! lol.
EmericanX said:
Lack of ADB seems to be kernel related. I flashed a different kernel and was able to pickup adb... of coarse it did't play well with libs but atleast its some sort of progress! lol.
Click to expand...
Click to collapse
It's something in the ramdisk I'm sure. I'll fix it when I get back this weekend if someone doesn't before then.
Sent from my HTC6435LVW using xda app-developers app
chad0989 said:
It's something in the ramdisk I'm sure. I'll fix it when I get back this weekend if someone doesn't before then.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I've started looking around ramdisk but I'm crashing for the night. I'll do some more looking around tomorrow.
EmericanX said:
I've started looking around ramdisk but I'm crashing for the night. I'll do some more looking around tomorrow.
Click to expand...
Click to collapse
I don't have time to do any real work on this (this is my daily driver, use heavily for work phone and it's a time sink to backup/restore/fix /sdcard/0) today,but I took the boot.img and changed init.rc to include init.dlx.usb.rc instead of init.usb.rc and I believe that should get adb up and running for you.
To test, I booted viper 1.1.3 with the old kernel (no adb ever, but amazingly enough the display works enough for the boot animation) and booted it with the changed kernel which give me adb access.
Related
DEVS ONLY
If you don't know what to do with these, you shouldn't be using them. Developers only talk here please. If you have questions about what works, or just want to talk about AOSP progress, please post in the Q&A thread here.
Build Sources
Ice Cream Sandwich/Android 4.0/CyanogenMod 9 (Not Supported)
Device Tree
Vendor Tree
Common Tree
Kernel Tree
Jellybean/Android 4.1/Cyanogenmod 10 (Not Supported)
Device Tree
Vendor Tree
Common Tree
Kernel Tree
Jellybean MR1/Android 4.2/Cyanogenmod 10.1 (Supported)
Device Tree
Vendor Tree
Common Tree
Kernel Tree
Jellybean MR2/Android 4.3/Cyanogenmod 10.2 (Not Supported)
Device Tree
Vendor Tree
Common Tree
Kernel Tree
​
Reserved for me
One more just incase...
MaulingDeOso said:
Well, if we never get ION/IOMMU working, we'll likely never see graphics output, unless it be severely underperforming. HTC should have made the transition with the ICS kernel like everyone else, but Gingerbread->ICS was completely half-assed, and that makes ICS->Jellybean even more difficult.
On positive side, through this I've learned that we're 100% likely to never see an official Jellybean release.
Click to expand...
Click to collapse
OSO, Y U REPOS NO MAKE ME BACON?!
I decided yesterday to switch things up and go full Bear with my CM10 manifest but for whatever reason, I'm missing most "makes" after building the envsetup
Sent from my Rezound using xda premium
---------- Post added at 07:55 AM ---------- Previous post was at 07:39 AM ----------
dmeadows013 said:
Post it here so everyone can see it and we can get things fixed quicker
Via my Google Galaxy S3 running AOKP goodness
Click to expand...
Click to collapse
Was too absorbed with working on my build. Will post this today
Sent from my Rezound using xda premium
IAmTheOneTheyCallNeo said:
OSO, Y U REPOS NO MAKE ME BACON?!
I decided yesterday to switch things up and go full Bear with my CM10 manifest but for whatever reason, I'm missing most "makes" after building the envsetup
Click to expand...
Click to collapse
Haven't had that problem myself. Did you start with a clean manifest from https://github.com/CyanogenMod/android/tree/jellybean?
MaulingDeOso said:
Haven't had that problem myself. Did you start with a clean manifest from https://github.com/CyanogenMod/android/tree/jellybean?
Click to expand...
Click to collapse
Yes. When I get to work I'm going to wype and resync. It's very possible that I messed it up
Thanks for making yours available
Sent from my Rezound using xda premium
IAmTheOneTheyCallNeo said:
Yes. When I get to work I'm going to wype and resync. It's very possible that I messed it up
Thanks for making yours available
Sent from my Rezound using xda premium
Click to expand...
Click to collapse
Well you did try to use the ics frameworks base on jb
Via my Google Galaxy S3 running AOKP goodness
Ya ya ya
Hence the "switching things up" I went full JB yesterday and my system no longer wishes to make my bacon.
Sent from my Rezound using xda premium
IAmTheOneTheyCallNeo said:
Ya ya ya
Hence the "switching things up" I went full JB yesterday and my system no longer wishes to make my bacon.
Sent from my Rezound using xda premium
Click to expand...
Click to collapse
better tell it to get back in the kitchen and make you some bacon.
side note my hhd is full (insert porn joke here). i think it still has the inc repo on it. going to wipe all and reinstall Ubuntu this weekend and start fresh.
From IAmTheOneTheyCallNeo's build, I am getting EGL errors. Which is causing the non-boot.
Snuzzo said:
From IAmTheOneTheyCallNeo's build, I am getting EGL errors. Which is causing the non-boot.
Click to expand...
Click to collapse
What EGL errors? If you post them, we're more likely to be able to help.
Make sure your drivers are the JB ones, to get past a driver mismatch, but I imagine they already are. You might see something about the vsync control sysfs interface missing, which I've gotten past but not yet posted. Now I'm at a stage where it is unable to allocate a framebuffer, since the stubs always fail because ion is disabled.
Snuzzo, are you talking about my CM10 build or D's AOKP build?
D, I was unable to pull a log from either of our roms :/
It never loaded kernel. I also tried Snuzzo's JB kernel.
In brunching I noticed it calls for a different wifi chipset that's off by a single digit which is fixed by simply renaming it.
Sent from my HTC Rezound using xda premium
Same. Was starting to get a logcat after a fresh flash but from what I can recall is the same status you were stating. I tried older egl from ics. Ended up erroring the same. Now remind you, these are after fresh flashes.
@Neo
Yes thats your build
Sent from my HTC Rezound using xda app-developers app
Please post your egl errors here. They may be fixed by using a newer version of the qualcomm drivers
Via my Google Galaxy S3 running AOKP goodness
I've got video partially working (page flipping is disabled, but getting a black framebuffer, that's progress ). I'm still running into reboots, so video isn't the cause of that, and the reliability of getting a log is temperamental, so there's probably a race condition in the init scripts.
Got working vid in CM10. Bootlogo at least. Doesn't completely boot though.
Edit: Got it to boot but repeated android.phone crash. Permissions thing most likely.
chad0989 said:
Got working vid in CM10. Bootlogo at least. Doesn't completely boot though.
Edit: Got it to boot but repeated android.phone crash. Permissions thing most likely.
Click to expand...
Click to collapse
Great! I'd been working at video for too long with little progress. Any chance of getting your trees pushed so we can poke at things?
MaulingDeOso said:
Great! I'd been working at video for too long with little progress. Any chance of getting your trees pushed so we can poke at things?
Click to expand...
Click to collapse
As soon as I get it organized.
chad0989 said:
Got working vid in CM10. Bootlogo at least. Doesn't completely boot though.
Edit: Got it to boot but repeated android.phone crash. Permissions thing most likely.
Click to expand...
Click to collapse
awesome work chad.
Ill try to get it posted tonight. Fixed the android.phone FC (partially at least) but still getting a trebuchet FC and some artifacting. I can confirm that so far what does work hardware wise (but not usable because of the FCs):
Signal and 4g connected using HTCQualcommRIL
Sound
BT turns on and off
Touch
Vibration
Ok I have been working on getting wimax working in the evervolv jellybean build. I have spent the week only about an hour a day (darn kids won't leave me alone 8)) setting it all up. Im able to bring up the wimax menu and attempt to connect. My problem is that i can get the wimax server to start. If I rip apart cm10's boot img and input my kernel leaving everything alone it boots up wimax server and im able to run with no problem well other problems because im using a little different setup. So I have it down to the boot img specificly the files inside initrd.img. I have reviewed all those files and can't seem to find anything wrong. Everything is setup properly from what i can tell. Im stuck and i know there is alot of great people on this fourms that will help me . I have a github with my device tree and kernel for review https://github.com/flintman
Pre thanks
flintman said:
Ok I have been working on getting wimax working in the evervolv jellybean build. I have spent the week only about an hour a day (darn kids won't leave me alone 8)) setting it all up. Im able to bring up the wimax menu and attempt to connect. My problem is that i can get the wimax server to start. If I rip apart cm10's boot img and input my kernel leaving everything alone it boots up wimax server and im able to run with no problem well other problems because im using a little different setup. So I have it down to the boot img specificly the files inside initrd.img. I have reviewed all those files and can't seem to find anything wrong. Everything is setup properly from what i can tell. Im stuck and i know there is alot of great people on this fourms that will help me . I have a github with my device tree and kernel for review https://github.com/flintman
Pre thanks
Click to expand...
Click to collapse
Good luck Flintman!! I'll be cheering you on!!:highfive::good:
evervolv JB is a source built rom....
if you set up your github and repos to sync evervolv
then all u need to do is fork cmwimaxsettings
then cherry pick two commits to add the wimax
PM me for links and details
Lens_flare said:
evervolv JB is a source built rom....
if you set up your github and repos to sync evervolv
then all u need to do is fork cmwimaxsettings
then cherry pick two commits to add the wimax
PM me for links and details
Click to expand...
Click to collapse
It's not as easy as that... We had to do some more modifications to get it working tonight (flintman and myself). Seems that most aosp jellybean builds had been using a prebuilt HTC init binary, but we figured out how to get around this. At least everything seems to be working properly now. Flintman will be testing it out later tomorrow morning.
Working Great. I posted under comments in gerrit. I notice one more small thing.
So hows the progress
Sent from my PG86100 using xda app-developers app
thatboiken said:
So hows the progress
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
Go check the evervolv thread............this thread was just used to discuss things
Wimax already works on Evervolv....lol
thatboiken said:
So hows the progress
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
Latest Nightly includes the Wimax and it is working very well.
preludedrew said:
It's not as easy as that... We had to do some more modifications to get it working tonight (flintman and myself). Seems that most aosp jellybean builds had been using a prebuilt HTC init binary, but we figured out how to get around this. At least everything seems to be working properly now. Flintman will be testing it out later tomorrow morning.
Click to expand...
Click to collapse
Thanks for the headsup....
forgot AOSP is alot different than CM10
and may depend on some different things
Im glad to see you got it up and running
Sorry I have been very busy this is working in evervolv. The status bar indicator isn't working yet. I'm on hold with that until 4.2 has been fully merge. Once the merge is complete I want to fix the indicator then move onto another broken feature. Thanks to prelude for the help in getting a fully working WiMAXwith thether capabilities
Sent from my PG86100 using xda app-developers app
Random question has anyone got 4g to work in a sense 4.0 rom?
Sent from my Evo3D using xda app-developers app
thatboiken said:
Random question has anyone got 4g to work in a sense 4.0 rom?
Sent from my Evo3D using xda app-developers app
Click to expand...
Click to collapse
Supposedly newtoroot has http://forum.xda-developers.com/showthread.php?t=1981551 BUT he's yet to put out anything OTHER then screenshots hahahaha
Mazda said:
Supposedly newtoroot has http://forum.xda-developers.com/showthread.php?t=1981551 BUT he's yet to put out anything OTHER then screenshots hahahaha
Click to expand...
Click to collapse
Well you gotta trust the guy, he is the one that started all of the sense 4 Rom fad in the 3d forums
Sent from my PG86100 using Tapatalk 2
No update since last month but thanks anyways
Sent from my Evo3D using xda app-developers app
VictoriousShooter said:
Well you gotta trust the guy, he is the one that started all of the sense 4 Rom fad in the 3d forums
Sent from my PG86100 using Tapatalk 2
Click to expand...
Click to collapse
Didn't say I don't trust him, just said it was only screenshots
I'm sure there's other things to be worked out with wimax on sense 4.0 and when is ready, it'll come........WHEN will it come? Who knows hahahahaha
Mazda said:
..WHEN will it come? Who knows hahahahaha
Click to expand...
Click to collapse
The day after I upgrade in July to the newest Evo.
coal686 said:
The day after I upgrade in July to the newest Evo.
Click to expand...
Click to collapse
Not before I get mine in april
are there wimax drivers that are released, i want to experiment putting wimax in a sense 4 rom
You know I have posted in my public github how I got Wimax working in my MIUI jb builds although I haven't updated it on there since September. What I've learned while trying to get it to work on sense based ROMs is that HTC has about 10000 lines of fairly useless code to sort through to get it going. In most sense ROMs for our device, and of course this is all smali, everything you need is in framework.jar, only the connection service email in services.jar, wimax.jar of course, and believe it or not the bear of the whole thing Settings. apk. Settings is where my focus has been on DH Miui ICS. See settings has all the action for the most part such as all the messy HTCPreference* classes. Those classes are crazy in the sense that there are so many events triggered in each one that most of my days trying to get it to work have been spent trying to follow all of these events to see which ones are necessary and which aren't. The Aosp wimax on our devices only requires a third of that editing and the rest is getting the right libs and modules for the most part. If you do a grep of the word wimax after decompiling everything in the sense roms you'll see all of the places you need to mess with and sometimes write your own smali classes from scratch for the most part. I believe someone could do it without much difficulty but its the time it will take that's most likely the hardest part. As long as you have the correct binaries.
Sent from my Evo 3D CDMA using Tapatalk 2
cmbaughman said:
I believe someone could do it without much difficulty
Sent from my Evo 3D CDMA using Tapatalk 2
Click to expand...
Click to collapse
I vote for you to be that someone.
I know, I know... the droid x2 is a lost cause, but i have to make it last a little while longer and I have 2 of them so...
Is anyone interested or talented enough to try to get CM11 (kitkat) ported over to this device? I know @kev1nMark has been "talking" to dragonzkiller about getting into it, but anyone else have resources to contribute? I've never worked on the device at such a low level before, but I have written apps for it as well as know a thing or two about code. I'm happy to contribute whatever i can, even if its as simple as running up tests on my spare device.
Thoughts?
smallzfsu said:
I know, I know... the droid x2 is a lost cause, but i have to make it last a little while longer and I have 2 of them so...
Is anyone interested or talented enough to try to get CM11 (kitkat) ported over to this device? I know @kev1nMark has been "talking" to dragonzkiller about getting into it, but anyone else have resources to contribute? I've never worked on the device at such a low level before, but I have written apps for it as well as know a thing or two about code. I'm happy to contribute whatever i can, even if its as simple as running up tests on my spare device.
Thoughts?
Click to expand...
Click to collapse
I am considering it. This devices is a royal pain to work with though. I will see what i can do.
I'm certainly willing to test any builds that may come up, I'll have to locate a wall charger though..
Sent from my LG-LS970 using xda app-developers app
smallzfsu said:
I've never worked on the device at such a low level before, but I have written apps for it as well as know a thing or two about code. I'm happy to contribute whatever i can, even if its as simple as running up tests on my spare device.
Click to expand...
Click to collapse
In the same situation. It's looking like a good deal of work and might be a task I just simply don't have the skill for at this point. Still, I really want to have a useful old phone. Gingerbread makes me sad. Jelly Bean is just a resource hog. I've always wanted to learn a little more about the ROM build process and this might be a decent way to do it.
How does one go about porting KitKat to the X2?
markrulesallnow said:
How does one go about porting KitKat to the X2?
Click to expand...
Click to collapse
This is where I'm starting also w/ dragonzkiller's CM10 repos. http://wiki.cyanogenmod.org/w/Doc:_porting_intro
EDIT: Perhaps it's better to start building an updated CM10 just to get everything building correctly? With my lack of experience diving right into CM11 seems a bit bold.
One can simply put cm11 framework on a cm10 base but that's not what we want.
Sent from my XT907 using XDA Premium 4 mobile app
AKShotgun said:
One can simply put cm11 framework on a cm10 base but that's not what we want.
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Not what we want, but it may be our only option.
Sent from my SCH-I535 using xda app-developers app
Should anyone decide to take on this herculean task, I'll be more than happy to be a test bunny. My X2 is presently a glorified paperweight.
-blu
I have a Milestone X2 running under the ACS Alaska carrier. My device is rooted and I've used every ROM that Larson Thorpe has put in his MX2 collection. The ICS and JB roms did work, but had too many issues/crashes/reboots/etc so I just stuck with Eclipse 2.3 which is based on Gingerbread.
This phone is just... hard to deal with sometimes, and we all know it's mostly due to the amount of RAM. KitKat seems to take care of a ton of memory issues in Android (tested on my N7.) People have said that KitKat won't actually improve older devices by much, but any improvement would be amazing!
I'm totally down to fully test any builds anyone comes up with. I wish I could help build/develop for this phone, but I'm a web developer and have absolutely no skill with ROM building or kernels or anything like that.
Here's to hoping!
I can get everything set up and running (as in, ready to compile) but the compile errors are truly a mess to debug.
Is anyone willing to make a "how to" thread that describes how to make a basic rom, specific to this phone?
I think enough people are still interested, but I think we'd get further if we helped to educate each other.
LaserChicken said:
Is anyone willing to make a "how to" thread that describes how to make a basic rom, specific to this phone?
I think enough people are still interested, but I think we'd get further if we helped to educate each other.
Click to expand...
Click to collapse
This is about the closest thing I have seen, thanks Kevin for pointing it out already:
http://wiki.cyanogenmod.org/w/Doc:_porting_intro
Maybe once it gets put on more devices and development starts up again. You could ask nitroglycerin if he would be willing to update eclipse. But being a 512mb device this would be huge.
Sent from my GT-N5110 using XDA Premium HD app
Since we don't have a unlocked bootloader we can't just download the source and compile it, it takes a lot of skill. That's why we have a low development rate
Sent from my XT907 using XDA Premium 4 mobile app
AKShotgun said:
Since we don't have a unlocked bootloader we can't just download the source and compile it, it takes a lot of skill. That's why we have a low development rate
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well, actually, you can have CM compile around a pre-compiled kernel (what we have) but there's more to it than that.
One, we already have graphics issues...and KitKat forces you to have newer drivers or else you get black artifacting
This is due to OpenGL 3 not being supported by the vendor blobs
Our blobs don't even have ICS support...
Another nightmare is, yes, getting CM to take the precompiled kernel
If I got my hands on the source that the cm10.1 rom is based off of, we could start work
I would aim to start with 10.2, then maybe add in cm11 features but keep the old system
It would make things easier, keep radios, wifi, storage and display working...hopefully
Also, being as I'm on cm10, could anyone link me the patched recovery?
I'm glad to see I'm not the only one on the ol' X2, this would be so awesome if we got a KitKat ROM
Sent from my MB870 using xda app-developers app
optimusprimeuya said:
I'm glad to see I'm not the only one on the ol' X2, this would be so awesome if we got a KitKat ROM
Sent from my MB870 using xda app-developers app
Click to expand...
Click to collapse
I'm literally ready to start working on it now
But I need our device stuff and I'm waiting for a reply to a PM for it
---------- Post added at 09:47 AM ---------- Previous post was at 09:45 AM ----------
Kevin M said:
I can get everything set up and running (as in, ready to compile) but the compile errors are truly a mess to debug.
Click to expand...
Click to collapse
You have the device tree?
That's all I really need to get started
I want to do this soooo badly
Hell...I'm willing to do this Nexus Image style: hacking the files into a precompiled image to get it working
---------- Post added at 10:04 AM ---------- Previous post was at 09:47 AM ----------
Found the sources
smallzfsu said:
I know, I know... the droid x2 is a lost cause, but i have to make it last a little while longer and I have 2 of them so...
Is anyone interested or talented enough to try to get CM11 (kitkat) ported over to this device? I know @kev1nMark has been "talking" to dragonzkiller about getting into it, but anyone else have resources to contribute? I've never worked on the device at such a low level before, but I have written apps for it as well as know a thing or two about code. I'm happy to contribute whatever i can, even if its as simple as running up tests on my spare device.
Thoughts?
Click to expand...
Click to collapse
I am willing to test. My programming skills are certainly not up to this task, but I would like to learn. Any way to get started?
polymath257 said:
I am willing to test. My programming skills are certainly not up to this task, but I would like to learn. Any way to get started?
Click to expand...
Click to collapse
I'm about to go work on it now
Maybe we'll have it in two weeks? No? Probably not...
I'll try building CM11, but don't expect the graphics to work
At all
Hey guys just wondering if there are any devs out there that can work on kernels. I think it would be awesome to have a kernel that includes dt2w. Anyone else as interested in this as me?
Sent from my HTC6435LVW using Tapatalk
coachcrey said:
Hey guys just wondering if there are any devs out there that can work on kernels. I think it would be awesome to have a kernel that includes dt2w. Anyone else as interested in this as me?
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
crparmer
not sure if i spelled it right.
thayl0 said:
crparmer
not sure if i spelled it right.
Click to expand...
Click to collapse
Yeah but I think he likes to keep thing as stock as possible.
Sent from my HTC6435LVW using Tapatalk
coachcrey said:
Yeah but I think he likes to keep thing as stock as possible.
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
Not really it done a amazing kernal for cm 10.2
And I believe he is working on one for 4.4 kitkat cm 11
thayl0 said:
Not really it done a amazing kernal for cm 10.2
And I believe he is working on one for 4.4 kitkat cm 11
Click to expand...
Click to collapse
I know that but when people have asked him to add sleep to wake he didn't seem interested in that I'm not dogging him at all man he great no question asked.
Sent from my HTC6435LVW using Tapatalk
Adding it takes time, adds risk to the stability of the phone and gives me no benefit. My phone is heavily locked down by my IT department and with a minimum 8 character alpha numeric password, the sweep or double tap to wake is not improving my life.
I love s2w as much add the next guy..... but try omnirom 4.4, and enable active display.... you might like it better.
Sent from my HTC6435LVW using xda app-developers app
crpalmer said:
Adding it takes time, adds risk to the stability of the phone and gives me no benefit. My phone is heavily locked down by my IT department and with a minimum 8 character alpha numeric password, the sweep or double tap to wake is not improving my life.
Click to expand...
Click to collapse
This is why i was trying to shout out to other. I know your work is the real deal man. Its just something I'm interested in. In no way was i trying to insult you.
Kauffman_c said:
I love s2w as much add the next guy..... but try omnirom 4.4, and enable active display.... you might like it better.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I'm not sure what settings you use with active display but I'm not really sold using it. I like sweep2wake as well.
Sent from my HTC6435LVW using Tapatalk
Okay, here's a dumb question... Right now we share the AOSP kernel source with the HTC One. Wouldn't flashing a custom AOSP kernel for the One work on the DNA?
yeah some nice s2w like the old cubed kernel so you can do just "back to home" to wake it, its so nice i dont see how ppl dont want it of course unless they have some crazy circumstance like crpalmer just described
but we have a lot of diff roms so something like this would be rather difficult to choose one version of android for this to be implemented on or many kernels, lotta work it seems.
Ask .torrented. He made a s2w kernel a few months ago. He may have a very busy schedule but if enough people ask he may do it.
jamiethemorris said:
Okay, here's a dumb question... Right now we share the AOSP kernel source with the HTC One. Wouldn't flashing a custom AOSP kernel for the One work on the DNA?
Click to expand...
Click to collapse
Yeah I Dont think it's that simple unfortunately.
Sent from my HTC6435LVW using Tapatalk
I don't think one of those kernels would be difficult to port though. I'm just wondering what exactly makes the kernels different, because if you compare the CyanogenMod pages for the DNA and the One, the kernel source link is for the M7 on both of them. I was considering trying to port a kernel myself a while back, but I couldn't find enough information online about it... I think it may be one of those things where if you have enough knowledge of ROM building and git than you just intuitively know how to do it.
Sent from my Droid DNA using Tapatalk Pro
jamiethemorris said:
I don't think one of those kernels would be difficult to port though. I'm just wondering what exactly makes the kernels different, because if you compare the CyanogenMod pages for the DNA and the One, the kernel source link is for the M7 on both of them. I was considering trying to port a kernel myself a while back, but I couldn't find enough information online about it... I think it may be one of those things where if you have enough knowledge of ROM building and git than you just intuitively know how to do it.
Sent from my Droid DNA using Tapatalk Pro
Click to expand...
Click to collapse
Yeah I'm not sure either. If you wanted to give it a run for your money I'm sure palmer would give you some pointers. I would love to see a dt2w kernel!! Lol
Sent from my HTC6435LVW using Tapatalk
I couldn't resist, I just had to try it. I figured the worst that would happen is I'd have to reflash my ROM. So I flashed the HTC one sti kernel here: http://forum.xda-developers.com/showthread.php?t=2507710 it flashed and booted just fine and everything works... None of the s2w dt2w features etc are working but it said it flashed successfully so I'm assuming it's running the kernel... I don't remember what it said in about phone before but it currently shows "3.4.10-CM-gbce7128 Robert @ minty #1."
Edit: yeah I'm pretty sure that's the stock kernel...
It was worth a try right?
@crpalmer would you be willing to give me some pointers on porting or building a kernel? I'm somewhat inexperienced with building, so I don't know if I should bother taking on a task like this.
Sent from my Droid DNA using Tapatalk Pro
coachcrey said:
Yeah I'm not sure either. If you wanted to give it a run for your money I'm sure palmer would give you some pointers. I would love to see a dt2w kernel!! Lol
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
Do not, really, do NOT flash a kernel for a different phone. The Linux kernel is setup to have the same core files across a huge number of devices but then have device specific files. We share the M7 kernel but we have different device specific files. These files control lots of things but the most important is determining what pieces of hardware are given specific voltages, etc.
If you want to try to build my kernel, you should be able to do so fairly easily. Porting the functionality will require some programming knowledge and some knowledge of git. If you think you can do it, let me know and I'll try to give you some first steps on building my kernel.
Porting a M7 kernel to our device might be hard. There is a high probability that they aren't necessarily keeping up-to-date on the changes to our device specific files. You'd have to figure out if they were and, if not, pull in the missing changes.
crpalmer said:
Do not, really, do NOT flash a kernel for a different phone. The Linux kernel is setup to have the same core files across a huge number of devices but then have device specific files. We share the M7 kernel but we have different device specific files. These files control lots of things but the most important is determining what pieces of hardware are given specific voltages, etc.
If you want to try to build my kernel, you should be able to do so fairly easily. Porting the functionality will require some programming knowledge and some knowledge of git. If you think you can do it, let me know and I'll try to give you some first steps on building my kernel.
Porting a M7 kernel to our device might be hard. There is a high probability that they aren't necessarily keeping up-to-date on the changes to our device specific files. You'd have to figure out if they were and, if not, pull in the missing changes.
Click to expand...
Click to collapse
I wasn't implying anybody should ever flash a kernel not built for this phone.
Sent from my HTC6435LVW using Tapatalk
coachcrey said:
I wasn't implying anybody should ever flash a kernel not built for this phone.
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
My bad. I quoted the wrong post! I just wanted to make sure it was clear that the same source is not the same as safe to flash because we have completely different hardware configuration. So, I guess it was good that I misquoted so that I have a chance to say it a second time!
crpalmer said:
My bad. I quoted the wrong post! I just wanted to make sure it was clear that the same source is not the same as safe to flash because we have completely different hardware configuration. So, I guess it was good that I misquoted so that I have a chance to say it a second time!
Click to expand...
Click to collapse
OK right in man. Thanks for all the hard work.
Sent from my HTC6435LVW using Tapatalk
I guess my post didn't go through... @crpalmer what type of programming knowledge are we taking about? My knowledge is limited to some dsdt editing and supercollider... In other words, I'm definitely not a programmer but I understand the general concepts.
Edit: I'm not too experienced with git either but I have built cm10.1 From the source for my nexus 7 a few just as learning experience.
Sent from my Droid DNA using Tapatalk Pro
Hey guys,
First off. Mahdi rom is Amazing! I love all the features and it had just the right amount of features for my new G2! Thanks Doc for maintaining this for us!
Second, I am a kernel dev and am working on my own kernel for the G2. I have essentially made my base Savoca's Furnace Kernel (With his permission of course) and will be adding in features as I go. Currently I build for the Moto G but wanted to buy a higher end device and love this phone. I have the D800 (AT&T) so as it stands I only have a test kernel for the D800/JDI. You may be able to use Savoca's new panel tool that you flash after flashing the kernel to swap screen support. I would love for some others to test it out and let me know. I will be bringing a different perspective to kernel Dev'n than normal. I like to be hands on about the process and to instigate discussion so others can learn. Let me know if anyone is interested.I will be building for all variants that Furnace kernel supports.
Note to ALL: I will open an official thread when I am satisfied with testing. Thanks for your interest! Hope I can bring something new to the G2!
Right now I have added:
Custom Hotplug from Blechd0se (Moto G) Falcon Hotplug - Ultra simplified and efficient.
Sl(auo)b optimizations
frandom
ETC
Check source for more indepth info!
Just pm me if you are interested. Everything looks to be going pretty good so I should be opening a thread pretty soon. Remember this is still in Beta. Still I would love to hear from others out there. Thanks!
Render-Kernel-AOSP_d800-06-29-BR3-JDI.zip
Render-Kernel-AOSP_vs980-06-29-BR3-LGD.zip
Render-Kernel-AOSP_d800-07-01-BR3-LGD.zip
Render-Kernel-AOSP_d802-07-01-BR3-LGD.zip
Kind Regards,
Render
Source
kk-test is my active branch right now
Glad to see you here! I'll test out VS980 when you start building the other variants ?
JRJ442 said:
Glad to see you here! I'll test out VS980 when you start building the other variants ?
Click to expand...
Click to collapse
I will go ahead and rip you a build. Give me a sec . . .
JDI?
RenderBroken said:
I will go ahead and rip you a build. Give me a sec . . .
JDI?
Click to expand...
Click to collapse
LGD
JRJ442 said:
LGD
Click to expand...
Click to collapse
OK Give me a tick and I will build it. Should not take long.
Nice, love devs being able to jump in on the g2. Glad your here. The link you posted for the d800....should that work on aicp...?
Sent from my LG-D800 using XDA Premium 4 mobile app
jeff5347 said:
Nice, love devs being able to jump in on the g2. Glad your here. The link you posted for the d800....should that work on aicp...?
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Not 100% sure but give it a try. Should hurt anything. I am fairly new to the G2 and don't know every single in and out yet. I do know that the source base is pretty fractured but I am hoping to bridge the gap a bit. Let me know so I can let others know in the future. Thanks!
OK just flashed. Booted fine but froze and that is my fault
..I started playing around and enabled intellidemand. From what I remember for some reason that gov is a problems. Rebooted and left the kernel stock. Now running fine and no problems. I'll update on battery and perf.
Sent from my LG-D800 using XDA Premium 4 mobile app
JRJ442 said:
LGD
Click to expand...
Click to collapse
OK Built and posted in OP#1
jeff5347 said:
OK just flashed. Booted fine but froze and that is my fault
..I started playing around and enabled intellidemand. From what I remember for some reason that gov is a problems. Rebooted and left the kernel stock. Now running fine and no problems. I'll update on battery and perf.
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Great, Thanks for the info, I will most likely be removing it anyways. I have inherited Savoca's source and am laying mine down ontop. He did all the amazing groundwork that will allow me to support numerous devices much much sooner. Thanks and let me know how it continues to work for you!
@RenderBroken booted up just fine. Running smooth. I'll report back tomorrow as well. Thanks again for building for us. ?
Render, since I cleaned the kernel and left it stock I'm getting the SOD. If I let the screen go off and try to turn the screen back on it just lights up black. Tried and tried but just a black screen. Unfortunately I had to go back for now. Can't wait to try it once it gets cleaned up.
Sent from my LG-D800 using XDA Premium 4 mobile app
Link to source ?
I looked at Savoca source and it appeared to have no FM support in audio driver, same as Mahdi now.
I'll copy my post from Mahdi thread, in case your interested in enabling FM:
I've concluded that sound/soc/msm/msm8974.c needs to be patched with the "#ifdef CONFIG_SND_FM_RADIO" code seen here: https://github.com/CyanogenMod/android_kernel_lge_msm8974/blob/cm-11.0/sound/soc/msm/msm8974.c
Unless you're up for that, I'll presume I'll try it myself.
Any tips for kernel building for a JDI LS980 ? I built a few Android kernels in 2013, but never even tried flashing them.
That said, I've been doing embedded linux professionally since 1997.
Thanks !
1 question. Why didn't you post the kernel in one of the development sections??
Transmitted via Geass
At first it could be in Original Dev section. I can test something on d802 LGD. @mikereidis u have a G2? if yes then it's great to see more devs here
RenderBroken said:
Not 100% sure but give it a try. Should hurt anything. I am fairly new to the G2 and don't know every single in and out yet. I do know that the source base is pretty fractured but I am hoping to bridge the gap a bit. Let me know so I can let others know in the future. Thanks!
Click to expand...
Click to collapse
hi, thank you for supporting our beloved g2 we all appreciate it, i just have a request. you see , only the Qremote can control the IR on our device, lg didnt use the real android open source drivers for it . so we cant use apps like smartIR whereas samsung n htc are compatible. im just suggesting if you can try and implement open source IR drivers to the g2 ? so that we can use all these apps that utilize that api i know this is gonna be an insanely though part as you'd have to figure out which hw IR we are using and then implement a compatible driver for it. but im just suggesting that this is perhaps the only bad part of the g2 till now
Super Post!
jeff5347 said:
Render, since I cleaned the kernel and left it stock I'm getting the SOD. If I let the screen go off and try to turn the screen back on it just lights up black. Tried and tried but just a black screen. Unfortunately I had to go back for now. Can't wait to try it once it gets cleaned up.
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Then it sounds like you don't have LDG like you said but you have JDI.
mikereidis said:
Link to source ?
I looked at Savoca source and it appeared to have no FM support in audio driver, same as Mahdi now.
I'll copy my post from Mahdi thread, in case your interested in enabling FM:
I've concluded that sound/soc/msm/msm8974.c needs to be patched with the "#ifdef CONFIG_SND_FM_RADIO" code seen here: https://github.com/CyanogenMod/android_kernel_lge_msm8974/blob/cm-11.0/sound/soc/msm/msm8974.c
Unless you're up for that, I'll presume I'll try it myself.
Any tips for kernel building for a JDI LS980 ? I built a few Android kernels in 2013, but never even tried flashing them.
That said, I've been doing embedded linux professionally since 1997.
Thanks !
Click to expand...
Click to collapse
I will go ahead and push the latest changes and post link. Also I am fairly new to the G2 scene and just how fractured the source code is for it. I would love to take a look at this if its simple enough to add in. I am not against trying though. If you could, remind me when I open up the main thrad in the next few days. I am heading to the beach with my wife and son so will not be able to do much in the next 2 days but when I get back and I get some good word about the builds, I will open the thread and kick in to overdrive.
Ace42 said:
1 question. Why didn't you post the kernel in one of the development sections??
Transmitted via Geass
Click to expand...
Click to collapse
Just wanted some testers for now. I dont want to open a thread to a million questions about each device yet when I don't have a kernel ready for them. I will be creating a thread very soon.
shriom_manerker said:
hi, thank you for supporting our beloved g2 we all appreciate it, i just have a request. you see , only the Qremote can control the IR on our device, lg didnt use the real android open source drivers for it . so we cant use apps like smartIR whereas samsung n htc are compatible. im just suggesting if you can try and implement open source IR drivers to the g2 ? so that we can use all these apps that utilize that api i know this is gonna be an insanely though part as you'd have to figure out which hw IR we are using and then implement a compatible driver for it. but im just suggesting that this is perhaps the only bad part of the g2 till now
Click to expand...
Click to collapse
I like challenges, I will take a look as soon as I can. Most likely it will be after I get everything completely setup. If you could remind me later when I open up the official thread. Thanks!
Planning d801?
RenderBroken said:
I like challenges, I will take a look as soon as I can. Most likely it will be after I get everything completely setup. If you could remind me later when I open up the official thread. Thanks!
Click to expand...
Click to collapse
im experienced at coding, c,java,html and php. i ahve compiled kernels in the past but that was like 4 years ago.ill try my best to help you. although ill need your help too.
I've looked under terminal and it states I have a lgd. Flashed savacos older kernels that were lgd and they all worked fine. I get no black lines just when I shut the screen off it comes on but full black.
Sent from my LG-D800 using XDA Premium 4 mobile app
jamesd1085 said:
Planning d801?
Click to expand...
Click to collapse
I planning for all variants.
shriom_manerker said:
im experienced at coding, c,java,html and php. i ahve compiled kernels in the past but that was like 4 years ago.ill try my best to help you. although ill need your help too.
Click to expand...
Click to collapse
Great, I love to collaborate. That's the best way to learn! Thanks for the offer. My Google hangouts is
[email protected]
jeff5347 said:
I've looked under terminal and it states I have a lgd. Flashed savacos older kernels that were lgd and they all worked fine. I get no black lines just when I shut the screen off it comes on but full black.
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Weird, I am pretty certain I build to LGD variant. Sorry brother. Try using Savoca's panel changer that you flash after the kernel. I even used Savoca's build script so not sure what the problem is but I am pretty sure that it's not a SoD problem you are having but a panel issue.