Bummer! You can try some of the tricks to get the Market/Play working, but they're hit-or-miss.
Your best bet is to try and find the APK standalone and see if you can install it. It very well might not work on our tired old hardware...
[BUILD] **Complete FroYo Bundle** FRX07.1 - Maintenance Release
- Thread starter arrrghhh
- Start date
-
- Tags
- htc touch pro2 xdandroid
Bummer! You can try some of the tricks to get the Market/Play working, but they're hit-or-miss.
Your best bet is to try and find the APK standalone and see if you can install it. It very well might not work on our tired old hardware...
ibm_chandan
Member
IS this Project still ALIVE !!??
Hello dear and respected developer and people involved in this project .
I just wanted to confirm , is this project still alive or dead and developers are only working on Gingerbread project for WinMO HTC Touch Pro 2/Rhodium ? Thanks
Hello dear and respected developer and people involved in this project .
I just wanted to confirm , is this project still alive or dead and developers are only working on Gingerbread project for WinMO HTC Touch Pro 2/Rhodium ? Thanks
All new development is happening on kernels at this point, with the exception of folks porting other builds to our phones (cm7, cm9, ICS, etc). Xdandroid itself has very little active development on froyo or gingerbread at this point.
NAND vs MicroSD?
Maybe a little bit off topic...but what is the advantages of NAND over SD card? Is NAND (I/O) much faster than a class 6 microSD card?
I am just a newbie here and it seems to me that flashing a NAND ROM is much more complicated than just simply download and unzip the files to an SD card. So I wonder whether it is worthy to spend a lot of time to read through all the posts, if there is no significant performance improvement after flashing the NAND ROM.
Or, put it in another way, what's the main differences (in speed/performance) between the NAND ROMs and MicroSD ones? Thanks
Maybe a little bit off topic...but what is the advantages of NAND over SD card? Is NAND (I/O) much faster than a class 6 microSD card?
I am just a newbie here and it seems to me that flashing a NAND ROM is much more complicated than just simply download and unzip the files to an SD card. So I wonder whether it is worthy to spend a lot of time to read through all the posts, if there is no significant performance improvement after flashing the NAND ROM.
Or, put it in another way, what's the main differences (in speed/performance) between the NAND ROMs and MicroSD ones? Thanks
NAND is a little faster for read access and quite a bit faster for booting up. Also, NAND makes USB Mass Storage work.
SD's main advantage is that it's easier to get started and doesn't carry much risk for the phone if something goes wrong.
Specifically for Rhodium XDA builds, the NAND kernel also has better battery management, but the SD kernel has support for auto backlight management.
SD's main advantage is that it's easier to get started and doesn't carry much risk for the phone if something goes wrong.
Specifically for Rhodium XDA builds, the NAND kernel also has better battery management, but the SD kernel has support for auto backlight management.
Device not connecting to wireless hotspot
Hi,
I don't know if anyone has asked this question before, searched through the thread couldn't find any response.
I'm using Connectify to share the internet on my PC. My device doesn't see it when it's WEP or open (I guess that's because it's adhoc,) but it sees it while it's secured by WPA2. While it sees the connection, it still doesn't connect, it stops at the obtaining IP address, disconnects and starts scanning again. It's been on the cycle since. Does anyone have an idea of what is to be done. I'm on a RHOD400.
Thanks
Hi,
I don't know if anyone has asked this question before, searched through the thread couldn't find any response.
I'm using Connectify to share the internet on my PC. My device doesn't see it when it's WEP or open (I guess that's because it's adhoc,) but it sees it while it's secured by WPA2. While it sees the connection, it still doesn't connect, it stops at the obtaining IP address, disconnects and starts scanning again. It's been on the cycle since. Does anyone have an idea of what is to be done. I'm on a RHOD400.
Thanks
FAQ first post of this thread.
http://xdandroid.com/wiki/Faq#How_do_I_connect_to_WiFi_networks_with_WEP_encryption.3F
I also suggest that you update to GBX0C.
Last edited:
Why not just use the built-in wifi tethering? Or are you doing it in the other direction...? Is your PC wired and you're trying to fudge a wifi hotspot...?
Most Android devices cannot connect to adhoc networks without wpa_supplicant hacks.
If people still want Froyo, more power to 'em... Just so long as they know there's pretty much 0 development on this build!
Yes, I am doing it the other way round PC => Android...
Anyway, I figured it out, I think. I simply changed the IP setting; so I'm using a static IP setting, it's connected now.
Thanks, Arrrghh! You've been most helpful on this forum.
---------- Post added at 07:30 AM ---------- Previous post was at 07:23 AM ----------
Thanks, I got it figured out.
About Gingerbread Bundle, the heading says testing. Is it out of test yet, my TP2 is my main phone and my office, I wouldn't want to mess with it, even though I don't mind testing.
thanks again
Sounds interesting. I tried that once and didn't get it working. Can you write up a quick how-to? It is off-topic for this thread but useful to me and probably others.
Sent from my Galaxy Nexus using XDA
Testing or not, it is more stable and performs better. I have no issues using it as a daily use rom.
I just went to Settings> Wireless & networks > Wi-Fi Settings > Advanced (by clicking Menu button) > Selected "Use static IP"
I changed the entries to suit what my PC wireless adapter is working with.
Anyways, I wasn't that smart at first, I had tried my hands on a few things before getting to the point of thinking about changing the settings. If you try this and you don't success at it, then it might be because I did what this guy directed here: http://xdaforums.com/showpost.php?p=19162859&postcount=55
Hope this helps.
---------- Post added at 11:15 PM ---------- Previous post was at 11:04 PM ----------
I guess I'm getting lazy at experimenting, must be sign of old age. lol! Thanks, man! I'll try it out as soon as this fever breaks
Last edited:
Okay so I have my start up configured on it, the keyboard layouts etc. but when I run HaRET.exe it give me the beautiful error: F:/ HaRET.exe is not a valid Win32 Application.
This has been bugging me all day and I'm about to give up, can someone help then? Running Win7 64bit btw.
This has been bugging me all day and I'm about to give up, can someone help then? Running Win7 64bit btw.
Are you trying to run HaRET on your computer...? You run it from your phone :good:
Oh lol... I must be an idiot. Sorry about that.
EDIT: Lol it booted and Nothing bad happened, until the point that it wont turn on WiFi
it just crashes
Last edited:
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 .
New posts
-
Hello friends, can you help me with the firmware of p30 pro vogL29
- Latest: Daniel2489
-
-
