Related
i just got my touch pro 2, it was used, but it was still new
it still even has the original plastic on the screen.
ever since ive had the phone though, everything on it is really really slow.
opening up a text, sending a text, going back to the home screen, opening up opera, clicking on the notification tab. EVERYTHING is really slow, or has some kind of lag to it. Why is this happening? What can i do to fix it?
This is really bothering me, and im about to trade for another phone because i cant take it. It takes me 5 minutes to send a text message, after i hit the send button.
ANY help is appreciated, thanks!!
First thing you want to check is which ROM is running on the device. Is it stock or a cooked ROM. Which version TP2 do you have? is there a carrier logo on it? The more information you can provide about the hardware/software on the device the better we can help you.
its the stock ROM. Original T-Mobile branded version. Its pretty much new out of the box it seems.
Since you just got it, and someone may have been using it before. i would suggest hard reset first off to remove any junk the previous user may have installed.
ok thats sounds like a good idea, how would i go about it?
(sorry for some of the questions i have been / will be asking, i just came from android to WinMo, so im completely lost)
1. While the HTC Touch Pro 2 is off, press and hold Talk/Send, End and Power until you see a message on the screen about deleting all data.
2. Release the buttons after the message appears.
3. Press the Volume Up button.
once you are done with that I would recommend disabling push internet and also the Dynamic Resource Proxy...
nayr1482 said:
once you are done with that I would recommend disabling push internet and also the Dynamic Resource Proxy...
Click to expand...
Click to collapse
The T-mobile stock ROMs do not have push pages and as such I do not believe it makes use of the Dynamic Proxy.
I came from an Android device (briefly, in between my Wizard to Rhodium). The screen itself is different. This may be part of the lag you are experiencing. I actually prefer the WinMo platform over the Droid one, as it feels more responsive and stable to me. My friends however, who have the the G3 or iPhone hate my Rhodium...so again, I suspect that if, after hard booting your device, it still feels laggy, it may be the differences in how the screen responds versus a Droid screen. The Devs here could explain it in much better techie terms than I.
There is a thread here pushing for a Droid port over to the Rhodium, and I sit here scratching my head asking why. I truly believe that much of it is perception, mine being that Android just isn't for me. You may consider checking out that thread and seeing if the port over is any closer to happening.
In the meantime, I have heard that the Energy roms are quite stable and fast, so you may consider flashing one and seeing if maybe your response issues are handled. Be sure to read up on unlocking/flashing your device first so you don't brick it.
I'm sorry I'm not much help here. I do think though that perhaps some of the issue may be the screen...I could be way off base here too, though.
I am testing out the Dymanic Resource Proxy hack to see if it makes any difference to me. Will let you know what i find, so far idling at about 55%
update:
well, i went ahead and did a system restore, it was faster, but still not to my liking, so iwent ahead and flashed a ROM to make one final test. i went ahead a flashed energy ROM, and i have to say, i very much enjoy it now. ALOT faster, much smoother transition between applications, accelrometer works alot better, an overall greatly improved experience.
thanks to everyone that helped me!
one last question though, after flashing the ROM, my ALT key doesn't seem to work. Any fix? i would do a search, but im already typing a response, so i thought i would go ahead and include it here.
http://forum.xda-developers.com/showthread.php?t=550559, should have your solution It's a sticky on this sub-forum a few posts on top of your post =p
b1ck132 said:
http://forum.xda-developers.com/showthread.php?t=550559, should have your solution It's a sticky on this sub-forum a few posts on top of your post =p
Click to expand...
Click to collapse
haha thank you, i knew it would probably be somewhere obvious, but i was just responding and figured i would go ahead and throw it in there
Hi,
Attached is a build of Honeycomb for DesireHD, I managed to find this by browsing the net and take no credit for creating it whatsoever.
I'm hoping one of our more clever members can do what needs doing with this to make it work on our beloved HD2.
Thanks.
http://www.multiupload.com/DLJ46IG55Q
Nobody is interested? Or is it a fake? Can anybody (with the right skills and tools) check this please.
???
Are you serious ?! someone can verify that build or can you make some screenshots ?
Could be, but dont know if his link is trusted.
http://tweakers.net/nieuws/72741/ontwikkelaar-installeert-android-honeycomb-op-htc-desire-hd.html
Also wrong section.
honeycomb is not really made for phones as I understand?
FrAsErTaG said:
honeycomb is not really made for phones as I understand?
Click to expand...
Click to collapse
Yes that's what i read
but hey
DFT can make it a reality as usual XD
If you check the link in my post, ist already ported and working.
There is a video there to, its a Dutch site though.
Yes its ported to EVO & is working..!!!
PS: - I haven't tried yet though
The LINK
[ROM-DEV] ||Honeycomb on EVO||Alpha||SpyderComb||Honeycomb Android 3.0||2/17/2011||
http://forum.xda-developers.com/showthread.php?t=957842
It is a genuine link, I haven't tested because I don't have a desire, I have seen video footage of it running from the same source and I have inspected the file which looks about right to me, just needs correct drivers and repackaging I believe. If only I knew how to do the repackaging and which driver files were needed I would do it myself.
Yup this is built for tablets and not phones but there are a few tablets with screens not much bigger than our hd2's. It may not even be practical for daily use but I'd love to have a play. : )
Sent from my HTC HD2 using XDA App
May be we can have a working one on our HD2's, can't say, DFT & the cheifs here ROCK..!!!
I like the lock screen & the home screen, it a really an evolution from the older Android Versions..!!!
So hope we get a working port pretty soon..!!!
here's a video for DesireHD release..
http://www.youtube.com/watch?v=t5-yO4FOAvI&feature=player_embedded#at=75
I know that mdeejay or one of the other devs on here could get it working in no time, I just don't have the knowledge, fingers crossed.
Sent from my HTC HD2 using XDA App
the expert cooks should be working to port it to the archos tablets
Booted it on my HD2, but... it lags, nearly nothing works by now etc, and it's hard to hit interface buttons... not sure this will be really useful, but I'll try to work on it
Don't ask for upload please...
Can someone point me in the direction for a tutorial for creating clockwork mod roms please?
this would be probably better suited for viewsonic g tablet
Probably, would still be fun to play with on my phone though.
Sent from my HTC HD2 using XDA App
I haven't had any fun
Nothing really works, sdcard mount, wifi, radio, bluetooth, etc etc, even some buttons are not properly mapped, so i couldn't turn the screen off, i haven't took a closer look though.
Default launcher, and some interface parts lag SO much
But this will really take time, cause everything should be fixed, and cause it's still preview SDK - not really worth it.
imilka said:
I haven't had any fun
Nothing really works, sdcard mount, wifi, radio, bluetooth, etc etc, even some buttons are not properly mapped, so i couldn't turn the screen off, i haven't took a closer look though.
Default launcher, and some interface parts lag SO much
But this will really take time, cause everything should be fixed, and cause it's still preview SDK - not really worth it.
Click to expand...
Click to collapse
i appreciate you taking the time and look forward to IF anything can be done.
Would someone mind posting the half working version so I can have a look please?
Sent from my HTC HD2 using XDA App
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
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?
Hi,
I would like to know if it is possible via an app or mod to add or remove or change the position of the capacitive buttons.
Currently the stock M8 Sense format is Back, Home, Switcher.
I would like to know if it is possible to make it Back, Menu, Home, Switcher, Search.
Please let me know I am dying for a regular menu and search button!
JaY iZz BaKk said:
Hi,
I would like to know if it is possible via an app or mod to add or remove or change the position of the capacitive buttons.
Currently the stock M8 Sense format is Back, Home, Switcher.
I would like to know if it is possible to make it Back, Menu, Home, Switcher, Search.
Please let me know I am dying for a regular menu and search button!
Click to expand...
Click to collapse
Why not just get to used to how Android is changing and not live in the past? It's not hard to get your head around it and it'll be easier then asking for mods people just don't want any more...
EddyOS said:
Why not just get to used to how Android is changing and not live in the past? It's not hard to get your head around it and it'll be easier then asking for mods people just don't want any more...
Click to expand...
Click to collapse
Android is all about customization and personalisation.
It doesn't hurt to ask and see if it is possible, because it has been done before. So no need for such a douchebag kind of response.
Hellscythe said:
Android is all about customization and personalisation.
It doesn't hurt to ask and see if it is possible, because it has been done before. So no need for such a douchebag kind of response.
Click to expand...
Click to collapse
OK, my response might've come across a bit 'off' but the principal is still the same. If the mod was wanted by the community then someone would've made it. Xposed might already have something similar available so might be worth looking at that option but I'd personally say it's better off to just get used to what Google are doing to make Android better (yes, better) and accept the change...
EddyOS said:
OK, my response might've come across a bit 'off' but the principal is still the same. If the mod was wanted by the community then someone would've made it. Xposed might already have something similar available so might be worth looking at that option but I'd personally say it's better off to just get used to what Google are doing to make Android better (yes, better) and accept the change...
Click to expand...
Click to collapse
the dude just wants an extra search and menu button because that's his preference. Like I said before, Android is all about personalization and customization. If you don't like a change that has been applied, then there are possible methods it can be altered. Telling someone to "accept the change" is contrary to the purpose of XDA and Android. Heck if a guy wanted a gingerbread style status bar or something are you going to tell him "no, just accept the change, it was for the better?"
You shouldn't, because it's all about preference. While it might be better for the majority of the user base, he might not like it and there is nothing wrong with asking if someone has devised a method to apply that change, ESPECIALLY because he posted in the Q/A section.
EddyOS said:
Why not just get to used to how Android is changing and not live in the past? It's not hard to get your head around it and it'll be easier then asking for mods people just don't want any more...
Click to expand...
Click to collapse
It's about preference...I never demanded someone make it or complain about it not being available.
Just asking to see if it is available, no need for this type of response
check these out. just stick it on the back of the case and program buttons for what you want.
http://www.cnet.com/news/dimple-nfc-sticker-adds-four-physical-buttons-to-your-android-device/