• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

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

Search This thread

arrrghhh

Inactive Recognized Developer
Feb 10, 2007
11,907
3,854
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.
 

Attachments

  • ts-calibration.zip
    200 bytes · Views: 7,064
Last edited:

arrrghhh

Inactive Recognized Developer
Feb 10, 2007
11,907
3,854
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.
 

arrrghhh

Inactive Recognized Developer
Feb 10, 2007
11,907
3,854
Layman's Changelog​

(As in, the changelog I wrote :p)​

FRX07.1 Changelog:

  • RHOD - all buttons on the front no longer wake the device. Only the power button wakes the device now.
  • Updated to the newest RIL
  • hyc's modified libs for video now baked in - *most* HQ YouTube videos (and other HQ videos) should finally work!
  • RHOD & TOPA - Userland (Android) now controls the LED by default now. If you need to debug sleep, you will have to change the behavior manually. See Detule's post on this topic.
  • Facebook sync should now work, out-of-box.

FRX07 Changelog:
  • Updated RIL (thanks hyc!) - this covers many different bugs that were in the old RIL - I'm only going to cover the major ones...
    • CDMA now works correctly (for the most part). force_cdma (and north_am_dialing) is now deprecated (not needed/ignored!)
    • You can boot with a SIM in on a CDMA device and choose your GSM or CDMA on the fly under Settings.
    • Location based on towers now works on CDMA.
    • 1xRTT now displays correctly, but I never seem to get EVDO Rev.a... I always get 0. This is represented by a 3g icon, as this is what the Android framework provides.
    • Full MMS support! Please see this page for configuration instructions. Will need help fleshing out the list of carriers folks!
    • Spotty service, switching towers, etc should no longer cause the dreaded SoD (Sleep of Death) condition!
  • (Basic audio) 3.5mm support for RHOD400/500
  • Droidwall works out of the box now
  • Keyboard backlight now fades in/out
  • Gallery3D back in! Picasa Web Sync comes with it ;)
  • A couple new apps added to AndroidApps folder:
    • rpierce99's app GetLogs
    • Titanium Backup
 
Last edited:
  • Like
Reactions: Starsheriff

arrrghhh

Inactive Recognized Developer
Feb 10, 2007
11,907
3,854
Caveats:

  • BT - works! But audio doesn't route. See this thread if you're feeling adventurous and want to play with/don't mind using some unstable/incomplete code...
  • After booting, TOPA seems to have a crippling issue where if the first call is inbound, the phone reboots. So I guess after booting make an outbound call and everything is fine? Someone please confirm...

That audio routing thread is in the RHOD section, and I've only tested it on a RHOD - but AFAIK it should work on other devices. Let me know.
 
Last edited:
  • Like
Reactions: Starsheriff

arrrghhh

Inactive Recognized Developer
Feb 10, 2007
11,907
3,854
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!
 

hb5

Senior Member
Mar 10, 2008
154
17
I have a small problem,when I run haret it comes to animated logo and then my phone go to rebote?
 
Last edited:
  • Like
Reactions: badass163

kujrv1

Member
Oct 29, 2008
25
1
Every time when is starting FRX07 the mobile reboot and start's windows?. Where is the problem?...
 

zooster

Senior Member
Oct 14, 2007
2,151
281
Use the latest kernel and rootfs, not the ones bundled with frx07.
 
Last edited:

arrrghhh

Inactive Recognized Developer
Feb 10, 2007
11,907
3,854

ebsbow

Senior Member
Jul 22, 2008
714
103
Antwerpen
Will you guy's please make an effort and read other posts on this topic instead of clogging up the forum.
Everything you need to know has been posted already, multiple times.
 

arrrghhh

Inactive Recognized Developer
Feb 10, 2007
11,907
3,854
last three kernels didn't work on my topa100
it runs haret and then reboot the device

I too have the reboot issue on animated start screen. Latest kernel used.

Any suggestions??

I put the last kernel and i have the same issue. Reboot on Animated logo

Wait...

Use the latest kernel and rootfs, not the ones bundled with frx07.

Seems to make me think it's working on the newest rootfs and kernel - is this not true?
 

mweirauch

Senior Member
Jun 23, 2009
360
29
www.m-phasis.de
Seems to make me think it's working on the newest rootfs and kernel - is this not true?

I've been switching my TOPA to FRX07 + .27 + rootfs (all selfbuilt) yesterday, and it boots up fine since the latest kernel fix.

So anything reported not working with latest autobuild kernel implies user error for me if it resets during bootanimation.

arrrghhh, thanks for taking care of the topa threads! So I can concentrate on not getting anything done for .35 :)

Michael
 

arrrghhh

Inactive Recognized Developer
Feb 10, 2007
11,907
3,854
Topaz can boot with last kernel, with htc-msm-linux @ 20110718_223029 it doesn't.

20110718_223029 is the latest kernel tho... are you saying emwe is lying? :p.

emwe - perhaps you should be like us heathens and try to run the pre-compiled binaries? I know, blasphemy...
 

uberto.costanzo

Senior Member
Sep 25, 2008
1,415
87
Venice Italy
Hi to all, is 2 day frx7 work in my topaz all work bt, wifi, 3g, lokscreen, rotate screen (no good) photo, opera, sms, gps an battery when is 10% work 6 hour, is speed. i like use android. thanks
 

Top Liked Posts

  • There are no posts matching your filters.
  • 17
    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.
    3
    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!
    2
    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.
    2
    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 :(

    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.
    2
    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!