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

Search This thread

teemo

Senior Member
Nov 18, 2007
2,430
2,315
Kolding
RHOD100
- 1. Backup my apps
- 2. Wipe SDCard w. HP full format
- 3. Copy FRX07 edit startup and add ts-calibration
- 4. Boot haret, all seem good
- 5. Setting google account and wait for sync to finish
- 6. Start Market to dl TitaniumBackup (damn autoupdate on all the G-stuff)
- 7. Market updates 5+ apps, so I switch to WiFi (without issues), Market updates, no problems.
- 8. Restore all apps from backup
- 9. So far NO issues. (BT connects to my HTC earphones but as expected, no audio routing)

- I'm happy!

Big THANKS to all developers and arrrghhh for keeping everybody updated.
 

zooster

Senior Member
Oct 14, 2007
2,151
281
Did anyone try the new bundle on a Topaz? It doesn't work at me.
At the end of the boot animation, right after the vibration, it reboots into winmo...
Tried the whole new bundle in a brand new folder, no oc nor pm.sleep...

Ok, it's the kernel bundled with frx07 that doesn't work, with the previous kernel it can boot, but there is an issue with the sim. It doesn't get any network (no service), nor it prompt for a sim pin (finally I deactivated it but no success). It's like radio is not working...

edit: if i try to get "status" report in "about phone" under settings, nothing turns back...

edit2: it actually doesn't seem to see the sim, but sim works perfectly in winm and previous frx...

edit3: IMEI doesn't show up using *#06#.
 
Last edited:
  • Like
Reactions: yahelite-rcell

rtrip

Member
Jan 27, 2008
23
2
Has anyone found a version of Flash that works?

I tried sideloading a few 10.3 apks, none of which would install.
 

trusa1

Senior Member
Jul 27, 2009
75
4
Zagreb
Hi arrrghhh,

rootfs.img from the FRX07 full bundle and latest one (rootfs-20110716-8a5419e) from the rootfs build service are not the same. Which version is more accurate?

MD5 rootfs.img from the FRX07 full bundle: 3f93e0a4449ef0d745c47dfb5133107a
MD5 rootfs.img from the rootfs build service: 17b69bb5d063d840aa69ddf81e9b7e1d
 

stinebd

Senior Member
Apr 25, 2008
197
166
Northampton, PA
After upgrading to the full bundle (except I'm using the new haret and I added the init line in case I use .39 again), wifi would turn on, appears to scan for 30 seconds to a minute, then turns itself off. I rolled back to my last kernel from 7/11 which had never had wifi issues, and it still behaves the same way.

The latest rootfs, rootfs-20110716-245f68a.zip, fixes this issue, which is caused by the wifi interface rename in cases where a data.img already exists. Thanks.
 

zooster

Senior Member
Oct 14, 2007
2,151
281
Stinebd, do you have a clue about the problem with my topaz?

update: with or without sim inserted it doesn't change or detect anything... still an x above net bars.
 
Last edited:

maff1989

Senior Member
Sep 20, 2010
410
83
Bolingbrook
I am having the same problem too!!! Also I realized that the previous CWM versions were snappier. However, this is a great leap in our strive to weed out WinMO

Personally, I've had a snappier experience with this ROM over CWM.. although it may well be my 2GB SD card causing the sluggish CWM performance, but the loopback FS is working best for me :D
 

waltibaba

Senior Member
Oct 26, 2008
82
5
HTC Leo
Samsung Galaxy Note 10.1
Excellent work and great looking rom so far! I actually enjoy loopback much more than cwm, and at our current level of progress, nand is a definite no-go hehe.
I do have a question though; I just recently got my rhod100 and am now finding that no rom lets me use wifi (including yours). When I turn wifi on it says unable to scan networks, and turns itself off again. I looked around and noticed that this issue was spoken of before (latest I found was around december/jan). Was there a solution to that? In particular with your rom, I doubt an early kernel build will work well (or at all). Does anyone here know of a solution? I'd be very grateful!
Once again, thank you for your great work and dedication!
 

dadaR6

Member
Jul 28, 2007
46
3
This release works really well, I can finally leave my SIM card inside my RHOD400.

FYI, I noticed that if Windows was booted up with BT ON or BT was used in Windows (even turned OFF before booting Android), then Android will not enter deep sleeps. BT needs to be OFF from beginning to end in Windows. I verified this with a fresh data.img and no app was installed.
 

arrrghhh

Inactive Recognized Developer
Feb 10, 2007
11,906
3,851
Excellent work and great looking rom so far! I actually enjoy loopback much more than cwm, and at our current level of progress, nand is a definite no-go hehe.
I do have a question though; I just recently got my rhod100 and am now finding that no rom lets me use wifi (including yours). When I turn wifi on it says unable to scan networks, and turns itself off again. I looked around and noticed that this issue was spoken of before (latest I found was around december/jan). Was there a solution to that? In particular with your rom, I doubt an early kernel build will work well (or at all). Does anyone here know of a solution? I'd be very grateful!
Once again, thank you for your great work and dedication!

For wifi, have you read this section of the FAQ...?

This release works really well, I can finally leave my SIM card inside my RHOD400.

FYI, I noticed that if Windows was booted up with BT ON or BT was used in Windows (even turned OFF before booting Android), then Android will not enter deep sleeps. BT needs to be OFF from beginning to end in Windows. I verified this with a fresh data.img and no app was installed.

Interesting find. I don't ever have BT on in WinMo (or anything for that matter :p) so I'd never run into this bug. I'll add it to the caveat list.

To those who have working BT headsets - wow! I didn't expect audio to route correctly.... Seems hit or miss. Don't expect it to work well :p.
 

MisterNauta

Member
Nov 19, 2007
6
0
I'm succesfully running FRX07 on my RHODIUM. It works great, just a little bit irresponsive (I mean slow to respond). in some situations. I'm using TIM Mobile operator from Brazil.
 

951porsche

New member
Dec 5, 2007
4
0
Can anyone running FRX07 see if they can install the bestparking.com app? I've been trying to work out why it won't install for hours now and I can't get it to install, it was fine on my FRX06 before but everytime I try to install it gives me the "installation unsucessful" error.
 

nasapunk88

Senior Member
Aug 9, 2008
201
27
great battery

I just restarted from a fresh setup last night before bed and this morning went to Disneyland. I had FRX07 running and installed all my apps, didn't turn any autokill on or shut anything down from Syncing automatically. My phone lasted from 8am to around 9:30pm. O_O i've never had this long before when I'm actually using the phone. I was even on/off gps checking in (foursquare) to all places and using it in lines. Amazing Battery Life! That's 13 1/2 hours. Avg on FRX06 was 8 for me.

Excellent work! Now I have time to start playing/testing each component and I'll get back to you.
 

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.