Database Develop

JIT in roms that already have it

I haven't had any luck enabling JIT in ROMs that come with it as an option. The DamageControl ROM as well as the PureROM both have it.
When you check the box to turn on JIT, it pops up a little text bar that says to reboot. I know you have to disable sense and the HTC lockscreen which I have done but my phone always goes to a bootloop.
The only ROM that I have found that doesn't have this issue is the darchdroid rom that has JIT and overclocking already enabled from the start.
Does anyone have any suggestions?
I have tried wiping dalvik after enabling JIT (by enabling, then shutting the phone off and booting to recovery with volume down key on powerup).

Jit can be so fickle sometimes =). try this
1. Download a different launcher(to use in place of Rosie.apk, aka sense launcher), i would recommend Launcher Pro, or ADW launcher from the market.
2. after installing it, hit your home button, and set the new launcher as default.
3. Set your background to an image on your SDcard
4. Open DCconfig, and go into banned apps. Ban SenseUI
5. Uninstall the XDA tapatalk app if you have it installed (if you really want to use it with JIT, search for xda 0.9, it works with jit)
6. reboot
7. Be sure you now have the vanilla lockscreen, and non-rosie launcher. If you have vanilla lock screen move to step 8, if you still have HTC lockscreen perform this code to be sure its gone....
Code:
adb remount
adb shell
cd /system/app
rm Rosie.apk
rm HtcLockScreen.apk
reboot
you should now have the vanilla lockscreen..
8. enable JIT in DConfig and reboot
Can you post a logcat if this gives you bootloops?

Ic3ROM has it, and when enabled, works flawlessly (only in version 2.8, though. I had problems with 2.9)
http://forum.xda-developers.com/showthread.php?t=663366

I'll keep messing with it. I've learned to Nandroid before doing it so I don't have to lose everything I've set up.
I've kinda given up on it for now. Maybe if the Hero gets official 2.2 it won't be such a big deal.
Frankly it'd be nice if ROM makers would enable JIT off the bat so it was on after you installed and then maybe people could go in and turn it off if they don't want it.

[Q] How do I get apps2sd ext 4 working on the Nexus one with the latest Cyanogen Mod?

Hey guys, I'm loving my new N1, but I keep running out of room for applications, and I wanted to know if I could implement Apps2sd ext2/3/4 or w.e to make more room. I like to use Cyanogen Mod, but I'm not sure how to implement it. If someone could help me, that'd be great! Thanks!

Ditto.
Sent from my Nexus One using XDA App

Try S2E or Link2ext in the market, our go look up Darktremors. Depending on what you want, the apps should be more than sufficient...

danger-rat said:
Try S2E or Link2ext in the market, our go look up Darktremors. Depending on what you want, the apps should be more than sufficient...
Click to expand...
Click to collapse
When i use darktremors, it doesn't work, but if I type in a2sd reinstall, it says location is read only

Try to fix permissions via ROM Manager. Also, try flashing DT before you flash gapps...

danger-rat said:
Try to fix permissions via ROM Manager. Also, try flashing DT before you flash gapps...
Click to expand...
Click to collapse
I tried that; it didn't work. Also, when I run a2sd reinstall, and reboot, its stuck on rebooting

Try the DT thread... xD

