yashsingh1/xdaforums huggingface dataset:
[myTouch 3G, Magic Android Development] bcrook:
There is an old SuperD boot.img I made? That must've been a WHILE ago. I can look into a new one.
[myTouch 3G, Magic Android Development] xaueious:
Yea. You just changed your directory structure so I don't know where you put it now. It was named bc-superD-ebi1-signed it actually boots super D and it mostly works. Dated December 21 so it wasn't that long ago.

I was on WG-Donut Y 2.6 but it gave me some issues with Google Apps. Cyanogenmod runs perfect but it was a bit choppy sometimes. Super D is faster than Cyanogenmod even though CompCache doesn't work. This is on your old SuperD patch by the way. Wireless reception on 3G is also not as good for some reason.
[myTouch 3G, Magic Android Development] bcrook:
Try this one:

http://briancrook.ca/magic/bc-superD17-ebi1-signed.zip

I redid it with the 4.2.13 kernel
[myTouch 3G, Magic Android Development] xaueious:
Trying it now. Got past the Rogers screen. Still booting with a weird black and white bar boot screen, but that's only cosmetic. I flashed the Rogers fix after applying this since this patch overwrites build.trout.prop

Multitouch works now (gallery and browser)

This is going to be my main rom now. Thanks!
[myTouch 3G, Magic Android Development] bcrook:
I would try without the Rogers "fix"

Build.prop changes can cause funny **** when used on incorrect ROMs.

The SuperD dev (I forget his name) doesn't publish his kernel source in a place I can find so my port will not be ideal.

Sorry.

If anyone wants to try out an eclair build, check out OpenEclair:

Info thread: http://xdaforums.com/showthread.php?t=624545

Download: http://short.to/153a2

Port File: http://briancrook.ca/magic/OpenEclair/OpenEclair-BETA1-ebi1-signed.zip
[myTouch 3G, Magic Android Development] xaueious:
Well the Rogers 'fix' and your new patch works fine. I wanted a fast ROM with multi-touch and this hits the sweetspot. I don't need a boot screen anyways so this is just fine. Since I didn't wipe I'm not sure if your SuperD patch does this or if the old one killed the bootscreen. I'll install Darkstar to try to fix that.

I don't think I'll move to the OpenEclair just yet. Do you want testers? I would like to move to it when it has at least hardware acceleration for videos. I don't need the camcorder. I know it uses CM Updater, but then I would need to reflash the EBI1 OpenEclair patch every time anyways.

Thanks for doing all this

Edit: Got my bootscreen back installing Darkstar for Super D. Everything is beautiful.

Edit 2:

There seems to be a bug with this. Compcache doesn't work but it is supposed to be on by default.

Manually running the custom_init results in the error:

init_module '/system.lib/compcache/ramzswap.ko failed (Exec format error)

I guess this is one of the things you warned about. I wonder where I can pull a working ramzswap.ko

Edit 3:

Compcache fix for Super D 1.7 on EBI1

Compcache is enabled on boot by custom_init.sh in /system/bin

Compcache needs the ramzswap.ko from Cyanogenmod 4.2.13 to work! And it does work!

Before replacing the file, "Exec format error" occurs on the ismod command for the ramzswap.ko

Cyanogenmod 4.2.13 ramzswap.ko Uploaded here: http://drop.io/uljo2ag

It needs to go into /system/lib/compcache/ to replace the existing one

Anyhow that's probably easy to implement into your new patch Brian.

I hope that's the end of my issues. Because this rom rocks.

(took me forever to figure out how to mount the squash fs modules.sqf from Cyanogenmod)

More notes about Compcache on Super D 1.7 EBI:

The Spare Parts Compcache option doesn't work, but I am not sure if that does anything in Super D's original 1.7 either.

There's a compcache shell script that comes with SuperD but it also doesn't work because it tries to point to the Cyanogen location for ramzswap.ko
[myTouch 3G, Magic Android Development] xaueious:
New Rogers Radio (Post 911 update)

