[ROM][GEN2]CyanogenMod 7 (Android 2.3.7)

[Guest targetbsp]

i tried that and it worked once or twice for a call, but after that it was stuck on black screen.

Yeah. I'm classing them as 2 different things. :D

The proximity doesn't work at all unless you calibrate it.

Then it only works right at the beginning of a call before it goes to sleep.

So yeah, there's not any great benefit in calibrating it right now but presumably it'll need done in the medium to long term anyway once the wakelock is added back.

Okay so i've barely followed this thread, for idk a month. The blade wiki says N175+ for GPS fix, im still running n148 not too bothered about the GPS fix didn't use GPS and someone posted the LED worked 6 pages ago, I didn't read them all.

Can someone suggest the best to use performance wise. Battery life isn't the issue. I'm guess what im asking is should I install the latest nightly?

LED notification does NOT work. It's returning at some point in the future.There's no substantial difference performance or battery wise between the version you're on and the latest nightly.

Edited September 10, 2011 by targetbsp

[Guest targetbsp]

Has no one an idea what happen with 179+ ?

I can't get LBE security to work :huh::unsure:

Doesn't work for me on the new kernel version either. Errors after getting root.

That functionality is built into CM7 anyway...

Edited September 10, 2011 by targetbsp

[Guest]

Doesn't work for me on the new kernel version either. Errors after getting root.

That functionality is built into CM7 anyway...

Yeah i know that CM7 has this functionality too.

But with the App i think it's more comfortable. But i ask from the normal 179+ without the new kernel.

Edited September 10, 2011 by Guest

[Guest CaptainSpectacular]

All's working great here with the n179+ with new kernel, except the proximity sensor during call with black screen and semi-working.

[Guest sej7278]

Yeah i know that CM7 has this functionality too.

But with the App i think it's more comfortable. But i ask from the normal 179+ without the new kernel.

looking at the number of bug reports in google, i'd say its a bug with the app, its not even cm7 or blade-specific!

does it even work with the official n179? if not, you're reporting the bug to the wrong people.

[Guest The_Knife]

you did remove the image directory from the sdcard after doing the TPT?

did the TPT actually run - its reboots into recovery 3027 after printing some coloured text?

did you unpack the TPT using winzip or 7zip - not that shite "compressed folders" microsoft bundle with windows?

I haven't removed the image directory. Why do you ask?

Yes, the TPT ran. Green text. Mr Pigfish say i have a Gen2 model. I've previously used the TPT with RC1 built in and a 140 MiB system partition. As you can see from my list of steps the system partition increased to 160 MiB when I ran Gen1-to-Gen2-TPT-v8-custom.zip. I used 7-zip to uncompress directly to the phone. I then ran Android File Verifier to check nandroid.md5 in the image directory and it reported 17 files checked.

if you've already done the v8 TPT which 710rc1 are you using - not the one with the TPT in it?

I used update-cm-7.1.0-RC1-Blade-signed.zip. It worked perfectly as opposed to the nightlies.

when you boot you're not holding down vol- or anything are you, as that will enter fastboot which just sits at the green android.

No, not holding anything but the power button. Holding vol+ or vol- would run TPT or clockwork.

Thanks for trying to help. Any other ideas?

Edited September 10, 2011 by The_Knife

[Guest sej7278]

I haven't removed the image directory. Why do you ask?

you should do as per the instructions, otherwise it could cause the phone to re-tpt accidently (shouldn't cause any harm i guess really).

no idea why the old RC1 should work and not the newer nightlies, that's just odd if you're gen2 now.

have you tried any other roms like ginger stirfry or my my cm7 test build with tom_g's 2.6.35 kernel in (download link in my sig below)?

Edited September 10, 2011 by sej7278

[Guest targetbsp]

looking at the number of bug reports in google, i'd say its a bug with the app, its not even cm7 or blade-specific!

It is also worth noting that the error message the app gives says to report the error to the app developer. :)

[Guest The_Knife]

no idea why the old RC1 should work and not the newer nightlies, that's just odd if you're gen2 now.

have you tried any other roms like ginger stirfry or my my cm7 test build with tom_g's 2.6.35 kernel in (download link in my sig below)?

Very odd indeed. Ginger Stir Fry beta 21 worked fine. I haven't tried 2.6.35.

Is there any way to debug boot failures like this? Is it possible to build a ROM that prints out debug messages while booting instead of just displaying the boot image for example?

[Guest Richard_Arkless]

Very odd indeed. Ginger Stir Fry beta 21 worked fine. I haven't tried 2.6.35.

Is there any way to debug boot failures like this? Is it possible to build a ROM that prints out debug messages while booting instead of just displaying the boot image for example?

I think you can download the android sdk, connect the phone to the pc and run adb logcat in a terminal/command line, that will display what the phone is currently doing and what its getting stuck on, for more information look at this page https://developer.android.com/guide/developing/tools/logcat.html

