Did setting it to 210 fix the issue...?
Strange that only you folk have had any problems with it.
[TESTING] XDAndroid GBX0C 2.3.7 Build
- Thread starter arrrghhh
- Start date
Did setting it to 210 fix the issue...?
Strange that only you folk have had any problems with it.
http://xdandroid.com/wiki/Logs
If you guys are going to test this stuff, knowing how to get logs is kinda essential. Thanks!!
Well, at least you have a workaround. I'm not sure what can be done, as the build.prop is the same for all devices...
Perhaps we can do some detection and do a setprop after the fact.
Great.. But I still don't know where to find "build.prop"
Sorry, very green noob here.
Well honestly users shouldn't need to modify the build.prop. Kinda disturbing that's the only fix, but I guess if it works...
In a terminal (thru adb or a terminal app like ConnectBot on the Market)
Code:
setprop qemu.sf.lcd_density=240Nope, tried it and the Android keyboard was still 3 mm high
I guess you can download "hacker keyboard" from the Market, and you can resize the kb completely....
correct usage should be:
Code:
setprop qemu.sf.lcd_density 240did try to set it to 210 and 240, not fixing... keyboard is still about 5mm size at the bottom.
tell me which logs you need!
\\edit:
I also tried the "reboot on missed call" error. the following issue is the problem:
when you have a wake up from the call, you just miss it by a second and then press any key or touchscreen the phone crashes. probably the wake up routine isn completed for "wakeup on incoming call" so that the touchscreen isn't ready... the phone just hangs for a few seconds with "missed call from blblabla" in the top line and then restarts.
Nevertheless, very good android port! runs flawlessly with a sandisk sd card.
greetings from germany!
Acid
Last edited:
So for the keyboard, it seems the easiest fix is 'hacker keyboard' on the Market.
As for the call issue, definitely will need logs for that. You'll probably need to setup continuous logs too, and try to recreate the issue...
http://xdandroid.com/wiki/Logs
Okay, I'll do the testing after some hours of sleep.
today was speed kernel day, I testes V12 with this release.
Runs somewhat faster, boot is good, everything else still works.
I attached the kernel and startup. Just copy everything to sdcard/V12
Add your system.ext2, rootfs.img, data.img and AndroidApps directory and boot.
\edit: removed, sorry guys too much straction from testing build.
Have fun!
-Acid
today was speed kernel day, I testes V12 with this release.
Runs somewhat faster, boot is good, everything else still works.
I attached the kernel and startup. Just copy everything to sdcard/V12
Add your system.ext2, rootfs.img, data.img and AndroidApps directory and boot.
\edit: removed, sorry guys too much straction from testing build.
Have fun!
-Acid
Last edited:
Hello, why I can not see video? Only gives me sound and black screen.I appearing when the program continues with the sound.Solution?
neopeek[dot]com/viewtopic.php?f=70&t=7650 this is the source.
V12 is the name of the kernel.
kernel sources can be found here: gitorious[dot]org/~helicopter88/linux-on-qualcomm-s-msm/ext3-kernel
I also made a new startup txt. is attached to the post. battery is 80% after 4h standby.
to prevent the overclocking from "going to sleep" (setting to 128mhz while asleep) put pm.sleep_mode=3
greets from germany,
acid
\edit: may not post outside links -.-'
\edit2: attachment removed, too much distraction from main topic!!! TEST THE BUILD AS IS!
Last edited:
Hrm... Video codecs *should* be up to snuff, but there still might be some videos that won't play.
What are you trying to play? Youtube HQ?? That should work, but again, there's probably some video resolutions that are just too much for this device. IIRC, hyc was able to get the binaries to pump up to 640x480, but was never able to get up to the 800x480 (er 400?) that our native resolutions are capable of...
I think he felt it was a hardware limitation. Whether it is or not, Android will probably never be on the same level as WinMo in the decoding high quality video area....
Ah, yea that stuff probably won't run on RHOD. Thanks tho.
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).