I updated to the newer Rogers radio (3.22.26.17 from 3.22.20.17) on the HTC Dream.

Cyanogenmod 4.2.13 confirmed to be working with the new radio. Everything seems to be good.

Super D "power off" ends up rebooting the phone. Enabling wireless location has force close problems since the last radio. I'm not on this rom anymore.

These are nandroid restores.

Sorry for double post
[myTouch 3G, Magic Android Development] bcrook:
How did you flash the radio? Do you have a radio.img?
[myTouch 3G, Magic Android Development] :
I'm into giving OpenEclair a go.

I'm unable to confirm what radio and SPL are needed for this ROM.

Also, think it's worth waiting until you guys get your beta2 working before flashing it for first time?
[myTouch 3G, Magic Android Development] bcrook:
Give it some time. wait for a new stable release. I have been getting some gapps FCs and stuff.

They are working towards not requiring a special SPL for the dream
[myTouch 3G, Magic Android Development] psycotic11:
So I followed this link under your "new install - magic"

but it redirects me to the other cyanogen install that requires it to be done over USB (i'd link it, but I can't as a new user :o)

I got ADB drivers to see the phone as "android phone"

but when I reboot in to fastboot, the device stops showing up and I am unable to continue with the flashing process

any help?
[myTouch 3G, Magic Android Development] DThor:
Well I've currently given up getting Rogers to re-enable my wife's latest cyanorom Magic - they're playing dumb now, the bcrooke patch(net2) isn't enough to restart it on it's own(after pulling the battery online with tech support), and they simply refuse to restart the network for the phone. My guy played dumb, I'm guessing that's what they do now. *My* Magic was reset a week ago without any trouble(although we called a business account support line - that may be the key to getting them to actually do what they're being asked to do). I even told the guy I have two identical phones, one works, one doesn't, please restart the network, and he simply shrugged. Playing dumb comes natural I guess.

Anyway, my wife at this point is really pissed, she wants her data back. I foolishly didn't backup the stock ROM and now I've found out HTC Sync won't talk to the cyanogen ROM - the comm program has been stripped. I downloaded a file 'sync.zip' which has PCSII.apk which is what was missing, but it crashes on any attempt to communicate with HTC Sync. Can anyone recommend either a working comm program, or a stock Rogers ROM I can re-install? I've been hunting without luck.

I'm just glad my phone is rooted and running...:-/

Thanks

DT
[myTouch 3G, Magic Android Development] bcrook:
Why don't you put CursorSense on her phone? It essentially IS the Rogers update but with root and some custom bits. It uses the same Radio as the Rogers update and you can keep a recovery and an engineering SPL. I flashed it about a week ago but decided to fight to keep my CM. It takes some radio and spl flashing but its very simple.

http://briancrook.ca/magic/rogers/rogers-wiped.zip

That is parts of a nandroid I did before I rooted my phone back in the summer. I believe thats just the system and the boot.img. My suggestion is CursorSense though.
[myTouch 3G, Magic Android Development] DThor:
Thanks bcrook, I'll give it a shot...

DT

Installation was easy enough...just waiting a day to see if Rogers comes through...

Thanks again

P.S. Ugh, I can see why sticking with CM is best if you can. Seems to be all sorts of almost political stuff going on here - like not allowing users to run task killers, because the modder 'handles it himself' and doesn't want you screwing around with it. My wife couldn't give a toss, but I'm hugging my CM phone right now...
[myTouch 3G, Magic Android Development] xaueious:
I flashed it using post #6 of this thread: http://xdaforums.com/showthread.php?t=622129

I don't know how to extract the radio.img from the nbh image.

I have not looked at my logs, but everything seems to be stable on CM. Still on 4.2.13 until the bugs iron out themselves on .14
[myTouch 3G, Magic Android Development] The Transporter:
This is the fastest ROM I ever tested !!!! I love it ! I'll never update !
[myTouch 3G, Magic Android Development] :
Brian,

