Develop Bugs

[SOLVED] Flashing Service LED

Well I have searched and searched and can not seem to figure out how to disable the service led without disabling all the functions of ALLledmgr. Of course that works but that means vibration and a number of other things. Someone had mentioned the nled reg entry hack tried that no luck. I have looked through countless dlls and files for any reference that might come close to disabling the service led but I just cant seem to find it. So many other phones(cheap phones) let you disable it why cant this one?
I remember back to a simple hex edit on my motorola that could do many things we even had script files that could change the leds colors etc and do crazy things on boot etc(that was linux of course).
So any of you pros out there came across anything that might be related to the service led?

i love the service LED's if it werent for them i wouldnt like my TyTN as much .. they really mean that much to me
sadly we're not in the good ole' motorola days (that was bliss) but i have the perfect soloution! :
Get a black permanent marker, and colour in the Service LED
et voila!! it no longer flashes and you still have vibrate, sounds etc ...

LOL

That´s was a really tip problem solution !!

Service LED does not bother me at all.

Or gently mash it with a sharp knife or screwdriver. (same solution for that silly light/speaker on cars that warn you to put a seatbelt on)

Maybe I wasnt clear about what I wanted. When I meant service led I meant that it just constantly flashes green to tell you that you have a signal. I want my leds to work, but the way I want them to. I want them to flash when I have a missed call or unread message etc. I just do not want it to constantly flash green in a service area Im always in a service area.
Many of you laugh of course and say it doesnt bother you etc. But I bet that when it is figured out where and how it is access and then being able to customize it change its colors etc, those who laugh will also be among the people using those nifty custom leds(blue for bluetooth,green for message,orange for missed call etc. So try and support the idea instead of laughing at it.
For me seeing that green flash over and over is just a constant reminder of something I can not customize on my super customized phone.
Psiodon

Psiodon said:
Well I have searched and searched and can not seem to figure out how to disable the service led without disabling all the functions of ALLledmgr. Of course that works but that means vibration and a number of other things. Someone had mentioned the nled reg entry hack tried that no luck. I have looked through countless dlls and files for any reference that might come close to disabling the service led but I just cant seem to find it. So many other phones(cheap phones) let you disable it why cant this one?
I remember back to a simple hex edit on my motorola that could do many things we even had script files that could change the leds colors etc and do crazy things on boot etc(that was linux of course).
So any of you pros out there came across anything that might be related to the service led?
Click to expand...
Click to collapse
try this out

Wow the attatched file actually worked! Still maintain all other functions with only the service led disabled. Im going to start ripping it apart and see if I can come up with anything new.
Thanks much for finding it, making it, or whatever, hats off to you.
Psiodon

Psiodon said:
Wow the attatched file actually worked! Still maintain all other functions with only the service led disabled. Im going to start ripping it apart and see if I can come up with anything new.
Thanks much for finding it, making it, or whatever, hats off to you.
Psiodon
Click to expand...
Click to collapse
that one was too early. it has a bug when charging. i have a 3.1 version that reads if the charger is on and works better. if you want it let me know.
this 2.1 version is the one i use.

codyppc said:
that one was too early. it has a bug when charging. i have a 3.1 version that reads if the charger is on and works better. if you want it let me know.
this 2.1 version is the one i use.
Click to expand...
Click to collapse
Please do post the 3.1 verison and thanks

The first one you posted seems to e 3.0 the second 2.1, ill try it to see whats the difference but 3.0 works fine even when charging except it gives you a flashing orange led instead of constant on led, letting it charge to full and see what happens. Yes please post any versions you have so I can try to see the different modifications they are doing between them.
I can see that it is simply using a mort script to scan the notification que for changes and using the treo exe to make modifications. Im in the process of decompiling the treo exe to see what mods can be made.
My concern here(which may be a retarded one so small) that you have a fight going on with the phone constantly telling it to do one thing and the mortscript and treo exe telling it to do something else. I can see that mortscript is using about 3%cpu cycle every 5 seconds or so. Not sure if that is going to impact battery usage or not, but my end goal would be do away with the fighting and just having the os do what its supposed to do.
Psiodon

I would like to request that anyone who likes or uses this app please stop by thier forums and send a thank you. After reading through all the threads they put alot of time and effort to make it work. And although it was not designed for our phones by chance it works. I have already sent my thank yous and hope more will do the same.
http://discussion.treocentral.com/showthread.php?p=1313922#post1313922
http://pdaphonehome.com/forums/ppc-6800-xv6800/89656-led-killer-3-1-a.html

BobbyK said:
Please do post the 3.1 verison and thanks
Click to expand...
Click to collapse
i put 3.1 in place of 3.0
i still think 2.1 is better. still work in progess.

fixed it myself

latest version installed working good no problems
Psiodon

@psiodon: Did you do any "re-work" on it? If yes, could u please attach here so everybody can benefit?
Thanks
Chris

No I have not done anything at all since it is already functional, what I am currently looking into is the other three leds that we have and what can done with them. Im also trying to figure out more info on our leds, if they are only tri color, etc and if its possible to get our two green and red phone leds blinking as a notification as well, but I am pretty sure those two leds are controlled together as on or off and probably cannot be controlled individually, time will tell.
Psiodon

Did this work on HTC Artemis (o2 Orbit) too?

Thank you!
Just a quick note of thanks to CodyPPC for the link!
That damned service light has been annoying me for months - I've taken to putting the phone in a draw / turning it upside down to stop the flashing annoying me when trying to get to sleep in an otherwise totally dark room!
This was the 1st site to come up on a google search - and am really impressed - cheers!
I'll send thanks to the devs on the other forum as well.
It looks like you're looking to enhance/fiddle with this further - controlling the LED's in various ways - - have you made any progress? are you in a position to share any code (compiled/source) or tips? I just want to dabble - have no real goal in mind - -- - the main thing is no more flashing green!!! woo!

I'm getting more and more pissed off with my Desire

Now I find out I cant even set an animated gif as a wallpaper.
For all this **** this phone can do there seems to be SOO much it can't do.

It's 'the new way forward' Be glad you don't have a device that starts with an i ... Even more restrictions and things it can't do.
On the other hand, who wants ugly old obsolete animated gifs as wallpaper anyway? Android allows for much much better and nicer wallpapers.
But oh well, it's all personal eh. So far I didn't run into anything the Desire couldn't do when I wanted something done... no.. NO! That's not entirely true, I want to use my Desire as a bluetooth keyboard for my PS3. It can't do that ... YET!

oursol, I have to agree with RaptorRVL - who nowadays would want to set an ugly looking pixelated, repetitive gif animation for background? We have muuuuch better Live wallpapers!
RaptorRVL ... bluetooth keyboard... I can only add a finishing YET to your post They got android on a f...n washing machine!

Okay, agreed.. but I am finding the little things just a little bit annoying so I needed to rant.
Is there a way of converting animations (flash or gif) to a live wallpaper?

tbh I feel your pain oursoul.
I've been looking at modding the Desire with themes, and icons etc. and I've pretty much hit a brick wall. While this phone is good for Dev's and people seriously into computing, to someone like me, whos wizo on photoshop but not into cmd:// stuff i'm finding this phone pita. The iPhone was much easier to fiddle with.
and I never thougtht I'd say that.
simples
Jailbreak, EXE, follow instructions, done
OpenSSH, find files, edit, compile into folder.
Open Winterboard, tick theme, Restart springboard.
Done
Android
Root phone, follow long drawn out process, upposed to EXE
At this point I'd had enough, frankly bricking the Desire, isn't worth it, and by what i've been told so far, making a theme will require java coding, and repacking into a APK.
tbh I'm seriously considering a iPhone 4, the only thing keeping me on the Desire is the idea of 2.2 with flash 10.1 if it doesn't show up, i'll be off.
so yes oursoul, I understand your frustrations completely...

U can install skins with metamorph MUCH easier than winterboard u can NeVER say that theming and editing of the phone in iPhone is easier than in Android thats just stupid!very stupid!

RaptorRVL said:
It's 'the new way forward' Be glad you don't have a device that starts with an i ... Even more restrictions and things it can't do.
On the other hand, who wants ugly old obsolete animated gifs as wallpaper anyway? Android allows for much much better and nicer wallpapers.
But oh well, it's all personal eh. So far I didn't run into anything the Desire couldn't do when I wanted something done... no.. NO! That's not entirely true, I want to use my Desire as a bluetooth keyboard for my PS3. It can't do that ... YET!
Click to expand...
Click to collapse
lol, I haven't found 1 live wallpaper out of the 30 I have tried which hasn't
lagged the hell out of my phone. I don't know weather it's simply bad coding
or what - but for now, live wallpapers are simply unusable for me.
(this is also with the processor at 1200mhz)
hopefully with all the claimed performance enhancements found in froyo however, the desire will handle them better

ill try metamorph out, but what i'm saying is from a n00bie, position is i'm trying to add to this community with themes, etc but i can't find out jack and when i do people tell me i've got to go routing through the guts of the phone, which i don't want to be doing, if i'm wrong, and it's not that involved i retract my previous statement, but at the moment i'm not getting very far, and thats not from a lack of effort.

Live wallpaper work fine for me at 1ghz! No lag at all.
On the subject of theming. Why not use an alternative home? Freedhome allows for a LOT of customization.
What exactly would you change? There are a million homes that change the look and function of the bottom bar. Wallpapers obviously you can change. There isn't much to change really.

diablous said:
ill try metamorph out, but what i'm saying is from a n00bie, position is i'm trying to add to this community with themes, etc but i can't find out jack and when i do people tell me i've got to go routing through the guts of the phone, which i don't want to be doing, if i'm wrong, and it's not that involved i retract my previous statement, but at the moment i'm not getting very far, and thats not from a lack of effort.
Click to expand...
Click to collapse
Give it time... it'd be crazy to do too much skinning just yet because who knows the full impact of the coming OTA on Sense.
I'm also a noob on android... so there's much to learn.

well all the icons would change the wallpaper obviously, colour scheme, probably even audio too to suit the theme. I want to complete skin the OS.
I've just managed to root the desire, got the SU icon on the menu. and i'm now trying to work out how to access the phones internal files?

ephumuris said:
Live wallpaper work fine for me at 1ghz! No lag at all.
Click to expand...
Click to collapse
i conquer, maybe lag issues are down to branded phone bloatware

Sorry to jump on the post but I am have an animated gif issue too:
I can't play them in a web browser, I have tried the built in browser, opera and dolphinHD but they just wont play. I am sure I read somewhere that 2.1 gives this functionality, yes I know some of you may say why would you want to play them anyway but this is old and basic functionality that I could do years ago on non smart phones.
Is it just my Desire that is at fault?

diablous said:
ill try metamorph out, but what i'm saying is from a n00bie, position is i'm trying to add to this community with themes, etc but i can't find out jack and when i do people tell me i've got to go routing through the guts of the phone, which i don't want to be doing, if i'm wrong, and it's not that involved i retract my previous statement, but at the moment i'm not getting very far, and thats not from a lack of effort.
Click to expand...
Click to collapse
That's what I've felt like as well, coming from an iPod touch I expected Android to be like an already jailbroken iPhone, turns out it's not that easy and there is a lot of stuff you just can't do. I am very tempted to get an iPhone 4 for other reasons as well, such as the fact that this phone is terrible as a media device.

I agree. For an open os and 1ghz, there seems to be alot it can not do with this phone. I cant use total recall to record calls what even my old nokia could. I can not use an screenshoot app without rooting the stupid thing. I can not record video with smooth fps. I can not play divx/xvid out of the box like with samsung spica. This are just some things im missing.
The live wallpaper do slow down my unbranded phone also. This isnt free on the cpu and battery either.

Just a suggestion...
Why don't you stop whining and next time before you buy a phone - research it and find out if it does what you need it to do! There is no point in *****ing in here. Coming from an iPod Touch user (mainly as a PDA) I AM IN HEAVEN WITH MY DESIRE AND I WOULD NEVER LOOK BACK!

xtcislove said:
U can install skins with metamorph MUCH easier than winterboard u can NeVER say that theming and editing of the phone in iPhone is easier than in Android thats just stupid!very stupid!
Click to expand...
Click to collapse
... Very Very VEry VERY stupid! Completely agree.

diablous said:
well all the icons would change the wallpaper obviously, colour scheme, probably even audio too to suit the theme. I want to complete skin the OS.
I've just managed to root the desire, got the SU icon on the menu. and i'm now trying to work out how to access the phones internal files?
Click to expand...
Click to collapse
It sounds more like you're just expected something to be simple and getting in a huff when it's not. Rooting is quite straightforward (easier on the Desire than the Hero in my experience say) if you can follow instructions and copy and paste.
But anyway, now that you have rooted. Go into recovery, use adb and pull '/system/framework/framework-res.apk', extract that, play around with it (change graphics and what not, but be careful and make sure you backup your original framework-res.apk file), repack the apk (it's just a signed zip - it might not even need signing) and push it back with adb. I warn you, I've not actually tested this myself but give it a go.
I'd make a nandroid backup before to be on the safe side (worst comes to worst you'd have to flash a new rom). If you didn't understand anything I said then look it up as I only know it from reading it.
Good luck, Rowan.
Edit: I just tried this to edit my alarm icon and confirm it doesn't need signing.

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

[DEV][CDMA/GSM] Group Effort to Optimize Existing HoneyComb Ports

Full credit goes to Ssserpentine, SpaceMoose, and OldMacnut for their work on their united efforts to port Honeycomb to our tablets! It seems they are no longer working on it so I decided to create this thread and see what we all could to do together to improve what they have given us!
The point of this thread is to find ways to gather anyone with knowledge on developing, even if its just the "lowly 7-Zippers" like me, to see how we can remove minor bugs and small issues from the ROM. I know Oldmacnut was going to pick it up, but he has a lot on his plate right now and he has been in pain and is more interested in finishing the CM7 Port instead. I respect his decision, but so many people want honeycomb working on our tabs. So I am turning to the dev community here to see if we can group together and fix things in this rom together. If we cant solve the major bugs, lets address all the little things, cuz the little things add up.
Spacemoose made a list of suggestions from users earlier on how to solve minor issues, and little workarounds, but I would like to see if there is a way to roll up those fixes into one full updated ROM flashable through a zip/odin/heimdall file, and see if we can come up with more. You can see this post here, but I have added them to the second post as well in a more organized form.
Some Useful Links as Well:
SpaceMoose's Github
6-19-11 Apps Confirmed Working on [CDMA] / [GSM] Honeycomb Alpha 2.5
Currently Known Bugs:
CDMA
A) Red Border Around Screen at Random Times
B) Constant Gallery Force Close
C) Stock Launcher hangs for many seconds at a time randomly
D) SD Card Does Not Mount
E) Youtube app does not work
F) Orientation Sensor is not functional
G) Honeycomb thinks Device Keyboard is enabled by default
H) When pressing Quick Settings, an image that is semi transparent that is supposed to cover the entire screen isnt scaled properly
I) HQ Youtube does not work (LQ does on the mobile site)
J) Quick Settings Shortcut on Bottom Right Side (Wi-Fi Toggle, Brightness Slider, etc) appears for a second but disappears afterwards.
K) Flash Player is not Fully Functional
GSM - Please Submit or confirm if the above bugs are the same and/or you have different ones!
Red - Signifies an issue that is unaddressed or has not been solved yet.
Orange - Signifies a Temporary Fix or Workaround is mentioned in the post I linked to.
Blue - Will signify a temporary fix or a work around that we have been able to include in a flashable file
Green - Will signify a bug that has been completely fixed in a flashable file.
------------------------------------------
Lets put our minds together and see what we can do guys! Btw this was inspired by Rodderik's thread [SPRINT][CDMA]Galaxy Tab (SPH-P100) Mega Development Starter Thread (CWM, EF17 TAR), so if youre interested in this, you might like his thread too!

