Database Users

[Q] Android 2.3 Gingerbread for HTC Buzz/Wildfire ???

Just wondering, but since Gingerbread is out now: I would love to know if:
a) it can be configured to run on the Wildfire?
b) how/who/when can do it, to make it happen?
c) if there are plans to build cyanogen mod on Gingerbread
Thanks and looking forward to it

You'll have to wait a few weeks as it hasn't been put on AOSP yet meaning the source isn't available. You might see a port of the emulator image on the nexus one as that has been done before with froyo. Once we have source it should(afaik) be a case of modifying the vendors that adeadrat and Jacob are using now to accommodate for the new build.prop etc.

seamon said:
just wondering, but since gingerbread is out now: I would love to know if:
A) it can be configured to run on the wildfire?
B) how/who/when can do it, to make it happen?
C) if there are plans to build cyanogen mod on gingerbread
thanks and looking forward to it
Click to expand...
Click to collapse
everything you're asking is already answered
ben1066 said:
you'll have to wait a few weeks as it hasn't been put on aosp yet meaning the source isn't available. You might see a port of the emulator image on the nexus one as that has been done before with froyo. Once we have source it should(afaik) be a case of modifying the vendors that adeadrat and jacob are using now to accommodate for the new build.prop etc.
Click to expand...
Click to collapse
there's no point answering people who's flooding this developement forum

warm welcome ...
Sympnotic said:
everything you're asking is already answered
there's no point answering people who's flooding this developement forum
Click to expand...
Click to collapse
well: I guess that wasn't the warmest possible welcome into the developing world. Hope for you guys that it's not all too rough out there ... I really have fun trying out the different custom ROMs that there are. I would even report bugs, as that's about the only thing I could contribute ...
still am excited to see how the work in Gingerbread for Wildfire is going, since I suspect it will be the last major release that can be run on the wildfire.
PS: This thread may not be completely lost if some folks who are into developing post any announcements on Gingerbread for Wildfire here ...
... have a happy Gingerbread Season!

http://www.youtube.com/watch?v=e6blPgPp9OM

Im guessing nothing further than screen is working atm?

ben1066 said:
Im guessing nothing further than screen is working atm?
Click to expand...
Click to collapse
screen and buttons
testing a new build now with potential fix to allow me to make calls etc.

seamon said:
well: I guess that wasn't the warmest possible welcome into the developing world. Hope for you guys that it's not all too rough out there ... I really have fun trying out the different custom ROMs that there are. I would even report bugs, as that's about the only thing I could contribute ...
still am excited to see how the work in Gingerbread for Wildfire is going, since I suspect it will be the last major release that can be run on the wildfire.
PS: This thread may not be completely lost if some folks who are into developing post any announcements on Gingerbread for Wildfire here ...
... have a happy Gingerbread Season!
Click to expand...
Click to collapse
This topic perfectly answers your questions : [Q]Gingerbread for Wildfire?
I'm not saying anything against you, and you're a new comer, the least would have been to read some topics.

Damn you already ported the gingerbread?! Nice work, How is it? Does it run smoother then 2.1/2.2 or is gingerbread more for tablets then this budget phone.

HCDR.Jacob said:
screen and buttons
testing a new build now with potential fix to allow me to make calls etc.
Click to expand...
Click to collapse
What features do you want functional before release, calls, wifi?

I know it is a bit much but is there any chance we will hame a cyanogen rc3 built on 2.3?
Sent from my HTC Wildfire using XDA App

Jesus, guys. Give him some time.
Good stuff Jacob, hope you get it up and running.

Amazing. Looking forward to it Jacob! =D

good work guys... please refine this rom and make the wildfire a great purchase for all people as it is a great little phone..
Also i don't know if this could be done but can something be done in regards to the resolution of the wildfire... please lol or is there a replacement screen for the wildfire? ......cause i really would like to get another screen and if anyone knows where that would be great.

I only know for the resolution of the wildfire, that there is a pixel density changer (I have no idea if this is any good, but you could look into it if you really want to change it)

Quick update from HCDRJacob (You remember me, right?)

Where I currently stand on the Huawei U8800:
So, I first got the U8800 a good number of months ago. I loved the device and started working on it straight away, made some good progress. Then I got lower AS Level results than I was hoping for. And my parents decided to split up. So basically, I needed to work harder at school, and my life was kind of a bit more hectic. I have still been working on the U8800, and I almost got CM7 finished. The only issue was that I had no camera preview (I was building libcamera from source rather than using prebuilt libs). A lot of hard work was put into it, and I can't take all the credit. Tom Giordano (Tom_G), bukington, dzo and stockwell were all helpful through the process (although contrary to popular belief I didn't just copy dzo and stockwell, I implemented things in different ways which I thought were cleaner). I respect all of the other developers despite any misunderstandings in the past. This brings me to where I stand today.
For the last few months, I've still been working on CM7 when I've had time to try and get it ready for 7.2, although that hasn't been often. Trying to fix the camera preview proved to be quite a hard process that resulted in me wanting to kill the phone on several occasions. I never succeeded. While I was doing this, Tom_G was working on CM9 for the ZTE Blade and bukington has been doing some great work on CM9 for the U8800. I've now realised that the port won't be ready for 7.2 and I am therefore abandoning it. THIS DOES NOT MEAN I AM ABANDONING THE U8800 OR CYANOGENMOD FOR IT. I am going to focus my efforts on working with bukington to get CM9 working on it. He has already done a lot of the work and it's looking promising. I will spend as much time as I can on it, but I need quite high grades to get to the University I want to be in, so I am aware that most of my time will still have to be devoted to school.
I am sorry to anyone who I have disappointed with this device, but time really isn't something I've had a lot of in the past 6 or 7 months.

Can or you know how to create a kernel that can fix the problem of the atmel screens on the 2.3.5 roms, and I don't know if you understand what iam speaking about.
Sent from my u8800 using XDA App

vlc_marcos said:
Can or you know how to create a kernel that can fix the problem of the atmel screens on the 2.3.5 roms, and I don't know if you understand what iam speaking about.
Sent from my u8800 using XDA App
Click to expand...
Click to collapse
I don't know what the problem even is. I'd love to help with it but I'd rather focus on ICS work than kernels for gingerbread. My time is limited now unfortunately.

Ao you are planning to use the 3.0 kernel for the ics version? Because on the 4.0 rim from dzo his kernel is a 2.3.5 version
Sent from my u8800 using XDA App

I have followed you on twitter. Sad things happen
Sent from my Derp using XDA Herp

I saw your post on your G+. I hope you can finish your work soon and get the high grades for the university that you want to be in
Sent from my U8800 using Tapatalk
-sorry for my bad english

Good stuff mate, have seen your updates on buckingtons github. Thanks for all the work and not to sound like an old fart, but good on you for keeping your priorities in order. Personal life and uni is a lot more important than a phone.
If it is all good to let us know, how is Buckingtons ICS port coming along?

Did anybody knows where to find HCDR.JACOB ???? I NEED TO TALK TO HIM.
Sent from my HTC Wildfire using xda app-developers app

sachoosaini said:
Did anybody knows where to find HCDR.JACOB ???? I NEED TO TALK TO HIM.
Sent from my HTC Wildfire using xda app-developers app
Click to expand...
Click to collapse
His Twitter: https://twitter.com/HCDRJacob

Why Atrix developers doesn't seem like to dev directly from ICS AOSP?

Usually, (for other devices of course), ICS roms that are developed from AOSP tend to be more stable, less buggy and better than CM9 roms, so im kind of curious why Atrix developers have decided to work on CM9, even thought its far from complete?
Just a question.

djluis48 said:
Usually, (for other devices of course), ICS roms that are developed from AOSP tend to be more stable, less buggy and better than CM9 roms, so im kind of curious why Atrix developers have decided to work on CM9, even thought its far from complete?
Just a question.
Click to expand...
Click to collapse
because CM9 is what we all want in the end.

