http://code.google.com/p/vogue-andr... Priority Component Owner Summary#makechanges
things change fast around here. try reading new threads before post useless request to fix an old problem from march
If your going to daddy me at least leave me a toy.
Wow learn to read. The android n00b thread people are still having these issues. Maybe something has changed but I have seen it. I see two categories of haret users those who work (miracles people who usually are using nand and may have some enviromental difference over us regular sdcard-hare ppl)..
If you can fix my issue fix it, but don't tell me its fixed when nothing says that. Albeit a night of going through all the updates on the different builds may produce results no one has done that in that particular thread (2, or 3, which upon someone coming up and saying this easy has ended up giving up) both threads are a bit different. One was supposed to be look how easy it is , with a few nand resistant fools getting every thing but sound. You sir are a troll... !#@@! @!# @#[email protected][email protected]@!
Seriously if you want new people using android put out a haret build that works... Don't make us n00bs flash our customized **** so we can say oh thats broke, i need that...
sorry if my tone was incorrect. let me try again
The link you posted refers to something that is not a problem any more or was due to old hardware, ie the button physically wasnt working.
k_k successfully used haret to test his build when he was working on the gps. that was the beginning of june
are you trying to say that the link is to YOUR problem? i cannot tell from the post of only a link. it looks like reading through this thread that you got past that problem.
if you need help please list your problem with as much detail as possible so i or someone else can help you.
if you are trying to make a case for haret dev, you should post links or quote more recent attempts and problems
Thanks for the news
Cool. I'll search up on that and post to the threads that I've been going to. It's just email never comes across very personable. People who say to read the entire forum get on my nerves or to search when I have is annoying because sometimes they have read it in an area I haven't landed and it like a race run condition due to bad communication. If you see something try to link it, glad I have a user name to search off, but if you can pt a better thread I'll be happy. Either way when I find it, I'll try to boot again maybe in a week or so. I'll be very happy if it does indeed work now, we'll see.. As far as my posting relating to haret, yet you can regain control of your buttons but if you actually read all of the thread you'll see it doesn't get better than that, it then is a sound issue. Either way haret is broken, and my point is that poor user from march is still suffering now, and this time its sound. I suspected that haret became broken due to the development direction towards nand. I.e. whatif system.file is reffed somehow as (NAND0,0):/initrd.gz. I mean droid when from system.img's to partitions so something very generic could lead to both issues esspecially if a user A who can't hear in haret, can hear in a nand install using the same release? See the modules and stuff are going to be the same. I hope your not wasting my time with the k_k bit...
tyler51773 said:
I hope your not wasting my time with the k_k bit...
Click to expand...
Click to collapse
no. he is one exmple of people who have it working. there are others, i just know him off the top of my head.
People who say to read the entire forum get on my nerves or to search when I have is annoying because sometimes they have read it in an area I haven't landed and it like a race run condition due to bad communication.
Click to expand...
Click to collapse
your first post was just as indirect. from that post i had no way of know you have been working on it. the specific link you post was probably not the best choice. with out direction from you i have no reason to go 2 links deep. not until you gave more description did i go into the xda thread where have been trying things.
it then is a sound issue.
Click to expand...
Click to collapse
yes there is still the sound issue. you could have gotten much better response if you had put something in the first post to indicate you specifically want the sound worked on.
sound it is.
its just more like a watch me thread for people who care about haret. i posted a bug on vogue-android.. but the drift it haret is broken. been broken. its bad right now. can we fix it? or is it fixed already. you mentioned K_K do you mean this thread http://forum.xda-developers.com/showthread.php?p=6852911 or do you mean kalt_kafee kernel are they same guy? where you saying dpad was fixed versus just sound. I guess I'm going to try his latest update kernel, unless you've seen a better thread. I've already got to goto bed. Maybe that's why the guy never came back on my own thread cause i sent him to a new kalt kernel hehehe..
sound working
Going through the list now. Thanks for the pointer. I'll will soon venture forward.
I got sound on an old androidinstall of unknown origin. it was freezing and unstable. I did not get sound ironically on VaniljEclair , the second install from the old android I also installed to system.img vs sdcard partition. trying warm
Aqtrans' CM-5.07 - nice and stable
warm eclair rls 1 - fast, worked great for a day then force closes all over
Incubus26Jc's SuperE beta 3 - still slow on kaiser
VaniljEclair 5.0.8 out! (not tested by me)
trying myn's warm donut then will try aqtrans'
you may have beaten the pepsi challenge.
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?
I have not received an update but wanted to see what i have to look forward to!!!
I just hope the reboot issue is fixed...
T-Mobile USA
4.0.2
Use search and find out
Sent from my Galaxy Nexus using xda premium
I did not but couldn't find a comprehensive list, just bits of info in many posts.
http://forum.xda-developers.com/showthread.php?t=1481044
Sent from my Galaxy Nexus using xda premium
Thank you!!!
The guy is trying to stimulate discussion on a hot subject. Stop posting links to 2months old and irrelevant (its not the the same update...). Besides, he didnt ask for a changelog... as far as i know..
Personally, the camera is a huge improvement in many ways, browser query delay is faster (definitely, not placebo). I cant say the device is "snappier" since it was already pretty much instant. Also, i used to have a kind of lag while typing text in browser (such as this post), that is also gone now. I did experience a few app crashes though, but i am certajn that its because the custom rom needs work (B29 aokp).
Edit: also, the android OS battery using is significantly less. Of course sampke is smalll but it went from 25% to 4-5%
MatAuc12 said:
The guy is trying to stimulate discussion on a hot subject. Stop posting links to 2months old and irrelevant (its not the the same update...). Besides, he didnt ask for a changelog... as far as i know..
Personally, the camera is a huge improvement in many ways, browser query delay is faster (definitely, not placebo). I cant say the device is "snappier" since it was already pretty much instant. Also, i used to have a kind of lag while typing text in browser (such as this post), that is also gone now. I did experience a few app crashes though, but i am certajn that its because the custom rom needs work (B29 aokp).
Click to expand...
Click to collapse
Honestly, even though it is a 2 month old thread. I read a few bullets on the OP post and most of those changes are relatively accurate on the OTA update released yesterday.
So I don't see what your point is? Even the points you made about 4.0.4 is listed,
Noticeably Faster
Browser performance noticeably improved
Miscellaneous camera UI changes
Click to expand...
Click to collapse
zephiK said:
Honestly, even though it is a 2 month old thread. I read a few bullets on the OP post and most of those changes are relatively accurate on the OTA update released yesterday.
So I don't see what your point is? Even the points you made about 4.0.4 is listed,
Click to expand...
Click to collapse
my point is relatively clear. It is old and this is a new update, you dont know how accurate it is. Besides, his post was more oriented towards a discussion than "please post change logs!!!!!". If you dont like those kind of discussions, fine, but i think its appropriate instead of being an ass about a new thread.
I find nothing wrong with this thread. Who knows what else Google coulda added to 4.0.4 for GSM over the leaked 4.0.4 for CDMA.
Not only are the phones different which can affect things such as reception and radios, but this is much newer and could have additional improvements. No point attaching GSM stuff to an already quite long CDMA change log thread as no one is going to see it.
-Picture quality is definitely improved; likely related to better operation
-Dialer is slightly bigger (?); layout a little different, e.g. settings button at bottom of dialer
-Haven't noted a difference in rotation,
-Backing out of some apps is faster, Play for instance, hit back-back-back and there is no lag migrating back and out of the app,
-The majority of my other observations are likely placebo (i.e. smoother, etc...)
Did google double the storage? Haha.
Iphone. Helping computer illiteracy get popular since 2007.
MatAuc12 said:
my point is relatively clear. It is old and this is a new update, you dont know how accurate it is. Besides, his post was more oriented towards a discussion than "please post change logs!!!!!". If you dont like those kind of discussions, fine, but i think its appropriate instead of being an ass about a new thread.
Click to expand...
Click to collapse
It actually is very accurate. Yes there are some new changes but not many. A lot of the most obvious changes have been pointed out in OP and we can quickly recognize them as we use 4.0.4.
That thread could of been continued on since OP actually had a lot of the points down. Many of the points that people are posting in this thread have been already made in that thread listing changes from a "leaked" build. The same bootloader from that leak made it into the OTA.
Scrolling seems odd in the browser and Facebook at times. Little slow... anyone else notice it?
Sdobron said:
Scrolling seems odd in the browser and Facebook at times. Little slow... anyone else notice it?
Click to expand...
Click to collapse
After 1 or 2 battery pulls that behavior went away for me.
First off, thought I'd let you know I updated with the CWM method. I was 100% stock but unlocked bootloader. Worked fine took 2min to do. One small quip was after my first reboot, I didn't have cellular network connection. Took 2-3 more reboots and lots of toggling to make it work. Now its working just fine.
Here's what I've observed:
1) Power menu sound toggles are nice (50x better if mute actually meant full system mute)
2) Screen shot sound changed to the same as the camera shutter sound
3) Feels snappy!
4) Color fade and transitions (like in menus) are now smooth instead of jittery.
5) Multitasking button has less lag. Definitely not perfect still though.
6) GTalk icon updated to look like Messaging and Google Voice.
7) When you turn the screen on, it fades in a much more pronounced way (imo).
8) Auto-rotate is fast and smooth, although I never found it particularly sluggish before.
9) Other, likely "placebo", effects of smoothness, etc.
developing...
Right i know there is a thread regarding battery stats. That is were everyone post their stats and basically each member show off their battery life and show off to people how much screen on time they can get.
What i want to do with this thread is the opposite. I want to help people who have issues with regarding poor battery life to post here there problems, to post information on their setup and were they think it is going wrong as to why they have poor battery life.
Rather than posting these issues on each individual thread all over the forum why not just keep it in one place. So that myself and hopefully more experienced members can help out others who have issues as in regarding the battery life and try to see for example what app keeps the phone awake while phone is suppose to be sleeping and try and guide members on how to resolve their issues and give them the battery that they are suppose to have.
I will try and do most of the helping and provide links to threads for example the BBS thread were you can download the application and find out what wakelocks you have and post your screenshots here of the app so we can see where the issues lie.
I am doing this to help and to keep the forums clean and organised and to keep the development threads less cluttered with battery issues. If you have those kinda issues then come here and i will try my best to help out.
If Mods feel that this thread is pointless then please close the thread. But i hope you understand my logic behind this thread and my goal to help out people were they need it.
Thanks to you all and thanks to all the developers who take their time to provide us with something amazing for our phones and to the Mods who keep our threads in order
BetterBatteryStats Explanation
Right here is were i will explain how BetterBatteryStats works. I know i do not have my phone back so it is kinda hard to post screenshots with explanations on how to work the app but will try my best to explain without it.
First of all here is the link were you can find the application:
BetterBatteryStats Thread
Apart from Titanium Backup for me BBS is the next must have application for your android phone and especially for the One X. Thanks to this application i have learned a lot in my time here on XDA on how to sass out what keeps the phone awake and what to do on how to go about fixing the issue and stoping the wakelock from happening.
Now i am thankful for more experienced members and kernel developers who take their time to explain on the different threads on what are the wakelocks and what issues they can cause. One of them is the dreaded AudioOut3 wakelock. That is caused by having keypad tones on, which is ticked in sound in settings and also lockscreen sounds and dialpad touch sounds on. By disabling those you save yourself massive battery time. To give you an example of what i mean here is an explanation:
*AudioOut_1 AudioOut is used to play notification and system sounds. Putting your device on silent or at least unticking in settings-sound and untick the following:
Touch keypad sound
Lockscreen Sound
Dialpad Touch Tone sound
This will make the wakelock go away. (thanks to Sishgupta and his thread is here for more info)
Sources:
https://github.com/asksven/BetterBatteryStats-Knowledge-Base/wiki/PowerManagerService
To follow more on a detailed basis regarding BetterBatteryStats is at the following link here when you can get connected to the wiki site
Link:
https://github.com/asksven/BetterBatteryStats-Knowledge-Base/wiki/_pages
Other issues that i found out that drain my battery is keeping Facebook on all the time and twitter as well. I would not recommend either to have on at the same time but if i was to choose which one i would like to keep constant notifications would be Twitter.
But my advice would be to once you finished from checking your Facebook stuff to log right back out straight away. Cause the connection will always be connected and that makes the phone to stay wake even when phone is in deep sleep
*Another thread that a few other members have unfortunately encountered wakelocks similar to what i have just posted here and they just go about explaining what they have done to encounter those wakelocks and stop them. These wakelocks again are the facebook and audioOut. Thread link here
*Deleting your battery stats in recovery. Do not do that. Does not improve battery at all. Bare fact it does not do anything actually. You can find more on this here.
Battery stats, stored in the batterystats.bin file, are only used to maintain information about what is using the battery when not recharging. That is, it essentially holds the information displayed in the Settings > Battery screen. Nothing more, nothing less. Thus:
It has no impact on the current battery level shown to you.
It has no impact on your battery life.
List of Apps you can freeze, delete or disable if not rooted
reserved
Goku80 said:
......
*AudioOut_1 AudioOut is used to play notification and system sounds. Putting your device on silent will make this go away. (thanks to
Click to expand...
Click to collapse
So you recommend to put the phone on silent?
exCluSive1 said:
So you recommend to put the phone on silent?
Click to expand...
Click to collapse
very funny. no just untick in settings -sound and untick touch keypad sounds- lockscreen sounds and dialpad tones. use haptic feedback instead and use notification tones and normal ringtones. that way trust me you shall see that you will have very minimal audioout wakelock
Goku80 said:
very funny. no just untick in settings -sound and untick touch keypad sounds- lockscreen sounds and dialpad tones. use haptic feedback instead and use notification tones and normal ringtones. that way trust me you shall see that you will have very minimal audioout wakelock
Click to expand...
Click to collapse
Yes and did you check how much relevant difference such a wakelock makes in battery percentages? Now, trust me, <2% for a whole 24 day cycle. Thus, irrelevant
exCluSive1 said:
Yes and did you check how much relevant difference such a wakelock makes in battery percentages? Now, trust me, <2% for a whole 24 day cycle. Thus, irrelevant
Click to expand...
Click to collapse
I beg to differ. It could be depending on what kernel you may be running or not but i have encountered massive drainage specially overnight due to this wakelock. And unfortunately the only way to beat this is to do as stated not just by me but also in the wiki thread
Some kernels you do not have that wakelock but on some you do.. I am still trying to build this thread up as i feel it has potential and gives more of a heads up to people out there what causes the battery to drain.
Only doing this as to help out noobs who just bought this phone. I want them to know what causes the issues they might face. If the phone of a user is set up properly and as you know yourself if you have it setup the right away you can get amazing battery life. So this is the idea behind the thread. To help out others
Goku80 said:
I beg to differ. It could be depending on what kernel you may be running or not but i have encountered massive drainage specially overnight due to this wakelock. And unfortunately the only way to beat this is to do as stated not just by me but also in the wiki thread
Some kernels you do not have that wakelock but on some you do.. I am still trying to build this thread up as i feel it has potential and gives more of a heads up to people out there what causes the battery to drain.
Only doing this as to help out noobs who just bought this phone. I want them to know what causes the issues they might face. If the phone of a user is set up properly and as you know yourself if you have it setup the right away you can get amazing battery life. So this is the idea behind the thread. To help out others
Click to expand...
Click to collapse
I know mate. And that's a good thought (and initiative).
One more question, what do you call 'massive drainage'? 5,10,20,50% overnight in 8 hours?
exCluSive1 said:
I know mate. And that's a good thought (and initiative).
One more question, what do you call 'massive drainage'? 5,10,20,50% overnight in 8 hours?
Click to expand...
Click to collapse
10% my friend. i really wished i did this thread when i had my phone and to be able to post shots of what i am talking about..that way it would make it more clearer to everyone. like i said i will be doing more testing and prove my theories that what other people have tried worked.
so once i get my phone back i will be doing the following from a fully charged battery. One to try and cause whatever wakelock i can specially the facebook one and the audiout one. Two on a second cycle i will do the following steps mentioned above and show people the difference that those steps can make and how much difference in battery i have saved
Goku80 said:
10% my friend. i really wished i did this thread when i had my phone and to be able to post shots of what i am talking about..that way it would make it more clearer to everyone. like i said i will be doing more testing and prove my theories that what other people have tried worked.
so once i get my phone back i will be doing the following from a fully charged battery. One to try and cause whatever wakelock i can specially the facebook one and the audiout one. Two on a second cycle i will do the following steps mentioned above and show people the difference that those steps can make and how much difference in battery i have saved
Click to expand...
Click to collapse
I see. I was particularly talking about that specific wakelock (specific sounds), in case you thought I was flaming this whole idea
exCluSive1 said:
I see. I was particularly talking about that specific wakelock (specific sounds), in case you thought I was flaming this whole idea
Click to expand...
Click to collapse
just google it mate. or i provided links already about it..check it out