Hello all.. so i started working again on hacks for android. I literally stopped it when i sold my sony xperia z5 premium and bought some samsung device.( It is literally no pleasure to work with all those s6 edge, s7 edge and note 5.. sorry samsung.. but your software is nothing but a nightmare for guys like me) .
I was desperate to buy a pixel 2 xl , waited so long to arrive at markets near me.. and when it arrived.. i grabbed one soon.. its a joy to hold this device.. well .. every happiness comes with some sorrows..
As soon as i got my pixel 2 xl, i unlocked the bootloader and rooted it in just 2 hours after i got it.. so.. even though this device is an awesome gadget to play with.. it have its own drawbacks at several things..
1) of course the infamous display issues.. ( lol.. those haters may wont even know what OLED( or pOLED) display does..
2) crackling of speakers ... Well i am not worried.. i know its something to do with the software.. and google or even we xda geniuses will fix it soon.. ( btw.. i am looking into some solutions)
3) touch screen sensitivity... Ya.. you heard it right.. this pannel have some touch issues.. may be most of you or some of you have noticed it now.. if you dont.. try a glass screen protector..
So while i was not able to fix the speaker issue by now ( my device is just 4 days old.. and i noticed it yesterday only, as i haven't even started using it with a sim card yet) , i possibly have a solution for touch sensitivity .. i just found it 10 minutes before creating this post. ( Thanks to some old knowledge for some sony hacks back in those days) ..
Way too boring talks?? Sorry.. i am basically a story teller type guy.. ok. No more stories.. lets get it done.
1) go to your favorite root file manager ..
2) go to - system / vendor/ usr / idc .
3) you will see a file named touchscreen.idc
4) open it with any text editor and remove all values from it and add these lines ( or replace with the attached file)
device.internal = 1
touch.deviceType = touchScreen
touch.orientationAware = 1
touch.filter.level = 0
touch.size.calibration = diameter
touch.size.scale = 5
touch.size.bias = 5
touch.size.isSummed = 0
touch.gestureMode = pointer
touch.pressure.calibration = physical
touch.pressure.scale = 0.00000125
touch.distance.calibration = none
touch.distance.scale = 0
touch.gestureMode = spots
MultitouchSettleInterval = 0.1ms
MultitouchMinDistance = 0.5 px
TapInterval = 0.5 ms
TapSlop = 0.5 px
touch.orientation.calibration = none
touch.coverage.calibration = box
5) save the file with its previous permissions ( i use filemanager named xplore, which automatically saves it with previous permissions)
6) reboot your device.. and enjoy your super responsive touch screen..
Guys.. please let me know your experience.. for further goods and bads..
Thank you..
Oh.. btw.. i have a bonus knowledge to share too..
If you find your colour calibration ( or colourfulness!! ) Of your device is low even after googles " saturated mode" , you can adjust it in build.prop file.
1) go to - system / vendor
2) open build.prop file in your fave text editor.
3) find this line - " persist.sys.sf.color_saturation=1.1 "
4) change the value to " persist.sys.sf.color_saturation=1.5 " or so..
5) you can go all the way upto "persist.sys.sf.color_saturation=2" but not more..
6) save file with its previous permissions
7) reboot and enjoy you " Samsung'ish " display..
Nb:-
dont burn ur eyes with all those alien looking colours with value of 2.. just keep it under 1.5 or so... Guys.. keep it as pixel, why go for that samsung colours
Wishes..
All praise Lord Dinkan..
Just tried it. Will report. If this fixes the telegram push to talk button, I will be overjoyed!
---------- Post added at 02:43 AM ---------- Previous post was at 02:01 AM ----------
Never mind.. the changes don't stick. I can edit the 2 files mentioned but after a reboot they back to the way they were. Tried multiple root browsers. Always after a reboot, everything is back stock settings. What am I missing?
Holy crap! Nice find my friend. I'll definitely be looking into this. Thanks a bunch! :good::good:
Same here. Didn't survive the reboot.
Sent from my Pixel 2 XL using Tapatalk
crowsnestitsupport said:
Just tried it. Will report. If this fixes the telegram push to talk button, I will be overjoyed!
---------- Post added at 02:43 AM ---------- Previous post was at 02:01 AM ----------
Never mind.. the changes don't stick. I can edit the 2 files mentioned but after a reboot they back to the way they were. Tried multiple root browsers. Always after a reboot, everything is back stock settings. What am I missing?
Click to expand...
Click to collapse
wolfeyes30 said:
Same here. Didn't survive the reboot.
Click to expand...
Click to collapse
That's kinda strange. I edited it with root explorer, rebooted, and the settings stuck! Definitely can tell the difference on my smart keyboard pro :good:
I didn't have general swipe issues, the only thing I had trouble with was swiping up on the lock screen to bring up the pin pad. Usually it took me two or three times before the pin pad would actually come up. In any event, I just tried your touch sensitivity suggestion, except that I just set it to .000125 (because I don't have a glass screen protector on it, and I didn't want it to be too sensitive), and that worked absolutely beautifully. I was just able to pull up the pin pad about 15 times in a row with absolutely no issues. Thank you so much!
If you can fix the crackling speaker sound, you'll be a god in my eyes! In my opinion, that is the only issue I have left with this phone.
I'll hit the thanks button tomorrow, I'm all out of thanks for today.
Sent from my Pixel 2 XL using XDA Labs
crowsnestitsupport said:
Just tried it. Will report. If this fixes the telegram push to talk button, I will be overjoyed!
---------- Post added at 02:43 AM ---------- Previous post was at 02:01 AM ----------
Never mind.. the changes don't stick. I can edit the 2 files mentioned but after a reboot they back to the way they were. Tried multiple root browsers. Always after a reboot, everything is back stock settings. What am I missing?
Click to expand...
Click to collapse
wolfeyes30 said:
Same here. Didn't survive the reboot.
Click to expand...
Click to collapse
There is two system folder system and system_root..
Also there is a vendor folder outside system folder..
I dont know the system structure yet ( as i didn't disassemble the factory images yet ) .. so i dont know why this all confusing folder structure..
Btw.. i think you have looked into system_root folder or vendor folder outside system folder..
Make sure u go into system ( not system_root) and find the file..
System - vendor - usr - idc..
Or may be just your filemanager didn't saved the value??
sharkie405 said:
I didn't have general swipe issues, the only thing I had trouble with was swiping up on the lock screen to bring up the pin pad. Usually it took me two or three times before the pin pad would actually come up. In any event, I just tried your touch sensitivity suggestion, except that I just set it to .000125 (because I don't have a glass screen protector on it, and I didn't want it to be too sensitive), and that worked absolutely beautifully. I was just able to pull up the pin pad about 15 times in a row with absolutely no issues. Thank you so much!
If you can fix the crackling speaker sound, you'll be a god in my eyes! In my opinion, that is the only issue I have left with this phone.
I'll hit the thanks button tomorrow, I'm all out of thanks for today.
Click to expand...
Click to collapse
Meh....just make him a special font package bro. That'll be some good thanks for sure! :good:
Root explorer doesn't save the change for some odd reason. I just tried xplore as well with no change. Once I reopen the file the value was back to stock.
Sent from my Pixel 2 XL using Tapatalk
wolfeyes30 said:
Root explorer doesn't save the change for some odd reason. I just tried xplore as well with no change. Once I reopen the file the value us back to stock.
Click to expand...
Click to collapse
I use FX and had no issues.
Sent from my Pixel 2 XL using XDA Labs
Like the OP said. The pic shows the proper path to the file. This is using root explore.
Dtbo image causing this maybe? I'm using the unofficial magisk without patching the dtbo.
crowsnestitsupport said:
Just tried it. Will report. If this fixes the telegram push to talk button, I will be overjoyed!
---------- Post added at 02:43 AM ---------- Previous post was at 02:01 AM ----------
Never mind.. the changes don't stick. I can edit the 2 files mentioned but after a reboot they back to the way they were. Tried multiple root browsers. Always after a reboot, everything is back stock settings. What am I missing?
Click to expand...
Click to collapse
wolfeyes30 said:
Same here. Didn't survive the reboot.
Click to expand...
Click to collapse
Avb 2.0 dm verity has to be patched in the dtbo image in order to edit the vendor partition. The above fix will stick once the dtbo image is patched. Will not stick without the patch.
---------- Post added at 03:04 AM ---------- Previous post was at 03:01 AM ----------
wolfeyes30 said:
Dtbo image causing this maybe? I'm using the unofficial magisk without patching the dtbo.
Click to expand...
Click to collapse
You got it. That's the problem
Golf c said:
Avb 2.0 dm verity has to be patched in the dtbo image in order to edit the vendor partition. The above fix will stick once the dtbo image is patched. Will not stick without the patch.
---------- Post added at 03:04 AM ---------- Previous post was at 03:01 AM ----------
You got it. That's the problem
Click to expand...
Click to collapse
Hey Golfc, you seem to know this magisk stuff pretty well. I'm still using the 14.5 zip, but using the 5.5 app. As you can see by the pic, force encryption and the AVB thingy are checked off. Everything is working fine. Would that change if I flashed the 14.6 version?? Only reason I haven't is I don't want to mess up my V4A. Any insight is greatly appreciated :good:
What's the correct way for me to get onboard with the official magisk with a patched dtbo?
I have twrp installed already and using custom kernel. Uninstall the unofficial magisk from magisk manager then flash stock boot image, flash stock dtbo image, flash custom kernel then flash official magisk?
Thanks
I'm sure I need to reflash twrp.zip somewhere during that process to keep from getting the stock recovery.
Badger50 said:
Hey Golfc, you seem to know this magisk stuff pretty well. I'm still using the 14.5 zip, but using the 5.5 app. As you can see by the pic, force encryption and the AVB thingy are checked off. Everything is working fine. Would that change if I flashed the 14.6 version?? Only reason I haven't is I don't want to mess up my V4A. Any insight is greatly appreciated :good:
Click to expand...
Click to collapse
Are you still getting the internal storage corruption message on boot? Your dtbo image is still patched then. It will not change by updating to 14.6. The only way to change is to fastboot the stock dtbo image and flash 14.6. In your current situation, all you would have to do is flash stock dtbo image and 14.6 Your Viper will still work.
wolfeyes30 said:
Root explorer doesn't save the change for some odd reason. I just tried xplore as well with no change. Once I reopen the file the value was back to stock.
Click to expand...
Click to collapse
I don't know what is the problem with your file manager bro.. i changed and checked it several times.. every single time it is working.. actually i have some more tweaks with touch.. i am experimenting some values.. so i put on each values and checking every single time..
Golf c said:
Are you still getting the internal storage corruption message on boot? Your dtbo image is still patched then. It will not change by updating to 14.6. The only way to change is to fastboot the stock dtbo image and flash 14.6. In your current situation, all you would have to do is flash stock dtbo image and 14.6 Your Viper will still work.
Click to expand...
Click to collapse
Thanks bud. Not sure about the V4A that Zackptg5 helped create. Been reading that magisk 14.6 is causing it not to work. Guess I'll find out. Thanks again :good:
wolfeyes30 said:
What's the correct way for me to get onboard with the official magisk with a patched dtbo?
I have twrp installed already and using custom kernel. Uninstall the unofficial magisk from magisk manager then flash stock boot image, flash stock dtbo image, flash custom kernel then flash official magisk?
Thanks
I'm sure I need to reflash twrp.zip somewhere during that process to keep from getting the stock recovery.
Click to expand...
Click to collapse
1. Fastboot stock dtbo image and stock boot image
2. Reboot Twrp recovery from bootloader screen
2. Flash Twrp, custom kernel and Magisk 14.6 in one session.
No need to uninstall anything. I also assume your custom kernel uses a Ak2 zip for flashing.
But i seriously doubt that the kernal configuration for touch screen calibration and the actual driver values of the touch screen drivers are some how miss matched.. the sensitivity is way too low at extreme bottom corners of the display ( both left and right bottom corners) .. but i have tweaked the values to give much better touch response than original. For now i think we can deal with the problem this way till google or some of us will come out with better solution.
Related
For my personal opinion the 200DPI is the best one, it's not to small as 160 and not to big, it's just perfect and compatible with the Tabblet UI.
How to?
(1) Install android SDK Tools download here;
(2) Be sure to check the adb option while installing;
(3) Go to windows Run and open cmd (hotkey is winflag + R);
(4) Now type cd\;
(5) Then type cd "installation path of adb" (prev. cd C:\Program Files (x86)\Android\android-sdk\platform-tools);
(4) Now connect the phone and reboot your'e android in to recovery and go to mount, mount the /system;
(5) Now in the cmd type: adb pull /system/build.prop c:\;
(6) Open the build.prop (located on c:\ drive, main folder) file with any text editor and search for ro.sf.lcd_density=;
(7) After the "=" just put a number like "200" (prev. ro.sf.lcd_density=200);
(8) Save the file;
(9) Go back to the cmd and now type: adb push c:\build.prop /system;
(10) Now type: adb shell;
(11) Now type: chmod 644 /system/build.prop;
(12) Reboot.
Thats pretty much it, i know it looks like, OMG, but it's very simpel if you done it one or two times you will now this without watching this topic again so it will work if you just follow the steps 1-by-1. Now don't be that smartass that says, don't type the "" symbols.
If you got any questions just ask and dont forget to thank
Btw im now responsoble if you done something stupid xD
You do NOT have to do all that to change the DPI. You don't even have to use ADB. Just use ROM Manager or open up the build.prop file in Root Explorer using Text Edit, find the line and change it, save and reboot. Some ROMs have the ability to change in the settings.
This thread isn't really needed in my opinion.
And don't forget if you use a custom dpi other then 320, 240, 160 etc lots of apps in the playstore won't run anymore.
andreww88 said:
You do NOT have to do all that to change the DPI. You don't even have to use ADB. Just use ROM Manager or open up the build.prop file in Root Explorer using Text Edit, find the line and change it, save and reboot. Some ROMs have the ability to change in the settings.
This thread isn't really needed in my opinion.
Click to expand...
Click to collapse
And what about the permissions fix? if you use ROM manager will it automatlicly fix the permissions?
friedje said:
And don't forget if you use a custom dpi other then 320, 240, 160 etc lots of apps in the playstore won't run anymore.
Click to expand...
Click to collapse
Well, all my tabblets apps still work on 200DPI
The app, rom tools lite is doing all that, and more
Just move the slider to the dedired dpi, and apply
Reboot - finished !
Well i didnt new that, im glad i now how adb works now so for the people that likes it just say thank and dont be that *****y. Im going to create a hole tutorial how to flash from stock to Stunner step by step for the noobs under us, sounds good or not?
Edited: ...
Galaxy Note N7000 - PARANOID ANDROID (CM9)
thomasvdalen90 said:
And what about the permissions fix? if you use ROM manager will it automatlicly fix the permissions?
Click to expand...
Click to collapse
Apparently, because I've never had any problems with just changing the build.prop file and rebooting. I never use rom manager, I was just saying it does it if you want an app to do it instead of digging in system files.
---------- Post added at 01:33 PM ---------- Previous post was at 01:31 PM ----------
thomasvdalen90 said:
Well i didnt new that, im glad i now how adb works now so for the people that likes it just say thank and dont be that *****y. Im going to create a hole tutorial how to flash from stock to Stunner step by step for the noobs under us, sounds good or not?
Click to expand...
Click to collapse
Ehh....I wouldn't use Stunner right now. Don't get me wrong, it is a fantastic ROM! However, it is still on a faulty kernel and we don't want people bricking their Notes. Do a ROM like Asylum or ParanoidAndroid or CM9 itself. Anything on the CM9 kernel.
But, every OP explains very well how to flash. If people would just read it.
You can use whatever file manager app you want as long as it has root access. Go to /system/build.prop, edit the line, reboot. It takes exactly 7.4 seconds.
(some of you have to change the permissions, so tap menu, permissions/properties and set to RW-R-R, reboot)
request for a move to general threads...nothing new here mate no offence...changing dpi can be done using apps (lcd density modder, rom toolbox etc) or manually by root explorer...and lets leave the tutorials for rom installations to the devs OP...
And this is in development why?
Use density modder app from market..
close thread?
andreww88 said:
Apparently, because I've never had any problems with just changing the build.prop file and rebooting. I never use rom manager, I was just saying it does it if you want an app to do it instead of digging in system files.
---------- Post added at 01:33 PM ---------- Previous post was at 01:31 PM ----------
Ehh....I wouldn't use Stunner right now. Don't get me wrong, it is a fantastic ROM! However, it is still on a faulty kernel and we don't want people bricking their Notes. Do a ROM like Asylum or ParanoidAndroid or CM9 itself. Anything on the CM9 kernel.
But, every OP explains very well how to flash. If people would just read it.
Click to expand...
Click to collapse
Why is it faulty? i read something about it but i dont have any problems and i though its the standard kernal.. I flashed abyss kernal to install Stunner for the safe way
thomasvdalen90 said:
Why is it faulty? i read something about it but i dont have any problems and i though its the standard kernal.. I flashed abyss kernal to install Stunner for the safe way
Click to expand...
Click to collapse
Causes the bricking because of the eMMc bug that corrupts your data partition (well, the motherboard is being replaced on those that have been bricked).
andreww88 said:
Causes the bricking because of the eMMc bug that corrupts your data partition (well, the motherboard is being replaced on those that have been bricked).
Click to expand...
Click to collapse
Yeah but i just flashed like this:
1 just odin to gingerbread
2 cf root
3 install abysskernal trough cwm
4 wipe
5 install stunner
6 stunner update
am i on a safe kernal now or not? just wanne now before im gonne flash my girlfriend gNote
thomasvdalen90 said:
Yeah but i just flashed like this:
1 just odin to gingerbread
2 cf root
3 install abysskernal trough cwm
4 wipe
5 install stunner
6 stunner update
am i on a safe kernal now or not? just wanne now before im gonne flash my girlfriend gNote
Click to expand...
Click to collapse
No you are not technically.....because you are on Stunner now. Stunner is not safe. Abyss is a GB kernel so that won't work. Stunner will need updating before it is "safe".
Basically, read the OPs and anything that says "CM9 kernel" is safe right now.
andreww88 said:
No you are not technically.....because you are on Stunner now. Stunner is not safe. Abyss is a GB kernel so that won't work. Stunner will need updating before it is "safe".
Basically, read the OPs and anything that says "CM9 kernel" is safe right now.
Click to expand...
Click to collapse
oww oops didnt new that, but im on stunner now, so if they update its safe? its working now will i be safed if im now flashing anymore? and can i just odin back to GB without risk?
thomasvdalen90 said:
oww oops didnt new that, but im on stunner now, so if they update its safe? its working now will i be safed if im now flashing anymore? and can i just odin back to GB without risk?
Click to expand...
Click to collapse
Abyss is used to restore nandroid backups on ICS since CWM can't.
Well, if you wipe data or do anything with BIG files you could potentially mess up your eMMc by "activating" that bad bug.
Personally, I would immediately ODIN back to GB, root it, and go to a CM9 based ROM.
andreww88 said:
Abyss is used to restore nandroid backups on ICS since CWM can't.
Well, if you wipe data or do anything with BIG files you could potentially mess up your eMMc by "activating" that bad bug.
Personally, I would immediately ODIN back to GB, root it, and go to a CM9 based ROM.
Click to expand...
Click to collapse
I im copiieng big files to my externalsd card theen my phone disconnects from the computer, is that the brick? :O then im already screwed
and does cm9 have tabblet ui?
thomasvdalen90 said:
I im copiieng big files to my externalsd card theen my phone disconnects from the computer, is that the brick? :O then im already screwed
Click to expand...
Click to collapse
External SD card? Umm, I don't think so. I haven't seen that. For your sake, I truly hope not.
Can you boot up? Can you get in recovery or download mode?
Edit:
PM me so we don't keep blowing up this thread with more potential "brick" stuff.
Hey fellow members of XDA!
If you didn't know, right now while I am posting this it is 3:07AM where I live.
Heres my story, ever since I got my first Android device I've been wanting to contribute to the comunity, but I haven't been able to figure out where to learn how to create ROM's. But today I thought to myself, why dont I just make some boot animations and themes? Because I have been animating through C4D for a while now. But enough with my life story, that will be on the thread for the boot animation.
I have been working on this bootanimation since 9:30, I have rendered it out about 7 different times through Cinema 4D, so I could get just the perfect quality/size ratio. The thing is, I've gotten that down. I have the bootanimation.zip perfectly finished and ready to go, the problem I'm having is that I wanted to make it flashable, and if you read that bit up at the top you would know, I dont have much experience with scripts, so I went online and searched up how to make one and looked through ROM's to see what their updater-script looked like, and I thought I had it down, but everytime I go to flash it, it goes like this,
Code:
]-- Install /sdcard/AFAinHD.zip ...
Finding update package...
Opening update package...
Installing update...
* Verifying filesystems...
* Verifying partition systems...
Error flashing zip '/sdcard/AFAinHD.zip'
I'm sorry to be posting this here asking for your guys help, but I have no idea what to do here, I want to release this bootanimation to you guys, but I want to make it simple and easy to install also.
Any help will be greatly appricated.
*The flashable zip has been attached below for you guys to look at*
Flashable .zip - http://www.mediafire.com/?bj7qf18t8qf6627
**Due to the time I have posted this thread if little to no replies are given I will bump this thread later in the day, Thank You**
Well...you missed out the crucial line below "error flashing xxx"...you should see something like a status ? (number) error...if you can tell me that, the maybe I can help you solve your problem......good job in making the bootanimation...
See, now thats one of things I was thinking about, there is no error code. I've tried flashing with both CWM and TWRP, but both fail without providing a reason.
Ok...let me take a look at the zip first...
EDIT: what a large bootanimation! XD...usually they are around 4MB...you don't really need your pictures to be that large, but just edit the dimensions in desc.txt...your device will rescale it for you......but nehmimd, let me complete my download first...slow connection here...
Ryuinferno said:
Ok...let me take a look at the zip first...
Click to expand...
Click to collapse
Okay, I'm gonna go check on my next batch of .png files to see if they are ready to be WinRar'ed.
Ryuinferno said:
EDIT: what a large bootanimation! XD...usually they are around 4MB...you don't really need your pictures to be that large, but just edit the dimensions in desc.txt...your device will rescale it for you......but nehmimd, let me complete my download first...slow connection here...
Click to expand...
Click to collapse
Lol the size isn't under my control, Cinema 4D says what size its gonna be and if you say differently your picture is gonna look terrible, the size is definatly worth the look though, it looks amazing when it starts. :laugh:
Ok...took a look and found the problem...I am not sure where you got the idea of making flashable zips but your directory structure is totally wrong...cause if you are making one for cwm, it should be something else...let me attach a sample for you ok? Uploading now (this is a dummy zip, contains nothing, only folders)...
Ryuinferno said:
Ok...took a look and found the problem...I am not sure where you got the idea of making flashable zips but your directory structure is totally wrong...cause if you are making one for cwm, it should be something else...let me attach a sample for you ok? Uploading now (this is a dummy zip, contains nothing, only folders)...
Click to expand...
Click to collapse
*Points finger at only result from google on how to compline an updater-script for a bootanimation* --> http://androidarea51.com/modifications/%28how-to%29-make-a-flashable-update-zip/
I have never made an updater-script before, or any time of script, I have no idea what I'm doing with them, I would love to know where you learned to make them.
[EDIT] Just looked at your post again, yea my directory structure, that i just winged that... Couldn't find anywhere to tell me how the hell to do that.
The guide is correct but you kinda got it wrong...lookie here:
http://www.androidfilehost.com/Ryuinferno/Sample.zip
By the way, you must replace the update-binary with a working one for Nexus 7 (just extract it from any cwm zip for Nexus 7)...and place your bootanimation.zip in media folder...cause that's usually where custom bootanimations are placed...rezip everything and flash again...
Dead link 404 error
[EDIT] Nevermind i went ahead and typed it in and it worked, let me try to complile one right now and make it into a .zip, brb.
Lol...wait a min...
EDIT: Fixed the link...try again...
---------- Post added at 06:06 PM ---------- Previous post was at 05:57 PM ----------
Saw the fixed link in my previous post?
Ryuinferno said:
Lol...wait a min...
EDIT: Fixed the link...try again...
---------- Post added at 06:06 PM ---------- Previous post was at 05:57 PM ----------
Saw the fixed link in my previous post?
Click to expand...
Click to collapse
Man, I just cannot get this to work, could you link me to a updater-script that you think would work? Also what is the update-binary file for that I keep seeing in other flashables?
[EDIT] Just tried flashing it again, didnt work, still no error code...I dont understand this...
There's nothing wrong with the updater-script...except if your tab does not have busybox...then it won't work...the update binary is device specific...think of it like something to tell your recovery what to do...so you should find one meant for Nexus 7 to replace mine...
Gonna give it another try, just pulled the update-binary from stock 4.1.2 rom
Well, we are making progress, error 6, .
[Just read that its an encoding error, so I went back into my updater-script and re-saved reziped, still getting the damn error, Im going to try a different binary....]
[[Just tried a different binary, here I'm gonna link my new build, tell me what noob mistake i made this time...]]
http://www.mediafire.com/?j1w0xp12qbt25jv
Well I'm going to bed, but for u guys that will still try to help through the night here is what I have done so far, I tried three different binaries, one from stock 4.1.2 one from smoothrom v3.1 and one from a theme, and I rewrote my updater_script by scratch, and no luck was gained from any of it, I just keep getting a error 6. So the download in the last post is still valid you can still look at it if you want to try and help thank you.
Sent from my Nexus 7 using XDA Premium HD app
Well...don't sleep just yet...XD...I made a flashable zip for you
http://www.androidfilehost.com/Ryuinferno/custom-bootani.zip
Flash this directly...I am 90% sure it should work...
Ryuinferno said:
Well...don't sleep just yet...XD...I made a flashable zip for you
http://www.androidfilehost.com/Ryuinferno/custom-bootani.zip
Flash this directly...I am 90% sure it should work...
Click to expand...
Click to collapse
Damn my xda addiction. Brb
Sent from my Nexus 7 using XDA Premium HD app
Okay, so, the flash was a sucess, but it just kinda replaced the bootanimation with a black screen that overlayed the os, so I just reflashed my ROM, were making progress, almost there...
Actually I think you have the EOL (end of line) error...you must use unix format for EOL in updater-script...
And for bootanimation.zip...the compression level must be set as "store"...
Feel free to discuss any possible bugs/issues that are to arise.
Plain-Tweak:
Ever wanted to control your kernel from a file on your internal storage? Now you can! There are currently 3 different ways
1.) Manually create a text file on the root of /sdcard
named 'plaintweak' with the following values:
gov=(your choice of governor)
maxkhz=(max cpu clockrate for all cores)
minkhz= (min cpu clockrate for all cores)
scheduler=(choice of IO scheduler)
tcpcong=(choice of TCP Congestion control)
2.)Invoking the instruction 'plaintweak' with adb shell or Terminal Emulator.
3.)Separate aroma package for your device(not yet created) or through the rom installer.
When I run 'plaintweak' from aroma package adb shell or Terminal Emulator wouldn't it get overwritten?
No! Not at all. Your old settings are saved at /sdcard/plain-tweak listed by date.
Don't like the values? Want a different configuration? Rather use Performance Control or another app?
Simply rename your current plaintweak file or move an older plaintweak file located in /sdcard/plain-tweak to root of /sdcard.
Def the most stable aosp on lg g2. On the new build im getting echos while in convo. Not on my side but on their side. Tried both dirty and clean flashing. Reverted to 10/25 and issue is gone. Regardless thanks for your work. Saves me from the stock software ?
Awesome rom I love the feel and how quick it is.. head and shoulders above the last stable CM11 (M6, which I had been using since May) for D800.
Couple questions - I viewed back about 15 pages but couldn't find anything..
I know CM has had some issues lately with rotation, proximity sensor and light sensor. I just flashed the 11/7 version and my phone won't rotate. Not a big deal to me, and I'm not sure if it's known, but I wanted to throw that out there.
Also, might be a stupid question but I removed the stock lockscreen and can't seem to get it back. Reflash?
@RamOdin
First, thank you for the feedback. Second; Reflash. Third; make sure you're on an unmodified kitkat baseband. Also check your quick toggles for the autorotate toggle prior.
Thanks - will do this evening. Is it normal for all ROMs to only be able to do google login from Wifi?
---------- Post added at 10:54 AM ---------- Previous post was at 10:42 AM ----------
Ignore that last post.. I'm a dummy sometimes. Additionally, I cannot edit it.
@RamOdin
Flash ROM. Boot. Reboot back to recovery. Flash gapps. Then on boot, launch Play store, that will bring up the Google account wizard.
@Snuzzo
So it's not your ROM causing the issues on my phone. I flashed both LiquidSmooth and DirtyUnicorns, both having the same issue.
Strangely, the only thing that fixed it was flashing the latest nightly from CM11, watching it go into a bootloop and then wiping in recovery and restoring my last backup of CM11 M6...
Weird.. *shrugs*
Any ideas? I know it's not your job to troubleshoot me, but I really love this ROM and would love to use it daily.
No clue unfortunately. These G2's can be finicky. Try doing a TOT/KDZ restore to stock.
I love it. Will update to your L rom when available.
On a side note for anyone who doesn't know, if you're using the ls980 (sprint variant) but on an American gsm network the dialer trick does work.
Remember, it's *#*#4636#*#*
Hey guys,
After seeing this Magisk module https://github.com/DeicPro/xiaomi-safetynet-fix
I began to experiment to make SafetyNet pass on Osprey.
And finally I was able to do just that.
DO REMEMBER THAT THIS REQUIRES MAGISK WITH MAGISK HIDE ENABLED. THIS WILL NOT WORK WITH SUPERSU.
IF YOU ALREADY HAD SuperSU, CLEAN FLASH THE ROM AND THEN FLASH MAGISK ZIP.
Steps-
NOTE: SINCE GOOGLE HAS UPDATED SAFETYNET, THE BELOW METHOD NOW REQUIRES MAGISK v14.0+-
Open the build.prop file located in /system. [REQUIRES ROOT]
Add this line to the build.prop file-
For XT1550(Retail Asia | India (2GB))-
ro.build.fingerprint=motorola/osprey_retasia_ds_2gb/osprey_ud2:6.0.1/MPIS24.107-55-2-12/14:user/release-keys
For XT1543(Retail Latin America (1GB)) -
ro.build.fingerprint=motorola/osprey_retla_ds/osprey_uds:6.0.1/MPI24.107-55-2/2:user/release-keys
For XT1540(Retail US (2GB)) -
ro.build.fingerprint=motorola/osprey_retus_2gb/osprey_u2:6.0/MPI24.65-25/28:user/release-keys
For XT1540(Retail US (1GB))-
ro.build.fingerprint=motorola/osprey_retus/osprey_umts:6.0/MPI24.65-25.1/1:user/release-keys
Save and Exit.
Make sure you have enabled Magisk Hide in Magisk setings.
Reboot.
NEW! Magisk module is available here.
~Please read the Note section below~
---------------------------------------------------------------------------------------------------------------------------------------------------------------
NOTE-
1. The fingerprint values need to be exactly the same. Any small change will trigger safetynet.
2. You can use any fingerprint value for your device. It's not necessary for you to take value specific to your device. As long as the fingerprint is valid, it will work.
3. This same trick should also work on Merlin devices.
4. Read this too please.
---------------------------------------------------------------------------------------------------------------------------------------------------------------
Thanks to -
@Rohi09 for providing stock ROM XT1550 build.prop
@Deic for his magisk module which inspired me to do this.
@KrisM22 for providing XT1540(2 GB) values.
@xMotoDA for providing XT1543 values.
@lettucecube for providing XT1540(1 GB) values and creating the Magisk module.
This method is working fine on purenexus rom
This is only for Asian Ospreys with 2GB of RAM, right?
Absolute killer! Thanks man.
Unfortunately, I still can't use digibank. Don't know what sort of check they perform.
xMotoDA said:
This is only for Asian Ospreys with 2GB of RAM, right?
Click to expand...
Click to collapse
Does that really matter?
Changing these specific values to the ones in the stock ROM makes SafetyNet pass! Since mine is dual sim and a different model I changed this in build.prop:
Code:
ro.product.name=osprey_retla_ds
ro.product.device=osprey_uds
ro.build.product=osprey_uds
ro.build.fingerprint=motorola/osprey_retla_ds/osprey_uds:6.0.1/MPI24.107-55-2/2:user/release-keys
bin.sayantan said:
Absolute killer! Thanks man.
Unfortunately, I still can't use digibank. Don't know what sort of check they perform.
Click to expand...
Click to collapse
Try to enable Magisk Hide for that specific app. Its there in the settings.
coolguy_16 said:
Try to enable Magisk Hide for that specific app. Its there in the settings.
Click to expand...
Click to collapse
Nothing happened. I even went a step further by totally uninstalling Magisk. Yet no luck.
bin.sayantan said:
Absolute killer! Thanks man.
Unfortunately, I still can't use digibank. Don't know what sort of check they perform.
Does that really matter?
Click to expand...
Click to collapse
I cant also log in my digi bank acount...i hav got a fixed deposit there....what is creating problem?any help
---------- Post added at 12:57 PM ---------- Previous post was at 12:35 PM ----------
Grt work....
I didnt found two lines in my build prop..so i add those...and safety net passed...
Thanx mate:good:
Can someone help me with this build.prop. Its from aex 4.2
Susan Dahal said:
Can someone help me with this build.prop. Its from aex 4.2
Click to expand...
Click to collapse
On AEX, you can simply add this line
ro.build.fingerprint=motorola/osprey_retasia_ds_2gb/osprey_ud2:6.0.1/MPIS24.107-55-2-12/14:user/release-keys
anywhere in the build.prop.
Make sure the above value is exactly the same.
coolguy_16 said:
On AEX, you can simply add this line
ro.build.fingerprint=motorola/osprey_retasia_ds_2gb/osprey_ud2:6.0.1/MPIS24.107-55-2-12/14:user/release-keys
anywhere in the build.prop.
Make sure the above value is exactly the same.
Click to expand...
Click to collapse
It worked Thanks
If you are willing could you look at mine - this is from a Moto G3 2015 XT1540 2GB US ATT
Thanks!
My stock is XT1540_OSPREY_RETUS_2GB_6.0_MPI24.65-25.1_cid9_subsidy-DEFAULT_CFC.xml.zip
So I tried
ro.build.fingerprint=motorola/OSPREY_RETUS_2GB/osprey_ud2:6.0/MPI24.65-25.1/14:user/release-keys
but no go.
also tried
ro.build.fingerprint=motorola/XT1540_OSPREY_RETUS_2GB/osprey_ud2:6.0/MPI24.65-25.1/14:user/release-keys
but no go.
KrisM22 said:
If you are willing could you look at mine - this is from a Moto G3 2015 XT1540 2GB US ATT
Thanks!
My stock is XT1540_OSPREY_RETUS_2GB_6.0_MPI24.65-25.1_cid9_subsidy-DEFAULT_CFC.xml.zip
So I tried
ro.build.fingerprint=motorola/OSPREY_RETUS_2GB/osprey_ud2:6.0/MPI24.65-25.1/14:user/release-keys
but no go.
also tried
ro.build.fingerprint=motorola/XT1540_OSPREY_RETUS_2GB/osprey_ud2:6.0/MPI24.65-25.1/14:user/release-keys
but no go.
Click to expand...
Click to collapse
The problem here is that the value "ro.build.fingerprint" has to be the exact same as Motorola made it. Meaning even a small change(even CAPS) will trigger safetynet.
Anyways, I searched XDA for your device build.prop and found what you can replace that value with-
ro.build.fingerprint=motorola/osprey_retus_2gb/osprey_u2:6.0/MPI24.65-25/28:user/release-keys
You can use the fingerprint value of my device too(the one mentioned in post). It will work without any issues.
I myself tried the fingerprint value of another model(that too a 1GB model) and it still worked.
Edit: I even tried the build.prop of your device on mine and that worked too.
Edit2: It seems like Step 2 in my OP is actually not necessary. Only fingerprint value is needed.
coolguy_16 said:
The problem here is that the value "ro.build.fingerprint" has to be the exact same as Motorola made it. Meaning even a small change(even CAPS) will trigger safetynet.
Anyways, I searched XDA for your device build.prop and found what you can replace that value with-
ro.build.fingerprint=motorola/osprey_retus_2gb/osprey_u2:6.0/MPI24.65-25/28:user/release-keys
You can use the fingerprint value of my device too(the one mentioned in post). It will work without any issues.
I myself tried the fingerprint value of another model(that too a 1GB model) and it still worked.
Edit: I even tried the build.prop of your device on mine and that worked too.
Edit2: It seems like Step 2 in my OP is actually not necessary. Only fingerprint value is needed.
Click to expand...
Click to collapse
Huge thanks for your time. I realized I had not installed magisk so I installed that but I have supersu 2.79 installed so maybe need to uninstall that and install the special one for LinOS?
KrisM22 said:
Huge thanks for your time. I realized I had not installed magisk so I installed that but I have supersu 2.79 installed so maybe need to uninstall that and install the special one for LinOS?
Click to expand...
Click to collapse
I'm pretty sure it won't work with SuperSU.
Yep, remove SuperSu and also Magisk.
Then flash magisk zip again.This time it will install MagiskSU too(Magisk avoids MagiskSU if existing root solution is detected)
coolguy_16 said:
I'm pretty sure it won't work with SuperSU.
Yep, remove SuperSu and also Magisk.
Then flash magisk zip again.This time it will install MagiskSU too(Magisk avoids MagiskSU if existing root solution is detected)
Click to expand...
Click to collapse
It works! Huge thanks!
(This is LineageOS 5-11-17 )
When I removed SuperSU, I chose not to clean up the boot since I saw someone who supposedly bricked their phone doing that, so of course Magisk gave a nasty message about it when flashing,
so I wiped everything (dalvic/ART,Data,System,Cache) and rebuilt: flash rom, flash gapps, install, when get to desktop, install Magisk Mgr with play store and d/l zip(Magisk-v12.0.zip), and go back to TWRP and flash that zip (it does not say anything about su), but after boot I installed TBPro and discovered that yes, indeed I had root. Somewhere in there I set Magisk to "hide". So modified build.prop by only adding the one line you gave me up 2 posts (repeated below) and voila! And PokeGo works!
This is the line I added:
ro.build.fingerprint=motorola/osprey_retus_2gb/osprey_u2:6.0/MPI24.65-25/28:user/release-keys
HINT: I used the JRummy Root Browser for a file manager to copy the line from a text file on my SDcard(from PC), to /system/build.prop and within that I use RB text editor. I say that because for some reason X-plore didn't work for me - edited fine, said saved, but didn't. Wasted time with that.
I do notice that HIDE is checked only for PokemonGo for me, so far, but I haven't tried any banking apps.
THANKS!!!.
Oops - next morning, no root access. Magisk status still shows good. Magisk/Superuser shows all 3 apps (BBS, JR RootBrowser, TBPro) and all switched ON.
EDIT: In Magisk/3 bars/Settings/Superuser - Superuser Access - Set it to "Apps and ADB". Root is back!
I believe @coolguy_16 has said this but I just went and tested and used the line from the 1st post:
ro.build.fingerprint=motorola/osprey_retasia_ds_2gb/osprey_ud2:6.0.1/MPIS24.107-55-2-12/14:user/release-keys
and safetynet works just fine. So it would seem that as long as you have a valid fingerprint for some phone, it doesn't seem to matter what phone you put it on.
It is unknown whether google's "snet" would eventually alert the safetynet folks to this incongruity and then block it. EDIT - I would guess in the long run it would probably be better to use an "exact" fingerprint that would look correct.
EDIT There is a short FAQ in the first post that may help for solving Magisk problems:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Guys just an FYI.
Even though one can pass safetynet, some apps will still refuse to work.
You can try to enable Magisk hide for that specific app(see Magisk settings)
This happens because -
1. The app is sh*t
2. The app checks for other "dangerous props"
So anything which the app finds wrong in your build.prop will cause that.
Well, to find out what your app is checking exactly for.. You will have to decompile it and check for yourself. (Google is your friend)
:good: Great, tks m8.
I am now able to use my banking app (KBC Sign)
(however the app has to be checked in Magisk Hide, otherwise it wont work) :good:
Use it at your own risk! (Don't flash it on any Q ROMs）The dtbo.img is extracted from the Chinese version of miui 9.8.2,so you better use version 9.8.2 or 9.8.1,This Mod is more stable than the old 84hz because of the vision of dtbo.Some people use 84hz not smooth，72hz is the best option，but i used 84hz and it's perfect for me! so what are you waiting for? this zip include 60hz-66hz-72hz-84hz-90hz
-Download the attached zip, unzip it
-Open TWRP
-Backup your dtbo partition
-Select the corresponding dtboxx.img,choose the dtbo partition,the flash it
-Reboot
You should see the changes immediately after the restart. It's way smoother than before.
If you want to go back to default, restore your dtbo partition backup or flash the dtbo60
https://drive.google.com/file/d/1pXg...ew?usp=sharing
Join the telegram an get the new file and new phone screen oc:
https://t.me/LenScreenOC
Or add my QQ number to get support (always on line):1403727621
https://drive.google.com/file/d/1pXg2gfa5SoTlQYGmgi3Nq6PiqMgrSchN/view?usp=sharing
HelloRickyLee said:
https://drive.google.com/file/d/1pXg2gfa5SoTlQYGmgi3Nq6PiqMgrSchN/view?usp=sharing
Click to expand...
Click to collapse
Theres no file in zip bro.
Asapakyou01 said:
Theres no file in zip bro.
Click to expand...
Click to collapse
There's a folder, where are dtbo images. Flash them in recovery, ADB, or Lanthanum Toolbox
_MartyMan_ said:
There's a folder, where are dtbo images. Flash them in recovery, ADB, or Lanthanum Toolbox
Click to expand...
Click to collapse
Why i cant see when i open the zip file
Asapakyou01 said:
Theres no file in zip bro.
Click to expand...
Click to collapse
i checked .no problem,maybe your network got wrong
Can u try to upload again bro. I cant see the dtbo imgs in zip file swear
Asapakyou01 said:
Can u try to upload again bro. I cant see the dtbo imgs in zip file swear
Click to expand...
Click to collapse
try this
link：https://pan.baidu.com/s/1JqaI6Lh0zYRXkL96lyqXFg
password：lomv
HelloRickyLee said:
try this
link：https://pan.baidu.com/s/1JqaI6Lh0zYRXkL96lyqXFg
password：lomv
Click to expand...
Click to collapse
I need an app to download this file bro?
HelloRickyLee said:
Use it at your own risk! (Don't flash it on any Q ROMs）The dtbo.img is extracted from the Chinese version of miui 9.8.2,so you better use version 9.8.2 or 9.8.1,This Mod is more stable than the old 84hz because of the vision of dtbo.Some people use 84hz not smooth，72hz is the best option，but i used 84hz and it's perfect for me! so what you waiting for? this zip include 60hz-66hz-72hz-84hz-90hz
-Download the attached zip, unzip it
-Open TWRP
-Backup your dtbo partition
-Select the corresponding dtboxx.img,choose the dtbo partition,the flash it
-Reboot
You should see the changes immediately after the restart. It's way smoother than before.
If you want to go back to default, restore your dtbo partition backup or flash the dtbo60
Click to expand...
Click to collapse
I can confirm the 90hz mod works. MIUI Global 10.2. It does not work the first time I installed it (as always). A couple of reboots later, it worked. Green tint is still present though.
Can u upload the 90hz file here bro
---------- Post added at 05:34 PM ---------- Previous post was at 05:33 PM ----------
I really want to try the 90hz mod
Bambaw22 said:
I can confirm the 90hz mod works. MIUI Global 10.2. It does not work the first time I installed it (as always). A couple of reboots later, it worked. Green tint is still present though.
Click to expand...
Click to collapse
The green tint is purely a hardware issue, silicon lottery as we say.
I already see the file and flash the 90hz. It was working but when i put the device on sleep. And wake up again. The display will be lag i check on ufotest its will go down in 45hz
I have tested the 90 ghz and at the moment everything is fine I do not perceive any green stains good work friend only the bad thing is that when I use mods so games run slow and I have to remove the mod
excuse me one question,for instance a had a green tint issue with the previous 84 hz mod,how is this more stable ?
I flashed the 72Hz version on 9.8.1, and it's awesome. no greenish color and much better than 60Hz. Thanks!
First, thank you for sharing this mod.
The 90Hz mod is useless, since, although the display is configured with 90Hz, it refreshes at max 84Hz (tested with testufo.com).
The greenish tint is still there. I tried comparing the gamma values for 60Hz, 90Hz and 84Hz by eye with the app "Display Tester". It seems like for the higher refresh rates the gamma for green gets lower (= it looks more green on lower brightness). On 60Hz I had about 2.0 to 2.2 gamma (green). Using the mods gamma was at about 1.8 to 2.0.
Using the 72Hz mod seems to be the sweet spot between color accuracy and refresh rate. Here, the green gamma was about 2.0 to 2.1.
Of course this is subjective, but this would also explain the slightly washed out colors (green tint), especially on lower brightness. On highest brightness it looks better (for all mods).
As I said in the other topic (84Hz) it would be so nice to have an option to adjust the display colors (gamma adjustment).
I hope there will be a developer who will develop a kernel with display color calibration features.
crs951 said:
excuse me one question,for instance a had a green tint issue with the previous 84 hz mod,how is this more stable ?
Click to expand...
Click to collapse
you should keep the same miui vision 8.1 or 8.2
Damnn ! This 72hz dtbo works flawlessly with the xiaomi eu 9.8.1
No green tint at all ( I had with 84hz, and huge difference compared to 60hz )
But the screen is a little more blurry, espacially in games (brawl stars)
Patched the 72hz on latest global but i dont see any difference since i still seldom use my mi9 yet