Database Develop

Cyan 5.0.5.3 - Battery Percentage suddenly broken?

Pretty much says it all, the battery percent that was working several hours ago is suddenly not working. I have not changed anything since this time, and luckily I do have a nandroid backup. My question is, does anyone know what the hell broke this in the first place? Does anyone else have a similar experience with this function randomly breaking? I've checked/unchecked the option in Spare Parts but that doesn't fix it.
Waiting to see if the nandroid I did was before this feature was broken. Not sure yet, but I don't know what info I need to be helpful either....
EDIT: restoring the nandroid I had on the device did fix this problem. I'm still not positive what broke it, which is what I'm really curious about. I don't wanna have to make backups at every little change just so I can preserve battery percentage lol.

isn't it an option in settings for 5.0.5.3?
could you have possibly changed it? also what do you mean by 'not working'

Do you think it is broken because it is fully charged and no number? The off set of the numbers doesn't let it show 100%. This issue should be fixed in the next release.

isn't it an option in settings for 5.0.5.3?
could you have possibly changed it? also what do you mean by 'not working'
Click to expand...
Click to collapse
Didn't change it, in fact I said that I hadn't changed anything settings-wise and checked the bit in Spare Parts for this issue.
Do you think it is broken because it is fully charged and no number? The off set of the numbers doesn't let it show 100%. This issue should be fixed in the next release.
Click to expand...
Click to collapse
The way all that's been working for me is that a full charge will show "99" when I pull it off of the charger (verified at 100% by Spare Parts and by the lock screen saying "Charged."
I figured out a possible way to keep this working; couldn't I just pull services.jar off of the device, and if it seems to break just push it back then reboot?

Editing build.prop made my phone not fully reboot?

Original thread in General: http://forum.xda-developers.com/showthread.php?t=2992447 (Tethering/Portable Hotspot on Verizon w/o root)
I followed some instructions in that thread to edit the build.prop file and add the following line at the bottom: "net.tethering.noprovisioning=true". We should then reboot for the change to take effect.
My problem is that even though my phone appears to shut down and power back on like normal, the phone is not actually rebooting. I say this because the same apps will still be open even after powering the phone back on. Every time.
Anyone know why this might be happening?

I have noticed The recents cards stay even with a reboot.

LeonDX82 said:
I have noticed The recents cards stay even with a reboot.
Click to expand...
Click to collapse
Thanks. I was pretty damn positive that the recent cards didn't stay after rebooting, but I guess I was wrong? Maybe this was different in 5.0.1? It was also weird that the build.prop edit didn't have any effect either.

Toaplan said:
Thanks. I was pretty damn positive that the recent cards didn't stay after rebooting, but I guess I was wrong? Maybe this was different in 5.0.1? It was also weird that the build.prop edit didn't have any effect either.
Click to expand...
Click to collapse
my galaxy nexus cards stay also on cm5.0.2

Thanks. I feel kind of stupid now.

Yes cards stay and you have to edit the sqldatabase as well

[Q&A] [Sprint/Boost/Virgin] DragonRom by Team YAR

Q&A for [Sprint/Boost/Virgin] DragonRom by Team YAR
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Sprint/Boost/Virgin] DragonRom by Team YAR. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

I can't even download it because boost mobile rely throttles your data speed down once you hit your high speed limit for the month ?

Ubiquitous_22 said:
I can't even download it because boost mobile rely throttles your data speed down once you hit your high speed limit for the month ?
Click to expand...
Click to collapse
Sorry. We've removed as much as we can and we still have the smallest ROM that I'm aware of.

Great Job Team YAR
Ok since i am new it wont let me post to the forums But instead go into the q/a.. So team YAR Firstly i just want to say great work on the rom however i few have few concerns and such.... Hangouts is great for sms however some people like the stock sms anyway to reimpliment that in case of someone not wanting to use hangouts as default as that is the only sms that is implemented in the rom. Also battery life is ok not a lot of things to bog it down however for some reason when your in the 3g vs 4g lte battery drain is hell. Is that a common issue when you have a 4g lte phone? Also i took a look through the build prop when i found out this rom has zero tethering capabilities. I turned the values on the build prop to reflect that tething is all in fact on however it does not allow tethering it stays greyed out. I could tether without an issue before this rom using Raptop rom. Im not calling any rom better i feel it is a based on taste decision. But i would like your rom 100% better if it included tethering. Also with this phone and i dont know if it falls the same for all boost variants but the hotspot feature has to do a subscription check to see if you actually paid for a monthly subscription. I did a little digging on the stock rom and found how to bypass it and tether without an issue. But could you please for the sake of other people include tethering with or without a bypass either native or a working 3rd party app. Also is there a way to make more space up because htc and boost did a real job on leaving little to no space and even with links2sd dont clear much up. Could removing some of the launchers help resolve the space issue?..... Sorry for the novel just my concerns

Having issue booting into rom, stuck at HTC also. :0(

originaleq said:
Having issue booting into rom, stuck at HTC also. :0(
Click to expand...
Click to collapse
Try pulling the battery. When I get hung up like that sometimes, pulling it usually does the trick. Worth a try. Let us know.

Oh yeh, was coming from RaptorRom v2. Cant get voicemail notifications with it and no visual voicemail so hoping to get on DragonRom. Yeh I have to do battery pull when the HTC screen freezes cause the power won't shut off at that point even when held down. The zip says it flashes and installs SUCESSFULLY, so I don't get it.

originaleq said:
Oh yeh, was coming from RaptorRom v2. Cant get voicemail notifications with it and no visual voicemail so hoping to get on DragonRom. Yeh I have to do battery pull when the HTC screen freezes cause the power won't shut off at that point even when held down. The zip says it flashes and installs SUCESSFULLY, so I don't get it.
Click to expand...
Click to collapse
Sometimes I have to do a "factory reset/wipe" like 3-4 times and then flash the ROM again. Usually, if all is good and I am installing the right thing, doing the right things etc, if boots up eventually. I know it can be a pain in the As* and it gets very frustrating at times, but usually it'll eventually work. Good luck man!!!

Well i dont guess im going to get a reply to my question lol

SheetzNGiggles said:
Well i dont guess im going to get a reply to my question lol
Click to expand...
Click to collapse
We didn't implement native tethering at this time. I'm sure its a function well include in a future version.
Per the space issue, Minimalist has literally just about everything we could remove, removed, if we find more things to remove, we will continue to do so. We are already planning our next release, unfortunately there is no eta currently.
As per Hangouts. I think the reason @dragonhart6505 included it is because it functions both as SMS and Hangouts. It's killing two birds with one stone for those that use Hangouts. As always, you can remove anything you deem unnecessary and replace it with your preferred app. I'm not at my computer, but if I remember correctly it is located in /system/app so you'll have to use Titanium to remove it. The kernel is pre-rooted and the write protection is disabled.

SheetzNGiggles said:
Well i dont guess im going to get a reply to my question lol
Click to expand...
Click to collapse
Native tethering has not been enabled as of yet, but we will work on including it. I use PDANet to tether via USB and Bluetooth, but its WiFi function does not work on our device. We'll get tethering resolved in a near update.
As @dip_spit said, we removed as much as possible while staying sure everything worked as it should. I am currently tearing through the entire system to find what cam be removed and what should stay. Minimalist is perfect if space is a concern, however you wont get much more than ~1gb on a stock based rom.
---------- Post added at 07:59 PM ---------- Previous post was at 07:54 PM ----------
originaleq said:
Oh yeh, was coming from RaptorRom v2. Cant get voicemail notifications with it and no visual voicemail so hoping to get on DragonRom. Yeh I have to do battery pull when the HTC screen freezes cause the power won't shut off at that point even when held down. The zip says it flashes and installs SUCESSFULLY, so I don't get it.
Click to expand...
Click to collapse
We recommend flashing from a Stock TWRP backup and factory reset as other roms appear to be conflicting with the permissions needed by a stock-based rom.
We apologize for the inconvenience and we are working on making DragonRom a fully flashable, self-sustained rom that requires no such system to be installed prior to flashing. It is alot of work getting the permissions necessary for this, so please bare with us.
Ive been late to the thread here as i was unaware it existed. Ive now subbed to the thread and will monitor it frequently

Ty
Thank you i was just wondering spacewise if links to sd would clear much more space if i was flashing minimalist rom and building from there? Also as for the tethering i hope its in your future release because i do tether alot lol and i cant always make use of bluetooth tether. But great job never the less im looking forward to testing anything new. Also i have a stock roms from any carrier as well as build.prop from any said carrier if needed.

first time poster
1st off... absolutely love this rom. I've been running the minimal rom for over a week, almost as soon as it was posted. Most storage space I've had yet on my phone! Any problems I had with initial install have easily been dealt with. The one problem I had from from the install was google play not working, would crash as soon as launched. Was solved by sending new version from my computer to install on phone. After my friend saw the rom, we tried to install the featured rom on his phone which got stuck on the HTC boot screen. This problem was solved by installing the stock backup from this site then installing the rom again. But again we love this rom, Thanks Team YAR!!!

Does DragonROM currently support Link2SD's mount scripts at boot for other filesystems than FAT? Also, how risky would it be to try Xposed at this stage of development?

kranao8472 said:
Does DragonROM currently support Link2SD's mount scripts at boot for other filesystems than FAT? Also, how risky would it be to try Xposed at this stage of development?
Click to expand...
Click to collapse
Xposed works pretty well for everyone who everyone who has installed. Remember to make TWRP backups before you install anything.

Front Facing Camera
**Ok I did a search from camera on this particular thread and nothing popped up, so sorry if someones already covered this but....
Has anyone tested the front facing camera on this mod? I need my selfies brah. Nah! but would be nice to have this back! Yo! My camera? Sweet innocent camera --never hurt anyone.

I think I screwed myself.
I think I really got a BRICK here. Ok, I did something stupid. I flashed the HBOOT trying to get the S-OFF but failed. All I got not is HBOOT and under that it says checking.,... overlaying the word checking are the words Press <POWER> to reboot. And that is it. If I try to boot regularly is hangs on the HTC Logo. Did I just really brick my phone for life???
FYI, device is NOT found using adb or fastboot. Interesting this though, when I did have the nonsense rom up and had this HBOOT issue, I could boot regularly and use flashify to boot into recover. So recover is there I just have NO way of getting to it now. Every since I flash with Dragon, no offence, cause dragon is hanging on me at the HTC Logo. AAAAHHHHHHHUUUGHHH. I just broke my phone, I think.

BadRx said:
I think I really got a BRICK here. Ok, I did something stupid. I flashed the HBOOT trying to get the S-OFF but failed. All I got not is HBOOT and under that it says checking.,... overlaying the word checking are the words Press <POWER> to reboot. And that is it. If I try to boot regularly is hangs on the HTC Logo. Did I just really brick my phone for life???
FYI, device is NOT found using adb or fastboot. Interesting this though, when I did have the nonsense rom up and had this HBOOT issue, I could boot regularly and use flashify to boot into recover. So recover is there I just have NO way of getting to it now. Every since I flash with Dragon, no offence, cause dragon is hanging on me at the HTC Logo. AAAAHHHHHHHUUUGHHH. I just broke my phone, I think.
Click to expand...
Click to collapse
Unfortunately, I think you did.
Have you tried pulling the battery and then after you put it back in hold the volume down button and then press the power button until it comes on to see if you can get into your recovery application?

MrMike2182 said:
Unfortunately, I think you did.
Have you tried pulling the battery and then after you put it back in hold the volume down button and then press the power button until it comes on to see if you can get into your recovery application?
Click to expand...
Click to collapse
WAIT! I'm back in baby!!!! HOOOOLLLLIYYYY MOLE' Apparently the HBOOT IMG was in the form of a zip files that was placed in the root of the SD CARD. As I go into HBOOT, bootloader is trying to upgrade to this zip file.. Once I took the SD Card out, bouya! HBOOT is back. What a scare that was. Still having issues booting into the new flash rom, however. I think i'm done for today though... i'm hanging up the hat for the day.

My phone is stuck on the HTC screen after installing DragonRom through the TWRP. I followed all of the directions. I'm on VM.

[Q] Xposed repository is empty

Booted up .... no repository. Just blank. I figured it wasn't loading due to crude wifi...continued business as usual. Switched to 4g, nothing. So I reboot considering I just uninstalled dm battery. Still nothing. Are thein servers down?

Yep, same here. I got the same problem. The repo server must be down.

I'm getting the same thing saying can't load the repository. Scared me for a sec cause I was messing around with new mods I just installed & activated then all of a sudden the repositories won't load. Hopefully it will be back up soon.

Same here hope its only temporary issue

This has been happening to me sense I updated yesterday. Was thinking it was that, but guess not.
Hope it gets worked out soon.

Seems to be working again. Looks like it was a server issue.

Yep is working now hope it wont happen again when I test new modules compatibility before going to work

Goodness
That's a relief. I'll be playing again as soon as the office xloses! Thanks to everyone for input!

Logcat for previous "Strange Issue" post.

So I posted about a strange issue with my device lately, when I shut it off, I can't turn it back on right away, I have to wait like, 20 seconds or so before it will show the "Google" splash screen again and boot. My thoughts were that maybe it is just shutting off the screen before the rest of the device ACTUALLY powers off, I messaged someone here on the forums and he told me that very well could be it. I have a logcat here of me powering off the device, is there anything here that seems off or not right? When it comes to logcats, I have no idea what any of this means lol Thanks in advance to anyone who can decipher this logcat.
http://pastebin.com/rDkb6TbQ

You can stop there! It's the new bootloader. You can roll it back an older one to fix it.

Does the logcat look suspicious? Or is this just a know thing? Thanks for the reply! I could use all the help!
Sent from my Nexus 6 using XDA-Developers mobile app

H4X0R46 said:
Does the logcat look suspicious? Or is this just a know thing? Thanks for the reply! I could use all the help!
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Didn't look at your log. Known issue

DR3W5K1 said:
Didn't look at your log. Known issue
Click to expand...
Click to collapse
Thanks! Seems like it does it with the MOB30I bootloader and the N preview bootloader, strange.

H4X0R46 said:
Thanks! Seems like it does it with the MOB30I bootloader and the N preview bootloader, strange.
Click to expand...
Click to collapse
Try the one before those two

H4X0R46 said:
So I posted about a strange issue with my device lately, when I shut it off, I can't turn it back on right away, I have to wait like, 20 seconds or so before it will show the "Google" splash screen again and boot. My thoughts were that maybe it is just shutting off the screen before the rest of the device ACTUALLY powers off, I messaged someone here on the forums and he told me that very well could be it. I have a logcat here of me powering off the device, is there anything here that seems off or not right? When it comes to logcats, I have no idea what any of this means lol Thanks in advance to anyone who can decipher this logcat.
http://pastebin.com/rDkb6TbQ
Click to expand...
Click to collapse
Im gonna be honest. You shot yourself in the foot. Any dev that looks at that logcat will not help you due to you having and using lucky patcher. That app will make sure that devs hate you. Sorry man but that is the way it is. Also might want to keep in mind that developers are adding in code that causes issues if it detects things like lucky patcher. Bewteen that and that malware ridden app of ES file manager and your issues could be many.
I will say this. There are tons of system errors all over that log. Might want to start from the ground up and knock out the system errors.

H4X0R46 said:
So I posted about a strange issue with my device lately, when I shut it off, I can't turn it back on right away, I have to wait like, 20 seconds or so before it will show the "Google" splash screen again and boot. My thoughts were that maybe it is just shutting off the screen before the rest of the device ACTUALLY powers off, I messaged someone here on the forums and he told me that very well could be it. I have a logcat here of me powering off the device, is there anything here that seems off or not right? When it comes to logcats, I have no idea what any of this means lol Thanks in advance to anyone who can decipher this logcat.
http://pastebin.com/rDkb6TbQ
Click to expand...
Click to collapse
DR3W5K1 said:
You can stop there! It's the new bootloader. You can roll it back an older one to fix it.
Click to expand...
Click to collapse
Which bootloader? I am running the latest bootloader from the N preview 3 firmware and when I power off my device, about 2 seconds after the screen goes black, I can then press the power button and it comes on just fine real quick. This is the bootloader that makes the "Google" logo bold. No problems here at all.
And out of curiosity, may I ask why you need to power off the device, and then turn it back on immediately? Why not just reboot your device if your on a custom firmware.

zelendel said:
Im gonna be honest. You shot yourself in the foot. Any dev that looks at that logcat will not help you due to you having and using lucky patcher. That app will make sure that devs hate you. Sorry man but that is the way it is. Also might want to keep in mind that developers are adding in code that causes issues if it detects things like lucky patcher. Bewteen that and that malware ridden app of ES file manager and your issues could be many.
I will say this. There are tons of system errors all over that log. Might want to start from the ground up and knock out the system errors.
Click to expand...
Click to collapse
So lucky patcher can cause issues, and es file manager is bad as well? Never knew. I saw that there were lots of errors in my logcat, but not experienced enough to figure out what they mean. Would you advise not using either of these apps then? And with this many issues in the logcat, is that the entire problem? Thanks.
EDIT: I should also add that I'm running the N preview.

christianpeso said:
Which bootloader? I am running the latest bootloader from the N preview 3 firmware and when I power off my device, about 2 seconds after the screen goes black, I can then press the power button and it comes on just fine real quick. This is the bootloader that makes the "Google" logo bold. No problems here at all.
And out of curiosity, may I ask why you need to power off the device, and then turn it back on immediately? Why not just reboot your device if your on a custom firmware.
Click to expand...
Click to collapse
Currently using Android N and the bootloader that comes with it, the one that makes "Google" show in bold. And reasoning would be to either boot into my bootloader and recovery, or to switch to another ROM. (I use multirom)
Another EDIT: I flashed MOB30I and formatted my userdata, clean start. I'm gonna keep an eye on my logcats and see what happens, so far, no errors like you saw in the posted logcat. Thanks Zelendel for mentioning all the errors caused by Lucky Patcher and ES File Manager.

H4X0R46 said:
Currently using Android N and the bootloader that comes with it, the one that makes "Google" show in bold. And reasoning would be to either boot into my bootloader and recovery, or to switch to another ROM. (I use multirom)
Another EDIT: I flashed MOB30I and formatted my userdata, clean start. I'm gonna keep an eye on my logcats and see what happens, so far, no errors like you saw in the posted logcat. Thanks Zelendel for mentioning all the errors caused by Lucky Patcher and ES File Manager.
Click to expand...
Click to collapse
No prob. Sorry for the late reply. Just got off of work. Yes lucky patcher is not only hated but worked against. It is one of the main apps that the Privacy Guard commits were made for. Others have code that won't boot the rom if it gets installed.
Es file explorer has gone to heck. Also avoid anything by the Cheetah company. Same issues.