This is Froyo Sense coming to Vogue...
Calling does not work!!
The latest kernel 240x320 works the best.
It runs about as fast as Super Hero with no Overclocking when WildVogue is oc'ed to 520 mhz with Rogue tools
It runs from a system.img but i am working to strip it down to NAND
Data should be put on NAND
I have no clue if this will work on Polaris or Kaiser(It'd be helpful if someone could try...)
here are some preliminary screenshots(attached).
This preliminary(Beta) build:
Thanks vellowax for all the help
Thanks Thoughtlesskyle for your kind suggestions
And the whole community for all the previous work that helped me get here.
Its a port from WildPuzzle v8 for Wildfire
the androidinstall.tar is here
I'm looking for help learning and developing it but I'm coming along
This is a Beta I have no responsibility whatsoever if you brick your phone
If you have any suggestions please reply in this thread
Lovely!
jholtom said:
This is Froyo Sense coming to Vogue...
Calling does not work!!
...
I'm looking for help learning and developing it but I'm coming along
This is a Beta I have no responsibility whatsoever if you brick your phone
If you have any suggestions please reply in this thread
Click to expand...
Click to collapse
I will try this when calling works but keep your progress--make it mature!
Your download link doesn't work
I figured it out, but you might want to edit it and correct it.
I'll do some testing with this as I have a spare phone that's not activated.
jholtom said:
I have no clue if this will work on Polaris or Kaiser(It'd be helpful if someone could try...)
Click to expand...
Click to collapse
Excellent Jholtom, I've linked this thread in Kaiser forums, If noone will be brave enough to try it out I will test it in the afternoon. Great job!
link is doesnt work if i download this ill try yhe kaiser but icant download this link
The link is fixed now
can not install kaiser because low memory on nand
What Kernel are you using for this jholtom ?
I tried using the 11/29/10 2.6.32 kernel and was getting an error message.
I'll try again with the 10/29/10 2.6.32 kernel
Will give this a try.
I have it installed on the kaiser. It took a little work but its on. It will only work in 320x240 and with at least 200 mb for sys and then use an ext2.img for data. One problem I am having though is that all the HTC setup apps fc. I am going to try just removing them and see how that works. I used an old october kernel as I tried to update to the 11/29 one and was getting a module error and did try the android update and it didnt solve it so I rolled back.
trashed my super froyo so i guess ill give this a try........
great jobs,i'll give it a try
I managed to actually get into the rom finally. I took a setupwizard from a froyo rom and used it. I had to really fight with it though. The wizard ran poorly, and the date and time settings at the end kept fc'ing looping it back to the beginning of the wizard until finally it went into the rom. Going to test it now. I do not believe its a phone issue but a build issue as of right now. If you could remove the date and time settings it is referring to then I think it might be a bit better.
To run on the kaiser so far i've had to:
Set resolution to 320x240, Change partition to be 200 MB on SYS and rest on DATA via ext2.img . Afterwards I took a setupwizard.apk from a froyo rom and then renamed and replaced the HTCSetupWizard.apk the rom included as that was contributing to FC's.
On the kaiser wifi and the radio are not working. Both get an error when attempting to be used. I am going to try bringing in a etc folder from a working froyo rom and see if that solves the issue.
Lastly there is a power issue on the kaiser. It seems to keep thinking its almost near dead while on usb even though in the kernel it shows the proper power levels.
OK...
Tried this on my Vogue
the 10-31-10 2.6.25 NBH kernel will work.
BUT!!!
Do NOT try this on a class 2 card - OMFG... WAY too slow
Class 4 or class 6 at least...
Hopefully you can fit it in NAND soon?
aceoyame said:
I managed to actually get into the rom finally. I took a setupwizard from a froyo rom and used it. I had to really fight with it though. The wizard ran poorly, and the date and time settings at the end kept fc'ing looping it back to the beginning of the wizard until finally it went into the rom. Going to test it now. I do not believe its a phone issue but a build issue as of right now. If you could remove the date and time settings it is referring to then I think it might be a bit better.
To run on the kaiser so far i've had to:
Set resolution to 320x240, Change partition to be 200 MB on SYS and rest on DATA via ext2.img . Afterwards I took a setupwizard.apk from a froyo rom and then renamed and replaced the HTCSetupWizard.apk the rom included as that was contributing to FC's.
On the kaiser wifi and the radio are not working. Both get an error when attempting to be used. I am going to try bringing in a etc folder from a working froyo rom and see if that solves the issue.
Lastly there is a power issue on the kaiser. It seems to keep thinking its almost near dead while on usb even though in the kernel it shows the proper power levels.
Click to expand...
Click to collapse
@aceoyame
you are on a kaiser right?
Everything works fine on my vogue running 240x320 2.6.32-froyo-09/10/21 kernel
I get through the setup wizard fine and it runs pretty darn fast for sense when overclocked to 545 with Rogue tools
Wifi and radio have not been repaired yet from froyo i'm working on
Remember this is a Beta build
Does_It_Matter said:
OK...
Tried this on my Vogue
the 10-31-10 2.6.25 NBH kernel will work.
BUT!!!
Do NOT try this on a class 2 card - OMFG... WAY too slow
Class 4 or class 6 at least...
Hopefully you can fit it in NAND soon?
Click to expand...
Click to collapse
@Does_it_Matter
What device are you on?
I would try the 240x320 2.6.32 froyo 09/10/21 kernel for vogue(if thats what you have)
I dont know for kaiser of polaris
The build itself is a decent speed but the problem is, your not able to clock up with rogue tools until after you have everything set up. So default were at 400 mhz which is dirt slow. As for the kernel, I don't believe thats going to make a difference here. I did try to merge the etc folder with fresh froyo's and it made no difference. I thought maybe the missing wifi levels folder and a couple other things would help.
That means our problem is deeper somewhere else for those. Also, I would include rogue tools in the build itself to save some hassle downloading it at slow speeds.
fyi, i'm a kaiser developer. I know I never post on the vogue or polaris forums.
jholtom said:
@aceoyame
you are on a kaiser right?
Everything works fine on my vogue running 240x320 2.6.32-froyo-09/10/21 kernel
I get through the setup wizard fine and it runs pretty darn fast for sense when overclocked to 545 with Rogue tools
Wifi and radio have not been repaired yet from froyo i'm working on
Remember this is a Beta build
Click to expand...
Click to collapse
I am using L1qu1ds .32 kernel dated from 10/29/2010. It isn't a kernel issue that I am having but like I said, rogue tools cannot clock up the build until after installation.
aceoyame said:
I am using L1qu1ds .32 kernel dated from 10/29/2010. It isn't a kernel issue that I am having but like I said, rogue tools cannot clock up the build until after installation.
Click to expand...
Click to collapse
> /sys/module/clock_7x00/parameters/ahb_div
echo 500 > /sys/module/clock_7x00/parameters/a11
add that to the top of the userinit.sh to have it overclocked to 500mhz from the getgo. It will be overclocked throughout the boot process.
Thanks mssmison for the info.
incubus26jc said:
> /sys/module/clock_7x00/parameters/ahb_div
echo 500 > /sys/module/clock_7x00/parameters/a11
add that to the top of the userinit.sh to have it overclocked to 500mhz from the getgo. It will be overclocked throughout the boot process.
Thanks mssmison for the info.
Click to expand...
Click to collapse
Thats not the same as overclocking through atools right? I know that through a tools the kaiser gets unstable as all hell. For some reason it doesnt with rogue tools.
Related
So just how stable is 4.999?
I want to root my phone to it, but I've read that a lot of people have been having issues with it..
I would get the 4.04, but does it come with the new 1.6 tmobile update?
xologist said:
So just how stable is 4.999?
Click to expand...
Click to collapse
You mean 4.1.999?
xologist said:
I want to root my phone to it, but I've read that a lot of people have been having issues with it..
Click to expand...
Click to collapse
I don't have any issues. An occasional forceclose/wait popup message and rarely a random reboot. Plus gps doesn't work too well with some map apps (especially Telenav) but I think that's app related and not to the rom. (Some apps need to be revised for 1.6.)
In any case as long as you have a recovery that allows you to do nandroid backups (you can use the RA-dream which is linked in my signature. It allows you to do switchrom so you can bookmark your current rom.)
So try 4.1.999 and if you don't like it, flash back and wait for a newer and more stable release.
xologist said:
I would get the 4.04, but does it come with the new 1.6 tmobile update?
Click to expand...
Click to collapse
No. 4.0.4 is Android 1.5.
i have been running 4.1.999 since it came out, about a week or so ago, and it can be a little slow at times, but a reboot will fix that (basically i reboot when i wake up in the morning, and it runs fine throughout the day for me). i think the reason mine slows down though is i have a 64mb linux-swap partition, and i have my swappiness set to 75.
overall though, i find it to be a great ROM, and no 4.0.4 is not based off of 1.6, it is 1.5.
oh cool, so 4.1.999 is based on 1.6 ?
and im kind of glad you guys say you dont have issues, because everytime I look here there is more issues :S
http://code.google.com/p/cyanogenmo...Priority Version Owner Summary Stars Modified
Flash it and try balancing it on a flat surface, you can tell how stable it is.
ok cool thnx
I dont use swap, just ext3, and Advanced Launcher, 4 App Limit Set, and mine runs smoothly....
Kazan22 said:
Flash it and try balancing it on a flat surface, you can tell how stable it is.
Click to expand...
Click to collapse
hmmm, this is going to be my new stability test when i try out a hero rom.
can it survive without falling over during the initial boot up?
http://forum.xda-developers.com/showthread.php?t=728797
Ion donut build based on Zenulators Ion Build http://ip208-100-42-21.static.xda-de...d.php?t=582810
Working
Everything
its a very fast build no fcs try it out and please give feedback thanks
hawks-SOAD said:
http://forum.xda-developers.com/showthread.php?t=728797
my Ion donut build
Working
Everything
its a very fast build no fcs try it out and please give feedback thanks
Click to expand...
Click to collapse
Ion seems pretty old, any reason in particular you are using ion, when everything works in donut, and most things in eclair or froyo?
EDIT: Err re read it ion donut :S, kinda threw me off
My rom is reborn...........................
http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=582810
If this is indeed zenulators work, you need to a. seek permission first to post. and then b. credit in the op.
I'm glad you continued this rom. Keep up the good work.
Sent from my HERO200 using XDA App
Well I'm not sure who to give the credit to, but I love this build so much it has become my daily driver.
Pair this up with the 7-2 .nbh and you've got a build where everything works and works snappily. (Is that a word?)
Kudos to all involved.
zenulator said:
I'm glad you continued this rom. Keep up the good work.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
was happy to the rom deserved it lol nut i cannot continue my kaiser died so until i get it fixed i can't do anything , i have moved on to the desire but my mum will be using the kaiser so i can test builds on it still
do you have a full market update?
otherwise i like this rom, thanks !
did you ever fix the camera?
camera works fine here?
jin5 said:
camera works fine here?
Click to expand...
Click to collapse
Camera works fine when paired with the 7-2 zimage/NBH file.
Mike
jin5 said:
do you have a full market update?
otherwise i like this rom, thanks !
Click to expand...
Click to collapse
I tried to bring in the market apk from Myn's Warm Donut, but since this is an Odex-ed build it didn't work. I may give it another try, though.
I've been using Incubus' Froyo for a while now, and was using Release 13
I backed up all my stuff and dumped my data to an img so I could always go back if necessary
Loaded up this RLS 3 of the HTC Ion build - wow... FAST
Nice ROM - good stability - everything works.
Upgraded to latest Google maps - its working no issues
Market seems to work fine, no issues
I also seem to get better signal on the phone with this Ion build than I did with Froyo
Any new updates planned on this?
Unless something really Astonishing or cool happens with a newer Foryo build,
I'm thinking that I'll be sticking with this HTC Ion build for the Vogue
Thanks to all the people that worked on this one!
Does_It_Matter said:
I've been using Incubus' Froyo for a while now, and was using Release 13
I backed up all my stuff and dumped my data to an img so I could always go back if necessary
Loaded up this RLS 3 of the HTC Ion build - wow... FAST
Nice ROM - good stability - everything works.
Click to expand...
Click to collapse
what nbh did you use if you don't mind me asking?
you're on the sprint vogue?
cheers!
cyburke said:
what nbh did you use if you don't mind me asking?
you're on the sprint vogue?
cheers!
Click to expand...
Click to collapse
Yes - Sprint network - HTC Vogue
http://it029000.massey.ac.nz/vogue/files/voguimg-320x480-02-07-10.nbh
is the image I downloaded and flashed
Either of these should work - depending on what resolution you want:
voguimg-320x480-02-07-10.nbh
voguimg-320x428-02-07-10.nbh
voguimg-240x320-02-07-10.nbh
I find the 320x480 to work quite well
Used Rogue Tools - set to 500mhz OC and also 160 DPI
this is a nice rom.. thanks to 'does_it_matter' i've been checking it out...
in froyo i was able to 1-second press the 'camera' button and it would act as the 'home' action and return you to home screen.
what is the 'home' screen button for this rom as that same action does not appear to work here...?
THANKS!
Does_It_Matter said:
I've been using Incubus' Froyo for a while now, and was using Release 13
I backed up all my stuff and dumped my data to an img so I could always go back if necessary
Loaded up this RLS 3 of the HTC Ion build - wow... FAST
Nice ROM - good stability - everything works.
Upgraded to latest Google maps - its working no issues
Market seems to work fine, no issues
I also seem to get better signal on the phone with this Ion build than I did with Froyo
Any new updates planned on this?
Unless something really Astonishing or cool happens with a newer Foryo build,
I'm thinking that I'll be sticking with this HTC Ion build for the Vogue
Thanks to all the people that worked on this one!
Click to expand...
Click to collapse
Can I ask how do you backup all your OS release? Can I do this if I am running haret with a partitioned card? ie: Backup all 3 partitions so I can reinstall easily?
Stupid pills here today, I can't figure out how to add more screens? I only got the 1 Home screen
NM, I just had to use my Pointer to swipe to screen
dsmturbo said:
Can I ask how do you backup all your OS release? Can I do this if I am running haret with a partitioned card? ie: Backup all 3 partitions so I can reinstall easily?
Click to expand...
Click to collapse
When you boot the phone, hold the center d-pad
Choose Backup data - and you can backup the data partition
it backs up to the Andboot folder and is 256MB in size so have the space available!
That way, I can just reload a Froyo Release, then re-load the data.img and I am back where I started!
I also backup all my contacts/sms to google
Does_It_Matter said:
I also backup all my contacts/sms to google
Click to expand...
Click to collapse
i got the backing up of contacts just fine to google, but how do you backup your SMS too?!
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?
So I've just recently flashed my vogue with myns donut for a couple days and It was pretty good. The camera worked but no video and neither did the gps. I understand that for verizon you have to follow a specific procudure to get that to work so that makes sense. I'm just curious to what android roms they are using for their vougue. I'm looking for one that has the most working features. Let me know what it is and how you had it set up.
For my Fresh Froyo although remember android no is 100% stable but Fresh Froyo is very good.
If you know what you want my barebones build is known to be one of the fastest and most stable builds. With that though you need to get the apk's to what you want and add them in. It is meant to be as cut down to the minimum to be light and lithe on our devices.
Another way to get apps is to use the market, I have the most recent version of the market in my build. CM 6.1 is Froyo based so you have video and all the other froyo features.
aceoyame said:
If you know what you want my barebones build is known to be one of the fastest and most stable builds. With that though you need to get the apk's to what you want and add them in. It is meant to be as cut down to the minimum to be light and lithe on our devices.
Another way to get apps is to use the market, I have the most recent version of the market in my build. CM 6.1 is Froyo based so you have video and all the other froyo features.
Click to expand...
Click to collapse
I tested more than 10 ROM including the yours and I am sorry to tell you than ever before me to worked well even the last released CM 6.1, does not work properly with the kernel that is in my signature and is the one that works best with the USB sync and just by this already this ruled out your ROM, so I'm still saying Fresh Froyo for me is the more stable and clean ROM of froyo that I tested.
Josue_181 said:
I tested more than 10 ROM including the yours and I am sorry to tell you than ever before me to worked well even the last released CM 6.1, does not work properly with the kernel that is in my signature and is the one that works best with the USB sync and just by this already this ruled out your ROM, so I'm still saying Fresh Froyo for me is the more stable and clean ROM of froyo that I tested.
Click to expand...
Click to collapse
Well mine is assuming you want to use the .32 kernel. Which with Clemsyn's kernel works very well. Battery life sucks though since the changes haven't been committed to git yet. But with that kernel I have not had any data loss since it came out.
Josue_181 ......Any chance you could post where you got the exact images/files etc. if it's not too much trouble. Thanks! I hope to run from haret if possible.
I have searched but it has been a while since I looked in this section. Is it DZO's Fresh Froyo you use and I cannot find Kernel: 2.6.25 10-31-10??? Hope you can help, thanks.
aceoyame said:
Well mine is assuming you want to use the .32 kernel. Which with Clemsyn's kernel works very well. Battery life sucks though since the changes haven't been committed to git yet. But with that kernel I have not had any data loss since it came out.
Click to expand...
Click to collapse
aceoyame,
How would it be possible to get the battery enhancements into the git? We need help!
aceoyame said:
Well mine is assuming you want to use the .32 kernel. Which with Clemsyn's kernel works very well. Battery life sucks though since the changes haven't been committed to git yet. But with that kernel I have not had any data loss since it came out.
Click to expand...
Click to collapse
Would have to prove with that kernel I know how to adapt the kernel Clemsyn's to our Vogue if it works I comment as I was to see if I change my mind about your ROM
krwilson said:
Josue_181 ......Any chance you could post where you got the exact images/files etc. if it's not too much trouble. Thanks! I hope to run from haret if possible.
Click to expand...
Click to collapse
The thread Fresh froyo this here, as well as guides for the installation of haret/nad, only is question search and read...
Prowess said:
aceoyame,
How would it be possible to get the battery enhancements into the git? We need help!
Click to expand...
Click to collapse
our vogue would not benefit from the battery enhancements since our kernels were designed for our battery
Okay so you say fresh froyo is one of the best? I looked it up but I am confused about what to download. Any advice would be great. I know how to install it I just dont know what file is the latest/best
loffyg said:
Okay so you say fresh froyo is one of the best? I looked it up but I am confused about what to download. Any advice would be great. I know how to install it I just dont know what file is the latest/best
Click to expand...
Click to collapse
This is my situation too....as I posted above. I know how to install, but am unsure of exactly what you are recommending as to the Fresh Froyo files. Thanks again.
Well try to be brief to that understand... (my English is very bad).
They must go to the thread of Fresh Froyo and go to this page, there download the ROM latest although I recommend the penultimate that is in my signature the most recent gave me problems.
The ROM download whith the name system-froyo-us-unodex-XX-XX-XX (X are date) have to rename it to androidinstall.tgz and copy in the ANDBOOT folder then locate the kernel of their choice here, the most recent is 2.6.32 although I recommend 2.6.25 which is in my signature if need USB mass storage in 2.6.32 doesn't work.
For the rest follow the installation guide in NAND is here and everything should go well.
Not be as it is done for HARET but here also the Guide to install in haret. I believe with what I said is more than enough so installed android in their device.
Best regards.
Josue_181 said:
Well try to be brief to that understand... (my English is very bad).
They must go to the thread of Fresh Froyo and go to this page, there download the ROM latest although I recommend the penultimate that is in my signature the most recent gave me problems.
ROM: Fresh Froyo 2010-12-03
Kernel: 2.6.25 10-31-10
The ROM download whith the name system-froyo-us-unodex-XX-XX-XX (X are date) have to rename it to androidinstall.tgz and copy in the ANDBOOT folder then locate the kernel of their choice here, the most recent is 2.6.32 although I recommend 2.6.25 which is in my signature if need USB mass storage in 2.6.32 doesn't work.
For the rest follow the installation guide in NAND is here and everything should go well.
Not be as it is done for HARET but here also the Guide to install in haret. I believe with what I said is more than enough so installed android in their device.
Best regards.
Click to expand...
Click to collapse
Okay I am pretty sure I understood what you said. I have the files you suggested thanks for the help I will try it tonight.
Josue_181 said:
the most recent is 2.6.32 although I recommend 2.6.25 which is in my signature if need USB mass storage in 2.6.32 doesn't work.
Click to expand...
Click to collapse
It works in Ubuntu Linux. It does not work for Windows 7, at least that I could configure successfully.
I'm using SuperFroyo and the 2.6.32.9 Kernel and a few things I noticed to make it more stable: don't use a Task Killer and be sparing in your use of a cache cleaner. Seriously, a week of doing that has really helped things. Trust the Linux Kernel, it's not Windows. I also used Autostarts to prevent a few of the more eager apps from starting automatically post-boot, but that's optional.
Prowess said:
aceoyame,
How would it be possible to get the battery enhancements into the git? We need help!
Click to expand...
Click to collapse
I cannot as I do not have Clemsyn's kernel so I cannot commit his fixes for stability to git. As far as the git kernel goes it already has those fixes.
Also with fresh froyo or any AOSP build you will not have as much speed since it does not have all the Cyanogen Mod tweaks.
So it loses a lot of those tweaks but I can say 1 thing about cm6.1 and 7 so far, they are getting rather large themselves, I can look into cm7 for hero and find atleast 10 apks that just take up space or are only good once
aceoyame said:
I cannot as I do not have Clemsyn's kernel so I cannot commit his fixes for stability to git. As far as the git kernel goes it already has those fixes.
Also with fresh froyo or any AOSP build you will not have as much speed since it does not have all the Cyanogen Mod tweaks.
Click to expand...
Click to collapse
Sent from my HTC Hero using XDA App
Yeah that is true, it's why I made a barebones.
goducks3620 said:
It works in Ubuntu Linux. It does not work for Windows 7, at least that I could configure successfully.
I'm using SuperFroyo and the 2.6.32.9 Kernel and a few things I noticed to make it more stable: don't use a Task Killer and be sparing in your use of a cache cleaner. Seriously, a week of doing that has really helped things. Trust the Linux Kernel, it's not Windows. I also used Autostarts to prevent a few of the more eager apps from starting automatically post-boot, but that's optional.
Click to expand...
Click to collapse
Does seem contradictory as to not use a task killer, the task killer close applications that are open and if you don't use are accumulating and this put slow the phone, the APP autostarts manager if I heard but none that worked well in my Vogue, which do you use?
aceoyame said:
I cannot as I do not have Clemsyn's kernel so I cannot commit his fixes for stability to git. As far as the git kernel goes it already has those fixes.
Also with fresh froyo or any AOSP build you will not have as much speed since it does not have all the Cyanogen Mod tweaks.
Click to expand...
Click to collapse
Using this kernel modified with atool I may obtained the benefits mentioned in the battery life?
aceoyame said:
Yeah that is true, it's why I made a barebones.
Click to expand...
Click to collapse
even with barebones, the cm settings along with the now statistic reporting and updater (which cause FC's if removed) are still pretty huge. i have grown to like cm7 on my hero but with having so much stuff commited to the project as much as i hate to say it, there is starting to be alot of ::gulp:: bloatware
Josue_181 said:
Does seem contradictory as to not use a task killer, the task killer close applications that are open and if you don't use are accumulating and this put slow the phone, the APP autostarts manager if I heard but none that worked well in my Vogue, which do you use?
Click to expand...
Click to collapse
You don't need a task killer. The newer versions of Android will shut down apps that aren't being used if the resources are needed elsewhere. If you run a Advanced Task Killer or something similar, it will use system resources shutting down apps that then re-open themselves, which the task killer will again kill. It drains the battery and makes the OS unstable. Uninstall your task killer for a few days and see if it helps.
I use Autostarts because it fixed a problem--the music player started randomly. I also use it to prevent some apps from starting up but it is probably not necessary.
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.