Current Workarounds/Temporary Fixes:
Letters correspond to the bugs listed in the OP.
A)
Ssserpentine:
1) Open up Dev Tools
2) Go to Development Settings
3) StrictMode Visual Indicator - turn it off
4) back out of app and now open it again.
5) If this doesn't get rid of MOST of the red borders, REBOOT and open app again.
Click to expand...
Click to collapse
B)
anfalas:
"Get Gallery3D to play nice by going into settings, applications then 'Clear Data' - works great, can change wallpaper etc. Only downside is it has to be done each reboot....."
Click to expand...
Click to collapse
C)
Ssserpentine:
“WANT IMPROVED UI, LESS RED BORDERS, LESS FC'S AND SCROLLING AND SOFT KEYS THAT PLAY NICER? Try adw launcher. for some reason just having it installed helps just as much as using it.”
Click to expand...
Click to collapse
D)
mattman83:
"to mount UMS if you have no external SD then use the below line. Same changes as above... echo /dev/block/mmcblk0p1 > /sys/devices/platform/s3c-usbgadget/gadget/lun1/file"
Click to expand...
Click to collapse
or
corodius:
"if you have an external sd, by extending the commands to: su mount -t vfat /dev/block/mmcblk0p1 /mnt/sdcard/ mount -t vfat /dev/block/mmcblk1p1 /mnt/sdcard/external_sd/ This will mount the cards the way they are originally mounted in the samsung/overcome roms."
Click to expand...
Click to collapse
E)
Use m.youtube.com to play LQ videos
Click to expand...
Click to collapse
F)
ztag100:
"If you download barcontrol from the market, you can set it so that a notification links to the rotation app, thus when the notification is clicked it will change the orientation."
Click to expand...
Click to collapse
G)
"one way to load keyboards On the language/keyboard settings page, turn physical keyboard to "no" or "off" or something like that. Now when on a text field, you should see a small keyboard tray in bottom right corner.."
Click to expand...
Click to collapse
H) ---
I) ---
J) ---
K) ---
----------------------------
Submit a New Bug or Fix:
Please submit bugs using the color coded system I explained in the OP. If you are submitting information on solving a bug please address the bug by the corresponding letter so that we can stay organized and know what youre talking about. If you have a new bug please check the OP to make sure I havent listed it, then post it on here and dont worry about the letter, I will alphabetize them. Of course I will credit you in the OP for any fixes or workarounds you may find! Good luck to us all!

