As the title states every time I get a message through Viber my screen turns on just as if I pressed the power button.
I've tried changing settings and obviously disabled the popup and "unlock for popups" but it still wont stay locked.
Is there something I've missed :s? Is it like that on other peoples Viber? It's damn annoying for me atleast..
Im using a Samsung Galaxy Nexus, maguro. Its been like this on stock 4.0, stock 4.1, a bunch of 4.1 roms and AOKP 4.1.2. Aka its always been like this..
Thank you for your time and please direct me if this is the wrong forums.
ps; ask if you need screen shots or whatnot and I will upload them.
Edit: If I disable notifications for the app through jellybeans new option to disable notifications from the app info screen the screen STILL lights up and unlocks when I get a message..though no notification or anything.
soo no one know anything about it?
Bresch said:
soo no one know anything about it?
Click to expand...
Click to collapse
Do u try change on Viber's setting ?
ok so you will have to gon in viber setting and uncheck new message popup. when you do this , next option unlock for popups , will be automatically disabled
This is something I've explained to viber in detail already and all they told me was to fix the settings so the unlock for pop up is unchecked. I emailed them back stating that it is unchecked and that this issue occurred ever since they did their last update and that I specifically mentioned my settings are set that way in the original email. All I got was an apology and that they would look into it. It's been months since and still no update from them
Sent from my Galaxy Nexus using Tapatalk 2
ljnkshady said:
Do u try change on Viber's setting ?
Click to expand...
Click to collapse
Yes as I explain in the original post I've tried everything.
khuzema9 said:
ok so you will have to gon in viber setting and uncheck new message popup. when you do this , next option unlock for popups , will be automatically disabled
Click to expand...
Click to collapse
Yes I've done that but it still unlocks the screen..
thephantom said:
This is something I've explained to viber in detail already and all they told me was to fix the settings so the unlock for pop up is unchecked. I emailed them back stating that it is unchecked and that this issue occurred ever since they did their last update and that I specifically mentioned my settings are set that way in the original email. All I got was an apology and that they would look into it. It's been months since and still no update from them
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I've written to them on twitter but they told me to write them an email but still haven't heard from them..
Also to note: If I disable notifications from the app through the new jellybean app info screen, the screen still unlocks and lits up but no sound or notification..my last desperate attempt would be to disable the permission to unlock screen somehow, is that possible?
Bresch said:
Yes as I explain in the original post I've tried everything.
Yes I've done that but it still unlocks the screen..
I've written to them on twitter but they told me to write them an email but still haven't heard from them..
Also to note: If I disable notifications from the app through the new jellybean app info screen, the screen still unlocks and lits up but no sound or notification..my last desperate attempt would be to disable the permission to unlock screen somehow, is that possible?
Click to expand...
Click to collapse
dude just try reinstalling it then and are you using any custom rom . though it should not cause such a problem
khuzema9 said:
dude just try reinstalling it then and are you using any custom rom . though it should not cause such a problem
Click to expand...
Click to collapse
As I stated in the original post, tried multiple times. Even went back to stock ICS just to see if it would help.
I believe it's the latest update they did last October which causes this issue. Gives me the same result in both my gnex and nexus one. Prior to the update it wasn't acting like it. I made a follow up email and the response I got was that it has been forwarded to the 'proper department'
Sent from my Galaxy Nexus using Tapatalk 2
thephantom said:
I believe it's the latest update they did last October which causes this issue. Gives me the same result in both my gnex and nexus one. Prior to the update it wasn't acting like it. I made a follow up email and the response I got was that it has been forwarded to the 'proper department'
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I had the problem before that and during some version it stopped and came back in October sometime sounds about right. It's a shame really.. But it's a free app that originated from iOS so shouldn't expect too much I guess..
Is there any way to strip the app of the permission?
I think going back to the previous version would fix it. But the one prior to the current version had proximity sensor issues
Sent from my Nexus 4 using Tapatalk 2
Hi,
This is a member of the Viber R&D Team.
@Bresch - Thanks for reporting your issue...
We are continuously working on updates, we hope the next update will fix this issue too.
One question, can you please tell us if this issue is unique only to Viber or is it relevant to other apps too?
Thanks,
Viber
Viber Team said:
Hi,
This is a member of the Viber R&D Team.
@Bresch - Thanks for reporting your issue...
We are continuously working on updates, we hope the next update will fix this issue too.
One question, can you please tell us if this issue is unique only to Viber or is it relevant to other apps too?
Thanks,
Viber
Click to expand...
Click to collapse
It is unique to viber. I've never had anything else unlock the screen...Especially not when you have the screen locked with a code or password.
Thanks for the info.
As we said, when our next major update is released, please try it out and let us know if the problem is resolved. If not, we'll be right here to assist and check the matter thoroughly.
Tested the update and still screen unlocks despite being unchecked in the settings. Nice work on being able to use system notifications though
Sent from my Nexus 4 using Tapatalk 2
Hi there,
As some of you have already noticed, we have released a new version of Viber - 2.3.0 !
What's new?
- Use your own ringtones from Android as your Viber ringtones!
- Include cool emoticons in your Viber text message.
- Reply to cellular (regular) SMS using Viber.
- Share Stickers with your Viber contacts.
- Add a custom location to your Viber texts.
- Many other enchancements and improvements.
So, make sure you download the latest version!
Please feel free to let us know your thoughts, questions and comments, we'd be happy to hear from you.
Viber Team
@thephantom -
Thanks for the report.
We kindly ask that you take a minute and report the details of the problem to our support team using this direct link: http://bit.ly/ukGVJ0
With this information, our development team will hopefully be able to find the source of the problem, and ultimately resolve it
Thanks in advance
Thanks for responding Viber team. I have already sent a report since Oct 4 which unfortunately doesn't have any concrete response. In fact, here's a screenshot of it tagged closed.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It would be nice to look at it as I've explained before that not only did I experience it on jellybean but also on another phone running gingerbread
Sent from my Nexus 4 using Tapatalk 2
@thephantom -
Thank you for the info.
There might have been some confusion there - "Closed" doesn't mean we stopped handling the problem, it merely means that it has been transferred departments within our own company.
However, I will make sure that this issue is brought up in our upcoming meetings and we will see what can be done to reproduce it here in our labs.
We apologize for any inconvenience caused.
Wow. Gotta hand it to you. After posting in a public forum, I got an email update all of a sudden. Whereas before, it took weeks and even months for a response. I guess it's better to post issues here
Sent from my Nexus 7 using Tapatalk 2
what's the point with having the permission to unlock screen anyway? its totally unnecessary! Why would you EVER want your phone waking up?
If its in your hand, you just unlock it yourself.
If its in your pocked, you NEVER want it to unlock.
Simply just strip the app of the permission please..this is not iOS. We don't want our phones getting lit up..
Related
I'm posting this here because I'm a noob and not yet allowed to post in the dev forums....
Thanks Jermaine151 for all of your time and effort! This is my first time flashing a ROM, and my old Incredible is now fast, smooth, and gets WAY better battery life.
The only issue I can't seem to figure out is the speech to text problem. I've read all the applicable posts (I think).... Tried anonymizing search history in dashboard, turning off voice customizations in voice settings, clearing voice search app data... With no luck. My voice to text is completely broken when there is any background noise. Am I missing something? Thanks in advance.
Sent from my ADR6300 using Tapatalk
Maddog61 said:
I'm posting this here because I'm a noob and not yet allowed to post in the dev forums....
Thanks Jermaine151 for all of your time and effort! This is my first time flashing a ROM, and my old Incredible is now fast, smooth, and gets WAY better battery life.
The only issue I can't seem to figure out is the speech to text problem. I've read all the applicable posts (I think).... Tried anonymizing search history in dashboard, turning off voice customizations in voice settings, clearing voice search app data... With no luck. My voice to text is completely broken when there is any background noise. Am I missing something? Thanks in advance.
Sent from my ADR6300 using Tapatalk
Click to expand...
Click to collapse
can you check something for me. go to settings > voice input & output > text to speech settings and click default engine and make sure you have one installed.
another way to test its to download https://market.android.com/details?id=com.dexetra.iris and if you dont have the text to speech engine it will ask to download it for the market
Thanks for getting back to me!
I checked and I do have an engine installed. It says "pico tts" and the box is ticked. I also downloaded Iris from your link. It didn't prompt me to install anything else.
The TTS works great if it's quiet, but any noise such as the air conditioning blowing in the car, or road noise, will cause it to hear nothing.
Sent from my ADR6300 using Tapatalk
Maddog61 said:
Thanks for getting back to me!
I checked and I do have an engine installed. It says "pico tts" and the box is ticked. I also downloaded Iris from your link. It didn't prompt me to install anything else.
The TTS works great if it's quiet, but any noise such as the air conditioning blowing in the car, or road noise, will cause it to hear nothing.
Sent from my ADR6300 using Tapatalk
Click to expand...
Click to collapse
oh so its picking up everything around you and not just your voice.
talking to iris and it works she hears you fine and all that?
is the box check for "personalized recognition" in settings > voice input & output settings > voice recognized settings ?
synisterwolf said:
oh so its picking up everything around you and not just your voice.
talking to iris and it works she hears you fine and all that?
is the box check for "personalized recognition" in settings > voice input & output settings > voice recognized settings ?
Click to expand...
Click to collapse
Kind of...
It's more like... When you use voice input in an environment with ANY background noise... You get the notice "no speech heard". It's like the mic is muted, and even if you yell into the phone it barely registers in the graphic display, or not at all... It acts the same with Iris, vlingo, etc.
I've read in other forums that this was a known bug with the 2.3 OTA, even on other devices, but it was later fixed with a patch.
I've tried it w/customization on and off, anonymized search history, and cleared voice search data. No luck.
In the stock+ v2.6 thread, it seems that others have had this problem but we're able to fix it by turning off customization.
Sent from my ADR6300 using Tapatalk
Maddog61 said:
Kind of...
It's more like... When you use voice input in an environment with ANY background noise... You get the notice "no speech heard". It's like the mic is muted, and even if you yell into the phone it barely registers in the graphic display, or not at all... It acts the same with Iris, vlingo, etc.
I've read in other forums that this was a known bug with the 2.3 OTA, even on other devices, but it was later fixed with a patch.
I've tried it w/customization on and off, anonymized search history, and cleared voice search data. No luck.
In the stock+ v2.6 thread, it seems that others have had this problem but we're able to fix it by turning off customization.
Sent from my ADR6300 using Tapatalk
Click to expand...
Click to collapse
do you have root?
if so try another rom?
when talking on the phone can people here you. or when using google search can it pick you up on there?
maybe there is lint in you mic on the bottom. have you tried cleaning it?
(sorry trying to cover all the basses.)
synisterwolf said:
do you have root?
if so try another rom?
when talking on the phone can people here you. or when using google search can it pick you up on there?
maybe there is lint in you mic on the bottom. have you tried cleaning it?
(sorry trying to cover all the basses.)
Click to expand...
Click to collapse
I do have root. Just rooted a couple of weeks ago, and this is my first ROM. I may have to try another ROM, ... I just like this one, and wanted to keep it if possible.
I need to look into what all I have to set up again if I do a nandroid restore.
I did clean the mic hole just for fun. No dice.
Also, all other mic functions Work great, just no voice to text w/background noise. Like in a moving car... Which is when I need it! Lol. It did work fine on 2.2. There are lots of complaints about it to online about GB breaking speech to text on the evo too. Going to CM would fix it in their tests. Thanks again for helping me.
Sent from my ADR6300 using Tapatalk
Maddog61 said:
I do have root. Just rooted a couple of weeks ago, and this is my first ROM. I may have to try another ROM, ... I just like this one, and wanted to keep it if possible.
I need to look into what all I have to set up again if I do a nandroid restore.
I did clean the mic hole just for fun. No dice.
Also, all other mic functions Work great, just no voice to text w/background noise. Like in a moving car... Which is when I need it! Lol. It did work fine on 2.2. There are lots of complaints about it to online about GB breaking speech to text on the evo too. Going to CM would fix it in their tests. Thanks again for helping me.
Sent from my ADR6300 using Tapatalk
Click to expand...
Click to collapse
no worries. i like brain storming. you can try another gb sense 2.1 rom like this one http://forum.xda-developers.com/showthread.php?t=1232557
1.when flashing a new rom the steps most people take to make sure all there data transfers over is do use an app called titanium backup. its free. just only 2.back up user apps and data not system.
3.then download the rom of your choice.
4.manually boot into recovery with the phone off press power and vol - till you see hboot screen (white with the 3 androids on the bottom)
click recovery.
when in recovery make a back up of your current rom.
wipe data and factory cache
then wipe cache partition
install rom that you downloaded and boot it back up.
download titanium from the market and restore user apps with data.
the only real things you would have to set up again are any system settings its not to bad to do.
I will give it a shot this weekend. Thanks again for you time! There are some seriously helpful people around here.
Sent from my ADR6300 using Tapatalk
Maddog61 said:
I will give it a shot this weekend. Thanks again for you time! There are some seriously helpful people around here.
Sent from my ADR6300 using Tapatalk
Click to expand...
Click to collapse
just think of it this way. were are all where you are at one point. only way to learn is to ask, gain the knowledge, then pass it on to keep the community alive.
feel free to pm me anytime if you have a problem or a question.
I appreciate that sir.
Sent from my ADR6300 using Tapatalk
Works fine with Froyo...
Here's an update:
I flashed the McSense rom. (Sweet rom too BTW) Same problem though. No speech heard in moving vehicle.
Nandroided back to stock froyo...works fine
Flashed Skyraider Sense. (Very functional, but not as smooth and fast...not sure if I'm getting the same battery life...too early to tell) (Froyo based) Speech to text works perfectly again.
I've found many threads on the web like this one...
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=4399393a95831baa&hl=en
and this..
http://androidforums.com/incredible-all-things-root/416724-2-3-inc-1-update-no-speech-heard-while-driving.html
So I'm guessing that GB broke this function on the Incredible....and it was never fixed? I wonder what jermaine151 thinks? I can't post in the dev forum yet. I would love to go back to his rom, just can't live without that function.
Maddog61 said:
Here's an update:
I flashed the McSense rom. (Sweet rom too BTW) Same problem though. No speech heard in moving vehicle.
Nandroided back to stock froyo...works fine
Flashed Skyraider Sense. (Very functional, but not as smooth and fast...not sure if I'm getting the same battery life...too early to tell) (Froyo based) Speech to text works perfectly again.
I've found many threads on the web like this one...
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=4399393a95831baa&hl=en
and this..
http://androidforums.com/incredible-all-things-root/416724-2-3-inc-1-update-no-speech-heard-while-driving.html
So I'm guessing that GB broke this function on the Incredible....and it was never fixed? I wonder what jermaine151 thinks? I can't post in the dev forum yet. I would love to go back to his rom, just can't live without that function.
Click to expand...
Click to collapse
try sending him a pm and see what he thinks. also can you make a back up and try CM7 i know for sure it works because that is what i use on my phone. if it doesnt work then its your phone if it does then start posting random post in here so you can go to his thread.
I'll try that when the kids start feeling better. We're having a puke fest @ my house!
Sent from my ADR6300 using Tapatalk
You are definitely not alone. Same as you, all of my searching has turned up a bunch of people making the same claim following the GB update. I find it strange that such a major feature has not caused any action by HTC or Verizon. I seem to recall that there was an update for one of the HTC phones on Sprint that fixed the issue, but I don't recall for certain at this point.
I am rooted and have run 3 or 4 different stock GB ROM's and they have all had the issue. I am currently on Stock Plus V2.6 and I also tried all of the steps you mentioned but no dice for me either.
yes, your not alone with this problem... It really is a pain because I use that speech to text a lot.. If there is any kind of background noise at all it doesn't work. But it works fine if you are in a completely silent room. If have tried all the suggestions but it just doesn't work as good a froyo..
Ahh. Good. So I'm not crazy
The good thing is, it forced me to learn how to do a nandroid restore, and to try some other roms.
I really like SkyRaider Sense 4.3. Tons of useful features, super stable so far, and the battery life looks to be excellent. I'll likely stick with it.
Sent from my ADR6300 using Tapatalk
looks like VZW knows your problem.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Lol. Now I like skyraider and I'm trying to avoid the OTA.
;
Sent from my ADR6300 using Tapatalk
Maddog61 said:
Lol. Now I like skyraider and I'm trying to avoid the OTA.
;
Sent from my ADR6300 using Tapatalk
Click to expand...
Click to collapse
lol well if you ever want to upgrade im sure the devs will add this patch to there roms once the zip is available.
It has been 2-3 days since the notification bar sopped functioning at all. I thought it might be problem with the ROM i was using. So i flashed another ROM. But the problem persists. Please help me fix this I don't know what caused this but I think something went seriously wrong. Any help is very much appreciated.
amibnrj said:
It has been 2-3 days since the notification bar sopped functioning at all. I thought it might be problem with the ROM i was using. So i flashed another ROM. But the problem persists. Please help me fix this I don't know what caused this but I think something went seriously wrong. Any help is very much appreciated.
Click to expand...
Click to collapse
Not much information - which ROM are you using (now and before...)? And you haven't flashed a new ROM/installed new apps before the problem occured?
eventcom said:
Not much information - which ROM are you using (now and before...)? And you haven't flashed a new ROM/installed new apps before the problem occured?
Click to expand...
Click to collapse
Before this i was using Joy OS ROM... then i went back to my stock ROM backup... now i am on KoolSense ROM... and i was on the joy os for pretty long time... do you think too much flashing is the cause of the problem??
amibnrj said:
Before this i was using Joy OS ROM... then i went back to my stock ROM backup... now i am on KoolSense ROM... and i was on the joy os for pretty long time... do you think too much flashing is the cause of the problem??
Click to expand...
Click to collapse
I dont think too much flashing has caused it,TBH i flash a new ROM almost daily,I have flashed ROMs on my phone hundreds of times,without a problem. :laugh:
That might be a hardware issue,I would suggest you to flash CM 7 and get the statusbar at the bottom of the screen through tablet tweaks setting as a temporary fix.I guess you need to replace your touch panel if its a hardware issue.
Or switch to landscape mode and stick some icons at the left side of the screen, which would be the top in portrait mode. See if there's a dead spot on your touchscreen.
Sent from my GT-I9100 using xda premium
Scratch0805 said:
Or switch to landscape mode and stick some icons at the left side of the screen, which would be the top in portrait mode. See if there's a dead spot on your touchscreen
Click to expand...
Click to collapse
I like those moments when simple little things flash up a short spot onto all the experience someone has with a certain topic. Outta thx again, I'll give you one of those instead :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
eventcom said:
I like those moments when simple little things flash up a short spot onto all the experience someone has with a certain topic. Outta thx again, I'll give you one of those instead :
Click to expand...
Click to collapse
Not a 100% sure but I read somewhere the other day that the thanks are unlimited on the xda app, I've never counted how many I've used in a single day but I've never run out.....
I'm not saying that because I want people to hit the thanks button for me as I don't really care how many I have but I've seen you mention that you'd run out before, I get enough enjoyment knowing I helped someone, made someone chuckle or just p'eed someone off....
Sent from my GT-I9100 using xda premium
Scratch0805 said:
Not a 100% sure but I read somewhere the other day that the thanks are unlimited on the xda app, I've never counted how many I've used in a single day but I've never run out.....
I'm not saying that because I want people to hit the thanks button for me as I don't really care how many I have but I've seen you mention that you'd run out before, I get enough enjoyment knowing I helped someone, made someone chuckle or just p'eed someone off....
Click to expand...
Click to collapse
interesting I'll check this out lol (already noticed that it's some kind of mystery as I'm pretty sure that I've given much more than 8 thx per day - more than once...)
Confirmed lol
Swyped from my HTC Wildfire (Buzz)
thanx everyone for your advice... just today noticed that in landscape mode the notification bar is drawable and i think there is a dead spot on the top of the screen... guess have to get it corrected though...
amibnrj said:
thanx everyone for your advice... just today noticed that in landscape mode the notification bar is drawable and i think there is a dead spot on the top of the screen... guess have to get it corrected though...
Click to expand...
Click to collapse
Yeh you'll probably need a new digitiser (touchscreen) don't get ripped off by someone charging you a fortune to do it, they are pretty cheap on eBay to buy and not too difficult to fit. Unless you're clumsy like me, I ended up snapping the button backlight cable so my backlights don't work.
Sent from my GT-I9100 using xda premium
Really is a piece of cake. I got an ebay replacement for £8gbp and followed a guide on here somewhere in less than 10 minutes. I too broke the clip but on the old digi taking more care with new replacement. Only part i didnt follow was the heat gun to loosen the glue!! I just forced it out by pushing it..... Worked but then your left with a not fully sealed screen which small dust particles etc sneak through. So my advice is to follow the guide without cutting corners lol. On the plus side.... Ive since fixed with some small ammounts of unibond . Im sure some kind soul will post the guide link :thumbup: late now so off to bed. Zzzzzzzzz
Sent mysteriously ota
Scratch0805 said:
Yeh you'll probably need a new digitiser (touchscreen) don't get ripped off by someone charging you a fortune to do it, they are pretty cheap on eBay to buy and not too difficult to fit. Unless you're clumsy like me, I ended up snapping the button backlight cable so my backlights don't work.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
This is crazy but now it seems this isn't hardware at all... Because today i installed an app called windows 7 notification bar and it works perfectly fine at the very place were i can't draw my notification bar... i can swipe right, left and tap on the same spot which i thought was dead... do you know how we can make some changes to the notification codes in the rom or what can i even do coz this is internal...
amibnrj said:
This is crazy but now it seems this isn't hardware at all... Because today i installed an app called windows 7 notification bar and it works perfectly fine at the very place were i can't draw my notification bar... i can swipe right, left and tap on the same spot which i thought was dead... do you know how we can make some changes to the notification codes in the rom or what can i even do coz this is internal...
Click to expand...
Click to collapse
If its a software fault then the only thing I can suggest is a fresh install, backup first then wipe data, cache and dalvik cache from recovery then install a ROM.
Failing that you can try going back to a stock ROM but with the full wipe mentioned above it should work either way.
Sent from my GT-I9100 using xda premium
amibnrj said:
... now i am on KoolSense ROM
Click to expand...
Click to collapse
if you're still on KoolSense and want to follow scratch's advice I'd suggest to choose a different ROM (just to make sure - I've read it needs heavy resizing...)
Scratch0805 said:
If its a software fault then the only thing I can suggest is a fresh install, backup first then wipe data, cache and dalvik cache from recovery then install a ROM.
Failing that you can try going back to a stock ROM but with the full wipe mentioned above it should work either way.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
I have already done it when faced the problem for the first time... this problem still remains even after wiping everything... do you think if i go back to things before downgrading and unrevoking the mobile, I can some how recover from this problem??
i have solve this into gsmat g1345 because in this phone there are a fuction CALIBRATION TOUCH!!!! If use this fuction and touch 4 random point... save results... after restart calibration.... touch correct point and notification bar restore!
Now it's possible insert calibration touch app into this phone??? Or need export this menu into wildfire.... can help ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
-----------------------------------------------------------------------------------------------
I'm in the Process of Reworking this post, so be warned things will change...
Also, I'm currently in the process of building the newest version of the ROM
Introducing
Project Bland Android, The successor to Bland Android. The goals of Project Bland Android, are simple. To Create three flavors of Android, Original, Cherry, and Dirty Boot (Sadly Name is now Temporarily Final). All work will remain open source, including Dirty Boot. Each Version will always be built upon the latest code base, and always attempt to update quickly. With the goal, of always being open, always being transparent, and always being helpful. This ROM is aimed to be a effort to help the community, and always have the community help others. If your not into that, this ROM will most likely not be for you.
Just like the Previous builds of Bland Android, I am not wanting to work on this all by myself the whole time, so any offers to help will not be turned down, I would love to see this working 100%, and growing, so PM me if interested, or just post in the thread, together, we can grow this ROM from more than a small project, but rather a community effort.
Introducing the Flavors:
Original Flavor, will remain Strictly AOSP, with small amounts of changes.
Cherry will become the Version that develops Somewhat rapidly, every week, there will be a vote for something to be cherry picked into Cherry, then during the next weeks vote, minor builds will be released with the goal of becoming stable by the time the next weeks cherry is integrated.
Finally, Dirty Boot, which will be the flavor that will develop at a slower pace, but with aims of always being stable. Again, code will remain open source, as long as credit is always provided. Not to mention, with enough request, support will be extended to other devices.
-----------------------------------------------------------------------------------------------
Current Android Version: 4.2.1_r1.2
Current Original Flavor: 0.0.3
Download:
-This build is tested to boot, not much more, unclear of bugs, most if not all should work, just supply your own G-APPs.
Current Cherry Flavor: 0.0.0
VOTING CLOSES FOR THIS BUILD: Feb 15th, 2013
Download:
Current Dirty Boot Flavor: 0.0.0
Download:
-----------------------------------------------------------------------------------------------
CREDITS FOR RESOURCES:
Thanks to greenblue for his easy to use source, which can be found here: on his github. or his tutorial:
here..
Kevdliu's Additional Toggles are integrated into the source, which can be found here: in this thread.
What works?
IDK yet
Whats Doesn't work?
IDK yet
Whats weird?
IDK yet
Old Versions...
ROM Build 3 is missing (hoping for a mirror)
ROM Build 2 (Missing Call Audio):
http://www.mediafire.com/download.php?bpib8jovq69xx3m
ROM Build 1 (Missing Audio and G-APPS):
http://www.mediafire.com/download.php?e352ga7jvx2sh4i
does phone volume woirk? does 4g wimax work?
r4dik4l said:
does phone volume woirk? does 4g wimax work?
Click to expand...
Click to collapse
There currently isn't any audio, period, phone volume and music volume aren't working yet though I'm hunting for the reason. And I can't test wimax (not in my area) but I added everything for wimax, so theoretically and I assume it should work.
this is my primary device, so until audio works I will not be able to test it much as soon as volume works I will test 4g wimax
r4dik4l said:
this is my primary device, so until audio works I will not be able to test it much as soon as volume works I will test 4g wimax
Click to expand...
Click to collapse
Well, I'm hunting for a fix for the audio, so hopefully soon that will be fixed.
are you able to use telephony from 4.1.2 or anything like that? I know hp420 has made a rom in the past and there are others, I wish I could help
My build has working audio. Took a while to get to it though since it keeps getting com.android.phone has stopped. Not sure if I should upload it and see if someone can find a fix.
yeah upload it, everyone helping rocks
ubnub82 said:
My build has working audio. Took a while to get to it though since it keeps getting com.android.phone has stopped. Not sure if I should upload it and see if someone can find a fix.
Click to expand...
Click to collapse
in call audio working? because thats the one thats got me stumped, I have everything else working it would appear.
budm said:
in call audio working? because thats the one thats got me stumped, I have everything else working it would appear.
Click to expand...
Click to collapse
Can't test in call audio as the phone force closing stops service.
ubnub82 said:
Can't test in call audio as the phone force closing stops service.
Click to expand...
Click to collapse
It might be worth uploading, seeing if anyone can get it going right.
The GPS is checked as if it is on, but when I try to use Google Now, it cannot register my location. Instead it gives me the option to access settings to turn on Location Services which are already on.
Sent from my Crespo4G using xda app-developers app
The Batman said:
The GPS is checked as if it is on, but when I try to use Google Now, it cannot register my location. Instead it gives me the option to access settings to turn on Location Services which are already on.
Sent from my Crespo4G using xda app-developers app
Click to expand...
Click to collapse
Did you try with Google Maps also? I was able to get a lock in maps, but that was all I tested in. Also, a logcat would be wonderful to see what is going on when this happens for you.
Google Maps attempts to lock into my location, unfortunately, both Google Maps and Google Now don't seem to be able to access GPS.
Going to see if I can get a logcat sometime today. Aldo want to check the settings to see if Google's "Gesture" keyboard is within the rom and if not whether installing a separate apk will work.
Edit: Google's Gesture keyboard is not set by default, however, I was able to install the apk separately and it works great. No logcat yet.
Also, when attempting to look at the Storage section under Settings, it FCs. This is also the case when attempting to access any 4G options for obvious reasons.
Sent from my Crespo4G using xda app-developers app
The Batman said:
Google Maps attempts to lock into my location, unfortunately, both Google Maps and Google Now don't seem to be able to access GPS.
Going to see if I can get a logcat sometime today. Aldo want to check the settings to see if Google's "Gesture" keyboard is within the rom and if not whether installing a separate apk will work.
Edit: Google's Gesture keyboard is not set by default, however, I was able to install the apk separately and it works great. No logcat yet.
Also, when attempting to look at the Storage section under Settings, it FCs. This is also the case when attempting to access any 4G options for obvious reasons.
Sent from my Crespo4G using xda app-developers app
Click to expand...
Click to collapse
Thanks for the heads up, I will add them to the OP, and please do get the logcat, and if you can get one for when the menus crash also, it might put me in the right direction.
budm said:
Thanks for the heads up, I will add them to the OP, and please do get the logcat, and if you can get one for when the menus crash also, it might put me in the right direction.
Click to expand...
Click to collapse
For some reason, I am unable to get a log cat. I keep getting the message "- waiting for device -" so I'm not exactly sure how to go about obtaining it. (FYI, I'm using a Mac).
If anyone has any tips on how or why this is not working, please feel free to let me know.
Edit: I was able to get the logcat. Do you want me to PM you with it (@budm)?
The Batman said:
For some reason, I am unable to get a log cat. I keep getting the message "- waiting for device -" so I'm not exactly sure how to go about obtaining it. (FYI, I'm using a Mac).
If anyone has any tips on how or why this is not working, please feel free to let me know.
Edit: I was able to get the logcat. Do you want me to PM you with it (@budm)?
Click to expand...
Click to collapse
Thanks for the Logcats, I'll read through them once I've had my morning coffee lol.
EDIT: Boy do I feel stupid. I forgot to include a few things, it should fix most your issues with the Google Now, and Maps.
Awesome. Just let me know if and when you want me to test out the new build. Unless of course you just post it in the OP.
Thanks for getting this rom together btw.
Edit: any way that you could cook the new Gmail apk into the rom? Also, I've been having Superuser issues. The rom doesn't allow for applications to obtain root access.
Sent from my Crespo4G using xda app-developers app
The Batman said:
Awesome. Just let me know if and when you want me to test out the new build. Unless of course you just post it in the OP.
Thanks for getting this rom together btw.
Edit: any way that you could cook the new Gmail apk into the rom? Also, I've been having Superuser issues. The rom doesn't allow for applications to obtain root access.
Sent from my Crespo4G using xda app-developers app
Click to expand...
Click to collapse
I'll be adding it to the OP once I fix/try to fix the settings stuff. and I just added the new Gmail ( I think, I'll double check this though) and I'll provide the SuperUser Zip for any issues. All in all, should be up in about 1 to 4 hours after I finish some things around my house.
is this ROM pretty stable? I am looking forward to flashing this but I know its a pretty new ROM and my phone has been acting funny and dont want to chance screwing it up!!
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.3 (Jelly Bean), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Instructions
First time flashing CyanogenMod 10.2 your device, or coming from another ROM?
Download the zip(s).
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe data & cache partitions of your device
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Useful Links
BBQLog changelog
Odin CyanogenMod wiki
Jira issue tracker
DO NOT REPORT BUGS FOR UNOFFICIAL BUILDS!
Other Issues?
Use this for obtaining logs.
These are unofficial beta builds so bug reports are not accepted. You are relying on yourself and your peers in this thread for support!
Download Links
CyanogenMod:
Builds: http://goo.im/devs/mithun46/CM4.3
Google apps addon:
Download: 4.3 Google Apps
Root access:
Go to Developer options --> Root Access
And change to "Apps and ADB" to fix root
Screenshots: 1, 2 & 3
Thanks to:
CyanogenMod: Thanks a lot! You guys are awesome!!
@jug6ernaut : For being a awesome friend! Thanks man!
Reserved
Sweet! Downloading now!
If I'm on stock rom, Do I just follow the OP instruction?
motoxxxx said:
If I'm on stock rom, Do I just follow the OP instruction?
Click to expand...
Click to collapse
Pretty much. Do you already have a recovery installed? You need to have an unlocked bootloader as well.
havanahjoe said:
Pretty much. Do you already have a recovery installed? You need to have an unlocked bootloader as well.
Click to expand...
Click to collapse
Thank! now I need to unlocked my bootloader.
How is the rom?
motoxxxx said:
Thank! now I need to unlocked my bootloader.
How is the rom?
Click to expand...
Click to collapse
I just installed it, looks good so far. Forgot to flash the superSU zip so I don't have root yet. Trying to figure out how to get into recovery after flashing.
If you are going to be restoring a Titanium Backup, there is a known issue on 4.3 where you have to change the backup folder location.
From the Nexus 4 thread:
Titanium Backup > Menu > Preferences > Backup Folder Location > DETECT > Whole Device > Select /storage/emulated/legacy/titaniumbackup and click yes when prompted to move backup files.
Click to expand...
Click to collapse
Looks like it works without doing that last step.
And in case you are trying to get into recovery, reboot and when you see the LED flash orange, hold the volume down button. Thanks mithun for the help
havanahjoe said:
I just installed it, looks good so far. Forgot to flash the superSU zip so I don't have root yet. Trying to figure out how to get into recovery after flashing.
If you are going to be restoring a Titanium Backup, there is a known issue on 4.3 where you have to change the backup folder location.
From the Nexus 4 thread:
Click to expand...
Click to collapse
Three otpions
1. Reboot phone, press volume down when you see the notification led go orange.
2. Advance reboot menu
3. From adb "adb reboot recovery"
jug6ernaut said:
Three otpions
1. Reboot phone, press volume down when you see the notification led go orange.
2. Advance reboot menu
3. From adb "adb reboot recovery"
Click to expand...
Click to collapse
Thanks jug6ernaut. Advanced reboot menu is not enabled by default. I had to look up where to enable it:
Enable developer options. (go to about phone, scroll to the bottom, find the “build number” field, click on it seven times and it will turn on developer options.)
go back one level to the main settings screen and you’ll see developer options now. Open that, Enable advanced reboot options by clicking on the relevant checkbox
Click to expand...
Click to collapse
havanahjoe said:
Thanks jug6ernaut. Advanced reboot menu is not enabled by default. I had to look up where to enable it:
Click to expand...
Click to collapse
True , which are under developer options for anyone wondering!
Small update for anyone who saw my "issue list" in the other CM thread. Almost all of my issues were caused by using the wrong gapps(was unaware there was a 4.3 version).
Im up on 4.3 again and its working beautifully , still few performance and graphical issues, but they are minor.
Edit: Cant get SMS to send, guessing this has to do with the Voice+ addition as MMS send fine. Can also receive MMS and SMS fine, just cant send SMS.
jug6ernaut said:
True , which are under developer options for anyone wondering!
Small update for anyone who saw my "issue list" in the other CM thread. Almost all of my issues were caused by using the wrong gapps(was unaware there was a 4.3 version).
Im up on 4.3 again and its working beautifully , still few performance and graphical issues, but they are minor.
Edit: Cant get SMS to send, guessing this has to do with the Voice+ addition as MMS send fine. Can also receive MMS and SMS fine, just cant send SMS.
Click to expand...
Click to collapse
Hmm I am running into the same issue with SMS, can't send.
I don't see the group MMS option in the stock messaging app. The Nexus 4 has it, so is this not the same Messaging app as the Nexus?
havanahjoe said:
Hmm I am running into the same issue with SMS, can't send.
I don't see the group MMS option in the stock messaging app. The Nexus 4 has it, so is this not the same Messaging app as the Nexus?
Click to expand...
Click to collapse
idk if this is an issue with CM for the ZL or what. Or if its my sim card. Plain and simple IDK.
BUT for me this is caused by my sim not having my phone number, the messaging app will not show the group messaging option if it does not know your number. To check this go to you phone settings/About Phone/Status/Phone number. Mine would show "UNKNOWN". To fix this after every flash i have to run a program called "Sim Number Changer", its an Xpoxed app. It worked for me.
jug6ernaut said:
idk if this is an issue with CM for the ZL or what. Or if its my sim card. Plain and simple IDK.
BUT for me this is caused by my sim not having my phone number, the messaging app will not show the group messaging option if it does not know your number. To check this go to you phone settings/About Phone/Status/Phone number. Mine would show "UNKNOWN". To fix this after every flash i have to run a program called "Sim Number Changer", its an Xpoxed app. It worked for me.
Click to expand...
Click to collapse
Ah yes. I had noticed that in my status page before, but didn't know it broke the Group MMS option. I'll use the Sim Number Changer.
I asked in the Z thread to see if they are having issues with SMS too.
EDIT: Sim Number Changer FCs on me
The Z users are able to send SMS, but they mentioned the HTC One had the problem. I looked in their threads and it's apparently gone in a new build.
I did a logcat and didn't see any errors when sending a message, other than chompsms telling me the message failed (and this I already had seen on the phone). The error message doesn't explain why.
---------- Post added at 05:16 PM ---------- Previous post was at 04:34 PM ----------
I don't like my phone showing up as a 6503 A quick build.prop edit fixes that.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
havanahjoe said:
The Z users are able to send SMS, but they mentioned the HTC One had the problem. I looked in their threads and it's apparently gone in a new build.
I did a logcat and didn't see any errors when sending a message, other than chompsms telling me the message failed (and this I already had seen on the phone). The error message doesn't explain why.
---------- Post added at 05:16 PM ---------- Previous post was at 04:34 PM ----------
I don't like my phone showing up as a 6503 A quick build.prop edit fixes that.
Click to expand...
Click to collapse
Haha nice!
Sent from my Nexus 7 using Tapatalk 2
jug6ernaut said:
Haha nice!
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
A little off topic, do you have the new Nexus 7?
havanahjoe said:
A little off topic, do you have the new Nexus 7?
Click to expand...
Click to collapse
I do .
jug6ernaut said:
I do .
Click to expand...
Click to collapse
The million dollar question is... Is it worth the upgrade from the original 7?
havanahjoe said:
The million dollar question is... Is it worth the upgrade from the original 7?
Click to expand...
Click to collapse
Tough question. I sold my original nexus 7 few months back in preparation for the new one. So for me its 100% worth it lol. Kind of hard for me to judge it the old model BC I don't have them side by side.
Buy I will say this thing is FAST. Screen is amazing, absolutely love it. Was thinking I would hate the space above/below the screen, don't mind it. Definitely thinner tho, its noticeable, also smaller side bezel is nice. One thing not getting a lot of attention is the speakers are definitely a step up from the original which were just poor.
Really the big thing for me is the screen, it really is a big improvement. Absolutely beautiful.
Is it worth it? Who knows, I say yes. I mean at the price it was hard to say no. If you have the original and your happy with it the new one isn't going to be anything ground breaking. But if you have the cash, it is a worthy upgrade.
Sent from my Nexus 7 using Tapatalk 2
jug6ernaut said:
Tough question. I sold my original nexus 7 few months back in preparation for the new one. So for me its 100% worth it lol. Kind of hard for me to judge it the old model BC I don't have them side by side.
Buy I will say this thing is FAST. Screen is amazing, absolutely love it. Was thinking I would hate the space above/below the screen, don't mind it. Definitely thinner tho, its noticeable, also smaller side bezel is nice. One thing not getting a lot of attention is the speakers are definitely a step up from the original which were just poor.
Really the big thing for me is the screen, it really is a big improvement. Absolutely beautiful.
Is it worth it? Who knows, I say yes. I mean at the price it was hard to say no. If you have the original and your happy with it the new one isn't going to be anything ground breaking. But if you have the cash, it is a worthy upgrade.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the quick review. I really don't have a lot of use for a tablet myself, I have my laptop with me almost all the time and I don't mind carrying it (even though it's a 17" MBP), but I have been considering using a Nexus 7 as Nav/Media in the car. I've seen several people with a Subaru Legacy do it on theirs and it seems to fit very well. In that case the screen wouldn't really matter that much and doing a quick search on craigslist I found a 16 GB for $100. With what you said, it seems like a no brainer to get the first gen.
Apologies for the off topic discussion. To bring it back to CM, I am currently building a copy myself. Thanks to mithun I got my Ubuntu VM ready for compiling and it's CCing away.
Just to qualify, I don't give two ****s about tripping knox, I just want this stupid broken "update" off my god damned phone that I PURCHASED and OWN. I have searched and read for hours, and I have not seen a single thing about downgrading the boot loader or the OS successfully, except for the falsely titled (and should be deleted as it's #1 in google) link here.
Someone please tell me there's a way to do this? I despise this update.
jmorgali said:
Just to qualify, I don't give two ****s about tripping knox, I just want this stupid broken "update" off my god damned phone that I PURCHASED and OWN. I have searched and read for hours, and I have not seen a single thing about downgrading the boot loader or the OS successfully, except for the falsely titled (and should be deleted as it's #1 in google) link here.
Someone please tell me there's a way to do this? I despise this update.
Click to expand...
Click to collapse
Ok so i'm guess you just purchased your Note 3 and it came with Kit Kat on it already? You say broken update? Can you please specify what is "BROKEN" about it. If you do not have the Knox issue that others have, then simply root your phone and run a custom rom. I assure you, whatever you think is broken with the phone will be fixed this way. Also read thru the update FAQ's and go thru the development thread for any issues you may have. Use the search box in the top right corner of any thread to look for a particular problem.
dragonstalker said:
Ok so i'm guess you just purchased your Note 3 and it came with Kit Kat on it already? You say broken update? Can you please specify what is "BROKEN" about it. If you do not have the Knox issue that others have, then simply root your phone and run a custom rom. I assure you, whatever you think is broken with the phone will be fixed this way. Also read thru the update FAQ's and go thru the development thread for any issues you may have. Use the search box in the top right corner of any thread to look for a particular problem.
Click to expand...
Click to collapse
My note 3 came with jellybean. I use a phone recording app to record all my calls. I also constantly move files between the sd card and the internal memory. Both of these things have broken since the update to kitkat. I would be happy to root my phone and go back to an earlier rom. Can you point me to a jellybean rom for t-mobile?
jmorgali said:
My note 3 came with jellybean. I use a phone recording app to record all my calls. I also constantly move files between the sd card and the internal memory. Both of these things have broken since the update to kitkat. I would be happy to root my phone and go back to an earlier rom. Can you point me to a jellybean rom for t-mobile?
Click to expand...
Click to collapse
Ok, I would like for you to read before posting in the future please.
1. Call recording was never a feature standard on TMO as it's illegal. It's a third party app that you can easily replace, just need the kit kat version.
2. The Sdcard R/W issue is not something that is "BROKEN" it is a standard feature on TW and Kit Kat, it makes the phone only write to the internal storage and you can only Read from the ExtSdcard. This was done because people buy $5 sdcards on Amazon then blame Android and their phones when performance sucks. This also has been discussed in-depth across XDA and every Android website known. In the developer section you will find all your answers. You just need to search and read.
dragonstalker said:
Ok, I would like for you to read before posting in the future please.
1. Call recording was never a feature standard on TMO as it's illegal. It's a third party app that you can easily replace, just need the kit kat version.
2. The Sdcard R/W issue is not something that is "BROKEN" it is a standard feature on TW and Kit Kat, it makes the phone only write to the internal storage and you can only Read from the ExtSdcard. This was done because people buy $5 sdcards on Amazon then blame Android and their phones when performance sucks. This also has been discussed in-depth across XDA and every Android website known. In the developer section you will find all your answers. You just need to search and read.
Click to expand...
Click to collapse
To expand on #2 it was also done to prevent 3rd party apps from writing to the entire SD Card in a major security issue.
Google made this change about 2 years ago and finally started to enforce it.
Also I don't know if you will have compatibility issues with going back to 4.3 while having a (unchangeable) 4.4.2 Boot loader. Its worth a shot though. But as the other poster mentioned if you root 4.4.2 you can get the SD Card RW back without having to go to 4.3
Sent from my SM-N900T using Tapatalk
I agree with OP, this KitKat update has totally soured me on the Note 3. I used to adore my battery life; now I despise it. I also used a call recorder app that no longer works on KitKat. These are only a couple of the numerous issues I've had with the update. I'd gladly downgrade if I could.
---------- Post added at 09:10 AM ---------- Previous post was at 09:05 AM ----------
dragonstalker said:
Ok, I would like for you to read before posting in the future please.
1. Call recording was never a feature standard on TMO as it's illegal.
Click to expand...
Click to collapse
Call recording is legal in many, many areas including where I live. Your statement is ignorant. I would like for you to read before posting in the future please.
hfuizo said:
I agree with OP, this KitKat update has totally soured me on the Note 3. I used to adore my battery life; now I despise it. I also used a call recorder app that no longer works on KitKat. These are only a couple of the numerous issues I've had with the update. I'd gladly downgrade if I could.
---------- Post added at 09:10 AM ---------- Previous post was at 09:05 AM ----------
Call recording is legal in many, many areas including where I live. Your statement is ignorant. I would like for you to read before posting in the future please.
Click to expand...
Click to collapse
Only in 12 States are not one party consent consider legal and admissable in court, But recording somebody phone calls without their knowledge is illegal and will get you sued. If you don't know what you are talking about. Please don't chime in.
Please don't try to challenge and confuse users. This is the exact reason the app is not standard on phones.
Accepted forms of notification for recording by a telephone company
The FCC defines accepted forms of notification for telephone recording by telephone companies as:
Prior verbal (oral) or written notification of all parties to the telephone conversation.
Verbal (oral) notification before the recording is made. This is the most commonly used type.
An audible beep tone repeated at regular intervals during the call.
dragonstalker said:
Ok, I would like for you to read before posting in the future please.
Click to expand...
Click to collapse
dragonstalker said:
Please don't chime in.
Click to expand...
Click to collapse
You are a condescending little twit. Not to mention the fact you are the one who posted incorrect information. I'm done with you.
hfuizo said:
You are a condescending little twit. Not to mention the fact you are the one who posted incorrect information. I'm done with you.
Click to expand...
Click to collapse
I'm sorry, that would be very knowledgable old twit, that just retired after 20 years of communication background on secured system. Information Security is kinda my job. Nothing i said was incorrect, and my statement stands, if your on XDA and you refuse to READ before posting, expect what your mind considers condescending .
As far recording being illegal goes, I'd love to hear the Aristotelian logic behind that. What's practical about recording being illegal?
But the other issue, downgrading, I don't understand why you can't just go to sammobile.com, get the old firmware and flash that honey.
I believe of you try to flash a 4.3 Rom or image with the 4.4 boot loader it will just fail the check and won't flash at least it was like that on a different t phone I had.
Sent from my Nexus 7 using Tapatalk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've gotta troubleshoot this. I hate kitkat
Sent from my SM-N900T using Tapatalk
hello all. I am also having problems with my TMO Note3. Since the 4.4.2 update the data has been flaky. I did couple of factory reset and did not help. before the update the device worked flawless. It would be great if we could go back to 4.3 til a patch is out to fix all the problems..
No problems with 4.4.2 at all. Stock rooted with a little bloat removed.
Sent from my SM-N900T using xda app-developers app
same here after the 4.4.2 update, the modem is much better, better signal that is for sure... no problems at all..
Nellyinda803 said:
I've gotta troubleshoot this. I hate kitkat
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
I only get a few hours screen time too but my battery will last 2 to 3 days. Wierd.
What aggravates me most is my battery monitor apps wont work cause im not rooted. They must not want us to know what the hell they're really running.
dragonstalker said:
Only in 12 States are not one party consent consider legal and admissable in court, But recording somebody phone calls without their knowledge is illegal and will get you sued. If you don't know what you are talking about. Please don't chime in.
Please don't try to challenge and confuse users. This is the exact reason the app is not standard on phones.
Click to expand...
Click to collapse
This is silly... Just because something can be used illegally does not make it illegal to use. If you notify as required by your State, it is not a problem and a very useful tool. BTW I am in one of those single party States, but Inform the other party on all calls if I will be using it.
herach said:
hello all. I am also having problems with my TMO Note3. Since the 4.4.2 update the data has been flaky. I did couple of factory reset and did not help. before the update the device worked flawless. It would be great if we could go back to 4.3 til a patch is out to fix all the problems..
Click to expand...
Click to collapse
Once you do the OTA, there is not going back without rooting apparently.
krelvinaz said:
This is silly... Just because something can be used illegally does not make it illegal to use. If you notify as required by your State, it is not a problem and a very useful tool. BTW I am in one of those single party States, but Inform the other party on all calls if I will be using it.
Click to expand...
Click to collapse
Well, that's up to the court. I, for one, will not record phone calls, even asking the other party. Actually, I am puzzled: in what situation will you need to record the call?
I mean, seriously, when on a call with your friend, company, boss or coworkers, do you TELL them you are recording the call? That just creates conflict.
I can say after 2 weeks this update is atrocious. Random reboots happen daily and several times at that. After deleting all Knox apks and odex files it still will appear Unfortunately Samsung Knox has stopped, if I'm on the market and every time I turn on the phone. Battery Life is better but not worth this mess. Network issues with tmobile but not on ATT. I have a s4 on tmobile it has no issues only my note 3. 4.3 is more stable and more reliable.
Sent from my SM-N900T using Tapatalk