Database Develop

[Script][A2SD]Darktremor 2.7.5.3 Beta 04 [Buzz] (01/29/2011)

Introducing...
Darktremor Apps2SD 2.7.5.3 Beta 04
Date of Release: January 29, 2011
Download Current Version
Instructions - Change Log - Commands - ROM List - Developer's Guide
Darktremor Apps2SD Fan Page ----
Darktremor Apps2SD Development Group
Are you installing Darktremor Apps2SD on your phone? Here are the instructions to help you: Facebook
Are you a developer wanting to include Darktremor Apps2SD in your latest ROM? Here is the Developer Guide: Facebook
Click to expand...
Click to collapse
Update on Beta 4
It seems I'm getting mixed results with these betas. I'm not sure why this is occurring, some people have been able to get this working right while others have had a hard time with it.
Currently, I'm rebuilding the entire program. This takes a while because I have to figure out how to pack all these options into the program but make it small enough to where it will run correctly.
I will say that some of the beta features are coming back out...one of them is the search for a partition code. I suspect that code may be leading me into issues with certain platforms, so I'm going back to the 2.7.5.2 method of mounting (mmcblk0p2 or mmcblk1p2).
Also, parts of the code will use Busybox Ash (the only code that won't will be starta2sd, which will still use Bash for the time being). The startup code will definitely use Busybox Ash.
Until then, here are the links to the the last two betas and the last official release:
Version 2.7.5.3 Beta 04 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.3-beta04-signed.zip
Version 2.7.5.3 Beta 03 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.3-beta03-signed.zip
Version 2.7.5.2-1 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.2-1-signed.zip
And, if you want past versions, you can view the repository: ftp://dtuser:[email protected] (ignore the smiley face...that's XDA doing that.)
Click to expand...
Click to collapse
Beta 04 took longer than I expected to release. I have done major changes to the code:
1. New commands: convert-ext4 - This will convert your EXT3 partition into EXT4. Just a friendly reminder on this command: Not every rom supports EXT4, so it is possible to go into a boot loop if you switch roms. Use with caution.
2. Reworked convert-ext3 (convert-ext4 gets similar code)...now a flag file is set before the reboot (no conversion is done before the reboot). At load time, the conversion is performed. This takes longer in the reboot process and you may think your phone has locked up...wait about five minutes before doing anything with the phone.
3. Repair is rebuilt...now it uses existing commands to repair the setup (reinstall, remove, cachesd, cachepart, nocache, datasd, nodata). Definitely shrinks the code.
4. Added fix_permissions program to the package. This may help with Superuser issues when using the datasd feature. It is used in reinstall, remove, datasd and nodata.
5. a2sd install is back!!! Both a2sd install and a2sd reinstall do the exact same thing.
6. Dalvik heap code has been shrunk and now creates a file called dalvikheap. Actually, the code has been doing this all along (since about 2.7.5.2, I think), but I never put the code in to use the file.
7. Low Memory Killer code has also been shrunk and uses a file caled dtset_lowmem to set the low memory killer parameter.
8. Replaced Busybox PS function with Toolbox PS. The issue with Busybox PS is that it gives a false reading when I look for android.process.acore (which is the main program when the GUI starts up). If that is present, the program thinks you are trying to run Darktremor without any command line parameters. This was because Busybox would report the process was there when, in reality, it wasn't (validated this when my phone was boot looping.) Toolbox's PS reports the correct setting. This should fix the bootlooping issues some people are experiencing.
9. New commands: usedtbusybox and usedefaultbusybox - these commands may help in diagnosing issues that is may be related to the native Busybox on your rom. a2sd usedtbusybox will use the Busybox that is packaged with Darktremor. a2sd usedefaultbusybox will turn back on the scan behavior of the program introduced in Beta 03.
10. Support for Darktremor Apps2SD version 2.7 and earlier has been discontinued. To upgrade correctly from one of those versions, use version 2.7.5.3 Beta 03b or earlier.
11. Finally fixed stalled boot issues (or at least my tests with several roms says so.)
See the change log for additional details.
You will notice that if the program runs repair and finds a problem, it will correct the issue and reboot. You will see a second reboot when the dalvik-cache clears (this is to fix timing issues with CyanogenMod...I can't control that startup as well as I can other roms). This only happens if repair is ran or you flash a new rom (as repair will realign all data). If you are upgrading from a previous version of Darktremor, you should not see the reboots.
Click to expand...
Click to collapse
This is Darktremor Apps2SD, a multipurpose program that primarily allows a user to execute applications created for the Android OS on their Secure Digital card (with the proper setup...more on that later). But, Darktremor Apps2SD is all about stability. The goal is to be able for all users of the Android OS to be able to take advantage of a method to run their applications from a secure digital card.
But just because the Darktremor Apps2SD is all about stability, doesn't mean it isn't packed with features:
- Move applications (both free and paid) to the Secure Digital card.
- Move Dalvik Cache to run either from your Secure Digital card or from your cache partition and clears the cache on demand.
- Boot Loop Protection: prevents the phone from boot looping in the event the SD card could not be mounted.
- Dalvik JIT for faster performance on Roms which support it.
- User selectable sizes for the Dalvik heap sizes, allowing a user to freely optimize their system.
- Activate a swap partition on your SD card and sets how often the swap partition is utilized.
- Automatically fixes configuration issues.
- Users can check the free space on their SD card and check the installation to make sure all is setup correctly.
- Runs ZipAlign on demand...this makes your programs load faster.
- Built in help system for easy reference of commands.
- All features can also be reversed without repartitioning your Secure Digital card.
- New logging features assists in troubleshooting issues.
- Commands to set the Low Memory Killer feature at boot time. Great for those people who are the "set it and forget it" type.
- And more...
Darktremor Apps2SD is not the same as Froyo Apps2SD. Froyo Apps2SD creates a secure folder on the FAT32 section of your SD card (this is the section that you see when you mount your phone to your computer) and stores the programs there. This is nice as you don't have to do anything special with the phone, but it isn't backwards compatible with older versions of Android (Cupcake, Donut, Eclair) and, because of the way Froyo works, older programs not designed for Froyo will automatically stay on your internal storage (unless you install a program that forces the move to your SD card).
Darktremor Apps2SD takes a different approach. Based on the original CyanogenMod works, Darktremor Apps2SD uses symbolic linking to force Android into moving your applications to the SD card. Because Android will not allow anything to be ran from the FAT32 partition on your SD card (and, in Froyo, it will only allow you to run programs from a special folder), Darktremor utilizes filesystems called EXT2, EXT3 and EXT4. Each one of these filesystems is native to Linux (the operating system running Android), which allows you to run programs from them (same as, say, a computer running Ubuntu). This method is completely compatible with all versions of Android, including Froyo. In fact, you can run both the Darktremor Apps2SD and Froyo Apps2SD at the same time.
Check out the list of Roms that either have Darktremor Apps2SD installed or are compatible with Darktremor Apps2SD. Click on the link labeled ROM List at the top of this message.

Very nice m8,
i'm using it on my CM7 Build #0, with much apps i have 156MB free..

cool man sounds orsum will have to add this to my new rom

Would you say this is better than the normal Froyo App2sd? is it any faster at loading the apps one the sd card loading from **** drive mode?

Froyo app2sd sucks, this one is heaps better as apps are stored on ext partition, so you save way more internal phone memory. And yea its fast.
Sent from my HTC Wildfire using XDA App

nice to se you here tkirton
but i would love to see you @ ZTE blade forum to
will use your app in those roms

I have now installed this, how do i know apps are being moved to the sd card?

I would love to for those roms. I'll have to look at the roms. Unfortunately, I don't have a ZTE Blade, but I don't own most of these phones that Darktremor works on (I only have a Sprint Hero and a Sprint Evo).
The more roms, the better.
danne_jo said:
nice to se you here tkirton
but i would love to see you @ ZTE blade forum to
will use your app in those roms
Click to expand...
Click to collapse

Run a2sd check. That will check the configuration and tell you if everything is setup correctly.
-Howad- said:
I have now installed this, how do i know apps are being moved to the sd card?
Click to expand...
Click to collapse

You can also just start "Titanium Backup" and check memory in the main screen

I installed Darktremor app2sd on Modaco custom rom (Froyo), and must say its excelent, I got internal memmory of 160 mb free, and now with 100 apps installed have 155 mb free. My ext3 partition is 512 mb and Dalvik cache is on ext3. With zipalign phone work well, no issues about stability, widgets work normal (its not case with Froyo a2sd).
Thanks Tkirton for this.

bump---new version available.

is there something what i have to do before installation?
i already have 2.7.5.2 .. or just install from new zip file?
anything before or after? (cahesd or smtg.)

rudyshy said:
is there something what i have to do before installation?
i already have 2.7.5.2 .. or just install from new zip file?
anything before or after? (cahesd or smtg.)
Click to expand...
Click to collapse
I want to know about that too. Can we flash the new version on top of the original one? Will it harm the installed apps?

"a2sd help" moves apps to phone???
"a2sd cachesdreset" doesn't seem to work???

how to instal it? i instaled it on 2.3 codegen from recovery chosing zip i downloaded and now everyting doesnt work in my phone. all programs are messed... i dont understand. now i need to reinstal new rom? because i lost a lot of programs and all widgets cant load.

Just flash on top of it.
rudyshy said:
is there something what i have to do before installation?
i already have 2.7.5.2 .. or just install from new zip file?
anything before or after? (cahesd or smtg.)
Click to expand...
Click to collapse

Download the 03a version...the Help issue is described on the first message.
Type a2sd reinstall to put the apps back on the phone.
As for a2sd cachesdreset, I will look into it.
UPDATE: I see the issue with a2sd cachesdreset. I'll issue an update shortly. In the meantime, use a2sd cachesd and, if you want to reset the cache, type a2sd resetcache
WackyWookie said:
"a2sd help" moves apps to phone???
"a2sd cachesdreset" doesn't seem to work???
Click to expand...
Click to collapse

Describe the steps that you went through in installing it, including any commands you ran after the install.
vilks said:
how to instal it? i instaled it on 2.3 codegen from recovery chosing zip i downloaded and now everyting doesnt work in my phone. all programs are messed... i dont understand. now i need to reinstal new rom? because i lost a lot of programs and all widgets cant load.
Click to expand...
Click to collapse

tkirton said:
Download the 03a version...the Help issue is described on the first message.
Type a2sd reinstall to put the apps back on the phone.
As for a2sd cachesdreset, I will look into it.
UPDATE: I see the issue with a2sd cachesdreset. I'll issue an update shortly. In the meantime, use a2sd cachesd and, if you want to reset the cache, type a2sd resetcache
Click to expand...
Click to collapse
Ah good I was starting to doubt my phone's installation, good to know it's a bug...
Sent from my HTC Wildfire using XDA App

Reboot when update/install apps cm7-dta2sd

I was using micromod's CM7 build, using dtapps2sd, everything worked fine until yesterday i tried to flash cm7-rc1. I noticed gmail and facebook were missing and would not install, so i reverted back to the previous nandroid. All my apps were missing, i had read that clockworkmod 3.0.0.5 has been screwing with people's phones.
So i backed up my SD card, wiped it and repartitioned it, and wiped and reflashed cm7. It installed fine, but if i try to install an app, either from market or from .apk, the phone will simply freeze then reboot.
after i downgraded my recovery, i was able to get my last nandroid to work fine, i am now back on micromods cm7 build. But i am still getting this reboot, which means i can't even update my apps.
So i am on :
Micromod v.1.4 (cm7-grh78)
dtapps2sd-2.7.5.2-1
Here is a logcat, but i have no idea whether it captured the important point, i really can't read these things.
Code:
W/DownloadManager( 4573): Aborting request for download 1600: http error 416
E/vending ( 4640): [21] DownloadManagerBroadcastReceiver.handleDownloadCompletedAction(): content://downloads/my_downloads/1600 state is INSTALLED
E/TalkProvider( 4408): replaceContactWithContactId: contactId==0!!! liam.lah(at)gmail.com, acct=1
E/TalkProvider( 4408): insert presence failed for account=1 username=liam.lah(at)gmail.com client_type=0 status= cap=15 priority=0 mode=5
W/dalvikvm-heap( 4392): Attempted recursive GC
W/ResourceType( 4303): Skipping entry 0x7f040000 in package table 0 because it is not complex!
W/ResourceType( 4303): Skipping entry 0x7f040001 in package table 0 because it is not complex!
E/vending ( 4640): [22] DownloadManagerBroadcastReceiver.handleDownloadCompletedAction(): content://downloads/my_downloads/1600 state is INSTALLED
W/Service ( 4532): setForeground: ignoring old API call on com.wsandroid.Core.BaseService
W/Service ( 4532): setForeground: ignoring old API call on com.wsandroid.Core.BaseService
W/Service ( 4532): setForeground: ignoring old API call on com.wsandroid.Core.BaseService
W/KeyCharacterMap( 5232): No keyboard for id 131074
W/IInputConnectionWrapper( 5051): showStatusIcon on inactive InputConnection
W/KeyCharacterMap( 5232): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
W/KeyCharacterMap( 4421): No keyboard for id 131074
W/KeyCharacterMap( 4421): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
W/KeyCharacterMap( 5232): No keyboard for id 131074
W/KeyCharacterMap( 5232): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
W/IInputConnectionWrapper( 5051): showStatusIcon on inactive InputConnection
W/KeyCharacterMap( 5232): No keyboard for id 131074
W/KeyCharacterMap( 5232): No keyboard for id 131074
W/KeyCharacterMap( 5232): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
W/KeyCharacterMap( 5232): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
W/KeyCharacterMap( 4421): No keyboard for id 131074
W/KeyCharacterMap( 4421): No keyboard for id 131074
W/KeyCharacterMap( 4421): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
W/KeyCharacterMap( 4421): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
On a final note, the closest i could find to my problem was this.
http://forum.xda-developers.com/showthread.php?p=11214755#post11214755
Would that likely be it?
Thanks for your help in advance

1) Yes, that's probably the reason. Another reason would be Cache2SD not working correctly as a result of something (and by default, it fails on CM7).
2) "Fix uid mismatches" in Amon_RA's recovery. Does wonders.