isikh said:
I tried that; it didn't work. Also, when I run a2sd reinstall, and reboot, its stuck on rebooting
Click to expand...
Click to collapse
Not been my experience. Strange that. What works for me...
Boot to recovery of your choice.
Do multiple wipes, both cache + dalvik-cache. Though just one wipe each is likely enough, IMO. Also wipe sd-ext.
Write your CyanMod of choice.
Write your gapps.
Write your DarkTremors. Go with the latest, OR, as others are insisting, stay away from that and go with the previous stable release. Latest works great for me.
Reboot device.
Wait a good minute after arriving at lockscreen and reboot device from lockscreen, OR find Quick Boot in app drawer if your power button is gorked (you'll need a working power button to reboot from lockscreen).
After reboot, wait a good minute at lockscreen. Then Proceed to open terminal session and start playing with a correctly installed (hopefully for you) DT2ext.
Lots of experts out there, but this has always worked for me. If you still need guidance, search in DarkTremor's thread to be advised about your partitions.

zero2cx said:
Not been my experience. Strange that. What works for me...
Boot to recovery of your choice.
Do multiple wipes, both cache + dalvik-cache. Though just one wipe each is likely enough, IMO. Also wipe sd-ext.
Write your CyanMod of choice.
Write your gapps.
Write your DarkTremors. Go with the latest, OR, as others are insisting, stay away from that and go with the previous stable release. Latest works great for me.
Reboot device.
Wait a good minute after arriving at lockscreen and reboot device from lockscreen, OR find Quick Boot in app drawer if your power button is gorked (you'll need a working power button to reboot from lockscreen).
After reboot, wait a good minute at lockscreen. Then Proceed to open terminal session and start playing with a correctly installed (hopefully for you) DT2ext.
Lots of experts out there, but this has always worked for me. If you still need guidance, search in DarkTremor's thread to be advised about your partitions.
Click to expand...
Click to collapse
Thank you, I figured it out.

DT is the best choice, but S2E is simpler than DT, it's avaliable in market

Kernel adiutor

Hi, I think this has been answered before but I can't find it..
Currently on 6.0.1. Kernel adiutor is crashing my phone whenever it applies settings on boot. Didn't happen on 6.0. Doesn't matter which rom cos I tried some but all freezes when applied settings.
I would be grateful if someone could point me in the right directions...

clear the app's app data before applying boot settings. Or get into supersu and disable root totally or for the app in particular more than likely its trying to set something that 6.0.1's kernel doesn't like. Alternatively you can delete folder /data/app/com.grarak.kerneladiutor from twrp which will effectively uninstall it. so you can reinstall it and start fresh.

StykerB said:
clear the app's app data before applying boot settings. Or get into supersu and disable root totally or for the app in particular more than likely its trying to set something that 6.0.1's kernel doesn't like. Alternatively you can delete folder /data/app/com.grarak.kerneladiutor from twrp which will effectively uninstall it. so you can reinstall it and start fresh.
Click to expand...
Click to collapse
Hmm. Ok. Does this happen to everyone? Or just me. Every kernel I tried gave me the same problem..

I'm using hells-Core N6: b13-M kernel & SuperSU v2.66 - No problems at all but I am unable to use under Settings -> Backup. The backup crashes my phone and has always done this so I just use Ti Backup for the app and save my profile settings.

Works fine with Pure Nexus.
Sent from my Nexus 6 using Tapatalk

Works fine chroma 01-10 you can try it

there could be two problems.
1)you are undervolting too much.
2) there is a bug in gpu governor on stock kernel(phone freezes on selecting simple_ondemand).
on boot,the app tries to set and which leads to crash/freeze/reboot.
So,delete app data from TWRP recovery from as mentioned by @StykerB

Can U check if Kernel Adiutor manage vibration intensity on chroma 1-10? I can't find this.

Help me diagnose "Files has stopped" error

Device info:
Oneplus 3T, OOS 5.0.1 (Android 8.0), rooted with Magisk v15.3
Recently, my phone has been giving me an error message "Files has stopped " whenever I do anything that requires me to pick a file. and sometimes for no reason. Some examples include selecting a module to install in Magisk Manager, or selecting a file to attach in Gmail.
I highly doubt my root is involved, as I even reflashed the OOS 5.0.1 OTA to try to fix it. I've also tried wiping the cache of the apps File Manager, Files, and all caches in TWRP recovery.
The problem disappears if I reboot into safe mode, meaning it might be due to a rogue app. The problem also seemed to start after I used a USB OTG thumbdrive if it helps, that's the only major thing I remember doing.
Any ideas? Is there any info I can find in logcat to diagnose the problem?

Emeraldscorpion said:
...
I've also tried wiping the cache of the apps File Manager, Files, and all caches in TWRP recovery.
...
Click to expand...
Click to collapse
Try clearing the apps' data in Settings>Apps.
Also, have you installed a theme using Substratum? If so, try disabling it for the File* apps.
Sent from my OnePlus3T using XDA Labs

BillGoss said:
Try clearing the apps' data in Settings>Apps.
Click to expand...
Click to collapse
Yup, already tried clearing data in Settings.
BillGoss said:
Also, have you installed a theme using Substratum? If so, try disabling it for the File* apps.
Click to expand...
Click to collapse
Not using Substratum. I think it's safe to rule out any modifications to /system or any that require root, as the problem persisted even after I reflashed the 5.0.1 OTA.

If you're by chance using Xposed, then Scoop app might be helpful. But if not, you would have to connect your phone to PC, run logcat from there and pause when crash occurs.
With logs it will be easier to debug

przemcio510 said:
If you're by chance using Xposed, then Scoop app might be helpful. But if not, you would have to connect your phone to PC, run logcat from there and pause when crash occurs.
With logs it will be easier to debug
Click to expand...
Click to collapse
I've tried to browse it on-device using the app CatLog, but I have no idea what I'm supposed to be looking for! Any tips on what I should be focusing on?

