I thought there might be a way to do it with xposed but I didn't know of the module. Thanks, I'll check out app settings.
Sent from my SGH-T999 using xda app-developers app
Sent from my SGH-T999 using xda app-developers app
[ROM][AOSP][Linaro]CarbonRom Nightlies/Releases [d2tmo]
- Thread starter dg4prez
- Start date
-
- Tags
- development
- Status
So I tried the gesture unlock feature and can't draw my gesture precisely enough so I can't unlock my phone. When I do forgot pattern/gesture and login with my Google account it takes me to the security section in the settings and tells me to enter my gesture in order to change it..
Is there a way to bypass it without wiping the system and reflashing?
Fixed it.. in case others were wondering after I unlocked it using my Google account I ignored when it asked me to re-enter my gesture and went to a root explorer app went to /data/system and deleted the gesture key.
Is there a way to bypass it without wiping the system and reflashing?
Fixed it.. in case others were wondering after I unlocked it using my Google account I ignored when it asked me to re-enter my gesture and went to a root explorer app went to /data/system and deleted the gesture key.
Last edited:
Did you find a fix? I have the same problem, looks really weird... I remember on Rootbox that feature did not do that, the lockscreen wallpaper went all the way at the top.
Which GAPPS should I use for the latest nightly and which Jelly Bean does the nightly use, 4.3?
Yes
Sent from my SGH-T999 using Tapatalk
Just to be sure. I'm coming from an older nightly build of this rom. If i want to update to the latest nightly, i just have to wipe cache and dalvik cache correct? No need to do a full wipe?
No I didn't find a fix. I just use the same wallpaper for the lockscreen as I do for the home screen.
Posted this on G+ wanted to post here just in case
Throwing this out there to see if anyone has experienced the similar issue. Running the 11/11 nightly for the d2tmo. Coming from the 4.2.2 final, clean flashed. I'm seeing 2 issues wondering if anyone can let me know if this is a nightly issue or something else...
1: on a PIN lockscreen, the lock symbol doesn't activate to bring up the PIN prompt. It's almost as if the screen target area 1-2cm across the bottom doesn't register touches BUT if I slide the lockscreen either right or left more toward the center of the screen, the lock symbol then registers touch
2: Notifications on various apps (built-in Messaging app, E-Mail, Gmail, Touchdown and others) do not notify. At first I thought I might have been custom sounds but even if I switch to built-in tones, none go off when receiving a notification. I don't think it's isolated to the built-in apps only, I've seen it 3rd party apps as well (Hangouts, Touchdown, Handcent, etc) and yes I do have the volume turned up.
Throwing this out there to see if anyone has experienced the similar issue. Running the 11/11 nightly for the d2tmo. Coming from the 4.2.2 final, clean flashed. I'm seeing 2 issues wondering if anyone can let me know if this is a nightly issue or something else...
1: on a PIN lockscreen, the lock symbol doesn't activate to bring up the PIN prompt. It's almost as if the screen target area 1-2cm across the bottom doesn't register touches BUT if I slide the lockscreen either right or left more toward the center of the screen, the lock symbol then registers touch
2: Notifications on various apps (built-in Messaging app, E-Mail, Gmail, Touchdown and others) do not notify. At first I thought I might have been custom sounds but even if I switch to built-in tones, none go off when receiving a notification. I don't think it's isolated to the built-in apps only, I've seen it 3rd party apps as well (Hangouts, Touchdown, Handcent, etc) and yes I do have the volume turned up.
B
Bass_Man25
Guest
Has anybody tried this ROM with Bluetooth? One of the biggest problems I have with 4.4.2 ROMs is that Bluetooth connectivity is very shaky. I'll have it connect to my car or xlink but then it either disconnects later on or the phone won't wake up to make the call (sometimes, even if I do wake up the phone it still doesn't work). I know Kit Kat ROMs are in the Development stage and I like what I see but, since I live on the road and BT is a must for me, I'm having to go back to 4.3 because of it.
I have tried CM11, SlimKat, LiquidSmooth KK, Cyan Fox, and Gummy. I've tried with stock kernel, dkp, ktoonz, BMS and Harkness. None of them are working right now. Any input would be greatly appreciated.
Thanks in advance.
I have tried CM11, SlimKat, LiquidSmooth KK, Cyan Fox, and Gummy. I've tried with stock kernel, dkp, ktoonz, BMS and Harkness. None of them are working right now. Any input would be greatly appreciated.
Thanks in advance.
Hello everyone, please join the new official thread here:
http://xdaforums.com/showthread.php?t=2634655
http://xdaforums.com/showthread.php?t=2634655
- Status
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
43About Carbon
CarbonRom is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look at, build, and use our code on CarbonDev GitHub.
We would like to thank CyanogenMod for their device trees, framework/settings mods and their code that was incorporated into this project. We also extend our gratitude to the devs whose code that we have incorporated. Proper authorship has been maintained and can be viewed on our repository.
Special thanks also go to Slim Rom for some of their features, PA, AOKP, and anyone else we may have borrowed commits from that hasn't been mentioned here. If you feel you have been unfairly left out, please - let us know.
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! If you have questions, ask your fellow users or ask us in #teamcarbon on freenode IRC.
Features
Simply stated, we can't really list features here. There are too many and they change too frequently, and we now support a truly insane number of devices. Chances are, if you like a feature, we have it already. Seriously.
Screenshots
Carbon Updates
Join us on these Social Media Channels to keep yourself up-to-date on all the latest Carbon news, updates, contests, and more! Join our completely open Google+ community for insider conversation with devs and other users.
Download Carbon
All Carbon downloads and further information such as features, changelog, and FAQ can be found on our goo.im page.
Both nightly and release builds are available. Please note that nightlies are for development purposes. This means that they may not work properly, may not flash, may not build for days at a time, and will probably eat your cat. If you flash these, know what you're doing, have backups, and don't complain when something happens. It's on you!
http://carbon-rom.com
Changelog
For a detailed changelog, check out the changes made each night here:
Change Log
You can also find a changelog in Settings->Carbon->About Carbon
Support
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our goo.im page linked above. It's new, but expanding fast. Just like us!
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Join our G+ Community: http://community.carbon-rom.com This is where we spend the bulk of our time and the best way to reach us and other community members. We update and frequent this community far more than XDA, simply due to time constraints and the convenience of G+.
5) Ask a question on our IRC channel. Connect to #teamcarbon on irc.freenode.net or click here. You'll find several other Carbon fans and usually one or more devs as well. Please be polite.
Who is Team Carbon?
Andros11
BigShotRob
Bionic Beast
dg4prez
Kejar31
mattmanwrx
morfic
nocoast
pixeldotz
slick_rick
winner00
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
9Hey everybody! So we decided to make an actual CarbonDev account and post useful information about the rom through this account instead of our personal accounts, you know, so we seem professional and whatnot.We are also in the process of changing the OP's to this account so they don't say 1.6 anymore lol. We have contacted xda and are waiting for that to get done, all in good time. We hope this change will make everything a bit easier for you, our precious users, but also for us in a logistical sense. We try to do everything possible to make Carbon user friendly and to meet the needs of the majority and hopefully this will help us maintain that goal. Anyways, back to work! Peace.55Try changing the ro.ril.hsxpa=1 to ----> ro.ril.hsxpa=3. Should help.
I'm not running this atm but if like previous "Liquid" ROMs, you might be able to do it in the settings without doing it manually. I prefer myself to do it manually via Root Explorer, but that is me.
If you do decide to do it via File Explorer, don't forget to hit Save after your edit or it won't change. People tend to forget that part a lot.