Reserved as well!

Yes, please
I would really love a Honeycomb ROM for the Galaxy Tab. There are many reasons why I want to put Honeycomb onto the original Galaxy Tab.
Just see the difference for yourself: Blank space, single pane, one-category-at-a-time menus in Gingerbread
VS.
Less blank space, concise, dual pane interfaces in Honeycomb.
Gingerbread apps are just designed for smaller smartphone screens, so they look too big and spaced-out on the 7-inch Galaxy Tab for my taste. I would really love to see some tablet-optimized apps on the Galaxy Tab!
-------------------------
And yes, I respect the developers and appreciate them so much for the time they put into making custom roms a reality for us!

Please make the thread for GSM also.

TheATHEiST said:
Please make the thread for GSM also.
Click to expand...
Click to collapse
Are the bugs the same? Or are there others that I havent mentioned? I will try to make a section for both tabs if theres different bugs in each one.

Why no mention of ssserpentine?
In op or thread tittle?
He worked on the GSM version.
Moose did the major part of the port and the cdma version.
That other person stumbled, or so he claims, on a audio fix. Never saw a release of this apparent audio fix.
Wonder how many donations he got on open thread with no release posted.
Hmm.
Makes ya wonder why that thread is even there.
Dole out the credits properly.
Just know it needed to be said, and go ahead and get mad. Truth hurts.
alot of angry responces coming, maybe, but dare ya to point out a single lie in this post. Even an exaggeration.
Moose did hc for MONTHS and noone offered any valid help, except ssserpentine, why do you think anyone is gonna get off their but now?
Why don't you, punkrock?
Cause I know how utterly hopeless this task is.
Why don't you all just wait for the leak of the next os?
That so much closer than some random Joe, or Joe's on xda getting hc ported at this point .
is the dead horse braised yet?
Still, hope is eternal, I suppose

PunkRock said:
Why no mention of ssserpentine?
In op or thread tittle?
He worked on the GSM version.
Moose did the major part of the port and the cdma version.
That other person stumbled, or so he claims, on a audio fix. Never saw a release of this apparent audio fix.
Wonder how many donations he got on open thread with no release posted.
Hmm.
Makes ya wonder why that thread is even there.
Dole out the credits properly.
Just know it needed to be said, and go ahead and get mad. Truth hurts.
alot of angry responces coming, maybe, but dare ya to point out a single lie in this post. Even an exaggeration.
Moose did hc for MONTHS and noone offered any valid help, except ssserpentine, why do you think anyone is gonna get off their but now?
Why don't you, punkrock?
Cause I know how utterly hopeless this task is.
Why don't you all just wait for the leak of the next os?
That so much closer than some random Joe, or Joe's on xda getting hc ported at this point .
is the dead horse braised yet?
Click to expand...
Click to collapse
Easy man, in my frenzy of trying to organize the thread, I forgot to credit Ssserpentine in the OP, youre right he did contribute a lot, no need to be rash, I will update it right now.
EDIT: btw oldmacnut did make an audio fix, im running his rom right now, I downloaded it when he had it posted before he took it down, and Im sure some of the bugs I mentioned are fixable on the rom level rather than through adb. My goal wasnt to debug the rom completely, it was to incorporate all the existing bug fixes and workarounds into one rom, while possibly solving others. Also the GSM devs are aplenty here, while we barely have any CDMA, Im sure we have enough talent to make it better than what it is. It might not be flawless, but Im sure we can squeeze more functionality out of it.

