Edit: Just wanted to add a video and picture
Also to let people know that if you answer posts with "didnt read" and "Complete FAIL!", its just not helpful.
http://youtu.be/IzhL6CZv3gk
OK the story so far and this warning..
I did a pudding unlock, all went good.
Then i did a Bootstrap Recovery on my stock rom that had been webdock and razr camera hacked. Did a reset then did a nand backup.
Then proceeded to install jokers cm9, then I installed the bundled recovery that joker provides.
After that I didn't much care for it because cm9 is always missing all the pst stuff. (But its nice to see the photon getting some ics love, compared to my shift.) After About 30 minutes i decided to restore from nand, fired up cmw.
Did a restore, it failed md5. I attributed that to different versions of cmw. So I simply installed bootstrap recovery again and rebooted, no luck still stuck with jokers.
So I just went ahead and did an advanced system restore and restore partition by partition. MD5 didnt fail, I started with system, then boot, then data. So everything was good and i was in adb dmesg and while restoring the data portion the phone shuts off and now i got a nvidia microboot device instead of a photon.
BEWARE this is my first real brick ever since the motoq days.
What a shame..
I know there is a way to recover with nvidia flasher but that requires having the partitions. I remember recovering a tablet like that once.
But it is bricked......................How sad....
If anyone can help, please help.
If you cant then be warned!!
Always use rsd!!!!!!!!! screw cmw to go back to stock
The worse part about it was that i was more than happy with the stock rom and kernel. This was the first phone in a while i was happy with.
this were my phone's last words.....
Code:
<6>[ 10.272942] usb 2-1: Product: Flash MDM6600
<6>[ 10.272947] usb 2-1: Manufacturer: Motorola, Incorporated
<6>[ 10.273178] usb 2-1: configuration #1 chosen from 1 choice
<6>[ 10.426045] BLUETOOTH: bt_power: Bluetooth power is off, and BT module is
in reset.
<6>[ 10.426055] Bluetooth: BlueSleep Mode Driver Ver 1.1
<6>[ 10.426196] moto-flashmdm 2-1:1.0: moto-flashmdm converter detected
<6>[ 10.426598] usb 2-1: moto-flashmdm converter now attached to ttyUSB0
<6>[ 10.427051] cpuidle: using governor ladder
<6>[ 10.427665] cpuidle: using governor menu
<6>[ 10.427770] sdhci: Secure Digital Host Controller Interface driver
<6>[ 10.427777] sdhci: Copyright(c) Pierre Ossman
<6>[ 10.427783] tegra_sdhci_simple_init
<6>[ 10.427829] tegra_sdhci_simple_probe
<6>[ 10.427855] tegra-sdhci-simple tegra-sdhci-simple.3: probe complete
<6>[ 10.428086] tegra-sdhci tegra-sdhci.3: write protect: -1, card detect: -1,
always on: 1
<4>[ 10.428118] mmc0: Invalid maximum block size, assuming 512 bytes
<6>[ 10.428257] Registered led device: mmc0::
<6>[ 10.428396] mmc0: SDHCI controller on tegra-sdhci.3 [tegra-sdhci.3] using
ADMA
<6>[ 10.428405] tegra-sdhci tegra-sdhci.3: probe complete
<6>[ 10.428453] tegra-sdhci tegra-sdhci.0: write protect: -1, card detect: -1,
always on: 1
<4>[ 10.428485] mmc1: Invalid maximum block size, assuming 512 bytes
<6>[ 10.428674] Registered led device: mmc1::
<6>[ 10.428796] mmc1: SDHCI controller on tegra-sdhci.0 [tegra-sdhci.0] using
ADMA
<6>[ 10.428805] tegra-sdhci tegra-sdhci.0: probe complete
<6>[ 10.428838] tegra-sdhci tegra-sdhci.1: no ODM SDIO adaptation
<6>[ 10.428851] tegra-sdhci tegra-sdhci.1: write protect: -1, card detect: -1,
always on: 1
<4>[ 10.428880] mmc2: Invalid maximum block size, assuming 512 bytes
<6>[ 10.429015] Registered led device: mmc2::
<6>[ 10.429147] mmc2: SDHCI controller on tegra-sdhci.1 [tegra-sdhci.1] using
ADMA
<6>[ 10.429156] tegra-sdhci tegra-sdhci.1: probe complete
<6>[ 10.429204] tegra-sdhci tegra-sdhci.2: write protect: -1, card detect: 69,
always on: 0
<4>[ 10.429305] mmc3: Invalid maximum block size, assuming 512 bytes
<6>[ 10.429438] Registered led device: mmc3::
<6>[ 10.429555] mmc3: SDHCI controller on tegra-sdhci.2 [tegra-sdhci.2] using
ADMA
<6>[ 10.429564] tegra-sdhci tegra-sdhci.2: probe complete
<6>[ 10.429843] Registered led device: button-backlight
<6>[ 10.429955] Registered led device: button-backlight-tcmd
<6>[ 10.430211] Registered led device: white
<6>[ 10.430328] Registered led device: red
<6>[ 10.430447] Registered led device: green
<6>[ 10.430554] Registered led device: blue
<6>[ 10.430644] lm3530_init: enter
<6>[ 10.430747] lm3532_init: enter
<6>[ 10.430770] lm3532_probe: enter, I2C address = 0x38, flags = 0x0
<6>[ 10.430782] disp_backlight_init: gpio_request(32, backlight_en) success!
<6>[ 10.430790] disp_backlight_power_on: display backlight is powered on
<6>[ 10.449795] lm3532_setup: revision 0xE4
<6>[ 10.450804] Registered led device: lcd-backlight
<6>[ 10.450912] Registered led device: lcd-backlight-tcmd
<6>[ 10.451021] Registered led device: lcd-backlight-webtop
<6>[ 10.479874] usbcore: registered new interface driver usbhid
<6>[ 10.479885] usbhid: v2.6:USB HID core driver
<6>[ 10.480282] logger: created 1024K log 'log_main'
<6>[ 10.480416] logger: created 512K log 'log_events'
<6>[ 10.480548] logger: created 64K log 'log_radio'
<6>[ 10.480684] logger: created 64K log 'log_system'
<4>[ 10.481142] nf_conntrack version 0.5.0 (13062 buckets, 52248 max)
<4>[ 10.481438] CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Plea
se use
<4>[ 10.481446] nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack modu
le option or
<4>[ 10.481453] sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
<6>[ 10.481660] ip_tables: (C) 2000-2006 Netfilter Core Team
<6>[ 10.481724] TCP cubic registered
<6>[ 10.482638] NET: Registered protocol family 10
<6>[ 10.482982] lo: Disabled Privacy Extensions
<6>[ 10.483225] Mobile IPv6
<6>[ 10.483231] IPv6 over IPv4 tunneling driver
<6>[ 10.483719] sit0: Disabled Privacy Extensions
<6>[ 10.483770] NET: Registered protocol family 17
<6>[ 10.483787] NET: Registered protocol family 15
<6>[ 10.483805] Bluetooth: L2CAP ver 2.14
<6>[ 10.483810] Bluetooth: L2CAP socket layer initialized
<6>[ 10.483819] Bluetooth: SCO (Voice Link) ver 0.6
<6>[ 10.483824] Bluetooth: SCO socket layer initialized
<6>[ 10.483896] Bluetooth: RFCOMM TTY layer initialized
<6>[ 10.483906] Bluetooth: RFCOMM socket layer initialized
<6>[ 10.483912] Bluetooth: RFCOMM ver 1.11
<6>[ 10.483918] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
<6>[ 10.483925] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
<6>[ 10.484082] VFP support v0.3: implementor 41 architecture 3 part 30 varian
t 9 rev 1
<4>[ 10.484905] regulator_init_complete: incomplete constraints, leaving vsimc
ard on
<4>[ 10.485089] regulator_init_complete: incomplete constraints, leaving vpll
on
<4>[ 10.485128] regulator_init_complete: incomplete constraints, leaving vsdio
on
<4>[ 10.485253] regulator_init_complete: incomplete constraints, leaving vcsi
on
<4>[ 10.485320] regulator_init_complete: incomplete constraints, leaving vusb
on
<4>[ 10.485358] regulator_init_complete: incomplete constraints, leaving sw4 o
n
<4>[ 10.485396] regulator_init_complete: incomplete constraints, leaving sw3 o
n
<4>[ 10.485434] regulator_init_complete: incomplete constraints, leaving sw2 o
n
<4>[ 10.485472] regulator_init_complete: incomplete constraints, leaving sw1 o
n
<3>[ 10.486221] regulator_check_voltage: operation not allowed for vusb
<6>[ 10.487029] cpcap_usb_det cpcap_usb_det: CPCAP USB detection device probed
<6>[ 10.488183] cpcap_rtc cpcap_rtc: setting system clock to 2012-02-29 21:15:
54 UTC (1330550154)
<6>[ 10.488600] Freeing init memory: 204K
<4>[ 10.488646] Warning: unable to open an initial console.
<3>[ 10.572237] init: cannot open '/initlogo.rle'
<3>[ 10.572668] init: Unable to open persistent property directory /data/prope
rty errno: 2
<6>[ 10.574819] enabling adb
<6>[ 10.574977] adb_open
<6>[ 10.576106] device_mode_change_write Mode change command=msc_adb
<6>[ 10.576111]
<6>[ 10.591147] device_mode_change_write - Successfully enabled function - msc
_adb
<6>[ 10.591152]
<6>[ 10.601372] cpcap_usb_det: state IDENTIFY
<6>[ 10.601560] cpcap_usb_det: SenseBits = 0x401c
<6>[ 10.601565] cpcap_usb_det: USB or USB_FLASH
<6>[ 10.601573] cpcap spi1.0: notify_accy: accy=0
<7>[ 10.602391] tegra_otg_set_mode setting OTG_STATE_B_PERIPHERAL
<6>[ 10.602400] android_usb_set_connected - connected = 1, accy = 0
<6>[ 10.602517] mdm_ctrl: set_ap_status(5)
<6>[ 10.602525] mdm_ctrl_set_usb_ipc: usb ipc count is now: 1
<6>[ 10.621831] mmc0: new high speed MMC card at address 0001
<6>[ 10.621983] mmc0: enable Toshiba workaround
<6>[ 10.622097] mmcblk0: mmc0:0001 Toshiba MMC16G 14.9 GiB
<6>[ 10.622220] mmcblk0: p1 p2 p3 p4 < p5 p6 p7 p8 p9 p10 p11 p12 p13 p14 p15
p16 p17 p18 p19 >
<6>[ 11.093000] android_usb gadget: high speed config #1: android
<3>[ 13.600817] EXT3-fs: mmcblk0p12: couldn't mount because of unsupported opt
ional features (40).
<4>[ 13.601299] EXT2-fs: mmcblk0p12: couldn't mount because of unsupported opt
ional features (40).
<6>[ 13.622523] EXT4-fs (mmcblk0p12): mounted filesystem with ordered data mod
e
<4>[ 13.682188] qtouch_process_info_block: Checksum mismatch (0x7364 != 0xf04b
)
<4>[ 13.690290] qtouch_process_info_block: Checksum mismatch (0x7364 != 0xf04b
)
<4>[ 13.698265] qtouch_process_info_block: Checksum mismatch (0x7364 != 0xf04b
)
<4>[ 13.988456] qtouch_hw_init: Doing hw init
<4>[ 14.016413] qtouch_process_info_block: Checksum mismatch (0x7364 != 0xf04b
)
<4>[ 14.096342] qtouch_process_info_block: Checksum mismatch (0x7364 != 0xf04b
)
<6>[ 14.787712] kjournald starting. Commit interval 5 seconds
<6>[ 14.791254] EXT3 FS on mmcblk0p15, internal journal
<6>[ 14.791268] EXT3-fs: mounted filesystem with ordered data mode.
<6>[ 23.195692] ------Active wakelock list(suspend)-----
<6>[ 23.195702] active wake lock cpcap-irq
<6>[ 23.195707] active wake lock usb
<6>[ 23.195711] active wake lock main
<6>[ 23.195717] active wake lock pwrkey, time left 20
<6>[ 23.195722] ------Active wakelock end-----
<6>[ 26.750388] ------Active wakelock list(suspend)-----
<6>[ 26.750398] active wake lock cpcap-irq
<6>[ 26.750403] active wake lock usb
<6>[ 26.750408] active wake lock main
<6>[ 26.750413] active wake lock pwrkey, time left 20
<6>[ 26.750418] ------Active wakelock end-----
<6>[ 35.348112] ------Active wakelock list(suspend)-----
<6>[ 35.348121] active wake lock cpcap-irq
<6>[ 35.348126] active wake lock usb
<6>[ 35.348131] active wake lock main
<6>[ 35.348136] active wake lock pwrkey, time left 20
<6>[ 35.348141] ------Active wakelock end-----
<6>[ 39.859844] ------Active wakelock list(suspend)-----
<6>[ 39.859853] active wake lock cpcap-irq
<6>[ 39.859858] active wake lock usb
<6>[ 39.859863] active wake lock main
<6>[ 39.859868] active wake lock pwrkey, time left 20
<6>[ 39.859873] ------Active wakelock end-----
<6>[ 45.535717] ------Active wakelock list(suspend)-----
<6>[ 45.535727] active wake lock cpcap-irq
<6>[ 45.535732] active wake lock usb
<6>[ 45.535736] active wake lock main
<6>[ 45.535742] active wake lock pwrkey, time left 20
<6>[ 45.535746] ------Active wakelock end-----
<6>[ 48.551358] ------Active wakelock list(suspend)-----
<6>[ 48.551368] active wake lock cpcap-irq
<6>[ 48.551373] active wake lock usb
<6>[ 48.551377] active wake lock main
<6>[ 48.551383] active wake lock pwrkey, time left 20
<6>[ 48.551387] ------Active wakelock end-----
<6>[ 50.453540] ------Active wakelock list(suspend)-----
<6>[ 50.453549] active wake lock cpcap-irq
<6>[ 50.453555] active wake lock usb
<6>[ 50.453559] active wake lock main
<6>[ 50.453564] active wake lock pwrkey, time left 20
<6>[ 50.453569] ------Active wakelock end-----
<6>[ 68.199956] ------Active wakelock list(suspend)-----
<6>[ 68.199966] active wake lock cpcap-irq
<6>[ 68.199971] active wake lock usb
<6>[ 68.199976] active wake lock main
<6>[ 68.199981] active wake lock pwrkey, time left 20
<6>[ 68.199986] ------Active wakelock end-----
<6>[ 71.457635] ------Active wakelock list(suspend)-----
<6>[ 71.457644] active wake lock cpcap-irq
<6>[ 71.457649] active wake lock usb
<6>[ 71.457654] active wake lock main
<6>[ 71.457659] active wake lock pwrkey, time left 20
<6>[ 71.457664] ------Active wakelock end-----
<6>[ 154.786741] kjournald starting. Commit interval 5 seconds
<6>[ 154.790014] EXT3 FS on mmcblk0p12, internal journal
<6>[ 154.790029] EXT3-fs: mounted filesystem with ordered data mode.
<6>[ 181.453093] usbnet_suspend
<6>[ 181.727873] usbnet_resume
<6>[ 181.727897] usbnet_disable
<7>[ 181.727904] mtp_function_disable(): disabled
<3>[ 181.728042] adb_read returning -5 for count 24
<6>[ 181.728142] adb_release
<6>[ 181.728262] adb_open
<6>[ 183.107124] android_usb gadget: high speed config #1: android
<6>[ 190.084812] usbnet_suspend
<6>[ 190.321582] usbnet_resume
<6>[ 190.321619] usbnet_disable
<7>[ 190.321626] mtp_function_disable(): disabled
<3>[ 190.321795] adb_read returning -5 for count 24
<6>[ 190.321906] adb_release
<6>[ 190.322011] adb_open
<6>[ 190.684555] android_usb gadget: high speed config #1: android
<6>[ 322.041989] ------Active wakelock list(suspend)-----
<6>[ 322.041998] active wake lock cpcap-irq
<6>[ 322.042003] active wake lock usb
<6>[ 322.042007] active wake lock main
<6>[ 322.042012] active wake lock pwrkey, time left 20
<6>[ 322.042017] ------Active wakelock end-----
<6>[ 326.920784] ------Active wakelock list(suspend)-----
<6>[ 326.920793] active wake lock cpcap-irq
<6>[ 326.920799] active wake lock usb
<6>[ 326.920803] active wake lock main
<6>[ 326.920809] active wake lock pwrkey, time left 20
<6>[ 326.920814] ------Active wakelock end-----
<6>[ 328.334973] ------Active wakelock list(suspend)-----
<6>[ 328.334982] active wake lock cpcap-irq
<6>[ 328.334987] active wake lock usb
<6>[ 328.334991] active wake lock main
<6>[ 328.334997] active wake lock pwrkey, time left 20
<6>[ 328.335002] ------Active wakelock end-----
<6>[ 333.452211] ------Active wakelock list(suspend)-----
<6>[ 333.452220] active wake lock cpcap-irq
<6>[ 333.452225] active wake lock usb
<6>[ 333.452230] active wake lock main
<6>[ 333.452235] active wake lock pwrkey, time left 20
<6>[ 333.452240] ------Active wakelock end-----
<6>[ 335.936481] ------Active wakelock list(suspend)-----
<6>[ 335.936490] active wake lock cpcap-irq
<6>[ 335.936495] active wake lock usb
<6>[ 335.936500] active wake lock main
<6>[ 335.936505] active wake lock pwrkey, time left 20
<6>[ 335.936510] ------Active wakelock end-----
<6>[ 459.465097] ------Active wakelock list(suspend)-----
<6>[ 459.465106] active wake lock cpcap-irq
<6>[ 459.465111] active wake lock usb
<6>[ 459.465116] active wake lock main
<6>[ 459.465121] active wake lock pwrkey, time left 20
<6>[ 459.465126] ------Active wakelock end-----
<6>[ 463.320575] ------Active wakelock list(suspend)-----
<6>[ 463.320584] active wake lock cpcap-irq
<6>[ 463.320589] active wake lock usb
<6>[ 463.320594] active wake lock main
<6>[ 463.320599] active wake lock pwrkey, time left 20
<6>[ 463.320604] ------Active wakelock end-----
<6>[ 464.238398] ------Active wakelock list(suspend)-----
<6>[ 464.238407] active wake lock cpcap-irq
<6>[ 464.238413] active wake lock usb
<6>[ 464.238417] active wake lock main
<6>[ 464.238422] active wake lock pwrkey, time left 20
<6>[ 464.238427] ------Active wakelock end-----
<6>[ 470.285493] ------Active wakelock list(suspend)-----
<6>[ 470.285502] active wake lock cpcap-irq
<6>[ 470.285508] active wake lock usb
<6>[ 470.285512] active wake lock main
<6>[ 470.285518] active wake lock pwrkey, time left 20
<6>[ 470.285523] ------Active wakelock end-----
<6>[ 472.222993] ------Active wakelock list(suspend)-----
<6>[ 472.223003] active wake lock cpcap-irq
<6>[ 472.223008] active wake lock usb
<6>[ 472.223013] active wake lock main
<6>[ 472.223018] active wake lock pwrkey, time left 20
<6>[ 472.223023] ------Active wakelock end-----
<6>[ 575.444659] kjournald starting. Commit interval 5 seconds
<6>[ 575.448189] EXT3 FS on mmcblk0p16, internal journal
<6>[ 575.448204] EXT3-fs: mounted filesystem with ordered data mode.
Saw the problem within 10 seconds, didn't read the rest .... can't flash CM9 with boot strap. You need a full CWM recovery.img
P.S. - it's not bricked. An SBF should fix it.
That's my 2 pennies
Yep, bootstrap not needed when you're unlocked. You needed romracers cwm-based recoveryhttp://forum.xda-developers.com/showpost.php?p=16654262&postcount=1
Have you tried rsd to flash the stock sbf?
KSmithInNY said:
Saw the problem within 10 seconds, didn't read the rest .... can't flash CM9 with boot strap. You need a full CWM recovery.img
P.S. - it's not bricked. An SBF should fix it.
That's my 2 pennies
Click to expand...
Click to collapse
I agree...
Also from the main post of the CM 9 thread:
First time flashing CyanogenMod 9 to the Motorola Photon 4G?, or coming from another ROM?
Root the Photon.
Unlock the Bootloader.
Flash the recovery on my site in cwm
Perform a NANDroid backup of your current ROM.
Format the system, data & cache partitions of your device.
Perform a factory reset.
Flash This ROM.
Click to expand...
Click to collapse
That would be the recovery from HERE
To the OP I would not be spreading FUD about CM9 Bricking your phone when you quite obviously did not read the original thread for CM9. Not ONCE does it say use the Bootstrap recovery there at all...
Complete FAIL!..
When you read more .. They chance of bricks errors etc less likely to occur like this one.. Let this be a lesson learned for ya ... ..
And i almost sold my soul for a epic.. But glad i checked their forums first.. Jesus Christ those guys are crazy demanding....smh i love this community
Sent from my MB855 using xda premium
I believe the title of this thread should be changed. When I read it, it seems CM9 caused his phone to be bricked which clearly it didn't.
Sent from my MB855 using XDA App
This is what happens when you dont read wtf your doing before doing NICE job
The OP can change the thread title under edit>advanced options
My experience as a forum mod is that would never happen. Maybe out of respect for joker, someone report the thread and ask for a title change. **** like this would piss me off as a mod (why should I wipe others ass?) But as a developer, I'd appreciate the time spent.
Cheers!
pastert33 said:
I believe the title of this thread should be changed. When I read it, it seems CM9 caused his phone to be bricked which clearly it didn't.
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
Absolutely agree!
He clearly did not fully read, understand, follow the instructions.
Mods should change title.
Its going again
Guys thanks for the quick reply, i was looking at it and I didnt answer because i had company.
Especially the bit about romracers, i was already eying that one.
Just to be clear, its not from not reading.
Its just an unfortunate incident.
I will change the name because now i know what happened.
What happened is that my charge mode is now gone.
Also i am not able to turn on the phone with the power button.
I have to connect it and it will then proceed to boot as normal after a little bit.
In other words i cant charge the phone unless it is on.
So i leave it connected but with the a piece of tape on the volume down button.
In minutes it goes to the motorola screen, where it says unlocked.
when i saw that i removed the battery and put it in my external battery charges. i recommend this one it works great and you dont have to worry about polarity. http://www.cellularpartsusa.com/for-universal-travel-charger-with-led.html
Then gave it about 1 hour on the charger and then I was able to go into fast boot and flashed recovery-red-photon3.img and I was able to go into recovery once more.
Where i then flashed cm9 again to see if it would fix my charge model, but I am in cm9 now
Surprise surprise it didn't fix the charger mode, so after getting some visit out of the way i am back on track to sbf it back to stock.
I will post a follow up once i sbf back to stock.
Recreated the problem
Ok I recreated the problem and saw exactly what happened.
When I was restoring the nandroid it erased the boot partition.
Then while writing it failed, but I was too busy with adb.
So i then manually recovered and then the phone restarted.
{
"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"
}
How is this not following instructions and not knowing how to flash?
http://farm8.staticflickr.com/7050/6796881166_e6e8ba294e.jpg
Sigh.. Because you did your Nandroid using bootstrap that DOES NOT BACKUP BOOT..
Yes it is because you did not read/research before doing it.
Here is what you SHOULD have done.
1. Pudding unlock
2. Install a REAL cwm recovery using fastboot (romracers)
3. Use Jokers cwm recovery zip in Romracers.
4. Then backup your phone using recovery (which will now back up everything unlike Bootstrap)
5. Install CM9
Seriously the whole issue is because you used bootstrap for your main backup. Your best bet is to SBF back to stock and write off your backup. Or sbf, root, use bootstrap, recover your backup, then follow the steps from point 2 and never EVER use bootstrap again.. If you had read the many guides you would have known that.
Also the reason everyone jumped on your back with "Fail" is because your original post was in the development area with the heading of "***WARNING*** Joker's CM9 Bricks your phone" or something to that effect. You brought it on yourself really...
Sent from my MB855 using Tapatalk
Related
As a lot of other persons I have the "screen lag" issue. After reading several posts I have found a way to fix it : I've just removed the back cover and I check the battery position, then I put back the back cover.
Now the big lag disappeared.....
No need to add a paper between the battery and the back cover in my case.
I hope it will help others.
Well, another thing that worked for me was tighten all screws a tiny bit.
Worked like charm ^^
I opened d battery twice since i bought my folio. Lagging issue oni several times for me. Is it really should do this i don know.
Should give a try bcoz it is no need to pay for opening d battery
I still believe that must of the lag is caused by bad software, though i also notice that screen is kind of lose.
bastospn said:
I still believe that must of the lag is caused by bad software
Click to expand...
Click to collapse
i do believe too, no prove but have the feeling that some app crashed behind the screen and make the folio lag or freezed.
somebody can confirm that?
waii69 said:
i do believe too, no prove but have the feeling that some app crashed behind the screen and make the folio lag or freezed.
somebody can confirm that?
Click to expand...
Click to collapse
using dev tools, u can monitor the cpu usage values. if it get above 2.0( except for the first 2/3 minutes when booting and when connecting to wifi), then some app is causing it to lag. if values are still below that number for a long time and still there is screen lag issue, then its definitely a hardware issue.
use an app called aLogCat to see what's happening during an error. Pretty handy errorlog tool
thanks guys, i will try and see what is happen.
This is what i get when i clear the log, then shut the screen and wait till it pops open.
Code:
D/WindowManager( 1081): I'm tired mEndcallBehavior=0x2
I/power ( 1081): *** set_screen_state 0
E/Sensors ( 1081): mask[0x0]
D/RemoteCtrlManager( 1081): ACTION_SCREEN_OFF
D/UpdateReceiver:( 1081): HDMI_UNPLUG
D/UpdateReceiver:( 1081): false
D/RemoteCtrlManager( 1081): initHDMIfalse
V/alogcat (12698): save instance
V/alogcat (12698): paused
D/JuicePlotter.CollectService( 1583): battery:81, plugged:1, screen:0, wifi:false,apn:false,bluetooth:false
D/ ( 976): NVRM_DAEMON(985): pm_notifier_thread: calling power_displays(false)
D/ ( 976): NVRM_DAEMON(988): pm_notifier_thread: returned from power_displays(false)
D/JuicePlotter.CollectService( 1583): battery:81, plugged:1, screen:0, wifi:false,apn:false,bluetooth:false
D/JuicePlotter.CollectService( 1583): battery:81, plugged:1, screen:0, wifi:false,apn:false,bluetooth:false
D/dalvikvm( 1178): GC_EXPLICIT freed 546 objects / 124312 bytes in 74ms
I/AKMD2 ( 930): akmd2 : Compass Closed.
D/dalvikvm( 5555): GC_EXPLICIT freed 2696 objects / 169120 bytes in 70ms
D/dalvikvm( 5835): GC_EXPLICIT freed 3104 objects / 113848 bytes in 93ms
D/ ( 976): NVRM_DAEMON(974): pm_notifier_thread: calling power NvddkAudioFxSuspend(true)
I/AKMD2 ( 930): akmd2 : Suspended.
W/EventHub( 1081): could not get event (errno=19)
I/EventHub( 1081): Removed device: path=/dev/input/event8 name=USB2.0 UVC 1.3M WebCam id=0x380008 (of 0x9) index=10 fd=328 classes=0x1
D/org.jraf.android.nolock.NoLockService( 1479): onStartCommand
D/org.jraf.android.nolock.NoLockService( 1479): handleStart locking=false (nolock ENABLED)
D/org.jraf.android.nolock.NoLockService( 1479): handleStart mKeyguardLock != null: reenabling keyguard
I/power ( 1081): *** set_screen_state 1
D/ ( 976): NVRM_DAEMON(980): pm_notifier_thread: calling power NvddkAudioFxSuspend(false)
D/ ( 976): NVRM_DAEMON(991): pm_notifier_thread: calling power_displays(true)
W/ResourceType( 1081): Invalid package identifier when getting bag for resource number 0x00000000
D/GoogleLoginService( 1178): onBind: Intent { act=android.accounts.AccountAuthenticator cmp=com.google.android.gsf/.loginservice.GoogleLoginService }
E/Sensors ( 1081): mask[0x0]
D/RemoteCtrlManager( 1081): ACTION_SCREEN_ON
D/UpdateReceiver:( 1081): HDMI_UNPLUG
D/UpdateReceiver:( 1081): false
D/RemoteCtrlManager( 1081): initHDMIfalse
V/alogcat (12698): resumed
D/ ( 976): NVRM_DAEMON(994): pm_notifier_thread: returned from power_displays(true)
Some unrelated stuff there too like juice plotter and no lock...sorry.
So after a week on cm7 i've decided to go back to my zckpa chinese rom. cm7 is not that stable for now, and most of its features i can get with zckpa rom. but the thing that still bugging stock/custom rom based on stock is sod. from my experience its caused by wifi, when the phone get out of known wifi range and it constantly scanning, it get sod. then i found this little app that solve my sod problem. u need to be rooted to try this btw.
1- edit build.prop file, add this line in it
Code:
wifi.supplicant_scan_interval=300
and save it. 300 means 5 minutes, but u can use other value eg 600 which is 10 minutes. by doing this we limit phone scanning wifi interval.
2- install wififixer from market. set it:
"set wifi usability" i use "max battery"
tick on "enable wifi lock"
"wifi sleep policy" to "never"
and i've never got sod for almost a week
btw i dont use android default wifi scanning, i just let wififixer do its job in the background. not just its solve my sods problem, it also gave me stable connection, no constant signal dropping for me now
an0nym0us_ said:
So after a week on cm7 i've decided to go back to my zckpa chinese rom. cm7 is not that stable for now, and most of its features i can get with zckpa rom. but the thing that still bugging stock/custom rom based on stock is sod. from my experience its caused by wifi, when the phone get out of known wifi range and it constantly scanning, it get sod. then i found this little app that solve my sod problem. u need to be rooted to try this btw.
1- edit build.prop file, add this line in it
Code:
wifi.supplicant_scan_interval=300
and save it. 300 means 5 minutes, but u can use other value eg 600 which is 10 minutes. by doing this we limit phone scanning wifi interval.
2- install wififixer from market. set it:
"set wifi usability" i use "max battery"
tick on "enable wifi lock"
"wifi sleep policy" to "never"
and i've never got sod for almost a week
btw i dont use android default wifi scanning, i just let wififixer do its job in the background. not just its solve my sods problem, it also gave me stable connection, no constant signal dropping for me now
Click to expand...
Click to collapse
im still trying to figure out why wifi scanning will cause sod.
well theres another file, /system/etc/firmware/wlan/qcom_cfg.ini which control wifi driver in stock rom. cm doesnt have this. its content is:
Code:
# This file allows user to override the factory
# defaults for the WLAN Driver
# Enable IMPS or not
gEnableImps=1
# Enable/Disable Idle Scan
gEnableIdleScan=0
# Increase sleep duration (seconds) during IMPS
gImpsModSleepTime=600
# Enable BMPS or not
gEnableBmps=1
# Enable suspend or not
# 1: Enable standby, 2: Enable Deep sleep, 3: Enable Mcast/Bcast Filter
gEnableSuspend=3
# Phy Mode (auto, b, g, n, etc)
gDot11Mode=0
# Handoff Enable(1) Disable(0)
gEnableHandoff=0
# CSR Roaming Enable(1) Disable(0)
gRoamingTime=0
# STA MAC Address - This will be used until NV items are in place
# Each byte of MAC address is represented in Hex format as XX
NetworkAddress=000AF58989FF
# UAPSD service interval for VO,VI, BE, BK traffic
InfraUapsdVoSrvIntv=0
InfraUapsdViSrvIntv=0
InfraUapsdBeSrvIntv=0
InfraUapsdBkSrvIntv=0
# Disable RSSI FW filtering
gEnableFWRssiMonitoring=0
# Make 1x1 the default antenna configuration
gNumRxAnt=1
# Beacon filtering frequency (unit in beacon intervals)
gNthBeaconFilter=50
# Enable WAPI or not
WAPIIsEnabled=0
# Flags to filter Mcast abd Bcast RX packets.
# Value 0: No filtering, 1: Filter all Multicast.
# 2: Filter all Broadcast. 3: Filter all Mcast abd Bcast
McastBcastFilter=0
gEnableLogp=1
#SoftAP Related Parameters
# AP MAC address
gAPMacAddr=00deadbeef11
# 802.11n Protection flag
gEnableApProt=1
#Enable/Disable UAPSD for SoftAP
gEnableApUapsd=1
# Fixed Rate
gFixedRate=0
# Maximum Tx power
gTxPowerCap=30
# Fragmentation Threshold
gFragmentationThreshold=2346
# RTS threshold
RTSThreshold=2347
# Intra-BSS forward
gDisableIntraBssFwd=0
# WMM mode: Auto(0) or QBSS(1) or No-QoS(2)
WmmIsEnabled=0
# 802.11d support
g11dSupportEnabled=1
# Country code
gAPCntryCode=USI
#Short Guard Interval Enable/disable
gShortGI20Mhz=1
#Auto Shutdown Value in seconds. A value of 0 means Auto shutoff is disabled
gAPAutoShutOff=0
#Enable OBSS protection
gEnableApOBSSProt=0
# Frames Processing Minimum Threshold
gMinFramesProcThres=0
# Listen Energy Detect Mode Configuration
# Valid values 0-128
# 128 means disable Energy Detect feature
# 0-9 are threshold code and 7 is recommended value from system if feature is to be enabled.
# 10-128 are reserved.
# The EDET threshold mapping is as follows in 3dB step:
# 0 = -60 dBm
# 1 = -63 dBm
# 2 = -66 dBm
# ...
# 7 = -81 dBm
# 8 = -84 dBm
# 9 = -87 dBm
# Note: Any of these settings are valid. Setting 0 would yield the highest power saving (in a noisy environment) at the cost of more range. The range impact is approximately #calculated as:
#
# Range Loss (dB) = EDET threshold level (dBm) + 97 dBm.
#
gEnablePhyAgcListenMode=128
END
# Note: Configuration parser would not read anything past the END marker
but i dont have any slight idea what those value means
xperia ray with gingerbread cyanogen mod 7.2.
somewhere along my travels the maps app 6.2.x or so, has stopped working. when i start it, i get a white screen then nothing happens. sometimes it force-closes on its own, other times i have to kill it. map never shows up.
if i install older versions that do NOT have the option of storing offline maps, they do work. this leads me to believe that something may be wrong with the downloaded map tiles. i'm unable to figure out where in the phone they're stored - and not 100% if that could be the root of the trouble.
how to troubleshoot / fix?
below a chunk of logcat:
12-23 22:08:58.782 I/InputDispatcher(434): Application is not responding: Window{2b4a9f00 com.google.android.apps.maps/com.google.android.maps.MapsActivity paused=false}. 5001.1ms since event, 5001.0ms since wait started
12-23 22:08:58.782 I/WindowManager(434): Input event dispatching timed out sending to com.google.android.apps.maps/com.google.android.maps.MapsActivity
12-23 22:09:00.072 E/ActivityManager(434): ANR in com.google.android.apps.maps (com.google.android.apps.maps/com.google.android.maps.MapsActivity)
12-23 22:09:00.072 E/ActivityManager(434): +0% 4139/com.google.android.apps.maps: 0% user + 0% kernel
12-23 22:09:00.072 E/ActivityManager(434): +0% 4186/com.google.android.apps.maps:GoogleLocationService: 0% user + 0% kernel
12-23 22:09:00.072 E/ActivityManager(434): +0% 4202/com.google.android.apps.maps:FriendService: 0% user + 0% kernel
12-23 22:09:00.072 E/ActivityManager(434): +0% 4211/com.google.android.apps.maps:LocationFriendService: 0% user + 0% kernel
12-23 22:09:00.072 E/ActivityManager(434): 3% 4186/com.google.android.apps.maps:GoogleLocationService: 3% user + 0% kernel / faults: 125 minor
12-23 22:09:00.072 E/ActivityManager(434): 1.5% 4139/com.google.android.apps.maps: 1.5% user + 0% kernel / faults: 46 minor
12-23 22:09:00.812 W/ActivityManager(434): Activity idle timeout for HistoryRecord{2b4ff668 com.google.android.apps.maps/com.google.android.maps.MapsActivity}
12-23 22:09:02.802 W/ActivityManager(434): Force finishing activity com.google.android.apps.maps/com.google.android.maps.MapsActivity
12-23 22:09:02.802 I/ActivityManager(434): Killing com.google.android.apps.maps (pid=4139): user's request
12-23 22:09:02.832 I/ActivityManager(434): Process com.google.android.apps.maps (pid 4139) has died.
12-23 22:09:02.832 I/WindowManager(434): WIN DEATH: Window{2b4a9f00 com.google.android.apps.maps/com.google.android.maps.MapsActivity paused=true}
I ask for help! My Swift 2 Plus, after using the main camera, the phone starts to consume 10-15% per night, if you restart the phone after using the camera - 0-1% per night. WLD logs do not show any gaming processes, hence Greenify does not help.
Third-party camera applications also do not solve the problem
As a temporary solution - restart the phone after taking pictures.
How to solve this problem?
My stats for 2 nights below
For the time of the experiment I never connected the charge \ of computers, I did not change any settings in the phone, I did not set any applications, the state of all sensors \ radio \ gps \ nfc \ bt \ wifi \ sync \ is one-to-one. Did so:
The first night: before going to bed I reset the phone, opened the camera, took a couple of pictures, put a custom label in BetterBatteryStats and went to bed. woke up - immediately saved the log from the user label to the current one.
The second night: before going to bed I reset the phone, put a custom label in BetterBatteryStats and went to bed. woke up - immediately saved the log from the user label to the current one.
Total face: 1.5% per hour drains after using the camera, against 0.1% per hour without camera
After using the camera:
/*
===================
General Information
===================
BetterBatteryStats version: 2.2.2.0
Creation Date: 2018-01-12 05:25:31
Statistic Type: Custom to Current
Since 7 h 34 m 5 s
Note:
VERSION.RELEASE: 7.1.2
BRAND: Wileyfox
DEVICE: marmite
MANUFACTURER: Wileyfox
MODEL: SM-N920C
OS.VERSION: 3.18.31-g6377f87
BOOTLOADER: marmite-N-ge8bbd8f
HARDWARE: qcom
FINGERPRINT: Xiaomi/sagit/sagit:7.1.1/NMF26X/V8.2.17.0.NCACNEC:user/release-keys
ID: N2G48B
TAGS: release-keys
USER: jenkins
PRODUCT: Swift2
RADIO: 937_GENNS_PACK-1.83666.1.89031.1
Root perms: true
SELinux Policy: Enforcing
BATTERY_STATS permission granted: true
XPosed BATTERY_STATS module enabled: false
============
Battery Info
============
Level lost [%]: Bat.: -11%(94% to 83%) [1,5%/h]
Voltage lost [mV]: (4151-4108) [5,7%/h]
===========
Other Usage
===========
Deep Sleep (): 7 h 26 m 31 s 98,3%
Awake (Screen Off) (): 7 m 8 s 1,6%
Screen On (): 25 s 0,1%
Wifi On (): 17 m 4 s 3,8%
Wifi Running (): 27 m 34 s 6,1%
Doze Interactive Time (): 24 s 0,1%
Sync (): 8 s 0,0%
Screen dark (): 0,0%
Screen medium (): 25 s 0,1%
======================================================
Without using the camera:
/*
===================
General Information
===================
BetterBatteryStats version: 2.2.2.0
Creation Date: 2018-01-13 07:55:30
Statistic Type: Custom to Current
Since 10 h 54 m 19 s
Note:
VERSION.RELEASE: 7.1.2
BRAND: Wileyfox
DEVICE: marmite
MANUFACTURER: Wileyfox
MODEL: SM-N920C
OS.VERSION: 3.18.31-g6377f87
BOOTLOADER: marmite-N-ge8bbd8f
HARDWARE: qcom
FINGERPRINT: Xiaomi/sagit/sagit:7.1.1/NMF26X/V8.2.17.0.NCACNEC:user/release-keys
ID: N2G48B
TAGS: release-keys
USER: jenkins
PRODUCT: Swift2
RADIO: 937_GENNS_PACK-1.83666.1.89031.1
Root perms: true
SELinux Policy: Enforcing
BATTERY_STATS permission granted: true
XPosed BATTERY_STATS module enabled: false
============
Battery Info
============
Level lost [%]: Bat.: -1%(50% to 49%) [0,1%/h]
Voltage lost [mV]: (3820-3836) [-1,5%/h]
===========
Other Usage
===========
Deep Sleep (): 10 h 48 m 3 s 99,0%
Awake (Screen Off) (): 5 m 56 s 0,9%
Screen On (): 19 s 0,0%
Wifi On (): 15 m 59 s 2,4%
Wifi Running (): 16 m 1 s 2,4%
Doze Interactive Time (): 18 s 0,0%
Sync (): 7 s 0,0%
Screen dark (): 0,0%
Screen medium (): 19 s 0,0%
======================================================
Interesting, but I hardly ever use the camera and I also have some nights where my phone loses about 20% and others where my phone loses only a couple (say, 5%). It cannot be ONLY due to the camera. I haven't been able to find out what's up, but a reboot every now and then keeps me performing ok.
Up
I'm thinking it's a camera software issue? I guess only an update with a patch could fix that.
Running Unofficial LineageOS 14.1.
The battery drainage in idle mode is about 3 times higher than normal after I use the camera.
Hello!
I see that there is no recent activity in this thread, but I hope to get some help...
I have Wileyfox Swift 2 and Swift 2 Plus phones. Swift 2 Plus has the battery drain possibly related to its camera usage. I tried to flash and use it with stock Android Nougat and Oreo as well as with unofficial Lineage 15 ROMs. Unfortunately, the battery drain appears with all of these ROMs. The only one solution I found is to restart the phone...
Did you have any other solutions or additional information?
Interesting that Swift 2 doesn't have this issue.
Thank you!
Hi all,
I want to use a beacon to run a task when I'm within range and out of range of the beacon.
To test I decided to make two simple tasks that just used the Flash Action to show whether the phone was within range of the ibeacon. The problem was I kept getting many false disconnects even when the phone was right next to the ibeacon. The thing is: it does not get lost by the phone, but only by Tasker. I tested that with the app "nRF Connect", which is able to display an "RSSI Graph", which is a time-oriented graph with the signal strengths from all received BT devices per second. It shows, that the phone receives the signal from the beacon constantly in a good signal strength.
Log is below.
So why is the phone seeing the beacon and Tasker is not?
Profile: Beacon Near
State: BT Near [ Name:* Address:FE:7E:B4:A9:CC:63 Major Device Class:Any Standard Devices:Off Low-Energy (LE) Devices:On Unpaired Devices:On Toggle BlueTooth:Off ]
Enter Task: Connected
A1: Variable Set [
Name: %Test
To: %PACTIVE
Max Rounding Digits: 3
Structure Output (JSON, etc): On ]
A2: Flash [
Text: Connected
Continue Task Immediately: On
Dismiss On Click: On ]
Exit Task: Disconnected
A1: Wait [
MS: 0
Seconds: 2
Minutes: 0
Hours: 0
Days: 0 ]
A2: Variable Set [
Name: %Test
To: %PACTIVE
Max Rounding Digits: 3
Structure Output (JSON, etc): On ]
A3: Flash [
Text: Disconnected
Continue Task Immediately: On
Dismiss On Click: On ]
Monitor Preferences:
BT Scan Seconds: 120
BT Minimum Timeout Seconds:15
All Checks Seconds:70
Timeout Seconds:60
Code:
20221020 07.57.18 M Restart ID0:0.0 Monitor
20221020 08.05.05 P Inactive ID26 Beacon Near
20221020 08.05.05 E Start ID0:0.0 TaskService
20221020 08.05.05 T Running ID28 Disconnected
20221020 08.05.08 A OK ID28.1 Disconnected.Wait
20221020 08.05.08 A OK ID28.2 Disconnected.Var Set, %Test=,AD On Off,
20221020 08.05.08 A OK ID28.3 Disconnected.Flash
20221020 08.05.08 T ExitOK ID28 Disconnected
20221020 08.05.08 E Stop ID0:0.0 TaskService