For Rogers users, it looks like we still need to apply the netfix2 / 3 or just update the build.sapphire.prop and build.trout.prop files with the correct ro.build.id.

Please confirm.
[myTouch 3G, Magic Android Development] bcrook:
It doesnt appear that the "scans" are actually looking at the build numbers. It sounds like its a radio thing. Magic users, thats annoying because you need to flash CursorSense and revert back to this after you get data, or wait for a CM port on 6.x

Dream users can just flash the radio and keep their SPL. This will get you data back, it doesnt seem like any data is being revoked.

I pulled the radio.img out of the NBH from Rogers

http://briancrook.ca/magic/rogers/dream_update/

(the system.img and boot.img are from the updated there too)
[myTouch 3G, Magic Android Development] :
Thanks.

Is the radio version or port that difficult of code to work with?

Or is it just a priority thing for devs?
[myTouch 3G, Magic Android Development] bcrook:
I believe its the fact that we dont have a compatible open source 2.6.29 kernel. Maybe if smarter people were working on it...
[myTouch 3G, Magic Android Development] Fedio:
Thanks a lot for the radio image...

but just to be clear, I have a dream, i'm using cyanogen and would like to flash the new radio... can I just go ahead using fastboot and all the rest stays the same, with no compatibility issue?

Thanks
[myTouch 3G, Magic Android Development] bcrook:
Yeah, people have been flashing the full dreamimg.nbh and then flashing cyanogenmod and this port file :)
[myTouch 3G, Magic Android Development] :
just wondering if i can use this kernel port over my super D 1.7 rom? (32A)

thanks....:)
[myTouch 3G, Magic Android Development] olvap377:
hi bcrook any news on super d 1.8 port?

btw

for the guy above here is the 1.7 port

http://briancrook.ca/magic/bc-superD17-ebi1-signed.zip
[myTouch 3G, Magic Android Development] kzin:
Modified netfix3

So I had the same idea as frency123 in post #674, so I downloaded the help file that had a screenshot of what Roger's expected. Last week I created a patch based on bcrook's update, but I updated a few other things. Changed kila to htcdream etc, because I noticed on my Exchange server it had a history of phones I connected with. It was showing "htcdream" then "TMobileG1" then "kila". I assumed if my Exchange could see this, Rogers could too.

Ok so I flashed and 'net never came back. But then I connected to online chat support and said I ran the update. They said it would need to be escalated to Tier2 to check whether or not I had run it. I said sure. 2 days later it still wasn't working, so I contacted them again via chat and they said "Its been 48 hours so Tier2 must have gone ok" and must have run my network refresh for me. Battery out and back in, I've had data since Friday =) (KNOCK on wood).

Lets hope they aren't following this thread to come up with fancy fixes to circumvent the fixes we come up with.

I've attached it if you want to try it. HTC Dream only.
[myTouch 3G, Magic Android Development] bcrook:
It actually is appearing that the radio version is what they are looking at. Many people have reporting flashing the 3.22.26.17 (?) radio for the Dream and having data back within 24hrs...just FYI.
[myTouch 3G, Magic Android Development] psycotic11:
can you elaborate? do i have to flash back to stock rogers somehow and apply their update?

Magic 32A here
[myTouch 3G, Magic Android Development] laxros:
I don't how long this will keep...

But what I did was put my sim into my old Blackberry and said I didn't have data access and that I switched it from my HTC device on the weekend and then the lady from the Blackberry queue got it up and running after I pulled the battery out (I also pulled the sim to give it that extra bit in case it was needed) and after it was up and running, plugged it all back into my stock