Edited September 10, 2011 by Richard_Arkless

[Guest Tom G]

Very odd indeed. Ginger Stir Fry beta 21 worked fine. I haven't tried 2.6.35.

Is there any way to debug boot failures like this? Is it possible to build a ROM that prints out debug messages while booting instead of just displaying the boot image for example?

It depends how far its getting in the boot process. The boot animation starts fairly early, so there's a good chance adb wont be started. If adb is started then you should be able to run

adb logcat

for android logs and

adb shell dmesg 

  or

adb shell cat /proc/kmsg

for linux kernel output.

Does it reboot if you unplug the usb cable while its sitting at the green android screen? if so after it reboots, boot into recovery (without powering off the phone) and run 'adb shell cat /proc/last_kmsg'

[Guest The_Knife]

The boot animation starts fairly early, so there's a good chance adb wont be started.

adb can't find the phone, although Android ADB Interface (USB\VID_19D2&PID_1354\Blade-CM7) shows up in device manager. An inaccessible mass storage device also shows up.

Does it reboot if you unplug the usb cable while its sitting at the green android screen? if so after it reboots, boot into recovery (without powering off the phone) and run 'adb shell cat /proc/last_kmsg'

Yes! last_kmsg has these interesting lines in it:

[01-01 00:00:00.858040] [1: swapper]rootfs image is not initramfs (junk in compressed archive); looks like an initrd

...

[09-10 16:45:37.500000] [1: swapper]RAMDISK: Couldn't find valid RAM disk image starting at 0.

[09-10 16:45:37.507136] [1: swapper]VFS: Cannot open root device "<NULL>" or unknown-block(0,255)

[09-10 16:45:37.507136] [1: swapper]Please append a correct "root=" boot option; here are the available partitions:

...

[09-10 16:45:37.507136] [1: swapper]Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,255)

Edit: Log uploaded.

Edited September 10, 2011 by The_Knife

[Guest Anil K Solanki]

I think you can download the android sdk, connect the phone to the pc and run adb logcat in a terminal/command line, that will display what the phone is currently doing and what its getting stuck on, for more information look at this page https://developer.an...ols/logcat.html

Hi Richard, this is purely an observation, but, do you realise your signature is HUGE! It's 5 times bigger than your posted reply and way bigger than the average reply/question.

It is pretty though.

Anil.

EDIT. Screen shot added for dramatic effect.

Edited September 11, 2011 by Anil K Solanki

[Guest mullen666]

<br />Hi Richard, this is purely an observation, but, do you realise your signature is HUGE! It's 5 times bigger than your posted reply and way bigger than the average reply/question.<br /><br />It is pretty though.<br /><br />Anil.<br /><br />EDIT. Screen shot added for dramatic effect.<br /><br /><img src="http://www.thisiswhatwedo.com/fileshuttle/hugesig_2691.gif" /><br />

<br /><br /><br />

Anil I thougt you'd gone?

Nice to see you back.

I haven't posted for a while

Lots of stuff going on

watching the .35 kernel developments with interest

Also lots of arguments regarding source code etc

New Nightlies thread? I don't think so

Seems to be abit of a silly thing as it just fragments the thread.

Anyway, great to see the balde forums still going strong

[Guest olol]

hi, guys, I am newbie

I have a v880, the Chinese version of the Blade ，256mb ram only

Here is hardware detection information by enter “*983*24474636#”

LCD Information:(here show me nothing, i don't know why)

)

TouchScreen Information:

touchscreen module

name :FocalTech

i2c addresss :0x3e

IC type :FT5X06

moudule:FocalTech :FT5X06

WIFI Information:

Device manufacturing:Atheros

Model Number:AR6002

BT Information:

BTS4025

Camera Information:

ID:0x2682

Nmae:MT9T112-3.0Mp-AF

Flash Information:

SAMSUNG 4G NAND

I heard some version mkae lcd black or reboot...

My question is which version of the rom i can use?

Edited September 11, 2011 by olol

[Guest tsddave]

hi, guys, I am newbie

I have a v880, the Chinese version of the Blade ，256mb ram only

Here is hardware detection information by enter “*983*24474636#”

LCD Information:(here show me nothing, i don't know why)

)

TouchScreen Information:

touchscreen module

name :FocalTech

i2c addresss :0x3e

IC type :FT5X06

moudule:FocalTech :FT5X06

WIFI Information:

Device manufacturing:Atheros

Model Number:AR6002

BT Information:

BTS4025

Camera Information:

ID:0x2682

Nmae:MT9T112-3.0Mp-AF

Flash Information:

SAMSUNG 4G NAND

I heard some version mkae lcd black or reboot...

My question is which version of the rom i can use?

An internet search revealed that your phone is the same as a San francisco which is the zte blade rebadged for the UK market.

I have one myself but my phone has 512mb. Maybe you have 512mb but need to unlock it.See this forum for that info.

