RunicMourning
Newbie
From what I saw in the testing chat last night, it should work anyway after flashing Metroff. I could be wrong. I don't have this issue as I am on Cricket.
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root [ROM][WIP] CyanogenMod 7 | Android 2.3.5 (Gingerbread) | Current Version: 09122011
- Thread starter isaacj87
- Start date
-
- Tags
- huawei ascend
Thanks for the info.. Didnt try that.. reverted back.. will wait for a fix..
septembersrain
句_句 Smurfing Awesome
Even though the APN does not show up, It's still working fine. :] This is the fastest build yet! When I first flashed it and it booted up, I was like O.O...Oh...I'm still at 600Mhz! *Goes to try 710 and gets excited at the zoom zooming*
I'm amazed at how much space I've got as well. I've got all my apps on the phone and I've got almost 80MB free. Considering on the last build I had like 63. I'm a stickler about keeping my cache and histories clean too.
PLUS I flashed with the USB cord plugged in, Rebooted with it STILL plugged in. All those minor problems I'd had before have vanished. No more "Write Protection" or boot loops! ~.o Smurfing awesome.
Edit: I still flash the Cm7 first, Let it boot up and then do Gapps and MetrOFF together. Golly I'm so old fashioned huh? Full wipes and still flashing through the CWM and not RM.
I'm amazed at how much space I've got as well. I've got all my apps on the phone and I've got almost 80MB free. Considering on the last build I had like 63. I'm a stickler about keeping my cache and histories clean too.
PLUS I flashed with the USB cord plugged in, Rebooted with it STILL plugged in. All those minor problems I'd had before have vanished. No more "Write Protection" or boot loops! ~.o Smurfing awesome.
Edit: I still flash the Cm7 first, Let it boot up and then do Gapps and MetrOFF together. Golly I'm so old fashioned huh? Full wipes and still flashing through the CWM and not RM.
nuttmeg
Extreme Android User
Even though the APN does not show up, It's still working fine. :] This is the fastest build yet! When I first flashed it and it booted up, I was like O.O...Oh...I'm still at 600Mhz! *Goes to try 710 and gets excited at the zoom zooming*
I'm amazed at how much space I've got as well. I've got all my apps on the phone and I've got almost 80MB free. Considering on the last build I had like 63. I'm a stickler about keeping my cache and histories clean too.
PLUS I flashed with the USB cord plugged in, Rebooted with it STILL plugged in. All those minor problems I'd had before have vanished. No more "Write Protection" or boot loops! ~.o Smurfing awesome.
Edit: I still flash the Cm7 first, Let it boot up and then do Gapps and MetrOFF together. Golly I'm so old fashioned huh? Full wipes and still flashing through the CWM and not RM.
move some of the apps...lol, i still have 120 left from moving things, ZOOOOOM!!!!
isaacj87
Android Expert
I'm not sure what happened to the APNs. I did a check though, even though they don't show up in the "Open APNs" menu, they're still intact.
Something changed in CM-land because this build is mostly only kernel work. Thanks to the testers and for all the support.
Happy Ascending.
Something changed in CM-land because this build is mostly only kernel work. Thanks to the testers and for all the support.
Happy Ascending.
septembersrain
句_句 Smurfing Awesome
Nah. :] Did you read my edit about me being an old fashioned coot? LOL
RunicMourning
Newbie
Holy crap! I just got a long text from my boss (usually long texts come through as MMS). She has an iPhone and it came through. I hope this means MMS from iPhones work now. 
Anyone confirm this?
Anyone confirm this?
PlayfulGod
Extreme Android User
did you flash the MetrOFF v1.3 MMS fix? If not you need to do so to get mms to work.
Yes, I run all 3, CM7, GAPPS and MetrOFF. On last build, I had to go into the list and select Metro since it wasn't selected by default.
PlayfulGod
Extreme Android User
Correct thats all you should have to do.
Cool man. I thought I needed to go into the APNs and select Metro from the list. If that is all, then I am good.
Thanks.
PlayfulGod
Extreme Android User
which governor you have set? my phone seems to like the interactive one best.
Well, now I am not even sure the CPU is causing this. I set it to ONDEMAND @ 710, and it ran fine for about 10 minutes. Then, I flashed MetrOFF and after 1 minute of restarting, the phone is rebooting.
ElasticNinja
Android Expert
if you are running at the borderline of your CPUs capabilities, having it run at max for a few minutes flat out will cause a reboot
I'm re-flashing for the 3rd time. This time I will leave the CPU @ 600, but flash MetrOFF to see what happens.
Thanks for the advice.
septembersrain
句_句 Smurfing Awesome
It is because I believe that with this new overclock kernel, It is "True" overclocking. At least this is what I gathered after talking to and reading some stuff Isaac wrote. So this would mean that if you've got a "Lazy" Ascend your phone would be stopped at a lower OC now. I'd suggest trying each one from 710-600, Find one that works well and does not cause you mass reboots. :]
I noticed that now my phone runs at 710Mhz what it used to at 729Mhz on the previous build!
fredrick1213
Well-Known Member
I'm also experiencing reboots on this build. This has never happened in any of the previous builds...
stamper
Newbie
I have read several thread posts about overclocking the Ascend phone and how some people can overclock higher than others and some cannot overclock at all.
I work in the IT industry and worked for computer builders for several years. I say this to shed some light on why this occurs. It is not a "lazy" cpu. There is no such thing as that.
What happens is that the cpu manufacturer does what is called "bin sorting" of the cpu's it produces. As they produce a batch of cpu's they test each one to see what speed it will operate safely. Out of one batch there will be some that work much slower than others and vice versa. Why they do that is to get more yeild out of the run of processors. As it regards to the Ascend cpu's, they will have out of a run of 100 cpu's maybe 20 that will run at 400mhz, 60 that run at 600mhz, and 20 that run at 748mhz. (these numbers are arbitary at best and for example only) The initial run was designed to have them all run at 748mhz but testing showed otherwise. They don't want to scrap the 80 processors so they brand them at 600mhz and sell them as such.
In the pc world, AMD, was known as the OCer's cpu of choice as they had the biggest range of Mhz speeds. If you knew how to read the serial numbers you could figure out what your cpu could be overclocked to. In the pc world we would water cool the cpu's to make them more stable and run at higher speeds.
The cpu's makers still do this today. That is why some of us can OC our phones faster than others with out having reboot issues. As you push the cpu farther without any other cooling it overheats and shuts down the device to protect the rest of the components. Overclocking a cpu with only stock cooling will shorten the life of the cpu. This is a known fact in the PC world of Overclocking. There is obviously no way to add a cooling fan or water cooling to a phone (that would be interesting to see though) so those of us who want to push the phone faster with OCing will have to deal with the reboots early on while we look to find out where we can, individually, ramp up the speed on our phones. Statistically, there will be few of us who will be able to run to the full extent of the cpu. Most of us will be able to OC somewhere in the middle. A lot of trial and error will be needed to find out where your phone will OC.
I publish this so that those of us who rushed to CM7 by Issac87 in hopes to push the phone up to 710 or higher and then moan and scratch our heads when we can't get there do not complain or blame the CM7 code for the problem. Issac87 is fixing code to hopefully get more of us to be able to safely OC our phones. He could put a fixed limit in the code and leave well enough alone but wants each of us to see how far we can push the limits. That information helps him as much as it helps us.
With the new build he released, it sounds as though he it getting this dialed in. What this means is that what we were running on the previous 05142011 build was not a true OC speed and the new 05212011 build is giving us a truer picture of what our phone cpu can really oc. This does not read like error in his coding.
Thanks Issac87 for all the work you are doing.
I work in the IT industry and worked for computer builders for several years. I say this to shed some light on why this occurs. It is not a "lazy" cpu. There is no such thing as that.
What happens is that the cpu manufacturer does what is called "bin sorting" of the cpu's it produces. As they produce a batch of cpu's they test each one to see what speed it will operate safely. Out of one batch there will be some that work much slower than others and vice versa. Why they do that is to get more yeild out of the run of processors. As it regards to the Ascend cpu's, they will have out of a run of 100 cpu's maybe 20 that will run at 400mhz, 60 that run at 600mhz, and 20 that run at 748mhz. (these numbers are arbitary at best and for example only) The initial run was designed to have them all run at 748mhz but testing showed otherwise. They don't want to scrap the 80 processors so they brand them at 600mhz and sell them as such.
In the pc world, AMD, was known as the OCer's cpu of choice as they had the biggest range of Mhz speeds. If you knew how to read the serial numbers you could figure out what your cpu could be overclocked to. In the pc world we would water cool the cpu's to make them more stable and run at higher speeds.
The cpu's makers still do this today. That is why some of us can OC our phones faster than others with out having reboot issues. As you push the cpu farther without any other cooling it overheats and shuts down the device to protect the rest of the components. Overclocking a cpu with only stock cooling will shorten the life of the cpu. This is a known fact in the PC world of Overclocking. There is obviously no way to add a cooling fan or water cooling to a phone (that would be interesting to see though) so those of us who want to push the phone faster with OCing will have to deal with the reboots early on while we look to find out where we can, individually, ramp up the speed on our phones. Statistically, there will be few of us who will be able to run to the full extent of the cpu. Most of us will be able to OC somewhere in the middle. A lot of trial and error will be needed to find out where your phone will OC.
I publish this so that those of us who rushed to CM7 by Issac87 in hopes to push the phone up to 710 or higher and then moan and scratch our heads when we can't get there do not complain or blame the CM7 code for the problem. Issac87 is fixing code to hopefully get more of us to be able to safely OC our phones. He could put a fixed limit in the code and leave well enough alone but wants each of us to see how far we can push the limits. That information helps him as much as it helps us.
With the new build he released, it sounds as though he it getting this dialed in. What this means is that what we were running on the previous 05142011 build was not a true OC speed and the new 05212011 build is giving us a truer picture of what our phone cpu can really oc. This does not read like error in his coding.
Thanks Issac87 for all the work you are doing.
hinicephone
Newbie
Wow I must say this is a wonderful build even my Facebook pics are loading much faster I'm just getting into it but so far so good