Try disabling GPS when you don't need it. Settings > Location & Security > Untick Use GPS Satellites
[BUILD] **Complete FroYo Bundle** FRX07.1 - Maintenance Release
- Thread starter arrrghhh
- Start date
-
- Tags
- htc touch pro2 xdandroid
Try disabling GPS when you don't need it. Settings > Location & Security > Untick Use GPS Satellites
Ya this thing is definitely a battery burner. That said, our devices are up to two years old now and before I switched I could already tell my battery just can't hold a charge like it used to.
Thanks guys for the tips, yeah I figured the battery was just getting old (it only needs to hold out for 4 more months!!), I did disable the GPS just now lets see if that helps any.
EDIT: Wow the light actually went green without me having to do a fresh restart. Maybe this GPS thing really worked.
EDIT: Wow the light actually went green without me having to do a fresh restart. Maybe this GPS thing really worked.
lol, the GPS bug is no lie.
One of the developers (emwe) fixed that bug in GB, hoping he can port it back to FroYo...
Although with that bug (along with GPS in general) fixed in GB, that'll be a very usable build. Can't wait for that release
.Does HTC G1 have almost the same hardware specs as the HTC touch pro2? I believe TP2 has even more memory than the G1, but how come my friends G1 works faster and smoother than my HTC touch pro2, even if I already OC it. Any thoughts? Thanks.
We're running hacks-in-progress off an sd card, they're running finished professionally tailored wares, possibly with some proprietary drivers off nand. Even if they run mods, it's easier to hack from a finished android product than it is to hack away from winmo.
Pretty much what fortunz said. I wouldn't ever expect our devices to be on-par with native ones, but perhaps one day.
BT looping on and off
After turning on BT on my phone it loops on and off. It comes on, scans and detect devices, turns off, and then turns itself on and starts over. I tried reading through all 51 pages of this thread (and searching elsewhere) but I have not found a resolution to this issue. Every one that I see posting about this issue seems to have resolved it by making sure BT is off in Windows before loading Android. I have turned on Airplane mode in Windows and rebooted into Windows before trying to load Android but I still have the issue. I am sure I am likely just doing something wrong ... any help would be greatly appreciated.
I have attached my logs in case it helps.
After turning on BT on my phone it loops on and off. It comes on, scans and detect devices, turns off, and then turns itself on and starts over. I tried reading through all 51 pages of this thread (and searching elsewhere) but I have not found a resolution to this issue. Every one that I see posting about this issue seems to have resolved it by making sure BT is off in Windows before loading Android. I have turned on Airplane mode in Windows and rebooted into Windows before trying to load Android but I still have the issue. I am sure I am likely just doing something wrong ... any help would be greatly appreciated.
I have attached my logs in case it helps.
Everyone that has had this issue has resolved it by having BT off.
You said you were in airplane mode in WinMo, did a soft reset, boot back to WinMo (still in airplane mode) and then boot Android and you still have issues with BT?
I don't know how concerned you should be with BT at this stage, it's not really useful for headsets yet.
Edit - did you have Pandora running? I've heard that wreaks havoc on BT for some reason..
Seems you were -
Code:
I/ActivityManager( 1344): Start proc com.pandora.android for broadcast com.pandora.android/.api.bluetooth.AutoStartReceiver: pid=2097 uid=10057 gids={3003, 3002, 3001}
Last edited:
I should have caught that .... I remember reading that Pandora and BT don't get along. After uninstalling it BT worked! If I had tried a fresh build with no apps installed I would have caught it through simple troubleshooting. Sorry for wasting your time. I'll try to do more thorough troubleshooting next time. Thanks for you help.
Not concerned, just excited. I was/am considering trying jb's code to see what happens (yes I am a glutten for punishment). Sadly it sounds like fun to me. I don't remember where I saw it but I think I remember reading in the last week or so that the the changes needed to be compiled into the latest kernel as well as adding the audio libraries to the userland. Too much to learn and fun to be had but so little time
I should have caught that .... I remember reading that Pandora and BT don't get along. After uninstalling it BT worked! If I had tried a fresh build with no apps installed I would have caught it through simple troubleshooting. Sorry for wasting your time. I'll try to do more thorough troubleshooting next time. Thanks for you help.
Not concerned, just excited. I was/am considering trying jb's code to see what happens (yes I am a glutten for punishment). Sadly it sounds like fun to me. I don't remember where I saw it but I think I remember reading in the last week or so that the the changes needed to be compiled into the latest kernel as well as adding the audio libraries to the userland. Too much to learn and fun to be had but so little time
I posted this a few pages back to get the in-call routing working for BT... I'm trying the new test Kernel arrrghhh through out in the forum to see if that changes anything... I think things are getting close to a fully functional BT though...
# 490
Good Luck!
Hi Arrrghhh
So do I make 2 x FAT32 partitions ? And if so, what size should I make the root one ? And do I need to do anything in particular in relation to having data on it's own separate partition ? Is there another posting covering this ?
C
It's not a supported configuration on XDAndroid. You can by all means do it, the rootfs will work with dedicated partitions (ironically Neopeek chose a different partition layout...) but there's no official support for it if you will.
It would be 1 FAT32 and 3 ext2 partitions. By different layout I mean:
p1 - FAT32
p2 - ext2 (rootfs, not required)
p3 - ext2 (system, at least 120mb)
p4 - ext2 (data, at least 256mb to match default...)
Neopeek's CWM uses a cache partition for p4...
I've been using Droid Explorer to copy files to and from my SD Card while in XDAndroid. Works really well and saves from having to make partitions.
Link
I have...
...working bluetoth working right out the gate
i will now apply the wifi nv trick to see if i can get wifi working, but I'm happy that i don't have to do any adding to the bluetoth as it is working perfect
i just checked th up time on my wife's htc pure and saw an amazing 53 hours straight, no restarts or anything like that
BTW, on my wife's htc pure everything worked right out of the gate
there are some stuff i still haven't tried but will keep checking and report back
...working bluetoth working right out the gate
i will now apply the wifi nv trick to see if i can get wifi working, but I'm happy that i don't have to do any adding to the bluetoth as it is working perfect
i just checked th up time on my wife's htc pure and saw an amazing 53 hours straight, no restarts or anything like that
BTW, on my wife's htc pure everything worked right out of the gate
there are some stuff i still haven't tried but will keep checking and report back
Now it works, thanks
FRX07 is a bit faster , more usable.
I too can confirm that using latest rootfs, wifi works and connects faster than before. thank-s alot everybody
if only somebody would work on getting pandora to work without killing my bluetooth, this would be a daily user for me
Last edited:
Hmm go to the root of your files... then to Data. Their you can find a file called wifi-nvram.txt
Open that file as text... on the first commandline with me it said ___fid (___ as in space). but it had to be manfid....
So i deleted the space and replaced it for manfid
That worked for me
it gives me error
"failed to find rootfs on sd card. you need to unzip a rootfs file to the root of your sd card
can not access tty job control turned off."
anybody got suggestion ?
"failed to find rootfs on sd card. you need to unzip a rootfs file to the root of your sd card
can not access tty job control turned off."
anybody got suggestion ?
Last edited:
One of two things is wrong.
1) You don't have a rootfs.img where you run HaRET.exe from.
2) You put everything in a folder, but didn't adjust rel_path= in your startup.txt. The default startups assume everything is extracted to the root of the SD card - haret, zImage, rootfs, etc not in a folder. If you want them in a folder, say FRX07, then rel_path=FRX07. This is in the first post...
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
65FRX07.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.14Layman'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. 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
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.11Caveats:
- 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 .