Magic (waiting to figure out who's ROM that I should go to before making the plunge as my Dream was AWESOME) and within 5 minutes had internet access. I'm pretty sure if they do another scan I'll be taken off, but until that time - I'm good to go. Now I just need to figure out how I can get them to credit me the data for the one month that I've been reading about on some sites.

Why is it WAY easier to (or at least it seems to me) upgrade the Dream than a Magic to these awesome ROMS that others have graciously created for us? I'm finding it harder to do this on the Magic (hence why I haven't jumped into the deep end yet) and I believe I've got one of the perfected SPL's, so hence why I'm a bit more nervous in attempting the switch over to a Cyanogen Rom or someone else's for that matter.

Awesome work you've been doing Brian...wish I had half the smarts you did so I could understand alot of what it takes for you to come up with how to do these transitions for the rest of us.

Later.
[myTouch 3G, Magic Android Development] :
Hey bcrook,

What radio version are you on?

What radio version do you use when you flash OpenEclair?

Do you know if OpenEclair supports or is compatible with any of the newer 6.x 32A Sapphire radio versions?

Thanks as always
[myTouch 3G, Magic Android Development] :
i would love this too....any help to port super D 1.8 with latest cyanogen 4.2.14.1 kernel?

thanks in advance:D
[myTouch 3G, Magic Android Development] :
Ignore this last question.

I just noticed your tweet asking HTC for the kernel source code for the 6.35.x Magic.