Having the same issue coming from the same Rom going to the same Rom.
UID did not fix the problem.

Ok, once my CM7 build compiles, I'll try to find some time for the following - back up my ROM, wipe everything, flash CM7, DT's A2SD and post the exact steps for making it work.

I run CM7 with dt, and don't have any problems. I use both the RC and nightlies, CWM 2.5.1.4 (because 3.x screwed up my SDcard, and wouldn't run dt properly), and I use the 2.7.5.2 version of DT...
Sent from my Nexus One using XDA App

Jack_R1 said:
1) Yes, that's probably the reason. Another reason would be Cache2SD not working correctly as a result of something (and by default, it fails on CM7).
2) "Fix uid mismatches" in Amon_RA's recovery. Does wonders.
Click to expand...
Click to collapse
Tried "fix UID mismatches, no luck,
I'm not using cache2sd, my card is too slow, so thats ruled out.
I'm assuming the command to change ownership of /data/app would be something like this in the android terminal.
Code:
su chown user /data/app
except, i don't know what the user is called on android.
Code:
ls - l
brings up root and system as owners. It may be, but i wouldnt expect 'system' is the correct answer.

Or perhaps it is the /sd-ext that is the problem, i noticed when i mounted it on my computer the other night, there was a Lost+found directory, the computer said it was owned by root, and i could not change that to anything else, the file did not go away, or change owner even after reformatting with Gparted. The file reported itself to be 1.1TB, (on a 512) partition, and since then when i have tried to nandroid backup, it hangs on backing up the ext.

