Hi everyone,
For Past week or so, I have been trying and trying and trying with varying degrees of success in my quest to get Android on my Wave. At the moment I am clueless about what I am doing wrong! I have followed the tutorial to the dot! except for the deletion of Wi-fi file. And I have faced all the issues mentioned in the TUT thread in different installs, now its just getting stuck at the language select menu! after choosing language, it freezes! So I want someone who has perfectly installed Android on Wave with applications and Wi-fi to tell me the small tit-bits and nuances, just the wisdom that you may have earned of...this procedure!
Here's my Specs:
Samsung Wave S8500 with XXJK1 firmware successfully flashed and tested with Android.
Sandick 16 GB SDHC Micro SD CARD
Tried 13 bada 2 android but not enough space errors
Tried 14 bada 1 android but random hangs, once boot fine. next time nothing!
Thanks!
It's a pre-alpha release. So you can't expect that it will run smoothly. So my advice wait for the first official release.
vanherst said:
It's a pre-alpha release. So you can't expect that it will run smoothly. So my advice wait for the first official release.
Click to expand...
Click to collapse
Yes, I understand that, but curiosity is killing me... I missed my work today in hope that I WILL GET THIS DONE! but hell, I am still going no where!
NHS2008 said:
Yes, I understand that, but curiosity is killing me... I missed my work today in hope that I WILL GET THIS DONE! but hell, I am still going no where!
Click to expand...
Click to collapse
Maby is it your Micro Card. More people are complaining that it's not working. I've a scandisk 4GB card and it's working fine. Have you treid both tuts?
Thing is, I had got it working without a hitch with 2gb, but no apps would install and then today I try as most say that you shuold not go over 1 gb for EXT2 Parttion, I kept it one gb and now I am having these absolutely random hangs. what is the secon tutorial? I don't thinnk thats the issue. what size of partition are you using? And what tutorial did you follow..? Thanks.
NHS2008 said:
Thing is, I had got it working without a hitch with 2gb, but no apps would install and then today I try as most say that you shuold not go over 1 gb for EXT2 Parttion, I kept it one gb and now I am having these absolutely random hangs. what is the secon tutorial? I don't thinnk thats the issue. what size of partition are you using? And what tutorial did you follow..? Thanks.
Click to expand...
Click to collapse
My partition is 1943 Mb. But if android is running and the partition is smaller then 4gb i think it's go wrong by the chmod 0777 command.
And you can install apps? Also I do not understand what you mean my your second sentence?? you yourseld have a partition of 1933 mb right? and why does it go wrong with chmod?? thanks for replying.. I am trying once again...
NHS2008 said:
And you can install apps? Also I do not understand what you mean my your second sentence?? you yourseld have a partition of 1933 mb right? and why does it go wrong with chmod?? thanks for replying.. I am trying once again...
Click to expand...
Click to collapse
The command CHMOD 0777 gives read/write/delete permissions on the folders and files. So when there goes something wrong with that command android can't write files on your sdcard.
Yes i can install apps and play games on android
So you don't use those commands (chmod) when you installed it? and how did you copy your files? thanks for the replies
EDIT: Woo hoo!! angry birds just worked! but I am getting ERROR when I try to enable Wi-fi! Do you know what this issue??
NHS2008 said:
So you don't use those commands (chmod) when you installed it? and how did you copy your files? thanks for the replies
EDIT: Woo hoo!! angry birds just worked! but I am getting ERROR when I try to enable Wi-fi! Do you know what this issue??
Click to expand...
Click to collapse
Yes i used the command (chmod) because if you don't use, the market never works.
Wi-Fi:
http://forum.xda-developers.com/showthread.php?t=1118436
first post in the faq
vanherst said:
Yes i used the command (chmod) because if you don't use, the market never works.
Wi-Fi:
http://forum.xda-developers.com/showthread.php?t=1118436
first post in the faq
Click to expand...
Click to collapse
No, my friend. I can't even enable it. before that it used to work but no I.P. now it just tries to start, then says error under Wi-fi. And doesnt turn green at all!
NHS2008 said:
No, my friend. I can't even enable it. before that it used to work but no I.P. now it just tries to start, then says error under Wi-fi. And doesnt turn green at all!
Click to expand...
Click to collapse
Then i've no idea. You can try on the IRQ channel, there are devs.
http://webchat.freenode.net/?randomnick=0&channels=androidonwave
RE
Android not booting anymore on 4GB, it breaks the ext2 filesystem. Now giving up and living on Bada again
The perfect recipe is WAITING for the stable release. Oleg and company are working so hard in this port and its so unstable not and have some clues to be solved.
Please, if you don't know what are you really doing, stop trying Android unless it will be fully ported. Because nowadays it will be unstable and nothing we can do will solve it.
We just have to be pacient and give our support to developers, and let then do their job.
Android in our Waves is now a reality, don't disturb people who are working on it and let them porting it. Maybe it will be fully ported in a few months.
This release is only for testing purposes, not for playing Angry Birds and nothing else, and its pretty useless. So don't think you will get a full Android right now installing some patches and touching the configuration, because it is IMPOSSIBLE right now.
Threads with no sense like this one, made only by impatient people, should be closed.
Regards.
agree with the last post, I am also tempted to make the port but I badly need a working phone , so I guess will wait for the stable version when I see everyone is ok with theirs
unmount your device and use fcsk -y /dev/<your_device>. this should correct problems becoz most of the people has prob due to not properly created filesystem or sudden shutdown. this will also solve input output error on chmod
Thanks people! but I got it working to the fullest (atleast, upto what is possible atm)!!
I noticed that for some reason, there were some files missing in 'System/etc' folder.
namely, the Wifi folder. So I pasted it from my PC and chmoded it and sudo synced it. then repaired with Gparted. Now works perfect! XD
Related
It is not quite self-explaining how to install Android on our Windows Mobile devices. Therefore I took some time and wrote down all the steps for people who are new to "Android".
More testers -> more experience -> more knowledge -> faster/better development.
I hope this way the forum is kept clean(er) from all kinds of questioned that have already been answered many times.
ReadMe Includes:
- Partitioning
- Device preparations
- Boot loader
- Install steps
- Fixes
- Links
- more...
If you are a developer (you create your own package) feel free to use my ReadMe for your packages (update regularly though).
to download the ReadMe click the [Android Repository] button in my signature.
It goes to a rapidshare page with 3 files, and when I click on the filename Android_README.TXT
or start download, I get the error
The file could not be found. Please check the download link.
ok thanks. i fixed it (rs bug when renaming files ^^)
How would i partition a 1GB SD Card? ie what sizes etc are the last 3 same but the unallocated is just whats left over?
I want to use a spare card rather then the one that came with my HD.
ATHiEST said:
How would i partition a 1GB SD Card? ie what sizes etc are the last 3 same but the unallocated is just whats left over?
I want to use a spare card rather then the one that came with my HD.
Click to expand...
Click to collapse
normally just calculate how i wrote in the readme:
whole space -768 (3* 256) and then the other 3 x 256
but in ur case i would make the swap smaller (i think its not even used at all) and the fat32 bigger; for instance:
fat32 - 384 MB
ext2 - 256 MB
ext2 - 256 MB
swap - 128 MB (rest)
To be honest the bit I find most confusing is all the different versions!
i didnt create any partitions on my card, and android works as good as it does on any, mind you i have not updated the files fo0r a month so alot might have changed
ReadMe updated!
updated a bit...
Geeba said:
To be honest the bit I find most confusing is all the different versions!
Click to expand...
Click to collapse
i agree...
i've been looking these posts here for a couple of days now and i still don't know how to do it....
especially the DualBoot thing...
is it possible to make a little bigger how-to manual?
or at least explain the versioning and the needed thing a little more?
the readme is about 50 times longer than anything else u will find about installing android anywhere else
the different versions are just like in windows mobile, theres not much to explain, its rather up to ur personal preference. doesnt take as long as flashing a wm rom, so its easy to try out more versions, especially with more sd cards.
dual boot is easy:
1. install the cab
2. open the dual boot program and make all your settings, for example: auto boot android (click on the checkbox/ratio under android logo), check auto boot checkbox and check fast boot (means 3 instead of 10 secs).
3. restart your device, DONT LAUNCH HARET because that will destroy all the dualboot settings. if you restart/shutdown the device normally, the settings will be stored and android will automatically booted at next startup (or whatever you set before)
if you have android autoboot and u want to boot wm, just QUICKLY press the wm LOGO when the dual boot screen appears.
i might include this in the readme soon, just dont have the time right now unfortunally
N!ghty said:
the readme is about 50 times longer than anything else u will find about installing android anywhere else
the different versions are just like in windows mobile, theres not much to explain, its rather up to ur personal preference. doesnt take as long as flashing a wm rom, so its easy to try out more versions, especially with more sd cards.
dual boot is easy:
1. install the cab
2. open the dual boot program and make all your settings, for example: auto boot android (click on the checkbox/ratio under android logo), check auto boot checkbox and check fast boot (means 3 instead of 10 secs).
3. restart your device, DONT LAUNCH HARET because that will destroy all the dualboot settings. if you restart/shutdown the device normally, the settings will be stored and android will automatically booted at next startup (or whatever you set before)
if you have android autoboot and u want to boot wm, just QUICKLY press the wm LOGO when the dual boot screen appears.
i might include this in the readme soon, just dont have the time right now unfortunally
Click to expand...
Click to collapse
Thanks for the dualboot help... i'll try that...
the first problem I have encountered yesterday when trying to put Android was SD card formating...
i downloaded the program you said and followed the instructions oh how-to and was not able to do it under Windows 7 with my 16GB SD card... does it even work for Windows 7??? is there another program I can try to do it with???
I have also dualboot on my PC with the Kubuntu being the second OS, but I'm not using it as much as Windows 7... I can try with it if you think it will work.. but first I have to download the 15GB of data from my SD card to my PC, again
I would like to put the Espresso build cause I saw that it has everything working beside the GPRS and camera...
can you tell me what should I download for my Blackstone so it works properly???
thanks alot...
qtype said:
Thanks for the dualboot help... i'll try that...
the first problem I have encountered yesterday when trying to put Android was SD card formating...
i downloaded the program you said and followed the instructions oh how-to and was not able to do it under Windows 7 with my 16GB SD card... does it even work for Windows 7??? is there another program I can try to do it with???
I have also dualboot on my PC with the Kubuntu being the second OS, but I'm not using it as much as Windows 7... I can try with it if you think it will work.. but first I have to download the 15GB of data from my SD card to my PC, again
I would like to put the Espresso build cause I saw that it has everything working beside the GPRS and camera...
can you tell me what should I download for my Blackstone so it works properly???
thanks alot...
Click to expand...
Click to collapse
like the readme says: partitioning is only needed for partitined builds, which means that android uses several partitions to store different kinds of data, for - hopefully - more speed. only glossy uses partitions, espresso doesnt.
for glossy, u can also use ubuntu (download parted magic or something similar) to create partitions.
for espresso, u just need to copy the stuff onto ur sdcard.
but thats all in the readme... i dont have time to explain in detail coz i need to study a whole ****in lot at the moment +.+
N!ghty said:
like the readme says: partitioning is only needed for partitined builds, which means that android uses several partitions to store different kinds of data, for - hopefully - more speed. only glossy uses partitions, espresso doesnt.
for glossy, u can also use ubuntu (download parted magic or something similar) to create partitions.
for espresso, u just need to copy the stuff onto ur sdcard.
but thats all in the readme... i dont have time to explain in detail coz i need to study a whole ****in lot at the moment +.+
Click to expand...
Click to collapse
ok... thanks for the help... you helped me a lot just with the claryfication of the versions that need partitioning and the ones that don't...
i didn't know that...
good luck with studying!!!!
one more question...
I get the following message '' Failed to load file\Storage Card\zImage''
Can you help me with that????
qtype said:
one more question...
I get the following message '' Failed to load file\Storage Card\zImage''
Can you help me with that????
Click to expand...
Click to collapse
meaning u dont have a zImage at all (ur probably using espresso?). so download one from here, copy files onto sd card and rename "zImage.xxxxxx" to "zImage" and ur ready to go.
N!ghty said:
meaning u dont have a zImage at all (ur probably using espresso?). so download one from here, copy files onto sd card and rename "zImage.xxxxxx" to "zImage" and ur ready to go.
Click to expand...
Click to collapse
yep, I downloaded it but I didn't know that i have to rename it...
It did the trick... booting up Android
thanks for all of your help...
updated the readme, not includes DualBoot howto and some other changes...
I managed to get the WiFi working but no matter which zImage I'm using I can't get the 3G to work...
I'm I doing something wrong or did I maybe forgot to do something????
qtype said:
I managed to get the WiFi working but no matter which zImage I'm using I can't get the 3G to work...
I'm I doing something wrong or did I maybe forgot to do something????
Click to expand...
Click to collapse
well, some details about what version you are using would be helpful. however, this is not the right channel to ask this question. i think this question has already been asked several times in other threads. try search function or read the thread for ur version, its probably a version-issue or only for your country/provider
N!ghty said:
well, some details about what version you are using would be helpful. however, this is not the right channel to ask this question. i think this question has already been asked several times in other threads. try search function or read the thread for ur version, its probably a version-issue or only for your country/provider
Click to expand...
Click to collapse
sorry about that...I realized it later that I should ask in another thread that question...
I managed to figure it out... I just needed to manually configure my APN settings...
Android boot error "micropklt_lcd_ctrl: This function should no longer be used"
I've been battling this error again and again whenever I tried another Android release, and since there are no real answers around, but some others have the same problem, which according to searches mostly goes unanswered in bigger threads, I decided to go ahead and dedicate one thread to it.
Problem: After installing Android and running it, its boot ends up in an eternal loop displaying
Code:
micropklt_lcd_ctrl: This function should no longer be used
.
Setting: German Rhodium. Initially an Energy ROM. Since I thought it might be something from the ROM, the latest one is Energy.RHODIUM.21889.Android(ULTRA_LITE_ROM)_28.Jan.
8 GB SD from Kingston. Since this was named as a possible problem, tried with 1 GB SD (Kingston) as well.
Reformatted SD and restarted from scratch.
Tried Android versions:
Project Android 030810.cab
Project Android 033110.cab
[MJG]Rhod.Eclair.Rebuild033110.3.rar
plus various older ones (with different base name, xAndroid or something like that?) already deleted.
Tried to disable 3D Hardware during boot.
Another suggested workaround to use specific files from older releases; these I could no longer find on the net.
To sum attempts up:
Tried different (?) Android releases (xAndroid, Project Android) - fail
Tried small SD card (1 GB) - fail
Tried SanDisk instead of Kingston SD card - pending
Tried to reformat SD card (with SD card formatter) - fail
Tried to disable 3D Hardware - fail
Tried WinMo ROM labeled as created for Android (Energy.RHODIUM.21889.Android(ULTRA_LITE_ROM)_28.Jan) - fail
Tried to insert SIM card (was missing) - fail
Tried to update HardSSL (Rhodium-HardSPL_V2_00R3.exe) - fail
Information:
(forum prevented me from adding links to external information)
This forum, other members with same problem
Looking for: suggestions what else to try.
ItsReallyMe said:
I've been battling this error again and again whenever I tried another Android release, and since there are no real answers around, but some others have the same problem, which according to searches mostly goes unanswered in bigger threads, I decided to go ahead and dedicate one thread to it.
Problem: After installing Android and running it, its boot ends up in an eternal loop displaying
Code:
micropklt_lcd_ctrl: This function should no longer be used
.
Setting: German Rhodium. Initially an Energy ROM. Since I thought it might be something from the ROM, the latest one is Energy.RHODIUM.21889.Android(ULTRA_LITE_ROM)_28.Jan.
8 GB SD from Kingston. Since this was named as a possible problem, tried with 1 GB SD (Kingston) as well.
.
Click to expand...
Click to collapse
I have an AT&T Tilt2, stock rom, 8GB SanDisk. I see a very similar message when booting xdandroid, but mine continues to boot through, my boot sequence snippet runs like this:
Code:
[ 26.309173] Adding 102392k swap on /dev/block/ramzswap0.
Priority:-1 extents:1 across: 102392k
[ 26.484039]Something used micropklt_lcd_ctrl: This function should no longer be used
USING EXPERIMENTAL TILT2 LAYOUT
op: cannot stat '/init.etc/keymaps/tilt2_navi_pad.kl': No such file or directory
Touchscreen device directory is /sys/class/input/input2
Then continues to the screen calibration. I know I'm not helping directly, but perhaps can help lead others to clues ?
i already started a topic for this exact error....
http://forum.xda-developers.com/showthread.php?t=632128
So far no one has come up with a solution...
Oh, sorry, I searched the forum a few times, but mus have forgotten that thread, otherwise I would've posted there as well...
From what I can read there, maybe I should try a SanDisk instead of Kingston SD? Or is it SD vs. SDHC? Anyway, I just ordered a 2 GB SanDisk from Amazon (smallest one I could get ) and will try this next...
I managed to solve it by reflashing the newest HardSPL. (In my case I had a corrupt microp firmware, casuing all kind of problems in WM as well).
It might not solve the problem for you, but it can't hurt either
My SanDisk SD has not yet arrived, but I tried to insert a SIM card (phone currently has none, since I' using another one while testing) - no changes.
Thanks for the HardSPL hint - tried as well. No Luck, but at least another topic to add to the "things I tried" list
Okay.. So, i tried HardSPL.
Task 29
Reloaded my Rom
Hard Reset
Formatted Memory Stick
Followed ALL instructions!
Nothing happened.
I then went back and tried an old version of android from this thread
I used the 12/20 2.01 version.
AAAANNND..... it loaded right away....
WHY does this old version work, and the new ones wont?
what is different?
Update: my SanDisk SD card arrived, so I loaded [MJG]Rhod.2.1Sense.042310.rar, extracted it to the card, and started it. Same problem. This means it does not seem like a Kingston SD card problem.
So... I tested, and can confirm that the old build you linked solved the problem for me as well!
I have searched this ENTIRE FORUM and read EVERY SINGLE GOD FORSAKEN post about this error. I am at my whits end!
Someone said they got it to work with a more current package and an old rootfs.img
I didnt try the same two builds they did, i tried the sense ui one and the old rootfs. from the build i said works. it did not work.
so i figured i would compare the two rootfs.img to see what the difference is.
however, i cannot open the contents in windows (from what i understand)
so i install UBUNTU on my computer.
I cant for the life of me figure out how to mount the damn image!
PLEASE SOMEONE ELSE! please look this up. i am frustrated beyond words.
if you can give me a way to compare these files in windows, i will be glad to do it.
I just cant stand windows mobile crashing all the mother f-ing time and i REALLY REALLY REALLY want to use android. Im sorry for being so frustrated. i have spent literally HOURS on this...
Anyone, anything?
Mount rootfs.img
eternalcold said:
Anyone, anything?
Click to expand...
Click to collapse
You can mount image in terminal like this:
first create dir with:
mkdir /mnt/rootfs
then mount the image:
mount rootfs.img /mnt/rootfs/ -o loop
then change dir to /mnt/rootfs and you have the android FS.
i will also compare old and new rootfs so maybe we will found something!
BR
I still have this problem.
I tried what you said, but i keep getting errors. I cant seem to get it to work. I will again look through all the threads again, as well as the different websites i found from google. i will link them tomorrow when i get a chance. If anyone else has found anything, please let me know.
The latest kernel has the following commit message
"rewritten micropklt_lcd_ctrl calls to micropklt_set_misc_states calls"
So this might fix it for you guys?
It seems to have some other problems with sleep etc, but if it boots it is something
I see, thanks for looking, however, i still cant figure out how to mount and change things in ubuntu (sorry, i know i am a newb) would you be able to repackage it with the line changed to the old one? and upload it? i will check it out to see if it works.
It's alive!!
Download latest Android build with latest kernel from hxxp://glemsom.anapnea.net/android/htc-msm-android/ and replace zImage and modules and thats it.
i didn't test it full, but it starts!
Thanks to Star-Lite for info!!!
BR
Ah yes it works! Beautiful beautiful!
Don't thank me, thank CaptNoord for fixing this in the kernel
I'm sure he has a donate button somewhere
I will donate as soon as the bills are past this month (a couple more days)
Out of plain curiousity, is there a reason why this error only happened on some devices and not others? Could it be from a hardware difference between maybe different revisions of the device?
use the right starup.txt file
FRX07 is out now!!
Removed...
Removed...
By the way, you can create a calibration file by hand, using the factory calibration settings. The settings are displayed when you boot into the SPL (power + volume down). Details here:
http://forum.xda-developers.com/showpost.php?p=10807361&postcount=515
http://forum.xda-developers.com/showpost.php?p=10817104&postcount=529
Very pleased
Loaded this on my 15yr olds Tilt II. It is the most complete and stable package I have used to date. He is a HAPPY boy.... Thank to all that have contributed to create it!
Doesnt work here. I had a EXT3 Partition (500 MB) from an earlier install, But after it says 'Allocated....' it just stops doing anything, and after, say, 10 mins the screen turns black and nothing happens. It runs now for 20 mins and still nothing happened. Whats wrong? Using a Touch Pro2.
Maarten90 said:
Doesnt work here. I had a EXT3 Partition (500 MB) from an earlier install, But after it says 'Allocated....' it just stops doing anything, and after, say, 10 mins the screen turns black and nothing happens. It runs now for 20 mins and still nothing happened. Whats wrong? Using a Touch Pro2.
Click to expand...
Click to collapse
I never mention anything about an ext3 partition, where is that coming from?
If you were using a neopeek build (they use ext2 partitions...) or something else, might be a good idea to go ahead and do a full format (FAT32) with the HP tool.
Whoops, indeed. I used a Neopeek build before. . But then, Why won't it boot? I copied everything to my FAT32 formatted SDcard, but it just does get stuck at the part mentioned before.
Maarten90 said:
Whoops, indeed. I used a Neopeek build before. . But then, Why won't it boot? I copied everything to my FAT32 formatted SDcard, but it just does get stuck at the part mentioned before.
Click to expand...
Click to collapse
Did you format the card? I'm not sure how neopeeks builds are configured, AFAIK our build requires the FAT32 partition be the first partition.
Yes it is the first partition according to fdisk:
Device Boot Start End Blocks Id System
/dev/sdb1 1 1885 15137792 b W95 FAT32
/dev/sdb2 1885 1950 524288 83 Linux
Click to expand...
Click to collapse
Maarten90 said:
Yes it is the first partition according to fdisk:
Click to expand...
Click to collapse
Ok, you followed the rest of the directions like moving the startup.txt? Did you put it in a folder, if so did you adjust the rel_path statement?
Can you at least try formatting the card as one big FAT32 partition?
I have indeed, moved the right startup.txt to the root of the SDCard, and I also have copied your calibration file to the root folder of the SDCard. Going to reformat the SDCard and I will report back once done .
Maarten90 said:
I have indeed, moved the right startup.txt to the root of the SDCard, and I also have copied your calibration file to the root folder of the SDCard. Going to reformat the SDCard and I will report back once done .
Click to expand...
Click to collapse
Ok. Not sure what else it could be to be honest.
It works! Thank you! While trying it out I tried to play Angry Birds, but it seems that Hardware 3D is not available yet?
Maarten90 said:
It works! Thank you! While trying it out I tried to play Angry Birds, but it seems that Hardware 3D is not available yet?
Click to expand...
Click to collapse
Oy...
HW3D works, but Angry Birds requires opengles2.0. Our phones support 1.1 at best IIRC.
I heard there's some other versions of Angry Birds flying around that work better on our old phones. I honestly do not understand the popularity of the game, and yes I have played it. "Boring" is about the only word I could come up with to describe it, but I'm not much of a gamer on my phone .
Ah OK, that explains the lag . I only installed Angry Birds for testing purposes, but thanks for your opinion on the game .
Maarten90 said:
Ah OK, that explains the lag . I only installed Angry Birds for testing purposes, but thanks for your opinion on the game .
Click to expand...
Click to collapse
Yea, you can ignore my opinion of the game. Most people seem to love it .
Search around, like I said there's some "lite" version of the game that I hear runs better .
arrrghhh said:
Yea, you can ignore my opinion of the game. Most people seem to love it .
Search around, like I said there's some "lite" version of the game that I hear runs better .
Click to expand...
Click to collapse
100% agree. What is the fascination with this game? Like you said, it is boring at best. I don't get it.
1) w/ the new kernel, what parts will consist of the most recent 'FRX04 stable'?
2) been doing a lot of Words With Friends recently anyone have any good combinations of kernels/rootfs/data.img that make it playable?
AkumaX said:
1) w/ the new kernel, what parts will consist of the most recent 'FRX04 stable'?
2) been doing a lot of Words With Friends recently anyone have any good combinations of kernels/rootfs/data.img that make it playable?
Click to expand...
Click to collapse
No clue what you're asking. Both of your questions appear to be in English, but they don't make any sense .
I bought my phone about a week ago, and I noticed it was pretty slow after installing some apps, even slower than my previous Nexus S.
I changed my phone from yakjuxw to yakju yesterday, and updated to 4.2. I even did a factory reset after everything was done.
It was the same, it started pretty fast but as I ran the apps from the backup I had made the phone started to slow down.
I still haven't managed to find which app is causing me problems, so I was hoping someone here could help...
Did you use Titantium Backup for apps?
As far as I know, it is recommended not to restore all apps via Titantium Backup but only the ones that have some data associated to them like games with their saves. So try installing a fresh 4.2 ROM, only restore the apps that needs their data, and download the others via Play Store
I hope you can either avoid the lag this way or at least spot the app causing it
ahmadallica said:
Did you use Titantium Backup for apps?
As far as I know, it is recommended not to restore all apps via Titantium Backup but only the ones that have some data associated to them like games with their saves. So try installing a fresh 4.2 ROM, only restore the apps that needs their data, and download the others via Play Store
I hope you can either avoid the lag this way or at least spot the app causing it
Click to expand...
Click to collapse
No, I restored it through the Nexus Toolkit (the GUI version).
I only restored normal apps and none of the system apps or data. And this has been on absolutely stock Google ROMs ever since I bought the phone.
KaiZ51 said:
I bought my phone about a week ago, and I noticed it was pretty slow after installing some apps, even slower than my previous Nexus S.
I changed my phone from yakjuxw to yakju yesterday, and updated to 4.2. I even did a factory reset after everything was done.
It was the same, it started pretty fast but as I ran the apps from the backup I had made the phone started to slow down.
I still haven't managed to find which app is causing me problems, so I was hoping someone here could help...
Click to expand...
Click to collapse
That happens when you restore rom essential apps...you only need to restore the apps you downloaded.
Sent from my Galaxy Nexus using xda premium
Maybe you have the eMMC bug/issue which may occur if your phone was produced 08/2012.
To check this install the "eMMC Brickbug Check" tool and verify if your if chip type is V3U00M and date 08/2012.
https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check
If yes check this link for a workaround for this annoying bug:
http://forum.xda-developers.com/showpost.php?p=35020486&postcount=10
KaiZ51 said:
No, I restored it through the Nexus Toolkit (the GUI version).
I only restored normal apps and none of the system apps or data. And this has been on absolutely stock Google ROMs ever since I bought the phone.
Click to expand...
Click to collapse
try to flash the image again and dont restore this time... see if that fixes your issue
navien said:
Maybe you have the eMMC bug/issue which may occur if your phone was produced 08/2012.
To check this install the "eMMC Brickbug Check" tool and verify if your if chip type is V3U00M and date 08/2012.
https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check
If yes check this link for a workaround for this annoying bug:
http://forum.xda-developers.com/showpost.php?p=35020486&postcount=10
Click to expand...
Click to collapse
Well, I've just checked it, and it seems like my phone falls within the parameters for this bug... The only difference is the date is 09/2012. But is there a way to know for sure that I'm affected by this bug? Besides, I'm going to have to root the phone, which is going to be a bit annoying since I really didn't want to do it because I may have problems with the warranty in case I need to return it...
Also, if I flash a custom ROM in the future, will I have to do that again, or do custom ROMs usually come with that fix?
k786 said:
try to flash the image again and dont restore this time... see if that fixes your issue
Click to expand...
Click to collapse
I was thinking of trying that as well, though it may be annoying because I'll lose my data... But if I have to I guess I really don't have a choice...
KaiZ51 said:
I was thinking of trying that as well, though it may be annoying because I'll lose my data... But if I have to I guess I really don't have a choice...
Click to expand...
Click to collapse
delete the userdata from the image and it wont wipe your internal storage
KaiZ51 said:
Well, I've just checked it, and it seems like my phone falls within the parameters for this bug... The only difference is the date is 09/2012. But is there a way to know for sure that I'm affected by this bug? Besides, I'm going to have to root the phone, which is going to be a bit annoying since I really didn't want to do it because I may have problems with the warranty in case I need to return it...
Also, if I flash a custom ROM in the future, will I have to do that again, or do custom ROMs usually come with that fix?
Click to expand...
Click to collapse
All people reported this bug (at least what i´ve found) have production date of 08/2012 - maybe this bug also affects newer models.
I think if your chip type is V3U00M then your'e phone is affected. But your can test this easily. Just copy a huge file (i've copied 1 hd movie ~11GB) to the internal storage. The phone should slow down extremely, even if you delete the file again. For example: my phone needed 4-6 seconds to open the contacts app - sometimes even more.
Rooting is no big issue - you can easily revert to stock image.
If you flash a ROM you will to have implement the workaround again. Custom ROMs will not include this fix in general because if you remount the data partition with the discard option on an eMMC other than V3U00M your phone will be hard bricked.
navien said:
All people reported this bug (at least what i´ve found) have production date of 08/2012 - maybe this bug also affects newer models.
I think if your chip type is V3U00M then your'e phone is affected. But your can test this easily. Just copy a huge file (i've copied 1 hd movie ~11GB) to the internal storage. The phone should slow down extremely, even if you delete the file again. For example: my phone needed 4-6 seconds to open the contacts app - sometimes even more.
Rooting is no big issue - you can easily revert to stock image.
If you flash a ROM you will to have implement the workaround again. Custom ROMs will not include this fix in general because if you remount the data partition with the discard option on an eMMC other than V3U00M your phone will be hard bricked.
Click to expand...
Click to collapse
So, I went ahead and followed the instructions on the link you gave me... And it seems to be much better so far I still haven't tested enough, but I think the problem is pretty much fixed. I just have a few more questions if you don't mind...
1- When I ran the dd command, it took a while like the instructions said, but when it finished it said something about not enough space. Could something have gone wrong, or is this normal?
2- Since it isn't likely custom ROMs implement this fix, is there any way I can "stick" this fix on the phone's system so that I don't have to worry about setting it every time I flash a new ROM?
3- Is there any way to make sure that the script I set up in Script Manager is fully working and running on boot?
KaiZ51 said:
So, I went ahead and followed the instructions on the link you gave me... And it seems to be much better so far I still haven't tested enough, but I think the problem is pretty much fixed. I just have a few more questions if you don't mind...
1- When I ran the dd command, it took a while like the instructions said, but when it finished it said something about not enough space. Could something have gone wrong, or is this normal?
2- Since it isn't likely custom ROMs implement this fix, is there any way I can "stick" this fix on the phone's system so that I don't have to worry about setting it every time I flash a new ROM?
3- Is there any way to make sure that the script I set up in Script Manager is fully working and running on boot?
Click to expand...
Click to collapse
Bumping...
KaiZ51 said:
So, I went ahead and followed the instructions on the link you gave me... And it seems to be much better so far I still haven't tested enough, but I think the problem is pretty much fixed. I just have a few more questions if you don't mind...
1- When I ran the dd command, it took a while like the instructions said, but when it finished it said something about not enough space. Could something have gone wrong, or is this normal?
2- Since it isn't likely custom ROMs implement this fix, is there any way I can "stick" this fix on the phone's system so that I don't have to worry about setting it every time I flash a new ROM?
3- Is there any way to make sure that the script I set up in Script Manager is fully working and running on boot?
Click to expand...
Click to collapse
The dd command fills the entire partition till full, therefore the not enough space message is normal.
I´ve not tested how to implemt this fix in a ROM before flashing.
In theory you only need to add the file with the script into the init.d folder of the zip before flashing.
I´ve made IO Benchmarks with AndroBench to check if the script works:
with enabled script i get for example RND WR ~135 IOPS without script 54 IOPS.
navien said:
The dd command fills the entire partition till full, therefore the not enough space message is normal.
I´ve not tested how to implemt this fix in a ROM before flashing.
In theory you only need to add the file with the script into the init.d folder of the zip before flashing.
I´ve made IO Benchmarks with AndroBench to check if the script works:
with enabled script i get for example RND WR ~135 IOPS without script 54 IOPS.
Click to expand...
Click to collapse
Apparently it isn't running, since I get my Random Write score in the 30's IOPS. Besides that, I made Script Manager output logs, and it seems like it says it could not mount.
So what can I do? I'm not sure if I've already said this, but I'm on the stock 4.2.1 yakju ROM, if it matters. I could do this the init.d way, but I'm not sure if it works fine on stock ROM...
Also, something I haven't yet understood, is the dd command for checking if the fix works temporarily, or do you really need to do it in order to prepare the phone for the script?
And do you need to have as much empty space as possible before running the command, or you don't need to care about that?
Sorry about all the trouble with this problem, it's just as you probably know the phone is barely usable with this bug so I have no choice but to ask for help... Google should really fix this in an update, it's something pretty urgent in my opinion.
KaiZ51 said:
Apparently it isn't running, since I get my Random Write score in the 30's IOPS. Besides that, I made Script Manager output logs, and it seems like it says it could not mount.
So what can I do? I'm not sure if I've already said this, but I'm on the stock 4.2.1 yakju ROM, if it matters. I could do this the init.d way, but I'm not sure if it works fine on stock ROM...
Also, something I haven't yet understood, is the dd command for checking if the fix works temporarily, or do you really need to do it in order to prepare the phone for the script?
And do you need to have as much empty space as possible before running the command, or you don't need to care about that?
Sorry about all the trouble with this problem, it's just as you probably know the phone is barely usable with this bug so I have no choice but to ask for help... Google should really fix this in an update, it's something pretty urgent in my opinion.
Click to expand...
Click to collapse
Oh, and do you think I should go to the store to replace my phone? I still haven't understood if this is a software or hardware issue, but I'm believing it's the first...
KaiZ51 said:
Apparently it isn't running, since I get my Random Write score in the 30's IOPS. Besides that, I made Script Manager output logs, and it seems like it says it could not mount.
So what can I do? I'm not sure if I've already said this, but I'm on the stock 4.2.1 yakju ROM, if it matters. I could do this the init.d way, but I'm not sure if it works fine on stock ROM...
Also, something I haven't yet understood, is the dd command for checking if the fix works temporarily, or do you really need to do it in order to prepare the phone for the script?
And do you need to have as much empty space as possible before running the command, or you don't need to care about that?
Sorry about all the trouble with this problem, it's just as you probably know the phone is barely usable with this bug so I have no choice but to ask for help... Google should really fix this in an update, it's something pretty urgent in my opinion.
Click to expand...
Click to collapse
OK. The workaround with the script needs a ROM with init.d support. I thought this was mentioned in the linked thread.
I´m using THIS one.
The real fix is the re-mounting of the /data & /cache partitions using the discard option. If you type the command in a terminal window it fixes the problem temporary.
After reboot the problem is back. So you need to make a init.d script which will be executed every boot.
I think the dd command 'cleans' the free memory but i'm not sure.
To my opinion it doesn't make any sense to replace the phone because there's a big chance to get a new one with same problem.
So it is a software bug which should be solved by google.
navien said:
OK. The workaround with the script needs a ROM with init.d support. I thought this was mentioned in the linked thread.
I´m using THIS one.
The real fix is the re-mounting of the /data & /cache partitions using the discard option. If you type the command in a terminal window it fixes the problem temporary.
After reboot the problem is back. So you need to make a init.d script which will be executed every boot.
I think the dd command 'cleans' the free memory but i'm not sure.
To my opinion it doesn't make any sense to replace the phone because there's a big chance to get a new one with same problem.
So it is a software bug which should be solved by google.
Click to expand...
Click to collapse
Hmm I see... But from what I understood, you can make the script run at boot with apps like ROM Toolbox and Script Manager, correct? Although I'm not sure if it's running on my system, I've tried both apps and the benchmarks are always in the 30's...
Or do you really need a ROM with init.d support? Also I have BusyBox installed on Google's stock ROM, not sure if that is enough to able to run init.d scripts.
But how would you run scripts with init.d? Sorry, I'm a noob to this kind of stuff, I never did stuff like this...
KaiZ51 said:
Well, I've just checked it, and it seems like my phone falls within the parameters for this bug... The only difference is the date is 09/2012.
Click to expand...
Click to collapse
Thank you for confirming chips produced 09/2012 as bad. Added this to the post linked above.
KaiZ51 said:
When I ran the dd command, it took a while like the instructions said, but when it finished it said something about not enough space. Could something have gone wrong, or is this normal?
Click to expand...
Click to collapse
This is normal as we don't give the dd command a particular file size to create. So it simply writes data until no space is left.
KaiZ51 said:
Since it isn't likely custom ROMs implement this fix, is there any way I can "stick" this fix on the phone's system so that I don't have to worry about setting it every time I flash a new ROM?
Click to expand...
Click to collapse
If you are only using ROMs that support something like init.d inside data (like CM), next time to worry about this will be when you do a full wipe.
Probably then the problem will already be fixed by Google or others as it gains more attention over time.
KaiZ51 said:
Is there any way to make sure that the script I set up in Script Manager is fully working and running on boot?
Click to expand...
Click to collapse
Jup. Type 'mount' in Terminal or adb after you rebooted your phone:
# mount
[...]
/dev/block/platform/omap/omap_hsmmc.0/by-name/userdata /data ext4 rw,noatime,errors=panic,barrier=1,nomblk_io_submit,data=ordered,noauto_da_alloc,discard 0 0
[...]
Click to expand...
Click to collapse
=> discard option added, script ran successfully
KaiZ51 said:
Apparently it isn't running, since I get my Random Write score in the 30's IOPS. Besides that, I made Script Manager output logs, and it seems like it says it could not mount.
Click to expand...
Click to collapse
Maybe you have to check something like 'run as root' or similar in Script Manager.
KaiZ51 said:
So what can I do? I'm not sure if I've already said this, but I'm on the stock 4.2.1 yakju ROM, if it matters. I could do this the init.d way, but I'm not sure if it works fine on stock ROM...
Click to expand...
Click to collapse
Nope. Stock does not support init.d.
KaiZ51 said:
Also, something I haven't yet understood, is the dd command for checking if the fix works temporarily, or do you really need to do it in order to prepare the phone for the script?
Click to expand...
Click to collapse
You can use the script without. The phone will speed up over time as more and more data is written/deleted and therefore the eMMC chip gets some discard commands.
The dd + rm just speeds up the process as all free blocks will be told to the eMMC chip due to the discard option added beforehand.
Another possibility (after installing the script and confirming that it works) would be to copy a large file that fills almost all space on the phone and remove it afterwards. The dd command is just considerably faster.
KaiZ51 said:
And do you need to have as much empty space as possible before running the command, or you don't need to care about that?
Click to expand...
Click to collapse
You don't need to care. Just keep around 1,0-1,5 GiB of free space everytime: Benchmark
KaiZ51 said:
Oh, and do you think I should go to the store to replace my phone? I still haven't understood if this is a software or hardware issue, but I'm believing it's the first...
Click to expand...
Click to collapse
Well, you might get a replacement phone and through bringing it back the chance that Google gets aware of the problem may be higher.
But possibly they will only wipe all data which makes the phone fast again for some time and tell you there is nothing wrong with it...
You may even think about it from this point of view: If the fix works for you, you have a phone with a blazingly fast eMMC chip, faster than any GNex produced before 08/2012 (until you have less than 1 GiB of free space on /data)
KaiZ51 said:
Google should really fix this in an update, it's something pretty urgent in my opinion.
Click to expand...
Click to collapse
+1
ph4zrd said:
Thank you for confirming chips produced 09/2012 as bad. Added this to the post linked above.
This is normal as we don't give the dd command a particular file size to create. So it simply writes data until no space is left.
If you are only using ROMs that support something like init.d inside data (like CM), next time to worry about this will be when you do a full wipe.
Probably then the problem will already be fixed by Google or others as it gains more attention over time.
Jup. Type 'mount' in Terminal or adb after you rebooted your phone:
=> discard option added, script ran successfully
Maybe you have to check something like 'run as root' or similar in Script Manager.
Nope. Stock does not support init.d.
You can use the script without. The phone will speed up over time as more and more data is written/deleted and therefore the eMMC chip gets some discard commands.
The dd + rm just speeds up the process as all free blocks will be told to the eMMC chip due to the discard option added beforehand.
Another possibility (after installing the script and confirming that it works) would be to copy a large file that fills almost all space on the phone and remove it afterwards. The dd command is just considerably faster.
You don't need to care. Just keep around 1,0-1,5 GiB of free space everytime: Benchmark
Well, you might get a replacement phone and through bringing it back the chance that Google gets aware of the problem may be higher.
But possibly they will only wipe all data which makes the phone fast again for some time and tell you there is nothing wrong with it...
You may even think about it from this point of view: If the fix works for you, you have a phone with a blazingly fast eMMC chip, faster than any GNex produced before 08/2012 (until you have less than 1 GiB of free space on /data)
+1
Click to expand...
Click to collapse
Thanks, that cleared a lot of questions.
So, after having tested the phone some more time (and I do have discard enabled at boot after all), the phone still seems pretty slow to me.
Yesterday I did the discard command with the adb shell, and then rebooted with the discard script enabled, but it's still pretty slow...
I've also benchmarked the phone in AndroBench a few times after this and Random Write scores ranged from as low as 6 (yes, six) IOPS, to 60's IOPS.
Still, this isn't that good since it seems like normal scores are in the 100's.
I really don't know what I should do now... Maybe the eMMC chip isn't actually the problem? But I find that rather strange since I don't think I have any apps that I already didn't have on my old Nexus S, and the phone does seem slower than my old one.
KaiZ51 said:
I really don't know what I should do now... Maybe the eMMC chip isn't actually the problem? But I find that rather strange since I don't think I have any apps that I already didn't have on my old Nexus S, and the phone does seem slower than my old one.
Click to expand...
Click to collapse
How much free space do you have left on /data or /sdcard?
And you used the dd-rm-combination after remounting with discard, right?
ph4zrd said:
How much free space do you have left on /data or /sdcard?
And you used the dd-rm-combination after remounting with discard, right?
Click to expand...
Click to collapse
I have 1.71GB free now.
And what do you mean about your second question? If you're asking if I used those commands when I connected the phone to my PC via USB Debugging, then yes.
If you're talking about the script that runs at boot, all I have in that script is
Code:
#!/system/bin/sh
mount -o remount,discard /data
mount -o remount,discard /cache
Should I put the script like this?
Code:
#!/system/bin/sh
mount -o remount,discard /data
mount -o remount,discard /cache
dd if=/dev/zero of=/data/tmp.bin
rm /data/tmp.bin
I didn't put them there since I thought the dd and rm commands were only meant to be run when connected via USB and not at boot as well...
Hi
I'm not a total iGO noob and been using it for a few years on HTC HD2 but now have a really annoying problem.
Just got a HTC One M8 (European) and rooted immediately plus gave SD card write access.
First thing I did was install iGO the usual way and add all the content.
When I'm in default 3D mode, the screen starts 'blinking' after a while. The route and the roads start to disappear and the terrain starts taking over the screen, so that for example it will be all green, the same as the fields. The whole screen starts flashing. This is happening on default scheme/skin or any other HD compatible skin. Meanwhile, the voice and the directions are still all ok.
A couple of times I've got a error message saying "memory is low, use different route options", but that's only a couple of times. Remember, this is a phone with bags of memory and no other apps.
I have tried with the moveable thin apks that I can move to SD with all the content, and have tried every other version of iGO apk with all the iGO folders on the internal memory.
I believe the data.zip is I have is a 1920x1080 HD file and I have tried starting with and without Branding files.
I have tried lots of different sys.txt combinations.
Obviously I delete the Save folder every time.
Please, anyone...HELP!
SD card write access
SD card write access.
HTC one m8 , iGO primo (2,4) 9.6.29.341779 and SD card write access problem.
I need to setup all settings each time I am running an application.
mssSphaera said:
SD card write access.
HTC one m8 , iGO primo (2,4) 9.6.29.341779 and SD card write access problem.
I need to setup all settings each time I am running an application.
Click to expand...
Click to collapse
The SD write problem is I think resolved for me by rooting and flashing a different kernel - I can't remember the thread I got this from, but will post when I find it.
So iGO works now, but the Lesscro Themechanger isn't working now!
The slow display I had came from a memory setting I changed in the sys.txt, thanks to another member.
marcusroberts said:
The SD write problem is I think resolved for me by rooting and flashing a different kernel - I can't remember the thread I got this from, but will post when I find it.
So iGO works now, but the Lesscro Themechanger isn't working now!
The slow display I had came from a memory setting I changed in the sys.txt, thanks to another member.
Click to expand...
Click to collapse
come on .. there must be a solution and not rooting phone.
mssSphaera said:
come on .. there must be a solution and not rooting phone.
Click to expand...
Click to collapse
Nope, afraid not. Even rooting and using SDFix won't work alone. I tried changing the permissions on the R/W SD data but keeps defaulting on reboot. Flashing a different kernel is the best way as far as I know.
It's the Google / KitKat policy that's messed things up!
To fix the sd card issue you have to root.There is no other alternative.Kitkat implemented this issue.To fix it you have to change permissions in es file explorer to rw for all.Or you can flash kernel which disables read/write protection.The best kernel is elementalx kernel.Go give it a try! :laugh:
igo roads disappear/blink
marcusroberts said:
The SD write problem is I think resolved for me by rooting and flashing a different kernel - I can't remember the thread I got this from, but will post when I find it.
So iGO works now, but the Lesscro Themechanger isn't working now!
The slow display I had came from a memory setting I changed in the sys.txt, thanks to another member.
Click to expand...
Click to collapse
Hi, I'm having the same problem with the blinking and disappearing roads running igo on my m8. Could you let me know the sys.text tweak that resolved this for you please? Cheers
ArchiGent said:
Hi, I'm having the same problem with the blinking and disappearing roads running igo on my m8. Could you let me know the sys.text tweak that resolved this for you please? Cheers
Click to expand...
Click to collapse
[debug]
max_memory=400000000
reserve_memory=15000000
cache=2048
This is what a member suggested and it worked for me!
Let me know if it works for you.
Are you using Themechanger at all? I'm struggling with that.
marcusroberts said:
[debug]
max_memory=400000000
reserve_memory=15000000
cache=2048
This is what a member suggested and it worked for me!
Let me know if it works for you.
Are you using Themechanger at all? I'm struggling with that.
Click to expand...
Click to collapse
I've just been on a quick trip around the block and adding the above into the sys.text does indeed seem to have done the trick! Many thanks.
I've not used Themechanger since switching from Windows to Android a few years ago.
Same problem here with HTC M8 and above settings did not help, not even a bit.
stathis95194 said:
Same problem here with HTC M8 and above settings did not help, not even a bit.
Click to expand...
Click to collapse
Do you mean that iGO is running slowly or just not starting? Have you deleted the SAVE folder and tried. Is your iGO on the SD card or internal?
ArchiGent said:
Hi, I'm having the same problem with the blinking and disappearing roads running igo on my m8. Could you let me know the sys.text tweak that resolved this for you please? Cheers
Click to expand...
Click to collapse
BTW the themechanger is now working great. It was a problem in sys.txt in the interface settings. Was still set for iGO Windows! Press the widget and changed weather/maps great.
marcusroberts said:
Do you mean that iGO is running slowly or just not starting? Have you deleted the SAVE folder and tried. Is your iGO on the SD card or internal?
Click to expand...
Click to collapse
No, i'm talking about iGo is starting fine, but after a while screen starts blinking until it becomes black. Program is still running but screen is black.
I have eleted save folder, re-installed, tried all kinds of versions
iGo is on sd card, but i'm rooted and on a custom kernel with the sdcard read/write permission fixed.
Same configuration on my One X is running fine.
stathis95194 said:
No, i'm talking about iGo is starting fine, but after a while screen starts blinking until it becomes black. Program is still running but screen is black.
I have eleted save folder, re-installed, tried all kinds of versions
iGo is on sd card, but i'm rooted and on a custom kernel with the sdcard read/write permission fixed.
Same configuration on my One X is running fine.
Click to expand...
Click to collapse
If you know of the best way to that I can share my iGO folder here, please let me know. It really should work well and I use it all day and every day. Let me know how to share please.
marcusroberts said:
If you know of the best way to that I can share my iGO folder here, please let me know. It really should work well and I use it all day and every day. Let me know how to share please.
Click to expand...
Click to collapse
Thanks for the offer. I think i fixed it with a workaround.
I moved the iGO folder on internal memory but kept the "big" content folder on sdcard (which is what i needed anyway)
It seems to work fine now. I will test it again tomorrow when i will be driving and report back.
Any probs let me know. It runs sweet on the m8 mate
marcusroberts said:
If you know of the best way to that I can share my iGO folder here, please let me know. It really should work well and I use it all day and every day. Let me know how to share please.
Click to expand...
Click to collapse
Well i think i might take you up on your offer. I can't get rid of the blinking problem.
I have tried everything. But i believe i have identified what creates the problem. If under iGO/content/map i have a lot of maps >3GB then i have the problem.
If i remove some maps then all is fine. It's definitely not my sdcard because i tried moving everything on internal memory and still get the same problem.
Any ideas that might help will be appreciated
stathis95194 said:
Well i think i might take you up on your offer. I can't get rid of the blinking problem.
I have tried everything. But i believe i have identified what creates the problem. If under iGO/content/map i have a lot of maps >3GB then i have the problem.
If i remove some maps then all is fine. It's definitely not my sdcard because i tried moving everything on internal memory and still get the same problem.
Any ideas that might help will be appreciated
Click to expand...
Click to collapse
It seems that although the above sys.txt file change made iGO run smooth as butter with just maps of one country, I added maps for all of Europe and it keeps freezing. Looks like I'll just have to add maps in whatever country I'm in!
stathis95194 said:
Thanks for the offer. I think i fixed it with a workaround.
I moved the iGO folder on internal memory but kept the "big" content folder on sdcard (which is what i needed anyway)
It seems to work fine now. I will test it again tomorrow when i will be driving and report back.
Click to expand...
Click to collapse
Hi,
trying to do the same with 'content' but i have tried many combinations of linked_root_list but cannot get it working from external card.
how did you do it?
i am rooted on standard rom.
R/W patch
gazzacbr said:
Hi,
trying to do the same with 'content' but i have tried many combinations of linked_root_list but cannot get it working from external card.
how did you do it?
i am rooted on standard rom.
Click to expand...
Click to collapse
You should patch first your M8 for 4.4.2 for R/W .
flash this: