[ROM][Updated 20/01/11] Higgsy Modded 2.2 ROM - Minimal Moto/Chinese

[naenee]

Before I try this later today, and I realize this may be a bit of an off-topic question: is Swype still part of this package and if not, can I just install the apk after having made a backup from a previous rom?

 

[Higgsy]

Before I try this later today, and I realize this may be a bit of an off-topic question: is Swype still part of this package and if not, can I just install the apk after having made a backup from a previous rom?

Have a look at the posts form around 4 hours ago mate was discussed there.

 

[naenee]

OK I didn't know, I have installed from swypeinc.com and It is working!

Ah, I see

 

[Foxhound.kl]

Thanks for the rom Higgsy, much appreciated. Just liked to let you know that everything is working well so far, flashed from UK 2.21.

Had to manually input the apn for my network (3 Mobile UK) to get 3g working. I also wiped the data from Gallery to get it working proper (used titanium backup). Also I used a titanium backup of setvsel and its working, no force close on my end.

For the latest swype beta, follows the steps in my post in the following thread;

http://forum.xda-developers.com/showthread.php?t=903213



Sent from my ME525 using XDA App

 

[morphin]

Yes
I have seen this too. I tried different settings like:

echo "54" > /proc/overclock/max_vsel
echo "1050000" > /proc/overclock/max_rate
echo "1 300000000 14" > /proc/overclock/mpu_opps
echo "2 550000000 26" > /proc/overclock/mpu_opps
echo "3 800000000 38" > /proc/overclock/mpu_opps
echo "4 1050000000 54" > /proc/overclock/mpu_opps
echo "0 1050000" > /proc/overclock/freq_table
echo "1 800000" > /proc/overclock/freq_table
echo "2 550000" > /proc/overclock/freq_table
echo "3 300000" > /proc/overclock/freq_table" > /system/xbin/setscaling.sh

->also with and without quotes. Starting the freq_table with 0 or 1, but no go. Defy restarts. I suppose the problem is with the freq_table

Can somebody try also please?

Andy

 

[MadStu]

Had you ever been on 2.51 Eclair rom in the past

No, I never went to 2.51 because of your warnings on the Modaco posts.

 

[Higgsy]

Yes
I have seen this too. I tried different settings like:

echo "54" > /proc/overclock/max_vsel
echo "1050000" > /proc/overclock/max_rate
echo "1 300000000 14" > /proc/overclock/mpu_opps
echo "2 550000000 26" > /proc/overclock/mpu_opps
echo "3 800000000 38" > /proc/overclock/mpu_opps
echo "4 1050000000 54" > /proc/overclock/mpu_opps
echo "0 1050000" > /proc/overclock/freq_table
echo "1 800000" > /proc/overclock/freq_table
echo "2 550000" > /proc/overclock/freq_table
echo "3 300000" > /proc/overclock/freq_table" > /system/xbin/setscaling.sh

->also with and without quotes. Starting the freq_table with 0 or 1, but no go. Defy restarts. I suppose the problem is with the freq_table

Can somebody try also please?

Andy

My defy would not handle a vsel of 14 @300mhz - that looks way to low mate. also you don't need quotes,

This is the way it should look. I would also recommend usig text editor in root explorer and also check for rogue characters that appear sometimes at the end of the lines I found I got this if editing in word pad on the PC. Also make sure the permissions are set correctly.

echo 54 > /proc/overclock/max_vsel
echo 1050000 > /proc/overclock/max_rate
echo 1 300000000 14 > /proc/overclock/mpu_opps
echo 2 550000000 26 > /proc/overclock/mpu_opps
echo 3 800000000 38 > /proc/overclock/mpu_opps
echo 4 1050000000 54 > /proc/overclock/mpu_opps
echo 0 1050000 > /proc/overclock/freq_table
echo 1 800000 > /proc/overclock/freq_table
echo 2 550000 > /proc/overclock/freq_table
echo 3 300000 > /proc/overclock/freq_table

 

[morphin]

Hi

No change:
# setscaling.sh
setscaling.sh
# mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
# cat /system/xbin/setscaling.sh
cat /system/xbin/setscaling.sh
#!/system/bin/sh
echo 60 > /proc/overclock/max_vsel
echo 1000000 > /proc/overclock/max_rate
echo 1 300000000 30 > /proc/overclock/mpu_opps
echo 2 550000000 40 > /proc/overclock/mpu_opps
echo 3 800000000 50 > /proc/overclock/mpu_opps
echo 4 1000000000 60 > /proc/overclock/mpu_opps
echo 0 1000000 > /proc/overclock/freq_table
echo 1 800000 > /proc/overclock/freq_table
echo 2 550000 > /proc/overclock/freq_table
echo 3 300000 > /proc/overclock/freq_table
# cat /proc/overclock/mpu_opps
cat /proc/overclock/mpu_opps
mpu_opps[3] rate=800000000 opp_id=3 vsel=50 sr_adjust_vsel=50
mpu_opps[2] rate=550000000 opp_id=2 vsel=40 sr_adjust_vsel=40
mpu_opps[1] rate=300000000 opp_id=1 vsel=30 sr_adjust_vsel=30
# cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq
cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq
300000
# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies

C:\Windows\Programs\Android\android-sdk-windows\platform-tools>
->defy is rebooting