Is it safe to say this was cause by clockwork ?
I couldnt find much related in the thread.
Ive never had a single issue with Ext partitions until yesterday using clockwork for the first time.
I wish I could be of more help ... I wiped twice , re flashed back to original Rom stated above apps are now installing but Ext partition doesnt mount or remains unseen.

At this stage, after all the reading and fiddling ive done, i would be very surprised if it turned out to not be caused by clockwork 3.0.0.5
Can everyone else who has this problem, go to your /sd-ext in root explorer, and ask to change permissions. It should come up with a dialogue box indicating that /sd-ext is a read only file system. This, i assume is the heart of the problem. Just to make sure, can people who aren't having this problem do the same?
I think it might be as easy as using chown command, but i don't know what the standard username:group is on android. So i can't try that.
Can any more advanced linux nerds help out?

liam.lah said:
At this stage, after all the reading and fiddling ive done, i would be very surprised if it turned out to not be caused by clockwork 3.0.0.5
Can everyone else who has this problem, go to your /sd-ext in root explorer, and ask to change permissions. It should come up with a dialogue box indicating that /sd-ext is a read only file system. This, i assume is the heart of the problem. Just to make sure, can people who aren't having this problem do the same?
I think it might be as easy as using chown command, but i don't know what the standard username:group is on android. So i can't try that.
Can any more advanced linux nerds help out?
Click to expand...
Click to collapse
Have you tried to use "fix permission" right after you install your rom?

