[BUILD] **Complete FroYo Bundle** FRX07.1 - Maintenance Release
- Thread starter arrrghhh
- Start date
thanks for the help..
I will try the other android version.
I will leave feedback..
... I was loking for the files of the NAND but I can't download it.. do you now where I can get those? I will be very pleasure to test that bundle and leave my feedback to the rest of the comunity.
I will try the other android version.
I will leave feedback..
... I was loking for the files of the NAND but I can't download it.. do you now where I can get those? I will be very pleasure to test that bundle and leave my feedback to the rest of the comunity.
After some reading on other posts..
I need to update the "startup.txt". I add this comand to the cmd line "msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave"
Now I have the startup.txt like this:
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 gsensor_axis=-2,-1,3 pm.sleep_mode=1 physkeyboard=blac msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave"
boot
WORKS PERFECT :victory:
Many Thanks
I need to update the "startup.txt". I add this comand to the cmd line "msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave"
Now I have the startup.txt like this:
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 gsensor_axis=-2,-1,3 pm.sleep_mode=1 physkeyboard=blac msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave"
boot
WORKS PERFECT :victory:
Many Thanks
Kernel download where?
Hi together,
1. the download links to http: zimages.googlecode.com/files are down.. any idea where to get other kernel or updates?
2. I have problems with the installation on HTC Blackstone.. after at least 15 trys wiith different SD cards, formatting, builds it now seems to install.. but after a few minutes there is shown since at least 10 minutes now "init: /init.rc: xxx: ignored duplicate definition of service .. >> dhcpcd >> ppd_gprs >>keystore >>mtpd >>wlan:loader ... and so on..
the boot display is not frozen and the messages repeats
any idea?
thanks for all
Hi together,
1. the download links to http: zimages.googlecode.com/files are down.. any idea where to get other kernel or updates?
2. I have problems with the installation on HTC Blackstone.. after at least 15 trys wiith different SD cards, formatting, builds it now seems to install.. but after a few minutes there is shown since at least 10 minutes now "init: /init.rc: xxx: ignored duplicate definition of service .. >> dhcpcd >> ppd_gprs >>keystore >>mtpd >>wlan:loader ... and so on..
the boot display is not frozen and the messages repeats
any idea?
thanks for all
Clock drift and battery life - use faster microSD
I had installed FRX07.1 on different versions of microSD and my conclusion is that the newer and faster cards give better clock consistency and improved battery life.
First, I tried an old (2008) class-2 8GB microSD. That did not work too well. Startup was problematic and sometimes need a couple of reboots before getting Android out. The clock drift and short battery life was very apparent.
Then I tried another newer (2010) no-class 8GB microSD. This worked better but I still experienced the clock drift (less than the previous microSD install) and relatively short battery life (10-14 hrs on standby).
Finally, I bought a new Class 4 32GB microSD and this worked much better. I did not experience any noticeable clock drift and battery life seemed to improved (in excess of 14 hours on standby but this was down to almost being drained so I had to charge it).
Based on my experience with different age and class of microSD cards, I have arrived a a simplistic conclusion that:
1. Faster cards have better read/write access times and this attributes to better clock (display) accuracy.
2. Faster cards will also have shorter dwell times in the read/write modes, so sucks up less energy.
3. Newer technology produces more energy-efficient cards.
Hope this helps those who wants to venture on the using this build.
PS:
I have now progressed to the the NAND ROM by fagyi.
[ROM] {NAND} AOSP-GBX | < Kernel: 2.6.27 > | 2013.01.20
It is now about 24 hours since Fully-charged (charging was done with device switched-off),
and battery icon reads 55%. Device was mostly on standby mode.
I had installed FRX07.1 on different versions of microSD and my conclusion is that the newer and faster cards give better clock consistency and improved battery life.
First, I tried an old (2008) class-2 8GB microSD. That did not work too well. Startup was problematic and sometimes need a couple of reboots before getting Android out. The clock drift and short battery life was very apparent.
Then I tried another newer (2010) no-class 8GB microSD. This worked better but I still experienced the clock drift (less than the previous microSD install) and relatively short battery life (10-14 hrs on standby).
Finally, I bought a new Class 4 32GB microSD and this worked much better. I did not experience any noticeable clock drift and battery life seemed to improved (in excess of 14 hours on standby but this was down to almost being drained so I had to charge it).
Based on my experience with different age and class of microSD cards, I have arrived a a simplistic conclusion that:
1. Faster cards have better read/write access times and this attributes to better clock (display) accuracy.
2. Faster cards will also have shorter dwell times in the read/write modes, so sucks up less energy.
3. Newer technology produces more energy-efficient cards.
Hope this helps those who wants to venture on the using this build.
PS:
I have now progressed to the the NAND ROM by fagyi.
[ROM] {NAND} AOSP-GBX | < Kernel: 2.6.27 > | 2013.01.20
It is now about 24 hours since Fully-charged (charging was done with device switched-off),
and battery icon reads 55%. Device was mostly on standby mode.
I tried it, and it works flawlessly. In fact, i use it as a daily phone side by side with two HD2s running nativesd, and a GT-N7100.
And at times, i wonder if the Touch HD will be strong enough to withstand the winds of ICS or maybe even Jellybean...
And at times, i wonder if the Touch HD will be strong enough to withstand the winds of ICS or maybe even Jellybean...
Nope. Not enough resources - too slow CPU, too little memory in ROM and RAM.
Since you have 2 HD2s, you could try to ICS or JB one of them. HD2s should have enough juice to run ICS/JB
Last edited:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
43FRX07.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
), reboot & go back to the newest kernel!
6. Run haret.exe.. Profit!
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.9Caveats:
- 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
Which kills the [battery] process. I'm sure this will have negative effects on the battery meter/battery life...Code:
su kill -9 28 - SD Card not working...? "Waiting for SD Card" appearing on boot...? Try putting this command in your startup.txt
See gummbah30's post reminding us of these commands.Code:
msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave - 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
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.5stinebd's Changelog:
stinebd said:
Layman's Changelog
(As in, the changelog I wrote)
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
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...
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.
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.
Yea, emwe hasn't been able to fix this bug... sorry!