http://twitter.com/bcrook88
[myTouch 3G, Magic Android Development] bcrook:
Magic users can just flash CursorSense until they get back and then revert to the 3.x radio and run CM again.
[myTouch 3G, Magic Android Development] bcrook:
Take my latest port file, extract the boot.img into boot.img-ramdisk and boot.img-kernel. Switch the ramdisk with the one from SuderD 1.8. Repack, rezip, resign.
[myTouch 3G, Magic Android Development] polaroid22:
Lost data :(

Last week I got a network refresh and got data and I was with bcrook netfix. Yesterday I've flashed my dream to with full dreamimg.nbh, so, I've boot in rogers's 911 rom and 3G data. After that, reflash CM with last port with still 3G. But this morning it seems I got a rescan and they turn off my data.

Anyone else got this?

I'll probably try bcrook netfix again or kzin's netfix (post 711)

*edit* Nevermind... shutdown, pulled down battery and reboot, data is back... weird.
[myTouch 3G, Magic Android Development] :
tried this....i use the kernel and repack with ramdisk extracted from super D 1.8..and resigned the package

but after flashed into the phone, it stopped at htc magic logo...logcat shows nothing just --waiting for device--

any help would be greatly appreciated:confused:
[myTouch 3G, Magic Android Development] celloin:
CM-4.2.14.1 BFS

Please thank r3pek for this BFS port and for teaching me how to do them in the future. Please note that cyanogen hasn't built a BFS version for a few versions because apparently its is crazy buggy. Good luck to those who run this!

works perfect. Thank you all. r3ped & bcrook
[myTouch 3G, Magic Android Development] :
never mind...after some trials & errors....i finally got a working port with this latest kernel 4.2.14.1 + NexusSuperD18-blk.zip

now I have multitouch on super D 1.8...yay!!! :D

thanks brook for your idea!!
[myTouch 3G, Magic Android Development] kzin:
K I flashed just to be sure, all I did was the radio.img_stock, I was running 3.22.20.17.

$ fastboot flash radio radio.img_stock
sending 'radio' (21504 KB)... OKAY
writing 'radio'... OKAY
$ fastboot reboot-bootloader
rebooting into bootloader... OKAY
[myTouch 3G, Magic Android Development] xaueious:
Okay I just flashed the BFS and am booting Cyanogenmod 4.2.14.1

I also installed adb now so I have logcat to tell me if the thing is actually still booting.

Edit: Installing BFS 4.2.14.1, performance increase is VERY NOTICEABLE. I don't know if they fixed something broken or if it is because of the BFS. You really have to see for yourself. Running stable over here.

4.2.14.1 seems to have fixed one the shut down error I had recorded with logcat about some end of file error. I didn't record it and I don't have another 40 minutes to swap back that Nandroid backup to figure it out. The only thing I don't like is the DeskClock.

Edit 2:

Unstable even after fix permissions. Some apps are having problems. Hopefully I just need to install this properly.

Cyanogenmod updates (flash over) have never worked for me in the past without issues. Lets just hope that was it.

Edit 3:

BFS breaks my Chinese IME. No go.

Motorola CIME.

Logcat shows no outstanding errors. Weird.

For the BFS patch, is there is a reason why the keylayout files were patched? I think that probably broke my CIME.

Ideally I can have a BFS for CM 4.2.13 since that has been rock solid for me so far that works with CIME

Can someone figure out the 10MB hack? I'm really interested in that.
[myTouch 3G, Magic Android Development] Survivor.Sole:
Im having a lot of troubles with this last release.

I got late at work 2 twice. Alarm clock does not work...

Some reboots, etc.
[myTouch 3G, Magic Android Development] polaroid22:
I've used "new" alarm clock this morning and all is fine, alarm clock is now in clock icon and no more "alarm clock" icon.

I'm using BFS port and new radio on my dream.
[myTouch 3G, Magic Android Development] kapsidi:
Alarm clock works...you have to keep "Clock" app alive though. Don't let any taskmanager you use kill it!
[myTouch 3G, Magic Android Development] Survivor.Sole:
Ok. Im talking about new alarm. It´s does not work with me. Strange.

I have setup two alarms. One for mon, wed, frid and another to thusdays.
[myTouch 3G, Magic Android Development] bcrook:
Keylayout files have been patched for the past few months because it fixed the volume-keys-working-while-phone-is-off issue. They have been in the CFS version the whole time. I am not sure if they are still required, they may have been included in CM by now.
[myTouch 3G, Magic Android Development] xaueious:
That's an issue? I liked that feature actually.

I pushed the BFS boot.img to my 4.2.13 and my Motorola CIME still works, by the way. But once I flashed the entire zip it the CIME just fails to load at all.

So I have the BFS kernel on 4.2.13. I did not notice as much of an improvement in speed as wtih BFS 4.2.14.1, so I think there's some sort of speed improvement with the new Cyanogenmod. But I can't stand the new alarm clock. It breaks my clock widget, and I don't know how to fix it. I suspect I can make some sort of symlink to it, but I don't really know how.
[myTouch 3G, Magic Android Development] bcrook:
The issue was that the buttons didnt work.

I will see if the correct files are included in CM and will remove them if they are. Keep in mind you can easily remove the boot.img from my port package and fastboot it. It should work with the wlan from the CFS port package.
[myTouch 3G, Magic Android Development] Macmee:
This is driving me nuts!

I am running a working cyan on my dream rooted ebl1. I flash the new rom and new kernel port and its stuck on the rogers screen every time. I was updating fine up until version 12 :confused:
[myTouch 3G, Magic Android Development] bcrook:
That's odd. Can you boot into fastboot mode (Power+Camera) and type what you see there?

Let's see if we can figure out what's up.
[myTouch 3G, Magic Android Development] xaueious:
Do you know how to run a logcat?

It might just be working but taking a very long time.

Try clearing your Dalvik cache
[myTouch 3G, Magic Android Development] alvinistic:
I tried the BFS version of 4.2.14.1. It feels faster, but I have an issue with it. The music player sometimes will automatically unpause music when I launch it. The button is still play button and there is no icon in status bar, but the music plays. I have to stop the music by pressing the button twice (play and pause).

I can reproduce the issue by:

- launching music app

- play music

- pause music

- launch gallery etc

- kill the gallery with taskiller

- launch the music app

For the time being, CFS is good enough though :)
[myTouch 3G, Magic Android Development] hyoo82:
flashed radio to...

