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

Search This thread

mistervinavil

Member
Mar 20, 2010
13
1
Just started Android on my blackstone
I don't seem to be able to switch between apps, phone and the browser.
Once I'm there I can only use what I've selected and there doesn't seem to e a way to go back to a main screen or home whatsoever.
Guessing the "hardware"buttons are failing

Changed keyboard settings in startup.txt.
from the standard startup to en very long cmdline I found in this post. Nothing works?

Please help.

I had the same problem with my blackstone: i used the second system2.ext (15july) and now home button works fine! :D
 

arrrghhh

Inactive Recognized Developer
Feb 10, 2007
11,906
3,851
I had the same problem with my blackstone: i used the second system2.ext (15july) and now home button works fine! :D

No need for that, just update to the newest rootfs and put the physkeyboard setting in your startup.txt... this is in the caveat post folks, please read it.

Sent from my Touch Pro 2 using XDA App
 

g3rm0

Senior Member
Feb 20, 2010
163
81
I'll just leave it right here ;)

IMPORTANT NOTES:
This is the most recent kernel (same as 20111017_080427 from autobuild) with jbruneaux "fix" for cracking audio. It was modified by me so it shouldn't break other devices like original solution did. All it does is temporary disabling of battery polling when speaker/headphones are active. This means battery status won't be updated until music is stopped. Modules are quite big because I had trouble with stripping them. Still... they should be functionally identical with the ones from autobuild.

Please note that I can't guarantee everything will work as with autobuild kernel. Unfortunately I've deleted all my linux VM files (by accident) and had to redo everything from a scratch. My previous build configuration was pretty solid but the new one is still unproven.
 

Attachments

  • kernel+modules-audio_shuttering.zip
    8.8 MB · Views: 169

welard

Senior Member
May 5, 2009
297
14
I'll just leave it right here ;)

IMPORTANT NOTES:
This is the most recent kernel (same as 20111017_080427 from autobuild) with jbruneaux "fix" for cracking audio. It was modified by me so it shouldn't break other devices like original solution did. All it does is temporary disabling of battery polling when speaker/headphones are active. This means battery status won't be updated until music is stopped. Modules are quite big because I had trouble with stripping them. Still... they should be functionally identical with the ones from autobuild.

Please note that I can't guarantee everything will work as with autobuild kernel. Unfortunately I've deleted all my linux VM files (by accident) and had to redo everything from a scratch. My previous build configuration was pretty solid but the new one is still unproven.


hi g3rm0...

i see your running gingerbread 2.3.7 on our blackstone, would u like to share?......would love to try your (own build)

thanks for the new kernel!:)
 

g3rm0

Senior Member
Feb 20, 2010
163
81
hi g3rm0...

i see your running gingerbread 2.3.7 on our blackstone, would u like to share?......would love to try your (own build)

thanks for the new kernel!:)

Hi,

I don't want to release anything that's wasn't published officially by XDAndroid devs. Also it's not exactly "my build" it's the same as XDAnroid repo with my apps and ringtones. I'm sure official release (better than my homegrown stuff) will come soon.

I should probably change my sig ;)
 

welard

Senior Member
May 5, 2009
297
14
Hi,

I don't want to release anything that's wasn't published officially by XDAndroid devs. Also it's not exactly "my build" it's the same as XDAnroid repo with my apps and ringtones. I'm sure official release (better than my homegrown stuff) will come soon.

I should probably change my sig ;)

ok thats fine i really understand.....i also tryed gingerbread 2.3.7 but had wake issues and camera not working after changing libcamera, liboemcamera, libcamera.service and libcamera.client......can i ask how you solved those two things....thanks
 

g3rm0

Senior Member
Feb 20, 2010
163
81
ok thats fine i really understand.....i also tryed gingerbread 2.3.7 but had wake issues and camera not working after changing libcamera, liboemcamera, libcamera.service and libcamera.client......can i ask how you solved those two things....thanks

