Develop Bugs

Vote to fix haret method.

http://code.google.com/p/vogue-andr... Priority Component Owner Summary#makechanges

things change fast around here. try reading new threads before post useless request to fix an old problem from march

If your going to daddy me at least leave me a toy.
Wow learn to read. The android n00b thread people are still having these issues. Maybe something has changed but I have seen it. I see two categories of haret users those who work (miracles people who usually are using nand and may have some enviromental difference over us regular sdcard-hare ppl)..
If you can fix my issue fix it, but don't tell me its fixed when nothing says that. Albeit a night of going through all the updates on the different builds may produce results no one has done that in that particular thread (2, or 3, which upon someone coming up and saying this easy has ended up giving up) both threads are a bit different. One was supposed to be look how easy it is , with a few nand resistant fools getting every thing but sound. You sir are a troll... !#@@! @!# @#[email protected][email protected]@!
Seriously if you want new people using android put out a haret build that works... Don't make us n00bs flash our customized **** so we can say oh thats broke, i need that...

sorry if my tone was incorrect. let me try again
The link you posted refers to something that is not a problem any more or was due to old hardware, ie the button physically wasnt working.
k_k successfully used haret to test his build when he was working on the gps. that was the beginning of june
are you trying to say that the link is to YOUR problem? i cannot tell from the post of only a link. it looks like reading through this thread that you got past that problem.
if you need help please list your problem with as much detail as possible so i or someone else can help you.
if you are trying to make a case for haret dev, you should post links or quote more recent attempts and problems

Thanks for the news
Cool. I'll search up on that and post to the threads that I've been going to. It's just email never comes across very personable. People who say to read the entire forum get on my nerves or to search when I have is annoying because sometimes they have read it in an area I haven't landed and it like a race run condition due to bad communication. If you see something try to link it, glad I have a user name to search off, but if you can pt a better thread I'll be happy. Either way when I find it, I'll try to boot again maybe in a week or so. I'll be very happy if it does indeed work now, we'll see.. As far as my posting relating to haret, yet you can regain control of your buttons but if you actually read all of the thread you'll see it doesn't get better than that, it then is a sound issue. Either way haret is broken, and my point is that poor user from march is still suffering now, and this time its sound. I suspected that haret became broken due to the development direction towards nand. I.e. whatif system.file is reffed somehow as (NAND0,0):/initrd.gz. I mean droid when from system.img's to partitions so something very generic could lead to both issues esspecially if a user A who can't hear in haret, can hear in a nand install using the same release? See the modules and stuff are going to be the same. I hope your not wasting my time with the k_k bit...

tyler51773 said:
I hope your not wasting my time with the k_k bit...
Click to expand...
Click to collapse
no. he is one exmple of people who have it working. there are others, i just know him off the top of my head.
People who say to read the entire forum get on my nerves or to search when I have is annoying because sometimes they have read it in an area I haven't landed and it like a race run condition due to bad communication.
Click to expand...
Click to collapse
your first post was just as indirect. from that post i had no way of know you have been working on it. the specific link you post was probably not the best choice. with out direction from you i have no reason to go 2 links deep. not until you gave more description did i go into the xda thread where have been trying things.
it then is a sound issue.
Click to expand...
Click to collapse
yes there is still the sound issue. you could have gotten much better response if you had put something in the first post to indicate you specifically want the sound worked on.

sound it is.
its just more like a watch me thread for people who care about haret. i posted a bug on vogue-android.. but the drift it haret is broken. been broken. its bad right now. can we fix it? or is it fixed already. you mentioned K_K do you mean this thread http://forum.xda-developers.com/showthread.php?p=6852911 or do you mean kalt_kafee kernel are they same guy? where you saying dpad was fixed versus just sound. I guess I'm going to try his latest update kernel, unless you've seen a better thread. I've already got to goto bed. Maybe that's why the guy never came back on my own thread cause i sent him to a new kalt kernel hehehe..