Lost+found IS owned by system (root), but should be empty. If it's bigger than the partition size - it means your EXT is corrupted. You could try deleting this file and checking the partition for data consistency (mounting in Linux).
It couldn't happen when flashing, only if your recovery is bad.

Gparted was acting up while i was trying to wipe all and start again. So trying with new sd card, backed up everything to computer, and will restore the nandroid again, keeping away from 3.0.0.5.
I'll keep everyone posted, it looks like a complete wipe of sd card may be the only choice.

liam.lah said:
Gparted was acting up while i was trying to wipe all and start again. So trying with new sd card, backed up everything to computer, and will restore the nandroid again, keeping away from 3.0.0.5.
I'll keep everyone posted, it looks like a complete wipe of sd card may be the only choice.
Click to expand...
Click to collapse
I've had the exact same problem for a couple of weeks now, never thought of the connection between my ext-problem and clockworkmod, but after reading this thread, i decided to try and change to AmonRa, and voila, everything is now back to normal! cm7-RC and DT a2sd are now playing nice again. All it took was a complete sd-wipe (after I copied everything to my pc), and a new sd partitioning in AmonRA!

Ok, have Re-done the partitions, and restored a nandroid. I can install .apks again.
But i'm getting a market force close, at the initial loading screen, it doesnt bring up a force close dialogue, just goes straight back to home screen. no cache to wipe. If i try flashing gapps again, i lose gmail for some reason, and don't get market working.

