What is the deal with voodoo?
Why would you want to disable a "fix"?
It sounds like "lagfix" would be something you'd not want to disable, but it seems to be something that most people disable.
Can anyone explain that one to me?
How much searching have you done? I'm pretty sure lagfix has been discussed a bunch of times.
... the lagfix is due to Samsung's proprietary RFS file system.
The "Voodoo Lagfix" changes the existing file structure and essentially makes the OS and I/O run smoother/faster.
People only disable it to be able to flash another ROM... although it is arguably easier to just flash back to stock and install the new ROM.
You may also want to disable the lagfix if you are looking to change the kernel or a theme. In normal use of the rom, no you would not want to disable
Sent from my SAMSUNG-SGH-I897 using XDA App
I'm having problems flashing fonts on my Thunderbolt. On my Eris and Incredible I could flash any font pack through CWM and Amon RA, respectively, but when I tried last night on my Bolt none of the fonts took. I made sure the font packs I flashed were edify fonts, but still no dice. One of my main reasons for rooting is because I hate the stock android font. Can someone please help me out with this? Thanks in advance
This is the link I got my fonts from in case anyone was wondering
http://forum.xda-developers.com/showpost.php?p=12024866&postcount=1006
Try using an app called absolute system from the market ...that's what I used on my dinc and it worked just fine
rusty2663 said:
Try using an app called absolute system from the market ...that's what I used on my dinc and it worked just fine
Click to expand...
Click to collapse
Was kinda hoping for a free way and a reason why manually flashing fonts isn't working on the TB. Thanks for the app, though, if i get desperate I'll d/l it. I hope someone smarter than me can come in here and help a brotha out
WormDoes said:
I'm having problems flashing fonts on my Thunderbolt. On my Eris and Incredible I could flash any font pack through CWM and Amon RA, respectively, but when I tried last night on my Bolt none of the fonts took. I made sure the font packs I flashed were edify fonts, but still no dice. One of my main reasons for rooting is because I hate the stock android font. Can someone please help me out with this? Thanks in advance
This is the link I got my fonts from in case anyone was wondering
http://forum.xda-developers.com/showpost.php?p=12024866&postcount=1006
Click to expand...
Click to collapse
I used to use these fonts, also, and could not get them to work now.......so I unzipped the file and pushed the 3 files to /system/fonts.....rebooted and I am good to go. By doing it that way, it does not matter if they are edify or amend.
Just use Font Changer, it's free AND it WORKS =P
wwjdd44 said:
I used to use these fonts, also, and could not get them to work now.......so I unzipped the file and pushed the 3 files to /system/fonts.....rebooted and I am good to go. By doing it that way, it does not matter if they are edify or amend.
Click to expand...
Click to collapse
That sounds awesome, but I don't know how to do that. I've been using font changer which is free on the market. I'd rather be able to flash them, because flashing things is great and it feeds the addiction, but this gets the job done
try typefresh on the market, only thing it does is back up and restore fonts... unfortunately requires AndExplorer to select fonts to restore but will back up all on its own... I actually like AndExplorer but use RootExplorer most of the time, AndExplorer has a more pleasing GUI however
i just used typefresh to install coconut-darkstar font (the most elegant font anywhere IMO) - worked great. was stuck at "rebooting..." after selecting the font so had to reboot manually but everything flashed fine. as posted earlier it required andexplorer but thats free in the market too.
0mie said:
Just use Font Changer, it's free AND it WORKS =P
Click to expand...
Click to collapse
font changer worked for me too, flashed a few different fonts to find one i liked. just do yourself a favor and hit reboot later when the app prompts you then reboot your phone via other means, the app's reboot function locked up my phone and had to pull the battery.
Anyone know what the default font for our phones are in case I want to go back?
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.
im having this problem since i upgrade to JB 4.1.2 i have try using many rom such as stock JB, JellyMOD, PureVanilla, and SlimJB. but every rom i use have this problem. so i guess its not the rom maybe, correct me. i also have try different kernel like cocore e5.0, 5.6.2, 6.0, 6.2 but still this problem exist. anybody know how to fix this?
extra info:
-moved app/game using app2sd and link2sd, app moved to sd still disappear after reboot.
-reboot, turn off, turn off + pull battery. still wont appear
-try using different launcher, adw, apex, touchwiz, still wont appear
-maybe setcpu or no-frill cpu have side effect?
-baseband dxamd1
-dpi 160
-swapped vold.stfab(dont know how to spell)
-with or without crossbreeder, wont appear also
after several frustrating hour try to figuring it out. i found what cause this to happen. its the storage swap, the vold.fstab. after swapping usb storage with sdcard. any app and games move to it will disappear after reboot. well i dont know why. do anybody know how to fix it?
I faced that problem but can solve by moving it to device memory using stock application manager.mostly games and also photo wounder too
Sent from my GT-I9070 using xda premium
Reply
SadvanceS said:
im having this problem since i upgrade to JB 4.1.2 i have try using many rom such as stock JB, JellyMOD, PureVanilla, and SlimJB. but every rom i use have this problem. so i guess its not the rom maybe, correct me. i also have try different kernel like cocore e5.0, 5.6.2, 6.0, 6.2 but still this problem exist. anybody know how to fix this?
extra info:
-moved app/game using app2sd and link2sd, app moved to sd still disappear after reboot.
-reboot, turn off, turn off + pull battery. still wont appear
-try using different launcher, adw, apex, touchwiz, still wont appear
-maybe setcpu or no-frill cpu have side effect?
-baseband dxamd1
-dpi 160
-swapped vold.stfab(dont know how to spell)
-with or without crossbreeder, wont appear also
Click to expand...
Click to collapse
reflash your stock rom with odin. I never try that swap memory thingy because it can affect my applications.
Dear helpful XDA-devs,
I ran into some weird display bugs which I did not experienced before. I've had the N5 and other phones and did often change my dpi without any side effect. However when I did it with my new Nexus 6 now I discovered some icons in the Play Store and "Locus Maps", for example, being oversized (see attachments).
What I did was to try to change my DPI using "Texdroider DPI" which let to an instant bootloop. So I reflashed /system from the stock image. Then I used the Nexus Root Toolkit to change the dpi via adb, what I thought worked perfectly back then (I changed it from default 560 to 530 in the end but tried a few other values as well). However, now I discovered these weird display issues in these two and one or two other apps. Any ideas what might be the reason, if it is DPI related at all, or if it worked fine when you did it yourself? Changing it back to default now does not solve the issue for me now, of course.
I'm on MOB30I, by the way. And I use TWRP+SuperSU on it. I did allow TWRP to make the /system partition writable to prevent Android from replacing TWRP. Might that be a reason why the adb-DPI-change let to bugs? Thanks for the help! :good:
To prevent people messing with the dpi many apps and Google are hard coding the sizes into the apks. I would just leave the dpi stock
zelendel said:
To prevent people messing with the dpi many apps and Google are hard coding the sizes into the apks. I would just leave the dpi stock
Click to expand...
Click to collapse
Thanks for your input. I just decides to reflash /system again (overwriting it via fastboot). But the problem persists!? How is this possible? Reflashing /system should reset DPI changes, right? Man, do I really have to reinstall all of Android? .. :crying:
karlo12 said:
Thanks for your input. I just decides to reflash /system again (overwriting it via fastboot). But the problem persists!? How is this possible? Reflashing /system should reset DPI changes, right? Man, do I really have to reinstall all of Android? .. :crying:
Click to expand...
Click to collapse
No not completely. That maybe your best bet. Also could try deleting the cache files.
You need to also change the dpi in build.prop, or you'll get those large icons.
Or if you want to go back to the old dpi, just do what you did in NRT, but change it to 560 this time.
change it in your build.prop file, then reboot for it to take affect. anyways, you will probably see other bugs with the dpi changed properly(but maybe not).