yashsingh1/xdaforums huggingface dataset:
[myTouch 3G, Magic Android Development] skittleguy:
The new radio doesn't have the boot offsets that are present in the original Rogers radio, and as a result the 32A roms don't work. The main benefit of doing this, is that the majority of roms released are for 32B Magics (which is what most people seem to be devving for) so as a result you don't need to wait for ports in order to enjoy the new roms. If you're perfectly comfortable with your current rom, or would rather just port the roms yourself, then you don't need to root.
[myTouch 3G, Magic Android Development] Wysie:
skittleguy: So it becomes a 32B with 288MB of RAM? Also, do you happen to know how to backup the radio? I'd like to be able to restore to stock should the need arise :). Thank you!
[myTouch 3G, Magic Android Development] Cheesebaron:
32B have all the ROM's out for Dream with slight modification...
[myTouch 3G, Magic Android Development] skittleguy:
If I knew how to I would :D

And yeah, it essentially becomes a 32B with more memory, so all the optimizations that were made make the roms crazy fast.
[myTouch 3G, Magic Android Development] Wysie:
The only thing stopping me now is the lack of a radio backup :(. I'd love to be able to switch it back to a 32A if possible.
[myTouch 3G, Magic Android Development] ruffneckc:
Wow. Interesting. Thanks for taking the time to answer these questions skittleguy. And your Roger's ROMS repo thread is awesome!
[myTouch 3G, Magic Android Development] Wysie:
One more thing, does this mean we can run the Dream ROMs as well (instead of the usual 32B ported ROMs)?
[myTouch 3G, Magic Android Development] skittleguy:
They still require porting, probably due to the boot.img-kernel being different between the Dream and Magic.
[myTouch 3G, Magic Android Development] dazcox5181:
Nope, the kernel is the same...

All that changes is the file in boot.img init.trout.rc gets renamed init.sapphire.rc and everything (wifi/bluetooth etc) works perfectly. i think the file is the hardware setup file and luckily the dream and magic are the same hardware, different case and keyboard :)
[myTouch 3G, Magic Android Development] skittleguy:
Hmmm...the Dream rom I flashed didn't work. I think I need to try something...
[myTouch 3G, Magic Android Development] dazcox5181:
with 32A or B? If 32A need the wlan.ko and maybe wpa_supplicant to go with it

32B works perfect for me

(unzip rom, unpack boot, rename file, repack boot, rezip, sign, flash :))
[myTouch 3G, Magic Android Development] skittleguy:
Ok it works now. Patience and repairing the ext filesystem seem to have done the trick.
[myTouch 3G, Magic Android Development] frankinmerth:
skittleguy did you flash a dream rom as-is or did you make the modifications dazcox5181 suggested?
[myTouch 3G, Magic Android Development] skittleguy:
JacXHero for the Dream as-is, and it works. It's a little buggy so I'm trying to wipe the ext3 partiton first (something I never really did).

Edit: Okay, it's way too buggy. There needs to be interdevice porting.
[myTouch 3G, Magic Android Development] Amon_RA:
They will work again if you do this
[myTouch 3G, Magic Android Development] skittleguy:
You're a saint.
[myTouch 3G, Magic Android Development] NguyenHuu:
this is awesome news! and there i was late last nite going around asking devs for 32a ports of their 32b roms lol. have people already tried this method and got their 32B roms running on 32A? any ill effects? so the radio makes your 32A into a 32B, so their shouldnt be any ill effects right? itll just be as if you had a 32B a to begin with plus you have extra ram and US 3g.
[myTouch 3G, Magic Android Development] Amon_RA:
Did anyone check the amount of RAM before and after flashing the 32B radio?

Check how much RAM do you have => cat /proc/meminfo

A 32A should have around 197000 kB free...
[myTouch 3G, Magic Android Development] daldroid:
Extra ram? Uhmm... I'm not so sure...

