yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 10.1 Android Development] Mischa42:
Hi folks,

I've an issue with Google Maps. I can't start it always crashes. I'm running Homemade v1.9 (from 27th October 2014) and latest version of maps (9.0.0). I tried to clear cache and data in app settings but did not work. If I start maps it asks for some questions (accept terms, location bla bla) and than it crashes.

Update: Found workaround: Deinstall Maps update (to version 8.4.1 coming with micro Gapps), clear cache and data.
[Galaxy Tab 10.1 Android Development] Prowler665:
Just give it a try with the screen-lock. I have a strong feeling that the problem might be caused by some incompatible settings that are inherited by dirty-flashing or restoring settings from backup - althou I usually only restore APN, WLAN, the accounts and maybe the wallpaper? Screen-lock is working fine here, tested with PIN and password.

And yes, Maps 9 is crashing here too. Restoring from backup to 8.4.1 did the trick.

Regards ;)
[Galaxy Tab 10.1 Android Development] BoulderGeek:
OK, as you expected, things are working fine even with screen lock enabled.

Could have been a series of dirty flashes of the nightlies. Or app interaction. Or sunspots, gremlins, comet landings, etc.

After a clean wipe and selective application management, it does appear that my tablet is working fine. I appreciate all of the attention!
[Galaxy Tab 10.1 Android Development] Prowler665:
Did you try a clean install (wiping /data, /system, /cache and /dalvik-cache before flashing the ROM)? This was working for me, using Titanium-Backup to restore the user-apps only.

Regards ;)

---------- Post added at 06:17 PM ---------- Previous post was at 06:12 PM ----------

I vote for comet landings :D

Glad it helped :)
[Galaxy Tab 10.1 Android Development] BeeGee_Tokyo:
I vote for sun erruptions (joke!!!!)

Serious, if you guys have problems, try a clean install after factory wipe. I know it hurts to reinstall all applications again, but Titanium Backup is really helpful with this.
[Galaxy Tab 10.1 Android Development] BeeGee_Tokyo:
You compare apple with peaches! Of course your quad-core 1.6GHz S4 is smoother than your double-core 1GHz 2 years old tablet. Do you really expect that such old hardware can be as fast as a modern smartphone?
[Galaxy Tab 10.1 Android Development] Technical:
No BeeGee, I know the differences... I'm just comparing the "experience" using one and other and, after all, I want the faster tablet I can get. If I can't get it faster, patience.

---------- Post added at 09:45 PM ---------- Previous post was at 09:28 PM ----------

Beegee:

1. Can you upgrade DashClock widget to the latest

2. Also Orbot to 13.0.7 (not sure if it is comming with the ROM).

I'm testing all my apps and will post from time to time.

Would it worth to keep inside ROM the Apollo app?
[Galaxy Tab 10.1 Android Development] BeeGee_Tokyo:
Got it.

Will check it.
[Galaxy Tab 10.1 Android Development] AtomicAardvark:
Hi there all,

Just some feedback after 4 days on the ROM.

I have OC'd to 1.4Mhz. No issues with screen glitches, self re-boots or crashes so far.

The stock UI felt a bit slow to respond, but the "feel" of the tab was better after I installed Apex Launcher Pro. I still did not like it as it was not snappy. I did a "dirty" flash of the ROM again and it felt a bit more snappy. Pulling down the notification panel and so is still a bit on the lazy side. Overall though I am happy with it.

Battery life seem to be fine. She sleeps nicely and I got 0.6%/h battery loss last night. She is currently at 19% loss after just over 13hrs at 1.4%/h.

Also to note, I did the performance settings as per OP.

Next I want to see how she performs at 1.5Mhz and above.

So far, great work BeeGee. I will stay with ROM even if your Ganberou ROM feels a bit more snappy.

Regards.
[Galaxy Tab 10.1 Android Development] Jaegermeiste:
FWIW I've been on the ROM for a few days too. A pretty good experience, although I've had annoying GAPPS problems (both PA and Banks) that seem to persist through multiple clean flashes. Oh well. My Tab freezes within a minute or two of overclocking (even to 1200), if not near-instantly. So that's out. What I found does help performance is setting the minimum processor speed to 400-something. I found that everything from the UI to Minecraft Pocket became significantly more responsive. I played with governors, but I didn't find one that performed better than interactive and I don't think smartassv2 works properly. I haven't successfully messed with schedulers - I get instant freezes. I also set maximum background processes to 3.

I might bump the minimum proc speed up another notch - but in my use case I don't really care about battery life and responsiveness is far more important.

Thanks to BeeGee and his predecessors for keeping this thing up to date!
[Galaxy Tab 10.1 Android Development] BeeGee_Tokyo:
[MENTION=4711963]Jaegermeiste[/MENTION](r)

The reason why your GApps problems survive a clean flash is that as long as you do not wipe system before flashing (factory reset does not wipe system!!!) the GApps survive the flashing.

The reason is that Nameless build in the updater-script a routine that calls any batch saved in system/addon.d. Most GApps installations place there a batch called 70-gapps.sh. This batch file saves all GApps apks and libs before the flashing wipes system and restores them just before the flashing is finished.

Need to add this to the post#1. Factory reset != full system wipe.

Sorry for the problems you had.
[Galaxy Tab 10.1 Android Development] Jaegermeiste:
I mounted and wiped system twice. Didn't really help. Thanks though.
[Galaxy Tab 10.1 Android Development] Olivier V:
Is it just me or is the touchscreen sometimes unresponsive for everyone?
[Galaxy Tab 10.1 Android Development] DefQoN_BE:
This isn't ROM related i guess, it could have something to do with your hardware, try another ROM and look what it says or try touchscreentune, never heard anyone complaining about the touchscreen, mine works perfect
[Galaxy Tab 10.1 Android Development] sherri:
I have had too many random reboots to use this. What I saw, I loved, and I hope I see a more "stable" version.

Heading back to BeeGee_Tokyo's Ganbarou ROM. Never had a hiccup using that!
[Galaxy Tab 10.1 Android Development] BeeGee_Tokyo:
Strange :confused:. I use this ROM now for 2 weeks :laugh: without any random reboot. But glad you are happy with my Ganbarou ROM :highfive:.
[Galaxy Tab 10.1 Android Development] sherri:
Honestly, back on Ganbarou. Works flawlessly, so thank you!
[Galaxy Tab 10.1 Android Development] Duvel999:
No reboots here, Rom works great..:cool:

Sent by my Z1 with XDA Fax
[Galaxy Tab 10.1 Android Development] AtomicAardvark:
Hi all,

Something that SEEM to have helped my tab to run a bit more responsive is sftrimming. Found under Device Control/Tools/Tasker.

The following article explained it a bit to me:

http://www.xda-developers.com/android/yet-another-reason-to-update-to-android-4-3-trim-support/

Has anyone used it and could give a bit of feedback?

Regards
[Galaxy Tab 10.1 Android Development] P500Alive:
My Apr 13 build works fine without reboots. Only using Chrome requires me to reboot the tablet because it becomes really sluggish.

So, IMHO this is very stable but performance wise, it is really slow, even after tweaking as described in 1st post.

I tried to force the TRIM with the app from XDA and it says my kernel does not support it, enabled it in tasker to run every 5 minutes, waited an hour but the tab is the same as before, really lagged.

I have NO apps installed other than gapps and Chrome, clean install from format.
[Galaxy Tab 10.1 Android Development] Vampiro2000:
No problems here! Running stable [MENTION=1024191]1504[/MENTION]... Only issue is with hw and default running apps that revert to defaults... The rest very smooth. using Google default launcher...
[Galaxy Tab 10.1 Android Development] Lt.col.johncross:
Any Hope for the p7500 brother the forgotten sch i905??

I have found the 4.2.2 rom http://xdaforums.com/showthread.php?t=2074202

So does that meant the resources for the sch i905 would be available to port this rom also????

If they are could this happen???
[Galaxy Tab 10.1 Android Development] BeeGee_Tokyo:
The ROM you found is Android 4.2.2, this one is 4.4.2. I tried once to build my Ganbarou ROM (up to Android 4.3) for the SCH-I905, but I cannot test it and at the tester it never bootet.

Sorry, I don't think I can do this.
[Galaxy Tab 10.1 Android Development] MagusWRM:
Mine is rebooting only sometimes after changing wireless network (like just after a forced connection or turning it on/off) and one time after a bluetooth file transfer.

My device is a P7500 with this custom modem: http://xdaforums.com/showthread.php?t=1875024

Ah, and thanks for the amazing rom! :good:
[Galaxy Tab 10.1 Android Development] mirskym:
Works great on my P7510, no random reboots.

Thanks for giving my old tablet new life!:good::good:
[Galaxy Tab 10.1 Android Development] Prowler665:
Full Ack :D

...and thanks for your work btw :)
[Galaxy Tab 10.1 Android Development] *mondman*:
I have the same problem PROWLER665.
[Galaxy Tab 10.1 Android Development] Prowler665:
It's all in the posts above, but let me do a quick summary:

- Backup all of your apps and settings first! Titanium-Backup is working fine for me...

- Boot into the recovery of your choice and wipe /data, /system, /cache and /dalvik-cache.

- Flash the ROM and GApps, optionally a lighter boot-animation too.

- Reboot and do a standard-setup without installing or restoring any apps or settings yet.

Wait a little and test if there are any problems, especially test if the tab will recover from a locked screen!

If the tab is behaving as expected, now would be a good time to boot into your recovery and do a nandroid-backup ;)

This done, start restoring the user-apps with Titanium-Backup. Check for any hickups and consider another nandroid-backup if all user-apps are installed and the tab is still working fine.

That's it ;)
[Galaxy Tab 10.1 Android Development] Grop:
reboot after locked screen

Noticed some undefined problems after setting up: with nova launcher, device control settings and charger connection. So I tried several options to find out what might cause the issue of not coming out of sleep after screen locked and only a reboot was possible. Everytime I did a full and complete setup (Rom, PA gapps mini, additional launcher (nova) and a restore through google backup, finally changed settings for smoothness as adviced in OP)

Did a clean install with only factory reset. Installed everything as usual. No success. Recovery from locked screen resulted to a reboot.

Then a new install, clean, in advanced wipe mode with option: wipe /data, /system, /cache and /dalvik-cache. Installed everything as usual but left Nova launcher away and used the google launcher. Problem with rebooting after locked screen after a while remained especially when charger was connected and after that every time also without charging.

Then this morning a new install with advanced wipe options, no nova launcher and did not change the settings in the settings/device control as adviced in the OP for smoothness. No trouble so far.

This last test resulted untill now in a good working tablet.

So I assume there are first of all some problems with the

device control settings in the settings menu

. I noticed that, as soon as I changed the CPU settings to 1400 or 1200 max, the min. settings and the setting to save cpu by restart, I could not adjust these figures anymore because no settings showed up, just a blank line appeared.

Hope this will help you all to find what the problem might be and a possible solution.
[Galaxy Tab 10.1 Android Development] Prowler665:
Nova-Launcher is working fine here, restored from backup and I didn't notice any problem with the charger yet. Also setting max. clock to 1400 MHz is performing flawless here.

I usually don't raise the min. CPU clock nor change any other settings apart from oc'ing to 1400 MHz, so I just tested it and I can confirm that raising the min. CPU setting to 312 MHz resulted in failing to come back from a locked screen! Simply reverting the settings didn't help to fix the problem. I had to restore from nandroid-backup to fix this...

So I guess it's safe to say that there are some problems with the device-control. I'd suggest that the smoothness-advice should be handled with care regarding the CPU-min. settings for now.

I also ran into the problem with the cpu frequency settings not showing up a while ago. In my case it was caused by a missing or not working su-binary that somehow got killed by installing AdAway using /system/etc/hosts as the hosts-file to be used. Simply reinstalling the rom and changing the hosts-file fixed this for me. I'm not sure how the su-binary got affected thou...

So if no settings show up for the cpu in the device-control, check if su is working first...

Regards :)
[Galaxy Tab 10.1 Android Development] Mischa42:
Just installed Homemade v1.20 (nameless-4.4.4-20141108-p4wifi-n-HOMEMADE) and it works without any issues. I'm coming from v1.19 and did not wipe anything. :good:
[Galaxy Tab 10.1 Android Development] genghisdani:
Hi all! I'm excited to see that there are still people that care about this old junker. One question before I jump in, is this usable as a daily driver? I want to use this to take notes at school; but if it's going to be crashing, that's gonna be a problem. Other uses may include reading books, comics, and watching anime, but I'll survive if those don't work perfectly.
[Galaxy Tab 10.1 Android Development] Prowler665:
The problem described above is only a minor hickup. I suggest making a nandroid-backup after the basic setup and especially before trying any settings in the device-control.

That said, the rom is pretty solid. Watching HD depends on the source, but using MX-player, it's working pretty good. CoolReader is a charm for ebooks, but it's all up to you. Just give it a try ;)

Just remember that NamelessRom is work in progress. Since there is no way to test every possible scenario, on every update something might break. Simply make a backup before playing with any updates and you're fine. You might also wanna stick to the homemade roms since opposed to the nightly's they are checked at least once :D ...just kidding ;)

Regards :)
[Galaxy Tab 10.1 Android Development] BeeGee_Tokyo:
Correct, the HomeMade ROMs are flashed on my tablet and tested (at least a quick check) before I release them.

The nightlies are just distributed without specific testing.
[Galaxy Tab 10.1 Android Development] Grop:
BeeGee_Tokyo, can you confirm the issue caused by changing the cpu settings in Settings/Device Control as we mentioned here in #1184 and #1185? Hope you have a solution for it.

Thanks for your work.
[Galaxy Tab 10.1 Android Development] BeeGee_Tokyo:
I can confirm that the device apk has a problem once you changed the min settings. And I get the same problem with the lock screen after I changed it.

I cannot test max CPU speed, because as soon as I set it to 1200MHz, my tablet freezes immediately. Seems the CPU in my tablet doesn't like overclocking at all.
[Galaxy Tab 10.1 Android Development] BMWPower06:
Help! After the flash, mine is not recognizing that it is plugged into the computer.

I flashed the ROM with no issue, then when I went to flash Gapps it said the file was too big and I would have to get the modular mini gapps. So I rebooted in hopes of dropping the modular mini onto the device, but I can't adb and my computer doesn't recognize the device as storage.

please help! Thanks!
[Galaxy Tab 10.1 Android Development] BeeGee_Tokyo:
Post#3 and in every post for a new release:
[Galaxy Tab 10.1 Android Development] BMWPower06:
you're a lifesaver! :good:
[Galaxy Tab 10.1 Android Development] Prowler665:
The nightly and homemade-builds use different kernels. While the nightly builds still use kaspar_h's kernel, I assume you and Grop use twa_priv's. It might be a coincidence but they might behave differently in conjunction with the device-control app.

Regards :)

---------- Post added at 07:49 AM ---------- Previous post was at 07:22 AM ----------

I just updated the device-control app to 0.7.2 but still no luck. Behaviour is exactly the same.

Regards :)
[Galaxy Tab 10.1 Android Development] Prowler665:
I played around a little more and reverted the device-controll app to version 0.7.0 as was present in nameless-4.4.4-20141019-p4-WEEKLY and it is working again as expected. I'm now using nameless-4.4.4-20141116-p4-WEEKLY with device-control v0.7.0.

It seems like this is the only relevant commit in the changelog for nameless-4.4.4-20141026-p4-WEEKLY

So a quickfix would be to set the version to be build into the rom to 0.7.0 again (...if the app is build from source that is...). Nevertheless, the maintainer of the app should be informed and automatic updates turned off for this app.

Regards ;)
[Galaxy Tab 10.1 Android Development] BMWPower06:
I flashed the latest nightly and everything seems to be working fine except for Google Maps, it will always FC a few seconds after opening the app. Does anyone have any ideas?

Thanks!
[Galaxy Tab 10.1 Android Development] Prowler665:
Try using the search funktion ;)

Google Maps search results

Regards :D
[Galaxy Tab 10.1 Android Development] aduhai:
Google maps ver 9 used neon. Not compatible with tegra . use google maps 8 below.
[Galaxy Tab 10.1 Android Development] BMWPower06:
I love this forum :highfive::good:
[Galaxy Tab 10.1 Android Development] Prowler665:
On a second look this looks promising too. Lots of changes usually mean trouble ;)

Regards :)
[Galaxy Tab 10.1 Android Development] Grop:
Nice work Prowler665. At least now we are sure about what is causing the trouble, and we know how to avoid this for the time being.

The only error I still have is that when I leave the tablet on, and charging during the night, the system crashes, restarts and hangs at the red/white android logo. A new start is necessary and this results in starting in the basic settings menu (language, time etc.). Also my business email (office365) has been wiped then.
[Galaxy Tab 10.1 Android Development] Prowler665:
One thing you can try is to leave the tab connected to your pc over night and have adb logcat running on your pc. This way you might catch the trigger for the crash. A simple adb logcat > log.txt should be sufficient. adb bugreport might also help shed some light on this strange behaviour, but the output usually is massive and hard to read.

Sounds almost like you are loosing your /data partition. Reformating your /data partition might help, but make sure to do a backup first!

EDIT:

Formating /data also erases your internal storage (/sdcard) - so make a backup to your pc!

You can restore the data with adb push.

Regards :)
[Galaxy Tab 10.1 Android Development] Mischa42:
Hi, I had the same issue as well (see some post ago) and uninstalled Google maps so that I got version 8 back (part of the gapps zip file you installed). Deselect the auto update function in Google Play for Maps and you will stay with a running version of maps :)

Cheers,

Mischa

---------- Post added at 03:34 PM ---------- Previous post was at 03:09 PM ----------

