Develop Bugs

Test kernel: Zoom bar acting as multitouch pinch to zoom

Someone asked what the point of the new .39 kernel is, well here's a new feature I've coded up that was made possible due to the more modern kernel.
I have modified the touchscreen driver in the kernel so that the zoom bar is now working, and it sends signals to Android that make it think you're sending a multitouch pinch-to-zoom.
I've got it set so that it sends an input from the center of the screen. As you slide right, the driver tells Android two fingers are moving apart from the center. As you slide left, the driver tells Android two fingers are sliding from the sides towards the center. The net result is that the zoom bar works in any app that supports pinch to zoom.
I've uploaded a video showing it in action:
http://www.youtube.com/watch?v=GRWUzPveU14
I'm going to submit this patch soon, and I'd like it if some people would try it out and give any feedback before I do so. I suppose things to pay attention to would be any increased wonkiness in the touch response, as well as boundaries for the zoom bar. Also, if you have a better idea on how this should work, it's now or never.
Unfortunately, this is a modification of the new .39 kernel, which means that a lot of things are not working on it, and this test kernel will most likely not be suitable for daily use if you like wifi and the other things that don't work on .39 yet.
In order to install you must do the following:
1. Replace your zImage with the one attached.
2. Use the .39 haret (included in the zip for your convenience) with the .39 startup.txt line (set initrd_offset 0x00a00000)
3. Place the included android.hardware.touchscreen.multitouch.xml under /system/etc/permissions. I tried bind-mounting it from conf, but for some reason that did not work for me. If you don't do add this permission file, the multitouch points will still be sent to Android (and will show up in the app Multitouch Test), but Google's own apps like Browser will ignore them.

Amazing.
First time, I can use this since ages.
Unfortunately, my phone has become very sluggish with this test kernel.

Tippfehler said:
Amazing.
First time, I can use this since ages.
Unfortunately, my phone has become very sluggish with this test kernel.
Click to expand...
Click to collapse
I totally agree with that!
Rhod100_nl
Nice work!

I assume pinch-to-zoom is pretty well supported in Android. Does this mean the zoom bar is now more supported (for zooming, button hacks aside) in XDAndroid than it ever was in officially baked HTC WinMo?
Impressive. Thanks for the vid.
I'm planning to give the .39 kernel a quick test run, hopefully this weekend. There's some software that crashes on me on open now and I'd like to see if its any different with .39. I'll try to give this a whirl then.
As for functionality, the p2z is cool, but not something I've been pining for. I don't know exactly what your plans are, but I'd love it if that function could be switched off easily (a line in startup.txt?), so future hacks creating, say, soft buttons on the bar instead could be more easily implemented.

fortunz said:
I'd love it if that function could be switched off easily (a line in startup.txt?), so future hacks creating, say, soft buttons on the bar instead could be more easily implemented.
Click to expand...
Click to collapse
well that bar has been designed to be a zoom bar. you can do whatever you want with it but always a zoom bar remains using it as a "virtual button" is possible but on the phone you will always have the magnifying glasses printed
What you suggest is an hack to the original zoom bar design and it's not as useful as the zoom function (that on our resistive single touch screens is missing)

LinoX said:
What you suggest is an hack to the original zoom bar design and it's not as useful as the zoom function (that on our resistive single touch screens is missing)
Click to expand...
Click to collapse
All I suggest is flexibility. I'm not trying to steal your zoom

fortunz said:
All I suggest is flexibility. I'm not trying to steal your zoom
Click to expand...
Click to collapse
All you are actually suggesting is complexity, indeed. A "soft" array button must be handled properly by the kernel / os / applications and it is a lot more than "one hack" for a function that will be probably not used because the zoom is a bit more important than a button

I'm going to have to break out the bold, aren't I? I'm not asking for soft buttons. I'm asking that this implementation be flexible enough to allow for future hacks like soft buttons, whether they are your favorite or not. I don't even know if the request is necessary, but I never imagined it would be controversial. If that flexibility really is too complex, forgive the request and ignore it.

It's "controversial" because you are asking for a strip of capacitive touch to turn into buttons. As the OP indicated, implementing this requires not only a new kernel+touch, but files in system.ext2, so the system _thinks_ you have p2z when you still have a resistive screen. So what you are asking for is to make that "flexible" when the base feature has barely been coded+tested.
If you truly want capacitive soft buttons, look at the DIAM or RAPH. Back way then (2.0ish), the LED on the bottom button-panel/scroll would light up on finger contact (not pressed) when running xdandroid. It was more of a "wow it's cool" thing because it was a strip of capacitive touch with 5+ LEDs. I don't remember if the p2z worked with the center scrolly or not...
-- Starfox

fortunz said:
I'm going to have to break out the bold, aren't I? I'm not asking for soft buttons. I'm asking that this implementation be flexible enough to allow for future hacks like soft buttons, whether they are your favorite or not. I don't even know if the request is necessary, but I never imagined it would be controversial. If that flexibility really is too complex, forgive the request and ignore it.
Click to expand...
Click to collapse
Alright, settle down children.
I think you're looking a little too far ahead fortunz, but that's just my opinion.
To manekineko - holy crap dude, that was fast! Nice work, definitely want to check it out.
But if you're on CDMA... then I'd imagine the experience is painful with data connected... still, great work. I'm sure the .39 kernel folk will gladly accept your patches, that's seriously cool!

arrrghhh said:
Alright, settle down children.
Click to expand...
Click to collapse
Bu... but... even with the bold starfox still couldn't get it Nevertheless, I am reaching out for my zen.
I think you're looking a little too far ahead fortunz, but that's just my opinion.
Click to expand...
Click to collapse
Fair enough. I was just trying to avoid any potential "now or never" deadline issues.

arrrghhh said:
Alright, settle down children.
I think you're looking a little too far ahead fortunz, but that's just my opinion.
To manekineko - holy crap dude, that was fast! Nice work, definitely want to check it out.
But if you're on CDMA... then I'd imagine the experience is painful with data connected... still, great work. I'm sure the .39 kernel folk will gladly accept your patches, that's seriously cool!
Click to expand...
Click to collapse
Yeah, after I got the .39 kernel, it took me like 30 minutes to get it working for the first time, and then a bit more time to clean up the code to look nicer.
Whereas I'd spent hours banging my head on the wall with .27, never quite sure where the problem was, since I thought I was sending all the right events in the driver. Now I know I was sending the right events (because it works in .39) which means that the problem must have been something in the kernel not passing along the multitouch sync events (I know it's that event missing from debugging the userland). That narrows things down quite a lot, but I don't think I really want to go back and spend the time fixing things up in the obsolete .27 kernel though.

Awesome work Manekineko!
I think the zoom bar code will be a fun addition to future cooks. It will be fun to see what uses people come up with. Be it soft buttons or just a zoom bar. Either way, cool stuff.

There never is and will never be a "now or never" with Android. If you want a feature and it can be coded, take the source and run with it. You may run into walls, and there will be many, but at least you can try - that's the beauty of open source.
-- Starfox

fortunz said:
I assume pinch-to-zoom is pretty well supported in Android. Does this mean the zoom bar is now more supported (for zooming, button hacks aside) in XDAndroid than it ever was in officially baked HTC WinMo?
Click to expand...
Click to collapse
Yes it does
fortunz said:
As for functionality, the p2z is cool, but not something I've been pining for. I don't know exactly what your plans are, but I'd love it if that function could be switched off easily (a line in startup.txt?), so future hacks creating, say, soft buttons on the bar instead could be more easily implemented.
Click to expand...
Click to collapse
Thanks for the suggestion. I'm not going to be implementing it at this time, but the way things are structured in the code, it wouldn't be hard for it to be done by someone interested in the future.
When I was fighting with getting .27 working, I considered at one point simply turning the zoom bar into soft buttons. However, I was never able to come up with a practical use for soft buttons on the zoom bar. The thing that makes it hard is that the list of keyevents Android understand are extremely limited.
You can see for yourself here:
http://developer.android.com/reference/android/view/KeyEvent.html
Set the filter level to API level 8 to see what's available on Froyo. Unfortunately, really useful keyevents like button zoom in/out only became available in Honeycomb (API level 11).
I'm not sure that soft buttons for things like home or power or search would be very convenient when they're not visible on the physical device, are right next to the screen, and could instantly rip you out of what you're doing.
Just in case anyone happens across this that is interested in doing so, here is how you'd probably want to do it:
Android's KeyInputQueue.java, which handles inputs from the touchscreen (and everything else). Do a search for readVirtualKeys and see that it reads from /sys/board_properties/virtualkeys.tssc_manager. Edit the driver so that it generates the virtualkeys file in the format specified in KeyInputQueue, and disable all of the topaz/rhodium zoom bar code.

manekineko said:
the way things are structured in the code, it wouldn't be hard for it to be done by someone interested in the future.
Click to expand...
Click to collapse
Flexible structure is really the only thing I was after. Glad it was already in the plan. And thanks for laying out some possible paths to additional features as well.

Thanks button activated! Great work!
whoops thanked fortunz accidentally -1 buddy

If anybody could find an app that supports touch pressure on a regular kernel on XDAndroid, that would be really helpful. I need to check how much we support pressure to start with and make sure that still is the case with this patch.
I tried Crayon Doodle Lite from the Market, which claims to support pressure, but I'm not seeing any pressure on a regular no-zoom-bar build, so that's not working as a test. Or it may simply be the case that pressure touch has always been broken.

arrrghhh said:
I think you're looking a little too far ahead fortunz, but that's just my opinion.
Click to expand...
Click to collapse
+1
Developing in a way that MAYBE, ONE DAY, SOMEONE, WILL (or just will not) adds unuseful complexity to every software.
BTW: Great work manekineko

Good job, but....
Broke my internet (is zoom tested with gprs or is it CDMA only ?)
Kernel.39+RIL2+F22 is running fine on my R100. After drop in of the Zoom-zImage, connection died.
Without zoom with working connection (SMS error is my operator NOT android):
k39_no_sms_log(537).txt
Zoom added - go to line 552
k39-zoom_no_data(552).txt

[BUILD] **Complete GingerBread Bundle!!** GBX0A - Alpha! Camera!

Please read this entire post!
<<<This is a link to the... FAQ Click it!!>>>​
I have created a complete bundle of GingerBread with the newest kernel from GIT (Feb 28 / 1276), and the newest rootfs from GIT (Feb 24).
Please, feel free to DONATE to the XDAndroid project!
Every little bit helps! We don't make empty promises, we just provide solid and complete builds. No ETA's, no threads without download links or instructions... Enjoy!
Directions:
1. Download the full bundle (zip). (Updated Mar. 11 2011)
If instead you just want the system.ext2 (zip) file (updated Mar. 25 2011) by itself... Don't download this unless you know you want to update!!
2. Extract it. You’ll see a folder, GBX0A, copy its contents to the root (base) of your SD card. If you want to run Android from a folder instead of all the files on the root of the card, follow the steps below.
3. Go into the STARTUPS folder. Grab the appropriate startup.txt for your device (if you don't know what device you have, you should read the FAQ), and move it to the root of the card (or where you run haret.exe from. If you want to change the location of the build, put a rel_path= statement in the cmdline section of the startup.txt. Mine is located two folders deep on the SD, so my rel_path=Androids/TP2Ref)
4. Download the ts-calibration file from this post (should work for BLAC) and extract the .zip to where you run haret.exe from - typically the root or 'base' folder of the SD card. Not within any folders, unless you run haret.exe from a folder!
**If you have issues with the above file, you must calibrate manually. To start manual calibration, just delete any ts-calibration files and boot. Sometimes this doesn't work, and you have to use an older kernel from GIT (I found 1225 works well) and generate the ts-calibration file by booting and pressing the 5 zones. Once you have a good calibration file hold on to it (make 15 copies if it's a really good one ), reboot & go back to the newest kernel from the autobuild service! Thanks**
6. Run haret.exe... Profit!
Let it settle out on the first boot. Many have reported they had to reboot basically because it was so slow - if you let it sit for about 10 mins or so the media scanner can go thru everything, etc. If you want adb in and watch the processes via top, you'll see why the phone seems so slow - there's lots of background processes cranking because this is the first boot .
Troubleshooting:
Please read the... FAQ
If you have any issues with the kernel, feel free to change it:
There are some devices that are having issues with the newest kernels. Please see the kernel autobuild service to get newer or archived kernels. Once you download a replacement kernel, go to where you run haret.exe from - remove your old zImage/modules-xxxxx.tar.gz. Take the new zImage/modules-xxxxx.tar.gz and replace the old ones, same folder - where you run haret.exe from. Make sure the ‘zImage’ is named just that. Do not rename the modules file, do not extract it - should be in .tar.gz format.
In addition, I am using the newest rootfs from GIT - Feb. 10. There are other rootfs options, see F22’s thread if you want to use more keys or move around the home button. Of course, there's always the roofs autobuild service if you want "stock" rootfs images - F22 builds his off of these and modifies them .
See Incremental Updates for more information on this topic of updating!!
Random issues can often be solved by forcing the system to create a new data.img. If you're worried about losing data, Titanium Backup works quite well. If you wish, you can rename the data.img to something else, and let the system create a new one - just to see if it resolves your problem.
Similarly, if you wish try formatting your SD card - I prefer to use the HP Tool - do a full format, FAT32.
Obviously this build is Alpha, and there are going to be problems. The next post will address issues particular to this build - PLEASE READ THESE before asking questions! Feel free to post questions in this thread, I will do my best to address them. Big thanks to stinebd for releasing the system image, and of course the other developers for their hard work on making these kernels available.
stinebd's original post HERE
Mar. 11 2011 Changelog

Things broken in this build:
libgps - explains itself, no GPS and probably no netloc (cell-tower based location)
HW3D is either not working, or just not preset - I ran neocore and let's just say a lot of textures are missing. Got a ridiculous score, but again - no textures, not much to render haha.
This line should be in the startup.txt file if that wasn't obvious .
Thanks to emc02 for that solution!
The keyboard should be fine, but I've had some Blackstone users complain - if you want, switch the keyboard out with another. mr_grisha's original post. Others have said this is a horrible keyboard, and you should just use Swype. I'm a big fan of use what works for you, so you folks make the decision for yourself!
Anything that's broken in Froyo, is probably broken in this build.
Blackstone users - help me flesh out this section! Anything that's not working let me know!

Changelog​ March 25, 2011
Further tuned keyboard sizing to be useful on VGA (also made the key labels bigger)
World-phone settings support (very important for future RIL enhancements especially on CDMA)
Enabled HSPA icon (someone on GSM please let me know if it actually works)

Enabled HSPA icon (someone on GSM please let me know if it actually works).....this does not work on my blackstone.....nor does it work on frx06.......overall gbxoa and frx06 works resonable well.....

Startup.txt that works with frx06 and gbx0a
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2030
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msm_blackstone_pad.vibrate=1 msmvkeyb_toggle=off gsensor_axis=-2,-1,3 msmsdcc_nopwrsave rel_path=GBX0A"
boot
use as "rel_path=*****",where ***** is the name of the folder where haret and other files are located (GBX0A in this example),eg if using stock names use FRX06 for frx06 and GBX0A for gbx0a
sensor rotation should be as it is in the text above
also stock android keyboard doesn't work,and keyboard suggested in first post works a bit crappy (with all due respect),so you should use some other,i personally use swype and it doesn't matter if you swype or just type,because swype is great for typing too,it's fast and responses instantly (unlike betterkeyboard)
i think F22's rootfs are modified to fit rhodium which has keyboard and different button mapping so there is no need to use it...you know,no need for additional code lines which are not necessary
i suggest using zeam launcher it's faster and lighter than the stock one
what else does not work:
led notifications (do not work at all,also if you plug in the cable in WM before you run haret, orange notification(or green if it's fully charged) will continue to glow,so our android has no control over it,not even to turn it off)
front camera
(will add if i remember something)
what works especially good
overall speed and performance is great
the build is stable,i almost never got SOD,sometimes you have to FC apps,but very rarely....anyway, performance mesmerizes you so well that you don't even notice those issues
calls are perfect,no "turn speaker on/off" bug,no rejecting calls
if you want to be able to install more apps,go to this thread and grab the data.img maker (resize tool)
http://forum.xda-developers.com/showthread.php?t=824154
if you need storage access,use wifi explorers,they proved very good solution for not being able to access sotrage via usb

welard said:
Enabled HSPA icon (someone on GSM please let me know if it actually works).....this does not work on my blackstone.....nor does it work on frx06.......overall gbxoa and frx06 works resonable well.....
Click to expand...
Click to collapse
Yea, IIRC the new RIL is required to properly show H. Does it show in WinMo? Thanks for the feedback .
farukb said:
not sure if pmem.extra=1 is needed at all and does it perfor better without it,i read somewhere that it does....maybe arrrghhh knows
use as "rel_path=*****",where ***** is the name of the folder where haret and other files are located (GBX0A in this example),eg if using stock names use FRX06 for frx06 and GBX0A for gbx0a
sensor rotation should be as it is in the text above
i've attached ts-calibration for blackstone,so if anyone needs it,it is precisely calibrated....additionally if someone wants to do it by himself,he (she) should use 11** kernels (current are 13**),because calibraiton feature was removed from later kernels
Click to expand...
Click to collapse
Just saw this. Do I need to change anything in the startup.txt file for Blackstone? rel_path is up to you, pmem.extra is deprecated. Please don't use it - won't hurt anything, but it does nothing .

arrrghhh said:
Just saw this. Do I need to change anything in the startup.txt file for Blackstone? rel_path is up to you, pmem.extra is deprecated. Please don't use it - won't hurt anything, but it does nothing .
Click to expand...
Click to collapse
yeah...i read that...think it was your post i remember you being allergic to that line
that in blue and red was for user who don't know how to do it,just a little hint....also i think provided startup.txt is ok,i just posted this so someone who maybe modified it or lost it can have it easily without having to download whole 120mb package

farukb said:
yeah...i read that...think it was your post i remember you being allergic to that line
that in blue and red was for user who don't know how to do it,just a little hint....also i think provided startup.txt is ok,i just posted this so someone who maybe modified it or lost it can have it easily without having to download whole 120mb package
Click to expand...
Click to collapse
Ah no worries. Let me know if there is something you think I should change, I don't have a Blackstone and I'm always looking to improve the process for you guys!

arrrghhh said:
Yea, IIRC the new RIL is required to properly show H. Does it show in WinMo? Thanks for the feedback .
Just saw this. Do I need to change anything in the startup.txt file for Blackstone? rel_path is up to you, pmem.extra is deprecated. Please don't use it - won't hurt anything, but it does nothing .
Click to expand...
Click to collapse
yes it shows in window....thanks

what else does not work:
led notifications (do not work at all,also if you plug in the cable in WM before you run haret, orange notification(or green if it's fully charged) will continue to glow,so our android has no control over it,not even to turn it off)
front camera
if you use glemsom kernels your audio will stutter a bit,you can overcome this by using g3rm0's kernel found in this forum section....although it'd be nice if someone implemented anti-stuttering into glemsom(xdandroid official) kernels
(will add if i remember something)
what works especially good
overall speed and performance is great
the build is stable,i almost never got SOD,sometimes you have to FC apps,but very rarely....anyway, performance mesmerizes you so well that you don't even notice those issues
calls are perfect,no "turn speaker on/off" bug,no rejecting calls
if you want to be able to install more apps,go to this thread and grab the data.img maker (resize tool)
http://forum.xda-developers.com/showthread.php?t=824154
copied everything to 5th post,so it's all in one place

farukb said:
what else does not work:
led notifications (do not work at all,also if you plug in the cable in WM before you run haret, orange notification(or green if it's fully charged) will continue to glow,so our android has no control over it,not even to turn it off)
front camera
if you use glemsom kernels your audio will stutter a bit,you can overcome this by using g3rm0's kernel found in this forum section....although it'd be nice if someone implemented anti-stuttering into glemsom(xdandroid official) kernels
(will add if i remember something)
what works especially good
overall speed and performance is great
the build is stable,i almost never got SOD,sometimes you have to FC apps,but very rarely....anyway, performance mesmerizes you so well that you don't even notice those issues
calls are perfect,no "turn speaker on/off" bug,no rejecting calls
Click to expand...
Click to collapse
all above quoted the same for me to......sometime loading apps can sometime take time to load and battery life falls quickly when downloading from market.........

farukb said:
also stock android keyboard doesn't work,and keyboard suggested in first post works a bit crappy (with all due respect),so you should use some other,i personally use swype and it doesn't matter if you swype or just type,because swype is great for typing too,it's fast and responses instantly (unlike betterkeyboard)
Click to expand...
Click to collapse
What recommendation do you have? I didn't think Swype was free..?
farukb said:
i think F22's rootfs are modified to fit rhodium which has keyboard and different button mapping so there is no need to use it...you know,no need for additional code lines which are not necessary
Click to expand...
Click to collapse
Probably true, I'll take that part out thanks.
farukb said:
what else does not work:
led notifications (do not work at all,also if you plug in the cable in WM before you run haret, orange notification(or green if it's fully charged) will continue to glow,so our android has no control over it,not even to turn it off)
Click to expand...
Click to collapse
orly... that's an odd bug. It seems that the hardware is not initialized by Android...
farukb said:
front camera
Click to expand...
Click to collapse
I'll add it, but don't expect it to work anytime soon .
farukb said:
if you use glemsom kernels your audio will stutter a bit,you can overcome this by using g3rm0's kernel found in this forum section....although it'd be nice if someone implemented anti-stuttering into glemsom(xdandroid official) kernels
Click to expand...
Click to collapse
I remember this bug, related to the battery code. g3rm0's kernel isn't such a good solution, it just kills the battery provider... I'll see if I can bug a dev into fixing it. Not sure what the actual problem is - does this persist even in the newest autobuild kernels?
farukb said:
@arrrghhh, i think you should remove the sensor rotation part of the post,because could confuse people...but then again you're the boss,so do as you please
Click to expand...
Click to collapse
For the DIAM? Is that not required? Sorry 'bout that. I removed it . I want this to be a Blackstone-specific thread, after all it is in the Blackstone forum. So anything I can do to help newbies with Blackstones is great. Keep up the feedback, and let me know how I can improve!
welard said:
all above quoted the same for me to......sometime loading apps can sometime take time to load and battery life falls quickly when downloading from market.........
Click to expand...
Click to collapse
Yup... apps loading for a while are partially due to the old hardware. Some of it might be the SD card being slow... NAND won't be a ton faster, but should give a little boost.
Battery life falls quickly because the battery driver is inherently flawed. There's some new battery software (SCBS) and it should improve this, but it doesn't seem like it'll be implemented into mainline anytime soon (many devices need support...)

arrrghhh said:
What recommendation do you have? I didn't think Swype was free..?
Probably true, I'll take that part out thanks.
orly... that's an odd bug. It seems that the hardware is not initialized by Android...
I'll add it, but don't expect it to work anytime soon .
I remember this bug, related to the battery code. g3rm0's kernel isn't such a good solution, it just kills the battery provider... I'll see if I can bug a dev into fixing it. Not sure what the actual problem is - does this persist even in the newest autobuild kernels?
For the DIAM? Is that not required? Sorry 'bout that. I removed it . I want this to be a Blackstone-specific thread, after all it is in the Blackstone forum. So anything I can do to help newbies with Blackstones is great. Keep up the feedback, and let me know how I can improve!
Yup... apps loading for a while are partially due to the old hardware. Some of it might be the SD card being slow... NAND won't be a ton faster, but should give a little boost.
Battery life falls quickly because the battery driver is inherently flawed. There's some new battery software (SCBS) and it should improve this, but it doesn't seem like it'll be implemented into mainline anytime soon (many devices need support...)
Click to expand...
Click to collapse
will we see meny of these fixes in frx07 and gingerbread in the next release? (nice to see things are happening here again by the way)

@argh
swype is free,you just need to register and you gain access to swype beta
it's called beta because it is made for devices that don't come with if out of the box and therefore are still developing it,but it works great,nevertheless

welard said:
will we see meny of these fixes in frx07 and gingerbread in the next release? (nice to see things are happening here again by the way)
Click to expand...
Click to collapse
well actually,nothing is happening at all all this is available since march (except for some of the incremental updates which chronologically came out later)

farukb said:
well actually,nothing is happening at all all this is available since march (except for some of the incremental updates which chronologically came out later)
Click to expand...
Click to collapse
what mean is help for making our blackstone run better because there was no one here to tell the problems we face on frx06 and gingerbread......now that arrrghhh is looking into our problems things mite just happen now.........

welard said:
what mean is help for making our blackstone run better because there was no one here to tell the problems we face on frx06 and gingerbread......now that arrrghhh is looking into our problems things mite just happen now.........
Click to expand...
Click to collapse
they might,but arrrghhh is a tester,not sure if he is a dev himself,but he could help pursue devs to do it
as for improvements,very few improvements happened at all over last few months to any device supported by xdandroid project

welard said:
what mean is help for making our blackstone run better because there was no one here to tell the problems we face on frx06 and gingerbread......now that arrrghhh is looking into our problems things mite just happen now.........
Click to expand...
Click to collapse
I was always around, but having dedicated threads in the Blackstone section will help. I tried to get others to create threads to support Blackstone, but I guess no one ever did... So here I am! Trying to support without a device.
If anyone feels like donating a device, it would be much appreciated. XDAndroid will pay shipping if you're willing to donate the device to a dev!
farukb said:
they might,but arrrghhh is a tester,not sure if he is a dev himself,but he could help pursue devs to do it
as for improvements,very few improvements happened at all over last few months to any device supported by xdandroid project
Click to expand...
Click to collapse
This is not true! There's been a ton of development over the last few months... It happens in spurts, but there has been quite a bit.
I'm not much of a dev (played around with init, working on getting rid of manual ts-calibration) but I am 'lead tester' for the project, I maintain the wiki, releases, and track bugs on the bugtracker.

arrrghhh said:
I was always around, but having dedicated threads in the Blackstone section will help. I tried to get others to create threads to support Blackstone, but I guess no one ever did... So here I am! Trying to support without a device.
If anyone feels like donating a device, it would be much appreciated. XDAndroid will pay shipping if you're willing to donate the device to a dev!
This is not true! There's been a ton of development over the last few months... It happens in spurts, but there has been quite a bit.
I'm not much of a dev (played around with init, working on getting rid of manual ts-calibration) but I am 'lead tester' for the project, I maintain the wiki, releases, and track bugs on the bugtracker.
Click to expand...
Click to collapse
i have not a device to donate.....but if we all donate for a device that would speed things up much faster...... i think you should start a new thread for donate for a blackstone device......im sure theres lots of blackstone users willing to do this because the end result will pay off for all of us.......

i had a sod and now i can't boot,the animation just keeps looping...hw buttons vibrate then i touch them,but do not work....power button doesn't work either
happened to me once before,but i don't know what i did to solve it...i maybe deleted the data.img
this time i tried to wipe and format the partition,didn't help
i tried with fresh files (except for the data.img) but still nothing...
@arrrghhh: wanna swap with me for your rhodium,if you want it badly?
@werald and others:if we are going to donate a device,it'd be best to donate it do a dev,maybe stinebd,don't know

What have you noticed better in 4.0.4!!!

I have not received an update but wanted to see what i have to look forward to!!!
I just hope the reboot issue is fixed...
T-Mobile USA
4.0.2

Use search and find out
Sent from my Galaxy Nexus using xda premium

I did not but couldn't find a comprehensive list, just bits of info in many posts.

http://forum.xda-developers.com/showthread.php?t=1481044
Sent from my Galaxy Nexus using xda premium

Thank you!!!

The guy is trying to stimulate discussion on a hot subject. Stop posting links to 2months old and irrelevant (its not the the same update...). Besides, he didnt ask for a changelog... as far as i know..
Personally, the camera is a huge improvement in many ways, browser query delay is faster (definitely, not placebo). I cant say the device is "snappier" since it was already pretty much instant. Also, i used to have a kind of lag while typing text in browser (such as this post), that is also gone now. I did experience a few app crashes though, but i am certajn that its because the custom rom needs work (B29 aokp).
Edit: also, the android OS battery using is significantly less. Of course sampke is smalll but it went from 25% to 4-5%

MatAuc12 said:
The guy is trying to stimulate discussion on a hot subject. Stop posting links to 2months old and irrelevant (its not the the same update...). Besides, he didnt ask for a changelog... as far as i know..
Personally, the camera is a huge improvement in many ways, browser query delay is faster (definitely, not placebo). I cant say the device is "snappier" since it was already pretty much instant. Also, i used to have a kind of lag while typing text in browser (such as this post), that is also gone now. I did experience a few app crashes though, but i am certajn that its because the custom rom needs work (B29 aokp).
Click to expand...
Click to collapse
Honestly, even though it is a 2 month old thread. I read a few bullets on the OP post and most of those changes are relatively accurate on the OTA update released yesterday.
So I don't see what your point is? Even the points you made about 4.0.4 is listed,
Noticeably Faster
Browser performance noticeably improved
Miscellaneous camera UI changes
Click to expand...
Click to collapse

zephiK said:
Honestly, even though it is a 2 month old thread. I read a few bullets on the OP post and most of those changes are relatively accurate on the OTA update released yesterday.
So I don't see what your point is? Even the points you made about 4.0.4 is listed,
Click to expand...
Click to collapse
my point is relatively clear. It is old and this is a new update, you dont know how accurate it is. Besides, his post was more oriented towards a discussion than "please post change logs!!!!!". If you dont like those kind of discussions, fine, but i think its appropriate instead of being an ass about a new thread.

I find nothing wrong with this thread. Who knows what else Google coulda added to 4.0.4 for GSM over the leaked 4.0.4 for CDMA.
Not only are the phones different which can affect things such as reception and radios, but this is much newer and could have additional improvements. No point attaching GSM stuff to an already quite long CDMA change log thread as no one is going to see it.

-Picture quality is definitely improved; likely related to better operation
-Dialer is slightly bigger (?); layout a little different, e.g. settings button at bottom of dialer
-Haven't noted a difference in rotation,
-Backing out of some apps is faster, Play for instance, hit back-back-back and there is no lag migrating back and out of the app,
-The majority of my other observations are likely placebo (i.e. smoother, etc...)

Did google double the storage? Haha.
Iphone. Helping computer illiteracy get popular since 2007.

MatAuc12 said:
my point is relatively clear. It is old and this is a new update, you dont know how accurate it is. Besides, his post was more oriented towards a discussion than "please post change logs!!!!!". If you dont like those kind of discussions, fine, but i think its appropriate instead of being an ass about a new thread.
Click to expand...
Click to collapse
It actually is very accurate. Yes there are some new changes but not many. A lot of the most obvious changes have been pointed out in OP and we can quickly recognize them as we use 4.0.4.
That thread could of been continued on since OP actually had a lot of the points down. Many of the points that people are posting in this thread have been already made in that thread listing changes from a "leaked" build. The same bootloader from that leak made it into the OTA.

Scrolling seems odd in the browser and Facebook at times. Little slow... anyone else notice it?

Sdobron said:
Scrolling seems odd in the browser and Facebook at times. Little slow... anyone else notice it?
Click to expand...
Click to collapse
After 1 or 2 battery pulls that behavior went away for me.

First off, thought I'd let you know I updated with the CWM method. I was 100% stock but unlocked bootloader. Worked fine took 2min to do. One small quip was after my first reboot, I didn't have cellular network connection. Took 2-3 more reboots and lots of toggling to make it work. Now its working just fine.
Here's what I've observed:
1) Power menu sound toggles are nice (50x better if mute actually meant full system mute)
2) Screen shot sound changed to the same as the camera shutter sound
3) Feels snappy!
4) Color fade and transitions (like in menus) are now smooth instead of jittery.
5) Multitasking button has less lag. Definitely not perfect still though.
6) GTalk icon updated to look like Messaging and Google Voice.
7) When you turn the screen on, it fades in a much more pronounced way (imo).
8) Auto-rotate is fast and smooth, although I never found it particularly sluggish before.
9) Other, likely "placebo", effects of smoothness, etc.
developing...