So either is it because of this ROM or because of the bootloader?
Andy
-> the last line "cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
" is responsible for rebboting. immediately after this command defy is rebooting

 

[Higgsy]

No, I never went to 2.51 because of your warnings on the Modaco posts.

Did you happen to try the camera when you loaded up the 2.34 rom, to make sure the flash worked ok?

 

[siukeee]

I found when I tap on the data manager to show the app data usage it does nothing, it is accumulating though... you can see the total amount used.

any work around with this? is it also happening to anyone?

 

[MadStu]

Did you happen to try the camera when you loaded up the 2.34 rom, to make sure the flash worked ok?

Yes it works on 2.34. I've just now installed the 2.34 sbf again as I use the camera a lot when I'm trail riding. I think I'll wait for the official Motorola Android 2.2 release for the UK or Europe, due soon I hope!

Thanks

 

[Higgsy]

Hi

No change:
# setscaling.sh
setscaling.sh
# mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
# cat /system/xbin/setscaling.sh
cat /system/xbin/setscaling.sh
#!/system/bin/sh
echo 60 > /proc/overclock/max_vsel
echo 1000000 > /proc/overclock/max_rate
echo 1 300000000 30 > /proc/overclock/mpu_opps
echo 2 550000000 40 > /proc/overclock/mpu_opps
echo 3 800000000 50 > /proc/overclock/mpu_opps
echo 4 1000000000 60 > /proc/overclock/mpu_opps
echo 0 1000000 > /proc/overclock/freq_table
echo 1 800000 > /proc/overclock/freq_table
echo 2 550000 > /proc/overclock/freq_table
echo 3 300000 > /proc/overclock/freq_table
# cat /proc/overclock/mpu_opps
cat /proc/overclock/mpu_opps
mpu_opps[3] rate=800000000 opp_id=3 vsel=50 sr_adjust_vsel=50
mpu_opps[2] rate=550000000 opp_id=2 vsel=40 sr_adjust_vsel=40
mpu_opps[1] rate=300000000 opp_id=1 vsel=30 sr_adjust_vsel=30
# cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq
cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq
300000
# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies

C:\Windows\Programs\Android\android-sdk-windows\platform-tools>
->defy is rebooting

So either is it because of this ROM or because of the bootloader?
Andy
-> the last line "cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
" is responsible for rebboting. immediately after this command defy is rebooting

Possibly the extra frequency step. As I said I haven't tested myself with 4 freq steps on this ROM. I'll have a look later when I've finished work.

 

[Higgsy]

I found when I tap on the data manager to show the app data usage it does nothing, it is accumulating though... you can see the total amount used.

any work around with this? is it also happening to anyone?

Try using ti backup to wipe the data only for the datamanager app. I think I may have forgotten to wipe this before I put this out

 

[Higgsy]

Yes it works on 2.34. I've just now installed the 2.34 sbf again as I use the camera a lot when I'm trail riding. I think I'll wait for the official Motorola Android 2.2 release for the UK or Europe, due soon I hope!

Thanks

Got give up hope mate Q2 could mean anywhere up to July!, I have a theory that I am going to test out later. Watch this space.

 

[Foxhound.kl]

My last post mentioned that I fixed the gallery app with a Titanium Backup data wipe, but its still messed up.

When you select a folder with pictures in it, it doesn't show whats supposed to be in the folder you have selected, it will open another in the list.

Any ideas on how this can be fixed?

##Edit##

Ok found it works ok when in vertical mode, but if the phone is held horizontal, the glitch I described comes back.

 

[Muznyu]

What works for me: Yesterday I spent a lot of time to fix the problem. The solution which I found is:

1. boot in clock work recovery mode
2. wipe data
3. wipe cache
4. restore backup
5. reboot
6. DON'T start camera !!!
7. start titanium backup
8. clear dalvik cache with titanium backup
9. wipe camera app with titanium backup
10. now flash light works for me

I am not sure that it works every time, but works for me

I tried this method and it looks like my flash is finally working (after reboot as well). When taking a picture the flashlight's color is a kind of green, but it's still better than nothing.

Edit:

Camera 360 killed the flash, wipe didn't help... Tried to restart the phone, but no luck, it's working only one time.

 

[naenee]

Okay, time to give this another shot. I can not say I like the idea of having to manually enter my APN, but I suppose it's a minor inconvenience compared to what else could be wrong and isn't.

 

[Higgsy]

My last post mentioned that I fixed the gallery app with a Titanium Backup data wipe, but its still messed up.

When you select a folder with pictures in it, it doesn't show whats supposed to be in the folder you have selected, it will open another in the list.

Any ideas on how this can be fixed?

##Edit##

Ok found it works ok when in vertical mode, but if the phone is held horizontal, the glitch I described comes back.

Not got the issue myself works ok

heres the apk if you want to replace, in case thats the issue

 

[martt]

Can I put that ROM in my Defy with JORLA_U3_6.14.5???

Or just to 2.21 or 2.34?

And i can install PT-BR language on this ROM?

Thanks

 

[Higgsy]

Can I put that ROM in my Defy with JORLA_U3_6.14.5???

Or just to 2.21 or 2.34?

And i can install PT-BR language on this ROM?

Thanks

1) yes but follow the process,

2)Yes if you know how to do it - its not that easy though! Only English on this ROM