yashsingh1/xdaforums huggingface dataset:
[myTouch 3G, Magic Android Development] metalelf0:
Already tried this... sorry for not specifying this in my previous post. I've never tried with the 1.6 HTC base though. Should I?
[myTouch 3G, Magic Android Development] bcrook:
Are you using A2SD? Swap? Have you tried switching/formatting your sdcard?
[myTouch 3G, Magic Android Development] metalelf0:
Yes to A2SD, no to swap. I've already tried formatting the SD card to only FAT without any change. I also ran a fsck on it, and it show no errors, so I think the card is ok.
[myTouch 3G, Magic Android Development] konstantinosmis:
Hi! Maybe you could add live walpapers support on your new rom like nexus one?
[myTouch 3G, Magic Android Development] bcrook:
I was just thinking about that. We considered it when I was doing entire ROMs and decided against it. But now, with just the port file, it may be possible.

We can talk about it for sure.

I only use a single fat32 partition, I dont think the 32As need the apps2sd or anything. My understanding is that nandroid backs up the on-phone partitions only (ie. /data, /system, etc). I believe BART backs up your ext partition as well.
[myTouch 3G, Magic Android Development] trujap:
AWESOME! Thanks guys!

oh and another quickie... I want to change the keyboard to something more HTC hero like. I've tried the HTC_IME.apk directly on the phone through astro and it installs but the keyboard is the same still. Any suggestions?

thanks!
[myTouch 3G, Magic Android Development] bcrook:
Dont think CM-Updater will work for now. Sorry.
[myTouch 3G, Magic Android Development] Charrion:
Awesome work man, you are a scholar and a gentleman. Any chances you might be porting RA 1.4.0 recovery to EBI1? I tried flashing the regular one yesterday but it just hangs on the boot splash. Or is there some trick to this? So far the only recovery image I've managed to get to work since going with the EBI1 kernel and radio is the one downloaded by flashrec.
[myTouch 3G, Magic Android Development] bcrook:
Just wait for Amon_RA to port it. We are usually a week or two behind but it is coming.
[myTouch 3G, Magic Android Development] The Compiler:
eh? Wouldn't that apply the port file first? *confused*

Florian
[myTouch 3G, Magic Android Development] bcrook:
Apply just means reboot to recovery.
[myTouch 3G, Magic Android Development] cursordroid:
Every time I try the Apply Now option, it reboots to recovery and installs the update.

Because the CM Updater stores all updates in /sdcard/cm-updates I can't get at them unless I move them to /sdcard/
[myTouch 3G, Magic Android Development] bcrook:
You are right. This process may not work. I probably should've actually tried it...i was trying to avoid

a) Asking the cm-updater devs to make a port section or something

b) Making a full ported ROM (which I will not do).

If anyone has any ideas, let me know.
[myTouch 3G, Magic Android Development] FernandoMiguel:
i had it happen to with 4.2.5

havent tested on 4.2.6
[myTouch 3G, Magic Android Development] FernandoMiguel:
try anysoftkeyboard. best keyb i know. and it has swipe each i love, multilanguage, and easy access to any language at any time
[myTouch 3G, Magic Android Development] FernandoMiguel:
every time i change from 2G to 3G and vice versa I loose signal and have to enter in AirMode and back for it to work.

also WiFi will stop working after a while, when screen is dimed.

with 4.2.5 it would be ON for hours without any probs.
[myTouch 3G, Magic Android Development] Tsanger:
Hero Keyboard

To install the hero keyboard, which files do I download from this site?

http://n0rp.chemlab.org/android/apps/

Do I download the md5sum files or the ones with out it?

Thanks
[myTouch 3G, Magic Android Development] ranger79:
Encounter bootloop using 4.2.7 port file.

Use back 4.2.6 port on 4.2.7 ROM works fine now.
[myTouch 3G, Magic Android Development] bcrook:
Really? Can you redownload 4.2.7? It works perfectly for me.
[myTouch 3G, Magic Android Development] ranger79:
Redownloaded 4.2.7 but still the same.