I've just tried installing freshly compiled CM7 build of my own - equal to CM7RC1 w/ Gapps compiled into it (somehow the compilation requests unneeded Gapps from Froyo, and fails to insert LatinIME, leaving me w/o keyboard - but it's another matter).
Steps (using a good SD card with EXT2 and Amon_RA's 2.2.1 recovery):
Wipe EVERYTHING, including SD-EXT.
Fresh install, formatting /system (verified in updater-script).
<you'll need to flash Gapps here>.
Flash DT-A2SD 2.7.5.3-beta04 (newest).
Reboot - it bootlooped twice, and booted well on third time - didn't touch it. Might be some build issues of my own.
Open Terminal.
Run "a2sd check".
See that everything works well, Dalvik-cache is on /data.
Tried opening Market, everything worked.
In Terminal, wrote "a2sd cachesd", waited until it did its job (+ several FCs) and rebooted the phone.
Tried opening Market, everything worked.
Conclusion - DT-A2SD works with CM7RC1.

So i grabbed the vending.apk out of the latest gapps, and replaced the other one and set permissions, for some reason it started working later.
So with a new repartitioned SD card, carefully avoiding clockworkmod 3.0.0.5. Everything works fine now.
Thanks for all your help, guys

Having the same problem.
I have HTC chacha running CM7. My phone reboots when I install an app.
Did not read the whole thread but is there a good fix for this problem?
thanks in advance

I had the same problem and the solution for me was format and repartition my sd card. I did an ext3 partition because i read it was the most stable with almost all scripts.
I hope i had helped you
Enviado desde mi Nexy usando xda premium

Open Source CM10.1 for Dell Streak 7 continuation

First you need to have giveen's original port installed: http://goo.im/devs/giveen/jellystreak (via the old thread: http://forum.xda-developers.com/showthread.php?t=2130081). The most important thing this does is installing the TWRP "recovery" bootmenu thingy. You can use it when powering on/restarting the dell streak 7 and then keeping power+volup pressed and then choosing "install update from sdcard" or so.
With AOKP there is one install image that wipes /system and an ota update. I have not tested the ota update.
Download for the AOKP 4.2 build for the Dell Streak 7: http://w3studi.informatik.uni-stuttgart.de/~haagch/aokp/
The non-ota update wipes /system. So you have to reinstall gapps every time too, preferably before rebooting (android deletes settings for apps that are not installed I think).
The "official" gapps package uses neon instructions that don't work on tegra2. You'll see the keyboard, tts, etc. crashing all the time. "tonyp" has created a gapps package that uses "old" libraries that work without neon instructions. So you should use this instead of the official gapps:
Download for non-neon gapps: http://goo.im/devs/tonyp/non-neon-gapps
Gesture typing on the keyboard doesn't seem to work for me, but tts works and it doesn't seem to be crashing.
Known issues for me:
[*]sensors don't work: rotation, accelerometer, gps (I think), magnet field (Sensor driver is sensors.p3.so for now, maybe later giveen gets open source drivers to work)
headphone jack doesn't mute/transfer for some headsets like ones with built in microphones
bluetooth keyboard
Performance problems. Especially when the ram gets full. You can use a ram manager like https://play.google.com/store/apps/details?id=com.jrummy.apps.memory.manager with the Aggressive or Extreme preset to make that problem go away with the cost of background apps being killed very quickly.
Here is the repository: https://github.com/ChristophHaag/android_device_dell_streak7
And here is how to build it on Archlinux:
AOKP: https://gist.github.com/ChristophHaag/6334554
Cyanogenmod: https://gist.github.com/ChristophHaag/6078249
I'm new to android but maybe some other people know something, so I post whatever I come about. Maybe someone else wants to get started too and finds this helpful.
If you want to engage in bug finding and fixing yourself:
Remote debugging c works like this:
On the android device you do
Code:
gdbserver --remote-debug :5039 --attach 1
Which will attach gdbserver to the process with pid 1 and listen on port 5039 on all interfaces.
For a gui debugger I tried nemiver:
For $ANDROID I use the path where the cyanogenmod was checked out.
Code:
nemiver --remote=<STREAK7-IP>:5039 --gdb-binary=$ANDROID/android/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-gdb --solib-prefix=$ANDROID/android/system/out/target/product/streak7/symbols/ $ANDROID/android/system/out/target/product/streak7/symbols/init
And in edit-preferences for sources I added some paths like symbols/, symbols/system/lib and the android/system directory.
There's also a statically compiled gdb that you can use over ssh or so: http://dan.drown.org/android/howto/gdb.html
Obsolete first look into the CyanogenMod adb bug:
I think the problem is in line 1068 in init.c
Code:
if (!action_queue_empty() || cur_action)
timeout = 0;
each time I looked when it comes there the cur_action->name was "property:sys.usb.config=none".
Maybe it is connected with the adb issue. When I googled for the
Code:
E/UsbDebuggingManager( 367): Communication error:
E/UsbDebuggingManager( 367): java.io.IOException: No such file or directory
E/UsbDebuggingManager( 367): at android.net.LocalSocketImpl.connectLocal(Native Method)
E/UsbDebuggingManager( 367): at android.net.LocalSocketImpl.connect(LocalSocketImpl.java:238)
E/UsbDebuggingManager( 367): at android.net.LocalSocket.connect(LocalSocket.java:108)
E/UsbDebuggingManager( 367): at com.android.server.usb.UsbDebuggingManager.listenToSocket(UsbDebuggingManager.java:79)
E/UsbDebuggingManager( 367): at com.android.server.usb.UsbDebuggingManager.run(UsbDebuggingManager.java:115)
E/UsbDebuggingManager( 367): at java.lang.Thread.run(Thread.java:856)
issue I found surprisingly many people having issues with this, but few answers.
But I also found e.g. this: https://gist.github.com/steven676/5...c-remove-obsolete-ro.debuggable-1-trigg.patch
so the problem may be in https://github.com/ChristophHaag/an...lob/master/prebuilts/root/init.streak7.usb.rc
but I didn't have time to really read documentation to that.
I think this file complements $ANDROID/system/core/rootdir/init.usb.rc
I'll either play around with that or I'll add debug output in android.net.LocalSocketImpl.connect(LocalSocketImpl.java:238)
Code:
connectLocal(fd, address.getName(), address.getNamespace().getId());
Then I would at least know what it's trying to do and it would get easier.
Many of the results I saw from googling mentioned that it might have to do with netd.
On the streak 7 I get this:
Code:
cat /dev/socket/netd
cat: can't open '/dev/socket/netd': No such device or address
I'm not sure if this is how it should behave...
An observation is that adbd run from a command line seems to start without an issue and listens on a port specified with
Code:
setprop service.adb.tcp.port 5555
but the access over adb connect <STREAK7-IP> does only say "unauthorized". And "start adbd" does nothing. None of the programs seem to have --help or -h, so I have to look closer into whether they can be started directly.
I'll change "[ro.adb.secure]: [1]" in /default.prop to 0 and see whether that does anything.
In the other thread from giveen I said that I don't see the log spam. This was with debugging in the developer settings disabled. When I enable it, the logspam starts. But whether it is enabled or not, init still eats 100% cpu. The trouble with the debugging is that each time it is enabled and I want to disable it, the streak 7 immediately reboots.
Now that I had logcat via ssh running I caught this when the reboot happened:
Code:
W/dalvikvm( 367): threadid=50: thread exiting with uncaught exception (group=0x40b0e930)
E/AndroidRuntime( 367): *** FATAL EXCEPTION IN SYSTEM PROCESS: UsbDebuggingHandler
E/AndroidRuntime( 367): java.lang.NullPointerException
E/AndroidRuntime( 367): at com.android.server.usb.UsbDebuggingManager.closeSocket(UsbDebuggingManager.java:125)
E/AndroidRuntime( 367): at com.android.server.usb.UsbDebuggingManager.access$200(UsbDebuggingManager.java:46)
E/AndroidRuntime( 367): at com.android.server.usb.UsbDebuggingManager$UsbDebuggingHandler.handleMessage(UsbDebuggingManager.java:177)
E/AndroidRuntime( 367): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 367): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 367): at android.os.HandlerThread.run(HandlerThread.java:60)
Looks bad.
For looking at the android code I just use grep and ls with globbing for the c and config files and for the java part I imported it in eclipse via this method: http://source.android.com/source/using-eclipse.html
This is a build I haven't tested yet: http://w3studi.informatik.uni-stuttgart.de/~haagch/cm-10.1-20130820-UNOFFICIAL-streak7.zip
This is giveen's original nvflash that I am not sure I am allowed to put there as giveen has not put any license information in there: http://w3studi.informatik.uni-stuttgart.de/~haagch/JB_Beta2.1.zip But then it's all apache code and there are no notices in reagards to the apache license or changed files anyway. If not, you can just tell me and I'll remove it.
------------------------------------------------
So the call to connectLocal() that throws the exception has as parameters
fd: FileDescriptor[263]
address namespace: RESERVED with address name space id: 1 and address name: adbd
That doesn't help me much yet, but there are frequent calls with FileDescriptor[263] and namespace RESERVED, id 1, name rild (radio service) that don't throw an exception.
So it's a "valid" file descriptor... But I think the problem is still that adbd is not started by init...
The whole UsbDebuggingManager.run method is
Code:
public void run() {
while (mAdbEnabled) {
try {
listenToSocket();
} catch (Exception e) {
/* Don't loop too fast if adbd dies, before init restarts it */
SystemClock.sleep(1000);
}
}
}
where listeToSocket() is ultimately throwing the exception.
I have also read a bit about how adbd is supposed to work. Apparently in android 4.2.2 they introduced rsa encryption. It looks very similar to ssh. You have your authorized public keys on the device in /data/misc/adb/adb_keys (like ~/ssh/authorized_keys) and on your computer you have your public key in ~/.android/adbkey.pub
So I put my ~/.android/adbkey.pub in /data/misc/adb/adb_keys on the streak 7 and started adbd from the command line on the device. And indeed, when I connect with "adb connect <STREAK7-IP>" I get "<STREAK7-IP>:5555 device product:cm_streak7 model:Streak_7 device:streak7" with "adb devices -l" and adb shell works. It's a bit unrelated, but this applies: https://code.google.com/p/android/issues/detail?id=48126
But the actually important part, the "start adbd" still doesn't do anything.
It really must be somethin with /init.streak7.usb.rc. The stuff in /sys/class/android_usb/android0/ seem to be set all wrong...
------------------------------------------------
I'll just keep posting random things I discover that I find strange or interesting and if anyone knows anything about any of those, they can just chime in.
In /init.streak7.usb.rc there is the line
Code:
write /sys/class/android_usb/android0/iProduct $ro.product.model
"getprop ro.product.model" says "Streak 7" but /sys/class/android_usb/android0/iProduct apparently doesn't seem to be able to take a string with a space because "cat /sys/class/android_usb/android0/iProduct" returns "Streak". You can write directly to it with "cat "Streak 7" > /sys/class/android_usb/android0/iProduct" but it only saves up to the space. I don't think that's really a problem but strange anyway.
I have googled for another tegra 2 device and looked at its usb init rc: https://raw.github.com/CyanogenMod/android_device_samsung_p4-common/ics/init.p3.usb.rc
Adding a section with on property:sys.usb.config=adb did nothing and it seems I haven't been able to google what should be in /sys/class/android_usb/android0/idProduct for the streak 7.
I think I'll just look into how init on android works and how the triggers work. Then it shouldn't be too hard to figure out what exactly it is trying to do and why it is failing.
------------------------------------------------
I was trying to get my head around why "getprop sys.usb.config" would always return "none" and the system wouldn't respond to "setprop sys.usb.config adb,mtp" in any way. So I got to suspect that /init.streak7.usb.rc was not used at all. Then I compared the imports and found that /init.streak7.rc did use a relative path for /init.streak7.usb.rc while all the other init*.rc were using absolute paths.
So I'm not sure if it this is really the thing that fixed it, but it's the latest thing I tested and now init's 100% cpu and adb are fixed: https://github.com/ChristophHaag/an...mmit/eee0625e11cfafd510c3bada6ae67a133766c0f4
Edit: Wait, it happened again. Maybe not. :/
Hm, no, definitely not it. Can't even reproduce it. It worked after adb sideload and wiping the cache and the dalvik cache.
At least it's clear now that init's 100% cpu usage and adb not working and the dalvik crash when disabling debugging are all the same issue.

