[BUILD] **Complete FroYo Bundle** FRX07.1 - Maintenance Release

Search This thread
By:
Advanced…
dop2010

dop2010

Member
Feb 18, 2010
45
14
Canberra
doptrix.com
arrrghhh said:
I still want dop2010 to try this bundle as-is without any changes!! Please let us know.
Click to expand...
Click to collapse

Ok, I tried original bundle and it works! Thanks! :)
Even my game works, unbelievable!! :)


This page on wiki says "It is recommended that you update the various components of XDAndroid with incremental updates" so I thought I should just use the latest files... Are there updates for my hadrware? how can I find them?


What about my second problem with WM? Do you know how to fix it?
 
Last edited:
M

mweirauch

Senior Member
Jun 23, 2009
360
29
www.m-phasis.de
dop2010 said:
What about my second problem with WM? Do you know how to fix it?
Click to expand...
Click to collapse

So you say, in WinCE a bigger part of the panel area does not work? Is this "reproduceable" in any application? Or is this a "launcher" issue. Like Sense going mad?

I know from my TOPA days, that occassionally the Sense install was screwed when coming back to it. To see if this is only a sense issue, switch to that windows launcher thingy. During development I mostly disabled any "launcher" WinCE thingy... (which also gave faster turn-around times ;))
 
dop2010

dop2010

Member
Feb 18, 2010
45
14
Canberra
doptrix.com
In home screen I can only press "Start" and top bar icons and two buttons in the bottom of the screen ("Phone" and "Contacts"?).
Everything else doesn't work.

When I press "Start", a list of programs opens, I can scroll it and start some programs (e.g. File Explorer). But I can't start Settings for example - the icon is highlighted, but nothing happens.
And some windows or programs don't disappear from the screen after I close them.

It's hard to explain, but it looks like the screen is not refreshing when it should..
 
M

mweirauch

Senior Member
Jun 23, 2009
360
29
www.m-phasis.de
dop2010 said:
In home screen I can only press "Start" and top bar icons and two buttons in the bottom of the screen ("Phone" and "Contacts"?).
Everything else doesn't work.

When I press "Start", a list of programs opens, I can scroll it and start some programs (e.g. File Explorer). But I can't start Settings for example - the icon is highlighted, but nothing happens.
And some windows or programs don't disappear from the screen after I close them.

It's hard to explain, but it looks like the screen is not refreshing when it should..
Click to expand...
Click to collapse

That sounds really like a HTC Sense issue. Are you runing a custom Sense install? Like MaxSense or some such? Try resinstalling. Otherwise try toggling the home screen "launcher" in the settings from and to Sense.

Otherwise, I dunno how to resolve this. I usually had to reinstall and was done.
 
K

kadooosh

Senior Member
Apr 1, 2007
106
2
I copied the folder to my sd card and the startup file but is it normal the first boot takes ages?
I'm talking about 1 hour +
I allready restarted it but its been going for a long time now again.
Its still active though I see its doing something.
Sometimes the screen goes black and when I turn the on button its back again(standby?).
 
A

arrrghhh

Inactive Recognized Developer
Feb 10, 2007
11,906
3,851
kadooosh said:
I copied the folder to my sd card and the startup file but is it normal the first boot takes ages?
I'm talking about 1 hour +
I allready restarted it but its been going for a long time now again.
Its still active though I see its doing something.
Sometimes the screen goes black and when I turn the on button its back again(standby?).
Click to expand...
Click to collapse

Did you skip the calibration step? Tap the screen a few times (5 to be exact). It should boot, but your screen will not be configured correctly.

Please re-read the first post, it has instructions on what to do for screen calibration (and is one of the steps to follow for installation :rolleyes:)

For reference, it should take ~10 minutes for the first boot. Anything over 15 is probably not going to finish.
 
A

ais11

Member
Jan 20, 2007
18
0
I have installed FRX07.1 on HTC Touch Diamond. Although it seems to be working but every action/click is dead slow. Is it normal on Touch Diamond or am I missing something? Thanks in advance for your assistance.
 
A

arrrghhh