sound working
Going through the list now. Thanks for the pointer. I'll will soon venture forward.
I got sound on an old androidinstall of unknown origin. it was freezing and unstable. I did not get sound ironically on VaniljEclair , the second install from the old android I also installed to system.img vs sdcard partition. trying warm
Aqtrans' CM-5.07 - nice and stable
warm eclair rls 1 - fast, worked great for a day then force closes all over
Incubus26Jc's SuperE beta 3 - still slow on kaiser
VaniljEclair 5.0.8 out! (not tested by me)
trying myn's warm donut then will try aqtrans'
you may have beaten the pepsi challenge.

[Cyanogenmod 6] - Force Close on Quick Profiles

http://forum.xda-developers.com/showpost.php?p=7401058&postcount=5946
I posted the above in the nightly build thread, but it's moving so fast I'm afraid no one will ever see/respond to such a specialized issue.
I need some help, guys. I've already spoken directly to the developer and they were not able to address the issue. I've been using a program called "Quick Profiles" every since I got my Evo. It's EXACTLY what I need. It worked fine on stock and damage control. But since I've switched to Cyan6, it's not worked. It force closes. The developer seems to think it's a problem with the ROM.
I've attached a logcat, so if anyone can take a look at it and give me some pointers I would appreciate it.
Click to expand...
Click to collapse
I know someone else in that thread (bkfitz) indicated he was having the same issue. I'm attaching a logcat to try to help identify the problem. Please chime in if you have any ideas on how to go forward. Like I alluded to above, I've been in contact with the Dev. We troubleshooted the problem for awhile and he, ultimately, decided it must be an issue with the ROM. He's monitoring the forums, I believe, and mentioned that he would be more than willing to collaborate on a solution if that's possible.

Bump.
10 chars

Same force close problem for me with QP and Cyan 6.0 stable mod. But QP works fine with Simply Stunning 4.7.

[FIXED] Compass not working in GingerBread rom's

Hello,
I have been trying out some GB roms lately and during the testing i saw that the compass was not showing north anymore.
If i turn the phone a little, the compass is swaying somewhere between NE and NW, but it never points north.
So i went back to FroYo roms, but now i have it there also.
I have been reading several messages fro different GB roms that people are having the same problem.
I also used the recommended radio's for the GB roms.
Since my AuraxTSense (FroYo) rom now also has this problem, it looks like a radio problem.
Can someone confirm this problem and tell me the solution or tell me the radio that is working?
Eric
Edit: See my post on page 2. There is a snq kernel fix for this problem.

Well, i have been testing some further.
Radios (old or new) make no difference.
Froyo rom (Aurax 8.4) and recalibrating the compass the old way, did make it work again.
Installing a new rom (GingerBread that is) and everything was wrong again. The radio version did not make any difference.
So i'm going back to Aurax and hope that i can recalibrate it again to let it work.
For other's with this problem:
Try the old way of calibrating the compass.
Make at least 2 figures 8, but do it slowly. It should take at least 2 seconds for every 8 you make.
Then turn the phone around 360 degrees along the length axe of the phone, also at least 2 times and 2 seconds per turn
Then turn 360 degrees along the sides axe (width), also at least 2 times and 2 seconds per turn.
If this did not work, repeat the last 2 ways of turning (length and width axe) but do it faster and about 6 to 8 times per direction.
This worked for me (and i hope it will work again in a few minutes).
Eric

Looks like North is up and South is down. The compass is now a "bubble" app.

MrXimi said:
Looks like North is up and South is down. The compass is now a "bubble" app.
Click to expand...
Click to collapse
I read a few days back that some Chinese Rom's had fixed it (HiAPK or something like that), but i just read that they also still have this problem.
So i will have to wait untill this is really fixed, because i need the compass for finding directions etc.

it seems to be a general gingerbread problem, other devices are affected too:
http://www.youtube.com/watch?v=l-9lehX8u2U
http://www.google.pn/support/forum/p/Google Mobile/thread?tid=07d4eaf9686b664e&hl=en

It is a general Ginger problem..we can nothing do about it but...waiting for fix