Good luck. I'll give you a hint as a parting gift. The USB issue is not kernel related.
I really dont care to licenses anything so you are free to do with as you will. Personally, I will continue to develop in private and if there are kernel changes, as per the GPL, I will make those updates available.

[moved to hidden section in first post]

[moved to hidden section in first post]

[moved to hidden section in first post]

If you really want to help, let me know. I'll let you in on my secret.

giveen said:
If you really want to help, let me know. I'll let you in on my secret.
Click to expand...
Click to collapse
Do I want to help? Does this thread look like I don't?
As I've said I'm new to the android code so I'm not really sure what I'm doing yet.
After rebooting with debugging enabled and adb sideloading an image it works for some reason (until you disable debugging in the developer settings, then it loops on sys.usb.config=none again) but it's all clearly not like intended by /init.streak7.usb.rc. /sys/class/android_usb/android0/idVendor is 18d1 and android_usb/android0/idProduct is d002 which is set in init.usb.rc for on property:sys.usb.config=adb...? I just don't get it yet. The init readme says declaring an action or service twice is an error but this is from upstream, so adb is supposed to always be 18d1:d002?
So if you know something I don't I would obviously greatly appreciate it if you told us. In fact you can directly push to the repository now if you wish to do so.

ccxxx said:
Do I want to help? Does this thread look like I don't?
As I've said I'm new to the android code so I'm not really sure what I'm doing yet.
After rebooting with debugging enabled and adb sideloading an image it works for some reason (until you disable debugging in the developer settings, then it loops on sys.usb.config=none again) but it's all clearly not like intended by /init.streak7.usb.rc. /sys/class/android_usb/android0/idVendor is 18d1 and android_usb/android0/idProduct is d002 which is set in init.usb.rc for on property:sys.usb.config=adb...? I just don't get it yet. The init readme says declaring an action or service twice is an error but this is from upstream, so adb is supposed to always be 18d1:d002?
So if you know something I don't I would obviously greatly appreciate it if you told us. In fact you can directly push to the repository now if you wish to do so.
Click to expand...
Click to collapse
The problem is CM.
I switched to AOKP which is close to Google's AOSP, and the problem solved itself. Something in the way USBManager is programmed in CM screwed things.

