Related
I've put up a new donut build for download based on the ADP1 recovery image signed-dream_devphone_userdebug-ota-14721.zip. It is not odexed and should be easier for people to theme.
It has the eclair dialer buttons, gmail from tattoo, latin ime and pinyin ime from the sdk, custom locale, dev tools, terminal, spare parts, calibrate screen, modem, and api demos from the sdk.
I removed music and will put up a modified version that works better with qvga. Until then you can download Meridian Player Evolve as a replacement or download the ADP recovery image and reinstall yourself.
I removed maps and youtube for those that want to install the ones from the eclair/sholes dump. I'll provide downloads for those as well as the standard maps and youtube.
For native qvga resolution set your default.txt to
Code:
mddi.width=240 mddi.height=320 lcd.density=120
Other resolutions also work with donut.
Use the latest basefiles, rootfs and zImage at vogue-android.
Compcache/Swap or renicer is not necessary for these builds. I have them turned off in my donut.user.conf
If you were previously using another build then rename your old data.img and let a new one be created.
I posted a small guide at vogue-android to get new users started. Read that before asking questions.
If you have problems please state what files your are using and what phone you are using.
This is tested using the latest files at vogue-android on a Verizon branded Vogue.
Download for system image: http://dl.dropbox.com/u/2888561/system-donut-110709r1.sqsh
Download for maps-youtube-voicesearch from ADP1 recovery image: http://dl.dropbox.com/u/2888561/maps-youtube-voicesearch.zip
Download for extra wallpapers: http://dl.dropbox.com/u/2888561/wallpaper-sholes.zip
zenulator said:
New thread for the CyanogenMod4.x Stable Vogue Port.
Direct Download
You can use all the same files you use to run Ion. You might want to let it create a fresh data.img. I haven't had time to test it with resolutions other than 320x480 so 320x428 might work. You should be able to use the new partial bluetooth functionality if you're using the latest files from vogue-android.
It's "based on Android 1.5r3 (crossbred with Donut)." Here is a link to the CyanogenMod Stable thread in the dream forums. It has a lot more information about whats included. Someone also started cyanogenmod.com so you can check that out too.
Click to expand...
Click to collapse
Does it need to run with the included initrd, rootfs and zImage, or can I just use the current ones?
pmos69 said:
Does it need to run with the included initrd, rootfs and zImage, or can I just use the current ones?
Click to expand...
Click to collapse
It runs with the same files as ion. So you can use the latest zImage and rootfs from vogue-android.
Nice port, but the camera doesn't seem to work for me, keep getting the force close.
Nice work
Nas
this build is alot more smoother than hero but not as pretty, eh i guess its one or the other. thanks zenulator
How do I get rid of the headset icon that's on the notifications bar?
I'm not using a headset.
jamezelle said:
this build is alot more smoother than hero but not as pretty, eh i guess its one or the other. thanks zenulator
Click to expand...
Click to collapse
Try zens xrom - smooth and pretty (ion with hero skin).
All I have to say is WOW!
Thanks a bundle for this release, I've been using the 08/08 bundle from vilord and was quite happy with it... till i tried this today I've been outta the loop for the last little while and haven't been able to keep up with development on the various builds (moving, lack of interwebs, RL getting in the way, etc) and have been VERY impressed with how this has some along. Experimental bluetooth too!!! OMGWTFBBQ!!!! Now to start work on the Android ROM again
edit: for those having issues with the bundled camera app, try FXCamera or PRO Paint Camera. Both are free and work rather well.
masalma said:
Nice port, but the camera doesn't seem to work for me, keep getting the force close.
Nice work
Nas
Click to expand...
Click to collapse
Yea don't use the camera. Download snap photo or fxcamera beta if you want to use the camera. There is also a pay app called camera zoom that works to.
zenulator said:
It runs with the same files as ion. So you can use the latest zImage and rootfs from vogue-android.
Click to expand...
Click to collapse
Yup, and it runs very fast also
Thanks.
zenulator said:
Yea don't use the camera. Download snap photo or fxcamera beta if you want to use the camera. There is also a pay app called camera zoom that works to.
Click to expand...
Click to collapse
Thank you for the great work, the app runs really smooth, what does the headset icon mean?
masalma said:
Thank you for the great work, the app runs really smooth, what does the headset icon mean?
Click to expand...
Click to collapse
It's just left over from the g1 version. It serves no purpose.
Anyone try 320x428 resolution with success yet?
No problem with different resolutions (in kaiser), runs great!!
ok, i tried researching this, but this is my problem - my phone (sprint vogue) works great with lcd_density = 0 (no grainy images, not drastically grainy, but if u look close, u can see the grains)..
but with newest zimage, rootfs(don't know wats causing the problem).. causes the images to be grainy.. when i boot up android, somewhere it says it is setting the lcd_density = 3 (which is what most sprint vogue users are supposed to use).. i don't want that.. isn't my settings in default not over-riding the settings based on what, i believe dzo wrote code for, to autodetect and use lcd_density...
zenulator - can u please help me as i guess u are the only person who can fix this...
love the newer donut builds, use them all the time.... but the grainy problem is driving me crazy..
myshinynewtouch said:
ok, i tried researching this, but this is my problem - my phone (sprint vogue) works great with lcd_density = 0 (no grainy images, not drastically grainy, but if u look close, u can see the grains)..
but with newest zimage, rootfs(don't know wats causing the problem).. causes the images to be grainy.. when i boot up android, somewhere it says it is setting the lcd_density = 3 (which is what most sprint vogue users are supposed to use).. i don't want that.. isn't my settings in default not over-riding the settings based on what, i believe dzo wrote code for, to autodetect and use lcd_density...
zenulator - can u please help me as i guess u are the only person who can fix this...
love the newer donut builds, use them all the time.... but the grainy problem is driving me crazy..
Click to expand...
Click to collapse
The lcd density should be 128 or 160 the panel types are either 1,2,3 and power/sleep is 0,1,2,3. You can also use other resolutions like 320x428 or turn down the screen brightness in settings. I've only noticed those lines when the screen brightness was all the way up.
zenulator said:
The lcd density should be 128 or 160 the panel types are either 1,2,3 and power/sleep is 0,1,2,3. You can also use other resolutions like 320x428 or turn down the screen brightness in settings. I've only noticed those lines when the screen brightness was all the way up.
Click to expand...
Click to collapse
i got it all confused, sorry zen, i meant the panel_type = 3, now that i am looking at my default file, i realize i got it all wrong, i had panel_type = 0 until now... don't know how that worked until now... power/sleep mode = 0
and u are right about the screen brightness as i have it at a higher brightness than wat comes by default..
is setting lcd density = 128 make any difference ? will it make it look any better if i increase the brightness
I'm going to post the cyanogen donut build later today. I'm also going to release a partial donut build from source.
zenulator - when u release the donut build from source, is it possible for you to incorporate cdma into your release plssss ? i can test it for you if necessary prior to your release or after it... anything u want...
myshinynewtouch said:
zenulator - when u release the donut build from source, is it possible for you to incorporate cdma into your release plssss ? i can test it for you if necessary prior to your release or after it... anything u want...
Click to expand...
Click to collapse
cdma is included it donut. i've still got a little work to do. I had to add some parts from cyanogen to make donut build functional. which is kind of redundant since the latest cyanogen is donut.
Hi all,
I have been searching high and low on XDA and using Google to try and find some answers to this but I have not had any luck. I've looked through the wiki and other threads. I'm sure that if I had looked when I first got my HD I would've found answers but now I can't. Did they ever exist? Anyway, my question....
My friend has a Diamond and his TF3D interface speed is amazing compared to mine. I have the stock rom and my TF3D version is 1.3.35350.1_1630.38.
The reason I ask now and didn't follow any developments when I first got my HD (around a year ago) is that I just installed SPB MS2. Now I am trying TF3D again but it is so slooooooow?
Another thing, my friend can just swipe his finger across the tab bar at the bottom and the different tabs load. Mine, I have to tap each button to see the relevant tab and even then, I wait sometimes half a second, sometimes a second or two. Edit: Sorry, wasn't pressing hard enough however, it is still slow at loading?
If it is suggested that I flash the ROM, I've never done this and so when doing so, do you lose all the installed programs and such? If yes, I have SPB Backup and so would doing a backup, flash ROM, run backup put me back to how my phone was pre-rom flash?
Thanks for any help offered.
Try searching this forum for a tweak software such as Tweak HD. If you install this and configure it with the adviced settings (ADV) your HD will be a lot faster.
You can also try and install the new VGA Driverpack from the project you can find in the ROM development section.
ThaDoc said:
Try searching this forum for a tweak software such as Tweak HD. If you install this and configure it with the adviced settings (ADV) your HD will be a lot faster.
You can also try and install the new VGA Driverpack from the project you can find in the ROM development section.
Click to expand...
Click to collapse
Thanks for the reply. I've installed HDTweak (did see this before) but was hoping for some registry tweaks instead. Would rather know what does what instead of installing an application that is supposed to perform certain changes/improvements.
See what happens after installing HDTweak.
Oh, I did also install the new Driverpack but found that games played slower. Maybe this has something to do with the screen having to draw more frames and so stressing the CPU more to do the same thing as if the driverpack wasn't installed? I'll post this question in that thread just to keep this one specific to TF3D!
Thanks
wayneywoo said:
Hi all,
I have been searching high and low on XDA and using Google to try and find some answers to this but I have not had any luck. I've looked through the wiki and other threads. I'm sure that if I had looked when I first got my HD I would've found answers but now I can't. Did they ever exist? Anyway, my question....
My friend has a Diamond and his TF3D interface speed is amazing compared to mine. I have the stock rom and my TF3D version is 1.3.35350.1_1630.38.
The reason I ask now and didn't follow any developments when I first got my HD (around a year ago) is that I just installed SPB MS2. Now I am trying TF3D again but it is so slooooooow?
Another thing, my friend can just swipe his finger across the tab bar at the bottom and the different tabs load. Mine, I have to tap each button to see the relevant tab and even then, I wait sometimes half a second, sometimes a second or two. Edit: Sorry, wasn't pressing hard enough however, it is still slow at loading?
If it is suggested that I flash the ROM, I've never done this and so when doing so, do you lose all the installed programs and such? If yes, I have SPB Backup and so would doing a backup, flash ROM, run backup put me back to how my phone was pre-rom flash?
Thanks for any help offered.
Click to expand...
Click to collapse
Are you sure? i had a diamond and the tf3d was crap even with the stock rom, i can use the swipe gesture on my HD to move from page to page aswell, and pages load pretty much instantly with mine, sounds like your device hasnt been optimed enough, just like a pc after extended use, it will become slow and unresponsive if you dont keep the file system and registy optimised
wayneywoo said:
Thanks for the reply. I've installed HDTweak (did see this before) but was hoping for some registry tweaks instead. Would rather know what does what instead of installing an application that is supposed to perform certain changes/improvements.
See what happens after installing HDTweak.
Oh, I did also install the new Driverpack but found that games played slower. Maybe this has something to do with the screen having to draw more frames and so stressing the CPU more to do the same thing as if the driverpack wasn't installed? I'll post this question in that thread just to keep this one specific to TF3D!
Thanks
Click to expand...
Click to collapse
Be sure to go through all HDTweak settings. Change values to ADV under the performance section.
i agree you have to....
optimize your device to its fullest capacity..i have stock rom ... on hd and have used hd tweak, plus few other applications found here, like driverpack 3 , gfxboost.. and few registry tweaks .etc...i am very impressed with touch ( sensitivity ) , speed of opening of most applications (yes ,some does have slight lag ) but overall, programs eg..file exployer,programs..settings etc..open instantaneous ...
( i also set sensitivity,finger pressure in hdtweak to very high )
i further hardly swipe manila ..."home " tab and it slides ,right through to last tab ( settings tab ) on manila ( vice versa)
my advice is also optimize ,( trail and error ) and seach, seach ..xda threads..
good luck
Sorry for my English
I don't konw whether it only happens on me，but I want to clame that，because it‘s really make my device very convenient.
when I install Stockwell's MIUI-110711,The problem appeared,While I touch screen,and move it,I found the screem was Flicking,and several lines of serrate on it.The 2D display become very awful.So I change the kernel.When I use the kernel that did not modify the fps(neocore test:45fps) ,My device tune to normal,but if I use the new kernel which has modify the fps(neocore:54fps),the 2D display became less responsive,So I hope if anyone can solve this problem,Thanks very much.
jiangheng90 said:
Sorry for my English
I don't konw whether it only happens on me，but I want to clame that，because it‘s really make my device very convenient.
when I install Stockwell's MIUI-110711,The problem appeared,While I touch screen,and move it,I found the screem was Flicking,and several lines of serrate on it.The 2D display become very awful.So I change the kernel.When I use the kernel that did not modify the fps(neocore test:45fps) ,My device tune to normal,but if I use the new kernel which has modify the fps(neocore:54fps),the 2D display became less responsive,So I hope if anyone can solve this problem,Thanks very much.
Click to expand...
Click to collapse
Thanks for your post, probably a good idea for any kernel devs to ensure vsync is enabled then, no doubt this will affect some other users.
i have the same problem with the new francokernel and its because the v-sync is off in tha kernel allowing up to 54 fps. this causes asynced frames which doesnt look very nice. if there is a way to turn v-sync on please somevody respond
I am very aware of that. I'll do some tests and see what happens with it enabled in terms of gaming performance.
Sent from my Huawei u8800 using XDA Premium App
Dear friends,
Please let me know the cons and pros of Android on Blackstone (Touch HD).
- Camera
- Game
- Appz
- Smoothness
- Speed
- Bluetooth
- Wifi
...
it depends on build but you should try out the new FRX07 it has most (if not all) of the things working very well,i personally am using GBX0A which is alpha version but the way i compiled it somehow gave it enormous stability and reliability....you should try for yourself and see if it fits you...
One other larger setback with Android would be battery standby. It's quite poor, I think, at the moment. Efforts are being made for increasing standby but I don't think our Blac is targeted for that.
farukb said:
it depends on build but you should try out the new FRX07 it has most (if not all) of the things working very well,i personally am using GBX0A which is alpha version but the way i compiled it somehow gave it enormous stability and reliability....you should try for yourself and see if it fits you...
Click to expand...
Click to collapse
Can you describe what you mean by "the way I compiled it"?
There is much newer code in the GB tree than what is in the release for GBX0A, so if you built the system image yourself, that might explain it .
- Camera - Works on Blackstone. Current Kernels have support for camera.
- Game - We have okay resolution so games with WVGA are not problems for us but problem is that resolution is quite high for Adreno 130.. So quite lacking of performance
- Appz - They are very good.
- Smoothness - With Jit + My kernel its working good (Neocore 29.8 Due to 30 FPS cap.. but you cant except that every app will work smoothly..
- Speed Its okay even from Sd card.. But i told you my reason..
- Bluetooth Pairing/sending is working. But A2DP is not working
- Wifi Seems to work fine.. Sometimes lower speed but its okay..
arrrghhh said:
Can you describe what you mean by "the way I compiled it"?
There is much newer code in the GB tree than what is in the release for GBX0A, so if you built the system image yourself, that might explain it .
Click to expand...
Click to collapse
it's the particular kernel and rootfs i used...i really have a daytime long battery and rock solid build...just don't remember which ones...maybe i could provide the img so you can check it
farukb said:
it's the particular kernel and rootfs i used...i really have a daytime long battery and rock solid build...just don't remember which ones...maybe i could provide the img so you can check it
Click to expand...
Click to collapse
Well the kernel is easy to figure out - in Android, Settings -> About -> kernel version. If in WinMo, just look at the name of the modules file...
rootfs is a little harder. Date/timestamp can help, assuming you extracted it directly to your card. Otherwise... I guess md5, but you really think there's a particular kernel&rootfs that are just completely bulletproof? Sounds like snake oil to me .
For me the biggest problems for daily use are:
- Bluetooth: Calls and A2DP are not working. I have long hours on the car...
- Call speaker: it's not working.
- Music stuttering: improved on the FRX07, but not solved (there is a patch on an old kernel but it has not been updated).
- Random freezes and SODs.
I also miss some WM6.5 apps and some Manila 2.5 features
The pros list is long, so better to run from SD and have the best of both worlds. it is a pitty that we can't run both at the same time...
It's a pity that we can run both at the same time...?
I'm all for NAND, but until Android is stable, I think it's great that we can run both at the same time. That way if there's something you just have to have that WinMo provides, you can just boot back to it...
arrrghhh said:
Well the kernel is easy to figure out - in Android, Settings -> About -> kernel version. If in WinMo, just look at the name of the modules file...
rootfs is a little harder. Date/timestamp can help, assuming you extracted it directly to your card. Otherwise... I guess md5, but you really think there's a particular kernel&rootfs that are just completely bulletproof? Sounds like snake oil to me .
Click to expand...
Click to collapse
i know how to check the current kernel but the thing is that old one did something when i first ran haret with it...although i'm not sure if rootfs leaves any trace of previous commits,so it may have nothing to do with rootfs
Thank you dear friends.
I will try FRX07.
The tit aaarrgh(troll)
Sent from my FroyoB THUNDERBOLT V1 using Tapatalk
Neopeek.com and tiad8.com for a friendly forum with no sarcastic childish comments from aaaarrgh(troll)
Sent from my FroyoB THUNDERBOLT V1 using Tapatalk
mrbennett said:
The tit aaarrgh(troll)
Click to expand...
Click to collapse
mrbennett said:
Neopeek.com and tiad8.com for a friendly forum with no sarcastic childish comments from aaaarrgh(troll)
Click to expand...
Click to collapse
Uh... what? I only see childish comments from you my friend.
Don't tell people to go to another site, that's childish. If you have a problem with me, then ignore me.
Some apps but not many.
Sent from my tiadriod nand
I have a question. I installes FRX07 on my blackstone and everything seems to work oké, but the sound. I don't seem to be able to get any sound out of the device, no ringtone (with incoming calls), no sounds with music, no sounds with video etc. Does anyone have any idea?
Regards,
Oasis2000
Oasis2000 said:
I have a question. I installes FRX07 on my blackstone and everything seems to work oké, but the sound. I don't seem to be able to get any sound out of the device, no ringtone (with incoming calls), no sounds with music, no sounds with video etc. Does anyone have any idea?
Regards,
Oasis2000
Click to expand...
Click to collapse
Hrm, I have heard of this issue before. Unfortunately I don't remember a specific resolution.
I would try to reboot, see if that changes anything. Also, check the volume - make sure it's turned up (there's several different volume controls, check Settings -> Sound).
Assuming those simple things don't solve it, you might want to try the 'grabbing at straws' method. First, I would simply delete the data.img and let it create a new one on boot. Let the phone sit after you see the lock screen for a few minutes. Then try to use it, try to preview a ringtone. Still failing? Format the SD card with the HP Tool (full format, FAT32) and I would start over completely with the directions in FRX07.1 thread.
If it's still failing, try another SD card. Rinse & repeat. Still failing!?!? Well, I'll probably have to send some logs to the developers, because I don't know what else could be done to triage. Something else must be awry. Pull system and kernel logs with the app GetLogs - in AndroidApps\Other.
Not much...
Hey man,
You won't really miss much (if anything) switching to android.
- Camera = ok but better in winmo
- Game = some work perfectly, some are laggy and others plain old just won't work
- Appz = ditto above
- Smoothness = depends on how much you want to fidddle with different configurations
- Speed = ditto above but also varys from build to build
- Bluetooth = haven't tested..
- Wifi = works well
Running Android off the sdcard isn't really isnt all that bad apart from the fact that sometimes though it can be a bit fiddly getting everything to work together for a smooth experience builds, kernels, gapps, resizing partititions.... ect but once thats all over i think it beats winmo
and plus if your a fiddly guy (i dont know why you would be here if you wernt ) then you will enjoy working it all out
I have problem with few things that i am coping hard to settle.
1: If a build doesn't have any % battery sign how do i add it? without cooking it into the build, rather some way like adding few files to root or system folder or any simple method and job done?
2: Some SD builds are giving heavy lag which is hard to cope up with at times specially whilst trying to use it on the go in hurry... i have been using few new builds same issue but had dropped them to very old build... Now problem with old one is i cant' find a way to add Arabic input or letters are broken... if Arabic is added through applications then it just write like abc not attached as Arabic should be written, so is there any solution to fix this?
3: I hate the cyanogen dial phone interface you have to click or say tap few times to get simple things done rather than the FROYO ones just type a digit either a name is displayed in list to help you get ones you searching for instantly! and so easy to handle as rather than just going through tabs etc... NOW is there a way to change Cyanogen builds Phone interface to froyo?
Please give me link here i have been searching a lot to handle these problems things i am in trouble with but can't fix thought i'd ask here for some help...
Awaits for some good replies and thank you all for your time in advance.
Cheers
supermaster said:
I have problem with few things that i am coping hard to settle.
1: If a build doesn't have any % battery sign how do i add it? without cooking it into the build, rather some way like adding few files to root or system folder or any simple method and job done?
2: Some SD builds are giving heavy lag which is hard to cope up with at times specially whilst trying to use it on the go in hurry... i have been using few new builds same issue but had dropped them to very old build... Now problem with old one is i cant' find a way to add Arabic input or letters are broken... if Arabic is added through applications then it just write like abc not attached as Arabic should be written, so is there any solution to fix this?
3: I hate the cyanogen dial phone interface you have to click or say tap few times to get simple things done rather than the FROYO ones just type a digit either a name is displayed in list to help you get ones you searching for instantly! and so easy to handle as rather than just going through tabs etc... NOW is there a way to change Cyanogen builds Phone interface to froyo?
Please give me link here i have been searching a lot to handle these problems things i am in trouble with but can't fix thought i'd ask here for some help...
Awaits for some good replies and thank you all for your time in advance.
Cheers
Click to expand...
Click to collapse
first of all i would say that sd builds are very slow compared to nand builds obviously because or read/write speeds !
try getting the latest cyanogenmod sd build (eg American Android) !!
also u can try custom dialers available in the market if you dont like the default one !!
btw may i ask why do u use sd builds ??
have u dualbooted ur hd2 ??
Hmm.. that didn't answer my problem which i really want someone to answer it.
as for ur question i use WM and SD build both and i test or say use wm 6.5 builds a lot!
The froyo dialer doesn't pull up contacts when you type the name, that's a feature of sense roms.
Try the go dialer, that does contact lookup.