Installed Lineage OS by Sultan - ONE Q&A, Help & Troubleshooting

And the problem is that, my bottom display does not work, the hardware part and also the place where software buttons appear. ( I have been living with this issue for months, I installed pie app which is way better )
The only problem is that I cannot go any further because pressing "Next" does not work (Nor I can swipe my screen to go left.. whaaaat???). I need the next to be able to be a bit more up so that I can continue with the setup. I cannot even rotate my screen in this rom. I can't open my notification bar to enable it. Nope.
Is there something that I can do via recovery to not do the startup setting ( or w.e its called ) I really want to use this Rom.
Any1 having any possible solution? Is there a way to increase DPI via recovery? I only need the damn thing to be a bit bigger than it currently. Thats it.

Riizq said:
And the problem is that, my bottom display does not work, the hardware part and also the place where software buttons appear. ( I have been living with this issue for months, I installed pie app which is way better )
The only problem is that I cannot go any further because pressing "Next" does not work (Nor I can swipe my screen to go left.. whaaaat???). I need the next to be able to be a bit more up so that I can continue with the setup. I cannot even rotate my screen in this rom. I can't open my notification bar to enable it. Nope.
Is there something that I can do via recovery to not do the startup setting ( or w.e its called ) I really want to use this Rom.
Any1 having any possible solution? Is there a way to increase DPI via recovery? I only need the damn thing to be a bit bigger than it currently. Thats it.
Click to expand...
Click to collapse
Just make a flashable zip of build.prop(with setting of DPI changes you want to make) and flash it through recovery.
Here's a guide on how to make flashable zip: https://www.google.co.in/amp/s/www....kages-with-android-flashable-zip-creator/amp/
Guide to edit DPI using build.prop: https://androidforums.com/threads/international-guide-changing-dpi-by-editing-build-prop.849534/
Default DPI for OPO is 480,I don't know if increasing it will even work..you'll have to try,also I'm not sure if DPI will be able to fix issue in your case..
Btw,how are you planning to flash anything using twrp(swipe to flash/enable anything) if bottom part of display doesn't work?
Why not just replace the display? It doesn't take much.

Mr.Ak said:
Just make a flashable zip of build.prop(with setting of DPI changes you want to make) and flash it through recovery.
Here's a guide on how to make flashable zip: https://www.google.co.in/amp/s/www....kages-with-android-flashable-zip-creator/amp/
Guide to edit DPI using build.prop: https://androidforums.com/threads/international-guide-changing-dpi-by-editing-build-prop.849534/
Default DPI for OPO is 480,I don't know if increasing it will even work..you'll have to try,also I'm not sure if DPI will be able to fix issue in your case..
Btw,how are you planning to flash anything using twrp(swipe to flash/enable anything) if bottom part of display doesn't work?
Why not just replace the display? It doesn't take much.
Click to expand...
Click to collapse
I can flash fine, because the swipe is slightly bigger than the broken touch portion. I installed lineage os tuga 46 instead.
I think I will have to stick with this Rom.
I know the display does not take much, but I have already changed it once. I don't feel the need to replace it again, not worth it for me.
Thanks for the reply though. I will check those threads out though. Changing DPI makes the screen size large, and with the "Next" being just big enough for me to successfully press it.
If it wasn't for this pie control app. I would still be using a S3 19300 xD

Riizq said:
I can flash fine, because the swipe is slightly bigger than the broken touch portion. I installed lineage os tuga 46 instead.
I think I will have to stick with this Rom.
I know the display does not take much, but I have already changed it once. I don't feel the need to replace it again, not worth it for me.
Thanks for the reply though. I will check those threads out though. Changing DPI makes the screen size large, and with the "Next" being just big enough for me to successfully press it.
If it wasn't for this pie control app. I would still be using a S3 19300 xD
Click to expand...
Click to collapse
S3 seems to be a major downgrade...

Having the same problem with Sultan's Lineage OS 14.1. I'm thinking it's ROM related. Have you tried other ROMs? I used TugaPower for one day but I don't remember this kind of problem.

Related

[Q] Livesuit Image For Stealth Pro 9.7C