Edit: Tried 4.2.7 BFS on 4.2.7.1 ROM and it's working flawlessly.
[myTouch 3G, Magic Android Development] evilmerlin:
I can't seem to update to the latest version of Google Maps when using this rom. Something about signing errors. Is there a solution to it?
[myTouch 3G, Magic Android Development] walie:
Here's a question thats been bugging me for a while

Do we 32a users need to setup and use compcache at all? If so, how do you go about setting it up?
[myTouch 3G, Magic Android Development] jayozki:
who can tell me the difference about CM-4.2.7 BFS and CM-4.2.7?

and Cyanogen updated 4.2.7.1...can i use this port for it?

thx~~~
[myTouch 3G, Magic Android Development] hengsin:
4.7.2.1 have been just release, do we need a new 32a port file ?
[myTouch 3G, Magic Android Development] metalelf0:
Looks like something is wrong with my RAM... this is the output of my last_kmsg:

[ 1841.850860] suspend: exit suspend, ret = 0 (2010-01-19 13:16:00.885284402 UTC)
[ 1844.891479] get_smem_clock: exit timeout state 10d29 clock 423281293 in 257 ticks
[ 1845.021575] get_smem_clock: invalid start state 10d29 clock 423281293
[ 1849.676177] Unable to handle kernel paging request at virtual address 1c1c1c30
[ 1849.676269] Unable to handle kernel paging request at virtual address e1a0c031
[ 1849.676300] Unable to handle kernel paging request at virtual address e92dd914
[ 1849.676330] Unable to handle kernel paging request at virtual address e92dd914
[ 1849.676361] Unable to handle kernel paging request at virtual address e92dd914
[ 1849.676391] Unable to handle kernel paging request at virtual address e92dd914
[ 1849.676422] Unable to handle kernel paging request at virtual address e92dd914
[ 1849.676513] Unable to handle kernel paging request at virtual address ea0000c6
[ 1849.676544] Unable to handle kernel paging request at virtual address e51b0074
[ 1849.676574] Unable to handle kernel paging request at virtual address e51b0074
[ 1849.676605] Unable to handle kernel paging request at virtual address e51b0074
[ 1849.676635] Unable to handle kernel paging request at virtual address e51b0074
[ 1849.676666] Unable to handle kernel paging request at virtual address e51b0074

0 Corrected bytes, 10 unrecoverable blocks
[myTouch 3G, Magic Android Development] MMartins:
well,

After about one day with this rom (i was using the original 1.5 that came with my 32A magic) I have some impressions to tell:

- it is better than the 1.5 (this auto tethering is priceless!), don't know if it is because it is 1.6 or CM

- until now doesn't seans that faster than my other 1.5, still stops some times, like writing an sms in horizontal with some apps open it is really slow like in 1.5 (in 1.5 it is all the time, it is a litle improved), i'm on the snd word and the phone is still on the fst.

- multi touch is not that good (pinch to zoom at least), hero rom (original at least) is much faster and precise.

- trackball only lights one time on sms now, i liked like on 1.5 to light every 5 sec (maybe it is 1.6 not CM)

- battery life is the same, 3g almost a day, 2g haven't tested.

- can't unistall mp3 store!

I have 2 apps for mail: e-mail and work mail! what's the difference between them?!

thanks
[myTouch 3G, Magic Android Development] bcrook:
-Wired tethering is ported from Hero and is cm specific

-Speed will be similar-ish - may be faster in some situations. If you came from a Rogers ROM, you wont notice a huge increase

-I agree, MT sucks, its a work in progress - its actually from an Eclair API

-The trackball is an HTC thing - this is a google build. There is an app you can use to make the ball glow, can't really remember the name though

-Mp3 store - you can since it is rooted:

adb remount
adb shell rm /system/app/com.amazon.mp3.apk

Enjoy.
[myTouch 3G, Magic Android Development] MMartins:
thanks for your answer :)

