Promised Land of speed / battery tweaks, FINALLY after 15? years!? on this site - Google Pixel 3 XL Themes, Apps, and Mods

Ok, so the thread i'm referencing is from the MIUI forum, but having tried it on my Pixel 3 XL, I am happy to report that it works FANTASTICALLY so far.
https://forum.xda-developers.com/Mi...en-to-84hz-t3942063/post79776396#post79776396
The OP is about a dbto.img replacement hack, using an apk called Lanthanum System Toolbox. The hack in question works great (I used the app to flash to dbto_a and dbto_b)
but the app itself is amazing. Forget init.d tweaks, magisk tweaks, searching for ever-better kernels, kernel aduitor, and all the rest.
There's a profile section which allows downloaded presets, the one for 845 SOC works great.
Only other things I should mention are that I had trouble dling the apk from xda, so i got it from their github (google Lanthanum System Toolbox) , and I'm running Colt OS - Enigma ROM (https://forum.xda-developers.com/pi...unofficial-colt-os-enigma-crosshatch-t3953043)
, boot.img extracted using https://forum.xda-developers.com/nokia-7-plus/how-to/guide-how-to-extract-payload-bin-ota-t3830962
, magisk canary patched and reflashed.
oh, and it's mostly localized in chinese,
but there's enough english that i was able to use it with very little trouble
perhaps i got the wrong apk, cause the screenshots on the OP are english
I really am surprised that there isn't a reference thread in the crosshatch forum already . you may consider my tone hyperbolic, but try it and you'll see i'm being understated if anything. enjoy!

not sure how increasing the refresh rate helps battery?

ha7msterx said:
Ok, so the thread i'm referencing is from the MIUI forum, but having tried it on my Pixel 3 XL, I am happy to report that it works FANTASTICALLY so far.
https://forum.xda-developers.com/Mi...en-to-84hz-t3942063/post79776396#post79776396
The OP is about a dbto.img replacement hack, using an apk called Lanthanum System Toolbox. The hack in question works great (I used the app to flash to dbto_a and dbto_b)
but the app itself is amazing. Forget init.d tweaks, magisk tweaks, searching for ever-better kernels, kernel aduitor, and all the rest.
There's a profile section which allows downloaded presets, the one for 845 SOC works great.
Only other things I should mention are that I had trouble dling the apk from xda, so i got it from their github (google Lanthanum System Toolbox) , and I'm running Colt OS - Enigma ROM (https://forum.xda-developers.com/pi...unofficial-colt-os-enigma-crosshatch-t3953043)
, boot.img extracted using https://forum.xda-developers.com/nokia-7-plus/how-to/guide-how-to-extract-payload-bin-ota-t3830962
, magisk canary patched and reflashed.
oh, and it's mostly localized in chinese,
but there's enough english that i was able to use it with very little trouble
perhaps i got the wrong apk, cause the screenshots on the OP are english
I really am surprised that there isn't a reference thread in the crosshatch forum already . you may consider my tone hyperbolic, but try it and you'll see i'm being understated if anything. enjoy!
Click to expand...
Click to collapse
Im getting bootloop when i tried itt on P

ha7msterx said:
Ok, so the thread i'm referencing is from the MIUI forum, but having tried it on my Pixel 3 XL, I am happy to report that it works FANTASTICALLY so far.
https://forum.xda-developers.com/Mi...en-to-84hz-t3942063/post79776396#post79776396
The OP is about a dbto.img replacement hack, using an apk called Lanthanum System Toolbox. The hack in question works great (I used the app to flash to dbto_a and dbto_b)
but the app itself is amazing. Forget init.d tweaks, magisk tweaks, searching for ever-better kernels, kernel aduitor, and all the rest.
There's a profile section which allows downloaded presets, the one for 845 SOC works great.
Only other things I should mention are that I had trouble dling the apk from xda, so i got it from their github (google Lanthanum System Toolbox) , and I'm running Colt OS - Enigma ROM (https://forum.xda-developers.com/pi...unofficial-colt-os-enigma-crosshatch-t3953043)
, boot.img extracted using https://forum.xda-developers.com/nokia-7-plus/how-to/guide-how-to-extract-payload-bin-ota-t3830962
, magisk canary patched and reflashed.
oh, and it's mostly localized in chinese,
but there's enough english that i was able to use it with very little trouble
perhaps i got the wrong apk, cause the screenshots on the OP are english
I really am surprised that there isn't a reference thread in the crosshatch forum already . you may consider my tone hyperbolic, but try it and you'll see i'm being understated if anything. enjoy!
Click to expand...
Click to collapse
Which dtbo.img did you use as well?

Don't try it on Android 10, it should work only on Pie

So does he mean that we can also get 84hz screen on pixel phone...?

DvLAx3l said:
Don't try it on Android 10, it should work only on Pie
Click to expand...
Click to collapse
I can't even get it to work on pie tho lol

ha7msterx said:
Ok, so the thread i'm referencing is from the MIUI forum, but having tried it on my Pixel 3 XL, I am happy to report that it works FANTASTICALLY so far.
https://forum.xda-developers.com/Mi...en-to-84hz-t3942063/post79776396#post79776396
The OP is about a dbto.img replacement hack, using an apk called Lanthanum System Toolbox. The hack in question works great (I used the app to flash to dbto_a and dbto_b)
but the app itself is amazing. Forget init.d tweaks, magisk tweaks, searching for ever-better kernels, kernel aduitor, and all the rest.
There's a profile section which allows downloaded presets, the one for 845 SOC works great.
Only other things I should mention are that I had trouble dling the apk from xda, so i got it from their github (google Lanthanum System Toolbox) , and I'm running Colt OS - Enigma ROM (https://forum.xda-developers.com/pi...unofficial-colt-os-enigma-crosshatch-t3953043)
, boot.img extracted using https://forum.xda-developers.com/nokia-7-plus/how-to/guide-how-to-extract-payload-bin-ota-t3830962
, magisk canary patched and reflashed.
oh, and it's mostly localized in chinese,
but there's enough english that i was able to use it with very little trouble
perhaps i got the wrong apk, cause the screenshots on the OP are english
I really am surprised that there isn't a reference thread in the crosshatch forum already . you may consider my tone hyperbolic, but try it and you'll see i'm being understated if anything. enjoy!
Click to expand...
Click to collapse
You used the dtbo.img from the mi9 thread that you linked? For me when I flash the dtbo.img the app just closes and nothing appears to happen. You were extract the boot.img for magisk or is it required for the mod as well? Thanks.

Well if some are interested, I can prepare kernel revisions with 64, 69, 70, 75, 80 and 84Hz screen refresh to test. I probably won't be able to test it before uploading each revision, so it would be up to each end user to check it's functionality. Of course I can get zero/natha/ responsibility if some devices are totally broken after.

melodystyle2003 said:
Well if some are interested, I can prepare kernel revisions with 64, 69, 70, 75, 80 and 84Hz screen refresh to test. I probably won't be able to test it before uploading each revision, so it would be up to each end user to check it's functionality. Of course I can get zero/natha/ responsibility if some devices are totally broken after.
Click to expand...
Click to collapse
That would be dope man, definitely willing to test it to tide me over until the pixel 4 comes out ?

eminem5055 said:
That would be dope man, definitely willing to test it to tide me over until the pixel 4 comes out
Click to expand...
Click to collapse
That would be awesome

OK, I ll try to get some permissions before building / posting the revisions.

melodystyle2003 said:
OK, I ll try to get some permissions before building / posting the revisions.
Click to expand...
Click to collapse
Sounds good man! ?

eminem5055 said:
Which dtbo.img did you use as well?
Click to expand...
Click to collapse
I used the one which is served directly from the OP I linked to..
I feel badly for all of the people who are having trouble with this.. bootloops and so forth. All I can say is I'm being truthful about the hardware and software I'm using, and it seems pretty straightforward to me. Using this device as my daily driver, still going strong.

ha7msterx said:
I used the one which is served directly from the OP I linked to..
I feel badly for all of the people who are having trouble with this.. bootloops and so forth. All I can say is I'm being truthful about the hardware and software I'm using, and it seems pretty straightforward to me. Using this device as my daily driver, still going strong.
Click to expand...
Click to collapse
ALSO, if the screen refresh part is a placebo, requiring a kernel modification to actually change, then ok.
Embarrassing to state, but I didn't actually test the resultant screen refresh rate, or really anything other than the subjective snappiness of my device.
So now I feel like I rushed to post, but I won't kill the thread because apparently melodystyle2003 is compiling a kernel. Thanks for that.

