Database Users

[Q] GPS.CONF question to the devs!

Could the devs create a something so we can specifiy our location for the gps.conf
1. in the startup.txt
2. or a script at startup where we only need to fill in X => X.pool.*
3. or I could make a map with ALL countries, for example
- Belgium
---gps.conf
- Germany
---gps.conf
- Estland
---gps.conf
and so on. and then at startup maybe someone can make a file selector, android asks you which file it should use for gps.
is any of these options possible? I guess this would be a great help for much people.
sometimes builds crash, all my apps fail when I startup after editing the gps.conf
other times my gps just gets useless, this is all because the root access is not always as easy to get, and when you have it, there can still be consequenses like appcrash of the system each time on startup.

Thanks For the post I'm having GPS issues also - Flashed 4 NAND Roms Changed GPS.Conf and still not getting Sat Fix on GPS

HectiQ said:
Could the devs create a something so we can specifiy our location for the gps.conf
1. in the startup.txt
2. or a script at startup where we only need to fill in X => X.pool.*
3. or I could make a map with ALL countries, for example
- Belgium
---gps.conf
- Germany
---gps.conf
- Estland
---gps.conf
and so on. and then at startup maybe someone can make a file selector, android asks you which file it should use for gps.
is any of these options possible? I guess this would be a great help for much people.
sometimes builds crash, all my apps fail when I startup after editing the gps.conf
other times my gps just gets useless, this is all because the root access is not always as easy to get, and when you have it, there can still be consequenses like appcrash of the system each time on startup.
Click to expand...
Click to collapse
An easy way I found from another thread is to use FasterFix, an app that lets you select the correct X.pool script line based on your location. No need to go and find the correct folder and edit the script. FasterFix even has a custom feature so that you can create your own script to get more specific a fix to the satellites in the region you are in. No more hunting to edit the script line! Also, for the other poster in the United States, I found that if you add the number and period 0. in front of us.pool.ntp.org script line, so it would look like: 0.us.pool.ntp.org, your phone will lock onto the satellites within 20 seconds (at least for me) from a cold start. Use the custom feature in FasterFix to do this. Doing this and using GPS Status first to obtain the AGPS information, the next GPS lock will be within a second or two. Here is a link to FasterFix, hope this helps.
FasterFix: http://forum.samdroid.net/f10/fasterfix-1747/

[ROM][2.3.6] U8860 Modified Port

