• 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
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
    164 bytes · Views: 20,185
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:

arrrghhh

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

  • BT - works now! 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...
    NOTE: BT must be disabled in WinMo before booting Android or else you'll run into all sorts of odd issues...
  • WEP on wifi doesn't work. I heard an app called 'wifi-ace' (on the Market) fixes WEP!
  • If auto-brightness is enabled, the keyboard/button lights will fail at random. See this post for more scant details :p.
 
Last edited:

wmg316

Senior Member
Dec 30, 2009
1,534
468
Tyler, TX
Quick question. Prior to right now I've been running Hyc's 5/30 build very successfully and very happily. With that build, sound was working when recording a video. With the new FRX07, no sound comes when recording a video. Any ideas on how to get the sound to work with recording video on FRX07?
 

arrrghhh

Inactive Recognized Developer
Feb 10, 2007
11,907
3,854
Quick question. Prior to right now I've been running Hyc's 5/30 build very successfully and very happily. With that build, sound was working when recording a video. With the new FRX07, no sound comes when recording a video. Any ideas on how to get the sound to work with recording video on FRX07?

His build has the new acoustic code seen here. It routes audio in a much better fashion, for sure... but it's not stable. Still needs some work, so it's not in FRX07...
 
  • Like
Reactions: wmg316

webxplore

Senior Member
Jan 19, 2007
99
9
Big thanks to every one on the dev team for FRX07. You guys are awesome.

Just extracted FRX07 on to a newly formatted sdcard, copied startup & calib from FRX06 and when I launch haret, i get the following error.

"Error reading file. Expected 4096 got 0"

Anyone know what it means? Search did not turn up many useful hits.
 
Last edited:

webxplore

Senior Member
Jan 19, 2007
99
9
Big thanks to every one on the dev team for FRX07. You guys are awesome.

Just extracted FRX07 on to a newly formatted sdcard, copied startup & calib from FRX06 and when I launch haret, i get the following error.

"Error reading file. Expected 4096 got 0"

Anyone know what it means? Search did not turn up many useful hits.

Figured out...Had a corrupt zimage file. Able to launch now.
 

rtrip

Member
Jan 27, 2008
23
2
After a few hours of testing, great job!

The battery status actually tracks really close to where windows mobile says it should be. It also seems to go to sleep, and stay sleeping!

The only thing that's keeping me from using it full time is the phone and speaker phone have noticeable static that windows mobile doesn't have. Does the beta audio routing fix this, or are there some new settings I can try?

I also love the recent apps on end long press, fancy :)
 

maff1989

Senior Member
Sep 20, 2010
408
83
Bolingbrook
First Impressions

Coming from FroyoB Hercules, this is a step up in my opinion. A HUGE step up.

I am running the Tilt2 with a 2GB Class 2 SD card and the provided FRX07 package .zip.

The build is running smooth and silky (making me have more faith in looped builds heh heh) with slight overclocking (633.600MHz). Had one hot reboot while accessing the Notification bar at the same time Market was updating Google apps, but after that the updates proceeded without issue. Everything else has yet to be tested, but I'm sure I won't run into anything major.

I'm 110% satisfied running the build. Accessing menus is quick and not laggy at all. To me, that's what's important: user functionality. You guys nailed it big time, and for that I thank you all very much. I won't be using CWM for a looong while ;)

EDIT: Figured I'd list what is and isn't working for me. Again, I'm using all the default components like kernel and whatnot on the Tilt2 and have the phone overclocked to 710.400MHz now:

WiFi - Works
Data - Works (most stable I've experienced)
Bluetooth - Works (haven't tried headset)
WiFi HotSpot - Buggy; Turns on, but disabling keeps the notification icon and enabling again causes reboot. Different kernel doesn't fix.
USB Tethering - Works/Turns On (Don't have the driver to test quite yet :p)
Camera/Camcorder - Works (Camcorder doesn't record sound.. known issue?)
Phone - Works flawlessly
MMS - Incoming/Outgoing Works
 
Last edited:
  • Like
Reactions: howhi50

bigheadlyf

Senior Member
Jun 4, 2009
79
16
Coming from FroyoB Hercules, this is a step up in my opinion. A HUGE step up.

I am running the Tilt2 with a 2GB Class 2 SD card and the provided FRX07 package .zip.

The build is running smooth and silky (making me have more faith in looped builds heh heh) with slight overclocking (633.600MHz). Had one hot reboot while accessing the Notification bar at the same time Market was updating Google apps, but after that the updates proceeded without issue. Everything else has yet to be tested, but I'm sure I won't run into anything major.

I'm 110% satisfied running the build. Accessing menus is quick and not laggy at all. To me, that's what's important: user functionality. You guys nailed it big time, and for that I thank you all very much. I won't be using CWM for a looong while ;)


+1

Come from FroyoB Hercules v2.

Any possible to run FRX07 on CWM?:p
 

highlandsun

Inactive Recognized Developer
Sep 15, 2009
872
263
Los Angeles
highlandsun.com
After a few hours of testing, great job!

The battery status actually tracks really close to where windows mobile says it should be. It also seems to go to sleep, and stay sleeping!

The only thing that's keeping me from using it full time is the phone and speaker phone have noticeable static that windows mobile doesn't have. Does the beta audio routing fix this, or are there some new settings I can try?

I also love the recent apps on end long press, fancy :)

I would bet that the new audio routing stuff fixes the static problems. It definitely cleaned things up for me. But at this point I think we need a newer kernel in addition to the new audio libraries, the stuff in that audio routing thread is rather out of date at the moment.


I've been running most of this stuff for more than a month without issues. It's definitely going to be a lot more solid than any previous builds...
 

Top Liked Posts

  • There are no posts matching your filters.
  • 65
    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.
    18
    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.
    14
    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
    13
    Yay! No more "when is FRX07 coming out?" posts!

    And to that effect, I would like to personally apologize to everyone for how long it took. Life has been crazy busy the past couple months. Hopefully we'll get GRX01 out in a more timely manner. :D
    11
    Caveats:

    • BT - works now! 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...
      NOTE: BT must be disabled in WinMo before booting Android or else you'll run into all sorts of odd issues...
    • WEP on wifi doesn't work. I heard an app called 'wifi-ace' (on the Market) fixes WEP!
    • If auto-brightness is enabled, the keyboard/button lights will fail at random. See this post for more scant details :p.