is there a way to get wifi tether for root users on the I/O device to work. Seems like there is something missing from the os. I saw an outdated post where it says to upgrade the kernal but stops other things from working and didn't want to do that. My friend also on here is trying to make a rom for the device with the hero theme on it and I asked him he said he will look into it but didn't really know. If anyone knows would be greatly appreciated.
TheArtiszan said:
is there a way to get wifi tether for root users on the I/O device to work. Seems like there is something missing from the os. I saw an outdated post where it says to upgrade the kernal but stops other things from working and didn't want to do that. My friend also on here is trying to make a rom for the device with the hero theme on it and I asked him he said he will look into it but didn't really know. If anyone knows would be greatly appreciated.
Click to expand...
Click to collapse
It's built in to the Smartphone France ROMs
I'm also desperate to get tethering on my magic (running a hero rom) any help greatly appreciated, as i'm moving soon and don't want an ISP!
this has been answered before, if you have a 32B magic almost every custom rom supports it, and if you have a 32A magic the answer is not possible for now.
k4r1m said:
if you have a 32B magic almost every custom rom supports it, and if you have a 32A magic the answer is not possible for now.
Click to expand...
Click to collapse
There's the first benefit of having a 32B over 32A! I'm not as upset about my 32B anymore Though this will change, i'm sure.
biggler said:
There's the first benefit of having a 32B over 32A! I'm not as upset about my 32B anymore Though this will change, i'm sure.
Click to expand...
Click to collapse
don't forget that we have almost double your runtime ram ;]
k4r1m said:
don't forget that we have almost double your runtime ram ;]
Click to expand...
Click to collapse
/me buys k4r1m a calculator for his/her b'day
it's true, you can rub the tehering app all you want in our faces but at the end you will never be able to get more ram but us, we have a high chance of getting it to work lol in your face?
I had wireless tethering running no problem on my 32B. The thing is, I've installed so many ROMS lately that I can't remember which one I had installed when it was working. All I know is that it was a Hero ROM.
k4r1m said:
it's true, you can rub the tehering app all you want in our faces but at the end you will never be able to get more ram but us, we have a high chance of getting it to work lol in your face?
Click to expand...
Click to collapse
To be honest, I'd swap my 32B for a 32A right now, even if the tethering app never worked on a 32A. I just want more ram after seeing a HTC Hero running with Rosie.
If there's only a ram difference between 32A and B then why doesnt the Tethering app work already? I thought all it required was root access? The 32A has been rooted... hasn't it?
Malky1903 said:
I can't remember which one I had installed when it was working. All I know is that it was a Hero ROM.
Click to expand...
Click to collapse
Download the .apk from here and try installing it manually?
tether
Yen if you have a 32B board sapphire you can look back a few posts and flash my hero build which is a port from jac dream build to the magic hardware. It has wick tether built in on the rim and works fine. The one with the wifi fix is back a few pages. Bur works good and quick.
Related
Hi all,
I've been waiting for the HTC Magic 32A kernel source for some time so that I can compile netfilter/iptables support into the kernel. I would really like to tether my phone to my laptop while I'm out of the office.
I notice that most of the 32B ROMs have support for tethering.
Would it be possible to flash a 32B radio on to my 32A device and then use the 32B ROMs?
I'm reasonably comfortable flashing the radio on my phone, but I don't want to go through the procedure if it's not going to work.
Could somebody point me in the right direction please?
cursordroid said:
Hi all,
I've been waiting for the HTC Magic 32A kernel source for some time so that I can compile netfilter/iptables support into the kernel. I would really like to tether my phone to my laptop while I'm out of the office.
I notice that most of the 32B ROMs have support for tethering.
Would it be possible to flash a 32B radio on to my 32A device and then use the 32B ROMs?
I'm reasonably comfortable flashing the radio on my phone, but I don't want to go through the procedure if it's not going to work.
Could somebody point me in the right direction please?
Click to expand...
Click to collapse
Yes it will work.
http://forum.xda-developers.com/showthread.php?t=544686
SWEET!!!
OK, now I'm not sitting here hitting 'F5' waiting for HTC to announce that they've released the source code. Still would like to see it available, but I can wait now.
Cheers!
cursordroid said:
SWEET!!!
OK, now I'm not sitting here hitting 'F5' waiting for HTC to announce that they've released the source code. Still would like to see it available, but I can wait now.
Cheers!
Click to expand...
Click to collapse
1 caveat. The 32A loses it's memory advantage. The 32B radio doesnt seem to allow the phone to see all of its memory...kernel issue probably. That's why not all 32A users have switched...we like our memory!
bcrook said:
1 caveat. The 32A loses it's memory advantage. The 32B radio doesnt seem to allow the phone to see all of its memory...kernel issue probably. That's why not all 32A users have switched...we like our memory!
Click to expand...
Click to collapse
Yes, and that's why I bought a 32a version in the first place!!
Yeah, I've noticed that the ROM that I flashed the morning (nk02 32B) is running a fair bit slower than its 32A counterpart. I think I can handle this until the 32A source is released and I can tether using a 32A ROM.
In the meantime though, I'm quite happy with the 3.5G data while out of the office.
cursordroid said:
Yeah, I've noticed that the ROM that I flashed the morning (nk02 32B) is running a fair bit slower than its 32A counterpart. I think I can handle this until the 32A source is released and I can tether using a 32A ROM.
In the meantime though, I'm quite happy with the 3.5G data while out of the office.
Click to expand...
Click to collapse
OK, I couldn't handle how slow my phone was running. It was painful! Waiting for the Apps tray to open sometimes took 15 seconds. And when I unlock the screen, I get a Close/Wait prompt for android.acore. I tried a couple different 32B ROMs but they were all pretty slow compared to the performance I'm used to. I'm sure if I didn't need to have so many apps installed and have the Hero theme it would be a lot faster...
As for the tethering, I found an application called AziLink. It doesn't use the iptables/netfilter functionality, but runs more like a VPN server through adb. It's buggy as hell, and disconnects all the time, but it'll do for now.
Title pretty much explains it. There are (not many) but more Hero roms on the GSM side of things than the Hero. But obviously, MoDaCo took his rom and switched it over to CDMA for us. So if anyone could help that would be great.
I also have been trying to port Malign's Hero rom for the Dream over to Hero but I'm getting stuck on boot. Loads up but Rosie doesnt seem to want to load. I am trying to do this so I can learn how to port over the good roms since it doesnt seem like many devs are interested in CDMA Hero, which is understandable considering it's price and carrier.
chuckhriczko said:
Title pretty much explains it. There are (not many) but more Hero roms on the GSM side of things than the Hero. But obviously, MoDaCo took his rom and switched it over to CDMA for us. So if anyone could help that would be great.
I also have been trying to port Malign's Hero rom for the Dream over to Hero but I'm getting stuck on boot. Loads up but Rosie doesnt seem to want to load. I am trying to do this so I can learn how to port over the good roms since it doesnt seem like many devs are interested in CDMA Hero, which is understandable considering it's price and carrier.
Click to expand...
Click to collapse
If you need any help with this task, I can help to, I am interested in this also
What's involved? The hand of God.
I'm kidding. Well, not really. I don't really know.
goku14238 said:
If you need any help with this task, I can help to, I am interested in this also
Click to expand...
Click to collapse
Are you saying you know a bit of how to do this or you just want to learn as well?
I don't know the ins and outs of the apks in that ROM, but I do know step 1 - a kernel recompile.
Thankfully, HTC released their kernel changes shortly after the CMDA Hero arrived, which you can download here:
http://developer.htc.com/
You'll need the android SDK and sources for whichever version you want to build - 1.5 should be fully compatible with this kernel, not sure about 1.6, but probably not 2.0.
Unforunately HTC probably won't release their changes for 2.0 until after they dunk Eclair onto the Hero. 2.0 support may work out of the box, may require just a few quick changes, or may be broken entirely, who knows!
[edit] Thinking on this further, a kernel rebuild might not be necessary, but it wouldn't be a bad idea. You may just be able to replace the kernel/boot image in the ROM with the kernel on your Hero (or yanked out of MoDaCo's ROM). No way to know execept to do a thang.
chuckhriczko said:
Are you saying you know a bit of how to do this or you just want to learn as well?
Click to expand...
Click to collapse
I would love to learn as well. can put android hacking, and rom making on my hacking/modding resume
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.
Yes I am very new to android. I managed to root mythouch 3g 1.2 to the fender rooted rom. I am just confused completely on the 2.1 roms. What is porting? I did the unlocker method with no problem. I had an epic fail trying to install a 2.1 rom! Mainly cuz I can't figure out what the heck all this porting and partitioning is. Any help would be appreciated so much!!
All that you can read here on these sits.
It must be the 32b that has messed me up. For some reason I thought the 3.5mm jack was on the 32a. That would be a good reason for that rom not working. Man I'm getting bad at this kinda stuff.
hammer4203 said:
It must be the 32b that has messed me up. For some reason I thought the 3.5mm jack was on the 32a. That would be a good reason for that rom not working. Man I'm getting bad at this kinda stuff.
Click to expand...
Click to collapse
NOOOO.. the 1.2/fender are ALL 32a boards. There are NO 2.1 roms for our phones yet because the drivers/kernel source have not been released. So for now, just use some of our themed roms. They work great and look great.
Again, NO 2.1 roms will work.
I had one pull up but touch screen was not working. I'm begging to think they just threw this phone together. I see some say there r roms but they have no bt and youtube. Or am I just that lost? I can live without bt and video.
hammer4203 said:
I had one pull up but touch screen was not working. I'm begging to think they just threw this phone together. I see some say there r roms but they have no bt and youtube. Or am I just that lost? I can live without bt and video.
Click to expand...
Click to collapse
Ok...
HTC has not released the source for the new touch screen drivers or 3.5 jack. So, if you would have read ont he instructions you used to root the phone, there are no special roms for our phones yet. Thrown together? It has a brand new touch screen and a new headphone jack that was not in the older version = no way to use them yet.
So, in these instructions you rushed through, you would have read that the only roms we have are the fender rom and the themed roms.
We have one 2.1 rom working from STokes. But you have to search it down in these forums under the Mytouch 1.2/fender threads.
Not trying to be an ass here, but its obvious you did not read fully before rooting your phone.
Thanks for the help! I was misunderstanding my phone config. I thought I had the 32a. That's why I was lost! Sorry! Although I did read it....and flashed it too! That's why my phone went stupid on me! Boy did I miss a big one there! Well I do appreciate the help all the same! That cleared all my confusion up.
Ok my phone says its a 32a ships s-on G. So how is that correct and work?
hammer4203 said:
Ok my phone says its a 32a ships s-on G. So how is that correct and work?
Click to expand...
Click to collapse
.. what are you asking? You showed us what board your phone is using, sooooo what? I need better english to understand you. I have no idea what "how is that correct and work" means. I hope you're not giving us your phones information so we can hold your hand and take you through step by step.
I also don't understand how you can't find information about all this porting and partitioning. I'm a normal member like you, how was I able to find all this information on these forums and google but you can't?
Can you do me a favour and start researching yourself rather than asking a bunch of questions that are already answered. You've already posted in the wrong section, and you obviously haven't tried hard enough. You didn't know if you had a 32A or 32B at first, which is the most basic thing of all. This is why people like you brick their phones. You totally just guessed which board you have.
Then you complain about the touch screen issues when it's all explained in the process of how to root it, wow. Get ready for flames if you continue to fail like this. Please read things more thoroughly and post in the right section.
What I guess I am trying to ask is the G or H relevent in any way? I understand the boards. I have been told It was a 32b then when I rooted it I rooted the wrong file. Which would have bricked it. That is why I am asking all the questions. It works fine with the fender root. It just doesn't seem to work loading any 2.1 rom at all. And yes I have tried 32a and 32b. The 32b 2.1 loads without the touch screen working. 32a 2.1 doesn't do a thing, just freezes. Does that help explain it a little better for you?
hammer4203 said:
What I guess I am trying to ask is the G or H relevent in any way? I understand the boards. I have been told It was a 32b then when I rooted it I rooted the wrong file. Which would have bricked it. That is why I am asking all the questions. It works fine with the fender root. It just doesn't seem to work loading any 2.1 rom at all. And yes I have tried 32a and 32b. The 32b 2.1 loads without the touch screen working. 32a 2.1 doesn't do a thing, just freezes. Does that help explain it a little better for you?
Click to expand...
Click to collapse
Did you not read this at all?
crypysmoker said:
NOOOO.. the 1.2/fender are ALL 32a boards. There are NO 2.1 roms for our phones yet because the drivers/kernel source have not been released. So for now, just use some of our themed roms. They work great and look great.
Again, NO 2.1 roms will work.
Click to expand...
Click to collapse
crypysmoker said:
Ok...
HTC has not released the source for the new touch screen drivers or 3.5 jack. So, if you would have read ont he instructions you used to root the phone, there are no special roms for our phones yet. Thrown together? It has a brand new touch screen and a new headphone jack that was not in the older version = no way to use them yet.
So, in these instructions you rushed through, you would have read that the only roms we have are the fender rom and the themed roms.
We have one 2.1 rom working from STokes. But you have to search it down in these forums under the Mytouch 1.2/fender threads.
Not trying to be an ass here, but its obvious you did not read fully before rooting your phone.
Click to expand...
Click to collapse
This is where I wound up and why!!! So flame away, but I was lead to that by this reply. WOW! I guess I'm not the only one that can make a mistake now am I? Stokes pointed me to the right direction for the file I really need to get 2.1 on my phone. I didn't mean to get everyone so angry! Thanks though!!
hammer4203 said:
This is where I wound up and why!!! So flame away, but I was lead to that by this reply. WOW! I guess I'm not the only one that can make a mistake now am I? Stokes pointed me to the right direction for the file I really need to get 2.1 on my phone. I didn't mean to get everyone so angry! Thanks though!!
Click to expand...
Click to collapse
You got a 32b 2.1 rom to boot??? which one please. If you can get it to boot, we can then flash the kernel over, reboot, and get things working.
I wasnt flaming you, I was mearly pointing out the fact that every single thing you asked, you would have had to have known before rooting the phone.
Yours says G... which makes no sense considering its a 32a HTC branded phone (maybe the 1.2's are different? because the fender is an HTC branded board.
We here, just get tired of people that say they have searched... yet its blatently obvious it doesnt.
Now that stokes has given you the 2.1 rom..... Now we have to hear you ask 15 times now why the Bluetooth and Wifi wont work.....
Stokes 2.1 loaded for me and it is 32b. Just the touch screen didn't work. I would say if it wasn't for my phone it shouldn't have had the droid saying touch to start. None of the others did that at all. Here is where I got it from.
http://forum.xda-developers.com/showthread.php?t=624411
I saw bt and video issue. I just wanted to see how cool it looked. I don't watch video on the phone anyway.
nevermind nevermind
hammer4203 said:
Stokes 2.1 loaded for me and it is 32b. Just the touch screen didn't work. I would say if it wasn't for my phone it shouldn't have had the droid saying touch to start. None of the others did that at all. Here is where I got it from.
http://forum.xda-developers.com/showthread.php?t=624411
I saw bt and video issue. I just wanted to see how cool it looked. I don't watch video on the phone anyway.
Click to expand...
Click to collapse
Oh now.. we have a fuly working stokes port working minus BT with touch screen. I was gona post it fo ryou but max file limit here is to small. Tomorrow when im not drunk Ill search a link down or get stokes to give me direct link. Im running it right now andf other then BT and youtube not working, it is so purdy with the live wallpapers. with the extra 32a ram, it runs just as well as the nexus one. If you have talked to stokes, ask him for his 1.41 Fender/LE port. Full wipe, Skip google sign in and sign in through market for sync. After that you will be very happy .
So the 2.1 rom works?
crypysmoker said:
Oh now.. we have a fuly working stokes port working minus BT with touch screen. I was gona post it fo ryou but max file limit here is to small. Tomorrow when im not drunk Ill search a link down or get stokes to give me direct link. Im running it right now andf other then BT and youtube not working, it is so purdy with the live wallpapers. with the extra 32a ram, it runs just as well as the nexus one. If you have talked to stokes, ask him for his 1.41 Fender/LE port. Full wipe, Skip google sign in and sign in through market for sync. After that you will be very happy .
Click to expand...
Click to collapse
Did he release on that has fixed Wifi? The last link I saw posted was missing the fixed wlan file.
hammer4203 said:
So the 2.1 rom works?
Click to expand...
Click to collapse
Yea ... here's the port
port_Stokes_Eclair.zip
You have to push the wlan.ko file to get wifi working though.
Is the one referenced here newer or older than the link you posted?
http://forum.xda-developers.com/showthread.php?p=6085708#post6085708
Can the 2.1 version for Rogers can put onto the T-Mobile version of the HTC Magic or will it be problematic?
Looks like it works on 32a
http://twitter.com/Amon_RA/status/24101277025
http://twitter.com/Amon_RA/status/24113346424
http://twitter.com/Amon_RA/status/24116479740
Yeah i'm curious if it can be ported to us on 32b. Would probably work smoother than those legend ports
Sent from my U20i using XDA App
Anyone know if this has "Smart Dialer"?
Sent from my HTC Dream SparksMod using XDA App
is it sense ui?
asb123 said:
is it sense ui?
Click to expand...
Click to collapse
Yes it is sense
http://www.youtube.com/watch?v=1lNeYGQWymM
Come On Dudes! Do It! A Magic Sense Rom must run good on the G1!
Maybe somebody could replace the Sense UI for the Android original. The hardware is not so different, just a little bit more memory.
I want this ROM ported to HTC Magic 32B because since Android 2.x we always have memory leaks in the camera driver.
I definitely want this ported!
I definitely want this ported too! Especially if it finally bring Sense to the G1 without draining our battery in less than day. Or in another cases requires so many changes that it becomes too unstable.
hmmm what did rogers do that cyanogen didn't?
qipengart said:
Can the 2.1 version for Rogers can put onto the T-Mobile version of the HTC Magic or will it be problematic?
Click to expand...
Click to collapse
Some1 ported to 32b please please please
R3N0V4D0 said:
hmmm what did rogers do that cyanogen didn't?
Click to expand...
Click to collapse
Dude its Sense I love sense = o )
solaresdonis said:
Dude its Sense I love sense = o )
Click to expand...
Click to collapse
this is definitely possible. Most people Dont know that the cause for battery drain is a combination of:
1. swap
2. "optimized kernels"
These both exist to make sense roms usable on our phones, and they do make them usable but they drain battery.
the only advantage that this 32a build with sense may have is optimizations of the apk's and frameworks that could account for a speedier experience, and therefore introduce the possibility of cutting down on the two factors listed above.
It is very possible to do, and in fact easy. If the demand is high enough, i'll do it myself... add ideas/input here.
I definitely am up for a port
Sent from my Htcclay's SuperBad 3G using XDA App
jcarrz1 said:
this is definitely possible. Most people Dont know that the cause for battery drain is a combination of:
1. swap
2. "optimized kernels"
These both exist to make sense roms usable on our phones, and they do make them usable but they drain battery.
the only advantage that this 32a build with sense may have is optimizations of the apk's and frameworks that could account for a speedier experience, and therefore introduce the possibility of cutting down on the two factors listed above.
It is very possible to do, and in fact easy. If the demand is high enough, i'll do it myself... add ideas/input here.
Click to expand...
Click to collapse
Another thing to remember is that 32A's have about 100 mb more ram, so 32B's actually need some of those things to make them more usable. Anybody know anything about the radio that released with it? I mean, is it still a locked down 3.X rogers radio, or is it something 2.X, or even 6.X? Another thing of interest would be bluetooth, but I'm not sure if 32A's and B's share the same bluetooth chip. +1 for the port jcarzz, I would try it myself but I'm still learning. We should also try to extract the camara drivers, the way I understand it in CM5/6 we're using a hacky method with backported donut drivers and a few other things. We could really pull a lot from this.
Okay, so I looked a few things up and answered some of my own questions. It does include a new radio 6.35.16.19, but it's not something we can use. Maybe some of the guys who have JTAG equipment can experiment with flashing it. Since it's not a G1 radio we shouldn't get bluetooth working so cross that off the list too. Still a promising release though.
jcarrz1 said:
this is definitely possible. Most people Dont know that the cause for battery drain is a combination of:
1. swap
2. "optimized kernels"
These both exist to make sense roms usable on our phones, and they do make them usable but they drain battery.
the only advantage that this 32a build with sense may have is optimizations of the apk's and frameworks that could account for a speedier experience, and therefore introduce the possibility of cutting down on the two factors listed above.
It is very possible to do, and in fact easy. If the demand is high enough, i'll do it myself... add ideas/input here.
Click to expand...
Click to collapse
Please my liege. Do it.
Request: Make it awesome .
mejorguille said:
Another thing of interest would be bluetooth, but I'm not sure if 32A's and B's share the same bluetooth chip.
Click to expand...
Click to collapse
No, just like all the early 1.5 Hero roms that were from 32a phone... no Bluetooth.
I did a quick dirty port... got to boot but runs like crap... nonstop FC's and crashes. Really no time to play with it.
fishman0919 said:
No, just like all the early 1.5 Hero roms that were from 32a phone... no Bluetooth.
I did a quick dirty port... got to boot but runs like crap... nonstop FC's and crashes. Really no time to play with it.
Click to expand...
Click to collapse
Hehe I figured so, but I wasn't rooted yet when all the hero rom's started coming out so I didn't know that til now. And I looked through cyanogen's twitter and he mentioned that the camera drivers were tied to the radio so we can't pull that from it either. GL on porting it.