M

mariosanoguera

Guest
Hello Walter, do you remember some users having the non charging problem when the defy was completely out of battery or with the phone shut down?

Have you found any solution to this?
 

walter79

Recognized Developer
Dec 18, 2006
4,100
4,618
263
maybe a update for /system/bootmenu/2nd-boot/ hbootuser and hboot.bin with latest cm10.1 files can help. Sorry but no time to test it.
 

viper.

Senior Member
Feb 10, 2010
323
51
0
ZAGREB
Cant install it after cm10.1 it just wont boot. I have left it for 20 minits,repeated that twice . All was good, checked some option in aroma installer then restart and after that just Blank screen.

Any thoughts? I cant access stock recovery...
 
M

mariosanoguera

Guest
Cant install it after cm10.1 it just wont boot. I have left it for 20 minits,repeated that twice . All was good, checked some option in aroma installer then restart and after that just Blank screen.

Any thoughts? I cant access stock recovery...
This is due CM10.1 is ext 3 and msginger uses ext 4

From this point, your only option is to flash from sbf and start from 0 (root, sndinit and then install msginger it will work)

@walter small doubt, I felt that the torch is very low compared to cm7 or cm10

so I searched and I found these are the values to be changed

ro.media.capture.flashIntensity=41
ro.media.capture.torchIntensity=25

what you reccomend me to put? I've put 45 and photos are much better under the same conditions and flash looks brighter, you reccomend me other values or changing other parts from build prop?
 
Last edited:

Antiga Prime

Senior Member
Sep 25, 2012
994
637
113
Cant install it after cm10.1 it just wont boot. I have left it for 20 minits,repeated that twice . All was good, checked some option in aroma installer then restart and after that just Blank screen.

Any thoughts? I cant access stock recovery...
Can you access Custom Recovery?

This is due CM10.1 is ext 3 and msginger uses ext 4

From this point, your only option is to flash from sbf and start from 0 (root, sndinit and then install msginger it will work)
Wrong. CM 10.1 is ext4, if anything you got it backwards. And also, if you can access Custom Recovery (CWM or TWRP) then you don't always need to flash an SBF. If the file system format is in fact your problem, then in the Boot Menu there's an option for formatting Data/Cache to EXT3. You can either use that or you can use the Aroma Wiper, which is a lot faster too, and even comes with instructions.
 
  • Like
Reactions: viper.

viper.

Senior Member
Feb 10, 2010
323
51
0
ZAGREB
Can you access Custom Recovery?



Wrong. CM 10.1 is ext4, if anything you got it backwards. And also, if you can access Custom Recovery (CWM or TWRP) then you don't always need to flash an SBF. If the file system format is in fact your problem, then in the Boot Menu there's an option for formatting Data/Cache to EXT3. You can either use that or you can use the Aroma Wiper, which is a lot faster too, and even comes with instructions.
yeah i can access custom recovery. And i did wipe data and cache i have wiped the dalvik cache too.
will try to format it to ext3 or new sbf ..

What do you suggest ,should i stay with 2.2 CEE or should i go to another sbf ?
 
M

mariosanoguera

Guest
yeah i can access custom recovery. And i did wipe data and cache i have wiped the dalvik cache too.
will try to format it to ext3 or new sbf ..

What do you suggest ,should i stay with 2.2 CEE or should i go to another sbf ?
I upgraded to DFL_U3_4.5.2_51-50_SIGNED_USADEFYB25RETLALA007.0R_STABLE45LADEFYRETLA_P008_A014_M001_HWp3_Service1FF and I have no problems at all

before I had JRDNEM_U3_3.4.2_177-005_NORDIC_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTNORD_P003_A001_HWp3_Service1FF and It gave problems (such as in msginger it didnt charge correctly, many bootloops and so, maybe it has nothing to do but I had 0 in any rom since I changed to 4.5.2

How does multitasking work on msginger 5.0? If I close an application (lets say web browser, it automatically hibernates?) or it has to pass a time, or just the process can be deleted by restarting the phone?
 

Antiga Prime

Senior Member
Sep 25, 2012
994
637
113
yeah i can access custom recovery. And i did wipe data and cache i have wiped the dalvik cache too.
will try to format it to ext3 or new sbf ..

What do you suggest ,should i stay with 2.2 CEE or should i go to another sbf ?
If I were you I'd try formatting to EXT3 first, and then reboot and see if it boots up. You can do that from the Boot Menu like I commented earlier.

Actually, if I were you, I'd even skip that step and go straight to the Aroma Wiper and do it all over again, just to be sure. Flash the Aroma Wiper, and it will open up the options. Select the option to Format to EXT3, and wipe System/Data/Cache, all three, and DO NOT REBOOT. Once it's done, just go back and flash the ROM right away.

If you want you can change SBFs, but I wouldn't do it unless there's actually a problem with the partitions. When you flash a ROM it will erase, or should erase, better said, everything in the /system partition anyway, so regarding that, it doesn't really matter which SBF you're on. All the other SMG files of the SBF are the same (as far as I know), except for one of them that contains the radio files which should be specific to the region that the phone was manufactured for. If I'm wrong someone correct me.

I've learned from observation that I get better battery life and signal reception when I use an SBF that was made for a same region that uses the frequencies used in my region. It could have just been placebo or other factors, but it's what I've observed. Then again, the radio files also get replaced when changing the basebands; maybe I've just been deceiving myself all this time! :)
 

walter79

Recognized Developer
Dec 18, 2006
4,100
4,618
263
This is due CM10.1 is ext 3 and msginger uses ext 4

From this point, your only option is to flash from sbf and start from 0 (root, sndinit and then install msginger it will work)

@walter small doubt, I felt that the torch is very low compared to cm7 or cm10

so I searched and I found these are the values to be changed

ro.media.capture.flashIntensity=41
ro.media.capture.torchIntensity=25

what you reccomend me to put? I've put 45 and photos are much better under the same conditions and flash looks brighter, you reccomend me other values or changing other parts from build prop?
MS2Ginger use lower settings for torch because some users (like me) killed the flash light on soc device.

MS2Ginger use ext3 for all partitions and not ext4. Thats why you have to wipe with motorola recovery cache and data if you flash from cm10.x
 

viper.

Senior Member
Feb 10, 2010
323
51
0
ZAGREB
MS2Ginger use lower settings for torch because some users (like me) killed the flash light on soc device.

MS2Ginger use ext3 for all partitions and not ext4. Thats why you have to wipe with motorola recovery cache and data if you flash from cm10.x
Did you killed your flash while it was on for long time or you ve got it killed beacuse MS2ginger is using china rom as base?
Why you havent switched to some other kernel(rom) from EU or USA if the china rom is killing flashes?
Are there any difference between flashes on SOC or Bayer devices? Like Bayer can use more voltage on the flash? Or its all the same ..
:confused:
I am using my flash light very often for biking at night , so i really want to know that .

P.S. Flashed some 4.5.1 SBF ,then MS2ginger and it works .
 
Last edited:

walter79

Recognized Developer
Dec 18, 2006
4,100
4,618
263
2 times using flash light with old froyo china rom killed the flash led.
(it was max. 2s switched on)

Use our flash lights settings they protect your defy. You can change it by your own. But it is your risk.
 
M

mariosanoguera

Guest
great rom! do you reccomend taking pictures at 5mp? or at widescreen walter? if you are going to watch them in the pc 5mp and if they are going to stay on the phone for ever widescreen?

btw.. I got a wierd "engineering call" when I call I don't listen anything but they listen to me, by restarting this bug got solved (before restarting tried youtube and it worked and call in loudspeaker didnt which is wierd)