Wow. It's been a long time since I made anything useful. Not being able to use NFC with the screen off has always been a pet peeve of mine with my Nexus, so I figured I'd fix it
This is a modified Nfc.apk, which is the system NFC service that runs at boot. It allows you to scan NFC tags either with the screen totally off, or with the screen on but still at the lockscreen. You get to choose which one you want to flash. Just download one of the zips below, and flash it via recovery (tested with ClockworkMod). To restore to stock, just pick the stock version.
The screen off version means you can ALWAYS scan an NFC tag. Don't have to turn the screen on or anything. Just touch the phone to the tag.
The lockscreen version lets you scan a tag whenever the screen is on, but it doesn't have to be unlocked. You can't scan while the screen is off, but you can just touch the power button to get to the lockscreen and then scan. If you have a passcode, no need to unlock your phone to scan a tag.
This has been compiled against CyanogenMod and tested on my own self-built tree based off CyanogenMod source. There is nothing here that should be specific to that ROM.
Devices
Sprint Galaxy Nexus (toroplus)
Fully working on CyanogenMod based ROMs
Fully functional on most AOKP ROMs. Throws random errors on some, but everything still works.
Not functional on some stock ROMs
GSM Galaxy Nexus (maguro)
Fully working on CyanogenMod based ROMs
Fully functional on most AOKP ROMs. Throws random errors on some, but everything still works.
Not functional on some stock ROMs
Verizon Galaxy Nexus (toro)
Untested as far as I know. If you test it let me know
Should be similar to other Galaxy Nexus SKUs
HTC One X
The user StephanSch has created a version for the One X. Get it in this post.
Only screen off seems to work, not lockscreen.
Don't know if this is for the Qualcomm S4 based One X or the Tegra 3 base. Not sure about carrier versions either.
Samsung Galaxy SIII
The user mayhemer has created a version for the SIII. Get it in this post.
I'm not aware of which version of the SIII this is for, now which ROM. As soon as I have info, I'll update it here.
Nexus S
Reported working from at least one user. Don't know GSM or CDMA version, nor which ROM.
Probably working on any CM9 build for either SKU, and possibly stock or AOKP.
It probably will not work on any manufacturer based skins on any other device.
If you try it on any other device, please let me know how it goes! I'll update the OP with your results!
Also of note, I do not know if this will allow you to use Wallet any differently than you can right now. I don't have any way to test it, and don't personally use Wallet. If you do, let me know whether it works or not so I can update this post!
Liability Disclaimer: As always, I hereby absolve myself of responsibility for any damage you cause to your phone by flashing this. There is inherent risk in modding your device, and by flashing anything in this thread you are taking that risk into your own hands. If something goes wrong, I will try and help, but I am not God.
Source Code Disclaimer: The only code modified here was given under the Apache v2 license. That means that I am not required to release source for this. It is an incredibly simple mod at this point, but I plan on taking it into the next level and creating a patch that makes this an option in settings, rather than a zip you have to flash. I will release source with this, but I want to wait until I clean it up and submit it to the CyanogenMod Gerrit as a full feature, rather than a cheap hack! Sorry if that disappoints anyone, I just wanted to get this out ASAP.
In the meantime, I explain what I'm doing in this post. That should be enough info if you're compiling from source, and might be enough if you are using a Smali edit. If you're critically concerned about it, shoot me a PM or an email and I'll try and help more.
How things stand for Jellybean:
I put this on hold for a while. The further I got into making this a toggleable option in settings, the deeper things ran into the system code. With the big change to Jellybean around the corner, I want to wait until Jellybean becomes the main CM branch so I can avoid the breaks that all the code churn will cause. I'm not done with this, but there's no point in putting the work in to make it fully functional when CM10 is around the corner to break it all. I'll get on it as soon as CM10 becomes closer to release. Before the code freeze for CM10.
In the mean time, @PHtQuE got ahold of me on Twitter and I told him what was happening. I gave him a couple pointers and he got it compiling on Jellybean at the same level it is right now on ICS. I may be wrong, but I believe this is his post right here. Regardless, this is a working screenoff version for JB.
Reserved, just in case...
That will definetly come in good use. Thanks
Sent From My Old Epic 4g via XDA Premium
This is nice! Thanks! One thing that I thought would be useful is to have a notification pull down toggle for NFC. so you think that's possible?
Sent from my Galaxy Nexus using XDA
This is handy thanks dog lol.
Sent from my Galaxy Nexus
Hmmm... I've always been able to use Google wallet with the screen off. I'm not sure about any other nfc use though.
Awesome man, thanks. Just bought some NFC stickers to mess around with and this was my biggest problem. Really appreciate it.
Nice!! So the screen of one is only if the screen is off without a lockscreen?
davidrules7778 said:
Nice!! So the screen of one is only if the screen is off without a lockscreen?
Click to expand...
Click to collapse
No. Sorry, I'll update the OP to be a little more clear.
Screen off means you can ALWAYS scan an NFC tag. Don't have to turn the screen on or anything. Just touch the phone to the tag.
The lockscreen version lets you scan a tag whenever the screen is on, but it doesn't have to be unlocked. You can't scan while the screen is off, but you can just touch the power button to get to the lockscreen and then scan. If you have a passcode, no need to unlock your phone to scan a tag.
pastert33 said:
This is nice! Thanks! One thing that I thought would be useful is to have a notification pull down toggle for NFC. so you think that's possible?
Click to expand...
Click to collapse
It's definitely possible. I'm working on getting the option in Settings now, and should have it working by the end of the day. Once there's an option in Settings, it should be super simple to add a notification bar toggle option as well. Haven't messed with that part before, but it's not too dissimilar from WiFi toggling, so I've got code to look at.
I was hoping to get the settings mod done in time to submit it to CM before they started the code freeze for CM9. Well, they went into code freeze this morning so I missed that. I'll still get it submitted ASAP, but don't expect to see it in the initial CM9 official build unless you use the nightlies. I'll of course update everything once I submit the patch and if it gets accepted.
Geniusdog254 said:
No. Sorry, I'll update the OP to be a little more clear.
Screen off means you can ALWAYS scan an NFC tag. Don't have to turn the screen on or anything. Just touch the phone to the tag.
The lockscreen version lets you scan a tag whenever the screen is on, but it doesn't have to be unlocked. You can't scan while the screen is off, but you can just touch the power button to get to the lockscreen and then scan. If you have a passcode, no need to unlock your phone to scan a tag.
It's definitely possible. I'm working on getting the option in Settings now, and should have it working by the end of the day. Once there's an option in Settings, it should be super simple to add a notification bar toggle option as well. Haven't messed with that part before, but it's not too dissimilar from WiFi toggling, so I've got code to look at.
I was hoping to get the settings mod done in time to submit it to CM before they started the code freeze for CM9. Well, they went into code freeze this morning so I missed that. I'll still get it submitted ASAP, but don't expect to see it in the initial CM9 official build unless you use the nightlies. I'll of course update everything once I submit the patch and if it gets accepted.
Click to expand...
Click to collapse
Darn it LOL i would love to have one that works with both
Great work tho, i will probaly get the lockscreen one
Any thoughts as to if this will work on the One X? I'm backing up my stock NFC.apk anyhow and am going to test it, but I thought I'd ask in advance.
agentdr8 said:
Any thoughts as to if this will work on the One X? I'm backing up my stock NFC.apk anyhow and am going to test it, but I thought I'd ask in advance.
Click to expand...
Click to collapse
In theory, it should work on any 4.0.4 base ROM, on any NFC device. No guarantees though
This is just what I've been looking for (FOR AGES) I know that it doesn't come like this from stock, due to the potential security risks, but sod it! Lol, i love it.
Thanks for the fantastic work
Rumble
Sent from my Galaxy Nexus using xda premium
im curious as to the effect on battery life. how noticeable is the difference?
I think that this is a great feature. But I thought that the reason
the NFC only worked with the screen on and phone unlocked was
a security reason. Meaning someone could not just walk up to
you and scan your phone without you knowing. you would have to
have the phone on for anything to work. I think that the settings
idea is great that way if you want to open then you can have it open
if you want it closed then you can keep it like stock. Great work. Worked
good on my GNexus (Sprint).
zcmack said:
im curious as to the effect on battery life. how noticeable is the difference?
Click to expand...
Click to collapse
I can't speak for the battery life, as my phone is plugged in either for tethering or testing code all day. Shouldn't be too noticeable.
Smurph82 said:
I think that this is a great feature. But I thought that the reason
the NFC only worked with the screen on and phone unlocked was
a security reason. Meaning someone could not just walk up to
you and scan your phone without you knowing. you would have to
have the phone on for anything to work. I think that the settings
idea is great that way if you want to open then you can have it open
if you want it closed then you can keep it like stock. Great work. Worked
good on my GNexus (Sprint).
Click to expand...
Click to collapse
Security is exactly the reason it doesn't come like this by default. It's also why I made two versions. If you're worried about security, then flash the lockscreen version and you have to turn the phone on to be able to scan.
Currently, there is no way that I know of to get anything malicious by scanning against someone's will. It doesn't just offer up credit card numbers when you scan it. If you have NFC Task manager on your phone, someone could scan it and make it start an app you have installed or turn off wifi or something mundane like that, but that's about it. Plus they'd have to get within ~5" of your pocket
Geniusdog254 said:
In theory, it should work on any 4.0.4 base ROM, on any NFC device. No guarantees though
Click to expand...
Click to collapse
It would appear that the One X's Nfc.apk has different hardware support. When I flashed your zip, NFC ReTag couldn't detect NFC hardware any more. And the option for NFC disappeared in Settings. Nothing a restore of the original apk couldn't fix, but it's unfortunate it didn't work.
Any chance you'd be willing to share what edits you made? If it's smali, I can probably tweak the One X's apk to be similar.
agentdr8 said:
It would appear that the One X's Nfc.apk has different hardware support. When I flashed your zip, NFC ReTag couldn't detect NFC hardware any more. And the option for NFC disappeared in Settings. Nothing a restore of the original apk couldn't fix, but it's unfortunate it didn't work.
Any chance you'd be willing to share what edits you made? If it's smali, I can probably tweak the One X's apk to be similar.
Click to expand...
Click to collapse
It's actually compiled from source. I've never messed with Smali, so I don't know how useful this will be. The easiest way is to tweak a variable called POLLING_MODE in the NfcService class. There are a couple different settings. 3 is the default, 2 works on lockscreen or unlocked, and 1 works with the screen off, at the lockscreen, or unlocked.
I don't think Smali keeps variable or function names, so that might be of no use at all.. The other method, in a function called applyRouting() there are a couple if/else statements that check if the current state matches POLLING_MODE or not. If you take those out, then it should also work although for some reason that only seems to enable it to the lockscreen level.
You should be able to see a copy of the file here, if that helps.
Geniusdog254 said:
Security is exactly the reason it doesn't come like this by default. It's also why I made two versions. If you're worried about security, then flash the lockscreen version and you have to turn the phone on to be able to scan.
Currently, there is no way that I know of to get anything malicious by scanning against someone's will. It doesn't just offer up credit card numbers when you scan it. If you have NFC Task manager on your phone, someone could scan it and make it start an app you have installed or turn off wifi or something mundane like that, but that's about it. Plus they'd have to get within ~5" of your pocket
Click to expand...
Click to collapse
I did not mean anything by my comment, I think that having to turn the phone
on to use it is a bit much. I like that you have the ability to run it form the lock
screen. I understand that right now you really cannot do much with the NFC,
hacker wise, other than changing settings you are not stealing information by
scanning. But being that NFC is still new(ish) I also feel that all the security
holes have not been discovered. I just wanted people to consider every angle.
I still think that you have created a great feature.
I love what I'm seeing here, well done! Can anyone confirm if this breaks Google Wallet functionality?
Related
Full credit goes to Ssserpentine, SpaceMoose, and OldMacnut for their work on their united efforts to port Honeycomb to our tablets! It seems they are no longer working on it so I decided to create this thread and see what we all could to do together to improve what they have given us!
The point of this thread is to find ways to gather anyone with knowledge on developing, even if its just the "lowly 7-Zippers" like me, to see how we can remove minor bugs and small issues from the ROM. I know Oldmacnut was going to pick it up, but he has a lot on his plate right now and he has been in pain and is more interested in finishing the CM7 Port instead. I respect his decision, but so many people want honeycomb working on our tabs. So I am turning to the dev community here to see if we can group together and fix things in this rom together. If we cant solve the major bugs, lets address all the little things, cuz the little things add up.
Spacemoose made a list of suggestions from users earlier on how to solve minor issues, and little workarounds, but I would like to see if there is a way to roll up those fixes into one full updated ROM flashable through a zip/odin/heimdall file, and see if we can come up with more. You can see this post here, but I have added them to the second post as well in a more organized form.
Some Useful Links as Well:
SpaceMoose's Github
6-19-11 Apps Confirmed Working on [CDMA] / [GSM] Honeycomb Alpha 2.5
Currently Known Bugs:
CDMA
A) Red Border Around Screen at Random Times
B) Constant Gallery Force Close
C) Stock Launcher hangs for many seconds at a time randomly
D) SD Card Does Not Mount
E) Youtube app does not work
F) Orientation Sensor is not functional
G) Honeycomb thinks Device Keyboard is enabled by default
H) When pressing Quick Settings, an image that is semi transparent that is supposed to cover the entire screen isnt scaled properly
I) HQ Youtube does not work (LQ does on the mobile site)
J) Quick Settings Shortcut on Bottom Right Side (Wi-Fi Toggle, Brightness Slider, etc) appears for a second but disappears afterwards.
K) Flash Player is not Fully Functional
GSM - Please Submit or confirm if the above bugs are the same and/or you have different ones!
Red - Signifies an issue that is unaddressed or has not been solved yet.
Orange - Signifies a Temporary Fix or Workaround is mentioned in the post I linked to.
Blue - Will signify a temporary fix or a work around that we have been able to include in a flashable file
Green - Will signify a bug that has been completely fixed in a flashable file.
------------------------------------------
Lets put our minds together and see what we can do guys! Btw this was inspired by Rodderik's thread [SPRINT][CDMA]Galaxy Tab (SPH-P100) Mega Development Starter Thread (CWM, EF17 TAR), so if youre interested in this, you might like his thread too!
Current Workarounds/Temporary Fixes:
Letters correspond to the bugs listed in the OP.
A)
Ssserpentine:
1) Open up Dev Tools
2) Go to Development Settings
3) StrictMode Visual Indicator - turn it off
4) back out of app and now open it again.
5) If this doesn't get rid of MOST of the red borders, REBOOT and open app again.
Click to expand...
Click to collapse
B)
anfalas:
"Get Gallery3D to play nice by going into settings, applications then 'Clear Data' - works great, can change wallpaper etc. Only downside is it has to be done each reboot....."
Click to expand...
Click to collapse
C)
Ssserpentine:
“WANT IMPROVED UI, LESS RED BORDERS, LESS FC'S AND SCROLLING AND SOFT KEYS THAT PLAY NICER? Try adw launcher. for some reason just having it installed helps just as much as using it.”
Click to expand...
Click to collapse
D)
mattman83:
"to mount UMS if you have no external SD then use the below line. Same changes as above... echo /dev/block/mmcblk0p1 > /sys/devices/platform/s3c-usbgadget/gadget/lun1/file"
Click to expand...
Click to collapse
or
corodius:
"if you have an external sd, by extending the commands to: su mount -t vfat /dev/block/mmcblk0p1 /mnt/sdcard/ mount -t vfat /dev/block/mmcblk1p1 /mnt/sdcard/external_sd/ This will mount the cards the way they are originally mounted in the samsung/overcome roms."
Click to expand...
Click to collapse
E)
Use m.youtube.com to play LQ videos
Click to expand...
Click to collapse
F)
ztag100:
"If you download barcontrol from the market, you can set it so that a notification links to the rotation app, thus when the notification is clicked it will change the orientation."
Click to expand...
Click to collapse
G)
"one way to load keyboards On the language/keyboard settings page, turn physical keyboard to "no" or "off" or something like that. Now when on a text field, you should see a small keyboard tray in bottom right corner.."
Click to expand...
Click to collapse
H) ---
I) ---
J) ---
K) ---
----------------------------
Submit a New Bug or Fix:
Please submit bugs using the color coded system I explained in the OP. If you are submitting information on solving a bug please address the bug by the corresponding letter so that we can stay organized and know what youre talking about. If you have a new bug please check the OP to make sure I havent listed it, then post it on here and dont worry about the letter, I will alphabetize them. Of course I will credit you in the OP for any fixes or workarounds you may find! Good luck to us all!
Reserved as well!
Yes, please
I would really love a Honeycomb ROM for the Galaxy Tab. There are many reasons why I want to put Honeycomb onto the original Galaxy Tab.
Just see the difference for yourself: Blank space, single pane, one-category-at-a-time menus in Gingerbread
VS.
Less blank space, concise, dual pane interfaces in Honeycomb.
Gingerbread apps are just designed for smaller smartphone screens, so they look too big and spaced-out on the 7-inch Galaxy Tab for my taste. I would really love to see some tablet-optimized apps on the Galaxy Tab!
-------------------------
And yes, I respect the developers and appreciate them so much for the time they put into making custom roms a reality for us!
Please make the thread for GSM also.
TheATHEiST said:
Please make the thread for GSM also.
Click to expand...
Click to collapse
Are the bugs the same? Or are there others that I havent mentioned? I will try to make a section for both tabs if theres different bugs in each one.
Why no mention of ssserpentine?
In op or thread tittle?
He worked on the GSM version.
Moose did the major part of the port and the cdma version.
That other person stumbled, or so he claims, on a audio fix. Never saw a release of this apparent audio fix.
Wonder how many donations he got on open thread with no release posted.
Hmm.
Makes ya wonder why that thread is even there.
Dole out the credits properly.
Just know it needed to be said, and go ahead and get mad. Truth hurts.
alot of angry responces coming, maybe, but dare ya to point out a single lie in this post. Even an exaggeration.
Moose did hc for MONTHS and noone offered any valid help, except ssserpentine, why do you think anyone is gonna get off their but now?
Why don't you, punkrock?
Cause I know how utterly hopeless this task is.
Why don't you all just wait for the leak of the next os?
That so much closer than some random Joe, or Joe's on xda getting hc ported at this point .
is the dead horse braised yet?
Still, hope is eternal, I suppose
PunkRock said:
Why no mention of ssserpentine?
In op or thread tittle?
He worked on the GSM version.
Moose did the major part of the port and the cdma version.
That other person stumbled, or so he claims, on a audio fix. Never saw a release of this apparent audio fix.
Wonder how many donations he got on open thread with no release posted.
Hmm.
Makes ya wonder why that thread is even there.
Dole out the credits properly.
Just know it needed to be said, and go ahead and get mad. Truth hurts.
alot of angry responces coming, maybe, but dare ya to point out a single lie in this post. Even an exaggeration.
Moose did hc for MONTHS and noone offered any valid help, except ssserpentine, why do you think anyone is gonna get off their but now?
Why don't you, punkrock?
Cause I know how utterly hopeless this task is.
Why don't you all just wait for the leak of the next os?
That so much closer than some random Joe, or Joe's on xda getting hc ported at this point .
is the dead horse braised yet?
Click to expand...
Click to collapse
Easy man, in my frenzy of trying to organize the thread, I forgot to credit Ssserpentine in the OP, youre right he did contribute a lot, no need to be rash, I will update it right now.
EDIT: btw oldmacnut did make an audio fix, im running his rom right now, I downloaded it when he had it posted before he took it down, and Im sure some of the bugs I mentioned are fixable on the rom level rather than through adb. My goal wasnt to debug the rom completely, it was to incorporate all the existing bug fixes and workarounds into one rom, while possibly solving others. Also the GSM devs are aplenty here, while we barely have any CDMA, Im sure we have enough talent to make it better than what it is. It might not be flawless, but Im sure we can squeeze more functionality out of it.
Its weird,
Honeycomb is more or less froyo based, obviously as we had hc long before gb, so at the time when I started getting into this whole dev thing hc/froyo seemed just different to me.
But after working on the abortion called gingerbread, and working onbthe kernel stuff, froyo to me, is starting to look like a much more viable and dev friendly option.
Alot if the work Dan did in hc was from scratch, or from the sdk, etc. The audio fix I did was from both.
The big issue on getting hc up and going into a usuable rom is source, we really really need that source for hc. Otherwise, its going to be a long drawn out road of trial and error building with alot of these issues never really getting fixed.
Truth is,
No device with our hardware exists with hc, so no drivers that we need.
We need Google to release the hc source.
I liked hc on my tab just like y'all, but.......I know its just a novel weekend fun toy till we get better resources.
Sent from my SCH-I800 using xda premium
oldmacnut said:
Its weird,
Honeycomb is more or less froyo based, obviously as we had hc long before gb, so at the time when I started getting into this whole dev thing hc/froyo seemed just different to me.
But after working on the abortion called gingerbread, and working onbthe kernel stuff, froyo to me, is starting to look like a much more viable and dev friendly option.
Alot if the work Dan did in hc was from scratch, or from the sdk, etc. The audio fix I did was from both.
The big issue on getting hc up and going into a usuable rom is source, we really really need that source for hc. Otherwise, its going to be a long drawn out road of trial and error building with alot of these issues never really getting fixed.
Truth is,
No device with our hardware exists with hc, so no drivers that we need.
We need Google to release the hc source.
I liked hc on my tab just like y'all, but.......I know its just a novel weekend fun toy till we get better resources.
Sent from my SCH-I800 using xda premium
Click to expand...
Click to collapse
Yeah I know, the lack of source sucks along with the fact we dont have drivers. I dont think we'll have everything working anytime soon at all, if ever even, but I think some of the minor annoyances like the disappearing quick settings toggle, sdcard mounting issues, and graphical errors can be solved without that kind of stuff. Me personally, Id just like HQ Video Playback and 3D Graphics working a hundred percent along with orientation, but as you said no drivers so idk how easy that'd be. Still, Im sure we could solve some of these minor issues. I keep browsing over the Nook Color Forums trying to find hints to solving some of these things
GSM Tab here I'll flash the old 2.5 alpha release and confirm these bugs, see what else I can do.
Sent from my GT-P1000 using xda premium
BulletproofIdeal said:
GSM Tab here I'll flash the old 2.5 alpha release and confirm these bugs, see what else I can do.
Sent from my GT-P1000 using xda premium
Click to expand...
Click to collapse
Nice to see something happening here. I love my Tab but would like some advancements in OS to address specific issues. I am very new to the dev side of the Android OS but would like to get involved.
--Mike
What blows my mind is that they have created an almost perfect HC port for the $150.00 walmart sold viewsonic g-tablet by means of the flashback roms so why is it so hard to get HC working on our tabs? And why can't someone just dump the Rom from the gtab10.1 and use that as a starting point?
On a different note, the alpha 2.5 HC Rom for gsm, the sd cards will not mount no matter what, I've tried The terminal and the mount instructions many times all I am able to do is get the tab to recognize my external sd as the internal sd, and if you try to go to settings applications and clear data for the gallery you get a force close as soon as you tap manage applications
Sent From Githrog's Tab
Ok done some immediate testing on my GSM Tab for some of the known issues
A) Red Border Around Screen at Random Times
Confirmed
Solution: is the same as the CDMA
B) Constant Gallery Force Close
Confirmed
Solution: Cannot be fixed through Setting, crashes as soon as you try to Manage Applications
C) Stock Launcher hangs for many seconds at a time randomly
Not really was slow on boot but no major problems
D) SD Card Does Not Mount
Confirmed
Solution: Haven't tested fix yet
E) Youtube app does not work
Confirmed
Solution: Confirmed
F) Orientation Sensor is not functional
Confirmed
Solution: "Rotating Screen" flips screen incorrectly so that capacitive buttons are on the top of the device
G) Honeycomb thinks Device Keyboard is enabled by default
Confirmed
Solution: Must be set on each boot
H) When pressing Quick Settings, an image that is semi transparent that is supposed to cover the entire screen isnt scaled properly
Confirmed
I) HQ Youtube does not work (LQ does on the mobile site)
Confirmed
J) Quick Settings Shortcut on Bottom Right Side (Wi-Fi Toggle, Brightness Slider, etc) appears for a second but disappears afterwards.
The widget that display battery level, time, etc stays active however no settings are located underneath it. While this menu is expanded a press on the bottom bar will cause the settings to briefly appear but then the whole menu will close
K) Flash Player is not Fully Functional
Not tested
"New" GSM bugs
1. Wi-fi settings are not saved on restart
2. Manage Applications and Running Services menu causes force close of settings
3. Small thing but Tab's first start had language set to Spanish (Not sure if it was spanish but it certainly was not English)
And as always 3G does not work (tried APN settings but it wouldn't let me save)
Alright I'm back to MIUI until I can find some more time on my hands
---------- Post added at 02:51 PM ---------- Previous post was at 02:31 PM ----------
Githrog said:
What blows my mind is that they have created an almost perfect HC port for the $150.00 walmart sold viewsonic g-tablet by means of the flashback roms so why is it so hard to get HC working on our tabs? And why can't someone just dump the Rom from the gtab10.1 and use that as a starting point?
Click to expand...
Click to collapse
If it were that simple I'm sure someone would have thought of that To be honest I think the problem is that the Tab is an extremely fractured device; it was really the first Android tablet to directly compete with the iPad, so it was spread as wide as possible. That's great for Samsung who got a pretty large base of customer but sucks for devs because the GSM and CDMA are 2 very different devices not to mention the P-1000N. When I got my Tab last month the first thing I noticed in this forum was the fragmentation between the different versions of Tabs. More profoundly this means that the developers are split apart, usually when one dev makes a break through everyone else can take advantage of it (i.e. the amazing Voodoo Sound/Color hacks) but not here. I feel like everyone is by themselves and I truly feel bad for the developers because they must make their own breakthroughs on top of dealing with complaints from Tab users with other versions that they want this awesome thing on their Tab. As if its no big deal to go and buy a $450 device to develop something as a hobby and then release it for free for people on the internet after already buying nearly the exact same device.
Sadly I think the Tab is a perfect storm working against modifying it in any ground breaking ways. Don't get me wrong I love my Tab and will try to help getting Honeycomb running but I almost feel like it would just be easier to wait for Ice Cream Sandwhich. /rant
Guys, there is no reason to develop honeycomb, it is inposible to make fully functional honeycomb rom, wait a month or less for ICS, read this (quote from android police posted today):
Honeycomb is closed source. Nobody can make a tablet without Google's blessing. The reason given is that Honeycomb was rushed out the door, and the code isn't good enough for an open source release. They're right you know, setting the emulator to anything smaller than a tablet will result in about a million force closes. Honeycomb just isn't as supportive of hardware as Gingerbread was. To save developers the headache of supporting a platform that wasn't ready, Android's openness got shelved.
Luckily this is going to change. The big cheese said so himself on the Official Android Developers blog, "This temporary delay does not represent a change in strategy. We remain firmly committed to providing Android as an open source platform across many device types." Source code is coming back. This will make the modding community's life much easier. Cyanogenmod 8 (I got excited just typing that) and Ice Cream Sandwich will be able to get hacked onto just about anything.
Click to expand...
Click to collapse
CROrION said:
Guys, there is no reason to develop honeycomb, it is inposible to make fully functional honeycomb rom, wait a month or less for ICS, read this (quote from android police posted today):
Click to expand...
Click to collapse
I just wanted an excuse to try out Honeycomb
BulletproofIdeal said:
Ok done some immediate testing on my GSM Tab for some of the known issues
A) Red Border Around Screen at Random Times
Confirmed
Solution: is the same as the CDMA
B) Constant Gallery Force Close
Confirmed
Solution: Cannot be fixed through Setting, crashes as soon as you try to Manage Applications
C) Stock Launcher hangs for many seconds at a time randomly
Not really was slow on boot but no major problems
D) SD Card Does Not Mount
Confirmed
Solution: Haven't tested fix yet
E) Youtube app does not work
Confirmed
Solution: Confirmed
F) Orientation Sensor is not functional
Confirmed
Solution: "Rotating Screen" flips screen incorrectly so that capacitive buttons are on the top of the device
G) Honeycomb thinks Device Keyboard is enabled by default
Confirmed
Solution: Must be set on each boot
H) When pressing Quick Settings, an image that is semi transparent that is supposed to cover the entire screen isnt scaled properly
Confirmed
I) HQ Youtube does not work (LQ does on the mobile site)
Confirmed
J) Quick Settings Shortcut on Bottom Right Side (Wi-Fi Toggle, Brightness Slider, etc) appears for a second but disappears afterwards.
The widget that display battery level, time, etc stays active however no settings are located underneath it. While this menu is expanded a press on the bottom bar will cause the settings to briefly appear but then the whole menu will close
K) Flash Player is not Fully Functional
Not tested
"New" GSM bugs
1. Wi-fi settings are not saved on restart
2. Manage Applications and Running Services menu causes force close of settings
3. Small thing but Tab's first start had language set to Spanish (Not sure if it was spanish but it certainly was not English)
And as always 3G does not work (tried APN settings but it wouldn't let me save)
Alright I'm back to MIUI until I can find some more time on my hands
---------- Post added at 02:51 PM ---------- Previous post was at 02:31 PM ----------
If it were that simple I'm sure someone would have thought of that To be honest I think the problem is that the Tab is an extremely fractured device; it was really the first Android tablet to directly compete with the iPad, so it was spread as wide as possible. That's great for Samsung who got a pretty large base of customer but sucks for devs because the GSM and CDMA are 2 very different devices not to mention the P-1000N. When I got my Tab last month the first thing I noticed in this forum was the fragmentation between the different versions of Tabs. More profoundly this means that the developers are split apart, usually when one dev makes a break through everyone else can take advantage of it (i.e. the amazing Voodoo Sound/Color hacks) but not here. I feel like everyone is by themselves and I truly feel bad for the developers because they must make their own breakthroughs on top of dealing with complaints from Tab users with other versions that they want this awesome thing on their Tab. As if its no big deal to go and buy a $450 device to develop something as a hobby and then release it for free for people on the internet after already buying nearly the exact same device.
Sadly I think the Tab is a perfect storm working against modifying it in any ground breaking ways. Don't get me wrong I love my Tab and will try to help getting Honeycomb running but I almost feel like it would just be easier to wait for Ice Cream Sandwhich. /rant
Click to expand...
Click to collapse
Wow now that is the kinda posts i like seeing on here! I will try to update the OP tonight with this info! Thanks so much! Definitely echo your sentiments about the fractured and fragmented development we have going on here, it really sucks =/
Ive found out that replacing the existing Gallery with Gallery3D should fix the FC that keeps popping up.
I think Ive found a working Youtube App (in LQ).
Ive also found a hint towards solving the sdcard mounting issue. Its not the vold.fstab its something either in the framework or ramdisk within the kernel, according to the Nook Color Forums.
This thread is interesting: http://forum.xda-developers.com/showthread.php?t=1062626 , actually the entire nook color forum is interesting for finding fixes.
Also changing the dalvik_heapsize to a certain value is supposed to increase app compatibility. Before I update the OP with some of these things, I wanna do a little more testing and see what I can come up with.
Sorry to bother for help,
Sorry to bother you guys for help, but I've been trying to install Oldmacnut's updated of Spacemoose's CDMA Honeycomb (2.5.1) for hours now, with no success.
I used Rodderick's awesome stock rom/kernel and got into clockworkmod (using 4.0.1.5 or 3.0.0.0), installed the zip from there, then rebooted the phone, but I would either 1) be stuck at logo for 10+ minutes 2) see the Sprint startup video loop over and over again, or 3) get stuck on a turned on, but black screen.
How did you guys install Honeycomb on your CDMA tab? Am I doing something wrong? Should I use Spacemoose's 2.5 rom instead of Oldmacnut's?
EDIT: NEVER MIND, IT BOOTED INTO HONEYCOMB. I am in a foreign language, haha, I'm guessing Portuguese?
EDIT EDIT: Google Translate detects the language as Catalan. Haha!
iliveinabucket said:
EDIT EDIT: Google Translate detects the language as Catalan. Haha!
Click to expand...
Click to collapse
Hehe that happened to me as well
First Impressions and problems encountered
HOLY SHOOT THIS IS QUITE FAST!
Considering there is no graphics acceleration support, Honeycomb runs much faster than I anticipated. SD card support is fantastic, and so is hearing sound! (I love you OMC) The UI is awetastic and the standard web browser is blazing fast. Scrolling in web pages is faster on Honeycomb than on Gingerbread stock.
The jittery touch screen bug I have is still there, unfortunately. Damn bug drives me crazy sometimes. I'm sure somebody has this problem that many of us have but have not found a fix to: http://forum.xda-developers.com/showthread.php?t=970965
Basically, when I hold down my finger to scroll on white or light-color backgrounds, the screen shakes back and forth in a spastic, noticeable way, especially when I hold it in place. This happens on every single rom I've been on, froyo, GB, CM7, and now Honeycomb. Has anyone found a fix for that yet?
Anyways, I think all the known Honeycomb bugs are true to me too. Youtube force closes on me, GPS doesn't work, auto-orientation doesn't work. Strangely enough, Quick Settings doesn't work for me. Anyone encounter that?
In the Samsung Galaxy S3 Stock ROM NFC does not work when screen is off or locked. With this mod NFC also works when screen is locked or off.
There are two versions. The first just enables NFC, when screen is on, but it also worked when it is locked. Also with a PIN or Password-Lock everything is fine. But it disables NFC when the SGS3 is in standby and the screen is off.
The second version let NFC active all the time, even when the SGS3 is in standby and the screen is off.
Nothing else is changed in the behaviour of the NFC.
There are also two zips to go back to stock Nfc, one is odexed and one deodexed.
All ZIPs have to be flashed with CWM. You should wipe Dalvik cache after flashing.
This mod works for at least for I747UCALEM. This mod does not work with LFB now. It also doesn't work for CM9 or CM10. I will provide an updated Mod in the middle of August because I am at vacation now.
Please give me feedback, because I do not own this device and I cannot test the Mod on it! I just ported my MOD for the international S3 to the I747.
Disclaimer: As always, I hereby absolve myself of responsibility for any damage you cause to your phone by flashing this. There is inherent risk in modding your device, and by flashing anything in this thread you are taking that risk into your own hands. If something goes wrong, I will try and help. You should always make a Nandroid Backup before flashing.
To ROM Devs: You are more than welcome to use this in your ROMs! Just shoot me a little bit of credit in your release post!
Thank you: Geniusdog254 for the idea and the infos in your thread.
Here ist the link to the thread for the international S3 version:
http://forum.xda-developers.com/showthread.php?t=1712024&page=7
I can confirm that the Lockscreen one is working!! Thanks a bunch.
Do you know how this affects battery life? What about for the "off" one?
I used the Screenoff version for about a week and I didn't recognise battery drain. There should be an impact on battery but it is less than for example always active bluetooth.
[tapatalk]Vom S3 mit Tapatalk[/tapatalk]
does this require the rom? or just root?
this is fantastic btw
many thanks to you
I have been looking for this for while. Love to see you mod it.
Just ordered my set of 15 NFC tags, should be here this week, looking forward to trying this out
Any update on the battery use with the screen off version? It'd be great to have the screen off version, but if it costs battery then it's almost as good just using lockscreen. Thanks to the dev for creating this, great hack
confirmed working with screen off zip. used v5 cwm to install. works perfectly and should have been like this out of the box.
How do I determine if I need the odex or deodexed stock ROM?
is anybody using this on the LG1 firmware?
This work for tmobile as well?
Sent from my SGH-T999 using xda premium
For those on cm10 be careful because it borks the NFC and it will not show in settings
Sent from my SAMSUNG-SGH-I747 using xda premium
will this work with "[ROM] AOKP(Jellybean & ICS) Task & Ktoonsez Run a Train (7.24.2012)(TGFY ONLINE!!!)" ??
No...tried it, didn't work.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Will this work with the LG1 update?
Edit: I guess it does... worked for me.
Has anyone experienced an issue where the NFC just stops working? The check box is still ENABLED in settings, but the NFC tags are not being read. This happens with screen off or on. I have to disable and re-enable NFC in the settings to make it work again and be able to read the same tag. Then, after a period of time, NFC stops working again and i have to repeat the process.
Does this work with Google wallet as well?
cronojay said:
For those on cm10 be careful because it borks the NFC and it will not show in settings
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
+1 on that. Had it happen. Is there a CM10 version of this mod? Some have said beware of leaving phone open to attacks but I like the convenience.
tefloncoated said:
Has anyone experienced an issue where the NFC just stops working? The check box is still ENABLED in settings, but the NFC tags are not being read. This happens with screen off or on. I have to disable and re-enable NFC in the settings to make it work again and be able to read the same tag. Then, after a period of time, NFC stops working again and i have to repeat the process.
Click to expand...
Click to collapse
Same thing happens to me
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Let's see if we can trace our latest updates or mods... Not 100% sure, but I think my NFC hack was working fine until I installed the Google wallet hack. What was your latest set of mods?
Finally have enough posts for dev section -- wanted to say thanks for putting this flash together. i've had the lockscreen version working on both lem and lg1.
Someone please please PLEASE tell me if there is a way to tell the captive touchkeys to stay on when the screen backlight is on. I may be in the minority but I can't stand the lights going out while I'm using the phone. Sounds simple but I REALLY hate them going off. There wasnt an issue with the unofficial CM10 alpha 5(?). At one time I had a rom that allowed me to set a timeout in seconds OR to match the backlight. That would be perfect in my mind. It would be great if the keyboard backlights were on any time the keyboard is open (IMO). If I'm in the minority then someone please tell me where I can set it at the OS level for just me. If I can't find a solution then I will have to go back to alpha 5 and stay there.
I have googled everything I can think of. I keep getting pages about a "great" new beature of CM9 that allows you to disable the backlight altogether. Great for some maybe but not me. I bring that up to say that I have tried to find the answer on my own first.
Is your capacitive lights feature unchecked in the advanced settings? I think the majority of people who have used samsung phones don't need the lights, so that's why this feature has been implemated.
Sent from my SPH-D700 using xda app-developers app
It is unchecked. I have no problem with the ability to disable but would love to have the option to have them stay on (JB Default) when the screen is on. I don't like having to guess where the buttons are when it's dark out. It's petty I know but it really does bother me enough to not use the rom If I can't change it.
Please post questions in Q&A
Thread moved
Thanks
FNM
FWIW - I'd like to see this as an option, too. It's an annoyance, but not a show stopper. I'm actually getting pretty good at guessing where the capacitive keys actually are, but sometimes get ticked at fumbling for them.
Al
Bump (he said sheepishly)
Can any of the kernel or ROM devs provide some words of wisdom here? On Epic TW-based ROMs, there's definitely a setting to have the capacitive key backlighting timeout match either the screen timeout or the keyboard lighting timeout (I don't remember which).
Thanks.
Al
arschend said:
Bump (he said sheepishly)
Can any of the kernel or ROM devs provide some words of wisdom here? On Epic TW-based ROMs, there's definitely a setting to have the capacitive key backlighting timeout match either the screen timeout or the keyboard lighting timeout (I don't remember which).
Thanks.
Al
Click to expand...
Click to collapse
This functionality would have to be added to the CM framework. The framework is what controls the 6 second timeout and a configurable timeout setting has not been coded. Anyone is free to work that out and submit it to the CM gerrit system
Sent from my SPH-D700 using xda app-developers app
I am a programmer but don't have the slightest clue where to even begin. To be honest, it's not worth it if I have to work for months to get up to speed to do it myself. I'll have to look at other roms. Sad because I love this rom except for this one thing.
Sent from my SPH-D700 using Tapatalk 2
reiter01 said:
I am a programmer but don't have the slightest clue where to even begin. To be honest, it's not worth it if I have to work for months to get up to speed to do it myself. I'll have to look at other roms. Sad because I love this rom except for this one thing.
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
Understandable, because that's no easy task. But another alternative is to build your own kernel, and revert this patch which is how I fixed the capacitive lights in the 3.0 kernel. You could effectively break them again. Don't worry, they will still go off when you turn off the screen, they just won't timeout after 6 seconds.
I finally got brave
bbelos said:
Understandable, because that's no easy task. But another alternative is to build your own kernel, and revert this patch which is how I fixed the capacitive lights in the 3.0 kernel. You could effectively break them again. Don't worry, they will still go off when you turn off the screen, they just won't timeout after 6 seconds.
Click to expand...
Click to collapse
A year has passed. Updates have come and gone. I even switched to another phone and back to the Epic4G. Same thing bugged me as always. I took the leap and set up a virtual machine so I could compile CM 10.1. I did a test compile and came out fine. I then made the changes you mentioned (that made more sense once I got used to the built process) and it WORKED!
I now have CM 10.1 fully working with the button backlight staying on as long as the screen backlight. I LOVE IT.
Thank you so much (a year late).
reiter01 said:
I now have CM 10.1 fully working with the button backlight staying on as long as the screen backlight. I LOVE IT.
Click to expand...
Click to collapse
I've had my Epic for a week, running CM 10.1, and this bugs the snot out of me too. Any chance you could PM me a link to your build? :laugh:
Sure
I'll try to figure out where to upload it. Keep in mind I know nothing about coding for Android. It's simply CM 10.1 (newest) for EpicMTD with 2 numbers changed and then compiled. I do like that the ability to control the brightness of the buttons still works. I don't like them super bright but I do want them always on.
Download
Here is a download of the rom I compiled. Use at your own risk.
http://d-h.st/iuU
reiter01 said:
Here is a download of the rom I compiled. Use at your own risk.
http://d-h.st/iuU
Click to expand...
Click to collapse
Understood, and thank you good sir. :highfive:
UPDATE: Loaded, booted, and is running without a hitch. You have solved my one major gripe with CM on my Epic. Thankyouthankyouthankyouthankyou!
Glad I could help someone else. CM10.1 is so near perfect in every way, it was frustrating to have such an annoying "flaw". In the older version of CM they didn't have the ability to adjust the brightness of the buttons so I can understand some people wanting them off or fast timeout. If I ever have some spare time I will try to add this as a feature to the menu but I doubt it will ever happen.
@bbelos
Any way I can get my hands on your most recent 4.4 build source so I can build it with the bug put back in?
reiter01 said:
@bbelos
Any way I can get my hands on your most recent 4.4 build source so I can build it with the bug put back in?
Click to expand...
Click to collapse
Well,
device: https://github.com/cyanogenmod/android_device_samsung_epicmtd/tree/cm-11.0
kernel: https://github.com/cyanogenmod/android_kernel_samsung_epicmtd/tree/cm-11.0
whatever is in here: http://review.cyanogenmod.org/#/q/epicmtd+status:open+branch:cm-11.0,n,z
Patch
bbelos said:
Well,
device: https://github.com/cyanogenmod/android_device_samsung_epicmtd/tree/cm-11.0
kernel: https://github.com/cyanogenmod/android_kernel_samsung_epicmtd/tree/cm-11.0
whatever is in here: http://review.cyanogenmod.org/#/q/epicmtd+status:open+branch:cm-11.0,n,z
Click to expand...
Click to collapse
Thank you very much. I am running your build now but would love to make my 1 edit. Is it possible, without total rebuild or large headache, to make a patch for the one file?
reiter01 said:
Thank you very much. I am running your build now but would love to make my 1 edit. Is it possible, without total rebuild or large headache, to make a patch for the one file?
Click to expand...
Click to collapse
One other thing that might make things easier, go to Settings->Buttons->Backlight, and set the timeout for "Don't turn off" and see if that behaves to your satisfaction.
Sent from my SPH-D700 using xda app-developers app
Awesome
bbelos said:
One other thing that might make things easier, go to Settings->Buttons->Backlight, and set the timeout for "Don't turn off" and see if that behaves to your satisfaction.
Sent from my SPH-D700 using xda app-developers app
Click to expand...
Click to collapse
I installed your cm11 but havent gone through and tweaked it out. Looks like that might do the trick. I have found a couple bugs (to be expected).
1. If on a call and hit home, there is no way to get back to hang up. Have to power off.
2. While on home screen. Hitting the "menu" button at the bottom and choosing "settings" brings up the launcher3 settings. Used to be the android settings...maybe it's a change. Not a deal breaker but I prefer the old way.
Thank you for all your work. I wish there was some way I could help you out.
I dont see a lot of posts about this. But, there is a very annoying bug after the update; where if I press the Home Button to wake the screen, it will sometimes launch the task manager about a second later. I've seen sporadic posts about this for Tmobile as well as Sprint for JB 4.1.2 update; but nobody seems to have a solution.
I guess it's possible that some people dont think it's annoying enough to post; or, it's a possiblility it only affects people who have the factory rooted update installed.
I'm hoping someone smarter than me has already figured out a way to circumvent this very annoying behavior. What makes it really bad is that it only sometimes happens.
PS: The only carrier that doesn't seem to have this issue after the 4.1.2 update is ATT. My guess is they caught this bug before pushing it to all their customers.
mkanet said:
I dont see a lot of posts about this. But, there is a very annoying bug after the update; where if I press the Home Button to wake the screen, it will sometimes launch the task manager about a second later. I've seen sporadic posts about this for Tmobile as well as Sprint for JB 4.1.2 update; but nobody seems to have a solution.
I guess it's possible that some people dont think it's annoying enough to post; or, it's a possiblility it only affects people who have the factory rooted update installed.
I'm hoping someone smarter than me has already figured out a way to circumvent this very annoying behavior. What makes it really bad is that it only sometimes happens.
PS: The only carrier that doesn't seem to have this issue after the 4.1.2 update is ATT. My guess is they caught this bug before pushing it to all their customers.
Click to expand...
Click to collapse
I'm going to bet that is you disable your lockscreen you'll see this behavior just about every time. I'm fairly certain I tracked down at least one way to circumvent this behavior - check out this post for some info on it. The take home - my approach requires a wee bit of smali hacking, and everything that utilizing such a solution entails...
Dwitherell, thank you so much for responding. I was even considering on reverting back to 4.1.1 because of this. I don't use any kind password or pattern lock.
Forgive my ignorance, but the post you pointed me to locks like its on a Jedi ROM. I don't even see any specific references to this issue. What is this fix for specifically? If it is for sure going to restore normal behavior, i guess i could try to do this hack.
If this issue is as wide spread as i think it is, is there any chance you could make a tiny root app that fixes the problem or some way of automating a fix for not so technical people? How wide spread is this issue? Thanks a million for your help.
dwitherell said:
I'm going to bet that is you disable your lockscreen you'll see this behavior just about every time. I'm fairly certain I tracked down at least one way to circumvent this behavior - check out this post for some info on it. The take home - my approach requires a wee bit of smali hacking, and everything that utilizing such a solution entails...
Click to expand...
Click to collapse
My annoying fix...
I have been plagued by this since the update as well. I have tried factory resets and uninstall programs one by one. Nothing worked. Today I decided to try removing my lock screen pin, just used the swipe to unlock. That did not work. Then it came to me...
I set back up my pin to unlock, and switched the setting "Lock automatically" to Immediately instead of having a delay that I love. That "worked" as in it no longer goes to recent apps. But now I have to chose to have a pin to unlock it every time my screen turns off or remove security or deal with the recent apps issue. Any way you choose it's an extra annoying step to unlock.
I'd like to hear if anyone else has found any other solution.
Edit.... I have tried every lock option and as long as set to lock immediately, it will eliminate the problem. And the same with setting any delay, with any lock option it will result in the recent apps.
I forgot to mention that lock screen prevents this bug from happenening. I'm guessing that's why not everyone has complained about the issue.. and why the bug somehow sneaked passed beta testing of 4.1.2. I would think this changed behavior was a new "feature" as horrible as it is, but it looks like it dad unintentional since its not consistent behavior.
I'm hoping that a kind android developer who also can't stand this problem, Kay offer a small script or app for rooted user to patch this problem.
mrtolles said:
I have been plagued by this since the update as well. I have tried factory resets and uninstall programs one by one. Nothing worked. Today I decided to try removing my lock screen pin, just used the swipe to unlock. That did not work. Then it came to me...
I set back up my pin to unlock, and switched the setting "Lock automatically" to Immediately instead of having a delay that I love. That "worked" as in it no longer goes to recent apps. But now I have to chose to have a pin to unlock it every time my screen turns off or remove security or deal with the recent apps issue. Any way you choose it's an extra annoying step to unlock.
I'd like to hear if anyone else has found any other solution.
Edit.... I have tried every lock option and as long as set to lock immediately, it will eliminate the problem. And the same with setting any delay, with any lock option it will result in the recent apps.
Click to expand...
Click to collapse
mkanet said:
Dwitherell, thank you so much for responding. I was even considering on reverting back to 4.1.1 because of this. I don't use any kind password or pattern lock.
Forgive my ignorance, but the post you pointed me to locks like its on a Jedi ROM. I don't even see any specific references to this issue. What is this fix for specifically? If it is for sure going to restore normal behavior, i guess i could try to do this hack.
If this issue is as wide spread as i think it is, is there any chance you could make a tiny root app that fixes the problem or some way of automating a fix for not so technical people? How wide spread is this issue? Thanks a million for your help.
Click to expand...
Click to collapse
It was posted in a Jedi thread, but only because that is where I noticed it was mentioned. The context outside that single post was someone stating the same observation as you, my responding saying that I was also annoyed by it, with a later edit saying I may have come up with a workaround for it, and their response of "tell me more". As far as automating a fix or creating an app or the like - that is well beyond my paygrade unfortunately. What are you running? If you are interested you could PM me - all I need is your android.policy.jar (or to know what you are currently running) and I can try to get a fix together for you given some other conditions (i.e. have a custom recovery installed so you can flash things). It seems to have fixed it on my end, but I would be very interested in getting some others to test
You did it! Your fix works perfectly! The bug is gone! ...like the bug was never there. My understanding is the fix prevents the phone from stupidly trying to launch the task manager when the screen wakes by the home button. I also donated for you time and effort. Thanks a million.
dwitherell said:
It was posted in a Jedi thread, but only because that is where I noticed it was mentioned. The context outside that single post was someone stating the same observation as you, my responding saying that I was also annoyed by it, with a later edit saying I may have come up with a workaround for it, and their response of "tell me more". As far as automating a fix or creating an app or the like - that is well beyond my paygrade unfortunately. What are you running? If you are interested you could PM me - all I need is your android.policy.jar (or to know what you are currently running) and I can try to get a fix together for you given some other conditions (i.e. have a custom recovery installed so you can flash things). It seems to have fixed it on my end, but I would be very interested in getting some others to test
Click to expand...
Click to collapse
No, thank you for making me learn how to put an odexed mod together and testing it for me!
So this fix will work for anyone running a stock odexed version of 4.1.2 UVBMB4 - you just need to be rooted, and having a custom recovery would be nice so you could flash it but you could also just copy the files over. That being said - would this be worthwhile to post?
I wish i had know i could just copy the files over.. that's actually less convoluted process than depending on a script. I thought the reason you made a patch via flashing is because the system files were locked/open by the system. Anyway, i am extremely thankful for this'll as there is no other way to fix the bug without adding extra steps to wake the screen.
You should definitely share both odexed and deodexed patches with others. I personally don't know how i could tollerate that bug for much longer. I'm sure there are others who don't use the lock screen. Plus, this would give a chance for others to appreciate your work by dontating for your time and effort.
mkanet said:
I wish i had know i could just copy the files over.. that's actually less convoluted process than depending on a script. I thought the reason you made a patch via flashing is because the system files were locked/open by the system. Anyway, i am extremely thankful for this'll as there is no other way to fix the bug without adding extra steps to wake the screen.
You should definitely share both odexed and deodexed patches with others. I personally don't know how i could tollerate that bug for much longer. I'm sure there are others who don't use the lock screen. Plus, this would give a chance for others to appreciate your work by dontating for your time and effort.
Click to expand...
Click to collapse
The flashable zip is just one method to get the files where they need to go. Literally all it does is overwrite the 2 files in /system/framework by moving the 2 files over from the zip - but there are definitely other ways to do such things. Some are more comfortable with this route, others are more comfortable w/ getting /system to be rw and move the files manually.
I'll likely post this at some point in the next few days
I don't mean to revive a dead thread or anything, but this bug has been driving me CRAZY & the smali hacking worked perfectly for me, thank you!!!
FYI, I'm willing to help people out with this as well. If anyone wants this done but doesn't wanna mess with the java stuff, PM me & send me your android.policy.jar and I'll hack it for you
kabuk1 said:
I don't mean to revive a dead thread or anything, but this bug has been driving me CRAZY & the smali hacking worked perfectly for me, thank you!!!
FYI, I'm willing to help people out with this as well. If anyone wants this done but doesn't wanna mess with the java stuff, PM me & send me your android.policy.jar and I'll hack it for you
Click to expand...
Click to collapse
Glad to hear
Is it possible that my phone isn't affected? If its a 4.1.2 bug, it should be in all phones with same version right?
This is not happening to my phone. Whether I have lock screen activated or not. I'm rooted but running stock ROM and I have Nova launcher installed if thats even important.
It's not all notes.
Sent from my SGH-T889 using xda premium
kabuk1 said:
I don't mean to revive a dead thread or anything, but this bug has been driving me CRAZY & the smali hacking worked perfectly for me, thank you!!!
FYI, I'm willing to help people out with this as well. If anyone wants this done but doesn't wanna mess with the java stuff, PM me & send me your android.policy.jar and I'll hack it for you
Click to expand...
Click to collapse
is this offer still good? i'm was experiencing the same problem and it was so annoying that the only solution i found was to revert back to 4.1.1. I'm currently running t889uvall4.
also, my phone is not rooted. will the fix dwitherell came up w/ work? or do i really have to root my phone?
wesblogger said:
is this offer still good? i'm was experiencing the same problem and it was so annoying that the only solution i found was to revert back to 4.1.1. I'm currently running t889uvall4.
also, my phone is not rooted. will the fix dwitherell came up w/ work? or do i really have to root my phone?
Click to expand...
Click to collapse
Yes you'll need to be rooted unfortunately - sorry
wesblogger said:
is this offer still good? i'm was experiencing the same problem and it was so annoying that the only solution i found was to revert back to 4.1.1. I'm currently running t889uvall4.
also, my phone is not rooted. will the fix dwitherell came up w/ work? or do i really have to root my phone?
Click to expand...
Click to collapse
Absolutely. just PM me. Yeah, you have to be rooted but that's easy to do & worth it for this hack & all the other things you can do once you're rooted.
kabuk1 said:
...Yeah, you have to be rooted but that's easy to do & worth it for this hack & all the other things you can do once you're rooted.
Click to expand...
Click to collapse
^^^ THIS - a thousand times over
I won't post the link here because I don't have permission to do so, but a couple of the developers from Cyanogenmod have been working on Alpha builds, and a new one (4.4.4) was released last night sometime. The following link is to the dev's G+ page so go ahead and find the link from there, not too hard.
https://plus.google.com/+TomMarshall/posts
Also, APN's are working along with LTE speeds, haven't tested out phone calls yet due to no vibration/sound anywhere in the device, so it's not really "usable" at this point. The newest SlimROM Gapps work just fine by the way.
Hopefully we can keep this thread as a central point for discussion since now there are multiple spread throughout the General and Q&A forums.
Are you sure there is no sound period? I thought there was sound through the earpiece just not the external speakers.
pside15 said:
Are you sure there is no sound period? I thought there was sound through the earpiece just not the external speakers.
Click to expand...
Click to collapse
Well, even if there is, that doesn't do any good for the casual user flashing this ROM, they won't hear/feel a phone call/message if the phone is in their pocket. Even if everything besides sound/vibration is working, I still like my phone to act like a phone, you know?
pside15 said:
Are you sure there is no sound period? I thought there was sound through the earpiece just not the external speakers.
Click to expand...
Click to collapse
I'm on the 09/07 build and I have sound through the earpiece, calls seem to work fine.
Edit: Headset sound works as well.
stevew84 said:
Well, even if there is, that doesn't do any good for the casual user flashing this ROM, they won't hear/feel a phone call/message if the phone is in their pocket. Even if everything besides sound/vibration is working, I still like my phone to act like a phone, you know?
Click to expand...
Click to collapse
Yeah, I understand. Was just wondering if I had read the info correctly before.
kchino said:
I'm on the 09/07 build and I have sound through the earpiece, calls seem to work fine.
Click to expand...
Click to collapse
That's all well and good, but I have to have a phone that notifies me of a call/text while it's sitting on my desk or in my pocket. I fully appreciate the fact this is an Alpha build and I'm not complaining in the least bit, I just can't wait until 5.0 hits the G3...or at least 4.4.4 stable with a good 5.0 theme.
If anyone is wondering this ROM is actually based off Slim as opposed to CM. It has Slims Recents, Quicktiles, Floating Window, Shake Events etc, which are all working.
kchino said:
If anyone is wondering this ROM is actually based off Slim as opposed to CM. It has Slims Recents, Quicktiles, Floating Window, Shake Events etc, which are all working.
Click to expand...
Click to collapse
This is what I don't get, given the fact that this is a PHONE, I would assume that the first thing to get working correctly would be any and everything relating to calls/texts.
Uh...well, everything gets tested and built from the ground up. So some things come along faster than others.
mzrdisi said:
Uh...well, everything gets tested and built from the ground up. So some things come along faster than others.
Click to expand...
Click to collapse
I know, my whole gripe with test/alpha build is that getting the phone part of the device isn't necessarily a priority upon releasing something.
stevew84 said:
I know, my whole gripe with test/alpha build is that getting the phone part of the device isn't necessarily a priority upon releasing something.
Click to expand...
Click to collapse
The "phone" part of the build does work correctly. The audio not working is a separate matter that has nothing to do with the "phone" part of the rom.
While audible notifications are most certainly a requirement for a daily driver, the reality is that these are alpha builds that are being worked on by a select few people. Everything will get worked out, it's just a matter of time. Been here in this very place several times with phones before the G3, unless you're in the know how, you just gotta play the waiting game
cvsolidx17 said:
The "phone" part of the build does work correctly. The audio not working is a separate matter that has nothing to do with the "phone" part of the rom.
While audible notifications are most certainly a requirement for a daily driver, the reality is that these are alpha builds that are being worked on by a select few people. Everything will get worked out, it's just a matter of time. Been here in this very place several times with phones before the G3, unless you're in the know how, you just gotta play the waiting game
Click to expand...
Click to collapse
Yea i know, been thinking about trying to learn how to go about compiling a CM build from scratch, or port from something similar, but that's a lot of time and effort.
stevew84 said:
I know, my whole gripe with test/alpha build is that getting the phone part of the device isn't necessarily a priority upon releasing something.
Click to expand...
Click to collapse
I'm not sure why you have a gripe at all? It's a very stable alpha build that is actively being worked on and provided to you for free! If you don't like the pace of development why don't you contribute? I understand that you opened this thread to discuss AOSP builds but contrary to your assertion that you are "not complaining" you've posted some inaccuracies about the 1st and only AOSP ROM and told us over and over how you need your phone to be a phone.
We get it. Go back to the LG ROMs until this one suits your needs.
kchino said:
I'm not sure why you have a gripe at all? It's a very stable alpha build that is actively being worked on and provided to you for free! If you don't like the pace of development why don't you contribute? I understand that you opened this thread to discuss AOSP builds but contrary to your assertion that you are "not complaining" you've posted some inaccuracies about the 1st and only AOSP ROM and told us over and over how you need your phone to be a phone.
We get it. Go back to the LG ROMs until this one suits your needs.
Click to expand...
Click to collapse
I'm simply responding to people here, I pointed out what works and what doesn't work with the TWO working Alpha builds. There is a third in the works by AICP but has yet to be released. My only gripe really is for a build to be released, although a test build, without the main functionality of the device working properly...that's it.
I am on an LG ROM at the moment.
The purpose of this thread is to discuss the builds as they come out and to have a central location for all prominent links.
stevew84 said:
I know, my whole gripe with test/alpha build is that getting the phone part of the device isn't necessarily a priority upon releasing something.
Click to expand...
Click to collapse
The thing is a lot of those things aren't phone specific so if they work on other builds they should work here.
For anyone who has tried this, does it get rid of the artificial sharpness?
GoogleAndroid said:
For anyone who has tried this, does it get rid of the artificial sharpness?
Click to expand...
Click to collapse
It looks fine, I mean I don't notice any over sharpening, but then again I don't have my face less than a few inches away from my eyes. Either way, the animation scale is set to .5 so it looks faster than it really is. Set the scales back to 1.0 and everything is really fluid with NO skipping/stuttering/whatever you want to call it.
Lack of vibration and sound across the board is really the only issue at this point. For day to day use, I mean.
Still waiting on the AICP build as that will probably incorporate the missing necessities that the other two builds are lacking.
stevew84 said:
This is what I don't get, given the fact that this is a PHONE, I would assume that the first thing to get working correctly would be any and everything relating to calls/texts.
Click to expand...
Click to collapse
Correct you don't get it. The source code for the ROM is already done, it already has their features. What they are doing is adding the device source and trying to get the drivers working. Its not like they think well lets go add 1% battery, its already in the source code. What they are working on is the device side not the feature side.
stevew84 said:
It looks fine, I mean I don't notice any over sharpening, but then again I don't have my face less than a few inches away from my eyes. Either way, the animation scale is set to .5 so it looks faster than it really is. Set the scales back to 1.0 and everything is really fluid with NO skipping/stuttering/whatever you want to call it.
Lack of vibration and sound across the board is really the only issue at this point. For day to day use, I mean.
Still waiting on the AICP build as that will probably incorporate the missing necessities that the other two builds are lacking.
Click to expand...
Click to collapse
I'm not sure why you continue to mislead based solely on your preference. I'm on the build right now, it is easier to state what doesn't work because this build is very close to beta:
1.2 09/07 build - Not working:
External Speaker (...On the back, Headset audio and earpiece audio are working fine.)
Vibration
Cameras & rear LED
External SD Card
Bluetooth
I haven't come across anything else that isn't working. Wifi, Mobile Data, GPS, incoming/outgoing calls have worked without a hitch. Also this is AOSP so there is zero of the text sharpening that is present in the LG ROMs. I've changed the governor to interactive by default it's set to performance and the cpu does not scale which will contribute to heat reports that initially popped up.
kchino said:
I'm not sure why you continue to mislead based solely on your preference. I'm on the build right now, it is easier to state what doesn't work because this build is very close to beta:
Not working:
External Speaker (...On the back, Headset audio and earpiece audio are working fine.)
Vibration
Cameras & rear LED
External SD Card
I haven't come across anything else that isn't working. Wifi, Mobile Data, GPS, incoming/outgoing calls have worked without a hitch. Also this is AOSP so there is zero of the text sharpening that is present in the LG ROMs. I've changed the governor to interactive by default it's set to performance and the cpu does not scale which will contribute to heat reports that initially popped up.
Click to expand...
Click to collapse
Mount to PC works for you? I mean internal storage.
Sent from my LG-D851 using XDA Free mobile app