Hi. Just wondering if anyone out there would happen to have a .img image of the firmware for the trio stealth pro 9.7c. I.ve looked everywhere and can only come up with images that install through CWM recovery. My tablet will not boot into recovery as I flashed a rom that I thought would work, but now no video. Not an emergency, but if someone has it, it would be much appreciated. Thanks in advance
jgb441 said:
Hi. Just wondering if anyone out there would happen to have a .img image of the firmware for the trio stealth pro 9.7c. I.ve looked everywhere and can only come up with images that install through CWM recovery. My tablet will not boot into recovery as I flashed a rom that I thought would work, but now no video. Not an emergency, but if someone has it, it would be much appreciated. Thanks in advance
Click to expand...
Click to collapse
I used a livesuit image that was supposedly for the 9.7 on my 9.7c and everything works flawlessly. Use at your own risk. can't post links. pm me if you want it
Try this.
A member called hammerite said in this post http://forum.xda-developers.com/showthread.php?p=52298998 that the firmware for Wintouch Q91 works with this tablet. Specifically the file name is Q91A30321.img. Google it. I'm just downloading it right now and hope to fix a friend's tablet with it..
Sorry to say that file didn't work for me.
Another works, kinda
Headroom said:
Sorry to say that file didn't work for me.
Click to expand...
Click to collapse
I was grasping at straws and downloaded the Q95A306043G file, and everything works, but you need to put it to english, and the colors are off, kinda like low res kinda look, but it's a good start if someone can fix the res of the screen :fingers-crossed:
A possible work around to get the 9.7c up and running
Headroom said:
Sorry to say that file didn't work for me.
Click to expand...
Click to collapse
Yeah didn't work for me either. But I did find a bit of a work-around to have a functioning tablet again. A bit of a pain in the butt way to go about it, yet it is usable. If anyone wants to give it a try so you can at least use the thing, I'll try to explain it.....here it goes.......
Things needed:
1. LiveSuit or PhoenixSuit (I used PhoenixSuit)
2. Not necessary, but useful later, Root_with_Restore_by_Bin4ry_v32.zip
3. F918-WCDMA-20130423.1.1.11-a106-dou0308.img (copy and paste this into google, you will see a link from a site called pan.baidu.com on the first search page. Turned up about the third search down during my search. It is in Chinese, but the download link to click will have the file size, (310.16mb) click it and another box will appear, click the white box on the right, then yet another box will appear, click the blue box on the left this time, then it will give you the download.) This image is for a ly-f918 tablet, but mostly functional on 9.7c
Now we can start flashing.......
1. Using either LiveSuit or PhoenixSuit, flash the image that you downloaded to the tablet.
2. After the flash, you will notice that the screen colors are messed up and screen rotation is 180 degrees off. For the rotation, I just turned off auto rotate.
We will get to the color issue in a few....The screen will be barely legible at this point, but if you squint just right, you can read it
3. Run Bin4ry to gain root
4. For the screen color issue, I signed into google, went to the play store and downloaded and app called Screen Adjuster Free, ( yes this rom has play store built in) Set the Screen Adjuster to on (box at the top of the app) and set the system brightness to 23%. The screen should now be legible.
Things that are NOT working:
As mentioned, auto rotate is off 180 degrees
Rear camera causes the tablet to shut down
Volume up button lowers the volume, volume down and back buttons do nothing. There are volume up/down icons on the notification bar though
Color still off in the notification bar
I know it seems half-assed, but I DO at least have a working tablet again!!
I did find another rom that touch, wifi and camera do not work, but the screen colors are right:
sun4i_crane_v1.5_T05A_mc32x0_20121012-tm2.img
Maybe if someone knows how to open the images to play around with them, the display driver from the sun4i rom can be put into the F918 rom so the color is right. And possibly fix the screen rotation issue. Then the only things to worry about are the hard buttons and rear camera at that point.
Sorry if this seems lame, but like I said, My Stealth Pro 9.7c is functional again ( to some degree any way ) and if you were in the same boat as I was.....holding a tablet that didn't work at all.......it's better than nothing.
as always, try at your own risk. Let me know if anyone has trouble with this method or improvements. Thanks!
WoppTorr said:
I was grasping at straws and downloaded the Q95A306043G file, and everything works, but you need to put it to english, and the colors are off, kinda like low res kinda look, but it's a good start if someone can fix the res of the screen :fingers-crossed:
Click to expand...
Click to collapse
Just noticed you posted this as I was writing my post Does auto rotate work right? and do the hard buttons fuction correctly? and rear camera work? If it does you're a step closer than I was. maybe if someone takes THAT rom and the second one I posted and made a flashable image, we would have a completely working rom!!
Just seen this thread and posted this earlier http://forum.xda-developers.com/showthread.php?p=53242286
Sent from my Nexus 7 using XDA Free mobile app
jgb441 said:
Just noticed you posted this as I was writing my post Does auto rotate work right? and do the hard buttons fuction correctly? and rear camera work? If it does you're a step closer than I was. maybe if someone takes THAT rom and the second one I posted and made a flashable image, we would have a completely working rom!!
Click to expand...
Click to collapse
Ya it's kinda the same as the one you were using, auto rotate is off 180 degrees, but no auto rotate fixes that been, testing it for awhile and found that utube, and netflix auto turns it upside down, and I have to use that other program to get the colors right, camara worked for a bit then it stopped working, but the play store worked just fine, sorry I've been gone, just busy at work =( volume up doesn't work but volume down does
Downloaded from where.the site won't let me download it

CM13 Z5P E6853 Beta -- Updated NegaSpork

This is a no-frills thread.
Okay here it is.
cm_satsuki-Nega_Spork.zip
For dsds testing: cm_satsuki_dsds_test_boot.img Note: you will see the Sony Bootanimation instead of CM13, this is intentional. Also detection may take a minute or two. Provide clear reports.
For dsds model owners, flash rom clean, then in recovery reboot to bootloader and flash this test boot.img with fastboot
Code:
fastboot flash boot cm_satsuki_dsds_test_boot.img
fastboot reboot
NegaSpork
Working:
Sim [single]
Storage
NFC
Audio record fixed
The rest is the same.
What doesn't work:
Since the camera is still not "fixed" we will just say it doesn't work, deal with it.
Next on my todo list is fmradio
DSDS support is still being worked out by the project members. [see test boot image above]
NOTE: OpenGapps may bug out quickpanel/pulldown menu. This may be related to version used.
I experienced this with pico and nano. [see note below]
Click to expand...
Click to collapse
Thanks @KbaB.BroS for testing :good:
Everything from before works, cell, mobile data, nfc, etc.
Internet speeds are good.
It feels snappier than before, so smooth
The pulldown bar works, I can interact with the toggles without any force closes. If somebody complains about their devices, let them know to use OpenGAPPS. I use the mini version
Click to expand...
Click to collapse
Cyanogenmod Source
Thanks to/for
@CTXz Sources and convincing me to get a Z5P instead of another Sammy device.
Sony Kitakami Platform Developer Organization
@zacharias.maladroit For answering questions, many questions. :silly: [ still have more... xD ]
Those of you without a sense of humor, go away.
Okay current features i'm working on and stuff that works/doesn't work
UVC support enabled in kernel. probably need to build rom-side support still. libuvc avutils etc.
- This is for plugging in camera devices in conjuction with apps like LegitDashcam.
USB Gadget functionality as per pelya's work ,
- pelya/android-keyboard-gadget Use in conjuction with the include USB Keyboard app to utilize your phone as a keyboard/mousepad.
I am working my kernel source here toward net-huntery goodness.
The rest you tell me, and you tell me properly. Messages like
"waahhh my whatchamhoozit is all floompy"
are not acceptable.
This is not a random discussion thread either. Idle chatter belongs in general.
This is also NOT a discussion thread for Xposed,Viper, etc..
Thank you.
m
Notes and Updates
NOTE
I have been running this build for two days now and so far , meh it's alright.
Audio [mic] and Camera issues are definitely annoying.
SELinux is COMPLETELY disabled on this build. If You want security go back to stock.
SELinux enforcing is the goal though.
I strongly recommend using a "traditional" root os SuperSU over systemless-root.
Reasons:
Opengapps requires a factory-reset or fresh install to set up correctly!
Privacy Guard based root sucks. It forgets alot of permissions granted.
Use BETA-SuperSU-v2.52 , I wil attach below as it seems hard to find by conventional means.
Would have posted earlier but needed a smoke break *>cough<* :silly:
Updates and Notes
Reserved
Attached UPDATE-SuperSU-v2.46.zip for another option ,
since that worked the best for me in the past.
Thanks for the input. I get error: 7 to install the .zip file
any solution?
Rubensss said:
Thanks for the input. I get error: 7 to install the .zip file
any solution?
Click to expand...
Click to collapse
You need to use the recovery @moonbutt74 compiled from his other thread.
Sent from my Z5 Premium using XDA Labs
KbaB.BroS said:
You need to use the recovery @moonbutt74 compiled from his other thread.
Sent from my Z5 Premium using XDA Labs
Click to expand...
Click to collapse
Thanks , I have already installed.
@moonbutt74
Would be easier to keep the ROM as daily and test if it supported the dual sim version phones too
Apart from that, some of my observations during a small period of usage :
Pardon me if these are already mentioned.
Screen brightness doesn't reach full capacity
Speaker volume is low I think
For me, I felt the display had some slight glitches. Enabled GPU rendering in developer settings and felt it got better , can't guarantee on this though
Had to revert to stock based since sim functionality for me wasn't available ( I have a dual sim phone)
Ashray_Vk
Okay good deal, umm let me try compiling a seperate kernel package.
Yep brightness is currently HORRIBLE
I didn't notice any glitches display-wise, do you actually mean lag in some screen transitions?
I only tested with radioball and raging thunder.
The build i just tested out had full WOW, HOW THE HELL DO I TURN THIS DOWN BRIGHTNESS. :silly:
So either atm i get crappy brightness as max level which is like 75% of stock.
Or i get the nice stock brightness but the slider breaks/doesn't work.
The speaker volume is limited to where it actually should be. Use a mediaplayer that has an option for software decoding, that is a 100% [double] boost. It's not the idea to bomb out the speakers by default, each user can find their own tweak.
m
On the "daily build" thing, my upload time is horrible, so i will not be pushing out excessive/pointless builds. when i have something else fixed, then i will upload another build. Currently i'm boxing with the brightness issue and getting the mic working for audio recording.
moonbutt74 said:
Ashray_Vk
Okay good deal, umm let me try compiling a seperate kernel package.
Yep brightness is currently HORRIBLE
I didn't notice any glitches display-wise, do you actually mean lag in some screen transitions?
I only tested with radioball and raging thunder.
The build i just tested out had full WOW, HOW THE HELL DO I TURN THIS DOWN BRIGHTNESS. :silly:
So either atm i get crappy brightness as max level which is like 75% of stock.
Or i get the nice stock brightness but the slider breaks/doesn't work.
The speaker volume is limited to where it actually should be. Use a mediaplayer that has an option for software decoding, that is a 100% [double] boost. It's not the idea to bomb out the speakers by default, each user can find their own tweak.
m
On the "daily build" thing, my upload time is horrible, so i will not be pushing out excessive/pointless builds. when i have something else fixed, then i will upload another build. Currently i'm boxing with the brightness issue and getting the mic working for audio recording.
Click to expand...
Click to collapse
By screen glitches, I meant that I saw a few glitches when I scrolled down menus ( like even settings app).
Might be just my sleepy eyes too, lol. And in the beginning, everything was feeling laggy, till I enabled those GPU options in the developer settings and turned the screen off and turned it back on.
Don't rely on this data though, I hope someone else verifies this thing before you take it up as an issue .
-Ash
Ashray_Vk said:
By screen glitches, I meant that I saw a few glitches when I scrolled down menus ( like even settings app).
Might be just my sleepy eyes too, lol. And in the beginning, everything was feeling laggy, till I enabled those GPU options in the developer settings and turned the screen off and turned it back on.
Don't rely on this data though, I hope someone else verifies this thing before you take it up as an issue .
-Ash
Click to expand...
Click to collapse
No problem I'm just looking for clarification, are you talking about lag or screen tearing?
moonbutt74 said:
No problem I'm just looking for clarification, are you talking about lag or screen tearing?
Click to expand...
Click to collapse
There was lag in the beginning, no doubt. Lag was there since the boot animation itself.
Yes! Screen tearing is the term i was searching for. I felt like I saw minor issues of screen tearing along with the lag. ( especially when I scrolled down the settings )
I'm so sorry if I am not able to make things clear.
Nice. My question is does it work well with xposed? Other rom gives me random soft reboot randomly
Sent from my E6853 using XDA-Developers mobile app
Killastyle said:
Nice. My question is does it work well with xposed? Other rom gives me random soft reboot randomly
Sent from my E6853 using XDA-Developers mobile app
Click to expand...
Click to collapse
K,
right now we are working on an Alpha build, self evident in thread title. Xposed being superfluous/unecessary is not being discussed in this thread. Of course later on in the release/beta level thread it will most likely be covered.
@KbaB.BroS
On the good side got brightness and auto brightness sorted.
@Ashray_Vk , give me a bit on the dsds kernel, from what I'm understanding SS an DS were supposed to have been combined, so I am running a fresh build after resync, which on my comp will take a day :silly: adn probably not as long as the actual upload
:laugh:
m
moonbutt74 said:
K,
right now we are working on an Alpha build, self evident in thread title. Xposed being superfluous/unecessary is not being discussed in this thread. Of course later on in the release/beta level thread it will most likely be covered.
@KbaB.BroS
On the good side got brightness and auto brightness sorted.
@Ashray_Vk , give me a bit on the dsds kernel, from what I'm understanding SS an DS were supposed to have been combined, so I am running a fresh build after resync, which on my comp will take a day :silly: adn probably not as long as the actual upload
:laugh:
m
Click to expand...
Click to collapse
Normally, if I'd flash a stock based ROM which was meant for single sim, one sim would work in the dual sim models but the memory card would be not detected . sadly, that wasn't the case with cm though. Not even a single sim gets detected.
Ashray_Vk said:
Normally, if I'd flash a stock based ROM which was meant for single sim, one sim would work in the dual sim models but the memory card would be not detected . sadly, that wasn't the case with cm though. Not even a single sim gets detected.
Click to expand...
Click to collapse
you tried enabling only single SIM mode in Sony's (or other) "Stock" ROM and then flashing this ROM ?
Then at least one SIM might work - unless of course the Z5 devices handle things entirely differently
zacharias.maladroit said:
you tried enabling only single SIM mode in Sony's (or other) "Stock" ROM and then flashing this ROM ?
Then at least one SIM might work - unless of course the Z5 devices handle things entirely differently
Click to expand...
Click to collapse
Um, actually, was running rom aur and then had disabled one sim ( just because i didnt want to use that sim) and then had flashed this.
Unfortunately, not even a single sim worked in this.
Killastyle said:
Nice. My question is does it work well with xposed? Other rom gives me random soft reboot randomly
Sent from my E6853 using XDA-Developers mobile app
Click to expand...
Click to collapse
No problem with XPosed for some time here
Updated Build
CM13 Z5P E6853 Somehwere in Alpha -- Updated DragonLady
see OP , OH! and READ IT. grrrrrrr
Please verify communications are functioning, sim detection, in-call mic working etc.
Is your model SS or DS? Please state model number.
Brightnes and auto brightness should be fixed.
External storage fixed
Re-introduced kcal support in kernel
Included system apps [free, and free versions] - as we are testing , some creature comforts.
Adaway.apk
HKB.apk <--- hacker's keyboard
HKNDCTRU.apk <--- hacker's keyboard cyrillic/russian support
KernelAuditor.apk
NetworkDiscovery.apk <--- fairly useful network discovery app, find it on fdroid
NovaLauncher.apk
OpenCamera.apk
PicuriRam.apk
Quickpic.apk
Rebooter.apk
Superuser.apk <--- enable developer options and root access via that way first, then run supersu and update.
Terminal.apk < jackpal terminal
TotalCommander.apk
USB-Keyboard.apk
USBKB.apk < this one and the one above are the same app, i dun goofed.
Wifitoggle.apk
i am working a vanilla cm13 as well as my own custom build in the same turn, the custom utility in sbin is ccrypt, if you want to know how to use it, pm me and i'll give you a break down. do not use it to encrypt a block device !! single files only, and do not use a generated key, use a memorizable alpha-numeric password, else leave it alone.
m
@zacharias.maladroit WHAT HAPPENED TO PERRY !?!?!?!? :crying:
@moonbutt74
I'm sort of wiping the slate clean in several areas of my life - and that (unfortunately) was part of it :angel:

Android Oreo Developer Preview Image Released!

This preview of the Oreo build is updated with the March 2018 security patches. It is Android Oreo, version 8.1. If you want to use this, keep in mind that this is a development preview! It is not the final release. There are also a few things to note about using it.
It requires you to be bootloader unlocked (unlocking wipes your phone)
This update will wipe your phone even if you're already unlocked
You will not get any OTAs while on this build
VoLTE and WiFi Calling might not work
No CTS, so Android Pay/Pokemon Go may not work
May be some undocumented bugs
If you're fine with all of that, then the download link can be found on Razer's developer page about the update.
If you want to go back to the stock Nougat images, just follow the instructions here.
If anyone does this can they show us some videos
iStasis said:
If anyone does this can they show us some videos
Click to expand...
Click to collapse
Look up a video of Oreo on a Pixel. It looks exactly the same.
No default white theme like normal Oreo same default theme as nougat.
Screen now has a colour option which can be set to show more vibrant colours.
Double tap to sleep (only on lockscreen)
Speakers seem louder than before.
And all the normal Oreo stuff
Also Pokémon go does work.
Roxas598 said:
No default white theme like normal Oreo same default theme as nougat.
Screen now has a colour option which can be set to show more vibrant colours.
Double tap to sleep (only on lockscreen)
Speakers seem louder than before.
And all the normal Oreo stuff
Also Pokémon go does work.
Click to expand...
Click to collapse
Color options and more power for the speakers are both great news. Much excited.
I'm tinkering with GSIs and I've realised you can go into Download Mode by tapping the Power button several times as soon as the Razer logo pops up (before the orange 'tampered' message appears).
In case that helps someone ^
linuxct said:
I'm tinkering with GSIs and I've realised you can go into Download Mode by tapping the Power button several times as soon as the Razer logo pops up (before the orange 'tampered' message appears).
In case that helps someone ^
Click to expand...
Click to collapse
I wonder if there's a way of doing that with maybe the volume buttons to go directly into recovery as well ?
Roxas598 said:
No default white theme like normal Oreo same default theme as nougat.
Screen now has a colour option which can be set to show more vibrant colours.
Double tap to sleep (only on lockscreen)
Speakers seem louder than before.
And all the normal Oreo stuff
Also Pokémon go does work.
Click to expand...
Click to collapse
How would you rate the new colors, I've always felt the display was a tiny bit washed out
need help
im trying to update my phone, but when i run the flash_all command, its says waiting for device and stays there for ever, now it has more than 30 minutes with no sign of working
Horuhe93 said:
im trying to update my phone, but when i run the flash_all command, its says waiting for device and stays there for ever, now it has more than 30 minutes with no sign of working
Click to expand...
Click to collapse
Install Android USB driver
hello5629 said:
Install Android USB driver
Click to expand...
Click to collapse
ADB reboot bootloader then the flash all bat
i tested oreo and it looks very good,but until official release i reflashed the noughat stock img and now my sim wont recognise any help
please
parky169 said:
i tested oreo and it looks very good,but until official release i reflashed the noughat stock img and now my sim wont recognise any help
please
Click to expand...
Click to collapse
It did the same thing to me when I flashed stock nougat to fix boot loop. Remove and reinstall the Sim card. That worked for me.
Anyone having Bluetooth mic issues on this preview?
Just got a new BT headset with a built in mic and it ain't working. Just thought I'd check in here before returning it.
I went back to Nougat but did anyone else notice the screen colours go between vibrant and normal all the time? noticed it on the lockscreen, Keyboard and quick toggles but it only seemed to happen with colourful stuff. Default Razer wallpaper, Coloured keyboard and theme applied etc
Yes @Roxas598 I did notice the colors change from vibrant to normal a lot. And I've been watching Netflix on it lately as well and have been watching the second season of a series of unfortunate events and the whole show has been looking darker than it should, making it hard to watch even with brightness all the way up.
AwesomeFabe said:
Yes @Roxas598 I did notice the colors change from vibrant to normal a lot. And I've been watching Netflix on it lately as well and have been watching the second season of a series of unfortunate events and the whole show has been looking darker than it should, making it hard to watch even with brightness all the way up.
Click to expand...
Click to collapse
I already reported the issue but wanted to make sure it wasn't just me. Thanks!
My Fitbit is not being recognised at all, and my bluetooth mic on my new headphones doesn't work. So it looks like there are some issues with Bluetooth which I'll revert to stock to resolve. Not bad so far, but obviously being close to stock means it doesn't feel much different to 7.1, certainly not enough that you get that excited buzz we once got back when Android revisions were massively different.
Literally got everything working
joemossjr said:
Literally got everything working
Click to expand...
Click to collapse
How did you do this? I'd like to know since I'd like to use Netflix and Google Pay.

[sGSI][Testing]Android 10.0 AOSP[24/10/2019]

Hi Guys,
Some of you may remember me if you had a Galaxy S9 or Note 10... I rooted my Note 10+ 5G (N976B) Last night and decided to try and have a stab at getting stock android on there by means of project treble. This is a Semi Generic System Image - meaning it's been/being enhanced specifically for our note devices and less focused towards being cross compatible with other devices.
If you have already tested the existing treble roms you'll know that the back lighting doesn't work and you can't adjust brightness. I've had a play around and I've got a working Android 10 AOSP build with fully working backlighting. I thought I'd share as I'd seen a few people who said they can't get GSI's working.
Download System Image
Gapps are included, the image is not rooted. You can flash Magisk yourself.
How to flash:
Make sure you're on a stock based rom (and rooted/twrped) Dr Ketan posted a good guide for this.
Download the System Image above
Reboot to TWRP
Select Wipe
Slide the bar across the bottom of the screen
Go back to the main TWRP menu and select install
Press "Install Image" at the bottom right.
Select the system image you downloaded and swipe to flash.
Once the GSI boots perform another reboot - for some reason the navbar doesn't start up on first boot.
What's working and not working:
Obviously you lose S-Pen functionality, but can still use it as a stylus. You also lose the ability to use your telephoto and telescopic lenses.
UltraSonic Fingerprint isn't working at the moment, but I'm looking into fixing that.
How can you help me?
Let me know how it's working for the different device models. People on other versions please can you let me know your device vendor fingerprint. (to do this On your device, in adb or Termux app use this command: getprop ro.vendor.build.fingerprint)
Credits:
phhusson - for all the project treble work, this is all thanks to him.
Please please support N976n. ???
xshaowenruix said:
Please please support N976n.
Click to expand...
Click to collapse
It should work, it's semi generic. Give it a try and let me know if it works.
If it doesn't I'll need your device fingerprint.
Good work!
Nice ... you stared to work whit the N10+ , still remember havoc in my N9 was a great time , keep goin Fox
@CodeFox. Thank you so much for your work with this! I booted successfully into Android 10 which is awesome. Installing Magisk was successful as well. Do you have any plans to add mods to this?
Welcome aboard
carandcar said:
@CodeFox. Thank you so much for your work with this! I booted successfully into Android 10 which is awesome. Installing Magisk was successful as well. Do you have any plans to add mods to this?
Click to expand...
Click to collapse
Glad to hear it worked for you - can I ask what specific device you're using?
No mods to this really, but right now I'm compiling a AEX pie based sGSI which I'm hoping should have some more improved functionality and potentially the fingerprint sensor working. There's no reason to mod bog standard Android 10, may aswell just use custom roms.
CodeFox said:
Glad to hear it worked for you - can I ask what specific device you're using?
No mods to this really, but right now I'm compiling a AEX pie based sGSI which I'm hoping should have some more improved functionality and potentially the fingerprint sensor working. There's no reason to mod bog standard Android 10, may aswell just use custom roms.
Click to expand...
Click to collapse
I have N975f. I understand what you mean about keeping it pure. I just like to be able to change the look up. ? Thank you again for bringing this to us.
I managed to get fingerprint working
I seem to have gotten it working by doing a fresh reset, flashing this version of gapps (https://forum.xda-developers.com/android/software/arm64-bitgapps-q-10-0-0-t3968500), wiped cache/dalvik then rebooted. i dont know if it made a difference or not but i also held my thumb on the sensor for extra long during the initial set up. Did it on N975F
Jamjarr said:
I seem to have gotten it working by doing a fresh reset, flashing this version of gapps (https://forum.xda-developers.com/android/software/arm64-bitgapps-q-10-0-0-t3968500), wiped cache/dalvik then rebooted. i dont know if it made a difference or not but i also held my thumb on the sensor for extra long during the initial set up. Did it on N975F
Click to expand...
Click to collapse
Hmm, Interesting. I will look into it. Thank you.
Thanks (and a quick question)
Thanks for the rom! This works for me on an N975F, including the fingerprint sensor. The only slight nit I have with it is that I can't figure out how to get rid of the cursor showing up on the screen when I use the stylus. Is there any chance there's a way to hide the cursor, or if it can be added? I don't use any other external input devices ever, so I'd be fully satisfied with a way to just disable the cursor globally on my device.
saghm said:
Thanks for the rom! This works for me on an N975F, including the fingerprint sensor. The only slight nit I have with it is that I can't figure out how to get rid of the cursor showing up on the screen when I use the stylus. Is there any chance there's a way to hide the cursor, or if it can be added? I don't use any other external input devices ever, so I'd be fully satisfied with a way to just disable the cursor globally on my device.
Click to expand...
Click to collapse
Was there any trick to getting the fingerprint to work?? I've had no joy with it. As soon as I try to register my fingerprint it says there was an enrolment error.
Would this gsi theoretically also fix the s10's brightness issue too?
CodeFox said:
Was there any trick to getting the fingerprint to work?? I've had no joy with it. As soon as I try to register my fingerprint it says there was an enrolment error.
Click to expand...
Click to collapse
It did this to me too when I was first setting up the phone, but after it was all set up, I went into the settings to try again, and it worked that time. It didn't show the fingerprint logo during this setup (and it still doesn't on the lock screen), but after a couple tries I was able to estimate correctly where the sensor was. Interestingly, the fingerprint logo does come up in the password manager app I use when I go to unlock it.
Not sure if there are logs that would help or if recording my screen while adding a new fingerprint would be informative, but I'd be happy to do either if that helps you debug in some way.
saghm said:
Thanks for the rom! This works for me on an N975F, including the fingerprint sensor. The only slight nit I have with it is that I can't figure out how to get rid of the cursor showing up on the screen when I use the stylus. Is there any chance there's a way to hide the cursor, or if it can be added? I don't use any other external input devices ever, so I'd be fully satisfied with a way to just disable the cursor globally on my device.
Click to expand...
Click to collapse
DBDPCG said:
Would this gsi theoretically also fix the s10's brightness issue too?
Click to expand...
Click to collapse
What's the issue with the S10? The backlight doesn't work?
CodeFox said:
What's the issue with the S10? The backlight doesn't work?
Click to expand...
Click to collapse
As I've heard, haven't tried it yet though
DBDPCG said:
As I've heard, haven't tried it yet though
Click to expand...
Click to collapse
For what it's worth, all the other GSI's I've tried for the Note 10+ weren't able to adjust the backlight; this is the first one where it just worked. I don't have an S10 to try this out on though, so I have no idea how this ROM would run on it.
LTE working despite phone claiming 3G
One thing I've noticed with this ROM is that the phone claims that it's always only getting 3G rather than LTE and has no bars; however, from doing a speed test on data (with wifi turned off, of course), I got around 8.5 Mbps down, which from a quick Google seems to be will beyond 3G range and into the range that LTE would give. If anyone else thinks they are having issues with getting LTE, I suggest doing a speed test, since you might actually be getting it despite what the phone reports.
saghm said:
One thing I've noticed with this ROM is that the phone claims that it's always only getting 3G rather than LTE and has no bars; however, from doing a speed test on data (with wifi turned off, of course), I got around 8.5 Mbps down, which from a quick Google seems to be will beyond 3G range and into the range that LTE would give. If anyone else thinks they are having issues with getting LTE, I suggest doing a speed test, since you might actually be getting it despite what the phone reports.
Click to expand...
Click to collapse
Go into your network settings and change the default connection from 3g to LTE/4G/3G.
For some reason it seems to default to 3g preferred.

[HELP] Screen size,notch,rounded corners change

Hi people, am currently waiting for bootloader unlock, am trying to sort things out and see how am gonna use my new rooted phone Xiaomi Redmi Note 9 Pro (got it as gift), well phone is great, but am coming from old era where rounded corners and notch was not a thing, i still prefeer screens with rectangle shape, and am willing to sacriface lower portion of screen up to ending of rounded corner and same above till the camera module, so i can have nice rectangular screen
Now my question is how to?
How to change screen size? (how to measure where to start and end)
If by software rounded corners still exist how to remove them?
Am planing to flash xiaomi.eu rom (am considering Ressurection Remix) and magisk root.
Thank you great people and community.
It's simple, and can be done without rooting, connect with ADB.
So your device has 1080x2400 resolution, you'll have to lower numbers from the height (2400) in order to get a rectangular display.
Play with numbers till you get it right, commands to use:
adb shell
wm size 1080x2200
Mohamedkam000 said:
It's simple, and can be done without rooting, connect with ADB.
So your device has 1080x2400 resolution, you'll have to lower numbers from the height (2400) in order to get a rectangular display.
Play with numbers till you get it right, commands to use:
adb shell
wm size 1080x2200
Click to expand...
Click to collapse
Thank you very much, i will check it out once i got bootloader unlock since am waiting 168h on Xiaomi devices, i will not fiddle with anything so i dont mess something up
And about software rounding, since when in settings i choose option to hide notch and move status bar down, it hides a notch and its completley disabled part of screen, but it still gets a rounded corners by software, i will try this with option dont hide anything maybe then under hardware display is rectangular, but you never know i will let you know , but if it is software how can i find it on my device, since i googled and found something for Pixel devices, and its all diffrent, thank you alot.
And what about DPI , or resolution after that change, should i keep everything as it is
essen33 said:
Thank you very much, i will check it out once i got bootloader unlock since am waiting 168h on Xiaomi devices, i will not fiddle with anything so i dont mess something up
And about software rounding, since when in settings i choose option to hide notch and move status bar down, it hides a notch and its completley disabled part of screen, but it still gets a rounded corners by software, i will try this with option dont hide anything maybe then under hardware display is rectangular, but you never know i will let you know , but if it is software how can i find it on my device, since i googled and found something for Pixel devices, and its all diffrent, thank you alot.
And what about DPI , or resolution after that change, should i keep everything as it is
Click to expand...
Click to collapse
Hiding notch ain't that effective, and you lose some of your screen doing so.
Your screen is a rounded AMOLED, that's hardware, it also has software roundness in order to be compatible with your screen. It's not that hard to disable roundness, for hardware, you can overcome it by "wm size", and you can change DPI by: "wm density xxx" to your desired value.
The software overcoming needs APK editing, so you need a PC/Laptop. You need to edit framework-res.apk (and maybe SystemUI.apk). There's an app that allows you to edit framework-res.apk values directly, you may want to check it:
Privset.
Mohamedkam000 said:
Hiding notch ain't that effective, and you lose some of your screen doing so.
Your screen is a rounded AMOLED, that's hardware, it also has software roundness in order to be compatible with your screen. It's not that hard to disable roundness, for hardware, you can overcome it by "wm size", and you can change DPI by: "wm density xxx" to your desired value.
The software overcoming needs APK editing, so you need a PC/Laptop. You need to edit framework-res.apk (and maybe SystemUI.apk). There's an app that allows you to edit framework-res.apk values directly, you may want to check it:
Privset.
Click to expand...
Click to collapse
Thank you, its actually LCD, on Redmi note 9 pro, Thank you for commands above, when i screenshot something it appears rectangle, so in theory it should work and rounded edges should not be there
Well for that APK stuff, does installing custom ROM help in that? I was thinking about RR rom,
Also, i dont mind losing screen size, and for me hiding notch is a must doing it this way, personally i hate it, i hate rounded edges, i just hate it my heart hurts when i see it, i got this phone as gift so i need to appreciate it i cant sell/replace it that way its kinda disrespectful
essen33 said:
Thank you, its actually LCD, on Redmi note 9 pro, Thank you for commands above, when i screenshot something it appears rectangle, so in theory it should work and rounded edges should not be there
Well for that APK stuff, does installing custom ROM help in that? I was thinking about RR rom,
Also, i dont mind losing screen size, and for me hiding notch is a must doing it this way, personally i hate it, i hate rounded edges, i just hate it my heart hurts when i see it, i got this phone as gift so i need to appreciate it i cant sell/replace it that way its kinda disrespectful
Click to expand...
Click to collapse
Oh sorry, I assumed it being a budget killer to offer an AMOLED display similar to RN10.
Well .. having LCD makes it a bit different, as the parts you cut off from your display will keep lightening up, that's how LCD displays work.
Honestly, you'll hate it more, it'll be like watching a long video on YouTube without fullscreen mode.
Strange tradition you've got right there, here, we're more understanding, if someone gifted you a phone, it won't matter if you sold it or replaced it, what matters is the feelings you've grown out of his gift.
About the APK stuff, it can be done on any ROM, but it's more stable on AOSP-based ROMs like RR, Havoc, PE, ...
An easy way to achieve your goal would be to use adb wm size, and reduce height. (There's another thing to do, adjust the new touch positions; cause your phone will keep using old positions, so if you're using gestures, it won't work that simple, till you recalculate it. (Easy to solve).
Mohamedkam000 said:
Oh sorry, I assumed it being a budget killer to offer an AMOLED display similar to RN10.
Well .. having LCD makes it a bit different, as the parts you cut off from your display will keep lightening up, that's how LCD displays work.
Honestly, you'll hate it more, it'll be like watching a long video on YouTube without fullscreen mode.
Strange tradition you've got right there, here, we're more understanding, if someone gifted you a phone, it won't matter if you sold it or replaced it, what matters is the feelings you've grown out of his gift.
About the APK stuff, it can be done on any ROM, but it's more stable on AOSP-based ROMs like RR, Havoc, PE, ...
An easy way to achieve your goal would be to use adb wm size, and reduce height. (There's another thing to do, adjust the new touch positions; cause your phone will keep using old positions, so if you're using gestures, it won't work that simple, till you recalculate it. (Easy to solve).
Click to expand...
Click to collapse
Well its a family gift so if i sell it it would be toxic "you didnt like my gift" , iam about to flash RR, so i will look into that, i dont mind having background light on unused part of screen, well how if you dont mind, your tips on recalculating touch positions, i found some googling around, what you recommend, thanks alot
essen33 said:
Well its a family gift so if i sell it it would be toxic "you didnt like my gift" , iam about to flash RR, so i will look into that, i dont mind having background light on unused part of screen, well how if you dont mind, your tips on recalculating touch positions, i found some googling around, what you recommend, thanks alot
Click to expand...
Click to collapse
Okay, so a year ago, I had Galaxy S7 that got some water issues, so the bottom part of screen wasn't working, and I was using on-screen navigation bar, so I used ADB wm commands to make the phone usable until it dries up.
What I did was, reducing screen height up to the usable part. Then, I used: adb wm overscan command.
This command tells the system where is the screen end, whether at top, bottom, right, or left. So if your bottom screen is reduced by 2 cm, you'll have to tell your system about that, so that it don't assume it's still at the actual hardware values.
The command uses numbered values separated by commas like this (original values):
wm overscan 0,0,0,0
The numbers are organised LEFT,TOP,RIGHT,BOTTOM
You can use minus too, I honestly don't remember which numbers were suitable for my case, you'll have to check it on your own (won't take over 10 minutes). Only change TOP & BOTTOM values.
Who knows, maybe you won't need to do this anymore, perhaps Android 11's AI does that automatically whenever changing screen resolution.
Mohamedkam000 said:
Okay, so a year ago, I had Galaxy S7 that got some water issues, so the bottom part of screen wasn't working, and I was using on-screen navigation bar, so I used ADB wm commands to make the phone usable until it dries up.
What I did was, reducing screen height up to the usable part. Then, I used: adb wm overscan command.
This command tells the system where is the screen end, whether at top, bottom, right, or left. So if your bottom screen is reduced by 2 cm, you'll have to tell your system about that, so that it don't assume it's still at the actual hardware values.
The command uses numbered values separated by commas like this (original values):
wm overscan 0,0,0,0
The numbers are organised LEFT,TOP,RIGHT,BOTTOM
You can use minus too, I honestly don't remember which numbers were suitable for my case, you'll have to check it on your own (won't take over 10 minutes). Only change TOP & BOTTOM values.
Who knows, maybe you won't need to do this anymore, perhaps Android 11's AI does that automatically whenever changing screen resolution.
Click to expand...
Click to collapse
Thanks alot i managed to set it up, very helpfull
essen33 said:
Thanks alot i managed to set it up, very helpfull
Click to expand...
Click to collapse
Glad I could help.
Hello, I have a problem and a question with him. When I install a custom rom and lower the resolution, despite using the notch bar killer, a notch remains that got bigger and I can't delete them, also when I put the dark mode it becomes white

Categories

Resources