I didn't have any issues with sleep/wake on current kernel and build (there is pm.sleep_mode=1 in my startup.txt but it's probably irrelevant). Camera can take stills but not video - known bug.
If you follow this tutorial you should be able to build your own system image with minimum effort. However there are few things to note:
1. You need to use Ubuntu 10.04. It won't work on older version and there are additional steps in Ubuntu 11.10 (not covered by this tutorial).
2. First build takes absurdly long time. It was something like 10 hours on my Linux VM. May be faster on quad-core native Linux machine but still it will be hours.
3. Using OpenJDK may not work! It's better to use latest sun-java6-jdk.
4. In step "Build Dependencies" you need to do everything as described with two exceptions.
a) signed-dream_devphone_userdebug-ota-14721.zip is no longer available on HTC Developer Center - google it.
b) HW3D driver is outdated. Google hw3d-20111216.zip.
5. Last thing to do before build is add booksphone.apk manually because it's missing from the latest gapps package. Google it and place under vendor/xdandroid/msm/proprietary.
 

welard

Senior Member
May 5, 2009
297
14
I didn't have any issues with sleep/wake on current kernel and build (there is pm.sleep_mode=1 in my startup.txt but it's probably irrelevant). Camera can take stills but not video - known bug.
If you follow this tutorial you should be able to build your own system image with minimum effort. However there are few things to note:
1. You need to use Ubuntu 10.04. It won't work on older version and there are additional steps in Ubuntu 11.10 (not covered by this tutorial).
2. First build takes absurdly long time. It was something like 10 hours on my Linux VM. May be faster on quad-core native Linux machine but still it will be hours.
3. Using OpenJDK may not work! It's better to use latest sun-java6-jdk.
4. In step "Build Dependencies" you need to do everything as described with two exceptions.
a) signed-dream_devphone_userdebug-ota-14721.zip is no longer available on HTC Developer Center - google it.
b) HW3D driver is outdated. Google hw3d-20111216.zip.
5. Last thing to do before build is add booksphone.apk manually because it's missing from the latest gapps package. Google it and place under vendor/xdandroid/msm/proprietary.

thanks alot for all the info.....will give it a shot....thanks again
 

arrrghhh

Inactive Recognized Developer
Feb 10, 2007
11,906
3,851
I didn't have any issues with sleep/wake on current kernel and build (there is pm.sleep_mode=1 in my startup.txt but it's probably irrelevant). Camera can take stills but not video - known bug.
If you follow this tutorial you should be able to build your own system image with minimum effort. However there are few things to note:
1. You need to use Ubuntu 10.04. It won't work on older version and there are additional steps in Ubuntu 11.10 (not covered by this tutorial).
2. First build takes absurdly long time. It was something like 10 hours on my Linux VM. May be faster on quad-core native Linux machine but still it will be hours.
3. Using OpenJDK may not work! It's better to use latest sun-java6-jdk.
4. In step "Build Dependencies" you need to do everything as described with two exceptions.
a) signed-dream_devphone_userdebug-ota-14721.zip is no longer available on HTC Developer Center - google it.
b) HW3D driver is outdated. Google hw3d-20111216.zip.
5. Last thing to do before build is add booksphone.apk manually because it's missing from the latest gapps package. Google it and place under vendor/xdandroid/msm/proprietary.

Can't believe no one has thanked this post...

g3rm0, nicely done. The Getting the Source and related pages have been updated to reflect all these silly gotchas. Thanks again!
 
  • Like
Reactions: Danny04

snake65

Senior Member
May 19, 2009
639
128
Adelaide
Hotspot

First of thanks for the great build.
Just wondering if any one has a fix for the wifi hotspot crashing wifi and it doesn't seem to matter what hotspot program I use. Any help would be much appreciated.
Cheers
John
 

arrrghhh

Inactive Recognized Developer
Feb 10, 2007
11,906
3,851
First of thanks for the great build.
Just wondering if any one has a fix for the wifi hotspot crashing wifi and it doesn't seem to matter what hotspot program I use. Any help would be much appreciated.
Cheers
John