and the 2 mail app what for?

No my rom was from a portuguese provider.

with handcent I think it will glow but handcent is slower than the regular program sms, the think that is more annoying to me in a device is the slow of the write, so it is my batle :)! that is just a bad memory management, we should have the option to actualy close an app and not have to use other to kill it.

and thanks a lot CM!
[myTouch 3G, Magic Android Development] bcrook:
Sorry, missed the mail part - it is for exchange and pop3 and imap and stuff.

There is an app that just controls the trackball light...forget the name though.

I find the stock KB fast and HTC_IME fast IF you turn off the vibrate feature.
[myTouch 3G, Magic Android Development] Vimes14:
Restore Rogers stock TrackBall reminder behaviour

NotifyLight is the application I use to provide reminder trackball illumination for missed calls/SMS. Does not work with email.

Search the forums for the apk as it does not appear in the Market.
[myTouch 3G, Magic Android Development] FazeOwl:
i guess im not the only one having issues with 4.2.13

went back to the 4.2.12.2 and its cleared up the issues i was having...

4.2.13 felt like i was using a tmobile mda... slow as could be, force closes 8 or more times a day, cam would crash 90% of the time after id take a pic. voice mail and text messages barely went through. or couldnt dail out to get my voice mails, battery is draining like crazy... the biggest thing that drives me crazy is the voice dialer would kick on when ever it wanted to.
[myTouch 3G, Magic Android Development] metalelf0:
Can anybody please confirm that

0 Corrected bytes, 10 unrecoverable blocks

means a RAM problem? If so, I will recover the original firmware and send my phone back for replacement.
[myTouch 3G, Magic Android Development] bcrook:
Dunno, sorry.

Join #cyanogenmod on freenode, some people might know there
[myTouch 3G, Magic Android Development] MMartins:
thanks :)

I will search for the program.

I'm using the anysoft keyboard to have portuguese dictionary on the writing, vibrating and sounds always off.

I found a "bug" maybe 1.6, if someone sends me an sms for eg at 2.00 and I have the phone off and turn ir on lite 10 hours later, 12.00 it shows on the time of the sms the 12.00 and not the 2.00.

that is kind of anoying because I cannot see the correct time of the sms and if i send an sms first of the network send the sms's i've received before they will show after mine! on 1.5 it worked good, only the usual timestamp problem...

another thing, i've made an wipe to the battery after a full charge, now it is drawing very fast this is usual right? I should drawn it until the phone don't start and re-charge again right?

thanks a lot
[myTouch 3G, Magic Android Development] MontAlbert:
NOPE. wasnt the lockscreen. i reflashed .13 without the lockscreen adn am still getting reboots for no reason- wasnt even using the phone- i was at work and noticed the screen all of a sudden light up - looked over and it was the boot screen. I now am back to thinking it is the kernel causing the issue.

Anyway, i think i will try out BC's new wesgarner kernel and see if that is more stable....
[myTouch 3G, Magic Android Development] bcrook:
Give it a try - actually haven't had ANY issues. I really have no idea whats causing the problem.
[myTouch 3G, Magic Android Development] zuk_:
Just wanted to confirm, this seems to be the logcat error that results in at least some of the random reboots (this seems to happen when the lockscreen is up and I'm not touching the phone... and usually soon after the phone has been turned on.... it does however randomly reboot all the time, sometimes continuously, but I don't have logcats in those instances, so I'm not sure what's causing it then):

