Related
Hi all!
First i would like to thank to all people that have made this forum, maintain it and help users. I am also very grateful for cyanogenmod that i am using.
Second of all, i have search this forum for a solution, and i didnt find it, i have used google too. If i have missed it somehow i apologize myself.
Since yesterday i am user of cyanogenmod 7.2.0-buzz and i like it so far (i didnt use any rom before as i had varanty which i didnt want to lose).
Everything is good so far, but there are 2 buggs (problems) which i dont know how to solve them, i would appreciate any help, even redirecting to another mod.
My problems are following:
- as several other members, i dont have working wifi (is there any solution for this in this particular mod version?)
- 4 main buttons of my htc wildfire always vibrate when i touch them (home, menu, back, search), i turn vibrating off in setting, but nothing happens. This is kinda annoying if text alot and surf the web.
So if anyone could help me fix it, i would appreciate it. Thanks in advance!
I don't know about the WiFi problem but for the soft keys go onto to settings-->sound-->haptic feedback. This worked for me and I am running the stable version of cm7.
Mubz_C said:
I don't know about the WiFi problem but for the soft keys go onto to settings-->sound-->haptic feedback. This worked for me and I am running the stable version of cm7.
Click to expand...
Click to collapse
Thank you, this worked for me too. Now only WiFi problem left.
Thread moved to Q&A
Please post in the correct section next time
E.Cadro said:
Thread moved to Q&A
Please post in the correct section next time
Click to expand...
Click to collapse
Ok, im sorry. I will. It was my first post.
Somehow, i got wifi to work. Now everything is ok.
I've noticed a large amount of glitches and bugs in GC01. If you find any please list them here.
some of the bugs ive noticed:
*Volume slider and slider animation
*Random Reboots
*Missing Features
*Unstable in general
eisawi99 said:
I've noticed a large amount of glitches and bugs in GC01. If you find any please list them here.
some of the bugs ive noticed:
*Volume slider and slider animation
*Random Reboots
*Missing Features
*Unstable in general
Click to expand...
Click to collapse
Just a suggestion, but you may want to consider expanding on the issues so those that may feel like investigating have more to go on. For example..:
*Volume slider and slider animation - Can you provide a screenshot for reference of the issue?
*Missing Features - A list of what you find missing would be helpful. For example; Sprint removed Maps and YouTube since they can be downloaded from the Play Store...
*Unstable in general - How so? What are you seeing that makes you say it's unstable..? FC's, freezing, etc?
There again, only a suggestion but you may get more participation or helpful thoughts on remedies..
More Updates?
I was half expecting gb27 to be the end of the line for this phone.
MrLint said:
I was half expecting gb27 to be the end of the line for this phone.
Click to expand...
Click to collapse
GC01 is Boost's Official JB release.
Post removed. Wrong thread.
Now stop the bickering please.
Post edited.
People please... keep this thread on topic. There are a large amount of boost mobile users that are debating on whether to update or not. Thank you.
Wow... A newbie throwing out rules... Granted threads should stay on topic, but you should understand who is posting in your thread, OP. Garwynn is one of the biggest contributors for the E4GT as well as MoHoGalore. I don't think you have any room to make those kinds of demands when a RC has given you advice on this thread and you completely ignore it. So really, this thread has no real topic of discussion because it says absolutely nothing because of the lack of information provided, therefore people can post whatever they want because this thread is just cluttering up the forum.
Sent from my SPH-D710 using xda premium
graydiggy said:
Wow... A newbie throwing out rules... Granted threads should stay on topic, but you should understand who is posting in your thread, OP. Garwynn is one of the biggest contributors for the E4GT as well as MoHoGalore. I don't think you have any room to make those kinds of demands when a RC has given you advice on this thread and you completely ignore it. So really, this thread has no real topic of discussion because it says absolutely nothing because of the lack of information provided, therefore people can post whatever they want because this thread is just cluttering up the forum.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Whether they're senior members or not, they should follow rules. They could be the owners of XDA and I'd still tell them to stay on topic. There are threads for general conversations, this is not one of them. Rules are rules, and they are meant to be followed. Now please stay on topic people, people really need these kinds of things. And also, he gave me a suggestion. I did not follow his advice because I did not feel the need to do so. My thread, my topic, my list. Whoever wants to add to the list can. Bugs need to be reported to samsung so that hopefully we will have a better future release.
eisawi99 said:
Whether they're senior members or not, they should follow rules. They could be the owners of XDA and I'd still tell them to stay on topic. There are threads for general conversations, this is not one of them. Rules are rules, and they are meant to be followed. Now please stay on topic people, people really need these kinds of things. And also, he gave me a suggestion. I did not follow his advice because I did not feel the need to do so. My thread, my topic, my list. Whoever wants to add to the list can. Bugs need to be reported to samsung so that hopefully we will have a better future release.
Click to expand...
Click to collapse
Well if his advice is not important, then I am going to ask a mod to close this thread because it provides nothing. Also, that will be the last update from Samsung, so with that said, this thread is useless. I also am curious about who is reporting said "bugs" to Samsung? Do you think they will come here to find it? Nope. For the record, they nor I are just Senior Members. All of us that have posted and offered advice are Recognized Contributors. One would do well to take the advice of an RC to help better a thread, instead of blatantly ignoring them. We have been around for quite some time and in that time have learned how things work.
Sent from my SPH-D710 using xda premium
as soon as i gather more bugs i will report to samsung over and over until they release another update, and it was never stated that this would be the last update for the boost model. and if this thread does get closed ill start a fresh new thread where theres no un-needed conversation.
Accidental extra post
eisawi99 said:
as soon as i gather more bugs i will report to samsung over and over until they release another update, and it was never stated that this would be the last update for the boost model. and if this thread does get closed ill start a fresh new thread where theres no un-needed conversation.
Click to expand...
Click to collapse
The Boost model is the same as the E4GT. The 4.1.2 JB Update has been reported as the final from the Samsung sources. I highly doubt they will pay attention to one person reporting little bugs, especially when you don't describe them at all. They have more important things to worry about.
i have a question. does it make you feel better to put people down over the internet? does it make you feel as if your in control of everybody? im not going to be the only one reporting. others that want a bug free GC01 will also report. now please stop further cluttering my thread and go troll someone else.
eisawi99 said:
i have a question. does it make you feel better to put people down over the internet? does it make you feel as if your in control of everybody? im not going to be the only one reporting. others that want a bug free GC01 will also report. now please stop further cluttering my thread and go troll someone else.
Click to expand...
Click to collapse
How am I putting you down? I am agreeing with another RC about your thread not having any descriptions to your so called "bugs". I am not trying to control anything. I am offering the same advice. You can do whatever you like, but I can bet that this thread will either die as is, or it will get closed. You can either let one of the 2 happen by not doing anything to fix it, or do something productive and make it a worthwhile thread. Also, take note. I have not seen very many other people complain about it. Seems like you are the only one or one of a very few people.
Protip: Putting full, well thought out descriptions of your issues will help us help you possibly fix them. If you don't think descriptions are important, you will get nothing.
Example: When testing Shadow_God's Jellyverse 2.0 ROM before he posted it. I ran into a few crashes. I didn't just say "Oh, it crashed". I went into details. "Downloaded via Wi-Fi and installed through Agats GB27 RePack. ROM booted fine, but shortly after getting into the setup process the Android.phone process started force closing. My baseband seems to have been wiped and the launcher seems to be nonexistent."
I then took steps to fix it myself. I was able to fix it with little to no effort, and SG was able to post the ROM without any issues.
So with all that said, if you want to ignore very experienced veterans on XDA, that is your choice. You are free to do so. But don't expect me or anyone else to take you seriously when we make an honest effort to gain viable and needed information to potentially resolve the issues, then have you ignore the efforts.
Consider the following, if we don't take you seriously because of your lack of information and willingness to help us help you, do you honestly think Samsung will give even the slightest crap? They won't... Like I said before, they have better and more important things to do.
From the moderator
To all in the thread...........
Post respectfully......... FOLLOW THE RULES OF XDA OR I CLOSE THE THREAD......
......Thx, oka1
oka1 said:
To all in the thread...........
Post respectfully......... FOLLOW THE RULES OF XDA OR I CLOSE THE THREAD......
......Thx, oka1
Click to expand...
Click to collapse
I vote for option two.
The lack of description on these so called bugs is not informative to the readers, it makes me want to try flashing GC01 to my E4GT just so that I can try to experience whatever issues are being mentioned.
Sent from my SPH-D710 using xda premium
Removed my first post on this thread. I was wrong to post here and op was right to call out.
Op... how you updated to gc01 makes a difference. I still recommend a factory reset or full restore one click. This will resolve most issues as noted in past.
As for whether to update or not that's your call. Most around here believe it is FAR better than ICS and even though this is expected to be the final s/w release feel free to complain to Samsung and/or Boost if not happy. That's your right.
But please avoid using generalizations and then assuming the build is bad based on one individual's experience. That too does other folks a disservice. If you can please provide more specific details it helps the community note confirmed issues and possibly address them on our own.
Thanks.
Sent from my SPH-L900 using Tapatalk 2
I never stated that the build was bad, but like every build it has bugs. the reason i didnt further explain is beacause there really is no way for a screenshot... but i believe i found a fix to anyone experiencing these bugs. so heres what i did to fix my problem.
1. download superuser.zip from rwilco's repo
2. download the gb27 repack from rwilco's repo
3. download the stock gc01 stock kernel
4. place superuser.zip on your sd card
5. Odin the GB27 repack
6. enter recovery and flash superuser.zip
7. delete dalvik cache
8. odin stock gc01 kernel
9. reboot twice
Mattix724 said:
I vote for option two.
The lack of description on these so called bugs is not informative to the readers, it makes me want to try flashing GC01 to my E4GT just so that I can try to experience whatever issues are being mentioned.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
go ahead. the more help the better. it is not some bug that will make you loose all your data... it is minor bugs that annoy the (insert profanity here) out of me. keep in mind there are two installation methods to installing GC01 provided by samsung, local and kies. i chose local because kies wouldnt update for somereason and would randomly crash
the volume wake option in this rom works sporadically at best. I have noticed that is doesnt matter if the phone is in deep sleep mode or not. it has a mind of its own. anyone know of a permanent fix for this issue?
I suspect that it might have something to do with the "experimental" part in the rom name but I need some clarification on this if possible.
here are the specs:
tmb sammy s3 (d2tmo)
cm-10.1-20130121-EXPERIMENTAL-d2tmo-M1.zip
thanks everyone!!!
Questions and help issues go in Q&A
Development is only for developers to post work
Thread moved
FNM
nycdave said:
the volume wake option in this rom works sporadically at best. I have noticed that is doesnt matter if the phone is in deep sleep mode or not. it has a mind of its own. anyone know of a permanent fix for this issue?
I suspect that it might have something to do with the "experimental" part in the rom name but I need some clarification on this if possible.
here are the specs:
tmb sammy s3 (d2tmo)
cm-10.1-20130121-EXPERIMENTAL-d2tmo-M1.zip
thanks everyone!!!
Click to expand...
Click to collapse
Youre in the wrong section buddy. Questions/Issues go in the Q&A forums. Not sure if you intentionally placed this thread here but i reported it, they should be moving it for you shortly!
As for your issue, it may be a kernel thing, try a different kernel.
I dont like that feature so i dont use it. Therefore i cant say i had issues with it or not. As you've already stated, its experimental, there is a newer M2 version you could also try.
Bug report for a two month old nightly. Really?
You already know what I'm going to tell you; update it.
thank you so much for letting me know my brother. I appreciate you doing this for me.
kennyglass123 said:
Questions and help issues go in Q&A
Development is only for developers to post work
Thread moved
FNM
Click to expand...
Click to collapse
sorry everyone.... not trying to be a pest. just didnt know if this was a common issue in this build or not - thanks for the responses. I was going to run the update but I didnt want to do that wihtout some solid responses. I appreciate the help.
Aerowinder said:
Bug report for a two month old nightly. Really?
You already know what I'm going to tell you; update it.
Click to expand...
Click to collapse
I dont see a lot of posts about this. But, there is a very annoying bug after the update; where if I press the Home Button to wake the screen, it will sometimes launch the task manager about a second later. I've seen sporadic posts about this for Tmobile as well as Sprint for JB 4.1.2 update; but nobody seems to have a solution.
I guess it's possible that some people dont think it's annoying enough to post; or, it's a possiblility it only affects people who have the factory rooted update installed.
I'm hoping someone smarter than me has already figured out a way to circumvent this very annoying behavior. What makes it really bad is that it only sometimes happens.
PS: The only carrier that doesn't seem to have this issue after the 4.1.2 update is ATT. My guess is they caught this bug before pushing it to all their customers.
mkanet said:
I dont see a lot of posts about this. But, there is a very annoying bug after the update; where if I press the Home Button to wake the screen, it will sometimes launch the task manager about a second later. I've seen sporadic posts about this for Tmobile as well as Sprint for JB 4.1.2 update; but nobody seems to have a solution.
I guess it's possible that some people dont think it's annoying enough to post; or, it's a possiblility it only affects people who have the factory rooted update installed.
I'm hoping someone smarter than me has already figured out a way to circumvent this very annoying behavior. What makes it really bad is that it only sometimes happens.
PS: The only carrier that doesn't seem to have this issue after the 4.1.2 update is ATT. My guess is they caught this bug before pushing it to all their customers.
Click to expand...
Click to collapse
I'm going to bet that is you disable your lockscreen you'll see this behavior just about every time. I'm fairly certain I tracked down at least one way to circumvent this behavior - check out this post for some info on it. The take home - my approach requires a wee bit of smali hacking, and everything that utilizing such a solution entails...
Dwitherell, thank you so much for responding. I was even considering on reverting back to 4.1.1 because of this. I don't use any kind password or pattern lock.
Forgive my ignorance, but the post you pointed me to locks like its on a Jedi ROM. I don't even see any specific references to this issue. What is this fix for specifically? If it is for sure going to restore normal behavior, i guess i could try to do this hack.
If this issue is as wide spread as i think it is, is there any chance you could make a tiny root app that fixes the problem or some way of automating a fix for not so technical people? How wide spread is this issue? Thanks a million for your help.
dwitherell said:
I'm going to bet that is you disable your lockscreen you'll see this behavior just about every time. I'm fairly certain I tracked down at least one way to circumvent this behavior - check out this post for some info on it. The take home - my approach requires a wee bit of smali hacking, and everything that utilizing such a solution entails...
Click to expand...
Click to collapse
My annoying fix...
I have been plagued by this since the update as well. I have tried factory resets and uninstall programs one by one. Nothing worked. Today I decided to try removing my lock screen pin, just used the swipe to unlock. That did not work. Then it came to me...
I set back up my pin to unlock, and switched the setting "Lock automatically" to Immediately instead of having a delay that I love. That "worked" as in it no longer goes to recent apps. But now I have to chose to have a pin to unlock it every time my screen turns off or remove security or deal with the recent apps issue. Any way you choose it's an extra annoying step to unlock.
I'd like to hear if anyone else has found any other solution.
Edit.... I have tried every lock option and as long as set to lock immediately, it will eliminate the problem. And the same with setting any delay, with any lock option it will result in the recent apps.
I forgot to mention that lock screen prevents this bug from happenening. I'm guessing that's why not everyone has complained about the issue.. and why the bug somehow sneaked passed beta testing of 4.1.2. I would think this changed behavior was a new "feature" as horrible as it is, but it looks like it dad unintentional since its not consistent behavior.
I'm hoping that a kind android developer who also can't stand this problem, Kay offer a small script or app for rooted user to patch this problem.
mrtolles said:
I have been plagued by this since the update as well. I have tried factory resets and uninstall programs one by one. Nothing worked. Today I decided to try removing my lock screen pin, just used the swipe to unlock. That did not work. Then it came to me...
I set back up my pin to unlock, and switched the setting "Lock automatically" to Immediately instead of having a delay that I love. That "worked" as in it no longer goes to recent apps. But now I have to chose to have a pin to unlock it every time my screen turns off or remove security or deal with the recent apps issue. Any way you choose it's an extra annoying step to unlock.
I'd like to hear if anyone else has found any other solution.
Edit.... I have tried every lock option and as long as set to lock immediately, it will eliminate the problem. And the same with setting any delay, with any lock option it will result in the recent apps.
Click to expand...
Click to collapse
mkanet said:
Dwitherell, thank you so much for responding. I was even considering on reverting back to 4.1.1 because of this. I don't use any kind password or pattern lock.
Forgive my ignorance, but the post you pointed me to locks like its on a Jedi ROM. I don't even see any specific references to this issue. What is this fix for specifically? If it is for sure going to restore normal behavior, i guess i could try to do this hack.
If this issue is as wide spread as i think it is, is there any chance you could make a tiny root app that fixes the problem or some way of automating a fix for not so technical people? How wide spread is this issue? Thanks a million for your help.
Click to expand...
Click to collapse
It was posted in a Jedi thread, but only because that is where I noticed it was mentioned. The context outside that single post was someone stating the same observation as you, my responding saying that I was also annoyed by it, with a later edit saying I may have come up with a workaround for it, and their response of "tell me more". As far as automating a fix or creating an app or the like - that is well beyond my paygrade unfortunately. What are you running? If you are interested you could PM me - all I need is your android.policy.jar (or to know what you are currently running) and I can try to get a fix together for you given some other conditions (i.e. have a custom recovery installed so you can flash things). It seems to have fixed it on my end, but I would be very interested in getting some others to test
You did it! Your fix works perfectly! The bug is gone! ...like the bug was never there. My understanding is the fix prevents the phone from stupidly trying to launch the task manager when the screen wakes by the home button. I also donated for you time and effort. Thanks a million.
dwitherell said:
It was posted in a Jedi thread, but only because that is where I noticed it was mentioned. The context outside that single post was someone stating the same observation as you, my responding saying that I was also annoyed by it, with a later edit saying I may have come up with a workaround for it, and their response of "tell me more". As far as automating a fix or creating an app or the like - that is well beyond my paygrade unfortunately. What are you running? If you are interested you could PM me - all I need is your android.policy.jar (or to know what you are currently running) and I can try to get a fix together for you given some other conditions (i.e. have a custom recovery installed so you can flash things). It seems to have fixed it on my end, but I would be very interested in getting some others to test
Click to expand...
Click to collapse
No, thank you for making me learn how to put an odexed mod together and testing it for me!
So this fix will work for anyone running a stock odexed version of 4.1.2 UVBMB4 - you just need to be rooted, and having a custom recovery would be nice so you could flash it but you could also just copy the files over. That being said - would this be worthwhile to post?
I wish i had know i could just copy the files over.. that's actually less convoluted process than depending on a script. I thought the reason you made a patch via flashing is because the system files were locked/open by the system. Anyway, i am extremely thankful for this'll as there is no other way to fix the bug without adding extra steps to wake the screen.
You should definitely share both odexed and deodexed patches with others. I personally don't know how i could tollerate that bug for much longer. I'm sure there are others who don't use the lock screen. Plus, this would give a chance for others to appreciate your work by dontating for your time and effort.
mkanet said:
I wish i had know i could just copy the files over.. that's actually less convoluted process than depending on a script. I thought the reason you made a patch via flashing is because the system files were locked/open by the system. Anyway, i am extremely thankful for this'll as there is no other way to fix the bug without adding extra steps to wake the screen.
You should definitely share both odexed and deodexed patches with others. I personally don't know how i could tollerate that bug for much longer. I'm sure there are others who don't use the lock screen. Plus, this would give a chance for others to appreciate your work by dontating for your time and effort.
Click to expand...
Click to collapse
The flashable zip is just one method to get the files where they need to go. Literally all it does is overwrite the 2 files in /system/framework by moving the 2 files over from the zip - but there are definitely other ways to do such things. Some are more comfortable with this route, others are more comfortable w/ getting /system to be rw and move the files manually.
I'll likely post this at some point in the next few days
I don't mean to revive a dead thread or anything, but this bug has been driving me CRAZY & the smali hacking worked perfectly for me, thank you!!!
FYI, I'm willing to help people out with this as well. If anyone wants this done but doesn't wanna mess with the java stuff, PM me & send me your android.policy.jar and I'll hack it for you
kabuk1 said:
I don't mean to revive a dead thread or anything, but this bug has been driving me CRAZY & the smali hacking worked perfectly for me, thank you!!!
FYI, I'm willing to help people out with this as well. If anyone wants this done but doesn't wanna mess with the java stuff, PM me & send me your android.policy.jar and I'll hack it for you
Click to expand...
Click to collapse
Glad to hear
Is it possible that my phone isn't affected? If its a 4.1.2 bug, it should be in all phones with same version right?
This is not happening to my phone. Whether I have lock screen activated or not. I'm rooted but running stock ROM and I have Nova launcher installed if thats even important.
It's not all notes.
Sent from my SGH-T889 using xda premium
kabuk1 said:
I don't mean to revive a dead thread or anything, but this bug has been driving me CRAZY & the smali hacking worked perfectly for me, thank you!!!
FYI, I'm willing to help people out with this as well. If anyone wants this done but doesn't wanna mess with the java stuff, PM me & send me your android.policy.jar and I'll hack it for you
Click to expand...
Click to collapse
is this offer still good? i'm was experiencing the same problem and it was so annoying that the only solution i found was to revert back to 4.1.1. I'm currently running t889uvall4.
also, my phone is not rooted. will the fix dwitherell came up w/ work? or do i really have to root my phone?
wesblogger said:
is this offer still good? i'm was experiencing the same problem and it was so annoying that the only solution i found was to revert back to 4.1.1. I'm currently running t889uvall4.
also, my phone is not rooted. will the fix dwitherell came up w/ work? or do i really have to root my phone?
Click to expand...
Click to collapse
Yes you'll need to be rooted unfortunately - sorry
wesblogger said:
is this offer still good? i'm was experiencing the same problem and it was so annoying that the only solution i found was to revert back to 4.1.1. I'm currently running t889uvall4.
also, my phone is not rooted. will the fix dwitherell came up w/ work? or do i really have to root my phone?
Click to expand...
Click to collapse
Absolutely. just PM me. Yeah, you have to be rooted but that's easy to do & worth it for this hack & all the other things you can do once you're rooted.
kabuk1 said:
...Yeah, you have to be rooted but that's easy to do & worth it for this hack & all the other things you can do once you're rooted.
Click to expand...
Click to collapse
^^^ THIS - a thousand times over
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?