Related
Hello guys, I've made the question, but the Q&A section is not very visited so...
http://forum.xda-developers.com/showthread.php?t=776871
Is there a DEV that can make the light sensor become adjustable in the SENSE UI roms? like on AOSP (i think open desire has it or cyanogen)
http://twitpic.com/2k4qjz
+1 really love to have one
casca said:
Is there a DEV that can make the light sensor become adjustable in the SENSE UI roms? like on AOSP (i think open desire has it or cyanogen)
http://twitpic.com/2k4qjz
Click to expand...
Click to collapse
Which one exactly? I'm willing to take a look at it as the issue annoys me too, if someone points me to the source (but no guarantees that I might have the time or be able to do anything about it).
EDIT: Found the CM source for it.
+1 I would love to see this as well.
martino2k6 said:
Which one exactly? I'm willing to take a look at it as the issue annoys me too, if someone points me to the source (but no guarantees that I might have the time or be able to do anything about it).
EDIT: Found the CM source for it.
Click to expand...
Click to collapse
you were faster than me searching, i was out lunching and haven't saw the topic reply e-mail
if you need assistance on testing, just PM me or let me know at the topic.
It would be nice to have this working, it's so annoying...
Why the f*ck do they include a light sensor if it doesn't work properly?!even after releasing fixes!?lol
Although I think I might know the answer...
"OK, so we gave them the hardware with buggy software to keep them busy...let them(users) figure out a fix, and this way we have time to develop some even nicer phones..."
The main problem here is that since we don't have HTC Sense sources, as they are proprietary, we can't modify system settings with an application which doesn't run as part of the system.
My understanding therefore is that this can be done in two ways:
1) Writing a kernel module which sets the appropriate/specified values on boot (I don't have enough experience to do that) or modifying the default kernel values.
2) Modify values in /sys (wherever they may be hiding) which will be reset any time you reboot, and also may get overwritten by the system at will.
That's my limited understanding anyway. If anyone would like to shed more light on this then please feel free to, or any other ways how this could be achieved...
Moved to Q&A. Please don't post question threads in Development.
fair enough
could we simply start an "official light sensor level developement for sense UI" thread or something like that ?
+1 guys we really neeeed that **** ;p
tks for your work !
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 everybody,
I have an annoying problem using roms based on Android 4.1.2 . I've tried codefireX and Jellytime. The same behavior has been noticed on both roms : there are main vertical thin stripes on the screen, falling from top to bottom, as if pixels were streaming. Most of stripes are visible on left and right parts of the screen, almost not in the middle. When I take a screenshot, problem is absolutely invisible. It can only be viewed on the touch screen directly.
When I tap on the sides of the phone, I have the impression that the stripes are lightly blinking or sparkling.
When I rotate the phone, stripes are not rotating. They still are going from the true top of the phone to the bottom.
And finaly, when I reinstall another rom, based on Android 4.0.4 (with or without Sense, suchas IceColdSandwich or ViperDHD), the stripes disappear.
Does anyone know anything about that ? or even heared something like that ?
Thanx a lot in advance,
Tom.
(sorry for my poor english )
TomVenom said:
Hi everybody,
I have an annoying problem using roms based on Android 4.1.2 . I've tried codefireX and Jellytime. The same behavior has been noticed on both roms : there are main vertical thin stripes on the screen, falling from top to bottom, as if pixels were streaming. Most of stripes are visible on left and right parts of the screen, almost not in the middle. When I take a screenshot, problem is absolutely invisible. It can only be viewed on the touch screen directly.
When I tap on the sides of the phone, I have the impression that the stripes are lightly blinking or sparkling.
When I rotate the phone, stripes are not rotating. They still are going from the true top of the phone to the bottom.
And finaly, when I reinstall another rom, based on Android 4.0.4 (with or without Sense, suchas IceColdSandwich or ViperDHD), the stripes disappear.
Does anyone know anything about that ? or even heared something like that ?
Thanx a lot in advance,
Tom.
(sorry for my poor english )[/QUOTE
Yes i have noticed that too. It seems to be a kernel issue not compatible with the phone. Forinstance if you flash lets say any 3.0.xx kernel onto icecoldICS rom you will get the lines just as in JB rom. Read that someone is trying to fix it so just keep your fingers x:crying:
Click to expand...
Click to collapse
AKK1983 said:
Yes i have noticed that too. It seems to be a kernel issue not compatible with the phone. Forinstance if you flash lets say any 3.0.xx kernel onto icecoldICS rom you will get the lines just as in JB rom. Read that someone is trying to fix it so just keep your fingers x:crying:
Click to expand...
Click to collapse
Hello,
thanks for your answer.
If it could be a kernel issue, why am I feeling so alone ?
Question about Kernels : is it possible to download Kernels Alternatives ?
TomVenom said:
Hello,
thanks for your answer.
If it could be a kernel issue, why am I feeling so alone ?
Click to expand...
Click to collapse
You are not alone. In JellyTime's issue tracker there is an open issue. Until now nothing changed. And with the new 4.2 release I wonder if JellyTime will get any stable updates in the near future. But that's the only place I found where the bug is reported. Is there an official codefireX bugtracker?
TomVenom said:
Hi everybody,
I have an annoying problem using roms based on Android 4.1.2 . I've tried codefireX and Jellytime. The same behavior has been noticed on both roms : there are main vertical thin stripes on the screen, falling from top to bottom, as if pixels were streaming. Most of stripes are visible on left and right parts of the screen, almost not in the middle. When I take a screenshot, problem is absolutely invisible. It can only be viewed on the touch screen directly.
When I tap on the sides of the phone, I have the impression that the stripes are lightly blinking or sparkling.
When I rotate the phone, stripes are not rotating. They still are going from the true top of the phone to the bottom.
And finaly, when I reinstall another rom, based on Android 4.0.4 (with or without Sense, suchas IceColdSandwich or ViperDHD), the stripes disappear.
Does anyone know anything about that ? or even heared something like that ?
Thanx a lot in advance,
Tom.
(sorry for my poor english )
Click to expand...
Click to collapse
"HW overlays cause graphical issues - in settings/developer options check disable hw overlays to fix"
I think you need this....try and gime me news:good:
Superuzzu said:
"HW overlays cause graphical issues - in settings/developer options check disable hw overlays to fix"
I think you need this....try and gime me news:good:
Click to expand...
Click to collapse
Even with HW overlays of u will still get the line. Even 4.2 has vertical lines bug! As said before its a bug which was introduced aftre 3.1 realise thus after 16th August. If u flash an older rom lets say rom builds before the 16th of August the bug is not present. I strongly doubt if the bug will b fixed cause it seems to afect only a few users and am one of them. I wander why RB pr synergy dont want to fix it
I know synergye was working on it and asking for logcats. I don't think he doesn't want to fix it. He might just not know how, since his device doesn't have the bug, and needs more info (like logcats).
bananagranola said:
I know synergye was working on it and asking for logcats. I don't think he doesn't want to fix it. He might just not know how, since his device doesn't have the bug, and needs more info (like logcats).
Click to expand...
Click to collapse
How do i produce the logcats and where fo i post them? And if am correct there should be a logcat about this on issues tracker. Its sad that we aren't able to enjoy these good roms cause of this bug. Really wish someone looks at it soon
Seems like i am notallowed to post in the development threads yet. Sigh.
Anyhow: I've been using thegreatergood's CM10.1 ROM for a while now, and love it.
I am glued to its corresponding development thread, always looking for updates and workarounds for the few bugs that remain - but i think it is a bit cumbersome. Issues get repeated, some get lost along the way, and a couple of answers are hidden between a couple of other unrelated posts.
Wouldn't it be neater to have a 'real' issue tracker for this (and any other, for that sake) ROMs? Does XDA offer something like this? Could that be hosted somewhere else?
Anyhow, my issues so far:
- Bluetooth Headset profile
- Audio in video recording not working
- Photosphere unavailable
- audio stutters if screen is turned off (seems to be a CPU sleeping issue)
- Something (i am suspecting Google+, even though i am not actively using it) is filling up my SD card with gigabytes of thumbnails, which i have to delete manually
- lockscreen takes too long to appear
- from 4.2.1 to 4.2.2 the mount point of the external SD card changed again (so 'acast' cant find my downloaded podcasts)
- auto-brightness is choppy and slow
- GPS usually get a lock in an okay-ish timeframe, but always reports that it's only locked to "0 / 2 satellites"
- face unlock doesnt work (hangs when opening the camera)
That's all i can think of right now.
Still an awesome ROM,
M.
mschweini said:
Seems like i am notallowed to post in the development threads yet. Sigh.
Anyhow: I've been using thegreatergood's CM10.1 ROM for a while now, and love it.
I am glued to its corresponding development thread, always looking for updates and workarounds for the few bugs that remain - but i think it is a bit cumbersome. Issues get repeated, some get lost along the way, and a couple of answers are hidden between a couple of other unrelated posts.
Wouldn't it be neater to have a 'real' issue tracker for this (and any other, for that sake) ROMs? Does XDA offer something like this? Could that be hosted somewhere else?
Anyhow, my issues so far:
- Bluetooth Headset profile
- Audio in video recording not working
- Photosphere unavailable
- audio stutters if screen is turned off (seems to be a CPU sleeping issue)
- Something (i am suspecting Google+, even though i am not actively using it) is filling up my SD card with gigabytes of thumbnails, which i have to delete manually
- lockscreen takes too long to appear
- from 4.2.1 to 4.2.2 the mount point of the external SD card changed again (so 'acast' cant find my downloaded podcasts)
- auto-brightness is choppy and slow
- GPS usually get a lock in an okay-ish timeframe, but always reports that it's only locked to "0 / 2 satellites"
- face unlock doesnt work (hangs when opening the camera)
That's all i can think of right now.
Still an awesome ROM,
M.
Click to expand...
Click to collapse
I concur, we need a bug tracker. Although I mentioned this in the dev thread, my concern seems to have fallen in deaf ears. No one replied to my post
http://forum.xda-developers.com/showpost.php?p=37566415&postcount=95
Well, I'm in the same boat where I can't ask in the official thread so I can't ask my questions there. Lame.
Under the "working" part, it lists:
- Keyboard Keys
- Keyboard Rotation
- Virtual Keyboard (no slide yet though)
I don't fully understand what that means, and it sounds contradictory. Does the physical slide-out keyboard work or not? Its the main reason I bought this phone, so...
snarfies said:
Well, I'm in the same boat where I can't ask in the official thread so I can't ask my questions there. Lame.
Under the "working" part, it lists:
- Keyboard Keys
- Keyboard Rotation
- Virtual Keyboard (no slide yet though)
I don't fully understand what that means, and it sounds contradictory. Does the physical slide-out keyboard work or not? Its the main reason I bought this phone, so...
Click to expand...
Click to collapse
I think it means swype does not work yet bro. Has nothing to do with physical keyboard as it says clearly "virtual keyboard".
Sent from my SGH-i927 using xda premium
i agree we do need a bug tracking thread ... i'm to busy to do it myself .... are any of you interested ..
thegreatergood said:
i agree we do need a bug tracking thread ... i'm to busy to do it myself .... are any of you interested ..
Click to expand...
Click to collapse
I would be very happy to help out!
Any preferences? Or are you using e.g. github already?
M.
UPDATE: maybe we can (ab)use XDA's wiki funtionality for this? XDA should really offer an issue tracker...
Great idea. Wish I thought of it before.
I have started a brand new bug tracker thread in the general section. Feel free to post all issues and problems there. I will update the OP accordingly.
Class now, will update in a few hours!
I was thinking more of a full-blown bug tracking system, which would also help all the other ROMs. But lets five this a shot...
mschweini said:
I was thinking more of a full-blown bug tracking system, which would also help all the other ROMs. But lets five this a shot...
Click to expand...
Click to collapse
Honestly, I'm not that sophisticated. If you can, that would be great. In the meantime, we have this :good:
No worries - wouldn't be that hard to do it in a 'pro' fashion.
But: IIRC, XDA has some policy of not linking to 'competitors' websites? I might be very wrong, though!
Could any mod confirm or deny this? Could we just say "go to example.com/CM10.1" to register bugs and issues?
Also: If thegreatergood already uses some (online) source control system (e.g. github), bug tracking would be a lot easier?
Cheers,
M.
Q&A for [4.4.x]Omni Nightlies for Find 7a/7s
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [4.4.x]Omni Nightlies for Find 7a/7s. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
I installed the nightly yesterday, got everything working, things have been going great... Except for one thing - my camera isn't working! Stock camera takes an entirely blank image and no file is saved, google camera doesn't take one at all. Anyone have any clues as to why? My searches are coming up empty.
Random freezes while gaming
Everything seems perfect except those random freezes I get while I'm gaming.
I'm on 02.11 , LVM setup, clean install.
Here is the logcat i took right after a freeze if you can get anything from it
Thx,
Hi,
I'd like to use Omni with LVM enabled to unify the partitions, but is it possible to then also use Link2SD and add my external SD card to the storage pool? I have all my music on the ext SD card and my car only sees the primary drive when plugged in.
slikvik said:
Hi,
I'd like to use Omni with LVM enabled to unify the partitions, but is it possible to then also use Link2SD and add my external SD card to the storage pool? I have all my music on the ext SD card and my car only sees the primary drive when plugged in.
Click to expand...
Click to collapse
I have no idea regarding Link2SD, I've never found a valid use case for it for years.
As to the car only seeing the internal drive - that's kind of strange. MTP can access both internal and external storage, and UMS (even if it were working) would only be able to access the external card anyway (due to the internal one being ext4 even in a split configuration...)
Thanks for replying Entropy!
Maybe I could put the question another way if Link2SD isn't adequate....is there a way of including the external SDCard into the unified storage either by the LVM or another app so I just have one large volume?
With regards to the car, all I can say is that with my Nexus 4 it scanned all the music on it fine, but when I upgraded to the FInd 7a (with music on my ext SDCard) it only picks up the few songs on the internal storage. Hence my request above - although given I'd never take out the 64Gb card I'd prefer it to all be unified anyway.
Thanks
slikvik said:
Thanks for replying Entropy!
Maybe I could put the question another way if Link2SD isn't adequate....is there a way of including the external SDCard into the unified storage either by the LVM or another app so I just have one large volume?
With regards to the car, all I can say is that with my Nexus 4 it scanned all the music on it fine, but when I upgraded to the FInd 7a (with music on my ext SDCard) it only picks up the few songs on the internal storage. Hence my request above - although given I'd never take out the 64Gb card I'd prefer it to all be unified anyway.
Thanks
Click to expand...
Click to collapse
Adding the external SD to the LV pool would cause MASSIVE performance issues for the entire system.
Not sure what's going on, unless your car's MTP implementation is semi-broken. I will double check later this week but I'm POSITIVE both external and internal storage appear in MTP.
A while back I read that Omni Rom had integrated a feature like the Nexus 5 had that let you type a name in the phone app, and you would get results back. Is this feature still in the Rom, and how do I enable it if so?
omni rom oppo find 7a
when call in and out,the screen blank and the touch screen not response untill the call been cancel..help please..
Hey all. Just got omni and am really liking it. However im getting significantly worse battery life than before - seems ok when in use just not great in standby. Android kernel is the main culprit according to gsam. Im on the 17/11 nightly if that helps. Any tips welcomed as other than this the rom is great.
krul apis said:
when call in and out,the screen blank and the touch screen not response untill the call been cancel..help please..
Click to expand...
Click to collapse
I have the same problem. As soon as I answer a call, the Screen goes black and stays black until I or the other person end the call.
Then you have to press the Power button two times to turn the screen on. I have checked for any option to enable screen during calls, but haven't found anything useful. The problem also exists with skype video calls.
Balimba said:
I have the same problem. As soon as I answer a call, the Screen goes black and stays black until I or the other person end the call.
Then you have to press the Power button two times to turn the screen on. I have checked for any option to enable screen during calls, but haven't found anything useful. The problem also exists with skype video calls.
Click to expand...
Click to collapse
Did you come from ColorOS 2.0?
There are some issues with proximity sensor when coming from newer versions of ColorOS we haven't had time to investigate. (We're busy with 5.0 bringup at the moment.)
Entropy512 said:
Did you come from ColorOS 2.0?
There are some issues with proximity sensor when coming from newer versions of ColorOS we haven't had time to investigate. (We're busy with 5.0 bringup at the moment.)
Click to expand...
Click to collapse
Thanks Entrophy512..after restore to color os 1.2.7,its back to normal again..
Feature question
First of all I apologize for the noob feature question. I've unfortunately never had the pleasure of using Omni in any of my devices so I don't know if it's there.
My Find7a's hardware keys are shot. They just stopped working one day out of the clear blue. They take like 50 presses to register a hit. I was stock Color OS at the time and did the build.prop hack to get the softkeys. I didn't want to mess around with shipping it back since I don't live in the US and it would be difficult.
I am currently on Gummy ROM, which does have a specific setting for enabling softkeys. Does Omni have this? If so, I can make the jump, since everything else sounds wonderful and the LVM solves my current space crunch for apps better than any partition hacks I've seen before and dit not want to touch.
If it does, would someone be kind enough to point me to the specific place where I can enable them? If/when I do the whole process to do LVM and flash Omni, I will want to enable them with as few presses of Home or Back as possible, since they will be painfully unresponsive (or even totally dead by now, so if there is an adb way to enable it or a way to do it without touching the hardware keys it would be fantastic).
Thank you and I apologize again for the question. I just read about 15 pages of this thread and also searched for "softkeys" and found nothing so I thought I would ask.
el_ochito said:
First of all I apologize for the noob feature question. I've unfortunately never had the pleasure of using Omni in any of my devices so I don't know if it's there.
My Find7a's hardware keys are shot. They just stopped working one day out of the clear blue. They take like 50 presses to register a hit. I was stock Color OS at the time and did the build.prop hack to get the softkeys. I didn't want to mess around with shipping it back since I don't live in the US and it would be difficult.
I am currently on Gummy ROM, which does have a specific setting for enabling softkeys. Does Omni have this? If so, I can make the jump, since everything else sounds wonderful and the LVM solves my current space crunch for apps better than any partition hacks I've seen before and dit not want to touch.
If it does, would someone be kind enough to point me to the specific place where I can enable them? If/when I do the whole process to do LVM and flash Omni, I will want to enable them with as few presses of Home or Back as possible, since they will be painfully unresponsive (or even totally dead by now, so if there is an adb way to enable it or a way to do it without touching the hardware keys it would be fantastic).
Thank you and I apologize again for the question. I just read about 15 pages of this thread and also searched for "softkeys" and found nothing so I thought I would ask.
Click to expand...
Click to collapse
Yes, but I can't remember exactly where. I'm currently not on it at the moment. I think there's a Button in the Settings menu
I cant connect my phone with computer. With color os 1.2.7i i could but now i cant. Only PTP works. MTP doesnt.. I tried many solutions, but nothing..
lazostat said:
I cant connect my phone with computer. With color os 1.2.7i i could but now i cant. Only PTP works. MTP doesnt.. I tried many solutions, but nothing..
Click to expand...
Click to collapse
Worked fine here last time I tried it. I'll try again tonight.
Now it worked. I uninstalled all hidden drivers from system devices and installed again.
I have some questions.
Where is the compass program?
Where is maxx audio?
Where is the "ultra" option in camera?
Where is the app drawer?
Why in antutu scores 41.000 and with color os 1.2.7i scores 45.000? Also i played some games and i have some lag. With color os i didnt.
Pls answer me.
Aosp roms don't have any ColorOS proprietary stuff. Also, benchmarks are unreliable. If you feel a game is lagging, try messing with the Performance settings. I personally find it just as smooth
farenteria said:
Aosp roms don't have any ColorOS proprietary stuff. Also, benchmarks are unreliable. If you feel a game is lagging, try messing with the Performance settings. I personally find it just as smooth
Click to expand...
Click to collapse
Benchmarks are unreliable and rarely mean that much, however in general you will always see AOSP-derivative projects on Qualcomm hardware benchmark a bit lower than official factory firmwares as there are a number of proprietary tweaks that Qualcomm doesn't allow to be put into open source projects.
That said, the reduced bloat in AOSP-derivative firmwares more than makes up for the slight reduction in benchmark epeen size.