[ROM] CyanogenMod 7.0.3 ALPHA3 - 5/11/11

Search This thread

rion_j

Senior Member
Aug 23, 2010
213
17
Jt, can we use cm7 themes for this or are themes rom specific similar to your cm6 build?
 

Whitepaint

Senior Member
Feb 24, 2010
162
1
After flashing and playing around I attempted to flash back to TW EC01 with nandroid and it bootloops at boot screen. I then Odined back to DL09 stock everything and worked back up. still cant boot anything.
 

adambobbyburgers

Senior Member
Dec 24, 2009
144
4
Texas
Just updated to the 4/21 version, and just like its predecessor, it hangs at the backup and restore section of the setup. I've taken a logcat, can be found right chyuhh: http://pastebin.com/v8nuWG1v (hopefully i did it correctly...) It's been going for about 15 minutes, so I think it's time for a battery pull. Hopefully this logcat helps. Thanks again for your continuous support!

Edit: so after a battery pull, the backup/restore part of the setup took less than a minute (second boot).
 
Last edited:

s44

Senior Member
Sep 25, 2010
1,142
191
Am I correct that this is the previous-style hack on our .32 and not a full build on .35 from the i9000 CM7 source? The latter has a *lot* working (basically everything, including video and camcorder -- helped by new GB video drivers!), but obviously radio is an issue for us.

Was PK doing the .35 CDMA-ification or this sort of .32 hack?
 

jt1134

Inactive Recognized Developer
May 8, 2010
1,098
3,151
Am I correct that this is the previous-style hack on our .32 and not a full build on .35 from the i9000 CM7 source? The latter has a *lot* working (basically everything, including video and camcorder -- helped by new GB video drivers!), but obviously radio is an issue for us.

Was PK doing the .35 CDMA-ification or this sort of .32 hack?

32 all the way. At this point 35 is a pipe dream

Sent from my SCH-I500 using XDA App
 
  • Like
Reactions: zerofighter1

tkdboi

Senior Member
Jul 10, 2010
65
2
New York
im pretty sure adrynalyn and JT working together we're gonna get a fully functional CM7 before we know it!

(except adryn is mostly on T-bolt forum now T.T)
 
Last edited:

tkdboi

Senior Member
Jul 10, 2010
65
2
New York
After flashing and playing around I attempted to flash back to TW EC01 with nandroid and it bootloops at boot screen. I then Odined back to DL09 stock everything and worked back up. still cant boot anything.

did you flash a TW kernel before you did a nandroid restore?

try these steps:

1. clear cache.
2. clear dalvik cache.
3. flash compatible kernel (TW, AOSP, CM7).
4. nandroid restore.
 

AlexDeGruven

Senior Member
Mar 24, 2008
685
213
Ann Arbor
www.structuredthought.org
Unfortunately, I need my camera and camcorder, so I'm going to have to flash back to ED01 today.

That's not to say I didn't have a ton of fun dickwaving yesterday (there are 5 or 6 of us on our floor with SGS devices).

Can't wait to see what happens when some usable .35 source drops.
 

zeroxg4

Senior Member
Nov 8, 2009
594
93
For some reason Root Explorer doesn't display anything, just a black screen. On the other hand, the File Manager that comes with this will display files (except for the contents of data/), but can't be used to r/w. Is this known or am I missing something?
 

bdemartino

Senior Member
Jan 18, 2011
873
191
Midwest
For some reason Root Explorer doesn't display anything, just a black screen. On the other hand, the File Manager that comes with this will display files (except for the contents of data/), but can't be used to r/w. Is this known or am I missing something?

Super user is causing issues, if you flash the CM7 OTB kernel that nemesis put out, it will fix QTadb and root explorer issues.
 

kidserious

Senior Member
Feb 11, 2011
979
238
Super user is causing issues, if you flash the CM7 OTB kernel that nemesis put out, it will fix QTadb and root explorer issues.

I can confirm that flashing nemesis's kernel fixed root explorer for me (because of the su package that he added in). Thanks Nemesis!

Sent from my SCH-I500 using XDA Premium App
 