...
I/global ( 374): Default buffer size used in BufferedReader constructor. It would be better to be explicit if an 8k-char buffer is required.
I/global ( 374): Default buffer size used in BufferedReader constructor. It would be better to be explicit if an 8k-char buffer is required.
D/GTalkService( 159): [OtrMgr] OTR not modified
D/dalvikvm( 374): GC freed 3172 objects / 293968 bytes in 101ms
W/dalvikvm( 106): threadid=37: thread exiting with uncaught exception (group=0x4001e170)
E/AndroidRuntime( 106): Uncaught handler: thread WindowManagerPolicy exiting due to uncaught exception
E/AndroidRuntime( 106): *** EXCEPTION IN SYSTEM PROCESS. System will crash.
E/AndroidRuntime( 106): java.lang.RuntimeException: Canvas: trying to use a recycled bitmap android.graphics.Bitmap@43c17a40
E/AndroidRuntime( 106):	at android.graphics.Canvas.throwIfRecycled(Canvas.java:955)
E/AndroidRuntime( 106):	at android.graphics.Canvas.drawBitmap(Canvas.java:980)
E/AndroidRuntime( 106):	at com.android.internal.policy.impl.LockPatternKeyguardView$FastBitmapDrawable.draw(LockPatternKeyguardView.java:602)
E/AndroidRuntime( 106):	at android.view.View.draw(View.java:6534)
E/AndroidRuntime( 106):	at android.widget.FrameLayout.draw(FrameLayout.java:352)
E/AndroidRuntime( 106):	at android.view.ViewGroup.drawChild(ViewGroup.java:1531)
E/AndroidRuntime( 106):	at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1258)
E/AndroidRuntime( 106):	at com.android.internal.policy.impl.KeyguardViewManager$KeyguardViewHost.dispatchDraw(KeyguardViewManager.java:85)
E/AndroidRuntime( 106):	at android.view.View.draw(View.java:6552)
E/AndroidRuntime( 106):	at android.widget.FrameLayout.draw(FrameLayout.java:352)
E/AndroidRuntime( 106):	at android.view.ViewRoot.draw(ViewRoot.java:1332)
E/AndroidRuntime( 106):	at android.view.ViewRoot.performTraversals(ViewRoot.java:1097)
E/AndroidRuntime( 106):	at android.view.ViewRoot.handleMessage(ViewRoot.java:1613)
E/AndroidRuntime( 106):	at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 106):	at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 106):	at com.android.server.WindowManagerService$PolicyThread.run(WindowManagerService.java:511)
I/Process ( 106): Sending signal. PID: 106 SIG: 9
[myTouch 3G, Magic Android Development] MontAlbert:
are you using a kernel you made or the radix one?
[myTouch 3G, Magic Android Development] bcrook:
Radix one - he does great work. Try the wg-kernel.
[myTouch 3G, Magic Android Development] MontAlbert:
hehe yeah i know... for a dodgy west Aussie :D

i think i just need to do another wipe and start from scratch but i cant be stuffed atm.... will try the WG kernel....

***edit*** now thinking my Magic is stuffed.... i loaded ahmgsk's Eclair GenX rom and that was a clean load... and i had a couple of random reboots in the hour or 2 i had that on.... same error log....

not sure whether i should try and return it under warranty (obviously will have to return to stock first)....
[myTouch 3G, Magic Android Development] bakavic:
I think I'm a bit late to the party, but I'll chime in :)

The fix seems to be ok so far for me. I'm on M1 in Singapore, and I also had the double carrier problem, which this fix solves.
[myTouch 3G, Magic Android Development] SpaceBoy2000:
Rogers Mandatory 911 Update

I was wondering, since you're on Rogers as well bcrook, how are you getting around the mandatory 911 update? I really want to stick with Cyanogen, so, is there any alternative or am I basically screwed and have to update?
[myTouch 3G, Magic Android Development] bcrook:
To concerned Rogers users:

Rogers will be scanning the network looking at the ro.build.description line in the build.sapphire.prop and build.trout.prop files. It must be > 1.89 for you to "pass" the network test.

I have created a build.{sapphire,trout}.prop with the modified lines but I have no way to test and NO idea if it will work.

If you guys want to test it and see what happens, you are welcome to.

Option 1:

Flash this as an update.zip in recovery

Option 2:

Go to http://www.briancrook.ca/magic/

Sapphire Users:

Right click on the build.sapphire.prop_rogers and save link as. Then:

