Thank you! I write my own material! I figured real life © was done to death...
Mastiff in Norway
Too bad. Well, I'll try to be patient. Not easy for me, I have to admit...
Mastiff in Norway
kk_adam_3g-ota-eng.2014-04-09.zip. Is running quiet well for me. I also really look forward to updated ROM's!
Sent from my Notion Ink ADAM using Tapatalk
Love your rom thanks Tenchi. No resets required so far with latest patch.
As with all the other kitkat roms on this site there is no adb or mass storage access from pc.
If I reboot into recovery however adb and mass storage access from pc work perfectly. (file paths require working out)
to test adb issues i've tried unmounting fuse assisted storage mounts..
unmounting fuse filesystems then restarting adbd
manualling entering commands like (with appropriate paths, via terminal with hackers keyboard "setprop...." )
Android Code Search(Android 4.4 Kitkat)Kitkat/device/asus/flo/init.flo.usb.rc
looked at this solution ... but actually running the commands manually doesn't work at this stage ..
[APP][v1.8 (+US)] SGS3 Easy UMS - Mount external microSD card as USB mass storage - Page 57 - xda-developers
but looking at the logs on my pc while adam boots...the problems would not appear to start until the gui loads? (then pc stops recognising device)
I can't see inside "init" as its compiled but init.rc looks clean...what next, xml files??
Last edited by ri9000; 05-02-2014 at 04:31 AM.
ps: my adam is overclocked to 1600mhz and seems reliable with no lockups. With pre-kitkat roms 1500mhz was the safe limit.
Was wondering if we could shut down one cpu core to improve idle battery life..or that done for deep sleep anyway?
What was in KatKiss kernel that might kill your Adam?
looking at ...(code for galaxy S4)
[APP][ROOT] SG USB Mass Storage Enabler - Page 28 - xda-developers (post 278)
echo /dev/block/vold/179:XX > /sys/devices/platform/s3c-usbgadget/gadget/lun0/file
echo /dev/block/vold/179:XX > /sys/devices/virtual/android_usb/android0/f_mass_storage/lun_ex/file
echo /dev/block/vold/179:XX > /sys/devices/virtual/android_usb/android0/f_mass_storage/lun/file
echo /dev/block/vold/179:XX > /sys/devices/virtual/android_usb/android0/f_mass_storage/lun0/file
echo /dev/block/vold/179:XX > /sys/devices/platform/msm_hsusb/gadget/lun0/file
Use as XX at first 8 and then 0
someone please correct me if i'm wrong.........but
"vold" appears to be the mounting demon, and looking at the files above, the common link between "adbd" and "mass storage".
The setup in recovery mode works perfectly. Whats the difference between the setup in "recovery" and normal boot?
An analysis of the file content shows no difference...What am i missing?? ...fuse mounts??
...or simply the order processes are performed?
Last edited by ri9000; 05-02-2014 at 07:09 AM.
I believe it already is shutting down one core in deep sleep. If I knew what was wrong I probably would have fixed before flashing the KatKiss kernel, hopefully Notion Ink will give some insight as to what was causing it not to power on.