Related
Does anyone have an idea (steps) on how to push ext4 on Galaxy W stock rom..? Since I saw a lot custom rom of our W already had it.
Sooo.. no one want to share the knowledge
pmeler said:
Sooo.. no one want to share the knowledge
Click to expand...
Click to collapse
I am extremely sorry about that. If i had knowledge I would sure let you know it.
I hope if we are the real Open Source Developer then someone will come up and will reply your query.
You can try link2sd from market.it uses the ext4 to efficiently reorganize how apps uses memory..e.g. It'll use ext4 to store some app libs and data hence allowing more apps to be installed..give it a shot..
Sent from my GT-I8150 using xda premium
faizulrahim said:
You can try link2sd from market.it uses the ext4 to efficiently reorganize how apps uses memory..e.g. It'll use ext4 to store some app libs and data hence allowing more apps to be installed..give it a shot..
Click to expand...
Click to collapse
Thank's.. but I want to know HOW TO, not just using available app
When I'm running the script, one error catches my attention
/sys/module/lowmemorykiller/parameters/adj: No such file or directory
I checked and it's true, the adj file is not there. How do I recreate it? And what do I put in it? How did it get deleted?
Anyone?
Sent from my Galaxy Nexus using Tapatalk 2
Same problem here... what changed? What version ROM are you running, JBNEX? I'm on CM10 10/21/2012 , just wanting to see if it is apparent in the newer versions of CM10 only. If so, I might go back a few.
socioteq said:
Same problem here... what changed? What version ROM are you running, JBNEX? I'm on CM10 10/21/2012 , just wanting to see if it is apparent in the newer versions of CM10 only. If so, I might go back a few.
Click to expand...
Click to collapse
I'm on XenonHD, its a kernel problem. You have to flash a kernel that supports adj, like Franck and it will work
For those who prefer open source builds, rather than "Factory Images", here is a zip which is a stock, AOSP 4.3 build, straight from source. Why post this when anyone could make it? Well, it seems Google messed up their binary drivers, so it took me a little while to fix them, and fix the problems and get the ROM booting (they put the wrong mali GLES driver in their blob package).
Anyway, I have fixed that, and made it build successfully, so without futher ado, an AOSP (no google proprietary apps etc) build of 4.3 for the Nexus 10. The fixed vendor blobs are available at https://github.com/pulser/vendor_samsung_manta for anyone wanting to build themselves, and all can be verified, as they came from the "Factory Image" of 4.3 for the Nexus 10.
This is a pure AOSP build, there is no boot animation or any other "Google" things - just a plain, pure, AOSP build.
Enjoy, and this can be rooted using Chainfire's current 4.3 root method using SuperSU, which is detailed at https://plus.google.com/+Chainfire/posts/WqS2E9kkN1L
Feel free to use, share, re-use, distribute, copy, paste, mirror, ignore, root, tweak, patch or mod. I am not like certain individuals who go ZOMG NO MIRRORS PLEASE... Go on, mirror, make a torrent if you want, and share it if anyone actually cares about this
Tested:
Wi-Fi
Bluetooth
GPS
Auto rotation
Accelermeter
Magnetic Field Sensor
Brightness Sensor (and Autobrightness)
Barometer
Seemingly not working:
Proximity sensor (not detected, but apparently has one)
Download:
http://goo.im/devs/pulser/Nexus10
Hmmm...I'm co cerned what you said about they put the wrong Mali driver in. What does this effect for those of us who flashed the stock image from the website?..
Sent from my SCH-I535 using xda app-developers app
duarian said:
Hmmm...I'm co cerned what you said about they put the wrong Mali driver in. What does this effect for those of us who flashed the stock image from the website?..
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Stock image isn't the AOSP?
I am not worrying.
Thanks OP.
duarian said:
Hmmm...I'm co cerned what you said about they put the wrong Mali driver in. What does this effect for those of us who flashed the stock image from the website?..
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Nothing to worry about. I took the RIGHT driver from the factory image (stock image).
The AOSP release they made had wrong blobs, I rectified it with the correct files from the stock image.
I missed a blob:
https://github.com/pulser/vendor_samsung_manta/commit/4c534c24407a163bc16bfa24cb769aef7ab9ebd3
Push to /system/vendor/lib/
pulser_g2 said:
I missed a blob:
https://github.com/pulser/vendor_samsung_manta/commit/4c534c24407a163bc16bfa24cb769aef7ab9ebd3
Push to /system/vendor/lib/
Click to expand...
Click to collapse
How do we download the file/blob please?
Never downloaded anything from Github before...
pulser_g2 said:
For those who prefer open source builds, rather than "Factory Images", here is a zip which is a stock, AOSP 4.3 build, straight from source. Why post this when anyone could make it? Well, it seems Google messed up their binary drivers, so it took me a little while to fix them, and fix the problems and get the ROM booting (they put the wrong mali GLES driver in their blob package).
Anyway, I have fixed that, and made it build successfully, so without futher ado, an AOSP (no google proprietary apps etc) build of 4.3 for the Nexus 10. The fixed vendor blobs are available at https://github.com/pulser/vendor_samsung_manta for anyone wanting to build themselves, and all can be verified, as they came from the "Factory Image" of 4.3 for the Nexus 10.
This is a pure AOSP build, there is no boot animation or any other "Google" things - just a plain, pure, AOSP build.
Enjoy, and this can be rooted using Chainfire's current 4.3 root method using SuperSU, which is detailed at https://plus.google.com/+Chainfire/posts/WqS2E9kkN1L
Feel free to use, share, re-use, distribute, copy, paste, mirror, ignore, root, tweak, patch or mod. I am not like certain individuals who go ZOMG NO MIRRORS PLEASE... Go on, mirror, make a torrent if you want, and share it if anyone actually cares about this
Tested:
Wi-Fi
Bluetooth
GPS
Auto rotation
Accelermeter
Magnetic Field Sensor
Brightness Sensor (and Autobrightness)
Barometer
Seemingly not working:
Proximity sensor (not detected, but apparently has one)
Download:
http://goo.im/devs/pulser/Nexus10
Click to expand...
Click to collapse
Is this why the latest version supported for manta is 4.2.2r1 (according to this) while everything else is 4.3xx?
Explains why I can't get a flashable build.
This is why I stick to factory images.
ridobe said:
Is this why the latest version supported for manta is 4.2.2r1 (according to this) while everything else is 4.3xx?
Explains why I can't get a flashable build.
Click to expand...
Click to collapse
It may well be, but the factory image is available.
But some of us don't want GApps, and don't want binary parts (save for the necessary evil of drivers), which is where AOSP builds come in.
pulser_g2 said:
It may well be, but the factory image is available.
But some of us don't want GApps, and don't want binary parts (save for the necessary evil of drivers), which is where AOSP builds come in.
Click to expand...
Click to collapse
Thanks. I like to build for myself but couldn't figure out why I couldn't flash successfully. Upon further investigation it appears that it is not supported (yet) in aosp. I'm running the factory images for now instead. However, this evening I'm going to flash this.
I just want to make sure. This wont wipe my internal hard drive. First time i flashed the new 4.2 i lost everything and cant backup anything as of now because i am outta town the whole summer.. Plz if anybody can confirm
Sent from my Nexus 10 using Tapatalk HD
BabyHuey said:
I just want to make sure. This wont wipe my internal hard drive. First time i flashed the new 4.2 i lost everything and cant backup anything as of now because i am outta town the whole summer.. Plz if anybody can confirm
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
I am not aware of anything to deliberately wipe /data, but I strongly suggest you don't flash this, unless you are willing to lose things? Why? because I didn't test every possible situation that could come up. I also didn't CHECK that /data remained...
So perhaps take the OTA (if you're on stock)? Or just hang off? It's nothing hugely special in my opinion.
pulser_g2 said:
I also didn't CHECK that /data remained...
Click to expand...
Click to collapse
It does, I flashed it.
Would still like to know how to get those missing blobs...
stonebear said:
It does, I flashed it.
Would still like to know how to get those missing blobs...
Click to expand...
Click to collapse
So nothing will be wiped?
Sent from my Nexus 10 using Tapatalk HD
BabyHuey said:
So nothing will be wiped?
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
My data remained, but I would be concerned if you took a chance on my say so and something went wrong. I was ok but maybe you wouldn't be for some reason.
Sent from my Nexus 7 using Tapatalk 4 Beta
stonebear said:
It does, I flashed it.
Would still like to know how to get those missing blobs...
Click to expand...
Click to collapse
Which ones? The blobs are in the github link and came from the factory image. I'm not aware of any missing ones.
pulser_g2 said:
Which ones? The blobs are in the github link and came from the factory image. I'm not aware of any missing ones.
Click to expand...
Click to collapse
I don't know how to download them. Are they downloadable?
I suppose if I could understand the page I would know which ones to take from the factory image...noob, sorry.
Is it just "libRSDriverArm.so"?
http://d-h.st/aPi
4.3 gapps
Sent from my AOSP on Manta using Tapatalk HD
Thanks pulser_g2 for adding the correct binary blobs! Glad I'm not completely insane like I thought I was, I too noticed that Google had forgotten to provide the correct graphics driver binaries so I tried building 4.3 with the 4.2.2 graphics binaries and it not surprisingly didn't boot past the Google logo. Glad we could get this fixed :good:.
stonebear said:
I don't know how to download them. Are they downloadable?
I suppose if I could understand the page I would know which ones to take from the factory image...noob, sorry.
Is it just "libRSDriverArm.so"?
Click to expand...
Click to collapse
Sure, that is the only "blob" I am aware I forgot. The N10 supposedly supports Bluetooth 4 (LE), but I have no idea how to test it, as I don't have any Bluetooth 4 LE devices. Can anyone test that? I will update the system.img today for you to make it easier It was only one blob I missed, and it only affects using front facing camera I believe.
I'm taking over a friends old R800i next week and I'm really looking forward to it since I've wanted one of these since about when it was released.
What I'm looking for is a rom that gives me all the usual stuff - GSM connection, working 3G, wifi, gps, sms, mms, camera - but, will a custom rom give me better performance for emulation?
I want to be able to emulate all kinds of consoles without losing too much performance due to the rom - nor do I want my battery to get drained while the phone isn't in use. I'm of course ready to try a bunch of roms and I have looked at some of the threads, without learning much to be honest. I'm not even up to date with who's roms are the stable ones or which is the highest SE provided rom for Play either.
Looking to emulate N64, nes, PS and sega genesis, mainly.
If you root and debloat the stock rom, you will get excellent gaming performance. I went rom using custom roms and went back to stock as it provided the best performance all around.
ozzmanj1 said:
If you root and debloat the stock rom, you will get excellent gaming performance. I went rom using custom roms and went back to stock as it provided the best performance all around.
Click to expand...
Click to collapse
Have a quicklist of which items to uninstall? Is there timescape and other such stuff on the Play?
Also, which android version do you use? 2.3.4?
Was waiting for a thread like this,
Visit Gene real and take a look at the Ace xp setup,
Sent from my R800i using xda app-developers app
stock rom is great even without any tweaks
you only need to debloat it
pedyvirus said:
stock rom is great even without any tweaks
you only need to debloat it
Click to expand...
Click to collapse
Guess I should use the latest provided rom from SE? Which one is it anyway?
well pizza_dox has a stock debloated of 79 frimware
but i cant find it now
but it had a little bug that its very easy to fix it(problem wasnt little but it was very easy to fix it)
Oh yeq,
It was in my Sig and I forgot to include SEMCSetupWizard which broke the home button...
Sent from my R800i using xda app-developers app
as i know editing the build.prob without adding the setup wizard again will solve the problem(there is aline about setup wizard in build.prob. but i cant test it now)
pedyvirus said:
well pizza_dox has a stock debloated of 79 frimware
but i cant find it now
but it had a little bug that its very easy to fix it(problem wasnt little but it was very easy to fix it)
Click to expand...
Click to collapse
Well Pizza_dox is an asshat refusing to answer on relevant questions in the thread he made for "the perfect setup", so I need a reliable source to go after since I have no idea what following the guide he provides will actually do to the phone (and I'm not going to learn by failing, hence why I ask questions which she/he refuses to respond properly to)
Dude sorry... But I might have been bussy and forgot to check the thread...
Sent from my R800i using xda app-developers app
niklasson said:
Well Pizza_dox is an asshat refusing to answer on relevant questions in the thread he made for "the perfect setup", so I need a reliable source to go after since I have no idea what following the guide he provides will actually do to the phone (and I'm not going to learn by failing, hence why I ask questions which she/he refuses to respond properly to)
Click to expand...
Click to collapse
Please act respectful: PizzaDox has opened many manu threads, and he can't be repling at all of them.
Anyway debloating a rom is simple and can be done by everyone that wants to, by extracting the system.sin from your .79 ftf, dumping its data with flashtool in order to make it a yaffs img, extracting it with a yaffs extractor and then removing the apps located into "app" that you consider as bloat
Sent from my R800i using xda app-developers app
Hello ,
My last ROM problem was solved and I know have CM9 ROM .
But I noticed that the files on my sd card are still there ,and I want a Clean start .
I am used that they are deleted whenever I made a ( Reset to factory settings ) as I was making always before thinking to Root and make Custom ROM ,
I just wanted to know what would happen if I Made a ( Reset to factory settings ) from the settings menu ,
ofcourse I know my backup that I have on the internal card will be deleted but :
Will I lose the Root ?
Will I lose the Custom ROM and go back to the original ROM ?
The second question is , I heard before that I can share some space from my external sdcard to my internal sd card , is that really possible by any method ?
Sorry for long topic .
Any one ?
Search on the W forum for a thread by @pepoluan about 'pristine' wiping your phone....it will help you achieve the 'fresh start' that you want....and yes, unless you move your nandroid to alternative storage, you will probably lose it.
And as far as I remember, CM9 has the option to swap storage mounts which will allow you to use your external micro SD card as phone storage......
Find it by......
Menu>>settings>>storage>>menu>>advanced....
and then 'tick' the box against (something like) 'use SD card as phone storage' (it's been a while so I can't remember the exact wording)......
Sent from my GT-I9100 using xda app-developers app
AhmedPower said:
Hello ,
My last ROM problem was solved and I know have CM9 ROM .
But I noticed that the files on my sd card are still there ,and I want a Clean start .
I am used that they are deleted whenever I made a ( Reset to factory settings ) as I was making always before thinking to Root and make Custom ROM ,
I just wanted to know what would happen if I Made a ( Reset to factory settings ) from the settings menu ,
ofcourse I know my backup that I have on the internal card will be deleted but :
Will I lose the Root ?
Will I lose the Custom ROM and go back to the original ROM ?
The second question is , I heard before that I can share some space from my external sdcard to my internal sd card , is that really possible by any method ?
Sorry for long topic .
Click to expand...
Click to collapse
Will I lose the Root ?
Click to expand...
Click to collapse
using reset to factory settings will not lose your root, afair coz i've used that b4.
Will I lose the Custom ROM and go back to the original ROM ?
Click to expand...
Click to collapse
when u install custom rom basically ur stock rom (original rom) is already erased, right? so i don't think it will restore ur stock rom, u can try it though
How do I swap the internal and external SD on CM9 ?
Click to expand...
Click to collapse
Settings -> Storage->Menu-Button->Storage configuration (a restart might be necessary)
for clean installation: Going 'Pristine' : What, Why, How
FYI there's a CyanogenMod 9 - Bug report / Discussion thread / FAQ under general forum, u should read that thread. HERE
keithross39 said:
Search on the W forum for a thread by @pepoluan about 'pristine' wiping your phone....it will help you achieve the 'fresh start' that you want....and yes, unless you move your nandroid to alternative storage, you will probably lose it.
And as far as I remember, CM9 has the option to swap storage mounts which will allow you to use your external micro SD card as phone storage......
Find it by......
Menu>>settings>>storage>>menu>>advanced....
and then 'tick' the box against (something like) 'use SD card as phone storage' (it's been a while so I can't remember the exact wording)......
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
dec0der said:
using reset to factory settings will not lose your root, afair coz i've used that b4.
when u install custom rom basically ur stock rom (original rom) is already erased, right? so i don't think it will restore ur stock rom, u can try it though
Settings -> Storage->Menu-Button->Storage configuration (a restart might be necessary)
FYI there's a CyanogenMod 9 - Bug report / Discussion thread / FAQ under general forum, u should read that thread. HERE
Click to expand...
Click to collapse
Thank you very much keithross39 and dec0der ,
I have resetted my phone without any problems at all ,
I just have another newbie question please
I see people talking about ROMs saying for example : CM9 EOL Honeyx Kernel
I don't inderstand anything in this except CM9 , But what is EOL , and what is Honeyx Kernel ?
I downloaded my CM9 version from the official thread here
I know it is written EOL in the Title of the official thread but I don't know what it mean ? and what is the Kernel ? and what name of the kernel I use ?
EOL as far as I know simply means end of line....which means the final release or no further development.... and the kernel is just something you flash on top of the ROM which allows greater control of things like processor speed, voltage etc. Flashing a kernel *can* have it's advantages, but it is not something you *have* to do......
Sent from my GT-I9100 using xda app-developers app
keithross39 said:
EOL as far as I know simply means end of line....which means the final release or no further development.... and the kernel is just something you flash on top of the ROM which allows greater control of things like processor speed, voltage etc. Flashing a kernel *can* have it's advantages, but it is not something you *have* to do......
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Yes thanks I get it .
But from your experience is flashing kernel is as risky as flashing ROMs ,and do I have to also swap my files when installing it , and if I have a CM 9 . Can I flash any kernel with the name CM9 on it and not CM10 right ?( I am sorry but indeed I was very scared to flash ROM because of the too much talk about bricking the phone ) .
When you modify your phone there's *always* going to be an element of risk.....whether that risk is higher when flashing a kernel or not, I don't know......I've always stayed with the kernel that comes with my chosen ROM. To answer another question, yes you have to use a kernel that is compatible with your ROMs OS version. As for the storage mount swap, I'm fairly certain that this is ROM controlled as opposed to kernel controlled, so you should be OK....
Sent from my GT-I9100 using xda app-developers app
keithross39 said:
When you modify your phone there's *always* going to be an element of risk.....whether that risk is higher when flashing a kernel or not, I don't know......I've always stayed with the kernel that comes with my chosen ROM. To answer another question, yes you have to use a kernel that is compatible with your ROMs OS version. As for the storage mount swap, I'm fairly certain that this is ROM controlled as opposed to kernel controlled, so you should be OK....
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Thanks keithross ,
So I think I am fine with just the CM9 and no need for other kernel ( at least for now ) .
Yeah.....you can always try a kernel another time....but do yourself a favor..... read as much as you can about every kernel you are considering before you flash it.....in the same way that every ROM is different, every kernel will be different and bring different tweaks to your phone.......
Sent from my GT-I9100 using xda app-developers app
AhmedPower said:
Thanks keithross ,
So I think I am fine with just the CM9 and no need for other kernel ( at least for now ) .
Click to expand...
Click to collapse
First of all it´s nice to see there are still such smart noobs like you who are posting their questions in the correct section. For this you deserve a 1+
About the rest it´s like keithross already said. First become familiar with your fevorite ROM. There is still time to test all the kernels out.
All the custom kernels are supposed to incrase battery life but also have some other tweaks included. Most of them are very similar because they are using a lot of the exact same tweaks like for example the ones for battery. However there are always some differences like the amount of added tweaks.
This is because all the Developers do have slightly different priorities to what is important to tweak. Some devs are more conservative and just adding the tweaks that are really important in his opinion and are also known to work properly with all devices whereas other devs are more openminded to add some new tweaks.
However this doesn´t mean some of them are better and some of them are worse. It´s just like that. One and the same kernel can work very good on one SGW whereas it may cause some problems on a secound SGW due to the included tweaks. Therefore it´s also good to have such a wide-spread variety of custom kernels, so everyone can find out which of them works best on his device.
People should start using Google.
Go to this URL and press 'Ctrl+F' or menu button then find on phones.
Type Kernel and discover things you never knew. As keithross said, research on these kind of stuff before you flash em.
I honestly learnt mine from here but you are free to use Google.
If you use the second link, ignore any talk about sbf. Its Motorola related.
Special thanks for all of you keithross , honeyx , and idelta ...
I think I have been very familial with the CM9 and I will be reading about your kernel honeyx very soon , I want to try it first one
Thanks again