Hello devs and users..i've seen on a website,that htc dream in the future (after android 2.0 eclair),can't be upgraded with new software version,because his internal memory is too small...is really so,or xda developers may create lighter updates?
Excuse for my (bad) english!
thanks everyone
PS:excuse me mods and amins but i've seen the correct section (dream Q&A)only now! =(
To answer the question here in case anybody else reads this thread (you should NEVER leave a thread in this state where it doesn't answer the question), the answer is this;
Those websites that you have read are written by MORONS. There is NO REASON AT ALL why dream can't be upgraded to any future android version. There is *plenty* of space, and a *LOT* that can be done to use storage and ram more efficiently.
iCe87 said:
Hello devs and users..i've seen on a website,that htc dream in the future (after android 2.0 eclair),can't be upgraded with new software version,because his internal memory is too small...is really so,or xda developers may create lighter updates?
Excuse for my (bad) english!
thanks everyone
PS:excuse me mods and amins but i've seen the correct section (dream Q&A)only now! =(
Click to expand...
Click to collapse
I gotta agree, those guys are morons. All the new android phones coming out are all close to the same specs so do you really think they would release phones now that will be obsolete before the contracts are up, nah. The dream has plenty of life in it and plenty of time for it to keep advancing. Plus the devs here work some crazy ass magic on this platform
Ok guys thanks for the answers =) i'm glad to read that!...however i expect to see the price of two android new phones: Motorola Cliq/Dext and Samsung Galaxy i5700..
their should be a low price smartphones (i hope this!)
the cliq looks like a nice peice of hardware coming out. But not be a bad next step, i got the g1 so i could be in on the ground floor of hacking android
but the dream has 256mb of rom memory. while all the other newer android devices have 512mb of rom memory and sources said that the cupcake update almost filled up the available rom memory. i just dont see how update past 2.0 will even fit. besides placing part of the rom on the sd card.
brian_v3ntura said:
but the dream has 256mb of rom memory. while all the other newer android devices have 512mb of rom memory and sources said that the cupcake update almost filled up the available rom memory. i just dont see how update past 2.0 will even fit. besides placing part of the rom on the sd card.
Click to expand...
Click to collapse
Sure 256. Thing is that the android OS DREAM ADP1 build (take a look at cyanogen's latest donut) is sitting at just over 60 MB (in the case of crazy experimental bloatware -- only 52.4 for the official image). And yes, that's already DONUT 1.6 (to prove that it can be done) My math says that we have a flexibility of somewhere in the neighborhood of (taking boot block and other stuff into account) about 140 MB sitting around that *could* be used for system. Very important to think about is the /cache partition, which is WASTING over *SIXTY MEGABYTES*, which means that we can EASILY fit in a system image that is *TWICE AS BIG*, and that is BEFORE compromising the /data partition (which also can be done yielding up to an additional 75MB).
Here's a tip for ROM developers as the /system partition starts to get tight....
mount /dev/block/mtdblock4 at somewhere like /system/block4, create a small (i.e. 5, 10 MB) loop filesystem at /system/block4/cache.img and mount THAT at /cache, then throw a whole bunch of crap from (for example) /system/app into /system/block4/app and create a link /system/app --> /system/block4/app.
Note: there is a WHOLE BUNCH of crap included in current system images that doesn't need to be there, i.e. install as regular apps instead of as system apps. Just as a quick look-through, there is over 10 MB that can be recovered just from the /system/app directory on cyanogen 4.1.10.1, with that, we can get close to 15 MB free on /system on a Donut build. Now put in some more aggressive optimizations...
There are *TONS* of things that can be done to fit in new android versions.
Oh, and did I mention that newer doesn't necessarily mean *bigger*? Who says that éclair (or flan) will be any bigger than 1.0 was?
Now consider this:
The "official" ADP1 v1.5 system image is only TWO MEGABYTES larger than 1.0 at 52.4 MB.. of an available 67.5 hmm.. that leaves plenty of space already = 15 MB. And I'm sure you're aware of how many new features and polishes they added into the 1.5 for only 2 MB.... Just think what they can do with 15! Just think what can be done with 75!!!! (before even compromising /data).
I'll repeat again just to be clear.... We are NOT up against a wall with space. There is *LOTS* of space for new versions.
Thanks to all for the informations!!i'm glad to to read that!!!!...
lbcoder said:
Sure 256. Thing is that the android OS DREAM ADP1 build (take a look at cyanogen's latest donut) is sitting at just over 60 MB (in the case of crazy experimental bloatware -- only 52.4 for the official image). And yes, that's already DONUT 1.6 (to prove that it can be done) My math says that we have a flexibility of somewhere in the neighborhood of (taking boot block and other stuff into account) about 140 MB sitting around that *could* be used for system. Very important to think about is the /cache partition, which is WASTING over *SIXTY MEGABYTES*, which means that we can EASILY fit in a system image that is *TWICE AS BIG*, and that is BEFORE compromising the /data partition (which also can be done yielding up to an additional 75MB).
Here's a tip for ROM developers as the /system partition starts to get tight....
mount /dev/block/mtdblock4 at somewhere like /system/block4, create a small (i.e. 5, 10 MB) loop filesystem at /system/block4/cache.img and mount THAT at /cache, then throw a whole bunch of crap from (for example) /system/app into /system/block4/app and create a link /system/app --> /system/block4/app.
Note: there is a WHOLE BUNCH of crap included in current system images that doesn't need to be there, i.e. install as regular apps instead of as system apps. Just as a quick look-through, there is over 10 MB that can be recovered just from the /system/app directory on cyanogen 4.1.10.1, with that, we can get close to 15 MB free on /system on a Donut build. Now put in some more aggressive optimizations...
There are *TONS* of things that can be done to fit in new android versions.
Oh, and did I mention that newer doesn't necessarily mean *bigger*? Who says that éclair (or flan) will be any bigger than 1.0 was?
Now consider this:
The "official" ADP1 v1.5 system image is only TWO MEGABYTES larger than 1.0 at 52.4 MB.. of an available 67.5 hmm.. that leaves plenty of space already = 15 MB. And I'm sure you're aware of how many new features and polishes they added into the 1.5 for only 2 MB.... Just think what they can do with 15! Just think what can be done with 75!!!! (before even compromising /data).
I'll repeat again just to be clear.... We are NOT up against a wall with space. There is *LOTS* of space for new versions.
Click to expand...
Click to collapse
only time willl tell. becuz i didnt get what u was saying i kinda skimmed. i just want to see the tru successor for the g1 from htc
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
gridlock32404 said:
Click to expand...
Click to collapse
hahahahahahahahahahahahahaha
Related
EDIT 23-11-2010: New Barebone release available!
The following CyanogenMod-Ports are available now:
"Official" CM6 + CM6.1 Barebone (this is the latest release)
FroyoRedux CM6
SuperFroyo
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Quick-Installation-Guide:
Read this installation instructions by chase21
Thanks go to:
Balsat, XDANDROID-TEAM, Cyanogen + Team, Seqzester, ferlanero and everyone else whom I forgot.
Used kernel + modules: htc-msm-linux by glemson and balsat
Used rootfs: XDAndroid ported to work on EXT2-Partition
Mixed-Up and ported by: Neopeek
Source: CyanogenMod-6
Changelog + Download
So if i understand correctly, i just need to create ext2 rootfs, use zimage from froyo port and it would work?
I will try it. Just my phone is currently completely dead (red light under power button) since android sucked last electrons of power from it
someone test this n reply ... .. and someone tell me how to create partition on my micro sd
matejdro said:
So if i understand correctly, i just need to create ext2 rootfs, use zimage from froyo port and it would work?
I will try it. Just my phone is currently completely dead (red light under power button) since android sucked last electrons of power from it
Click to expand...
Click to collapse
Yes, it may work. I can't guarantuee it for you. Also you will have to set MTYPE accordingly in startup.txt and add also keyboard of X1 to it. Perhaps you will have to tweak some other thingies but just let's see what happens
I have tried all files from Tremere's froyo build except rootfs from your build. But it's keep looping at "30.000ms after vsync request" something like that.
What the hell is MTYPE? Sorry i'm completely newbie here.
matejdro said:
I have tried all files from Tremere's froyo build except rootfs from your build. But it's keep looping at "30.000ms after vsync request" something like that.
What the hell is MTYPE? Sorry i'm completely newbie here.
Click to expand...
Click to collapse
MTYPE, RAMADDR and RAMSIZE are set in startup.txt
Just use my complete HARET-PAKET and combine it with the latest zImage + kernel and edit values in startup.txt. No need for initrd.gz and rootfs.img as both are included in the tarred gzip-archive which you have to extract to the root of your ext2-partition. Haret-Paket goes to FAT32-partition with the modification stated above. You may also set lcd density accordingly.
I think an experienced linux user may give this a try...and keep in mind to securely unmount your ext2 -partition in linux before starting haret
So you mean that I should partition my sd card?
Sent from my X1 via XDA android app. Sorry for typos, it's pain in the ass to type here.
matejdro said:
So you mean that I should partition my sd card?
Sent from my X1 via XDA android app. Sorry for typos, it's pain in the ass to type here.
Click to expand...
Click to collapse
Without partitioning it won't work. You may follow my signature to the other threads to see how it's working for others. Initially a lot of people had probs getting this to work when i released my first eclair-port...
So there is no way to stuff file system into rootfs file like releases till now?
okay card partitioned, files copied but after running hater it is going to restart
using startup.txt from tremeres distro
after adding root=/dev/mmcblk0p2 init=/init rootwait rw rootdelay=3 console=tty0 rootdelay=3 to the startup.txt it is running but upside down screen
screen is upside down but press detetection is ok ....
how to extract ext2 file ?
Devaster said:
screen is upside down but press detetection is ok ....
how to extract ext2 file ?
Click to expand...
Click to collapse
He have maybe not add the patch to rotate the screen upside down(x1 have the screen upside down but WM rotate it and Android with patch).
Use linux and mount it to get the file inside. Howto mount: use google
vatoloco: you'll need to either apply http://code.google.com/p/android/issues/detail?id=9604 to your aosp source or take libsurfaceflinger from the system image from my dist/recent xdandroid.
as well you need to detect the Xperia (grep cpuinfo for Kovsky) and set ro.sf.hwrotation=180
tremere : what i need to search for replacing ?
@ temere : can u post in a detail way wat all we shud do step by step ...
i have very meagre knowledge of this ..
ur effort will be appreciated a lot
Ok, glad to hear that it booted up. As I have seen that stinebd added kovsky support for rootfs I wanted to check if this boots up for you. Last days I didn't add any updates and will continue updating my builds accordingly by tomorrow! I will surely need some help of any of you guys in testing this as I have no X1 to test on my own.
New release is available. I only implemented latest rootfs-updates by stinebd into it. The new base is: CyanogenMod 6 RC2.
Maybe someone can try and let me know what doesn't work.
vatoloco: you'll need to either apply http://code.google.com/p/android/issues/detail?id=9604 to your aosp source or take libsurfaceflinger from the system image from my dist/recent xdandroid.
as well you need to detect the Xperia (grep cpuinfo for Kovsky) and set ro.sf.hwrotation=180
Click to expand...
Click to collapse
Can anyone please try the fix posted by Tremere. I may package it up from his build and provide you with an androidupdate.tar if it works. Just let me know...
ro.sf.hwrotation=180 should go into build.prop
libsurfaceflinger.so should go into /system/lib/
Sorry I still have no X1 to test, so it's up on you...
Here are some screenies:
i've tested it,
this worked:
gps works i think
keyboard layout works
data works
sd card readen + music
this didnt worked:
bluetooth didnt work for me
speaker still makes sound
battery gets les hot in standby but stil takes 67% \
wifi gives an error
thats what i got til now
err ...please pardon my ignorance ...
can someone tell me the difference between cyanogen builds and usual android builds tht temere releases ...?
Hey Neopeek,
Good to see you working on the X1 again. I'll see if I can find some time to test your version.
included ro.sf.hwrotation=180 into build.pro, libsurface on its place but display rotated upside down and touch not working ....
I've been working for the past couple of days on a multiboot/multi-ROM system for the Incredible, based conceptually (no code or implementation has been lifted) on Team ADX's DualRom.
It's a bit of a work in progress, right now, so I'm not entirely comfortable releasing anything (ROM images, the app), but I can give a couple screenshots and a brief technical rundown of how it works.
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Implementation
ROMs (meh, I don't like calling them that anymore, they're not read-only ) are stored in /emmc as a collection of filesystem images. This is at odds with DualRom, which takes over all of /emmc as a system volume and maintains symlinks for /data and /cache. HBOOT seems too evil to leave well-enough alone, and may try to tinker with the /emmc volume, corrupting certain non-FAT32 partitions.
ROM update.zips need to be modified to create these loopback filesystems and loopmount them. I will be providing reference implementations for these update.zip modifications.
initramfs images will also need to be modified to loopback mount these images from /emmc. I will be providing reference implementations for these modifications, as well.
ROM icons and information are stored next to their images.
Example Filesystem Layout
Code:
$ ls -lh /emmc
----rwxr-x 1 system sdcard_r 45 Apr 19 23:20 CM7.ROM.json
----rwxr-x 1 system sdcard_r 17.4K Apr 20 03:12 CM7.ROM.png
----rwxr-x 1 system sdcard_r 1.9M Apr 19 23:20 CM7.boot.img
----rwxr-x 1 system sdcard_r 128.0M Apr 19 16:27 CM7.cache.img
----rwxr-x 1 system sdcard_r 640.0M Apr 19 16:31 CM7.data.img
----rwxr-x 1 system sdcard_r 200.0M Apr 19 16:31 CM7.system.img
Critique
Super ROM Switcher isn't actually its final name, but I am rather uncreative . I'm open to suggestions and feedback (about names, the interface, etc.)
There are a few rough edges that I plan to work out before release, such as the fact that it clutters /emmc and the interface doesn't display much useful information.
Planned Features
Mount a ROM hierarchy (reconstruct / from the initramfs into tmpfs, loop-mount /system, /data and /cache into it).
Possibly download prebuilt images.
Delete an entire ROM image set.
Release
TBD
Thanks
Team ADX - DualRom as inspiration
jaykresge - Nothing Special (used as Stock-style ROM in my testing)
MIUI devs - MIUI (used in testing)
CyanogenMod Team - CM7 (used in testing, and is awesome )
Looking forward to this!
DHowett said:
ROM update.zips need to be modified to create these loopback filesystems and loopmount them. I will be providing reference implementations for these update.zip modifications.
Click to expand...
Click to collapse
I think this is a great implementation concept, which is quite clean. The only issues I can think of (until I try it) is likely sd-ext, but I stopped using it long ago. I figure once I actually run out of space in data I'll switch.
DHowett said:
ROM update.zips need to be modified to create these loopback filesystems and loopmount them. I will be providing reference implementations for these update.zip modifications.
initramfs images will also need to be modified to loopback mount these images from /emmc. I will be providing reference implementations for these modifications, as well.
Click to expand...
Click to collapse
Now we just need someone to modify the clockwork recovery code to intercept the updates so we can get nightlies and other non dual boot .zip's working
EDIT: Meant to say great work! Looks very promising. As soon as I can use the existing (at least majority of) zips with this set up, would easily switch.
I like this too....now we could boot more than 2 roms
Sent from my ADR6300 using XDA App
DHowett said:
ROMs (meh, I don't like calling them that anymore, they're not read-only ) are stored in /emmc as a collection of filesystem images.
Click to expand...
Click to collapse
How do you feel about calling them "Loads," rather than ROMs? (This might also help with giving some permanent name ideas for this cool project.)
dscribe said:
How do you feel about calling them "Loads," rather than ROMs? (This might also help with giving some permanent name ideas for this cool project.)
Click to expand...
Click to collapse
So how many "loads" can this app take?
davwman said:
So how many "loads" can this app take?
Click to expand...
Click to collapse
Then why don't we call this app "She". How many "Loads" can "She" take.
Oh, and I can't wait to try this. Awesome work!
sd5500 said:
Then why don't we call this app "She". How many "Loads" can "She" take.
Oh, and I can't wait to try this. Awesome work!
Click to expand...
Click to collapse
I don't get itt
Sent from my ADR6300 using XDA App
This looks awesome! Will this let us install ROMs that have system folders larger than 250MB? If so, Sense 3.0 will be here in no time.
corypaul said:
I don't get itt
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Ill tell you when you're older.
Tapatalk Pro Sig. Yep, boring.
ROM Glom?
glom
verb
to take physical control or possession of (something) suddenly or forcibly
Dual boot is great.. it takes less than a minute to push a button to switch from stock sense to cm7 .... aka dual " she " boot
I think this kind of thing would be great as long as both ROMs can actively read each others texts and phone logs and that sort of thing.
Kind of like how I dual boot Ubuntu and Windows. The Ubuntu partition is relatively small, but I've got symlinks for the music, pictures, videos, etc. on the Windows partition. It keeps everything very smooth and convenient. (I know the music stored on the SD card will do this, I'm just using that as an example.)
I'm assuming, though, that since the AOSP and Sense DBs are so different, that it might not be feasible. Either way, I'll definitely be trying this. It's a really cool concept.
Mounting
Code:
localhost / # ls /emmc/SkyRaider4
bootcomplete.inc.rc init sbin
cache init.goldfish.rc shutdown.inc.rc
data init.inc.rc sys
default.prop init.rc system
dev proc
localhost / # ls /emmc/SkyRaider4/data
app dalvik-cache drm misc system
app-private data local property
backup dontpanic lost+found skyraider
localhost / # df -h
...
tmpfs 8.0M 304.0K 7.7M 4% /mnt/emmc/SkyRaider4
/dev/block/loop17 371.9M 235.4M 136.5M 63% /mnt/emmc/SkyRaider4/system
/dev/block/loop18 629.9M 121.9M 476.0M 20% /mnt/emmc/SkyRaider4/data
/dev/block/loop19 124.0M 5.5M 112.0M 5% /mnt/emmc/SkyRaider4/cache
The rootfs simulacrum is in tmpfs and mounted read-only to mimick that the ramdisk can't be modified easily. Everything else is accessible and modifiable.
Research
I looked into a couple means for booting kernels without reflashing boot.img. kexec() doesn't work properly (and most kernels aren't actually built with support for it, so it's a moot point). Meh, oh well.
Addendi
I'm going to open-source the management program once it's ready.
Questions
godsmacked4653 said:
I think this kind of thing would be great as long as both ROMs can actively read each others texts and phone logs and that sort of thing.
Kind of like how I dual boot Ubuntu and Windows. The Ubuntu partition is relatively small, but I've got symlinks for the music, pictures, videos, etc. on the Windows partition. It keeps everything very smooth and convenient. (I know the music stored on the SD card will do this, I'm just using that as an example.)
I'm assuming, though, that since the AOSP and Sense DBs are so different, that it might not be feasible. Either way, I'll definitely be trying this. It's a really cool concept.
Click to expand...
Click to collapse
Sense->Sense and AOSP->AOSP works, but anything else is a little bit iffy. I actually brought mmssms.db through Sense to AOSP but it required a full dump/reimport (with table fixing in between). It's too difficult to allow. However, mounting (as above) might help in copying over some data .
frostincredible said:
This looks awesome! Will this let us install ROMs that have system folders larger than 250MB? If so, Sense 3.0 will be here in no time.
Click to expand...
Click to collapse
Yep! Pretty much any size up to 4GB is supported (FAT32 limitation).
djh816 said:
Now we just need someone to modify the clockwork recovery code to intercept the updates so we can get nightlies and other non dual boot .zip's working
EDIT: Meant to say great work! Looks very promising. As soon as I can use the existing (at least majority of) zips with this set up, would easily switch.
Click to expand...
Click to collapse
I have an edify parser that (with some prodding) will turn an update.zip into ROM.system.img, ROM.data.img (etc)... a recovery modification isn't out-of-the-question, however!
Thanks for the support!
This sounds genius lol, would definitely save a lot of time and stress from flashing, switching, and wiping our phones all over creation lol.
Sent from my ADR6300 using XDA Premium App
Quite excited about this project I have to say.
What theme is on the screen of the OP?
Super excited about this. Is there an irc channel?
--
Sent from my Android phone. Please excuse my brevity/typos.
Blanko6 said:
What theme is on the screen of the OP?
Click to expand...
Click to collapse
Rover, but just the statusbar icons split into a separate theme.
daftlush said:
Super excited about this. Is there an irc channel?
Click to expand...
Click to collapse
irc.saurik.com #superrom
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Virtuous Unity is the first custom Sense 3.0 ROM, scaled for WVGA screens, to be based on an official shipping release from HTC (1.35.75.1).
The entire ROM is brand new, taking no application or framework components from any prior Sense 3 releases.
Unity is the result of a collaborative, team effort by the following developers:
Flemmard
Diamondback2010
rmk40
chrisch1974
m-deejay
seo
eViL D:
Screenshots
Features
Based on the official Sensation shipping ROM (1.35.75.1).
Ported for full functionality on each supported devices. Additional device support is being added regularly.
Resized for WVGA (800x480) displays, using a purpose built tool to modify HTC's proprietary m10 binaries, developed by Flemmard and Diamondback.
Heavily optimized for fluid performance and usability.
Overclocked kernels with numerous additional kernel modules.
Built-in screen state frequency scaling (1.2Ghz-245MHz/ondemand screen-on, 806Mhz-245Mz/conservative screen-off), via custom built Virtuous_OC C daemon.
Trackpad wake support (DesireZ/G2 and MT4G only).
WiFi calling (T-Mobile USA only).
Fully functional device hardware, including wifi, bluetooth, camera, camcorder, etc.
Market-sourced applications (Gmail, Maps, Voice, etc) automatically installed on first boot into /data/app for easy removal.
Bloatware and unnecessary applications removed.
Supported Devices
Desire HD
Desire Z
Desire S
Incredible S
Inspire 4G
myTouch 4G
Porting Information and Credits
Virtuous Unity, or any components therein, may not be ported to other devices without explicit email approval from the development team. We will be approving ports, presuming the develop of a given port is ready and willing to follow the same revision control and release processes currently employed existing devices.
hrk - Allowing use of ghostySMS Vision version.
cypis - For his awesome Unity-banner
robocik - Tips regarding APK compression.
Sybregunne - Virtuous Overclock Controller GUI.
HTC/Google- For building such a good base system.
Important Notes
If you are experiencing random freezes and/or reboots, this is likely due to your device being incapable of handling our overclocking defaults. Download and apply this flashable patch, which will reduce the maximum CPU frequency to 1Ghz and likely eliminate this issue.
You must complete a full wipe prior to installing this ROM the first time. We also recommend wiping between upgrades, but you are welcome to try upgrading without a wipe. However, no support will be provided if you file a bug without having wiped prior to submission.
Bugs and Errors
To ease the process of reporting bugs to the team, we made a public bugtracker where you can report the bugs you found. Please make sure you read all the existing entries there to avoid doubling the errors.
The bugtracker is located here.
Device specific information
Support for the Droid Incredible is in BETA status. Some compromises had to be made to support an older device. This includes disabling of the EBook Reader and using the Sense 2.1 Gallery application. Additionally, the custom kernel for this device is not ready yet, so the OC daemon does not function. Everything else should function normally.
*** SD-EXT PARTITION IS REQUIRED (512MB is fine) ***
Download :: Changelog :: More Information(Official Website of Virtuous ROM)
Reserved for future use.
Also reserved for future use.
I haven't used a sense rom in a while (since your other Virtuous ROM), have been using CM7 ever since. This has me tempted to give sense another try.
SD-Ext.
Noticed on virtuousroms that Ext4 journaling is used. Didn't see a way to upgrade the SD partition to 4 in CMR3.0.08. Will the default work? Also any recommendation on the partition size and do we need to specify a swap file? I am figuring with a 378MB file Dinc will need some help, lotsa help
Been waiting for this. Thanks for not forgetting about us old Inc users.
Sent from my ADR6300 using XDA App
flashing now
Only major issue so far has been weather force-closing so unable to change settings to Farenheit. After it settles for a bit the initial sluggishness improved. Very nice Rom...thank you
mcfarlan said:
Noticed on virtuousroms that Ext4 journaling is used. Didn't see a way to upgrade the SD partition to 4 in CMR3.0.08. Will the default work? Also any recommendation on the partition size and do we need to specify a swap file? I am figuring with a 378MB file Dinc will need some help, lotsa help
Click to expand...
Click to collapse
Take a look inside the rom. It actually has the setup for every phone inside it. So i'd imagine the final rom is around 260-270 for our phone. It also has some ebooks inside and a pretty large theme.
Is there any instructions for the sd-ext part? I've never done that.
Thanks
Sent from my ADR6300 using XDA App
i cant get past white htc screen
anyone know why ?????
Would you guys prefer using /data rather than /sd-ext? It's a fairly easy change. It'll mean less room for Market applications but makes it easier on most people also.
We may also be able to detect whether sd-ext is available and use it if it is, otherwise fall back to data.
rmk40 said:
Would you guys prefer using /data rather than /sd-ext? It's a fairly easy change. It'll mean less room for Market applications but makes it easier on most people also.
We may also be able to detect whether sd-ext is available and use it if it is, otherwise fall back to data.
Click to expand...
Click to collapse
i would say either
with complete instructions
is this why i can only get to the white htc screen????
jdog94 said:
i would say either
with complete instructions
is this why i can only get to the white htc screen????
Click to expand...
Click to collapse
Yes, very likely the reason.
rmk40 said:
Yes, very likely the reason.
Click to expand...
Click to collapse
How do you do the Sd-Ext I want to try this rom.....
Yay! Im going to try asap
rmk40 said:
Would you guys prefer using /data rather than /sd-ext? It's a fairly easy change. It'll mean less room for Market applications but makes it easier on most people also.
We may also be able to detect whether sd-ext is available and use it if it is, otherwise fall back to data.
Click to expand...
Click to collapse
Yes, I rather use /data
stick to SD-EXT
IncredibleDoes said:
stick to SD-EXT
Click to expand...
Click to collapse
Could you guys explain how to do the SD-EXT.. Im already giving up on this rom cuz I can get it to install...?? Thanks
1107963 said:
Could you guys explain how to do the SD-EXT.. Im already giving up on this rom cuz I can get it to install...?? Thanks
Click to expand...
Click to collapse
Clockworkmod recovery lets you partition your SD. Backup SD because it will wipe everything.
Avatar Rom
// RazrHD XT925
// Android 4.1.2
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Attention
Always do a backup before flashing, responsibility lies with the operator of the device ultimately
General Info
Of all the open-sourceish MIUI alternatives this rom wins, It is absolutely fantastic in every regard, I love it.
General Features
-MIUI Security
-MIUI Swipe Keyboard
-MIUI Notes
-MIUI-ish Theme Manager (accessed through CMs themes, requires internet connection to DL and first-time boot)
-MIUI Weather (US only)
-MIUI Status Bar
-MIUI Framework themes
-MIUI Calculator
-MIUI Music
Known Annoyances
- Unknown
- Stock Camera may spout USB related BS, try a 3rd party one
- USB mounting is currently borked but maybe not, some people have no issue with it some do.
Instructions
Do a full wipe and install via the usual method in CWM or touch recovery, whichever you use
Download
3/12/13: AvatarRom
Big thanks to
Specifically every person here that does source work
Waiting patiently for download link
Nice
LG G2X
A few things about this rom, firstly this is a port from a Samsung device, thus it features control panel options not normally found in some CM roms, you MAY need to go to the app store if this has no on-screen navigation buttons.
I have added MIUI apps not normally found to round it off as a MIUI clone, I think this is something you folks will like a lot since your CM10 base is so functional to begin with. : D
To get themes, go to themes in settings like you normally would, It's been replaced with a fully working clone of the MIUI theme manager which can apply themes, and can browse themes online.
you XT925 folks are going to have to inform me of the working status of this in order for progress to happen, if any is needed.
So are the same things that are wrong with CM 10 affecting this ROM too? (i.e. Bluetooth music)?
Have any rogers users tried it yet? does LTE work?
Doesnt work. I used cwm, but stuck in a bootloop
Sent from my XT925 using xda premium
mapleleafz06 said:
Doesnt work. I used cwm, but stuck in a bootloop
Sent from my XT925 using xda premium
Click to expand...
Click to collapse
The same for me. Boot loop every time. I even formatted /system. Erased /data and /cache. Nothing works.
It seems to work, as you can see the start up welcome screen, but before you have a chance to click on the "next" button, the system reboots.
It's an issue with the base, I will upload a working one either tonite or tomorrow.
Ok, for the next revision of this I will need a dedicated tester to confirm the working order before I put a release up, please PM me with some kind of real-time contact info
WORKING BUILD COMIN' TONITE FOLKS. ;o
Working build has arrived!
Can anyone confirm the status of the USB?
Tquetski said:
Can anyone confirm the status of the USB?
Click to expand...
Click to collapse
I can confirm it. I cannot restore my backups because the system cant find an SD. I can write to the internal and external SDs using the built in file manager, but for some strange reason, I cannot write to them using ROM Toolbox, nor any other program. also, for the same reason, I cannot download the Gapps file listed on the update part of the settings.
Thank you for your hard work.
estuardo4 said:
I can confirm it. I cannot restore my backups because the system cant find an SD. I can write to the internal and external SDs using the built in file manager, but for some strange reason, I cannot write to them using ROM Toolbox, nor any other program. also, for the same reason, I cannot download the Gapps file listed on the update part of the settings.
Thank you for your hard work.
Click to expand...
Click to collapse
Don't mess around with any OTA updates or it could mess up your phone; anyway I'm not sure exactly why this is happening, I am going to send a PM to another porter of this rom who is used to Moto Devices and see what they have to say!
Tquetski said:
Can anyone confirm the status of the USB?
Click to expand...
Click to collapse
Thanks for Rom!
Usb works for camera mode (used IP Webcam to stream), but does crash for media, get android.process.media stopped...
Good job man
Sliced by my Razr HD on Tapatalk
Hello Tquetski. Any progress on this ROM? I guess you are really busy now, but I got so frustrated because you ae so close on this one.
I hope you have the time to continue working on this and future ROMs. Your continue support on porting for this phone is really appreciated.
Appreciate it as well. Also same USB problem as previous post about it. Same crash with media but when plugging in the cable or trying to use the gapps I used. Installed twice. First time the crash wouldn't allow adb, second time was with gapps from 20121130 and still crash on cable but adb works. Play store crashes with same media related file but youtube works. Perhaps youtube was already part of the rom....
Am uninstalling for now but can come back to it to test (Not a lot of time of the day for it though, but as much as I can) if you need it.
Also, don't know if it matters but I noticed that symlinks in the ROM don't work as expected, for example sdcard and /mnt/sdcard just return sdcard and /mnt/sdcard when typing ls. putting a trailing slash works, for example /sdcard/
I've noticed some apps rely on /mnt when they look for things.
update from above. Installed gapps from cm site and that went better and the store works. Titanium backups were on external drive and restored fine, as you'de expect. Titanium backup states, upon launch, Media Storage: not mounted but also then displays the correct amount of available storage for it.
So for example it says:
-----------------------------------
Root Acces: ok
Hypershell: yes
...
Media Storage: Not mounted
Backup Directory: /storage/sdcard1/Titanium
Then at the bottom
System Rom: 1.53 gb (1.09 GB Free)
Internal: *looks like the correct amount*
Media: *looks like the correct amount*
Ext. Sd Card: *looks like the correct amount*
-------------------------------------
Internal and Media in the above part are slightly differant than what df at the terminal says but not by much so it seems that Titanium certainly sees the space there in the second part but doesn't see it as the space its supposed to use.
I hope you can fix it. Thanks for getting this far.
One last edit; stock rom behaves the same way with symlinks.
File permissions of mounted internal sd card look the same, from memory, so its not something so simple overlooked at that level.
Happy to have been of no help
Introducing… RaptorSense7
from the...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclaimer
Thanks to all the beta testers who reported the bugs and provided logcats so i can fix them.
Always do a backup, if your alarm fails to go off, or phone doesn't ring or you throw it and break something I am not responsible. Its build off of stock so nothing should go wrong but if it does I will be here to answer any questions.
Introduction
Quote:
LarryBoyG proudly presents his RaptorRom Series.
Installation instructions
Quote:
Instructions:
1. Always make a backup
2. Wipe Dalvik, system and data
3. Install Zip
4. Wait for system to boot, be patient.
Theme Instructions:
Some of the Apps were based on Android 5.0
One of the Apps was the HomePersonalize.apk
To use themes you must
1. Long Press homescreen
2. Select Themes
3. This will take you the wallpaper section of themes
4 to download and apply a whole theme you need to select one of the options from the drop down menu
5. When you find a wallpaper you like, don't download it. scroll all the way down to the bottom and find the asscotiated theme and icon set. download and select apply.
Changelog
Quote:
Code:
Current Changelog 3-27-2015
Update Most Apps to Sense 7
3-23-2015:
Deodexed and Entire Rom for Future Theming.
Zipaligned for better memory management.
Updated Stock Themes.
Integrated all updates into Rom
Rom is based off of 4.4.4 M8 Stable
Added Apps from M8:
Notes
Task Manager
Car Mode
Stocks
Tasks
FM Radio
Added Live Weather Animation
Stock International Icons in Status Bar
FIXED G#&^@&MN PLAY STORE!
2-20-2015
Changelog:
De-Sprinted, Removed Spark UI
De-Bloated, Rom is below 620mb!
Added Quicksettings in pulldown
Fixed boot animations
Works on all Sprint MNVO’s
Added: pattyboi’s Awesome Kernel
Added Leaked M9 wallpaper
Downloads
Quote:
https://drive.google.com/file/d/0B9eZWhO0DB6QdlN2elRjODc5Qjg/view?usp=sharing
XDA:DevDB Information
RaptorRom v2, ROM for the HTC Desire 510
Contributors
LarryBoyG, jdmedeiros, Pattyboi
Source Code: https://drive.google.com/file/d/0B9eZWhO0DB6QdlN2elRjODc5Qjg/view?usp=sharing
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Stock 3.19
Version Information
Status: Stable
Stable Release Date: 2015-03-23
Created 2015-02-20
Last Updated 2015-07-31
Screenshots up soon.
Installing as we speak will update with status. This could very well be the answer to my prayers:laugh::good:
Screenies!
So far so good. Starting with a wiped phone started me out with about 3.6gb / 4gb internal storage which compared to the HTC rom is a pleasent surprise. Im on VM and all is well so far. data,voice, ect ect. not sure what else needs to be tested exactly but if i see something i will let you know.
Can you de-odex it?
I posted too soon. Cannot connect to my Moto 360. I cannot recreate the error that popped up but it was something like HTC service cannot ect something something. i wish i could have gotten a screencap of it. Still though lots of space. Snappy and I really like the included launchers. Must wait though until it supports my watch though. Thanks for the hard work man.
I'll look into it tonight. If you could get a screencap that would be really helpful.
I actually forgot I put the launchers in there, I really wasn't intending to. This thing would be under 600mb if I hadn't.
cm11?
What's different about this rom than cm11? Cameras work? signal? wifi? will this work on the boost variant?
Unxsnt3 said:
What's different about this rom than cm11? Cameras work? signal? wifi? will this work on the boost variant?
Click to expand...
Click to collapse
This isn't AOSP, it works with all the cdma variants. WiFi, cameras work.
Wifi Tether
LarryBoyG said:
This isn't AOSP, it works with all the cdma variants. WiFi, cameras work.
Click to expand...
Click to collapse
I can currently wifi tether with my device and I don't want to lose that capability.
mallamike said:
So far so good. Starting with a wiped phone started me out with about 3.6gb / 4gb internal storage which compared to the HTC rom is a pleasent surprise. Im on VM and all is well so far. data,voice, ect ect. not sure what else needs to be tested exactly but if i see something i will let you know.
Click to expand...
Click to collapse
Does this mean you had 3.6 gb available after installing? If not, how much space on internal storage do you have?
Hope this helps
LarryBoyG said:
Hope this helps
Click to expand...
Click to collapse
It does. Flashed it myself and was sorta depressed to have 0.90gb available. Once I restored my data backup from my own modded stock rom, then proceeded to uninstall all the HTC crap still left in this Rom (a little irritating) I had LITERALLY no more space than on my own revised Rom. Seems the cap on how much space you can have on stock is just a little over 1gb if you don't install anything else. Bummer...
I also don't understand the quick settings bar if we already have a menu with the same functions in the notification bar?
Regardless I see no reason to switch back to my System backup if there's nothing to be gained or lost so I'll stick with it for now
dragonhart6505 said:
It does. Flashed it myself and was sorta depressed to have 0.90gb available. Once I restored my data backup from my own modded stock rom, then proceeded to uninstall all the HTC crap still left in this Rom (a little irritating) I had LITERALLY no more space than on my own revised Rom. Seems the cap on how much space you can have on stock is just a little over 1gb if you don't install anything else. Bummer...
I also don't understand the quick settings bar if we already have a menu with the same functions in the notification bar?
Regardless I see no reason to switch back to my System backup if there's nothing to be gained or lost so I'll stick with it for now
Click to expand...
Click to collapse
I put the quick settings in because I took out a few widgets that did the same thing, to save space. I wanted to keep as close to stock experience as I possibly can. I also did a lot of back end editing. Removing a lot of redundancies that HTC left in. XML code that spent a lot of time going through. I hope that it feels more snappier.
LarryBoyG said:
I put the quick settings in because I took out a few widgets that did the same thing, to save space. I wanted to keep as close to stock experience as I possibly can. I also did a lot of back end editing. Removing a lot of redundancies that HTC left in. XML code that spent a lot of time going through. I hope that it feels more snappier.
Click to expand...
Click to collapse
I removed every widget you left in as I don't use them, though I'm sure others may be. If you don't mind me asking, where did you remove the excess "back-end" stuff? It might seem snappier, I haven't had a chance to try it out too much. I'm a super-gamer and I'll be trying out some of my more intense stuff that usually holds up pretty well with some minor performance stutters. I noticed you added pattyboi's kernel which I was initially suspecting as the cause of the issues I was having performance-wise (not happy with the idle GPU freq) but I'll leave it as is and try to report what I can. I'm a power user/proficient tester, so I should be able to notice the SUPER little things that don't mean much to others. I'll check in later
Alternate Link
Is there an alternate download link for this Rom? I'm eager to try it out as I flashed CM11 and was highly disappointed with the camera and sd card issues. The link provided only pulls up my archive viewer and won't actually download the .zip file. I'm an avid tester, and keep several backups ready, in case I mess up. I would love to help with development as much as possible. Currently running the PattyBoi kernel over stock Rom. Overall quick response, but still no true customization options, even with root. I'd to change my boot animation as well as a few other things. S-Off for this device would be huge as well.
Is it possible to install this rom on a Sprint Pre-paid version, And if i will, Will it unlock the phone to other sim cards?
dragonhart6505 said:
It does. Flashed it myself and was sorta depressed to have 0.90gb available. Once I restored my data backup from my own modded stock rom, then proceeded to uninstall all the HTC crap still left in this Rom (a little irritating) I had LITERALLY no more space than on my own revised Rom. Seems the cap on how much space you can have on stock is just a little over 1gb if you don't install anything else. Bummer...
I also don't understand the quick settings bar if we already have a menu with the same functions in the notification bar?
Regardless I see no reason to switch back to my System backup if there's nothing to be gained or lost so I'll stick with it for now
Click to expand...
Click to collapse
Ill tell you that i actually got it much lower by booting into recovery and wiping the folders that didnt pertain to the OS. ultimately i ended up with 2.97gb/4gb. its really important that you stop it from automatically updating all your apps. and only update the ones you use. for example i think google play books is almost 20 megs... as soon as i get home from work ill get my phone out and do it again and see exactly what i did.