Jump to content

[ROM] FLB-Mod 1 (Based on Android 2.1)


Guest Simon O

Recommended Posts

Guest dodge-167
Ok. this is my output:

a2sd check

[ ] Launching Darktremor A2SD

[*] Starting Darktremor Apps2SD version 2.7.5 preview fix 1

[ ] Mounting /system as read-write

[ ] Starting Apps2SD in check mode

[ ] Running A2SD Check Program.

Darktremor Apps2SD Status Report

===============================================================

[ ] Searching for Mount Point...

[*] Mount point /system/sd located.

[ ] Checking for ext partition

/dev/block/mmcblk0p2 /system/sd ext2 rw,noatime,nodiratime,errors=continue 0 0

[*] Ext partition is mounted.

SD Mount	  - [*] SD Card mounted.


Apps		  - [-] Linked to SD Card.

				[-] Apps2SD no start not found.

				[*] Programs run from SD card

				To run from internal storage, type a2sd remove


Private Apps  - [-] Linked to SD Card.

				[-] Apps2SD no start not found.

				[*] Private Programs run from SD card

				To run from internal storage, type a2sd remove


Dalvik Cache  - [-] Symbolically Linked.

				[-] Dalvik on SD found.

				[*] Dalvik runs from SD card

				To run from internal storage, type a2sd nocache

				To run from /cache partition, type a2sd cachepart


Swap		   - [!] Partition not present.

				 [!] Swap does not start.


ZipAlign	   - [!] Not running at boot.


Dalvik Heap	- [*] 24m


Property Patch  - [-] File System Ready property

					  found.

				  [*] Boot image init.rc patched.

Is yours anything like that? Are both the apps running from internal storage or SD?

I moved Dalvik Cache to SD now... And now everything its ok :)

Link to comment
Share on other sites

Guest Simon O
I just installed the FLB V1 on my U8230.

Everything works except the 3G. (France) :)

I had no problem with the v1.0 beta 5.1update1 - 28th June 2010.

Back in beta 5.1 or is there a solution Flibble?

Anyway congratulations to you and your team for this fantastic job! :D

Ok. I see the 3G problem seems to be with U8230 users. I'll make a new thread.

Link to comment
Share on other sites

Guest dodge-167

I cant open Android Commander... Its says that he didnt wfind any devices...:S

Has your ROM everything what Android commander needs?

Phone Requirements:

- ROOT (only for Applications Manager and flashing options)

- BusyBox (required only for rooted phones; included to most ROMs)

Link to comment
Share on other sites

Guest igor_anta

Strange but the slow bot i due to the bootanimation :) Just change the one you put in the rom and it boots rather fast. Other than that it AMAZING, great work! Cheers!

Link to comment
Share on other sites

Guest Simon O
Strange but the slow bot i due to the bootanimation :) Just change the one you put in the rom and it boots rather fast. Other than that it AMAZING, great work! Cheers!

Hm. What did you change it to?

Link to comment
Share on other sites

Guest Simon O
I cant open Android Commander... Its says that he didnt wfind any devices...:S

Has your ROM everything what Android commander needs?

Phone Requirements:

- ROOT (only for Applications Manager and flashing options)

- BusyBox (required only for rooted phones; included to most ROMs)

Yes it has those. The problem is that, for some reason, our phones don't provide a device name over adb.

Link to comment
Share on other sites

Guest igor_anta
Hm. What did you change it to?

Try the red rage animation I posted on the boot animation topic, just to see how fast it boots, not saying you should keep it :) Cheers!

EDIT: I think the solution is to add a part1 folder with just the final pic in it (you should modify the part0 animation frames so it ends with the logo), and rename it to the number that follows the last pic from part0. The just modify the desc.txt like so: 320 480 24p 1 0 part0p 0 0 part1 and it should be good to go. Cheers!

Edited by igor_anta
Link to comment
Share on other sites

Guest dodge-167
Yes it has those. The problem is that, for some reason, our phones don't provide a device name over adb.

But it worked when i had 5.1 FLB-ROM... :)

Link to comment
Share on other sites

Guest Simon O
Try the red rage animation I posted on the boot animation topic, just to see how fast it boots, not saying you should keep it :D Cheers!

EDIT: I think the solution is to add a part1 folder with just the final pic in it (you should modify the part0 animation frames so it ends with the logo), and rename it to the number that follows the last pic from part0. The just modify the desc.txt like so: 320 480 24p 1 0 part0p 0 0 part1 and it should be good to go. Cheers!

Wow, surprisingly it worked. Weird.. a 5MB bootanimation quicker than a 300kb animation :)

Fusion0306 fixy please? :P

Link to comment
Share on other sites

Guest Simon O
But it worked when i had 5.1 FLB-ROM... :)

Okay I'll take a look at this.

Works. Do you see anything on the right pane? Unplug your USB cable, plug it in again. Anything showing up? Does ADB work?

Edited by flibblesan
Link to comment
Share on other sites

Guest dodge-167

Here is the picture:

thumb-64D8_4C37B457.jpg

I dont know about adb.. but 3 hours ago everything worked great...

Edited by dodge-167
Link to comment
Share on other sites

Guest Simon O
Here is the picture:

thumb-64D8_4C37B457.jpg

I dont know about adb.. but 3 hours ago everything worked great...

I just downloaded it and ran it, found my phone straight away. The filesize is different so maybe there is a new version?

Link to comment
Share on other sites

Guest dodge-167

I downloaded the newest one, and still nothing...

I had this problem before... when my phone didnt have A2SD... Strange... :)

Link to comment
Share on other sites

Guest igor_anta
Wow, surprisingly it worked. Weird.. a 5MB bootanimation quicker than a 300kb animation :)

Fusion0306 fixy please? :D

Well i think it just enters a loop that lasts longer than it should. Try the method I mentioned and it should work fine. Cheers!

Link to comment
Share on other sites

Guest Fusion0306
Wow, surprisingly it worked. Weird.. a 5MB bootanimation quicker than a 300kb animation :)

Fusion0306 fixy please? :D

I edited the desc.txt to repeat the animation 7 times. It should work now. It works fine for me... if it doesn't, play with the figure "7" in the desc.txt. Don't forget to set compression to store when you're done.

DOWNLOAD

bootanimation.zip

Edited by Fusion0306
Link to comment
Share on other sites

Guest Simon O
I edited the desc.txt to repeat the animation 7 times. It should work now. It works fine for me... if it doesn't, play with the figure "7" in the desc.txt. Don't forget to set compression to store when you're done.

DOWNLOAD

bootanimation.zip

Works perfectly. 7 repeats is the perfect amount :) thank you

Link to comment
Share on other sites

Guest aidanj

how much free internal memory do you guys have after checking a2sd is working correctly? i have 27.6 mb, and i think someone on here said they have 70 mb free? i moved dalvik cache to sd + apps (or so it said), through the 'other' menu in recovery mode. am i supposed to do something else on the terminal emulator?

Link to comment
Share on other sites

Guest twics

ADW still has the notification bug it hides and comes back by itself not often though once for me, also coming out of the ADW setting got an fc on android.process, market seems to loadup twice but not often, had an fc on acore but cant remember what i was doing :)

This is just what iv experienced so far still a great Rom though :D

Link to comment
Share on other sites

Guest Simon O
ADW still has the notification bug it hides and comes back by itself not often though once for me, also coming out of the ADW setting got an fc on android.process, market seems to loadup twice but not often, had an fc on acore but cant remember what i was doing :)

This is just what iv experienced so far still a great Rom though :D

That bug with ADW is one that annoys me. The market shouldn't be loading twice though :P

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

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