A small update, almost done with the first revision. I am dealing with some weird errors during the compiling procedure, that's why the 'almost' above, but hopefully tomorrow or day after tomorrow might have them tracked down and solved. After that, any upcoming revisions can be built much faster. My limited time can't guarantee any ETAs though. The guys that responded (with a like, quote or reply) to my previous relevant post, shall receive a download link of the kernel.

melodystyle2003 said:
A small update, almost done with the first revision. I am dealing with some weird errors during the compiling procedure, that's why the 'almost' above, but hopefully tomorrow or day after tomorrow might have them tracked down and solved. After that, any upcoming revisions can be built much faster. My limited time can't guarantee any ETAs though. The guys that responded (with a like, quote or reply) to my previous relevant post, shall receive a download link of the kernel.
Click to expand...
Click to collapse
Really looking forward to this

melodystyle2003 said:
A small update, almost done with the first revision. I am dealing with some weird errors during the compiling procedure, that's why the 'almost' above, but hopefully tomorrow or day after tomorrow might have them tracked down and solved. After that, any upcoming revisions can be built much faster. My limited time can't guarantee any ETAs though. The guys that responded (with a like, quote or reply) to my previous relevant post, shall receive a download link of the kernel.
Click to expand...
Click to collapse
Why don’t you just publish your code somewhere on github, so maybe somebody can help you to compile a kernel with your intended changes or can review the changes?
I’m pretty sure you can’t overclock the display of the pixel 3 devices as we’re using command mode panels and not video mode panels like some other devices where it’s possible to overclock the display refresh rate.
If you’re trying to modify this line for the pixel 3 xl:
https://github.com/freak07/Kirisaku...oogle/dsi-panel-s6e3ha8-dsc-wqhd-cmd.dtsi#L17
It will do nothing.
It’s similar to what happened in this thread and was described in this post
https://forum.xda-developers.com/showpost.php?p=79970079&postcount=35

Freak07 said:
Why don’t you just publish your code somewhere on github, so maybe somebody can help you to compile a kernel with your intended changes or can review the changes?
I’m pretty sure you can’t overclock the display of the pixel 3 devices as we’re using command mode panels and not video mode panels like some other devices where it’s possible to overclock the display refresh rate.
If you’re trying to modify this line for the pixel 3 xl:
https://github.com/freak07/Kirisaku...oogle/dsi-panel-s6e3ha8-dsc-wqhd-cmd.dtsi#L17
It will do nothing.
It’s similar to what happened in this thread and was described in this post
https://forum.xda-developers.com/showpost.php?p=79970079&postcount=35
Click to expand...
Click to collapse
Thanks for the information. On pocophone, changing the
"qcom,mdss-dsi-panel-framerate = <60>;" to the desired refresh rate i.e. 65 or more, was actually doing what was intended to. Have you tried something similar already that actually led only to the placebo effect described on the post you linked? If no, would you kindly do the corresponding changes in your kernel so someone can try it?
Regards

melodystyle2003 said:
Thanks for the information. On pocophone, changing the
"qcom,mdss-dsi-panel-framerate = <60>;" to the desired refresh rate i.e. 65 or more, was actually doing what was intended to. Have you tried something similar already that actually led only to the placebo effect described on the post you linked? If no, would you kindly do the corresponding changes in your kernel so someone can try it?
Regards
Click to expand...
Click to collapse
It´s not possible to overclock the displays of the pixel 3 or the pixel 3 xl that way. I don´t need to compile a test kernel to be able to tell you.
Displays running in command mode can´t be overclocked that way, unless you have access to internal files or you are able to flash display firmware to your device.
Both panels from Pixel 3 or Pixel 3 XL run in command mode:
https://github.com/freak07/Kirisaku...oogle/dsi-panel-s6e3ha8-dsc-wqhd-cmd.dtsi#L20
https://github.com/freak07/Kirisaku...google/dsi-panel-sw43408-dsc-fhd-cmd.dtsi#L20
Whereas the pocophone runs (as it seems more than one type of display across different units) all used panels in video mode.
https://github.com/d1stru3t0r/testz...qcom/dsi-panel-ebbg-fhd-ft8719-video.dtsi#L24
https://github.com/d1stru3t0r/testz.../dsi-panel-tianma-fhd-nt36672a-video.dtsi#L24
Panels in video mode can be overclocked this way, if it´s desirable is another question.
Sorry to be the bearer of bad news, but it´s simply not possible on Pixel 3 devices.
You can even unpack the dtbo.img, change the line you intend to change and any fps app might show you more than 60fps, but you just fooled the app into thinking our displays refresh at a higher rate than 60fps.

Related

[BUILD] **Complete GingerBread Bundle!!** GBX0A - Alpha! Camera!

Please read this entire post!
<<<This is a link to the... FAQ Click it!!>>>​
I have created a complete bundle of GingerBread with the newest kernel from GIT (Feb 28 / 1276), and the newest rootfs from GIT (Feb 24).
Please, feel free to DONATE to the XDAndroid project!
Every little bit helps! We don't make empty promises, we just provide solid and complete builds. No ETA's, no threads without download links or instructions... Enjoy!
Directions:
1. Download the full bundle (zip). (Updated Mar. 11 2011)
If instead you just want the system.ext2 (zip) file (updated Mar. 25 2011) by itself... Don't download this unless you know you want to update!!
2. Extract it. You’ll see a folder, GBX0A, copy its contents to the root (base) of your SD card. If you want to run Android from a folder instead of all the files on the root of the card, follow the steps below.
3. Go into the STARTUPS folder. Grab the appropriate startup.txt for your device (if you don't know what device you have, you should read the FAQ), and move it to the root of the card (or where you run haret.exe from. If you want to change the location of the build, put a rel_path= statement in the cmdline section of the startup.txt. Mine is located two folders deep on the SD, so my rel_path=Androids/TP2Ref)
4. Download the ts-calibration file from this post (should work for BLAC) and extract the .zip to where you run haret.exe from - typically the root or 'base' folder of the SD card. Not within any folders, unless you run haret.exe from a folder!
**If you have issues with the above file, you must calibrate manually. To start manual calibration, just delete any ts-calibration files and boot. Sometimes this doesn't work, and you have to use an older kernel from GIT (I found 1225 works well) and generate the ts-calibration file by booting and pressing the 5 zones. Once you have a good calibration file hold on to it (make 15 copies if it's a really good one ), reboot & go back to the newest kernel from the autobuild service! Thanks**
6. Run haret.exe... Profit!
Let it settle out on the first boot. Many have reported they had to reboot basically because it was so slow - if you let it sit for about 10 mins or so the media scanner can go thru everything, etc. If you want adb in and watch the processes via top, you'll see why the phone seems so slow - there's lots of background processes cranking because this is the first boot .
Troubleshooting:
Please read the... FAQ
If you have any issues with the kernel, feel free to change it:
There are some devices that are having issues with the newest kernels. Please see the kernel autobuild service to get newer or archived kernels. Once you download a replacement kernel, go to where you run haret.exe from - remove your old zImage/modules-xxxxx.tar.gz. Take the new zImage/modules-xxxxx.tar.gz and replace the old ones, same folder - where you run haret.exe from. Make sure the ‘zImage’ is named just that. Do not rename the modules file, do not extract it - should be in .tar.gz format.
In addition, I am using the newest rootfs from GIT - Feb. 10. There are other rootfs options, see F22’s thread if you want to use more keys or move around the home button. Of course, there's always the roofs autobuild service if you want "stock" rootfs images - F22 builds his off of these and modifies them .
See Incremental Updates for more information on this topic of updating!!
Random issues can often be solved by forcing the system to create a new data.img. If you're worried about losing data, Titanium Backup works quite well. If you wish, you can rename the data.img to something else, and let the system create a new one - just to see if it resolves your problem.
Similarly, if you wish try formatting your SD card - I prefer to use the HP Tool - do a full format, FAT32.
Obviously this build is Alpha, and there are going to be problems. The next post will address issues particular to this build - PLEASE READ THESE before asking questions! Feel free to post questions in this thread, I will do my best to address them. Big thanks to stinebd for releasing the system image, and of course the other developers for their hard work on making these kernels available.
stinebd's original post HERE
Mar. 11 2011 Changelog
Things broken in this build:
libgps - explains itself, no GPS and probably no netloc (cell-tower based location)
HW3D is either not working, or just not preset - I ran neocore and let's just say a lot of textures are missing. Got a ridiculous score, but again - no textures, not much to render haha.
This line should be in the startup.txt file if that wasn't obvious .
Thanks to emc02 for that solution!
The keyboard should be fine, but I've had some Blackstone users complain - if you want, switch the keyboard out with another. mr_grisha's original post. Others have said this is a horrible keyboard, and you should just use Swype. I'm a big fan of use what works for you, so you folks make the decision for yourself!
Anything that's broken in Froyo, is probably broken in this build.
Blackstone users - help me flesh out this section! Anything that's not working let me know!
Changelog​ March 25, 2011
Further tuned keyboard sizing to be useful on VGA (also made the key labels bigger)
World-phone settings support (very important for future RIL enhancements especially on CDMA)
Enabled HSPA icon (someone on GSM please let me know if it actually works)
Enabled HSPA icon (someone on GSM please let me know if it actually works).....this does not work on my blackstone.....nor does it work on frx06.......overall gbxoa and frx06 works resonable well.....
Startup.txt that works with frx06 and gbx0a
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2030
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msm_blackstone_pad.vibrate=1 msmvkeyb_toggle=off gsensor_axis=-2,-1,3 msmsdcc_nopwrsave rel_path=GBX0A"
boot
use as "rel_path=*****",where ***** is the name of the folder where haret and other files are located (GBX0A in this example),eg if using stock names use FRX06 for frx06 and GBX0A for gbx0a
sensor rotation should be as it is in the text above
also stock android keyboard doesn't work,and keyboard suggested in first post works a bit crappy (with all due respect),so you should use some other,i personally use swype and it doesn't matter if you swype or just type,because swype is great for typing too,it's fast and responses instantly (unlike betterkeyboard)
i think F22's rootfs are modified to fit rhodium which has keyboard and different button mapping so there is no need to use it...you know,no need for additional code lines which are not necessary
i suggest using zeam launcher it's faster and lighter than the stock one
what else does not work:
led notifications (do not work at all,also if you plug in the cable in WM before you run haret, orange notification(or green if it's fully charged) will continue to glow,so our android has no control over it,not even to turn it off)
front camera
(will add if i remember something)
what works especially good
overall speed and performance is great
the build is stable,i almost never got SOD,sometimes you have to FC apps,but very rarely....anyway, performance mesmerizes you so well that you don't even notice those issues
calls are perfect,no "turn speaker on/off" bug,no rejecting calls
if you want to be able to install more apps,go to this thread and grab the data.img maker (resize tool)
http://forum.xda-developers.com/showthread.php?t=824154
if you need storage access,use wifi explorers,they proved very good solution for not being able to access sotrage via usb
welard said:
Enabled HSPA icon (someone on GSM please let me know if it actually works).....this does not work on my blackstone.....nor does it work on frx06.......overall gbxoa and frx06 works resonable well.....
Click to expand...
Click to collapse
Yea, IIRC the new RIL is required to properly show H. Does it show in WinMo? Thanks for the feedback .
farukb said:
not sure if pmem.extra=1 is needed at all and does it perfor better without it,i read somewhere that it does....maybe arrrghhh knows
use as "rel_path=*****",where ***** is the name of the folder where haret and other files are located (GBX0A in this example),eg if using stock names use FRX06 for frx06 and GBX0A for gbx0a
sensor rotation should be as it is in the text above
i've attached ts-calibration for blackstone,so if anyone needs it,it is precisely calibrated....additionally if someone wants to do it by himself,he (she) should use 11** kernels (current are 13**),because calibraiton feature was removed from later kernels
Click to expand...
Click to collapse
Just saw this. Do I need to change anything in the startup.txt file for Blackstone? rel_path is up to you, pmem.extra is deprecated. Please don't use it - won't hurt anything, but it does nothing .
arrrghhh said:
Just saw this. Do I need to change anything in the startup.txt file for Blackstone? rel_path is up to you, pmem.extra is deprecated. Please don't use it - won't hurt anything, but it does nothing .
Click to expand...
Click to collapse
yeah...i read that...think it was your post i remember you being allergic to that line
that in blue and red was for user who don't know how to do it,just a little hint....also i think provided startup.txt is ok,i just posted this so someone who maybe modified it or lost it can have it easily without having to download whole 120mb package
farukb said:
yeah...i read that...think it was your post i remember you being allergic to that line
that in blue and red was for user who don't know how to do it,just a little hint....also i think provided startup.txt is ok,i just posted this so someone who maybe modified it or lost it can have it easily without having to download whole 120mb package
Click to expand...
Click to collapse
Ah no worries. Let me know if there is something you think I should change, I don't have a Blackstone and I'm always looking to improve the process for you guys!
arrrghhh said:
Yea, IIRC the new RIL is required to properly show H. Does it show in WinMo? Thanks for the feedback .
Just saw this. Do I need to change anything in the startup.txt file for Blackstone? rel_path is up to you, pmem.extra is deprecated. Please don't use it - won't hurt anything, but it does nothing .
Click to expand...
Click to collapse
yes it shows in window....thanks
what else does not work:
led notifications (do not work at all,also if you plug in the cable in WM before you run haret, orange notification(or green if it's fully charged) will continue to glow,so our android has no control over it,not even to turn it off)
front camera
if you use glemsom kernels your audio will stutter a bit,you can overcome this by using g3rm0's kernel found in this forum section....although it'd be nice if someone implemented anti-stuttering into glemsom(xdandroid official) kernels
(will add if i remember something)
what works especially good
overall speed and performance is great
the build is stable,i almost never got SOD,sometimes you have to FC apps,but very rarely....anyway, performance mesmerizes you so well that you don't even notice those issues
calls are perfect,no "turn speaker on/off" bug,no rejecting calls
if you want to be able to install more apps,go to this thread and grab the data.img maker (resize tool)
http://forum.xda-developers.com/showthread.php?t=824154
copied everything to 5th post,so it's all in one place
farukb said:
what else does not work:
led notifications (do not work at all,also if you plug in the cable in WM before you run haret, orange notification(or green if it's fully charged) will continue to glow,so our android has no control over it,not even to turn it off)
front camera
if you use glemsom kernels your audio will stutter a bit,you can overcome this by using g3rm0's kernel found in this forum section....although it'd be nice if someone implemented anti-stuttering into glemsom(xdandroid official) kernels
(will add if i remember something)
what works especially good
overall speed and performance is great
the build is stable,i almost never got SOD,sometimes you have to FC apps,but very rarely....anyway, performance mesmerizes you so well that you don't even notice those issues
calls are perfect,no "turn speaker on/off" bug,no rejecting calls
Click to expand...
Click to collapse
all above quoted the same for me to......sometime loading apps can sometime take time to load and battery life falls quickly when downloading from market.........
farukb said:
also stock android keyboard doesn't work,and keyboard suggested in first post works a bit crappy (with all due respect),so you should use some other,i personally use swype and it doesn't matter if you swype or just type,because swype is great for typing too,it's fast and responses instantly (unlike betterkeyboard)
Click to expand...
Click to collapse
What recommendation do you have? I didn't think Swype was free..?
farukb said:
i think F22's rootfs are modified to fit rhodium which has keyboard and different button mapping so there is no need to use it...you know,no need for additional code lines which are not necessary
Click to expand...
Click to collapse
Probably true, I'll take that part out thanks.
farukb said:
what else does not work:
led notifications (do not work at all,also if you plug in the cable in WM before you run haret, orange notification(or green if it's fully charged) will continue to glow,so our android has no control over it,not even to turn it off)
Click to expand...
Click to collapse
orly... that's an odd bug. It seems that the hardware is not initialized by Android...
farukb said:
front camera
Click to expand...
Click to collapse
I'll add it, but don't expect it to work anytime soon .
farukb said:
if you use glemsom kernels your audio will stutter a bit,you can overcome this by using g3rm0's kernel found in this forum section....although it'd be nice if someone implemented anti-stuttering into glemsom(xdandroid official) kernels
Click to expand...
Click to collapse
I remember this bug, related to the battery code. g3rm0's kernel isn't such a good solution, it just kills the battery provider... I'll see if I can bug a dev into fixing it. Not sure what the actual problem is - does this persist even in the newest autobuild kernels?
farukb said:
@arrrghhh, i think you should remove the sensor rotation part of the post,because could confuse people...but then again you're the boss,so do as you please
Click to expand...
Click to collapse
For the DIAM? Is that not required? Sorry 'bout that. I removed it . I want this to be a Blackstone-specific thread, after all it is in the Blackstone forum. So anything I can do to help newbies with Blackstones is great. Keep up the feedback, and let me know how I can improve!
welard said:
all above quoted the same for me to......sometime loading apps can sometime take time to load and battery life falls quickly when downloading from market.........
Click to expand...
Click to collapse
Yup... apps loading for a while are partially due to the old hardware. Some of it might be the SD card being slow... NAND won't be a ton faster, but should give a little boost.
Battery life falls quickly because the battery driver is inherently flawed. There's some new battery software (SCBS) and it should improve this, but it doesn't seem like it'll be implemented into mainline anytime soon (many devices need support...)
arrrghhh said:
What recommendation do you have? I didn't think Swype was free..?
Probably true, I'll take that part out thanks.
orly... that's an odd bug. It seems that the hardware is not initialized by Android...
I'll add it, but don't expect it to work anytime soon .
I remember this bug, related to the battery code. g3rm0's kernel isn't such a good solution, it just kills the battery provider... I'll see if I can bug a dev into fixing it. Not sure what the actual problem is - does this persist even in the newest autobuild kernels?
For the DIAM? Is that not required? Sorry 'bout that. I removed it . I want this to be a Blackstone-specific thread, after all it is in the Blackstone forum. So anything I can do to help newbies with Blackstones is great. Keep up the feedback, and let me know how I can improve!
Yup... apps loading for a while are partially due to the old hardware. Some of it might be the SD card being slow... NAND won't be a ton faster, but should give a little boost.
Battery life falls quickly because the battery driver is inherently flawed. There's some new battery software (SCBS) and it should improve this, but it doesn't seem like it'll be implemented into mainline anytime soon (many devices need support...)
Click to expand...
Click to collapse
will we see meny of these fixes in frx07 and gingerbread in the next release? (nice to see things are happening here again by the way)
@argh
swype is free,you just need to register and you gain access to swype beta
it's called beta because it is made for devices that don't come with if out of the box and therefore are still developing it,but it works great,nevertheless
welard said:
will we see meny of these fixes in frx07 and gingerbread in the next release? (nice to see things are happening here again by the way)
Click to expand...
Click to collapse
well actually,nothing is happening at all all this is available since march (except for some of the incremental updates which chronologically came out later)
farukb said:
well actually,nothing is happening at all all this is available since march (except for some of the incremental updates which chronologically came out later)
Click to expand...
Click to collapse
what mean is help for making our blackstone run better because there was no one here to tell the problems we face on frx06 and gingerbread......now that arrrghhh is looking into our problems things mite just happen now.........
welard said:
what mean is help for making our blackstone run better because there was no one here to tell the problems we face on frx06 and gingerbread......now that arrrghhh is looking into our problems things mite just happen now.........
Click to expand...
Click to collapse
they might,but arrrghhh is a tester,not sure if he is a dev himself,but he could help pursue devs to do it
as for improvements,very few improvements happened at all over last few months to any device supported by xdandroid project
welard said:
what mean is help for making our blackstone run better because there was no one here to tell the problems we face on frx06 and gingerbread......now that arrrghhh is looking into our problems things mite just happen now.........
Click to expand...
Click to collapse
I was always around, but having dedicated threads in the Blackstone section will help. I tried to get others to create threads to support Blackstone, but I guess no one ever did... So here I am! Trying to support without a device.
If anyone feels like donating a device, it would be much appreciated. XDAndroid will pay shipping if you're willing to donate the device to a dev!
farukb said:
they might,but arrrghhh is a tester,not sure if he is a dev himself,but he could help pursue devs to do it
as for improvements,very few improvements happened at all over last few months to any device supported by xdandroid project
Click to expand...
Click to collapse
This is not true! There's been a ton of development over the last few months... It happens in spurts, but there has been quite a bit.
I'm not much of a dev (played around with init, working on getting rid of manual ts-calibration) but I am 'lead tester' for the project, I maintain the wiki, releases, and track bugs on the bugtracker.
arrrghhh said:
I was always around, but having dedicated threads in the Blackstone section will help. I tried to get others to create threads to support Blackstone, but I guess no one ever did... So here I am! Trying to support without a device.
If anyone feels like donating a device, it would be much appreciated. XDAndroid will pay shipping if you're willing to donate the device to a dev!
This is not true! There's been a ton of development over the last few months... It happens in spurts, but there has been quite a bit.
I'm not much of a dev (played around with init, working on getting rid of manual ts-calibration) but I am 'lead tester' for the project, I maintain the wiki, releases, and track bugs on the bugtracker.
Click to expand...
Click to collapse
i have not a device to donate.....but if we all donate for a device that would speed things up much faster...... i think you should start a new thread for donate for a blackstone device......im sure theres lots of blackstone users willing to do this because the end result will pay off for all of us.......
i had a sod and now i can't boot,the animation just keeps looping...hw buttons vibrate then i touch them,but do not work....power button doesn't work either
happened to me once before,but i don't know what i did to solve it...i maybe deleted the data.img
this time i tried to wipe and format the partition,didn't help
i tried with fresh files (except for the data.img) but still nothing...
@arrrghhh: wanna swap with me for your rhodium,if you want it badly?
@werald and others:if we are going to donate a device,it'd be best to donate it do a dev,maybe stinebd,don't know

[FIX][ICS][Stock ROMs and derivates][08/07]CRT-On and CRT-Off effects

As reported in multiple places on the forum, stock ICS ROMs do not come with the CRT-Off effect available, although the code is there and lots of existing mods already exist to be able to turn it on.
The implementation, however, contains a glitch and every once in a while the full screen image will blink right after the beam collapses.
I have managed to apply the fix to the Sammy's custom library that implements this, even though the source code is not available. (this wouldn't be possible without the good folks on CM9, though!).
The discussion that lead to this work can be found here, on the awesome JKay mod. BTW, if this fix is useful to you, do me a favor a buy that man's Deluxe app (it's really a favor you're doing to yourself, not me ).
For any ROM cookers, MOD developers, or end-users, I leave the patched file and a few instructions to make sure the provided lib only changes the flicker part. This is because I have performed the changes on the file shipped on XWLP9, and if other different files exist in other builds, it's more convenient to apply the fix there instead of using the lib from a different ROM and possibly lose some other improvements or fixes applied by Samsung.
Please check the Readme file in the archive for instructions on what to confirm and how to apply the change, and let me know if there's any question or if you have a different base version.
EDIT:
The library has been updated to handle CRT-On effect as well. You can safely replace it with the attached version, although you'll need to have a mod to activate the CRT-On effect as well.
If you want to install a standalone patch to activate this, have a look at this post and follow the instructions.
Technical notes
The code has been revised to display 8 frames when turning on - as opposed to 24 when turning off - in order to have a faster response. This is however still dependent on the time taken by the kernel to wake the CPU, before drawing can begin (currently about 1s). This delay will not happen if you don't wait long enough after turning off, as the CPU will not enter deep sleep.
Changes from Kamma have also been applied, in order to have a similar effect when turning On - "normal" screen colors instead of random color spikes. This might be barely noticeable due to the animation speed.
EDIT2:
No more issues with the library, it now works perfectly with Youtube playing videos, etc. Also the CRT-On effect is now very smooth (although faster than CRT-Off, on purpose).
Major kudos to rovo89 for turning an initial hack to fix the glitches in a polished final product!!!
Be aware that this just contains the library for the effects to work properly. You'll still need your ROM to be modded to activate them (instructions included in this zip file), or, better yet, install rovo89's Xposed Tweakbox module which overrides the behavior without replacing any files and should work even with non-stock roms.
Out of the box solutions for getting the CRT effects
Tweakbox by rovo89 (and a bit of help from myself) - works for pretty much all stock roms and derivatives, odexed or deodexed. It's even working for S3, since it contains a patched file from that model.
If you're using Deodexed XWLPG, you can also go to this post by The Undertakerr and fetch a flashable zip that contains everything that's needed to have CRT_On and CRT_Off effects always active.
Works great on Wanam V11.7 (LPD)
Wow thanks a lot for this
Enviado desde mi GT-I9100 usando Tapatalk 2
Thanks man!
Applied JKay's CRT mod just today and noticed the bug, now you fixed it!
I try on Turkbeyrom V9 Lpd. Its working perfect.
Wysłane z mojego GT-I9100 za pomocą Tapatalk 2
@ Tungstwenty
... Carried over from jkays thread,
You're right i didn't have any anything to turn crt on, i presumed it enabled it by default, since i flashed a similar fix from another thread and it enabled it straight off.
So hopefully jkay includes it in his mod and 'jobs a goodin'
Cheers
Sent via courier pigeon
Works perfect on Wanam V11.7.
Thank man!!
This is working great, also on LPQ. I also thought about patching the library directly, but didn't know where I could get the replacement code from. Great work!
I have been working hard today to bring some binary patching functionality to Xposed. Finally, I think I was successful. Learned some new things, like modifying a different process' memory. That will make it possible to patch the library on the fly, just if the MD5 sum matches etc. I believe this will make it easier to use for those who are not as experienced with adb/SSH/...
rovo89 said:
This is working great, also on LPQ. I also thought about patching the library directly, but didn't know where I could get the replacement code from. Great work!
I have been working hard today to bring some binary patching functionality to Xposed. Finally, I think I was successful. Learned some new things, like modifying a different process' memory. That will make it possible to patch the library on the fly, just if the MD5 sum matches etc. I believe this will make it easier to use for those who are not as experienced with adb/SSH/...
Click to expand...
Click to collapse
Wow, that would be yet another massive leap in your framework. Patching e.g. native libs on running processes from within java would really be awesome
If you've reached that stage already, you probably already know that "cat /proc/nnnn/maps" yields interesting information on where each library's segment is mapped. Other pseudo-files on that path also hold tons of information just waiting to be explored and hacked
Works perfectly well on LPF build.
I'm wondering whether its possible for you to make a flash able version?
SGSII GT-i9100 via Tapatalk II
I pasted it using romtoolbox but it didnt work so I rebooted and it works !!
Thanks
Tungstwenty said:
Wow, that would be yet another massive leap in your framework. Patching e.g. native libs on running processes from within java would really be awesome
If you've reached that stage already, you probably already know that "cat /proc/nnnn/maps" yields interesting information on where each library's segment is mapped. Other pseudo-files on that path also hold tons of information just waiting to be explored and hacked
Click to expand...
Click to collapse
Indeed, I'm using the files in /proc for patching. Plus "ptrace" to manipulate the /system/bin/surfaceflinger process, after I noticed that the library isn't used directly by any process started by Zygote. And for the patch file, I'm using bsdiff and a MD5 sum comparison.
If anyone would like to try out, here are betas of the upcoming Xposed framework and the Tweakbox. Installing instructions are in the linked threads. Afterwards, you can check "Patch libsurfaceflinger.so" in the Tweakbox settings, which will become effective after a reboot (but doesn't require replacing any files).
Please note that I have also added new helper methods for developers. Let me know in case setting the statusbar clock color is not working for you.
Tungstwenty said:
Wow, that would be yet another massive leap in your framework. Patching e.g. native libs on running processes from within java would really be awesome
If you've reached that stage already, you probably already know that "cat /proc/nnnn/maps" yields interesting information on where each library's segment is mapped. Other pseudo-files on that path also hold tons of information just waiting to be explored and hacked
Click to expand...
Click to collapse
I've been testing your lib for 2 days now and as i told you in Jkay's thread flicker bug is gone
The only thing i noticed,happened only 2 times ,i had no crt off effect at all.
The screen locked as in stock.
Thank you for this
Please check and confirm guys..
Unlock screen, do not do anything. Just wait 7-8 Seconds without touching on the screen and then turn off screen, there will not be any CRT Off effect.
This, Tungstwenty, is a huge step forwards in development of the I9100. Even on Gingerbread the CTROff effect wasn't as beautiful as it is now!
CtrON is also available allready for ICS 4.0.3, only not for our device.
XDA member Kamma made it work on the Galaxy Nexus, and also posted the sources for it.
It involves changes in the libsurfaceflinger.so and in the services.jar.
Since you seem to be able to make changes in the .lib, my hope is on you, perhaps you could also bring the CRTON to the I9100 with ICS!
Sources+ info you can find in this thread:
http://forum.xda-developers.com/showthread.php?t=1490127
Thanks in advance for looking into it and bringing us a perfect CrtOff!!!
The Undertakerr said:
This, Tungstwenty, is a huge step forwards in development of the I9100. Even on Gingerbread the CTROff effect wasn't as beautiful as it is now!
CtrON is also available allready for ICS 4.0.3, only not for our device.
XDA member Kamma made it work on the Galaxy Nexus, and also posted the sources for it.
It involves changes in the libsurfaceflinger.so and in the services.jar.
Since you seem to be able to make changes in the .lib, my hope is on you, perhaps you could also bring the CRTON to the I9100 with ICS!
Sources+ info you can find in this thread:
http://forum.xda-developers.com/showthread.php?t=1490127
Thanks in advance for looking into it and bringing us a perfect CrtOff!!!
Click to expand...
Click to collapse
It is not perfect, please check my post above and confirm..
mzeshanhakeem said:
Please check and confirm guys..
Unlock screen, do not do anything. Just wait 7-8 Seconds without touching on the screen and then turn off screen, there will not be any CRT Off effect.
Click to expand...
Click to collapse
Tried to reproduce this a couple of times, but it always worked fine. I turned the phone on, unlocked (using WidgetLocker), then didn't do anything for few seconds and pressed the power button to lock the phone. The effect is showing for me.
mzeshanhakeem said:
It is not perfect, please check my post above and confirm..
Click to expand...
Click to collapse
I cannot confirm the behaviour you have, I'm sorry. It's nothing new. The thing you describe also happened before the change made to libsurfaceflinger.so by Tungstwenty.
It even also happened on Gingerbread!
Sometimes the lockscreen also freeze for a few secs, but that's also not because of this change. You can read about it in the Siya kernel thread, seems to be related to the newest Siyakernel...
The Undertakerr said:
I cannot confirm the behaviour you have, I'm sorry. It's nothing new. The thing you describe also happened before the change made to libsurfaceflinger.so by Tungstwenty.
It even also happened on Gingerbread!
Sometimes the lockscreen also freeze for a few secs, but that's also not because of this change. You can read about it in the Siya kernel thread, seems to be related to the newest Siyakernel...
Click to expand...
Click to collapse
That may be the reason.
I am on Wanam v11.8 with CF Root Kernel.
mzeshanhakeem said:
Please check and confirm guys..
Unlock screen, do not do anything. Just wait 7-8 Seconds without touching on the screen and then turn off screen, there will not be any CRT Off effect.
Click to expand...
Click to collapse
I cannot reproduce this also.
Tried just turning on screen and leave it alone, it will automatically CRT Off after 10s with my current settings. If I press Power 1 or 2 seconds before that, it still does the effect.
Also tried it with actual unlocking (going to the home screen), and effect also displays when turning off after 8s idle.
Does it always happen to you?
Running on XWLPF with JKay and Siyah 3.2.6.3

[ROM] MIUI Port

This ROM is in no way suitable for daily use and is only shared so that other fellow developers can take a look and maybe provide fixes to one or multiple things on the "not working" list.
Take it as a very early proof of concept.
ROM DOWNLOAD: http://www.androidfilehost.com/?fid=23501681358554238
What I did to get this far...
1. I took the MI3W miui-germany ROM
2. I unpacked the MI3W's ROM
3. I unpacked the boot.img of the MI3W ROM (zImage, dt.img, ramdisk)
4. I patched the fstab.qcom and init*.rc files to match the Find 7a
5. I unpacked the latest OmniROM for Find7a
6. I unpacked the boot.img of OmniROM (zImage, dt.img, ramdisk)
7. I copied zImage and dt.img from OmniROM's extracted boot.img into MI3W's extracted boot.img
8. I repacked the MI3W boot.img
9. I bundled the MI3W system partition with the modified MI3W boot.img and uploaded it onto the internet for someone else to iron out the remaining bugs
What seems to work...
*) Basic Operation (MIUI apps, status bar, well what you would expect really)
*) Bluetooth
*) Wired Headset / Bluetooth Audio
*) RIL / Mobile Data
*) GPS
What doesn't work... yet...
*) WiFi (there seems to be some issues with wcnss / pronto / prima, this one is bad...)
*) Random Reboots / Blackscreen Glitches (from what kmsg tells me it seems to be related to wcnss, aka. WiFi drivers causing a critical error in kernel every once in a while, fix WiFi and this error will fix itself)
*) Speaker Audio
*) Rotation Sensor (and probably others)
*) Vibration
*) Skyline Notification Light
*) NFC
For pictures check the thread at the oppoforums: http://www.oppoforums.com/threads/rom-miui-port-for-find-7a.17409
Good things always have the obstacles.
You've done your part. And let other(s) help you.
I don't have knowledge about cooking a ROM.
But I think someone can help. @Entropy512, can you look at this one?
If you want mae some cool port, i thikn sense rom is good candidate...
Great work
hey there mrcoldbird,
great work so far...keep it up..will definately help support you on this when it is up and running..i am not a dev but if you need someone to just bug report i am there for you,will keep my eyes n ears peeled on the thread and as soon as it's near ready i will flash and help you anyway i can...thank you for all your hard work so far
Right now we need developers involved in this. We know the countless obvious bugs.
Just have to fix them.
Awesome work. Thanks bird. Any chance you want to try lewa os while you're at it. I personally think it is better. I imagine just how busy you are but just wanted to throw it out there
Porting really should only be done when there is no source available for said ROM.
For unicorn a source rebuild might be better.
MrColdbird said:
Porting really should only be done when there is no source available for said ROM.
For unicorn a source rebuild might be better.
Click to expand...
Click to collapse
I updated my post. You should really check out lewa. It has find 5 official support
uppon2 said:
I updated my post. You should really check out lewa. It has find 5 official support
Click to expand...
Click to collapse
no news about this rom
I was actually searching for people to help me with this but no one bit the bait yet.
I am continually working on MIUI, bit by bit... but due to reallife interference it goes... slowly.
MrColdbird said:
I was actually searching for people to help me with this but no one bit the bait yet.
I am continually working on MIUI, bit by bit... but due to reallife interference it goes... slowly.
Click to expand...
Click to collapse
ok thanks for answer. i love miui rom. i think it can be the best rom for find 7a
good luck
---------- Post added at 12:23 PM ---------- Previous post was at 12:21 PM ----------
MrColdbird said:
I was actually searching for people to help me with this but no one bit the bait yet.
I am continually working on MIUI, bit by bit... but due to reallife interference it goes... slowly.
Click to expand...
Click to collapse
if you need help for test rom tell me. i have a lot of time for this.
when i try to install your rom twrp failed. do you know why ?
jazzypit said:
no news about this rom
Click to expand...
Click to collapse
Lewa OS website
YouTube video
uppon2 said:
Lewa OS website
YouTube video
Click to expand...
Click to collapse
no rom for oppo find 7a
do you have a link for test ?
jazzypit said:
no rom for oppo find 7a
do you have a link for test ?
Click to expand...
Click to collapse
No. That is what I'm asking for; a build for lewa for the find 7.
uppon2 said:
No. That is what I'm asking for; a build for lewa for the find 7.
Click to expand...
Click to collapse
Which doesn't belong in this thread. Take it elsewhere.
justin654 said:
Which doesn't belong in this thread. Take it elsewhere.
Click to expand...
Click to collapse
Lewa OS is extremely similar to MIUI and that is why I even bothered to mention it. I know the developer is having some trouble with MIUI so I thought it would be useful and helpful to mention Lewa as it might be a project that will help the development of either or rom.
Please don't take a blunt tone with me (if that's what it was) as it only makes you look arrogant. Taking in to account our post and thanks scores it is quite clear who has contributed in a more positive way towards XDA. On that note; you might also want to thank MrColdbird in the OP for his contribution, which you have not done as of yet but you seem to be poking your nose in to the thread
That is all
Edit* I apologise MrColdbird if my suggestion was unwarranted.
MrColdbird said:
I was actually searching for people to help me with this but no one bit the bait yet.
I am continually working on MIUI, bit by bit... but due to reallife interference it goes... slowly.
Click to expand...
Click to collapse
I am setting up a build environment and will be looking in to it; starting with wifi. I think I might check out lewa as well.
good luck
I've pm one of the Miui dev from note 1 community, and hope that he willing to lend his hand for you @MrColdbird.
Mr @Gerrett, can you help him? If you got some free time. I know you so busy. But at least, just a little guide for him.
FareedYusoff said:
I've pm one of the Miui dev from note 1 community, and hope that he willing to lend his hand for you @MrColdbird.
Mr @Gerrett, can you help him? If you got some free time. I know you so busy. But at least, just a little guide for him.
Click to expand...
Click to collapse
Actually I've got 99% of the issues resolved already by using a different port-rom in conjunction with a few OmniROM injects.
At the moment only the proximity sensor (screen off on holding the phone to your ear) and nfc are broken, lte works, but needs to be reselected every time the phone reboots via the service menu (dialer code).
Sadly, I'm not allowed to share that (quite nicely working) ROM just yet as I switched port-bases to a unreleased chinese one in favor of the MI3W port-base.
Until that chinese author releases his first public port base-rom I'm kinda bound by the promise I gave not to unveil things early.
Just hang in there, it shouldn't be long until you guys have MIUI on Find7a... all I can tell you is that it works nicely and without any critical flaws I can see except those mentioned above (which we will get fixed too eventually).
MrColdbird said:
Actually I've got 99% of the issues resolved already by using a different port-rom in conjunction with a few OmniROM injects.
At the moment only the proximity sensor (screen off on holding the phone to your ear) and nfc are broken, lte works, but needs to be reselected every time the phone reboots via the service menu (dialer code).
Sadly, I'm not allowed to share that (quite nicely working) ROM just yet as I switched port-bases to a unreleased chinese one in favor of the MI3W port-base.
Until that chinese author releases his first public port base-rom I'm kinda bound by the promise I gave not to unveil things early.
Just hang in there, it shouldn't be long until you guys have MIUI on Find7a... all I can tell you is that it works nicely and without any critical flaws I can see except those mentioned above (which we will get fixed too eventually).
Click to expand...
Click to collapse
Quite fast actually. By the way, I just can wait and see your nice work.
I'm trying to help, but that's all I can do right now. All the best on your effort.
I appriciate your hardwork. :highfive:

Custom 7.0 ROM for the Galaxy s6 edge Plus!

This device may be a few years old, but its still great. Support for it has almost disappeared, but there are still people out there like me that are on this device that can't/won't upgrade for one reason or another. Sure, Superstock is a great ROM, but lollipop is outdated, and having the features of custom ROMS but on a newer base would be freaking great. I am right?
I may have missed them, but as far as I could find on XDA, I couldnt find any nougat custom ROMs for this device. I would super excited to petition for one of the awesome developers out there to make a new ROM, even if it might be the last for this phone. Or maybe there is one, and I have just been much to dense to see it. Let this thread be for all posts related to the development of a custom Nougat rom, or sharing of one that already exists. Thanks everyone for reading and participating! :laugh:
EDIT: SM-G928T is the model number, just in case it isn't implied
"petition for one of the awesome developers out there to make a new ROM"
Wow... no need to do that buddy..
I'll save you the headache, hassle and lynching..
Check this out.. https://forum.xda-developers.com/s6-edge-plus
Heads up, read thru the thread carefully, many of these ROMs will require the "T-Mobile audio fix" to get in call audio, that is if you have the T-Mobile variant (G928T). You can search for the fix..
We can run Note 5 ROMs too, check out the TMo N5 or the Int'l forums, like I mentioned, above.
Talysdaddy said:
"petition for one of the awesome developers out there to make a new ROM"
Wow... no need to do that buddy..
I'll save you the headache, hassle and lynching..
Check this out.. https://forum.xda-developers.com/s6-edge-plus
Heads up, read thru the thread carefully, many of these ROMs will require the "T-Mobile audio fix" to get in call audio, that is if you have the T-Mobile variant (G928T). You can search for the fix..
We can run Note 5 ROMs too, check out the TMo N5 or the Int'l forums, like I mentioned, above.
Click to expand...
Click to collapse
Thanks for the response. I had no idea we could run international ROMs on variant devices. I am having the issue you mentioned, though, with the call audio. So far ive tried two roms, flashed the fix, without any change. Ideas as to how i might get that working?
There is a audio fix on the T mobile Galaxy Note 5 page, it worked for me using Dr Ketan's rom
N
LEGONIKES said:
Thanks for the response. I had no idea we could run international ROMs on variant devices. I am having the issue you mentioned, though, with the call audio. So far ive tried two roms, flashed the fix, without any change. Ideas as to how i might get that working?
Click to expand...
Click to collapse
I do know that theres a few different "audio fixes" available. Im thinking they differ bcuz of the Android version? Just a guess, but what I'll do, is, I'll use only Roms that another 928T user already reported their success using it. I dont want to waste my time and effort being the guinea pig and then, for it not to work. Usually, whomever confirmed compatibility, will also list anything thats needed additionally to get it running, like the audio fix, along with link(s) to get it. If it doesn't work, they'll usually state the issues they found. Someone else's issue with it, might not be relevant to another person so they may decide to run it.
The best way to do this is to simply go to the OP of the Rom thread, in the upper right corner, you'll see a "search" option/box, (depending on browser or app, might see 3 dots instead, its a drop down list) click on it and enter our phone model, "928T, 928-T" or "T-Mobile, Tmobile, TMO " I try to cover the different variations, others here use to identify the phone. Seems like the search function, searches only the exact characters, as entered in the box, doubting it can identify and include similar known ones, so rather be thorough and not miss something. It searches your entry only in that particular thread and lists the results.
If you're braver than I, and dont mind going where no other TMO'rs have gone before and found only the in call audio isnt working, then its likely, flashing the audio fix is all thats needed.
The best way to solve this is, again, with a simple search. This time I'd recommend, a broader search using Google's search engine, type "XDA T-Mobile audio fix," bcuz this will search all XDA forums, more importantly, both S6 E+ and N5, carrier and int'l forums all at once. Then just go down the list if results, making sure that youre in either of the 4 forums, above, locating the download. Last I checked there was 3 or so fixes available, this was many months ago though. Anyway, having more isnt a bad thing, less would mean needing to go back and finding the one you missed. Once you have them, flash each one seperately, in recovery, reboot, confirm whether you're issue is fixed or not. If not, then continue these steps till it works. Flashing the audio fix won't mess your phone up. No need to reset, clear cache or anything of the sort, between each audio fix, just flash only the audio fix and rebooting is necessary. If you want to be organized, you can cross reference the dates of each audio fix, with the current firmware available at the time. That way you can flash any Rom you desire and will already have the fix ready.
Wow, my apologies, talk about rambling on about nothing more than finding correct file, flash your device, confirm its fixed, if not then repeat till its fixed. If no fix is found then, Rom isnt compatible...
Sorry, one last thing, Im sure that you'll help many others like yourself, if you had minute to post your experience with whichever Rom(s), you chose.
For example, "Rom works great, needed this (link to audio fix) for in call audio on the TMO variant"
It seems like you're the first 928T to try the Rom you have so,
report your experience, posts are permanent, its there forever, for any curious new comers, you'd be their hero! It'd most def get a "thx" from me.. :good:
Any updates on your experience here?
Zulmonster said:
Any updates on your experience here?
Click to expand...
Click to collapse
Found a few ROMs that work without fixes and run nougat. Khongloi's s8 port works and has some of the best features I've ever had on this phone, but is heavy on the battery. AndroidSword's NFuel XL runs fast and light, but doesn't have edge features. The original NFuel also has full support for 928T, but I haven't tried it yet. I'm also working on my own custom ROM now since every ROM I tried was missing something I wanted.
LEGONIKES said:
Found a few ROMs that work without fixes and run nougat. Khongloi's s8 port works and has some of the best features I've ever had on this phone, but is heavy on the battery. AndroidSword's NFuel XL runs fast and light, but doesn't have edge features. The original NFuel also has full support for 928T, but I haven't tried it yet. I'm also working on my own custom ROM now since every ROM I tried was missing something I wanted.
Click to expand...
Click to collapse
Thanks for the info. My S8 has kicked the bucket, and so I'm back on my S6 for the time being and want to give it a bit of a refresh. I'll look up those NFUEL ROMs.
Zulmonster said:
Thanks for the info. My S8 has kicked the bucket, and so I'm back on my S6 for the time being and want to give it a bit of a refresh. I'll look up those NFUEL ROMs.
Click to expand...
Click to collapse
Nearly lost my phone today and realized find my mobile does not work on NFuel XL. Would not recommend if your one to lose you phone like me.
Zulmonster said:
Thanks for the info. My S8 has kicked the bucket, and so I'm back on my S6 for the time being and want to give it a bit of a refresh. I'll look up those NFUEL ROMs.
Click to expand...
Click to collapse
I've just finished cooking a second version of my custom rom. Haven't had any issues so far. It's Called TrueStockN.
Here's a list of ROMs I was able to get working for the G928T:
Khongloi's s8 Port
Nemesis s7 Port
N-Fuel
TrueStockN
These are just Nougat roms I that worked for me off the bat, no additional audio fix required. Of course, there may be more, but these are the ones I know of and have used extensively.

