Welcome to CyanogenMod
![]() |
Welcome to our forum. Like most online communities you must register to post, but don't worry this is a simple free process that requires minimal information for you to signup. Be a part of the CyanogenMod Forum by signing in or creating an account. You can even sign in with your Facebook or Twitter account.
|
Is it worth trying CM 7 on the HTCDream
#1
Posted 07 July 2011 - 08:40 PM
#2
Posted 11 July 2011 - 02:30 AM
Sent from my HTC HD2 using tapatalk.
#3
Posted 12 July 2011 - 10:52 PM
Kid A, on 11 July 2011 - 02:30 AM, said:
Sent from my HTC HD2 using tapatalk.
#4
Posted 19 July 2011 - 04:36 PM
not trying to sound like a troll. G/f and I got our respective phones at the same time (mytouch 1.2 for me, and cliq for her), I will say, I was not impressed with her Cliq. Of course, she broke the screen and is now sporting a Mytouch 4G, while I'm still on my older mytouch 1.2....
#5
Posted 20 July 2011 - 01:14 AM
I tried going back to CM6.1 and THEN I was disappointed.
Try it yourself, it isn't so hard... Backup your current rom, flash a new one. If you don't like it, revert.
good luck!
ps.: I have a MT3G 32A, not a dream, but it's basically the same thing.
#6
Posted 23 July 2011 - 12:21 PM
The recommendation for CM7 on the Dream is New Radio 2.22.28.07 OR 2.22.25.28 & SPL 1.13.0013d but I happen to be sporting SPL 1.13.0013d with Radio: 2.22.27.08. Am I safe with that radio? I am just being careful after what happened to my last Dream (lol).
#7
Posted 23 July 2011 - 09:46 PM
1)Root using superoneclick or any other method (I used soc and it took 30 seconds).
2)Install Titanium Backup and backup all your user apps
3)Install Rom Manager and use it to install Clockwork Recovery (you'll have to do it every time you boot until you flash a new rom IIRC)
4)Backup your sdcard and create an EXT4 partition using rom manager (which made my quadrant reach 500 points)
5)Download Osahka Super Wipe and flash it through Clockwork Recovery (it'll erase all that's necessary for a new rom, but not your sdcard).
6)Use Rom Manager to flash cos-ds (or do it straight with clockwork recovery)
7)Configure your brand new rom
7)Restore user apps with titanium.
You're set!
My phone is basically the same as yours, cos-ds supports our radios and spl.
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO-2.22.28.25
#8
Posted 09 September 2011 - 12:23 AM
I'm glad I did!
#9
Posted 10 September 2011 - 06:03 PM
#10
Posted 10 September 2011 - 10:13 PM
#11
Posted 12 September 2011 - 07:28 AM
#12
Posted 16 December 2011 - 04:36 PM
The problem I am having is that even though I compiled and build CM7.2 from source I cannot install it - apparently I need to have a newer bootloader (1.33.xxxx) and (possibly) a new radio.
I currently have HBOOT 1.33.2005 and my radio is 2.22.19.26I, so despite my searches I cannot find how to upgrade these (if indeed an upgrade is possible without bricking the phone).
#13
Posted 20 December 2011 - 04:06 PM
Hboot-1.33.0013d
Radio-2.22.28.25
http://forum.cyanoge...r-new-radiospl/
http://forum.cyanoge...stion-and-help/ This link is what I used...
http://forum.xda-dev...790#post9055790
Here's some gingerbread roms for G1
http://forum.xda-dev...ad.php?t=882356 ezterry's EzGingerbread rocks
native support for Apps2SDext
http://dl.dropbox.co...1s7m/index.html
http://forum.xda-dev...ad.php?t=932118
http://forum.xda-dev...d.php?t=1100710
http://forum.xda-dev...ad.php?t=950765
not much development for G1 other than ezterry
good luck
Edited by mrnsx2008, 20 December 2011 - 04:27 PM.
#14
Posted 22 December 2011 - 11:49 PM
I've done my radio upgrades - flawless!
I've since installed CM7.2 on my G1 - almost flawless!
The CM7.2 gingerbread kernel is buggered, so I had to use the newest kernel from ezterry, then it all worked out.
I am now in a process of cleansing stuff from /system/app.
One thing I still find very annoying though - CM7.2 seems unable to "recognise" my ext2/3/4 partition for installing apps - the partition is successfully mounted at boot (as /sd-ext), but I seem unable to install anything on it - I could use it from the File explorer and the terminal, but that's about it.
The Amon_RA recovery (the cyan version) also seems unable to recognise my ext2/3/4 partition and insists on having a fat one to place my backups/updates on.
Last, but not least - after applying ezterry's radio updates I seem to have lost my IMEI, IMEI SV and Baseband settings! How do I get to restore these (or get new ones, if that's legal)?
#15
Posted 23 December 2011 - 05:59 AM
I've created 3 *.bat files for apps backup, uninstall and install...
adb remount
adb pull /system/app/Gallery3D.apk
adb pull /system/app/Launcher2.apk
adb remount
adb shell rm -f /system/app/BooksPhone.apk
adb uninstall com.google.android.apps.books
adb shell rm -f /system/app/CarHomeGoogle.apk
adb uninstall com.google.android.carhome
adb shell rm -f /system/app/CarHomeLauncher.apk
adb uninstall com.android.cardock
adb shell rm -f /system/app/CMStats.apk
adb uninstall com.cyanogenmod.stats
adb shell rm -f /system/app/Development.apk
adb uninstall com.android.development
adb shell rm -f /system/app/DSPManager.apk
adb uninstall com.bel.android.dspmanager
adb shell rm -f /system/app/FileManager.apk
adb uninstall org.openintents.filemanager
adb shell rm -f /system/app/Gallery3D.apk
adb uninstall com.cooliris.media
adb shell rm -f /system/app/GenieWidget.apk
adb uninstall com.google.android.apps.genie.geniewidget
adb shell rm -f /system/app/GoogleQuickSearchBox.apk
adb uninstall com.google.android.googlequicksearchbox
adb shell rm -f /system/app/kickback.apk
adb uninstall com.google.android.marvin.kickback
adb shell rm -f /system/app/Launcher2.apk
adb uninstall com.android.launcher
adb shell rm -f /system/app/LiveWallpapersPicker.apk
adb uninstall com.android.wallpaper.livepicker
adb shell rm -f /system/app/OpenWnn.apk
adb uninstall jp.co.omronsoft.OpenWnn
adb shell rm -f /system/app/Protips.apk
adb uninstall com.android.protips
adb shell rm -f /system/app/QuickSearchBox.apk
adb uninstall com.android.quicksearchbox
adb shell rm -f /system/app/soundback.apk
adb uninstall com.google.android.marvin.soundback
adb shell rm -f /system/app/SoundRecorder.apk
adb uninstall com.android.soundrecorder
adb shell rm -f /system/app/SpareParts.apk
adb uninstall com.android.spare_parts
adb shell rm -f /system/app/SpeechRecorder.apk
adb uninstall com.android.speechrecorder
adb shell rm -f /system/app/talkback.apk
adb uninstall com.google.android.marvin.talkback
adb shell rm -f /system/app/VoiceDialer.apk
adb uninstall com.android.voicedialer
adb shell rm -f /system/app/VoiceSearch.apk
adb uninstall com.google.android.voicesearch
adb remount
adb install Gallery3D.apk
adb install Launcher2.apk
In place of Gallery3D, I install QuickPic from Market
In place of default launcher, I stall Zeam Launcher from Market
2.
use ext4?
https://market.andro...d=ru.krikun.s2e easy
Firerat's a2sdext magpie
http://forum.cyanoge...ude-apkmanager/
http://forum.cyanoge...pie-2010-12-07/
http://forum.xda-dev...ad.php?t=679572
3.
to my knowledge all the flash files has to be in the root of the SD card /sdcard for both
Amon_Ra recovery 1.7.0
ClockworkMod Recovery v4.0.0.5 http://www.multiupload.com/UHW7UTGF9O
recovery-clockwork-2.5.0.7-dream.img
4.
Boot into Bootloader and double check if it shows Hboot-1.33.0013d Radio-2.22.28.25 S-On
Try out the sim card on another phone first
if you believe its the radio affecting the IMEI... maybe you can try switching to Radios 2.22.27.08
you should try xda forum...
hope this helps
Edited by mrnsx2008, 23 December 2011 - 06:01 AM.
#16
Posted 23 December 2011 - 04:21 PM
The guide I found on the CM wiki (Barebones setup - http://wiki.cyanogen.../wiki/Barebones) indicates that in order to uninstall a package I simply need to delete the .apk file from /system/app or /data/app and the PackageManager will do the rest on reboot.
Indeed, that seems to be the case - according to the logs all "dangling" permissions and "data" are swiftly removed. Still, do I need to use "adb unistall" in this case?
As for a2sdext - I haven't decided which one to download yet (the Russian .apk explicitly states that it is for CM7, while FireRat's version seems to do the job/setup and can be applied for any future CM version), so tough to decide which one to use.
Another question related to this, possibly covering the Amon_RA issue I have - ideally, I'd like to get rid of the fat partition completely.
In other words "replace" mmcblk0p1's file system (i.e. /sdcard) from fat to ext4. I remember when I tried that Amon_RA and it didn't like it (all of the update zip files were in /sdcard, but the file system was ext4). Same goes for my CM7.2 setup - it couldn't "recognise" the card (though I think if I install any of the above packages that might change, right?).
So I am not sure I could replace fat with ext4 completely - I might be wrong though!
When I go into fastboot mode (back+power) I see the following:
DREAM PVT 32B SHIP S-ON
HBOOT-1.33.0013d (DREA11000)
CPLD-4
RADIO-2.22.28.25
So I presume I've got the latest (and greatest) available from ezterry, right?
One other thing I forgot to mention in my previous reply - I've also applied ezterry's GPRS Patch (http://sandbox.devnu...prs_patch_S.zip), so don't know if that is what caused me to loose my IMEI settings.
Lastly about the xda forum - I am already registered there, but they have this nazi-style rule that you can't post in any of the dev forums unless you clock up at least 10 posts and a moderator then need to "approve" you for posting in these forums. Quite pathetic really!
As most of my queries are dev-related, at present I am stuck!
#17
Posted 24 December 2011 - 08:56 AM
"adb uninstall" is not necessary I just use it for Precautionary measures. no worries
2.
I would use cm7 supported *.apk just to keep it simple until I start having issues.
3.
ahh the age old question "to ext or not ext?"
Until google/android/developers design roms's exclusively to run on ext...
It's just not convenient due to lack of support for non-linux systems for now.
That having said, I'm pretty sure ClockworkMod Recovery v4.0.0.5 supports ext4 but G1 doesn't like it due to lack of memory so make sure you backup everything before you do anything
4.
"Most users will experience better mobile network rates if they flash and choose yes, however if you run into problems SIMPLEY RE-FLASH CHOOSING NO to revert to the ezGingerbread defaults"
5.
http://forum.xda-dev...ad.php?t=959240
perhaps you can send private message directly and/or ask to post the questions for you...
Happy holidays
Edited by mrnsx2008, 24 December 2011 - 09:04 AM.
#18
Posted 24 December 2011 - 02:02 PM
I will postpone the ext4 upgrade for now as I am tackling a bigger issue which I need to sort out first and that is to learn how to build a single .apk without rebuilding the whole CM7.2 image - I must find this out as I need to upgrade iptables (and most of the Netfilter stack) and bring it up to a more "decent" level as it is now.
I've spend a good few hours studying the Android iptables port and to say that I am unimpressed would be an understatement!
For some bizarre reason iptables-save/-restore has been scrapped completely from Android/CM distribution, which means that I cannot build my firewall using a single-file restore, but have to do it by executing iptables for each statement.
Either that, or compile a proper (understand Linux) iptables executable - statically linked - and use that instead (at the moment I am inclined to go for the latter option).
After what I have seen in the iptables code, I am no longer convinced that the Netfilter stack in the Android kernel is "pristine" (understand pure Linux) and I fear that I will have an uphill struggle to use "standard" Linux iptools to manipulate my firewall the way I want - I hope I am wrong!
I was hoping to introduce some of my Netfilter developments into the Android/CM world, but the road might be a bit bumpy and not as easier as I thought initially!
I am facing a similar problem with wpa_supplicant - the version supplied with CM7.2/Android is 0.5.11, the latest release which I have used for quite a while is 0.7.3. From what I've seen during my (admittedly very short) google search I am in for a nasty surprise there as well.
Anyway, that's for another day - Christmas eve is upon us, so I am going to enjoy the occasion. Happy Christmas, have a good one and enjoy it!
#19
Posted 17 January 2012 - 08:37 AM



















