Related
The dev has released more updates, currently on version 0.6. Check it out, the app got a whole lot cooler, and is in pretty active development now!
There's a dev in the I9000 forums working on using the AMOLED screen to display notifications. Currently it's displayed as a red dot in the top left corner of the screen. It's in an early stage, but it works on my Captivate.
Read the thread here for more info:
http://forum.xda-developers.com/showthread.php?t=730692
The dev is apparently going on vacation soon, and won't be working on it for a while, so any potential developers here that know how to implement something like this, take note!
Edit: I don't take responsibility for the work on this app at all; just posting here because it works on the Captivate and is an awesome idea.
Sweet this is something exactly what I was looking for!
Hope he can make use of the bottom 4 buttons or something.
Edit: I just read there are no API's to light up the capacitive buttons
But the project so far looks amazing. I'll have to give it a run when I get off of work.
works! sideloaded this thing right into my Captivate easier than rooting (and that was possibly the easiest thing I've done customizing a phone in the past!)
thanks! was definitely missing my notification LED from my last two WinMo phones....
I have got to find out how to side load apps.
Install the Android sdk, add the tools directory to the system PATH, install Samsung drivers to your computer if its 64 bit Windows you need 64 bit drivers, open a command prompt, type "adb install blahblah.apk"... that's pretty much it... obviously your current working directory needs to be the same as the apk file.
For those who don't want to get real dirty
http://www.androidcentral.com/sideload-android-apps-all-you-want-sideload-wonder-machine
tysj said:
For those who don't want to get real dirty
fantastic!!! Thank you tysj
Click to expand...
Click to collapse
tysj said:
For those who don't want to get real dirty
http://www.androidcentral.com/sideload-android-apps-all-you-want-sideload-wonder-machine
Click to expand...
Click to collapse
yeah, that's what I used alright..... WAY too simple to use, I mean, it isn't drag and drop to a CAB folder like WinMo, but this thing installs the program for you, making it just that much easier to use!
Wow I'm going to have to try that way installer thing since I'm not rooted
Sent from my SAMSUNG-SGH-I897 using XDA App
Works for my on my captivate. Thanks for the great work OP!
how does this app affect battery life?
the developer said that since it doesn't use any timers within the cpu, it is very VERY minimal on battery.
It worked for me with an SMS, (I use Handcent) but it didn't work for an email. (K9-mail)
I had to remove it because it wasn't letting me go to my screen our unlock my phone
Sent from my SAMSUNG-SGH-I897 using XDA App
madjsp said:
I had to remove it because it wasn't letting me go to my screen our unlock my phone
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
The screen is already on so you have to press the Home button.
it was not working correctly every time. It would render the touch screen useless until I locked and unlocked it a few times.
Sent from my SAMSUNG-SGH-I897 using XDA App
madjsp said:
it was not working correctly every time. It would render the touch screen useless until I locked and unlocked it a few times.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Well, it's still better than nothing. The app is still very much a work-in-progress, and hopefully the dev makes some good progress on it soon.
I've been trying to learn how to write Android apps, since the dev won't be around for a while to work on it, but all I've accomplished is realizing how incompetent I am in Java, heh.
When i first saw this app the word pixel burnout came to mind. But the dev says the red square moves around on the screen to prevent that so it might just end up being useful. I think samsung and google need to give us an api to use the menu keys since they didn't provide us with a notification light.
Sent from my SAMSUNG-SGH-I897 using XDA App
60HertzJig said:
Well, it's still better than nothing. The app is still very much a work-in-progress, and hopefully the dev makes some good progress on it soon.
I've been trying to learn how to write Android apps, since the dev won't be around for a while to work on it, but all I've accomplished is realizing how incompetent I am in Java, heh.
Click to expand...
Click to collapse
Oh I agree, it is a work in progress. It was an awesome idea, but I was close to some battery pulls because I couldn't get the touch screen to work.
I wonder about all the complaints regarding a notification LED, since Samsung gave us 384,000 LEDs to play with.
So this is a well-known trick that has worked since the N4 but I wanted to share it anyway. If you go to check for the update and it still says up to date, try this method as it has just worked for my N5 and my N7:
Settings>Apps>All Tab>Google Services Framework>Clear Data>Go back to check update and it should work, if not try the steps again.
Like I said, this has worked for my previous N4, N5, and N7(2013). Each time, I tried the check update button alone at least 5 times in a row with no luck, then trying the trick and checking it worked for each device.
Oh and BTW, this trick if done EXACTLY like this DOES NOT invalidate the tokens like some claim. My play store and GMAIL are completely fine on both devices.
PS: Do this at your own risk/if your new to Android (Butthurt syndrome cured)
A Google employee also explained why you should not do this: http://www.reddit.com/r/Android/com...ear_data_for_google_service_framework/cdiymrp
Oh no you didn't.
myorks1127 said:
So this is a well-known trick that has worked since the N4 but I wanted to share it anyway. If you go to check for the update and it still says up to date, try this method as it has just worked for my N5 and my N7:
Settings>Apps>All Tab>Google Services Framework>Clear Data>Go back to check update and it should work, if not try the steps again.
Like I said, this has worked for my previous N4, N5, and N7(2013). Each time, I tried the check update button alone at least 5 times in a row with no luck, then trying the trick and checking it worked for each device.
Oh and BTW, this trick if done EXACTLY like this DOES NOT invalidate the tokens like some claim. My play store and GMAIL are completely fine on both devices.
Click to expand...
Click to collapse
You're wrong, you shouldn't do that. A quick Google will tell you why
bozzykid said:
A Google employee also explained why you should not do this: http://www.reddit.com/r/Android/com...ear_data_for_google_service_framework/cdiymrp
Click to expand...
Click to collapse
I read that post before and have yet to find a single issue with my devices and never had an issue for my N4 when I did it so I don't see what the big deal is...there is another very similar method that does indeed mess up the tokens but it IS NOT the same by any means.
Please prove me wrong, I will check anything on my phone that you think isn't working now because I did this the quick and easy way instead of wasting my time sideloading...
myorks1127 said:
I read that post before and have yet to find a single issue with my devices and never had an issue for my N4 when I did it so I don't see what the big deal is...there is another very similar method that does indeed mess up the tokens but it IS NOT the same by any means.
Please prove me wrong, I will check anything on my phone that you think isn't working now because I did this the quick and easy way instead of wasting my time sideloading...
Click to expand...
Click to collapse
i'm going to go out on a limb and guess that you don't work for Google, specifically the Android/Mobile division. but since you don't see what the big deal is (going against what a Google engineer says) we should all believe you.
this may not mess up your phone, but it wrecks havoc on the back end of Google's servers... when a Google engineer tells us all not to do something, then thoroughly explains why, it's probably best to heed his advice.
Tried this, took five data clears and it gave me the update. Thanks!
Sent from my Nexus 5 using xda app-developers app
Lucke said:
i'm going to go out on a limb and guess that you don't work for Google, specifically the Android/Mobile division. but since you don't see what the big deal is (going against what a Google engineer says) we should all believe you.
this may not mess up your phone, but it wrecks havoc on the back end of Google's servers... when a Google engineer tells us all not to do something, then thoroughly explains why, it's probably best to heed his advice.
Click to expand...
Click to collapse
It doesn't wreak havok on my end so why would I care?
I'll go out on a limb and say if it caused that much grief for Google the clear data feature would have been gone a long time ago.
Its worked since the nexus s btw
Sent from my Nexus 5 using xda app-developers app
---------- Post added at 06:02 PM ---------- Previous post was at 06:01 PM ----------
I've done it with every update since ICS and never had an issue...and its always worked
Sent from my Nexus 5 using xda app-developers app
Glad I finally have some people backing me up lol, my brother is an engineer for Amazon and he thinks he knows everything too...
And this is how people who don't know better come here to XDA and mess up their devices because they follow bad advice that they read. Don't do this. It can have unintended consequences and according to Google has absolutely no effect on when you will receive an OTA.
muyoso said:
And this is how people who don't know better come here to XDA and mess up their devices because they follow bad advice that they read. Don't do this. It can have unintended consequences and according to Google has absolutely no effect on when you will receive an OTA.
Click to expand...
Click to collapse
People who don't follow the exact directions you mean..and are you saying that this trick worked for 3 Nexus devices I own completely by chance after trying to update over 5 times each before doing the trick and then it working after the trick?
myorks1127 said:
People who don't follow the exact directions you mean..and are you saying that this trick worked for 3 Nexus devices I own completely by chance after trying to update over 5 times each before doing the trick and then it working after the trick?
Click to expand...
Click to collapse
What I am saying is that it doesn't matter how many people like you swear that it works. The people who actually work on Android say it doesn't and that it can have bad consequences. And anyone who actually wants the update can simply sideload it with absolutely no ill effects if they want to force the update onto their devices early. There is absolutely zero reason to do what you swear works.
muyoso said:
What I am saying is that it doesn't matter how many people like you swear that it works. The people who actually work on Android say it doesn't and that it can have bad consequences. And anyone who actually wants the update can simply sideload it with absolutely no ill effects if they want to force the update onto their devices early. There is absolutely zero reason to do what you swear works.
Click to expand...
Click to collapse
The reason to do it is to save time and hassle of doing all the steps needed for side loading, but no worries, I got the update faster and easier than anyone who side loaded with ZERO consequences to me..:good:, your Google knee pads must be pretty worn out by now huh?
Or you can just wait for the update. I'm still on 4.4 and happy about it. 4.4.1 brought radio issues, and 4.4.2 also seems to have a few bugs. Hopefully by the time I get the OTA, the bugs will be fixed.
myorks1127 said:
The reason to do it is to save time and hassle of doing all the steps needed for side loading, but no worries, I got the update faster and easier than anyone who side loaded with ZERO consequences to me..:good:, your Google knee pads must be pretty worn out by now huh?
Click to expand...
Click to collapse
Yes, I am sucking Google's **** because I am telling users who don't know better that Google specifically said not to do this. You got me. My secret is out.
myorks1127 said:
It doesn't wreak havok on my end so why would I care?
Click to expand...
Click to collapse
The problem is you don't know if it does. Because the GCM id changes, things like push messages from different apps will likely stop working (maybe permanently if they don't properly handle a changing id). You might not of noticed this much in the past because not a lot of apps utilized GCM push messages. However, more and more apps are using them today.
It's amazing that people will ignore advice from the people that have written the actual software. Just don't do it. The worst part about doing it is that you may not even know that something has messed up because its not obvious.
Thanks worked for me
Took me straight from 4,4 to 4,4.2 after 4 attempts
Hello everyone!
This is my first attempt at porting Android Wear to the Galaxy Gear! I am not an experienced dev and this was done fairly quickly using null_23 as a base and the Gear Live system dump. This is not at all ready and definitely not ready to flash. If you do decide to flash it, you risk bricking your device. That being said, I am requesting that a more experienced dev check over my work. If it seems in order, then it will be tested, until such a time, test at your own risk.
Link: http://d-h.st/go2
UPDATE: [ONLY FOR BRAVE PEOPLE INTERESTED IN TESTING]: Since I used null_ as the base, the addons are still available, but please do not flash any of them! And use the stock kernel for the time being!
UPDATE 2: It might be a good idea to try using the custom kernel we have available to us. If I can get an updater script from the gear live or other android wear device and look in to modifying the bootclasspath in the preexisting custom kernel that we have.
UPDATE 3: I have figured out how to modify the bootclasspath, will make the modification shortly. I just need an updater script for an android wear device and we may have a booting android wear port.
UPDATE 4: Link to Attempt 2 coming soon. This has a modified updater script that will hopefully set all permissions correctly. This may be all it needs to boot properly. If not, then I may still need some help getting the Gear Live Kernel to modify our kernel's bootclasspath. If anyone would like to flash this, same as before, I can't guarantee anything will work or that your device will work afterward.
Link: AWAttempt2.zip
UPDATE 5: added my slightly modified updater files from fomey's null_ ROM attached at the bottom. fomey, if we get this working, could you package it in to null_ as a second ROM option?
TekGadgt said:
Hello everyone!
This is my first attempt at porting Android Wear to the Galaxy Gear! I am not an experienced dev and this was done fairly quickly using null_23 as a base and the Gear Live system dump. This is not at all ready and definitely not ready to flash. If you do decide to flash it, you risk bricking your device. That being said, I am requesting that a more experienced dev check over my work. If it seems in order, then it will be tested, until such a time, test at your own risk.
Link: http://d-h.st/go2
Click to expand...
Click to collapse
Dude, you are fast!
I will not try it out right away because i just set up Null 23 and cloudnotifier so that to have notifications on the iPhone.
BTW, is there any chance that it will work with an iPhone. Ala Google Glass, that is.
TekGadgt said:
Hello everyone!
This is my first attempt at porting Android Wear to the Galaxy Gear! I am not an experienced dev and this was done fairly quickly using null_23 as a base and the Gear Live system dump. This is not at all ready and definitely not ready to flash. If you do decide to flash it, you risk bricking your device. That being said, I am requesting that a more experienced dev check over my work. If it seems in order, then it will be tested, until such a time, test at your own risk.
Link: http://d-h.st/go2
Click to expand...
Click to collapse
I just tried it out with the installation through TWRP, definitely not working as you said yet, just boot loops. I've been looking around in the zip and I see no problems that were noticeable. Hopefully this port of android wear can happen!
Sent from my SM-N900V using XDA Premium 4 mobile app
sandvich123127 said:
I just tried it out with the installation through TWRP, definitely not working as you said yet, just boot loops. I've been looking around in the zip and I see no problems that were noticeable. Hopefully this port of android wear can happen!
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you for testing so quickly! I'm glad it did not cause any serious issues to your device. I will do some talking with some devs I know and see what I can get worked out. Porting to the 1 will actually be easier than to the 2 or Neo, since there is an android base for the 1, unlike the 2 and Neo which are Tizen only.
Do you have a change log? If this is based on Null, it's still 4.2, while the wear launcher, if I remember correctly, requires a newer version of Android, probably 4.4. Just curious what your plans are to deal with that. Seems to me the only real options are either editing the wear app or porting 4.4 aosp and hoping the launcher works. Theoretically, the gear live dump could be ported but the major difference between cpus makes it a much more difficult task than people originally hoped. I think the best chance would be if a dev team (ie CM) were to pick up the protect, but there's the downside to a large bounty: there's a lot of people wanting to go it alone for the cash.
Sent from my VS985 4G using XDA Free mobile app
Trust me, I'm not doing this in an attempt to get the bounty. The money doesn't interest me at all. As far as the change log goes, this is the absolute first attempt, so there hasn't been anything changed yet. So again, this was a quick attempt in an effort to get the ball rolling and get the community involved in the development.
TekGadgt said:
Trust me, I'm not doing this in an attempt to get the bounty. The money doesn't interest me at all. As far as the change log goes, this is the absolute first attempt, so there hasn't been anything changed yet. So again, this was a quick attempt in an effort to get the ball rolling and get the community involved in the development.
Click to expand...
Click to collapse
No worries, I didn't think you were. You didn't have the typical billion "Donate please!" links that they would.
But what does first attempt mean? Just null kernel and modules with gear live system folder? I know a little about these things so I'd like to take a look, mostly out of curiosity, so I'd like to know what you've already done, preliminary as it is.
I agree though, we needed some kind of thread started and I agree that it's too early to put anything in the development forum.
Sent from my VS985 4G using XDA Free mobile app
Sent from my VS985 4G using XDA Free mobile app
JesusFreak316 said:
No worries, I didn't think you were. You didn't have the typical billion "Donate please!" links that they would.
But what does first attempt mean? Just null kernel and modules with gear live system folder? I know a little about these things so I'd like to take a look, mostly out of curiosity, so I'd like to know what you've already done, preliminary as it is.
I agree though, we needed some kind of thread started and I agree that it's too early to put anything in the development forum.
Sent from my VS985 4G using XDA Free mobile app
Sent from my VS985 4G using XDA Free mobile app
Click to expand...
Click to collapse
Not just a swapped out system folder. the base of the null_ system folder is still there. I only migrated the things necessary for a standard port. The only issue is that there is no ROM for the gear live yet, so a proper permissions section is not available for me to port from the updater script of the live to the updater script of the galaxy gear. I'm pretty convinced that if someone with a little more knowledge than myself edited the updater script permissions section to set the proper permissions for the new files, that this would at least boot.
Hi guys, I stumbled across this ebay listing item number 161368138405 . The seller claims he will update your gear to 4.4.2 for £25 + p & p , I have emailed the developer a link to the bounty thread, hopefully he may be able to help.
Sent from my SM-T320 using Tapatalk
Its some fake **** i think.
Would like to se a device info screen screenshot.
In the pictures he wirtes "This is not for the watch"
And later on "(1) Watch will become android 4,4,2"
Does he know what he is selling or not?
When he says "This is not for the watch", I think he means that you are not buying the watch in the picture. That is, you are not buying the physical watch, just the software upgrade.
I think it is high risk when you send your watch to him.
TekGadgt said:
...........
Click to expand...
Click to collapse
But for you rom is started?
4.2.2.
I wouldn't be surprised if he means 4.2.2.
He was pretty sure on his reply to me it was 4.4.2
RevengeDevTeam said:
But for you rom is started?
Click to expand...
Click to collapse
gingerdude said:
He was pretty sure on his reply to me it was 4.4.2
Click to expand...
Click to collapse
RevengeDevTeam: I have not necessarily classified this as a ROM, since it currently doesn't boot. That's why this is listed in the general thread. I am working on it, but there are no guarantees right now.
gingerdude: I'm pretty sure it's a scam. I wouldn't send him my watch if I were you.
gingerdude said:
Hi guys, I stumbled across this ebay listing item number 161368138405 . The seller claims he will update your gear to 4.4.2 for £25 + p & p , I have emailed the developer a link to the bounty thread, hopefully he may be able to help.
Sent from my SM-T320 using Tapatalk
Click to expand...
Click to collapse
Yeah, the listing was ended by the poster because there was an error in the listing. I bet he got scared cause people started to figure him out.
Oh that's a shame. I thought it might give you guys a head start
Will be watching with interest
Sent from my Nexus 5 using Tapatalk
richlum said:
When he says "This is not for the watch", I think he means that you are not buying the watch in the picture. That is, you are not buying the physical watch, just the software upgrade.
Click to expand...
Click to collapse
So I emailed the seller and he said it was Null Rom but it was 4.4...apparently he was mistaken haha
--------------------------------------------------------------------------------
From: shagmeimbj
To: lexirodster81
Subject: Details about item: shagmeimbj sent a message about Samsung gear watch SM- V700 unlocking service to android 4.4.2 #161368138405
Sent Date: Jul-16-14 06:37:52 PDT
Dear lexirodster81,
Can you maybe send a screenshot of the 4.4.2 in the settings menu...not saying I don't believe you haha these pics could be from Null rom though which is 4.2.
- shagmeimbj
This was his response...
"Dear shagmeimbj,
Hello
This service is to install the null rom what is 4.4.2
- lexirodster81
Click "respond" to reply through Messages, or go to your email to reply
Respond
So, according to drakon.us, Samsung has provided factory bootloader unlocker in the Samsung App store.
Search for "CROM Service", You can see the process here:
https://youtu.be/KTTgXqaP7Rk
I'm in preorder hell waiting for my gold S6E from Verizon so I can't verify independently. Is this something we can use?
Seems it's not showing up in the US Store. I'll see if anyone I know in that region can grab the app for us. Might be worth looking into.
So there was a link here to a place to find the app, then poof it magically disappeared. LOL gotta love how that happens. Regardless, the app that was linked did not work, it downloaded and installed fine, but when trying to open it, it just force closes.
androidoholic said:
So there was a link here to a place to find the app, then poof it magically disappeared. LOL gotta love how that happens. Regardless, the app that was linked did not work, it downloaded and installed fine, but when trying to open it, it just force closes.
Click to expand...
Click to collapse
fc here also
Sent from my SM-G925V using XDA Free mobile app
elliwigy said:
fc here also
Sent from my SM-G925V using XDA Free mobile app
Click to expand...
Click to collapse
Like I said, can't download it... If anyone could post it I'd be grateful. Wondering if it could be decompiled.
The.Jericho.Initiative said:
Like I said, can't download it... If anyone could post it I'd be grateful. Wondering if it could be decompiled.
Click to expand...
Click to collapse
I PM'd ya a link, it's in my google drive.
androidoholic said:
I PM'd ya a link, it's in my google drive. Since it was deleted, I am assuming the fine folks at xda for some reason don't want it shared.
Click to expand...
Click to collapse
Can you hook me up as well please
androidoholic said:
I PM'd ya a link, it's in my google drive. Since it was deleted, I am assuming the fine folks at xda for some reason don't want it shared.
Click to expand...
Click to collapse
No posts have been edited or removed from this thread. I believe the OP was talking about the link was deleted from the Youtube video link.
skylinegtr116 said:
Can you hook me up as well please
Click to expand...
Click to collapse
Skyline,
No need for a hook up.There's a thread in the hacker/dev forum with both versions of the apk that I've come across... They're available to download there.
http://forum.xda-developers.com/and...sung-factory-bootloader-unlocker-apk-t3086609
So is there a way to make this work .... FC for me after installing
Well like I said earlier, I'm trying to relearn all this after not using it for six or so years... My intuition tells me that this tool is invaluable, and we know it is functional as we've seen on a Galaxy Tab, it does install and load, but after the disclaimer, it FC's. This is telling me it is probable that the device is simply failing a version or class checker.
If that is true, depending on how this was created, the source can be altered to work with our devices. What's critical here is that these are official Samsung apps; we're not recreating the wheel here. What we're doing is looking at an unencrypted tool that was designed specifically for the purpose of unlocking our device. That's why I posted these to Hacking/Dev. While I am starting almost from square one, someone who is familiar with the environment and scripting language would be far ahead of me on the curve.
Will it work out of the box? Nope, but there is the potential it can be made to work.
The.Jericho.Initiative said:
Well like I said earlier, I'm trying to relearn all this after not using it for six or so years... My intuition tells me that this tool is invaluable, and we know it is functional as we've seen on a Galaxy Tab, it does install and load, but after the disclaimer, it FC's. This is telling me it is probable that the device is simply failing a version or class checker.
If that is true, depending on how this was created, the source can be altered to work with our devices. What's critical here is that these are official Samsung apps; we're not recreating the wheel here. What we're doing is looking at an unencrypted tool that was designed specifically for the purpose of unlocking our device. That's why I posted these to Hacking/Dev. While I am starting almost from square one, someone who is familiar with the environment and scripting language would be far ahead of me on the curve.
Will it work out of the box? Nope, but there is the potential it can be made to work.
Click to expand...
Click to collapse
Good lord I hope you or someone else gets it to work. There's hope!
Decompiled the apk and explored around a little, heres the strings.xml. Just wanting to share what it shows.
I really hope this goes somewhere. If this gets ported than I will be so thankful. If there is anything I can do to help I would but I have not much experience with programming
Title is misleading. I would edit it
Done.
Any updates on progress or is it completely dead?
By the looks of it you can get it to work you just need to obtain root first... Which means it serves no use seeing as the phones that have root are already bootloader unlocked
Wiseor said:
By the looks of it you can get it to work you just need to obtain root first... Which means it serves no use seeing as the phones that have root are already bootloader unlocked
Click to expand...
Click to collapse
But phones with locked BL's can be rooted given the right tool is created. And if it is then once rooted we can unlock our BL's and flash Roms like everyone else.
Sent from My Samsung Galaxy S6 "Pure" Black
Root doesn't guarantee any bootloader unlock. If that was true, then every phone with root would have an unlocked bootloader, which isn't the case.
Root would be nice, but without an unlocked bootloader I see many bricks happening from inexperienced users pushing things too far and not knowing a way out.
This is not your typical Nexus crowd in here.
This right here pisses me off
Sick of this damn call timer when trying to use other apps during a call.
Although that there isnt the main reason why I'm getting rid of this phone, I'll go ahead and add it to the ever growing list of reasons why I'm dumping it and getting a Nexus 6. Screw LG and their locked down pile of garbage. Sad thing is, it's so much wasted potential.
I love it when a new device comes out, and XDA becomes riddled with whiney posts about "this" or "that" which users say they 'hate' or 'can't stand'. Okay, so there's no publicized root method yet, deemed safe for consumerism, but once that's released I'm sure that every little quarky nuance will have a method to remove, hide, or alter in some way. The call timer has an option for hiding in the LG G3 via G3 Tweaksbox. With that example, I stand confident that this phone will have some type of similarities to, as I mentioned, "deal" with the things people complain about. Fact is, this phone is not impressively different from the G3, and there are no real profoundly engineered improvements made in the G4. You may ask, "Apex, y u bye did fone den?" Good question. My answer is this, I like LG's products and I appreciate the work developers are able to do, in order to make something good, great. So, in the meamtime, until root is available, you won't hear me having a hissy fit about (insert whatever) things. Samsung isn't for me, HTC is bunk, Motorola, well... been there, done that. I think most folks would respect those complaints be made on Reddit, or somewhere besides the place that developers afford us the grace of enjoying what they do for the community, free of charge.
Sent from my LG-H811 using XDA Free mobile app
painedglass said:
Although that there isnt the main reason why I'm getting rid of this phone, I'll go ahead and add it to the ever growing list of reasons why I'm dumping it and getting a Nexus 6. Screw LG and their locked down pile of garbage. Sad thing is, it's so much wasted potential.
Click to expand...
Click to collapse
locked down how? seems pretty rooted to me
lobo4806 said:
locked down how? seems pretty rooted to me
Click to expand...
Click to collapse
TWRP now too.. ROMS will be flowing soon.
Meh, I left the steaming pile of hardware failures that is a Nexus 6 for the G4. Volume rockers stopped working on the first one, new phone had screen issues, ya, the N6 isn't the greatest phone ever.
lobo4806 said:
locked down how? seems pretty rooted to me
Click to expand...
Click to collapse
It sure was when I posted, or did you not see the date of the Op? Yay, you got root on a phone that should have been unlocked in the first place.
painedglass said:
It sure was when I posted, or did you not see the date of the Op? Yay, you got root on a phone that should have been unlocked in the first place.
Click to expand...
Click to collapse
Angry much?
painedglass said:
It sure was when I posted, or did you not see the date of the Op? Yay, you got root on a phone that should have been unlocked in the first place.
Click to expand...
Click to collapse
Because clicking a check box to unlock the bootloader is so hard. Root takes time on all modern devices.
Hahaha... Now root being available, I've installed debloated ROM and 3000mah battery serves me really well. Not to mention boost in speed as well. On stock ROM, I was missing my nexus 5 so much.
I hope you stuck around for a little longer. Feels like beasty phone just got injected with the steroid.
Sent from my LG-H811 using XDA Free mobile app
Agreed....I was fed up with this phone.....root came and glory glory amen it's a better phone. Even with just a simple debloated ROM....can't wait till they really tweak the stock ROM like crazy. I probably won't go aosp....because of the camera app...whole reason I bought the phone...it deletes the side car RAW file in the default gallery aosp can't do that...neither can manual camera app or Fv5
---------- Post added at 06:22 PM ---------- Previous post was at 06:20 PM ----------
The thermal throttling and stuff needs some crazy tweaking...and a better kernel...my apps have to re draw too much...memory leak somewhere
Kingaries79 said:
This right here pisses me off
Sick of this damn call timer when trying to use other apps during a call.
Click to expand...
Click to collapse
I'm not sure if you figured it out, but since we have root, you can download app ops from play store. Go to the phone section and disable draw on top. It will stop the timer. And so far I have not noticed anything wrong.
Sent from my LG-H811 using Tapatalk
mawells787 said:
I'm not sure if you figured it out, but since we have root, you can download app ops from play store. Go to the phone section and disable draw on top. It will stop the timer. And so far I have not noticed anything wrong.
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
this is gold. i dont have a tmobile version, but thanks!!! ahh boo the side effect to this is that when someone calls, you dont see the answer/decline dialog and the notification bar doesnt work
ExTREmE99 said:
this is gold. i dont have a tmobile version, but thanks!!! ahh boo the side effect to this is that when someone calls, you dont see the answer/decline dialog and the notification bar doesnt work
Click to expand...
Click to collapse
I checked and I still get the dialog box, make sure the option is checked in the call settings. I'm not sure what you mean about the notification bar, but I can drag down and click on the call, which brings me back to the call.
Sent from my LG-H811 using Tapatalk
mawells787 said:
I'm not sure if you figured it out, but since we have root, you can download app ops from play store. Go to the phone section and disable draw on top. It will stop the timer. And so far I have not noticed anything wrong.
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
Thanks for this
Seems like a really silly reason to get rid of an otherwise awesome phone...
What's funny is that the current root methods as dangerous as they are. Are no more dangerous then when I had my Evo4g, and that team didn't have something like "OEM Unlock" to make it easier. No risk, no reward.
Not to mention that you can drag that icon anywhere on the screen so i dont see how it can be so intrucive during other app usage. Also why dont you just talk on the phone, your on a call, pay attention and stop playing with other apps, real easy
Sent from my LG-H811 using XDA Free mobile app
Apex said:
I love it when a new device comes out, and XDA becomes riddled with whiney posts about "this" or "that" which users say they 'hate' or 'can't stand'. Okay, so there's no publicized root method yet, deemed safe for consumerism, but once that's released I'm sure that every little quarky nuance will have a method to remove, hide, or alter in some way. The call timer has an option for hiding in the LG G3 via G3 Tweaksbox. With that example, I stand confident that this phone will have some type of similarities to, as I mentioned, "deal" with the things people complain about. Fact is, this phone is not impressively different from the G3, and there are no real profoundly engineered improvements made in the G4. You may ask, "Apex, y u bye did fone den?" Good question. My answer is this, I like LG's products and I appreciate the work developers are able to do, in order to make something good, great. So, in the meamtime, until root is available, you won't hear me having a hissy fit about (insert whatever) things. Samsung isn't for me, HTC is bunk, Motorola, well... been there, done that. I think most folks would respect those complaints be made on Reddit, or somewhere besides the place that developers afford us the grace of enjoying what they do for the community, free of charge.
Sent from my LG-H811 using XDA Free mobile app
Click to expand...
Click to collapse
your point is?
Would you be so kind as to elaborate on
XDA becomes riddled with whiney posts
Click to expand...
Click to collapse