yashsingh1/xdaforums huggingface dataset:
[Flipout and Charm General] Skellie:
Great news! ~ And a doubt

You guys don't have a clue of how I am happy with this being developed released around here.

However, I have no idea of how to flashing my device into a Linux distro. I don't use Microsoft Windows so... have you guys any instructions of how to make this upgrade using a Linux system?

Thanks for the great job! :D
[Flipout and Charm General] moodroid:
If you do an internet search for "rsd lite linux" it looks like there are solutions available?

Also, I didn't have to flash in order to install this rom - I just installed cwm and it all worked, although I did need to flash to go back to 2.1, but there may be ways around that too.
[Flipout and Charm General] Skellie:
Thanks 4 reply

So the installation of the CWM can be done just using the apk, right? Or it need some workaround?

And I'm sorry for any misunderstanding regarding the instructions posted here. English is not my native language so, sometimes is better ask a few more questions to get everything understood. Hope not to bother you guys. :p
[Flipout and Charm General] ShockBuddy:
Yes, use the apk. You can only enter CWM using this App!

You should be able to backup your 2.1 within this CWM.
[Flipout and Charm General] Skellie:
Gingerbread running.

I didn't have tested the Bluetooth yet but apart from the problems already mentioned by you guys, the WiFi doesn't work well here. I'm getting some problems to connect to a network.

Anyways, how can I help to improve this ROM?
[Flipout and Charm General] ShockBuddy:
Bluetooth File Transfer working without issues, WiFi is okay on my device.

Sent from somewhere...
[Flipout and Charm General] Skellie:
Bluetooth is working here. WiFi, after reboot the device twice, is working.

The mainly problem right now is the several times that Flipout reboot itself. And yes, I know that something like that could be happening.

And yet I'm waiting to know how I can help to improve this ROM. :cool:

Once more, thanks guys, for all the help and by this ROM!
[Flipout and Charm General] xxxo:
I deleted ROM manager before install, try cleaning all battery terminals,worked on my old phone
[Flipout and Charm General] phchshow:
Use cyanogenmod4milestone's libaudio.so to recompile cm7.

fix fmradio and Integrate fix-20130413.zip to preview version 3.
[Flipout and Charm General] Skellie:
Updates.

I have tested Bluetooth. No problems to send and receive files, but can't connect to wireless headsets. I tried with two devices of this type: a Nokia and a Motorola (model S305).

About the libaudio.so, is there a copy of this file on XDA? I Googled it and I just find people complaining about problemas in they Motorola devices running CM7.

NOTE: I've installed the fix-20130413.zip.

By the way, my main problem in this case is with the registration of my SIM Card on the carrier network.
[Flipout and Charm General] osk386:
Ok after some changes I have an excellent connection to my GSM network 3.5G on CHARM MB502 but still with the weird keypad layout, and most important I can hear with very good quality the people on the other side but they dont to me.

I changed kl files but still the same. :mad:

---------- Post added at 04:15 PM ---------- Previous post was at 03:57 PM ----------

Copy the original eclair bp_nvm_default folder to sdcard

then install the RUTH ROM

then replace all the files in /system/etc/motorola/bp_nvm_default folder with the sdcard/bp_nvm_default files::: REPLACE FILES NOT THE FOLDER SO DON'T DELETE ANY OTHER FILE

set permissions to 664

then reboot in recovery mode and wipe data and finally reboot system

now you can use your GSM network with your SIM and your signal will be the best ... like the original.

:good:
[Flipout and Charm General] ShockBuddy:
You forgot That this Rom is built for MB511 Ruth Flipout, Not charm.

Someone could try to Port this Rom over to charm, maybe Transfering some Files from stock charm to this Rom, dont Know much about it.

Sent from somewhere...
[Flipout and Charm General] phchshow:
you should try compile cm7 for charm.

about keypad:

check getprop about sholes-keypad

# getprop | grep sholes-keypad

[hw.keyboards.0.devname]: [sholes-keypad]

[hw.keyboards.131072.devname]: [sholes-keypad]

and check your keypad

#cat /proc/device-tree/System@0/Keypad@0/name

