[TESTING] XDAndroid GBX0C 2.3.7 Build
- Thread starter arrrghhh
- Start date
Hi,
now i get connected to android via adb.
If i try 'adb pull /data/system/dropbox/'
i get
i also tried this:
edit:
i got the file with 'adb pull /proc/last_kmsg'
(see attached)
i hope it is the right one ?
now i get connected to android via adb.
If i try 'adb pull /data/system/dropbox/'
i get
i also tried this:
edit:
i got the file with 'adb pull /proc/last_kmsg'
(see attached)
i hope it is the right one ?
Last edited:
Code:
[ 471.416992] ARM9 has CRASHEDYou're using EVERYTHING from the first post? I can't see which kernel you're running. Perhaps you could post a dmesg as well...?
I'm not sure why it would only be you failing.
I think there may be a slight misunderstanding: the first post (about this problem) was by me, so at least I am no longer the only one to get almost immediate reboots.
I didn't get round to pulling the last_kmsg file yet, but I reformatted my SD card with the HP tools (twice) and tried again with only GBX0C on the card, once at the root and the other time in a folder: still rebooting!
I didn't get round to pulling the last_kmsg file yet, but I reformatted my SD card with the HP tools (twice) and tried again with only GBX0C on the card, once at the root and the other time in a folder: still rebooting!
For me, (regardless of whether I was running FRX07 or GBX0A/B/C), if I'm connecting to any secured WiFi, I get random intermittent problems (disconnects, reboots, etc). Sometimes it works fora while, then, boom, disconnects or (less frequently) reboot to WM.
When I 'unsecure' my router, my network connectivity on my Touch HD running GBX0C is quite stable. Obviously this causes other problems, so I don't leave my router like this all the time... Give it a shot and see what happens! Maybe it's a related issue.
this is not normal... of course my internet is WEP
WEP is extremely insecure, you might as well run an open network...
Use WPA2 preferably, or at least WPA.
Are you booting Android with WinMo in Airplane Mode...? I wonder if something from WinMo is "bleeding over" and causing this...
Are all Blackstone users having this issue? I wouldn't think so...
i tried it with Windows Airplane Mode.. -> same problem
i think not all blackstone users have this problem, but Motik and I get this.
And we did not know how we solve it. I did not know what can i try to do to solve the problem. Could it be a problem with 2G or 3G, because it is only when i unlock the blackstone...
i think not all blackstone users have this problem, but Motik and I get this.
And we did not know how we solve it. I did not know what can i try to do to solve the problem. Could it be a problem with 2G or 3G, because it is only when i unlock the blackstone...
that decision is not up to me...
---------- Post added at 06:23 PM ---------- Previous post was at 06:22 PM ----------
I'm not...
Interesting. If you're in airplane mode, I would think it would be OK. But Android I guess is not in airplane mode... Can you hold the power button and put it in airplane mode before it reboots? I'm thinking the issue is GPS, but I'm not positive.
Have you tried any other SD cards?
I'm kind of at a loss as to what it could be. This is a fresh data.img? Unpartitioned card? I think I've asked you to do a full FAT32 format of the card with the HP Tool, which will take care of that...
I would encourage whoever has made such a decision to change it...
lol, with company I mean the the internet service company (zon). Should I installed the equipement alone? lol
Oh. If it's yours, then change it. Like I said, it's very insecure. Anyone with an extra few minutes on their hands can crack WEP keys with simple packet injection. You might as well be running an open network...
ok, thanks
can one of the builds run in 300 mb, with no apps at all, just the fundamental? I really think that's impossible, but if it was possible i could try some things...
I don't understand what you mean. So you'd like to only have 300mb on the FAT32 partition of the SD card? If so, probably not. A 512mb card is required at bare minimum. I guess you could make the data.img smaller than 256mb... But why? What's the point?
this is just me thinking, and it might sound stupid since it was just a idea that I had, so here it goes: I resetted my HTC Touch HD (not hardreset, with the system tool) and I had 300mb free space.
If a directory was made on the main memory, android would run, not has a ROM, but like in the sdcard, but running in the main memory. Of course this seems impossible, because of the low amount of memory. It was just an idea that I had and I would try it with not installing any apps, just having the minimum space possible occupied... windows is only occupying around 30mb, but with Android builds is a different thing...
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
16Hey folks,
This is a completely new build, with all the new changes baked in. We wanted to do a semi-official test release to collect bugs and hopefully do a formal official release with everything settled. The main pain point is the CSV files (see pre-install prep).
So a brief overview:
- New acoustic routing code baked in. Should fix most if not all audio routing problems, and will provide more debugging if stuff does go wrong. Also allows for more granular tweaking, see the CSV files.
- GPS fixes for GB - GPS not only works in GB now, but it doesn't kill sleep! I was able to use GPS, get a solid lock, and put the device to sleep no problem.
- BT should work & well with the new acoustic code. Post results.
- RHOD users now have a choice of kernels. .35+ all have the new acoustic - so .35, .39, 3.0 and 3.1 are all fair game now... This is bundled with .27!!
- Keep in mind, autobuild .27 kernels will produce no audio in this build... Obviously the bundled kernel will work, and the absolute newest .27 autobuild kernel does work now - Feb.27 2012 or newer.
- rootfs tweaks - first, it will detect which kernel you're on (.27 or .35+) and automatically apply the correct firmware. Second, is it will always copy/extract the modules... failures there were getting annoying, and this is surefire if brute-force...
- Few Easter egg apk's...
- Probably a lot I'm forgetting, this might change
Pre-Install Prep REQUIRED!!!
This step is crucial, and I forgot all about it! You must copy all of the *.CSV file from your WinMo ROM - these are in the \Windows\ directory. There's a very easy way to do this. It involves the Total Commander app for WinMo (Direct Link for the perpetually lazy...) (included in EnergyROM and others probably).
Now you're in Total Commander looking at your \Windows\ directory. Whew... lots of files. Fear not! Hit the "CTRL" button, then the green "Plus" button. This opens the Select/Unselect files dialog. Put in *.csv, press "select" and voila. All CSV files are selected. Now - File -> Copy/Move -> I want you to copy these (should be 10) files to the ROOT of your SD card. No folders!!! This is hardset right now, until we get it all implemented into the build properly. Thanks!
Install
Assuming you've done the pre-install prep; this is installed just like the other XDAndroid builds - grab your startup.txt (don't forget rel_path= if you don't have it at the root of the SD!), ts-calibration and boot!
Download3Sorry. [...] I thought you are having trouble with this phone development, just tried to help. It will never happen again...
Still don't get how you talking about selling the phone cheaply helps with development.
Any developer is welcome to join... the project on the Blackstone front never really had a developer. A few came and went, but very few... none stayed long either.
So if you want to help, by all means. If you're just going to talk about selling your phone go elsewhere - these types of posts have NO business in a development forum.3
Either make one, or STFU. Eternally posting this doesn't help anyone. Really getting tired of seeing this exact same post from you over and over and over...2Caveats:
- Audio stutters every 10sec. The only fix I've heard is using a kernel from G3rmo (unfortunately it is old), or
Which kills the [battery] process. I'm sure this will have negative effects on the battery meter/battery life...Code:
su kill -9 28 - SD Card not working...? "Waiting for SD Card" appearing on boot...? Try putting this command in your startup.txt
See gummbah30's post reminding us of these commands.Code:
msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave - SD Card has partitions? (If you used a non-XDAndroid build the answer is YES) Then you need to add "no_partitions" to your startup.txt. Between the quotes on the set cmdline line. Do not put it on its own line, it goes in between the quotes! Make sure there is one space between each item.
- BT might still be flaky
- The CSV files from my BLAC100 are attached for the lazy. I'd like to gather CSV's from each RHOD, I'm curious if any ROM devs have changed them out either... This could get interesting. If you folks don't mind, post up your CSV's, point out differences with mine, etc... We're trying to figure out how to unify these, if possible! Thanks!
- Keyboard tiny/unusable? Either change the IME (long press on the input box) Get rid of it! I've heard "Hackers Keyboard" is a good alternative - many options. There's also "Better Keyboard", Swype, etc... Side load the APK using AndroidApps, adb install, etc.
GBX0C Changelog- Camcorder: Now works (tested on rhodium).
- Acoustic: Bug-fix : correct random loss of dual(rear)-mic.
- MMS: Bug-fix: Slides with zero duration on Sprint.
- Gps: Bug-fix: Init/de-init sequence fix (correct gps not starting up after being unchecked in Settings).
- Gps: Bug-fix: End gps session with a correct rpc call (relevant to amss6125 devices).
- Gps: Bug-fix: Don't send delayed position requests after session has ended (possibly relevant to Navigation issues).
- Gps: New feature: Xtra (aGPS) -> verified to work on rhodium/cdma raph.
- X1 specific: Screen rotation patch.
- Added tytung's GPS injector app to AndroidApps\Other as well as updating/cleaning up some apps in AndroidApps.
- Modified rootfs for newest apsta firmware & wifi firmware - wifi tethering now works flawlessly in the newest kernels! .27 is still bundled for the record...
2
RIP?
Nothing tangible. No devs for BLAC either, as I've stated 1,000x.
Patches welcome, haven't seen any (that are actually useful, lol).
