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
Related
As CM9 is now mostly being worked on by Lupohirp and I also wanted to bring some IceCream Sandwich to our phone I started building ICS from Code Aurora sources.
I have fixed most build errors allready and I'm almost finished.
So this evening or tomorrow I will know if it boots
After that I need to implement Lupohirps fixes for hardwareacceleration, I'm waiting for the latest patches as they mean full hardwareacceleration.
After first release this thread will be used as discussion-thread.
Instead of posting Thanks, you're the greatest etc., please press Thanks-button
Tip: If you use only capitals in thread name, you will have all characters non-capital.
So, if I were you, I would fully spell Ice Scream Sandwich (joke) instead of ICS.
Since that is VERY important, I thought help him out
But thanks anyway, looking forward.
Wasn't ciaox busy with it also?
Greets!
He planned to, but when he has his laptop again he is going to work on it with me
After that he probably will work on OpenOptimus 3
Very interesting, waiting for your rom.
mDroidd said:
Tip: If you use only capitals in thread name, you will have all characters non-capital.
So, if I were you, I would fully spell Ice Scream Sandwich (joke) instead of ICS.
Since that is VERY important, I thought help him out
But thanks anyway, looking forward.
Wasn't ciaox busy with it also?
Greets!
Click to expand...
Click to collapse
Hey, you found a nice name for the rom lol
Sent from my LG-P500
Why did you stop Screaming for Sandwich Arjen?? It was looking kool...!
Please make it IceScreamSandwich to make it look like a kool custom ROM like CodeName Android n all..
Try making it like:
[WIP][ROM][ICS][4.0.3] IceScreamSandwich from CodeAurora Sources
Sent from my iPad 3 using XDA App
RockR172 said:
Why did you stop Screaming for Sandwich Arjen?? It was looking kool...!
Please make it IceScreamSandwich to make it look like a kool custom ROM like CodeName Android n all..
Try making it like:
[WIP][ROM][ICS][4.0.3] IceScreamSandwich from CodeAurora Sources
Sent from my iPad 3 using XDA App
Click to expand...
Click to collapse
Ok, it is a really cool name I must admit
IMHO this is better: I scream: sandwich!! Sorry for the OT
http://www.youtube.com/watch?v=7rK3s_BP9kE
Is this cm9 or aosp?(when released)
Sent from my LG-P500
It's Code Aurora, like mentioned in first post But looks same as aosp.
When released feel free to use it as base for other Roms
Sent from my LG-P500 using XDA App
It isn't based on CyanogenMod? Maybe there isn't APN problem!
I think I'll try this ROM
Lets hope there are no problems with tmobile usa apn's
Sent from my LG-P500 using xda premium
Update:
Succeeded building, but getting bootloops.
Rebuilding again after make clean to see if there still are problems during build.
Edit:
Build process is fine, but still bootloops.
Need to look in logcat.
_Arjen_ said:
Update:
Succeeded building, but getting bootloops.
Rebuilding again after make clean to see if there still are problems during build.
Edit:
Build process is fine, but still bootloops.
Need to look in logcat.
Click to expand...
Click to collapse
Woohoo! Finally you started,I will join ASAP. There's a little possibility I can have my laptop back in week-end
BTW: What device folder did you use? I think we have to make one from zero. I would suggest an AOSP device folder for ICS,or maybe just our gb device folder with some mods for ICS.
Bytecode said:
Woohoo! Finally you started,I will join ASAP. There's a little possibility I can have my laptop back in week-end
BTW: What device folder did you use? I think we have to make one from zero. I would suggest an AOSP device folder for ICS,or maybe just our gb device folder with some mods for ICS.
Click to expand...
Click to collapse
or maybe, lupohirps?? It will make work faster..
Sent from my iPad 3 using XDA App
I did use Lupohirps device folder as base and converted it to aosp.
Made a special Github for it to work on will upload it asap so you can work on it too Bytecode
A few things needed to be altered in some things from external folder and framework. In logcat I get errors about libsurfaceflinger and some other things.
Tonight I will work on it again.
@arjen---any update?? It is much awaited rom but i cant see that much heat on it
BTW:what about the video...does it work smoothly and one more thing--does anything crash when we use lcd resolution(com.android.phone crashes on lupo's build)
---------- Post added at 09:59 PM ---------- Previous post was at 09:59 PM ----------
@arjen---any update?? It is much awaited rom but i cant see that much heat on it
BTW:what about the video...does it work smoothly and one more thing--does anything crash when we use lcd resolution(com.android.phone crashes on lupo's build)
I'm no machine
I gave an update (right before your post), please read before posting, there ain't that many posts yet
i think it would have been easier if u have posted the info rather than going mad at me
i just asked about the stuff(not asked u to build it)
sry for expecting some good feedback from your rom and you
Thanks....... question, will you make this for both new and old basebands? I would appreciate it much.
Sent from my LG-P500 using XDA App
I am not part of the cyanogenmod team, I just got bored and decided to put this together. I'm flashing a different ROM so there will be no support/fixes/further development (unless I change my mind but dont expect it)
Sync'd and built 3/28
Toastcfh's stock kernel
Wifi is borked, cyanogenmod must have updated something and broke compatibility with with the device tree I used.
I've ran it since last night after I built it and everything seemed to work (obviously excluding camera, wifi, 4g, 3D) but I haven't taken it through any thorough testing nor do I use things such as bluetooth or in-call mute so some things are untested.
Use at your own risk I am not responsible for anything wrong that happens to your phone as a result of flashing this.
Download Link: http://d-h.st/dUf
Use it, don't, mod, fix, mirror, repost, link, do whatever with it. I don't care.
Credits:
Cyanogenmod Team for the source (duh)
toastcfh for the device tree/kernel
opensensation team for msm8660 common files
Thanks for posting this.... But I'll pass until CM9 is more stable and has camera, 4g, wifi and 3D working.
DarkManX4lf said:
Thanks for posting this.... But I'll pass until CM9 is more stable and has camera, 4g, wifi and 3D working.
Click to expand...
Click to collapse
That's going to be quite a long wait.
Smartass with a Dumb Phone.
DarkManX4lf said:
Thanks for posting this.... But I'll pass until CM9 is more stable and has camera, 4g, wifi and 3D working.
Click to expand...
Click to collapse
It would be easier to acquire a unicorns horn.
FreEvo 2.3d
Sony Brava Engine d-_-b
dannyboyex said:
It would be easier to acquire a unicorns horn.
FreEvo 2.3d
Sony Brava Engine d-_-b
Click to expand...
Click to collapse
Haha, in fact.. your best bet to get a fully functioning CM9 wil be to get another phone. The 3D is the bastard child of real development!
Rippley05 said:
Haha, in fact.. your best bet to get a fully functioning CM9 wil be to get another phone. The 3D is the bastard child of real development!
Click to expand...
Click to collapse
Yeah that definitely seems to be true.
Rippley05 said:
Haha, in fact.. your best bet to get a fully functioning CM9 wil be to get another phone. The 3D is the bastard child of real development!
Click to expand...
Click to collapse
Try owning a Moto product!
DaveRichardson said:
Try owning a Moto product!
Click to expand...
Click to collapse
this up to 100k times
oh u used msm8660-common from open sensation maybe thats why mine wont boot...im using cm's
JoelZ9614 said:
oh u used msm8660-common from open sensation maybe thats why mine wont boot...im using cm's
Click to expand...
Click to collapse
i made it like right before it became part of CMs github i think they just pulled it from opensensations github. ill do a repo sync and build a 4.0.4 with how my stuffs set up and if it boots ill let you know how i set it up
pwnyourace said:
i made it like right before it became part of CMs github i think they just pulled it from opensensations github. ill do a repo sync and build a 4.0.4 with how my stuffs set up and if it boots ill let you know how i set it up
Click to expand...
Click to collapse
alright cool
JoelZ9614 said:
alright cool
Click to expand...
Click to collapse
if i can get wifi going, which i think i just figured out while looking through the common files and the sensation tree, i might keep updating this and post it in dev..
pwnyourace said:
if i can get wifi going, which i think i just figured out while looking through the common files and the sensation tree, i might keep updating this and post it in dev..
Click to expand...
Click to collapse
4.0.4 booted for u?
JoelZ9614 said:
4.0.4 booted for u?
Click to expand...
Click to collapse
almost done compiling, was just saying lol. idk what could be causing it not to boot, i was on preludedrews twitter and evervolv has 4.0.4 booting just fine. its optimizing the nightly zip right now so ill give it a try and some troubleshooting and hopefully i can come up with something
ive got it booting but still no wifi D:
edit: oh, well i guess that might be why XD there is no bcm4329.hcd in my firmware folder lol. must edit code D:
pwnyourace said:
ive got it booting but still no wifi D:
edit: oh, well i guess that might be why XD there is no bcm4329.hcd in my firmware folder lol. must edit code D:
Click to expand...
Click to collapse
can u send me ur tree and vendor and common folder in pm?
JoelZ9614 said:
can u send me ur tree and vendor and common folder in pm?
Click to expand...
Click to collapse
actually..thats not necessary, i thought theyd have fixed it but i just had to do it to make it boot. pm me ur updater-script
pwnyourace said:
actually..thats not necessary, i thought theyd have fixed it but i just had to do it to make it boot. pm me ur updater-script
Click to expand...
Click to collapse
well wifi might be because some devices are using bcmdhd.ko.....idk though
JoelZ9614 said:
well wifi might be because some devices are using bcmdhd.ko.....idk though
Click to expand...
Click to collapse
i think i got it for real this time lol.
$(call inherit-product-if-exists, hardware/broadcom/wlan/bcmdhd/firmware/bcm4329/device-bcm.mk)
wasnt in the shooter.mk, so i wasnt getting fw_bcm4329.bin and fw_bcm4329_apsta.bin in my system/vendor/firmware folder. compiling now and seeing what happens. #fingerscrossed
pwnyourace said:
i think i got it for real this time lol.
$(call inherit-product-if-exists, hardware/broadcom/wlan/bcmdhd/firmware/bcm4329/device-bcm.mk)
wasnt in the shooter.mk, so i wasnt getting fw_bcm4329.bin and fw_bcm4329_apsta.bin in my system/vendor/firmware folder. compiling now and seeing what happens. #fingerscrossed
Click to expand...
Click to collapse
awesome...i just was trying to compile cm9 to get a working tree and vendor
for BAMF...now i need to merge cm commits into the frameworks base
Does anyone know of an AOKP build for the nook tablet 16g?
I ask because I like AOKP and in the current state of cm9 development it offers far more settings. If their isn't would it be as simple as compiling the source code with the 2.6 kernel.
It should work if it's working with CM9. The only thing is that it's more work to do and it's not really worth it when there is so much to fix with ICS right now.
Id try from source if I could get the device files and my aokp source would build. Maybe I'll try a quick port for fun.
No.
CM9 is the only ICS based rom in development. I don't know if there are any gingerbread versions of AOKP but if there is, someone could probably port it using the CM7 code.
Keithn said:
It should work if it's working with CM9. The only thing is that it's more work to do and it's not really worth it when there is so much to fix with ICS right now.
Id try from source if I could get the device files and my aokp source would build. Maybe I'll try a quick port for fun.
Click to expand...
Click to collapse
Hey, if you do end up compiling one, be sure to post it so we can try!
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
Oh I would love to see an open Kang of ICS, I've been testing CM9 and so far so good is stable but there are some things that need to be fixed for sure.
Sent from my NookTablet using xda premium
I'd love to be able to compile it but for some reason I cant get the source code to compile even an official device and it did work before so my pc is setup. I did do a quick port using the zips but have tons of force closes I need to figure out. I'll play around and see if I can get m5 to work. Obviously it will still have every issue that the current cm9 has.
And AOKP is only ICS
Keithn said:
I'd love to be able to compile it but for some reason I cant get the source code to compile even an official device and it did work before so my pc is setup. I did do a quick port using the zips but have tons of force closes I need to figure out. I'll play around and see if I can get m5 to work. Obviously it will still have every issue that the current cm9 has.
And AOKP is only ICS
Click to expand...
Click to collapse
You should make a thread in development so we can follow your progress/ maybe try and help. I'm excited for this rom because of the limitless customization!
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
I got it to boot just FC after FC lol
Keithn said:
I got it to boot just FC after FC lol
Click to expand...
Click to collapse
Well at list you made it boot, take it from there and keep it up. Good luck!
Sent from my SGH-I897 using xda premium
Got it to boot with no FCs however the screen thinks it's 90 degrees to the side yet the toutchpoints on the screen are accurate for the way its being held.
Port
I did a port of the Kindle Fires AOKP and got it to boot but after going back and flashing gapps it stopped booting past Cyanoboot.
I might try compiling in a Ubuntu vm later.
EDITKeithn do the app previews from the recent apps key look rotated?
I made a thread in general about It, its probably a better place to figure this out. My entire screen is 90° off not just the recent apps lol
Sent from my Nook Tablet using XDA
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.
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.