Greets all,
I just wanted to inform everyone that is using NAND builds Especially DFT's I have solved the G-Sensor Problem. After searching, and sorry for saying no one even giving me an idea even where to look, I finally after days of digging found it!
I can't Promise this will work for everyone, but This does work for me, and it should work for everyone else. Download the attached file, unzip it and then copy your existing bma150_user file from system/bin and make a backup (DO NOT DELETE THIS FILE from its location), then with root access copy the file I attached to the same location over-writing the existing one, then REBOOT, you can now calibrate your G-Sensor without it being facedown.
This MIGHT fix the G-Sensor freeze issues that some have also, again MIGHT
Worse case if this doesnt fix your G-Sensor problem, then copy back your backup and you wont have to hate me, but I think this should work for just about everyone!
(Filesource Credit: Ripped from Motomans234 Carbom EVO Remix SDCard Android)
*** Updated: 1/15/11 ***
Apparently It seems somethings have changed in certain Builds that have stopped the replacing of this file from working. I went on the hunt, and found another work around, but this file is still needed. Follow Below:
Before installing the file above, go to System/Bin and delete the bma150_usr, then navigate to Data/Misc, and delete the following files:
AK8973Prms.txt
AK8973.Prms.txt.tmp (If there)
bma150_usr.txt (If there)
After navigate to the above file and add it to System/BIN and then your calibrating will function correctly and adjust the values properly.
*** UPDATE 1/19/11 ***
This is for anyone that DOESNT have the G-Sensor under Display, but anyone can use it:
Go to market, and download a program called Bubble. Its a program to use your phone as a level. Install it and run it, you have to calibrate it 4 times. First vertical (Side without the volume rocker against something straight), Second horizontal (First volume rocker facing down, bottom against something straight), Third horizontal (Volume rocker facing up, top of phone against something straight). And lastly calibrate the phone laying flat on its back. After that your phone should be calibrated for use.
This workaround will NOT fix the auto-rotation problem.
Any issues, post, if it works for you post a comment so others know.
Hey! nice one!!!
Good job
hi thank you for you solving.
but my hd2 gsensor calibration was freezed yet.
mda
well, it's not working for me
backup restored, sry man
I have no issues with my G-Sensor, though I do appreciate the continuous development by others
Well done!
NICE - Great work
a big tnx to you for sorting this out
//SB
Again just so everyone knows the only phone I can test this out on is the HD2 TMOUS made after June 2010. I seriously think this might have to do with some sort of hardware revision. But I cant be sure.
But I'm trying, as we all know all setups and phones arent the same, just like desktops, but anyone I can help Im happy.
Just a quick bump for the people that are still having issues with the G-Sensor.
AngelDeath said:
Just a quick bump for the people that are still having issues with the G-Sensor.
Click to expand...
Click to collapse
Hi, thank you for working this out. I wanna ask a question, is this solution compatiable with all the NAND ROM?
dont work for tested on mult nand rom
lextad666 said:
dont work for tested on mult nand rom
Click to expand...
Click to collapse
It doesn't work on the rom I'm using now, either. Gonna try DFT ROM later, maybe it only works on it.
Again, I dont know which phones it will work with, I do know with a USA HD2 TMOUS made after june 2010 which is what I have it works. The file in question is the bma150_usr file. The file I posted is from Motoman's Carbon EVO remix sdcard android, and it works with the DFT NAND Rom.
For anyone willing to read, or wishes to know how I found this, here is my reference point in finding the driver which controls G-Sensor:
http://www.slideshare.net/appleboy/introduction-to-gsensor-i2c-driver
Reference pages: 10 thru 24.
AngelDeath said:
Again, I dont know which phones it will work with, I do know with a USA HD2 TMOUS made after june 2010 which is what I have it works. The file in question is the bma150_usr file. The file I posted is from Motoman's Carbon EVO remix sdcard android, and it works with the DFT NAND Rom.
For anyone willing to read, or wishes to know how I found this, here is my reference point in finding the driver which controls G-Sensor:
http://www.slideshare.net/appleboy/introduction-to-gsensor-i2c-driver
Reference pages: 10 thru 24.
Click to expand...
Click to collapse
Hey, thanks, man. You have given enough information so far. Good work!
Please show me how to copy your file to system/bin, I tried but I has received a message : "This folder read only", although my hd2 rooted by z4root ?
DungEps said:
Please show me how to copy your file to system/bin, I tried but I has received a message : "This folder read only", although my hd2 rooted by z4root ?
Click to expand...
Click to collapse
When in system/bin, depending on the explorer you are using you have to change to Mount R/W, by default you are viewing the folder as Mount R/O.
R/W = Read/Write
R/O = Read/Only
AngelDeath said:
When in system/bin, depending on the explorer you are using you have to change to Mount R/W, by default you are viewing the folder as Mount R/O.
R/W = Read/Write
R/O = Read/Only
Click to expand...
Click to collapse
Thanks! I did it, but i don't know why it doesn't work on my phone, although it's running on DFT NAND Rom
Hey, thanks
G-Sensor fix
Did NOT work for me.but I don't have the T-Mobile version either. Yours is probably the T8585, and I have a T9193 (Australian version which does 3G on AT&T) When I 1st did it, it seemed to work (right side calibrator was not going crazy anymore) but then would not rotate screen at all. A temporary work around is if you reinstall the rom, and do NOT use the calibrator at all, screen rotation works fine. Sort of like the old joke; "Doctor it hurts when I touch this!" Doctors reply; "Then don't touch it!"
AngelDeath said:
Just a quick bump for the people that are still having issues with the G-Sensor.
Click to expand...
Click to collapse
Even though I didn't use this fix per se, (my G-Sensor was just freezing) this still fixed my issue. The last part where he said about calibrating it face down is what caught my eye. I just did that on the edge of a table and bam, its fixed! My G is now working as it should. So stoked!
Sent from my HTC HD2 Running Android 2.2 using XDA App
Main Post Updated with New Info
Related
Starting this thread here for running this Eclair-Hero build on our Kaisers. Many thanks to all devs below!!
jamezelle said:
King Klair Hero 0.6
First and Foremost this build was ported by Mssmison and the ril(radio interface layer), and audio libraries were written by Vilord!!! im pretty sure the gps library was written by Srwalter. vilord may have helped port it to eclair. (will get back to you on that). without DZO we would still be using windows mobile "" but were not ""
To Donate: to these fine gents visit http://sourceforge.net/apps/trac/androidhtc/wiki/WikiStart and scroll down to the donation links
B to the E to the T to the A
this is very beta, well almost alpha(first release for us vogue users so report any bugs that havent been mentioned in this post)
what works:
gps
calls
data
wifi
sync(dont sign in to google during htc wizard, wait till next boot!! you have been warned!!!)
market
gmail
what doesn't:
camera
bluetooth
gtalk
get more widgets
will add screenies later
ENJOY
Click to expand...
Click to collapse
UPDATE 17 Dec:
Download the new rootfs below for working WiFi! Thanks enatefox!
Download:
system.sqsh [ver 0.6.01]
Eclair-ready__rootfs.img (rename to rootfs.img, of course)
eclairhero.user.conf (goes on your SD card in /android/conf)
OR if you have a swap partition on your SD card: eclairhero-swap_partition.user.conf (goes on your SD card as /android/conf/eclairhero.user.conf)
And if you don't have them already:
zImage-15-12-09 (the latest kernel from 15 Dec)
startup.txt (My personal HaRET startup.txt)
rootfs changelog:
Copied /init.cfg/init.eclairhero.rc to /init.cfg/init.eclairhero.kaiser.rc
Copied /init.cfg/init.eclair.rc to /init.cfg/init.eclair.kaiser.rc
Altered init to check that media folder exists in /sdcard/android/media instead of /sdcard/media
Altered init to support eclair.user.conf and eclairhero.user.conf
TIPS:
You will need a fresh data partition/data.img for this build. Don't forget to back up your old one first!
Go straight to version 0.6.01 as posted above, version 0.6 gives me weird SIM errors.
This build takes FOREVER (5-10min) to boot. It goes through and even attempts to make a number of thumbnails for your images during first boot. I suggest watching it over adb so you'll know when it's settled and ready for input.
The HTC widgets are not working with this build.
TaskKiller is an absolute must, like other Hero builds this one loves to keep apps open.
Hmm, this build has successfully rebooted itself twice, during heavy use. I wish I knew how that worked, so we could get it to reboot on command!
Wifi not working D:
Also if I put 15-02-19, Haret asks for 11-12-09 (where can I find the latest haret?)
Why does it happen?
Almost downloaded Hero, just got vanilla Eclair to boot the first time. I'll look into wifi. Maybe it's me but Eclair seems faster than Donut but I haven't messed with it much. That should make Hero much nicer.. will post back when I get further
rugalck said:
Wifi not working D:
Also if I put 15-02-19, Haret asks for 11-12-09 (where can I find the latest haret?)
Why does it happen?
Click to expand...
Click to collapse
The startup.txt needs to be updated for the new zImage, or you can download my updated one from the first post.
@enatefox:
O
Hero is very buggy, has too many problems to run daily for now. Overall Eclair Mike the fastest yet though! And the fonts are much better for qvga. Text autocomplete has issues.
polyrhythmic said:
The startup.txt needs to be updated for the new zImage, or you can download my updated one from the first post.
Click to expand...
Click to collapse
Nah, don't worry, it was something really really stupid.
In the same file you said, it was like "zImage 11-12-09" so now I saved it saying just "zImage". Now works fine.
Waiting for wifi updates, great work guys!
BTW, is there any way to take screenshots?
damn bootloop. I'll look at this tomorrow but that's a promise . I don't know where these wifi files came from. I dropped in the ones that I've used and we'll see. Right now I'm fixing telnet and some other issues to post back with but it will take a little bit of time. We're going to get this working for daily use.
Here's working wifi for Eclair:
http://www.mediafire.com/?ezyzekjozj3
EDIT, I didn't get Hero to boot for me (looping) but I forgot to update Eclair Hero's conf file to match conf.eclair.kaiser.rc.. can someone either do that and repost or wait for me to finish some perm issues with it and I will upload one for Hero. Sorry about that.
I have got to be doing something wrong. I am using all of the files from the 1st post and the rootfs.img from enatefox's last post and this sat for 30 minutes. I even copied the user file to the sd card, to the /sdcard/CONF folder and into the /sdcard/Android/CONF folder and still it sits. I'll get a post of the last few lines up later to see if I just need to wait more or not. I am also using an empy 2GB Fat32 SD Card with the 1.71 radio. All other builds work but this one???
Any ideas?
I could mirror my files. They're working perfect, even wifi and etc (bluetooth not yet).
Folder Screenshot:
http://i46.tinypic.com/oqbo2c.jpg
Then you delete data.img to start from the beginning.
that could solve your issues
rugalck said:
I could mirror my files. They're working perfect, even wifi and etc (bluetooth not yet).
Folder Screenshot:
http://i46.tinypic.com/oqbo2c.jpg
Then you delete data.img to start from the beginning.
that could solve your issues
Click to expand...
Click to collapse
If u don't mind, that would be great. I also just noticed that even after a 1/2 hr, a data.img file never was created
edit: wait, your system file in that picture is only 44.325 MB; the latest system file from post 1 is 89.3? Why so different?
Also
polyrhythmic said:
TIPS:
You will need a fresh data partition/data.img for this build. Don't forget to back up your old one first!
Click to expand...
Click to collapse
What do you mean, clean data.img, do I need a clean one already on the SDCard for 1st run, so none present?
FYI, your 'conf' and 'android' folders should be named in lowercase, if they aren't already.
The only way we can tell what is wrong is to see whatever the console says before it freezes, or ADB logs if you can make it that far. Post whatever you've got.
j101399j said:
If u don't mind, that would be great. I also just noticed that even after a 1/2 hr, a data.img file never was created
edit: wait, your system file in that picture is only 44.325 MB; the latest system file from post 1 is 89.3? Why so different?
Also
What do you mean, clean data.img, do I need a clean one already on the SDCard for 1st run, so none present?
Click to expand...
Click to collapse
If it wasn't created then... you wouldn't need to delete it, do you?
ROM Size: That's because I use mixed files from the different Eclair thread's.
It's a "package" of what worked fine on my device.
Most of the files are from this thread, but the system.sqsh is from this one:
http://forum.xda-developers.com/showthread.php?t=600154
Mirror File: http://rapidshare.com/files/322793487/android.rar.html (up to 10 times, I don't have a premium account D: )
j101399j said:
What do you mean, clean data.img, do I need a clean one already on the SDCard for 1st run, so none present?
Click to expand...
Click to collapse
You need to have one of two things:
If you are using the partitioned SD method, you need a fresh ext2 partition (newly created with a partition manager, or wiped using the Android install script)
If you are using the data.img file method, just make sure there's no data.img on your SD so the installer can create one during boot.
rugalck said:
ROM Size: That's because I use mixed files from the different Eclair thread's.
http://forum.xda-developers.com/showthread.php?t=600154
Click to expand...
Click to collapse
thank you, will try
polyrhythmic said:
You need to have one of two things:
If you are using the partitioned SD method, you need a fresh ext2 partition (newly created with a partition manager, or wiped using the Android install script)
If you are using the data.img file method, just make sure there's no data.img on your SD so the installer can create one during boot.
Click to expand...
Click to collapse
I competly forgot about needing all lowercase letters; as for the data.img file, that is what I though; Thank you
[EDIT]
That is so wierd; I had to place the system.img into the /sdcard/android folder and the use user file in these 3 places /sdcard /sdcard/android and /sdcard/android/conf
Now it works. Don't know what changed, but it works
j101399j said:
thank you, will try
Click to expand...
Click to collapse
http://rapidshare.com/files/322793487/android.rar.html
I can almost guarantee you that the .conf file in your SD root and the .conf file in /android/ are ignored, try deleting them and just leave the .conf in the /conf/ directory. And yes, everything including the system.img/system.sqsh should go in the /android/ folder now.
I bet you can boot this Hero build, but it has a lot of bugs, you'll probably be happier with plain Eclair that rugalck linked.
hey guys ill update when king drops 0.7
keep getting stuck at this part:
ANDROID [ 30.906001] init: Unable
to open persistant property directory /data/property
error 2
How to fix this
thanks
RDilus said:
keep getting stuck at this part:
ANDROID [ 30.906001] init: Unable
to open persistant property directory /data/property
error 2
How to fix this
thanks
Click to expand...
Click to collapse
If it's the first boot, make sure to have at least 300mb free in your SD card.
rugalck said:
If it's the first boot, make sure to have at least 300mb free in your SD card.
Click to expand...
Click to collapse
not to be rude but im not stupid -.-'
i have like 5GB free...
This is a complete package just unzip folder on sd card.
Here is original thread by neopeek
people having wifi problems check the original thread they have a fix
This is the CWM 1.9 thread wich is included in folder already
Using starfox test kernel from XDA (Rhodium only)
EDIT: per starfox dont use test kernels use his new vanilla stable kernel
GAPPS already included.
Im not a dev, just put stuff together credit goes to all authors just posting here to spread the word
DOWNLOAD
Sure, I'll bite. I've got an extra micro-sd card here. What's the worst that could happen?
It's a pretty fast build, I tried it on Neopeeks site.
It is MDPI, so the look of it isn't quite as crisp... (you can see what I mean by the notification bar 3g, etc...lower resolution basically) but I was impressed by the speed. All the animations, etc are disabled by default and I believe that's Zeam that is the default launcher... it is quite snappy out of the box.
what tweaks you did?
no tweaks just put it together
This version is the fastest thing I've tried (probably due to mdpi-gapps), but I have two major issues.
1) Wifi will sometimes refuse to turn on, saying wifi error on the check box. It must be related to tethering and hotspot settings, because after I mess with these I get an instant reboot.
2) Camera is tremendously unstable. Most of the times it crashes bringing down the entire OS or if I am lucky it will crash the camera app and refuse to start again until a reboot.
Of course there are random hiccups here and there (like most builds), but it is quite close replacing WM for every day usage.
XavierGr said:
1) Wifi will sometimes refuse to turn on, saying wifi error on the check box. It must be related to tethering and hotspot settings, because after I mess with these I get an instant reboot.
Click to expand...
Click to collapse
This is actually not that unusual... I would get this on my epic4g... which is an android phone .
If you don't mind, please use the vanilla kernel that I posted instead of the testing kernel. While I don't mind that it is being bundled, the [Test] kernel was never meant to be used for long term, and is liable to include stuff that is unstable and/or changed on my whim. The vanilla kernel contains some of the tweaks that I consider to be stable and is based on known autobuild releases+supports all devices. Thanks.
http://forum.xda-developers.com/showthread.php?t=1221499
-- Starfox
you think you can make a build with the latest rootfs, starfox's latest kernel, the led patches too?
anish88 said:
you think you can make a build with the latest rootfs, starfox's latest kernel, the led patches too?
Click to expand...
Click to collapse
There's nothing stopping you from doing that.
Including testing stuff into a public build is never a good idea. I wouldn't appreciate anything I distribute for testing to be put into a build. It's meant for testing, so anyone that installs/uses it should know full well what they're getting into. Placing it into a build circumvents that, and everyone ends up using it unknowingly.
To everybody with wi-fi issue:
I've done a small fix
http://www.multiupload.com/7NSGZQZXPC
(wich is in the first post of this thread on neopeek.com)
This will fix if your problem isn't the kernel
wifi scanning problem:
after updating wifi-nvram seems to be ok.
anyway,
fastest rom i have tried.
nekikekec said:
wifi scanning problem:
after updating wifi-nvram seems to be ok.
anyway,
fastest rom i have tried.
Click to expand...
Click to collapse
What problem did you have exactly and what do you mean by updating wifi-nvram?
I also have a wifi problem specifically with this build but can't solve it.
(Wifi works only once per boot)
after turning wifi on phone started scanning for networks. after few seconds app crashed not finding anything. i guess there is a problem with assigning mac address.
anyway, as already described, it is known problem :
here
nekikekec said:
after turning wifi on phone started scanning for networks. after few seconds app crashed not finding anything. i guess there is a problem with assigning mac address.
anyway, as already described, it is known problem :
here
Click to expand...
Click to collapse
That didn't work for me at all.
Can't get CWM working
Hey guys,
I must be doing something wrong, but don't know what.
I just can't get CWM running on my TP2. I followed all the instructions precisely, got into CWM once, even flashed the ROM from SD card, but can't do it again.
I even reflashed my device, Re did the entire SD card but just can't get in to CWM.
Upon booting Haret, I press volume down, but the screen just gets stuck there and doesn't move forward. Please help, I'm trying to flash NeoFroyo 0.1
Regards,
Nilesh
nileshvedi said:
Hey guys,
I must be doing something wrong, but don't know what.
I just can't get CWM running on my TP2. I followed all the instructions precisely, got into CWM once, even flashed the ROM from SD card, but can't do it again.
I even reflashed my device, Re did the entire SD card but just can't get in to CWM.
Upon booting Haret, I press volume down, but the screen just gets stuck there and doesn't move forward. Please help, I'm trying to flash NeoFroyo 0.1
Regards,
Nilesh
Click to expand...
Click to collapse
Did you set all your partitions as primary?
vzihome said:
Did you set all your partitions as primary?
Click to expand...
Click to collapse
Yes I did that too....
SD Card (All Partitions Primary)
Partition 1: 6.4 GB - FAT32
Partition 2: System - 300 MB - EXT2
Partition 1: Data - 300 MB - EXT2
Partition 1: Cache - 300 MB - EXT2
I put the npkboot folder with startup for RHOD100 on the SD Card (Root) and the NeoFroyo Zip also on the root.
Plus, I also put the contents of the npkboot folder on root of the phone. (Not the folder npkboot)
Run Haret from SD Card through File Explorer & press Volume Down - Result: Frozen Screen!!!
Does not enter into CWM recovery...
Are all the steps above right.
Regards,
nileshvedi said:
Plus, I also put the contents of the npkboot folder on root of the phone. (Not the folder npkboot)
Click to expand...
Click to collapse
WHY?
CWM rootfs works only in npkboot.
nileshvedi said:
Plus, I also put the contents of the npkboot folder on root of the phone. (Not the folder npkboot)
Click to expand...
Click to collapse
I'm a little confused with what you did.
Basically just unzip his folder you downloaded and then move the Entire npkboot folder to the root of ur sd card.
So there will be nothing on your sd card except the folder. Inside that folder will be everything just as you unzipped it. So for example haret would be at "Sdcard/npkboot/haret.exe". Then just switch/edit the startup.txt in the npkboot folder for your phone and boot into CWM.
You don't need to move anything outside of his npkboot folder that you unzipped.
DO NOT APPLY THE ZIP I UPLOADED, READ EDIT 2
Edit: I will make a flashable fix in a .zip inspired from CM7 RC1.5, with only the mmcfix in it, therefor anybody can use it, even people on official ROMs or other custom ROMs than CM7.
Work in progress....
Flashable zip nearly ready with mmcfix from CM7...
Zip script works correctly, testing...
Soft brick..
Flashed back my stock Froyo, restoring my nandroid backup (this shows you how important a backup can be! )....
Back to work! ^^ .....
Edit 2: I'll upload my mmcfix_signed_crakeron.zip for show only, it !!!DOES NOT WORK!!! right now and if you apply it through CWM you will !!!SOFTBRICK!!!. It is for people to take a look at it only, especially my update-script, and try and figure out what is wrong, or in my opinion, what i have forgot to put in it, seen as there is no sytax problems.
Hi all,
As you all know, our lovely Defy seems to have a problem when it comes to using sd cards... where *GENERALLY* all class 2 cards are fine, and problems may occur with higher class cards.
The problem is basically: the phone loses its write acces to the card, and therefor for example the photo camera app can take pictures, but can't save them... Another sign of this issue would be an absurd "SD Card damages/corrupted, please format" notification, and the sdcard never mounting again untill you well...re-format the card. This happens to me once a week, making me have to backup my stuff to the pc, format the card, and then put it all back on the card, and voila off we go till the next "false corruption" .
I've done some research, seen as this is a software issue, and not hardware, and i have found out it is an OMAP kernel issue:
"SD card problems since 2.2 update is a bug in OMAP kernel sources for froyo. CyanogenMod developpers worked hard to patch the kernel but it is hard to correct motorola bugs due to the locked bootloader." (source: Motorola support forums")
here is what i also found:
http://maemo.org/community/maemo-users/n900_microsd_card_i-o_errors_and_corruption/
To resume the thread, a Nokia n900 user, which also has a TI OMAP proc., discovered what was faulty:
some function in the driver (to keep this simple i will not name it, people interested and devs please just click on the link), dynamically calculates a DTO value based on the SD card's caracteristics. THIS IS WHAT IS NOT WORKING CORRECTLY
the guy simply modified a function in the omap_hsmmc driver so as it would use a constant universal DTO value, that would work with all sdcards, turning the DTO from dynamic, to static
Right, now you're thinking "what has this got to do with our Defy?"
Well...it has been sead in motorola milestone forum in xda, that:
"Since N900 uses the same SOC as Milestone and probably much of the drivers code are the same, perhaps the fix for N900 could be implemented as well? Not sure whether TI OMAP drivers are builtin in the kernel or not... If possible, could you please check this?"
(source: http://forum.xda-developers.com/showpost.php?p=17033833&postcount=5563)
and it is also said somewhere that this fix should also apply to the Motorola Defy.
I think I could be capable of making this fix for us, i just need some help:
(1) Where is the omap mmc driver situated in our /system ?
After having found it, i can copy it on to my sd card, and open it up and have a look (it is expected to be a C language file, i'm familiar enough with C to be able to edit the driver )
(2) I would like that driver from an official 2.1 ROM, and one from a 2.2 one, just to compare them
What do you think guys? If one of you know where to find the driver could you PM me to help me get started?
P.S This is not a thread about who's sdcard works and who's doesn't, so don't post millions of "my kingston 8gb class X works fine"
P.P.S Hit the THANKS! button if you want to support me, it costs nothing and makes my day!
the fix is already included in cyanogenmod since RC 1.5
reserved for futur use
vick33 said:
the fix is already included in cyanogenmod since RC 1.5
Click to expand...
Click to collapse
I know, but some of us out here don't want to go CyanogenMod, i'll contact Quarx and see if he could cooperate with me so that every one and every ROM could benefit from the fix
crakeron said:
I know, but some of us out here don't want to go CyanogenMod, i'll contact Quarx and see if he could cooperate with me so that every one and every ROM could benefit from the fix
Click to expand...
Click to collapse
The sources are public you can use them if you want. Now cyanogenmod is extremely good and stable. Because of the same kernel i think you can use the modul from cyanogenmod. Try if it works or not.
vick33 said:
The sources are public you can use them if you want. Now cyanogenmod is extremely good and stable. Because of the same kernel i think you can use the modul from cyanogenmod. Try if it works or not.
Click to expand...
Click to collapse
Will do. I'm working on it right now and planning to make a flashable .zip for cwm, that way everyone will have the fix
P.S. this is exciting
Made the update zip, the script seems to be OK, but just a bit missing, the device didn't like having something added in /system/lib/modules. I had write acces to it, maybe i have to put acces back to read only before ending script?
You can have a look at it to try and find out, but DO NOT flash the zip or you'll soft brick
Hi Crackeron, any good news for your script ?
Best regards
Cordialement...
alias4defy said:
Hi Crackeron, any good news for your script ?
Best regards
Cordialement...
Click to expand...
Click to collapse
no aka fail
i´m waiting for this fix too!!!
I've built an update-script which writes the module into "/system" partition.
In case of soft-brick, i've built another script which erases the file.
I've flashed it on CM7 ( 15th of october ) and it worked as the fix is already embedded in the ROM.
Let me know whether it works with other ROMs.
P.S. Scripts are written in Edify syntax.
Update: i forgot to include the init.d script that loads the fix once the device is on.
Now i've fixed. It should work!
Could u please drop a few words about install procedure? Thx.
toffifee63 said:
Could u please drop a few words about install procedure? Thx.
Click to expand...
Click to collapse
You've only to flash the zip through clockwork recovery mod.
carlo93 said:
I've built an update-script which writes the module into "/system" partition.
In case of soft-brick, i've built another script which erases the file.
I've flashed it on CM7 ( 15th of october ) and it worked as the fix is already embedded in the ROM.
Let me know whether it works with other ROMs.
P.S. Scripts are written in Edify syntax.
Update: i forgot to include the init.d script that loads the fix once the device is on.
Now i've fixed. It should work!
Click to expand...
Click to collapse
I've been looking on github on the CM7 project, and unfortunately it seems that there is not ONLY mmcfix.ko needed. We must figure out which files are needed in order for the fix to work :/ (i'm thinking of this "hangs.c" file if i remember correctly that appears in the C code in mmcfix.ko... I'll have a talk to quarx.
Sorry for the time it takes, i'm quite busy with my studies right now, but i haven't forgot you guys =).
Solved!!
i figure out:
please, see this post
http://forum.xda-developers.com/showthread.php?t=1596997
espaciosalter20 said:
i figure out:
please, see this post
http://forum.xda-developers.com/showthread.php?t=1596997
Click to expand...
Click to collapse
Oh, it wasn't as hard as i thought then :/..i was going waaay complicated in the init scripts ><. Anyway well done
Motorola Defy, CM7 @ 1Ghz + CM9 multiboot
[Guide] Install double boot CM7 + CM9
[Guide][Root needed] Unsimlock your Defy
espaciosalter20 said:
i figure out:
please, see this post
http://forum.xda-developers.com/showthread.php?t=1596997
Click to expand...
Click to collapse
I can't post/reply at Development group, so I post here. The patch still have problem. After apply this path on MS2Ginger 3.0, any install app action from SD card will cause reboot problem. My phone is defy with red lens, and the sd card is transcend 16G c10 card.
need this fix, don't have a reader...
my SD cards were all recognised on stock froyo (not sure of build, possibly taiwan retail):? but now after new eclair and froyo sbfs the sdcards not recognised...weird huh?
I have a class 10 16GB.
The stock Froyo SEA 15 hangs often.... yesterday the defy said that SD card is damaged... but I did not format it and removed sdcard and put it in Nokia E5 and to my surprise it was working perfect there....
I have not installed your fix or any mcc fix till now.
This FIX is desparately needed.
For those who get the error that SD Card is damaged... please dont format it in your defy.
Use a computer or other mobile to format the sd card.
OK Guys got solution in this thread:
http://forum.xda-developers.com/show...00&postcount=2
Copy mmcfix.ko & symsearch.ko in /system/lib/modules and change the permissions to rw r r for both files.
Modify load_modules.sh as mentioned below and set permission as rwx r-x r-x
So just add the following lines in load_modules.sh files of /system/bin so it looks like this:
#!/system/bin/sh
export PATH=/system/bin:$PATH
# Install GAN virtual interface kernel module
if [ -e /system/lib/modules/kineto_gan.ko ]; then
insmod /system/lib/modules/kineto_gan.ko
insmod /system/lib/modules/symsearch.ko
insmod /system/lib/modules/mmcfix.ko
fi
Enjoy !!
!ALWAYS make a databackup.img on your device BEFORE making any changes!
Hi all!
For the past 3 weeks I have been making small changes to the build prop file inside the Android /system folder.
These changes incorporate not only a increase in speed but also stability.
What I would like to see happen is one of 2 things, or both if possible.
1. Incorporate this build.prop file into the various "System_Froyo" builds available, forcing these changes on initial install, or
2. Vogue/Polaris developers browse the file for contradicting information (things that won't work on a Vogue/Polaris) and make appropriate changes.
Improvements include:
ro.ril.disable.power.collapse (prevents sleep of death),
various dalvik vm improvements,
force hardware acceleration and performance tuning,
various telephony enhancements including ring delay time and data speeds.
After making these changes, the phone rings immediately, the UI is much smoother (GUI uses video processor primarily), and data jumped from 1.3Mb/sec to over 3.2Mb/sec, making web pages load faster. (EDIT: The 3.2Mb/sec is the top of the scale, I actually averaged 2.2Mb/sec with average pings between 300-500 across 3 different radio roms).
VOGUE/POLARIS OWNERS!
Please test this file and report findings here.
IF you find you need to remove any lines, please do so before copying the file into /system. This file works well on the AT&T networks (Cingular), but may not have much effect on other networks.
If you have trouble after installing this file, please post your bootlog file.
PoX
So may I know what rom support this?
This has only been tested on a "clean" Froyo build, so I cannot make any assumptions as to if it will work in Gingerbread/Eclair/Donut/etc.
If everyone follows the install guide on the front page, I would assume that it would work worldwide, as long as it's Froyo.
In the future I could try it out on Gingerbread and other builds, but I make no promises as development has all but ended for Android on MSM72**.
I can test this. Perhaps, kaiser on Android could be good for daily use?...
Thanks for sharing
PoXFreak said:
Hi all!
For the past 2 weeks I have been making small changes to the build prop file inside the Android /system folder.
These changes incorporate not only a increase in speed but also stability.
What I would like to see happen is one of 2 things, or both if possible.
1. Incorporate this build.prop file into the various "System_Froyo" builds available, forcing these changes on initial install, or
2. Vogue/Polaris developers browse the file for contradicting information (things that won't work on a Vogue/Polaris) and make appropriate changes.
Improvements include:
ro.ril.disable.power.collapse (prevents sleep of death),
various dalvik vm improvements,
force hardware acceleration and performance tuning,
various telephony enhancements including ring delay time and data speeds.
After making these changes, the phone rings immediately, the UI is much smoother (GUI uses video processor primarily), and data jumped from 1.3Mb/sec to over 3.2Mb/sec, making web pages load faster.
If there is interest in this, please respond to this post. If there is enough interest I will attach it to this post as a .tar file.
Click to expand...
Click to collapse
PoXFreak said:
This has only been tested on a "clean" Froyo build, so I cannot make any assumptions as to if it will work in Gingerbread/Eclair/Donut/etc.
If everyone follows the install guide on the front page, I would assume that it would work worldwide, as long as it's Froyo.
In the future I could try it out on Gingerbread and other builds, but I make no promises as development has all but ended for Android on MSM72k.
Click to expand...
Click to collapse
I'm interested in your new build.prop tar, but I do not understand the thing about the install guide, you mentioned in you second post.
My Kaiser is running CM7 RC3 on haret, so maybe I can do some testing on gingerbread, with you.
Your trials, about tweaking the app download possibility, sound very interesting too, as I read about a tweaked build.prop for a tab that simulates to be a samsung tab in combination with an older version of the app market.
Feel free to PM, although I'm quite a newby to android.
I can build with Fresh Froyo and try it, but not until April sorry.
I am currently traveling and away from a development system.
I have been slowly trying to get a reliable app2sd capability working.
I'd suggest searching old posts for power collapse to see if dzo or others long ago tried this.
It sounds promising.
muckelmaus said:
I'm interested in your new build.prop tar, but I do not understand the thing about the install guide, you mentioned in you second post.
My Kaiser is running CM7 RC3 on haret, so maybe I can do some testing on gingerbread, with you.
Your trials, about tweaking the app download possibility, sound very interesting too, as I read about a tweaked build.prop for a tab that simulates to be a samsung tab in combination with an older version of the app market.
Feel free to PM, although I'm quite a newby to android.
Click to expand...
Click to collapse
The "install guide" I'm referring to is here...
How to replace Windows Mobile with Android (Guide)
There would be a change to the original build.prop file which exists inside the /system folder and would be installed when Android is installed on the Kaiser.
Mind you, I live in a busy city with LOTS of cell towers and, since 3g works on the principle of multi-tower usage, YMMV. If you live way out in the country with maybe 2-3 towers nearby, this may not help you.
Also, this has been tested on a NAND-installed OS, not a HaRet install. I cannot verify or guarantee this will work with a HaReT install as I have no way to test it and I think of HaReT as the "slow cousin" to a NAND install.
On a side note: My Kaiser has not had one sleep of death, hard-lock, white screen or even an FC for 9 days now. Apps running out of memory can be a slight problem but they will just close on their own as opposed to FC-ing. at worst I've had one hot reboot called by the system, and the FCs' are few, even with heavy Facebook and Maps use.
n2, if this works on all Kaisers, is there a way to push it to SF and either add it as a mod or rebuild the "system_froyo" install files and incorporate it within?
I will try in early April. Until then please solicit Vogue and Polaris users to try it.
Sent from my Nexus One using XDA
I am interested and willing to try this out!
Where is your " "Fixed" build.prop file for Kaiser "?
Tarball added to OP, please test and report back. Any problems should be reported here along with the bootlog from your phone.
Hi guys!
Problem occured when moving file to root folder. To solve I tried root explorer and z4root both. CM7 + Krazy-Killa's Kernel on tilt 8925.
Please talk what to do with it!
thanks!
Rename original build.prop file to "build.prop.old" or something you will remember, without the quotes, then paste the new build.prop file into the /system folder... it should go right in with no errors, unless you try it without read/write abilities.
CM7 may already have some of these fixes installed in the existing build.prop file. To check, open this build.prop with a text editor and check the entries under "additional build properties".
n2rjt said:
I will try in early April. Until then please solicit Vogue and Polaris users to try it.
Sent from my Nexus One using XDA
Click to expand...
Click to collapse
Vogue/Polaris users solicited, although I'm not sure if this can be used on a CDMA network. Last count shows about 15-20% of the "other" phones were Vogues, the rest were Polaris users.
It would be nice to start getting good feedback since this would be my first actual "hard" mod (one that is installed with the system, not modded through some other installer/program).
PoXFreak said:
Rename original build.prop file to "build.prop.old" or something you will remember, without the quotes, then paste the new build.prop file into the /system folder... it should go right in with no errors, unless you try it without read/write abilities.
CM7 may already have some of these fixes installed in the existing build.prop file. To check, open this build.prop with a text editor and check the entries under "additional build properties".
Click to expand...
Click to collapse
Can't rename. And can't change file attributions read only to read/write.
ZLodei said:
Can't rename. And can't change file attributions read only to read/write.
Click to expand...
Click to collapse
You probably need to remount /system read/write. I just wish I could remember how. Been a long time since I put my vogue down.
If you can get terminal emulator up on that phone, I believe all you would have to do is type in "su" then "mount /system".
All Kaiser/Polaris/Vogue Android builds are rooted and usually have superuser installed. I will take a look into Scoot's CM7 and confirm this. I know there is an update to superuser that leaves the old binary unable to be updated.
PoXFreak said:
If you can get terminal emulator up on that phone, I believe all you would have to do is type in "su" then "mount /system".
All Kaiser/Polaris/Vogue Android builds are rooted and usually have superuser installed. I will take a look into Scoot's CM7 and confirm this. I know there is an update to superuser that leaves the old binary unable to be updated.
Click to expand...
Click to collapse
Hi! Thank you!
What does exactly I have to do in terminal emulator?
I would hope you have superuser capability, if you don't then use another build that does have them...
Anyway, this is all I could figure out to remount the /system as RW. Type the following below into terminal emulator...
mount -o rw,remount -t yaffs2 /dev/block/mtdblock2 /system
(Where "mtdblock2" has /system, "mtdblock3" has /data, and "mtdblock4" has /cache.)
Hope this helps...
Please correct me if i'm wrong.
I installed this new build.prop from the bootloader using androidupdate.tar.
Because i made a tar archive this way: system/build.prop
Isn't it the easiest method? No mounting and hacking in terminal emulator.
Anyway, do anybody know which ROM contains hungarian language? I gave my Kaiser to my father and it would be great if he could use it in hungarian.
I thought VaniljEclair 11 has it, and it is almost true. It has hungarian language but when i set it nothing happens. Everything is in english as before.
Thanks!
Edit:
You can download it from here:
http://mattempus.sohasenem.hu/pub/androidupdate.tar
Hi
I'm not a total iGO noob and been using it for a few years on HTC HD2 but now have a really annoying problem.
Just got a HTC One M8 (European) and rooted immediately plus gave SD card write access.
First thing I did was install iGO the usual way and add all the content.
When I'm in default 3D mode, the screen starts 'blinking' after a while. The route and the roads start to disappear and the terrain starts taking over the screen, so that for example it will be all green, the same as the fields. The whole screen starts flashing. This is happening on default scheme/skin or any other HD compatible skin. Meanwhile, the voice and the directions are still all ok.
A couple of times I've got a error message saying "memory is low, use different route options", but that's only a couple of times. Remember, this is a phone with bags of memory and no other apps.
I have tried with the moveable thin apks that I can move to SD with all the content, and have tried every other version of iGO apk with all the iGO folders on the internal memory.
I believe the data.zip is I have is a 1920x1080 HD file and I have tried starting with and without Branding files.
I have tried lots of different sys.txt combinations.
Obviously I delete the Save folder every time.
Please, anyone...HELP!
SD card write access
SD card write access.
HTC one m8 , iGO primo (2,4) 9.6.29.341779 and SD card write access problem.
I need to setup all settings each time I am running an application.
mssSphaera said:
SD card write access.
HTC one m8 , iGO primo (2,4) 9.6.29.341779 and SD card write access problem.
I need to setup all settings each time I am running an application.
Click to expand...
Click to collapse
The SD write problem is I think resolved for me by rooting and flashing a different kernel - I can't remember the thread I got this from, but will post when I find it.
So iGO works now, but the Lesscro Themechanger isn't working now!
The slow display I had came from a memory setting I changed in the sys.txt, thanks to another member.
marcusroberts said:
The SD write problem is I think resolved for me by rooting and flashing a different kernel - I can't remember the thread I got this from, but will post when I find it.
So iGO works now, but the Lesscro Themechanger isn't working now!
The slow display I had came from a memory setting I changed in the sys.txt, thanks to another member.
Click to expand...
Click to collapse
come on .. there must be a solution and not rooting phone.
mssSphaera said:
come on .. there must be a solution and not rooting phone.
Click to expand...
Click to collapse
Nope, afraid not. Even rooting and using SDFix won't work alone. I tried changing the permissions on the R/W SD data but keeps defaulting on reboot. Flashing a different kernel is the best way as far as I know.
It's the Google / KitKat policy that's messed things up!
To fix the sd card issue you have to root.There is no other alternative.Kitkat implemented this issue.To fix it you have to change permissions in es file explorer to rw for all.Or you can flash kernel which disables read/write protection.The best kernel is elementalx kernel.Go give it a try! :laugh:
igo roads disappear/blink
marcusroberts said:
The SD write problem is I think resolved for me by rooting and flashing a different kernel - I can't remember the thread I got this from, but will post when I find it.
So iGO works now, but the Lesscro Themechanger isn't working now!
The slow display I had came from a memory setting I changed in the sys.txt, thanks to another member.
Click to expand...
Click to collapse
Hi, I'm having the same problem with the blinking and disappearing roads running igo on my m8. Could you let me know the sys.text tweak that resolved this for you please? Cheers
ArchiGent said:
Hi, I'm having the same problem with the blinking and disappearing roads running igo on my m8. Could you let me know the sys.text tweak that resolved this for you please? Cheers
Click to expand...
Click to collapse
[debug]
max_memory=400000000
reserve_memory=15000000
cache=2048
This is what a member suggested and it worked for me!
Let me know if it works for you.
Are you using Themechanger at all? I'm struggling with that.
marcusroberts said:
[debug]
max_memory=400000000
reserve_memory=15000000
cache=2048
This is what a member suggested and it worked for me!
Let me know if it works for you.
Are you using Themechanger at all? I'm struggling with that.
Click to expand...
Click to collapse
I've just been on a quick trip around the block and adding the above into the sys.text does indeed seem to have done the trick! Many thanks.
I've not used Themechanger since switching from Windows to Android a few years ago.
Same problem here with HTC M8 and above settings did not help, not even a bit.
stathis95194 said:
Same problem here with HTC M8 and above settings did not help, not even a bit.
Click to expand...
Click to collapse
Do you mean that iGO is running slowly or just not starting? Have you deleted the SAVE folder and tried. Is your iGO on the SD card or internal?
ArchiGent said:
Hi, I'm having the same problem with the blinking and disappearing roads running igo on my m8. Could you let me know the sys.text tweak that resolved this for you please? Cheers
Click to expand...
Click to collapse
BTW the themechanger is now working great. It was a problem in sys.txt in the interface settings. Was still set for iGO Windows! Press the widget and changed weather/maps great.
marcusroberts said:
Do you mean that iGO is running slowly or just not starting? Have you deleted the SAVE folder and tried. Is your iGO on the SD card or internal?
Click to expand...
Click to collapse
No, i'm talking about iGo is starting fine, but after a while screen starts blinking until it becomes black. Program is still running but screen is black.
I have eleted save folder, re-installed, tried all kinds of versions
iGo is on sd card, but i'm rooted and on a custom kernel with the sdcard read/write permission fixed.
Same configuration on my One X is running fine.
stathis95194 said:
No, i'm talking about iGo is starting fine, but after a while screen starts blinking until it becomes black. Program is still running but screen is black.
I have eleted save folder, re-installed, tried all kinds of versions
iGo is on sd card, but i'm rooted and on a custom kernel with the sdcard read/write permission fixed.
Same configuration on my One X is running fine.
Click to expand...
Click to collapse
If you know of the best way to that I can share my iGO folder here, please let me know. It really should work well and I use it all day and every day. Let me know how to share please.
marcusroberts said:
If you know of the best way to that I can share my iGO folder here, please let me know. It really should work well and I use it all day and every day. Let me know how to share please.
Click to expand...
Click to collapse
Thanks for the offer. I think i fixed it with a workaround.
I moved the iGO folder on internal memory but kept the "big" content folder on sdcard (which is what i needed anyway)
It seems to work fine now. I will test it again tomorrow when i will be driving and report back.
Any probs let me know. It runs sweet on the m8 mate
marcusroberts said:
If you know of the best way to that I can share my iGO folder here, please let me know. It really should work well and I use it all day and every day. Let me know how to share please.
Click to expand...
Click to collapse
Well i think i might take you up on your offer. I can't get rid of the blinking problem.
I have tried everything. But i believe i have identified what creates the problem. If under iGO/content/map i have a lot of maps >3GB then i have the problem.
If i remove some maps then all is fine. It's definitely not my sdcard because i tried moving everything on internal memory and still get the same problem.
Any ideas that might help will be appreciated
stathis95194 said:
Well i think i might take you up on your offer. I can't get rid of the blinking problem.
I have tried everything. But i believe i have identified what creates the problem. If under iGO/content/map i have a lot of maps >3GB then i have the problem.
If i remove some maps then all is fine. It's definitely not my sdcard because i tried moving everything on internal memory and still get the same problem.
Any ideas that might help will be appreciated
Click to expand...
Click to collapse
It seems that although the above sys.txt file change made iGO run smooth as butter with just maps of one country, I added maps for all of Europe and it keeps freezing. Looks like I'll just have to add maps in whatever country I'm in!
stathis95194 said:
Thanks for the offer. I think i fixed it with a workaround.
I moved the iGO folder on internal memory but kept the "big" content folder on sdcard (which is what i needed anyway)
It seems to work fine now. I will test it again tomorrow when i will be driving and report back.
Click to expand...
Click to collapse
Hi,
trying to do the same with 'content' but i have tried many combinations of linked_root_list but cannot get it working from external card.
how did you do it?
i am rooted on standard rom.
R/W patch
gazzacbr said:
Hi,
trying to do the same with 'content' but i have tried many combinations of linked_root_list but cannot get it working from external card.
how did you do it?
i am rooted on standard rom.
Click to expand...
Click to collapse
You should patch first your M8 for 4.4.2 for R/W .
flash this: