i9001 CM9 alpha 5 navigation issue - Galaxy S I9000 Q&A, Help & Troubleshooting

I see that someone posted this in the main dev thread, but I can't post there and the solutions don't help.
Navigation and maps work only the first or second time I use them on this rom, after which they start crashing in a different way each time. Very weird.
Here's what I've done:
1: Installed the CM9 rom, cleanly:- full factory reset, wipe dalvik and wipe cache before and after.
2: Installed the GApps .zip
3: noticed that navigation and gmail etc. weren't included in the Gapps package. Not sure why. Installed them from the market.
4: Boot
Porblems:
5: Navigation works fine the first time, much faster gps lock than stock. Sometimes it works more times if I don't reboot, charge, or run other apps in between.
6: The second time, navigation gets stuck at the navigation logo after I choose a destination.
7: The third time, navigation wont even load - just a black screen. If I wait and the screen times out the phone goes into a state where the only way to get it back running is to remove the battery.
8: If I run the app and then go back to homescreen, next time the phone goes to sleep the same thing as #8 happens again. Trying again takes me back to one of the above options seemingly at random, but it never works again other than the first time.
What I've done to try a fix:
8.25: Reinstalled Gapps from .zip. Navigation may again work the first time, but back to failing after a try or two.
8.5: Reinstalled maps from market. No change.
9: Fix permissions. Same as above.
10: Full reflash from scratch, wiping everything. Same as above.
11: Selected internal GPS source in settings. No change.
12: Ticked all the location boxes in settings. No change.
13: Installed a different version of Gapps. Again same as above even though it was the gingerbread Gapps. Wondering if the ICS gapps package installed correctly in the first place?
14: Used GPS status to confirm that GPS itself is fine. It's just the app that's the issue. Perhaps other nav apps would work? Shame they all suck/cost money.
In the meantime I'm going to try the sygic free trial. Any ideas for what I could have missed?

Seems like these forums move too fast to be of any real help. Maybe I'll keep posting around the place til I can get Arco to respond.
For now I've give back to cm7. Navigation works fine now. I'll try cm9 again once it goes beta or maybe just wait for cm10

Related

[Q] NookieComb 4.13OC bugs

First off, this is a great ROM. Since I purchased my NC a couple months ago, I have had CM7 (up to nightly 32), Deeper Blue's 3.0v4 and Ultimate Droid and this one, IMHO works better even with a couple bugs and wonder if anyone else has had the same issues and found a workaround.
1) I get an error message that says "android.process.media has stopped working" and it force closes whatever media I am using except video and also affects the market when I try to download an app. I have cleared the dalvek cache and also reinstalled the ROM and I am still getting the error.
2) Issues downloading and sideloading apps. Some apps, mostly games and wallpapers will force reboot when I try to download or sideload them. For sideload, I have used Root Explorer and Easy Installer.
For first time installation of this ROM, format system, data and cache before the installation.
Worked fine for me.
Cheers!

[Q] How do I get apps2sd ext 4 working on the Nexus one with the latest Cyanogen Mod?

Hey guys, I'm loving my new N1, but I keep running out of room for applications, and I wanted to know if I could implement Apps2sd ext2/3/4 or w.e to make more room. I like to use Cyanogen Mod, but I'm not sure how to implement it. If someone could help me, that'd be great! Thanks!
Ditto.
Sent from my Nexus One using XDA App
Try S2E or Link2ext in the market, our go look up Darktremors. Depending on what you want, the apps should be more than sufficient...
danger-rat said:
Try S2E or Link2ext in the market, our go look up Darktremors. Depending on what you want, the apps should be more than sufficient...
Click to expand...
Click to collapse
When i use darktremors, it doesn't work, but if I type in a2sd reinstall, it says location is read only
Try to fix permissions via ROM Manager. Also, try flashing DT before you flash gapps...
danger-rat said:
Try to fix permissions via ROM Manager. Also, try flashing DT before you flash gapps...
Click to expand...
Click to collapse
I tried that; it didn't work. Also, when I run a2sd reinstall, and reboot, its stuck on rebooting
Try the DT thread... xD
isikh said:
I tried that; it didn't work. Also, when I run a2sd reinstall, and reboot, its stuck on rebooting
Click to expand...
Click to collapse
Not been my experience. Strange that. What works for me...
Boot to recovery of your choice.
Do multiple wipes, both cache + dalvik-cache. Though just one wipe each is likely enough, IMO. Also wipe sd-ext.
Write your CyanMod of choice.
Write your gapps.
Write your DarkTremors. Go with the latest, OR, as others are insisting, stay away from that and go with the previous stable release. Latest works great for me.
Reboot device.
Wait a good minute after arriving at lockscreen and reboot device from lockscreen, OR find Quick Boot in app drawer if your power button is gorked (you'll need a working power button to reboot from lockscreen).
After reboot, wait a good minute at lockscreen. Then Proceed to open terminal session and start playing with a correctly installed (hopefully for you) DT2ext.
Lots of experts out there, but this has always worked for me. If you still need guidance, search in DarkTremor's thread to be advised about your partitions.
zero2cx said:
Not been my experience. Strange that. What works for me...
Boot to recovery of your choice.
Do multiple wipes, both cache + dalvik-cache. Though just one wipe each is likely enough, IMO. Also wipe sd-ext.
Write your CyanMod of choice.
Write your gapps.
Write your DarkTremors. Go with the latest, OR, as others are insisting, stay away from that and go with the previous stable release. Latest works great for me.
Reboot device.
Wait a good minute after arriving at lockscreen and reboot device from lockscreen, OR find Quick Boot in app drawer if your power button is gorked (you'll need a working power button to reboot from lockscreen).
After reboot, wait a good minute at lockscreen. Then Proceed to open terminal session and start playing with a correctly installed (hopefully for you) DT2ext.
Lots of experts out there, but this has always worked for me. If you still need guidance, search in DarkTremor's thread to be advised about your partitions.
Click to expand...
Click to collapse
Thank you, I figured it out.
DT is the best choice, but S2E is simpler than DT, it's avaliable in market

[CM7/ICSP/MIUI][GPS FIX] Yet Another Software GPS Fix VERSION 2 - 12/13/11

Yet Another GPS Fix
YAGF Version 2
For users running AOSP Gingerbread (CM7) and ICS (CM9/ICS Passion) ROMs​
Why another GPS Fix?
This GPS fix is a modification of the GPS fix by strictlyrude27 (link). The newest builds of CM7 don't play nice with that GPS fix and hang at the kernel boot screen for 10 minutes waiting to download GPS LTO data.
This fix does several things differently:
It addresses the 10-minute hang time by removing GPS LTO data download altogether. I have no problem getting a GPS fix without it! You can see the test results below.
It uses a modified GPS library that actually reads config files (even if you don't have AngryGPS installed), now finally allowing Google's SUPL server to be used.
It lets the GPS use hot fixes now. After getting an initial fix, if you leave and come back to the GPS later you can get a fix in as little as 2 seconds.
It cuts out AngryGPS. You can still use it if you want to do GPS performance testing, but the configuration it writes will not be of any use. You can uninstall AngryGPS if you want now! This is to allow the fix to work properly even if you do not have AngryGPS installed.
Important for ICS users: If you are getting issues with GPS locks after deep sleep, you may need to try WallaceLau's addendum to this fix. As I am not having issues with GPS dying after deep sleep, I cannot vouch for the effectiveness of copying over HTC Desire GPS files, but as it does not overwrite any existing files, it should be fairly harmless.
Note for ICSP RC1 (v13): This fix is only halfway onboard. You should flash this fix after flashing the ROM and cleanup zips to get the proper configuration files.
What does this work on?
This works on the latest CM7 and CM9/ICS PASSION builds.
This has been tested with the stock CM7 kernel, Eugene373's Streamline kernel (EB7 build), and the Glitch V13 kernel.
Users have reported it working with MIUI as well.
I have not tested this on any other configurations! YMMV even on these configurations!
Testing method
To test the GPS effectiveless, the time to first fix (TTFF) was tested using the S/W test mode in AngryGPS. Interval 5 seconds, cold fix, with XTRA download enabled. Timeout was set to 255 seconds.
I wiped and reinstalled nightly 182 between each set of tests. The phone was connected to a wifi network during all the tests to obtain the best possible speed for XTRA data download.
10 TTFF data points were obtained for each test configuration. Error bars are calculated as the standard error of the mean (SEM) of each data set.
Test results
The stock installations of CM7 and the Glitch kernel do not have any sort of GPS fixes built in and fail to lock within 255 seconds. The Streamline kernel has a GPS fix but only acquired a lock 5 out of 10 times (50%).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Comparing only the GPS fix from strictlyrude27 and this fix:
What do the graphs mean?
This shows that these two GPS fixes essentially perform the same, and that removing LTO download (and the 10 minute hang time on boot) has no statistically significant effect on GPS performance.
In addition, one can conclude that using either Streamline or Glitch kernels offers significant GPS performance benefits over the stock CM7 kernel.
Is it safe to flash?
Most likely (though I offer no guarantee of this)! All this does is delete your old GPS fixes if they are present, delete the agpsd daemon that was causing problems on my CM7 Vibrant, and flash the gpsd and gps.conf that were in strictlyrude27's fix. If that fix didn't give you problems, this one definitely won't.
INSTRUCTIONS
Have CM7.1.0.1 or a newer nightly installed on your Vibrant
Transfer yagf2.zip to your phone
Turn off the GPS!
Reboot into recovery
Flash your kernel of choice (if you have not done so already)
Install yagf2.zip from wherever you put the file
Reboot and turn on the GPS. Enjoy!
Download below as an attachment
Mirror
Version 1 (Old version)
Thanks for this. You know, I still can't reproduce the bootloop issue; I'm running the latest nightly. I wonder if this is a kernel thing? I'm on Glitch V13..
I'd only had working GPS on one 2.2 rom since I'd gotten the phone in July of last year...until I'd flashed this! Thank you so much!
Sent from my SGH-T959 using XDA App
strictlyrude27 said:
Thanks for this. You know, I still can't reproduce the bootloop issue; I'm running the latest nightly. I wonder if this is a kernel thing? I'm on Glitch V13..
Click to expand...
Click to collapse
I think it's only in the more recent builds since they redid the init system that it happens. What nightly are you using, or are you on stable? I'm guessing the init scripts were reordered so that the network got initialized after the files in /etc/init.d were run, but I haven't really looked that much into it.
Interestingly enough, they did add in a gpslto service in init.aries.rc that calls a nonexistent file, /system/bin/get-gps-lto, but I was playing around with it and couldn't get it to work.
Already had a pretty stable gps running with Streamline Kernel and CM7 nightly (kb5)
it always took about a minute for it to load up, but it was getting to a point where I could expect a gps lock with a bit of hopeful regularity.
After flashing this, my first attempt for a gps lock would yield no results no matter how long i left it on, and if i exited out of gps test, the gps icon would never reappear. i attempted to delete gps data and do some tiff tests as well, but for some reason the gps icon will only initialize once per boot, and i've never gotten anywhere with it.
Should I re-flash streemline AFTER installing this patch? Do you recommend deleting gps data before you flash?
I've restored a pre-fix backup and reflashed twice now, yielding the same results.
Might try again tomorrow. I was very hopeful for this one.
Streemline has already worked wonders. I'm confident gps will only get better with the vibrant.
edit: hrm. I might have gone about this incorrectly. You have a gpsfix.zip file attacked to this post, yet your instructions are to flash yagf1.zip. I had assumed that you meant your gpsfix.zil file and perhaps made a type or something. going to attempt to flash one more time with the specific mirrored yagf1.zip file. What is the gpsfix.zip file attached to this post? It's not mentioned.
edit 2: also, step 3. in the first post is to flash the kernel of your choice. if i'm already on the kernel of my choice is this necessary? must we reflash the kernel AND the fix in one go from cwm before booting up?
edit 3: HOOOOOLY CRAP! THIS IS AMAZING! I used a kernel cleaning script in cwm, then flashed streamline, then the yagf1.zip file. booted up. and got a lock within 10 seconds. it's the fastest this puppy has ever EVER fired up. I'm so very impressed. Well done sir. This is the best gps signal i've ever gotten, and i was already impressed with the progress with eugenes kernel. Give this a try people!
edit 4: dumb question. in angry gps, what exactly does 'delete gps data' do. does it negate any of this fix? everyone seems to recommend it, but i don't want to ruin any fixes i've flashed.
twotone8 said:
Should I re-flash streemline AFTER installing this patch? Do you recommend deleting gps data before you flash?
Click to expand...
Click to collapse
Reflashing the kernel will overwrite this GPS fix, so no, don't reflash it.
twotone8 said:
edit: hrm. I might have gone about this incorrectly. You have a gpsfix.zip file attacked to this post, yet your instructions are to flash yagf1.zip.
Click to expand...
Click to collapse
Oops. I didn't notice that, you're absolutely right. They're the same file, just with different names. I decided to rename it something with a later letter in the alphabet so I could just hit the vol+ button in recovery a few times to get to the file more quickly I've renamed it now.
twotone8 said:
edit 2: also, step 3. in the first post is to flash the kernel of your choice. if i'm already on the kernel of my choice is this necessary? must we reflash the kernel AND the fix in one go from cwm before booting up?
Click to expand...
Click to collapse
nope, just go ahead and flash this on top of it. This cleans up any interfering GPS fixes that might have been flashed alongside your kernel.
twotone8 said:
edit 4: dumb question. in angry gps, what exactly does 'delete gps data' do. does it negate any of this fix? everyone seems to recommend it, but i don't want to ruin any fixes i've flashed.
Click to expand...
Click to collapse
I think it deletes the temporary data about the satellites in current view generated by gpsd that can be used for a "hot fix" within the next few minutes. Deleting it forces your GPS to do a "cold fix" (assisted by the xtra data and network location). It doesn't negate this fix.
rexrbgh said:
I'd only had working GPS on one 2.2 rom since I'd gotten the phone in July of last year...until I'd flashed this! Thank you so much!
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I finally have a working GPS on my Vibrant. This is the only fix that has worked for me. Every time I turn my GPS on now it actually stays locked on to satellites for the whole time I use it. This has NEVER happened to me before. Thanks alot.
Never had working gps on gingerbread until now. Thank you very much kind sir.
Sent from my SGH-T959 using xda premium
Seemed to work, nice work.. thanks!
Sent from my SGH-T959 using xda premium
Excellent work. I never quite got there with previous GPS fixes for CM or other 2.3.x ROMs.
I love using Waze to monitor traffic conditions, report problems, etc. Lack of reliable GPS had kept me on 2.2. It takes a little while for GPS to get a lock, but I suspect that will improve.
So, do you have a tip jar?
---------- Post added at 07:03 AM ---------- Previous post was at 06:58 AM ----------
twotone8 said:
edit 3: HOOOOOLY CRAP! THIS IS AMAZING! I used a kernel cleaning script in cwm, then flashed streamline, then the yagf1.zip file. booted up. and got a lock within 10 seconds. it's the fastest this puppy has ever EVER fired up. I'm so very impressed. Well done sir. This is the best gps signal i've ever gotten, and i was already impressed with the progress with eugenes kernel. Give this a try people!
Click to expand...
Click to collapse
Which script did you use?
This thing works...
Sent from my SGH-T959 using XDA App
The GPS attempts to lock in maps then the GPS lock icon/indicator never shows up again when I try any other program that requires GPS... until I reboot.
Flashed the latest nightly with everything wiped
Eugene streamline
YASGPS fix
I think I'm in the "results may vary category". From what I've been reading, that is because Vibrant hardware differs from one another. The one I'm using was manufactured Jul/06/2010.
Don't give up yet. That's exactly what mine used top do when I flashed this. just keep trying things. what worked for me one time was simply to disable GPS before a restart, then re enable it and everything worked great.
I had it working perfectly, them had to do a nandroid restore, and that problem came right back. Somewhere between reflashing kernels, fixes, restarts, and finally just turning of GPS before restarting. every thing works great again.
Sent from my SGH-T959 using XDA App
jsparakov said:
The GPS attempts to lock in maps then the GPS lock icon/indicator never shows up again when I try any other program that requires GPS... until I reboot.
Flashed the latest nightly with everything wiped
Eugene streamline
YASGPS fix
I think I'm in the "results may vary category". From what I've been reading, that is because Vibrant hardware differs from one another. The one I'm using was manufactured Jul/06/2010.
Click to expand...
Click to collapse
Can you try fixing permissions and clearing your dalvik cache in recovery? If that doesn't work can you send me a logcat?
chui101 said:
Can you try fixing permissions and clearing your dalvik cache in recovery? If that doesn't work can you send me a logcat?
Click to expand...
Click to collapse
I've cleared dalvik cache many times already. Edit: but I'll continue to do so every time I make an attempt.
I'll go ahead and try those two with the nightly. Let me know if you have any particular way of doing logcat other than adb (I don't do this very often).
jsparakov said:
I've cleared dalvik cache many times already. Edit: but I'll continue to do so every time I make an attempt.
I'd be very happy to follow those other two suggestions. Do you have any link to instructions on how to do those two things properly (what and how to fix the files + creating a logcat)?
Click to expand...
Click to collapse
Fixing permissions is under the 'advanced' menu in CWM recovery, I believe.
You can do a logcat on the phone by opening up the terminal emulator and typing logcat. You can redirect output to a file with -f (i.e. 'logcat -f /mnt/sdcard/logcat.txt'). Run it before you open up Maps, then let it run in the background while you open up maps. When you are done, close it with CTRL-C (VOL- + C in the terminal emulator).
Alternatively, you can do this from your computer by using adb if you have it installed. Just do adb logcat -f /mnt/sdcard/somefile.txt and it'll save a logcat to the same directory as it would have on your phone. CTRL+C exits.
markinct said:
So, do you have a tip jar?
Click to expand...
Click to collapse
Nope, but I'll take atinm's lead and suggest that you show thanks by signing up to be an organ donor!
Thanks a lot for your efforts and help, chui. I had to revert to Stable 7.1.0.1, hopefully that doesn't make a difference. Radio is KB5.
(Any flashing and permissions was done in recovery)
Recover to Stable 7.1.0.1, cleared cache, cleared dalvik, reboot
Flashed Ultimate Cleaning Script v4, flashed EB-Streamline, reboot
Flashed yagpsf, reboot, fixed permissions, reboot
Before Google Maps logcat (permission denied, dev/log/main is 0 bytes)
Open Google Maps
logcat post-Google Maps (again, permission denied for logcat)
Result: GPS icon/indicator works once. If I try to reload maps or turn my screen back on, the indicator no longer comes up. For some reason, logcat isn't being written into to it. The permissions for dev/log/main is rw-rw--w-.
Edit: I just tried alogcat, and it's giving an overwhelming amount of output. So I think it's because I don't know how to use logcat.
---------- Post added at 11:16 PM ---------- Previous post was at 10:51 PM ----------
Alright, got some logs, I'll be PM'ing you.
jsparakov said:
Thanks a lot for your efforts and help, chui. I had to revert to Stable 7.1.0.1, hopefully that doesn't make a difference. Radio is KB5.
(Any flashing and permissions was done in recovery)
Recover to Stable 7.1.0.1, cleared cache, cleared dalvik, reboot
Flashed Ultimate Cleaning Script v4, flashed EB-Streamline, reboot
Flashed yagpsf, reboot, fixed permissions, reboot
Before Google Maps logcat (permission denied, dev/log/main is 0 bytes)
Open Google Maps
logcat post-Google Maps (again, permission denied for logcat)
Result: GPS icon/indicator works once. If I try to reload maps or turn my screen back on, the indicator no longer comes up. For some reason, logcat isn't being written into to it. The permissions for dev/log/main is rw-rw--w-.
Edit: I just tried alogcat, and it's giving an overwhelming amount of output. So I think it's because I don't know how to use logcat.
---------- Post added at 11:16 PM ---------- Previous post was at 10:51 PM ----------
Alright, got some logs, I'll be PM'ing you.
Click to expand...
Click to collapse
I don't know if this helps but i'm not seeing any issues with KA7
kdf2883 said:
I don't know if this helps but i'm not seeing any issues with KA7
Click to expand...
Click to collapse
I've been using KA7 for the longest time now just before flashing it just for this. Yes, the problem persisted using BALI and Software GPS Fix v1.5.1.
In any case, I'll try KA7 again more methodically (KA7 + Clear Dalvik + Fix Permissions) and see if that allows the GPS indicator to work more than once per boot.
Out of curiosity, what's the date on the box/under-battery for your Vibrant? Mine is Jul/2010.

Ubuntu Touch SGH-T999

Okay everybody, I want to start a WIP on this as it seems that we can get somewhere. The last dev seems to have dropped the project so I picked it up. :good:
***NOTE*** This is meant for development/testing purposes ONLY. It is in NO WAY for the faint of heart and you must follow ALL instructions or it will not boot! You have been warned!
As of 5/7/2013, the following things are working:
Camera (flash works, it takes pictures)
Sound (the only reason I know this works is because the shutter noise goes off in the camera app, there is no other way to test this right now)
The test apps (browser, notepad, gallery, camera, browser, phone, calculator, calendar, clock)
Power button (phone goes to sleep and wakes, hold the power button down to shut off the phone - the shutdown takes a second because it shuts down just like a linux kernel would - plug it in the charger to test this, it will vibrate once it is off)
Not working - just about everything else. Most items are still placeholders and there is a stability issue where the apps all close themselves after a few seconds which I am trying to figure out. There is no data or cellular connectivity of any kind. This may be fixable, however, since I was able to get the camera working by pulling the prebuilts from a different CM version. I'll keep experimenting with this. If you put the device to sleep, it does not wake up to the same brightness (it is dimmed) and you can not adjust the brightness right now (working on this as well, its a permissions issue in the kernel source but I haven't been able to narrow it down yet).
It is VERY finicky about how it is installed. I won't give any support for anything but TWRP 2.5.0.0
To install:
-Download the kernel zip and the latest daily from Ubuntu (I will post links later)
-Backup your current ROM in its entirety using TWRP - check every item on the list or you may have to go to a fresh install of your version you were running previously.
-In TWRP (once again, make sure its 2.5.0.0 because these are 2.5.0.0 specific instructions), factory reset but do an advanced reset, check dalvik, data, system, and cache. ***MAKE SURE THAT YOU DON'T FORMAT YOUR MICROSD***
-Install the kernel zip and do not wipe cache or dalvik
-Install the Ubuntu preinstalled image, once again make sure you do not wipe the cache or the dalvik.
-Do not do anything else, no fixing permissions or anything, just reboot
-Wait about 2 minutes for the lock screen to come up and then you can use it
I will keep working on the kernel - the other functions will not work until Ubuntu implements them.
This is my first time working with actual development - if anyone wants to give me a tutorial to get my project up on GitHub so everyone can work on it, I would be more than happy to do so.
Here are the links:
Kernel built 5/7/2013: http://d-h.st/185
Latest Ubuntu Touch base: http://cdimage.ubuntu.com/ubuntu-to...current/raring-preinstalled-phablet-armhf.zip
Since the source has been moved to Raring Ringtail, there should not be a need to update that link. Please note that the 5/7/2013 build is the one that I tested and be sure to let me know if it gets broken in the future.
Enjoy everyone and once again, if you want to contribute, I'm more than happy to set up a GitHub, I just need some basic help getting it started.
How about now since they are realeasing daily builds
Sent from my SGH-T999 using Tapatalk 2
Sweet!
if you need testers or people to try it out let me know

There is something wrong with your data partition ....

Hello World,
before I explain my problem, I am most humbly asking for one small favour:
Please(!!) nobody give me any advice along the line of: Just do a factory reset and start from scratch
I've got almost a thousand apps installed on my system and I'm in no mood to even try to reconfigure it all over again.
Some time ago I installed the latest beta of Cyanogenmod on my Samsung Galaxy Note Tablet SM-P900.
After some time I encountered so many quirks with it, that I decided to flash back to the latest stable build 12.1-20151029 (Android v5.1.1).
Since I was always able to upgrade w/o wiping data, I did the same here, but right after the downgrade the system started misbehaving.
Matter of fact, I could only boot through to the desktop, once I had removed some google.* related dirs from the data/data location. Right afterwards I reinstalled the affected apps from backup and that fixed that.
Unfortunately during the proces of peeking and poking in data/data I messed up some ownership/permission settings.
I also managed to fix those via an old backup (via: chmod/chown --reference), *but* now I am getting a popup message telling me:
"There is something wrong with your data partition..." everytime I reboot the system.
Afterwards I can work just fine with the tablet, but every 3rd or 4th day it suddenly reboots - then being stable again for another couple of days.
If I could only find out what fault this messages refers to, I could fix it manually - but I couldn't find anything useful by reviewing the logcat info.

Categories

Resources