adb shell reboot recovery
***Wait for it to boot to recovery***
adb shell mount -a
adb push build.sapphire.prop_rogers /system/build.sapphire.prop
adb shell reboot

Dream Users:

Right click on the build.trout.prop_rogers and save link as. Then:

adb shell reboot recovery
***Wait for it to boot to recovery***
adb shell mount -a
adb push build.trout.prop_rogers /system/build.trout.prop
adb shell reboot

Again - I have NO idea if this will work. I hope it does.

For those of you who want to use the Rogers ROM and pass the test relatively legitimately, check out CursorSense 1.2

http://xdaforums.com/showthread.php?t=592856
[myTouch 3G, Magic Android Development] SpaceBoy2000:
Thanks bcrook, I've loaded it and I'll get back to you if it does work.
[myTouch 3G, Magic Android Development] CalvinW:
Followed your instructions on my Dream, no changes from the About Phone screen, not sure if there should be though.

If this works you'll officially be a hero. Thanks!
[myTouch 3G, Magic Android Development] playingdoh:
the "fix" looks to have worked, its now 6:55am and I still have 3G. i just feel bad for all the people who installed the perfected spl. I wonder how long rogers script will take to "do its thing"? Ill report back if anything changes.

Is there anyone in the Hamilton area who didnt downgrade or spoof that lost there 3G yet?
[myTouch 3G, Magic Android Development] :
Although I did not use bcrooks patch I used one almost exactly the same and I still have 3G on 2 magics and a dream.

Thanks for the work bcrook it appears it works!
[myTouch 3G, Magic Android Development] SpaceBoy2000:
I'm posting this using my Magic over 3G. So, it looks like your simple fix worked bcrook. Congrats and thanks a lot!
[myTouch 3G, Magic Android Development] bcrook:
So, its 10.15am in Ontario, which means it is after 6am everywhere in Canada and i have 3g on my cyanogenmod Magic. Either Rogers bailed OR we beat those f*ckers....
[myTouch 3G, Magic Android Development] stilbon:
Morning all,

I'm on CM and I figured I'd wait until they smoked me out.

It's about 11:15am here in Winnipeg - I turned off my wifi at about 10:30am and still had 3G access, but by 10:45am it was gone. Either my timing was 'perfect' or they had a look at my phone once I connected.

I've thrown in your patch on my Dream and I guess I'll wait with everyone else to see if it all comes back up.

Thanks all your work bcrook, I wish us all luck!
[myTouch 3G, Magic Android Development] beatryder:
Mine was down for a little while, but it seems to be back up now.

I'm on Cyanogen 4.2.13 and also running Danger SPL and radio.
[myTouch 3G, Magic Android Development] CalvinW:
I'm still going fine running Cyanogen with bcrook's patch on my Dream. I've read somewhere that the check is done when the devices attempts to acquire an IP, so it would make sense that it happens when swapping from wifi, rebooting, after losing a connection, etc.

Not 100% sure if that is how it happens though, there are also people talking about them "scanning" the devices. It might also be a combination of these things I suppose.
[myTouch 3G, Magic Android Development] Wulfbane:
3G working even after reboot, 32A running older CM 4.2.7

I have a 32A Magic running an older version of CM 4.2.7. I'm in Burlington and 3G still works for me. Takes a few more seconds to establish a connection when resuming from lock screen.

Going to try a full reboot...

...3G still works!
[myTouch 3G, Magic Android Development] Curaxa:
I try to apply bcrook's fix when I run adb shell mount -a I get

Any ideas?
[myTouch 3G, Magic Android Development] bcrook:
Thats fine. Just use the update.zip form - just changes the build.prop files.