The restart and hang at boot animation while on charger over night happened to me only once. After a restart everything was okay (nothing wiped or lost). Could not replicate yet.

Maybe it was full moon or on the 13th :laugh::laugh:

Cheers,

Mischa
[Galaxy Tab 10.1 Android Development] Sharke08:
Missing SD card files

Installed Nameless Rom today, my original SD card files and folders are not visible within the rom when using ES file explorer. It appears the ROM has created a new file directory.

When I enter clockworkmod bootloader and navigate sd card I can still see the original files. I have some vpn files and other apps i'd like to access, anyone know how to navigate to the old sd card files?
[Galaxy Tab 10.1 Android Development] Prowler665:
Looks like you are using an outdated recovery. Starting with android 4.2 the files are in /data/media/0.

Using a root file manager or shell, create a /data/media/0 directory if it doesn't exist already, and then move all the other files from /data/media into the 0 subdirectory, and it should become visible within Android again.

If you use this version of ClockworkMod for backups, you may find that it can no longer find your backups directory afterwards, because it's still looking for /data/media/clockworkmod, not /data/media/0/clockworkmod. You can fix that by creating a symlink in the old location. From a root shell, run these two commands:

cd /data/media

ln -s 0/clockworkmod clockworkmod

Or simply upgrade your recovery.

Regards :)
[Galaxy Tab 10.1 Android Development] Sharke08:
I'm working with Rom Manager on a P4WIFI Galaxy Tab. It has my recovery listed as ClockWorkMod 6.0.3.1. Should i flash something newer? Any apps i can use to do that?
[Galaxy Tab 10.1 Android Development] Prowler665:
I never tried RomManager but CWM 6.0.3.1 looks kinda old to me. I would recomend using TWRP since you can get the latest versions for our tab. Links are provided in the first post or in my sig. I don't recall if the files are moved automatically to the new location, but that can be easily done with ES file explorer.

You can install TWRP like any other ZIP with CWM. After that you just boot into TWRP as your recovery.

Make sure to read the first few posts and refrain from using the device-control to set cpu-frequencies for now. This way you're good to go ;)

Regards :)
[Galaxy Tab 10.1 Android Development] paiktaras:
i make the solution for the Smoothness advice .

The first step write overclock cpu.... my device have max 1700, to place it in this unit? Is safe so high ?
[Galaxy Tab 10.1 Android Development] Grop:
Don't use the smoothness advice at this moment. It causes some trouble. Read a couple of pages back about the problems.
[Galaxy Tab 10.1 Android Development] paiktaras:
Please sent me this post if you can

sent from my Oneplus One
[Galaxy Tab 10.1 Android Development] Prowler665:
Take a look here for a quick workaround.

Regards :)
[Galaxy Tab 10.1 Android Development] Skippernl:
Tablet got stuck in bootannimation.

Started recovery checked the data partition. My apps are there.

Tried fix-permissions got back -> Fix permissions is not valid when a factory reset is issued. (there are not the exact words)

Tablet was on juice for more than 24h.

Recoverd with the latest backup.
[Galaxy Tab 10.1 Android Development] Prowler665:
Without any detailed information noone will be able to help you in any way... You may try the crystal ball department thou ;)

That said, this is some of the information that is needed in every bugreport or help request...

- What device are you useing (p4/p4wifi)?

- Which Rom did you try to install (version, hommade or nighty)?

- What Rom are you coming from (stock, other costom, previous nameless)?

- What recovery are you using (CWM, TWRP, version)?

- Did you try to get a log?

To get a log of the boot-process...

- Turn off your tab and connect it to your pc.

- On your pc start adb logcat > boot.txt.

- Start up your tab.

- When done hit ctrl+c on your pc to exit adb.

The same should work for adb shell dmesg > dmesg.txt.

Regards :)
[Galaxy Tab 10.1 Android Development] Skippernl:
Hi,
[Galaxy Tab 10.1 Android Development] Prowler665:
Way better ;) Let me see if I get this right...

You tried to dirty flash HomeMade version 1.20 over a HomeMade version 1.18 or lower. The Rom installed ok, but crashed later at night (crystal ball)? You reverted to your previous installation and the tab is working as expected again?

Did you follow the "smoothness-advice" and changed the cpu-frequency settings? If so, there is a major bug in the DeviceControll app. On upgrading from HomeMade v1.18 to a newer rom, you will need to do a clean install and either downgrade the DeviceControll app to version 0.70, or refrain from using it at all.

B.t.w. ... If interleaving versions while updating to the newest rom, it is always a good idea to do a clean install.

If the error still persists, try to get a log ;)

Regards :)