Emeraldscorpion said:
I've tried to browse it on-device using the app CatLog, but I have no idea what I'm supposed to be looking for! Any tips on what I should be focusing on?
Click to expand...
Click to collapse
Maybe do it another way - start logging in an app, make Files crash and then stop. Paste the log at pastebin.com and link it here, we will see what's wrong

Been MIA due to exams.
I was trying the adb logcat method when I realised that the problem disappeared! Weird. Maybe the app causing it update again. Anyway, thanks for the help!

N960U1 and could not update software. Need help.

Hi everyone,
So straight into the problem: I got my phone around the end of November 2018, which was when the Security Patch for that month came out. After that last update, I checked manually every month to see if there was another one. But after 12/14/2018, which was the last time I was able to check for updates, the phone would keep saying that it failed to download update, and a network or server error has occurred. I desperately need help.
View attachment 4685945

NahteT said:
So straight into the problem: I got my phone around the end of November 2018, which was when the Security Patch for that month came out. After that last update, I checked manually every month to see if there was another one. But after 12/14/2018, which was the last time I was able to check for updates, the phone would keep saying that it failed to download update, and a network or server error has occurred. I desperately need help.
View attachment 4685945
Click to expand...
Click to collapse
Boot into recovery & wipe the cache partition,reboot to system & then try again.
If that doesn't help,try using Samsung Smart Switch on your PC to update.
https://www.samsung.com/us/support/owners/app/smart-switch

KOLIOSIS said:
Boot into recovery & wipe the cache partition,reboot to system & then try again.
If that doesn't help,try using Samsung Smart Switch on your PC to update.
https://www.samsung.com/us/support/owners/app/smart-switch
Click to expand...
Click to collapse
Sadly, none of the two options worked for me. I have also tried booting into Safe mode, but the same problem would occur again. What else can I do, other than a factory reset?

NahteT said:
Sadly, none of the two options worked for me. I have also tried booting into Safe mode, but the same problem would occur again. What else can I do, other than a factory reset?
Click to expand...
Click to collapse
The only thing I can think of ATM is find the system apps responsible for system updates (two,I believe) wipe the cache & data ,if possible,from both,& try again.
If you are running an unadulterated version of the firmware that shipped with the phone,I'm stumped as to why you cannot update.
If you have any disabled apps perhaps enable them to rule out anything that might be causing this.

KOLIOSIS said:
The only thing I can think of ATM is find the system apps responsible for system updates (two,I believe) wipe the cache & data ,if possible,from both,& try again.
If you are running an unadulterated version of the firmware that shipped with the phone,I'm stumped as to why you cannot update.
If you have any disabled apps perhaps enable them to rule out anything that might be causing this.
Click to expand...
Click to collapse
Do you have to rely on ADB to wipe the cache and data? I found the two system apps that are used for Software Update (com.sec.android.soagent , com.wssyncmldm), but I can't seem to find the command code to do that.

NahteT said:
Do you have to rely on ADB to wipe the cache and data? I found the two system apps that are used for Software Update (com.sec.android.soagent , com.wssyncmldm), but I can't seem to find the command code to do that.
Click to expand...
Click to collapse
No,just navigate to Settings > Apps & tap on the 3-dot menu in the corner,select to view all/system apps & wipe each software update app.
If the buttons are greyed-out,then of course that can't be done.

KOLIOSIS said:
No,just navigate to Settings > Apps & tap on the 3-dot menu in the corner,select to view all/system apps & wipe each software update app.
If the buttons are greyed-out,then of course that can't be done.
Click to expand...
Click to collapse
I have just tried wiping the cache and data for the system apps, and also wipe the cache partition of the phone, yet nothing changes. I think what happened was that I accidentally disabled the two system packages for Software Update through ADB before this problem occurs, and now re-enabling them would have no effect.

NahteT said:
I have just tried wiping the cache and data for the system apps, and also wipe the cache partition of the phone, yet nothing changes. I think what happened was that I accidentally disabled the two system packages for Software Update through ADB before this problem occurs, and now re-enabling them would have no effect.
Click to expand...
Click to collapse
You can't re-enable apps that have been disabled by ADB w/o a factory reset.
In the future, you may want to consider using one of the Package Disabling apps that are available to avoid situations like this.

KOLIOSIS said:
You can't re-enable apps that have been disabled by ADB w/o a factory reset.
In the future, you may want to consider using one of the Package Disabling apps that are available to avoid situations like this.
Click to expand...
Click to collapse
If that's the case, then it wouldn't make sense that I were able to re-enable quite a lot of apps disabled by ADB. Or is this a special case where the crucial system apps that when disabled, they can't be re-enabled again?

