Hey there,
first I have to say - I'm new here - and yes, I have searched for my issue in this forum and elsewhere, but I didn't find a solution. So I decided to register here and ask you experts about helping me to fix my problem:
I'm on Epinters-Rom CM 10.1(Android 4.2) (26/08 Built) and having a problem with a fast GPS-Fix. Always when I use GPS the first time a day it lasts about 5-10Min to get a Sat-Fix. I have done some research about this problem and found this:
In a post on a german forum (I'm from Germany) for Defy Froyo and GPS bug I encountered that there are system files that contain specific configurations for GPS or direct downloading instructions of "ancillary data" (such as A-GPS Data). However, there are no configuration files with the name "location" in Epinters-Rom as they are mentioned in this thread, but I noticed a file in my system folder (system / ect / ) called "gps.config".
Doing more research about this file, I found a post here on XDA in epinters CM10.1 thread from August. Here is mentioned, that Epinters "gps.config" has no entry to an so called "NTP server. He made this entry and now the GPS fix is quick. I didnt really see that Epinter commented this, but a year before, Epinter said (at another Rom) that the NTP server entry is no longer necessary (without further explanation).
Then I remembered (coming from Neutrino-Rom) that Neutrino has had an "GPS-Addon" that was separate flashable - a fix for every single country. So I looked at the the GPS addon of Neutrino (Germany) and behold: When flashing this GPS addon it seems, that just the "gps.config" will be fixed with the following entry for Germany:
Code:
NTP_SERVER de.pool.ntp.org
NTP_SERVER = 0.de.pool.ntp.org
NTP_SERVER = 1.de.pool.ntp.org
NTP_SERVER = 2.de.pool.ntp.org
NTP_SERVER = 3.de.pool.ntp.org
NTP_SERVER = 0.europe.pool.ntp.org
NTP_SERVER = 1.europe.pool.ntp.org
NTP_SERVER = 2.europe.pool.ntp.org
NTP_SERVER = 3.europe.pool.ntp.org
XTRA_SERVER_1 = http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_2 = http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3 = http://xtra3.gpsonextra.net/xtra.bin
# DEBUG LEVELS : 0 - none , 1 - Error , 2 - Warning , 3 - Info
# 4 - Debug , 5 - Verbose
DEBUG_LEVEL = 0
# Intermediate position report , 1 = enable , 0 = disable
INTERMEDIATE_POS = 0
# Accuracy threshold for intermediate positions
# Less accurate positions are ignored , 0 for passing all positions
ACCURACY_THRES = 0
# Report supl ref location as position , 1 = enable , 0 = disable
REPORT_POSITION_USE_SUPL_REFLOC = 1
# Wiper ( wifi positioning ), 1 = enable , 0 = disable
ENABLE_WIPER = 1
# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
# # # # # AGPS server settings # # # # #
# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
# FOR SUPL SUPPORT , set the Following Following
SUPL_HOST = supl.google.com
SUPL_PORT = 7276
SUPL_NO_SECURE_PORT = 3425
SUPL_SECURE_PORT = 7275
SUPL_TLS_HOST = FQDN
SUPL_TLS_CERT = / etc / SuplRootCert
# FOR C2K PDE SUPPORT , set the Following Following
C2K_HOST = c2k.pde.com
C2K_PORT = 1234
CURRENT_CARRIER = common
DEFAULT_AGPS_ENABLE = TRUE
DEFAULT_SSL_ENABLE = FALSE
# TRUE for " User Plane " , FALSE for " Control Plane "
DEFAULT_USER_PLANE = TRUE
In comparison to that, Epinters "gps.config" is only:
Code:
XTRA_SERVER_1 http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_2 = http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3 = http://xtra3.gpsonextra.net/xtra.bin
SUPL_HOST = supl.google.com
SUPL_PORT = 7276
Do you think I could risk simply replace the two files? Or is it better to flash the file of neutrino? Or to edit the file by Epinter right? Or at least nothing at all? I do not even want to fabricate a Brick ...
So you techies from this forum! Can you help me?
Thanks for reading this and sorry for my poor english... its not my native language!
Regards,
Asmaron
PS: The Germany.zip in the appendix contains the files that would be flashed with neutrinos Rom (including the "gps.config"). The other single "gps.config.zip" is that of Epinters Rom. Simply open it in Editor/TextEdit or similar programs and you can see the above entries.
asmaron said:
Hey there,
first I have to say - I'm new here - and yes, I have searched for my issue in this forum and elsewhere, but I didn't find a solution. So I decided to register here and ask you experts about helping me to fix my problem:
I'm on Epinters-Rom CM 10.1(Android 4.2) (26/08 Built) and having a problem with a fast GPS-Fix. Always when I use GPS the first time a day it lasts about 5-10Min to get a Sat-Fix. I have done some research about this problem and found this:
In a post on a german forum (I'm from Germany) for Defy Froyo and GPS bug I encountered that there are system files that contain specific configurations for GPS or direct downloading instructions of "ancillary data" (such as A-GPS Data). However, there are no configuration files with the name "location" in Epinters-Rom as they are mentioned in this thread, but I noticed a file in my system folder (system / ect / ) called "gps.config".
Doing more research about this file, I found a post here on XDA in epinters CM10.1 thread from August. Here is mentioned, that Epinters "gps.config" has no entry to an so called "NTP server. He made this entry and now the GPS fix is quick. I didnt really see that Epinter commented this, but a year before, Epinter said (at another Rom) that the NTP server entry is no longer necessary (without further explanation).
Then I remembered (coming from Neutrino-Rom) that Neutrino has had an "GPS-Addon" that was separate flashable - a fix for every single country. So I looked at the the GPS addon of Neutrino (Germany) and behold: When flashing this GPS addon it seems, that just the "gps.config" will be fixed with the following entry for Germany:
Code:
Removed long code
Do you think I could risk simply replace the two files? Or is it better to flash the file of neutrino? Or to edit the file by Epinter right? Or at least nothing at all? I do not even want to fabricate a Brick ...
So you techies from this forum! Can you help me?
Thanks for reading this and sorry for my poor english... its not my native language!
Regards,
Asmaron
PS: The Germany.zip in the appendix contains the files that would be flashed with neutrinos Rom (including the "gps.config"). The other single "gps.config.zip" is that of Epinters Rom. Simply open it in Editor/TextEdit or similar programs and you can see the above entries.
Click to expand...
Click to collapse
For me, epinter's cm10.1 was the first time gps lock in in about 5 to 10 seconds, even if i was inside my house...
perhaps is better (previous backup) to edit the file and change the ntp servers to match your coutry's pools. then try,..
on cm7 i use an app called gps status to force calibration of the compass and to force inject fresh agps data, which helps a little
andresrivas said:
perhaps is better (previous backup) to edit the file and change the ntp servers to match your coutry's pools. then try,..
on cm7 i use an app called gps status to force calibration of the compass and to force inject fresh agps data, which helps a little
Click to expand...
Click to collapse
Hey!
Thanks for replying!
I use the GPS Status App too (and tried many other GPS Apps in market) and resetted agps-data many times an refreshed it. It helps a little but just for the moment and after one day not using GPS the fix lasts really long...
I would try to edit the "gps.conf" file but I use the Atrix as my main device, so I dont wanna brick it... Do you think, that editing this file will not force an brick? And what do you think is the best:
a) Editing Epinters "gps.conf" (of course after backing up the org. file, and everything else),
b) Exchange Epinters file with Neutrinos, or
c) Flashing Neutrinos "Germany.zip"?
Or even an absolute other solution?
Regards,
Asmaron
asmaron said:
Hey!
Thanks for replying!
I use the GPS Status App too (and tried many other GPS Apps in market) and resetted agps-data many times an refreshed it. It helps a little but just for the moment and after one day not using GPS the fix lasts really long...
I would try to edit the "gps.conf" file but I use the Atrix as my main device, so I dont wanna brick it... Do you think, that editing this file will not force an brick? And what do you think is the best:
a) Editing Epinters "gps.conf" (of course after backing up the org. file, and everything else),
b) Exchange Epinters file with Neutrinos, or
c) Flashing Neutrinos "Germany.zip"?
Or even an absolute other solution?
Regards,
Asmaron
Click to expand...
Click to collapse
Humm.. I edited the file and had no problems, I think edit is the safer option due to Neutrinos' files are for Gingerbread and we don't know what changed in the middle
andresrivas said:
Humm.. I edited the file and had no problems, I think edit is the safer option due to Neutrinos' files are for Gingerbread and we don't know what changed in the middle
Click to expand...
Click to collapse
Hmm... yeah thats true... so you have edited the file by yourself? What entries did you add? I thought Epinters settings worked for you?
asmaron said:
Hmm... yeah thats true... so you have edited the file by yourself? What entries did you add? I thought Epinters settings worked for you?
Click to expand...
Click to collapse
Sorry, that was on Gb, I edited the ntp servers to the ones off my country (Argentina). I was using root explorer at the time, but in cm10 the stock file manager can do it without problems (I used it to edit touchpad.cfg to fix raindrop bug). Only thing is you need to give it access via the app settings (can't remember as I'm back on cm7)
Hey!
Meanwhile I flashed the ROM from "Zn7mkUKzN1r8aCIV" where the flash is working. The fix lasts also very long and wasnt even stable. The entries of the "gps.conf" of "Zn7mkUKzN1r8aCIV" are exactly the same as the ones of epinter. So i tried to edit the "gps.conf":
- Editing the strings from the neutrino file (check OP), had the result that i didnt get a fix in even a half an hour.
- Restoring the "gps.conf" has the result of getting a fix after some minutes but not very stable.
- Now I have a edit of the "gps.conf" with the strings nlabrad mentioned in the post i told you before and the NTP-Server-Entries of Neutrino for germany (without blanks between the "="). Now i get a fix after some minutes that is stable, but the accuracy gets not better than 100 meters (328 feet). It stucks here and gets not better even after more than half an hour having a stable fix. To be exact it gets not better and not even worser. It stucks exactly at 100 meter accuracy.
Now i will test the GPS fix from that is mentioned here and i will report later!
Regards,
Asmaron
Did it!
Hey there!
I did it!
First it didn't work to exchange the "libnmea.so" from Krystian mentioned in the post above using the integrated file explorer. I allways got an Error when editing/copying/deleting the orig. "libnmea.so" in the "system/lib" folder. After that error somtimes GPS didn't work anymore at all (cant start it) or nothing was changed to the accuracy of the GPS. Well I have seen that by exchanging the file you have to set the permissions new (chmod 644) but I wasn't able to change it without getting an error.
So I tried another way: I extracted the Files of Zn7mkUKzN1r8aCIV's ROM and exchanged the "libnmea.so" org. file with the file from Krystian. I also replaced the "gps.conf" with an modified "gps.conf" containing the Neutrinos Strings from the Germany "gps.conf". Than I ziped and signed the modified files with LambOfGods Zip Signer Tool (v1.1) and flashed it (wiped Cache & Dalvik).
And now: Get a GPS-Fix (indoor) in about 45 sec with an accuracy of about 4 meters! YEAH! :victory:
Thanks for helping! Esp. thanks to you andresrivas and of course Zn7mkUKzN1r8aCIV and Krystian and so on!
Regards,
Asmaron
[/COLOR]
asmaron said:
Hey there!
I did it!
First it didn't work to exchange the "libnmea.so" from Krystian mentioned in the post above using the integrated file explorer. I allways got an Error when editing/copying/deleting the orig. "libnmea.so" in the "system/lib" folder. After that error somtimes GPS didn't work anymore at all (cant start it) or nothing was changed to the accuracy of the GPS. Well I have seen that by exchanging the file you have to set the permissions new (chmod 644) but I wasn't able to change it without getting an error.
So I tried another way: I extracted the Files of Zn7mkUKzN1r8aCIV's ROM and exchanged the "libnmea.so" org. file with the file from Krystian. I also replaced the "gps.conf" with an modified "gps.conf" containing the Neutrinos Strings from the Germany "gps.conf". Than I ziped and signed the modified files with LambOfGods Zip Signer Tool (v1.1) and flashed it (wiped Cache & Dalvik).
And now: Get a GPS-Fix (indoor) in about 45 sec with an accuracy of about 4 meters! YEAH! :victory:
Thanks for helping! Esp. thanks to you andresrivas and of course Zn7mkUKzN1r8aCIV and Krystian and so on!
Regards,
Asmaron
Click to expand...
Click to collapse
hI! I'm having hard time to understand exactly what you did to fix GPS accuracy. I'm the guy who asked Zn7mkUKzN1r8aCIV about the bug and I tried to overwrite the libnmea.so but it didn't work.... (I've had to flash again the rom to get back to 100m accuracy) Can you explain in a easier D) way how to fix it? I understand that you made a flashable zip maybe can you share it?
Hey there!
Well what I did exactly is:
1) Downloaded Zn7mkUKzN1r8aCIV's ROM (from 10/10/13) and extract it
2) Downloaded "libnmea.so" from Krystian
3) Replaced Zn7mkUKzN1r8aCIV's original "libnmea.so" in folder "system/lib/" with Krystian's one
4) Edited the "gps.conf" of Zn7mkUKzN1r8aCIV in folder "system/etc/" with the strings of Neutrinos "gps.conf" for germany (!) mentioned above *
5) Ziped and signatured the GPS-modified ROM files with "LambOfGods Zip Signer Tool (v1.1)" mentioned above
6) Wiped Cache & Dalvik - Flashed and GPS worked
I've uploaded my GPS-modified ROM with the german (!) "gps.conf" here:
Based on Zn7mkUKzN1r8aCIV's ROM 10/10/13 wich is based on Epinters ROM with modified GPS files for Germany from Krystian and Neutrino
Click to expand...
Click to collapse
with
a) "Standard"-Kernel:
CM10.1_Android4.2_GPSmodified.zip - 166.48 MB
b) "Hporch32-"Kernel (when Screen-Tearing occurs):
CM10.1_Android4.2.2_GPSmodified_hporch32.zip - 166.48 MB
I can't edit the "gps.conf" for every single county. Thats to much work. But you can do that on your own! I uploaded the files of Neutrionos "gps.conf"-Tweak here so you can download it and take the strings that you need for your country. In your case, I would do the following:
1) Download my GPS-modified ROM
2) Flash it, reboot and try out GPS - I will not take any responsibility for defects of your hardware! You flash it on your own risk!
2.a) If it works fast, its proofed that Neutrinos Strings in the "gps.conf" has no real effect - you can go to step 8
2.b) If it doesn't work (fast) you go to step 3
3. Download Neutrino GPS-Files and extract them
4. Choose the "gps.conf" that is related to your country (always stored in "system/etc/" folder of the zip-file of your country) and open it with editor
5. Edit the strings in the "gps.conf" on your Atrix (folder "system/etc/" - you will see, there are the german strings) with the ones of your country from the Neutrino File (make sure that there are no blanks between the " = " of each string**)
6. Save your edited "gps.conf" of the folder "system/etc" & check (imperative!) that the rights of the file are set on chmod 644!
7. Reboot and try out GPS
8. (Hopefully) Enjoy!
I hope it works! Looking forward to hear your report!
Regards,
Asmaron
* It is not proofed that this has any effect, but I think so, and now I have a GPS-Fix in almost a half minute.
** The effect of this is also not proofed! What I mean is type e.g.
Code:
NTP_SERVER=0.de.pool.ntp.org
instead of
Code:
NTP_SERVER = 0.de.pool.ntp.org
Hey! Did it work for you?
If not i have another suggestion:
Download my modified GPS-ROM, flash it (on your own risk), download the app "faster GPS" from playstore, choose your country settings in the app. It will modify the "gps.conf" and will set the NTP-Server settings for your country and region.
Maybe it helps... would be glad if you report here!
Regards,
Asmaron
libnmea.ko hack works on ICSROM (and related, I imagine)
asmaron said:
[...] Now i will test the GPS fix from that is mentioned here and i will report later!
Regards,
Asmaron
Click to expand...
Click to collapse
Came across this searching for a fix on my recent ICSROM update. I had to do the same thing when I first root/unlocked to install MROM, so that certainly helped. I noticed that the files sizes were identical, and not to the GB files, as one would expect. Anway, the issue manifested as GPS apps showing 0 accuracy, and WiFi-disabled Google Maps showing 1200m accuracy. After updating the file and chmod, it was showing ~7m accuracy.
Yup works a-ok...
jeremywh7 said:
[...] After updating the file and chmod, it was showing ~7m accuracy.
Click to expand...
Click to collapse
I meant '7ft accuracy' above. Anyway, I tested on my way to work this morn; locked at 5ft. I did see a couple times when it lost the lock and jumped around the map, but was brief. And I recall seeing that happen on the GB rom too.
Related
Current version: !IMEIme 2.2.0.4
Bug Fix
Fixed bug in use previous patch that could result in variable used before declared error.
Changed processing order when custom patches were to be used
The program will now process custom patches prior to editing framework.jar and build.prop edits. With new kernel patches requiring a new build.prop users would lose build.prop edits if the kernel was included in custom patches, the program will now patch any user modifications, then process IMEI generation and build.prop edits.
Updated to work with ROMs that do not include GSMPhone.smali
Recently, many ROMs are not including GSM phone utilities in framework.jar. I have added testing for missing GSMPhone.smali and patching via TelephonyManager.smali if necessary.
UPDATED FILES UPLOADED
MANY of the support files have been updated to the newer versions (smali, baksmali, adb and components).
I encourage you to delete all files in your existing IMEI Generator folder and use the new !IMEIMe.exe to generate the files necessary.
The devices.dat file if you've used the previous version has several issues that prevents the device model from being correctly patched on many of the devices. This has been fixed here and in the device list thread.
There is a known issue with the GUI when your screen settings are set at 125% in Control Panel - Appearance and Personalization - Display... I will work on fixing that in the next release.
Bug reporting thread for !IMEIme
Device list thread
New features:
Will patch GSMPhone.smali if present in framework... patches TelephonyManager.smali otherwise.
I chose this method since more ROMs are coming out for wifi tablets that do not have GSM phone information included in framework.jar. I was playing with CM10.1 and discovered GSMPhone.smali is not present, thus I was getting unable to patch GSMPhone.smali error, and there was no patching for an IMEI. In all honesty... this should be irrelevent, since IMEI is only utilized in cellular communications on GSM phones... however... some applications MAY (xda free does) require an IMEI to work, even on wifi only devices.
ODEX files still in the works
odex file support... I think this solution will work on odex file systems as long as the patching is done on the ROM prior to flashing to device (anyone using odexed system please let us know) and I am working on in place patching on odexed systems... however, I am not completely comfortable since there is a lot of work done by the device itself during odexing of the modified files... I am very hesitant since any mistake could render a bricked device and I don't have a system to test with prior to release.
Previous Important Changes
The new version of the IMEI Generator will no longer overwrite your existing devices.dat file with the current. To use new devices.dat file, delete the old one prior to running the program, or download the new one and unzip it in the IMEI Generator directory.
Device Communications not necessary in certain situations
If you select to Update ROM, using Serial Number based IMEI and do not select Encrypt IMEI, the program will no longer need to communicate with the device when performing its tasks. The framework.jar patch will not hard patch the IMEI in this situation as before. This is useful for patching a ROM for distribution to multiple people, since they will all maintain unique IMEI's. This is accomplished with the following change in the framework.jar
Code:
/com/android/internal/telephony/gsm/GSMPhone.smali
.method public getDeviceId()Ljava/lang/String;
[b]changed[/b] iget-object v0, p0, Lcom/android/internal/telephony/gsm/GSMPhone;->mImei:Ljava/lang/String;
[b]to[/b] sget-object v1, Landroid/os/Build;->SERIAL:Ljava/lang/String;
prior to patching in code to prepend "0"
.method public getDeviceSvn()Ljava/lang/String;
[b]changed[/b] iget-object v0, p0, Lcom/android/internal/telephony/gsm/GSMPhone;->mImeiSv:Ljava/lang/String;
[b]to[/b] sget-object v1, Landroid/os/Build;->SERIAL:Ljava/lang/String;
prior to patching in code to prepend "0"
To try to explain the above a little...
The above is always changed, no matter what IMEI generation method you select...
If you select Serial Number and New Type IMEI and not Encrypt: no other patching is done for the IMEI... this can be implemented on many devices, since each will have a unique serial number.
If you select Serial Number and do not select New Type: additional code is added to format the IMEI to the old standard ("00-" and "-"s)... this can be implemented on many devices for same reason.
If you select MAC Address or Encrypt (or both): additional code is added that results in the IMEI being hard coded, this makes it very much device specific.
If you select MAC Address or Encrypt (or both) and do not select New Type: additional code is added that results in the IMEI being hard coded as well as code to format the IMEI, this makes it very much device specific.
Use Custom Patch NOTE: This is only used when patching a ROM
This is going to take some major explanation, since I ran into so many possible scenarios...
One thing of note... the only additional lines added to updater-script will be for files in the base directory
The order of processing is:
1. Original ROM updater-script and files
2. Custom Patch zip file
3. Custom Patch folder
The program will utilize folders (from Patch zip file or Patch folder itself) named modboot, modsys, or system (not case sensitive in windows) as well as files in the base folder
Any files in modboot will be moved to the root of the **ROM**-IMEI.zip file and lines added to updater-script as needed
Any files in modsys will be moved to the system directory of the **ROM**-IMEI.zip file
If Custom Patch is checked...
/META-INF/com/google/android/updater-script is extracted from the ROM
the program will ask you to select the Custom Patch Folder
If there is a zip file present in the folder the program will ask if you want to use it
You have 3 options, "Yes", "No" or "Cancel"
Yes = Use the zip file
No = Don't use it, select another
Cancel = Don't use a zip file
If you use a zip file, it will extract the zip file and process the updater-script in it for any additional lines needed
After the above, any non-zip files and modboot, modsys and system directories in the Patch Folder will be processed
I chose this order so you can have a "go to" patch zip file, and test other additions by using the file, folder options prior to including them in the zip.
Example here:
I have my custom patches in folder /CM7/UserMods with these contents:
/META-INF
/modboot
/modsys
patch.zip
The program processes patch.zip first, then overwrites any files with the files in modboot and modsys
It also processes /META-INF/com/google/android/updater-script for any lines extracting files to /boot and adds them to the original ROM updater-script if not already there.
It then adds lines for any files originally in /modboot to updater-script to extract them to /boot
"New IMEI Type" of IMEI which no longer has the "-"s in it, but maintain backward compatibility for those who already have IMEI's generated or prefer the old style. When the new type is selected in the GUI:
NOTE: Per the IMEI standards... Using a single 0 prepended to the IMEI indicates a TEST IMEI for a country with 3 digit international code... while it should have no implications to us since we are not on a cell... it may provide potential country validity issues... I will monitor this and resort to 00 prefix in the new type of IMEI if necessary.
ADDITIONAL NOTE: Per the IMEI standards... For devices without an IMEI, they are to provide a unique serial number to be used... This program modifies framework.jar to allow this.
I am now patching framework.jar in the /com/android/internal/telephony/gsm/GSMPhone.smali file instead of /android/telephony/TelephonyManager.smali (this change is what allows the information to display in the about tablet information)
I am renaming and patching 2 functions... getDeviceID() and getDeviceSvn()
By patching the two functions in this file... the IMEI now shows in Settings... About Tablet... Status... no longer have to use external program or dial *#06# to verify the device is patched.
getDeviceID() shows it in IMEI
getDeviceSvn() shows it in IMEI SVN
You can rename or copy !IMEIme.ini to IMEIme.ini and the program will work.... useful for *nix users and probably mac users... since they have issues with special char actors (!)... While I like to use it in windows to keep the executable and ini file at the top of the file list in windows explorer... anyway...
The program looks for IMEIme.ini first and uses it if present... if it is not... it then looks for !IMEIme.ini (which will be there... because the program installs the generic !IMEIme.ini if it isn't ) This also provides a good way to keep your ini.. and see the new settings in the compiled in ini.
GUI selection and related ini setting
GUI: New IMEI Type
INI Setting:
New_Type =
; If 0 then the old type of "00-XXXXXX-YYYYYY-ZZZ" will be used
; If 1 then the new type of "00XXXXXXYYYYYYZZZ" will be used
BUG FIX
No known or reported bugs to work out.
!IMEIme.ini file default settings and explanation:
Code:
;The setting options are 1 (use the option) or 0 (don't use the option)
;WiFi IP Address can be set to your Nook's IP address here to a default to use
;IMEI can be set to a default here... you can also set the seed you use for generation
;Setting Device_Manufacturer to anything will result in an edit to build.prop setting the entered manufacturer
;IF Device_Manufacturer is NOT blank then:
;Setting Manufacturer_Device to anything will result in an edit to build.prop setting the entered device
;
;NOTE: ONLY Device_Manufacturer is necessary for this edit... there have been no software that appears to
; require a device edit
;
;Setting LCD_Density will result in build.prop edit for this setting regardless of Device_Manufacturer setting
;
;Set all options in [Settings] section at the bottom
[Settings_Explained]
Use_In_Place = 1
; If 0 Disable In Place patching... useful for those who always update AOSP ROM files and never patches on device framework.jar
; If 1 Enables In Place patching if ADB is working
Use_Previous_Patch = 0
; If 0 Ignore IMEI.fix
; If 1 AND IMEI.fix exists... use it for patching
Use_Serial_Number = 1
; If 0 then do not base IMEI off of Device Serial Number
; If 1 then base IMEI off of Device Serial Number
; NOTE: This takes priority over Use_MAC_Address
Use_MAC_Address = 0
; If 0 then do not base IMEI off of Device MAC Address
; If 1 then base IMEI off of of DeOvice MAC Address (last 5 hex words) (2 bytes = 1 hex word)
; 0A is converted to 010, FF is converted to 255 etc.
; NOTE: Use_Serial_Number takes priority
Use_Manual_Input = 1
; If 0 then Manual Input disabled
; If 1 then Manual Input enabled
Encrypt_IMEI = 1
; If 0 then uses actual data for IMEI... i.e. Serial Number (last 15 digits) or MAC Address (last 5 hex words) is actual IMEI
; If 1 then program encrypts data for IMEI generation... hiding actual Device data
New_Type = 1
; If 0 then the old type of "00-XXXXXX-YYYYYY-ZZZ" will be used
; If 1 then the new type of "00XXXXXXYYYYYYZZZ" will be used
Use_ADB = 1
; If 0 then ADB is disabled... this will prevent In-Place updating from working all together
; If 1 then ADB is enabled... In-Place will work... IF adb is working on your device
; NOTE: This takes priority over Use_ADB(usb) and Use_ADB(WiFi)
Use_ADB(usb) = 1
; If 0 then ADB via USB connection is disabled... I use this since some ROM's have Debug Mode issues
; If 1 then ADB via USB is enabled and attempted first
; NOTE: Use_ADB takes priority over Use_ADB(usb) and Use_ADB(WiFi)
Use_ADB(WiFi) = 1
; If 0 then ADB via WiFi connection is disabled
; If 1 then ADB via WiFi is enabled... I use this since some ROM's have Debug Mode issues
; NOTE: Use_ADB takes priority over Use_ADB(usb) and Use_ADB(WiFi)
Clean_Up = 1
; If 0 then the program will leave all support files when cleaning up and exiting
; If 1 then the program will delete all support files when cleaning up and exiting if none of them
; existed at program start
Include_Patch = 0
; If 0 then custom patches is disabled
; If 1 then the program will prompt for custom patches to include
Device_Manufacturer =
; If blank then the program will not edit build.prop
; If anything other than blank the program will edit build.prop to include manufacturer
Manufacturer_Device =
; If blank then the program will not include device in build.prop edit
; IF anything other than blank the program will include device in build.prop edit
; NOTE: No build.prop edit will occur if Device_Manufacturer is blank
Device_Model =
; If blank then the program will not include model in build.prop edit
; IF anything other than blank the program will include model in build.prop edit
; NOTE: No build.prop edit will occur if Device_Manufacturer is blank
Build_Fingerprint =
; If blank then the program will not include Build Fingerprint in build.prop edit
; IF anything other than blank the program will include Build Fingerprint in build.prop edit
; NOTE: This edit will occur even if Device_Manufacturer is blank
LCD_Density =
; If blank then the program will not include LCD Density in build.prop edit
; IF anything other than blank the program will include LCD Density in build.prop edit
; NOTE: This edit will occur even if Device_Manufacturer is blank
WiFi_IP_Address =
; You can enter the default Device IP address here... especially useful if you are only using this on one device...
; or if you keep seperate folders for each device you use (!IMEIme.exe and !IMEIme.ini must be in each folder)...
; i.e. folder for "sister" containing the program and ini file at minimum.
; If blank the program will prompt you for the IP address of the device to establish ADB WiFi connection
IMEI =
; Enter a base 10 (integer) and it will be used as the IMEI (duplicated until 15 digits is reached)
; Enter your "seed" and the program will generate an IMEI based off of it
; NOTE: If you try to generate the old GENERIC IMEI the program will not do it
[Settings]
Use_In_Place = 0
Use_Previous_Patch = 0
Use_Serial_Number = 1
Use_MAC_Address = 0
Use_Manual_Input = 1
Encrypt_IMEI = 0
New_Type = 1
Use_IMEI(15) = 0
Use_ADB = 1
Use_ADB(usb) = 1
Use_ADB(WiFi) = 1
Clean_Up = 1
Include_Patch = 1
Device_Manufacturer =
Manufacturer_Device =
Device_Model =
Build_Fingerprint =
LCD_Density =
WiFi_IP_Address =
IMEI =
Credits:
mthe0ry: Credit for the original IMEI patches released for us Nookers(TM). His original thread is here...
martian21: Took mthe0ry's work and maintained it for releases of CM7, upeating it for each nightly that needed a new one. Martian21's thread.
HacDan on irc.freenodes.net #nookcolor for helping me figure out patching GSMphone.smali instead of TelephonyManager.smali
Thank you's:
paleh0rse: I believe was the first to download and test this program... I think the first bug report too... helped many users with suggestions regarding their apps.
mr_fosi: Continues testing and reporting despite no need to. Tested a few private beta builds to help iron out a significant issue. Also providing information regarding Phone App *#06# IMEI test.
martian21: Set the wheels turning. Provides invaluable feedback and suggestions. He is an invaluable tester and Q&A guy. Thanks for dangling that bait
mellopete: Provided the very first bug report... prompted me to include necessary files in the program itself.
TheMainCat, 12paq and frankusb: Provided bug reports leading me to look at why some Windows versions didn't run the program initially.
Nayla1977: Bug report regarding a mistyped EndIf in my source.
jdexheimer: Bug report that lead me to find a problem with folders with spaces in them.
LinuxParadigm: Bug report regarding missmatching If - EndIf's.
BitingChaos: first public post to get me back on target.
dillweed, garrisj and many others: for PM's indicating the importance of this solution.
lemdaddy for reporting the bug that we tracked down to the java version and reporting back that it was the java version causing issues.
adusumilli for reporting the bug where IMEI was generated as "00-cat: c-an't o-pen"
topcaser for being persistent enough with the bug causing In-Place to fail in certain situations.
HacDan on IRC for leading me in the right direction to impliment the patching of GSMphone.smali.
We are all adults, if we break our toys... we only have ourselves to blame and we may have to buy new ones... (this will NOT break your Nook... I PROMISE you that! but it may break some of your apps... more on that later in post)
BUG REPORTING:
This program was initially ineteded to generate a unique IMEI based on your device S/N and update Dev's install zip files... it has become so much more, and as such there are many functions involved in this process.
Due to the complexity the program has taken on... far beyond what I initially intended... to report bugs please try to use the following as a template:
Function attempting: i.e. Updating ROM... In Place Upgrade... Update framwork saved on computer... etc.
Error Messages: any error message you receive... or the last message you saw prior to the issue.
End result: i.e. GSMphone.smali updated, ROM not... GSMphone.smali updated framework.jar not... etc....
Environment: ROM in same folder as IMEIme.exe... ROM on same drive as IMEIme.exe... ROM on different drive... etc. (same for framework if updating framework instead)
!IMEIme.ini settings: you can put your entire ini file if you'd like.
If you could take notes of EXACTLY what which selection in the GUI you have selected and any buttons you click on which prompt it would be EXTREMELY helpful...
As I said, this program has taken on functions I initially had not imagined including... the more features added, the more complex testing and tracking bugs becomes... I don't want to include a bunch of messages just for the sake of letting you know where in the code you are... would not be beneficial to you... more buttons to click for no reason, etc.
The more detailed you can be, the quicker I can see what is happening... otherwise I have to try to duplicate what I think you are doing when you get the error.
mr_fosi and martian21 have been very tedious in reporting bugs... I greatly appreciate their testing despite not needing to, and the manner in which they document what is going on....
Everyone should click "Thanks" on their bug report posts... they have been instrumental in getting the program where it is so far.
Background:
Some developers require a unique number that is supposed to be provided by hardware manufacturers that is unique to every device. This unique number (IMEI) is extremely important in devices utilizing cellular communications.
Since B&N has not registered IMEI numbers for the Nooks, the AOS's we are using do not acquire it as they do in other Android devices.
The developers that require a unique IMEI have been less than receptive of our devices and past methods to provide functionality to utilize their apps.
I decided to provide what I believe to be a viable solution to this problem.
What this program is:
It is a method to provide a unique IMEI (with reasonable certainty) for our Nooks.
It IS intended to be a supplement until IMEI is addressed in dev's ROM's.
It IS viable for Froyo... CM7... CM9... CM10...Honeycomb... MIUI.... AOKP... and others.
I can't think of any reason it will not work with ANY ROM you choose to utilize... if you run across one... just let me know and I'll see if I can't fix that.
What this program is not and does not do:
This is not a perfect solution to our Nook specific issues. Let me make it PERFECTLY CLEAR there is NO PERFECT SOLUTION We are generating an IMEI from something else... I use TEST IMEI patterns based off of our device serial number, to ensure apk devs wouldn't come down on us.
It is not targeting any specific AOS.
It is not guaranteed to be accepted by any other developers.
It is not intended to be the end all, beat all solution.
It is not intended to dissuade other developers from providing what they feel is a better method.
It will not cause any programs to show in the market. That has to be dealt with via APK developers and/or build.prop Manufacturer strings.
Potential issues:
There is NO legitimate solution to the IMEI issue we Nookers (TM) face... unless a group desires to register a block of them for our use... thus I am generating TEST IMEI's... ideal... no, but the only method available to us.
While I feel, with significant certainty, there will be no negative consequences from apk devs in general, I cannot speak for them, or their logic. This can easily be disabled by them again. That is on them, not me or us. By the same token, they can decide to stop providing their service for cause, I still have no control over that.
Above, I emphasize “with reasonable certainty” due to the fact that, in theory, you can wind up with an IMEI that 9 other Nooks that use this software has. That can only happen if the other 9 owners use this program and have a serial number within the same 10 as yours. This is even less likely with the New IMEI Type since it is using the right most 16 digits of a device serial number (and we know they all start with 2)
If everyone who has the same beginning 15 digits utilizes this program to generate an IMEI, you will all wind up with the same IMEI. Given the number of Nooks out there compared to the number of user's hacking them.... I find it extremely difficult to believe, with a reasonable certainty, that any 2 (much less 10) devices would ever wind up with the same IMEI generated by this program. This is prevented when using the New IMEI Type
What this program does/is capable of:
It allows you to extract framework.jar from a developers update zip file.
It will allow you to pull framework.jar from your Nook or use an existing framework.jar already stored on your computer.
It will generate an IMEI based on your Nook's serial number (or MAC Address) if adb is working on your system. If you have issues running adb via USB (ADB(USB)), it provides the opportunity to utilize adb via WiFi (ADB(WiFi)) for any computer-device communications.
It will provide you a method to manually input your serial number if you cannot connect to the device via adb. You can also input a “seed” (easy to remember word or phrase) and generate an IMEI based on the ASCII codes of the text you enter.
It will edit /com/android/internal/telephony/gsm/GSMPhone.smali to rename any existing getDeviceId() and getDeviceSvn() function to getDeviceId2() getDeviceSvn2() and append the patch to end of that file. NOTE: When the program "smali's" the resulting GSMphone.smali... it relocates the appended function to be before the renamed function.
It will save the patch as IMEI.fix, thus allowing you to utilize it for subsequent runs of the program. A caveat to this is... if you run it from the same folder on a friend's Nook... it will overwrite your original one if it is in the same folder or they will have the same IMEI as you do if you use Previous Run.
It will offer to push the patched framework.jar to your Nook... IF you opted to pull framework.jar from your Nook AND adb successfully worked to do that. This facilates in place upgrading.
It will backup the existing developers zip file appending “-IMEI” to it, distinguishing it is one this program has been used on. It will update this file, not the original developers file.
If there are issues with file names that become duplicate in a case insensitive OS such that windows is, it will warn you of this case and not remove the updated framework.jar to facilitate manual updating of the zip file.
Caveats:
This program is known to work on Java version 1.6.0_23 and known NOT to work on version 1.6.0_17 or earlier. If your system seems to work fine... but the nook does not give you an IMEI number... check your java version by typing this in a DOS window (start-run and type in cmd):
java -version
this will tell you the version of java you are running.
Java must be on your system. It must be in your system's path statement, or this program must be in the java/bin folder. It is possible that you must have java 32 bit version, this is being researched.
It will very likely break your swype, or any other app that utilizes IMEI for validation and you have used previous methods to circumvent their validation process.
It will likely break the same software if/when developers include a fix to the Nook IMEI situation in their AOS. Unless you opt to use this method again on their AOS to ensure you maintain the IMEI you used my program to generate.
Since I have opted to utilize test formed IMEI's to prevent duplicating someone's “real device” IMEI, software developers can easily shut us down again. That is their option. I am trying to provide a solution that is acceptable to both sides of the fence.
Closing statement:
As I desire to make this program as beneficial as possible... PLEASE provide any feedback and/or bug reports... just don't continue to push your ideals once it has been discussed... beating dead horses gets tiresome and just wastes precious time.
112 downloads of 2.2.0.3 with bug when pervious fix was selected
1686 downloads of 2.2.0.2 with no bugs reported
141 downloads of 2.2.0.1 with CM10 in place bug that would cause BBSOB and never boot
197 downloads of 2.2.0.0 (that actually appeared to be 2.1.0.4 in the zip) with a few minor bugs... mostly in custom patching
648 downloads of 2.1.0.3 with known GT for GameLoft issues
1123 downloads of 2.1 with no known bugs
182 downloads of 2.0a with a Generic IMEI bug
1919 downloads of 1.9 with no bug reports
3131 downloads of 1.8 with all bug reports being for non-nook devices
80 downloads of 1.7 with no bug reports
600 downloads of 1.6 with a couple of reports of In-Place update bug
880 downloads of 1.5a with 0 bug reports
148 downloads of 1.5 with a bug that could result in IMEI being generated without being properly formed.
36 downloads of 1.4 with a bug that could result in IMEI of "cat: can't open".
258 downloads of 1.3 with 0 bug reports... time to move on with next feature.
1618 downloads of 1.1 and the only bug noted has been tracked to the user's Java version.
12,758 downloads prior to the current version.
Bug reporting thread for !IMEIme
Device list thread
Looks like I have something new to mess with tomorrow night... thanks for working this, we owe ya!
Been looking forward to this! Thanks for your hard work DizzyDen.
Tested it out however it isn't finding 7zip. I've tried both the 64-bit and the 32-bit version (on 64-bit Windows 7). I'm probably doing something wrong if so please feel free to enlighten me
Martian21
martian21 said:
Been looking forward to this! Thanks for your hard work DizzyDen.
Tested it out however it isn't finding 7zip. I've tried both the 64-bit and the 32-bit version (on 64-bit Windows 7). I'm probably doing something wrong if so please feel free to enlighten me
Martian21
Click to expand...
Click to collapse
It wasn't you... there's something weird with the API to the fileopendialog that changes the working directory... a TEMPORARY work around is to copy the zip file to the folder you are running the program from.
Updating to beta 2 to auto extract support files on run.
Beta 2 is up... OP updated... note the bold text... for now the zip file must be in the same folder as IMEIme.exe
That will be fixed shortly.
Updated to beta 3. OP updated.
Fixed file browse for update file.
Improved cleanup behind itself before exiting...
removes helper files
removes framework.jar
removes classes.dex
removes out folder
removes system folder (the one used to add framework.jar to the zip file)
Still debating ability to allow manual input of the IMEI or a serial number... but those that want to do it will probably figure out how to do it manually... its REALLY not that hard.
Will add random IMEI generation as an option. The only purpose I see for this is for those who don't want to use the generic IMEI and cannot get adb working... even with the included adb in this program.
Feedback and bug reports are welcome and will help improve the program.
Thank you for this
I had to copy my AdbWinApi.dll for it to work. It did not put the new framework.jar in the zip though. It made the files, but didn't update the zip. I moved it to the root of my drive and ran it as administrator, but it still didn't update the zip. I am using Windows 7 x64. I used the IMEI.fix file and updated the zip myself. Thanks again for this nice tool.
mellopete said:
I had to copy my AdbWinApi.dll for it to work. It did not put the new framework.jar in the zip though. It made the files, but didn't update the zip. I moved it to the root of my drive and ran it as administrator, but it still didn't update the zip. I am using Windows 7 x64. I used the IMEI.fix file and updated the zip myself. Thanks again for this nice tool.
Click to expand...
Click to collapse
Did you use something prior to b3 ?
There was an issue I discovered that was preventing appending IMEI.fix to TelephoneProvider.smali that was fixed in b3.
I did my development on windows64 so that shouldn't be an issue.
As for the dll... I hadn't experience issues with that... but I can certainly add it to the program.
Both adb dll's will be included in all releases after b3.
Good job!
Can you explain more about how rom is being affected?and what to check?
Sent from my phiremod for Nook using Tapatalk
DizzyDen said:
Did you use something prior to b3 ?
There was an issue I discovered that was preventing appending IMEI.fix to TelephoneProvider.smali that was fixed in b3.
I did my development on windows64 so that shouldn't be an issue.
As for the dll... I hadn't experience issues with that... but I can certainly add it to the program.
Both adb dll's will be included in all releases after b3.
Click to expand...
Click to collapse
b3 is the first one I tried. I didn't look at the classes.dex before it was deleted. I will check.
RASTAVIPER said:
Good job!
Can you explain more about how rom is being affected?and what to check?
Sent from my phiremod for Nook using Tapatalk
Click to expand...
Click to collapse
Read here http://forum.xda-developers.com/showthread.php?t=1004102
TelephonyManager.smali did not change.
mellopete said:
TelephonyManager.smali did not change.
Click to expand...
Click to collapse
Please make sure b3 is the one you are using. When you originally posted... the thread was showing 0 downloads of that file.... or just wait a few minutes... beta 4 is on its way shortly.
To ensure TelephonyManager.smali is not changed you need to look in two places.... the easiest way is to search for getDeviceID
If it worked correctly you should find 2 instances... the first is the original function and my program renames it to getDeviceID2()... the second should be the one !IMEMe adds to the end of TelephonyManager.smali
Additionally... could you check and see if your run is actually overwriting update zip file.... see if there is a update ".zip.tmp" file left over... if it is there... the zipping is running into an issue overwriting the original file... I thought I had that issue worked out... but may need to add a check for that within my program.
I d/l b4, dropped it in a directory with just the .zip for n87 and ran it (win7 pro 64-bit). It errored out and here's the play-by-play of each of the windows which popped up one immediately after the other:
- I was warned about you being an unverified software publisher, which I OKed.
- "Windows cannot find 'java'. Make sure you typed the name correctly, and then try again." I OKed this one as well.
- window titled "DizzyDen's IMEI Generator" containing: "Return Code is:0 and Error Code is: 1"
- window titled "DizzyDen's IMEI Generator" containing: "Java is required on your system. You can download the current version from http://java.com"
I have JRE6 on my machine, though it is not in the system PATH.
Oh, and there were files for 7za, adb, .dll's and .jar files left behind.
mr_fosi said:
I d/l b4, dropped it in a directory with just the .zip for n87 and ran it (win7 pro 64-bit). It errored out and here's the play-by-play of each of the windows which popped up one immediately after the other:
- I was warned about you being an unverified software publisher, which I OKed.
- "Windows cannot find 'java'. Make sure you typed the name correctly, and then try again." I OKed this one as well.
- window titled "DizzyDen's IMEI Generator" containing: "Return Code is:0 and Error Code is: 1"
- window titled "DizzyDen's IMEI Generator" containing: "Java is required on your system. You can download the current version from http://java.com"
I have JRE6 on my machine, though it is not in the system PATH.
Oh, and there were files for 7za, adb, .dll's and .jar files left behind.
Click to expand...
Click to collapse
java will need to be in your path... I have no way of including all possible locations of where it could be installed... and it is way too big to include with my program.
The left over files is due to the program exiting when it did... I will fix that in next beta... should have waited until java was tested to extract them... or have it perform cleanup before exiting on any errors... sorry bout that.... you can leave them... when you have successful run (or run beta 5 or later) it will clean them up.
For now you may have to run as administrator.... I will try to add code to avoid this in the short future.
BTW. Nowhere does getDeviceID does it say that it must be a well formed IMEI.
nemith said:
BTW. Nowhere does getDeviceID does it say that it must be a well formed IMEI.
Click to expand...
Click to collapse
As much as I admire your work... I am honored that you are even checking this out.
I do understand that as of now it is not required... but I figure if I utilize standards (as much as there are anyway) we may avoid future issues if dev's start checking for well formed IMEI's.
I figure if I'm going to make this... I might as well make it right.
As far as I can determine... if a sw dev implemented IMEI checks, the only thing that could cause them to shut down someone using this would be to check that it is a "TEST" IMEI... but I don't see that happening, because hardware manufacturers do use these in testing.
DizzyDen said:
java will need to be in your path... I have no way of including all possible locations of where it could be installed... and it is way too big to include with my program.
Click to expand...
Click to collapse
Roger that. Should the instructions then note either the required change to PATH or that the file must be run in the user's jre#\bin directory?
DizzyDen said:
The left over files is due to the program exiting when it did... I will fix that in next beta...
Click to expand...
Click to collapse
I figured as much, but thought you should know.
DizzyDen said:
For now you may have to run as administrator...
Click to expand...
Click to collapse
I ran it this way and got the same behavior.
I'll keep a lookout for further versions, test them and report.
Beta 5 is up... OP updated to include Java requirements... thank you mr_fosi for pointing this out.
RASTAVIPER said:
Good job!
Can you explain more about how rom is being affected?and what to check?
Sent from my phiremod for Nook using Tapatalk
Click to expand...
Click to collapse
Did you find the information in the thread linked in response to your questions?
TY mellopete for that.
- Plugged NC into USB port.
- Copied new B5 exe and n87 zip to java\jre6\bin directory.
- Ran exe as admin.
- Prompted for .zip check ("is this correct") and it was, so I OKed it. Not OKing it gave me the option to browse for the file, which I cancelled, resulting in a termination of the prog with a few more dialogs. Any extracted files were cleaned up an prog close, except for adb.exe (which I deal with below).
- Re-ran, exe, chose the detected n87 .zip.
- Displayed correct serial.
- Displayed correct generated 17-digit IMEI.
- Dialog contents "Modifying" gave error "Unable to open file", which I OKed.
- Several more dialogs flew by in rapid succession without error, ending with "Updating ROM" overlaid by "Updated ROM file has been saved as: cm_encore_full-87-IMEI.zip".
- Not all ancillary files were cleaned up. Two files remained: 1) IMEI.fix, a plain txt file containing the correct code to insert the generated IMEI and 2)adb.exe which could not be removed because it was still running the devices server. Running "adb kill-server" in the java\jre6\bin directory allowed me to remove adb.exe.
- A check of the modified smali showed only one instance of "getDeviceId" indicating that the smali had not been modified to add the code to spoof the IMEI.
I would also not have been able to eject my NC, had I tried, until I killed the adb server. Looks like one more line of code to add before cleanup.
BUG REPORTING:
This program was initially ineteded to generate a unique IMEI based on your device S/N and update Dev's install zip files... it has become so much more, and as such there are many functions involved in this process.
Due to the complexity the program has taken on... far beyond what I initially intended... to report bugs please try to use the following as a template:
Function attempting: i.e. Updating ROM... In Place Upgrade... Update framework saved on computer... etc.
Error Messages: any error message you receive... or the last message you saw prior to the issue.
End result: i.e. TelephonyManager updated, ROM not... TelephonyManager updated framework.jar not... etc....
Environment: ROM in same folder as !IMEIme.exe... ROM on same drive as IMEIme.exe... ROM on different drive... etc. (same for framework if updating framework instead)
!IMEIme.ini settings: you can put your entire ini file if you'd like.
If you could take notes of EXACTLY what buttons you click on which prompt it would be EXTREMELY helpful...
As I said, this program has taken on functions I initially had not imagined including... the more features added, the more complex testing and tracking bugs becomes... I don't want to include a bunch of messages just for the sake of letting you know where in the code you are... would not be beneficial to you... more buttons to click for no reason, etc.
The more detailed you can be, the quicker I can see what is happening... otherwise I have to try to duplicate what I think you are doing when you get the error.
Everyone should click "Thanks" on bug report posts... they have been instrumental in getting the program where it is so far.
RESERVED...
Adverse effects after running
First off, thanks for a wonderful application! Your app did in fact correctly give my Kindle a IDEI number, but it seems to have adverse effects.
Function attempting: Tried both in place Rom and update device and now attempting to use app with sound
Error Messages: Unfortunately DSP Manager has stopped (repeatably on any app)
End result: No sound and music apps crash. Some apps work but many do not. (I can provide logcat if needed)
Environment: Kindle Fire running cm9 using Hashcodes 3.0 Kernal latest (11) update.
!IMEIme.ini settings:
Use_In_Place = 0
Use_Previous_Patch = 0
Use_Serial_Number = 0
Use_MAC_Address = 0
Use_Manual_Input = 1
Encrypt_IMEI = 0
Use_IMEI(15) = 0
Use_ADB = 1
Use_ADB(usb) = 1
Use_ADB(WiFi) = 0
Clean_Up = 1
Include_Patch = 1
Device_Manufacturer = TI
Manufacturer_Device = Blaze
Device_Model = Full Android on Blaze or SDP
Build_Fingerprint = google/passion/passion:2.3.6/GRK39F/189904:user/release-keys
LCD_Density =
WiFi_IP_Address =
IMEI = 00127948612384612
Although I have tried multiple settings and configurations. I am sort of a noob so sorry if this is a silly problem.
Having looked into this... I can tell you there's nothing that the IMEI Generator does that would cause the issues you are seeing. I would recommend flashing a non-IMEI'd ROM for testing... then either do in place IMEI generation or running the IMEI Generator against the same ROM you flash.
For what you are doing... there are 2 files that are being modified, and neither should cause FC issues...
/sysem/build.prop for the manufacture, device, and build fingerprint
/system/framework/framework.jar is being extracted and edited to patch the IMEI in the GetDeviceID() function in android/telephony/TelephonyManager.smali and recompiled.
Clearing cache and dalvik cache may be something to try.
Thanks! Clearing both caches AFTER the install made it work great. I had been clearing all of the memory beforehand but it did not work. My apps now work great!
Motorola Razr GSM (SPDREM_U_01.6.7.2-180_SPU-19-TA-11.6_SIGNEuropeAustraliaEMEA_USASPDRICSRTGB_HWp2b_Service1FF) ICS.
I deodexed framework.jar because application seems to not work on odex files (as stock is), anyway new deodexed framework have not /com/android/internal/telephony/gsm/GSMPhone.smali file?! (or dir!!) infact !IMEIme 2.2.0.2 tell me about this issue (no GSMPhone.smali found). framework patched do not present diffecence between original one. exactly the same. no /android/telephony/TelephonyManager.smali mod applied.
I tryied to patch framework by "update device" + adb usb, with no device connected i choosed my framework.jar in my pc.
[Settings]
Use_In_Place = 1
Use_Previous_Patch = 0
Use_Serial_Number = 1
Use_MAC_Address = 0
Use_Manual_Input = 1
Encrypt_IMEI = 0
New_Type = 1
Use_IMEI(15) = 0
Use_ADB = 1
Use_ADB(usb) = 1
Use_ADB(WiFi) = 0
Clean_Up = 1
Include_Patch = 0
Device_Manufacturer =
Manufacturer_Device =
Device_Model =
Build_Fingerprint =
LCD_Density =
WiFi_IP_Address =
IMEI = 02546451548481584
stock framework.odex, jar and my deodexed framework attached.
Yes... due to another user trying to use the generator on a device with a framework.odex file instead of framework.jar I am looking into the most effective method of handling that situation. As of now... the generator will not work for you to patch imei functionality into the framework on these devices.
i deodexed also framework.jar but no way to patch it, GSMPhone.smali is missing totally even in backsmalied odex too!!!!
I decided to apply the patch manually, but without this file and TelephonyManager.smali not regoular i was thinking about hard mod by motorola?! do you know something about?
Pls man, give me an hand, show me the way, backsmali it you too http://forum.xda-developers.com/attachment.php?attachmentid=1634550&d=1357865096
I'm looking into the method to implement the imei into this.
do you mean into TelephonyManager.smali? I'm looking on it too. Seems so strange this framework...
Actually... looking through to find the best call to implement the patch into... TelephonyManager was the original method... but there may be better places to patch it.
Code:
invoke-direct {p0}, Landroid/telephony/TelephonyManager;->getSubscriberInfo()Lcom/android/internal/telephony/IPhoneSubInfo;
move-result-object v2
invoke-interface {v2}, Lcom/android/internal/telephony/IPhoneSubInfo;->getDeviceId()Ljava/lang/String;
All does make sense now:
http://grepcode.com/file/repository...nternal/telephony/IPhoneSubInfo.java?av=f#174
BUT, where is com.android.internal.telephony.iphonesubinfo!?!?! seems not present... all "internal" dir is missing here, backsmali fault or my fault?!
hiiii
hi,
any news of this? =)
This is the best software for this!
I'm working on the best solution... I understand the desire for this... but I want to ensure the method I choose is the best overall... and to ensure I can properly detect which method to implement during the operation.
If you could zip your entire /system/framework folder and add your /system/build.prop file it would help me test some things I've been putting together for odexed systems.
attaching files
DizzyDen said:
If you could zip your entire /system/framework folder and add your /system/build.prop file it would help me test some things I've been putting together for odexed systems.
Click to expand...
Click to collapse
Hi, Im attaching my files.
You can download here: w w w . 4 s h a r e d . c o m / z i p / j Q n n 9 8 _ B / s y s t e m . h t m l
Thanks for the help
Error ...
Hi Dizzy
I tried to use your update, but have a error ... My device is Motorola Razr XT910 with 4.0.4
after I choose the "framework.jar" he return this error:
Line 3710 (File: ".....\IMEI\!IMEIme.exe");
Error: Variable used without being declared.
After this the program close without any click to exit ..
Im, attaching a print screen
Tnx a lot man
waldirsp11 said:
Hi Dizzy
I tried to use your update, but have a error ... My device is Motorola Razr XT910 with 4.0.4
after I choose the "framework.jar" he return this error:
Line 3710 (File: ".....\IMEI\!IMEIme.exe");
Error: Variable used without being declared.
After this the program close without any click to exit ..
Im, attaching a print screen
Tnx a lot man
Click to expand...
Click to collapse
fixed... I guess nobody has been using the "Use Previous Fix" option for a while. New version uploaded... thank you for the bug report. The screen shots really helped track it down.
another error...
Hi DizzyDen,
I want to add an IMEI to my "SUPERPAD 6", but after the window: "IMEI is..." is displayed, then popup an autoit error window:
Line 3710 (File "..."): Error: Variable used without being declared.
Can you help?
Ponozka said:
Hi DizzyDen,
I want to add an IMEI to my "SUPERPAD 6", but after the window: "IMEI is..." is displayed, then popup an autoit error window:
Line 3710 (File "..."): Error: Variable used without being declared.
Can you help?
Click to expand...
Click to collapse
Before I start looking into this... note that the IMEI generator does not support de-odexing odexed systems yet... I would suggest using it on the ROM then flashing it to the device and let the device odex it again.
After some google action, I'm posting my problem here:
Scenary:
Gear: Motorola Atrix 4G AT&T - stock ROM (4.5.91, Android 2.3.4, WebTop version WT-1.2.0-110)
1. run webtop2sd (1.1.2) - OK
2. running web scripts - OK
Then when trying to install for example openoffice.org or trying to do:
# sudo dpkg-reconfigure tzdata
(setting to Europe/Ljubljana - or any other location for that matters)
Current default timezone: 'Europe/Ljubljana/
date: invalid date 'Wed Oct 5 07:06:25 UTC 2011'
This is the reason why packages that update or configure tzdata (tzdata-java) fail with apt-get or synaptic.
What I tried:
probably all locations with reconfiguring tzdata.. fail
manualy edited timezone.. fail
removing&reinstaling tzdata.. epic fail
Anybody else has this issue... solved ?
Same here! Any help would be greatly appreciated.
Not the right answer, but this works...
I was having the same problem, and after a few hours of struggling, here's what I eventually did.
Edit the file /var/lib/dpkg/info/tzdata.postinst and on the first blank line (3 rows down) just put exit 0 which makes the script stop and return a success. This isn't a good solution, but it does work.
Now i can go on my merry way installing things to my hearts content, but I'd love to hear if someone has a proper solution...
conundri said:
I was having the same problem, and after a few hours of struggling, here's what I eventually did.
Edit the file /var/lib/dpkg/info/tzdata.postinst and on the first blank line (3 rows down) just put exit 0 which makes the script stop and return a success. This isn't a good solution, but it does work.
Now i can go on my merry way installing things to my hearts content, but I'd love to hear if someone has a proper solution...
Click to expand...
Click to collapse
thanks a millon man,that totally fixed my problem I was having with my webtop
I took another look at this and has anyone tried adding exit 0 to just after the second to last fi close of the if then part at the bottom, I use dthe workaround posted above and went back looked over it more after having installed a few programs and added exit 0 to line 46 and it seems to be working fine. Can some one confirm this for me if they are looking at it for the first time on their version of webtop.
Hi there, I have a new install webtop2sd, and the script still failed after adding exit 0 at line 46. I have put exit 0 at line 3 afterwards to get past the problem.
I figured out the cause of the 'invalid date' problem. Actually the bug is on the end of the file in the following lines:
Code:
UTdate=$(LC_ALL=C TZ=UTC0 date -d "$TZBase")
TZdate=$(unset TZ ; LANG=C date -d "$TZBase")
The problem is that webtop uses Busybox instead of the 'original' tools. Busybox has an incomplete implementation of 'date -d'. Replacing it with an alternative like GNU Tools is the best solution for this problem. But this could be complicated and I have not much time. Adapting this script to Busybox is easier and still better than the 'exit' workaround.
All you have to do is replacing the line
Code:
TZBase=$(LC_ALL=C TZ=UTC0 date)
with
Code:
TZBase=$(LC_ALL=C TZ=UTC0 date +%m%d%H%M%Y.%S)
STD DISCLAIMER: I am not responsible for you screwing up your phone. Make BACKUPS!
I have the ever-present problem with the media files on my phone showing up as duplicates. I see from around the forums that several other users experience this regularly on CM9/CM10/AOKP based roms. I'm not sure why this is happening, but it seems to be a side-effect of the mediascanner re-indexing media it shouldn't. In this guide I show you what is going on with your data and how to remove the duplicates.
REQUIREMENTS
Your phone must be rooted to access the sqlite3 database.
You must have debugging turned on your phone
You must have access to adb and ideally have used it in the past. This thread is not about adb/driver setup!
PROCEDURE
Connect your phone via USB and make sure your adb server is started.
Code:
[[email protected] ~]$ adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Run 'adb shell' and become superuser (run 'su')
Code:
[[email protected] ~]$ adb shell
[email protected]:/ $
255|[email protected]:/ $ su
su
[email protected]:/ #
cd to /data/data/com.android.providers.media/databases/
Code:
[email protected]:/ # cd /data/data/com.android.providers.media/databases/
cd /data/data/com.android.providers.media/databases/
[email protected]:/data/data/com.android.providers.media/databases # ls
ls
external.db
external.db-shm
external.db-wal
internal.db
internal.db-shm
internal.db-wal
Attach to the external.db database with sqlite3
Code:
[email protected]:/data/data/com.android.providers.media/databases # sqlite3 external.db
external.db <
SQLite version 3.7.4
Enter ".help" for instructions
Enter SQL statements terminated with a ";"
sqlite>
view the avaible tables (.tables). Now almost every table here, except for the 'files' table is a view based on the files table. What happens is that some data is in 'files' is blanked out and the views create duplicates of the data with seemingly good filenames. However since the primary piece of data in 'files' is missing, all the media players relying on this database freak out.
Code:
sqlite> .tables
.tables
album_art audio files
album_info audio_genres images
albums audio_genres_map search
android_metadata audio_genres_map_noid searchhelpertitle
artist_info audio_meta thumbnails
artists audio_playlists video
artists_albums_map audio_playlists_map videothumbnails
sqlite>
look at the files table sql schema and find an example (.schema files). With the duplicate problem bad data is created with the '_data' field blanked out, but a valid media_type=2, since views rely on the media_type=2 but merges other fields with the file name, etc. you get a media entry that looks good but no entry to pull off the file system. See the _data section of the single entry I queried below to see what a good record looks like. A bad record will have a different '_id' and blank '_data'
Code:
sqlite> .schema files
.schema files
CREATE TABLE files (_id INTEGER PRIMARY KEY AUTOINCREMENT,_data TEXT,_size INTEGER,format INTEGER,parent INTEGER,date_added INTEGER,date_modified INTEGER,mime_type TEXT,title TEXT,description TEXT,_display_name TEXT,picasa_id TEXT,orientation INTEGER,latitude DOUBLE,longitude DOUBLE,datetaken INTEGER,mini_thumb_magic INTEGER,bucket_id TEXT,bucket_display_name TEXT,isprivate INTEGER,title_key TEXT,artist_id INTEGER,album_id INTEGER,composer TEXT,track INTEGER,year INTEGER CHECK(year!=0),is_ringtone INTEGER,is_music INTEGER,is_alarm INTEGER,is_notification INTEGER,is_podcast INTEGER,album_artist TEXT,duration INTEGER,bookmark INTEGER,artist TEXT,album TEXT,resolution TEXT,tags TEXT,category TEXT,language TEXT,mini_thumb_data TEXT,name TEXT,media_type INTEGER,old_id INTEGER, storage_id INTEGER, is_drm INTEGER, width INTEGER, height INTEGER);
CREATE INDEX album_id_idx ON files(album_id);
CREATE INDEX artist_id_idx ON files(artist_id);
CREATE INDEX bucket_index on files(bucket_id, media_type, datetaken, _id);
CREATE INDEX bucket_name on files(bucket_id, media_type, bucket_display_name);
CREATE INDEX format_index ON files(format);
CREATE INDEX media_type_index ON files(media_type);
CREATE INDEX parent_index ON files(parent);
CREATE INDEX path_index ON files(_data);
CREATE INDEX sort_index ON files(datetaken ASC, _id ASC);
CREATE INDEX title_idx ON files(title);
CREATE INDEX titlekey_index ON files(title_key);
CREATE TRIGGER audio_meta_cleanup DELETE ON files WHEN old.media_type = 2 BEGIN DELETE FROM audio_genres_map WHERE audio_id = old._id;DELETE FROM audio_playlists_map WHERE audio_id = old._id;END;
CREATE TRIGGER audio_playlists_cleanup DELETE ON files WHEN old.media_type = 4 BEGIN DELETE FROM audio_playlists_map WHERE playlist_id = old._id;SELECT _DELETE_FILE(old._data);END;
CREATE TRIGGER files_cleanup DELETE ON files BEGIN SELECT _OBJECT_REMOVED(old._id);END;
CREATE TRIGGER images_cleanup DELETE ON files WHEN old.media_type = 1 BEGIN DELETE FROM thumbnails WHERE image_id = old._id;SELECT _DELETE_FILE(old._data);END;
CREATE TRIGGER video_cleanup DELETE ON files WHEN old.media_type = 3 BEGIN SELECT _DELETE_FILE(old._data);END;
sqlite>
sqlite> select * from files where _data like '%Unhuman%';
select * from files where _data like '%Unhuman%';
16566|/mnt/emmc/mp3/Architect - 2010 - Consume Adapt Create/Architect - 04 - Unhuman.ogg|8176842|47362|16559|1345650424|1337460350|application/ogg|Unhuman||Architect - 04 - Unhuman.ogg|||||||-1041554543|Architect - 2010 - Consume Adapt Create|| O A 5 O ? ' A |5|7||4||0|1|0|0|0||338973||||||||||2||131073|0||
query the duplicates in the files tables. Here I look at just one example... This is from a later date than the earlier section. You can see how the one media file id = 16566 has been re-indexed again. 16566 and 19522 have been blanked and new record 22822 has been indexed with the complete record.
Code:
sqlite> select _id,_data,_display_name from files WHERE _data = '' AND media_type = 2;
select _id,_data,_display_name from files WHERE _data = '' AND media_type = 2;
19518||Architect - 13 - Wachsmuth.ogg
19519||Architect - 01 - The ***** is Back.ogg
19520||Architect - 02 - The Shadow of Eve.ogg
19521||Architect - 03 - Fast Lane (Freeze Frame).ogg
19522||Architect - 04 - Unhuman.ogg
19523||Architect - 05 - For You.ogg
19524||Architect - 06 - So I Went Out.ogg
19525||Architect - 08 - Attack Ships on Fire.ogg
19526||Architect - 09 - Pure.ogg
19527||Architect - 10 - I Lost my 808 on a Rainy Day.ogg
19528||Architect - 11 - Awake (Album Version).ogg
19529||Architect - 12 - The Beauty and the Beat (Rokka).ogg
<<more bad entries>>
sqlite> select * from files where _display_name like '%Unhuman%';
select * from files where _display_name like '%Unhuman%';
16566||8176842|47362|16559|1345650424|1337460350|application/ogg|Unhuman||Architect - 04 - Unhuman.ogg|||||||-1041554543|Architect - 2010 - Consume Adapt Create|| O A 5 O ? 'A |5|7||4||0|1|0|0|0||338973||||||||||2||131073|0||
19522||8176842|47362|19515|1345728924|1337460350|application/ogg|Unhuman||Architect - 04 - Unhuman.ogg|||||||-1041554543|Architect - 2010 - Consume Adapt Create|| O A 5 O ? 'A |5|7||4||0|1|0|0|0||338973||||||||||2||131073|0||
22822|/mnt/emmc/mp3/Architect - 2010 - Consume Adapt Create/Architect - 04 - Unhuman.ogg|8176842|47362|22815|1346073675|1337460350|application/ogg|Unhuman||Architect - 04 - Unhuman.ogg|||||||-1041554543|Architect - 2010 - Consume Adapt Create|| O A 5 O ? ' A |5|7||4||0|1|0|0|0||338973||||||||||2||131073|0||
delete all the duplicates. Note we won't be able to delete until we temporarily remove any triggers referring to api functions. If you look at '.schema' again you'll note a trigger refer to _OBJECT_REMOVED, we'll need to remove them. So STEP1. List schema -- cut and paste this to notepad or something. STEP2. DROP TRIGGER on anything referencing _OBJECT_REMOVED. STEP 3. delete our duplicates. STEP 4. re-create all triggers.
Code:
sqlite> drop TRIGGER files_cleanup;
drop TRIGGER files_cleanup;
sqlite> DELETE FROM files WHERE _data = '' and media_type = 2;
DELETE FROM files WHERE _data = '' and media_type = 2;
sqlite> CREATE TRIGGER files_cleanup DELETE ON files BEGIN SELECT _OBJECT_REMOVED(old._id);END;
(optional) Add a trigger to nuke duplicates. So maybe I'd like sqlite3 to remove dupes for me anytime it re-indexes, say for a deletion? Some other events might be too expensive to have this triggering all the time, but I've tested it with a file delete and it works.
Code:
CREATE TRIGGER duplicates_cleanup DELETE ON files WHEN old.media_type = 2 BEGIN DELETE FROM files WHERE _data = '' and media_type = 2;END;
That's IT.
Code:
sqlite> .quit
.quit
Takes about 2-5 minutes to clean up manually, vs waiting 14-30 minutes to re-index a huge collection. This could also be automated if you were so inclined with a better trigger or an app.
UPDATE: 10/26/2012
One clarification: media_type = 2 is audio files -- mp3, ogg, wav and the like. If you have issues with other media you can simple use that media type, or leave the qualifier off for all media types.
I was 'trying out' this trigger, but now have gone for months without any duplicates. I think it works. Basically, you can skip doing any other sql work in the above guide -- just creating this trigger and adding a media audio file. Adding a media file should launch this trigger and clear out any duplicates (may have to reboot once).
Code:
sqlite> create trigger duplicates_cleanup AFTER UPDATE OF _data ON files BEGIN DELETE FROM files WHERE _data = '' and media_type = 2;END;
create trigger duplicates_cleanup AFTER UPDATE OF _data ON files BEGIN DELETE FROM files WHERE _data = '' and media_type = 2;END;
Interesting.
Where do you see duplicates show up? I'm not running aosp.
The reason this caught my eye is because I've always had the issue of duplicate entries in ringtone and notification sounds lists, while there are not duplicate files in /system/media/audio/*. I don't think this is the same issue you are adressing, is it?
creepyncrawly said:
Interesting.
Where do you see duplicates show up? I'm not running aosp.
The reason this caught my eye is because I've always had the issue of duplicate entries in ringtone and notification sounds lists, while there are not duplicate files in /system/media/audio/*. I don't think this is the same issue you are adressing, is it?
Click to expand...
Click to collapse
It's a similar issue. Note the following items in the schema:
is_ringtone INTEGER,is_music INTEGER,is_alarm INTEGER,is_notification INTEGER,is_podcast INTEGER
The same thing could very well be happening where you have two records with mostly the same records but a blank '_data'.
othermark said:
It's a similar issue. Note the following items in the schema:
is_ringtone INTEGER,is_music INTEGER,is_alarm INTEGER,is_notification INTEGER,is_podcast INTEGER
The same thing could very well be happening where you have two records with mostly the same records but a blank '_data'.
Click to expand...
Click to collapse
Meaning it would be the same database?
creepyncrawly said:
Meaning it would be the same database?
Click to expand...
Click to collapse
If the duplicates are all on external media, yes, however, if it's on the internal media then it will be in the internal.db instead of the external.db as posted in my guide.
So if you're seeing duplicates with 'Whistle' showing up twice in notifications, there's probably a problem with internal.db.
Had a little time to play around with this today. First, I was surprised that I didn't have sqlite3 on my phone. I had to install it, using a market app called SQLite Installer for Root by ptSoft. (SHOstock2 v4.1.3)
I ran the query "select _id,_data from files WHERE _data = '' and media_type = 2;" on both the external.db and internal.db but in both cases no entries were found. So no joy finding duplicate entries in notifications and ringtones with this method.
creepyncrawly said:
Had a little time to play around with this today. First, I was surprised that I didn't have sqlite3 on my phone. I had to install it, using a market app called SQLite Installer for Root by ptSoft. (SHOstock2 v4.1.3)
I ran the query "select _id,_data from files WHERE _data = '' and media_type = 2;" on both the external.db and internal.db but in both cases no entries were found. So no joy finding duplicate entries in notifications and ringtones with this method.
Click to expand...
Click to collapse
The schema is maybe different in samsung based roms? How I originally found this was to pick a duplicate and look at the various tables and work backwards through the views and matching up fields.
You can always start with a select * from files and see if you can find where it lists the same name or file name twice. This should be easy to do on the internal.db with it's limited number of entries.
for the past year that i've had my sgs2, i've constantly had this issue with my phone and it's been a constant annoyance. i honestly want to say thank you for this but the problem is i got to step 1 and i went full retard. for some reason, i already have adb on my comp and i guess i used it for something at some point, possibly when i was rooting my phone a while back but i have no clue how to use it that well. i would love to try and get this to work on my phone but can you really dumb it down for those not really familiar with how to do all this? if not, i thank you for putting this up in the first place, i'll try to give it another go.
I tried the fix and it seemed to work until I pulled up ringtones a second time and there were the doubles and even triples. Frustrated that it didn't take I delved deeper into my files and discovered a couple unzipped (but not installed) ROMs that I had extracted just to look at. Deleted them and problem solved. Did I mention I'm a noob, lol?
bandit1210 said:
I tried the fix and it seemed to work until I pulled up ringtones a second time and there were the doubles and even triples. Frustrated that it didn't take I delved deeper into my files and discovered a couple unzipped (but not installed) ROMs that I had extracted just to look at. Deleted them and problem solved. Did I mention I'm a noob, lol?
Click to expand...
Click to collapse
Cool
ok, is there anyway to undo all of this because i have a feeling this might have caused my phone to delete all my pictures i've taken and when i try to flash a new rom, it sends me into a boot loop and i can't reflash anything.
ender127 said:
ok, is there anyway to undo all of this because i have a feeling this might have caused my phone to delete all my pictures i've taken and when i try to flash a new rom, it sends me into a boot loop and i can't reflash anything.
Click to expand...
Click to collapse
Flash to stock?
ender127 said:
ok, is there anyway to undo all of this because i have a feeling this might have caused my phone to delete all my pictures i've taken and when i try to flash a new rom, it sends me into a boot loop and i can't reflash anything.
Click to expand...
Click to collapse
You can "Clear Data" on the "Media Storage" app, this has the same effect as removing the db files.
However a boot loop is already beyond all this... You need to get into recovery to fix that.
well, i figured it was one of two things. after i did this on saturday, i tried to flash new firmwarm (10.31 task) but i got stuck in a boot loop. i can flash to another rom (super nexus) without problems and i can get to a really old nandroid backup. but basically you're telling me if i do a clear data on media storage, it'll wipe anything i did on adb? i really appreciate the responses by the way, i literally just flew out of the country for vacation and luckily i brought a laptop to fix this, but i can't function without my phone running.
ender127 said:
basically you're telling me if i do a clear data on media storage, it'll wipe anything i did on adb.
Click to expand...
Click to collapse
I believe so, yes. At least that is my experience.
How do delete duplicates if the _data is NOT empty
If you have root and can put sqlite3 on your device, this works without scanning and all that silliness:
http://forum.xda-developers.com/showthread.php?t=1847586
---------- Post added at 02:09 PM ---------- Previous post was at 01:49 PM ----------
Sweet, thank you so much for this. I found that on my Galaxy S3, Zedge creates a mess of things. I had up to 5 of each notification and ringtone, all with the same valid info aside from _id. Here's what I did to pick the first entry and clean things up:
sqlite3 external.db
FROM files WHERE _id not in (select MIN(_id) FROM files GROUP BY _data);
You can choose to keep the LAST entry for each by changing MIN to MAX, which might be a better idea if you trust recent modifications over earlier ones. If they all have valid _data it probably does not matter.
This must be the most asked question I have googled in a long time
There are so many results but nothing that resolves my dilemma
Without any tweaks I can access channel 13 via the router with my Xperia Ray running the latest nightly CM10
So whats the issue you may be asking, well this is the strange part
If I turn off the SSID of the router so it no longer broadcasts its name then the issue starts
My mobile will not connect to channel 13 thereafter it just disconnects
HOWEVER I have no issues with channels 1 - 12 with the SSID turned off
and certainly had no issues with Miui v4 with the same kernel installed
I have seen this happen with a few tablets but once the tablet has seen the network on channel 13 it was fine and then I could turn off the SSID
SO why do I need to turn off the SSID - because I prefer it was off in an area high with WiFi activity that's all
and I need to use channel 13 because of the high volume of wifi traffic in the area constantly changing there channels
Wifi 13 seems more stable and quicker anyhow I am in the UK and the routers in our street are all set to auto channel???????!!! why I dont know, but none use channel 13
So is there a solution to this very bizarre issue or am I going to have to leave my SSID on
SOLUTION Found thanks sirkay
Thanks to sirkay I can now access any hidden non broadcasting SSID wifi network
http://forum.xda-developers.com/showpost.php?p=23564367&postcount=5
A simple script that is supposed to enable extra channels actually fixed my issue with a hidden SSID
-----------------------------------------------------
Channel 13 issues
[ SOLUTION: To Enabled Wifi Channels 12-14 ]
1. using Root Explorer, goto /system/etc/init.d
2. open one of your init.d scripts, i suggest first in the list (Menu > Open in text editor)
3. paste line below
Code:
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "INSERT INTO secure (name, value) VALUES ('wifi_country_code', 'JP');"
4. close and save
5. reboot
note: to enabled channel 12-13 just change "JP" to "EU" or "ES"
-------------------------------------------------------------------------------------------------------------------------------------------
I created a fresh file called 10wifi
and add these lines
#!/system/bin/sh
#
# Fix wifi channels 12 - 14
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "INSERT INTO secure (name, value) VALUES ('wifi_country_code', 'EU');"
-------------------------------------------------------------------------------------------
I put the file into an install-able zip and added permissions to the update_script
set_perm(0, 0, 0777, "/system/xbin/10wifi");
NeilDownx said:
Thanks to sirkay I can now access any hidden non broadcasting SSID wifi network
http://forum.xda-developers.com/showpost.php?p=23564367&postcount=5
A simple script that is supposed to enable extra channels actually fixed my issue with a hidden SSID
-----------------------------------------------------
Channel 13 issues
[ SOLUTION: To Enabled Wifi Channels 12-14 ]
1. using Root Explorer, goto /system/etc/init.d
2. open one of your init.d scripts, i suggest first in the list (Menu > Open in text editor)
3. paste line below
Code:
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "INSERT INTO secure (name, value) VALUES ('wifi_country_code', 'JP');"
4. close and save
5. reboot
note: to enabled channel 12-13 just change "JP" to "EU" or "ES"
-------------------------------------------------------------------------------------------------------------------------------------------
I created a fresh file called 10wifi
and add these lines
#!/system/bin/sh
#
# Fix wifi channels 12 - 14
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "INSERT INTO secure (name, value) VALUES ('wifi_country_code', 'EU');"
-------------------------------------------------------------------------------------------
I put the file into an install-able zip and added permissions to the update_script
set_perm(0, 0, 0777, "/system/xbin/10wifi");
Click to expand...
Click to collapse
I copied the script and saw that actually in my settings.db the value wifi_country_code is correctly added, but my galaxy tab s with Blisspop rom still doesn't see the 13th channel...
someone can help me please?
tribio said:
I copied the script and saw that actually in my settings.db the value wifi_country_code is correctly added, but my galaxy tab s with Blisspop rom still doesn't see the 13th channel...
someone can help me please?
Click to expand...
Click to collapse
Have a look in your build.prop file and amend as below
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=13
now finally reboot and if it still fails you may need to change kernels......
I no longer have to bother with these settings as changing the kernel fixed my past issues
...Another solution
1. Turn off WiFi
2. Copy /data/misc/wifi/wpa_supplicant.conf to /sdcard
3. Rename /data/misc/wifi/wpa_supplicant.conf to /data/misc/wifi/wpa_supplicant.conf.old
4. Copy /sdcard/wpa_supplicant.conf to /data/misc/wifi
5. Edit /data/misc/wifi/wpa_supplicant.conf (using ES File Explorer) and remove the pmf=1 line
6. Save the file and make sure the permissions are appropriately set to rw-rw----, the owner is system and the group is wifi otherwise your WiFi will not turn on.
7. Reboot
8. Turn on WiFi
Found this solution on the CM12 errors list - lost of people having similar wifi issues
Tried to update build.prop and nothing change...
Opened wpa_supplicant.conf and there is not "pmf=1" written in the file..
I suppose I have to change kernels?
Thanks a lot for the help!!!
none of the above methods worked for me either
tribio said:
Tried to update build.prop and nothing change...
Opened wpa_supplicant.conf and there is not "pmf=1" written in the file..
I suppose I have to change kernels?
Thanks a lot for the help!!!
Click to expand...
Click to collapse
I seem to have the same problem. Did you resolve your issue? Thanks in advance.
nope!
working with CM12
tribio said:
nope!
Click to expand...
Click to collapse
I got fed up with this and decided to go all out and install Lollipop. I installed Installed Cyanogenmod (CM12) and then Temasek ROM port. I did this at home where the router is using a low channel number. I took the tablet to work and voila channel 13 was working. No need to mess with any wifi_country_codes. I am pretty sure it would work fine without the Temasek port. It might also have worked fine with CM10 or CM11. The disadvantage to this whole process is that I don't have the same spen functionality as stock. I'm still figuring out what apps to using for my "new" Note 10.1.