I opened a bug report on android's bug tracker, I encourage everyone who has this issue to confirm it so it will be fixed.
http://code.google.com/p/android/issues/detail?id=16741

I added my comments also.
Sent from my HTC Desire using XDA App

supposedly this fixes the problem on GbB as well but I havent tried it yet and don't feel much like flashing a GB rom and having to go back again to froyo if ot doesnt work:
http://forum.xda-developers.com/attachment.php?attachmentid=425776&d=1287930092

godutch said:
supposedly this fixes the problem on GbB as well but I havent tried it yet and don't feel much like flashing a GB rom and having to go back again to froyo if ot doesnt work:
http://forum.xda-developers.com/attachment.php?attachmentid=425776&d=1287930092
Click to expand...
Click to collapse
In the RCmix S thread there was somebody who had tried it.
In GB most of the files are not found.
The fix is for Froyo and not GB.
The guy (i think) reported that it did not work at all.
We will have to wait for some other solution.

godutch said:
I opened a bug report on android's bug tracker, I encourage everyone who has this issue to confirm it so it will be fixed.
http://code.google.com/p/android/issues/detail?id=16741
Click to expand...
Click to collapse
Confirmed

godutch said:
i opened a bug report on android's bug tracker, i encourage everyone who has this issue to confirm it so it will be fixed.
confirmed... Thnx
Click to expand...
Click to collapse

Compass fixed with new kernel
Since yesterday there is a fix for the Compass problem in the GB rom's
It is a new kernel from snq and works for (at least) most GB rom's and probably all GB rom's.
I have not had time to try it, but in most rom threads there are people who have tried it and it works!!!!!
The fix can be found here:
http://forum.xda-developers.com/showthread.php?t=1039004
If you want the flashable version, you can find it on the line with this text (on the previous page link):
download: zImage-v05 (flashable v04-to-v05 kernel image update package here)
Click to expand...
Click to collapse
or click on the link below:
http://api.viglink.com/api/click?format=go&drKey=1359&loc=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php%3Ft%3D1039004&v=1&libid=1306265553578&out=http%3A%2F%2Fdl.dropbox.com%2Fu%2F13432479%2Fmsm-2.6.35-bravo-GB%2Fg308ba26%2Fv04_to_v05-img-upd-flash.zip&ref=http%3A%2F%2Fforum.xda-developers.com%2Fforumdisplay.php%3Ff%3D628%26order%3Ddesc%26page%3D2&title=%5BKERNEL%5D%5BGB%2FSENSE%5D%202.6.35.10%20%5Bv05%5D%20%7C%20OC1152%20%7C%20LZMA%20%7C%20COMPASS%20%7C%20fixes%20%2Baddtl%20modules%20-%20xda-developers&txt=here
Have fun with it. I will when i have time to flash it

Confirmed working btw, got it in my ROM and it's fine

Yeah, works for me too. Using latest leedroid.

sorry. wrong post.
~renzs

Working on Nexus S
Hello,
is this fix working on Nexus S, too?

So, is this fix going to be incorporated into the official Acer releases (prob not)?
I guess we have to root and flash after market roms to fix their fubars...

lost sound on jelly bean rom

