RIL requires us to figure out how to get the data to work on sense devices via the cdma lte radio driver. Now that the full binaries are open source for vzw galaxy nexus via aosp, could we not build a driver for our rezound? Just trying to think over here!
http://mobile.theverge.com/2012/7/1...project?utm_source=dlvr.it&utm_medium=twitter
The hardware is different therefore so would the drivers.
From what I've read, the RIL is as far as it can go until the ICS kernel source is released.
mjones73 said:
The hardware is different therefore so would the drivers.
From what I've read, the RIL is as far as it can go until the ICS kernel source is released.
Click to expand...
Click to collapse
Don't believe everything you read, protekk lied to us saying the RIL was fixed, saying all it needed was a kernel.
And when it came to proving it he just whinned and called us idiots
Chad has working 1x and calls go check his thread out
Sent from my ADR6425LVW using Tapatalk 2
superchilpil said:
Don't believe everything you read, protekk lied to us saying the RIL was fixed, saying all it needed was a kernel.
And when it came to proving it he just whinned and called us idiots
Chad has working 1x and calls go check his thread out
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
He's probably using the ril fix...
We need Chad to make the kernel because the ril fix we have now makes the pmem overflow(not enough alloted).
Because of this Chad is building a kernel ported from holiday and has to change the ril a little bit to fix it.
Hmm you're right, the RIL is the problem. All the devs just keep complaining and saying we need kernal source, clearly ril is the problem.
Sent from my ADR6425LVW using xda app-developers app
Reaper0294 said:
Hmm you're right, the RIL is the problem. All the devs just keep complaining and saying we need kernal source, clearly ril is the problem.
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Actually it's mostly users copying what protekk said if you pay attention.
I've only seen a few devs say they need kernel source, and they only said it will make it easier not suddenly fix all problems with ril like protekk implied
My point being protekk lied, get it?
Sent from my ADR6425LVW using Tapatalk 2
superchilpil said:
Actually it's mostly users copying what protekk said if you pay attention.
I've only seen a few devs say they need kernel source, and they only said it will make it easier not suddenly fix all problems with ril like protekk implied
My point being protekk lied, get it?
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
But he didn't lie. The kernel really needs more pmem. I have run the kernel and it keeps crashing and the log message says it needs more pmem
The Thunderbolt had source for ages...and it took forever for a stable MIUI port to be released because of the RIL. The RIL is not a part of the source code. To my understanding, it's "wired" into the libs, buildprop, framework, etc. In this case, ours is based off of Sense, not AOSP (if that makes any, well, sense.)
Like I said, to my understanding lol.
superchilpil said:
Actually it's mostly users copying what protekk said if you pay attention.
I've only seen a few devs say they need kernel source, and they only said it will make it easier not suddenly fix all problems with ril like protekk implied
My point being protekk lied, get it?
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Building a working kernel without source isn't impossibly difficult. It has been done on several devices, including the Rezound. The Anthrax GB kernel is not built from HTC source, for example.
The RIL, would be much harder to reverse engineer without HTC Source code, but again not totally impossible either, just nearly so... We don't need the kernel source, we need the Android source from them. This will contain the source for HTC's Sense implementation of RIL, and give developers the information they need to reverse engineer a working AOSP RIL.
a.mcdear said:
Building a working kernel without source isn't impossibly difficult. It has been done on several devices, including the Rezound. The Anthrax GB kernel is not built from HTC source, for example.
The RIL, would be much harder to reverse engineer without HTC Source code, but again not totally impossible either, just nearly so... We don't need the kernel source, we need the Android source from them. This will contain the source for HTC's Sense implementation of RIL, and give developers the information they need to reverse engineer a working AOSP RIL.
Click to expand...
Click to collapse
And oems don't usually release those proprietary drivers :/
Po1soNNN said:
And oems don't usually release those proprietary drivers :/
Click to expand...
Click to collapse
True. But its not really the drivers that we need. The drivers are actually included in the "radio" packages that come with new firmware updates. What RIL is, is basically the bit of software that lies in between the radio drivers and the Android OS API's and stuff.
In other words, we have working drivers for the radios. What we need is the part that allows Android to interface properly with those radio drivers. But these parts are also often proprietary as I understand it...
You guys need to check out chads thread... He seems to be getting close..said was able to get 1x data on cm
Sent from my ADR6425LVW using Tapatalk 2
Jmrwbilly said:
You guys need to check out chads thread... He seems to be getting close..said was able to get 1x data on cm
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Which thread? His Incredikernel thread in developement?
**edit** nevermind found it
Jmrwbilly said:
You guys need to check out chads thread... He seems to be getting close..said was able to get 1x data on cm
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Was mentioned already in this thread earlier.
Sent from my ADR6425LVW using xda app-developers app
Great, I was not aware of the progress. Please don't spam the poor guy. Lets keep our fingers crossed. Anything we can do to help should be brought up in this thread.
a.mcdear said:
Which thread? His Incredikernel thread in developement?
**edit** nevermind found it
Click to expand...
Click to collapse
Where you find it at? I got lost!
superchilpil said:
Actually it's mostly users copying what protekk said if you pay attention.
I've only seen a few devs say they need kernel source, and they only said it will make it easier not suddenly fix all problems with ril like protekk implied
My point being protekk lied, get it?
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Ok kernel has nothing to do with ril all it has is permissions for the radio (I'm not a kernel dev but I've been told this)
Sent from my Galaxy Nexus using xda app-developers app
xrintintin said:
RIL requires us to figure out how to get the data to work on sense devices via the cdma lte radio driver. Now that the full binaries are open source for vzw galaxy nexus via aosp, could we not build a driver for our rezound? Just trying to think over here!
http://mobile.theverge.com/2012/7/1...project?utm_source=dlvr.it&utm_medium=twitter
Click to expand...
Click to collapse
They're not open source theyre closed source but Verizon has provided the compiled binaries these websites need to get their info straight open source would mean they're uncompiled but we only have compiled binaries atm
Sent from my Galaxy Nexus using xda app-developers app
Po1soNNN said:
But he didn't lie. The kernel really needs more pmem. I have run the kernel and it keeps crashing and the log message says it needs more pmem
Click to expand...
Click to collapse
Omg get over it he lied lol even said on twitter that he didn't care anymore that Google I/o open his eyes chad already attempted to fix the pmem errors but as he said those errors are present even in stock roms he lied end of story
Sent from my Galaxy Nexus using xda app-developers app
a.mcdear said:
Which thread? His Incredikernel thread in developement?
**edit** nevermind found it
Click to expand...
Click to collapse
link?
Related
Obviously CM7 Development is not dead at this time. http://forum.xda-developers.com/showthread.php?t=1304881
No u should be working on reading a little. Mrinehart is working in his build in his spare time. He is a full time student. He has a device and several members test his work.
The other build (GSM) is under construction in HIS spare time. These things take lots of time. Be patient.they are being worked on.
Sent phrom my Mo-Pho
It's not dead...
Sent from my MB855 using xda premium
I believe the GSM Dev said himself he wouldn't support it as he wouldn't have time. So he's done what he can, I believe. And the CDMA one will be worked on again in probably a week or so. I think he had three weeks worth of school work that too priority.
xTMFxOffshore said:
I believe the GSM Dev said himself he wouldn't support it as he wouldn't have time. So he's done what he can, I believe. And the CDMA one will be worked on again in probably a week or so. I think he had three weeks worth of school work that too priority.
Click to expand...
Click to collapse
Ok, makes sense, was a little confusing with both ROMs getting quick updates and then dying off for a while.
I think the GSM build was based off the CDMA build and that was has been a long painful process to even get it booting.
xTMFxOffshore said:
I think the GSM build was based off the CDMA build and that was has been a long painful process to even get it booting.
Click to expand...
Click to collapse
I thought it was independent, as the CDMA build did not have CDMA actually working. BTW is there source code for the GSM build?
It may have been, I'm not totally sure. As for source code, You'd have to PM the Dev and ask. I have no idea on that.
It's on his github,
Lightsword1942 said:
I thought it was independent, as the CDMA build did not have CDMA actually working. BTW is there source code for the GSM build?
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
As far as progress goes, alcohol(not money) is required as development is a huge pain in the (edited for language). It's trial and error and some people just have magical powers that others don't. Cm7 is based on aosp, while motoblur is too, motorola makes there own stuff to get it to work. Then they make there special files/drivers depend on other stuff that's theirs. Some of these drivers/files have no source. Theres where the problem is.
Now the GSM cm7 is actually a kang, or cm7 with built in moto files. The reason cdma doesn't work is because it isn't called correctly, as the files necessary are part of blur. The the other cm7 is pure cm. It's a long tedious road for anyone attempting cm but once we have it upgrading will be easy. Personally I think more people should be helping. Pm the CDMA dev and ask how to build to his point, sync with his git, read up on the cm forums and try to help. Even if you only fix a small thing, submitting it back to him and it will bring cm faster.
As far as me, I plan to start helping soon after I redo my dev box(ran out of room) . I hope others will too.
Sent from my MB855 using XDA App
jokersax11 said:
As far as progress goes, alcohol(not money) is required as development is a huge pain in the (edited for language). It's trial and error and some people just have magical powers that others don't. Cm7 is based on aosp, while motoblur is too, motorola makes there own stuff to get it to work. Then they make there special files/drivers depend on other stuff that's theirs. Some of these drivers/files have no source. Theres where the problem is.
Now the GSM cm7 is actually a kang, or cm7 with built in moto files. The reason cdma doesn't work is because it isn't called correctly, as the files necessary are part of blur. The the other cm7 is pure cm. It's a long tedious road for anyone attempting cm but once we have it upgrading will be easy. Personally I think more people should be helping. Pm the CDMA dev and ask how to build to his point, sync with his git, read up on the cm forums and try to help. Even if you only fix a small thing, submitting it back to him and it will bring cm faster.
As far as me, I plan to start helping soon after I redo my dev box. I hope others will too.
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
Well, I found cybik's(GSM) source code (https://github.com/cybik/Sunfire) and have been playing around with building it. I'm not sure how much help I can be with it though.
its true, development work is best done between .13-.20 BAC
seeing as how we don't pay these people to bring us anything, we can't really expect them to work on this day and night. I'm sure CM will be done eventually, I have no doubts about that. As for how long it's going to take, i really don't care. I'll happily accept a "when it's done" ETA.
devilsshadow said:
seeing as how we don't pay these people to bring us anything, we can't really expect them to work on this day and night. I'm sure CM will be done eventually, I have no doubts about that. As for how long it's going to take, i really don't care. I'll happily accept a "when it's done" ETA.
Click to expand...
Click to collapse
Yeah, I am just trying to see if there is anything that is holding development up.
shabbypenguin said:
its true, development work is best done between .13-.20 BAC
Click to expand...
Click to collapse
Balmers peak?
Sent from my MB855 using xda premium
Kcarpenter said:
Balmers peak?
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
Beat me to it...
Sent from my MB855 using xda premium
Kcarpenter said:
Balmers peak?
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
relevant
http://xkcd.com/323/
It is dead
Sent from my MB855 using xda premium
LexLuger82 said:
It is dead
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
Why is it you are always so negative? Yet don't contribute anything but complaining. Just curious.
Sent from my MB855 using XDA App
xTMFxOffshore said:
Why is it you are always so negative? Yet don't contribute anything but complaining. Just curious.
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
lol pwnd..........
Hi guys since cm9 is community built i figure you guys might have some good ideas on how to fix things so i'm making this thread for brainstorming and any general discussion and questions
Using the CM port to try and attempt to port other things, and try to fix that instead
Sent from my HTC_Amaze_4G using Tapatalk 2
What are some phones that share the same chip set? We could possibly port fixes from that device to this device
Sent from my HTC_Amaze_4G using XDA
ziggy46 said:
What are some phones that share the same chip set? We could possibly port fixes from that device to this device
Sent from my HTC_Amaze_4G using XDA
Click to expand...
Click to collapse
Sensation
Evo 3D
Sent from my HTC_Amaze_4G using xda premium
sportsstar89 said:
Sensation
Evo 3D
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
If they use the same or similar hardware the fixes should just drop in. Check there commits ans see what they did to fix things like data and camera
Sent from my HTC_Amaze_4G using XDA
ziggy46 said:
If they use the same or similar hardware the fixes should just drop in. Check there commits ans see what they did to fix things like data and camera
Sent from my HTC_Amaze_4G using XDA
Click to expand...
Click to collapse
Same chipset doesn't mean same hardware the amaze is an oddball uses the ti wireless which the others don't
Sent from my HTC_Amaze_4G using xda premium
sportsstar89 said:
Same chipset doesn't mean same hardware the amaze is an oddball uses the ti wireless which the others don't
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
and im assuming you need that driver source correct? if so is there any way that you could make the source call for values from the pre-baked driver? ive heard of this being done before on another phone. they hacked around to get it to work with a gingerbread driver.
ziggy46 said:
and im assuming you need that driver source correct? if so is there any way that you could make the source call for values from the pre-baked driver? ive heard of this being done before on another phone. they hacked around to get it to work with a gingerbread driver.
Click to expand...
Click to collapse
That would include writing a wrapper which is extremely difficult and I don't know how to it requires a very in dept knowledge of which all the calls mean and how to translate what the new kernel is calling to the old driver
Sent from my HTC_Amaze_4G using xda premium
sportsstar89 said:
That would include writing a wrapper which is extremely difficult and I don't know how to it requires a very in dept knowledge of which all the calls mean and how to translate what the new kernel is calling to the old driver
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
i know one thing that might be worth doing... you could contact "mantera" over here about making a wrapper. cause im pretty sure they did that for the motorola triumph. (and that phone has no source)
http://androidforums.com/triumph-all-things-root/488824-dev-continuing-triumph-ics-development.html
i think he is even a member here on this forum too.
but yeah, he would be the one to ask about writing a wrapper.
doesnt the vivid have the same hardware? havent really checked the development over there recently but they have a sense 4.0 port almost fully functioning
Ignore
I'm convinced from a few logs I've seen since the ext.jar fix that the problem is the way it scans for data..
Doesn't the sensation have very similar hardware? Wouldn't their data fix be similar to what we need?
I am convinced that there is some very simple edit that is needed... and tho I hate suggesting it, data was the last issue to be resolved with all the gingerbread roms, has someone tried to contact x to see what the fix was he used for that?
Okay, so there are tons of files in the framework2.jar file that stock has needed for data in com/android/internal/telephony, and the same directory in CM9 framework.jar is missing many files compared to stock..
there is no framework2.jar for cm9, so I'm thinking that either we need to copy the files over that match from framework2.jar(Edit: no files match.. if i do whole directory I get UNEXPECTED TOP-LEVEL EXCEPTIONrg.jf.dexlib.Util.ExceptionWithContext: method index is too large.), or we need to try adding framework2.jar to the bootclasspath of the boot.img. The framework is supposed to be handling part of the data, but the cm9 framework is missing many files..
Basically, the stock rom has everything needed for data split between framework.jar and framework2.jar.. and for cm9/10 we need to recombine parts somehow- but the index for the classes.dex file is written when it is originally built..
Just some things to think about. Elements of framework need to be rebuilt from scratch with some missing files in com/android/internal/telephony contained in the classes.dex of the framework.jar
I don't know if this will help or not, but worth a try
http://processors.wiki.ti.com/index.php/TI-Android-ICS-PortingGuide
Sent from my HTC_Amaze_4G using xda app-developers app
Whether this means anything for us is yet to be seen but still cool to know
http://www.droid-life.com/2012/07/09/android-4-1-headed-to-aosp-today/
Won't mean much for this phone since it doesn't have a functioning AOSP RIL.
Yet.
Sent from my ADR6425LVW using xda app-developers app
Is anyone even working on the RIL still? I mean almost all the devs have left this phone.
zetsumeikuro said:
Is anyone even working on the RIL still? I mean almost all the devs have left this phone.
Click to expand...
Click to collapse
Dmeadows hasn't posted anything in so long I just consider this dead.
Sent from my ADR6425LVW using xda app-developers app
Check chads thread. He has it booting with calls and 1x working
Sent from my ADR6425LVW using Tapatalk 2
Damn, you beat me to it...
Is RIL version specific, or should it work for all versions of Android?
socal87 said:
Damn, you beat me to it...
Is RIL version specific, or should it work for all versions of Android?
Click to expand...
Click to collapse
Well if you mean towards jelly bean, yes and no. I don't think we can get aosp jb as their wont be a kernel for it. I think since JB is closely related to ICs versus the big difference between GB and ICS that it wont be as hard to go from one to the other
Correct me if I am wrong here. Trying to answer based on what I skim and read.
Sent from my ADR6425LVW using xda app-developers app
Actually yes, Chad is working on the kernel/RIL issue. I talked to Dmaedows on twitter informed him of it, it was the first he heard of Chad's working on it. Tweeted back later, it seems the two are going to work together, or at the very least Dmeadows is going to merge his fixes with Chad to make something useable.
But as always, remain cautiously optimistic, no promises.
http://www.twitlonger.com/show/i7dae2
I doubt we'll get a fully working JB port any time soon, few months at best.
Last I read on the ICS RIL was the kernel source was needed so we are stuck waiting for the update to be release and the source to be posted on HTC's dev site shortly afterwards...
No idea if that's truly the hold up, just something I saw awhile back.
guys yes rils are done. Currently waiting on kernel source to do anything.
Sent from my ADR6425LVW using Tapatalk 2
XRaptor29 said:
guys yes rils are done. Currently waiting on kernel source to do anything.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
No offence, but will believe it when i see it (and if i missed a genuine, validated announcement, my bad...)
nosympathy said:
Dmeadows hasn't posted anything in so long I just consider this dead.
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
You know what's sad and good in some way?
The development for this device is almost dead and the good old original Incredible is so active in development. This is just Incredible. Lol
Kratz17 said:
You know what's sad and good in some way?
The development for this device is almost dead and the good old original Incredible is so active in development. This is just Incredible. Lol
Click to expand...
Click to collapse
I noticed this too. My gf has been using my Inc and I went to flash a rom and saw a bunch of new Roms on there.
Sent from my ADR6425LVW using xda premium
chrisjz said:
I noticed this too. My gf has been using my Inc and I went to flash a rom and saw a bunch of new Roms on there.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Yeah is crazy bunch of roms people and development on the ogdinc I still have my dinc but I don't wanna leave my lte speed.
Divine_Madcat said:
No offence, but will believe it when i see it (and if i missed a genuine, validated announcement, my bad...)
Click to expand...
Click to collapse
Same
ReZound
Really looking forward to seeing Chad's work. I was going to sell my Rezound but I cracked the digitizer; so I'm keeping lol.
Sent from my Galaxy Nexus using Tapatalk 2
The og inc was one if the best phones..def. they didn't have a problem with ril because it wasn't a 4g phone
Sent from my Galaxy Nexus using Tapatalk 2
Developers only!!! Please no general discussion in this thread. Any comments / thanks etc can go over in the general section.
To build you will need:
android_frameworks_base
device_htc_vigor
vendor_htc_vigor
android_device_htc_msm8660-common
vigor_aosp_kernel
Place in the respective places in your AOSP branch of choice and build. In CM9 I have:
Working:
Radio
Wifi
GPS
G sensor/accelerometer
Compass
Vibration
Sound
Microphone
Light/prox sensor
USB mounting
Cameras
Not working:
Bluetooth headset
If you fix something please send a pull request back to me.
Good luck have fun
https://github.com/Chad0989
New build box fund:
Goal reached. Thanks everyone!!
What I ordered: AMD FX-8120 + 16GB DDR3 (2x 8GB) + cheap board + cheap graphics card
I will try to get the CM9 source to download (I have tried about 10 times w/o luck) and take a look at this! We all appreciate your hard work.
nice chad but question is their any specific commits i need from the frameworks_base? the ones u merged in i assume? the last 5
JoelZ9614 said:
nice chad but question is their any specific commits i need from the frameworks_base? the ones u merged in i assume? the last 5
Click to expand...
Click to collapse
Yes. I pulled in and based it on some JB stuff. Makes it easier in the future. HTCVigorQualcommRIL will probably disappear eventually. JB seems to have the right idea where radio stuff is headed by separating SIM states from radio states .
If someone has a lot of spare time to and a fast build machine It would be really great if you could go through the vendor files and figure out which prebuilt libs we can get rid of and build from source instead. I'm sure there's a ton of stuff in there that's not necessary.
chad0989 said:
If someone has a lot of spare time to and a fast build machine It would be really great if you could go through the vendor files and figure out which prebuilt libs we can get rid of and build from source instead. I'm sure there's a ton of stuff in there that's not necessary.
Click to expand...
Click to collapse
I'm gonna see if I can get this to build on AOKP... I'll need to merge the frameworks/base stuff first.
dmeadows013 said:
I'm gonna see if I can get this to build on AOKP... I'll need to merge the frameworks/base stuff first.
Click to expand...
Click to collapse
Repo sync took way too long... Building now...
Ok got a libcrypto error... Idk what the problem is... Gonna check with Roman
Edit: Roman says it's a problem with the recovery that koush edited for CM code. Trying to revert it
dmeadows013 said:
Ok got a libcrypto error... Idk what the problem is... Gonna check with Roman
Edit: Roman says it's a problem with the recovery that koush edited for CM code. Trying to revert it
Click to expand...
Click to collapse
Or you could use amon ra
Sent from my Kindle Fire using Tapatalk 2
pwned3 said:
Or you could use amon ra
Sent from my Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
No it's causing it to not build lol. I think I fixed it though...
dmeadows013 said:
No it's causing it to not build lol. I think I fixed it though...
Click to expand...
Click to collapse
So protekks loss of power doesnt affect you at all?
Btw, chad, does this use the gb wifi drivers since we don't have ics source?
Sent from my cm_tenderloin using Tapatalk 2
antp121 said:
So protekks loss of power doesnt affect you at all?
Btw, chad, does this use the gb wifi drivers since we don't have ics source?
Sent from my cm_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
Yeah he said it uses the old drivers until we get kernel source.
Sent from my Rez with fangs
i remember when we were in the age of cm7，most people thought the camera didnt work due to the kernel source，but a guy from China made some tweaks and then the camera worked，can anyone else recall this？maybe we can take that way
Sent from my ADR6425LVW using xda premium
Still working on AOKP but I tweeted a CM build
dmeadows013 said:
Still working on AOKP but here's a CM build http://www.androidfilehost.com/main...meadows013/cm-9-20120730-UNOFFICIAL-vigor.zip
Click to expand...
Click to collapse
This does NOT have gapps, correct?
Sent from my ADR6425LVW using Tapatalk 2
antp121 said:
This does NOT have gapps, correct?
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Correct. This should be the last post in this thread about it. Its a dev thread lol
dmeadows013 said:
Correct. This should be the last post in this thread about it. Its a dev thread lol
Click to expand...
Click to collapse
Ive booted up with CM9 and its so amazing. AMAZING work chad and dmeadows. I get Roaming Indicator On, but according to twitter you guys get that too. Wonder if thats normal?
Edit -
AOKP M6 from DMeadows here: http://t.co/5dyljWG1
The roaming indicator problem should be fixed now thanks to joelz
How long did the 4G dropout take? I have been running aokp for a little while now and using data like a mad man and haven't broke a strong 4G signal yet. No roaming issues either.
Sent from my PG86100 using Tapatalk 2
Downloading meadows cm9 now.
Edit: didn't mean to post this delete please.
Sent from my ADR6425LVW using xda app-developers app
Any chance of getting cm, maybe official so we can use the amazing cyandelta app.
Sent from my ADR6410LVW using xda app-developers app
playmobot said:
Any chance of getting cm, maybe official so we can use the amazing cyandelta app.
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
That requires either a CM guy to have our phone and decide to develop for it, or one of our amazing dev's to port it. Since we just got the ability to unlock the bootloader, It'll take a little while for things to ramp up. Baby steps.
Patgt500 said:
That requires either a CM guy to have our phone and decide to develop for it, or one of our amazing dev's to port it. Since we just got the ability to unlock the bootloader, It'll take a little while for things to ramp up. Baby steps.
Click to expand...
Click to collapse
How hard can it be to port CM?? I ask because I am considering attempting to do this over thanksgiving... I never ported CM before and I don't have much of an understanding of the Android Source code... But I can get my way around basic source code editing, if I have a lot of help... So, if someone can tell me how to start porting this thing, I may attempt to do so over thanksgiving.. but don't get your hopes up, I am just a novice dude here...
I think there are some porting guides on xda somewhere for cm9 try looking at those. Im willing to test builds by the way.
Sent from my ADR6410LVW using xda app-developers app
I would imagine it would be fairly difficult, the rezound took some time to get AOSP on it.
litetaker said:
How hard can it be to port CM?? I ask because I am considering attempting to do this over thanksgiving... I never ported CM before and I don't have much of an understanding of the Android Source code... But I can get my way around basic source code editing, if I have a lot of help... So, if someone can tell me how to start porting this thing, I may attempt to do so over thanksgiving.. but don't get your hopes up, I am just a novice dude here...
Click to expand...
Click to collapse
Ya gotta start somewhere. Good luck!
good luck my friend.
prepare for many sleepless, banging head against the wall - nights/mornings.
What Andy said lol. Also, look in the rez forums, there are a few developers there who have already encountered some of the issues you may and they may be able to help you (particularly Chad)
Sent from my ADR6410LVW using Xparent Blue Tapatalk 2
Hehe I have a Jellybean AOKP test build available. Tester needs S-ON bootloader unlocked. Not S-Off, cause I don't want to brick anyone. Also need to be able to get/send me a logcat of the build. PM me.
dmeadows013 said:
Hehe I have a Jellybean AOKP test build available. Tester needs S-ON bootloader unlocked. Not S-Off, cause I don't want to brick anyone. Also need to be able to get/send me a logcat of the build. PM me.
Click to expand...
Click to collapse
Well that was quick! You're a boss dmeadows. Post that shiz in development, I'd help but I'll be busy until Sunday night unfortunately
Sent from my ADR6410LVW using Xparent Blue Tapatalk 2
dmeadows you just made my night. No joke.
Sent from my ADR6410LVW using Tapatalk 2
dmeadows013 said:
Hehe I have a Jellybean AOKP test build available. Tester needs S-ON bootloader unlocked. Not S-Off, cause I don't want to brick anyone. Also need to be able to get/send me a logcat of the build. PM me.
Click to expand...
Click to collapse
Great job!!! I can test it but briefly tonight. Or after Sunday.
Sent from my ADR6410LVW using XDA Premium HD app
I Dont mind testing as well. Pm me if you need peepz
Sent from my ADR6410LVW using xda app-developers app
Is this still being worked on? It would be great to have it. Thanks.
Sent from my ADR6410LVW using xda app-developers app
+1 miss aosp
Linch89 said:
+1 miss aosp
Click to expand...
Click to collapse
dmeadows013 said something about a build being available but not quite sure if he was being serious or not. Anyway, I have a plan cooking up. I will download source and try to compile it, but fair warning I am a total newb to aosp deving and it may take forever, or never, to make a working AOSP build. I'm getting myself a new laptop which should help me build this thing. So far I put it off as my primary machine is tied up doing my regular work and with this spare laptop, I can do the hell I want while doing my regular work. Multitasking at its best!
Also, I really want to get some pointers on how to setup the build for a new device. I know that if all we are trying to do is build for a device that is already supported, then you already have the necessary files to compile it for that device. But, what I don't know is how to set up the build environment for a new device. Someone with some know how will be greatly appreciated. Thanks!
litetaker said:
dmeadows013 said something about a build being available but not quite sure if he was being serious or not. Anyway, I have a plan cooking up. I will download source and try to compile it, but fair warning I am a total newb to aosp deving and it may take forever, or never, to make a working AOSP build. I'm getting myself a new laptop which should help me build this thing. So far I put it off as my primary machine is tied up doing my regular work and with this spare laptop, I can do the hell I want while doing my regular work. Multitasking at its best!
Also, I really want to get some pointers on how to setup the build for a new device. I know that if all we are trying to do is build for a device that is already supported, then you already have the necessary files to compile it for that device. But, what I don't know is how to set up the build environment for a new device. Someone with some know how will be greatly appreciated. Thanks!
Click to expand...
Click to collapse
I would talk to dmeandows, I tested a few builds for him that didn't boot up
you want CM, get a phone to AREOEVAN. he's the one that can do it.
Aldo101t said:
you want CM, get a phone to AREOEVAN. he's the one that can do it.
Click to expand...
Click to collapse
this is true, we should start a bounty thread for him to get aphone
Yesssssssssss let's get Evan's ass over here