May I suggest someone who already flashed the .2005 spl with the ota-radio update on 32A boards to post the output for the commands:

adb shell cat /proc/iomem

adb shell cat /proc/meminfo

adb shell cat /proc/cmdline

thanx
[myTouch 3G, Magic Android Development] daldroid:
You were faster than me in asking that ;-)

From a quick overview, I see no patch to older .2005 spl and the released ota-radio-rom.

no htc modded kernel sources available yet, I suppose the dream and 32b magic kernels built from sources do not init the correct memory map.

Hope to be wrong ;-)
[myTouch 3G, Magic Android Development] frankinmerth:
>adb shell cat /proc/iomem

10000000-153fffff : System RAM

10026000-103bffff : Kernel text

103c0000-1049bd2b : Kernel data

16400000-1649afff : msm_panel.0

16d00000-16d1ffff : ram_console

a0200000-a0200fff : msm_serial_hs.0

a0400000-a0400fff : msm_sdcc.1

a0500000-a0500fff : msm_sdcc.2

a0800000-a0801000 : msm_hsusb

a9900000-a9900fff : msm_i2c.0

a9900000-a9900fff : msm_i2c

a9a00000-a9a00fff : msm_serial.0

a9a00000-a9a00fff : msm_serial

aa200000-aa2effff : mdp

aa600000-aa600fff : msm_mddi.0

e8100010-e8100017 : leds-cpld

>adb shell cat /proc/meminfo

MemTotal: 80628 kB

MemFree: 1580 kB

Buffers: 268 kB

Cached: 18948 kB

SwapCached: 0 kB

Active: 33040 kB

Inactive: 33200 kB

Active(anon): 23876 kB

Inactive(anon): 23744 kB

Active(file): 9164 kB

Inactive(file): 9456 kB

Unevictable: 256 kB

Mlocked: 0 kB

SwapTotal: 0 kB

SwapFree: 0 kB

Dirty: 0 kB

Writeback: 0 kB

AnonPages: 47292 kB

Mapped: 14204 kB

Slab: 5512 kB

SReclaimable: 892 kB

SUnreclaim: 4620 kB

PageTables: 3348 kB

NFS_Unstable: 0 kB

Bounce: 0 kB

WritebackTmp: 0 kB

CommitLimit: 40312 kB

Committed_AS: 911500 kB

VmallocTotal: 172032 kB

VmallocUsed: 46832 kB

VmallocChunk: 54268 kB

>adb shell cat /proc/cmdline

board_sapphire.disable_uart3=0 board_sapphire.usb_h2w_sw=0 board_sapphire.disable_sdcard=0 smisize=32 androidboot.baseband=2.22.19.26I androidboot.cid=ROGER001 androidboot.carrier=Rogers androidboot.keycaps=qwerty androidboot.mode=normal androidboot.serialno=HT95MNK02218 androidboot.bootloader=1.33.2005 no_console_suspend=1 console=null
[myTouch 3G, Magic Android Development] mizunox:
Hey, can someone give me a hand with the SPL flashing on my Rogers Magic?

(sorry for the double post - I posted this over in the Dream Root post but didn't get an answer.)

I downloaded the SPL from the link in the first post, then rename it update.zip and place it on the root of the SD card.

Next I need a recovery image, so I got this one: "RAv1.2.0 : Modded ION recovery!" and renamed it recovery.img

Then start my phone holding down volume and power, then press back and it says "fastboot USB".

Then I went to my android sdk folder and typed "fastboot boot recovery.img"

It reboots the phone and hangs at a rogers logo.

What am I missing?
[myTouch 3G, Magic Android Development] Meleeeee:
so...if i flash this radio on my 32a.....and for example the qtek hero rom or jachero for 32b..

1) is wifi working then without making changes myself in the .zips?

2) the same with bluetooth

3) haykuro says the radio is netfilter/iptable enabled, so does f.e. wifi tether then work on every rom?!

