FAQs - Massive Question Round Up Thread for Flo
፨ INTRODUCTION ፨
Hello! So you got your awesome flashy new tablet but you have a million questions to ask. Maybe it's your first Android tablet. Maybe you're late to the party. Maybe you forgot everything you know.
It's okay. This thread will help you. This thread is not to discourage you from posting a new one but simply to save you time in case your question has been answered but buried over time.
This thread will also help the forum stay fresh and clutter free. However if your question was not answered here, feel free to start your own.
፨ IMPORTANT ፨
There are some things to keep in mind before reading this thread:
It is impossible to gather all knowledge on this device, therefore this thread will always be incomplete. Please keep in mind that if something is not answered here it does not mean it wasn't elsewhere on the forum. Search before posting.
All of the questions/issues have been researched in depth and a source will be given if applicable. However, there is always a chance some of the information is wrong. Please only attempt a fix if you're comfortable doing so.
This thread will get quite long over time, I recommend you Ctrl+F (or equivalent) and search by keyword.
If you have any suggestions or want to submit a question/answer, PLEASE do so. It makes keeping this updated easier and lets the community participate. Credit will be given.
፨ FAQs ፨
Q: How do I unlock my bootloader/root/install a custom recovery?
A: philos64 walks you through the entire procedure. From stock, to unlocked bootloader, root and TWRP. Find his guide here.
Q: Is there a way to unlock my bootloader without losing my data? Thanks to marcusjt.
A: No. When you initiate the bootloader unlock process the data will be lost. It is recommended to unlock the bootloader before you start filling it with data. However if you have already done so you can still back up your apps with an external application, such as TitaniumBackup. Please be aware, however that if you install a custom ROM, it is recommended to not restore previous data and start fresh instead.
Q: I have to relock the bootloader, how do I go about doing that?
A: Just as easy as unlocking. Boot to the bootloader and on fastboot type: fastboot oem lock
Q: What is the difference between root and an unlocked bootloader?
A: An unlocked bootloader allows you to write protected partitions such as system or recovery. This lets you flash custom ROMs (un-official non-stock operating systems that have more functionality such as CyanogenMod, AOKP, ParanoidAndroid, etc.). Root does not mess with partitions, instead it grants you complete control over the OS (Android) itself. It will let you write and edit any file you wish. This lets you run apps like Titanium Backup and Adblock that need to either access or edit system files.
Q: This is my first Nexus device. I was told with my previous device to wait until an unlock or root method is found before upgrading to a new release. Is that the case here?
A: No. With Nexus devices there is no fear of having the bootloader locked down further. It will always be unlocked in the same fashion and root is a flash away.
Q: Will I lose OTA notifications if I root/unlock bootloader/install custom ROM? Thanks to marcusjt.
A: If all you do is root or unlock the bootloader then you will continue to receive OTA notifications from Google. Please be aware that root will be lost if you don't preserve it through your SU app. Most custom ROMs remove the ability to receive official OTA notifications from Google.
Q: What is the name of this Nexus 7? I keep hearing all these different names! Thanks to zaclimon.
A: Our device is named after a previous one with the same name, thus confusion will arise. The official name for it is Nexus 7 (2013), this is what Google calls it. Amazon brought a new name: Nexus 7 FHD presumably after "full high definition". Furthermore, there are two other names that refer to our device, Flo (this thread's title) refers to the board of the device (hardware). While Razor is the device's codename.
Q: Does the Nexus 7 support USB OTG?
A: According to forum members in this thread most OTG uses should work. However be aware that for certain devices external power might be needed.
Q: Is the notification light RGB? Why can I only have it flash white?
A: The software is reporting that the LED on the Nexus 7 is only white (my explanation here). Also, looking at the actual LED we can see that it can only support one color, white.
Q: Where is the NFC sensor? What about the wireless charger?
A: Both the NFC and the Qi coil are located in the middle of the device. X marks the spot, line up the X on the Nexus logo on the back to activate NFC or begin wireless charging.
Q: How do I take a screenshot?
A: Press power and volume down at the same time for a couple of seconds.
Q: Does the tablet have a magnetic screen on/off feature like its predecessor?
A: kpa2727 has confirmed that the tablet does indeed have a magnetic sensor for the display. The smart cover sensor is located on the bottom left of this device.
Q: Does it contain haptic feedback? (Vibration)
A: No, just like the previous N7 this one does not have any rumble feedback.
Q: Do I need an official wireless charger to charge my tablet without wires?
A: The Nexus 7 is Qi compatible which means that any Qi certified charger will work. Official or otherwise.
Q: Can I pair my Wiimote controller to my Nexus 7?
A: Since Google updated the bluetooth stack to Qualcomms in Android 4.2, Wiimotes and the like have not been able to pair. This is no different on the Nexus 7 running Android 4.3+ (or any other 4.x build). UPDATE: A new app hit the market that allows this for 4.x, however an external USB OTG adapter is needed (must be a EDR dongle with a CSR chipset).
Q: How come Google Wallet won't install? Play store says my device is not compatible.
A: The new Nexus 7 is missing the secure element required in order for Wallet to work at all. A Google rep has confirmed that the Nexus 7 lacks the hardware, this cannot be fixed through software. UPDATE: As of Android version 4.4, Wallet will begin to work with the Nexus 7 thanks to the new HCE feature.
Q: Why does GPS lock up on me?
A: This issue occurs on early builds of the software. Starting with build JSS15Q this has been fixed so all that needs to be done is update to the latest OTA or ROM based on this build. However if you would not like to update, sfhub has a solution in his thread that allows the GPS issue to be fixed without updating your OS.
Q: The touch screen is sometimes inaccurate and I get phantom touches, especially with multi-touches, why?
A: Different digitizer hardware were used on our N7 so depending on what touchscreen hardware you have this might be an issue. Not everyone will experience this and the latest JSS15Q update has fixed the problem for some users. If the update does not fix your issue, sfhub has a post located here that aims to fix the problem for most people.
Q: Wireless charging is not working, why?
A: Some early built tablets have an issue with the wireless connector. If you do not want to void your warranty simply get it exchanged. Otherwise if you're bold enough to open your tablet, tkdsl explains how to fix the issue (the four connectors are each pair to the right of the circle in this picture).
Q: The speakers are making a static/buzzing/white noise sound when my volume is low, is my unit defective?
A: No, it's not defective, this is the way the hardware was built. If you want to know what causes the issue, siraltus has a very good explanation here.
Q: I'm stuck in a bootloop/my tablet wont get past the startup animation. What can I do?
A: If you think you have soft bricked your device, ATGAdmin has a one click restore tool located here. It will restore your tablet to it's condition out of the box.
Q: What ROM, kernel or mod should I use? There are too many options!
A: Options are always good! While no one can tell you what works best for you, philos64 has created a repository of ROMs, kernels and more to make it easier to find than wading through the forum. His thread is located here. Thanks to pelago for informing me about the updated thread.
Q: Can my Nexus 7 (2013) Data Version place phone calls/send texts through mobile data?
A: It will likely not be available out of the box. Or at all. If devs take interest it MIGHT be possible. The previous Nexus 7 can only send SMS but no GSM calls however, the Galaxy Tab 10.1 can do both. Bottom line is: don't expect this, it will likely never happen, consider this before purchasing the tablet.
Q: Does the Nexus 7 (2013) have an IR (Infrared) blaster for TV control?
A: No, it does not.
Q: My question isn't answered here, what can I do?
A: Well that depends on what your situation is. Here are a couple of helpful tips, though:
If your question is a general one about the tablet (how do I X?) then first SEARCH the forums. Try different key words. If that doesn't answer your question, feel free to make a new thread.
If you don't want to start a thread and have stage fright, feel free to post your question here. Also, if you know the answer to a posted question, please answer it -- this thread is for the community to work together.
Forgot a reserve post, whoops
Can I buy the equipment in another country?
I have a doubt that is related to the fact that the tablet is not yet marketed in Portugal.
I know I can buy, but what I want to know is if I'm not having problems accessing Google Play and other services that may not yet be working in Portugal.
fabiomsseabra said:
I have a doubt that is related to the fact that the tablet is not yet marketed in Portugal.
I know I can buy, but what I want to know is if I'm not having problems accessing Google Play and other services that may not yet be working in Portugal.
Click to expand...
Click to collapse
While it's possible to use a VPN to trick Google services to think you're in the us it's not recommended because you would always have to use it. Also payment becomes an issue.
If a service is not available in your country you would have to wait until Google expands I'm afraid
I know there is a tool out there for fixing a soft brick but my question is how could I have soft bricked when all I did yesterday was install apps and update to 4.3.....Then I charged the device and shut it off. Tried turning it on this morning and it won't go bast the Nexus logo. Please help!
rickm8384 said:
I know there is a tool out there for fixing a soft brick but my question is how could I have soft bricked when all I did yesterday was install apps and update to 4.3.....Then I charged the device and shut it off. Tried turning it on this morning and it won't go bast the Nexus logo. Please help!
Click to expand...
Click to collapse
The were some people that did brick on the update, but it's weird in your case because it sounds like you got a boot after the update. I just recommend you use the tool or factory reset it yourself. Otherwise check out the emergency thread by philos64 here.
Sent from my Nexus 7 using Tapatalk HD
Ended up calling Google support. The strange thing was, they couldn't even boot me into recovery. We kept getting a screen that said "no action". Ended up having to use a different button sequence but eventually we got into recovery and factory reset. Back in working order.
Sent from my SGH-T889 using Tapatalk 4 Beta
software developing
Im a noob. When custom roms comes out in the future, will it be a big factor if the model is wifi or 3g, or developers will just easily add a radio/baseband/modem into their custom roms and it will have support for 3g devices already?
Speaking of softbricks, I updated and unlocked/TWRP/rooted two days ago and rebooted two or three times with everything being just fine until this morning, where it wouldn't get past the X logo.
The last thing I had done before powering down last night was watch that "Luna" short in Play Movies. Weird
my N7 will not boot without having to format data. I unlocked the bootloader, rooted it with supersu and flashed twrp on it. It worked fine for a few hours, I hadn't installed any mods. Then all of a sudden I get stuck on the splash screen indefinitely several times. The only thing that brings it back is to go into recovery and format data.
Sent from my Nexus 7 using Tapatalk HD
Maybe someone here would find the post I just made useful:
http://forum.xda-developers.com/showthread.php?p=44187424#post44187424
What is this popup i keep getting on custom roms it doesnt hapoen on stock roms though ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 7 using Tapatalk 4 Beta
im stuck on the X logo on bootup! i can only bootup to bootloader mode, i have fastboot cmd available, what do i do? i think i still have stock recovery hw: rev e
bootloader: flo3-14
signing -yes
secure boot enabled
unlocked state
Okay, it SEEMS like the emergency thread was merged with mine. I will try to help as best I can, however be advised that I did not intend for this thread to be an emergency solution.
---
casonswag said:
What is this popup i keep getting on custom roms it doesnt hapoen on stock roms though ?
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
This has to do with the way your device is identified. While I don't know a solution (short of doing what the image suggests) someone made a thread here. Perhaps he found another solution.
cobyman7035 said:
im stuck on the X logo on bootup! i can only bootup to bootloader mode, i have fastboot cmd available, what do i do? i think i still have stock recovery hw: rev e
bootloader: flo3-14
signing -yes
secure boot enabled
unlocked state
Click to expand...
Click to collapse
A couple of users have reported this happening to them when updating the tablet from the stock image it comes with. Looking around I found this thread and while the OP in that thread ended up trading the device for another one, before doing that try a couple of things. Restart the device (obvious, I know, but still, hold down power for 30 secs, let it reboot). If that does not work, attempt a hard reset (it will wipe your data). This should definitely fix the issue and remember that the first boot will take longer so don't freak out after the reset.
TaintedByte said:
Okay, it SEEMS like the emergency thread was merged with mine. I will try to help as best I can, however be advised that I did not intend for this thread to be an emergency solution.
Click to expand...
Click to collapse
I requested to delete my thread because it was useless to have a duplicate with your. I think we don't need to have several posts for trying to resolve problems (all problems are an emergency, but sometimes not real )
And it's more easier for members to search ONE thread for post a problem and having a solution.
But before to post something, members need to read and search in this thread before. A solution for a problem was maybe posted before
Thanks
3G version support voice calling or not ?
3G version support voice calling or not ?
Click to expand...
Click to collapse
Normally not
When the 4g version comes out, will I just be able to take the SIM out of my S4 and put it in the N7 to use data at home then put it back in my S4 when I leave without a problem?
Digital_Fidelity said:
When the 4g version comes out, will I just be able to take the SIM out of my S4 and put it in the N7 to use data at home then put it back in my S4 when I leave without a problem?
Click to expand...
Click to collapse
Yes you can do it normally without problem.
If it's a micro sim, it's ok
philos64 said:
Yes you can do it normally without problem.
If it's a micro sim, it's ok
Click to expand...
Click to collapse
Awesome, thank you. I was thinking about getting an Xperia Tablet Z but I think I'll just wait for the Nexus 7 4G and save several hundred dollars lol
Related
DO NOT TRY OCLF, if you can not go to factory reset.
I have read almost all the threads answer etc. on many forums, How many people faced the problem and I think I am latest victim after having OCLF, phone doesn't start anymore, does not go in hard reset..nothing just vibration and 2 lights in bottom nothing else.
It just screwed me, OCLF 2.2, with Z4Root , Android 2.2 froyo on SGS....installed and you are gone. still you want it go ahead, feel free....I am angry on myself not on anybody else but I thought, I better write something to save few people at least, opposed to other people who are also bricked and praised the fix to not to stand alone.
Finally I gave phone back, not sure if I get a new one or get same repaired ( in warranty or I have to pay if they can detect that It was me not the hardware or something else...), will post what happens but for now, its not safe, do not go for it and remember there is very thin line between bravery and foolishness. decide yourself.
There are numerous ways to recover your SGS, all you had to do was have a read on here, don't panic and use the search function.
I'm new to all this and i've been in the same position as you and have thought I had bricked my phone at least 5 or more times. But thanks to others on XDA they have same me and my SGS )
sorry but if you dont know what you are doing, why are you doing it?
and btw there are alot of things you can do to recover your phone, even if its totally bricked.
you saying you read all threads etc? i dont think so cuz then you would know what to do.
and OCLF IS SAFE, if you know what you doing and have to do if its going wrong.
ps: if you need help, pm me i will explain you what to do, but only if you have the phone in front of you.
There should be a big banner in the development section which says "Don't try these if you are a n00b and not willing to read and learn before flashing anything!"
That is a thoughtless, misinformed thread title maligning a good developer's excellent work.
Think hard before you post in future........
doc jpy 7.1, jpx, k12i.
OCLF pertains to the Software Level. I see no reason for the Hardware to be affected. You should always be able to go the Download Mode after removing the battery for sometime.
i just say OMG.. i "bricked" (like you) my device about 7-8 times... no problem! i also BRICKED my device 1 time... no problem! don't panic, sgs is very strong! use search function of forum, the problem is not OCLF itself, is a "dead" sd-card (i don't know exactely, i'm a noob) it's a problem connected with the mount of an internal memory, i personally discovered that it might be also connected with a wrong flash of the csc (personal experience!)
Next time (yes it will be) don't panic there's a solution
No panic, just another way of adding some more info for OCLF
Well well well, I am not in panic, I have had galaxy for 5 days only and of-course a new comer for Android, I didn't hesitate for the fix, tried to figure out pros and cons (unfortunately didn't see complains for the problem I had after reboot, until I became the victim) and to be clear not trying to blacken the founder of OCLF with due respect.
Thanks for the fellows offering help, I don't have phone with me as I was not willing to play around with other fixes as I can get it fixed by service center but it would be great if you can blog about it or mention steps here for a problem of a phone stuck on Galaxy screen and can't go in recovery mode and does not connect with odin. what you get is black screen, 2 lightning button in the bottom and vibration when you press any key in bottom or screen.
I was already expecting the several responses and staring eyes but if its safe then why you have so many thread complaining a frozen phone. If this fix is safe then why its removed from Market? (arrg Google norms..but for a good thing and open source system, don''t understand, make it an enhancement, put it already in ROM)
and why OCLF app does not warn, if you have a temp root or permanent root? before making the fix. if its not possible in this context then place info window as it will fail with temp root.
ODIN thing will only work with rooted phone what if its temp rooted and do you want any user to open their phone's mother board for making some soldering to re flash.
Please somebody make a detailed instruction page, if its safe and get proper steps and don'ts list, I won't mind doing it again once I get phone back and keeping fingers crossed that they won't charge me for this out of warranty. Not sure I'll get replacement or repaired one.
Again its not safe until and unless in any case you are ready for using other fixes (which may or may not be applicable for your situation)to fix the phone.There are chances that you loose important data(if not backup). Go for it, if you have enough time and nothing else to do, if it works, good for you, if not don't panic..............
and don;t forget its not your development machine, open in front of you, for free by company, which has corrupted passwd file or something and not booting up....it's your costly new smart phone.
yeah criticize me but its doesn't feel nice when your brick your new phone.
in the end some more things to remember based on my exp for prevention:
1. Back up data
2. make sure you have hard reset option available
3. Root permanent
Please add more if you know. anyways thanks for all the responses.
Tried once to have a bricked phone, my first try actually..
Formated the system by mistake, to high i guess.. LOL..
Non the less, had black-screen ofc, System format, in more than 5 hours, till I tried odin with the org firmware, and brick gone
Sure, thought Sh!!!!!t at first, but then started reading, that was what I've spent the 5 hours on, and 7mins later up and running.. No worries for brick no more
So, think you could have made it your self, instead of returning it, sry
Or maybe you couldn't go into DL mode? I could with formated system?
Just like dhiru1602 wrote, DL mode should be in place, it was on mine like I said
SandeepSharma said:
Well well well, I am not in panic, I have had galaxy for 5 days only and of-course a new comer for Android, I didn't hesitate for the fix, tried to figure out pros and cons (unfortunately didn't see complains for the problem I had after reboot, until I became the victim) and to be clear not trying to blacken the founder of OCLF with due respect.
Thanks for the fellows offering help, I don't have phone with me as I was not willing to play around with other fixes as I can get it fixed by service center but it would be great if you can blog about it or mention steps here for a problem of a phone stuck on Galaxy screen and can't go in recovery mode and does not connect with odin. what you get is black screen, 2 lightning button in the bottom and vibration when you press any key in bottom or screen.
I was already expecting the several responses and staring eyes but if its safe then why you have so many thread complaining a frozen phone. If this fix is safe then why its removed from Market? (arrg Google norms..but for a good thing and open source system, don''t understand, make it an enhancement, put it already in ROM)
and why OCLF app does not warn, if you have a temp root or permanent root? before making the fix. if its not possible in this context then place info window as it will fail with temp root.
ODIN thing will only work with rooted phone what if its temp rooted and do you want any user to open their phone's mother board for making some soldering to re flash.
Please somebody make a detailed instruction page, if its safe and get proper steps and don'ts list, I won't mind doing it again once I get phone back and keeping fingers crossed that they won't charge me for this out of warranty. Not sure I'll get replacement or repaired one.
Again its not safe until and unless in any case you are ready for using other fixes (which may or may not be applicable for your situation)to fix the phone.There are chances that you loose important data(if not backup). Go for it, if you have enough time and nothing else to do, if it works, good for you, if not don't panic..............
and don;t forget its not your development machine, open in front of you, for free by company, which has corrupted passwd file or something and not booting up....it's your costly new smart phone.
yeah criticize me but its doesn't feel nice when your brick your new phone.
in the end some more things to remember based on my exp for prevention:
1. Back up data
2. make sure you have hard reset option available
3. Root permanent
Please add more if you know. anyways thanks for all the responses.
Click to expand...
Click to collapse
Did u read the info screen that pops up when u first started oclf? I guess u didnt coz there are very clear instructions on what u have to do to apply the lagfix sucessfully...
Edit: btw ockf is on market again he just had to remove the abillity to root...
Sent from my GT-I9000 using Tapatalk
SandeepSharma said:
Well well well, I am not in panic, I have had galaxy for 5 days only and of-course a new comer for Android, I didn't hesitate for the fix, tried to figure out pros and cons (unfortunately didn't see complains for the problem I had after reboot, until I became the victim) and to be clear not trying to blacken the founder of OCLF with due respect.
Thanks for the fellows offering help, I don't have phone with me as I was not willing to play around with other fixes as I can get it fixed by service center but it would be great if you can blog about it or mention steps here for a problem of a phone stuck on Galaxy screen and can't go in recovery mode and does not connect with odin. what you get is black screen, 2 lightning button in the bottom and vibration when you press any key in bottom or screen.
I was already expecting the several responses and staring eyes but if its safe then why you have so many thread complaining a frozen phone. If this fix is safe then why its removed from Market? (arrg Google norms..but for a good thing and open source system, don''t understand, make it an enhancement, put it already in ROM)
and why OCLF app does not warn, if you have a temp root or permanent root? before making the fix. if its not possible in this context then place info window as it will fail with temp root.
ODIN thing will only work with rooted phone what if its temp rooted and do you want any user to open their phone's mother board for making some soldering to re flash.
Please somebody make a detailed instruction page, if its safe and get proper steps and don'ts list, I won't mind doing it again once I get phone back and keeping fingers crossed that they won't charge me for this out of warranty. Not sure I'll get replacement or repaired one.
Again its not safe until and unless in any case you are ready for using other fixes (which may or may not be applicable for your situation)to fix the phone.There are chances that you loose important data(if not backup). Go for it, if you have enough time and nothing else to do, if it works, good for you, if not don't panic..............
and don;t forget its not your development machine, open in front of you, for free by company, which has corrupted passwd file or something and not booting up....it's your costly new smart phone.
yeah criticize me but its doesn't feel nice when your brick your new phone.
in the end some more things to remember based on my exp for prevention:
1. Back up data
2. make sure you have hard reset option available
3. Root permanent
Please add more if you know. anyways thanks for all the responses.
Click to expand...
Click to collapse
READ!!!!!!!!!!!!!!!!! SEARCH!!!!!!!!!!!!!!!!!!!!!!!!!!!! READ!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! SEARCH!!!!!!!!!!!!!!!!!!!!!!!!! BREATH IN!!!!!!!!!!!!!!!!!!!!!!! BREATH OUT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
1. You didn't read instructions clearly
2. You created a misleading thread title
3. You are now asking for step by step instructions when there is already numerous guides and answers on how to get your phone going again
4. You now look like a lazy, ignorant and upset kid that broke his new toy because he was too rough with it and now expects to be spoon fed instead of actually learning from his mistake.
5. I am not usually this hard on anybody but I am annoyed by this thread
you're funny. maybe you can discuss why it's so bad with RyanZA himself?
herpderp.
If you hadn't have badmouthed his work, you'd have found Ryan extremely helpful, in fact, he's such a good bloke, he'd probably still help you if it was necessary.
doc jpy 7.1, jpx, k12i.
@OP: Please change the thread's title to something more respectful for RyanZA's hard work.
A good title like : "too lazy to read before doing something potentially dangerous to my expensive smartphone, I've bricked it (in fact probably not...) while trying OCLF..."
___________________________________
Sent from my GT-I9000 ××× DocRambone®'s XXJPY_Kitchen, Hardcore®'s SpeedMod K12I, ext4-all ××× using Tapatalk Pro®
its ok now guys, he is new to android and galaxy. Close this thread pls.
pm me if you got your phone back and i still will help you and explain everything.
Just plug it into the computer and use adb reboot recovery. Should work, it did for me.
Sent from my GT-I9000 using XDA App
madfix said:
@OP: Please change the thread's title to something more respectful for RyanZA's hard work.
A good title like : "too lazy to read before doing something potentially dangerous to my expensive smartphone, I've bricked it (in fact probably not...) while trying OCLF..."
___________________________________
Sent from my GT-I9000 ××× DocRambone®'s XXJPY_Kitchen, Hardcore®'s SpeedMod K12I, ext4-all ××× using Tapatalk Pro®
Click to expand...
Click to collapse
@OP (original poster) please change the title or delete the thread.
I installed OCLF about 2 weeks ago on my new Froyo install (!!>after reading<!!) and had no problems at all. I used version 1.1 on Eclair and version 2 on Froyo. Ryanza has made a brilliant tool and does not at all deserve to be tainted like this
A ignorant noob like u dont even deserve the help! Uve read? Where?? In every instruction its writte try this at ur own risk.. I had the same problem..Didnt u read abt the 3 button combo?? Z4root and OCLF dont always work well together! AH m very annoyed cuz i really respect Ryan's work!! READ ----- READ----- then again READ--
no point flaming him too much. just report his post
all i can say is LOL
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?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
-----------------------------------------------------------------------------------------------
I'm in the Process of Reworking this post, so be warned things will change...
Also, I'm currently in the process of building the newest version of the ROM
Introducing
Project Bland Android, The successor to Bland Android. The goals of Project Bland Android, are simple. To Create three flavors of Android, Original, Cherry, and Dirty Boot (Sadly Name is now Temporarily Final). All work will remain open source, including Dirty Boot. Each Version will always be built upon the latest code base, and always attempt to update quickly. With the goal, of always being open, always being transparent, and always being helpful. This ROM is aimed to be a effort to help the community, and always have the community help others. If your not into that, this ROM will most likely not be for you.
Just like the Previous builds of Bland Android, I am not wanting to work on this all by myself the whole time, so any offers to help will not be turned down, I would love to see this working 100%, and growing, so PM me if interested, or just post in the thread, together, we can grow this ROM from more than a small project, but rather a community effort.
Introducing the Flavors:
Original Flavor, will remain Strictly AOSP, with small amounts of changes.
Cherry will become the Version that develops Somewhat rapidly, every week, there will be a vote for something to be cherry picked into Cherry, then during the next weeks vote, minor builds will be released with the goal of becoming stable by the time the next weeks cherry is integrated.
Finally, Dirty Boot, which will be the flavor that will develop at a slower pace, but with aims of always being stable. Again, code will remain open source, as long as credit is always provided. Not to mention, with enough request, support will be extended to other devices.
-----------------------------------------------------------------------------------------------
Current Android Version: 4.2.1_r1.2
Current Original Flavor: 0.0.3
Download:
-This build is tested to boot, not much more, unclear of bugs, most if not all should work, just supply your own G-APPs.
Current Cherry Flavor: 0.0.0
VOTING CLOSES FOR THIS BUILD: Feb 15th, 2013
Download:
Current Dirty Boot Flavor: 0.0.0
Download:
-----------------------------------------------------------------------------------------------
CREDITS FOR RESOURCES:
Thanks to greenblue for his easy to use source, which can be found here: on his github. or his tutorial:
here..
Kevdliu's Additional Toggles are integrated into the source, which can be found here: in this thread.
What works?
IDK yet
Whats Doesn't work?
IDK yet
Whats weird?
IDK yet
Old Versions...
ROM Build 3 is missing (hoping for a mirror)
ROM Build 2 (Missing Call Audio):
http://www.mediafire.com/download.php?bpib8jovq69xx3m
ROM Build 1 (Missing Audio and G-APPS):
http://www.mediafire.com/download.php?e352ga7jvx2sh4i
does phone volume woirk? does 4g wimax work?
r4dik4l said:
does phone volume woirk? does 4g wimax work?
Click to expand...
Click to collapse
There currently isn't any audio, period, phone volume and music volume aren't working yet though I'm hunting for the reason. And I can't test wimax (not in my area) but I added everything for wimax, so theoretically and I assume it should work.
this is my primary device, so until audio works I will not be able to test it much as soon as volume works I will test 4g wimax
r4dik4l said:
this is my primary device, so until audio works I will not be able to test it much as soon as volume works I will test 4g wimax
Click to expand...
Click to collapse
Well, I'm hunting for a fix for the audio, so hopefully soon that will be fixed.
are you able to use telephony from 4.1.2 or anything like that? I know hp420 has made a rom in the past and there are others, I wish I could help
My build has working audio. Took a while to get to it though since it keeps getting com.android.phone has stopped. Not sure if I should upload it and see if someone can find a fix.
yeah upload it, everyone helping rocks
ubnub82 said:
My build has working audio. Took a while to get to it though since it keeps getting com.android.phone has stopped. Not sure if I should upload it and see if someone can find a fix.
Click to expand...
Click to collapse
in call audio working? because thats the one thats got me stumped, I have everything else working it would appear.
budm said:
in call audio working? because thats the one thats got me stumped, I have everything else working it would appear.
Click to expand...
Click to collapse
Can't test in call audio as the phone force closing stops service.
ubnub82 said:
Can't test in call audio as the phone force closing stops service.
Click to expand...
Click to collapse
It might be worth uploading, seeing if anyone can get it going right.
The GPS is checked as if it is on, but when I try to use Google Now, it cannot register my location. Instead it gives me the option to access settings to turn on Location Services which are already on.
Sent from my Crespo4G using xda app-developers app
The Batman said:
The GPS is checked as if it is on, but when I try to use Google Now, it cannot register my location. Instead it gives me the option to access settings to turn on Location Services which are already on.
Sent from my Crespo4G using xda app-developers app
Click to expand...
Click to collapse
Did you try with Google Maps also? I was able to get a lock in maps, but that was all I tested in. Also, a logcat would be wonderful to see what is going on when this happens for you.
Google Maps attempts to lock into my location, unfortunately, both Google Maps and Google Now don't seem to be able to access GPS.
Going to see if I can get a logcat sometime today. Aldo want to check the settings to see if Google's "Gesture" keyboard is within the rom and if not whether installing a separate apk will work.
Edit: Google's Gesture keyboard is not set by default, however, I was able to install the apk separately and it works great. No logcat yet.
Also, when attempting to look at the Storage section under Settings, it FCs. This is also the case when attempting to access any 4G options for obvious reasons.
Sent from my Crespo4G using xda app-developers app
The Batman said:
Google Maps attempts to lock into my location, unfortunately, both Google Maps and Google Now don't seem to be able to access GPS.
Going to see if I can get a logcat sometime today. Aldo want to check the settings to see if Google's "Gesture" keyboard is within the rom and if not whether installing a separate apk will work.
Edit: Google's Gesture keyboard is not set by default, however, I was able to install the apk separately and it works great. No logcat yet.
Also, when attempting to look at the Storage section under Settings, it FCs. This is also the case when attempting to access any 4G options for obvious reasons.
Sent from my Crespo4G using xda app-developers app
Click to expand...
Click to collapse
Thanks for the heads up, I will add them to the OP, and please do get the logcat, and if you can get one for when the menus crash also, it might put me in the right direction.
budm said:
Thanks for the heads up, I will add them to the OP, and please do get the logcat, and if you can get one for when the menus crash also, it might put me in the right direction.
Click to expand...
Click to collapse
For some reason, I am unable to get a log cat. I keep getting the message "- waiting for device -" so I'm not exactly sure how to go about obtaining it. (FYI, I'm using a Mac).
If anyone has any tips on how or why this is not working, please feel free to let me know.
Edit: I was able to get the logcat. Do you want me to PM you with it (@budm)?
The Batman said:
For some reason, I am unable to get a log cat. I keep getting the message "- waiting for device -" so I'm not exactly sure how to go about obtaining it. (FYI, I'm using a Mac).
If anyone has any tips on how or why this is not working, please feel free to let me know.
Edit: I was able to get the logcat. Do you want me to PM you with it (@budm)?
Click to expand...
Click to collapse
Thanks for the Logcats, I'll read through them once I've had my morning coffee lol.
EDIT: Boy do I feel stupid. I forgot to include a few things, it should fix most your issues with the Google Now, and Maps.
Awesome. Just let me know if and when you want me to test out the new build. Unless of course you just post it in the OP.
Thanks for getting this rom together btw.
Edit: any way that you could cook the new Gmail apk into the rom? Also, I've been having Superuser issues. The rom doesn't allow for applications to obtain root access.
Sent from my Crespo4G using xda app-developers app
The Batman said:
Awesome. Just let me know if and when you want me to test out the new build. Unless of course you just post it in the OP.
Thanks for getting this rom together btw.
Edit: any way that you could cook the new Gmail apk into the rom? Also, I've been having Superuser issues. The rom doesn't allow for applications to obtain root access.
Sent from my Crespo4G using xda app-developers app
Click to expand...
Click to collapse
I'll be adding it to the OP once I fix/try to fix the settings stuff. and I just added the new Gmail ( I think, I'll double check this though) and I'll provide the SuperUser Zip for any issues. All in all, should be up in about 1 to 4 hours after I finish some things around my house.
is this ROM pretty stable? I am looking forward to flashing this but I know its a pretty new ROM and my phone has been acting funny and dont want to chance screwing it up!!
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.3 (Jelly Bean), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Instructions
First time flashing CyanogenMod 10.2 your device, or coming from another ROM?
Download the zip(s).
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe data & cache partitions of your device
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Useful Links
BBQLog changelog
Odin CyanogenMod wiki
Jira issue tracker
DO NOT REPORT BUGS FOR UNOFFICIAL BUILDS!
Other Issues?
Use this for obtaining logs.
These are unofficial beta builds so bug reports are not accepted. You are relying on yourself and your peers in this thread for support!
Download Links
CyanogenMod:
Builds: http://goo.im/devs/mithun46/CM4.3
Google apps addon:
Download: 4.3 Google Apps
Root access:
Go to Developer options --> Root Access
And change to "Apps and ADB" to fix root
Screenshots: 1, 2 & 3
Thanks to:
CyanogenMod: Thanks a lot! You guys are awesome!!
@jug6ernaut : For being a awesome friend! Thanks man!
Reserved
Sweet! Downloading now!
If I'm on stock rom, Do I just follow the OP instruction?
motoxxxx said:
If I'm on stock rom, Do I just follow the OP instruction?
Click to expand...
Click to collapse
Pretty much. Do you already have a recovery installed? You need to have an unlocked bootloader as well.
havanahjoe said:
Pretty much. Do you already have a recovery installed? You need to have an unlocked bootloader as well.
Click to expand...
Click to collapse
Thank! now I need to unlocked my bootloader.
How is the rom?
motoxxxx said:
Thank! now I need to unlocked my bootloader.
How is the rom?
Click to expand...
Click to collapse
I just installed it, looks good so far. Forgot to flash the superSU zip so I don't have root yet. Trying to figure out how to get into recovery after flashing.
If you are going to be restoring a Titanium Backup, there is a known issue on 4.3 where you have to change the backup folder location.
From the Nexus 4 thread:
Titanium Backup > Menu > Preferences > Backup Folder Location > DETECT > Whole Device > Select /storage/emulated/legacy/titaniumbackup and click yes when prompted to move backup files.
Click to expand...
Click to collapse
Looks like it works without doing that last step.
And in case you are trying to get into recovery, reboot and when you see the LED flash orange, hold the volume down button. Thanks mithun for the help
havanahjoe said:
I just installed it, looks good so far. Forgot to flash the superSU zip so I don't have root yet. Trying to figure out how to get into recovery after flashing.
If you are going to be restoring a Titanium Backup, there is a known issue on 4.3 where you have to change the backup folder location.
From the Nexus 4 thread:
Click to expand...
Click to collapse
Three otpions
1. Reboot phone, press volume down when you see the notification led go orange.
2. Advance reboot menu
3. From adb "adb reboot recovery"
jug6ernaut said:
Three otpions
1. Reboot phone, press volume down when you see the notification led go orange.
2. Advance reboot menu
3. From adb "adb reboot recovery"
Click to expand...
Click to collapse
Thanks jug6ernaut. Advanced reboot menu is not enabled by default. I had to look up where to enable it:
Enable developer options. (go to about phone, scroll to the bottom, find the “build number” field, click on it seven times and it will turn on developer options.)
go back one level to the main settings screen and you’ll see developer options now. Open that, Enable advanced reboot options by clicking on the relevant checkbox
Click to expand...
Click to collapse
havanahjoe said:
Thanks jug6ernaut. Advanced reboot menu is not enabled by default. I had to look up where to enable it:
Click to expand...
Click to collapse
True , which are under developer options for anyone wondering!
Small update for anyone who saw my "issue list" in the other CM thread. Almost all of my issues were caused by using the wrong gapps(was unaware there was a 4.3 version).
Im up on 4.3 again and its working beautifully , still few performance and graphical issues, but they are minor.
Edit: Cant get SMS to send, guessing this has to do with the Voice+ addition as MMS send fine. Can also receive MMS and SMS fine, just cant send SMS.
jug6ernaut said:
True , which are under developer options for anyone wondering!
Small update for anyone who saw my "issue list" in the other CM thread. Almost all of my issues were caused by using the wrong gapps(was unaware there was a 4.3 version).
Im up on 4.3 again and its working beautifully , still few performance and graphical issues, but they are minor.
Edit: Cant get SMS to send, guessing this has to do with the Voice+ addition as MMS send fine. Can also receive MMS and SMS fine, just cant send SMS.
Click to expand...
Click to collapse
Hmm I am running into the same issue with SMS, can't send.
I don't see the group MMS option in the stock messaging app. The Nexus 4 has it, so is this not the same Messaging app as the Nexus?
havanahjoe said:
Hmm I am running into the same issue with SMS, can't send.
I don't see the group MMS option in the stock messaging app. The Nexus 4 has it, so is this not the same Messaging app as the Nexus?
Click to expand...
Click to collapse
idk if this is an issue with CM for the ZL or what. Or if its my sim card. Plain and simple IDK.
BUT for me this is caused by my sim not having my phone number, the messaging app will not show the group messaging option if it does not know your number. To check this go to you phone settings/About Phone/Status/Phone number. Mine would show "UNKNOWN". To fix this after every flash i have to run a program called "Sim Number Changer", its an Xpoxed app. It worked for me.
jug6ernaut said:
idk if this is an issue with CM for the ZL or what. Or if its my sim card. Plain and simple IDK.
BUT for me this is caused by my sim not having my phone number, the messaging app will not show the group messaging option if it does not know your number. To check this go to you phone settings/About Phone/Status/Phone number. Mine would show "UNKNOWN". To fix this after every flash i have to run a program called "Sim Number Changer", its an Xpoxed app. It worked for me.
Click to expand...
Click to collapse
Ah yes. I had noticed that in my status page before, but didn't know it broke the Group MMS option. I'll use the Sim Number Changer.
I asked in the Z thread to see if they are having issues with SMS too.
EDIT: Sim Number Changer FCs on me
The Z users are able to send SMS, but they mentioned the HTC One had the problem. I looked in their threads and it's apparently gone in a new build.
I did a logcat and didn't see any errors when sending a message, other than chompsms telling me the message failed (and this I already had seen on the phone). The error message doesn't explain why.
---------- Post added at 05:16 PM ---------- Previous post was at 04:34 PM ----------
I don't like my phone showing up as a 6503 A quick build.prop edit fixes that.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
havanahjoe said:
The Z users are able to send SMS, but they mentioned the HTC One had the problem. I looked in their threads and it's apparently gone in a new build.
I did a logcat and didn't see any errors when sending a message, other than chompsms telling me the message failed (and this I already had seen on the phone). The error message doesn't explain why.
---------- Post added at 05:16 PM ---------- Previous post was at 04:34 PM ----------
I don't like my phone showing up as a 6503 A quick build.prop edit fixes that.
Click to expand...
Click to collapse
Haha nice!
Sent from my Nexus 7 using Tapatalk 2
jug6ernaut said:
Haha nice!
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
A little off topic, do you have the new Nexus 7?
havanahjoe said:
A little off topic, do you have the new Nexus 7?
Click to expand...
Click to collapse
I do .
jug6ernaut said:
I do .
Click to expand...
Click to collapse
The million dollar question is... Is it worth the upgrade from the original 7?
havanahjoe said:
The million dollar question is... Is it worth the upgrade from the original 7?
Click to expand...
Click to collapse
Tough question. I sold my original nexus 7 few months back in preparation for the new one. So for me its 100% worth it lol. Kind of hard for me to judge it the old model BC I don't have them side by side.
Buy I will say this thing is FAST. Screen is amazing, absolutely love it. Was thinking I would hate the space above/below the screen, don't mind it. Definitely thinner tho, its noticeable, also smaller side bezel is nice. One thing not getting a lot of attention is the speakers are definitely a step up from the original which were just poor.
Really the big thing for me is the screen, it really is a big improvement. Absolutely beautiful.
Is it worth it? Who knows, I say yes. I mean at the price it was hard to say no. If you have the original and your happy with it the new one isn't going to be anything ground breaking. But if you have the cash, it is a worthy upgrade.
Sent from my Nexus 7 using Tapatalk 2
jug6ernaut said:
Tough question. I sold my original nexus 7 few months back in preparation for the new one. So for me its 100% worth it lol. Kind of hard for me to judge it the old model BC I don't have them side by side.
Buy I will say this thing is FAST. Screen is amazing, absolutely love it. Was thinking I would hate the space above/below the screen, don't mind it. Definitely thinner tho, its noticeable, also smaller side bezel is nice. One thing not getting a lot of attention is the speakers are definitely a step up from the original which were just poor.
Really the big thing for me is the screen, it really is a big improvement. Absolutely beautiful.
Is it worth it? Who knows, I say yes. I mean at the price it was hard to say no. If you have the original and your happy with it the new one isn't going to be anything ground breaking. But if you have the cash, it is a worthy upgrade.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the quick review. I really don't have a lot of use for a tablet myself, I have my laptop with me almost all the time and I don't mind carrying it (even though it's a 17" MBP), but I have been considering using a Nexus 7 as Nav/Media in the car. I've seen several people with a Subaru Legacy do it on theirs and it seems to fit very well. In that case the screen wouldn't really matter that much and doing a quick search on craigslist I found a 16 GB for $100. With what you said, it seems like a no brainer to get the first gen.
Apologies for the off topic discussion. To bring it back to CM, I am currently building a copy myself. Thanks to mithun I got my Ubuntu VM ready for compiling and it's CCing away.
Just to qualify, I don't give two ****s about tripping knox, I just want this stupid broken "update" off my god damned phone that I PURCHASED and OWN. I have searched and read for hours, and I have not seen a single thing about downgrading the boot loader or the OS successfully, except for the falsely titled (and should be deleted as it's #1 in google) link here.
Someone please tell me there's a way to do this? I despise this update.
jmorgali said:
Just to qualify, I don't give two ****s about tripping knox, I just want this stupid broken "update" off my god damned phone that I PURCHASED and OWN. I have searched and read for hours, and I have not seen a single thing about downgrading the boot loader or the OS successfully, except for the falsely titled (and should be deleted as it's #1 in google) link here.
Someone please tell me there's a way to do this? I despise this update.
Click to expand...
Click to collapse
Ok so i'm guess you just purchased your Note 3 and it came with Kit Kat on it already? You say broken update? Can you please specify what is "BROKEN" about it. If you do not have the Knox issue that others have, then simply root your phone and run a custom rom. I assure you, whatever you think is broken with the phone will be fixed this way. Also read thru the update FAQ's and go thru the development thread for any issues you may have. Use the search box in the top right corner of any thread to look for a particular problem.
dragonstalker said:
Ok so i'm guess you just purchased your Note 3 and it came with Kit Kat on it already? You say broken update? Can you please specify what is "BROKEN" about it. If you do not have the Knox issue that others have, then simply root your phone and run a custom rom. I assure you, whatever you think is broken with the phone will be fixed this way. Also read thru the update FAQ's and go thru the development thread for any issues you may have. Use the search box in the top right corner of any thread to look for a particular problem.
Click to expand...
Click to collapse
My note 3 came with jellybean. I use a phone recording app to record all my calls. I also constantly move files between the sd card and the internal memory. Both of these things have broken since the update to kitkat. I would be happy to root my phone and go back to an earlier rom. Can you point me to a jellybean rom for t-mobile?
jmorgali said:
My note 3 came with jellybean. I use a phone recording app to record all my calls. I also constantly move files between the sd card and the internal memory. Both of these things have broken since the update to kitkat. I would be happy to root my phone and go back to an earlier rom. Can you point me to a jellybean rom for t-mobile?
Click to expand...
Click to collapse
Ok, I would like for you to read before posting in the future please.
1. Call recording was never a feature standard on TMO as it's illegal. It's a third party app that you can easily replace, just need the kit kat version.
2. The Sdcard R/W issue is not something that is "BROKEN" it is a standard feature on TW and Kit Kat, it makes the phone only write to the internal storage and you can only Read from the ExtSdcard. This was done because people buy $5 sdcards on Amazon then blame Android and their phones when performance sucks. This also has been discussed in-depth across XDA and every Android website known. In the developer section you will find all your answers. You just need to search and read.
dragonstalker said:
Ok, I would like for you to read before posting in the future please.
1. Call recording was never a feature standard on TMO as it's illegal. It's a third party app that you can easily replace, just need the kit kat version.
2. The Sdcard R/W issue is not something that is "BROKEN" it is a standard feature on TW and Kit Kat, it makes the phone only write to the internal storage and you can only Read from the ExtSdcard. This was done because people buy $5 sdcards on Amazon then blame Android and their phones when performance sucks. This also has been discussed in-depth across XDA and every Android website known. In the developer section you will find all your answers. You just need to search and read.
Click to expand...
Click to collapse
To expand on #2 it was also done to prevent 3rd party apps from writing to the entire SD Card in a major security issue.
Google made this change about 2 years ago and finally started to enforce it.
Also I don't know if you will have compatibility issues with going back to 4.3 while having a (unchangeable) 4.4.2 Boot loader. Its worth a shot though. But as the other poster mentioned if you root 4.4.2 you can get the SD Card RW back without having to go to 4.3
Sent from my SM-N900T using Tapatalk
I agree with OP, this KitKat update has totally soured me on the Note 3. I used to adore my battery life; now I despise it. I also used a call recorder app that no longer works on KitKat. These are only a couple of the numerous issues I've had with the update. I'd gladly downgrade if I could.
---------- Post added at 09:10 AM ---------- Previous post was at 09:05 AM ----------
dragonstalker said:
Ok, I would like for you to read before posting in the future please.
1. Call recording was never a feature standard on TMO as it's illegal.
Click to expand...
Click to collapse
Call recording is legal in many, many areas including where I live. Your statement is ignorant. I would like for you to read before posting in the future please.
hfuizo said:
I agree with OP, this KitKat update has totally soured me on the Note 3. I used to adore my battery life; now I despise it. I also used a call recorder app that no longer works on KitKat. These are only a couple of the numerous issues I've had with the update. I'd gladly downgrade if I could.
---------- Post added at 09:10 AM ---------- Previous post was at 09:05 AM ----------
Call recording is legal in many, many areas including where I live. Your statement is ignorant. I would like for you to read before posting in the future please.
Click to expand...
Click to collapse
Only in 12 States are not one party consent consider legal and admissable in court, But recording somebody phone calls without their knowledge is illegal and will get you sued. If you don't know what you are talking about. Please don't chime in.
Please don't try to challenge and confuse users. This is the exact reason the app is not standard on phones.
Accepted forms of notification for recording by a telephone company
The FCC defines accepted forms of notification for telephone recording by telephone companies as:
Prior verbal (oral) or written notification of all parties to the telephone conversation.
Verbal (oral) notification before the recording is made. This is the most commonly used type.
An audible beep tone repeated at regular intervals during the call.
dragonstalker said:
Ok, I would like for you to read before posting in the future please.
Click to expand...
Click to collapse
dragonstalker said:
Please don't chime in.
Click to expand...
Click to collapse
You are a condescending little twit. Not to mention the fact you are the one who posted incorrect information. I'm done with you.
hfuizo said:
You are a condescending little twit. Not to mention the fact you are the one who posted incorrect information. I'm done with you.
Click to expand...
Click to collapse
I'm sorry, that would be very knowledgable old twit, that just retired after 20 years of communication background on secured system. Information Security is kinda my job. Nothing i said was incorrect, and my statement stands, if your on XDA and you refuse to READ before posting, expect what your mind considers condescending .
As far recording being illegal goes, I'd love to hear the Aristotelian logic behind that. What's practical about recording being illegal?
But the other issue, downgrading, I don't understand why you can't just go to sammobile.com, get the old firmware and flash that honey.
I believe of you try to flash a 4.3 Rom or image with the 4.4 boot loader it will just fail the check and won't flash at least it was like that on a different t phone I had.
Sent from my Nexus 7 using Tapatalk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've gotta troubleshoot this. I hate kitkat
Sent from my SM-N900T using Tapatalk
hello all. I am also having problems with my TMO Note3. Since the 4.4.2 update the data has been flaky. I did couple of factory reset and did not help. before the update the device worked flawless. It would be great if we could go back to 4.3 til a patch is out to fix all the problems..
No problems with 4.4.2 at all. Stock rooted with a little bloat removed.
Sent from my SM-N900T using xda app-developers app
same here after the 4.4.2 update, the modem is much better, better signal that is for sure... no problems at all..
Nellyinda803 said:
I've gotta troubleshoot this. I hate kitkat
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
I only get a few hours screen time too but my battery will last 2 to 3 days. Wierd.
What aggravates me most is my battery monitor apps wont work cause im not rooted. They must not want us to know what the hell they're really running.
dragonstalker said:
Only in 12 States are not one party consent consider legal and admissable in court, But recording somebody phone calls without their knowledge is illegal and will get you sued. If you don't know what you are talking about. Please don't chime in.
Please don't try to challenge and confuse users. This is the exact reason the app is not standard on phones.
Click to expand...
Click to collapse
This is silly... Just because something can be used illegally does not make it illegal to use. If you notify as required by your State, it is not a problem and a very useful tool. BTW I am in one of those single party States, but Inform the other party on all calls if I will be using it.
herach said:
hello all. I am also having problems with my TMO Note3. Since the 4.4.2 update the data has been flaky. I did couple of factory reset and did not help. before the update the device worked flawless. It would be great if we could go back to 4.3 til a patch is out to fix all the problems..
Click to expand...
Click to collapse
Once you do the OTA, there is not going back without rooting apparently.
krelvinaz said:
This is silly... Just because something can be used illegally does not make it illegal to use. If you notify as required by your State, it is not a problem and a very useful tool. BTW I am in one of those single party States, but Inform the other party on all calls if I will be using it.
Click to expand...
Click to collapse
Well, that's up to the court. I, for one, will not record phone calls, even asking the other party. Actually, I am puzzled: in what situation will you need to record the call?
I mean, seriously, when on a call with your friend, company, boss or coworkers, do you TELL them you are recording the call? That just creates conflict.
I can say after 2 weeks this update is atrocious. Random reboots happen daily and several times at that. After deleting all Knox apks and odex files it still will appear Unfortunately Samsung Knox has stopped, if I'm on the market and every time I turn on the phone. Battery Life is better but not worth this mess. Network issues with tmobile but not on ATT. I have a s4 on tmobile it has no issues only my note 3. 4.3 is more stable and more reliable.
Sent from my SM-N900T using Tapatalk