Its weird,
Honeycomb is more or less froyo based, obviously as we had hc long before gb, so at the time when I started getting into this whole dev thing hc/froyo seemed just different to me.
But after working on the abortion called gingerbread, and working onbthe kernel stuff, froyo to me, is starting to look like a much more viable and dev friendly option.
Alot if the work Dan did in hc was from scratch, or from the sdk, etc. The audio fix I did was from both.
The big issue on getting hc up and going into a usuable rom is source, we really really need that source for hc. Otherwise, its going to be a long drawn out road of trial and error building with alot of these issues never really getting fixed.
Truth is,
No device with our hardware exists with hc, so no drivers that we need.
We need Google to release the hc source.
I liked hc on my tab just like y'all, but.......I know its just a novel weekend fun toy till we get better resources.
Sent from my SCH-I800 using xda premium

oldmacnut said:
Its weird,
Honeycomb is more or less froyo based, obviously as we had hc long before gb, so at the time when I started getting into this whole dev thing hc/froyo seemed just different to me.
But after working on the abortion called gingerbread, and working onbthe kernel stuff, froyo to me, is starting to look like a much more viable and dev friendly option.
Alot if the work Dan did in hc was from scratch, or from the sdk, etc. The audio fix I did was from both.
The big issue on getting hc up and going into a usuable rom is source, we really really need that source for hc. Otherwise, its going to be a long drawn out road of trial and error building with alot of these issues never really getting fixed.
Truth is,
No device with our hardware exists with hc, so no drivers that we need.
We need Google to release the hc source.
I liked hc on my tab just like y'all, but.......I know its just a novel weekend fun toy till we get better resources.
Sent from my SCH-I800 using xda premium
Click to expand...
Click to collapse
Yeah I know, the lack of source sucks along with the fact we dont have drivers. I dont think we'll have everything working anytime soon at all, if ever even, but I think some of the minor annoyances like the disappearing quick settings toggle, sdcard mounting issues, and graphical errors can be solved without that kind of stuff. Me personally, Id just like HQ Video Playback and 3D Graphics working a hundred percent along with orientation, but as you said no drivers so idk how easy that'd be. Still, Im sure we could solve some of these minor issues. I keep browsing over the Nook Color Forums trying to find hints to solving some of these things