I got around to download aokp today.
The build system is slightly different, but easy enough to set up. I first just did an "update" to it, but the adb/init problem persisted, acore kept crashing (but deleting data for the contacts app "solved" that).
So I decided to finally make a factory reset. Not really sure what happens there, but that didn't delete the apps in /system/apps I think so I just wiped everything except sdcard etc. with twrp and installed the image again. This time it works better it seems. adb seems ok for now, cpu usage is okay.
The 4.2.2. google apps for that are these: http://goo.im/gapps/gapps-jb-20130812-signed.zip
Now I'm not sure: Would a factory reset/complete reinstall have helped with cyanogenmod too?
aokp is missing a few features cyanogenmod has, most notably the performance settings where you can overclock and set up zram with the gui.
Keyboard still crashes. Not really surprising that illegal instruction hasn't changed.
There doesn't seem to be recent apps when long pressing the home button. Strange.
Not sure how much I like it yet and whether I'd rather use cyanogenmod.
Here it is: http://w3studi.informatik.uni-stuttgart.de/~haagch/aokp_streak7_unofficial_2013-08-23.zip
Thanks, giveen.

No problem. AOSP keyboard burns RAM like nothing else. If you switch to an 3rd party keyboard , you will no longer crash. This problem is common on a lot of low memory devices. ZRAM doesn't really work. I have a script that I want to test out that DJ_Steve had originally wrote. Also, I will send you the sensor files you need to modify to get them to work.

google has this keyboard in the play store https://play.google.com/store/apps/details?id=com.google.android.inputmethod.latin and I got it from http://dl.androidnext.de/com.google.android.inputmethod.latin.apk. Works ok, but has issues like you can't disable the "ducking" blocking of "offensive" words...
The sensors changes you commited work well. Rotation/acceleration/magnet/light seem to react normally.
It's almost usable now.
For people building it from source: If you get a weird error like "ERROR: couldn't find <type 'property'> in build.prop" and can't find anything useful with google... I deleted out/* and did a complete rebuild and then it worked.
Plugging in a headset still doesn't turn off speakers but it seems only like a minor issue since it seems to be detected just fine:
Code:
V/WiredAccessoryManager( 374): Headset UEVENT: {SUBSYSTEM=switch, SWITCH_STATE=1, DEVPATH=/devices/virtual/switch/h2w, SEQNUM=2006, ACTION=change, SWITCH_NAME=h2w}
V/WiredAccessoryManager( 374): newName=h2w newState=1 headsetState=1 prev headsetState=0
W/AudioPolicyManagerBase( 103): checkOutputsForDevice(): No output available for device 0004
V/WiredAccessoryManager( 374): device h2w connected
Google tts is crashing like the keyboard (
Code:
F/libc ( 6525): Fatal signal 4 (SIGILL) at 0x5dc80738 (code=1), thread 6525 (gle.android.tts)
) but pico tts seems to work, at least with english.
A Google search gave me this:
http://stackoverflow.com/questions/7102606/sigill-in-android-ndk-code/7104177#7104177
And further this might be worth looking into: http://forum.xda-developers.com/showthread.php?t=2186251
Not sure whether it's simply neon instructions or register usage of 16+ since I haven't looked that close into the build system yet. But probably ILL_ILLOPC means it's a neon instruction.

So sensors work now? I've been at that for months and I wasn't sure if I got it right. If I got it right, that was months of work there that I wasn't even sure was going to work.
Headphones and microphones need to be adjusted in mixer_paths.xml

Months of untested work that just works? Impossible! :good:
I haven't done a really thorough test, but they all seem to be doing something. https://play.google.com/store/apps/details?id=imoblife.androidsensorbox seems to have a little problem with the directions with the rotated screen though. But in general it all does something that seems related to what I do to the device.

The AKM8973. is a chip that is normally found on qualcomm devices. So I had to track down the right HAL and then modify to work with Tegra sword ices. It's a terrible hack/slash, modify and pray it works job. I had Just finished. Does the screen rotate?