Inactive Recognized Developer
Feb 10, 2007
11,906
3,851
ais11 said:
I have installed FRX07.1 on HTC Touch Diamond. Although it seems to be working but every action/click is dead slow. Is it normal on Touch Diamond or am I missing something? Thanks in advance for your assistance.
Click to expand...
Click to collapse

This is the TD2 section, not the regular Diamond section.

The regular Diamond only has 192 mb of RAM... So yes, slowness is expected. There's not a lot that can be done - no SD card slot in the DIAM so you can't put in a faster random read/write card... So check my Speed Improvements thread. Might help.
 
eclyptos

eclyptos

Senior Member
Jun 14, 2008
3,040
640
Planet Earth
Hey Gays, Thanks for the amazing job!

After I saw this thread I pick up from garbage my old Diamond 2 and I copied the bundle into the sd, I hope it still alive again but I start the Android and he is taking too long, 20 minunts now in boot with all this tiny numbers and links.

How long it will boot? :)

Everything Works?
 
eclyptos

eclyptos

Senior Member
Jun 14, 2008
3,040
640
Planet Earth
ebsbow said:
First boot takes some time. Next boot should be faster.
Click to expand...
Click to collapse

ok, but here is momething wrong, now is 1 hour and I think the boot go in loop, at the end of tiny stripes is always; mdp_dma: busy :confused:

I think I have to repeat all again.

---------- Post added at 08:59 PM ---------- Previous post was at 08:15 PM ----------

Guys, something not right! I deleted the last one Android and I installed a fresh one but he do not want to boot, he still in booting and in looping.

Somebody have or had this problem?
 
eclyptos

eclyptos

Senior Member
Jun 14, 2008
3,040
640
Planet Earth
ok, I find the problem in booting the Android, after I launch the app into the boot appear this:

"Filed: rootfs.img not find in SD card" :confused: (the file is there)

..and after this point the boot go in loops and I have to pull out the battery.

Someone can help me to understand where is the problem, thanks.
 
eclyptos

eclyptos

Senior Member
Jun 14, 2008
3,040
640
Planet Earth
ARE YOU READY?

am I stupid? YES, I am stupid duck, idot, I should find different hobbie!

I forgot to put the cmdline "rel_path=Androids" into the startup.txt, now the Android start fantastically!

Now all of you are free to insult me!! Yes, you can!

:angel:
 
latinohot

latinohot

Senior Member
Jul 2, 2008
2,208
276
all over the u.s.a
Samsung Galaxy Z Fold3
eclyptos said:
ARE YOU READY?

am I stupid? YES, I am stupid duck, idot, I should find different hobbie!

I forgot to put the cmdline "rel_path=Androids" into the startup.txt, now the Android start fantastically!

Now all of you are free to insult me!! Yes, you can!

:angel:
Click to expand...
Click to collapse

None of us are perfect, that's all I can say

sent from: an universe built by Sean;)
 
eclyptos

eclyptos

Senior Member
Jun 14, 2008
3,040
640
Planet Earth
I don't know if you know this issue but this FRX07.1 is hungry of my battery! :p

I can say my battery life is about 12 hours and if I leave the phone in standby he crash dead.

I came late to work this morning! :angel:

Any fix?
 
You must log in or register to reply here.

Similar threads