First a quick shout out to Albinoman who made the JB rom in question here (I'll put a link to it at the bottom of this post). He did an amazing job and I am thoroughly enjoying jelly bean goodness on my very old and abused incredible.
I should mention (if it helps someone figure out what happened) that the device has been torn apart by myself multiple times to solve two issues: (and for fun)
The first being the display was shattered and had to be replaced,
And the second being that the device had been laid down in something wet for over a week while not in my possession, covering the internal parts with said wet..ness.. (no idea what it was). A few days disassembled in rice fixed the wetness issue and it worked perfectly!
Now I fixed some other software issues it was having (lost root after a failed rom flash) and loaded cm6.1 onto the device, and then cm7.2, and then this JB rom.. in one afternoon....... (gets addicting after only one flash!!). It was doing fine all day with only issues with the camera and Google chrome until I went to mess with the sound settings and went to: settings/ sound/ volumes. When I tapped volumes it said, "Unfortunately, Settings has stopped." All sound no longer works.. A battery pull, multiple restarts with setting changes, and finally a factory reset later and nothing has changed. Thanks for reading this much too long post. any ideas what I should do next?
As promised, here is a link to Albinoman's rom which I highly recommend checking out.
[ http://forum.xda-developers.com/showthread.php?t=1778190 ]

fixed sound issue
I'm still kicking myself over this.. I put the speaker in backwards.. yep.. now would be a good time to learn how to delete a thread..

btw, many devs, Albinoman included, would appreciate it if you ask questions that are related to their roms, on the rom's original post. just a heads up man.

ra9b said:
btw, many devs, Albinoman included, would appreciate it if you ask questions that are related to their roms, on the rom's original post. just a heads up man.
Click to expand...
Click to collapse
They would, but there's that 10 post rule here on xda...
@markd: Glad you got it figured out! Props to you for not being afraid to tinker.

ra9b said:
btw, many devs, Albinoman included, would appreciate it if you ask questions that are related to their roms, on the rom's original post. just a heads up man.
Click to expand...
Click to collapse
Actually q&a is for questions of anything related to the device and the rom threads as I understand is supposed to be only for posts contributing to development of that project but you're right most devs including me like when issues/questions are in the ROM thread.
Hey I got an idea. Remove the 10 post rule to post in dev but not allow creating topics in dev until 40 or 50 posts.
Sent from my Galaxy Nexus using Tapatalk 2

[Q&A] [ROM][4.4.4][SM-T700] Bliss Stalk by Team Bliss

Q&A for [ROM][4.4.4][SM-T700] Bliss Stalk by Team Bliss
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 [ROM][4.4.4][SM-T700] Bliss Stalk by Team Bliss. 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!

jewnersey said:
not sure why that's happening..but a new build should be up in the next day, hopefully, with some of the kinks ironed out. Probably best to just wait until then.
Click to expand...
Click to collapse
@ jewnersey: It could be the greatest rom :angel:, if you can embedded camera features in the next update. Not forcing you to do that immediately, just requesting you since you are engaged with your job. Thanks.

cant believe how great this rom is..i agree..so so many options...one of the best custom roms ever had..it flashed perfect for me..ive read how some people are haveing problems with wifi not working,i flashed the rom,then kernal,then gapps,and wifi worked out of the box..if it diddnt i was gonna flash a diff recovery like philz and try again..normally that works for me...only issue ive had is when pressing language and input it crashes.i was gonna install a themed google keyboard and activate it as main keyboard but cant get into the settings to even see what keyboard is installed..but still love the rom and understand its a work in progress...thanks bliss team for this rom and port,much better then what i had before this!!!
update..now see witch keyboard is installed threw settings/apps....it is android keyboard..could request that android keyboard come with diff themed options i really like the shafta google keyboards,but cant install if google keyboard allready exsists,and i dont wanna mess with freezeing/uninstalling system apps

any lovin for the t705??
we uad some advancements but got stuck at the lte implementation.
could be due to the 4g/3g intel chip samdung used for its exynos chip.....
i feel so cheated out of my snapdragon 801.....

Am uploading a newer build that should be much cleaner and ironed out.
As far as other devices... I am not a developer, so bug fixing etc is currently beyond me... However, if there is a CM port for the device, I can probably port Bliss for that device, but all the shortcomings of the CM rom will exist in Bliss as well.. Either way, I will see what I can do after I make sure T700 is running smoothly.

New build is up.

Hey
It would be nicer if you have some specific screenshots. BTW, hope you guys can ported this rom to T805 lots of Asian users are waiting for you

stkpxl said:
Tried the new build. Tried to create a second user (which is a must for me). When trying to use the new user, the launcher crashes and basically wont let me do anything. With the new CM11 build, I don't have that issue. Which is weird, since I understand thats what your build is using.
Click to expand...
Click to collapse
will look into this.
vo.tran.thanh.luong said:
It would be nicer if you have some specific screenshots. BTW, hope you guys can ported this rom to T805 lots of Asian users are waiting for you
Click to expand...
Click to collapse
screenshots added.....
I am basically relying on the real developers, so once CM or an equivalent arrives for 805, ill fire up a Bliss derivation.

Thank you for your hard work providing this rom! just couldn't stand the stutter of touchwiz.
one thing I desperately miss is the color calibration though.
I can't find the option in settings. could somebody please point it out to me?
another thing I noticed is that the tablet runs smoother when plugged in. when I pull the plug I have a tiny bit of stutter. Do you have any suggestions how to fix this?

Screen Locks automatically and frequently
Hi Jewnersy,
I appreciate your efforts in creating the Bliss Rom for Samsung Tab S (T700). I have been using the rom from the last two releases. I love the settings and customizations provided in the Rom . I observed one small issue in the latest build. I am using a Flipcover cover for my Tab. When I close the cover, screen goes off which is fine. But When I open the cover am able to the see the lock screen, but not able to unlock the screen by swiping the lock icon to right side. After swiping it to right side, screen suddenly locks again. After giving trails for 10 - 15 times, am able to unlock the device. While watching movies also screen locking unexpectedly. Please help me in getting a solution for the issue. Thanks again for your response & support in advance.

schmandchen said:
Thank you for your hard work providing this rom! just couldn't stand the stutter of touchwiz.
one thing I desperately miss is the color calibration though.
I can't find the option in settings. could somebody please point it out to me?
another thing I noticed is that the tablet runs smoother when plugged in. when I pull the plug I have a tiny bit of stutter. Do you have any suggestions how to fix this?
Click to expand...
Click to collapse
Don't think there are any color options built in to the rom unfortunately. Regarding stuttering.. I'm not sure I'm having that issue. The latest rom had been smooth as butter for me... Interactive governor, cfq, Westwood.
Dynamic status bar will cause constant stutter. Use the xposed mod discussed in thread as an alternative
raghavamsc said:
Hi Jewnersy,
I appreciate your efforts in creating the Bliss Rom for Samsung Tab S (T700). I have been using the rom from the last two releases. I love the settings and customizations provided in the Rom . I observed one small issue in the latest build. I am using a Flipcover cover for my Tab. When I close the cover, screen goes off which is fine. But When I open the cover am able to the see the lock screen, but not able to unlock the screen by swiping the lock icon to right side. After swiping it to right side, screen suddenly locks again. After giving trails for 10 - 15 times, am able to unlock the device. While watching movies also screen locking unexpectedly. Please help me in getting a solution for the issue. Thanks again for your response & support in advance.
Click to expand...
Click to collapse
I noticed a flip cover quirk as well. Will investigate tomorrow and grab some other fixes from other folks.

WiFi is not turning on with the latest (12/15) build of the Bliss Stalk ROM for the SM-T800.
For some truly asinine reason XDA is forcing this reply into a separate Q&A thread (where it will undoubtedly go unnoticed by the developer of this ROM) just because I have fewer than 10 posts.
This post is INTENDED to be a reply to this post:
http://forum.xda-developers.com/showpost.php?p=57506489&postcount=89
Again, I apologize for this reply not appearing in the correct location - blame XDA or whomever thought it would be a good idea to force all replies by new users into a totally separate thread.
---------- Post added at 03:32 AM ---------- Previous post was at 03:27 AM ----------
Zimus said:
WiFi is not turning on with the latest (12/15) build of the Bliss Stalk ROM for the SM-T800.
For some truly asinine reason XDA is forcing this reply into a separate Q&A thread (where it will undoubtedly go unnoticed by the developer of this ROM) just because I have fewer than 10 posts.
This post is INTENDED to be a reply to this post:
http://forum.xda-developers.com/showpost.php?p=57506489&postcount=89
Again, I apologize for this reply not appearing in the correct location - blame XDA or whomever thought it would be a good idea to force all replies by new users into a totally separate thread.
Click to expand...
Click to collapse
Feel free to ignore this particular post, I'm going to post a bunch of B.S. until I can get my total post count over the 10 post threshold so that I can actually post bug reports in the proper thread.

Zimus said:
WiFi is not turning on with the latest (12/15) build of the Bliss Stalk ROM for the SM-T800.
For some truly asinine reason XDA is forcing this reply into a separate Q&A thread (where it will undoubtedly go unnoticed by the developer of this ROM) just because I have fewer than 10 posts.
This post is INTENDED to be a reply to this post:
http://forum.xda-developers.com/showpost.php?p=57506489&postcount=89
Again, I apologize for this reply not appearing in the correct location - blame XDA or whomever thought it would be a good idea to force all replies by new users into a totally separate thread.
---------- Post added at 03:32 AM ---------- Previous post was at 03:27 AM ----------
Feel free to ignore this particular post, I'm going to post a bunch of B.S. until I can get my total post count over the 10 post threshold so that I can actually post bug reports in the proper thread.
Click to expand...
Click to collapse
Wow I tested too! I posted in the rom thread. If your reporting bugs then it's OK to post in the rom thread. q and a stuff goes here about the thread. It's just to remind you to ask questions here. I'm surprised Ui lag is gone! Once you make more than 100 posts then there's no limit on posts.

DUHAsianSKILLZ said:
Wow I tested too! I posted in the rom thread. If your reporting bugs then it's OK to post in the rom thread. q and a stuff goes here about the thread. It's just to remind you to ask questions here. I'm surprised Ui lag is gone! Once you make more than 100 posts then there's no limit on posts.
Click to expand...
Click to collapse
I TRIED to post in the ROM thread by clicking the "reply" button on post #89, but received an error message stating the developer has decided that all posts from users with less than 10 posts should be moved to a separate Q&A thread. Such a decision makes it impossible to actually submit bugs...

Zimus said:
I TRIED to post in the ROM thread by clicking the "reply" button on post #89, but received an error message stating the developer has decided that all posts from users with less than 10 posts should be moved to a separate Q&A thread. Such a decision makes it impossible to actually submit bugs...
Click to expand...
Click to collapse
Lol. After a few posts you can post there. Did you try the camera and see if it works? I forgot to check that.

Zimus said:
I TRIED to post in the ROM thread by clicking the "reply" button on post #89, but received an error message stating the developer has decided that all posts from users with less than 10 posts should be moved to a separate Q&A thread. Such a decision makes it impossible to actually submit bugs...
Click to expand...
Click to collapse
not my decision, but rather the forums.
ANYWAYS, did you try without the kernel or with the kernel?

DUHAsianSKILLZ said:
Lol. After a few posts you can post there. Did you try the camera and see if it works? I forgot to check that.
Click to expand...
Click to collapse
I switched back to the 11/27 build due to wifi not working on the 12/15 build. The camera doesn't work on 11/27, but the developer is already aware of that issue. Give me a few min and I'll re-flash the 12/15 build and check the camera.

Zimus said:
I switched back to the 11/27 build due to wifi not working on the 12/15 build. The camera doesn't work on 11/27, but the developer is already aware of that issue. Give me a few min and I'll re-flash the 12/15 build and check the camera.
Click to expand...
Click to collapse
let me know if you are using the 'skyhigh' kernel or not...
basically need to know if wifi is broken with and without kernel
as well as camera under both conditions,

jewnersey said:
not my decision, but rather the forums.
ANYWAYS, did you try without the kernel or with the kernel?
Click to expand...
Click to collapse
I tried just the ROM w/o flashing the SkyHigh kernel - wifi still wouldn't turn on. My apologies on my rant concerning the 10 post minimum, the "error" message made it sound like it was your decision -- sorry!

Zimus said:
I tried just the ROM w/o flashing the SkyHigh kernel - wifi still wouldn't turn on. My apologies on my rant concerning the 10 post minimum, the "error" message made it sound like it was your decision -- sorry!
Click to expand...
Click to collapse
not a problem.
Let me have a look at the source and see if i can figure whats going wrong. probably something super easy. hopefully can post a new build in a few hours. did you try camera?