giveen said:
The AKM8973. is a chip that is normally found on qualcomm devices. So I had to track down the right HAL and then modify to work with Tegra sword ices. It's a terrible hack/slash, modify and pray it works job. I had Just finished. Does the screen rotate?
Click to expand...
Click to collapse
Yes, the screen rotates. And even more impressively, it rotates correctly!

Good. Now i can focus my energy on the camera.

Hm, having difficulty with my compiles booting. Chris, if you compile and upload the zip, I can give you my goo.im information and you can push it as an auto-update. Don't forget to include your name in there somewhere for credit as well as you are now part of the team.

giveen said:
Hm, having difficulty with my compiles booting. Chris, if you compile and upload the zip, I can give you my goo.im information and you can push it as an auto-update.
Click to expand...
Click to collapse
I have edited my first post.
http://w3studi.informatik.uni-stuttgart.de/~haagch/aokp_streak7_unofficial_2013-08-25.zip
http://w3studi.informatik.uni-stuttgart.de/~haagch/aokp_streak7-ota-eng.c-builder.zip
giveen said:
Don't forget to include your name in there somewhere for credit as well as you are now part of the team.
Click to expand...
Click to collapse
Yea, maybe if I contribute something substantial instead of cosmetic changes.

OH yeah, bluetooth keyboard, I see that as one of your issues. I'll upload a bunch of idc files that should at least address that issue, not sure though.

Are you missing any commits? I noticed your update has sensor working but my build does not.

[Q] Dynamic Kat 1.4 Lost root

Since I'm mostly a lurker and I rarely run into issues that someone hasn't already run into, I don't have the post count to post on the actual Dynamic 1.4 thread. But I'm a little stumped. I seem to have lost root, and when I run anything in SS I get multiple I/O errors referencing data/data/chainfire su files.
I came from knoxraid. Installed new safestrap. wiped. Installed 1.0 from SS then 1.4 from SS. Set up the phone. Restored apps. Set up my favorite xposed modules. All was good for a few hours then I noticed I didn't get a full screen call ID on a call. I went in to check xposed and all the modules were unchecked. I tried to install/update but it said xposed wasn't compatible with my version. So I uninstalled xposed and tried reinstalling. Now it errors on install with "Can't install, free up space and try again" I have plenty of space, but I noticed the last I/O error I get in SS refers to data/data/xposed something or other. So I did the whole wipe and start with 1.0 process over, but nothing changed. No root. And I don't know if the I/O errors are keeping SS from wiping system when it installs, so I'm wary about installing another rom just to see if it works. But I can still boot into SS.
So I'm not sure which direction to go from here.
The errors are:
E:error: I/O error
E:error opening '/data/data/eu.chainfire.supersu/logs'
E:error opening '/data/data/de.robv.android.xposed.installer'
" " " /data/data/eu.chainfire.supersu/requests
fix permissions didn't work. An extra error was "unable to chmod data/data/eu.chainfire.supersu/requests"
I can't access those files using file explorer in SS.

Well if anyone runs into a similar issue- I wasn't able to install any applications after that as well.
A wipe from stock recovery fixed it. Although it wiped a lot more than I had anticipated

Was the installation on the stock slot? That is where it needs to be. Get your post count up so you can join us!

bri315317 said:
Was the installation on the stock slot? That is where it needs to be. Get your post count up so you can join us!
Click to expand...
Click to collapse
Yeah I made sure to use stock slot. And everything was fine for a few hours. I really don't think it had anything to do with the rom. I'm leaning towards and install/enable/unistall/disable process that I was burning through on xposed, since the locked up files were su and xposed. And I had other apps downloading and installing in the background. I just gotta learn to slow down. Got everything set up today and it's running beautifully. I was on your Dynamic GPE for JB and it was my favorite. I gave the KK version of knoxraid a shot but got super excited when I saw SS had updated and I could go back to dynamic without odin.
It was fun now that it's fixed. I hadn't been into stock recovery since the old DX days. I didn't realize a data wipe from there took out just about everything on internal storage. Good thing I had the important stuff backed up.
I've been following your work for a while. And you sir, are fantastic. :good:

There is something wrong with your data partition ....

Hello World,
before I explain my problem, I am most humbly asking for one small favour:
Please(!!) nobody give me any advice along the line of: Just do a factory reset and start from scratch
I've got almost a thousand apps installed on my system and I'm in no mood to even try to reconfigure it all over again.
Some time ago I installed the latest beta of Cyanogenmod on my Samsung Galaxy Note Tablet SM-P900.
After some time I encountered so many quirks with it, that I decided to flash back to the latest stable build 12.1-20151029 (Android v5.1.1).
Since I was always able to upgrade w/o wiping data, I did the same here, but right after the downgrade the system started misbehaving.
Matter of fact, I could only boot through to the desktop, once I had removed some google.* related dirs from the data/data location. Right afterwards I reinstalled the affected apps from backup and that fixed that.
Unfortunately during the proces of peeking and poking in data/data I messed up some ownership/permission settings.
I also managed to fix those via an old backup (via: chmod/chown --reference), *but* now I am getting a popup message telling me:
"There is something wrong with your data partition..." everytime I reboot the system.
Afterwards I can work just fine with the tablet, but every 3rd or 4th day it suddenly reboots - then being stable again for another couple of days.
If I could only find out what fault this messages refers to, I could fix it manually - but I couldn't find anything useful by reviewing the logcat info.