Related
I have been helping Sinistertensai with his ShenduOS port for the HTC EVO 4G. I got Wimax to work and was wanting to see if anyone knows how to add a Wimax toggle to the power widget dropdown from the status bar. The port is CM7 based. In the SystemUI.apk I see there is WimaxButton.smali. I have tried adding the ids for it in public.xml and creating pngs for the toggle. I get no errors on compile but I get reboots or force closes when I try to bring up the power widget dropdown. I have very limited experience with editing smail code. I have also tried copying over the resources, classes, and xmls to the original apk with the same results. I have researched how to edit smali but I could just be doing it wrong or leaving something out. This has been driving me to madness. If anyone could help out that would be amazing!
Is there a reason you can't rebuild from source with Wimax enabled?
Sent from my SCH-R760 using Tapatalk 2
The ShenduOS SystemUI has been changed drastically and I cannot find the source code. That would require me to completely redo what Shendu has done and is well beyond my capabilities. The functionality for the wimax is there, I just need to find a way to add the toggle button. The actual widget has a wimax toggle which works, just not the one in the status bar.
Sent from my EVO using xda premium
I have only done smali a few times. How I did it was for example get a cm build going. Remove all wimax toggle related noti widget elements. Compile. Now you have a systemui base. Now build with the wimax toggle. You have a wimax toggle systemui.
Then use a program like beyond compare and after apktooling both systemui in their own folders. Compare the smali differences. Should get you pretty close. Of course there will be some trial and error if the systemui is different then that of cm.
Sent from my Galaxy Nexus using xda premium
The code is quite different that the CM7 code. I have found what needs to be edited, it just results in reboots upon clicking on the status bar to open the powerwidget dropdown. Here are the steps I take:
Decompile SystemUI.apk
In PowerWidget.smali -> replace both instances of toggleNetworkMode with toggleWimax
In WimaxButton.smali -> write down ids from method updateState (0x7f0200ca is off, 0x7f0200cb is on)
In public.xml -> Removed bad APKTOOL_DUMMYs for above ids. Add the following lines:
<public type="drawable" name="stat_wimax_off" id="0x7f0200ca" />
<public type="drawable" name="stat_wimax_on" id="0x7f0200cb" />
In res/drawable-hdpi -> Created on/off images and placed them there
In drawables.xml -> Removed bad APKTOOL_DUMMYs for above ids that were set to false. Add the following lines:
<item type="drawable" name="stat_wimax_off">true</item>
<item type="drawable" name="stat_wimax_on">true</item>
Recompiled
Pushed to phone with adb and cleared dalvik cache
Reboot
I have also tried pushing the changes and overwriting the ones in the original using Archive Manager(Ubuntu) with the same issues. If someone could point out what I am doing wrong that would help alot! I could have broken my tools(Android Utility/apktool). Feel free to give it a shot if you want. Once I/someone gets it right I will write up a tutorial.
Finally got the time to hack some files to make 4x5 Sense rosie available on the Evo 4G LTE. This post is like most guides: assumes some knowledge of apktool, hex editing, and other programming "skills". Note that this post is designed for 720p displays so the numbers like the cell gaps might have to be modified if your phone is other than 720 x 1280 resolution, but the basics should still work. Also, as of this time, there are no M10 editing tools that work with Sense 4 so if some become available, obviously the best method of changing the M10 files will change (you won't have to use a hex editor). That said, the basics will still guide you through what you need to do in order to get 4x5 rosie working on your Sense 4 ROM.
First, let's edit the relevant m10 files
Once you've decompiled Rosie.apk from your ROM, we will edit these m10 files with a hex editor. We only need to change 3 bytes in one file and one byte in the second m10 file:
First, open \assets\Port\rosie_screen.m10 in your hex editor. I use XVI32. Search for "cell on Y" without the quotes. Note that you must use a unicode search (because there are zeroes between each character). Either that, or search for the hex string that is displayed in the window below instead. There should only be one occurrence. When you get there, we want to change the "4" that follows that and the "80" associated with the cell gap. We'll change the "4" to a "5" and the cell gap from "80" to "70". You can only reduce the cell gap slightly because many multi-cell widgets take up not only multiple rows, but also assume a certain size for the cell gap. Taking the value from 80 to 70 seems to be the best compromise for fitting all the icons (and text) and not overlapping 2-row widgets. Here's a screen shot showing the two values that got changed. When done editing, save the changes to the rosie_screen.m10 file.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After you've edited \assets\Port\rosie_screen.m10 as above, go to \assets\Land\rosie_screen.m10 and do the edits as above but only do the first edit: changing the 4 to a 5. In landscape mode, there's already only a 10 pixel gap between cells and you really can't reduce it. Landscape rosie at 4x5 is a compromise at best, but it does work without changing the gap... although with a bit of unavoidable overlap.
m10 editing done, now let's edit the XML files
Open \res\values\integers.xml and we'll change the bottom line from a 4 to a 5. It should look like this after edited:
Code:
<integer name="config_folderCellCountY">5</integer>
Open \res\values-normal-port-xhdpi\integers.xml and changeone 4 to a 5. This is how the line look after edited:
Code:
<integer name="config_cellLayoutCellCountY">5</integer>
Open \res\values-normal-port-xhdpi\dimens.xml and change one 80 to a 26. This is how the two lines look after edited:
Code:
<dimen name="workspace_height_gap">26.0px</dimen>
Open \res\values-normal-land-xhdpi\integers.xml and change one 4 to 5 near the top. This is how the line looks after edited:
Code:
<integer name="config_cellLayoutCellCountY">5</integer>
Open \res\values-normal-land-xhdpi\dimens.xml and change one 155 to 122 near the top/middle. This is how the line looks after edited:
Code:
<dimen name="workspace_cell_height">122.0px</dimen>
That's it. Recompile with the modified m10 and xml files and you should have a working 4x5 rosie for Sense 4. Note that the "xhdpi" folder is what is used on 720p phones like the Evo 4G LTE and One X. If your phone uses quarter-HQ (QHD), the files you'll want to edit will be the same XML files but in a different folder (like hdpi instead of xhdpi).
Mike
reserved
Woooo first? Lol
Sent from my EVO using Tapatalk 2
Thanks mike.
Sent from my EVO using xda app-developers app
Looks good. This was one of the more annoying things about Sense while I was still using it.
How are you not a rec dev
Sent from my EVO using xda premium
Awesome.
Sent from my White EVO LTE on Tapa2
Great job Mikey. I'd love to see some screenshots...
ssojyeti2 said:
Great job Mikey. I'd love to see some screenshots...
Click to expand...
Click to collapse
Sent from my Mean Evo LtE
almost
this is what i got following the op
(perhaps because i selected Sense 4 instead of ICS in apk changer)
in the op, the 3rd xml file edit,
dev mentions two, but only one edit and line is listed
Its nice to see a dev share their work that they figured out :victory: Big props on beings a nice dude you sir will be the first person i donate to when i get back from vagas
fernando sor said:
How are you not a rec dev
Sent from my EVO using xda premium
Click to expand...
Click to collapse
+1 Mikey knows his stuff and his Rom is the best!
would there be a way in these same files to remove the names under the shortcuts and/or adjust the size of the app drawer? How would we go about exploring these?
removed ...
mikeyxda said:
Finally got the time to hack some files to make 4x5 Sense rosie available on the Evo 4G LTE. This post is like most guides: assumes some knowledge of apktool, hex editing, and other programming "skills". Note that this post is designed for 720p displays so the numbers like the cell gaps might have to be modified if your phone is other than 720 x 1280 resolution, but the basics should still work. Also, as of this time, there are no M10 editing tools that work with Sense 4 so if some become available, obviously the best method of changing the M10 files will change (you won't have to use a hex editor). That said, the basics will still guide you through what you need to do in order to get 4x5 rosie working on your Sense 4 ROM.
First, let's edit the relevant m10 files
Once you've decompiled Rosie.apk from your ROM, we will edit these m10 files with a hex editor. We only need to change 3 bytes in one file and one byte in the second m10 file:
First, open \assets\Port\rosie_screen.m10 in your hex editor. I use XVI32. Search for "cell on Y" without the quotes. Note that you must use a unicode search (because there are zeroes between each character). Either that, or search for the hex string that is displayed in the window below instead. There should only be one occurrence. When you get there, we want to change the "4" that follows that and the "80" associated with the cell gap. We'll change the "4" to a "5" and the cell gap from "80" to "70". You can only reduce the cell gap slightly because many multi-cell widgets take up not only multiple rows, but also assume a certain size for the cell gap. Taking the value from 80 to 70 seems to be the best compromise for fitting all the icons (and text) and not overlapping 2-row widgets. Here's a screen shot showing the two values that got changed. When done editing, save the changes to the rosie_screen.m10 file.
After you've edited \assets\Port\rosie_screen.m10 as above, go to \assets\Land\rosie_screen.m10 and do the edits as above but only do the first edit: changing the 4 to a 5. In landscape mode, there's already only a 10 pixel gap between cells and you really can't reduce it. Landscape rosie at 4x5 is a compromise at best, but it does work without changing the gap... although with a bit of unavoidable overlap.
m10 editing done, now let's edit the XML files
Open \res\values\integers.xml and we'll change the bottom line from a 4 to a 5. It should look like this after edited:
Code:
<integer name="config_folderCellCountY">5</integer>
Open \res\values-normal-port-xhdpi\integers.xml and changeone 4 to a 5. This is how the line look after edited:
Code:
<integer name="config_cellLayoutCellCountY">5</integer>
Open \res\values-normal-port-xhdpi\dimens.xml and change one 80 to a 26. This is how the two lines look after edited:
Code:
<dimen name="workspace_height_gap">26.0px</dimen>
Open \res\values-normal-land-xhdpi\integers.xml and change one 4 to 5 near the top. This is how the line looks after edited:
Code:
<integer name="config_cellLayoutCellCountY">5</integer>
Open \res\values-normal-land-xhdpi\dimens.xml and change one 155 to 122 near the top/middle. This is how the line looks after edited:
Code:
<dimen name="workspace_cell_height">122.0px</dimen>
That's it. Recompile with the modified m10 and xml files and you should have a working 4x5 rosie for Sense 4. Note that the "xhdpi" folder is what is used on 720p phones like the Evo 4G LTE and One X. If your phone uses quarter-HQ (QHD), the files you'll want to edit will be the same XML files but in a different folder (like hdpi instead of xhdpi).
Mike
Click to expand...
Click to collapse
Is it possible to create a flashable version or automated version of this mod? Thanks!
~ Mike
michael.stollaire said:
Is it possible to create a flashable version or automated version of this mod? Thanks!
~ Mike
Click to expand...
Click to collapse
+1
Sent from my EVO using xda premium
michael.stollaire said:
Is it possible to create a flashable version or automated version of this mod? Thanks!
~ Mike
Click to expand...
Click to collapse
you mean you're not using his ROM ? tsk tsk
4x5 with/without 360 is available in Mean ROM
this is from private betatest i'm running (not Mean ROM)
following the op guide,
i got 4x5 working on it -
thanks for posting and sharing this info, op.
@mikeyxda -
Now that m10 tools is out and working via VTS, this method is no longer needed. I just modded rosie for superLTE ROM base and it worked better and easier than this.
Essentially the "correct" way to do this now would be the way that jeffsanace originally discoved on the evo3D with some tweaking.
In rosie screen m10 you change the Y cells to 5, you had the spacing at 70 which is not correct, he and I discovered today that it is 100 for the LTE (after some testing)
Also the only edits needed in values are in integers near the bottom, change cell folder Y from 4 to 5, and then in values-normal-port-xhdpi near the top do the same thing. nothing at all in dimensions or other folders.
that's it, easy peasy, spacing is correct and all that jazz.
If you want the apk feel free to pull that from our svn, otherwise our write a more professional tutorial later on, thanks for breaking ground, hope you enjoy the new method and no spacing issues
il Duce said:
@mikeyxda -
Now that m10 tools is out and working via VTS, this method is no longer needed. I just modded rosie for superLTE ROM base and it worked better and easier than this.
Essentially the "correct" way to do this now would be the way that jeffsanace originally discoved on the evo3D with some tweaking.
In rosie screen m10 you change the Y cells to 5, you had the spacing at 70 which is not correct, he and I discovered today that it is 100 for the LTE (after some testing)
Also the only edits needed in values are in integers near the bottom, change cell folder Y from 4 to 5, and then in values-normal-port-xhdpi near the top do the same thing. nothing at all in dimensions or other folders.
that's it, easy peasy, spacing is correct and all that jazz.
If you want the apk feel free to pull that from our svn, otherwise our write a more professional tutorial later on, thanks for breaking ground, hope you enjoy the new method and no spacing issues
Click to expand...
Click to collapse
ok duce. sometime this week please show me how easy peasy it is for this noob, if you would. thanks.
Sent from my SPH-L710 using xda premium
lowetax said:
ok duce. sometime this week please show me how easy peasy it is for this noob, if you would. thanks.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
lol, I just did. jk,
First go get VTS (virtuous ten studio) then hit me up on gtalk (or PM me your gtalk) and I'll walk you thru it. I might put up a tut, jeff might put up a tut, since really this is HIS mod. But not all right away and stuff, we be busy
Evening all,
Does any one know of a way to either Remove or Hide the operator logo form the Lock-screen ? My OCD is starting to kick in.
Thanks in advance.
Schumi 01 said:
Evening all,
Does any one know of a way to either Remove or Hide the operator logo form the Lock-screen ? My OCD is starting to kick in.
Thanks in advance.
Click to expand...
Click to collapse
Removing operator name requires you to decompile M10 files, I do this for fun so the only tool I'm aware of that does this is VTS. Nevertheless the steps are:
Decompile Idlescreen_Base.apk
In assets open: Lockscreen_time.m10/0x0dc105ce/lockscreen_time/timeline.time_fade/
Locate the code that says: /text.lockscreentime_operator - change the value to zero
Recompile the apk, then you can push the modded app to your phone via VTS or just swap it out with a file browser and reboot.
I've attached an Idlescreen.apk that is already modded, however, the clock text has been slightly downsized (not a result of the mod), also I don't like screen shortcuts, but they will still work.
Thanks for the tip!! I was able to remove everything. Operator, Time and Date.
Better thing to do is to look for <Bool Name="Visible" Header="239748898" IDC="true">true</Bool>
<Unknown Name="0x7ce54727" Header="239748898" IDC="true">00000000</Unknown>
<Unknown Name="0x7c9663eb" Header="239748898" IDC="true">00406144</Unknown>
and change to
<Bool Name="Visible" Header="239748898" IDC="true">false</Bool>
<Unknown Name="0x7ce54727" Header="239748898" IDC="true">00000000</Unknown>
<Unknown Name="0x7c9663eb" Header="239748898" IDC="true">00406144</Unknown>
Thanks for the info Ghost, if you'd like to go even more minimal you can hide the shortcut text:
Lockscreen_shortcut.m10/0x0dc105ce/Lockscreen_Shortcut/
Under: <FxTimeLine Name="textcomp.shortcut_name1" Header="0x7c89ba8b" Type="0x19930c9c">
Find: <Bool Name="Visible" Header="239748898" IDC="true">true</Bool>
Change to: <Bool Name="Visible" Header="239748898" IDC="true">false</Bool>
Under: <FxTimeLine Name="textcomp.shortcut_name2" Header="0x7c89ba8b" Type="0x19930c9c">
Find: <Bool Name="Visible" Header="239748898" IDC="true">true</Bool>
Change to: <Bool Name="Visible" Header="239748898" IDC="true">false</Bool>
Under: <FxTimeLine Name="textcomp.shortcut_name3" Header="0x7c89ba8b" Type="0x19930c9c">
Find: <Bool Name="Visible" Header="239748898" IDC="true">true</Bool>
Change to: <Bool Name="Visible" Header="239748898" IDC="true">false</Bool>
Under: <FxTimeLine Name="textcomp.shortcut_name4" Header="0x7c89ba8b" Type="0x19930c9c">
Find: <Bool Name="Visible" Header="239748898" IDC="true">true</Bool>
Change to: <Bool Name="Visible" Header="239748898" IDC="true">false</Bool>
Is it possible to remove the (current) bit from the location?
Ghost said:
Is it possible to remove the (current) bit from the location?
Click to expand...
Click to collapse
If you set that specific location instead of using current location
Sent from my HTC One XL using Tapatalk 2
Thank you both, will give them a go a bit later in, thanks again for your replies.
Sent from my HOX+
fnut6969 said:
Removing operator name requires you to decompile M10 files, I do this for fun so the only tool I'm aware of that does this is VTS. Nevertheless the steps are:
Decompile Idlescreen_Base.apk
In assets open: Lockscreen_time.m10/0x0dc105ce/lockscreen_time/timeline.time_fade/
Locate the code that says: /text.lockscreentime_operator - change the value to zero
Recompile the apk, then you can push the modded app to your phone via VTS or just swap it out with a file browser and reboot.
I've attached an Idlescreen.apk that is already modded, however, the clock text has been slightly downsized (not a result of the mod), also I don't like screen shortcuts, but they will still work.
Click to expand...
Click to collapse
Thank you for supplying the Apk file, so much easier for myself to use that, than try to decompile an Apk file It worked like a charm
Really happy now the logo has gone.
Thanks once again.
Sent from my HOX+
Schumi 01 said:
Thank you for supplying the Apk file, so much easier for myself to use that, than try to decompile an Apk file It worked like a charm
Really happy now the logo has gone.
Thanks once again.
Sent from my HOX+
Click to expand...
Click to collapse
You're welcome, not a problem at all, if you'd like one with the original text size or no icon labels let me know.
fnut6969 said:
You're welcome, not a problem at all, if you'd like one with the original text size or no icon labels let me know.
Click to expand...
Click to collapse
Thanks, if it isnt too much bother could you post one without the No icon labels too,I think it looks so much cleaner without the labels.
The text size is on the clock is fine.
Thanks
superchilpil said:
If you set that specific location instead of using current location
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
I dont think you can use a spseific location in the weather lock screen can you?
Schumi 01 said:
Thanks, if it isnt too much bother could you post one without the No icon labels too,I think it looks so much cleaner without the labels.
The text size is on the clock is fine.
Thanks
Click to expand...
Click to collapse
Here you go.
Ghost said:
I dont think you can use a spseific location in the weather lock screen can you?
Click to expand...
Click to collapse
Ghost, did you try looking in Idlescreen_Weather.apk I found a way to hide the entire city name, but it also inadvertently hid the current weather conditions.
fnut6969 said:
Here you go.
Click to expand...
Click to collapse
Thanks fnut, you are a prince amongst men, it works like a charm and it looks so much better.
Sent from my HOX+
Schumi, here is the Idlescreen you wanted, if you need the text size changed or anything moved lower let me know.
Compile
How can I compile and decompile M10 file...?
Can you please send me Link from where I can download that tool.?
samecin said:
How can I compile and decompile M10 file...?
Can you please send me Link from where I can download that tool.?
Click to expand...
Click to collapse
Vts is the tool try here
http://www.virtuous-ten-studio.com/
Sent From My Sweet Ass EVO LTE
fnut6969 said:
Schumi, here is the Idlescreen you wanted, if you need the text size changed or anything moved lower let me know.
Click to expand...
Click to collapse
Oh fnut, you are a star, once again i thank you.
Brilliant.
Thanks very much.
Sent from my HOX+
fnut6969 said:
Schumi, here is the Idlescreen you wanted, if you need the text size changed or anything moved lower let me know.
Click to expand...
Click to collapse
Sorry to be a pain, but in your own time obviously, could you just change the text size to the first APK you sent me, then that will be the last request i have.
Honestly.
Thanks again fnut
Schumi, here's the IdleScreen the text is 3/4's (or whatever value 0.75 is in the world of M10 code)of the stock size.
Anyone have a flashable zip of the original at&t signal icons? I kinda miss the original 4G 4GLTE icons on my phone after I updated to an international ROM. I know there are the colored ones but I just want the plain white ones. Thanks.
+1
Sent from my HTC One using Tapatalk now Free
The easiest way to do this is just to change the sku_id in /system/customize/ACC/default.xml to 7. You can do this with any text editor, and the line you're looking for is near the end:
<item type="integer" name="sku_id">42</item> (42 is the sku_id for wwe versions, 7 is for ATT)
Then reboot
[How-to] Maximum StatusBar Brightness 4.4.2
This guide is based on the KK 4.4.2 Galaxy S5 builds.
I noticed that Samsung always make the statusbar notification areas a bit dim. Probably to help with battery conservation.
This requires decompiling SystemUI.apk.
SystemUI/res/values/dimens.xml edit
Code:
Change these three lines
New values are in BLUE
<item type="dimen" name="status_bar_icon_drawing_alpha">[COLOR="Blue"]100.0%[/COLOR]</item>
<item type="dimen" name="system_icon_area_alpha">[COLOR="Blue"]1.0[/COLOR]</item>
<item type="dimen" name="notification_icon_area_alpha">[COLOR="Blue"]1.0[/COLOR]</item>
Note:
Screenshots are best viewed from a PC so you can rapidly swap images to see the difference.
Nice.
Thanks
Weird. I have no values/dimens.xml file. Using to rootexplorer.
cAase said:
Weird. I have no values/dimens.xml file. Using to rootexplorer.
Click to expand...
Click to collapse
As stated in the OP, this requires being able to decompile the system file SystemUI.apk to make the edits.
This thread is now part of the GALAXY S5 UNIFIED MODS THREAD - GUIDES & LINKS. Check it out when you have time.
Where i can find your teme for status bar ?.
Thanks
Great mod tdunham thank you very much for this tutorial. Working on my S3 using your old method found here. This may be the lazy way but it worked a lot easier for me to just make vrtheme flashables for this instead of doing a full release.
The reason they do this i think is not to save battery but to stop screen burn in of the statusbar icons. Doesnt matter on roms that have changeable icons or colors i suppose but doing this on a standard systemui with white icons may increase the chance of burn in.
I may be wrong but thought it worth mentioning
Sent from my SM-G900F using Tapatalk