DirgeExtinction

Senior Member
Sep 24, 2010
2,055
324
Punk.Kaos has been sick; hence why he hasn't been that active lately.

Sent from my SCH-I500 using XDA App
 

bdemartino

Senior Member
Jan 18, 2011
873
191
Midwest
Its ****ing gingerbread of course its worth flashing :) the only con compared to CM6 is the camera

Sent from my SCH-I500 using XDA Premium App
 

jt1134

Inactive Recognized Developer
May 8, 2010
1,098
3,151
JT: Titanium Backup FCs after getting sudo for me. Gonna try and re-flash.

http://pastebin.com/zGTAU2Di

No dice. Oh well. Looks good!

Looks like your titanium install is corrupt. It's missing one of its data files.

Code:
W/System.err( 3171): java.io.FileNotFoundException: /data/data/com.keramidas.TitaniumBackup/shared_prefs/filter_default.bin (No such file or directory)
 
Last edited:

suppliesidejesus

Senior Member
Apr 1, 2010
609
117
Looks like your titanium install is corrupt. It's missing one of its data files.

Sent from my SCH-I500 using XDA App

That is unfortunate, because I wiped and re-installed CM7 and then installed TiBu from the Market again and it did the exact same thing. If I try again, I'll get the apk from their website and see if that works. Thanks for looking into it.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 100
    Got bored again, this time I merged my device tree and fixes into CM7 Gingerbread :D ROM is built from the newest CM7 source code, and has been merged with the majority of my device specific fixes from previous ROMs. I love open source, so of course source code is available for everything, here (ROM), here (kernel), and here (initramfs). If you would like to follow the changes I make, check my github rss feed here.

    *** WORKING ***
    RIL (calls/sms/3g data)
    WiFi
    GPS
    sdcard and USB mass storage
    rotation and proximity sensors
    screen on/off animation :cool:
    haptic feedback

    *** NOT WORKING ***
    Camera/Camcorder
    MMS
    BT
    most video codecs - Youtube playback (LQ & HQ) is broken for example - youtube does work from a browser if you use a desktop user-agent
    Voodoo lagfix conversions


    There are still plenty of bugs! and there likely will be until we have a true GB leak or official release to work off of.

    PLEASE READ
    It is considerably difficult for me to stumble upon every issue out there, and even more difficult to narrow these issues down, let alone fix them. That said, PLEASE do not clutter this thread with "thank you" or "X/Y/Z doesn't work" or "I'd love to flash this if..." type posts. I APPRECIATE THE THANKS AND THE FEEDBACK!!! Don't get me wrong. But these posts are not at all helpful in moving this ROM forward, and simply add more clutter to the forum. If you make such a post, don't expect a response.

    If you experience a bug, PLEASE GET LOGS! I can't fix something simply by knowing that it does not work. A bug report without significant details is a useless post, it just is what it is. Logs help identify the code affected, and thereby help facilitate the fixes that we all love. PLEASE share your issues if you can provide helpful data in fixing them
    THANKS FOR READING :)


    The ROM package currently includes the base CM7 ROM, and a compatible kernel. Flash gapps from the package linked below. DO NOT FLASH ANY OTHER GAPPS OR KERNEL PACKAGES! The ROM package uses edify scripting, so it is flashable with any iteration of ClockworkMod recovery.

    ALSO: devs and noobs alike please take notice : this ROM uses ClockworkMod recovery 3.x. I will no longer be supporting older recoveries!

    Much thanks to the EpicCM and teamhacksung folks for code and ideas, and of course props to the CM team for all they do, it's their ROM after all.

    If you appreciate the time and effort I have put into this ROM please click the "Thanks" or "Donate" buttons. Either one is fine by me :)


    ***** Update 4/26 - ALPHA2 *****
    fixed USB mass storage
    fixed haptic feedback
    fixed TiBu 'whoami' bug
    update to 3.x ClockworkMod recovery
    sync'd with latest CM code
    updated to latest Market
    stubbed the camera (yes, I know it takes pictures of nothing but a green android :rolleyes:)
    ** package still includes gapps and kernel **
    ** changed to new kernel that can be used with BOTH rfs AND ext4 - but it does not include the Voodoo lagfix code, so no conversions! **
    ** Make sure to wipe data even if coming from the previous alpha! **

    ***** Update 5/11 - ALPHA3 *****
    updated to latest CM7 code (7.0.3)
    enabled recent CM code to prevent "ring only once" bug (lightly tested)
    made one of my sms hacks "optional" for easy editing by the mesmerize/showcase users (simply remove "ro.sms.padding=1" from build.prop to fix sms on these devices)
    fixed some memory settings in kernel - should fix the lag experienced when using previous versions
    added other tweaks to kernel for speed improvement (increased sdcard readahead cache/lowmemkiller/etc)
    included punk-kaos' recent camera changes into kernel (cam not working, but getting there)
    unstubbed camera (no more pics of a green android :p)
    cleaned up my build tree a bit for a smaller download for people building themselves
    removed gapps from ROM package, download from link below (kernel still included in ROM package)
    ROM package will no longer flash a recovery
    switched to bmlwrite for flashing kernel (screen will no longer wig out during kernel flashes)

    Instructions:
    flash with Clockwordmod recovery
    flash ROM first then flash gapps package
    WIPE DATA! if coming from ANY other ROM
    Don't worry about disabling lagfix or any of that nonsense, ROM will work whether you are using ext4 or rfs


    ALPHA3
    http://www.mediafire.com/?ziawa7ot8dhdq4k

    GAPPS
    http://www.mediafire.com/?ogylu5w024148lt

    Enjoy and remember: If your phone breaks after flashing, YOU broke it! Not ME!
    10
    As do I, which is why I haven't set it as my daily driver yet. I've been using jt's stuff since super clean; he and kaos well definitely get the camera working.

    KangBanging since day one!
    CommRom 1.3
    OTB 1.4
    OC'd (stable) 1200 mhz
    ED03
    Tapatalked!

    Got camera and camcorder working last night ;) It's on a completely new build, based on the mainline code so we lost radio :(

    Hope to have a much more functional build soon.

    Sent from my SCH-I500 using XDA App
    3
    jt,

    I was building your stuff just now and these cyanogen commits from tonight gave me some errors.

    https://github.com/CyanogenMod/andr...mmit/a400a9ae85ea24a1fe307a437f20d55efe453168
    https://github.com/CyanogenMod/andr...mmit/f4c5fbac0b2dcc19749c7f37285d553149957e1a

    I just re-synced, using the prior revision in the manifest. That got me around it for now, waiting for the rest of the build to finish. When you merge changes for frameworks/base in your tree it will get rid of the errors.

    I was also wondering how to go about removing the recovery from the zip for the build (and possibly the kernel as well). I know I can manually remove them from the zip after it's made, but I'd rather do it properly if I can. I was fighting with device/samsung/fascinate/BoardConfig.mk for awhile but it seemed like whenever I settled on a change the build would explode.

    manifest got behind due to mainline cm changes. fixed it.

    hopefully won't be doing it this way much longer, working on getting stuff merged into mainline :D
    3
    i love this rrom , are we going to see any new updates? i understand if we arent going. to , but just checking up if this gets mms capabilities, i will use it for tue rest of my life

    My entire town has been without power for the last week due to the recent mass tornadoes in the southeast. Updates will be coming along as time and other factors permit.

    Sent from my SCH-I500 using XDA App
    1
    This may peg my level of knowledge but here goes. . .What logs would be most beneficial? Assuming alogcat is the standard method, there are a lot of different options of logs in there. Any specific ones that would be the most helpful in tracking down a bug?

    Not trying to clutter, hopefully avoiding more in the future :D

    any random bugs can usually be picked up from the main log. anything having to do with the radio (call issues/sms issues/etc) need the radio specific log

    I'm not familiar with alogcat (market app right?), but the logs can be dumped using adb from a pc. ex:

    adb logcat > logcat.txt
    will dump the main log

    adb logcat -b radio > radio.txt
    will dump the radio log

    thank you for your concern :)