I flashed my radio to the dream 3.22.26.17, The Theory is they are just checking the radio bands? I should have data back within 24H?
[myTouch 3G, Magic Android Development] bcrook:
Hopefully. It seems to have been working that way for people.
[myTouch 3G, Magic Android Development] hyoo82:
Woops forgot to mention I'm running an HTC 32A magic
[myTouch 3G, Magic Android Development] bcrook:
You flashed the 3.22.16.17 dream radio on a Magic? That worked?

Chances are for you to get data back you will need to flash the 6.x radio because that's what they'll be expecting for magics.
[myTouch 3G, Magic Android Development] hyoo82:
I flashed the radio in fastboot I've got 3.22.26.17

Still nothing yet, We'll see how it goes.
[myTouch 3G, Magic Android Development] Macmee:
I'm not sure what that stuff means:p

It says:

DREAM PVT 32B ENG S-OFF

HBOOT-1.33.2005 (DRE21000)

CPLD-4

RADIO-3.22.20.17
[myTouch 3G, Magic Android Development] vincentkosasih:
just upgrade to this rom, be4 using ver 4.2.13...

not much improvement, but still smooth...

:Dbtw, where i could find the change log?

thx anyway...
[myTouch 3G, Magic Android Development] beav_35:
http://wiki.cyanogenmod.com/index.php/Logcat

You can wipe Dalvik cache through RA recovery. Not sure about CM though.

Second post here: http://xdaforums.com/showthread.php?t=567610
[myTouch 3G, Magic Android Development] xaueious:
I would really like to see some 10MB ram hack builds for the G1 someday. I would rather see a build of that rather than the BFS build.

I rarely use 3D apps and I really see how the G1 needs that ram.

It would be nice :)
[myTouch 3G, Magic Android Development] xaueious:
New issue actually sorry for double post

SPL 1.33.2005

Cyanogenmod 4.2.13

4.2.14.1 EBI1 CFS kernel

3.22.26.17 radio

SDCard no longer reads

I have detailed this problem here http://xdaforums.com/showthread.php?t=623431. I haven't booted to my main system because I don't want to screw it up, so I can only report that this is a problem in recovery (RA-dream-v1.5.R)

Whenever you are free I would appreciate the help. Right now I can't use my phone.

I'm not sure if this is a result of my using the 4.2.14.1 EBI1 kernel.

I am wondering if this has to do with flashing the radio AFTER installing the SPL. Am I supposed to reinstall SPL?
[myTouch 3G, Magic Android Development] Macmee:
Here is my log file:

http://macmee.com/android/log.txt
[myTouch 3G, Magic Android Development] bcrook:
If you havent wiped dalvik cache and done a fix UID mismatches from recovery,do that. If that doesnt help you will likely need to wipe, reflash defanged base, ROM and port file.
[myTouch 3G, Magic Android Development] jgalea:
Dialer

Can someone point me to how I can replace the dialer on this ROM to the one that does the searches in the contacts when your typing digits? I really miss that. Other than that, I positively love this ROM. The port to EBI1 was a brilliant idea!
[myTouch 3G, Magic Android Development] maymaymay:
Search the Market for aContacts.
[myTouch 3G, Magic Android Development] xaueious:
Just checking with devs here.

How updated is the guide for building the kernel port located here: http://wiki.cyanogenmod.com/index.php/How_to_build_a_kernel_port

I try to would like to build my own kernel ports for my EBI1 Dream.
[myTouch 3G, Magic Android Development] Rede83:
Is there a way to port this to the 3.65 radio? I'm hoping maybe that would end the endless frustration of Rogers repeatedly cutting off my service.
[myTouch 3G, Magic Android Development] bcrook:
You mean 6.x radio? So far, no.
[myTouch 3G, Magic Android Development] Rede83:
Yeah, sorry, 6.35. Was worth a shot :)
[myTouch 3G, Magic Android Development] bcrook:
Yeah - it is up to date. Lemme know if you have questions.
[myTouch 3G, Magic Android Development] jgalea:
Dialer

That's not bad, thought exactly what I wanted. What I was looking for was to replace the existing dialer with one from another build that had the search in it. Any other ideas?