• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

[beta] CyanogenMod 7 [beta]

DIRECTIONS FOR DOWNLOADING:

download with a computer for the best results
then transfer to your sdcard

if you must use your phone to download
then you need to use a better browser than the stock one

**i will NEVER respond to any posts about not being able to download the file, so don't waste your time and just acknowledge that you've done something wrong and fix it**


DIRECTIONS FOR INSTALLING

this is what i suggest, and regardless whether you think it's the best way or not, i suggest you follow my directions

i will not respond to any posts about installation problems

after properly downloading the file and transferring to your sdcard

1) reboot into your recovery

2) make a nandroid of your current system

3) wipe all your user data

4) install the zip

5) reboot the phone and allow the first boot to fully complete

6) unlock the screen

7) open app drawer

8) when all apps load on the screen, use the power button to reboot the phone into recovery

9) when in recovery, do not wipe userdata, do not wipe anything

10) install the zip one more time

11) reboot



​
 
GUIDELINES FOR POSTING PROBLEMS:

IF YOU HAVE EVER HAD TO DO A BATTERY PULL ON YOUR DEVICE, YOU HAVE BAD BLOCKS ON YOUR NAND

BAD BLOCKS ON THE NAND ARE NOT FIXED BY A FORMAT. THESE BAD BLOCKS WILL CAUSE ALL SORTS OF ISSUES WITH THIS ROM

YOU WILL GET PANIC SOFT REBOOTS, FORCE CLOSES, AND A WHOLE HOST OF OTHER PROBLEMS, AND THESE PROBLEMS WILL BE MORE PRONOUNCED IN DEVICES THAT HAVE BEEN ABUSED OVER AND OVER AGAIN


(MOST OF THE ABOVE, IF NOT ALL, HAS BEEN REMEDIED)


WITH THAT BEING SAID, THE ROM HAS BEEN STABLE FOR TWO DAYS ON MY TEST DEVICE AND IS GOOD ENOUGH FOR A DAILY DRIVER IN MY EXPERIENCE--OTHERWISE I WOULD NOT GIVE IT TO YOU

THIS MEANS THAT I DON'T WANT TO HEAR ABOUT EVERY LITTLE PROBLEM YOU HAVE AND I'M NOT GOING TO WASTE MY TIME RESPONDING TO IT, AND NEITHER IS ANYONE ELSE.



!!!ONLY REPORT PROBLEMS THAT CAN NOT BE SOLVED BY THE FOLLOWING DIAGNOSTIC INSTRUCTIONS--THEN AND ONLY THEN REPORT THE PROBLEM!!!



1. ADW LAUNCHER IS UNSTABLE IN THE SMALL AMOUNT OF VIRTUAL MEMORY SPACE AVAILABLE AND WILL FORCE CLOSE AND HANG FROM TIME TO TIME. JUST COMPLETELY REBOOT THE PHONE TO FIX. ADW IS RESPONSIBLE FOR POWER OPTIONS REFUSING TO WORK AT TIMES, SO YOU MIGHT HAVE TO REBOOT BY ADB (preferred) OR JUST A BATTERY PULL IF THIS PROBLEM OCCURS

2. WHEN APPS FORCE CLOSE OR PRODUCE BUGGY BEHAVIOR, REBOOT THE PHONE COMPLETELY AND TRY AGAIN. IF THE PROBLEM PERSISTS, REBOOT AND WIPE DALVIK-CACHE, AND TRY AGAIN. IF THE PROBLEM STILL PERSISTS, REINSTALL AND TRY AGAIN.

3. THE PROBLEMS WITH BLUETOOTH AND WIFI, IF YOU EXPERIENCE ANY, I AM INTERESTED IN, BUT ONLY IF THEY ARE NOT FIXED BY REBOOTING, REBOOTING AND WIPING DALVIK-CACHE, OR REINSTALLING. ONLY THEN REPORT IT

4. THE CAMERA WILL TAKE PICTURES IN LANDSCAPE AND PORTRAIT, BUT IT WILL NOT FLIP THE FINAL PRODUCT. USE THE CAMERA IN LANDSCAPE MODE ELSE YOUR PICTURES WILL BE TURNED. DON'T REPORT IT CAUSE I ALREADY KNOW ABOUT IT. THE CAMERA WILL CAUSE THE SCREEN TO GET STUCK IN LANDSCAPE--SIMPLY LOCK AND UNLOCK THE SCREEN TO RETURN IT TO PORTRAIT MODE, OR JUST TURN OFF AUTO-ROTATION IN DISPLAY SETTINGS.

5. ALL OTHER PROBLEMS: FULLY REBOOT, TRY AGAIN. REBOOT, WIPE DALVIK-CACHE, TRY AGAIN. REBOOT AND REINSTALL, TRY AGAIN. DOESN'T FIX IT? REPORT IT.