my devices is ruthp1-keypad

you can lookup /init_prep_keypad.sh. then you will know how to use charm's keylayout and keychars.
[Flipout and Charm General] osk386:
Thanx... pscshow, I know that compiling rom is a hard work to do, but dont know much about that, i think i will spend my weekend on that! :cyclops:

I follow your suggestion abt keypad, and works!

I copied the kelayout and keychars files from the original system to the custom rom, set permissions and run the init_prep_keypad.sh.

thanks a lot.

About phone call error that people can't hear at the other side of the phone, I've reviewed the logcat and it shows some errors when make a call, the first error is in AudioMsgHandler : Permission Denied

other AudioMgrTAPI: AUDMGR_setMuteState() failed

and these repeat many times while the call is active.
[Flipout and Charm General] lennonkaufmann:
I upgraded to version 0.6.3. Still no network here. Baseband version: epu_u_02.38.00
[Flipout and Charm General] osk386:
Did you follow my instructions about putting original baseband files into custom rom bp_nvm_default folder?

:confused:

---------- Post added at 01:52 PM ---------- Previous post was at 01:04 PM ----------

this is the full logcat just when call started (I take only Debug and Errors):

D/AudioMgrTAPI(2068): AUDMGR_enableVoicePath() called

D/AudioMgrTAPI(2068): Client fd 33 sending message ID 2

D/AudioMsgHandler(2960): Received AUD_MSG_TAPI_ENABLE_VOICEPATH from socket client fd 20

D/AudioMgrIPC(2960): am_aipcm_voice_call_enable() called with enable_disable = 1

D/AudioMgrIPC(2960): Message sent for message id 9

D/AudioMgrTAPI(2068): Client fd 33 received reply for message ID 2

D/AudioMgrIPC(2960): select returned, need to do a read

D/AudioMgrIPC(2960): ID 0x8000, Tag 0x8100: Ack received for message with id = 9

D/AudioMgrTAPI(2014): AUDMGR_setMuteState() called with mic_spkr=1 and mute_setting=0

E/AudioMsgHandler(2014): Error:Connection failed: Permission denied

E/AudioMgrTAPI(2014): Error when initializing the socket connection

E/AudioMgrTAPI(2014): AUDMGR_setMuteState() failed

D/AudioMgrTAPI(2014): AUDMGR_setMuteState() called with mic_spkr=1 and mute_setting=0

E/AudioMsgHandler(2014): Error:Connection failed: Permission denied

E/AudioMgrTAPI(2014): Error when initializing the socket connection

E/AudioMgrTAPI(2014): AUDMGR_setMuteState() failed

I think this line refferes to mute when calling:

D/AudioMgrIPC(2960): am_aipcm_voice_call_enable() called with enable_disable = 1

:fingers-crossed:
[Flipout and Charm General] lennonkaufmann:
The Rom is already quite stable, I think that soon the FINAL version comes out.
[Flipout and Charm General] inaroom:
it's stable,the only thing holding me back for daily use is the portrait mode when keyboard flipped out and the speaker issue in calling..by the way how is battery life?mine is very very short
[Flipout and Charm General] ShockBuddy:
I can confirm this, battery is awful!

But im following this, of course.

Sent from somewhere...
[Flipout and Charm General] lennonkaufmann:
Disabled the option "Auto-rotate screen" in settings the screen. So he does not rotate the screen in all applications. Only in some rare cases.

My battery always lasted little .

Normal functioning 3G here ...

I can not move apps to SD , I tried Link2SD, App2SD. And the native ...
[Flipout and Charm General] ShockBuddy:
Same here!
[Flipout and Charm General] laluth:
try it

http://android.doshaska.net/app2sd
[Flipout and Charm General] Skellie:
How the things are going in Brazil.

The battery life is almost normal. But I don't know if it is working this way because some other things are not working.

Still having problems to get registered in the carrier network. So GSM/WCDMA(HSDPA -- simply 2G/3G) is not working and it's pretty sad. :crying:

I've replaced the files in the /system/etc/motorola/bp_nvm_default folder as was recommended to do and... boom! I rebooted the device and I've got a loop process forever. So at this very moment I flashed Eclair into MB511 again. Of course I'm going back to Gingerbread and restart all the tests. So if you guys want some log information or anything else, let me know.

PS: before the loop process thing, GB had problems to write into SD card. The system could read but not write anything in the SD card, which means that many apps doesn't worked the way they should. I'm rooting the device right now and I'll keep you guys posted about my situation.

And sorry about my English. Isn't good but it's not that bad, I guess. LOL ~ Still improving.
[Flipout and Charm General] lennonkaufmann:
Um brasileiro na parada , rs . Tive o mesmo problema de registrar a rede . Troquei os arquivos e parou de funcionar a ROM . É o seguinte manin , salva os arquivos da pasta bp_nvm_default no cartão SD e passa para o PC , vá nessa pasta , selecione TODOS arquivos e copie . Abra o 0.6.3.zip (Arquivo da ROM) com o WinRAR . vá abrindo as pastas /system/etc/motorola/bp_nvm_default CTRL+V e aperta enter na tela que aparecer . Assim irá substituir os arquivos da pasta bp_nvm_default da Custom ROM . Feche o WinRAR . Passe o 0.6.3.zip denovo para o celular , e reinstale .

For anyone who is having the same problem registry network. Replace the file with the Custom ROM files from your baseband to WinRAR.

Reinstall using the 0.6.3 file you modified ...

Failure continues giving
[Flipout and Charm General] Skellie:
Brazucas na rede!

Cara, muda pro 7zip. É melhor que o WinRAR e, é gratuito. Software de código aberto: http://www.7-zip.org/

E olha qu'eu nem uso Windows. :P

Pois é. Tentei fazer a mudança enquanto o sistema rodava e não foi a melhor opção. Já fiz exatamente o que você indicou. Só não reinstalei o Gingebread ainda porque tou checando os arquivos responsáveis pelo GPS, que também, não funcionou aqui.

Cê tá trabalhando no desenvolvimento da ROM ou só acompanhando o andamento?
[Flipout and Charm General] ShockBuddy:
XDA: Speak a English!? (Insider zing xD)

But please speak English ^^

Sent from somewhere...
[Flipout and Charm General] Skellie:
Back to English! :)

Yeah, I know. I know! lol

Sorry. That happened because we are Brazilians and we've just figured it out a few minutes ago. Anyways, we haven't post anything too much different of what you guys have did, when giving instructions.

Ultimately, sorry about that.
[Flipout and Charm General] osk386:
Ok skellie try follow these steps:

install v0.6.3 ruth rom:

Turn on your device:

Then connect cable, (I suppose your android is in Developer mode)

Open command line and path to your ADB location.

Run

adb devices

to verify you have connection with your device

Then run

adb shell
su

You must be in superuser mode, so you will see # prompt instead $ in the shell

now mount system to read,write

mount -o remount,rw /dev/block/mtdblock7 /system

Then copy files to your system (my files are in /sdcard/bp_nvm_default/)

