Related
I need to change my LCD density on my phone (NAND / Warm Donut), but I do not want to reinstall the whole system...is there a way to change the LCD density without formatting/reinstalling Android?
Also what is the best NBH resolution and density combination to use?...I tried 120 density on 240x320 NBH file, but it is 'too big'...I have to scroll down to see stuff. 110 was perfect it seemed for 240x320 except that it left some black space on the edges at times.
Thanks,
-C
su
mount /system -o rw,remount
edit ro.sf.lcd_density in /system/build.prop
mount /system -o ro,remount
then reboot
I am a Windows user. How do I do it in Windows or in the phone. Also my phone is not "rooted" (whatever that means)
crobs808 said:
I am a Windows user. How do I do it in Windows or in the phone. Also my phone is not "rooted" (whatever that means)
Click to expand...
Click to collapse
Our phones are rooted, period.
You have to use adb to do it from windows or linux, or be comfy using vi on the phone (ha.)
so you'd do the remount stuff mentioned above, then
Code:
adb pull /system/build.prop/ro.sf.lcd_density c:\mydata\ro.sf.lcd_density
*edit the pulled file*
adb push c:\mydata\ro.sf.lcd_density /system/build.prop/
mrkite38 said:
Our phones are rooted, period.
You have to use adb to do it from windows or linux, or be comfy using vi on the phone (ha.)
so you'd do the remount stuff mentioned above, then
Code:
adb pull /system/build.prop/ro.sf.lcd_density c:\mydata\ro.sf.lcd_density
*edit the pulled file*
adb push c:\mydata\ro.sf.lcd_density /system/build.prop/
Click to expand...
Click to collapse
Ok thanks...now, what is the best NBH resolution and density value combination to use for the Vogue?
open a terminal "better terminal emulator" on your phone
type
su
mount /system -o rw,remount
Click to expand...
Click to collapse
use astro to browse and edit /system/build.prop
look for the line ro.sf.lcd_density=120
change it to whatever you like save changes.
makes filesystem read only
Code:
mount /system -o ro,remount
restart phone
seriously read Tatnai's FAQ (apparently yours isn't the easiest if it didn't work on your own Vogue) and stop making these useless threads.
berardi said:
seriously read Tatnai's FAQ (apparently yours isn't the easiest if it didn't work on your own Vogue) and stop making these useless threads.
Click to expand...
Click to collapse
Huh? I didn't incorporate anything about LCD density into my tutorial on purpose...my tutorial is about how to install Android via the NAND method...has nothing to do with density tweaking, and I never intended it to.
Also "stop making threads"...? What is this forum for then, because I only post a thread when the search or FAQs do not cover something. Isn't that the point of a forum?
myn said:
Change LCD Density to 110
Change LCD Density to 160
Click to expand...
Click to collapse
If you want any other density edit the build.prop within these files - look for lcd density and change it to what you want. Go into your boot up menu and do "install update"
Do a little reading like everyone else does, studies show it is good for your brain.
if using 320x480, you should use lcd.density of 160.
if using 240x320, most people use something between 110 and 120. I like 110, things are a little smaller, easier to see in messaging, and the eclair dialer and wysie's dialer fit the screen. others like 120, because supposedly it is a little "crisper"; try for yourself. I've played around with 113, 115, -> basically everything between 120 and 110.
if using 320x428 (does anyone use this anymore???) use 160 (I think, I can't even remember anymore).
there is a full discussion of other benefits of different resolutions in the FAQ thread. also, you might want to take a look at the market FAQ post, as it applies.
berardi said:
If you want any other density edit the build.prop within these files - look for lcd density and change it to what you want. Go into your boot up menu and do "install update"
Do a little reading like everyone else does, studies show it is good for your brain.
Click to expand...
Click to collapse
ha...you like following me around the board and insulting me. you have done this now on three threads where i simply ask a question on how to do something, then you state that my post is 'useless'. that really lends itself to good discussion. please re-evaluate why you post things because you are definitely not doing it to help me or answer the original question.
p.s. - i did read the forum and search before i posted. all the instructions so far were how to do it on Linux or how to do it using ADB, neither of which I have at my disposal. The other posters in this thread helped, which I had already stated (post #5 on pg.1) before you even posted, so there was no reason for you to post all all, except to get your insult in I guess. Stop following me around the forum. Now.
crobs808 said:
ha...you like following me around the board and insulting me. you have done this now on three threads where i simply ask a question on how to do something, then you state that my post is 'useless'. that really lends itself to good discussion. please re-evaluate why you post things because you are definitely not doing it to help me or answer the original question.
p.s. - i did read the forum and search before i posted. all the instructions so far were how to do it on Linux or how to do it using ADB, neither of which I have at my disposal. The other posters in this thread helped, which I had already stated (post #5 on pg.1) before you even posted, so there was no reason for you to post all all, except to get your insult in I guess. Stop following me around the forum. Now.
Click to expand...
Click to collapse
It is my opinion man, can't we all post our own opinions wherever we want? these were your words afterall..
As for you reading the forum and not finding the answers, well apparently you can't read very well. Trust me I am FAR from a coder / developer / hacker - I learned how to do it simply by reading other posts. If you do a little reading you can get far.
Hoping someone can point out the error of my ways ... I am running kaiser-eclair via nand on my Polaris and trying to edit build.prop in order to adjust density using the "su" and "mount" commands above. Astro is unable to save changes as I do not appear to be getting write access to either /system or build.prop. When I open terminal, I am greeted by $. I entered "su" and got a new line with #. Here I typed "mount /system -o rw,remount". I changed ro.sf.lcd_density from 160 to 110 in build.prop using Astro but could not save changes - I checked the build.prop permissions (-r-) and /system permissions (dr-). Please pardon my lack of Linux savvy-ness, but what have I missed? Thanks!
tmcfarland said:
Hoping someone can point out the error of my ways ... I am running kaiser-eclair via nand on my Polaris and trying to edit build.prop in order to adjust density using the "su" and "mount" commands above. Astro is unable to save changes as I do not appear to be getting write access to either /system or build.prop. When I open terminal, I am greeted by $. I entered "su" and got a new line with #. Here I typed "mount /system -o rw,remount". I changed ro.sf.lcd_density from 160 to 110 in build.prop using Astro but could not save changes - I checked the build.prop permissions (-r-) and /system permissions (dr-). Please pardon my lack of Linux savvy-ness, but what have I missed? Thanks!
Click to expand...
Click to collapse
Are you using one of those files I linked to? I found it easiest to do it in windows on a pc. If so, open up the .tar file and look for build.prop - open that and make the change. Close the file and it should allow you to save changes. Put that on an sd card in your phone reboot and install update and you should be good.
berardi said:
Are you using one of those files I linked to? I found it easiest to do it in windows on a pc. If so, open up the .tar file and look for build.prop - open that and make the change. Close the file and it should allow you to save changes. Put that on an sd card in your phone reboot and install update and you should be good.
Click to expand...
Click to collapse
That did the trick ... many thanks!
crobs808 said:
I need to change my LCD density on my phone (NAND / Warm Donut), but I do not want to reinstall the whole system...is there a way to change the LCD density without formatting/reinstalling Android?
Also what is the best NBH resolution and density combination to use?...I tried 120 density on 240x320 NBH file, but it is 'too big'...I have to scroll down to see stuff. 110 was perfect it seemed for 240x320 except that it left some black space on the edges at times.
Thanks,
-C
Click to expand...
Click to collapse
Either use an androidupdate.tar, or, if you need to do it on your phone:
Open BetterTerminal.
1. Type 'su', enter.
2. Type 'mount -o remount,rw /system', enter.
3. Type 'vi /system/build.prop'.
4. Scroll down to the build.prop section. Put the cursor where you want to modify.
5. Hit 'i' to go into edit/insert mode.
6. Hit backspace to delete the comment "#" of the line you want..
7. Add a # to the old density line. You can safely use the dpad to move in edit mode.
8. Hit escape (Hold Center Button and type '1'), to leave edit/insert mode.
9. Type ':wq', then enter, to write and quit.
10. Power down (the proper way, hold red button, hit power off....).
You can always hit escape (Center-1), then ':q<enter>' to quit without saving if you mess up. Then start over.
I just did this, so it works.
Vi has two modes, edit mode, and command mode. If you don't know what mode you're in, always just hit ESC (Hold center button, type the number '1') to return you to command mode.
BetterTerminal is kinda screwy, the cursor covers the letter before it, so you have to keep that in mind.
Personally, I prefer 120, it's nice and clear. It originally was changed from 120 to 110 because Google Maps would freeze on the 3.4.0? update and a density of 120, however 4.0.0+ seems to fix that. I don't know why Myn doesn't go back.... Google maps works perfectly fine for me now on 120.
jnadke said:
Either use an androidupdate.tar, or, if you need to do it on your phone:
Open BetterTerminal.
1. Type 'su', enter.
2. Type 'remount -o remount,rw /system', enter.
3. Type 'vi /system/build.prop'.
4. Scroll down to the build.prop section. Put the cursor where you want to modify.
5. Hit 'i' to go into edit/insert mode.
6. Hit backspace to delete the comment "#" of the line you want..
7. Add a # to the old density line. You can safely use the dpad to move in edit mode.
8. Hit escape (Hold Center Button and type '1'), to leave edit/insert mode.
9. Type ':wq', then enter, to write and quit.
You can always hit escape (Center-1), then ':q<enter>' to quit without saving if you mess up. Then start over.
I just did this, so it works.
Vi has two modes, edit mode, and command mode. If you don't know what mode you're in, always just hit ESC (Hold center button, type the number '1') to return you to command mode.
BetterTerminal is kinda screwy, the cursor covers the letter before it, so you have to keep that in mind.
Personally, I prefer 120, it's nice and clear. It originally was changed from 120 to 110 because Google Maps would freeze on the 3.4.0 update and a density of 120, however 3.4.1+ seems to fix that. I don't know why Myn doesn't go back....
Click to expand...
Click to collapse
Man you are a vi hacker!!
The only reason I am using 110 (soon to be 113) is because the eclair dialers cut off the top of the numbers with 120. Some themes however don't have the eclair dialer so 120 is completely perfect for it.
This process of changing density will become inherently easier come the next release of Warm Donut . More to come as I make more progress.. I will leave it at that.
myn said:
Man you are a vi hacker!!
The only reason I am using 110 (soon to be 113) is because the eclair dialers cut off the top of the numbers with 120. Some themes however don't have the eclair dialer so 120 is completely perfect for it.
This process of changing density will become inherently easier come the next release of Warm Donut . More to come as I make more progress.. I will leave it at that.
Click to expand...
Click to collapse
Astro wouldn't save the changes to build.prop Even after su/remount (That's because only BetterTerminal gets su privileges, not Astro)
Yeah, I've learned to love vi, mainly because searching is similar to sed, unlike that stupid emacs.
I actually use 123, I'm greedy
the 1, 2, 3 don't bother me in the least, you can still press them and I rarely dial numbers manually
tmcfarland said:
Hoping someone can point out the error of my ways ... I am running kaiser-eclair via nand on my Polaris and trying to edit build.prop in order to adjust density using the "su" and "mount" commands above. Astro is unable to save changes as I do not appear to be getting write access to either /system or build.prop. When I open terminal, I am greeted by $. I entered "su" and got a new line with #. Here I typed "mount /system -o rw,remount". I changed ro.sf.lcd_density from 160 to 110 in build.prop using Astro but could not save changes - I checked the build.prop permissions (-r-) and /system permissions (dr-). Please pardon my lack of Linux savvy-ness, but what have I missed? Thanks!
Click to expand...
Click to collapse
Ditto - I tried doing it this way after reading a post on page like 153 (or there abouts) on the main Myn Warm Donut thread to no avail. Definitely doesn't work.
I was really getting tired of my carrier name showing up twice on the lockscreen and taking up extra real estate on my notification drop-down so I figured out how to disable the SPN from showing and how to customize the PLMN to say whatever I want.
KEY FILES TO EDIT
/data/data/com.android.providers.telephony/optable.db
/system/etc/apns-conf.xml
/system/etc/spn-conf.xml
In the apns-conf.xml make sure your provider is listed with a numeric value.
Here's an example: numeric="311370" mcc="311" mnc="370"
* As you can see the numeric is the MCC plus the MNC.
In the spn-conf.xml make sure your provider is listed with an spnOverride.
Here's an example: <spnOverride numeric="311370" spn_display_rule="SPN_RULE_SHOW_PLMN" spn_override_only_on="310,311"/>
The optable.db needs to be edited with SQLite Database Browser to add your numeric and the text to display.
Here are a few pre-configured downloads:
PLMN: CyanogenMod
http://www.4shared.com/file/BawWWTpv/cm7_plmn_gsm_crespo.html
PLMN: The Ultimate Droid
http://www.4shared.com/file/jo0455rx/tud_plmn_gsm_crespo.html
PLMN: GCI Wireless
http://www.4shared.com/file/l3fZUzGu/gci-apns-plmn.html
PLMN: B*** I Got An Android (with no asterisks)
http://www.4shared.com/file/Vkz6poYC/*****_plmn_gsm_crespo.html
NSFW YouTube Video - B*** I Got An Android
Flash these files AFTER you have flashed a ROM and booted up at least once! I tested all four files on TUD 3.0.0 Beta, CM7 A3, and various CM7 Crackflasher builds.
*Screenshots are from CM7 Crackflasher build #54 with the Jungle Waterfall livewallpaper
Very cool mod. I will try this out when I have the time!
thank you
Love this, it worked great on Bionix with 1.3 kernel. For some reason running the same rom with the new 1.4b kernel it no longer works and yes I tried reflashing and wiping a few times. Any ideas?
Hey could you make me one and either PM me or post it up?
I'm on CM7 on a Nexus S, and I don't see a '/system/etc/spn-conf.xml' file. It doesn't seem to exist on mine. I'm on the latest nightly (#8) and have updated everything. Am I missing something?
How exactly did you get these files? I'm having all sorts of trouble with this. First off, the optable.db file is zero K, even when I extract it through ASTRO or Root Explorer with R/W permissions. Secondly, as I mentioned in the last post, the 3rd file is missing from the stated directory.
I'm really confused, as it seems that none of these instructions add up for a Nexus S. I'd like my T-Mobile message to instead display "Nexus S: Pure Android, Pure Google"
Did not work on Modaco R9, CM7 or The Cracker builds...
nickmv said:
I'm on CM7 on a Nexus S, and I don't see a '/system/etc/spn-conf.xml' file. It doesn't seem to exist on mine. I'm on the latest nightly (#8) and have updated everything. Am I missing something?
Click to expand...
Click to collapse
spns-conf.xml does not exist on the Nexus S originally, but if you place it in /system/etc/ the OS knows to use it.
nickmv said:
How exactly did you get these files? I'm having all sorts of trouble with this. First off, the optable.db file is zero K, even when I extract it through ASTRO or Root Explorer with R/W permissions. Secondly, as I mentioned in the last post, the 3rd file is missing from the stated directory.
Use the optable.db from my zip and just edit it as you see fit.
I'm really confused, as it seems that none of these instructions add up for a Nexus S. I'd like my T-Mobile message to instead display "Nexus S: Pure Android, Pure Google"
Click to expand...
Click to collapse
I'm not sure what the character limit is but that might be too long.
I have all the files in the proper folders but it still doesn't work. Modaco R9
for those having problems getting this to work try using clockwork and press mount/storage then mount/system. hope this works.
tsalate said:
for those having problems getting this to work try using clockwork and press mount/storage then mount/system. hope this works.
Click to expand...
Click to collapse
You might be on to something, it worked for about 3 seconds then went right back to T-Mobile.
Still doesn't work. Mounted /system and /data. Does it only work for certain carriers? I'm using a&t
Is there a way to apply this to ALL carriers, rather than selecting one manually.
thanks
Hi, just got a NC today. Am a total noob to Android (no smartphone) and am hoping someone can help me out. I have read and searched a bit of the posts in these NC forums, but there is just A LOT and I'm kinda lost. To start out..
After playing around with the stock 1.2 ROM for a bit, I installed the latest nightly (177) CM7 with this guide,
http://forum.xda-developers.com/showthread.php?t=1030227
Before this, I also switched to the older 1/5GB app/data partition with DeanGibson's zips via CWM. The installs are fine, although CM7's UI is thoroughly confusing. My questions are:
By installing CM7, am I also rooted as part of the process? If not, is there any additional benefit to get root?
Is ManualNooter needed if I have CM7, or is it redundant? Can I install it on top of CM7?
I can't get most apps from the Market ("your device is not compatible"). I also went to Amazon.com to try and get its AppStore app, but it gives the same error. Is this a noob issue, or is there a real problem, and is there a workaround if the latter?
What's a simple way to access network shares on my Windows network?
Is there a way to dismount & remove the microSD w/o turning the NC off?
Links would be fine. TIA for any help.
You are rooted! You might want to install clock work mod from the market... I'm not sure about the computability issue as I have never had it myself.
Sent from my NookColor using XDA Premium App
If I'm understanding this correctly, you were able to go from completely stock to CM7 without rooting with manualnooter first? I'm buying a NC next week and i was unsure root was needed to go to CM7.
You are already rooted.
Market fixes: http://forum.xda-developers.com/showthread.php?t=1255689
Sent from my LG Optimus V using Tapatalk
@sevs753
Yes, apparently the CM7 install does the root thing for you. Still not quite sure if it's needed for anything else other than allowing custom ROMs.
I'm a little flustered with Android at the moment. Trying to edit the build.prop as some others have mentioned to temp fix the market problem, only to find that I can't download ES Explorer (what others are reportedly using) to edit the file. Was going to edit it in terminal emulator & nano, but found that the soft keyboard has no cursor keys. So I found an ES Explorer apk, and now am trying to figure out how to sideload the app--I believe that's the correct lingo for Android.
I also found that many embedded flash videos don't play (Youtube does). I thought this was a done deal with 2.3 and CM7, but apparently not. Tried to download Flash 10.3 from market, but again am blocked.
Am also trying to find the parameters of what is allowable for video playback for 2.3. For HC, you can play up to 720p and high profile H264 with "reasonable" params. I've been encoding various test clips, and it looks like the max is 854x480 at baseline profile, same as with the stock ROM.
Change your LCD density to 240 and your market will start working. It makes the icons really large but you get used to it. The best way to change the density is by editing the build.prop line that is default: qemu.sf.lcd_density=161
Change that 161 to 240 and then save your build.prop and reboot. Problem should then be solved.
I edit the build.prop with root explorer (Paid version) - you have to change from r/o to r/w first, then change back to r/o after you are done editing.
Shandon84321 said:
Change your LCD density to 240 and your market will start working. It makes the icons really large but you get used to it. The best way to change the density is by editing the build.prop line that is default: qemu.sf.lcd_density=161
Change that 161 to 240 and then save your build.prop and reboot. Problem should then be solved.
I edit the build.prop with root explorer (Paid version) - you have to change from r/o to r/w first, then change back to r/o after you are done editing.
Click to expand...
Click to collapse
That's quite a jump. Most people are changing to 160 which is also a standard density.
Until you really get familiar with the CM7 and the NC, I suggest you try CM7 off uSD card.
patruns said:
That's quite a jump. Most people are changing to 160 which is also a standard density.
Click to expand...
Click to collapse
With 160 you will be clearing Market app data daily for it to keep working. 240 seems to keep working... I guess because almost all phones are set to 240.
DizzyDen said:
With 160 you will be clearing Market app data daily for it to keep working. 240 seems to keep working... I guess because almost all phones are set to 240.
Click to expand...
Click to collapse
+1 on this. I was going forever on 240 without a hiccup.
Note that ICS has also been demonstrated to change the UI depending on the density, with 160 for a tablet UI (honeycomb-ish) and 240 for phone UI (gingerbread-ish). Came across a couple references showing that density was the only thing that needed to be changed to make this happen.
I kind of suspect this may be part of why density is becoming such a big issue. It also fits with the fact that tablet-related apps show up in the market at 160 but not at 240. Perhaps Google is setting market up ahead of ICS release to handle this?
skwalas said:
+1 on this. I was going forever on 240 without a hiccup.
Note that ICS has also been demonstrated to change the UI depending on the density, with 160 for a tablet UI (honeycomb-ish) and 240 for phone UI (gingerbread-ish). Came across a couple references showing that density was the only thing that needed to be changed to make this happen.
I kind of suspect this may be part of why density is becoming such a big issue. It also fits with the fact that tablet-related apps show up in the market at 160 but not at 240. Perhaps Google is setting market up ahead of ICS release to handle this?
Click to expand...
Click to collapse
If i remember correctly this also happens on Honeycomb.
Sent from my LG Optimus V using Tapatalk
You're at the same spot I was at earlier last week. I just got my NC, and read about and made the cm7 sd card. To get market working correctly this is what I did:
- installed cm7 and gapps using this guide - http://forum.xda-developers.com/showthread.php?t=1000957
- once that was working I went to the market and got titanium backup installed
- once that's installed, I went to applications/manage/market and force closed market, cleared the cache, and uninstalled updates
- then I went to titanium and found marketupdater.apk and uninstalled it
- after that I opened market again, if force closed once but opened fine the second time. I now have the old style market and everything seems to work well.
I haven't used manualrooter, I only followed the above guide. As for unmounting the card, I have no idea. I'm probably going to keep things as they are, I really like being able to turn the NC off, take the card out, and have it back as stock.
koopakid08 said:
If i remember correctly this also happens on Honeycomb.
Sent from my LG Optimus V using Tapatalk
Click to expand...
Click to collapse
I believe honeycomb had the capability built in but was not supposed to be enabled. Would have to dig around for links n such.
I just want to say thanks for all those who replied. I'm taking some time trying different stuff on the NC, now that I've gotten a basic handle on CM7. I'll be sure to try some of the tips & info proffered.
Re: Market issue - I tried w/ File Expert to change file.prop's attribs so I can edit them, but the changes don't take. Since the entire /system partition is RO, I'm assuming I need to remount it to RW before I can do anything to the files, per NookDev's instruction. Am further assuming I'll need to install the SDK so I can get ADB running.
@Kingston73: I'm sure there are apps that do it more efficiently, but mount/unmount SD is in Settings | Storage.
More questions:
Is there a way to not have a wallpaper and have the default black background changed to something else? I like having just a plain background.
I'm using the default browser for now. Most of the sites with embedded Flash don't work (no Flash installed). I tried installing Flash 10.3 from the Adobe site, but it gives the same error as Market's. Can 10.3 be installed into CM7 at all, or is this because of the LCD density issue (which I'll get around to fixing)?
Thanks again for all your help. Am learning both Android and CM7 as I go along.
Noob^2 said:
I just want to say thanks for all those who replied. I'm taking some time trying different stuff on the NC, now that I've gotten a basic handle on CM7. I'll be sure to try some of the tips & info proffered.
Re: Market issue - I tried w/ File Expert to change file.prop's attribs so I can edit them, but the changes don't take. Since the entire /system partition is RO, I'm assuming I need to remount it to RW before I can do anything to the files, per NookDev's instruction. Am further assuming I'll need to install the SDK so I can get ADB running.
@Kingston73: I'm sure there are apps that do it more efficiently, but mount/unmount SD is in Settings | Storage.
More questions:
Is there a way to not have a wallpaper and have the default black background changed to something else? I like having just a plain background.
I'm using the default browser for now. Most of the sites with embedded Flash don't work (no Flash installed). I tried installing Flash 10.3 from the Adobe site, but it gives the same error as Market's. Can 10.3 be installed into CM7 at all, or is this because of the LCD density issue (which I'll get around to fixing)?
Thanks again for all your help. Am learning both Android and CM7 as I go along.
Click to expand...
Click to collapse
Flash will install fine from the market if you are in the old market. It doesn't care about the density.
More questions:
Is there a way to not have a wallpaper and have the default black background changed to something else? I like having just a plain background.
Click to expand...
Click to collapse
You can set or remove wallpaper upon your will.
I'm using the default browser for now. Most of the sites with embedded Flash don't work (no Flash installed). I tried installing Flash 10.3 from the Adobe site, but it gives the same error as Market's. Can 10.3 be installed into CM7 at all, or is this because of the LCD density issue (which I'll get around to fixing)?
Click to expand...
Click to collapse
Flash 10.3 installed and worked w/o any issue with CM7.
If you can't download it directly from Market, try to sideload it.
Oh, and, recommend trying Opera browser
patruns said:
Flash will install fine from the market if you are in the old market. It doesn't care about the density.
Click to expand...
Click to collapse
Flash should install fine with the new market too, if density is at 160 (or 240) and market data is freshly cleared. It is possible that in some cases the market will update itself too quickly for the 160 fix to stick long enough to install, and this has happened to me on occasion. If installing the basic "problematic" apps (flash, facebook, repligo, maps, etc.) for the first time, would suggest working with 240 dpi to get all the apps on your nook, then revert to 160 if that is your preferred screen sizing going forward.
Thanks for the continuing tips. I did get Flash 10.3 to install via sideloading. I still can't get Market to lift its "partial-ban", since the only version I have is 3.1.3 and there is no rollback. I did manage to edit build.prop to 160, then 240, (and cleared cache) but the ban is still present. I think us Johnny-come-latelies are just a bit screwed until some shining knight comes through with a fix.
To relate my further misadventures with CM7 and Market, I'm recounting some of my steps, in hope that they'll help someone else.
Networking to Windows boxes: I used CIFS Manager, which worked straightaway. Before that, I tried the networking function of ES File Explorer and Astro (w/ SMB plugin), but they both crashed or hung.
Finding a good file manager: I tried File Expert, ES File Explorer, and Astro File Manager. They have more functions than CM7's built-in file mgr, but the built-in mgr is the fastest at reading off large directories from the network (which still isn't that fast). This is critical for me, since most of my media will be accessed via wifi.
Finding a better terminal emulator: The built-in one is kinda barebone. Looks like Better Terminal Emulator Pro is the only game in town?
Finding a better keyboard: Since I'm a commandline guy, Hacker's Keyboard fits the bill. Well, at least until my BT keyboard arrives.
Getting USB HDD/key to work: Ordered a Tekkeon TekCharge MP1550 4xAA batt pack and a Y-cable, along with a 90-degree micro-USB cable.
Install font for Viet or any language not already on CyanogenMod 7:
I have a collection of Viet songs/movies, and most of them have UTF-8 filenames. I used this below to change the font so CM7 can see the files (it's also what I used to edit build.prop). There are easier ways to do this, but here you don't need to install anything else.
1. Get DejaVu Fonts from dejavu-fonts.org (personally, I used Arial.ttf from my Windows box since I know it covers Viet)
2. Get DejaVuSans.ttf and rename to DroidSansFallback.ttf
3. Copy DroidSansFallback.ttf to root dir of SD card
4. Insert SD card into NC and mount it (Settings | Storage)
5. Run Terminal Emulator
6. Enter su (confirm when asked) (all commands case-sensitive)
7. Enter mount. Note device node & FS for /system. For CM7, it's /dev/block/mmcblk0p5 /system ext4 (ro[...])
8. Enter mount -o rw,remount -t ext4 /dev/block/mmcblk0p5 /system (node & FS must match)
9. Enter mount again to check, it should read /dev/block/mmcblk0p5 /system ext4 (rw[...])
10. Enter chmod 4755 /system/fonts/DroidSansFallback.ttf
11. Enter dd if=/sdcard/DroidSansFallback.ttf of=/system/fonts/DroidSansFallback.ttf
12. Reboot. File and partition permissions should return to default.
I found that local UTF8 filenames are recognized, but not files over the network. After some hair pulling and a bunch more Googling, I stumbled on the extra needed step.
13. Unmount the CIFS share in CIFS Manager. Long-press to edit the share, enter iocharset=utf8 in the Options box. Save and remount.
Other apps chosen: EzPDF for PDFs, Aldiko for ePubs, FBReader for Mobis, PerfectViewers for CBRs, OverDrive for library checkouts, MoboPlayer for SD MKVs (doesn't work for AVI/XviD).
To-Do's:
. Try Opera like another had suggested. The default browser is pretty limited.
. Check out some of the compilers & editors for Android.
. Find a decent office suite.
Question:
. I'm having trouble with file associations with the built-in file mgr (am assuming it is part of ADW). The association is lost after a few files, and apparently it associates all file types in the share with the single app, regardless of extension. Is this an ADW issue, or did I just miss a setting somewhere?
Noob^2 said:
Thanks for the continuing tips. I did get Flash 10.3 to install via sideloading. I still can't get Market to lift its "partial-ban", since the only version I have is 3.1.3 and there is no rollback. I did manage to edit build.prop to 160, then 240, (and cleared cache) but the ban is still present. I think us Johnny-come-latelies are just a bit screwed until some shining knight comes through with a fix.
Click to expand...
Click to collapse
Are you actually clearing the market data specifically? if you're just clearing cache (such as through rom manager), that's a completely different thing and won't fix the problem. You need to clear the application data for the market specifically.
Would be seriously odd that you couldn't get the apps. Note that if you've flashed gapps through rom manager, it should install the old market. selecting "uninstall updates" in the application manager screen for the market should take you back to that old market, but it will update very quickly unless the market updater apk is already disabled.
To get missing ("incompatible") apps to show up in the Market you will need to edit your build.prop.
You will need root (unlock your bootloader at htcdev.com) and Root Explorer (can do it through adb but Root Explorer is easier).
Open Root Explorer and go to /system and find build.prop. Long press on it and choose Open in Text Editor. Find these lines
ro.product.model=PH39100
ro.aa.modelid=PH3910000
ro.product.brand=cingular_us
ro.product.name=htc_holiday
ro.product.device=holiday
ro.product.board=holiday
and change them to
ro.product.model=HTC Pyramid
ro.aa.modelid=PG5811000
ro.product.brand=htc_wwe
ro.product.name=htc_pyramid
ro.product.device=pyramid
ro.product.board=pyramid
Press the Menu key, Save and Exit. Reboot.
I'm on RumRaider Beta 10 so I'll upload my build.prop if you want to just copy/paste it over your current one.
http://www.multiupload.com/YAMH40C8LW
EDIT:
Apparently, modifying this line
ro.product.device=holiday
Click to expand...
Click to collapse
Is causing issues with the camera making it take shots/recocrd in blue. So, I recommend still following the directions above, but only modify ro.product.device=holiday when you need to update/download apps and once done, change it back to ro.product.device=holiday to use the camera again.
Do not use these settings if you own a rogers/Bell HTC raider! Changing them will turn all of your X710a's pictures/video blue! I can not speak for other versions of the raider but the x710a is affected. I just figured this out after playing with all the settings in the camera app, and I even contemplated calling HTC!!! I had to revert the values back to original to get the camera to work normally.
Hmm, I noticed that issue to but just thought it was the Rom. That's interesting. Anyways, I fiddled around with the settings and discovered that it was this line that messing up the camera
ro.product.device=pyramid
So I'd recommend the switching this back to 'holiday' and when you need/want to download (or update) an app, simply switch this back to 'pyramid' and when your done restore it back to holiday.
What are the apps that we are expected to gain? Can you give us an idea what we are missing out on?
You can't know your limits until you exceed them.
The apps I gained were GTA3, Order and Chaos Online, Snapdragon GameCommand, and Desert Winds.
has anyone tried playing order and chaos after changing the file name back to correct the camera issue? I have read elsewhere that the game will give you issues on rooted devices
Spartoi said:
To get missing ("incompatible") apps to show up in the Market you will need to edit your build.prop.
You will need root (unlock your bootloader at htcdev.com) and Root Explorer (can do it through adb but Root Explorer is easier).
Open Root Explorer and go to /system and find build.prop. Long press on it and choose Open in Text Editor. Find these lines
ro.product.model=PH39100
ro.aa.modelid=PH3910000
ro.product.brand=cingular_us
ro.product.name=htc_holiday
ro.product.device=holiday
ro.product.board=holiday
and change them to
ro.product.model=HTC Pyramid
ro.aa.modelid=PG5811000
ro.product.brand=htc_wwe
ro.product.name=htc_pyramid
ro.product.device=pyramid
ro.product.board=pyramid
Press the Menu key, Save and Exit. Reboot.
I'm on RumRaider Beta 10 so I'll upload my build.prop if you want to just copy/paste it over your current one.
http://www.multiupload.com/YAMH40C8LW
EDIT:
Apparently, modifying this line
Is causing issues with the camera making it take shots/recocrd in blue. So, I recommend still following the directions above, but only modify ro.product.device=holiday when you need to update/download apps and once done, change it back to ro.product.device=holiday to use the camera again.
Click to expand...
Click to collapse
This method doesn't seem to work anymore.. in the play store it will still list it as incompatible.. unless there is something else needed to be done?
DXMD3 Stock Jelly Bean Phabletized!
DISCLAIMER TIME:
First thing's first: I am not a chef, nor am I a developer of any sort. This was just an experiment and it worked. All I'm doing is sharing the results and the method of achieving them.
Also, I am in no way responsible if you mess up your device. That said, these modifications are mostly harmless and reversible, if you follow the instructions to the letter. (Worst case scenario: You flash stock JB again or restore a nand backup and you're safe.)
Oh and your device must be rooted. You can't go around changing things if it's not.
I do need a bit of help with some things, you can read the help wanted section at the bottom of the post,
If you're still interested, read on.
INTRO SPEECH:
I've always wanted the phablet experience on my 7.7, but all of the roms I've tried had imperfections (if ever so slight). If any developers are reading this, please do not take this as an insult. Your roms are wonderful masterpieces. I admit I couldn't even begin to understand how much knowledge and hard work is poured into them. I just wanted a 100% daily driver to have and to hold, meaning as few updates as possible (oh the irony). The closest I could find to a perfect rom was the PAC rom by @daniel_hk, but it always started acting out after a couple of weeks. Might have also been my apps or a combination of apps that did this, I don't know. The customization options on PAC are… It's simply amazing. If you're up for it, do check it out in the development thread. Out of all the roms I've tried, I liked PAC the best. That was a message from our (non)sponsors (my personal opinion). Then I tried E-Robot, which is almost stock – I'd say it's a Note 8 rom modified for our 7.7. But it still didn't feel right. I went back to the stock JB rom and started thinking I could simply alter build.prop's dpi setting and get phablet on stock JB. I was half-right. I did alter it and got phablet mode, but a lot of apps stopped working, a few of them crucial (phone, contacts, …). So I started replacing those apps with apps from the E-Robot rom. And it worked. I've identified and replaced most of the apps and the rom is very smooth. I dare say it's even smoother than E-Robot.
List of apps that need replacing:
- Accuweather
- Most mini apps
- Pen memo
- Camera
- Gallery
- Calculator
- S Planner / Calendar
- Phone
- Contacts
- TouchWiz Launcher
- Task manager
- Memo (text memo)
List of apps I haven't yet found replacements for (HELP WANTED, see below):
- Samsung keyboard
- Reader's hub
APPS YOU'LL NEED:
I like ES File Explorer the most, you can use other file managers if you like. LINK
I find it easiest to flash roms with Mobile ODIN. LINK
If you're not interested in purchasing Mobile Odin, you can look it up on XDA forums. It's available for free.
7zip. You'll need to unzip the package. LINK
APP SUBSTITUTION PACKAGE:
LINK
Please, do not mirror this as these instructions are not yet 100% complete.
INSTRUCTIONS:
Read first. Then apply.
1) Get the stock DXMD3 Jelly Bean on www.samfirmware.com
2) I can't stress this enough: Back up all of your files on your internal storage. All of them. I will not be blamed for the loss your lolcat collection.
3) Flash it with Mobile Odin and choose to root the rom and inject superuser
4) A custom recovery is probably a good idea. Use either CWM or TWRP and make a full system backup. Just in case. Easiest to flash with Odin.
5) Unzip the "PHABLETIZE!" package to your tablet internal storage.
6) Default home to a custom launcher. Just in case. I used Apex. (You'll be replacing TouchWiz, remember?) Also, Install a custom keyboard. The stock keyboard isn't happy with 213dpi. I use Jelly Bean Keyboard.
7) Turn on "Root Explorer" mode in ES File Explorer (side menu, accessible from the top left bluish globe icon)
7a) Alternatively, you can use LCDDensity from Play. I haven't tested this personally. This is a recommendation from obbeguin. Skip step 8.
8) Make a backup of your build.prop file. Edit the build.prop to be used by the system (/system/build.prop): "ro.sf.lcd_density=160" changed to "ro.sf.lcd_density=213" (the one between rild.libargs and ro.lcd_brightness)
9) Restart and marvel at the half-finished glory of phablet mode.
10) Here is where you would see TouchWiz crash and you'd be stuck if you hadn't defaulted to a custom launcher in step 6. Luckily, you did.
11) Open ES, navigate to /system/app/ and start replacing the apps from the package. Yes, manually. I don't know how to make a CWM flashable package, so again, yes, manually. (HELP WANTED) I'd also recommend backing up the original files (just copy them to a backup folder on your storage). All apps should replace just fine, since they crash when launched anyway. You should also backup and delete their odex counterparts. Do not replace those.
12) I haven't included the camera and gallery apks. The gallery wasn't working well and I found a replacement here. Not sure yet if I can hijack his files to use in my zip so I'm posting a link for the time being. Also, I've found I like the SGS4 dialer and messaging app much better than the tablet apps from Note8. Look for it here.
13) Restart
14) If you have any issues with any of the apps, first try clearing their caches and data or wiping dalvik cache and cache in recovery mode.
I'd also recommend SkyHigh's custom kernel. I like it and it allows me to use ExFat on my external SD card. It's no NTFS, but large files (>4GB) get across just fine and it works on my computer and in my tablet without a hitch.
And for that extra "Startled Android" effect, I went with Xposed framework and per-app dpi settings. Not quite paranoid but does the job ok.
If you like the Samsung keyboard, you might want to give this one a go. Suggested by @stenny
HELP WANTED SECTION:
As written before, I need some help. It would be tons easier to just flash a CWM package over the stock JB and get phablet mode. Trouble is, I can't build it. Getting around to this one. Got around to it. Now I'm having scripting problems. If anyone is script savvy, please check out the code below.
I have no clue where to find a replacement Reader's hub app – one that works on 213dpi instead of 160dpi If anyone knows where I could find it, please leave a comment.
Don't hesitate to leave your feedback in the comments.
Unhide to see the script code.
#!/sbin/sh
# remove old backup
[ -d /sdcard/phabletize/backup ] && rm -r /sdcard/phabletize/backup
# backing up original apk
echo "Backing up /system/app/"
busybox mkdir -p /sdcard/phabletize/backup/system/app
busybox mkdir -p /sdcard/phabletize/system/app
cd /sdcard/phabletize/list/
for f in $(ls)
do
echo "Processing $f"
busybox cp /system/app/$f /sdcard/phabletize/backup/system/app/
busybox rm /system/app/$f
done
echo "Backups done for system apps"
# backing up original build.prop
echo "Backing up /system/build.prop"
cp /system/build.prop /sdcard/phabletize/backup/system/build.prop
echo "Backup done for build.prop"
# delete odex files and old apk files
echo "Deleting original odex and apk files from /system/app"
cd /sdcard/phabletize/list
for f in $(ls)
do
echo "Processing $f"
busybox rm /system/app/$f
done
echo "Original odex and apk files deleted. Don't worry. You still have your backup."
# for each of the system apps needing processed
echo "Copying modified apks to /system/app"
cd /sdcard/phabletize/system/app
cp -p * /system/app
echo "Finished copying modified apks"
# copy modified build.prop
echo "Copying modified build.prop to /system"
cd /sdcard/phabletize/system
cp -p build.prop /system
echo "Finished copying modified build.prop"
# the end
echo "All done. Enjoy you Phabletized 7.7 JB"
The above left my tablet in a bootloop stuck on the bootanimation turned landscape and distorted/stretched. I was trying to accomplish the following: back up the original apks and build.prop file to a folder on the sdcard. The list of apks needing backups would be determined from the list of apks in the replacement folder. And copying the replacement apks and build.prop file to the proper folder in /system.
I hope I've proofread this enough times so that it's decent...
Screenshots:
They're big. There are many, Unhide to see.
Mostly just showing off the Samsung apps. From my experience, most apps are a lot easier to handle on a bigger dpi. Again, if on some apps you don't like the change...go with Xposed framework.
Undoubtedly you'll notice how the fonts in the Settings app seem smaller than the rest of the rom and the alarm clock app seems bigger. You're right. They are. That's Xposed + App settings hard at work. I want the alarm clock buttons big when I'm smacking the **** out of my tab in the morning (300dpi) and don't need the big fonts when I'm fiddling with the settings (160dpi).
By the way, don't mind the "25% brightness" (I had it at -28% on some other screenshot). That's just Lux. It helps keep the display at a comfortable level in the dark. A screen filter basically. I also found this and this very helpful on a big screen and fiddly-sometimes-hard-to-press-when-your-hands-are-messy-when-cooking-and-just-need-to-look-at-the-recipe-one-more-time buttons (the other two persistent notifications).
Coming soon: Flashable zip. I'll get around to it, I promise. Having trouble scripting the thing. Take a look at the help wanted section if you think you can help. Thanks.
It is wonderful seeing someone try to create something for our Tablets...
I wish I could help in your efforts but instead I can only thank and applause you...
Good luck...
actually... e-robot doing the same thing that you're doing... replacing the apk from note 8.0 to 7.7 but they did alter some apk to fit their mod.
btw. you can use the keyboard from e-robot as well. but you need to find all related lib files to make it work on 7.7
Conserning cwm flashable zips... I don't know the syntax either. But I just use a zip from gapps and delete all the contents and modify the outputted text. Don't use a zip from a rom because they often wipe stuff.
Sent from my GT-p6800 using xda app-developers app
Lemme start by giving you a well deserved thanks and excellent job.
Can you maybe post a few screenshots and maybe even a video of you have time?
Sent from my GT-P6800 using xda app-developers app
zip
You can use the app "app2zip". It shows you all installed apps, then you choose yours from your pack and
click create. This zip file is then flashable in the recovery.
edan1979 said:
actually... e-robot doing the same thing that you're doing... replacing the apk from note 8.0 to 7.7 but they did alter some apk to fit their mod.
btw. you can use the keyboard from e-robot as well. but you need to find all related lib files to make it work on 7.7
Click to expand...
Click to collapse
Doesn't e-robot have some issues? I got the distinct feeling it wasn't quite so stock. I might be wrong though.
EDIT: Now I remember! I couldn't get over the flickering wifi icon in the status bar. Annoyed the **** out of me. Trivial, I know. I could live with something not working quite right if it wasn't visible most of the time.
{Diemex} said:
Conserning cwm flashable zips... I don't know the syntax either. But I just use a zip from gapps and delete all the contents and modify the outputted text. Don't use a zip from a rom because they often wipe stuff.
Sent from my GT-p6800 using xda app-developers app
Click to expand...
Click to collapse
Good tip. Thanks!
vivalamoza said:
Lemme start by giving you a well deserved thanks and excellent job.
Can you maybe post a few screenshots and maybe even a video of you have time?
Sent from my GT-P6800 using xda app-developers app
Click to expand...
Click to collapse
I'll take some and post asap.
konsolen said:
You can use the app "app2zip". It shows you all installed apps, then you choose yours from your pack and
click create. This zip file is then flashable in the recovery.
Click to expand...
Click to collapse
Can this create a single zip for multiple apps or is it one app = one zip?
It creates one ZIP file. So exactly what you looking for.
Just a quick update:
I'm working on a cwm flashable zip that would back up the original apk and odex files and copy the new ones in place. Plus, I've been toying around with other versions of system apps.
I will be posting everything in the next few days - after I test it out.
Cheers
paranoiadk said:
DXMD3 Stock Jelly Bean Phabletized!
INSTRUCTIONS:
Read first. Then apply.
1) Get the stock DXMD3 Jelly Bean on www.samfirmware.com
2) I can't stress this enough: Back up all of your files on your internal storage. All of them. I will not be blamed for the loss your lolcat collection.
3) Flash it with Mobile Odin and choose to root the rom and inject superuser
4) A custom recovery is probably a good idea. Use either CWM or TWRP and make a full system backup. Just in case. Easiest to flash with Odin.
5) Unzip the "PHABLETIZE!" package to your tablet internal storage.
6) Default home to a custom launcher. Just in case. I used Apex. (You'll be replacing TouchWiz, remember?) Also, Install a custom keyboard. The stock keyboard isn't happy with 213dpi. I use Jelly Bean Keyboard.
7) Turn on "Root Explorer" mode in ES File Explorer (side menu, accessible from the top left bluish globe icon)
8) Make a backup of your build.prop file. Edit the build.prop to be used by the system (/system/build.prop): "ro.sf.lcd_density=160" changed to "ro.sf.lcd_density=213" (the one between rild.libargs and ro.lcd_brightness)
9) Restart and marvel at the half-finished glory of phablet mode.
10) Here is where you would see TouchWiz crash and you'd be stuck if you hadn't defaulted to a custom launcher in step 6. Luckily, you did.
11) Open ES, navigate to /system/app/ and start replacing the apps from the package. Yes, manually. I don't know how to make a CWM flashable package, so again, yes, manually. (HELP WANTED) I'd also recommend backing up the original files (just copy them to a backup folder on your storage). All apps should replace just fine, since they crash when launched anyway. You should also backup and delete their odex counterparts. Do not replace those.
12) Restart
13) If you have any issues with any of the apps, first try clearing their caches and data.
Click to expand...
Click to collapse
Concerning the point 7 & 8, wouldnt it be easier to just use LCDDensity for root ?
Using it, it is must more easy to change the density without even having to manually modify the build.prop file... And the phablet mod start for any density higher than 180..
And for people who forgot to install a second launcher, they no need to panic..
They can still go to the tablet settings using the notification bar, even if Touchwiz doesnt work.
There, they can check they are connected to internet and install a second launcher by logging on google play by using a PC.
obeguin said:
Concerning the point 7 & 8, wouldnt it be easier to just use LCDDensity for root ?
Using it, it is must more easy to change the density without even having to manually modify the build.prop file... And the phablet mod start for any density higher than 180..
And for people who forgot to install a second launcher, they no need to panic..
They can still go to the tablet settings using the notification bar, even if Touchwiz doesnt work.
There, they can check they are connected to internet and install a second launcher by logging on google play by using a PC.
Click to expand...
Click to collapse
Never heard of LCDDensity before, but I'll add it to the instructions.
You're correct, the phablet ui starts at 180 (176 I believe), but the navigation bar keys are off center when lcd density is not set to 213.
Sort of defeats the purpose of phablet ui for me. Personally, I changed to a smaller dpi (for a smaller status bar - 195) and removed the navigation bar with the qemu.hw.mainkeys switch. I mainly navigate thru gestures (using GMD Gesture Control) anyway.
Again, you're correct. But when starting out on a freshly flashed rom, some might happen to skip the part where they connect to the wifi or connect their google account. Besides, I've seen Play being hesitant to install and update on it's own - sometimes it requires you to launch it before you get update notifications and automated app downloads which requires a launcher. I want the instructions to be as foolproof as possible. That's why I'll be making a separate flashable zip with a custom home and keyboard, just in case.
On that topic, do you know anything about scripting? I'm having trouble with the update script. Check out the first post.
You can try this note 8 samsung keyboard, it work on both tablet and phablet ui.
http://forum.xda-developers.com/showthread.php?t=2228836
Sent from my GT-P6800 using XDA Premium 4 mobile app
paranoiadk said:
DXMD3 Stock Jelly Bean Phabletized!
DISCLAIMER TIME:
First thing's first: I am not a chef, nor am I a developer of any sort. This was just an experiment and it worked. All I'm doing is sharing the results and the method of achieving them.
Also, I am in no way responsible if you mess up your device. That said, these modifications are mostly harmless and reversible, if you follow the instructions to the letter. (Worst case scenario: You flash stock JB again or restore a nand backup and you're safe.)
Oh and your device must be rooted. You can't go around changing things if it's not.
I do need a bit of help with some things, you can read the help wanted section at the bottom of the post,
If you're still interested, read on.
INTRO SPEECH:
I've always wanted the phablet experience on my 7.7, but all of the roms I've tried had imperfections (if ever so slight). If any developers are reading this, please do not take this as an insult. Your roms are wonderful masterpieces. I admit I couldn't even begin to understand how much knowledge and hard work is poured into them. I just wanted a 100% daily driver to have and to hold, meaning as few updates as possible (oh the irony). The closest I could find to a perfect rom was the PAC rom by @daniel_hk, but it always started acting out after a couple of weeks. Might have also been my apps or a combination of apps that did this, I don't know. The customization options on PAC are… It's simply amazing. If you're up for it, do check it out in the development thread. Out of all the roms I've tried, I liked PAC the best. That was a message from our (non)sponsors (my personal opinion). Then I tried E-Robot, which is almost stock – I'd say it's a Note 8 rom modified for our 7.7. But it still didn't feel right. I went back to the stock JB rom and started thinking I could simply alter build.prop's dpi setting and get phablet on stock JB. I was half-right. I did alter it and got phablet mode, but a lot of apps stopped working, a few of them crucial (phone, contacts, …). So I started replacing those apps with apps from the E-Robot rom. And it worked. I've identified and replaced most of the apps and the rom is very smooth. I dare say it's even smoother than E-Robot.
List of apps that need replacing:
- Accuweather
- Most mini apps
- Pen memo
- Camera
- Gallery
- Calculator
- S Planner / Calendar
- Phone
- Contacts
- TouchWiz Launcher
- Task manager
- Memo (text memo)
List of apps I haven't yet found replacements for (HELP WANTED, see below):
- Samsung keyboard
- Reader's hub
APPS YOU'LL NEED:
I like ES File Explorer the most, you can use other file managers if you like. LINK
I find it easiest to flash roms with Mobile ODIN. LINK
If you're not interested in purchasing Mobile Odin, you can look it up on XDA forums. It's available for free.
7zip. You'll need to unzip the package. LINK
APP SUBSTITUTION PACKAGE:
LINK
Please, do not mirror this as these instructions are not yet 100% complete.
INSTRUCTIONS:
Read first. Then apply.
1) Get the stock DXMD3 Jelly Bean on www.samfirmware.com
2) I can't stress this enough: Back up all of your files on your internal storage. All of them. I will not be blamed for the loss your lolcat collection.
3) Flash it with Mobile Odin and choose to root the rom and inject superuser
4) A custom recovery is probably a good idea. Use either CWM or TWRP and make a full system backup. Just in case. Easiest to flash with Odin.
5) Unzip the "PHABLETIZE!" package to your tablet internal storage.
6) Default home to a custom launcher. Just in case. I used Apex. (You'll be replacing TouchWiz, remember?) Also, Install a custom keyboard. The stock keyboard isn't happy with 213dpi. I use Jelly Bean Keyboard.
7) Turn on "Root Explorer" mode in ES File Explorer (side menu, accessible from the top left bluish globe icon)
7a) Alternatively, you can use LCDDensity from Play. I haven't tested this personally. This is a recommendation from obbeguin. Skip step 8.
8) Make a backup of your build.prop file. Edit the build.prop to be used by the system (/system/build.prop): "ro.sf.lcd_density=160" changed to "ro.sf.lcd_density=213" (the one between rild.libargs and ro.lcd_brightness)
9) Restart and marvel at the half-finished glory of phablet mode.
10) Here is where you would see TouchWiz crash and you'd be stuck if you hadn't defaulted to a custom launcher in step 6. Luckily, you did.
11) Open ES, navigate to /system/app/ and start replacing the apps from the package. Yes, manually. I don't know how to make a CWM flashable package, so again, yes, manually. (HELP WANTED) I'd also recommend backing up the original files (just copy them to a backup folder on your storage). All apps should replace just fine, since they crash when launched anyway. You should also backup and delete their odex counterparts. Do not replace those.
12) I haven't included the camera and gallery apks. The gallery wasn't working well and I found a replacement here. Not sure yet if I can hijack his files to use in my zip so I'm posting a link for the time being. Also, I've found I like the SGS4 dialer and messaging app much better than the tablet apps from Note8. Look for it here.
13) Restart
14) If you have any issues with any of the apps, first try clearing their caches and data or wiping dalvik cache and cache in recovery mode.
I'd also recommend SkyHigh's custom kernel. I like it and it allows me to use ExFat on my external SD card. It's no NTFS, but large files (>4GB) get across just fine and it works on my computer and in my tablet without a hitch.
And for that extra "Startled Android" effect, I went with Xposed framework and per-app dpi settings. Not quite paranoid but does the job ok.
If you like the Samsung keyboard, you might want to give this one a go. Suggested by @stenny
HELP WANTED SECTION:
As written before, I need some help. It would be tons easier to just flash a CWM package over the stock JB and get phablet mode. Trouble is, I can't build it. Getting around to this one. Got around to it. Now I'm having scripting problems. If anyone is script savvy, please check out the code below.
I have no clue where to find a replacement Reader's hub app – one that works on 213dpi instead of 160dpi If anyone knows where I could find it, please leave a comment.
Don't hesitate to leave your feedback in the comments.
Unhide to see the script code.
#!/sbin/sh
# remove old backup
[ -d /sdcard/phabletize/backup ] && rm -r /sdcard/phabletize/backup
# backing up original apk
echo "Backing up /system/app/"
busybox mkdir -p /sdcard/phabletize/backup/system/app
busybox mkdir -p /sdcard/phabletize/system/app
cd /sdcard/phabletize/list/
for f in $(ls)
do
echo "Processing $f"
busybox cp /system/app/$f /sdcard/phabletize/backup/system/app/
busybox rm /system/app/$f
done
echo "Backups done for system apps"
# backing up original build.prop
echo "Backing up /system/build.prop"
cp /system/build.prop /sdcard/phabletize/backup/system/build.prop
echo "Backup done for build.prop"
# delete odex files and old apk files
echo "Deleting original odex and apk files from /system/app"
cd /sdcard/phabletize/list
for f in $(ls)
do
echo "Processing $f"
busybox rm /system/app/$f
done
echo "Original odex and apk files deleted. Don't worry. You still have your backup."
# for each of the system apps needing processed
echo "Copying modified apks to /system/app"
cd /sdcard/phabletize/system/app
cp -p * /system/app
echo "Finished copying modified apks"
# copy modified build.prop
echo "Copying modified build.prop to /system"
cd /sdcard/phabletize/system
cp -p build.prop /system
echo "Finished copying modified build.prop"
# the end
echo "All done. Enjoy you Phabletized 7.7 JB"
The above left my tablet in a bootloop stuck on the bootanimation turned landscape and distorted/stretched. I was trying to accomplish the following: back up the original apks and build.prop file to a folder on the sdcard. The list of apks needing backups would be determined from the list of apks in the replacement folder. And copying the replacement apks and build.prop file to the proper folder in /system.
I hope I've proofread this enough times so that it's decent...
Click to expand...
Click to collapse
Didn't work for me, lots of apps couldn't be pasted in system/app even after R/W, I even tried to do it in TWRP and it still failed
vivalamoza said:
Didn't work for me, lots of apps couldn't be pasted in system/app even after R/W, I even tried to do it in TWRP and it still failed
Click to expand...
Click to collapse
My suggestions:
You sure you're rooted?
You might have free space issues. Try disabling and uninstalling the apps from titanium backup and then pasting the apps in place. Samsung roms are pretty huge and fill the available space almost to the limit.
Pasting sometimes didn't work for me when the apps were running. Try closing them from a task manager. I always did the modding after a fresh boot on a fresh rom.
I hope this is helpful.