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

Search This thread
By:
Advanced…
A

arrrghhh

Inactive Recognized Developer
Feb 10, 2007
11,906
3,851
crvmolinari said:
any suggestions to make the battery live longer?
Click to expand...
Click to collapse

Don't use widgets.

Disable apps that always sync which you don't always want syncing.

Use wifi whenever possible (it draws less power & is faster).

Disable data when not in use - this one is HUGE, but it's also a huge pain in the butt if you're used to always-on data. If you can live with data being off, your battery life will skyrocket.
 
  • Like
Reactions: crvmolinari
C

crvmolinari

Member
Dec 23, 2009
7
2
arrrghhh said:
Don't use widgets.

Disable apps that always sync which you don't always want syncing.

Use wifi whenever possible (it draws less power & is faster).

Disable data when not in use - this one is HUGE, but it's also a huge pain in the butt if you're used to always-on data. If you can live with data being off, your battery life will skyrocket.
Click to expand...
Click to collapse

THANKS! i downloaded "widgetsoid" (widget) to activate/deactivate wifi, data connection, Bluetooth, synchronization and gps in one click just when i need it... (I used to have data connection always on in winmo :S)
thanks again!
 
  • Like
Reactions: Danny04
A

arrrghhh

Inactive Recognized Developer
Feb 10, 2007
11,906
3,851
crvmolinari said:
THANKS! i downloaded "widgetsoid" (widget) to activate/deactivate wifi, data connection, Bluetooth, synchronization and gps in one click just when i need it... (I used to have data connection always on in winmo :S)
thanks again!
Click to expand...
Click to collapse

You'll never get as good of battery as WinMo. Perhaps we can get close in total sleep, no radios on... but the simple fact is Android does more in the background (apps syncing, etc) so it will suck more battery, regardless.

There's many ways the port could probably be improved as far as battery life goes - but the complete lack of manpower is troublesome.
 
R

raptus84

Member
Feb 2, 2010
10
1
Sorry but I can't undestand that thing yet. Why must you have a phisical blackstone device for an Android development? Are there noone that could give you a support for testing (without giving out his phone) or there is no possibility to develop via web/skype? Is that so "hardware-oriented"?
If this is not, I'm sure that lot of people could give their support online.
 
A

arrrghhh

Inactive Recognized Developer
Feb 10, 2007
11,906
3,851
raptus84 said:
Sorry but I can't undestand that thing yet. Why must you have a phisical blackstone device for an Android development? Are there noone that could give you a support for testing (without giving out his phone) or there is no possibility to develop via web/skype? Is that so "hardware-oriented"?
If this is not, I'm sure that lot of people could give their support online.
Click to expand...
Click to collapse

a) You'd need a really good tester
b) You'd need to work with them very closely
c) It'd still be 10,000,000x easier with the device in-hand to test changes on the fly. C'mon, is this really so hard to grasp?

If you don't want to donate, that's fine. But don't fill the thread with drivel, thanks.
 
jeanfrederic

jeanfrederic

Senior Member
Dec 29, 2007
506
11
Bruxelles
www.whazup.be
arrrghhh said:
Caveats:​
[*]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)!
[/list]
Click to expand...
Click to collapse
Hello, I'm trying to run your FRX7.1 from WinMo Premium EDGE v4.0.2 made by ypsmav.
Although i tried your advice here above, I still can't use my front buttons.
Could you please tell me if my startut.txt is correct?

set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2030
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmvkeyb_toggle=off msm_blackstone_pad.vibrate=1 physkeyboard=blac gsensor_axis=-2,-1,3 pm.sleep_mode=1"
boot
Click to expand...
Click to collapse
Mind I use the latest rootfs.
Thx a lot.


By the way, the last kernel htc-msm-linux-2.6.35-20120127_222030-package.tar.bz2 prevent my blackstone to boot...
 
Last edited:
masrterk

masrterk

Senior Member
Jul 27, 2008
541
23
www.ppctuga.net
Android Rom please . Wm6.x is Dead

now is time for android development
Can´t wait for a full Android rom
if some one interested to develope a full Android rom i will donate ...

thanks
 
A

arrrghhh

Inactive Recognized Developer
Feb 10, 2007
11,906
3,851
jeanfrederic said:
Hello, I'm trying to run your FRX7.1 from WinMo Premium EDGE v4.0.2 made by ypsmav.
Although i tried your advice here above, I still can't use my front buttons.
Could you please tell me if my startut.txt is correct?


Mind I use the latest rootfs.
Thx a lot.


By the way, the last kernel htc-msm-linux-2.6.35-20120127_222030-package.tar.bz2 prevent my blackstone to boot...
Click to expand...
Click to collapse

Blackstone can't use .35 kernels.

Upgrade the rootfs please, not the kernel. I need to make a new bundle, sorry.
 
A

arrrghhh

Inactive Recognized Developer
Feb 10, 2007
11,906
3,851
jeanfrederic said:
OK, thx for your reply. Will forget about kernel, About rootfs, it is already upgraded.
But any idea why I can't use the front buttons?
Thx
Click to expand...
Click to collapse

Assuming you followed the steps correctly, no.

You're on the newest rootfs, and it's named rootfs.img. There's no old rootfs' on your card. You also have physkeyboard=blac in your startup.txt.

