Hi Everyone!
I'm posting this here since I don't have posting privileges in the development area.
I have converted my Korean Galaxy Tab 10.1 as explained in the development section in this thread:
http://forum.xda-developers.com/showthread.php?t=1360588&page=5
to a 7510.
Everything worked fine.
Just one tiny problem I am experiencing:
My Wifi reception has greatly decreased after the conversion.
I noticed this imediately after the conversion but hoped it would "go away" once I had rooted the Tab an installed a modded ROM.
Unfortunately this was not the case.
Does anyone of you other "converters" have any experience with this problem or am I the only one?
best regards an looking forward to your answers
Krügge
Happy new year to everyone!
Well, since noone seems to have my problem I looked into the files myself.
The wifi drivers and their configuration files are located in /etc/wifi of the system image.
I flashed the korean shw-m380w original version and did a backup using CWM. I then did the same with the original gt-p7510 version.
When I compared the filesizes I noticed differences and the content of the configuration files were different as well.
So I just replaced the contents of the european wifi folder with the contents of the korean one. I had to use a linux shell, since the file permissions need to be saved.
I copied the newly created system tar file into the CWM backup directory of the european version, adapted the the md5 hash in the same directory for the new system tar file and went into CWM and did a restore.
Worked like charm. I'm back to my old, much better, wifi reception performance.
I don't know if this is the fastest an easiest method but it worked....
best regards
kruegge99
kruegge99 said:
Happy new year to everyone!
Well, since noone seems to have my problem I looked into the files myself.
The wifi drivers and their configuration files are located in /etc/wifi of the system image.
I flashed the korean shw-m380w original version and did a backup using CWM. I then did the same with the original gt-p7510 version.
When I compared the filesizes I noticed differences and the content of the configuration files were different as well.
So I just replaced the contents of the european wifi folder with the contents of the korean one. I had to use a linux shell, since the file permissions need to be saved.
I copied the newly created system tar file into the CWM backup directory of the european version, adapted the the md5 hash in the same directory for the new system tar file and went into CWM and did a restore.
Worked like charm. I'm back to my old, much better, wifi reception performance.
I don't know if this is the fastest an easiest method but it worked....
best regards
kruegge99
Click to expand...
Click to collapse
i have same problem with you. can you please explain to me step by step how to fix the wifi like you did?
Hi Everyone!
I have done some more experimenting.
Since I wanted to install different Android Versions and different Kernels and the fact that the Kernel Drivers are always compiled to work with only one particualer Kernel, I needed to find a way to improve Wifi reception without having the korean drivers.
I acomplished this by just pasting the config file nvram_net.txt from the korean Android into the directory /system/etc/wifi.
I renamed the original file to nvram_net.txt.orig and pasted, Afterwards I adjusted the permissions to be the same as the ones of the original file and rebooted.
This has worked with every Android Version I installed so far.
I have attached a Screenshot of the directory and the nvram_net.txt file of the korean tab.
I hope I can help somone with this.
To me it seems that the korean tab has just a slightly different Wifi Hardware than the P7510.
best regards
Krügge
Related
Hi all,
This morning I tried to update my Camera firmware using the *#34971539# (Camera Firmware Update) code. During this upgrade I got the message 'FactoryTest stopped'. After that message my camera app stopped working, it starts, shows the buttons, but the image is black. Also I am unable to access the camera firmware update screen... I get the same message as before (FactoryTest stopped).
I tried a few custom roms, but this didn't solve the issue. I also restored a backup I created with CMW, but no luck.
Does any of you have an idea how to get my camera to start working again ????
Thanks.
Best regards,
Vinzie
Try to flash a 3-part firmware with PIT and repartition checked!
Remove the camera update and go back to your previous camera
PJF16 said:
Try to flash a 3-part firmware with PIT and repartition checked!
Click to expand...
Click to collapse
Can you tell me which firmware is 3part ??? Up until now I only used/found single file firmwares...
I red an old galaxy S thread on XDA, apparently you can copy the correct file onto the device (you need root access though) and then you should be able to run *#34971539# again, without it crashing. At least that is how it worked on the galaxy S. I've look on the filesystem of the galaxy S3 and I don't have a 'firmware' folder in the /system/ folder, so I guess the camera files are located elsewhere on the galaxy S3/ICS... does anyone have an idea where these files are located ? And is anyone willing on posting their camera firmware files here....?
Vinzie said:
I red an old galaxy S thread on XDA, apparently you can copy the correct file onto the device (you need root access though) and then you should be able to run *#34971539# again, without it crashing. At least that is how it worked on the galaxy S. I've look on the filesystem of the galaxy S3 and I don't have a 'firmware' folder in the /system/ folder, so I guess the camera files are located elsewhere on the galaxy S3/ICS... does anyone have an idea where these files are located ? And is anyone willing on posting their camera firmware files here....?
Click to expand...
Click to collapse
Apparently people using CM9 also had camera issues and where able to fix them by putting the following files back onto their phone:
/data/cfw/SlimISP_GD.bin
/data/cfw/SLIMISP_ZD.bin
Would someone please send me those 2 files, so I can try if this will fix the camera issues ?
Also also saw that there are firmware files in the folder '/system/cameradata/', I would also love to have those...
Vinzie said:
does anyone have an idea where these files are located ? And is anyone willing on posting their camera firmware files here....?
Click to expand...
Click to collapse
The camera firmware is in two locations. The camera itself contains one (the one you can "flash") and one in the kernel. When the camera loads up (first time after a clean boot) it does a comparison of the two firmwares, decides which one is the latest and loads that one into memory. Hence, there's no need to flash the camera FW itself. It will load the latest of the two.
There is a option in kernel somewhere to store the camera firmware externally. I'm fairly sure this is how CM9 does it, hence the firmware in /data/cfw.
It could also be that CM9 dumps the camera firmware to that folder, for whatever reason I do not know.
You can download the latest firmware CM9 uses directly from their source. I can't make heads or tails when browsing their github, it's a horrible mess, but it's there somewhere. Files are called SlimISP_GD.bin.ihex and SlimISP_ZD.bin.ihex.
Daelyn said:
The camera firmware is in two locations. The camera itself contains one (the one you can "flash") and one in the kernel. When the camera loads up (first time after a clean boot) it does a comparison of the two firmwares, decides which one is the latest and loads that one into memory. Hence, there's no need to flash the camera FW itself. It will load the latest of the two.
There is a option in kernel somewhere to store the camera firmware externally. I'm fairly sure this is how CM9 does it, hence the firmware in /data/cfw.
It could also be that CM9 dumps the camera firmware to that folder, for whatever reason I do not know.
You can download the latest firmware CM9 uses directly from their source. I can't make heads or tails when browsing their github, it's a horrible mess, but it's there somewhere. Files are called SlimISP_GD.bin.ihex and SlimISP_ZD.bin.ihex.
Click to expand...
Click to collapse
OK I found the 2 files, they were present in a dump posted on the XDA forum. I put both files in the /data/cfw/ folder, restarted the phone and tried the camera, but no luck. I tried it once with and once without the .ihex extention. I also tried the same by putting the files into the /system/vendor/firmware/ folder.... but no luck there either...
Any thoughs on what location I can try ? Or is restarting the phone not enough...? Should I do a hard reset ?
hello there,
i have a GT-I9100 phone best known as the Galaxy S II International, and i'm very fond of messing around with the custom firmwares and stuff. i like to test every nightly that comes out from CyanogenMod, so i'm almost always installing new firmwares, and i'd like to carry on some small updates that i do to each firmware.
however, there is a problem. an update.zip would be useful for static files such as replacing the bootanimation.zip and adding the init.d scripts i want. however, i also like to edit the build.prop files, that are changed each nightly, to show the correct date and other minimum details.
following that, i'd like to know if there's a way to not replace the build.prop file, but just edit/add some lines into it through some script that could go inside the update.zip.
thank you.
After lots of reading XDA and using the many tweaks and fixes one can find here (thanks!) I ran into a problem I can't seem to solve.
I'm modifying a custom ROM (by www.jiayu.es --> version 20131203-000001) for the Jiayu G4B (basic 1/4 3000mah) for use in the Netherlands. I already applied some fixes (GPS-fix, APN-settings, SMS-fix, add some APKs) and created a flashable zip file for use with CWM (thanks to dsixda kitchen).
One thing I can't seem to implement is the replacement of modem.img (in system/etc/firmware) with an updated version that fixes frequent drops of the connection to the network. This fix is documented on the dutch site tweakers.net.
The original fix is quite simple: you just replace modem.img (using a file explorer) with the updated one, straighten out the file permissions and reboot the phone. The thing is I don't want to have to do this manually everytime I flash a new ROM, and furthermore it's fun to learn how to customize my own ROM.
So I thought I could just replace modem.img in my working folder with the newer one and be done with it. Problem is that after I flash the ROM containing the new modem.img both my sims remain offline and the only way to go online again is by restoring a CWM backup.
I already checked the file permissions and they are correct. Unfortunately google also couldn't help me find the answer. Does any here have an idea how to solve this?
matthijsph said:
After lots of reading XDA and using the many tweaks and fixes one can find here (thanks!) I ran into a problem I can't seem to solve.
I'm modifying a custom ROM (by www.jiayu.es --> version 20131203-000001) for the Jiayu G4B (basic 1/4 3000mah) for use in the Netherlands. I already applied some fixes (GPS-fix, APN-settings, SMS-fix, add some APKs) and created a flashable zip file for use with CWM (thanks to dsixda kitchen).
One thing I can't seem to implement is the replacement of modem.img (in system/etc/firmware) with an updated version that fixes frequent drops of the connection to the network. This fix is documented on the dutch site tweakers.net.
The original fix is quite simple: you just replace modem.img (using a file explorer) with the updated one, straighten out the file permissions and reboot the phone. The thing is I don't want to have to do this manually everytime I flash a new ROM, and furthermore it's fun to learn how to customize my own ROM.
So I thought I could just replace modem.img in my working folder with the newer one and be done with it. Problem is that after I flash the ROM containing the new modem.img both my sims remain offline and the only way to go online again is by restoring a CWM backup.
I already checked the file permissions and they are correct. Unfortunately google also couldn't help me find the answer. Does any here have an idea how to solve this?
Click to expand...
Click to collapse
So did you ever find the solution to this problem??? Did it involve taking the battery out immediately after you flash the ROM with the desired modem.img?
No it was never solved, I gave up after a while.
I don't have the phone anymore, so I can't test your solution.
matthijsph said:
No it was never solved, I gave up after a while.
I don't have the phone anymore, so I can't test your solution.
Click to expand...
Click to collapse
having that kinda problem, thinking to replace system.img 1st with push adb, then use dd if=...of=.. not sure if gonna work
*******************************************************************************************************************************************************************************
Solution found see here
*******************************************************************************************************************************************************************************
Hello all,
So I've been searching for a way to change the boot animation on my S3, all I was able to find were ~year old or older tutorials...
(Currently have version 4.4.2, model i747M)
Now I've got no boot animation at all, (sound is still there), and I'm just looking to get it back. (Or if possible a custom one but I'll settle for anything at this point.)
I used the following tutorial to try and change it:
http://forum.xda-developers.com/showthread.php?t=2063280
I believe, (based off the files used in the tutorial), that the problem may be in/with the following:
/system/bin/bootanimation (exe)
or
/system/bin/samsungani (exe)
or
/system/bin/sh (text file)
Any help would be amazing.
*******************************************************************************************************************************************************************************
These have NOT worked for me, but hopefully anyone else experiencing this problem could benefit from them:
http://forum.xda-developers.com/gal...-to-restore-s3-samsung-bootanimation-t2288545 (credit to @thenookieforlife3)
http://forum.xda-developers.com/showthread.php?p=34815984&highlight=bootanimation#post34815984 (directed to specific post)
http://forum.xda-developers.com/galaxy-s3-att/help/trying-to-create-boot-animation-cm11-t2818466 (short thread with a "walkthrough")
*******************************************************************************************************************************************************************************
Hello there, @JamPro,
To restore your boot animation, check out the tutorial here.
Hey @thenookieforlife3,
I've already tried this, (and just tried it again), and sadly it didn't work.
I believe the problem may be with/in:
/system/bin/bootanimation (exe)
or
/system/bin/samsungani (exe)
or
/system/bin/sh (text file)
They were altered/used with the original tutorial that I tried.
Thank you very much for trying though
Do you have a custom rom or just rooted stock? Samsung uses qmg files for the stock and custom ones are in zip format typically.
es0tericcha0s said:
Do you have a custom rom or just rooted stock? Samsung uses qmg files for the stock and custom ones are in zip format typically.
Click to expand...
Click to collapse
I just have rooted stock. The tutorial I used uses .zip's, but, I think, it might have been a work around instead of using .qmg files.
Either way, I have my original bootsamsung.qmg and bootsamsumgloop.qmg files, but it won't display the stock animation...
I've added some potential fixes in my original post. None of them worked for me, but anyone looking for a potential fix should give them a look.
I can get the OUYA controller connected fine, but the button mappings are terribly wrong. I found a keylayout file, but the tablet doesn't seem to want to use it. I tried it with my S3 running CM 11 and it was able to use it and the mappings are fine. I'm running a rooted 10.6.A.0454 and I've done the following.
1. Copied the keylayout file Vendor_2836_Product_0001.kl to /system/usr/keylayout (verified the Vendor and Product #s are correct)
2. Set the group to root and gave it permissions 644 (like all the other .kl files)
3. Rebooted tablet
I don't know why it doesn't want to work because I've gotten that exact file to work on older builds for the tablet, as well as my S3 running CM11. Any suggestions would be appreciated. Thanks.
cain05 said:
I can get the OUYA controller connected fine, but the button mappings are terribly wrong. I found a keylayout file, but the tablet doesn't seem to want to use it. I tried it with my S3 running CM 11 and it was able to use it and the mappings are fine. I'm running a rooted 10.6.A.0454 and I've done the following.
1. Copied the keylayout file Vendor_2836_Product_0001.kl to /system/usr/keylayout (verified the Vendor and Product #s are correct)
2. Set the group to root and gave it permissions 644 (like all the other .kl files)
3. Rebooted tablet
I don't know why it doesn't want to work because I've gotten that exact file to work on older builds for the tablet, as well as my S3 running CM11. Any suggestions would be appreciated. Thanks.
Click to expand...
Click to collapse
CM11 is android 4.4.4 as far as i remember. Stock 10.6.A.0454 ROM is android 5.0.2.
So the file you are copying is from different android version, which seems to be incompatible.
You can update to CM12(.1) and copy the same file to 10.6.A.0454 firmware or update to stock 5.1.1 ROM (10.7.A.0.222).
Secondly there is SixAxis controller app which will (presumably) help you to change keyboard mapping without messing with Vendor_2836_Product... files.
So this way is less difficult, i think. But the app is paid and you need root-access to use it.