Jump to content

MCR r22.1 archive


Recommended Posts

Guest internettoughguy
Posted

Yup, Kitchen not working for me either. Get the same error as the members above.

Guest muncheese
Posted (edited)

I updated to the latest radio after I flashed this rom and now I'm having high cell standby usage. About the same usage I was getting with the first stock antenna. The OTA update fixed that for me.

So I'm back to square one in terms of cell standby usage. Anyone else in a similar situation?

Cell standby and Idle time are identical in terms of usage both 37%. =/

Edited by muncheese
Guest Kruzkal
Posted

As a fellow Brit is there any chance of an option to swap the £ and the $ symbols on the keyboards in your next builds Paul?

Guest internettoughguy
Posted

Kitchen issue just for US members perhaps?

Guest nexvision
Posted
Kitchen broke for me as well.

Kitchen for 1.9 broke as well so its all of em it appears still calling to bake.php

Guest Klarato
Posted

Hey guys,

Has anyone had an issue with the latest build in trying to search for mobile networks?

I tend to roam off my normal network alot so when im at certain locations i just set it to roaming so it doesnt bonce back and forth.

Although since the update it comes up with error searching for networks. And sometimes when it automatically trys to register me to networks it comes up as Your SIM is not aloud on this network O_O!

Lost reception for a good 25min last night since it wouldn't seem to let me connect to the roaming network for some reason =/.

Anyone had anything simular happen over the last few builds?

I'm in Australia on the Three network btw and i flashed A14 with radio in the bake.

-Klara

Guest JonnyRockets
Posted (edited)
Maybe I am just totally confused. I logged on to phone browser. I am at the URL www.google.com/voice

I even was asked to log in again with Google user name and password. I am at screen now that says Mobile with a phone icon top left and it shows my google phone number correctly. I type in a quick phone number to call. The screen changes to call the number with:

phone 1: (my cell number):(my cell number)

IOW, it will call using my cell number instead of using google number at top of this screen.

IF... I use my method of calling my google voice number, the enter in my 4 digit in, and then enter in the number 2 and the phone number I chose as a quick call, this is completed by calling with the google voice number which is registered correctly with caller ID on the phone I am calling. Where am i going wrong with this.

<sigh>

I don't think you understand what Google Voice actually is... :mellow:

It's just a forwarding service.

Anyway, for using www.google.com/voice, you click contacts, you select who you want to call, and THEN, this is the important part

  1. GV calls YOU


  2. GV calls the person.


  3. It connects the two.
The difference is that the other person sees the caller ID as YOUR GOOGLE VOICE NUMBER. <_<

If you have access to another phone (work phone, wife, friend, Skype-In, etc), call the other number using www.google.com/voice and look at what the caller ID shows up as.

Edited by JonnyRockets
Guest PhonePersona
Posted

Found a bug!

Using the default messaging app on this ROM you get a Force Close if you try to record an audio attachment.

I haven't tried doing this if the voice recorder is absent, nor have I tried with the HTC messaging application.

I tried baking a ROM for testing this out, but I too am getting errors once I hit 'Bake' <_<

Somebody done burned down de kitchen!

Guest craskman
Posted

Hi Paul,

Nice work and thanks for share this rom. I just would like to know a little bit about this ROM that was leaked, did you get the sources or are you smali > java all these bits that you are fixing?

Thanks, keep up your good work

Posted

Kitchen fixed, apologies peep!

craskman - never any sources for HTC ROMs! So, it's a case of fixing how you can using a variety of methods, including baksmali/smali amongst others yes!

P

Guest Jak Crow
Posted

I did a clean install of a14, and so far, I've had two complete lock ups of the phone that needed the battery pulled to fix. I've reverted back to my a13 backup.

Guest michi770
Posted

Has anyone a link back to alpha 12?

Thanks

My Friend Stream does not work :-(

Guest argylesocks
Posted
Yeah, wait for HTC to fix the Camera app in a future beta. N1 Torch works so it's not a ROM issue.

P

I saw the question asked, but didn't find an answer... .can we install the camera.apk from cyan's .zip to replace the broken one??

Love this ROM, Paul... but I do miss the camera flash.

Guest Docmjldds
Posted
Wow, what do you have running, I get much better than that on this ROM. I have the same setup as I did running MCR and only main thing I do is use setcpu to limit the CPU in standby.

I believe it's a defective battery. I already contacted Seido on this for a replacement. But I do have a tendency to run a bunch of apps in the background. I do have advanced task manager. I just get lazy at times in using it.

Guest Docmjldds
Posted
Kitchen fixed, apologies peep!

craskman - never any sources for HTC ROMs! So, it's a case of fixing how you can using a variety of methods, including baksmali/smali amongst others yes!

P

Paul, any concern you are limited with what you can accomplish with this Alpha when TMob is announcing I believe around March 27th in the UK, the Desire? Not meant to be a comment at all on your work. Being a plus member here, I really appreciate the time you take to provide us with everything you do.

Guest taz5176
Posted

thx paul for the rom, GOOD JOB!

hope to c more coming!

also hope that the default sense usb connection feature works in future release

Guest Docmjldds
Posted

If you have access to another phone (work phone, wife, friend, Skype-In, etc), call the other number using www.google.com/voice and look at what the caller ID shows up as.

Guest DistortedLoop
Posted
I did a clean install of a14, and so far, I've had two complete lock ups of the phone that needed the battery pulled to fix. I've reverted back to my a13 backup.

A14 was the first try of this ROM for me. First boot was okay, but then something crashed after playing with it for a while, and 3 separate reboots all resulted in having to do a battery pull somewhere between the lockscreen first showing up and actually getting launcher to open after the lockscreen.

I ran a logcat on the phone during one of the boots if that would be helpful.

After three failed attempts to even get the phone started again, I just ended up wiping and going back to CM.

Not sure I was that impressed with Sense, it's definitely flashier, but I don't know about being more functional FOR ME.

I really liked the camera app, though. I haven't read most of this thread, but I was able to set the camera to 5mp - I thought this one was limited to 3. Anyways, awesome face recognition, and the iPhone-like tap-to-focus feature is sorely missed in the Google stock camera. This ROM/Camera still had that frickin' pink blur problem on my phone, though.

Guest JonnyRockets
Posted (edited)
If you have access to another phone (work phone, wife, friend, Skype-In, etc), call the other number using www.google.com/voice and look at what the caller ID shows up as.

I do have access. I have Vonage and two independent phone lines. Using www.google.com/voice on my phone and calling my Vonage alternate line, called ID shows my original TMobile cell number...NOT the google voice number. IF.....I use my N1 and call my google voice number, I enter the 4 digit pin number when prompted, enter 2 to place a call, call the same Vonage number and NOW...Google voice ID shows up on the Vonage line I just called. Yes..I know Google Voice is basically a call forwarding service. I guess I will do what works for me. Maybe, when GV quit working way back with Alpha 7 and I went thru the trouble of actually getting a new (different) Google voice number. and manually changed the call forwarding setup on my phone, it changed something wrt my account setup. Don't know.....

That's impossible.

Or you're doing something wrong.

Ok, try this:

Go to www.google.com/voice *on your PC*. Click call and try it.

On the phone you're calling to, does it still show your cell phone number or GV #?

Edited by JonnyRockets
Guest rasmusjv
Posted (edited)

Nice ROM Paul :-)

But is there a chance that the "Camera Flash" will be fixed any time soon (it's totally off). The flash goes off before the picture is taken :-( resulting in dark pictures, is there a fix for this?

- RasmusJV, Denmark

Edited by rasmusjv
Guest DistortedLoop
Posted (edited)
I have gone from 12 hours down to 6-7 hours at best. And that's with the aftermarket 1600 Seido battery <_<

I believe it's a defective battery. I already contacted Seido on this for a replacement. But I do have a tendency to run a bunch of apps in the background. I do have advanced task manager. I just get lazy at times in using it.

I'm suffering from what I consider horrible battery life with every ROM I use, and every kernel, undervolted, overclocked/undervolted, stock, tck, etc.

I'm also using a Seidio 1600mah battery. I was starting to suspect those things aren't that good, your post furthers my suspicion. I need to shove the stock battery back in and see if I actually get more juice out of it. I see people with stock batteries and heavier use than I reporting two to three times the battery life of the phone.

I'm going to run the stock battery for a day or two and see if I notice anything different, but it might be hard to tell since weekend use of the phone will be different than weekday.

I don't want to hijack this thread with a Seidio discussion, so I've started a new thread here: http://android.modaco.com/index.php?s=&amp...t&p=1216384

Edited by DistortedLoop
Guest cortez
Posted
I did a clean install of a14, and so far, I've had two complete lock ups of the phone that needed the battery pulled to fix. I've reverted back to my a13 backup.
A14 was the first try of this ROM for me. First boot was okay, but then something crashed after playing with it for a while, and 3 separate reboots all resulted in having to do a battery pull somewhere between the lockscreen first showing up and actually getting launcher to open after the lockscreen.

I ran a logcat on the phone during one of the boots if that would be helpful.

After three failed attempts to even get the phone started again, I just ended up wiping and going back to CM.

Not sure I was that impressed with Sense, it's definitely flashier, but I don't know about being more functional FOR ME.

I really liked the camera app, though. I haven't read most of this thread, but I was able to set the camera to 5mp - I thought this one was limited to 3. Anyways, awesome face recognition, and the iPhone-like tap-to-focus feature is sorely missed in the Google stock camera. This ROM/Camera still had that frickin' pink blur problem on my phone, though.

guys, since both of you experienced issues when switching to Alpha 14, can you confirm that you wiped both the data and dalvik cache before flashing Alpha 14? i was evaluating Alpha 14 and Alpha 12 and had no issues as long as i wiped both caches. i skipped wiping the dalvik cache going from 14 to 12 and i had a couple of start up issues. i rewiped both (data and dalvik) reflashed 12 and didn't have any issues. thanks!
Guest DistortedLoop
Posted
guys, since both of you experienced issues when switching to Alpha 14, can you confirm that you wiped both the data and dalvik cache before flashing Alpha 14? i was evaluating Alpha 14 and Alpha 12 and had no issues as long as i wiped both caches. i skipped wiping the dalvik cache going from 14 to 12 and i had a couple of start up issues. i rewiped both (data and dalvik) reflashed 12 and didn't have any issues. thanks!

I initially screwed up and forgot to wipe - installed A14 on top of Cyanogen. As soon as it booted and I saw the #boobs wallpaper I knew what I had done and immediately rebooted to reinstall it. That time I wiped both factory reset and dalvik cache in RA_Recovery. I always do that when going from one mod to another, except when I screw and forget. LOL.

So, yes, the install that I was referring to which required three battery pulls in a row on startup was on a freshly wiped data and dalvik installation.

Posted

How long did you wait? The first time I flashed the desire rom the first boot took over 5 minutes.

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.