Hello all,sorry to open such a thread in Dev section,it's only temporary and to be deleted as soon as it's stated useless by your reports or by moderators but i think there's a general issue with /datadata partition on CM10.1 based roms and i'd like to see things identified as soon as possible.
Question is simple:
If you're then on a CM10.1 based rom,approximately post 05/12,could you check you're /datadata partition and report if it is empty/unused?
"Chances" for that to happen: Having done a factory reset after 05/12 and not come no wipe from other rom than CM10.1 sources based ones (so not coming from Pawitp's aosp preview as /datadata works fine with it,only cm10.1 sources based roms).
Thanks for help.
Since that I am Helly Bean (base CM 10.1), I have never made of factory reset, however, my "datadata" folder is empty. I don't know when and how, this has begun!
Otherwise, all works correctly, it's good, fast and smooth... Go to understand why!
Try to use "df" command in terminal emulator, and check used space of /datadata.
KSLevel11 said:
Try to use "df" command in terminal emulator, and check used space of /datadata.
Click to expand...
Click to collapse
Yeah,that's what i want CM10.1 based roms users to do and report
{
"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"
}
This one of Wingg to compare! datadata is OK for him...
/datadata is a protected folder. You can't view its content with a simple file browser. You must use a root file explorer.
Viewed using Root Explorer. My /datadata seems to be fine. Tictico might have a point.
ROM: BeastROM 12/07 build
tictico said:
/datadata is a protected folder. You can't view its content with a simple file browser. You must use a root file explorer.
Click to expand...
Click to collapse
Lame , you can see that Franzyroy has run the 'su' command already which allows complete root access to that app.
Also , I tried Hellybean 2012/12/08 today and my datadata is 8.5MB used , but it is empty inside.
If 4.2 doesnt use datadata , then maybe Fishears build without datadata and 1.8GB /data is actually beneficial, as we get extra space for apps without losing speed.
tictico said:
/datadata is a protected folder. You can't view its content with a simple file browser. You must use a root file explorer.
Click to expand...
Click to collapse
I know... I uses Solid Explorer or Estrongs Files Explorer with root activated, and also show the hidden files.
---------- Post added at 05:20 PM ---------- Previous post was at 05:14 PM ----------
ts1506 said:
Lame , you can see that Franzyroy has run the 'su' command already which allows complete root access to that app.
Click to expand...
Click to collapse
Good seen! But to confirm with su command.
!n0x said:
Viewed using Root Explorer. My /datadata seems to be fine. Tictico might have a point.
ROM: BeastROM 12/07 build
Click to expand...
Click to collapse
I was wondering what point but i got it now,no i'm used to that stuffs and not just reporting my own issue,it's just that i see many concording reports here and there and see peoples complaining about lags,reflashing,wiping data again thinking it's a specific rom issue and not knowing why their device COULD be laggy (not every phone acts the same with /datadata></data/data symlink broken).
Reports must come with little background please,the main point is "wiped data at least one time since approximately 05/12?"
By the way there's is two Beast rom 12/07 builds,yours is 4.2.1?
ts1506 said:
If 4.2 doesnt use datadata , then maybe Fishears build without datadata and 1.8GB /data is actually beneficial, as we get extra space for apps without losing speed.
Click to expand...
Click to collapse
Indeed as Fishears build doesn't use any /datadata partition it is not concerned but i don't think it will be 4.2 on sgs cm10.1 way.
It seems to have seen a Rom without datadata folder, I was wondering why, but I haven't reported it. I won't know to say which it was!
No lags
Bejda said:
I was wondering what point but i got it now,no i'm used to that stuffs and not just reporting my own issue,it's just that i see many concording reports here and there and see peoples complaining about lags,reflashing,wiping data again thinking it's a specific rom issue and not knowing why their device COULD be laggy (not every phone acts the same with /datadata></data/data symlink broken).
Reports must come with little background please,the main point is "wiped data at least one time since approximately 05/12?"
Click to expand...
Click to collapse
I always flash with full wipes of /data , /datadata , /cache , /system , and I dont face any lags with Hellybean 05/12 or 08/12 . Also , I tried GNex 4.2 ROM by Elite F7 build, no lags .
Without wiping from CM10 , there are some lags , but they are easily solved by only cache , dalvik cache wipe.
All is well on my end. I use CM10 daily , but will test Hellybean 08/12 from tomorrow in order to find lag issue, if any. Will report findings.
ts1506 said:
I always flash with full wipes of /data , /datadata , /cache , /system , and I dont face any lags with Hellybean 05/12 or 08/12 . Also , I tried GNex 4.2 ROM by Elite F7 build, no lags .
Without wiping from CM10 , there are some lags , but they are easily solved by only cache , dalvik cache wipe.
All is well on my end. I use CM10 daily , but will test Hellybean 08/12 from tomorrow in order to find lag issue, if any. Will report findings.
Click to expand...
Click to collapse
You may not face any lags with unused /datadata partition,check Fishears thread to know that first:
fishears said:
So, Is this ROM right for me?
If you have the fast iNand then, yes, because you'll get more data storage space with no loss of speed If you have the MoviNand then maybe yes, maybe no. My advice is "Try both".
To see which Nand you have look at the following file in a text viewer:
/sys/devices/platform/s3c-sdhci.0/mmc_host/mmc0/mmc0:0001/name
If the content starts with "S" then you have iNand. If it starts with "M" then you have MoviNand.
Click to expand...
Click to collapse
And even if as me you're on MoviNand you still may not face any visible lags on your device,mine does as many others,a choice has been made on cm10 to keep using /datadata as it was the better solution for the majority of users.
Keep using /datadata + lvm for best performance/storage balance for majority.
Bejda said:
You may not face any lags with unused /datadata partition,check Fishears thread to know that first:
And even if as me you're on MoviNand you still may not face any visible lags on your device,mine does as many others,a choice has been made on cm10 to keep using /datadata as it was the better solution for the majority of users.
Keep using /datadata + lvm for best performance/storage balance for majority.
Click to expand...
Click to collapse
My Galaxy S has iNand, maybe thats why my phone does not lag, but one of my friends have Galaxy S with moviNand , with Elite F7 4.2.1 , his phone also doesnt face any lag( this is installed with full wipe ).
ts1506 said:
My Galaxy S has iNand, maybe thats why my phone does not lag, but one of my friends have Galaxy S with moviNand , with Elite F7 4.2.1 , his phone also doesnt face any lag( this is installed with full wipe ).
Click to expand...
Click to collapse
That's why,at least the main reason.
Fishears build could be a good choice for you if you need more /data space (among others things like following a cool dev and enjoy rom's specific features and all...)
The bug,if exists,is only concerning CM10.1 recents builds.Elite's rom is aosp build.
so datadata should be anything else but 0.0?
Szighy said:
so datadata should be anything else but 0.0?
Click to expand...
Click to collapse
It should be filled with some app's data (cache,libs,...) It should have the exact same content as what you have in /data/data,it's a symlink.
Bejda said:
It should be filled with some app's data (cache,libs,...) It should have the exact same content as what you have in /data/data,it's a symlink.
Click to expand...
Click to collapse
for me says only 2.3M in terminal emulator...i guess that's not good then
Szighy said:
for me says only 2.3M in terminal emulator...i guess that's not good then
Click to expand...
Click to collapse
No good in theory If you're not feeling lags on the rom you are then don't worry.
Wich rom btw?Helly user too?
For now i tested 3 rom with same behavior,Helly 05 and 08/12,Mackay 08/12 and matt73300's 05/12 unofficial build.
Related
I have got CM7 to boot on my Galaxy S using some of the same methods used to boot the stock Gingerbread ROM.
I take credit for nothing... All I did was switched around a couple files to boot CM7 instead of GB.
Requirements
You must be root on your phone
Your /data must be converted in Ext4 by Voodoo lagfix or another Ext4 lagfix.
You must have proceed to complete backups before
Some busybox installation is also useful for tar.
Another Important note
Be absolutely 100% sure you have access to the download mode using the 3 buttons combination.
If you don't, it will be extremely difficult (even if in theory not impossible) to to flash another kernel back.
This is the gingerbread Folder to push in /data/: h**p://dl.dropbox.com/u/17890197/gingerbread.tar
Steps:
1: Download CM7 dump to SDCARD:
h**p://dl.dropbox.com/u/17890197/CyanogenMod/CM7.tar
2: Run the following via ADB
adb shell
su
busybox mount -o remount,rw /data
cd /data
mkdir gingerbread
cd gingerbread
busybox tar zxvf /sdcard/CM7.tar
busybox cp -a /efs efs
sync
reboot recovery
3: Flash "nsonsgs-unsigned-cwm-update.zip" via CWM Recovery
Watch CyanogenMod 7 boot on your phone!
How do I get back?
This is a dual-boot setup... Everything is still intact that you were running before this.
All you have to do is download and flash your previous kernel via ODIN. Once you do this, the phone will reboot into Froyo. Simply reinstall the nsonsgs-unsigned-cwm-update.zip and your back on CM7 again, just like you left it. MAGIC!
What's about this port:
- It uses the Nexus S kernel compiled from sources by supercurio
- It runs the exact /system image release, that I pulled from a CM7 alpha .zip file posted in the NS forums.
Which filesystem?
This is simply a mod of supercurio's early gingerbread preview, so it runs on Ext4. no RFS at all, the kernel don't support RFS.
Does everything work ?
No; will update as I discover more of what does and doesn't work.
Camera is not working.
Wifi is not working.
This can fry the front camera.
Phone could not work . ( sometimes it works )
KEEP IN MIND
CyanogenMod ROMs do not come with any Gapps and using this method, you will not be able to access CWMrecovery to flash the Gapps files floating around. I hope to have an answer to getting Gapps installed with ease by late tonight.
Thanks for all the devs who did this hard work in such a short period of time... please donate to them.
DOWNLOADS:
Kernel : h**p://dl.project-voodoo.org/nexus-s-kernel-on-galaxy-s/nsonsgs-unsigned-cwm-update.zip
CM7 : h**p://dl.dropbox.com/u/17890197/CyanogenMod/CM7.tar
Gingerbread Folder: h**p://dl.dropbox.com/u/17890197/gingerbread.tar
Alberto96 said:
Kernel : http://dl.project-voodoo.org/nexus-s-kernel-on-galaxy-s/nsonsgs-unsigned-cwm-update.zip
CM7 : http://db.tt/TrRnYdm
Click to expand...
Click to collapse
Does this kernel fry front-facing camera?
Just a heads up.
Camera app is not working.
where did this CM7 come from?
from nexus s alpha build . http://forum.xda-developers.com/showthread.php?t=886903
sounds nice, thanks for sharing!
do phone/sms/data/wifi work?
jodue said:
sounds nice, thanks for sharing!
do phone/sms/data/wifi work?
Click to expand...
Click to collapse
Based on my experience from when running the GRH78 build, data etc will work (polling problems persist) Wifi will not work.
Just a heads up for people codeworkx and coolya said not to use this kernel as the voltages are wrong and can cause for you to fry your front facing camera.
They are working on a proper port. Be patient.
Plus its not really alpha because you are not really working in it so how can there be a beta?
This shouldn't really be in the development section.
Sent from my GT-I9000 using XDA App
I was thinking of doing this, never mind
Sent from my GT-I9000 using XDA App
@Alberto96, your CM7.tar.gz file is corrupted !
I've just tried your tutorial in the first post all went well until I typed the line "busybox tar zxvf /sdcard/CM7.tar.gz" then it gived an error :
tar: invalid tar magic
# tar: write: Broken pipe
Click to expand...
Click to collapse
I've tried re-downloading it three times, wipe dalvik cache, update busybox, activate USB debugging but it always gived me this error
tried with supercurios dump and all went well so it can only come from your dump
help will be much apreciated
i will upload a new CM7.tar soon . now i can't because is too late . tomorrow you will have the working one . However, it worked on my Galaxy. Maybe the upload is unsuccessful.
Edit : I did a test and found intact , not corrupted.
7-Zip [64] 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-18
Processing archive: C:\Users\Utente\Downloads\.ptmp573137\system.tar
Testing system
Testing system\app
Testing ..............
Testing system\xbin\vim
Everything is Ok
Folders: 63
Files: 1267
Size: 114894721
Compressed: 115906048
Will check that another time then...
Maybe that's because I tried to download it within the phone, I'm downloading now from my PC but... it is now a CM7.tar.tar file ??
will report back after few minutes...
still the same problem here
I've made a screenshot if it can help...
When you said u tested it what are you meanig ? did you try to flash or do you just clicked on the properties thing on the file ?
@Rawat, you are really boring if you don't want to test it on your GS just go get a life and leave this thread alone ! you are ridiculous...
{
"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"
}
Just bumping this.
This Rom/Port whatever will most likely fry your front camera
skyworxx said:
Just bumping this.
This Rom/Port whatever will most likely fry your front camera
Click to expand...
Click to collapse
Not correct if you don't use it at all
thanks for soft.
but loop boot, not work
device nexus, device android ... device nexus, device android ....
Everyone, we (the mods) have gone over this thread and the ROM posted here, and while it certainly will have a limited appeal and use, it is still within the guidelines for what is allowed...the proper credits, etc are included, and it doesn't violate GPL or any other regulations. Therefore the thread will remain, and I will ask everyone here to keep the discussions related to troubleshooting of the ROM itself.
I firmly believe that we should wait until an official alpha is posted by the CMSGS team.
After hearing of the front camera overvoltage, who knows what else could happen? The devs do, and they are working hard to bring us a great experience.
Excitement is great, but so is patience I'm sure it will be available very soon, so just hold on.
If you have a boot loop you must convert your data in EXT4 . I'm uploading the new file . And you must have mounted has R/W the data folder
i uploaded the new CM7.tar . Please test it on your phones .
{
"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"
}
If you've been following my Twitter feed, you will have noticed i've finally started playing with (and enjoying) my Tab.
I've been playing with ROM updates, ClockworkMod recovery and other bits and bobs, and here is the first fruit of my labour - MoDaCo Custom Kernel r1 for the Samsung Galaxy Tab.
What? Why?
Koush has posted his EXT4 converting ClockworkMod release / kernel at XDA-Developers, however unfortunately it breaks a fair few things on the latest ROMs for international Tabs - keyboard backlights, rotation, camera and a few other bits. So, I set about compiling up my own kernel using Samsung's source, with the aim of including all of Koush's great additions plus the usual TUN and CIFS modules, as well as including things like IKCONFIG to make kernel development easy for others (particularly as I plan to upload the whole lot to github). As well as releasing for EXT4 / ClockworkMod, i've packaged it for standard RFS ROMs. The kernel / ramdisk is 'insecure' (for adb remount etc.).
This turned out to be somewhat traumatic due to the 'update1' Samsung source refusing to work on my device, but I got there in the end. So this is a prelude to the MoDaCo Custom ROM... my MoDaCo Custom Kernel.
Requirements
This kernel has been tested on a number of Tabs running a number of different ROMs with no issues. It comes in two versions - a simple 'RFS' version to use with a regular ROM, or the 'EXT4 ClockworkMod' version if you already have (or wish to) convert to EXT4.
In order to use either kernel you need to be familiar with flashing via Odin or Heimdall, although you could in theory extract the TAR file and flash using 'flash_image' I guess.
If you plan to do the EXT4 conversion, you MUST have a microSD inserted with enough space to do a backup of your system / data partitions (so this will depend on how much data is on your device).
YOU SHOULD BACKUP BEFORE INSTALLATION OR BE FAMILIAR USING ODIN / HEIMDALL FOR FULL SYSTEM RECOVERY IN CASE OF A SERIOUS ISSUE. YOU USE THESE DOWNLOADS AT YOUR OWN RISK!
This kernel is ONLY tested on a UK Galaxy Tab. It MAY work on other GSM Tabs, it almost certainly WON'T work on a CDMA Tab. If you have a non UK Tab and want to test (and know how to flash back to a regular version), then go ahead and report your results. At your own risk.
How to
RFS version
To use the RFS version (i.e. you have not converted to EXT4 yet and don't wish to)...
Download the RFS TAR file from below
Flash using ODIN (version 1.7, do not select the 'repartition' option)
Reboot, you're done!
Optionally download the kernel modules zip (for TUN/CIFS) and copy to a location of your choice
Simple huh?
EXT4 version
To use the EXT4 version (i.e. you are already running EXT4 or you wish to convert)...
Download the EXT4 TAR file from below
Flash using ODIN (version 1.7, do not select the 'repartition' option)
IF YOU NEED TO UPGRADE TO EXT4: Your device won't reboot normally - that's OK, just turn it off (hold down power button for 5 seconds)
IF YOU NEED TO UPGRADE TO EXT4: Load recovery - turn the device on with 'volume up' held
IF YOU NEED TO UPGRADE TO EXT4: Your device will now perform the EXT4 conversion - depending on the volume of your data, this can take a while, so be patient
Reboot, you're done!
Optionally download the kernel modules zip (for TUN/CIFS) and copy to a location of your choice
Downloads
DOWNLOAD
And finally
I hope this is usual for everyone - i've found this is a real performance boost (particularly with the newest ROMs) and I look forward to rolling MCR out for the Tab! I'll have the kernel in GitHub soon, after which i'll post the URL here.
Enjoy!
P
Changelog
r3 26/Jan
Additional governor / scheduler options
Battery icon fix for when device is powered off
Other minor tweaks
r2 24/Jan
Set default governor to 'on demand'
Added Fuse module (by request)
MCK version now shown in about
Updated compiler
EXT4 performance tweaks
r1 23/Jan
Initial release
Looks good!
Great too see you here!
Looking forward to the first MCR!
Does the RFS version include CWM?
On what versions will this work?
Thanks for the effort you put into this. Can you please tell on what version the base Tab must be, to make this kernel work? And also, if it will work with the protected bootloaders?
Thanks again!
Testing it now on Roger/AT&T GSM Tab i987.
It is backing up and converting to ext4 right now.
It would be helpful if you put GSM in the title, or Euro for that matter, if that's the case.
Cheers Paul,
Will give the EXT4 a whirl once I work out the pros/cons
Confirmed that it works for NA GSM Tabs. Converted everything over to ext4 and working.
No real increase in speed really. Quadrant scores are about the same...around 1000.
Gallery has some glitches were it does not show pictures the first time...have to exit and come back in.
Let's give it a shoot
Sent from my GT-P1000 using Tapatalk
rmanaudio said:
Confirmed that it works for NA GSM Tabs. Converted everything over to ext4 and working.
No real increase in speed really. Quadrant scores are about the same...around 1000.
Gallery has some glitches were it does not show pictures the first time...have to exit and come back in.
Click to expand...
Click to collapse
I get this on all my Android devices now and again if a media index is running (generally soon after a boot)...
P
paulobrien said:
I get this on all my Android devices now and again if a media index is running (generally soon after a boot)...
P
Click to expand...
Click to collapse
Really weird problem where browser (with google.com as homepage) starts to rotate itself once you open browser till it is upside down!
If you have any issues, please post your ROM version and whether you are on the latest release.
I am on XXJMF and don't experience the issues mentioned above.
P
Great work man thank you!!! Only 1 ( noob i think question ) : what exactly do the additionals zip TUN/CIFS?
Frustu said:
Great work man thank you!!! Only 1 ( noob i think question ) : what exactly do the additionals zip TUN/CIFS?
Click to expand...
Click to collapse
If you don't know what they are, you don't need them
Screenshot from r2 (coming tomorrow).
P
TheGrammarFreak said:
If you don't know what they are, you don't need them
Click to expand...
Click to collapse
Ah ok thank you ... But i m curious please tell me
Im on Roto JME v4...and only problem found is Web browser rotates itself 180 degrees when you start it up.
Frustu said:
Ah ok thank you ... But i m curious please tell me
Click to expand...
Click to collapse
http://lmgtfy.com/?q=What+is+CIFS
http://lmgtfy.com/?q=What+is+TUN
TheGrammarFreak said:
http://lmgtfy.com/?q=What+is+CIFS
http://lmgtfy.com/?q=What+is+TUN
Click to expand...
Click to collapse
Well i learn 2 new things thank you
I have had my Desire Z since October 2011. It has been great. I love the phone, and the swing-out keyboard with the number keys missing hasn't bothered me at all.
What does bother me is HOW DANG SLOW my phone is now. I installed Cyanogen 7, the last build available for Desire Z. I seem to remember the phone being responsive when I installed. However, now, the phone is almost becoming unusable. Starting applications like Google Maps frequently results in the "Wait / Force Close" dialog. It can take 10 seconds to realign the screen when I move the keyboard. I've tried CPU monitoring but don't find anything in the background eating the CPU.
What's going on? Lately I've thought about buying a new phone, but I love my Desire Z! (and I've already paid for it and I should get 2 years out of a phone)
Mine is snappy as ever, try a different kernel, a different ROM, partition to ext4, supercharge it, add swap, compcache or zram, pimpmyrom, remove bloat and bad apps, overclock, etc. there are so many things you can do to change how your phone performs, try some things find what works for you.
Then again your idea of slow may differ than mine, I will say that I can hardly remember what a force closed looks like as its been so long...
Sent from my Nexus 7 using xda premium
How do I find out what's slow? And how to make it faster?
My G2 is slow because I've had it for over two years now, it's single-core and is pretty slow even compared to the first dual-core Android phones, I've flashed numerous ROMs on it, etc. In spite of all of that, it has been my most reliable Android phone and is always the one I grab when I brick any other device of mine.
By the way, flash one of Flinny's CM10.1 ROMs and thank me later.
Hi.
Try to stay free ROM more than 500Mb.
AW: [Q] Why is my Desire Z so DANG SLOW?
I would recommend to flash the latest official CyanogenMod 7.2 for DesireZ. It's the fastest in daily use for me.
I also tested Flinnys CM10.1 but flashed CM7.2 again after a couple of days, because it does not run as smooth as CM7.2 and the new features do not wight it.
demkantor said:
Mine is snappy as ever, try a different kernel, a different ROM, partition to ext4, supercharge it, add swap, compcache or zram, pimpmyrom, remove bloat and bad apps, overclock, etc. there are so many things you can do to change how your phone performs, try some things find what works for you.
Then again your idea of slow may differ than mine, I will say that I can hardly remember what a force closed looks like as its been so long...
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
seriously, mine is fast too. If I compare it with a s2, my dz isn't that bad at all!
viperZ is very impressive, I dont know what they did on this rom, but it's fast.
-no swap
-no ext4
-no supercharge
- zram off
-seeder entropy ON
- animation off
- 2d force gpu
- smartassv2 governor
- 1.4 ghz
mobil_z said:
I would recommend to flash the latest official CyanogenMod 7.2 for DesireZ. It's the fastest in daily use for me.
I also tested Flinnys CM10.1 but flashed CM7.2 again after a couple of days, because it does not run as smooth as CM7.2 and the new features do not wight it.
Click to expand...
Click to collapse
Cyanogen 7.2 is exactly what I'm running! It's the latest version of Cyanogen ever released for Desire Z. I just can't understand why other peoples' phones are OK while mine drags. It's the same hardware and software!
its your apps that are installed or your not partitioned to ext 4 or many other things.
personally i havent liked 7.2 for the vision and dont use it as i found it a bit buggy. like i said try a few roms and try some various mods and settings, find what works for you
I noticed this too. Supercharging it helped a bit
---------- Post added at 09:41 PM ---------- Previous post was at 09:41 PM ----------
Another recommendation is to clean your sdcard. Some apps leave crap and crap all over the SD card and you install/uninstall some and its still there. Might help.
{
"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"
}
What does this tell anyone?
I don't think it's stuff on the SDcard. That's data, it just sits there and doesn't interfere with the operation of the system.
gromky said:
What does this tell anyone?
I don't think it's stuff on the SDcard. That's data, it just sits there and doesn't interfere with the operation of the system.
Click to expand...
Click to collapse
Could Overclock a little, like others said have you tried supercharge or if you dont like messing with scripts there is always
https://play.google.com/store/apps/...sImNvbS5qcnVtbXkuYXBwcy5tZW1vcnkubWFuYWdlciJd
Also check a task manager see what background programs are running sometimes apps on the sdcard don't just sit there I like android assistant made by Aaron. mainly for its 4x1 widget. Also I have found if things sync alot then my phone seems slower along with short battery.
Hope that helps a little
gromky said:
[I don't think it's stuff on the SDcard. That's data, it just sits there and doesn't interfere with the operation of the system.
Click to expand...
Click to collapse
And that data does what? Just sit there? No, it is constanly being (more) read and (less) written to. That has a overhead.
Check your apps and delete any innceesary ones.
gromky said:
What does this tell anyone?
I don't think it's stuff on the SDcard. That's data, it just sits there and doesn't interfere with the operation of the system.
Click to expand...
Click to collapse
Get SD Main from the Play store and run corpse finder a system cleaner. See if anything's clogging your sd card and / or /data/ partition up, and clean it.
Also use swap enabler to move apps to sd-ext (I wouldn't recommend memory swap though) this noticeably and immediately speeds my G2 up.
AW: [Q] Why is my Desire Z so DANG SLOW?
HTCDreamOn said:
I wouldn't recommend memory swap though
Click to expand...
Click to collapse
Right, unfortunately CM does not support a swap partition as far as I know.
Somebody knows a kernel, what can be flashed in CM7.2 to support swap?
mobil_z said:
Right, unfortunately CM does not support a swap partition as far as I know.
Somebody knows a kernel, what can be flashed in CM7.2 to support swap?
Click to expand...
Click to collapse
Of course it does. Check if you have an sd-ext partition, if you don't know then you probably don't have one, in which case backup your SD card onto your computer, reboot to recovery and select partition SD card, wherever that may be. You don't need a swap partition, and if you have room I would suggest having a 1.5GB SD ext, although 512MB is fine for me.
Now put all the data back onto your SD card which you backed up to your computer earlier, if you get errors then don't copy over .android_secure, Android, and data folders (along with any other .folders / hidden folders).
Now reboot to recovery and flash swap enabler select skip data swap and SD swap but enable sd-ext, it should give you happy messages about it working and then you can reboot. You'll notice you'll have an init.d script and your apps will have moved to SD ext. If you don't like it, just flags swap enabler again and remove it, it will move your apps back for you.
This relies simply on an init.d script as I said, which literally just moves and binds /data/app to sd-ext, don't worry about kernels or anything.
By the way, I would upgrade from Gingerbread if I were you.
Also, if you're only getting 3500ish in An tutu, there is a problem because I get over 3700 at 768MHz in Andromadus CM10.1
I just used SDmaid's "corpsefind" function. After deleting files, my Chinese dictionary didn't work, ADWlauncher crashed and wouldn't come back up, and when I reboot the system was screwed up and needed to be restored. It's a bit too agressive in "cleaning" the system. It deleted files that were still in use by installed applications.
gromky said:
I just used SDmaid's "corpsefind" function. After deleting files, my Chinese dictionary didn't work, ADWlauncher crashed and wouldn't come back up, and when I reboot the system was screwed up and needed to be restored. It's a bit too agressive in "cleaning" the system. It deleted files that were still in use by installed applications.
Click to expand...
Click to collapse
It shouldn't, it usually just gets rid of databases left behind by uninstalled apps. If you're getting these sorts of problems you really should do a full clean install, maybe try some different ROMs.
{
"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"
}
Disclaimer: We are not responsible for any damages on your device.
Original Slim Features:
The Real Dark Slim
Notification drawer Shortcuts
Full hardware key rebinding!
Keyboard rotation
SlimCenter
Check out our full feature list here
Changelog
Find our latest Changelog go here
Chat with the slim team and other slim users
IRC: #slimusers
New to IRC? Don't have a native app? Try the Freenode web client [link] or the Firefox extension Chatzilla [link]
Google+ [link]
Twitter [link]
Facebook [Link]
Installation instructions
For Most Users
Please keep in mind if a special instruction is needed it will be noted in the Changelog
Download the latest build from [here]
Addons ( 4.3 packages are different from 4.2.2) from [here]
!Recommended! Full wipe, and manual format /system
Flash ROM and the addons you want, reboot
FAQ
Check out out FAQ before posting! Keeps more common questions answered in one place!
To get root working go to Settings/Developer options/
Then change the option "root access" to "apps and adb".
Help us out!
If you want to help us by translating slim to your language check out Crowdin.net and submite your translations.
Or consider a donation.
Thanks!
You can find the full list of credits here
Source
Please visit here for the rom source code.
Kernel source can be found here
NOTE : To get root working go to Settings -> Developer options, then change the option "root access" to "apps and adb".
NOTE: Completely new base with over 5 million code changes.... Please format system and factory reset to avoid any issues.!!!
I'm always getting an 'android.process.media' FC when installing 4.3beta, installation was done according to the instructions (twice!).
Known issue or just me?
First of all, BIG THANKS to SlimTeam for providing SlimBean 4.3 to SGS1 :thumbup:
One question, may I know what does it mean by the statement in Slim website about Titanium Backup below?
* If you use TitaniumBackup you need to change in settings you backup/restore path to "legacy" *
I was trying to find this setting but couldn't find any.
Kindly elaborate more. Thank you.
thank you further quick update.waiting for native su/root fix.4.3 is new so will take time to fix those small bugs.
surubutna said:
I'm always getting an 'android.process.media' FC when installing 4.3beta, installation was done according to the instructions (twice!).
Known issue or just me?
Click to expand...
Click to collapse
Cannot reproduce here.. try a massive wipe and system format and reinstall.. clean up the storage if possible, may contain corrupted media files.
rmsinaga said:
May I know what does it mean by the statement in Slim website about Titanium Backup below?
* If you use TitaniumBackup you need to change in settings you backup/restore path to "legacy" *
I was trying to find this setting but couldn't find any.
Kindly elaborate more. Thank you.
Click to expand...
Click to collapse
I suppose it was applicable only for the restore option in some particular version of titanium backup. Will look into it.
senotrius said:
thank you further quick update.waiting for native su/root fix.4.3 is new so will take time to fix those small bugs.
Click to expand...
Click to collapse
SU works all fine on slim. You just have to select 'Apps and ADB' in developer options as mentioned in OP.
surubutna said:
I'm always getting an 'android.process.media' FC when installing 4.3beta, installation was done according to the instructions (twice!).
Known issue or just me?
Click to expand...
Click to collapse
Same here. Just installed the beta1 with full wipe and format /system. I did a wipe cache and wipe dalvik cache and rebooted. Now it seems to be working ok.
Edit: can't get root access. I had the same problem yesterday with Mackay Rom 3.0.0 (4.3 base). Solution was to enable developer options >> root access >> enable (or similar).
I'm always getting an 'android.process.media' FC when installing 4.3beta, installation was done according to the instructions (twice!). fuul wipe 4 times and dalvik cache all but same and googla apps proces stoped
AWESOME!!! Gonna wait a bit until it is stable... only in build 7.5-8 and using cyancore 2.8.6 i finally managed to make my phone stable and i don't wanna ruin it now but thanks a lot slim team... best dev team out there!
aamor said:
I'm always getting an 'android.process.media' FC when installing 4.3beta, installation was done according to the instructions (twice!). fuul wipe 4 times and dalvik cache all but same and googla apps proces stoped
Click to expand...
Click to collapse
Which gapps you are using? have to use gapps for 4.3
Samtan4326 said:
Which gapps you are using? have to use gapps for 4.3
Click to expand...
Click to collapse
yes 4.3
aamor said:
yes 4.3
Click to expand...
Click to collapse
do a wipe cache and wipe dalvik cache and reboot.
Samtan4326 said:
do a wipe cache and wipe dalvik cache and reboot.
Click to expand...
Click to collapse
zes 4 times and same,but never mind i install other.tnx
After flash ROM do 2 wipe without format
Sent from my GT-I9000 using xda app-developers app
Since there is no Semaphore kernel for Android 4.3 yet is there any chance you will implement Devil kernel? 4.3 version is floating around here somewhere. I used to flash it with Slim 4.2.2 builds and it rocked.
Edit: here's Devil Kernel for 4.3: http://forum.xda-developers.com/showpost.php?p=44389038&postcount=276
How can i install the old keyboa rd, the one from 4.2.2 builds?
senotrius said:
thank you further quick update.waiting for native su/root fix.4.3 is new so will take time to fix those small bugs.
Click to expand...
Click to collapse
there will be never a native su/root fix because root is now beginning to be a thing of the past. Google introduced selinux into aosp which gives the possibility that apps can get explicit permissions to do operations over it without an overall root. Which has the big advantage that your phone is way more secure. There are really only some smaller cases which do not work without root (like firewalls and something like that) but thats it.
So do not expect at least from us that we break this system like some other roms are doing. We will leave root of course...but it is not anymore enabled by default and respects the new selinux integration. So for now you need to enable it....and when all devs have changed their apps all is well without the need of root. Just a thing of time.
Maybe a nice short easy readup about it from steve
http://www.dailytech.com/CyanogenMod+Creator+Tells+Android+Users+to+Rethink+Rooting/article33058.htm
about titanium backup (they did not update till now a fixed tibu version):
go into preferences->set backup/restore path....hit 2 times the back button then you are in /storage/emulated/ then press legacy and then press titaniumbackup...then press use the current folder....then 2 times ok...tibu will restart
that has something to do with selinux permissions...tibu need to change that due it is not longer the case that all emulated folders are mounted due of security reasons some ppl just flash SuperSU to solve this problem due that supersu is mounting it back the old way but that breaks selinux completly and is just a dumb solution tibu will com with an update for sure
kiddoo said:
How can i install the old keyboa rd, the one from 4.2.2 builds?
Click to expand...
Click to collapse
Solved.
THX ROM fantastic :beer:
aamor said:
I'm always getting an 'android.process.media' FC when installing 4.3beta, installation was done according to the instructions (twice!). fuul wipe 4 times and dalvik cache all but same and googla apps proces stoped
Click to expand...
Click to collapse
Clear data of Gallery.apk then reboot!
OnePlus One CyanogenMod 11S for the Oppo Find 7a
People with much better skills and more time on their hands than me have been doing great work on this after I initially posted it. I am updating the OP with their comment. Please give all credit to them.
CM11s for Find 7(a) V3: DOWNLOAD
SDCard Support Package V3: DOWNLOAD
Changelog:
*) Removed NFC Support (it was broken anyway, and consumed a lot of battery)
*) Greatly increased Battery Runtime (see above why)
*) VOOC Charging Support
*) SDCard Lagfix (for those using the SDCard Support Image, if you like benchmarks see appendum)
Appendum:
SDCard Benchmark before Lagfix (128GB Sandisk SD Card):
27.82MB/s Read / 12.48MB/s Write
SDCard Benchmark after Lagfix (128GB Sandisk SD Card):
39.42MB/s Read / 12.55MB/s Write
INSTRUCTIONS FOR INTERNAL MEMORY USERS (10GB Storage)
1. Install TWRP Recovery
2. Install cm11s-oppo-find7a.zip
3. In TWRP Recovery do... Wipe -> Advanced Wipe -> Tick System, Cache and Internal SD -> Slide to Wipe
4. Reboot System
INSTRUCTIONS FOR EXTERNAL MEMORY USERS (as much storage as your SD-card can offer, for me thats 128GB)
1. Format your SD-Card as EXT4 and plug it into your Find 7(a)
2. Install TWRP Recovery
3. Install cm11s-oppo-find7a.zip followed directly by sdcard-data.zip
4. In TWRP Recovery do... Wipe -> Advanced Wipe -> Tick System and Cache -> Slide to Wipe
5. Reboot System
Final Notes
This bundle includes the first two OTAs from the first page of this topic, a bunch of sensor configuration changes to fix the sluggish behavior of the GUI and the slow (un)locking of the screen as well as the proper Find 7(a) radio binaries to give you proper reception.
The Back Camera is still upside-down with this package and just like many other people in this topic I'm still researching why that is the case / how to fix it. Truth be told though I think someone else will have it figured out way before me!
Also - this ROM is meant to work with a "unified storage" at its core.
The basic installation will use the internal /sdcard partition as its unified storage (rather than the leak on page 1 which uses /data) giving you 10GB of unified storage for both your apps and data.
If you need more storage, you can flash the optional sdcard-data package which will use your external SD-card as the unified storage for apps, settings and data.
To do that though your SD-card has to be EXT4 formatted, I suggest using Ubuntu plus the gparted Tool to get the job done, a live-boot-disc is enough to do that.
As for me, I highly suggest going the SD-card unified storage route, its damn nice having 128gb of unified storage to work with.
Also, should you ever need to back your data up all you have to do is pull the SD-card and copy it somewhere using Linux (all your data - and I do mean ALL - is stored on that SD-card after all thanks to the unified storage).
PS. Unlike what some other people have told here, using this build with the changed sensor configuration seems to run okay on FastCharging from what I can tell. Non the less please handle all of this thread's contents as early early alpha content and expect to run into bugs.
Should you find any, please report them and / or share constructive criticism on how to fix them.
rayfin said:
You can install the OnePlus One ROM from the OnePlus One on the Find 7a.
What works:
Front Camera / Video
Microphone
WiFi
Data
Bluetooth
Sound
GPS
Calling
What doesn't work:
Rear Camera / Video are upside down
Voice Wake
NFC
Storage is only reporting 3GB
--------------------
I modified the updater script to not check for the OnePlus One (bacon) when flashing. You can download it here:
Full ROM: http://www.androidfilehost.com/?fid=23487008491963275
OTA: http://www.androidfilehost.com/?fid=23487008491963298
Click to expand...
Click to collapse
Awesome! Thanks. Now someone needs to tinker with it and get everything tweaked to work properly on the 7a.
Nice.. Now give me credit
Sent from my One using Tapatalk
rayfin said:
You can install the OnePlus One ROM from the OnePlus One on the Find 7a.
What works:
Front Camera / Video
Microphone
WiFi
Data
Bluetooth
Sound
GPS
Calling
What doesn't work:
Rear Camera / Video are upside down
Voice Wake
NFC
Storage is only reporting 3GB
--------------------
I modified the updater script to not check for the OnePlus One (bacon) when flashing. You can download it here:
Full ROM: http://www.androidfilehost.com/?fid=23487008491963275
OTA: http://www.androidfilehost.com/?fid=23487008491963298
Click to expand...
Click to collapse
I've got the ColorOS rom downloaded, so I'll give this a shot tomorrow after work and report back.
Doesn't look like there could be too much more to fix (other than optimizations of course) in order to get this ported completely...
rear camera can likely be fixed by using find7a's sensor conf
http://www23.zippyshare.com/v/76743245/file.html
^ second system update
ayysir said:
http://www23.zippyshare.com/v/76743245/file.html
^ second system update
Click to expand...
Click to collapse
Hi Ayysir, do you have any idea of what has been changed with this update?
MicMeo said:
Hi Ayysir, do you have any idea of what has been changed with this update?
Click to expand...
Click to collapse
The OnePlus One is currently running a pre-production build of CM11S. This is another OTA to get bugs squashed before launch.
ayysir said:
http://www23.zippyshare.com/v/76743245/file.html
^ second system update
Click to expand...
Click to collapse
I'll take a look at this when I get home in a few see of I can get it working.
Sent from my One using Tapatalk
graffixnyc said:
I'll take a look at this when I get home in a few see of I can get it working.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
2nd update is 109 mb
{
"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"
}
ayysir said:
2nd update is 109 mb
Click to expand...
Click to collapse
@ayysir: It would be very appreciated if you could upload the 2nd update to another host as I'm downloading from Zippyshare with around 2KBps.
Cheers.
Please post screenshots or updates so we know how it's going and what everything looks like. Kudos to person/persons responsible for porting this to the 7a.
Looks fun ! Same device with another name... then another ROm... Portage can be easy enough...
babyree said:
Please post screenshots or updates so we know how it's going and what everything looks like. Kudos to person/persons responsible for porting this to the 7a.
Click to expand...
Click to collapse
use google.com and youtube.com... plenty to find there
There is no need to download all updates. You guys can flash original 1+1 recovery and then you get all 1+1 updates OTA.
Gesendet von meinem One mit Tapatalk
When you do so, are there any bugs left? Because if not they wouldn´t get fixed because of the original ota which is for the oneplus, or not?
EnormoDerClown said:
When you do so, are there any bugs left? Because if not they wouldn´t get fixed because of the original ota which is for the oneplus, or not?
Click to expand...
Click to collapse
ofc there is bugs... sensors is derped and storage is mapped for internal sd only
That´s what i thought, but than an official ota is useless, because you will never be able to use the phone fpr 100%, or not?
ayysir said:
ofc there is bugs... sensors is derped and storage is mapped for internal sd only
Click to expand...
Click to collapse
I think AOSPA is round the corner because you can use alot stuff from 1+1.
m3dd0g said:
I think AOSPA is round the corner because you can use alot stuff from 1+1.
Click to expand...
Click to collapse
actually wrong, most of the blobs are the same and cm using some old configs