I happen to be one of those rooters who still enjoys the Sense UI over an AOSP base.
However, I was wondering if there was a way to lower the amount of home screens I have. My daily is Myn's RLS4 and with Sense I find myself only really using 3-5 home screens and basically fill the other 2 with widgets just so they are not blank. I wouldn't mind them if I have to, but it's possible my phone would run a little quicker and save some battery if I were able to limit the amount of home screens and focus on using the apps for the info when I need it rather than have the widgets constantly running.
I'm not sure if there is a way to integrate a Miui or ADW/Launcher Pro method of controlling how many screens we have, but I think it's not far out of the ballpark.
I searched through the forums for about an hour looking for any info, but didn't find anything. Please post a link if this has been discussed already.
haha bump. i would like to know that aswell. there are times that i miss the clouds fly by lol.
teshxx said:
haha bump. i would like to know that aswell. there are times that i miss the clouds fly by lol.
Click to expand...
Click to collapse
hahahahahahabumpha
Seriously though, when I first got the Evo, I was like yeah seven screens your other phones suck. Now I just want 3, maybe 5.
teshxx said:
haha bump. i would like to know that aswell. there are times that i miss the clouds fly by lol.
Click to expand...
Click to collapse
For the clouds just install "widgetlocker" it has the option
Hey bud not sure if you noticed, but this is not the Q&A section. Questions are to be asked in Q&A.
....really you cant change that in the sense options somewhere? Just another reason Sense is lame, imo.
LauncherProPlus, FTW!!! I got one homescreen, and 15 icons in my dock, not to mention swype gestures, and running CM6 so i have lockscreen gestures as well...
My Evo > Sense UI
Yellowcard8992 said:
Hey bud not sure if you noticed, but this is not the Q&A section. Questions are to be asked in Q&A.
Click to expand...
Click to collapse
Hey buddy, this is a development question. It was more of a suggestion of an idea that I had not seen before more than a question about something that exists.
The community is about making better devices, apps, etc. for all and there's no need to waste your time posting a reply about being in the wrong section. If it is violating anything, the mods can move it.
Moved to Q&A as this is a [Q]. The Android Development threads are for software coding/releases.
Bump. Nothing on this yet?
Any info would be nice.
Thanks
bump
Would love some guidance on this, hoping the # of homescreens config is held in a file somewhere and someone with a rooted phone can edit it?
Hi Everyone!
I just picked up a Samsung Continuum last night. Actually returned my Droid X for this phone. The allure of cracking the Ticker was too much for me to handle any longer.
So with that said, has anyone been able to find out any information on developing stuff for the ticker? I know Samsung has not released any official APIs for using it. I'm assuming, however, that the drivers and some source code for using it has been released with the OS source code.
Is this a true assumption? If so has anyone started looking into how we can take advantage of it? I'm not a ROM developer so I'm hoping I can find ways into the API with the stock ROM.
Any advice and or pointers anyone can offer (especially if you've already been looking into it!) would be greatly helpful for me. As I said, the whole reason I got this phone was to hack the ticker. I can see so many incredible uses for it that I must find a way to take advantage of it!
Thanks in advance!
Oh, and this is my first post so Hi
Honestly i have no idea what so ever.
But i really hope we can do something. I bet there is some sweet stuff the right person can do with the ticker.
We currently have one dev (who doesn't have a Continuum) and a handful of testers working on getting Odin, Clockwork Recovery, and a Ported version of CyanogenMod going. No other devs or work that I know of..... Future looks bright though...
Thank you both for the replies!
I've spent a few hours looking into the source and dedexing some files off my Continuum. Made some progress, I think. I've spent my time looking over the TickerHistory service (the activity that gets launched when you click the up/down arrow in the right side of the ticker).
I'm trying to track down what actually happens when you click the Refresh button on that screen. I know when I press it my ticker updates but I'm not sure if that's controlled by the TickerHistory or something else. That's what I'm hoping to find out.
I wish I could see LogCat outputs but the Continuum is not being picked up by this computer. I will have to wait until I'm around my development machine. In the mean time I'm going to start playing with Titanium Backup. Going to freeze a bunch of services and see if any of them cause the ticker to stop working. That should help get me some more focused direction
I'll keep ya'll posted!
Jaylach said:
Thank you both for the replies!
I've spent a few hours looking into the source and dedexing some files off my Continuum. Made some progress, I think. I've spent my time looking over the TickerHistory service (the activity that gets launched when you click the up/down arrow in the right side of the ticker).
I'm trying to track down what actually happens when you click the Refresh button on that screen. I know when I press it my ticker updates but I'm not sure if that's controlled by the TickerHistory or something else. That's what I'm hoping to find out.
I wish I could see LogCat outputs but the Continuum is not being picked up by this computer. I will have to wait until I'm around my development machine. In the mean time I'm going to start playing with Titanium Backup. Going to freeze a bunch of services and see if any of them cause the ticker to stop working. That should help get me some more focused direction
I'll keep ya'll posted!
Click to expand...
Click to collapse
Oh... sounds like we might have a dev on our hands... ....
Jaylach said:
Thank you both for the replies!
I've spent a few hours looking into the source and dedexing some files off my Continuum. Made some progress, I think. I've spent my time looking over the TickerHistory service (the activity that gets launched when you click the up/down arrow in the right side of the ticker).
I'm trying to track down what actually happens when you click the Refresh button on that screen. I know when I press it my ticker updates but I'm not sure if that's controlled by the TickerHistory or something else. That's what I'm hoping to find out.
I wish I could see LogCat outputs but the Continuum is not being picked up by this computer. I will have to wait until I'm around my development machine. In the mean time I'm going to start playing with Titanium Backup. Going to freeze a bunch of services and see if any of them cause the ticker to stop working. That should help get me some more focused direction
I'll keep ya'll posted!
Click to expand...
Click to collapse
Def keep us up to date i would love to see what can come of this!
Weudel said:
Oh... sounds like we might have a dev on our hands... ....
Click to expand...
Click to collapse
People have been known to call me that =)
I only wish I had a better knowledge of C/C++ (Unfortunately I work in a MS/Java/Adobe world) so I could help with the ROM cooking. I figured attempting to crack the ticker would be a good first step into the Android modding world =)
Well, it's nice to see we might have another Dev! Welcome to the forums!
ticker
Hey I been testing the the developers code and he had me dump the file attached. See if it helps.
http://www.megaupload.com/?d=YW8CKXZA
Logan
Thanks for the dump Logan!
I've learned a few things since I've been home. Nothing major but the new information should help point us in the right direction.
No matter what service I freeze in Titanium the ticker continues to get updates. This could mean many things. Maybe the service is hidden, maybe there isn't a service. Who knows right now. This is really what we're looking for.
Disabling some applications makes the ticker not work when clicking an item.
For example, disabling SNS Provider makes it so it can't launch email when clicking on the email icon
TickerRootView is what LogCat displays as a Tag when interacting with the ticker (ie: swiping left to right)
TickerStandbyView is what LogCat displays as a Tag when, well, the ticker goes into StandBy
Disabling a service, sending a test email, re-enabling the service is not a fun process when you have over 100 items to test
As I said, nothing major has been learned yet but this information should help to keep pointing us in the right direction. Will keep playing and will hopefully have more updates by the end of the night
The ticker easily has the most potential for customization as far as development for this phone is concerned. I'm glad you've chosen it as your starting point. Many thanks for your hard work to come.
Sent from my SCH-I400 using XDA App
Editing out my previous message I had here -
Semi-decent break through.
Ticker code lives inside the services.jar file. com.android.server.ticker.*
Now to see where I can go from here =)
Just my little wish list:
Ability to set update interval
Ability to put 4x1 widgets in the ticker
Oh, and, someone else suggested being able to drop the dock down there, to free up screen space.
Sent from my SCH-I400 using XDA App
Changing the update frequency may be fairly simple. Need to test a few things with that.
I'm still looking into how we can get a custom View down there. The neat thing is it's just a ViewFlipper rendering Views, both Java coded and XML declared.
Sent from my SCH-I400 using XDA App
I purchased my Continuum for the very same reasons. I see this baby as being one helluva phone once we wash all of the 'whiz off of it!
As odd as it sounds, I am just as interested in cracking the soft buttons just as much as the ticker. The screen being physically a 480 x 992 display with rationed space for the buttons and ticker, I'd like to go about changing the buttons. Maybe make them bigger or in a different order, or have them change depending on mode or activity. Or rotate with the orientation of the phone! Perhaps a subtle pulsing of a button to indicate a notification while the phone is timed-out.
I feel that when the phone is figured out, we'll have a damn impressive device in our hands. A developer's dream.
-EJDII
I'd like to see the Pandora menu down there when it's opened. Can't believe Samsung didn't already do this.
Sent from my SCH-I400 using XDA App
samuelhadams said:
I'd like to see the Pandora menu down there when it's opened. Can't believe Samsung didn't already do this.
Sent from my SCH-I400 using XDA App
Click to expand...
Click to collapse
That's a fine example of a 4x1 widget we could put down there... I would like to see Tweetdeck as well, but we don't have to agree on which ones if we just get the widget functionality....
Viva la devs!!!
ErikJDurwoodII said:
I purchased my Continuum for the very same reasons. I see this baby as being one helluva phone once we wash all of the 'whiz off of it!
As odd as it sounds, I am just as interested in cracking the soft buttons just as much as the ticker. The screen being physically a 480 x 992 display with rationed space for the buttons and ticker, I'd like to go about changing the buttons. Maybe make them bigger or in a different order, or have them change depending on mode or activity. Or rotate with the orientation of the phone! Perhaps a subtle pulsing of a button to indicate a notification while the phone is timed-out.
I feel that when the phone is figured out, we'll have a damn impressive device in our hands. A developer's dream.
-EJDII
Click to expand...
Click to collapse
The icons for the ticker (like the music player and the weather widget and etc) and the soft keys are in framework-res.apk just in case someone didn't know I just can't find am appropriate way to sign the apk back up once you unpack it so that the phone doesn't reject it xP lol
Sent from my SCH-I400 using XDA App
No progress to speak of today, unfortunately. Still trying to figure out if it's possible to add our own views to the ticker. Quite honestly, I'm not all that optimistic. At least not with having the ability to do it without requiring a custom SOMETHING (services.jar, ROM, etc).
The reason I say this is it looks like all the widgets are hard coded into the Ticker code. That may or may not be a bad thing. If I can find out where those widgets are added we may be able to tap into it.
I've also started looking into changing the update frequency for the facebook/twitter/myspace ticker widget. If I could figure out how to get the /data/data folder off my phone it would be super helpful. I guess I don't know ADB well enough. Even though I'm rooted every time I do an adb pull /data/data /usr/development/continuum/data I get a permission denied error. I know it's possible but for some reason I'm struggling with it, lol.
Will keep ya'll posted! I'll start looking into the "button bar" as well. See if I can come up with anything there.
I've been looking into the services that the ticker depends on for its feeds, and widgets, and it's all very interesting to me. I'm definitely going to be diving into this once I get clockwork up and running for everyone. Stay in touch and maybe we could co-op this one. (;
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?
Hey guys! I just jumped the sinking Sprint ship and made the move to AT&T. I got myself a brand new LG Nitro and immediately rooted and installed CM9. I'm used to the cm experience as I had an Epic 4G on sprint. Anyways, after installing CM9 my LED buttons won't light up. Is this a known issue? I could use some help because without the LEDs its hard to use this phone in the dark since I'm not used to the button placement yet. Thanks in advance!
I just had the same problem. Look through the setting. Turn auto-bright on
Sent from my LG-P930 using XDA
Derpp. thanks man!
Settings?
I'm still getting used to the settings of CM9 and can't seem to find the spot where that toggle is. Can you give me a menu ---> location pls?
Thanks
next time do a simple search and you will find a # of posts on this topic and none of them needed to clutter up the main forum starting a new thread about it.
learn to do your own research like 99.9% of the rest of us had to do.
trobertson said:
Hey guys! I just jumped the sinking Sprint ship and made the move to AT&T. I got myself a brand new LG Nitro and immediately rooted and installed CM9. I'm used to the cm experience as I had an Epic 4G on sprint. Anyways, after installing CM9 my LED buttons won't light up. Is this a known issue? I could use some help because without the LEDs its hard to use this phone in the dark since I'm not used to the button placement yet. Thanks in advance!
Click to expand...
Click to collapse
play with settings>display>automaticbacjklight>click use custom, and set brightness to automatic
scott0 said:
next time do a simple search and you will find a # of posts on this topic and none of them needed to clutter up the main forum starting a new thread about it.
learn to do your own research like 99.9% of the rest of us had to do.
Click to expand...
Click to collapse
I performed a search before posting and was unable to find a working fix. Next time, try posting something a little more productive and less useless trolling. Thanks.
THanks
scott0 said:
next time do a simple search and you will find a # of posts on this topic and none of them needed to clutter up the main forum starting a new thread about it.
learn to do your own research like 99.9% of the rest of us had to do.
Click to expand...
Click to collapse
I'm familiar with forums thanks. It's my Android that I'm not. In fact I did do a search and found a day old thread which I figured was the best way to get my information.
Thank you for you input
does anyone know if its possible to swap the location of the navigation buttons and the popup menu? Like making the navigation buttons on the right and the popup menu on the left? I dont see anything about this anywhere, but im curious if its possible.
Its in the Framework somewhere. Perhaps I might try to bug hashcode? lol
The navigation buttons aren't part of Trebuchet. Changing their configuration is most likely out of the scope of your abilities, unless you're good at coding.
soupmagnet said:
The navigation buttons aren't part of Trebuchet. Changing their configuration is most likely out of the scope of your abilities, unless you're good at coding.
Click to expand...
Click to collapse
Well its actually part of the framework. Theres not really "coding" to be done. It would be more of finding things and swapping their values more than likely. But yeah ive done a few things, Ive ported a sense rom to the Nexus s 4G and helped fix a few things in cm7 for the Epic 4G touch, so im not totally retarded i just wanted to ask and see if anyone had ventured into this yet.
HaiKaiDo said:
Well its actually part of the framework. Theres not really "coding" to be done. It would be more of finding things and swapping their values more than likely. But yeah ive done a few things, Ive ported a sense rom to the Nexus s 4G and helped fix a few things in cm7 for the Epic 4G touch, so im not totally retarded i just wanted to ask and see if anyone had ventured into this yet.
Click to expand...
Click to collapse
Forgive my assumptions but your original thread title made it seem like a "dumbed down" answer was necessary.
You still have to have somewhat of an understanding of Java but if you are up to it so be it. There are a few Kindle Fire roms on github where you can get full uncompiled frameworks files for editing/research/whatever. Or if you want to go through the process of decompiling/editing/recompiling, you could do that as well. But I'm sure you know that already.
[Edit:] As for an answer to your question, I haven't seen anyone here messing with the placement of the status/nav bar items, only editing the graphics.