ReWind402
[25/03/11]XDAndroid - Topaz [2.2.2][FRX06 Final]
Replies
6K
Views
2M
PopaStefanx
PopaStefanx
A
[TESTING] XDAndroid GBX0C 2.3.7 Build
Replies
95
Views
62K
Q
Quigley
txtter
XDAndroid Gingerbread Public Test Build（from south cape）
Replies
66
Views
26K
P
porkovich
J
Working Froyo Build
Replies
2
Views
7K
J
jasonyump
J
XDANDROID - Latest FRX07 Release (15th July 2011)
Replies
8
Views
14K
K
kchris48

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 17
    A
    arrrghhh
    Figured you TOPA folk needed your own thread... At least to track TOPA-specific issues!

    FRX07.1 is here!!

    This is a maintenance release - basically taking the newest components to make a completely up-to-date (as of Sept. 1).

    Quite a lot has changed since FRX06 - the install process hasn't really, but be sure to read the changelog in the next post and the caveats in post #3!

    <<<This is a link to the... FAQ Click it!!>>>​

    I have created a complete bundle of FroYo with a stable kernel from GIT (August 19 / 1348), and rootfs from GIT (Sept. 2).

    Please, feel free to DONATE to the XDAndroid project!

    Every little bit helps!

    Directions:

    1. Download the full bundle (zip). (Updated September 1 2011)

    If instead you just want the system.ext2 (zip) (Updated July 15 2011) file by itself... Don't download this if you're not sure! Grab the full bundle!

    2. Extract it. You’ll see a folder, FRX07.1, copy its contents to the root of your SD card. If you want to run Android from a folder instead of all the files on the root of the card, follow the steps below.

    3. Go into the STARTUPS folder. Grab the appropriate startup.txt for your device (if you don't know what device you have, you should read the FAQ), and move it to the root of the card (or where you run haret.exe from. If you want to change the location of the build, put a rel_path= statement in the cmdline section of the startup.txt. Mine is located two folders deep on the SD, so my rel_path=Androids/TP2Ref)

    4. Screen calibration - you have three choices:
    • Re-use an old ts-calibration file if you have it and you know it's good.
    • Download the ts-calibration.zip file and extract it to where you put the rest of the files (root of SD or in a folder - make sure it all stays together!)
    • Manually calibrate - boot with no ts-calibration file and watch the boot process - you'll be asked to hit 5 points to calibrate the screen. If you have issues calibrating, try an older kernel (1225 works well) Once you have the calibration file hold on to it (make 15 copies if it's a good one :p), reboot & go back to the newest kernel!

    6. Run haret.exe.. Profit! :D

    Let it settle out on the first boot. Many have reported they had to reboot basically because it was so slow - if you let it sit for about 10 mins so the media scanner can go thru everything, etc. it will be much more pleasurable experience. If you want adb in and watch the processes via top, you'll see why the phone seems so slow - there's lots of background processes cranking because this is the first boot ;).

    Troubleshooting:
    Please read the... FAQ
    If you have any issues with the kernel, feel free to change it:
    There are some devices that are having issues with the newest kernels. Please see the kernel autobuild service to get archived kernels. Once you download a replacement kernel, go to where you run haret.exe from - remove your old zImage/modules-xxxxx.tar.gz. Take the new zImage/modules-xxxxx.tar.gz and replace the old ones, same folder - where you run haret.exe from. Make sure the ‘zImage’ is named just that. Do not rename the modules file, do not extract it - should be in .tar.gz format.

    See Incremental Updates for more information on updating the kernel and other components.

    Random issues can often be solved by forcing the system to create a new data.img. If you're worried about losing data (all user data is stored in the data.img!!), Titanium Backup works quite well. If you wish, you can rename the data.img to something else, and let the system create a new one - just to see if it resolves your problem.

    Similarly, if you wish try formatting your SD card - I prefer to use the HP Tool - do a full format, FAT32.

    Even though this build is considered fairly stable, you are more than likely going to run into issues. The next post will address issues particular to this build - PLEASE READ THESE before asking questions! Feel free to post questions in this thread, I will do my best to address them. Big thanks to stinebd for releasing the system image, and of course the other developers for their hard work on making these kernels available.
    View
    3
    A
    arrrghhh
    Hey guys, updated to FRX07.1 maintenance release. Some outlying bugs fixed, and the build is completely up-to-date. See the changelog for details!
    View
    2
    A
    arrrghhh
    stinebd's Changelog:​


    stinebd said:
    Here’s a new release for you, folks. This is a major release with a ton of changes, new features, and fixes. Our friend hyc/highlandsun did most of the heavy lifting for this release. Highlights include a rewritten RIL with support for world phones and greatly improved CDMA support; fixes for the media codecs; fixes for MMS on Sprint; increased security with the Superuser app.

    A list of changes is included below. The FRX07 system image is available for download now, and will require the use of a new rootfs image, also available now. Additionally, we have a new bundle containing everything needed to enjoy a full FRX07 system.

    Note: Due to the incredibly long list of changes, this is a somewhat condensed, terse changelog describing only the overall scope of the changes.

    FRX07:
    • frameworks/base:
      • Major frameworks changes for CDMA/GSM dual-mode worldphone support. (hyc)
      • Fixes for data connection handling to improve startup time. (hyc)
      • Fixes for wifi handling to avoid issues on hanged drivers. (hyc)
      • Stagefreight (media codecs) fixes. (hyc/viruscrazy)
      • Fixes for Sprint’s wonky MMS markup structure. (hyc)
      • Fix MediaScanner not finding audio files (including ringtones) in system.ext2
    • hardware/libhardware_legacy:
      • Minor GPS driver fixes. (Alex[sp3dev])
      • Rename wifi interfaces to wlan0 on all devices (hyc)
    • hardware/xdandroid-ril: Major RIL refactoring for improved performance on all devices, and added CDMA/GSM dual-mode worldphone support. (hyc)
    • packages/apps/Gallery3D: Switched back to Gallery3D as the gallery app (closes bug #111)
    • packages/apps/Mms: Fixes for Sprint’s wonky MMS markup structure. (hyc)
    • packages/apps/Phone: Fixes for CDMA/GSM dual-mode worldphone support. (hyc)
    • packages/apps/Superuser: Added the Superuser package for authorizing su privileges. This, along with our signed builds, provides greatly increased security for the end user (mostly against malicious apps from the Market).
    • system/extras/su: Added as a dependency for the Superuser package
    • vendor/qcom/android-open: Include missing stagefright codec symbols. (hyc/viruscrazy)

    To coincide with the FRX07 system image, the following rootfs changes have been made:
    • init.froyo.rc modifications...
      • Adjust wpa_supplicant service for the new abstraction provided by libhardware_legacy, as well as interface rename
      • Abstract the hciattach service to provide bluetooth support on both chipsets
    • Rename wifi interface to wlan0 on all devices
    • apns-conf.xml updated
    • keymaps completely reorganized, and RHOD end-call key has been remapped to be the Home key in Android.
    • default.prop: set ro.secure=1 to lock down the adb shell - su can be used with the Superuser app to authorize root access in adb if needed.
    Click to expand...
    Click to collapse
    View
    2
    D
    detule
    Black.Heart said:
    But's it's really slow and I can say it's the slowest kernel I ever used. I'd love to see a nice .35 kernel for our devices. Since I don't have the necessary knowledge of developing open source (yet!), I can only wait to use other dev's work :(
    Click to expand...
    Click to collapse

    I am no expert but the cutting edge development right now in terms of kernels for our devices is in fact happening in the .35 trees for topaz and kovsky. In fact, the LED changes to .27 are only a backport of ideas emwe and Alex had already in place in their .35 trees. Count yourself fortunate that the main .35 effort seems to include topaz right now (more so than say rhodium).

    Alas, as with most advancements, it's not a smooth progression and I think the newer kernels are seeing some of this. While .35 and .39 both seem to improve the way our devices behave in certain aspects, they seem to break other things on our phones.

    Finally, while wince "developers" porting android seems like a mythical group of people, they are in fact only human, and only a few of them at that. They all take vacations, have jobs in real life, and most of all, have the freedom to pick the projects that interest them. It is the nature of things, and I think it's best to come to terms with the situation right now: many people that have the know-how to develop for our phones have moved on to other devices, and more will with each passing week. I would temper my expectations and not even hope for a stable release of a post .27 kernel that would work across all legacy devices that the current kernel supports.

    The moral of the story is, if you want something done, it's best you start staring at the git trees and trying to learn low level C.
    View
    2
    A
    arrrghhh
    Whew, here you go TOPA folk!

    I figured you guys needed a thread for this, if only to track issues that are TOPA-specific. Let me know what I need to add in the caveat section for TOPA! Also let me know if ts-calibration file is good or not ;).

    Also, if you guys already have FRX07 running/working... there's nothing new here. Mainly using this thread as a place for newbie's to go and you experienced folk to help me track issues again for new users!
    View

New posts