xPhoenix777
Member
rild doesn't seem to appear in the list of files in Romer_v5 in "system/bin" - give that a copy over (if it exists in stock)... like I said, rild played with sensors somehow.
DroidForums.net | Android Forum & News
This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
[ROM Tools] Team Get~R~Done D2G Rom-er Tool - a tool Convert D2 Roms for use on D2G
- Thread starter buryboi
- Start date
No go
But wait...I didn't see the rild thing...trying again.
rild* was on my Samsung Intercept when I had a similar problem... It dealt with sensors... if you can't find it, the D2Gs might not need it.
Empty out the akmd file, but leave it be. Then reboot. See if the system partially fills it. Then log files of the softboot (if it does) might show something.
Trying now... waiting for reboot.
edit: left it blank + softboots
Last edited:
xPhoenix777
Member
From XDA Developers (full thread link):
cd /data/misc
rm -r akmd*
rm -r rild*
Then replace Launcher.Apk - from stock?
^^^^^^^^^^
That was the general "fix" for a similar issue that I referenced last summer when working on the Samsung Intercept... I worked iwth the akmd and rild files to make sure that they were the stock ones (in data/misc and in system/bin) when getting a ROM from the Samsung Moment running. I just wish I had the logs I used to find the problem.
cd /data/misc
rm -r akmd*
rm -r rild*
Then replace Launcher.Apk - from stock?
^^^^^^^^^^
That was the general "fix" for a similar issue that I referenced last summer when working on the Samsung Intercept... I worked iwth the akmd and rild files to make sure that they were the stock ones (in data/misc and in system/bin) when getting a ROM from the Samsung Moment running. I just wish I had the logs I used to find the problem.
xPhoenix777
Member
No go
But wait...I didn't see the rild thing...trying again.
rild* was on my Samsung Intercept when I had a similar problem... It dealt with sensors... if you can't find it, the D2Gs might not need it.
Empty out the akmd file, but leave it be. Then reboot. See if the system partially fills it. Then log files of the softboot (if it does) might show something.
Trying now... waiting for reboot.
edit: left it blank + softboots
One thing I didn't think about, chmod 0777 the file so the system has full write access if it doesn't already, then reboot.
Sorry to be throwing all these things at you and they seemingly don't work.
You lost me on that one...
Its fine, would rather be helping to solve this than sleeping... i can sleep in class tomorrow, do anyways (teacher doesnt care.... have a high A in that class).
xPhoenix777
Member
open up adb terminal or terminal emulator on the phone:
type:
cd /data/misc
chmod amkd_set.txt 777
Also try this too:
cd /system/bin
chmod akmd2 755
That should get things working again... Not sure, but is there an akmd (not akmd2) in system/bin on stock (anyone, and you don't have to go back and check13th).
type:
cd /data/misc
chmod amkd_set.txt 777
Also try this too:
cd /system/bin
chmod akmd2 755
That should get things working again... Not sure, but is there an akmd (not akmd2) in system/bin on stock (anyone, and you don't have to go back and check13th).
xPhoenix777
Member
Good catch Nova... I will give this a shot tomorrow unless someone beats me to it.
I will also look at file permissions on stock... all the files seem to be read only in the system/bin (which is smart) but I think that the akmd2 might need 755 perms on it.
Its 1:30 and I work at 7am :S
Night all.
I will also look at file permissions on stock... all the files seem to be read only in the system/bin (which is smart) but I think that the akmd2 might need 755 perms on it.
Its 1:30 and I work at 7am :S
Night all.
Still blank...
did the rm -r akmd after and it doesnt get replaced on reboot.
did the rm -r akmd after and it doesnt get replaced on reboot.
xPhoenix777
Member
Hmm, well logs all claim there is a missing sensor driver... My past experience and research say its akmd stuff... More work tomorrow. Thanks again for testing it out with me.
I am bad at going to bed...
I am bad at going to bed...
So is what nova is saying is flash Romer over stock rom and check the log for issues?
Just so we're all on the same page, the Romer files are stock files.
The original romer only had stock D2G /system/lib files (all except libandroid_runtime.so and libandroid_servers.so) and /system/usr files (for keyboard).
Version 3 included those plus /system/etc, /system/fonts, /system/bin, /system/tts, /system/media. (I believe that the /bin files fixed global data and there is a btinit file that I think fixed bluetooth).
Version 4 was the same as 3 but without loadpreinstalls.sh (messed with the custom liberty version that installs their toolbox among other things).
Version 5 only added the script to disable sensors automatically.
Version 6 (unreleased) only includes files from those folders with different md5sums or files that are unique to D2G (non existent on D2).
I've got a few google docs that compare md5sums of D2 Roms to D2G Roms if that would be helpful. (this let me isolate which .so files to mess with rather than going one by one, I only change ones that were different).
Now all that being said, the Romer sets permissions based on Fissions and Liberty's updater-scripts...maybe thats partly to blame. (Fission is only a partial Rom, but it does set system permissions, and if liberty is missing a particular D2G file that fission doesn't change either, it might not set the right permissions for that one either...)
Just so we're all on the same page, the Romer files are stock files.
The original romer only had stock D2G /system/lib files (all except libandroid_runtime.so and libandroid_servers.so) and /system/usr files (for keyboard).
Version 3 included those plus /system/etc, /system/fonts, /system/bin, /system/tts, /system/media. (I believe that the /bin files fixed global data and there is a btinit file that I think fixed bluetooth).
Version 4 was the same as 3 but without loadpreinstalls.sh (messed with the custom liberty version that installs their toolbox among other things).
Version 5 only added the script to disable sensors automatically.
Version 6 (unreleased) only includes files from those folders with different md5sums or files that are unique to D2G (non existent on D2).
I've got a few google docs that compare md5sums of D2 Roms to D2G Roms if that would be helpful. (this let me isolate which .so files to mess with rather than going one by one, I only change ones that were different).
Now all that being said, the Romer sets permissions based on Fissions and Liberty's updater-scripts...maybe thats partly to blame. (Fission is only a partial Rom, but it does set system permissions, and if liberty is missing a particular D2G file that fission doesn't change either, it might not set the right permissions for that one either...)
Last edited:
Im not sure the reasoning behind it but ill try it.... waiting on it to restore back to stock... even if ill be missing liberty the entire time im on stock.
Edit: tried it, everything works right still....
Edit: tried it, everything works right still....
Last edited:
xPhoenix777
Member
I will give those logs a look, thanks.
I assume it could be a permission issue, since you are copying over the D2G files. Astro File Manager showed all my /system/bin to be -r- for permissions, which is minimal. They don't appear to have taken on the 755 assigned to them in the installer, I could be wrong (especially if Astro FM is not reading permissions properly).
The big thing is, we need to figure out this (which I still think is linked to AMKD):
Right after JIT loaded in on the ROM (I think this one was from a Liberty install) it tried to load the sensor driver (AMKD_set.txt - but I will verify with more testing today).
A guy at work this morning said he had a similar problem on another phone he was doing ROM work on. He replaced the Launcher.APK with the stock and the AMKD* (his was AMKD, ours would be AMKD2) with stock in /system/bin, even though the md5 sums were the same. Then he applied 755 to that file, and 777 on the /data/misc folder.
Maybe that helps at all? I have meetings this morning, so forum work an a little log work is all I can do until about 12PM EST.
I assume it could be a permission issue, since you are copying over the D2G files. Astro File Manager showed all my /system/bin to be -r- for permissions, which is minimal. They don't appear to have taken on the 755 assigned to them in the installer, I could be wrong (especially if Astro FM is not reading permissions properly).
The big thing is, we need to figure out this (which I still think is linked to AMKD):
Code:
02-16 08:42:39.896 D/dalvikvm( 5879): JIT started for system_server
02-16 08:42:39.943 E/Sensors ( 5879): Couldn't find or open 'sensors' driver (No such file or directory)
02-16 08:42:39.951 I/EventHub( 5879): ignoring event id /dev/input/event7 driver sensors
02-16 08:42:39.959 D/Sensors ( 5879): using sensors (name=sensors)
02-16 08:42:39.959 D/SensorService( 5879): android_open numFds = 1
02-16 08:42:39.959 D/SensorService( 5879): android_open fd = 0x48927b64 pfd = 0x48927b60
02-16 08:42:39.966 W/dalvikvm( 5879): VFY: unable to find class referenced in signature (Lcom/android/server/ThrottleService;)
02-16 08:42:39.966 I/dalvikvm( 5879): Could not find method com.android.server.ThrottleService.systemReady, referenced from method com.android.server.ServerThread$1.run
02-16 08:42:39.966 W/dalvikvm( 5879): VFY: unable to resolve virtual method 3949: Lcom/android/server/ThrottleService;.systemReady ()V
02-16 08:42:39.966 D/dalvikvm( 5879): VFY: replacing opcode 0x6e at 0x0067
02-16 08:42:39.966 D/Sensors ( 5879): Poll thread started
02-16 08:42:39.966 D/Sensors ( 5879): using accelerometer (name=accelerometer)
02-16 08:42:39.966 D/Sensors ( 5879): using compass (name=compass)
02-16 08:42:39.966 D/Sensors ( 5879): using proximity (name=proximity)
02-16 08:42:39.966 D/Sensors ( 5879): using als (name=als)Right after JIT loaded in on the ROM (I think this one was from a Liberty install) it tried to load the sensor driver (AMKD_set.txt - but I will verify with more testing today).
A guy at work this morning said he had a similar problem on another phone he was doing ROM work on. He replaced the Launcher.APK with the stock and the AMKD* (his was AMKD, ours would be AMKD2) with stock in /system/bin, even though the md5 sums were the same. Then he applied 755 to that file, and 777 on the /data/misc folder.
Maybe that helps at all? I have meetings this morning, so forum work an a little log work is all I can do until about 12PM EST.
I cant really do anything until after school either so ill be free to test whatever after 3 central..... high school is somewhat annoying lol
Sent from my Liberated D2G
Sent from my Liberated D2G
ilovegetrdone
New Member
I got the sensors to work again. I don't know how long it will last but i'll tell you guys when it crashes. I flashed the sensors, installed doodle jump, played a game, then flashed a new boot logo again using the app 'boot logo changer' and its working fine. Last time I ran into problems with my charger so i'll keep you guys updated
Last edited: