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.
I have searched the forum, but haven't found an awnser.
I haven't been using mobile shell 3.5 much because of the lag when switching screens. I've read many people with the TP2 use it, so I guess the user experience seems to differ.
Can someone give me tips on how to speed up mobile shell 3.5?
The 3d carousel works perfectly, while that should be more demanding on my phone. I have installed and tried several ROMS. I'm now running a very light one.
Any tips, tweaks or graphics drivers?
Thanks in advance.
quarintus said:
I have searched the forum, but haven't found an awnser.
I haven't been using mobile shell 3.5 much because of the lag when switching screens. I've read many people with the TP2 use it, so I guess the user experience seems to differ.
Can someone give me tips on how to speed up mobile shell 3.5?
The 3d carousel works perfectly, while that should be more demanding on my phone. I have installed and tried several ROMS. I'm now running a very light one.
Any tips, tweaks or graphics drivers?
Thanks in advance.
Click to expand...
Click to collapse
I was actually able to run SBP MS on my old wizard (197Mhz proc!) and the carousel was completely lag-free even on that hardware, but I did have a slight lag on screen changes though.
I have only seen one set of "upgraded" video drivers for the TP2, in the thread below. Note- despite the title, they're actually OpenGL drivers, not D3D. I don't know if they'll improve MS 3.5 for you, but it's worth taking a look at:
http://forum.xda-developers.com/showthread.php?t=546522&highlight=at0mang+driver
Tried it. Thanks. Sadly no improvements on WM shell.
quarintus said:
I have searched the forum, but haven't found an awnser.
I haven't been using mobile shell 3.5 much because of the lag when switching screens. I've read many people with the TP2 use it, so I guess the user experience seems to differ.
Can someone give me tips on how to speed up mobile shell 3.5?
The 3d carousel works perfectly, while that should be more demanding on my phone. I have installed and tried several ROMS. I'm now running a very light one.
Any tips, tweaks or graphics drivers?
Thanks in advance.
Click to expand...
Click to collapse
Are you referring to when you use your finger to move left / right / up down? Or do you mean when selecting the Contact button? Or is is slow everywhere?
One thing you should do is change the file system settings to increase performance. Also change the glyph settings & Etc. I think BsB Tweaks will change these.
stevedebi said:
Are you referring to when you use your finger to move left / right / up down? Or do you mean when selecting the Contact button? Or is is slow everywhere?
One thing you should do is change the file system settings to increase performance. Also change the glyph settings & Etc. I think BsB Tweaks will change these.
Click to expand...
Click to collapse
It's mainly using your finger to scroll. But also a bit the icon loads. I'll try BsB tweaks. Not sure what settings you mean, but I try something.
If anyone can make this more clear, it's apreciated.
Only settings I found was ther glyph setting. That one I did. It actually became a little faster. So if the other tweaks work just as good, I'd like to know where to find them.
quarintus said:
Only settings I found was ther glyph setting. That one I did. It actually became a little faster. So if the other tweaks work just as good, I'd like to know where to find them.
Click to expand...
Click to collapse
Actually, they are in the Advanced Configuration tool, under "Performances". Change the system cache to the advised settings.
http://forum.xda-developers.com/showthread.php?t=418151
stevedebi said:
Actually, they are in the Advanced Configuration tool, under "Performances". Change the system cache to the advised settings.
The Advanced Config Tool works wonders speeding up many things. Fixed some network lag problems I was having since I had to flash back to the stock at&t rom while traveling. Only thing that has caused any problem for me was a camera setting I didn't need (naturally when I really needed the camera) the one that encodes rotated images as portrait. Other than that it has really helped out. (I now store the .net compact framework cab on my sd card so I don't need a computer to deal with it on the train...) Still looking for better video playback with standard encoded .avi's though (OpenGL drivers worked but I didn't notice an improvement...)
Click to expand...
Click to collapse
hey guys, i'm developing a Legend-based ROM "Fallah":
http://forum.xda-developers.com/showthread.php?t=706649
i'm having a problem with Rosie being laggy !!
I used APKTool to decode it, but I don't know what to modify and I have no experience in Sense UI.
when on a ListView the animation is smooth, and NeoCore GPU benchmarks are pushing 30's without sound "which is very good". i'm guessing it's a FPS issue in Rosie launcher ??
so if Rosie hackers can lend me some of their time and tell me what to modify in Smali code to fix the lag??
Behnam (@benocharm on twitter) solved that Ask him!
thanks bro..
I tweeted him last night and waiting for his reply..
MaXo64 said:
thanks bro..
I tweeted him last night and waiting for his reply..
Click to expand...
Click to collapse
I dont have my build environment left but what I did was to use the "Launcher" classes (Launcher*.smali) from a generic Hero 2.1 ROM. So simply replace all "Launcher(number).smali" from Legend's Rosie with the ones from Hero's Rosie and then fix up all issues it might cause (i.e. icons are misplaced)
Regards,
B
behnaam said:
I dont have my build environment left but what I did was to use the "Launcher" classes (Launcher*.smali) from a generic Hero 2.1 ROM. So simply replace all "Launcher(number).smali" from Legend's Rosie with the ones from Hero's Rosie and then fix up all issues it might cause (i.e. icons are misplaced)
Regards,
B
Click to expand...
Click to collapse
thanks behnaam, I'll try it and report back
Hey Behnaam! good to see you back around these parts again.
Just noticed on your twitter you were looking to start hero dev again. You going to be helping with the .34 port? and did you ever get anywhere with Hero UV'ing?
just another question, after building the APK and signing it with my private key. it shows in logcat that it doesn't have the same signature as "com.htc.rosie.uid.shared"?!
I tried making the "SharedUserId" in the AndroidManifest.xml as "android.util.root". it worked but I cant add HTC widgets. I assigned HtcAddProgramWidget.apk with the same SharedUserId but no luck.
the question is, where can I find the "com.htc.rosie.uid.shared" package? in the framework?
thanks in advance..
a better question is how do we edit the widgets not to be dependent on rosie cause then we could use whatever launcher
capychimp said:
a better question is how do we edit the widgets not to be dependent on rosie cause then we could use whatever launcher
Click to expand...
Click to collapse
I dreamed about that once
these days i am comparing normal widgets and sense widgets to see if i can find out how
MaXo64 said:
just another question, after building the APK and signing it with my private key. it shows in logcat that it doesn't have the same signature as "com.htc.rosie.uid.shared"?!
I tried making the "SharedUserId" in the AndroidManifest.xml as "android.util.root". it worked but I cant add HTC widgets. I assigned HtcAddProgramWidget.apk with the same SharedUserId but no luck.
the question is, where can I find the "com.htc.rosie.uid.shared" package? in the framework?
thanks in advance..
Click to expand...
Click to collapse
Sign all htc widgets and rosie with the same key and then flash, all widgets are under the shared rosie uid. That will help you
Btw did rosie get faster?
Regards,
B
ggrammer said:
Hey Behnaam! good to see you back around these parts again.
Just noticed on your twitter you were looking to start hero dev again. You going to be helping with the .34 port? and did you ever get anywhere with Hero UV'ing?
Click to expand...
Click to collapse
I'll checkout the work on .34 and try to help out, kernels isn't really my area tbh But I'll try to help out.
I can't really remember how far I went with Hero UV'ing.
behnaam said:
Sign all htc widgets and rosie with the same key and then flash, all widgets are under the shared rosie uid. That will help you
Btw did rosie get faster?
Regards,
B
Click to expand...
Click to collapse
it improved a lot, but still not like official Hero..
MaXo64 said:
it improved a lot, but still not like official Hero..
Click to expand...
Click to collapse
Well then you could look through the transition speeds, cant remember where I found it but it's probably in SettingUtils class (SettingsUtils.smali)
You may not get the exact same speed as the generic Hero Rosie but speeds similar to it.
Hi,
Anybody can tell me that how to enable dual -touch on phone...
I know the method of editing build.prop
but will it be possible or it needs a kernel support??
Phone is running on 2.2 Froyo....
my friend is going to buy this phone tomorrow but it doesnt have multi-touch....
I know how to root this phone
so anyone can help me little please?
I hope you can enable multitouch on Galaxy PRO, it would be awesome!
tried build.prop tweak.... not working
We have to wait to improve this phone, I think.
ya.... i think so...
actually i dont have this phone.... my friend is having....
I tried changing LCD density and fonts and few things but nothing worked because of it's low resolution ..... fonts are still unreadable sometime.......
Zeam launcher is working fine...... u can try it....
mir2006 said:
I hope you can enable multitouch on Galaxy PRO, it would be awesome!
Click to expand...
Click to collapse
forum.xda-developers.com/showthread.php?t=920669
check this out...before that take a backup operation.And read the instructions properly.
I have no responsibility.
Won't work that way, you'll need to re-compile the kernel and maybe re-write the touchscreen driver to support dual/multi-touch
From my fingers to your eyez
Hi to all
I wonder if anyone knows of any way to achieve kcal screen configuration on H2OS.
I think that there is still no kernel developement for h2os, but perhaps theres another way to figure out to set saturation and contrast controls.
I would like H2OS as daily driver, but i need to change kcal screen default settings.
Any idea?
Thanks!!
smrdelj said:
Hi to all
I wonder if anyone knows of any way to achieve kcal screen configuration on H2OS.
I think that there is still no kernel developement for h2os, but perhaps theres another way to figure out to set saturation and contrast controls.
I would like H2OS as daily driver, but i need to change kcal screen default settings.
Any idea?
Thanks!!
Click to expand...
Click to collapse
It's unlikely this can happen. We don't have kernel sources for H2OS or O2 so we cannot compile a kernel with KCAL drivers. I hope I helped
So, is it really impossible without developing a kernel? No app, tweak, or anything instead? I can't believe it!
smrdelj said:
So, is it really impossible without developing a kernel? No app, tweak, or anything instead? I can't believe it!
Click to expand...
Click to collapse
As @zFramed said, unless the kernel has kcal incorporated, it isn't possible.
Ok guys, thanks!