Dont think it works - lost 3G/EDGE around noon EST today.
[myTouch 3G, Magic Android Development] Curaxa:
That's too bad. I was hoping to not get back to the stone ages on my Dream again and possibly not ever come back out. I'll have to wait to see if there are other fixes but I do need my internet back on my dream outside of wifi zones so I may have to give in. Thanks for the hard work and the try bcrook, it was well appreciated.
[myTouch 3G, Magic Android Development] CalvinW:
bcrook, I had the same errors as Curaxa when I attempted it. I ignored them and proceeded with the other steps and it seemed to work. Is there a way to check if it was properly applied?

EDIT: Just lost my 3G, still hoping it is that everyone loses it then they start turning it back on...
[myTouch 3G, Magic Android Development] :
3G still working fine here in Smiths Falls at 2:30, patched one in Markham that is still working too. Used my patch but was basically the same as bcrooks.
[myTouch 3G, Magic Android Development] bcrook:
From my understanding (after reading the text and talking to a Rogers Tech Support guy) EVERYONE loses data for 24hrs. People will then start getting data back IF you pass their update check (whatever that is).

People using my "patch" do the update.zip method. The way to confirm is to check the About page - the Build Number SHOULD have DRC92 3.03.... on it. That is just a cosmetic thing I but in to see if the flash worked. You could also pull the build.sapphire.prop from the device and see if there is a 3.03... number in the ro.build.description line.
[myTouch 3G, Magic Android Development] Curaxa:
I know that my sister did the patch and she never lost her internet where as I did without the patch. I've applied the update from bcrook but my build number is still DRC83. I'll check the prop file later but running a Dream should I check the build.sapphire.prop, build.trout.prop, or build.prop (though I will likely check all three). Also, srlee, would it maybe be possible for you to link your patch? I have faith in bcrook but hey, if there is a working fix out there, less work for him.
[myTouch 3G, Magic Android Development] CalvinW:
brook, I am also DCR83 as my build number after applying your patch on my Dream. This was after both using adb and the update.zip method.

I don't mean to be a pest but any help would really be appreciated.:)
[myTouch 3G, Magic Android Development] bcrook:
Thats just cosmetic. I am working on a refined one.

UPDATE:

I just went on the Online Chat, I waited just over an hour and got a rep. I asked for a network reset and said that I updated. The support guy said I had to wait for 24hrs, I asked again, then he said network was all back-end, I asked again and he said he could do it but warned that it might cause issues when it is automatically re-enabled (which it won't be cause I am running CM).

Everyone try it - it should work eventually.
[myTouch 3G, Magic Android Development] SpaceBoy2000:
Welp, looks like I spoke prematurely, and I've lost 3G. Oh well, 24 hours eh?I can live that long on WiFi.
[myTouch 3G, Magic Android Development] fkung:
Should I take recent comments to mean that simply overwriting the build number will not work automatically, and I need to call them? Or is there still hope? =)

(one thing I'll also note, for some reason my phone has a /system/build.prop file in addition to build.sapphire.prop, and I needed to edit the build.prop file to make the changes show up on the "About" screen. Don't know which file the backend build number is read from...)
[myTouch 3G, Magic Android Development] mlav:
I' ve solved the 3G/data lost connexion issue by doing the following:

1. Using bcrook's patch

2. Online chatting with Rogers tech support, telling them that I have an updated custom ROM without the 911 problem; the tech asked me my build number (3.05.631.7), then to remove the battery for little less than 10 min., then to put back the battery and reboot.

What I wonder right now is if the problem could have been solved automatically (waiting for the Rogers script to find my patched ROM or just by removing the battery for 10 min without calling them) and if the tech could have reactivated my 3G/data connexion without bcrook's patch...
[myTouch 3G, Magic Android Development] kubaczka:
Is there any way to fix that laggy keyboard? When I'm typing fast, it's damn choppy - keyboard is missing a lot of letters, so I have to really slow down. When I was using AmonRA RAV ROM keyboard was smooth and nice :|
[myTouch 3G, Magic Android Development] bcrook:
Which keyboard? The HTC one is much faster if you turn off vibration.
[myTouch 3G, Magic Android Development] kubaczka:
Default Cyanogen keyboard, turned off vibration and beeps.