Maybe this is a Blackstone thing? If so, I'll need logs. I don't have a Blackstone.

The built-in wifi tethering app works great on RHOD... until you try to disable it. Locks up the phone hard, must reboot. Again, it works great until you disable.

As for the third party ones (like XDAndroid's own) work just fine on RHOD, they just don't put up a 'real' AP. It creates an adhoc AP, similar to how wifi tethering works on WinMo.
 

Igoritza

Senior Member
May 23, 2008
209
101
Belgrade
Im fairly capable with tech, im also an android app developer, but I really cant read whole 46 pages, please help me:

I got myself a replacement Digitizer, and it's NOT hard to replace it if it's bought separately from screen. I purchased it on amazon for 13$, and it works perfectly. only thing that botheres me is goddamn dust particle stuck in between, and i just cant open it again .. too much trouble.

so, Im now interested in isntaling android, cause I want to educate my little brother who is apple fan, and giving him Android blackstone instead of his 2G iPhone.

with the latest build on this thread, does everything work ? I reached page 10, and saw that camera and keyboard are not working, keyboard has the market solution, but what about camera .. ?

and, could someone please link the latest instruction post for instaling android .. ?


Im again really sorry for not reading the whole thread, I just dont have time, cause im working 2 jobs at the moment, and I really want to Androify my little brother for his birthday. Im owner of Desire Z, and I still didnt have time to remove stock HTC with something awesome, cause Desire Z has so much potential.
 

arrrghhh

Inactive Recognized Developer
Feb 10, 2007
11,906
3,851
Im fairly capable with tech, im also an android app developer, but I really cant read whole 46 pages, please help me:

I got myself a replacement Digitizer, and it's NOT hard to replace it if it's bought separately from screen. I purchased it on amazon for 13$, and it works perfectly. only thing that botheres me is goddamn dust particle stuck in between, and i just cant open it again .. too much trouble.

so, Im now interested in isntaling android, cause I want to educate my little brother who is apple fan, and giving him Android blackstone instead of his 2G iPhone.

with the latest build on this thread, does everything work ? I reached page 10, and saw that camera and keyboard are not working, keyboard has the market solution, but what about camera .. ?

and, could someone please link the latest instruction post for instaling android .. ?


Im again really sorry for not reading the whole thread, I just dont have time, cause im working 2 jobs at the moment, and I really want to Androify my little brother for his birthday. Im owner of Desire Z, and I still didnt have time to remove stock HTC with something awesome, cause Desire Z has so much potential.

Such a long rambling post about nothing...

Use search.

Read the first post, install process is there.

No one expects you to read every post in the entire thread...

I don't have a Blackstone, but I think the rear cam works. Front does not.
 

Igoritza

Senior Member
May 23, 2008
209
101
Belgrade
oh, sorry, i saw another thread where dude didnt edit the first post, so you had to find the instructions through whole thread, of 100+ pages. im on it now. will post results.
 

Biofobico

Member
Jan 28, 2009
12
0
Caveats:

(...) (in conjunction with physkeyboard=blac in your startup.txt)!
How should I insert that piece of code?
I tried like this with no success;
Code:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2030
set KERNEL zImage
set initrd initrd.gz
set cmdline "msmts_calib=0x395.0x3c9.0x79.0x77 lcd.density=240 clock-7x00.a11=500 msmvkeyb_toggle=off gsensor_axis=-2,-1,3"
physkeyboard=blac
boot
I am also using your rootfs and still cant navigate using the hardware keys (or in any other way tbh).

Thanks in advance for any help.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 43
    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.
    9
    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...
    • Audio stutters every 10sec. The only fix I've heard is using a kernel from G3rmo (unfortunately it is old), or
      Code:
      su
      kill -9 28
      Which kills the [battery] process. I'm sure this will have negative effects on the battery meter/battery life...
    • SD Card not working...? "Waiting for SD Card" appearing on boot...? Try putting this command in your startup.txt
      Code:
      msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave
      See gummbah30's post reminding us of these commands.
    • SD Card has partitions? (If you used a non-XDAndroid build the answer is YES) Then you need to add "no_partitions" to your startup.txt. Between the quotes on the set cmdline line. Do not put it on its own line, it goes in between the quotes! Make sure there is one space between each item.
    • Front buttons messed up/wrong? You can use my rootfs which incorporates g3rm0's layout. This custom rootfs is no longer necessary, I have committed the changes so you can use the autobuild rootfs (in conjunction with physkeyboard=blac in your startup.txt)!
    • Keyboard tiny/unusable? Either change the IME (long press on the input box) Get rid of it! I've heard "Hackers Keyboard" is a good alternative - many options. There's also "Better Keyboard", Swype, etc... Side load the APK using AndroidApps, adb install, etc.
    6
    ok thats fine i really understand.....i also tryed gingerbread 2.3.7 but had wake issues and camera not working after changing libcamera, liboemcamera, libcamera.service and libcamera.client......can i ask how you solved those two things....thanks

    I didn't have any issues with sleep/wake on current kernel and build (there is pm.sleep_mode=1 in my startup.txt but it's probably irrelevant). Camera can take stills but not video - known bug.
    If you follow this tutorial you should be able to build your own system image with minimum effort. However there are few things to note:
    1. You need to use Ubuntu 10.04. It won't work on older version and there are additional steps in Ubuntu 11.10 (not covered by this tutorial).
    2. First build takes absurdly long time. It was something like 10 hours on my Linux VM. May be faster on quad-core native Linux machine but still it will be hours.
    3. Using OpenJDK may not work! It's better to use latest sun-java6-jdk.
    4. In step "Build Dependencies" you need to do everything as described with two exceptions.
    a) signed-dream_devphone_userdebug-ota-14721.zip is no longer available on HTC Developer Center - google it.
    b) HW3D driver is outdated. Google hw3d-20111216.zip.
    5. Last thing to do before build is add booksphone.apk manually because it's missing from the latest gapps package. Google it and place under vendor/xdandroid/msm/proprietary.
    5
    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 keya 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.

    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.
    • 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
    3
    Download "Spare parts" from market to remap "end call" to Home. It's the easiest way. You can remap shutdown button to end calls too in Settings/Accesibility menu.

    It's also provided in the AndroidApps/Other folder - it has no ad's ;).

    ok if i mix arrrghhh's rootfs and mod with g3rm0 patched kernel my phone wont finish its android boot.... again....
    if i use both g3rm0 kernel and roofts with arrrghhh's FRX07 build it freezes in the android boot again

    i tried an older version of his kernel and it still didnt work with FRX07 .... temprimental mod isnt it

    what is a ROOFTS???? whats the difference between yours and this guys?
    could arrrghhh add this key formating from his roofts into urs?

    EDIT: Tried the latest g3rm0 kernel again after a few restarts and its working :) playing music much better, occasional hickup but nothing as bad

    rootfs changed quite a bit for FRX07. Not sure why it would cause issues with g3rm0's kernel...

    yes please! and music patch in next package

    This "music patch" literally disables the [battery] process... while it's a noble effort to fix BLAC's music woe's, it is not an acceptable patch for mainline kernels... sorry. Someone's actually going to have to figure out what in the battery code is causing the issue for BLAC's :p.

    I want to ask a question...

    There was an option on Froyo X Red build is that:

    When you click long press at home screen, you can choose preferences option and you can easily arrange action bindings double tab swipe up or down etc...

    Is there any option at that build like Froyo X Red?

    Thanks...

    I think that's just part of Zeam launcher. You can use any launcher you please on FRX07 - I prefer ADW myself. All on ze Market.

    Any thing work perfect in Topaz (kernel:1332), except the incoming call, still need to make a "1'st call" as FRX06, any idea?

    Yea, emwe hasn't been able to fix this bug... sorry!