General Pre rooted roms(project rooted)

Mod edit: TG link removed as per XDA's TG Chat Rules.
(TG link and home page was removed I can only see in their rules the TG link all good so adding back the home page to the home page)
I started project rooted to provide pre rooted roms to people. I'm looking for someone to help with pixel 6 pro. If anyone is interested please let me know. All it really is is patching operating systems, recompiling then, and sharing them.
I think that there is no value at all in this project. All anyone needs to do is run the original boot.img through magisk before they write it to the boot partition and the job is done.
In addition, if anyone was inclined to use 3rd party hosted pre-rooted (or not) boot images, I would VERY STRONGLY recommend that they DO NOT. This is simply because it opens them up to whatever other undisclosed changes happen to have been added to it.
Thanks for the feedback!!! I can assure you that there is absolutely no malicious intent or anything out of the ordinary in these roms. I've had mixed responses with some liking and disliking the project. If it's not your preference no problem I'm not going to stop you from doing it manually or not using my project either way. I'm doing this for fun and am providing a convenient place for roms in one place(without having to search through chats) and with the bonus of being rooted from the start.
Edit: typo
Jacobh1245 said:
Thanks for the feedback!!! I can assure you that there is absolutely no malicious intent or anything out of the ordinary in these roms. I've had mixed responses with some liking and disliking the project. If it's not your preference no problem I'm not going to stop you from doing it manually or not using my project either way. I'm doing this for fun and am providing a convenient place for roms in one place(without having to search through chats) and with the bonus of being rooted from the start.
Edit: typo
Click to expand...
Click to collapse
And I can absolutely assure you that I am a Nigerian Prince, and if you direct deposit $500 into my bank acount, I will turn it into $5,000,000.
Gytole said:
And I can absolutely assure you that I am a Nigerian Prince, and if you direct deposit $500 into my bank acount, I will turn it into $5,000,000.
Click to expand...
Click to collapse
Lol, I get it. I'm not well known or trusted yet as this is not my first project but first I've tried to get out there as much as I am. Again I'll reiterate that you don't have to use it if you don't trust it all my work is posted even the as basic as it is website is open source on GitHub. If you have any genuine feedback for me I'd love to hear it. Constructive feedback on how to get started and trusted wouldn't be so bad. Thanks for your opinion though, it's good to hear what a community thinks of new projects/ideas
Jacobh1245 said:
Lol, I get it. I'm not well known or trusted yet as this is not my first project but first I've tried to get out there as much as I am. Again I'll reiterate that you don't have to use it if you don't trust it all my work is posted even the as basic as it is website is open source on GitHub. If you have any genuine feedback for me I'd love to hear it. Constructive feedback on how to get started and trusted wouldn't be so bad. Thanks for your opinion though, it's good to hear what a community thinks of new projects/ideas
Click to expand...
Click to collapse
Thanks for being a great sport
Is there benefit in having it pre rooted? Perhaps easier to pass the safety checks for banking apps?
TrustAugustus said:
Is there benefit in having it pre rooted? Perhaps easier to pass the safety checks for banking apps?
Click to expand...
Click to collapse
Yes I have had better success with safetynet since doing this they don't always work out like that but for the most part it's been better. As far as pre-rooted with pixel devices it's not too hard to do, just time consuming. I'm going to build a set of instructions tonight for my website as to how to do so yourself for those who would rather do it manually
That sounds great. I'm looking forward to the project.
Back... like 10 years ago roms came pre rooted as well
TrustAugustus said:
That sounds great. I'm looking forward to the project.
Back... like 10 years ago roms came pre rooted as well
Click to expand...
Click to collapse
I remember that was one of the best things ever. That's just one of my reasons I wanted to do this. THANKS for the support!!!
Jacobh1245 said:
I remember that was one of the best things ever. That's just one of my reasons I wanted to do this. THANKS for the support!!!
Click to expand...
Click to collapse
We understand, just with the new safeties built into to hardware anymore it can comicate things for some people. I am not saying prerooted is WRONG, it can just cause problems. It's not you. Lol
Yeah, some devices can, some won't. I am alware of these but also understand the risk is minimal and unlikely to be president. Reality with anything like this even down to the roms themselves have so many variables that could cause problems. Which I why I have taken the extra steps to test that I have a solidly rooted Rom
Jacobh1245 said:
I started project rooted to provide pre rooted roms to people. I'm looking for someone to help with pixel 6 pro. If anyone is interested please let me know. All it really is is patching operating systems, recompiling then, and sharing them.
Click to expand...
Click to collapse
For anyone who might want to know this. I have a very poor excuse for a guide on making pre rooted roms on my page now if you have a pixel device it does work. It was quickly put together and I WILL update it SOON and will add screenshots to help as well as fine tuning the wording.
What would be nice is to have the installation routinely root the boot.img if the system is pre-rooted, like Lineage 18 does on my 1+7pro.
Jacobh1245 said:
Thanks for the feedback!!! I can assure you that there is absolutely no malicious intent or anything out of the ordinary in these roms. I've had mixed responses with some liking and disliking the project. If it's not your preference no problem I'm not going to stop you from doing it manually or not using my project either way. I'm doing this for fun and am providing a convenient place for roms in one place(without having to search through chats) and with the bonus of being rooted from the start.
Edit: typo
Click to expand...
Click to collapse
Its not a question of you having malicious intent. Its a question of best practices for security. Other people who may be more or less trustworthy than you may have similar projects (and in fact, I remember another thread with this exact purpose), and trusting those may be quite dangerous.
But more to the point, and WITHOUT putting your trustworthiness or honor in question, how can anybody know whether you are *actually* trustworthy or just someone claiming (falsely) to be?
And since the process of running it through Magisk is so absurdly trivial, what advantage does this provide to users to compensate them for the risk?
Advantages: nil
Risks: elevated
Rational choice: avoid.
96carboard said:
Its not a question of you having malicious intent. Its a question of best practices for security. Other people who may be more or less trustworthy than you may have similar projects (and in fact, I remember another thread with this exact purpose), and trusting those may be quite dangerous.
But more to the point, and WITHOUT putting your trustworthiness or honor in question, how can anybody know whether you are *actually* trustworthy or just someone claiming (falsely) to be?
And since the process of running it through Magisk is so absurdly trivial, what advantage does this provide to users to compensate them for the risk?
Advantages: nil
Risks: elevated
Rational choice: avoid.
Click to expand...
Click to collapse
It does a few things, it in many cases seems to help with safetynet being easier to pass( not always some roms are more stubborn). It provides a convinent place where everything is at. All my stuff is open source and downloadable so you may check whatever you want. Though I don't have the source code to the roms since I'm not building them. And I put links to the roms group chat and instructions as to how(for pixel devices) to make a pre-rooted rom yourself. So if you don't trust it but want it I give how to and where to get the files to do so some also fear that things may not work as mentioned above can happen but is very minimal especially since I test before releasing.
Jacobh1245 said:
It does a few things, it in many cases seems to help with safetynet being easier to pass( not always some roms are more stubborn). It provides a convinent place where everything is at. All my stuff is open source and downloadable so you may check whatever you want. Though I don't have the source code to the roms since I'm not building them. And I put links to the roms group chat and instructions as to how(for pixel devices) to make a pre-rooted rom yourself. So if you don't trust it but want it I give how to and where to get the files to do so some also fear that things may not work as mentioned above can happen but is very minimal especially since I test before releasing.
Click to expand...
Click to collapse
What version of Magisk do you intend to use? Because on at least 2 or 3 occasions due to Google changing things, Canary has been needed. On the other hand, there have also been occasions where Canary broke some things and Stable was needed.
Because the Pixel 6 series seems to be "often" affected by changes made by Google in their monthly updates, as well as Magisk itself, it seems that pre-rooting a rom on the Pixel 6 series "may" cause some unintended problems.
It's been quite the cat and mouse game when it comes to the Pixel 6 series and rooting in terms of these changes, and not in terms of just rooting itself, but other things like custom kernels, etc..
Lughnasadh said:
What version of Magisk do you intend to use? Because on at least 2 or 3 occasions due to Google changing things, Canary has been needed. On the other hand, there have also been occasions where Canary broke some things and Stable was needed.
Because the Pixel 6 series seems to be "often" affected by changes made by Google in their monthly updates, as well as Magisk itself, it seems that pre-rooting a rom on the Pixel 6 series "may" cause some unintended problems.
It's been quite the cat and mouse game when it comes to the Pixel 6 series and rooting in terms of these changes, and not in terms of just rooting itself, but other things like custom kernels, etc..
Click to expand...
Click to collapse
Currently I've been using v25.0 that is one thing I test too and check with others about. So far 25.0 is working great with the minor detail of having to download the magisk apk and install rather then the greyed out icon to "update" but it still works exactly the same and I have not experienced anything broken so far
Jacobh1245 said:
Currently I've been using v25.0 that is one thing I test too and check with others about. So far 25.0 is working great with the minor detail of having to download the magisk apk and install rather then the greyed out icon to "update" but it still works exactly the same and I have not experienced anything broken so far
Click to expand...
Click to collapse
Yes, but there have been occasions where after a monthly update a Canary version was needed (e.g. December update when Google moved its fstab to /system/etc.) and John had to update Magisk and push a Canary version before people could actually boot a rooted boot image.
And I'm curious if you closely follow the issues, PRs and commits in the Magisk Github? For example, Beta 25.0 has changed (actually changed with Canary 24303 I believe) so that custom kernels will no longer boot unless verity and verification are disabled or if the kernel uses the latest AK3 which patches vendor_dlkm.img and vbmeta.img, or if the kernel patches them itself.
My point is there could be some unintended consequences for people who may not be aware of any current issues unless they are made aware of them before flashing a pre-rooted rom.
Anyway, if people find this useful then good for them and good for you.
Lughnasadh said:
Yes, but there have been occasions where after a monthly update a Canary version was needed (e.g. December update when Google moved its fstab to /system/etc.) and John had to update Magisk and push a Canary version before people could actually boot a rooted boot image.
And I'm curious if you closely follow the issues, PRs and commits in the Magisk Github? For example, Beta 25.0 has changed (actually changed with Canary 24303 I believe) so that custom kernels will no longer boot unless verity and verification are disabled or if the kernel uses the latest AK3 which patches vendor_dlkm.img and vbmeta.img, or if the kernel patches them itself.
My point is there could be some unintended consequences for people who may not be aware of any current issues unless they are made aware of them before flashing a pre-rooted rom.
Anyway, if people find this useful then good for them and good for you.
Click to expand...
Click to collapse
I which case testing would show that plus I'm usually pretty good at keeping up with that kind of thing. It is a valid concern but since the versions I release are going to have the correct version for them I will do the same for each rom indevidually as need to make sure they will work properly. Whenever a new version is released. That too means if you are on the same rom and dirty flash to the next one magisk will prompt you to update the app(has been tested too)

Categories

Resources