Related
Hey guys,
Got an issue with my toggle switches on my today screen (wifi on/off, disconnect data, and flight mode). They were working just fine up until today, so I know that the issue occurred when I was messing with it today.
The error that I get when trying to use the switches says "The file 'JMLComm' cannot be opened. Either it is not signed with a trusted certificate, or one of its components cannot be found. If the problem persists, try reinstalling or restoring this file."
Today, i did three things, one that I'm almost positive had nothing to do with it was added morph gear and a Rom for SNES. The other two were adding Bandswitch (didn't work the way I wanted it to, so I removed it) and added Setup Dial Up Enable Disabler, which didn't cut off the data connection after the time I selected. so I deleted that also.
Any tips or suggestions? thank you
well, since no one can respond to that, how about this.where can I look up to see if that file is still on the phone our just got deleted.
JMLComm should be in the windows directory, a ROM file, so you will need to show all files, size on mine is 45k, attributes RM
There is also JMLTasks.exe, 74k, RM
Neither of them do anything when i try to run them. I believe they probably need command line parameters.
a quick google shows that jmlcomm is associated with enabling/disabling BT and WIFI (which makes sense)
yea, I saw that when I did a search, so im wondering what changed so I cant use my toggles.maybe if I were to reload the file on the phone it would fix it? or maybe theres something blocking it so I cant use it.im wondering how adding those two programs could have done that...
PedroEMT said:
yea, I saw that when I did a search, so im wondering what changed so I cant use my toggles.maybe if I were to reload the file on the phone it would fix it? or maybe theres something blocking it so I cant use it.im wondering how adding those two programs could have done that...
Click to expand...
Click to collapse
its a rom file, so it is not removeable. you acn copy over it, using some file managers (resco, total commander) or use a cab to instal a copy over it, but the file would still be there 'underneath' the one you add.
Id be more suspicious that its a bad install of cookies home tab (they are the toggles you mean, right?)
I'd probably go for a hard reset and reinstal, but thats me.
But would it take 2 weeks for something to happen? because CHT was the first thing i installed, and everything worked fine
oh no, it will be something that happened recently, but its often easier to start over than to backtrack. Plus rolling back the offending item wont necessarilly fix it.
dang.alright.thanks, and off topic, I know, but when I do a hard reset, what all on the phone was preloaded that will get deleted?
Sounds like one of the things you install used the same file as your problem program. So when it was in stall it over wrote it and when uninstalled it deleted it causing an issue. When you hard reset it will take the phone back to your last flash, what ever was installed on the rom by the cook will be there but anything you loaded after the flash will need to be restored
did you ever find a fix to this? my phone just started doing this!
*edit* If you're using CHT & this happened just reinstall.
xnifex said:
did you ever find a fix to this? my phone just started doing this!
Click to expand...
Click to collapse
I guess the development certificates / signing went out of date.
search after sdkcertsnew2015.cab to renew them.
GG
Hola,
I have recently noticed that each time I reboot my Note I717 the previously selected ringtone and notification sounds revert to the factory default. When I enter Settings -> Sounds I see the active selection reads "Unknown Ringtone." I go to the list of those ringtones/notifications available to check why and I find that the name of the downloaded ringtone/notification file has been replicated. Of the multiple files only the bottom-most on the list will actually play the file. Right now I have four entries for yy downloaded ringtone; three do nothing, but the last on the list selects the correct file. The same is true for the notification sound file.
Admittedly, this is not a big deal, but is annoying the hell out of me. Has anyone else encountered this situation? Is there an obvious solution of which I am unaware? Anyone care to venture a guess?
BTW, my Note is rooted, but is AT&T stock all the way, Version 4.0.4, BB UCLF6, Kernel 3.0.8.
Further info: I first loaded the ringtone/notification files on the SD Card, but recently moved the file to the internal memory. That change had no effect on the situation.
Regards,
Bubba
SAME HERE!
Have the exact same problem with my Infuse since I upgraded to ICS...Will get back to you if I finally find an answer!
settings-->> apps-->> all-->> media storage-->> clear data-->> force stop -->> REBOOT !!
Something similar happens with mine. When swapping batteries out it exhibits this. If i just reboot using the toggle it doesn't happen. Also, it only happens with custom ringtones. If i use stock ringtones i have no problems.
I have tried what the post above mine suggests but problem returns as soon as i swap batteries again.
Thanks. This worked. Haven't tried swapping batteries yet.
UnicornKaz said:
settings-->> apps-->> all-->> media storage-->> clear data-->> force stop -->> REBOOT !!
Click to expand...
Click to collapse
Thanks, This worked. Haven't tried to swap batteries yet.
zancro said:
Thanks, This worked. Haven't tried to swap batteries yet.
Click to expand...
Click to collapse
I was saying it happens when i swap batteries. Not swapping batteries as a cure...:sly:
UnicornKaz said:
settings-->> apps-->> all-->> media storage-->> clear data-->> force stop -->> REBOOT !!
Click to expand...
Click to collapse
That worked - at first. After the reboot, the default ringtone was listed as "ATT Play-on" and the notification was "sherbet". However, when I tried to change the ringtone to one I had created, it went back to being an unknown ringtone. The phone is the I777 and the OS is ICS, both from ATT. The ringtone is a 29 second MP3 file I created.
I did go back and try the reboot sequence again after the first attempt and it did clear it back to the default ringtone/notification, but as soon as I changed either, it was listed as unknown again. Is there a special format for ringtones?
Thanks!
I have found a good work around for those of you who may enjoy more usable space on your screen. With the screen the S4 comes with it only makes sense to use it. Only follow these steps after you are running on Hyperdrive ROM successfully (I am guessing this will work with other roms as long as Xposed Framework can be installed).
Background Work (no major changes yet)
1) Open the app Hyperdrive Control
2) Navigate Custom Settings > Advanced Mods > Framework Installer
3) Click Install/Update
4) Select the tab 'modules' from the top
5) Check all the boxes you see (I had 3)
4) Click Reboot
Let's get started
1) Reopen Hyperdrive Control
2) Navigate Custom Settings > Advanced Mods > Per App DPI Settings
3) Select Google Keyboard
4) Turn the switch to ON
5) Enter 160 for DPI, 100 for Font and check the box labeled 'xlarge res'
6) Click save and click yes.
7) Repeat steps 4-6 with the apps Swype and Samsung Keyboard
8) Make sure you followed the above steps then continue
9) Now find an app called Android System from the list and select it.
10) Enter 280 and don't change anything else (I don't know what you would be doing so I stayed away)
11) Click save and click NO.
12) Restart and enjoy.
I went back and changed System UI to 340 as I didn't like how small the notification bar became. Also recommending ExDialer as the stock keypad won't 'stretch' and lastly as a must, look into a good launcher. I am using NOVA Prime.
If you want to undo changes you can simply turn everything 'Off' and click Save and No. Then restart.
Hopefully this helps some!
If I am missing anything or if anyone wants to add more detail let me know! Side note: random but AOSP helper was installed on my device also allowing easy toggle from 3G to 4G with JuiceDefender...
Colton
Mods can you list this as a [HOWTO]... sorry left that out.
awesome.. .thank you!
OMG thank you for this, i has given up on how to do anything on it. I did not know how to use Xposed frameworks, this is what i needed, than you very much:good:
Has anyone tried changing the overall system DPI and then changing just the misbehaving Samsung applications back to stock (i.e., Contacts/Dialer, Camera)? I pretty much manually set all of my apps to between 320 and 340, but the Notification dropdown is way too big. (Email and Gmail both at 320 in order to become usable).
This made my launcher grid super tiny and the keyboard is unusable it is so small. I can imagine how some slight DPI adjustment could be good, but this is aweful!
that being said, I will use this method to adjust things how I would like them.
I'm glad it worked well for you guys but both of those changes made things worse for me. I put it back on stock and am very happy with it.
I'm running 320 DPI in my build prop. To fix the dialer I went into the per app DPI and changed the contacts app and phone app to stock 480 DPI and also the calculator app as well. They all run just like stock now no problems at all
Forgot to mention gallery as well
Sent from my SCH-I545 using xda premium
im using 360 in my build.prop. and have had no problems. only thing i had to fix was my market. which i used this market found here
http://forum.xda-developers.com/showthread.php?t=1839871
using the correct version of the one in my current rom(hyperdrive). Dont ask me why this works. But someone else said they tried it and it worked. so i did and it worked. Sometimes ive noticed it will all the sudden on reboot, change to a different version of the market. But that has only happened a couple of times. and usually it didnt matter(most apps still showed up like normal). But i dont know that this will work the same way for everyone since it seems to be a semi flakey method.
It works fine in HyperDrive RLS 4. Don't try to change the build.prop for the first boot, though. Let it boot once, then change it. Let's just say that the results were a hung device first.
I added clock back to 480 because there are issues with it.. The year view in Calendar is a bit off, but that's the only screen that doesn't work right... The Market works fine at this resolution (360). This is much easier than what I was doing before...
Now Touchwiz can be somewhat usable as it isn't huge gigantic text everywhere (even on the Tiny selection in Screen)
My system ui keeps crashing whenever I change anything related to Android System. Followed the directions but no luck so far.
kcellb said:
My system ui keeps crashing whenever I change anything related to Android System. Followed the directions but no luck so far.
Click to expand...
Click to collapse
That's why I just went the other way around and changed build.prop then made things larger as needed. Less problems this way...
jeffreycentex said:
That's why I just went the other way around and changed build.prop then made things larger as needed. Less problems this way...
Click to expand...
Click to collapse
I will be the first to admit that I am not an expert at this in anyway. This is just how I got it to work...
You said Hyperdrive Build 4 is working for you? I flashed it and have had nothing but troubles so far. It always hangs at SAMSUNG Custom boot screen... I have tried everything and now once I went back to my Nandroid of 3.1 it boots up with no issue, Then I go to reboot through the power menu and it hangs on that screen again.
Colton
PS I guess an easier approach also to allow most programs to stay stock would be to allow the android system to stay stock and just change what you need like the launcher...
I had the same problem about system ui... make sure you are pressing NO to the option it gives you and then reboot. I also had some DPIs that the phone just didn't like (240)... everything kept fc'ing...
colton22 said:
I will be the first to admit that I am not an expert at this in anyway. This is just how I got it to work...
You said Hyperdrive Build 4 is working for you? I flashed it and have had nothing but troubles so far. It always hangs at SAMSUNG Custom boot screen... I have tried everything and now once I went back to my Nandroid of 3.1 it boots up with no issue, Then I go to reboot through the power menu and it hangs on that screen again.
Colton
PS I guess an easier approach also to allow most programs to stay stock would be to allow the android system to stay stock and just change what you need like the launcher...
I had the same problem about system ui... make sure you are pressing NO to the option it gives you and then reboot. I also had some DPIs that the phone just didn't like (240)... everything kept fc'ing...
Click to expand...
Click to collapse
I had problems with the first two downloads. Then I was able to get one to work early this morning... Also note that it is supposed to be a wipe'd flash, so make sure you do the format data/cache 3 times, then format system... I generally do a flash of the rom first to make sure that there aren't problems, though, before I format system...
I only use 320, 360, and 480's as DPI's on the S4.
Your approach is the way I used to do, but I wanted everything smaller, so every time I installed a program, I changed it to 320/360.. But then I wanted 320/360 to be the overall and only make exceptions for the things that demand stock DPI.
Understood - I didnt wipe to flash as i never did before without an issue. I am downloading stock ODIN now as something is up with my data partition...? It hangs on every second+ boot from restore/install and will not even boot off an install. I will go to stock odin, root, recovery and then install. Also downloading a fresh copy of Hyperdrive RLS4... Thank you for the tips.
C22
Found a better way!
Okay so I am now on RLS 10.2.0...
Download some type of Root file manager... I paid for/use Root Explorer love it.
Navigate to /system and long press build.prop
Find the line that contains screen density =480 and change it to your desired DPI (I am using 280)
From there all apps/everything is changed to that dpi... some stock apps you will have to use xposed to change them back to 480 just to make it work because they show different resolutions horribly.
I followed these steps...
http://forum.xda-developers.com/showthread.php?t=2269483
works great! Enjoy.. Also on the Multi DPI stock app post, the only one that works with the Verizion phone is the Gallery S4 v2.zip file... The others I am trying to work with the dev on getting up and running for our phones.
Colton22
deleted
Thanks
Intro
I don't mean this to be a thread for any specific ROM or problem, but rather a general guide that essentially eliminates all doubt of machine or user error (we all make mistakes). This is generally geared towards the issues users are experiencing when flashing an AOSP ROM, but can also apply to Sense, and even other devices. This covers from downloading a ROM forward, and also making sure that everything gets properly installed with no corners cut, so that everybody can be on the same page when a problem arises. I'm not trying to say anybody's way of doing things is wrong, but I've see a lot of people asking different questions that end up getting solved with the same few answers. This isn't a "how to flash" thread, but rather how to ensure you're getting your device in a clean, fresh state so that everybody can be on the same page when it comes to bugs, otherwise nobody is going to want to help you if you don't try to help yourself first.
I know this is on the longer side, so key points are underlined, with a TL;DR at the bottom
Downloading
Checksums or hashes are a great way to make sure that the *.zip or any other file you're downloading is not only the right one, but that it hasn't been corrupted or tampered in transfer (uploads or downloads). You'll probably need to install something to work with chescksums- personally I like the open-source HashCheck for Windows. It adds a "Checksums" tab to the right-click > Properties dialog that automatically calculates MD5 (most common) and SHA-1 (more advanced) hashes. I encourage anyone posting a file to also post the MD5 with it, for everybody's sake, since it only takes a few extra seconds to eliminate all doubt of a bad upload or download. HashCheck even gives an option to create a *.MD5 file, just like the ones you might get from goo.im. If you're on Linux, Android, or presumably Mac you can check a file's md5 by opening terminal and simply typing "md5sum <filename>" without the quotes. If a file is posted without an MD5, you can download it twice and check it against itself, but just keep in mind you're going to be hitting somebody's server twice as hard, so only do it if necessary. Now that you're sure you have the right files...
Wiping/Flashing
Most people know dirty flashing is at your own risk, and if you have a problem, the first thing anybody's going to tell you is to do a clean flash. No really, just clean flash- that's what backups are for, but that's a whole different topic. Unfortunately, most people consider a clean flash to be just a factory reset, but that only wipes dalvik, cache, and data (except your sdcard), while leaving the system partition intact. To do a proper clean flash you want to go into advanced and make sure that system gets wiped in addition to dalvik, cache, and data. I can't say exactly what (sorry), but there's lots of miscellaneous things that can persist between flashes, especially when you're going to a different ROM. For us DNA owners, there's still a lot of activity in our CM device tree, meaning that even on the same ROM, some of our device files may change between versions which will necessitate a wipe of system. Maybe it's just me, but it seems things go out of line more often on 4.3 so I just always wipe system now.
If you're here, you probably know how to flash a ROM, but always double check the OP or first few posts and see what gapps/settings/etc are recommended. I'm also going to remind you that it takes just a few extra seconds to create a *.md5 file with HashCheck that you can push to your device along with the *.zip and TWRP (probably CWM too) will check the file against it's MD5 before flashing it. After using the Setup Wizard to log in to your Google account, make sure that you uncheck the box to restore settings and data to your phone, otherwise those can cause problems. Now you can be sure that whatever is on your device is clean as can be and as the developer intended, otherwise you're probably not going to get much help.
Narrowing down the problem
Now that you've got a brand spanking new and clean ROM is the best time to try and narrow down a problem, but before you post anything, try the golden rule of IT- "Have you tried rebooting it yet?" Also, you can try booting to recovery to clear just dalvik and cache and/or repair permissions. This is the first time you should consider making a post about your problem, but please, please, please don't make a post that just says something like "Settings FCs." Posts like that don't tell anybody anything- the best thing you can do is pull a log (more on that in a second), and create a post in the appropriate thread which you can determine as follows: Start by seeing if the problem occurs with nothing installed besides the ROM and recommended gapps- do not restore any backups, install any apps, or flash any kernels, even if the OP recommends it. If you're having problems with Settings or any Google app, there's likely a conflict with the gapps package that should go away if you reflash only the ROM, otherwise it's a bug in the ROM itself. Either way, if you can reproduce a problem at this point you should post in the ROM thread. If you want to flash a custom kernel, only do so after you've verified the problem isn't with the ROM or gapps. Flash only the kernel, and if there's any problems after that, post them in thread you got the kernel from, not the ROM thread.
If you're having a problem with an app, once you've completed the above steps, install only that app without restoring any data. If you can't replicate the problem, there's likely an incompatibility any corresponding data you may have restored, and sorry, but there's not really anything you can do about that. If the problem occurs with a freshly installed app, first check the Play Store to see if other users are experiencing the same problem- there may just be something wrong with the app. If it only seems to be you having this problem with a clean install, the ROM thread is the best place to post, although keep in mind other users may not be familiar with app.
Pulling and posting logs
Even now, nobody is obligated to help you (you flashed that ROM at your own risk, remember?), but once you're at this point, you'll have a better chance at getting help. Try to include as much information as possible like what else you were doing, what screen you were on, what button you tried to press, etc. and if you can, try to see if you can replicate it. Like I mentioned above, posting a log is the best way to get help, and they're really easy to get. Not everybody is going to understand every line, but if you know what you're looking for, occasionally the log can tell the developer exactly what the problem is, and bam- easy fix.
First make sure USB Debugging is enabled in Developer Options (if you don't see Developer Options, go into About Phone and tap on the Build Number line 7 times), and make sure that Root Access is set to both Apps and ADB. Now as far as gathering these logs, SysLog is by far one of the easiest ways- download it, open it, and press "Take Log." It pop up a toast message saying that your logs are in /sdcard/SysLog/<DATE_TIME>.zip and it'll even give you the option to share it via email, Dropbox, or anything else you might use. Post that and you'll have even better chances of getting help. For simplicity, I'm not going to details on manually pulling logs, however if you're stuck in a bootloop or something like that and can't run the app, use "adb pull /proc/last_kmsg" and post a link to that file.
TL;DR
Sh*t happens, learn to deal with it or go back to stock
Verify your download with an MD5 Checksum
Wipe system in addition to factory reset (dalvik, cache, & data)
Flash ROM and gapps without installing anything else or restoring any data
Pull a log, it's really easy
Now is the best time to make a post about your problem
Radio/Reception Problems on the DNA?
First things first- Double check your settings in Settings > More > Mobile networks. They should be as follows:
Data Enabled: Yes
Data Roaming: No (unless you're actually roaming)
National Data Roaming: Yes (otherwise you'll probably lose data; this won't get you any roaming fees)
Network Mode (Verizon): LTE/CDMA/EvDO (or Global, which is everything, I've never noticed any difference between the two)
Network Mode (GSM): GSM/WCDMA preferred (depending on the ROM, you may also need to flash the GSM patch courtesy of Flyhalf205 from the 2nd post in the original CM10.1 thread.)
System Select/CDMA Roaming: Automatic
CDMA Subscription: RUIM/SIM
GSM users may also need to manually enter APN settings for your carrier to get things like MMS functioning properly. I'm not going to compile a worldwide list, but if Google fails you, your carrier should have support documentation with these settings. Recently, I noticed this file in the android source lists tons of APNs, so try finding your carrier in there too.
Why do I have 0-1 bars? I got a lot more on Sense
Don't be alarmed if your reception looks low/non-existent. Sense "pads" the signal bar to get it to show bars more "accurately," but AOSP does not, so expect a drop in bars. To get an accurate assessment, you want to be looking at your actual signal in dB before trying to diagnose anything by going to Settings > Interface > Status Bar and changing Signal Status Style to Text, and your signal bars will be replaced with a negative number, therefore a value closer to zero indicates a stronger signal. If you don't like negative numbers, another way of thinking about this is as if the phone was telling you how far you are away from the nearest tower. What would normally be 5 bars on Sense equates to -70dB, and 1 bar equates to -115, but these are approximate values and depending on your location and environment, you might bee numbers outside this range.
I'm still having problems
Unfortunately, our phone is known to have problems with reading the SIM card. Some say it's purely software, some say its purely hardware, but I believe it can be either. I'd first suggest giving your SIM card a cleaning by popping it out and gently rubbing the contacts with a clean rubber eraser, another more risky option is a just drop of isopropyl alcohol on a cotton swab. If you have compressed air, you can give that a small blast into the SIM slot from a few inches away. If the phone is still having issues with reading the SIM after that, it might need to be replaced.
Another possibility is issues with the radio firmware. You can try updating the firmware by following the instructions in this post. Personally, I recommend the most recent version, 2.06.605.1. Some users, myself included, have reported that sometimes a full RUU back to 100% stock is necessary to restore proper radio function. Instructions for that can be found here, but be aware that this can be a lengthy, tedious process. You'll end up having to re-unlock and root your phone before you'll be able to flash anything else again, so I only recommend this as a last resort, but is nonetheless something to bear in mind.
Stickie this?
Sent from my HTC6435LVW using Tapatalk 4
I'm going to stick it for now, it's actually good basic info. But I am moving it to the Q&A forum.
Thank you. I debated where to post this, but since this mainly applies to those of us who are flashing away from Sense, I thought it would get more attention with the development section, but I respect your decision to move it.
pyroguysf said:
Thank you. I debated where to post this, but since this mainly applies to those of us who are flashing away from Sense, I thought it would get more attention with the development section, but I respect your decision to move it.
Click to expand...
Click to collapse
Yeah that makes sense, and I was hoping this would also cut down on unnecessary thread starts.
I think what I'll do is have this in both development forums as a sticky, hopefully this will help out some of the chefs.
If you edit one thread, be sure to edit the clone in the other forum.
I am going to let you clean this up as much as possible over the weekend, then maybe move it to the dev threads Monday as a polished product, see if you can get as much info as possible about GSM to include about the signal issues etc.
Part of the issue is that a lot of the users who are guilty of saying "this is broken, fix it" with no logcat and not having wiped or installing some app that is causing the issue don't read stickies, but it's a good resource to have.
You might add something about restoring apps from TI or MyBackup and apps causing issues, or installing some root app and then having issues, a solution might be to wipe, then boot, then try to reproduce the issue, or uninstalling the app.
Also if you flash a different kernel, do not then go into the ROM thread and start saying something doesn't work, having installed a kernel that did not even come with the ROM and confusing the chef.
orangekid said:
Part of the issue is that a lot of the users who are guilty of saying "this is broken, fix it" with no logcat and not having wiped or installing some app that is causing the issue don't read stickies, but it's a good resource to have.
Click to expand...
Click to collapse
I've noticed this, but I made this in hopes of giving people a place to link back to rather than having to waste time typing out the same things over and over, which is why I also put the link in my sig.
orangekid said:
You might add something about restoring apps from TI or MyBackup and apps causing issues, or installing some root app and then having issues, a solution might be to wipe, then boot, then try to reproduce the issue, or uninstalling the app.
Also if you flash a different kernel, do not then go into the ROM thread and start saying something doesn't work, having installed a kernel that did not even come with the ROM and confusing the chef.
Click to expand...
Click to collapse
Good ideas. I'll try to add a section for apps when I get a chance. I tried to briefly touch on the kernel situation by saying to read the OP for recommended settings, but I'll definitely expand on that.
OP edited for clarity/grammar and updated with information for apps and determining where to submit your post (e.g. ROM vs kernel thread). Second post updated with GSM info.
pyroguysf said:
OP edited for clarity/grammar and updated with information for apps and determining where to submit your post (e.g. ROM vs kernel thread). Second post updated with GSM info.
Click to expand...
Click to collapse
Sounds good.
Moved to dev forum.
If you want to go ahead and create the same thread and copy / paste the first 2 posts, I can sticky it.
Hi guys.
Just started to build my own AOSP build from source. Im using Ubuntu 12.04 LTS and everything works great with repo sync and building the rom.
I flash the build and everything works great to. Time and date is correct. Google sync works. Google now works.
But when i reboot my phone the time resets to 1970 for about 15 seconds till it goes to current date and time. But i get like 10 notifications from all of my apps saying google sync error, Time error and WhatsApp says time error to. Goggle sync is stuck on sync. google now dont work and so on.
I have tried to build it over and over again without luck. I wiped everything before flashing the zip. I even did a fresh clean install of ubuntu and did everything from the begining but it still resets to 1970.
I tried to build CM11 rom also and everything works great. No time issues. So why is pure AOSP doing this?
Someone said something about qualcomm time daemon not storing time in data/system/time directory .
I have been trying to fix this for days without any luck.
bariz143 said:
Hi guys.
Just started to build my own AOSP build from source. Im using Ubuntu 12.04 LTS and everything works great with repo sync and building the rom.
I flash the build and everything works great to. Time and date is correct. Google sync works. Google now works.
But when i reboot my phone the time resets to 1970 for about 15 seconds till it goes to current date and time. But i get like 10 notifications from all of my apps saying google sync error, Time error and WhatsApp says time error to. Goggle sync is stuck on sync. google now dont work and so on.
I have tried to build it over and over again without luck. I wiped everything before flashing the zip. I even did a fresh clean install of ubuntu and did everything from the begining but it still resets to 1970.
I tried to build CM11 rom also and everything works great. No time issues. So why is pure AOSP doing this?
Someone said something about qualcomm time daemon not storing time in data/system/time directory .
I have been trying to fix this for days without any luck.
Click to expand...
Click to collapse
I'm not a dev (though I know how to compile, just not any coding) so don't have a fix for you, but found this as a potential work around until someone can help you sort the rest: http://software.techassistbox.com/datetime-1970-bug-aosp-workaround_136694.html
The time issue is solved thank you
Time to include Superuser to the build but i have no idea how to do that.
Someone want to help?
bariz143 said:
The time issue is solved thank you
Time to include Superuser to the build but i have no idea how to do that.
Someone want to help?
Click to expand...
Click to collapse
Out of curiosity, how did you resolve?
I was under the impression that you just have to add the SuperSU apk to /system/app and the SU binary to /system/bin, but not entirely sure on that part. If you are trying to bake it into the actual Settings app, not sure on that.
The Google binaries had some missing files so I pulled the binaries from stock factory image and it worked
I want the superuser baked in as the other roms out there
Still haven't found a guide or help from someone.
What happens to XDA soul where everyone helped each other back in the days. I have pm a lot of developers and no one answered back
Found some guides on how to add stuff AFTER it's been built, but not during the build itself.
I know a lot of the devs get bombarded with inane questions from random people so often ignore PMs. Not saying your question is, but most of them don't like to answer questions there that should be in the thread for their stuff so often just overlook the inbox.
Come to think of it, you aren't really adding SuperSU TO Settings, just enabling a shortcut in the Settings app that leads to the app.
http://developer.android.com/reference/android/provider/Settings.html
I'm wondering if this:
public static final String ACTION_APPLICATION_SETTINGS
Activity Action: Show settings to allow configuration of application-related settings.
In some cases, a matching Activity may not exist, so ensure you safeguard against this.
Input: Nothing.
Output: Nothing.
Constant Value: "android.settings.APPLICATION_SETTINGS"
Part isn't something to do with creating that link...? Just making an educated guess.
Info on adding stuff after it's built - might be helpful to see where things are at?
http://forum.xda-developers.com/showthread.php?t=2184207
http://forum.xda-developers.com/showthread.php?t=2341389
Also, check out this dev/thread: http://forum.xda-developers.com/nexus-4/themes-apps/mod-custom-options-settings-app-ops-t2593536 Maybe you can ask him or decompile his Settings.apk and see where he added the necessary coding in.
es0tericcha0s said:
Found some guides on how to add stuff AFTER it's been built, but not during the build itself.
I know a lot of the devs get bombarded with inane questions from random people so often ignore PMs. Not saying your question is, but most of them don't like to answer questions there that should be in the thread for their stuff so often just overlook the inbox.
Come to think of it, you aren't really adding SuperSU TO Settings, just enabling a shortcut in the Settings app that leads to the app.
http://developer.android.com/reference/android/provider/Settings.html
I'm wondering if this:
public static final String ACTION_APPLICATION_SETTINGS
Activity Action: Show settings to allow configuration of application-related settings.
In some cases, a matching Activity may not exist, so ensure you safeguard against this.
Input: Nothing.
Output: Nothing.
Constant Value: "android.settings.APPLICATION_SETTINGS"
Part isn't something to do with creating that link...? Just making an educated guess.
Info on adding stuff after it's built - might be helpful to see where things are at?
http://forum.xda-developers.com/showthread.php?t=2184207
http://forum.xda-developers.com/showthread.php?t=2341389
Also, check out this dev/thread: http://forum.xda-developers.com/nexus-4/themes-apps/mod-custom-options-settings-app-ops-t2593536 Maybe you can ask him or decompile his Settings.apk and see where he added the necessary coding in.
Click to expand...
Click to collapse
Holy sh!"¤%t. Thats alot to do. I have to study this for a month to maybe succed
Compiling the rom feels alot easier when reading this haha
bariz143 said:
Holy sh!"¤%t. Thats alot to do. I have to study this for a month to maybe succed
Compiling the rom feels alot easier when reading this haha
Click to expand...
Click to collapse
The more you learn, the more you realize you dunno.
es0tericcha0s said:
The more you learn, the more you realize you dunno.
Click to expand...
Click to collapse
Haha good answer. Man I don't know where to start. I will look in to it but not today.
deleted
Just noticed that my aosp build cant locate my location. And thats a huge setback. Really need help with this. Without gps there is no way i can use this this rom as a DD.
Downloaded gps status app and started it and it doesnt find even 1 satelite so something is wrong there.
See if you can grab the gps.conf file from a working rom for your phone. Or try this - which might be able to make the right one for you: https://play.google.com/store/apps/details?id=org.fastergps
es0tericcha0s said:
See if you can grab the gps.conf file from a working rom for your phone. Or try this - which might be able to make the right one for you: https://play.google.com/store/apps/details?id=org.fastergps
Click to expand...
Click to collapse
Tried that app. Nothing happend. Going to grab a gps.conf file from some rom.
EDIT: Just tried that without sucess. No gps lock at all. Think it has something to do with my binaries. Cant figur it out
EDIT2: FIXED:but GPS connection is very bad. Have to go outside to get a lock. Could get connection inside before
At least you are making progress. So the gps.confg file helped a bit? Now that it is working somewhat, maybe one of the GPS status apps can help make it stronger?
es0tericcha0s said:
At least you are making progress. So the gps.confg file helped a bit? Now that it is working somewhat, maybe one of the GPS status apps can help make it stronger?
Click to expand...
Click to collapse
Okey its not the gps.conf file. Just flashed a custom rom (No names) and it locates my location in a heartbeat inside my apartment. My build is much slower and don''t work inside.
Dropped development ATM. Need to fix gps. Dont know where to start. I tried with the binaries again without luck
bariz143 said:
Dropped development ATM. Need to fix gps. Dont know where to start. I tried with the binaries again without luck
Click to expand...
Click to collapse
Bariz I have the same time issues which bin files did you replace/add was time_daemon one of them?
kidkoala_uk said:
Bariz I have the same time issues which bin files did you replace/add was time_daemon one of them?
Click to expand...
Click to collapse
I just extracted all the binaries from stock rom and put them in my vendor if I remember it right. It was a long time ago since I developed. To much for me man
bariz143 said:
I just extracted all the binaries from stock rom and put them in my vendor if I remember it right. It was a long time ago since I developed. To much for me man
Click to expand...
Click to collapse
Cheers bro.
Edit: Issue now resolved the Google proprietary blobs are missing a number of files. Got the necessary files and added to my build.
AOSP build resetting time to 1971 after reboot in Airplane Mode
bariz143 said:
The Google binaries had some missing files so I pulled the binaries from stock factory image and it worked
I want the superuser baked in as the other roms out there
Still haven't found a guide or help from someone.
What happens to XDA soul where everyone helped each other back in the days. I have pm a lot of developers and no one answered back
Click to expand...
Click to collapse
We are having the same issue with a Nexus 5 (Hammerhead) where the date/time are not sticking after reboot when in Airplane Mode (no data connection, wifi off). Can you provide some more detail about how solved the problem? Which binaries and how did you pull them over? Thanks.