6. REPORTING YOUR PROBLEM MEANS TELLING ME PLAINLY, CLEARLY, IN ACCURATE ENGLISH, BRIEFLY, EXACTLY WHAT HAPPENED AND WHAT YOU WERE DOING, EXACTLY, WHEN IT HAPPENED, AND WHETHER YOU CAN DUPLICATE THE PROBLEM EVERY TIME OR NOT. IF THESE GUIDELINES ARE NOT FOLLOWED YOU WILL BE IGNORED. POST YOUR ISSUE IN A RESPONSE HERE, DO NOT PM ME WITH YOUR ISSUES WITH THIS ROM CAUSE I WILL IGNORE YOU.


THANK YOU FOR YOUR COMPLIANCE AND HELP IN DEBUGGING THIS ROM
​
 
crazy...

so many complained for so long about wanting CM7,

and now here it is, and hardly anyone has downloaded it or tried it.

and after many many many many many days and nights and weeks of working on it with every free moment.

crazy
 
Great job with cm7 it is pretty smooth but your aosp build is much more smooth. Been messing with both trying to see which one works better when bogged down with apps and regular use. Cm7 started panic booting every boot, but I credit that to my own use. Thanks again for all your work and every other dev as well who have worked on this device.
 
TrustME90 said:
Great job with cm7 it is pretty smooth but your aosp build is much more smooth. Been messing with both trying to see which one works better when bogged down with apps and regular use. Cm7 started panic booting every boot, but I credit that to my own use. Thanks again for all your work and every other dev as well who have worked on this device.
Click to expand...

thank you.

the most recent upload for CM7 should be just as stable as aosp now. they are both running on the stock kernel's virtual memory split which fixes most of the problems the first few uploads had. you might retry the new download.

i prefer the aosp build though. i was never really a fan of CM to begin with.
 
TrustME90 said:
Any chance for oc on these kernels?
Click to expand...

i haven't implemented it yet on my end.

i don't really plan to use the ahb overclocking configuration from the blade source because it causes sleep of death problems because the frequencies aren't right for the avail/merit.

if i release an overclocking kernel it will be overclocked by default and will not require any change on the user's end; although change will be possible
 
stayboogy said:
crazy...

so many complained for so long about wanting CM7,

and now here it is, and hardly anyone has downloaded it or tried it.

and after many many many many many days and nights and weeks of working on it with every free moment.

crazy
Click to expand...

Some of my friend and me were rejected by the fact about corrupted nand blocks... We did pullotus of our Euro Roamer too many times.
Nevertheless, thank you for this.
 
Stefan Mrsevic said:
Some of my friend and me were rejected by the fact about corrupted nand blocks... We did pullotus of our Euro Roamer too many times.
Nevertheless, thank you for this.
Click to expand...

the rom DOESN'T cause bad blocks

battery pulls do though, and before, not now, the 3gvmsplit kernel reacted negatively to bad blocks causing issues.

using the 2gvmsplit kernel config from the stock kernel fixed those issues though. it's reliably stable in my opinion now.

i still like my aosp build better, and from now onward that is where my attention is going to be focused mainly
 
So .... after the test CM7 we have the following two problems. The first is SMS, the other forced the closure of Google Play, which is not a problem because it solves easily, on the first reboot or clearing your cache.
I'm sorry to be a problem with SMS reappeared, but it's there.
Now, the ROM is fantastic, does everything on it, bluetooth, radio, camera, wifi is very fluid, no chopping, and I think this is definitely the best rom for the roamer.
Maybe there is another problem with calling party does not hear me, but I did not investigate, and probably that resolved.
My roamer is retired, but I am due to the effort that is invested boogie had to try it and report impressions.
Thank you for this rom but frequently a sms that because it will not work in Europe.
 
i've fixed the mic being muted in call.

yet, now the mute button doesn't work... hold works though, but that's not the same as mute.

and it's a problem related to androidhardware.cpp alone from libaudio. somewhere along the line they started adding dual mic configs for mic and non-mic headsets and that screwed the whole thing up. trying to back engineer this at the moment and still leave the code intact. not an easy process.

the main problem is that ZTE use their own vendor specific libaudio source that was built from msm7x30.

compiling msm7x30 libaudio is currently broken though and i can't seem to get it to compile correctly. keeps saying a struct is bad when it looks exact to me...
 
CM7 was just a stepping stone :D.

My thought was that if we can boot the most common custom ROM for a device in the same class as the Merit, then we can work from there for other things.

I'm sticking to my pure AOSP project, but I may use your ROMs occassionally :P
 
You must log in or register to reply here.
Back
Top Bottom