Jump to content

sibbor

Members
  • Content Count

    71
  • Joined

  • Last visited

Community Reputation

0 Neutral

About sibbor

  • Rank
    Regular

Contact Methods

  • Website URL
    http://sibbor.nu/

Profile Information

  • Your Current Device(s)
    HTC One X, LG Optimus 2x
  1. It is, but one might be able to activate the companion chip somehow? The chip seems to do all the magic in the HOX, as seen in the first paragraph. Also as seen in the 2nd paragraph we would need some software to use it (modified camera). Btw, looking forward to another update now ;)... Awesome work with the 3.1 kernel, even though it's rebooting. Anything else in store for us CM9 users? EDIT: HTC references to the the dedicated chip as HTC ImageChip.
  2. As a developer I must agree, totally. Stability improvements + battery performance is always nice. That makes our beasts really useful. Your kernel will probably be used as base/reference by some developers. Already seen some developers pulled some patches. Sharing is caring. I'm glad you're keeping the kernel open and helping out. The source code from HTC really needs a lot of attention. Really cool to see so many developers working on delivering improvements. EDIT: Trip, since you've been digging deep into the kernel code for a while: you seen anything about USB Host/OTG? I heard HTC is planning to add support for this in the future on the HOX. With their dirty fingers I rather do it myself, but I lack the skills on this subject.
  3. I was thinking that the echo sound during phone calls might occur because of incompatible RIL/baseband (BB). The LG Optimus 2X had similar issues and LG released a lot of different RILs + basebands... it was a mess to get right. That's why I created GetRIL; to match RIL/BB up. Today I've added preliminary support for our HTC One X + non-rooted devices (presenting more data, but inactivated downloading & installing of RILs, naturally). Does anyone care to test GetRIL 0.8.3 beta 1? I haven't tested it enough and I'm in need for some feedback. Does it work properly for our HTC One X's? Does it report a certain RIL for you (only added three WWE so far -> 1.26, 1.28, 1.29)? Does installing a RIL solve the echo for you? I've attached the APK, as a .txt file because the file wasn't allowed the .apk extension. GetRIL 0.8.3-beta-01.txt
  4. True, but couldn't that be fun? Ban party over at XDA ;-)... J/K.
  5. Sharing your sources might be useful here. That way your work would be able to exists on XDA, with proper credits back to you (hopefully?!). You're doing great work with the ROM, but it really doesn't get the attention it deserves. This ROM + a kernel from XDA is the way to go, at least until your kernel is released.
  6. Great news. Looking forward to see what's included in [Agent] 007 release ;) Btw, did you see my tweet regarding the RIL? What files is really needed for our HTC One X? I can only see that you've included the following file: rild.libpath=/system/lib/libhtc_ril.so And not: # RilLibPath for Ganlite by William_Lai rild.libpath.ganlite=/system/lib/librilswitch.so rilswitch.vendorlibpath=/system/lib/libhtc_ril.so rilswitch.ganlibpath=/system/lib/libganril.so[/code] Howcome? What are these other files?
  7. Perhaps you could try CallVolumeFix-0.1.1.apk made by me? Unsure whether or not it works for the HTC One X. If it is that would be great. If not, well then it's up to Trip to fix it ;)
  8. I've read using test-keys can trigger Play Stores issues...Here's some diffs I see between build.prop for CM9 and stock ROM 1.29: ro.product.locale.language=en // CM9 ro.product.locale.language=xhdpi // Stock 1.29 ro.build.tags=test-keys // CM9 ro.build.tags=release-keys // Stock 1.29 ro.build.type=userdebug // CM9 ro.build.type=user // Stock 1.29 CM7 on the LG O2X had some in-call volume issues too, but they could be fixed by maxing out the volume bar and then lowering it to the preferred volume level. Therefore I made an app (a service) that did this manually everytime a phone call was hooked. These properties is probably not used for AOSP or CM9, but perhaps tells us a bit about the preferred volume levels for the H1X. # ----------------------------- # speaker volume is from 20 to 31 # this corresponds to -2dB to +8dB # ----------------------------- audio.speaker.voice.0=20 audio.speaker.voice.1=21 audio.speaker.voice.2=24 audio.speaker.voice.3=26 audio.speaker.voice.4=28 audio.speaker.voice.5=31 # ----------------------------- # earpiece volume is from 20 to 31 # this corresponds to -2dB to +8dB # ----------------------------- audio.earpiece.voice.0=20 audio.earpiece.voice.1=21 audio.earpiece.voice.2=24 audio.earpiece.voice.3=26 audio.earpiece.voice.4=28 audio.earpiece.voice.5=31
  9. Interesting... Noeri ...‏ @TripNRaVeR "Release of fixed CM9 soon :) l'm the one you've been waiting for" -- https://twitter.com/#!/TripNRaVeR/status/200482977883504640
  10. Mr. O'Brien, what can I do to assist? See a few posts back for full details. Running everything manually on Ubuntu 12.04, via adb, I'm getting all files pushed but got issues with the fs: [email protected]:~$ adb shell "mount -wo remount rootfs /" error: insufficient permissions for device [email protected]:~$ adb shell "cat /data/local/busybox > /system/xbin/busybox" error: insufficient permissions for device
  11. Doesn't work: S-Off, locked bootloader, unrooted, 1.29 stock ROM. I've got the Android SDK installed, so made some changes to root-linux.sh. I can't get it to work though: * daemon not running. starting it now on port 5037 * * daemon started successfully * cannot stat 'busybox': No such file or directory cannot stat 'su': No such file or directory cannot stat 'Superuser.apk': No such file or directory Unable to chmod /data/local/busybox: No such file or directory Unable to chmod /data/local/su: No such file or directory Unable to chmod /data/local/Superuser.apk: No such file or directory rm failed for /data/local.prop, No such file or directory Reboot Reboot again... note that when device returns it may appear to be bootlooping, don't panic! /data/local/busybox: No such file or directory Unable to chmod /system/xbin/su: No such file or directory Unable to chmod /system/xbin/su: No such file or directory Unable to chmod /system/app/Superuser.apk: No such file or directory Reboot one last time... SLIGHTLY OFF-TOPIC: My adb broke since upgrading to Ubuntu 12.04, and this is how I fixed it: [email protected]:~$ adb devices List of devices attached ???????????? no permission 1. Create the file: /etc/udev/rules.d/51-android.rules 2. Add the following line to the file: SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666" 3. Restart udev service: sudo service udev restart [email protected]:~$ adb devices List of devices attached HT23ZW100391 device
  12. Alright. Any plans on sharing your findings in the future? I'm a C/Java developer, but not really into this ROM development. Always enjoy reading changelogs and source code. Did a few KANGs for the LG Optimus 2X, for private use only. Will see if I can make CM9 run on my H1X soon too. Keep up the good work!
  13. Yeah, I noticed... ;) https://github.com/T...12997b0dac057fa Doesn't seem like the source is up to date or the one that shipped with the device either? Saw your tweet about the benchmark. Low memory performance. Or did you do any experiments? Btw, got your CM9 source available somewhere? EDIT: or are you still cleaning it up before showing it in public?
  14. Could you please provide a changelog with your releases on the first post or at least for the post where you're announcing the new update. Downloading 005 now. I guess 005 006 contains fixes for the mic noise cancelling? WiFi over mobile data fix too? AP priority fixes? Non-wiping version? These are the once I've seen discussed. A bit hard to follow. GREAT work with the ROM + the kernel (noticed on Twitter)!
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.