4) and...erm..will i have the full ram available? i mean, i guess so, but maybe there are some restrictions...just curious.

thx m8s!
[myTouch 3G, Magic Android Development] Amon_RA:
Congratulations, you lost 100MB by flashing the 32B radio ;)
[myTouch 3G, Magic Android Development] dazcox5181:
Firstly, it wont work fully withour changing the boot.img.

Second the instructions clearly say to erase the ext3 first - in the thread many people have this issue then follow the instructions and love the rom...

There is no 'porting' required, the dream and magic hardware is same, just hero roms are buggy atm.

Try a cyano rom like 3.9.7 and see how quick it can be :)
[myTouch 3G, Magic Android Development] skittleguy:
I think Amon_RA is on the right track here. It wouldn't matter if I got it working, the loss of 100MB of memory is a crap deal.
[myTouch 3G, Magic Android Development] dazcox5181:
Really?? Ha Ha :) oopsie!

If only it worked the other way and flashing a 32a radio gave an extra 100mb... actually, maybe that might just work ;) jk
[myTouch 3G, Magic Android Development] hakeem9:
Yea, unfortunately this looks to be accurate. I am also down 100+mb after the flash :(
[myTouch 3G, Magic Android Development] daldroid:
Thank you. unfortunately it seems all is like I supposed: you're flashing firmware and SPL for 32B and dream boards, It works but there are no hacks enabling the full use of 32A board resources without a modified kernel.

If we get access to the HTC modified kernel sources, we don't need to flash this older spl and the radio-rom.

BTW, I don't recommend to try, but if the available binary kernel from the original HERO rom supports 32A boards, we could flash HERO SPL and HERO radio rom to 32A boards and run almost plain original hero rom (really there are hw differences, like the akm sensor which may require different drivers in kernel).

I was tempted to try flashing hero's spl and radio rom on my 32A board, but the risk of bricking is very high.

Anyone with a serial number for scandinavian original HTC Magic already downloaded the firmware update from htc europe support site?

maybe while we wait for htc to release the updated kernel sources we could have a nice surprise by verifying if the new rom update includes iptables and so on ;-)

Having a TIM device, I cannot download it myself.

Thanx again

Edit: forgot to say that with this mod you are using half the ram available on 32A boards:

MemTotal: 80628 kB

MemFree: 1580 kB
[myTouch 3G, Magic Android Development] haykuro:
Hmm, anyone with an ion device care to share how much ram is in there?

it's odd because the ion runs the 26I radio (reference)
[myTouch 3G, Magic Android Development] skittleguy:
I thought that HTC was making the Dream and Magic source available at the end of July?
[myTouch 3G, Magic Android Development] daldroid:
The radio has nothing to do with netfilter/iptable: it depends on kenel.

By flashing this radio (by the way, it's not hacked, it's the original one), you can boot kernels for dream/sapphire 32B which are built with netfilter/iptables.

Moreover, the sources for that kernel are available, so you can rebuild it yourself or try the good builds cyanogen seems to prepare (at the moment I prefer to use all of my 32A ram, so I won't flash this mod)
[myTouch 3G, Magic Android Development] daldroid:
Yes, someone has posted a reply from an htc rep (really a vice-president) saying so.

I checked the git tree this morning, and no mods were available.

Maybe they are preparing their own site, but I'm not aware if they already did it.

The first one to discover it, pleas inform the rest of us ;-)
[myTouch 3G, Magic Android Development] haykuro:
lol i never said radio is netfilter/iptable, ;P

this is correct.

HTC, like many other companies, likes slapping "GPL" licensing on things and then "forgets" to release what they HAVE to release.
[myTouch 3G, Magic Android Development] Meleeeee:
okay, thank you, seems like i misunderstood something then...but now its clear to me, just logic after all ;-)