[ROM] VanillaRocket - Mods please close this topic

UPDATE 4
Hello all,
Pending a new release for this ROM, I will stop supporting the "0.3" version originally posted.
I would like some help deciding cosmetics & features next release before it goes live. Please complete the following brief survey:
http://www.surveymonkey.com/s/VJRLWRZ
A lot of fixes and changes have been made and requests have been accounted for as long as they do not deviate from the nature of this ROM being clean, functional, stable, good-looking, and ready to be a base for future devs. The appearance will be very AOSP-ish but with traces of TouchWiz.
Heads up: there will be no XLoud\Beats Audio by default. We have enough audio issues as it is and these are IMHO not any better than using DSPManager (aside from having the cute Sony\Beats branding stamped on them).
I'm not releasing anything until I fix the damn call echo issue ...worst case scenario I will workaround it by keeping Noise Reduction off. But I want to fix it
Q&A: http://forum.xda-developers.com/showthread.php?p=24253640
General questions? post in the above link...it will help me keep track better
^^
I no longer wish to have two seperate topics. So post here...but wait till the next release before you do
First of all, thank you to Racing19969 and anybody else associated with the Skyrocket ICS port...you made this possible.
Also want to thank CyanogenMod (<3) and the original author of DSP Manager (will find credits tomorrow) from which I borrowing DSP Manager for this ROM
The goal: to make a CLEAN, no frills alien TouchWiz + ICS rom. Its not meant to be exciting or have a crazy amount of hacks in it. In fact as of right now, the only packages added from the community are SuperUser and DSP Manager. And I don't plan on changing that.
Current status is...the ROM is running and its running QUICK. But there are some minor issues to be worked out and some beautification to be done.
The priorities:
Stability
Friendliness
Battery Life
If you are going to comment without constructive criticism, then just look away from this thread. The ROM is what it is. If you are going to install it, I would appreciate pointing out as many bugs as you can
For right now (temporarily): I did add the wonderful, feather-weight Zeam Launcher alongside TouchWiz...this is because I had issues with TW force closing on me early on in the modification process. So until more progress is made on this ROM, I've decided to keep it in there in such an event that TW decides to be unhappy and constantly force close.
A *lot* of bloatware was removed, especially from AT&T and some of Samsung's own social/media/diary/etc packages. I want this ROM to be STABLE, fast, and clean.
Next release ETA:VERY VERY SOON. NOW THAT AUTO ROTATE WORKS :-D
That being said, there are still issues to be worked out. Here is the list of changes made right now:
Added DSPManager from update-cm-9-20120330-NIGHTLY-galaxys2-signed, not functional ATM
Added Gallery, Mms, and Shutdown from GT-I9100 XWKI4 ROM; This fixes the shutdown issue, the Gallery landscape resize issue, and the delete SMS thread FC issue
Also added Browser from GT-I9100 XWKI4 ROM; not only is it more stable but the Search icon is fixed in its place and it has more features
Added apns-conf.xml from above CM9 nightly
International Galaxy S2 boot animation (AT&T anim is hideous)
Removed many many bloat; I'll try to compile a better list later
Added latest version of Polaris Office from T-Mobile ROM...It's a simple, lightweight, and pretty good doc editor/viewer
Already rooted
TODO:
Merge racie's unsecure Skyrocket Kernel COMPLETE
^^ Transform samsung boot animation to a ZIP to work with above kernel
Remove traces of Software Update COMPLETE
Put back the 2G - 3G / band select setting in our Settings menu Priority
Identify as SGH-T989 in build.prop
Removing AT&T contact sync wizard from Contacts.apk, also restore Contacts to the dialer tabs IN PROGRESS
Revisit shutdown issue IN PROGRESS
CWM flashable patch for the Skyrocket folks
Remove AT&T VM icon in Phone dialer
Fix T-Mo Voicemail indicator SMS Priority
Fix Auto-Rotation (perhaps by modifying Framework \ WindowListener) FIXED FOR NEXT RELEASE / PATCH AVAILABLE NOW
Remove remaining traces of AT&T Bloatware
Modify TouchWiz default home screen XML so that widget_service_v0.1.4_shared.apk can be removed from the system/app folder entirely prior to emptying the home screens COMPLETE
Remove debugging / service testing apps
Wi-Fi calling for T-Mobile
Change ugly status bar icons to stock ICS style; remove AM/PM indicator, and remove carrier label from status bar itself IN PROGRESS
Optimize PNGs, zipalign
Call echo and RIL issues; improve call quality IN PROGRESS Priority
Add quick toggles due to demand IN PROGRESS
Set up bug tracker website
Default Market to Play Store
A "Tweaks" menu to make some important modifications but without necessitating manual editing or downloading a lot of stuff from Market
PRIOR TO INSTALLING: Make sure you superwipe with DARKSIDE's SUPERWIPE script.
And finally...
the link (flash with CWM):
http://dl.dropbox.com/u/50663221/CleanICS0.3.zip
MIRROR:
http://www.4shared.com/zip/9iWiyyMY/CleanICS03.html
Thank you to markusf21 for providing the above mirror. Bandwidth costs money, so please give this user a thanks!!
PS, my personal opinion...install the Telus radio. no echo issues thus far. But if you don't know what a radio is....don't do it.
Update: I have big suspicions that this is a RIL or qualcomm audio config issue. It is now the priority problem which I will look to tomorrow..