Disclaimer: I am not responsible for any damage (including, but not limited to, loss of data, non-functional device etc.) which may occur to your device from following the directions (or from any failure to follow the directions) found on this post. Use (and flash) at your own risk.
Credits go to genokolar for actually porting the U8860 2.3.6 firmware to the U8800Pro. This builds upon his port.
You may find his port announcement here, and you can download it from here. Thanks to user Skyline111 for the mirror.
Thanks also go to birdyi, who ported the U8860 2.3.6 firmware to the U8860. His port contained some brilliant things such as CarrierIQ framework removal.
--
This is a 2.3.6 ROM for the U8800Pro based on the U8860 B866 ROM. 2.3.6, naturally, brings a slightly newer version of Gingerbread compared to our 2.3.5 with B540. While I know it's all about CM9 (ICS), MIUI and so on these days, I'm a fan of stock (in the Huawei sense of the term) Gingerbread.
Features (or limitations depending on what you think of some of the following entries) of this ROM:
Rooted (adb also runs as root, too)
(Huawei) DLNA
(Huawei) A task manager that shows open applications with pictures (launching it when pressing Home has disabled in this modification because I found the Recent menu saves more time)
(Huawei) Security Guard, a way of hiding text messages, I think
(Huawei) Traffic Manager – a data counter
(Huawei) Wi-Fi WPS support
(Genokolar) FPS unlocked by default (configurable in enhanced.conf)
(Genokolar) ZRAM (Compcache) enabled
(Genokolar) Changed the autorun.iso path to the image partition so that formatting /data from CWM does not leave you with an empty CD-ROM drive when you plug the phone into a computer
bugreports service turned off entirely so that pressing the volume up button quickly after you've pressed volume down does not leave you with a few seconds' delay and a bugreports folder on your memory card
BusyBox from CM7
Android’s toolbox (poor coreutils replacement; more barebones than BusyBox) has its full set of links installed in /system/bin, so you use Android’s native chmod etc. tools. Why? To match the stock B512 firmware and to ensure developers testing on the U8800Pro correctly hardcode “busybox” in their root programs if needed
Optional lazy CPUfreq governor
Default language and region changed from Chinese – China to English – United Kingdom
Added in boombuler’s AppWidgetPicker
CM7’s Pacman added in to remind you to install Google Apps after adding an account with the Setup Wizard (make sure GApps is installed!)
VoiceDialler.apk added in from B512 firmware (although, to be honest, the microphone quality on my phone is awful…)
Bash shell, fix_permissions script, iwmulticall, MMS.apk, tcpdump and gdbserver and additional ringtones etc. from CyanogenMod (20120107-cm-7.1.0-u8800pro-Geno-en.zip) added in
Phone model changed to Desire HD, so Gameloft games can be bought. This may cause licensing problems with bought Market applications so be careful. (Although, I must admit that giving money to a company that doesn't support our phone seems counter-intuitive.)
Shutdown vibration reduced from 500ms to 100ms because I hate it (especially at night) but understand its usefulness in determining the answer to the question “Has the phone gone off yet?”
Huawei’s god-awful Low Battery notification replaced with a nicer one from CyanogenMod
Widgets actually restore themselves after a reboot! This was fixed by me replacing 2.3.6's PackageManager service with Huawei's 2.3.5 one.
MyCalendar widget from birdyi's port and MyEmail from B512 added in
Fixed proximity sensor dying if the light sensor was on, too.
Stripped down enhanced.conf - only swappiness, VSync and ZRAM settings available. I don't like /system/log.txt being created every time my phone boots and I think using a tool in Android like, say, No-frills CPU Control is the better place to set the frequency. SetXperia has support for setting the phone's CPU voltage.
More languages selectable from the Setup Wizard than just English (US) and Chinese.
Flash Player removed for copyright reasons. You can install it from the Market
Notepad and Richpad removed
Droid Sans Fallback supports more character ranges
Toolbox correctly has "Wi-Fi" instead of "WLAN"
Misc. kernel modules, like in B512, included
But I like the BusyBox tools and want to use them without having to prefix BusyBox everytime!
Just run the bash shell; BusyBox versions of cat, chmod, chown, df, insmod, ln, lsmod, mkdir, mount, mv, rm, rmdir, rmmod, umount, sleep, kill, and ifconfig will become the default while you’re using the bash shell (also nicer, BTW: you get tab-completion, for one) thanks to the CyanogenMod team.
Attempts to remove Carrier IQ. Huawei *do* include Carrier IQ in their firmware.
I’ve done the following to attempt to remove it the best I can:
Edited boot.img to not start Carrier IQ services
Removed Carrier IQ libraries from /system/lib and CiQ binaries from /system/bin
Added lines to build.prop to disable CarrierIQ, taken from the framework.jar file itself.
birdyi has also modified framework.jar to stop the CarrierIQ objects from being instantiated.
Ideally the best way to be Huawei-free is to use CyanogenMod.
I've removed the Cloud+ apps because of this. I've left some Huawei apps in, but I strongly recommend you install PDroid (the patcher works fine with this ROM) and block the more concerning permissions of Huawei system apps.
Kernel changes
Since the kernel genokolar provided with his port had a problem when a program used the light and proximity sensor at the same time – the proximity sensor would die out until the next restart – I took it upon myself to rebuild the kernel available from his github repository with the config from his latest kernel. After comparing his kernel to the source Huawei put out, I could see no code changes that would cause the proximity sensor to die out. Since I was rebuilding the kernel, I thought I’d make a few changes:
Add in the Lazy CPU governor by Ezekeel
Update a patch by stockwell to disable keypad lights (echo 1 > /sys/module/leds_msm_pmic/parameters/disable_button_leds) - use ButtonLock to control
Reverse genokolar’s decision to always allow NV logging – this can be turned on and off from the service menu on a stock ROM anyway…
Set minimum backlight level to 15, from Franco’s kernel. Warning: I haven’t tried setting it to 15 so I don’t know if that value renders the display practically useless, and I don’t know if Android lets you set it to 15 from its settings!
ButtonLock
Not as revolutionary as I'd like it to be, but useful nevertheless. I've written a quick widget, which looks like the Power Saving one, that turns off the button backlight. Useful for when you're reading books through FBReader.
You need to be using my kernel as it has the disable_button_leds patch. The advantage the disable_button_leds patch has over the chmod 444 method is that it doesn't introduce noticable lag. The widget's source is in the same folder.
When pressing the widget's button for the first time, there is a delay as the Superuser allow/deny dialog box takes its time to come up. After accepting, future launches are instantaneous.
If you need something that this ROM doesn’t provide compared to other stock ROMs, I recommend:
Not using it; or
Using a combination of diff, abootimg, Winmerge (or Beyond Compare) and apktool to compare this with genokolar’s original release, and with birdyi's ROM, and add what you want back in
Installation
Note: You must be running firmware version B522 on your device! If you have B540, you need to downgrade. If you have a firmware version lower than B522 (Froyo?), you must upgrade to B522 first. If you're already running a custom ROM, ignore this.
Take out the SIM card if you want the setup wizard to use Wi-Fi during setup.
Install genokolar’s recovery: http://forum.xda-developers.com/showthread.php?t=1343276
Place u8800pro-2.3.6-geno-v1-modified.zip on the internal memory card or an external one (I recommend the internal one to ensure you don’t run into U8800Pro CWM bugs with the external).
Get gapps for Gingerbread and place on your memory card. Find the link using every Android user’s favourite search engine.
I highly recommend using PDroid, but it’s up to you whether you want to use it. If you would like to use it, get the patcher from http://forum.xda-developers.com/showthread.php?t=1357056 and point it to u8800pro-2.3.6-geno-v1-modified.zip. Place the PDroid-v1.27-u8800pro-2.3.6-geno-v1-modified.zip file onto your memory card.
Boot into recovery (make sure that fast boot is turned off in Settings->Applications and hold power and volume up while turning the phone on)
Do a data/factory reset.
Install the ZIPs, starting with u8800pro-2.3.6-geno-v1-modified.zip (obviously).
Reboot!
Install the Google apps (those ones not included in CM's gapps ZIP like YouTube) if desired when prompted – but note that the Market will probably close as you’re doing this as it will automatically update itself.
Downloads
ROM: http://www.mediafire.com/?k0g17z1kraw7b67
SHA512: 4988B123488B8B24732401420DE849E8D8E5632C075A4520F176AA1D64DA0ECF946FF4D4E6CEC4D257EE4C4C999200A93C2CB309FD7B5FE50234A1C5700DEB2D
Modified kernel source (I suck at Git - I really need to read that VCS by Example book I have ): http://www.mediafire.com/download.php?a0022t73q2v7r7d
ButtonLock source (Apache licensed, though I must admit I'm more of a GPL person...): attached.
--
Extras:
genokolar's 5.0.27 recovery for the U8800Pro with the charging animations from https://github.com/Victor-android/android_device_huawei_u8800pro/tree/master/recovery/res/images:
attached.

Anyone tried it?
ill try it this evening I hope it fixes missed calls....
I have B512 official gingerbread, am I good to go?

Too times was a situation, when phone lost connection with wi-fi spot, he see the network, but can't connect. Help reboot.. else working so far without problems, testing..
...
turned off the wi-fi and got the main bug - does not work 3g/2g data transfer, hmm....

bobsido said:
with wi-fi spot, he see the network, but can't connect. Help reboot.. else working so far without problems, testing..
Click to expand...
Click to collapse
Interesting. I've had no problems reconnecting to a network that uses WPA2-PSK and another that uses 802.11x authentication.
turned off the wi-fi and got the main bug - does not work 3g/2g data transfer, hmm....
Click to expand...
Click to collapse
Are your APNs set correctly? In my case 2G works and I've had HSDPA working because when testing the Weather Clock widget (from B522, when I had it in) it would connect using it - I could see the icon in the status bar - and I had the pleasure of having my balance run down each time - I'm not a rich man
Edit: In build.prop, you can try playing with ro.config.hw_fast_dormancy=3 - genokolar had it set to 2, but I changed it back to 3 from the U8800Pro original ROM because I wouldn't be able to connect to my network otherwise.
Hopefully, it's not the case but it could be hardware differences. genokolar, who's work this is based on, being from China, probably has a Unicom U8800Pro, just like I do...
@Zaic
B512? This is for the U8800Pro. I'd advise you not to flash it. I'd recommend using birdyi's ROM. If you're after a certain improvement from this ROM, tell me and I'll try and isolate it for you (as long as it doesn't involve kernel stuff - I don't know how to build U8800 kernels) so that you can use with birdyi's ROM

I have u8800 pro - 100%
My ROM is original unrooted 2.3.5 B512 its one before the latest release which is B540
My ROM still has access to pink screen, otherwise its the same as B540 I guess
SO what should I do first to install this ROM? roll back to 2.2.2 or was it 2.2.3?

Ah, if you're running 2.3.5 already and in the pink screen mode you see a folder called image when connecting your phone to the computer you're ready to go

Hi!
My compliments for the porting of Android 2.3.6 to U8800Pro!
I am using your rom since yesterday and still now I am not having any kind of problems.
Anyway I notice the same bug of the B512 and B540 roms: put your smartphone on screenoff, then wait about 1 minute and fastly unlock the screen and try to pinch to zoom on the home. Sometimes the multitouch doesn't work on every position of your fingers, it only works correctly if your fingers are in the position of principal axes.
Please try to reproduce this bug.
I am using LauncherPro but this bug is indipendent by the launcher (for example I tried also Zeam Launcher, Go Launcher EX, etc etc).
I hope you can solve this bug, maybe kernel-related.
Regards,
kalo86

Hi,
kalo86 said:
My compliments for the porting of Android 2.3.6 to U8800Pro!
Click to expand...
Click to collapse
The honor is genokolar's
I am using your rom since yesterday and still now I am not having any kind of problems.
Click to expand...
Click to collapse
Thanks; it's nice to know that it's working OK on somebody else's device other than mine.
Anyway I notice the same bug of the B512 and B540 roms: put your smartphone on screenoff, then wait about 1 minute and fastly unlock the screen and try to pinch to zoom on the home. Sometimes the multitouch doesn't work on every position of your fingers, it only works correctly if your fingers are in the position of principal axes.
Click to expand...
Click to collapse
Sorry for asking, but how do you pinch to zoom on the home screen? I'm using Go Launcher Ex and I know that that has the swipe up gesture but I can activate that with one finger, anyway.
In any case, have you applied the Synaptics touchscreen update? For me it has increased the touchscreen performance greatly. I had one problem that when after unlocking, the touchscreen wouldn't respond unless I turned the screen off and tried again. The update solved that.
If you want to try it, open the service menu (*#*#2846579#*#*), go to ProjectMenu->Upgrade->Touch screen version query and see if it says "synaptics". If so, put the original Huawei recovery.img back on and put the synaptics.img file in a folder called update on your SD card. Use the recovery's "touchscreen firmware update" update option and it will automatically reboot when it's done.
Best regards,
qwerty12

Oh, really thank you for this "news" about the synaptics touchscreen update!
I have a synaptics too, then I am going to update the firmware.
Another bug, still present in B512, B540, Cyanogen and U8860 port: unplug your battery from the smartphone, insert it again, power on, then open your file manager and try to read the sdcard content. At 99% my sdcard is not read, then I have to reboot my U8800Pro and magically the sdcard is read.
Thanks to You and Genokolar for our development!
Regards,
kalo86
UPDATE: I updated the synaptics touchpanel but I have always the bug of multitouch. It is reproducible when you unlock the screen after a pause of 1 minute (about), then you open the stock browser and try to zoom with the multitouch. It works only if your fingers are on the principal axes and not in other positions. I have this bug on 4 different U8800 Pro! It cannot be a singular problem.
So, I have tried a lot of roms, based on B512, B540, U8860, CyanogenMod 7.1, I am sure I will try this bug on the next release because it's mabe a kernel bug due to the multitouch field.

Video demonstration
This is a video which I just uploaded on YouTube with the real multitouch bug.
This bug is in 4 different U8800 Pro.
http://www.youtube.com/watch?v=avSdW2V8TLg

kalo86 said:
Another bug, still present in B512, B540, Cyanogen and U8860 port: unplug your battery from the smartphone, insert it again, power on, then open your file manager and try to read the sdcard content. At 99% my sdcard is not read, then I have to reboot my U8800Pro and magically the sdcard is read.
Click to expand...
Click to collapse
I really can't reproduce this. I pulled out the battery while it was on, put it back in and started File manager (the one included with Huawei ROMs) and the internal SD card along with my external one were seen fine.
UPDATE: I updated the synaptics touchpanel but I have always the bug of multitouch. It is reproducible when you unlock the screen after a pause of 1 minute (about), then you open the stock browser and try to zoom with the multitouch. It works only if your fingers are on the principal axes and not in other positions. I have this bug on 4 different U8800 Pro! It cannot be a singular problem.
So, I have tried a lot of roms, based on B512, B540, U8860, CyanogenMod 7.1, I am sure I will try this bug on the next release because it's mabe a kernel bug due to the multitouch field.
Click to expand...
Click to collapse
Thanks for the video! Unfortunately I don't know how this can be fixed - I'm not a developer! It was only yesterday I tried looking in the driver to see how I can enable more than two finger recognition but I'm not seeing it...
Best regards,
qwerty12

Sorry for disturbing you, but I have a question: do you have the same bug of the multitouch after the lock-screen?
This is a second video about the same problem:
http://youtu.be/64NvbFJD3rs

qwerty12 said:
I really can't reproduce this. I pulled out the battery while it was on, put it back in and started File manager (the one included with Huawei ROMs) and the internal SD card along with my external one were seen fine.
Click to expand...
Click to collapse
The same here with sd,full power off device, power on then sd card is not mounted and cpu load is almost 100%. after restart or reinserting sd, problem just dissapear. on every rom i tried. i flashed official V100R001C00B512G001Gb (2.3.5) and then tried CM7; u8800+v100r001c00b540g001gb-rooted_geno-v4.

Is FM Radio working in this ROM?

Yes, Radio is working fine

qwerty12 said:
Are your APNs set correctly?
Click to expand...
Click to collapse
i fix APN settings and 3g/2g start work, thanks.. after reflashing wi-fi start work without problem. but after first reflash don`t work home button. they have response, but nothing happen. i secondary reflash phone, without wipe data/cash and home button start to work correct.. now tests are continuing

kalo86 said:
Sorry for disturbing you, but I have a question: do you have the same bug of the multitouch after the lock-screen?
This is a second video about the same problem:
http://youtu.be/64NvbFJD3rs
Click to expand...
Click to collapse
A little bit - after unlocking, I can do the multitouch gesture and phone will respond like it's supposed to but I have seen twice that it has not responded to me; I have to do it twice more...
Barracuda72 said:
Is FM Radio working in this ROM?
Click to expand...
Click to collapse
Like kalo86 said, it is indeed
bobsido said:
i fix APN settings and 3g/2g start work, thanks.. after reflashing wi-fi start work without problem. but after first reflash don`t work home button. they have response, but nothing happen. i secondary reflash phone, without wipe data/cash and home button start to work correct.. now tests are continuing
Click to expand...
Click to collapse
Please do let me know if you come across more problems

Zaic said:
Anyone tried it?
ill try it this evening I hope it fixes missed calls....
I have B512 official gingerbread, am I good to go?
Click to expand...
Click to collapse
So, any missed calls?

If someone wants to help the Community to understand the sdcard mount bug, please have a look here: http://forum.xda-developers.com/showthread.php?t=1483519
This is a poll, please vote!
Best regards,
kalo86

Zyzas said:
So, any missed calls?
Click to expand...
Click to collapse
Haven't had time to install this ROM yet.... but ill report as soon as I know

[stop-dev][TWHK][cm7][flipout-mb511-ruth][testing] status: become stable

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

Enabling The Double Tap To Wake Up in Lineage OS and Resurrection Remix

Hi guys;
I found a way to enable the double tap to wake up in LineageOS and RR for the mi mix.
Here it comes:
1: Donwload the Root Explorer and the QuickEdit;
2: With Root Explorer, go to sys/bus/i2c/12-0038/wakeup-mode;
3: Open that with Quick Edit and change the value "0" to "1";
4: Save it;
5: Have fun.
This is my first post here, take easy guys. I searched here for a solution for this problem, but didn't find anything about this two roms.
Thanks if it works!
PS: The only problem is that when you reboot the system, the system automatically returns to "0", so you will have to do the whole process again every time you restart the device. Does anyone know the solution to leave this fixed by default?

I'll add that to init process in ramdisk and enable it in source again. In build 0412 it is disabled, but it seems to work anyway Thx for finding it out.

pappschlumpf said:
I'll add that to init process in ramdisk and enable it in source again. In build 0412 it is disabled, but it seems to work anyway Thx for finding it out.
Click to expand...
Click to collapse
No problem! This is a tweak that I cant live without! And, congratulations for the amazing job. The ROM is perfect to me, Im using as my daily driver. The only 2 problens that I found, is this one and the low volume in Calls. Thanks to provide this ROM, I really appreciated.

Great! Is working fine...

Hello ,
works fine , but after reboot it is back to"0"
mfg , hjf

hjfisch said:
Hello ,
works fine , but after reboot it is back to"0"
mfg , hjf
Click to expand...
Click to collapse
As I said

Couldn't i just change the value and save the file as read only? I'm kind of afraid to try it out but wouldn't that work?

Blackphantom said:
Couldn't i just change the value and save the file as read only? I'm kind of afraid to try it out but wouldn't that work?
Click to expand...
Click to collapse
Will work. Just change the value to 1, save and exit. But, every time that you reboot the device, u will need make the process again.

I understand that. My question was if i save the file as read only wouldn't that "deny" the system from changing the value even after rebooting?

Blackphantom said:
I understand that. My question was if i save the file as read only wouldn't that "deny" the system from changing the value even after rebooting?
Click to expand...
Click to collapse
Dont know. Could you try and post the result?

Blackphantom said:
I understand that. My question was if i save the file as read only wouldn't that "deny" the system from changing the value even after rebooting?
Click to expand...
Click to collapse
NO, as /sys is just a mountpoint for a virtual Filesystem (type sysfs)
So basically, everything under /sys/ is virtual, so no real Files, so no persistance after a reboot. At least not by interacting with sysfs.
This is the Linux way of making runtime live adaptations of certain hardware or software features.
Let me give you an example.
On a regular Dektop-Linux, if you do:
>> echo "1" > /sys/block/sda/device/delete
on the command line, you tell the kernel to flush the caches of the sda disk and spin it down. (so you could safely hotswap)
and if you do not replace your disk, but now want to get that disk spinning again, you put:
>> echo "0 0 0" > /sys/bus/scsi/devices/host1/scsi_host/host1/scan
into console.
So some of the Files there are read only (in like nothing happens when you change the content) , and others can be tampered with, but every change is gone after reboot.
except when you can manage to let some startup-skript make those changes, or you can edit the kernel-source default initialisation variables.

rootgremlin said:
NO, as /sys is just a mountpoint for a virtual Filesystem (type sysfs)
So basically, everything under /sys/ is virtual, so no real Files, so no persistance after a reboot. At least not by interacting with sysfs.
This is the Linux way of making runtime live adaptations of certain hardware or software features.
Let me give you an example.
On a regular Dektop-Linux, if you do:
>> echo "1" > /sys/block/sda/device/delete
on the command line, you tell the kernel to flush the caches of the sda disk and spin it down. (so you could safely hotswap)
and if you do not replace your disk, but now want to get that disk spinning again, you put:
>> echo "0 0 0" > /sys/bus/scsi/devices/host1/scsi_host/host1/scan
into console.
So some of the Files there are read only (in like nothing happens when you change the content) , and others can be tampered with, but every change is gone after reboot.
except when you can manage to let some startup-skript make those changes, or you can edit the kernel-source default initialisation variables.
Click to expand...
Click to collapse
Yeah that makes sense. I tried it and realized that it was set back to zero every time i restarted so i figured it would be something like that. Luckily DT2W works now in the build so we don't have to do that anymore.
Thanks for the explanation though. Really appreciated.

Hey there
i followed your steps but i cant seem to find the 12-0038 folder after i2c. Any thoughts?

If you're using Lineage just install the DragonXiaKernel. Double Tap To Wake is working fine.

Tiago A said:
Hi guys;
I found a way to enable the double tap to wake up in LineageOS and RR for the mi mix.
Here it comes:
1: Donwload the Root Explorer and the QuickEdit;
2: With Root Explorer, go to sys/bus/i2c/12-0038/wakeup-mode;
3: Open that with Quick Edit and change the value "0" to "1";
4: Save it;
5: Have fun.
This is my first post here, take easy guys. I searched here for a solution for this problem, but didn't find anything about this two roms.
Thanks if it works!
PS: The only problem is that when you reboot the system, the system automatically returns to "0", so you will have to do the whole process again every time you restart the device. Does anyone know the solution to leave this fixed by default?
Click to expand...
Click to collapse
I installed "lineage-14.1-20170415-UNOFFICIAL-X3". I only get path till sys/bus/i2c/
There is no 12-0038/ folder. Can you help me out on this? I need it badly.

same here, no 12-0038
running smooth with 14.1-20170725-NIGHTLY-hammerhead though

Same for me on 14.1 LG g4 can't t find the file

Ls .../i2c/devices/
0-0006
0-a004
0-a006
1-0051
10-0048
11-003b
...
There iz no 12-0038 in both /i2c/ and /i2c/devices/
:crying:

Vipxpert said:
Ls .../i2c/devices/
0-0006
0-a004
0-a006
1-0051
10-0048
11-003b
...
There iz no 12-0038 in both /i2c/ and /i2c/devices/
:crying:
Click to expand...
Click to collapse
DT2W is working in RR (Oreo) just fine and I assume it's the same for Lineage 15.1 (Oreo). Which ROM are you using?

gavin19 said:
DT2W is working in RR (Oreo) just fine and I assume it's the same for Lineage 15.1 (Oreo). Which ROM are you using?
Click to expand...
Click to collapse
RR oreo as u said !

[GUIDE] How to properly change / remove zoom error in eui/miuipro

Guys as we all know when we root our eui we get stuck with zoom sheeting on every app.
But I have found out a fix.
First things first tools required:
1:terminal emulator
2:build prop editor / root file manager
Fix:
Go ahead and open terminal emulator.
Enter the following code
Su
And click enter
wm density ###
### us where you input the amount of DPI you want 420 is normal DPI
-1st part done!
Now open build prop editor
Next Look for "ro.sf.lcd_density=###"
Change ### to previous value which you have set in terminal emulator.
Reboot!
Done!
Now you may think I might have done this in some DPI app but it will make more problems than solving it . believe me!
Special thanks my friend: snehashish
For providing me the fix
Hit thanks if you like my work!
Cheers:highfive:

Guys you can also use this to properly change DPI in eui and miui pro without font or clock glitches.:good:

Gautham V said:
Guys as we all know when we root our eui we get stuck with zoom sheeting on every app.
But I have found out a fix.
First things first tools required:
1:terminal emulator
2:build prop editor / root file manager
Fix:
Go ahead and open terminal emulator.
Enter the following code
Su
And click enter
wm density ###
### us where you input the amount of DPI you want 420 is normal DPI
-1st part done!
Now open build prop editor
Next Look for "ro.sf.lcd_density=###"
Change ### to previous value which you have set in terminal emulator.
Reboot!
Done!
Now you may think I might have done this in some DPI app but it will make more problems than solving it . believe me!
Special thanks my friend: snehashish
For providing me the fix
Hit thanks if you like my work!
Cheers:highfive:
Click to expand...
Click to collapse
The first part works. The second part does not: there is no ro.sf.lcd_density setting in the build.prop. And the settings app still reports the display as zoomed.

emkorial said:
The first part works. The second part does not: there is no ro.sf.lcd_density setting in the build.prop. And the settings app still reports the display as zoomed.
Click to expand...
Click to collapse
It does still say zoomed in settings but it is not

emkorial said:
The first part works. The second part does not: there is no ro.sf.lcd_density setting in the build.prop. And the settings app still reports the display as zoomed.
Click to expand...
Click to collapse
You wil fund the line ro.sf.lcd_density in all ROM except eUI, in eUI you can search for persist.ro.sf.lcd_density
Or similar to this one but that line start with persist

after doing this trick in miui pro rom i am continuously getting an error that system stopped

Rajashekar0675 said:
after doing this trick in miui pro rom i am continuously getting an error that system stopped
Click to expand...
Click to collapse
You must have messed somewhere

I tried the fix and didnt get any errors, but it still randomly switches from zoom mode to normal when opening apps. I really only notice it in gmail and chrome.

Guess changing the DPI has resulted in zoomed in pictures when cropping, cropping happens right as the markers indicate but the crop preview is zoomed in which makes it impossible to edit pictures. Is there a solution/hack for this?