Related
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?
Tired of the wait and the reviews coming back that the battery isn't all that great compared to the Galaxy Nexus (which I have and totally sucks haha).
1. I saw a screen shot with on screen buttons, is this a ROM feature or something that can be flashed?
2. Currently I don't think any ROM has multiwindow and wifi calling together but when the official multiwindow update comes out, we should see both features included in a ROM right?
3. I saw the phone in person and it was just HUGE. I don't mind the physical size but everything on the screen just looked big, like it was blown up. Is there anyway to include more on the screen?
4. If i install a launcher (Apex Launcher), will I lose any S-Pen features?
tracerit said:
Tired of the wait and the reviews coming back that the battery isn't all that great compared to the Galaxy Nexus (which I have and totally sucks haha).
1. I saw a screen shot with on screen buttons, is this a ROM feature or something that can be flashed?
2. Currently I don't think any ROM has multiwindow and wifi calling together but when the official multiwindow update comes out, we should see both features included in a ROM right?
3. I saw the phone in person and it was just HUGE. I don't mind the physical size but everything on the screen just looked big, like it was blown up. Is there anyway to include more on the screen?
4. If i install a launcher (Apex Launcher), will I lose any S-Pen features?
Click to expand...
Click to collapse
1. Not that I know of.
2. Yes.
3. You will get used to the size in a week. after a week I felt the pone was perfect and other phones felt like toys. especially my old 4S.
4. Not at all.
If rooted you can add the following line to your build.prop to get the on screen navigation buttons
qemu.hw.mainkeys=0
Sent from my SGH-T889 using xda premium
tracerit said:
Tired of the wait and the reviews coming back that the battery isn't all that great compared to the Galaxy Nexus (which I have and totally sucks haha).
1. I saw a screen shot with on screen buttons, is this a ROM feature or something that can be flashed?
2. Currently I don't think any ROM has multiwindow and wifi calling together but when the official multiwindow update comes out, we should see both features included in a ROM right?
3. I saw the phone in person and it was just HUGE. I don't mind the physical size but everything on the screen just looked big, like it was blown up. Is there anyway to include more on the screen?
4. If i install a launcher (Apex Launcher), will I lose any S-Pen features?
Click to expand...
Click to collapse
1) see post above
2) yes. It is possible now with wildchild's XquiziT rom, flash v4 set up wifu calling, flash v6 for multi Window. Just dont wipe between fladhes and u get both.
3) set text size to small helps.
4) only thing you lose is page buddy and to me its annoying anyway.
thanks for the replies. i'm gonna drop by T-Mobile today to check it out again before the Cyber Monday sale ends.
I only just recently got my Note II and it has got ARHD on it, which I installed because it's a rom based on samsung software with no comptability issues and great battery life.
I also have a Galaxy Nexus and I noticed a few "problems" the Note 2 has and the older Nexus doesn't:
the browser on the Note 2 looks okay but the pointer precision is just very bad. To give an example: if you swipe your finger up or down vertically for a few centimeters, and then you start sliding diagonally (without having lifted off your finger off the screen in the meanwhile), it will only continue to keep scrolling vertically, it won't "follow" your left or right (or diagonal) movement. When you lift off your finger from the screen, retouch it and then scroll diagonal right away it will follow the movement. I find this very annoying, it prevents me of having a smooth browsing experience. My older Nexus with stock android 4.2.2 and stock browser is smooth as butter and follows my swiping movements 1 to 1..
I tested Dolphin browser, Maxthon.. all still bad pointer precision.. Chrome seems to be the least bad of all the browsers, but then on the other hand I find it very choppy.
PS. I already tried an AOSP/CM rom (Sentinel ROM), and there the browser was smooth, yet, non-touchwiz roms are not bugfree and the battery life is nowhere as good as with a samsung based rom.. And especially that last factor is really important to me. (Unless anyone can advise me a bugfree AOSP rom with batterylife that is as good as a samsung based rom).
SOLVED, SOLUTION IN POST #15
Then something else that annoys me quite a bit: when the screen is off and I press the wakebutton, it takes like 1 to 2 seconds until it actually wakes.. I've read I'm not the only one with this problem but I find it kind of unacceptable for a quad core phone with 2GB of ram.. Same problem when you are in an application and you press the homebutton to go to the homescreen, it sometimes takes like a second or more too.. Once again, stuff like that on my simple dual core nexus with half the amount of ram doesn't happen.
UNDERLINED PART SOLVED, SOLUTION IN POST #3 (thanks Kremata)
Then the good stuff has to be said too: homescreen-scrolling is insanely smooth, watching videos is awesome, the camera is great (so is the samsung camera app) and not to forget, the battery life is a revelation to me, I get through the day easily with hardcore use of the phone (that cannot be said of my old Nexus..).
I really like the Note II, but these few problems really crash the party for me.. Also I never thought I'd say it as a Nexus-fan but I generally find Touchwiz pretty cool and suiting on the Note 2.. So I'd prefer to stay on a samsung based rom like ARHD if possible.
Hope there's some experts here who can give me advise on how to handle these little problems.
For the record, I managed installing the AOSP browser, and the bug is still there. So it must be rom/kernel related, not app-related..
The HOME button problem is not a bug. It is because you have set your S-voice to open by double pressing the Home button. So the lag comes from TW waiting for a second press before doing anything.
Just uncheck "Open via the Home Key" in S-voice setting.
For the browser thing I don't know. I never felt it was a problem for me.
Kremata said:
The HOME button problem is not a bug. It is because you have set your S-voice to open by double pressing the Home button. So the lag comes from TW waiting for a second press before doing anything.
Just uncheck "Open via the Home Key" in S-voice setting.
Click to expand...
Click to collapse
One problem solved already, thanks for that!
I placed a video of the pointing precision problem on youtube. Btw I checked if the touchscreen is ok by using "show touches", and it followed my touches 100% perfectly, so it's not the phone, it's definitely some software problem..
This is the video
Could anyone with a samsung-based rom try to reproduce the above problem and see if it happens or not ? If not, could you tell me what rom + kernel you are using, would be much appreciated..
I repeat that when I tried an AOSP rom on my Note II, this issue did not happen.
I'm on DLL4 and before this was on 4.1.1 and do not have this issue.
whisky_ said:
I'm on DLL4 and before this was on 4.1.1 and do not have this issue.
Click to expand...
Click to collapse
Could you give me more information on DLL4 ? Maybe a link to such rom, etc. How is your battery life ?
PS. I have the international (european) version.
wtr_dhd said:
Could you give me more information on DLL4 ? Maybe a link to such rom, etc. How is your battery life ?
PS. I have the international (european) version.
Click to expand...
Click to collapse
I have the exact same thing on my phone (ARHDv18). A work around is to start with a diagonal instead of a vertical line then it works fine
Kremata said:
I have the exact same thing on my phone (ARHDv18). A work around is to start with a diagonal instead of a vertical line then it works fine
Click to expand...
Click to collapse
Thanks, I'll sleep a bit better now tonight
Yes I know.. but it's very annoying.. Since years I used stock android/AOSP, now I went to the dark side P) to use a TW device, so this "problem" kind of annoys me.. I wonder if one of our awesome developers would be able to make a samsung based TW rom with an AOSP-like smooth browsing experience..
wtr_dhd said:
Thanks, I'll sleep a bit better now tonight
Yes I know.. but it's very annoying.. Since years I used stock android/AOSP, now I went to the dark side P) to use a TW device, so this "problem" kind of annoys me.. I wonder if one of our awesome developers would be able to make a samsung based TW rom with an AOSP-like smooth browsing experience..
Click to expand...
Click to collapse
I just realized this problem. I'm using Crash ROM, and sometimes it will happen like in the video, but sometimes it work perfectly.
So weird that I seem to be the first one remarking this problem as imo it's quite annoying, and I'm definitely not alone here.
wtr_dhd said:
So weird that I seem to be the first one remarking this problem as imo it's quite annoying, and I'm definitely not alone here.
Click to expand...
Click to collapse
You must be more picky than most of us as I never noticed this before either.
Kremata said:
You must be more picky than most of us as I never noticed this before either.
Click to expand...
Click to collapse
You don't forget the good stuff of stock android! But the samsung rom has some pretty cool features too..
HOORAY.
With "Chrome Beta" the swiping "bug" is not present! /me happy
Now my Note 2 is "perfect"
This is my first time I am ever posting and I am extremely anxious and shy about doing this or if I even make myself understandable and as helpful as I can..... Please if there is something that doesn't make sense please let me know so I can try to be a little more clear....
Now........To Begin
:victory:
I had a previous Sprint Samsung Galaxy S2 SPH-D710 that did not have this problem at all but I traded it for a black one because I did not like having a white phone and that's where my problems began....I had known the phone had a pressing button problem but I did not know what it was at the time or what it was called. But I was sure there was a way to fix it somehow. As soon as I had the phobe in my hands I saw how horrible it was.....It did not let me do anything not even for 30 seconds without the menu, back buttons, and I was upset because since I had to reinstall a new ROM on this phone (which I don't mind that's the fun part) but the keys kept going off every couple of seconds so I decided to look into finding a way to fix it and I did kinda. And I will post the link to the first one too because it can be useful and work for someone else and if it wasn't fir that post I wouldn't have thought of my fix.
Anyway here is the link to the first one : http://forum.xda-developers.com/showthread.php?t=
I followed these steps and basically what it is, is a method where you disable your hardkey that is causing you problems and switching it to the search button since most of us really don't use the search key anyway. But I won't go much into detail the post above goes more in depth. In the beginning it actually worked but then I noticed that the back key started pressing itself and then the menu still presses itself and even now and the search button which was converted to the new menu so I got upset and exasparated because to even do this method took me literally 2 hours because the damn keys wouldn't stop pressing themselves. And then I thought of another method which to me proved easier than that and does work. I simply used the same method but when I got to the General.kl instead of disabling one key I disabled all 4 and bang problem solved! But BEFORE that you need to make sure you have already installed an app where you can get your hardkeys on your screen and set it up to where you kniw your keys all work * OH AND YOU NEED TO BE ROOTED FOR THE SETTINGS FOR MENU AND BACK WORK! *. And I found a really good and free app in the market that is easy to use and wont get in the way of your screen while typing and customizable. It is called "Floating Toucher" and once installed and set up and disabled keys in General.kl and rebooted phone everything was working fine!!!! AND IT WORKED JUST FINE YOU JUST HAVE TO GET USED TO NOT TOUCHING KEYS ANYMORE AS THEY DON'T WORK BUT ITS TRUSTHWORTHY!....
Anyway I when all this happened I had GB27 4.1.2 and I wanted an upgrade so I flashed to Revolt JB ROM 4.3.1 (will post link to this ROM if you are interested in this method) and after that because the phone reset itself the hardkeys were enabled again. So because I it was a new ROM for me I looked in depth at their settings and there is where I found my solution!
1. Go to your settings and you go to Revolt Control.
2. When you are there you will see they have extra settings for the phone.
3. Scroll down to: Pie Controls
4. Click on the first setting that says: Pie Controls/ Allows navagation and status report and enable it.
5. Customize the settings how you want then to be to your liking!
6. Go back to previous menu.
7. Scroll down to: Soft Keys Options
8. Click on: Enable Soft Keys Options
9. You will notice all four of your hard keys are there including the setting when you long press them. Simply click on each one and press blank on all of them.
10. Then you go to previous screen and reboot and there! Easier than having to install over apps or disable keys! Its in the settings already and I am extemely happy now! No more Phantom Ghost Key!!!
The link for Revolt if anyone wants to change to ROM is : http://forum.xda-developers.com/showthread.php?t=2238252
And I hope this helps someone!
Man, you have a lot of patience posting a guide in a wrong device forum... You link to a ReVolt ROM for HTC Rezound, and here we have Samsung Epic 4G, which doesn't have ReVolt at all (all we have is a buggy CM10.2).
Sent from Samsung Captivate Glide @ CM10.2
Yes I have a Sprint Samsung Galaxy S2 SPH-D710 which is commonly known also as Epic 4G. But I see what you mean I accidently put the wrong link! I will update the proper link ASAP!!!!!
I'm not surprised I made a mistake my first post..... Thanks for letting me know!!!
Sent from my SPH-D710 using XDA Premium 4 mobile app
Updated Proper Link to Rom!
I have updated the proper link on my post but just in case I will post it here again!!! Thanks for pointing that out!!! How embarrassing
Revolt Rom : http://forum.xda-developers.com/showthread.php?t=2238252
:angel:
Innocent_Psycho said:
Yes I have a Sprint Samsung Galaxy S2 SPH-D710 which is commonly known also as Epic 4G. But I see what you mean I accidently put the wrong link! I will update the proper link ASAP!!!!!
I'm not surprised I made a mistake my first post..... Thanks for letting me know!!!
Sent from my SPH-D710 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Still the wrong device forum... You have an Epic 4G Touch (SPH-D710). This forum is for Epic 4G (SPH-D700), a totally different device with a slide-out keyboard. There's a separate forum for your device.
Sorry if all these sound rude, I simply wanna guide you to the right place
Sent from Google Nexus 4 @ CM11
OHHHHHHH I SEE I'VE ALWAYS GOTTEN CONFUSED ABOUT THE DIFFEEENT S2 MODELS AND WHAT NOW!!! Honestly it was much harder when I first trying to even learn about root and try..... Before this phone was a BOOST Samsung Galaxy S2 SPH-D710BST and proper files to flash was extremely hard to find. But I flashed it to Sprint and it was slightly easier then. But yea I do continue to get confused with these names especially cuz those 2 sound so similar. ...darnit !
Well I looked for their forum and its under maintenance so I have to wait....
Sorry for the mistake!
And no you're not being rude in the least thank you sooooo much !!!!
Sent from my SPH-D710 using XDA Premium 4 mobile app
Since the official ROM thread is closed for the foreseeable future, I figured those of us who are running, not running away from, the AOSP Android 7 ROM by @Schischu need a place to discuss bugs, find solutions, etc.
Of course, given the situation, we can't officially recommend the ROM, no matter how much we might love it. So we assume that if you are posting here, you already have the ROM installed, and have read all of the original thread.
Schischu will probably not be helping out with this thread. I haven't even asked him about starting it. I have had no part in the ROM's development, so this is strictly UNOFFICIAL. Think of it as a twelve-step program for those who have been left hanging by this situation. Hopefully some of the guys from the original thread who are real devs will be nice enough to chime in. And, hopefully we will inspire Schischu to return to the development of the ROM and resolution of whatever underlying issues that led to the suspension of the old thread.
I think we should start with a known bug list, and I'll come back a little later and post a few that I am aware of.
My personal bug list:
T-700
·Graphics glitches when changing screen orientation or swapping between apps
·Certain streaming apps (USA Now, Syfy Now in my case) won't stream video
·Slow charging while the tablet is on
·Camera Apps freeze (Stock, better camera) when trying to record video, don't access full camera resolution
·I'll add more if I find/think of any
T-800
·YouTube videos stutter while playing
I may try to keep this as a comprehensive list, but I won't always be able to, so no promises.
What we're the issues that caused the thread to be closed? I'm running it on a T800 and it's been fine. Was it security issues or legal/admin issues?
Sent from my SM-T800 using XDA-Developers mobile app
touchee said:
What we're the issues that caused the thread to be closed? I'm running it on a T800 and it's been fine. Was it security issues or legal/admin issues?
Sent from my SM-T800 using XDA-Developers mobile app
Click to expand...
Click to collapse
Update : here's the answer to the question I posed below. Apparently the AOSP MM will not get further develop either. The issues all surround a GPL compliance complaint which the Dev denies. See: http://forum.xda-developers.com/showthread.php?p=68673187
I agree and that the thread's close message was rather vague. Is the Dev continuing to support his aosp MM ROM? I may just return to that one (nandroid backup) as the YouTube stutter is too annoying if it won't be fixed for a very long time. I liked the Nexus feel of this tablet over going the Samsung stock route.
Sent from my SM-T800 using XDA Premium HD app
Kindergarden
WTF tha's kinda childish behav. Man don't acting like that, blowing out the things you don't like and discuss, we are humans, we can talk ! in my opinion it's a really sad situation and for all the other too.
Meet and TALK ! Thanks
3DSammy said:
Update : here's the answer to the question I posed below. Apparently the AOSP MM will not get further develop either. The issues all surround a GPL compliance complaint which the Dev denies. See: http://forum.xda-developers.com/showthread.php?p=68673187
I agree and that the thread's close message was rather vague. Is the Dev continuing to support his aosp MM ROM? I may just return to that one (nandroid backup) as the YouTube stutter is too annoying if it won't be fixed for a very long time. I liked the Nexus feel of this tablet over going the Samsung stock route.
Click to expand...
Click to collapse
Sounds like he's not doing any development on either of them for the time being. I'm sticking with the N ROM for now, even with the problems. YouTube has been fine for me, fwiw.
It's pure speculation, but I have to guess that someone is accusing him of using code from their version of the kernel. If there are usability or stability issues with the kernel, then that's what I'm hoping we can figure out with this thread, and if Schischu does not return to working on it, then maybe we can install an N-friendly kernel from another dev when one comes available.
amateurhack said:
Sounds like he's not doing any development on either of them for the time being. I'm sticking with the N ROM for now, even with the problems. YouTube has been fine for me, fwiw.
It's pure speculation, but I have to guess that someone is accusing him of using code from their version of the kernel. If there are usability or stability issues with the kernel, then that's what I'm hoping we can figure out with this thread, and if Schischu does not return to working on it, then maybe we can install an N-friendly kernel from another dev when one comes available.
Click to expand...
Click to collapse
The MM6 is very stable but multiwindows that any mods can't add on marshmallow is very useful on a tab. I use N7 on my t800 with the bugs (yt bug too ) but for me when I update to a new Android version and use it for a while, downgrade is very hard I will continue use N7 anyway and hope to see schischu coming back for a simple reason is that he's roms are very popular.. future will tell us
So you gotta love this, I have tried twice to send the dev a PM regarding the closing of the other thread, once with the app on my Tab S, and once just now on the web. Neither message shows up in my sent items. Is this normal?
On my T-800, I have the following minor issues which I have not really tried to troubleshoot (with the exception of #3):
1) graphical glitches on rotate and power off
2) not able to see all widgets provided by one app - specifically BeautifulWidgets - I can scroll through their widgets, but it stops half way through one icon and doesn't scroll to the rest
3) I was experiencing about 25% less battery life relative to 5.0.2 (I didn't try MM), but this seems to have settled down now and I'm getting close to what I saw on 5.0.2
4) GPS appears to get location, but GPS Status App seems limited to 4 satellites and does not indicate a fix has been obtained
5) I have a hard time getting into Recovery mode - the power option built in the ROM and Quick Boot app - both reboot to recovery goes to black screen and frozen tab - have to do Vol Down - Home - Power combo to get it to come back alive, but it comes to the Download mode screen. If I cancel out of Download mode, it sometimes goes to Recovery, but more often goes to black screen and frozen again. If I try Vol Up-Home-Power combo nothing happens.
EDIT: for #5 - i waited a bit longer on the black screen and hit power - recovery popped up. This may be related to a historical screen time out issue which has already been identified elsewhere
EDIT 2: for #5 - I seem to be stuck - I made it into recovery after a number of tries and turned off the screen timeout option. Now it won't boot into either recovery or system - just goes to black screen again. I can still get into Download mode so I'll have to wait until I can plug into a PC at home and try ADB fastboot - does anyone have any other suggestions?
amateurhack said:
Sounds like he's not doing any development on either of them for the time being. I'm sticking with the N ROM for now, even with the problems. YouTube has been fine for me, fwiw.
It's pure speculation, but I have to guess that someone is accusing him of using code from their version of the kernel. If there are usability or stability issues with the kernel, then that's what I'm hoping we can figure out with this thread, and if Schischu does not return to working on it, then maybe we can install an N-friendly kernel from another dev when one comes available.
Click to expand...
Click to collapse
agree with you N is working 100 % for me. Schishu on N or MM it's just a repetition
oh yeah i'm on Slim6 now
---------- Post added at 08:15 PM ---------- Previous post was at 08:09 PM ----------
amateurhack said:
So you gotta love this, I have tried twice to send the dev a PM regarding the closing of the other thread, once with the app on my Tab S, and once just now on the web. Neither message shows up in my sent items. Is this normal?
Click to expand...
Click to collapse
found it on another thread
schishu went ballistic over the fact that a lot of people were sending money to get their devices on nougat which led to a half bake ROM with a lot of problems, schishu being who he is, never give any support and just let everyone deal with their problems.. Therefore the moderator said enough is enough and just closed the thread until schishu get his sh** together... And it's not me who've made a complaint..... Schischu did a very good job on the MM6 , it's only a good guess.......
kaodd said:
,,,found it on another thread
schishu went ballistic over the fact that a lot of people were sending money to get their devices on nougat which led to a half bake ROM with a lot of problems, schishu being who he is, never give any support and just let everyone deal with their problems.. Therefore the moderator said enough is enough and just closed the thread until schishu get his sh** together... And it's not me who've made a complaint..... Schischu did a very good job on the MM6 , it's only a good guess.......
Click to expand...
Click to collapse
I'am a person who donated to Schichu after his efforts with Nougat so quickly created while Samsung at that point still had not made Marshmallow readily available. I did that not as much for his Nougat ROM but because I'd been using his mature AOSP Marshmallow ROM for months already at that point. I find it difficult to see the words "half baked" and "get his act together" on a ROM clearly marked as ALPHA. That is simply not fair as this developer put out monthly security updates which again is better than Samsung manages. I do not regret my donation as I reverted to his AOSP MM from a nandroid backup just hours ago. Samsung stock Marshmallow does not support Substratum theming which I find manditory and is slower than the Nexus like AOSP build..
kaodd said:
found it on another thread
schishu went ballistic over the fact that a lot of people were sending money to get their devices on nougat which led to a half bake ROM with a lot of problems, schishu being who he is, never give any support and just let everyone deal with their problems.. Therefore the moderator said enough is enough and just closed the thread until schishu get his sh** together... And it's not me who've made a complaint..... Schischu did a very good job on the MM6 , it's only a good guess.......
Click to expand...
Click to collapse
That seems odd that it would be shut down for being half-baked! The 1st page of the ROM thread clearly states it is "Alpha". For an alpha, it certainly ran well - others clearly had unreasonable expectations for an alpha status ROM.
slow1234 said:
On my T-800, I have the following minor issues which I have not really tried to troubleshoot (with the exception of #3):
1) graphical glitches on rotate and power off
2) not able to see all widgets provided by one app - specifically BeautifulWidgets - I can scroll through their widgets, but it stops half way through one icon and doesn't scroll to the rest
3) I was experiencing about 25% less battery life relative to 5.0.2 (I didn't try MM), but this seems to have settled down now and I'm getting close to what I saw on 5.0.2
4) GPS appears to get location, but GPS Status App seems limited to 4 satellites and does not indicate a fix has been obtained
5) I have a hard time getting into Recovery mode - the power option built in the ROM and Quick Boot app - both reboot to recovery goes to black screen and frozen tab - have to do Vol Down - Home - Power combo to get it to come back alive, but it comes to the Download mode screen. If I cancel out of Download mode, it sometimes goes to Recovery, but more often goes to black screen and frozen again. If I try Vol Up-Home-Power combo nothing happens.
EDIT: for #5 - i waited a bit longer on the black screen and hit power - recovery popped up. This may be related to a historical screen time out issue which has already been identified elsewhere
EDIT 2: for #5 - I seem to be stuck - I made it into recovery after a number of tries and turned off the screen timeout option. Now it won't boot into either recovery or system - just goes to black screen again. I can still get into Download mode so I'll have to wait until I can plug into a PC at home and try ADB fastboot - does anyone have any other suggestions?
Click to expand...
Click to collapse
I hope that works out. Please give an update when you can. I will add yours to the list after we hear back.
amateurhack said:
I hope that works out. Please give an update when you can. I will add yours to the list after we hear back.
Click to expand...
Click to collapse
Access to recovery is very inconsistent - I don't know much about this - maybe I have a corrupt bootloader or something.
I kept rebooting to Download mode with Power-VolDn-Home combo and then cancelling it - finally it went into Recovery and I could reboot from there to System.
I'm kicking myself- I should have turned screen timeout back on in TWRP as it seemed I could get into recovery more frequently (but still inconsistently) after cancelling out of download mode.
slow1234 said:
Access to recovery is very inconsistent - I don't know much about this - maybe I have a corrupt bootloader or something.
I kept rebooting to Download mode with Power-VolDn-Home combo and then cancelling it - finally it went into Recovery and I could reboot from there to System.
I'm kicking myself- I should have turned screen timeout back on in TWRP as it seemed I could get into recovery more frequently (but still inconsistently) after cancelling out of download mode.
Click to expand...
Click to collapse
I've never been good at getting those button combinations to work. I always use the power reboot menu, the reboot menu in either TWRP Manager or Titanium, or use adb commands. I guess I'm just not coordinated enough. =) Hopefully you'll get it figured out.
slow1234 said:
That seems odd that it would be shut down for being half-baked! The 1st page of the ROM thread clearly states it is "Alpha". For an alpha, it certainly ran well - others clearly had unreasonable expectations for an alpha status ROM.
Click to expand...
Click to collapse
Ok it's in alpha, alpha is half baked, Schishu, Samsung or LG it's the same for me. the xda supervisor kickt him out coz much probs as i understand .
". . . . . schishu being who he is, never give any support and just let everyone deal with their problems.. Therefore the moderator said enough . . . . "
I'm satisfied with N, so i cant complain
---------- Post added at 09:17 PM ---------- Previous post was at 09:09 PM ----------
slow1234 said:
Access to recovery is very inconsistent - I don't know much about this - maybe I have a corrupt bootloader or something.
I kept rebooting to Download mode with Power-VolDn-Home combo and then cancelling it - finally it went into Recovery and I could reboot from there to System.
I'm kicking myself- I should have turned screen timeout back on in TWRP as it seemed I could get into recovery more frequently (but still inconsistently) after cancelling out of download mode.
Click to expand...
Click to collapse
hold the buttons pressed - home-voldn-power - when u get a black screen just go to volup, u have a sec or fewer. works fine have to do it serveral times after sitting fest in dl mode. (or take out the battery LOL)
Sam Ash has posted in another thread indicating that he will reply to my questions at some point.
In other news, I hate drama.
amateurhack said:
Sam Ash has posted in another thread indicating that he will reply to my questions at some point.
In other news, I hate drama.
Click to expand...
Click to collapse
so take it as an action movie action is alway good, sometime grows a new flower up, who knows . . . .
kaodd said:
[/COLOR]
hold the buttons pressed - home-voldn-power - when u get a black screen just go to volup, u have a sec or fewer. works fine have to do it serveral times after sitting fest in dl mode. (or take out the battery LOL)
Click to expand...
Click to collapse
Thanks - I'll have to try a quicker finger. Hopefully it's that simple, but because of the issues I'm having I am not going to try to boot to recovery any time soon unless I absolutely need to!
slow1234 said:
Thanks - I'll have to try a quicker finger. Hopefully it's that simple, but because of the issues I'm having I am not going to try to boot to recovery any time soon unless I absolutely need to!
Click to expand...
Click to collapse
maybe it's coz your nickname