NahteT said:
If that's the case, then it wouldn't make sense that I were able to re-enable quite a lot of apps disabled by ADB. Or is this a special case where the crucial system apps that when disabled, they can't be re-enabled again?
Click to expand...
Click to collapse
That would be my guess, otherwise, you should be able to update.

KOLIOSIS said:
That would be my guess, otherwise, you should be able to update.
Click to expand...
Click to collapse
Okay, I'll do a factory reset to see if this would solve the problem. Thanks for your help.

NahteT said:
Okay, I'll do a factory reset to see if this would solve the problem. Thanks for your help.
Click to expand...
Click to collapse
Please keep us posted on your outcome.

KOLIOSIS said:
Please keep us posted on your outcome.
Click to expand...
Click to collapse
So problem is solved: I did a factory reset, and the software update works just fine. I guess that the assumption about disabling crucial system apps caused them to not become re-enabled again must be right. Well I learned my lesson now - not to abuse ADB too much when it comes to bloatware. Thank you once again, I appreciate your help a lot.

NahteT said:
So problem is solved: I did a factory reset, and the software update works just fine. I guess that the assumption about disabling crucial system apps caused them to not become re-enabled again must be right. Well I learned my lesson now - not to abuse ADB too much when it comes to bloatware. Thank you once again, I appreciate your help a lot.
Click to expand...
Click to collapse
No problem, glad to be of help.
As for the ADB Removal & re-install of apps, I 1st heard about it from this XDA article/how-to:
https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/amp/
As it mentions the inability to re-install/re-enable apks, I just took their word for it & never uninstalled anything that I might need at some point.
That's why I like using package disablers, it's easily reversible without a reset.
Regardless, a factory reset isn't the end of the world, just a PITA at most.
Glad you got things going again.

Sorry to bother you again, but now I have problems with package disablers. I'm currently using a package disabler app, and it requires Device Owner App permission in order to disable bloatware apps, which can easily be done through ADB.
adb shell dpm set-device-owner com.pdp.deviceowner/.receivers.AdminReceiver
However, upon doing this, the lock screen of the phone will now show "This device is managed by your organization" at the bottom of the screen, and I don't feel comfortable about it. I have tried to uninstall the package disabler after done removing bloatware, but it wouldn't let me because the app is now a device administrator. I kind of screwed up myself after using the uninstall option inside the app, without knowing that it has completely uninstalled all the bloatware I disabled (instead of uninstalling the app itself), and caused my phone to stuck in boot loop, but I managed to fix that by another factory reset.
What kind of ADB command do I need so I can remove Device Owner App from the package disabler after I'm done disabling the bloatware?? (this is so ironic: disable a package disabler). Very sorry to disturb you again.

NahteT said:
Well I learned my lesson now - not to abuse ADB too much when it comes to bloatware..
Click to expand...
Click to collapse
Glad the problem was solved. My view is that concern with bloatware is a vestige of the past. On present-day phones, I'd guess that less than 0.1% of storage, memory, processor time, or battery charge are tied up with bloatware apps. So trying to identify and disable them won't have any noticeable benefit, and may well break things.

NahteT said:
Sorry to bother you again, but now I have problems with package disablers. I'm currently using a package disabler app, and it requires Device Owner App permission in order to disable bloatware apps, which can easily be done through ADB.
adb shell dpm set-device-owner com.pdp.deviceowner/.receivers.AdminReceiver
However, upon doing this, the lock screen of the phone will now show "This device is managed by your organization" at the bottom of the screen, and I don't feel comfortable about it. I have tried to uninstall the package disabler after done removing bloatware, but it wouldn't let me because the app is now a device administrator. I kind of screwed up myself after using the uninstall option inside the app, without knowing that it has completely uninstalled all the bloatware I disabled (instead of uninstalling the app itself), and caused my phone to stuck in boot loop, but I managed to fix that by another factory reset.
What kind of ADB command do I need so I can remove Device Owner App from the package disabler after I'm done disabling the bloatware?? (this is so ironic: disable a package disabler). Very sorry to disturb you again.
Click to expand...
Click to collapse
The message is just a generic one (as used when you grant admin rights for work e-mail,for example).
What it comes down to is if you trust the package disabler app & its developer,as I don't think there is any way to revoke the permission as long as you are using it to disable any apps at all.
I may be wrong on that,but,it seems like that's what's going on here.
If this still bothers you,then the next best solution is to continue using the disabling app long enough to determine which apps you are 100% certain are not needed/wanted.
Make a list & then switch to the ADB method.
That way,you get the admin rights to the disabler app off of your phone,but,you do give up the flexibility of the app as well.
The only way I see around your predicament is gaining root access & using the disabler app w/o admin rights,or,another app such as SD Maid Pro or Titanium Backup Pro.