WARNING:
This update zip use write mot_boot_mode as shell script to run bootmenu,
don't modify it. otherwise, maybe you will get stop at M logo.
NOTICE: This update zip is ONLY for mb511, if you want to update, please check your stock rom.
If you use this update zip at charm(mb502), is unstable, mb502 and mb511 still has some different.
My STOCK ROM VERSION:
Code:
RUTEM_U3_01.14.16_DEBLUR_SIGNED_USARUTH15ND0RTINT056.0R_PDS000_USARUTHEHKTWEMARA_P011_A010_HWp3_1FF.sbf
If you try to call, but can't hear sound or can't registration of the carrier network, try this ROM version to update RC version.
RC version 5: v0.7.4
configure sources
NOTICE:If you want update fix zip, you should use bootmenu to update.When boot at motologo,click click and click "vol -" to enter bootmenu.
->because bootmenu executed by mot_boot_mode, so /system can't umount, only can remount.
--and update zip have to modify updater-script, remount /system.
[2013/11/13]:
last update:
Seems we can use the command of telnetd to do emergency rescue.
I write telnetd as shell script. It's only to execute bootmenu, if someone modify mot_boot_mode maybe cause bootmenu can't execute.
The telnetd will execute by eclair's init_mapphone30_umts.rc. But it's only can use bootmenu to execute adb to do some things (ex. modify mot_boot_mode).
These days, I try using 2ndboot, but still freeze on hbootmod, I don't know why we can't execute hbootmod.
I can't find anything solution, and can't get more message.
For me, it's hard to debug, I'm not kernel developer. I try to understand the source code of hbootmod, should stuck on do_branch.
But I still can't get any idea to solve this question.
Hope someone can complete it, let we can use new kernel.
RC version 5 should can be a stable version.
[2013/10/04]:
RC version 5:
Seems when I try fix camera, has incorrect modify of sensors. Fix incorrect modify.
write shell script /etc/init.d/07cphostapconf, copy /system/etc/wifi/softap/hostapd.conf to /data/misc/wifi/hostapd.conf
modify updater-script, clear /data/dalvik-cache. if already upgraded previous version update zip, should can direct flash RC5, skip double wipe.
[2013/09/26]:
20130926.zip:
I forget modify configure sources of buttonblink.sh.
old buttonblink.sh file will get bad battery life.
[2013/09/19]:
20130919.zip:
According to this, use smartass is more stable, thanks edgarsongla.
modify init.mapphone30_umts.rc, set smartass as default and delete cpufreq_interactive.ko.
[2013/09/18]:
for traditional chinese user:
fork tcime unofficial for flipout.
upload tcime.apk for flipout.
source code
[2013/09/16]:
baseband:
use and modify cyanogenmod4milestone's configure files of mmparts.
but I'm not do full test, should be ok.
reduce reboot times:
seems wakelock cause reboot, I guess.
these steps maybe can reduce reboot times.
disable wi-fi or don't set wi-fi sleep policy at never.
disable Android debugging.
but maybe still has reboot problem. I can't find solution.
[2013/08/28]:
camera:
use and modify CyanogenKobe's configure of libcamera.
fix part of camera. Take picture is normal, solved rotation 90 degree problem. But video recorder still rotation 90 degree.
wifi:
use stock rom's files.
media:
add libraries of 720p files. but 720p still has problem.
[2013/08/15]:
fix part of magnetic sensor, tested by google map.
modify lights code. when enter standby to check notification, if exist set buttons backlight on.
and if already standby when get notification, set blink and backlight on.
delete /system/etc/init.d/99buttonblink, modify /system/xbin/buttonblink.sh(for enter standby and exist notification use).
[2013/08/08]:
seems write to Android services will get bad use of battery.
so write to /system/etc/init.d/99buttonblink, to start service (check blinking of buttons backlight).
[2013/08/01]:
fix notification blinking of buttons(menu, home and back) backlight.
[2013/07/03]:
find the way to compile tiap_drv.ko
-->if get error, try this command then reboot.
Code:
cp /system/etc/wifi/softap/hostapd.conf /data/misc/wifi/hostapd.conf
modify overlay of auto brightness and notification LED.
[2013/06/26]:
use CyanogenModXT720's libaudio.so, ril should be normal.
use CyanogenModXT720's dsp directory.
get some kernel modules from CyanogenModXT720.
-->seems tiap_drv.ko can use, but still has problem, try to fix in next version.
[2013/06/23]:
define open keyboard of orientation by overlay.
modify BoardConfig.mk.
use cyanogenmod4milestone's apns-conf.xml.
use "mka bacon" to compile cm7.
separate gapps:
-->attachments gapps.zip for bootmenu use.
can work:
camera
battd
fmradio
bluetooth
gps
sensors
usb connect
audio
half work:
video
-> 720p has problem.
wifi
->I only use 2G service, so I can't test softap.
ril
->I only use 2G service, so I can't test 3G.
use mknod to replace mv /dev/xxx
[2013/04/01]:
resume original parameter in init.mapphone30_umts.rc
->symlink /dev /dev/netmux
I don't know why I deleted it...
modify /system/bootmenu/2nd-init/init.rc:
/mnt/sdcard -> /sdcard
modify void.fstab:
/mnt/sdcard -> /sdcard
delete /system/etc/init.d/02movedevice
fix sdcard mount question.
replace files by upload zip, and delete /system/etc/init.d/02movedevice. Or wait release new version.
fix in preview version 2.
In terms of audio recorder, following information may help:
Flipout uses Sample Rate '16KHz' or "22KHz" to record sound, NOT '44KHz'. This is why flipout cannot use skype >_<. If you guys are using a recorder that uses Sample Rate "44KHz" (which almost all recorders set as default Sample Rate), you have to change the setting.
No phone to test
>.<
Sorry guy I can't help
May be I can help to fix this bugs.audio,fmradio,sensors,camera,ril&wifi,look this:https://github.com/xn-Dream/android_device_motorola_sage-1,and you can pm me else.
Seems use mb508's libaudio.so can use video(low quality,landscape orientation) and audio recorder.
-- hard decoding still problem, can use some player (like mxplayer) to play with soft decoding.
-- Spirit FM will be no sound.
-- call phone number still no sound.
[2013/04/02]:recompile cm7 with mb508's libaudio.so
Now we can hear sound from the other side , but the other side can't hear what I say .
But use speaker it's no problem.
sim unlock problem
Hi, first thanks for do this ROM :good:
I install but when start now the system want to give a sim unlock code, I was use before so do u have any idea or something that i have to do to solve this problem
Sorry for my english is not my native language
Best regards
phchshow said:
Seems use mb508's libaudio.so can use video(low quality,landscape orientation) and audio recorder.
-- hard decoding still problem, can use some player (like mxplayer) to play with soft decoding.
-- Spirit FM will be no sound.
-- call phone number still no sound.
[2013/04/02]:recompile cm7 with mb508's libaudio.so
Now we can hear sound from the other side , but the other side can't hear what I say .
But use speaker it's no problem.
Click to expand...
Click to collapse
error log
about 3G
3gw.Service 7225 Mobile Network not connected - not roaming
about codec
Error TIOMX_CORE 2045 dlopen libOMX.TI.720P.Decoder.so failed because Cannot load library: load_library[1111]: Library 'libOMX.TI.720P.Decoder.so' not found
Info TI_Video_Decoder 2045 TI Video Decoder
Error OMXCodec 2045 Profile and/or level exceed the decoder's capabilities.
Error MediaPlayer 16597 error (1, -2147483648)
Error MediaPlayer 16597 Error (1,-2147483648)
Error MX.Player.Joint 16597 1st error: what=1 extra=-2147483648
Use 508 libOMX.TI.720P.Decoder.so put into system/lib
Error OMXCodec 2048 [OMX.TI.720P.Decoder] ERROR(0x80001009, 1)
I'm impressed that you finally got it working, but i have a evil kind of Bug around here!
The Play Store vanishes every Reboot, Titanium says it is Frozen and im unable to unfreeze it.
If i can i would provide a logcat in the next hours!
Anyway, awesome to finally see 2.3.7 on MB511 ^^
//EDIT: I connected the Device with the Internet, now it is working fine ^^
everything is working except that when phone reboot version is still 2.1 and nothing changed :/
adout keylayout:
unzip keylayout.zip
--init.mapphone30_umts.rc
--init_prep_keypad.sh
to /system/bootmenu/2nd-init/
chmod 0644 /system/bootmenu/2nd-init/init.mapphone30_umts.rc
chmod 0755 /system/bootmenu/2nd-init/init_prep_keypad.sh
Integrate to fix-20130413.zip.
phchshow said:
adout keylayout:
unzip keylayout.zip
--init.mapphone30_umts.rc
--init_prep_keypad.sh
to /system/bootmenu/2nd-init/
chmod 0644 /system/bootmenu/2nd-init/init.mapphone30_umts.rc
chmod 0755 /system/bootmenu/2nd-init/init_prep_keypad.sh
Click to expand...
Click to collapse
Is This QWERTZ?
Should be QWERTY.
There are two files, ruthp0-keypad.kl and ruthp1-keypad.kl.
use this command
"cat /proc/device-tree/[email protected]/[email protected]/name"
My device get ruthp1-keypad.
If you want to use QWERTZ, you can try replace ruthp0-keypad.kl, ruthp1-keypad.kl, ruthp0-keypad.kcm.bin and ruthp1-keypad.kcm.bin.
Get from QWERTZ version.
ShockBuddy said:
Is This QWERTZ?
Click to expand...
Click to collapse
Maybe can solved Turn on USB storage problem.
Integrate to fix-20130413.zip.
if replug usb, maybe has problem, use killall com.motorola.usb to reset usb.
Hi to all,
Thanks to all that are working on this rom.
Since both models are merged in the same post because the same hardware, I wonder if I can deploy this rom into a Motorola Charm, or if I got to make changes on code, I guess at least have to change some files where refers to 511 to 512, and where refers "Ruth" to "Charm".
What other changes should I do to make this model work?
Thanx for response.
Please help
Please help me, How do i do to work because i have not service,
The problem is SIM NETWOR UNLOCK PIN
Please HELP!!!!
just the key pad related files, I was unable to compile this ROM from source using charm files, I think an update file to replace keypad files with charm should do the trick.
I shall try it and let you know.
there are so many attachments here
please put them into #1
Great job, men!
netmanmac said:
Please help me, How do i do to work because i have not service,
The problem is SIM NETWOR UNLOCK PIN
Please HELP!!!!
Click to expand...
Click to collapse
I dont have the Issue and i haven't inserted any SIM Card, it should be enough to reboot without Sim Card.
If you get to Homescreen, use a Root Explorer and edit /system/build.prop, check if
Code:
keyguard.no_require_sim=xyz
is set to "false", if it isn't in there, add it!
Hope i helped :fingers-crossed:
finally installed.is the screen orientation working good?when i flip out the keyboard the screen orientation remains protrait,pretty annoying!anyway great job,never though i'd have seen cm on flipout!love this device,unlike any other
Hello,
Since many days, i have the message "Camera failed" (echec appareil photo in french) when i open the camera app on my mobile Samsung Galaxy S3 Neo (GT-I9301I).
When i press "OK", the app closes.
Android version : 4.4.2
Current Build number version : KOT49H.I9301IXDUAOF2
I did many tests to solve the problem : install others camera app, factory data reset, install other official french roms or last other country roms from sammobile.com,... but each of them without success.
My mobile is under warranty but the Support Center Samsung near home doesn't want take in charge because my mobile has the micro usb connector broken (the electric charging works but usb connection to pc doesn't works). In detail, they can send it but first I will received a paying quotation (60€ approximately) for the unit broken (micro-usb).
On the other hand, i saw a solution on xda-developers.com was to flash the rom by Odin, but i cannot use this because my micro usb is broken and it is not recognized by any PC. The roms in the early tests was installed after having added them on my sd card inserted in my phone.
To finish, when i install a last camera app from Google play, i noticed that the camera in front works but not the camera in back.
Considering all these items, Does anyone has a solution to solve my camera problem on the Galaxy S3 Neo and more generally on my android ? Do you think my camera at the back should be changed? Sorry for my english. Thanks in advance.
Didier
Juste check this thread https://www.google.com/url?sa=t&sou...QcHCoQ&usg=AFQjCNGVctHwF6ct2wkMZS7EktkBFhCHFw
Hey guys, I know that the G4 doesn't have the greatest camera in the world, but I was just wondering for tinkering/P.O.C. purposes if RAW photos are possible. According to freedcam, this phone is only using the camera1 API, which from what I understand does not natively support RAW capture. Would a custom ROM, like that CM13 build being worked on for example, be able to shoot in RAW format even if the phone doesn't originally support it?
LeifEricson said:
Hey guys, I know that the G4 doesn't have the greatest camera in the world, but I was just wondering for tinkering/P.O.C. purposes if RAW photos are possible. According to freedcam, this phone is only using the camera1 API, which from what I understand does not natively support RAW capture. Would a custom ROM, like that CM13 build being worked on for example, be able to shoot in RAW format even if the phone doesn't originally support it?
Click to expand...
Click to collapse
It seems with Motorola you just need to patch the hal add me on telegram at defcomk them send me the camera.msm**** / camera.vendor.***.so found in /system/lib/hw/
I've seen that defcomg found a solution for moto g5 to get raw working by enabling camera2 API. I want to know if I can use the same terminal command for moto g4 plus to get raw, even if with freedcam only
Martinezjpo said:
I've seen that defcomg found a solution for moto g5 to get raw working by enabling camera2 API. I want to know if I can use the same terminal command for moto g4 plus to get raw, even if with freedcam only
Click to expand...
Click to collapse
It should work the same as Moto G5 plus but it seemed nobody was interested
defcomg said:
It should work the same as Moto G5 plus but it seemed nobody was interested
Click to expand...
Click to collapse
I AM!
I've tried the following codes that you posted here:
Enable Camera 2 API
via editing the build.prop
Code:
persist.camera.HAL3.enabled=1
or
via terminal / shell
Code:
su persist.camera.HAL3.enabled 1
I've tried this code via terminal but returned as "Unknown ID" for the string.
Also, this string at the build.prop wasn't available, so I created, but with no sucess enabling raw.
If you want some files to test, I can help you out. Anyway, I'll look for any string related at the build.prop. If I have any sucess, I'll return here.
Martinezjpo said:
I AM!
I've tried the following codes that you posted here:
Enable Camera 2 API
via editing the build.prop
or
via terminal / shell
I've tried this code via terminal but returned as "Unknown ID" for the string.
Also, this string at the build.prop wasn't available, so I created, but with no sucess enabling raw.
If you want some files to test, I can help you out. Anyway, I'll look for any string related at the build.prop. If I have any sucess, I'll return here.
Click to expand...
Click to collapse
From terminal
Type su grant it permission if it ask
Then type setprop persist.camera.HAL3.enable 1
Reboot then in freedcam clear app data start it check in menu if it's on api2
defcomg said:
From terminal
Type su grant it permission if it ask
Then type setprop persist.camera.HAL3.enable 1
Reboot then in freedcam clear app data start it check in menu if it's on api2
Click to expand...
Click to collapse
The command worked. Camera2 API is now enabled and I was able to enable two raw modes: raw_sensor and raw10. Only raw10 "worked", as the other showed black only.
EDIT1: There are DNGs at the FreeDcam files, but when I've tried to open any, the Moto Files app crash repeatedly.
FreeDcam constantly crashes using the Camera2 API, and I couldn't take any pictures with raw enabled. It just freeze when I hit the trigger button and capture no image. It returns with "Error 4" when doesn't crash.
Also, the 2160p recording option was enabled, but didn't seem to work too. Maybe a tweak in the app would solve these problems?
Martinezjpo said:
The command worked. Camera2 API is now enabled and I was able to enable two raw modes: raw_sensor and raw10. Only raw10 "worked", as the other showed black only.
EDIT1: There are DNGs at the FreeDcam files, but when I've tried to open any, the Moto Files app crash repeatedly.
FreeDcam constantly crashes using the Camera2 API, and I couldn't take any pictures with raw enabled. It just freeze when I hit the trigger button and capture no image. It returns with "Error 4" when doesn't crash.
Also, the 2160p recording option was enabled, but didn't seem to work too. Maybe a tweak in the app would solve these problems?
Click to expand...
Click to collapse
Yeah there is a bug with Moto devices where the camera calibration matrix in the dng becomes invalid rendering it useless there is a workaround for that I'm on telegram @defcomk I'll forward you an apk to test
defcomg said:
Yeah there is a bug with Moto devices where the camera calibration matrix in the dng becomes invalid rendering it useless there is a workaround for that I'm on telegram @defcomk I'll forward you an apk to test
Click to expand...
Click to collapse
Maybe I can help you by testing whatever you're going to develope. ? Seems enabling camera 2 api is not enough for this device. Good luck with your work.
[email protected] said:
Maybe I can help you by testing whatever you're going to develope. ? Seems enabling camera 2 api is not enough for this device. Good luck with your work.
Click to expand...
Click to collapse
I got a g5 plus had the same bug anyway I just hardcoded the metadata that was incorrect all's well
defcomg said:
I got a g5 plus had the same bug anyway I just hardcoded the metadata that was incorrect all's well
Click to expand...
Click to collapse
What changes you made in metadata? Can you help me with that?
Martinezjpo said:
I AM!
I've tried the following codes that you posted here:
Enable Camera 2 API
via editing the build.prop
or
via terminal / shell
I've tried this code via terminal but returned as "Unknown ID" for the string.
Also, this string at the build.prop wasn't available, so I created, but with no sucess enabling raw.
If you want some files to test, I can help you out. Anyway, I'll look for any string related at the build.prop. If I have any sucess, I'll return here.
Click to expand...
Click to collapse
Is it for Moto G5 or G4