I made it for fun and it is NOT usable and will not be before we get official source
http://saraev.ca/signed_120810_223045.zip
working:
- data/radio (no incall microphone)
- wifi
not working: everything else
please do not report bugs. I know whats not working but can fix NOTHING for now
Good job. IMO these ports will be unusable for the next few months until cyanogen comes up with a release.
It was like that with eclair and later froyo. History tends to repeat itself.
Woot Woot, Hopefully once we get the source this can become stable. The magic lives on. Not many froyo builds I tried for the 32a werent that easy on battery life. Hopefully this turns out good. Hope the devs will work together to create a stable rom, instead of having their own builds with pros and cons.
If 2.3 ever starts working on 32A + NR, I am jumping ship asap! I miss vanilla android
eyegor said:
Good job. IMO these ports will be unusable for the next few months until cyanogen comes up with a release.
It was like that with eclair and later froyo. History tends to repeat itself.
Click to expand...
Click to collapse
There is no beginning no end. We are never be alone
HTC planning any updates in the future for "oldest" device? :/
eyegor said:
Good job. IMO these ports will be unusable for the next few months until cyanogen comes up with a release.
It was like that with eclair and later froyo. History tends to repeat itself.
Click to expand...
Click to collapse
I would have to agree with you except for I think I read on Cyanogen's twitter page that they will NOT be supporting first gen devices after CM6.1 which I assume meant NO ported 2.3 for us.
Hopefully I am wrong.
where is that quote? can't see it
good job!!!!!!!! hahahahaha
Did anyone1 tried on OR and cm Bcrook kernel???
i want to make a team for dev this rom to work full on magic..contact me..
nice hopefully it will fully work
Download does not work?
Really impressive work Hope to see this fully working.
what changes are needed for this to boot on 32b?
This is all well and good and I'll try it if I get my repaired phone back and can once again have a spare to play with.
However is it reasonable to expect this to ever be usable? We don't seem to be able to get a fully working 2.2 under the new radio so why would 2.3 ever get enough attention or drivers? I used 2.2 for a long time on the old radio but I really needed to use the new radio and have since gone back to 2.1 since it is now my daily driver again.
This will be great fun once I can put the Magic back to dev use.
I tested this on my g1, with a pershoots kernel over top so that it boots. And I was wondering how you got wifi to work? I tried replacing many things, but still get an error starting wifi supplicant daemon on logcat.
Just curious, not like I expect anything to ever become usable haha
studjuice said:
I tested this on my g1, with a pershoots kernel over top so that it boots. And I was wondering how you got wifi to work? I tried replacing many things, but still get an error starting wifi supplicant daemon on logcat.
Just curious, not like I expect anything to ever become usable haha
Click to expand...
Click to collapse
hm did you replace wlan.ko ? you should
also take a look at init.sapphire.rc:
Ive changed wpa_supplicant service a little because wlan_loader is not used as in eclair/froyo roms. my *wpa_supplicant.exec* loads the firmware and then starts *real* wpa_supplicant.
I realy dont have an idea whether firmware & tiwlan.ini are different for trout/sapphire. if they are you can edit wpa_supplicant.exec to load propper firmware files..
EDIT: this will not be usable untill we get gingerbrad sources published by google. then maybe cyanogen will do a build for us. I heard he will not support sapphire/trout anmore and if and *only if* it is true I will try to make a working one. I hope it isn't true and cyanogen will still suport our devices because he can do it better than me for sure
saibot64 said:
where is that quote? can't see it
Click to expand...
Click to collapse
twitter.com/cyanogen/statuses/8805829046177792
twitter.com/cyanogen/statuses/10393734621433856
*bump* any news, updates, anything?
found this
http://phandroid.com/2010/12/15/gingerbread-source-headed-to-aosp-soon-now-the-real-fun-begins/
Hopefully we can get a working build, dont wanna let the magic die.
Porting
Anyone done any work porting this? I'm currently working to compile this for my fender. Hopefully with the new radio. Which I've read doesn't work, so... anyone found a working one? I'm running eclipse to compile but if you'd like to help, let me know what you use and I'll send you what I've got.
Related
Alright so it's been a couple of weeks and anyone can see that the Nexus is casting a shadow over the new MyTouch so it's probably not going to get much attention from Cyanogen. We can still use his roms however we lose touchscreen support. Actually, we can use pretty much any rom as the old MT3G and G1 can use but we can't use the touchscreen.
What I've tried was pulling the /system/usr directory, flashing a CM rom and pushing the directory back but it still didn't make any difference.
I've tried flashing the Cyanogen ROM then flash the boot.img from the Fender ROM but I forgot that the current SPL (1.33.0013) is locked. Another obstacle. So I replaced the boot.img in the CM rom with the Fender and of course it didn't work. I'm out of ideas... but I'm far from being a dev. But there are a lot of you smart guys out there. Has anyone broken any ground on these devices? Now that the original MyTouch is obsolete it's only a matter of time that the popularity of this device will grow since the MyTouch (original) is more popular that the G1 to date.
In conclusion I see two options from here:
We cook a custom MT3G 1.2 ROM from source (whereever that could be found).
We work together to discover a workaround for this touchscreen issue to allow us to use CM ROMs (perferred).
So far the only ROM for the new MT3G 1.2/Fender is an odexed stock rom from http://forum.xda-developers.com/showthread.php?t=623141 (thanks CursorDroid) and the only method of rooting is by goldcard methoddiscovered by Crypysmoker.
If there are any others can you please post them.
I would really like to see the development for this device take off and I'm sure that it will eventually. Themes, kernal mods, custom roms, tethering, overclocking, a2sd, etc and I'm sure that I'm not alone.
Thanks.
I would love to see this phone get some attention. I call it my poor mans nexus
Has anyone tried adb pulling the touchscreen kernel module from stock and inserting it into a modded ROM to see if it even loads?
/system/lib/modules only has wlan.ko
It looks like the driver might be tied to the kernel so a new kernel is needed
robkoehler said:
I would love to see this phone get some attention. I call it my poor mans nexus
Click to expand...
Click to collapse
LMAO!! Even though I don't have one and don't intend to get one cause I'm satisfied with my original MyTouch, ROM development is always encouraged. the more ROMs, the better!
epeets said:
LMAO!! Even though I don't have one and don't intend to get one cause I'm satisfied with my original MyTouch, ROM development is always encouraged. the more ROMs, the better!
Click to expand...
Click to collapse
Unfortunately, the more ROMs the more confusion.
Now that we have two different MyTouch verions (not including the 32a/32b for the original) this is going to get VERY confusing. It already is. Even if you use "1.2" people are going to wonder if that's the ROM version or the phone version. Maybe MT3G2 or something.
tepic said:
Has anyone tried adb pulling the touchscreen kernel module from stock and inserting it into a modded ROM to see if it even loads?
/system/lib/modules only has wlan.ko
It looks like the driver might be tied to the kernel so a new kernel is needed
Click to expand...
Click to collapse
And thus we need a dev. LOL. Unless someone can tell us what controls the touchscreen input. That might give us a step in the right direction.
I'm still hoping for Cyanogen ROMs on the Mytouch 1.2.
Lol since im the one who even discovered the pain staking rooting process ... omg such a pain... I felt the need to comment.
I just today started using my fender over my G1 because Criffmon (however the hell you spell it) came out with the themed stock rom. It looks perfect.
But the reason for no rom yet is the kernel tied into the new touchscreen drivers and 3.5mm jack. There is a whole new touchscreen which is why it doesnt work when u load other roms.
Binary100100;5694320
So far the only ROM for the new MT3G 1.2/Fender is an odexed stock rom from [URL="http://forum.xda-developers.com/showthread.php?t=622530" said:
http://forum.xda-developers.com/showthread.php?t=623141[/URL] (thanks CursorDroid) and the only method of rooting is by goldcard method.
If there are any others can you please post them.
Click to expand...
Click to collapse
What bout this post though?
http://forum.xda-developers.com/showthread.php?t=623141
That's what I rooted my Fender with. (downgrading of course done with the link you provided)
crypysmoker said:
Lol since im the one who even discovered the pain staking rooting process ... omg such a pain... I felt the need to comment.
I just today started using my fender over my G1 because Criffmon (however the hell you spell it) came out with the themed stock rom. It looks perfect.
But the reason for no rom yet is the kernel tied into the new touchscreen drivers and 3.5mm jack. There is a whole new touchscreen which is why it doesnt work when u load other roms.
Click to expand...
Click to collapse
Of course. How rude of me. Sorry Crypysmoker. I'll update the op.
kbeezie said:
What bout this post though?
http://forum.xda-developers.com/showthread.php?t=623141
That's what I rooted my Fender with. (downgrading of course done with the link you provided)
Click to expand...
Click to collapse
Yeah that's the rom that I used too... maybe i got my links confused.
That rom is odexed. I managed to de-odex the apps but I can't figure out the framework. I would like to add things like the modified browsers, dialer, contacts, mms app, etc. But I am unsure if it can be done because of the odex.
Binary100100 said:
Yeah that's the rom that I used too... maybe i got my links confused.
That rom is odexed. I managed to de-odex the apps but I can't figure out the framework. I would like to add things like the modified browsers, dialer, contacts, mms app, etc. But I am unsure if it can be done because of the odex.
Click to expand...
Click to collapse
Ahh I see. (runs off to google 'odexed' )
crypysmoker said:
...I just today started using my fender over my G1 because Criffmon (however the hell you spell it) came out with the themed stock rom. It looks perfect...
Click to expand...
Click to collapse
Link please?
EDIT: ahh... did you mean this? http://forum.xda-developers.com/showpost.php?p=5665902
Binary100100 said:
Link please?
EDIT: ahh... did you mean this? http://forum.xda-developers.com/showpost.php?p=5665902
Click to expand...
Click to collapse
wow that looks sweet!!!...
So according to tmonews the MyTouch 1.2 is sold out and anyone interested will have to wait until this Spring to pick theirs up.
Then I noticed an interesting tweet from Haykuro:
"just realized something. The Nexus One and the N900 are amazing phones and a whole bunch of people have it but you NEVER see anyone with it."
So let's get this straight... the newest MyTouch is sold out and all of the devs (like Cyanogen) are rushing to develop firmware for a device that isn't anywhere near as popular. Meanwhile... what has been accomplished with the new MyTouch?
What's wrong with this picture???
Has anyone made any progress at all lately?
there's loads of things wrong with that. but sadly when your a gifted developer you have the right to develop for whatever device you want, even if loads of people won't be using it.
Aeikozz said:
there's loads of things wrong with that. but sadly when your a gifted developer you have the right to develop for whatever device you want, even if loads of people won't be using it.
Click to expand...
Click to collapse
I understand all that but my point is out of the hundred of thousands of devices sold there isn't ONE person out there that tried to develop a rom for it and share it? There are over two dozen people (at LEAST) in this forum that has the phone and not one of them possess the skills to at least figure out how to use a CM rom on the device? Really? Why is that so hard for me to believe?
I'm not saying that I can do better because I know that I can't... but I also don't have any coding experience either. It would appear that all the T-Mobile customers with coding experiences decided NOT to buy this device for some reason. Or they decided to buy it... but not try to improve on it in any way.
You know that if Haykuro or Cyanogen had the phone we'd be on the twelfth rom version by now. C'mon devs! I'm still using my G1 if I want to show off the power of Android. I want to retire this device already.
Binary100100 said:
I understand all that but my point is out of the hundred of thousands of devices sold there isn't ONE person out there that tried to develop a rom for it and share it? There are over two dozen people (at LEAST) in this forum that has the phone and not one of them possess the skills to at least figure out how to use a CM rom on the device? Really? Why is that so hard for me to believe?
I'm not saying that I can do better because I know that I can't... but I also don't have any coding experience either. It would appear that all the T-Mobile customers with coding experiences decided NOT to buy this device for some reason. Or they decided to buy it... but not try to improve on it in any way.
You know that if Haykuro or Cyanogen had the phone we'd be on the twelfth rom version by now. C'mon devs! I'm still using my G1 if I want to show off the power of Android. I want to retire this device already.
Click to expand...
Click to collapse
No no.. You have it a bit wrong. Wes and Ctso were/have been working on it trying to get the kernel into Open eclair.
The main problem is those 3 drivers we need for the touch screen and 3.5 jack seem to be a super pain in the ass to extract from the current kernel to push into another or build a new one all together. Basically, the drivers can be seen, but not used.
ALL 32a roms will boot on the fender/mytouch 1.2, I have tried literally 10 pages of them.... Bu the moment it looks for a touch screen, all it sees is the track ball and defaults to it. YOu can fully run other roms, but you cant touch. They are trying lol, But were basicly gona have to deal with criffmon's themes for now since 2.1 will be on us in the next few weeks. Supposedly, we are getting the full 2.1 since these are 32a boards.
People are trying, But think of this as a first, NEW release in a long while.
I mean hell, it took me 3 days just to figure out how to root it, when the nexus 1 took maybe a few hours with ways already known.
It will come, be patient. The moment I get a working kernel I will let everyone know.
Hey Crypysmoker!!! Thanks for all the hard work on this!
It's good to know there are people working on this device.
(taken from engadget)
Droid, Milestone, Eris, Moment, Spica, even the Hero, all have had their Eclair, one way or another. G1 and myTouch 3G? Not so much. But don't worry, Android early adopters, because Cyanogen's got your back. Most all the bells, whistles and hardware-accelerated graphics of Android 2.1 are coming to the HTC Dream, Magic and Sapphire in CyanogenMod 5.0.7, and you can see a video of a T-Mobile G1 running the new build after the break. Twitter buzz indicates the ROM will be out any minute now; the dev himself tweeted that it's ready to go and just needs G1-friendly bite size packaging.
There is video also.
Tried to submit with links but got "To prevent spam to the forums, new users are not permitted to post outside links in their messages. All new user accounts will be verified by moderators before this restriction is removed."
Got to engadget(dot)com to see.
engadget(dot)com/2010/04/29/cyanogen-ports-android-2-1-to-g1-and-mytouch-3g/
www(dot)youtube(dot)com/watch?v=3HVBVlAui3s&feature=player_embedded
Update: Don't stay up all night waiting -- Cyanogen says he's got "two more bugs to kill" and is "hoping for a test1 public beta tomorrow night."
Sweet this is really gonna annoy my bro xD he's been banging on about his nexus and how much it cost and how great 2.1 is
what about 32A?
this looks great!!!!...cannot wait for this to come out. I have tried some other various ports of the 2.1 they all seemed very choopy and needed alot more work... I am a very busy guy that needs stuff to work when I tap the screen to make it work, Cant wait around for things to happen....Cyanogen's build looks very smooth and responds very well....when will we know when it gets released?
For the latest news, including the release (which should be tonight according to cyanogen) you can keep an eye on twitter(DOT)com/cyanogen
I haven't really looked forward to the release of a ROM in a while. If what Cyanogen is saying in his Twitter is all correct (everything working with 2.1), then this one is the one.
xyrcncp said:
I haven't really looked forward to the release of a ROM in a while. If what Cyanogen is saying in his Twitter is all correct (everything working with 2.1), then this one is the one.
Click to expand...
Click to collapse
I totally agree with you on this one.....I was having a hard time putting the latest super D rom back onto my G1 after flashing one of the other 2.1 ports...so I am now currently running [ROM]TheOfficial DONUT TMO, ADP & AOSP (dream/magic)(EBI0/EBI1) [3/17/2010] -- v2.6.3 (which is also found here btw) with the Buuf theme...it is an alright ROM but this 2.1 port that Mr. Cyanogen released with help with other various "modders"....it looks great...flashin it as I am typing (YAY)
THANX TO ALL MODDERS INVOLVED WITH THIS BUILD
just a quick thought....i just finished flashing this rom to my G1 and I was thinking that it would be cool to add the nexus "X" boot screen that would cross over into the cyanogen symbol....would try to make it myself but I do not have the slightest clue on how to do that!!
Just to let everyone know the rom is up and running great. I got it on my mt3g 32B. Only thing is that the LED notification light is purple. Could anyone please tell me how to change it. thanks.
Does this work with the mytouch 1.2 with 3.5 jack? I am new to this and hoping to get some help. I just want to make sure I got this right.
1. Backup my phone. What do I use to do this?
2. Root my phone.
3. Flash phone with new rom.
If anyone could point me in the right direction on how to flash a phone I would appreciate it. Thanks
HyDrO84 said:
just a quick thought....i just finished flashing this rom to my G1 and I was thinking that it would be cool to add the nexus "X" boot screen that would cross over into the cyanogen symbol....would try to make it myself but I do not have the slightest clue on how to do that!!
Click to expand...
Click to collapse
yes i know that I am quoting one of my previous posts but....THIS ROM IS F-IN AWESOME
GREAT JOB MODDERS!!!!!
Hey XDA, this is my first rom its just a basic compile of AOSP, very slow and buggy at this stage i'm afraid, but figured you guys would want to see it in the flesh and hopefully i will be making it run alot quicker in the near future.
To install:
1) Wipe / Data / Cache
2) flash Pryon_Gingerbread.zip
3) flash 2708 kernel found here: http://droidbasement.com/g1/kernels/ram/2635/18/boot-cm_2635.9_ds_32b-oc-uv-xtra-ram-fp-121510.zip
4) Boot Gingerbread.
v.03 COMING SOON
12/21/2010 v.02
LINK :: http://www.4shared.com/file/HCuuugqE/pryon_gingerbread_v02.html
12/19/2010 (first release) v.01
:: Change log:: v.02
Added Gapps that doesn't crash rom
Added Busybox and Toolbox
Google Sync should be working now
Added Facebook
Slightly faster but still very buggy and not a daily rom.
WiFi Fixed also should work with mytouch now.
firsstt....to reserve for future commenting lol
well... if wifi and gapps were working..it mite b good for many to atleast download n try n bug reporting
I thought AOSP was suppose to be fast?
Working on WiFi now, bug reports would be good, although there's to many to count
2.2 AOSP seemed a whole lot faster then 2.3 but this is just a start and also this is the first time i have cooked a rom worth releasing so be patient please speed takes time + I'm new to all this
Can you please post some screen shots? and btw, have you fixed wi-fi in this build or are you planning on a ver .2 ? And yes, can I please have a list of what's actually working? I know its all too much to ask for but I guess these questions will help understand this AOSP for G1 more.
Thanks in advance
Compiling a new build now with jit and a few extras, also hopefully WiFi should be up and running, anyways will be a update tomorrow.
Dominating said:
Compiling a new build now with jit and a few extras, also hopefully WiFi should be up and running, anyways will be a update tomorrow.
Click to expand...
Click to collapse
You may be interested in:
http://forum.xda-developers.com/showpost.php?p=9930562&postcount=23
camera works .. (still a long list of other glaring issues thus why I have no binary)
oh cheers ezterry, syncing now i think i'm pretty close to camera built on my compile but I've always had trouble with the camera stub := false cammands.
Looking forward to future updates
........................10 char
Photos and benchmarks would be nice. I'm a flash-o-holic as it is, but I wanna start using my phone. Seems like every week I'm switching to another rom. So I'm sticking to what I got.
Dukenukemx said:
Photos and benchmarks would be nice. I'm a flash-o-holic as it is, but I wanna start using my phone. Seems like every week I'm switching to another rom. So I'm sticking to what I got.
Click to expand...
Click to collapse
Um dunno if you read the whole post, but bro said this ain't fast and is buggy, and to top it off he said he's new to this. Soo it can't really be a daily driver. I'm using that CM6 gingerbread mock up, which I like and its been fine for days on end, don't do much on it but I have the new radio w/ 15 or 14 ram hack, firerats aio-script, and new market, don't use data but use wifi, and I almost have half battery by the end of the day and that's about a good ten hours for me. Dunno what's good for you, but I recommend. But really use common sense and read the op. You can keep up on the progress or support the cause and help out and give a bug report
Sent from my HTC Dream
Today 0.2?
cctv35 said:
Today 0.2?
Click to expand...
Click to collapse
Hopefully
Although right now i'm not using the ROM i'm eager to see some progress
Does it work on Magic 32B too ?
I'm interested in this!
Btw how is the 3d working on your build ?
Sorry guys had a real busy day yesterday didn't get much done but before i head out christmas shopping i'll try and get the next release fixed wifi and hopefully some gapps will be included.
does this have the gingerbread screen off animation?
I know all you guys have been waiting for 2.3 on the vega well here it is its very raw and probably not good enough for every day use.The build is at the same stage as the gtab so it has all the same bugs and so on as the gtab plus a few more just for us lol :-D(as we don't have kernel source yet :-( ).
There will be little support if any for this build as i am currently working on a LOT of stuff. But when we get kernel source i can work some more on this
Please have the stock rom and nvflash ready in-case u have to recover from this :-D
Nither me or the cyanogenmod team are responsible for any damage caused by this rom weather that is bricking your device, eating babies, global warming or your house burning down !
ChangeLog[/B
B1
- Status Bar Buttons
- Newer CM src (due to issues with 2.3.3 not latest)
(WIPE DATA IF COMING FROM STOCK ROM)
B1
- Fixed Camera
- Fixed Rotation
- Latest CM source
[What Doesnt Work]
- Some GPS apps will FC (maps works but it needs to be version 5.0) the gtab has these same issues when they have a fix so will we
[What Does Work]
- Everything Else !
[Requirements]
- Advent Vega (ovb)
- ClockworkMod 2.x.x
[Install]
the normal way in clockworkmod :-D
[Download]
B2 HERE !
To enable camera
in adb shell / terminal app / gscript
ON = "echo 'set28h' > /proc/gpio"
OFF = "echo 'set28l' > /proc/gpio"
I suggest having the camera off when not in use as i haven't tested the affects of having it on for long periods of time are
[Credits]
- Bekit + sceptrr for the original gtab vendor setup
- CyanogenMod team for there awesome src
- Anyone else i missed
im so gona flash this. if its only camera, rotation and video decoding not working it seams usable to me. I just have to wait to friday maybe monday when my POV Mobii arrives. I got CM7 on my DHD. I also have an Archos70IT but no roms for that and a Toshiba Folio wich really is quiet nice. But it dosent have that strong community and rom devs around it. Then i saw that You had jumped on AdventVega and was going to make a CM7 build for it+ it has several other roms and rom builders working for it. So i orderd one. I really miss having an active community around the devices i got. Well the Desire HD is good, but the plates i got, when i check there forums almost never any activity. I hope people will tturn to Xda for the Vega not just Modaco.
I just your kernels for the DHD. Always good qquality work, thats promising for the CM7 for Vega.
PS. Download link for CM6 dont work, i only get error 404. Could you please upload a working link
I really need rotation to work before I can stick on one of these CM roms
However good news, kernel sources should be out today or tomorrow and Paul at modaco may already have it.
Nice one, I thought you'd abandoned this.
What is the point of releasing cm7 when you get cm6 to work properly for day to day use. I say waste of time.
Whats the point on working on 2.2 when 2.3 runs with the same buggs?
Apache14 said:
Whats the point on working on 2.2 when 2.3 runs with the same buggs?
Click to expand...
Click to collapse
I concur, plus CM7 has better features for our tablets than CM6.1 i.e. how to move apps2sd
It still doesn't make sense as both of them still buggy and not good for daily use.
lol the issue is the fix for sensors on 2.2 would fix 2.3 soo really 2.3 is thing to work at ... that and getting a solid vendor base so when 3.0 hits aosp we will be able to make best use of it .....
the main issue is nither 2.2 or 2.3 aosp have any real support for tegra 2 chips (hw decoding and other features) .... 3.0 aosp will do as there main device will be tegra based im hoping it wont be too much trouble getting 3.0 on this device
Apache14 said:
lol the issue is the fix for sensors on 2.2 would fix 2.3 soo really 2.3 is thing to work at ... that and getting a solid vendor base so when 3.0 hits aosp we will be able to make best use of it .....
the main issue is nither 2.2 or 2.3 aosp have any real support for tegra 2 chips (hw decoding and other features) .... 3.0 aosp will do as there main device will be tegra based im hoping it wont be too much trouble getting 3.0 on this device
Click to expand...
Click to collapse
Shouldn't be, and of course I will do all I can to help you or whoever decides to build it.
Fair enough. @apache14 I pm u some days ago did you get it.
Lennyuk said:
Shouldn't be, and of course I will do all I can to help you or whoever decides to build it.
Click to expand...
Click to collapse
nice :-D I will be .... im hoping to become the maintainer for vega on CM git (also need to get the vega into RaiderX's hands )
alphaola said:
Fair enough. @apache14 I pm u some days ago did you get it.
Click to expand...
Click to collapse
Oh did u ? i didnt see ill look for it in a bit mate
Apache14 said:
nice :-D I will be .... im hoping to become the maintainer for vega on CM git (also need to get the vega into RaiderX's hands )
Oh did u ? i didnt see ill look for it in a bit mate
Click to expand...
Click to collapse
Well if enough people donate to Raider he will soon have enough ££ to get one.
Nice work, Apache14!
Also, the kernel source is being released by Advent tomorrow.
http://twitter.com/adventvega
This rom is working awesome for me so far.
Installed the gapps from here http://goo-inside.me/google-apps/
Thanks bumbledroid.
Is this useful? -> http://forum.xda-developers.com/showthread.php?t=912197
@apache14, you didn't get back to me about the pm.I guess you choosed to ignore me. Cheers
alphaola said:
@apache14, you didn't get back to me about the pm.I guess you choosed to ignore me. Cheers
Click to expand...
Click to collapse
If apache14 didn't reply to you about the pm, then why would apache14 reply to you about this?
Also, apache14 will now probably ignore you, because you are too impatient, and don't realise that he/she may have other, more important things to do...
HunteronX said:
If apache14 didn't reply to you about the pm, then why would apache14 reply to you about this?
Also, apache14 will now probably ignore you, because you are too impatient, and don't realise that he/she may have other, more important things to do...
Click to expand...
Click to collapse
Or maybe his just arrogant ass that thinks he knows it all and can't acknowledge just a question. And its quite nosey to respond to someone's question especially when it specifically directed to someone [email protected], you don't know what the pm is about.so y unsolicited response.
I know you go on about its a forum and blah blah,am sure etiquette ring a bell to you.
Source code released - http://androidcommunity.com/advent-vega-source-code-v1-08-released-20110128/
This is good news, no?
I'll keep this post upto date with the last on the status of the build.
I've updated the manifest and it's inline with cm10. https://github.com/TeamICS/manifest_ics_cm/tree/jellybean
Builds are located here.
Nightlies are here or here
If you are not using firerats or don't know what that is make sure you use one of the "_shrunk" nightlies.
Currently the room boots. Lots of things work, here is what doesn't:
Bluetooth (pairing)
HW Acceleration (not likely)
Anything missing from CM10
Known issues are:
Headphone + speaker plays when headphones are in
<--previous-->
IT LIVES!
The build doesn't flash, but it successfully built. You need to use firerats as the system partition is over 173mb by itself. Not sure of optimal settings as it doesn't flash but we're getting closer.
Complete repo diff and repo status is here:
https://gist.github.com/3095432
Things disabled at build:
audioinwrapper from srec
libaac/libFDK
compiler-rt
maybe others.
Please note I haven't cleaned anything so it's quite messy and some stuff isn't pushed up to the repos yet. However it builds and that's a big step. It's off to bed and work tomorrow so I won't get a chance to work on it until the evening/friday.
Very close to a build, libaac is the only blocker, I've reached out to cyanogenmod guys to see if they have any ideas to fix aac, without completely rewritting the asm code. The problem is armv6j doesn't support smmul, clz and others in thumb mode, but armv7 (and the few devices with thumb2 on armv6t2) do. I don't have enough experience with arm asm to figure out how to rework the code to convert from 32 bit operations to 16bit operations. Also valgrind is not supported in armv6 (and can't be) so its disabled.
problems building aac, due to asm code, currently disabled a blocker
problems building srec due to audio issue, disabled
haven't ported camera
So far there is only two show stoppers, first is the audio because its changed again slightly. Shouldn't be too hard to work around. Second is cm team is still porting over all armv6 patches. Building on armv5 get stuck at audio, but armv6 get stuck on some asm code in bionic.[/sstrike] aac. AAC is being a really PITA!
<--Original Post-->
So I'm sure some of you guys are watching the I/O live. For those that aren't it's offical Jellybean will be 4.1. It's got loads of new and nice features. A lot of performance upgrades and the most important thing is the annoucement of the platform development kit. It's got all the low level details and apis need to port hardware to android.
Source code will be released in mid july, which is when the real development starts.
The hardwork everyone did on ICS, jaybob, matt, evervolv team and everyone from the G1, hero and eris forums laid the foundation. The main issue that has always held the heroc back has been the drivers. We have a great .35 kernel but with ICS a lot of the framework, that is hardware <-> software interactions changed. Thats what our audio issue was at first, and the camera. Audio was fixed by porting gingerbread patches and legacy audio support. The camera was tougher but eventually fell to the power of the community! The only two major things left are camcorder and full gpu acceleration.
The PDK will hopefully provide the last little bit we need to get acceleration working fully. It's no magic but from the keynote sounds like it might provide the information we need. Or it might not. Won't know until it lands on the web.
Overall jellybean is a step further from our old heroc's but there is still almost 20k devices officially running cm7! We obviously still have a community here who has yet to upgrade so the new goal is jellybean or bust!
As more information and sources are released I'll update the thread. I plan to port our TeamICS github account to Jellybean as soon as it's released. With luck everything will compile and be in the same boat as ics but only time will tell.
Thank you so much for posting this thread! I would have never knew about this. I'm willing to contribute to Jellybean although I'm with the Evo Shift now. I can make AOSP whenever the first jellybean Rom is released hopefully fixing some things!
count me in, i still have a few months on my heroc left until i upgrade
most of the fixes that happened from eligorom should be able to be applied to jellybean, as its basically the same rom as ics (from early reports)
I really need to add it to a signature when here in the HeroC forums, but:
My HeroC has been inactive on a carrier for the last year +, that being said, I still use the crap out of the device when I can, for a clock/alarm, music, GVoice and GrooveIP phone calls when home...
Basically, I would LOVE to see this thing continue to get updates, I still run CM7 over CM9 or ICS because for me, I see the most performance with CM7. Your talk of the PDK has me excited that I might see equal or better performance out of Jelly Bean on my HeroC!
TYVM, keep us updated
im pretty sure jellybean is going to run equal with ics for us, since hardware acceleration is still not available to us
i've been scouring the web for a solution, but no dice so far. we can turn off hwa, but i see no performance increase from doing so
from what i read, its going to take a module and some tweaks, so its going to take a dev with alot of time and knowledge on their hands to get us up to par with the adreno 200, which may never happen (although i hope it does, the heroc is awesome)
Thanks for sharing! Hard!
Not to sure if it can get 4.1. I'm having troubles getting it on the Evo Shift right now...
whoshotjr2006 said:
im pretty sure jellybean is going to run equal with ics for us, since hardware acceleration is still not available to us
i've been scouring the web for a solution, but no dice so far. we can turn off hwa, but i see no performance increase from doing so
from what i read, its going to take a module and some tweaks, so its going to take a dev with alot of time and knowledge on their hands to get us up to par with the adreno 200, which may never happen (although i hope it does, the heroc is awesome)
Click to expand...
Click to collapse
So will Project Butter have no effect on the Hero? I would think that it would at least have some effect in adding smoothness.
Sent from my SPH-D710 using xda app-developers app
I have to say I'm really exited about this. I ran ICS a few times on my hero with no problems, but I'm still using it as a daily even though I'm sure it would run fine. Ive been thinking about upgrading, but i don't see why. I really don't like any new phones. Their too big, no track ball, and i just simply don't like any of the new phones out right now. So all that being said... JELLYBEAN !!!!!
Source is out!
https://groups.google.com/forum/#!topic/android-building/XBYeD-bhk1o
edit: Not quite yet.
I'll update the TeamICS github with a new manifest for it as soon as it's out. Good news is that I happen to have tomorrow off so looks like I'll get a nice full day of playing around and trying to get it building. As with ICS I suspect most things will be broken, audio, dalvik, etc. So we'll have to port the ICS patches to jb. Once cm updates it's sources to jb, then we can switch back to them as they will have most of the patches in place already.
Shelnutt2 said:
Source is out!
https://groups.google.com/forum/#!topic/android-building/XBYeD-bhk1o
edit: Not quite yet.
I'll update the TeamICS github with a new manifest for it as soon as it's out. Good news is that I happen to have tomorrow off so looks like I'll get a nice full day of playing around and trying to get it building. As with ICS I suspect most things will be broken, audio, dalvik, etc. So we'll have to port the ICS patches to jb. Once cm updates it's sources to jb, then we can switch back to them as they will have most of the patches in place already.
Click to expand...
Click to collapse
I change my mind, i do think the hero can run jb BUT im not to sure about 5.0 or whatever they call it.. i upgraded to the evo shift and love it!! Just letting y'all know because this might be the last upgrade sadly said :/
Sent from my BNTV250 using xda premium
awesome, cant wait to see the first source build
ill help in whatever way i can, i just cant dl source because of my crappy internet connection (but if i can find someone to borrow faster internet from for a few hours ill most definitely dl source and try to contribute back that way)
Lol may take me a while before I can start porting for the hero again..
My current projects for the evo shift:
Motoblur
Porting Sense
4.1
3.0
Thats pretty much it =)
Well the cyanogenmod guys are making quick work of jellybean. Every hour more and more patches are ported over. Good news is we are very close to a build. Here are the current issue and workarounds.
Audio doesn't build, working on porting it over
problems with v6 in dalvik, changed to arm mode and ported ics *.S files
problems building aac, due to asm code, currently disabled
problems building srec due to audio issue, working on porting audio
haven't ported camera
Currently hungry and looking for lunch :fingers-crossed:
Shelnutt2 said:
Well the cyanogenmod guys are making quick work of jellybean. Every hour more and more patches are ported over. Good news is we are very close to a build. Here are the current issue and workarounds.
Audio doesn't build, working on porting it over
problems with v6 in dalvik, changed to arm mode and ported ics *.S files
problems building aac, due to asm code, currently disabled
problems building srec due to audio issue, working on porting audio
haven't ported camera
Currently hungry and looking for lunch :fingers-crossed:
Click to expand...
Click to collapse
So excited. My Hero has a sweet tooth.
Ha yeah to be honest the hero is getting more development on ics then my evo shift because y'all have aokp.. I need help with someone getting it to work on my evo shift.. We just had a ICS Kernel released so that better get some devs working .. Even though we lost A LOT to the evo 4g lte sadly said..
megaghostgamer said:
Ha yeah to be honest the hero is getting more development on ics then my evo shift because y'all have aokp.. I need help with someone getting it to work on my evo shift.. We just had a ICS Kernel released so that better get some devs working .. Even though we lost A LOT to the evo 4g lte sadly said..
Click to expand...
Click to collapse
I dont know about AOKP. Sure it was ported, but what work has there been done on it since? Honestly ICS ran super smooth for me on my Hero, especially coupled with V6SuperCharger. I was using LauncherPro on ICS to add to the smoothness, but the V6SuperCharger allows for smooth use of Apex.
yeah, it wasnt aokp that accelerated our cause, aokp has only been around for a few weeks for us so far. it was jaybob's ics aosp rom that really kicked things into gear. that and stritfajt with the camera fix, and the guys over at hero gsm for all the different tweaks and fixes, and mongoosehelix over at eris that kicked butt with evervolv for us. im sure im missing some people, but it doesnt make them any less important to the cause.
and last but not least all the testers and rom flashers that gave excellent feedback
i look forward to seeing jb run like ics
So the reason it's unflashable was because it's over the 170mb limit of the phone. Even though I'm using firerats there still seems to be a hard limit of the recovery and fastboot. The solution is to use a newer recovery, anything cwm 3.x or higher works. The dev phone I'm using had 2.5 cwm and that was the issue. Now it flashes fine. Only problem is for some reason sh didn't build, so now I'm looking to see why it didn't build.
we can cut out some cruft, like live wallpapers, and ringtones/notification sounds. live wallpapers dont work well on heroc anyway.
the sh error is boggling me too, supposedly its mksh symlinked as sh, which should have worked as thats how it is in ics roms.
im on the job lol
edit: yeah something is definitely rotton with those permissions, i checked them against an ics rom and everything checks out, but we still get the permissions error. i'm wondering if its the update binary possibly? ill do some checking and let you know one way or the other