thx also to daldroid...but as it seems we just loose our main advantage by flashing this..so its not an option for me for now :-)
[myTouch 3G, Magic Android Development] frankinmerth:
No harm done. I was sort of surprised that it worked at all!
[myTouch 3G, Magic Android Development] hengsin:
Instead of waiting for HTC to release the kernel source, is it a feasible alternative to try to patch the opensource kernel to use the 32a memory configuration ?
[Hero, G2 Touch Themes and Apps] kevwright:
I might have to send mine back, if I were to buy some apps and then get a different handset, can I still use them on the new device.

Kev
[Hero, G2 Touch Themes and Apps] minogue:
no they are tied to your gmail account. So if you send it back you can restore them on your new device without having to pay again..
[Hero, G2 Touch Themes and Apps] Dayzee:
I can verify this - I have apps that I bought for my G1, still in my downloads when I got my magic and again have been transferred to my Hero. Linking to your gmail account is a really fair way for software to work -

On Win Mo it was often tied to the IMEI so if it bust or you sold it you had to buy again or grovel for another code....

Dayzz
[Hero, G2 Touch Themes and Apps] kevwright:
Thanks Both, that is good to know.

Coupled with a post I have read on here from someone who apparantly got a refund very simply on an app, it is making Android look really good.

Only issues left for me are.

1. Trying to forget how good the iPhone is (at the things it does)

2. Try to increase font sizes on Hero.

3. Try to solve the frequent "a network error has occured, please retry, or cancel and return to the previous screen"

4. Solve the seemingly poor wi-fi reception.

5. Try to forgot how none of those things are an issue on iPhone :-)

Kev
[Hero, G2 Touch Themes and Apps] nicelad_uk:
Lot of things there that you have compared to the iPhone, what do you like better than the iPhone though?
[Hero, G2 Touch Themes and Apps] Dayzee:
<CrunchyNutclusters Mode>

Nahhh get a iPhone. The Hero's not for you. It's 'orrible. You won't Like it.

<CrunchyNutClusters Mode/>

Hehehe ;)

Dayzzzz - Get set for going off to the Ed Festival...
[Hero, G2 Touch Themes and Apps] ElRazur:
It appears to be tied in my experience. I bought video safe and photo safe on the g1, and on upgrading to a g2, it am unable to install those apps. It appears that trying to reinstall is making an attempt to charge my bank card again.

I have emailed the supplier. I would see what they have to say.
[Hero, G2 Touch Themes and Apps] Dayzee:
You might get a checking credit card details message but I think this is just to check that its the same as the one that paid. I've never been charged again for the apps I've bought, including copilot .

Dayz
[Hero, G2 Touch Q&A, Help & Troubleshooting] amplizz:
Why can't I find where the week view is in Hero? This was a option in Dream, and in the Heros manual, it says that I can choose from month, week, day and agenda view..

And when I choose which calendars I want to sync with google calendar on the web, some of my calendars don't show on the phone. And the other way around. There is a "My calendar" on the phone which don't appear on the web.

Syncing events in the calenders that do appear in both places, is no problem..

What is the problem?

I've had the phone almost a week, and the other calendars just wont show up. It did show up on my Dream.
[Hero, G2 Touch Q&A, Help & Troubleshooting] ppiixx:
One of my google calendars just wouldnt show up. In the end I just created a new one and edited the events to be on that one.
[Touch Cruise ROM Development] hugorfn:
when I have two signals of network does not receive calls or sms.

is as if no network.

some one can help me
[Touch Cruise ROM Development] nicandris:
try changing the radio. are you using a cutom ROM or htc official?
[Touch Cruise ROM Development] hugorfn:
I have a M-ANIME PTG but i try a oriinal rom with original radio but have the same problem.