djluis48 said:
Usually, (for other devices of course), ICS roms that are developed from AOSP tend to be more stable, less buggy and better than CM9 roms, so im kind of curious why Atrix developers have decided to work on CM9, even thought its far from complete?
Just a question.
Click to expand...
Click to collapse
I'm not 100% but I think the developers need something from the moto/nvidia which is why the rom was ported from the photon and not just built From the ground up .
Again not 100%
Sent from the Atrix of Chuck Norris.

djluis48 said:
Usually, (for other devices of course), ICS roms that are developed from AOSP tend to be more stable, less buggy and better than CM9 roms, so im kind of curious why Atrix developers have decided to work on CM9, even thought its far from complete?
Just a question.
Click to expand...
Click to collapse
NVidia won't release the drivers and sources required to accomplish this, so a 1/2 ass port is all that can be done at the moment. This has nothing to do with the devs. They are giving us the best they can with what they have right now.

djluis48 said:
Usually, (for other devices of course), ICS roms that are developed from AOSP tend to be more stable, less buggy and better than CM9 roms, so im kind of curious why Atrix developers have decided to work on CM9, even thought its far from complete?
Just a question.
Click to expand...
Click to collapse
Please open eyes before posting. Development are working hard and doing what they can.
Sent from my MB860 using xda premium

JayRolla said:
Please open eyes before posting. Development are working hard and doing what they can.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Not saying that they arent working hard, just asking why they choosing CM9 instead of AOSP 4.0, just a simple question. And ponting out that builds based on AOSP seems to be more solid and stable than builds based on CM9, mostly because CM9 itself its still not from complete
Sent from my MB860 using XDA

Also, IIRC, they're borrowing heavily from CM7 for our current CM9 builds. I believe we'll see more options when we finally get official source and drivers in Q3.
Sent from my MB860 using xda premium

CaelanT said:
NVidia won't release the drivers and sources required to accomplish this, so a 1/2 ass port is all that can be done at the moment. This has nothing to do with the devs. They are giving us the best they can with what they have right now.
Click to expand...
Click to collapse
Please read the above before commenting again! If you had read it the first time you would not have posted what you did below!.............Or maybe you still would have, who knows!!! You can program all you want for an AOSP ROM, but without device specific drivers you can never optimize for any one device. Simple as this, for any ICS on the Atrix, whether AOSP, CM9, MIUI, or whatever, you still need device drivers. Try running your NVidia graphics card in your computer without a driver................yeah, see what I mean (but then again you might like 640 x 480!)!
djluis48 said:
Not saying that they arent working hard, just asking why they choosing CM9 instead of AOSP 4.0, just a simple question. And ponting out that builds based on AOSP seems to be more solid and stable than builds based on CM9, mostly because CM9 itself its still not from complete
Sent from my MB860 using XDA
Click to expand...
Click to collapse
BTW...........Please link the AOSP 4.0 builds for the Atrix you are referring to!

CaelanT said:
Please read the above before commenting again! If you had read it the first time you would not have posted what you did below!.............Or maybe you still would have, who knows!!! You can program all you want for an AOSP ROM, but without device specific drivers you can never optimize for any one device. Simple as this, for any ICS on the Atrix, whether AOSP, CM9, MIUI, or whatever, you still need device drivers. Try running your NVidia graphics card in your computer without a driver................yeah, see what I mean (but then again you might like 640 x 480!)!
BTW...........Please link the AOSP 4.0 builds for the Atrix you are referring to!
Click to expand...
Click to collapse
You're rude.

Purple Drama Llama said:
You're rude.
Click to expand...
Click to collapse
No! I already answered the question earlier in the thread, but OP obviously is not reading and persists.
Both my posts were quite nice actually!
Bye!
BTW, why no comment about this post being rude?:
JayRolla said:
Please open eyes before posting. Development are working hard and doing what they can.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse

CaelanT said:
BTW...........Please link the AOSP 4.0 builds for the Atrix you are referring to![/B]
Click to expand...
Click to collapse
Woops, i forgot to tell that i was refering to other devices AOSP 4.0 ROMS, but if you are as inteligent as you seems to be, you should have known that because the Atrix actually doesn't have any rom coded from AOPS 4.0, at least on this forum.
The roms i was refering to was ICS Passion and ICS Euforia, both made by the same developer, Neobuddy, made for the Samsung Vibrant, a 1ghz phone, with 512mb for ram, without official drivrrs released, and the rom is more stable than the current Atrix ICS builds (no offend, i recongnize the guys are doing a great job making it happen), and almost as smooth as a the builds, and that phone is in a similar condition driver-related, that its, without any drivers being released. Thats why my doubt came, why the developers chiosed CM9 as a base, even thought it isnt really stable yet, and not completed, and why builds made from AOSP 4.0 tend to be more stable?
Sent from my MB860 using XDA

djluis48 said:
Woops, i forgot to tell that i was refering to other devices AOSP 4.0 ROMS, but if you are as inteligent as you seems to be, you should have known that because the Atrix actually doesn't have any rom coded from AOPS 4.0, at least on this forum.
Click to expand...
Click to collapse
And that's why I asked you to link them. You are comparing AOSP ROM's on other devices to CM9 on other devices. Because you see something run more smoothly on one device, does not directly mean it will run smoothly on another device. In any event, your question was answered in as far as there are drivers and source that the devs do not have in order to make any ICS based ROM's work optimally on the Atrix. If I had to hazard a guess as to why the devs are using CM9 as a base, it would be because the groundwork has been laid for them. The Atrix doesn't have an army of devs, so we get a smaller mix of options with ROM's.

CaelanT said:
And that's why I asked you to link them. You are comparing AOSP ROM's on other devices to CM9 on other devices. Because you see something run more smoothly on one device, does not directly mean it will run smoothly on another device. In any event, your question was answered in as far as there are drivers and source that the devs do not have in order to make any ICS based ROM's work optimally on the Atrix. If I had to hazard a guess as to why the devs are using CM9 as a base, it would be because the groundwork has been laid for them. The Atrix doesn't have an army of devs, so we get a smaller mix of options with ROM's.
Click to expand...
Click to collapse
The OP was asking why the Atrix doesn't have AOSP ROM's.. so you.. ask him to link them?
I've been lurking around the forums since the release of this phone and you have got to be one of my favorite posters so far, give me a good laugh every time.
Sent from my MB860 using xda premium

Celidonius said:
The OP was asking why the Atrix doesn't have AOSP ROM's.. so you.. ask him to link them?
I've been lurking around the forums since the release of this phone and you have got to be one of my favorite posters so far, give me a good laugh every time.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
I wrote something about that yesterday but in the mist of trying to add a pic xda app fc'd.
+1
Sent from my MB860 using xda premium

I kind of think I get what the OP is asking. He's asking why build a really souped up race car where as a regular car is just as fine. Seems like he's not picky and he would be content with anything stable vs anything available now. But that's another thread isn't it?
Sent from my MB860 using XDA

Idea for 3.x Kernel

hello,
i posted it in the ICS update thread:
Hey, silly question, i know, think it would be asked many times.
i wanne opend a new thread at dev, but i cant't to less comments --_--
now, we know, we never get a 3.X kernel from moto, so, we must help us at our own, i asked me, how?
my idea was, what abei the LG P990, i heard, there are 3.x kernel, no officiel, i know.
What are the hardware differences at the LG and the atrix? fingerprint and camera, i know, but what about the rest?
it it identicly? is it possible, that we can work with it? at beginning, without camera and fingerprint?
perhaps we found an other device with an identicly camera and 3.x kernel, perhaps we can look in a direction like that? only moto bashing wont help anyway
Click to expand...
Click to collapse
i hope any dev get give informations to me?