If those are true, the front buttons should work just fine. Paste your startup.txt if you can't figure it out... I honestly don't know why this is so difficult to understand, but I realize it's a simple thing to update on my end. Just been ridiculously busy at work lately.
 
jeanfrederic

jeanfrederic

Senior Member
Dec 29, 2007
506
11
Bruxelles
www.whazup.be
arrrghhh said:
Assuming you followed the steps correctly, no.

You're on the newest rootfs, and it's named rootfs.img. There's no old rootfs' on your card. You also have physkeyboard=blac in your startup.txt.

If those are true, the front buttons should work just fine. Paste your startup.txt if you can't figure it out... I honestly don't know why this is so difficult to understand, but I realize it's a simple thing to update on my end. Just been ridiculously busy at work lately.
Click to expand...
Click to collapse

I know Android on Blackstone from the beginning, so I guess I know how to update the rootfs, but since the beginning (android 1.6) it runs randomly on my Blackstone. I tried your build on 3 differents µSD (2 no-class, 1 class 4) with no luck, even stock 7.1 doesn't works at it should. It is just...boring. This blackstone is gonna learn to fly, i'm pretty sure of !
 
K

kevinmys

New member
Jul 10, 2007
1
0
I had the same behaviour on my blackstone, impossible to use the home button and I have followed the guidance... I have edited the startup file, added the physkeyboard=blac and restarted android and now it works

if it can help here is the content of my startup

set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2030
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 physkeyboard=blac msmvkeyb_toggle=off msm_blackstone_pad.vibrate=1 gsensor_axis=-2,-1,3 pm.sleep_mode=1"
boot

and now it works fine, I can at last use this rom :)

hope that helps

Youpee
 
jeanfrederic

jeanfrederic

Senior Member
Dec 29, 2007
506
11
Bruxelles
www.whazup.be
kevinmys said:
I had the same behaviour on my blackstone, impossible to use the home button and I have followed the guidance... I have edited the startup file, added the physkeyboard=blac and restarted android and now it works

if it can help here is the content of my startup

set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2030
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 physkeyboard=blac msmvkeyb_toggle=off msm_blackstone_pad.vibrate=1 gsensor_axis=-2,-1,3 pm.sleep_mode=1"
boot

and now it works fine, I can at last use this rom :)

hope that helps

Youpee
Click to expand...
Click to collapse
Except the sentence "physkeyboard=blac" is not at the same place, we have exactly the same startup.txt. Will try your config, who knows...
Thanks anyway.
 
A

arrrghhh

Inactive Recognized Developer
Feb 10, 2007
11,906
3,851
jeanfrederic said:
Except the sentence "physkeyboard=blac" is not at the same place, we have exactly the same startup.txt. Will try your config, who knows...
Thanks anyway.
Click to expand...
Click to collapse

Doesn't matter where in the cmdline the command goes. It just needs to be somewhere on the cmdline between the quotes, with at least one space between each item.

You're also on the newest autobuild rootfs?
 
jeanfrederic

jeanfrederic

Senior Member
Dec 29, 2007
506
11
Bruxelles
www.whazup.be
I tried without the TS calibration, with 1225 kernel and with your, with latest rootfs and with yours from the bundle. The front buttons make the blackstone to vibrate, but still do not work. I don't understand why...
 
A

arrrghhh

Inactive Recognized Developer
Feb 10, 2007
11,906
3,851
jeanfrederic said:
I tried without the TS calibration, with 1225 kernel and with your, with latest rootfs and with yours from the bundle. The front buttons make the blackstone to vibrate, but still do not work. I don't understand why...
Click to expand...
Click to collapse

The ts-calib shouldn't have anything to do with the front buttons, from what I understand. I assume the touchscreen is accurate and works well?

Did you put the newest rootfs AND make the startup.txt change, physkeyboard=blac?
 
You must log in or register to reply here.

Similar threads

T
  • Locked
Android 2.2 (FroYo) On HTC [03 Sep 2010] (V1.6)
Replies
1K
Views
856K
Chef_Tony
Chef_Tony
A
  • Locked
[BUILD] **Complete GingerBread Bundle!!** GBX0A - Alpha! Camera!
Replies
84
Views
134K
A
arrrghhh
S
[Glossy Themed Eclair(2.0.1]+[Android 2.1 with SENSE (beta).. NEW BUILD (08/04/2010)
Replies
759
Views
280K
CoolThingsBro
CoolThingsBro
S
  • Locked
[ROM | 1/5/2011] - NANDDROID - Android Froyo X Ginger Build
Replies
155
Views
91K
TheDeadCPU
TheDeadCPU
osamaa
[PROJECT] Android Flan 2.1 Hero build with Sense UI - Added conf for swap partition
Replies
172
Views
124K
H
HTC Guess

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 43
    A
    arrrghhh
    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
    9
    A
    arrrghhh
    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.
    View
    6
    g3rm0
    g3rm0
    welard said:
    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
    Click to expand...
    Click to collapse

    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.
    View
    5
    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 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.
    Click to expand...
    Click to collapse

    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
    View
    3
    A
    arrrghhh
    Eodun said:
    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.
    Click to expand...
    Click to collapse

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

    alphecca911 said:
    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
    Click to expand...
    Click to collapse

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

    alphecca911 said:
    yes please! and music patch in next package
    Click to expand...
    Click to collapse

    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.

    faramir86us said:
    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...
    Click to expand...
    Click to collapse

    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.

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

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

New posts