I've been on these alphas for a while now, with great joy but sad battery life. I noticed in BetterBatteryStats that my phone is awake 100% of the time, and found "bluesleep" running 97% of the time under kernel wakelocks.
I remembered reading about it in the Neutrino thread, where they found a fix ->link<-
and gave it a shot at copying those same files, though taken from a cm7 ROM. But it worked! No more bluesleep, and the phone sleeps as it's supposed to.
I started out with the prime suspects: hciconfig, hcitool, -and copied them in order, with intermittent reboots, to see which one would solve the problem. But it didn't work until I added hcidump. So that might actually be the only one needed...
I'll attach them all anyway, if anyone else wants to try.
BTW, this is supposedly related to Bluetooth, which I never use, so I wouldn't know if it breaks anything.
http://forum.xda-developers.com/showpost.php?p=22216714&postcount=1450
Hello, excuse me for my english but I have a question, it's sure I have to copy the unzipped files to /system/xbin and set permissions xxx x-x x-x and not /system/bin ?
kezayah said:
I've been on these alphas for a while now, with great joy but sad battery life. I noticed in BetterBatteryStats that my phone is awake 100% of the time, and found "bluesleep" running 97% of the time under kernel wakelocks.
I remembered reading about it in the Neutrino thread, where they found a fix ->link<-
and gave it a shot at copying those same files, though taken from a cm7 ROM. But it worked! No more bluesleep, and the phone sleeps as it's supposed to.
I started out with the prime suspects: hciconfig, hcitool, -and copied them in order, with intermittent reboots, to see which one would solve the problem. But it didn't work until I added hcidump. So that might actually be the only one needed...
I'll attach them all anyway, if anyone else wants to try.
BTW, this is supposedly related to Bluetooth, which I never use, so I wouldn't know if it breaks anything.
http://forum.xda-developers.com/showpost.php?p=22216714&postcount=1450
Hello, excuse me for my english but I have a question, it's sure I have to copy the unzipped files to /system/xbin and set permissions xxx x-x x-x and not /system/bin ?
Click to expand...
Click to collapse
Yes you need to copy them to /system/xbin and set the permissions as stated above. I copied only 3 files: hciconfig, hcidump, and hcitool. After I set the permissions I rebooted that my phone calls would drop or get cut off when my screen blanked. To fix it I tried deleting hcitool and rebooted. This fixed the phone call issue but I haven't figured out if my battery life has improved.
Try that and repost with your results.
Sent from my MB860 using XDA App
I think you must copy the files in system/bin, not system/xbin !
Envoyé depuis mon MB860 avec Tapatalk
Here is a link to the fix at the devs site with instructions.
http://www.jokersax.com/developer-pages/jokersax/fixes/
Excuse me, but I speak English poorly. I copied the 3 files in system / bin instead of system / xbin and my battery lasts longer. At rest, I -55 mA instead of -90 mA. And I have no problem with black screen during a call.
In the bin directory, there are 3 files in the file bluesleep.zip!
kezayah said:
Excuse me, but I speak English poorly. I copied the 3 files in system / bin instead of system / xbin and my battery lasts longer. At rest, I -55 mA instead of -90 mA. And I have no problem with black screen during a call.
In the bin directory, there are 3 files in the file bluesleep.zip!
Click to expand...
Click to collapse
Thank you...that is good to know as I think there is still debate on where to put the files.
Related
Hey there everyone. So, I'm getting really close to finishing up a new boot animation. I'm just getting stuck on little things like size of the pngs (they're usually around 120,000 to 150,000MB and the whole thing is 21.1KB(164 png frames). That seems bigger than most I have seen, but I am pretty much a noob at any of these things. The fact that I have this thing working is just amazing to me lol. Also, having some issues with how to write the desc.txt file. Currently I have it set up like such:
320 480 24
p 1 0 part0
p 3 0 part1
From my understanding, I am telling the animation to be 320pixels x 480 pixels, running at 24 frames/sec, playing folder 0 once with no time inbetween frames, and playing folder 1 3 times with no time lapse between the frames. Is this correct? I'm having issues with the 2nd folder playing 3 times. I've tried playing around with arrangement of the last line and it will play in various configurations, but will usually just play all the way through and stop until the phone loads completely or if I put it all in just one folder, then use p 0 0 part0 then it will loop. I don't mind this so much, but would prefer just to have the 2nd half of the pngs recycle. Also, would love to add part of a mp3, but it seems no one has figured this one out yet? Have tried naming it boot.mp3/android_audio.mp3/android_sounds.mp3 in and around the zip file and in and around both the data/local files and the system/media files.
So, any advice? Would love to get this working to my expectations so I can share it with everyone!
The only way i've found to get sound on the regular 2.1 rom is to do it the bootscreen folder way (boot.gif, xml, etc..) instead of the bootanimation.zip (.png, desc.txt, etc..).
-------------------------------------
Sent via the XDA Tapatalk App
I suppose maybe it would have helped if I mentioned I am running Aloysius V12? Or do you mean regular 2.1 as far as Sense and not Vanilla? I really don't want to have to learn how to turn this into a gif and the other stuff, but it might be worth it if that is my only chance. I'm doing a Super Mario Galaxy 2 animation and wanted to add a bit of an orchestra performing some of the music from the game.
I'm using more of a stock 2.1 sense rom, and doing the bootscreen method is the only way i could get sound working on it. As far as other roms i'm not real sure about, some may work with bootanimation.zip and an android_audio.mp3 in the system/media/ folder.
Thanks Magnum. Any chance that you could give me a few pointers on how to convert what I have to the bootscreen type idea? Do I just convert all my pngs to gifs and then find an .xml file and replace the info with mine? I really think the mp3 will add to the animation. I tried every combo of adding the mp3 that I have seen or heard of, to no avail.
PS. How big should this file be? Right now it feels like it might be too large because it stays on the skateboarding android screen for a pretty long time it seems. I don't remember it taking quite as long as before I started playing around with it.
So, totally meant to put down it's 21.1MB not KB. Silly me.
probably need an animation program that will convert your png's to a single boot.gif animation. Heres a link to the nexus bootscreen to look at. As far as file size, the one i use is around about 2 mb i think, not sure how big it can go though. Also not sure if the bootscreen way will work on non-rooted phones by pushing to /data/local method.
Also sent a pm (if it went through lol).
Alright, well just finally got it playing like I wanted. Loving it! Looks pretty sweet IMO, but it does take just over a minute on the boot screen before the animation starts. Is this normal? I've never really payed attention to it. I'm gonna see what I can do as far as reducing the pngs to take up less space, then I might try the gif deal.
es0tericcha0s said:
Alright, well just finally got it playing like I wanted. Loving it! Looks pretty sweet IMO, but it does take just over a minute on the boot screen before the animation starts. Is this normal? I've never really payed attention to it. I'm gonna see what I can do as far as reducing the pngs to take up less space, then I might try the gif deal.
Click to expand...
Click to collapse
mine takes a little bit to get to the boot animation also.
es0tericcha0s said:
So, totally meant to put down it's 21.1MB not KB. Silly me.
Click to expand...
Click to collapse
Btw, might want to try to get the file size down quite a bit, that seems kinda big for a boot animation.
es0tericcha0s said:
Hey there everyone. So, I'm getting really close to finishing up a new boot animation. I'm just getting stuck on little things like size of the pngs (they're usually around 120,000 to 150,000MB and the whole thing is 21.1KB(164 png frames). That seems bigger than most I have seen, but I am pretty much a noob at any of these things. The fact that I have this thing working is just amazing to me lol. Also, having some issues with how to write the desc.txt file. Currently I have it set up like such:
320 480 24
p 1 0 part0
p 3 0 part1
From my understanding, I am telling the animation to be 320pixels x 480 pixels, running at 24 frames/sec, playing folder 0 once with no time inbetween frames, and playing folder 1 3 times with no time lapse between the frames. Is this correct? I'm having issues with the 2nd folder playing 3 times. I've tried playing around with arrangement of the last line and it will play in various configurations, but will usually just play all the way through and stop until the phone loads completely or if I put it all in just one folder, then use p 0 0 part0 then it will loop. I don't mind this so much, but would prefer just to have the 2nd half of the pngs recycle. Also, would love to add part of a mp3, but it seems no one has figured this one out yet? Have tried naming it boot.mp3/android_audio.mp3/android_sounds.mp3 in and around the zip file and in and around both the data/local files and the system/media files.
So, any advice? Would love to get this working to my expectations so I can share it with everyone!
Click to expand...
Click to collapse
To get audio, one of your folders must be named 'android' and your audio file must be names android_audio.mp3. Take a look at mine to see what I did. Both of these files would go to /data/local. The pdf file is really the mp3. This site does not allow attaching mp3 files.
Ihtfp69 - you are awesome! I've been wrestling with getting this file down to a manageable size for a couple of days and then with your post I realized I could do JPGs instead of PNGs, and voila! I went back through and redid the whole process in almost no time. After all the reading and research I've done and from your post, it's fairly easy now. I still couldn't work out the audio file though. I downloaded your file, but couldn't open it so wasn't quite sure what you were trying to show me. I put the correctly labeled mp3 in a file lableled android file and tried it in and out of the Zip file, and nothing happened. Yes, the obvious was considered and the volume was turned up. Either way, thanks for your help(and you too Magnum)! Check out my new post with the file in it and see what you think...
Send me your audio file and I will get it working for you. Did you rename my pdf file to mp3 before opening?
-------------------------------------
Sent from my Evil Eris
I am at work now and don't have it handy at the moment. How long should the mp3 be to work the best? I originally had cut the mp3 out of a Youtube video and was approx. 30 seconds long and around 172 KB. Once you let me know, then I will recut it and PM you. Thanks!
It doesn't matter how long, but it should sync with your animation. Normally your phone won't take too long to boot. Just time it to see.
-------------------------------------
Sent from my Evil Eris
Send me your audio file and I will get it working for you. Did you rename my pdf file to mp3 before opening?
-------------------------------------
Sent from my Evil Eris
Click to expand...
Click to collapse
I've tried different ways i think to get audio on the stock like rom with not much luck (other than bootscreen/xml method), think i even tried your bootanimation. May just not work with the stock like rom, dunno lol.
-------------------------------------
Sent via the XDA Tapatalk App
Hmm, maybe I should try it on a more Vanilla type rom. I like the idea of Vanilla, but just seem to have better luck with the Sense roms. Probably because people have been messing with those for longer and have more of the issues under control.
es0tericcha0s said:
I am at work now and don't have it handy at the moment. How long should the mp3 be to work the best? I originally had cut the mp3 out of a Youtube video and was approx. 30 seconds long and around 172 KB. Once you let me know, then I will recut it and PM you. Thanks!
Click to expand...
Click to collapse
Sent you a PM.
Well heres some bad news...I was working on Version 5 of my rom. Completely bricked my Nexus one.... Tmobile gave me a decent upgrade/trade in so i got the New Galaxy S 4g... I will leave Versions 3 and 4 of my rom up for everyone to enjoy an further it to bigger an better things. I will no longer be able to support or answer any tech questions since i do not own a nexus one anymore. Its been fun
_______________________________________________________________
3/3 5:45am Finally Ive finished testing and making sure the GRI40 is running smooth an flawless, Sorry it took so long to test, but it seems i hit my data cap of 5gigs in less than 8 days so it was slow on testing HSDPA speeds but thats all worked out now on my friends t-mo sim card i hit 4.5MB/s
Rom features: A2sd set up on first boot. If you dont want it dont set a Ext3 partition
Rooted with SU+busybox, Davik-Cache on SD, Deoxed file system, Zipaligned for ram. Few other things i cant remember because i spent 12 hours tryin to figure out why my data was so slow before i realized they capped me. This version is without the TB alerts. V3.1 with trackball alerts will be posted up here very shortly since trackball alerts will not work with A2sd because it reads trigger files.
Download link: http://www.mediafire.com/?6x9ng1m7589iuyd
Radio download: http://www.megaupload.com/?d=G37OCBVB
Nand recovery image: http://www.mediafire.com/?81h19gk0p880qra
For your complete an easy 2.3.3 GRI40 flash
Use Hboot to flash radio image
V3.Trackball Alerts are here at last!!! i would like to thank the creator of Light flow for allowing me to cook in the lite version of his app, The light flow app is probably the best trackball alert ive ever seen, Allows you to set trackball color to the type of alert it is. i used this app all night on my first version of the GRI40 and loved it so much i had to email and ask if i could use it. so yes i got permission from him to cook his app in. all the features of the rom are same as V3 without. Managed to get A2sd working with trackball alert app after i had already cooked the first one up. so take your pic, you can have trackball alerts or just the regular GRI40 .. Also did a internal task killer mod on this V3.1 which in turn SHOULD free up more ram my processes status is showing 285MB of free ram so ENJOY, Feedback is always welcome, use Radio image above if you want.
Md5 checksum: c3baa58db0f47e067e6674078cd0620d
Download link: http://www.mediafire.com/?y737tdq8kxevzro
Reserved...
I took down V4 due to many issues with it, started from scratch on this V4.1 build, added Spare parts, Terminal, and Adobe flash player. Removed Books Apk and Amazon Mp3. Fixed Camera issue that plagued V4 Should also be flashable from Clockwork Mod. IF not use Ra passion please to flash. Also took off Light flow TB alerts as stock google TB alerts seem to be working with this build.
Rooted, Busyboxed, Zipaligned, deoxed, and all the other flavors from my previous rom builds.
new an improved V4.1
Download link: http://www.mediafire.com/?8da00nvd0nbu2ob
Enjoy
Gone back to school support an updates will slow down majorly, but please feel free to download mod, and make these roms better than i made um
quick q, how do u enable a2sd? just make a ext3 partition? or do i have to run some commands as well
thanks for doing this!
Was there a separate radio in the 2.4 dump, cuz I missed that fact?
Btw this rom is real quick. I'm loving it
Sent from my Nexus One using XDA App
Any chance of cooking in Trackball Wake?
knightnz said:
Any chance of cooking in Trackball Wake?
Click to expand...
Click to collapse
if someone would send me a link to the script, id be more than happy to try cooking it in
http://forum.xda-developers.com/showthread.php?t=966635
I dont have such script, but you can take a look at this Build from Superatel, GB 2.3.3 with track ball wake working here (i'm running it-very smooth and stable). Perhaps you should ask him for Trackball wake solution
Anyway, thanks for your time building this job.
Just to let you know, flashed ver2 over ver1 with cache and dalvik-cache wipe and all is great!
Took a while to boot but a2sd all setup nicely now.
+1 for trackball wake
Anyone tried trackball alert ?
Many thanks
How is the battery life and USB transfer speed with this ROM?
bryanchapman9999 said:
Just to let you know, flashed ver2 over ver1 with cache and dalvik-cache wipe and all is great!
Took a while to boot but a2sd all setup nicely now.
+1 for trackball wake
Anyone tried trackball alert ?
Many thanks
Click to expand...
Click to collapse
Can I ask how u set up a2sd? And smali patch with trackball alert and a reboot and trackball alert works perfect
Sent from my Nexus One using XDA App
meechto said:
How is the battery life and USB transfer speed with this ROM?
Click to expand...
Click to collapse
Usb transfer speed is actually pretty fast, actually shocked me since i still use USB 1.0 and battery life is still being watched, seems to be pretty great life though
should we use ext2, ext3 or ext4?
thanks
rockuman_ex said:
should we use ext2, ext3 or ext4?
thanks
Click to expand...
Click to collapse
Ext2 or ext3 is fine, ext4 is still unsupported on first boot, my phone automatically made a ext2 partition at 512Mb no swap an set it all up for me. so just try that first then if you want more, reflash it with a bigger partition set up
malikadnanm said:
Can I ask how u set up a2sd? And smali patch with trackball alert and a reboot and trackball alert works perfect
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Did nothing to setup A2SD, it does it automagically Took a while to boot though. This was after flashing v2 over the top of v1.
Thanks for the tip on trackball alert
Bryan
Well ive spent the last 7 hours cooking up 50 different roms trying to get a working trackball wake, i had ONE working trackball wake but it seems to disable all the other hardware buttons, so if anyone has ANY idea on how to do this please shoot me a message, hope all are enjoying the rom till i can get this trackball mod working
nocturnalmike said:
Usb transfer speed is actually pretty fast, actually shocked me since i still use USB 1.0 and battery life is still being watched, seems to be pretty great life though
Click to expand...
Click to collapse
Sounds great Could you please paste the MD5 Hash next to the download links?
Edit: Didn't have the patience to wait for the MD5 Hash So downloaded and installed the ROM. Quick boot as said in the OP. Looks pretty good so far. Haven't tried it out extensively though. As of now, I found the USB transfer speed to be pretty decent. Not the best that I have experienced so far but definitely better than the other Gingerbread ROMs using the stock kernel. The Camera worked fine as well. Though I can not ascertain that it is 720p as I was not able to download the file to my PC. While accessing the Camera folder over USB, Windows7 says that the folder is either inaccessible or corrupted. Any idea why so? I was able to access the folder on my phone and the file played well. Will update more about the ROM as and how I use it. Thanks, buddy
Edit: One random reboot after restoring an application using Titanium Backup
Edit: I was able to access the Camera folder on my phone from my PC after restarting the phone once. Also the video is indeed 720p recorded at 12 fps.
I have tried quite a few Gingerbread ROMs out there and this one is just what I needed - plain vanilla stock ROM patched with the Apps2SD script.
Looking forward to the track ball awake and battery percentage. Will report regarding battery life after a few hours.
Edit: One more random reboot after unplugging the USB cable from the phone
Edit: One more reboot while copy data from phone to PC over USB
flashing this right now. Will report later tonight or tomorrow
meechto said:
Sounds great Could you please paste the MD5 Hash next to the download links?
Edit: Didn't have the patience to wait for the MD5 Hash So downloaded and installed the ROM. Quick boot as said in the OP. Looks pretty good so far. Haven't tried it out extensively though. As of now, I found the USB transfer speed to be pretty decent. Not the best that I have experienced so far but definitely better than the other Gingerbread ROMs using the stock kernel. The Camera worked fine as well. Though I can not ascertain that it is 720p as I was not able to download the file to my PC. While accessing the Camera folder over USB, Windows7 says that the folder is either inaccessible or corrupted. Any idea why so? I was able to access the folder on my phone and the file played well. Will update more about the ROM as and how I use it. Thanks, buddy
Edit: One random reboot after restoring an application using Titanium Backup
Edit: I was able to access the Camera folder on my phone from my PC after restarting the phone once. Also the video is indeed 720p recorded at 12 fps.
I have tried quite a few Gingerbread ROMs out there and this one is just what I needed - plain vanilla stock ROM patched with the Apps2SD script.
Looking forward to the track ball awake and battery percentage. Will report regarding battery life after a few hours.
Edit: One more random reboot after unplugging the USB cable from the phone
Click to expand...
Click to collapse
That's odd, I haven't had any reboots. This is the best and fastest rom out of all the gingerbread ones. Great job dev
Sent from my Nexus One using XDA App
meechto said:
Sounds great Could you please paste the MD5 Hash next to the download links?
Edit: Didn't have the patience to wait for the MD5 Hash So downloaded and installed the ROM. Quick boot as said in the OP. Looks pretty good so far. Haven't tried it out extensively though. As of now, I found the USB transfer speed to be pretty decent. Not the best that I have experienced so far but definitely better than the other Gingerbread ROMs using the stock kernel. The Camera worked fine as well. Though I can not ascertain that it is 720p as I was not able to download the file to my PC. While accessing the Camera folder over USB, Windows7 says that the folder is either inaccessible or corrupted. Any idea why so? I was able to access the folder on my phone and the file played well. Will update more about the ROM as and how I use it. Thanks, buddy
Edit: One random reboot after restoring an application using Titanium Backup
Edit: I was able to access the Camera folder on my phone from my PC after restarting the phone once. Also the video is indeed 720p recorded at 12 fps.
I have tried quite a few Gingerbread ROMs out there and this one is just what I needed - plain vanilla stock ROM patched with the Apps2SD script.
Looking forward to the track ball awake and battery percentage. Will report regarding battery life after a few hours.
Edit: One more random reboot after unplugging the USB cable from the phone
Edit: One more reboot while copy data from phone to PC over USB
Click to expand...
Click to collapse
damn dude, sorry to hear bout ti randomly rebooting on you, i hope it was just a bad flash with you an nothing else thats too serious, but ill look into it
FULL CREDIT TO lambgx02!
Original Post | CWM
Hi guys!
Lately my defy+ ( with the quarx ROM CM10-20121222-NIGHTLY-mb526) was slow and laggish.
I was planning to do a fresh install, but I've installed this tweak and the smartphone has come back from the dead!
Every app now opens fast and I don't have long pauses anymore.
The phone must be rooted.
Please post your experience and ROM, so we can help the developer and understand if this fix is good in order to put it as standard in the new builds!
Description
Quote Original Post link - Click Here
Download
Seeder-1.0alpha6.apk
Instructions
1) Install the apk and activate all the options (first time doesn't ask for root permissions)
2) Reboot the phone
3) Give to Seeder all the permissions needed
I'm 100% going to install it but I've read that it makes wakepoints and affects the battery more then usual. What is your experience?
Mavasilisk said:
I'm 100% going to install it but I've read that it makes wakepoints and affects the battery more then usual. What is your experience?
Click to expand...
Click to collapse
Well, I don't know if it's affecting the battery, I don't notice any change.. if you think about it, all the lag and slowness was causing also battery drain. So, maybe there is no big change.
After more 24 hours of usage, the performance change is huge :good:
I just installed it (CM7) and I must say that it seems to really reduce the lags in starting apps. Furthermore, I do not observe any additional wakelocks!
Btw: here is the original post
Seeder 1.1 is out here: http://forum.xda-developers.com/newreply.php?do=newreply&noquote=1&p=36264200
I've read some articles and replies about that.
The thing is that the random trick it's useless, the only thing is that the cpu is used every second, so the phone is never in sleep mode.
More details here http://www.xda-developers.com/android/entropy-seed-generator-not-all-its-hacked-up-to-be/
I confirm that the effect of this is close to zero. It does enlarge the entropy-pool but not a measurable gain in speed or reduce of lag. And if u use the .Zip and want to deinstall it, the uninstall zip does not remove all of it. I had to manually delete the files the zip installed. Simply open the zip and check what to delete!
Rein haun,
David
Gesendet von meinem MB525 mit Tapatalk 2
I see no change. Maybe I am too pesimistic.
ok, for some reason, thought build.prop q's were relevant to the kernel...
anyway, I edited build.prop in /system with RootExplorer's text editor. changed the value for wifi.supplicant_scan_interval from 30 to 120. no extra lines or spaces, etc- just changed the number, saved, then rebooted. it took an obscene amount of time to boot up and the device stopped going into deep sleep after a short while. I installed better battery stats to see what was wrong and the app indicated mmc_delayed_work under kernel or partial wakelocks (i forget which). I restored the original build.prop and the device worked like normal.
Is this a bug or is ICS/JB different enough from GB that you have to go through alternate means to change build.prop (eg flashing an update script from CWM, or something similar)?
I've tried this twice already and gotten similar results and the method by which I edited the build.prop was exactly the same as I used to edit it on GB without issue.
another thread I checked out in the S II dev thread indicated that this is possible- editing build.prop (wifi scan at least, on top of a few others parameters)- w/o issue, so....yeah.
alljokingaside said:
ok, for some reason, thought build.prop q's were relevant to the kernel...
anyway, I edited build.prop in /system with RootExplorer's text editor. changed the value for wifi.supplicant_scan_interval from 30 to 120. no extra lines or spaces, etc- just changed the number, saved, then rebooted. it took an obscene amount of time to boot up and the device stopped going into deep sleep after a short while. I installed better battery stats to see what was wrong and the app indicated mmc_delayed_work under kernel or partial wakelocks (i forget which). I restored the original build.prop and the device worked like normal.
Is this a bug or is ICS/JB different enough from GB that you have to go through alternate means to change build.prop (eg flashing an update script from CWM, or something similar)?
I've tried this twice already and gotten similar results and the method by which I edited the build.prop was exactly the same as I used to edit it on GB without issue.
another thread I checked out in the S II dev thread indicated that this is possible- editing build.prop (wifi scan at least, on top of a few others parameters)- w/o issue, so....yeah.
Click to expand...
Click to collapse
I have no idea why that would happen, but I guarantee you the interval is fine where it is. I've left my player on with wi-fi over a week.
Mevordel said:
I have no idea why that would happen, but I guarantee you the interval is fine where it is. I've left my player on with wi-fi over a week.
Click to expand...
Click to collapse
I'm recording atm but problem isn't replicating. go figure; well, if it does, I'll post a logcat. if not, good for me since I forget to turn the wifi off most of the time and especially in places with no open wifi. anyway, I was posting this in case someone else did come across a similar problem and had a solution since my searches led nowhere (searching for anything mmc_delayed_work related comes up with little useful info/apparently a lot of once-valid GB tweaks are "busted"/not in ICS code base)
whether or not the scan interval isn't exactly the point, why I'm pursuing it; it's the specific point atm, but the general point is device ownership- tailoring your device to your heart's desire; complete ownership. that's the premise behind this whole site as I'm sure everyone here is aware. if I did something to mess it up along the way, great. but if it is a bug or something with ICS code base, it's be nice to know. a lot of folk like messing with build.prop so it'd be nice to know what can or cannot be messed with.
atm, it does look like I messed something up when editing and saving- perhaps I added a space or line where it shouldn't've been- since the device is sleeping as it should, again, if I find something, I'll post the logcat.
thanks for the re:
alljokingaside said:
I'm recording atm but problem isn't replicating. go figure; well, if it does, I'll post a logcat. if not, good for me since I forget to turn the wifi off most of the time and especially in places with no open wifi. anyway, I was posting this in case someone else did come across a similar problem and had a solution since my searches led nowhere (searching for anything mmc_delayed_work related comes up with little useful info/apparently a lot of once-valid GB tweaks are "busted"/not in ICS code base)
whether or not the scan interval isn't exactly the point, why I'm pursuing it; it's the specific point atm, but the general point is device ownership- tailoring your device to your heart's desire; complete ownership. that's the premise behind this whole site as I'm sure everyone here is aware. if I did something to mess it up along the way, great. but if it is a bug or something with ICS code base, it's be nice to know. a lot of folk like messing with build.prop so it'd be nice to know what can or cannot be messed with.
atm, it does look like I messed something up when editing and saving- perhaps I added a space or line where it shouldn't've been- since the device is sleeping as it should, again, if I find something, I'll post the logcat.
thanks for the re:
Click to expand...
Click to collapse
I understand.
Thinking about it, mmc_delayed_work seems like it's tryng to catch up the SDcard or something. Did you reboot cleanly? That may be the issue.
Mevordel said:
I understand.
Thinking about it, mmc_delayed_work seems like it's tryng to catch up the SDcard or something. Did you reboot cleanly? That may be the issue.
Click to expand...
Click to collapse
No clue. what do you mean by "reboot cleanly"? if by that you mean, did I reboot using the reboot option in the power menu, then yes. always.
After restoring a backup and re-editing build.prop, sleep worked like gamebusters. Except, bluetooth auto-toggled on ("bluetooth is turning on"). After rebooting, it was stuck on the boot animation screen for a few minutes. A reboot after that pretty much boot looped it. I restored my backup afterwards...
Looking in the logcat (after editing), I noticed a ton of errors and permission denials.... Since I don't have much expertise here, I can't say for sure that they're normal but they seem to be abnormal. Wayyy more than I remember seeing when I browsed through before on a "clean" boot. But again, with the lack of expertise (or any functional knowledge for that matter)
==
Now, after having restored the backup before making the edits and rebooting, it seems to be stuck in a bootloop....huh. ok, after rebooting it 2x, it finally seems to have booted up "normally." Both before restoring (w/ edits and BT error) and after restoring (w/o build.prop edits), it's taking a lot longer to boot up than it used to....guesstimating 3-4 minutes. When it boots up, I get/got: "process system isn't responding" (both before and after restores now) and something about alarm error.
I've attached logcats of both pre- and post-event, if you're curious. As to "solving" this,I'm just gonna re-flash the PA ROM and wipe caches to get rid of these problems. ergh. device meets my foot against the wall is next on the checklist.
thanks again. I'd like to say, Stay classy, San Diego, but we all know San Diego and its class
Hello all,
This is my first post on XDA, so I apologize in advance if I'm in the wrong place. I've searched high and low for an answer to this, but all the threads I've come across are at least 5+ years old and don't directly relate to the issue I'm having.
Basically, here's what's going on. I have two app APK files that I have edited to change some of the resources in them. One of them is SwiftKey. I used APKEditor from the Play Store to replace two of the keyboard sounds included to custom ones. After I save the edited APK, I rename it to 'base.apk' and then replaced the 'base.apk' inside of the app's directory with the edited one. After doing this, everything seems to work fine, and the app continues to work normally with the new sounds I've added in.
However, the issue I'm having is that anytime I need to reboot my phone, any apps that I've edited the APK for disappear. After Android starts up, I can see the apps on my home screen for a second, and then they vanish. The folder for the app is still present inside of /data/apps, but the app does not appear under the list of installed apps anymore. I'm wondering if this is maybe because the modified APK isn't being signed right, or if I'm doing something wrong. I made sure the permissions were correct too after I replaced the base.apk file as well.
If there is another (better) way to do this, I am all ears! I'm pretty tech savvy, but I just recently switched from iOS to Android after not using Android for 4-5 years, so things are a bit different now than they were the last time I used Android.
Thank you for your help!
*EDIT- I also should mention that I am rooted, although that may have already been apparent