the developers already know that moto left us behind..
they're talking about it and what they are going to do??..just the time will tell us...we have to wait hehe
I'm not a developer but sometimes i asked then about start the work from some other similar device's kernel (same that you're suggesting here)..they told that it's an idea but should be necessary a massive rewriting...so it's not easy and they will need time even if the device is similar..

thats the point, i think we don't have any other chance, similar devices kernel, or from scratch, the second is the option which needs more time, i think
i wanne call me a developer, nothing in comparsion with our big ones but i would like to help your devs and i think, i'm not the only one, but i don't know how - i know that is many work and needs massive rewriting, but it's our only option.
i only hope some devs would found together and can say, how we, the, i wanne call it "non-kernel-hackers" , can help.

sw0pt5 said:
Why Defy can use Froyo kernel for CM9?
Why Defy can use GB kernel for CM10?
Why Defy bootloader is locked but still have a better development?
Defy also only have GB, no ICS
Click to expand...
Click to collapse
I'm not sure if you noticed but the defy and the atrix are two very different phones.
Sent from my MB860 using xda app-developers app

sw0pt5 said:
And two group of devs
but using same kind of OS
Click to expand...
Click to collapse
Its not as simple as that. Each device is different regardless of the OS. If you think our devs aren't good enough or they aren't trying hard enough then I'm sure you know exactly how to do it so just try yourself .
Sent from my MB860 using xda app-developers app

I just ask quarx for help...
Quarx said:
Cocolopes said:
Hi quarx!
I want to ask you something...how you do to make hwa work on jb for defy?...I ask this because in atrix forum we are mad cos motorola **** us not releasen ICS...
So I think...in first time the problem on defy was the locked bootloader...but you get it work. Atrix has an unlocked bootloader..and we have Nvidia drivers...and I think there is a phone using the same tegra chip on a 2.x kernel...soooo its possible to make something?
If the answer is YES...and you know how to do it...maybe the atrix comunity can donate to you to buy an atrix...
Sorry for the bad english...and I wait for your answer..thank in advance!
from the (m)ATRIX...
Click to expand...
Click to collapse
You need update EGL libs and kernel drvier for this libs.
Hwa should work automatically.
Click to expand...
Click to collapse
We have great devs working on atrix...the best ones....but we have no choice...we need help...so...
from the (m)ATRIX... no more moto!

I think atrix slowly died

sw0pt5 said:
Exactly!
Just hope someone can make a smooth CM7 with all the best tweats.
Actually, the stock ROM is quite reliable as daily driver.
Click to expand...
Click to collapse
+1
base gb on cm7 or miui

Thread moved to general and cleaned.
There will be no more flaming here.....

I know of a dev that might be able to help us, as he has made CM10 stable Kernels for many devices and might be able to help us. He goes by the name of Hashcode, I'd link to a profile but I'm on mobile at the moment x.x
Sent from my MB860 using xda premium

MewRai95 said:
I know of a dev that might be able to help us, as he has made CM10 stable Kernels for many devices and might be able to help us. He goes by the name of Hashcode, I'd link to a profile but I'm on mobile at the moment x.x
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Please. Any help would be appreciated.

MewRai95 said:
I know of a dev that might be able to help us, as he has made CM10 stable Kernels for many devices and might be able to help us. He goes by the name of Hashcode, I'd link to a profile but I'm on mobile at the moment x.x
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
http://forum.xda-developers.com/member.php?u=4243514

i worte a message to him, i hope he can help us
i'm glad, that this thread went to the direction i thought about at starting it

Anyway, i think that our best chances is to raise a found, by donating, and offer it as a bounty for the first dev to create a 3.x kernel for our device. We might find someone that way. Create that kernel takes lots of time and skills. Very very few people are willing to invest all the time required for free.

djluis48 said:
Anyway, i think that our best chances is to raise a found, by donating, and offer it as a bounty for the first dev to create a 3.x kernel for our device. We might find someone that way. Create that kernel takes lots of time and skills. Very very few people are willing to invest all the time required for free.
Click to expand...
Click to collapse
agree

Cocolopes said:
I just ask quarx for help...
We have great devs working on atrix...the best ones....but we have no choice...we need help...so...
from the (m)ATRIX... no more moto!
Click to expand...
Click to collapse
Got a response?

MewRai95 said:
I know of a dev that might be able to help us, as he has made CM10 stable Kernels for many devices and might be able to help us. He goes by the name of Hashcode, I'd link to a profile but I'm on mobile at the moment x.x
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
yes hashcode is awesome developer and he has got kexec working one the droid razr/razr maxxx, bionoic and droid 3 I think..

djluis48 said:
Got a response?
Click to expand...
Click to collapse
Yes...but I think he didnt have time to help us...
quarxs said:
You need update EGL libs and kernel drvier for this libs.
Hwa should work automatically.
Click to expand...
Click to collapse
from the (m)ATRIX...

I too have sent Hashcode a message asking for possible assistance. I told him we would be willing to donate to the cause.

If you can organise a decent fund/development device, I'd recommend contacting TripNRaVeR. He has experience porting the vanilla 3.1.10 Tegra kernel code to a new device (the One X, which shipped with 2.6.39) hence he's probably already halfway there with knowing where to go next. It looks like LG and Sammy have ditched DVFS in their 3.1.10 releases on the Galaxy R and O2X, which would be nice (using standard governors )

KitKat made for low end devices with 512MB

Hello,
XDA and other sites have broken news on new features in KitKat and one of them is that its made for wearable devices with as low as 512MB. Our Desire Z has 512MB so this will be great news Obviously our processor still lacks and GPU drivers are sticks and gum but something is better than nothing.

I was excited to hear this when I first read that about KitKat. I'm quite excited to see if anyone out there is gonna work on a ROM once everything needed to port it over is available.

fireball0093 said:
I was excited to hear this when I first read that about KitKat. I'm quite excited to see if anyone out there is gonna work on a ROM once everything needed to port it over is available.
Click to expand...
Click to collapse
The team at Cyanogenmod has commented that this wont mean a revivial of old devices since a lot of things (drivers) are needed besides RAM but needless to say in my opinion and seeing what Jelly Bean brought to the table, I think its a good sign of things to come.
Sadly, there are few really active developers on JB/Desire Z. Lets hope someone comes out with a KitKat ROM.

Speaking of KitKat, here is a lot of the stuff ripped from the Nexus 5 ROM, I personally have all of them running on CM10.1 Andromadous (I think that's the right spelling.) Hope it helps people! bit. ly /1arIQCU (via DroidLife)

I would be very surprised if Kit Kat is ported to this wonderful device. The fact that it has been ported anything beyond Ice Cream Sandwich is astonishing already, so whether they support Kit Kat or not I'd still be happy until a true hardware keyboard phone comes out.
Sent from my HTC Vision using xda app-developers app

I would be really happy to see KitKat ported over. I mean even if it isn't I'd be happy running either CM10.1 or the Gslim 1.6 ROMs, but I hope that since KitKat supports lower ram that it helps performance wise. I'm tempted to try and get into developing roms but I'm quite a newbie when it comes to that.

i hope that somebody make it for our device

I'm a newbie as well when it comes to development, but if i have the time and someone ports 4.4 to a similar device (desire HD perhaps) then i'll definitely attempt to port 4.4 to the g2. I love my old g2, when i had to send my GS3 back do to a defect in the screen I used my g2 for 2 weeks and was still impressed with how snappy it was. So yea, I may end up attempting a 4.4 rom at some point. I'll share it here and perhaps some of the better developers can take it and improve on it

DRSdroid said:
I'm a newbie as well when it comes to development, but if i have the time and someone ports 4.4 to a similar device (desire HD perhaps) then i'll definitely attempt to port 4.4 to the g2. I love my old g2, when i had to send my GS3 back do to a defect in the screen I used my g2 for 2 weeks and was still impressed with how snappy it was. So yea, I may end up attempting a 4.4 rom at some point. I'll share it here and perhaps some of the better developers can take it and improve on it
Click to expand...
Click to collapse
If you want a tester if you do attempt it, count me in. I'm looking into porting roms currently since I have a ton of free time

riahc3 said:
Our Desire Z has 512MB so this will be great news
Click to expand...
Click to collapse
Desire Z has 384MB of RAM. Rest is allocated for video memory.
But not sure if there is a way to strip the video memory or even have dynamic vram.

nex86 said:
Desire Z has 384MB of RAM. Rest is allocated for video memory.
But not sure if there is a way to strip the video memory or even have dynamic vram.
Click to expand...
Click to collapse
Still, seeing as how smooth CM10.1 is even on our device, shows pretty good promise for KitKat in my opinion

fireball0093 said:
Still, seeing as how smooth CM10.1 is even on our device, shows pretty good promise for KitKat in my opinion
Click to expand...
Click to collapse
I was think about trying that first !
What do you think?

Kéno40 said:
I was think about trying that first !
What do you think?
Click to expand...
Click to collapse
I think it's fantastic, once in a while I'll come across a small little hiccup, but that's expected personally for a port. I would make it my daily driver but I use Gslim as my daily rom only for battery life because not around my charger much, otherwise I'd be running CM10

fireball0093 said:
I think it's fantastic, once in a while I'll come across a small little hiccup, but that's expected personally for a port. I would make it my daily driver but I use Gslim as my daily rom only for battery life because not around my charger much, otherwise I'd be running CM10
Click to expand...
Click to collapse
I meant just trying to start with that, but it's far away from being so easy. I have no experience! and we need drivers!

Kéno40 said:
I meant just trying to start with that, but it's far away from being so easy. I have no experience! and we need drivers!
Click to expand...
Click to collapse
Oh oh oh, I understand what you meant now. I was still waking up when reading that, I'l use that as an excuse. I'm slowly teaching myself how to port over roms, I'm probably going to end up buying another secondhand G2/Desire Z as a test device so I don't bork the one that I use daily

cm11.0
I'm currently working on getting cm11.0 4.4 to build. I Had it built already and a new version of cwm recovery 6.0.2.8. The rom starts but there is no splash for the time being. Don't even have permission to view the log cat. Been working off of nevergone's stuff. What recovery version do you guys have?
For your guys proof
github - adknight87
I'll upload the new cwm-recovery image on dropbox if anyone wants to try it out lol.

adknight87 said:
I'm currently working on getting cm11.0 4.4 to build. I Had it built already and a new version of cwm recovery 6.0.2.8. The rom starts but there is no splash for the time being. Don't even have permission to view the log cat. Been working off of nevergone's stuff. What recovery version do you guys have?
For your guys proof
github - adknight87
I'll upload the new cwm-recovery image on dropbox if anyone wants to try it out lol.
Click to expand...
Click to collapse
I'm on cwm v5.0.2.7 currently. If you want a tester I'll help out

I have 4ext recovery latest..
And it works fine.
Sent from my HTC Vision using xda app-developers app

arunal_123 said:
I have 4ext recovery latest..
And it works fine.
Sent from my HTC Vision using xda app-developers app
Click to expand...
Click to collapse
I can't get it to build anymore for some reason and I lost all my work I still have the zip but it doesn't boot. But I got
https dl dropboxusercontent com/u/70782275/cwm-recovery-6.0.2.8.img
I can't post in the dev side of the xda here but where can I find the work gits for someone working on cm11.0 for this device I'm trying to get this thing to work again. Also is there a irc room for the group?
I figured the cwm version that built worked with the new set_metadata in the updater-scripts for the 4.3 and up

I would like to help with, (attempt to) coordinate, and start the development efforts for KitKat/CM11 on the G2.
I can beta test, build, and debug/reverse-engineer where needed.
I'm getting a build environment prepared, so it will be a bit until I crank out builds.