cp /sdcard/bp_nvm_default/* /system/etc/motorola/bp_nvm_default

Now set permissions:

chmod 0644 /system/etc/motorola/bp_nvm_default/*

Then exit from su and exit from shell

exit
exit

Now in windows shell run:

adb reboot recovery

System will rebbot in recovery mode.

Finally and mandatory select wipe data/factory reset -- Yes delete all user data -- reboot system now

I hope this quick guide function to fix your GSM connection. :o

saludos

---------- Post added at 02:40 PM ---------- Previous post was at 02:25 PM ----------

Ok skellie try follow these steps:

install v0.6.3 ruth rom:

Turn on your device:

Then connect cable, (I suppose your android is in Developer mode)

Open command line and path to your ADB location.

Run

adb devices

to verify you have connection with your device

Then run

adb shell
su

You must be in superuser mode, so you will see # prompt instead $ in the shell

now mount system to read,write

mount -o remount,rw /dev/block/mtdblock7 /system

Then copy files to your system (my files are in /sdcard/bp_nvm_default/)

cp /sdcard/bp_nvm_default/* /system/etc/motorola/bp_nvm_default

Now set permissions:

chmod 0644 /system/etc/motorola/bp_nvm_default/*

Then exit from su and exit from shell

exit
exit

Now in windows shell run:

adb reboot recovery

System will rebbot in recovery mode.

Finally and mandatory select wipe data/factory reset -- Yes delete all user data -- reboot system now

I hope this quick guide function to fix your GSM connection. :o

saludos
[Flipout and Charm General] Skellie:
Oh, boy.

Adb wasn't working (even over the air) this time, and I tried again to copy and replace all the needed files. Except that I followed your step-by-step and the phone still in loop process. No boot at all. So I'm flashing Eclair again.

Any ideas?
[Flipout and Charm General] osk386:
No errors log or anything else?

Did you flash the original rom from pschshow?

What do you mean with adb wasn't working?

try reviewing the /system/etc/motorola/bp_nvm_default folder before reboot, on gingerbread after copy files

check that all files have the correct permissions

on adb with su :

# cd /system/etc/motorola/bp_nvm_default
# ls -l
[Flipout and Charm General] lennonkaufmann:
Só acompanhando ...

Entendo poucas coisas ...

move apps to SD without fail?
[Flipout and Charm General] phchshow:
if you update to preview version, you can use bootmenu to connect adb.

When boot at moto logo , click click click " VOL - ", enter the bootmenu, then use tools->ADB Daemon.

I will check sdcard write problem.
[Flipout and Charm General] inaroom:
nope, mine always rotate to portrait when flip out the keyboard..wich makes the qwerty a bit useless,sadly
[Flipout and Charm General] phchshow:
about app2sd:

-->compile kernel modules:

---dm-mod.ko

---dm-crypt.ko

---twofish_common.ko

---twofish.ko

modify init.rc and init.mapphone30_umts.rc.

20130501.zip should can fix app2sd.
[Flipout and Charm General] ShockBuddy:
In combination with my pretty much usage of These keys (means they dont react well) its a pain XD

But on Xperia Arc S with Swype, im much faster @ writing ^^

Sent from somewhere...
[Flipout and Charm General] Alawey94:
Wont make phone calls and week signal :(
[Flipout and Charm General] xxxo:
I just added APN and 3g was working in Europe,install a lighter launcher for better battery I use lightning,and rotation locker sorts landscape out,and I am happy,thanks OP
[Flipout and Charm General] lennonkaufmann:
I use Go Launcher PRO. It has the same option , Lighter Launcher. More themes and accepts multiple hard settings

I use Go SMS PRO is an SMS messenger multiple hard settings, themes, etc. etc..
[Flipout and Charm General] ShockBuddy:
Go Apps are eating much Ram, so be warned!

Sent from somewhere...
[Flipout and Charm General] laluth:
replace apns-conf.xml on system/etc . 3G should be working.
[Flipout and Charm General] lennonkaufmann:
304MB free. Ram is no problem in MB511 are 512 ram ...

My microphone is muted D: .
[Flipout and Charm General] inaroom:
i use adw launcher ex, how long your battery?mine doesn't reach a day,in idle, that mean without touching the phone it will get out of battery before evening...but my battery might be a bit exhausted, i was thinking about getting a 1200mah battery on the bay,they're like 5 or 6 $

gonna try rotation locker right away thanks!
[Flipout and Charm General] phchshow:
about sensors:

-->add open keyboard event to sensor.

-->modify init.mapphone30_umts.rc:

---add setprop hw.keypad 1

---for open keyboard event to sensor.

about open keyboard of orientation:

method 1:

-->modify cm7 sources frameworks/base/services/java/com/android/server/WindowManagerService.java

---near 4579 line, add

try{
Thread.sleep(50);

if(android.os.SystemProperties.get("hw.keypad.init").toString().equals("")
&& android.os.SystemProperties.get("hw.keypad").toString().charAt(0)=='1'
){
android.os.SystemProperties.set("hw.keypad.init","finish");
Configuration config = mContext.getResources().getConfiguration();
if(config.hardKeyboardHidden != config.HARDKEYBOARDHIDDEN_YES){
android.os.SystemProperties.set("hw.keypad","0");
rotation = 0;
}
}
else{
Slog.i(TAG, "hw.keypad:"+android.os.SystemProperties.get("hw.keypad").toString());
if(android.os.SystemProperties.get("hw.keypad").toString().charAt(0)=='0')
rotation = 0;
}
}
catch(Exception Rotationex){
Slog.i(TAG,"Error get hw.keypad");
}

check keyboard status to set rotation.

20130506.zip should can fix 3 axis accelerometer and orientation problem, maybe need double wipe.

fix in preview version 4.

method 2:

seems can define open keyboard of orientation by overlay.

<!-- The number of degrees to rotate the display when the keyboard is open. -->
<integer name="config_lidOpenRotation">0</integer>

<!-- Indicate whether the lid state impacts the accessibility of
the physical keyboard. 0 means it doesn't, 1 means it is accessible
when the lid is open, 2 means it is accessible when the lid is
closed. The default is 1. -->
<integer name="config_lidKeyboardAccessibility">1</integer>

<!-- Indicate whether the lid state impacts the accessibility of
the physical keyboard. 0 means it doesn't, 1 means it is accessible
when the lid is open, 2 means it is accessible when the lid is
closed. The default is 0. -->
<integer name="config_lidNavigationAccessibility">0</integer>
[Flipout and Charm General] xt610:
Good Afternoon, of course you apologize for my bad English I'm using a translator.

Well the point I want to thank you for the effort you are doing and these words are to encourage him to continue in this improvement. I want to share my experience with you, my girlfriend has a long flipout 2/3 years, and I try to improve it handle all because I could not install many applications and your phone is always slow and she was angry then decided to compare another phone and to flipout put it in a drawer.

Well I always wanted to give this cel use because I think differently to everyone, is pretty little.

Well a few weeks ago I saw this thread and then look for this cel dusty saved and returned to give life thanks to you.

Thank you very much and all the time I'm aware of the advances that are emerging in order to improve this rom.

I want to say that many people rely on these improved to remember this cel and return to life.

Thank you. Since the end of the world.
[Flipout and Charm General] xinbada007:
It seems the 'USB Mode' is very, very, and very buggy. I have to reboot many, many, and many times to get a lucky chance for a working 'USB Mode'. For most of the time, nothing happened while plugging usb cable.

Do you guys have this problem ?
[Flipout and Charm General] coca-cola_:
need help

I get an error message:

Finding update package...

Opening update package...

Installing update...

Installation aborted.

Can someone help me, please?
[Flipout and Charm General] ShockBuddy:
Mounted /System/ ?

Sent from somewhere...

(Specs: Arc S "ayame" \ 3.0.8 Kernel nAa \ moAOKP \ Flow Theme CM10, Dev Device Moto MB511 2.3.7 CM7)
[Flipout and Charm General] phchshow:
It's bug. Because Usb relation files are from eclair, some eclair class not found in gingerbread, but when you connect usb, you can use terminal and use killall com.motorola.usb to reconnect usb.

I will try write Listener to auto killall com.motorola.usb, but not now.

Or hope someone can write gingerbread version for flipout.
[Flipout and Charm General] coca-cola_:
Yes, i followed the steps :(
[Flipout and Charm General] ShockBuddy:
Maybe your package is bugged, try to open it on your PC or Download it again!

Also make sure you follow my Guide STEP BY STEP!

http://xdaforums.com/showthread.php?t=2226058
[Flipout and Charm General] lennonkaufmann:
My microphone is muted, the problem is in the ROM.
[Flipout and Charm General] xinbada007:
That's good mate. Take time and I can wait...

I saw you had added a 'overclock.ko' module into CM7 rom. That's nice and perfect cause I always overclock to 1GHz when using flipout. But with this rom I found it is very difficult to overclcok. For example, I tried to set max_vsel/max_rate to '66'/'1000' which is the most stable combination I've found on my flipout with eclair(use this combination for more than one year), but failed with CM7. I also tried to set a lower rate such as 900MHz, but it also only run for several minutes and freeze&reboot automatically again. Any idea about this?

Thanks very much.
[Flipout and Charm General] reggiexp:
soo good news this phone gets a new life^^

i mean some one is developing something, stil have this phone some where in a closet^^
[Flipout and Charm General] lennonkaufmann:
Because the owner of the topic does not make a forum post CyanongenMod?

With their help the ROM would be completed faster.
[Flipout and Charm General] coca-cola_:
I found another Error. After "wipe data/ factory reset"..

E: Can't mount /cache/recovery/log

E: Can't open /cache/recovery/log

E: Can't mount /cache/recovery/last_log

E: Can't open /cache/recovery/last_log
[Flipout and Charm General] osk386:
Hi, i have a question: proximity sensor is working on your devices?, I mean screen turns off when you are closing telephone to your head on calling??

thanX.

:cyclops:
[Flipout and Charm General] inaroom:
might be wrong, but there's no proximity sensor...but someone wil confirm you

i have bad problems with battery life.got the new battery but it last really short as the other one,charged the phone at 9.30 am, by 6 pm the phone was dead, without using it. i already have advanced task killer, don't know what could be the problem..
[Flipout and Charm General] phchshow:
proximity sensor -> /dev/sfh7743

I remember it's ok. I test add code to show log. It's work.

But I forget when closing phone the screen is turns off or not.

These days so busy, can't test at now.
[Flipout and Charm General] osk386:
Yes sensor works, but the functionality doesn't! at least in my phone.

:eek:
[Flipout and Charm General] laluth:
Found bug

random reboot

last logcat before reboot:

18:37:01.932 Warning KeyCharacterMap 5612 Can't open keycharmap file

18:37:01.932 Warning KeyCharacterMap 5612 Error loading keycharmap file '/system/usr/keychars/qtouch-touchscreen.kcm.bin'. hw.keyboards.65537.devname='qtouch-touchscreen'

18:37:01.932 Warning KeyCharacterMap 5612 Using default keymap: /system/usr/keychars/qwerty.kcm.bin

18:37:02.057 Debug dalvikvm 5612 GC_CONCURRENT freed 111K, 44% free 3366K/5959K, external 127K/512K, paused 4ms+3ms
[Flipout and Charm General] phchshow:
When I close keypad, It's no problem.

But open keypad, the sensor seems not get event.
[Flipout and Charm General] xinbada007:
does overclock ever work on your phone?
[Flipout and Charm General] phchshow:
My overclock configure

I use setcpu's stress test, about 165 minutes(9956482 ms) no errors.

battery 100% -> 30%

#!/system/bin/sh

insmod /system/lib/modules/overclock.ko omap2_clk_init_cpufreq_table_addr=0xc00505b4

echo 60 > /proc/overclock/max_vsel

echo 800000 > /proc/overclock/max_rate

echo "1 600000" > /proc/overclock/freq_table

echo "2 400000" > /proc/overclock/freq_table

echo "3 300000" > /proc/overclock/freq_table

echo "4 200000" > /proc/overclock/freq_table

echo "1 200000000 23" > /proc/overclock/mpu_opps

echo "2 300000000 28" > /proc/overclock/mpu_opps

echo "3 400000000 35" > /proc/overclock/mpu_opps

echo "4 600000000 48" > /proc/overclock/mpu_opps
[Flipout and Charm General] xinbada007:
800MHz is too low, after all the default max_rate is 720MHz. I think it should be able to reach 1GHz.
[Flipout and Charm General] phchshow:
It's ok, but battery will be hot, I don't like this, so I use 800MHz.

And max_vsel I use 60, because I tested 55 and 58 sometimes unstable,but 60 is stable.
[Flipout and Charm General] xinbada007:
66vsel/1Ghz is very stable in my phone, but only with 2.1 Rom. With CM7, this phone can only reach 800+(1Ghz freezes phone), a bit weird. How do you think, anything wrong with CM7 Rom?
[Flipout and Charm General] phchshow:
I don't know, I remember previous test 1Ghz is no problem, so I forget check again.

Seems 1Ghz has problem, but I test 66vsel/900Mhz is no problem.