Thanks
[Touch Cruise ROM Development] nicandris:
ok first of all try the SIM in another phone if you have one, or contact your carrier. Anyhow, try rom and radio in my signature (first the radio). If it's still the same then something is wrong with the hardware.
[G1 Q&A, Help & Troubleshooting] Daneshm90:
Hey guys...neone know wht file u gotta edit to move the service providers name in the expanded status bar like he did ?
[G1 Q&A, Help & Troubleshooting] DirectMatrix:
Interesting

I would also be interested in finding this out, however I would like to remove it completely lol....

I'm subscribed to the thread but if you find out some other way, can you PM me?
[G1 Q&A, Help & Troubleshooting] Daneshm90:
Sure lol...im waitin on a couple of themers to answer me...i know its in the layout folder of framework-res.apk....just dont know wht file n wht value
[G1 Q&A, Help & Troubleshooting] DirectMatrix:
Yeah, I've been doing some exploring in directories with adb for 20 mins and I have little to no chance of finding it without a starting point. Lemme know if you get a response from the themers...I read up on their tutorials over in Themes section and I don't remember reading anything specific on this subject.
[G1 Q&A, Help & Troubleshooting] supremeteam256:
I don't know the answer so I'm just throwin this out there. Wouldn't that have to be edited in the .xml file just like any other theme.
[Touch Pro2, Tilt 2 Windows Mobile General] tjobbins:
sorry stupid question, removed.
[myTouch 3G, Magic Android Development] Captchunk:
I'm not sure where to post this thread, I'm picking here because I believe if I can be helped, it'll be by the people here. This morning I followed the guide posted by Haykuro to get "real" root on the Rogers. However, I made the most basic mistake of noobdom and didn't bother to check that this was for my phone. It's not, it's for the Dream. I can still boot into fastboot, but through the guide I flashed the new radio which I think is completely incompatable with the Magic, so to start, could someone post the original Rogers radio? Please don't clutter up the thread with "ur an idiot" type posts, trust me, you can't possibly call me anything I haven't called myself for the past half hour. I want to punch myself in the face, but I'm a bleeder.

Here is the post http://xdaforums.com/showpost.php?p=4271500&postcount=1
[myTouch 3G, Magic Android Development] ClintonH:
Here are the SPLs. But I'm not sure that will help you out, I think you may have to send it in.

Clinton
[myTouch 3G, Magic Android Development] Captchunk:
Thanks, I don't think those contain radio.img though, unless I'm wrong?
[myTouch 3G, Magic Android Development] Deicist:
If you can still get into fastboot your best bet is probably to restore a nandroid backup from someone's untouched rogers handset.

that should fix everything and reset your phone to how it was.
[myTouch 3G, Magic Android Development] Captchunk:
I have the wiped nandroid backup posted by Skittleguy on my computer, so I'll try that in a few and post my results shortly.
[myTouch 3G, Magic Android Development] Captchunk:
Restoring the Wiped Nandroid Backup didn't work, I don't think that it's updating the radio, which is why I think that if I flash the original radio back first and then do the tutorial again using a Magic recovery, that I might be okay. I'm just thinking out loud here though.
[myTouch 3G, Magic Android Development] skittleguy:
So wait, do you own a Rogers Magic (32A)? If you do, then it should work (using it right now as a matter of fact). Just make sure that you use a 32B compatible recovery.
[myTouch 3G, Magic Android Development] Captchunk:
What should work? The wiped nandroid backup?
[myTouch 3G, Magic Android Development] skittleguy:
Reflashing the radio. From what I understand, this root method essentially turns the Rogers phone into a "32B" Magic. You still have all the memory and goodies, but you should now be able to flash any 32B rom onto your phone. And for that reason, you need to use the 32B compatible recovery and then you can flash any 32B rom.

And for future reference, Nandroid does not back up your radio. To the best of my knowledge, there is no way of getting the Rogers radio unless you probably do some hardware modding.

