• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Mikfroyo 4.4 beta I

[ROM] - [01/08/2011] - MikFroYo v4.3 - ReEngineered Sense - Simply Fast. - Page 402 - xda-developers

a few more graphical changes.

changed some of the framework-res values to what cm use by def (hopefully will show faster dl/ul and better batt life)

tunedup animation a little

moved boot anim to def sprint location (so it will be easier for u bouncing letters hating guys to switch.... kidding)

yes... the robot is in the pull down (my version of it - not the old screen shot - on the left and a little darker with trans in it)
 
Drew5150 said:
[ROM] - [01/08/2011] - MikFroYo v4.3 - ReEngineered Sense - Simply Fast. - Page 402 - xda-developers

a few more graphical changes.

changed some of the framework-res values to what cm use by def (hopefully will show faster dl/ul and better batt life)

tunedup animation a little

moved boot anim to def sprint location (so it will be easier for u bouncing letters hating guys to switch.... kidding)

yes... the robot is in the pull down (my version of it - not the old screen shot - on the left and a little darker with trans in it)
Click to expand...
Yes my daily fix.......yeeepeeeee....I'm on this like white on rice:D....downloading now
 
I think thats fine since you dont HAVE to use the apps2sd if you dont want to, plus he said it was faster anyways, thanks for the updates!
 
Hunterbeav said:
What PRI version is everyone running using the mikfroyo 4.4 beta II.
Click to expand...

The only reason you *shouldn't* be using 1.90 is if you suspect it's giving you wake lock/stability issues. Otherwise, you can downgrade to 1.77, but you should stick with 1.90 if you can.
 
akazabam said:
The only reason you *shouldn't* be using 1.90 is if you suspect it's giving you wake lock/stability issues. Otherwise, you can downgrade to 1.77, but you should stick with 1.90 if you can.
Click to expand...
Got ya...thanks. I have done a search to find out what the PRI does and what it effects but really haven't found much:(
 
I am, don't notice much difference from 4.3 its still fast as ever, no probs so far. There is a little android guy in the pull down bar, and you can update flash and still have Hulu work
 
menu is darker, but I dont think the options are any different, not sure what he meant by "brushed up some graphics" ...?
 
I haven't tried out 4.4 yet, but I'll have to try it out later today. From what I understand, he did move dalvik to /cache by default. He left it up to using a2sd, but I read that he'll add a flashable zip to move it if you don't use a2sd.
 
luigic81 said:
menu is darker, but I dont think the options are any different, not sure what he meant by "brushed up some graphics" ...?
Click to expand...

not from the rom...either log cat or pandora is causing this
01-16 14:05:40.648 D/dalvikvm( 1943): GetFieldID: unable to find field Ljava/util/HashMap;.loadFactor:F

I am curious if he can fix the wimax issue some people are seeing...I noticed it did this in his rom as well.

I/Wimax ( 2276): <DC> Try to establish a connection to DC server.
E/Wimax ( 2276): <DC CONNECT> IO error: msg='/127.0.0.1:7771 - Connection refused'

and then this one keeps popping up as well also not from rom..pandora or logcat causing this
01-16 14:05:24.508 W/KeyCharacterMap( 1928): No keyboard for id 65540
01-16 14:05:24.518 W/KeyCharacterMap( 1928): Using default keymap: /system/usr/keychars/qwerty.kcm.bin

I am going to flash final and see if it fixes any of that
 
akazabam said:
I haven't tried out 4.4 yet, but I'll have to try it out later today. From what I understand, he did move dalvik to /cache by default. He left it up to using a2sd, but I read that he'll add a flashable zip to move it if you don't use a2sd.
Click to expand...

not sure what is default, i'm way behind now as i went out of town for the weekend. but here are instructions to getting a2sd working properly on mikfroyo. it has instructions on how to move dalvik to cache. i believe you first need to have your sd card partitioned correctly for this to happen by default, not sure. xda-developers - View Single Post - [ROM] - [01/15/2011] - MikFroYo v4.4 - ReEngineered Sense - Simply Faster.

i haven't gotten a chance to load the final yet. probably going to later tonight. i'm actually kinda surprised he released the final 4.4. friday he had mentioned skipping it and moving to 4.5 caused he wanted to change some things. i have no idea now if he is even going to move forward to a 4.5.

anyways, yeah 4.4 beta has been great for me :)
 
Mr. Ed said:
I am using one of his beta's from last week and seeing some color error codes in log cat...thinking/hoping maybe he just cleaned all of that up.

01-16 14:05:40.648 D/dalvikvm( 1943): GetFieldID: unable to find field Ljava/util/HashMap;.loadFactor:F

I am curious if he can fix the wimax issue some people are seeing...I noticed it did this in his rom as well.

I/Wimax ( 2276): <DC> Try to establish a connection to DC server.
E/Wimax ( 2276): <DC CONNECT> IO error: msg='/127.0.0.1:7771 - Connection refused'

and then this one keeps popping up as well
01-16 14:05:24.508 W/KeyCharacterMap( 1928): No keyboard for id 65540
01-16 14:05:24.518 W/KeyCharacterMap( 1928): Using default keymap: /system/usr/keychars/qwerty.kcm.bin

I am going to flash final and see if it fixes any of that
Click to expand...

I'll have to see if any of those errors are repeating on 4.3, as that's what I'm still on. As for the 4g issue, I'm not entirely convinced that this was actually fixed with the 3.70 OTA. I know some people are no longer seeing it, but there are a lot of other factors to consider. What kernel are you using? Now that I'm thinking about it, I can understand how those using anything but HTC #15 could still have this error.

Drew5150 said:
not sure what is default, i'm way behind now as i went out of town for the weekend. but here are instructions to getting a2sd working properly on mikfroyo. it has instructions on how to move dalvik to cache. i believe you first need to have your sd card partitioned correctly for this to happen by default, not sure. xda-developers - View Single Post - [ROM] - [01/15/2011] - MikFroYo v4.4 - ReEngineered Sense - Simply Faster.

i haven't gotten a chance to load the final yet. probably going to later tonight. i'm actually kinda surprised he released the final 4.4. friday he had mentioned skipping it and moving to 4.5 caused he wanted to change some things. i have no idea now if he is even going to move forward to a 4.5.

anyways, yeah 4.4 beta has been great for me :)
Click to expand...

He stopped moving dalvik to /cache by default because it apparently caused problems with those using a2sd (you can move dalvik to the sdcard with it). He's giving you a choice now - use a2sd for those who have a partitioned card and want to use it, or flash an a update that will move dalvik to /cache for you, and you never have to use a2sd if you don't want to. I assume he did this, also, because he no longer has two versions - a2sd and non-a2sd. Makes sense.
 
Mr. Ed said:
I am using one of his beta's from last week and seeing some color error codes in log cat...thinking/hoping maybe he just cleaned all of that up.

01-16 14:05:40.648 D/dalvikvm( 1943): GetFieldID: unable to find field Ljava/util/HashMap;.loadFactor:F

I am curious if he can fix the wimax issue some people are seeing...I noticed it did this in his rom as well.

I/Wimax ( 2276): <DC> Try to establish a connection to DC server.
E/Wimax ( 2276): <DC CONNECT> IO error: msg='/127.0.0.1:7771 - Connection refused'

and then this one keeps popping up as well
01-16 14:05:24.508 W/KeyCharacterMap( 1928): No keyboard for id 65540
01-16 14:05:24.518 W/KeyCharacterMap( 1928): Using default keymap: /system/usr/keychars/qwerty.kcm.bin

I am going to flash final and see if it fixes any of that
Click to expand...

i don't think mik is going to work on this. as he doesn't really know how to code (he has stated this in his thread) he just like to move or change things around to make them work better i guess.

i think this error happens on all roms - Evo Battery Tips and Explanations **Updated 1-11-11** - xda-developers

i talked to mik about this issue with widgets. and people had mentioned 4g starting on its own after a reboot. mik said he may remove the 4g toggle from the pull down widget, but don't think he bothered as not many people knew or cared about it.

if you feel you are having issues with the 4g widget you can edit the widget.txt to your liking. i don't have the link right now to set it up, sorry.

rebooting your phone after 4g use should kill the wimax i/error connection refused.
 
akazabam said:
I'll have to see if any of those errors are repeating on 4.3, as that's what I'm still on. As for the 4g issue, I'm not entirely convinced that this was actually fixed with the 3.70 OTA. I know some people are no longer seeing it, but there are a lot of other factors to consider. What kernel are you using? Now that I'm thinking about it, I can understand how those using anything but HTC #15 could still have this error.



He stopped moving dalvik to /cache by default because it apparently caused problems with those using a2sd (you can move dalvik to the sdcard with it). He's giving you a choice now - use a2sd for those who have a partitioned card and want to use it, or flash an a update that will move dalvik to /cache for you, and you never have to use a2sd if you don't want to. I assume he did this, also, because he no longer has two versions - a2sd and non-a2sd. Makes sense.
Click to expand...

you still get the wimax i/o error on 3.70 and htc #15 just check using 4.4 beta II. and i know i have seen it using other 3.70 roms. the people that don't see it probably don't know when or where to check honestly.

dalvik to chache, ahh gotcha ya and it does make sense.
 
I have the link somewhere...and though the issue is still there..I am not seeing the slow down and battery drain associated with it in the past.

I believe you are right...folks see the new behavior in the settings menu, combined with no more lag etc and think it is gone....(i did lol)


akazabam...that is what I am on, 4.3
 
Yeah, I think you're right. They just don't know how to actually verify the problem is still there. I know it used to keep my phone awake, but doesn't anymore.

Mr. Ed, I thought you meant you were using one of the 4.4 betas :).
 
<i actually thought I was on a 4.4 beta but when I checked it was 4.3 lol

I have been having issues getting 4.4 to download. :(
 
You must log in or register to reply here.
Back
Top Bottom