I use my captivate as my primary phone, so am pretty careful about what, when, and how I flash the phone. I see a few people posting problems with CM10 upgrade, even the stable build.
I've found CM10 exceptionally solid during a couple of weeks of use, and thought it might be helpful to share some specifics, if anyone is considering the upgrade but concerned about result.
Here are the details of my upgrade path and config. This JB config has been more stable than the stock GB or Froyo roms I've run on this phone in the past.
I upgraded to CM10 from GB KK4, Corn 7.06a with ext4 filesystem, not rfs). my cappy is August 2011 build date.
files used:
CM10.0
http://get.cm/get/jenkins/12598/cm-10.0.0-captivatemtd.zip
Gapps
http://goo.im/gapps/gapps-jb-20121011-signed.zip
---
sequence used:
1. complete cwm backup, complete TiBU Pro backup, copy both to remote cloud.
2. from cwm, clear both dalvik and system caches, then factory reset.
3. from cwm, flash captivatemtd, twice, then reboot to recovery, flash gapps, then reboot.
4. Restoration:
entered Google accounts profiles.
Rather than batch restore user apps from TiBU, I selectively restored apps from Google Play. Then restored data only for user apps from TiBU.
Significant diffs in beginning of my setup:
1. used TouchPal 5 keyboard. some folks have reported cappy probs with CM keyboard. Touchpal is laggy startup on first use after each boot, but okay afterwards.
2. I prefer GO Launcher Ex to Trebuchet launcher. I also use the Go Contacts app and dialer only because I could not find a way to create speed dials in the dialer included in CM10. If there is a way to create speed dials in the included dialer, I couldn't find it.
3. Settings, performance: Interactive governor, cfq, CPU 100-1000. I ran it with 1200 OC, and while stable, it reduces batt life, so I only switch to OC occasionally. Battery life is about 20% less than GB, but I'm fairly sure it will improve as I tweak it further.
Don't be surprised if it takes a few boots and several hours of use before the cappy really starts running without many lags.
Governor note: JB definitely balks at conservative gov and the default ondemand gov is okay, but interactive seems best. I wish CM included SmartassV2 gov in their kernel - that was best one for me when running GB.
4. I used System Tuner app to disable several apps at startup (ones that don't need it, e.g., Google maps), and to set SD buffer to 1024 instead of default 128. This increases write speed to both internal and external sd by about 30% in sd tools test).
Frozen apps
Apollo
DSP manager
Talk
TalkBack
Disabled startups, these system apps only launch when needed or not at all., the default was launch at boot:
Exchange Services
Gallery
Maps
News and Weather
and also a bunch of user apps that don't need to run at startup (EBay, various games, etc)
hope this is helpful to anyone considering jump to JB via CM10.
Sent from my SGH-I897
edit: added the list of apps frozen or disabled startup at boot. edited links.
Screenshot
{
"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"
}
Sent from my SGH-I897
This speed test result with JB 4.1.2 CM10 @ 6 Mbps download is significantly better than the 3 to 4 Mbps that I got with GB. I don't know how much of this may be due to AT&T network changes versus better network performance with JB. In the screenshot below, my IP address is scratched out for security.
Sent from my SGH-I897
Re: Jelly Bean: my stable CM10 path with notes
recently flashed Semaphore 2.6.5c and am pleased with the result.
using Semaphore manager to tweak a few things. It has SmartassV2 governor, and SD card read ahead tweaks. OC doesn't seem to work, however.
Sent from my SGH-I897
Re: Jelly Bean: my stable CM10 path with notes
changes, updated from feb 1 post, and written on 4/13.
running cm10.1 nightly, 2013 April 12.
holo launcher hd.
better bean blue/black theme
system tuner pro used to disable many apps at start up and set sd read ahead to 512 on boot completed.
bug that remains since late March nightlies-
custom mp3 ringtones on internal sd don't remain set after boot, even if in auto created ringtone folder. it happens with the regular ringtone in setttings, and with ringtone assigned to a contact. also with alarm tones.
the custom tone assignments are replaced with a series of numbers, or 'unknown ringtone'. i think it is a media storage bug and reported it to nightly thread a week or to ago.
my first solution was to copy the files to system/media/ringtones folder and chmod 644, then set the custom tone assignments for default tone and for various contacts that each have their own custom tone.
it is a pain to repeat those tasks after flashing each rom update, so I've found an easier way to do the workaround-
I add my custom ringtones into the system/media/ringtones folder of the nightly zip file before flashing, and then cwm flash from recovery with sig verification disabled. The custom tone assignments now survive updates and reboots because they are always in the system/media/ringtones folder.
additional notes-
the migration from cm10.0 to cm10.1 in january was easy. wipe cache and dalvik cache, then flash.
I find the cwm dup format unhelpful for two reasons-
1. the many folders and files under blobs take longer to backup to my cloud storage.
2. if I have removed an app and then do a backup via cwm, then cwm removes the app from the blobs, even if it included in an earlier cwm backup. So restoring from that earlier backup would be incomplete.
I have changed my default cwm backup format to tar, not dup. while this takes more storage space than dup, it ensures that each backup contains all the files needed to restore complete system with all apps.
sent via carrier pigeon, jungle drums and smoke signals.
Running the April 24th nightly CM 10.1 and am very pleased with the continuous improvements in this Jelly Bean 4.2.2 ROM.
Also switched from TouchPal to SwiftKey, which is better, IMHO.
I also appreciate the well documented change log for each CM nightly. I take a look at the change log before deciding to flash a particular nightly. Unless there are many changes, or a particular change that addresses a noticeable bug, then I'll wait a few days before my next flash.
I am grateful for the work by pawitp and the entire CM team.
sent by the scare crow, tin man, and cowardly lion on the yellow brickfree cm10.1 road.
laughingT said:
Screenshot
View attachment 1552619
Sent from my SGH-I897
Click to expand...
Click to collapse
What clock widget is that?
x0ne215 said:
What clock widget is that?
Click to expand...
Click to collapse
One More Clock Widget free. It has seventy different clock widgets
https://play.google.com/store/apps/details?id=com.sunnykwong.freeomc
sent by the scare crow, tin man, and cowardly lion on the yellow brickfree cm10.1 road.
for reference, a list of cm10.1 mounts, excluding individual app license key mounts.
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
tmpfs /storage tmpfs rw,relatime,mode=050,gid=1028 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,relatime,mode=775,gid=1000 0 0
/dev/block/mtdblock3 /cache yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock5 /radio yaffs2 rw,relatime 0 0
/dev/block/mtdblock2 /datadata yaffs2 rw,relatime 0 0
/dev/lvpool/system /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/lvpool/userdata /data ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,nomblk_io_submit,data=ordered 0 0
/dev/block/mtdblock4 /efs yaffs2 rw,relatime 0 0
/dev/block/vold/179:9 /storage/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /storage/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /storage/sdcard0/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
Sent via Monty Pythons Flying Circus
well, now I have blown it. my speaker went fluky. fixed it once with taking cappy apart and fixed, by the screw adustment. a month later, when it started failing, I took it apart again and attempted to fix it again, this time by releasing the speaker cable from the duaghter board to reseat the cable.
the problem, with aging and possibly heat, the connector release was so brittle that it just crumbled. so, I now have a speakerless, vibratorless cappy. otherwise, phone is good, works well, including ear speaker. I get ringtones via bluetooth headset or wired headset.
jeez. well, two years of good use, contract is up in October.
Sent via Monty Pythons Flying Circus
laughingT said:
well, now I have blown it. my speaker went fluky. fixed it once with taking cappy apart and fixed, by the screw adustment. a month later, when it started failing, I took it apart again and attempted to fix it again, this time by releasing the speaker cable from the duaghter board to reseat the cable.
the problem, with aging and possibly heat, the connector release was so brittle that it just crumbled. so, I now have a speakerless, vibratorless cappy. otherwise, phone is good, works well, including ear speaker. I get ringtones via bluetooth headset or wired headset.
jeez. well, two years of good use, contract is up in October.
Sent via Monty Pythons Flying Circus
Click to expand...
Click to collapse
Well, its been 8 month, and you haven't encountered the Encryption bug, so thats a blessing there XD. Put the board up for sales here as a replacement for borked Internal SD devices
thanks, but not for sale.
Sent via Monty Pythons Flying Circus
Related
Hey Everyone,
I know there probably wont be much interest in this but I thought I should post my results. This is instructions on how I got my wiimote and accessories to work with my Dream. It should be possible to setup Bluetooth keyboards that use UINPUT too.
1. I emailed cyanogen and asked him to enable UINPUT in the kernel and he was Awesome and did this for me. Thanks Cyanogen!!
2. I added the following line to my bootdeb script to make UINPUT show up in chroot debian. I would appreciate any input on how appropriate this mount is. Im a linux noob. The second line is to reference where I stuck it.
mount -o bind /dev $mnt/dev <-- I added this line
mount -t devpts devpts $mnt/dev/pts <--above this line present in bootdeb
3. I installed wminput with
apt-get install wminput
4. I configured buttons. The config files are in /etc/cwiid/wminput/. Nano was very glitched out for me but it got the job done.
cd /etc/cwiid/wminput/
nano buttons
The info in these 3 links should allow any button to be mapped.
http://abstrakraft.org/cwiid/browser/trunk/wminput/action_enum.txt
http://abstrakraft.org/cwiid/browser/trunk/doc/wminput.list
http://www.kandroid.org/android_pdk/keymaps_keyboard_input.html
5. Run wminput and drop debian to the background.
wminput -d -c buttons
Press 1 and 2 on the wiimote
Press the home button to drop debian to the background and your done
I did this mainly to play nes on the train in a comfortable fassion. And it turns out there is a bit of a lag now and again which causes the buttons to stick while it catches up. Just for a moment but enough to throw Megaman/Mario off a cliff! If anyone else tries this, Im very curious if you have this same issue. I tried setting the priority higher with nice but it didnt help. Does that work in a chroot environment? Does anyone have any thoughts on how I could remove lag? I dont think its being cause by excessive cpu usage since it happens just at the prompt when pressing buttons quickly.
Thanks for any input,
Tous
Awesome, now we just need to overclock to about 3 Ghz without the phone exploding, and we can emulate Wii games!
Thank you in advance if you can help with this, unfortunately I'm not going to be able to follow through with this very well at the moment. If this gets no attention I'll bump it when I can follow through.
I want to mount a smb/cifs share from my router to my Nexus 5.
I can successfully mount the share and view it in terminal but none of it shows up in any apps...and that's pretty much my issue.
Here's some unimportant info, and a little info about me, I'm as scatterbrained as they come. The reason I want to do this is to stream my movies on the "NAS" to my Chromecast through Allcast or something.
As of now I'm using an entware mini dlna package on the router to stream everything to Avia. My problem is dlna broadcasts all my media to my entire network...no password required or anything. Also accessing my files through Avia is a pain in the ass, navigating through the folders repetitively gets exhausting.
Here's what I've come up with so far:
I'm using hammerhead-faux123-010m kernel, and SlimRC3.
CIFS DebugData:
Code:
CIFS Version 1.78
Features: posix xattr
Active VFS Requests: 0
Servers:
1) Name: 192.168.1.1 Domain: WORKGROUP Uses: 1 OS: Unix
NOS: Samba 3.0.37 Capability: 0x80e3fd
SMB session status: 1 TCP status: 1
Local Users To Server: 1 SecMode: 0x3 Req On Wire: 0
Shares:
1) \\192.168.1.1\NAS Mounts: 1 Type: NTFS DevInfo: 0x0 Attributes: 0xf
PathComponentMax: 255 Status: 0x1 type: 0
MIDs:
The disk is actually Ext3, not NTFS.
This guy kinda just crushed all my hopes and dreams of the future but I'm trying to use his OneClickMount alpha app.
http://forum.xda-developers.com/showpost.php?p=49651026&postcount=127
app here:
http://forum.xda-developers.com/showpost.php?p=49693815&postcount=129
This is what I have tried, I ended up with the same results:
Code:
[email protected]:/storage/emulated/0/cifs # setenforce Permissive
[email protected]:/storage/emulated/0/cifs # getenforce
Permissive
[email protected]:/storage/emulated/0/cifs # mount -r -o noperm,rw,file_mode=777,dir_mode=777,uid=1023,gid=1023,unc=\\\\192.168.1.1\\NAS,username=***,password=*** -t cifs none /storage/emulated/0/cifs
[email protected]:/storage/emulated/0/cifs # ls
My Music
My Pictures
My Videos
Torrents
Then I tried OneClick Mount app:
https://www.dropbox.com/sh/muabb9vp1i8ubxt/o78FSYMcHo
From what I can tell from the app logcat, the app tries to move the debuggered file, create its own with a chosen command inside, start then stop it, and restart the original.
I might try to do this manually later, as in a month from now at the least. I'm pretty sure a certain someone is pissed off at me for not becoming one with the universe n all that jazz.
I'm gonna leave a couple links here so I can delve into them later, they seem to have crazy amounts of useful information:
[HINT] How Stickmount (and others...) are working with Android 4.2
Debuggered script
Sincerely, Head is spinning
Sorry but as of android 4.4.2 CIFS at a device level (all accounts see the network shares) no longer works and no one has a solution. This includes rooted devices and custom Roms. Of course apps such as ES File Explorer can have network share accesses but not all apps can utilize that access. For example MX player can be invoked from an ES file folder by clicking on a video file but apps like PowerAmp cannot see those folders. Some apps include built in network share features but they have the same restrictions as I previously described.
Things all changed when Android included multiple accounts and security started to get tighter. Initially developers found ways around those measures but too my knowledge, with 4.4.2 no one has found a work around.
Sent from my Nexus 10 using XDA Premium HD app
3DSammy said:
Things all changed when Android included multiple accounts and security started to get tighter. Initially developers found ways around those measures but too my knowledge, with 4.4.2 no one has found a work around.
Sent from my Nexus 10 using XDA Premium HD app
Click to expand...
Click to collapse
One workaround is hijack a system process such as debuggerd (debugger daemon) which runs with higher than su permissions. This method still works but is awkward to exploit manually. Apps such as foldermount use this workaround but not for network mounting, but it shows that it is still possible.
I have a Raspberry Pi running OpenELEC for streaming my locally stored media. I use my Chromecast for streaming Netflix, Google Play media, etc.
I understand what you are trying to do, but a dedicated device works great for me.
That said, you might keep an eye on VLC to see if they start supporting casting to Chromecast. That would likely accomplish what you are asking.
rootSU said:
One workaround is hijack a system process such as debuggerd (debugger daemon) which runs with higher than su permissions. This method still works but is awkward to exploit manually. Apps such as foldermount use this workaround but not for network mounting, but it shows that it is still possible.
Click to expand...
Click to collapse
This is what I'm going to attempt next, from what I read it can be terribly inconsistent if not done through SSH, so that's a bummer. I just need to get more information on how to do it. Debuggered in general confuses me.
embhorn said:
I have a Raspberry Pi running OpenELEC for streaming my locally stored media. I use my Chromecast for streaming Netflix, Google Play media, etc.
I understand what you are trying to do, but a dedicated device works great for me.
That said, you might keep an eye on VLC to see if they start supporting casting to Chromecast. That would likely accomplish what you are asking.
Click to expand...
Click to collapse
This is what I've been wanting to do with my old Galaxy Nexus. I have the HDMI adapter and everything but the screen is broke (the digitizer works), so I plug it into my TV and randomly hit the screen hoping to eventually connect my bluetooth mouse lol. No such luck. I wish I could just boot it into a custom build but that's never gonna happen. Unless OpenELEC works on android devices? Seems unlikely.
debuggerd can be replaced with a shell script with the mount command in it and it will run at boot.
It's really messy. I found I had to put the original debuggerd back or the phone would lock up.
Sent from my Nexus 5 using Tapatalk
WEEEEEOOOOOOO I finally got all my stuff to show in a file manager, now I just need to find a terminal command to trigger media scan on the folder. Right after I eat a bunch of chicken.
Awesome, it works perfectly. And by perfectly I mean it's the messiest thing I've ever done on Android. I'm not really sure how this affects battery and all but thank god this finally works.
For anyone interested:
Follow the directions in this post.
I didn't understand the mount command he used so I used
Code:
/system/xbin/busybox mount -r -o noperm,rw,file_mode=777,dir_mode=777,uid=1023,gid=1023,unc=\\\\192.168.1.1\\NAS,username=***,password=*** -t cifs none /data/media/0/cifs
You also need to use /data/media/0/ otherwise it will only work in already opened apps apparently.
So thanks rootSU...And that should work, I'm going to do it in a way where I don't have to use scriptmanager but that's the gist. All the credit goes to the people in the threads I linked, I have absolutely no idea what I did here and I learned nothing.
Nothing special to see here. :good:
Here's a way to unmount it so it doesn't explode your apps when you disconnect WiFi:
/system/bin/debuggerd.binnn
Code:
#!/system/bin/sh
/system/bin/umount_movies.sh
exec /system/bin/debuggerd.bin "[email protected]"
/system/bin/umount_movies.sh
Code:
#!/system/bin/sh
/system/xbin/busybox umount /data/media/0/cifs
/system/xbin/busybox umount -r -o noperm,rw,file_mode=777,dir_mode=777,uid=1023,gid=1023,unc=\\\\192.168.1.1\\NAS,username=***,password=*** -t cifs none /data/media/0/cifs
Script_eject.sh
Code:
#!/system/bin/sh
mount -o rw,remount /system
sleep1
/system/xbin/busybox mv /system/bin/debuggerd /system/bin/debuggerd.binn
sleep 1
/system/xbin/busybox mv /system/bin/debuggerd.binnn /system/bin/debuggerd
sleep 1
mypid=$(/system/xbin/busybox ps -o pid,comm | /system/xbin/busybox grep 'debuggerd' | /system/xbin/busybox awk 'NR == 1 {print $1}')
/system/bin/kill $mypid
sleep 1
/system/xbin/busybox mv /system/bin/debuggerd /system/bin/debuggerd.binnn
sleep 1
/system/xbin/busybox mv /system/bin/debuggerd.binn /system/bin/debuggerd
sleep 1
mount -o ro,remount /system
I'm automating all this with Tasker.
Script task: (I have it run at boot)
waits 15 seconds
run shell command to kill debuggerd
wait 5 seconds
media action scan card /
Script_eject task: (I have it run when I disconnect from my SSID)
run shell command with the script_eject.sh code
wait 6 seconds
media scan card /
It has been seamless so far, also lol.
sendan said:
For anyone interested:
Follow the directions in this post....
Click to expand...
Click to collapse
I have yet to try your solution but what Rom and kernel do you have installed? I ask because in the past (Android 4.1) you needed a custom kernel that supported CIFS or you needed to add modules to stock.
I'm using rooted stock, Franco Kernel.
Sent from my Nexus 10 using XDA Premium HD app
3DSammy said:
I have yet to try your solution but what Rom and kernel do you have installed? I ask because in the past (Android 4.1) you needed a custom kernel that supported CIFS or you needed to add modules to stock.
I'm using rooted stock, Franco Kernel.
Sent from my Nexus 10 using XDA Premium HD app
Click to expand...
Click to collapse
I'm on the latest Slim, with latest faux kernel. Faux has cifs modules built in, I'm not sure about Slim or Franco kernel. If you have a cifs folder in /proc/fs I assume that means the kernel has the cifs modules.
Hello,
I'm new here, therefor I think I'm not allowed to post in the developer's threads...
I just wanted to say that there is a problem with the browser2ram script and opera:
Opera performs very bad on my TF700 (using cromi-x), and when I look for tmpfs I cannot see something mounted for opera:
Code:
[email protected]:/ # cat /proc/mounts | grep tmpfs
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
tmpfs /storage tmpfs rw,relatime,mode=050,gid=1028 0 0
tmpfs /storage/emulated tmpfs rw,nosuid,nodev,relatime,mode=050,gid=1028 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
com.android.browser_cache /data/data/com.android.browser/cache tmpfs rw,relatime,size=102400k 0 0
com.android.chrome_cache /data/data/com.android.chrome/cache tmpfs rw,relatime,size=102400k 0 0
com.chrome.beta_cache /data/data/com.chrome.beta/cache tmpfs rw,relatime,size=102400k 0 0
com.jiubang.browser_cache /data/data/com.jiubang.browser/cache tmpfs rw,relatime,size=102400k 0 0
tmpfs /Removable tmpfs rw,relatime,mode=755,gid=1000 0 0
In the script it says:
Code:
[email protected]:/ # cat /system/etc/init.d/70B2R
...
datadir=/data/data/$BROWSER/cache
...
but when you look at
Code:
[email protected]:/ # ls /data/data | grep opera
com.opera.browser
[email protected]:/ # ls /data/data/com.opera.browser/
lib
[email protected]:/ # ls /data/data/com.opera.browser/lib/
libch.so
liblzma.so
libom.so
there obviously doesn't exist any file or folder named "cache", so I think they changed something or the browser2ram script never worked for opera?
Would be glad if this could be fixed.
btw: I never ever get such smooth "ipad-like" scrolling with any kitkat rom, just with jellybean based roms and stock or chrome browser. Is that normal?
(pls no info about the differences between android and ipad rendering while scrolling, I know about that, just wanted to know if everybody has similar issues with scrolling smoothness kitkat vs jellybean)
greets,
MiM81
MiM81 said:
Hello,
I'm new here, therefor I think I'm not allowed to post in the developer's threads...
I just wanted to say that there is a problem with the browser2ram script and opera:
Opera performs very bad on my TF700 (using cromi-x), and when I look for tmpfs I cannot see something mounted for opera:
Code:
[email protected]android:/ # cat /proc/mounts | grep tmpfs
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
tmpfs /storage tmpfs rw,relatime,mode=050,gid=1028 0 0
tmpfs /storage/emulated tmpfs rw,nosuid,nodev,relatime,mode=050,gid=1028 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
com.android.browser_cache /data/data/com.android.browser/cache tmpfs rw,relatime,size=102400k 0 0
com.android.chrome_cache /data/data/com.android.chrome/cache tmpfs rw,relatime,size=102400k 0 0
com.chrome.beta_cache /data/data/com.chrome.beta/cache tmpfs rw,relatime,size=102400k 0 0
com.jiubang.browser_cache /data/data/com.jiubang.browser/cache tmpfs rw,relatime,size=102400k 0 0
tmpfs /Removable tmpfs rw,relatime,mode=755,gid=1000 0 0
In the script it says:
Code:
[email protected]:/ # cat /system/etc/init.d/70B2R
...
datadir=/data/data/$BROWSER/cache
...
but when you look at
Code:
[email protected]:/ # ls /data/data | grep opera
com.opera.browser
[email protected]:/ # ls /data/data/com.opera.browser/
lib
[email protected]:/ # ls /data/data/com.opera.browser/lib/
libch.so
liblzma.so
libom.so
there obviously doesn't exist any file or folder named "cache", so I think they changed something or the browser2ram script never worked for opera?
Would be glad if this could be fixed.
btw: I never ever get such smooth "ipad-like" scrolling with any kitkat rom, just with jellybean based roms and stock or chrome browser. Is that normal?
(pls no info about the differences between android and ipad rendering while scrolling, I know about that, just wanted to know if everybody has similar issues with scrolling smoothness kitkat vs jellybean)
greets,
MiM81
Click to expand...
Click to collapse
I will look into it - opera must have changed where their cache goes.
BTW try ZOMBi-X for smooth like scrolling on KK
EDIT There are 4 versions of opera - which one should I be installing?
{
"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"
}
sbdags said:
I will look into it - opera must have changed where there cache goes.
BTW try ZOMBi-X for smooth like scrolling on KK
Click to expand...
Click to collapse
I did so, am on Zombi-X now, so it took me a while to answer. If you change gallery from aosp to asus, gallery cannot be started btw
Nonetheless you're right, everything is snappy and smooth now (though stock browser still is not as smooth as when running cromi-x, but chrome runs better now)
Thx so far
Just to describe, what behaviour I mean when saying "smooth": In ios everything stops rendering while scrolling (easy to test with animated gifs: no animation while scrolling). Therefor scrolling is always smooth as technically an unanimated image is scrolled.
In Android, when I use stock browser ("real" stock or alternate with smoother scrolling) and browser2ram on cromi-x, the scrolling is almost as smooth as on ios: there is still rendering but when I slowly move my finger over the screen from bottom to top, the page content stays exactly under my finger.
With any kitkat based rom the scrolling is smooth while I do it QUICK (results in very fast scrolling and smooth slowing down) but when I slowly move my finger over the screen (as I think most users do while reading articles, forum threads and so on) there is always some disturbing stuttering and the content does not stay exactly under the finger. (still talking about stock browser, chrome is nice scrolling now)
I hope this was a clear description as I am German and my English is not that good...
sbdags said:
EDIT There are 4 versions of opera - which one should I be installing?
Click to expand...
Click to collapse
Didn't reinstall anything yet but I for myself use to install "Opera Browser for Android", I think...
greets,
MiM81
ok I checked and com.opera.browser has a cache folder inside and is also getting cached.... ??
mount | grep tmpfs
shows it caching nicely.
sbdags said:
ok I checked and com.opera.browser has a cache folder inside and is also getting cached.... ??
mount | grep tmpfs
shows it caching nicely.
Click to expand...
Click to collapse
Huh? Okay, then something went wrong in my case. As you can see from my code pastings, there has not been any "cache" folder for me.
Since I was running cromi-x and now am using your newest build zombi-x ( ... outstanding by the way!) and I cannot obtain root (terminal doesn't start and super su doesn't work yet) I cannot see if everything is okay with opera's cache now.
But I think so as you tell me so
So thx for watching
greets,
MiM81
MiM81 said:
Huh? Okay, then something went wrong in my case. As you can see from my code pastings, there has not been any "cache" folder for me.
Since I was running cromi-x and now am using your newest build zombi-x ( ... outstanding by the way!) and I cannot obtain root (terminal doesn't start and super su doesn't work yet) I cannot see if everything is okay with opera's cache now.
But I think so as you tell me so
So thx for watching
greets,
MiM81
Click to expand...
Click to collapse
Flash this to get root back for now
that should kick start your B2R as it needs root
http://forum.xda-developers.com/devdb/project/dl/?id=8198
sbdags said:
Flash this to get root back for now
that should kick start your B2R as it needs root
http://forum.xda-developers.com/devdb/project/dl/?id=8198
Click to expand...
Click to collapse
Thank you. Super Su seems to work now, while apps which need super user rights still seem to have problems. At last in my case (better to say that a little more explicit since the browser cache problem ... hehe)
For example Terminal still does force close immediately and AdAway obtains super user rights but closes about 1 minute later.
But I know everything is beta and I am very impressed by your new ROM, so please feel free to do all the more important stuff first
I am very happy that people like you find the time to build these roms, as this is what still makes me prefer my tf700 (even my old tf101) over my ipad 3 though all the trouble with ASUS support.
greets,
MiM81
MiM81 said:
Thank you. Super Su seems to work now, while apps which need super user rights still seem to have problems. At last in my case (better to say that a little more explicit since the browser cache problem ... hehe)
For example Terminal still does force close immediately and AdAway obtains super user rights but closes about 1 minute later.
But I know everything is beta and I am very impressed by your new ROM, so please feel free to do all the more important stuff first
I am very happy that people like you find the time to build these roms, as this is what still makes me prefer my tf700 (even my old tf101) over my ipad 3 though all the trouble with ASUS support.
greets,
MiM81
Click to expand...
Click to collapse
I have fixed terminal for the next release later That was a different issue and my fault.
I haven't seen an issue with adaway - can you be more specific?
sbdags said:
I have fixed terminal for the next release later That was a different issue and my fault.
I haven't seen an issue with adaway - can you be more specific?
Click to expand...
Click to collapse
I installed the zip file and rebooted. Then I started AdAway (for the first time) just because I know it would ask me to obtain super user rights (to test if super su ist working now). It started and about 1 minute later there was a system popup, telling me AdAway force closed. Now I rebooted and AdAway says it is working fine. (about 5 minutes now since reboot).
I cannot check if it really does as I run my own dns-server with dns manipulations very similar to those used by AdAway, but I think it is running okay since it says it could successfully update the hosts file.
greets,
MiM81
@sbdags in the hope you will read it here as I am not allowed to post in the right section yet:
So... now that I wrote so many different possibilities, I finally have found what irritates me when I try to use the omni switch bar:
1. Open some app with the app launcher menu of omni switch bar which you did not open before (not in your recent apps list), let's say Google Maps.
2. Now that Google Maps is in your recent apps list (the omni switch bar) long press it and make it a floating window.
3. Now for some reason use the home button to look at your homescreen.
4. Now reopen omni switch bar, you want to go back to your Google Maps: Google maps item will be disappered.
5. Reopen Google Maps by using the app launcher menu in omni switch bar again: your floating window of Google Maps still exists and will reappear.
6. For some reason you switch a while between several floating windows you have and then you are in the app launcher menu and decide to press Google Maps button from there to switch back to your existing instance of that app (just because you see it there next to your finger while looking for some other app and you were able to let it reappear this way before) : Now a new instance in full view opens, instead of the existing one. The existing instance does not (accessible) exist any longer.
This way my original post here got more and more confusing as I switched alot the way described above and therefor every few minutes had different "stages" of my forum editor content here (due to several instnces of chrome) and didn't understand what was going on.
So for me it would be highly more usable if:
1. apps won't disappear from the recent apps list after pressing the home button (they should stay accessible all the time as long as they are recent...)
2. there would be all the time in any case used the same instances of apps, not new ones.
Might be I just didn't really understand the benefits of the floating apps feature, but these 2 points would make it much more intuitive for me to use it.
greets,
MiM81
I've been using rsync to keep my iTunes Music folder on my mac sync'ed to the Music folder on my sdcard. As long as I only sync in one direction and carefully choose my rsync options it works pretty well. But if I make changes on my phone and try to sync them back to my mac, it gets messy. Every time I switch direction rsync thinks it needs to sync a bunch of stuff even though the files are all already identical.
I think the culprit is some combination of: 1) the vfat filesystem, which has an incompatible permissions and ownership model, and 2) the mount options, which include a umask that prevents rsync from replicating permissions from my mac, maybe including mtime?
I tried for awhile to switch my sdcard to ext4, but can't get it working. Then I tried to run a mount -o remount to change the umask, but that didn't seem to work. I'm stuck.
Old thread, but the answer is still valid: The problem here is that vfat stores time with a 2-second resolution only. rsync will detect files as changed even though they didn't change at all.
Use the "--modify-window=1" cmdline switch to ignore difference in time up to one second.
From the rsync manpage:
--modify-window
When comparing two timestamps, rsync treats the timestamps as being equal if they differ by no more than the modify-window value. This is normally 0 (for an exact match), but you may find it useful to set this to a larger value in some situations. In particular, when transferring to or from an MS Windows FAT filesystem (which represents times with a 2-second resolution), --modify-window=1 is useful (allowing times to differ by up to 1 second).
Click to expand...
Click to collapse
You might have noticed we have a spanish rom that popped up in the android development section. I've been browsing through it as best I can and one of the things I noticed is they are using trickster mod kernel settings available on xda here: http://forum.xda-developers.com/showthread.php?t=1768315 to control some settings in their kernel...so I tried the same things and it seemed to both speed up performance AND lower temperature as that's one of the settings you can enable. In any case it looks like the spanish rom lowers the minimum cpu speed from 960 to 800 and sets it to enable on boot. The min speed gets set back to 960 at odd times..not sure why yet. They set the readahead cache on the sd to 1024 up from the default 512 I set the scheduler to "deadline" since it provides a performance boost when using flashed based media. Those are all under "General Settings". Under "Specific Settings" enabled "Temperature Throttle" which will lower cpu speed when the cpu starts getting hot....the phone runs much cooler and yet I still don't see the lag I was seeing before. Give it a try..all these options are available in the free version.
hmm ill give it a try no issues?
gecko702 said:
hmm ill give it a try no issues?
Click to expand...
Click to collapse
No issues other than the phone resets the min speed to 960 instead of 800 even though I've got it set on boot. I also set the speed. io scheduler etc using rom toolbox (pro) without issue which is what I'm using now cause I tweaked a few other things. Both worked fine. We can't really get into any of the "fancy" settings till we get a kernel compiled that allows it.
Hmm i see until alcatel releases their source thats when a proper kernel can be compiled right? And yes it overheats and feels really hot when im charging and using an app lets say youtube
The trickster mod also has a section for temperature control. It works pretty well. Yes when they release the source we can compiler own kernel.
Sent from my 6045I using Tapatalk
I tried it works thanks!
famewolf said:
You might have noticed we have a spanish rom that popped up in the android development section. I've been browsing through it as best I can and one of the things I noticed is they are using trickster mod kernel settings available on xda here: http://forum.xda-developers.com/showthread.php?t=1768315 to control some settings in their kernel...so I tried the same things and it seemed to both speed up performance AND lower temperature as that's one of the settings you can enable. In any case it looks like the spanish rom lowers the minimum cpu speed from 960 to 800 and sets it to enable on boot. The min speed gets set back to 960 at odd times..not sure why yet. They set the readahead cache on the sd to 1024 up from the default 512 I set the scheduler to "deadline" since it provides a performance boost when using flashed based media. Those are all under "General Settings". Under "Specific Settings" enabled "Temperature Throttle" which will lower cpu speed when the cpu starts getting hot....the phone runs much cooler and yet I still don't see the lag I was seeing before. Give it a try..all these options are available in the free version.
Click to expand...
Click to collapse
Clock speeds get reset because of mpdecison which is the stock Qualcomm daemon.
techware7 said:
Clock speeds get reset because of mpdecison which is the stock Qualcomm daemon.
Click to expand...
Click to collapse
So using Rom toolbox and setting up profiles for instance to lower cpu speed when phone is hotter than 100F are going to be useless?
I found this in a google search......
The easiest way to avoid the restart of the mpdecision service is to rename the mpdecision binary. You can use the following steps to do so from a shell on your computer:
// To disable MP decision
$ adb root [ for us adb shell and then su ]
$ adb remount [for us "mount -o remount,rw /system"]
$ adb shell stop mpdecision [for us just "stop mpdecision"]
$ adb shell mv /system/bin/mpdecision /system/bin/mpdecision-rm <---- *problem* There is no "mpdecision" in /system/bin
// To re-enable MP decision
$ adb root [ for us adb shell and then su ]
$ adb remount [for us "mount -o remount,rw /system"]
$ adb shell mv /system/bin/mpdecision-rm /system/bin/mpdecision <--- *same problem*
$ adb shell start mpdecision [ for us "start mpdecision"]
The start and stop mpdecision commands work but no idea where the binaries are or even whether disabling mpdecision so I can do cpu profiles is a good idea.
Well we need to have something like intelliplug or some modded mpdecision - pretty much a custom kernel
Anyone getting random infrequent reboots? 3 times for me today. I've started backing off on some of the recommended settings. I'm currently down to just using the 1024 read ahead buffer and CPU governor as ondemand. I'll report back if I get any more reboots.
psu2fan said:
Anyone getting random infrequent reboots? 3 times for me today. I've started backing off on some of the recommended settings. I'm currently down to just using the 1024 read ahead buffer and CPU governor as ondemand. I'll report back if I get any more reboots.
Click to expand...
Click to collapse
My idol is fine with no reboots; but for those values/variables I have the defaults: 512 readahead cache (I think is the most optimized) and interactive as governor. Interactive Is newer than ondeman - you should feel less "lag/jerkiness" when you switch from one app to another with interactive. Interactive came along with the whole project butter initiative.
Can we use this with stock-rooted rom?
snugroho3 said:
Can we use this with stock-rooted rom?
Click to expand...
Click to collapse
Yes, somewhat.
techware7 said:
My idol is fine with no reboots; but for those values/variables I have the defaults: 512 readahead cache (I think is the most optimized) and interactive as governor. Interactive Is newer than ondeman - you should feel less "lag/jerkiness" when you switch from one app to another with interactive. Interactive came along with the whole project butter initiative.
Click to expand...
Click to collapse
In rom toolbox it does benchmarking for the readahead and with my sd card 4096 was the best read/write performance. Interactive is the default governor. In the end I ditched the app because the stock kernel resets the cpu settings. The io scheduler I use is deadline which is supposed to give superior performance when dealing with flash based media....which all our media is. It's also the default for lollipop I think.
famewolf said:
So using Rom toolbox and setting up profiles for instance to lower cpu speed when phone is hotter than 100F are going to be useless?
I found this in a google search......
The easiest way to avoid the restart of the mpdecision service is to rename the mpdecision binary. You can use the following steps to do so from a shell on your computer:
// To disable MP decision
$ adb root [ for us adb shell and then su ]
$ adb remount [for us "mount -o remount,rw /system"]
$ adb shell stop mpdecision [for us just "stop mpdecision"]
$ adb shell mv /system/bin/mpdecision /system/bin/mpdecision-rm <---- *problem* There is no "mpdecision" in /system/bin
// To re-enable MP decision
$ adb root [ for us adb shell and then su ]
$ adb remount [for us "mount -o remount,rw /system"]
$ adb shell mv /system/bin/mpdecision-rm /system/bin/mpdecision <--- *same problem*
$ adb shell start mpdecision [ for us "start mpdecision"]
The start and stop mpdecision commands work but no idea where the binaries are or even whether disabling mpdecision so I can do cpu profiles is a good idea.
Click to expand...
Click to collapse
There are a few interesting things in /etc/init.qcom.post_boot.sh, regarding CPU profiles among others. I'll take a look later today and let you know if I find anything worth looking into. You can also just put the mpdecision stop command in there.
Sent from my 6039H using XDA Free mobile app