1134 replies to this topic

[Joshua Lim]

HTC Sense livewallpaper isn't working, Paul. Getting forced closed.

[Docmjldds]

Edit:...double post. Disregard

Edited by Docmjldds, 28 May 2010 - 10:52 AM.

[Askani]

I got FC when adding my gmail account,  so,  no good for me...

[RatSon]

-only system dalvik is moved to cache. would it be a problem if i moved data dalvik too??

-the included busybox is writing out ls improperly, maybe because of the color coding. can it be fixed?

-build.prop needs the following added:

Quote

ro.media.enc.file.format = 3gp,mp4
ro.media.enc.vid.codec = m4v,h263
ro.media.enc.vid.h263.width = 176,352
ro.media.enc.vid.h263.height = 144,288
ro.media.enc.vid.h263.bps = 64000,800000
ro.media.enc.vid.h263.fps = 1,30
ro.media.enc.vid.m4v.width = 176,352
ro.media.enc.vid.m4v.height = 144,288
ro.media.enc.vid.m4v.bps = 64000,800000
ro.media.enc.vid.m4v.fps = 1,30

ro.ril.hsxpa=2
ro.ril.gprsclass=12

Edit:
i have moved all dalvik (data,system,mnt) to /cache no problem thus far.
this filled ~45% of my /cache partition. will it cause no problems? i don't really know what is stored in /cache....

Edited by RatSon, 28 May 2010 - 01:24 PM.

[Docmjldds]

RatSon, on May 28 2010, 05:36, said:

-only system dalvik is moved to cache. would it be a problem if i moved data dalvik too??

-the included busybox is writing out ls inproperly, maby because of the color coding. can it be fixed?

-build.prop needs the following added:
Edit:
i have moved also data dalvik to /cache no problem thus far. i try moving all (system, data, mnt)
this will fill ~40% of my /cache partition. will it cause no problems? i don't really know what is stored in /cache....

I have tested with and without those build.prop edits. I see no difference. There was a long thread on that over on XDA when Froyo was first released. I was a believer at first. In fact, someone posted info that was incorrect totally regarding Nexus one, specifically. Just my 2c. So far, having the market build.prop info so apps show correctly seem to be the only edit I have seen worthwhile for Froyo, and Paul correctly included that in the kitchen.

[RatSon]

Docmjldds, on May 28 2010, 15:17, said:

I have tested with and without those build.prop edits. I see no difference. There was a long thread on that over on XDA when Froyo was first released. I was a believer at first. In fact, someone posted info that was incorrect totally regarding Nexus one, specifically. Just my 2c. So far, having the market build.prop info so apps show correctly seem to be the only edit I have seen worthwhile for Froyo, and Paul correctly included that in the kitchen.

ok, but

Quote

ro.ril.hsxpa=2
ro.ril.gprsclass=12

makes sense.

afaik /cache is for browser cache. i have moved my full dalvik there, now i have +40mb free in /data

[monci85]

I can not flash the rom .. I have left on the X to infinity .. how can I do? I come from the root Froyo modaco.. thanks

[nyke]

monci85, on May 28 2010, 14:30, said:

I can not flash the rom .. I have left on the X to infinity .. how can I do? I come from the root Froyo modaco.. thanks

try without App2SD or App2SD+

[monci85]

nyke, on May 28 2010, 13:41, said:

try without App2SD or App2SD+

I activated apps2sd by adb .. I included not in the kitchen .. how can I disable apps2sd?

[Namuna]

Batkoto, on May 27 2010, 19:29, said:

Try flashing again, but this time cook a ROM without radio update and see if its working

Thanks, that did the trick!

[Docmjldds]

species8472, on May 27 2010, 23:59, said:

Awesome Paul..

Question.. Any suffering from fast battery drain? I mean like 10% in under 30 min at times..

On standby I am losing approx 1%/hr. Was a little more with stock kernel. I am running Raven's last Froyo specific kernel which is undervolted, but no overclock. CFS 925mv.
2.6.34_AVS-925mV_CFS_20100523_1351.zip
http://forum.xda-dev...ad.php?t=653598

[mamoulian]

Yup same problem for me, the A2SD+ build kept looping round the boot animation.

This was after doing all the wipes I could find - main, dalvik-cache and sd:ext.

I do have the partitions set up correctly, previously they've worked fine with CM 5.


Baked one without A2SD and it's fine!
Thanks Paul! :-)

[DDDWU]

fixed. I think I know what's happened...

Edited by DDDWU, 28 May 2010 - 03:14 PM.

[tasomaniac]

I was just happy when I saw this because of the old app2sd. But no luck. I tried everything. And not working.

[pjcforpres2020]

Docmjldds, on May 28 2010, 06:16, said:

Yes to A2SD. I am unclear by your post what my fix would be. You first state I have to have ext2/3/4 on my SD. I have AMon recovery 1.7 and I used that to partition my SD card prior to installing kangorama 7 final, on the XDA Developers site. I upgraded from Ext2 to ext4 using the app on the recovery. So, what is the fix as it is right now. My Nandroid backup of Pauls initial 24 May Froyo release installed without a hitch. I can see a slew of other users here reporting the same issues, so your point you are making needs to be addressed in a readme, prior to installing this. I read the readme stuff, and didn't see anything regarding the A2SD. I did see a post over on XDA about forcing all apps on Froyo to install to the sd card. I used a2sd and not the a2sd+ only because I hade partitioned with the older method initially, prior to installing the Kang with CM 5.7.0.1 update. Hope I made this clear on where I am now. And specifically, not sure from your post what my fix would be.

It sounds like the A2SD itself is broken... but what I was saying is exactly what I said.  If you use the community made A2SD, you have to have an ext2/3/4 partition on your SD card, and when coming from another ROM series you have to wipe your ext2/3/4 partition.  IIRC, Nandroid backs up your ext partitions as well, not 100% on that though since I don't use Nandroid a whole lot (my only nandroid on my SD card is from ere27)... anyways, I was as clear as I could be, while not the root of the problem this time, 99% of the time people have a boot loop on an A2SD ROM it is because they don't have their ext partitions, or didn't wipe their ext partitions.

[mamoulian]

@pjcforpres2020

Nope my sd partitioning is fine, used it on cm. Definitely wiped the sd: ext before flashing this one.

[joninatl]

The cache partition is where OTA updates are downloaded to. Since rooted phones don't get OTAs, it's fine to use it.

RatSon, on May 28 2010, 08:36, said:

-only system dalvik is moved to cache. would it be a problem if i moved data dalvik too??

-the included busybox is writing out ls improperly, maybe because of the color coding. can it be fixed?

-build.prop needs the following added:
Edit:
i have moved all dalvik (data,system,mnt) to /cache no problem thus far.
this filled ~45% of my /cache partition. will it cause no problems? i don't really know what is stored in /cache....

[hks18psigst]

ok.. so i have some minor metamorph's that worked on Paul's and Cyanogen's other Froyo builds now my Metamorh is saying "this phone doesn't have root, can't find SU file." but i can use rooted apps and i can type SU in terminal and get # sign... SOOO confused. any help is greatly appreciated.

                                                                                                Thanks hks!

[rgbc]

hks18psigst, on May 28 2010, 14:08, said:

ok.. so i have some minor metamorph's that worked on Paul's and Cyanogen's other Froyo builds now my Metamorh is saying "this phone doesn't have root, can't find SU file." but i can use rooted apps and i can type SU in terminal and get # sign... SOOO confused. any help is greatly appreciated.

                                                                                                Thanks hks!

Did you install the froyo version in this thread or the original posted here http://android.modac...online-kitchen/

With the original rom I got the same error as you with metamorph, fixed it by flashing Cyanogen's quick rooter http://forum.xda-dev...ad.php?t=686627

I did a clean install of Paul's r16 rom and metamorph is working fine.

[hks18psigst]

rgbc, on May 28 2010, 17:28, said:

Did you install the froyo version in this thread or the original posted here http://android.modac...online-kitchen/

With the original rom I got the same error as you with metamorph, fixed it by flashing Cyanogen's quick rooter http://forum.xda-dev...ad.php?t=686627

I did a clean install of Paul's r16 rom and metamorph is working fine.

I currently have r16 and metamorph is not working for me. and quick rooter puts r16 into a bootloop and i did a full wipe coming to r16 but maybe i'll try to wipe again