I have been able to use any rom on the forum on my phone as if the website I saw is correct ,then so should you.

Here is the link I found http://www.modem3g.c...-v880-p-82.html

Before you install any rom then you should download clockworkmod and backup what you have.That way if anything goes wrong you can easily go back to where you are now.

Edited September 11, 2011 by tsddave

[Guest Anil K Solanki]

<br /><br /><br />

Anil I thougt you'd gone?

Nice to see you back.

I haven't posted for a while

Lots of stuff going on

watching the .35 kernel developments with interest

Also lots of arguments regarding source code etc

New Nightlies thread? I don't think so

Seems to be abit of a silly thing as it just fragments the thread.

Anyway, great to see the balde forums still going strong

Hi mullen666, I have given my Blade to my girlfriend, I only poped in, to hit the "stop watching" button & well, one thing led to another. I saw Mr. Arkless' humonguos signature & I had to say something, other than, "wipe that cache".

Bye forever & ever. It's been a pleasure. Anil.

[Guest Tom G]

hi, guys, I am newbie

I have a v880, the Chinese version of the Blade ，256mb ram only

Here is hardware detection information by enter “*983*24474636#”

LCD Information:(here show me nothing, i don't know why)

)

TouchScreen Information:

touchscreen module

name :FocalTech

i2c addresss :0x3e

IC type :FT5X06

moudule:FocalTech :FT5X06

WIFI Information:

Device manufacturing:Atheros

Model Number:AR6002

BT Information:

BTS4025

Camera Information:

ID:0x2682

Nmae:MT9T112-3.0Mp-AF

Flash Information:

SAMSUNG 4G NAND

I heard some version mkae lcd black or reboot...

My question is which version of the rom i can use?

An internet search revealed that your phone is the same as a San francisco which is the zte blade rebadged for the UK market.

I have one myself but my phone has 512mb. Maybe you have 512mb but need to unlock it.See this forum for that info.

I have been able to use any rom on the forum on my phone as if the website I saw is correct ,then so should you.

Here is the link I found http://www.modem3g.c...-v880-p-82.html

Before you install any rom then you should download clockworkmod and backup what you have.That way if anything goes wrong you can easily go back to where you are now.

The v880s only have 256MB RAM, there isn't any more to unlock.

The recent v880s have some hardware changes that have not been seen in European models yet. Recent CM7 nightly builds added support for the new LCD panel and FocalTech touchscreen used in the v880, however I'm not sure if the new kernel currently being tested has support for these (I think it does). The specs listed mention 4G NAND, I assume this mean 4Gb (512MB), but if it is actually 4GB, then that is a change I haven't seen before and will probably be incompatible with all roms. NAND sizes are usually specified in bits, not bytes so it is probably 512MB.

The most recent CM7 nightly build should work. I'm not sure if any other custom roms added support for the newer hardware.

[Guest Ficus]

sometimes, when i turn on my phone, i don't have data traffic (although it is enabled in my phone's settings), and i need to reboot to make it work. i have n179, anyone with this issue?

also, sometimes the icons in the status bar (? - the one on the top - battery, 3g and signal bars) are green, other times are grey. what is the difference? why do they change color?

[Guest targetbsp]

They are green when you have a data connection to Googles servers so I guess them being grey goes with your other issue. :D

[Guest Ficus]

mm no..when i don't have traffic data, there is no 3g icon. so i need to reboot the phone, and the icon reappears. i can find no difference in usage between green and grey icons, it is just curiosity.

[Guest ritterkeks]

It also happened to me sometimes that the data connection would not be established.

Unticking "Data" and putting it back on in settings would'nt help, sometimes even switching flight mode /back neither.

So I also had to reboot it to get data back...

But for me it seems to be related to international data roaming (which I have switched off most of the time),

when I come back to my provider's country, the blade kind off misses that it should now establish the data connection again.

sometimes it comes back when I switch the screen on and wait for a few sec, sometimes it doesn't.

But I don't think it happened with n179++

[Guest targetbsp]

Patchset 2 for the new kernel is up: http://review.cyanogenmod.com/#change,7852

[Guest hlubepet]

Patchset 2 for the new kernel is up: http://review.cyanogenmod.com/#change,7852

very nice.. cant wait....

[Guest asm19]

sej7278 there's some new version KANG with these changes TomGiordano? If so, you provided for testing? The burstlam know has done the kernel update:

Update 11th Sep 2011

changelog:

V.2.4 (11th Sep 2011)

- Add TOMG's Patch on Proximity Sensor, works fine on my SFBLADE OLED with a clean install.

- Drop Androko FM with RDS driver support (the battery drainageissue is in a deadend, May be it Should Be Dealt with the apps Fmlibaudio.so.which Itself and I do not have the resources to the OS.)

Let's see if the proximity sensor is working properly.

Edited September 11, 2011 by asm19