after wiping dalvik cache to flash a kernel....
this problem is caused when there are .odex files in /data/app folder than have permissions set so system can no write to them during the optimization process. There may be other causes, but this is the leading cause, i read about 15 threads on this, for alot of people its the app titanium backup odex file that causes the issue but there can be other programs. for these people the fix is uninstall and reinstall titanium backup. for me, i used es file explorer (root req) and i deleted any .odex (in data/app) that i found that didn't have write permissions for the system, i found two odex files that were rw- r-- r-- and deleted them. then i rebooted and the android is upgrading message did not come back (after 2nd reboot) at this point i reinstalled the two apps that had the odex files without w permission for system.
i assume the problem could also be fixed by changing the permissions on the odex files without having to reinstall them, but if the permissions were set like that for a reason, you'll want to set it back to rw- r-- r-- after you stop getting the android is upgrading message at bootup.
cheers guys, just made this thread because the other 15 threads i read on this topic were all lacking in useful information.
note: some outdated versions of ICS are known to have an issue where the system scans EVERY app on EVERY restart, this fix does not fix that. if your phone is rescanning EVERY app and not just the ones with odex w permission off then you need to update your ics version or get a custom rom that is up to date to fix this.
80 views today just gonna bump this once
NEED HELP
KronicSkillz said:
80 views today just gonna bump this once
Click to expand...
Click to collapse
HI,
FIRST OF ALL I AM REALLY THANKFUL TO EVERY MEMBER OF XDA DEVELOPERS. BECAUSE I HAVE LEARNT MANY MANY GOOD THINGS FROM XDA DEVELOPER. I DONT BELIEVE MYSELF AS A DEVELOPER I AM JUST AN ADVANCE USER.
I NEED HELP FROM YOU. I AM USING SONY XPERIA-S CELLPHONE WITH DUAL BOOT MANAGER DEVELOPED BY SENIOR XDA MEMBER letama HERE IS THE DETAILS OF MY DEVICE
MODEL SONY XPERIA-S
DUAL BOOT MANAGER BY letama
NATIVE OS ANDROID 4.0.4 ICS 6.1.A.2.55 STOCK ROOTED
ON LOOP HACK I AM USING ANDROID 4.2.2 CUSTOM ROM PAC VER 20.00
I AM ALSO USING FEW MODS ON STOCK OS LIKE
ACID AUDIO VER 4.00
BEATS AUDIO APPLICATION
BRAVIA ENGINE-2
CYBER SHOT CAMERA 4.72
NOW ABOUT MY PROBLEM. EVERY TIME I REBOOT MY DEVICE WITH NATIVE KERNEL (ICS STOCK) I AM GETTING MESSAGE ANDROID IS UPGRADING AND APPLICATION COUNT UP TO 58. THEN STARTING APPLICATIONS. THEN PHONE WORKS PROPERLY. BUT IT TAKE LONG TIME TO START.
I HAVE THIS PROBLEM SINCE I THINK I USED ABOVE MODS SO NO PROBLEMS WITH DUAL BOOT MANAGER BECAUSE THIS PROBLEM STARTED BEFORE USE OF DUAL BOOT MANAGER. THE CUSTOM ROM IS WORKING FINE AND NO ISSUES
I HAVE TRIED THIS TO SOLVE
FIRST I HAVE CHECKED FILES IN /DATA/APP BUT I HAVE NOT FOUND ANY ODEX FILES IN THIS FOLDER.
THEN I HAVE CLEANED DALVIK CATCH AND ALSO CLEANED DATA IN TWARP RECOVERY
THEN I FLASHED STOCK ICS 6.1.A.2.55 KERNEL
BUT STILL NOTHING WORKED FOR ME. PLEAS HELP ME IN THIS REGARDS. THANKS IN ADVANCE.
first of all there is no need to use all caps, secondly i answered your question in the last comment of my first post.
you need to get a newer version of ics or a custom rom thats been updated to fix this bug that was part with some old stock versions of ics and GB.
if u like the stock rom, just find a custom updated version of ics that has bloatware removed and memory leaks fixed, there is one available for most mainstream devices, the one i use is for my device though and is not supported on your phone.
if u like custom roms get somethign like cyanogenmod last stable release just google cyanogenmod "your phone model here" and it shoudl come up
KronicSkillz said:
first of all there is no need to use all caps, secondly i answered your question in the last comment of my first post.
you need to get a newer version of ics or a custom rom thats been updated to fix this bug that was part with some old stock versions of ics and GB.
if u like the stock rom, just find a custom updated version of ics that has bloatware removed and memory leaks fixed, there is one available for most mainstream devices, the one i use is for my device though and is not supported on your phone.
Click to expand...
Click to collapse
Hi. Thanks for your reply. I found the reseon for my above mantion problem. As I mantion I m using acid audio engine version 4 I have restored my cwm backup which was taken before the installation of acid audio. After restoration android is upgrading msg gone and phone boot normally. Then I tried different versions of acid audio like 5 and the latest 7 but after instalation the problem comes back so there must be something in acid audio package. So plz if u have some time then plz help me in this because apart from problem this audio mod is very nice. I herewith paste the build prop lines which acid audio adds during installation for your reference.
###AC!D Sound Tweaks by R-ikfoot###
#Sony Xloud
ro.service.swiqi.supported=true
persist.service.swiqi.enable=1
ro.semc.sound_effects_enabled=true
ro.semc.xloud.supported=true
persist.service.xloud.enable=1
#Resampling Tweaks
af.resampler.quality=255
af.resample=48000
ro.audio.samplerate=48000
ro.audio.pcm.samplerate=48000
persist.dev.pm.dyn_samplingrate=1
persist.audio.samplerate=48000
persist.audio.pcm.samplerate=48000
persist.af.resampler.quality=255
persist.af.resample=48000
#One X+ Beats
persist.tegra.nvmmlite = 1
persist.audio.SupportHTCHWAEC=1
htc.audio.swalt.enable=1
htc.audio.swalt.mingain=14512
ro.audio.pcm.samplerate=48000
i dont think it has anything to do with what you posted, but im not 100% sure
my comments:
1. why do u need this sound tweak?
2. have u tried the same installation on another rom... everything i've read about rescanning all apps is a problem with stock ics 4.0.4 or some GB stock roms, which is fixed by upgrading to newer stock ics or custom roms.
3. have you contacted the developer of the tweak you are adding and asked him about it? i dont know anything about audio addons because i mostly play music in my car over bluetooth and its always sounded incredible so i've never had a need to tweak it.
4. what lead you to think that the build.prop changes are causing the problem?
5. without knowing what other modifications this audio tweak you are using does it hard for me to even try to figure this out.
6. i dont see why a bunch of audio setting changes would cause your phone to scan all apps every restart...
7. this thread is not meant to deal with this issue caused by things other than dalvik wipe/kernel upgrade/old bug in some versions of GB/ISC
does your acid audio addon or w/e its called make changes to the kernel? if so that is more likely the issue, have u checked permissions of all your files in /app folder
I don't get it. Every single app in my data\app folder is rw-r--r-- Should it be something else??
are you getting the kernel upgrading on every boot?
i think the permission problem is the .odex not the apps, i think its normal for the apps to all be rw r r
i thought it was both app and odex at first but i think just the odex is the issue. not 100% sure, either way if you are seeing the error on boot play with the permissions, or reinstall apps in question if that doesn't work. start with the odex permissions i think you are right and the apps are rw r r by default. therefore that probably isn't the issue.
i just did another kernel upgrade so i tried the method of changing permissions, it doesn't seem as reliable as uninstall reinstall.
when i changed permissions the optimizing of app went away but i still got annoying upgrading message.
i recommend uninstalling and reinstalling any apps that have odex in data/apps folder. i'm still not 100% sure why this fixes it but it does for me.
the permission changes seem like they only fix the issue sometimes
Hi Kronic,
I've got a Nexus 4 on stock and rooted (updated to 4.2.2) and constantly get the "Android is upgrading" on every boot. I've had this issue for sometime now and only every so often will I dedicate time to finding a solution with no avail. I updated a couple of days ago, had to do a factory reset and upon booting up that was the first message.
I had a looked into the data/app file and I do not have a single .odex file, all apk. I do have a strange file in that folder though, sensor_ctl_socket with permissions set to rwx-rw-rw
Thoughts?
its normal for it to happen after a factory reset, you should only look into fixing it if it continues this behavior after multiple reboots
KronicSkillz said:
its normal for it to happen after a factory reset, you should only look into fixing it if it continues this behavior after multiple reboots
Click to expand...
Click to collapse
Hi Kronic, thanks for the reply. Notice the key word EVERY boot/reboot . Granted, I don't have to reboot or power off my phone often BUT when I do it is annoying to see the Android is upgrading message and it takes a while to update all of the apps. (I actually had to reboot a few times while fixing a gallery/camera issue).
I've searched multiple forums/posts/pages for a solution and have found nothing. I tried undoing the Dalvik integration as recommended on this postand that didn't help either.
what version of android are you using, are you possibly using the bugged version? you did a factory reset and you haven't updated right? there was a few versions of android that have this bug and have to be updated to be fixed. aside from that i'm not sure what else it could be, let me know if you've already updated we'll look into some other solutions.
KronicSkillz said:
what version of android are you using, are you possibly using the bugged version? you did a factory reset and you haven't updated right? there was a few versions of android that have this bug and have to be updated to be fixed. aside from that i'm not sure what else it could be, let me know if you've already updated we'll look into some other solutions.
Click to expand...
Click to collapse
Rooted, stock on 4.2.2 (see image attached) Thanks for your help
you might wanna see if reinstalling apps fixes it but its wierd cuz u have a fairly new version of android.
kill .odex junk file
Bammed the "Thanks" button on this post, for solving this nutcracker.
KronicSkillz said:
after wiping dalvik cache to flash a kernel....
this problem is caused when there are .odex files in /data/app folder than have permissions set so system can no write to them during the optimization process. There may be other causes, but this is the leading cause, i read about 15 threads on this, for alot of people its the app titanium backup odex file that causes the issue but there can be other programs. for these people the fix is uninstall and reinstall titanium backup. for me, i used es file explorer (root req) and i deleted any .odex (in data/app) that i found that didn't have write permissions for the system, i found two odex files that were rw- r-- r-- and deleted them. then i rebooted and the android is upgrading message did not come back (after 2nd reboot) at this point i reinstalled the two apps that had the odex files without w permission for system.
i assume the problem could also be fixed by changing the permissions on the odex files without having to reinstall them, but if the permissions were set like that for a reason, you'll want to set it back to rw- r-- r-- after you stop getting the android is upgrading message at bootup.
cheers guys, just made this thread because the other 15 threads i read on this topic were all lacking in useful information.
note: some outdated versions of ICS are
known to have an issue where the system scans EVERY app on EVERY restart, this fix does not fix that. if your phone is rescanning EVERY app and not just the ones with odex w permission off then you need to update your ics version or get a custom rom that is up to date to fix this.
Click to expand...
Click to collapse
Thank you for extremely for this info.... Thought I was gonna have to re flash my phone again
Night_1 said:
Thank you for extremely for this info.... Thought I was gonna have to re flash my phone again
Click to expand...
Click to collapse
then push the thank you button
Related
Ever since I received the upgrade to gingerbread (first 4.06 and now 4.08), Sense will get shut down when I am in other applications. Then when I hit the home button I get the white "HTC" screen and then sense has to start up and reload all my home screens and widgets. It typically happens when I use the browser but has sometimes happens when in other applications.
Here are the things I've tried to keep this from happening:
* reducing the number of things on my home screens
* removed all widgets to try and reduce the memory footprint
* factory reset/cleared dalvik cache
* renice <htc.com.launcher process> -20
* installed Auto memory manager (AMM) and set it to "aggressive" mode
* using AMM reset the priority of "HTC Sense" from 6 down to 2 and specified "always keep alive" but the kernel seems to just reset the priority.
What's really annoying is when I look at the list of processes, things like facebook and weatherbug have a higher (meaning lower number) priority than Sense. Does anyone have any idea how to force Sense to be given priority over other apps so it can stop from being shut down?
tia,
John
swindelljd said:
Ever since I received the upgrade to gingerbread (first 4.06 and now 4.08), Sense will get shut down when I am in other applications. Then when I hit the home button I get the white "HTC" screen and then sense has to start up and reload all my home screens and widgets. It typically happens when I use the browser but has sometimes happens when in other applications.
Here are the things I've tried to keep this from happening:
* reducing the number of things on my home screens
* removed all widgets to try and reduce the memory footprint
* factory reset/cleared dalvik cache
* renice <htc.com.launcher process> -20
* installed Auto memory manager (AMM) and set it to "aggressive" mode
* using AMM reset the priority of "HTC Sense" from 6 down to 2 and specified "always keep alive" but the kernel seems to just reset the priority.
What's really annoying is when I look at the list of processes, things like facebook and weatherbug have a higher (meaning lower number) priority than Sense. Does anyone have any idea how to force Sense to be given priority over other apps so it can stop from being shut down?
tia,
John
Click to expand...
Click to collapse
with any OTA its recommended to do a factory reset. did you do this? its a pain to loss all your data but it might fix your problems.
sorry i didnt have my morning coffee yet.... If you wiped dalvik then that means you have root. your phone is not shutting down. something is killing rosie (the sense launcher.) and that why the white HTC splash screen comes up again. What rom are you runing? i know its the OTA but is it the RUU or one of the devs roms based off RUU??
swindelljd said:
Here are the things I've tried to keep this from happening:
* reducing the number of things on my home screens
* removed all widgets to try and reduce the memory footprint
* factory reset/cleared dalvik cache
Click to expand...
Click to collapse
If you read his entire post you would know he did a factory reset.
My best guess is to go back to stock sense before the last ota (by rooting and flashing or whatever way you wish..sbf or whatever) then download the ota on your computer and try manually updating your phone..if that doesn't work then I don't know
/Droid3
What about bulletproofing the launcher with V6 Supercharger?
Sent from my ADR6300 using XDA App
RamAir02 said:
What about bulletproofing the launcher with V6 Supercharger?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
That worked for me.
synisterwolf said:
... i know its the OTA but is it the RUU or one of the devs roms based off RUU??
Click to expand...
Click to collapse
Most recently I am running the stock 4.08 version starting with applying the 4.06 RUU and then applying the 4.06 to 4.08 update file. I do have root and really use it for monitoring/managing the /data/data partition.
RamAir02 said:
What about bulletproofing the launcher with V6 Supercharger?
Click to expand...
Click to collapse
Whoa, that looks pretty serious. I'll have to read that through first so I can understand what it's doing and so I don't accidentally brick my phone.
swindelljd said:
Most recently I am running the stock 4.08 version starting with applying the 4.06 RUU and then applying the 4.06 to 4.08 update file. I do have root and really use it for monitoring/managing the /data/data partition.
Whoa, that looks pretty serious. I'll have to read that through first so I can understand what it's doing and so I don't accidentally brick my phone.
Click to expand...
Click to collapse
There's no risk of brick with v6. It just tweaked a couple parts of the kernel.
Sent from my ADR6300 using Tapatalk
swindelljd said:
Whoa, that looks pretty serious. I'll have to read that through first so I can understand what it's doing and so I don't accidentally brick my phone.
Click to expand...
Click to collapse
You'll just want to make sure you have busybox 1.18.2 installed, then run the script with Script Manager, and you'll want to select either 6 or 7 (I use option 7), then reboot. It won't brick your phone, but you can always run a nandroid backup to have something to fall back to.
RMarkwald said:
You'll just want to make sure you have busybox 1.18.2 installed, then run the script with Script Manager, and you'll want to select either 6 or 7 (I use option 7), then reboot. It won't brick your phone, but you can always run a nandroid backup to have something to fall back to.
Click to expand...
Click to collapse
Is this the correct script manager app: https://market.android.com/details?id=os.tools.scriptmanager ?
Noob question, how do I check which version of busybox I have installed. I found one in TitaniumBackup that is 1.18.14 but that looks like it is local to TitaniumBackup. I did find "toolbox" in /system/bin which looks like the stock rom's version of busybox. Is this what I should be looking at or is busybox installed somewhere else?
swindelljd said:
Is this the correct script manager app: https://market.android.com/details?id=os.tools.scriptmanager ?
Noob question, how do I check which version of busybox I have installed. I found one in TitaniumBackup that is 1.18.14 but that looks like it is local to TitaniumBackup. I did find "toolbox" in /system/bin which looks like the stock rom's version of busybox. Is this what I should be looking at or is busybox installed somewhere else?
Click to expand...
Click to collapse
Yes, that's the app.
Download this app as well: Busybox Installer
It'll tell you what version you have (if you have it), then you can select what version you want to install. No need to adjust where it installs, just leave that at the default, just select version 1.18.2, then hit Install.
I read through the script just to get a sense (no pun intended) of what it was doing and then installed Busybox 1.18.2 and applied setting 11 "Hard to kill launcher" from the script. I've done a bunch of browsing to sites that normally caused Sense to get shut down and so far so good.
I initially installed busybox with symlinks and it the script threw a ton of errors so I reinstalled with symlinks to fix that.
Thanks for all the help. For completeness, here is a link to V6 Supercharger so all the links are in this one thread http://forum.xda-developers.com/showthread.php?t=991276 .
One thing I did have to change because I am running Sense and not a stock android launcher is the name of the launcher process itself.
On line 64, I changed this "pidof com.android.launcher" to this "pidof com.htc.launcher"
will the V6 script it just tells the android memory system to not reclaim memory from the launcher app so it stays on no matter what happens. only way to kill it is to go to settings and FC the launcher. also with the script you cant brick the phone because its not ran till after the phone boots. The term brick means : that the phone will not boot at all. you just have a phone that does nothing at all not even turn on. You can soft brick the phone meaning the software will not boot. all you need to do is make a backup before installing the script and you will always have a way back if anything happens.
for me i run the beta V6 script option under -=*512HP*=- which is more of a balanced one with bullet prof launcher and its is wonderful. but each phone is different so just try them out and see what works for you.
synisterwolf said:
... You can soft brick the phone meaning the software will not boot. ...
Click to expand...
Click to collapse
I did "soft" brick the phone recently when I deleted build.prop and forgot to put a new one in it's place before I rebooted. Had to use adb to access the phone to restore build.prop. I can tell you that was a nervous few minutes after I realized what I had done. Definitely not a recommended activity.
swindelljd said:
I did "soft" brick the phone recently when I deleted build.prop and forgot to put a new one in it's place before I rebooted. Had to use adb to access the phone to restore build.prop. I can tell you that was a nervous few minutes after I realized what I had done. Definitely not a recommended activity.
Click to expand...
Click to collapse
Yeah, you kinda need that one there!
Good job getting it replaced using adb and all, good to hear you figured it out!
swindelljd said:
I did "soft" brick the phone recently when I deleted build.prop and forgot to put a new one in it's place before I rebooted. Had to use adb to access the phone to restore build.prop. I can tell you that was a nervous few minutes after I realized what I had done. Definitely not a recommended activity.
Click to expand...
Click to collapse
yes that will do it. lol i did that a long time ago when i wanted to edit it my fat finger deleted it. now as good practice i always make a copy of it but add .bak at the end of it so if i do delete it i can just replace it before reboot.
I've been using options 1, 8, and 12 in the V6 Supercharger and my phone has been running great. What options did everyone else choose?
Hi everyone,
this is my very first post so I hope I'm not making any mistake posting here instead of somewhere else.
I installed this ROM yesterday (incredible and awesome job, btw) but no conversations.apk was in it and I had to install Hardcent SMS to handle the messaging.
Is it normal or I made something wrong? I also checked the rom .zip before posting.
I searched for infos in the official thread (http://forum.xda-developers.com/showthread.php?t=1399238) but I've found nothing.
Thanks in advance,
--tyler--
Dunno - unless you didn't flash bigxie's gapps file immediately afterwards before rebooting, but in that case you'd be missing more than just messaging. I assume you did a full wipe first as per instructions.
I installed Apex 1.0.2 and have the native sms apk, although I didn't test it since I prefer Handcent and have disabled native texting.
Maybe your flash had a hiccup, you could try reflashing...
or open up the zip file and see if there's a conversations.apk in it.
I just updated from Apex 1.0.0 to 1.0.2 and I had the stock SMS application on both versions. You may have forgotten to flash the gapps package. Unlike CM7 and other Gingerbread ROMs, the gapps package needs to be flashed along with the ROM every time you update/install.
Clancy_s said:
Dunno - unless you didn't flash bigxie's gapps file immediately afterwards before rebooting, but in that case you'd be missing more than just messaging. I assume you did a full wipe first as per instructions.
I installed Apex 1.0.2 and have the native sms apk, although I didn't test it since I prefer Handcent and have disabled native texting.
Maybe your flash had a hiccup, you could try reflashing...
or open up the zip file and see if there's a conversations.apk in it.
Click to expand...
Click to collapse
Hi Clancy_s,
thank you for your reply. I followed the instructions line-by-line as always and also I tried to download again the rom and flash it a second time but nothing...
As I said, I also checked the zip file in order to get the apk and put it manually on /system/app, but I couldn't find it!!
Now you're telling me that you have the stock messaging app on your phone and you also have the same rom I have... that's strange!
Could you please check your rom .zip and look for conversation.apk?
--tyler--
synaesthetic said:
I just updated from Apex 1.0.0 to 1.0.2 and I had the stock SMS application on both versions. You may have forgotten to flash the gapps package. Unlike CM7 and other Gingerbread ROMs, the gapps package needs to be flashed along with the ROM every time you update/install.
Click to expand...
Click to collapse
I swear I did it!
--tyler-- said:
Now you're telling me that you have the stock messaging app on your phone and you also have the same rom I have... that's strange!
Could you please check your rom .zip and look for conversation.apk?
--tyler--
Click to expand...
Click to collapse
I can but it'll have to wait a couple of days - I'm away from home for the next 3 and like to use a pc for that sort of thing.
I upgraded from Apex 1.0.0 so it's possible the conversation.apk carried over from there...
goo-inside.me/roms/fabolous/maguro/bigxie_maguro_Apex_v1-0-2.zip
<-- link to actuall gapps
i also need to reinstall it after updating from 9.2 -> apex1.0 (namechange) to get sync with google acc
so...I downloaded the file...again... (third time!) and unzipped it.
Am I crazy or there is no conversation.apk in it?
seriously guys: where is it?
it should be in System/App, am I right?
why it isn't there?
today I wiped my phone and flashed for the third time, with the brand new file downloaded few seconds before, after that I flashed the gappas (without rebooting the phone) and THEN I made a reboot.
Still no conversation.apk....??
--tyler--
im on easydoesit v2.2 and im having trouble mounting in root explorer...if i reboot enough times i can get it to mount but the files that i delete or add don't save...
for example...im trying to delete apex launcher since i have go launcher...when i delete the apk it says file deleted...but when i click refresh it comes back
is this a problem specific to the rom or are others having the same problem on other ICS roms?
if anyone knows how to fix this please help
thanks in advance
I had some odd Superuser issues on Raver's ROM, so I flashed Wrathdu's latest Superuser binary and it seems to have fixed that. Search for Wrathdu or Zeppelinrox, he posted it too
-the ultimate black dragon-
forum.xda-developers.com/showpost.php?p=22643465&postcount=8328
is this the exact one? want to make sure its the correct one for our phone model
This is for the Galaxy S2 on T-mobile, for the LG Volt StockWalk go here
What this rom is.[/COLOR]
===========[/SIZE]
This a rebuilt stock deodexed rooted base, with some added csc tweaks and build.prop tweaks.
I have also updated the apps to their latest versions and included a couple extra Google apps (keep, and voice). Also included is
Mi FileExplorer, and Adobe Flash.
But this rom will be kept as the stock Touchwiz feel, I didn't like the way it was debloated by some so I decided to do it myself. And
I like the result.
Some of the features added
=================
Flash Player preinstalled and working - Apk Thread Here Thanks to stempox.
Browser has the user agent set to desktop by default
Browser exit option
Browser Bookmarks are editable
Carrier IQ removed (I consider that a feature lol)
Internet tweaks
4 way reboot - Credit to bryan2894
data/app folder for uninstallation of extra apps
proper root and busybox
Removed Preload Folder
data/app support
HD/off screen playback youtube - credit to theos0o
It does not have (yet)
=============
Unrestricted tethering/data cap (coming to a future build, i wanna take my time with smali editing though... its been a while)
Any kernel changes (never will, you can flash your own[I flash Tiberius])
Volume rocker wake (I hate it)
Flashbar (The amount of info on this is dang near nonexistant, so any help would be appreciated)
Issues
====
Starting with 1.1.1 there will be a tag to the right stating which post the release
started on for easy navigation later for people looking for issues in a particular version
Older
1.0.0
I ran into a no boot issue when wiping cache and dalvik cache, and when trying to flash a kernel, I am working on ripping a new base to attempt to resolve those issues, other than that no issues. The new base will be the next build.
1.0.1
superuser broken see post 13 for fix
1.0.3
left some stuff out by accident, skipping.
1.0.4
if google search is missing just download from play store.
1.1.1 post #36 is the release post
Google now settings don't stick, uninstall googlequicksearchbox.apk from system/app , reboot and install from market.
or just clear the data for google search...
Current
1.2.0 (lite) post #57 is release post
over 30 days of stability!!!!!
1.3.0 Updated version of 1.2.0
post #120 is the release post (if using twrp dont fix root)
Instructions
========
DISCLAIMER: I RUN THIS ON MY OWN PHONE AS MY DAILY DRIVER.
BUT I AM NOT RESPONSIBLE FOR BRICKED DEVICES OR SOMEONES
INABILITY TO READ. I WILL HOWEVER DO MY BEST TO HELP WITH
ANY ISSUES...
TWRP IS RECOMMENDED I AM CURRENTLY USING 2.5
-1. have a nandroid backup in case you have issues
0. use the superwipe scripts to eliminate any issues if you need them.
1. Wipe cache, dalvik cache, factory reset and system.
2. Install rom
2.5. If asked to fix root, don't.
3. Reboot
4. Wait for it to boot and have fun (works best if you
wait a few minutes after it boots for the signal to settle,)
If you use CWM recovery please let me know if it works.
Downloads
=========
Older
1.0.0 - Initial build
1.0.1 - Rebuilt base rom
1.0.3 - Uses chainfire su instead (skipped)
1.0.4 - removed boot sound, fixed flash player preinstallation
1.1.1 - Lots of internal revisions and prep for longterm stability. So far 95% stability, one hiccup. see if you can find anything else.
all old links broken and i have no backups of those
Current
1.2.0 - Lite version, no extra widgets, swype, tmemo or extra live wallpapers. (more system memory, no other apps removed.) over 24 hours of stability!!!!!
1.3.0 - update release for 1.2.0 (if using twrp dont fix root)
Changelog
=======
1.0.0 - Initial Release
1.0.1 - The awesome has begun. Totally re-done from scratch in ubuntu with dsixda's kitchen.
after some thorough testing it shows to be more stable and you can flash compatible kernels and tweaks with no issues, after wiping cache and dalvik cache you may have a slightly longer boot
1.0.4 - Uses Chainfire su v1.25, removed boot sound. fixed preinstallation of flash.
1.0.5 to 1.1.1 - Removed preload folder, updated apps, fixed broken apps, did some tidywork on the app naming for future upgradibility.
1.2.0 - slimmed way down to give 77 mb of space on /system compared to 39mb... removed swype, tmemo, some widgets and wallpapers (check screenshots... what you see is what you get.)
1.3.0 - Same as 1.2.0, Updated superuser and about 5 other apps.
Thanks/Credit
============
Koragg618 - 1.0.0 Base
Google
XDA
bryan2894 - 4 way reboot mod
chainsdd - superuser on versions 1.0.1 and 1.0.2
stempox - Adobe Flash apk
Jamison904 - wipe scripts
Powered by SuperSU - on version 1.0.0 and 1.0.3 and up
theos0o - HD Youtube with off screen playback
If you like this rom and want to use it as a base I'm cool with that. Please give credit to those above when you do.
THREAD RULES
============
i have some ground rules i wanna throw out early on so that everyone knows. I know there are rules and guidelines on xda about searching and whatnot before you post blah blah blah.
screw that... in this thread these are my guidelines (xda is total law over these obviously... what a mod says goes...) i suggest.
1. chit chat is cool as long as it semi-pertains to this rom. I've gotten great ideas and suggestions from chit chat.
2. if a total noob asks a total noob question, don't rip his/her ass for it. answer it or stfu and i will answer it. I don't care if the answer was one page back or in the op... be nice about it.
3. suggestions, feedback, and criticism negative or positive is encouraged. ESPECIALLY NEGATIVE CRITICISM. i'm super serious. the whole point of the rom is to rid all of the crap that annoys you.
4. I will always update the OP (original post, first post) whenever there is an update. and while i am working on the rom i update it super often (every few mins sometimes)..
5. eta requests are allowed.. and ill give one... but know that the e in eta stands for estimated.
Screenshots (1.2.0)
==============
Great
Sent from my SGH-T989 using xda premium
Mine....:thumbup:
Sent from my SGH-T989 using xda premium
New build is up. let me know if you find any issues at all. I cant find any yet.
I liked at but I had no play store. Installed an apk but that didn't work either, would just close immediately. That was the only issue I found.
Sent from my SGH-T989 using xda app-developers app
gariputo said:
I liked at but I had no play store. Installed an apk but that didn't work either, would just close immediately. That was the only issue I found.
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
try the new build, its completely rebuilt, but as an fyi on the 1.0.0 version the playstore was working for me and phonesky.apk is in the preload folder and updated, along with gmscore and the others. also if you didnt let it settle for a couple minutes that may have been an issue. just try the 1.0.1 and lemme know. im running it now with no issues.
having trouble with superuser not asking for permissions on apps, any suggestions?
thank you for pointing that out. it may be the version of superuser, im gonna try another one and get another build out tonight.
NerdmastaX said:
thank you for pointing that out. it may be the version of superuser, im gonna try another one and get another build out tonight.
Click to expand...
Click to collapse
cool, i will wait, like you i hate volume rocker wake, at least on this phone...lol
edit: if its not to much to ask or i can do it when downloaded, but i also dont like on, off sound but if you do thats cool i can do it...thanks for the hard work and reply
yeah n/p ill remove the startup sound this go round, im deodexing again with the kitchen but this time im rooting with chainfire instead of chainsdd. manually replacing the superuser.apk and su binary fixes the root issue, i still want to let it finish deodexing the new build for that fresh build taste though. his superuser asks for an update on boot tho in the play store, so im gonna bundle it in so it doesnt ask.
NerdmastaX said:
yeah n/p ill remove the startup sound this go round, im deodexing again with the kitchen but this time im rooting with chainfire instead of chainsdd. manually replacing the superuser.apk and su binary fixes the root issue, i still want to let it finish deodexing the new build for that fresh build taste though. his superuser asks for an update on boot tho in the play store, so im gonna bundle it in so it doesnt ask.
Click to expand...
Click to collapse
sweet, Thank You, i will be waiting then report when all set up so you know whats going on...more info for you the better
this may fix your superuser issues for now while i work on the next build. i wanna do the tethering while i have the rom on the bench again.
NerdmastaX said:
this may fix your superuser issues for now while i work on the next build. i wanna do the tethering while i have the rom on the bench again.
Click to expand...
Click to collapse
if you want i can try that or i can wait no biggie to me, let me know
Hmmm, flashed the latest and still no Play Store. I am also not able to add a Google account. I waited 15 minutes after flashing. I am using Clockwork Recovery. I get stuck on the boot screen us TWRP. I did the appropriate wipes before flashing and cleared caches after.
gariputo said:
Hmmm, flashed the latest and still no Play Store. I am also not able to add a Google account. I waited 15 minutes after flashing. I am using Clockwork Recovery. I get stuck on the boot screen us TWRP. I did the appropriate wipes before flashing and cleared caches after.
Click to expand...
Click to collapse
4.1.2 is havinf trouble when wiping caches afterward, either dont wipe or use the cache wipe file from Jamison904. i dont wipe after flash anymore now...hope this helps
here is the link to it...http://forum.xda-developers.com/showthread.php?t=2235141.
just a helpful pointer if you think it gets stuck after wiping cache on twrp, it stays on the end of that loading bar what seems like forever but eventually does boot, so try giving it a little time, you may be thinking its stuck when its not. shouldnt take longer than 5 mins though.
btw new build is uploading now. root and flashplayer are working.
edit.... please read second post, the wipe scripts should solve our issues.
if i'm on ICS stock rooted, can i flash this in TWR to switch on over to JB?
850Mda said:
if i'm on ICS stock rooted, can i flash this in TWR to switch on over to JB?
Click to expand...
Click to collapse
i would reccomend you flash the newest radio beforehand for no issues (radios can be found here) UVMC6 should be at the top, also be sure to nandroid a backup first.
(note, im not certain if the radio is required, but its the way im using it, perhaps someone can clarify.)
Also... New build up... this should be the one to rule them all, very careful tweaking from here on out. please let me know of any issues you can find, also be mindful of how you wipe due to the symlink partition (read post 2)...
that being said i wiped normally even after flashing a kernel and i am not having any issues other than having to log into my google account again. and thats only when i wipe through twrp. but it does boot regardless if you wait. using the scripts should eliminate that problem though.
reflashed after downloading from my dev host link through the phone and i can flash dalvik cache and cache just fine again through twrp. so this is looking very promising and should turn out to be a stable base.
installed just fine, setup went good has superuser..set up to my liking now, using tiberus kernel with kernel tuner set both cores to max=1836 min=192, smartassv2, scheduler=row, and sd to 4096..only have internal sd so ( dont know if that matters but placebo effect makes me think it does...lol )......no volume rocker wake=awesome...no boot up or shut down sound=awesome.....steup screen to 220 density.....rebooted into TRWP recovery wiped cache/dalvik cache using Twrp advance wipe option installed miui player, s-voice, and transparent accuweather widget...running smooth and fast, wifi calling works...will report back after some more time but for now running great...awesome work, Thank You for the hard work!!!!
Many others besides myself seem to have an issue where adfree/adaway don't seem to work.
I tried manually replacing my hosts file in /etc with esfile (root explorer enabled and system mounted R/W). However after rebooting, my hosts file seems to have changed back to the default one.
The steps I took:
- Pasted edited hosts file into /system/etc/. (I'm rooted so no errors so far)
- Changed permissions to rw-r-r
- Reboot
And after the reboot the my larger hosts file seems to have been replaced with some default one.
I'm currently using MyRom, but I've tired checking any setting that would interfere with this. I've also tried a fresh install of MyRom and this still happens. I think other people may have similar problems with adfree/adaway because of a similar issue. I'm thinking about reverting to stock and trying it again?
dinjin said:
Many others besides myself seem to have an issue where adfree/adaway don't seem to work.
I tried manually replacing my hosts file in /etc with esfile (root explorer enabled and system mounted R/W). However after rebooting, my hosts file seems to have changed back to the default one.
The steps I took:
- Pasted edited hosts file into /system/etc/. (I'm rooted so no errors so far)
- Changed permissions to rw-r-r
- Reboot
And after the reboot the my larger hosts file seems to have been replaced with some default one.
I'm currently using MyRom, but I've tired checking any setting that would interfere with this. I've also tried a fresh install of MyRom and this still happens. I think other people may have similar problems with adfree/adaway because of a similar issue. I'm thinking about reverting to stock and trying it again?
Click to expand...
Click to collapse
are you using adfree program restored from TB or from the store? if so you need to use TB Restore Fix after running TB .
dragonstalker said:
are you using adfree program restored from TB or from the store? if so you need to use TB Restore Fix after running TB .
Click to expand...
Click to collapse
Not that I know of. I tried doing this on a fresh rom install too, with no adfree programs installed.
dinjin said:
Not that I know of. I tried doing this on a fresh rom install too, with no adfree programs installed.
Click to expand...
Click to collapse
I'll email the dev and see how the app is handling the host file. There is a known issue with some apps overwriting itself on reboot with (what i call) last known data.
Thanks for bringing this up.
* WHAT SPECIFIC APP ARE YOU USING (IE. ADAWAY)
I used adaway on official stock. Never had this issue with hosts reverting on reboot . It was however a pain to install, it fails and freezes multiple times before it works when ever I tried to update or revert the file.
Sent from my SM-N900T using Tapatalk 2
lm that guy said:
I used adaway on official stock. Never had this issue with hosts reverting on reboot . It was however a pain to install, it fails and freezes multiple times before it works when ever I tried to update or revert the file.
Sent from my SM-N900T using Tapatalk 2
Click to expand...
Click to collapse
Did somebody find a solution to this problem?? :crying::crying:
This does not answer your question directly, it gives you an alternative solution.
I use Adfree (for several years) by BigTinCan.com, it is easy to use and set up. I have never experienced a problem with it. Reboots work fine.
Sent from my SM-N900T using XDA Premium 4 mobile app
Seems strange that your host file would be changing if you never added a host adjusting app. Unless the ROM you are using includes it by default...
When I first started using AdAway on my GN3 it had problems.... It would start to update, stall, etc.... After a while however after an update or two, it worked itself out. Now I rarely think about it and manually updating it is very easy.