OK.. First. After running this on my Pure, I could kick myself for not getting an android phone to begin with!
Now, my questions and queries..
1. Is there any version 2.1, 2.2 ..etc that has sound (external speaker, screen taps, music etc) working?
2. I played with 2.1 startups and etc and got everything to work essentially but the external sound. After I tried the latest 2.2 and rc1, which would hang on calls (only time I got it to load completely), I went back to 2.1, which hangs on calls now. So, my question is, is there a recommended setup for 2.1 on a Pure TOPA210?
3. The release notes say for rc1 the sound issues are fixed. I try to run it, and it freezes on creating data.img. There is a post describing using the image from 2.1, but that makes "panic", and none of the fixes in that post seem to work. So question is, any recommendations on setup for 2.2 on Pure TOPA210?
Really awesome thing y'all are doing here, BTW.
smoakeater said:
OK.. First. After running this on my Pure, I could kick myself for not getting an android phone to begin with!
Now, my questions and queries..
1. Is there any version 2.1, 2.2 ..etc that has sound (external speaker, screen taps, music etc) working?
2. I played with 2.1 startups and etc and got everything to work essentially but the external sound. After I tried the latest 2.2 and rc1, which would hang on calls (only time I got it to load completely), I went back to 2.1, which hangs on calls now. So, my question is, is there a recommended setup for 2.1 on a Pure TOPA210?
3. The release notes say for rc1 the sound issues are fixed. I try to run it, and it freezes on creating data.img. There is a post describing using the image from 2.1, but that makes "panic", and none of the fixes in that post seem to work. So question is, any recommendations on setup for 2.2 on Pure TOPA210?
Really awesome thing y'all are doing here, BTW.
Click to expand...
Click to collapse
There are no noobish questions, only stupid answers .
1. There is no build yet with the external sound working ( known and common problem on TP2 and TD2 ).
2. I would recommend to use the 2.2 Froyo build because the 2.1 is no longer under development, we are focusing now ( devs i mean ) to Froyo build mainly now.
3. From Froyo beta v2 till RC1 we had some problems running the build ( kernel panics ), but all was fixed with a new zImage ( 20/07 zImage i think ) anyway head over to the general thread here and go back 1-2 pages back and you will see which one fixes that.
Thanks! The newer zimage and such got it going! I cam use the data connection, but still hangs on calls with the latest, so will try the image from 7-20 and see how that works.. Thanks for the help!
I guess I'm a bigger noob! I'm having trouble locating a froyo build that works on my HTC PURE (topa210).
What builds / sources are you using?
nitronikon said:
I guess I'm a bigger noob! I'm having trouble locating a froyo build that works on my HTC PURE (topa210).
What builds / sources are you using?
Click to expand...
Click to collapse
I am using the newest package and the 7-29 silage package and works great on my pure
Sent from my MSM using XDA App
QUESTION TIME:
if we are using xdandroid on on our td2's does that make it by default rooted???
and do we have cyanogen mod or not???
Trekfan422991 said:
QUESTION TIME:
if we are using xdandroid on on our td2's does that make it by default rooted???
and do we have cyanogen mod or not???
Click to expand...
Click to collapse
Answer time :
Yes, XDAndroid is by default rooted.
Yeah we have CyanogenMod for our device, head over here for more details.
cool thanks.. one more...
will any android rom work on our device or just specialy cooked ones for the td2 (pure)
Trekfan422991 said:
cool thanks.. one more...
will any android rom work on our device or just specialy cooked ones for the td2 (pure)
Click to expand...
Click to collapse
Some of the chefs modifies the kernel,... for their devices ( but they are very rare ). You can use the "roms" from devices listed in my signature under the XDAndroid logo. But i think in near future the Android "roms" for TD2 will start poping up.
Where can the "silage package" be found?
Thanks!
is it true that the random app launching is a an issue on all android phones and that google can gemotely do anything that they want to to the device???
im really hating the ads and the random app launching!!!!
Related
Hello all,
I am new to this site and new to the custom ROM rooting, I not the biggest fan of android 2.1 so I looking for a new ROM, does anyone have any suggestion's on ROM's I could use for my phone and the directions, since I being new I have no idea how to root. I have the Sprint CDMA Hero, Thanks in advance and sorry for being a newbie
My favorite 1.5 rom was Fresh 1.1 accompanied by the gumbo kernel.
You'll have to do a little searching to find it though, pretty much everything has been built on 2.1 for the last few months.
Ya I notice most newer ROM's are based off 2.1 which is fine with me, I just not a fan of the andriod 2.1 update, lots of apps just run randomly, and horrible call and dial lag
Jmoney24 said:
Ya I notice most newer ROM's are based off 2.1 which is fine with me, I just not a fan of the andriod 2.1 update, lots of apps just run randomly, and horrible call and dial lag
Click to expand...
Click to collapse
Not a fan of Android 2.1? Or Sense 2.1? I'd go try darchdroid before going back to anything 1.5
+1 for DarchDroid.
Check the Stickies or the Wiki. Everything you need to Root and flash ROM's is in those.
Hello all,
I'd like to ask which is the best distribution of Android for Kaiser - I mean everything working fine and so on.
I have HardSPL 3.29 and Radio 1.70.19.09 .. I tried one distro (Froyo 2.2 - Incubus26Jc's Super FroYo RLS14 All Languages) but when I started it.. it runs some time then the screen goes dark like sleep.. but when I press the power the screen image is broken... like white lines on the screen.. (this happens on both Incubus Super FroYo and Myn's Donut) ... I don't know is there some additional software that should be installed...
I use starting with HaReT via SD card...
I appreciate any help... Thanks in advance!
Best Regards,
Dimitar Dimitrov
The screen problem is wrong panel type, edit the default.txt in andboot folder, change the panel type, (board-htckaiser.panel_type=X), it can be either 1,2 or 3, if the display looks fine apart from sleep issues when you press power key, chances are you have a panel type 3, panel types 2 and 3 display the same, but have sleep issues if you choose the wrong one.
As for the best build? That is something you have to find out for yourself, not being funny, just that everyone has a different idea of 'best'
Thanks a lot!
Okay about the distribution... As I am new to Android at all... Can you please tell me your opinion about which distribution is working on kaiser (probably one you have tested and you are happy with it)
Thanks once again!
Kind regards!
Depends on what you want.
If you want speed, go with Myn's Warm Donut.
If you want to more apps, and less speed, go with Eclair.
If you want the latest apps and even less speed, try Froyo.
Thank you I'll try which one is working well on my kaiser and i'll choose one.. sorry for stupid questions anyway just i think it is better to ask someone who passed by those kinds of issues
MykoB said:
Okay about the distribution... As I am new to Android at all... Can you please tell me your opinion about which distribution is working on kaiser (probably one you have tested and you are happy with it)
Click to expand...
Click to collapse
I think I have tried all of them, and only 1 is working fine and fast for me: dzo's froyo (currently 26-08-2010). http://forum.xda-developers.com/showthread.php?t=715402 (get it here: http://sourceforge.net/projects/androidhtc/files/ ) (the latest builds include all of the fixes, you don't need to patch anything after installing).
I am running it with haret on the SDcard. It's so fast and smooth I don't even feel the need to flash it to the nand (which would work even faster).
The eclair builds, (polymod 2.1d, etc...) even with compcache enabled they are too slow. Cyanogenmod is also extremely slow, and it was also freezing while the phone was sleeping). And the Donut builds are lacking features.
On my kaiser the dzo froyo build is at least as fast as the fastest donut builds I have used, and it's rock stable. Far better than the eclair and other froyo builds like cyanogenmod.
PS: do not use any "unodexed" or "deodexed" builds. They are slower.
nemuro said:
Depends on what you want.
If you want speed, go with Myn's Warm Donut.
If you want to more apps, and less speed, go with Eclair.
If you want the latest apps and even less speed, try Froyo.
Click to expand...
Click to collapse
If you want the latest apps and the best speed and the best stability, try dzo's froyo.
On my kaiser this build feels like it came flashed originally instead of windows mobile. In comparison, the other builds felt like "hacks": slow and/or buggy.
Myn's RLS5 is the best for my kaiser.
And what about battery life?, Cyanogen literaly drain power in a few hours, froyo from dzo is better, but still is a problem for these builds.
Any recommendation?, the old Donut build battery lafe is the best (at least for me) but after several days the phone signal drops to zero, and i cant recover it !!
Please, your comments, thanks in advance!
yap i have same problem with phone signal. i wonder why...
Had this problem with a number of builds, turns out that using the 1.71 radio was the problem, reflashing 1.65 radio cured my 'No Signal' problems, sometimes latest is not always best
zenity said:
Had this problem with a number of builds, turns out that using the 1.71 radio was the problem, reflashing 1.65 radio cured my 'No Signal' problems, sometimes latest is not always best
Click to expand...
Click to collapse
I will try this, is terrific news !! at leas for me, haha.
Thank you !!
Regards
BigMango said:
If you want the latest apps and the best speed and the best stability, try dzo's froyo.
On my kaiser this build feels like it came flashed originally instead of windows mobile. In comparison, the other builds felt like "hacks": slow and/or buggy.
Click to expand...
Click to collapse
I downloaded the latest system-WHATEVER for dzo's froyo...on my hd2 you unzip a zip...extract Android dir to SD card and run haret to start android....where exactly is haret and the other things to actually boot the system? It's not in the .tgz's being posted in that sourceforge dir.
zenity said:
Had this problem with a number of builds, turns out that using the 1.71 radio was the problem, reflashing 1.65 radio cured my 'No Signal' problems, sometimes latest is not always best
Click to expand...
Click to collapse
good new, but unfortunatly is not the only problem...did you solved battery draind issue? if yes let me know pls
BigMango said:
If you want the latest apps and the best speed and the best stability, try dzo's froyo.
On my kaiser this build feels like it came flashed originally instead of windows mobile. In comparison, the other builds felt like "hacks": slow and/or buggy.
Click to expand...
Click to collapse
This has been my experience too. I tried several of each of the donut/eclair/froyo builds but the lastest kernel along with dzo's fresh froyo have made a world of difference. Way faster than even the donut builds that had previously been the faster of all of them.
famewolf said:
I downloaded the latest system-WHATEVER for dzo's froyo...on my hd2 you unzip a zip...extract Android dir to SD card and run haret to start android....where exactly is haret and the other things to actually boot the system? It's not in the .tgz's being posted in that sourceforge dir.
Click to expand...
Click to collapse
HaRET is a separate tool, you can get it here.
2011 Builds
Hi
I see that no new builds are posted and for all the latest downloads are from 2010.
I tried using aTools and also downloaded new Froyo from SourceForge.net, but no luck - Android hangs. What other files should be updated to for all to work?
I understand, that aTools ia a mgnificent tool, and everybody can "cook" his own version at home, but it is not totally clear regarding what should be used as basefiles, or if you download a distribution (like i did system-froyo-all-odex-29-08-11_19-patched.tgz) will it properly work, or what should be done to work.
Any advices?
I just erased my CyonogenMod because was a bit slow and as i read, DZO froyo should do it.
Creating the defaul.txt is not a problem. My concern is the zimage, the initrd and the androidinstall to work together properly.
Cheers
---------- Post added at 04:25 PM ---------- Previous post was at 03:31 PM ----------
OK? solved: i had to swith aTools to use a Stable branch and downloaded another initrd. Now all went smooth, and i have latest android on my Kaiser - working fast.
No FileManager, but WiFi works, so as Market, so just download
As a last step, i created with atools an androidupdate file to change my keyboard settings.
That's it.
Astro was not showing up in Market so i went here and downloaded the apps / widgets as a standalone update: forum.smartphonejunkie.com/windows-mobile-apps/202417-dzos-fresh-froyo-2-2-odexed-vanilla-rls6-7-2-10-a.html
I have a single problem now: market does not show all the apps. I search for something, gives me 411 results, but shows only 2 apps. Why is that?
How can market be fixed?
7th September 2010, 01:58 AM
Click to expand...
Click to collapse
This thread is a YEAR old. Of course there are newer roms after that date
I know there are newer roms, but had not been posted. But no problem, i found what i wanted, and i installed Android. Fixed market also.
I have another problem, and maybe i can reformulate the topic's title:
Which Android build is best for Kaiser's battery life?
I mean, the newest froyo drained my battery in one night. Windows Mobile last 3-4 days - depending on the use.
Tough question?
Hey guyz, im new to android world so id like to introduce myself shreddd ... im a software developper so as soon as i get confortable with android i will be developpin some apps . (android sdk is already installed on my eclipse hehe)
Alright so there is my situation.
I have a captivate i896 just rooted it the hard way. Ive search the forum a bit and im going to put cog froyo on my phone. My question is : Ive read about lag fixes specially voodoo lag fixes wich seems efficient and i was wondering if i should install that lag fix before or after flashing to froyo 2.0 ?
Since froyo rom could overwrite everything it could be useless to install the fix before , but since this fix it format the sdcard it could be usefull... anyway you tell me hehe
If I am not mistaken the latest cognition has voodoo built in, it will install automatically.
yessir you put cog on your phone VooDoo is not only initiated but also it will be rooted happy flashing!!
Sent w/cog v2.4 using smoke signals
Please don't post this in Development.
Sent from my Captivate.
On some roms especially i9000 based you have the option between like 5 or 6 lag fixes
Sent from my SAMSUNG-SGH-I897 using XDA App
So, I see that there is a 2.1 update for the HTC Hero CDMA from Sprint and I'm very interested in upgrading to be able to use some of the better software out there that doesn't work on 1.5.
The thing is, I finally managed to fix this phone from a bad rooting procedure (it's a used phone, the previous owner rooted it using who-knows-what method and ROM, which caused the wifi to stop working) after spending weeks on the problem and finally have a good, fully-functional phone. So, now, I'm a bit paranoid about any rooting or upgrade procedure, though I suspect and official update from a Sprint shouldn't cause a problem.
I'm also considering doing a basic rooting (no custom ROM) so I can boot into ClockworkMod Recovery and make a complete backup, but, again, I'm very leery about it.
Is there any possibility that rooting, in and of itself, could cause the wifi to stop working or was it that the specific ROM that was installed didn't have the right wifi driver?
epp_b said:
So, I see that there is a 2.1 update for the HTC Hero CDMA from Sprint and I'm very interested in upgrading to be able to use some of the better software out there that doesn't work on 1.5.
The thing is, I finally managed to fix this phone from a bad rooting procedure (it's a used phone, the previous owner rooted it using who-knows-what method and ROM, which caused the wifi to stop working) after spending weeks on the problem and finally have a good, fully-functional phone. So, now, I'm a bit paranoid about any rooting or upgrade procedure, though I suspect and official update from a Sprint shouldn't cause a problem.
I'm also considering doing a basic rooting (no custom ROM) so I can boot into ClockworkMod Recovery and make a complete backup, but, again, I'm very leery about it.
Is there any possibility that rooting, in and of itself, could cause the wifi to stop working or was it that the specific ROM that was installed didn't have the right wifi driver?
Click to expand...
Click to collapse
Dude there are literally thousands of people running custom roms flawlessly ....taking that in to consideration, what do you think the answer to your question is? Lol for liability purposes we all have to say "there's a risk" but my 11 year old sister rooted her evo and flashed cm7 without any help
Sent from my HERO200 using XDA App
Fair enough, the custom ROM that was used must have been a crappy one.
epp_b said:
Fair enough, the custom ROM that was used must have been a crappy one.
Click to expand...
Click to collapse
Well we've had some that had broken wifi long ago but really you probably just could've flashed a new working kernel over it and the problem would be gone. If you wanna stay stock-ish I'd recommend fresh 2.1 but if you wanna really see it fly flash kush-deck gb. Flash the. 29 kernel after you boot and you will never regret it
Sent from my HERO200 using XDA App
Thanks, I'll check those out sometime. Have you got links for them?
Believe me, you don't want the stock Sprint 2.1 on your Hero. It's terrible. Super slow and it freezes constantly. I ran it for a short time after Sprint released it and that's when I decided to root. If I remember correctly you also can't put your apps on the SD card with it which really limits how many apps you can install.
I am running CyanogenMod 6.0 Froyo with ADW Launcher (built into the Rom) and its snappy and reliable but still has a lot of the bells and whistles. Try Beautiful Widgets and you can have a homescreen clock with animated weather just like the HTC Sense homescreen.
I tried CM 6.1.1 recently (updated froyo with new features) but it used more internal memory than 6.0 which made my phone laggy.
Be sure to get the appropriate Google apps zip file with the new Market
Sent from my HTC Hero running CM6 RC1 with the XDA app
what's 2.1?
Android Eclair. 2.2 is Froyo
Sent from my HTC Hero running CM6 RC1 with the XDA app
I managed to find some of the software I was looking for and I'm actually pretty happy to run 1.5; I actually find it quite usable.
Which ROM is better?
I don't know for sure, but it seems that samuaz's is texasice's build plus the CM goodies. So I would say samuaz's has more features.
bassmadrigal said:
I don't know for sure, but it seems that samuaz's is texasice's build plus the CM goodies. So I would say samuaz's has more features.
Click to expand...
Click to collapse
Ok. Hey, aren't you that Cyanogenmod moderator?
That'd be me
why ask--try them both--
Am using texasice's ROM since like day 1 and loving it. Its my daily driver
I tried thrice to use texacise ROM [Alpha 8, ev-1, and latest p3]. There are huge improvements and p3 is quite close to be used as daily rom. However, still there are issues with network dropping off , random soft reboots and many Apps FCing.
Nexy has good future with both these ROMs progressing so fast [it is less than 50 days since google released the code].
The samuaz ROM, looking at the feedback, I'll give it a try for couple of days next week.
Yes I do notice those soft reboots with p3. But no FCs and no network drops. However the progress for each build looks quite promising.
Would be nice if Samuaz too release a mini skirt version for stock Hboot
Yet another reason not to stay on stock Hboot: Camera is already working (not completely) on N1.
Also msm kernel 3.0 is ready. Just a few days before we get ICS beta
Where can we get the msm 3.0 kernel?
JoshX said:
Where can we get the msm 3.0 kernel?
Click to expand...
Click to collapse
Where? From a kernel dev, of course.
When? When it's ready. Further questions will not aid in getting it faster.
I heard the kernel dev over at the Desire forums is going to upload his msm-3.0 sources to guthub and will make it work on the HD2 and Nexus One, of course after it works on the Desire itself.
Just wait patiently and it will be here sooner or later.
Which rom work on 2g network?
Mohamad_j said:
Which rom work on 2g network?
Click to expand...
Click to collapse
I think texasice's ROM works with 2G network.
Theshawty said:
Where? From a kernel dev, of course.
When? When it's ready. Further questions will not aid in getting it faster.
I heard the kernel dev over at the Desire forums is going to upload his msm-3.0 sources to guthub and will make it work on the HD2 and Nexus One, of course after it works on the Desire itself.
Just wait patiently and it will be here sooner or later.
Click to expand...
Click to collapse
That's what I figured, but it seemed to be implied, by indiangeek, that one was already available.
I just upgraded from CM 7 to Texas ICS p4. The market didn't work (my apps didn't auto-sync and re-download - couldn't get it working after an hour of trying), the animations were a little jerky, camera didn't work, USB mass storage didn't work, CM mods weren't there. In it's current form, it could use a little polishing.
I tried Samuaz's MeDroid ICS 4.1 and it works way better. No market issues. Animations are much more fluid, camera works (panorama and video are broken). Gallery doesn't pull in picasa web albums (that'll be fixed today in 4.2). Also, you get CM features, which aren't present in TICS. I got a few force closes, but I think that was due to not rebooting after restoring from mybackup root, as I haven't had the FCs in a while. Oh, and USB mass storage is working, so I can restore apps and data from my backups. Sometimes the USB icon shows up or the app starts up (like at startup) when nothing is plugged in. Minor issue, though.
Upgrade method (some of these flash files aren't signed, so I needed to disable signature verification before they'd flash):
Upgrade bootloader (HBOOT) to 0.35.0017
Flash latest radio (5.12.00.08) - CHECK THE MD5 BEFORE FLASHING
Install Blackrose using the automatic method (It will not work without the HBOOT above)
Install custom blackrose from http://forum.xda-developers.com/showthread.php?t=1366897 - this increases the space available for ICS to install
Use recovery to do a full wipe three times (people had issues only wiping once)
Mount SD card via recovery and deleted/backed up everything.
Flash Evervolv-Perdo-2.1.0p4-passion.zip from http://forum.xda-developers.com/showthread.php?t=1366897
(Realize a bunch of things weren't working)
Use recovery to do a full wipe three times (people had issues only wiping once)
Flash MeDroid 4.1 from http://forum.xda-developers.com/showpost.php?p=21093710&postcount=188
To do yet:
Upgrade as soon as 4.2 comes out to fix gallery - I'll probably just use adb to replace the current gallery app - http://forum.xda-developers.com/showpost.php?p=21097768&postcount=191
Replace MeDroid's boot animation with this one http://forum.xda-developers.com/showthread.php?t=1429308
Am I the only one to be a little knee-shaking when it comes to flashing radios? I mean, ****ing up the system or boot seems easily restorable, but flashing a corrupted or unsigned radio may turn your device into a fully usable paperweight?
That's kinda the reason I've stayed with the 5.08.00.04 or what it's called. I mean, it works for me and hasn't bugged in any way, so why upgrade it?
I agree it's scary, but I saw so many people using the same file without issues, I was alright with it. Radios are the only file I check md5 on for this reason.
I think you're ok if fastbooting the img and like loki980 said, checking md5
I've done it a few times with no issues
Theshawty said:
That's kinda the reason I've stayed with the 5.08.00.04 or what it's called. I mean, it works for me and hasn't bugged in any way, so why upgrade it?
Click to expand...
Click to collapse
In all my time in the CyanogenMod forum (which is probably waaay too much time), it seems that the 5.08 is the best supported radio with the N1. I have never seen issues fixed from going from the 5.08 to the 5.12, but I have seen quite a few fixed doing the reverse. A lot of people get great results with 5.12, but it seems that more have better luck with 5.08.
Plus, I am sure that Google did a lot of testing before they sent out the Gingerbread update, and I'd bet there is a reason they included the 5.08 instead of the 5.12.