Related
Since I am only new to the forums I can't post in the Rom dev area.
I just installed Rom from http://forum.xda-developers.com/showthread.php?t=2481828
I was wondering if anyone knows how to remove the mobile signal icon from the status bar. It's great to have the stock Samsung Android 4.1.2 on my Galaxy Tab 7.7 wifi model, even if it's not perfect.
I have root access, so if it's just a matter of removing an app, i can uninstall it.
Peter
I'm pretty sure the process will involve de/re-compiling etc. Maybe SystemUI.apk. If you have data options in your device settings menu, settings.apk might need to be looked at as well.
Edit: I will take a look at a few things when I return home (away working).
Priority (apart from family) is a P6810 SkyHigh JB kernel, then followed by possible stock ROM mods, tweaks, or maybe a even a SkyHigh custom ROM - just for fun. Maybe not too, supporting a release takes precious time and testing, which I have very little ATM. Kernel release and support will be enough.
But last priority will be looking at (trying) removing any P6800 specific parts from the firmware, providing they don't impact the ROM or 'negative' effect on performance.
Please post any other firmware observations that shouldn't be on our Wi-Fi model.
Thanks.
UITA
Sent from my GT-I9500 using XDA Premium 4 mobile app
Remove: tw_stat_sys_signal_null* from SystemUI/res/drawable-mdpi
bodivas said:
Remove: tw_stat_sys_signal_null* from SystemUI/res/drawable-mdpi
Click to expand...
Click to collapse
Excellent, saves me the time
But I think that's just cosmetic. We need to look deeper yet.
Sent from my GT-I9500 using XDA Premium 4 mobile app
UpInTheAir said:
Excellent, saves me the time
But I think that's just cosmetic. We need to look deeper yet.
Sent from my GT-I9500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The following APK can be safely removed : /preload/symlink/system/app/secphone.apk
It will also stop the tablet to try to access any mobile signal... Which cannot be achieved anyway as it is only a wifi version... Thus draining the battery for no reason..
obeguin said:
The following APK can be safely removed : /preload/symlink/system/app/secphone.apk
It will also stop the tablet to try to access any mobile signal... Which cannot be achieved anyway as it is only a wifi version... Thus draining the battery for no reason..
Click to expand...
Click to collapse
Thought there may be more to remove/edit, RIL etc, but it could just that simple. Thanks.
Sent from my GT-I9500 using XDA Premium 4 mobile app
obeguin said:
The following APK can be safely removed : /preload/symlink/system/app/secphone.apk
It will also stop the tablet to try to access any mobile signal... Which cannot be achieved anyway as it is only a wifi version... Thus draining the battery for no reason..
Click to expand...
Click to collapse
can I uninstalled with titanium? I cant see it in the list :S
can we remove " Sim toolkit" too?
Morloc2 said:
can I uninstalled with titanium? I cant see it in the list :S
can we remove " Sim toolkit" too?
Click to expand...
Click to collapse
I just installed the new Multi Window version of the Rom, which is great. However, I was wondering how you enable the Split screen mode. The apps all launch in resizable Windows, so you can have many running, I click on the pin button (which somewhere I read might switch modes) but it doesn't seem to work.
Elsewhere, I read that you need to change the DPI of the tablet in the build.prop file? Mine is currently on 160, I think some said 176 might be required to activate the split screen?
Anyone know the answer to this?
-error-
could it work?
sd3993 said:
Sorry about the late reply. Computer HD crashed :/
Anyways here are the steps.
1)Decompile SystemUI.apk
2)Go to com/android/systemui/statusbar/policy/StatusBarPolicy.smali <---Make a backup of this file before proceeding.
3)Find 'phone_signal_2' and delete the invoke-virtual 'setIcon()' method after it. (The invoke-virtual setIcon() method MAY NOT be immediately after 'phone_signal_2'. There maybe other lines in between. DO NOT delete those.)
4)Repeat Step 3 for EVERY instance of 'phone_signal_2'.
5)Recompile SystemUI.apk(don't forget to delete classes.dex from the 'keep' folder )
6)Push it back to your phone and change permissions to rw-rw-r
7)Reboot & Enjoy the extra status bar space
Click to expand...
Click to collapse
Morloc2 said:
could it work?
Click to expand...
Click to collapse
yes it works
EDIT:-Okay i absolutely did not notice the 4.1.2 :/
This mod was for gingerbread only. The files are very different in JB.
Process should be more or less the same but different files.
nice, so..what I need to try it?
can I connec the tab and modify this file?
ty
p3dboard said:
I just installed the new Multi Window version of the Rom, which is great. However, I was wondering how you enable the Split screen mode. The apps all launch in resizable Windows, so you can have many running, I click on the pin button (which somewhere I read might switch modes) but it doesn't seem to work.
Elsewhere, I read that you need to change the DPI of the tablet in the build.prop file? Mine is currently on 160, I think some said 176 might be required to activate the split screen?
Anyone know the answer to this?
Click to expand...
Click to collapse
I have played about, setting the dpi to 176 in build.prop does change it from windowed mode to split screen. However you need to change the default launcher from touchwiz before changing it from 160 to 176, as touchwiz is configured to only work at 160dpi, it crashes on any other dpi. The Samsung keyboard also has the same issue, so switch to google keyboard or SwiftKey before rebooting to bring the dpi into effect.
Also samsung calculator, camera and memo don't work at 176dpi. But if you get the photosphere camera from Android 4.3 from the s4 google edition it works.
I have seen that some have modified touchwiz to work at different dpi settings, so there might be another way to fix the Samsung apps.
If you change the dpi to 184/186, you get phablet mode for notifications, which looks more like the note 8 layout.
I think at different dpi the multi window changes mode. At 160 its like the note 10.1, with resizable Windows. At 176, its more like the note 8.
On a side note 176 dpi also fixed a bug in the aview app in the play store which would crash in portrait mode when launching videos from the Abc iview service.
how do you change this settings?
Morloc2 said:
how do you change this settings?
Click to expand...
Click to collapse
I changed the dpi by using es explorer from the play store, you can mount /system as read/write and then edit /system/build.prop
You set the lcd density to 176. Save and reboot. But make sure you change your launcher first, otherwise you will have touchwiz crashing. Another app that crashes when not running at 160 dpi is the Samsung task manager. But at 176 dpi, the split screen and windowed modes both work, the little pin in the left corner switches between modes
My next question if anyone knows. The v4 multiwindow systemui.apk, is different from the one in the p6810 rom, that is the one from the p6800 multiwindow post, if i replace my current systemui.apk, will this fix my not having split screen at 160 dpi?
p3dboard said:
I changed the dpi by using es explorer from the play store, you can mount /system as read/write and then edit /system/build.prop
You set the lcd density to 176. Save and reboot. But make sure you change your launcher first, otherwise you will have touchwiz crashing. Another app that crashes when not running at 160 dpi is the Samsung task manager. But at 176 dpi, the split screen and windowed modes both work, the little pin in the left corner switches between modes
My next question if anyone knows. The v4 multiwindow systemui.apk, is different from the one in the p6810 rom, that is the one from the p6800 multiwindow post, if i replace my current systemui.apk, will this fix my not having split screen at 160 dpi?
Click to expand...
Click to collapse
I tried replacing systemui.apk, and this copy crashed, so I went back to the copy that came with the new Rom (the working copy is 4 mb, where as the one in v4 was about 2.5mb).
I tried 156dpi, as a test, and Touch Wiz and Samsung apps work fine at this DPI, they don't crash, but then the split screen bar doesn't show, but the apps launched in windows do seem to snap to the width of the screen at 156dpi. So I think the Touchwiz / Samsung apps have some sort of upper DPI limit coded into them. So, if anyone knows how to increase this to 176dpi, this would make the Rom perfect.
Samsung APK's that would need fixing from what I can see are
- Touchwiz
- Task Manager
- Camera
- Calculator
- Memo
Great news. I tried the modified systemui.apk and after it initially crashed after replacing the 4mb version, I decided to reboot anyway to see if it worked. It does, but better than that it works at 160dpi. Split screen works!
Also you need the double lcd dpi setting in build.prop for the split screen bar to work properly.
So don't worry about the initial crash, swap over. You also get the multi screen layout tool on the system bar. If you get the version from the p6810 stock android 4.1.2 thread it also eliminates the no mobile signal icon. Finally its almost perfect !
The latest Multi-Window ROM is really good.
I did some basic tests and it seems quite good.
Cannot believe Samsung aren't putting together a Jelly Bean ROM for P6810...
Anyway flashed this ROM and tested a few things.
Globally it seems very good.
I have spotted a few cosmetic issues but I guess this is because this ROM was designed for the P6800:
- Mobile Data Icon still there,
- About device/Status, crashes.
One major problem I have though is the fact I cannot mount my 64GB Cruzer Fit (FAT32) with this ROM anymore.
This is quite a show stopper and was wondering if anything could be done about this.
I did some more testing. The modified systemui.apk and the samsung multiwindow can sometimes have a double split screen bar. Both work, but are seperate to each other so when you move one the app snaps to it, but you move the other and it snaps to it.
Not sure the exact trigger, but if you disable multiwindow in settings, you can still launch multiwindow apps using the system bar quick launcher at the bottom of the screen that is in the new modified systemui.apk.
If you go back to the original systemui.apk after using the new one, split screen actually works at 160 dpi. So i am guessing it makes some files that fix the issue at 160 dpi. The only slight issue is the split screen bar is slightly small at 160dpi.
Another bug with the modified systemui.apk is if you hold down the home button the google now quick launch ring appears in the wrong location, off to the side. The original systemui.apk doesn't have this issue. Anyway, just feedback incase someone can fix these bugs.
Feedback on the great ROM
I am now using this ROM on my GT-P6810 and I have to say it is really good with the Kernel from UpInTheAir.
I can now mount an external 64GB CruzerFit USB key. I am getting a strange white square in the menu bar though.
I cannot copy to the key but can read from it.
The work that has been done so far is great though. Thanks to both. How hard will it be to remove any (if possible) non GT-6800 menus, I don't know but it is very usable. I have no idea why Samsung haven't done such thing really. This tab still rocks!
There is one thing I would really love though and that will be to be able to write to external key. When I try do do so the key is unmounted automatically. The OS start writing to it the it is being dismounted...
Hey guys,
I'm using an LCD density of 360 on my Nexus 5 by ending the build.prop, this feels comfortable for my use and I'd like to keep it that way. BUT I sorely miss not having phablet ui. Is there a setting I need to be using to change my SystemUI to a particular dpi to switch everything to Phablet UI while still keeping the overall LCD density to 360? I'm using the "App Settings" module in Xposed and have tried just about everything but can't get the Phablet UI to engage. Any advice would be very much appreciated.
Thanks.
the7thson said:
Hey guys,
I'm using an LCD density of 360 on my Nexus 5 by ending the build.prop, this feels comfortable for my use and I'd like to keep it that way. BUT I sorely miss not having phablet ui. Is there a setting I need to be using to change my SystemUI to a particular dpi to switch everything to Phablet UI while still keeping the overall LCD density to 360? I'm using the "App Settings" module in Xposed and have tried just about everything but can't get the Phablet UI to engage. Any advice would be very much appreciated.
Thanks.
Click to expand...
Click to collapse
i want to do this too...anyone willing to help ?
ranasrule said:
i want to do this too...anyone willing to help ?
Click to expand...
Click to collapse
There are 2 things we need to discuss.
1) System UI layout change to Tablet mode or Phablet mode UI. This changes the layout of the Nav Bar, Status bar and Notification area. Google removed this function. There is no way to get it back.
2) Triggered Tablet layout of specific apps. Developers of apps may wish to change the layout of their apps for a tablet. More screen real estate can mean there are better layouts than used for the phone. The only reliable trigger that a developer can use is dpi.
The bigger screen at the same resolution will have a lower dpi than a smaller screen at the same resolution. We can trigger tablet layout in apps by forcing the dpi down system wide using the build.prop. However, different developers will be triggered by different dpi's meaning you may need a dpi so low you cant see it on your small screen before some apps trigger.
You can use the Xposed module named "app settings" to actually change the layout of individual apps to tablet layout. So for example, you can set Chrome to be tablet layout without changing the dpi of the system or tha app itself. That's the only option though. Not all apps have a tablet mode.
rootSU said:
There are 2 things we need to discuss.
1) System UI layout change to Tablet mode or Phablet mode UI. This changes the layout of the Nav Bar, Status bar and Notification area. Google removed this function. There is no way to get it back.
2) Triggered Tablet layout of specific apps. Developers of apps may wish to change the layout of their apps for a tablet. More screen real estate can mean there are better layouts than used for the phone. The only reliable trigger that a developer can use is dpi.
The bigger screen at the same resolution will have a lower dpi than a smaller screen at the same resolution. We can trigger tablet layout in apps by forcing the dpi down system wide using the build.prop. However, different developers will be triggered by different dpi's meaning you may need a dpi so low you cant see it on your small screen before some apps trigger.
You can use the Xposed module named "app settings" to actually change the layout of individual apps to tablet layout. So for example, you can set Chrome to be tablet layout without changing the dpi of the system or tha app itself. That's the only option though. Not all apps have a tablet mode.
Click to expand...
Click to collapse
Thanks for the reply but the request is for Phablet UI...kind of something like this atleast >>> http://forum.xda-developers.com/showpost.php?p=50945366&postcount=750
as far as my Info goes tablet UI is not longer available but Phablet is possible
ranasrule said:
Thanks for the reply but the request is for Phablet UI...kind of something like this atleast >>> http://forum.xda-developers.com/showpost.php?p=50945366&postcount=750
Click to expand...
Click to collapse
For phablet ui, read point 1.
That screenshot is not phablet ui. Its just a lower dpi.
To lower dpi, either do it system wide using build prop or with xposed module "app settings", set dpi for systemui lower. Say maybe 300.
Sent from my Nexus 5 using Tapatalk
rootSU said:
For phablet ui, read point 1.
That screenshot is not phablet ui. Its just a lower dpi.
To lower dpi, either do it system wide using build prop or with xposed module "app settings", set dpi for systemui lower. Say maybe 300.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I thought Google only removed TableUI, but PhabletUI still exists. I could be wrong though.
the7thson said:
I thought Google only removed TableUI, but PhabletUI still exists. I could be wrong though.
Click to expand...
Click to collapse
Maybe I don't know. My understanding was there was 1 UI now. Maybe you need to ask someone in PA team
IF it does exist, there's no way to get it... Unless PA can do it.
When I got my Oneplus One I was a little disappointed because some apps don't realy leverage the screen size gain compared to smaller screens. E.g. the standard Email-app shows just as many items per screen as it does on a 4.2" screen, just bigger.
Also I wondered how to increase the number of app symbols in a row in the Trebuchet (CM11s standard-launcher) app drawer.
Then I found the solution:
Install Xposed and the App Settings module. Don't forget to activate both and restart the phone.
In App Settings you can change the DPI for individual apps. E.g. I changed the DPI to 400 for Trebuchet. Now I get 5 apps in a row in the app drawer instead of 4. Same with the Email-app: Now it shows more items in the list of mails, just a little smaller.
Hope this helps.
Mitch.
You could also change the DPI from 480 to something smaller in BUILD.PROP, root is required obviously, but then again Xposed also needs root AFAIK.
Changing the BUILD.PROP setting will change your entire UI to the desired DPI which looks pretty amazing IMO
Yep, changing the build.prop is a much more effective method. One small change and you have a global effect, rather than having to change the DPI for apps individually.
Transmitted via Bacon
Another way to change DPI is using https://play.google.com/store/apps/details?id=com.texdroider.texdroider_dpi very minimal app and does the job well. 380 is the dpi I use, no problems with Play Store apps either.
zephiK said:
Another way to change DPI is using https://play.google.com/store/apps/details?id=com.texdroider.texdroider_dpi very minimal app and does the job well. 380 is the dpi I use, no problems with Play Store apps either.
Click to expand...
Click to collapse
I use a DPI of 370 on mine, I can't stand the way everything looks with a stock DPI, it's such a waste of screen real estate.
Transmitted via Bacon
mitch.munich said:
When I got my Oneplus One I was a little disappointed because some apps don't realy leverage the screen size gain compared to smaller screens. E.g. the standard Email-app shows just as many items per screen as it does on a 4.2" screen, just bigger.
Also I wondered how to increase the number of app symbols in a row in the Trebuchet (CM11s standard-launcher) app drawer.
Then I found the solution:
Install Xposed and the App Settings module. Don't forget to activate both and restart the phone.
In App Settings you can change the DPI for individual apps. E.g. I changed the DPI to 400 for Trebuchet. Now I get 5 apps in a row in the app drawer instead of 4. Same with the Email-app: Now it shows more items in the list of mails, just a little smaller.
Hope this helps.
Mitch.
Click to expand...
Click to collapse
Thanks. i will try it with the game "My Railway"... This is so small on stock Opo, it doesn't make fun...
zephiK said:
Another way to change DPI is using https://play.google.com/store/apps/details?id=com.texdroider.texdroider_dpi very minimal app and does the job well. 380 is the dpi I use, no problems with Play Store apps either.
Click to expand...
Click to collapse
since the new hangouts app, it says that this app is not compatible with your device. can anyone else replicate this problem, my dpi is at 410
Afaik there are some "special" dpi levels for apps.. Stock dpi may work, 410 may not, but for example 370 may work again... Dont remember exactly which are good
gerciolisz said:
Afaik there are some "special" dpi levels for apps.. Stock dpi may work, 410 may not, but for example 370 may work again... Dont remember exactly which are good
Click to expand...
Click to collapse
Shows compatible with 380 but yeah what gerciolisz said. Depending what dpi it is, play store may not like it.
There was a modded play store that work around the problem but it hasnt been updated.
Hey, Im currently on 380 dpi and still feel the nav bar is using too much of my screen. I was wondering if you were able to Make it thinner without the use of gravitybox or reducing the DPI. Cheers
Use a custom rom, they have this feature to change the size. Or manually do it but that requires you to get your hands dirty and to recompile the files which there is a guide online on how to do this.
Google search for the guide.
Sent from my A0001 using Tapatalk
Ok, so in the past Huawei has decided on a few of their larger devices to go with 400 DPI instead of the standard 320 DPI that android should be at. This makes the UI a little to large. Sure you can root your phone and tweak the build.prop file for different DPI, but then icons look weird and there's other issues. 400 DPI just looks wrong to me, I'm sure some folks like it, but I really don't
I found something called "App Layout" in the settings today. This is awesome my friends.....
The "Standard" setting is 400 DPI (Default)
"Reduced" looks to be 320 DPI
There's even a custom where you can do per app DPI settings just like you can in Xposed framework!
This is truly a great piece of work from Huawei, Now we can set the DPI where we want it. Nicely done Huawei!
All we need now is to have the memory manager work a little better and I will go on record saying that other than Cyanogen or plain android, this is the best Vendor skin to date. So much you can do with it... I haven't even unlocked or rooted my phone yet and I don't think i'm going to bother (Plus I want to install all the update files without hassle since it seems like they are coming out pretty fast)
omniphil said:
Ok, so in the past Huawei has decided on a few of their larger devices to go with 400 DPI instead of the standard 320 DPI that android should be at. This makes the UI a little to large. Sure you can root your phone and tweak the build.prop file for different DPI, but then icons look weird and there's other issues. 400 DPI just looks wrong to me, I'm sure some folks like it, but I really don't
I found something called "App Layout" in the settings today. This is awesome my friends.....
The "Standard" setting is 400 DPI (Default)
"Reduced" looks to be 320 DPI
There's even a custom where you can do per app DPI settings just like you can in Xposed framework!
This is truly a great piece of work from Huawei, Now we can set the DPI where we want it. Nicely done Huawei!
All we need now is to have the memory manager work a little better and I will go on record saying that other than Cyanogen or plain android, this is the best Vendor skin to date. So much you can do with it... I haven't even unlocked or rooted my phone yet and I don't think i'm going to bother (Plus I want to install all the update files without hassle since it seems like they are coming out pretty fast)
Click to expand...
Click to collapse
Yeah, it's great if you decide to stay stock as you don't have to do much to change the DPI. You can change the DPI also without rooting by opening a command prompt in adb and running a command.
omniphil said:
Ok, so in the past Huawei has decided on a few of their larger devices to go with 400 DPI instead of the standard 320 DPI that android should be at. This makes the UI a little to large. Sure you can root your phone and tweak the build.prop file for different DPI, but then icons look weird and there's other issues. 400 DPI just looks wrong to me, I'm sure some folks like it, but I really don't
I found something called "App Layout" in the settings today. This is awesome my friends.....
The "Standard" setting is 400 DPI (Default)
"Reduced" looks to be 320 DPI
There's even a custom where you can do per app DPI settings just like you can in Xposed framework!
This is truly a great piece of work from Huawei, Now we can set the DPI where we want it. Nicely done Huawei!
All we need now is to have the memory manager work a little better and I will go on record saying that other than Cyanogen or plain android, this is the best Vendor skin to date. So much you can do with it... I haven't even unlocked or rooted my phone yet and I don't think i'm going to bother (Plus I want to install all the update files without hassle since it seems like they are coming out pretty fast)
Click to expand...
Click to collapse
Is this on the new updated roms? Because if can not find this setting on my stock 702 rom version?
Benjiro said:
Is this on the new updated roms? Because if can not find this setting on my stock 702 rom version?
Click to expand...
Click to collapse
I'm on a 703 running B108.
Settings -> Apps -> App Layout
That's what I have...
omniphil said:
I'm on a 703 running B108.
Settings -> Apps -> App Layout
That's what I have...
Click to expand...
Click to collapse
That explains that ... My 702 is still on B103 ... No official updates have come yet for the internal updater.
the only problem though is that the Microsoft Office apps such as Word does not go to tablet mode despite it being set to reducing mode but whenever I tweak the dpi to 320 via adb, it does show in tablet mode but some app icons and task manager are a bit messed up. Other apps such as Facebook or Youtube does seem to display on tablet orientation when in reducing mode.
mcdhol_24 said:
the only problem though is that the Microsoft Office apps such as Word does not go to tablet mode despite it being set to reducing mode but whenever I tweak the dpi to 320 via adb, it does show in tablet mode but some app icons and task manager are a bit messed up. Other apps such as Facebook or Youtube does seem to display on tablet orientation when in reducing mode.
Click to expand...
Click to collapse
I think that has to do with teh odd 1920x1200 rez. If it were 1920x1080 then it probably would detect phone mode/tablet mode correctly
Flash rom KangVIP, you can adjust DPI switching to 400, 380,360,340,320 dpi
http://cn.club.vmall.com/thread-6033530-1-1.html
eennap said:
Flash rom KangVIP, you can adjust DPI switching to 400, 380,360,340,320 dpi
http://cn.club.vmall.com/thread-6033530-1-1.html
Click to expand...
Click to collapse
If I switch the dpi to 320 if I'm using that rom does the UI becomes a bit weird? I just wanna ask because whenever I switch the actual dpi to 320 via adb (with the original B109 rom), some of the icons are smaller and have green background in them and other glitches.
mcdhol_24 said:
If I switch the dpi to 320 if I'm using that rom does the UI becomes a bit weird? I just wanna ask because whenever I switch the actual dpi to 320 via adb (with the original B109 rom), some of the icons are smaller and have green background in them and other glitches.
Click to expand...
Click to collapse
UI will be normal same as original B109 rom but font in app will be smaller.
mcdhol_24 said:
If I switch the dpi to 320 if I'm using that rom does the UI becomes a bit weird? I just wanna ask because whenever I switch the actual dpi to 320 via adb (with the original B109 rom), some of the icons are smaller and have green background in them and other glitches.
Click to expand...
Click to collapse
If you use Nova Launcher, that fixes the icon problem.
For the unlucky ones with 702L. I found a possible fix (still testing) to set the dpi to 320 without issues in SwiftKey being huge for example. Need to be ROOTED. So this is what I did.
1. Edit the build prop and add/change both " qemu.sf.lcd_density=320 " and " ro.sf.lcd_density=320 "
2. Use terminal emulator with
Su
Wm density 320
Reboot.
Now Wm density should show one value not 2 and SwiftKey should work as well.
Cheers.
Nice. Been looking for the SwiftKey fix. So, for this fix to be working do you need to get it rooted? Cheers
On 2nd thought, this SwiftKey problem doesn't exist on other keyboard apps like fleksy, googles own and go keyboard.
Yes you have to be rooted for that. But being rooted has of course a lot of other advantages and is easy to do once the bootloader is unlocked (I used the paid option from the root guide and I was rooted within half an hour).
I tried the other keyboards as well, seems SwiftKey uses other parts of build.prop to get dpi.
Hope I could help.