GSM Tab here I'll flash the old 2.5 alpha release and confirm these bugs, see what else I can do.
Sent from my GT-P1000 using xda premium

BulletproofIdeal said:
GSM Tab here I'll flash the old 2.5 alpha release and confirm these bugs, see what else I can do.
Sent from my GT-P1000 using xda premium
Click to expand...
Click to collapse
Nice to see something happening here. I love my Tab but would like some advancements in OS to address specific issues. I am very new to the dev side of the Android OS but would like to get involved.
--Mike

What blows my mind is that they have created an almost perfect HC port for the $150.00 walmart sold viewsonic g-tablet by means of the flashback roms so why is it so hard to get HC working on our tabs? And why can't someone just dump the Rom from the gtab10.1 and use that as a starting point?
On a different note, the alpha 2.5 HC Rom for gsm, the sd cards will not mount no matter what, I've tried The terminal and the mount instructions many times all I am able to do is get the tab to recognize my external sd as the internal sd, and if you try to go to settings applications and clear data for the gallery you get a force close as soon as you tap manage applications
Sent From Githrog's Tab

Ok done some immediate testing on my GSM Tab for some of the known issues
A) Red Border Around Screen at Random Times
Confirmed
Solution: is the same as the CDMA
B) Constant Gallery Force Close
Confirmed
Solution: Cannot be fixed through Setting, crashes as soon as you try to Manage Applications
C) Stock Launcher hangs for many seconds at a time randomly
Not really was slow on boot but no major problems
D) SD Card Does Not Mount
Confirmed
Solution: Haven't tested fix yet
E) Youtube app does not work
Confirmed
Solution: Confirmed
F) Orientation Sensor is not functional
Confirmed
Solution: "Rotating Screen" flips screen incorrectly so that capacitive buttons are on the top of the device
G) Honeycomb thinks Device Keyboard is enabled by default
Confirmed
Solution: Must be set on each boot
H) When pressing Quick Settings, an image that is semi transparent that is supposed to cover the entire screen isnt scaled properly
Confirmed
I) HQ Youtube does not work (LQ does on the mobile site)
Confirmed
J) Quick Settings Shortcut on Bottom Right Side (Wi-Fi Toggle, Brightness Slider, etc) appears for a second but disappears afterwards.
The widget that display battery level, time, etc stays active however no settings are located underneath it. While this menu is expanded a press on the bottom bar will cause the settings to briefly appear but then the whole menu will close
K) Flash Player is not Fully Functional
Not tested
"New" GSM bugs
1. Wi-fi settings are not saved on restart
2. Manage Applications and Running Services menu causes force close of settings
3. Small thing but Tab's first start had language set to Spanish (Not sure if it was spanish but it certainly was not English)
And as always 3G does not work (tried APN settings but it wouldn't let me save)
Alright I'm back to MIUI until I can find some more time on my hands
---------- Post added at 02:51 PM ---------- Previous post was at 02:31 PM ----------
Githrog said:
What blows my mind is that they have created an almost perfect HC port for the $150.00 walmart sold viewsonic g-tablet by means of the flashback roms so why is it so hard to get HC working on our tabs? And why can't someone just dump the Rom from the gtab10.1 and use that as a starting point?
Click to expand...
Click to collapse
If it were that simple I'm sure someone would have thought of that To be honest I think the problem is that the Tab is an extremely fractured device; it was really the first Android tablet to directly compete with the iPad, so it was spread as wide as possible. That's great for Samsung who got a pretty large base of customer but sucks for devs because the GSM and CDMA are 2 very different devices not to mention the P-1000N. When I got my Tab last month the first thing I noticed in this forum was the fragmentation between the different versions of Tabs. More profoundly this means that the developers are split apart, usually when one dev makes a break through everyone else can take advantage of it (i.e. the amazing Voodoo Sound/Color hacks) but not here. I feel like everyone is by themselves and I truly feel bad for the developers because they must make their own breakthroughs on top of dealing with complaints from Tab users with other versions that they want this awesome thing on their Tab. As if its no big deal to go and buy a $450 device to develop something as a hobby and then release it for free for people on the internet after already buying nearly the exact same device.
Sadly I think the Tab is a perfect storm working against modifying it in any ground breaking ways. Don't get me wrong I love my Tab and will try to help getting Honeycomb running but I almost feel like it would just be easier to wait for Ice Cream Sandwhich. /rant

Guys, there is no reason to develop honeycomb, it is inposible to make fully functional honeycomb rom, wait a month or less for ICS, read this (quote from android police posted today):
Honeycomb is closed source. Nobody can make a tablet without Google's blessing. The reason given is that Honeycomb was rushed out the door, and the code isn't good enough for an open source release. They're right you know, setting the emulator to anything smaller than a tablet will result in about a million force closes. Honeycomb just isn't as supportive of hardware as Gingerbread was. To save developers the headache of supporting a platform that wasn't ready, Android's openness got shelved.
Luckily this is going to change. The big cheese said so himself on the Official Android Developers blog, "This temporary delay does not represent a change in strategy. We remain firmly committed to providing Android as an open source platform across many device types." Source code is coming back. This will make the modding community's life much easier. Cyanogenmod 8 (I got excited just typing that) and Ice Cream Sandwich will be able to get hacked onto just about anything.
Click to expand...
Click to collapse

CROrION said:
Guys, there is no reason to develop honeycomb, it is inposible to make fully functional honeycomb rom, wait a month or less for ICS, read this (quote from android police posted today):
Click to expand...
Click to collapse
I just wanted an excuse to try out Honeycomb

BulletproofIdeal said:
Ok done some immediate testing on my GSM Tab for some of the known issues
A) Red Border Around Screen at Random Times
Confirmed
Solution: is the same as the CDMA
B) Constant Gallery Force Close
Confirmed
Solution: Cannot be fixed through Setting, crashes as soon as you try to Manage Applications
C) Stock Launcher hangs for many seconds at a time randomly
Not really was slow on boot but no major problems
D) SD Card Does Not Mount
Confirmed
Solution: Haven't tested fix yet
E) Youtube app does not work
Confirmed
Solution: Confirmed
F) Orientation Sensor is not functional
Confirmed
Solution: "Rotating Screen" flips screen incorrectly so that capacitive buttons are on the top of the device
G) Honeycomb thinks Device Keyboard is enabled by default
Confirmed
Solution: Must be set on each boot
H) When pressing Quick Settings, an image that is semi transparent that is supposed to cover the entire screen isnt scaled properly
Confirmed
I) HQ Youtube does not work (LQ does on the mobile site)
Confirmed
J) Quick Settings Shortcut on Bottom Right Side (Wi-Fi Toggle, Brightness Slider, etc) appears for a second but disappears afterwards.
The widget that display battery level, time, etc stays active however no settings are located underneath it. While this menu is expanded a press on the bottom bar will cause the settings to briefly appear but then the whole menu will close
K) Flash Player is not Fully Functional
Not tested
"New" GSM bugs
1. Wi-fi settings are not saved on restart
2. Manage Applications and Running Services menu causes force close of settings
3. Small thing but Tab's first start had language set to Spanish (Not sure if it was spanish but it certainly was not English)
And as always 3G does not work (tried APN settings but it wouldn't let me save)
Alright I'm back to MIUI until I can find some more time on my hands
---------- Post added at 02:51 PM ---------- Previous post was at 02:31 PM ----------
If it were that simple I'm sure someone would have thought of that To be honest I think the problem is that the Tab is an extremely fractured device; it was really the first Android tablet to directly compete with the iPad, so it was spread as wide as possible. That's great for Samsung who got a pretty large base of customer but sucks for devs because the GSM and CDMA are 2 very different devices not to mention the P-1000N. When I got my Tab last month the first thing I noticed in this forum was the fragmentation between the different versions of Tabs. More profoundly this means that the developers are split apart, usually when one dev makes a break through everyone else can take advantage of it (i.e. the amazing Voodoo Sound/Color hacks) but not here. I feel like everyone is by themselves and I truly feel bad for the developers because they must make their own breakthroughs on top of dealing with complaints from Tab users with other versions that they want this awesome thing on their Tab. As if its no big deal to go and buy a $450 device to develop something as a hobby and then release it for free for people on the internet after already buying nearly the exact same device.
Sadly I think the Tab is a perfect storm working against modifying it in any ground breaking ways. Don't get me wrong I love my Tab and will try to help getting Honeycomb running but I almost feel like it would just be easier to wait for Ice Cream Sandwhich. /rant
Click to expand...
Click to collapse
Wow now that is the kinda posts i like seeing on here! I will try to update the OP tonight with this info! Thanks so much! Definitely echo your sentiments about the fractured and fragmented development we have going on here, it really sucks =/
Ive found out that replacing the existing Gallery with Gallery3D should fix the FC that keeps popping up.
I think Ive found a working Youtube App (in LQ).
Ive also found a hint towards solving the sdcard mounting issue. Its not the vold.fstab its something either in the framework or ramdisk within the kernel, according to the Nook Color Forums.
This thread is interesting: http://forum.xda-developers.com/showthread.php?t=1062626 , actually the entire nook color forum is interesting for finding fixes.
Also changing the dalvik_heapsize to a certain value is supposed to increase app compatibility. Before I update the OP with some of these things, I wanna do a little more testing and see what I can come up with.

Sorry to bother for help,
Sorry to bother you guys for help, but I've been trying to install Oldmacnut's updated of Spacemoose's CDMA Honeycomb (2.5.1) for hours now, with no success.
I used Rodderick's awesome stock rom/kernel and got into clockworkmod (using 4.0.1.5 or 3.0.0.0), installed the zip from there, then rebooted the phone, but I would either 1) be stuck at logo for 10+ minutes 2) see the Sprint startup video loop over and over again, or 3) get stuck on a turned on, but black screen.
How did you guys install Honeycomb on your CDMA tab? Am I doing something wrong? Should I use Spacemoose's 2.5 rom instead of Oldmacnut's?
EDIT: NEVER MIND, IT BOOTED INTO HONEYCOMB. I am in a foreign language, haha, I'm guessing Portuguese?
EDIT EDIT: Google Translate detects the language as Catalan. Haha!

iliveinabucket said:
EDIT EDIT: Google Translate detects the language as Catalan. Haha!
Click to expand...
Click to collapse
Hehe that happened to me as well

First Impressions and problems encountered
HOLY SHOOT THIS IS QUITE FAST!
Considering there is no graphics acceleration support, Honeycomb runs much faster than I anticipated. SD card support is fantastic, and so is hearing sound! (I love you OMC) The UI is awetastic and the standard web browser is blazing fast. Scrolling in web pages is faster on Honeycomb than on Gingerbread stock.
The jittery touch screen bug I have is still there, unfortunately. Damn bug drives me crazy sometimes. I'm sure somebody has this problem that many of us have but have not found a fix to: http://forum.xda-developers.com/showthread.php?t=970965
Basically, when I hold down my finger to scroll on white or light-color backgrounds, the screen shakes back and forth in a spastic, noticeable way, especially when I hold it in place. This happens on every single rom I've been on, froyo, GB, CM7, and now Honeycomb. Has anyone found a fix for that yet?
Anyways, I think all the known Honeycomb bugs are true to me too. Youtube force closes on me, GPS doesn't work, auto-orientation doesn't work. Strangely enough, Quick Settings doesn't work for me. Anyone encounter that?

Just a idea feel free to comment

I was haning out with. My friends
and this idea struck me out of the blue
Why can't android have a easy click on wifi icon bring up local networks function like most desktops
Positive.or negitive comments welcome
If you think its possible let me know ill try my hardest to get it to work
Think of it like the status bar quicksettings in Stef of power on off make it so it turns on or off a list of avilible networks listed in the notifications click one get rather a prompt for a password or connect to open network
Sent from my PC36100 using xda premium

for phones if you can view it in quicksettings thats would be awesome, im about to add that a rom ive been working on, and ill see if i can figure out how to incorporate it. but for 3.x/4.x android tablets, its pretty much useless since its already available in the bottom right corner.

I must agree, as a quick setting switch this would be freaking amazing. However, you can add a shortcut to any screen that goes straight to wireless settings.... I'm sure prolly every dev, which i am not nor prolly ever will be, already know this, maybe it'll help a non-dev.

maybe you can create a poll, and if we get enough people to see it, maybe an experienced dev will make it. im just starting making my own roms, so I cant do it myself (yet).

If Simone wants to start a pole go right a head.
Sent from my PC36100 using xda premium

like when you click on the wireless network icon in taskbar and brings up the list of networks?
I would think that's awesome especially as a quick setting but my first concern would that not drain the battery, if wifi is on it'll continually scan but having the graphics change often I think that would drain the battery. To me it would be more of a tactical eyecandy.

Sounds cool, I like it