Edit: Post 100!
[myTouch 3G, Magic Android Development] Captchunk:
Alright, I'm flashing a 32B Rom as we speak.
[myTouch 3G, Magic Android Development] Captchunk:
Okay, my phone flashed, and it's working just fine with a 32B Rom. Although now, I wonder what I did, because it wouldn't boot before. In the mad dash that has been the last hour, I'm sure (obviously) that I did something wrong, but I don't know what. Thanks everyone for your replies, and Skittleguy especially thank you for verbally slapping me back into reality! Mod, you can lock this thread down.
[Windows Mobile Development and Hacking General] cmydlarz:
Im a researcher at Salford uni, UK using mobile devices to allow the public to carry out noise surveys.

Im hoping to recruit thousands of people to install our app on their j2me mobile or WM PDA, which allows them to record the sound around them and comment on it using some simple scales.

The projects in its pilot at the mo so im trialling the software and methodology with some hard core beta testing.

Im really hoping you guys might be keen to test the WM app out and give me some feedback on how it works and how it could be improved.

Ive attached the cab file and source for your testing pleasure! The code is quite scatty but should be pretty readable.

As a side issue im also looking for some feedback on our project site @ http://www.soundaroundyou.com.

I'm the only one developing the projects different parts so im the worst one to be checking out its accessibility, usability and functionality. Thats why im calling on you guys for your mad development and testing skills.

Any feedback is good feedback for me so be as brutal as you like.

Cheers!

Charlie

NB: Just changed the source and CAB to support (hopefully) all resolutions of devices. All ive done is scaled up all controls in the app depending on the screen size of the target device. There may be some strange side effects of this on device but it seems ok on the emulator...

New site look and feel. Map page also updated with new upload section for online uploads of soundscapes. Check it out...:D (http://www.soundaroundyou.com)
[Windows Mobile Development and Hacking General] m.schmidler:
Sounds really interesting, I´ll give it a try. Please keep the first post up-to-date, maybe add screenshots as well, thanks :)
[Windows Mobile Development and Hacking General] m.schmidler:
---delete, double-post---
[Windows Mobile Development and Hacking General] MasterOfDesasters:
any chance to get a vwga version instead of qvgaas it is not useable on my topaz.
[Windows Mobile Development and Hacking General] cmydlarz:
Cheers for the interest, im downloading the WM 6.5 toolkit now so I can give it a whirl on that platform.

Ill post up here when ive sorted it.

Cheers, C
[Windows Mobile Development and Hacking General] cmydlarz:
Just uploaded new version

In response to MasterOfDesasters ive edited the app so that it scales all of its controls to be usable on a larger screened device.

Its a quick fix really but seems to do the job and makes sure that everything can be navigated and used as you would on it native sized version.

This scaling is not ideal so might throw up some strange effects on control placement, but ive found no issues yet on the emulator.

Thanks again for your interest, C
[Windows Mobile Development and Hacking General] MasterOfDesasters:
works so far, but the capture tab is rotated 180 degrees :D
[Windows Mobile Development and Hacking General] aussiebum:
interesting... but would like some more details. 1) there are two cabs - which should be installed? and 2) where are the sound recordings stored? internal or external?
[Windows Mobile Development and Hacking General] + Que PPC:
yep same questions here... i would like to participate on your proyect seems to be nice... but why? :p
[Windows Mobile Development and Hacking General] cmydlarz:
Strange but necessary!

Strange but intentional!
[Windows Mobile Development and Hacking General] cmydlarz:
Hey there, the single cab attachment is the one to install but it should be the same as the one in the source zip anyways.

The sounds are stored on the devices root in a folder named "Sound Around You" There is a settings file and however many wav files for each recording. Each of these recordings has an associated xml text file that contains your subjective responses.

You can locate and upload your recordings using the PC app so they are viewable on the world soundscape map and can then be used in my research.

Thanks for your interest and let me know how it goes for you. Any other thoughts you might have on the PC app or website would also be great as im having a hard time attracting the public to take part and im far too nerd orientated to properly publicise the project!