Enjoy
Update coming tomorrow..
For today I am tired!

Hopefully I can get this one to boot. Raver's just gives me booltloops to eat. We'll give this a run. I'll report back.
Edit: booted right up and is going well. Nothing too crazy yet. Will keep you posted.
Youtube played well and video was right on. I could actually hold it in landscape and watch video with not much effort.
>>DARKSIDE

the first boot may take a few min as this is Deodexed
Also, nice to see a fellow P999er here

I have been running the port for the past 3 days and the only issue I have is the rotate and I know that's a kernel issue but that port took many flashes and reboots. Let's see if this one is easier to install and I'll report later.
Edit : I always use darkside wipe just like on my transformer there some kind of wipe just like it and I'm so glad that the gs2 has it too.
Sent from Samsung Galaxy S II

It's important to to siperwipe. Darksides script works perfectly everytime, but prior to using it it took me many attempts to flash the leak. I am looking into hacking usermode android into invertig the kernels auto rotation parameters. Dirty hack but I believe it is possible

by looking at the change log I think you are on the right track! I do have one question, on the ics skyrocket leak, I noticed there is a lot of freezing and watching streamed videos is damn near impossible it lags beyond belief, so I was wondering if you had a chance to take a look at some streamed videos.
Sent from my SGH-T989 using XDA

Have not tried any streaming but youtube...youtube works well
Edit: HQ working perfectly on youtube as well

Link is down now can anybody mirror?
Sent from my SAMSUNG-SGH-T989 using xda premium

Somebody offered me to mirror via PM. I just asked him to help me out
Edit
much gratitude to markusf21 for helping me out
Link coming in 15min
MD5 sum: d5206397a40483cd017e3c3295f8a1c3

It really works well ty. One question the ics youtube is ridiculous is it possible to bring back the GB app?
Sent from my t989 --- SAMSUNG-SGH-I727 using XDA

Any chance we can see some ROM screenshots of changes?

Dead link can you please provide a mirror

Mirror on the way...
Screenshots I will try my best to do tonight, although I do not think I can until tomorrow (~12 hours from now since we're all in different timezones)
I'm not into any drastic theming, so there is not much specialty here. I like clean and simplicity....I cannot BELIEVE AT&T and Samsung even plan on releasing the current ROM they have for Skyrocket. It's bloated to hell.
EDIT:
If anybody can confirm the following MD5 with the mirror:
d5206397a40483cd017e3c3295f8a1c3
I appreciate it. I just want to make sure I calculated the right one and that the mirror is also the same.

raycaster3 said:
Hopefully I can get this one to boot. Raver's just gives me booltloops to eat. We'll give this a run. I'll report back.
Edit: booted right up and is going well. Nothing too crazy yet. Will keep you posted.
Youtube played well and video was right on. I could actually hold it in landscape and watch video with not much effort.
>>DARKSIDE
Click to expand...
Click to collapse
How did u get youtube in landscape? I have the hacked hd ics youtube pushed into system apps . It works great but no landscape.....is it the youtube that comes with the rom? Oh and for a camera fix use camera zoom fx... it will actually show pics the right way in gallery and send to people the right way too. For portrait shots just hit menu and rotate once

sarni84 said:
How did u get youtube in landscape? I have the hacked hd ics youtube pushed into system apps . It works great but no landscape.....is it the youtube that comes with the rom? Oh and for a camera fix use camera zoom fx... it will actually show pics the right way in gallery and send to people the right way too. For portrait shots just hit menu and rotate once
Click to expand...
Click to collapse
Well since our auto rotate is broken, I just turned it on and physically put the phone in portrait mode. LOL
And agreed at Camera Zoom FX. Like it a lot. If the autorotate fix doesn't work out, I will compile an ICS camera locked to landscape mode**.
@Skorpion_
I will look into it, hopefully in the next 24 hours.

yaldak said:
Mirror on the way...
Screenshots I will try my best to do tonight, although I do not think I can until tomorrow (~12 hours from now since we're all in different timezones)
I'm not into any drastic theming, so there is not much specialty here. I like clean and simplicity....I cannot BELIEVE AT&T and Samsung even plan on releasing the current ROM they have for Skyrocket. It's bloated to hell.
Click to expand...
Click to collapse
No worries man take your time you earned it buddy!!
Sent from my SGH-T989 using XDA

sarni84 said:
How did u get youtube in landscape? I have the hacked hd ics youtube pushed into system apps . It works great but no landscape.....is it the youtube that comes with the rom? Oh and for a camera fix use camera zoom fx... it will actually show pics the right way in gallery and send to people the right way too. For portrait shots just hit menu and rotate once
Click to expand...
Click to collapse
I started the video then turned on screen rotation then held in vertically and slowly moved to horizontal and voila. I used the YouTube app that came in the rom.
The only real gripe I have right now is that the sideways scrolling16 panel toggle (thanks lidroid & RaverX3X) and the folders ui in gtab simiclock is pretty sticky, from lack of a better word. I'm sure it's due to the rotation issue. Looking good so far. Adwex hauls ass on this rom.
Oh yeah and vignette is great for pics too, alas youbhv to go into gallery and rotate them. Snaps em quickly tho. No delay like the stock camera.
>>DARKSIDE

raycaster3 said:
I started the video then turned on screen rotation then held in vertically and slowly moved to horizontal and voila. I used the YouTube app that came in the rom.
The only real gripe I have right now is that the sideways scrolling16 panel toggle (thanks lidroid & RaverX3X) and the folders ui in gtab simiclock is pretty sticky, from lack of a better word. I'm sure it's due to the rotation issue. Looking good so far. Adwex hauls ass on this rom.
>>DARKSIDE
Click to expand...
Click to collapse
Ok gotcha now...

if this is from ics leak from our skyrocket then im just gonna flash this .. it'll make life easier since somethings like rotation issue won't be there haha.. good job dev. and will wait for your update..
edit: also if u need a theme im working on fully revamped ics theme which will blow minds let me know im on i727 forum

Bug & Issue Tracker for greatergood's i927 - CM10.1 ?

Seems like i am notallowed to post in the development threads yet. Sigh.
Anyhow: I've been using thegreatergood's CM10.1 ROM for a while now, and love it.
I am glued to its corresponding development thread, always looking for updates and workarounds for the few bugs that remain - but i think it is a bit cumbersome. Issues get repeated, some get lost along the way, and a couple of answers are hidden between a couple of other unrelated posts.
Wouldn't it be neater to have a 'real' issue tracker for this (and any other, for that sake) ROMs? Does XDA offer something like this? Could that be hosted somewhere else?
Anyhow, my issues so far:
- Bluetooth Headset profile
- Audio in video recording not working
- Photosphere unavailable
- audio stutters if screen is turned off (seems to be a CPU sleeping issue)
- Something (i am suspecting Google+, even though i am not actively using it) is filling up my SD card with gigabytes of thumbnails, which i have to delete manually
- lockscreen takes too long to appear
- from 4.2.1 to 4.2.2 the mount point of the external SD card changed again (so 'acast' cant find my downloaded podcasts)
- auto-brightness is choppy and slow
- GPS usually get a lock in an okay-ish timeframe, but always reports that it's only locked to "0 / 2 satellites"
- face unlock doesnt work (hangs when opening the camera)
That's all i can think of right now.
Still an awesome ROM,
M.

mschweini said:
Seems like i am notallowed to post in the development threads yet. Sigh.
Anyhow: I've been using thegreatergood's CM10.1 ROM for a while now, and love it.
I am glued to its corresponding development thread, always looking for updates and workarounds for the few bugs that remain - but i think it is a bit cumbersome. Issues get repeated, some get lost along the way, and a couple of answers are hidden between a couple of other unrelated posts.
Wouldn't it be neater to have a 'real' issue tracker for this (and any other, for that sake) ROMs? Does XDA offer something like this? Could that be hosted somewhere else?
Anyhow, my issues so far:
- Bluetooth Headset profile
- Audio in video recording not working
- Photosphere unavailable
- audio stutters if screen is turned off (seems to be a CPU sleeping issue)
- Something (i am suspecting Google+, even though i am not actively using it) is filling up my SD card with gigabytes of thumbnails, which i have to delete manually
- lockscreen takes too long to appear
- from 4.2.1 to 4.2.2 the mount point of the external SD card changed again (so 'acast' cant find my downloaded podcasts)
- auto-brightness is choppy and slow
- GPS usually get a lock in an okay-ish timeframe, but always reports that it's only locked to "0 / 2 satellites"
- face unlock doesnt work (hangs when opening the camera)
That's all i can think of right now.
Still an awesome ROM,
M.
Click to expand...
Click to collapse
I concur, we need a bug tracker. Although I mentioned this in the dev thread, my concern seems to have fallen in deaf ears. No one replied to my post
http://forum.xda-developers.com/showpost.php?p=37566415&postcount=95

Well, I'm in the same boat where I can't ask in the official thread so I can't ask my questions there. Lame.
Under the "working" part, it lists:
- Keyboard Keys
- Keyboard Rotation
- Virtual Keyboard (no slide yet though)
I don't fully understand what that means, and it sounds contradictory. Does the physical slide-out keyboard work or not? Its the main reason I bought this phone, so...

snarfies said:
Well, I'm in the same boat where I can't ask in the official thread so I can't ask my questions there. Lame.
Under the "working" part, it lists:
- Keyboard Keys
- Keyboard Rotation
- Virtual Keyboard (no slide yet though)
I don't fully understand what that means, and it sounds contradictory. Does the physical slide-out keyboard work or not? Its the main reason I bought this phone, so...
Click to expand...
Click to collapse
I think it means swype does not work yet bro. Has nothing to do with physical keyboard as it says clearly "virtual keyboard".
Sent from my SGH-i927 using xda premium

i agree we do need a bug tracking thread ... i'm to busy to do it myself .... are any of you interested ..

thegreatergood said:
i agree we do need a bug tracking thread ... i'm to busy to do it myself .... are any of you interested ..
Click to expand...
Click to collapse
I would be very happy to help out!
Any preferences? Or are you using e.g. github already?
M.
UPDATE: maybe we can (ab)use XDA's wiki funtionality for this? XDA should really offer an issue tracker...

Great idea. Wish I thought of it before.
I have started a brand new bug tracker thread in the general section. Feel free to post all issues and problems there. I will update the OP accordingly.
Class now, will update in a few hours!

I was thinking more of a full-blown bug tracking system, which would also help all the other ROMs. But lets five this a shot...

mschweini said:
I was thinking more of a full-blown bug tracking system, which would also help all the other ROMs. But lets five this a shot...
Click to expand...
Click to collapse
Honestly, I'm not that sophisticated. If you can, that would be great. In the meantime, we have this :good:

No worries - wouldn't be that hard to do it in a 'pro' fashion.
But: IIRC, XDA has some policy of not linking to 'competitors' websites? I might be very wrong, though!
Could any mod confirm or deny this? Could we just say "go to example.com/CM10.1" to register bugs and issues?
Also: If thegreatergood already uses some (online) source control system (e.g. github), bug tracking would be a lot easier?
Cheers,
M.